WEBVTT Kind: captions Language: en 00:00:18.140 --> 00:00:21.859 align:start position:0% so<00:00:19.140> I'm<00:00:19.529> gonna<00:00:19.650> be<00:00:19.830> talking<00:00:19.980> about<00:00:20.869> something 00:00:21.859 --> 00:00:21.869 align:start position:0% so I'm gonna be talking about something 00:00:21.869 --> 00:00:24.650 align:start position:0% so I'm gonna be talking about something a<00:00:22.020> little<00:00:22.140> bit<00:00:22.320> different<00:00:22.680> today<00:00:23.269> as<00:00:24.269> Jesse 00:00:24.650 --> 00:00:24.660 align:start position:0% a little bit different today as Jesse 00:00:24.660 --> 00:00:26.570 align:start position:0% a little bit different today as Jesse mentioned<00:00:24.960> my<00:00:25.019> name<00:00:25.050> is<00:00:25.320> Taylor<00:00:25.500> Goering<00:00:26.010> I've 00:00:26.570 --> 00:00:26.580 align:start position:0% mentioned my name is Taylor Goering I've 00:00:26.580 --> 00:00:28.730 align:start position:0% mentioned my name is Taylor Goering I've been<00:00:26.970> working<00:00:27.750> with<00:00:27.779> the<00:00:27.990> etherion<00:00:28.349> project 00:00:28.730 --> 00:00:28.740 align:start position:0% been working with the etherion project 00:00:28.740 --> 00:00:31.790 align:start position:0% been working with the etherion project for<00:00:28.920> about<00:00:29.039> two<00:00:29.279> years<00:00:29.490> now<00:00:30.590> she's<00:00:31.590> quite<00:00:31.769> a 00:00:31.790 --> 00:00:31.800 align:start position:0% for about two years now she's quite a 00:00:31.800 --> 00:00:34.160 align:start position:0% for about two years now she's quite a long<00:00:31.980> time<00:00:32.009> in<00:00:32.279> this<00:00:32.340> space<00:00:32.520> I<00:00:32.700> suppose<00:00:33.170> I've 00:00:34.160 --> 00:00:34.170 align:start position:0% long time in this space I suppose I've 00:00:34.170 --> 00:00:35.630 align:start position:0% long time in this space I suppose I've been<00:00:34.350> doing<00:00:34.530> a<00:00:34.620> variety<00:00:34.829> of<00:00:34.980> things<00:00:35.250> from 00:00:35.630 --> 00:00:35.640 align:start position:0% been doing a variety of things from 00:00:35.640 --> 00:00:38.660 align:start position:0% been doing a variety of things from server<00:00:36.000> administration<00:00:36.660> to<00:00:37.550> working<00:00:38.550> on<00:00:38.610> the 00:00:38.660 --> 00:00:38.670 align:start position:0% server administration to working on the 00:00:38.670 --> 00:00:41.080 align:start position:0% server administration to working on the website<00:00:38.790> I've<00:00:39.780> helped<00:00:40.079> with<00:00:40.170> the<00:00:40.260> go<00:00:40.410> client 00:00:41.080 --> 00:00:41.090 align:start position:0% website I've helped with the go client 00:00:41.090 --> 00:00:44.930 align:start position:0% website I've helped with the go client on<00:00:42.090> Jeffrey<00:00:42.390> Wilkie's<00:00:42.719> team<00:00:43.670> I've<00:00:44.670> written 00:00:44.930 --> 00:00:44.940 align:start position:0% on Jeffrey Wilkie's team I've written 00:00:44.940 --> 00:00:46.850 align:start position:0% on Jeffrey Wilkie's team I've written some<00:00:45.120> blog<00:00:45.390> posts<00:00:45.420> I'm<00:00:45.960> active<00:00:46.230> on<00:00:46.320> reddit<00:00:46.649> so 00:00:46.850 --> 00:00:46.860 align:start position:0% some blog posts I'm active on reddit so 00:00:46.860 --> 00:00:48.260 align:start position:0% some blog posts I'm active on reddit so you<00:00:46.920> might<00:00:47.280> have<00:00:47.370> seen<00:00:47.520> my<00:00:47.640> name<00:00:47.789> around<00:00:48.030> there 00:00:48.260 --> 00:00:48.270 align:start position:0% you might have seen my name around there 00:00:48.270 --> 00:00:51.770 align:start position:0% you might have seen my name around there a<00:00:48.450> bit<00:00:50.149> but<00:00:51.149> I'm<00:00:51.239> not<00:00:51.329> going<00:00:51.420> to<00:00:51.480> talk<00:00:51.660> about 00:00:51.770 --> 00:00:51.780 align:start position:0% a bit but I'm not going to talk about 00:00:51.780 --> 00:00:54.229 align:start position:0% a bit but I'm not going to talk about what<00:00:52.050> we've<00:00:52.170> worked<00:00:52.590> on<00:00:52.800> to<00:00:53.280> date<00:00:53.460> so<00:00:53.760> far<00:00:53.789> I 00:00:54.229 --> 00:00:54.239 align:start position:0% what we've worked on to date so far I 00:00:54.239 --> 00:00:56.630 align:start position:0% what we've worked on to date so far I want<00:00:54.660> to<00:00:54.690> talk<00:00:54.809> about<00:00:54.930> the<00:00:55.110> future<00:00:55.260> and<00:00:55.640> where 00:00:56.630 --> 00:00:56.640 align:start position:0% want to talk about the future and where 00:00:56.640 --> 00:01:00.920 align:start position:0% want to talk about the future and where athyrium<00:00:57.329> could<00:00:57.629> bring<00:00:57.809> us<00:00:57.989> in<00:00:58.739> 2<00:00:59.609> 4<00:01:00.120> 5<00:01:00.149> 10 00:01:00.920 --> 00:01:00.930 align:start position:0% athyrium could bring us in 2 4 5 10 00:01:00.930 --> 00:01:03.319 align:start position:0% athyrium could bring us in 2 4 5 10 years<00:01:01.609> there's<00:01:02.609> a<00:01:02.670> lot<00:01:02.850> of<00:01:02.879> interest<00:01:03.270> from 00:01:03.319 --> 00:01:03.329 align:start position:0% years there's a lot of interest from 00:01:03.329 --> 00:01:06.350 align:start position:0% years there's a lot of interest from enterprises<00:01:04.199> out<00:01:04.320> there<00:01:04.559> and<00:01:04.970> although<00:01:05.970> the 00:01:06.350 --> 00:01:06.360 align:start position:0% enterprises out there and although the 00:01:06.360 --> 00:01:10.070 align:start position:0% enterprises out there and although the public<00:01:06.900> block<00:01:07.799> chain<00:01:08.070> gets<00:01:08.220> a<00:01:08.369> lot<00:01:08.490> of<00:01:09.080> the 00:01:10.070 --> 00:01:10.080 align:start position:0% public block chain gets a lot of the 00:01:10.080 --> 00:01:11.899 align:start position:0% public block chain gets a lot of the spotlight<00:01:10.619> in<00:01:10.799> the<00:01:10.830> limelight<00:01:11.070> I<00:01:11.460> think<00:01:11.760> there 00:01:11.899 --> 00:01:11.909 align:start position:0% spotlight in the limelight I think there 00:01:11.909 --> 00:01:14.090 align:start position:0% spotlight in the limelight I think there is<00:01:12.119> a<00:01:12.479> case<00:01:12.750> to<00:01:12.930> be<00:01:12.960> made<00:01:13.049> that<00:01:13.229> a<00:01:13.439> film<00:01:13.770> can<00:01:14.070> be 00:01:14.090 --> 00:01:14.100 align:start position:0% is a case to be made that a film can be 00:01:14.100 --> 00:01:16.460 align:start position:0% is a case to be made that a film can be used<00:01:14.549> in<00:01:14.850> an<00:01:14.970> enterprise<00:01:15.150> environment<00:01:15.810> not 00:01:16.460 --> 00:01:16.470 align:start position:0% used in an enterprise environment not 00:01:16.470 --> 00:01:18.740 align:start position:0% used in an enterprise environment not just<00:01:16.500> for<00:01:16.950> removing<00:01:17.369> trust<00:01:17.700> and<00:01:18.030> removing 00:01:18.740 --> 00:01:18.750 align:start position:0% just for removing trust and removing 00:01:18.750 --> 00:01:20.690 align:start position:0% just for removing trust and removing intermediaries<00:01:19.500> but<00:01:19.979> I<00:01:20.040> think<00:01:20.100> in<00:01:20.280> a<00:01:20.340> general 00:01:20.690 --> 00:01:20.700 align:start position:0% intermediaries but I think in a general 00:01:20.700 --> 00:01:22.910 align:start position:0% intermediaries but I think in a general sense<00:01:20.850> as<00:01:21.090> technology<00:01:22.020> stack<00:01:22.290> athyrium<00:01:22.860> is 00:01:22.910 --> 00:01:22.920 align:start position:0% sense as technology stack athyrium is 00:01:22.920 --> 00:01:26.480 align:start position:0% sense as technology stack athyrium is really<00:01:23.130> powerful<00:01:24.409> so<00:01:25.409> the<00:01:25.500> things<00:01:25.710> I<00:01:25.830> think 00:01:26.480 --> 00:01:26.490 align:start position:0% really powerful so the things I think 00:01:26.490 --> 00:01:27.920 align:start position:0% really powerful so the things I think that<00:01:26.640> it<00:01:26.729> can<00:01:26.820> bring<00:01:26.970> to<00:01:27.150> you<00:01:27.270> your 00:01:27.920 --> 00:01:27.930 align:start position:0% that it can bring to you your 00:01:27.930 --> 00:01:29.870 align:start position:0% that it can bring to you your environment<00:01:28.439> if<00:01:28.500> you're<00:01:28.680> an<00:01:28.770> IT<00:01:28.890> manager<00:01:29.130> or 00:01:29.870 --> 00:01:29.880 align:start position:0% environment if you're an IT manager or 00:01:29.880 --> 00:01:33.230 align:start position:0% environment if you're an IT manager or an<00:01:30.060> executive<00:01:31.130> basically<00:01:32.130> my<00:01:32.310> cell<00:01:32.640> to<00:01:32.850> you<00:01:32.939> is 00:01:33.230 --> 00:01:33.240 align:start position:0% an executive basically my cell to you is 00:01:33.240 --> 00:01:34.819 align:start position:0% an executive basically my cell to you is that<00:01:33.270> a<00:01:33.630> human<00:01:33.900> can<00:01:34.170> increase<00:01:34.650> agility 00:01:34.819 --> 00:01:34.829 align:start position:0% that a human can increase agility 00:01:34.829 --> 00:01:40.819 align:start position:0% that a human can increase agility reduced<00:01:35.820> risk<00:01:36.180> and<00:01:36.450> lower<00:01:36.689> costs<00:01:39.500> so<00:01:40.500> really 00:01:40.819 --> 00:01:40.829 align:start position:0% reduced risk and lower costs so really 00:01:40.829 --> 00:01:42.440 align:start position:0% reduced risk and lower costs so really the<00:01:41.040> first<00:01:41.189> question<00:01:41.579> is<00:01:41.670> do<00:01:42.180> blockchains 00:01:42.440 --> 00:01:42.450 align:start position:0% the first question is do blockchains 00:01:42.450 --> 00:01:47.350 align:start position:0% the first question is do blockchains have<00:01:42.869> a<00:01:42.899> role<00:01:43.170> in<00:01:43.439> the<00:01:43.500> private<00:01:44.189> environment 00:01:47.350 --> 00:01:47.360 align:start position:0% 00:01:47.360 --> 00:01:49.520 align:start position:0% to<00:01:48.360> answer<00:01:48.689> this<00:01:48.840> we<00:01:49.049> really<00:01:49.290> need<00:01:49.439> to 00:01:49.520 --> 00:01:49.530 align:start position:0% to answer this we really need to 00:01:49.530 --> 00:01:51.050 align:start position:0% to answer this we really need to understand<00:01:49.979> a<00:01:50.070> little<00:01:50.189> bit<00:01:50.310> more<00:01:50.520> about<00:01:50.759> what 00:01:51.050 --> 00:01:51.060 align:start position:0% understand a little bit more about what 00:01:51.060 --> 00:01:54.499 align:start position:0% understand a little bit more about what is<00:01:51.659> a<00:01:52.259> block<00:01:52.470> chain<00:01:52.710> where<00:01:53.640> it<00:01:53.790> came<00:01:53.939> from<00:01:54.000> how 00:01:54.499 --> 00:01:54.509 align:start position:0% is a block chain where it came from how 00:01:54.509 --> 00:01:57.289 align:start position:0% is a block chain where it came from how we<00:01:54.780> got<00:01:54.990> here<00:01:55.020> and<00:01:55.700> to<00:01:56.700> do<00:01:56.820> that<00:01:56.969> we<00:01:57.119> need<00:01:57.149> to 00:01:57.289 --> 00:01:57.299 align:start position:0% we got here and to do that we need to 00:01:57.299 --> 00:01:58.520 align:start position:0% we got here and to do that we need to know<00:01:57.479> that<00:01:57.689> bought<00:01:57.869> jeans<00:01:58.079> are<00:01:58.259> really<00:01:58.290> a 00:01:58.520 --> 00:01:58.530 align:start position:0% know that bought jeans are really a 00:01:58.530 --> 00:02:01.160 align:start position:0% know that bought jeans are really a culmination<00:01:58.979> of<00:01:59.159> prior<00:01:59.369> work<00:01:59.750> Satoshi<00:02:00.750> didn't 00:02:01.160 --> 00:02:01.170 align:start position:0% culmination of prior work Satoshi didn't 00:02:01.170 --> 00:02:02.630 align:start position:0% culmination of prior work Satoshi didn't just<00:02:01.290> come<00:02:01.439> up<00:02:01.560> with<00:02:01.680> this<00:02:01.770> randomly<00:02:02.189> one<00:02:02.430> day 00:02:02.630 --> 00:02:02.640 align:start position:0% just come up with this randomly one day 00:02:02.640 --> 00:02:05.929 align:start position:0% just come up with this randomly one day all<00:02:03.060> this<00:02:03.119> magic<00:02:03.719> boom<00:02:04.079> there<00:02:04.439> it<00:02:04.469> is<00:02:04.649> no<00:02:05.549> it 00:02:05.929 --> 00:02:05.939 align:start position:0% all this magic boom there it is no it 00:02:05.939 --> 00:02:08.050 align:start position:0% all this magic boom there it is no it goes<00:02:06.090> back<00:02:06.299> to<00:02:06.390> the<00:02:06.509> 70s<00:02:06.930> ralph<00:02:07.619> merkle 00:02:08.050 --> 00:02:08.060 align:start position:0% goes back to the 70s ralph merkle 00:02:08.060 --> 00:02:10.639 align:start position:0% goes back to the 70s ralph merkle inventing<00:02:09.060> Merkel<00:02:09.690> hash<00:02:09.840> trees<00:02:10.200> patenting 00:02:10.639 --> 00:02:10.649 align:start position:0% inventing Merkel hash trees patenting 00:02:10.649 --> 00:02:12.940 align:start position:0% inventing Merkel hash trees patenting that<00:02:10.800> in<00:02:10.890> 1979 00:02:12.940 --> 00:02:12.950 align:start position:0% that in 1979 00:02:12.950 --> 00:02:15.470 align:start position:0% that in 1979 we<00:02:13.950> also<00:02:14.130> have<00:02:14.370> distributed<00:02:14.880> hash<00:02:15.060> tables 00:02:15.470 --> 00:02:15.480 align:start position:0% we also have distributed hash tables 00:02:15.480 --> 00:02:18.110 align:start position:0% we also have distributed hash tables became<00:02:15.750> really<00:02:15.990> popular<00:02:16.050> in<00:02:16.440> the<00:02:16.590> 90s<00:02:17.120> Napster 00:02:18.110 --> 00:02:18.120 align:start position:0% became really popular in the 90s Napster 00:02:18.120 --> 00:02:21.470 align:start position:0% became really popular in the 90s Napster was<00:02:18.540> a<00:02:19.140> big<00:02:19.730> way<00:02:20.730> that<00:02:20.910> this<00:02:21.030> kind<00:02:21.180> of<00:02:21.240> made<00:02:21.390> it 00:02:21.470 --> 00:02:21.480 align:start position:0% was a big way that this kind of made it 00:02:21.480 --> 00:02:23.440 align:start position:0% was a big way that this kind of made it into<00:02:21.780> the<00:02:21.810> public<00:02:22.470> mind<00:02:22.830> chair<00:02:23.130> and 00:02:23.440 --> 00:02:23.450 align:start position:0% into the public mind chair and 00:02:23.450 --> 00:02:25.820 align:start position:0% into the public mind chair and eventually<00:02:24.450> we<00:02:24.480> had<00:02:24.750> the<00:02:25.440> proof<00:02:25.590> of<00:02:25.709> work 00:02:25.820 --> 00:02:25.830 align:start position:0% eventually we had the proof of work 00:02:25.830 --> 00:02:29.390 align:start position:0% eventually we had the proof of work system<00:02:26.220> which<00:02:26.580> as<00:02:26.910> I<00:02:27.390> read<00:02:27.630> was<00:02:28.050> first<00:02:28.560> kind<00:02:29.310> of 00:02:29.390 --> 00:02:29.400 align:start position:0% system which as I read was first kind of 00:02:29.400 --> 00:02:31.760 align:start position:0% system which as I read was first kind of developed<00:02:29.820> around<00:02:30.030> 93<00:02:30.870> and<00:02:31.140> then<00:02:31.320> finally 00:02:31.760 --> 00:02:31.770 align:start position:0% developed around 93 and then finally 00:02:31.770 --> 00:02:35.180 align:start position:0% developed around 93 and then finally formalized<00:02:32.190> in<00:02:32.340> 1999<00:02:33.470> and<00:02:34.470> these<00:02:34.950> three 00:02:35.180 --> 00:02:35.190 align:start position:0% formalized in 1999 and these three 00:02:35.190 --> 00:02:37.130 align:start position:0% formalized in 1999 and these three components<00:02:35.340> are<00:02:35.730> kind<00:02:35.940> of<00:02:36.000> interesting<00:02:36.720> in 00:02:37.130 --> 00:02:37.140 align:start position:0% components are kind of interesting in 00:02:37.140 --> 00:02:39.229 align:start position:0% components are kind of interesting in particular<00:02:37.380> in<00:02:37.680> certain<00:02:37.890> ways<00:02:38.090> the<00:02:39.090> way<00:02:39.209> I 00:02:39.229 --> 00:02:39.239 align:start position:0% particular in certain ways the way I 00:02:39.239 --> 00:02:40.790 align:start position:0% particular in certain ways the way I look<00:02:39.510> at<00:02:39.660> it<00:02:39.690> the<00:02:39.930> hash<00:02:40.290> trees<00:02:40.620> are 00:02:40.790 --> 00:02:40.800 align:start position:0% look at it the hash trees are 00:02:40.800 --> 00:02:43.100 align:start position:0% look at it the hash trees are effectively<00:02:41.190> you<00:02:42.120> know<00:02:42.239> this<00:02:42.420> data<00:02:42.720> structure 00:02:43.100 --> 00:02:43.110 align:start position:0% effectively you know this data structure 00:02:43.110 --> 00:02:45.530 align:start position:0% effectively you know this data structure that<00:02:43.650> the<00:02:43.800> blockchain<00:02:43.980> is<00:02:44.250> built<00:02:44.430> on<00:02:44.580> the 00:02:45.530 --> 00:02:45.540 align:start position:0% that the blockchain is built on the 00:02:45.540 --> 00:02:48.260 align:start position:0% that the blockchain is built on the distributed<00:02:46.470> hash<00:02:46.590> tables<00:02:47.040> or<00:02:47.310> dhts<00:02:47.910> is<00:02:48.239> a 00:02:48.260 --> 00:02:48.270 align:start position:0% distributed hash tables or dhts is a 00:02:48.270 --> 00:02:50.380 align:start position:0% distributed hash tables or dhts is a kind<00:02:48.989> of<00:02:49.020> this<00:02:49.140> networking<00:02:49.560> component<00:02:49.890> and 00:02:50.380 --> 00:02:50.390 align:start position:0% kind of this networking component and 00:02:50.390 --> 00:02:52.729 align:start position:0% kind of this networking component and finally<00:02:51.390> we<00:02:51.510> have<00:02:51.630> this<00:02:51.720> proof<00:02:52.019> of<00:02:52.200> work<00:02:52.380> thing 00:02:52.729 --> 00:02:52.739 align:start position:0% finally we have this proof of work thing 00:02:52.739 --> 00:02:55.280 align:start position:0% finally we have this proof of work thing and<00:02:52.980> this<00:02:53.760> seems<00:02:53.970> to<00:02:54.060> be<00:02:54.150> the<00:02:54.330> most<00:02:54.510> confusing 00:02:55.280 --> 00:02:55.290 align:start position:0% and this seems to be the most confusing 00:02:55.290 --> 00:02:59.990 align:start position:0% and this seems to be the most confusing part<00:02:56.040> of<00:02:56.280> it<00:02:56.370> all<00:02:57.769> what<00:02:58.769> are<00:02:58.890> miners<00:02:59.400> what<00:02:59.910> are 00:02:59.990 --> 00:03:00.000 align:start position:0% part of it all what are miners what are 00:03:00.000 --> 00:03:01.340 align:start position:0% part of it all what are miners what are they<00:03:00.090> doing<00:03:00.540> people<00:03:00.870> kind<00:03:01.019> of<00:03:01.110> call<00:03:01.230> it 00:03:01.340 --> 00:03:01.350 align:start position:0% they doing people kind of call it 00:03:01.350 --> 00:03:06.500 align:start position:0% they doing people kind of call it validator<00:03:01.890> sometimes<00:03:04.010> in<00:03:05.010> some<00:03:05.310> circles<00:03:05.730> this 00:03:06.500 --> 00:03:06.510 align:start position:0% validator sometimes in some circles this 00:03:06.510 --> 00:03:08.360 align:start position:0% validator sometimes in some circles this seems<00:03:06.750> to<00:03:06.840> be<00:03:06.900> a<00:03:07.019> huge<00:03:07.560> point<00:03:07.830> of<00:03:08.040> contention 00:03:08.360 --> 00:03:08.370 align:start position:0% seems to be a huge point of contention 00:03:08.370 --> 00:03:12.380 align:start position:0% seems to be a huge point of contention that<00:03:09.110> only<00:03:10.110> proof<00:03:10.410> of<00:03:10.560> work<00:03:10.709> can<00:03:10.890> exist<00:03:11.390> but 00:03:12.380 --> 00:03:12.390 align:start position:0% that only proof of work can exist but 00:03:12.390 --> 00:03:13.940 align:start position:0% that only proof of work can exist but even<00:03:12.600> with<00:03:12.720> an<00:03:12.810> etherion<00:03:13.290> we're<00:03:13.410> trying<00:03:13.709> to 00:03:13.940 --> 00:03:13.950 align:start position:0% even with an etherion we're trying to 00:03:13.950 --> 00:03:15.590 align:start position:0% even with an etherion we're trying to look<00:03:14.070> at<00:03:14.220> solutions<00:03:14.430> of<00:03:14.700> proof<00:03:14.940> of<00:03:15.060> stake<00:03:15.180> and 00:03:15.590 --> 00:03:15.600 align:start position:0% look at solutions of proof of stake and 00:03:15.600 --> 00:03:21.350 align:start position:0% look at solutions of proof of stake and kasper<00:03:16.019> and<00:03:16.050> so<00:03:16.290> forth<00:03:19.910> so<00:03:20.910> that's<00:03:21.060> great 00:03:21.350 --> 00:03:21.360 align:start position:0% kasper and so forth so that's great 00:03:21.360 --> 00:03:23.030 align:start position:0% kasper and so forth so that's great you've<00:03:21.870> told<00:03:22.049> me<00:03:22.140> what<00:03:22.230> block<00:03:22.650> chains<00:03:22.890> are 00:03:23.030 --> 00:03:23.040 align:start position:0% you've told me what block chains are 00:03:23.040 --> 00:03:28.780 align:start position:0% you've told me what block chains are made<00:03:23.190> of<00:03:23.310> but<00:03:24.090> what<00:03:24.239> do<00:03:24.329> they<00:03:24.420> really<00:03:24.630> do<00:03:27.260> now 00:03:28.780 --> 00:03:28.790 align:start position:0% made of but what do they really do now 00:03:28.790 --> 00:03:31.640 align:start position:0% made of but what do they really do now when<00:03:29.790> I<00:03:29.820> started<00:03:29.940> thinking<00:03:30.480> about<00:03:30.570> this<00:03:30.930> it 00:03:31.640 --> 00:03:31.650 align:start position:0% when I started thinking about this it 00:03:31.650 --> 00:03:33.860 align:start position:0% when I started thinking about this it kind<00:03:31.920> of<00:03:31.950> reminded<00:03:32.310> me<00:03:32.459> about<00:03:32.489> the<00:03:32.820> scene<00:03:33.060> from 00:03:33.860 --> 00:03:33.870 align:start position:0% kind of reminded me about the scene from 00:03:33.870 --> 00:03:36.860 align:start position:0% kind of reminded me about the scene from this<00:03:34.140> movie<00:03:34.500> idiocracy<00:03:35.390> really<00:03:36.390> fantastic 00:03:36.860 --> 00:03:36.870 align:start position:0% this movie idiocracy really fantastic 00:03:36.870 --> 00:03:38.600 align:start position:0% this movie idiocracy really fantastic movie<00:03:37.110> if<00:03:37.200> you<00:03:37.290> haven't<00:03:37.560> seen<00:03:37.680> it<00:03:37.829> wasn't 00:03:38.600 --> 00:03:38.610 align:start position:0% movie if you haven't seen it wasn't 00:03:38.610 --> 00:03:41.180 align:start position:0% movie if you haven't seen it wasn't terribly<00:03:38.910> popular<00:03:39.120> but<00:03:39.950> hilarious<00:03:40.950> in<00:03:41.070> its 00:03:41.180 --> 00:03:41.190 align:start position:0% terribly popular but hilarious in its 00:03:41.190 --> 00:03:44.120 align:start position:0% terribly popular but hilarious in its own<00:03:41.340> right<00:03:41.549> and<00:03:42.470> just<00:03:43.470> to<00:03:43.560> set<00:03:43.680> up<00:03:43.799> the<00:03:43.920> scene 00:03:44.120 --> 00:03:44.130 align:start position:0% own right and just to set up the scene 00:03:44.130 --> 00:03:46.490 align:start position:0% own right and just to set up the scene for<00:03:44.370> you<00:03:44.459> a<00:03:44.489> little<00:03:44.610> bit<00:03:44.850> the<00:03:45.810> main<00:03:46.019> character 00:03:46.490 --> 00:03:46.500 align:start position:0% for you a little bit the main character 00:03:46.500 --> 00:03:47.810 align:start position:0% for you a little bit the main character is<00:03:46.620> kind<00:03:46.829> of<00:03:46.890> trying<00:03:47.190> to<00:03:47.250> explain<00:03:47.549> to<00:03:47.700> his 00:03:47.810 --> 00:03:47.820 align:start position:0% is kind of trying to explain to his 00:03:47.820 --> 00:03:52.240 align:start position:0% is kind of trying to explain to his colleagues<00:03:48.170> that<00:03:49.489> putting<00:03:50.489> sports<00:03:51.150> drink<00:03:51.510> on 00:03:52.240 --> 00:03:52.250 align:start position:0% colleagues that putting sports drink on 00:03:52.250 --> 00:03:55.819 align:start position:0% colleagues that putting sports drink on plants<00:03:53.250> will<00:03:53.850> not<00:03:54.030> help<00:03:54.269> them<00:03:54.480> grow<00:03:54.829> they 00:03:55.819 --> 00:03:55.829 align:start position:0% plants will not help them grow they 00:03:55.829 --> 00:03:59.750 align:start position:0% plants will not help them grow they don't<00:03:55.980> quite<00:03:56.220> seem<00:03:56.640> to<00:03:56.730> understand<00:03:57.209> why<00:03:58.760> so 00:03:59.750 --> 00:03:59.760 align:start position:0% don't quite seem to understand why so 00:03:59.760 --> 00:04:02.390 align:start position:0% don't quite seem to understand why so let<00:04:00.750> me<00:04:00.780> just<00:04:00.989> let<00:04:01.320> you<00:04:01.440> watch<00:04:01.590> this<00:04:01.829> and<00:04:02.100> maybe 00:04:02.390 --> 00:04:02.400 align:start position:0% let me just let you watch this and maybe 00:04:02.400 --> 00:04:06.050 align:start position:0% let me just let you watch this and maybe you'll<00:04:02.579> get<00:04:02.730> the<00:04:02.820> idea<00:04:04.549> what's<00:04:05.549> killing<00:04:06.030> the 00:04:06.050 --> 00:04:06.060 align:start position:0% you'll get the idea what's killing the 00:04:06.060 --> 00:04:08.990 align:start position:0% you'll get the idea what's killing the crops<00:04:06.480> is<00:04:06.810> this<00:04:07.019> Brando<00:04:07.590> stuff<00:04:07.980> the<00:04:08.519> Broncos 00:04:08.990 --> 00:04:09.000 align:start position:0% crops is this Brando stuff the Broncos 00:04:09.000 --> 00:04:10.430 align:start position:0% crops is this Brando stuff the Broncos got<00:04:09.180> what<00:04:09.359> plants<00:04:09.480> crave<00:04:09.720> it's<00:04:10.260> got 00:04:10.430 --> 00:04:10.440 align:start position:0% got what plants crave it's got 00:04:10.440 --> 00:04:12.650 align:start position:0% got what plants crave it's got electrolytes<00:04:10.670> so<00:04:11.670> wait<00:04:11.820> a<00:04:11.850> minute<00:04:12.239> what 00:04:12.650 --> 00:04:12.660 align:start position:0% electrolytes so wait a minute what 00:04:12.660 --> 00:04:15.050 align:start position:0% electrolytes so wait a minute what you're<00:04:12.840> saying<00:04:13.140> is<00:04:13.560> that<00:04:13.890> you<00:04:14.160> want<00:04:14.190> us<00:04:14.609> to<00:04:14.850> put 00:04:15.050 --> 00:04:15.060 align:start position:0% you're saying is that you want us to put 00:04:15.060 --> 00:04:19.789 align:start position:0% you're saying is that you want us to put water<00:04:15.959> on<00:04:16.410> the<00:04:16.890> crops<00:04:16.919> yes<00:04:17.760> bladder<00:04:18.620> like<00:04:19.620> out 00:04:19.789 --> 00:04:19.799 align:start position:0% water on the crops yes bladder like out 00:04:19.799 --> 00:04:21.039 align:start position:0% water on the crops yes bladder like out the<00:04:19.950> toilet<00:04:20.340> well 00:04:21.039 --> 00:04:21.049 align:start position:0% the toilet well 00:04:21.049 --> 00:04:22.899 align:start position:0% the toilet well it<00:04:21.349> doesn't<00:04:21.650> have<00:04:21.829> to<00:04:22.039> be<00:04:22.069> out<00:04:22.280> of<00:04:22.310> the<00:04:22.490> toilet 00:04:22.899 --> 00:04:22.909 align:start position:0% it doesn't have to be out of the toilet 00:04:22.909 --> 00:04:24.670 align:start position:0% it doesn't have to be out of the toilet but<00:04:23.030> but<00:04:23.270> yeah<00:04:23.389> that's<00:04:23.449> the<00:04:23.780> idea<00:04:23.810> but 00:04:24.670 --> 00:04:24.680 align:start position:0% but but yeah that's the idea but 00:04:24.680 --> 00:04:26.980 align:start position:0% but but yeah that's the idea but brawndo's<00:04:25.009> got<00:04:25.250> what<00:04:25.460> plants<00:04:25.639> crave<00:04:26.000> it's<00:04:26.720> got 00:04:26.980 --> 00:04:26.990 align:start position:0% brawndo's got what plants crave it's got 00:04:26.990 --> 00:04:31.480 align:start position:0% brawndo's got what plants crave it's got electrolytes<00:04:27.169> okay<00:04:28.599> look<00:04:29.889> the<00:04:30.889> plants<00:04:31.310> aren't 00:04:31.480 --> 00:04:31.490 align:start position:0% electrolytes okay look the plants aren't 00:04:31.490 --> 00:04:33.129 align:start position:0% electrolytes okay look the plants aren't growing<00:04:31.610> so<00:04:32.300> i'm<00:04:32.419> pretty<00:04:32.629> sure<00:04:32.870> that<00:04:32.900> the 00:04:33.129 --> 00:04:33.139 align:start position:0% growing so i'm pretty sure that the 00:04:33.139 --> 00:04:35.170 align:start position:0% growing so i'm pretty sure that the Brando's<00:04:33.590> not<00:04:33.800> working<00:04:34.250> no<00:04:34.370> I'm<00:04:34.520> no<00:04:34.699> botanist 00:04:35.170 --> 00:04:35.180 align:start position:0% Brando's not working no I'm no botanist 00:04:35.180 --> 00:04:37.029 align:start position:0% Brando's not working no I'm no botanist but<00:04:35.210> I<00:04:35.419> do<00:04:35.509> know<00:04:35.780> that<00:04:35.810> if<00:04:36.259> you<00:04:36.409> put<00:04:36.620> water<00:04:36.889> on 00:04:37.029 --> 00:04:37.039 align:start position:0% but I do know that if you put water on 00:04:37.039 --> 00:04:40.029 align:start position:0% but I do know that if you put water on plants<00:04:37.520> they<00:04:37.849> grow<00:04:37.879> well<00:04:38.780> I've<00:04:39.020> never<00:04:39.440> seen<00:04:39.770> no 00:04:40.029 --> 00:04:40.039 align:start position:0% plants they grow well I've never seen no 00:04:40.039 --> 00:04:42.730 align:start position:0% plants they grow well I've never seen no plants<00:04:40.520> grouted<00:04:40.909> own<00:04:41.060> toilet<00:04:41.720> that's<00:04:42.409> good 00:04:42.730 --> 00:04:42.740 align:start position:0% plants grouted own toilet that's good 00:04:42.740 --> 00:04:44.260 align:start position:0% plants grouted own toilet that's good you<00:04:43.129> sure<00:04:43.280> you<00:04:43.310> want<00:04:43.580> to<00:04:43.669> smartest<00:04:44.030> guy<00:04:44.150> in<00:04:44.180> the 00:04:44.260 --> 00:04:44.270 align:start position:0% you sure you want to smartest guy in the 00:04:44.270 --> 00:04:47.830 align:start position:0% you sure you want to smartest guy in the world<00:04:44.330> yeah<00:04:45.610> okay<00:04:46.610> look<00:04:46.819> you<00:04:47.330> want<00:04:47.509> to<00:04:47.599> solve 00:04:47.830 --> 00:04:47.840 align:start position:0% world yeah okay look you want to solve 00:04:47.840 --> 00:04:49.689 align:start position:0% world yeah okay look you want to solve this<00:04:47.990> problem<00:04:48.470> I<00:04:48.560> want<00:04:48.800> to<00:04:48.860> get<00:04:48.979> my<00:04:49.099> pardon<00:04:49.490> so 00:04:49.689 --> 00:04:49.699 align:start position:0% this problem I want to get my pardon so 00:04:49.699 --> 00:04:52.210 align:start position:0% this problem I want to get my pardon so why<00:04:50.090> don't<00:04:50.270> we<00:04:50.330> just<00:04:50.569> try<00:04:50.960> it<00:04:50.990> okay<00:04:51.740> and<00:04:52.009> not 00:04:52.210 --> 00:04:52.220 align:start position:0% why don't we just try it okay and not 00:04:52.220 --> 00:04:55.119 align:start position:0% why don't we just try it okay and not worry<00:04:52.520> about<00:04:52.610> what<00:04:52.849> plants<00:04:53.270> crave<00:04:54.129> Brandon's 00:04:55.119 --> 00:04:55.129 align:start position:0% worry about what plants crave Brandon's 00:04:55.129 --> 00:04:57.850 align:start position:0% worry about what plants crave Brandon's got<00:04:55.370> look<00:04:55.610> thanks<00:04:55.969> Dave<00:04:56.229> yeah<00:04:57.229> it's<00:04:57.620> got 00:04:57.850 --> 00:04:57.860 align:start position:0% got look thanks Dave yeah it's got 00:04:57.860 --> 00:05:00.640 align:start position:0% got look thanks Dave yeah it's got electrolytes<00:04:58.120> what<00:04:59.120> are<00:04:59.449> electrolytes<00:04:59.690> they 00:05:00.640 --> 00:05:00.650 align:start position:0% electrolytes what are electrolytes they 00:05:00.650 --> 00:05:06.070 align:start position:0% electrolytes what are electrolytes they even<00:05:00.949> know<00:05:03.039> so<00:05:04.039> what<00:05:04.610> our<00:05:04.759> block<00:05:05.120> chains<00:05:05.479> do<00:05:05.960> we 00:05:06.070 --> 00:05:06.080 align:start position:0% even know so what our block chains do we 00:05:06.080 --> 00:05:09.730 align:start position:0% even know so what our block chains do we even<00:05:06.229> know<00:05:08.050> that's<00:05:09.050> what<00:05:09.259> I<00:05:09.289> want<00:05:09.530> to<00:05:09.590> ask 00:05:09.730 --> 00:05:09.740 align:start position:0% even know that's what I want to ask 00:05:09.740 --> 00:05:10.930 align:start position:0% even know that's what I want to ask these<00:05:10.009> people<00:05:10.190> who<00:05:10.460> don't<00:05:10.669> seem<00:05:10.849> to 00:05:10.930 --> 00:05:10.940 align:start position:0% these people who don't seem to 00:05:10.940 --> 00:05:13.149 align:start position:0% these people who don't seem to understand<00:05:11.479> what<00:05:12.110> I<00:05:12.139> understand<00:05:12.860> they<00:05:13.009> seem 00:05:13.149 --> 00:05:13.159 align:start position:0% understand what I understand they seem 00:05:13.159 --> 00:05:14.469 align:start position:0% understand what I understand they seem to<00:05:13.190> have<00:05:13.280> a<00:05:13.400> slightly<00:05:13.909> different<00:05:14.240> perspective 00:05:14.469 --> 00:05:14.479 align:start position:0% to have a slightly different perspective 00:05:14.479 --> 00:05:18.879 align:start position:0% to have a slightly different perspective on<00:05:15.020> the<00:05:15.259> view<00:05:15.889> than<00:05:16.039> I<00:05:16.129> do<00:05:17.469> for<00:05:18.469> me<00:05:18.560> block 00:05:18.879 --> 00:05:18.889 align:start position:0% on the view than I do for me block 00:05:18.889 --> 00:05:21.100 align:start position:0% on the view than I do for me block chains<00:05:19.129> are<00:05:19.250> a<00:05:19.280> tool<00:05:19.900> they're<00:05:20.900> really 00:05:21.100 --> 00:05:21.110 align:start position:0% chains are a tool they're really 00:05:21.110 --> 00:05:23.290 align:start position:0% chains are a tool they're really wonderful<00:05:21.740> tool<00:05:21.949> but<00:05:22.909> they're<00:05:23.030> not<00:05:23.120> going<00:05:23.240> to 00:05:23.290 --> 00:05:23.300 align:start position:0% wonderful tool but they're not going to 00:05:23.300 --> 00:05:26.559 align:start position:0% wonderful tool but they're not going to replace<00:05:23.569> all<00:05:23.810> other<00:05:24.169> tools<00:05:24.669> though<00:05:25.669> hopefully 00:05:26.559 --> 00:05:26.569 align:start position:0% replace all other tools though hopefully 00:05:26.569 --> 00:05:29.140 align:start position:0% replace all other tools though hopefully maybe<00:05:27.289> join<00:05:27.770> an<00:05:27.919> arsenal<00:05:28.370> of<00:05:28.460> other<00:05:28.639> solutions 00:05:29.140 --> 00:05:29.150 align:start position:0% maybe join an arsenal of other solutions 00:05:29.150 --> 00:05:31.420 align:start position:0% maybe join an arsenal of other solutions that<00:05:29.270> are<00:05:29.330> out<00:05:29.509> there<00:05:30.009> but<00:05:31.009> really<00:05:31.310> the 00:05:31.420 --> 00:05:31.430 align:start position:0% that are out there but really the 00:05:31.430 --> 00:05:33.550 align:start position:0% that are out there but really the properties<00:05:32.120> of<00:05:32.150> the<00:05:32.389> block<00:05:32.569> chain<00:05:32.599> dictate 00:05:33.550 --> 00:05:33.560 align:start position:0% properties of the block chain dictate 00:05:33.560 --> 00:05:36.550 align:start position:0% properties of the block chain dictate the<00:05:33.710> use<00:05:33.860> case<00:05:34.130> my<00:05:35.120> opinion<00:05:35.539> is<00:05:35.719> bitcoins<00:05:36.440> are 00:05:36.550 --> 00:05:36.560 align:start position:0% the use case my opinion is bitcoins are 00:05:36.560 --> 00:05:38.950 align:start position:0% the use case my opinion is bitcoins are really<00:05:36.860> good<00:05:37.009> at<00:05:37.130> value<00:05:37.430> transfer<00:05:37.960> etherium 00:05:38.950 --> 00:05:38.960 align:start position:0% really good at value transfer etherium 00:05:38.960 --> 00:05:40.649 align:start position:0% really good at value transfer etherium is<00:05:39.020> really<00:05:39.259> good<00:05:39.440> at<00:05:39.529> trusted<00:05:39.860> computation 00:05:40.649 --> 00:05:40.659 align:start position:0% is really good at trusted computation 00:05:40.659 --> 00:05:44.290 align:start position:0% is really good at trusted computation both<00:05:41.659> can<00:05:41.900> probably<00:05:42.409> do<00:05:42.529> the<00:05:42.680> other<00:05:42.830> thing<00:05:43.300> but 00:05:44.290 --> 00:05:44.300 align:start position:0% both can probably do the other thing but 00:05:44.300 --> 00:05:47.080 align:start position:0% both can probably do the other thing but really<00:05:44.690> they<00:05:45.110> have<00:05:45.349> their<00:05:45.560> niche<00:05:45.740> and<00:05:46.090> that's 00:05:47.080 --> 00:05:47.090 align:start position:0% really they have their niche and that's 00:05:47.090 --> 00:05:49.390 align:start position:0% really they have their niche and that's kind<00:05:47.419> of<00:05:47.509> it<00:05:47.870> makes<00:05:47.960> sense<00:05:48.349> we<00:05:48.620> see<00:05:48.860> software 00:05:49.390 --> 00:05:49.400 align:start position:0% kind of it makes sense we see software 00:05:49.400 --> 00:05:51.430 align:start position:0% kind of it makes sense we see software serves<00:05:49.879> different<00:05:50.240> roles<00:05:50.690> and<00:05:50.960> for<00:05:51.169> different 00:05:51.430 --> 00:05:51.440 align:start position:0% serves different roles and for different 00:05:51.440 --> 00:05:53.589 align:start position:0% serves different roles and for different needs<00:05:51.909> it<00:05:52.909> shouldn't<00:05:53.210> really<00:05:53.270> surprise 00:05:53.589 --> 00:05:53.599 align:start position:0% needs it shouldn't really surprise 00:05:53.599 --> 00:05:57.249 align:start position:0% needs it shouldn't really surprise anybody<00:05:55.330> so<00:05:56.330> I<00:05:56.360> would<00:05:56.659> say<00:05:56.840> really 00:05:57.249 --> 00:05:57.259 align:start position:0% anybody so I would say really 00:05:57.259 --> 00:06:03.430 align:start position:0% anybody so I would say really blockchains<00:05:58.039> excel<00:05:58.699> at<00:05:59.000> coordination<00:06:02.440> but 00:06:03.430 --> 00:06:03.440 align:start position:0% blockchains excel at coordination but 00:06:03.440 --> 00:06:04.950 align:start position:0% blockchains excel at coordination but it's<00:06:03.590> not<00:06:03.740> just<00:06:04.190> about<00:06:04.310> the<00:06:04.550> blockchain 00:06:04.950 --> 00:06:04.960 align:start position:0% it's not just about the blockchain 00:06:04.960 --> 00:06:08.320 align:start position:0% it's not just about the blockchain theorems<00:06:05.960> written<00:06:06.349> about<00:06:06.610> more<00:06:07.610> components 00:06:08.320 --> 00:06:08.330 align:start position:0% theorems written about more components 00:06:08.330 --> 00:06:11.260 align:start position:0% theorems written about more components than<00:06:08.360> just<00:06:09.169> this<00:06:09.550> distributed<00:06:10.550> shared<00:06:10.610> ledger 00:06:11.260 --> 00:06:11.270 align:start position:0% than just this distributed shared ledger 00:06:11.270 --> 00:06:14.769 align:start position:0% than just this distributed shared ledger idea<00:06:12.129> we've<00:06:13.129> written<00:06:13.250> about<00:06:13.430> the<00:06:14.330> idea<00:06:14.690> of 00:06:14.769 --> 00:06:14.779 align:start position:0% idea we've written about the idea of 00:06:14.779 --> 00:06:17.439 align:start position:0% idea we've written about the idea of swarm<00:06:15.199> and<00:06:15.469> we're<00:06:16.279> not<00:06:16.400> the<00:06:16.520> only<00:06:16.550> company<00:06:17.150> or 00:06:17.439 --> 00:06:17.449 align:start position:0% swarm and we're not the only company or 00:06:17.449 --> 00:06:19.300 align:start position:0% swarm and we're not the only company or organization<00:06:18.229> out<00:06:18.349> there<00:06:18.379> trying<00:06:18.979> to<00:06:19.099> tackle 00:06:19.300 --> 00:06:19.310 align:start position:0% organization out there trying to tackle 00:06:19.310 --> 00:06:21.760 align:start position:0% organization out there trying to tackle this<00:06:19.750> there<00:06:20.750> are<00:06:20.840> lots<00:06:20.930> of<00:06:21.110> companies<00:06:21.469> trying 00:06:21.760 --> 00:06:21.770 align:start position:0% this there are lots of companies trying 00:06:21.770 --> 00:06:24.610 align:start position:0% this there are lots of companies trying to<00:06:21.860> do<00:06:22.009> a<00:06:22.310> distributed<00:06:22.940> storage<00:06:23.240> bit<00:06:24.199> torn<00:06:24.469> is 00:06:24.610 --> 00:06:24.620 align:start position:0% to do a distributed storage bit torn is 00:06:24.620 --> 00:06:26.800 align:start position:0% to do a distributed storage bit torn is obvious<00:06:25.460> kind<00:06:25.819> of<00:06:25.909> predecessor<00:06:26.479> to<00:06:26.539> all<00:06:26.659> of 00:06:26.800 --> 00:06:26.810 align:start position:0% obvious kind of predecessor to all of 00:06:26.810 --> 00:06:30.430 align:start position:0% obvious kind of predecessor to all of this<00:06:26.979> we've<00:06:27.979> also<00:06:28.340> talked<00:06:28.669> about<00:06:28.729> whisper<00:06:29.440> for 00:06:30.430 --> 00:06:30.440 align:start position:0% this we've also talked about whisper for 00:06:30.440 --> 00:06:33.080 align:start position:0% this we've also talked about whisper for dynamic<00:06:30.919> comms<00:06:31.190> messaging<00:06:31.940> etc 00:06:33.080 --> 00:06:33.090 align:start position:0% dynamic comms messaging etc 00:06:33.090 --> 00:06:34.909 align:start position:0% dynamic comms messaging etc and<00:06:33.210> this<00:06:33.360> is<00:06:33.480> kind<00:06:33.690> of<00:06:33.780> important<00:06:34.290> because<00:06:34.470> it 00:06:34.909 --> 00:06:34.919 align:start position:0% and this is kind of important because it 00:06:34.919 --> 00:06:37.250 align:start position:0% and this is kind of important because it goes<00:06:35.040> back<00:06:35.220> to<00:06:35.250> this<00:06:35.400> property's<00:06:35.970> idea<00:06:36.300> block 00:06:37.250 --> 00:06:37.260 align:start position:0% goes back to this property's idea block 00:06:37.260 --> 00:06:38.890 align:start position:0% goes back to this property's idea block chains<00:06:37.500> are<00:06:37.650> really<00:06:37.980> good<00:06:38.190> at<00:06:38.310> coordination 00:06:38.890 --> 00:06:38.900 align:start position:0% chains are really good at coordination 00:06:38.900 --> 00:06:42.230 align:start position:0% chains are really good at coordination they<00:06:39.900> can<00:06:40.260> do<00:06:40.500> storage<00:06:41.040> for<00:06:41.760> very<00:06:42.090> very 00:06:42.230 --> 00:06:42.240 align:start position:0% they can do storage for very very 00:06:42.240 --> 00:06:46.010 align:start position:0% they can do storage for very very expensive<00:06:42.810> costs<00:06:43.560> they<00:06:44.370> can<00:06:44.699> do<00:06:45.060> messaging 00:06:46.010 --> 00:06:46.020 align:start position:0% expensive costs they can do messaging 00:06:46.020 --> 00:06:50.300 align:start position:0% expensive costs they can do messaging for<00:06:46.740> very<00:06:47.190> very<00:06:47.550> slow<00:06:47.880> block<00:06:48.120> times<00:06:48.590> so<00:06:49.590> if<00:06:50.010> we 00:06:50.300 --> 00:06:50.310 align:start position:0% for very very slow block times so if we 00:06:50.310 --> 00:06:51.500 align:start position:0% for very very slow block times so if we kind<00:06:50.610> of<00:06:50.669> build<00:06:50.970> in<00:06:51.090> a<00:06:51.180> couple<00:06:51.419> extra 00:06:51.500 --> 00:06:51.510 align:start position:0% kind of build in a couple extra 00:06:51.510 --> 00:06:54.110 align:start position:0% kind of build in a couple extra components<00:06:52.290> we<00:06:53.100> can<00:06:53.280> actually<00:06:53.610> have<00:06:53.790> a<00:06:53.820> more 00:06:54.110 --> 00:06:54.120 align:start position:0% components we can actually have a more 00:06:54.120 --> 00:06:58.670 align:start position:0% components we can actually have a more diverse<00:06:54.300> ecosystem<00:06:55.139> of<00:06:55.229> tools<00:06:55.500> and<00:06:57.350> we<00:06:58.350> when 00:06:58.670 --> 00:06:58.680 align:start position:0% diverse ecosystem of tools and we when 00:06:58.680 --> 00:07:00.500 align:start position:0% diverse ecosystem of tools and we when we<00:06:58.710> start<00:06:58.979> looking<00:06:59.190> at<00:06:59.430> it<00:06:59.580> in<00:06:59.669> this<00:06:59.790> way<00:07:00.000> we 00:07:00.500 --> 00:07:00.510 align:start position:0% we start looking at it in this way we 00:07:00.510 --> 00:07:02.510 align:start position:0% we start looking at it in this way we can<00:07:00.570> kind<00:07:00.810> of<00:07:00.930> see<00:07:01.139> it<00:07:01.260> as<00:07:01.410> perhaps<00:07:01.889> a<00:07:02.250> network 00:07:02.510 --> 00:07:02.520 align:start position:0% can kind of see it as perhaps a network 00:07:02.520 --> 00:07:04.250 align:start position:0% can kind of see it as perhaps a network database<00:07:02.699> something<00:07:03.449> that<00:07:03.600> the<00:07:03.780> neg<00:07:03.930> gupta<00:07:04.229> is 00:07:04.250 --> 00:07:04.260 align:start position:0% database something that the neg gupta is 00:07:04.260 --> 00:07:06.500 align:start position:0% database something that the neg gupta is written<00:07:04.500> about<00:07:04.650> a<00:07:04.889> few<00:07:05.280> times<00:07:05.430> done<00:07:06.330> some 00:07:06.500 --> 00:07:06.510 align:start position:0% written about a few times done some 00:07:06.510 --> 00:07:10.070 align:start position:0% written about a few times done some speeches<00:07:06.750> on<00:07:07.820> this<00:07:08.820> is<00:07:08.990> basically<00:07:09.990> the 00:07:10.070 --> 00:07:10.080 align:start position:0% speeches on this is basically the 00:07:10.080 --> 00:07:12.920 align:start position:0% speeches on this is basically the scenario<00:07:10.500> where<00:07:10.680> code<00:07:10.979> is<00:07:11.250> data<00:07:11.940> they're<00:07:12.570> kind 00:07:12.920 --> 00:07:12.930 align:start position:0% scenario where code is data they're kind 00:07:12.930 --> 00:07:14.810 align:start position:0% scenario where code is data they're kind of<00:07:12.990> both<00:07:13.200> first-class<00:07:13.680> citizens<00:07:14.280> in<00:07:14.700> this 00:07:14.810 --> 00:07:14.820 align:start position:0% of both first-class citizens in this 00:07:14.820 --> 00:07:16.129 align:start position:0% of both first-class citizens in this environment<00:07:15.060> which<00:07:15.450> i<00:07:15.570> think<00:07:15.660> is<00:07:15.780> a<00:07:15.870> hugely 00:07:16.129 --> 00:07:16.139 align:start position:0% environment which i think is a hugely 00:07:16.139 --> 00:07:18.200 align:start position:0% environment which i think is a hugely powerful<00:07:16.380> idea<00:07:16.919> that<00:07:17.100> we<00:07:17.190> don't<00:07:17.700> fully<00:07:17.940> yet 00:07:18.200 --> 00:07:18.210 align:start position:0% powerful idea that we don't fully yet 00:07:18.210 --> 00:07:20.270 align:start position:0% powerful idea that we don't fully yet appreciate<00:07:18.800> yeah<00:07:19.800> automatic 00:07:20.270 --> 00:07:20.280 align:start position:0% appreciate yeah automatic 00:07:20.280 --> 00:07:23.360 align:start position:0% appreciate yeah automatic synchronization<00:07:20.690> fault<00:07:21.690> tolerance<00:07:22.370> identity 00:07:23.360 --> 00:07:23.370 align:start position:0% synchronization fault tolerance identity 00:07:23.370 --> 00:07:25.219 align:start position:0% synchronization fault tolerance identity for<00:07:23.580> free<00:07:23.790> and<00:07:24.060> it's<00:07:24.570> all<00:07:24.690> cryptographically 00:07:25.219 --> 00:07:25.229 align:start position:0% for free and it's all cryptographically 00:07:25.229 --> 00:07:28.670 align:start position:0% for free and it's all cryptographically secured<00:07:25.889> and<00:07:26.039> validated<00:07:26.550> to<00:07:27.419> me<00:07:27.600> as<00:07:27.900> an<00:07:28.500> IT 00:07:28.670 --> 00:07:28.680 align:start position:0% secured and validated to me as an IT 00:07:28.680 --> 00:07:30.379 align:start position:0% secured and validated to me as an IT person<00:07:29.190> who<00:07:29.610> might<00:07:29.729> be<00:07:29.880> implementing<00:07:30.330> a 00:07:30.379 --> 00:07:30.389 align:start position:0% person who might be implementing a 00:07:30.389 --> 00:07:33.469 align:start position:0% person who might be implementing a project<00:07:30.780> in<00:07:30.870> an<00:07:30.960> organization<00:07:32.330> these<00:07:33.330> are 00:07:33.469 --> 00:07:33.479 align:start position:0% project in an organization these are 00:07:33.479 --> 00:07:35.480 align:start position:0% project in an organization these are really<00:07:33.630> great<00:07:33.840> things<00:07:34.199> makes<00:07:34.830> my<00:07:35.070> life<00:07:35.250> much 00:07:35.480 --> 00:07:35.490 align:start position:0% really great things makes my life much 00:07:35.490 --> 00:07:37.580 align:start position:0% really great things makes my life much easier<00:07:35.550> and<00:07:36.150> I'd<00:07:36.750> like<00:07:36.930> to<00:07:37.050> bring<00:07:37.200> it<00:07:37.260> into<00:07:37.410> my 00:07:37.580 --> 00:07:37.590 align:start position:0% easier and I'd like to bring it into my 00:07:37.590 --> 00:07:44.360 align:start position:0% easier and I'd like to bring it into my organization<00:07:41.389> why<00:07:42.389> well<00:07:43.160> cryptography<00:07:44.160> gives 00:07:44.360 --> 00:07:44.370 align:start position:0% organization why well cryptography gives 00:07:44.370 --> 00:07:46.490 align:start position:0% organization why well cryptography gives us<00:07:44.520> nice<00:07:44.880> properties<00:07:45.570> data<00:07:45.900> confidentiality 00:07:46.490 --> 00:07:46.500 align:start position:0% us nice properties data confidentiality 00:07:46.500 --> 00:07:49.159 align:start position:0% us nice properties data confidentiality data<00:07:47.460> integrity<00:07:48.169> authentication 00:07:49.159 --> 00:07:49.169 align:start position:0% data integrity authentication 00:07:49.169 --> 00:07:52.219 align:start position:0% data integrity authentication non-repudiation<00:07:50.510> but<00:07:51.510> it's<00:07:51.660> kind<00:07:52.050> of 00:07:52.219 --> 00:07:52.229 align:start position:0% non-repudiation but it's kind of 00:07:52.229 --> 00:07:55.790 align:start position:0% non-repudiation but it's kind of complicated<00:07:52.849> if<00:07:53.960> you've<00:07:54.960> ever<00:07:55.200> tried<00:07:55.590> to 00:07:55.790 --> 00:07:55.800 align:start position:0% complicated if you've ever tried to 00:07:55.800 --> 00:07:57.860 align:start position:0% complicated if you've ever tried to develop<00:07:56.220> it<00:07:56.460> on<00:07:56.610> Bitcoin<00:07:57.150> it's<00:07:57.539> not<00:07:57.720> the 00:07:57.860 --> 00:07:57.870 align:start position:0% develop it on Bitcoin it's not the 00:07:57.870 --> 00:08:00.260 align:start position:0% develop it on Bitcoin it's not the easiest<00:07:57.900> platform<00:07:58.680> if<00:07:58.889> you've<00:07:59.610> ever<00:07:59.820> tried<00:08:00.150> to 00:08:00.260 --> 00:08:00.270 align:start position:0% easiest platform if you've ever tried to 00:08:00.270 --> 00:08:02.719 align:start position:0% easiest platform if you've ever tried to extend<00:08:00.750> the<00:08:01.050> idea<00:08:01.410> of<00:08:01.530> value<00:08:01.860> transfer<00:08:02.130> and<00:08:02.580> do 00:08:02.719 --> 00:08:02.729 align:start position:0% extend the idea of value transfer and do 00:08:02.729 --> 00:08:06.950 align:start position:0% extend the idea of value transfer and do multi<00:08:03.510> sig<00:08:03.930> or<00:08:04.410> arbitrary<00:08:04.860> computation<00:08:05.960> maybe 00:08:06.950 --> 00:08:06.960 align:start position:0% multi sig or arbitrary computation maybe 00:08:06.960 --> 00:08:09.200 align:start position:0% multi sig or arbitrary computation maybe you<00:08:07.139> can<00:08:07.289> get<00:08:07.380> away<00:08:07.500> with<00:08:07.800> a<00:08:07.830> few<00:08:08.099> things<00:08:08.250> but 00:08:09.200 --> 00:08:09.210 align:start position:0% you can get away with a few things but 00:08:09.210 --> 00:08:11.600 align:start position:0% you can get away with a few things but really<00:08:09.990> it<00:08:10.080> excels<00:08:10.440> at<00:08:10.590> value<00:08:10.889> transfer<00:08:11.160> and 00:08:11.600 --> 00:08:11.610 align:start position:0% really it excels at value transfer and 00:08:11.610 --> 00:08:15.110 align:start position:0% really it excels at value transfer and storage<00:08:12.650> what<00:08:13.650> we<00:08:13.740> really<00:08:14.190> need<00:08:14.220> for<00:08:14.970> block 00:08:15.110 --> 00:08:15.120 align:start position:0% storage what we really need for block 00:08:15.120 --> 00:08:17.089 align:start position:0% storage what we really need for block chains<00:08:15.330> to<00:08:15.510> take<00:08:15.690> off<00:08:15.930> is<00:08:16.470> for<00:08:16.680> it<00:08:16.740> to<00:08:16.830> be<00:08:16.919> as 00:08:17.089 --> 00:08:17.099 align:start position:0% chains to take off is for it to be as 00:08:17.099 --> 00:08:20.719 align:start position:0% chains to take off is for it to be as easy<00:08:17.610> as<00:08:17.849> web<00:08:18.060> development<00:08:18.630> right<00:08:19.729> javascript 00:08:20.719 --> 00:08:20.729 align:start position:0% easy as web development right javascript 00:08:20.729 --> 00:08:22.670 align:start position:0% easy as web development right javascript almost<00:08:21.300> every<00:08:21.539> developer<00:08:22.020> can<00:08:22.169> program<00:08:22.530> in 00:08:22.670 --> 00:08:22.680 align:start position:0% almost every developer can program in 00:08:22.680 --> 00:08:24.650 align:start position:0% almost every developer can program in java<00:08:22.860> script<00:08:23.039> if<00:08:23.639> we<00:08:23.880> can<00:08:24.060> make<00:08:24.180> block<00:08:24.419> chains 00:08:24.650 --> 00:08:24.660 align:start position:0% java script if we can make block chains 00:08:24.660 --> 00:08:26.900 align:start position:0% java script if we can make block chains as<00:08:24.810> easy<00:08:25.050> as<00:08:25.229> javascript<00:08:25.889> everybody<00:08:26.610> can<00:08:26.789> use 00:08:26.900 --> 00:08:26.910 align:start position:0% as easy as javascript everybody can use 00:08:26.910 --> 00:08:29.839 align:start position:0% as easy as javascript everybody can use block<00:08:27.120> chains<00:08:27.680> in<00:08:28.680> addition<00:08:29.250> to<00:08:29.460> that<00:08:29.669> we've 00:08:29.839 --> 00:08:29.849 align:start position:0% block chains in addition to that we've 00:08:29.849 --> 00:08:32.260 align:start position:0% block chains in addition to that we've got<00:08:30.030> organisations<00:08:30.840> building<00:08:31.740> other<00:08:31.889> tools 00:08:32.260 --> 00:08:32.270 align:start position:0% got organisations building other tools 00:08:32.270 --> 00:08:35.810 align:start position:0% got organisations building other tools services<00:08:33.270> frameworks<00:08:34.020> toolkits<00:08:34.820> consensus 00:08:35.810 --> 00:08:35.820 align:start position:0% services frameworks toolkits consensus 00:08:35.820 --> 00:08:37.959 align:start position:0% services frameworks toolkits consensus is<00:08:36.029> building<00:08:36.360> lots<00:08:36.599> of<00:08:36.779> tools<00:08:36.990> and<00:08:37.110> frameworks 00:08:37.959 --> 00:08:37.969 align:start position:0% is building lots of tools and frameworks 00:08:37.969 --> 00:08:40.850 align:start position:0% is building lots of tools and frameworks we<00:08:38.969> now<00:08:39.120> have<00:08:39.419> athyrium<00:08:40.260> block<00:08:40.500> chain<00:08:40.709> as<00:08:40.830> a 00:08:40.850 --> 00:08:40.860 align:start position:0% we now have athyrium block chain as a 00:08:40.860 --> 00:08:43.190 align:start position:0% we now have athyrium block chain as a service<00:08:41.250> on<00:08:41.430> edger<00:08:41.909> so<00:08:42.510> you<00:08:42.599> don't<00:08:42.959> even<00:08:43.020> have 00:08:43.190 --> 00:08:43.200 align:start position:0% service on edger so you don't even have 00:08:43.200 --> 00:08:45.230 align:start position:0% service on edger so you don't even have to<00:08:43.289> care<00:08:43.620> about<00:08:43.740> setting<00:08:44.159> up<00:08:44.250> you<00:08:44.940> can<00:08:45.089> just 00:08:45.230 --> 00:08:45.240 align:start position:0% to care about setting up you can just 00:08:45.240 --> 00:08:46.950 align:start position:0% to care about setting up you can just spin<00:08:46.079> up<00:08:46.200> a<00:08:46.320> vm<00:08:46.530> in<00:08:46.680> the 00:08:46.950 --> 00:08:46.960 align:start position:0% spin up a vm in the 00:08:46.960 --> 00:08:49.410 align:start position:0% spin up a vm in the loud<00:08:47.130> start<00:08:48.130> playing<00:08:48.370> with<00:08:48.490> it<00:08:48.550> testing<00:08:49.270> it 00:08:49.410 --> 00:08:49.420 align:start position:0% loud start playing with it testing it 00:08:49.420 --> 00:08:50.930 align:start position:0% loud start playing with it testing it figuring<00:08:50.020> out<00:08:50.080> in<00:08:50.230> the<00:08:50.320> ways<00:08:50.500> in<00:08:50.800> which 00:08:50.930 --> 00:08:50.940 align:start position:0% figuring out in the ways in which 00:08:50.940 --> 00:08:56.670 align:start position:0% figuring out in the ways in which athyrium<00:08:51.940> or<00:08:52.120> block<00:08:52.300> chains<00:08:52.600> can<00:08:52.810> help<00:08:52.990> you<00:08:55.680> so 00:08:56.670 --> 00:08:56.680 align:start position:0% athyrium or block chains can help you so 00:08:56.680 --> 00:08:59.610 align:start position:0% athyrium or block chains can help you so the<00:08:57.340> benefits<00:08:57.850> that<00:08:57.970> I<00:08:58.120> would<00:08:58.720> say<00:08:58.840> you<00:08:58.900> want 00:08:59.610 --> 00:08:59.620 align:start position:0% the benefits that I would say you want 00:08:59.620 --> 00:09:01.920 align:start position:0% the benefits that I would say you want to<00:08:59.740> take<00:08:59.920> away<00:09:00.070> with<00:09:00.370> this<00:09:00.540> take<00:09:01.540> back<00:09:01.750> to<00:09:01.870> your 00:09:01.920 --> 00:09:01.930 align:start position:0% to take away with this take back to your 00:09:01.930 --> 00:09:03.660 align:start position:0% to take away with this take back to your organization<00:09:02.560> your<00:09:02.680> IT<00:09:02.830> managers<00:09:03.430> your 00:09:03.660 --> 00:09:03.670 align:start position:0% organization your IT managers your 00:09:03.670 --> 00:09:07.200 align:start position:0% organization your IT managers your executives<00:09:04.380> is<00:09:05.380> that<00:09:05.560> shared<00:09:05.860> code<00:09:06.190> in<00:09:06.520> this 00:09:07.200 --> 00:09:07.210 align:start position:0% executives is that shared code in this 00:09:07.210 --> 00:09:10.560 align:start position:0% executives is that shared code in this distributed<00:09:07.990> EVM<00:09:08.470> means<00:09:09.420> consistent<00:09:10.420> and 00:09:10.560 --> 00:09:10.570 align:start position:0% distributed EVM means consistent and 00:09:10.570 --> 00:09:13.740 align:start position:0% distributed EVM means consistent and predictable<00:09:10.710> execution<00:09:11.710> and<00:09:12.420> append<00:09:13.420> only 00:09:13.740 --> 00:09:13.750 align:start position:0% predictable execution and append only 00:09:13.750 --> 00:09:15.120 align:start position:0% predictable execution and append only database<00:09:14.170> that's<00:09:14.410> cryptographically 00:09:15.120 --> 00:09:15.130 align:start position:0% database that's cryptographically 00:09:15.130 --> 00:09:17.730 align:start position:0% database that's cryptographically verified<00:09:15.880> it<00:09:16.150> cannot<00:09:16.450> be<00:09:16.630> tampered<00:09:16.870> with<00:09:17.110> even 00:09:17.730 --> 00:09:17.740 align:start position:0% verified it cannot be tampered with even 00:09:17.740 --> 00:09:21.240 align:start position:0% verified it cannot be tampered with even by<00:09:17.890> system<00:09:18.370> administrators<00:09:19.440> that's<00:09:20.440> huge<00:09:21.100> for 00:09:21.240 --> 00:09:21.250 align:start position:0% by system administrators that's huge for 00:09:21.250 --> 00:09:24.690 align:start position:0% by system administrators that's huge for regulators<00:09:23.220> anybody<00:09:24.220> that's<00:09:24.460> in<00:09:24.610> the 00:09:24.690 --> 00:09:24.700 align:start position:0% regulators anybody that's in the 00:09:24.700 --> 00:09:29.340 align:start position:0% regulators anybody that's in the business<00:09:24.880> of<00:09:25.120> auditing<00:09:25.800> accounting<00:09:26.940> or<00:09:28.350> going 00:09:29.340 --> 00:09:29.350 align:start position:0% business of auditing accounting or going 00:09:29.350 --> 00:09:32.610 align:start position:0% business of auditing accounting or going to<00:09:29.410> love<00:09:29.560> this<00:09:29.710> and<00:09:30.780> finally<00:09:31.780> automatic<00:09:32.470> and 00:09:32.610 --> 00:09:32.620 align:start position:0% to love this and finally automatic and 00:09:32.620 --> 00:09:34.170 align:start position:0% to love this and finally automatic and low-cost<00:09:32.920> distribution<00:09:33.670> using<00:09:33.820> peer-to-peer 00:09:34.170 --> 00:09:34.180 align:start position:0% low-cost distribution using peer-to-peer 00:09:34.180 --> 00:09:36.660 align:start position:0% low-cost distribution using peer-to-peer technology<00:09:34.800> and<00:09:35.800> this<00:09:35.950> is<00:09:36.100> where<00:09:36.310> the<00:09:36.550> other 00:09:36.660 --> 00:09:36.670 align:start position:0% technology and this is where the other 00:09:36.670 --> 00:09:38.730 align:start position:0% technology and this is where the other components<00:09:37.360> like<00:09:37.630> swarm<00:09:38.110> and<00:09:38.320> whisper<00:09:38.620> will 00:09:38.730 --> 00:09:38.740 align:start position:0% components like swarm and whisper will 00:09:38.740 --> 00:09:42.150 align:start position:0% components like swarm and whisper will come<00:09:38.950> in<00:09:39.210> if<00:09:40.210> you<00:09:40.480> couple<00:09:40.870> a<00:09:41.260> blockchain<00:09:41.800> as<00:09:42.130> a 00:09:42.150 --> 00:09:42.160 align:start position:0% come in if you couple a blockchain as a 00:09:42.160 --> 00:09:43.950 align:start position:0% come in if you couple a blockchain as a coordination<00:09:42.610> mechanism<00:09:43.300> with<00:09:43.570> something 00:09:43.950 --> 00:09:43.960 align:start position:0% coordination mechanism with something 00:09:43.960 --> 00:09:45.480 align:start position:0% coordination mechanism with something like<00:09:44.110> bit<00:09:44.380> torn<00:09:44.620> as<00:09:44.770> a<00:09:44.800> data<00:09:45.070> distribution 00:09:45.480 --> 00:09:45.490 align:start position:0% like bit torn as a data distribution 00:09:45.490 --> 00:09:48.180 align:start position:0% like bit torn as a data distribution mechanism<00:09:46.330> and<00:09:46.510> then<00:09:47.170> use<00:09:47.440> something<00:09:48.160> like 00:09:48.180 --> 00:09:48.190 align:start position:0% mechanism and then use something like 00:09:48.190 --> 00:09:50.910 align:start position:0% mechanism and then use something like tell<00:09:48.550> hash<00:09:48.820> for<00:09:49.270> messaging<00:09:50.170> you<00:09:50.710> have<00:09:50.890> a 00:09:50.910 --> 00:09:50.920 align:start position:0% tell hash for messaging you have a 00:09:50.920 --> 00:09:53.510 align:start position:0% tell hash for messaging you have a really<00:09:51.310> diverse<00:09:51.640> set<00:09:52.060> of<00:09:52.090> tools<00:09:52.450> all 00:09:53.510 --> 00:09:53.520 align:start position:0% really diverse set of tools all 00:09:53.520 --> 00:09:56.000 align:start position:0% really diverse set of tools all interlinked<00:09:54.520> knowing<00:09:55.270> about<00:09:55.390> each<00:09:55.630> other 00:09:56.000 --> 00:09:56.010 align:start position:0% interlinked knowing about each other 00:09:56.010 --> 00:09:58.530 align:start position:0% interlinked knowing about each other cooperating<00:09:57.010> with<00:09:57.100> each<00:09:57.130> other<00:09:57.460> and<00:09:57.760> giving 00:09:58.530 --> 00:09:58.540 align:start position:0% cooperating with each other and giving 00:09:58.540 --> 00:10:01.320 align:start position:0% cooperating with each other and giving you<00:09:58.720> this<00:09:58.900> kind<00:09:59.260> of<00:09:59.470> mesh<00:10:00.220> distributed<00:10:01.150> type 00:10:01.320 --> 00:10:01.330 align:start position:0% you this kind of mesh distributed type 00:10:01.330 --> 00:10:03.900 align:start position:0% you this kind of mesh distributed type network<00:10:01.750> that<00:10:02.320> when<00:10:02.710> an<00:10:02.830> office<00:10:03.160> goes<00:10:03.370> down<00:10:03.640> or 00:10:03.900 --> 00:10:03.910 align:start position:0% network that when an office goes down or 00:10:03.910 --> 00:10:05.670 align:start position:0% network that when an office goes down or you<00:10:04.180> have<00:10:04.450> a<00:10:04.480> mobile<00:10:04.930> client<00:10:05.320> that<00:10:05.440> is<00:10:05.530> only 00:10:05.670 --> 00:10:05.680 align:start position:0% you have a mobile client that is only 00:10:05.680 --> 00:10:08.100 align:start position:0% you have a mobile client that is only partially<00:10:06.160> connected<00:10:06.660> having<00:10:07.660> to<00:10:07.750> deal<00:10:07.930> these 00:10:08.100 --> 00:10:08.110 align:start position:0% partially connected having to deal these 00:10:08.110 --> 00:10:10.260 align:start position:0% partially connected having to deal these kinds<00:10:08.410> of<00:10:08.440> problems<00:10:08.650> goes<00:10:09.010> away<00:10:09.160> you<00:10:10.120> don't 00:10:10.260 --> 00:10:10.270 align:start position:0% kinds of problems goes away you don't 00:10:10.270 --> 00:10:12.120 align:start position:0% kinds of problems goes away you don't have<00:10:10.420> to<00:10:10.570> set<00:10:10.750> up<00:10:10.840> database<00:10:11.200> replication<00:10:11.410> it's 00:10:12.120 --> 00:10:12.130 align:start position:0% have to set up database replication it's 00:10:12.130 --> 00:10:15.810 align:start position:0% have to set up database replication it's given<00:10:12.460> to<00:10:12.580> you<00:10:12.670> for<00:10:12.880> free<00:10:14.460> so<00:10:15.460> these<00:10:15.610> are<00:10:15.670> the 00:10:15.810 --> 00:10:15.820 align:start position:0% given to you for free so these are the 00:10:15.820 --> 00:10:18.500 align:start position:0% given to you for free so these are the reasons<00:10:16.210> that<00:10:16.300> I<00:10:16.390> think<00:10:16.660> etherium<00:10:17.230> really 00:10:18.500 --> 00:10:18.510 align:start position:0% reasons that I think etherium really 00:10:18.510 --> 00:10:20.670 align:start position:0% reasons that I think etherium really beneficial<00:10:19.510> for<00:10:20.230> the<00:10:20.470> enterprise 00:10:20.670 --> 00:10:20.680 align:start position:0% beneficial for the enterprise 00:10:20.680 --> 00:10:24.360 align:start position:0% beneficial for the enterprise environment<00:10:21.400> and<00:10:21.520> why<00:10:22.860> you<00:10:23.860> should<00:10:24.040> want<00:10:24.220> to 00:10:24.360 --> 00:10:24.370 align:start position:0% environment and why you should want to 00:10:24.370 --> 00:10:26.610 align:start position:0% environment and why you should want to investigate<00:10:25.000> this<00:10:25.330> not<00:10:25.780> because<00:10:25.960> blockchains 00:10:26.610 --> 00:10:26.620 align:start position:0% investigate this not because blockchains 00:10:26.620 --> 00:10:30.060 align:start position:0% investigate this not because blockchains just<00:10:27.400> can<00:10:27.550> remove<00:10:27.760> trust<00:10:28.410> or<00:10:29.410> can<00:10:29.830> remove 00:10:30.060 --> 00:10:30.070 align:start position:0% just can remove trust or can remove 00:10:30.070 --> 00:10:31.860 align:start position:0% just can remove trust or can remove intermediaries<00:10:30.790> yes<00:10:31.090> they<00:10:31.300> can<00:10:31.360> do<00:10:31.690> those 00:10:31.860 --> 00:10:31.870 align:start position:0% intermediaries yes they can do those 00:10:31.870 --> 00:10:33.540 align:start position:0% intermediaries yes they can do those things<00:10:32.140> but<00:10:32.350> is<00:10:32.770> in<00:10:32.860> a<00:10:32.950> general<00:10:33.280> sense<00:10:33.400> of 00:10:33.540 --> 00:10:33.550 align:start position:0% things but is in a general sense of 00:10:33.550 --> 00:10:36.150 align:start position:0% things but is in a general sense of coordination<00:10:34.030> mechanism<00:10:34.660> and<00:10:35.590> having<00:10:35.980> these 00:10:36.150 --> 00:10:36.160 align:start position:0% coordination mechanism and having these 00:10:36.160 --> 00:10:38.400 align:start position:0% coordination mechanism and having these this<00:10:36.490> code<00:10:36.760> and<00:10:37.030> data<00:10:37.120> coupled<00:10:37.540> together<00:10:37.660> is<00:10:38.020> a 00:10:38.400 --> 00:10:38.410 align:start position:0% this code and data coupled together is a 00:10:38.410 --> 00:10:41.400 align:start position:0% this code and data coupled together is a really<00:10:38.830> powerful<00:10:39.010> idea<00:10:39.960> I've<00:10:40.960> talked<00:10:41.230> to<00:10:41.380> a 00:10:41.400 --> 00:10:41.410 align:start position:0% really powerful idea I've talked to a 00:10:41.410 --> 00:10:44.100 align:start position:0% really powerful idea I've talked to a few<00:10:41.950> of<00:10:42.100> you<00:10:42.250> throughout<00:10:43.180> the<00:10:43.300> week<00:10:43.450> I've<00:10:43.990> been 00:10:44.100 --> 00:10:44.110 align:start position:0% few of you throughout the week I've been 00:10:44.110 --> 00:10:45.450 align:start position:0% few of you throughout the week I've been working<00:10:44.410> on<00:10:44.470> a<00:10:44.530> project<00:10:44.800> in<00:10:45.040> my<00:10:45.130> spare<00:10:45.430> time 00:10:45.450 --> 00:10:45.460 align:start position:0% working on a project in my spare time 00:10:45.460 --> 00:10:48.450 align:start position:0% working on a project in my spare time it's<00:10:46.230> got<00:10:47.230> this<00:10:47.320> really<00:10:47.560> awful<00:10:47.830> name<00:10:48.220> but 00:10:48.450 --> 00:10:48.460 align:start position:0% it's got this really awful name but 00:10:48.460 --> 00:10:50.220 align:start position:0% it's got this really awful name but essentially<00:10:48.730> it's<00:10:48.970> a<00:10:49.090> DAP<00:10:49.360> generator<00:10:49.990> if 00:10:50.220 --> 00:10:50.230 align:start position:0% essentially it's a DAP generator if 00:10:50.230 --> 00:10:53.510 align:start position:0% essentially it's a DAP generator if you've<00:10:50.920> started<00:10:51.430> working<00:10:51.820> on<00:10:51.990> adapt<00:10:52.990> at<00:10:53.140> all 00:10:53.510 --> 00:10:53.520 align:start position:0% you've started working on adapt at all 00:10:53.520 --> 00:10:56.160 align:start position:0% you've started working on adapt at all you'll<00:10:54.520> know<00:10:54.700> that<00:10:54.730> you<00:10:55.420> have<00:10:55.570> to<00:10:55.660> write<00:10:55.990> some 00:10:56.160 --> 00:10:56.170 align:start position:0% you'll know that you have to write some 00:10:56.170 --> 00:10:59.040 align:start position:0% you'll know that you have to write some JavaScript<00:10:56.860> put<00:10:57.370> some<00:10:57.580> HTML<00:10:58.030> and<00:10:58.300> elements<00:10:58.960> in 00:10:59.040 --> 00:10:59.050 align:start position:0% JavaScript put some HTML and elements in 00:10:59.050 --> 00:11:00.690 align:start position:0% JavaScript put some HTML and elements in front<00:10:59.230> of<00:10:59.290> it<00:10:59.380> to<00:10:59.470> give<00:10:59.620> it<00:10:59.710> a<00:10:59.800> UI 00:11:00.690 --> 00:11:00.700 align:start position:0% front of it to give it a UI 00:11:00.700 --> 00:11:03.810 align:start position:0% front of it to give it a UI I<00:11:01.390> found<00:11:01.960> that<00:11:02.110> a<00:11:02.170> bit<00:11:02.320> annoying<00:11:02.680> and<00:11:03.070> I<00:11:03.580> tend 00:11:03.810 --> 00:11:03.820 align:start position:0% I found that a bit annoying and I tend 00:11:03.820 --> 00:11:06.120 align:start position:0% I found that a bit annoying and I tend to<00:11:03.880> find<00:11:04.000> myself<00:11:04.210> as<00:11:04.720> a<00:11:04.780> general<00:11:05.740> programmer 00:11:06.120 --> 00:11:06.130 align:start position:0% to find myself as a general programmer 00:11:06.130 --> 00:11:08.940 align:start position:0% to find myself as a general programmer does<00:11:06.790> you<00:11:07.450> know<00:11:07.570> abstracting<00:11:08.320> making<00:11:08.740> things 00:11:08.940 --> 00:11:08.950 align:start position:0% does you know abstracting making things 00:11:08.950 --> 00:11:11.700 align:start position:0% does you know abstracting making things more<00:11:09.100> generic<00:11:09.520> so<00:11:10.090> I<00:11:10.120> wrote<00:11:10.420> an<00:11:10.630> interface<00:11:11.260> to 00:11:11.700 --> 00:11:11.710 align:start position:0% more generic so I wrote an interface to 00:11:11.710 --> 00:11:14.700 align:start position:0% more generic so I wrote an interface to generate<00:11:12.370> interfaces<00:11:13.030> basically<00:11:13.660> you<00:11:14.530> can 00:11:14.700 --> 00:11:14.710 align:start position:0% generate interfaces basically you can 00:11:14.710 --> 00:11:16.950 align:start position:0% generate interfaces basically you can just<00:11:14.920> give<00:11:15.100> it<00:11:15.250> the<00:11:15.430> ABI<00:11:15.850> generated<00:11:16.720> from<00:11:16.810> the 00:11:16.950 --> 00:11:16.960 align:start position:0% just give it the ABI generated from the 00:11:16.960 --> 00:11:19.080 align:start position:0% just give it the ABI generated from the contract<00:11:17.410> and<00:11:17.590> it<00:11:18.190> will<00:11:18.370> give<00:11:18.550> you<00:11:18.730> a<00:11:18.760> free 00:11:19.080 --> 00:11:19.090 align:start position:0% contract and it will give you a free 00:11:19.090 --> 00:11:20.760 align:start position:0% contract and it will give you a free HTML<00:11:19.480> interface<00:11:19.810> which<00:11:20.200> you<00:11:20.320> can<00:11:20.440> just<00:11:20.590> tweak 00:11:20.760 --> 00:11:20.770 align:start position:0% HTML interface which you can just tweak 00:11:20.770 --> 00:11:22.800 align:start position:0% HTML interface which you can just tweak with<00:11:20.950> some<00:11:21.130> CSS<00:11:21.610> you<00:11:22.240> don't<00:11:22.390> have<00:11:22.510> to<00:11:22.600> tell 00:11:22.800 --> 00:11:22.810 align:start position:0% with some CSS you don't have to tell 00:11:22.810 --> 00:11:25.080 align:start position:0% with some CSS you don't have to tell anything<00:11:23.140> about<00:11:23.350> the<00:11:23.680> contract<00:11:24.190> just<00:11:24.730> figures 00:11:25.080 --> 00:11:25.090 align:start position:0% anything about the contract just figures 00:11:25.090 --> 00:11:27.240 align:start position:0% anything about the contract just figures it<00:11:25.240> out<00:11:25.360> it<00:11:25.900> knows<00:11:26.140> what<00:11:26.320> events<00:11:26.650> to<00:11:26.770> watch<00:11:26.920> for 00:11:27.240 --> 00:11:27.250 align:start position:0% it out it knows what events to watch for 00:11:27.250 --> 00:11:29.610 align:start position:0% it out it knows what events to watch for its<00:11:27.880> really<00:11:28.150> really<00:11:28.270> nice<00:11:28.510> so<00:11:29.290> I<00:11:29.350> think<00:11:29.530> as 00:11:29.610 --> 00:11:29.620 align:start position:0% its really really nice so I think as 00:11:29.620 --> 00:11:32.310 align:start position:0% its really really nice so I think as tools<00:11:30.400> like<00:11:30.730> this<00:11:31.000> or<00:11:31.180> built<00:11:31.390> up<00:11:31.570> we<00:11:32.140> can 00:11:32.310 --> 00:11:32.320 align:start position:0% tools like this or built up we can 00:11:32.320 --> 00:11:35.630 align:start position:0% tools like this or built up we can really<00:11:32.590> see<00:11:33.000> more<00:11:34.000> proliferation<00:11:34.750> of<00:11:34.810> this<00:11:34.990> I 00:11:35.630 --> 00:11:35.640 align:start position:0% really see more proliferation of this I 00:11:35.640 --> 00:11:37.890 align:start position:0% really see more proliferation of this I tried<00:11:36.640> to<00:11:36.730> record<00:11:36.940> this<00:11:37.090> as<00:11:37.270> a<00:11:37.300> movie<00:11:37.570> to<00:11:37.690> save 00:11:37.890 --> 00:11:37.900 align:start position:0% tried to record this as a movie to save 00:11:37.900 --> 00:11:39.210 align:start position:0% tried to record this as a movie to save me<00:11:38.140> the<00:11:38.260> headache<00:11:38.410> of<00:11:38.650> having<00:11:38.710> to<00:11:38.980> do<00:11:39.070> this 00:11:39.210 --> 00:11:39.220 align:start position:0% me the headache of having to do this 00:11:39.220 --> 00:11:43.170 align:start position:0% me the headache of having to do this live<00:11:39.460> but<00:11:40.270> my<00:11:40.930> tools<00:11:41.260> refuse<00:11:42.070> to<00:11:42.370> like<00:11:42.520> export 00:11:43.170 --> 00:11:43.180 align:start position:0% live but my tools refuse to like export 00:11:43.180 --> 00:11:45.390 align:start position:0% live but my tools refuse to like export and<00:11:43.450> put<00:11:44.230> it<00:11:44.350> in<00:11:44.440> the<00:11:44.500> presentation<00:11:44.920> so<00:11:45.310> I'm 00:11:45.390 --> 00:11:45.400 align:start position:0% and put it in the presentation so I'm 00:11:45.400 --> 00:11:47.010 align:start position:0% and put it in the presentation so I'm going<00:11:45.640> to<00:11:45.700> try<00:11:45.880> to<00:11:45.910> do<00:11:46.090> it<00:11:46.210> live<00:11:46.390> here<00:11:46.660> locally 00:11:47.010 --> 00:11:47.020 align:start position:0% going to try to do it live here locally 00:11:47.020 --> 00:11:51.180 align:start position:0% going to try to do it live here locally just<00:11:47.200> to<00:11:47.320> kind<00:11:47.530> of<00:11:47.620> show<00:11:47.800> you<00:11:47.830> the<00:11:48.070> idea<00:11:50.190> I'm 00:11:51.180 --> 00:11:51.190 align:start position:0% just to kind of show you the idea I'm 00:11:51.190 --> 00:11:53.340 align:start position:0% just to kind of show you the idea I'm running<00:11:52.030> this<00:11:52.180> on<00:11:52.420> my<00:11:52.600> local<00:11:52.870> machine<00:11:52.900> so 00:11:53.340 --> 00:11:53.350 align:start position:0% running this on my local machine so 00:11:53.350 --> 00:11:54.540 align:start position:0% running this on my local machine so hopefully<00:11:53.620> I<00:11:53.650> won't<00:11:53.770> have<00:11:53.890> too<00:11:54.070> many<00:11:54.160> network 00:11:54.540 --> 00:11:54.550 align:start position:0% hopefully I won't have too many network 00:11:54.550 --> 00:12:02.730 align:start position:0% hopefully I won't have too many network problems<00:11:55.080> but<00:11:56.080> we'll<00:11:56.230> see<00:11:59.010> so<00:12:00.010> right<00:12:01.740> just 00:12:02.730 --> 00:12:02.740 align:start position:0% problems but we'll see so right just 00:12:02.740 --> 00:12:05.070 align:start position:0% problems but we'll see so right just going<00:12:02.890> to<00:12:02.950> start<00:12:03.130> my<00:12:03.280> minor<00:12:03.690> so<00:12:04.690> I've<00:12:05.050> just 00:12:05.070 --> 00:12:05.080 align:start position:0% going to start my minor so I've just 00:12:05.080 --> 00:12:08.880 align:start position:0% going to start my minor so I've just loaded<00:12:05.650> a<00:12:05.680> page<00:12:06.250> here<00:12:06.780> it's<00:12:07.780> connected<00:12:08.230> to<00:12:08.260> our 00:12:08.880 --> 00:12:08.890 align:start position:0% loaded a page here it's connected to our 00:12:08.890 --> 00:12:10.920 align:start position:0% loaded a page here it's connected to our guests<00:12:09.100> instance<00:12:09.550> we're<00:12:10.300> watching<00:12:10.660> for<00:12:10.690> new 00:12:10.920 --> 00:12:10.930 align:start position:0% guests instance we're watching for new 00:12:10.930 --> 00:12:13.230 align:start position:0% guests instance we're watching for new incoming<00:12:11.290> blocks<00:12:11.650> and<00:12:12.460> when<00:12:12.640> blocks<00:12:12.880> our<00:12:13.030> mind 00:12:13.230 --> 00:12:13.240 align:start position:0% incoming blocks and when blocks our mind 00:12:13.240 --> 00:12:15.270 align:start position:0% incoming blocks and when blocks our mind we<00:12:13.420> should<00:12:13.600> see<00:12:13.810> a<00:12:14.230> little<00:12:14.590> update<00:12:14.860> here<00:12:15.220> at 00:12:15.270 --> 00:12:15.280 align:start position:0% we should see a little update here at 00:12:15.280 --> 00:12:17.700 align:start position:0% we should see a little update here at the<00:12:15.370> top<00:12:15.550> here<00:12:16.510> we<00:12:16.690> have<00:12:16.810> our<00:12:16.840> contract<00:12:17.470> this 00:12:17.700 --> 00:12:17.710 align:start position:0% the top here we have our contract this 00:12:17.710 --> 00:12:22.440 align:start position:0% the top here we have our contract this is<00:12:17.860> just<00:12:18.070> a<00:12:18.160> wallet<00:12:18.730> written<00:12:19.060> in<00:12:19.120> solidity<00:12:21.450> we 00:12:22.440 --> 00:12:22.450 align:start position:0% is just a wallet written in solidity we 00:12:22.450 --> 00:12:25.140 align:start position:0% is just a wallet written in solidity we can<00:12:22.600> compile<00:12:22.960> this<00:12:23.200> it<00:12:24.190> gives<00:12:24.400> us<00:12:24.580> this<00:12:24.760> ABI 00:12:25.140 --> 00:12:25.150 align:start position:0% can compile this it gives us this ABI 00:12:25.150 --> 00:12:28.380 align:start position:0% can compile this it gives us this ABI here<00:12:25.510> and<00:12:25.660> from<00:12:26.410> this<00:12:26.530> ABI<00:12:26.920> we<00:12:27.790> get<00:12:28.030> this<00:12:28.180> kind 00:12:28.380 --> 00:12:28.390 align:start position:0% here and from this ABI we get this kind 00:12:28.390 --> 00:12:31.020 align:start position:0% here and from this ABI we get this kind of<00:12:28.450> free<00:12:28.690> interface<00:12:29.110> down<00:12:29.380> here<00:12:29.680> I've<00:12:30.670> made<00:12:30.940> it 00:12:31.020 --> 00:12:31.030 align:start position:0% of free interface down here I've made it 00:12:31.030 --> 00:12:32.550 align:start position:0% of free interface down here I've made it looked<00:12:31.210> like<00:12:31.300> this<00:12:31.450> tab<00:12:31.840> kind<00:12:32.170> of<00:12:32.230> interface 00:12:32.550 --> 00:12:32.560 align:start position:0% looked like this tab kind of interface 00:12:32.560 --> 00:12:35.760 align:start position:0% looked like this tab kind of interface but<00:12:32.980> really<00:12:33.550> this<00:12:33.880> is<00:12:34.060> just<00:12:34.090> CSS<00:12:34.680> making<00:12:35.680> it 00:12:35.760 --> 00:12:35.770 align:start position:0% but really this is just CSS making it 00:12:35.770 --> 00:12:37.380 align:start position:0% but really this is just CSS making it look<00:12:35.890> like<00:12:35.920> that<00:12:36.190> you<00:12:36.340> can<00:12:36.460> do<00:12:37.060> anything<00:12:37.270> you 00:12:37.380 --> 00:12:37.390 align:start position:0% look like that you can do anything you 00:12:37.390 --> 00:12:40.110 align:start position:0% look like that you can do anything you want<00:12:37.630> to<00:12:37.720> it<00:12:38.280> this<00:12:39.280> is<00:12:39.400> all<00:12:39.550> for<00:12:39.670> free<00:12:39.820> I<00:12:39.910> didn't 00:12:40.110 --> 00:12:40.120 align:start position:0% want to it this is all for free I didn't 00:12:40.120 --> 00:12:42.900 align:start position:0% want to it this is all for free I didn't have<00:12:40.240> to<00:12:40.330> write<00:12:40.480> any<00:12:40.630> of<00:12:40.690> this<00:12:40.780> custom<00:12:41.910> it's 00:12:42.900 --> 00:12:42.910 align:start position:0% have to write any of this custom it's 00:12:42.910 --> 00:12:44.610 align:start position:0% have to write any of this custom it's really<00:12:43.120> nice<00:12:43.300> i<00:12:43.510> can<00:12:43.630> deploy<00:12:43.870> a<00:12:43.900> contract 00:12:44.610 --> 00:12:44.620 align:start position:0% really nice i can deploy a contract 00:12:44.620 --> 00:12:48.420 align:start position:0% really nice i can deploy a contract let's<00:12:44.890> see<00:12:45.040> if<00:12:45.160> i<00:12:45.220> can<00:12:45.400> do<00:12:45.880> that<00:12:46.030> now<00:12:46.710> ok<00:12:47.710> so 00:12:48.420 --> 00:12:48.430 align:start position:0% let's see if i can do that now ok so 00:12:48.430 --> 00:12:50.850 align:start position:0% let's see if i can do that now ok so I've<00:12:48.700> deployed<00:12:48.940> the<00:12:49.150> contract<00:12:49.660> I'm<00:12:50.530> going<00:12:50.800> to 00:12:50.850 --> 00:12:50.860 align:start position:0% I've deployed the contract I'm going to 00:12:50.860 --> 00:12:53.730 align:start position:0% I've deployed the contract I'm going to wait<00:12:51.100> for<00:12:51.310> it<00:12:51.340> to<00:12:51.430> mine<00:12:51.730> here<00:12:52.060> there<00:12:52.540> we<00:12:52.630> go<00:12:52.780> so 00:12:53.730 --> 00:12:53.740 align:start position:0% wait for it to mine here there we go so 00:12:53.740 --> 00:12:56.910 align:start position:0% wait for it to mine here there we go so it's<00:12:54.280> been<00:12:54.400> mocked<00:12:54.640> mind<00:12:55.090> and<00:12:55.270> blocked<00:12:55.620> 7226<00:12:56.620> I 00:12:56.910 --> 00:12:56.920 align:start position:0% it's been mocked mind and blocked 7226 I 00:12:56.920 --> 00:12:58.440 align:start position:0% it's been mocked mind and blocked 7226 I have<00:12:57.130> the<00:12:57.250> address<00:12:57.340> there<00:12:57.790> which<00:12:58.000> I<00:12:58.090> can<00:12:58.240> see 00:12:58.440 --> 00:12:58.450 align:start position:0% have the address there which I can see 00:12:58.450 --> 00:13:01.830 align:start position:0% have the address there which I can see has<00:12:58.690> been<00:12:58.990> set<00:12:59.920> in<00:13:00.040> the<00:13:00.190> to<00:13:00.460> field<00:13:00.490> here<00:13:01.090> making 00:13:01.830 --> 00:13:01.840 align:start position:0% has been set in the to field here making 00:13:01.840 --> 00:13:04.010 align:start position:0% has been set in the to field here making it<00:13:01.930> convenient<00:13:02.290> for<00:13:02.440> me<00:13:02.620> to<00:13:02.650> interact<00:13:02.980> with<00:13:03.310> it 00:13:04.010 --> 00:13:04.020 align:start position:0% it convenient for me to interact with it 00:13:04.020 --> 00:13:07.150 align:start position:0% it convenient for me to interact with it let<00:13:05.020> me<00:13:05.050> just<00:13:05.380> grab<00:13:05.620> my 00:13:07.150 --> 00:13:07.160 align:start position:0% let me just grab my 00:13:07.160 --> 00:13:09.470 align:start position:0% let me just grab my address<00:13:08.160> here<00:13:08.430> I<00:13:08.460> want<00:13:08.700> to<00:13:08.760> check<00:13:09.210> and<00:13:09.420> verify 00:13:09.470 --> 00:13:09.480 align:start position:0% address here I want to check and verify 00:13:09.480 --> 00:13:13.270 align:start position:0% address here I want to check and verify that<00:13:09.990> i'm<00:13:10.080> actually<00:13:10.260> the<00:13:10.770> owner<00:13:10.920> of<00:13:11.070> this<00:13:11.360> so 00:13:13.270 --> 00:13:13.280 align:start position:0% that i'm actually the owner of this so 00:13:13.280 --> 00:13:16.520 align:start position:0% that i'm actually the owner of this so go<00:13:14.280> down<00:13:14.400> to<00:13:14.550> his<00:13:14.670> owner<00:13:14.910> paste<00:13:15.840> in<00:13:16.020> my<00:13:16.170> address 00:13:16.520 --> 00:13:16.530 align:start position:0% go down to his owner paste in my address 00:13:16.530 --> 00:13:18.350 align:start position:0% go down to his owner paste in my address you<00:13:16.920> can<00:13:17.040> see<00:13:17.250> it's<00:13:17.370> pulling<00:13:17.970> the<00:13:18.060> fields 00:13:18.350 --> 00:13:18.360 align:start position:0% you can see it's pulling the fields 00:13:18.360 --> 00:13:20.800 align:start position:0% you can see it's pulling the fields together<00:13:18.510> from<00:13:18.960> the<00:13:19.200> actual<00:13:19.560> contract<00:13:20.280> fields 00:13:20.800 --> 00:13:20.810 align:start position:0% together from the actual contract fields 00:13:20.810 --> 00:13:28.070 align:start position:0% together from the actual contract fields hit<00:13:21.810> call<00:13:22.050> turns<00:13:22.770> true<00:13:23.070> nice<00:13:24.920> can<00:13:26.930> check<00:13:27.930> our 00:13:28.070 --> 00:13:28.080 align:start position:0% hit call turns true nice can check our 00:13:28.080 --> 00:13:31.310 align:start position:0% hit call turns true nice can check our daily<00:13:28.230> limit<00:13:29.000> so<00:13:30.000> for<00:13:30.360> multi<00:13:30.630> sig<00:13:30.870> we<00:13:31.020> have<00:13:31.170> no 00:13:31.310 --> 00:13:31.320 align:start position:0% daily limit so for multi sig we have no 00:13:31.320 --> 00:13:32.690 align:start position:0% daily limit so for multi sig we have no limit<00:13:31.590> we<00:13:31.830> want<00:13:32.010> to<00:13:32.100> kind<00:13:32.190> of<00:13:32.310> raise<00:13:32.490> that<00:13:32.640> a 00:13:32.690 --> 00:13:32.700 align:start position:0% limit we want to kind of raise that a 00:13:32.700 --> 00:13:39.650 align:start position:0% limit we want to kind of raise that a little<00:13:32.970> bit<00:13:33.380> so<00:13:34.380> come<00:13:35.340> down<00:13:35.520> here<00:13:37.940> set<00:13:38.940> it<00:13:39.060> send 00:13:39.650 --> 00:13:39.660 align:start position:0% little bit so come down here set it send 00:13:39.660 --> 00:13:42.620 align:start position:0% little bit so come down here set it send the<00:13:39.720> transaction<00:13:40.940> wait<00:13:41.940> for<00:13:42.150> a<00:13:42.180> block<00:13:42.390> to<00:13:42.420> be 00:13:42.620 --> 00:13:42.630 align:start position:0% the transaction wait for a block to be 00:13:42.630 --> 00:13:51.080 align:start position:0% the transaction wait for a block to be mined<00:13:44.570> or<00:13:45.570> two<00:13:49.280> there<00:13:50.280> we<00:13:50.400> go<00:13:50.550> we<00:13:50.970> have<00:13:51.060> a 00:13:51.080 --> 00:13:51.090 align:start position:0% mined or two there we go we have a 00:13:51.090 --> 00:13:54.350 align:start position:0% mined or two there we go we have a confirmation<00:13:52.340> really<00:13:53.340> nice<00:13:53.460> we<00:13:53.940> can<00:13:54.090> go<00:13:54.180> back 00:13:54.350 --> 00:13:54.360 align:start position:0% confirmation really nice we can go back 00:13:54.360 --> 00:13:56.450 align:start position:0% confirmation really nice we can go back to<00:13:54.420> check<00:13:54.960> the<00:13:55.080> daily<00:13:55.260> limit<00:13:55.620> hit<00:13:56.220> call 00:13:56.450 --> 00:13:56.460 align:start position:0% to check the daily limit hit call 00:13:56.460 --> 00:14:00.920 align:start position:0% to check the daily limit hit call returns<00:13:57.090> 100<00:13:57.540> as<00:13:57.630> we'd<00:13:57.840> expect<00:13:59.690> it's<00:14:00.690> really 00:14:00.920 --> 00:14:00.930 align:start position:0% returns 100 as we'd expect it's really 00:14:00.930 --> 00:14:03.200 align:start position:0% returns 100 as we'd expect it's really neat<00:14:01.080> I<00:14:01.350> can<00:14:01.770> even<00:14:01.860> go<00:14:02.190> into<00:14:02.370> the<00:14:02.580> logs<00:14:02.820> and 00:14:03.200 --> 00:14:03.210 align:start position:0% neat I can even go into the logs and 00:14:03.210 --> 00:14:05.720 align:start position:0% neat I can even go into the logs and check<00:14:04.050> for<00:14:04.200> my<00:14:04.290> confirmation<00:14:04.620> so<00:14:05.340> I<00:14:05.370> see<00:14:05.640> it 00:14:05.720 --> 00:14:05.730 align:start position:0% check for my confirmation so I see it 00:14:05.730 --> 00:14:08.690 align:start position:0% check for my confirmation so I see it was<00:14:05.850> in<00:14:06.000> some<00:14:06.180> block<00:14:06.480> 7<00:14:06.780> 2<00:14:06.900> 3<00:14:07.170> 4<00:14:07.470> get<00:14:08.460> logs 00:14:08.690 --> 00:14:08.700 align:start position:0% was in some block 7 2 3 4 get logs 00:14:08.700 --> 00:14:11.090 align:start position:0% was in some block 7 2 3 4 get logs there's<00:14:09.600> my<00:14:09.810> confirmation<00:14:10.140> information<00:14:10.920> what 00:14:11.090 --> 00:14:11.100 align:start position:0% there's my confirmation information what 00:14:11.100 --> 00:14:13.460 align:start position:0% there's my confirmation information what transaction<00:14:11.730> where<00:14:12.270> exactly<00:14:12.570> in<00:14:12.870> chain<00:14:13.320> it 00:14:13.460 --> 00:14:13.470 align:start position:0% transaction where exactly in chain it 00:14:13.470 --> 00:14:15.410 align:start position:0% transaction where exactly in chain it occurred<00:14:13.770> the<00:14:14.010> block<00:14:14.220> hi<00:14:14.460> the<00:14:14.820> transaction 00:14:15.410 --> 00:14:15.420 align:start position:0% occurred the block hi the transaction 00:14:15.420 --> 00:14:18.200 align:start position:0% occurred the block hi the transaction index<00:14:15.750> and<00:14:16.070> you<00:14:17.070> know<00:14:17.160> log<00:14:17.430> index<00:14:17.760> the<00:14:18.000> gas 00:14:18.200 --> 00:14:18.210 align:start position:0% index and you know log index the gas 00:14:18.210 --> 00:14:20.810 align:start position:0% index and you know log index the gas used<00:14:18.600> and<00:14:18.930> this<00:14:19.770> particular<00:14:20.100> fields<00:14:20.550> on<00:14:20.640> this 00:14:20.810 --> 00:14:20.820 align:start position:0% used and this particular fields on this 00:14:20.820 --> 00:14:23.900 align:start position:0% used and this particular fields on this now<00:14:21.600> I<00:14:21.990> haven't<00:14:22.560> done<00:14:22.710> anything<00:14:22.770> to<00:14:23.400> tell<00:14:23.760> it 00:14:23.900 --> 00:14:23.910 align:start position:0% now I haven't done anything to tell it 00:14:23.910 --> 00:14:25.760 align:start position:0% now I haven't done anything to tell it about<00:14:24.150> these<00:14:24.360> contract<00:14:24.960> or<00:14:25.170> the<00:14:25.260> functions<00:14:25.650> or 00:14:25.760 --> 00:14:25.770 align:start position:0% about these contract or the functions or 00:14:25.770 --> 00:14:27.740 align:start position:0% about these contract or the functions or methods<00:14:25.800> it's<00:14:26.700> been<00:14:26.910> all<00:14:27.120> automatically 00:14:27.740 --> 00:14:27.750 align:start position:0% methods it's been all automatically 00:14:27.750 --> 00:14:29.630 align:start position:0% methods it's been all automatically generated<00:14:28.260> from<00:14:28.320> this<00:14:28.470> ABI<00:14:28.830> and<00:14:29.400> this<00:14:29.520> is 00:14:29.630 --> 00:14:29.640 align:start position:0% generated from this ABI and this is 00:14:29.640 --> 00:14:31.250 align:start position:0% generated from this ABI and this is really<00:14:29.910> where<00:14:30.150> this<00:14:30.300> value<00:14:30.690> comes<00:14:30.930> in<00:14:31.110> of 00:14:31.250 --> 00:14:31.260 align:start position:0% really where this value comes in of 00:14:31.260 --> 00:14:33.500 align:start position:0% really where this value comes in of having<00:14:31.530> code<00:14:31.800> as<00:14:32.010> data<00:14:32.340> having<00:14:32.940> it<00:14:33.030> in<00:14:33.210> the 00:14:33.500 --> 00:14:33.510 align:start position:0% having code as data having it in the 00:14:33.510 --> 00:14:36.590 align:start position:0% having code as data having it in the shared<00:14:33.780> location<00:14:34.380> right<00:14:34.560> we<00:14:35.300> have<00:14:36.300> it<00:14:36.420> in<00:14:36.510> this 00:14:36.590 --> 00:14:36.600 align:start position:0% shared location right we have it in this 00:14:36.600 --> 00:14:38.720 align:start position:0% shared location right we have it in this one<00:14:36.840> spot<00:14:36.870> we<00:14:37.740> are<00:14:37.830> given<00:14:38.100> an<00:14:38.190> interface<00:14:38.550> on 00:14:38.720 --> 00:14:38.730 align:start position:0% one spot we are given an interface on 00:14:38.730 --> 00:14:40.700 align:start position:0% one spot we are given an interface on how<00:14:38.850> to<00:14:38.910> interact<00:14:39.210> with<00:14:39.450> it<00:14:39.690> and<00:14:39.870> no<00:14:40.590> matter 00:14:40.700 --> 00:14:40.710 align:start position:0% how to interact with it and no matter 00:14:40.710 --> 00:14:42.110 align:start position:0% how to interact with it and no matter who<00:14:40.920> you<00:14:40.980> are<00:14:41.070> where<00:14:41.430> you<00:14:41.610> are<00:14:41.640> you<00:14:42.090> can 00:14:42.110 --> 00:14:42.120 align:start position:0% who you are where you are you can 00:14:42.120 --> 00:14:44.270 align:start position:0% who you are where you are you can interact<00:14:42.720> with<00:14:42.870> it<00:14:42.960> in<00:14:43.050> the<00:14:43.110> same<00:14:43.350> way<00:14:43.560> if<00:14:43.800> you 00:14:44.270 --> 00:14:44.280 align:start position:0% interact with it in the same way if you 00:14:44.280 --> 00:14:45.860 align:start position:0% interact with it in the same way if you were<00:14:44.370> to<00:14:44.490> run<00:14:44.610> this<00:14:44.730> here<00:14:45.000> on<00:14:45.150> your<00:14:45.660> machine 00:14:45.860 --> 00:14:45.870 align:start position:0% were to run this here on your machine 00:14:45.870 --> 00:14:47.710 align:start position:0% were to run this here on your machine you'll<00:14:46.230> get<00:14:46.380> the<00:14:46.470> same<00:14:46.620> exact<00:14:46.950> results<00:14:47.370> I 00:14:47.710 --> 00:14:47.720 align:start position:0% you'll get the same exact results I 00:14:47.720 --> 00:14:50.210 align:start position:0% you'll get the same exact results I think<00:14:48.720> as<00:14:48.810> we<00:14:48.960> push<00:14:49.500> forward<00:14:49.830> these<00:14:49.920> kind<00:14:50.160> of 00:14:50.210 --> 00:14:50.220 align:start position:0% think as we push forward these kind of 00:14:50.220 --> 00:14:51.680 align:start position:0% think as we push forward these kind of tools<00:14:50.370> more<00:14:50.700> and<00:14:50.820> more<00:14:51.000> we'll<00:14:51.240> see<00:14:51.450> more 00:14:51.680 --> 00:14:51.690 align:start position:0% tools more and more we'll see more 00:14:51.690 --> 00:14:53.300 align:start position:0% tools more and more we'll see more adoption<00:14:52.140> of<00:14:52.200> this<00:14:52.320> in<00:14:52.470> the<00:14:52.590> enterprise<00:14:52.980> and 00:14:53.300 --> 00:14:53.310 align:start position:0% adoption of this in the enterprise and 00:14:53.310 --> 00:14:55.400 align:start position:0% adoption of this in the enterprise and for<00:14:53.850> me<00:14:53.970> that's<00:14:54.180> where<00:14:54.480> the<00:14:54.510> huge<00:14:54.990> adoption 00:14:55.400 --> 00:14:55.410 align:start position:0% for me that's where the huge adoption 00:14:55.410 --> 00:15:00.520 align:start position:0% for me that's where the huge adoption comes<00:14:56.150> beyond<00:14:57.150> the<00:14:57.420> cryptographic<00:14:57.780> space 00:15:00.520 --> 00:15:00.530 align:start position:0% 00:15:00.530 --> 00:15:02.540 align:start position:0% thank<00:15:01.530> you<00:15:01.590> very<00:15:01.650> much<00:15:01.860> that's<00:15:02.130> all<00:15:02.310> I<00:15:02.370> have 00:15:02.540 --> 00:15:02.550 align:start position:0% thank you very much that's all I have 00:15:02.550 --> 00:15:11.730 align:start position:0% thank you very much that's all I have today 00:15:11.730 --> 00:15:11.740 align:start position:0% 00:15:11.740 --> 00:15:15.300 align:start position:0% time<00:15:12.740> for<00:15:12.920> questions<00:15:13.310> if<00:15:13.699> anybody<00:15:13.940> has<00:15:14.180> any 00:15:15.300 --> 00:15:15.310 align:start position:0% time for questions if anybody has any 00:15:15.310 --> 00:15:23.009 align:start position:0% time for questions if anybody has any minute<00:15:16.329> yes<00:15:18.730> where<00:15:19.730> can<00:15:19.940> we<00:15:20.089> get<00:15:20.360> your<00:15:20.720> code 00:15:23.009 --> 00:15:23.019 align:start position:0% minute yes where can we get your code 00:15:23.019 --> 00:15:27.579 align:start position:0% minute yes where can we get your code this<00:15:24.019> is<00:15:24.290> on<00:15:24.529> github<00:15:25.509> my<00:15:26.509> github<00:15:26.959> name<00:15:27.230> is<00:15:27.350> T 00:15:27.579 --> 00:15:27.589 align:start position:0% this is on github my github name is T 00:15:27.589 --> 00:15:31.629 align:start position:0% this is on github my github name is T Goering<00:15:28.180> I<00:15:29.439> have<00:15:30.439> it<00:15:30.589> running<00:15:30.800> also<00:15:31.220> on<00:15:31.459> the 00:15:31.629 --> 00:15:31.639 align:start position:0% Goering I have it running also on the 00:15:31.639 --> 00:15:33.699 align:start position:0% Goering I have it running also on the like<00:15:32.089> github<00:15:32.360> pages<00:15:32.720> but<00:15:33.199> due<00:15:33.470> to<00:15:33.500> the 00:15:33.699 --> 00:15:33.709 align:start position:0% like github pages but due to the 00:15:33.709 --> 00:15:36.160 align:start position:0% like github pages but due to the limitations<00:15:34.339> of<00:15:34.430> browsers<00:15:34.879> between<00:15:35.269> HTTPS 00:15:36.160 --> 00:15:36.170 align:start position:0% limitations of browsers between HTTPS 00:15:36.170 --> 00:15:38.889 align:start position:0% limitations of browsers between HTTPS and<00:15:36.199> HTTP<00:15:37.160> it<00:15:37.399> doesn't<00:15:37.730> really<00:15:38.240> work<00:15:38.389> so<00:15:38.750> well 00:15:38.889 --> 00:15:38.899 align:start position:0% and HTTP it doesn't really work so well 00:15:38.899 --> 00:15:40.720 align:start position:0% and HTTP it doesn't really work so well but<00:15:39.350> all<00:15:39.439> you<00:15:39.500> have<00:15:39.620> to<00:15:39.680> do<00:15:39.769> is<00:15:39.860> get<00:15:40.009> clone<00:15:40.310> and 00:15:40.720 --> 00:15:40.730 align:start position:0% but all you have to do is get clone and 00:15:40.730 --> 00:15:43.600 align:start position:0% but all you have to do is get clone and open<00:15:41.000> up<00:15:41.060> index.html<00:15:42.019> and<00:15:42.079> it's<00:15:42.350> there<00:15:42.589> I<00:15:43.009> will 00:15:43.600 --> 00:15:43.610 align:start position:0% open up index.html and it's there I will 00:15:43.610 --> 00:15:46.269 align:start position:0% open up index.html and it's there I will warn<00:15:43.850> you<00:15:44.029> it<00:15:44.269> is<00:15:44.660> under<00:15:45.470> heavy<00:15:45.680> development 00:15:46.269 --> 00:15:46.279 align:start position:0% warn you it is under heavy development 00:15:46.279 --> 00:15:52.499 align:start position:0% warn you it is under heavy development and<00:15:46.459> not<00:15:47.149> perfect<00:15:48.339> but<00:15:49.339> the<00:15:49.879> codes<00:15:50.089> on<00:15:50.180> github 00:15:52.499 --> 00:15:52.509 align:start position:0% 00:15:52.509 --> 00:15:55.990 align:start position:0% any<00:15:53.509> other<00:15:53.600> questions