WEBVTT Kind: captions Language: en 00:00:17.230 --> 00:00:20.679 align:start position:0% thank<00:00:18.230> you<00:00:18.320> so<00:00:18.880> this<00:00:19.880> is<00:00:20.060> a<00:00:20.090> short<00:00:20.419> talk<00:00:20.570> so 00:00:20.679 --> 00:00:20.689 align:start position:0% thank you so this is a short talk so 00:00:20.689 --> 00:00:22.179 align:start position:0% thank you so this is a short talk so I'll<00:00:20.779> go<00:00:20.899> ahead<00:00:21.020> and<00:00:21.259> just<00:00:21.470> jump<00:00:21.560> into<00:00:21.890> it<00:00:21.980> I 00:00:22.179 --> 00:00:22.189 align:start position:0% I'll go ahead and just jump into it I 00:00:22.189 --> 00:00:25.420 align:start position:0% I'll go ahead and just jump into it I was<00:00:22.310> going<00:00:22.489> to<00:00:22.640> give<00:00:22.849> a<00:00:23.860> you<00:00:24.860> know<00:00:24.950> basic<00:00:25.279> how 00:00:25.420 --> 00:00:25.430 align:start position:0% was going to give a you know basic how 00:00:25.430 --> 00:00:27.790 align:start position:0% was going to give a you know basic how prediction<00:00:26.419> markets<00:00:26.720> work<00:00:26.899> introduction<00:00:27.680> I 00:00:27.790 --> 00:00:27.800 align:start position:0% prediction markets work introduction I 00:00:27.800 --> 00:00:29.290 align:start position:0% prediction markets work introduction I thought<00:00:27.980> we<00:00:28.550> put<00:00:28.700> together<00:00:28.820> this<00:00:29.000> really<00:00:29.210> nice 00:00:29.290 --> 00:00:29.300 align:start position:0% thought we put together this really nice 00:00:29.300 --> 00:00:31.900 align:start position:0% thought we put together this really nice video<00:00:29.509> and<00:00:29.899> lead<00:00:30.739> up<00:00:30.829> to<00:00:30.860> our<00:00:31.040> crowd<00:00:31.220> sale<00:00:31.489> so 00:00:31.900 --> 00:00:31.910 align:start position:0% video and lead up to our crowd sale so 00:00:31.910 --> 00:00:32.830 align:start position:0% video and lead up to our crowd sale so I'll<00:00:31.970> just<00:00:32.090> show<00:00:32.210> you<00:00:32.270> the<00:00:32.390> video<00:00:32.630> and<00:00:32.660> we'll 00:00:32.830 --> 00:00:32.840 align:start position:0% I'll just show you the video and we'll 00:00:32.840 --> 00:00:34.360 align:start position:0% I'll just show you the video and we'll have<00:00:32.930> time<00:00:33.140> for<00:00:33.170> some<00:00:33.440> actual<00:00:34.010> technical 00:00:34.360 --> 00:00:34.370 align:start position:0% have time for some actual technical 00:00:34.370 --> 00:00:45.400 align:start position:0% have time for some actual technical stuff<00:00:43.120> auger<00:00:44.120> is<00:00:44.270> a<00:00:44.300> prediction<00:00:44.960> market 00:00:45.400 --> 00:00:45.410 align:start position:0% stuff auger is a prediction market 00:00:45.410 --> 00:00:47.350 align:start position:0% stuff auger is a prediction market platform<00:00:45.980> that<00:00:46.220> rewards<00:00:46.700> a<00:00:46.790> user<00:00:47.030> for 00:00:47.350 --> 00:00:47.360 align:start position:0% platform that rewards a user for 00:00:47.360 --> 00:00:51.030 align:start position:0% platform that rewards a user for correctly<00:00:47.810> predicting<00:00:48.530> future<00:00:48.800> events 00:00:51.030 --> 00:00:51.040 align:start position:0% correctly predicting future events 00:00:51.040 --> 00:00:53.380 align:start position:0% correctly predicting future events prediction<00:00:52.040> markets<00:00:52.430> allow<00:00:52.700> users<00:00:53.210> to 00:00:53.380 --> 00:00:53.390 align:start position:0% prediction markets allow users to 00:00:53.390 --> 00:00:55.600 align:start position:0% prediction markets allow users to purchase<00:00:53.630> and<00:00:54.050> sell<00:00:54.320> shares<00:00:54.350> and<00:00:55.010> the<00:00:55.070> outcome 00:00:55.600 --> 00:00:55.610 align:start position:0% purchase and sell shares and the outcome 00:00:55.610 --> 00:00:58.180 align:start position:0% purchase and sell shares and the outcome of<00:00:55.640> an<00:00:55.940> event<00:00:56.230> the<00:00:57.230> current<00:00:57.590> market<00:00:57.890> price<00:00:58.160> of 00:00:58.180 --> 00:00:58.190 align:start position:0% of an event the current market price of 00:00:58.190 --> 00:00:59.979 align:start position:0% of an event the current market price of a<00:00:58.460> share<00:00:58.489> is<00:00:58.940> an<00:00:59.090> estimate<00:00:59.630> of<00:00:59.690> the 00:00:59.979 --> 00:00:59.989 align:start position:0% a share is an estimate of the 00:00:59.989 --> 00:01:01.540 align:start position:0% a share is an estimate of the probability<00:01:00.110> of<00:01:00.920> an<00:01:01.040> event<00:01:01.130> actually 00:01:01.540 --> 00:01:01.550 align:start position:0% probability of an event actually 00:01:01.550 --> 00:01:02.460 align:start position:0% probability of an event actually occurring 00:01:02.460 --> 00:01:02.470 align:start position:0% occurring 00:01:02.470 --> 00:01:05.649 align:start position:0% occurring the<00:01:03.470> prices<00:01:03.980> of<00:01:04.009> each<00:01:04.339> share<00:01:04.729> adds<00:01:05.030> up<00:01:05.299> to<00:01:05.329> one 00:01:05.649 --> 00:01:05.659 align:start position:0% the prices of each share adds up to one 00:01:05.659 --> 00:01:07.810 align:start position:0% the prices of each share adds up to one dollar<00:01:05.930> so<00:01:06.439> if<00:01:06.560> you<00:01:06.680> buy<00:01:06.860> a<00:01:06.890> share<00:01:07.009> and<00:01:07.490> even 00:01:07.810 --> 00:01:07.820 align:start position:0% dollar so if you buy a share and even 00:01:07.820 --> 00:01:10.719 align:start position:0% dollar so if you buy a share and even odds<00:01:08.030> in<00:01:08.390> the<00:01:08.479> cost<00:01:08.720> you<00:01:08.870> fifty<00:01:09.380> cents<00:01:09.770> if<00:01:10.580> you 00:01:10.719 --> 00:01:10.729 align:start position:0% odds in the cost you fifty cents if you 00:01:10.729 --> 00:01:13.060 align:start position:0% odds in the cost you fifty cents if you end<00:01:10.909> up<00:01:11.030> being<00:01:11.240> right<00:01:11.510> you'll<00:01:12.140> receive<00:01:12.440> $1<00:01:12.770> for 00:01:13.060 --> 00:01:13.070 align:start position:0% end up being right you'll receive $1 for 00:01:13.070 --> 00:01:16.030 align:start position:0% end up being right you'll receive $1 for that<00:01:13.190> share<00:01:13.720> these<00:01:14.720> markets<00:01:15.380> rely<00:01:15.740> on<00:01:15.770> a 00:01:16.030 --> 00:01:16.040 align:start position:0% that share these markets rely on a 00:01:16.040 --> 00:01:18.310 align:start position:0% that share these markets rely on a scientific<00:01:16.700> principle<00:01:16.880> known<00:01:17.600> as<00:01:17.630> the<00:01:17.810> wisdom 00:01:18.310 --> 00:01:18.320 align:start position:0% scientific principle known as the wisdom 00:01:18.320 --> 00:01:20.740 align:start position:0% scientific principle known as the wisdom of<00:01:18.440> the<00:01:18.560> crowd<00:01:18.890> which<00:01:19.670> states<00:01:20.060> that<00:01:20.420> if<00:01:20.659> you 00:01:20.740 --> 00:01:20.750 align:start position:0% of the crowd which states that if you 00:01:20.750 --> 00:01:22.480 align:start position:0% of the crowd which states that if you ask<00:01:20.960> enough<00:01:21.350> people<00:01:21.620> something<00:01:22.040> their 00:01:22.480 --> 00:01:22.490 align:start position:0% ask enough people something their 00:01:22.490 --> 00:01:23.880 align:start position:0% ask enough people something their average<00:01:22.940> answer<00:01:23.210> is 00:01:23.880 --> 00:01:23.890 align:start position:0% average answer is 00:01:23.890 --> 00:01:27.270 align:start position:0% average answer is far<00:01:24.520> more<00:01:24.550> accurate<00:01:25.030> than<00:01:25.510> any<00:01:25.690> expert<00:01:26.280> this 00:01:27.270 --> 00:01:27.280 align:start position:0% far more accurate than any expert this 00:01:27.280 --> 00:01:29.250 align:start position:0% far more accurate than any expert this allows<00:01:27.940> us<00:01:28.240> to<00:01:28.390> create<00:01:28.690> one<00:01:29.050> of<00:01:29.080> the<00:01:29.229> most 00:01:29.250 --> 00:01:29.260 align:start position:0% allows us to create one of the most 00:01:29.260 --> 00:01:33.180 align:start position:0% allows us to create one of the most powerful<00:01:30.270> forecasting<00:01:31.270> tools<00:01:31.680> the<00:01:32.680> problem 00:01:33.180 --> 00:01:33.190 align:start position:0% powerful forecasting tools the problem 00:01:33.190 --> 00:01:35.280 align:start position:0% powerful forecasting tools the problem with<00:01:33.340> previous<00:01:33.880> prediction<00:01:34.479> markets<00:01:34.930> is<00:01:35.110> that 00:01:35.280 --> 00:01:35.290 align:start position:0% with previous prediction markets is that 00:01:35.290 --> 00:01:37.620 align:start position:0% with previous prediction markets is that they<00:01:35.470> were<00:01:35.530> centralized<00:01:36.369> allowing<00:01:37.330> them<00:01:37.510> to 00:01:37.620 --> 00:01:37.630 align:start position:0% they were centralized allowing them to 00:01:37.630 --> 00:01:40.620 align:start position:0% they were centralized allowing them to be<00:01:37.750> easily<00:01:38.200> shut<00:01:38.590> down<00:01:38.950> another<00:01:39.940> problem<00:01:40.479> is 00:01:40.620 --> 00:01:40.630 align:start position:0% be easily shut down another problem is 00:01:40.630 --> 00:01:42.749 align:start position:0% be easily shut down another problem is that<00:01:40.930> with<00:01:41.080> any<00:01:41.350> prediction<00:01:41.890> markets<00:01:42.400> someone 00:01:42.749 --> 00:01:42.759 align:start position:0% that with any prediction markets someone 00:01:42.759 --> 00:01:44.790 align:start position:0% that with any prediction markets someone has<00:01:42.940> to<00:01:43.090> report<00:01:43.509> what<00:01:43.750> actually<00:01:44.320> happened 00:01:44.790 --> 00:01:44.800 align:start position:0% has to report what actually happened 00:01:44.800 --> 00:01:48.060 align:start position:0% has to report what actually happened after<00:01:45.460> the<00:01:45.610> event<00:01:45.970> occurred<00:01:46.150> in<00:01:47.110> centralized 00:01:48.060 --> 00:01:48.070 align:start position:0% after the event occurred in centralized 00:01:48.070 --> 00:01:51.210 align:start position:0% after the event occurred in centralized markets<00:01:48.700> one<00:01:49.090> person<00:01:49.780> does<00:01:50.020> this<00:01:50.290> which<00:01:50.950> means 00:01:51.210 --> 00:01:51.220 align:start position:0% markets one person does this which means 00:01:51.220 --> 00:01:53.490 align:start position:0% markets one person does this which means there<00:01:51.430> could<00:01:51.550> be<00:01:51.610> mistakes<00:01:51.960> or<00:01:52.960> outright 00:01:53.490 --> 00:01:53.500 align:start position:0% there could be mistakes or outright 00:01:53.500 --> 00:01:56.820 align:start position:0% there could be mistakes or outright manipulation<00:01:54.479> with<00:01:55.479> augur<00:01:56.080> will<00:01:56.649> have 00:01:56.820 --> 00:01:56.830 align:start position:0% manipulation with augur will have 00:01:56.830 --> 00:01:58.950 align:start position:0% manipulation with augur will have thousands<00:01:57.610> of<00:01:57.670> users<00:01:57.970> reporting<00:01:58.660> on<00:01:58.810> these 00:01:58.950 --> 00:01:58.960 align:start position:0% thousands of users reporting on these 00:01:58.960 --> 00:02:00.620 align:start position:0% thousands of users reporting on these outcomes<00:01:59.500> using<00:01:59.830> something<00:02:00.250> called 00:02:00.620 --> 00:02:00.630 align:start position:0% outcomes using something called 00:02:00.630 --> 00:02:03.749 align:start position:0% outcomes using something called reputation<00:02:02.070> using<00:02:03.070> augur 00:02:03.749 --> 00:02:03.759 align:start position:0% reputation using augur 00:02:03.759 --> 00:02:06.540 align:start position:0% reputation using augur anyone<00:02:04.509> anywhere<00:02:05.289> in<00:02:05.350> the<00:02:05.530> world<00:02:05.619> can<00:02:06.250> create 00:02:06.540 --> 00:02:06.550 align:start position:0% anyone anywhere in the world can create 00:02:06.550 --> 00:02:08.100 align:start position:0% anyone anywhere in the world can create a<00:02:06.580> market<00:02:07.030> asking<00:02:07.420> a<00:02:07.509> question<00:02:07.930> about 00:02:08.100 --> 00:02:08.110 align:start position:0% a market asking a question about 00:02:08.110 --> 00:02:11.100 align:start position:0% a market asking a question about anything<00:02:09.060> market<00:02:10.060> makers<00:02:10.420> provide<00:02:10.869> some 00:02:11.100 --> 00:02:11.110 align:start position:0% anything market makers provide some 00:02:11.110 --> 00:02:13.170 align:start position:0% anything market makers provide some initial<00:02:11.350> funding<00:02:11.950> for<00:02:12.160> the<00:02:12.220> market<00:02:12.610> and<00:02:12.970> in 00:02:13.170 --> 00:02:13.180 align:start position:0% initial funding for the market and in 00:02:13.180 --> 00:02:15.410 align:start position:0% initial funding for the market and in return<00:02:13.570> receives<00:02:14.110> some<00:02:14.350> trading<00:02:14.620> fees 00:02:15.410 --> 00:02:15.420 align:start position:0% return receives some trading fees 00:02:15.420 --> 00:02:19.050 align:start position:0% return receives some trading fees anybody<00:02:16.420> can<00:02:16.810> freely<00:02:17.140> buy<00:02:17.590> and<00:02:17.950> sell<00:02:18.580> shares 00:02:19.050 --> 00:02:19.060 align:start position:0% anybody can freely buy and sell shares 00:02:19.060 --> 00:02:21.420 align:start position:0% anybody can freely buy and sell shares in<00:02:19.390> the<00:02:19.480> outcome<00:02:19.900> of<00:02:19.930> that<00:02:20.080> market<00:02:20.680> in<00:02:21.280> the 00:02:21.420 --> 00:02:21.430 align:start position:0% in the outcome of that market in the 00:02:21.430 --> 00:02:23.550 align:start position:0% in the outcome of that market in the current<00:02:21.790> share<00:02:22.090> prices<00:02:22.450> provide<00:02:22.989> the<00:02:23.230> best 00:02:23.550 --> 00:02:23.560 align:start position:0% current share prices provide the best 00:02:23.560 --> 00:02:27.090 align:start position:0% current share prices provide the best estimate<00:02:24.280> of<00:02:24.459> that<00:02:24.730> event<00:02:25.060> occurring<00:02:26.100> imagine 00:02:27.090 --> 00:02:27.100 align:start position:0% estimate of that event occurring imagine 00:02:27.100 --> 00:02:29.340 align:start position:0% estimate of that event occurring imagine being<00:02:27.700> able<00:02:27.850> to<00:02:28.000> Google<00:02:28.540> questions<00:02:29.079> about 00:02:29.340 --> 00:02:29.350 align:start position:0% being able to Google questions about 00:02:29.350 --> 00:02:31.050 align:start position:0% being able to Google questions about things<00:02:29.590> that<00:02:29.769> haven't<00:02:30.220> happened<00:02:30.430> yet<00:02:30.670> and 00:02:31.050 --> 00:02:31.060 align:start position:0% things that haven't happened yet and 00:02:31.060 --> 00:02:33.180 align:start position:0% things that haven't happened yet and receiving<00:02:31.900> accurate<00:02:32.200> odds<00:02:32.680> of<00:02:33.040> their 00:02:33.180 --> 00:02:33.190 align:start position:0% receiving accurate odds of their 00:02:33.190 --> 00:02:36.420 align:start position:0% receiving accurate odds of their occurrence<00:02:33.750> that<00:02:34.750> power<00:02:35.200> the<00:02:35.709> power<00:02:36.040> dat 00:02:36.420 --> 00:02:36.430 align:start position:0% occurrence that power the power dat 00:02:36.430 --> 00:02:38.460 align:start position:0% occurrence that power the power dat glimpse<00:02:36.820> into<00:02:36.970> the<00:02:37.180> future<00:02:37.209> is<00:02:38.019> what<00:02:38.290> we 00:02:38.460 --> 00:02:38.470 align:start position:0% glimpse into the future is what we 00:02:38.470 --> 00:02:45.250 align:start position:0% glimpse into the future is what we believe<00:02:38.650> everyone<00:02:39.430> should<00:02:39.880> have<00:02:39.970> access<00:02:40.209> to 00:02:45.250 --> 00:02:45.260 align:start position:0% 00:02:45.260 --> 00:02:47.750 align:start position:0% okay<00:02:46.260> so<00:02:46.320> that's<00:02:46.500> the<00:02:46.740> sort<00:02:47.430> of<00:02:47.490> a<00:02:47.550> high-level 00:02:47.750 --> 00:02:47.760 align:start position:0% okay so that's the sort of a high-level 00:02:47.760 --> 00:02:50.300 align:start position:0% okay so that's the sort of a high-level overview<00:02:47.970> of<00:02:48.270> just<00:02:48.990> what<00:02:49.320> what<00:02:49.860> are<00:02:49.950> we<00:02:49.980> making 00:02:50.300 --> 00:02:50.310 align:start position:0% overview of just what what are we making 00:02:50.310 --> 00:02:51.590 align:start position:0% overview of just what what are we making we're<00:02:50.640> making<00:02:50.880> a<00:02:50.970> prediction<00:02:51.210> market 00:02:51.590 --> 00:02:51.600 align:start position:0% we're making a prediction market 00:02:51.600 --> 00:02:54.860 align:start position:0% we're making a prediction market platform<00:02:51.990> now<00:02:53.030> so<00:02:54.030> we've<00:02:54.180> learned<00:02:54.270> a<00:02:54.450> lot<00:02:54.480> of 00:02:54.860 --> 00:02:54.870 align:start position:0% platform now so we've learned a lot of 00:02:54.870 --> 00:02:58.460 align:start position:0% platform now so we've learned a lot of sort<00:02:55.140> of<00:02:55.280> low-level<00:02:56.280> stuff<00:02:56.400> about<00:02:57.470> etherium 00:02:58.460 --> 00:02:58.470 align:start position:0% sort of low-level stuff about etherium 00:02:58.470 --> 00:03:00.500 align:start position:0% sort of low-level stuff about etherium and<00:02:58.740> how<00:02:59.160> you<00:02:59.220> make<00:02:59.850> decentralized 00:03:00.500 --> 00:03:00.510 align:start position:0% and how you make decentralized 00:03:00.510 --> 00:03:02.150 align:start position:0% and how you make decentralized applications<00:03:00.690> over<00:03:01.230> the<00:03:01.320> past<00:03:01.500> few<00:03:01.650> days<00:03:01.800> and 00:03:02.150 --> 00:03:02.160 align:start position:0% applications over the past few days and 00:03:02.160 --> 00:03:04.070 align:start position:0% applications over the past few days and so<00:03:02.430> you<00:03:02.520> might<00:03:02.610> be<00:03:02.670> wondering<00:03:02.910> how<00:03:03.300> the<00:03:03.930> heck 00:03:04.070 --> 00:03:04.080 align:start position:0% so you might be wondering how the heck 00:03:04.080 --> 00:03:05.090 align:start position:0% so you might be wondering how the heck you<00:03:04.110> make<00:03:04.350> something<00:03:04.560> like<00:03:04.650> that<00:03:04.890> on 00:03:05.090 --> 00:03:05.100 align:start position:0% you make something like that on 00:03:05.100 --> 00:03:07.250 align:start position:0% you make something like that on aetherium<00:03:05.850> just<00:03:06.060> using<00:03:06.300> smart<00:03:06.570> contracts<00:03:06.990> and 00:03:07.250 --> 00:03:07.260 align:start position:0% aetherium just using smart contracts and 00:03:07.260 --> 00:03:09.500 align:start position:0% aetherium just using smart contracts and I<00:03:08.220> know<00:03:08.610> this<00:03:08.790> is<00:03:08.910> a<00:03:08.940> fairly<00:03:09.240> technical 00:03:09.500 --> 00:03:09.510 align:start position:0% I know this is a fairly technical 00:03:09.510 --> 00:03:12.740 align:start position:0% I know this is a fairly technical audience<00:03:09.840> so<00:03:11.150> rather<00:03:12.150> than<00:03:12.300> going<00:03:12.450> through<00:03:12.570> my 00:03:12.740 --> 00:03:12.750 align:start position:0% audience so rather than going through my 00:03:12.750 --> 00:03:14.750 align:start position:0% audience so rather than going through my usual<00:03:12.930> sort<00:03:13.560> of<00:03:13.620> high-level<00:03:13.770> augurs<00:03:14.310> feel<00:03:14.550> I 00:03:14.750 --> 00:03:14.760 align:start position:0% usual sort of high-level augurs feel I 00:03:14.760 --> 00:03:16.250 align:start position:0% usual sort of high-level augurs feel I thought<00:03:15.510> I'd<00:03:15.630> actually<00:03:15.780> go<00:03:16.020> through<00:03:16.170> the 00:03:16.250 --> 00:03:16.260 align:start position:0% thought I'd actually go through the 00:03:16.260 --> 00:03:26.330 align:start position:0% thought I'd actually go through the details<00:03:21.200> okay<00:03:22.200> so<00:03:24.650> so<00:03:25.650> this<00:03:25.740> is<00:03:25.800> the<00:03:26.040> augur 00:03:26.330 --> 00:03:26.340 align:start position:0% details okay so so this is the augur 00:03:26.340 --> 00:03:28.250 align:start position:0% details okay so so this is the augur interface<00:03:26.700> now<00:03:26.850> the<00:03:26.910> first<00:03:27.120> thing<00:03:27.270> I<00:03:27.600> want<00:03:28.200> you 00:03:28.250 --> 00:03:28.260 align:start position:0% interface now the first thing I want you 00:03:28.260 --> 00:03:30.740 align:start position:0% interface now the first thing I want you to<00:03:28.350> notice<00:03:28.530> is<00:03:28.860> that<00:03:28.920> all<00:03:29.790> you<00:03:30.360> have<00:03:30.390> to<00:03:30.510> do<00:03:30.600> is 00:03:30.740 --> 00:03:30.750 align:start position:0% to notice is that all you have to do is 00:03:30.750 --> 00:03:33.290 align:start position:0% to notice is that all you have to do is go<00:03:30.900> to<00:03:30.930> a<00:03:31.530> website<00:03:32.070> so<00:03:32.520> you<00:03:32.610> go<00:03:32.730> to<00:03:32.790> client 00:03:33.290 --> 00:03:33.300 align:start position:0% go to a website so you go to client 00:03:33.300 --> 00:03:37.280 align:start position:0% go to a website so you go to client augur<00:03:33.750> net<00:03:34.140> and<00:03:34.460> the<00:03:35.460> way<00:03:35.580> this<00:03:35.730> works<00:03:35.970> is<00:03:36.300> we 00:03:37.280 --> 00:03:37.290 align:start position:0% augur net and the way this works is we 00:03:37.290 --> 00:03:40.730 align:start position:0% augur net and the way this works is we want<00:03:37.770> this<00:03:37.890> to<00:03:38.160> be<00:03:38.310> as<00:03:38.550> much<00:03:38.910> like<00:03:39.240> just<00:03:40.050> using 00:03:40.730 --> 00:03:40.740 align:start position:0% want this to be as much like just using 00:03:40.740 --> 00:03:43.010 align:start position:0% want this to be as much like just using a<00:03:40.800> regular<00:03:41.160> web<00:03:41.340> site<00:03:41.610> as<00:03:41.880> possible<00:03:42.690> even 00:03:43.010 --> 00:03:43.020 align:start position:0% a regular web site as possible even 00:03:43.020 --> 00:03:44.390 align:start position:0% a regular web site as possible even though<00:03:43.170> it's<00:03:43.290> decentralized<00:03:43.740> on<00:03:44.130> the<00:03:44.250> back 00:03:44.390 --> 00:03:44.400 align:start position:0% though it's decentralized on the back 00:03:44.400 --> 00:03:47.480 align:start position:0% though it's decentralized on the back end<00:03:44.640> so<00:03:44.850> you<00:03:45.060> don't<00:03:45.150> have<00:03:45.420> to<00:03:45.740> be<00:03:46.740> running<00:03:46.950> a 00:03:47.480 --> 00:03:47.490 align:start position:0% end so you don't have to be running a 00:03:47.490 --> 00:03:49.940 align:start position:0% end so you don't have to be running a local<00:03:48.180> etherium<00:03:48.660> node<00:03:48.840> although<00:03:49.470> you<00:03:49.530> can<00:03:49.770> and 00:03:49.940 --> 00:03:49.950 align:start position:0% local etherium node although you can and 00:03:49.950 --> 00:03:51.980 align:start position:0% local etherium node although you can and if<00:03:50.010> you<00:03:50.100> are<00:03:50.280> it<00:03:50.340> will<00:03:50.400> talk<00:03:50.580> to<00:03:50.760> it<00:03:50.880> but<00:03:51.810> if<00:03:51.900> you 00:03:51.980 --> 00:03:51.990 align:start position:0% if you are it will talk to it but if you 00:03:51.990 --> 00:03:54.620 align:start position:0% if you are it will talk to it but if you aren't<00:03:52.200> it<00:03:52.470> talks<00:03:52.770> to<00:03:53.040> one<00:03:53.760> of<00:03:53.880> our<00:03:54.120> hosted 00:03:54.620 --> 00:03:54.630 align:start position:0% aren't it talks to one of our hosted 00:03:54.630 --> 00:03:57.050 align:start position:0% aren't it talks to one of our hosted nodes<00:03:55.160> so<00:03:56.160> I<00:03:56.190> have<00:03:56.310> to<00:03:56.370> do<00:03:56.460> is<00:03:56.550> go<00:03:56.610> to<00:03:56.670> client 00:03:57.050 --> 00:03:57.060 align:start position:0% nodes so I have to do is go to client 00:03:57.060 --> 00:04:01.700 align:start position:0% nodes so I have to do is go to client augur<00:03:58.050> at<00:03:58.440> and<00:04:00.170> you'll<00:04:01.170> be<00:04:01.290> presented<00:04:01.680> with 00:04:01.700 --> 00:04:01.710 align:start position:0% augur at and you'll be presented with 00:04:01.710 --> 00:04:06.470 align:start position:0% augur at and you'll be presented with our<00:04:02.070> interface<00:04:02.970> so<00:04:04.130> there's<00:04:05.130> three<00:04:05.820> trending 00:04:06.470 --> 00:04:06.480 align:start position:0% our interface so there's three trending 00:04:06.480 --> 00:04:08.570 align:start position:0% our interface so there's three trending markets<00:04:06.900> you<00:04:07.080> can<00:04:07.260> see<00:04:07.560> here<00:04:08.370> in<00:04:08.460> the<00:04:08.550> middle 00:04:08.570 --> 00:04:08.580 align:start position:0% markets you can see here in the middle 00:04:08.580 --> 00:04:15.849 align:start position:0% markets you can see here in the middle and<00:04:13.400> so<00:04:14.400> one<00:04:14.820> thing<00:04:14.850> we'll<00:04:15.090> notice<00:04:15.210> is<00:04:15.570> that 00:04:15.849 --> 00:04:15.859 align:start position:0% and so one thing we'll notice is that 00:04:15.859 --> 00:04:18.590 align:start position:0% and so one thing we'll notice is that there's<00:04:16.859> one<00:04:17.040> market<00:04:17.340> that<00:04:17.489> says<00:04:17.730> will<00:04:18.480> the 00:04:18.590 --> 00:04:18.600 align:start position:0% there's one market that says will the 00:04:18.600 --> 00:04:21.410 align:start position:0% there's one market that says will the Sun<00:04:18.810> turn<00:04:19.020> into<00:04:19.290> a<00:04:19.320> red<00:04:19.560> giant<00:04:19.770> and<00:04:20.299> engulf<00:04:21.299> the 00:04:21.410 --> 00:04:21.420 align:start position:0% Sun turn into a red giant and engulf the 00:04:21.420 --> 00:04:24.950 align:start position:0% Sun turn into a red giant and engulf the earth<00:04:21.450> by<00:04:21.840> the<00:04:21.900> end<00:04:22.140> of<00:04:22.260> 2015<00:04:22.530> and<00:04:23.450> it<00:04:24.450> sits<00:04:24.750> at 00:04:24.950 --> 00:04:24.960 align:start position:0% earth by the end of 2015 and it sits at 00:04:24.960 --> 00:04:26.380 align:start position:0% earth by the end of 2015 and it sits at 18% 00:04:26.380 --> 00:04:26.390 align:start position:0% 18% 00:04:26.390 --> 00:04:29.300 align:start position:0% 18% so<00:04:27.390> now<00:04:27.510> that<00:04:27.630> seems<00:04:27.900> maybe<00:04:28.170> well<00:04:28.950> that<00:04:29.160> seems 00:04:29.300 --> 00:04:29.310 align:start position:0% so now that seems maybe well that seems 00:04:29.310 --> 00:04:31.940 align:start position:0% so now that seems maybe well that seems maybe<00:04:29.460> a<00:04:29.580> little<00:04:29.760> high<00:04:29.910> right<00:04:30.210> because<00:04:30.720> I<00:04:31.110> mean 00:04:31.940 --> 00:04:31.950 align:start position:0% maybe a little high right because I mean 00:04:31.950 --> 00:04:33.440 align:start position:0% maybe a little high right because I mean the<00:04:32.100> Sun<00:04:32.310> is<00:04:32.520> probably<00:04:32.880> not<00:04:33.060> going<00:04:33.300> to<00:04:33.360> turn 00:04:33.440 --> 00:04:33.450 align:start position:0% the Sun is probably not going to turn 00:04:33.450 --> 00:04:34.940 align:start position:0% the Sun is probably not going to turn into<00:04:33.630> a<00:04:33.720> red<00:04:33.870> giant<00:04:34.050> and<00:04:34.230> engulf<00:04:34.500> the<00:04:34.650> earth<00:04:34.680> by 00:04:34.940 --> 00:04:34.950 align:start position:0% into a red giant and engulf the earth by 00:04:34.950 --> 00:04:37.670 align:start position:0% into a red giant and engulf the earth by the<00:04:35.010> end<00:04:35.400> of<00:04:35.490> 2015<00:04:35.820> so<00:04:36.410> we<00:04:37.410> could<00:04:37.560> probably 00:04:37.670 --> 00:04:37.680 align:start position:0% the end of 2015 so we could probably 00:04:37.680 --> 00:04:40.250 align:start position:0% the end of 2015 so we could probably make<00:04:37.980> some<00:04:38.190> money<00:04:38.310> off<00:04:38.460> that<00:04:38.700> because<00:04:39.260> the 00:04:40.250 --> 00:04:40.260 align:start position:0% make some money off that because the 00:04:40.260 --> 00:04:41.900 align:start position:0% make some money off that because the this<00:04:40.920> says<00:04:41.100> of<00:04:41.250> them<00:04:41.370> in<00:04:41.490> the<00:04:41.610> market<00:04:41.850> price 00:04:41.900 --> 00:04:41.910 align:start position:0% this says of them in the market price 00:04:41.910 --> 00:04:43.520 align:start position:0% this says of them in the market price there's<00:04:42.390> an<00:04:42.480> 18<00:04:42.810> percent<00:04:42.960> chance<00:04:43.350> of<00:04:43.440> that 00:04:43.520 --> 00:04:43.530 align:start position:0% there's an 18 percent chance of that 00:04:43.530 --> 00:04:46.390 align:start position:0% there's an 18 percent chance of that happening<00:04:44.090> so 00:04:46.390 --> 00:04:46.400 align:start position:0% happening so 00:04:46.400 --> 00:04:48.740 align:start position:0% happening so so<00:04:47.400> we<00:04:47.490> need<00:04:47.849> to<00:04:47.909> create<00:04:48.060> an<00:04:48.210> account<00:04:48.419> to<00:04:48.569> do 00:04:48.740 --> 00:04:48.750 align:start position:0% so we need to create an account to do 00:04:48.750 --> 00:04:50.649 align:start position:0% so we need to create an account to do that<00:04:48.900> now<00:04:49.349> you<00:04:49.409> so<00:04:50.159> you<00:04:50.220> can<00:04:50.430> use<00:04:50.610> your 00:04:50.649 --> 00:04:50.659 align:start position:0% that now you so you can use your 00:04:50.659 --> 00:04:52.790 align:start position:0% that now you so you can use your existing<00:04:51.659> etherium<00:04:52.110> accounts<00:04:52.470> you<00:04:52.560> can<00:04:52.650> use 00:04:52.790 --> 00:04:52.800 align:start position:0% existing etherium accounts you can use 00:04:52.800 --> 00:04:55.700 align:start position:0% existing etherium accounts you can use this<00:04:52.949> using<00:04:53.159> a<00:04:53.490> local<00:04:53.759> node<00:04:54.289> in<00:04:55.289> which<00:04:55.530> case 00:04:55.700 --> 00:04:55.710 align:start position:0% this using a local node in which case 00:04:55.710 --> 00:04:57.409 align:start position:0% this using a local node in which case it'll<00:04:55.919> just<00:04:56.159> automatically<00:04:56.879> connect<00:04:57.240> to<00:04:57.300> your 00:04:57.409 --> 00:04:57.419 align:start position:0% it'll just automatically connect to your 00:04:57.419 --> 00:05:00.589 align:start position:0% it'll just automatically connect to your account<00:04:57.719> by<00:04:58.469> talking<00:04:58.860> to<00:04:59.150> by<00:05:00.150> talking<00:05:00.449> to<00:05:00.479> the 00:05:00.589 --> 00:05:00.599 align:start position:0% account by talking to by talking to the 00:05:00.599 --> 00:05:03.890 align:start position:0% account by talking to by talking to the node<00:05:00.750> by<00:05:00.900> talking<00:05:01.169> together<00:05:02.300> or<00:05:03.300> you<00:05:03.629> can 00:05:03.890 --> 00:05:03.900 align:start position:0% node by talking together or you can 00:05:03.900 --> 00:05:07.450 align:start position:0% node by talking together or you can create<00:05:04.650> an<00:05:04.770> account<00:05:04.860> using<00:05:05.189> our<00:05:05.400> system<00:05:05.960> and 00:05:07.450 --> 00:05:07.460 align:start position:0% create an account using our system and 00:05:07.460 --> 00:05:09.589 align:start position:0% create an account using our system and so<00:05:08.460> you'll<00:05:08.759> notice<00:05:08.789> in<00:05:09.090> the<00:05:09.180> top<00:05:09.389> right<00:05:09.569> hand 00:05:09.589 --> 00:05:09.599 align:start position:0% so you'll notice in the top right hand 00:05:09.599 --> 00:05:11.420 align:start position:0% so you'll notice in the top right hand corner<00:05:09.810> we<00:05:10.169> have<00:05:10.319> sign<00:05:10.710> in<00:05:10.919> and<00:05:11.159> register 00:05:11.420 --> 00:05:11.430 align:start position:0% corner we have sign in and register 00:05:11.430 --> 00:05:13.939 align:start position:0% corner we have sign in and register buttons<00:05:12.060> so<00:05:12.479> again<00:05:13.169> looks<00:05:13.409> very<00:05:13.680> much<00:05:13.770> like<00:05:13.800> a 00:05:13.939 --> 00:05:13.949 align:start position:0% buttons so again looks very much like a 00:05:13.949 --> 00:05:17.480 align:start position:0% buttons so again looks very much like a regular<00:05:14.280> website<00:05:14.479> so<00:05:16.099> if<00:05:17.099> you<00:05:17.250> click<00:05:17.370> on 00:05:17.480 --> 00:05:17.490 align:start position:0% regular website so if you click on 00:05:17.490 --> 00:05:20.089 align:start position:0% regular website so if you click on register<00:05:18.349> well<00:05:19.349> I'm<00:05:19.409> gonna<00:05:19.530> I'm<00:05:19.830> gonna<00:05:19.889> walk 00:05:20.089 --> 00:05:20.099 align:start position:0% register well I'm gonna I'm gonna walk 00:05:20.099 --> 00:05:21.409 align:start position:0% register well I'm gonna I'm gonna walk you<00:05:20.250> through<00:05:20.280> the<00:05:20.580> steps<00:05:20.940> of<00:05:21.030> what<00:05:21.090> happens 00:05:21.409 --> 00:05:21.419 align:start position:0% you through the steps of what happens 00:05:21.419 --> 00:05:22.430 align:start position:0% you through the steps of what happens after<00:05:21.599> you<00:05:21.629> click<00:05:21.810> on<00:05:21.960> it<00:05:22.050> so<00:05:22.139> you<00:05:22.199> click<00:05:22.319> on 00:05:22.430 --> 00:05:22.440 align:start position:0% after you click on it so you click on 00:05:22.440 --> 00:05:26.209 align:start position:0% after you click on it so you click on register<00:05:22.500> and<00:05:24.199> type<00:05:25.199> in<00:05:25.349> your<00:05:25.500> username<00:05:25.889> and 00:05:26.209 --> 00:05:26.219 align:start position:0% register and type in your username and 00:05:26.219 --> 00:05:29.950 align:start position:0% register and type in your username and password<00:05:26.490> and<00:05:28.129> I've<00:05:29.129> got<00:05:29.250> the<00:05:29.370> two<00:05:29.490> inputs 00:05:29.950 --> 00:05:29.960 align:start position:0% password and I've got the two inputs 00:05:29.960 --> 00:05:33.260 align:start position:0% password and I've got the two inputs there<00:05:30.960> you'll<00:05:31.080> see<00:05:31.199> whether<00:05:31.349> like<00:05:31.560> that<00:05:32.270> and 00:05:33.260 --> 00:05:33.270 align:start position:0% there you'll see whether like that and 00:05:33.270 --> 00:05:35.930 align:start position:0% there you'll see whether like that and through<00:05:34.229> May<00:05:34.379> we<00:05:34.530> made<00:05:34.710> a<00:05:34.740> tool<00:05:35.370> called<00:05:35.610> which 00:05:35.930 --> 00:05:35.940 align:start position:0% through May we made a tool called which 00:05:35.940 --> 00:05:38.149 align:start position:0% through May we made a tool called which we<00:05:36.060> called<00:05:36.240> key<00:05:36.810> theorem<00:05:37.110> we're<00:05:37.770> fairly<00:05:37.949> proud 00:05:38.149 --> 00:05:38.159 align:start position:0% we called key theorem we're fairly proud 00:05:38.159 --> 00:05:40.550 align:start position:0% we called key theorem we're fairly proud of<00:05:38.279> that<00:05:38.340> name<00:05:38.539> and<00:05:39.539> it's<00:05:40.020> basically<00:05:40.289> just<00:05:40.409> the 00:05:40.550 --> 00:05:40.560 align:start position:0% of that name and it's basically just the 00:05:40.560 --> 00:05:42.769 align:start position:0% of that name and it's basically just the key<00:05:40.770> man<00:05:40.919> it's<00:05:41.340> a<00:05:41.460> standalone<00:05:41.969> JavaScript<00:05:42.629> key 00:05:42.769 --> 00:05:42.779 align:start position:0% key man it's a standalone JavaScript key 00:05:42.779 --> 00:05:45.439 align:start position:0% key man it's a standalone JavaScript key management<00:05:43.199> tool<00:05:43.349> for<00:05:44.000> etherium<00:05:45.029> and<00:05:45.180> what<00:05:45.360> it 00:05:45.439 --> 00:05:45.449 align:start position:0% management tool for etherium and what it 00:05:45.449 --> 00:05:49.580 align:start position:0% management tool for etherium and what it does<00:05:45.629> is<00:05:45.889> it<00:05:46.889> is<00:05:47.699> it's<00:05:48.509> it's<00:05:48.870> JavaScript<00:05:49.439> code 00:05:49.580 --> 00:05:49.590 align:start position:0% does is it is it's it's JavaScript code 00:05:49.590 --> 00:05:53.119 align:start position:0% does is it is it's it's JavaScript code that<00:05:49.620> creates<00:05:50.279> the<00:05:51.259> the<00:05:52.259> same<00:05:52.469> key<00:05:52.680> store<00:05:52.979> or 00:05:53.119 --> 00:05:53.129 align:start position:0% that creates the the same key store or 00:05:53.129 --> 00:05:56.540 align:start position:0% that creates the the same key store or files<00:05:53.370> that<00:05:53.610> get<00:05:54.449> natively<00:05:55.020> uses<00:05:55.409> so<00:05:56.039> what 00:05:56.540 --> 00:05:56.550 align:start position:0% files that get natively uses so what 00:05:56.550 --> 00:06:00.529 align:start position:0% files that get natively uses so what happens<00:05:56.879> is<00:05:57.120> it<00:05:57.629> generates<00:05:58.169> a<00:05:59.389> private<00:06:00.389> key 00:06:00.529 --> 00:06:00.539 align:start position:0% happens is it generates a private key 00:06:00.539 --> 00:06:03.499 align:start position:0% happens is it generates a private key which<00:06:00.719> is<00:06:00.990> just<00:06:01.199> a<00:06:01.379> random<00:06:01.529> 256<00:06:02.339> bit<00:06:02.460> number<00:06:02.729> it 00:06:03.499 --> 00:06:03.509 align:start position:0% which is just a random 256 bit number it 00:06:03.509 --> 00:06:05.570 align:start position:0% which is just a random 256 bit number it also<00:06:03.629> generates<00:06:04.169> random<00:06:04.949> salt<00:06:05.370> and 00:06:05.570 --> 00:06:05.580 align:start position:0% also generates random salt and 00:06:05.580 --> 00:06:08.329 align:start position:0% also generates random salt and neutralization<00:06:06.180> initialization<00:06:07.169> vector 00:06:08.329 --> 00:06:08.339 align:start position:0% neutralization initialization vector 00:06:08.339 --> 00:06:12.079 align:start position:0% neutralization initialization vector puts<00:06:08.940> those<00:06:09.060> through<00:06:09.560> it<00:06:10.560> puts<00:06:10.740> the<00:06:11.089> password 00:06:12.079 --> 00:06:12.089 align:start position:0% puts those through it puts the password 00:06:12.089 --> 00:06:16.300 align:start position:0% puts those through it puts the password and<00:06:12.360> the<00:06:12.690> salt<00:06:12.960> through<00:06:13.589> I<00:06:14.219> think<00:06:15.210> we're<00:06:15.300> using 00:06:16.300 --> 00:06:16.310 align:start position:0% and the salt through I think we're using 00:06:16.310 --> 00:06:19.820 align:start position:0% and the salt through I think we're using 10,000<00:06:17.310> rounds<00:06:17.400> a<00:06:17.699> script<00:06:18.409> to<00:06:19.409> generate<00:06:19.740> an 00:06:19.820 --> 00:06:19.830 align:start position:0% 10,000 rounds a script to generate an 00:06:19.830 --> 00:06:24.709 align:start position:0% 10,000 rounds a script to generate an encryption<00:06:20.159> key<00:06:20.400> and<00:06:22.099> this<00:06:23.099> so<00:06:24.089> this<00:06:24.509> is<00:06:24.569> a 00:06:24.709 --> 00:06:24.719 align:start position:0% encryption key and this so this is a 00:06:24.719 --> 00:06:26.240 align:start position:0% encryption key and this so this is a symmetric<00:06:24.990> encryption<00:06:25.349> key<00:06:25.800> and<00:06:25.919> it's<00:06:26.039> used 00:06:26.240 --> 00:06:26.250 align:start position:0% symmetric encryption key and it's used 00:06:26.250 --> 00:06:30.589 align:start position:0% symmetric encryption key and it's used to<00:06:27.169> it's<00:06:28.169> used<00:06:28.319> to<00:06:28.469> encrypt<00:06:28.889> the<00:06:29.599> plaintext 00:06:30.589 --> 00:06:30.599 align:start position:0% to it's used to encrypt the plaintext 00:06:30.599 --> 00:06:32.420 align:start position:0% to it's used to encrypt the plaintext private<00:06:31.169> key<00:06:31.319> so<00:06:31.469> this<00:06:31.620> is<00:06:31.740> this<00:06:32.039> is<00:06:32.129> your<00:06:32.250> new 00:06:32.420 --> 00:06:32.430 align:start position:0% private key so this is this is your new 00:06:32.430 --> 00:06:36.740 align:start position:0% private key so this is this is your new accounts<00:06:32.940> private<00:06:33.360> key<00:06:33.949> and<00:06:34.949> we<00:06:35.909> and<00:06:36.240> we<00:06:36.629> do 00:06:36.740 --> 00:06:36.750 align:start position:0% accounts private key and we and we do 00:06:36.750 --> 00:06:39.920 align:start position:0% accounts private key and we and we do the<00:06:36.870> encryption<00:06:37.050> using<00:06:37.680> AES<00:06:38.639> 128<00:06:39.210> which<00:06:39.779> is 00:06:39.920 --> 00:06:39.930 align:start position:0% the encryption using AES 128 which is 00:06:39.930 --> 00:06:44.480 align:start position:0% the encryption using AES 128 which is just<00:06:40.409> a<00:06:40.469> strong<00:06:40.710> symmetric<00:06:41.190> cipher<00:06:41.550> and<00:06:43.490> so 00:06:44.480 --> 00:06:44.490 align:start position:0% just a strong symmetric cipher and so 00:06:44.490 --> 00:06:47.149 align:start position:0% just a strong symmetric cipher and so one<00:06:45.229> one<00:06:46.229> interesting<00:06:46.650> thing<00:06:46.680> here<00:06:47.039> is<00:06:47.129> that 00:06:47.149 --> 00:06:47.159 align:start position:0% one one interesting thing here is that 00:06:47.159 --> 00:06:50.959 align:start position:0% one one interesting thing here is that this<00:06:47.819> is<00:06:48.349> by<00:06:49.349> design<00:06:49.560> the<00:06:50.009> exact<00:06:50.310> same<00:06:50.490> process 00:06:50.959 --> 00:06:50.969 align:start position:0% this is by design the exact same process 00:06:50.969 --> 00:06:55.170 align:start position:0% this is by design the exact same process that<00:06:51.319> that<00:06:52.319> get<00:06:52.529> uses<00:06:52.919> right<00:06:53.639> and 00:06:55.170 --> 00:06:55.180 align:start position:0% that that get uses right and 00:06:55.180 --> 00:06:57.930 align:start position:0% that that get uses right and that<00:06:55.900> means<00:06:56.139> that<00:06:56.500> this<00:06:57.039> encrypted<00:06:57.610> private 00:06:57.930 --> 00:06:57.940 align:start position:0% that means that this encrypted private 00:06:57.940 --> 00:07:02.550 align:start position:0% that means that this encrypted private key<00:06:58.090> and<00:06:58.650> the<00:06:59.650> the<00:07:00.460> JSON<00:07:01.240> file<00:07:02.020> that<00:07:02.050> can<00:07:02.440> be 00:07:02.550 --> 00:07:02.560 align:start position:0% key and the the JSON file that can be 00:07:02.560 --> 00:07:04.529 align:start position:0% key and the the JSON file that can be exported<00:07:02.889> from<00:07:03.130> this<00:07:03.340> can<00:07:03.940> just<00:07:04.150> be<00:07:04.270> used 00:07:04.529 --> 00:07:04.539 align:start position:0% exported from this can just be used 00:07:04.539 --> 00:07:09.629 align:start position:0% exported from this can just be used natively<00:07:05.199> in<00:07:05.800> Gath<00:07:06.130> and<00:07:07.830> so<00:07:08.830> you<00:07:08.889> actually<00:07:09.460> can 00:07:09.629 --> 00:07:09.639 align:start position:0% natively in Gath and so you actually can 00:07:09.639 --> 00:07:11.670 align:start position:0% natively in Gath and so you actually can export<00:07:10.240> this<00:07:10.449> and<00:07:10.660> just<00:07:10.840> copy<00:07:11.259> it<00:07:11.410> into<00:07:11.560> your 00:07:11.670 --> 00:07:11.680 align:start position:0% export this and just copy it into your 00:07:11.680 --> 00:07:13.170 align:start position:0% export this and just copy it into your key<00:07:11.800> store<00:07:12.009> directory<00:07:12.370> and<00:07:12.580> you<00:07:12.699> can<00:07:12.850> just<00:07:13.000> you 00:07:13.170 --> 00:07:13.180 align:start position:0% key store directory and you can just you 00:07:13.180 --> 00:07:14.610 align:start position:0% key store directory and you can just you can<00:07:13.300> use<00:07:13.330> it<00:07:13.570> you<00:07:13.720> can<00:07:13.750> you'll<00:07:14.080> even<00:07:14.229> use<00:07:14.440> the 00:07:14.610 --> 00:07:14.620 align:start position:0% can use it you can you'll even use the 00:07:14.620 --> 00:07:16.950 align:start position:0% can use it you can you'll even use the same<00:07:14.770> password<00:07:15.370> because<00:07:15.669> it<00:07:15.820> knows<00:07:16.780> how<00:07:16.930> to 00:07:16.950 --> 00:07:16.960 align:start position:0% same password because it knows how to 00:07:16.960 --> 00:07:19.379 align:start position:0% same password because it knows how to read<00:07:17.259> the<00:07:17.580> encryption<00:07:18.580> parameters<00:07:19.000> right<00:07:19.240> out 00:07:19.379 --> 00:07:19.389 align:start position:0% read the encryption parameters right out 00:07:19.389 --> 00:07:23.779 align:start position:0% read the encryption parameters right out of<00:07:19.419> this<00:07:19.570> file<00:07:20.759> now<00:07:21.759> what<00:07:22.150> happens<00:07:22.479> with<00:07:22.630> this 00:07:23.779 --> 00:07:23.789 align:start position:0% of this file now what happens with this 00:07:23.789 --> 00:07:28.740 align:start position:0% of this file now what happens with this encrypted<00:07:24.930> JSON<00:07:25.930> file<00:07:26.139> is<00:07:26.940> we<00:07:27.940> store<00:07:28.419> it<00:07:28.539> in 00:07:28.740 --> 00:07:28.750 align:start position:0% encrypted JSON file is we store it in 00:07:28.750 --> 00:07:34.710 align:start position:0% encrypted JSON file is we store it in ipfs<00:07:29.440> and<00:07:31.080> this<00:07:32.080> so<00:07:32.470> this<00:07:32.500> file<00:07:32.919> is<00:07:33.389> assigned<00:07:34.389> a 00:07:34.710 --> 00:07:34.720 align:start position:0% ipfs and this so this file is assigned a 00:07:34.720 --> 00:07:37.170 align:start position:0% ipfs and this so this file is assigned a hash<00:07:35.020> by<00:07:35.380> ipfs<00:07:36.039> according<00:07:36.460> to<00:07:36.550> the<00:07:36.669> data<00:07:37.030> in 00:07:37.170 --> 00:07:37.180 align:start position:0% hash by ipfs according to the data in 00:07:37.180 --> 00:07:41.249 align:start position:0% hash by ipfs according to the data in the<00:07:37.240> file<00:07:37.419> and<00:07:39.630> because<00:07:40.630> we<00:07:40.930> want<00:07:41.169> to 00:07:41.249 --> 00:07:41.259 align:start position:0% the file and because we want to 00:07:41.259 --> 00:07:43.170 align:start position:0% the file and because we want to associate<00:07:41.860> this<00:07:42.160> data<00:07:42.400> with<00:07:42.669> a<00:07:42.699> username 00:07:43.170 --> 00:07:43.180 align:start position:0% associate this data with a username 00:07:43.180 --> 00:07:45.210 align:start position:0% associate this data with a username which<00:07:43.900> is<00:07:44.020> sort<00:07:44.320> of<00:07:44.410> an<00:07:44.470> arbitrary<00:07:44.650> string 00:07:45.210 --> 00:07:45.220 align:start position:0% which is sort of an arbitrary string 00:07:45.220 --> 00:07:48.600 align:start position:0% which is sort of an arbitrary string rather<00:07:45.490> than<00:07:45.910> the<00:07:46.210> ipfs<00:07:46.690> hash<00:07:46.900> which<00:07:47.560> is<00:07:47.770> you 00:07:48.600 --> 00:07:48.610 align:start position:0% rather than the ipfs hash which is you 00:07:48.610 --> 00:07:50.370 align:start position:0% rather than the ipfs hash which is you know<00:07:48.699> it's<00:07:48.820> sort<00:07:48.940> of<00:07:48.970> a<00:07:49.030> hard<00:07:49.210> to<00:07:49.330> remember<00:07:49.570> 256 00:07:50.370 --> 00:07:50.380 align:start position:0% know it's sort of a hard to remember 256 00:07:50.380 --> 00:07:53.730 align:start position:0% know it's sort of a hard to remember 256 bit<00:07:50.530> number<00:07:51.570> what<00:07:52.570> we<00:07:52.780> do<00:07:52.900> is<00:07:53.020> we<00:07:53.169> have<00:07:53.320> well<00:07:53.650> we 00:07:53.730 --> 00:07:53.740 align:start position:0% bit number what we do is we have well we 00:07:53.740 --> 00:07:56.930 align:start position:0% bit number what we do is we have well we have<00:07:53.830> an<00:07:53.919> etherium<00:07:54.340> contract<00:07:54.820> that<00:07:55.330> is<00:07:55.710> just 00:07:56.930 --> 00:07:56.940 align:start position:0% have an etherium contract that is just 00:07:56.940 --> 00:08:00.089 align:start position:0% have an etherium contract that is just it<00:07:57.940> Maps<00:07:58.270> the<00:07:58.870> username<00:07:59.349> that<00:07:59.380> the<00:07:59.680> user<00:07:59.830> typed 00:08:00.089 --> 00:08:00.099 align:start position:0% it Maps the username that the user typed 00:08:00.099 --> 00:08:07.320 align:start position:0% it Maps the username that the user typed in<00:08:00.960> onto<00:08:01.960> the<00:08:02.289> ipfs<00:08:02.860> hash<00:08:04.770> and<00:08:06.030> their<00:08:07.030> way 00:08:07.320 --> 00:08:07.330 align:start position:0% in onto the ipfs hash and their way 00:08:07.330 --> 00:08:08.969 align:start position:0% in onto the ipfs hash and their way think<00:08:07.510> if<00:08:07.599> I've<00:08:07.690> been<00:08:07.840> at<00:08:07.930> at<00:08:08.169> me<00:08:08.260> so<00:08:08.440> I<00:08:08.620> need<00:08:08.830> to 00:08:08.969 --> 00:08:08.979 align:start position:0% think if I've been at at me so I need to 00:08:08.979 --> 00:08:11.490 align:start position:0% think if I've been at at me so I need to move<00:08:09.190> faster<00:08:09.520> and<00:08:09.699> so<00:08:10.539> one<00:08:11.020> thing<00:08:11.050> I<00:08:11.260> want<00:08:11.440> to 00:08:11.490 --> 00:08:11.500 align:start position:0% move faster and so one thing I want to 00:08:11.500 --> 00:08:15.240 align:start position:0% move faster and so one thing I want to comment<00:08:11.650> about<00:08:11.830> this<00:08:12.099> is<00:08:12.400> that<00:08:13.050> because<00:08:14.250> when 00:08:15.240 --> 00:08:15.250 align:start position:0% comment about this is that because when 00:08:15.250 --> 00:08:18.480 align:start position:0% comment about this is that because when you<00:08:15.340> look<00:08:15.460> up<00:08:15.610> the<00:08:15.639> hash<00:08:15.909> it<00:08:16.330> is<00:08:17.280> broadcast<00:08:18.280> to 00:08:18.480 --> 00:08:18.490 align:start position:0% you look up the hash it is broadcast to 00:08:18.490 --> 00:08:21.029 align:start position:0% you look up the hash it is broadcast to the<00:08:18.820> DHT<00:08:19.060> and<00:08:19.389> ipfs<00:08:19.900> this<00:08:20.229> is<00:08:20.380> not<00:08:20.530> as<00:08:20.680> secure 00:08:21.029 --> 00:08:21.039 align:start position:0% the DHT and ipfs this is not as secure 00:08:21.039 --> 00:08:26.310 align:start position:0% the DHT and ipfs this is not as secure as<00:08:21.190> it<00:08:21.310> could<00:08:21.460> be<00:08:21.610> and<00:08:23.009> I'm<00:08:24.009> talking<00:08:24.699> to<00:08:24.909> one<00:08:25.870> I 00:08:26.310 --> 00:08:26.320 align:start position:0% as it could be and I'm talking to one I 00:08:26.320 --> 00:08:29.520 align:start position:0% as it could be and I'm talking to one I P<00:08:26.530> FS<00:08:26.800> guy<00:08:26.979> about<00:08:27.490> this<00:08:27.699> and<00:08:28.020> we<00:08:29.020> are<00:08:29.199> because 00:08:29.520 --> 00:08:29.530 align:start position:0% P FS guy about this and we are because 00:08:29.530 --> 00:08:30.480 align:start position:0% P FS guy about this and we are because of<00:08:29.650> this<00:08:29.740> we're<00:08:29.889> going<00:08:30.039> to<00:08:30.130> also<00:08:30.250> have<00:08:30.400> an 00:08:30.480 --> 00:08:30.490 align:start position:0% of this we're going to also have an 00:08:30.490 --> 00:08:31.920 align:start position:0% of this we're going to also have an option<00:08:30.759> of<00:08:30.849> just<00:08:31.000> storing<00:08:31.599> it<00:08:31.690> in<00:08:31.780> local 00:08:31.920 --> 00:08:31.930 align:start position:0% option of just storing it in local 00:08:31.930 --> 00:08:36.300 align:start position:0% option of just storing it in local storage<00:08:32.700> okay<00:08:33.700> and<00:08:34.060> so<00:08:34.180> the<00:08:34.959> the<00:08:35.860> converse<00:08:36.190> of 00:08:36.300 --> 00:08:36.310 align:start position:0% storage okay and so the the converse of 00:08:36.310 --> 00:08:39.659 align:start position:0% storage okay and so the the converse of this<00:08:36.459> is<00:08:36.640> when<00:08:37.209> you<00:08:37.630> log<00:08:37.930> in<00:08:38.200> you<00:08:39.159> supply<00:08:39.640> a 00:08:39.659 --> 00:08:39.669 align:start position:0% this is when you log in you supply a 00:08:39.669 --> 00:08:41.760 align:start position:0% this is when you log in you supply a username<00:08:39.940> and<00:08:40.329> password<00:08:40.390> is<00:08:41.140> sort<00:08:41.589> of<00:08:41.650> the 00:08:41.760 --> 00:08:41.770 align:start position:0% username and password is sort of the 00:08:41.770 --> 00:08:43.050 align:start position:0% username and password is sort of the reverse<00:08:41.890> of<00:08:42.130> this<00:08:42.250> magic<00:08:42.610> happens<00:08:42.909> you<00:08:43.029> have 00:08:43.050 --> 00:08:43.060 align:start position:0% reverse of this magic happens you have 00:08:43.060 --> 00:08:45.329 align:start position:0% reverse of this magic happens you have the<00:08:43.329> decrypted<00:08:44.260> private<00:08:44.589> key<00:08:44.709> which<00:08:44.920> you<00:08:45.160> can 00:08:45.329 --> 00:08:45.339 align:start position:0% the decrypted private key which you can 00:08:45.339 --> 00:08:48.530 align:start position:0% the decrypted private key which you can use<00:08:45.520> to<00:08:45.790> sign<00:08:46.450> transactions<00:08:47.170> in<00:08:47.380> the<00:08:47.500> browser 00:08:48.530 --> 00:08:48.540 align:start position:0% use to sign transactions in the browser 00:08:48.540 --> 00:08:55.740 align:start position:0% use to sign transactions in the browser using<00:08:49.540> the<00:08:50.350> etherium<00:08:51.040> J<00:08:51.339> s<00:08:51.630> TX<00:08:52.630> library<00:08:53.350> and<00:08:54.750> so 00:08:55.740 --> 00:08:55.750 align:start position:0% using the etherium J s TX library and so 00:08:55.750 --> 00:08:58.310 align:start position:0% using the etherium J s TX library and so we<00:08:56.320> so<00:08:56.649> we<00:08:56.680> registered<00:08:56.920> for<00:08:57.190> an<00:08:57.399> account 00:08:58.310 --> 00:08:58.320 align:start position:0% we so we registered for an account 00:08:58.320 --> 00:09:01.629 align:start position:0% we so we registered for an account and<00:08:58.790> because<00:08:59.790> right<00:09:00.060> now<00:09:00.480> we're<00:09:00.690> on<00:09:00.870> just<00:09:01.380> the 00:09:01.629 --> 00:09:01.639 align:start position:0% and because right now we're on just the 00:09:01.639 --> 00:09:05.870 align:start position:0% and because right now we're on just the augur<00:09:02.639> private<00:09:03.089> chain<00:09:03.329> while<00:09:03.810> we<00:09:03.990> test<00:09:04.880> we 00:09:05.870 --> 00:09:05.880 align:start position:0% augur private chain while we test we 00:09:05.880 --> 00:09:07.670 align:start position:0% augur private chain while we test we give<00:09:06.060> all<00:09:06.209> new<00:09:06.329> accounts<00:09:06.720> just<00:09:06.899> 100<00:09:07.440> free 00:09:07.670 --> 00:09:07.680 align:start position:0% give all new accounts just 100 free 00:09:07.680 --> 00:09:10.430 align:start position:0% give all new accounts just 100 free ether<00:09:07.980> it's<00:09:08.279> not<00:09:08.430> real<00:09:08.639> either<00:09:08.759> so<00:09:09.300> I<00:09:09.600> got<00:09:10.259> my 00:09:10.430 --> 00:09:10.440 align:start position:0% ether it's not real either so I got my 00:09:10.440 --> 00:09:15.019 align:start position:0% ether it's not real either so I got my hundred<00:09:10.920> free<00:09:11.100> either<00:09:11.220> and<00:09:12.350> you<00:09:13.350> can<00:09:13.790> use<00:09:14.790> the 00:09:15.019 --> 00:09:15.029 align:start position:0% hundred free either and you can use the 00:09:15.029 --> 00:09:17.569 align:start position:0% hundred free either and you can use the faucets<00:09:15.480> to<00:09:15.660> get<00:09:15.810> cash<00:09:16.139> and<00:09:16.560> reputation<00:09:17.160> so 00:09:17.569 --> 00:09:17.579 align:start position:0% faucets to get cash and reputation so 00:09:17.579 --> 00:09:20.300 align:start position:0% faucets to get cash and reputation so you<00:09:17.670> actually<00:09:17.819> place<00:09:18.149> bets<00:09:18.449> in<00:09:19.310> the 00:09:20.300 --> 00:09:20.310 align:start position:0% you actually place bets in the 00:09:20.310 --> 00:09:22.670 align:start position:0% you actually place bets in the prediction<00:09:20.639> markets<00:09:20.970> using<00:09:21.089> using<00:09:21.779> cash<00:09:22.019> and 00:09:22.670 --> 00:09:22.680 align:start position:0% prediction markets using using cash and 00:09:22.680 --> 00:09:24.470 align:start position:0% prediction markets using using cash and so<00:09:23.399> now<00:09:23.550> we're<00:09:23.670> finally<00:09:23.940> at<00:09:23.970> the<00:09:24.089> point<00:09:24.120> where 00:09:24.470 --> 00:09:24.480 align:start position:0% so now we're finally at the point where 00:09:24.480 --> 00:09:27.800 align:start position:0% so now we're finally at the point where we<00:09:24.660> can<00:09:24.839> bet<00:09:25.050> on<00:09:25.579> this<00:09:26.579> absurd<00:09:27.089> event<00:09:27.389> and<00:09:27.600> as 00:09:27.800 --> 00:09:27.810 align:start position:0% we can bet on this absurd event and as 00:09:27.810 --> 00:09:34.460 align:start position:0% we can bet on this absurd event and as the<00:09:27.930> comment<00:09:28.259> says<00:09:28.410> Yahoo<00:09:30.050> so<00:09:33.259> yeah<00:09:34.259> so<00:09:34.380> you 00:09:34.460 --> 00:09:34.470 align:start position:0% the comment says Yahoo so yeah so you 00:09:34.470 --> 00:09:36.590 align:start position:0% the comment says Yahoo so yeah so you can<00:09:34.589> see<00:09:34.649> we<00:09:34.769> have<00:09:34.889> like<00:09:35.009> a<00:09:35.040> price<00:09:35.970> series<00:09:36.360> and 00:09:36.590 --> 00:09:36.600 align:start position:0% can see we have like a price series and 00:09:36.600 --> 00:09:38.120 align:start position:0% can see we have like a price series and comments<00:09:37.350> comments<00:09:37.680> are<00:09:37.769> still<00:09:37.920> a<00:09:37.949> little 00:09:38.120 --> 00:09:38.130 align:start position:0% comments comments are still a little 00:09:38.130 --> 00:09:43.160 align:start position:0% comments comments are still a little finicky<00:09:38.310> right<00:09:38.550> now<00:09:39.290> and<00:09:41.720> so<00:09:42.720> we<00:09:42.750> want<00:09:43.019> we<00:09:43.139> want 00:09:43.160 --> 00:09:43.170 align:start position:0% finicky right now and so we want we want 00:09:43.170 --> 00:09:44.689 align:start position:0% finicky right now and so we want we want a<00:09:43.350> bet<00:09:43.470> on<00:09:43.500> no<00:09:43.769> right<00:09:43.980> because<00:09:44.160> we<00:09:44.370> think<00:09:44.519> that 00:09:44.689 --> 00:09:44.699 align:start position:0% a bet on no right because we think that 00:09:44.699 --> 00:09:46.850 align:start position:0% a bet on no right because we think that man<00:09:44.880> this<00:09:45.000> is<00:09:45.180> this<00:09:45.360> is<00:09:45.540> really<00:09:45.810> under<00:09:46.649> price 00:09:46.850 --> 00:09:46.860 align:start position:0% man this is this is really under price 00:09:46.860 --> 00:09:48.379 align:start position:0% man this is this is really under price given<00:09:47.250> that<00:09:47.370> we<00:09:47.459> know<00:09:47.790> this<00:09:47.970> isn't<00:09:48.240> going<00:09:48.329> to 00:09:48.379 --> 00:09:48.389 align:start position:0% given that we know this isn't going to 00:09:48.389 --> 00:09:51.499 align:start position:0% given that we know this isn't going to happen<00:09:48.509> so<00:09:49.730> I'm<00:09:50.730> gonna<00:09:50.910> say<00:09:51.089> we're<00:09:51.209> gonna<00:09:51.269> buy 00:09:51.499 --> 00:09:51.509 align:start position:0% happen so I'm gonna say we're gonna buy 00:09:51.509 --> 00:09:54.620 align:start position:0% happen so I'm gonna say we're gonna buy 485<00:09:52.470> shares<00:09:53.399> of<00:09:53.699> no<00:09:53.910> this<00:09:54.180> will<00:09:54.300> bring<00:09:54.480> the 00:09:54.620 --> 00:09:54.630 align:start position:0% 485 shares of no this will bring the 00:09:54.630 --> 00:09:56.569 align:start position:0% 485 shares of no this will bring the probability<00:09:55.079> up<00:09:55.170> to<00:09:55.259> 100%<00:09:55.620> because<00:09:56.370> we<00:09:56.490> know 00:09:56.569 --> 00:09:56.579 align:start position:0% probability up to 100% because we know 00:09:56.579 --> 00:09:57.769 align:start position:0% probability up to 100% because we know this<00:09:56.670> isn't<00:09:56.910> gonna<00:09:57.000> happen<00:09:57.180> since<00:09:57.569> it's<00:09:57.690> all 00:09:57.769 --> 00:09:57.779 align:start position:0% this isn't gonna happen since it's all 00:09:57.779 --> 00:10:02.090 align:start position:0% this isn't gonna happen since it's all profit<00:09:58.199> and<00:09:58.970> click<00:09:59.970> buy<00:10:00.180> now<00:10:00.209> we<00:10:01.079> have<00:10:01.259> 485 00:10:02.090 --> 00:10:02.100 align:start position:0% profit and click buy now we have 485 00:10:02.100 --> 00:10:05.750 align:start position:0% profit and click buy now we have 485 shares<00:10:02.639> pending<00:10:03.230> about<00:10:04.230> 12<00:10:04.620> seconds<00:10:04.980> later<00:10:05.130> it 00:10:05.750 --> 00:10:05.760 align:start position:0% shares pending about 12 seconds later it 00:10:05.760 --> 00:10:07.730 align:start position:0% shares pending about 12 seconds later it clears<00:10:06.449> and<00:10:06.720> now<00:10:06.930> we<00:10:06.990> have<00:10:07.230> that<00:10:07.350> many<00:10:07.529> shares 00:10:07.730 --> 00:10:07.740 align:start position:0% clears and now we have that many shares 00:10:07.740 --> 00:10:09.590 align:start position:0% clears and now we have that many shares so<00:10:08.100> you<00:10:08.519> can<00:10:08.670> see<00:10:08.790> the<00:10:08.880> price<00:10:09.060> now<00:10:09.269> has<00:10:09.480> moved 00:10:09.590 --> 00:10:09.600 align:start position:0% so you can see the price now has moved 00:10:09.600 --> 00:10:14.150 align:start position:0% so you can see the price now has moved up<00:10:09.810> to<00:10:10.639> 100%<00:10:12.410> okay<00:10:13.410> so<00:10:13.470> what<00:10:13.680> just<00:10:13.860> happened 00:10:14.150 --> 00:10:14.160 align:start position:0% up to 100% okay so what just happened 00:10:14.160 --> 00:10:15.160 align:start position:0% up to 100% okay so what just happened here 00:10:15.160 --> 00:10:15.170 align:start position:0% here 00:10:15.170 --> 00:10:17.329 align:start position:0% here well<00:10:16.170> so<00:10:16.290> want<00:10:16.470> to<00:10:16.529> click<00:10:16.680> the<00:10:16.769> Buy<00:10:16.889> button<00:10:16.920> but 00:10:17.329 --> 00:10:17.339 align:start position:0% well so want to click the Buy button but 00:10:17.339 --> 00:10:18.110 align:start position:0% well so want to click the Buy button but what<00:10:17.430> happens<00:10:17.699> after<00:10:17.940> that 00:10:18.110 --> 00:10:18.120 align:start position:0% what happens after that 00:10:18.120 --> 00:10:21.230 align:start position:0% what happens after that so<00:10:18.269> the<00:10:18.630> your<00:10:18.870> buy<00:10:19.019> order<00:10:19.410> gets<00:10:20.240> serialized 00:10:21.230 --> 00:10:21.240 align:start position:0% so the your buy order gets serialized 00:10:21.240 --> 00:10:24.500 align:start position:0% so the your buy order gets serialized bundled<00:10:21.660> into<00:10:21.750> a<00:10:21.870> transaction<00:10:22.560> and<00:10:22.800> on<00:10:23.760> the 00:10:24.500 --> 00:10:24.510 align:start position:0% bundled into a transaction and on the 00:10:24.510 --> 00:10:25.819 align:start position:0% bundled into a transaction and on the augur<00:10:24.779> trading<00:10:25.079> contract<00:10:25.410> there's<00:10:25.560> a<00:10:25.620> by 00:10:25.819 --> 00:10:25.829 align:start position:0% augur trading contract there's a by 00:10:25.829 --> 00:10:29.360 align:start position:0% augur trading contract there's a by shares<00:10:26.220> method<00:10:26.810> now<00:10:27.810> this<00:10:27.990> the<00:10:28.860> transaction 00:10:29.360 --> 00:10:29.370 align:start position:0% shares method now this the transaction 00:10:29.370 --> 00:10:30.740 align:start position:0% shares method now this the transaction actually<00:10:29.610> gets<00:10:29.730> signed<00:10:30.000> in<00:10:30.269> the<00:10:30.540> browser 00:10:30.740 --> 00:10:30.750 align:start position:0% actually gets signed in the browser 00:10:30.750 --> 00:10:32.750 align:start position:0% actually gets signed in the browser right<00:10:31.350> so<00:10:31.589> this<00:10:31.800> I<00:10:32.010> said<00:10:32.279> that<00:10:32.399> you<00:10:32.459> don't<00:10:32.550> need 00:10:32.750 --> 00:10:32.760 align:start position:0% right so this I said that you don't need 00:10:32.760 --> 00:10:36.139 align:start position:0% right so this I said that you don't need to<00:10:32.819> have<00:10:33.089> a<00:10:33.389> local<00:10:33.779> guest<00:10:34.589> node<00:10:34.829> running<00:10:35.149> in 00:10:36.139 --> 00:10:36.149 align:start position:0% to have a local guest node running in 00:10:36.149 --> 00:10:38.990 align:start position:0% to have a local guest node running in fact<00:10:36.420> you<00:10:36.870> can<00:10:37.079> sign<00:10:37.949> this<00:10:38.220> just<00:10:38.699> using 00:10:38.990 --> 00:10:39.000 align:start position:0% fact you can sign this just using 00:10:39.000 --> 00:10:40.309 align:start position:0% fact you can sign this just using javascript<00:10:39.360> in<00:10:39.720> the<00:10:39.750> browser<00:10:39.839> then<00:10:40.290> you 00:10:40.309 --> 00:10:40.319 align:start position:0% javascript in the browser then you 00:10:40.319 --> 00:10:43.670 align:start position:0% javascript in the browser then you submit<00:10:40.680> the<00:10:41.069> signed<00:10:41.339> raw<00:10:42.089> transaction<00:10:42.839> to<00:10:43.380> the 00:10:43.670 --> 00:10:43.680 align:start position:0% submit the signed raw transaction to the 00:10:43.680 --> 00:10:46.970 align:start position:0% submit the signed raw transaction to the etherium<00:10:44.069> node<00:10:44.250> that<00:10:44.910> way<00:10:45.149> and<00:10:45.560> in<00:10:46.560> that<00:10:46.800> case 00:10:46.970 --> 00:10:46.980 align:start position:0% etherium node that way and in that case 00:10:46.980 --> 00:10:48.710 align:start position:0% etherium node that way and in that case the<00:10:47.189> etherium<00:10:47.490> node<00:10:47.639> does<00:10:47.819> not<00:10:47.850> ever<00:10:48.240> need<00:10:48.540> to 00:10:48.710 --> 00:10:48.720 align:start position:0% the etherium node does not ever need to 00:10:48.720 --> 00:10:50.540 align:start position:0% the etherium node does not ever need to see<00:10:48.930> your<00:10:49.139> private<00:10:49.560> key<00:10:49.740> it<00:10:49.860> just<00:10:50.069> gets<00:10:50.279> the 00:10:50.540 --> 00:10:50.550 align:start position:0% see your private key it just gets the 00:10:50.550 --> 00:10:54.550 align:start position:0% see your private key it just gets the encrypted<00:10:51.089> it<00:10:51.389> gets<00:10:51.569> the<00:10:51.750> signed<00:10:52.589> transaction 00:10:54.550 --> 00:10:54.560 align:start position:0% encrypted it gets the signed transaction 00:10:54.560 --> 00:10:57.439 align:start position:0% encrypted it gets the signed transaction then<00:10:55.560> we<00:10:55.680> send<00:10:55.920> it<00:10:56.069> to<00:10:56.100> Jeff<00:10:56.579> Jeff<00:10:57.180> cross 00:10:57.439 --> 00:10:57.449 align:start position:0% then we send it to Jeff Jeff cross 00:10:57.449 --> 00:10:59.449 align:start position:0% then we send it to Jeff Jeff cross broadcast<00:10:58.079> the<00:10:58.170> transaction<00:10:58.680> to<00:10:58.949> the<00:10:58.980> network 00:10:59.449 --> 00:10:59.459 align:start position:0% broadcast the transaction to the network 00:10:59.459 --> 00:11:01.790 align:start position:0% broadcast the transaction to the network and<00:10:59.670> then<00:10:59.970> we<00:11:00.149> just<00:11:00.300> pull<00:11:00.509> get<00:11:00.720> see<00:11:01.110> when<00:11:01.680> the 00:11:01.790 --> 00:11:01.800 align:start position:0% and then we just pull get see when the 00:11:01.800 --> 00:11:03.230 align:start position:0% and then we just pull get see when the transactions<00:11:02.370> been<00:11:02.519> incorporated<00:11:03.029> into<00:11:03.149> a 00:11:03.230 --> 00:11:03.240 align:start position:0% transactions been incorporated into a 00:11:03.240 --> 00:11:06.290 align:start position:0% transactions been incorporated into a block<00:11:03.480> and<00:11:03.889> this<00:11:04.889> is<00:11:05.069> what<00:11:05.279> our<00:11:05.459> architecture 00:11:06.290 --> 00:11:06.300 align:start position:0% block and this is what our architecture 00:11:06.300 --> 00:11:08.960 align:start position:0% block and this is what our architecture looks<00:11:06.510> like<00:11:06.720> so<00:11:07.319> we've<00:11:07.920> got<00:11:08.069> our<00:11:08.339> very<00:11:08.610> happy 00:11:08.960 --> 00:11:08.970 align:start position:0% looks like so we've got our very happy 00:11:08.970 --> 00:11:10.790 align:start position:0% looks like so we've got our very happy user<00:11:09.180> and<00:11:09.510> this<00:11:09.990> interface<00:11:10.410> that<00:11:10.439> I've<00:11:10.680> been 00:11:10.790 --> 00:11:10.800 align:start position:0% user and this interface that I've been 00:11:10.800 --> 00:11:11.390 align:start position:0% user and this interface that I've been showing<00:11:11.040> you 00:11:11.390 --> 00:11:11.400 align:start position:0% showing you 00:11:11.400 --> 00:11:13.760 align:start position:0% showing you is<00:11:11.520> so<00:11:12.300> that's<00:11:12.450> the<00:11:12.660> sort<00:11:12.960> of<00:11:13.020> pinkish<00:11:13.320> purple 00:11:13.760 --> 00:11:13.770 align:start position:0% is so that's the sort of pinkish purple 00:11:13.770 --> 00:11:17.860 align:start position:0% is so that's the sort of pinkish purple blob<00:11:13.920> where<00:11:14.160> it<00:11:14.220> says<00:11:14.310> auger<00:11:14.640> client<00:11:15.000> and 00:11:17.860 --> 00:11:17.870 align:start position:0% blob where it says auger client and 00:11:17.870 --> 00:11:20.720 align:start position:0% blob where it says auger client and because<00:11:18.870> a<00:11:19.080> lot<00:11:19.800> of<00:11:19.920> the<00:11:19.980> nice<00:11:20.130> tooling<00:11:20.580> that 00:11:20.720 --> 00:11:20.730 align:start position:0% because a lot of the nice tooling that 00:11:20.730 --> 00:11:21.890 align:start position:0% because a lot of the nice tooling that that<00:11:21.060> has<00:11:21.300> been<00:11:21.450> talked<00:11:21.630> about<00:11:21.750> here 00:11:21.890 --> 00:11:21.900 align:start position:0% that has been talked about here 00:11:21.900 --> 00:11:24.230 align:start position:0% that has been talked about here basically<00:11:22.800> didn't<00:11:23.370> exist<00:11:23.670> when<00:11:23.850> we<00:11:23.910> got 00:11:24.230 --> 00:11:24.240 align:start position:0% basically didn't exist when we got 00:11:24.240 --> 00:11:25.850 align:start position:0% basically didn't exist when we got started<00:11:24.480> we're<00:11:25.020> mostly<00:11:25.290> just<00:11:25.440> working<00:11:25.740> with 00:11:25.850 --> 00:11:25.860 align:start position:0% started we're mostly just working with 00:11:25.860 --> 00:11:27.830 align:start position:0% started we're mostly just working with our<00:11:26.160> own<00:11:26.400> stack<00:11:26.790> so<00:11:27.420> we<00:11:27.450> have<00:11:27.600> our<00:11:27.750> own 00:11:27.830 --> 00:11:27.840 align:start position:0% our own stack so we have our own 00:11:27.840 --> 00:11:32.120 align:start position:0% our own stack so we have our own middleware<00:11:28.260> and<00:11:29.930> and<00:11:30.930> that's<00:11:31.800> the<00:11:31.920> way<00:11:32.010> it 00:11:32.120 --> 00:11:32.130 align:start position:0% middleware and and that's the way it 00:11:32.130 --> 00:11:35.420 align:start position:0% middleware and and that's the way it talks<00:11:32.400> to<00:11:33.650> aetherium<00:11:34.650> which<00:11:34.980> here<00:11:35.190> would<00:11:35.310> be 00:11:35.420 --> 00:11:35.430 align:start position:0% talks to aetherium which here would be 00:11:35.430 --> 00:11:37.550 align:start position:0% talks to aetherium which here would be on<00:11:35.550> the<00:11:35.670> user's<00:11:35.940> computer<00:11:36.120> in<00:11:36.600> the<00:11:37.080> example<00:11:37.530> I 00:11:37.550 --> 00:11:37.560 align:start position:0% on the user's computer in the example I 00:11:37.560 --> 00:11:38.930 align:start position:0% on the user's computer in the example I just<00:11:37.590> showed<00:11:37.770> you<00:11:37.920> it's<00:11:38.130> actually<00:11:38.280> running<00:11:38.670> on 00:11:38.930 --> 00:11:38.940 align:start position:0% just showed you it's actually running on 00:11:38.940 --> 00:11:42.410 align:start position:0% just showed you it's actually running on our<00:11:39.450> remote<00:11:39.720> server<00:11:40.140> and<00:11:40.410> that<00:11:40.440> talked<00:11:41.430> to<00:11:41.820> the 00:11:42.410 --> 00:11:42.420 align:start position:0% our remote server and that talked to the 00:11:42.420 --> 00:11:47.510 align:start position:0% our remote server and that talked to the decentralized<00:11:43.110> network<00:11:45.830> so<00:11:46.830> let<00:11:47.160> me<00:11:47.250> let<00:11:47.490> me 00:11:47.510 --> 00:11:47.520 align:start position:0% decentralized network so let me let me 00:11:47.520 --> 00:11:49.850 align:start position:0% decentralized network so let me let me walk<00:11:47.730> you<00:11:47.760> through<00:11:47.930> if<00:11:48.930> I<00:11:49.050> have<00:11:49.200> time<00:11:49.380> two 00:11:49.850 --> 00:11:49.860 align:start position:0% walk you through if I have time two 00:11:49.860 --> 00:11:51.170 align:start position:0% walk you through if I have time two minutes<00:11:50.100> they<00:11:50.460> walk<00:11:50.640> you<00:11:50.670> through<00:11:50.910> exactly 00:11:51.170 --> 00:11:51.180 align:start position:0% minutes they walk you through exactly 00:11:51.180 --> 00:11:54.800 align:start position:0% minutes they walk you through exactly what<00:11:51.660> happens<00:11:52.080> when<00:11:52.620> you<00:11:53.570> when<00:11:54.570> you<00:11:54.660> buy 00:11:54.800 --> 00:11:54.810 align:start position:0% what happens when you when you buy 00:11:54.810 --> 00:11:59.510 align:start position:0% what happens when you when you buy shares<00:11:55.440> so<00:11:56.390> so<00:11:57.390> that<00:11:57.540> this<00:11:57.720> is<00:11:58.370> this<00:11:59.370> is<00:11:59.460> sort 00:11:59.510 --> 00:11:59.520 align:start position:0% shares so so that this is this is sort 00:11:59.520 --> 00:12:01.700 align:start position:0% shares so so that this is this is sort of<00:11:59.640> a<00:11:59.700> simplified<00:12:00.180> version<00:12:00.390> of<00:12:00.780> our<00:12:01.050> markets 00:12:01.700 --> 00:12:01.710 align:start position:0% of a simplified version of our markets 00:12:01.710 --> 00:12:04.850 align:start position:0% of a simplified version of our markets data<00:12:01.980> contract<00:12:02.490> so<00:12:03.000> there<00:12:03.540> is<00:12:03.690> there's<00:12:04.020> a<00:12:04.110> so 00:12:04.850 --> 00:12:04.860 align:start position:0% data contract so there is there's a so 00:12:04.860 --> 00:12:06.290 align:start position:0% data contract so there is there's a so all<00:12:05.310> of<00:12:05.430> our<00:12:05.490> contracts<00:12:05.910> are<00:12:06.000> written<00:12:06.060> in 00:12:06.290 --> 00:12:06.300 align:start position:0% all of our contracts are written in 00:12:06.300 --> 00:12:11.900 align:start position:0% all of our contracts are written in serpent<00:12:06.720> and<00:12:08.240> we<00:12:10.130> all<00:12:11.130> information<00:12:11.790> about 00:12:11.900 --> 00:12:11.910 align:start position:0% serpent and we all information about 00:12:11.910 --> 00:12:14.150 align:start position:0% serpent and we all information about shares<00:12:12.480> and<00:12:12.870> bets<00:12:13.380> that<00:12:13.530> people<00:12:13.800> have<00:12:13.890> placed 00:12:14.150 --> 00:12:14.160 align:start position:0% shares and bets that people have placed 00:12:14.160 --> 00:12:16.610 align:start position:0% shares and bets that people have placed they're<00:12:14.430> stored<00:12:14.820> as<00:12:14.970> data<00:12:15.300> on<00:12:15.540> contracts<00:12:16.170> all 00:12:16.610 --> 00:12:16.620 align:start position:0% they're stored as data on contracts all 00:12:16.620 --> 00:12:18.110 align:start position:0% they're stored as data on contracts all right<00:12:16.710> so<00:12:16.830> the<00:12:16.920> set<00:12:17.070> of<00:12:17.160> contracts<00:12:17.580> is<00:12:17.760> fixed 00:12:18.110 --> 00:12:18.120 align:start position:0% right so the set of contracts is fixed 00:12:18.120 --> 00:12:21.800 align:start position:0% right so the set of contracts is fixed and<00:12:18.890> the<00:12:19.890> the<00:12:20.280> trades<00:12:20.580> that<00:12:20.700> you<00:12:20.910> make<00:12:21.090> and<00:12:21.360> who 00:12:21.800 --> 00:12:21.810 align:start position:0% and the the trades that you make and who 00:12:21.810 --> 00:12:23.090 align:start position:0% and the the trades that you make and who has<00:12:21.960> made<00:12:22.140> them<00:12:22.380> and<00:12:22.620> the<00:12:22.680> events<00:12:22.920> that<00:12:22.980> are 00:12:23.090 --> 00:12:23.100 align:start position:0% has made them and the events that are 00:12:23.100 --> 00:12:25.340 align:start position:0% has made them and the events that are incorporated<00:12:23.550> in<00:12:23.640> markets<00:12:24.080> these<00:12:25.080> are<00:12:25.230> just 00:12:25.340 --> 00:12:25.350 align:start position:0% incorporated in markets these are just 00:12:25.350 --> 00:12:27.950 align:start position:0% incorporated in markets these are just data<00:12:25.620> on<00:12:26.070> the<00:12:26.460> contracts<00:12:26.970> sort<00:12:27.480> is<00:12:27.600> basically 00:12:27.950 --> 00:12:27.960 align:start position:0% data on the contracts sort is basically 00:12:27.960 --> 00:12:32.150 align:start position:0% data on the contracts sort is basically a<00:12:28.080> big<00:12:28.980> dictionary<00:12:29.630> and<00:12:30.630> we<00:12:30.810> have<00:12:30.900> a<00:12:30.930> modify<00:12:31.380> we 00:12:32.150 --> 00:12:32.160 align:start position:0% a big dictionary and we have a modify we 00:12:32.160 --> 00:12:33.560 align:start position:0% a big dictionary and we have a modify we have<00:12:32.250> a<00:12:32.280> modify<00:12:32.670> shares<00:12:32.970> method<00:12:33.270> so<00:12:33.390> this 00:12:33.560 --> 00:12:33.570 align:start position:0% have a modify shares method so this 00:12:33.570 --> 00:12:36.080 align:start position:0% have a modify shares method so this method<00:12:34.170> gets<00:12:34.530> called<00:12:34.590> so<00:12:35.070> if<00:12:35.160> Alice<00:12:35.490> so<00:12:35.730> Alice 00:12:36.080 --> 00:12:36.090 align:start position:0% method gets called so if Alice so Alice 00:12:36.090 --> 00:12:38.090 align:start position:0% method gets called so if Alice so Alice buys<00:12:36.510> two<00:12:36.840> shares<00:12:37.050> of<00:12:37.200> outcome<00:12:37.500> 1<00:12:37.650> and<00:12:37.830> market 00:12:38.090 --> 00:12:38.100 align:start position:0% buys two shares of outcome 1 and market 00:12:38.100 --> 00:12:40.340 align:start position:0% buys two shares of outcome 1 and market em<00:12:38.220> so<00:12:38.550> we<00:12:39.000> invoke<00:12:39.330> modify<00:12:39.750> shares<00:12:40.020> and 00:12:40.340 --> 00:12:40.350 align:start position:0% em so we invoke modify shares and 00:12:40.350 --> 00:12:42.830 align:start position:0% em so we invoke modify shares and basically<00:12:41.190> this<00:12:41.430> is<00:12:41.490> what<00:12:41.730> happens<00:12:42.060> right<00:12:42.570> so 00:12:42.830 --> 00:12:42.840 align:start position:0% basically this is what happens right so 00:12:42.840 --> 00:12:45.320 align:start position:0% basically this is what happens right so this<00:12:43.230> is<00:12:43.410> that<00:12:43.560> data<00:12:43.740> structure<00:12:44.190> up<00:12:44.250> top<00:12:44.490> then 00:12:45.320 --> 00:12:45.330 align:start position:0% this is that data structure up top then 00:12:45.330 --> 00:12:46.700 align:start position:0% this is that data structure up top then we<00:12:45.420> can<00:12:45.510> say<00:12:45.600> okay<00:12:45.750> now<00:12:45.900> she<00:12:46.050> has<00:12:46.290> two<00:12:46.500> shares 00:12:46.700 --> 00:12:46.710 align:start position:0% we can say okay now she has two shares 00:12:46.710 --> 00:12:51.020 align:start position:0% we can say okay now she has two shares of<00:12:46.830> point<00:12:49.700> now 00:12:51.020 --> 00:12:51.030 align:start position:0% of point now 00:12:51.030 --> 00:12:53.450 align:start position:0% of point now I've<00:12:51.990> described<00:12:52.380> this<00:12:52.500> sort<00:12:52.710> of<00:12:52.770> somewhat 00:12:53.450 --> 00:12:53.460 align:start position:0% I've described this sort of somewhat 00:12:53.460 --> 00:12:55.850 align:start position:0% I've described this sort of somewhat complicated<00:12:53.940> system<00:12:54.390> and<00:12:54.510> it's<00:12:55.140> augers 00:12:55.850 --> 00:12:55.860 align:start position:0% complicated system and it's augers 00:12:55.860 --> 00:12:57.530 align:start position:0% complicated system and it's augers really<00:12:56.130> it's<00:12:56.430> too<00:12:56.640> big<00:12:56.850> for<00:12:57.060> one<00:12:57.210> contra 00:12:57.530 --> 00:12:57.540 align:start position:0% really it's too big for one contra 00:12:57.540 --> 00:12:59.000 align:start position:0% really it's too big for one contra originally<00:12:57.930> had<00:12:58.110> it<00:12:58.200> all<00:12:58.320> in<00:12:58.410> one<00:12:58.530> contract 00:12:59.000 --> 00:12:59.010 align:start position:0% originally had it all in one contract 00:12:59.010 --> 00:13:01.210 align:start position:0% originally had it all in one contract there<00:12:59.580> are<00:12:59.670> some<00:12:59.790> nice<00:12:59.970> things<00:13:00.000> about<00:13:00.390> that 00:13:01.210 --> 00:13:01.220 align:start position:0% there are some nice things about that 00:13:01.220 --> 00:13:04.190 align:start position:0% there are some nice things about that but<00:13:02.220> basically<00:13:03.000> it's<00:13:03.300> way<00:13:03.480> too<00:13:03.540> big<00:13:03.660> to<00:13:03.840> upload 00:13:04.190 --> 00:13:04.200 align:start position:0% but basically it's way too big to upload 00:13:04.200 --> 00:13:07.760 align:start position:0% but basically it's way too big to upload so<00:13:04.350> we<00:13:04.440> actually<00:13:04.590> have<00:13:04.830> it<00:13:04.950> split<00:13:05.400> into<00:13:06.770> 26 00:13:07.760 --> 00:13:07.770 align:start position:0% so we actually have it split into 26 00:13:07.770 --> 00:13:11.120 align:start position:0% so we actually have it split into 26 contracts<00:13:08.220> and<00:13:08.490> so<00:13:09.180> our<00:13:09.720> contracts<00:13:10.380> are<00:13:10.500> we 00:13:11.120 --> 00:13:11.130 align:start position:0% contracts and so our contracts are we 00:13:11.130 --> 00:13:13.460 align:start position:0% contracts and so our contracts are we have<00:13:11.280> data<00:13:11.730> contracts<00:13:12.300> which<00:13:12.630> basically<00:13:13.320> are 00:13:13.460 --> 00:13:13.470 align:start position:0% have data contracts which basically are 00:13:13.470 --> 00:13:17.570 align:start position:0% have data contracts which basically are there<00:13:15.260> they<00:13:16.260> have<00:13:16.440> things<00:13:16.680> like<00:13:16.890> this<00:13:17.070> market 00:13:17.570 --> 00:13:17.580 align:start position:0% there they have things like this market 00:13:17.580 --> 00:13:19.820 align:start position:0% there they have things like this market data<00:13:17.730> structure<00:13:18.240> and<00:13:18.450> then<00:13:19.230> they<00:13:19.380> have 00:13:19.820 --> 00:13:19.830 align:start position:0% data structure and then they have 00:13:19.830 --> 00:13:21.090 align:start position:0% data structure and then they have setter<00:13:20.070> and<00:13:20.280> getter<00:13:20.340> methods 00:13:21.090 --> 00:13:21.100 align:start position:0% setter and getter methods 00:13:21.100 --> 00:13:23.640 align:start position:0% setter and getter methods and<00:13:21.190> these<00:13:21.760> can<00:13:21.940> be<00:13:22.090> imported<00:13:22.720> into<00:13:22.960> the 00:13:23.640 --> 00:13:23.650 align:start position:0% and these can be imported into the 00:13:23.650 --> 00:13:26.430 align:start position:0% and these can be imported into the function<00:13:24.040> contracts<00:13:24.870> which<00:13:25.870> sort<00:13:26.200> of<00:13:26.260> make 00:13:26.430 --> 00:13:26.440 align:start position:0% function contracts which sort of make 00:13:26.440 --> 00:13:27.840 align:start position:0% function contracts which sort of make use<00:13:26.590> of<00:13:26.620> them<00:13:26.890> and<00:13:27.040> the<00:13:27.340> reason<00:13:27.580> we<00:13:27.670> have<00:13:27.760> it 00:13:27.840 --> 00:13:27.850 align:start position:0% use of them and the reason we have it 00:13:27.850 --> 00:13:29.850 align:start position:0% use of them and the reason we have it set<00:13:27.970> up<00:13:28.000> like<00:13:28.210> that<00:13:28.240> is<00:13:28.510> so<00:13:28.630> that<00:13:28.780> most<00:13:29.620> of<00:13:29.770> the 00:13:29.850 --> 00:13:29.860 align:start position:0% set up like that is so that most of the 00:13:29.860 --> 00:13:31.590 align:start position:0% set up like that is so that most of the functionality<00:13:30.460> is<00:13:30.580> in<00:13:30.790> the<00:13:30.910> functions<00:13:31.360> and 00:13:31.590 --> 00:13:31.600 align:start position:0% functionality is in the functions and 00:13:31.600 --> 00:13:34.140 align:start position:0% functionality is in the functions and the<00:13:32.050> function<00:13:32.350> contracts<00:13:32.740> and<00:13:33.120> because<00:13:34.120> of 00:13:34.140 --> 00:13:34.150 align:start position:0% the function contracts and because of 00:13:34.150 --> 00:13:37.740 align:start position:0% the function contracts and because of that<00:13:34.680> we<00:13:35.680> can<00:13:35.920> we<00:13:36.610> can<00:13:36.760> make<00:13:36.790> changes<00:13:37.360> without 00:13:37.740 --> 00:13:37.750 align:start position:0% that we can we can make changes without 00:13:37.750 --> 00:13:39.570 align:start position:0% that we can we can make changes without having<00:13:37.960> to<00:13:38.320> throw<00:13:38.470> out<00:13:38.680> all<00:13:38.860> the<00:13:38.980> data<00:13:39.100> which 00:13:39.570 --> 00:13:39.580 align:start position:0% having to throw out all the data which 00:13:39.580 --> 00:13:42.690 align:start position:0% having to throw out all the data which is<00:13:40.560> even<00:13:41.560> when<00:13:41.710> we're<00:13:41.860> testing<00:13:42.010> is<00:13:42.370> really 00:13:42.690 --> 00:13:42.700 align:start position:0% is even when we're testing is really 00:13:42.700 --> 00:13:48.330 align:start position:0% is even when we're testing is really nice<00:13:45.540> so<00:13:46.540> I<00:13:46.570> want<00:13:47.170> to<00:13:47.260> give<00:13:47.350> you<00:13:47.380> an<00:13:47.680> example<00:13:48.010> of 00:13:48.330 --> 00:13:48.340 align:start position:0% nice so I want to give you an example of 00:13:48.340 --> 00:13:51.540 align:start position:0% nice so I want to give you an example of how<00:13:49.680> multiple<00:13:50.680> contracts<00:13:51.130> work<00:13:51.370> together 00:13:51.540 --> 00:13:51.550 align:start position:0% how multiple contracts work together 00:13:51.550 --> 00:13:56.340 align:start position:0% how multiple contracts work together just<00:13:51.730> very<00:13:52.090> quickly<00:13:52.770> so<00:13:53.770> this<00:13:53.950> is<00:13:54.190> in<00:13:55.350> the 00:13:56.340 --> 00:13:56.350 align:start position:0% just very quickly so this is in the 00:13:56.350 --> 00:13:57.840 align:start position:0% just very quickly so this is in the little<00:13:56.560> walkthrough<00:13:56.740> I<00:13:57.010> just<00:13:57.460> gave<00:13:57.580> you<00:13:57.610> so 00:13:57.840 --> 00:13:57.850 align:start position:0% little walkthrough I just gave you so 00:13:57.850 --> 00:14:00.120 align:start position:0% little walkthrough I just gave you so many<00:13:57.940> use<00:13:58.630> are<00:13:58.900> what<00:13:59.320> are<00:13:59.410> called<00:13:59.500> our<00:13:59.620> faucets 00:14:00.120 --> 00:14:00.130 align:start position:0% many use are what are called our faucets 00:14:00.130 --> 00:14:02.070 align:start position:0% many use are what are called our faucets so<00:14:00.430> this<00:14:00.580> is<00:14:00.730> is<00:14:01.120> your<00:14:01.300> free<00:14:01.480> cash<00:14:01.690> and<00:14:01.960> free 00:14:02.070 --> 00:14:02.080 align:start position:0% so this is is your free cash and free 00:14:02.080 --> 00:14:04.680 align:start position:0% so this is is your free cash and free reputation<00:14:02.650> so<00:14:03.250> these<00:14:03.970> are<00:14:04.120> methods<00:14:04.300> on<00:14:04.660> the 00:14:04.680 --> 00:14:04.690 align:start position:0% reputation so these are methods on the 00:14:04.690 --> 00:14:06.630 align:start position:0% reputation so these are methods on the faucets<00:14:05.230> contract<00:14:05.650> which<00:14:05.800> is<00:14:05.830> it's<00:14:06.250> one<00:14:06.460> it's 00:14:06.630 --> 00:14:06.640 align:start position:0% faucets contract which is it's one it's 00:14:06.640 --> 00:14:09.930 align:start position:0% faucets contract which is it's one it's one<00:14:06.730> of<00:14:06.970> the<00:14:07.090> function<00:14:07.480> contracts<00:14:08.140> and<00:14:09.040> it<00:14:09.820> has 00:14:09.930 --> 00:14:09.940 align:start position:0% one of the function contracts and it has 00:14:09.940 --> 00:14:12.420 align:start position:0% one of the function contracts and it has to<00:14:10.120> import<00:14:10.540> the<00:14:11.110> cash<00:14:11.350> and<00:14:11.740> the<00:14:12.010> reporting 00:14:12.420 --> 00:14:12.430 align:start position:0% to import the cash and the reporting 00:14:12.430 --> 00:14:16.320 align:start position:0% to import the cash and the reporting contracts<00:14:12.820> to<00:14:12.970> do<00:14:13.090> this<00:14:14.370> so<00:14:15.370> that's<00:14:15.610> the 00:14:16.320 --> 00:14:16.330 align:start position:0% contracts to do this so that's the 00:14:16.330 --> 00:14:17.910 align:start position:0% contracts to do this so that's the syntax<00:14:16.540> to<00:14:16.810> do<00:14:16.930> this<00:14:17.050> in<00:14:17.290> serpent<00:14:17.800> and 00:14:17.910 --> 00:14:17.920 align:start position:0% syntax to do this in serpent and 00:14:17.920 --> 00:14:19.410 align:start position:0% syntax to do this in serpent and actually<00:14:18.430> don't<00:14:18.550> know<00:14:18.760> the<00:14:19.000> syntax<00:14:19.180> and 00:14:19.410 --> 00:14:19.420 align:start position:0% actually don't know the syntax and 00:14:19.420 --> 00:14:20.850 align:start position:0% actually don't know the syntax and solidity<00:14:19.750> but<00:14:19.990> the<00:14:20.080> syntax<00:14:20.230> in<00:14:20.500> serpent 00:14:20.850 --> 00:14:20.860 align:start position:0% solidity but the syntax in serpent 00:14:20.860 --> 00:14:23.040 align:start position:0% solidity but the syntax in serpent actually<00:14:21.070> requires<00:14:21.400> you<00:14:21.730> to<00:14:21.780> it's<00:14:22.780> somewhat 00:14:23.040 --> 00:14:23.050 align:start position:0% actually requires you to it's somewhat 00:14:23.050 --> 00:14:25.020 align:start position:0% actually requires you to it's somewhat verbose<00:14:23.410> and<00:14:23.680> requires<00:14:24.490> you<00:14:24.580> to<00:14:24.730> actually 00:14:25.020 --> 00:14:25.030 align:start position:0% verbose and requires you to actually 00:14:25.030 --> 00:14:28.260 align:start position:0% verbose and requires you to actually specify<00:14:25.660> the<00:14:25.720> address<00:14:25.960> of<00:14:26.610> cash<00:14:27.610> and<00:14:27.970> that's 00:14:28.260 --> 00:14:28.270 align:start position:0% specify the address of cash and that's 00:14:28.270 --> 00:14:30.270 align:start position:0% specify the address of cash and that's somewhat<00:14:28.660> inconvenient<00:14:29.260> because<00:14:29.560> that<00:14:30.100> will 00:14:30.270 --> 00:14:30.280 align:start position:0% somewhat inconvenient because that will 00:14:30.280 --> 00:14:35.190 align:start position:0% somewhat inconvenient because that will change<00:14:30.310> if<00:14:30.850> cash<00:14:31.510> contract<00:14:31.990> changes<00:14:32.320> and<00:14:34.200> that 00:14:35.190 --> 00:14:35.200 align:start position:0% change if cash contract changes and that 00:14:35.200 --> 00:14:36.750 align:start position:0% change if cash contract changes and that if<00:14:35.440> you<00:14:35.590> have<00:14:35.740> you<00:14:36.280> know<00:14:36.310> multiple 00:14:36.750 --> 00:14:36.760 align:start position:0% if you have you know multiple 00:14:36.760 --> 00:14:40.130 align:start position:0% if you have you know multiple dependencies<00:14:37.300> that<00:14:37.660> can<00:14:37.900> be<00:14:38.050> a<00:14:38.290> real<00:14:38.470> pain<00:14:38.650> so 00:14:40.130 --> 00:14:40.140 align:start position:0% dependencies that can be a real pain so 00:14:40.140 --> 00:14:42.450 align:start position:0% dependencies that can be a real pain so what<00:14:41.140> we<00:14:41.230> did<00:14:41.320> is<00:14:41.470> we<00:14:41.620> have<00:14:41.770> a<00:14:41.800> dependency 00:14:42.450 --> 00:14:42.460 align:start position:0% what we did is we have a dependency 00:14:42.460 --> 00:14:44.970 align:start position:0% what we did is we have a dependency resolution<00:14:42.870> script<00:14:43.870> that<00:14:44.290> takes<00:14:44.350> care<00:14:44.950> of 00:14:44.970 --> 00:14:44.980 align:start position:0% resolution script that takes care of 00:14:44.980 --> 00:14:46.410 align:start position:0% resolution script that takes care of this<00:14:45.100> for<00:14:45.310> us<00:14:45.400> so<00:14:45.430> we<00:14:45.700> can<00:14:45.790> use<00:14:45.940> this<00:14:46.120> sort<00:14:46.330> of 00:14:46.410 --> 00:14:46.420 align:start position:0% this for us so we can use this sort of 00:14:46.420 --> 00:14:49.290 align:start position:0% this for us so we can use this sort of pythonic<00:14:46.900> syntax<00:14:47.320> import<00:14:47.980> cash<00:14:48.190> as<00:14:48.520> cash<00:14:49.000> and 00:14:49.290 --> 00:14:49.300 align:start position:0% pythonic syntax import cash as cash and 00:14:49.300 --> 00:14:54.230 align:start position:0% pythonic syntax import cash as cash and it<00:14:50.200> inserts<00:14:50.560> the<00:14:50.710> externs<00:14:51.450> as<00:14:52.450> needed<00:14:52.960> and 00:14:54.230 --> 00:14:54.240 align:start position:0% it inserts the externs as needed and 00:14:54.240 --> 00:14:57.060 align:start position:0% it inserts the externs as needed and then<00:14:55.240> we<00:14:55.300> can<00:14:55.420> just<00:14:55.540> use<00:14:55.570> it<00:14:55.660> that<00:14:55.900> way<00:14:56.070> okay 00:14:57.060 --> 00:14:57.070 align:start position:0% then we can just use it that way okay 00:14:57.070 --> 00:14:58.590 align:start position:0% then we can just use it that way okay and<00:14:57.100> I<00:14:57.520> also<00:14:57.670> just<00:14:57.850> wanted<00:14:58.060> to<00:14:58.120> say<00:14:58.180> all<00:14:58.420> our 00:14:58.590 --> 00:14:58.600 align:start position:0% and I also just wanted to say all our 00:14:58.600 --> 00:15:00.480 align:start position:0% and I also just wanted to say all our code<00:14:58.780> is<00:14:59.020> open<00:14:59.470> source<00:14:59.620> I<00:15:00.070> know<00:15:00.190> this<00:15:00.310> was<00:15:00.460> just 00:15:00.480 --> 00:15:00.490 align:start position:0% code is open source I know this was just 00:15:00.490 --> 00:15:04.080 align:start position:0% code is open source I know this was just sort<00:15:00.940> of<00:15:00.970> a<00:15:01.060> whirlwind<00:15:01.420> tour<00:15:01.830> it's<00:15:02.830> all<00:15:03.010> at<00:15:03.190> on 00:15:04.080 --> 00:15:04.090 align:start position:0% sort of a whirlwind tour it's all at on 00:15:04.090 --> 00:15:06.920 align:start position:0% sort of a whirlwind tour it's all at on our<00:15:04.330> github<00:15:04.600> so<00:15:05.080> if<00:15:05.380> you<00:15:05.770> want<00:15:06.130> to<00:15:06.280> pitch<00:15:06.850> in 00:15:06.920 --> 00:15:06.930 align:start position:0% our github so if you want to pitch in 00:15:06.930 --> 00:15:12.630 align:start position:0% our github so if you want to pitch in please<00:15:07.930> do<00:15:08.670> yeah<00:15:09.670> that's<00:15:10.480> it