WEBVTT Kind: captions Language: en 00:00:13.690 --> 00:00:15.850 align:start position:0% our<00:00:14.690> contract<00:00:15.019> developers<00:00:15.320> are<00:00:15.469> there<00:00:15.619> well 00:00:15.850 --> 00:00:15.860 align:start position:0% our contract developers are there well 00:00:15.860 --> 00:00:18.130 align:start position:0% our contract developers are there well the<00:00:15.950> answer<00:00:16.190> is<00:00:16.219> not<00:00:16.460> enough<00:00:16.900> we're<00:00:17.900> mirroring 00:00:18.130 --> 00:00:18.140 align:start position:0% the answer is not enough we're mirroring 00:00:18.140 --> 00:00:19.870 align:start position:0% the answer is not enough we're mirroring a<00:00:18.350> similar<00:00:18.740> situation<00:00:18.950> that<00:00:19.400> happened<00:00:19.730> in<00:00:19.790> the 00:00:19.870 --> 00:00:19.880 align:start position:0% a similar situation that happened in the 00:00:19.880 --> 00:00:21.580 align:start position:0% a similar situation that happened in the early<00:00:20.120> days<00:00:20.330> of<00:00:20.630> what<00:00:20.780> development<00:00:21.140> in<00:00:21.470> the 00:00:21.580 --> 00:00:21.590 align:start position:0% early days of what development in the 00:00:21.590 --> 00:00:25.090 align:start position:0% early days of what development in the 1990s<00:00:22.900> we<00:00:23.900> have<00:00:24.080> high<00:00:24.260> demand<00:00:24.560> low<00:00:24.770> supply 00:00:25.090 --> 00:00:25.100 align:start position:0% 1990s we have high demand low supply 00:00:25.100 --> 00:00:26.950 align:start position:0% 1990s we have high demand low supply right<00:00:25.520> now<00:00:25.550> we<00:00:25.700> have<00:00:25.880> around<00:00:25.970> 9<00:00:26.390> million<00:00:26.660> Java 00:00:26.950 --> 00:00:26.960 align:start position:0% right now we have around 9 million Java 00:00:26.960 --> 00:00:29.220 align:start position:0% right now we have around 9 million Java developers<00:00:27.440> and<00:00:27.680> that's<00:00:28.430> paled<00:00:28.970> and 00:00:29.220 --> 00:00:29.230 align:start position:0% developers and that's paled and 00:00:29.230 --> 00:00:32.049 align:start position:0% developers and that's paled and conspiracy<00:00:30.230> to<00:00:30.410> like<00:00:30.560> the<00:00:30.680> less<00:00:30.830> than<00:00:31.059> 10000 00:00:32.049 --> 00:00:32.059 align:start position:0% conspiracy to like the less than 10000 00:00:32.059 --> 00:00:34.690 align:start position:0% conspiracy to like the less than 10000 blockchain<00:00:32.629> developers<00:00:33.079> and<00:00:33.469> even<00:00:34.070> less<00:00:34.280> mark 00:00:34.690 --> 00:00:34.700 align:start position:0% blockchain developers and even less mark 00:00:34.700 --> 00:00:37.090 align:start position:0% blockchain developers and even less mark contract<00:00:35.000> developers<00:00:35.390> and<00:00:36.230> these<00:00:36.890> smart 00:00:37.090 --> 00:00:37.100 align:start position:0% contract developers and these smart 00:00:37.100 --> 00:00:38.980 align:start position:0% contract developers and these smart contract<00:00:37.460> developers<00:00:37.940> are<00:00:38.210> up<00:00:38.420> against<00:00:38.720> a<00:00:38.810> lot 00:00:38.980 --> 00:00:38.990 align:start position:0% contract developers are up against a lot 00:00:38.990 --> 00:00:42.690 align:start position:0% contract developers are up against a lot and<00:00:39.370> here's<00:00:40.370> one<00:00:40.520> example<00:00:40.610> of<00:00:40.940> how<00:00:41.090> they<00:00:41.210> are 00:00:42.690 --> 00:00:42.700 align:start position:0% and here's one example of how they are 00:00:42.700 --> 00:00:44.950 align:start position:0% and here's one example of how they are and<00:00:43.700> so<00:00:43.970> we<00:00:44.120> created<00:00:44.300> a<00:00:44.600> smart<00:00:44.840> contract 00:00:44.950 --> 00:00:44.960 align:start position:0% and so we created a smart contract 00:00:44.960 --> 00:00:47.560 align:start position:0% and so we created a smart contract lifecycle<00:00:45.350> and<00:00:46.340> this<00:00:46.610> is<00:00:46.730> a<00:00:46.760> brand<00:00:47.120> departure 00:00:47.560 --> 00:00:47.570 align:start position:0% lifecycle and this is a brand departure 00:00:47.570 --> 00:00:49.540 align:start position:0% lifecycle and this is a brand departure actually<00:00:47.870> from<00:00:48.280> traditional<00:00:49.280> software 00:00:49.540 --> 00:00:49.550 align:start position:0% actually from traditional software 00:00:49.550 --> 00:00:51.340 align:start position:0% actually from traditional software development<00:00:50.030> life<00:00:50.149> cycles<00:00:50.540> and<00:00:50.989> I<00:00:51.110> come<00:00:51.260> from 00:00:51.340 --> 00:00:51.350 align:start position:0% development life cycles and I come from 00:00:51.350 --> 00:00:52.870 align:start position:0% development life cycles and I come from a<00:00:51.470> project<00:00:51.649> management<00:00:51.860> so<00:00:52.489> I<00:00:52.520> love<00:00:52.670> the<00:00:52.760> life 00:00:52.870 --> 00:00:52.880 align:start position:0% a project management so I love the life 00:00:52.880 --> 00:00:55.420 align:start position:0% a project management so I love the life cycles<00:00:53.590> we<00:00:54.590> start<00:00:54.800> the<00:00:54.920> business<00:00:55.160> model 00:00:55.420 --> 00:00:55.430 align:start position:0% cycles we start the business model 00:00:55.430 --> 00:00:57.850 align:start position:0% cycles we start the business model specifications<00:00:56.410> currently<00:00:57.410> we're 00:00:57.850 --> 00:00:57.860 align:start position:0% specifications currently we're 00:00:57.860 --> 00:00:59.590 align:start position:0% specifications currently we're programming<00:00:58.190> money<00:00:58.520> essentially<00:00:59.120> with<00:00:59.270> smart 00:00:59.590 --> 00:00:59.600 align:start position:0% programming money essentially with smart 00:00:59.600 --> 00:01:01.209 align:start position:0% programming money essentially with smart contracts<00:00:59.989> that's<00:01:00.260> a<00:01:00.500> departure<00:01:00.980> from 00:01:01.209 --> 00:01:01.219 align:start position:0% contracts that's a departure from 00:01:01.219 --> 00:01:02.799 align:start position:0% contracts that's a departure from traditional<00:01:01.760> software<00:01:02.090> depending<00:01:02.570> on<00:01:02.660> what 00:01:02.799 --> 00:01:02.809 align:start position:0% traditional software depending on what 00:01:02.809 --> 00:01:04.329 align:start position:0% traditional software depending on what you're<00:01:02.930> programming<00:01:03.320> and<00:01:03.860> what<00:01:04.159> you're 00:01:04.329 --> 00:01:04.339 align:start position:0% you're programming and what you're 00:01:04.339 --> 00:01:06.700 align:start position:0% you're programming and what you're building<00:01:04.430> but<00:01:05.390> analysis<00:01:06.110> requirements<00:01:06.620> are 00:01:06.700 --> 00:01:06.710 align:start position:0% building but analysis requirements are 00:01:06.710 --> 00:01:08.440 align:start position:0% building but analysis requirements are standard<00:01:07.070> architecture<00:01:07.340> design<00:01:07.880> code<00:01:08.210> that's 00:01:08.440 --> 00:01:08.450 align:start position:0% standard architecture design code that's 00:01:08.450 --> 00:01:09.610 align:start position:0% standard architecture design code that's standard<00:01:08.840> and<00:01:08.960> then<00:01:09.049> we<00:01:09.110> get<00:01:09.200> to<00:01:09.320> system 00:01:09.610 --> 00:01:09.620 align:start position:0% standard and then we get to system 00:01:09.620 --> 00:01:13.330 align:start position:0% standard and then we get to system testing<00:01:10.040> we<00:01:10.880> are<00:01:10.970> programming<00:01:11.330> money<00:01:11.600> and<00:01:12.340> any 00:01:13.330 --> 00:01:13.340 align:start position:0% testing we are programming money and any 00:01:13.340 --> 00:01:15.580 align:start position:0% testing we are programming money and any bug<00:01:13.970> is<00:01:14.240> actually<00:01:14.840> catastrophic<00:01:15.440> to<00:01:15.560> our 00:01:15.580 --> 00:01:15.590 align:start position:0% bug is actually catastrophic to our 00:01:15.590 --> 00:01:17.020 align:start position:0% bug is actually catastrophic to our business<00:01:16.010> model<00:01:16.310> it<00:01:16.400> ruins<00:01:16.670> our<00:01:16.729> entire 00:01:17.020 --> 00:01:17.030 align:start position:0% business model it ruins our entire 00:01:17.030 --> 00:01:18.910 align:start position:0% business model it ruins our entire business<00:01:17.180> model<00:01:17.659> so<00:01:18.110> we<00:01:18.200> spend<00:01:18.440> a<00:01:18.530> lot<00:01:18.650> of<00:01:18.680> time 00:01:18.910 --> 00:01:18.920 align:start position:0% business model so we spend a lot of time 00:01:18.920 --> 00:01:22.240 align:start position:0% business model so we spend a lot of time in<00:01:19.070> testing<00:01:19.430> and<00:01:20.020> we<00:01:21.020> go<00:01:21.229> through<00:01:21.470> UAT<00:01:21.770> testing 00:01:22.240 --> 00:01:22.250 align:start position:0% in testing and we go through UAT testing 00:01:22.250 --> 00:01:23.950 align:start position:0% in testing and we go through UAT testing regression<00:01:22.430> testing<00:01:23.030> we<00:01:23.240> try<00:01:23.450> to<00:01:23.510> break<00:01:23.780> these 00:01:23.950 --> 00:01:23.960 align:start position:0% regression testing we try to break these 00:01:23.960 --> 00:01:26.590 align:start position:0% regression testing we try to break these things<00:01:24.020> and<00:01:24.560> then<00:01:25.130> we<00:01:25.220> try<00:01:25.400> to<00:01:25.430> get<00:01:25.610> it<00:01:25.760> audited 00:01:26.590 --> 00:01:26.600 align:start position:0% things and then we try to get it audited 00:01:26.600 --> 00:01:28.740 align:start position:0% things and then we try to get it audited that's<00:01:27.530> all<00:01:27.710> so<00:01:27.830> the<00:01:27.979> parts<00:01:28.220> are<00:01:28.310> from 00:01:28.740 --> 00:01:28.750 align:start position:0% that's all so the parts are from 00:01:28.750 --> 00:01:30.850 align:start position:0% that's all so the parts are from traditional<00:01:29.750> software<00:01:30.049> development<00:01:30.170> it's 00:01:30.850 --> 00:01:30.860 align:start position:0% traditional software development it's 00:01:30.860 --> 00:01:32.770 align:start position:0% traditional software development it's not<00:01:31.070> a<00:01:31.100> standard<00:01:31.549> but<00:01:32.090> here<00:01:32.360> it<00:01:32.479> pretty<00:01:32.689> much 00:01:32.770 --> 00:01:32.780 align:start position:0% not a standard but here it pretty much 00:01:32.780 --> 00:01:35.289 align:start position:0% not a standard but here it pretty much is<00:01:32.990> we<00:01:33.619> confident<00:01:34.490> we<00:01:34.549> deploy<00:01:34.790> it<00:01:34.909> and<00:01:35.030> then<00:01:35.150> we 00:01:35.289 --> 00:01:35.299 align:start position:0% is we confident we deploy it and then we 00:01:35.299 --> 00:01:37.149 align:start position:0% is we confident we deploy it and then we support<00:01:35.659> maintain<00:01:36.020> that's<00:01:36.950> another 00:01:37.149 --> 00:01:37.159 align:start position:0% support maintain that's another 00:01:37.159 --> 00:01:39.550 align:start position:0% support maintain that's another departure<00:01:37.869> supporting<00:01:38.869> maintaining<00:01:39.320> is<00:01:39.409> done 00:01:39.550 --> 00:01:39.560 align:start position:0% departure supporting maintaining is done 00:01:39.560 --> 00:01:42.130 align:start position:0% departure supporting maintaining is done by<00:01:39.710> the<00:01:39.770> EVM<00:01:40.280> there's<00:01:40.939> no<00:01:41.510> back<00:01:41.750> office 00:01:42.130 --> 00:01:42.140 align:start position:0% by the EVM there's no back office 00:01:42.140 --> 00:01:44.740 align:start position:0% by the EVM there's no back office supporting<00:01:42.740> this<00:01:42.830> it's<00:01:43.070> supported<00:01:43.850> by<00:01:43.970> four 00:01:44.740 --> 00:01:44.750 align:start position:0% supporting this it's supported by four 00:01:44.750 --> 00:01:47.710 align:start position:0% supporting this it's supported by four nodes<00:01:45.049> and<00:01:45.320> miners<00:01:45.680> and<00:01:45.920> so<00:01:46.729> after<00:01:47.240> death<00:01:47.479> or 00:01:47.710 --> 00:01:47.720 align:start position:0% nodes and miners and so after death or 00:01:47.720 --> 00:01:49.510 align:start position:0% nodes and miners and so after death or business<00:01:48.350> power<00:01:48.530> user<00:01:48.770> really<00:01:49.220> how<00:01:49.460> to 00:01:49.510 --> 00:01:49.520 align:start position:0% business power user really how to 00:01:49.520 --> 00:01:50.890 align:start position:0% business power user really how to interact<00:01:49.820> with<00:01:49.880> your<00:01:50.000> smart<00:01:50.270> contract<00:01:50.689> it's<00:01:50.810> a 00:01:50.890 --> 00:01:50.900 align:start position:0% interact with your smart contract it's a 00:01:50.900 --> 00:01:54.399 align:start position:0% interact with your smart contract it's a minimal<00:01:51.290> footprint<00:01:51.680> and<00:01:52.930> you<00:01:53.930> will<00:01:54.080> have<00:01:54.290> to 00:01:54.399 --> 00:01:54.409 align:start position:0% minimal footprint and you will have to 00:01:54.409 --> 00:01:56.580 align:start position:0% minimal footprint and you will have to support<00:01:54.740> any<00:01:54.920> bugs<00:01:55.189> and<00:01:55.520> what<00:01:56.150> does<00:01:56.270> that<00:01:56.299> mean 00:01:56.580 --> 00:01:56.590 align:start position:0% support any bugs and what does that mean 00:01:56.590 --> 00:01:58.929 align:start position:0% support any bugs and what does that mean when<00:01:57.590> a<00:01:57.829> bug<00:01:58.100> comes<00:01:58.130> across<00:01:58.460> your<00:01:58.700> smart 00:01:58.929 --> 00:01:58.939 align:start position:0% when a bug comes across your smart 00:01:58.939 --> 00:02:00.730 align:start position:0% when a bug comes across your smart contract<00:01:59.329> or<00:01:59.540> you<00:01:59.659> have<00:01:59.780> to<00:01:59.900> upgrade<00:02:00.110> it<00:02:00.470> or<00:02:00.590> a 00:02:00.730 --> 00:02:00.740 align:start position:0% contract or you have to upgrade it or a 00:02:00.740 --> 00:02:02.440 align:start position:0% contract or you have to upgrade it or a feature<00:02:00.979> you<00:02:01.729> have<00:02:01.880> to<00:02:02.000> run<00:02:02.210> through<00:02:02.360> this 00:02:02.440 --> 00:02:02.450 align:start position:0% feature you have to run through this 00:02:02.450 --> 00:02:04.899 align:start position:0% feature you have to run through this entire<00:02:02.630> cycle<00:02:03.110> again<00:02:03.610> traditional<00:02:04.610> software 00:02:04.899 --> 00:02:04.909 align:start position:0% entire cycle again traditional software 00:02:04.909 --> 00:02:06.700 align:start position:0% entire cycle again traditional software development<00:02:05.000> allows<00:02:05.960> us<00:02:06.170> to<00:02:06.350> just<00:02:06.530> add 00:02:06.700 --> 00:02:06.710 align:start position:0% development allows us to just add 00:02:06.710 --> 00:02:10.419 align:start position:0% development allows us to just add features<00:02:07.280> upgrades<00:02:07.970> fix<00:02:08.810> bugs<00:02:09.079> and<00:02:09.429> really 00:02:10.419 --> 00:02:10.429 align:start position:0% features upgrades fix bugs and really 00:02:10.429 --> 00:02:12.640 align:start position:0% features upgrades fix bugs and really just<00:02:10.640> deploy<00:02:11.569> it<00:02:11.720> again<00:02:11.900> here<00:02:12.260> we<00:02:12.380> have<00:02:12.500> to 00:02:12.640 --> 00:02:12.650 align:start position:0% just deploy it again here we have to 00:02:12.650 --> 00:02:14.700 align:start position:0% just deploy it again here we have to create<00:02:13.370> a<00:02:13.430> new<00:02:13.580> smart<00:02:14.120> card 00:02:14.700 --> 00:02:14.710 align:start position:0% create a new smart card 00:02:14.710 --> 00:02:18.900 align:start position:0% create a new smart card to<00:02:14.950> fix<00:02:15.250> anything<00:02:15.730> or<00:02:16.060> to<00:02:16.480> upgrade<00:02:16.780> it<00:02:16.930> and<00:02:17.910> so 00:02:18.900 --> 00:02:18.910 align:start position:0% to fix anything or to upgrade it and so 00:02:18.910 --> 00:02:21.450 align:start position:0% to fix anything or to upgrade it and so that<00:02:19.180> adds<00:02:20.050> to<00:02:20.470> the<00:02:20.560> smart<00:02:20.800> contracts<00:02:21.250> that 00:02:21.450 --> 00:02:21.460 align:start position:0% that adds to the smart contracts that 00:02:21.460 --> 00:02:23.340 align:start position:0% that adds to the smart contracts that are<00:02:21.610> retired<00:02:22.420> what<00:02:22.870> they're<00:02:23.020> now<00:02:23.110> really 00:02:23.340 --> 00:02:23.350 align:start position:0% are retired what they're now really 00:02:23.350 --> 00:02:25.260 align:start position:0% are retired what they're now really retired<00:02:23.710> and<00:02:24.010> so<00:02:24.610> we<00:02:24.700> have<00:02:24.820> a<00:02:24.850> lot<00:02:25.000> of<00:02:25.030> them<00:02:25.180> on 00:02:25.260 --> 00:02:25.270 align:start position:0% retired and so we have a lot of them on 00:02:25.270 --> 00:02:29.730 align:start position:0% retired and so we have a lot of them on the<00:02:25.360> network<00:02:27.780> so<00:02:28.780> there's<00:02:29.050> more<00:02:29.230> than<00:02:29.380> 1.8 00:02:29.730 --> 00:02:29.740 align:start position:0% the network so there's more than 1.8 00:02:29.740 --> 00:02:31.260 align:start position:0% the network so there's more than 1.8 million<00:02:29.980> smart<00:02:30.280> contracts<00:02:30.700> on<00:02:30.880> the<00:02:30.970> EVM 00:02:31.260 --> 00:02:31.270 align:start position:0% million smart contracts on the EVM 00:02:31.270 --> 00:02:33.060 align:start position:0% million smart contracts on the EVM that's<00:02:31.660> closer<00:02:31.900> to<00:02:32.020> 2<00:02:32.200> million<00:02:32.440> now<00:02:32.650> and 00:02:33.060 --> 00:02:33.070 align:start position:0% that's closer to 2 million now and 00:02:33.070 --> 00:02:36.180 align:start position:0% that's closer to 2 million now and they're<00:02:33.460> growing<00:02:34.650> so<00:02:35.650> let's<00:02:35.770> go<00:02:35.860> inside<00:02:36.070> the 00:02:36.180 --> 00:02:36.190 align:start position:0% they're growing so let's go inside the 00:02:36.190 --> 00:02:39.210 align:start position:0% they're growing so let's go inside the network<00:02:37.170> and<00:02:38.170> so<00:02:38.650> we<00:02:38.770> got<00:02:38.860> this<00:02:39.010> information 00:02:39.210 --> 00:02:39.220 align:start position:0% network and so we got this information 00:02:39.220 --> 00:02:41.760 align:start position:0% network and so we got this information from<00:02:39.580> ether<00:02:40.030> camp<00:02:40.270> and<00:02:40.480> ether<00:02:40.690> scan<00:02:40.960> since 00:02:41.760 --> 00:02:41.770 align:start position:0% from ether camp and ether scan since 00:02:41.770 --> 00:02:44.070 align:start position:0% from ether camp and ether scan since 2015<00:02:42.370> we've<00:02:42.880> been<00:02:43.090> slowly<00:02:43.360> growing<00:02:43.510> on<00:02:43.870> smart 00:02:44.070 --> 00:02:44.080 align:start position:0% 2015 we've been slowly growing on smart 00:02:44.080 --> 00:02:47.220 align:start position:0% 2015 we've been slowly growing on smart contracts<00:02:44.500> in<00:02:44.770> the<00:02:45.070> EVM<00:02:45.820> and<00:02:46.090> now<00:02:46.780> in<00:02:46.960> quarter 00:02:47.220 --> 00:02:47.230 align:start position:0% contracts in the EVM and now in quarter 00:02:47.230 --> 00:02:49.680 align:start position:0% contracts in the EVM and now in quarter 3<00:02:47.620> 2017<00:02:48.280> we've<00:02:48.460> have<00:02:48.670> more<00:02:49.000> than<00:02:49.120> a<00:02:49.180> million<00:02:49.480> in 00:02:49.680 --> 00:02:49.690 align:start position:0% 3 2017 we've have more than a million in 00:02:49.690 --> 00:02:51.840 align:start position:0% 3 2017 we've have more than a million in the<00:02:49.780> court<00:02:50.050> in<00:02:50.200> this<00:02:50.350> quarter<00:02:50.740> alone<00:02:51.070> deployed 00:02:51.840 --> 00:02:51.850 align:start position:0% the court in this quarter alone deployed 00:02:51.850 --> 00:02:53.820 align:start position:0% the court in this quarter alone deployed to<00:02:52.270> the<00:02:52.300> EVM<00:02:52.690> and<00:02:53.110> we<00:02:53.290> project<00:02:53.470> that<00:02:53.680> it's 00:02:53.820 --> 00:02:53.830 align:start position:0% to the EVM and we project that it's 00:02:53.830 --> 00:02:56.730 align:start position:0% to the EVM and we project that it's going<00:02:53.920> to<00:02:53.980> grow<00:02:54.540> until<00:02:55.540> we<00:02:55.630> get<00:02:55.840> you<00:02:56.110> know<00:02:56.140> 2018 00:02:56.730 --> 00:02:56.740 align:start position:0% going to grow until we get you know 2018 00:02:56.740 --> 00:02:58.080 align:start position:0% going to grow until we get you know 2018 where<00:02:56.860> we<00:02:56.950> have<00:02:57.100> a<00:02:57.130> million<00:02:57.460> smart<00:02:57.700> contracts 00:02:58.080 --> 00:02:58.090 align:start position:0% where we have a million smart contracts 00:02:58.090 --> 00:03:00.900 align:start position:0% where we have a million smart contracts per<00:02:58.270> month<00:02:58.570> and<00:02:59.250> if<00:03:00.250> you<00:03:00.370> compare<00:03:00.580> that<00:03:00.760> to 00:03:00.900 --> 00:03:00.910 align:start position:0% per month and if you compare that to 00:03:00.910 --> 00:03:03.720 align:start position:0% per month and if you compare that to blogging<00:03:01.840> there's<00:03:02.770> over<00:03:03.160> a<00:03:03.220> hundred<00:03:03.280> million 00:03:03.720 --> 00:03:03.730 align:start position:0% blogging there's over a hundred million 00:03:03.730 --> 00:03:07.380 align:start position:0% blogging there's over a hundred million blogs<00:03:04.150> created<00:03:04.480> each<00:03:04.750> month<00:03:05.400> and<00:03:06.400> so<00:03:07.150> that's<00:03:07.300> a 00:03:07.380 --> 00:03:07.390 align:start position:0% blogs created each month and so that's a 00:03:07.390 --> 00:03:09.330 align:start position:0% blogs created each month and so that's a trivial<00:03:07.630> number<00:03:07.990> when<00:03:08.710> you<00:03:08.830> compare<00:03:09.160> that<00:03:09.190> to 00:03:09.330 --> 00:03:09.340 align:start position:0% trivial number when you compare that to 00:03:09.340 --> 00:03:11.070 align:start position:0% trivial number when you compare that to these<00:03:09.790> systems<00:03:10.180> that<00:03:10.300> are<00:03:10.360> already<00:03:10.480> been 00:03:11.070 --> 00:03:11.080 align:start position:0% these systems that are already been 00:03:11.080 --> 00:03:14.490 align:start position:0% these systems that are already been extracted<00:03:11.770> and<00:03:11.830> are<00:03:11.980> being<00:03:12.160> used<00:03:12.430> and<00:03:13.180> so<00:03:14.170> what 00:03:14.490 --> 00:03:14.500 align:start position:0% extracted and are being used and so what 00:03:14.500 --> 00:03:15.810 align:start position:0% extracted and are being used and so what else<00:03:14.620> are<00:03:14.680> we<00:03:14.770> going<00:03:14.920> up<00:03:15.040> against<00:03:15.460> well 00:03:15.810 --> 00:03:15.820 align:start position:0% else are we going up against well 00:03:15.820 --> 00:03:18.840 align:start position:0% else are we going up against well difficulties<00:03:16.450> our<00:03:16.630> contract<00:03:17.050> so<00:03:18.010> we<00:03:18.040> have<00:03:18.280> you 00:03:18.840 --> 00:03:18.850 align:start position:0% difficulties our contract so we have you 00:03:18.850 --> 00:03:20.610 align:start position:0% difficulties our contract so we have you know<00:03:18.910> basic<00:03:19.510> nuances<00:03:19.990> like<00:03:20.020> the<00:03:20.260> differences 00:03:20.610 --> 00:03:20.620 align:start position:0% know basic nuances like the differences 00:03:20.620 --> 00:03:22.620 align:start position:0% know basic nuances like the differences between<00:03:20.800> send<00:03:21.190> transfer<00:03:21.670> and<00:03:21.910> call<00:03:22.480> that 00:03:22.620 --> 00:03:22.630 align:start position:0% between send transfer and call that 00:03:22.630 --> 00:03:24.410 align:start position:0% between send transfer and call that value<00:03:22.840> and<00:03:23.110> then<00:03:23.200> we<00:03:23.230> have<00:03:23.410> more<00:03:23.590> advanced 00:03:24.410 --> 00:03:24.420 align:start position:0% value and then we have more advanced 00:03:24.420 --> 00:03:28.260 align:start position:0% value and then we have more advanced nuances<00:03:25.420> like<00:03:25.450> reenter<00:03:26.440> C<00:03:26.590> issues<00:03:26.940> and<00:03:27.940> so<00:03:28.120> all 00:03:28.260 --> 00:03:28.270 align:start position:0% nuances like reenter C issues and so all 00:03:28.270 --> 00:03:30.720 align:start position:0% nuances like reenter C issues and so all this<00:03:28.420> adds<00:03:28.660> to<00:03:29.140> creating<00:03:29.980> going<00:03:30.370> back<00:03:30.520> into 00:03:30.720 --> 00:03:30.730 align:start position:0% this adds to creating going back into 00:03:30.730 --> 00:03:33.230 align:start position:0% this adds to creating going back into that<00:03:30.820> smart<00:03:31.150> contract<00:03:31.510> lifecycle<00:03:31.690> and 00:03:33.230 --> 00:03:33.240 align:start position:0% that smart contract lifecycle and 00:03:33.240 --> 00:03:35.610 align:start position:0% that smart contract lifecycle and running<00:03:34.240> through<00:03:34.420> it<00:03:34.570> over<00:03:35.080> again<00:03:35.170> because 00:03:35.610 --> 00:03:35.620 align:start position:0% running through it over again because 00:03:35.620 --> 00:03:37.580 align:start position:0% running through it over again because you<00:03:35.680> have<00:03:35.740> to<00:03:35.860> add<00:03:35.980> a<00:03:36.010> feature<00:03:36.250> fix<00:03:36.550> a<00:03:36.640> bug<00:03:36.790> and 00:03:37.580 --> 00:03:37.590 align:start position:0% you have to add a feature fix a bug and 00:03:37.590 --> 00:03:41.010 align:start position:0% you have to add a feature fix a bug and so<00:03:38.590> how<00:03:39.459> do<00:03:39.520> we<00:03:39.760> enable<00:03:39.910> rapid<00:03:40.450> smart<00:03:40.690> contract 00:03:41.010 --> 00:03:41.020 align:start position:0% so how do we enable rapid smart contract 00:03:41.020 --> 00:03:42.840 align:start position:0% so how do we enable rapid smart contract development<00:03:41.440> well<00:03:42.160> we<00:03:42.250> need<00:03:42.370> to<00:03:42.459> abstract<00:03:42.700> a 00:03:42.840 --> 00:03:42.850 align:start position:0% development well we need to abstract a 00:03:42.850 --> 00:03:46.590 align:start position:0% development well we need to abstract a few<00:03:43.030> things<00:03:43.270> from<00:03:43.360> here<00:03:43.600> namely<00:03:45.180> this<00:03:46.180> portion 00:03:46.590 --> 00:03:46.600 align:start position:0% few things from here namely this portion 00:03:46.600 --> 00:03:49.860 align:start position:0% few things from here namely this portion right<00:03:47.130> and<00:03:48.130> this<00:03:48.340> is<00:03:48.459> and<00:03:48.730> there's<00:03:49.390> this<00:03:49.690> has 00:03:49.860 --> 00:03:49.870 align:start position:0% right and this is and there's this has 00:03:49.870 --> 00:03:52.860 align:start position:0% right and this is and there's this has been<00:03:50.050> this<00:03:50.650> is<00:03:50.709> gonna<00:03:50.920> help<00:03:51.310> average<00:03:51.880> users<00:03:52.239> to 00:03:52.860 --> 00:03:52.870 align:start position:0% been this is gonna help average users to 00:03:52.870 --> 00:03:55.680 align:start position:0% been this is gonna help average users to use<00:03:53.020> this<00:03:53.110> platform<00:03:53.550> now<00:03:54.550> Alex<00:03:55.270> funder<00:03:55.510> son 00:03:55.680 --> 00:03:55.690 align:start position:0% use this platform now Alex funder son 00:03:55.690 --> 00:03:57.600 align:start position:0% use this platform now Alex funder son said<00:03:55.989> the<00:03:56.230> average<00:03:56.560> user<00:03:56.739> is<00:03:56.920> just<00:03:57.100> a<00:03:57.190> lift<00:03:57.370> and 00:03:57.600 --> 00:03:57.610 align:start position:0% said the average user is just a lift and 00:03:57.610 --> 00:04:00.180 align:start position:0% said the average user is just a lift and mystical<00:03:58.150> and<00:03:58.330> elusive<00:03:58.690> creature<00:03:58.900> but<00:03:59.470> that's 00:04:00.180 --> 00:04:00.190 align:start position:0% mystical and elusive creature but that's 00:04:00.190 --> 00:04:02.250 align:start position:0% mystical and elusive creature but that's not<00:04:00.700> true<00:04:00.880> because<00:04:00.940> we<00:04:01.270> know<00:04:01.390> who<00:04:01.510> the<00:04:01.630> average 00:04:02.250 --> 00:04:02.260 align:start position:0% not true because we know who the average 00:04:02.260 --> 00:04:06.630 align:start position:0% not true because we know who the average user<00:04:02.440> is<00:04:02.500> and<00:04:03.540> so<00:04:04.830> the<00:04:05.830> average<00:04:05.920> user<00:04:06.250> is 00:04:06.630 --> 00:04:06.640 align:start position:0% user is and so the average user is 00:04:06.640 --> 00:04:09.120 align:start position:0% user is and so the average user is really<00:04:07.570> developers<00:04:08.020> there's<00:04:08.830> a<00:04:08.860> highly 00:04:09.120 --> 00:04:09.130 align:start position:0% really developers there's a highly 00:04:09.130 --> 00:04:11.100 align:start position:0% really developers there's a highly technical<00:04:09.459> and<00:04:09.730> a<00:04:10.060> small<00:04:10.300> portion<00:04:10.480> is<00:04:10.780> just 00:04:11.100 --> 00:04:11.110 align:start position:0% technical and a small portion is just 00:04:11.110 --> 00:04:14.610 align:start position:0% technical and a small portion is just the<00:04:11.260> consumer<00:04:11.680> Chad<00:04:11.920> and<00:04:12.510> so<00:04:13.510> we<00:04:14.260> have<00:04:14.470> to 00:04:14.610 --> 00:04:14.620 align:start position:0% the consumer Chad and so we have to 00:04:14.620 --> 00:04:16.620 align:start position:0% the consumer Chad and so we have to develop<00:04:14.860> a<00:04:15.010> platform<00:04:15.220> that<00:04:15.970> targets<00:04:16.419> all 00:04:16.620 --> 00:04:16.630 align:start position:0% develop a platform that targets all 00:04:16.630 --> 00:04:18.240 align:start position:0% develop a platform that targets all three<00:04:16.930> of<00:04:17.020> these<00:04:17.140> to<00:04:17.410> enable<00:04:17.680> rapid<00:04:17.980> mark<00:04:18.130> on 00:04:18.240 --> 00:04:18.250 align:start position:0% three of these to enable rapid mark on 00:04:18.250 --> 00:04:20.090 align:start position:0% three of these to enable rapid mark on tech<00:04:18.400> development<00:04:18.760> and<00:04:18.880> mass<00:04:19.299> adoption<00:04:19.540> and 00:04:20.090 --> 00:04:20.100 align:start position:0% tech development and mass adoption and 00:04:20.100 --> 00:04:25.000 align:start position:0% tech development and mass adoption and so<00:04:21.100> how<00:04:21.760> do<00:04:21.820> we<00:04:21.880> do<00:04:22.000> that<00:04:22.530> well<00:04:23.530> we<00:04:23.620> start<00:04:23.860> small 00:04:25.000 --> 00:04:25.010 align:start position:0% so how do we do that well we start small 00:04:25.010 --> 00:04:26.800 align:start position:0% so how do we do that well we start small we<00:04:25.250> crawl<00:04:25.670> there<00:04:25.910> right<00:04:26.120> we<00:04:26.270> do<00:04:26.390> templates 00:04:26.800 --> 00:04:26.810 align:start position:0% we crawl there right we do templates 00:04:26.810 --> 00:04:28.150 align:start position:0% we crawl there right we do templates these<00:04:26.930> are<00:04:27.080> very<00:04:27.230> easy<00:04:27.470> just<00:04:27.890> fill<00:04:28.070> in<00:04:28.130> the 00:04:28.150 --> 00:04:28.160 align:start position:0% these are very easy just fill in the 00:04:28.160 --> 00:04:30.190 align:start position:0% these are very easy just fill in the blank<00:04:28.370> templates<00:04:28.760> yeah<00:04:28.910> very<00:04:29.690> one<00:04:29.960> use<00:04:30.140> case 00:04:30.190 --> 00:04:30.200 align:start position:0% blank templates yeah very one use case 00:04:30.200 --> 00:04:32.170 align:start position:0% blank templates yeah very one use case they<00:04:30.500> do<00:04:30.620> it<00:04:30.740> very<00:04:30.950> well<00:04:31.040> and<00:04:31.370> that's<00:04:31.790> it 00:04:32.170 --> 00:04:32.180 align:start position:0% they do it very well and that's it 00:04:32.180 --> 00:04:33.760 align:start position:0% they do it very well and that's it but<00:04:32.510> it's<00:04:32.630> too<00:04:32.780> narrow<00:04:32.930> and<00:04:33.500> that's<00:04:33.680> not 00:04:33.760 --> 00:04:33.770 align:start position:0% but it's too narrow and that's not 00:04:33.770 --> 00:04:36.220 align:start position:0% but it's too narrow and that's not enough<00:04:34.330> so<00:04:35.330> what's<00:04:35.510> the<00:04:35.600> next<00:04:35.720> step 00:04:36.220 --> 00:04:36.230 align:start position:0% enough so what's the next step 00:04:36.230 --> 00:04:38.110 align:start position:0% enough so what's the next step configurable<00:04:36.920> smart<00:04:37.160> contracts<00:04:37.580> you 00:04:38.110 --> 00:04:38.120 align:start position:0% configurable smart contracts you 00:04:38.120 --> 00:04:40.000 align:start position:0% configurable smart contracts you basically<00:04:38.480> take<00:04:38.780> that<00:04:38.990> template<00:04:39.440> and<00:04:39.620> you<00:04:39.830> add 00:04:40.000 --> 00:04:40.010 align:start position:0% basically take that template and you add 00:04:40.010 --> 00:04:42.460 align:start position:0% basically take that template and you add features<00:04:40.640> and<00:04:40.670> and<00:04:41.060> additions<00:04:41.900> to<00:04:41.990> it<00:04:42.140> so<00:04:42.380> you 00:04:42.460 --> 00:04:42.470 align:start position:0% features and and additions to it so you 00:04:42.470 --> 00:04:43.900 align:start position:0% features and and additions to it so you can<00:04:42.620> just<00:04:42.650> switch<00:04:42.980> on<00:04:43.160> and<00:04:43.370> off<00:04:43.400> what<00:04:43.640> you<00:04:43.760> need 00:04:43.900 --> 00:04:43.910 align:start position:0% can just switch on and off what you need 00:04:43.910 --> 00:04:45.730 align:start position:0% can just switch on and off what you need but<00:04:44.630> that<00:04:44.780> still<00:04:45.020> isn't<00:04:45.170> enough<00:04:45.440> because<00:04:45.590> that 00:04:45.730 --> 00:04:45.740 align:start position:0% but that still isn't enough because that 00:04:45.740 --> 00:04:48.460 align:start position:0% but that still isn't enough because that is<00:04:45.980> still<00:04:46.070> a<00:04:46.340> rather<00:04:46.550> narrow<00:04:46.850> use<00:04:47.090> case<00:04:47.300> and<00:04:48.020> so 00:04:48.460 --> 00:04:48.470 align:start position:0% is still a rather narrow use case and so 00:04:48.470 --> 00:04:51.730 align:start position:0% is still a rather narrow use case and so what's<00:04:48.650> the<00:04:48.770> next<00:04:48.890> step<00:04:50.320> smart<00:04:51.320> contract 00:04:51.730 --> 00:04:51.740 align:start position:0% what's the next step smart contract 00:04:51.740 --> 00:04:55.540 align:start position:0% what's the next step smart contract creation<00:04:52.100> via<00:04:52.820> a<00:04:52.880> GUI<00:04:53.590> so<00:04:54.590> what<00:04:54.740> we<00:04:54.830> can<00:04:54.980> do<00:04:55.160> is 00:04:55.540 --> 00:04:55.550 align:start position:0% creation via a GUI so what we can do is 00:04:55.550 --> 00:04:59.380 align:start position:0% creation via a GUI so what we can do is throw<00:04:56.120> a<00:04:56.150> template<00:04:56.720> or<00:04:57.110> throw<00:04:57.980> I'm<00:04:58.910> sorry<00:04:59.210> we 00:04:59.380 --> 00:04:59.390 align:start position:0% throw a template or throw I'm sorry we 00:04:59.390 --> 00:05:03.310 align:start position:0% throw a template or throw I'm sorry we can<00:04:59.540> throw<00:04:59.750> elements<00:05:00.320> of<00:05:00.470> GUI<00:05:01.720> onto<00:05:02.720> another<00:05:02.870> a 00:05:03.310 --> 00:05:03.320 align:start position:0% can throw elements of GUI onto another a 00:05:03.320 --> 00:05:05.860 align:start position:0% can throw elements of GUI onto another a canvas<00:05:04.190> and<00:05:04.400> we<00:05:04.640> can<00:05:04.820> abstract<00:05:05.180> code<00:05:05.540> from<00:05:05.720> it 00:05:05.860 --> 00:05:05.870 align:start position:0% canvas and we can abstract code from it 00:05:05.870 --> 00:05:08.260 align:start position:0% canvas and we can abstract code from it and<00:05:06.020> develop<00:05:06.380> our<00:05:06.500> smart<00:05:06.770> contracts<00:05:07.190> and<00:05:07.460> then 00:05:08.260 --> 00:05:08.270 align:start position:0% and develop our smart contracts and then 00:05:08.270 --> 00:05:09.970 align:start position:0% and develop our smart contracts and then reverse<00:05:08.600> we<00:05:08.990> can<00:05:09.140> take<00:05:09.290> our<00:05:09.380> smart<00:05:09.620> contract 00:05:09.970 --> 00:05:09.980 align:start position:0% reverse we can take our smart contract 00:05:09.980 --> 00:05:12.160 align:start position:0% reverse we can take our smart contract upload<00:05:10.340> it<00:05:10.430> into<00:05:10.550> the<00:05:10.610> platform<00:05:10.850> and<00:05:11.300> develop 00:05:12.160 --> 00:05:12.170 align:start position:0% upload it into the platform and develop 00:05:12.170 --> 00:05:15.190 align:start position:0% upload it into the platform and develop a<00:05:12.320> GUI<00:05:12.770> from<00:05:13.400> it<00:05:13.580> so<00:05:14.420> you<00:05:14.480> can<00:05:14.630> interact<00:05:14.930> with 00:05:15.190 --> 00:05:15.200 align:start position:0% a GUI from it so you can interact with 00:05:15.200 --> 00:05:17.950 align:start position:0% a GUI from it so you can interact with your<00:05:15.410> smart<00:05:15.650> contract<00:05:16.090> and<00:05:17.090> so<00:05:17.810> we've 00:05:17.950 --> 00:05:17.960 align:start position:0% your smart contract and so we've 00:05:17.960 --> 00:05:21.250 align:start position:0% your smart contract and so we've answered<00:05:18.110> the<00:05:18.380> what<00:05:19.190> and<00:05:19.430> the<00:05:19.460> why<00:05:20.180> and<00:05:20.480> well 00:05:21.250 --> 00:05:21.260 align:start position:0% answered the what and the why and well 00:05:21.260 --> 00:05:39.159 align:start position:0% answered the what and the why and well now<00:05:21.590> we<00:05:21.650> got<00:05:21.800> to<00:05:21.860> answer<00:05:21.950> the<00:05:22.160> powell 00:05:39.159 --> 00:05:39.169 align:start position:0% 00:05:39.169 --> 00:05:42.050 align:start position:0% hello<00:05:40.169> everyone<00:05:40.440> I'm<00:05:40.710> Matt<00:05:40.770> Swezey<00:05:41.190> founder 00:05:42.050 --> 00:05:42.060 align:start position:0% hello everyone I'm Matt Swezey founder 00:05:42.060 --> 00:05:44.629 align:start position:0% hello everyone I'm Matt Swezey founder product<00:05:42.479> lead<00:05:42.630> and<00:05:42.840> developer<00:05:43.229> at<00:05:43.380> pactum<00:05:43.710> how 00:05:44.629 --> 00:05:44.639 align:start position:0% product lead and developer at pactum how 00:05:44.639 --> 00:05:46.159 align:start position:0% product lead and developer at pactum how would<00:05:44.790> one<00:05:45.000> build<00:05:45.270> such<00:05:45.479> a<00:05:45.510> platform<00:05:45.960> to 00:05:46.159 --> 00:05:46.169 align:start position:0% would one build such a platform to 00:05:46.169 --> 00:05:48.409 align:start position:0% would one build such a platform to further<00:05:46.410> encourage<00:05:46.820> mass<00:05:47.820> adoption<00:05:48.030> and 00:05:48.409 --> 00:05:48.419 align:start position:0% further encourage mass adoption and 00:05:48.419 --> 00:05:51.460 align:start position:0% further encourage mass adoption and enable<00:05:48.690> rapid<00:05:49.050> smart<00:05:49.350> contract<00:05:49.680> development 00:05:51.460 --> 00:05:51.470 align:start position:0% enable rapid smart contract development 00:05:51.470 --> 00:06:12.659 align:start position:0% enable rapid smart contract development first<00:05:52.470> let's<00:05:52.830> do<00:05:52.949> a<00:05:52.979> quick<00:05:58.160> user<00:05:59.160> error 00:06:12.659 --> 00:06:12.669 align:start position:0% 00:06:12.669 --> 00:06:18.890 align:start position:0% there<00:06:13.300> you 00:06:18.890 --> 00:06:18.900 align:start position:0% 00:06:18.900 --> 00:06:20.659 align:start position:0% I'm<00:06:19.350> sure<00:06:19.560> many<00:06:19.740> of<00:06:19.919> you<00:06:20.040> have<00:06:20.190> seen<00:06:20.370> and 00:06:20.659 --> 00:06:20.669 align:start position:0% I'm sure many of you have seen and 00:06:20.669 --> 00:06:22.129 align:start position:0% I'm sure many of you have seen and recognize<00:06:21.030> this<00:06:21.150> diagram<00:06:21.570> this<00:06:21.930> platform 00:06:22.129 --> 00:06:22.139 align:start position:0% recognize this diagram this platform 00:06:22.139 --> 00:06:24.469 align:start position:0% recognize this diagram this platform needs<00:06:22.530> to<00:06:22.620> be<00:06:22.740> able<00:06:22.830> to<00:06:22.949> receive<00:06:23.250> store<00:06:23.820> Allies 00:06:24.469 --> 00:06:24.479 align:start position:0% needs to be able to receive store Allies 00:06:24.479 --> 00:06:26.390 align:start position:0% needs to be able to receive store Allies and<00:06:24.750> compile<00:06:25.139> solidity<00:06:25.680> and<00:06:25.770> VIPRE<00:06:26.070> source 00:06:26.390 --> 00:06:26.400 align:start position:0% and compile solidity and VIPRE source 00:06:26.400 --> 00:06:28.430 align:start position:0% and compile solidity and VIPRE source code<00:06:26.729> as<00:06:27.270> well<00:06:27.419> as<00:06:27.479> captured<00:06:27.930> the<00:06:28.050> generated 00:06:28.430 --> 00:06:28.440 align:start position:0% code as well as captured the generated 00:06:28.440 --> 00:06:30.740 align:start position:0% code as well as captured the generated ABI<00:06:28.860> and<00:06:29.250> byte<00:06:29.490> code<00:06:29.699> and<00:06:30.210> be<00:06:30.330> able<00:06:30.389> to<00:06:30.570> sign 00:06:30.740 --> 00:06:30.750 align:start position:0% ABI and byte code and be able to sign 00:06:30.750 --> 00:06:32.830 align:start position:0% ABI and byte code and be able to sign and<00:06:31.050> submit<00:06:31.169> transactions<00:06:31.860> to<00:06:32.220> the<00:06:32.250> EVM 00:06:32.830 --> 00:06:32.840 align:start position:0% and submit transactions to the EVM 00:06:32.840 --> 00:06:35.450 align:start position:0% and submit transactions to the EVM there's<00:06:33.840> nothing<00:06:34.110> new<00:06:34.229> here<00:06:34.259> what<00:06:35.130> is<00:06:35.220> needed 00:06:35.450 --> 00:06:35.460 align:start position:0% there's nothing new here what is needed 00:06:35.460 --> 00:06:37.939 align:start position:0% there's nothing new here what is needed is<00:06:35.759> an<00:06:35.910> interactive<00:06:36.419> friendly<00:06:37.199> UI<00:06:37.350> to<00:06:37.770> allow 00:06:37.939 --> 00:06:37.949 align:start position:0% is an interactive friendly UI to allow 00:06:37.949 --> 00:06:40.400 align:start position:0% is an interactive friendly UI to allow everyday<00:06:38.639> people<00:06:39.000> are<00:06:39.210> not<00:06:39.570> developers<00:06:40.110> to 00:06:40.400 --> 00:06:40.410 align:start position:0% everyday people are not developers to 00:06:40.410 --> 00:06:42.409 align:start position:0% everyday people are not developers to build<00:06:40.560> out<00:06:40.740> and<00:06:40.949> deploy<00:06:41.130> smart<00:06:41.520> contracts<00:06:41.940> to 00:06:42.409 --> 00:06:42.419 align:start position:0% build out and deploy smart contracts to 00:06:42.419 --> 00:06:45.140 align:start position:0% build out and deploy smart contracts to meet<00:06:43.020> their<00:06:43.229> unique<00:06:43.259> needs<00:06:43.770> at<00:06:44.580> the<00:06:44.699> same<00:06:44.910> time 00:06:45.140 --> 00:06:45.150 align:start position:0% meet their unique needs at the same time 00:06:45.150 --> 00:06:46.730 align:start position:0% meet their unique needs at the same time this<00:06:45.479> platform<00:06:45.780> cannot<00:06:46.289> forget<00:06:46.620> about 00:06:46.730 --> 00:06:46.740 align:start position:0% this platform cannot forget about 00:06:46.740 --> 00:06:49.219 align:start position:0% this platform cannot forget about developers<00:06:47.250> more<00:06:47.970> on<00:06:48.030> that<00:06:48.120> later<00:06:48.240> now<00:06:48.570> let's 00:06:49.219 --> 00:06:49.229 align:start position:0% developers more on that later now let's 00:06:49.229 --> 00:06:57.710 align:start position:0% developers more on that later now let's explore<00:06:49.530> the<00:06:49.680> platform<00:06:50.100> layer<00:06:50.490> by<00:06:50.669> layer<00:06:56.720> the 00:06:57.710 --> 00:06:57.720 align:start position:0% explore the platform layer by layer the 00:06:57.720 --> 00:06:59.570 align:start position:0% explore the platform layer by layer the platform<00:06:58.080> needs<00:06:58.199> a<00:06:58.289> killer<00:06:58.590> UI<00:06:58.770> and<00:06:59.190> an 00:06:59.570 --> 00:06:59.580 align:start position:0% platform needs a killer UI and an 00:06:59.580 --> 00:07:02.029 align:start position:0% platform needs a killer UI and an Internet<00:07:00.110> intuitive<00:07:01.110> and<00:07:01.260> cutting-edge<00:07:01.650> UX 00:07:02.029 --> 00:07:02.039 align:start position:0% Internet intuitive and cutting-edge UX 00:07:02.039 --> 00:07:04.610 align:start position:0% Internet intuitive and cutting-edge UX that<00:07:02.250> is<00:07:02.370> a<00:07:02.400> must<00:07:02.669> do<00:07:03.479> UI<00:07:03.630> needs<00:07:03.870> to<00:07:03.930> be<00:07:04.080> desktop 00:07:04.610 --> 00:07:04.620 align:start position:0% that is a must do UI needs to be desktop 00:07:04.620 --> 00:07:05.450 align:start position:0% that is a must do UI needs to be desktop and<00:07:04.800> mobile<00:07:04.860> friendly 00:07:05.450 --> 00:07:05.460 align:start position:0% and mobile friendly 00:07:05.460 --> 00:07:07.279 align:start position:0% and mobile friendly thanks<00:07:05.850> to<00:07:05.940> dozens<00:07:06.330> of<00:07:06.419> front-end<00:07:06.750> libraries 00:07:07.279 --> 00:07:07.289 align:start position:0% thanks to dozens of front-end libraries 00:07:07.289 --> 00:07:08.960 align:start position:0% thanks to dozens of front-end libraries frameworks<00:07:07.830> and<00:07:08.010> templating<00:07:08.370> engines<00:07:08.760> such 00:07:08.960 --> 00:07:08.970 align:start position:0% frameworks and templating engines such 00:07:08.970 --> 00:07:11.629 align:start position:0% frameworks and templating engines such as<00:07:09.090> jQuery<00:07:09.419> and<00:07:10.080> Euler<00:07:10.440> bootstrap<00:07:11.190> mustache 00:07:11.629 --> 00:07:11.639 align:start position:0% as jQuery and Euler bootstrap mustache 00:07:11.639 --> 00:07:13.810 align:start position:0% as jQuery and Euler bootstrap mustache and<00:07:11.910> various<00:07:12.150> others<00:07:12.510> building<00:07:13.260> such<00:07:13.380> a<00:07:13.410> UI 00:07:13.810 --> 00:07:13.820 align:start position:0% and various others building such a UI 00:07:13.820 --> 00:07:16.070 align:start position:0% and various others building such a UI won't<00:07:14.820> be<00:07:14.910> much<00:07:15.180> of<00:07:15.210> a<00:07:15.360> challenge<00:07:15.510> once<00:07:15.960> the 00:07:16.070 --> 00:07:16.080 align:start position:0% won't be much of a challenge once the 00:07:16.080 --> 00:07:18.680 align:start position:0% won't be much of a challenge once the design<00:07:16.320> has<00:07:16.500> been<00:07:16.650> established<00:07:17.509> required<00:07:18.509> at 00:07:18.680 --> 00:07:18.690 align:start position:0% design has been established required at 00:07:18.690 --> 00:07:21.260 align:start position:0% design has been established required at the<00:07:18.750> client-side<00:07:19.320> is<00:07:19.680> web<00:07:20.190> 3j<00:07:21.120> s 00:07:21.260 --> 00:07:21.270 align:start position:0% the client-side is web 3j s 00:07:21.270 --> 00:07:23.000 align:start position:0% the client-side is web 3j s implementation<00:07:21.990> and<00:07:22.259> third-party<00:07:22.620> wallet 00:07:23.000 --> 00:07:23.010 align:start position:0% implementation and third-party wallet 00:07:23.010 --> 00:07:25.159 align:start position:0% implementation and third-party wallet integration<00:07:23.610> for<00:07:24.030> outside<00:07:24.300> wallets<00:07:24.690> such<00:07:25.020> as 00:07:25.159 --> 00:07:25.169 align:start position:0% integration for outside wallets such as 00:07:25.169 --> 00:07:28.490 align:start position:0% integration for outside wallets such as meta<00:07:25.800> mask<00:07:26.010> to<00:07:26.580> allow<00:07:26.729> users<00:07:27.000> that<00:07:27.330> to<00:07:27.750> control 00:07:28.490 --> 00:07:28.500 align:start position:0% meta mask to allow users that to control 00:07:28.500 --> 00:07:30.529 align:start position:0% meta mask to allow users that to control their<00:07:28.620> own<00:07:28.650> wallets<00:07:29.160> directly<00:07:30.060> or<00:07:30.240> indirectly 00:07:30.529 --> 00:07:30.539 align:start position:0% their own wallets directly or indirectly 00:07:30.539 --> 00:07:39.290 align:start position:0% their own wallets directly or indirectly to<00:07:31.199> sign<00:07:31.410> and<00:07:31.650> submit<00:07:31.770> transactions<00:07:38.300> mobile 00:07:39.290 --> 00:07:39.300 align:start position:0% to sign and submit transactions mobile 00:07:39.300 --> 00:07:41.540 align:start position:0% to sign and submit transactions mobile developers<00:07:39.750> web<00:07:40.229> app<00:07:40.380> developers<00:07:40.889> back-end 00:07:41.540 --> 00:07:41.550 align:start position:0% developers web app developers back-end 00:07:41.550 --> 00:07:43.250 align:start position:0% developers web app developers back-end developers<00:07:42.000> front-end<00:07:42.810> developers 00:07:43.250 --> 00:07:43.260 align:start position:0% developers front-end developers 00:07:43.260 --> 00:07:45.260 align:start position:0% developers front-end developers blockchain<00:07:44.039> and<00:07:44.070> finally<00:07:44.520> smart<00:07:44.820> contract 00:07:45.260 --> 00:07:45.270 align:start position:0% blockchain and finally smart contract 00:07:45.270 --> 00:07:47.089 align:start position:0% blockchain and finally smart contract developers<00:07:45.659> there's<00:07:46.139> such<00:07:46.289> a<00:07:46.320> vast<00:07:46.620> amount<00:07:46.979> of 00:07:47.089 --> 00:07:47.099 align:start position:0% developers there's such a vast amount of 00:07:47.099 --> 00:07:48.710 align:start position:0% developers there's such a vast amount of skill<00:07:47.310> sets<00:07:47.520> out<00:07:47.669> there<00:07:47.820> it's<00:07:48.030> impossible<00:07:48.330> to 00:07:48.710 --> 00:07:48.720 align:start position:0% skill sets out there it's impossible to 00:07:48.720 --> 00:07:50.960 align:start position:0% skill sets out there it's impossible to master<00:07:48.870> them<00:07:49.199> all<00:07:49.320> the<00:07:49.919> API<00:07:50.220> layer<00:07:50.520> of<00:07:50.849> the 00:07:50.960 --> 00:07:50.970 align:start position:0% master them all the API layer of the 00:07:50.970 --> 00:07:52.580 align:start position:0% master them all the API layer of the platform<00:07:51.300> will<00:07:51.419> enable<00:07:51.539> any<00:07:51.960> developer<00:07:52.470> to 00:07:52.580 --> 00:07:52.590 align:start position:0% platform will enable any developer to 00:07:52.590 --> 00:07:54.170 align:start position:0% platform will enable any developer to harness<00:07:52.919> the<00:07:53.159> power<00:07:53.370> of<00:07:53.430> smart<00:07:53.760> contracts 00:07:54.170 --> 00:07:54.180 align:start position:0% harness the power of smart contracts 00:07:54.180 --> 00:07:56.390 align:start position:0% harness the power of smart contracts without<00:07:54.780> having<00:07:55.080> to<00:07:55.229> wrestle<00:07:55.470> actual<00:07:56.130> smart 00:07:56.390 --> 00:07:56.400 align:start position:0% without having to wrestle actual smart 00:07:56.400 --> 00:07:58.490 align:start position:0% without having to wrestle actual smart contract<00:07:56.789> code<00:07:57.020> this<00:07:58.020> layer<00:07:58.229> of<00:07:58.349> abstraction 00:07:58.490 --> 00:07:58.500 align:start position:0% contract code this layer of abstraction 00:07:58.500 --> 00:08:00.409 align:start position:0% contract code this layer of abstraction will<00:07:58.949> empower<00:07:59.220> regular<00:07:59.669> websites<00:08:00.150> and 00:08:00.409 --> 00:08:00.419 align:start position:0% will empower regular websites and 00:08:00.419 --> 00:08:02.659 align:start position:0% will empower regular websites and applications<00:08:00.510> to<00:08:01.020> deploy<00:08:01.289> execute<00:08:02.220> and<00:08:02.370> query 00:08:02.659 --> 00:08:02.669 align:start position:0% applications to deploy execute and query 00:08:02.669 --> 00:08:04.339 align:start position:0% applications to deploy execute and query the<00:08:02.729> EVM<00:08:03.210> without<00:08:03.630> needing<00:08:03.870> to<00:08:03.900> do<00:08:04.050> actual 00:08:04.339 --> 00:08:04.349 align:start position:0% the EVM without needing to do actual 00:08:04.349 --> 00:08:06.560 align:start position:0% the EVM without needing to do actual code<00:08:04.650> development<00:08:05.039> themselves<00:08:05.699> save<00:08:06.270> me<00:08:06.360> time 00:08:06.560 --> 00:08:06.570 align:start position:0% code development themselves save me time 00:08:06.570 --> 00:08:08.990 align:start position:0% code development themselves save me time money<00:08:07.169> and<00:08:07.409> stress<00:08:07.500> of<00:08:07.979> having<00:08:08.099> learning<00:08:08.849> a 00:08:08.990 --> 00:08:09.000 align:start position:0% money and stress of having learning a 00:08:09.000 --> 00:08:14.170 align:start position:0% money and stress of having learning a new<00:08:09.300> skill<00:08:09.419> set 00:08:14.170 --> 00:08:14.180 align:start position:0% 00:08:14.180 --> 00:08:15.700 align:start position:0% moving<00:08:14.900> on<00:08:15.020> to<00:08:15.140> the<00:08:15.230> meat<00:08:15.440> and<00:08:15.470> the<00:08:15.680> potatoes 00:08:15.700 --> 00:08:15.710 align:start position:0% moving on to the meat and the potatoes 00:08:15.710 --> 00:08:17.920 align:start position:0% moving on to the meat and the potatoes of<00:08:16.400> the<00:08:16.490> platform<00:08:16.910> the<00:08:17.330> middle<00:08:17.600> layer<00:08:17.750> of<00:08:17.780> the 00:08:17.920 --> 00:08:17.930 align:start position:0% of the platform the middle layer of the 00:08:17.930 --> 00:08:20.140 align:start position:0% of the platform the middle layer of the stack<00:08:18.080> or<00:08:18.920> the<00:08:18.980> back<00:08:19.190> end<00:08:19.370> of<00:08:19.400> the<00:08:19.520> platform<00:08:19.910> is 00:08:20.140 --> 00:08:20.150 align:start position:0% stack or the back end of the platform is 00:08:20.150 --> 00:08:22.360 align:start position:0% stack or the back end of the platform is what<00:08:20.330> connects<00:08:20.570> the<00:08:20.720> UI<00:08:20.870> api<00:08:21.530> to<00:08:21.650> the<00:08:21.980> EBM 00:08:22.360 --> 00:08:22.370 align:start position:0% what connects the UI api to the EBM 00:08:22.370 --> 00:08:24.220 align:start position:0% what connects the UI api to the EBM along<00:08:23.030> with<00:08:23.180> running<00:08:23.480> other<00:08:23.660> methods<00:08:24.080> and 00:08:24.220 --> 00:08:24.230 align:start position:0% along with running other methods and 00:08:24.230 --> 00:08:26.470 align:start position:0% along with running other methods and business<00:08:24.500> logic<00:08:24.710> to<00:08:25.610> interact<00:08:25.910> with<00:08:25.970> the<00:08:26.120> EVM 00:08:26.470 --> 00:08:26.480 align:start position:0% business logic to interact with the EVM 00:08:26.480 --> 00:08:28.120 align:start position:0% business logic to interact with the EVM the<00:08:26.810> middle<00:08:27.080> layer<00:08:27.170> needs<00:08:27.410> to<00:08:27.530> leverage<00:08:27.860> web 00:08:28.120 --> 00:08:28.130 align:start position:0% the middle layer needs to leverage web 00:08:28.130 --> 00:08:31.620 align:start position:0% the middle layer needs to leverage web 3gs<00:08:28.580> for<00:08:29.090> JSON<00:08:29.420> RPC<00:08:30.140> calls<00:08:30.800> to<00:08:30.950> the<00:08:31.040> EVM<00:08:31.340> nodes 00:08:31.620 --> 00:08:31.630 align:start position:0% 3gs for JSON RPC calls to the EVM nodes 00:08:31.630 --> 00:08:34.390 align:start position:0% 3gs for JSON RPC calls to the EVM nodes luckily<00:08:32.630> for<00:08:32.750> us<00:08:32.810> back<00:08:33.050> in<00:08:33.110> developers<00:08:33.740> we 00:08:34.390 --> 00:08:34.400 align:start position:0% luckily for us back in developers we 00:08:34.400 --> 00:08:36.670 align:start position:0% luckily for us back in developers we have<00:08:34.490> Java<00:08:34.730> and.net<00:08:35.090> libraries<00:08:35.840> such<00:08:36.170> as<00:08:36.200> web 00:08:36.670 --> 00:08:36.680 align:start position:0% have Java and.net libraries such as web 00:08:36.680 --> 00:08:38.680 align:start position:0% have Java and.net libraries such as web 3j<00:08:37.100> and<00:08:37.400> aetherium<00:08:37.940> two<00:08:38.210> important<00:08:38.600> two 00:08:38.680 --> 00:08:38.690 align:start position:0% 3j and aetherium two important two 00:08:38.690 --> 00:08:40.660 align:start position:0% 3j and aetherium two important two projects<00:08:39.110> as<00:08:39.230> dependencies<00:08:39.770> eliminating<00:08:40.580> the 00:08:40.660 --> 00:08:40.670 align:start position:0% projects as dependencies eliminating the 00:08:40.670 --> 00:08:43.800 align:start position:0% projects as dependencies eliminating the need<00:08:40.880> to<00:08:41.180> code<00:08:41.780> direct<00:08:42.200> web<00:08:42.500> 3<00:08:42.770> JS<00:08:43.010> integration 00:08:43.800 --> 00:08:43.810 align:start position:0% need to code direct web 3 JS integration 00:08:43.810 --> 00:08:46.690 align:start position:0% need to code direct web 3 JS integration developers<00:08:44.810> can<00:08:45.020> now<00:08:45.140> call<00:08:45.440> Java<00:08:45.980> and<00:08:46.370> c-sharp 00:08:46.690 --> 00:08:46.700 align:start position:0% developers can now call Java and c-sharp 00:08:46.700 --> 00:08:48.870 align:start position:0% developers can now call Java and c-sharp methods<00:08:47.270> to<00:08:47.540> interact<00:08:47.840> with<00:08:47.900> the<00:08:48.050> blockchain 00:08:48.870 --> 00:08:48.880 align:start position:0% methods to interact with the blockchain 00:08:48.880 --> 00:08:52.420 align:start position:0% methods to interact with the blockchain now<00:08:49.880> what<00:08:50.480> are<00:08:50.570> other<00:08:50.720> features<00:08:50.990> this<00:08:51.440> should 00:08:52.420 --> 00:08:52.430 align:start position:0% now what are other features this should 00:08:52.430 --> 00:08:54.250 align:start position:0% now what are other features this should be<00:08:52.520> extracted<00:08:53.210> to<00:08:53.570> accelerate<00:08:53.960> smart 00:08:54.250 --> 00:08:54.260 align:start position:0% be extracted to accelerate smart 00:08:54.260 --> 00:08:59.440 align:start position:0% be extracted to accelerate smart contract<00:08:54.770> adoption<00:08:57.730> username<00:08:58.730> to<00:08:59.090> wallet 00:08:59.440 --> 00:08:59.450 align:start position:0% contract adoption username to wallet 00:08:59.450 --> 00:09:02.110 align:start position:0% contract adoption username to wallet address<00:09:00.050> association<00:09:00.770> similar<00:09:01.430> to<00:09:01.550> how<00:09:01.610> ENS 00:09:02.110 --> 00:09:02.120 align:start position:0% address association similar to how ENS 00:09:02.120 --> 00:09:03.790 align:start position:0% address association similar to how ENS works<00:09:02.360> but<00:09:02.930> now<00:09:03.050> for<00:09:03.320> contact<00:09:03.710> information 00:09:03.790 --> 00:09:03.800 align:start position:0% works but now for contact information 00:09:03.800 --> 00:09:07.180 align:start position:0% works but now for contact information says<00:09:04.460> phone<00:09:05.060> numbers<00:09:05.390> emails<00:09:05.870> user<00:09:06.170> names<00:09:06.440> can 00:09:07.180 --> 00:09:07.190 align:start position:0% says phone numbers emails user names can 00:09:07.190 --> 00:09:09.070 align:start position:0% says phone numbers emails user names can be<00:09:07.280> used<00:09:07.430> instead<00:09:07.700> of<00:09:07.760> handling<00:09:08.150> 40<00:09:08.690> character 00:09:09.070 --> 00:09:09.080 align:start position:0% be used instead of handling 40 character 00:09:09.080 --> 00:09:11.620 align:start position:0% be used instead of handling 40 character hexadecimal<00:09:09.740> strings<00:09:10.100> if<00:09:10.370> you<00:09:10.820> exclude<00:09:11.600> the 00:09:11.620 --> 00:09:11.630 align:start position:0% hexadecimal strings if you exclude the 00:09:11.630 --> 00:09:14.710 align:start position:0% hexadecimal strings if you exclude the prefix<00:09:12.460> with<00:09:13.460> these<00:09:13.580> associations<00:09:14.060> users 00:09:14.710 --> 00:09:14.720 align:start position:0% prefix with these associations users 00:09:14.720 --> 00:09:16.450 align:start position:0% prefix with these associations users will<00:09:14.870> now<00:09:14.960> be<00:09:15.110> able<00:09:15.170> to<00:09:15.800> have<00:09:15.950> a<00:09:15.980> directory 00:09:16.450 --> 00:09:16.460 align:start position:0% will now be able to have a directory 00:09:16.460 --> 00:09:17.920 align:start position:0% will now be able to have a directory lookup<00:09:16.820> and<00:09:17.030> keep<00:09:17.330> their<00:09:17.450> own<00:09:17.570> private 00:09:17.920 --> 00:09:17.930 align:start position:0% lookup and keep their own private 00:09:17.930 --> 00:09:21.640 align:start position:0% lookup and keep their own private address<00:09:18.260> book<00:09:18.470> on<00:09:18.620> the<00:09:18.920> platform<00:09:20.650> another 00:09:21.640 --> 00:09:21.650 align:start position:0% address book on the platform another 00:09:21.650 --> 00:09:24.130 align:start position:0% address book on the platform another example<00:09:21.770> is<00:09:22.280> wallet<00:09:22.730> management<00:09:23.240> while<00:09:24.020> at 00:09:24.130 --> 00:09:24.140 align:start position:0% example is wallet management while at 00:09:24.140 --> 00:09:26.650 align:start position:0% example is wallet management while at generation<00:09:24.590> security<00:09:25.310> and<00:09:25.490> handling<00:09:25.850> for<00:09:26.450> new 00:09:26.650 --> 00:09:26.660 align:start position:0% generation security and handling for new 00:09:26.660 --> 00:09:29.320 align:start position:0% generation security and handling for new non<00:09:27.050> tech<00:09:27.530> savvy<00:09:27.860> users<00:09:28.190> are<00:09:28.610> those<00:09:29.060> wanting 00:09:29.320 --> 00:09:29.330 align:start position:0% non tech savvy users are those wanting 00:09:29.330 --> 00:09:30.340 align:start position:0% non tech savvy users are those wanting to<00:09:29.420> be<00:09:29.480> lazy<00:09:29.720> and<00:09:29.930> not<00:09:29.990> worrying<00:09:30.290> about 00:09:30.340 --> 00:09:30.350 align:start position:0% to be lazy and not worrying about 00:09:30.350 --> 00:09:33.700 align:start position:0% to be lazy and not worrying about handling<00:09:30.770> their<00:09:30.980> private<00:09:31.280> keys<00:09:32.470> this<00:09:33.470> is<00:09:33.560> not 00:09:33.700 --> 00:09:33.710 align:start position:0% handling their private keys this is not 00:09:33.710 --> 00:09:35.080 align:start position:0% handling their private keys this is not the<00:09:33.800> preferred<00:09:34.130> method<00:09:34.490> though<00:09:34.610> amongst 00:09:35.080 --> 00:09:35.090 align:start position:0% the preferred method though amongst 00:09:35.090 --> 00:09:36.820 align:start position:0% the preferred method though amongst early<00:09:35.330> adopters<00:09:35.810> before<00:09:36.470> mass<00:09:36.590> adoption 00:09:36.820 --> 00:09:36.830 align:start position:0% early adopters before mass adoption 00:09:36.830 --> 00:09:38.500 align:start position:0% early adopters before mass adoption there<00:09:37.310> must<00:09:37.490> be<00:09:37.640> a<00:09:37.670> middle<00:09:37.970> ground<00:09:38.210> to 00:09:38.500 --> 00:09:38.510 align:start position:0% there must be a middle ground to 00:09:38.510 --> 00:09:46.570 align:start position:0% there must be a middle ground to encourage<00:09:39.170> new<00:09:39.500> user<00:09:39.740> growth<00:09:44.950> and<00:09:45.950> finally<00:09:46.340> to 00:09:46.570 --> 00:09:46.580 align:start position:0% encourage new user growth and finally to 00:09:46.580 --> 00:09:48.640 align:start position:0% encourage new user growth and finally to the<00:09:46.670> EVM<00:09:47.090> note<00:09:47.300> layer<00:09:47.480> the<00:09:48.110> platform<00:09:48.500> should 00:09:48.640 --> 00:09:48.650 align:start position:0% the EVM note layer the platform should 00:09:48.650 --> 00:09:51.100 align:start position:0% the EVM note layer the platform should have<00:09:48.890> its<00:09:49.700> own<00:09:49.790> local<00:09:50.180> within<00:09:50.510> iam<00:09:50.690> clients 00:09:51.100 --> 00:09:51.110 align:start position:0% have its own local within iam clients 00:09:51.110 --> 00:09:53.110 align:start position:0% have its own local within iam clients one<00:09:51.560> to<00:09:51.830> support<00:09:52.160> that<00:09:52.310> both<00:09:52.490> the<00:09:52.760> test<00:09:52.970> net 00:09:53.110 --> 00:09:53.120 align:start position:0% one to support that both the test net 00:09:53.120 --> 00:09:55.660 align:start position:0% one to support that both the test net and<00:09:53.300> main<00:09:53.450> it<00:09:53.630> works<00:09:54.020> and<00:09:54.800> also<00:09:55.220> in<00:09:55.340> order<00:09:55.490> to 00:09:55.660 --> 00:09:55.670 align:start position:0% and main it works and also in order to 00:09:55.670 --> 00:09:57.610 align:start position:0% and main it works and also in order to deploy<00:09:55.850> execute<00:09:56.540> and<00:09:56.660> query<00:09:56.870> smart<00:09:57.170> contracts 00:09:57.610 --> 00:09:57.620 align:start position:0% deploy execute and query smart contracts 00:09:57.620 --> 00:09:59.800 align:start position:0% deploy execute and query smart contracts as<00:09:57.830> well<00:09:58.190> as<00:09:58.460> send<00:09:58.700> transactions<00:09:59.270> if<00:09:59.510> the<00:09:59.630> user 00:09:59.800 --> 00:09:59.810 align:start position:0% as well as send transactions if the user 00:09:59.810 --> 00:10:01.840 align:start position:0% as well as send transactions if the user is<00:09:59.960> utilizing<00:10:00.380> the<00:10:00.560> platform's<00:10:01.190> user<00:10:01.430> wallet 00:10:01.840 --> 00:10:01.850 align:start position:0% is utilizing the platform's user wallet 00:10:01.850 --> 00:10:08.680 align:start position:0% is utilizing the platform's user wallet management<00:10:02.300> system<00:10:02.600> now<00:10:07.330> here's<00:10:08.330> the<00:10:08.450> stack 00:10:08.680 --> 00:10:08.690 align:start position:0% management system now here's the stack 00:10:08.690 --> 00:10:10.300 align:start position:0% management system now here's the stack as<00:10:08.900> the<00:10:09.050> layers<00:10:09.260> come<00:10:09.470> together<00:10:09.590> and<00:10:10.100> let's 00:10:10.300 --> 00:10:10.310 align:start position:0% as the layers come together and let's 00:10:10.310 --> 00:10:13.030 align:start position:0% as the layers come together and let's run<00:10:10.670> through<00:10:10.910> a<00:10:11.300> non<00:10:12.020> developer<00:10:12.500> user<00:10:12.650> story 00:10:13.030 --> 00:10:13.040 align:start position:0% run through a non developer user story 00:10:13.040 --> 00:10:14.860 align:start position:0% run through a non developer user story to<00:10:13.490> see<00:10:13.640> how<00:10:13.760> the<00:10:13.820> platform<00:10:14.420> stack<00:10:14.690> is 00:10:14.860 --> 00:10:14.870 align:start position:0% to see how the platform stack is 00:10:14.870 --> 00:10:19.600 align:start position:0% to see how the platform stack is utilized<00:10:16.690> now<00:10:17.690> say<00:10:17.840> users<00:10:18.830> come<00:10:19.160> in<00:10:19.310> to<00:10:19.490> this 00:10:19.600 --> 00:10:19.610 align:start position:0% utilized now say users come in to this 00:10:19.610 --> 00:10:21.490 align:start position:0% utilized now say users come in to this platform<00:10:19.850> desktop<00:10:20.540> or<00:10:20.660> mobile<00:10:20.690> UI<00:10:21.050> and<00:10:21.410> they 00:10:21.490 --> 00:10:21.500 align:start position:0% platform desktop or mobile UI and they 00:10:21.500 --> 00:10:23.910 align:start position:0% platform desktop or mobile UI and they want<00:10:21.680> to<00:10:21.740> sign<00:10:21.980> a<00:10:22.220> Dowell<00:10:22.460> smart<00:10:23.090> contract 00:10:23.910 --> 00:10:23.920 align:start position:0% want to sign a Dowell smart contract 00:10:23.920 --> 00:10:27.010 align:start position:0% want to sign a Dowell smart contract well<00:10:24.920> they<00:10:25.220> drag<00:10:25.550> and<00:10:25.760> drop<00:10:25.910> UI<00:10:26.240> elements<00:10:26.750> onto 00:10:27.010 --> 00:10:27.020 align:start position:0% well they drag and drop UI elements onto 00:10:27.020 --> 00:10:27.490 align:start position:0% well they drag and drop UI elements onto a<00:10:27.050> camp 00:10:27.490 --> 00:10:27.500 align:start position:0% a camp 00:10:27.500 --> 00:10:30.340 align:start position:0% a camp let's<00:10:28.160> say<00:10:28.340> the<00:10:28.790> first<00:10:28.820> one<00:10:29.180> they<00:10:29.300> drag<00:10:29.570> pick 00:10:30.340 --> 00:10:30.350 align:start position:0% let's say the first one they drag pick 00:10:30.350 --> 00:10:33.940 align:start position:0% let's say the first one they drag pick select<00:10:31.100> is<00:10:31.280> a<00:10:32.150> UI<00:10:32.720> element<00:10:32.840> representing<00:10:33.710> the 00:10:33.940 --> 00:10:33.950 align:start position:0% select is a UI element representing the 00:10:33.950 --> 00:10:36.220 align:start position:0% select is a UI element representing the Board<00:10:34.190> of<00:10:34.400> the<00:10:34.490> Dow<00:10:34.730> now<00:10:35.510> after<00:10:35.780> they<00:10:35.930> drag<00:10:36.110> it 00:10:36.220 --> 00:10:36.230 align:start position:0% Board of the Dow now after they drag it 00:10:36.230 --> 00:10:37.720 align:start position:0% Board of the Dow now after they drag it onto<00:10:36.350> the<00:10:36.470> canvas<00:10:36.620> they<00:10:37.370> should<00:10:37.520> be<00:10:37.580> able<00:10:37.640> to 00:10:37.720 --> 00:10:37.730 align:start position:0% onto the canvas they should be able to 00:10:37.730 --> 00:10:40.170 align:start position:0% onto the canvas they should be able to click<00:10:37.940> on<00:10:38.090> the<00:10:38.180> element<00:10:38.540> and<00:10:38.720> then<00:10:39.350> configure 00:10:40.170 --> 00:10:40.180 align:start position:0% click on the element and then configure 00:10:40.180 --> 00:10:42.430 align:start position:0% click on the element and then configure what<00:10:41.180> should<00:10:41.300> they<00:10:41.360> could<00:10:41.510> figure<00:10:41.660> well<00:10:42.050> let's 00:10:42.430 --> 00:10:42.440 align:start position:0% what should they could figure well let's 00:10:42.440 --> 00:10:43.990 align:start position:0% what should they could figure well let's for<00:10:42.590> example<00:10:42.620> say<00:10:43.160> how<00:10:43.520> many<00:10:43.580> board<00:10:43.910> members 00:10:43.990 --> 00:10:44.000 align:start position:0% for example say how many board members 00:10:44.000 --> 00:10:46.180 align:start position:0% for example say how many board members total<00:10:44.480> there<00:10:44.600> are<00:10:44.750> or<00:10:44.990> what<00:10:45.620> decisions 00:10:46.180 --> 00:10:46.190 align:start position:0% total there are or what decisions 00:10:46.190 --> 00:10:49.540 align:start position:0% total there are or what decisions require<00:10:46.580> majority<00:10:47.150> are<00:10:47.330> unanimous<00:10:48.200> votes<00:10:48.550> how 00:10:49.540 --> 00:10:49.550 align:start position:0% require majority are unanimous votes how 00:10:49.550 --> 00:10:51.760 align:start position:0% require majority are unanimous votes how our<00:10:49.700> board<00:10:49.910> members<00:10:50.240> added<00:10:50.960> removed<00:10:51.350> or 00:10:51.760 --> 00:10:51.770 align:start position:0% our board members added removed or 00:10:51.770 --> 00:10:55.150 align:start position:0% our board members added removed or replaced<00:10:52.960> now<00:10:53.960> after<00:10:54.230> completing<00:10:54.350> the<00:10:54.830> design 00:10:55.150 --> 00:10:55.160 align:start position:0% replaced now after completing the design 00:10:55.160 --> 00:10:57.190 align:start position:0% replaced now after completing the design of<00:10:55.490> the<00:10:55.790> Dow<00:10:55.940> these<00:10:56.720> are<00:10:56.870> will<00:10:56.990> know 00:10:57.190 --> 00:10:57.200 align:start position:0% of the Dow these are will know 00:10:57.200 --> 00:10:59.140 align:start position:0% of the Dow these are will know immediately<00:10:57.530> if<00:10:57.830> their<00:10:58.190> design<00:10:58.490> contains<00:10:58.880> any 00:10:59.140 --> 00:10:59.150 align:start position:0% immediately if their design contains any 00:10:59.150 --> 00:11:02.260 align:start position:0% immediately if their design contains any errors<00:10:59.600> once<00:11:00.500> error-free<00:11:00.770> the<00:11:01.580> user<00:11:01.760> ability' 00:11:02.260 --> 00:11:02.270 align:start position:0% errors once error-free the user ability' 00:11:02.270 --> 00:11:04.060 align:start position:0% errors once error-free the user ability' deploy<00:11:02.570> the<00:11:02.960> dow<00:11:03.110> smart<00:11:03.440> contract<00:11:03.860> to<00:11:03.980> the 00:11:04.060 --> 00:11:04.070 align:start position:0% deploy the dow smart contract to the 00:11:04.070 --> 00:11:07.270 align:start position:0% deploy the dow smart contract to the test<00:11:04.310> net<00:11:04.490> or<00:11:04.700> directly<00:11:05.360> to<00:11:05.510> the<00:11:05.630> main<00:11:05.780> net<00:11:06.280> the 00:11:07.270 --> 00:11:07.280 align:start position:0% test net or directly to the main net the 00:11:07.280 --> 00:11:09.250 align:start position:0% test net or directly to the main net the steps<00:11:07.550> involved<00:11:08.120> here<00:11:08.330> can<00:11:08.570> be<00:11:08.660> contained<00:11:09.170> in 00:11:09.250 --> 00:11:09.260 align:start position:0% steps involved here can be contained in 00:11:09.260 --> 00:11:11.590 align:start position:0% steps involved here can be contained in the<00:11:09.350> user's<00:11:09.680> browser<00:11:09.890> are<00:11:10.550> taken<00:11:10.940> to<00:11:11.510> the 00:11:11.590 --> 00:11:11.600 align:start position:0% the user's browser are taken to the 00:11:11.600 --> 00:11:13.210 align:start position:0% the user's browser are taken to the middle<00:11:11.810> layer<00:11:11.960> of<00:11:12.200> the<00:11:12.260> platform<00:11:12.710> depending 00:11:13.210 --> 00:11:13.220 align:start position:0% middle layer of the platform depending 00:11:13.220 --> 00:11:14.440 align:start position:0% middle layer of the platform depending if<00:11:13.310> the<00:11:13.400> users<00:11:13.640> utilizing<00:11:14.180> their<00:11:14.300> own 00:11:14.440 --> 00:11:14.450 align:start position:0% if the users utilizing their own 00:11:14.450 --> 00:11:17.500 align:start position:0% if the users utilizing their own third-party<00:11:15.080> wallet<00:11:15.380> which<00:11:16.010> is<00:11:16.250> preferred<00:11:16.730> or 00:11:17.500 --> 00:11:17.510 align:start position:0% third-party wallet which is preferred or 00:11:17.510 --> 00:11:19.870 align:start position:0% third-party wallet which is preferred or if<00:11:17.960> they're<00:11:18.110> using<00:11:18.380> like<00:11:18.530> utilizing<00:11:19.310> the 00:11:19.870 --> 00:11:19.880 align:start position:0% if they're using like utilizing the 00:11:19.880 --> 00:11:24.730 align:start position:0% if they're using like utilizing the platform's<00:11:20.360> wallet<00:11:20.660> management<00:11:21.110> system<00:11:23.740> okay 00:11:24.730 --> 00:11:24.740 align:start position:0% platform's wallet management system okay 00:11:24.740 --> 00:11:27.190 align:start position:0% platform's wallet management system okay let's<00:11:25.550> move<00:11:25.670> on<00:11:25.790> to<00:11:26.000> a<00:11:26.090> dev<00:11:26.480> user<00:11:26.750> story<00:11:27.020> a 00:11:27.190 --> 00:11:27.200 align:start position:0% let's move on to a dev user story a 00:11:27.200 --> 00:11:29.790 align:start position:0% let's move on to a dev user story a developer<00:11:28.070> comes<00:11:28.310> up<00:11:29.000> with<00:11:29.150> the<00:11:29.240> most<00:11:29.270> amazing 00:11:29.790 --> 00:11:29.800 align:start position:0% developer comes up with the most amazing 00:11:29.800 --> 00:11:32.260 align:start position:0% developer comes up with the most amazing ICL<00:11:30.800> smart<00:11:31.040> contract<00:11:31.490> and<00:11:31.880> once<00:11:32.060> the 00:11:32.260 --> 00:11:32.270 align:start position:0% ICL smart contract and once the 00:11:32.270 --> 00:11:33.690 align:start position:0% ICL smart contract and once the community<00:11:32.570> to<00:11:32.930> utilize<00:11:33.170> their<00:11:33.350> design 00:11:33.690 --> 00:11:33.700 align:start position:0% community to utilize their design 00:11:33.700 --> 00:11:35.890 align:start position:0% community to utilize their design they've<00:11:34.700> come<00:11:34.940> to<00:11:35.150> the<00:11:35.240> platform's<00:11:35.570> interface 00:11:35.890 --> 00:11:35.900 align:start position:0% they've come to the platform's interface 00:11:35.900 --> 00:11:37.810 align:start position:0% they've come to the platform's interface upload<00:11:36.470> the<00:11:36.560> source<00:11:36.740> code<00:11:36.950> and<00:11:37.160> vie<00:11:37.550> for<00:11:37.610> our 00:11:37.810 --> 00:11:37.820 align:start position:0% upload the source code and vie for our 00:11:37.820 --> 00:11:39.640 align:start position:0% upload the source code and vie for our solidity<00:11:38.180> the<00:11:38.840> platform<00:11:39.230> would<00:11:39.350> then<00:11:39.500> check 00:11:39.640 --> 00:11:39.650 align:start position:0% solidity the platform would then check 00:11:39.650 --> 00:11:41.650 align:start position:0% solidity the platform would then check for<00:11:39.800> errors<00:11:39.980> compile<00:11:40.640> and<00:11:40.940> generate<00:11:41.240> the<00:11:41.360> API 00:11:41.650 --> 00:11:41.660 align:start position:0% for errors compile and generate the API 00:11:41.660 --> 00:11:43.750 align:start position:0% for errors compile and generate the API and<00:11:42.230> finally<00:11:42.500> parse<00:11:42.680> out<00:11:42.860> the<00:11:42.890> annotations<00:11:43.550> to 00:11:43.750 --> 00:11:43.760 align:start position:0% and finally parse out the annotations to 00:11:43.760 --> 00:11:46.960 align:start position:0% and finally parse out the annotations to generate<00:11:44.030> the<00:11:44.120> UI<00:11:44.300> interface<00:11:45.910> now<00:11:46.910> the 00:11:46.960 --> 00:11:46.970 align:start position:0% generate the UI interface now the 00:11:46.970 --> 00:11:48.670 align:start position:0% generate the UI interface now the developer<00:11:47.390> can<00:11:47.570> publish<00:11:47.900> this<00:11:48.140> configurable 00:11:48.670 --> 00:11:48.680 align:start position:0% developer can publish this configurable 00:11:48.680 --> 00:11:51.220 align:start position:0% developer can publish this configurable smart<00:11:48.950> contract<00:11:49.400> now<00:11:49.610> to<00:11:50.510> the<00:11:50.600> public<00:11:50.750> along 00:11:51.220 --> 00:11:51.230 align:start position:0% smart contract now to the public along 00:11:51.230 --> 00:11:52.660 align:start position:0% smart contract now to the public along someone<00:11:51.530> like<00:11:51.650> a<00:11:51.710> chat<00:11:51.980> to<00:11:52.190> launch<00:11:52.370> his<00:11:52.580> own 00:11:52.660 --> 00:11:52.670 align:start position:0% someone like a chat to launch his own 00:11:52.670 --> 00:11:54.550 align:start position:0% someone like a chat to launch his own token<00:11:53.300> with<00:11:53.570> minimal<00:11:53.960> effort<00:11:54.080> and<00:11:54.440> no 00:11:54.550 --> 00:11:54.560 align:start position:0% token with minimal effort and no 00:11:54.560 --> 00:12:07.900 align:start position:0% token with minimal effort and no coding<00:12:01.510> this<00:12:02.510> is<00:12:02.660> an<00:12:02.750> intro<00:12:06.040> alright<00:12:07.040> so 00:12:07.900 --> 00:12:07.910 align:start position:0% coding this is an intro alright so 00:12:07.910 --> 00:12:09.580 align:start position:0% coding this is an intro alright so closing<00:12:08.240> thoughts<00:12:08.420> here<00:12:08.630> that<00:12:08.780> here's<00:12:09.500> a 00:12:09.580 --> 00:12:09.590 align:start position:0% closing thoughts here that here's a 00:12:09.590 --> 00:12:11.230 align:start position:0% closing thoughts here that here's a great<00:12:09.860> visualization<00:12:10.760> of<00:12:10.940> what<00:12:11.120> this 00:12:11.230 --> 00:12:11.240 align:start position:0% great visualization of what this 00:12:11.240 --> 00:12:12.880 align:start position:0% great visualization of what this platform<00:12:11.480> is<00:12:11.780> striving<00:12:12.170> to<00:12:12.290> achieve<00:12:12.410> at<00:12:12.860> a 00:12:12.880 --> 00:12:12.890 align:start position:0% platform is striving to achieve at a 00:12:12.890 --> 00:12:15.520 align:start position:0% platform is striving to achieve at a high<00:12:13.070> level<00:12:13.100> we<00:12:14.060> want<00:12:14.270> mass<00:12:14.630> adoption<00:12:15.020> of<00:12:15.440> a 00:12:15.520 --> 00:12:15.530 align:start position:0% high level we want mass adoption of a 00:12:15.530 --> 00:12:17.140 align:start position:0% high level we want mass adoption of a thin<00:12:15.680> idioms<00:12:15.890> smart<00:12:16.339> contract<00:12:16.700> technology 00:12:17.140 --> 00:12:17.150 align:start position:0% thin idioms smart contract technology 00:12:17.150 --> 00:12:18.850 align:start position:0% thin idioms smart contract technology right<00:12:17.360> this<00:12:18.350> is<00:12:18.440> possible<00:12:18.740> through 00:12:18.850 --> 00:12:18.860 align:start position:0% right this is possible through 00:12:18.860 --> 00:12:20.770 align:start position:0% right this is possible through abstracting<00:12:19.460> smart<00:12:19.760> contract<00:12:20.120> development 00:12:20.770 --> 00:12:20.780 align:start position:0% abstracting smart contract development 00:12:20.780 --> 00:12:22.720 align:start position:0% abstracting smart contract development away<00:12:21.170> from<00:12:21.410> non<00:12:21.589> smart<00:12:21.980> contract<00:12:22.370> developers 00:12:22.720 --> 00:12:22.730 align:start position:0% away from non smart contract developers 00:12:22.730 --> 00:12:25.030 align:start position:0% away from non smart contract developers and<00:12:22.940> non<00:12:23.180> developers<00:12:23.630> among<00:12:23.990> the<00:12:24.500> use<00:12:24.680> of<00:12:24.890> the 00:12:25.030 --> 00:12:25.040 align:start position:0% and non developers among the use of the 00:12:25.040 --> 00:12:27.730 align:start position:0% and non developers among the use of the platform<00:12:25.660> users<00:12:26.660> enter<00:12:27.470> the<00:12:27.560> platform 00:12:27.730 --> 00:12:27.740 align:start position:0% platform users enter the platform 00:12:27.740 --> 00:12:29.950 align:start position:0% platform users enter the platform through<00:12:28.250> the<00:12:28.310> UI<00:12:28.490> and<00:12:28.700> API<00:12:29.060> layers<00:12:29.390> this 00:12:29.950 --> 00:12:29.960 align:start position:0% through the UI and API layers this 00:12:29.960 --> 00:12:34.810 align:start position:0% through the UI and API layers this allows<00:12:30.260> for<00:12:30.290> a<00:12:30.770> sec<00:12:31.510> CSC<00:12:32.510> and<00:12:32.560> CST<00:12:33.560> T's<00:12:34.250> to<00:12:34.730> be 00:12:34.810 --> 00:12:34.820 align:start position:0% allows for a sec CSC and CST T's to be 00:12:34.820 --> 00:12:39.070 align:start position:0% allows for a sec CSC and CST T's to be consumed<00:12:37.060> now<00:12:38.060> smart<00:12:38.330> contract<00:12:38.720> developers 00:12:39.070 --> 00:12:39.080 align:start position:0% consumed now smart contract developers 00:12:39.080 --> 00:12:40.240 align:start position:0% consumed now smart contract developers will<00:12:39.320> also<00:12:39.620> enter<00:12:39.950> in<00:12:40.070> through<00:12:40.130> the 00:12:40.240 --> 00:12:40.250 align:start position:0% will also enter in through the 00:12:40.250 --> 00:12:41.220 align:start position:0% will also enter in through the platform's<00:12:40.730> you 00:12:41.220 --> 00:12:41.230 align:start position:0% platform's you 00:12:41.230 --> 00:12:43.780 align:start position:0% platform's you although<00:12:42.230> smart<00:12:42.829> contracts<00:12:43.189> source<00:12:43.339> code<00:12:43.550> as 00:12:43.780 --> 00:12:43.790 align:start position:0% although smart contracts source code as 00:12:43.790 --> 00:12:45.910 align:start position:0% although smart contracts source code as stated<00:12:44.119> before<00:12:44.410> have<00:12:45.410> you<00:12:45.589> i<00:12:45.619> aughtta 00:12:45.910 --> 00:12:45.920 align:start position:0% stated before have you i aughtta 00:12:45.920 --> 00:12:49.720 align:start position:0% stated before have you i aughtta generated<00:12:46.519> through<00:12:46.879> the<00:12:46.999> use<00:12:47.149> of<00:12:48.519> parsing<00:12:49.519> the 00:12:49.720 --> 00:12:49.730 align:start position:0% generated through the use of parsing the 00:12:49.730 --> 00:12:52.449 align:start position:0% generated through the use of parsing the ABI<00:12:50.029> and<00:12:50.449> also<00:12:50.869> through<00:12:51.259> new<00:12:51.920> development 00:12:52.449 --> 00:12:52.459 align:start position:0% ABI and also through new development 00:12:52.459 --> 00:12:54.569 align:start position:0% ABI and also through new development methods<00:12:52.819> and<00:12:53.179> ideologies<00:12:53.689> we<00:12:53.869> will<00:12:53.990> introduce 00:12:54.569 --> 00:12:54.579 align:start position:0% methods and ideologies we will introduce 00:12:54.579 --> 00:12:58.210 align:start position:0% methods and ideologies we will introduce the<00:12:55.579> through<00:12:55.970> the<00:12:56.059> platform<00:12:57.189> such<00:12:58.189> as 00:12:58.210 --> 00:12:58.220 align:start position:0% the through the platform such as 00:12:58.220 --> 00:13:00.280 align:start position:0% the through the platform such as annotations<00:12:58.910> that<00:12:59.029> allow<00:12:59.749> audible 00:13:00.280 --> 00:13:00.290 align:start position:0% annotations that allow audible 00:13:00.290 --> 00:13:02.439 align:start position:0% annotations that allow audible generation<00:13:00.709> of<00:13:00.800> the<00:13:00.860> UI<00:13:00.980> for<00:13:01.759> interaction<00:13:02.269> and 00:13:02.439 --> 00:13:02.449 align:start position:0% generation of the UI for interaction and 00:13:02.449 --> 00:13:04.960 align:start position:0% generation of the UI for interaction and if<00:13:02.540> they<00:13:02.749> desire<00:13:03.139> to<00:13:03.339> they<00:13:04.339> can<00:13:04.490> publish<00:13:04.819> this 00:13:04.960 --> 00:13:04.970 align:start position:0% if they desire to they can publish this 00:13:04.970 --> 00:13:07.809 align:start position:0% if they desire to they can publish this source<00:13:05.929> code<00:13:06.170> to<00:13:06.439> the<00:13:06.980> platform's<00:13:07.369> library 00:13:07.809 --> 00:13:07.819 align:start position:0% source code to the platform's library 00:13:07.819 --> 00:13:11.079 align:start position:0% source code to the platform's library and<00:13:08.089> now<00:13:08.779> that<00:13:09.369> smart<00:13:10.369> contract<00:13:10.759> is<00:13:10.910> now<00:13:11.059> a 00:13:11.079 --> 00:13:11.089 align:start position:0% and now that smart contract is now a 00:13:11.089 --> 00:13:13.150 align:start position:0% and now that smart contract is now a configural<00:13:11.509> smart<00:13:11.720> contract<00:13:12.170> our<00:13:12.800> smart 00:13:13.150 --> 00:13:13.160 align:start position:0% configural smart contract our smart 00:13:13.160 --> 00:13:16.540 align:start position:0% configural smart contract our smart contract<00:13:13.490> template<00:13:13.850> that<00:13:14.980> your<00:13:15.980> average<00:13:16.160> user 00:13:16.540 --> 00:13:16.550 align:start position:0% contract template that your average user 00:13:16.550 --> 00:13:22.049 align:start position:0% contract template that your average user can't<00:13:16.910> consume<00:13:18.040> now<00:13:19.360> we<00:13:20.360> talked<00:13:20.540> about<00:13:20.600> how 00:13:22.049 --> 00:13:22.059 align:start position:0% can't consume now we talked about how 00:13:22.059 --> 00:13:24.819 align:start position:0% can't consume now we talked about how the<00:13:23.059> platform<00:13:23.449> is<00:13:23.509> going<00:13:23.600> to<00:13:23.660> do<00:13:23.809> it<00:13:23.959> now<00:13:24.559> there 00:13:24.819 --> 00:13:24.829 align:start position:0% the platform is going to do it now there 00:13:24.829 --> 00:13:26.169 align:start position:0% the platform is going to do it now there are<00:13:24.949> some<00:13:25.129> responsibilities<00:13:25.939> that<00:13:26.089> this 00:13:26.169 --> 00:13:26.179 align:start position:0% are some responsibilities that this 00:13:26.179 --> 00:13:29.590 align:start position:0% are some responsibilities that this platform<00:13:26.420> should<00:13:26.899> take<00:13:27.139> in<00:13:28.480> encouraging<00:13:29.480> mass 00:13:29.590 --> 00:13:29.600 align:start position:0% platform should take in encouraging mass 00:13:29.600 --> 00:13:33.220 align:start position:0% platform should take in encouraging mass adoption<00:13:30.399> one<00:13:31.399> is<00:13:31.519> education<00:13:31.869> we<00:13:32.869> want<00:13:33.019> to 00:13:33.220 --> 00:13:33.230 align:start position:0% adoption one is education we want to 00:13:33.230 --> 00:13:34.869 align:start position:0% adoption one is education we want to promote<00:13:33.529> user<00:13:33.800> growth<00:13:34.100> so<00:13:34.579> we<00:13:34.610> need<00:13:34.819> to 00:13:34.869 --> 00:13:34.879 align:start position:0% promote user growth so we need to 00:13:34.879 --> 00:13:36.460 align:start position:0% promote user growth so we need to educate<00:13:34.970> new<00:13:35.300> users<00:13:35.749> on<00:13:35.959> what<00:13:36.170> a<00:13:36.199> blockchain 00:13:36.460 --> 00:13:36.470 align:start position:0% educate new users on what a blockchain 00:13:36.470 --> 00:13:39.730 align:start position:0% educate new users on what a blockchain is<00:13:36.889> what<00:13:37.670> restless<00:13:38.029> agreements<00:13:38.720> are<00:13:38.869> and<00:13:39.290> how 00:13:39.730 --> 00:13:39.740 align:start position:0% is what restless agreements are and how 00:13:39.740 --> 00:13:41.859 align:start position:0% is what restless agreements are and how programmable<00:13:40.429> currency<00:13:41.149> can<00:13:41.389> improve<00:13:41.689> their 00:13:41.859 --> 00:13:41.869 align:start position:0% programmable currency can improve their 00:13:41.869 --> 00:13:44.919 align:start position:0% programmable currency can improve their lives<00:13:42.019> on<00:13:42.230> a<00:13:42.259> daily<00:13:42.470> basis<00:13:43.300> also<00:13:44.300> involved<00:13:44.809> is 00:13:44.919 --> 00:13:44.929 align:start position:0% lives on a daily basis also involved is 00:13:44.929 --> 00:13:46.989 align:start position:0% lives on a daily basis also involved is protection<00:13:45.290> we<00:13:46.069> need<00:13:46.189> to<00:13:46.339> prevent<00:13:46.639> and<00:13:46.910> stop 00:13:46.989 --> 00:13:46.999 align:start position:0% protection we need to prevent and stop 00:13:46.999 --> 00:13:49.119 align:start position:0% protection we need to prevent and stop attackers<00:13:47.689> and<00:13:47.929> scammers<00:13:48.499> as<00:13:48.799> much<00:13:48.980> as 00:13:49.119 --> 00:13:49.129 align:start position:0% attackers and scammers as much as 00:13:49.129 --> 00:13:51.340 align:start position:0% attackers and scammers as much as possible<00:13:49.309> especially<00:13:49.999> as<00:13:50.389> new<00:13:50.420> users<00:13:50.959> come<00:13:51.139> in 00:13:51.340 --> 00:13:51.350 align:start position:0% possible especially as new users come in 00:13:51.350 --> 00:13:55.210 align:start position:0% possible especially as new users come in they're<00:13:51.769> very<00:13:51.980> naive<00:13:53.110> y'all<00:13:54.110> sure<00:13:54.619> get<00:13:54.920> slack 00:13:55.210 --> 00:13:55.220 align:start position:0% they're very naive y'all sure get slack 00:13:55.220 --> 00:13:58.030 align:start position:0% they're very naive y'all sure get slack email<00:13:55.759> spam<00:13:56.149> all<00:13:56.629> that<00:13:56.839> but<00:13:57.139> you<00:13:57.679> know<00:13:57.769> check 00:13:58.030 --> 00:13:58.040 align:start position:0% email spam all that but you know check 00:13:58.040 --> 00:13:59.889 align:start position:0% email spam all that but you know check your<00:13:58.189> wallet<00:13:58.490> check<00:13:58.819> this<00:13:58.970> you<00:13:59.509> know<00:13:59.629> fake 00:13:59.889 --> 00:13:59.899 align:start position:0% your wallet check this you know fake 00:13:59.899 --> 00:14:02.109 align:start position:0% your wallet check this you know fake leak<00:14:00.139> to<00:14:00.439> mune<00:14:00.829> upload<00:14:01.519> your<00:14:01.610> private<00:14:01.939> key 00:14:02.109 --> 00:14:02.119 align:start position:0% leak to mune upload your private key 00:14:02.119 --> 00:14:04.480 align:start position:0% leak to mune upload your private key like<00:14:02.569> they're<00:14:02.929> gonna<00:14:03.110> fall<00:14:03.350> for<00:14:03.499> that<00:14:03.559> but<00:14:04.429> the 00:14:04.480 --> 00:14:04.490 align:start position:0% like they're gonna fall for that but the 00:14:04.490 --> 00:14:06.400 align:start position:0% like they're gonna fall for that but the average<00:14:04.639> user<00:14:04.939> will<00:14:05.269> because<00:14:05.660> these<00:14:05.809> emails 00:14:06.400 --> 00:14:06.410 align:start position:0% average user will because these emails 00:14:06.410 --> 00:14:08.169 align:start position:0% average user will because these emails are<00:14:06.649> more<00:14:07.009> and<00:14:07.129> more<00:14:07.249> on<00:14:07.399> a<00:14:07.459> daily<00:14:07.790> basis 00:14:08.169 --> 00:14:08.179 align:start position:0% are more and more on a daily basis 00:14:08.179 --> 00:14:13.389 align:start position:0% are more and more on a daily basis getting<00:14:08.929> more<00:14:09.999> official-looking<00:14:11.740> one<00:14:12.740> way<00:14:12.889> to 00:14:13.389 --> 00:14:13.399 align:start position:0% getting more official-looking one way to 00:14:13.399 --> 00:14:16.269 align:start position:0% getting more official-looking one way to stop<00:14:13.910> this<00:14:14.179> is<00:14:14.449> to<00:14:14.509> blacklist<00:14:15.170> proven<00:14:16.069> bad 00:14:16.269 --> 00:14:16.279 align:start position:0% stop this is to blacklist proven bad 00:14:16.279 --> 00:14:18.489 align:start position:0% stop this is to blacklist proven bad contract<00:14:16.879> addresses<00:14:17.480> or<00:14:17.689> wallet<00:14:18.110> addresses 00:14:18.489 --> 00:14:18.499 align:start position:0% contract addresses or wallet addresses 00:14:18.499 --> 00:14:20.619 align:start position:0% contract addresses or wallet addresses now<00:14:19.249> this<00:14:19.429> can<00:14:19.730> you<00:14:20.089> know<00:14:20.119> range<00:14:20.449> from 00:14:20.619 --> 00:14:20.629 align:start position:0% now this can you know range from 00:14:20.629 --> 00:14:22.539 align:start position:0% now this can you know range from different<00:14:21.019> levels<00:14:21.290> one<00:14:21.860> you<00:14:22.040> can<00:14:22.160> notify<00:14:22.429> the 00:14:22.539 --> 00:14:22.549 align:start position:0% different levels one you can notify the 00:14:22.549 --> 00:14:24.389 align:start position:0% different levels one you can notify the user<00:14:22.819> like<00:14:23.059> hey<00:14:23.209> you're<00:14:23.809> about<00:14:23.929> to<00:14:24.079> sin 00:14:24.389 --> 00:14:24.399 align:start position:0% user like hey you're about to sin 00:14:24.399 --> 00:14:28.660 align:start position:0% user like hey you're about to sin transactions<00:14:25.399> to<00:14:26.240> a<00:14:26.720> known<00:14:27.079> bad<00:14:27.490> wallet<00:14:28.490> our 00:14:28.660 --> 00:14:28.670 align:start position:0% transactions to a known bad wallet our 00:14:28.670 --> 00:14:32.079 align:start position:0% transactions to a known bad wallet our smart<00:14:28.970> contract<00:14:29.299> address<00:14:29.720> or<00:14:30.410> if<00:14:30.920> you<00:14:31.279> the 00:14:32.079 --> 00:14:32.089 align:start position:0% smart contract address or if you the 00:14:32.089 --> 00:14:33.910 align:start position:0% smart contract address or if you the user<00:14:32.329> chooses<00:14:32.600> to<00:14:32.869> through<00:14:33.589> the<00:14:33.709> platform 00:14:33.910 --> 00:14:33.920 align:start position:0% user chooses to through the platform 00:14:33.920 --> 00:14:35.859 align:start position:0% user chooses to through the platform they<00:14:34.279> should<00:14:34.429> be<00:14:34.519> allowed<00:14:34.790> full<00:14:35.299> protection 00:14:35.859 --> 00:14:35.869 align:start position:0% they should be allowed full protection 00:14:35.869 --> 00:14:37.900 align:start position:0% they should be allowed full protection and<00:14:36.049> then<00:14:36.379> the<00:14:36.499> platform<00:14:36.679> should<00:14:36.910> completely 00:14:37.900 --> 00:14:37.910 align:start position:0% and then the platform should completely 00:14:37.910 --> 00:14:39.309 align:start position:0% and then the platform should completely block<00:14:38.089> their<00:14:38.240> transaction<00:14:38.749> and<00:14:38.929> then<00:14:39.019> notify 00:14:39.309 --> 00:14:39.319 align:start position:0% block their transaction and then notify 00:14:39.319 --> 00:14:41.470 align:start position:0% block their transaction and then notify them<00:14:39.529> why<00:14:39.980> the<00:14:40.040> transaction<00:14:40.639> was<00:14:40.759> blocked<00:14:40.970> for 00:14:41.470 --> 00:14:41.480 align:start position:0% them why the transaction was blocked for 00:14:41.480 --> 00:14:46.269 align:start position:0% them why the transaction was blocked for further<00:14:41.779> protection<00:14:43.990> now<00:14:44.990> people<00:14:45.350> browse<00:14:45.679> the 00:14:46.269 --> 00:14:46.279 align:start position:0% further protection now people browse the 00:14:46.279 --> 00:14:48.460 align:start position:0% further protection now people browse the web<00:14:46.459> every<00:14:46.730> day<00:14:47.179> most<00:14:47.839> do<00:14:47.959> not<00:14:47.990> realize 00:14:48.460 --> 00:14:48.470 align:start position:0% web every day most do not realize 00:14:48.470 --> 00:14:50.619 align:start position:0% web every day most do not realize they're<00:14:48.740> indirectly<00:14:49.429> using<00:14:49.759> TCP<00:14:50.329> and<00:14:50.480> IP 00:14:50.619 --> 00:14:50.629 align:start position:0% they're indirectly using TCP and IP 00:14:50.629 --> 00:14:52.419 align:start position:0% they're indirectly using TCP and IP protocols<00:14:51.319> to<00:14:51.529> visit<00:14:51.769> their<00:14:51.889> favorite<00:14:52.040> sites 00:14:52.419 --> 00:14:52.429 align:start position:0% protocols to visit their favorite sites 00:14:52.429 --> 00:14:54.790 align:start position:0% protocols to visit their favorite sites and<00:14:52.730> five<00:14:53.419> years<00:14:53.629> or<00:14:53.749> so<00:14:53.929> this<00:14:54.499> plan 00:14:54.790 --> 00:14:54.800 align:start position:0% and five years or so this plan 00:14:54.800 --> 00:14:56.889 align:start position:0% and five years or so this plan form<00:14:55.010> should<00:14:55.430> achieve<00:14:55.519> the<00:14:55.820> same<00:14:56.029> result<00:14:56.420> the 00:14:56.889 --> 00:14:56.899 align:start position:0% form should achieve the same result the 00:14:56.899 --> 00:14:58.840 align:start position:0% form should achieve the same result the average<00:14:57.050> user<00:14:57.350> will<00:14:57.649> be<00:14:57.680> extracted<00:14:58.310> away<00:14:58.490> from 00:14:58.840 --> 00:14:58.850 align:start position:0% average user will be extracted away from 00:14:58.850 --> 00:15:00.880 align:start position:0% average user will be extracted away from the<00:14:59.029> protocol<00:14:59.480> and<00:15:00.019> essentially<00:15:00.529> never<00:15:00.680> knew 00:15:00.880 --> 00:15:00.890 align:start position:0% the protocol and essentially never knew 00:15:00.890 --> 00:15:04.840 align:start position:0% the protocol and essentially never knew they<00:15:01.250> were<00:15:01.310> interacting<00:15:01.940> with<00:15:02.180> the<00:15:02.269> EVM<00:15:03.850> thank 00:15:04.840 --> 00:15:04.850 align:start position:0% they were interacting with the EVM thank 00:15:04.850 --> 00:15:06.160 align:start position:0% they were interacting with the EVM thank you 00:15:06.160 --> 00:15:06.170 align:start position:0% you 00:15:06.170 --> 00:15:15.140 align:start position:0% you [Applause] 00:15:15.140 --> 00:15:15.150 align:start position:0% 00:15:15.150 --> 00:15:22.730 align:start position:0% [Music]