WEBVTT Kind: captions Language: en 00:00:17.860 --> 00:00:20.470 align:start position:0% so<00:00:18.860> I'm<00:00:19.009> Victor<00:00:19.310> Wang<00:00:19.490> one<00:00:19.880> of<00:00:19.970> the<00:00:20.060> founders 00:00:20.470 --> 00:00:20.480 align:start position:0% so I'm Victor Wang one of the founders 00:00:20.480 --> 00:00:22.089 align:start position:0% so I'm Victor Wang one of the founders of<00:00:20.509> block<00:00:20.899> apps<00:00:21.140> and<00:00:21.439> I'm<00:00:21.529> here<00:00:21.770> to<00:00:21.890> introduce 00:00:22.089 --> 00:00:22.099 align:start position:0% of block apps and I'm here to introduce 00:00:22.099 --> 00:00:24.490 align:start position:0% of block apps and I'm here to introduce to<00:00:22.550> the<00:00:22.669> world<00:00:22.700> block<00:00:23.599> apps<00:00:23.840> Trudeau<00:00:24.230> on 00:00:24.490 --> 00:00:24.500 align:start position:0% to the world block apps Trudeau on 00:00:24.500 --> 00:00:26.979 align:start position:0% to the world block apps Trudeau on Microsoft<00:00:25.040> Azure<00:00:25.250> the<00:00:26.000> easiest<00:00:26.570> way<00:00:26.689> to<00:00:26.720> build 00:00:26.979 --> 00:00:26.989 align:start position:0% Microsoft Azure the easiest way to build 00:00:26.989 --> 00:00:31.479 align:start position:0% Microsoft Azure the easiest way to build blockchain<00:00:27.590> applications<00:00:30.009> you've<00:00:31.009> seen<00:00:31.250> this 00:00:31.479 --> 00:00:31.489 align:start position:0% blockchain applications you've seen this 00:00:31.489 --> 00:00:34.810 align:start position:0% blockchain applications you've seen this comparison<00:00:32.119> made<00:00:32.300> countless<00:00:32.689> times<00:00:33.820> Bitcoin 00:00:34.810 --> 00:00:34.820 align:start position:0% comparison made countless times Bitcoin 00:00:34.820 --> 00:00:36.970 align:start position:0% comparison made countless times Bitcoin as<00:00:35.120> a<00:00:35.149> blockchain<00:00:35.600> we<00:00:36.050> know<00:00:36.200> is<00:00:36.350> limited<00:00:36.830> in 00:00:36.970 --> 00:00:36.980 align:start position:0% as a blockchain we know is limited in 00:00:36.980 --> 00:00:39.400 align:start position:0% as a blockchain we know is limited in functionality<00:00:37.220> and<00:00:37.940> thanks<00:00:38.570> to<00:00:38.690> Vitalik<00:00:39.200> and 00:00:39.400 --> 00:00:39.410 align:start position:0% functionality and thanks to Vitalik and 00:00:39.410 --> 00:00:41.110 align:start position:0% functionality and thanks to Vitalik and the<00:00:39.620> work<00:00:39.740> of<00:00:39.890> the<00:00:39.980> etherium<00:00:40.340> foundation<00:00:40.910> and 00:00:41.110 --> 00:00:41.120 align:start position:0% the work of the etherium foundation and 00:00:41.120 --> 00:00:42.100 align:start position:0% the work of the etherium foundation and eat<00:00:41.570> them 00:00:42.100 --> 00:00:42.110 align:start position:0% eat them 00:00:42.110 --> 00:00:45.190 align:start position:0% eat them we<00:00:42.470> now<00:00:42.680> have<00:00:43.010> a<00:00:43.220> completely<00:00:43.910> new<00:00:44.450> global 00:00:45.190 --> 00:00:45.200 align:start position:0% we now have a completely new global 00:00:45.200 --> 00:00:48.900 align:start position:0% we now have a completely new global computing<00:00:46.040> platform<00:00:46.720> but<00:00:47.720> because<00:00:48.500> of<00:00:48.530> that 00:00:48.900 --> 00:00:48.910 align:start position:0% computing platform but because of that 00:00:48.910 --> 00:00:52.000 align:start position:0% computing platform but because of that the<00:00:49.910> success<00:00:50.420> or<00:00:50.600> failure<00:00:50.660> of<00:00:51.020> almost<00:00:51.650> any 00:00:52.000 --> 00:00:52.010 align:start position:0% the success or failure of almost any 00:00:52.010 --> 00:00:54.730 align:start position:0% the success or failure of almost any computing<00:00:52.670> platform<00:00:53.150> is<00:00:53.329> actually<00:00:54.200> based<00:00:54.500> on 00:00:54.730 --> 00:00:54.740 align:start position:0% computing platform is actually based on 00:00:54.740 --> 00:00:56.680 align:start position:0% computing platform is actually based on the<00:00:54.860> number<00:00:55.489> of<00:00:55.579> applications<00:00:56.090> that<00:00:56.420> are 00:00:56.680 --> 00:00:56.690 align:start position:0% the number of applications that are 00:00:56.690 --> 00:01:01.300 align:start position:0% the number of applications that are being<00:00:56.870> delivered<00:00:57.200> on<00:00:57.410> it<00:00:58.989> so<00:00:59.989> black<00:01:00.800> ops<00:01:01.070> has<00:01:01.280> a 00:01:01.300 --> 00:01:01.310 align:start position:0% being delivered on it so black ops has a 00:01:01.310 --> 00:01:04.479 align:start position:0% being delivered on it so black ops has a simple<00:01:01.730> mission<00:01:01.910> we<00:01:02.780> want<00:01:03.050> to<00:01:03.200> be<00:01:03.410> the<00:01:03.890> easiest 00:01:04.479 --> 00:01:04.489 align:start position:0% simple mission we want to be the easiest 00:01:04.489 --> 00:01:07.030 align:start position:0% simple mission we want to be the easiest way<00:01:04.790> to<00:01:04.820> build<00:01:05.299> and<00:01:05.570> deploy<00:01:06.040> blockchain 00:01:07.030 --> 00:01:07.040 align:start position:0% way to build and deploy blockchain 00:01:07.040 --> 00:01:09.340 align:start position:0% way to build and deploy blockchain applications<00:01:07.729> and<00:01:07.939> businesses<00:01:08.510> on<00:01:08.720> the 00:01:09.340 --> 00:01:09.350 align:start position:0% applications and businesses on the 00:01:09.350 --> 00:01:12.580 align:start position:0% applications and businesses on the etherium<00:01:09.850> platform<00:01:10.960> were<00:01:11.960> the<00:01:12.140> team<00:01:12.380> behind 00:01:12.580 --> 00:01:12.590 align:start position:0% etherium platform were the team behind 00:01:12.590 --> 00:01:16.170 align:start position:0% etherium platform were the team behind the<00:01:13.659> etherium<00:01:14.690> Pascal<00:01:15.140> implementation<00:01:15.830> and 00:01:16.170 --> 00:01:16.180 align:start position:0% the etherium Pascal implementation and 00:01:16.180 --> 00:01:18.610 align:start position:0% the etherium Pascal implementation and we<00:01:17.180> want<00:01:17.390> to<00:01:17.479> be<00:01:17.600> able<00:01:17.690> to<00:01:17.930> provide<00:01:18.440> the 00:01:18.610 --> 00:01:18.620 align:start position:0% we want to be able to provide the 00:01:18.620 --> 00:01:21.430 align:start position:0% we want to be able to provide the facility<00:01:19.159> to<00:01:19.640> easily<00:01:20.210> deploy<00:01:20.600> private 00:01:21.430 --> 00:01:21.440 align:start position:0% facility to easily deploy private 00:01:21.440 --> 00:01:22.300 align:start position:0% facility to easily deploy private blockchains 00:01:22.300 --> 00:01:22.310 align:start position:0% blockchains 00:01:22.310 --> 00:01:25.750 align:start position:0% blockchains but<00:01:22.909> also<00:01:23.479> have<00:01:23.750> these<00:01:24.020> block<00:01:24.409> chains<00:01:24.710> be<00:01:25.549> able 00:01:25.750 --> 00:01:25.760 align:start position:0% but also have these block chains be able 00:01:25.760 --> 00:01:27.010 align:start position:0% but also have these block chains be able to<00:01:25.850> communicate<00:01:26.150> with<00:01:26.510> the<00:01:26.840> public 00:01:27.010 --> 00:01:27.020 align:start position:0% to communicate with the public 00:01:27.020 --> 00:01:30.730 align:start position:0% to communicate with the public blockchain<00:01:28.210> lastly<00:01:29.210> we<00:01:29.870> want<00:01:30.110> to<00:01:30.290> make<00:01:30.530> sure 00:01:30.730 --> 00:01:30.740 align:start position:0% blockchain lastly we want to make sure 00:01:30.740 --> 00:01:33.490 align:start position:0% blockchain lastly we want to make sure that<00:01:30.979> applications<00:01:31.760> built<00:01:32.090> on<00:01:32.360> our<00:01:32.540> on<00:01:32.869> our 00:01:33.490 --> 00:01:33.500 align:start position:0% that applications built on our on our 00:01:33.500 --> 00:01:36.160 align:start position:0% that applications built on our on our platform<00:01:34.220> can<00:01:34.880> communicate<00:01:35.479> with<00:01:35.690> existing 00:01:36.160 --> 00:01:36.170 align:start position:0% platform can communicate with existing 00:01:36.170 --> 00:01:39.039 align:start position:0% platform can communicate with existing systems<00:01:36.619> and<00:01:37.220> devices<00:01:37.760> in<00:01:37.970> a<00:01:38.510> sense<00:01:38.750> what<00:01:38.930> we 00:01:39.039 --> 00:01:39.049 align:start position:0% systems and devices in a sense what we 00:01:39.049 --> 00:01:41.170 align:start position:0% systems and devices in a sense what we want<00:01:39.229> to<00:01:39.380> provide<00:01:39.680> is<00:01:39.890> a<00:01:40.040> bridge<00:01:40.700> to<00:01:41.060> the 00:01:41.170 --> 00:01:41.180 align:start position:0% want to provide is a bridge to the 00:01:41.180 --> 00:01:46.570 align:start position:0% want to provide is a bridge to the existing<00:01:41.690> world<00:01:41.930> with<00:01:42.680> ethereal<00:01:45.369> but<00:01:46.369> here's 00:01:46.570 --> 00:01:46.580 align:start position:0% existing world with ethereal but here's 00:01:46.580 --> 00:01:50.380 align:start position:0% existing world with ethereal but here's the<00:01:46.700> challenge<00:01:47.080> now<00:01:48.490> many<00:01:49.490> of<00:01:49.640> you<00:01:49.700> know<00:01:49.850> all 00:01:50.380 --> 00:01:50.390 align:start position:0% the challenge now many of you know all 00:01:50.390 --> 00:01:52.690 align:start position:0% the challenge now many of you know all these<00:01:50.630> terms<00:01:50.990> you<00:01:51.320> know<00:01:51.680> what<00:01:51.979> this<00:01:52.220> entire 00:01:52.690 --> 00:01:52.700 align:start position:0% these terms you know what this entire 00:01:52.700 --> 00:01:55.270 align:start position:0% these terms you know what this entire ecosystem<00:01:53.119> is<00:01:53.600> about<00:01:53.869> but<00:01:54.409> I<00:01:54.560> can<00:01:54.860> tell<00:01:55.070> you 00:01:55.270 --> 00:01:55.280 align:start position:0% ecosystem is about but I can tell you 00:01:55.280 --> 00:01:57.640 align:start position:0% ecosystem is about but I can tell you when<00:01:55.610> you<00:01:55.729> show<00:01:55.970> this<00:01:56.150> slide<00:01:56.360> to<00:01:56.840> regular 00:01:57.640 --> 00:01:57.650 align:start position:0% when you show this slide to regular 00:01:57.650 --> 00:02:00.280 align:start position:0% when you show this slide to regular people<00:01:57.979> they<00:01:58.130> are<00:01:58.460> terrified<00:01:58.970> they<00:01:59.840> have<00:01:59.990> no 00:02:00.280 --> 00:02:00.290 align:start position:0% people they are terrified they have no 00:02:00.290 --> 00:02:02.590 align:start position:0% people they are terrified they have no idea<00:02:00.740> about<00:02:01.009> where<00:02:01.220> to<00:02:01.369> begin<00:02:01.520> because<00:02:02.299> truly 00:02:02.590 --> 00:02:02.600 align:start position:0% idea about where to begin because truly 00:02:02.600 --> 00:02:05.260 align:start position:0% idea about where to begin because truly the<00:02:03.290> etherium<00:02:03.680> ecosystem<00:02:04.280> is<00:02:04.430> not<00:02:04.670> just<00:02:04.909> one 00:02:05.260 --> 00:02:05.270 align:start position:0% the etherium ecosystem is not just one 00:02:05.270 --> 00:02:07.499 align:start position:0% the etherium ecosystem is not just one tool<00:02:05.720> but<00:02:06.409> a<00:02:06.439> series<00:02:06.890> of<00:02:06.920> interconnected 00:02:07.499 --> 00:02:07.509 align:start position:0% tool but a series of interconnected 00:02:07.509 --> 00:02:09.850 align:start position:0% tool but a series of interconnected technologies<00:02:08.509> and<00:02:08.720> tools<00:02:08.929> and<00:02:09.349> you<00:02:09.530> have<00:02:09.560> to 00:02:09.850 --> 00:02:09.860 align:start position:0% technologies and tools and you have to 00:02:09.860 --> 00:02:12.729 align:start position:0% technologies and tools and you have to understand<00:02:10.489> the<00:02:10.909> entire<00:02:11.299> picture<00:02:11.629> to<00:02:12.349> really 00:02:12.729 --> 00:02:12.739 align:start position:0% understand the entire picture to really 00:02:12.739 --> 00:02:15.220 align:start position:0% understand the entire picture to really be<00:02:12.889> able<00:02:12.980> to<00:02:13.329> maximize<00:02:14.329> the<00:02:14.510> use<00:02:14.689> of<00:02:14.900> it<00:02:15.049> so 00:02:15.220 --> 00:02:15.230 align:start position:0% be able to maximize the use of it so 00:02:15.230 --> 00:02:17.680 align:start position:0% be able to maximize the use of it so many<00:02:15.950> people<00:02:16.279> come<00:02:16.430> to<00:02:16.459> us<00:02:16.669> and<00:02:16.819> they<00:02:16.939> say 00:02:17.680 --> 00:02:17.690 align:start position:0% many people come to us and they say 00:02:17.690 --> 00:02:20.170 align:start position:0% many people come to us and they say well<00:02:17.840> where<00:02:18.590> do<00:02:18.710> I<00:02:18.770> start<00:02:19.160> where<00:02:19.760> do<00:02:19.910> I<00:02:19.940> begin 00:02:20.170 --> 00:02:20.180 align:start position:0% well where do I start where do I begin 00:02:20.180 --> 00:02:23.530 align:start position:0% well where do I start where do I begin and<00:02:21.220> that's<00:02:22.220> where<00:02:22.460> black<00:02:22.670> ops<00:02:22.880> Jurado<00:02:23.210> comes 00:02:23.530 --> 00:02:23.540 align:start position:0% and that's where black ops Jurado comes 00:02:23.540 --> 00:02:26.850 align:start position:0% and that's where black ops Jurado comes in<00:02:23.720> basically<00:02:24.710> what<00:02:25.010> black<00:02:25.310> ops<00:02:25.580> Jurado<00:02:25.970> is<00:02:26.360> a 00:02:26.850 --> 00:02:26.860 align:start position:0% in basically what black ops Jurado is a 00:02:26.860 --> 00:02:30.000 align:start position:0% in basically what black ops Jurado is a full<00:02:27.860> aetherium<00:02:28.730> blotching<00:02:29.300> as<00:02:29.450> a<00:02:29.480> service 00:02:30.000 --> 00:02:30.010 align:start position:0% full aetherium blotching as a service 00:02:30.010 --> 00:02:33.010 align:start position:0% full aetherium blotching as a service framework<00:02:31.010> that<00:02:31.790> gives<00:02:31.940> you<00:02:32.150> everything<00:02:32.360> you 00:02:33.010 --> 00:02:33.020 align:start position:0% framework that gives you everything you 00:02:33.020 --> 00:02:35.290 align:start position:0% framework that gives you everything you need<00:02:33.200> to<00:02:33.890> start<00:02:34.100> building<00:02:34.400> blockchain 00:02:35.290 --> 00:02:35.300 align:start position:0% need to start building blockchain 00:02:35.300 --> 00:02:38.590 align:start position:0% need to start building blockchain applications<00:02:36.050> today<00:02:36.640> that<00:02:37.640> goes<00:02:38.030> all<00:02:38.300> the<00:02:38.360> way 00:02:38.590 --> 00:02:38.600 align:start position:0% applications today that goes all the way 00:02:38.600 --> 00:02:41.770 align:start position:0% applications today that goes all the way from<00:02:39.460> spinning<00:02:40.460> up<00:02:40.610> your<00:02:40.790> bone<00:02:40.970> blockchain<00:02:41.540> a 00:02:41.770 --> 00:02:41.780 align:start position:0% from spinning up your bone blockchain a 00:02:41.780 --> 00:02:45.910 align:start position:0% from spinning up your bone blockchain a bit<00:02:42.470> aware<00:02:42.800> API<00:02:43.460> connector<00:02:44.090> wallets<00:02:45.080> faucets 00:02:45.910 --> 00:02:45.920 align:start position:0% bit aware API connector wallets faucets 00:02:45.920 --> 00:02:48.100 align:start position:0% bit aware API connector wallets faucets everything<00:02:46.610> you<00:02:46.730> need<00:02:46.910> to<00:02:47.390> build<00:02:47.600> and<00:02:47.810> deploy 00:02:48.100 --> 00:02:48.110 align:start position:0% everything you need to build and deploy 00:02:48.110 --> 00:02:50.920 align:start position:0% everything you need to build and deploy applications<00:02:48.940> and<00:02:49.940> we're<00:02:50.600> going<00:02:50.750> to<00:02:50.780> show<00:02:50.900> you 00:02:50.920 --> 00:02:50.930 align:start position:0% applications and we're going to show you 00:02:50.930 --> 00:02:53.290 align:start position:0% applications and we're going to show you a<00:02:51.080> live<00:02:51.200> coding<00:02:51.620> demo<00:02:51.920> by<00:02:52.250> one<00:02:52.520> by<00:02:52.670> co-founders 00:02:53.290 --> 00:02:53.300 align:start position:0% a live coding demo by one by co-founders 00:02:53.300 --> 00:02:55.240 align:start position:0% a live coding demo by one by co-founders Karen<00:02:54.020> James<00:02:54.230> Logan<00:02:54.470> our<00:02:54.800> chief<00:02:55.070> data 00:02:55.240 --> 00:02:55.250 align:start position:0% Karen James Logan our chief data 00:02:55.250 --> 00:03:15.180 align:start position:0% Karen James Logan our chief data scientist<00:03:01.630> thanks<00:03:02.630> Victor 00:03:15.180 --> 00:03:15.190 align:start position:0% 00:03:15.190 --> 00:03:21.600 align:start position:0% okay<00:03:15.970> there<00:03:16.150> we<00:03:16.210> go<00:03:17.490> let<00:03:18.490> me<00:03:18.760> maximize<00:03:19.600> this<00:03:20.610> so 00:03:21.600 --> 00:03:21.610 align:start position:0% okay there we go let me maximize this so 00:03:21.610 --> 00:03:23.490 align:start position:0% okay there we go let me maximize this so first<00:03:22.570> thing<00:03:22.690> I'm<00:03:22.810> gonna<00:03:22.900> do<00:03:23.110> is<00:03:23.140> actually 00:03:23.490 --> 00:03:23.500 align:start position:0% first thing I'm gonna do is actually 00:03:23.500 --> 00:03:26.610 align:start position:0% first thing I'm gonna do is actually launch<00:03:24.070> a<00:03:24.340> live<00:03:24.990> instance<00:03:25.990> of<00:03:26.170> Strato 00:03:26.610 --> 00:03:26.620 align:start position:0% launch a live instance of Strato 00:03:26.620 --> 00:03:28.560 align:start position:0% launch a live instance of Strato it<00:03:27.040> takes<00:03:27.340> a<00:03:27.580> minute<00:03:27.850> to<00:03:27.940> spin<00:03:28.180> up<00:03:28.330> and<00:03:28.480> we've 00:03:28.560 --> 00:03:28.570 align:start position:0% it takes a minute to spin up and we've 00:03:28.570 --> 00:03:30.570 align:start position:0% it takes a minute to spin up and we've got<00:03:28.600> Network<00:03:29.110> latency<00:03:29.620> then<00:03:30.220> I'm<00:03:30.310> gonna<00:03:30.400> go 00:03:30.570 --> 00:03:30.580 align:start position:0% got Network latency then I'm gonna go 00:03:30.580 --> 00:03:32.940 align:start position:0% got Network latency then I'm gonna go into<00:03:30.730> one<00:03:31.090> of<00:03:31.180> our<00:03:31.270> demos<00:03:31.690> so<00:03:32.380> we<00:03:32.530> have<00:03:32.620> to<00:03:32.710> pick 00:03:32.940 --> 00:03:32.950 align:start position:0% into one of our demos so we have to pick 00:03:32.950 --> 00:03:34.500 align:start position:0% into one of our demos so we have to pick exactly<00:03:33.670> what<00:03:33.790> I'm<00:03:33.880> gonna<00:03:34.000> code 00:03:34.500 --> 00:03:34.510 align:start position:0% exactly what I'm gonna code 00:03:34.510 --> 00:03:37.130 align:start position:0% exactly what I'm gonna code I've<00:03:34.570> got<00:03:34.750> about<00:03:34.930> five<00:03:35.230> minutes<00:03:35.380> to<00:03:35.680> do<00:03:35.830> it 00:03:37.130 --> 00:03:37.140 align:start position:0% I've got about five minutes to do it 00:03:37.140 --> 00:03:40.350 align:start position:0% I've got about five minutes to do it sure<00:03:38.170> so<00:03:38.890> Karen<00:03:39.580> since<00:03:39.760> we're<00:03:39.970> partners<00:03:40.330> with 00:03:40.350 --> 00:03:40.360 align:start position:0% sure so Karen since we're partners with 00:03:40.360 --> 00:03:42.830 align:start position:0% sure so Karen since we're partners with Microsoft<00:03:41.020> now<00:03:41.170> I'd<00:03:41.440> like<00:03:41.620> you<00:03:41.770> to<00:03:41.920> change<00:03:42.310> our 00:03:42.830 --> 00:03:42.840 align:start position:0% Microsoft now I'd like you to change our 00:03:42.840 --> 00:03:45.540 align:start position:0% Microsoft now I'd like you to change our revenue<00:03:43.840> sharing<00:03:44.140> agreement<00:03:44.740> so<00:03:45.190> I'd 00:03:45.540 --> 00:03:45.550 align:start position:0% revenue sharing agreement so I'd 00:03:45.550 --> 00:03:49.380 align:start position:0% revenue sharing agreement so I'd Microsoft<00:03:46.390> into<00:03:47.350> our<00:03:47.470> company<00:03:47.920> and<00:03:48.240> let<00:03:49.240> them 00:03:49.380 --> 00:03:49.390 align:start position:0% Microsoft into our company and let them 00:03:49.390 --> 00:03:51.240 align:start position:0% Microsoft into our company and let them share<00:03:49.570> part<00:03:49.870> of<00:03:49.960> the<00:03:50.080> revenue<00:03:50.380> and<00:03:50.680> I'd<00:03:50.980> also 00:03:51.240 --> 00:03:51.250 align:start position:0% share part of the revenue and I'd also 00:03:51.250 --> 00:03:52.860 align:start position:0% share part of the revenue and I'd also like<00:03:51.520> to<00:03:51.580> make<00:03:51.970> sure<00:03:52.000> you<00:03:52.270> have<00:03:52.360> five<00:03:52.540> minutes 00:03:52.860 --> 00:03:52.870 align:start position:0% like to make sure you have five minutes 00:03:52.870 --> 00:03:54.450 align:start position:0% like to make sure you have five minutes right<00:03:53.020> yeah<00:03:53.350> make<00:03:53.740> sure<00:03:53.770> everything<00:03:54.400> you 00:03:54.450 --> 00:03:54.460 align:start position:0% right yeah make sure everything you 00:03:54.460 --> 00:03:55.980 align:start position:0% right yeah make sure everything you write<00:03:54.700> can<00:03:54.940> run<00:03:55.120> on<00:03:55.240> any<00:03:55.510> internet-connected 00:03:55.980 --> 00:03:55.990 align:start position:0% write can run on any internet-connected 00:03:55.990 --> 00:03:59.670 align:start position:0% write can run on any internet-connected device<00:03:56.800> including<00:03:57.670> a<00:03:57.910> mobile<00:03:58.180> phone<00:03:58.540> and<00:03:58.870> any 00:03:59.670 --> 00:03:59.680 align:start position:0% device including a mobile phone and any 00:03:59.680 --> 00:04:02.160 align:start position:0% device including a mobile phone and any browser<00:04:00.070> okay<00:04:01.030> got<00:04:01.480> it<00:04:01.510> we<00:04:01.720> fire<00:04:01.930> up<00:04:01.960> the 00:04:02.160 --> 00:04:02.170 align:start position:0% browser okay got it we fire up the 00:04:02.170 --> 00:04:08.490 align:start position:0% browser okay got it we fire up the instance<00:04:04.260> all<00:04:05.260> right<00:04:06.960> start<00:04:07.960> in<00:04:08.080> the<00:04:08.170> deploy 00:04:08.490 --> 00:04:08.500 align:start position:0% instance all right start in the deploy 00:04:08.500 --> 00:04:13.260 align:start position:0% instance all right start in the deploy here<00:04:11.220> so<00:04:12.220> this<00:04:12.310> all<00:04:12.490> get<00:04:12.670> listed<00:04:13.090> on<00:04:13.180> the 00:04:13.260 --> 00:04:13.270 align:start position:0% here so this all get listed on the 00:04:13.270 --> 00:04:15.570 align:start position:0% here so this all get listed on the marketplace<00:04:13.630> soon<00:04:14.050> but<00:04:14.410> this<00:04:14.860> is<00:04:15.040> the<00:04:15.370> block 00:04:15.570 --> 00:04:15.580 align:start position:0% marketplace soon but this is the block 00:04:15.580 --> 00:04:17.880 align:start position:0% marketplace soon but this is the block apps<00:04:15.790> login<00:04:16.269> for<00:04:16.510> the<00:04:16.540> moment<00:04:16.900> it's<00:04:17.590> called 00:04:17.880 --> 00:04:17.890 align:start position:0% apps login for the moment it's called 00:04:17.890 --> 00:04:32.730 align:start position:0% apps login for the moment it's called this<00:04:18.600> Strato<00:04:19.600> dev 00:04:32.730 --> 00:04:32.740 align:start position:0% 00:04:32.740 --> 00:04:38.950 align:start position:0% we're<00:04:33.740> firing<00:04:33.980> up<00:04:37.330> all<00:04:38.330> right<00:04:38.450> looks<00:04:38.630> good<00:04:38.720> let 00:04:38.950 --> 00:04:38.960 align:start position:0% we're firing up all right looks good let 00:04:38.960 --> 00:04:42.580 align:start position:0% we're firing up all right looks good let me<00:04:38.990> go<00:04:39.140> go<00:04:39.560> into<00:04:39.830> the<00:04:39.920> contract<00:04:40.400> so<00:04:41.380> I'm<00:04:42.380> about 00:04:42.580 --> 00:04:42.590 align:start position:0% me go go into the contract so I'm about 00:04:42.590 --> 00:04:44.260 align:start position:0% me go go into the contract so I'm about to<00:04:42.710> show<00:04:42.890> you<00:04:42.920> a<00:04:43.070> command<00:04:43.400> line<00:04:43.670> tool<00:04:43.790> called 00:04:44.260 --> 00:04:44.270 align:start position:0% to show you a command line tool called 00:04:44.270 --> 00:04:48.040 align:start position:0% to show you a command line tool called block<00:04:46.390> these<00:04:47.390> are<00:04:47.570> the<00:04:47.630> commands<00:04:47.930> and 00:04:48.040 --> 00:04:48.050 align:start position:0% block these are the commands and 00:04:48.050 --> 00:04:52.080 align:start position:0% block these are the commands and supports<00:04:49.060> and<00:04:50.060> what<00:04:50.660> I've<00:04:50.810> set<00:04:50.990> up<00:04:51.020> here<00:04:51.380> is<00:04:51.590> a 00:04:52.080 --> 00:04:52.090 align:start position:0% supports and what I've set up here is a 00:04:52.090 --> 00:04:56.020 align:start position:0% supports and what I've set up here is a scaffolded<00:04:53.860> blockchain<00:04:54.860> application<00:04:55.460> kind 00:04:56.020 --> 00:04:56.030 align:start position:0% scaffolded blockchain application kind 00:04:56.030 --> 00:04:57.970 align:start position:0% scaffolded blockchain application kind of<00:04:56.150> looks<00:04:56.330> like<00:04:56.390> a<00:04:56.480> web<00:04:56.720> app<00:04:56.930> you<00:04:57.650> can<00:04:57.770> see 00:04:57.970 --> 00:04:57.980 align:start position:0% of looks like a web app you can see 00:04:57.980 --> 00:05:02.920 align:start position:0% of looks like a web app you can see we've<00:04:58.310> got<00:04:58.340> HTML<00:04:59.500> Javascript<00:05:00.500> CSS<00:05:00.770> and<00:05:01.730> a<00:05:02.180> pas 00:05:02.920 --> 00:05:02.930 align:start position:0% we've got HTML Javascript CSS and a pas 00:05:02.930 --> 00:05:05.380 align:start position:0% we've got HTML Javascript CSS and a pas to<00:05:03.200> run<00:05:03.350> a<00:05:03.380> web<00:05:03.590> server<00:05:03.920> even<00:05:04.670> get<00:05:04.880> a<00:05:04.910> contracts 00:05:05.380 --> 00:05:05.390 align:start position:0% to run a web server even get a contracts 00:05:05.390 --> 00:05:07.690 align:start position:0% to run a web server even get a contracts folder<00:05:05.600> and<00:05:05.930> in<00:05:06.740> the<00:05:06.860> contracts<00:05:07.280> folder<00:05:07.430> we've 00:05:07.690 --> 00:05:07.700 align:start position:0% folder and in the contracts folder we've 00:05:07.700 --> 00:05:09.610 align:start position:0% folder and in the contracts folder we've got<00:05:07.880> some<00:05:08.090> standard<00:05:08.360> solidity<00:05:08.930> contracts<00:05:09.530> to 00:05:09.610 --> 00:05:09.620 align:start position:0% got some standard solidity contracts to 00:05:09.620 --> 00:05:11.860 align:start position:0% got some standard solidity contracts to get<00:05:09.770> you<00:05:09.890> up<00:05:10.040> and<00:05:10.160> running<00:05:10.220> quickly<00:05:10.690> so<00:05:11.690> let's 00:05:11.860 --> 00:05:11.870 align:start position:0% get you up and running quickly so let's 00:05:11.870 --> 00:05:16.150 align:start position:0% get you up and running quickly so let's take<00:05:12.020> a<00:05:12.050> look<00:05:12.350> at<00:05:12.770> what's<00:05:13.040> there<00:05:15.100> it's<00:05:16.100> a 00:05:16.150 --> 00:05:16.160 align:start position:0% take a look at what's there it's a 00:05:16.160 --> 00:05:19.450 align:start position:0% take a look at what's there it's a couple<00:05:16.430> samples<00:05:17.170> the<00:05:18.170> payout<00:05:18.530> contract<00:05:19.190> is 00:05:19.450 --> 00:05:19.460 align:start position:0% couple samples the payout contract is 00:05:19.460 --> 00:05:21.010 align:start position:0% couple samples the payout contract is the<00:05:19.610> contract<00:05:20.090> that<00:05:20.150> block<00:05:20.450> Apps<00:05:20.690> has<00:05:20.810> been 00:05:21.010 --> 00:05:21.020 align:start position:0% the contract that block Apps has been 00:05:21.020 --> 00:05:23.080 align:start position:0% the contract that block Apps has been working<00:05:21.200> on<00:05:21.440> this<00:05:22.130> encodes<00:05:22.550> the<00:05:22.730> revenue 00:05:23.080 --> 00:05:23.090 align:start position:0% working on this encodes the revenue 00:05:23.090 --> 00:05:25.540 align:start position:0% working on this encodes the revenue split<00:05:23.270> or<00:05:23.810> they<00:05:24.050> be<00:05:24.110> the<00:05:24.860> ownership<00:05:25.130> split 00:05:25.540 --> 00:05:25.550 align:start position:0% split or they be the ownership split 00:05:25.550 --> 00:05:27.910 align:start position:0% split or they be the ownership split between<00:05:25.760> Victor<00:05:26.600> Jim<00:05:26.840> and<00:05:27.020> I<00:05:27.080> and<00:05:27.290> we're<00:05:27.830> gonna 00:05:27.910 --> 00:05:27.920 align:start position:0% between Victor Jim and I and we're gonna 00:05:27.920 --> 00:05:32.230 align:start position:0% between Victor Jim and I and we're gonna cut<00:05:28.220> Microsoft<00:05:28.790> in<00:05:29.000> in<00:05:29.630> a<00:05:29.750> moment<00:05:31.030> let's<00:05:32.030> look 00:05:32.230 --> 00:05:32.240 align:start position:0% cut Microsoft in in a moment let's look 00:05:32.240 --> 00:05:34.450 align:start position:0% cut Microsoft in in a moment let's look at<00:05:32.390> our<00:05:32.420> instance<00:05:32.930> looks<00:05:33.740> like<00:05:33.890> it's<00:05:34.040> almost 00:05:34.450 --> 00:05:34.460 align:start position:0% at our instance looks like it's almost 00:05:34.460 --> 00:05:45.589 align:start position:0% at our instance looks like it's almost ready<00:05:34.730> and<00:05:36.580> show<00:05:37.580> you<00:05:37.640> the<00:05:37.730> code 00:05:45.589 --> 00:05:45.599 align:start position:0% 00:05:45.599 --> 00:05:48.950 align:start position:0% okay<00:05:46.319> very<00:05:46.710> simple<00:05:46.830> solidity<00:05:47.460> contract<00:05:48.029> three 00:05:48.950 --> 00:05:48.960 align:start position:0% okay very simple solidity contract three 00:05:48.960 --> 00:05:52.249 align:start position:0% okay very simple solidity contract three dresses<00:05:49.369> Victor<00:05:50.369> Jim<00:05:50.580> and<00:05:50.729> I<00:05:51.259> ownership 00:05:52.249 --> 00:05:52.259 align:start position:0% dresses Victor Jim and I ownership 00:05:52.259 --> 00:05:55.699 align:start position:0% dresses Victor Jim and I ownership distribution<00:05:52.919> a<00:05:53.360> setup<00:05:54.360> function<00:05:54.809> in<00:05:55.559> which 00:05:55.699 --> 00:05:55.709 align:start position:0% distribution a setup function in which 00:05:55.709 --> 00:06:01.969 align:start position:0% distribution a setup function in which we<00:05:55.919> split<00:05:56.249> the<00:05:56.639> equity<00:05:57.050> and<00:05:58.050> a<00:05:58.169> dividend<00:06:00.979> see 00:06:01.969 --> 00:06:01.979 align:start position:0% we split the equity and a dividend see 00:06:01.979 --> 00:06:02.889 align:start position:0% we split the equity and a dividend see how<00:06:02.039> we're<00:06:02.189> doing<00:06:02.219> here 00:06:02.889 --> 00:06:02.899 align:start position:0% how we're doing here 00:06:02.899 --> 00:06:12.980 align:start position:0% how we're doing here it's<00:06:03.899> almost<00:06:04.259> ready 00:06:12.980 --> 00:06:12.990 align:start position:0% 00:06:12.990 --> 00:06:21.450 align:start position:0% okay<00:06:17.249> good<00:06:19.199> so<00:06:20.199> now<00:06:20.319> what<00:06:20.469> I'm<00:06:20.559> gonna<00:06:20.619> do<00:06:20.860> I'm 00:06:21.450 --> 00:06:21.460 align:start position:0% okay good so now what I'm gonna do I'm 00:06:21.460 --> 00:06:28.610 align:start position:0% okay good so now what I'm gonna do I'm gonna<00:06:21.550> cut<00:06:21.789> marleah 00:06:28.610 --> 00:06:28.620 align:start position:0% 00:06:28.620 --> 00:06:31.490 align:start position:0% let's<00:06:29.220> give<00:06:29.400> Marley<00:06:29.760> the<00:06:30.210> address<00:06:30.510> with 00:06:31.490 --> 00:06:31.500 align:start position:0% let's give Marley the address with 00:06:31.500 --> 00:06:43.180 align:start position:0% let's give Marley the address with foursie's 00:06:43.180 --> 00:06:43.190 align:start position:0% 00:06:43.190 --> 00:06:49.350 align:start position:0% and<00:06:43.910> because<00:06:44.840> he's<00:06:44.960> been<00:06:45.140> so<00:06:45.380> kind<00:06:45.590> to<00:06:45.740> us 00:06:49.350 --> 00:06:49.360 align:start position:0% 00:06:49.360 --> 00:07:01.050 align:start position:0% we're<00:06:50.360> doing<00:06:50.570> Marley<00:06:52.030> 70%<00:06:53.030> of<00:06:53.090> block<00:06:53.330> ups 00:07:01.050 --> 00:07:01.060 align:start position:0% 00:07:01.060 --> 00:07:12.660 align:start position:0% gotta<00:07:02.060> add<00:07:02.240> a<00:07:02.270> line<00:07:02.570> here 00:07:12.660 --> 00:07:12.670 align:start position:0% 00:07:12.670 --> 00:07:14.770 align:start position:0% normally<00:07:13.670> I<00:07:13.700> don't<00:07:13.820> roll<00:07:14.000> over<00:07:14.060> like<00:07:14.450> that<00:07:14.660> in 00:07:14.770 --> 00:07:14.780 align:start position:0% normally I don't roll over like that in 00:07:14.780 --> 00:07:22.270 align:start position:0% normally I don't roll over like that in negotiations<00:07:20.740> okay<00:07:21.740> it<00:07:21.800> looks<00:07:21.950> like<00:07:22.100> we're 00:07:22.270 --> 00:07:22.280 align:start position:0% negotiations okay it looks like we're 00:07:22.280 --> 00:07:25.050 align:start position:0% negotiations okay it looks like we're good<00:07:22.400> to<00:07:22.580> go<00:07:22.610> I've<00:07:22.910> set<00:07:23.180> the<00:07:23.330> URL<00:07:23.510> up<00:07:24.080> already 00:07:25.050 --> 00:07:25.060 align:start position:0% good to go I've set the URL up already 00:07:25.060 --> 00:07:27.730 align:start position:0% good to go I've set the URL up already so<00:07:26.060> what<00:07:26.330> we're<00:07:26.480> gonna<00:07:26.540> do<00:07:26.810> now<00:07:26.990> is<00:07:27.230> compile 00:07:27.730 --> 00:07:27.740 align:start position:0% so what we're gonna do now is compile 00:07:27.740 --> 00:07:30.100 align:start position:0% so what we're gonna do now is compile this<00:07:27.920> contract<00:07:28.570> it's<00:07:29.570> a<00:07:29.630> command<00:07:29.960> called 00:07:30.100 --> 00:07:30.110 align:start position:0% this contract it's a command called 00:07:30.110 --> 00:07:34.450 align:start position:0% this contract it's a command called block<00:07:30.410> compile<00:07:32.470> okay<00:07:33.470> that<00:07:33.650> looks<00:07:33.800> good<00:07:34.130> and 00:07:34.450 --> 00:07:34.460 align:start position:0% block compile okay that looks good and 00:07:34.460 --> 00:07:39.280 align:start position:0% block compile okay that looks good and let's<00:07:35.420> go<00:07:35.570> visit<00:07:36.020> our<00:07:36.290> web<00:07:37.070> server<00:07:38.140> so<00:07:39.140> if<00:07:39.230> I 00:07:39.280 --> 00:07:39.290 align:start position:0% let's go visit our web server so if I 00:07:39.290 --> 00:07:41.230 align:start position:0% let's go visit our web server so if I type<00:07:39.470> block<00:07:39.770> start<00:07:40.130> this<00:07:40.370> launches<00:07:40.820> a<00:07:40.850> local 00:07:41.230 --> 00:07:41.240 align:start position:0% type block start this launches a local 00:07:41.240 --> 00:07:43.210 align:start position:0% type block start this launches a local web<00:07:41.390> server<00:07:41.630> and<00:07:42.350> we'll<00:07:42.740> just<00:07:42.920> see<00:07:43.070> what<00:07:43.160> our 00:07:43.210 --> 00:07:43.220 align:start position:0% web server and we'll just see what our 00:07:43.220 --> 00:07:46.060 align:start position:0% web server and we'll just see what our contract<00:07:43.760> looks<00:07:43.910> like<00:07:44.800> so<00:07:45.800> that's<00:07:45.890> at 00:07:46.060 --> 00:07:46.070 align:start position:0% contract looks like so that's at 00:07:46.070 --> 00:07:52.660 align:start position:0% contract looks like so that's at localhost<00:07:46.550> 3000<00:07:49.210> and<00:07:50.210> p.m.<00:07:51.160> so<00:07:52.160> what<00:07:52.280> block<00:07:52.460> is 00:07:52.660 --> 00:07:52.670 align:start position:0% localhost 3000 and p.m. so what block is 00:07:52.670 --> 00:07:54.810 align:start position:0% localhost 3000 and p.m. so what block is done<00:07:52.850> here<00:07:53.120> is<00:07:53.240> scaffolded<00:07:53.840> a<00:07:53.960> user<00:07:54.200> interface 00:07:54.810 --> 00:07:54.820 align:start position:0% done here is scaffolded a user interface 00:07:54.820 --> 00:07:57.280 align:start position:0% done here is scaffolded a user interface for<00:07:55.820> this<00:07:55.970> contract<00:07:56.420> it's<00:07:56.690> automatically 00:07:57.280 --> 00:07:57.290 align:start position:0% for this contract it's automatically 00:07:57.290 --> 00:07:59.920 align:start position:0% for this contract it's automatically generated<00:07:57.860> and<00:07:58.370> we<00:07:59.120> can<00:07:59.300> see<00:07:59.420> that<00:07:59.600> hey<00:07:59.780> we've 00:07:59.920 --> 00:07:59.930 align:start position:0% generated and we can see that hey we've 00:07:59.930 --> 00:08:02.530 align:start position:0% generated and we can see that hey we've compiled<00:08:00.350> the<00:08:00.440> contract<00:08:01.010> but<00:08:01.670> I<00:08:01.970> don't<00:08:02.390> have<00:08:02.480> a 00:08:02.530 --> 00:08:02.540 align:start position:0% compiled the contract but I don't have a 00:08:02.540 --> 00:08:05.020 align:start position:0% compiled the contract but I don't have a wallet<00:08:02.720> yet<00:08:03.020> and<00:08:03.320> I<00:08:04.250> still<00:08:04.490> need<00:08:04.580> to<00:08:04.730> upload 00:08:05.020 --> 00:08:05.030 align:start position:0% wallet yet and I still need to upload 00:08:05.030 --> 00:08:10.500 align:start position:0% wallet yet and I still need to upload the<00:08:05.150> contractors<00:08:06.190> make<00:08:07.190> it<00:08:07.310> bigger<00:08:07.580> yes<00:08:09.460> so 00:08:10.500 --> 00:08:10.510 align:start position:0% the contractors make it bigger yes so 00:08:10.510 --> 00:08:13.180 align:start position:0% the contractors make it bigger yes so block<00:08:11.510> is<00:08:11.660> here<00:08:11.840> to<00:08:11.930> guide<00:08:12.110> you<00:08:12.170> through<00:08:12.710> the 00:08:13.180 --> 00:08:13.190 align:start position:0% block is here to guide you through the 00:08:13.190 --> 00:08:14.890 align:start position:0% block is here to guide you through the process<00:08:13.640> of<00:08:13.730> creating<00:08:13.790> an<00:08:14.180> application<00:08:14.330> it'll 00:08:14.890 --> 00:08:14.900 align:start position:0% process of creating an application it'll 00:08:14.900 --> 00:08:16.600 align:start position:0% process of creating an application it'll remind<00:08:15.110> you<00:08:15.290> about<00:08:15.440> things<00:08:15.740> like<00:08:15.860> deploying 00:08:16.600 --> 00:08:16.610 align:start position:0% remind you about things like deploying 00:08:16.610 --> 00:08:18.670 align:start position:0% remind you about things like deploying contracts<00:08:17.330> or<00:08:17.510> when<00:08:18.020> you<00:08:18.110> need<00:08:18.260> to<00:08:18.350> upload<00:08:18.560> a 00:08:18.670 --> 00:08:18.680 align:start position:0% contracts or when you need to upload a 00:08:18.680 --> 00:08:20.260 align:start position:0% contracts or when you need to upload a new<00:08:18.770> version<00:08:19.040> of<00:08:19.250> your<00:08:19.370> contract<00:08:19.850> after<00:08:20.150> it's 00:08:20.260 --> 00:08:20.270 align:start position:0% new version of your contract after it's 00:08:20.270 --> 00:08:22.650 align:start position:0% new version of your contract after it's been<00:08:20.390> uploaded<00:08:20.660> up<00:08:21.050> updated<00:08:21.770> excuse<00:08:22.190> me 00:08:22.650 --> 00:08:22.660 align:start position:0% been uploaded up updated excuse me 00:08:22.660 --> 00:08:27.400 align:start position:0% been uploaded up updated excuse me okay<00:08:25.120> so<00:08:26.120> I'm<00:08:26.180> gonna<00:08:26.270> go<00:08:26.420> ahead<00:08:26.480> and<00:08:26.570> generate 00:08:27.400 --> 00:08:27.410 align:start position:0% okay so I'm gonna go ahead and generate 00:08:27.410 --> 00:08:33.800 align:start position:0% okay so I'm gonna go ahead and generate a<00:08:27.440> key 00:08:33.800 --> 00:08:33.810 align:start position:0% 00:08:33.810 --> 00:08:38.100 align:start position:0% got<00:08:34.810> a<00:08:34.840> network<00:08:35.140> there<00:08:35.380> we<00:08:35.440> go<00:08:36.930> now<00:08:37.930> I'm<00:08:38.020> gonna 00:08:38.100 --> 00:08:38.110 align:start position:0% got a network there we go now I'm gonna 00:08:38.110 --> 00:08:49.160 align:start position:0% got a network there we go now I'm gonna go<00:08:38.340> upload<00:08:39.340> this<00:08:39.729> contract 00:08:49.160 --> 00:08:49.170 align:start position:0% 00:08:49.170 --> 00:08:55.230 align:start position:0% all<00:08:50.170> right<00:08:50.760> and<00:08:51.760> i<00:08:51.940> refresh<00:08:52.570> this<00:08:52.750> page<00:08:54.240> you 00:08:55.230 --> 00:08:55.240 align:start position:0% all right and i refresh this page you 00:08:55.240 --> 00:08:58.290 align:start position:0% all right and i refresh this page you see<00:08:55.270> it<00:08:55.450> as<00:08:55.540> an<00:08:55.660> address<00:08:55.960> now<00:08:57.089> checking<00:08:58.089> the 00:08:58.290 --> 00:08:58.300 align:start position:0% see it as an address now checking the 00:08:58.300 --> 00:09:01.230 align:start position:0% see it as an address now checking the password<00:08:58.690> in<00:08:59.580> we've<00:09:00.580> got<00:09:00.730> some<00:09:00.910> data<00:09:01.060> in 00:09:01.230 --> 00:09:01.240 align:start position:0% password in we've got some data in 00:09:01.240 --> 00:09:02.820 align:start position:0% password in we've got some data in storage<00:09:01.630> you<00:09:01.810> can<00:09:01.930> see<00:09:02.080> these<00:09:02.200> addresses<00:09:02.680> have 00:09:02.820 --> 00:09:02.830 align:start position:0% storage you can see these addresses have 00:09:02.830 --> 00:09:04.350 align:start position:0% storage you can see these addresses have not<00:09:02.980> been<00:09:03.250> filled<00:09:03.520> in<00:09:03.640> cuz<00:09:03.850> we<00:09:03.970> haven't<00:09:04.180> called 00:09:04.350 --> 00:09:04.360 align:start position:0% not been filled in cuz we haven't called 00:09:04.360 --> 00:09:06.269 align:start position:0% not been filled in cuz we haven't called the<00:09:04.480> setup<00:09:04.750> function<00:09:05.170> just<00:09:05.290> yet 00:09:06.269 --> 00:09:06.279 align:start position:0% the setup function just yet 00:09:06.279 --> 00:09:08.760 align:start position:0% the setup function just yet I<00:09:06.339> have<00:09:07.120> about<00:09:07.810> a<00:09:07.870> thousand<00:09:08.350> ether<00:09:08.560> in<00:09:08.680> the 00:09:08.760 --> 00:09:08.770 align:start position:0% I have about a thousand ether in the 00:09:08.770 --> 00:09:11.880 align:start position:0% I have about a thousand ether in the bank<00:09:09.010> the<00:09:09.250> contract<00:09:09.730> has<00:09:09.880> zero<00:09:10.209> ether<00:09:10.570> so<00:09:11.260> and 00:09:11.880 --> 00:09:11.890 align:start position:0% bank the contract has zero ether so and 00:09:11.890 --> 00:09:13.650 align:start position:0% bank the contract has zero ether so and assume<00:09:12.130> the<00:09:12.250> contract<00:09:12.670> some<00:09:12.790> ether<00:09:12.910> and<00:09:13.360> do 00:09:13.650 --> 00:09:13.660 align:start position:0% assume the contract some ether and do 00:09:13.660 --> 00:09:20.070 align:start position:0% assume the contract some ether and do the<00:09:13.779> setup<00:09:17.430> okay<00:09:18.430> you<00:09:18.940> can<00:09:19.089> see<00:09:19.240> that<00:09:19.390> Marley 00:09:20.070 --> 00:09:20.080 align:start position:0% the setup okay you can see that Marley 00:09:20.080 --> 00:09:22.260 align:start position:0% the setup okay you can see that Marley now<00:09:20.230> is<00:09:20.290> an<00:09:20.440> address<00:09:20.740> as<00:09:21.070> this<00:09:21.310> Victor<00:09:21.670> Jim<00:09:22.120> and 00:09:22.260 --> 00:09:22.270 align:start position:0% now is an address as this Victor Jim and 00:09:22.270 --> 00:09:24.090 align:start position:0% now is an address as this Victor Jim and I<00:09:22.330> and<00:09:22.540> the<00:09:22.870> contract<00:09:23.230> doesn't<00:09:23.380> any 00:09:24.090 --> 00:09:24.100 align:start position:0% I and the contract doesn't any 00:09:24.100 --> 00:09:27.300 align:start position:0% I and the contract doesn't any so<00:09:25.060> here's<00:09:26.050> Marley's<00:09:26.410> address<00:09:26.740> there's 00:09:27.300 --> 00:09:27.310 align:start position:0% so here's Marley's address there's 00:09:27.310 --> 00:09:28.920 align:start position:0% so here's Marley's address there's nothing<00:09:27.640> at<00:09:27.790> it<00:09:27.940> this<00:09:28.240> is<00:09:28.390> actually<00:09:28.510> what<00:09:28.839> we 00:09:28.920 --> 00:09:28.930 align:start position:0% nothing at it this is actually what we 00:09:28.930 --> 00:09:32.490 align:start position:0% nothing at it this is actually what we want<00:09:29.190> and<00:09:30.190> I'm<00:09:30.820> about<00:09:31.060> to<00:09:31.420> carry<00:09:32.110> out<00:09:32.320> the 00:09:32.490 --> 00:09:32.500 align:start position:0% want and I'm about to carry out the 00:09:32.500 --> 00:09:47.869 align:start position:0% want and I'm about to carry out the dividend 00:09:47.869 --> 00:09:47.879 align:start position:0% 00:09:47.879 --> 00:09:51.139 align:start position:0% there<00:09:48.879> we<00:09:48.970> go<00:09:49.319> all<00:09:50.319> right<00:09:50.379> so<00:09:50.709> if<00:09:50.800> I<00:09:50.860> check<00:09:51.069> this 00:09:51.139 --> 00:09:51.149 align:start position:0% there we go all right so if I check this 00:09:51.149 --> 00:09:53.720 align:start position:0% there we go all right so if I check this Marley<00:09:52.149> should<00:09:52.420> have<00:09:52.600> a<00:09:52.629> balance<00:09:52.990> now 00:09:53.720 --> 00:09:53.730 align:start position:0% Marley should have a balance now 00:09:53.730 --> 00:09:56.280 align:start position:0% Marley should have a balance now and<00:09:54.730> there<00:09:54.850> it<00:09:54.940> is<00:09:55.089> it's<00:09:55.629> in<00:09:55.810> a<00:09:55.870> way<00:09:55.990> you<00:09:56.050> can 00:09:56.280 --> 00:09:56.290 align:start position:0% and there it is it's in a way you can 00:09:56.290 --> 00:09:59.189 align:start position:0% and there it is it's in a way you can see<00:09:56.470> you<00:09:56.529> got<00:09:56.680> 70%<00:09:57.540> we<00:09:58.540> should<00:09:58.720> label<00:09:58.899> those 00:09:59.189 --> 00:09:59.199 align:start position:0% see you got 70% we should label those 00:09:59.199 --> 00:10:01.860 align:start position:0% see you got 70% we should label those units<00:09:59.560> a<00:09:59.620> little<00:09:59.829> bit<00:09:59.949> better<00:10:00.100> but<00:10:00.750> there<00:10:01.750> we 00:10:01.860 --> 00:10:01.870 align:start position:0% units a little bit better but there we 00:10:01.870 --> 00:10:04.889 align:start position:0% units a little bit better but there we go<00:10:02.019> we<00:10:02.889> didn't<00:10:03.040> need<00:10:03.160> any<00:10:03.310> lawyers<00:10:03.720> we<00:10:04.720> stood 00:10:04.889 --> 00:10:04.899 align:start position:0% go we didn't need any lawyers we stood 00:10:04.899 --> 00:10:10.110 align:start position:0% go we didn't need any lawyers we stood up<00:10:05.019> the<00:10:05.310> the<00:10:06.310> revenue<00:10:06.699> split<00:10:08.879> there<00:10:09.879> the<00:10:09.970> back 00:10:10.110 --> 00:10:10.120 align:start position:0% up the the revenue split there the back 00:10:10.120 --> 00:10:13.889 align:start position:0% up the the revenue split there the back in<00:10:10.899> the<00:10:11.019> back<00:10:11.230> ah<00:10:11.470> well<00:10:12.300> we<00:10:13.300> let<00:10:13.480> him<00:10:13.569> in<00:10:13.720> for 00:10:13.889 --> 00:10:13.899 align:start position:0% in the back ah well we let him in for 00:10:13.899 --> 00:10:16.230 align:start position:0% in the back ah well we let him in for this<00:10:14.019> conference<00:10:14.350> not<00:10:14.829> the<00:10:14.980> next<00:10:15.160> one<00:10:15.339> anyway 00:10:16.230 --> 00:10:16.240 align:start position:0% this conference not the next one anyway 00:10:16.240 --> 00:10:17.850 align:start position:0% this conference not the next one anyway so<00:10:16.629> that's<00:10:16.750> how<00:10:16.870> you<00:10:16.930> can<00:10:17.110> get<00:10:17.560> up<00:10:17.680> and<00:10:17.800> running 00:10:17.850 --> 00:10:17.860 align:start position:0% so that's how you can get up and running 00:10:17.860 --> 00:10:19.790 align:start position:0% so that's how you can get up and running in<00:10:18.189> five<00:10:18.639> minutes<00:10:18.970> and<00:10:19.120> build<00:10:19.269> your<00:10:19.360> first<00:10:19.600> app 00:10:19.790 --> 00:10:19.800 align:start position:0% in five minutes and build your first app 00:10:19.800 --> 00:10:30.659 align:start position:0% in five minutes and build your first app with<00:10:20.800> block<00:10:21.100> on<00:10:21.370> block<00:10:21.699> ups<00:10:21.939> ryan<00:10:22.810> later<00:10:23.079> will 00:10:30.659 --> 00:10:30.669 align:start position:0% 00:10:30.669 --> 00:10:34.329 align:start position:0% so<00:10:31.899> block<00:10:32.899> is<00:10:33.079> a<00:10:33.109> wrapper<00:10:33.409> around<00:10:33.559> block<00:10:34.069> apps 00:10:34.329 --> 00:10:34.339 align:start position:0% so block is a wrapper around block apps 00:10:34.339 --> 00:10:37.769 align:start position:0% so block is a wrapper around block apps jas<00:10:34.879> which<00:10:35.239> is<00:10:35.449> our<00:10:36.129> every<00:10:37.129> purpose 00:10:37.769 --> 00:10:37.779 align:start position:0% jas which is our every purpose 00:10:37.779 --> 00:10:42.009 align:start position:0% jas which is our every purpose JavaScript<00:10:38.779> API<00:10:39.999> so<00:10:40.999> blocked<00:10:41.269> takes<00:10:41.809> care<00:10:41.989> of 00:10:42.009 --> 00:10:42.019 align:start position:0% JavaScript API so blocked takes care of 00:10:42.019 --> 00:10:43.629 align:start position:0% JavaScript API so blocked takes care of the<00:10:42.109> scaffolding<00:10:42.649> and<00:10:42.799> the<00:10:42.859> onboarding<00:10:43.369> but 00:10:43.629 --> 00:10:43.639 align:start position:0% the scaffolding and the onboarding but 00:10:43.639 --> 00:10:45.939 align:start position:0% the scaffolding and the onboarding but block<00:10:43.969> XJS<00:10:44.479> you<00:10:44.629> can<00:10:44.779> drop<00:10:45.019> into<00:10:45.229> any<00:10:45.379> project 00:10:45.939 --> 00:10:45.949 align:start position:0% block XJS you can drop into any project 00:10:45.949 --> 00:10:47.739 align:start position:0% block XJS you can drop into any project that<00:10:46.129> you<00:10:46.279> already<00:10:46.489> have<00:10:46.759> so<00:10:46.789> maybe<00:10:47.509> when<00:10:47.659> you 00:10:47.739 --> 00:10:47.749 align:start position:0% that you already have so maybe when you 00:10:47.749 --> 00:10:49.059 align:start position:0% that you already have so maybe when you do<00:10:47.899> something<00:10:48.079> more<00:10:48.349> complicated<00:10:48.649> do<00:10:49.009> you 00:10:49.059 --> 00:10:49.069 align:start position:0% do something more complicated do you 00:10:49.069 --> 00:11:06.669 align:start position:0% do something more complicated do you want<00:10:49.219> to<00:10:49.279> use<00:10:49.399> block<00:10:49.639> XJS<00:10:50.589> thanks<00:10:51.589> Victor<00:11:05.679> so 00:11:06.669 --> 00:11:06.679 align:start position:0% want to use block XJS thanks Victor so 00:11:06.679 --> 00:11:08.529 align:start position:0% want to use block XJS thanks Victor so as<00:11:06.799> you<00:11:06.949> can<00:11:07.099> see<00:11:07.159> black<00:11:07.579> ops<00:11:07.789> trudeau<00:11:08.149> is 00:11:08.529 --> 00:11:08.539 align:start position:0% as you can see black ops trudeau is 00:11:08.539 --> 00:11:11.679 align:start position:0% as you can see black ops trudeau is designed<00:11:09.259> for<00:11:09.529> very<00:11:10.039> very<00:11:10.429> rapid<00:11:10.969> deployment 00:11:11.679 --> 00:11:11.689 align:start position:0% designed for very very rapid deployment 00:11:11.689 --> 00:11:14.289 align:start position:0% designed for very very rapid deployment and<00:11:12.109> development<00:11:12.549> some<00:11:13.549> of<00:11:13.579> the<00:11:13.699> key<00:11:13.879> features 00:11:14.289 --> 00:11:14.299 align:start position:0% and development some of the key features 00:11:14.299 --> 00:11:17.339 align:start position:0% and development some of the key features are<00:11:14.509> that<00:11:14.689> it's<00:11:15.019> designed<00:11:15.619> for<00:11:15.799> building 00:11:17.339 --> 00:11:17.349 align:start position:0% are that it's designed for building 00:11:17.349 --> 00:11:19.509 align:start position:0% are that it's designed for building customizable<00:11:18.349> private<00:11:18.919> a<00:11:19.069> theorem 00:11:19.509 --> 00:11:19.519 align:start position:0% customizable private a theorem 00:11:19.519 --> 00:11:22.659 align:start position:0% customizable private a theorem compatible<00:11:20.209> networks<00:11:20.859> you<00:11:21.859> do<00:11:22.069> rapid 00:11:22.659 --> 00:11:22.669 align:start position:0% compatible networks you do rapid 00:11:22.669 --> 00:11:24.849 align:start position:0% compatible networks you do rapid deployment<00:11:23.179> and<00:11:23.599> interest<00:11:23.989> on<00:11:24.169> existing 00:11:24.849 --> 00:11:24.859 align:start position:0% deployment and interest on existing 00:11:24.859 --> 00:11:27.879 align:start position:0% deployment and interest on existing infrastructure<00:11:25.519> like<00:11:25.819> asura<00:11:26.239> as<00:11:27.169> Marly 00:11:27.879 --> 00:11:27.889 align:start position:0% infrastructure like asura as Marly 00:11:27.889 --> 00:11:29.259 align:start position:0% infrastructure like asura as Marly mentioned<00:11:28.279> coming<00:11:28.789> suits<00:11:29.059> in<00:11:29.179> the 00:11:29.259 --> 00:11:29.269 align:start position:0% mentioned coming suits in the 00:11:29.269 --> 00:11:31.449 align:start position:0% mentioned coming suits in the marketplace<00:11:29.779> will<00:11:30.229> be<00:11:30.379> one-click<00:11:30.859> deployment 00:11:31.449 --> 00:11:31.459 align:start position:0% marketplace will be one-click deployment 00:11:31.459 --> 00:11:34.539 align:start position:0% marketplace will be one-click deployment it<00:11:32.449> has<00:11:32.689> a<00:11:32.719> restful<00:11:33.289> api<00:11:33.589> which<00:11:34.039> is<00:11:34.189> designed 00:11:34.539 --> 00:11:34.549 align:start position:0% it has a restful api which is designed 00:11:34.549 --> 00:11:37.119 align:start position:0% it has a restful api which is designed for<00:11:34.729> integration<00:11:35.239> with<00:11:35.629> existing<00:11:36.129> services 00:11:37.119 --> 00:11:37.129 align:start position:0% for integration with existing services 00:11:37.129 --> 00:11:41.439 align:start position:0% for integration with existing services and<00:11:37.459> devices<00:11:37.729> and<00:11:38.829> one<00:11:39.829> thing<00:11:40.099> is<00:11:40.339> it<00:11:40.579> scales 00:11:41.439 --> 00:11:41.449 align:start position:0% and devices and one thing is it scales 00:11:41.449 --> 00:11:44.829 align:start position:0% and devices and one thing is it scales easily<00:11:42.289> from<00:11:42.649> small<00:11:43.249> private<00:11:43.849> sandbox 00:11:44.829 --> 00:11:44.839 align:start position:0% easily from small private sandbox 00:11:44.839 --> 00:11:47.289 align:start position:0% easily from small private sandbox deployments<00:11:45.499> into<00:11:46.129> multiple<00:11:46.579> consortium 00:11:47.289 --> 00:11:47.299 align:start position:0% deployments into multiple consortium 00:11:47.299 --> 00:11:50.769 align:start position:0% deployments into multiple consortium deployments<00:11:47.899> and<00:11:48.189> even<00:11:49.419> elements<00:11:50.419> of<00:11:50.569> the 00:11:50.769 --> 00:11:50.779 align:start position:0% deployments and even elements of the 00:11:50.779 --> 00:11:52.719 align:start position:0% deployments and even elements of the public<00:11:51.199> of<00:11:51.349> your<00:11:51.529> in<00:11:51.649> blockchain<00:11:52.189> it's 00:11:52.719 --> 00:11:52.729 align:start position:0% public of your in blockchain it's 00:11:52.729 --> 00:11:55.629 align:start position:0% public of your in blockchain it's write-once<00:11:53.419> use<00:11:54.199> on<00:11:54.529> any<00:11:54.829> network<00:11:55.099> that<00:11:55.489> you 00:11:55.629 --> 00:11:55.639 align:start position:0% write-once use on any network that you 00:11:55.639 --> 00:11:59.499 align:start position:0% write-once use on any network that you want<00:11:55.879> and<00:11:56.179> all<00:11:57.169> of<00:11:57.439> this<00:11:57.619> is<00:11:57.889> built<00:11:58.309> on<00:11:58.669> the 00:11:59.499 --> 00:11:59.509 align:start position:0% want and all of this is built on the 00:11:59.509 --> 00:12:01.329 align:start position:0% want and all of this is built on the technology<00:12:00.049> we<00:12:00.079> developed<00:12:00.649> for<00:12:00.829> the<00:12:00.859> etherium 00:12:01.329 --> 00:12:01.339 align:start position:0% technology we developed for the etherium 00:12:01.339 --> 00:12:03.729 align:start position:0% technology we developed for the etherium haskell<00:12:01.819> implementation<00:12:02.539> and<00:12:02.779> to<00:12:03.289> talk<00:12:03.470> about 00:12:03.729 --> 00:12:03.739 align:start position:0% haskell implementation and to talk about 00:12:03.739 --> 00:12:05.139 align:start position:0% haskell implementation and to talk about that<00:12:03.919> I'm<00:12:04.189> going<00:12:04.369> troduce<00:12:04.759> my<00:12:04.999> other 00:12:05.139 --> 00:12:05.149 align:start position:0% that I'm going troduce my other 00:12:05.149 --> 00:12:08.259 align:start position:0% that I'm going troduce my other co-founder<00:12:05.839> James<00:12:06.499> for<00:12:06.739> Mazda<00:12:06.889> your<00:12:07.129> PhD<00:12:07.999> and 00:12:08.259 --> 00:12:08.269 align:start position:0% co-founder James for Mazda your PhD and 00:12:08.269 --> 00:12:15.390 align:start position:0% co-founder James for Mazda your PhD and creator<00:12:08.989> of<00:12:09.079> SSL<00:12:09.919> VPN 00:12:15.390 --> 00:12:15.400 align:start position:0% 00:12:15.400 --> 00:12:21.090 align:start position:0% Thank<00:12:16.400> You<00:12:16.490> Victor<00:12:17.470> so<00:12:18.470> about<00:12:19.370> a<00:12:19.430> year<00:12:19.550> ago<00:12:19.760> I 00:12:21.090 --> 00:12:21.100 align:start position:0% Thank You Victor so about a year ago I 00:12:21.100 --> 00:12:23.620 align:start position:0% Thank You Victor so about a year ago I Karen<00:12:22.100> actually<00:12:22.220> contacted<00:12:22.940> me<00:12:22.970> and<00:12:23.270> I 00:12:23.620 --> 00:12:23.630 align:start position:0% Karen actually contacted me and I 00:12:23.630 --> 00:12:24.610 align:start position:0% Karen actually contacted me and I learned<00:12:23.870> a<00:12:23.990> little<00:12:24.140> bit<00:12:24.290> about 00:12:24.610 --> 00:12:24.620 align:start position:0% learned a little bit about 00:12:24.620 --> 00:12:26.710 align:start position:0% learned a little bit about etherium<00:12:25.190> and<00:12:25.340> I<00:12:25.400> became<00:12:25.820> fascinated<00:12:26.120> right 00:12:26.710 --> 00:12:26.720 align:start position:0% etherium and I became fascinated right 00:12:26.720 --> 00:12:29.530 align:start position:0% etherium and I became fascinated right away<00:12:26.930> with<00:12:27.260> the<00:12:27.410> theorem<00:12:27.650> and<00:12:27.980> I<00:12:28.210> went<00:12:29.210> out<00:12:29.360> and 00:12:29.530 --> 00:12:29.540 align:start position:0% away with the theorem and I went out and 00:12:29.540 --> 00:12:31.060 align:start position:0% away with the theorem and I went out and started<00:12:29.750> reading<00:12:30.020> everything<00:12:30.260> about<00:12:30.740> it<00:12:30.920> and 00:12:31.060 --> 00:12:31.070 align:start position:0% started reading everything about it and 00:12:31.070 --> 00:12:34.000 align:start position:0% started reading everything about it and I<00:12:31.130> immediately<00:12:31.250> wanted<00:12:31.940> to<00:12:32.680> dig<00:12:33.680> in<00:12:33.830> and 00:12:34.000 --> 00:12:34.010 align:start position:0% I immediately wanted to dig in and 00:12:34.010 --> 00:12:36.400 align:start position:0% I immediately wanted to dig in and understand<00:12:34.490> how<00:12:34.670> it<00:12:34.850> worked<00:12:35.120> and<00:12:35.600> for<00:12:36.050> me<00:12:36.140> the 00:12:36.400 --> 00:12:36.410 align:start position:0% understand how it worked and for me the 00:12:36.410 --> 00:12:39.220 align:start position:0% understand how it worked and for me the natural<00:12:36.890> choice<00:12:37.370> of<00:12:37.700> a<00:12:37.820> language<00:12:38.240> to<00:12:38.480> use<00:12:38.660> to 00:12:39.220 --> 00:12:39.230 align:start position:0% natural choice of a language to use to 00:12:39.230 --> 00:12:43.660 align:start position:0% natural choice of a language to use to work<00:12:39.980> with<00:12:40.160> aetherium<00:12:40.640> was<00:12:41.150> tasco<00:12:42.130> I've<00:12:43.130> been 00:12:43.660 --> 00:12:43.670 align:start position:0% work with aetherium was tasco I've been 00:12:43.670 --> 00:12:46.300 align:start position:0% work with aetherium was tasco I've been using<00:12:43.940> Haskell<00:12:44.630> for<00:12:44.930> about<00:12:45.620> five<00:12:45.920> years<00:12:46.160> now 00:12:46.300 --> 00:12:46.310 align:start position:0% using Haskell for about five years now 00:12:46.310 --> 00:12:49.750 align:start position:0% using Haskell for about five years now and<00:12:46.820> it's<00:12:47.830> over<00:12:48.830> that<00:12:48.980> time<00:12:49.160> become<00:12:49.460> my 00:12:49.750 --> 00:12:49.760 align:start position:0% and it's over that time become my 00:12:49.760 --> 00:12:51.670 align:start position:0% and it's over that time become my favorite<00:12:50.240> language<00:12:50.390> it's<00:12:51.290> got<00:12:51.440> a<00:12:51.470> lot<00:12:51.650> of 00:12:51.670 --> 00:12:51.680 align:start position:0% favorite language it's got a lot of 00:12:51.680 --> 00:12:55.990 align:start position:0% favorite language it's got a lot of features<00:12:52.160> that<00:12:52.190> are<00:12:53.320> extremely<00:12:54.320> nice<00:12:55.000> first 00:12:55.990 --> 00:12:56.000 align:start position:0% features that are extremely nice first 00:12:56.000 --> 00:12:59.110 align:start position:0% features that are extremely nice first of<00:12:56.180> all<00:12:56.270> as<00:12:56.480> you<00:12:56.660> heard<00:12:57.140> yesterday<00:12:57.910> Haskell<00:12:58.910> is 00:12:59.110 --> 00:12:59.120 align:start position:0% of all as you heard yesterday Haskell is 00:12:59.120 --> 00:13:01.290 align:start position:0% of all as you heard yesterday Haskell is a<00:12:59.150> functional<00:12:59.960> programming<00:13:00.410> language<00:13:00.920> and 00:13:01.290 --> 00:13:01.300 align:start position:0% a functional programming language and 00:13:01.300 --> 00:13:03.700 align:start position:0% a functional programming language and the<00:13:02.300> thing<00:13:02.600> about<00:13:02.780> a<00:13:02.840> functional<00:13:03.320> programming 00:13:03.700 --> 00:13:03.710 align:start position:0% the thing about a functional programming 00:13:03.710 --> 00:13:05.890 align:start position:0% the thing about a functional programming language<00:13:04.310> is<00:13:04.490> that<00:13:04.520> the<00:13:04.730> specification<00:13:05.660> is 00:13:05.890 --> 00:13:05.900 align:start position:0% language is that the specification is 00:13:05.900 --> 00:13:08.110 align:start position:0% language is that the specification is the<00:13:06.110> executable<00:13:06.680> the<00:13:07.040> code<00:13:07.460> that<00:13:07.730> you<00:13:07.850> write 00:13:08.110 --> 00:13:08.120 align:start position:0% the executable the code that you write 00:13:08.120 --> 00:13:11.350 align:start position:0% the executable the code that you write with<00:13:08.770> Haskell<00:13:09.770> looks<00:13:10.370> a<00:13:10.490> lot<00:13:10.700> like<00:13:10.880> the 00:13:11.350 --> 00:13:11.360 align:start position:0% with Haskell looks a lot like the 00:13:11.360 --> 00:13:13.500 align:start position:0% with Haskell looks a lot like the description<00:13:12.110> of<00:13:12.290> the<00:13:12.470> code<00:13:12.710> that<00:13:12.980> you<00:13:13.130> are 00:13:13.500 --> 00:13:13.510 align:start position:0% description of the code that you are 00:13:13.510 --> 00:13:15.430 align:start position:0% description of the code that you are writing 00:13:15.430 --> 00:13:15.440 align:start position:0% writing 00:13:15.440 --> 00:13:17.020 align:start position:0% writing second<00:13:16.190> of<00:13:16.250> all<00:13:16.280> it's<00:13:16.580> one<00:13:16.760> of<00:13:16.850> the<00:13:16.910> most 00:13:17.020 --> 00:13:17.030 align:start position:0% second of all it's one of the most 00:13:17.030 --> 00:13:19.990 align:start position:0% second of all it's one of the most strongly<00:13:18.020> statically<00:13:18.800> typed<00:13:19.070> languages<00:13:19.700> that 00:13:19.990 --> 00:13:20.000 align:start position:0% strongly statically typed languages that 00:13:20.000 --> 00:13:23.080 align:start position:0% strongly statically typed languages that exists<00:13:20.600> so<00:13:21.370> generally<00:13:22.370> speaking<00:13:22.400> if<00:13:22.970> it 00:13:23.080 --> 00:13:23.090 align:start position:0% exists so generally speaking if it 00:13:23.090 --> 00:13:26.230 align:start position:0% exists so generally speaking if it compiles<00:13:23.720> it's<00:13:24.680> correct<00:13:25.160> and<00:13:25.490> I've<00:13:25.760> had<00:13:25.940> many 00:13:26.230 --> 00:13:26.240 align:start position:0% compiles it's correct and I've had many 00:13:26.240 --> 00:13:28.090 align:start position:0% compiles it's correct and I've had many experiences<00:13:26.300> over<00:13:27.260> the<00:13:27.290> last<00:13:27.380> year<00:13:27.860> where 00:13:28.090 --> 00:13:28.100 align:start position:0% experiences over the last year where 00:13:28.100 --> 00:13:30.700 align:start position:0% experiences over the last year where I've<00:13:28.580> had<00:13:29.300> to<00:13:29.450> make<00:13:29.600> changes<00:13:29.810> to<00:13:30.050> the<00:13:30.290> code<00:13:30.440> and 00:13:30.700 --> 00:13:30.710 align:start position:0% I've had to make changes to the code and 00:13:30.710 --> 00:13:32.770 align:start position:0% I've had to make changes to the code and I've<00:13:30.800> spent<00:13:31.700> hours<00:13:31.970> ripping<00:13:32.630> it<00:13:32.720> apart 00:13:32.770 --> 00:13:32.780 align:start position:0% I've spent hours ripping it apart 00:13:32.780 --> 00:13:37.300 align:start position:0% I've spent hours ripping it apart rewriting<00:13:33.680> it<00:13:33.800> and<00:13:34.000> and<00:13:35.000> I'm<00:13:36.130> generally<00:13:37.130> very 00:13:37.300 --> 00:13:37.310 align:start position:0% rewriting it and and I'm generally very 00:13:37.310 --> 00:13:38.740 align:start position:0% rewriting it and and I'm generally very surprised<00:13:37.730> at<00:13:37.940> the<00:13:38.060> end<00:13:38.090> of<00:13:38.240> the<00:13:38.300> day<00:13:38.390> once<00:13:38.600> it 00:13:38.740 --> 00:13:38.750 align:start position:0% surprised at the end of the day once it 00:13:38.750 --> 00:13:40.570 align:start position:0% surprised at the end of the day once it compiles<00:13:39.290> it<00:13:39.440> tends<00:13:39.650> to<00:13:39.860> come<00:13:40.010> up<00:13:40.160> and<00:13:40.310> it<00:13:40.400> just 00:13:40.570 --> 00:13:40.580 align:start position:0% compiles it tends to come up and it just 00:13:40.580 --> 00:13:44.830 align:start position:0% compiles it tends to come up and it just works<00:13:40.790> without<00:13:41.090> bugs<00:13:41.420> so<00:13:42.670> and<00:13:43.670> third<00:13:44.630> of<00:13:44.750> all 00:13:44.830 --> 00:13:44.840 align:start position:0% works without bugs so and third of all 00:13:44.840 --> 00:13:48.730 align:start position:0% works without bugs so and third of all it's<00:13:44.990> very<00:13:45.200> performant<00:13:45.770> language<00:13:47.020> so<00:13:48.020> when 00:13:48.730 --> 00:13:48.740 align:start position:0% it's very performant language so when 00:13:48.740 --> 00:13:51.010 align:start position:0% it's very performant language so when you<00:13:48.920> compile<00:13:49.430> Haskell<00:13:50.120> it<00:13:50.270> compiles<00:13:50.750> to 00:13:51.010 --> 00:13:51.020 align:start position:0% you compile Haskell it compiles to 00:13:51.020 --> 00:13:53.140 align:start position:0% you compile Haskell it compiles to Native<00:13:51.440> executables<00:13:52.070> and<00:13:52.250> if<00:13:52.700> you<00:13:52.790> write<00:13:53.000> your 00:13:53.140 --> 00:13:53.150 align:start position:0% Native executables and if you write your 00:13:53.150 --> 00:13:54.790 align:start position:0% Native executables and if you write your Haskell<00:13:53.510> code<00:13:53.660> properly<00:13:53.960> it<00:13:54.350> can<00:13:54.500> run<00:13:54.650> as<00:13:54.770> fast 00:13:54.790 --> 00:13:54.800 align:start position:0% Haskell code properly it can run as fast 00:13:54.800 --> 00:13:59.920 align:start position:0% Haskell code properly it can run as fast as<00:13:55.190> C<00:13:55.460> so<00:13:57.940> generally<00:13:58.940> speaking<00:13:58.970> if<00:13:59.630> you<00:13:59.750> want 00:13:59.920 --> 00:13:59.930 align:start position:0% as C so generally speaking if you want 00:13:59.930 --> 00:14:01.420 align:start position:0% as C so generally speaking if you want to<00:14:00.050> write<00:14:00.230> something<00:14:00.530> and<00:14:00.800> you<00:14:01.040> just<00:14:01.070> want<00:14:01.400> to 00:14:01.420 --> 00:14:01.430 align:start position:0% to write something and you just want to 00:14:01.430 --> 00:14:02.740 align:start position:0% to write something and you just want to make<00:14:01.610> sure<00:14:01.640> that<00:14:01.940> it<00:14:02.060> works<00:14:02.300> and<00:14:02.480> it<00:14:02.600> works 00:14:02.740 --> 00:14:02.750 align:start position:0% make sure that it works and it works 00:14:02.750 --> 00:14:05.530 align:start position:0% make sure that it works and it works fast<00:14:03.050> Haskell<00:14:03.710> is<00:14:03.890> your<00:14:04.160> language<00:14:04.360> and<00:14:05.360> it's 00:14:05.530 --> 00:14:05.540 align:start position:0% fast Haskell is your language and it's 00:14:05.540 --> 00:14:07.030 align:start position:0% fast Haskell is your language and it's been<00:14:05.810> as<00:14:05.990> you<00:14:06.140> can<00:14:06.290> see<00:14:06.440> here<00:14:06.590> we<00:14:06.680> put<00:14:06.830> a<00:14:06.860> few 00:14:07.030 --> 00:14:07.040 align:start position:0% been as you can see here we put a few 00:14:07.040 --> 00:14:10.300 align:start position:0% been as you can see here we put a few examples<00:14:07.550> of<00:14:08.560> companies<00:14:09.560> that<00:14:09.830> have<00:14:10.070> been 00:14:10.300 --> 00:14:10.310 align:start position:0% examples of companies that have been 00:14:10.310 --> 00:14:15.480 align:start position:0% examples of companies that have been using<00:14:10.490> it<00:14:10.700> in<00:14:10.790> the<00:14:10.940> last<00:14:11.120> few<00:14:11.390> years 00:14:15.480 --> 00:14:15.490 align:start position:0% 00:14:15.490 --> 00:14:17.710 align:start position:0% let<00:14:16.490> me<00:14:16.580> talk<00:14:16.760> just<00:14:16.970> a<00:14:17.120> moment<00:14:17.270> about<00:14:17.480> the 00:14:17.710 --> 00:14:17.720 align:start position:0% let me talk just a moment about the 00:14:17.720 --> 00:14:21.490 align:start position:0% let me talk just a moment about the architecture<00:14:18.170> of<00:14:18.320> Strato<00:14:18.649> so<00:14:19.580> Strato<00:14:20.360> as<00:14:21.230> you 00:14:21.490 --> 00:14:21.500 align:start position:0% architecture of Strato so Strato as you 00:14:21.500 --> 00:14:24.340 align:start position:0% architecture of Strato so Strato as you can<00:14:21.680> see<00:14:21.920> it's<00:14:22.100> from<00:14:22.730> the<00:14:22.880> beginning<00:14:23.240> we<00:14:23.630> wrote 00:14:24.340 --> 00:14:24.350 align:start position:0% can see it's from the beginning we wrote 00:14:24.350 --> 00:14:28.810 align:start position:0% can see it's from the beginning we wrote strata<00:14:24.740> to<00:14:24.950> be<00:14:25.040> fully<00:14:25.660> modular<00:14:26.660> eyes<00:14:27.110> and<00:14:27.820> in 00:14:28.810 --> 00:14:28.820 align:start position:0% strata to be fully modular eyes and in 00:14:28.820 --> 00:14:31.800 align:start position:0% strata to be fully modular eyes and in the<00:14:29.029> center<00:14:29.480> we<00:14:29.690> have<00:14:29.839> a<00:14:30.320> sequel<00:14:30.770> database<00:14:31.160> and 00:14:31.800 --> 00:14:31.810 align:start position:0% the center we have a sequel database and 00:14:31.810 --> 00:14:34.570 align:start position:0% the center we have a sequel database and around<00:14:32.810> that<00:14:33.020> sequel<00:14:33.380> database<00:14:33.770> we<00:14:33.950> have<00:14:34.100> many 00:14:34.570 --> 00:14:34.580 align:start position:0% around that sequel database we have many 00:14:34.580 --> 00:14:39.790 align:start position:0% around that sequel database we have many pluggable<00:14:35.450> modules<00:14:37.930> for<00:14:38.930> instance<00:14:39.380> the<00:14:39.529> VM 00:14:39.790 --> 00:14:39.800 align:start position:0% pluggable modules for instance the VM 00:14:39.800 --> 00:14:42.639 align:start position:0% pluggable modules for instance the VM itself<00:14:39.950> is<00:14:40.370> just<00:14:40.670> one<00:14:40.970> process<00:14:41.690> that<00:14:41.720> runs<00:14:42.230> and 00:14:42.639 --> 00:14:42.649 align:start position:0% itself is just one process that runs and 00:14:42.649 --> 00:14:44.350 align:start position:0% itself is just one process that runs and it<00:14:42.770> connects<00:14:43.190> grabs<00:14:43.520> the<00:14:43.730> data<00:14:43.940> out<00:14:44.149> of<00:14:44.180> the 00:14:44.350 --> 00:14:44.360 align:start position:0% it connects grabs the data out of the 00:14:44.360 --> 00:14:47.350 align:start position:0% it connects grabs the data out of the database<00:14:44.720> and<00:14:45.190> processes<00:14:46.190> it<00:14:46.370> we<00:14:46.790> have<00:14:46.970> all<00:14:47.209> of 00:14:47.350 --> 00:14:47.360 align:start position:0% database and processes it we have all of 00:14:47.360 --> 00:14:48.880 align:start position:0% database and processes it we have all of our<00:14:47.480> communication<00:14:48.140> to<00:14:48.290> the<00:14:48.380> outside<00:14:48.709> world 00:14:48.880 --> 00:14:48.890 align:start position:0% our communication to the outside world 00:14:48.890 --> 00:14:51.010 align:start position:0% our communication to the outside world are<00:14:49.190> separate<00:14:49.610> pluggable<00:14:50.060> modules<00:14:50.480> we<00:14:50.990> have 00:14:51.010 --> 00:14:51.020 align:start position:0% are separate pluggable modules we have 00:14:51.020 --> 00:14:53.470 align:start position:0% are separate pluggable modules we have analytics<00:14:51.860> that<00:14:52.040> are<00:14:52.160> occurring<00:14:52.580> so<00:14:53.209> forth 00:14:53.470 --> 00:14:53.480 align:start position:0% analytics that are occurring so forth 00:14:53.480 --> 00:14:56.920 align:start position:0% analytics that are occurring so forth but<00:14:54.230> the<00:14:54.529> important<00:14:55.339> thing<00:14:55.880> here<00:14:55.910> was<00:14:56.420> we<00:14:56.660> put 00:14:56.920 --> 00:14:56.930 align:start position:0% but the important thing here was we put 00:14:56.930 --> 00:14:58.540 align:start position:0% but the important thing here was we put sequel<00:14:57.410> in<00:14:57.500> the<00:14:57.560> middle<00:14:57.860> and<00:14:57.980> we<00:14:58.070> chose<00:14:58.310> that 00:14:58.540 --> 00:14:58.550 align:start position:0% sequel in the middle and we chose that 00:14:58.550 --> 00:15:01.690 align:start position:0% sequel in the middle and we chose that deliberately<00:14:59.149> because<00:14:59.570> we<00:15:00.140> wanted<00:15:00.440> Strato<00:15:01.339> to 00:15:01.690 --> 00:15:01.700 align:start position:0% deliberately because we wanted Strato to 00:15:01.700 --> 00:15:04.000 align:start position:0% deliberately because we wanted Strato to be<00:15:01.910> a<00:15:02.209> an<00:15:02.540> architecture<00:15:03.380> that<00:15:03.440> would<00:15:03.680> plug 00:15:04.000 --> 00:15:04.010 align:start position:0% be a an architecture that would plug 00:15:04.010 --> 00:15:07.769 align:start position:0% be a an architecture that would plug right<00:15:04.370> into<00:15:04.660> existing<00:15:05.660> enterprise 00:15:07.769 --> 00:15:07.779 align:start position:0% right into existing enterprise 00:15:07.779 --> 00:15:12.940 align:start position:0% right into existing enterprise environments<00:15:08.779> today<00:15:09.050> so<00:15:11.649> thank<00:15:12.649> you<00:15:12.830> very 00:15:12.940 --> 00:15:12.950 align:start position:0% environments today so thank you very 00:15:12.950 --> 00:15:19.540 align:start position:0% environments today so thank you very much 00:15:19.540 --> 00:15:19.550 align:start position:0% 00:15:19.550 --> 00:15:22.790 align:start position:0% so<00:15:20.550> what<00:15:20.820> one<00:15:21.150> thing<00:15:21.360> about<00:15:21.450> Strato<00:15:22.230> and<00:15:22.500> the 00:15:22.790 --> 00:15:22.800 align:start position:0% so what one thing about Strato and the 00:15:22.800 --> 00:15:24.940 align:start position:0% so what one thing about Strato and the etherium<00:15:23.400> architecture<00:15:24.270> that<00:15:24.450> we've<00:15:24.600> chosen 00:15:24.940 --> 00:15:24.950 align:start position:0% etherium architecture that we've chosen 00:15:24.950 --> 00:15:28.460 align:start position:0% etherium architecture that we've chosen that<00:15:25.950> Jim<00:15:26.220> has<00:15:26.400> created<00:15:26.820> is<00:15:27.200> because<00:15:28.200> of<00:15:28.320> its 00:15:28.460 --> 00:15:28.470 align:start position:0% that Jim has created is because of its 00:15:28.470 --> 00:15:30.950 align:start position:0% that Jim has created is because of its modular<00:15:28.980> nature<00:15:29.160> it's<00:15:29.850> actually<00:15:30.240> completely 00:15:30.950 --> 00:15:30.960 align:start position:0% modular nature it's actually completely 00:15:30.960 --> 00:15:33.380 align:start position:0% modular nature it's actually completely compatible<00:15:31.350> with<00:15:32.220> many<00:15:32.490> of<00:15:32.820> the<00:15:32.940> existing 00:15:33.380 --> 00:15:33.390 align:start position:0% compatible with many of the existing 00:15:33.390 --> 00:15:35.210 align:start position:0% compatible with many of the existing aetherium<00:15:33.780> tools<00:15:34.050> you<00:15:34.620> can<00:15:34.800> spin<00:15:35.010> up<00:15:35.040> a 00:15:35.210 --> 00:15:35.220 align:start position:0% aetherium tools you can spin up a 00:15:35.220 --> 00:15:37.160 align:start position:0% aetherium tools you can spin up a private<00:15:35.610> network<00:15:35.940> and<00:15:36.060> also<00:15:36.570> connected<00:15:37.050> to<00:15:37.140> a 00:15:37.160 --> 00:15:37.170 align:start position:0% private network and also connected to a 00:15:37.170 --> 00:15:40.400 align:start position:0% private network and also connected to a deaf<00:15:37.440> node<00:15:37.710> or<00:15:37.940> C++<00:15:38.940> node<00:15:39.210> you<00:15:39.900> can<00:15:40.110> use 00:15:40.400 --> 00:15:40.410 align:start position:0% deaf node or C++ node you can use 00:15:40.410 --> 00:15:42.080 align:start position:0% deaf node or C++ node you can use front-end<00:15:41.130> tools<00:15:41.430> that<00:15:41.700> are<00:15:41.820> being<00:15:41.970> developed 00:15:42.080 --> 00:15:42.090 align:start position:0% front-end tools that are being developed 00:15:42.090 --> 00:15:44.900 align:start position:0% front-end tools that are being developed all<00:15:42.720> over<00:15:42.990> by<00:15:43.200> the<00:15:43.260> community<00:15:43.830> such<00:15:44.400> as<00:15:44.430> ether 00:15:44.900 --> 00:15:44.910 align:start position:0% all over by the community such as ether 00:15:44.910 --> 00:15:49.040 align:start position:0% all over by the community such as ether camp<00:15:45.150> truffle<00:15:46.080> and<00:15:46.320> embark<00:15:46.710> so<00:15:47.570> really<00:15:48.570> what 00:15:49.040 --> 00:15:49.050 align:start position:0% camp truffle and embark so really what 00:15:49.050 --> 00:15:51.470 align:start position:0% camp truffle and embark so really what what<00:15:49.680> when<00:15:50.130> you<00:15:50.250> use<00:15:50.460> straddle<00:15:51.000> you're<00:15:51.270> not 00:15:51.470 --> 00:15:51.480 align:start position:0% what when you use straddle you're not 00:15:51.480 --> 00:15:56.690 align:start position:0% what when you use straddle you're not restricted<00:15:52.320> to<00:15:52.800> only<00:15:52.830> articles<00:15:53.610> that<00:15:55.640> now<00:15:56.640> the 00:15:56.690 --> 00:15:56.700 align:start position:0% restricted to only articles that now the 00:15:56.700 --> 00:15:59.120 align:start position:0% restricted to only articles that now the one<00:15:56.970> thing<00:15:57.150> is<00:15:57.330> in<00:15:57.600> order<00:15:57.870> to<00:15:58.020> really<00:15:58.410> get<00:15:58.920> a 00:15:59.120 --> 00:15:59.130 align:start position:0% one thing is in order to really get a 00:15:59.130 --> 00:16:01.730 align:start position:0% one thing is in order to really get a theorem<00:15:59.610> applications<00:16:00.300> created<00:16:00.870> simply 00:16:01.730 --> 00:16:01.740 align:start position:0% theorem applications created simply 00:16:01.740 --> 00:16:03.580 align:start position:0% theorem applications created simply having<00:16:02.040> the<00:16:02.130> technology<00:16:02.730> is<00:16:02.850> not<00:16:03.030> enough 00:16:03.580 --> 00:16:03.590 align:start position:0% having the technology is not enough 00:16:03.590 --> 00:16:05.720 align:start position:0% having the technology is not enough education<00:16:04.590> is<00:16:04.710> a<00:16:04.740> big<00:16:05.040> piece<00:16:05.250> of<00:16:05.310> the<00:16:05.580> puzzle 00:16:05.720 --> 00:16:05.730 align:start position:0% education is a big piece of the puzzle 00:16:05.730 --> 00:16:08.210 align:start position:0% education is a big piece of the puzzle and<00:16:06.180> in<00:16:06.900> order<00:16:07.140> to<00:16:07.290> accomplish<00:16:07.620> that<00:16:07.800> we've 00:16:08.210 --> 00:16:08.220 align:start position:0% and in order to accomplish that we've 00:16:08.220 --> 00:16:11.360 align:start position:0% and in order to accomplish that we've been<00:16:08.370> holding<00:16:08.700> a<00:16:08.940> bunch<00:16:09.750> of<00:16:09.960> workshops<00:16:10.370> we 00:16:11.360 --> 00:16:11.370 align:start position:0% been holding a bunch of workshops we 00:16:11.370 --> 00:16:14.720 align:start position:0% been holding a bunch of workshops we call<00:16:11.580> them<00:16:11.760> zero<00:16:12.540> to<00:16:12.690> barge<00:16:13.470> a<00:16:13.650> nap<00:16:13.890> where<00:16:14.490> you 00:16:14.720 --> 00:16:14.730 align:start position:0% call them zero to barge a nap where you 00:16:14.730 --> 00:16:16.400 align:start position:0% call them zero to barge a nap where you come<00:16:14.910> in<00:16:15.060> for<00:16:15.210> a<00:16:15.270> couple<00:16:15.570> hours<00:16:15.660> you<00:16:15.900> start 00:16:16.400 --> 00:16:16.410 align:start position:0% come in for a couple hours you start 00:16:16.410 --> 00:16:18.500 align:start position:0% come in for a couple hours you start playing<00:16:16.590> around<00:16:16.710> with<00:16:16.920> the<00:16:17.100> tools<00:16:17.310> and<00:16:17.700> you 00:16:18.500 --> 00:16:18.510 align:start position:0% playing around with the tools and you 00:16:18.510 --> 00:16:20.180 align:start position:0% playing around with the tools and you walk<00:16:18.810> out<00:16:19.020> having<00:16:19.470> built<00:16:19.710> your<00:16:19.980> first 00:16:20.180 --> 00:16:20.190 align:start position:0% walk out having built your first 00:16:20.190 --> 00:16:22.670 align:start position:0% walk out having built your first blockchain<00:16:20.670> now<00:16:20.820> in<00:16:21.360> addition<00:16:22.290> we've<00:16:22.530> been 00:16:22.670 --> 00:16:22.680 align:start position:0% blockchain now in addition we've been 00:16:22.680 --> 00:16:24.650 align:start position:0% blockchain now in addition we've been actively<00:16:23.100> involved<00:16:23.700> in<00:16:23.970> a<00:16:24.270> series<00:16:24.630> of 00:16:24.650 --> 00:16:24.660 align:start position:0% actively involved in a series of 00:16:24.660 --> 00:16:27.740 align:start position:0% actively involved in a series of hackathons<00:16:25.910> co-sponsored<00:16:26.910> by<00:16:26.940> consensus<00:16:27.630> in 00:16:27.740 --> 00:16:27.750 align:start position:0% hackathons co-sponsored by consensus in 00:16:27.750 --> 00:16:31.040 align:start position:0% hackathons co-sponsored by consensus in the<00:16:27.810> ether<00:16:28.020> camp<00:16:28.260> and<00:16:29.330> without<00:16:30.330> our<00:16:30.360> prompting 00:16:31.040 --> 00:16:31.050 align:start position:0% the ether camp and without our prompting 00:16:31.050 --> 00:16:32.930 align:start position:0% the ether camp and without our prompting it<00:16:31.230> seems<00:16:31.500> that<00:16:31.710> our<00:16:31.950> tools<00:16:32.220> have<00:16:32.460> now<00:16:32.640> gotten 00:16:32.930 --> 00:16:32.940 align:start position:0% it seems that our tools have now gotten 00:16:32.940 --> 00:16:35.210 align:start position:0% it seems that our tools have now gotten picked<00:16:33.330> up<00:16:33.510> by<00:16:33.930> other<00:16:34.140> developers<00:16:34.800> who<00:16:34.950> found 00:16:35.210 --> 00:16:35.220 align:start position:0% picked up by other developers who found 00:16:35.220 --> 00:16:37.820 align:start position:0% picked up by other developers who found it's<00:16:35.460> a<00:16:35.550> very<00:16:35.760> easy<00:16:36.000> way<00:16:36.480> to<00:16:36.870> build<00:16:37.590> a 00:16:37.820 --> 00:16:37.830 align:start position:0% it's a very easy way to build a 00:16:37.830 --> 00:16:39.860 align:start position:0% it's a very easy way to build a blockchain<00:16:38.250> application<00:16:39.090> in<00:16:39.360> fact<00:16:39.780> the 00:16:39.860 --> 00:16:39.870 align:start position:0% blockchain application in fact the 00:16:39.870 --> 00:16:41.990 align:start position:0% blockchain application in fact the recent<00:16:40.230> winner<00:16:40.410> of<00:16:40.560> the<00:16:40.950> rise<00:16:41.160> Barclays 00:16:41.990 --> 00:16:42.000 align:start position:0% recent winner of the rise Barclays 00:16:42.000 --> 00:16:45.080 align:start position:0% recent winner of the rise Barclays hackathon<00:16:42.570> one<00:16:43.350> using<00:16:44.070> block<00:16:44.310> app<00:16:44.520> straddle 00:16:45.080 --> 00:16:45.090 align:start position:0% hackathon one using block app straddle 00:16:45.090 --> 00:16:48.470 align:start position:0% hackathon one using block app straddle and<00:16:45.240> here's<00:16:46.080> the<00:16:46.230> thing<00:16:46.440> he<00:16:47.010> had<00:16:47.100> never<00:16:47.480> looked 00:16:48.470 --> 00:16:48.480 align:start position:0% and here's the thing he had never looked 00:16:48.480 --> 00:16:50.780 align:start position:0% and here's the thing he had never looked at<00:16:48.690> a<00:16:48.750> single<00:16:49.260> line<00:16:49.470> of<00:16:49.620> solidity<00:16:50.100> before<00:16:50.640> that 00:16:50.780 --> 00:16:50.790 align:start position:0% at a single line of solidity before that 00:16:50.790 --> 00:16:55.970 align:start position:0% at a single line of solidity before that akka<00:16:51.030> phone<00:16:53.660> so<00:16:54.660> what<00:16:54.990> we're<00:16:55.140> trying<00:16:55.260> to<00:16:55.530> do<00:16:55.710> is 00:16:55.970 --> 00:16:55.980 align:start position:0% akka phone so what we're trying to do is 00:16:55.980 --> 00:16:58.100 align:start position:0% akka phone so what we're trying to do is essentially<00:16:56.640> provide<00:16:57.120> a<00:16:57.150> complete<00:16:57.690> solution 00:16:58.100 --> 00:16:58.110 align:start position:0% essentially provide a complete solution 00:16:58.110 --> 00:16:59.930 align:start position:0% essentially provide a complete solution with<00:16:59.070> Microsoft 00:16:59.930 --> 00:16:59.940 align:start position:0% with Microsoft 00:16:59.940 --> 00:17:02.630 align:start position:0% with Microsoft we<00:17:00.240> now<00:17:00.360> have<00:17:00.600> one-click<00:17:01.200> deployment<00:17:01.800> on<00:17:02.010> the 00:17:02.630 --> 00:17:02.640 align:start position:0% we now have one-click deployment on the 00:17:02.640 --> 00:17:05.420 align:start position:0% we now have one-click deployment on the Microsoft<00:17:03.180> Azure<00:17:03.630> cloud<00:17:04.100> we're<00:17:05.100> providing 00:17:05.420 --> 00:17:05.430 align:start position:0% Microsoft Azure cloud we're providing 00:17:05.430 --> 00:17:08.180 align:start position:0% Microsoft Azure cloud we're providing hands-on<00:17:05.970> workshops<00:17:06.960> and<00:17:07.260> education<00:17:07.830> efforts 00:17:08.180 --> 00:17:08.190 align:start position:0% hands-on workshops and education efforts 00:17:08.190 --> 00:17:10.100 align:start position:0% hands-on workshops and education efforts to<00:17:08.550> make<00:17:08.730> sure<00:17:08.880> people<00:17:09.090> can<00:17:09.390> use<00:17:09.630> these<00:17:09.810> tools 00:17:10.100 --> 00:17:10.110 align:start position:0% to make sure people can use these tools 00:17:10.110 --> 00:17:12.110 align:start position:0% to make sure people can use these tools and<00:17:10.380> lastly<00:17:11.220> with<00:17:11.520> our<00:17:11.700> parent<00:17:12.000> company 00:17:12.110 --> 00:17:12.120 align:start position:0% and lastly with our parent company 00:17:12.120 --> 00:17:14.860 align:start position:0% and lastly with our parent company consensus<00:17:12.900> enterprise<00:17:13.470> we're<00:17:14.280> helping 00:17:14.860 --> 00:17:14.870 align:start position:0% consensus enterprise we're helping 00:17:14.870 --> 00:17:18.380 align:start position:0% consensus enterprise we're helping companies<00:17:16.130> figure<00:17:17.130> out<00:17:17.280> how<00:17:17.580> to<00:17:17.640> build<00:17:17.970> and 00:17:18.380 --> 00:17:18.390 align:start position:0% companies figure out how to build and 00:17:18.390 --> 00:17:23.270 align:start position:0% companies figure out how to build and use<00:17:18.570> these<00:17:18.840> technologies<00:17:19.290> in<00:17:19.770> long<00:17:19.950> term<00:17:22.280> this 00:17:23.270 --> 00:17:23.280 align:start position:0% use these technologies in long term this 00:17:23.280 --> 00:17:26.170 align:start position:0% use these technologies in long term this is<00:17:23.430> our<00:17:23.580> team<00:17:23.820> come<00:17:24.780> look<00:17:25.290> for<00:17:25.320> this<00:17:25.620> teacher 00:17:26.170 --> 00:17:26.180 align:start position:0% is our team come look for this teacher 00:17:26.180 --> 00:17:29.210 align:start position:0% is our team come look for this teacher we<00:17:27.180> are<00:17:27.360> very<00:17:27.660> friendly<00:17:28.020> and<00:17:28.440> open<00:17:28.770> we'd<00:17:28.950> love 00:17:29.210 --> 00:17:29.220 align:start position:0% we are very friendly and open we'd love 00:17:29.220 --> 00:17:31.010 align:start position:0% we are very friendly and open we'd love to<00:17:29.250> talk<00:17:29.580> to<00:17:29.640> you<00:17:29.850> about<00:17:29.970> how<00:17:30.480> to<00:17:30.510> use<00:17:30.660> our 00:17:31.010 --> 00:17:31.020 align:start position:0% to talk to you about how to use our 00:17:31.020 --> 00:17:32.000 align:start position:0% to talk to you about how to use our tools 00:17:32.000 --> 00:17:32.010 align:start position:0% tools 00:17:32.010 --> 00:17:33.980 align:start position:0% tools on<00:17:32.100> how<00:17:32.460> to<00:17:32.520> make<00:17:32.790> our<00:17:32.970> tools<00:17:33.240> interoperate 00:17:33.980 --> 00:17:33.990 align:start position:0% on how to make our tools interoperate 00:17:33.990 --> 00:17:39.020 align:start position:0% on how to make our tools interoperate with<00:17:34.020> whatever<00:17:34.410> you're<00:17:34.799> doing<00:17:36.410> so<00:17:37.850> the<00:17:38.850> key 00:17:39.020 --> 00:17:39.030 align:start position:0% with whatever you're doing so the key 00:17:39.030 --> 00:17:41.690 align:start position:0% with whatever you're doing so the key message<00:17:39.059> of<00:17:39.570> all<00:17:39.780> of<00:17:39.960> this<00:17:40.080> is<00:17:40.370> this<00:17:41.370> isn't 00:17:41.690 --> 00:17:41.700 align:start position:0% message of all of this is this isn't 00:17:41.700 --> 00:17:43.970 align:start position:0% message of all of this is this isn't about<00:17:41.910> the<00:17:42.030> future<00:17:42.419> this<00:17:43.169> is<00:17:43.230> about<00:17:43.559> today 00:17:43.970 --> 00:17:43.980 align:start position:0% about the future this is about today 00:17:43.980 --> 00:17:46.570 align:start position:0% about the future this is about today what<00:17:44.700> can<00:17:44.880> we<00:17:45.000> start<00:17:45.299> building<00:17:45.840> right<00:17:46.320> now 00:17:46.570 --> 00:17:46.580 align:start position:0% what can we start building right now 00:17:46.580 --> 00:18:27.029 align:start position:0% what can we start building right now thank<00:17:47.580> you<00:17:47.640> very<00:17:47.700> much 00:18:27.029 --> 00:18:27.039 align:start position:0% 00:18:27.039 --> 00:18:30.690 align:start position:0% wait 00:18:30.690 --> 00:18:30.700 align:start position:0% 00:18:30.700 --> 00:18:33.249 align:start position:0% so<00:18:31.700> my<00:18:31.850> Google<00:18:32.149> Calendar<00:18:32.330> wants<00:18:32.960> me<00:18:33.080> to<00:18:33.109> know 00:18:33.249 --> 00:18:33.259 align:start position:0% so my Google Calendar wants me to know 00:18:33.259 --> 00:18:42.029 align:start position:0% so my Google Calendar wants me to know that<00:18:33.619> I<00:18:33.649> have<00:18:33.919> a<00:18:36.190> yes<00:18:37.570> thank<00:18:38.570> you<00:18:38.690> google<00:18:39.669> okay 00:18:42.029 --> 00:18:42.039 align:start position:0% that I have a yes thank you google okay 00:18:42.039 --> 00:18:45.970 align:start position:0% that I have a yes thank you google okay so<00:18:43.039> I'm<00:18:43.519> Ryan<00:18:44.239> rice<00:18:44.450> I'm<00:18:44.779> the<00:18:45.350> author<00:18:45.499> of<00:18:45.710> the 00:18:45.970 --> 00:18:45.980 align:start position:0% so I'm Ryan rice I'm the author of the 00:18:45.980 --> 00:18:50.379 align:start position:0% so I'm Ryan rice I'm the author of the block<00:18:46.279> apps<00:18:46.489> j/s<00:18:47.059> JavaScript<00:18:48.019> library<00:18:49.389> block 00:18:50.379 --> 00:18:50.389 align:start position:0% block apps j/s JavaScript library block 00:18:50.389 --> 00:18:54.509 align:start position:0% block apps j/s JavaScript library block upstairs<00:18:50.869> connects<00:18:51.379> aetherium<00:18:51.799> to<00:18:52.639> the<00:18:52.759> web 00:18:54.509 --> 00:18:54.519 align:start position:0% upstairs connects aetherium to the web 00:18:54.519 --> 00:18:58.799 align:start position:0% upstairs connects aetherium to the web block<00:18:55.519> apps<00:18:55.730> itself<00:18:56.210> as<00:18:56.799> Jim<00:18:57.799> just<00:18:57.980> told<00:18:58.220> you 00:18:58.799 --> 00:18:58.809 align:start position:0% block apps itself as Jim just told you 00:18:58.809 --> 00:19:03.789 align:start position:0% block apps itself as Jim just told you exposes<00:18:59.809> aetherium<00:19:00.470> as<00:19:00.649> a<00:19:01.580> database<00:19:02.799> using 00:19:03.789 --> 00:19:03.799 align:start position:0% exposes aetherium as a database using 00:19:03.799 --> 00:19:07.629 align:start position:0% exposes aetherium as a database using our<00:19:04.159> restful<00:19:04.789> api<00:19:05.090> you<00:19:05.929> can<00:19:06.169> query<00:19:06.529> any<00:19:07.159> number 00:19:07.629 --> 00:19:07.639 align:start position:0% our restful api you can query any number 00:19:07.639 --> 00:19:12.070 align:start position:0% our restful api you can query any number of<00:19:08.139> aspects<00:19:09.139> of<00:19:09.289> aetherium<00:19:09.999> both<00:19:10.999> by<00:19:11.269> native 00:19:12.070 --> 00:19:12.080 align:start position:0% of aspects of aetherium both by native 00:19:12.080 --> 00:19:14.320 align:start position:0% of aspects of aetherium both by native metadata<00:19:12.619> and<00:19:12.889> by<00:19:13.100> metadata<00:19:13.609> that<00:19:13.730> you<00:19:14.090> can 00:19:14.320 --> 00:19:14.330 align:start position:0% metadata and by metadata that you can 00:19:14.330 --> 00:19:16.060 align:start position:0% metadata and by metadata that you can only<00:19:14.690> extract<00:19:15.049> by<00:19:15.379> having<00:19:15.710> run<00:19:15.919> those 00:19:16.060 --> 00:19:16.070 align:start position:0% only extract by having run those 00:19:16.070 --> 00:19:18.989 align:start position:0% only extract by having run those transactions<00:19:17.049> you<00:19:18.049> can<00:19:18.230> query<00:19:18.470> blocks 00:19:18.989 --> 00:19:18.999 align:start position:0% transactions you can query blocks 00:19:18.999 --> 00:19:20.739 align:start position:0% transactions you can query blocks transactions<00:19:19.999> accounts<00:19:20.539> or<00:19:20.659> accounts 00:19:20.739 --> 00:19:20.749 align:start position:0% transactions accounts or accounts 00:19:20.749 --> 00:19:24.580 align:start position:0% transactions accounts or accounts storage<00:19:21.499> and<00:19:21.799> you<00:19:22.639> can<00:19:22.820> query<00:19:23.600> things<00:19:24.019> those 00:19:24.580 --> 00:19:24.590 align:start position:0% storage and you can query things those 00:19:24.590 --> 00:19:27.879 align:start position:0% storage and you can query things those transactions<00:19:25.460> by<00:19:25.669> such<00:19:26.289> such<00:19:27.289> features<00:19:27.859> as 00:19:27.879 --> 00:19:27.889 align:start position:0% transactions by such such features as 00:19:27.889 --> 00:19:30.249 align:start position:0% transactions by such such features as what<00:19:28.519> accounts<00:19:28.940> have<00:19:29.090> changed<00:19:29.480> in<00:19:29.659> them<00:19:29.869> and 00:19:30.249 --> 00:19:30.259 align:start position:0% what accounts have changed in them and 00:19:30.259 --> 00:19:32.259 align:start position:0% what accounts have changed in them and other<00:19:31.070> such<00:19:31.369> things<00:19:31.399> that<00:19:31.850> might<00:19:31.999> be<00:19:32.149> of 00:19:32.259 --> 00:19:32.269 align:start position:0% other such things that might be of 00:19:32.269 --> 00:19:35.739 align:start position:0% other such things that might be of interest<00:19:32.389> as<00:19:32.960> analytics<00:19:34.029> block<00:19:35.029> eps<00:19:35.269> j/s 00:19:35.739 --> 00:19:35.749 align:start position:0% interest as analytics block eps j/s 00:19:35.749 --> 00:19:39.249 align:start position:0% interest as analytics block eps j/s builds<00:19:36.739> upon<00:19:36.830> this<00:19:37.309> api<00:19:37.759> by<00:19:38.450> wrapping<00:19:38.869> in 00:19:39.249 --> 00:19:39.259 align:start position:0% builds upon this api by wrapping in 00:19:39.259 --> 00:19:43.180 align:start position:0% builds upon this api by wrapping in high-level<00:19:39.529> javascript<00:19:41.440> in<00:19:42.440> fact<00:19:42.859> it 00:19:43.180 --> 00:19:43.190 align:start position:0% high-level javascript in fact it 00:19:43.190 --> 00:19:46.539 align:start position:0% high-level javascript in fact it supports<00:19:43.940> solidity<00:19:44.710> very<00:19:45.710> transparently<00:19:46.460> a 00:19:46.539 --> 00:19:46.549 align:start position:0% supports solidity very transparently a 00:19:46.549 --> 00:19:48.999 align:start position:0% supports solidity very transparently a trap<00:19:46.909> solidity<00:19:47.419> contracts<00:19:48.109> in<00:19:48.289> JavaScript 00:19:48.999 --> 00:19:49.009 align:start position:0% trap solidity contracts in JavaScript 00:19:49.009 --> 00:19:53.739 align:start position:0% trap solidity contracts in JavaScript objects<00:19:50.379> thus<00:19:51.379> realizing<00:19:51.679> the<00:19:52.749> the 00:19:53.739 --> 00:19:53.749 align:start position:0% objects thus realizing the the 00:19:53.749 --> 00:19:55.359 align:start position:0% objects thus realizing the the programmatic<00:19:54.109> structure<00:19:54.889> of<00:19:54.950> a<00:19:55.009> solidity 00:19:55.359 --> 00:19:55.369 align:start position:0% programmatic structure of a solidity 00:19:55.369 --> 00:19:58.749 align:start position:0% programmatic structure of a solidity program<00:19:55.850> as<00:19:56.109> the<00:19:57.109> programmatic<00:19:57.859> structure<00:19:58.549> in 00:19:58.749 --> 00:19:58.759 align:start position:0% program as the programmatic structure in 00:19:58.759 --> 00:20:00.849 align:start position:0% program as the programmatic structure in javascript<00:19:59.450> so<00:20:00.080> that<00:20:00.230> you<00:20:00.320> can<00:20:00.470> easily 00:20:00.849 --> 00:20:00.859 align:start position:0% javascript so that you can easily 00:20:00.859 --> 00:20:03.759 align:start position:0% javascript so that you can easily integrate<00:20:01.100> it<00:20:01.429> into<00:20:01.580> an<00:20:01.789> application<00:20:02.769> since 00:20:03.759 --> 00:20:03.769 align:start position:0% integrate it into an application since 00:20:03.769 --> 00:20:06.849 align:start position:0% integrate it into an application since any<00:20:04.220> network<00:20:04.700> communication<00:20:05.619> necessarily<00:20:06.619> is 00:20:06.849 --> 00:20:06.859 align:start position:0% any network communication necessarily is 00:20:06.859 --> 00:20:11.859 align:start position:0% any network communication necessarily is asynchronous<00:20:07.989> Java<00:20:08.989> apps<00:20:09.950> uses<00:20:10.789> a<00:20:10.999> popular 00:20:11.859 --> 00:20:11.869 align:start position:0% asynchronous Java apps uses a popular 00:20:11.869 --> 00:20:16.419 align:start position:0% asynchronous Java apps uses a popular promise<00:20:12.830> library<00:20:13.369> Bluebird<00:20:13.989> to<00:20:14.989> make<00:20:15.249> to<00:20:16.249> make 00:20:16.419 --> 00:20:16.429 align:start position:0% promise library Bluebird to make to make 00:20:16.429 --> 00:20:19.599 align:start position:0% promise library Bluebird to make to make these<00:20:17.139> your<00:20:18.139> interaction<00:20:18.859> with<00:20:18.889> this 00:20:19.599 --> 00:20:19.609 align:start position:0% these your interaction with this 00:20:19.609 --> 00:20:22.529 align:start position:0% these your interaction with this asynchronous<00:20:20.379> activity<00:20:21.379> powerful<00:20:22.129> and 00:20:22.529 --> 00:20:22.539 align:start position:0% asynchronous activity powerful and 00:20:22.539 --> 00:20:26.710 align:start position:0% asynchronous activity powerful and uncomfortable<00:20:24.999> nope 00:20:26.710 --> 00:20:26.720 align:start position:0% uncomfortable nope 00:20:26.720 --> 00:20:35.080 align:start position:0% uncomfortable nope there<00:20:27.350> we<00:20:27.530> go<00:20:27.920> not<00:20:28.280> done<00:20:28.550> yet<00:20:28.580> so<00:20:33.280> let<00:20:34.280> us<00:20:34.310> now 00:20:35.080 --> 00:20:35.090 align:start position:0% there we go not done yet so let us now 00:20:35.090 --> 00:20:37.960 align:start position:0% there we go not done yet so let us now take<00:20:35.150> a<00:20:35.570> look<00:20:35.810> at<00:20:36.020> something<00:20:37.010> that<00:20:37.160> you<00:20:37.460> might 00:20:37.960 --> 00:20:37.970 align:start position:0% take a look at something that you might 00:20:37.970 --> 00:20:43.870 align:start position:0% take a look at something that you might write<00:20:38.240> with<00:20:38.570> lockup<00:20:39.140> J<00:20:39.560> s<00:20:41.350> so<00:20:42.700> this<00:20:43.700> is<00:20:43.760> a 00:20:43.870 --> 00:20:43.880 align:start position:0% write with lockup J s so this is a 00:20:43.880 --> 00:20:46.740 align:start position:0% write with lockup J s so this is a little<00:20:44.390> bit<00:20:44.540> too<00:20:44.780> expanded<00:20:45.710> here<00:20:46.370> we<00:20:46.460> are 00:20:46.740 --> 00:20:46.750 align:start position:0% little bit too expanded here we are 00:20:46.750 --> 00:20:49.030 align:start position:0% little bit too expanded here we are still<00:20:47.750> large<00:20:47.930> enough<00:20:47.960> to<00:20:48.170> say<00:20:48.470> hopefully<00:20:48.680> the 00:20:49.030 --> 00:20:49.040 align:start position:0% still large enough to say hopefully the 00:20:49.040 --> 00:20:52.900 align:start position:0% still large enough to say hopefully the color<00:20:49.370> scheme<00:20:49.730> isn't<00:20:50.150> too<00:20:50.840> dark<00:20:51.670> mmm<00:20:52.700> is<00:20:52.760> it 00:20:52.900 --> 00:20:52.910 align:start position:0% color scheme isn't too dark mmm is it 00:20:52.910 --> 00:20:58.510 align:start position:0% color scheme isn't too dark mmm is it too<00:20:53.030> dark<00:20:53.500> all<00:20:54.500> right<00:20:55.720> well<00:20:57.100> I'm<00:20:58.100> going<00:20:58.430> to 00:20:58.510 --> 00:20:58.520 align:start position:0% too dark all right well I'm going to 00:20:58.520 --> 00:21:01.210 align:start position:0% too dark all right well I'm going to just<00:20:59.500> attempt<00:21:00.500> to<00:21:00.560> power<00:21:00.800> through<00:21:01.130> this 00:21:01.210 --> 00:21:01.220 align:start position:0% just attempt to power through this 00:21:01.220 --> 00:21:15.210 align:start position:0% just attempt to power through this anyway<00:21:02.470> because<00:21:07.300> select<00:21:08.300> what<00:21:08.450> ah<00:21:12.100> very<00:21:13.100> good 00:21:15.210 --> 00:21:15.220 align:start position:0% 00:21:15.220 --> 00:21:22.360 align:start position:0% okay<00:21:16.690> so<00:21:18.910> this<00:21:19.910> is<00:21:20.120> the<00:21:20.480> HTML<00:21:21.260> portion<00:21:22.040> of<00:21:22.250> the 00:21:22.360 --> 00:21:22.370 align:start position:0% okay so this is the HTML portion of the 00:21:22.370 --> 00:21:24.160 align:start position:0% okay so this is the HTML portion of the DAP<00:21:22.550> that<00:21:22.760> you<00:21:22.820> might<00:21:22.970> write<00:21:23.120> with<00:21:23.330> lockup<00:21:23.780> yes 00:21:24.160 --> 00:21:24.170 align:start position:0% DAP that you might write with lockup yes 00:21:24.170 --> 00:21:29.370 align:start position:0% DAP that you might write with lockup yes it's<00:21:24.470> very<00:21:24.620> simple<00:21:25.070> and<00:21:25.390> it<00:21:26.410> just<00:21:27.410> produces<00:21:27.560> a 00:21:29.370 --> 00:21:29.380 align:start position:0% it's very simple and it just produces a 00:21:29.380 --> 00:21:31.660 align:start position:0% it's very simple and it just produces a little<00:21:30.380> interface<00:21:30.770> that<00:21:31.010> looks<00:21:31.160> like<00:21:31.430> that 00:21:31.660 --> 00:21:31.670 align:start position:0% little interface that looks like that 00:21:31.670 --> 00:21:35.110 align:start position:0% little interface that looks like that just<00:21:31.970> a<00:21:32.150> box<00:21:32.540> with<00:21:32.930> a<00:21:33.380> couple<00:21:33.800> a<00:21:34.310> couple<00:21:34.520> fields 00:21:35.110 --> 00:21:35.120 align:start position:0% just a box with a couple a couple fields 00:21:35.120 --> 00:21:38.830 align:start position:0% just a box with a couple a couple fields you<00:21:35.210> can<00:21:35.240> fill<00:21:35.600> in<00:21:37.270> you'll<00:21:38.270> notice<00:21:38.390> that<00:21:38.690> it's 00:21:38.830 --> 00:21:38.840 align:start position:0% you can fill in you'll notice that it's 00:21:38.840 --> 00:21:41.560 align:start position:0% you can fill in you'll notice that it's fetching<00:21:39.050> it's<00:21:39.470> it's<00:21:40.340> JavaScript<00:21:40.610> from<00:21:41.330> the 00:21:41.560 --> 00:21:41.570 align:start position:0% fetching it's it's JavaScript from the 00:21:41.570 --> 00:21:45.010 align:start position:0% fetching it's it's JavaScript from the Strato<00:21:42.050> dev<00:21:42.580> address<00:21:43.580> this<00:21:43.790> is<00:21:43.970> a<00:21:44.020> Azhar 00:21:45.010 --> 00:21:45.020 align:start position:0% Strato dev address this is a Azhar 00:21:45.020 --> 00:21:46.600 align:start position:0% Strato dev address this is a Azhar instance<00:21:45.500> that<00:21:45.680> we<00:21:45.830> started<00:21:46.250> up<00:21:46.370> for 00:21:46.600 --> 00:21:46.610 align:start position:0% instance that we started up for 00:21:46.610 --> 00:21:50.170 align:start position:0% instance that we started up for ourselves<00:21:47.590> where<00:21:48.590> Strato<00:21:49.280> is<00:21:49.520> always<00:21:49.790> running 00:21:50.170 --> 00:21:50.180 align:start position:0% ourselves where Strato is always running 00:21:50.180 --> 00:21:53.440 align:start position:0% ourselves where Strato is always running and<00:21:50.420> this<00:21:51.230> library<00:21:51.470> is<00:21:51.830> available<00:21:52.150> all<00:21:53.150> that 00:21:53.440 --> 00:21:53.450 align:start position:0% and this library is available all that 00:21:53.450 --> 00:21:55.810 align:start position:0% and this library is available all that happens<00:21:53.780> when<00:21:53.930> you<00:21:54.020> open<00:21:54.320> this<00:21:54.440> this<00:21:55.430> page<00:21:55.670> is 00:21:55.810 --> 00:21:55.820 align:start position:0% happens when you open this this page is 00:21:55.820 --> 00:21:57.370 align:start position:0% happens when you open this this page is that<00:21:55.850> it<00:21:56.120> runs<00:21:56.300> a<00:21:56.480> function<00:21:56.870> and<00:21:57.020> waits<00:21:57.170> for 00:21:57.370 --> 00:21:57.380 align:start position:0% that it runs a function and waits for 00:21:57.380 --> 00:22:05.119 align:start position:0% that it runs a function and waits for you<00:21:57.470> to<00:21:57.560> push<00:21:57.740> the<00:21:57.860> button<00:21:59.680> all<00:22:00.680> right<00:22:00.800> so 00:22:05.119 --> 00:22:05.129 align:start position:0% 00:22:05.129 --> 00:22:10.019 align:start position:0% the<00:22:06.690> code<00:22:07.690> the<00:22:08.440> solidity<00:22:08.860> contracts<00:22:09.580> that<00:22:09.820> is 00:22:10.019 --> 00:22:10.029 align:start position:0% the code the solidity contracts that is 00:22:10.029 --> 00:22:14.340 align:start position:0% the code the solidity contracts that is behind<00:22:10.779> this<00:22:12.389> behind<00:22:13.389> this<00:22:13.509> application<00:22:14.169> is<00:22:14.320> a 00:22:14.340 --> 00:22:14.350 align:start position:0% behind this behind this application is a 00:22:14.350 --> 00:22:16.980 align:start position:0% behind this behind this application is a simple<00:22:14.740> crowdsourcing<00:22:15.490> thing<00:22:15.990> basically 00:22:16.980 --> 00:22:16.990 align:start position:0% simple crowdsourcing thing basically 00:22:16.990 --> 00:22:19.470 align:start position:0% simple crowdsourcing thing basically people<00:22:17.830> can<00:22:18.220> submit<00:22:18.700> their<00:22:18.879> names<00:22:19.090> a<00:22:19.210> little 00:22:19.470 --> 00:22:19.480 align:start position:0% people can submit their names a little 00:22:19.480 --> 00:22:21.119 align:start position:0% people can submit their names a little bit<00:22:19.600> of<00:22:19.690> ether<00:22:19.899> and<00:22:20.259> they<00:22:20.679> can<00:22:20.830> get 00:22:21.119 --> 00:22:21.129 align:start position:0% bit of ether and they can get 00:22:21.129 --> 00:22:23.039 align:start position:0% bit of ether and they can get contributed<00:22:21.669> to<00:22:21.759> the<00:22:21.850> contract<00:22:22.360> and<00:22:22.539> after<00:22:23.019> a 00:22:23.039 --> 00:22:23.049 align:start position:0% contributed to the contract and after a 00:22:23.049 --> 00:22:27.090 align:start position:0% contributed to the contract and after a certain<00:22:23.259> point<00:22:23.679> they<00:22:24.490> are<00:22:25.679> you<00:22:26.679> can<00:22:26.860> just 00:22:27.090 --> 00:22:27.100 align:start position:0% certain point they are you can just 00:22:27.100 --> 00:22:29.159 align:start position:0% certain point they are you can just decide<00:22:27.460> to<00:22:27.730> pay<00:22:27.879> it<00:22:27.999> out<00:22:28.120> so<00:22:28.840> this<00:22:28.929> is<00:22:28.990> not 00:22:29.159 --> 00:22:29.169 align:start position:0% decide to pay it out so this is not 00:22:29.169 --> 00:22:30.869 align:start position:0% decide to pay it out so this is not intended<00:22:29.499> to<00:22:29.679> be<00:22:29.769> clever<00:22:30.039> it's<00:22:30.309> just<00:22:30.429> intended 00:22:30.869 --> 00:22:30.879 align:start position:0% intended to be clever it's just intended 00:22:30.879 --> 00:22:36.210 align:start position:0% intended to be clever it's just intended to<00:22:30.970> be<00:22:31.120> instructive<00:22:33.960> you'll<00:22:34.960> notice<00:22:35.289> that<00:22:35.769> a 00:22:36.210 --> 00:22:36.220 align:start position:0% to be instructive you'll notice that a 00:22:36.220 --> 00:22:38.609 align:start position:0% to be instructive you'll notice that a little<00:22:36.789> way<00:22:36.879> down<00:22:36.909> I<00:22:37.389> have<00:22:37.600> this<00:22:37.809> set<00:22:38.110> profile 00:22:38.609 --> 00:22:38.619 align:start position:0% little way down I have this set profile 00:22:38.619 --> 00:22:41.190 align:start position:0% little way down I have this set profile option<00:22:39.100> this<00:22:39.220> is<00:22:39.629> one<00:22:40.629> of<00:22:40.659> the<00:22:40.869> features<00:22:41.169> of 00:22:41.190 --> 00:22:41.200 align:start position:0% option this is one of the features of 00:22:41.200 --> 00:22:44.340 align:start position:0% option this is one of the features of block<00:22:41.590> fjs<00:22:42.279> that<00:22:43.059> makes<00:22:43.570> it<00:22:43.749> easy<00:22:43.990> to<00:22:44.320> use 00:22:44.340 --> 00:22:44.350 align:start position:0% block fjs that makes it easy to use 00:22:44.350 --> 00:22:47.190 align:start position:0% block fjs that makes it easy to use different<00:22:44.860> block<00:22:45.159> chains<00:22:45.549> or<00:22:45.909> or<00:22:46.749> different 00:22:47.190 --> 00:22:47.200 align:start position:0% different block chains or or different 00:22:47.200 --> 00:22:51.810 align:start position:0% different block chains or or different strata<00:22:47.740> nodes<00:22:48.389> we<00:22:49.389> have<00:22:49.619> at<00:22:50.619> the<00:22:50.919> very<00:22:50.950> least<00:22:51.429> a 00:22:51.810 --> 00:22:51.820 align:start position:0% strata nodes we have at the very least a 00:22:51.820 --> 00:22:54.239 align:start position:0% strata nodes we have at the very least a straddle<00:22:52.570> live<00:22:52.779> node<00:22:53.350> in<00:22:53.740> addition<00:22:54.129> to 00:22:54.239 --> 00:22:54.249 align:start position:0% straddle live node in addition to 00:22:54.249 --> 00:22:57.419 align:start position:0% straddle live node in addition to straddle<00:22:54.549> dev<00:22:54.909> node<00:22:55.179> and<00:22:55.619> that<00:22:56.619> is<00:22:56.919> running 00:22:57.419 --> 00:22:57.429 align:start position:0% straddle dev node and that is running 00:22:57.429 --> 00:23:01.470 align:start position:0% straddle dev node and that is running rather<00:22:58.149> than<00:22:58.509> a<00:22:58.749> sandbox<00:22:59.379> blockchain<00:23:00.220> a<00:23:00.480> live 00:23:01.470 --> 00:23:01.480 align:start position:0% rather than a sandbox blockchain a live 00:23:01.480 --> 00:23:03.210 align:start position:0% rather than a sandbox blockchain a live etherion<00:23:02.019> blockchain<00:23:02.499> and<00:23:02.529> by<00:23:02.830> simply 00:23:03.210 --> 00:23:03.220 align:start position:0% etherion blockchain and by simply 00:23:03.220 --> 00:23:10.560 align:start position:0% etherion blockchain and by simply changing<00:23:03.460> the<00:23:04.419> word<00:23:04.629> let<00:23:05.169> me<00:23:05.259> just<00:23:08.700> in<00:23:09.700> dev<00:23:10.090> to 00:23:10.560 --> 00:23:10.570 align:start position:0% changing the word let me just in dev to 00:23:10.570 --> 00:23:14.820 align:start position:0% changing the word let me just in dev to live<00:23:11.169> I<00:23:12.210> could<00:23:13.210> make<00:23:13.749> it<00:23:13.929> run<00:23:14.139> on<00:23:14.379> the<00:23:14.649> live 00:23:14.820 --> 00:23:14.830 align:start position:0% live I could make it run on the live 00:23:14.830 --> 00:23:17.460 align:start position:0% live I could make it run on the live Network<00:23:15.279> now<00:23:15.490> it<00:23:16.330> wouldn't<00:23:16.539> be<00:23:16.629> wise<00:23:16.869> because 00:23:17.460 --> 00:23:17.470 align:start position:0% Network now it wouldn't be wise because 00:23:17.470 --> 00:23:19.859 align:start position:0% Network now it wouldn't be wise because I<00:23:17.499> have<00:23:17.860> decided<00:23:18.429> to<00:23:18.730> use<00:23:18.909> an<00:23:19.090> address<00:23:19.480> it<00:23:19.720> has 00:23:19.859 --> 00:23:19.869 align:start position:0% I have decided to use an address it has 00:23:19.869 --> 00:23:21.810 align:start position:0% I have decided to use an address it has no<00:23:20.080> ether<00:23:20.470> and<00:23:20.710> I've<00:23:20.919> also<00:23:21.070> put<00:23:21.220> his<00:23:21.460> public 00:23:21.810 --> 00:23:21.820 align:start position:0% no ether and I've also put his public 00:23:21.820 --> 00:23:23.850 align:start position:0% no ether and I've also put his public key<00:23:21.970> up<00:23:22.090> on<00:23:22.240> the<00:23:22.360> screen<00:23:22.629> so<00:23:23.379> it<00:23:23.649> had<00:23:23.740> better 00:23:23.850 --> 00:23:23.860 align:start position:0% key up on the screen so it had better 00:23:23.860 --> 00:23:27.509 align:start position:0% key up on the screen so it had better not<00:23:23.950> have<00:23:24.279> any<00:23:24.429> ether<00:23:24.730> but<00:23:25.619> if<00:23:26.619> I<00:23:26.799> darka<00:23:27.220> tected 00:23:27.509 --> 00:23:27.519 align:start position:0% not have any ether but if I darka tected 00:23:27.519 --> 00:23:29.009 align:start position:0% not have any ether but if I darka tected this<00:23:27.669> just<00:23:27.909> a<00:23:27.999> little<00:23:28.210> bit<00:23:28.330> more<00:23:28.480> carefully 00:23:29.009 --> 00:23:29.019 align:start position:0% this just a little bit more carefully 00:23:29.019 --> 00:23:32.639 align:start position:0% this just a little bit more carefully than<00:23:29.999> just<00:23:30.999> by<00:23:31.119> making<00:23:31.269> that<00:23:31.539> one<00:23:31.600> change<00:23:32.139> it 00:23:32.639 --> 00:23:32.649 align:start position:0% than just by making that one change it 00:23:32.649 --> 00:23:36.060 align:start position:0% than just by making that one change it would<00:23:32.889> in<00:23:33.039> fact<00:23:33.190> be<00:23:33.490> a<00:23:33.519> real<00:23:33.789> a<00:23:33.820> real<00:23:34.269> dab<00:23:35.070> so 00:23:36.060 --> 00:23:36.070 align:start position:0% would in fact be a real a real dab so 00:23:36.070 --> 00:23:39.539 align:start position:0% would in fact be a real a real dab so block<00:23:36.730> fgs<00:23:37.090> is<00:23:37.269> a<00:23:37.299> number<00:23:37.570> of<00:23:37.690> modules<00:23:38.220> it<00:23:39.220> has 00:23:39.539 --> 00:23:39.549 align:start position:0% block fgs is a number of modules it has 00:23:39.549 --> 00:23:45.060 align:start position:0% block fgs is a number of modules it has a<00:23:40.679> it<00:23:41.679> has<00:23:41.710> a<00:23:41.950> solidity<00:23:42.610> module<00:23:43.649> for<00:23:44.649> one<00:23:44.799> thing 00:23:45.060 --> 00:23:45.070 align:start position:0% a it has a solidity module for one thing 00:23:45.070 --> 00:23:47.220 align:start position:0% a it has a solidity module for one thing and<00:23:45.369> that's<00:23:46.360> the<00:23:46.509> module<00:23:46.869> you're<00:23:46.960> going<00:23:47.080> to<00:23:47.139> be 00:23:47.220 --> 00:23:47.230 align:start position:0% and that's the module you're going to be 00:23:47.230 --> 00:23:50.159 align:start position:0% and that's the module you're going to be using<00:23:47.470> the<00:23:47.590> most<00:23:47.710> often<00:23:48.249> it<00:23:49.090> has<00:23:49.360> some<00:23:49.539> some 00:23:50.159 --> 00:23:50.169 align:start position:0% using the most often it has some some 00:23:50.169 --> 00:23:52.529 align:start position:0% using the most often it has some some basic<00:23:50.499> support<00:23:50.830> for<00:23:50.950> for<00:23:51.669> aetherium<00:23:52.059> concepts 00:23:52.529 --> 00:23:52.539 align:start position:0% basic support for for aetherium concepts 00:23:52.539 --> 00:23:55.470 align:start position:0% basic support for for aetherium concepts below<00:23:52.840> solidity<00:23:53.320> but<00:23:53.649> in<00:23:53.950> fact<00:23:54.249> solidity<00:23:54.909> just 00:23:55.470 --> 00:23:55.480 align:start position:0% below solidity but in fact solidity just 00:23:55.480 --> 00:23:57.180 align:start position:0% below solidity but in fact solidity just abstracts<00:23:56.350> all<00:23:56.559> of<00:23:56.619> them<00:23:56.769> to<00:23:56.889> a<00:23:56.950> higher<00:23:57.159> level 00:23:57.180 --> 00:23:57.190 align:start position:0% abstracts all of them to a higher level 00:23:57.190 --> 00:23:58.739 align:start position:0% abstracts all of them to a higher level so<00:23:57.669> for<00:23:57.850> the<00:23:57.909> most<00:23:58.090> part<00:23:58.330> you're<00:23:58.480> just<00:23:58.509> going 00:23:58.739 --> 00:23:58.749 align:start position:0% so for the most part you're just going 00:23:58.749 --> 00:24:01.560 align:start position:0% so for the most part you're just going to<00:23:58.779> be<00:23:58.899> using<00:23:59.230> that<00:23:59.440> however<00:24:00.369> as<00:24:01.360> you'll 00:24:01.560 --> 00:24:01.570 align:start position:0% to be using that however as you'll 00:24:01.570 --> 00:24:04.529 align:start position:0% to be using that however as you'll notice<00:24:01.720> in<00:24:01.990> Kieran's<00:24:02.440> contract<00:24:03.119> you<00:24:04.119> can 00:24:04.529 --> 00:24:04.539 align:start position:0% notice in Kieran's contract you can 00:24:04.539 --> 00:24:06.960 align:start position:0% notice in Kieran's contract you can sometimes<00:24:04.749> find<00:24:05.110> yourself<00:24:05.259> submitting<00:24:05.970> eval 00:24:06.960 --> 00:24:06.970 align:start position:0% sometimes find yourself submitting eval 00:24:06.970 --> 00:24:08.730 align:start position:0% sometimes find yourself submitting eval use<00:24:07.240> in<00:24:07.509> way<00:24:07.899> when<00:24:08.200> you<00:24:08.289> really<00:24:08.499> meant<00:24:08.649> the 00:24:08.730 --> 00:24:08.740 align:start position:0% use in way when you really meant the 00:24:08.740 --> 00:24:11.970 align:start position:0% use in way when you really meant the submit<00:24:09.009> them<00:24:09.190> in<00:24:09.279> ether<00:24:09.669> so<00:24:10.499> you<00:24:11.499> can<00:24:11.679> in<00:24:11.799> fact 00:24:11.970 --> 00:24:11.980 align:start position:0% submit them in ether so you can in fact 00:24:11.980 --> 00:24:13.799 align:start position:0% submit them in ether so you can in fact convert<00:24:12.730> them<00:24:12.940> back<00:24:13.299> and<00:24:13.480> forth<00:24:13.509> pretty 00:24:13.799 --> 00:24:13.809 align:start position:0% convert them back and forth pretty 00:24:13.809 --> 00:24:15.510 align:start position:0% convert them back and forth pretty easily<00:24:14.049> with<00:24:14.379> the<00:24:14.559> unit's<00:24:14.889> model 00:24:15.510 --> 00:24:15.520 align:start position:0% easily with the unit's model 00:24:15.520 --> 00:24:19.130 align:start position:0% easily with the unit's model this<00:24:16.180> faucet<00:24:16.570> thing<00:24:17.190> is<00:24:18.190> a<00:24:18.250> testing<00:24:18.790> facility 00:24:19.130 --> 00:24:19.140 align:start position:0% this faucet thing is a testing facility 00:24:19.140 --> 00:24:21.780 align:start position:0% this faucet thing is a testing facility like<00:24:20.140> I<00:24:20.260> said<00:24:20.440> this<00:24:20.560> address<00:24:20.950> has<00:24:21.190> no<00:24:21.460> real 00:24:21.780 --> 00:24:21.790 align:start position:0% like I said this address has no real 00:24:21.790 --> 00:24:25.140 align:start position:0% like I said this address has no real ether<00:24:22.180> on<00:24:22.330> it<00:24:22.540> but<00:24:22.840> on<00:24:23.140> the<00:24:23.710> test<00:24:24.190> net<00:24:24.460> Strato 00:24:25.140 --> 00:24:25.150 align:start position:0% ether on it but on the test net Strato 00:24:25.150 --> 00:24:29.040 align:start position:0% ether on it but on the test net Strato dev<00:24:25.660> it<00:24:26.230> doesn't<00:24:27.010> need<00:24:27.220> either<00:24:27.730> it<00:24:28.660> or<00:24:28.870> rather 00:24:29.040 --> 00:24:29.050 align:start position:0% dev it doesn't need either it or rather 00:24:29.050 --> 00:24:30.480 align:start position:0% dev it doesn't need either it or rather it<00:24:29.230> doesn't<00:24:29.530> either<00:24:29.590> but<00:24:29.980> it<00:24:30.070> doesn't<00:24:30.310> need<00:24:30.400> to 00:24:30.480 --> 00:24:30.490 align:start position:0% it doesn't either but it doesn't need to 00:24:30.490 --> 00:24:31.950 align:start position:0% it doesn't either but it doesn't need to real<00:24:30.700> ether<00:24:31.210> but<00:24:31.480> we<00:24:31.570> need<00:24:31.690> to<00:24:31.810> give<00:24:31.930> it 00:24:31.950 --> 00:24:31.960 align:start position:0% real ether but we need to give it 00:24:31.960 --> 00:24:34.740 align:start position:0% real ether but we need to give it something<00:24:32.290> so<00:24:32.800> that<00:24:33.010> the<00:24:33.160> VM<00:24:34.060> will<00:24:34.240> work<00:24:34.450> the 00:24:34.740 --> 00:24:34.750 align:start position:0% something so that the VM will work the 00:24:34.750 --> 00:24:36.300 align:start position:0% something so that the VM will work the faucet<00:24:35.110> just<00:24:35.140> supplies<00:24:35.620> any<00:24:35.920> address<00:24:36.190> they 00:24:36.300 --> 00:24:36.310 align:start position:0% faucet just supplies any address they 00:24:36.310 --> 00:24:39.780 align:start position:0% faucet just supplies any address they want<00:24:36.490> with<00:24:36.640> a<00:24:36.670> thousand<00:24:37.150> fake<00:24:37.300> ether<00:24:38.580> so<00:24:39.580> let's 00:24:39.780 --> 00:24:39.790 align:start position:0% want with a thousand fake ether so let's 00:24:39.790 --> 00:24:42.270 align:start position:0% want with a thousand fake ether so let's change<00:24:40.060> that<00:24:40.180> back<00:24:40.540> to<00:24:40.570> Strato<00:24:41.200> dev<00:24:41.530> so<00:24:42.100> that<00:24:42.250> I 00:24:42.270 --> 00:24:42.280 align:start position:0% change that back to Strato dev so that I 00:24:42.280 --> 00:24:43.710 align:start position:0% change that back to Strato dev so that I don't<00:24:42.520> accidentally<00:24:43.060> try<00:24:43.420> to<00:24:43.480> spend 00:24:43.710 --> 00:24:43.720 align:start position:0% don't accidentally try to spend 00:24:43.720 --> 00:24:46.940 align:start position:0% don't accidentally try to spend something<00:24:44.080> I<00:24:44.170> don't<00:24:44.350> have<00:24:44.910> all<00:24:45.910> right<00:24:46.060> so 00:24:46.940 --> 00:24:46.950 align:start position:0% something I don't have all right so 00:24:46.950 --> 00:24:55.530 align:start position:0% something I don't have all right so let's<00:24:47.950> go<00:24:48.550> down<00:24:48.760> and<00:24:49.950> look<00:24:50.950> at<00:24:51.100> this<00:24:51.280> code<00:24:54.540> so 00:24:55.530 --> 00:24:55.540 align:start position:0% let's go down and look at this code so 00:24:55.540 --> 00:24:57.990 align:start position:0% let's go down and look at this code so what's<00:24:56.530> going<00:24:56.770> on<00:24:56.920> here<00:24:57.190> is<00:24:57.370> that<00:24:57.400> it 00:24:57.990 --> 00:24:58.000 align:start position:0% what's going on here is that it 00:24:58.000 --> 00:25:03.750 align:start position:0% what's going on here is that it remembers<00:24:59.910> the<00:25:01.470> address<00:25:02.470> of<00:25:02.650> the<00:25:02.770> of<00:25:03.490> the 00:25:03.750 --> 00:25:03.760 align:start position:0% remembers the address of the of the 00:25:03.760 --> 00:25:07.440 align:start position:0% remembers the address of the of the individual<00:25:04.570> who<00:25:04.900> you<00:25:05.080> are<00:25:06.330> benefiting<00:25:07.330> with 00:25:07.440 --> 00:25:07.450 align:start position:0% individual who you are benefiting with 00:25:07.450 --> 00:25:09.690 align:start position:0% individual who you are benefiting with your<00:25:07.600> contributions<00:25:08.320> as<00:25:08.500> well<00:25:08.800> as<00:25:09.040> various 00:25:09.690 --> 00:25:09.700 align:start position:0% your contributions as well as various 00:25:09.700 --> 00:25:11.880 align:start position:0% your contributions as well as various information<00:25:10.270> about<00:25:10.600> the<00:25:10.840> people<00:25:11.620> who<00:25:11.740> have 00:25:11.880 --> 00:25:11.890 align:start position:0% information about the people who have 00:25:11.890 --> 00:25:16.700 align:start position:0% information about the people who have paid<00:25:12.540> as<00:25:13.540> you<00:25:14.470> can<00:25:14.620> see<00:25:14.860> this<00:25:15.040> is<00:25:15.190> a<00:25:15.220> fairly 00:25:16.700 --> 00:25:16.710 align:start position:0% paid as you can see this is a fairly 00:25:16.710 --> 00:25:20.010 align:start position:0% paid as you can see this is a fairly complex<00:25:17.710> solidity<00:25:18.610> structure<00:25:19.210> it's<00:25:19.870> a 00:25:20.010 --> 00:25:20.020 align:start position:0% complex solidity structure it's a 00:25:20.020 --> 00:25:22.620 align:start position:0% complex solidity structure it's a mapping<00:25:20.230> from<00:25:20.680> addresses<00:25:21.250> to<00:25:21.640> a<00:25:21.910> user-defined 00:25:22.620 --> 00:25:22.630 align:start position:0% mapping from addresses to a user-defined 00:25:22.630 --> 00:25:26.040 align:start position:0% mapping from addresses to a user-defined struct<00:25:23.560> and<00:25:23.710> the<00:25:24.130> Java<00:25:24.370> sir<00:25:24.640> the<00:25:25.060> block<00:25:25.450> XJS 00:25:26.040 --> 00:25:26.050 align:start position:0% struct and the Java sir the block XJS 00:25:26.050 --> 00:25:28.940 align:start position:0% struct and the Java sir the block XJS library<00:25:26.470> actually<00:25:26.650> does<00:25:27.070> support 00:25:28.940 --> 00:25:28.950 align:start position:0% library actually does support 00:25:28.950 --> 00:25:31.770 align:start position:0% library actually does support interpreting<00:25:29.950> the<00:25:30.130> values<00:25:30.610> of<00:25:30.910> even<00:25:31.540> such<00:25:31.750> a 00:25:31.770 --> 00:25:31.780 align:start position:0% interpreting the values of even such a 00:25:31.780 --> 00:25:36.210 align:start position:0% interpreting the values of even such a complex<00:25:32.580> object<00:25:33.580> it<00:25:34.180> reads<00:25:34.450> the<00:25:34.690> storage<00:25:35.220> it 00:25:36.210 --> 00:25:36.220 align:start position:0% complex object it reads the storage it 00:25:36.220 --> 00:25:38.880 align:start position:0% complex object it reads the storage it interprets<00:25:37.210> the<00:25:37.570> structure<00:25:38.440> of<00:25:38.650> this 00:25:38.880 --> 00:25:38.890 align:start position:0% interprets the structure of this 00:25:38.890 --> 00:25:42.540 align:start position:0% interprets the structure of this solidity<00:25:39.340> code<00:25:39.730> and<00:25:40.030> it<00:25:41.020> figures<00:25:41.470> out<00:25:41.680> what<00:25:42.280> of 00:25:42.540 --> 00:25:42.550 align:start position:0% solidity code and it figures out what of 00:25:42.550 --> 00:25:46.140 align:start position:0% solidity code and it figures out what of the<00:25:43.260> hexadecimal<00:25:44.490> nonsense<00:25:45.490> that<00:25:45.760> lives<00:25:46.000> in 00:25:46.140 --> 00:25:46.150 align:start position:0% the hexadecimal nonsense that lives in 00:25:46.150 --> 00:25:48.150 align:start position:0% the hexadecimal nonsense that lives in the<00:25:46.240> etherium<00:25:46.660> storage<00:25:47.050> corresponds<00:25:47.890> to<00:25:47.920> the 00:25:48.150 --> 00:25:48.160 align:start position:0% the etherium storage corresponds to the 00:25:48.160 --> 00:25:50.250 align:start position:0% the etherium storage corresponds to the values<00:25:49.150> you<00:25:49.300> meant<00:25:49.480> to<00:25:49.600> put<00:25:49.750> in<00:25:49.870> there<00:25:50.050> and<00:25:50.200> it 00:25:50.250 --> 00:25:50.260 align:start position:0% values you meant to put in there and it 00:25:50.260 --> 00:25:52.590 align:start position:0% values you meant to put in there and it converts<00:25:50.590> them<00:25:50.770> into<00:25:50.800> JavaScript<00:25:51.520> types<00:25:51.760> so 00:25:52.590 --> 00:25:52.600 align:start position:0% converts them into JavaScript types so 00:25:52.600 --> 00:25:54.180 align:start position:0% converts them into JavaScript types so you<00:25:52.630> don't<00:25:52.960> have<00:25:53.110> to<00:25:53.290> worry<00:25:53.500> about<00:25:53.590> any<00:25:53.890> of<00:25:54.070> the 00:25:54.180 --> 00:25:54.190 align:start position:0% you don't have to worry about any of the 00:25:54.190 --> 00:25:57.300 align:start position:0% you don't have to worry about any of the implementation<00:25:54.850> details<00:25:55.030> of<00:25:55.570> aetherium<00:25:56.310> when 00:25:57.300 --> 00:25:57.310 align:start position:0% implementation details of aetherium when 00:25:57.310 --> 00:25:59.700 align:start position:0% implementation details of aetherium when you<00:25:57.460> are<00:25:57.580> working<00:25:57.760> with<00:25:58.000> lockups<00:25:58.870> yes<00:25:59.050> it<00:25:59.350> does 00:25:59.700 --> 00:25:59.710 align:start position:0% you are working with lockups yes it does 00:25:59.710 --> 00:26:02.190 align:start position:0% you are working with lockups yes it does as<00:25:59.860> much<00:26:00.040> as<00:26:00.160> possible<00:26:00.340> to<00:26:01.180> to<00:26:01.780> take<00:26:01.930> care<00:26:01.990> of 00:26:02.190 --> 00:26:02.200 align:start position:0% as much as possible to to take care of 00:26:02.200 --> 00:26:07.620 align:start position:0% as much as possible to to take care of them<00:26:02.410> for<00:26:02.650> you<00:26:04.260> so<00:26:05.260> when<00:26:06.100> you<00:26:06.510> create<00:26:07.510> this 00:26:07.620 --> 00:26:07.630 align:start position:0% them for you so when you create this 00:26:07.630 --> 00:26:10.220 align:start position:0% them for you so when you create this contract<00:26:08.170> all<00:26:08.350> it<00:26:08.470> will<00:26:08.590> do<00:26:08.710> is<00:26:08.890> store<00:26:09.550> the 00:26:10.220 --> 00:26:10.230 align:start position:0% contract all it will do is store the 00:26:10.230 --> 00:26:13.020 align:start position:0% contract all it will do is store the store<00:26:11.230> the<00:26:11.380> name<00:26:11.560> of<00:26:11.800> the<00:26:12.160> or<00:26:12.460> the<00:26:12.730> address 00:26:13.020 --> 00:26:13.030 align:start position:0% store the name of the or the address 00:26:13.030 --> 00:26:14.940 align:start position:0% store the name of the or the address rather<00:26:13.390> of<00:26:13.690> the<00:26:14.170> person<00:26:14.470> who's<00:26:14.620> supposed<00:26:14.710> to 00:26:14.940 --> 00:26:14.950 align:start position:0% rather of the person who's supposed to 00:26:14.950 --> 00:26:15.540 align:start position:0% rather of the person who's supposed to get<00:26:15.130> the<00:26:15.250> money 00:26:15.540 --> 00:26:15.550 align:start position:0% get the money 00:26:15.550 --> 00:26:19.580 align:start position:0% get the money it<00:26:16.540> also<00:26:16.690> initializes<00:26:17.470> that<00:26:17.650> array<00:26:17.920> of 00:26:19.580 --> 00:26:19.590 align:start position:0% it also initializes that array of 00:26:19.590 --> 00:26:21.870 align:start position:0% it also initializes that array of contributors<00:26:20.590> and<00:26:20.860> then<00:26:21.580> when<00:26:21.760> you 00:26:21.870 --> 00:26:21.880 align:start position:0% contributors and then when you 00:26:21.880 --> 00:26:24.720 align:start position:0% contributors and then when you contribute 00:26:24.720 --> 00:26:24.730 align:start position:0% 00:26:24.730 --> 00:26:29.549 align:start position:0% oops<00:26:26.110> alright<00:26:27.110> so<00:26:27.500> when<00:26:27.679> you<00:26:27.799> contribute<00:26:28.100> it 00:26:29.549 --> 00:26:29.559 align:start position:0% oops alright so when you contribute it 00:26:29.559 --> 00:26:31.600 align:start position:0% oops alright so when you contribute it well<00:26:30.559> does<00:26:30.799> a<00:26:30.830> little<00:26:31.100> check<00:26:31.250> to<00:26:31.340> see<00:26:31.490> if<00:26:31.549> you 00:26:31.600 --> 00:26:31.610 align:start position:0% well does a little check to see if you 00:26:31.610 --> 00:26:33.610 align:start position:0% well does a little check to see if you haven't<00:26:31.880> given<00:26:32.000> anything<00:26:32.299> but<00:26:32.570> otherwise<00:26:32.779> it 00:26:33.610 --> 00:26:33.620 align:start position:0% haven't given anything but otherwise it 00:26:33.620 --> 00:26:36.130 align:start position:0% haven't given anything but otherwise it simply<00:26:34.429> adds<00:26:34.820> the<00:26:35.299> contributor<00:26:35.779> to<00:26:35.899> the<00:26:36.020> end 00:26:36.130 --> 00:26:36.140 align:start position:0% simply adds the contributor to the end 00:26:36.140 --> 00:26:39.960 align:start position:0% simply adds the contributor to the end of<00:26:36.289> the<00:26:36.440> array<00:26:36.909> and<00:26:37.909> adds<00:26:38.600> the<00:26:38.840> value<00:26:39.230> to<00:26:39.679> the 00:26:39.960 --> 00:26:39.970 align:start position:0% of the array and adds the value to the 00:26:39.970 --> 00:26:43.180 align:start position:0% of the array and adds the value to the to<00:26:40.970> the<00:26:41.140> struct<00:26:42.140> the<00:26:42.440> corresponding<00:26:42.980> to<00:26:43.070> that 00:26:43.180 --> 00:26:43.190 align:start position:0% to the struct the corresponding to that 00:26:43.190 --> 00:26:45.659 align:start position:0% to the struct the corresponding to that contributor<00:26:43.760> which<00:26:44.330> lives<00:26:44.600> in<00:26:44.720> the<00:26:44.779> mapping 00:26:45.659 --> 00:26:45.669 align:start position:0% contributor which lives in the mapping 00:26:45.669 --> 00:26:47.680 align:start position:0% contributor which lives in the mapping then<00:26:46.669> then<00:26:47.120> it<00:26:47.240> tells<00:26:47.390> you<00:26:47.480> that<00:26:47.510> the 00:26:47.680 --> 00:26:47.690 align:start position:0% then then it tells you that the 00:26:47.690 --> 00:26:54.700 align:start position:0% then then it tells you that the transaction<00:26:48.230> succeeded<00:26:48.760> so<00:26:51.220> if<00:26:52.220> I<00:26:52.520> were<00:26:52.760> to<00:26:53.710> if 00:26:54.700 --> 00:26:54.710 align:start position:0% transaction succeeded so if I were to if 00:26:54.710 --> 00:26:56.409 align:start position:0% transaction succeeded so if I were to if I<00:26:54.830> were<00:26:54.980> to<00:26:55.159> try<00:26:55.429> to<00:26:55.490> give<00:26:55.730> some<00:26:55.760> ether<00:26:56.090> to<00:26:56.299> that 00:26:56.409 --> 00:26:56.419 align:start position:0% I were to try to give some ether to that 00:26:56.419 --> 00:26:57.159 align:start position:0% I were to try to give some ether to that right<00:26:56.659> now 00:26:57.159 --> 00:26:57.169 align:start position:0% right now 00:26:57.169 --> 00:27:01.450 align:start position:0% right now say<00:26:57.440> myself<00:26:57.890> 10<00:26:58.669> ether<00:26:59.470> then<00:27:00.470> you<00:27:01.340> would 00:27:01.450 --> 00:27:01.460 align:start position:0% say myself 10 ether then you would 00:27:01.460 --> 00:27:05.230 align:start position:0% say myself 10 ether then you would expect<00:27:01.669> to<00:27:01.850> see<00:27:02.059> something<00:27:02.270> pop<00:27:02.600> up<00:27:02.840> and<00:27:04.240> it 00:27:05.230 --> 00:27:05.240 align:start position:0% expect to see something pop up and it 00:27:05.240 --> 00:27:08.380 align:start position:0% expect to see something pop up and it does<00:27:05.510> in<00:27:05.659> fact<00:27:05.779> pop<00:27:06.110> up<00:27:06.320> I<00:27:06.500> have<00:27:07.090> I've<00:27:08.090> been 00:27:08.380 --> 00:27:08.390 align:start position:0% does in fact pop up I have I've been 00:27:08.390 --> 00:27:10.210 align:start position:0% does in fact pop up I have I've been thanked<00:27:08.779> generously<00:27:09.230> for<00:27:09.529> giving<00:27:09.799> 10<00:27:09.950> ether 00:27:10.210 --> 00:27:10.220 align:start position:0% thanked generously for giving 10 ether 00:27:10.220 --> 00:27:12.460 align:start position:0% thanked generously for giving 10 ether to<00:27:10.340> this<00:27:10.490> person<00:27:10.940> so<00:27:11.600> how<00:27:11.779> did<00:27:11.929> that<00:27:12.049> happen 00:27:12.460 --> 00:27:12.470 align:start position:0% to this person so how did that happen 00:27:12.470 --> 00:27:16.620 align:start position:0% to this person so how did that happen exactly<00:27:12.620> this<00:27:13.549> is<00:27:13.760> where<00:27:14.110> lockups<00:27:15.110> jeaious 00:27:16.620 --> 00:27:16.630 align:start position:0% exactly this is where lockups jeaious 00:27:16.630 --> 00:27:20.680 align:start position:0% exactly this is where lockups jeaious actually<00:27:17.630> does<00:27:17.809> its<00:27:17.990> work<00:27:18.279> so<00:27:19.510> at<00:27:20.510> the 00:27:20.680 --> 00:27:20.690 align:start position:0% actually does its work so at the 00:27:20.690 --> 00:27:23.470 align:start position:0% actually does its work so at the beginning<00:27:21.080> of<00:27:21.169> the<00:27:21.380> mmm<00:27:22.250> at<00:27:22.820> the<00:27:23.029> beginning<00:27:23.330> of 00:27:23.470 --> 00:27:23.480 align:start position:0% beginning of the mmm at the beginning of 00:27:23.480 --> 00:27:25.899 align:start position:0% beginning of the mmm at the beginning of this<00:27:23.690> this<00:27:24.260> app<00:27:24.500> before<00:27:24.799> I<00:27:25.039> even<00:27:25.340> came<00:27:25.669> here<00:27:25.880> I 00:27:25.899 --> 00:27:25.909 align:start position:0% this this app before I even came here I 00:27:25.909 --> 00:27:27.220 align:start position:0% this this app before I even came here I loaded<00:27:26.179> this<00:27:26.360> page<00:27:26.600> and<00:27:26.779> it<00:27:26.870> created<00:27:27.140> that 00:27:27.220 --> 00:27:27.230 align:start position:0% loaded this page and it created that 00:27:27.230 --> 00:27:29.769 align:start position:0% loaded this page and it created that contract<00:27:27.890> all<00:27:28.669> I<00:27:28.730> did<00:27:29.029> was<00:27:29.149> it<00:27:29.270> took<00:27:29.299> that<00:27:29.600> code 00:27:29.769 --> 00:27:29.779 align:start position:0% contract all I did was it took that code 00:27:29.779 --> 00:27:31.450 align:start position:0% contract all I did was it took that code I<00:27:29.809> plugged<00:27:30.140> it<00:27:30.289> into<00:27:30.440> the<00:27:30.529> solidity<00:27:30.950> module 00:27:31.450 --> 00:27:31.460 align:start position:0% I plugged it into the solidity module 00:27:31.460 --> 00:27:33.029 align:start position:0% I plugged it into the solidity module and<00:27:31.640> I<00:27:31.669> called<00:27:31.940> the<00:27:32.090> new<00:27:32.240> contract<00:27:32.720> method 00:27:33.029 --> 00:27:33.039 align:start position:0% and I called the new contract method 00:27:33.039 --> 00:27:35.409 align:start position:0% and I called the new contract method since<00:27:34.039> most<00:27:34.279> of<00:27:34.460> these<00:27:34.610> operations<00:27:35.270> are 00:27:35.409 --> 00:27:35.419 align:start position:0% since most of these operations are 00:27:35.419 --> 00:27:37.240 align:start position:0% since most of these operations are asynchronous<00:27:35.720> the<00:27:36.380> call<00:27:36.770> looks<00:27:37.039> a<00:27:37.100> little 00:27:37.240 --> 00:27:37.250 align:start position:0% asynchronous the call looks a little 00:27:37.250 --> 00:27:38.769 align:start position:0% asynchronous the call looks a little strange<00:27:37.669> you<00:27:37.789> would<00:27:37.970> expect<00:27:38.330> it<00:27:38.510> to<00:27:38.630> be<00:27:38.750> a 00:27:38.769 --> 00:27:38.779 align:start position:0% strange you would expect it to be a 00:27:38.779 --> 00:27:40.539 align:start position:0% strange you would expect it to be a member<00:27:39.110> function<00:27:39.320> and<00:27:39.860> it<00:27:40.010> is<00:27:40.159> but<00:27:40.429> as<00:27:40.520> a 00:27:40.539 --> 00:27:40.549 align:start position:0% member function and it is but as a 00:27:40.549 --> 00:27:42.310 align:start position:0% member function and it is but as a member<00:27:40.760> function<00:27:41.059> of<00:27:41.330> the<00:27:41.390> return<00:27:41.750> value<00:27:42.110> of<00:27:42.200> a 00:27:42.310 --> 00:27:42.320 align:start position:0% member function of the return value of a 00:27:42.320 --> 00:27:44.500 align:start position:0% member function of the return value of a promise<00:27:42.679> so<00:27:43.220> I'm<00:27:43.340> using<00:27:43.520> some<00:27:43.669> promise<00:27:44.120> syntax 00:27:44.500 --> 00:27:44.510 align:start position:0% promise so I'm using some promise syntax 00:27:44.510 --> 00:27:46.659 align:start position:0% promise so I'm using some promise syntax for<00:27:44.809> that<00:27:44.990> and<00:27:45.260> all<00:27:45.590> it<00:27:45.740> does<00:27:45.890> is<00:27:45.950> it<00:27:46.250> creates<00:27:46.370> a 00:27:46.659 --> 00:27:46.669 align:start position:0% for that and all it does is it creates a 00:27:46.669 --> 00:27:49.269 align:start position:0% for that and all it does is it creates a contract<00:27:47.179> and<00:27:47.450> saves<00:27:48.110> that<00:27:48.260> contract<00:27:48.799> in<00:27:49.039> the 00:27:49.269 --> 00:27:49.279 align:start position:0% contract and saves that contract in the 00:27:49.279 --> 00:27:52.960 align:start position:0% contract and saves that contract in the in<00:27:49.970> the<00:27:50.750> in<00:27:51.320> the<00:27:51.380> page<00:27:51.770> for<00:27:52.279> for<00:27:52.789> later 00:27:52.960 --> 00:27:52.970 align:start position:0% in the in the page for for later 00:27:52.970 --> 00:27:54.940 align:start position:0% in the in the page for for later reference<00:27:53.240> and<00:27:53.720> it<00:27:53.899> also<00:27:54.049> activates<00:27:54.559> that 00:27:54.940 --> 00:27:54.950 align:start position:0% reference and it also activates that 00:27:54.950 --> 00:27:57.070 align:start position:0% reference and it also activates that button<00:27:55.429> since<00:27:56.090> there<00:27:56.270> was<00:27:56.360> no<00:27:56.480> error<00:27:56.690> I<00:27:56.779> don't 00:27:57.070 --> 00:27:57.080 align:start position:0% button since there was no error I don't 00:27:57.080 --> 00:28:00.519 align:start position:0% button since there was no error I don't care<00:27:57.230> about<00:27:57.320> the<00:27:57.590> other<00:27:57.710> function<00:27:58.720> now<00:27:59.720> when<00:28:00.500> I 00:28:00.519 --> 00:28:00.529 align:start position:0% care about the other function now when I 00:28:00.529 --> 00:28:04.210 align:start position:0% care about the other function now when I push<00:28:00.860> that<00:28:01.100> button<00:28:01.159> it<00:28:02.770> went<00:28:03.770> through<00:28:03.919> a<00:28:04.010> long 00:28:04.210 --> 00:28:04.220 align:start position:0% push that button it went through a long 00:28:04.220 --> 00:28:07.210 align:start position:0% push that button it went through a long chain<00:28:04.700> of<00:28:04.909> promise<00:28:05.659> operations<00:28:06.409> the 00:28:07.210 --> 00:28:07.220 align:start position:0% chain of promise operations the 00:28:07.220 --> 00:28:09.159 align:start position:0% chain of promise operations the beginning<00:28:07.610> of<00:28:07.730> which<00:28:07.940> was<00:28:08.390> to<00:28:08.750> run<00:28:09.020> this 00:28:09.159 --> 00:28:09.169 align:start position:0% beginning of which was to run this 00:28:09.169 --> 00:28:11.190 align:start position:0% beginning of which was to run this function<00:28:09.380> which<00:28:09.710> I've<00:28:09.890> called<00:28:10.130> patronize 00:28:11.190 --> 00:28:11.200 align:start position:0% function which I've called patronize 00:28:11.200 --> 00:28:15.840 align:start position:0% function which I've called patronize maybe<00:28:12.200> I<00:28:12.260> should<00:28:12.409> have<00:28:12.500> called<00:28:12.649> it<00:28:12.799> contribute 00:28:15.840 --> 00:28:15.850 align:start position:0% 00:28:15.850 --> 00:28:21.760 align:start position:0% so<00:28:16.850> let's<00:28:17.299> look<00:28:17.419> at<00:28:17.570> how<00:28:17.690> that<00:28:17.750> works<00:28:20.770> that's 00:28:21.760 --> 00:28:21.770 align:start position:0% so let's look at how that works that's 00:28:21.770 --> 00:28:25.539 align:start position:0% so let's look at how that works that's based<00:28:22.130> on<00:28:22.370> these<00:28:23.029> three<00:28:23.270> functions<00:28:23.830> so<00:28:24.830> the 00:28:25.539 --> 00:28:25.549 align:start position:0% based on these three functions so the 00:28:25.549 --> 00:28:27.730 align:start position:0% based on these three functions so the core<00:28:25.789> the<00:28:26.330> core<00:28:26.360> piece<00:28:26.720> of<00:28:26.899> functionality<00:28:27.080> is 00:28:27.730 --> 00:28:27.740 align:start position:0% core the core piece of functionality is 00:28:27.740 --> 00:28:29.230 align:start position:0% core the core piece of functionality is the<00:28:27.860> second<00:28:28.190> function<00:28:28.340> there<00:28:28.669> patronize 00:28:29.230 --> 00:28:29.240 align:start position:0% the second function there patronize 00:28:29.240 --> 00:28:31.180 align:start position:0% the second function there patronize which<00:28:29.630> takes<00:28:29.929> a<00:28:30.049> name<00:28:30.200> and<00:28:30.350> a<00:28:30.409> value<00:28:30.590> the 00:28:31.180 --> 00:28:31.190 align:start position:0% which takes a name and a value the 00:28:31.190 --> 00:28:33.519 align:start position:0% which takes a name and a value the things<00:28:31.399> that<00:28:31.549> appeared<00:28:31.820> in<00:28:31.880> those<00:28:32.059> boxes<00:28:32.529> so 00:28:33.519 --> 00:28:33.529 align:start position:0% things that appeared in those boxes so 00:28:33.529 --> 00:28:36.070 align:start position:0% things that appeared in those boxes so all<00:28:34.520> it<00:28:34.820> does<00:28:34.970> is<00:28:35.179> it<00:28:35.299> takes<00:28:35.419> that<00:28:35.659> contract 00:28:36.070 --> 00:28:36.080 align:start position:0% all it does is it takes that contract 00:28:36.080 --> 00:28:37.110 align:start position:0% all it does is it takes that contract object<00:28:36.470> which<00:28:36.620> is 00:28:37.110 --> 00:28:37.120 align:start position:0% object which is 00:28:37.120 --> 00:28:39.299 align:start position:0% object which is perhaps<00:28:37.779> not<00:28:38.049> creatively<00:28:38.559> called<00:28:38.710> contract 00:28:39.299 --> 00:28:39.309 align:start position:0% perhaps not creatively called contract 00:28:39.309 --> 00:28:43.350 align:start position:0% perhaps not creatively called contract looks<00:28:39.940> in<00:28:40.149> its<00:28:40.330> state<00:28:40.750> which<00:28:41.559> is<00:28:41.740> a<00:28:42.299> sub-sub 00:28:43.350 --> 00:28:43.360 align:start position:0% looks in its state which is a sub-sub 00:28:43.360 --> 00:28:45.180 align:start position:0% looks in its state which is a sub-sub object<00:28:43.720> which<00:28:43.840> is<00:28:43.990> automatically<00:28:44.470> created<00:28:44.769> by 00:28:45.180 --> 00:28:45.190 align:start position:0% object which is automatically created by 00:28:45.190 --> 00:28:48.060 align:start position:0% object which is automatically created by the<00:28:45.250> library<00:28:45.850> and<00:28:46.090> in<00:28:47.049> there<00:28:47.440> it<00:28:47.559> finds<00:28:47.919> a 00:28:48.060 --> 00:28:48.070 align:start position:0% the library and in there it finds a 00:28:48.070 --> 00:28:49.529 align:start position:0% the library and in there it finds a method<00:28:48.399> called<00:28:48.610> contribute<00:28:49.120> and<00:28:49.299> if<00:28:49.419> you 00:28:49.529 --> 00:28:49.539 align:start position:0% method called contribute and if you 00:28:49.539 --> 00:28:52.320 align:start position:0% method called contribute and if you remember<00:28:49.960> back<00:28:50.409> at<00:28:50.679> the<00:28:50.950> solidity<00:28:51.820> code<00:28:52.120> that 00:28:52.320 --> 00:28:52.330 align:start position:0% remember back at the solidity code that 00:28:52.330 --> 00:28:53.879 align:start position:0% remember back at the solidity code that was<00:28:52.480> the<00:28:52.600> method<00:28:52.750> in<00:28:53.019> the<00:28:53.110> solidity<00:28:53.470> code<00:28:53.710> it's 00:28:53.879 --> 00:28:53.889 align:start position:0% was the method in the solidity code it's 00:28:53.889 --> 00:28:56.340 align:start position:0% was the method in the solidity code it's named<00:28:54.070> the<00:28:54.220> same<00:28:54.370> thing<00:28:54.700> and<00:28:54.970> it's<00:28:55.929> only 00:28:56.340 --> 00:28:56.350 align:start position:0% named the same thing and it's only 00:28:56.350 --> 00:28:57.720 align:start position:0% named the same thing and it's only natural<00:28:56.529> that<00:28:56.799> it<00:28:57.039> should<00:28:57.070> in<00:28:57.309> fact<00:28:57.370> be<00:28:57.610> a 00:28:57.720 --> 00:28:57.730 align:start position:0% natural that it should in fact be a 00:28:57.730 --> 00:28:59.430 align:start position:0% natural that it should in fact be a function<00:28:58.149> object<00:28:58.539> in<00:28:58.659> JavaScript<00:28:59.259> so<00:28:59.350> that 00:28:59.430 --> 00:28:59.440 align:start position:0% function object in JavaScript so that 00:28:59.440 --> 00:29:01.980 align:start position:0% function object in JavaScript so that thing<00:28:59.799> takes<00:29:00.070> a<00:29:00.190> variable<00:29:00.519> which<00:29:01.419> is<00:29:01.450> the<00:29:01.630> same 00:29:01.980 --> 00:29:01.990 align:start position:0% thing takes a variable which is the same 00:29:01.990 --> 00:29:03.629 align:start position:0% thing takes a variable which is the same argument<00:29:02.620> as<00:29:02.740> it<00:29:02.860> would<00:29:02.980> take<00:29:03.100> in<00:29:03.220> solidity 00:29:03.629 --> 00:29:03.639 align:start position:0% argument as it would take in solidity 00:29:03.639 --> 00:29:07.470 align:start position:0% argument as it would take in solidity and<00:29:04.200> I<00:29:05.200> can<00:29:05.559> also<00:29:05.710> specify<00:29:06.190> that<00:29:07.029> it<00:29:07.210> sends 00:29:07.470 --> 00:29:07.480 align:start position:0% and I can also specify that it sends 00:29:07.480 --> 00:29:10.110 align:start position:0% and I can also specify that it sends some<00:29:07.720> other<00:29:07.899> stuff<00:29:08.259> in<00:29:09.190> the<00:29:09.340> transaction 00:29:10.110 --> 00:29:10.120 align:start position:0% some other stuff in the transaction 00:29:10.120 --> 00:29:12.629 align:start position:0% some other stuff in the transaction parameters<00:29:10.720> DX<00:29:11.409> params<00:29:11.830> I<00:29:12.039> can<00:29:12.190> specify<00:29:12.370> a 00:29:12.629 --> 00:29:12.639 align:start position:0% parameters DX params I can specify a 00:29:12.639 --> 00:29:14.549 align:start position:0% parameters DX params I can specify a value<00:29:12.940> which<00:29:13.779> you'll<00:29:14.049> notice<00:29:14.320> that<00:29:14.409> I've 00:29:14.549 --> 00:29:14.559 align:start position:0% value which you'll notice that I've 00:29:14.559 --> 00:29:17.310 align:start position:0% value which you'll notice that I've specified<00:29:15.039> in<00:29:15.309> ether<00:29:15.700> and<00:29:15.909> it's<00:29:16.809> pretty<00:29:17.049> clear 00:29:17.310 --> 00:29:17.320 align:start position:0% specified in ether and it's pretty clear 00:29:17.320 --> 00:29:19.019 align:start position:0% specified in ether and it's pretty clear that<00:29:17.350> I<00:29:17.529> meant<00:29:17.740> to<00:29:17.830> specify<00:29:18.279> an<00:29:18.519> ether<00:29:18.820> from 00:29:19.019 --> 00:29:19.029 align:start position:0% that I meant to specify an ether from 00:29:19.029 --> 00:29:21.779 align:start position:0% that I meant to specify an ether from the<00:29:19.120> syntax<00:29:19.539> I<00:29:19.899> could<00:29:20.470> also<00:29:20.620> set<00:29:21.100> gas<00:29:21.340> price<00:29:21.669> to 00:29:21.779 --> 00:29:21.789 align:start position:0% the syntax I could also set gas price to 00:29:21.789 --> 00:29:23.310 align:start position:0% the syntax I could also set gas price to gas<00:29:21.940> limit<00:29:22.179> if<00:29:22.389> I<00:29:22.480> wanted<00:29:22.809> to<00:29:22.960> but<00:29:23.169> I<00:29:23.200> don't 00:29:23.310 --> 00:29:23.320 align:start position:0% gas limit if I wanted to but I don't 00:29:23.320 --> 00:29:24.509 align:start position:0% gas limit if I wanted to but I don't particularly<00:29:23.799> because<00:29:24.250> those<00:29:24.399> are 00:29:24.509 --> 00:29:24.519 align:start position:0% particularly because those are 00:29:24.519 --> 00:29:28.590 align:start position:0% particularly because those are implementation<00:29:25.179> details<00:29:25.600> and<00:29:26.610> the<00:29:27.610> profile 00:29:28.590 --> 00:29:28.600 align:start position:0% implementation details and the profile 00:29:28.600 --> 00:29:31.200 align:start position:0% implementation details and the profile back<00:29:29.350> up<00:29:29.529> at<00:29:29.679> the<00:29:29.710> top<00:29:29.950> which<00:29:30.490> was<00:29:30.730> set<00:29:31.000> to 00:29:31.200 --> 00:29:31.210 align:start position:0% back up at the top which was set to 00:29:31.210 --> 00:29:34.499 align:start position:0% back up at the top which was set to Strato<00:29:31.779> dev<00:29:32.080> also<00:29:32.409> has<00:29:32.590> some<00:29:33.509> somewhat 00:29:34.499 --> 00:29:34.509 align:start position:0% Strato dev also has some somewhat 00:29:34.509 --> 00:29:35.820 align:start position:0% Strato dev also has some somewhat permissive<00:29:34.899> defaults<00:29:35.289> in<00:29:35.379> the<00:29:35.470> case<00:29:35.649> of 00:29:35.820 --> 00:29:35.830 align:start position:0% permissive defaults in the case of 00:29:35.830 --> 00:29:37.440 align:start position:0% permissive defaults in the case of Strato<00:29:36.100> dev<00:29:36.399> and<00:29:36.669> in<00:29:36.759> the<00:29:36.850> case<00:29:37.000> of<00:29:37.149> shadow 00:29:37.440 --> 00:29:37.450 align:start position:0% Strato dev and in the case of shadow 00:29:37.450 --> 00:29:39.299 align:start position:0% Strato dev and in the case of shadow lives<00:29:37.720> somewhat<00:29:38.230> less<00:29:38.440> permissive<00:29:38.769> default 00:29:39.299 --> 00:29:39.309 align:start position:0% lives somewhat less permissive default 00:29:39.309 --> 00:29:41.159 align:start position:0% lives somewhat less permissive default that<00:29:39.610> it<00:29:39.970> seemed<00:29:40.210> compatible<00:29:40.809> with<00:29:40.960> the<00:29:41.049> other 00:29:41.159 --> 00:29:41.169 align:start position:0% that it seemed compatible with the other 00:29:41.169 --> 00:29:44.220 align:start position:0% that it seemed compatible with the other with<00:29:41.649> the<00:29:41.769> existing<00:29:42.509> aetherium<00:29:43.509> clients<00:29:44.019> get 00:29:44.220 --> 00:29:44.230 align:start position:0% with the existing aetherium clients get 00:29:44.230 --> 00:29:48.119 align:start position:0% with the existing aetherium clients get in<00:29:44.500> C++<00:29:45.399> so<00:29:46.110> that<00:29:47.110> the<00:29:47.320> transaction<00:29:48.039> will 00:29:48.119 --> 00:29:48.129 align:start position:0% in C++ so that the transaction will 00:29:48.129 --> 00:29:50.129 align:start position:0% in C++ so that the transaction will likely<00:29:48.309> be<00:29:48.580> accepted<00:29:49.149> and<00:29:49.299> you<00:29:49.720> don't<00:29:49.870> have<00:29:49.990> to 00:29:50.129 --> 00:29:50.139 align:start position:0% likely be accepted and you don't have to 00:29:50.139 --> 00:29:51.180 align:start position:0% likely be accepted and you don't have to worry<00:29:50.320> about<00:29:50.440> it<00:29:50.679> unless<00:29:50.889> you're<00:29:51.100> really 00:29:51.180 --> 00:29:51.190 align:start position:0% worry about it unless you're really 00:29:51.190 --> 00:29:55.340 align:start position:0% worry about it unless you're really concerned<00:29:51.700> with<00:29:51.970> the<00:29:52.830> fine<00:29:53.830> the<00:29:54.490> fine<00:29:54.700> print 00:29:55.340 --> 00:29:55.350 align:start position:0% concerned with the fine the fine print 00:29:55.350 --> 00:29:57.659 align:start position:0% concerned with the fine the fine print after<00:29:56.350> I've<00:29:56.440> set<00:29:56.620> all<00:29:56.649> that<00:29:56.889> up<00:29:56.950> I<00:29:57.190> just<00:29:57.460> call 00:29:57.659 --> 00:29:57.669 align:start position:0% after I've set all that up I just call 00:29:57.669 --> 00:30:01.799 align:start position:0% after I've set all that up I just call it<00:29:57.789> from<00:29:58.470> well<00:29:59.580> something<00:30:00.580> I<00:30:00.820> need<00:30:01.360> a<00:30:01.389> private 00:30:01.799 --> 00:30:01.809 align:start position:0% it from well something I need a private 00:30:01.809 --> 00:30:06.539 align:start position:0% it from well something I need a private key<00:30:02.019> and<00:30:04.379> the<00:30:05.379> private<00:30:05.740> key<00:30:05.860> in<00:30:05.980> this<00:30:06.129> case<00:30:06.340> is 00:30:06.539 --> 00:30:06.549 align:start position:0% key and the private key in this case is 00:30:06.549 --> 00:30:08.159 align:start position:0% key and the private key in this case is just<00:30:06.730> being<00:30:06.909> created<00:30:07.360> on<00:30:07.450> the<00:30:07.539> fly<00:30:07.720> from<00:30:08.019> a 00:30:08.159 --> 00:30:08.169 align:start position:0% just being created on the fly from a 00:30:08.169 --> 00:30:11.249 align:start position:0% just being created on the fly from a library<00:30:08.679> from<00:30:09.070> a<00:30:09.250> a<00:30:09.549> wallet<00:30:10.179> that<00:30:10.450> I<00:30:10.480> have<00:30:10.809> I 00:30:11.249 --> 00:30:11.259 align:start position:0% library from a a wallet that I have I 00:30:11.259 --> 00:30:15.060 align:start position:0% library from a a wallet that I have I have<00:30:12.360> spun<00:30:13.360> up<00:30:13.509> in<00:30:14.169> the<00:30:14.320> page<00:30:14.559> this<00:30:14.799> is<00:30:14.919> not<00:30:15.039> a 00:30:15.060 --> 00:30:15.070 align:start position:0% have spun up in the page this is not a 00:30:15.070 --> 00:30:17.519 align:start position:0% have spun up in the page this is not a very<00:30:15.279> secure<00:30:15.669> wallet<00:30:16.149> it<00:30:16.269> just<00:30:16.480> every<00:30:17.200> name<00:30:17.379> it 00:30:17.519 --> 00:30:17.529 align:start position:0% very secure wallet it just every name it 00:30:17.529 --> 00:30:18.899 align:start position:0% very secure wallet it just every name it takes<00:30:17.769> it<00:30:17.980> randomly<00:30:18.309> generates<00:30:18.730> an<00:30:18.820> address 00:30:18.899 --> 00:30:18.909 align:start position:0% takes it randomly generates an address 00:30:18.909 --> 00:30:22.049 align:start position:0% takes it randomly generates an address for<00:30:19.419> it<00:30:19.600> and<00:30:20.500> then<00:30:20.710> with<00:30:21.129> the<00:30:21.250> fund<00:30:21.519> function 00:30:22.049 --> 00:30:22.059 align:start position:0% for it and then with the fund function 00:30:22.059 --> 00:30:24.990 align:start position:0% for it and then with the fund function at<00:30:22.179> the<00:30:22.269> top<00:30:22.299> of<00:30:22.600> the<00:30:22.690> screen<00:30:22.960> it<00:30:23.970> applies<00:30:24.970> the 00:30:24.990 --> 00:30:25.000 align:start position:0% at the top of the screen it applies the 00:30:25.000 --> 00:30:26.820 align:start position:0% at the top of the screen it applies the faucet<00:30:25.600> to<00:30:25.720> that<00:30:25.870> address<00:30:26.169> and<00:30:26.320> gives<00:30:26.649> it<00:30:26.769> a 00:30:26.820 --> 00:30:26.830 align:start position:0% faucet to that address and gives it a 00:30:26.830 --> 00:30:31.169 align:start position:0% faucet to that address and gives it a thousand<00:30:27.129> ether<00:30:29.220> once<00:30:30.220> it<00:30:30.370> has<00:30:30.549> the<00:30:30.580> address 00:30:31.169 --> 00:30:31.179 align:start position:0% thousand ether once it has the address 00:30:31.179 --> 00:30:33.119 align:start position:0% thousand ether once it has the address it<00:30:31.539> has<00:30:31.690> the<00:30:31.809> private<00:30:32.169> key<00:30:32.320> also<00:30:32.740> and<00:30:32.919> it<00:30:32.980> just 00:30:33.119 --> 00:30:33.129 align:start position:0% it has the private key also and it just 00:30:33.129 --> 00:30:35.369 align:start position:0% it has the private key also and it just sends<00:30:33.669> that<00:30:33.850> into<00:30:34.120> the<00:30:34.240> patronised<00:30:34.899> function 00:30:35.369 --> 00:30:35.379 align:start position:0% sends that into the patronised function 00:30:35.379 --> 00:30:38.730 align:start position:0% sends that into the patronised function and<00:30:35.879> and<00:30:36.879> and<00:30:37.539> to<00:30:37.750> miss<00:30:37.899> the<00:30:38.019> transaction<00:30:38.590> and 00:30:38.730 --> 00:30:38.740 align:start position:0% and and and to miss the transaction and 00:30:38.740 --> 00:30:41.639 align:start position:0% and and and to miss the transaction and that<00:30:38.769> was<00:30:39.009> what<00:30:39.159> you<00:30:39.279> saw<00:30:39.490> happen<00:30:40.389> here<00:30:40.779> of 00:30:41.639 --> 00:30:41.649 align:start position:0% that was what you saw happen here of 00:30:41.649 --> 00:30:43.200 align:start position:0% that was what you saw happen here of course<00:30:41.980> what<00:30:42.309> you<00:30:42.340> haven't<00:30:42.700> seen<00:30:42.879> yet<00:30:43.029> is 00:30:43.200 --> 00:30:43.210 align:start position:0% course what you haven't seen yet is 00:30:43.210 --> 00:30:45.600 align:start position:0% course what you haven't seen yet is actually<00:30:43.750> pretty<00:30:44.100> obtaining<00:30:45.100> the<00:30:45.220> values 00:30:45.600 --> 00:30:45.610 align:start position:0% actually pretty obtaining the values 00:30:45.610 --> 00:30:47.789 align:start position:0% actually pretty obtaining the values that<00:30:45.789> are<00:30:45.940> printed<00:30:46.360> aren't<00:30:47.019> very<00:30:47.169> many<00:30:47.230> values 00:30:47.789 --> 00:30:47.799 align:start position:0% that are printed aren't very many values 00:30:47.799 --> 00:30:50.520 align:start position:0% that are printed aren't very many values but<00:30:48.039> something<00:30:48.429> had<00:30:48.549> to<00:30:48.700> be<00:30:48.789> done<00:30:48.820> to<00:30:49.090> get<00:30:49.179> them 00:30:50.520 --> 00:30:50.530 align:start position:0% but something had to be done to get them 00:30:50.530 --> 00:30:53.370 align:start position:0% but something had to be done to get them so<00:30:51.530> this<00:30:51.680> is<00:30:51.830> where<00:30:51.980> the<00:30:52.100> placard<00:30:52.520> is<00:30:52.640> printed 00:30:53.370 --> 00:30:53.380 align:start position:0% so this is where the placard is printed 00:30:53.380 --> 00:30:56.560 align:start position:0% so this is where the placard is printed this<00:30:54.380> is<00:30:54.560> where<00:30:54.800> the<00:30:54.980> contents<00:30:55.850> of<00:30:55.970> the 00:30:56.560 --> 00:30:56.570 align:start position:0% this is where the contents of the 00:30:56.570 --> 00:30:59.800 align:start position:0% this is where the contents of the contracts<00:30:57.410> are<00:30:57.620> interpreted<00:30:58.460> by<00:30:58.640> l'a<00:30:59.540> caps 00:30:59.800 --> 00:30:59.810 align:start position:0% contracts are interpreted by l'a caps 00:30:59.810 --> 00:31:02.170 align:start position:0% contracts are interpreted by l'a caps Jas<00:31:00.230> if<00:31:00.560> you<00:31:01.130> remember<00:31:01.430> the<00:31:01.520> contract<00:31:02.000> had<00:31:02.150> a 00:31:02.170 --> 00:31:02.180 align:start position:0% Jas if you remember the contract had a 00:31:02.180 --> 00:31:03.940 align:start position:0% Jas if you remember the contract had a recipient<00:31:02.720> who<00:31:03.170> was<00:31:03.320> the<00:31:03.440> creator<00:31:03.650> of<00:31:03.830> the 00:31:03.940 --> 00:31:03.950 align:start position:0% recipient who was the creator of the 00:31:03.950 --> 00:31:07.120 align:start position:0% recipient who was the creator of the contract<00:31:04.640> a<00:31:04.910> number<00:31:05.510> of<00:31:05.600> contributors<00:31:06.200> and<00:31:06.470> a 00:31:07.120 --> 00:31:07.130 align:start position:0% contract a number of contributors and a 00:31:07.130 --> 00:31:10.450 align:start position:0% contract a number of contributors and a array<00:31:07.790> of<00:31:08.090> contributor<00:31:08.750> addresses<00:31:09.400> as<00:31:10.400> well 00:31:10.450 --> 00:31:10.460 align:start position:0% array of contributor addresses as well 00:31:10.460 --> 00:31:17.590 align:start position:0% array of contributor addresses as well as<00:31:11.000> a<00:31:11.300> mapping<00:31:12.080> of<00:31:12.460> a<00:31:14.530> mapping<00:31:15.530> of<00:31:16.600> contributor 00:31:17.590 --> 00:31:17.600 align:start position:0% as a mapping of a mapping of contributor 00:31:17.600 --> 00:31:20.440 align:start position:0% as a mapping of a mapping of contributor data<00:31:18.080> so<00:31:18.950> I've<00:31:19.610> done<00:31:19.850> a<00:31:19.910> little<00:31:20.000> bit<00:31:20.240> of 00:31:20.440 --> 00:31:20.450 align:start position:0% data so I've done a little bit of 00:31:20.450 --> 00:31:23.920 align:start position:0% data so I've done a little bit of functional<00:31:21.020> style<00:31:21.820> coding<00:31:22.820> to<00:31:23.090> extract<00:31:23.690> the 00:31:23.920 --> 00:31:23.930 align:start position:0% functional style coding to extract the 00:31:23.930 --> 00:31:27.100 align:start position:0% functional style coding to extract the information<00:31:24.140> from<00:31:24.620> the<00:31:25.990> from<00:31:26.990> the 00:31:27.100 --> 00:31:27.110 align:start position:0% information from the from the 00:31:27.110 --> 00:31:29.980 align:start position:0% information from the from the contributors<00:31:27.620> there<00:31:27.920> what<00:31:28.790> I<00:31:28.820> did<00:31:29.030> was<00:31:29.210> I<00:31:29.360> yeah 00:31:29.980 --> 00:31:29.990 align:start position:0% contributors there what I did was I yeah 00:31:29.990 --> 00:31:33.130 align:start position:0% contributors there what I did was I yeah I<00:31:30.470> happen<00:31:31.130> to<00:31:31.160> know<00:31:31.400> that<00:31:31.730> the<00:31:32.240> contribute 00:31:33.130 --> 00:31:33.140 align:start position:0% I happen to know that the contribute 00:31:33.140 --> 00:31:37.030 align:start position:0% I happen to know that the contribute info<00:31:33.500> member<00:31:34.430> of<00:31:34.700> the<00:31:35.020> contract<00:31:36.040> remember 00:31:37.030 --> 00:31:37.040 align:start position:0% info member of the contract remember 00:31:37.040 --> 00:31:38.260 align:start position:0% info member of the contract remember that<00:31:37.160> was<00:31:37.310> a<00:31:37.340> mapping<00:31:37.760> in<00:31:37.880> the<00:31:37.910> solidity 00:31:38.260 --> 00:31:38.270 align:start position:0% that was a mapping in the solidity 00:31:38.270 --> 00:31:40.240 align:start position:0% that was a mapping in the solidity contract<00:31:38.810> and<00:31:39.050> a<00:31:39.290> mapping<00:31:39.680> is<00:31:39.800> nothing<00:31:40.130> other 00:31:40.240 --> 00:31:40.250 align:start position:0% contract and a mapping is nothing other 00:31:40.250 --> 00:31:41.950 align:start position:0% contract and a mapping is nothing other than<00:31:40.370> a<00:31:40.520> function<00:31:41.030> from<00:31:41.210> its<00:31:41.450> keys<00:31:41.660> to<00:31:41.840> its 00:31:41.950 --> 00:31:41.960 align:start position:0% than a function from its keys to its 00:31:41.960 --> 00:31:44.230 align:start position:0% than a function from its keys to its values<00:31:42.380> and<00:31:42.560> that's<00:31:42.620> how<00:31:43.060> mappings<00:31:44.060> are 00:31:44.230 --> 00:31:44.240 align:start position:0% values and that's how mappings are 00:31:44.240 --> 00:31:47.620 align:start position:0% values and that's how mappings are represented<00:31:44.810> in<00:31:44.930> in<00:31:45.350> block<00:31:45.740> fjs<00:31:46.340> so<00:31:47.270> I<00:31:47.300> just 00:31:47.620 --> 00:31:47.630 align:start position:0% represented in in block fjs so I just 00:31:47.630 --> 00:31:49.750 align:start position:0% represented in in block fjs so I just took<00:31:48.230> this<00:31:48.410> function<00:31:48.920> and<00:31:49.100> I<00:31:49.220> applied<00:31:49.520> it<00:31:49.670> to 00:31:49.750 --> 00:31:49.760 align:start position:0% took this function and I applied it to 00:31:49.760 --> 00:31:51.880 align:start position:0% took this function and I applied it to each<00:31:49.910> member<00:31:50.180> of<00:31:50.540> the<00:31:51.050> contributors<00:31:51.560> array 00:31:51.880 --> 00:31:51.890 align:start position:0% each member of the contributors array 00:31:51.890 --> 00:31:54.640 align:start position:0% each member of the contributors array whose<00:31:52.370> elements<00:31:53.000> or<00:31:53.090> addresses<00:31:53.630> and<00:31:53.900> that 00:31:54.640 --> 00:31:54.650 align:start position:0% whose elements or addresses and that 00:31:54.650 --> 00:31:56.260 align:start position:0% whose elements or addresses and that turns<00:31:54.890> the<00:31:55.070> array<00:31:55.220> of<00:31:55.340> addresses<00:31:55.790> into<00:31:55.940> array 00:31:56.260 --> 00:31:56.270 align:start position:0% turns the array of addresses into array 00:31:56.270 --> 00:31:59.020 align:start position:0% turns the array of addresses into array of<00:31:56.890> objects<00:31:57.890> containing<00:31:58.370> two<00:31:58.580> contributor 00:31:59.020 --> 00:31:59.030 align:start position:0% of objects containing two contributor 00:31:59.030 --> 00:32:01.690 align:start position:0% of objects containing two contributor information<00:31:59.660> that<00:32:00.230> was<00:32:00.350> put<00:32:00.560> in<00:32:00.650> there<00:32:00.890> when 00:32:01.690 --> 00:32:01.700 align:start position:0% information that was put in there when 00:32:01.700 --> 00:32:04.950 align:start position:0% information that was put in there when the<00:32:01.970> when<00:32:02.750> the<00:32:02.840> contract<00:32:03.230> was<00:32:03.320> invoked<00:32:03.940> and 00:32:04.950 --> 00:32:04.960 align:start position:0% the when the contract was invoked and 00:32:04.960 --> 00:32:07.150 align:start position:0% the when the contract was invoked and after<00:32:05.960> I've<00:32:06.050> obtained<00:32:06.380> all<00:32:06.560> of<00:32:06.680> those<00:32:06.800> things 00:32:07.150 --> 00:32:07.160 align:start position:0% after I've obtained all of those things 00:32:07.160 --> 00:32:09.640 align:start position:0% after I've obtained all of those things I<00:32:07.460> joined<00:32:08.270> the<00:32:08.390> contracts<00:32:09.020> with<00:32:09.170> with<00:32:09.560> the 00:32:09.640 --> 00:32:09.650 align:start position:0% I joined the contracts with with the 00:32:09.650 --> 00:32:12.670 align:start position:0% I joined the contracts with with the function<00:32:10.070> that<00:32:10.540> that<00:32:11.540> uses<00:32:11.900> their<00:32:12.050> values<00:32:12.440> and 00:32:12.670 --> 00:32:12.680 align:start position:0% function that that uses their values and 00:32:12.680 --> 00:32:14.170 align:start position:0% function that that uses their values and in<00:32:12.740> this<00:32:12.830> case<00:32:13.040> just<00:32:13.280> takes<00:32:13.490> the<00:32:13.610> recipient 00:32:14.170 --> 00:32:14.180 align:start position:0% in this case just takes the recipient 00:32:14.180 --> 00:32:15.640 align:start position:0% in this case just takes the recipient the<00:32:14.390> contributor<00:32:14.900> know<00:32:15.080> the<00:32:15.320> number<00:32:15.590> of 00:32:15.640 --> 00:32:15.650 align:start position:0% the contributor know the number of 00:32:15.650 --> 00:32:18.100 align:start position:0% the contributor know the number of contributions<00:32:16.250> and<00:32:16.910> the<00:32:17.240> information<00:32:17.840> of<00:32:17.990> all 00:32:18.100 --> 00:32:18.110 align:start position:0% contributions and the information of all 00:32:18.110 --> 00:32:20.890 align:start position:0% contributions and the information of all the<00:32:18.230> contributors<00:32:18.740> and<00:32:19.420> prints<00:32:20.420> out<00:32:20.570> a<00:32:20.600> number 00:32:20.890 --> 00:32:20.900 align:start position:0% the contributors and prints out a number 00:32:20.900 --> 00:32:23.200 align:start position:0% the contributors and prints out a number of<00:32:20.990> lines<00:32:21.170> explaining<00:32:21.860> what<00:32:22.010> exactly<00:32:22.040> was<00:32:23.030> in 00:32:23.200 --> 00:32:23.210 align:start position:0% of lines explaining what exactly was in 00:32:23.210 --> 00:32:25.570 align:start position:0% of lines explaining what exactly was in all<00:32:23.330> of<00:32:23.480> that<00:32:23.660> and<00:32:24.040> well<00:32:25.040> you<00:32:25.130> can<00:32:25.280> see<00:32:25.460> the 00:32:25.570 --> 00:32:25.580 align:start position:0% all of that and well you can see the 00:32:25.580 --> 00:32:27.520 align:start position:0% all of that and well you can see the results<00:32:26.000> up<00:32:26.120> here<00:32:26.420> I<00:32:26.600> don't<00:32:27.200> need<00:32:27.320> to<00:32:27.410> go 00:32:27.520 --> 00:32:27.530 align:start position:0% results up here I don't need to go 00:32:27.530 --> 00:32:30.820 align:start position:0% results up here I don't need to go through<00:32:27.770> the<00:32:28.090> the<00:32:29.290> user<00:32:30.290> interface 00:32:30.820 --> 00:32:30.830 align:start position:0% through the the user interface 00:32:30.830 --> 00:32:32.320 align:start position:0% through the the user interface formatting<00:32:31.430> that<00:32:31.520> goes<00:32:31.880> into<00:32:32.060> that 00:32:32.320 --> 00:32:32.330 align:start position:0% formatting that goes into that 00:32:32.330 --> 00:32:34.240 align:start position:0% formatting that goes into that easily<00:32:32.750> the<00:32:32.780> least<00:32:33.230> interesting<00:32:33.770> part<00:32:33.980> of<00:32:34.100> any 00:32:34.240 --> 00:32:34.250 align:start position:0% easily the least interesting part of any 00:32:34.250 --> 00:32:38.740 align:start position:0% easily the least interesting part of any program<00:32:34.930> writing<00:32:36.700> writing<00:32:37.700> writing<00:32:37.880> text<00:32:38.660> to 00:32:38.740 --> 00:32:38.750 align:start position:0% program writing writing writing text to 00:32:38.750 --> 00:32:42.040 align:start position:0% program writing writing writing text to output<00:32:39.110> something<00:32:39.350> I<00:32:39.740> could<00:32:40.310> give<00:32:40.430> more<00:32:41.050> turns 00:32:42.040 --> 00:32:42.050 align:start position:0% output something I could give more turns 00:32:42.050 --> 00:32:43.570 align:start position:0% output something I could give more turns out<00:32:42.230> that<00:32:42.410> I<00:32:42.470> really<00:32:42.740> like<00:32:42.890> this<00:32:43.070> guy<00:32:43.310> I'm 00:32:43.570 --> 00:32:43.580 align:start position:0% out that I really like this guy I'm 00:32:43.580 --> 00:32:46.380 align:start position:0% out that I really like this guy I'm gonna<00:32:43.730> give<00:32:43.940> five<00:32:44.180> more<00:32:44.420> ether<00:32:44.600> so<00:32:45.440> I 00:32:46.380 --> 00:32:46.390 align:start position:0% gonna give five more ether so I 00:32:46.390 --> 00:32:51.010 align:start position:0% gonna give five more ether so I contribute<00:32:47.390> once<00:32:47.600> again<00:32:47.900> and<00:32:49.480> now<00:32:50.480> I've<00:32:50.780> given 00:32:51.010 --> 00:32:51.020 align:start position:0% contribute once again and now I've given 00:32:51.020 --> 00:32:54.670 align:start position:0% contribute once again and now I've given 15<00:32:51.640> my<00:32:52.640> brother<00:32:52.880> Doug<00:32:53.210> who<00:32:54.110> makes<00:32:54.440> more<00:32:54.620> money 00:32:54.670 --> 00:32:54.680 align:start position:0% 15 my brother Doug who makes more money 00:32:54.680 --> 00:32:57.610 align:start position:0% 15 my brother Doug who makes more money than<00:32:54.920> I<00:32:55.160> do<00:32:55.220> wants<00:32:55.610> to<00:32:55.700> give<00:32:55.820> 20<00:32:56.290> he<00:32:57.290> makes<00:32:57.470> more 00:32:57.610 --> 00:32:57.620 align:start position:0% than I do wants to give 20 he makes more 00:32:57.620 --> 00:33:00.730 align:start position:0% than I do wants to give 20 he makes more money<00:32:57.770> because<00:32:57.920> he<00:32:58.100> works<00:32:58.250> at<00:32:58.400> a<00:32:58.430> bank 00:33:00.730 --> 00:33:00.740 align:start position:0% 00:33:00.740 --> 00:33:05.779 align:start position:0% for<00:33:01.740> now<00:33:01.950> yeah<00:33:03.919> soon<00:33:04.919> I<00:33:05.100> hope<00:33:05.249> I<00:33:05.429> won't<00:33:05.610> be<00:33:05.700> the 00:33:05.779 --> 00:33:05.789 align:start position:0% for now yeah soon I hope I won't be the 00:33:05.789 --> 00:33:10.430 align:start position:0% for now yeah soon I hope I won't be the one<00:33:05.820> making<00:33:06.059> more<00:33:06.389> money<00:33:08.419> so<00:33:09.419> Doug<00:33:09.990> is<00:33:10.139> given 00:33:10.430 --> 00:33:10.440 align:start position:0% one making more money so Doug is given 00:33:10.440 --> 00:33:15.409 align:start position:0% one making more money so Doug is given 20<00:33:10.769> and<00:33:12.259> so<00:33:13.259> let's<00:33:13.830> close<00:33:14.129> off<00:33:14.340> this<00:33:14.549> this 00:33:15.409 --> 00:33:15.419 align:start position:0% 20 and so let's close off this this 00:33:15.419 --> 00:33:17.149 align:start position:0% 20 and so let's close off this this little<00:33:15.600> round<00:33:15.869> of<00:33:15.960> crowdsourcing<00:33:16.769> and<00:33:16.950> pay 00:33:17.149 --> 00:33:17.159 align:start position:0% little round of crowdsourcing and pay 00:33:17.159 --> 00:33:21.560 align:start position:0% little round of crowdsourcing and pay the<00:33:17.309> guy<00:33:17.460> whoever<00:33:18.240> that<00:33:18.419> guy<00:33:18.659> is<00:33:20.059> so<00:33:21.059> pay<00:33:21.450> the 00:33:21.560 --> 00:33:21.570 align:start position:0% the guy whoever that guy is so pay the 00:33:21.570 --> 00:33:24.529 align:start position:0% the guy whoever that guy is so pay the recipient<00:33:22.879> turns<00:33:23.879> out<00:33:23.999> he<00:33:24.149> raised<00:33:24.330> thirty 00:33:24.529 --> 00:33:24.539 align:start position:0% recipient turns out he raised thirty 00:33:24.539 --> 00:33:26.359 align:start position:0% recipient turns out he raised thirty five<00:33:24.749> and<00:33:25.200> what<00:33:25.409> actually<00:33:25.590> happens<00:33:26.220> when<00:33:26.279> I 00:33:26.359 --> 00:33:26.369 align:start position:0% five and what actually happens when I 00:33:26.369 --> 00:33:30.440 align:start position:0% five and what actually happens when I did<00:33:26.610> that<00:33:26.789> is<00:33:27.059> I<00:33:27.929> had<00:33:28.139> a<00:33:28.409> final<00:33:29.340> method<00:33:29.700> in<00:33:30.090> the 00:33:30.440 --> 00:33:30.450 align:start position:0% did that is I had a final method in the 00:33:30.450 --> 00:33:33.440 align:start position:0% did that is I had a final method in the contract<00:33:31.139> let<00:33:31.409> me<00:33:31.529> just<00:33:31.799> sort<00:33:31.980> of<00:33:32.269> scroll<00:33:33.269> back 00:33:33.440 --> 00:33:33.450 align:start position:0% contract let me just sort of scroll back 00:33:33.450 --> 00:33:35.119 align:start position:0% contract let me just sort of scroll back up<00:33:33.480> to<00:33:33.659> the<00:33:33.840> source<00:33:34.139> code<00:33:34.440> so<00:33:34.470> I<00:33:34.710> can<00:33:34.919> point 00:33:35.119 --> 00:33:35.129 align:start position:0% up to the source code so I can point 00:33:35.129 --> 00:33:36.379 align:start position:0% up to the source code so I can point that<00:33:35.190> out<00:33:35.309> to<00:33:35.639> you<00:33:35.759> because<00:33:35.789> it<00:33:36.059> was<00:33:36.149> very 00:33:36.379 --> 00:33:36.389 align:start position:0% that out to you because it was very 00:33:36.389 --> 00:33:41.749 align:start position:0% that out to you because it was very small<00:33:37.549> payout<00:33:39.259> suicides<00:33:40.259> the<00:33:40.590> contract<00:33:41.100> it 00:33:41.749 --> 00:33:41.759 align:start position:0% small payout suicides the contract it 00:33:41.759 --> 00:33:44.090 align:start position:0% small payout suicides the contract it closes<00:33:42.360> it<00:33:42.509> out<00:33:42.629> and<00:33:42.990> pays<00:33:43.499> all<00:33:43.649> the<00:33:43.679> money<00:33:43.950> to 00:33:44.090 --> 00:33:44.100 align:start position:0% closes it out and pays all the money to 00:33:44.100 --> 00:33:47.230 align:start position:0% closes it out and pays all the money to the<00:33:44.190> recipient<00:33:44.730> and<00:33:45.470> way<00:33:46.470> down<00:33:46.499> here 00:33:47.230 --> 00:33:47.240 align:start position:0% the recipient and way down here 00:33:47.240 --> 00:33:50.749 align:start position:0% the recipient and way down here the<00:33:48.240> payout<00:33:48.929> button<00:33:49.320> just<00:33:49.799> invokes<00:33:50.369> the 00:33:50.749 --> 00:33:50.759 align:start position:0% the payout button just invokes the 00:33:50.759 --> 00:33:53.090 align:start position:0% the payout button just invokes the payout<00:33:51.480> function<00:33:51.749> calls<00:33:52.710> it<00:33:52.860> from<00:33:53.009> the 00:33:53.090 --> 00:33:53.100 align:start position:0% payout function calls it from the 00:33:53.100 --> 00:33:56.080 align:start position:0% payout function calls it from the private<00:33:53.490> key<00:33:53.700> and<00:33:54.110> that<00:33:55.110> function<00:33:55.679> invocation 00:33:56.080 --> 00:33:56.090 align:start position:0% private key and that function invocation 00:33:56.090 --> 00:34:01.580 align:start position:0% private key and that function invocation returns<00:33:57.090> a<00:33:57.539> value<00:33:59.690> but<00:34:00.690> in<00:34:00.840> this<00:34:00.990> case<00:34:01.169> it 00:34:01.580 --> 00:34:01.590 align:start position:0% returns a value but in this case it 00:34:01.590 --> 00:34:04.159 align:start position:0% returns a value but in this case it doesn't<00:34:01.769> return<00:34:02.070> anything<00:34:02.399> so<00:34:03.119> in<00:34:03.539> contract 00:34:04.159 --> 00:34:04.169 align:start position:0% doesn't return anything so in contract 00:34:04.169 --> 00:34:05.720 align:start position:0% doesn't return anything so in contract language<00:34:04.529> I<00:34:04.679> just<00:34:04.710> replaced<00:34:05.340> the<00:34:05.490> return 00:34:05.720 --> 00:34:05.730 align:start position:0% language I just replaced the return 00:34:05.730 --> 00:34:07.700 align:start position:0% language I just replaced the return value<00:34:06.240> with<00:34:06.419> what<00:34:06.899> I<00:34:06.929> want<00:34:07.230> to<00:34:07.320> see<00:34:07.499> which<00:34:07.679> is 00:34:07.700 --> 00:34:07.710 align:start position:0% value with what I want to see which is 00:34:07.710 --> 00:34:09.740 align:start position:0% value with what I want to see which is the<00:34:07.860> balance<00:34:08.250> of<00:34:08.339> the<00:34:08.460> contract<00:34:08.940> and<00:34:09.210> then<00:34:09.690> I 00:34:09.740 --> 00:34:09.750 align:start position:0% the balance of the contract and then I 00:34:09.750 --> 00:34:17.809 align:start position:0% the balance of the contract and then I format<00:34:10.109> a<00:34:10.169> line<00:34:10.379> that<00:34:10.559> displays<00:34:10.889> it<00:34:12.020> so<00:34:15.619> as<00:34:16.819> you 00:34:17.809 --> 00:34:17.819 align:start position:0% format a line that displays it so as you 00:34:17.819 --> 00:34:21.500 align:start position:0% format a line that displays it so as you can<00:34:17.970> see<00:34:18.240> this<00:34:19.049> is<00:34:19.230> the<00:34:19.349> same<00:34:19.849> basic<00:34:20.849> operation 00:34:21.500 --> 00:34:21.510 align:start position:0% can see this is the same basic operation 00:34:21.510 --> 00:34:24.349 align:start position:0% can see this is the same basic operation that<00:34:22.079> you<00:34:22.500> witnessed<00:34:22.950> with<00:34:23.339> with<00:34:23.970> Kieran's 00:34:24.349 --> 00:34:24.359 align:start position:0% that you witnessed with with Kieran's 00:34:24.359 --> 00:34:26.659 align:start position:0% that you witnessed with with Kieran's example<00:34:24.750> in<00:34:24.869> Strato<00:34:25.230> but<00:34:25.889> more<00:34:26.069> customized 00:34:26.659 --> 00:34:26.669 align:start position:0% example in Strato but more customized 00:34:26.669 --> 00:34:29.000 align:start position:0% example in Strato but more customized miss<00:34:27.299> Trudeau<00:34:27.629> has<00:34:27.960> your<00:34:28.139> scaffolded<00:34:28.799> page 00:34:29.000 --> 00:34:29.010 align:start position:0% miss Trudeau has your scaffolded page 00:34:29.010 --> 00:34:34.369 align:start position:0% miss Trudeau has your scaffolded page already<00:34:29.369> for<00:34:29.790> you<00:34:30.139> with<00:34:32.419> with<00:34:33.419> block<00:34:33.659> EPS<00:34:33.869> j/s 00:34:34.369 --> 00:34:34.379 align:start position:0% already for you with with block EPS j/s 00:34:34.379 --> 00:34:36.919 align:start position:0% already for you with with block EPS j/s you'll<00:34:35.129> want<00:34:35.490> to<00:34:35.549> write<00:34:35.730> your<00:34:35.909> HTML<00:34:36.480> yourself 00:34:36.919 --> 00:34:36.929 align:start position:0% you'll want to write your HTML yourself 00:34:36.929 --> 00:34:39.619 align:start position:0% you'll want to write your HTML yourself or<00:34:37.169> if<00:34:37.589> you<00:34:38.129> start<00:34:38.490> with<00:34:38.639> your<00:34:38.700> Strato<00:34:39.059> if<00:34:39.510> you 00:34:39.619 --> 00:34:39.629 align:start position:0% or if you start with your Strato if you 00:34:39.629 --> 00:34:41.000 align:start position:0% or if you start with your Strato if you start<00:34:39.869> with<00:34:39.929> your<00:34:39.990> shadow<00:34:40.349> page<00:34:40.649> you<00:34:40.859> can 00:34:41.000 --> 00:34:41.010 align:start position:0% start with your shadow page you can 00:34:41.010 --> 00:34:43.520 align:start position:0% start with your shadow page you can tweak<00:34:41.220> it<00:34:41.339> a<00:34:41.429> little<00:34:41.460> bit<00:34:41.869> and<00:34:42.869> knowing<00:34:43.379> how 00:34:43.520 --> 00:34:43.530 align:start position:0% tweak it a little bit and knowing how 00:34:43.530 --> 00:34:45.200 align:start position:0% tweak it a little bit and knowing how block<00:34:43.770> fjs<00:34:44.280> works<00:34:44.520> you<00:34:44.700> can<00:34:44.849> add<00:34:45.000> more 00:34:45.200 --> 00:34:45.210 align:start position:0% block fjs works you can add more 00:34:45.210 --> 00:34:47.750 align:start position:0% block fjs works you can add more functionality<00:34:45.929> than<00:34:46.109> simply<00:34:46.490> than<00:34:47.490> simply 00:34:47.750 --> 00:34:47.760 align:start position:0% functionality than simply than simply 00:34:47.760 --> 00:34:50.359 align:start position:0% functionality than simply than simply showing<00:34:48.059> the<00:34:48.450> storage<00:34:49.109> contents<00:34:49.829> of<00:34:49.950> the 00:34:50.359 --> 00:34:50.369 align:start position:0% showing the storage contents of the 00:34:50.369 --> 00:34:54.109 align:start position:0% showing the storage contents of the address<00:34:50.669> you're<00:34:50.879> working<00:34:51.240> with<00:34:52.819> lockups<00:34:53.819> GS 00:34:54.109 --> 00:34:54.119 align:start position:0% address you're working with lockups GS 00:34:54.119 --> 00:34:59.140 align:start position:0% address you're working with lockups GS is<00:34:54.389> the<00:34:54.809> power<00:34:55.679> users<00:34:56.420> is<00:34:57.420> the<00:34:57.599> power<00:34:57.780> users 00:34:59.140 --> 00:34:59.150 align:start position:0% is the power users is the power users 00:34:59.150 --> 00:35:02.059 align:start position:0% is the power users is the power users inroads<00:35:00.150> to<00:35:00.480> connecting<00:35:01.290> aetherium<00:35:01.770> to<00:35:01.950> the 00:35:02.059 --> 00:35:02.069 align:start position:0% inroads to connecting aetherium to the 00:35:02.069 --> 00:35:04.700 align:start position:0% inroads to connecting aetherium to the web<00:35:02.869> anything<00:35:03.869> you<00:35:03.960> can<00:35:04.109> do<00:35:04.200> with<00:35:04.319> solidity 00:35:04.700 --> 00:35:04.710 align:start position:0% web anything you can do with solidity 00:35:04.710 --> 00:35:08.150 align:start position:0% web anything you can do with solidity you<00:35:05.130> can<00:35:05.480> you<00:35:06.480> can<00:35:06.660> benefit<00:35:07.079> from<00:35:07.140> in<00:35:07.680> your 00:35:08.150 --> 00:35:08.160 align:start position:0% you can you can benefit from in your 00:35:08.160 --> 00:35:10.920 align:start position:0% you can you can benefit from in your application<00:35:08.849> by<00:35:09.180> running<00:35:09.420> this<00:35:09.599> library 00:35:10.920 --> 00:35:10.930 align:start position:0% application by running this library 00:35:10.930 --> 00:35:13.810 align:start position:0% application by running this library so<00:35:11.930> let's<00:35:12.560> go<00:35:12.680> back<00:35:12.710> to<00:35:12.860> this<00:35:13.070> slide<00:35:13.220> and<00:35:13.610> press 00:35:13.810 --> 00:35:13.820 align:start position:0% so let's go back to this slide and press 00:35:13.820 --> 00:35:15.570 align:start position:0% so let's go back to this slide and press spacebar<00:35:14.300> again 00:35:15.570 --> 00:35:15.580 align:start position:0% spacebar again 00:35:15.580 --> 00:35:18.700 align:start position:0% spacebar again thank<00:35:16.580> you<00:35:16.700> for<00:35:17.440> receiving<00:35:18.440> this 00:35:18.700 --> 00:35:18.710 align:start position:0% thank you for receiving this 00:35:18.710 --> 00:35:21.100 align:start position:0% thank you for receiving this presentation<00:35:19.540> we're<00:35:20.540> happy<00:35:20.780> to<00:35:20.870> give<00:35:20.990> this 00:35:21.100 --> 00:35:21.110 align:start position:0% presentation we're happy to give this 00:35:21.110 --> 00:35:24.760 align:start position:0% presentation we're happy to give this technology<00:35:21.800> to<00:35:21.980> you<00:35:22.100> to<00:35:22.400> enjoy<00:35:22.850> to<00:35:23.560> and<00:35:24.560> to 00:35:24.760 --> 00:35:24.770 align:start position:0% technology to you to enjoy to and to 00:35:24.770 --> 00:35:27.730 align:start position:0% technology to you to enjoy to and to build<00:35:25.040> wonderful<00:35:25.970> wonderful<00:35:26.870> aetherium<00:35:27.530> apps 00:35:27.730 --> 00:35:27.740 align:start position:0% build wonderful wonderful aetherium apps 00:35:27.740 --> 00:35:30.010 align:start position:0% build wonderful wonderful aetherium apps with