WEBVTT Kind: captions Language: en 00:00:09.190 --> 00:00:14.879 align:start position:0% [Music] 00:00:14.879 --> 00:00:14.889 align:start position:0% [Music] 00:00:14.889 --> 00:00:18.640 align:start position:0% [Music] hi<00:00:15.889> everybody<00:00:16.190> my<00:00:16.699> name<00:00:17.119> is<00:00:17.150> Piper<00:00:17.630> and<00:00:18.020> I've 00:00:18.640 --> 00:00:18.650 align:start position:0% hi everybody my name is Piper and I've 00:00:18.650 --> 00:00:21.070 align:start position:0% hi everybody my name is Piper and I've been<00:00:19.310> making<00:00:19.670> tooling<00:00:20.480> and<00:00:20.660> things<00:00:20.870> like<00:00:21.020> that 00:00:21.070 --> 00:00:21.080 align:start position:0% been making tooling and things like that 00:00:21.080 --> 00:00:23.860 align:start position:0% been making tooling and things like that in<00:00:21.440> the<00:00:21.560> Python<00:00:21.830> Python<00:00:22.480> ecosystem<00:00:23.480> since 00:00:23.860 --> 00:00:23.870 align:start position:0% in the Python Python ecosystem since 00:00:23.870 --> 00:00:26.140 align:start position:0% in the Python Python ecosystem since about<00:00:24.290> well<00:00:25.220> since<00:00:25.400> the<00:00:25.520> frontier<00:00:25.850> network 00:00:26.140 --> 00:00:26.150 align:start position:0% about well since the frontier network 00:00:26.150 --> 00:00:27.940 align:start position:0% about well since the frontier network launched<00:00:26.480> and<00:00:26.750> today<00:00:27.470> we're<00:00:27.650> gonna<00:00:27.710> do<00:00:27.920> a 00:00:27.940 --> 00:00:27.950 align:start position:0% launched and today we're gonna do a 00:00:27.950 --> 00:00:30.280 align:start position:0% launched and today we're gonna do a really<00:00:28.640> fast<00:00:28.910> run<00:00:29.240> through<00:00:29.480> of<00:00:29.660> the<00:00:29.870> entire 00:00:30.280 --> 00:00:30.290 align:start position:0% really fast run through of the entire 00:00:30.290 --> 00:00:32.650 align:start position:0% really fast run through of the entire Python<00:00:30.830> toolset<00:00:31.280> that<00:00:31.700> that<00:00:32.390> I've<00:00:32.480> been 00:00:32.650 --> 00:00:32.660 align:start position:0% Python toolset that that I've been 00:00:32.660 --> 00:00:35.710 align:start position:0% Python toolset that that I've been working<00:00:32.840> on<00:00:33.100> and<00:00:34.100> talked<00:00:34.430> sort<00:00:34.670> of<00:00:34.730> about<00:00:34.970> the 00:00:35.710 --> 00:00:35.720 align:start position:0% working on and talked sort of about the 00:00:35.720 --> 00:00:37.090 align:start position:0% working on and talked sort of about the road<00:00:35.930> map<00:00:36.110> there<00:00:36.350> and<00:00:36.620> then<00:00:36.710> at<00:00:36.800> the<00:00:36.890> end<00:00:36.920> I'm 00:00:37.090 --> 00:00:37.100 align:start position:0% road map there and then at the end I'm 00:00:37.100 --> 00:00:38.680 align:start position:0% road map there and then at the end I'm gonna<00:00:37.190> talk<00:00:37.430> to<00:00:37.460> you<00:00:37.579> about<00:00:37.670> PI<00:00:37.940> EVM<00:00:38.360> which<00:00:38.570> is 00:00:38.680 --> 00:00:38.690 align:start position:0% gonna talk to you about PI EVM which is 00:00:38.690 --> 00:00:40.270 align:start position:0% gonna talk to you about PI EVM which is the<00:00:38.870> project<00:00:39.260> I'm<00:00:39.380> most<00:00:39.560> excited<00:00:39.680> about<00:00:39.980> right 00:00:40.270 --> 00:00:40.280 align:start position:0% the project I'm most excited about right 00:00:40.280 --> 00:00:43.150 align:start position:0% the project I'm most excited about right now<00:00:40.510> cool<00:00:41.510> so<00:00:41.900> uh<00:00:41.930> python<00:00:42.560> etherium<00:00:42.980> let's 00:00:43.150 --> 00:00:43.160 align:start position:0% now cool so uh python etherium let's 00:00:43.160 --> 00:00:44.560 align:start position:0% now cool so uh python etherium let's first<00:00:43.340> let's<00:00:43.550> talk<00:00:43.640> about<00:00:43.760> why<00:00:43.970> python<00:00:44.390> python 00:00:44.560 --> 00:00:44.570 align:start position:0% first let's talk about why python python 00:00:44.570 --> 00:00:46.540 align:start position:0% first let's talk about why python python is<00:00:44.930> slow<00:00:45.560> people<00:00:45.860> have<00:00:46.040> complaints<00:00:46.460> about 00:00:46.540 --> 00:00:46.550 align:start position:0% is slow people have complaints about 00:00:46.550 --> 00:00:48.760 align:start position:0% is slow people have complaints about python<00:00:47.030> there's<00:00:47.329> the<00:00:47.540> global<00:00:48.230> interpreter<00:00:48.590> to 00:00:48.760 --> 00:00:48.770 align:start position:0% python there's the global interpreter to 00:00:48.770 --> 00:00:51.010 align:start position:0% python there's the global interpreter to lock<00:00:48.920> things<00:00:49.130> like<00:00:49.340> that<00:00:49.520> but<00:00:50.480> the<00:00:50.600> big<00:00:50.780> thing 00:00:51.010 --> 00:00:51.020 align:start position:0% lock things like that but the big thing 00:00:51.020 --> 00:00:53.560 align:start position:0% lock things like that but the big thing here<00:00:51.200> is<00:00:51.410> that<00:00:51.680> diversity<00:00:51.860> matters<00:00:52.570> ëthere 00:00:53.560 --> 00:00:53.570 align:start position:0% here is that diversity matters ëthere 00:00:53.570 --> 00:00:55.600 align:start position:0% here is that diversity matters ëthere IAM<00:00:53.750> is<00:00:53.870> not<00:00:54.020> a<00:00:54.050> language<00:00:54.500> specific<00:00:54.980> tool<00:00:55.220> and 00:00:55.600 --> 00:00:55.610 align:start position:0% IAM is not a language specific tool and 00:00:55.610 --> 00:00:57.700 align:start position:0% IAM is not a language specific tool and if<00:00:55.760> developers<00:00:56.059> can<00:00:56.660> pickup<00:00:56.989> tooling<00:00:57.559> and 00:00:57.700 --> 00:00:57.710 align:start position:0% if developers can pickup tooling and 00:00:57.710 --> 00:00:59.950 align:start position:0% if developers can pickup tooling and languages<00:00:58.130> that<00:00:58.220> the<00:00:58.370> languages<00:00:59.180> that<00:00:59.420> they 00:00:59.950 --> 00:00:59.960 align:start position:0% languages that the languages that they 00:00:59.960 --> 00:01:02.020 align:start position:0% languages that the languages that they are<00:01:00.050> familiar<00:01:00.260> with<00:01:00.770> then<00:01:01.250> it<00:01:01.460> will<00:01:01.640> speed<00:01:01.910> up 00:01:02.020 --> 00:01:02.030 align:start position:0% are familiar with then it will speed up 00:01:02.030 --> 00:01:03.880 align:start position:0% are familiar with then it will speed up adoption<00:01:02.540> and<00:01:02.690> that's<00:01:02.840> a<00:01:02.960> big<00:01:03.110> deal<00:01:03.260> so<00:01:03.800> we 00:01:03.880 --> 00:01:03.890 align:start position:0% adoption and that's a big deal so we 00:01:03.890 --> 00:01:06.630 align:start position:0% adoption and that's a big deal so we need<00:01:04.009> more<00:01:04.339> tooling<00:01:04.969> in<00:01:05.149> more<00:01:05.449> languages<00:01:05.840> and 00:01:06.630 --> 00:01:06.640 align:start position:0% need more tooling in more languages and 00:01:06.640 --> 00:01:09.789 align:start position:0% need more tooling in more languages and python<00:01:07.640> is<00:01:07.729> a<00:01:07.790> big<00:01:07.940> deal<00:01:08.350> python<00:01:09.350> is<00:01:09.500> used<00:01:09.680> for 00:01:09.789 --> 00:01:09.799 align:start position:0% python is a big deal python is used for 00:01:09.799 --> 00:01:11.560 align:start position:0% python is a big deal python is used for all<00:01:09.979> kinds<00:01:10.370> of<00:01:10.430> stuff<00:01:10.670> it<00:01:10.909> is<00:01:11.030> an<00:01:11.180> extremely 00:01:11.560 --> 00:01:11.570 align:start position:0% all kinds of stuff it is an extremely 00:01:11.570 --> 00:01:14.020 align:start position:0% all kinds of stuff it is an extremely accessible<00:01:12.140> language<00:01:12.520> it's<00:01:13.520> used<00:01:13.700> heavily<00:01:13.880> in 00:01:14.020 --> 00:01:14.030 align:start position:0% accessible language it's used heavily in 00:01:14.030 --> 00:01:16.060 align:start position:0% accessible language it's used heavily in data<00:01:14.240> science<00:01:14.450> and<00:01:14.930> web<00:01:15.229> development<00:01:15.650> and<00:01:15.920> all 00:01:16.060 --> 00:01:16.070 align:start position:0% data science and web development and all 00:01:16.070 --> 00:01:18.580 align:start position:0% data science and web development and all these<00:01:16.190> things<00:01:16.460> and<00:01:16.670> so<00:01:16.960> we<00:01:17.960> need<00:01:18.170> good<00:01:18.200> tools 00:01:18.580 --> 00:01:18.590 align:start position:0% these things and so we need good tools 00:01:18.590 --> 00:01:21.160 align:start position:0% these things and so we need good tools in<00:01:18.740> Python<00:01:19.070> because<00:01:19.510> lots<00:01:20.510> of<00:01:20.630> people<00:01:20.690> use<00:01:21.020> it 00:01:21.160 --> 00:01:21.170 align:start position:0% in Python because lots of people use it 00:01:21.170 --> 00:01:23.890 align:start position:0% in Python because lots of people use it and<00:01:21.590> this<00:01:22.130> is<00:01:22.220> my<00:01:22.369> favorite<00:01:22.700> Python<00:01:23.600> is<00:01:23.720> the 00:01:23.890 --> 00:01:23.900 align:start position:0% and this is my favorite Python is the 00:01:23.900 --> 00:01:27.149 align:start position:0% and this is my favorite Python is the second<00:01:24.320> best<00:01:24.710> language<00:01:25.190> for<00:01:25.520> everything<00:01:26.119> I 00:01:27.149 --> 00:01:27.159 align:start position:0% second best language for everything I 00:01:27.159 --> 00:01:29.530 align:start position:0% second best language for everything I this<00:01:28.159> rings<00:01:28.430> so<00:01:28.640> true<00:01:28.670> to<00:01:29.000> me 00:01:29.530 --> 00:01:29.540 align:start position:0% this rings so true to me 00:01:29.540 --> 00:01:31.330 align:start position:0% this rings so true to me pythons<00:01:30.020> got<00:01:30.229> its<00:01:30.380> works<00:01:30.619> and<00:01:30.799> its<00:01:30.920> problems 00:01:31.330 --> 00:01:31.340 align:start position:0% pythons got its works and its problems 00:01:31.340 --> 00:01:33.880 align:start position:0% pythons got its works and its problems but<00:01:31.580> it's<00:01:31.729> also<00:01:31.880> a<00:01:32.000> wonderful<00:01:32.420> language<00:01:32.890> also 00:01:33.880 --> 00:01:33.890 align:start position:0% but it's also a wonderful language also 00:01:33.890 --> 00:01:35.950 align:start position:0% but it's also a wonderful language also we<00:01:34.490> have<00:01:34.610> tons<00:01:34.790> of<00:01:34.909> cute<00:01:35.090> animal<00:01:35.390> pictures<00:01:35.720> in 00:01:35.950 --> 00:01:35.960 align:start position:0% we have tons of cute animal pictures in 00:01:35.960 --> 00:01:38.320 align:start position:0% we have tons of cute animal pictures in our<00:01:36.049> github<00:01:37.210> cool 00:01:38.320 --> 00:01:38.330 align:start position:0% our github cool 00:01:38.330 --> 00:01:40.300 align:start position:0% our github cool so<00:01:38.450> the<00:01:38.720> Python<00:01:39.020> III<00:01:39.350> I'm<00:01:39.439> told<00:01:39.590> chain<00:01:39.770> first 00:01:40.300 --> 00:01:40.310 align:start position:0% so the Python III I'm told chain first 00:01:40.310 --> 00:01:41.640 align:start position:0% so the Python III I'm told chain first we'll<00:01:40.430> start<00:01:40.490> with<00:01:40.640> web<00:01:40.880> 3py 00:01:41.640 --> 00:01:41.650 align:start position:0% we'll start with web 3py 00:01:41.650 --> 00:01:44.620 align:start position:0% we'll start with web 3py thank<00:01:42.650> you<00:01:42.770> web<00:01:42.920> 3j<00:01:43.340> s<00:01:43.490> team<00:01:43.790> we<00:01:44.150> literally 00:01:44.620 --> 00:01:44.630 align:start position:0% thank you web 3j s team we literally 00:01:44.630 --> 00:01:46.719 align:start position:0% thank you web 3j s team we literally copied<00:01:45.049> your<00:01:45.200> codebase<00:01:45.619> converted<00:01:46.549> it<00:01:46.640> to 00:01:46.719 --> 00:01:46.729 align:start position:0% copied your codebase converted it to 00:01:46.729 --> 00:01:48.969 align:start position:0% copied your codebase converted it to Python<00:01:47.119> and<00:01:47.420> then<00:01:47.600> took<00:01:47.720> it<00:01:47.840> from<00:01:47.960> there 00:01:48.969 --> 00:01:48.979 align:start position:0% Python and then took it from there 00:01:48.979 --> 00:01:52.630 align:start position:0% Python and then took it from there so<00:01:49.759> what<00:01:50.060> three<00:01:50.240> py<00:01:50.570> is<00:01:50.630> your<00:01:51.619> sort<00:01:52.040> of<00:01:52.130> way<00:01:52.580> to 00:01:52.630 --> 00:01:52.640 align:start position:0% so what three py is your sort of way to 00:01:52.640 --> 00:01:54.370 align:start position:0% so what three py is your sort of way to access<00:01:53.210> the<00:01:53.330> bought<00:01:53.479> chain<00:01:53.689> it<00:01:53.930> handles<00:01:54.259> all 00:01:54.370 --> 00:01:54.380 align:start position:0% access the bought chain it handles all 00:01:54.380 --> 00:01:56.410 align:start position:0% access the bought chain it handles all your<00:01:54.560> all<00:01:54.740> of<00:01:54.770> your<00:01:54.950> RPC<00:01:55.369> communications<00:01:56.210> when 00:01:56.410 --> 00:01:56.420 align:start position:0% your all of your RPC communications when 00:01:56.420 --> 00:01:58.090 align:start position:0% your all of your RPC communications when you<00:01:56.509> want<00:01:56.630> to<00:01:56.720> talk<00:01:56.840> to<00:01:56.990> a<00:01:57.020> node<00:01:57.290> it<00:01:57.619> does 00:01:58.090 --> 00:01:58.100 align:start position:0% you want to talk to a node it does 00:01:58.100 --> 00:01:59.620 align:start position:0% you want to talk to a node it does things<00:01:58.310> like<00:01:58.430> converting<00:01:58.939> the<00:01:59.030> responses<00:01:59.600> to 00:01:59.620 --> 00:01:59.630 align:start position:0% things like converting the responses to 00:01:59.630 --> 00:02:01.330 align:start position:0% things like converting the responses to Python<00:02:00.079> objects<00:02:00.590> so<00:02:00.770> that<00:02:00.799> they're<00:02:01.009> nice<00:02:01.130> and 00:02:01.330 --> 00:02:01.340 align:start position:0% Python objects so that they're nice and 00:02:01.340 --> 00:02:04.630 align:start position:0% Python objects so that they're nice and friendly<00:02:01.520> for<00:02:01.850> you<00:02:03.130> things<00:02:04.130> that<00:02:04.280> you<00:02:04.430> don't 00:02:04.630 --> 00:02:04.640 align:start position:0% friendly for you things that you don't 00:02:04.640 --> 00:02:05.980 align:start position:0% friendly for you things that you don't want<00:02:04.909> to<00:02:05.030> be<00:02:05.150> working<00:02:05.299> on<00:02:05.600> when<00:02:05.869> you're 00:02:05.980 --> 00:02:05.990 align:start position:0% want to be working on when you're 00:02:05.990 --> 00:02:08.020 align:start position:0% want to be working on when you're building<00:02:06.170> your<00:02:06.290> product<00:02:06.710> it<00:02:07.610> has<00:02:07.729> tons<00:02:07.939> of 00:02:08.020 --> 00:02:08.030 align:start position:0% building your product it has tons of 00:02:08.030 --> 00:02:09.790 align:start position:0% building your product it has tons of built-in<00:02:08.329> utilities<00:02:08.840> for<00:02:09.049> doing<00:02:09.259> conversions 00:02:09.790 --> 00:02:09.800 align:start position:0% built-in utilities for doing conversions 00:02:09.800 --> 00:02:11.650 align:start position:0% built-in utilities for doing conversions converting<00:02:10.399> things<00:02:10.610> to<00:02:10.759> hex<00:02:10.970> and<00:02:11.239> from<00:02:11.420> hex 00:02:11.650 --> 00:02:11.660 align:start position:0% converting things to hex and from hex 00:02:11.660 --> 00:02:14.200 align:start position:0% converting things to hex and from hex and<00:02:11.959> between<00:02:12.380> bytes<00:02:12.709> and<00:02:12.950> text<00:02:13.220> formats 00:02:14.200 --> 00:02:14.210 align:start position:0% and between bytes and text formats 00:02:14.210 --> 00:02:16.840 align:start position:0% and between bytes and text formats those<00:02:14.360> currency<00:02:14.840> conversions<00:02:15.550> again<00:02:16.550> things 00:02:16.840 --> 00:02:16.850 align:start position:0% those currency conversions again things 00:02:16.850 --> 00:02:18.310 align:start position:0% those currency conversions again things you<00:02:16.940> don't<00:02:17.030> want<00:02:17.210> to<00:02:17.240> be<00:02:17.360> implementing<00:02:17.900> you 00:02:18.310 --> 00:02:18.320 align:start position:0% you don't want to be implementing you 00:02:18.320 --> 00:02:20.800 align:start position:0% you don't want to be implementing you can<00:02:18.410> focus<00:02:18.620> on<00:02:18.740> your<00:02:18.890> product<00:02:19.690> we<00:02:20.690> have 00:02:20.800 --> 00:02:20.810 align:start position:0% can focus on your product we have 00:02:20.810 --> 00:02:23.110 align:start position:0% can focus on your product we have contract<00:02:21.460> abstractions<00:02:22.460> for<00:02:22.610> a<00:02:22.670> contract 00:02:23.110 --> 00:02:23.120 align:start position:0% contract abstractions for a contract 00:02:23.120 --> 00:02:25.420 align:start position:0% contract abstractions for a contract objects<00:02:23.600> that<00:02:23.780> give<00:02:23.990> you<00:02:24.230> really<00:02:25.130> convenient 00:02:25.420 --> 00:02:25.430 align:start position:0% objects that give you really convenient 00:02:25.430 --> 00:02:26.830 align:start position:0% objects that give you really convenient all<00:02:25.610> you<00:02:25.700> have<00:02:25.790> to<00:02:25.910> do<00:02:26.000> is<00:02:26.120> feed<00:02:26.330> us<00:02:26.420> your<00:02:26.570> ABI 00:02:26.830 --> 00:02:26.840 align:start position:0% all you have to do is feed us your ABI 00:02:26.840 --> 00:02:28.900 align:start position:0% all you have to do is feed us your ABI tell<00:02:27.350> us<00:02:27.440> what<00:02:27.590> address<00:02:27.950> you're<00:02:28.130> at<00:02:28.250> you<00:02:28.760> can 00:02:28.900 --> 00:02:28.910 align:start position:0% tell us what address you're at you can 00:02:28.910 --> 00:02:30.490 align:start position:0% tell us what address you're at you can interact<00:02:29.240> with<00:02:29.330> your<00:02:29.510> contract<00:02:30.020> this<00:02:30.290> does 00:02:30.490 --> 00:02:30.500 align:start position:0% interact with your contract this does 00:02:30.500 --> 00:02:33.400 align:start position:0% interact with your contract this does deployment<00:02:31.100> all<00:02:31.910> of<00:02:32.090> the<00:02:32.210> ABI<00:02:32.600> in<00:02:32.840> coatings<00:02:33.260> of 00:02:33.400 --> 00:02:33.410 align:start position:0% deployment all of the ABI in coatings of 00:02:33.410 --> 00:02:37.720 align:start position:0% deployment all of the ABI in coatings of arguments<00:02:33.950> and<00:02:34.130> things<00:02:34.310> like<00:02:34.490> that<00:02:36.730> that's 00:02:37.720 --> 00:02:37.730 align:start position:0% arguments and things like that that's 00:02:37.730 --> 00:02:39.460 align:start position:0% arguments and things like that that's again<00:02:38.420> things<00:02:38.840> you<00:02:38.990> don't<00:02:39.170> want<00:02:39.290> to<00:02:39.380> be 00:02:39.460 --> 00:02:39.470 align:start position:0% again things you don't want to be 00:02:39.470 --> 00:02:42.910 align:start position:0% again things you don't want to be building<00:02:40.540> we<00:02:41.540> also<00:02:41.690> have<00:02:42.140> an<00:02:42.290> Accounts<00:02:42.650> API 00:02:42.910 --> 00:02:42.920 align:start position:0% building we also have an Accounts API 00:02:42.920 --> 00:02:45.760 align:start position:0% building we also have an Accounts API this<00:02:43.040> is<00:02:43.490> currently<00:02:44.360> in<00:02:44.690> sort<00:02:45.230> of<00:02:45.260> a<00:02:45.410> alpha 00:02:45.760 --> 00:02:45.770 align:start position:0% this is currently in sort of a alpha 00:02:45.770 --> 00:02:47.830 align:start position:0% this is currently in sort of a alpha stage<00:02:46.130> if<00:02:46.910> you're<00:02:47.090> familiar<00:02:47.270> with<00:02:47.630> the<00:02:47.690> web 00:02:47.830 --> 00:02:47.840 align:start position:0% stage if you're familiar with the web 00:02:47.840 --> 00:02:51.460 align:start position:0% stage if you're familiar with the web PHAs<00:02:48.440> new<00:02:49.340> accounts<00:02:49.700> API<00:02:50.000> again<00:02:50.570> we<00:02:50.960> generally 00:02:51.460 --> 00:02:51.470 align:start position:0% PHAs new accounts API again we generally 00:02:51.470 --> 00:02:53.730 align:start position:0% PHAs new accounts API again we generally kind<00:02:51.620> of<00:02:51.740> copied<00:02:52.100> this<00:02:52.250> you<00:02:53.060> can<00:02:53.210> do 00:02:53.730 --> 00:02:53.740 align:start position:0% kind of copied this you can do 00:02:53.740 --> 00:02:56.260 align:start position:0% kind of copied this you can do generation<00:02:54.740> of<00:02:54.980> accounts<00:02:55.550> management<00:02:56.120> of 00:02:56.260 --> 00:02:56.270 align:start position:0% generation of accounts management of 00:02:56.270 --> 00:02:57.820 align:start position:0% generation of accounts management of private<00:02:56.630> keys<00:02:56.780> from<00:02:57.050> right<00:02:57.230> there<00:02:57.260> within 00:02:57.820 --> 00:02:57.830 align:start position:0% private keys from right there within 00:02:57.830 --> 00:03:01.030 align:start position:0% private keys from right there within your<00:02:58.130> Python<00:02:58.970> code<00:02:59.180> base<00:02:59.590> loading<00:03:00.590> key<00:03:00.770> files 00:03:01.030 --> 00:03:01.040 align:start position:0% your Python code base loading key files 00:03:01.040 --> 00:03:03.280 align:start position:0% your Python code base loading key files signing<00:03:01.910> messages<00:03:02.480> sending<00:03:03.020> signed 00:03:03.280 --> 00:03:03.290 align:start position:0% signing messages sending signed 00:03:03.290 --> 00:03:06.010 align:start position:0% signing messages sending signed transactions<00:03:03.980> things<00:03:04.220> like<00:03:04.370> that<00:03:04.690> and<00:03:05.690> we 00:03:06.010 --> 00:03:06.020 align:start position:0% transactions things like that and we 00:03:06.020 --> 00:03:07.690 align:start position:0% transactions things like that and we have<00:03:06.110> this<00:03:06.200> great<00:03:06.410> middleware<00:03:06.860> API<00:03:07.190> and<00:03:07.580> this 00:03:07.690 --> 00:03:07.700 align:start position:0% have this great middleware API and this 00:03:07.700 --> 00:03:11.440 align:start position:0% have this great middleware API and this is<00:03:07.850> a<00:03:07.990> much<00:03:08.990> lower<00:03:09.230> level<00:03:09.380> API<00:03:09.920> but<00:03:10.340> impact<00:03:10.820> it 00:03:11.440 --> 00:03:11.450 align:start position:0% is a much lower level API but impact it 00:03:11.450 --> 00:03:13.740 align:start position:0% is a much lower level API but impact it enables<00:03:12.080> a<00:03:12.170> lot<00:03:12.320> of<00:03:12.410> really<00:03:12.620> powerful<00:03:12.800> things 00:03:13.740 --> 00:03:13.750 align:start position:0% enables a lot of really powerful things 00:03:13.750 --> 00:03:16.960 align:start position:0% enables a lot of really powerful things caching<00:03:14.920> interception<00:03:15.920> of<00:03:16.130> requests<00:03:16.820> and 00:03:16.960 --> 00:03:16.970 align:start position:0% caching interception of requests and 00:03:16.970 --> 00:03:19.020 align:start position:0% caching interception of requests and signing<00:03:17.450> them<00:03:17.600> in<00:03:17.750> flight<00:03:18.050> things<00:03:18.530> like<00:03:18.710> that 00:03:19.020 --> 00:03:19.030 align:start position:0% signing them in flight things like that 00:03:19.030 --> 00:03:21.790 align:start position:0% signing them in flight things like that that<00:03:20.030> you<00:03:20.300> can<00:03:20.480> build<00:03:20.810> using<00:03:21.140> this<00:03:21.380> middleware 00:03:21.790 --> 00:03:21.800 align:start position:0% that you can build using this middleware 00:03:21.800 --> 00:03:24.670 align:start position:0% that you can build using this middleware API<00:03:22.690> all<00:03:23.690> right<00:03:23.810> let's<00:03:23.960> talk<00:03:24.020> about<00:03:24.140> populist 00:03:24.670 --> 00:03:24.680 align:start position:0% API all right let's talk about populist 00:03:24.680 --> 00:03:26.980 align:start position:0% API all right let's talk about populist populist<00:03:25.460> is<00:03:25.610> a<00:03:25.640> development<00:03:26.570> framework 00:03:26.980 --> 00:03:26.990 align:start position:0% populist is a development framework 00:03:26.990 --> 00:03:28.990 align:start position:0% populist is a development framework written<00:03:27.560> in<00:03:27.770> Python<00:03:28.160> and<00:03:28.400> it<00:03:28.730> should<00:03:28.880> be 00:03:28.990 --> 00:03:29.000 align:start position:0% written in Python and it should be 00:03:29.000 --> 00:03:30.460 align:start position:0% written in Python and it should be pretty<00:03:29.090> familiar<00:03:29.300> for<00:03:29.750> Python<00:03:30.020> developers 00:03:30.460 --> 00:03:30.470 align:start position:0% pretty familiar for Python developers 00:03:30.470 --> 00:03:32.710 align:start position:0% pretty familiar for Python developers they're<00:03:31.400> really<00:03:31.670> the<00:03:31.970> biggest<00:03:32.180> thing<00:03:32.360> that<00:03:32.600> it 00:03:32.710 --> 00:03:32.720 align:start position:0% they're really the biggest thing that it 00:03:32.720 --> 00:03:34.560 align:start position:0% they're really the biggest thing that it that<00:03:32.960> it<00:03:33.080> focuses<00:03:33.470> on<00:03:33.620> is<00:03:33.680> testing<00:03:34.220> but 00:03:34.560 --> 00:03:34.570 align:start position:0% that it focuses on is testing but 00:03:34.570 --> 00:03:36.250 align:start position:0% that it focuses on is testing but populist<00:03:35.570> will<00:03:35.720> handle<00:03:35.990> all<00:03:36.110> of<00:03:36.140> your 00:03:36.250 --> 00:03:36.260 align:start position:0% populist will handle all of your 00:03:36.260 --> 00:03:40.360 align:start position:0% populist will handle all of your compilation<00:03:36.890> and<00:03:36.980> deployment<00:03:37.310> for<00:03:37.700> you<00:03:39.370> which 00:03:40.360 --> 00:03:40.370 align:start position:0% compilation and deployment for you which 00:03:40.370 --> 00:03:42.460 align:start position:0% compilation and deployment for you which means<00:03:40.550> finding<00:03:41.240> all<00:03:41.540> of<00:03:41.660> your<00:03:41.810> contracts 00:03:42.460 --> 00:03:42.470 align:start position:0% means finding all of your contracts 00:03:42.470 --> 00:03:44.200 align:start position:0% means finding all of your contracts scraping<00:03:42.890> them<00:03:43.040> all<00:03:43.160> up<00:03:43.370> feeding<00:03:43.730> them<00:03:44.000> into 00:03:44.200 --> 00:03:44.210 align:start position:0% scraping them all up feeding them into 00:03:44.210 --> 00:03:46.360 align:start position:0% scraping them all up feeding them into the<00:03:44.330> solidity<00:03:44.660> compiler<00:03:45.320> and<00:03:45.560> giving<00:03:46.220> you<00:03:46.280> the 00:03:46.360 --> 00:03:46.370 align:start position:0% the solidity compiler and giving you the 00:03:46.370 --> 00:03:49.480 align:start position:0% the solidity compiler and giving you the results<00:03:46.790> same<00:03:47.000> with<00:03:47.150> deployment<00:03:48.490> deploying 00:03:49.480 --> 00:03:49.490 align:start position:0% results same with deployment deploying 00:03:49.490 --> 00:03:51.340 align:start position:0% results same with deployment deploying those<00:03:49.880> and<00:03:50.300> then<00:03:50.510> recording<00:03:51.140> those 00:03:51.340 --> 00:03:51.350 align:start position:0% those and then recording those 00:03:51.350 --> 00:03:53.140 align:start position:0% those and then recording those deployments<00:03:51.710> so<00:03:52.130> that<00:03:52.310> for<00:03:52.610> future 00:03:53.140 --> 00:03:53.150 align:start position:0% deployments so that for future 00:03:53.150 --> 00:03:54.760 align:start position:0% deployments so that for future deployments<00:03:53.780> you<00:03:53.870> can<00:03:54.020> still<00:03:54.230> reference<00:03:54.560> old 00:03:54.760 --> 00:03:54.770 align:start position:0% deployments you can still reference old 00:03:54.770 --> 00:03:56.740 align:start position:0% deployments you can still reference old deployments<00:03:55.340> things<00:03:55.520> like<00:03:55.670> that 00:03:56.740 --> 00:03:56.750 align:start position:0% deployments things like that 00:03:56.750 --> 00:03:59.080 align:start position:0% deployments things like that it<00:03:57.320> handles<00:03:57.890> library<00:03:58.370> linking<00:03:58.730> so<00:03:58.880> when<00:03:59.000> you 00:03:59.080 --> 00:03:59.090 align:start position:0% it handles library linking so when you 00:03:59.090 --> 00:04:00.610 align:start position:0% it handles library linking so when you use<00:03:59.240> libraries<00:03:59.870> you<00:04:00.050> end<00:04:00.200> up<00:04:00.290> with<00:04:00.440> something 00:04:00.610 --> 00:04:00.620 align:start position:0% use libraries you end up with something 00:04:00.620 --> 00:04:02.350 align:start position:0% use libraries you end up with something like<00:04:00.830> this<00:04:01.130> in<00:04:01.370> your<00:04:01.400> bytecode<00:04:01.940> you<00:04:02.120> see<00:04:02.240> that 00:04:02.350 --> 00:04:02.360 align:start position:0% like this in your bytecode you see that 00:04:02.360 --> 00:04:03.850 align:start position:0% like this in your bytecode you see that thing<00:04:02.510> at<00:04:02.630> the<00:04:02.660> bottom<00:04:03.050> there<00:04:03.260> and<00:04:03.650> that's<00:04:03.770> a 00:04:03.850 --> 00:04:03.860 align:start position:0% thing at the bottom there and that's a 00:04:03.860 --> 00:04:06.250 align:start position:0% thing at the bottom there and that's a placeholder<00:04:04.190> and<00:04:04.790> what<00:04:05.270> needs<00:04:05.570> to<00:04:05.720> go<00:04:05.990> there 00:04:06.250 --> 00:04:06.260 align:start position:0% placeholder and what needs to go there 00:04:06.260 --> 00:04:08.140 align:start position:0% placeholder and what needs to go there is<00:04:06.410> the<00:04:06.530> actual<00:04:06.890> address<00:04:07.400> of<00:04:07.550> the<00:04:07.700> deployed 00:04:08.140 --> 00:04:08.150 align:start position:0% is the actual address of the deployed 00:04:08.150 --> 00:04:11.680 align:start position:0% is the actual address of the deployed version<00:04:08.570> of<00:04:08.930> that<00:04:09.050> greeter<00:04:09.500> library<00:04:10.220> and<00:04:11.210> this 00:04:11.680 --> 00:04:11.690 align:start position:0% version of that greeter library and this 00:04:11.690 --> 00:04:14.530 align:start position:0% version of that greeter library and this stuff<00:04:11.960> is<00:04:12.140> is<00:04:12.530> you<00:04:13.460> need<00:04:13.760> to<00:04:13.850> get<00:04:13.970> it<00:04:14.060> right<00:04:14.270> and 00:04:14.530 --> 00:04:14.540 align:start position:0% stuff is is you need to get it right and 00:04:14.540 --> 00:04:16.539 align:start position:0% stuff is is you need to get it right and populist<00:04:14.960> just<00:04:15.200> automates<00:04:15.650> and<00:04:15.860> does<00:04:16.010> all<00:04:16.220> of 00:04:16.539 --> 00:04:16.549 align:start position:0% populist just automates and does all of 00:04:16.549 --> 00:04:20.260 align:start position:0% populist just automates and does all of this<00:04:16.850> sort<00:04:17.150> of<00:04:17.210> stuff<00:04:17.450> for<00:04:17.690> you<00:04:18.760> and<00:04:19.760> package 00:04:20.260 --> 00:04:20.270 align:start position:0% this sort of stuff for you and package 00:04:20.270 --> 00:04:22.480 align:start position:0% this sort of stuff for you and package management<00:04:20.600> we<00:04:21.230> have<00:04:21.350> this<00:04:21.530> sort<00:04:21.950> of<00:04:22.040> unmerged 00:04:22.480 --> 00:04:22.490 align:start position:0% management we have this sort of unmerged 00:04:22.490 --> 00:04:25.270 align:start position:0% management we have this sort of unmerged branch<00:04:22.970> that<00:04:23.210> has<00:04:23.360> all<00:04:23.600> of<00:04:23.630> the<00:04:24.020> ERC<00:04:24.350> 190 00:04:25.270 --> 00:04:25.280 align:start position:0% branch that has all of the ERC 190 00:04:25.280 --> 00:04:27.520 align:start position:0% branch that has all of the ERC 190 management's<00:04:25.850> stuff<00:04:26.030> in<00:04:26.180> it<00:04:26.300> it<00:04:26.780> is<00:04:27.170> a<00:04:27.200> high 00:04:27.520 --> 00:04:27.530 align:start position:0% management's stuff in it it is a high 00:04:27.530 --> 00:04:29.080 align:start position:0% management's stuff in it it is a high priority<00:04:27.830> for<00:04:28.160> us<00:04:28.340> to<00:04:28.490> get<00:04:28.610> this<00:04:28.730> stuff<00:04:28.970> in 00:04:29.080 --> 00:04:29.090 align:start position:0% priority for us to get this stuff in 00:04:29.090 --> 00:04:32.320 align:start position:0% priority for us to get this stuff in real<00:04:29.120> soon<00:04:29.630> and<00:04:30.220> well<00:04:31.220> package<00:04:31.790> management's 00:04:32.320 --> 00:04:32.330 align:start position:0% real soon and well package management's 00:04:32.330 --> 00:04:35.440 align:start position:0% real soon and well package management's a<00:04:32.360> big<00:04:32.510> deal<00:04:33.100> alright<00:04:34.100> there's<00:04:34.760> also<00:04:34.940> a<00:04:35.060> bunch 00:04:35.440 --> 00:04:35.450 align:start position:0% a big deal alright there's also a bunch 00:04:35.450 --> 00:04:37.810 align:start position:0% a big deal alright there's also a bunch of<00:04:35.630> other<00:04:35.780> tools<00:04:36.050> there's<00:04:36.950> a<00:04:37.070> youth<00:04:37.220> a<00:04:37.430> theorem 00:04:37.810 --> 00:04:37.820 align:start position:0% of other tools there's a youth a theorem 00:04:37.820 --> 00:04:39.400 align:start position:0% of other tools there's a youth a theorem utils<00:04:38.180> library<00:04:38.300> that<00:04:38.900> has<00:04:39.050> a<00:04:39.080> bunch<00:04:39.320> of 00:04:39.400 --> 00:04:39.410 align:start position:0% utils library that has a bunch of 00:04:39.410 --> 00:04:41.500 align:start position:0% utils library that has a bunch of low-level<00:04:39.919> stuff<00:04:40.220> that's<00:04:40.610> just<00:04:40.669> functional 00:04:41.500 --> 00:04:41.510 align:start position:0% low-level stuff that's just functional 00:04:41.510 --> 00:04:43.270 align:start position:0% low-level stuff that's just functional functions<00:04:42.080> that<00:04:42.380> you<00:04:42.500> can<00:04:42.530> use<00:04:42.830> that<00:04:43.040> do<00:04:43.160> all 00:04:43.270 --> 00:04:43.280 align:start position:0% functions that you can use that do all 00:04:43.280 --> 00:04:46.600 align:start position:0% functions that you can use that do all kinds<00:04:43.580> of<00:04:44.260> nice<00:04:45.260> convenient<00:04:46.010> useful<00:04:46.370> things 00:04:46.600 --> 00:04:46.610 align:start position:0% kinds of nice convenient useful things 00:04:46.610 --> 00:04:49.870 align:start position:0% kinds of nice convenient useful things that<00:04:46.880> are<00:04:47.260> that<00:04:48.260> that<00:04:48.590> prop<00:04:49.040> up<00:04:49.220> commonly<00:04:49.700> when 00:04:49.870 --> 00:04:49.880 align:start position:0% that are that that prop up commonly when 00:04:49.880 --> 00:04:51.550 align:start position:0% that are that that prop up commonly when you're<00:04:50.000> doing<00:04:50.150> ether<00:04:50.360> name<00:04:50.510> development<00:04:50.990> we 00:04:51.550 --> 00:04:51.560 align:start position:0% you're doing ether name development we 00:04:51.560 --> 00:04:53.290 align:start position:0% you're doing ether name development we have<00:04:51.650> an<00:04:51.740> ABI<00:04:51.980> utils<00:04:52.430> library<00:04:52.520> that<00:04:53.000> does<00:04:53.150> all 00:04:53.290 --> 00:04:53.300 align:start position:0% have an ABI utils library that does all 00:04:53.300 --> 00:04:55.120 align:start position:0% have an ABI utils library that does all the<00:04:53.419> ABI<00:04:53.690> encoding<00:04:54.230> and<00:04:54.320> decoding<00:04:54.470> so<00:04:54.980> if<00:04:55.040> you 00:04:55.120 --> 00:04:55.130 align:start position:0% the ABI encoding and decoding so if you 00:04:55.130 --> 00:04:56.590 align:start position:0% the ABI encoding and decoding so if you need<00:04:55.280> to<00:04:55.340> do<00:04:55.430> low-level<00:04:55.910> stuff<00:04:56.180> you<00:04:56.510> know 00:04:56.590 --> 00:04:56.600 align:start position:0% need to do low-level stuff you know 00:04:56.600 --> 00:04:58.240 align:start position:0% need to do low-level stuff you know pulling<00:04:56.840> old<00:04:57.050> transactions<00:04:57.740> seeing<00:04:58.100> what 00:04:58.240 --> 00:04:58.250 align:start position:0% pulling old transactions seeing what 00:04:58.250 --> 00:05:00.220 align:start position:0% pulling old transactions seeing what data<00:04:58.430> they<00:04:58.640> sent<00:04:58.880> stuff<00:04:59.150> like<00:04:59.300> that<00:04:59.510> you<00:05:00.080> can 00:05:00.220 --> 00:05:00.230 align:start position:0% data they sent stuff like that you can 00:05:00.230 --> 00:05:02.920 align:start position:0% data they sent stuff like that you can do<00:05:00.320> that<00:05:00.550> we<00:05:01.550> have<00:05:01.669> a<00:05:01.700> Keyes<00:05:02.180> library<00:05:02.750> that 00:05:02.920 --> 00:05:02.930 align:start position:0% do that we have a Keyes library that 00:05:02.930 --> 00:05:04.870 align:start position:0% do that we have a Keyes library that handles<00:05:03.140> the<00:05:03.730> elliptical<00:05:04.730> curve 00:05:04.870 --> 00:05:04.880 align:start position:0% handles the elliptical curve 00:05:04.880 --> 00:05:06.730 align:start position:0% handles the elliptical curve cryptography<00:05:05.120> stuff<00:05:05.930> for<00:05:06.200> you<00:05:06.380> so<00:05:06.560> if<00:05:06.620> you 00:05:06.730 --> 00:05:06.740 align:start position:0% cryptography stuff for you so if you 00:05:06.740 --> 00:05:09.220 align:start position:0% cryptography stuff for you so if you want<00:05:06.770> to<00:05:06.950> do<00:05:07.360> low-level<00:05:08.360> message<00:05:08.810> signing 00:05:09.220 --> 00:05:09.230 align:start position:0% want to do low-level message signing 00:05:09.230 --> 00:05:10.960 align:start position:0% want to do low-level message signing things<00:05:09.470> like<00:05:09.650> that<00:05:09.890> it<00:05:10.340> has<00:05:10.460> a<00:05:10.490> native<00:05:10.700> Python 00:05:10.960 --> 00:05:10.970 align:start position:0% things like that it has a native Python 00:05:10.970 --> 00:05:12.940 align:start position:0% things like that it has a native Python implementation<00:05:11.330> it'll<00:05:12.169> also<00:05:12.440> detect<00:05:12.830> the 00:05:12.940 --> 00:05:12.950 align:start position:0% implementation it'll also detect the 00:05:12.950 --> 00:05:14.890 align:start position:0% implementation it'll also detect the coin<00:05:13.130> curve<00:05:13.430> is<00:05:13.610> installed<00:05:14.030> and<00:05:14.419> use<00:05:14.660> coin 00:05:14.890 --> 00:05:14.900 align:start position:0% coin curve is installed and use coin 00:05:14.900 --> 00:05:18.430 align:start position:0% coin curve is installed and use coin curve<00:05:15.140> which<00:05:15.320> is<00:05:15.350> much<00:05:15.590> faster<00:05:17.050> and<00:05:18.050> it<00:05:18.320> has<00:05:18.410> a 00:05:18.430 --> 00:05:18.440 align:start position:0% curve which is much faster and it has a 00:05:18.440 --> 00:05:19.810 align:start position:0% curve which is much faster and it has a back-end<00:05:18.680> system<00:05:19.010> so<00:05:19.340> if<00:05:19.430> you<00:05:19.550> have<00:05:19.640> some 00:05:19.810 --> 00:05:19.820 align:start position:0% back-end system so if you have some 00:05:19.820 --> 00:05:21.610 align:start position:0% back-end system so if you have some other<00:05:19.970> implementation<00:05:20.720> of<00:05:20.810> ECC<00:05:21.229> that<00:05:21.470> you 00:05:21.610 --> 00:05:21.620 align:start position:0% other implementation of ECC that you 00:05:21.620 --> 00:05:24.670 align:start position:0% other implementation of ECC that you want<00:05:22.040> to<00:05:22.130> use<00:05:22.280> you<00:05:22.520> can<00:05:22.580> plug<00:05:22.940> it<00:05:23.060> right<00:05:23.180> in<00:05:23.680> you 00:05:24.670 --> 00:05:24.680 align:start position:0% want to use you can plug it right in you 00:05:24.680 --> 00:05:26.770 align:start position:0% want to use you can plug it right in you thin<00:05:24.830> room<00:05:24.950> key<00:05:25.100> file<00:05:25.370> loading<00:05:25.970> key<00:05:26.210> files<00:05:26.479> off 00:05:26.770 --> 00:05:26.780 align:start position:0% thin room key file loading key files off 00:05:26.780 --> 00:05:28.750 align:start position:0% thin room key file loading key files off disk<00:05:27.050> generating<00:05:27.770> key<00:05:27.950> files<00:05:28.160> from<00:05:28.400> private 00:05:28.750 --> 00:05:28.760 align:start position:0% disk generating key files from private 00:05:28.760 --> 00:05:31.690 align:start position:0% disk generating key files from private keys<00:05:29.680> key<00:05:30.680> stretching<00:05:30.979> that<00:05:31.250> sort<00:05:31.490> of<00:05:31.520> thing 00:05:31.690 --> 00:05:31.700 align:start position:0% keys key stretching that sort of thing 00:05:31.700 --> 00:05:33.580 align:start position:0% keys key stretching that sort of thing it's<00:05:31.850> all<00:05:31.970> handled<00:05:32.330> for<00:05:32.450> you<00:05:32.510> we<00:05:33.320> have<00:05:33.410> this 00:05:33.580 --> 00:05:33.590 align:start position:0% it's all handled for you we have this 00:05:33.590 --> 00:05:35.260 align:start position:0% it's all handled for you we have this library<00:05:34.100> called<00:05:34.250> PI<00:05:34.370> soul<00:05:34.610> C<00:05:34.820> which<00:05:35.090> is<00:05:35.240> a 00:05:35.260 --> 00:05:35.270 align:start position:0% library called PI soul C which is a 00:05:35.270 --> 00:05:38.040 align:start position:0% library called PI soul C which is a wrapper<00:05:35.570> around<00:05:35.900> the<00:05:36.500> solidity<00:05:36.860> compiler 00:05:38.040 --> 00:05:38.050 align:start position:0% wrapper around the solidity compiler 00:05:38.050 --> 00:05:40.000 align:start position:0% wrapper around the solidity compiler which<00:05:39.050> is<00:05:39.200> nice<00:05:39.380> because<00:05:39.530> you<00:05:39.650> can<00:05:39.890> do 00:05:40.000 --> 00:05:40.010 align:start position:0% which is nice because you can do 00:05:40.010 --> 00:05:41.830 align:start position:0% which is nice because you can do compilation<00:05:40.669> from<00:05:40.880> your<00:05:41.060> Python<00:05:41.390> code<00:05:41.630> you 00:05:41.830 --> 00:05:41.840 align:start position:0% compilation from your Python code you 00:05:41.840 --> 00:05:44.350 align:start position:0% compilation from your Python code you know<00:05:41.960> feet<00:05:42.169> in<00:05:42.370> feet<00:05:43.370> in<00:05:43.490> just<00:05:43.610> the<00:05:43.820> sources 00:05:44.350 --> 00:05:44.360 align:start position:0% know feet in feet in just the sources 00:05:44.360 --> 00:05:46.450 align:start position:0% know feet in feet in just the sources text<00:05:44.780> or<00:05:44.960> reference<00:05:45.470> some<00:05:45.650> files<00:05:46.010> and<00:05:46.370> just 00:05:46.450 --> 00:05:46.460 align:start position:0% text or reference some files and just 00:05:46.460 --> 00:05:48.159 align:start position:0% text or reference some files and just compilation<00:05:47.240> but<00:05:47.660> the<00:05:47.720> thing<00:05:47.870> that's<00:05:48.020> really 00:05:48.159 --> 00:05:48.169 align:start position:0% compilation but the thing that's really 00:05:48.169 --> 00:05:50.350 align:start position:0% compilation but the thing that's really great<00:05:48.500> here<00:05:48.770> is<00:05:48.950> that<00:05:49.190> we<00:05:49.820> have<00:05:49.910> automation 00:05:50.350 --> 00:05:50.360 align:start position:0% great here is that we have automation 00:05:50.360 --> 00:05:52.930 align:start position:0% great here is that we have automation built<00:05:50.720> into<00:05:50.990> it<00:05:51.110> for<00:05:51.320> installing<00:05:51.940> specific 00:05:52.930 --> 00:05:52.940 align:start position:0% built into it for installing specific 00:05:52.940 --> 00:05:55.360 align:start position:0% built into it for installing specific versions<00:05:53.270> of<00:05:53.419> solidity<00:05:53.810> from<00:05:54.080> source<00:05:54.380> so<00:05:55.070> if 00:05:55.360 --> 00:05:55.370 align:start position:0% versions of solidity from source so if 00:05:55.370 --> 00:05:57.040 align:start position:0% versions of solidity from source so if you<00:05:55.460> have<00:05:55.580> a<00:05:55.610> CI<00:05:55.850> environment<00:05:56.570> and<00:05:56.780> you<00:05:56.870> want 00:05:57.040 --> 00:05:57.050 align:start position:0% you have a CI environment and you want 00:05:57.050 --> 00:05:58.810 align:start position:0% you have a CI environment and you want to<00:05:57.110> run<00:05:57.289> your<00:05:57.440> stuff<00:05:57.710> in<00:05:57.860> Travis<00:05:58.340> and<00:05:58.610> you<00:05:58.669> want 00:05:58.810 --> 00:05:58.820 align:start position:0% to run your stuff in Travis and you want 00:05:58.820 --> 00:06:00.310 align:start position:0% to run your stuff in Travis and you want to<00:05:58.880> run<00:05:58.970> it<00:05:59.060> against<00:05:59.270> a<00:05:59.390> specific<00:05:59.600> solidity 00:06:00.310 --> 00:06:00.320 align:start position:0% to run it against a specific solidity 00:06:00.320 --> 00:06:02.830 align:start position:0% to run it against a specific solidity version<00:06:00.740> this<00:06:01.669> library<00:06:01.940> will<00:06:02.419> let<00:06:02.570> you<00:06:02.690> do 00:06:02.830 --> 00:06:02.840 align:start position:0% version this library will let you do 00:06:02.840 --> 00:06:04.870 align:start position:0% version this library will let you do that<00:06:02.990> right<00:06:03.229> off<00:06:03.380> the<00:06:03.530> bat<00:06:03.770> we<00:06:04.010> zaardon<00:06:04.370> almost 00:06:04.870 --> 00:06:04.880 align:start position:0% that right off the bat we zaardon almost 00:06:04.880 --> 00:06:06.219 align:start position:0% that right off the bat we zaardon almost all<00:06:05.030> of<00:06:05.150> our<00:06:05.270> other<00:06:05.360> repos<00:06:05.810> that<00:06:05.840> need 00:06:06.219 --> 00:06:06.229 align:start position:0% all of our other repos that need 00:06:06.229 --> 00:06:08.140 align:start position:0% all of our other repos that need solidity<00:06:06.650> and<00:06:06.919> it<00:06:07.400> lets<00:06:07.580> us<00:06:07.700> test<00:06:07.850> against 00:06:08.140 --> 00:06:08.150 align:start position:0% solidity and it lets us test against 00:06:08.150 --> 00:06:11.140 align:start position:0% solidity and it lets us test against specific<00:06:08.600> versions<00:06:08.930> of<00:06:09.080> solidity<00:06:10.150> aetherium 00:06:11.140 --> 00:06:11.150 align:start position:0% specific versions of solidity aetherium 00:06:11.150 --> 00:06:12.940 align:start position:0% specific versions of solidity aetherium tester<00:06:11.539> is<00:06:11.780> a<00:06:11.810> library<00:06:12.560> that<00:06:12.590> we've<00:06:12.800> been 00:06:12.940 --> 00:06:12.950 align:start position:0% tester is a library that we've been 00:06:12.950 --> 00:06:15.990 align:start position:0% tester is a library that we've been working<00:06:13.310> on<00:06:13.460> it's<00:06:13.820> a<00:06:14.060> sort<00:06:14.390> of<00:06:14.530> wrapper<00:06:15.530> around 00:06:15.990 --> 00:06:16.000 align:start position:0% working on it's a sort of wrapper around 00:06:16.000 --> 00:06:18.700 align:start position:0% working on it's a sort of wrapper around using<00:06:17.000> test<00:06:17.270> block<00:06:17.510> chains<00:06:17.810> so<00:06:18.229> right<00:06:18.440> now<00:06:18.560> it 00:06:18.700 --> 00:06:18.710 align:start position:0% using test block chains so right now it 00:06:18.710 --> 00:06:20.920 align:start position:0% using test block chains so right now it supports<00:06:19.160> the<00:06:19.250> PI<00:06:20.150> II<00:06:20.180> theory<00:06:20.510> and<00:06:20.690> blockchain 00:06:20.920 --> 00:06:20.930 align:start position:0% supports the PI II theory and blockchain 00:06:20.930 --> 00:06:23.469 align:start position:0% supports the PI II theory and blockchain but<00:06:21.500> sort<00:06:21.710> of<00:06:21.740> an<00:06:21.860> older<00:06:22.160> version<00:06:22.340> of<00:06:22.580> it<00:06:22.729> we're 00:06:23.469 --> 00:06:23.479 align:start position:0% but sort of an older version of it we're 00:06:23.479 --> 00:06:26.610 align:start position:0% but sort of an older version of it we're working<00:06:23.900> on<00:06:24.280> more<00:06:25.280> backends<00:06:25.970> for<00:06:26.000> more 00:06:26.610 --> 00:06:26.620 align:start position:0% working on more backends for more 00:06:26.620 --> 00:06:30.370 align:start position:0% working on more backends for more options<00:06:27.620> for<00:06:27.740> testing<00:06:28.600> specifically<00:06:29.600> PI<00:06:29.960> EVM 00:06:30.370 --> 00:06:30.380 align:start position:0% options for testing specifically PI EVM 00:06:30.380 --> 00:06:32.680 align:start position:0% options for testing specifically PI EVM is<00:06:30.590> the<00:06:30.800> one<00:06:30.950> that<00:06:31.039> we're<00:06:31.160> focusing<00:06:31.550> on<00:06:31.669> and<00:06:31.970> it 00:06:32.680 --> 00:06:32.690 align:start position:0% is the one that we're focusing on and it 00:06:32.690 --> 00:06:34.659 align:start position:0% is the one that we're focusing on and it has<00:06:32.840> really<00:06:33.050> nice<00:06:33.229> web<00:06:33.470> 3<00:06:33.710> integration<00:06:34.250> so<00:06:34.430> if 00:06:34.659 --> 00:06:34.669 align:start position:0% has really nice web 3 integration so if 00:06:34.669 --> 00:06:36.190 align:start position:0% has really nice web 3 integration so if you're<00:06:34.820> using<00:06:35.000> web<00:06:35.240> 3<00:06:35.419> py<00:06:35.750> in<00:06:36.080> your 00:06:36.190 --> 00:06:36.200 align:start position:0% you're using web 3 py in your 00:06:36.200 --> 00:06:38.600 align:start position:0% you're using web 3 py in your application<00:06:36.770> and<00:06:37.010> you<00:06:37.400> want<00:06:37.610> to<00:06:37.760> test<00:06:38.060> again 00:06:38.600 --> 00:06:38.610 align:start position:0% application and you want to test again 00:06:38.610 --> 00:06:40.700 align:start position:0% application and you want to test again blockchain<00:06:39.270> all<00:06:39.810> you<00:06:39.990> have<00:06:40.110> to<00:06:40.199> do<00:06:40.319> is<00:06:40.439> swap 00:06:40.700 --> 00:06:40.710 align:start position:0% blockchain all you have to do is swap 00:06:40.710 --> 00:06:42.499 align:start position:0% blockchain all you have to do is swap out<00:06:40.889> the<00:06:41.009> provider<00:06:41.430> rather<00:06:41.789> than<00:06:42.090> changing<00:06:42.449> a 00:06:42.499 --> 00:06:42.509 align:start position:0% out the provider rather than changing a 00:06:42.509 --> 00:06:44.390 align:start position:0% out the provider rather than changing a bunch<00:06:42.689> of<00:06:42.750> your<00:06:42.900> code<00:06:43.110> and<00:06:43.409> you<00:06:43.770> can<00:06:43.800> test<00:06:44.159> and 00:06:44.390 --> 00:06:44.400 align:start position:0% bunch of your code and you can test and 00:06:44.400 --> 00:06:46.279 align:start position:0% bunch of your code and you can test and you<00:06:44.759> can<00:06:44.879> run<00:06:45.060> your<00:06:45.090> application<00:06:45.719> against<00:06:46.139> a 00:06:46.279 --> 00:06:46.289 align:start position:0% you can run your application against a 00:06:46.289 --> 00:06:49.610 align:start position:0% you can run your application against a test<00:06:46.560> bachi<00:06:47.030> blockchain<00:06:48.139> and<00:06:49.139> we've<00:06:49.469> got<00:06:49.590> a 00:06:49.610 --> 00:06:49.620 align:start position:0% test bachi blockchain and we've got a 00:06:49.620 --> 00:06:51.230 align:start position:0% test bachi blockchain and we've got a bunch<00:06:49.740> of<00:06:49.860> more<00:06:50.009> things<00:06:50.250> there's<00:06:50.699> this<00:06:50.819> pi<00:06:51.000> f 00:06:51.230 --> 00:06:51.240 align:start position:0% bunch of more things there's this pi f 00:06:51.240 --> 00:06:52.730 align:start position:0% bunch of more things there's this pi f library<00:06:51.689> that<00:06:51.900> has<00:06:52.080> some<00:06:52.199> nice<00:06:52.319> wrappers 00:06:52.730 --> 00:06:52.740 align:start position:0% library that has some nice wrappers 00:06:52.740 --> 00:06:55.100 align:start position:0% library that has some nice wrappers around<00:06:52.770> the<00:06:53.180> etherium<00:06:54.180> command<00:06:54.449> line<00:06:54.629> and 00:06:55.100 --> 00:06:55.110 align:start position:0% around the etherium command line and 00:06:55.110 --> 00:06:57.379 align:start position:0% around the etherium command line and implementation<00:06:55.919> of<00:06:56.009> the<00:06:56.099> of<00:06:56.789> the<00:06:57.060> patricia 00:06:57.379 --> 00:06:57.389 align:start position:0% implementation of the of the patricia 00:06:57.389 --> 00:06:59.300 align:start position:0% implementation of the of the patricia tree<00:06:57.750> and<00:06:58.169> implementation<00:06:58.979> of<00:06:59.069> the<00:06:59.129> bloom 00:06:59.300 --> 00:06:59.310 align:start position:0% tree and implementation of the bloom 00:06:59.310 --> 00:07:03.950 align:start position:0% tree and implementation of the bloom filter<00:07:00.110> lots<00:07:01.110> of<00:07:01.259> tools<00:07:01.759> wides<00:07:02.759> wide<00:07:03.569> array<00:07:03.930> of 00:07:03.950 --> 00:07:03.960 align:start position:0% filter lots of tools wides wide array of 00:07:03.960 --> 00:07:06.770 align:start position:0% filter lots of tools wides wide array of them<00:07:04.879> that<00:07:05.879> are<00:07:05.939> all<00:07:06.030> supported<00:07:06.599> where 00:07:06.770 --> 00:07:06.780 align:start position:0% them that are all supported where 00:07:06.780 --> 00:07:09.499 align:start position:0% them that are all supported where they're<00:07:07.020> all<00:07:07.139> actively<00:07:07.620> developed<00:07:08.069> and<00:07:08.509> you 00:07:09.499 --> 00:07:09.509 align:start position:0% they're all actively developed and you 00:07:09.509 --> 00:07:12.170 align:start position:0% they're all actively developed and you should<00:07:09.689> give<00:07:09.810> them<00:07:09.900> a<00:07:09.960> try<00:07:10.759> but<00:07:11.759> what<00:07:11.909> I<00:07:11.939> really 00:07:12.170 --> 00:07:12.180 align:start position:0% should give them a try but what I really 00:07:12.180 --> 00:07:15.260 align:start position:0% should give them a try but what I really want<00:07:12.300> to<00:07:12.330> talk<00:07:12.479> about<00:07:12.599> is<00:07:12.750> PI<00:07:12.900> EVM<00:07:13.430> PI<00:07:14.430> a<00:07:14.460> VM<00:07:14.849> is 00:07:15.260 --> 00:07:15.270 align:start position:0% want to talk about is PI EVM PI a VM is 00:07:15.270 --> 00:07:18.649 align:start position:0% want to talk about is PI EVM PI a VM is a<00:07:15.810> new<00:07:16.800> implementation<00:07:17.639> of<00:07:17.849> the<00:07:18.210> theory<00:07:18.569> and 00:07:18.649 --> 00:07:18.659 align:start position:0% a new implementation of the theory and 00:07:18.659 --> 00:07:20.899 align:start position:0% a new implementation of the theory and virtual<00:07:18.960> machine<00:07:19.229> in<00:07:19.319> Python<00:07:19.680> and<00:07:20.550> it<00:07:20.729> came 00:07:20.899 --> 00:07:20.909 align:start position:0% virtual machine in Python and it came 00:07:20.909 --> 00:07:22.570 align:start position:0% virtual machine in Python and it came about<00:07:21.060> sort<00:07:21.569> of<00:07:21.659> in<00:07:21.779> this<00:07:21.930> roundabout<00:07:22.289> way 00:07:22.570 --> 00:07:22.580 align:start position:0% about sort of in this roundabout way 00:07:22.580 --> 00:07:24.800 align:start position:0% about sort of in this roundabout way originally<00:07:23.580> there's<00:07:23.759> PI<00:07:23.969> e<00:07:24.000> theorem<00:07:24.509> and<00:07:24.629> PI<00:07:24.779> 3 00:07:24.800 --> 00:07:24.810 align:start position:0% originally there's PI e theorem and PI 3 00:07:24.810 --> 00:07:27.559 align:start position:0% originally there's PI e theorem and PI 3 and<00:07:25.199> PI<00:07:25.409> EVM<00:07:25.889> are<00:07:26.039> not<00:07:26.250> the<00:07:26.460> same<00:07:26.610> thing 00:07:27.559 --> 00:07:27.569 align:start position:0% and PI EVM are not the same thing 00:07:27.569 --> 00:07:29.719 align:start position:0% and PI EVM are not the same thing pi<00:07:27.930> e<00:07:27.960> theorem<00:07:28.349> is<00:07:28.590> a<00:07:28.620> library<00:07:29.400> that's<00:07:29.580> been 00:07:29.719 --> 00:07:29.729 align:start position:0% pi e theorem is a library that's been 00:07:29.729 --> 00:07:32.779 align:start position:0% pi e theorem is a library that's been around<00:07:29.819> since<00:07:30.240> the<00:07:30.509> since<00:07:31.110> for<00:07:31.560> well<00:07:31.860> as<00:07:32.610> long 00:07:32.779 --> 00:07:32.789 align:start position:0% around since the since for well as long 00:07:32.789 --> 00:07:34.580 align:start position:0% around since the since for well as long as<00:07:32.909> I<00:07:32.969> can<00:07:33.090> remember<00:07:33.150> I<00:07:33.599> was<00:07:34.199> written<00:07:34.379> by<00:07:34.529> the 00:07:34.580 --> 00:07:34.590 align:start position:0% as I can remember I was written by the 00:07:34.590 --> 00:07:37.219 align:start position:0% as I can remember I was written by the talaq<00:07:35.069> it's<00:07:35.849> a<00:07:36.060> library<00:07:36.509> dependency<00:07:36.990> and<00:07:37.169> a 00:07:37.219 --> 00:07:37.229 align:start position:0% talaq it's a library dependency and a 00:07:37.229 --> 00:07:40.219 align:start position:0% talaq it's a library dependency and a ton<00:07:37.439> of<00:07:37.469> our<00:07:37.680> code<00:07:37.860> bases<00:07:38.240> and<00:07:39.240> it<00:07:39.659> is<00:07:39.930> used 00:07:40.219 --> 00:07:40.229 align:start position:0% ton of our code bases and it is used 00:07:40.229 --> 00:07:42.080 align:start position:0% ton of our code bases and it is used heavily<00:07:40.500> right<00:07:40.830> now<00:07:40.979> by<00:07:41.159> the<00:07:41.219> by<00:07:41.550> the<00:07:41.610> Kasper 00:07:42.080 --> 00:07:42.090 align:start position:0% heavily right now by the by the Kasper 00:07:42.090 --> 00:07:44.540 align:start position:0% heavily right now by the by the Kasper research<00:07:42.360> team<00:07:42.740> Python<00:07:43.740> is<00:07:43.860> a<00:07:43.889> great<00:07:44.159> research 00:07:44.540 --> 00:07:44.550 align:start position:0% research team Python is a great research 00:07:44.550 --> 00:07:46.670 align:start position:0% research team Python is a great research tool<00:07:44.580> because<00:07:45.060> it's<00:07:45.210> so<00:07:45.449> mutable<00:07:46.110> I<00:07:46.229> just 00:07:46.670 --> 00:07:46.680 align:start position:0% tool because it's so mutable I just 00:07:46.680 --> 00:07:50.149 align:start position:0% tool because it's so mutable I just reach<00:07:46.860> in<00:07:47.069> do<00:07:47.250> whatever<00:07:47.400> you<00:07:47.699> want<00:07:47.909> and<00:07:48.750> and<00:07:49.159> PI 00:07:50.149 --> 00:07:50.159 align:start position:0% reach in do whatever you want and and PI 00:07:50.159 --> 00:07:53.269 align:start position:0% reach in do whatever you want and and PI aetherium<00:07:50.669> has<00:07:51.000> been<00:07:51.330> key<00:07:51.839> for<00:07:52.080> so<00:07:52.979> much<00:07:53.099> of 00:07:53.269 --> 00:07:53.279 align:start position:0% aetherium has been key for so much of 00:07:53.279 --> 00:07:54.529 align:start position:0% aetherium has been key for so much of the<00:07:53.370> research<00:07:53.520> and<00:07:53.909> things<00:07:54.089> that<00:07:54.180> have<00:07:54.389> been 00:07:54.529 --> 00:07:54.539 align:start position:0% the research and things that have been 00:07:54.539 --> 00:07:57.499 align:start position:0% the research and things that have been done<00:07:54.750> for<00:07:55.139> the<00:07:55.500> etherium<00:07:55.889> network<00:07:56.159> however<00:07:56.969> it 00:07:57.499 --> 00:07:57.509 align:start position:0% done for the etherium network however it 00:07:57.509 --> 00:07:59.839 align:start position:0% done for the etherium network however it has<00:07:57.719> not<00:07:57.930> been<00:07:58.169> a<00:07:58.229> very<00:07:58.319> good<00:07:58.740> library<00:07:59.430> for<00:07:59.699> us 00:07:59.839 --> 00:07:59.849 align:start position:0% has not been a very good library for us 00:07:59.849 --> 00:08:02.540 align:start position:0% has not been a very good library for us to<00:08:00.089> build<00:08:00.330> on<00:08:00.569> top<00:08:00.599> of<00:08:01.129> and<00:08:02.129> I'll<00:08:02.219> go<00:08:02.339> into<00:08:02.520> some 00:08:02.540 --> 00:08:02.550 align:start position:0% to build on top of and I'll go into some 00:08:02.550 --> 00:08:04.070 align:start position:0% to build on top of and I'll go into some reasons<00:08:02.940> there<00:08:03.120> and<00:08:03.300> then<00:08:03.419> there's<00:08:03.569> PI<00:08:03.719> Etha 00:08:04.070 --> 00:08:04.080 align:start position:0% reasons there and then there's PI Etha 00:08:04.080 --> 00:08:06.469 align:start position:0% reasons there and then there's PI Etha pand<00:08:04.319> PI<00:08:04.409> Etha<00:08:04.740> is<00:08:04.979> the<00:08:05.190> Python<00:08:05.729> aetherium 00:08:06.469 --> 00:08:06.479 align:start position:0% pand PI Etha is the Python aetherium 00:08:06.479 --> 00:08:07.879 align:start position:0% pand PI Etha is the Python aetherium node<00:08:06.690> so<00:08:06.900> if<00:08:06.990> you<00:08:07.050> want<00:08:07.169> to<00:08:07.229> run<00:08:07.379> connect<00:08:07.800> to 00:08:07.879 --> 00:08:07.889 align:start position:0% node so if you want to run connect to 00:08:07.889 --> 00:08:10.279 align:start position:0% node so if you want to run connect to the<00:08:07.979> network<00:08:08.159> then<00:08:08.819> PI<00:08:09.029> e<00:08:09.060> thapa's<00:08:09.599> is<00:08:09.870> the 00:08:10.279 --> 00:08:10.289 align:start position:0% the network then PI e thapa's is the 00:08:10.289 --> 00:08:12.110 align:start position:0% the network then PI e thapa's is the thing<00:08:10.500> that<00:08:10.740> in<00:08:10.979> theory<00:08:11.580> could<00:08:11.849> do<00:08:11.969> that 00:08:12.110 --> 00:08:12.120 align:start position:0% thing that in theory could do that 00:08:12.120 --> 00:08:13.969 align:start position:0% thing that in theory could do that however<00:08:12.569> for<00:08:12.990> a<00:08:13.020> very<00:08:13.259> long<00:08:13.439> time<00:08:13.710> it<00:08:13.860> has<00:08:13.949> not 00:08:13.969 --> 00:08:13.979 align:start position:0% however for a very long time it has not 00:08:13.979 --> 00:08:15.260 align:start position:0% however for a very long time it has not been<00:08:14.189> able<00:08:14.310> to<00:08:14.520> sync<00:08:14.729> with<00:08:14.849> the<00:08:14.909> main<00:08:15.060> net 00:08:15.260 --> 00:08:15.270 align:start position:0% been able to sync with the main net 00:08:15.270 --> 00:08:18.890 align:start position:0% been able to sync with the main net network<00:08:15.680> so<00:08:16.680> we<00:08:17.180> had<00:08:18.180> these<00:08:18.300> two<00:08:18.360> existing 00:08:18.890 --> 00:08:18.900 align:start position:0% network so we had these two existing 00:08:18.900 --> 00:08:21.230 align:start position:0% network so we had these two existing libraries<00:08:19.409> and<00:08:19.650> they<00:08:19.979> facilitated<00:08:20.580> a<00:08:20.969> ton<00:08:21.210> of 00:08:21.230 --> 00:08:21.240 align:start position:0% libraries and they facilitated a ton of 00:08:21.240 --> 00:08:24.829 align:start position:0% libraries and they facilitated a ton of research<00:08:21.659> but<00:08:22.159> but<00:08:23.159> over<00:08:23.580> the<00:08:23.969> last<00:08:24.150> two<00:08:24.659> and<00:08:24.689> a 00:08:24.829 --> 00:08:24.839 align:start position:0% research but but over the last two and a 00:08:24.839 --> 00:08:26.510 align:start position:0% research but but over the last two and a half<00:08:24.990> or<00:08:25.229> three<00:08:25.259> years<00:08:25.650> or<00:08:25.710> however<00:08:26.009> long<00:08:26.250> it's 00:08:26.510 --> 00:08:26.520 align:start position:0% half or three years or however long it's 00:08:26.520 --> 00:08:28.820 align:start position:0% half or three years or however long it's been<00:08:26.810> these<00:08:27.810> libraries<00:08:28.379> have<00:08:28.469> also<00:08:28.589> been<00:08:28.800> a 00:08:28.820 --> 00:08:28.830 align:start position:0% been these libraries have also been a 00:08:28.830 --> 00:08:31.579 align:start position:0% been these libraries have also been a huge<00:08:28.889> thorn<00:08:29.400> in<00:08:29.550> my<00:08:29.580> side<00:08:29.699> because<00:08:30.439> there's<00:08:31.439> no 00:08:31.579 --> 00:08:31.589 align:start position:0% huge thorn in my side because there's no 00:08:31.589 --> 00:08:32.959 align:start position:0% huge thorn in my side because there's no definition<00:08:32.099> of<00:08:32.159> what<00:08:32.339> is<00:08:32.459> a<00:08:32.490> public<00:08:32.849> and 00:08:32.959 --> 00:08:32.969 align:start position:0% definition of what is a public and 00:08:32.969 --> 00:08:35.000 align:start position:0% definition of what is a public and private<00:08:33.000> API<00:08:33.539> and<00:08:34.050> and<00:08:34.260> therein<00:08:34.560> they're<00:08:34.709> big 00:08:35.000 --> 00:08:35.010 align:start position:0% private API and and therein they're big 00:08:35.010 --> 00:08:36.889 align:start position:0% private API and and therein they're big and<00:08:35.370> there's<00:08:35.669> and<00:08:35.969> they're<00:08:36.089> monoliths<00:08:36.690> and 00:08:36.889 --> 00:08:36.899 align:start position:0% and there's and they're monoliths and 00:08:36.899 --> 00:08:39.230 align:start position:0% and there's and they're monoliths and and<00:08:37.140> things<00:08:37.800> changed<00:08:38.159> out<00:08:38.279> from<00:08:38.459> under<00:08:38.760> us<00:08:38.909> and 00:08:39.230 --> 00:08:39.240 align:start position:0% and things changed out from under us and 00:08:39.240 --> 00:08:41.240 align:start position:0% and things changed out from under us and and<00:08:39.659> they're<00:08:39.930> just<00:08:40.079> not<00:08:40.380> the<00:08:40.649> foundation<00:08:41.099> that 00:08:41.240 --> 00:08:41.250 align:start position:0% and they're just not the foundation that 00:08:41.250 --> 00:08:44.120 align:start position:0% and they're just not the foundation that we<00:08:41.310> needed<00:08:41.490> them<00:08:41.729> to<00:08:41.760> be<00:08:42.000> so<00:08:42.719> about<00:08:43.620> a<00:08:43.680> year<00:08:43.800> ago 00:08:44.120 --> 00:08:44.130 align:start position:0% we needed them to be so about a year ago 00:08:44.130 --> 00:08:46.579 align:start position:0% we needed them to be so about a year ago I<00:08:44.519> started<00:08:44.940> tinkering<00:08:45.269> with<00:08:45.630> okay<00:08:46.230> well<00:08:46.380> what 00:08:46.579 --> 00:08:46.589 align:start position:0% I started tinkering with okay well what 00:08:46.589 --> 00:08:50.180 align:start position:0% I started tinkering with okay well what if<00:08:46.680> I<00:08:46.770> write<00:08:46.920> my<00:08:47.069> own<00:08:47.870> so<00:08:48.870> anyway<00:08:49.290> so<00:08:49.560> I<00:08:49.589> started 00:08:50.180 --> 00:08:50.190 align:start position:0% if I write my own so anyway so I started 00:08:50.190 --> 00:08:51.670 align:start position:0% if I write my own so anyway so I started this<00:08:50.310> experimental<00:08:50.819> project 00:08:51.670 --> 00:08:51.680 align:start position:0% this experimental project 00:08:51.680 --> 00:08:57.369 align:start position:0% this experimental project evm<00:08:52.449> and<00:08:53.449> it<00:08:54.110> sort<00:08:54.410> of<00:08:55.209> festered<00:08:56.209> and<00:08:56.389> and<00:08:56.839> kept 00:08:57.369 --> 00:08:57.379 align:start position:0% evm and it sort of festered and and kept 00:08:57.379 --> 00:09:00.609 align:start position:0% evm and it sort of festered and and kept going<00:08:57.499> and<00:08:57.800> kept<00:08:57.980> going<00:08:58.040> and<00:08:59.350> let<00:09:00.350> me<00:09:00.410> tell<00:09:00.529> you 00:09:00.609 --> 00:09:00.619 align:start position:0% going and kept going and let me tell you 00:09:00.619 --> 00:09:02.379 align:start position:0% going and kept going and let me tell you some<00:09:00.769> of<00:09:00.800> the<00:09:00.920> origins<00:09:01.309> so<00:09:01.579> one<00:09:02.029> of<00:09:02.059> the<00:09:02.240> big 00:09:02.379 --> 00:09:02.389 align:start position:0% some of the origins so one of the big 00:09:02.389 --> 00:09:04.869 align:start position:0% some of the origins so one of the big things<00:09:02.600> was<00:09:02.839> don't<00:09:03.259> bother<00:09:03.439> Vitalik<00:09:04.069> that<00:09:04.790> was 00:09:04.869 --> 00:09:04.879 align:start position:0% things was don't bother Vitalik that was 00:09:04.879 --> 00:09:07.019 align:start position:0% things was don't bother Vitalik that was one<00:09:05.029> of<00:09:05.089> the<00:09:05.180> main<00:09:05.360> motivations<00:09:05.689> here<00:09:06.319> I 00:09:07.019 --> 00:09:07.029 align:start position:0% one of the main motivations here I 00:09:07.029 --> 00:09:09.069 align:start position:0% one of the main motivations here I didn't<00:09:08.029> think<00:09:08.209> that<00:09:08.360> I<00:09:08.420> could<00:09:08.629> fix<00:09:08.839> by 00:09:09.069 --> 00:09:09.079 align:start position:0% didn't think that I could fix by 00:09:09.079 --> 00:09:11.259 align:start position:0% didn't think that I could fix by aetherium<00:09:09.649> without<00:09:10.129> interrupting<00:09:10.639> his<00:09:11.059> work 00:09:11.259 --> 00:09:11.269 align:start position:0% aetherium without interrupting his work 00:09:11.269 --> 00:09:12.730 align:start position:0% aetherium without interrupting his work there<00:09:11.779> was<00:09:11.899> so<00:09:12.050> much<00:09:12.170> that<00:09:12.379> needed<00:09:12.619> to<00:09:12.649> be 00:09:12.730 --> 00:09:12.740 align:start position:0% there was so much that needed to be 00:09:12.740 --> 00:09:16.059 align:start position:0% there was so much that needed to be changed<00:09:13.279> that<00:09:13.429> I<00:09:13.490> felt<00:09:14.259> that<00:09:15.259> the<00:09:15.679> scope<00:09:15.920> of 00:09:16.059 --> 00:09:16.069 align:start position:0% changed that I felt that the scope of 00:09:16.069 --> 00:09:17.980 align:start position:0% changed that I felt that the scope of the<00:09:16.220> changes<00:09:16.550> it<00:09:16.639> was<00:09:16.699> so<00:09:16.879> large<00:09:17.059> that<00:09:17.209> I<00:09:17.420> that 00:09:17.980 --> 00:09:17.990 align:start position:0% the changes it was so large that I that 00:09:17.990 --> 00:09:19.780 align:start position:0% the changes it was so large that I that I<00:09:18.019> assumed<00:09:18.470> that<00:09:18.740> it<00:09:19.129> would<00:09:19.429> be<00:09:19.519> impossible 00:09:19.780 --> 00:09:19.790 align:start position:0% I assumed that it would be impossible 00:09:19.790 --> 00:09:21.869 align:start position:0% I assumed that it would be impossible for<00:09:20.119> me<00:09:20.300> to<00:09:20.449> fix<00:09:20.600> pi-theorem<00:09:21.050> without 00:09:21.869 --> 00:09:21.879 align:start position:0% for me to fix pi-theorem without 00:09:21.879 --> 00:09:24.609 align:start position:0% for me to fix pi-theorem without disrupting<00:09:22.879> metallics<00:09:23.420> work<00:09:23.629> I<00:09:24.139> wanted<00:09:24.559> to 00:09:24.609 --> 00:09:24.619 align:start position:0% disrupting metallics work I wanted to 00:09:24.619 --> 00:09:27.129 align:start position:0% disrupting metallics work I wanted to better<00:09:24.800> understand<00:09:25.399> the<00:09:25.519> EVM<00:09:25.879> and<00:09:26.209> it's<00:09:26.749> that 00:09:27.129 --> 00:09:27.139 align:start position:0% better understand the EVM and it's that 00:09:27.139 --> 00:09:28.150 align:start position:0% better understand the EVM and it's that thing<00:09:27.319> that<00:09:27.470> I<00:09:27.499> need<00:09:27.679> I<00:09:27.709> needed<00:09:28.069> a 00:09:28.150 --> 00:09:28.160 align:start position:0% thing that I need I needed a 00:09:28.160 --> 00:09:29.559 align:start position:0% thing that I need I needed a foundational<00:09:28.759> library<00:09:29.149> that<00:09:29.240> I<00:09:29.300> could<00:09:29.449> build 00:09:29.559 --> 00:09:29.569 align:start position:0% foundational library that I could build 00:09:29.569 --> 00:09:33.249 align:start position:0% foundational library that I could build on<00:09:29.749> top<00:09:29.899> of<00:09:30.550> um<00:09:31.550> we<00:09:32.179> are<00:09:32.389> shooting<00:09:32.689> for 00:09:33.249 --> 00:09:33.259 align:start position:0% on top of um we are shooting for 00:09:33.259 --> 00:09:35.470 align:start position:0% on top of um we are shooting for something<00:09:33.949> that<00:09:34.309> is<00:09:34.459> the<00:09:34.699> easiest<00:09:35.089> to<00:09:35.360> install 00:09:35.470 --> 00:09:35.480 align:start position:0% something that is the easiest to install 00:09:35.480 --> 00:09:36.939 align:start position:0% something that is the easiest to install client 00:09:36.939 --> 00:09:36.949 align:start position:0% client 00:09:36.949 --> 00:09:39.160 align:start position:0% client it'll<00:09:37.429> be<00:09:37.550> primarily<00:09:38.089> focused<00:09:38.360> on<00:09:38.869> being<00:09:39.050> a 00:09:39.160 --> 00:09:39.170 align:start position:0% it'll be primarily focused on being a 00:09:39.170 --> 00:09:41.230 align:start position:0% it'll be primarily focused on being a light<00:09:39.350> client<00:09:39.740> although<00:09:39.920> we<00:09:40.160> will<00:09:40.399> support 00:09:41.230 --> 00:09:41.240 align:start position:0% light client although we will support 00:09:41.240 --> 00:09:43.660 align:start position:0% light client although we will support being<00:09:41.480> a<00:09:41.569> full<00:09:41.749> node<00:09:41.959> and<00:09:42.369> we're<00:09:43.369> hoping<00:09:43.610> that 00:09:43.660 --> 00:09:43.670 align:start position:0% being a full node and we're hoping that 00:09:43.670 --> 00:09:45.639 align:start position:0% being a full node and we're hoping that it's<00:09:43.879> gonna<00:09:43.939> facilitate<00:09:44.600> research<00:09:45.170> really 00:09:45.639 --> 00:09:45.649 align:start position:0% it's gonna facilitate research really 00:09:45.649 --> 00:09:47.980 align:start position:0% it's gonna facilitate research really well<00:09:45.889> but<00:09:46.220> we<00:09:46.490> have<00:09:46.910> every<00:09:47.209> intention<00:09:47.689> of<00:09:47.809> this 00:09:47.980 --> 00:09:47.990 align:start position:0% well but we have every intention of this 00:09:47.990 --> 00:09:51.129 align:start position:0% well but we have every intention of this be<00:09:48.259> being<00:09:49.129> a<00:09:49.339> full<00:09:49.579> node<00:09:49.819> or<00:09:50.149> a<00:09:50.209> light<00:09:50.839> client 00:09:51.129 --> 00:09:51.139 align:start position:0% be being a full node or a light client 00:09:51.139 --> 00:09:52.569 align:start position:0% be being a full node or a light client node<00:09:51.319> that<00:09:51.470> you<00:09:51.589> can<00:09:51.740> run<00:09:51.980> and<00:09:52.249> use<00:09:52.399> in 00:09:52.569 --> 00:09:52.579 align:start position:0% node that you can run and use in 00:09:52.579 --> 00:09:56.079 align:start position:0% node that you can run and use in production<00:09:54.220> this<00:09:55.220> is<00:09:55.279> our<00:09:55.490> status<00:09:55.850> right<00:09:56.029> now 00:09:56.079 --> 00:09:56.089 align:start position:0% production this is our status right now 00:09:56.089 --> 00:09:58.239 align:start position:0% production this is our status right now we've<00:09:56.749> got<00:09:56.959> most<00:09:57.199> of<00:09:57.350> the<00:09:57.499> fork<00:09:57.740> rules<00:09:58.009> done 00:09:58.239 --> 00:09:58.249 align:start position:0% we've got most of the fork rules done 00:09:58.249 --> 00:10:00.400 align:start position:0% we've got most of the fork rules done byzantium<00:09:58.939> is<00:09:59.089> still<00:09:59.240> in<00:09:59.360> progress<00:09:59.660> and<00:10:00.199> we've 00:10:00.400 --> 00:10:00.410 align:start position:0% byzantium is still in progress and we've 00:10:00.410 --> 00:10:02.860 align:start position:0% byzantium is still in progress and we've got<00:10:00.709> the<00:10:01.339> le<00:10:01.579> s<00:10:01.699> protocol<00:10:02.179> in<00:10:02.300> progress<00:10:02.509> right 00:10:02.860 --> 00:10:02.870 align:start position:0% got the le s protocol in progress right 00:10:02.870 --> 00:10:06.610 align:start position:0% got the le s protocol in progress right now<00:10:03.829> we<00:10:04.009> have<00:10:04.429> we're<00:10:05.300> probably<00:10:05.720> a<00:10:06.290> month<00:10:06.559> or 00:10:06.610 --> 00:10:06.620 align:start position:0% now we have we're probably a month or 00:10:06.620 --> 00:10:10.720 align:start position:0% now we have we're probably a month or two<00:10:07.009> from<00:10:07.550> a<00:10:08.259> very<00:10:09.259> alpha<00:10:09.589> stage<00:10:09.980> version<00:10:10.490> of 00:10:10.720 --> 00:10:10.730 align:start position:0% two from a very alpha stage version of 00:10:10.730 --> 00:10:12.280 align:start position:0% two from a very alpha stage version of this<00:10:10.879> that<00:10:11.149> can<00:10:11.329> sync<00:10:11.600> up<00:10:11.689> with<00:10:11.839> the<00:10:11.899> main<00:10:12.110> net 00:10:12.280 --> 00:10:12.290 align:start position:0% this that can sync up with the main net 00:10:12.290 --> 00:10:14.590 align:start position:0% this that can sync up with the main net and<00:10:13.129> run<00:10:13.339> as<00:10:13.490> a<00:10:13.519> light<00:10:13.730> client<00:10:14.059> so<00:10:14.179> we're<00:10:14.329> very 00:10:14.590 --> 00:10:14.600 align:start position:0% and run as a light client so we're very 00:10:14.600 --> 00:10:20.799 align:start position:0% and run as a light client so we're very close<00:10:14.839> on<00:10:15.019> this<00:10:16.059> and<00:10:17.059> and<00:10:17.540> it's<00:10:18.110> a<00:10:19.809> this 00:10:20.799 --> 00:10:20.809 align:start position:0% close on this and and it's a this 00:10:20.809 --> 00:10:23.110 align:start position:0% close on this and and it's a this project<00:10:21.470> is<00:10:21.709> intended<00:10:22.279> to<00:10:22.519> be<00:10:22.730> sort<00:10:22.970> of<00:10:22.999> a 00:10:23.110 --> 00:10:23.120 align:start position:0% project is intended to be sort of a 00:10:23.120 --> 00:10:24.369 align:start position:0% project is intended to be sort of a foundational<00:10:23.720> piece<00:10:23.899> to<00:10:24.110> the<00:10:24.199> Python 00:10:24.369 --> 00:10:24.379 align:start position:0% foundational piece to the Python 00:10:24.379 --> 00:10:27.009 align:start position:0% foundational piece to the Python ecosystem<00:10:25.129> um<00:10:25.339> I'm<00:10:26.240> very<00:10:26.300> proud<00:10:26.749> of<00:10:26.809> this 00:10:27.009 --> 00:10:27.019 align:start position:0% ecosystem um I'm very proud of this 00:10:27.019 --> 00:10:31.049 align:start position:0% ecosystem um I'm very proud of this library<00:10:27.259> and<00:10:27.800> I<00:10:28.100> and<00:10:28.459> I<00:10:28.550> think<00:10:28.790> it's<00:10:28.910> going<00:10:29.209> to 00:10:31.049 --> 00:10:31.059 align:start position:0% library and I and I think it's going to 00:10:31.059 --> 00:10:33.400 align:start position:0% library and I and I think it's going to be<00:10:32.059> one<00:10:32.240> of<00:10:32.329> the<00:10:32.420> cornerstone<00:10:32.899> pieces<00:10:33.019> that 00:10:33.400 --> 00:10:33.410 align:start position:0% be one of the cornerstone pieces that 00:10:33.410 --> 00:10:35.710 align:start position:0% be one of the cornerstone pieces that helps<00:10:33.679> bring<00:10:33.920> the<00:10:34.339> Python<00:10:34.699> ecosystem<00:10:35.299> up<00:10:35.449> to 00:10:35.710 --> 00:10:35.720 align:start position:0% helps bring the Python ecosystem up to 00:10:35.720 --> 00:10:39.009 align:start position:0% helps bring the Python ecosystem up to par<00:10:35.959> with<00:10:36.170> some<00:10:36.949> of<00:10:37.100> the<00:10:37.220> other<00:10:37.339> rika<00:10:37.929> III<00:10:38.929> AM 00:10:39.009 --> 00:10:39.019 align:start position:0% par with some of the other rika III AM 00:10:39.019 --> 00:10:41.530 align:start position:0% par with some of the other rika III AM tooling<00:10:39.470> out<00:10:39.709> there<00:10:40.009> and<00:10:40.699> that's<00:10:40.910> really<00:10:41.089> sort 00:10:41.530 --> 00:10:41.540 align:start position:0% tooling out there and that's really sort 00:10:41.540 --> 00:10:43.210 align:start position:0% tooling out there and that's really sort of<00:10:41.600> part<00:10:41.809> of<00:10:41.899> a<00:10:41.990> broader<00:10:42.230> goal<00:10:42.559> of<00:10:42.799> mine<00:10:42.980> which 00:10:43.210 --> 00:10:43.220 align:start position:0% of part of a broader goal of mine which 00:10:43.220 --> 00:10:46.329 align:start position:0% of part of a broader goal of mine which is<00:10:43.370> I<00:10:43.610> set<00:10:43.999> out<00:10:44.120> earlier<00:10:45.110> this<00:10:45.319> year<00:10:45.379> with<00:10:46.220> the 00:10:46.329 --> 00:10:46.339 align:start position:0% is I set out earlier this year with the 00:10:46.339 --> 00:10:48.489 align:start position:0% is I set out earlier this year with the sort<00:10:46.549> of<00:10:46.610> abstract<00:10:47.149> goal<00:10:47.360> of<00:10:47.660> maturing<00:10:48.199> all<00:10:48.350> of 00:10:48.489 --> 00:10:48.499 align:start position:0% sort of abstract goal of maturing all of 00:10:48.499 --> 00:10:50.799 align:start position:0% sort of abstract goal of maturing all of the<00:10:48.589> Python<00:10:48.949> tooling<00:10:49.420> because<00:10:50.420> we<00:10:50.569> needed 00:10:50.799 --> 00:10:50.809 align:start position:0% the Python tooling because we needed 00:10:50.809 --> 00:10:53.889 align:start position:0% the Python tooling because we needed better<00:10:51.079> tooling<00:10:51.589> and<00:10:51.889> and<00:10:52.369> and<00:10:52.759> so<00:10:53.689> many 00:10:53.889 --> 00:10:53.899 align:start position:0% better tooling and and and so many 00:10:53.899 --> 00:10:56.199 align:start position:0% better tooling and and and so many people<00:10:54.110> were<00:10:54.619> flocking<00:10:55.309> to<00:10:55.519> the<00:10:55.610> JavaScript 00:10:56.199 --> 00:10:56.209 align:start position:0% people were flocking to the JavaScript 00:10:56.209 --> 00:10:57.789 align:start position:0% people were flocking to the JavaScript stack<00:10:56.480> which<00:10:56.959> is<00:10:56.990> fine<00:10:57.350> because<00:10:57.589> the 00:10:57.789 --> 00:10:57.799 align:start position:0% stack which is fine because the 00:10:57.799 --> 00:10:59.470 align:start position:0% stack which is fine because the JavaScript<00:10:58.369> stack<00:10:58.549> has<00:10:58.699> been<00:10:58.910> the<00:10:59.059> superior 00:10:59.470 --> 00:10:59.480 align:start position:0% JavaScript stack has been the superior 00:10:59.480 --> 00:11:01.480 align:start position:0% JavaScript stack has been the superior stack<00:10:59.720> for<00:10:59.899> a<00:10:59.929> long<00:11:00.199> time<00:11:00.620> and<00:11:00.949> it's<00:11:01.069> a<00:11:01.189> great 00:11:01.480 --> 00:11:01.490 align:start position:0% stack for a long time and it's a great 00:11:01.490 --> 00:11:04.340 align:start position:0% stack for a long time and it's a great stack<00:11:01.899> but<00:11:02.899> people<00:11:03.139> need<00:11:03.259> choices<00:11:03.679> and<00:11:03.889> so 00:11:04.340 --> 00:11:04.350 align:start position:0% stack but people need choices and so 00:11:04.350 --> 00:11:06.500 align:start position:0% stack but people need choices and so I<00:11:04.440> wanted<00:11:05.040> to<00:11:05.190> set<00:11:05.400> out<00:11:05.490> to<00:11:05.790> actually<00:11:06.150> give 00:11:06.500 --> 00:11:06.510 align:start position:0% I wanted to set out to actually give 00:11:06.510 --> 00:11:09.410 align:start position:0% I wanted to set out to actually give them<00:11:06.750> those<00:11:07.170> choices<00:11:07.580> all<00:11:08.580> right<00:11:08.700> one<00:11:09.270> last 00:11:09.410 --> 00:11:09.420 align:start position:0% them those choices all right one last 00:11:09.420 --> 00:11:14.450 align:start position:0% them those choices all right one last note<00:11:09.630> Python<00:11:10.470> three<00:11:11.450> starting<00:11:12.450> in<00:11:12.540> 2018<00:11:13.460> we 00:11:14.450 --> 00:11:14.460 align:start position:0% note Python three starting in 2018 we 00:11:14.460 --> 00:11:16.850 align:start position:0% note Python three starting in 2018 we will<00:11:14.490> begin<00:11:15.180> dropping<00:11:15.720> support<00:11:16.080> for<00:11:16.350> Python<00:11:16.650> 2 00:11:16.850 --> 00:11:16.860 align:start position:0% will begin dropping support for Python 2 00:11:16.860 --> 00:11:18.770 align:start position:0% will begin dropping support for Python 2 so<00:11:17.310> if<00:11:17.400> you're<00:11:17.550> using<00:11:17.850> these<00:11:18.090> tools<00:11:18.360> and 00:11:18.770 --> 00:11:18.780 align:start position:0% so if you're using these tools and 00:11:18.780 --> 00:11:20.960 align:start position:0% so if you're using these tools and you're<00:11:18.960> using<00:11:19.110> Python<00:11:19.590> 2<00:11:19.830> you<00:11:20.610> need<00:11:20.820> to 00:11:20.960 --> 00:11:20.970 align:start position:0% you're using Python 2 you need to 00:11:20.970 --> 00:11:23.450 align:start position:0% you're using Python 2 you need to upgrade<00:11:21.680> because<00:11:22.680> they<00:11:22.800> are<00:11:22.860> going<00:11:23.070> to<00:11:23.190> break 00:11:23.450 --> 00:11:23.460 align:start position:0% upgrade because they are going to break 00:11:23.460 --> 00:11:27.410 align:start position:0% upgrade because they are going to break on<00:11:23.730> you<00:11:24.410> it's<00:11:25.410> time<00:11:25.970> you<00:11:26.970> need<00:11:27.120> to<00:11:27.270> upgrade 00:11:27.410 --> 00:11:27.420 align:start position:0% on you it's time you need to upgrade 00:11:27.420 --> 00:11:30.890 align:start position:0% on you it's time you need to upgrade your<00:11:27.630> code<00:11:27.990> base<00:11:29.300> Python<00:11:30.300> 3<00:11:30.480> is<00:11:30.600> great 00:11:30.890 --> 00:11:30.900 align:start position:0% your code base Python 3 is great 00:11:30.900 --> 00:11:33.740 align:start position:0% your code base Python 3 is great upgrading<00:11:31.860> to<00:11:32.010> it<00:11:32.190> is<00:11:32.430> very<00:11:32.460> easy<00:11:33.300> there<00:11:33.600> are<00:11:33.720> a 00:11:33.740 --> 00:11:33.750 align:start position:0% upgrading to it is very easy there are a 00:11:33.750 --> 00:11:35.570 align:start position:0% upgrading to it is very easy there are a ton<00:11:33.960> of<00:11:33.990> resources<00:11:34.350> out<00:11:34.620> there<00:11:34.650> we<00:11:35.550> are 00:11:35.570 --> 00:11:35.580 align:start position:0% ton of resources out there we are 00:11:35.580 --> 00:11:38.120 align:start position:0% ton of resources out there we are dropping<00:11:36.240> support<00:11:36.750> for<00:11:36.990> this<00:11:37.140> if<00:11:37.380> this<00:11:37.920> is<00:11:37.980> a 00:11:38.120 --> 00:11:38.130 align:start position:0% dropping support for this if this is a 00:11:38.130 --> 00:11:40.160 align:start position:0% dropping support for this if this is a problem<00:11:38.670> for<00:11:38.700> you<00:11:39.090> please<00:11:39.660> come<00:11:39.840> talk<00:11:39.990> to<00:11:40.050> me 00:11:40.160 --> 00:11:40.170 align:start position:0% problem for you please come talk to me 00:11:40.170 --> 00:11:43.610 align:start position:0% problem for you please come talk to me but<00:11:40.980> the<00:11:41.610> answer<00:11:41.970> is<00:11:42.270> likely<00:11:42.660> to<00:11:42.960> be<00:11:43.110> that<00:11:43.350> you 00:11:43.610 --> 00:11:43.620 align:start position:0% but the answer is likely to be that you 00:11:43.620 --> 00:11:46.040 align:start position:0% but the answer is likely to be that you need<00:11:43.800> to<00:11:43.890> upgrade<00:11:44.010> your<00:11:44.280> code<00:11:44.550> base<00:11:44.960> thank<00:11:45.960> you 00:11:46.040 --> 00:11:46.050 align:start position:0% need to upgrade your code base thank you 00:11:46.050 --> 00:11:53.940 align:start position:0% need to upgrade your code base thank you all<00:11:46.170> for<00:11:46.350> your<00:11:46.380> time 00:11:53.940 --> 00:11:53.950 align:start position:0% 00:11:53.950 --> 00:12:01.529 align:start position:0% [Music]