WEBVTT Kind: captions Language: en 00:00:04.490 --> 00:00:07.180 align:start position:0% okay<00:00:05.480> I'm<00:00:05.690> Nikhil<00:00:06.020> I'm<00:00:06.230> the<00:00:06.500> CEO<00:00:06.680> of<00:00:06.770> alchemy 00:00:07.180 --> 00:00:07.190 align:start position:0% okay I'm Nikhil I'm the CEO of alchemy 00:00:07.190 --> 00:00:09.340 align:start position:0% okay I'm Nikhil I'm the CEO of alchemy hopefully<00:00:08.149> you're<00:00:08.270> here<00:00:08.360> for<00:00:08.570> this<00:00:08.690> talk<00:00:08.900> if 00:00:09.340 --> 00:00:09.350 align:start position:0% hopefully you're here for this talk if 00:00:09.350 --> 00:00:11.110 align:start position:0% hopefully you're here for this talk if not<00:00:09.620> you<00:00:09.950> should<00:00:10.010> just<00:00:10.190> stay<00:00:10.370> cuz<00:00:10.670> it's<00:00:11.000> gonna 00:00:11.110 --> 00:00:11.120 align:start position:0% not you should just stay cuz it's gonna 00:00:11.120 --> 00:00:13.629 align:start position:0% not you should just stay cuz it's gonna be<00:00:11.299> hopefully<00:00:11.630> good<00:00:12.220> we're<00:00:13.220> gonna<00:00:13.370> talk<00:00:13.460> about 00:00:13.629 --> 00:00:13.639 align:start position:0% be hopefully good we're gonna talk about 00:00:13.639 --> 00:00:16.299 align:start position:0% be hopefully good we're gonna talk about designing<00:00:14.000> protocols<00:00:14.510> for<00:00:15.110> api's<00:00:15.830> today<00:00:16.130> and 00:00:16.299 --> 00:00:16.309 align:start position:0% designing protocols for api's today and 00:00:16.309 --> 00:00:17.769 align:start position:0% designing protocols for api's today and it's<00:00:17.029> gonna<00:00:17.119> go<00:00:17.270> into<00:00:17.390> a<00:00:17.450> couple<00:00:17.630> details 00:00:17.769 --> 00:00:17.779 align:start position:0% it's gonna go into a couple details 00:00:17.779 --> 00:00:19.510 align:start position:0% it's gonna go into a couple details about<00:00:18.170> aetherium<00:00:18.590> and<00:00:18.830> some<00:00:19.009> of<00:00:19.099> the<00:00:19.160> projects 00:00:19.510 --> 00:00:19.520 align:start position:0% about aetherium and some of the projects 00:00:19.520 --> 00:00:22.810 align:start position:0% about aetherium and some of the projects that<00:00:19.610> we've<00:00:19.730> done<00:00:19.759> so<00:00:20.689> quick<00:00:21.650> roadmap<00:00:22.189> talk 00:00:22.810 --> 00:00:22.820 align:start position:0% that we've done so quick roadmap talk 00:00:22.820 --> 00:00:24.700 align:start position:0% that we've done so quick roadmap talk about<00:00:23.029> the<00:00:23.119> background<00:00:23.270> a<00:00:23.810> little<00:00:24.200> bit<00:00:24.349> about 00:00:24.700 --> 00:00:24.710 align:start position:0% about the background a little bit about 00:00:24.710 --> 00:00:25.389 align:start position:0% about the background a little bit about what<00:00:24.890> we<00:00:24.950> do 00:00:25.389 --> 00:00:25.399 align:start position:0% what we do 00:00:25.399 --> 00:00:27.760 align:start position:0% what we do why<00:00:25.880> developer<00:00:26.779> API<00:00:26.960> sort<00:00:27.200> of<00:00:27.259> been<00:00:27.349> important 00:00:27.760 --> 00:00:27.770 align:start position:0% why developer API sort of been important 00:00:27.770 --> 00:00:30.370 align:start position:0% why developer API sort of been important talk<00:00:28.310> about<00:00:28.489> how<00:00:28.550> to<00:00:28.610> enhance<00:00:28.790> aetherium<00:00:29.660> and 00:00:30.370 --> 00:00:30.380 align:start position:0% talk about how to enhance aetherium and 00:00:30.380 --> 00:00:31.900 align:start position:0% talk about how to enhance aetherium and then<00:00:30.500> go<00:00:30.590> into<00:00:30.710> cheese<00:00:30.950> wizards<00:00:31.279> and<00:00:31.520> a<00:00:31.790> few 00:00:31.900 --> 00:00:31.910 align:start position:0% then go into cheese wizards and a few 00:00:31.910 --> 00:00:34.540 align:start position:0% then go into cheese wizards and a few design<00:00:32.210> principles<00:00:32.829> so<00:00:33.829> a<00:00:34.040> little<00:00:34.309> bit<00:00:34.520> a 00:00:34.540 --> 00:00:34.550 align:start position:0% design principles so a little bit a 00:00:34.550 --> 00:00:36.610 align:start position:0% design principles so a little bit a brief<00:00:35.030> background<00:00:35.239> of<00:00:35.480> me<00:00:35.600> we've<00:00:36.260> been<00:00:36.380> pretty 00:00:36.610 --> 00:00:36.620 align:start position:0% brief background of me we've been pretty 00:00:36.620 --> 00:00:38.410 align:start position:0% brief background of me we've been pretty quiet<00:00:36.829> as<00:00:37.190> a<00:00:37.219> company<00:00:37.609> so<00:00:37.850> just<00:00:38.090> want<00:00:38.239> to<00:00:38.269> share 00:00:38.410 --> 00:00:38.420 align:start position:0% quiet as a company so just want to share 00:00:38.420 --> 00:00:39.819 align:start position:0% quiet as a company so just want to share so<00:00:38.660> my<00:00:39.050> background<00:00:39.410> is<00:00:39.440> actually<00:00:39.769> an 00:00:39.819 --> 00:00:39.829 align:start position:0% so my background is actually an 00:00:39.829 --> 00:00:41.099 align:start position:0% so my background is actually an artificial<00:00:40.160> intelligence<00:00:40.670> that<00:00:40.730> Stanford 00:00:41.099 --> 00:00:41.109 align:start position:0% artificial intelligence that Stanford 00:00:41.109 --> 00:00:43.119 align:start position:0% artificial intelligence that Stanford did<00:00:42.109> a<00:00:42.170> bunch<00:00:42.260> of<00:00:42.350> research<00:00:42.589> there<00:00:42.890> and 00:00:43.119 --> 00:00:43.129 align:start position:0% did a bunch of research there and 00:00:43.129 --> 00:00:45.549 align:start position:0% did a bunch of research there and previously<00:00:44.000> my<00:00:44.149> co-founder<00:00:44.539> Joe<00:00:44.750> and<00:00:44.960> I<00:00:45.019> did 00:00:45.549 --> 00:00:45.559 align:start position:0% previously my co-founder Joe and I did 00:00:45.559 --> 00:00:46.779 align:start position:0% previously my co-founder Joe and I did consumer<00:00:45.980> apps<00:00:46.129> and<00:00:46.339> one<00:00:46.429> of<00:00:46.519> the<00:00:46.579> apps<00:00:46.699> we 00:00:46.779 --> 00:00:46.789 align:start position:0% consumer apps and one of the apps we 00:00:46.789 --> 00:00:48.459 align:start position:0% consumer apps and one of the apps we built<00:00:47.030> kind<00:00:47.420> of<00:00:47.510> for<00:00:47.660> fun<00:00:47.690> ended<00:00:48.170> up<00:00:48.260> being<00:00:48.410> the 00:00:48.459 --> 00:00:48.469 align:start position:0% built kind of for fun ended up being the 00:00:48.469 --> 00:00:49.959 align:start position:0% built kind of for fun ended up being the gnome<00:00:48.620> own<00:00:48.739> app<00:00:48.859> on<00:00:48.980> the<00:00:49.039> App<00:00:49.160> Store<00:00:49.399> so<00:00:49.640> we<00:00:49.820> did 00:00:49.959 --> 00:00:49.969 align:start position:0% gnome own app on the App Store so we did 00:00:49.969 --> 00:00:51.819 align:start position:0% gnome own app on the App Store so we did that<00:00:50.089> for<00:00:50.239> many<00:00:50.390> years<00:00:50.600> and<00:00:51.379> then<00:00:51.499> we<00:00:51.559> started 00:00:51.819 --> 00:00:51.829 align:start position:0% that for many years and then we started 00:00:51.829 --> 00:00:53.310 align:start position:0% that for many years and then we started doing<00:00:51.890> blockchain<00:00:52.309> stuff 00:00:53.310 --> 00:00:53.320 align:start position:0% doing blockchain stuff 00:00:53.320 --> 00:00:56.590 align:start position:0% doing blockchain stuff so<00:00:54.320> what<00:00:55.160> alchemy<00:00:55.609> does<00:00:55.789> is<00:00:56.059> we<00:00:56.269> power 00:00:56.590 --> 00:00:56.600 align:start position:0% so what alchemy does is we power 00:00:56.600 --> 00:00:58.630 align:start position:0% so what alchemy does is we power infrastructure<00:00:57.350> and<00:00:57.499> developer<00:00:57.829> tools<00:00:58.039> for<00:00:58.609> a 00:00:58.630 --> 00:00:58.640 align:start position:0% infrastructure and developer tools for a 00:00:58.640 --> 00:00:59.979 align:start position:0% infrastructure and developer tools for a bunch<00:00:59.120> of<00:00:59.210> different<00:00:59.449> people<00:00:59.570> across<00:00:59.839> the 00:00:59.979 --> 00:00:59.989 align:start position:0% bunch of different people across the 00:00:59.989 --> 00:01:01.509 align:start position:0% bunch of different people across the space<00:01:00.199> so<00:01:00.620> we've<00:01:00.739> we've<00:01:01.010> kind<00:01:01.249> of<00:01:01.280> been<00:01:01.399> in 00:01:01.509 --> 00:01:01.519 align:start position:0% space so we've we've kind of been in 00:01:01.519 --> 00:01:03.759 align:start position:0% space so we've we've kind of been in pseudo<00:01:01.969> stealth<00:01:02.329> but<00:01:03.230> we're<00:01:03.350> about<00:01:03.440> to<00:01:03.559> do 00:01:03.759 --> 00:01:03.769 align:start position:0% pseudo stealth but we're about to do 00:01:03.769 --> 00:01:06.490 align:start position:0% pseudo stealth but we're about to do kind<00:01:03.920> of<00:01:04.040> a<00:01:04.100> big<00:01:04.220> announcement<00:01:04.400> and<00:01:04.990> our<00:01:05.990> goal 00:01:06.490 --> 00:01:06.500 align:start position:0% kind of a big announcement and our goal 00:01:06.500 --> 00:01:08.050 align:start position:0% kind of a big announcement and our goal as<00:01:06.800> a<00:01:06.830> company<00:01:07.280> is<00:01:07.460> we<00:01:07.640> want<00:01:07.850> to<00:01:07.880> push 00:01:08.050 --> 00:01:08.060 align:start position:0% as a company is we want to push 00:01:08.060 --> 00:01:10.090 align:start position:0% as a company is we want to push blockchain<00:01:08.570> development<00:01:08.960> forward<00:01:09.200> by<00:01:09.770> we 00:01:10.090 --> 00:01:10.100 align:start position:0% blockchain development forward by we 00:01:10.100 --> 00:01:11.590 align:start position:0% blockchain development forward by we don't<00:01:10.250> push<00:01:10.369> the<00:01:10.490> whole<00:01:10.640> ecosystem<00:01:10.970> forward 00:01:11.590 --> 00:01:11.600 align:start position:0% don't push the whole ecosystem forward 00:01:11.600 --> 00:01:13.539 align:start position:0% don't push the whole ecosystem forward by<00:01:11.899> really<00:01:12.409> really<00:01:12.619> making<00:01:12.890> it<00:01:12.920> easy<00:01:13.189> for 00:01:13.539 --> 00:01:13.549 align:start position:0% by really really making it easy for 00:01:13.549 --> 00:01:15.160 align:start position:0% by really really making it easy for people<00:01:13.640> to<00:01:13.790> build<00:01:13.970> applications<00:01:14.170> because 00:01:15.160 --> 00:01:15.170 align:start position:0% people to build applications because 00:01:15.170 --> 00:01:16.690 align:start position:0% people to build applications because ultimately<00:01:15.500> what<00:01:16.009> we<00:01:16.130> think<00:01:16.369> and<00:01:16.549> what<00:01:16.670> we 00:01:16.690 --> 00:01:16.700 align:start position:0% ultimately what we think and what we 00:01:16.700 --> 00:01:18.580 align:start position:0% ultimately what we think and what we believe<00:01:16.880> is<00:01:17.270> in<00:01:17.509> order<00:01:17.990> for<00:01:18.140> blockchain<00:01:18.500> to 00:01:18.580 --> 00:01:18.590 align:start position:0% believe is in order for blockchain to 00:01:18.590 --> 00:01:20.350 align:start position:0% believe is in order for blockchain to reach<00:01:18.740> his<00:01:18.890> full<00:01:19.040> potential<00:01:19.399> we<00:01:19.939> really<00:01:20.210> need 00:01:20.350 --> 00:01:20.360 align:start position:0% reach his full potential we really need 00:01:20.360 --> 00:01:21.910 align:start position:0% reach his full potential we really need to<00:01:20.420> have<00:01:20.509> users<00:01:21.170> using<00:01:21.530> real-world 00:01:21.910 --> 00:01:21.920 align:start position:0% to have users using real-world 00:01:21.920 --> 00:01:24.340 align:start position:0% to have users using real-world applications<00:01:22.880> and<00:01:23.119> getting<00:01:23.780> value<00:01:24.049> from<00:01:24.140> that 00:01:24.340 --> 00:01:24.350 align:start position:0% applications and getting value from that 00:01:24.350 --> 00:01:26.050 align:start position:0% applications and getting value from that and<00:01:24.530> what<00:01:24.890> you<00:01:24.979> need<00:01:25.100> to<00:01:25.159> do<00:01:25.399> that<00:01:25.549> is<00:01:25.790> you<00:01:25.909> need 00:01:26.050 --> 00:01:26.060 align:start position:0% and what you need to do that is you need 00:01:26.060 --> 00:01:27.399 align:start position:0% and what you need to do that is you need to<00:01:26.090> make<00:01:26.270> it<00:01:26.390> really<00:01:26.719> really<00:01:26.750> easy<00:01:26.960> for 00:01:27.399 --> 00:01:27.409 align:start position:0% to make it really really easy for 00:01:27.409 --> 00:01:29.230 align:start position:0% to make it really really easy for developers<00:01:27.469> to<00:01:27.860> create<00:01:27.979> applications<00:01:28.159> so<00:01:28.850> our 00:01:29.230 --> 00:01:29.240 align:start position:0% developers to create applications so our 00:01:29.240 --> 00:01:31.450 align:start position:0% developers to create applications so our whole<00:01:29.570> focus<00:01:29.930> as<00:01:30.320> a<00:01:30.350> company<00:01:30.770> is<00:01:30.950> doing<00:01:31.340> that 00:01:31.450 --> 00:01:31.460 align:start position:0% whole focus as a company is doing that 00:01:31.460 --> 00:01:34.480 align:start position:0% whole focus as a company is doing that and<00:01:32.049> feel<00:01:33.049> free<00:01:33.170> to<00:01:33.200> come<00:01:33.560> by<00:01:33.710> and<00:01:33.979> ask<00:01:34.250> me<00:01:34.430> any 00:01:34.480 --> 00:01:34.490 align:start position:0% and feel free to come by and ask me any 00:01:34.490 --> 00:01:37.270 align:start position:0% and feel free to come by and ask me any questions<00:01:34.880> afterwards<00:01:35.299> about<00:01:35.479> this<00:01:35.659> so<00:01:36.320> what 00:01:37.270 --> 00:01:37.280 align:start position:0% questions afterwards about this so what 00:01:37.280 --> 00:01:39.279 align:start position:0% questions afterwards about this so what is<00:01:37.460> a<00:01:37.490> developer<00:01:37.939> API<00:01:38.180> you<00:01:38.270> and<00:01:38.750> I<00:01:39.020> know<00:01:39.079> this 00:01:39.279 --> 00:01:39.289 align:start position:0% is a developer API you and I know this 00:01:39.289 --> 00:01:40.660 align:start position:0% is a developer API you and I know this sounds<00:01:39.530> really<00:01:39.740> basic<00:01:40.219> but<00:01:40.340> I<00:01:40.369> just<00:01:40.490> want<00:01:40.640> to 00:01:40.660 --> 00:01:40.670 align:start position:0% sounds really basic but I just want to 00:01:40.670 --> 00:01:42.429 align:start position:0% sounds really basic but I just want to go<00:01:40.820> back<00:01:41.000> to<00:01:41.149> the<00:01:41.240> core<00:01:41.539> of<00:01:41.750> what<00:01:42.020> it<00:01:42.049> means<00:01:42.229> to 00:01:42.429 --> 00:01:42.439 align:start position:0% go back to the core of what it means to 00:01:42.439 --> 00:01:44.740 align:start position:0% go back to the core of what it means to create<00:01:43.100> an<00:01:43.219> API<00:01:43.460> for<00:01:43.549> developers<00:01:43.969> to<00:01:44.360> build 00:01:44.740 --> 00:01:44.750 align:start position:0% create an API for developers to build 00:01:44.750 --> 00:01:47.200 align:start position:0% create an API for developers to build products<00:01:45.320> right<00:01:45.560> and<00:01:45.909> ultimately<00:01:46.909> what<00:01:47.119> it 00:01:47.200 --> 00:01:47.210 align:start position:0% products right and ultimately what it 00:01:47.210 --> 00:01:49.209 align:start position:0% products right and ultimately what it means<00:01:47.359> is<00:01:47.570> it's<00:01:47.719> just<00:01:47.780> a<00:01:47.990> way<00:01:48.170> for<00:01:48.200> programs<00:01:49.130> to 00:01:49.209 --> 00:01:49.219 align:start position:0% means is it's just a way for programs to 00:01:49.219 --> 00:01:51.670 align:start position:0% means is it's just a way for programs to access<00:01:49.579> data<00:01:49.789> right<00:01:50.299> and<00:01:50.479> I<00:01:50.659> think<00:01:51.200> the<00:01:51.409> thing 00:01:51.670 --> 00:01:51.680 align:start position:0% access data right and I think the thing 00:01:51.680 --> 00:01:52.990 align:start position:0% access data right and I think the thing that<00:01:51.710> we<00:01:51.950> need<00:01:52.039> to<00:01:52.159> really<00:01:52.340> stress<00:01:52.729> on<00:01:52.909> as 00:01:52.990 --> 00:01:53.000 align:start position:0% that we need to really stress on as 00:01:53.000 --> 00:01:54.789 align:start position:0% that we need to really stress on as community<00:01:53.450> is<00:01:53.630> the<00:01:54.109> goal<00:01:54.350> is<00:01:54.500> to<00:01:54.619> make 00:01:54.789 --> 00:01:54.799 align:start position:0% community is the goal is to make 00:01:54.799 --> 00:01:56.770 align:start position:0% community is the goal is to make development<00:01:55.310> easy<00:01:55.609> right<00:01:56.210> we<00:01:56.390> need<00:01:56.570> to<00:01:56.689> make 00:01:56.770 --> 00:01:56.780 align:start position:0% development easy right we need to make 00:01:56.780 --> 00:01:58.899 align:start position:0% development easy right we need to make it<00:01:56.930> as<00:01:57.020> simple<00:01:57.259> as<00:01:57.469> possible<00:01:57.649> and<00:01:58.130> that<00:01:58.640> should 00:01:58.899 --> 00:01:58.909 align:start position:0% it as simple as possible and that should 00:01:58.909 --> 00:02:02.020 align:start position:0% it as simple as possible and that should be<00:01:59.000> our<00:01:59.030> whole<00:01:59.270> focus<00:01:59.530> and<00:02:00.530> today<00:02:01.369> right<00:02:02.000> now 00:02:02.020 --> 00:02:02.030 align:start position:0% be our whole focus and today right now 00:02:02.030 --> 00:02:04.240 align:start position:0% be our whole focus and today right now you<00:02:02.630> know<00:02:02.719> as<00:02:02.929> aetherium<00:02:03.350> is<00:02:03.500> evolved<00:02:03.890> people 00:02:04.240 --> 00:02:04.250 align:start position:0% you know as aetherium is evolved people 00:02:04.250 --> 00:02:05.380 align:start position:0% you know as aetherium is evolved people are<00:02:04.490> building<00:02:04.609> really<00:02:05.030> incredible 00:02:05.380 --> 00:02:05.390 align:start position:0% are building really incredible 00:02:05.390 --> 00:02:07.870 align:start position:0% are building really incredible applications<00:02:05.539> and<00:02:06.200> those<00:02:06.409> applications<00:02:06.880> need 00:02:07.870 --> 00:02:07.880 align:start position:0% applications and those applications need 00:02:07.880 --> 00:02:09.669 align:start position:0% applications and those applications need more<00:02:08.210> power<00:02:08.420> than<00:02:08.810> a<00:02:08.960> theory<00:02:09.200> was<00:02:09.320> initially 00:02:09.669 --> 00:02:09.679 align:start position:0% more power than a theory was initially 00:02:09.679 --> 00:02:11.170 align:start position:0% more power than a theory was initially designed<00:02:09.830> for<00:02:10.220> and<00:02:10.610> we'll<00:02:10.700> go<00:02:10.789> into<00:02:10.880> a<00:02:10.970> couple 00:02:11.170 --> 00:02:11.180 align:start position:0% designed for and we'll go into a couple 00:02:11.180 --> 00:02:12.840 align:start position:0% designed for and we'll go into a couple examples<00:02:11.600> of<00:02:11.660> what<00:02:11.720> that<00:02:11.870> means<00:02:12.170> but 00:02:12.840 --> 00:02:12.850 align:start position:0% examples of what that means but 00:02:12.850 --> 00:02:15.730 align:start position:0% examples of what that means but basically<00:02:13.850> and<00:02:14.150> then<00:02:14.840> actually<00:02:15.410> the<00:02:15.560> reason 00:02:15.730 --> 00:02:15.740 align:start position:0% basically and then actually the reason 00:02:15.740 --> 00:02:17.920 align:start position:0% basically and then actually the reason that<00:02:16.010> this<00:02:16.340> is<00:02:16.400> so<00:02:16.640> important<00:02:17.060> is<00:02:17.150> I<00:02:17.510> alluded 00:02:17.920 --> 00:02:17.930 align:start position:0% that this is so important is I alluded 00:02:17.930 --> 00:02:18.190 align:start position:0% that this is so important is I alluded to<00:02:17.960> the 00:02:18.190 --> 00:02:18.200 align:start position:0% to the 00:02:18.200 --> 00:02:20.770 align:start position:0% to the earlier<00:02:18.560> but<00:02:19.099> what<00:02:19.370> happens<00:02:19.760> is<00:02:19.940> we<00:02:20.599> actually 00:02:20.770 --> 00:02:20.780 align:start position:0% earlier but what happens is we actually 00:02:20.780 --> 00:02:23.170 align:start position:0% earlier but what happens is we actually want<00:02:21.080> to<00:02:21.440> have<00:02:21.890> more<00:02:22.430> people<00:02:22.700> using 00:02:23.170 --> 00:02:23.180 align:start position:0% want to have more people using 00:02:23.180 --> 00:02:24.580 align:start position:0% want to have more people using real-world<00:02:23.629> applications<00:02:24.260> if<00:02:24.379> we<00:02:24.440> want 00:02:24.580 --> 00:02:24.590 align:start position:0% real-world applications if we want 00:02:24.590 --> 00:02:25.930 align:start position:0% real-world applications if we want billions<00:02:24.920> of<00:02:24.950> people<00:02:25.310> to<00:02:25.400> use<00:02:25.519> blockchain 00:02:25.930 --> 00:02:25.940 align:start position:0% billions of people to use blockchain 00:02:25.940 --> 00:02:27.880 align:start position:0% billions of people to use blockchain when<00:02:26.330> you<00:02:26.420> have<00:02:26.540> real<00:02:26.840> concrete<00:02:27.200> applications 00:02:27.880 --> 00:02:27.890 align:start position:0% when you have real concrete applications 00:02:27.890 --> 00:02:29.320 align:start position:0% when you have real concrete applications that<00:02:27.980> provide<00:02:28.099> tangible<00:02:28.760> value<00:02:28.879> to<00:02:29.150> them<00:02:29.300> in 00:02:29.320 --> 00:02:29.330 align:start position:0% that provide tangible value to them in 00:02:29.330 --> 00:02:30.160 align:start position:0% that provide tangible value to them in their<00:02:29.540> daily<00:02:29.720> lives 00:02:30.160 --> 00:02:30.170 align:start position:0% their daily lives 00:02:30.170 --> 00:02:31.990 align:start position:0% their daily lives in<00:02:30.260> order<00:02:30.769> to<00:02:30.860> do<00:02:31.010> that<00:02:31.160> we<00:02:31.610> need<00:02:31.760> to<00:02:31.849> make 00:02:31.990 --> 00:02:32.000 align:start position:0% in order to do that we need to make 00:02:32.000 --> 00:02:34.030 align:start position:0% in order to do that we need to make developers<00:02:32.450> lives<00:02:32.959> much<00:02:33.319> easier<00:02:33.709> so<00:02:33.830> we<00:02:33.920> can 00:02:34.030 --> 00:02:34.040 align:start position:0% developers lives much easier so we can 00:02:34.040 --> 00:02:36.220 align:start position:0% developers lives much easier so we can have<00:02:34.280> more<00:02:34.310> applications<00:02:35.180> so<00:02:35.630> kind<00:02:35.900> of<00:02:35.989> that 00:02:36.220 --> 00:02:36.230 align:start position:0% have more applications so kind of that 00:02:36.230 --> 00:02:40.300 align:start position:0% have more applications so kind of that is<00:02:36.440> our<00:02:36.590> whole<00:02:36.769> focus<00:02:37.190> as<00:02:37.370> a<00:02:37.790> company<00:02:38.290> so<00:02:39.310> to 00:02:40.300 --> 00:02:40.310 align:start position:0% is our whole focus as a company so to 00:02:40.310 --> 00:02:42.309 align:start position:0% is our whole focus as a company so to give<00:02:40.459> you<00:02:40.550> many<00:02:41.510> people<00:02:41.720> are<00:02:41.780> developers<00:02:42.170> in 00:02:42.309 --> 00:02:42.319 align:start position:0% give you many people are developers in 00:02:42.319 --> 00:02:45.490 align:start position:0% give you many people are developers in here<00:02:42.580> ok<00:02:43.580> ok<00:02:44.480> I<00:02:44.510> didn't<00:02:44.720> expect<00:02:44.989> everyone<00:02:45.349> to 00:02:45.490 --> 00:02:45.500 align:start position:0% here ok ok I didn't expect everyone to 00:02:45.500 --> 00:02:47.350 align:start position:0% here ok ok I didn't expect everyone to be<00:02:45.590> so<00:02:45.830> this<00:02:45.950> is<00:02:46.099> probably<00:02:46.400> a<00:02:46.670> little<00:02:47.120> a<00:02:47.150> little 00:02:47.350 --> 00:02:47.360 align:start position:0% be so this is probably a little a little 00:02:47.360 --> 00:02:49.479 align:start position:0% be so this is probably a little a little obvious<00:02:47.569> but<00:02:47.810> the<00:02:48.709> reason<00:02:49.010> that<00:02:49.040> good<00:02:49.280> told 00:02:49.479 --> 00:02:49.489 align:start position:0% obvious but the reason that good told 00:02:49.489 --> 00:02:51.339 align:start position:0% obvious but the reason that good told people<00:02:49.730> actually<00:02:50.209> often<00:02:50.690> underestimate<00:02:51.170> how 00:02:51.339 --> 00:02:51.349 align:start position:0% people actually often underestimate how 00:02:51.349 --> 00:02:53.410 align:start position:0% people actually often underestimate how much<00:02:51.530> good<00:02:51.680> tooling<00:02:52.040> matters<00:02:52.340> and<00:02:52.549> it's<00:02:53.120> it 00:02:53.410 --> 00:02:53.420 align:start position:0% much good tooling matters and it's it 00:02:53.420 --> 00:02:56.140 align:start position:0% much good tooling matters and it's it matters<00:02:53.840> a<00:02:53.870> lot<00:02:54.200> not<00:02:54.769> because<00:02:54.830> it<00:02:55.670> helps<00:02:56.060> you 00:02:56.140 --> 00:02:56.150 align:start position:0% matters a lot not because it helps you 00:02:56.150 --> 00:02:57.729 align:start position:0% matters a lot not because it helps you build<00:02:56.269> products<00:02:56.720> faster<00:02:56.870> which<00:02:57.349> is<00:02:57.470> what<00:02:57.620> it 00:02:57.729 --> 00:02:57.739 align:start position:0% build products faster which is what it 00:02:57.739 --> 00:03:00.130 align:start position:0% build products faster which is what it does<00:02:57.890> but<00:02:58.610> it<00:02:58.970> actually<00:02:59.120> lets<00:02:59.420> you<00:02:59.510> create<00:02:59.720> new 00:03:00.130 --> 00:03:00.140 align:start position:0% does but it actually lets you create new 00:03:00.140 --> 00:03:01.449 align:start position:0% does but it actually lets you create new types<00:03:00.410> of<00:03:00.560> products<00:03:00.920> you<00:03:01.010> weren't<00:03:01.220> able<00:03:01.310> to 00:03:01.449 --> 00:03:01.459 align:start position:0% types of products you weren't able to 00:03:01.459 --> 00:03:03.069 align:start position:0% types of products you weren't able to before<00:03:01.670> right<00:03:02.329> so<00:03:02.569> let's<00:03:02.750> say<00:03:02.870> you<00:03:02.959> were 00:03:03.069 --> 00:03:03.079 align:start position:0% before right so let's say you were 00:03:03.079 --> 00:03:05.199 align:start position:0% before right so let's say you were baking<00:03:03.319> your<00:03:03.829> baking<00:03:04.099> cake<00:03:04.280> you<00:03:04.700> have<00:03:04.760> oven 00:03:05.199 --> 00:03:05.209 align:start position:0% baking your baking cake you have oven 00:03:05.209 --> 00:03:06.880 align:start position:0% baking your baking cake you have oven you<00:03:05.390> have<00:03:05.420> timer<00:03:05.840> and<00:03:06.019> measuring<00:03:06.260> cup<00:03:06.410> you<00:03:06.769> can 00:03:06.880 --> 00:03:06.890 align:start position:0% you have timer and measuring cup you can 00:03:06.890 --> 00:03:09.100 align:start position:0% you have timer and measuring cup you can make<00:03:06.980> like<00:03:07.130> a<00:03:07.160> really<00:03:07.310> cool<00:03:07.549> cake<00:03:07.760> right<00:03:08.269> but 00:03:09.100 --> 00:03:09.110 align:start position:0% make like a really cool cake right but 00:03:09.110 --> 00:03:10.479 align:start position:0% make like a really cool cake right but the<00:03:09.260> challenge<00:03:09.560> is<00:03:09.650> imagine<00:03:10.010> if<00:03:10.099> you<00:03:10.190> just<00:03:10.340> had 00:03:10.479 --> 00:03:10.489 align:start position:0% the challenge is imagine if you just had 00:03:10.489 --> 00:03:13.000 align:start position:0% the challenge is imagine if you just had fire<00:03:10.880> no<00:03:11.630> timer<00:03:11.989> you<00:03:12.380> just<00:03:12.530> like<00:03:12.620> measuring 00:03:13.000 --> 00:03:13.010 align:start position:0% fire no timer you just like measuring 00:03:13.010 --> 00:03:14.650 align:start position:0% fire no timer you just like measuring stuff<00:03:13.310> by<00:03:13.430> hand<00:03:13.610> you're<00:03:13.849> kind<00:03:14.120> of<00:03:14.150> guessing<00:03:14.420> on 00:03:14.650 --> 00:03:14.660 align:start position:0% stuff by hand you're kind of guessing on 00:03:14.660 --> 00:03:16.210 align:start position:0% stuff by hand you're kind of guessing on your<00:03:14.780> time<00:03:14.959> kind<00:03:15.560> of<00:03:15.590> like<00:03:15.709> me<00:03:15.860> right<00:03:16.099> now 00:03:16.210 --> 00:03:16.220 align:start position:0% your time kind of like me right now 00:03:16.220 --> 00:03:17.830 align:start position:0% your time kind of like me right now seeing<00:03:16.519> how<00:03:16.579> much<00:03:16.760> time<00:03:16.880> I<00:03:16.910> have<00:03:17.090> left<00:03:17.150> so 00:03:17.830 --> 00:03:17.840 align:start position:0% seeing how much time I have left so 00:03:17.840 --> 00:03:19.150 align:start position:0% seeing how much time I have left so you're<00:03:18.349> gonna<00:03:18.470> end<00:03:18.650> up<00:03:18.739> with<00:03:18.860> something<00:03:19.010> like 00:03:19.150 --> 00:03:19.160 align:start position:0% you're gonna end up with something like 00:03:19.160 --> 00:03:21.759 align:start position:0% you're gonna end up with something like this<00:03:19.340> right<00:03:19.880> so<00:03:20.690> we<00:03:21.140> really<00:03:21.380> want<00:03:21.560> to<00:03:21.620> make<00:03:21.709> it 00:03:21.759 --> 00:03:21.769 align:start position:0% this right so we really want to make it 00:03:21.769 --> 00:03:23.860 align:start position:0% this right so we really want to make it easy<00:03:22.160> easy<00:03:22.519> easy<00:03:22.670> to<00:03:23.030> create<00:03:23.329> new<00:03:23.510> products 00:03:23.860 --> 00:03:23.870 align:start position:0% easy easy easy to create new products 00:03:23.870 --> 00:03:25.960 align:start position:0% easy easy easy to create new products and<00:03:23.989> also<00:03:24.109> enable<00:03:24.650> new<00:03:24.799> products<00:03:25.190> to<00:03:25.639> happen 00:03:25.960 --> 00:03:25.970 align:start position:0% and also enable new products to happen 00:03:25.970 --> 00:03:27.400 align:start position:0% and also enable new products to happen and<00:03:26.120> that's<00:03:26.299> why<00:03:26.569> developer<00:03:26.930> api's<00:03:27.200> are 00:03:27.400 --> 00:03:27.410 align:start position:0% and that's why developer api's are 00:03:27.410 --> 00:03:29.590 align:start position:0% and that's why developer api's are really<00:03:27.590> important<00:03:27.950> so<00:03:28.269> let's<00:03:29.269> go<00:03:29.359> through<00:03:29.540> an 00:03:29.590 --> 00:03:29.600 align:start position:0% really important so let's go through an 00:03:29.600 --> 00:03:31.960 align:start position:0% really important so let's go through an example<00:03:29.660> about<00:03:30.079> aetherium<00:03:30.560> so<00:03:31.100> right<00:03:31.459> now<00:03:31.639> one 00:03:31.960 --> 00:03:31.970 align:start position:0% example about aetherium so right now one 00:03:31.970 --> 00:03:34.780 align:start position:0% example about aetherium so right now one a<00:03:32.000> very<00:03:32.180> common<00:03:32.750> use<00:03:32.930> case<00:03:33.200> for<00:03:33.769> a<00:03:34.250> lot<00:03:34.760> of 00:03:34.780 --> 00:03:34.790 align:start position:0% a very common use case for a lot of 00:03:34.790 --> 00:03:36.879 align:start position:0% a very common use case for a lot of people's<00:03:35.090> applications<00:03:35.260> wallets<00:03:36.260> games<00:03:36.590> is 00:03:36.879 --> 00:03:36.889 align:start position:0% people's applications wallets games is 00:03:36.889 --> 00:03:38.920 align:start position:0% people's applications wallets games is you<00:03:37.430> want<00:03:37.579> to<00:03:37.639> list<00:03:37.880> all<00:03:38.120> the<00:03:38.150> transactions 00:03:38.920 --> 00:03:38.930 align:start position:0% you want to list all the transactions 00:03:38.930 --> 00:03:41.500 align:start position:0% you want to list all the transactions that<00:03:39.380> an<00:03:39.590> address<00:03:39.889> has<00:03:40.069> right<00:03:40.700> and<00:03:40.910> and<00:03:41.150> this 00:03:41.500 --> 00:03:41.510 align:start position:0% that an address has right and and this 00:03:41.510 --> 00:03:43.330 align:start position:0% that an address has right and and this is<00:03:41.750> actually<00:03:42.109> very<00:03:42.290> common<00:03:43.010> we<00:03:43.100> see<00:03:43.130> this 00:03:43.330 --> 00:03:43.340 align:start position:0% is actually very common we see this 00:03:43.340 --> 00:03:44.920 align:start position:0% is actually very common we see this among<00:03:43.489> a<00:03:43.519> lot<00:03:43.730> of<00:03:43.760> our<00:03:43.940> customers<00:03:44.090> but<00:03:44.810> it's 00:03:44.920 --> 00:03:44.930 align:start position:0% among a lot of our customers but it's 00:03:44.930 --> 00:03:46.750 align:start position:0% among a lot of our customers but it's actually<00:03:45.200> very<00:03:45.350> difficult<00:03:45.500> to<00:03:45.950> do<00:03:46.100> in<00:03:46.459> order 00:03:46.750 --> 00:03:46.760 align:start position:0% actually very difficult to do in order 00:03:46.760 --> 00:03:48.789 align:start position:0% actually very difficult to do in order to<00:03:46.850> do<00:03:46.970> this<00:03:47.090> you<00:03:47.299> need<00:03:47.450> to<00:03:47.540> go<00:03:47.660> block<00:03:48.290> by<00:03:48.590> block 00:03:48.789 --> 00:03:48.799 align:start position:0% to do this you need to go block by block 00:03:48.799 --> 00:03:50.590 align:start position:0% to do this you need to go block by block and<00:03:49.220> inspect<00:03:49.790> every<00:03:50.150> single<00:03:50.389> transaction 00:03:50.590 --> 00:03:50.600 align:start position:0% and inspect every single transaction 00:03:50.600 --> 00:03:52.930 align:start position:0% and inspect every single transaction like<00:03:51.079> let's<00:03:51.290> say<00:03:51.380> I<00:03:51.590> had<00:03:52.100> coinbase<00:03:52.519> wallet 00:03:52.930 --> 00:03:52.940 align:start position:0% like let's say I had coinbase wallet 00:03:52.940 --> 00:03:54.879 align:start position:0% like let's say I had coinbase wallet right<00:03:53.090> and<00:03:53.299> I<00:03:53.660> want<00:03:53.870> to<00:03:53.959> show<00:03:54.109> my<00:03:54.139> transaction 00:03:54.879 --> 00:03:54.889 align:start position:0% right and I want to show my transaction 00:03:54.889 --> 00:03:57.009 align:start position:0% right and I want to show my transaction history<00:03:54.980> coinbase<00:03:55.880> has<00:03:56.150> to<00:03:56.239> go<00:03:56.329> block<00:03:56.720> by 00:03:57.009 --> 00:03:57.019 align:start position:0% history coinbase has to go block by 00:03:57.019 --> 00:03:58.210 align:start position:0% history coinbase has to go block by block<00:03:57.170> look<00:03:57.560> through<00:03:57.739> every<00:03:58.069> single 00:03:58.210 --> 00:03:58.220 align:start position:0% block look through every single 00:03:58.220 --> 00:03:59.349 align:start position:0% block look through every single transaction<00:03:58.670> in<00:03:59.030> that<00:03:59.180> they're<00:03:59.299> in 00:03:59.349 --> 00:03:59.359 align:start position:0% transaction in that they're in 00:03:59.359 --> 00:04:01.240 align:start position:0% transaction in that they're in blockchain<00:03:59.720> and<00:03:59.900> see<00:04:00.319> which<00:04:00.500> one<00:04:00.680> is<00:04:00.859> relevant 00:04:01.240 --> 00:04:01.250 align:start position:0% blockchain and see which one is relevant 00:04:01.250 --> 00:04:02.589 align:start position:0% blockchain and see which one is relevant to<00:04:01.310> mine<00:04:01.459> so<00:04:01.730> out<00:04:01.880> of<00:04:01.970> the<00:04:02.060> millions<00:04:02.450> and 00:04:02.589 --> 00:04:02.599 align:start position:0% to mine so out of the millions and 00:04:02.599 --> 00:04:04.509 align:start position:0% to mine so out of the millions and millions<00:04:02.840> maybe<00:04:03.170> I'd<00:04:03.319> had<00:04:03.530> 10<00:04:03.859> transactions 00:04:04.509 --> 00:04:04.519 align:start position:0% millions maybe I'd had 10 transactions 00:04:04.519 --> 00:04:05.979 align:start position:0% millions maybe I'd had 10 transactions right<00:04:04.730> so<00:04:05.120> you<00:04:05.180> can<00:04:05.299> imagine<00:04:05.450> so<00:04:05.750> it's<00:04:05.840> not 00:04:05.979 --> 00:04:05.989 align:start position:0% right so you can imagine so it's not 00:04:05.989 --> 00:04:07.660 align:start position:0% right so you can imagine so it's not feasible<00:04:06.349> to<00:04:06.620> do<00:04:06.889> and<00:04:07.040> you<00:04:07.099> actually<00:04:07.280> can't 00:04:07.660 --> 00:04:07.670 align:start position:0% feasible to do and you actually can't 00:04:07.670 --> 00:04:08.920 align:start position:0% feasible to do and you actually can't build<00:04:07.910> an<00:04:08.000> application<00:04:08.480> like<00:04:08.569> that<00:04:08.630> it<00:04:08.810> would 00:04:08.920 --> 00:04:08.930 align:start position:0% build an application like that it would 00:04:08.930 --> 00:04:10.960 align:start position:0% build an application like that it would take<00:04:09.019> like<00:04:09.170> an<00:04:09.290> hour<00:04:09.380> to<00:04:09.859> load<00:04:10.040> to<00:04:10.519> applicate 00:04:10.960 --> 00:04:10.970 align:start position:0% take like an hour to load to applicate 00:04:10.970 --> 00:04:13.539 align:start position:0% take like an hour to load to applicate the<00:04:11.150> app<00:04:11.299> so<00:04:11.920> one<00:04:12.920> of<00:04:12.950> the<00:04:13.069> things<00:04:13.190> that<00:04:13.310> we<00:04:13.400> do 00:04:13.539 --> 00:04:13.549 align:start position:0% the app so one of the things that we do 00:04:13.549 --> 00:04:16.000 align:start position:0% the app so one of the things that we do is<00:04:13.760> provide<00:04:14.209> an<00:04:14.630> enhanced<00:04:14.780> developer<00:04:15.500> API<00:04:15.739> and 00:04:16.000 --> 00:04:16.010 align:start position:0% is provide an enhanced developer API and 00:04:16.010 --> 00:04:19.569 align:start position:0% is provide an enhanced developer API and what<00:04:16.639> that<00:04:16.820> does<00:04:17.060> is<00:04:17.299> it<00:04:17.539> backs<00:04:17.930> it<00:04:18.579> indexes 00:04:19.569 --> 00:04:19.579 align:start position:0% what that does is it backs it indexes 00:04:19.579 --> 00:04:22.120 align:start position:0% what that does is it backs it indexes and<00:04:19.760> stores<00:04:19.940> the<00:04:20.060> blockchain<00:04:20.349> with<00:04:21.349> a<00:04:21.650> lot<00:04:21.979> of 00:04:22.120 --> 00:04:22.130 align:start position:0% and stores the blockchain with a lot of 00:04:22.130 --> 00:04:24.490 align:start position:0% and stores the blockchain with a lot of infrastructure<00:04:22.789> so<00:04:23.180> then<00:04:23.750> for<00:04:24.229> the<00:04:24.320> user 00:04:24.490 --> 00:04:24.500 align:start position:0% infrastructure so then for the user 00:04:24.500 --> 00:04:26.469 align:start position:0% infrastructure so then for the user experience<00:04:24.680> it<00:04:25.099> just<00:04:25.250> turns<00:04:25.430> into<00:04:25.550> one<00:04:25.789> API 00:04:26.469 --> 00:04:26.479 align:start position:0% experience it just turns into one API 00:04:26.479 --> 00:04:28.060 align:start position:0% experience it just turns into one API calls<00:04:26.780> so<00:04:26.930> transact<00:04:27.380> get<00:04:27.590> transaction 00:04:28.060 --> 00:04:28.070 align:start position:0% calls so transact get transaction 00:04:28.070 --> 00:04:30.010 align:start position:0% calls so transact get transaction history<00:04:28.400> by<00:04:28.849> address<00:04:29.240> right<00:04:29.479> and<00:04:29.630> then<00:04:29.930> you 00:04:30.010 --> 00:04:30.020 align:start position:0% history by address right and then you 00:04:30.020 --> 00:04:31.580 align:start position:0% history by address right and then you just<00:04:30.169> get<00:04:30.260> all<00:04:30.380> your<00:04:30.409> results<00:04:30.620> immediately 00:04:31.580 --> 00:04:31.590 align:start position:0% just get all your results immediately 00:04:31.590 --> 00:04:32.930 align:start position:0% just get all your results immediately what<00:04:31.680> this<00:04:31.770> does<00:04:31.980> is<00:04:32.190> provides<00:04:32.520> a<00:04:32.610> building 00:04:32.930 --> 00:04:32.940 align:start position:0% what this does is provides a building 00:04:32.940 --> 00:04:35.030 align:start position:0% what this does is provides a building block<00:04:33.090> so<00:04:33.330> now<00:04:33.510> as<00:04:33.780> a<00:04:34.350> developer<00:04:34.560> you<00:04:34.890> don't 00:04:35.030 --> 00:04:35.040 align:start position:0% block so now as a developer you don't 00:04:35.040 --> 00:04:37.010 align:start position:0% block so now as a developer you don't need<00:04:35.160> to<00:04:35.250> go<00:04:35.370> build<00:04:35.700> all<00:04:36.450> of<00:04:36.600> that<00:04:36.750> from 00:04:37.010 --> 00:04:37.020 align:start position:0% need to go build all of that from 00:04:37.020 --> 00:04:39.080 align:start position:0% need to go build all of that from scratch<00:04:37.290> so<00:04:37.770> I<00:04:38.040> give<00:04:38.400> this<00:04:38.490> example<00:04:38.850> to<00:04:39.030> show 00:04:39.080 --> 00:04:39.090 align:start position:0% scratch so I give this example to show 00:04:39.090 --> 00:04:41.540 align:start position:0% scratch so I give this example to show you<00:04:39.500> this<00:04:40.500> is<00:04:40.650> almost<00:04:40.830> like<00:04:40.950> a<00:04:41.010> building<00:04:41.370> block 00:04:41.540 --> 00:04:41.550 align:start position:0% you this is almost like a building block 00:04:41.550 --> 00:04:43.640 align:start position:0% you this is almost like a building block so<00:04:41.760> now<00:04:42.000> when<00:04:42.240> you<00:04:42.330> look<00:04:42.360> at<00:04:42.690> an<00:04:42.960> application 00:04:43.640 --> 00:04:43.650 align:start position:0% so now when you look at an application 00:04:43.650 --> 00:04:45.830 align:start position:0% so now when you look at an application like<00:04:43.740> cheese<00:04:43.980> wizards<00:04:44.400> then<00:04:44.970> you<00:04:45.480> take<00:04:45.690> these 00:04:45.830 --> 00:04:45.840 align:start position:0% like cheese wizards then you take these 00:04:45.840 --> 00:04:47.450 align:start position:0% like cheese wizards then you take these same<00:04:46.140> concepts<00:04:46.620> and<00:04:46.770> apply<00:04:47.010> it<00:04:47.070> to<00:04:47.280> making 00:04:47.450 --> 00:04:47.460 align:start position:0% same concepts and apply it to making 00:04:47.460 --> 00:04:48.830 align:start position:0% same concepts and apply it to making that<00:04:47.790> development<00:04:48.150> experience<00:04:48.540> even<00:04:48.720> better 00:04:48.830 --> 00:04:48.840 align:start position:0% that development experience even better 00:04:48.840 --> 00:04:51.740 align:start position:0% that development experience even better and<00:04:49.140> you<00:04:49.740> end<00:04:49.890> up<00:04:49.950> something<00:04:50.280> really<00:04:50.430> great<00:04:50.750> so 00:04:51.740 --> 00:04:51.750 align:start position:0% and you end up something really great so 00:04:51.750 --> 00:04:53.240 align:start position:0% and you end up something really great so how<00:04:52.470> many<00:04:52.530> of<00:04:52.650> you<00:04:52.710> have<00:04:52.860> heard<00:04:52.950> of<00:04:53.040> cheese 00:04:53.240 --> 00:04:53.250 align:start position:0% how many of you have heard of cheese 00:04:53.250 --> 00:04:55.190 align:start position:0% how many of you have heard of cheese wizards<00:04:53.670> raise<00:04:53.970> your<00:04:54.060> hand<00:04:54.210> okay<00:04:54.780> cool<00:04:54.990> so 00:04:55.190 --> 00:04:55.200 align:start position:0% wizards raise your hand okay cool so 00:04:55.200 --> 00:04:57.740 align:start position:0% wizards raise your hand okay cool so cheese<00:04:55.770> wizards<00:04:56.130> is<00:04:56.310> a<00:04:56.820> new<00:04:57.150> game<00:04:57.330> by<00:04:57.450> crypto 00:04:57.740 --> 00:04:57.750 align:start position:0% cheese wizards is a new game by crypto 00:04:57.750 --> 00:04:59.060 align:start position:0% cheese wizards is a new game by crypto kitties<00:04:57.990> how<00:04:58.320> many<00:04:58.470> people<00:04:58.620> heard<00:04:58.770> of<00:04:58.830> crypto 00:04:59.060 --> 00:04:59.070 align:start position:0% kitties how many people heard of crypto 00:04:59.070 --> 00:05:02.420 align:start position:0% kitties how many people heard of crypto kitties<00:04:59.480> okay<00:05:00.480> so<00:05:00.900> basically<00:05:01.800> cryptic 00:05:02.420 --> 00:05:02.430 align:start position:0% kitties okay so basically cryptic 00:05:02.430 --> 00:05:03.710 align:start position:0% kitties okay so basically cryptic kitties<00:05:02.610> is<00:05:02.730> one<00:05:02.850> of<00:05:02.910> those<00:05:03.030> popular<00:05:03.270> games<00:05:03.570> on 00:05:03.710 --> 00:05:03.720 align:start position:0% kitties is one of those popular games on 00:05:03.720 --> 00:05:04.130 align:start position:0% kitties is one of those popular games on aetherium 00:05:04.130 --> 00:05:04.140 align:start position:0% aetherium 00:05:04.140 --> 00:05:06.380 align:start position:0% aetherium about<00:05:04.650> a<00:05:04.680> year<00:05:04.950> and<00:05:05.040> half<00:05:05.160> ago<00:05:05.280> they<00:05:06.120> came<00:05:06.300> out 00:05:06.380 --> 00:05:06.390 align:start position:0% about a year and half ago they came out 00:05:06.390 --> 00:05:07.610 align:start position:0% about a year and half ago they came out with<00:05:06.450> a<00:05:06.540> new<00:05:06.690> game<00:05:06.870> and<00:05:07.110> they<00:05:07.230> came<00:05:07.350> to<00:05:07.500> us<00:05:07.560> and 00:05:07.610 --> 00:05:07.620 align:start position:0% with a new game and they came to us and 00:05:07.620 --> 00:05:09.260 align:start position:0% with a new game and they came to us and said<00:05:07.710> hey<00:05:07.830> we<00:05:08.070> really<00:05:08.340> want<00:05:08.550> a<00:05:08.730> really<00:05:09.240> really 00:05:09.260 --> 00:05:09.270 align:start position:0% said hey we really want a really really 00:05:09.270 --> 00:05:10.880 align:start position:0% said hey we really want a really really cool<00:05:09.720> developer<00:05:10.140> experience<00:05:10.620> and<00:05:10.800> a 00:05:10.880 --> 00:05:10.890 align:start position:0% cool developer experience and a 00:05:10.890 --> 00:05:12.980 align:start position:0% cool developer experience and a developer<00:05:11.310> community<00:05:11.730> and<00:05:11.910> the<00:05:12.510> reason<00:05:12.870> for 00:05:12.980 --> 00:05:12.990 align:start position:0% developer community and the reason for 00:05:12.990 --> 00:05:14.300 align:start position:0% developer community and the reason for this<00:05:13.140> and<00:05:13.410> this<00:05:13.620> is<00:05:13.770> one<00:05:13.890> of<00:05:13.920> the<00:05:14.010> cool<00:05:14.130> things 00:05:14.300 --> 00:05:14.310 align:start position:0% this and this is one of the cool things 00:05:14.310 --> 00:05:15.950 align:start position:0% this and this is one of the cool things about<00:05:14.340> blockchain<00:05:14.640> right<00:05:15.090> is<00:05:15.240> since<00:05:15.780> it's 00:05:15.950 --> 00:05:15.960 align:start position:0% about blockchain right is since it's 00:05:15.960 --> 00:05:18.200 align:start position:0% about blockchain right is since it's open<00:05:16.350> people<00:05:17.130> can<00:05:17.400> build<00:05:17.580> any<00:05:17.940> kind<00:05:18.180> of 00:05:18.200 --> 00:05:18.210 align:start position:0% open people can build any kind of 00:05:18.210 --> 00:05:20.000 align:start position:0% open people can build any kind of application<00:05:18.360> they<00:05:18.900> want<00:05:19.140> with<00:05:19.590> the<00:05:19.710> crypto 00:05:20.000 --> 00:05:20.010 align:start position:0% application they want with the crypto 00:05:20.010 --> 00:05:22.550 align:start position:0% application they want with the crypto with<00:05:20.220> the<00:05:20.340> cheese<00:05:20.520> wizards<00:05:20.850> data<00:05:21.090> so<00:05:21.660> the<00:05:22.260> goal 00:05:22.550 --> 00:05:22.560 align:start position:0% with the cheese wizards data so the goal 00:05:22.560 --> 00:05:24.860 align:start position:0% with the cheese wizards data so the goal in<00:05:22.920> order<00:05:23.190> to<00:05:23.460> create<00:05:24.120> a<00:05:24.180> really<00:05:24.270> flourishing 00:05:24.860 --> 00:05:24.870 align:start position:0% in order to create a really flourishing 00:05:24.870 --> 00:05:25.730 align:start position:0% in order to create a really flourishing community<00:05:25.230> is<00:05:25.350> you<00:05:25.470> need<00:05:25.590> to<00:05:25.620> make 00:05:25.730 --> 00:05:25.740 align:start position:0% community is you need to make 00:05:25.740 --> 00:05:27.530 align:start position:0% community is you need to make development<00:05:26.520> as<00:05:26.610> easy<00:05:26.820> as<00:05:26.940> possible<00:05:27.300> like<00:05:27.390> we 00:05:27.530 --> 00:05:27.540 align:start position:0% development as easy as possible like we 00:05:27.540 --> 00:05:28.880 align:start position:0% development as easy as possible like we talked<00:05:27.750> about<00:05:27.870> before<00:05:28.080> both<00:05:28.680> on<00:05:28.830> the 00:05:28.880 --> 00:05:28.890 align:start position:0% talked about before both on the 00:05:28.890 --> 00:05:30.650 align:start position:0% talked about before both on the infrastructure<00:05:29.280> side<00:05:29.520> and<00:05:29.790> on<00:05:30.150> the<00:05:30.270> tool<00:05:30.450> side 00:05:30.650 --> 00:05:30.660 align:start position:0% infrastructure side and on the tool side 00:05:30.660 --> 00:05:33.530 align:start position:0% infrastructure side and on the tool side and<00:05:30.900> on<00:05:31.290> the<00:05:31.380> API<00:05:31.680> side<00:05:32.010> and<00:05:32.220> back<00:05:33.060> to<00:05:33.300> kind<00:05:33.480> of 00:05:33.530 --> 00:05:33.540 align:start position:0% and on the API side and back to kind of 00:05:33.540 --> 00:05:34.610 align:start position:0% and on the API side and back to kind of how<00:05:33.630> we<00:05:33.690> were<00:05:33.810> talking<00:05:33.990> about<00:05:34.200> aetherium 00:05:34.610 --> 00:05:34.620 align:start position:0% how we were talking about aetherium 00:05:34.620 --> 00:05:36.320 align:start position:0% how we were talking about aetherium transaction<00:05:35.220> history<00:05:35.310> a<00:05:35.700> lot<00:05:36.120> of<00:05:36.240> these 00:05:36.320 --> 00:05:36.330 align:start position:0% transaction history a lot of these 00:05:36.330 --> 00:05:38.420 align:start position:0% transaction history a lot of these things<00:05:36.570> were<00:05:36.750> not<00:05:36.780> feasible<00:05:37.260> to<00:05:37.590> do<00:05:37.800> if<00:05:38.040> you're 00:05:38.420 --> 00:05:38.430 align:start position:0% things were not feasible to do if you're 00:05:38.430 --> 00:05:39.890 align:start position:0% things were not feasible to do if you're doing<00:05:38.460> it<00:05:38.820> on<00:05:38.880> the<00:05:38.910> standard<00:05:39.330> aetherium<00:05:39.600> API 00:05:39.890 --> 00:05:39.900 align:start position:0% doing it on the standard aetherium API 00:05:39.900 --> 00:05:41.930 align:start position:0% doing it on the standard aetherium API so<00:05:40.410> if<00:05:40.560> you're<00:05:40.680> just<00:05:40.710> trying<00:05:41.010> to<00:05:41.070> load<00:05:41.340> all<00:05:41.610> the 00:05:41.930 --> 00:05:41.940 align:start position:0% so if you're just trying to load all the 00:05:41.940 --> 00:05:43.250 align:start position:0% so if you're just trying to load all the cheese<00:05:42.120> wizards<00:05:42.600> and<00:05:42.780> we'll<00:05:42.930> go<00:05:43.050> through<00:05:43.230> a 00:05:43.250 --> 00:05:43.260 align:start position:0% cheese wizards and we'll go through a 00:05:43.260 --> 00:05:45.140 align:start position:0% cheese wizards and we'll go through a couple<00:05:43.380> examples<00:05:43.530> today<00:05:44.070> it's<00:05:44.670> actually<00:05:44.760> you 00:05:45.140 --> 00:05:45.150 align:start position:0% couple examples today it's actually you 00:05:45.150 --> 00:05:46.880 align:start position:0% couple examples today it's actually you just<00:05:45.420> can't<00:05:45.750> do<00:05:45.990> it<00:05:46.020> unless<00:05:46.380> you<00:05:46.560> build<00:05:46.680> your 00:05:46.880 --> 00:05:46.890 align:start position:0% just can't do it unless you build your 00:05:46.890 --> 00:05:48.260 align:start position:0% just can't do it unless you build your own<00:05:46.950> database<00:05:47.280> and<00:05:47.640> infrastructure<00:05:48.090> and<00:05:48.150> all 00:05:48.260 --> 00:05:48.270 align:start position:0% own database and infrastructure and all 00:05:48.270 --> 00:05:50.720 align:start position:0% own database and infrastructure and all these<00:05:48.360> things<00:05:48.630> so<00:05:49.280> that's<00:05:50.280> kind<00:05:50.580> of<00:05:50.610> the 00:05:50.720 --> 00:05:50.730 align:start position:0% these things so that's kind of the 00:05:50.730 --> 00:05:52.940 align:start position:0% these things so that's kind of the motivation<00:05:50.910> behind<00:05:51.300> why<00:05:51.810> they<00:05:52.470> wanted<00:05:52.890> to 00:05:52.940 --> 00:05:52.950 align:start position:0% motivation behind why they wanted to 00:05:52.950 --> 00:05:55.730 align:start position:0% motivation behind why they wanted to create<00:05:53.400> a<00:05:53.430> really<00:05:53.730> great<00:05:53.910> developer<00:05:54.330> API<00:05:54.740> so 00:05:55.730 --> 00:05:55.740 align:start position:0% create a really great developer API so 00:05:55.740 --> 00:05:57.380 align:start position:0% create a really great developer API so really<00:05:56.280> quick<00:05:56.460> highlight<00:05:56.790> of<00:05:56.940> what<00:05:57.090> the<00:05:57.240> game 00:05:57.380 --> 00:05:57.390 align:start position:0% really quick highlight of what the game 00:05:57.390 --> 00:05:59.510 align:start position:0% really quick highlight of what the game is<00:05:57.630> what<00:05:58.500> it<00:05:58.620> does<00:05:58.740> is<00:05:58.980> it's<00:05:59.130> kind<00:05:59.340> of<00:05:59.370> like<00:05:59.490> a 00:05:59.510 --> 00:05:59.520 align:start position:0% is what it does is it's kind of like a 00:05:59.520 --> 00:06:01.220 align:start position:0% is what it does is it's kind of like a rock-paper-scissors<00:05:59.760> game<00:06:00.480> guys<00:06:00.930> haven't 00:06:01.220 --> 00:06:01.230 align:start position:0% rock-paper-scissors game guys haven't 00:06:01.230 --> 00:06:03.020 align:start position:0% rock-paper-scissors game guys haven't played<00:06:01.350> it<00:06:01.500> definitely<00:06:01.920> check<00:06:02.040> it<00:06:02.070> out<00:06:02.220> and 00:06:03.020 --> 00:06:03.030 align:start position:0% played it definitely check it out and 00:06:03.030 --> 00:06:04.400 align:start position:0% played it definitely check it out and you<00:06:03.240> have<00:06:03.330> these<00:06:03.420> wizards<00:06:03.870> and<00:06:04.110> they<00:06:04.200> fight 00:06:04.400 --> 00:06:04.410 align:start position:0% you have these wizards and they fight 00:06:04.410 --> 00:06:08.570 align:start position:0% you have these wizards and they fight tools<00:06:04.770> and<00:06:05.960> basically<00:06:06.960> it<00:06:07.200> lets<00:06:07.350> you<00:06:07.530> you<00:06:08.460> have 00:06:08.570 --> 00:06:08.580 align:start position:0% tools and basically it lets you you have 00:06:08.580 --> 00:06:10.580 align:start position:0% tools and basically it lets you you have these<00:06:08.730> moves<00:06:09.000> like<00:06:09.210> wind<00:06:09.510> fire<00:06:09.930> and<00:06:10.140> water<00:06:10.200> and 00:06:10.580 --> 00:06:10.590 align:start position:0% these moves like wind fire and water and 00:06:10.590 --> 00:06:11.900 align:start position:0% these moves like wind fire and water and you<00:06:11.010> fight<00:06:11.190> each<00:06:11.310> other<00:06:11.490> it's<00:06:11.670> just<00:06:11.820> like 00:06:11.900 --> 00:06:11.910 align:start position:0% you fight each other it's just like 00:06:11.910 --> 00:06:13.730 align:start position:0% you fight each other it's just like tournament<00:06:12.330> and<00:06:12.420> you<00:06:12.480> go<00:06:12.600> up<00:06:12.720> so<00:06:13.290> and<00:06:13.530> I'm<00:06:13.590> just 00:06:13.730 --> 00:06:13.740 align:start position:0% tournament and you go up so and I'm just 00:06:13.740 --> 00:06:14.900 align:start position:0% tournament and you go up so and I'm just showing<00:06:13.920> this<00:06:14.040> so<00:06:14.250> you<00:06:14.340> can<00:06:14.490> get<00:06:14.610> a<00:06:14.640> little<00:06:14.760> bit 00:06:14.900 --> 00:06:14.910 align:start position:0% showing this so you can get a little bit 00:06:14.910 --> 00:06:16.190 align:start position:0% showing this so you can get a little bit understanding<00:06:15.630> when<00:06:15.720> we<00:06:15.810> go<00:06:15.930> through<00:06:16.110> the 00:06:16.190 --> 00:06:16.200 align:start position:0% understanding when we go through the 00:06:16.200 --> 00:06:19.370 align:start position:0% understanding when we go through the examples<00:06:16.550> so<00:06:17.550> how<00:06:18.510> do<00:06:18.570> we<00:06:18.660> think<00:06:18.960> about<00:06:19.080> the 00:06:19.370 --> 00:06:19.380 align:start position:0% examples so how do we think about the 00:06:19.380 --> 00:06:21.350 align:start position:0% examples so how do we think about the API<00:06:19.650> so<00:06:20.070> the<00:06:20.340> first<00:06:20.520> part<00:06:20.760> is<00:06:20.880> we<00:06:20.970> mourn<00:06:21.150> to<00:06:21.270> be 00:06:21.350 --> 00:06:21.360 align:start position:0% API so the first part is we mourn to be 00:06:21.360 --> 00:06:22.790 align:start position:0% API so the first part is we mourn to be just<00:06:21.540> really<00:06:21.630> simple<00:06:22.080> like<00:06:22.320> when<00:06:22.470> you<00:06:22.530> look<00:06:22.650> at 00:06:22.790 --> 00:06:22.800 align:start position:0% just really simple like when you look at 00:06:22.800 --> 00:06:24.440 align:start position:0% just really simple like when you look at it<00:06:22.920> it's<00:06:23.100> almost<00:06:23.220> like<00:06:23.340> deceptively<00:06:23.790> simple 00:06:24.440 --> 00:06:24.450 align:start position:0% it it's almost like deceptively simple 00:06:24.450 --> 00:06:26.990 align:start position:0% it it's almost like deceptively simple the<00:06:25.050> user<00:06:25.230> experience<00:06:25.830> right<00:06:26.220> and<00:06:26.520> that<00:06:26.850> was 00:06:26.990 --> 00:06:27.000 align:start position:0% the user experience right and that was 00:06:27.000 --> 00:06:28.640 align:start position:0% the user experience right and that was on<00:06:27.090> purpose<00:06:27.330> and<00:06:27.720> it's<00:06:27.840> actually<00:06:28.080> one<00:06:28.500> thing 00:06:28.640 --> 00:06:28.650 align:start position:0% on purpose and it's actually one thing 00:06:28.650 --> 00:06:30.110 align:start position:0% on purpose and it's actually one thing is<00:06:28.980> you<00:06:29.070> guys<00:06:29.190> know<00:06:29.370> it's<00:06:29.520> actually<00:06:29.730> more 00:06:30.110 --> 00:06:30.120 align:start position:0% is you guys know it's actually more 00:06:30.120 --> 00:06:31.910 align:start position:0% is you guys know it's actually more difficult<00:06:30.540> to<00:06:30.600> design<00:06:30.780> simple<00:06:31.440> user 00:06:31.910 --> 00:06:31.920 align:start position:0% difficult to design simple user 00:06:31.920 --> 00:06:33.710 align:start position:0% difficult to design simple user experiences<00:06:32.520> then<00:06:32.790> to<00:06:32.940> design<00:06:33.090> complicated 00:06:33.710 --> 00:06:33.720 align:start position:0% experiences then to design complicated 00:06:33.720 --> 00:06:34.790 align:start position:0% experiences then to design complicated ones<00:06:33.900> because<00:06:34.110> you<00:06:34.200> have<00:06:34.320> to<00:06:34.410> put<00:06:34.530> in<00:06:34.590> a<00:06:34.650> lot<00:06:34.770> of 00:06:34.790 --> 00:06:34.800 align:start position:0% ones because you have to put in a lot of 00:06:34.800 --> 00:06:35.990 align:start position:0% ones because you have to put in a lot of thought<00:06:35.070> and<00:06:35.190> a<00:06:35.250> lot<00:06:35.370> of<00:06:35.400> infrastructure<00:06:35.880> on 00:06:35.990 --> 00:06:36.000 align:start position:0% thought and a lot of infrastructure on 00:06:36.000 --> 00:06:37.700 align:start position:0% thought and a lot of infrastructure on the<00:06:36.090> backend<00:06:36.270> the<00:06:36.660> other<00:06:37.080> thing<00:06:37.290> we<00:06:37.380> wanted<00:06:37.620> to 00:06:37.700 --> 00:06:37.710 align:start position:0% the backend the other thing we wanted to 00:06:37.710 --> 00:06:39.350 align:start position:0% the backend the other thing we wanted to do<00:06:37.830> is<00:06:37.920> have<00:06:38.010> a<00:06:38.100> powerful<00:06:38.430> querying<00:06:38.850> system<00:06:39.210> so 00:06:39.350 --> 00:06:39.360 align:start position:0% do is have a powerful querying system so 00:06:39.360 --> 00:06:41.150 align:start position:0% do is have a powerful querying system so you<00:06:39.450> can<00:06:39.570> actually<00:06:40.020> get<00:06:40.440> the<00:06:40.560> data<00:06:40.710> you<00:06:40.920> want 00:06:41.150 --> 00:06:41.160 align:start position:0% you can actually get the data you want 00:06:41.160 --> 00:06:42.740 align:start position:0% you can actually get the data you want so<00:06:41.520> you<00:06:41.550> can<00:06:41.640> build<00:06:41.880> applications<00:06:42.030> really 00:06:42.740 --> 00:06:42.750 align:start position:0% so you can build applications really 00:06:42.750 --> 00:06:44.900 align:start position:0% so you can build applications really easily<00:06:43.050> right<00:06:43.740> and<00:06:43.860> the<00:06:43.920> third<00:06:44.100> thing<00:06:44.400> is<00:06:44.610> we 00:06:44.900 --> 00:06:44.910 align:start position:0% easily right and the third thing is we 00:06:44.910 --> 00:06:45.380 align:start position:0% easily right and the third thing is we wanted<00:06:45.120> to<00:06:45.210> make 00:06:45.380 --> 00:06:45.390 align:start position:0% wanted to make 00:06:45.390 --> 00:06:46.370 align:start position:0% wanted to make get<00:06:45.480> really<00:06:45.660> easy<00:06:45.810> so<00:06:46.020> you'll<00:06:46.110> have<00:06:46.200> to<00:06:46.290> go 00:06:46.370 --> 00:06:46.380 align:start position:0% get really easy so you'll have to go 00:06:46.380 --> 00:06:47.960 align:start position:0% get really easy so you'll have to go spin<00:06:46.950> up<00:06:47.070> your<00:06:47.190> own<00:06:47.340> node<00:06:47.580> like<00:06:47.790> if<00:06:47.880> you're 00:06:47.960 --> 00:06:47.970 align:start position:0% spin up your own node like if you're 00:06:47.970 --> 00:06:48.950 align:start position:0% spin up your own node like if you're building<00:06:48.060> a<00:06:48.240> website<00:06:48.420> you<00:06:48.660> don't<00:06:48.720> have<00:06:48.900> to 00:06:48.950 --> 00:06:48.960 align:start position:0% building a website you don't have to 00:06:48.960 --> 00:06:50.540 align:start position:0% building a website you don't have to like<00:06:49.050> spin<00:06:49.560> up<00:06:49.650> your<00:06:49.770> own<00:06:49.860> server<00:06:50.100> and<00:06:50.400> do<00:06:50.460> all 00:06:50.540 --> 00:06:50.550 align:start position:0% like spin up your own server and do all 00:06:50.550 --> 00:06:51.860 align:start position:0% like spin up your own server and do all this<00:06:50.730> awfully<00:06:51.090> you<00:06:51.150> just<00:06:51.300> open<00:06:51.510> your<00:06:51.570> text 00:06:51.860 --> 00:06:51.870 align:start position:0% this awfully you just open your text 00:06:51.870 --> 00:06:53.420 align:start position:0% this awfully you just open your text editor<00:06:51.960> and<00:06:52.200> start<00:06:52.320> typing<00:06:52.590> so<00:06:52.950> for 00:06:53.420 --> 00:06:53.430 align:start position:0% editor and start typing so for 00:06:53.430 --> 00:06:55.010 align:start position:0% editor and start typing so for blockchain<00:06:53.730> we<00:06:53.910> did<00:06:54.060> for<00:06:54.270> cheese<00:06:54.510> moszer's<00:06:54.840> we 00:06:55.010 --> 00:06:55.020 align:start position:0% blockchain we did for cheese moszer's we 00:06:55.020 --> 00:06:56.660 align:start position:0% blockchain we did for cheese moszer's we didn't<00:06:55.230> want<00:06:55.380> you<00:06:55.500> to<00:06:55.590> have<00:06:55.710> to<00:06:55.830> spin<00:06:56.430> up<00:06:56.550> a<00:06:56.640> new 00:06:56.660 --> 00:06:56.670 align:start position:0% didn't want you to have to spin up a new 00:06:56.670 --> 00:06:59.240 align:start position:0% didn't want you to have to spin up a new ec2<00:06:57.330> instance<00:06:57.780> and<00:06:57.990> install<00:06:58.500> a<00:06:58.530> node<00:06:58.860> and<00:06:59.040> sync 00:06:59.240 --> 00:06:59.250 align:start position:0% ec2 instance and install a node and sync 00:06:59.250 --> 00:07:00.620 align:start position:0% ec2 instance and install a node and sync it<00:06:59.340> from<00:06:59.520> scratch<00:06:59.820> and<00:07:00.090> then<00:07:00.180> do<00:07:00.420> all<00:07:00.540> this 00:07:00.620 --> 00:07:00.630 align:start position:0% it from scratch and then do all this 00:07:00.630 --> 00:07:01.850 align:start position:0% it from scratch and then do all this extra<00:07:00.900> stuff<00:07:01.110> so<00:07:01.260> we're<00:07:01.380> like<00:07:01.500> we<00:07:01.620> just<00:07:01.710> wanna 00:07:01.850 --> 00:07:01.860 align:start position:0% extra stuff so we're like we just wanna 00:07:01.860 --> 00:07:03.950 align:start position:0% extra stuff so we're like we just wanna make<00:07:01.950> it<00:07:02.010> super<00:07:02.400> simple<00:07:02.430> web<00:07:03.180> API<00:07:03.480> so<00:07:03.780> you<00:07:03.810> can 00:07:03.950 --> 00:07:03.960 align:start position:0% make it super simple web API so you can 00:07:03.960 --> 00:07:05.480 align:start position:0% make it super simple web API so you can just<00:07:04.080> prototype<00:07:04.470> and<00:07:04.680> build<00:07:04.980> really<00:07:05.220> quickly 00:07:05.480 --> 00:07:05.490 align:start position:0% just prototype and build really quickly 00:07:05.490 --> 00:07:07.460 align:start position:0% just prototype and build really quickly so<00:07:06.120> under<00:07:06.420> the<00:07:06.510> hood<00:07:06.720> what<00:07:06.870> we<00:07:07.020> had<00:07:07.170> to<00:07:07.260> do<00:07:07.350> is 00:07:07.460 --> 00:07:07.470 align:start position:0% so under the hood what we had to do is 00:07:07.470 --> 00:07:08.810 align:start position:0% so under the hood what we had to do is actually<00:07:07.590> build<00:07:07.770> a<00:07:07.890> ton<00:07:08.190> of<00:07:08.220> complicated 00:07:08.810 --> 00:07:08.820 align:start position:0% actually build a ton of complicated 00:07:08.820 --> 00:07:10.640 align:start position:0% actually build a ton of complicated indexing<00:07:09.270> infrastructure<00:07:09.780> that<00:07:10.200> allows<00:07:10.620> us 00:07:10.640 --> 00:07:10.650 align:start position:0% indexing infrastructure that allows us 00:07:10.650 --> 00:07:12.410 align:start position:0% indexing infrastructure that allows us to<00:07:10.950> serve<00:07:11.280> and<00:07:11.490> query<00:07:11.670> this<00:07:11.850> data<00:07:12.030> very<00:07:12.360> very 00:07:12.410 --> 00:07:12.420 align:start position:0% to serve and query this data very very 00:07:12.420 --> 00:07:15.800 align:start position:0% to serve and query this data very very easily<00:07:13.190> so<00:07:14.190> let's<00:07:15.090> go<00:07:15.480> through<00:07:15.600> a<00:07:15.660> couple 00:07:15.800 --> 00:07:15.810 align:start position:0% easily so let's go through a couple 00:07:15.810 --> 00:07:17.840 align:start position:0% easily so let's go through a couple examples<00:07:15.990> of<00:07:16.410> what<00:07:16.560> that<00:07:16.590> looks<00:07:16.950> like<00:07:17.040> so<00:07:17.370> you 00:07:17.840 --> 00:07:17.850 align:start position:0% examples of what that looks like so you 00:07:17.850 --> 00:07:19.550 align:start position:0% examples of what that looks like so you can<00:07:17.970> think<00:07:18.120> of<00:07:18.330> it<00:07:18.660> let's<00:07:18.990> say<00:07:19.110> we're<00:07:19.290> building 00:07:19.550 --> 00:07:19.560 align:start position:0% can think of it let's say we're building 00:07:19.560 --> 00:07:21.410 align:start position:0% can think of it let's say we're building a<00:07:19.620> leaderboard<00:07:19.950> so<00:07:20.550> we<00:07:20.700> want<00:07:20.850> to<00:07:20.940> show<00:07:21.060> all<00:07:21.300> the 00:07:21.410 --> 00:07:21.420 align:start position:0% a leaderboard so we want to show all the 00:07:21.420 --> 00:07:22.610 align:start position:0% a leaderboard so we want to show all the cheese<00:07:21.600> wizards<00:07:21.960> and<00:07:22.140> who's<00:07:22.350> the<00:07:22.470> most 00:07:22.610 --> 00:07:22.620 align:start position:0% cheese wizards and who's the most 00:07:22.620 --> 00:07:25.070 align:start position:0% cheese wizards and who's the most powerful<00:07:23.070> one<00:07:23.250> and<00:07:23.490> who<00:07:23.700> has<00:07:23.970> been<00:07:24.570> winning 00:07:25.070 --> 00:07:25.080 align:start position:0% powerful one and who has been winning 00:07:25.080 --> 00:07:27.140 align:start position:0% powerful one and who has been winning these<00:07:25.380> fights<00:07:25.800> which<00:07:26.070> are<00:07:26.190> called<00:07:26.310> duels<00:07:26.610> so 00:07:27.140 --> 00:07:27.150 align:start position:0% these fights which are called duels so 00:07:27.150 --> 00:07:28.970 align:start position:0% these fights which are called duels so this<00:07:27.960> is<00:07:28.110> what<00:07:28.260> it<00:07:28.350> would<00:07:28.440> look<00:07:28.500> like<00:07:28.770> without 00:07:28.970 --> 00:07:28.980 align:start position:0% this is what it would look like without 00:07:28.980 --> 00:07:31.910 align:start position:0% this is what it would look like without the<00:07:29.250> API<00:07:29.490> and<00:07:29.730> this<00:07:29.820> is<00:07:29.910> actually<00:07:30.300> so<00:07:31.200> this<00:07:31.800> is 00:07:31.910 --> 00:07:31.920 align:start position:0% the API and this is actually so this is 00:07:31.920 --> 00:07:33.050 align:start position:0% the API and this is actually so this is actually<00:07:32.160> a<00:07:32.190> shortened<00:07:32.550> version<00:07:32.760> of<00:07:32.820> the<00:07:32.880> code 00:07:33.050 --> 00:07:33.060 align:start position:0% actually a shortened version of the code 00:07:33.060 --> 00:07:34.610 align:start position:0% actually a shortened version of the code we're<00:07:33.270> writing<00:07:33.480> this<00:07:33.630> last<00:07:33.870> night<00:07:34.050> and<00:07:34.230> we're 00:07:34.610 --> 00:07:34.620 align:start position:0% we're writing this last night and we're 00:07:34.620 --> 00:07:36.230 align:start position:0% we're writing this last night and we're magicians<00:07:34.770> like<00:07:35.280> actually<00:07:35.640> I<00:07:35.700> had<00:07:35.850> to<00:07:35.940> cut<00:07:36.120> out 00:07:36.230 --> 00:07:36.240 align:start position:0% magicians like actually I had to cut out 00:07:36.240 --> 00:07:38.300 align:start position:0% magicians like actually I had to cut out like<00:07:36.450> 2/3<00:07:36.930> of<00:07:37.080> the<00:07:37.170> code<00:07:37.350> because<00:07:37.560> it<00:07:38.070> wouldn't 00:07:38.300 --> 00:07:38.310 align:start position:0% like 2/3 of the code because it wouldn't 00:07:38.310 --> 00:07:39.980 align:start position:0% like 2/3 of the code because it wouldn't fit<00:07:38.430> on<00:07:38.610> one<00:07:38.640> screenshot<00:07:39.030> but<00:07:39.690> you<00:07:39.750> get<00:07:39.870> you 00:07:39.980 --> 00:07:39.990 align:start position:0% fit on one screenshot but you get you 00:07:39.990 --> 00:07:41.570 align:start position:0% fit on one screenshot but you get you get<00:07:40.110> the<00:07:40.200> idea<00:07:40.440> right<00:07:40.680> so<00:07:40.830> don't<00:07:40.980> try<00:07:41.340> to<00:07:41.400> run 00:07:41.570 --> 00:07:41.580 align:start position:0% get the idea right so don't try to run 00:07:41.580 --> 00:07:42.860 align:start position:0% get the idea right so don't try to run this<00:07:41.700> so<00:07:41.820> it<00:07:41.880> won't<00:07:42.000> actually<00:07:42.060> work<00:07:42.390> but 00:07:42.860 --> 00:07:42.870 align:start position:0% this so it won't actually work but 00:07:42.870 --> 00:07:45.350 align:start position:0% this so it won't actually work but basically<00:07:43.770> like<00:07:44.100> this<00:07:44.790> you<00:07:45.120> would<00:07:45.210> have<00:07:45.240> to 00:07:45.350 --> 00:07:45.360 align:start position:0% basically like this you would have to 00:07:45.360 --> 00:07:47.180 align:start position:0% basically like this you would have to write<00:07:45.480> this<00:07:45.750> much<00:07:45.990> code<00:07:46.230> just<00:07:46.680> to<00:07:46.830> get<00:07:46.950> all<00:07:47.040> the 00:07:47.180 --> 00:07:47.190 align:start position:0% write this much code just to get all the 00:07:47.190 --> 00:07:49.040 align:start position:0% write this much code just to get all the duels<00:07:47.460> and<00:07:47.730> you<00:07:48.270> know<00:07:48.360> that's<00:07:48.630> actually<00:07:48.870> not 00:07:49.040 --> 00:07:49.050 align:start position:0% duels and you know that's actually not 00:07:49.050 --> 00:07:50.480 align:start position:0% duels and you know that's actually not the<00:07:49.290> hard<00:07:49.470> part<00:07:49.530> because<00:07:49.890> you<00:07:50.100> can<00:07:50.220> write<00:07:50.340> this 00:07:50.480 --> 00:07:50.490 align:start position:0% the hard part because you can write this 00:07:50.490 --> 00:07:52.130 align:start position:0% the hard part because you can write this code<00:07:50.670> right<00:07:50.850> but<00:07:51.420> the<00:07:51.510> thing<00:07:51.540> is<00:07:51.750> it<00:07:52.110> takes 00:07:52.130 --> 00:07:52.140 align:start position:0% code right but the thing is it takes 00:07:52.140 --> 00:07:54.140 align:start position:0% code right but the thing is it takes like<00:07:52.500> 10<00:07:52.770> minutes<00:07:52.950> to<00:07:53.040> load<00:07:53.220> a<00:07:53.250> page<00:07:53.490> because 00:07:54.140 --> 00:07:54.150 align:start position:0% like 10 minutes to load a page because 00:07:54.150 --> 00:07:55.850 align:start position:0% like 10 minutes to load a page because again<00:07:54.390> this<00:07:54.540> is<00:07:54.660> going<00:07:54.810> through<00:07:55.050> every<00:07:55.590> block 00:07:55.850 --> 00:07:55.860 align:start position:0% again this is going through every block 00:07:55.860 --> 00:07:58.040 align:start position:0% again this is going through every block and<00:07:56.160> every<00:07:56.340> transaction<00:07:56.670> in<00:07:57.390> all<00:07:57.720> the<00:07:57.840> logs 00:07:58.040 --> 00:07:58.050 align:start position:0% and every transaction in all the logs 00:07:58.050 --> 00:07:59.900 align:start position:0% and every transaction in all the logs and<00:07:58.290> figuring<00:07:58.620> all<00:07:58.710> that<00:07:58.950> stuff<00:07:59.220> out<00:07:59.400> right<00:07:59.640> so 00:07:59.900 --> 00:07:59.910 align:start position:0% and figuring all that stuff out right so 00:07:59.910 --> 00:08:01.460 align:start position:0% and figuring all that stuff out right so it's<00:08:00.030> not<00:08:00.150> feasible<00:08:00.510> each<00:08:00.870> query<00:08:01.140> will<00:08:01.320> take 00:08:01.460 --> 00:08:01.470 align:start position:0% it's not feasible each query will take 00:08:01.470 --> 00:08:03.590 align:start position:0% it's not feasible each query will take like<00:08:01.620> about<00:08:02.100> a<00:08:02.130> minute<00:08:02.340> so<00:08:02.640> you<00:08:02.700> need<00:08:02.970> many 00:08:03.590 --> 00:08:03.600 align:start position:0% like about a minute so you need many 00:08:03.600 --> 00:08:04.700 align:start position:0% like about a minute so you need many queries<00:08:03.900> on<00:08:03.990> your<00:08:04.080> page<00:08:04.200> it's<00:08:04.380> gonna<00:08:04.440> take<00:08:04.680> a 00:08:04.700 --> 00:08:04.710 align:start position:0% queries on your page it's gonna take a 00:08:04.710 --> 00:08:06.380 align:start position:0% queries on your page it's gonna take a long<00:08:04.980> time<00:08:05.040> so<00:08:05.250> you<00:08:05.460> can't<00:08:05.730> build<00:08:05.880> and<00:08:06.180> no 00:08:06.380 --> 00:08:06.390 align:start position:0% long time so you can't build and no 00:08:06.390 --> 00:08:08.000 align:start position:0% long time so you can't build and no users<00:08:06.720> gonna<00:08:06.900> click<00:08:07.110> a<00:08:07.140> button<00:08:07.320> and<00:08:07.560> then<00:08:07.860> wait 00:08:08.000 --> 00:08:08.010 align:start position:0% users gonna click a button and then wait 00:08:08.010 --> 00:08:09.380 align:start position:0% users gonna click a button and then wait 10<00:08:08.160> minutes<00:08:08.370> for<00:08:08.520> something<00:08:08.700> to<00:08:08.850> happen<00:08:09.120> right 00:08:09.380 --> 00:08:09.390 align:start position:0% 10 minutes for something to happen right 00:08:09.390 --> 00:08:12.200 align:start position:0% 10 minutes for something to happen right so<00:08:09.710> with<00:08:10.710> backing<00:08:11.190> with<00:08:11.490> infrastructure<00:08:11.940> you 00:08:12.200 --> 00:08:12.210 align:start position:0% so with backing with infrastructure you 00:08:12.210 --> 00:08:13.490 align:start position:0% so with backing with infrastructure you end<00:08:12.360> up<00:08:12.420> with<00:08:12.510> something<00:08:12.660> like<00:08:12.840> this<00:08:13.020> you<00:08:13.440> have 00:08:13.490 --> 00:08:13.500 align:start position:0% end up with something like this you have 00:08:13.500 --> 00:08:15.920 align:start position:0% end up with something like this you have one<00:08:13.770> API<00:08:14.040> call<00:08:14.370> that<00:08:14.580> just<00:08:15.210> immediately<00:08:15.720> gets 00:08:15.920 --> 00:08:15.930 align:start position:0% one API call that just immediately gets 00:08:15.930 --> 00:08:18.680 align:start position:0% one API call that just immediately gets you<00:08:16.020> back<00:08:16.200> all<00:08:16.410> the<00:08:16.560> data<00:08:16.770> that<00:08:17.220> you<00:08:17.340> need<00:08:17.690> so 00:08:18.680 --> 00:08:18.690 align:start position:0% you back all the data that you need so 00:08:18.690 --> 00:08:21.470 align:start position:0% you back all the data that you need so in<00:08:19.140> in<00:08:20.070> one<00:08:20.430> line<00:08:20.580> of<00:08:20.700> code<00:08:20.730> and<00:08:21.090> most 00:08:21.470 --> 00:08:21.480 align:start position:0% in in one line of code and most 00:08:21.480 --> 00:08:22.850 align:start position:0% in in one line of code and most importantly<00:08:21.930> the<00:08:22.230> application<00:08:22.650> loads 00:08:22.850 --> 00:08:22.860 align:start position:0% importantly the application loads 00:08:22.860 --> 00:08:25.250 align:start position:0% importantly the application loads instantly<00:08:23.310> so<00:08:23.850> that's<00:08:24.420> kind<00:08:24.780> of<00:08:24.810> one<00:08:25.080> example 00:08:25.250 --> 00:08:25.260 align:start position:0% instantly so that's kind of one example 00:08:25.260 --> 00:08:27.890 align:start position:0% instantly so that's kind of one example and<00:08:25.770> this<00:08:26.160> is<00:08:26.310> an<00:08:26.400> example<00:08:26.640> where<00:08:26.970> the<00:08:27.480> smart 00:08:27.890 --> 00:08:27.900 align:start position:0% and this is an example where the smart 00:08:27.900 --> 00:08:29.300 align:start position:0% and this is an example where the smart contract<00:08:28.350> and<00:08:28.500> this<00:08:28.560> is<00:08:28.680> a<00:08:28.740> distinction<00:08:29.100> I'm 00:08:29.300 --> 00:08:29.310 align:start position:0% contract and this is a distinction I'm 00:08:29.310 --> 00:08:30.590 align:start position:0% contract and this is a distinction I'm gonna<00:08:29.460> make<00:08:29.580> between<00:08:29.730> this<00:08:30.000> example<00:08:30.390> in<00:08:30.540> the 00:08:30.590 --> 00:08:30.600 align:start position:0% gonna make between this example in the 00:08:30.600 --> 00:08:32.360 align:start position:0% gonna make between this example in the next<00:08:30.810> example<00:08:31.230> is<00:08:31.350> the<00:08:31.680> smart<00:08:31.950> contract 00:08:32.360 --> 00:08:32.370 align:start position:0% next example is the smart contract 00:08:32.370 --> 00:08:34.160 align:start position:0% next example is the smart contract actually<00:08:32.550> doesn't<00:08:33.090> have<00:08:33.180> any<00:08:33.390> methods<00:08:33.750> for 00:08:34.160 --> 00:08:34.170 align:start position:0% actually doesn't have any methods for 00:08:34.170 --> 00:08:35.510 align:start position:0% actually doesn't have any methods for getting<00:08:34.290> duels<00:08:34.710> for<00:08:34.860> wizard<00:08:35.160> you<00:08:35.280> actually 00:08:35.510 --> 00:08:35.520 align:start position:0% getting duels for wizard you actually 00:08:35.520 --> 00:08:36.830 align:start position:0% getting duels for wizard you actually have<00:08:35.610> to<00:08:35.670> go<00:08:35.729> explore<00:08:36.120> all<00:08:36.240> the<00:08:36.360> logs<00:08:36.570> and<00:08:36.780> the 00:08:36.830 --> 00:08:36.840 align:start position:0% have to go explore all the logs and the 00:08:36.840 --> 00:08:38.690 align:start position:0% have to go explore all the logs and the events<00:08:37.170> and<00:08:37.350> all<00:08:37.650> that<00:08:37.860> stuff<00:08:38.070> so<00:08:38.250> this<00:08:38.340> is<00:08:38.490> not 00:08:38.690 --> 00:08:38.700 align:start position:0% events and all that stuff so this is not 00:08:38.700 --> 00:08:40.969 align:start position:0% events and all that stuff so this is not built<00:08:39.000> into<00:08:39.150> the<00:08:39.330> smart<00:08:39.570> contract<00:08:39.690> right<00:08:40.470> so 00:08:40.969 --> 00:08:40.979 align:start position:0% built into the smart contract right so 00:08:40.979 --> 00:08:43.040 align:start position:0% built into the smart contract right so now<00:08:41.130> you<00:08:41.190> say<00:08:41.520> ok<00:08:41.910> what<00:08:42.240> if<00:08:42.330> it<00:08:42.420> is<00:08:42.600> built<00:08:42.900> into 00:08:43.040 --> 00:08:43.050 align:start position:0% now you say ok what if it is built into 00:08:43.050 --> 00:08:44.390 align:start position:0% now you say ok what if it is built into the<00:08:43.170> smart<00:08:43.380> contract<00:08:43.740> what<00:08:43.979> does<00:08:44.070> that<00:08:44.100> look 00:08:44.390 --> 00:08:44.400 align:start position:0% the smart contract what does that look 00:08:44.400 --> 00:08:46.700 align:start position:0% the smart contract what does that look like<00:08:44.430> alright<00:08:45.060> so<00:08:45.270> here's<00:08:45.450> here's<00:08:45.690> the<00:08:45.960> API 00:08:46.700 --> 00:08:46.710 align:start position:0% like alright so here's here's the API 00:08:46.710 --> 00:08:48.230 align:start position:0% like alright so here's here's the API call<00:08:46.980> that<00:08:47.160> actually<00:08:47.520> is<00:08:47.640> built<00:08:47.940> into<00:08:48.090> the 00:08:48.230 --> 00:08:48.240 align:start position:0% call that actually is built into the 00:08:48.240 --> 00:08:50.990 align:start position:0% call that actually is built into the smart<00:08:48.450> contract<00:08:49.100> there's<00:08:50.100> we<00:08:50.550> want<00:08:50.760> to<00:08:50.850> do 00:08:50.990 --> 00:08:51.000 align:start position:0% smart contract there's we want to do 00:08:51.000 --> 00:08:52.340 align:start position:0% smart contract there's we want to do let's<00:08:51.300> say<00:08:51.330> we<00:08:51.480> want<00:08:51.600> to<00:08:51.630> get<00:08:51.720> all<00:08:51.900> the<00:08:52.020> wizards 00:08:52.340 --> 00:08:52.350 align:start position:0% let's say we want to get all the wizards 00:08:52.350 --> 00:08:55.640 align:start position:0% let's say we want to get all the wizards owned<00:08:52.800> by<00:08:53.160> like<00:08:53.730> Joe<00:08:54.000> Wright<00:08:54.360> and<00:08:54.600> we<00:08:55.380> want<00:08:55.560> to 00:08:55.640 --> 00:08:55.650 align:start position:0% owned by like Joe Wright and we want to 00:08:55.650 --> 00:08:57.500 align:start position:0% owned by like Joe Wright and we want to see<00:08:55.800> is<00:08:56.040> he<00:08:56.580> does<00:08:56.940> he<00:08:57.030> have<00:08:57.120> any<00:08:57.270> cool<00:08:57.480> ones 00:08:57.500 --> 00:08:57.510 align:start position:0% see is he does he have any cool ones 00:08:57.510 --> 00:08:59.220 align:start position:0% see is he does he have any cool ones Donna 00:08:59.220 --> 00:08:59.230 align:start position:0% Donna 00:08:59.230 --> 00:09:01.110 align:start position:0% Donna so<00:08:59.680> the<00:08:59.769> smart<00:08:59.949> contract<00:09:00.250> actually<00:09:00.459> has<00:09:00.760> a 00:09:01.110 --> 00:09:01.120 align:start position:0% so the smart contract actually has a 00:09:01.120 --> 00:09:03.509 align:start position:0% so the smart contract actually has a method<00:09:01.899> that's<00:09:02.079> called<00:09:02.139> get<00:09:02.680> wizard<00:09:03.100> by<00:09:03.250> ID 00:09:03.509 --> 00:09:03.519 align:start position:0% method that's called get wizard by ID 00:09:03.519 --> 00:09:05.970 align:start position:0% method that's called get wizard by ID but<00:09:04.420> the<00:09:04.690> challenge<00:09:05.260> is<00:09:05.320> we<00:09:05.440> don't<00:09:05.529> want<00:09:05.740> it<00:09:05.860> we 00:09:05.970 --> 00:09:05.980 align:start position:0% but the challenge is we don't want it we 00:09:05.980 --> 00:09:07.110 align:start position:0% but the challenge is we don't want it we don't<00:09:06.130> know<00:09:06.190> the<00:09:06.310> idea<00:09:06.399> of<00:09:06.550> the<00:09:06.670> wizard<00:09:06.940> we 00:09:07.110 --> 00:09:07.120 align:start position:0% don't know the idea of the wizard we 00:09:07.120 --> 00:09:09.990 align:start position:0% don't know the idea of the wizard we want<00:09:07.360> joe's<00:09:07.839> wizards<00:09:08.260> right<00:09:08.649> and<00:09:08.949> that<00:09:09.490> small 00:09:09.990 --> 00:09:10.000 align:start position:0% want joe's wizards right and that small 00:09:10.000 --> 00:09:13.199 align:start position:0% want joe's wizards right and that small tweak<00:09:10.449> in<00:09:10.720> the<00:09:11.470> smart<00:09:11.709> contract<00:09:12.100> is<00:09:12.279> makes<00:09:13.000> it 00:09:13.199 --> 00:09:13.209 align:start position:0% tweak in the smart contract is makes it 00:09:13.209 --> 00:09:15.750 align:start position:0% tweak in the smart contract is makes it so<00:09:13.360> that<00:09:13.510> you<00:09:13.720> actually<00:09:13.899> can't<00:09:14.440> get<00:09:15.339> the<00:09:15.490> data 00:09:15.750 --> 00:09:15.760 align:start position:0% so that you actually can't get the data 00:09:15.760 --> 00:09:17.519 align:start position:0% so that you actually can't get the data you<00:09:15.850> need<00:09:16.000> so<00:09:16.570> the<00:09:16.779> challenge<00:09:17.139> here<00:09:17.320> is<00:09:17.500> that 00:09:17.519 --> 00:09:17.529 align:start position:0% you need so the challenge here is that 00:09:17.529 --> 00:09:19.889 align:start position:0% you need so the challenge here is that in<00:09:18.250> order<00:09:18.670> there's<00:09:18.940> no<00:09:19.209> way<00:09:19.480> the<00:09:19.660> smart 00:09:19.889 --> 00:09:19.899 align:start position:0% in order there's no way the smart 00:09:19.899 --> 00:09:21.840 align:start position:0% in order there's no way the smart contract<00:09:20.230> can<00:09:20.380> have<00:09:20.500> all<00:09:20.740> of<00:09:21.130> the<00:09:21.250> methods<00:09:21.639> to 00:09:21.840 --> 00:09:21.850 align:start position:0% contract can have all of the methods to 00:09:21.850 --> 00:09:24.269 align:start position:0% contract can have all of the methods to any<00:09:22.750> kind<00:09:23.110> of<00:09:23.199> way<00:09:23.500> that<00:09:23.529> people<00:09:24.100> want<00:09:24.250> to 00:09:24.269 --> 00:09:24.279 align:start position:0% any kind of way that people want to 00:09:24.279 --> 00:09:25.920 align:start position:0% any kind of way that people want to build<00:09:24.430> applications<00:09:24.550> so<00:09:25.360> if<00:09:25.630> it's<00:09:25.810> not 00:09:25.920 --> 00:09:25.930 align:start position:0% build applications so if it's not 00:09:25.930 --> 00:09:28.139 align:start position:0% build applications so if it's not exactly<00:09:26.500> what<00:09:26.769> you<00:09:26.889> want<00:09:27.160> you<00:09:27.639> still<00:09:27.880> end<00:09:28.089> up 00:09:28.139 --> 00:09:28.149 align:start position:0% exactly what you want you still end up 00:09:28.149 --> 00:09:30.480 align:start position:0% exactly what you want you still end up with<00:09:28.209> something<00:09:28.449> like<00:09:28.630> this<00:09:28.810> right<00:09:29.139> this<00:09:30.070> this 00:09:30.480 --> 00:09:30.490 align:start position:0% with something like this right this this 00:09:30.490 --> 00:09:32.220 align:start position:0% with something like this right this this actually<00:09:30.970> fit<00:09:31.300> into<00:09:31.420> one<00:09:31.540> screenshot<00:09:31.959> so<00:09:32.139> we 00:09:32.220 --> 00:09:32.230 align:start position:0% actually fit into one screenshot so we 00:09:32.230 --> 00:09:33.300 align:start position:0% actually fit into one screenshot so we left<00:09:32.380> it<00:09:32.470> like<00:09:32.589> this<00:09:32.709> I<00:09:32.800> think<00:09:32.949> we<00:09:33.010> cut<00:09:33.160> out<00:09:33.250> a 00:09:33.300 --> 00:09:33.310 align:start position:0% left it like this I think we cut out a 00:09:33.310 --> 00:09:35.189 align:start position:0% left it like this I think we cut out a few<00:09:33.550> variable<00:09:34.180> definitions<00:09:34.630> and<00:09:34.810> stuff<00:09:34.990> but 00:09:35.189 --> 00:09:35.199 align:start position:0% few variable definitions and stuff but 00:09:35.199 --> 00:09:36.840 align:start position:0% few variable definitions and stuff but it's<00:09:35.620> essentially<00:09:36.070> like<00:09:36.250> a<00:09:36.399> bunch<00:09:36.610> of<00:09:36.699> code 00:09:36.840 --> 00:09:36.850 align:start position:0% it's essentially like a bunch of code 00:09:36.850 --> 00:09:37.470 align:start position:0% it's essentially like a bunch of code you<00:09:36.940> have<00:09:36.970> to<00:09:37.060> write<00:09:37.120> it's<00:09:37.300> really 00:09:37.470 --> 00:09:37.480 align:start position:0% you have to write it's really 00:09:37.480 --> 00:09:39.810 align:start position:0% you have to write it's really complicated<00:09:37.750> and<00:09:38.170> most<00:09:38.920> importantly<00:09:39.339> you 00:09:39.810 --> 00:09:39.820 align:start position:0% complicated and most importantly you 00:09:39.820 --> 00:09:41.340 align:start position:0% complicated and most importantly you know<00:09:39.940> it's<00:09:40.209> the<00:09:40.360> same<00:09:40.540> thing<00:09:40.779> the<00:09:41.079> smart 00:09:41.340 --> 00:09:41.350 align:start position:0% know it's the same thing the smart 00:09:41.350 --> 00:09:43.650 align:start position:0% know it's the same thing the smart contracts<00:09:41.769> method<00:09:42.430> exists<00:09:43.269> but<00:09:43.449> it's<00:09:43.570> not 00:09:43.650 --> 00:09:43.660 align:start position:0% contracts method exists but it's not 00:09:43.660 --> 00:09:45.090 align:start position:0% contracts method exists but it's not exactly<00:09:43.810> what<00:09:44.079> we<00:09:44.139> need<00:09:44.350> so<00:09:44.680> you<00:09:44.769> still<00:09:44.980> have 00:09:45.090 --> 00:09:45.100 align:start position:0% exactly what we need so you still have 00:09:45.100 --> 00:09:46.319 align:start position:0% exactly what we need so you still have to<00:09:45.160> go<00:09:45.250> through<00:09:45.430> all<00:09:45.519> the<00:09:45.639> logs<00:09:45.850> and<00:09:46.060> events 00:09:46.319 --> 00:09:46.329 align:start position:0% to go through all the logs and events 00:09:46.329 --> 00:09:47.430 align:start position:0% to go through all the logs and events and<00:09:46.480> it<00:09:46.540> takes<00:09:46.839> about<00:09:46.959> ten<00:09:47.199> and<00:09:47.290> a<00:09:47.350> half 00:09:47.430 --> 00:09:47.440 align:start position:0% and it takes about ten and a half 00:09:47.440 --> 00:09:49.949 align:start position:0% and it takes about ten and a half minutes<00:09:47.740> to<00:09:47.829> load<00:09:48.310> a<00:09:48.339> page<00:09:48.550> so<00:09:49.029> now<00:09:49.540> with<00:09:49.870> the 00:09:49.949 --> 00:09:49.959 align:start position:0% minutes to load a page so now with the 00:09:49.959 --> 00:09:51.329 align:start position:0% minutes to load a page so now with the API<00:09:50.199> you<00:09:50.620> end<00:09:50.769> up<00:09:50.860> with<00:09:50.949> something<00:09:51.070> like<00:09:51.220> this 00:09:51.329 --> 00:09:51.339 align:start position:0% API you end up with something like this 00:09:51.339 --> 00:09:54.540 align:start position:0% API you end up with something like this one<00:09:51.699> line<00:09:51.880> and<00:09:52.149> it's<00:09:52.870> loads<00:09:53.440> instantly<00:09:53.649> right 00:09:54.540 --> 00:09:54.550 align:start position:0% one line and it's loads instantly right 00:09:54.550 --> 00:09:57.300 align:start position:0% one line and it's loads instantly right so<00:09:55.230> that's<00:09:56.230> that's<00:09:56.709> kind<00:09:56.889> of<00:09:57.040> a<00:09:57.160> couple 00:09:57.300 --> 00:09:57.310 align:start position:0% so that's that's kind of a couple 00:09:57.310 --> 00:09:59.100 align:start position:0% so that's that's kind of a couple examples<00:09:57.519> of<00:09:57.850> why<00:09:58.180> it's<00:09:58.570> important<00:09:59.019> so 00:09:59.100 --> 00:09:59.110 align:start position:0% examples of why it's important so 00:09:59.110 --> 00:10:00.810 align:start position:0% examples of why it's important so hopefully<00:09:59.380> you<00:09:59.440> can<00:09:59.529> see<00:09:59.769> that<00:10:00.310> this<00:10:00.639> is<00:10:00.790> a 00:10:00.810 --> 00:10:00.820 align:start position:0% hopefully you can see that this is a 00:10:00.820 --> 00:10:03.480 align:start position:0% hopefully you can see that this is a really<00:10:01.209> really<00:10:01.949> huge<00:10:02.949> difference<00:10:03.370> in 00:10:03.480 --> 00:10:03.490 align:start position:0% really really huge difference in 00:10:03.490 --> 00:10:05.220 align:start position:0% really really huge difference in developer<00:10:03.850> experience<00:10:04.600> not<00:10:04.810> only<00:10:04.839> is<00:10:05.199> it 00:10:05.220 --> 00:10:05.230 align:start position:0% developer experience not only is it 00:10:05.230 --> 00:10:06.990 align:start position:0% developer experience not only is it easier<00:10:05.649> and<00:10:05.709> you<00:10:05.800> write<00:10:05.980> less<00:10:06.160> code<00:10:06.190> but<00:10:06.880> it's 00:10:06.990 --> 00:10:07.000 align:start position:0% easier and you write less code but it's 00:10:07.000 --> 00:10:08.759 align:start position:0% easier and you write less code but it's also<00:10:07.389> enables<00:10:07.930> you<00:10:08.050> to<00:10:08.110> do<00:10:08.290> things<00:10:08.529> that<00:10:08.649> you 00:10:08.759 --> 00:10:08.769 align:start position:0% also enables you to do things that you 00:10:08.769 --> 00:10:10.139 align:start position:0% also enables you to do things that you couldn't<00:10:08.980> before<00:10:09.190> unless<00:10:09.730> you're<00:10:09.910> gonna<00:10:10.000> go 00:10:10.139 --> 00:10:10.149 align:start position:0% couldn't before unless you're gonna go 00:10:10.149 --> 00:10:11.309 align:start position:0% couldn't before unless you're gonna go sit<00:10:10.389> there<00:10:10.540> and<00:10:10.630> say<00:10:10.750> I<00:10:10.899> wouldn't<00:10:11.110> build<00:10:11.260> a 00:10:11.309 --> 00:10:11.319 align:start position:0% sit there and say I wouldn't build a 00:10:11.319 --> 00:10:12.900 align:start position:0% sit there and say I wouldn't build a cheese<00:10:11.500> was<00:10:11.649> a<00:10:11.680> game<00:10:11.980> but<00:10:12.279> first<00:10:12.459> let<00:10:12.670> me<00:10:12.699> spend 00:10:12.900 --> 00:10:12.910 align:start position:0% cheese was a game but first let me spend 00:10:12.910 --> 00:10:14.040 align:start position:0% cheese was a game but first let me spend like<00:10:13.029> a<00:10:13.180> week<00:10:13.209> building<00:10:13.779> out<00:10:13.870> all<00:10:13.959> the 00:10:14.040 --> 00:10:14.050 align:start position:0% like a week building out all the 00:10:14.050 --> 00:10:16.470 align:start position:0% like a week building out all the infrastructure<00:10:14.500> to<00:10:14.740> do<00:10:14.980> all<00:10:15.100> this<00:10:15.250> right<00:10:16.060> so 00:10:16.470 --> 00:10:16.480 align:start position:0% infrastructure to do all this right so 00:10:16.480 --> 00:10:19.199 align:start position:0% infrastructure to do all this right so let's<00:10:16.870> go<00:10:17.019> finally<00:10:17.800> want<00:10:18.730> to<00:10:18.819> go<00:10:18.910> over<00:10:19.180> a 00:10:19.199 --> 00:10:19.209 align:start position:0% let's go finally want to go over a 00:10:19.209 --> 00:10:21.629 align:start position:0% let's go finally want to go over a couple<00:10:19.480> principles<00:10:20.050> API<00:10:20.380> design<00:10:20.740> so<00:10:20.980> we<00:10:21.100> we 00:10:21.629 --> 00:10:21.639 align:start position:0% couple principles API design so we we 00:10:21.639 --> 00:10:24.030 align:start position:0% couple principles API design so we we now<00:10:21.880> power<00:10:22.230> nobody<00:10:23.230> can<00:10:23.350> say<00:10:23.470> publicly<00:10:23.800> we<00:10:23.949> now 00:10:24.030 --> 00:10:24.040 align:start position:0% now power nobody can say publicly we now 00:10:24.040 --> 00:10:25.530 align:start position:0% now power nobody can say publicly we now power<00:10:24.279> billions<00:10:24.730> of<00:10:24.760> billions<00:10:24.910> queries<00:10:25.300> for 00:10:25.530 --> 00:10:25.540 align:start position:0% power billions of billions queries for 00:10:25.540 --> 00:10:27.509 align:start position:0% power billions of billions queries for hundreds<00:10:25.930> companies<00:10:26.199> around<00:10:26.319> the<00:10:26.440> world<00:10:26.560> so<00:10:27.100> a 00:10:27.509 --> 00:10:27.519 align:start position:0% hundreds companies around the world so a 00:10:27.519 --> 00:10:29.040 align:start position:0% hundreds companies around the world so a few<00:10:28.000> things<00:10:28.209> that<00:10:28.360> we've<00:10:28.480> learned<00:10:28.690> from 00:10:29.040 --> 00:10:29.050 align:start position:0% few things that we've learned from 00:10:29.050 --> 00:10:31.500 align:start position:0% few things that we've learned from talking<00:10:29.230> to<00:10:29.440> hundreds<00:10:30.250> of<00:10:30.339> companies<00:10:30.490> so<00:10:30.850> the 00:10:31.500 --> 00:10:31.510 align:start position:0% talking to hundreds of companies so the 00:10:31.510 --> 00:10:33.540 align:start position:0% talking to hundreds of companies so the first<00:10:32.110> thing<00:10:32.319> is<00:10:32.649> it's<00:10:33.040> really<00:10:33.250> important<00:10:33.490> to 00:10:33.540 --> 00:10:33.550 align:start position:0% first thing is it's really important to 00:10:33.550 --> 00:10:35.370 align:start position:0% first thing is it's really important to understand<00:10:33.880> your<00:10:34.029> goals<00:10:34.240> and<00:10:34.449> this<00:10:34.600> sounds 00:10:35.370 --> 00:10:35.380 align:start position:0% understand your goals and this sounds 00:10:35.380 --> 00:10:38.400 align:start position:0% understand your goals and this sounds very<00:10:35.430> obvious<00:10:36.430> but<00:10:36.730> it's<00:10:37.240> actually<00:10:37.660> not<00:10:38.139> and 00:10:38.400 --> 00:10:38.410 align:start position:0% very obvious but it's actually not and 00:10:38.410 --> 00:10:40.230 align:start position:0% very obvious but it's actually not and the<00:10:39.040> reason<00:10:39.069> is<00:10:39.459> you<00:10:39.490> kind<00:10:39.790> of<00:10:39.850> sit<00:10:40.029> there<00:10:40.060> and 00:10:40.230 --> 00:10:40.240 align:start position:0% the reason is you kind of sit there and 00:10:40.240 --> 00:10:41.879 align:start position:0% the reason is you kind of sit there and think<00:10:40.360> okay<00:10:40.839> cool<00:10:41.050> like<00:10:41.230> yeah<00:10:41.589> we<00:10:41.709> want 00:10:41.879 --> 00:10:41.889 align:start position:0% think okay cool like yeah we want 00:10:41.889 --> 00:10:43.319 align:start position:0% think okay cool like yeah we want developers<00:10:42.339> use<00:10:42.519> this<00:10:42.670> let's<00:10:42.880> just<00:10:42.910> like<00:10:43.149> put 00:10:43.319 --> 00:10:43.329 align:start position:0% developers use this let's just like put 00:10:43.329 --> 00:10:44.639 align:start position:0% developers use this let's just like put something<00:10:43.480> together<00:10:43.690> but<00:10:44.050> I<00:10:44.319> think<00:10:44.350> there's 00:10:44.639 --> 00:10:44.649 align:start position:0% something together but I think there's 00:10:44.649 --> 00:10:46.259 align:start position:0% something together but I think there's actually<00:10:45.069> like<00:10:45.220> a<00:10:45.250> very<00:10:45.639> big<00:10:45.910> trade-off 00:10:46.259 --> 00:10:46.269 align:start position:0% actually like a very big trade-off 00:10:46.269 --> 00:10:49.350 align:start position:0% actually like a very big trade-off around<00:10:46.839> how<00:10:47.350> easy<00:10:47.680> is<00:10:47.889> it<00:10:47.920> to<00:10:48.069> use<00:10:48.399> how<00:10:48.880> fast<00:10:49.180> is 00:10:49.350 --> 00:10:49.360 align:start position:0% around how easy is it to use how fast is 00:10:49.360 --> 00:10:51.059 align:start position:0% around how easy is it to use how fast is it<00:10:49.480> for<00:10:49.630> developers<00:10:50.110> how<00:10:50.470> much<00:10:50.620> time<00:10:50.860> do<00:10:51.010> you 00:10:51.059 --> 00:10:51.069 align:start position:0% it for developers how much time do you 00:10:51.069 --> 00:10:53.160 align:start position:0% it for developers how much time do you want<00:10:51.339> to<00:10:51.430> invest<00:10:51.730> you<00:10:52.240> know<00:10:52.360> are<00:10:52.630> you<00:10:52.870> gonna<00:10:52.990> be 00:10:53.160 --> 00:10:53.170 align:start position:0% want to invest you know are you gonna be 00:10:53.170 --> 00:10:54.329 align:start position:0% want to invest you know are you gonna be building<00:10:53.470> out<00:10:53.560> the<00:10:53.740> full<00:10:54.010> end-to-end 00:10:54.329 --> 00:10:54.339 align:start position:0% building out the full end-to-end 00:10:54.339 --> 00:10:55.439 align:start position:0% building out the full end-to-end experience<00:10:54.610> and<00:10:55.029> there's<00:10:55.149> a<00:10:55.209> lot<00:10:55.329> of 00:10:55.439 --> 00:10:55.449 align:start position:0% experience and there's a lot of 00:10:55.449 --> 00:10:57.360 align:start position:0% experience and there's a lot of trade-offs<00:10:55.690> here<00:10:56.079> and<00:10:56.290> really<00:10:56.980> clearly 00:10:57.360 --> 00:10:57.370 align:start position:0% trade-offs here and really clearly 00:10:57.370 --> 00:10:58.889 align:start position:0% trade-offs here and really clearly defining<00:10:57.819> your<00:10:57.880> goals<00:10:58.120> is<00:10:58.360> really<00:10:58.389> really 00:10:58.889 --> 00:10:58.899 align:start position:0% defining your goals is really really 00:10:58.899 --> 00:11:01.050 align:start position:0% defining your goals is really really important<00:10:59.319> than<00:10:59.410> that<00:10:59.550> again<00:11:00.550> something<00:11:00.819> that 00:11:01.050 --> 00:11:01.060 align:start position:0% important than that again something that 00:11:01.060 --> 00:11:02.460 align:start position:0% important than that again something that as<00:11:01.240> an<00:11:01.360> engineer<00:11:01.690> when<00:11:01.870> I<00:11:01.959> look<00:11:02.110> at<00:11:02.170> stuff<00:11:02.350> like 00:11:02.460 --> 00:11:02.470 align:start position:0% as an engineer when I look at stuff like 00:11:02.470 --> 00:11:04.110 align:start position:0% as an engineer when I look at stuff like this<00:11:02.620> you<00:11:02.860> know<00:11:02.980> I'm<00:11:03.430> like<00:11:03.579> ah<00:11:03.730> this<00:11:03.970> is 00:11:04.110 --> 00:11:04.120 align:start position:0% this you know I'm like ah this is 00:11:04.120 --> 00:11:05.340 align:start position:0% this you know I'm like ah this is obvious<00:11:04.449> but<00:11:04.600> then<00:11:04.750> when<00:11:04.870> you<00:11:04.930> actually<00:11:05.050> sit 00:11:05.340 --> 00:11:05.350 align:start position:0% obvious but then when you actually sit 00:11:05.350 --> 00:11:06.540 align:start position:0% obvious but then when you actually sit down<00:11:05.380> and<00:11:05.500> do<00:11:05.680> it<00:11:05.769> this<00:11:05.860> is<00:11:06.010> one<00:11:06.130> of<00:11:06.160> the<00:11:06.279> really 00:11:06.540 --> 00:11:06.550 align:start position:0% down and do it this is one of the really 00:11:06.550 --> 00:11:08.009 align:start position:0% down and do it this is one of the really most<00:11:06.730> important<00:11:07.149> things<00:11:07.300> know<00:11:07.600> what<00:11:07.720> you<00:11:07.810> want 00:11:08.009 --> 00:11:08.019 align:start position:0% most important things know what you want 00:11:08.019 --> 00:11:10.650 align:start position:0% most important things know what you want the<00:11:09.010> second<00:11:09.279> thing<00:11:09.399> in<00:11:09.610> again<00:11:10.149> something<00:11:10.540> that 00:11:10.650 --> 00:11:10.660 align:start position:0% the second thing in again something that 00:11:10.660 --> 00:11:12.280 align:start position:0% the second thing in again something that sounds<00:11:11.019> really<00:11:11.500> obvious<00:11:11.680> but<00:11:11.980> may 00:11:12.280 --> 00:11:12.290 align:start position:0% sounds really obvious but may 00:11:12.290 --> 00:11:15.129 align:start position:0% sounds really obvious but may a<00:11:12.320> huge<00:11:12.920> huge<00:11:13.190> huge<00:11:13.399> difference<00:11:13.839> really<00:11:14.839> like 00:11:15.129 --> 00:11:15.139 align:start position:0% a huge huge huge difference really like 00:11:15.139 --> 00:11:16.960 align:start position:0% a huge huge huge difference really like talk<00:11:15.560> to<00:11:15.740> your<00:11:15.860> users<00:11:16.160> and<00:11:16.190> understand<00:11:16.820> what 00:11:16.960 --> 00:11:16.970 align:start position:0% talk to your users and understand what 00:11:16.970 --> 00:11:18.550 align:start position:0% talk to your users and understand what they<00:11:17.060> want<00:11:17.240> right<00:11:17.660> you<00:11:17.810> think<00:11:18.050> that<00:11:18.230> you<00:11:18.320> know 00:11:18.550 --> 00:11:18.560 align:start position:0% they want right you think that you know 00:11:18.560 --> 00:11:20.920 align:start position:0% they want right you think that you know but<00:11:19.130> you<00:11:19.759> know<00:11:19.850> you<00:11:20.060> might<00:11:20.269> know<00:11:20.480> but<00:11:20.810> you 00:11:20.920 --> 00:11:20.930 align:start position:0% but you know you might know but you 00:11:20.930 --> 00:11:22.540 align:start position:0% but you know you might know but you probably<00:11:21.320> don't<00:11:21.560> know<00:11:21.680> all<00:11:21.920> of<00:11:21.949> it<00:11:22.100> right<00:11:22.339> so 00:11:22.540 --> 00:11:22.550 align:start position:0% probably don't know all of it right so 00:11:22.550 --> 00:11:24.280 align:start position:0% probably don't know all of it right so one<00:11:23.029> of<00:11:23.120> the<00:11:23.180> examples<00:11:23.570> was<00:11:23.750> when<00:11:23.899> we<00:11:24.019> built 00:11:24.280 --> 00:11:24.290 align:start position:0% one of the examples was when we built 00:11:24.290 --> 00:11:25.569 align:start position:0% one of the examples was when we built this<00:11:24.410> consumer<00:11:24.829> app<00:11:24.949> is<00:11:25.070> called<00:11:25.250> down<00:11:25.430> to 00:11:25.569 --> 00:11:25.579 align:start position:0% this consumer app is called down to 00:11:25.579 --> 00:11:27.670 align:start position:0% this consumer app is called down to lunch<00:11:25.730> we<00:11:26.360> actually<00:11:26.690> put<00:11:26.839> wheat<00:11:27.019> so<00:11:27.199> it<00:11:27.470> kind 00:11:27.670 --> 00:11:27.680 align:start position:0% lunch we actually put wheat so it kind 00:11:27.680 --> 00:11:28.780 align:start position:0% lunch we actually put wheat so it kind of<00:11:27.709> start<00:11:27.920> off<00:11:27.980> this<00:11:28.130> thing<00:11:28.399> where<00:11:28.550> we<00:11:28.579> thought 00:11:28.780 --> 00:11:28.790 align:start position:0% of start off this thing where we thought 00:11:28.790 --> 00:11:30.579 align:start position:0% of start off this thing where we thought no<00:11:28.940> one<00:11:29.060> would<00:11:29.149> use<00:11:29.329> it<00:11:29.509> and<00:11:29.690> we<00:11:30.019> put<00:11:30.199> our<00:11:30.319> phone 00:11:30.579 --> 00:11:30.589 align:start position:0% no one would use it and we put our phone 00:11:30.589 --> 00:11:32.800 align:start position:0% no one would use it and we put our phone number<00:11:30.889> in<00:11:31.040> the<00:11:31.220> app<00:11:31.339> and<00:11:31.639> anybody<00:11:32.329> could<00:11:32.569> text 00:11:32.800 --> 00:11:32.810 align:start position:0% number in the app and anybody could text 00:11:32.810 --> 00:11:33.939 align:start position:0% number in the app and anybody could text us<00:11:32.990> right<00:11:33.110> we<00:11:33.319> thought<00:11:33.529> it's<00:11:33.620> just<00:11:33.649> gonna<00:11:33.860> be 00:11:33.939 --> 00:11:33.949 align:start position:0% us right we thought it's just gonna be 00:11:33.949 --> 00:11:35.710 align:start position:0% us right we thought it's just gonna be our<00:11:34.040> two<00:11:34.190> friends<00:11:34.579> ended<00:11:35.149> up<00:11:35.209> being<00:11:35.360> Millie's 00:11:35.710 --> 00:11:35.720 align:start position:0% our two friends ended up being Millie's 00:11:35.720 --> 00:11:36.460 align:start position:0% our two friends ended up being Millie's people<00:11:35.930> around<00:11:36.050> the<00:11:36.199> world 00:11:36.460 --> 00:11:36.470 align:start position:0% people around the world 00:11:36.470 --> 00:11:38.199 align:start position:0% people around the world we<00:11:36.589> started<00:11:36.860> getting<00:11:36.949> 10,000<00:11:37.610> text<00:11:37.819> messages 00:11:38.199 --> 00:11:38.209 align:start position:0% we started getting 10,000 text messages 00:11:38.209 --> 00:11:39.970 align:start position:0% we started getting 10,000 text messages a<00:11:38.240> day<00:11:38.329> literally<00:11:39.110> broke<00:11:39.380> the<00:11:39.560> iMessage 00:11:39.970 --> 00:11:39.980 align:start position:0% a day literally broke the iMessage 00:11:39.980 --> 00:11:41.470 align:start position:0% a day literally broke the iMessage infrastructure<00:11:40.550> I<00:11:40.610> had<00:11:40.730> to<00:11:40.819> email<00:11:40.940> Tim<00:11:41.269> Cook 00:11:41.470 --> 00:11:41.480 align:start position:0% infrastructure I had to email Tim Cook 00:11:41.480 --> 00:11:42.819 align:start position:0% infrastructure I had to email Tim Cook the<00:11:41.509> CEO<00:11:41.779> of<00:11:41.899> Apple<00:11:41.990> and<00:11:42.139> be<00:11:42.230> like<00:11:42.350> we<00:11:42.740> were 00:11:42.819 --> 00:11:42.829 align:start position:0% the CEO of Apple and be like we were 00:11:42.829 --> 00:11:44.439 align:start position:0% the CEO of Apple and be like we were almost<00:11:43.160> neighbors<00:11:43.339> you<00:11:43.730> have<00:11:43.970> to<00:11:44.120> help<00:11:44.240> me<00:11:44.389> I 00:11:44.439 --> 00:11:44.449 align:start position:0% almost neighbors you have to help me I 00:11:44.449 --> 00:11:45.819 align:start position:0% almost neighbors you have to help me I spent<00:11:44.720> three<00:11:44.870> days<00:11:44.959> at<00:11:45.139> Apple<00:11:45.500> Store<00:11:45.649> and<00:11:45.769> they 00:11:45.819 --> 00:11:45.829 align:start position:0% spent three days at Apple Store and they 00:11:45.829 --> 00:11:48.699 align:start position:0% spent three days at Apple Store and they didn't<00:11:46.519> help<00:11:46.670> me<00:11:46.730> right<00:11:46.910> and<00:11:47.089> the<00:11:47.720> the<00:11:48.199> result 00:11:48.699 --> 00:11:48.709 align:start position:0% didn't help me right and the the result 00:11:48.709 --> 00:11:50.620 align:start position:0% didn't help me right and the the result of<00:11:48.800> this<00:11:48.889> is<00:11:49.100> like<00:11:49.250> we<00:11:49.699> were<00:11:49.819> actually<00:11:49.970> really 00:11:50.620 --> 00:11:50.630 align:start position:0% of this is like we were actually really 00:11:50.630 --> 00:11:51.999 align:start position:0% of this is like we were actually really really<00:11:50.839> really<00:11:50.990> in<00:11:51.319> touch<00:11:51.440> with<00:11:51.500> our<00:11:51.709> users<00:11:51.980> so 00:11:51.999 --> 00:11:52.009 align:start position:0% really really in touch with our users so 00:11:52.009 --> 00:11:53.199 align:start position:0% really really in touch with our users so right<00:11:52.190> now<00:11:52.279> I<00:11:52.339> see<00:11:52.490> some<00:11:52.670> of<00:11:52.730> our<00:11:52.850> customers 00:11:53.199 --> 00:11:53.209 align:start position:0% right now I see some of our customers 00:11:53.209 --> 00:11:55.300 align:start position:0% right now I see some of our customers are<00:11:53.300> here<00:11:53.509> you<00:11:53.899> know<00:11:53.990> we<00:11:54.290> have<00:11:54.440> a<00:11:54.470> we<00:11:55.040> have<00:11:55.279> a 00:11:55.300 --> 00:11:55.310 align:start position:0% are here you know we have a we have a 00:11:55.310 --> 00:11:57.189 align:start position:0% are here you know we have a we have a telegram<00:11:55.610> chat<00:11:55.970> with<00:11:56.480> every<00:11:56.810> single<00:11:57.019> of<00:11:57.079> our 00:11:57.189 --> 00:11:57.199 align:start position:0% telegram chat with every single of our 00:11:57.199 --> 00:11:58.720 align:start position:0% telegram chat with every single of our customers<00:11:57.500> real-time<00:11:57.949> and<00:11:58.190> you<00:11:58.459> know<00:11:58.550> it's 00:11:58.720 --> 00:11:58.730 align:start position:0% customers real-time and you know it's 00:11:58.730 --> 00:12:00.129 align:start position:0% customers real-time and you know it's super<00:11:59.089> valuable<00:11:59.240> for<00:11:59.600> them<00:11:59.720> but<00:11:59.959> the<00:12:00.019> most 00:12:00.129 --> 00:12:00.139 align:start position:0% super valuable for them but the most 00:12:00.139 --> 00:12:01.269 align:start position:0% super valuable for them but the most important<00:12:00.470> thing<00:12:00.589> is<00:12:00.769> it's<00:12:01.040> really<00:12:01.069> valuable 00:12:01.269 --> 00:12:01.279 align:start position:0% important thing is it's really valuable 00:12:01.279 --> 00:12:02.860 align:start position:0% important thing is it's really valuable for<00:12:01.519> us<00:12:01.730> for<00:12:02.000> getting<00:12:02.180> feedback<00:12:02.300> on<00:12:02.509> what's 00:12:02.860 --> 00:12:02.870 align:start position:0% for us for getting feedback on what's 00:12:02.870 --> 00:12:04.509 align:start position:0% for us for getting feedback on what's good<00:12:03.110> and<00:12:03.290> what's<00:12:03.740> not<00:12:03.829> and<00:12:04.160> how<00:12:04.250> we<00:12:04.310> can 00:12:04.509 --> 00:12:04.519 align:start position:0% good and what's not and how we can 00:12:04.519 --> 00:12:06.579 align:start position:0% good and what's not and how we can improve<00:12:04.699> it<00:12:04.910> so<00:12:05.060> really<00:12:05.810> you<00:12:06.079> know<00:12:06.139> I<00:12:06.290> can't 00:12:06.579 --> 00:12:06.589 align:start position:0% improve it so really you know I can't 00:12:06.589 --> 00:12:08.889 align:start position:0% improve it so really you know I can't stress<00:12:06.920> this<00:12:07.100> enough<00:12:07.509> the<00:12:08.509> third<00:12:08.690> thing<00:12:08.839> is 00:12:08.889 --> 00:12:08.899 align:start position:0% stress this enough the third thing is 00:12:08.899 --> 00:12:10.360 align:start position:0% stress this enough the third thing is keep<00:12:09.110> it<00:12:09.230> simple<00:12:09.259> one<00:12:09.740> thing<00:12:09.889> that<00:12:10.009> we<00:12:10.100> see<00:12:10.130> in 00:12:10.360 --> 00:12:10.370 align:start position:0% keep it simple one thing that we see in 00:12:10.370 --> 00:12:12.040 align:start position:0% keep it simple one thing that we see in a<00:12:10.430> lot<00:12:10.459> of<00:12:10.639> developer<00:12:11.149> tools<00:12:11.329> an<00:12:11.449> API<00:12:11.660> designs 00:12:12.040 --> 00:12:12.050 align:start position:0% a lot of developer tools an API designs 00:12:12.050 --> 00:12:13.420 align:start position:0% a lot of developer tools an API designs and<00:12:12.290> documentation<00:12:13.100> so<00:12:13.190> that's<00:12:13.310> really 00:12:13.420 --> 00:12:13.430 align:start position:0% and documentation so that's really 00:12:13.430 --> 00:12:14.889 align:start position:0% and documentation so that's really complicated<00:12:13.699> like<00:12:14.240> and<00:12:14.480> you<00:12:14.750> have<00:12:14.779> to 00:12:14.889 --> 00:12:14.899 align:start position:0% complicated like and you have to 00:12:14.899 --> 00:12:17.439 align:start position:0% complicated like and you have to remember<00:12:15.190> building<00:12:16.190> if<00:12:16.880> you<00:12:17.060> let's<00:12:17.389> say 00:12:17.439 --> 00:12:17.449 align:start position:0% remember building if you let's say 00:12:17.449 --> 00:12:19.360 align:start position:0% remember building if you let's say you're<00:12:17.600> building<00:12:17.690> cheese<00:12:17.990> wizards<00:12:18.350> when<00:12:19.279> you 00:12:19.360 --> 00:12:19.370 align:start position:0% you're building cheese wizards when you 00:12:19.370 --> 00:12:20.769 align:start position:0% you're building cheese wizards when you have<00:12:19.490> these<00:12:19.670> developers<00:12:20.149> coming<00:12:20.360> to<00:12:20.510> use<00:12:20.630> your 00:12:20.769 --> 00:12:20.779 align:start position:0% have these developers coming to use your 00:12:20.779 --> 00:12:22.300 align:start position:0% have these developers coming to use your platform<00:12:20.899> that<00:12:21.680> is<00:12:21.800> not<00:12:21.980> their<00:12:22.160> main 00:12:22.300 --> 00:12:22.310 align:start position:0% platform that is not their main 00:12:22.310 --> 00:12:23.680 align:start position:0% platform that is not their main objective<00:12:22.790> in<00:12:22.880> life<00:12:22.910> their<00:12:23.180> main<00:12:23.300> objective 00:12:23.680 --> 00:12:23.690 align:start position:0% objective in life their main objective 00:12:23.690 --> 00:12:25.720 align:start position:0% objective in life their main objective in<00:12:23.750> life<00:12:23.870> is<00:12:24.050> not<00:12:24.079> how<00:12:24.889> do<00:12:24.949> I<00:12:25.069> build<00:12:25.279> the<00:12:25.459> best 00:12:25.720 --> 00:12:25.730 align:start position:0% in life is not how do I build the best 00:12:25.730 --> 00:12:27.069 align:start position:0% in life is not how do I build the best cheese<00:12:26.000> was<00:12:26.180> there<00:12:26.300> an<00:12:26.389> application<00:12:26.480> right 00:12:27.069 --> 00:12:27.079 align:start position:0% cheese was there an application right 00:12:27.079 --> 00:12:28.809 align:start position:0% cheese was there an application right there<00:12:27.529> coming<00:12:27.800> this<00:12:27.889> thing<00:12:28.100> they<00:12:28.430> have<00:12:28.519> 30 00:12:28.809 --> 00:12:28.819 align:start position:0% there coming this thing they have 30 00:12:28.819 --> 00:12:31.269 align:start position:0% there coming this thing they have 30 minutes<00:12:29.060> you<00:12:29.389> know<00:12:29.510> free<00:12:30.110> between<00:12:30.560> before<00:12:31.040> the 00:12:31.269 --> 00:12:31.279 align:start position:0% minutes you know free between before the 00:12:31.279 --> 00:12:32.500 align:start position:0% minutes you know free between before the game<00:12:31.399> of<00:12:31.430> Thrones<00:12:31.760> episode<00:12:32.149> and<00:12:32.269> they<00:12:32.329> just 00:12:32.500 --> 00:12:32.510 align:start position:0% game of Thrones episode and they just 00:12:32.510 --> 00:12:33.699 align:start position:0% game of Thrones episode and they just want<00:12:32.630> to<00:12:32.690> make<00:12:32.779> it<00:12:32.930> see<00:12:33.290> if<00:12:33.380> they<00:12:33.470> can<00:12:33.620> build 00:12:33.699 --> 00:12:33.709 align:start position:0% want to make it see if they can build 00:12:33.709 --> 00:12:34.329 align:start position:0% want to make it see if they can build something<00:12:33.920> cool 00:12:34.329 --> 00:12:34.339 align:start position:0% something cool 00:12:34.339 --> 00:12:35.710 align:start position:0% something cool if<00:12:34.399> you<00:12:34.610> can't<00:12:34.819> capture<00:12:35.060> their<00:12:35.300> attention<00:12:35.389> and 00:12:35.710 --> 00:12:35.720 align:start position:0% if you can't capture their attention and 00:12:35.720 --> 00:12:37.180 align:start position:0% if you can't capture their attention and make<00:12:35.839> it<00:12:35.959> really<00:12:36.199> easy<00:12:36.230> to<00:12:36.500> do<00:12:36.709> you're<00:12:37.100> gonna 00:12:37.180 --> 00:12:37.190 align:start position:0% make it really easy to do you're gonna 00:12:37.190 --> 00:12:38.829 align:start position:0% make it really easy to do you're gonna lose<00:12:37.399> them<00:12:37.579> and<00:12:37.790> this<00:12:38.029> is<00:12:38.149> something<00:12:38.329> that<00:12:38.480> a 00:12:38.829 --> 00:12:38.839 align:start position:0% lose them and this is something that a 00:12:38.839 --> 00:12:40.960 align:start position:0% lose them and this is something that a bigger<00:12:39.199> theme<00:12:39.529> around<00:12:39.740> building<00:12:40.519> products 00:12:40.960 --> 00:12:40.970 align:start position:0% bigger theme around building products 00:12:40.970 --> 00:12:42.850 align:start position:0% bigger theme around building products for<00:12:41.209> blockchain<00:12:41.720> we<00:12:42.110> need<00:12:42.260> to<00:12:42.319> approach<00:12:42.500> it<00:12:42.560> as 00:12:42.850 --> 00:12:42.860 align:start position:0% for blockchain we need to approach it as 00:12:42.860 --> 00:12:45.189 align:start position:0% for blockchain we need to approach it as a<00:12:43.220> focus<00:12:43.699> of<00:12:43.880> hey<00:12:44.360> we<00:12:44.510> need<00:12:44.660> to<00:12:44.750> build<00:12:44.870> we<00:12:45.079> need 00:12:45.189 --> 00:12:45.199 align:start position:0% a focus of hey we need to build we need 00:12:45.199 --> 00:12:46.750 align:start position:0% a focus of hey we need to build we need to<00:12:45.319> treat<00:12:45.500> this<00:12:45.649> as<00:12:45.829> this<00:12:46.250> is<00:12:46.310> something<00:12:46.670> we 00:12:46.750 --> 00:12:46.760 align:start position:0% to treat this as this is something we 00:12:46.760 --> 00:12:48.579 align:start position:0% to treat this as this is something we need<00:12:46.880> to<00:12:46.910> really<00:12:47.000> engage<00:12:47.630> people<00:12:47.660> on<00:12:48.079> and<00:12:48.290> it's 00:12:48.579 --> 00:12:48.589 align:start position:0% need to really engage people on and it's 00:12:48.589 --> 00:12:49.809 align:start position:0% need to really engage people on and it's not<00:12:48.680> something<00:12:49.040> that<00:12:49.130> deal<00:12:49.370> we<00:12:49.550> should<00:12:49.699> just 00:12:49.809 --> 00:12:49.819 align:start position:0% not something that deal we should just 00:12:49.819 --> 00:12:50.949 align:start position:0% not something that deal we should just take<00:12:49.970> for<00:12:50.120> granted<00:12:50.149> that<00:12:50.420> they're<00:12:50.870> gonna 00:12:50.949 --> 00:12:50.959 align:start position:0% take for granted that they're gonna 00:12:50.959 --> 00:12:52.139 align:start position:0% take for granted that they're gonna devote<00:12:51.230> their<00:12:51.350> whole<00:12:51.440> life<00:12:51.589> to<00:12:51.620> blockchain 00:12:52.139 --> 00:12:52.149 align:start position:0% devote their whole life to blockchain 00:12:52.149 --> 00:12:55.420 align:start position:0% devote their whole life to blockchain the<00:12:53.149> last<00:12:53.329> thing<00:12:53.540> is<00:12:53.920> testing<00:12:54.920> your<00:12:54.980> API<00:12:55.189> and 00:12:55.420 --> 00:12:55.430 align:start position:0% the last thing is testing your API and 00:12:55.430 --> 00:12:56.920 align:start position:0% the last thing is testing your API and this<00:12:55.519> we<00:12:55.730> this<00:12:56.000> again<00:12:56.329> all<00:12:56.569> these<00:12:56.870> things 00:12:56.920 --> 00:12:56.930 align:start position:0% this we this again all these things 00:12:56.930 --> 00:12:58.540 align:start position:0% this we this again all these things sounds<00:12:57.380> super<00:12:57.620> obvious<00:12:57.769> but<00:12:58.069> when<00:12:58.279> you<00:12:58.399> go<00:12:58.490> to 00:12:58.540 --> 00:12:58.550 align:start position:0% sounds super obvious but when you go to 00:12:58.550 --> 00:13:00.280 align:start position:0% sounds super obvious but when you go to build<00:12:58.760> an<00:12:58.880> API<00:12:58.970> people<00:12:59.720> understand<00:13:00.110> that<00:13:00.199> this 00:13:00.280 --> 00:13:00.290 align:start position:0% build an API people understand that this 00:13:00.290 --> 00:13:03.370 align:start position:0% build an API people understand that this is<00:13:00.350> really<00:13:00.649> important<00:13:01.010> so<00:13:01.399> basically<00:13:02.199> what<00:13:03.199> we 00:13:03.370 --> 00:13:03.380 align:start position:0% is really important so basically what we 00:13:03.380 --> 00:13:05.019 align:start position:0% is really important so basically what we found<00:13:03.589> is<00:13:03.889> there<00:13:04.040> a<00:13:04.069> lot<00:13:04.399> of<00:13:04.430> edge<00:13:04.699> cases 00:13:05.019 --> 00:13:05.029 align:start position:0% found is there a lot of edge cases 00:13:05.029 --> 00:13:06.939 align:start position:0% found is there a lot of edge cases especially<00:13:05.449> with<00:13:05.720> smart<00:13:05.899> contracts<00:13:06.260> and 00:13:06.939 --> 00:13:06.949 align:start position:0% especially with smart contracts and 00:13:06.949 --> 00:13:08.860 align:start position:0% especially with smart contracts and people<00:13:07.189> querying<00:13:07.490> stuff<00:13:07.760> so<00:13:07.970> having<00:13:08.449> a<00:13:08.569> tight 00:13:08.860 --> 00:13:08.870 align:start position:0% people querying stuff so having a tight 00:13:08.870 --> 00:13:10.179 align:start position:0% people querying stuff so having a tight feedback<00:13:09.110> loop<00:13:09.290> and<00:13:09.560> testing<00:13:09.889> a<00:13:09.949> bunch<00:13:10.040> of 00:13:10.179 --> 00:13:10.189 align:start position:0% feedback loop and testing a bunch of 00:13:10.189 --> 00:13:11.800 align:start position:0% feedback loop and testing a bunch of stuff<00:13:10.370> before<00:13:10.550> we've<00:13:11.180> done<00:13:11.329> this<00:13:11.480> good<00:13:11.689> and 00:13:11.800 --> 00:13:11.810 align:start position:0% stuff before we've done this good and 00:13:11.810 --> 00:13:13.329 align:start position:0% stuff before we've done this good and we've<00:13:11.930> done<00:13:12.079> this<00:13:12.199> bad<00:13:12.350> like<00:13:12.560> sometimes<00:13:12.920> you 00:13:13.329 --> 00:13:13.339 align:start position:0% we've done this bad like sometimes you 00:13:13.339 --> 00:13:14.980 align:start position:0% we've done this bad like sometimes you know<00:13:13.459> there's<00:13:14.060> been<00:13:14.209> a<00:13:14.240> couple<00:13:14.420> times<00:13:14.569> where 00:13:14.980 --> 00:13:14.990 align:start position:0% know there's been a couple times where 00:13:14.990 --> 00:13:16.269 align:start position:0% know there's been a couple times where we<00:13:15.170> launch<00:13:15.410> things<00:13:15.560> we<00:13:15.769> thought<00:13:15.920> we<00:13:16.040> had<00:13:16.160> good 00:13:16.269 --> 00:13:16.279 align:start position:0% we launch things we thought we had good 00:13:16.279 --> 00:13:18.069 align:start position:0% we launch things we thought we had good coverage<00:13:16.459> and<00:13:16.819> people<00:13:16.970> would<00:13:17.060> have<00:13:17.209> like<00:13:17.449> a 00:13:18.069 --> 00:13:18.079 align:start position:0% coverage and people would have like a 00:13:18.079 --> 00:13:20.350 align:start position:0% coverage and people would have like a really<00:13:18.589> crazy<00:13:18.920> educate<00:13:19.370> so<00:13:19.579> I<00:13:19.759> think<00:13:19.970> this<00:13:20.209> is 00:13:20.350 --> 00:13:20.360 align:start position:0% really crazy educate so I think this is 00:13:20.360 --> 00:13:22.300 align:start position:0% really crazy educate so I think this is this<00:13:20.660> is<00:13:20.720> really<00:13:20.990> really<00:13:21.170> important<00:13:21.560> the 00:13:22.300 --> 00:13:22.310 align:start position:0% this is really really important the 00:13:22.310 --> 00:13:24.730 align:start position:0% this is really really important the other<00:13:22.459> thing<00:13:22.639> is<00:13:22.910> we<00:13:23.449> found<00:13:23.480> oh<00:13:23.959> my<00:13:24.319> gosh 00:13:24.730 --> 00:13:24.740 align:start position:0% other thing is we found oh my gosh 00:13:24.740 --> 00:13:25.930 align:start position:0% other thing is we found oh my gosh creating<00:13:25.250> good<00:13:25.279> documents 00:13:25.930 --> 00:13:25.940 align:start position:0% creating good documents 00:13:25.940 --> 00:13:27.190 align:start position:0% creating good documents this<00:13:26.210> is<00:13:26.300> probably<00:13:26.480> the<00:13:26.630> highest<00:13:26.780> leverage 00:13:27.190 --> 00:13:27.200 align:start position:0% this is probably the highest leverage 00:13:27.200 --> 00:13:29.350 align:start position:0% this is probably the highest leverage you<00:13:27.470> can<00:13:27.650> have<00:13:27.830> on<00:13:28.100> your<00:13:28.250> own<00:13:28.280> time<00:13:28.670> because 00:13:29.350 --> 00:13:29.360 align:start position:0% you can have on your own time because 00:13:29.360 --> 00:13:30.580 align:start position:0% you can have on your own time because what<00:13:29.660> happens<00:13:29.960> if<00:13:30.020> you<00:13:30.110> don't<00:13:30.290> create<00:13:30.410> good 00:13:30.580 --> 00:13:30.590 align:start position:0% what happens if you don't create good 00:13:30.590 --> 00:13:31.990 align:start position:0% what happens if you don't create good documentation<00:13:30.920> people<00:13:31.310> ping<00:13:31.460> you<00:13:31.550> all<00:13:31.760> the 00:13:31.990 --> 00:13:32.000 align:start position:0% documentation people ping you all the 00:13:32.000 --> 00:13:33.940 align:start position:0% documentation people ping you all the time<00:13:32.180> of<00:13:32.330> questions<00:13:32.660> and<00:13:32.900> super<00:13:33.440> super<00:13:33.590> super 00:13:33.940 --> 00:13:33.950 align:start position:0% time of questions and super super super 00:13:33.950 --> 00:13:35.920 align:start position:0% time of questions and super super super important<00:13:34.340> not<00:13:35.090> only<00:13:35.120> for<00:13:35.540> the<00:13:35.630> developer 00:13:35.920 --> 00:13:35.930 align:start position:0% important not only for the developer 00:13:35.930 --> 00:13:37.090 align:start position:0% important not only for the developer experience<00:13:36.290> but<00:13:36.440> also<00:13:36.560> to<00:13:36.710> save<00:13:36.920> your<00:13:37.070> own 00:13:37.090 --> 00:13:37.100 align:start position:0% experience but also to save your own 00:13:37.100 --> 00:13:39.790 align:start position:0% experience but also to save your own time<00:13:37.510> and<00:13:38.510> then<00:13:38.660> the<00:13:38.750> last<00:13:38.870> thing<00:13:39.080> is<00:13:39.380> our 00:13:39.790 --> 00:13:39.800 align:start position:0% time and then the last thing is our 00:13:39.800 --> 00:13:41.440 align:start position:0% time and then the last thing is our second<00:13:40.250> glossing<00:13:40.580> is<00:13:40.760> getting<00:13:41.060> feedback<00:13:41.210> in 00:13:41.440 --> 00:13:41.450 align:start position:0% second glossing is getting feedback in 00:13:41.450 --> 00:13:42.520 align:start position:0% second glossing is getting feedback in the<00:13:41.510> iterating<00:13:41.810> when<00:13:41.990> you<00:13:42.080> ship<00:13:42.320> something 00:13:42.520 --> 00:13:42.530 align:start position:0% the iterating when you ship something 00:13:42.530 --> 00:13:44.140 align:start position:0% the iterating when you ship something it's<00:13:42.770> not<00:13:42.890> done<00:13:43.190> it's<00:13:43.700> like<00:13:43.760> you<00:13:43.940> got<00:13:44.060> to 00:13:44.140 --> 00:13:44.150 align:start position:0% it's not done it's like you got to 00:13:44.150 --> 00:13:45.820 align:start position:0% it's not done it's like you got to continually<00:13:44.750> continually<00:13:45.320> iterate<00:13:45.680> on<00:13:45.710> that 00:13:45.820 --> 00:13:45.830 align:start position:0% continually continually iterate on that 00:13:45.830 --> 00:13:47.620 align:start position:0% continually continually iterate on that and<00:13:46.160> make<00:13:46.700> it<00:13:46.820> better<00:13:46.910> and<00:13:47.120> better<00:13:47.270> and<00:13:47.510> this 00:13:47.620 --> 00:13:47.630 align:start position:0% and make it better and better and this 00:13:47.630 --> 00:13:48.940 align:start position:0% and make it better and better and this is<00:13:47.690> really<00:13:47.960> what<00:13:48.170> separates<00:13:48.530> the<00:13:48.740> good 00:13:48.940 --> 00:13:48.950 align:start position:0% is really what separates the good 00:13:48.950 --> 00:13:51.070 align:start position:0% is really what separates the good products<00:13:49.700> from<00:13:49.820> the<00:13:49.940> great<00:13:50.120> products<00:13:50.540> right 00:13:51.070 --> 00:13:51.080 align:start position:0% products from the great products right 00:13:51.080 --> 00:13:53.260 align:start position:0% products from the great products right and<00:13:51.350> the<00:13:52.160> last<00:13:52.400> thing<00:13:52.670> I<00:13:52.820> think<00:13:52.880> to<00:13:53.150> think 00:13:53.260 --> 00:13:53.270 align:start position:0% and the last thing I think to think 00:13:53.270 --> 00:13:55.450 align:start position:0% and the last thing I think to think about<00:13:53.540> is<00:13:53.720> really<00:13:54.530> think<00:13:54.770> about<00:13:54.830> solving<00:13:55.190> the 00:13:55.450 --> 00:13:55.460 align:start position:0% about is really think about solving the 00:13:55.460 --> 00:13:57.430 align:start position:0% about is really think about solving the users<00:13:55.730> problem<00:13:56.210> it's<00:13:56.420> not<00:13:56.630> just<00:13:56.900> oh<00:13:57.050> we<00:13:57.260> built 00:13:57.430 --> 00:13:57.440 align:start position:0% users problem it's not just oh we built 00:13:57.440 --> 00:13:59.650 align:start position:0% users problem it's not just oh we built this<00:13:57.530> API<00:13:57.830> we're<00:13:58.040> done<00:13:58.220> it's<00:13:58.460> like<00:13:58.550> you<00:13:59.510> need 00:13:59.650 --> 00:13:59.660 align:start position:0% this API we're done it's like you need 00:13:59.660 --> 00:14:02.500 align:start position:0% this API we're done it's like you need to<00:13:59.690> like<00:13:59.930> like<00:14:00.440> literally<00:14:01.070> have<00:14:01.940> the<00:14:02.270> whole 00:14:02.500 --> 00:14:02.510 align:start position:0% to like like literally have the whole 00:14:02.510 --> 00:14:04.240 align:start position:0% to like like literally have the whole experience<00:14:03.140> covered<00:14:03.680> right<00:14:03.800> you<00:14:03.980> need<00:14:04.100> to 00:14:04.240 --> 00:14:04.250 align:start position:0% experience covered right you need to 00:14:04.250 --> 00:14:05.890 align:start position:0% experience covered right you need to like<00:14:04.370> the<00:14:04.790> best<00:14:05.030> experience<00:14:05.270> is<00:14:05.570> like<00:14:05.690> oh<00:14:05.840> you 00:14:05.890 --> 00:14:05.900 align:start position:0% like the best experience is like oh you 00:14:05.900 --> 00:14:07.300 align:start position:0% like the best experience is like oh you know<00:14:06.080> I<00:14:06.110> don't<00:14:06.260> have<00:14:06.350> spin<00:14:06.530> up<00:14:06.620> a<00:14:06.710> node<00:14:06.920> I<00:14:07.130> just 00:14:07.300 --> 00:14:07.310 align:start position:0% know I don't have spin up a node I just 00:14:07.310 --> 00:14:09.310 align:start position:0% know I don't have spin up a node I just have<00:14:07.430> a<00:14:07.460> Web<00:14:07.640> API<00:14:07.940> and<00:14:08.360> then<00:14:08.690> it's<00:14:08.930> like<00:14:09.050> oh<00:14:09.200> you 00:14:09.310 --> 00:14:09.320 align:start position:0% have a Web API and then it's like oh you 00:14:09.320 --> 00:14:12.010 align:start position:0% have a Web API and then it's like oh you know<00:14:09.680> I<00:14:09.890> don't<00:14:10.310> need<00:14:10.520> to<00:14:10.700> even<00:14:11.150> like<00:14:11.570> write<00:14:11.870> my 00:14:12.010 --> 00:14:12.020 align:start position:0% know I don't need to even like write my 00:14:12.020 --> 00:14:14.170 align:start position:0% know I don't need to even like write my own<00:14:12.200> HTTP<00:14:12.920> wrappers<00:14:13.310> I<00:14:13.490> can<00:14:13.640> just<00:14:13.790> use<00:14:13.970> like<00:14:14.090> an 00:14:14.170 --> 00:14:14.180 align:start position:0% own HTTP wrappers I can just use like an 00:14:14.180 --> 00:14:16.060 align:start position:0% own HTTP wrappers I can just use like an SDK<00:14:14.630> a<00:14:14.660> JavaScript<00:14:15.230> down<00:14:15.560> to<00:14:15.710> like<00:14:15.860> oh<00:14:15.980> you 00:14:16.060 --> 00:14:16.070 align:start position:0% SDK a JavaScript down to like oh you 00:14:16.070 --> 00:14:17.770 align:start position:0% SDK a JavaScript down to like oh you know<00:14:16.310> the<00:14:16.580> app<00:14:16.700> just<00:14:16.970> calls<00:14:17.150> them<00:14:17.300> an<00:14:17.390> uber<00:14:17.480> to 00:14:17.770 --> 00:14:17.780 align:start position:0% know the app just calls them an uber to 00:14:17.780 --> 00:14:19.000 align:start position:0% know the app just calls them an uber to get<00:14:17.900> to<00:14:18.020> their<00:14:18.140> office<00:14:18.440> in<00:14:18.590> the<00:14:18.650> morning<00:14:18.890> like 00:14:19.000 --> 00:14:19.010 align:start position:0% get to their office in the morning like 00:14:19.010 --> 00:14:20.470 align:start position:0% get to their office in the morning like you<00:14:19.130> need<00:14:19.280> to<00:14:19.310> make<00:14:19.550> this<00:14:19.730> like<00:14:19.970> think<00:14:20.390> about 00:14:20.470 --> 00:14:20.480 align:start position:0% you need to make this like think about 00:14:20.480 --> 00:14:22.330 align:start position:0% you need to make this like think about it<00:14:20.720> end-to-end<00:14:21.080> and<00:14:21.500> this<00:14:21.860> is<00:14:22.010> what<00:14:22.130> really 00:14:22.330 --> 00:14:22.340 align:start position:0% it end-to-end and this is what really 00:14:22.340 --> 00:14:25.420 align:start position:0% it end-to-end and this is what really makes<00:14:22.460> a<00:14:22.730> great<00:14:23.060> user<00:14:23.540> experience<00:14:24.020> so<00:14:24.440> in 00:14:25.420 --> 00:14:25.430 align:start position:0% makes a great user experience so in 00:14:25.430 --> 00:14:28.900 align:start position:0% makes a great user experience so in conclusion<00:14:25.640> you<00:14:26.150> know<00:14:26.710> it<00:14:27.710> is<00:14:27.950> maybe<00:14:28.640> not<00:14:28.820> the 00:14:28.900 --> 00:14:28.910 align:start position:0% conclusion you know it is maybe not the 00:14:28.910 --> 00:14:30.550 align:start position:0% conclusion you know it is maybe not the key<00:14:29.090> to<00:14:29.210> life<00:14:29.360> but<00:14:29.750> it's<00:14:29.930> but<00:14:30.260> it<00:14:30.410> is 00:14:30.550 --> 00:14:30.560 align:start position:0% key to life but it's but it is 00:14:30.560 --> 00:14:32.520 align:start position:0% key to life but it's but it is definitely<00:14:31.130> the<00:14:31.160> key<00:14:31.430> to<00:14:31.760> creating 00:14:32.520 --> 00:14:32.530 align:start position:0% definitely the key to creating 00:14:32.530 --> 00:14:34.570 align:start position:0% definitely the key to creating blockchain<00:14:33.560> applications<00:14:34.310> that<00:14:34.430> people 00:14:34.570 --> 00:14:34.580 align:start position:0% blockchain applications that people 00:14:34.580 --> 00:14:37.120 align:start position:0% blockchain applications that people really<00:14:35.000> use<00:14:35.240> and<00:14:35.450> ultimately<00:14:35.870> like<00:14:36.770> pushing 00:14:37.120 --> 00:14:37.130 align:start position:0% really use and ultimately like pushing 00:14:37.130 --> 00:14:38.830 align:start position:0% really use and ultimately like pushing for<00:14:37.280> the<00:14:37.430> success<00:14:37.730> of<00:14:37.760> our<00:14:37.940> whole<00:14:38.030> industry<00:14:38.060> so 00:14:38.830 --> 00:14:38.840 align:start position:0% for the success of our whole industry so 00:14:38.840 --> 00:14:41.950 align:start position:0% for the success of our whole industry so I<00:14:38.870> think<00:14:39.070> we<00:14:40.070> see<00:14:40.310> this<00:14:40.490> on<00:14:40.730> every<00:14:41.540> single<00:14:41.570> this 00:14:41.950 --> 00:14:41.960 align:start position:0% I think we see this on every single this 00:14:41.960 --> 00:14:44.230 align:start position:0% I think we see this on every single this is<00:14:42.080> like<00:14:42.230> what<00:14:42.500> we<00:14:42.740> eat<00:14:43.160> sleep<00:14:43.490> breathe<00:14:43.940> and 00:14:44.230 --> 00:14:44.240 align:start position:0% is like what we eat sleep breathe and 00:14:44.240 --> 00:14:46.690 align:start position:0% is like what we eat sleep breathe and live<00:14:44.390> at<00:14:44.510> alchemy<00:14:44.870> so<00:14:45.080> it's<00:14:45.530> very<00:14:45.920> it<00:14:46.340> kind<00:14:46.610> of 00:14:46.690 --> 00:14:46.700 align:start position:0% live at alchemy so it's very it kind of 00:14:46.700 --> 00:14:48.430 align:start position:0% live at alchemy so it's very it kind of ingrained<00:14:47.090> in<00:14:47.210> us<00:14:47.330> but<00:14:47.420> I<00:14:47.510> want<00:14:47.840> to<00:14:48.050> emphasize 00:14:48.430 --> 00:14:48.440 align:start position:0% ingrained in us but I want to emphasize 00:14:48.440 --> 00:14:50.020 align:start position:0% ingrained in us but I want to emphasize how<00:14:48.710> important<00:14:49.100> it<00:14:49.190> is<00:14:49.250> for<00:14:49.460> those<00:14:49.760> you<00:14:49.910> guys 00:14:50.020 --> 00:14:50.030 align:start position:0% how important it is for those you guys 00:14:50.030 --> 00:14:51.460 align:start position:0% how important it is for those you guys who<00:14:50.120> are<00:14:50.180> building<00:14:50.330> developer<00:14:50.750> products<00:14:51.050> put 00:14:51.460 --> 00:14:51.470 align:start position:0% who are building developer products put 00:14:51.470 --> 00:14:52.780 align:start position:0% who are building developer products put a<00:14:51.500> lot<00:14:51.680> of<00:14:51.800> thought<00:14:51.950> and<00:14:52.070> care<00:14:52.280> and<00:14:52.460> you'll<00:14:52.580> get 00:14:52.780 --> 00:14:52.790 align:start position:0% a lot of thought and care and you'll get 00:14:52.790 --> 00:14:55.330 align:start position:0% a lot of thought and care and you'll get many<00:14:53.270> many<00:14:53.480> many<00:14:53.720> times<00:14:53.810> over<00:14:54.140> reward<00:14:55.130> in<00:14:55.220> the 00:14:55.330 --> 00:14:55.340 align:start position:0% many many many times over reward in the 00:14:55.340 --> 00:14:58.420 align:start position:0% many many many times over reward in the dividends<00:14:55.760> so<00:14:56.200> thanks<00:14:57.200> if<00:14:57.350> I'll<00:14:58.070> be<00:14:58.160> around 00:14:58.420 --> 00:14:58.430 align:start position:0% dividends so thanks if I'll be around 00:14:58.430 --> 00:15:01.510 align:start position:0% dividends so thanks if I'll be around Zebedee<00:14:58.850> have<00:14:58.970> any<00:14:59.090> quick<00:14:59.390> questions<00:15:00.520> great 00:15:01.510 --> 00:15:01.520 align:start position:0% Zebedee have any quick questions great 00:15:01.520 --> 00:15:02.080 align:start position:0% Zebedee have any quick questions great talk 00:15:02.080 --> 00:15:02.090 align:start position:0% talk 00:15:02.090 --> 00:15:05.110 align:start position:0% talk thanks<00:15:02.570> happy<00:15:02.930> birthday<00:15:03.260> yeah<00:15:03.790> yeah<00:15:04.790> I<00:15:04.820> have<00:15:05.060> a 00:15:05.110 --> 00:15:05.120 align:start position:0% thanks happy birthday yeah yeah I have a 00:15:05.120 --> 00:15:08.920 align:start position:0% thanks happy birthday yeah yeah I have a question<00:15:05.620> you<00:15:06.620> said<00:15:06.890> that<00:15:07.130> you<00:15:07.310> use<00:15:08.090> the<00:15:08.510> owner 00:15:08.920 --> 00:15:08.930 align:start position:0% question you said that you use the owner 00:15:08.930 --> 00:15:10.990 align:start position:0% question you said that you use the owner instead<00:15:09.560> of<00:15:09.680> tech<00:15:09.860> G<00:15:10.100> and<00:15:10.370> there<00:15:10.790> is<00:15:10.850> some 00:15:10.990 --> 00:15:11.000 align:start position:0% instead of tech G and there is some 00:15:11.000 --> 00:15:14.080 align:start position:0% instead of tech G and there is some logic<00:15:11.120> that<00:15:11.360> you<00:15:11.570> had<00:15:12.080> to<00:15:12.290> add<00:15:12.440> do<00:15:13.250> you<00:15:13.460> process 00:15:14.080 --> 00:15:14.090 align:start position:0% logic that you had to add do you process 00:15:14.090 --> 00:15:16.930 align:start position:0% logic that you had to add do you process that<00:15:14.300> but<00:15:14.690> your<00:15:15.200> team<00:15:15.440> who<00:15:16.010> builds<00:15:16.370> the<00:15:16.400> logic 00:15:16.930 --> 00:15:16.940 align:start position:0% that but your team who builds the logic 00:15:16.940 --> 00:15:19.600 align:start position:0% that but your team who builds the logic with<00:15:17.060> the<00:15:17.150> transformation<00:15:17.960> like<00:15:18.860> something 00:15:19.600 --> 00:15:19.610 align:start position:0% with the transformation like something 00:15:19.610 --> 00:15:21.490 align:start position:0% with the transformation like something like<00:15:19.790> D<00:15:20.030> graph<00:15:20.270> protocol<00:15:20.840> something<00:15:21.410> like 00:15:21.490 --> 00:15:21.500 align:start position:0% like D graph protocol something like 00:15:21.500 --> 00:15:22.450 align:start position:0% like D graph protocol something like that<00:15:21.680> yeah 00:15:22.450 --> 00:15:22.460 align:start position:0% that yeah 00:15:22.460 --> 00:15:23.740 align:start position:0% that yeah that<00:15:22.640> that's<00:15:22.940> a<00:15:23.000> great<00:15:23.090> question<00:15:23.180> so<00:15:23.660> the 00:15:23.740 --> 00:15:23.750 align:start position:0% that that's a great question so the 00:15:23.750 --> 00:15:25.420 align:start position:0% that that's a great question so the question<00:15:24.050> was<00:15:24.170> you<00:15:24.500> know<00:15:24.740> when<00:15:25.070> we<00:15:25.160> go<00:15:25.250> back<00:15:25.400> to 00:15:25.420 --> 00:15:25.430 align:start position:0% question was you know when we go back to 00:15:25.430 --> 00:15:29.740 align:start position:0% question was you know when we go back to this<00:15:25.640> slide<00:15:27.220> this<00:15:28.220> one<00:15:28.430> right<00:15:28.880> so<00:15:29.120> like<00:15:29.270> it's 00:15:29.740 --> 00:15:29.750 align:start position:0% this slide this one right so like it's 00:15:29.750 --> 00:15:30.970 align:start position:0% this slide this one right so like it's slightly<00:15:30.080> different<00:15:30.410> than<00:15:30.620> the<00:15:30.740> smart 00:15:30.970 --> 00:15:30.980 align:start position:0% slightly different than the smart 00:15:30.980 --> 00:15:33.190 align:start position:0% slightly different than the smart contract<00:15:31.130> and<00:15:31.640> where<00:15:31.880> does<00:15:32.090> that<00:15:32.150> data<00:15:32.930> get 00:15:33.190 --> 00:15:33.200 align:start position:0% contract and where does that data get 00:15:33.200 --> 00:15:35.530 align:start position:0% contract and where does that data get processed<00:15:33.740> and<00:15:34.460> is<00:15:34.730> that<00:15:34.910> on<00:15:35.030> our<00:15:35.150> side<00:15:35.360> is 00:15:35.530 --> 00:15:35.540 align:start position:0% processed and is that on our side is 00:15:35.540 --> 00:15:37.630 align:start position:0% processed and is that on our side is that<00:15:35.690> on<00:15:35.780> the<00:15:35.870> user<00:15:36.020> side<00:15:36.140> so<00:15:36.800> there's<00:15:37.430> kind<00:15:37.610> of 00:15:37.630 --> 00:15:37.640 align:start position:0% that on the user side so there's kind of 00:15:37.640 --> 00:15:39.670 align:start position:0% that on the user side so there's kind of two<00:15:37.700> ways<00:15:38.090> to<00:15:38.390> handle<00:15:38.540> this<00:15:38.780> like 00:15:39.670 --> 00:15:39.680 align:start position:0% two ways to handle this like 00:15:39.680 --> 00:15:42.400 align:start position:0% two ways to handle this like one<00:15:39.889> is<00:15:40.189> we<00:15:40.759> actually<00:15:40.939> we<00:15:41.389> actually<00:15:41.689> provide<00:15:42.379> a 00:15:42.400 --> 00:15:42.410 align:start position:0% one is we actually we actually provide a 00:15:42.410 --> 00:15:43.689 align:start position:0% one is we actually we actually provide a bunch<00:15:42.769> of<00:15:42.829> different<00:15:43.069> transformations<00:15:43.610> of 00:15:43.689 --> 00:15:43.699 align:start position:0% bunch of different transformations of 00:15:43.699 --> 00:15:45.309 align:start position:0% bunch of different transformations of the<00:15:43.759> data<00:15:43.939> so<00:15:44.149> users<00:15:44.449> can<00:15:44.629> access<00:15:44.779> in<00:15:45.019> any<00:15:45.110> way 00:15:45.309 --> 00:15:45.319 align:start position:0% the data so users can access in any way 00:15:45.319 --> 00:15:47.859 align:start position:0% the data so users can access in any way and<00:15:46.040> then<00:15:46.189> there's<00:15:46.369> also<00:15:46.600> there's<00:15:47.600> we<00:15:47.839> have 00:15:47.859 --> 00:15:47.869 align:start position:0% and then there's also there's we have 00:15:47.869 --> 00:15:49.179 align:start position:0% and then there's also there's we have plans<00:15:48.230> for<00:15:48.319> like<00:15:48.470> a<00:15:48.529> decentralized<00:15:49.100> system 00:15:49.179 --> 00:15:49.189 align:start position:0% plans for like a decentralized system 00:15:49.189 --> 00:15:51.460 align:start position:0% plans for like a decentralized system but<00:15:49.610> what<00:15:49.999> we<00:15:50.119> found<00:15:50.300> is<00:15:50.660> most<00:15:51.019> of<00:15:51.230> the<00:15:51.290> time 00:15:51.460 --> 00:15:51.470 align:start position:0% but what we found is most of the time 00:15:51.470 --> 00:15:52.900 align:start position:0% but what we found is most of the time people<00:15:51.740> just<00:15:51.980> want<00:15:52.129> the<00:15:52.220> centralized<00:15:52.610> version 00:15:52.900 --> 00:15:52.910 align:start position:0% people just want the centralized version 00:15:52.910 --> 00:15:54.100 align:start position:0% people just want the centralized version first<00:15:53.180> and<00:15:53.449> then<00:15:53.749> you<00:15:53.839> can<00:15:53.959> make<00:15:54.079> it 00:15:54.100 --> 00:15:54.110 align:start position:0% first and then you can make it 00:15:54.110 --> 00:15:55.989 align:start position:0% first and then you can make it decentralized<00:15:54.740> so<00:15:55.129> that<00:15:55.369> can<00:15:55.699> answer<00:15:55.879> your 00:15:55.989 --> 00:15:55.999 align:start position:0% decentralized so that can answer your 00:15:55.999 --> 00:16:03.280 align:start position:0% decentralized so that can answer your question<00:15:56.379> kind<00:15:57.379> of<00:16:01.029> in<00:16:02.029> cheats<00:16:02.480> in<00:16:02.809> some<00:16:03.199> of 00:16:03.280 --> 00:16:03.290 align:start position:0% question kind of in cheats in some of 00:16:03.290 --> 00:16:04.840 align:start position:0% question kind of in cheats in some of the<00:16:03.350> things<00:16:03.529> we<00:16:03.649> do<00:16:03.800> yes<00:16:04.069> and<00:16:04.339> cheese<00:16:04.639> was 00:16:04.840 --> 00:16:04.850 align:start position:0% the things we do yes and cheese was 00:16:04.850 --> 00:16:06.730 align:start position:0% the things we do yes and cheese was particularly<00:16:05.660> know<00:16:05.929> there's<00:16:06.199> like<00:16:06.350> standard 00:16:06.730 --> 00:16:06.740 align:start position:0% particularly know there's like standard 00:16:06.740 --> 00:16:08.199 align:start position:0% particularly know there's like standard API<00:16:06.980> and<00:16:07.369> the<00:16:07.459> reason<00:16:07.730> for<00:16:07.759> that<00:16:07.910> is<00:16:08.089> we 00:16:08.199 --> 00:16:08.209 align:start position:0% API and the reason for that is we 00:16:08.209 --> 00:16:10.329 align:start position:0% API and the reason for that is we basically<00:16:08.749> thought<00:16:09.259> through<00:16:09.649> every<00:16:10.129> single 00:16:10.329 --> 00:16:10.339 align:start position:0% basically thought through every single 00:16:10.339 --> 00:16:12.040 align:start position:0% basically thought through every single kind<00:16:11.059> of<00:16:11.119> use<00:16:11.300> case<00:16:11.509> that<00:16:11.720> people<00:16:11.839> would<00:16:12.019> want 00:16:12.040 --> 00:16:12.050 align:start position:0% kind of use case that people would want 00:16:12.050 --> 00:16:13.989 align:start position:0% kind of use case that people would want and<00:16:12.649> we<00:16:12.740> provide<00:16:13.069> like<00:16:13.309> parameters<00:16:13.790> so<00:16:13.970> you 00:16:13.989 --> 00:16:13.999 align:start position:0% and we provide like parameters so you 00:16:13.999 --> 00:16:16.359 align:start position:0% and we provide like parameters so you can<00:16:14.179> say<00:16:14.389> for<00:16:14.899> the<00:16:14.990> API<00:16:15.230> calls<00:16:15.559> you<00:16:16.009> can<00:16:16.129> say 00:16:16.359 --> 00:16:16.369 align:start position:0% can say for the API calls you can say 00:16:16.369 --> 00:16:18.999 align:start position:0% can say for the API calls you can say query<00:16:16.759> wizards<00:16:17.269> based<00:16:17.569> on<00:16:17.809> fire<00:16:18.379> type<00:16:18.740> based 00:16:18.999 --> 00:16:19.009 align:start position:0% query wizards based on fire type based 00:16:19.009 --> 00:16:21.460 align:start position:0% query wizards based on fire type based on<00:16:19.160> wind<00:16:19.429> type<00:16:19.699> or<00:16:19.910> based<00:16:20.480> on<00:16:20.660> owner<00:16:20.959> or<00:16:21.290> based 00:16:21.460 --> 00:16:21.470 align:start position:0% on wind type or based on owner or based 00:16:21.470 --> 00:16:23.230 align:start position:0% on wind type or based on owner or based on<00:16:21.649> duels<00:16:21.920> so<00:16:22.309> we<00:16:22.670> basically<00:16:22.879> think<00:16:23.059> of 00:16:23.230 --> 00:16:23.240 align:start position:0% on duels so we basically think of 00:16:23.240 --> 00:16:24.579 align:start position:0% on duels so we basically think of everything<00:16:23.629> you<00:16:23.720> need<00:16:23.839> and<00:16:23.990> build<00:16:24.110> a<00:16:24.230> flexible 00:16:24.579 --> 00:16:24.589 align:start position:0% everything you need and build a flexible 00:16:24.589 --> 00:16:28.989 align:start position:0% everything you need and build a flexible system<00:16:24.769> so<00:16:25.869> yeah<00:16:26.869> question<00:16:27.249> great<00:16:28.249> doc<00:16:28.429> Thanks 00:16:28.989 --> 00:16:28.999 align:start position:0% system so yeah question great doc Thanks 00:16:28.999 --> 00:16:31.809 align:start position:0% system so yeah question great doc Thanks so<00:16:29.029> I<00:16:29.449> I<00:16:29.720> saw<00:16:30.290> that<00:16:30.439> your<00:16:30.619> API<00:16:30.889> queries<00:16:31.610> a<00:16:31.699> lot 00:16:31.809 --> 00:16:31.819 align:start position:0% so I I saw that your API queries a lot 00:16:31.819 --> 00:16:33.579 align:start position:0% so I I saw that your API queries a lot of<00:16:31.939> data<00:16:32.119> yeah<00:16:32.600> but<00:16:32.839> do<00:16:32.929> you<00:16:32.959> also<00:16:33.259> post 00:16:33.579 --> 00:16:33.589 align:start position:0% of data yeah but do you also post 00:16:33.589 --> 00:16:35.350 align:start position:0% of data yeah but do you also post transactions<00:16:34.309> to<00:16:34.429> the<00:16:34.579> to<00:16:35.059> the<00:16:35.149> blockchain 00:16:35.350 --> 00:16:35.360 align:start position:0% transactions to the to the blockchain 00:16:35.360 --> 00:16:37.569 align:start position:0% transactions to the to the blockchain would<00:16:35.869> you<00:16:35.959> okay<00:16:36.259> yes<00:16:36.559> yes<00:16:37.040> and<00:16:37.279> do<00:16:37.399> you<00:16:37.459> use 00:16:37.569 --> 00:16:37.579 align:start position:0% would you okay yes yes and do you use 00:16:37.579 --> 00:16:39.359 align:start position:0% would you okay yes yes and do you use meta<00:16:37.790> transactions<00:16:38.389> or<00:16:38.509> how<00:16:38.660> do<00:16:38.720> you<00:16:38.749> do<00:16:38.869> it 00:16:39.359 --> 00:16:39.369 align:start position:0% meta transactions or how do you do it 00:16:39.369 --> 00:16:41.230 align:start position:0% meta transactions or how do you do it what<00:16:40.369> do<00:16:40.459> you<00:16:40.490> mean<00:16:40.639> do<00:16:40.759> we<00:16:40.850> do<00:16:40.999> we<00:16:41.089> batch 00:16:41.230 --> 00:16:41.240 align:start position:0% what do you mean do we do we batch 00:16:41.240 --> 00:16:43.840 align:start position:0% what do you mean do we do we batch transactions<00:16:41.869> together<00:16:42.139> I<00:16:42.379> mean<00:16:42.670> as<00:16:43.670> a 00:16:43.840 --> 00:16:43.850 align:start position:0% transactions together I mean as a 00:16:43.850 --> 00:16:46.269 align:start position:0% transactions together I mean as a developer<00:16:44.360> I<00:16:44.600> sign<00:16:45.290> a<00:16:45.319> transaction<00:16:45.769> and<00:16:46.100> send 00:16:46.269 --> 00:16:46.279 align:start position:0% developer I sign a transaction and send 00:16:46.279 --> 00:16:48.549 align:start position:0% developer I sign a transaction and send it<00:16:46.339> through<00:16:46.670> your<00:16:46.879> API<00:16:47.120> or<00:16:47.480> others<00:16:47.749> work<00:16:47.959> yes 00:16:48.549 --> 00:16:48.559 align:start position:0% it through your API or others work yes 00:16:48.559 --> 00:16:50.710 align:start position:0% it through your API or others work yes so<00:16:48.920> we<00:16:49.399> don't<00:16:49.610> we<00:16:49.819> don't<00:16:49.939> hold<00:16:50.149> any<00:16:50.360> private 00:16:50.710 --> 00:16:50.720 align:start position:0% so we don't we don't hold any private 00:16:50.720 --> 00:16:53.350 align:start position:0% so we don't we don't hold any private keys<00:16:50.870> we<00:16:51.139> don't<00:16:51.350> so<00:16:51.980> the<00:16:52.100> question<00:16:52.399> was<00:16:52.610> how<00:16:53.300> do 00:16:53.350 --> 00:16:53.360 align:start position:0% keys we don't so the question was how do 00:16:53.360 --> 00:16:55.030 align:start position:0% keys we don't so the question was how do we<00:16:53.509> how<00:16:53.720> do<00:16:53.779> transactions<00:16:54.350> work<00:16:54.529> do<00:16:54.860> we<00:16:54.889> do 00:16:55.030 --> 00:16:55.040 align:start position:0% we how do transactions work do we do 00:16:55.040 --> 00:16:56.110 align:start position:0% we how do transactions work do we do transactions<00:16:55.639> and<00:16:55.790> how<00:16:55.850> do<00:16:55.910> we<00:16:56.029> do 00:16:56.110 --> 00:16:56.120 align:start position:0% transactions and how do we do 00:16:56.120 --> 00:16:58.030 align:start position:0% transactions and how do we do transactions<00:16:56.689> in<00:16:56.809> the<00:16:56.899> system<00:16:57.199> the<00:16:57.620> answer<00:16:57.829> is 00:16:58.030 --> 00:16:58.040 align:start position:0% transactions in the system the answer is 00:16:58.040 --> 00:16:59.949 align:start position:0% transactions in the system the answer is we<00:16:58.519> don't<00:16:58.639> hold<00:16:58.819> any<00:16:58.999> private<00:16:59.360> keys<00:16:59.509> you<00:16:59.749> kind 00:16:59.949 --> 00:16:59.959 align:start position:0% we don't hold any private keys you kind 00:16:59.959 --> 00:17:01.299 align:start position:0% we don't hold any private keys you kind of<00:16:59.990> like<00:17:00.199> the<00:17:00.559> way<00:17:00.649> to<00:17:00.709> think<00:17:00.920> about<00:17:01.069> is<00:17:01.189> you 00:17:01.299 --> 00:17:01.309 align:start position:0% of like the way to think about is you 00:17:01.309 --> 00:17:03.369 align:start position:0% of like the way to think about is you package<00:17:01.730> this<00:17:01.910> transaction<00:17:02.300> and<00:17:02.629> you<00:17:02.720> hand<00:17:03.290> it 00:17:03.369 --> 00:17:03.379 align:start position:0% package this transaction and you hand it 00:17:03.379 --> 00:17:05.019 align:start position:0% package this transaction and you hand it to<00:17:03.529> us<00:17:03.709> and<00:17:03.980> we're<00:17:04.459> just<00:17:04.579> kind<00:17:04.789> of<00:17:04.819> like<00:17:04.909> the 00:17:05.019 --> 00:17:05.029 align:start position:0% to us and we're just kind of like the 00:17:05.029 --> 00:17:06.519 align:start position:0% to us and we're just kind of like the pipe<00:17:05.270> to<00:17:05.480> the<00:17:05.569> blockchain<00:17:05.839> kind<00:17:06.230> of<00:17:06.289> like<00:17:06.380> your 00:17:06.519 --> 00:17:06.529 align:start position:0% pipe to the blockchain kind of like your 00:17:06.529 --> 00:17:07.689 align:start position:0% pipe to the blockchain kind of like your internet<00:17:06.799> provider<00:17:06.919> it<00:17:07.189> gives<00:17:07.339> you<00:17:07.399> internet 00:17:07.689 --> 00:17:07.699 align:start position:0% internet provider it gives you internet 00:17:07.699 --> 00:17:10.120 align:start position:0% internet provider it gives you internet we<00:17:08.149> give<00:17:08.360> you<00:17:08.539> access<00:17:08.809> to<00:17:09.020> the<00:17:09.169> watching<00:17:09.529> so<00:17:09.980> we 00:17:10.120 --> 00:17:10.130 align:start position:0% we give you access to the watching so we 00:17:10.130 --> 00:17:12.220 align:start position:0% we give you access to the watching so we put<00:17:10.459> it<00:17:10.549> in<00:17:10.610> this<00:17:11.390> little<00:17:11.569> tube<00:17:11.809> and<00:17:12.020> that 00:17:12.220 --> 00:17:12.230 align:start position:0% put it in this little tube and that 00:17:12.230 --> 00:17:16.840 align:start position:0% put it in this little tube and that comes<00:17:12.409> out<00:17:12.529> on<00:17:12.709> blockchain<00:17:15.100> yeah<00:17:16.100> so<00:17:16.730> like 00:17:16.840 --> 00:17:16.850 align:start position:0% comes out on blockchain yeah so like 00:17:16.850 --> 00:17:19.299 align:start position:0% comes out on blockchain yeah so like this<00:17:17.419> API<00:17:17.839> that<00:17:18.049> you<00:17:18.199> build<00:17:18.380> is<00:17:18.500> it<00:17:18.589> like<00:17:18.770> you 00:17:19.299 --> 00:17:19.309 align:start position:0% this API that you build is it like you 00:17:19.309 --> 00:17:20.590 align:start position:0% this API that you build is it like you build<00:17:19.490> a<00:17:19.520> custom<00:17:19.880> one<00:17:20.000> for<00:17:20.179> each<00:17:20.270> one<00:17:20.390> of<00:17:20.419> your 00:17:20.590 --> 00:17:20.600 align:start position:0% build a custom one for each one of your 00:17:20.600 --> 00:17:21.850 align:start position:0% build a custom one for each one of your clients<00:17:20.809> or<00:17:21.230> is<00:17:21.319> it<00:17:21.409> like<00:17:21.529> sort<00:17:21.740> of<00:17:21.770> an 00:17:21.850 --> 00:17:21.860 align:start position:0% clients or is it like sort of an 00:17:21.860 --> 00:17:24.370 align:start position:0% clients or is it like sort of an automated<00:17:22.220> product<00:17:22.699> where<00:17:22.909> I<00:17:23.199> give<00:17:24.199> you<00:17:24.260> my 00:17:24.370 --> 00:17:24.380 align:start position:0% automated product where I give you my 00:17:24.380 --> 00:17:25.720 align:start position:0% automated product where I give you my contracts<00:17:24.860> and<00:17:25.069> it<00:17:25.130> sort<00:17:25.279> of<00:17:25.309> generates<00:17:25.640> an 00:17:25.720 --> 00:17:25.730 align:start position:0% contracts and it sort of generates an 00:17:25.730 --> 00:17:27.970 align:start position:0% contracts and it sort of generates an API<00:17:25.970> how<00:17:26.419> does<00:17:26.569> it<00:17:26.659> work 00:17:27.970 --> 00:17:27.980 align:start position:0% API how does it work 00:17:27.980 --> 00:17:29.950 align:start position:0% API how does it work great<00:17:28.370> question<00:17:28.640> so<00:17:28.789> the<00:17:28.880> question<00:17:28.909> was<00:17:29.360> do<00:17:29.750> we 00:17:29.950 --> 00:17:29.960 align:start position:0% great question so the question was do we 00:17:29.960 --> 00:17:32.139 align:start position:0% great question so the question was do we build<00:17:30.740> one<00:17:30.980> a<00:17:31.010> custom<00:17:31.250> one<00:17:31.520> for<00:17:31.640> every<00:17:31.789> client 00:17:32.139 --> 00:17:32.149 align:start position:0% build one a custom one for every client 00:17:32.149 --> 00:17:33.789 align:start position:0% build one a custom one for every client or<00:17:32.240> do<00:17:32.539> we<00:17:32.690> is<00:17:32.899> it<00:17:33.020> kind<00:17:33.200> of<00:17:33.230> like<00:17:33.350> an<00:17:33.470> automated 00:17:33.789 --> 00:17:33.799 align:start position:0% or do we is it kind of like an automated 00:17:33.799 --> 00:17:34.180 align:start position:0% or do we is it kind of like an automated one 00:17:34.180 --> 00:17:34.190 align:start position:0% one 00:17:34.190 --> 00:17:37.360 align:start position:0% one so<00:17:34.909> typically<00:17:35.750> we<00:17:36.049> mostly<00:17:36.440> focus<00:17:36.890> on<00:17:37.100> a 00:17:37.360 --> 00:17:37.370 align:start position:0% so typically we mostly focus on a 00:17:37.370 --> 00:17:39.070 align:start position:0% so typically we mostly focus on a theorem<00:17:37.700> API<00:17:37.970> so<00:17:38.330> we<00:17:38.539> build<00:17:38.779> kind<00:17:38.929> of<00:17:38.990> a 00:17:39.070 --> 00:17:39.080 align:start position:0% theorem API so we build kind of a 00:17:39.080 --> 00:17:40.630 align:start position:0% theorem API so we build kind of a standard<00:17:39.380> API<00:17:39.500> and<00:17:39.799> enhance<00:17:40.130> so<00:17:40.279> we<00:17:40.370> support 00:17:40.630 --> 00:17:40.640 align:start position:0% standard API and enhance so we support 00:17:40.640 --> 00:17:42.700 align:start position:0% standard API and enhance so we support the<00:17:40.820> standard<00:17:41.240> JSON<00:17:41.419> RPC<00:17:41.690> API<00:17:42.200> for<00:17:42.320> theorem 00:17:42.700 --> 00:17:42.710 align:start position:0% the standard JSON RPC API for theorem 00:17:42.710 --> 00:17:44.529 align:start position:0% the standard JSON RPC API for theorem and<00:17:42.890> then<00:17:43.250> we<00:17:43.399> build<00:17:43.610> a<00:17:43.700> suite<00:17:43.970> of<00:17:44.149> etherium 00:17:44.529 --> 00:17:44.539 align:start position:0% and then we build a suite of etherium 00:17:44.539 --> 00:17:47.110 align:start position:0% and then we build a suite of etherium api's<00:17:44.899> this<00:17:45.890> is<00:17:46.010> actually<00:17:46.279> the<00:17:46.370> first<00:17:46.610> API 00:17:47.110 --> 00:17:47.120 align:start position:0% api's this is actually the first API 00:17:47.120 --> 00:17:48.610 align:start position:0% api's this is actually the first API that<00:17:47.330> we<00:17:47.419> built<00:17:47.659> for<00:17:47.870> kind<00:17:48.200> of<00:17:48.230> a<00:17:48.320> specific 00:17:48.610 --> 00:17:48.620 align:start position:0% that we built for kind of a specific 00:17:48.620 --> 00:17:51.549 align:start position:0% that we built for kind of a specific customer<00:17:49.179> and<00:17:50.179> typically<00:17:50.750> we<00:17:51.020> don't<00:17:51.169> do<00:17:51.409> these 00:17:51.549 --> 00:17:51.559 align:start position:0% customer and typically we don't do these 00:17:51.559 --> 00:17:53.030 align:start position:0% customer and typically we don't do these but 00:17:53.030 --> 00:17:53.040 align:start position:0% but 00:17:53.040 --> 00:17:54.860 align:start position:0% but short<00:17:53.190> answer<00:17:53.430> is<00:17:53.460> this<00:17:53.730> was<00:17:53.910> custom<00:17:54.120> but<00:17:54.750> we 00:17:54.860 --> 00:17:54.870 align:start position:0% short answer is this was custom but we 00:17:54.870 --> 00:17:56.570 align:start position:0% short answer is this was custom but we do<00:17:55.080> have<00:17:55.260> kind<00:17:55.560> of<00:17:55.650> way<00:17:55.800> to<00:17:55.830> do<00:17:56.040> automate<00:17:56.400> if<00:17:56.490> we 00:17:56.570 --> 00:17:56.580 align:start position:0% do have kind of way to do automate if we 00:17:56.580 --> 00:17:57.800 align:start position:0% do have kind of way to do automate if we wanted<00:17:56.910> to<00:17:57.000> but<00:17:57.150> it's<00:17:57.270> not<00:17:57.420> kind<00:17:57.600> of<00:17:57.630> like<00:17:57.780> a 00:17:57.800 --> 00:17:57.810 align:start position:0% wanted to but it's not kind of like a 00:17:57.810 --> 00:18:01.060 align:start position:0% wanted to but it's not kind of like a big<00:17:58.140> area<00:17:58.410> that<00:17:58.650> we're<00:17:58.770> focusing<00:17:58.800> on<00:17:59.300> okay<00:18:00.300> so 00:18:01.060 --> 00:18:01.070 align:start position:0% big area that we're focusing on okay so 00:18:01.070 --> 00:18:03.830 align:start position:0% big area that we're focusing on okay so second<00:18:02.070> question<00:18:02.100> it's<00:18:02.970> kind<00:18:03.270> of<00:18:03.330> it's<00:18:03.690> not 00:18:03.830 --> 00:18:03.840 align:start position:0% second question it's kind of it's not 00:18:03.840 --> 00:18:04.760 align:start position:0% second question it's kind of it's not like<00:18:03.990> a<00:18:04.020> lot<00:18:04.200> of<00:18:04.230> the<00:18:04.320> questions<00:18:04.680> I<00:18:04.740> just 00:18:04.760 --> 00:18:04.770 align:start position:0% like a lot of the questions I just 00:18:04.770 --> 00:18:07.310 align:start position:0% like a lot of the questions I just really<00:18:05.160> want<00:18:05.280> to<00:18:05.340> try<00:18:05.550> to<00:18:05.580> understand<00:18:06.090> so<00:18:06.320> like 00:18:07.310 --> 00:18:07.320 align:start position:0% really want to try to understand so like 00:18:07.320 --> 00:18:09.680 align:start position:0% really want to try to understand so like pretty<00:18:07.770> much<00:18:07.920> every<00:18:08.340> Deb<00:18:08.880> if<00:18:09.150> they<00:18:09.390> want<00:18:09.600> to 00:18:09.680 --> 00:18:09.690 align:start position:0% pretty much every Deb if they want to 00:18:09.690 --> 00:18:12.650 align:start position:0% pretty much every Deb if they want to have<00:18:09.900> like<00:18:10.080> good<00:18:10.950> usability<00:18:11.280> and<00:18:11.850> good<00:18:12.330> like 00:18:12.650 --> 00:18:12.660 align:start position:0% have like good usability and good like 00:18:12.660 --> 00:18:15.080 align:start position:0% have like good usability and good like um<00:18:12.870> like<00:18:13.290> fast<00:18:13.650> responses<00:18:14.220> what<00:18:14.700> you<00:18:14.820> do<00:18:14.910> is 00:18:15.080 --> 00:18:15.090 align:start position:0% um like fast responses what you do is 00:18:15.090 --> 00:18:17.870 align:start position:0% um like fast responses what you do is you<00:18:15.570> take<00:18:15.720> your<00:18:15.930> smart<00:18:16.140> contracts<00:18:16.650> you<00:18:17.160> just 00:18:17.870 --> 00:18:17.880 align:start position:0% you take your smart contracts you just 00:18:17.880 --> 00:18:20.090 align:start position:0% you take your smart contracts you just listen<00:18:18.300> for<00:18:18.420> your<00:18:18.570> own<00:18:18.660> events<00:18:19.080> you<00:18:19.770> save<00:18:19.950> them 00:18:20.090 --> 00:18:20.100 align:start position:0% listen for your own events you save them 00:18:20.100 --> 00:18:21.590 align:start position:0% listen for your own events you save them on<00:18:20.190> your<00:18:20.220> api's<00:18:20.610> and<00:18:20.970> then<00:18:21.060> you<00:18:21.210> mean<00:18:21.360> decks 00:18:21.590 --> 00:18:21.600 align:start position:0% on your api's and then you mean decks 00:18:21.600 --> 00:18:23.180 align:start position:0% on your api's and then you mean decks all<00:18:21.810> the<00:18:21.930> stuff<00:18:22.140> buy<00:18:22.350> whatever<00:18:22.530> you<00:18:22.800> want<00:18:22.980> then 00:18:23.180 --> 00:18:23.190 align:start position:0% all the stuff buy whatever you want then 00:18:23.190 --> 00:18:24.980 align:start position:0% all the stuff buy whatever you want then you<00:18:23.280> expose<00:18:23.550> your<00:18:23.700> own<00:18:23.790> API<00:18:23.910> for<00:18:24.330> your<00:18:24.480> app<00:18:24.720> is 00:18:24.980 --> 00:18:24.990 align:start position:0% you expose your own API for your app is 00:18:24.990 --> 00:18:27.110 align:start position:0% you expose your own API for your app is this<00:18:25.470> the<00:18:25.590> same<00:18:25.770> thing<00:18:26.010> you're<00:18:26.130> doing<00:18:26.160> or<00:18:26.610> are 00:18:27.110 --> 00:18:27.120 align:start position:0% this the same thing you're doing or are 00:18:27.120 --> 00:18:28.640 align:start position:0% this the same thing you're doing or are you<00:18:27.240> like<00:18:27.360> taking<00:18:27.660> a<00:18:27.720> political<00:18:28.020> a<00:18:28.350> different 00:18:28.640 --> 00:18:28.650 align:start position:0% you like taking a political a different 00:18:28.650 --> 00:18:31.610 align:start position:0% you like taking a political a different approach<00:18:28.860> yeah<00:18:29.400> it's<00:18:30.180> it's<00:18:30.600> similar<00:18:31.050> so<00:18:31.590> I 00:18:31.610 --> 00:18:31.620 align:start position:0% approach yeah it's it's similar so I 00:18:31.620 --> 00:18:34.670 align:start position:0% approach yeah it's it's similar so I think<00:18:31.880> for<00:18:32.880> a<00:18:32.940> theory<00:18:33.270> I'm<00:18:33.450> and<00:18:34.080> I<00:18:34.320> think<00:18:34.590> this 00:18:34.670 --> 00:18:34.680 align:start position:0% think for a theory I'm and I think this 00:18:34.680 --> 00:18:35.900 align:start position:0% think for a theory I'm and I think this is<00:18:34.740> probably<00:18:34.860> like<00:18:35.070> ask<00:18:35.280> me<00:18:35.370> afterwards<00:18:35.670> I'm 00:18:35.900 --> 00:18:35.910 align:start position:0% is probably like ask me afterwards I'm 00:18:35.910 --> 00:18:37.190 align:start position:0% is probably like ask me afterwards I'm happy<00:18:36.060> to<00:18:36.150> go<00:18:36.240> through<00:18:36.450> it<00:18:36.570> but<00:18:36.900> basically 00:18:37.190 --> 00:18:37.200 align:start position:0% happy to go through it but basically 00:18:37.200 --> 00:18:38.390 align:start position:0% happy to go through it but basically what<00:18:37.590> we<00:18:37.650> do<00:18:37.770> for<00:18:37.920> aetherium 00:18:38.390 --> 00:18:38.400 align:start position:0% what we do for aetherium 00:18:38.400 --> 00:18:40.700 align:start position:0% what we do for aetherium is<00:18:38.520> we<00:18:39.150> basically<00:18:39.300> take<00:18:39.960> each<00:18:40.230> piece<00:18:40.560> of 00:18:40.700 --> 00:18:40.710 align:start position:0% is we basically take each piece of 00:18:40.710 --> 00:18:42.470 align:start position:0% is we basically take each piece of etherium<00:18:41.040> data<00:18:41.250> and<00:18:41.520> it's<00:18:41.910> not<00:18:42.000> we<00:18:42.120> just<00:18:42.240> dump 00:18:42.470 --> 00:18:42.480 align:start position:0% etherium data and it's not we just dump 00:18:42.480 --> 00:18:43.910 align:start position:0% etherium data and it's not we just dump into<00:18:42.630> a<00:18:42.720> database<00:18:43.020> we<00:18:43.260> actually<00:18:43.470> index<00:18:43.740> and 00:18:43.910 --> 00:18:43.920 align:start position:0% into a database we actually index and 00:18:43.920 --> 00:18:45.290 align:start position:0% into a database we actually index and store<00:18:44.070> it<00:18:44.160> in<00:18:44.220> a<00:18:44.280> bunch<00:18:44.490> of<00:18:44.580> different<00:18:44.640> ways<00:18:44.970> so 00:18:45.290 --> 00:18:45.300 align:start position:0% store it in a bunch of different ways so 00:18:45.300 --> 00:18:47.480 align:start position:0% store it in a bunch of different ways so you<00:18:45.390> can<00:18:45.510> query<00:18:45.720> it<00:18:45.870> in<00:18:46.470> really<00:18:46.770> flexibly<00:18:47.250> so 00:18:47.480 --> 00:18:47.490 align:start position:0% you can query it in really flexibly so 00:18:47.490 --> 00:18:49.310 align:start position:0% you can query it in really flexibly so for<00:18:48.060> example<00:18:48.420> the<00:18:48.570> simple<00:18:48.720> naive<00:18:49.110> way<00:18:49.200> of 00:18:49.310 --> 00:18:49.320 align:start position:0% for example the simple naive way of 00:18:49.320 --> 00:18:50.870 align:start position:0% for example the simple naive way of doing<00:18:49.500> you<00:18:49.590> just<00:18:49.740> take<00:18:50.100> all<00:18:50.220> the<00:18:50.310> data<00:18:50.430> dump<00:18:50.790> in 00:18:50.870 --> 00:18:50.880 align:start position:0% doing you just take all the data dump in 00:18:50.880 --> 00:18:52.400 align:start position:0% doing you just take all the data dump in a<00:18:50.940> sequel<00:18:51.210> database<00:18:51.480> and<00:18:51.660> you<00:18:51.750> and<00:18:51.960> you<00:18:52.050> return 00:18:52.400 --> 00:18:52.410 align:start position:0% a sequel database and you and you return 00:18:52.410 --> 00:18:53.840 align:start position:0% a sequel database and you and you return it<00:18:52.560> but<00:18:52.860> you<00:18:52.920> can<00:18:53.010> only<00:18:53.070> query<00:18:53.250> certain<00:18:53.640> things 00:18:53.840 --> 00:18:53.850 align:start position:0% it but you can only query certain things 00:18:53.850 --> 00:18:55.550 align:start position:0% it but you can only query certain things like<00:18:54.060> that<00:18:54.210> so<00:18:54.660> we<00:18:54.750> have<00:18:54.900> like<00:18:55.050> time<00:18:55.290> series 00:18:55.550 --> 00:18:55.560 align:start position:0% like that so we have like time series 00:18:55.560 --> 00:18:57.710 align:start position:0% like that so we have like time series database<00:18:55.890> we<00:18:56.040> have<00:18:56.070> caches<00:18:56.550> we<00:18:56.730> have<00:18:56.820> Redis<00:18:57.540> we 00:18:57.710 --> 00:18:57.720 align:start position:0% database we have caches we have Redis we 00:18:57.720 --> 00:18:58.820 align:start position:0% database we have caches we have Redis we have<00:18:57.810> an<00:18:57.900> emcee<00:18:58.170> quote<00:18:58.320> we<00:18:58.410> have<00:18:58.440> like<00:18:58.620> all 00:18:58.820 --> 00:18:58.830 align:start position:0% have an emcee quote we have like all 00:18:58.830 --> 00:19:00.590 align:start position:0% have an emcee quote we have like all these<00:18:58.980> different<00:18:59.370> things<00:18:59.520> that<00:18:59.880> we<00:19:00.060> use<00:19:00.300> that 00:19:00.590 --> 00:19:00.600 align:start position:0% these different things that we use that 00:19:00.600 --> 00:19:02.600 align:start position:0% these different things that we use that enables<00:19:01.350> you<00:19:01.470> to<00:19:01.500> query<00:19:01.740> like<00:19:02.100> really<00:19:02.490> really 00:19:02.600 --> 00:19:02.610 align:start position:0% enables you to query like really really 00:19:02.610 --> 00:19:03.170 align:start position:0% enables you to query like really really flexibly 00:19:03.170 --> 00:19:03.180 align:start position:0% flexibly 00:19:03.180 --> 00:19:05.420 align:start position:0% flexibly so<00:19:03.540> the<00:19:03.840> short<00:19:04.020> answer<00:19:04.080> is<00:19:04.290> like<00:19:04.440> it's<00:19:05.250> kind<00:19:05.400> of 00:19:05.420 --> 00:19:05.430 align:start position:0% so the short answer is like it's kind of 00:19:05.430 --> 00:19:07.310 align:start position:0% so the short answer is like it's kind of like<00:19:05.520> you<00:19:05.970> know<00:19:06.000> if<00:19:06.360> you're<00:19:06.600> bicycling<00:19:07.110> is 00:19:07.310 --> 00:19:07.320 align:start position:0% like you know if you're bicycling is 00:19:07.320 --> 00:19:08.420 align:start position:0% like you know if you're bicycling is that<00:19:07.440> the<00:19:07.530> same<00:19:07.710> thing<00:19:07.860> as<00:19:08.010> like<00:19:08.160> a<00:19:08.190> Ferrari 00:19:08.420 --> 00:19:08.430 align:start position:0% that the same thing as like a Ferrari 00:19:08.430 --> 00:19:10.130 align:start position:0% that the same thing as like a Ferrari it's<00:19:08.730> like<00:19:08.820> you<00:19:09.000> know<00:19:09.120> kind<00:19:09.450> of<00:19:09.540> but<00:19:09.720> little 00:19:10.130 --> 00:19:10.140 align:start position:0% it's like you know kind of but little 00:19:10.140 --> 00:19:12.410 align:start position:0% it's like you know kind of but little different<00:19:10.440> okay<00:19:10.950> so<00:19:11.460> in<00:19:11.580> this<00:19:11.670> case<00:19:11.880> like<00:19:12.060> to 00:19:12.410 --> 00:19:12.420 align:start position:0% different okay so in this case like to 00:19:12.420 --> 00:19:14.690 align:start position:0% different okay so in this case like to get<00:19:12.570> the<00:19:12.900> wizards<00:19:13.590> by<00:19:13.740> owner<00:19:13.980> this<00:19:14.400> was<00:19:14.550> like 00:19:14.690 --> 00:19:14.700 align:start position:0% get the wizards by owner this was like 00:19:14.700 --> 00:19:16.490 align:start position:0% get the wizards by owner this was like your<00:19:14.910> client<00:19:15.270> that<00:19:15.330> gave<00:19:15.600> you<00:19:15.810> like 00:19:16.490 --> 00:19:16.500 align:start position:0% your client that gave you like 00:19:16.500 --> 00:19:18.110 align:start position:0% your client that gave you like requirement<00:19:17.220> fees<00:19:17.370> I<00:19:17.490> want<00:19:17.700> to<00:19:17.760> get<00:19:17.850> them<00:19:18.000> by 00:19:18.110 --> 00:19:18.120 align:start position:0% requirement fees I want to get them by 00:19:18.120 --> 00:19:20.180 align:start position:0% requirement fees I want to get them by the<00:19:18.180> owner<00:19:18.420> or<00:19:18.690> it<00:19:19.410> just<00:19:19.620> like<00:19:19.800> build 00:19:20.180 --> 00:19:20.190 align:start position:0% the owner or it just like build 00:19:20.190 --> 00:19:21.440 align:start position:0% the owner or it just like build something<00:19:20.520> so<00:19:20.610> generic<00:19:21.030> that<00:19:21.060> it<00:19:21.300> also 00:19:21.440 --> 00:19:21.450 align:start position:0% something so generic that it also 00:19:21.450 --> 00:19:23.210 align:start position:0% something so generic that it also supports<00:19:21.780> getting<00:19:22.110> by<00:19:22.290> the<00:19:22.350> owner<00:19:22.530> we<00:19:22.980> it's 00:19:23.210 --> 00:19:23.220 align:start position:0% supports getting by the owner we it's 00:19:23.220 --> 00:19:24.800 align:start position:0% supports getting by the owner we it's great<00:19:23.340> question<00:19:23.670> we<00:19:24.240> actually<00:19:24.390> did<00:19:24.690> the 00:19:24.800 --> 00:19:24.810 align:start position:0% great question we actually did the 00:19:24.810 --> 00:19:26.300 align:start position:0% great question we actually did the process<00:19:25.020> I<00:19:25.290> talked<00:19:25.500> about<00:19:25.680> earlier<00:19:25.950> we<00:19:26.100> sat 00:19:26.300 --> 00:19:26.310 align:start position:0% process I talked about earlier we sat 00:19:26.310 --> 00:19:27.410 align:start position:0% process I talked about earlier we sat down<00:19:26.340> with<00:19:26.640> our<00:19:26.670> customer<00:19:27.030> which<00:19:27.150> sat<00:19:27.330> down 00:19:27.410 --> 00:19:27.420 align:start position:0% down with our customer which sat down 00:19:27.420 --> 00:19:29.180 align:start position:0% down with our customer which sat down crypto<00:19:27.720> kiddies<00:19:27.990> and<00:19:28.110> we<00:19:28.470> brainstormed<00:19:29.070> and 00:19:29.180 --> 00:19:29.190 align:start position:0% crypto kiddies and we brainstormed and 00:19:29.190 --> 00:19:30.530 align:start position:0% crypto kiddies and we brainstormed and we<00:19:29.280> talked<00:19:29.460> some<00:19:29.580> developers<00:19:30.060> and<00:19:30.300> we<00:19:30.360> said 00:19:30.530 --> 00:19:30.540 align:start position:0% we talked some developers and we said 00:19:30.540 --> 00:19:32.210 align:start position:0% we talked some developers and we said hey<00:19:30.900> here's<00:19:31.200> what<00:19:31.410> we<00:19:31.500> think<00:19:31.770> it<00:19:31.890> should<00:19:32.070> do 00:19:32.210 --> 00:19:32.220 align:start position:0% hey here's what we think it should do 00:19:32.220 --> 00:19:34.070 align:start position:0% hey here's what we think it should do and<00:19:32.490> it<00:19:33.090> turns<00:19:33.270> out<00:19:33.390> in<00:19:33.480> this<00:19:33.630> case<00:19:33.690> was 00:19:34.070 --> 00:19:34.080 align:start position:0% and it turns out in this case was 00:19:34.080 --> 00:19:35.480 align:start position:0% and it turns out in this case was actually<00:19:34.350> pretty<00:19:34.530> easy<00:19:34.620> we<00:19:34.950> did<00:19:35.070> like<00:19:35.190> three 00:19:35.480 --> 00:19:35.490 align:start position:0% actually pretty easy we did like three 00:19:35.490 --> 00:19:36.560 align:start position:0% actually pretty easy we did like three or<00:19:35.580> four<00:19:35.610> iterations<00:19:35.850> and<00:19:36.300> we're<00:19:36.390> done 00:19:36.560 --> 00:19:36.570 align:start position:0% or four iterations and we're done 00:19:36.570 --> 00:19:38.570 align:start position:0% or four iterations and we're done because<00:19:36.930> the<00:19:37.320> game<00:19:37.530> is<00:19:37.680> a<00:19:37.710> very<00:19:37.860> small<00:19:38.310> subset 00:19:38.570 --> 00:19:38.580 align:start position:0% because the game is a very small subset 00:19:38.580 --> 00:19:39.920 align:start position:0% because the game is a very small subset you<00:19:38.940> can<00:19:39.060> only<00:19:39.150> do<00:19:39.270> a<00:19:39.330> few<00:19:39.360> things<00:19:39.570> you<00:19:39.900> have 00:19:39.920 --> 00:19:39.930 align:start position:0% you can only do a few things you have 00:19:39.930 --> 00:19:41.330 align:start position:0% you can only do a few things you have wizards<00:19:40.260> they<00:19:40.410> fight<00:19:40.650> and<00:19:40.830> there's<00:19:40.980> duels<00:19:41.250> and 00:19:41.330 --> 00:19:41.340 align:start position:0% wizards they fight and there's duels and 00:19:41.340 --> 00:19:42.500 align:start position:0% wizards they fight and there's duels and that's<00:19:41.490> about<00:19:41.610> it<00:19:41.790> and<00:19:42.060> something<00:19:42.330> like<00:19:42.360> a 00:19:42.500 --> 00:19:42.510 align:start position:0% that's about it and something like a 00:19:42.510 --> 00:19:44.000 align:start position:0% that's about it and something like a theorem<00:19:42.840> is<00:19:42.930> much<00:19:43.200> more<00:19:43.410> complicated<00:19:43.710> because 00:19:44.000 --> 00:19:44.010 align:start position:0% theorem is much more complicated because 00:19:44.010 --> 00:19:45.620 align:start position:0% theorem is much more complicated because you<00:19:44.190> can<00:19:44.280> query<00:19:44.460> it<00:19:44.580> in<00:19:44.700> any<00:19:44.790> way<00:19:44.970> possible 00:19:45.620 --> 00:19:45.630 align:start position:0% you can query it in any way possible 00:19:45.630 --> 00:19:46.940 align:start position:0% you can query it in any way possible well<00:19:45.840> basically<00:19:46.260> took<00:19:46.350> the<00:19:46.500> approach<00:19:46.710> they 00:19:46.940 --> 00:19:46.950 align:start position:0% well basically took the approach they 00:19:46.950 --> 00:19:49.970 align:start position:0% well basically took the approach they shared<00:19:47.520> earlier<00:19:47.670> thanks<00:19:48.390> yeah<00:19:48.830> all<00:19:49.830> right 00:19:49.970 --> 00:19:49.980 align:start position:0% shared earlier thanks yeah all right 00:19:49.980 --> 00:19:51.500 align:start position:0% shared earlier thanks yeah all right cool<00:19:50.220> I<00:19:50.310> think<00:19:50.460> we're<00:19:50.580> times<00:19:50.880> up<00:19:51.030> but<00:19:51.210> I'll<00:19:51.390> be 00:19:51.500 --> 00:19:51.510 align:start position:0% cool I think we're times up but I'll be 00:19:51.510 --> 00:19:51.830 align:start position:0% cool I think we're times up but I'll be around 00:19:51.830 --> 00:19:51.840 align:start position:0% around 00:19:51.840 --> 00:19:55.820 align:start position:0% around I<00:19:51.870> have<00:19:52.320> stickers<00:19:52.680> and<00:19:53.090> I<00:19:54.090> have<00:19:54.780> answers<00:19:55.260> some 00:19:55.820 --> 00:19:55.830 align:start position:0% I have stickers and I have answers some 00:19:55.830 --> 00:19:57.050 align:start position:0% I have stickers and I have answers some answers<00:19:56.130> to<00:19:56.340> some<00:19:56.370> of<00:19:56.550> the<00:19:56.610> questions<00:19:56.940> you'll 00:19:57.050 --> 00:19:57.060 align:start position:0% answers to some of the questions you'll 00:19:57.060 --> 00:20:00.150 align:start position:0% answers to some of the questions you'll probably<00:19:57.240> ask<00:19:57.390> but<00:19:57.930> come<00:19:58.200> find<00:19:58.350> me<00:19:58.410> thanks 00:20:00.150 --> 00:20:00.160 align:start position:0% probably ask but come find me thanks 00:20:00.160 --> 00:20:09.420 align:start position:0% probably ask but come find me thanks you 00:20:09.420 --> 00:20:09.430 align:start position:0% 00:20:09.430 --> 00:20:11.490 align:start position:0% you