WEBVTT Kind: captions Language: en 00:00:14.400 --> 00:00:18.439 align:start position:0% so<00:00:15.400> I'm<00:00:15.460> going<00:00:15.550> to<00:00:15.639> be<00:00:15.700> talking<00:00:16.119> about<00:00:16.410> DAP<00:00:17.410> hub 00:00:18.439 --> 00:00:18.449 align:start position:0% so I'm going to be talking about DAP hub 00:00:18.449 --> 00:00:24.179 align:start position:0% so I'm going to be talking about DAP hub what<00:00:19.449> is<00:00:19.659> Dabba<00:00:21.179> Dabba<00:00:22.179> is<00:00:22.689> a<00:00:23.189> self-organizing 00:00:24.179 --> 00:00:24.189 align:start position:0% what is Dabba Dabba is a self-organizing 00:00:24.189 --> 00:00:26.970 align:start position:0% what is Dabba Dabba is a self-organizing network<00:00:24.699> of<00:00:25.259> logicians<00:00:26.259> research 00:00:26.970 --> 00:00:26.980 align:start position:0% network of logicians research 00:00:26.980 --> 00:00:30.329 align:start position:0% network of logicians research researchers<00:00:27.640> designers<00:00:28.539> and<00:00:28.810> developers<00:00:29.339> who 00:00:30.329 --> 00:00:30.339 align:start position:0% researchers designers and developers who 00:00:30.339 --> 00:00:32.819 align:start position:0% researchers designers and developers who have<00:00:30.399> come<00:00:30.729> together<00:00:30.880> to<00:00:31.359> think<00:00:32.259> rigorously 00:00:32.819 --> 00:00:32.829 align:start position:0% have come together to think rigorously 00:00:32.829 --> 00:00:36.230 align:start position:0% have come together to think rigorously about<00:00:33.670> gaps<00:00:34.120> from<00:00:34.870> first<00:00:35.200> principles<00:00:35.860> you 00:00:36.230 --> 00:00:36.240 align:start position:0% about gaps from first principles you 00:00:36.240 --> 00:00:38.700 align:start position:0% about gaps from first principles you could<00:00:37.240> say<00:00:37.480> that<00:00:37.870> we<00:00:37.990> are<00:00:38.080> trying<00:00:38.320> to<00:00:38.440> solve 00:00:38.700 --> 00:00:38.710 align:start position:0% could say that we are trying to solve 00:00:38.710 --> 00:00:41.670 align:start position:0% could say that we are trying to solve the<00:00:38.950> root<00:00:39.220> problems<00:00:39.820> that<00:00:40.750> need<00:00:41.020> to<00:00:41.170> be<00:00:41.200> solved 00:00:41.670 --> 00:00:41.680 align:start position:0% the root problems that need to be solved 00:00:41.680 --> 00:00:44.220 align:start position:0% the root problems that need to be solved before<00:00:41.950> any<00:00:42.400> interesting<00:00:43.000> gaps<00:00:43.240> can<00:00:44.170> be 00:00:44.220 --> 00:00:44.230 align:start position:0% before any interesting gaps can be 00:00:44.230 --> 00:00:50.160 align:start position:0% before any interesting gaps can be created<00:00:46.410> you're<00:00:47.410> very<00:00:47.890> inspired<00:00:48.610> by<00:00:49.060> the<00:00:49.630> UNIX 00:00:50.160 --> 00:00:50.170 align:start position:0% created you're very inspired by the UNIX 00:00:50.170 --> 00:00:53.940 align:start position:0% created you're very inspired by the UNIX design<00:00:50.770> philosophy<00:00:52.230> to<00:00:53.230> sum<00:00:53.380> it<00:00:53.410> up<00:00:53.530> simply 00:00:53.940 --> 00:00:53.950 align:start position:0% design philosophy to sum it up simply 00:00:53.950 --> 00:00:57.030 align:start position:0% design philosophy to sum it up simply the<00:00:54.640> UNIX<00:00:54.910> design<00:00:55.210> philosophy<00:00:56.040> encourages 00:00:57.030 --> 00:00:57.040 align:start position:0% the UNIX design philosophy encourages 00:00:57.040 --> 00:01:00.990 align:start position:0% the UNIX design philosophy encourages developers<00:00:57.870> to<00:00:58.870> write<00:00:59.200> programs<00:00:59.770> that<00:01:00.310> do<00:01:00.579> one 00:01:00.990 --> 00:01:01.000 align:start position:0% developers to write programs that do one 00:01:01.000 --> 00:01:04.530 align:start position:0% developers to write programs that do one thing<00:01:01.329> and<00:01:01.660> do<00:01:02.530> it<00:01:02.560> well<00:01:02.890> and<00:01:03.360> to<00:01:04.360> write 00:01:04.530 --> 00:01:04.540 align:start position:0% thing and do it well and to write 00:01:04.540 --> 00:01:08.039 align:start position:0% thing and do it well and to write programs<00:01:05.019> that<00:01:05.110> work<00:01:05.379> together<00:01:06.210> this<00:01:07.210> is<00:01:07.270> this 00:01:08.039 --> 00:01:08.049 align:start position:0% programs that work together this is this 00:01:08.049 --> 00:01:11.340 align:start position:0% programs that work together this is this philosophy<00:01:08.859> underpins<00:01:09.460> all<00:01:09.960> of<00:01:10.960> the<00:01:11.049> UNIX 00:01:11.340 --> 00:01:11.350 align:start position:0% philosophy underpins all of the UNIX 00:01:11.350 --> 00:01:13.380 align:start position:0% philosophy underpins all of the UNIX operating<00:01:11.499> system<00:01:11.829> and<00:01:12.310> it<00:01:12.369> essentially<00:01:13.090> is<00:01:13.329> a 00:01:13.380 --> 00:01:13.390 align:start position:0% operating system and it essentially is a 00:01:13.390 --> 00:01:16.919 align:start position:0% operating system and it essentially is a philosophy<00:01:14.109> of<00:01:14.140> modularity<00:01:15.359> creating<00:01:16.359> small 00:01:16.919 --> 00:01:16.929 align:start position:0% philosophy of modularity creating small 00:01:16.929 --> 00:01:20.849 align:start position:0% philosophy of modularity creating small components<00:01:17.679> laser<00:01:18.520> focusing<00:01:19.179> on<00:01:19.329> them<00:01:19.859> until 00:01:20.849 --> 00:01:20.859 align:start position:0% components laser focusing on them until 00:01:20.859 --> 00:01:24.359 align:start position:0% components laser focusing on them until they<00:01:20.979> are<00:01:21.009> right<00:01:21.429> and<00:01:21.869> then<00:01:23.159> assembling<00:01:24.159> them 00:01:24.359 --> 00:01:24.369 align:start position:0% they are right and then assembling them 00:01:24.369 --> 00:01:26.580 align:start position:0% they are right and then assembling them together<00:01:24.549> and<00:01:24.939> composing<00:01:25.600> them<00:01:25.780> to<00:01:26.350> higher 00:01:26.580 --> 00:01:26.590 align:start position:0% together and composing them to higher 00:01:26.590 --> 00:01:31.080 align:start position:0% together and composing them to higher order<00:01:27.009> systems<00:01:28.289> these<00:01:29.289> are<00:01:29.350> not<00:01:29.740> new<00:01:30.579> ideas 00:01:31.080 --> 00:01:31.090 align:start position:0% order systems these are not new ideas 00:01:31.090 --> 00:01:33.510 align:start position:0% order systems these are not new ideas what<00:01:31.420> I'm<00:01:31.539> talking<00:01:31.869> about<00:01:31.929> right<00:01:32.259> now<00:01:32.459> is<00:01:33.459> a 00:01:33.510 --> 00:01:33.520 align:start position:0% what I'm talking about right now is a 00:01:33.520 --> 00:01:39.260 align:start position:0% what I'm talking about right now is a proven<00:01:34.179> approach<00:01:34.420> to<00:01:35.409> design<00:01:37.829> and 00:01:39.260 --> 00:01:39.270 align:start position:0% proven approach to design and 00:01:39.270 --> 00:01:41.489 align:start position:0% proven approach to design and particularly<00:01:40.270> it<00:01:40.780> is<00:01:41.020> something<00:01:41.229> that<00:01:41.409> we 00:01:41.489 --> 00:01:41.499 align:start position:0% particularly it is something that we 00:01:41.499 --> 00:01:43.529 align:start position:0% particularly it is something that we think<00:01:41.530> it<00:01:42.009> is<00:01:42.130> a<00:01:42.159> design<00:01:42.700> philosophy<00:01:43.329> that<00:01:43.450> we 00:01:43.529 --> 00:01:43.539 align:start position:0% think it is a design philosophy that we 00:01:43.539 --> 00:01:45.959 align:start position:0% think it is a design philosophy that we think<00:01:43.749> is<00:01:43.869> underappreciated<00:01:44.380> in<00:01:45.100> the<00:01:45.819> world 00:01:45.959 --> 00:01:45.969 align:start position:0% think is underappreciated in the world 00:01:45.969 --> 00:01:46.859 align:start position:0% think is underappreciated in the world of<00:01:46.119> blockchains 00:01:46.859 --> 00:01:46.869 align:start position:0% of blockchains 00:01:46.869 --> 00:01:52.399 align:start position:0% of blockchains both<00:01:47.170> on<00:01:47.409> and<00:01:47.859> off<00:01:48.009> chain<00:01:50.999> we<00:01:51.999> are<00:01:52.119> also 00:01:52.399 --> 00:01:52.409 align:start position:0% both on and off chain we are also 00:01:52.409 --> 00:01:56.809 align:start position:0% both on and off chain we are also inspired<00:01:53.409> by<00:01:53.709> the<00:01:53.950> free<00:01:54.279> software<00:01:54.729> movement 00:01:56.809 --> 00:01:56.819 align:start position:0% 00:01:56.819 --> 00:01:59.039 align:start position:0% we<00:01:57.819> think<00:01:58.090> that<00:01:58.209> the<00:01:58.299> free<00:01:58.539> software<00:01:58.959> movement 00:01:59.039 --> 00:01:59.049 align:start position:0% we think that the free software movement 00:01:59.049 --> 00:02:02.099 align:start position:0% we think that the free software movement is<00:01:59.829> the<00:02:00.130> most<00:02:00.459> important<00:02:01.450> cultural 00:02:02.099 --> 00:02:02.109 align:start position:0% is the most important cultural 00:02:02.109 --> 00:02:04.649 align:start position:0% is the most important cultural predecessor<00:02:03.009> to<00:02:03.909> the<00:02:04.060> modern<00:02:04.209> day 00:02:04.649 --> 00:02:04.659 align:start position:0% predecessor to the modern day 00:02:04.659 --> 00:02:06.709 align:start position:0% predecessor to the modern day Renaissance<00:02:05.200> in<00:02:05.499> decentralized<00:02:06.340> technology 00:02:06.709 --> 00:02:06.719 align:start position:0% Renaissance in decentralized technology 00:02:06.719 --> 00:02:11.130 align:start position:0% Renaissance in decentralized technology and<00:02:07.719> because<00:02:08.560> of<00:02:08.590> this<00:02:09.390> when<00:02:10.390> we<00:02:10.570> look<00:02:10.810> out<00:02:10.930> in 00:02:11.130 --> 00:02:11.140 align:start position:0% and because of this when we look out in 00:02:11.140 --> 00:02:12.570 align:start position:0% and because of this when we look out in the<00:02:11.170> world 00:02:12.570 --> 00:02:12.580 align:start position:0% the world 00:02:12.580 --> 00:02:15.360 align:start position:0% the world and<00:02:12.670> we<00:02:12.940> see<00:02:13.150> interesting<00:02:13.780> dabs<00:02:14.370> that 00:02:15.360 --> 00:02:15.370 align:start position:0% and we see interesting dabs that 00:02:15.370 --> 00:02:18.810 align:start position:0% and we see interesting dabs that unfortunately<00:02:16.090> use<00:02:16.750> have<00:02:17.710> useless<00:02:18.340> tokens 00:02:18.810 --> 00:02:18.820 align:start position:0% unfortunately use have useless tokens 00:02:18.820 --> 00:02:22.340 align:start position:0% unfortunately use have useless tokens that<00:02:19.120> have<00:02:19.420> been<00:02:19.540> added<00:02:20.070> we<00:02:21.070> consider<00:02:21.490> it<00:02:21.670> a 00:02:22.340 --> 00:02:22.350 align:start position:0% that have been added we consider it a 00:02:22.350 --> 00:02:26.490 align:start position:0% that have been added we consider it a call<00:02:23.350> to<00:02:23.620> action<00:02:24.840> we<00:02:25.840> don't<00:02:26.020> like<00:02:26.230> useless 00:02:26.490 --> 00:02:26.500 align:start position:0% call to action we don't like useless 00:02:26.500 --> 00:02:29.280 align:start position:0% call to action we don't like useless tokens<00:02:27.010> and<00:02:27.280> we<00:02:27.400> like<00:02:27.670> free<00:02:28.150> dabs<00:02:28.480> and<00:02:28.840> at<00:02:29.110> a 00:02:29.280 --> 00:02:29.290 align:start position:0% tokens and we like free dabs and at a 00:02:29.290 --> 00:02:32.250 align:start position:0% tokens and we like free dabs and at a pub<00:02:29.560> we<00:02:30.220> are<00:02:30.340> committed<00:02:30.880> to<00:02:31.060> freeing<00:02:31.660> dabs 00:02:32.250 --> 00:02:32.260 align:start position:0% pub we are committed to freeing dabs 00:02:32.260 --> 00:02:38.610 align:start position:0% pub we are committed to freeing dabs from<00:02:32.950> useless<00:02:33.280> tokens<00:02:34.740> yeah<00:02:35.740> I<00:02:37.350> knew<00:02:38.350> that<00:02:38.500> be 00:02:38.610 --> 00:02:38.620 align:start position:0% from useless tokens yeah I knew that be 00:02:38.620 --> 00:02:43.890 align:start position:0% from useless tokens yeah I knew that be popular<00:02:40.650> today<00:02:42.120> when<00:02:43.120> people<00:02:43.420> talk<00:02:43.630> to<00:02:43.660> the 00:02:43.890 --> 00:02:43.900 align:start position:0% popular today when people talk to the 00:02:43.900 --> 00:02:46.560 align:start position:0% popular today when people talk to the proprietors<00:02:44.500> of<00:02:44.530> these<00:02:44.800> useless<00:02:45.070> tokens<00:02:45.640> they 00:02:46.560 --> 00:02:46.570 align:start position:0% proprietors of these useless tokens they 00:02:46.570 --> 00:02:49.770 align:start position:0% proprietors of these useless tokens they say<00:02:47.130> aren't<00:02:48.130> you<00:02:48.250> worried<00:02:48.610> somebody's<00:02:49.600> gonna 00:02:49.770 --> 00:02:49.780 align:start position:0% say aren't you worried somebody's gonna 00:02:49.780 --> 00:02:52.530 align:start position:0% say aren't you worried somebody's gonna fork<00:02:50.140> your<00:02:50.290> project<00:02:50.740> and<00:02:51.209> remove<00:02:52.209> the<00:02:52.420> useless 00:02:52.530 --> 00:02:52.540 align:start position:0% fork your project and remove the useless 00:02:52.540 --> 00:02:56.540 align:start position:0% fork your project and remove the useless token<00:02:53.790> it<00:02:54.790> is<00:02:54.970> my<00:02:55.150> hope<00:02:55.420> that<00:02:55.450> in<00:02:56.050> the<00:02:56.140> future 00:02:56.540 --> 00:02:56.550 align:start position:0% token it is my hope that in the future 00:02:56.550 --> 00:03:00.780 align:start position:0% token it is my hope that in the future they<00:02:57.550> will<00:02:57.670> ask<00:02:58.140> aren't<00:02:59.140> you<00:02:59.320> worried<00:02:59.680> that<00:02:59.950> a 00:03:00.780 --> 00:03:00.790 align:start position:0% they will ask aren't you worried that a 00:03:00.790 --> 00:03:03.150 align:start position:0% they will ask aren't you worried that a pub<00:03:01.090> is<00:03:01.570> going<00:03:01.840> to<00:03:01.900> fork<00:03:02.140> your<00:03:02.290> project<00:03:02.740> and 00:03:03.150 --> 00:03:03.160 align:start position:0% pub is going to fork your project and 00:03:03.160 --> 00:03:09.120 align:start position:0% pub is going to fork your project and remove<00:03:03.730> the<00:03:03.910> useless<00:03:04.030> token<00:03:07.380> this<00:03:08.380> is<00:03:08.560> a<00:03:08.620> moral 00:03:09.120 --> 00:03:09.130 align:start position:0% remove the useless token this is a moral 00:03:09.130 --> 00:03:11.790 align:start position:0% remove the useless token this is a moral issue<00:03:10.050> it's<00:03:11.050> something<00:03:11.140> that<00:03:11.470> we<00:03:11.560> feel 00:03:11.790 --> 00:03:11.800 align:start position:0% issue it's something that we feel 00:03:11.800 --> 00:03:14.430 align:start position:0% issue it's something that we feel strongly<00:03:12.220> about<00:03:12.490> so<00:03:12.730> you<00:03:12.820> mark<00:03:13.120> my<00:03:13.390> words<00:03:13.440> we 00:03:14.430 --> 00:03:14.440 align:start position:0% strongly about so you mark my words we 00:03:14.440 --> 00:03:16.710 align:start position:0% strongly about so you mark my words we are<00:03:14.620> here<00:03:15.010> on<00:03:15.190> this<00:03:15.430> earth<00:03:15.610> to<00:03:15.700> do<00:03:16.240> this<00:03:16.450> we<00:03:16.660> are 00:03:16.710 --> 00:03:16.720 align:start position:0% are here on this earth to do this we are 00:03:16.720 --> 00:03:19.979 align:start position:0% are here on this earth to do this we are here<00:03:16.989> to<00:03:17.140> free<00:03:17.470> the<00:03:17.800> dabs<00:03:18.150> we<00:03:19.150> believe<00:03:19.540> in<00:03:19.780> free 00:03:19.979 --> 00:03:19.989 align:start position:0% here to free the dabs we believe in free 00:03:19.989 --> 00:03:24.750 align:start position:0% here to free the dabs we believe in free software<00:03:21.269> in<00:03:22.290> line<00:03:23.290> with<00:03:23.650> the<00:03:23.769> goals<00:03:24.010> of<00:03:24.459> the 00:03:24.750 --> 00:03:24.760 align:start position:0% software in line with the goals of the 00:03:24.760 --> 00:03:27.600 align:start position:0% software in line with the goals of the free<00:03:24.970> software<00:03:25.150> movement<00:03:25.860> we<00:03:26.860> have<00:03:27.040> created 00:03:27.600 --> 00:03:27.610 align:start position:0% free software movement we have created 00:03:27.610 --> 00:03:32.729 align:start position:0% free software movement we have created an<00:03:28.350> ergonomic<00:03:30.360> etherium<00:03:31.360> tool<00:03:31.570> chain<00:03:31.870> to 00:03:32.729 --> 00:03:32.739 align:start position:0% an ergonomic etherium tool chain to 00:03:32.739 --> 00:03:34.759 align:start position:0% an ergonomic etherium tool chain to empower<00:03:33.100> hackers<00:03:33.790> everywhere 00:03:34.759 --> 00:03:34.769 align:start position:0% empower hackers everywhere 00:03:34.769 --> 00:03:37.770 align:start position:0% empower hackers everywhere we<00:03:35.769> originally<00:03:36.040> created<00:03:36.519> it<00:03:36.850> for<00:03:37.480> our<00:03:37.600> own 00:03:37.770 --> 00:03:37.780 align:start position:0% we originally created it for our own 00:03:37.780 --> 00:03:39.840 align:start position:0% we originally created it for our own purposes<00:03:38.400> particularly<00:03:39.400> during<00:03:39.730> the 00:03:39.840 --> 00:03:39.850 align:start position:0% purposes particularly during the 00:03:39.850 --> 00:03:43.050 align:start position:0% purposes particularly during the development<00:03:40.330> of<00:03:40.480> maker<00:03:41.019> Dow<00:03:41.290> a<00:03:41.850> stable<00:03:42.850> coin 00:03:43.050 --> 00:03:43.060 align:start position:0% development of maker Dow a stable coin 00:03:43.060 --> 00:03:44.460 align:start position:0% development of maker Dow a stable coin project<00:03:43.510> that<00:03:43.630> I'm<00:03:43.720> gonna<00:03:43.840> be<00:03:44.019> talking<00:03:44.200> about 00:03:44.460 --> 00:03:44.470 align:start position:0% project that I'm gonna be talking about 00:03:44.470 --> 00:03:48.600 align:start position:0% project that I'm gonna be talking about tomorrow<00:03:44.890> which<00:03:45.760> you<00:03:45.790> should<00:03:46.060> tune<00:03:46.269> into<00:03:47.610> but 00:03:48.600 --> 00:03:48.610 align:start position:0% tomorrow which you should tune into but 00:03:48.610 --> 00:03:51.780 align:start position:0% tomorrow which you should tune into but we<00:03:49.300> share<00:03:49.660> these<00:03:49.870> tools<00:03:50.140> using<00:03:50.950> the<00:03:51.459> NYX 00:03:51.780 --> 00:03:51.790 align:start position:0% we share these tools using the NYX 00:03:51.790 --> 00:03:56.449 align:start position:0% we share these tools using the NYX package<00:03:52.420> manager<00:03:53.610> no<00:03:54.610> unfortunately<00:03:55.290> yeah 00:03:56.449 --> 00:03:56.459 align:start position:0% package manager no unfortunately yeah 00:03:56.459 --> 00:03:58.620 align:start position:0% package manager no unfortunately yeah give<00:03:57.459> it<00:03:57.489> up<00:03:57.610> for<00:03:57.640> the<00:03:57.820> next<00:03:57.970> package<00:03:58.239> manager 00:03:58.620 --> 00:03:58.630 align:start position:0% give it up for the next package manager 00:03:58.630 --> 00:04:02.310 align:start position:0% give it up for the next package manager for<00:04:00.660> those<00:04:01.660> of<00:04:01.840> you<00:04:01.930> who<00:04:02.050> don't<00:04:02.260> know 00:04:02.310 --> 00:04:02.320 align:start position:0% for those of you who don't know 00:04:02.320 --> 00:04:03.870 align:start position:0% for those of you who don't know unfortunately<00:04:02.980> I<00:04:03.010> don't<00:04:03.100> have<00:04:03.280> any<00:04:03.550> time<00:04:03.850> to 00:04:03.870 --> 00:04:03.880 align:start position:0% unfortunately I don't have any time to 00:04:03.880 --> 00:04:04.680 align:start position:0% unfortunately I don't have any time to talk<00:04:04.150> about<00:04:04.300> it 00:04:04.680 --> 00:04:04.690 align:start position:0% talk about it 00:04:04.690 --> 00:04:12.570 align:start position:0% talk about it but<00:04:05.500> I<00:04:05.739> will<00:04:05.950> tease<00:04:06.280> it<00:04:06.519> with<00:04:07.209> this<00:04:10.830> society<00:04:11.830> is 00:04:12.570 --> 00:04:12.580 align:start position:0% but I will tease it with this society is 00:04:12.580 --> 00:04:15.259 align:start position:0% but I will tease it with this society is just<00:04:13.060> beginning<00:04:13.330> to<00:04:13.660> feel<00:04:14.049> the<00:04:14.290> effects<00:04:14.650> of 00:04:15.259 --> 00:04:15.269 align:start position:0% just beginning to feel the effects of 00:04:15.269 --> 00:04:18.469 align:start position:0% just beginning to feel the effects of immutable<00:04:16.269> hash<00:04:16.660> based<00:04:17.049> data<00:04:17.590> structures 00:04:18.469 --> 00:04:18.479 align:start position:0% immutable hash based data structures 00:04:18.479 --> 00:04:24.510 align:start position:0% immutable hash based data structures from<00:04:19.479> get<00:04:19.979> to<00:04:20.979> block<00:04:21.250> chains<00:04:21.609> to<00:04:22.510> ipfs<00:04:23.310> it<00:04:24.310> is 00:04:24.510 --> 00:04:24.520 align:start position:0% from get to block chains to ipfs it is 00:04:24.520 --> 00:04:25.700 align:start position:0% from get to block chains to ipfs it is clear 00:04:25.700 --> 00:04:25.710 align:start position:0% clear 00:04:25.710 --> 00:04:27.890 align:start position:0% clear this<00:04:25.919> method<00:04:26.280> of<00:04:26.340> organizing<00:04:26.729> data<00:04:27.090> is<00:04:27.419> having 00:04:27.890 --> 00:04:27.900 align:start position:0% this method of organizing data is having 00:04:27.900 --> 00:04:30.320 align:start position:0% this method of organizing data is having profound<00:04:28.380> effects<00:04:28.919> on<00:04:29.069> the<00:04:29.910> way<00:04:30.030> that<00:04:30.210> we 00:04:30.320 --> 00:04:30.330 align:start position:0% profound effects on the way that we 00:04:30.330 --> 00:04:33.159 align:start position:0% profound effects on the way that we think<00:04:30.479> about<00:04:30.810> computers<00:04:31.680> and<00:04:31.949> applications 00:04:33.159 --> 00:04:33.169 align:start position:0% think about computers and applications 00:04:33.169 --> 00:04:37.670 align:start position:0% think about computers and applications Nix<00:04:34.169> OS<00:04:34.889> and<00:04:35.340> the<00:04:35.699> NYX<00:04:35.940> package<00:04:36.360> manager<00:04:36.810> is 00:04:37.670 --> 00:04:37.680 align:start position:0% Nix OS and the NYX package manager is 00:04:37.680 --> 00:04:41.480 align:start position:0% Nix OS and the NYX package manager is what<00:04:37.949> happens<00:04:38.400> when<00:04:39.360> you<00:04:39.449> combine<00:04:39.630> Linux<00:04:40.490> with 00:04:41.480 --> 00:04:41.490 align:start position:0% what happens when you combine Linux with 00:04:41.490 --> 00:04:45.230 align:start position:0% what happens when you combine Linux with immutable<00:04:42.060> hash<00:04:42.270> based<00:04:42.509> data<00:04:42.840> structures<00:04:44.240> and 00:04:45.230 --> 00:04:45.240 align:start position:0% immutable hash based data structures and 00:04:45.240 --> 00:04:48.860 align:start position:0% immutable hash based data structures and I<00:04:45.479> will<00:04:45.599> leave<00:04:45.780> it<00:04:45.900> at<00:04:46.020> that<00:04:46.050> so<00:04:47.630> on<00:04:48.630> to<00:04:48.840> the 00:04:48.860 --> 00:04:48.870 align:start position:0% I will leave it at that so on to the 00:04:48.870 --> 00:04:50.779 align:start position:0% I will leave it at that so on to the tools<00:04:49.139> what<00:04:49.410> do<00:04:49.470> we<00:04:49.560> distribute<00:04:49.830> the<00:04:50.490> first 00:04:50.779 --> 00:04:50.789 align:start position:0% tools what do we distribute the first 00:04:50.789 --> 00:04:54.290 align:start position:0% tools what do we distribute the first one<00:04:51.000> is<00:04:51.210> called<00:04:51.419> Seth<00:04:51.840> Seth<00:04:52.770> is<00:04:53.039> the<00:04:53.610> ethereum 00:04:54.290 --> 00:04:54.300 align:start position:0% one is called Seth Seth is the ethereum 00:04:54.300 --> 00:04:57.830 align:start position:0% one is called Seth Seth is the ethereum Swiss<00:04:54.840> Army<00:04:55.319> knife<00:04:55.789> if<00:04:56.789> you<00:04:57.060> it<00:04:57.300> helps<00:04:57.539> you<00:04:57.630> use 00:04:57.830 --> 00:04:57.840 align:start position:0% Swiss Army knife if you it helps you use 00:04:57.840 --> 00:05:00.379 align:start position:0% Swiss Army knife if you it helps you use the<00:04:58.020> etherium<00:04:58.530> api<00:04:58.889> if<00:04:59.490> you've<00:04:59.699> ever<00:04:59.849> used<00:04:59.940> the 00:05:00.379 --> 00:05:00.389 align:start position:0% the etherium api if you've ever used the 00:05:00.389 --> 00:05:02.810 align:start position:0% the etherium api if you've ever used the etherium<00:05:00.870> api<00:05:01.139> you<00:05:01.590> know<00:05:01.800> that<00:05:02.220> it's<00:05:02.340> a<00:05:02.400> bit<00:05:02.610> of 00:05:02.810 --> 00:05:02.820 align:start position:0% etherium api you know that it's a bit of 00:05:02.820 --> 00:05:06.800 align:start position:0% etherium api you know that it's a bit of a<00:05:02.910> pain<00:05:03.590> it's<00:05:04.590> got<00:05:04.740> curl<00:05:05.130> it's<00:05:05.789> got<00:05:05.970> post<00:05:06.330> you 00:05:06.800 --> 00:05:06.810 align:start position:0% a pain it's got curl it's got post you 00:05:06.810 --> 00:05:08.960 align:start position:0% a pain it's got curl it's got post you have<00:05:06.900> to<00:05:06.990> memorize<00:05:07.440> all<00:05:07.710> these<00:05:07.830> RPC<00:05:08.430> methods 00:05:08.960 --> 00:05:08.970 align:start position:0% have to memorize all these RPC methods 00:05:08.970 --> 00:05:11.839 align:start position:0% have to memorize all these RPC methods it's<00:05:09.330> annoying<00:05:09.840> using<00:05:10.770> Seth<00:05:11.039> makes<00:05:11.580> it 00:05:11.839 --> 00:05:11.849 align:start position:0% it's annoying using Seth makes it 00:05:11.849 --> 00:05:14.570 align:start position:0% it's annoying using Seth makes it delightful<00:05:12.380> if<00:05:13.380> I<00:05:13.530> wanted<00:05:13.800> to<00:05:13.949> send<00:05:14.250> a 00:05:14.570 --> 00:05:14.580 align:start position:0% delightful if I wanted to send a 00:05:14.580 --> 00:05:18.529 align:start position:0% delightful if I wanted to send a function<00:05:15.180> call<00:05:15.389> to<00:05:15.830> a<00:05:16.830> smart<00:05:17.250> contract<00:05:17.539> using 00:05:18.529 --> 00:05:18.539 align:start position:0% function call to a smart contract using 00:05:18.539 --> 00:05:20.870 align:start position:0% function call to a smart contract using the<00:05:18.750> etherium<00:05:19.169> RPC<00:05:19.620> right<00:05:19.860> now<00:05:20.009> it<00:05:20.669> would<00:05:20.849> be 00:05:20.870 --> 00:05:20.880 align:start position:0% the etherium RPC right now it would be 00:05:20.880 --> 00:05:25.159 align:start position:0% the etherium RPC right now it would be curl<00:05:21.389> blah<00:05:21.960> blah<00:05:22.440> blah<00:05:22.949> -<00:05:23.280> ex<00:05:23.849> blah<00:05:24.270> blah<00:05:24.690> blah 00:05:25.159 --> 00:05:25.169 align:start position:0% curl blah blah blah - ex blah blah blah 00:05:25.169 --> 00:05:27.350 align:start position:0% curl blah blah blah - ex blah blah blah encoding<00:05:25.919> blah<00:05:26.130> blah<00:05:26.430> blah<00:05:26.639> is<00:05:26.759> horrible 00:05:27.350 --> 00:05:27.360 align:start position:0% encoding blah blah blah is horrible 00:05:27.360 --> 00:05:29.839 align:start position:0% encoding blah blah blah is horrible with<00:05:27.720> Seth<00:05:27.990> it's<00:05:28.289> Seth<00:05:28.650> send<00:05:29.250> address 00:05:29.839 --> 00:05:29.849 align:start position:0% with Seth it's Seth send address 00:05:29.849 --> 00:05:32.960 align:start position:0% with Seth it's Seth send address function<00:05:30.479> name<00:05:30.630> parameters<00:05:31.199> boom<00:05:31.820> you're<00:05:32.820> off 00:05:32.960 --> 00:05:32.970 align:start position:0% function name parameters boom you're off 00:05:32.970 --> 00:05:35.180 align:start position:0% function name parameters boom you're off to<00:05:33.180> the<00:05:33.210> races<00:05:33.300> it's<00:05:33.990> that<00:05:34.229> simple<00:05:34.530> it<00:05:34.830> reads 00:05:35.180 --> 00:05:35.190 align:start position:0% to the races it's that simple it reads 00:05:35.190 --> 00:05:39.740 align:start position:0% to the races it's that simple it reads like<00:05:35.490> prose<00:05:36.470> is<00:05:37.470> delightful<00:05:38.449> if<00:05:39.449> you<00:05:39.539> want<00:05:39.659> to 00:05:39.740 --> 00:05:39.750 align:start position:0% like prose is delightful if you want to 00:05:39.750 --> 00:05:43.249 align:start position:0% like prose is delightful if you want to read<00:05:39.900> from<00:05:40.080> the<00:05:40.229> blockchain<00:05:40.440> it's<00:05:40.919> s<00:05:41.310> T<00:05:41.880> X<00:05:42.259> hash 00:05:43.249 --> 00:05:43.259 align:start position:0% read from the blockchain it's s T X hash 00:05:43.259 --> 00:05:45.290 align:start position:0% read from the blockchain it's s T X hash boom<00:05:43.949> and<00:05:44.219> it's<00:05:44.340> out<00:05:44.490> there<00:05:44.699> you<00:05:44.909> can<00:05:45.150> output 00:05:45.290 --> 00:05:45.300 align:start position:0% boom and it's out there you can output 00:05:45.300 --> 00:05:47.089 align:start position:0% boom and it's out there you can output it<00:05:45.509> as<00:05:45.599> plain<00:05:45.840> text<00:05:46.050> you<00:05:46.500> can<00:05:46.590> output<00:05:46.919> it<00:05:47.009> as 00:05:47.089 --> 00:05:47.099 align:start position:0% it as plain text you can output it as 00:05:47.099 --> 00:05:49.730 align:start position:0% it as plain text you can output it as JSON<00:05:47.580> you<00:05:47.789> can<00:05:48.030> filter<00:05:48.270> by<00:05:48.389> field<00:05:48.840> these<00:05:49.380> tools 00:05:49.730 --> 00:05:49.740 align:start position:0% JSON you can filter by field these tools 00:05:49.740 --> 00:05:52.249 align:start position:0% JSON you can filter by field these tools they<00:05:50.009> work<00:05:50.280> together<00:05:50.520> you<00:05:51.300> can<00:05:51.479> compose<00:05:51.870> this 00:05:52.249 --> 00:05:52.259 align:start position:0% they work together you can compose this 00:05:52.259 --> 00:05:55.070 align:start position:0% they work together you can compose this into<00:05:52.919> a<00:05:52.949> more<00:05:53.159> interesting<00:05:53.520> tool<00:05:53.880> on<00:05:54.090> top<00:05:54.300> the 00:05:55.070 --> 00:05:55.080 align:start position:0% into a more interesting tool on top the 00:05:55.080 --> 00:05:56.689 align:start position:0% into a more interesting tool on top the next<00:05:55.500> tools<00:05:55.860> I'm<00:05:55.949> going<00:05:55.979> to<00:05:56.099> describe<00:05:56.370> build 00:05:56.689 --> 00:05:56.699 align:start position:0% next tools I'm going to describe build 00:05:56.699 --> 00:05:58.520 align:start position:0% next tools I'm going to describe build on<00:05:56.820> top<00:05:57.060> of<00:05:57.240> stuff<00:05:57.419> I'd<00:05:57.659> make<00:05:58.139> her<00:05:58.259> doubt<00:05:58.409> we 00:05:58.520 --> 00:05:58.530 align:start position:0% on top of stuff I'd make her doubt we 00:05:58.530 --> 00:06:00.589 align:start position:0% on top of stuff I'd make her doubt we build<00:05:58.740> many<00:05:58.979> we<00:05:59.669> build<00:05:59.849> our<00:05:59.940> entire<00:06:00.240> feed 00:06:00.589 --> 00:06:00.599 align:start position:0% build many we build our entire feed 00:06:00.599 --> 00:06:02.959 align:start position:0% build many we build our entire feed infrastructure<00:06:01.320> on<00:06:01.469> top<00:06:01.800> of<00:06:02.009> Seth<00:06:02.280> if<00:06:02.520> you're 00:06:02.959 --> 00:06:02.969 align:start position:0% infrastructure on top of Seth if you're 00:06:02.969 --> 00:06:06.020 align:start position:0% infrastructure on top of Seth if you're doing<00:06:03.180> anything<00:06:03.960> interesting<00:06:04.289> on<00:06:05.070> the 00:06:06.020 --> 00:06:06.030 align:start position:0% doing anything interesting on the 00:06:06.030 --> 00:06:07.760 align:start position:0% doing anything interesting on the blockchain<00:06:06.300> that's<00:06:06.840> reading<00:06:07.229> information 00:06:07.760 --> 00:06:07.770 align:start position:0% blockchain that's reading information 00:06:07.770 --> 00:06:09.740 align:start position:0% blockchain that's reading information from<00:06:07.889> the<00:06:08.009> blockchain<00:06:08.250> and<00:06:08.849> using<00:06:09.240> it<00:06:09.389> on<00:06:09.570> the 00:06:09.740 --> 00:06:09.750 align:start position:0% from the blockchain and using it on the 00:06:09.750 --> 00:06:10.459 align:start position:0% from the blockchain and using it on the command<00:06:09.990> line 00:06:10.459 --> 00:06:10.469 align:start position:0% command line 00:06:10.469 --> 00:06:13.339 align:start position:0% command line I<00:06:10.500> guarantee<00:06:11.659> Seth<00:06:12.659> will<00:06:12.900> make<00:06:13.050> your<00:06:13.199> life 00:06:13.339 --> 00:06:13.349 align:start position:0% I guarantee Seth will make your life 00:06:13.349 --> 00:06:15.589 align:start position:0% I guarantee Seth will make your life easier<00:06:13.949> I<00:06:14.099> encourage<00:06:14.849> you<00:06:14.969> to<00:06:15.000> look<00:06:15.210> into<00:06:15.389> it 00:06:15.589 --> 00:06:15.599 align:start position:0% easier I encourage you to look into it 00:06:15.599 --> 00:06:18.080 align:start position:0% easier I encourage you to look into it if<00:06:15.719> you<00:06:15.840> want<00:06:15.990> to<00:06:16.050> get<00:06:16.169> logs<00:06:16.500> from<00:06:17.400> a<00:06:17.550> contract 00:06:18.080 --> 00:06:18.090 align:start position:0% if you want to get logs from a contract 00:06:18.090 --> 00:06:20.959 align:start position:0% if you want to get logs from a contract Seth<00:06:18.690> logs<00:06:19.259> address<00:06:19.889> there<00:06:20.460> they<00:06:20.580> are 00:06:20.959 --> 00:06:20.969 align:start position:0% Seth logs address there they are 00:06:20.969 --> 00:06:23.240 align:start position:0% Seth logs address there they are if<00:06:21.659> you<00:06:21.810> wanted<00:06:22.020> to<00:06:22.110> stay<00:06:22.349> alive<00:06:22.650> in<00:06:22.860> report 00:06:23.240 --> 00:06:23.250 align:start position:0% if you wanted to stay alive in report 00:06:23.250 --> 00:06:25.939 align:start position:0% if you wanted to stay alive in report logs<00:06:23.460> as<00:06:23.639> they<00:06:23.669> come<00:06:23.969> in<00:06:24.090> -<00:06:24.389> -<00:06:24.599> follow<00:06:24.930> up<00:06:25.080> you 00:06:25.939 --> 00:06:25.949 align:start position:0% logs as they come in - - follow up you 00:06:25.949 --> 00:06:27.920 align:start position:0% logs as they come in - - follow up you can<00:06:26.130> compose<00:06:26.550> some<00:06:27.030> commands<00:06:27.449> here<00:06:27.719> we<00:06:27.810> have 00:06:27.920 --> 00:06:27.930 align:start position:0% can compose some commands here we have 00:06:27.930 --> 00:06:33.110 align:start position:0% can compose some commands here we have Seth<00:06:28.259> sin<00:06:28.949> address<00:06:29.729> value<00:06:30.770> sub<00:06:31.770> shell<00:06:32.130> and<00:06:32.490> a 00:06:33.110 --> 00:06:33.120 align:start position:0% Seth sin address value sub shell and a 00:06:33.120 --> 00:06:34.790 align:start position:0% Seth sin address value sub shell and a nice<00:06:33.300> little<00:06:33.539> conversion<00:06:34.110> function<00:06:34.469> isn't 00:06:34.790 --> 00:06:34.800 align:start position:0% nice little conversion function isn't 00:06:34.800 --> 00:06:36.110 align:start position:0% nice little conversion function isn't annoying<00:06:34.979> going<00:06:35.490> from<00:06:35.639> eath<00:06:35.789> to<00:06:36.000> way 00:06:36.110 --> 00:06:36.120 align:start position:0% annoying going from eath to way 00:06:36.120 --> 00:06:38.420 align:start position:0% annoying going from eath to way sometimes 00:06:38.420 --> 00:06:38.430 align:start position:0% sometimes 00:06:38.430 --> 00:06:44.429 align:start position:0% sometimes the<00:06:39.430> next<00:06:39.819> tool<00:06:40.409> is<00:06:41.409> called<00:06:41.619> dap<00:06:42.210> dap<00:06:43.210> is<00:06:44.199> our 00:06:44.429 --> 00:06:44.439 align:start position:0% the next tool is called dap dap is our 00:06:44.439 --> 00:06:46.350 align:start position:0% the next tool is called dap dap is our developer<00:06:44.919> multi-tool<00:06:45.430> it<00:06:45.789> helps<00:06:46.029> us<00:06:46.149> use 00:06:46.350 --> 00:06:46.360 align:start position:0% developer multi-tool it helps us use 00:06:46.360 --> 00:06:50.459 align:start position:0% developer multi-tool it helps us use solidity<00:06:46.839> and<00:06:46.930> helps<00:06:47.229> us<00:06:47.319> develop<00:06:47.469> taps<00:06:49.469> tap 00:06:50.459 --> 00:06:50.469 align:start position:0% solidity and helps us develop taps tap 00:06:50.469 --> 00:06:53.369 align:start position:0% solidity and helps us develop taps tap build<00:06:51.330> invokes<00:06:52.330> the<00:06:52.479> solidity<00:06:52.809> compiler<00:06:53.169> the 00:06:53.369 --> 00:06:53.379 align:start position:0% build invokes the solidity compiler the 00:06:53.379 --> 00:06:56.730 align:start position:0% build invokes the solidity compiler the C++<00:06:54.159> compiler<00:06:54.520> which<00:06:54.879> is<00:06:55.059> very<00:06:55.419> fast<00:06:55.809> as 00:06:56.730 --> 00:06:56.740 align:start position:0% C++ compiler which is very fast as 00:06:56.740 --> 00:06:58.350 align:start position:0% C++ compiler which is very fast as possible<00:06:57.309> you're<00:06:57.430> not<00:06:57.460> used<00:06:57.789> to<00:06:57.909> using<00:06:57.969> it 00:06:58.350 --> 00:06:58.360 align:start position:0% possible you're not used to using it 00:06:58.360 --> 00:07:01.529 align:start position:0% possible you're not used to using it you'll<00:06:58.599> be<00:06:58.749> shocked<00:06:59.080> by<00:06:59.710> how<00:06:59.830> fast<00:07:00.159> it<00:07:00.339> is<00:07:00.539> is 00:07:01.529 --> 00:07:01.539 align:start position:0% you'll be shocked by how fast it is is 00:07:01.539 --> 00:07:03.269 align:start position:0% you'll be shocked by how fast it is is much<00:07:01.960> faster<00:07:02.169> than<00:07:02.469> the<00:07:02.589> JavaScript<00:07:03.039> compiler 00:07:03.269 --> 00:07:03.279 align:start position:0% much faster than the JavaScript compiler 00:07:03.279 --> 00:07:05.629 align:start position:0% much faster than the JavaScript compiler and<00:07:03.610> if<00:07:03.969> you're<00:07:04.089> in<00:07:04.149> a<00:07:04.210> hurry<00:07:04.360> to<00:07:04.659> make<00:07:04.779> a<00:07:04.839> DAP<00:07:05.110> I 00:07:05.629 --> 00:07:05.639 align:start position:0% and if you're in a hurry to make a DAP I 00:07:05.639 --> 00:07:08.309 align:start position:0% and if you're in a hurry to make a DAP I you<00:07:06.639> really<00:07:06.879> want<00:07:07.149> to<00:07:07.210> invoke<00:07:07.479> the<00:07:07.749> C++ 00:07:08.309 --> 00:07:08.319 align:start position:0% you really want to invoke the C++ 00:07:08.319 --> 00:07:12.029 align:start position:0% you really want to invoke the C++ solidity<00:07:08.919> compiler<00:07:09.479> it<00:07:10.479> has<00:07:10.629> testing<00:07:11.199> here's 00:07:12.029 --> 00:07:12.039 align:start position:0% solidity compiler it has testing here's 00:07:12.039 --> 00:07:14.879 align:start position:0% solidity compiler it has testing here's a<00:07:12.069> native<00:07:12.550> solidity<00:07:13.180> unit<00:07:13.809> test<00:07:14.050> runner<00:07:14.319> if 00:07:14.879 --> 00:07:14.889 align:start position:0% a native solidity unit test runner if 00:07:14.889 --> 00:07:16.019 align:start position:0% a native solidity unit test runner if you<00:07:14.949> don't<00:07:15.099> want<00:07:15.219> to<00:07:15.279> switch<00:07:15.520> to<00:07:15.729> some<00:07:15.909> other 00:07:16.019 --> 00:07:16.029 align:start position:0% you don't want to switch to some other 00:07:16.029 --> 00:07:17.699 align:start position:0% you don't want to switch to some other programming<00:07:16.479> language<00:07:16.930> to<00:07:17.139> write<00:07:17.229> your<00:07:17.409> tests 00:07:17.699 --> 00:07:17.709 align:start position:0% programming language to write your tests 00:07:17.709 --> 00:07:19.379 align:start position:0% programming language to write your tests you<00:07:17.860> want<00:07:18.009> to<00:07:18.099> keep<00:07:18.580> that<00:07:18.759> context<00:07:19.300> on 00:07:19.379 --> 00:07:19.389 align:start position:0% you want to keep that context on 00:07:19.389 --> 00:07:21.059 align:start position:0% you want to keep that context on solidity<00:07:19.749> you<00:07:20.409> can<00:07:20.529> write<00:07:20.680> your<00:07:20.800> tests<00:07:20.979> in 00:07:21.059 --> 00:07:21.069 align:start position:0% solidity you can write your tests in 00:07:21.069 --> 00:07:25.320 align:start position:0% solidity you can write your tests in solidity<00:07:21.459> and<00:07:22.319> it<00:07:23.319> has<00:07:23.469> stack<00:07:23.889> traces<00:07:24.330> isn't 00:07:25.320 --> 00:07:25.330 align:start position:0% solidity and it has stack traces isn't 00:07:25.330 --> 00:07:27.420 align:start position:0% solidity and it has stack traces isn't that<00:07:25.419> nice<00:07:25.659> never<00:07:26.289> had<00:07:26.409> stack<00:07:26.680> traces<00:07:26.949> before 00:07:27.420 --> 00:07:27.430 align:start position:0% that nice never had stack traces before 00:07:27.430 --> 00:07:30.659 align:start position:0% that nice never had stack traces before it's<00:07:27.550> solidity<00:07:28.050> so<00:07:29.050> it<00:07:29.259> makes<00:07:29.499> debugging<00:07:30.069> much 00:07:30.659 --> 00:07:30.669 align:start position:0% it's solidity so it makes debugging much 00:07:30.669 --> 00:07:32.309 align:start position:0% it's solidity so it makes debugging much much<00:07:30.879> easier<00:07:30.909> and<00:07:31.419> it<00:07:31.479> runs<00:07:31.689> your<00:07:31.839> tests 00:07:32.309 --> 00:07:32.319 align:start position:0% much easier and it runs your tests 00:07:32.319 --> 00:07:36.329 align:start position:0% much easier and it runs your tests really<00:07:33.069> fast<00:07:33.959> I'm<00:07:34.959> talking<00:07:35.379> 150<00:07:35.889> tests<00:07:36.279> in 00:07:36.329 --> 00:07:36.339 align:start position:0% really fast I'm talking 150 tests in 00:07:36.339 --> 00:07:39.389 align:start position:0% really fast I'm talking 150 tests in under<00:07:36.580> a<00:07:36.610> second<00:07:37.029> easy<00:07:37.599> and<00:07:38.259> the<00:07:38.709> reason<00:07:39.099> how 00:07:39.389 --> 00:07:39.399 align:start position:0% under a second easy and the reason how 00:07:39.399 --> 00:07:41.189 align:start position:0% under a second easy and the reason how to<00:07:39.430> run<00:07:39.639> them<00:07:39.819> so<00:07:39.969> fast<00:07:40.149> is<00:07:40.599> because<00:07:40.749> it<00:07:41.020> has 00:07:41.189 --> 00:07:41.199 align:start position:0% to run them so fast is because it has 00:07:41.199 --> 00:07:44.879 align:start position:0% to run them so fast is because it has its<00:07:41.559> own<00:07:41.680> e<00:07:43.349> own<00:07:44.349> oh<00:07:44.499> I'm<00:07:44.620> sorry 00:07:44.879 --> 00:07:44.889 align:start position:0% its own e own oh I'm sorry 00:07:44.889 --> 00:07:47.749 align:start position:0% its own e own oh I'm sorry all<00:07:45.219> right<00:07:45.339> talk<00:07:45.459> about<00:07:45.639> that<00:07:45.759> as<00:07:45.939> dap<00:07:46.689> create 00:07:47.749 --> 00:07:47.759 align:start position:0% all right talk about that as dap create 00:07:47.759 --> 00:07:51.179 align:start position:0% all right talk about that as dap create deb<00:07:48.759> create<00:07:49.059> similar<00:07:49.930> sort<00:07:50.379> of<00:07:50.499> trying<00:07:51.159> to 00:07:51.179 --> 00:07:51.189 align:start position:0% deb create similar sort of trying to 00:07:51.189 --> 00:07:52.949 align:start position:0% deb create similar sort of trying to make<00:07:51.279> using<00:07:51.729> the<00:07:51.879> etherium<00:07:52.240> api<00:07:52.509> a<00:07:52.599> little<00:07:52.870> bit 00:07:52.949 --> 00:07:52.959 align:start position:0% make using the etherium api a little bit 00:07:52.959 --> 00:07:54.809 align:start position:0% make using the etherium api a little bit more<00:07:53.080> prosaic<00:07:53.589> we've<00:07:54.009> got<00:07:54.219> debt<00:07:54.519> if<00:07:54.610> you<00:07:54.669> want 00:07:54.809 --> 00:07:54.819 align:start position:0% more prosaic we've got debt if you want 00:07:54.819 --> 00:07:57.449 align:start position:0% more prosaic we've got debt if you want to<00:07:54.879> deploy<00:07:55.120> adapt<00:07:55.539> to<00:07:56.439> the<00:07:56.529> blockchain<00:07:56.740> it's 00:07:57.449 --> 00:07:57.459 align:start position:0% to deploy adapt to the blockchain it's 00:07:57.459 --> 00:08:00.420 align:start position:0% to deploy adapt to the blockchain it's damp<00:07:57.999> create<00:07:58.659> type<00:07:59.229> name<00:07:59.469> parameters<00:08:00.099> boom 00:08:00.420 --> 00:08:00.430 align:start position:0% damp create type name parameters boom 00:08:00.430 --> 00:08:02.610 align:start position:0% damp create type name parameters boom you<00:08:01.360> can<00:08:01.479> see<00:08:01.689> us<00:08:01.779> using<00:08:02.110> Seth<00:08:02.349> in<00:08:02.529> the 00:08:02.610 --> 00:08:02.620 align:start position:0% you can see us using Seth in the 00:08:02.620 --> 00:08:04.290 align:start position:0% you can see us using Seth in the background<00:08:03.009> there<00:08:03.189> like<00:08:03.580> I<00:08:03.699> said<00:08:03.909> these<00:08:04.029> tools 00:08:04.290 --> 00:08:04.300 align:start position:0% background there like I said these tools 00:08:04.300 --> 00:08:06.269 align:start position:0% background there like I said these tools they<00:08:04.479> build<00:08:04.749> on<00:08:05.050> top<00:08:05.259> of<00:08:05.379> each<00:08:05.529> other<00:08:05.709> this<00:08:06.009> is 00:08:06.269 --> 00:08:06.279 align:start position:0% they build on top of each other this is 00:08:06.279 --> 00:08:08.369 align:start position:0% they build on top of each other this is the<00:08:06.490> UNIX<00:08:06.849> design<00:08:07.119> philosophy<00:08:07.689> in<00:08:07.839> action 00:08:08.369 --> 00:08:08.379 align:start position:0% the UNIX design philosophy in action 00:08:08.379 --> 00:08:12.509 align:start position:0% the UNIX design philosophy in action people<00:08:08.740> is<00:08:09.189> very<00:08:09.449> very<00:08:10.449> nice<00:08:11.169> way<00:08:11.469> to<00:08:11.740> build<00:08:12.309> on 00:08:12.509 --> 00:08:12.519 align:start position:0% people is very very nice way to build on 00:08:12.519 --> 00:08:15.480 align:start position:0% people is very very nice way to build on top<00:08:12.699> of<00:08:12.879> your<00:08:13.029> previous<00:08:13.509> achievements<00:08:14.490> by 00:08:15.480 --> 00:08:15.490 align:start position:0% top of your previous achievements by 00:08:15.490 --> 00:08:18.480 align:start position:0% top of your previous achievements by making<00:08:15.819> things<00:08:15.999> modular<00:08:17.069> like<00:08:18.069> I<00:08:18.159> was<00:08:18.309> saying 00:08:18.480 --> 00:08:18.490 align:start position:0% making things modular like I was saying 00:08:18.490 --> 00:08:20.100 align:start position:0% making things modular like I was saying the<00:08:18.639> reason<00:08:18.759> that<00:08:18.969> tap<00:08:19.180> runs<00:08:19.509> its<00:08:19.659> test<00:08:19.959> so 00:08:20.100 --> 00:08:20.110 align:start position:0% the reason that tap runs its test so 00:08:20.110 --> 00:08:21.540 align:start position:0% the reason that tap runs its test so fast<00:08:20.349> is<00:08:20.589> because<00:08:20.860> it<00:08:20.949> uses<00:08:21.249> something<00:08:21.430> called 00:08:21.540 --> 00:08:21.550 align:start position:0% fast is because it uses something called 00:08:21.550 --> 00:08:24.959 align:start position:0% fast is because it uses something called H<00:08:21.879> EVM<00:08:22.539> under<00:08:23.139> the<00:08:23.229> hood<00:08:23.409> which<00:08:24.189> is<00:08:24.309> a<00:08:24.339> Haskell 00:08:24.959 --> 00:08:24.969 align:start position:0% H EVM under the hood which is a Haskell 00:08:24.969 --> 00:08:28.980 align:start position:0% H EVM under the hood which is a Haskell EVM<00:08:25.959> execution<00:08:26.709> environment<00:08:27.360> we<00:08:28.360> created<00:08:28.869> a 00:08:28.980 --> 00:08:28.990 align:start position:0% EVM execution environment we created a 00:08:28.990 --> 00:08:31.189 align:start position:0% EVM execution environment we created a chi<00:08:29.169> VM<00:08:29.469> for<00:08:30.249> a<00:08:30.309> few<00:08:30.550> different<00:08:30.639> reasons 00:08:31.189 --> 00:08:31.199 align:start position:0% chi VM for a few different reasons 00:08:31.199 --> 00:08:33.750 align:start position:0% chi VM for a few different reasons mainly<00:08:32.199> around<00:08:32.529> verification<00:08:33.339> we're<00:08:33.669> gonna 00:08:33.750 --> 00:08:33.760 align:start position:0% mainly around verification we're gonna 00:08:33.760 --> 00:08:35.850 align:start position:0% mainly around verification we're gonna link<00:08:34.120> it<00:08:34.180> up<00:08:34.329> to<00:08:34.419> other<00:08:34.599> interesting<00:08:35.199> haskell 00:08:35.850 --> 00:08:35.860 align:start position:0% link it up to other interesting haskell 00:08:35.860 --> 00:08:38.009 align:start position:0% link it up to other interesting haskell verification<00:08:36.490> tools<00:08:36.669> like<00:08:36.819> quick<00:08:37.029> check<00:08:37.360> but 00:08:38.009 --> 00:08:38.019 align:start position:0% verification tools like quick check but 00:08:38.019 --> 00:08:40.800 align:start position:0% verification tools like quick check but what<00:08:38.319> i'm<00:08:38.409> showing<00:08:38.709> you<00:08:38.889> here<00:08:39.269> is<00:08:40.269> that<00:08:40.539> it<00:08:40.689> has 00:08:40.800 --> 00:08:40.810 align:start position:0% what i'm showing you here is that it has 00:08:40.810 --> 00:08:42.809 align:start position:0% what i'm showing you here is that it has an<00:08:40.930> interactive<00:08:41.439> solidity<00:08:41.979> debugger<00:08:42.459> you 00:08:42.809 --> 00:08:42.819 align:start position:0% an interactive solidity debugger you 00:08:42.819 --> 00:08:44.970 align:start position:0% an interactive solidity debugger you want<00:08:43.360> to<00:08:43.449> step<00:08:43.779> through<00:08:44.050> solidity<00:08:44.470> functions 00:08:44.970 --> 00:08:44.980 align:start position:0% want to step through solidity functions 00:08:44.980 --> 00:08:47.220 align:start position:0% want to step through solidity functions on<00:08:45.310> the<00:08:45.430> command<00:08:45.759> line<00:08:45.819> you<00:08:46.660> can<00:08:46.810> do<00:08:46.930> so<00:08:47.110> with 00:08:47.220 --> 00:08:47.230 align:start position:0% on the command line you can do so with 00:08:47.230 --> 00:08:51.480 align:start position:0% on the command line you can do so with snap<00:08:47.470> using<00:08:48.189> H<00:08:48.579> EVM<00:08:49.060> under<00:08:49.810> the<00:08:49.930> hood<00:08:50.220> up<00:08:51.220> top 00:08:51.480 --> 00:08:51.490 align:start position:0% snap using H EVM under the hood up top 00:08:51.490 --> 00:08:51.750 align:start position:0% snap using H EVM under the hood up top you 00:08:51.750 --> 00:08:51.760 align:start position:0% you 00:08:51.760 --> 00:08:54.930 align:start position:0% you see<00:08:51.970> all<00:08:52.300> of<00:08:52.540> the<00:08:53.130> instructions<00:08:54.130> as<00:08:54.400> they<00:08:54.850> get 00:08:54.930 --> 00:08:54.940 align:start position:0% see all of the instructions as they get 00:08:54.940 --> 00:08:58.520 align:start position:0% see all of the instructions as they get executed<00:08:55.450> super<00:08:56.320> cool<00:08:56.470> super<00:08:56.950> interesting 00:08:58.520 --> 00:08:58.530 align:start position:0% executed super cool super interesting 00:08:58.530 --> 00:09:04.410 align:start position:0% executed super cool super interesting and<00:09:00.210> last<00:09:01.530> is<00:09:02.530> dab<00:09:02.860> sus<00:09:03.160> it's<00:09:03.970> been<00:09:04.120> the<00:09:04.240> rest 00:09:04.410 --> 00:09:04.420 align:start position:0% and last is dab sus it's been the rest 00:09:04.420 --> 00:09:07.050 align:start position:0% and last is dab sus it's been the rest of<00:09:04.690> my<00:09:04.810> time<00:09:05.050> talking<00:09:05.560> about<00:09:05.770> dab<00:09:06.130> sis<00:09:06.400> this<00:09:07.000> is 00:09:07.050 --> 00:09:07.060 align:start position:0% of my time talking about dab sis this is 00:09:07.060 --> 00:09:11.280 align:start position:0% of my time talking about dab sis this is our<00:09:07.360> provable<00:09:08.400> standard<00:09:09.400> library<00:09:09.940> of<00:09:10.420> smart 00:09:11.280 --> 00:09:11.290 align:start position:0% our provable standard library of smart 00:09:11.290 --> 00:09:13.860 align:start position:0% our provable standard library of smart contract<00:09:11.710> building<00:09:12.040> blocks<00:09:12.280> a<00:09:12.580> ton<00:09:13.510> of<00:09:13.540> useful 00:09:13.860 --> 00:09:13.870 align:start position:0% contract building blocks a ton of useful 00:09:13.870 --> 00:09:15.900 align:start position:0% contract building blocks a ton of useful stuff<00:09:14.170> here<00:09:14.590> and<00:09:14.740> the<00:09:15.130> reason<00:09:15.460> I<00:09:15.580> say<00:09:15.760> it's 00:09:15.900 --> 00:09:15.910 align:start position:0% stuff here and the reason I say it's 00:09:15.910 --> 00:09:19.260 align:start position:0% stuff here and the reason I say it's provable<00:09:16.890> is<00:09:17.890> because<00:09:18.220> it<00:09:18.340> was<00:09:18.460> built<00:09:18.760> with<00:09:18.940> an 00:09:19.260 --> 00:09:19.270 align:start position:0% provable is because it was built with an 00:09:19.270 --> 00:09:23.640 align:start position:0% provable is because it was built with an eye<00:09:19.800> towards<00:09:20.800> formal<00:09:21.220> verification<00:09:22.500> it<00:09:23.500> is 00:09:23.640 --> 00:09:23.650 align:start position:0% eye towards formal verification it is 00:09:23.650 --> 00:09:26.610 align:start position:0% eye towards formal verification it is the<00:09:23.800> truth<00:09:24.390> but<00:09:25.390> not<00:09:25.630> all<00:09:25.870> contracts<00:09:26.440> are 00:09:26.610 --> 00:09:26.620 align:start position:0% the truth but not all contracts are 00:09:26.620 --> 00:09:29.130 align:start position:0% the truth but not all contracts are equally<00:09:27.100> provable<00:09:27.700> you<00:09:28.450> have<00:09:28.570> to<00:09:28.660> build<00:09:28.900> with 00:09:29.130 --> 00:09:29.140 align:start position:0% equally provable you have to build with 00:09:29.140 --> 00:09:30.990 align:start position:0% equally provable you have to build with the<00:09:29.230> expectation<00:09:30.040> that<00:09:30.070> it<00:09:30.190> will<00:09:30.430> be<00:09:30.670> verified 00:09:30.990 --> 00:09:31.000 align:start position:0% the expectation that it will be verified 00:09:31.000 --> 00:09:34.050 align:start position:0% the expectation that it will be verified in<00:09:31.270> the<00:09:31.360> future<00:09:31.750> and<00:09:32.640> that<00:09:33.640> is<00:09:33.670> what<00:09:33.940> we've 00:09:34.050 --> 00:09:34.060 align:start position:0% in the future and that is what we've 00:09:34.060 --> 00:09:36.870 align:start position:0% in the future and that is what we've done<00:09:34.090> with<00:09:34.630> taps<00:09:34.960> us<00:09:35.170> a<00:09:35.440> lot<00:09:36.010> of<00:09:36.040> it<00:09:36.280> it's<00:09:36.760> gonna 00:09:36.870 --> 00:09:36.880 align:start position:0% done with taps us a lot of it it's gonna 00:09:36.880 --> 00:09:38.460 align:start position:0% done with taps us a lot of it it's gonna sound<00:09:37.060> familiar<00:09:37.270> to<00:09:37.840> what<00:09:37.870> I've<00:09:38.050> been<00:09:38.170> saying 00:09:38.460 --> 00:09:38.470 align:start position:0% sound familiar to what I've been saying 00:09:38.470 --> 00:09:40.380 align:start position:0% sound familiar to what I've been saying so<00:09:38.710> far<00:09:38.890> you<00:09:39.070> have<00:09:39.160> to<00:09:39.280> make<00:09:39.430> them<00:09:39.610> really 00:09:40.380 --> 00:09:40.390 align:start position:0% so far you have to make them really 00:09:40.390 --> 00:09:42.450 align:start position:0% so far you have to make them really really<00:09:40.660> small<00:09:40.870> easily<00:09:41.470> isolate<00:09:41.650> able<00:09:42.190> so<00:09:42.370> you 00:09:42.450 --> 00:09:42.460 align:start position:0% really small easily isolate able so you 00:09:42.460 --> 00:09:43.980 align:start position:0% really small easily isolate able so you can<00:09:42.610> check<00:09:42.820> their<00:09:43.030> invariance<00:09:43.570> and<00:09:43.720> then<00:09:43.870> it 00:09:43.980 --> 00:09:43.990 align:start position:0% can check their invariance and then it 00:09:43.990 --> 00:09:46.500 align:start position:0% can check their invariance and then it can<00:09:44.110> slot<00:09:44.470> into<00:09:44.740> a<00:09:44.920> larger<00:09:45.310> system<00:09:45.520> the<00:09:46.060> UNIX 00:09:46.500 --> 00:09:46.510 align:start position:0% can slot into a larger system the UNIX 00:09:46.510 --> 00:09:48.540 align:start position:0% can slot into a larger system the UNIX design<00:09:46.810> philosophy<00:09:47.440> this<00:09:47.680> is<00:09:47.830> a<00:09:47.980> proven 00:09:48.540 --> 00:09:48.550 align:start position:0% design philosophy this is a proven 00:09:48.550 --> 00:09:50.490 align:start position:0% design philosophy this is a proven approach<00:09:48.910> to<00:09:49.090> design<00:09:49.420> I<00:09:49.450> told<00:09:49.870> you<00:09:50.050> this 00:09:50.490 --> 00:09:50.500 align:start position:0% approach to design I told you this 00:09:50.500 --> 00:09:52.770 align:start position:0% approach to design I told you this appears<00:09:51.400> here<00:09:51.640> in<00:09:51.760> deficits<00:09:52.180> there's<00:09:52.360> a<00:09:52.450> ton 00:09:52.770 --> 00:09:52.780 align:start position:0% appears here in deficits there's a ton 00:09:52.780 --> 00:09:55.320 align:start position:0% appears here in deficits there's a ton of<00:09:53.140> useful<00:09:53.950> building<00:09:54.670> blocks<00:09:54.910> here<00:09:55.090> I<00:09:55.180> could 00:09:55.320 --> 00:09:55.330 align:start position:0% of useful building blocks here I could 00:09:55.330 --> 00:09:57.150 align:start position:0% of useful building blocks here I could honestly<00:09:55.540> have<00:09:55.960> a<00:09:55.990> whole<00:09:56.410> talk<00:09:56.680> about<00:09:56.980> each 00:09:57.150 --> 00:09:57.160 align:start position:0% honestly have a whole talk about each 00:09:57.160 --> 00:10:00.060 align:start position:0% honestly have a whole talk about each one<00:09:57.400> of<00:09:57.520> these<00:09:58.290> I'm<00:09:59.290> gonna<00:09:59.410> talk<00:09:59.590> about<00:09:59.710> two 00:10:00.060 --> 00:10:00.070 align:start position:0% one of these I'm gonna talk about two 00:10:00.070 --> 00:10:01.860 align:start position:0% one of these I'm gonna talk about two today<00:10:00.400> but<00:10:00.640> first<00:10:00.970> let's<00:10:01.660> talk<00:10:01.810> about 00:10:01.860 --> 00:10:01.870 align:start position:0% today but first let's talk about 00:10:01.870 --> 00:10:08.690 align:start position:0% today but first let's talk about deficits<00:10:02.470> at<00:10:03.010> a<00:10:03.070> high<00:10:03.220> level<00:10:07.170> at<00:10:08.170> a<00:10:08.230> high<00:10:08.410> level 00:10:08.690 --> 00:10:08.700 align:start position:0% deficits at a high level at a high level 00:10:08.700 --> 00:10:12.240 align:start position:0% deficits at a high level at a high level there<00:10:09.700> are<00:10:09.730> two<00:10:09.850> main<00:10:10.600> types<00:10:10.870> of<00:10:11.230> DAPs<00:10:12.040> this 00:10:12.240 --> 00:10:12.250 align:start position:0% there are two main types of DAPs this 00:10:12.250 --> 00:10:18.630 align:start position:0% there are two main types of DAPs this packages<00:10:12.900> boxes<00:10:13.900> and<00:10:14.640> mix-ins<00:10:16.650> mix-ins<00:10:17.650> will 00:10:18.630 --> 00:10:18.640 align:start position:0% packages boxes and mix-ins mix-ins will 00:10:18.640 --> 00:10:20.220 align:start position:0% packages boxes and mix-ins mix-ins will appear<00:10:18.910> very<00:10:19.060> familiar<00:10:19.540> to<00:10:19.570> you<00:10:19.810> these<00:10:20.080> are 00:10:20.220 --> 00:10:20.230 align:start position:0% appear very familiar to you these are 00:10:20.230 --> 00:10:22.860 align:start position:0% appear very familiar to you these are base<00:10:20.410> classes<00:10:20.950> you<00:10:21.430> mix<00:10:21.790> them<00:10:22.000> in<00:10:22.210> to<00:10:22.780> your 00:10:22.860 --> 00:10:22.870 align:start position:0% base classes you mix them in to your 00:10:22.870 --> 00:10:25.620 align:start position:0% base classes you mix them in to your adapt<00:10:23.110> logic<00:10:23.560> to<00:10:24.130> get<00:10:24.310> access<00:10:24.820> to<00:10:25.000> interesting 00:10:25.620 --> 00:10:25.630 align:start position:0% adapt logic to get access to interesting 00:10:25.630 --> 00:10:28.590 align:start position:0% adapt logic to get access to interesting functions<00:10:25.990> and<00:10:26.140> modifiers<00:10:26.530> here<00:10:27.400> my<00:10:27.970> DAP<00:10:28.210> is 00:10:28.590 --> 00:10:28.600 align:start position:0% functions and modifiers here my DAP is 00:10:28.600 --> 00:10:34.860 align:start position:0% functions and modifiers here my DAP is mixing<00:10:29.380> in<00:10:29.560> D<00:10:30.370> s<00:10:30.580> and<00:10:31.230> D<00:10:32.230> s<00:10:32.410> math<00:10:32.800> D<00:10:33.790> s<00:10:33.880> auth<00:10:34.120> is 00:10:34.860 --> 00:10:34.870 align:start position:0% mixing in D s and D s math D s auth is 00:10:34.870 --> 00:10:36.950 align:start position:0% mixing in D s and D s math D s auth is providing<00:10:35.320> access<00:10:35.500> to<00:10:35.710> this<00:10:35.980> off<00:10:36.160> modifier 00:10:36.950 --> 00:10:36.960 align:start position:0% providing access to this off modifier 00:10:36.960 --> 00:10:41.250 align:start position:0% providing access to this off modifier and<00:10:38.010> D<00:10:39.010> s<00:10:39.130> math<00:10:39.520> is<00:10:39.970> providing<00:10:40.570> access<00:10:40.750> to<00:10:40.990> this 00:10:41.250 --> 00:10:41.260 align:start position:0% and D s math is providing access to this 00:10:41.260 --> 00:10:44.910 align:start position:0% and D s math is providing access to this w<00:10:41.830> mul<00:10:42.040> function<00:10:42.730> I<00:10:43.140> don't<00:10:44.140> have<00:10:44.230> any<00:10:44.440> time<00:10:44.710> to 00:10:44.910 --> 00:10:44.920 align:start position:0% w mul function I don't have any time to 00:10:44.920 --> 00:10:46.950 align:start position:0% w mul function I don't have any time to talk<00:10:45.100> about<00:10:45.220> D<00:10:45.490> s<00:10:45.610> math<00:10:46.060> but<00:10:46.480> what<00:10:46.660> I<00:10:46.690> can<00:10:46.840> tell 00:10:46.950 --> 00:10:46.960 align:start position:0% talk about D s math but what I can tell 00:10:46.960 --> 00:10:48.840 align:start position:0% talk about D s math but what I can tell you<00:10:47.020> is<00:10:47.290> that<00:10:47.410> this<00:10:47.560> is<00:10:47.710> a<00:10:47.740> very<00:10:48.160> interesting 00:10:48.840 --> 00:10:48.850 align:start position:0% you is that this is a very interesting 00:10:48.850 --> 00:10:51.600 align:start position:0% you is that this is a very interesting safe<00:10:49.720> math<00:10:50.080> library<00:10:50.740> probably<00:10:51.130> the<00:10:51.400> most 00:10:51.600 --> 00:10:51.610 align:start position:0% safe math library probably the most 00:10:51.610 --> 00:10:53.340 align:start position:0% safe math library probably the most interesting<00:10:52.090> safe<00:10:52.570> math<00:10:52.810> library<00:10:53.170> in<00:10:53.260> the 00:10:53.340 --> 00:10:53.350 align:start position:0% interesting safe math library in the 00:10:53.350 --> 00:10:56.280 align:start position:0% interesting safe math library in the business<00:10:53.710> it<00:10:54.070> does<00:10:54.280> not<00:10:54.550> just<00:10:55.330> do<00:10:55.510> overflow 00:10:56.280 --> 00:10:56.290 align:start position:0% business it does not just do overflow 00:10:56.290 --> 00:10:59.130 align:start position:0% business it does not just do overflow protection<00:10:56.440> it<00:10:57.040> does<00:10:57.220> interesting<00:10:58.060> types<00:10:58.900> of 00:10:59.130 --> 00:10:59.140 align:start position:0% protection it does interesting types of 00:10:59.140 --> 00:11:02.040 align:start position:0% protection it does interesting types of token<00:10:59.770> mathematics<00:11:00.400> and<00:11:00.670> that's<00:11:01.390> what<00:11:01.510> W<00:11:01.840> mall 00:11:02.040 --> 00:11:02.050 align:start position:0% token mathematics and that's what W mall 00:11:02.050 --> 00:11:04.880 align:start position:0% token mathematics and that's what W mall is<00:11:02.320> doing<00:11:02.650> there 00:11:04.880 --> 00:11:04.890 align:start position:0% 00:11:04.890 --> 00:11:09.190 align:start position:0% he's<00:11:05.040> second<00:11:05.540> high-level<00:11:06.540> idea<00:11:07.010> our<00:11:08.010> boxes 00:11:09.190 --> 00:11:09.200 align:start position:0% he's second high-level idea our boxes 00:11:09.200 --> 00:11:12.440 align:start position:0% he's second high-level idea our boxes this<00:11:10.200> is<00:11:10.260> a<00:11:10.410> concept<00:11:10.890> that<00:11:11.010> we've<00:11:11.370> invented<00:11:11.700> to 00:11:12.440 --> 00:11:12.450 align:start position:0% this is a concept that we've invented to 00:11:12.450 --> 00:11:16.450 align:start position:0% this is a concept that we've invented to describe<00:11:13.280> safe<00:11:14.960> prefabricated<00:11:15.960> components 00:11:16.450 --> 00:11:16.460 align:start position:0% describe safe prefabricated components 00:11:16.460 --> 00:11:20.300 align:start position:0% describe safe prefabricated components that<00:11:17.460> you<00:11:17.580> take<00:11:17.790> directly<00:11:18.510> off<00:11:18.750> the<00:11:18.930> shelf<00:11:19.310> and 00:11:20.300 --> 00:11:20.310 align:start position:0% that you take directly off the shelf and 00:11:20.310 --> 00:11:22.490 align:start position:0% that you take directly off the shelf and put<00:11:20.580> onto<00:11:20.730> the<00:11:20.880> blockchain<00:11:21.500> without 00:11:22.490 --> 00:11:22.500 align:start position:0% put onto the blockchain without 00:11:22.500 --> 00:11:24.080 align:start position:0% put onto the blockchain without modifying<00:11:23.040> them<00:11:23.340> you<00:11:23.610> think<00:11:23.730> of<00:11:23.880> them<00:11:23.970> as 00:11:24.080 --> 00:11:24.090 align:start position:0% modifying them you think of them as 00:11:24.090 --> 00:11:27.290 align:start position:0% modifying them you think of them as boxes<00:11:24.680> again<00:11:25.680> I'm<00:11:26.040> reusing<00:11:26.460> metaphors<00:11:27.210> here 00:11:27.290 --> 00:11:27.300 align:start position:0% boxes again I'm reusing metaphors here 00:11:27.300 --> 00:11:28.730 align:start position:0% boxes again I'm reusing metaphors here but<00:11:27.720> what<00:11:27.840> we're<00:11:27.990> doing<00:11:28.020> is<00:11:28.380> we're<00:11:28.560> taking 00:11:28.730 --> 00:11:28.740 align:start position:0% but what we're doing is we're taking 00:11:28.740 --> 00:11:30.620 align:start position:0% but what we're doing is we're taking components<00:11:29.460> putting<00:11:30.330> them<00:11:30.420> on<00:11:30.540> the 00:11:30.620 --> 00:11:30.630 align:start position:0% components putting them on the 00:11:30.630 --> 00:11:33.140 align:start position:0% components putting them on the blockchain<00:11:31.160> taking<00:11:32.160> more<00:11:32.370> components<00:11:32.880> and 00:11:33.140 --> 00:11:33.150 align:start position:0% blockchain taking more components and 00:11:33.150 --> 00:11:35.930 align:start position:0% blockchain taking more components and we're<00:11:33.450> wiring<00:11:33.810> them<00:11:34.170> up<00:11:34.350> it<00:11:35.220> actually<00:11:35.340> looks<00:11:35.730> a 00:11:35.930 --> 00:11:35.940 align:start position:0% we're wiring them up it actually looks a 00:11:35.940 --> 00:11:38.270 align:start position:0% we're wiring them up it actually looks a lot<00:11:36.330> like<00:11:36.570> hardware<00:11:36.990> design<00:11:37.350> ma<00:11:37.860> pre 00:11:38.270 --> 00:11:38.280 align:start position:0% lot like hardware design ma pre 00:11:38.280 --> 00:11:40.850 align:start position:0% lot like hardware design ma pre fabricated<00:11:39.030> components<00:11:39.810> and<00:11:40.080> wiring<00:11:40.620> them<00:11:40.740> up 00:11:40.850 --> 00:11:40.860 align:start position:0% fabricated components and wiring them up 00:11:40.860 --> 00:11:42.260 align:start position:0% fabricated components and wiring them up into<00:11:41.010> the<00:11:41.130> apps<00:11:41.280> that<00:11:41.430> was<00:11:41.760> that's<00:11:42.000> what<00:11:42.150> we've 00:11:42.260 --> 00:11:42.270 align:start position:0% into the apps that was that's what we've 00:11:42.270 --> 00:11:44.240 align:start position:0% into the apps that was that's what we've got<00:11:42.450> here<00:11:42.600> on<00:11:42.720> the<00:11:42.750> slide<00:11:43.050> we've<00:11:43.770> got<00:11:43.950> a<00:11:43.980> bunch 00:11:44.240 --> 00:11:44.250 align:start position:0% got here on the slide we've got a bunch 00:11:44.250 --> 00:11:46.940 align:start position:0% got here on the slide we've got a bunch of<00:11:44.490> boxes<00:11:44.970> that<00:11:45.030> have<00:11:45.300> been<00:11:45.390> wired<00:11:45.720> up<00:11:45.990> into<00:11:46.860> an 00:11:46.940 --> 00:11:46.950 align:start position:0% of boxes that have been wired up into an 00:11:46.950 --> 00:11:50.780 align:start position:0% of boxes that have been wired up into an interesting<00:11:47.160> gap<00:11:47.520> most<00:11:48.120> of<00:11:48.420> maker<00:11:48.720> Dow<00:11:49.790> is 00:11:50.780 --> 00:11:50.790 align:start position:0% interesting gap most of maker Dow is 00:11:50.790 --> 00:11:53.030 align:start position:0% interesting gap most of maker Dow is made<00:11:51.240> up<00:11:51.420> of<00:11:51.600> boxes<00:11:52.290> that<00:11:52.320> have<00:11:52.650> been<00:11:52.770> wired 00:11:53.030 --> 00:11:53.040 align:start position:0% made up of boxes that have been wired 00:11:53.040 --> 00:11:54.500 align:start position:0% made up of boxes that have been wired together<00:11:53.250> there's<00:11:53.670> actually<00:11:53.970> relatively 00:11:54.500 --> 00:11:54.510 align:start position:0% together there's actually relatively 00:11:54.510 --> 00:11:57.950 align:start position:0% together there's actually relatively little<00:11:55.550> custom<00:11:56.550> code<00:11:56.820> when<00:11:57.390> you<00:11:57.420> look<00:11:57.750> at<00:11:57.870> the 00:11:57.950 --> 00:11:57.960 align:start position:0% little custom code when you look at the 00:11:57.960 --> 00:11:59.870 align:start position:0% little custom code when you look at the whole<00:11:58.110> thing<00:11:58.190> you<00:11:59.190> don't<00:11:59.370> need<00:11:59.580> to<00:11:59.700> write<00:11:59.820> that 00:11:59.870 --> 00:11:59.880 align:start position:0% whole thing you don't need to write that 00:11:59.880 --> 00:12:01.490 align:start position:0% whole thing you don't need to write that much<00:12:00.210> and<00:12:00.360> you<00:12:00.420> don't<00:12:00.660> need<00:12:00.900> to<00:12:01.020> change<00:12:01.320> the 00:12:01.490 --> 00:12:01.500 align:start position:0% much and you don't need to change the 00:12:01.500 --> 00:12:03.170 align:start position:0% much and you don't need to change the code<00:12:01.800> you<00:12:02.010> don't<00:12:02.160> need<00:12:02.250> to<00:12:02.340> inherit<00:12:02.820> from<00:12:02.970> it 00:12:03.170 --> 00:12:03.180 align:start position:0% code you don't need to inherit from it 00:12:03.180 --> 00:12:05.120 align:start position:0% code you don't need to inherit from it and<00:12:03.660> add<00:12:03.840> in<00:12:04.140> your<00:12:04.260> own<00:12:04.350> logic<00:12:04.500> you<00:12:04.770> just<00:12:04.950> take 00:12:05.120 --> 00:12:05.130 align:start position:0% and add in your own logic you just take 00:12:05.130 --> 00:12:07.370 align:start position:0% and add in your own logic you just take it<00:12:05.250> off<00:12:05.340> the<00:12:05.430> shelf<00:12:05.670> put<00:12:06.300> it<00:12:06.390> right<00:12:06.630> onto<00:12:07.170> the 00:12:07.370 --> 00:12:07.380 align:start position:0% it off the shelf put it right onto the 00:12:07.380 --> 00:12:12.170 align:start position:0% it off the shelf put it right onto the blockchain<00:12:09.620> so<00:12:10.620> let's<00:12:10.830> talk<00:12:11.070> about<00:12:11.310> a<00:12:11.580> mixin 00:12:12.170 --> 00:12:12.180 align:start position:0% blockchain so let's talk about a mixin 00:12:12.180 --> 00:12:14.030 align:start position:0% blockchain so let's talk about a mixin and<00:12:12.450> then<00:12:12.600> let's<00:12:12.780> talk<00:12:12.960> about<00:12:13.020> a<00:12:13.200> box<00:12:13.560> that 00:12:14.030 --> 00:12:14.040 align:start position:0% and then let's talk about a box that 00:12:14.040 --> 00:12:18.650 align:start position:0% and then let's talk about a box that enables<00:12:15.410> this<00:12:16.410> right<00:12:16.770> here<00:12:17.100> is<00:12:17.850> the<00:12:18.030> DES<00:12:18.300> auth 00:12:18.650 --> 00:12:18.660 align:start position:0% enables this right here is the DES auth 00:12:18.660 --> 00:12:20.870 align:start position:0% enables this right here is the DES auth mixin<00:12:19.260> if<00:12:19.410> you<00:12:19.620> don't<00:12:19.980> take<00:12:20.250> anything<00:12:20.610> else 00:12:20.870 --> 00:12:20.880 align:start position:0% mixin if you don't take anything else 00:12:20.880 --> 00:12:24.590 align:start position:0% mixin if you don't take anything else away<00:12:21.060> from<00:12:21.180> this<00:12:21.420> talk<00:12:22.160> please<00:12:23.600> consider 00:12:24.590 --> 00:12:24.600 align:start position:0% away from this talk please consider 00:12:24.600 --> 00:12:27.680 align:start position:0% away from this talk please consider using<00:12:25.200> TS<00:12:25.770> off<00:12:26.100> so<00:12:26.790> that<00:12:26.820> means<00:12:27.030> wake<00:12:27.270> up<00:12:27.480> in 00:12:27.680 --> 00:12:27.690 align:start position:0% using TS off so that means wake up in 00:12:27.690 --> 00:12:28.760 align:start position:0% using TS off so that means wake up in the<00:12:27.810> back<00:12:27.990> if<00:12:28.260> you're<00:12:28.440> not<00:12:28.470> paying<00:12:28.680> attention 00:12:28.760 --> 00:12:28.770 align:start position:0% the back if you're not paying attention 00:12:28.770 --> 00:12:30.920 align:start position:0% the back if you're not paying attention this<00:12:29.580> is<00:12:29.730> the<00:12:29.820> only<00:12:30.000> thing<00:12:30.330> that<00:12:30.600> is<00:12:30.690> truly 00:12:30.920 --> 00:12:30.930 align:start position:0% this is the only thing that is truly 00:12:30.930 --> 00:12:34.490 align:start position:0% this is the only thing that is truly important<00:12:31.410> in<00:12:31.470> this<00:12:31.590> entire<00:12:31.890> talk<00:12:32.190> D<00:12:32.850> s<00:12:33.090> off<00:12:33.500> is 00:12:34.490 --> 00:12:34.500 align:start position:0% important in this entire talk D s off is 00:12:34.500 --> 00:12:37.610 align:start position:0% important in this entire talk D s off is a<00:12:34.650> mixin<00:12:35.190> that<00:12:35.820> allows<00:12:36.090> you<00:12:36.270> to<00:12:36.420> abstract<00:12:36.960> your 00:12:37.610 --> 00:12:37.620 align:start position:0% a mixin that allows you to abstract your 00:12:37.620 --> 00:12:41.180 align:start position:0% a mixin that allows you to abstract your authorization<00:12:38.040> logic<00:12:39.230> away<00:12:40.230> from<00:12:40.800> your<00:12:40.950> taps 00:12:41.180 --> 00:12:41.190 align:start position:0% authorization logic away from your taps 00:12:41.190 --> 00:12:45.230 align:start position:0% authorization logic away from your taps business<00:12:41.940> logic<00:12:42.890> what<00:12:43.890> I<00:12:43.920> mean<00:12:44.220> by<00:12:44.430> that<00:12:44.460> is 00:12:45.230 --> 00:12:45.240 align:start position:0% business logic what I mean by that is 00:12:45.240 --> 00:12:48.530 align:start position:0% business logic what I mean by that is that<00:12:45.330> your<00:12:45.600> DAP<00:12:45.900> can<00:12:46.710> just<00:12:47.070> focus<00:12:47.310> on<00:12:48.030> whatever 00:12:48.530 --> 00:12:48.540 align:start position:0% that your DAP can just focus on whatever 00:12:48.540 --> 00:12:50.750 align:start position:0% that your DAP can just focus on whatever it<00:12:48.840> was<00:12:48.930> created<00:12:49.290> to<00:12:49.380> do<00:12:49.530> and<00:12:49.920> it<00:12:50.130> doesn't<00:12:50.640> need 00:12:50.750 --> 00:12:50.760 align:start position:0% it was created to do and it doesn't need 00:12:50.760 --> 00:12:53.150 align:start position:0% it was created to do and it doesn't need to<00:12:51.000> think<00:12:51.030> about<00:12:51.840> who<00:12:52.200> is<00:12:52.230> allowed<00:12:52.410> to<00:12:52.770> call<00:12:52.980> it 00:12:53.150 --> 00:12:53.160 align:start position:0% to think about who is allowed to call it 00:12:53.160 --> 00:12:57.950 align:start position:0% to think about who is allowed to call it Y<00:12:53.790> when<00:12:54.330> or<00:12:54.630> how<00:12:55.310> and<00:12:56.310> the<00:12:57.240> way<00:12:57.480> that<00:12:57.690> it<00:12:57.780> does 00:12:57.950 --> 00:12:57.960 align:start position:0% Y when or how and the way that it does 00:12:57.960 --> 00:13:01.820 align:start position:0% Y when or how and the way that it does this<00:12:57.990> is<00:12:58.470> by<00:12:59.400> providing<00:12:59.850> a<00:13:00.360> DES<00:13:00.900> thority 00:13:01.820 --> 00:13:01.830 align:start position:0% this is by providing a DES thority 00:13:01.830 --> 00:13:04.510 align:start position:0% this is by providing a DES thority object<00:13:02.280> all<00:13:02.430> des<00:13:02.790> off<00:13:03.000> types<00:13:03.360> provided<00:13:04.080> es 00:13:04.510 --> 00:13:04.520 align:start position:0% object all des off types provided es 00:13:04.520 --> 00:13:08.840 align:start position:0% object all des off types provided es Authority<00:13:05.520> member<00:13:06.650> deeza<00:13:07.650> thority<00:13:08.310> is<00:13:08.520> an 00:13:08.840 --> 00:13:08.850 align:start position:0% Authority member deeza thority is an 00:13:08.850 --> 00:13:11.750 align:start position:0% Authority member deeza thority is an interface<00:13:09.420> just<00:13:10.410> like<00:13:10.590> ER<00:13:10.950> c20<00:13:11.490> is<00:13:11.610> an 00:13:11.750 --> 00:13:11.760 align:start position:0% interface just like ER c20 is an 00:13:11.760 --> 00:13:14.540 align:start position:0% interface just like ER c20 is an interface<00:13:12.150> it's<00:13:12.540> a<00:13:12.630> function<00:13:13.230> that<00:13:13.550> different 00:13:14.540 --> 00:13:14.550 align:start position:0% interface it's a function that different 00:13:14.550 --> 00:13:16.760 align:start position:0% interface it's a function that different boxes<00:13:15.030> are<00:13:15.420> expected<00:13:16.020> to<00:13:16.140> implement<00:13:16.410> and<00:13:16.740> that 00:13:16.760 --> 00:13:16.770 align:start position:0% boxes are expected to implement and that 00:13:16.770 --> 00:13:17.980 align:start position:0% boxes are expected to implement and that function 00:13:17.980 --> 00:13:17.990 align:start position:0% function 00:13:17.990 --> 00:13:23.980 align:start position:0% function is<00:13:18.050> can<00:13:18.620> call<00:13:20.620> can<00:13:21.620> call<00:13:21.970> will<00:13:22.970> respond<00:13:23.480> true 00:13:23.980 --> 00:13:23.990 align:start position:0% is can call can call will respond true 00:13:23.990 --> 00:13:28.720 align:start position:0% is can call can call will respond true or<00:13:24.230> false<00:13:24.640> if<00:13:25.640> the<00:13:26.209> pram<00:13:26.600> the<00:13:26.990> source<00:13:27.950> can<00:13:28.430> call 00:13:28.720 --> 00:13:28.730 align:start position:0% or false if the pram the source can call 00:13:28.730 --> 00:13:31.030 align:start position:0% or false if the pram the source can call the<00:13:29.060> death<00:13:29.209> of<00:13:29.360> function<00:13:29.839> on<00:13:30.170> the<00:13:30.470> destination 00:13:31.030 --> 00:13:31.040 align:start position:0% the death of function on the destination 00:13:31.040 --> 00:13:33.280 align:start position:0% the death of function on the destination so<00:13:31.459> here<00:13:31.640> we've<00:13:31.790> got<00:13:31.970> Bob<00:13:32.209> calling<00:13:33.200> the 00:13:33.280 --> 00:13:33.290 align:start position:0% so here we've got Bob calling the 00:13:33.290 --> 00:13:36.090 align:start position:0% so here we've got Bob calling the finalized<00:13:33.890> function<00:13:34.399> on<00:13:34.580> the<00:13:35.270> auction<00:13:35.750> and 00:13:36.090 --> 00:13:36.100 align:start position:0% finalized function on the auction and 00:13:36.100 --> 00:13:40.389 align:start position:0% finalized function on the auction and the<00:13:37.100> auction<00:13:37.550> as<00:13:37.760> its<00:13:38.390> des<00:13:38.930> authority<00:13:39.649> box<00:13:40.070> if 00:13:40.389 --> 00:13:40.399 align:start position:0% the auction as its des authority box if 00:13:40.399 --> 00:13:42.760 align:start position:0% the auction as its des authority box if Bob<00:13:41.300> can<00:13:41.660> call<00:13:41.870> the<00:13:41.990> finalize<00:13:42.350> function<00:13:42.680> on 00:13:42.760 --> 00:13:42.770 align:start position:0% Bob can call the finalize function on 00:13:42.770 --> 00:13:45.430 align:start position:0% Bob can call the finalize function on the<00:13:42.860> auction<00:13:43.010> and<00:13:43.370> the<00:13:44.330> DSO<00:13:44.720> authority<00:13:45.050> will 00:13:45.430 --> 00:13:45.440 align:start position:0% the auction and the DSO authority will 00:13:45.440 --> 00:13:46.090 align:start position:0% the auction and the DSO authority will respond 00:13:46.090 --> 00:13:46.100 align:start position:0% respond 00:13:46.100 --> 00:13:50.530 align:start position:0% respond true<00:13:46.370> or<00:13:46.399> false<00:13:47.589> based<00:13:48.589> on<00:13:48.830> any<00:13:49.540> arbitrary 00:13:50.530 --> 00:13:50.540 align:start position:0% true or false based on any arbitrary 00:13:50.540 --> 00:13:52.600 align:start position:0% true or false based on any arbitrary business<00:13:51.110> logic<00:13:51.320> and<00:13:51.680> this<00:13:51.860> is<00:13:52.100> what<00:13:52.279> makes<00:13:52.430> it 00:13:52.600 --> 00:13:52.610 align:start position:0% business logic and this is what makes it 00:13:52.610 --> 00:13:54.220 align:start position:0% business logic and this is what makes it interesting<00:13:52.910> and<00:13:53.209> this<00:13:53.480> is<00:13:53.690> what<00:13:53.870> makes<00:13:54.080> it 00:13:54.220 --> 00:13:54.230 align:start position:0% interesting and this is what makes it 00:13:54.230 --> 00:13:57.160 align:start position:0% interesting and this is what makes it important<00:13:54.920> because<00:13:55.540> that<00:13:56.540> business<00:13:56.990> logic 00:13:57.160 --> 00:13:57.170 align:start position:0% important because that business logic 00:13:57.170 --> 00:13:59.050 align:start position:0% important because that business logic could<00:13:57.470> be<00:13:57.589> as<00:13:57.709> simple<00:13:58.010> or<00:13:58.310> complex<00:13:58.760> as<00:13:59.000> you 00:13:59.050 --> 00:13:59.060 align:start position:0% could be as simple or complex as you 00:13:59.060 --> 00:14:01.870 align:start position:0% could be as simple or complex as you want<00:13:59.209> look<00:14:00.200> at<00:14:00.320> all<00:14:00.470> this<00:14:00.560> business<00:14:01.010> logic<00:14:01.160> the 00:14:01.870 --> 00:14:01.880 align:start position:0% want look at all this business logic the 00:14:01.880 --> 00:14:04.889 align:start position:0% want look at all this business logic the DSO<00:14:02.330> thority<00:14:02.750> could<00:14:03.110> be<00:14:03.260> a<00:14:03.470> simple<00:14:04.100> whitelist 00:14:04.889 --> 00:14:04.899 align:start position:0% DSO thority could be a simple whitelist 00:14:04.899 --> 00:14:08.079 align:start position:0% DSO thority could be a simple whitelist bob<00:14:05.899> can<00:14:06.290> call<00:14:06.500> finalize<00:14:07.100> it<00:14:07.850> could<00:14:07.970> be<00:14:08.060> a 00:14:08.079 --> 00:14:08.089 align:start position:0% bob can call finalize it could be a 00:14:08.089 --> 00:14:10.060 align:start position:0% bob can call finalize it could be a time-locked<00:14:08.660> whitelist<00:14:09.080> bob<00:14:09.500> can<00:14:09.860> call 00:14:10.060 --> 00:14:10.070 align:start position:0% time-locked whitelist bob can call 00:14:10.070 --> 00:14:13.630 align:start position:0% time-locked whitelist bob can call finalize<00:14:10.610> in<00:14:10.820> two<00:14:11.029> days<00:14:11.440> it<00:14:12.440> could<00:14:12.830> be<00:14:13.040> a<00:14:13.279> role 00:14:13.630 --> 00:14:13.640 align:start position:0% finalize in two days it could be a role 00:14:13.640 --> 00:14:15.250 align:start position:0% finalize in two days it could be a role based<00:14:13.970> permissioning<00:14:14.510> system<00:14:14.870> we<00:14:14.990> have<00:14:15.140> one 00:14:15.250 --> 00:14:15.260 align:start position:0% based permissioning system we have one 00:14:15.260 --> 00:14:17.829 align:start position:0% based permissioning system we have one of<00:14:15.350> those<00:14:15.410> indexes<00:14:15.980> bob<00:14:16.790> is<00:14:17.330> a<00:14:17.420> member<00:14:17.810> of 00:14:17.829 --> 00:14:17.839 align:start position:0% of those indexes bob is a member of 00:14:17.839 --> 00:14:21.730 align:start position:0% of those indexes bob is a member of group<00:14:18.110> one<00:14:18.790> which<00:14:19.790> can't<00:14:20.089> call<00:14:20.270> finalized<00:14:20.740> or 00:14:21.730 --> 00:14:21.740 align:start position:0% group one which can't call finalized or 00:14:21.740 --> 00:14:23.889 align:start position:0% group one which can't call finalized or and<00:14:22.399> this<00:14:22.730> is<00:14:22.940> where<00:14:23.089> it<00:14:23.180> gets<00:14:23.270> interesting 00:14:23.889 --> 00:14:23.899 align:start position:0% and this is where it gets interesting 00:14:23.899 --> 00:14:27.420 align:start position:0% and this is where it gets interesting Bob<00:14:24.800> can<00:14:25.550> call<00:14:25.760> finalized<00:14:26.390> in<00:14:26.690> two<00:14:27.020> days 00:14:27.420 --> 00:14:27.430 align:start position:0% Bob can call finalized in two days 00:14:27.430 --> 00:14:32.019 align:start position:0% Bob can call finalized in two days unless<00:14:28.430> the<00:14:28.640> token<00:14:29.120> holders<00:14:29.620> veto<00:14:30.620> him<00:14:31.029> what 00:14:32.019 --> 00:14:32.029 align:start position:0% unless the token holders veto him what 00:14:32.029 --> 00:14:34.769 align:start position:0% unless the token holders veto him what I'm<00:14:32.120> saying<00:14:32.570> here<00:14:33.050> is<00:14:33.079> that<00:14:33.470> des<00:14:33.770> Authority 00:14:34.769 --> 00:14:34.779 align:start position:0% I'm saying here is that des Authority 00:14:34.779 --> 00:14:37.569 align:start position:0% I'm saying here is that des Authority moves<00:14:35.779> the<00:14:36.079> conversation<00:14:36.829> forward<00:14:37.220> on 00:14:37.569 --> 00:14:37.579 align:start position:0% moves the conversation forward on 00:14:37.579 --> 00:14:39.610 align:start position:0% moves the conversation forward on governance<00:14:38.180> this<00:14:38.510> is<00:14:38.720> blockchain<00:14:39.170> governance 00:14:39.610 --> 00:14:39.620 align:start position:0% governance this is blockchain governance 00:14:39.620 --> 00:14:40.990 align:start position:0% governance this is blockchain governance right<00:14:39.950> here<00:14:40.250> this<00:14:40.490> is<00:14:40.640> what<00:14:40.790> you're<00:14:40.910> looking 00:14:40.990 --> 00:14:41.000 align:start position:0% right here this is what you're looking 00:14:41.000 --> 00:14:42.790 align:start position:0% right here this is what you're looking at<00:14:41.300> your<00:14:41.600> dabs<00:14:41.899> are<00:14:42.140> your<00:14:42.260> tabs<00:14:42.500> and<00:14:42.709> your 00:14:42.790 --> 00:14:42.800 align:start position:0% at your dabs are your tabs and your 00:14:42.800 --> 00:14:44.139 align:start position:0% at your dabs are your tabs and your governance<00:14:43.220> is<00:14:43.370> your<00:14:43.520> governance<00:14:43.880> and<00:14:44.060> your 00:14:44.139 --> 00:14:44.149 align:start position:0% governance is your governance and your 00:14:44.149 --> 00:14:46.300 align:start position:0% governance is your governance and your governance<00:14:44.600> is<00:14:44.839> the<00:14:45.290> DES<00:14:45.529> Authority 00:14:46.300 --> 00:14:46.310 align:start position:0% governance is the DES Authority 00:14:46.310 --> 00:14:48.960 align:start position:0% governance is the DES Authority interface<00:14:46.790> if<00:14:47.029> the<00:14:47.450> entire<00:14:47.870> community 00:14:48.960 --> 00:14:48.970 align:start position:0% interface if the entire community 00:14:48.970 --> 00:14:53.350 align:start position:0% interface if the entire community converges<00:14:49.970> on<00:14:50.350> can<00:14:51.350> call<00:14:51.740> that's<00:14:52.370> it<00:14:52.550> just<00:14:53.089> can 00:14:53.350 --> 00:14:53.360 align:start position:0% converges on can call that's it just can 00:14:53.360 --> 00:14:57.370 align:start position:0% converges on can call that's it just can call<00:14:53.690> I<00:14:53.990> promise<00:14:54.829> you<00:14:55.570> 2017<00:14:56.570> will<00:14:56.870> have<00:14:57.020> been<00:14:57.200> a 00:14:57.370 --> 00:14:57.380 align:start position:0% call I promise you 2017 will have been a 00:14:57.380 --> 00:14:59.410 align:start position:0% call I promise you 2017 will have been a good<00:14:57.620> year<00:14:57.680> for<00:14:58.010> blockchain<00:14:58.579> governance<00:14:59.029> this 00:14:59.410 --> 00:14:59.420 align:start position:0% good year for blockchain governance this 00:14:59.420 --> 00:15:03.130 align:start position:0% good year for blockchain governance this is<00:14:59.660> a<00:15:00.290> Germain<00:15:01.279> idea<00:15:01.730> this<00:15:01.940> is<00:15:02.000> a<00:15:02.089> new<00:15:02.329> idea<00:15:02.540> and 00:15:03.130 --> 00:15:03.140 align:start position:0% is a Germain idea this is a new idea and 00:15:03.140 --> 00:15:05.500 align:start position:0% is a Germain idea this is a new idea and if<00:15:03.410> we<00:15:03.529> can<00:15:03.680> think<00:15:04.010> in<00:15:04.160> this<00:15:04.279> way<00:15:04.520> abstracting 00:15:05.500 --> 00:15:05.510 align:start position:0% if we can think in this way abstracting 00:15:05.510 --> 00:15:07.540 align:start position:0% if we can think in this way abstracting authorization<00:15:06.110> away<00:15:06.440> from<00:15:06.649> governance<00:15:07.070> we 00:15:07.540 --> 00:15:07.550 align:start position:0% authorization away from governance we 00:15:07.550 --> 00:15:10.329 align:start position:0% authorization away from governance we will<00:15:07.670> move<00:15:07.850> significantly<00:15:08.270> beyond<00:15:09.230> the<00:15:09.890> only 00:15:10.329 --> 00:15:10.339 align:start position:0% will move significantly beyond the only 00:15:10.339 --> 00:15:12.610 align:start position:0% will move significantly beyond the only owner<00:15:10.579> modifier<00:15:11.149> and<00:15:12.020> we<00:15:12.110> can<00:15:12.260> start<00:15:12.470> using 00:15:12.610 --> 00:15:12.620 align:start position:0% owner modifier and we can start using 00:15:12.620 --> 00:15:15.970 align:start position:0% owner modifier and we can start using the<00:15:12.920> off<00:15:13.100> modifier<00:15:13.820> this<00:15:14.390> is<00:15:14.540> a<00:15:14.570> big<00:15:14.839> deal<00:15:15.050> and 00:15:15.970 --> 00:15:15.980 align:start position:0% the off modifier this is a big deal and 00:15:15.980 --> 00:15:20.440 align:start position:0% the off modifier this is a big deal and I'm<00:15:16.070> gonna<00:15:16.160> show<00:15:17.320> thank<00:15:18.320> you<00:15:19.000> this<00:15:20.000> is<00:15:20.029> a<00:15:20.209> big 00:15:20.440 --> 00:15:20.450 align:start position:0% I'm gonna show thank you this is a big 00:15:20.450 --> 00:15:23.930 align:start position:0% I'm gonna show thank you this is a big deal 00:15:23.930 --> 00:15:23.940 align:start position:0% 00:15:23.940 --> 00:15:26.340 align:start position:0% this<00:15:24.940> is<00:15:25.180> blockchain<00:15:25.630> governance<00:15:25.990> right<00:15:26.170> here 00:15:26.340 --> 00:15:26.350 align:start position:0% this is blockchain governance right here 00:15:26.350 --> 00:15:30.480 align:start position:0% this is blockchain governance right here dsr<00:15:27.070> write<00:15:27.940> that<00:15:28.120> down<00:15:28.950> and<00:15:29.950> I'm<00:15:30.070> gonna<00:15:30.160> show 00:15:30.480 --> 00:15:30.490 align:start position:0% dsr write that down and I'm gonna show 00:15:30.490 --> 00:15:33.720 align:start position:0% dsr write that down and I'm gonna show you<00:15:30.550> now<00:15:30.790> a<00:15:31.000> box<00:15:31.420> that<00:15:32.200> is<00:15:32.320> enabled<00:15:32.800> by<00:15:33.190> DSR 00:15:33.720 --> 00:15:33.730 align:start position:0% you now a box that is enabled by DSR 00:15:33.730 --> 00:15:38.670 align:start position:0% you now a box that is enabled by DSR that<00:15:34.270> is<00:15:34.450> the<00:15:34.570> DES<00:15:34.810> token<00:15:35.470> box<00:15:36.840> D<00:15:37.840> s<00:15:37.960> token<00:15:38.350> as 00:15:38.670 --> 00:15:38.680 align:start position:0% that is the DES token box D s token as 00:15:38.680 --> 00:15:41.340 align:start position:0% that is the DES token box D s token as you<00:15:38.830> can<00:15:38.950> imagine<00:15:39.210> is<00:15:40.210> a<00:15:40.240> token<00:15:40.450> it's<00:15:40.810> an<00:15:40.870> ER<00:15:41.140> C 00:15:41.340 --> 00:15:41.350 align:start position:0% you can imagine is a token it's an ER C 00:15:41.350 --> 00:15:45.630 align:start position:0% you can imagine is a token it's an ER C 20<00:15:41.680> and<00:15:42.190> it<00:15:43.060> is<00:15:43.180> of<00:15:43.360> type<00:15:43.570> D<00:15:43.960> s<00:15:44.200> off<00:15:44.530> and<00:15:45.370> the 00:15:45.630 --> 00:15:45.640 align:start position:0% 20 and it is of type D s off and the 00:15:45.640 --> 00:15:47.700 align:start position:0% 20 and it is of type D s off and the reason<00:15:45.880> that<00:15:46.210> is<00:15:46.540> of<00:15:46.750> type<00:15:46.960> T<00:15:47.140> s<00:15:47.260> off<00:15:47.470> is 00:15:47.700 --> 00:15:47.710 align:start position:0% reason that is of type T s off is 00:15:47.710 --> 00:15:52.100 align:start position:0% reason that is of type T s off is because<00:15:48.070> it<00:15:48.190> has<00:15:48.400> four<00:15:49.150> new<00:15:49.960> functions<00:15:50.970> stop 00:15:52.100 --> 00:15:52.110 align:start position:0% because it has four new functions stop 00:15:52.110 --> 00:15:56.670 align:start position:0% because it has four new functions stop which<00:15:53.110> stops<00:15:53.440> token<00:15:53.860> transfers<00:15:54.570> start<00:15:55.680> which 00:15:56.670 --> 00:15:56.680 align:start position:0% which stops token transfers start which 00:15:56.680 --> 00:15:59.820 align:start position:0% which stops token transfers start which restarts<00:15:57.130> token<00:15:57.550> transfers<00:15:57.880> mint<00:15:58.840> which 00:15:59.820 --> 00:15:59.830 align:start position:0% restarts token transfers mint which 00:15:59.830 --> 00:16:01.740 align:start position:0% restarts token transfers mint which creates<00:16:00.250> new<00:16:00.550> tokens<00:16:00.940> for<00:16:01.120> the<00:16:01.240> caller<00:16:01.450> and 00:16:01.740 --> 00:16:01.750 align:start position:0% creates new tokens for the caller and 00:16:01.750 --> 00:16:04.860 align:start position:0% creates new tokens for the caller and burn<00:16:02.590> which<00:16:03.400> removes<00:16:03.820> the<00:16:04.090> callers<00:16:04.420> tokens 00:16:04.860 --> 00:16:04.870 align:start position:0% burn which removes the callers tokens 00:16:04.870 --> 00:16:08.340 align:start position:0% burn which removes the callers tokens lowering<00:16:05.470> total<00:16:05.710> supply<00:16:06.960> we<00:16:07.960> have<00:16:07.990> thought 00:16:08.340 --> 00:16:08.350 align:start position:0% lowering total supply we have thought 00:16:08.350 --> 00:16:10.560 align:start position:0% lowering total supply we have thought about<00:16:08.380> tokens<00:16:08.860> for<00:16:09.040> a<00:16:09.070> long<00:16:09.370> time<00:16:09.880> at<00:16:10.150> a<00:16:10.330> pub 00:16:10.560 --> 00:16:10.570 align:start position:0% about tokens for a long time at a pub 00:16:10.570 --> 00:16:12.030 align:start position:0% about tokens for a long time at a pub this<00:16:10.930> is<00:16:11.050> we're<00:16:11.290> one<00:16:11.410> of<00:16:11.500> the<00:16:11.560> most<00:16:11.680> senior 00:16:12.030 --> 00:16:12.040 align:start position:0% this is we're one of the most senior 00:16:12.040 --> 00:16:13.440 align:start position:0% this is we're one of the most senior teams<00:16:12.310> and<00:16:12.550> all<00:16:12.700> of<00:16:12.850> its<00:16:13.000> here<00:16:13.120> Ian<00:16:13.240> we've 00:16:13.440 --> 00:16:13.450 align:start position:0% teams and all of its here Ian we've 00:16:13.450 --> 00:16:15.600 align:start position:0% teams and all of its here Ian we've thought<00:16:13.600> about<00:16:13.660> tokens<00:16:14.280> basically<00:16:15.280> as<00:16:15.400> long 00:16:15.600 --> 00:16:15.610 align:start position:0% thought about tokens basically as long 00:16:15.610 --> 00:16:17.700 align:start position:0% thought about tokens basically as long as<00:16:15.820> a<00:16:15.940> theorem<00:16:16.240> has<00:16:16.330> existed<00:16:16.870> and<00:16:17.020> we<00:16:17.530> have 00:16:17.700 --> 00:16:17.710 align:start position:0% as a theorem has existed and we have 00:16:17.710 --> 00:16:20.520 align:start position:0% as a theorem has existed and we have decided<00:16:18.300> based<00:16:19.300> on<00:16:19.480> our<00:16:19.600> love<00:16:19.870> of<00:16:19.900> the<00:16:20.200> UNIX 00:16:20.520 --> 00:16:20.530 align:start position:0% decided based on our love of the UNIX 00:16:20.530 --> 00:16:22.500 align:start position:0% decided based on our love of the UNIX design<00:16:20.800> philosophy<00:16:21.400> and<00:16:21.640> our<00:16:21.730> own<00:16:21.910> needs<00:16:21.940> in 00:16:22.500 --> 00:16:22.510 align:start position:0% design philosophy and our own needs in 00:16:22.510 --> 00:16:25.320 align:start position:0% design philosophy and our own needs in maker<00:16:22.720> Dow<00:16:22.990> that<00:16:23.530> this<00:16:23.860> covers<00:16:24.700> the<00:16:24.910> entirety 00:16:25.320 --> 00:16:25.330 align:start position:0% maker Dow that this covers the entirety 00:16:25.330 --> 00:16:27.630 align:start position:0% maker Dow that this covers the entirety of<00:16:25.480> the<00:16:25.690> token<00:16:25.990> use<00:16:26.140> case<00:16:26.380> because<00:16:27.070> what<00:16:27.460> l'm 00:16:27.630 --> 00:16:27.640 align:start position:0% of the token use case because what l'm 00:16:27.640 --> 00:16:30.180 align:start position:0% of the token use case because what l'm staying<00:16:27.940> here<00:16:28.300> up<00:16:28.780> here<00:16:28.840> on<00:16:29.170> stage<00:16:29.410> to<00:16:29.620> say<00:16:29.890> is 00:16:30.180 --> 00:16:30.190 align:start position:0% staying here up here on stage to say is 00:16:30.190 --> 00:16:33.330 align:start position:0% staying here up here on stage to say is let<00:16:30.790> tokens<00:16:31.300> show<00:16:31.690> us<00:16:31.780> to<00:16:31.900> be<00:16:32.020> tokens<00:16:32.500> just 00:16:33.330 --> 00:16:33.340 align:start position:0% let tokens show us to be tokens just 00:16:33.340 --> 00:16:34.950 align:start position:0% let tokens show us to be tokens just have<00:16:33.610> them<00:16:33.790> be<00:16:33.820> tokens<00:16:34.360> they're<00:16:34.540> just<00:16:34.780> a 00:16:34.950 --> 00:16:34.960 align:start position:0% have them be tokens they're just a 00:16:34.960 --> 00:16:37.590 align:start position:0% have them be tokens they're just a database<00:16:35.500> of<00:16:35.710> token<00:16:36.490> balances<00:16:36.940> they<00:16:37.270> can<00:16:37.420> only 00:16:37.590 --> 00:16:37.600 align:start position:0% database of token balances they can only 00:16:37.600 --> 00:16:41.070 align:start position:0% database of token balances they can only do<00:16:37.870> a<00:16:37.900> few<00:16:38.290> things<00:16:38.320> and<00:16:38.800> here<00:16:39.310> we<00:16:39.430> can<00:16:39.550> see<00:16:40.080> this 00:16:41.070 --> 00:16:41.080 align:start position:0% do a few things and here we can see this 00:16:41.080 --> 00:16:42.270 align:start position:0% do a few things and here we can see this diagram<00:16:41.650> but<00:16:41.800> they<00:16:41.920> can<00:16:42.040> still<00:16:42.250> be 00:16:42.270 --> 00:16:42.280 align:start position:0% diagram but they can still be 00:16:42.280 --> 00:16:44.520 align:start position:0% diagram but they can still be interesting<00:16:43.240> parts<00:16:43.600> of<00:16:43.750> depths<00:16:44.170> right<00:16:44.380> we've 00:16:44.520 --> 00:16:44.530 align:start position:0% interesting parts of depths right we've 00:16:44.530 --> 00:16:46.440 align:start position:0% interesting parts of depths right we've got<00:16:44.740> Bob<00:16:44.950> here<00:16:45.310> calling<00:16:45.670> his<00:16:45.760> claim<00:16:46.060> reward 00:16:46.440 --> 00:16:46.450 align:start position:0% got Bob here calling his claim reward 00:16:46.450 --> 00:16:49.740 align:start position:0% got Bob here calling his claim reward function<00:16:46.740> the<00:16:47.740> distributor<00:16:48.460> is<00:16:48.880> authorized 00:16:49.740 --> 00:16:49.750 align:start position:0% function the distributor is authorized 00:16:49.750 --> 00:16:53.250 align:start position:0% function the distributor is authorized to<00:16:50.230> mint<00:16:50.650> tokens<00:16:51.190> on<00:16:51.630> mint<00:16:52.630> tokens<00:16:53.080> and 00:16:53.250 --> 00:16:53.260 align:start position:0% to mint tokens on mint tokens and 00:16:53.260 --> 00:16:55.860 align:start position:0% to mint tokens on mint tokens and distribute<00:16:53.650> them<00:16:53.770> to<00:16:53.890> Bob<00:16:54.040> right<00:16:54.670> we've<00:16:55.660> got 00:16:55.860 --> 00:16:55.870 align:start position:0% distribute them to Bob right we've got 00:16:55.870 --> 00:16:57.630 align:start position:0% distribute them to Bob right we've got fancy<00:16:56.320> things<00:16:56.560> we've<00:16:56.740> got<00:16:56.980> fancy<00:16:57.430> business 00:16:57.630 --> 00:16:57.640 align:start position:0% fancy things we've got fancy business 00:16:57.640 --> 00:16:59.490 align:start position:0% fancy things we've got fancy business logic<00:16:58.000> it's<00:16:58.300> just<00:16:58.510> not<00:16:58.750> in<00:16:58.990> the<00:16:59.110> token 00:16:59.490 --> 00:16:59.500 align:start position:0% logic it's just not in the token 00:16:59.500 --> 00:17:02.370 align:start position:0% logic it's just not in the token contract<00:17:00.040> and<00:17:00.600> when<00:17:01.600> you<00:17:01.690> make<00:17:01.930> a<00:17:01.960> token 00:17:02.370 --> 00:17:02.380 align:start position:0% contract and when you make a token 00:17:02.380 --> 00:17:04.950 align:start position:0% contract and when you make a token contract<00:17:02.830> only<00:17:03.010> a<00:17:03.400> token<00:17:03.910> contract<00:17:04.390> but<00:17:04.900> you 00:17:04.950 --> 00:17:04.960 align:start position:0% contract only a token contract but you 00:17:04.960 --> 00:17:07.560 align:start position:0% contract only a token contract but you still<00:17:05.380> make<00:17:05.620> it<00:17:05.770> flexible<00:17:06.280> with<00:17:06.670> DES<00:17:07.000> often 00:17:07.560 --> 00:17:07.570 align:start position:0% still make it flexible with DES often 00:17:07.570 --> 00:17:10.200 align:start position:0% still make it flexible with DES often these<00:17:07.690> extended<00:17:08.380> functionality<00:17:09.060> you<00:17:10.060> can 00:17:10.200 --> 00:17:10.210 align:start position:0% these extended functionality you can 00:17:10.210 --> 00:17:11.640 align:start position:0% these extended functionality you can have<00:17:10.420> interesting<00:17:11.110> things<00:17:11.200> you<00:17:11.350> can<00:17:11.470> think 00:17:11.640 --> 00:17:11.650 align:start position:0% have interesting things you can think 00:17:11.650 --> 00:17:13.800 align:start position:0% have interesting things you can think about<00:17:11.710> tokens<00:17:12.130> in<00:17:12.280> better<00:17:12.910> ways<00:17:13.210> let<00:17:13.570> me<00:17:13.660> show 00:17:13.800 --> 00:17:13.810 align:start position:0% about tokens in better ways let me show 00:17:13.810 --> 00:17:16.110 align:start position:0% about tokens in better ways let me show you<00:17:13.870> an<00:17:14.110> old<00:17:14.410> way<00:17:14.710> that<00:17:15.280> we<00:17:15.550> used<00:17:15.790> to<00:17:15.910> think 00:17:16.110 --> 00:17:16.120 align:start position:0% you an old way that we used to think 00:17:16.120 --> 00:17:17.760 align:start position:0% you an old way that we used to think about<00:17:16.180> tokens<00:17:16.720> we<00:17:17.200> used<00:17:17.350> to<00:17:17.410> think<00:17:17.590> about 00:17:17.760 --> 00:17:17.770 align:start position:0% about tokens we used to think about 00:17:17.770 --> 00:17:21.420 align:start position:0% about tokens we used to think about tokens<00:17:18.660> kind<00:17:19.660> of<00:17:19.750> in<00:17:19.900> this<00:17:20.430> front-end 00:17:21.420 --> 00:17:21.430 align:start position:0% tokens kind of in this front-end 00:17:21.430 --> 00:17:25.320 align:start position:0% tokens kind of in this front-end controller<00:17:22.000> a<00:17:22.150> datastore<00:17:23.550> model<00:17:24.550> this<00:17:25.120> is<00:17:25.300> a 00:17:25.320 --> 00:17:25.330 align:start position:0% controller a datastore model this is a 00:17:25.330 --> 00:17:26.940 align:start position:0% controller a datastore model this is a very<00:17:25.570> common<00:17:25.930> model<00:17:26.140> to<00:17:26.230> think<00:17:26.410> about<00:17:26.590> tokens 00:17:26.940 --> 00:17:26.950 align:start position:0% very common model to think about tokens 00:17:26.950 --> 00:17:28.980 align:start position:0% very common model to think about tokens it<00:17:27.220> was<00:17:27.310> called<00:17:27.460> the<00:17:27.520> upgradable<00:17:28.210> token<00:17:28.570> so 00:17:28.980 --> 00:17:28.990 align:start position:0% it was called the upgradable token so 00:17:28.990 --> 00:17:30.300 align:start position:0% it was called the upgradable token so what<00:17:29.110> you<00:17:29.200> had<00:17:29.350> was<00:17:29.380> you<00:17:29.650> had<00:17:29.770> your<00:17:29.920> static 00:17:30.300 --> 00:17:30.310 align:start position:0% what you had was you had your static 00:17:30.310 --> 00:17:32.460 align:start position:0% what you had was you had your static front-end<00:17:30.700> you<00:17:31.000> had<00:17:31.120> your<00:17:31.270> static<00:17:31.660> token 00:17:32.460 --> 00:17:32.470 align:start position:0% front-end you had your static token 00:17:32.470 --> 00:17:33.630 align:start position:0% front-end you had your static token datastore<00:17:32.920> and<00:17:33.130> then<00:17:33.430> you<00:17:33.490> had<00:17:33.610> your 00:17:33.630 --> 00:17:33.640 align:start position:0% datastore and then you had your 00:17:33.640 --> 00:17:35.130 align:start position:0% datastore and then you had your controller<00:17:34.150> which<00:17:34.510> had<00:17:34.690> some<00:17:34.900> sort 00:17:35.130 --> 00:17:35.140 align:start position:0% controller which had some sort 00:17:35.140 --> 00:17:36.510 align:start position:0% controller which had some sort touken<00:17:35.530> business<00:17:35.830> logic<00:17:36.040> whatever<00:17:36.400> your 00:17:36.510 --> 00:17:36.520 align:start position:0% touken business logic whatever your 00:17:36.520 --> 00:17:39.620 align:start position:0% touken business logic whatever your token<00:17:36.850> did<00:17:37.060> in<00:17:37.660> this<00:17:37.810> case<00:17:37.990> it's<00:17:38.200> doing<00:17:38.440> voting 00:17:39.620 --> 00:17:39.630 align:start position:0% token did in this case it's doing voting 00:17:39.630 --> 00:17:41.730 align:start position:0% token did in this case it's doing voting and<00:17:40.630> then<00:17:40.750> you<00:17:40.840> would<00:17:40.960> call<00:17:41.230> the<00:17:41.410> controller 00:17:41.730 --> 00:17:41.740 align:start position:0% and then you would call the controller 00:17:41.740 --> 00:17:43.380 align:start position:0% and then you would call the controller and<00:17:41.860> sometimes<00:17:42.160> you'd<00:17:42.280> swap<00:17:42.640> it<00:17:42.820> out<00:17:42.940> when<00:17:43.330> you 00:17:43.380 --> 00:17:43.390 align:start position:0% and sometimes you'd swap it out when you 00:17:43.390 --> 00:17:45.000 align:start position:0% and sometimes you'd swap it out when you wanted<00:17:43.600> to<00:17:43.720> update<00:17:43.870> the<00:17:44.140> functionality<00:17:44.800> the 00:17:45.000 --> 00:17:45.010 align:start position:0% wanted to update the functionality the 00:17:45.010 --> 00:17:48.630 align:start position:0% wanted to update the functionality the hope<00:17:46.020> that<00:17:47.020> you<00:17:47.080> wouldn't<00:17:47.500> swap<00:17:47.770> out<00:17:48.010> the<00:17:48.430> data 00:17:48.630 --> 00:17:48.640 align:start position:0% hope that you wouldn't swap out the data 00:17:48.640 --> 00:17:50.460 align:start position:0% hope that you wouldn't swap out the data store<00:17:48.970> but<00:17:49.300> you<00:17:49.360> can't<00:17:49.630> merely<00:17:49.960> make<00:17:50.230> that 00:17:50.460 --> 00:17:50.470 align:start position:0% store but you can't merely make that 00:17:50.470 --> 00:17:51.810 align:start position:0% store but you can't merely make that promise<00:17:50.770> when<00:17:51.190> you're<00:17:51.280> looking<00:17:51.490> at<00:17:51.640> something 00:17:51.810 --> 00:17:51.820 align:start position:0% promise when you're looking at something 00:17:51.820 --> 00:17:54.420 align:start position:0% promise when you're looking at something like<00:17:51.940> this<00:17:52.180> right<00:17:52.420> you<00:17:52.570> can't<00:17:52.810> provably<00:17:53.740> make 00:17:54.420 --> 00:17:54.430 align:start position:0% like this right you can't provably make 00:17:54.430 --> 00:17:57.180 align:start position:0% like this right you can't provably make that<00:17:54.640> promise<00:17:55.140> when<00:17:56.140> you<00:17:56.230> have<00:17:56.440> everything 00:17:57.180 --> 00:17:57.190 align:start position:0% that promise when you have everything 00:17:57.190 --> 00:18:01.050 align:start position:0% that promise when you have everything quite<00:17:58.180> so<00:17:58.480> dynamic<00:17:59.200> right<00:17:59.730> we<00:18:00.730> want<00:18:00.880> to<00:18:00.940> make 00:18:01.050 --> 00:18:01.060 align:start position:0% quite so dynamic right we want to make 00:18:01.060 --> 00:18:02.790 align:start position:0% quite so dynamic right we want to make credible<00:18:01.480> promises<00:18:02.110> to<00:18:02.230> our<00:18:02.320> stakeholders 00:18:02.790 --> 00:18:02.800 align:start position:0% credible promises to our stakeholders 00:18:02.800 --> 00:18:04.590 align:start position:0% credible promises to our stakeholders provable<00:18:03.340> promises<00:18:03.940> to<00:18:04.060> our<00:18:04.180> stakeholders 00:18:04.590 --> 00:18:04.600 align:start position:0% provable promises to our stakeholders 00:18:04.600 --> 00:18:06.210 align:start position:0% provable promises to our stakeholders and<00:18:04.630> not<00:18:04.930> only<00:18:05.110> that<00:18:05.290> this<00:18:05.890> is<00:18:05.950> too 00:18:06.210 --> 00:18:06.220 align:start position:0% and not only that this is too 00:18:06.220 --> 00:18:08.610 align:start position:0% and not only that this is too complicated<00:18:06.580> this<00:18:07.240> thing<00:18:07.390> is<00:18:07.480> huge<00:18:07.690> waste<00:18:08.320> gas 00:18:08.610 --> 00:18:08.620 align:start position:0% complicated this thing is huge waste gas 00:18:08.620 --> 00:18:11.340 align:start position:0% complicated this thing is huge waste gas and<00:18:09.010> it's<00:18:09.670> not<00:18:09.880> being<00:18:10.270> a<00:18:10.450> token<00:18:10.900> it's<00:18:11.020> being<00:18:11.230> a 00:18:11.340 --> 00:18:11.350 align:start position:0% and it's not being a token it's being a 00:18:11.350 --> 00:18:13.920 align:start position:0% and it's not being a token it's being a bunch<00:18:11.620> of<00:18:11.800> stuff<00:18:12.100> it's<00:18:12.700> difficult<00:18:13.300> to<00:18:13.630> reason 00:18:13.920 --> 00:18:13.930 align:start position:0% bunch of stuff it's difficult to reason 00:18:13.930 --> 00:18:17.370 align:start position:0% bunch of stuff it's difficult to reason about<00:18:14.970> let's<00:18:15.970> look<00:18:16.150> at<00:18:16.240> voting<00:18:16.600> in<00:18:16.750> a<00:18:17.140> much 00:18:17.370 --> 00:18:17.380 align:start position:0% about let's look at voting in a much 00:18:17.380 --> 00:18:19.890 align:start position:0% about let's look at voting in a much easier<00:18:17.560> way<00:18:17.920> the<00:18:18.250> box<00:18:18.520> mentality<00:18:19.240> here<00:18:19.780> we 00:18:19.890 --> 00:18:19.900 align:start position:0% easier way the box mentality here we 00:18:19.900 --> 00:18:24.140 align:start position:0% easier way the box mentality here we have<00:18:20.110> Bob<00:18:21.180> calling<00:18:22.180> vote<00:18:22.480> on<00:18:22.990> the<00:18:23.140> voting<00:18:23.500> box 00:18:24.140 --> 00:18:24.150 align:start position:0% have Bob calling vote on the voting box 00:18:24.150 --> 00:18:27.030 align:start position:0% have Bob calling vote on the voting box and<00:18:25.150> it's<00:18:25.300> just<00:18:25.480> pulling<00:18:25.930> tokens<00:18:26.410> it's<00:18:26.860> just 00:18:27.030 --> 00:18:27.040 align:start position:0% and it's just pulling tokens it's just 00:18:27.040 --> 00:18:29.100 align:start position:0% and it's just pulling tokens it's just pulling<00:18:27.250> tokens<00:18:27.730> into<00:18:28.060> its<00:18:28.210> box<00:18:28.420> and<00:18:28.750> holding 00:18:29.100 --> 00:18:29.110 align:start position:0% pulling tokens into its box and holding 00:18:29.110 --> 00:18:31.440 align:start position:0% pulling tokens into its box and holding them<00:18:29.260> is<00:18:29.800> literally<00:18:30.310> like<00:18:30.580> a<00:18:30.610> ballot<00:18:30.970> box<00:18:31.210> I 00:18:31.440 --> 00:18:31.450 align:start position:0% them is literally like a ballot box I 00:18:31.450 --> 00:18:33.240 align:start position:0% them is literally like a ballot box I mean<00:18:31.480> look<00:18:31.750> at<00:18:31.810> this<00:18:31.930> thing<00:18:31.990> it<00:18:32.770> pulls<00:18:33.070> the 00:18:33.240 --> 00:18:33.250 align:start position:0% mean look at this thing it pulls the 00:18:33.250 --> 00:18:34.650 align:start position:0% mean look at this thing it pulls the tokens<00:18:33.610> it<00:18:33.790> counts<00:18:34.120> the<00:18:34.210> votes<00:18:34.240> when 00:18:34.650 --> 00:18:34.660 align:start position:0% tokens it counts the votes when 00:18:34.660 --> 00:18:36.270 align:start position:0% tokens it counts the votes when everybody's<00:18:35.020> done<00:18:35.170> voting<00:18:35.530> it<00:18:35.710> releases<00:18:35.980> the 00:18:36.270 --> 00:18:36.280 align:start position:0% everybody's done voting it releases the 00:18:36.280 --> 00:18:39.330 align:start position:0% everybody's done voting it releases the tokens<00:18:36.750> much<00:18:37.750> much<00:18:38.230> better<00:18:38.560> way<00:18:38.800> to<00:18:38.830> vote<00:18:39.160> the 00:18:39.330 --> 00:18:39.340 align:start position:0% tokens much much better way to vote the 00:18:39.340 --> 00:18:41.400 align:start position:0% tokens much much better way to vote the token<00:18:39.700> is<00:18:39.790> a<00:18:39.820> token<00:18:40.090> the<00:18:40.690> voting<00:18:40.990> box<00:18:41.110> is<00:18:41.320> the 00:18:41.400 --> 00:18:41.410 align:start position:0% token is a token the voting box is the 00:18:41.410 --> 00:18:44.250 align:start position:0% token is a token the voting box is the voting<00:18:41.680> box<00:18:41.830> and<00:18:42.100> look<00:18:42.520> the<00:18:43.420> voting<00:18:43.840> box<00:18:43.960> can 00:18:44.250 --> 00:18:44.260 align:start position:0% voting box and look the voting box can 00:18:44.260 --> 00:18:46.590 align:start position:0% voting box and look the voting box can be<00:18:44.290> an<00:18:44.470> authority<00:18:44.830> right<00:18:45.820> this<00:18:46.240> is<00:18:46.390> what<00:18:46.510> I'm 00:18:46.590 --> 00:18:46.600 align:start position:0% be an authority right this is what I'm 00:18:46.600 --> 00:18:47.940 align:start position:0% be an authority right this is what I'm talking<00:18:46.900> about<00:18:46.960> when<00:18:47.170> I<00:18:47.200> talk<00:18:47.410> about<00:18:47.530> token 00:18:47.940 --> 00:18:47.950 align:start position:0% talking about when I talk about token 00:18:47.950 --> 00:18:50.910 align:start position:0% talking about when I talk about token governance<00:18:48.340> it<00:18:48.640> can<00:18:48.760> be<00:18:48.880> a<00:18:48.910> DES<00:18:49.450> thority<00:18:50.350> for 00:18:50.910 --> 00:18:50.920 align:start position:0% governance it can be a DES thority for 00:18:50.920 --> 00:18:54.120 align:start position:0% governance it can be a DES thority for an<00:18:50.980> entire<00:18:51.280> system<00:18:51.880> of<00:18:51.970> taps<00:18:52.920> and<00:18:53.920> not<00:18:54.040> only 00:18:54.120 --> 00:18:54.130 align:start position:0% an entire system of taps and not only 00:18:54.130 --> 00:18:56.400 align:start position:0% an entire system of taps and not only that<00:18:54.400> it<00:18:55.210> can<00:18:55.240> be<00:18:55.420> a<00:18:55.450> DSO<00:18:55.840> thority<00:18:56.170> for<00:18:56.320> the 00:18:56.400 --> 00:18:56.410 align:start position:0% that it can be a DSO thority for the 00:18:56.410 --> 00:18:58.620 align:start position:0% that it can be a DSO thority for the token<00:18:56.620> you<00:18:57.040> can<00:18:57.160> make<00:18:57.310> a<00:18:57.340> cycle<00:18:57.880> here<00:18:58.180> where 00:18:58.620 --> 00:18:58.630 align:start position:0% token you can make a cycle here where 00:18:58.630 --> 00:19:01.770 align:start position:0% token you can make a cycle here where the<00:18:58.810> token<00:18:59.320> holders<00:18:59.770> are<00:19:00.390> governing<00:19:01.390> the 00:19:01.770 --> 00:19:01.780 align:start position:0% the token holders are governing the 00:19:01.780 --> 00:19:04.100 align:start position:0% the token holders are governing the authority<00:19:02.290> that<00:19:02.530> controls<00:19:02.680> the<00:19:03.220> mint<00:19:03.460> burn 00:19:04.100 --> 00:19:04.110 align:start position:0% authority that controls the mint burn 00:19:04.110 --> 00:19:06.980 align:start position:0% authority that controls the mint burn start<00:19:05.110> and<00:19:05.260> stop<00:19:05.470> functions<00:19:05.890> on<00:19:06.040> themselves 00:19:06.980 --> 00:19:06.990 align:start position:0% start and stop functions on themselves 00:19:06.990 --> 00:19:09.030 align:start position:0% start and stop functions on themselves it's<00:19:07.990> like<00:19:08.110> a<00:19:08.140> cycle<00:19:08.590> because<00:19:08.890> they're 00:19:09.030 --> 00:19:09.040 align:start position:0% it's like a cycle because they're 00:19:09.040 --> 00:19:11.460 align:start position:0% it's like a cycle because they're governing<00:19:09.550> their<00:19:09.730> own<00:19:09.940> token<00:19:10.600> that's<00:19:11.020> neat 00:19:11.460 --> 00:19:11.470 align:start position:0% governing their own token that's neat 00:19:11.470 --> 00:19:12.870 align:start position:0% governing their own token that's neat that's<00:19:12.310> cool 00:19:12.870 --> 00:19:12.880 align:start position:0% that's cool 00:19:12.880 --> 00:19:15.780 align:start position:0% that's cool that<00:19:13.000> pushes<00:19:13.380> the<00:19:14.380> conversation<00:19:15.070> about<00:19:15.400> token 00:19:15.780 --> 00:19:15.790 align:start position:0% that pushes the conversation about token 00:19:15.790 --> 00:19:18.270 align:start position:0% that pushes the conversation about token governance<00:19:16.180> forward<00:19:16.810> and<00:19:17.200> that's<00:19:17.920> what<00:19:18.070> we<00:19:18.160> do 00:19:18.270 --> 00:19:18.280 align:start position:0% governance forward and that's what we do 00:19:18.280 --> 00:19:21.300 align:start position:0% governance forward and that's what we do at<00:19:18.400> a<00:19:18.520> pub<00:19:19.470> if<00:19:20.470> you're<00:19:20.680> interested<00:19:21.160> in<00:19:21.250> this 00:19:21.300 --> 00:19:21.310 align:start position:0% at a pub if you're interested in this 00:19:21.310 --> 00:19:23.100 align:start position:0% at a pub if you're interested in this type<00:19:21.490> of<00:19:21.550> stuff<00:19:21.910> if<00:19:22.240> you're<00:19:22.510> interested<00:19:23.020> in 00:19:23.100 --> 00:19:23.110 align:start position:0% type of stuff if you're interested in 00:19:23.110 --> 00:19:25.290 align:start position:0% type of stuff if you're interested in formal<00:19:23.440> verification<00:19:23.620> if<00:19:24.310> you're<00:19:24.760> interested 00:19:25.290 --> 00:19:25.300 align:start position:0% formal verification if you're interested 00:19:25.300 --> 00:19:27.630 align:start position:0% formal verification if you're interested in<00:19:25.420> that<00:19:25.600> old-school<00:19:26.170> hacker<00:19:26.710> mentality<00:19:27.370> and 00:19:27.630 --> 00:19:27.640 align:start position:0% in that old-school hacker mentality and 00:19:27.640 --> 00:19:31.170 align:start position:0% in that old-school hacker mentality and aesthetic<00:19:28.600> I<00:19:29.250> recommend<00:19:30.250> that<00:19:30.610> you<00:19:30.670> come<00:19:30.940> and 00:19:31.170 --> 00:19:31.180 align:start position:0% aesthetic I recommend that you come and 00:19:31.180 --> 00:19:33.180 align:start position:0% aesthetic I recommend that you come and introduce<00:19:31.630> yourself<00:19:32.020> come<00:19:32.350> to<00:19:32.470> da<00:19:32.620> pub<00:19:32.830> comm 00:19:33.180 --> 00:19:33.190 align:start position:0% introduce yourself come to da pub comm 00:19:33.190 --> 00:19:34.860 align:start position:0% introduce yourself come to da pub comm all<00:19:33.430> the<00:19:33.640> links<00:19:33.880> are<00:19:34.000> there<00:19:34.120> check<00:19:34.570> out<00:19:34.720> our 00:19:34.860 --> 00:19:34.870 align:start position:0% all the links are there check out our 00:19:34.870 --> 00:19:37.380 align:start position:0% all the links are there check out our tools<00:19:35.080> check<00:19:35.890> out<00:19:36.040> our<00:19:36.220> chat<00:19:36.460> tap<00:19:36.790> pub<00:19:37.000> chat 00:19:37.380 --> 00:19:37.390 align:start position:0% tools check out our chat tap pub chat 00:19:37.390 --> 00:19:39.750 align:start position:0% tools check out our chat tap pub chat but<00:19:38.020> a<00:19:38.050> lot<00:19:38.260> of<00:19:38.380> interesting<00:19:38.800> stuff<00:19:39.040> we<00:19:39.730> are 00:19:39.750 --> 00:19:39.760 align:start position:0% but a lot of interesting stuff we are 00:19:39.760 --> 00:19:42.330 align:start position:0% but a lot of interesting stuff we are here<00:19:40.000> to<00:19:40.180> create<00:19:40.480> free<00:19:41.080> software<00:19:41.590> for<00:19:42.160> tap 00:19:42.330 --> 00:19:42.340 align:start position:0% here to create free software for tap 00:19:42.340 --> 00:19:49.340 align:start position:0% here to create free software for tap tubs<00:19:42.610> thank<00:19:43.600> you 00:19:49.340 --> 00:19:49.350 align:start position:0% 00:19:49.350 --> 00:19:50.550 align:start position:0% you 00:19:50.550 --> 00:19:50.560 align:start position:0% you 00:19:50.560 --> 00:19:58.140 align:start position:0% you [Music]