WEBVTT Kind: captions Language: en 00:00:09.190 --> 00:00:14.470 align:start position:0% [Music] 00:00:14.470 --> 00:00:14.480 align:start position:0% [Music] 00:00:14.480 --> 00:00:18.279 align:start position:0% [Music] thank<00:00:14.929> you<00:00:16.240> I'm<00:00:17.240> gonna<00:00:17.420> try<00:00:17.660> this<00:00:17.720> in<00:00:17.930> Spanish 00:00:18.279 --> 00:00:18.289 align:start position:0% thank you I'm gonna try this in Spanish 00:00:18.289 --> 00:00:19.679 align:start position:0% thank you I'm gonna try this in Spanish Bienvenue 00:00:19.679 --> 00:00:19.689 align:start position:0% Bienvenue 00:00:19.689 --> 00:00:22.510 align:start position:0% Bienvenue DEFCON<00:00:20.689> three<00:00:21.020> their<00:00:21.289> serum<00:00:21.710> foundation<00:00:22.310> I 00:00:22.510 --> 00:00:22.520 align:start position:0% DEFCON three their serum foundation I 00:00:22.520 --> 00:00:31.120 align:start position:0% DEFCON three their serum foundation I can<00:00:23.599> Mexico<00:00:24.230> I'm<00:00:29.289> we're<00:00:30.289> a<00:00:30.320> little<00:00:30.770> bit 00:00:31.120 --> 00:00:31.130 align:start position:0% can Mexico I'm we're a little bit 00:00:31.130 --> 00:00:32.950 align:start position:0% can Mexico I'm we're a little bit late<00:00:31.340> in<00:00:31.520> starting<00:00:31.640> so<00:00:32.180> I'm<00:00:32.300> probably<00:00:32.599> going 00:00:32.950 --> 00:00:32.960 align:start position:0% late in starting so I'm probably going 00:00:32.960 --> 00:00:35.139 align:start position:0% late in starting so I'm probably going to<00:00:33.050> go<00:00:33.170> right<00:00:33.410> into<00:00:33.649> the<00:00:34.100> etherium<00:00:34.910> team 00:00:35.139 --> 00:00:35.149 align:start position:0% to go right into the etherium team 00:00:35.149 --> 00:00:37.510 align:start position:0% to go right into the etherium team introduction<00:00:35.780> the<00:00:36.200> team<00:00:36.410> is<00:00:36.590> the<00:00:36.829> team<00:00:37.280> leads 00:00:37.510 --> 00:00:37.520 align:start position:0% introduction the team is the team leads 00:00:37.520 --> 00:00:40.060 align:start position:0% introduction the team is the team leads are<00:00:37.700> here<00:00:38.059> and<00:00:38.300> I<00:00:38.750> am<00:00:39.260> just<00:00:39.500> gonna<00:00:39.649> say<00:00:39.860> their 00:00:40.060 --> 00:00:40.070 align:start position:0% are here and I am just gonna say their 00:00:40.070 --> 00:00:41.910 align:start position:0% are here and I am just gonna say their names<00:00:40.309> first<00:00:40.700> and<00:00:41.059> then<00:00:41.180> have<00:00:41.329> them<00:00:41.510> come<00:00:41.540> up 00:00:41.910 --> 00:00:41.920 align:start position:0% names first and then have them come up 00:00:41.920 --> 00:00:45.130 align:start position:0% names first and then have them come up and<00:00:42.920> stand<00:00:43.219> beside<00:00:43.399> me<00:00:43.610> and<00:00:44.030> after<00:00:44.719> that<00:00:44.899> they 00:00:45.130 --> 00:00:45.140 align:start position:0% and stand beside me and after that they 00:00:45.140 --> 00:00:47.920 align:start position:0% and stand beside me and after that they will<00:00:45.260> each<00:00:45.530> come<00:00:45.770> up<00:00:45.829> and<00:00:46.190> do<00:00:46.490> a<00:00:46.930> quick 00:00:47.920 --> 00:00:47.930 align:start position:0% will each come up and do a quick 00:00:47.930 --> 00:00:49.420 align:start position:0% will each come up and do a quick introduction<00:00:48.320> of<00:00:48.590> themselves<00:00:48.710> and<00:00:49.340> the 00:00:49.420 --> 00:00:49.430 align:start position:0% introduction of themselves and the 00:00:49.430 --> 00:00:51.610 align:start position:0% introduction of themselves and the projects<00:00:49.970> that<00:00:50.000> they<00:00:50.330> that<00:00:50.990> they<00:00:51.140> lead<00:00:51.350> in<00:00:51.500> the 00:00:51.610 --> 00:00:51.620 align:start position:0% projects that they that they lead in the 00:00:51.620 --> 00:00:53.860 align:start position:0% projects that they that they lead in the efforts<00:00:51.920> that<00:00:52.040> they<00:00:52.130> lead<00:00:52.310> so<00:00:52.880> Vitalik 00:00:53.860 --> 00:00:53.870 align:start position:0% efforts that they lead so Vitalik 00:00:53.870 --> 00:01:03.190 align:start position:0% efforts that they lead so Vitalik butterin<00:01:00.550> chief<00:01:01.550> scientist<00:01:02.300> overseeing 00:01:03.190 --> 00:01:03.200 align:start position:0% butterin chief scientist overseeing 00:01:03.200 --> 00:01:11.500 align:start position:0% butterin chief scientist overseeing research<00:01:03.909> Martin<00:01:04.909> spender<00:01:07.630> security<00:01:08.630> lead 00:01:11.500 --> 00:01:11.510 align:start position:0% 00:01:11.510 --> 00:01:12.840 align:start position:0% [Applause] 00:01:12.840 --> 00:01:12.850 align:start position:0% [Applause] 00:01:12.850 --> 00:01:21.060 align:start position:0% [Applause] Peter<00:01:13.850> salade<00:01:14.360> you<00:01:16.210> go<00:01:17.210> team<00:01:17.570> lead 00:01:21.060 --> 00:01:21.070 align:start position:0% 00:01:21.070 --> 00:01:25.710 align:start position:0% jolt<00:01:21.880> tenfold<00:01:22.540> a<00:01:24.000> go<00:01:25.000> team 00:01:25.710 --> 00:01:25.720 align:start position:0% jolt tenfold a go team 00:01:25.720 --> 00:01:29.670 align:start position:0% jolt tenfold a go team like<00:01:26.230> client<00:01:26.710> lien<00:01:28.050> dr.<00:01:29.050> Christian<00:01:29.470> right 00:01:29.670 --> 00:01:29.680 align:start position:0% like client lien dr. Christian right 00:01:29.680 --> 00:01:38.190 align:start position:0% like client lien dr. Christian right beast<00:01:29.920> now<00:01:31.020> C++<00:01:32.020> solidity<00:01:32.560> lead<00:01:36.630> yo<00:01:37.630> Ichi<00:01:37.990> hit 00:01:38.190 --> 00:01:38.200 align:start position:0% beast now C++ solidity lead yo Ichi hit 00:01:38.200 --> 00:01:43.550 align:start position:0% beast now C++ solidity lead yo Ichi hit I<00:01:39.180> formal<00:01:40.180> verification<00:01:40.830> testing<00:01:41.830> research 00:01:43.550 --> 00:01:43.560 align:start position:0% I formal verification testing research 00:01:43.560 --> 00:01:46.040 align:start position:0% I formal verification testing research [Applause] 00:01:46.040 --> 00:01:46.050 align:start position:0% [Applause] 00:01:46.050 --> 00:01:50.670 align:start position:0% [Applause] Alec<00:01:47.050> spirit<00:01:47.410> saucy<00:01:48.030> he<00:01:49.030> was<00:01:49.270> um<00:01:49.570> a<00:01:49.810> theorem<00:01:50.320> jf 00:01:50.670 --> 00:01:50.680 align:start position:0% Alec spirit saucy he was um a theorem jf 00:01:50.680 --> 00:02:00.590 align:start position:0% Alec spirit saucy he was um a theorem jf and<00:01:51.280> solidity<00:01:54.119> yan<00:01:55.119> laro<00:01:55.680> remix 00:02:00.590 --> 00:02:00.600 align:start position:0% 00:02:00.600 --> 00:02:06.220 align:start position:0% Piper<00:02:01.290> Miriam<00:02:01.950> I<00:02:02.190> am 00:02:06.220 --> 00:02:06.230 align:start position:0% 00:02:06.230 --> 00:02:07.670 align:start position:0% [Applause] 00:02:07.670 --> 00:02:07.680 align:start position:0% [Applause] 00:02:07.680 --> 00:02:10.820 align:start position:0% [Applause] Victor<00:02:08.580> Tron<00:02:08.940> although<00:02:09.479> I<00:02:09.510> think<00:02:09.660> it's<00:02:09.990> dániel 00:02:10.820 --> 00:02:10.830 align:start position:0% Victor Tron although I think it's dániel 00:02:10.830 --> 00:02:12.520 align:start position:0% Victor Tron although I think it's dániel nagy<00:02:10.979> who<00:02:11.280> will<00:02:11.460> be<00:02:11.550> standing<00:02:12.000> in<00:02:12.120> for<00:02:12.330> him 00:02:12.520 --> 00:02:12.530 align:start position:0% nagy who will be standing in for him 00:02:12.530 --> 00:02:21.740 align:start position:0% nagy who will be standing in for him Daniel<00:02:14.750> swarm<00:02:15.750> team<00:02:19.610> flag<00:02:20.610> go<00:02:20.850> Huskies<00:02:21.120> what 00:02:21.740 --> 00:02:21.750 align:start position:0% Daniel swarm team flag go Huskies what 00:02:21.750 --> 00:02:25.490 align:start position:0% Daniel swarm team flag go Huskies what here<00:02:22.140> come<00:02:23.010> on<00:02:23.160> up<00:02:23.370> whisper<00:02:23.970> whisper<00:02:24.500> team 00:02:25.490 --> 00:02:25.500 align:start position:0% here come on up whisper whisper team 00:02:25.500 --> 00:02:30.320 align:start position:0% here come on up whisper whisper team lead<00:02:27.890> average<00:02:28.890> in<00:02:29.070> Fraga<00:02:29.400> representing<00:02:30.240> the 00:02:30.320 --> 00:02:30.330 align:start position:0% lead average in Fraga representing the 00:02:30.330 --> 00:02:37.880 align:start position:0% lead average in Fraga representing the mist<00:02:30.570> team<00:02:32.330> and<00:02:34.430> Fabien<00:02:35.430> Vogel<00:02:35.970> Shella<00:02:36.300> of<00:02:36.890> web 00:02:37.880 --> 00:02:37.890 align:start position:0% mist team and Fabien Vogel Shella of web 00:02:37.890 --> 00:02:51.730 align:start position:0% mist team and Fabien Vogel Shella of web 3-2<00:02:38.280> j/s<00:02:38.670> and<00:02:38.940> mist<00:02:41.810> okay<00:02:43.190> Vitalik<00:02:44.930> Vitalik 00:02:51.730 --> 00:02:51.740 align:start position:0% 00:02:51.740 --> 00:02:53.270 align:start position:0% okay 00:02:53.270 --> 00:02:53.280 align:start position:0% okay 00:02:53.280 --> 00:03:03.350 align:start position:0% okay hello<00:02:54.090> everyone<00:02:59.450> yeah<00:03:00.450> so<00:03:00.720> I<00:03:00.750> am<00:03:01.710> and<00:03:02.460> as<00:03:03.150> you 00:03:03.350 --> 00:03:03.360 align:start position:0% hello everyone yeah so I am and as you 00:03:03.360 --> 00:03:04.760 align:start position:0% hello everyone yeah so I am and as you all<00:03:03.510> know<00:03:03.660> the<00:03:03.930> founder<00:03:04.230> of<00:03:04.320> Ethier<00:03:04.590> iam 00:03:04.760 --> 00:03:04.770 align:start position:0% all know the founder of Ethier iam 00:03:04.770 --> 00:03:07.880 align:start position:0% all know the founder of Ethier iam project<00:03:05.250> and<00:03:05.640> the<00:03:06.090> chief<00:03:06.450> scientist<00:03:07.140> of<00:03:07.350> the 00:03:07.880 --> 00:03:07.890 align:start position:0% project and the chief scientist of the 00:03:07.890 --> 00:03:12.440 align:start position:0% project and the chief scientist of the etherium<00:03:08.310> foundation<00:03:08.880> and<00:03:09.260> I<00:03:11.450> basically 00:03:12.440 --> 00:03:12.450 align:start position:0% etherium foundation and I basically 00:03:12.450 --> 00:03:15.080 align:start position:0% etherium foundation and I basically spend<00:03:13.200> most<00:03:13.560> of<00:03:13.830> my<00:03:13.890> time<00:03:14.040> focusing<00:03:14.880> on 00:03:15.080 --> 00:03:15.090 align:start position:0% spend most of my time focusing on 00:03:15.090 --> 00:03:18.680 align:start position:0% spend most of my time focusing on research<00:03:15.780> problems<00:03:16.380> so<00:03:16.860> this<00:03:17.850> basically<00:03:18.420> has 00:03:18.680 --> 00:03:18.690 align:start position:0% research problems so this basically has 00:03:18.690 --> 00:03:21.170 align:start position:0% research problems so this basically has to<00:03:18.870> do<00:03:19.020> with<00:03:19.489> figuring<00:03:20.489> out<00:03:20.670> what<00:03:21.060> the 00:03:21.170 --> 00:03:21.180 align:start position:0% to do with figuring out what the 00:03:21.180 --> 00:03:23.150 align:start position:0% to do with figuring out what the etherium<00:03:21.600> protocol<00:03:22.080> might<00:03:22.440> look<00:03:22.650> like<00:03:22.709> in<00:03:23.070> the 00:03:23.150 --> 00:03:23.160 align:start position:0% etherium protocol might look like in the 00:03:23.160 --> 00:03:25.760 align:start position:0% etherium protocol might look like in the future<00:03:23.450> coming<00:03:24.450> up<00:03:24.690> with<00:03:24.930> thinking<00:03:25.530> about 00:03:25.760 --> 00:03:25.770 align:start position:0% future coming up with thinking about 00:03:25.770 --> 00:03:28.550 align:start position:0% future coming up with thinking about working<00:03:26.310> on<00:03:26.430> refining<00:03:26.840> various<00:03:27.840> advancements 00:03:28.550 --> 00:03:28.560 align:start position:0% working on refining various advancements 00:03:28.560 --> 00:03:30.949 align:start position:0% working on refining various advancements including<00:03:28.910> proof<00:03:29.910> of<00:03:30.060> stake<00:03:30.330> sharding 00:03:30.949 --> 00:03:30.959 align:start position:0% including proof of stake sharding 00:03:30.959 --> 00:03:33.520 align:start position:0% including proof of stake sharding scalability<00:03:31.800> solutions<00:03:32.340> privacy<00:03:32.880> solutions 00:03:33.520 --> 00:03:33.530 align:start position:0% scalability solutions privacy solutions 00:03:33.530 --> 00:03:36.020 align:start position:0% scalability solutions privacy solutions basically<00:03:34.530> things<00:03:34.860> that<00:03:35.040> will<00:03:35.160> take<00:03:35.400> etherium 00:03:36.020 --> 00:03:36.030 align:start position:0% basically things that will take etherium 00:03:36.030 --> 00:03:39.020 align:start position:0% basically things that will take etherium from<00:03:36.450> the<00:03:37.230> state<00:03:37.440> where<00:03:37.620> it<00:03:37.650> is<00:03:37.770> now<00:03:38.100> into 00:03:39.020 --> 00:03:39.030 align:start position:0% from the state where it is now into 00:03:39.030 --> 00:03:41.570 align:start position:0% from the state where it is now into something<00:03:39.870> that<00:03:40.050> actually<00:03:40.200> could<00:03:40.770> be<00:03:40.830> used<00:03:40.950> by 00:03:41.570 --> 00:03:41.580 align:start position:0% something that actually could be used by 00:03:41.580 --> 00:03:43.610 align:start position:0% something that actually could be used by decentralized<00:03:42.570> applications<00:03:42.750> that<00:03:43.410> would<00:03:43.500> be 00:03:43.610 --> 00:03:43.620 align:start position:0% decentralized applications that would be 00:03:43.620 --> 00:03:47.540 align:start position:0% decentralized applications that would be used<00:03:43.920> by<00:03:43.980> millions<00:03:44.280> of<00:03:44.520> people<00:03:44.580> so<00:03:45.560> and<00:03:46.560> I<00:03:46.830> the 00:03:47.540 --> 00:03:47.550 align:start position:0% used by millions of people so and I the 00:03:47.550 --> 00:03:50.930 align:start position:0% used by millions of people so and I the etherium<00:03:48.209> research<00:03:48.630> team<00:03:48.959> has<00:03:49.610> expanded<00:03:50.610> very 00:03:50.930 --> 00:03:50.940 align:start position:0% etherium research team has expanded very 00:03:50.940 --> 00:03:52.759 align:start position:0% etherium research team has expanded very significantly<00:03:51.630> in<00:03:51.870> the<00:03:51.989> last<00:03:52.019> a<00:03:52.410> few<00:03:52.590> months 00:03:52.759 --> 00:03:52.769 align:start position:0% significantly in the last a few months 00:03:52.769 --> 00:03:55.759 align:start position:0% significantly in the last a few months from<00:03:53.580> only<00:03:54.570> maybe<00:03:54.810> a<00:03:54.959> few<00:03:55.230> people<00:03:55.260> to 00:03:55.759 --> 00:03:55.769 align:start position:0% from only maybe a few people to 00:03:55.769 --> 00:03:57.770 align:start position:0% from only maybe a few people to something<00:03:56.220> like<00:03:56.340> 15<00:03:56.730> people<00:03:56.910> altogether<00:03:57.300> and 00:03:57.770 --> 00:03:57.780 align:start position:0% something like 15 people altogether and 00:03:57.780 --> 00:04:01.880 align:start position:0% something like 15 people altogether and it<00:03:58.230> will<00:03:58.380> only<00:03:58.920> continue<00:03:59.430> to<00:03:59.610> grow<00:03:59.930> so<00:04:00.930> and 00:04:01.880 --> 00:04:01.890 align:start position:0% it will only continue to grow so and 00:04:01.890 --> 00:04:04.280 align:start position:0% it will only continue to grow so and we'll<00:04:02.100> talk<00:04:02.310> about<00:04:02.640> much<00:04:03.300> more<00:04:03.630> of<00:04:03.900> what<00:04:04.110> we're 00:04:04.280 --> 00:04:04.290 align:start position:0% we'll talk about much more of what we're 00:04:04.290 --> 00:04:06.979 align:start position:0% we'll talk about much more of what we're doing<00:04:04.680> a<00:04:04.950> leader<00:04:05.730> over<00:04:06.150> the<00:04:06.239> over<00:04:06.630> the<00:04:06.660> course 00:04:06.979 --> 00:04:06.989 align:start position:0% doing a leader over the over the course 00:04:06.989 --> 00:04:09.320 align:start position:0% doing a leader over the over the course of<00:04:07.200> today<00:04:07.620> and<00:04:07.980> some<00:04:08.550> of<00:04:08.640> the<00:04:08.760> following<00:04:09.150> days 00:04:09.320 --> 00:04:09.330 align:start position:0% of today and some of the following days 00:04:09.330 --> 00:04:11.900 align:start position:0% of today and some of the following days but<00:04:10.080> some<00:04:10.470> of<00:04:10.590> the<00:04:10.709> highlights<00:04:11.220> include 00:04:11.900 --> 00:04:11.910 align:start position:0% but some of the highlights include 00:04:11.910 --> 00:04:16.220 align:start position:0% but some of the highlights include Casper<00:04:12.870> which<00:04:13.500> we<00:04:14.040> have<00:04:14.280> in<00:04:15.090> Vlad's<00:04:15.780> iam<00:04:16.019> fear 00:04:16.220 --> 00:04:16.230 align:start position:0% Casper which we have in Vlad's iam fear 00:04:16.230 --> 00:04:19.280 align:start position:0% Casper which we have in Vlad's iam fear carl<00:04:16.620> Forsch<00:04:17.010> and<00:04:17.690> changwu<00:04:18.690> who<00:04:18.900> is<00:04:19.019> going<00:04:19.230> to 00:04:19.280 --> 00:04:19.290 align:start position:0% carl Forsch and changwu who is going to 00:04:19.290 --> 00:04:20.960 align:start position:0% carl Forsch and changwu who is going to be<00:04:19.430> presenting 00:04:20.960 --> 00:04:20.970 align:start position:0% be presenting 00:04:20.970 --> 00:04:22.700 align:start position:0% be presenting about<00:04:21.209> an<00:04:21.360> hour<00:04:21.480> and<00:04:21.660> a<00:04:21.750> bit<00:04:21.900> right<00:04:22.110> right 00:04:22.700 --> 00:04:22.710 align:start position:0% about an hour and a bit right right 00:04:22.710 --> 00:04:23.990 align:start position:0% about an hour and a bit right right after<00:04:23.010> I<00:04:23.040> make<00:04:23.310> an<00:04:23.430> introduction<00:04:23.820> to 00:04:23.990 --> 00:04:24.000 align:start position:0% after I make an introduction to 00:04:24.000 --> 00:04:26.990 align:start position:0% after I make an introduction to aetherium<00:04:24.420> we<00:04:25.380> have<00:04:25.620> sharding<00:04:26.550> which<00:04:26.760> is<00:04:26.970> a 00:04:26.990 --> 00:04:27.000 align:start position:0% aetherium we have sharding which is a 00:04:27.000 --> 00:04:30.230 align:start position:0% aetherium we have sharding which is a scalability<00:04:27.690> solution<00:04:28.410> that<00:04:29.010> we<00:04:29.730> have<00:04:29.940> a 00:04:30.230 --> 00:04:30.240 align:start position:0% scalability solution that we have a 00:04:30.240 --> 00:04:32.420 align:start position:0% scalability solution that we have a couple<00:04:30.690> of<00:04:30.840> developers<00:04:31.350> starting<00:04:31.920> to<00:04:32.040> work<00:04:32.220> on 00:04:32.420 --> 00:04:32.430 align:start position:0% couple of developers starting to work on 00:04:32.430 --> 00:04:36.500 align:start position:0% couple of developers starting to work on as<00:04:32.580> well<00:04:32.760> and<00:04:33.720> we're<00:04:34.530> also<00:04:35.090> focusing<00:04:36.090> on<00:04:36.300> just 00:04:36.500 --> 00:04:36.510 align:start position:0% as well and we're also focusing on just 00:04:36.510 --> 00:04:38.750 align:start position:0% as well and we're also focusing on just various<00:04:37.170> smaller<00:04:37.530> protocol<00:04:38.130> improvements 00:04:38.750 --> 00:04:38.760 align:start position:0% various smaller protocol improvements 00:04:38.760 --> 00:04:41.090 align:start position:0% various smaller protocol improvements including<00:04:39.270> things<00:04:39.840> like<00:04:39.990> paralyze<00:04:40.590> ability 00:04:41.090 --> 00:04:41.100 align:start position:0% including things like paralyze ability 00:04:41.100 --> 00:04:43.610 align:start position:0% including things like paralyze ability cache<00:04:41.490> ability<00:04:42.030> something<00:04:42.810> you're<00:04:42.990> here 00:04:43.610 --> 00:04:43.620 align:start position:0% cache ability something you're here 00:04:43.620 --> 00:04:46.010 align:start position:0% cache ability something you're here about<00:04:43.740> called<00:04:44.100> stateless<00:04:44.340> clients<00:04:45.030> and<00:04:45.270> this 00:04:46.010 --> 00:04:46.020 align:start position:0% about called stateless clients and this 00:04:46.020 --> 00:04:49.250 align:start position:0% about called stateless clients and this various<00:04:46.590> other<00:04:47.090> smaller<00:04:48.090> but<00:04:48.480> very 00:04:49.250 --> 00:04:49.260 align:start position:0% various other smaller but very 00:04:49.260 --> 00:04:52.580 align:start position:0% various other smaller but very significant<00:04:50.960> improvements<00:04:51.960> to<00:04:51.990> the<00:04:52.200> etherium 00:04:52.580 --> 00:04:52.590 align:start position:0% significant improvements to the etherium 00:04:52.590 --> 00:04:56.930 align:start position:0% significant improvements to the etherium protocol<00:04:53.040> so<00:04:53.850> I<00:04:54.860> also<00:04:55.860> I<00:04:56.100> just<00:04:56.580> personally 00:04:56.930 --> 00:04:56.940 align:start position:0% protocol so I also I just personally 00:04:56.940 --> 00:05:00.530 align:start position:0% protocol so I also I just personally hope<00:04:57.330> that<00:04:57.740> everyone<00:04:58.740> enjoys<00:04:59.640> everything 00:05:00.530 --> 00:05:00.540 align:start position:0% hope that everyone enjoys everything 00:05:00.540 --> 00:05:02.870 align:start position:0% hope that everyone enjoys everything that<00:05:00.990> we're<00:05:01.590> going<00:05:01.740> to<00:05:01.890> present<00:05:02.040> over<00:05:02.790> the 00:05:02.870 --> 00:05:02.880 align:start position:0% that we're going to present over the 00:05:02.880 --> 00:05:06.460 align:start position:0% that we're going to present over the next<00:05:03.090> couple<00:05:03.300> of<00:05:03.480> days<00:05:03.660> and<00:05:04.160> you<00:05:05.160> know<00:05:05.250> just 00:05:06.460 --> 00:05:06.470 align:start position:0% next couple of days and you know just 00:05:06.470 --> 00:05:10.130 align:start position:0% next couple of days and you know just listen<00:05:07.470> and<00:05:07.950> I<00:05:08.010> see<00:05:08.430> ya<00:05:08.880> you<00:05:09.000> know<00:05:09.030> see<00:05:09.900> what's 00:05:10.130 --> 00:05:10.140 align:start position:0% listen and I see ya you know see what's 00:05:10.140 --> 00:05:12.650 align:start position:0% listen and I see ya you know see what's here<00:05:10.470> and<00:05:10.530> just<00:05:11.340> you<00:05:11.820> know<00:05:11.880> hope<00:05:12.240> there's 00:05:12.650 --> 00:05:12.660 align:start position:0% here and just you know hope there's 00:05:12.660 --> 00:05:14.060 align:start position:0% here and just you know hope there's something<00:05:12.900> that<00:05:13.080> you<00:05:13.169> find<00:05:13.320> interesting<00:05:13.530> so 00:05:14.060 --> 00:05:14.070 align:start position:0% something that you find interesting so 00:05:14.070 --> 00:05:17.060 align:start position:0% something that you find interesting so thank<00:05:14.400> you 00:05:17.060 --> 00:05:17.070 align:start position:0% 00:05:17.070 --> 00:05:21.689 align:start position:0% [Applause] 00:05:21.689 --> 00:05:21.699 align:start position:0% [Applause] 00:05:21.699 --> 00:05:25.540 align:start position:0% [Applause] hello<00:05:22.699> everyone<00:05:23.199> my<00:05:24.199> name<00:05:24.349> is<00:05:24.379> Martin<00:05:25.039> sander 00:05:25.540 --> 00:05:25.550 align:start position:0% hello everyone my name is Martin sander 00:05:25.550 --> 00:05:29.850 align:start position:0% hello everyone my name is Martin sander I<00:05:25.729> work<00:05:26.599> as<00:05:26.780> a<00:05:27.219> foundation<00:05:28.219> security<00:05:28.849> lead 00:05:29.850 --> 00:05:29.860 align:start position:0% I work as a foundation security lead 00:05:29.860 --> 00:05:32.950 align:start position:0% I work as a foundation security lead which<00:05:30.860> means<00:05:31.219> that<00:05:31.490> I'm<00:05:31.669> part<00:05:32.210> of<00:05:32.419> basically 00:05:32.950 --> 00:05:32.960 align:start position:0% which means that I'm part of basically 00:05:32.960 --> 00:05:35.469 align:start position:0% which means that I'm part of basically all<00:05:33.169> the<00:05:33.379> projects<00:05:34.099> and<00:05:34.400> trying<00:05:34.699> to<00:05:34.939> ensure 00:05:35.469 --> 00:05:35.479 align:start position:0% all the projects and trying to ensure 00:05:35.479 --> 00:05:39.550 align:start position:0% all the projects and trying to ensure that<00:05:35.509> the<00:05:36.169> security<00:05:37.240> aspects<00:05:38.349> someone<00:05:39.349> looks 00:05:39.550 --> 00:05:39.560 align:start position:0% that the security aspects someone looks 00:05:39.560 --> 00:05:41.920 align:start position:0% that the security aspects someone looks at<00:05:39.710> those<00:05:39.919> and<00:05:40.280> takes<00:05:40.460> care<00:05:40.729> of<00:05:40.759> those<00:05:41.030> during 00:05:41.920 --> 00:05:41.930 align:start position:0% at those and takes care of those during 00:05:41.930 --> 00:05:46.379 align:start position:0% at those and takes care of those during the<00:05:41.990> life<00:05:42.169> cycles<00:05:42.650> of<00:05:42.770> the<00:05:43.129> projects<00:05:43.639> and<00:05:44.889> also 00:05:46.379 --> 00:05:46.389 align:start position:0% the life cycles of the projects and also 00:05:46.389 --> 00:05:49.300 align:start position:0% the life cycles of the projects and also not<00:05:47.389> only<00:05:47.569> within<00:05:47.870> the<00:05:48.080> organization<00:05:48.800> but<00:05:49.280> I 00:05:49.300 --> 00:05:49.310 align:start position:0% not only within the organization but I 00:05:49.310 --> 00:05:53.350 align:start position:0% not only within the organization but I also<00:05:49.490> work<00:05:49.789> with<00:05:50.469> actors<00:05:51.469> in<00:05:52.310> the<00:05:52.490> ecosystem 00:05:53.350 --> 00:05:53.360 align:start position:0% also work with actors in the ecosystem 00:05:53.360 --> 00:05:55.839 align:start position:0% also work with actors in the ecosystem in<00:05:53.599> general<00:05:54.099> for<00:05:55.099> all<00:05:55.129> the<00:05:55.340> issues<00:05:55.639> concerning 00:05:55.839 --> 00:05:55.849 align:start position:0% in general for all the issues concerning 00:05:55.849 --> 00:05:58.809 align:start position:0% in general for all the issues concerning the<00:05:56.270> ethereum<00:05:57.080> Network<00:05:57.529> and<00:05:57.979> the<00:05:58.250> protocol 00:05:58.809 --> 00:05:58.819 align:start position:0% the ethereum Network and the protocol 00:05:58.819 --> 00:06:03.309 align:start position:0% the ethereum Network and the protocol and<00:06:01.090> security<00:06:02.090> in<00:06:02.150> its<00:06:02.360> various<00:06:02.629> forms<00:06:02.689> for 00:06:03.309 --> 00:06:03.319 align:start position:0% and security in its various forms for 00:06:03.319 --> 00:06:05.499 align:start position:0% and security in its various forms for all<00:06:03.379> these<00:06:03.500> participants<00:06:03.889> and<00:06:04.580> in<00:06:04.789> my<00:06:04.969> talk 00:06:05.499 --> 00:06:05.509 align:start position:0% all these participants and in my talk 00:06:05.509 --> 00:06:07.420 align:start position:0% all these participants and in my talk tomorrow<00:06:05.900> I'm<00:06:06.050> going<00:06:06.199> to<00:06:06.259> talk<00:06:06.439> a<00:06:06.469> bit<00:06:06.590> about<00:06:06.740> a 00:06:07.420 --> 00:06:07.430 align:start position:0% tomorrow I'm going to talk a bit about a 00:06:07.430 --> 00:06:09.459 align:start position:0% tomorrow I'm going to talk a bit about a retrospective<00:06:07.879> of<00:06:08.330> what's<00:06:08.659> happened<00:06:09.169> during 00:06:09.459 --> 00:06:09.469 align:start position:0% retrospective of what's happened during 00:06:09.469 --> 00:06:13.860 align:start position:0% retrospective of what's happened during the<00:06:09.680> last<00:06:09.889> year<00:06:10.340> and<00:06:11.409> how<00:06:12.409> we<00:06:12.469> have<00:06:12.800> improved 00:06:13.860 --> 00:06:13.870 align:start position:0% the last year and how we have improved 00:06:13.870 --> 00:06:16.779 align:start position:0% the last year and how we have improved and<00:06:14.870> in<00:06:15.110> what<00:06:15.289> ways<00:06:15.529> and<00:06:16.009> what<00:06:16.310> work<00:06:16.550> we've 00:06:16.779 --> 00:06:16.789 align:start position:0% and in what ways and what work we've 00:06:16.789 --> 00:06:19.420 align:start position:0% and in what ways and what work we've done<00:06:16.819> in<00:06:17.479> some<00:06:17.990> snippets<00:06:18.349> of<00:06:18.770> the<00:06:19.009> security 00:06:19.420 --> 00:06:19.430 align:start position:0% done in some snippets of the security 00:06:19.430 --> 00:06:19.839 align:start position:0% done in some snippets of the security field 00:06:19.839 --> 00:06:19.849 align:start position:0% field 00:06:19.849 --> 00:06:27.490 align:start position:0% field thank<00:06:20.449> you<00:06:25.810> hello<00:06:26.810> everybody 00:06:27.490 --> 00:06:27.500 align:start position:0% thank you hello everybody 00:06:27.500 --> 00:06:29.649 align:start position:0% thank you hello everybody my<00:06:28.069> name<00:06:28.190> is<00:06:28.279> Peter<00:06:28.490> you<00:06:28.940> probably<00:06:29.300> don't<00:06:29.479> want 00:06:29.649 --> 00:06:29.659 align:start position:0% my name is Peter you probably don't want 00:06:29.659 --> 00:06:31.350 align:start position:0% my name is Peter you probably don't want to<00:06:29.690> pronounce<00:06:29.990> my<00:06:30.139> family<00:06:30.469> name<00:06:30.620> and 00:06:31.350 --> 00:06:31.360 align:start position:0% to pronounce my family name and 00:06:31.360 --> 00:06:33.850 align:start position:0% to pronounce my family name and currently<00:06:32.360> I'm<00:06:32.479> the<00:06:32.539> team<00:06:33.080> lead<00:06:33.259> at<00:06:33.409> Goethe 00:06:33.850 --> 00:06:33.860 align:start position:0% currently I'm the team lead at Goethe 00:06:33.860 --> 00:06:36.550 align:start position:0% currently I'm the team lead at Goethe reom<00:06:34.069> and<00:06:34.810> just<00:06:35.810> I<00:06:35.930> would<00:06:36.050> like<00:06:36.169> to<00:06:36.259> give<00:06:36.409> you<00:06:36.529> a 00:06:36.550 --> 00:06:36.560 align:start position:0% reom and just I would like to give you a 00:06:36.560 --> 00:06:38.230 align:start position:0% reom and just I would like to give you a quick<00:06:36.860> recap<00:06:37.190> of<00:06:37.339> what<00:06:37.400> happened<00:06:37.909> behind<00:06:38.029> the 00:06:38.230 --> 00:06:38.240 align:start position:0% quick recap of what happened behind the 00:06:38.240 --> 00:06:40.209 align:start position:0% quick recap of what happened behind the scenes<00:06:38.330> over<00:06:38.810> the<00:06:38.900> last<00:06:39.050> year<00:06:39.349> since<00:06:39.680> Shanghai 00:06:40.209 --> 00:06:40.219 align:start position:0% scenes over the last year since Shanghai 00:06:40.219 --> 00:06:44.200 align:start position:0% scenes over the last year since Shanghai so<00:06:41.110> Goethe<00:06:42.110> had<00:06:42.349> quite<00:06:42.589> a<00:06:42.620> large<00:06:43.610> progression 00:06:44.200 --> 00:06:44.210 align:start position:0% so Goethe had quite a large progression 00:06:44.210 --> 00:06:46.540 align:start position:0% so Goethe had quite a large progression we<00:06:44.419> since<00:06:45.169> Shanghai<00:06:45.740> we<00:06:45.919> actually<00:06:46.250> released 00:06:46.540 --> 00:06:46.550 align:start position:0% we since Shanghai we actually released 00:06:46.550 --> 00:06:48.610 align:start position:0% we since Shanghai we actually released mobile<00:06:46.940> libraries<00:06:47.360> for<00:06:47.539> Android<00:06:47.810> and<00:06:47.960> iOS<00:06:48.080> for 00:06:48.610 --> 00:06:48.620 align:start position:0% mobile libraries for Android and iOS for 00:06:48.620 --> 00:06:50.950 align:start position:0% mobile libraries for Android and iOS for etherium<00:06:49.129> we<00:06:49.580> have<00:06:49.759> been<00:06:49.969> working<00:06:50.210> and<00:06:50.659> you 00:06:50.950 --> 00:06:50.960 align:start position:0% etherium we have been working and you 00:06:50.960 --> 00:06:52.869 align:start position:0% etherium we have been working and you will<00:06:51.139> actually<00:06:51.289> be<00:06:51.469> able<00:06:51.589> to<00:06:51.830> really<00:06:52.099> hear 00:06:52.869 --> 00:06:52.879 align:start position:0% will actually be able to really hear 00:06:52.879 --> 00:06:54.999 align:start position:0% will actually be able to really hear more<00:06:53.120> about<00:06:53.150> these<00:06:53.599> on<00:06:53.839> the<00:06:53.990> status<00:06:54.379> talk 00:06:54.999 --> 00:06:55.009 align:start position:0% more about these on the status talk 00:06:55.009 --> 00:06:56.829 align:start position:0% more about these on the status talk tomorrow<00:06:55.219> and<00:06:55.490> the<00:06:55.909> Wally's<00:06:56.210> talk<00:06:56.509> tomorrow 00:06:56.829 --> 00:06:56.839 align:start position:0% tomorrow and the Wally's talk tomorrow 00:06:56.839 --> 00:07:00.249 align:start position:0% tomorrow and the Wally's talk tomorrow then<00:06:57.830> we<00:06:58.159> have<00:06:58.610> actually<00:06:59.150> developed<00:06:59.750> a<00:07:00.110> new 00:07:00.249 --> 00:07:00.259 align:start position:0% then we have actually developed a new 00:07:00.259 --> 00:07:02.170 align:start position:0% then we have actually developed a new peer-to-peer<00:07:00.830> discovery<00:07:01.430> protocol<00:07:01.849> to<00:07:02.029> aid 00:07:02.170 --> 00:07:02.180 align:start position:0% peer-to-peer discovery protocol to aid 00:07:02.180 --> 00:07:04.240 align:start position:0% peer-to-peer discovery protocol to aid in<00:07:02.509> private<00:07:02.990> networks<00:07:03.379> and<00:07:03.620> test<00:07:03.830> networks 00:07:04.240 --> 00:07:04.250 align:start position:0% in private networks and test networks 00:07:04.250 --> 00:07:06.490 align:start position:0% in private networks and test networks Felix<00:07:04.759> will<00:07:04.939> give<00:07:05.240> a<00:07:05.270> talk<00:07:05.509> about<00:07:05.779> this<00:07:06.020> again 00:07:06.490 --> 00:07:06.500 align:start position:0% Felix will give a talk about this again 00:07:06.500 --> 00:07:10.329 align:start position:0% Felix will give a talk about this again tomorrow<00:07:06.680> from<00:07:07.189> 9<00:07:07.370> o'clock<00:07:07.490> 9:15<00:07:08.449> 3:50<00:07:09.339> we 00:07:10.329 --> 00:07:10.339 align:start position:0% tomorrow from 9 o'clock 9:15 3:50 we 00:07:10.339 --> 00:07:11.860 align:start position:0% tomorrow from 9 o'clock 9:15 3:50 we have<00:07:10.460> been<00:07:10.610> working<00:07:10.819> and<00:07:11.120> released<00:07:11.539> a<00:07:11.719> light 00:07:11.860 --> 00:07:11.870 align:start position:0% have been working and released a light 00:07:11.870 --> 00:07:13.779 align:start position:0% have been working and released a light client<00:07:12.319> version<00:07:12.680> 1<00:07:12.830> and<00:07:12.860> version<00:07:13.039> 2<00:07:13.400> short 00:07:13.779 --> 00:07:13.789 align:start position:0% client version 1 and version 2 short 00:07:13.789 --> 00:07:16.959 align:start position:0% client version 1 and version 2 short will<00:07:14.000> probably<00:07:14.330> detail<00:07:14.689> this<00:07:14.870> in<00:07:15.169> a<00:07:15.289> moment<00:07:15.969> we 00:07:16.959 --> 00:07:16.969 align:start position:0% will probably detail this in a moment we 00:07:16.969 --> 00:07:20.409 align:start position:0% will probably detail this in a moment we have<00:07:17.180> and<00:07:18.020> we<00:07:18.589> did<00:07:18.740> a<00:07:18.770> lot<00:07:19.009> of<00:07:19.089> things<00:07:20.089> to<00:07:20.270> help 00:07:20.409 --> 00:07:20.419 align:start position:0% have and we did a lot of things to help 00:07:20.419 --> 00:07:22.059 align:start position:0% have and we did a lot of things to help developers<00:07:20.960> for<00:07:21.169> example<00:07:21.529> we<00:07:21.620> supported 00:07:22.059 --> 00:07:22.069 align:start position:0% developers for example we supported 00:07:22.069 --> 00:07:23.110 align:start position:0% developers for example we supported configuration<00:07:22.639> files 00:07:23.110 --> 00:07:23.120 align:start position:0% configuration files 00:07:23.120 --> 00:07:25.869 align:start position:0% configuration files you<00:07:23.509> probably<00:07:23.719> remember<00:07:24.259> last<00:07:24.710> or<00:07:25.279> that<00:07:25.310> at 00:07:25.869 --> 00:07:25.879 align:start position:0% you probably remember last or that at 00:07:25.879 --> 00:07:27.129 align:start position:0% you probably remember last or that at the<00:07:26.000> beginning<00:07:26.270> of<00:07:26.389> this<00:07:26.539> year<00:07:26.750> where<00:07:26.990> the 00:07:27.129 --> 00:07:27.139 align:start position:0% the beginning of this year where the 00:07:27.139 --> 00:07:29.230 align:start position:0% the beginning of this year where the robson<00:07:27.469> test<00:07:27.680> network<00:07:28.039> fell<00:07:28.219> apart<00:07:28.520> and<00:07:28.789> thus 00:07:29.230 --> 00:07:29.240 align:start position:0% robson test network fell apart and thus 00:07:29.240 --> 00:07:31.209 align:start position:0% robson test network fell apart and thus we<00:07:29.449> actually<00:07:29.810> introduced<00:07:30.259> proof<00:07:31.099> of 00:07:31.209 --> 00:07:31.219 align:start position:0% we actually introduced proof of 00:07:31.219 --> 00:07:32.860 align:start position:0% we actually introduced proof of Authority<00:07:31.669> protocol<00:07:32.089> in<00:07:32.209> to<00:07:32.330> go<00:07:32.449> with<00:07:32.599> theorem 00:07:32.860 --> 00:07:32.870 align:start position:0% Authority protocol in to go with theorem 00:07:32.870 --> 00:07:33.610 align:start position:0% Authority protocol in to go with theorem to<00:07:32.990> have<00:07:33.139> a 00:07:33.610 --> 00:07:33.620 align:start position:0% to have a 00:07:33.620 --> 00:07:36.280 align:start position:0% to have a test<00:07:33.860> Network<00:07:34.160> that's<00:07:34.340> not<00:07:34.460> attackable<00:07:35.290> with 00:07:36.280 --> 00:07:36.290 align:start position:0% test Network that's not attackable with 00:07:36.290 --> 00:07:38.440 align:start position:0% test Network that's not attackable with a<00:07:36.530> pluggable<00:07:36.860> consensus<00:07:37.460> model<00:07:37.820> that 00:07:38.440 --> 00:07:38.450 align:start position:0% a pluggable consensus model that 00:07:38.450 --> 00:07:40.570 align:start position:0% a pluggable consensus model that actually<00:07:39.350> has<00:07:39.500> functioned<00:07:39.980> really<00:07:40.190> well<00:07:40.370> for 00:07:40.570 --> 00:07:40.580 align:start position:0% actually has functioned really well for 00:07:40.580 --> 00:07:43.060 align:start position:0% actually has functioned really well for the<00:07:40.700> last<00:07:40.850> year<00:07:41.420> or<00:07:41.600> so<00:07:41.630> and<00:07:42.050> we're<00:07:42.590> already<00:07:42.770> at 00:07:43.060 --> 00:07:43.070 align:start position:0% the last year or so and we're already at 00:07:43.070 --> 00:07:45.490 align:start position:0% the last year or so and we're already at like<00:07:43.190> 1<00:07:43.430> million<00:07:43.610> and<00:07:43.820> something<00:07:44.500> we're 00:07:45.490 --> 00:07:45.500 align:start position:0% like 1 million and something we're 00:07:45.500 --> 00:07:48.820 align:start position:0% like 1 million and something we're really<00:07:45.530> proud<00:07:45.740> of<00:07:46.160> that<00:07:46.310> one<00:07:47.560> swarm<00:07:48.560> had<00:07:48.800> a 00:07:48.820 --> 00:07:48.830 align:start position:0% really proud of that one swarm had a 00:07:48.830 --> 00:07:52.240 align:start position:0% really proud of that one swarm had a huge<00:07:50.350> never<00:07:51.350> mind<00:07:51.620> I'll<00:07:51.740> leave<00:07:51.920> it<00:07:52.040> to<00:07:52.070> the 00:07:52.240 --> 00:07:52.250 align:start position:0% huge never mind I'll leave it to the 00:07:52.250 --> 00:07:55.270 align:start position:0% huge never mind I'll leave it to the swarm<00:07:52.490> people<00:07:53.380> it's<00:07:54.380> simpler 00:07:55.270 --> 00:07:55.280 align:start position:0% swarm people it's simpler 00:07:55.280 --> 00:07:57.640 align:start position:0% swarm people it's simpler we<00:07:55.640> introduced<00:07:56.060> a<00:07:56.240> support<00:07:57.140> for<00:07:57.380> hardware 00:07:57.640 --> 00:07:57.650 align:start position:0% we introduced a support for hardware 00:07:57.650 --> 00:07:58.960 align:start position:0% we introduced a support for hardware wallets<00:07:58.130> for<00:07:58.220> example<00:07:58.550> the<00:07:58.640> ledger<00:07:58.820> and 00:07:58.960 --> 00:07:58.970 align:start position:0% wallets for example the ledger and 00:07:58.970 --> 00:08:00.760 align:start position:0% wallets for example the ledger and tracer<00:07:59.330> which<00:07:59.600> we're<00:07:59.780> kind<00:08:00.020> of<00:08:00.110> proud<00:08:00.290> of<00:08:00.350> and 00:08:00.760 --> 00:08:00.770 align:start position:0% tracer which we're kind of proud of and 00:08:00.770 --> 00:08:02.830 align:start position:0% tracer which we're kind of proud of and just<00:08:01.670> to<00:08:01.760> give<00:08:01.880> you<00:08:01.970> a<00:08:02.030> sense<00:08:02.360> of<00:08:02.540> what<00:08:02.690> we're 00:08:02.830 --> 00:08:02.840 align:start position:0% just to give you a sense of what we're 00:08:02.840 --> 00:08:04.420 align:start position:0% just to give you a sense of what we're currently<00:08:02.990> working<00:08:03.410> on<00:08:03.650> we<00:08:03.920> kind<00:08:04.130> of<00:08:04.250> feel 00:08:04.420 --> 00:08:04.430 align:start position:0% currently working on we kind of feel 00:08:04.430 --> 00:08:07.570 align:start position:0% currently working on we kind of feel that<00:08:04.930> one<00:08:05.930> of<00:08:06.050> the<00:08:06.170> biggest<00:08:06.500> issues<00:08:06.830> at<00:08:07.340> least 00:08:07.570 --> 00:08:07.580 align:start position:0% that one of the biggest issues at least 00:08:07.580 --> 00:08:09.100 align:start position:0% that one of the biggest issues at least for<00:08:07.730> GUI<00:08:07.910> theorem<00:08:08.330> is<00:08:08.480> performance 00:08:09.100 --> 00:08:09.110 align:start position:0% for GUI theorem is performance 00:08:09.110 --> 00:08:11.770 align:start position:0% for GUI theorem is performance bottlenecks<00:08:09.560> currently<00:08:10.040> so<00:08:10.610> we've<00:08:11.090> put<00:08:11.600> quite 00:08:11.770 --> 00:08:11.780 align:start position:0% bottlenecks currently so we've put quite 00:08:11.780 --> 00:08:13.780 align:start position:0% bottlenecks currently so we've put quite a<00:08:11.840> lot<00:08:11.990> of<00:08:12.140> work<00:08:12.320> into<00:08:12.800> on<00:08:13.190> this<00:08:13.370> front<00:08:13.610> for 00:08:13.780 --> 00:08:13.790 align:start position:0% a lot of work into on this front for 00:08:13.790 --> 00:08:15.400 align:start position:0% a lot of work into on this front for example<00:08:14.180> we've<00:08:14.330> reduced<00:08:14.690> the<00:08:14.780> database<00:08:15.170> size 00:08:15.400 --> 00:08:15.410 align:start position:0% example we've reduced the database size 00:08:15.410 --> 00:08:17.860 align:start position:0% example we've reduced the database size by<00:08:15.680> about<00:08:15.890> 50%<00:08:16.280> we<00:08:17.240> reduce<00:08:17.630> the 00:08:17.860 --> 00:08:17.870 align:start position:0% by about 50% we reduce the 00:08:17.870 --> 00:08:21.820 align:start position:0% by about 50% we reduce the synchronization<00:08:18.680> bandwidth<00:08:19.040> by<00:08:19.220> 60%<00:08:20.500> we<00:08:21.500> kind 00:08:21.820 --> 00:08:21.830 align:start position:0% synchronization bandwidth by 60% we kind 00:08:21.830 --> 00:08:24.490 align:start position:0% synchronization bandwidth by 60% we kind of<00:08:22.150> introduced<00:08:23.150> long<00:08:23.360> or<00:08:23.840> improved<00:08:24.290> long 00:08:24.490 --> 00:08:24.500 align:start position:0% of introduced long or improved long 00:08:24.500 --> 00:08:25.780 align:start position:0% of introduced long or improved long filtering<00:08:24.980> by<00:08:25.100> two<00:08:25.160> orders<00:08:25.580> of<00:08:25.670> magnitude 00:08:25.780 --> 00:08:25.790 align:start position:0% filtering by two orders of magnitude 00:08:25.790 --> 00:08:29.290 align:start position:0% filtering by two orders of magnitude from<00:08:26.630> minutes<00:08:27.170> to<00:08:27.260> seconds<00:08:27.770> and<00:08:28.300> currently 00:08:29.290 --> 00:08:29.300 align:start position:0% from minutes to seconds and currently 00:08:29.300 --> 00:08:31.360 align:start position:0% from minutes to seconds and currently we're<00:08:29.450> actually<00:08:29.600> working<00:08:29.960> on<00:08:30.140> in<00:08:30.370> revamping 00:08:31.360 --> 00:08:31.370 align:start position:0% we're actually working on in revamping 00:08:31.370 --> 00:08:33.340 align:start position:0% we're actually working on in revamping the<00:08:31.520> entire<00:08:31.760> sync<00:08:32.060> mechanism<00:08:32.570> so<00:08:32.750> hopefully 00:08:33.340 --> 00:08:33.350 align:start position:0% the entire sync mechanism so hopefully 00:08:33.350 --> 00:08:35.620 align:start position:0% the entire sync mechanism so hopefully we<00:08:33.590> could<00:08:33.830> get<00:08:34.070> a<00:08:34.310> node<00:08:34.610> up<00:08:34.790> and<00:08:35.030> running<00:08:35.330> in 00:08:35.620 --> 00:08:35.630 align:start position:0% we could get a node up and running in 00:08:35.630 --> 00:08:38.440 align:start position:0% we could get a node up and running in maybe<00:08:36.380> two<00:08:36.830> minutes<00:08:37.370> but<00:08:37.790> maybe<00:08:38.030> that's<00:08:38.210> a<00:08:38.360> bit 00:08:38.440 --> 00:08:38.450 align:start position:0% maybe two minutes but maybe that's a bit 00:08:38.450 --> 00:08:42.850 align:start position:0% maybe two minutes but maybe that's a bit too<00:08:38.900> optimistic<00:08:39.080> but<00:08:39.620> that's<00:08:39.830> our<00:08:40.040> ago<00:08:40.310> and<00:08:41.860> so 00:08:42.850 --> 00:08:42.860 align:start position:0% too optimistic but that's our ago and so 00:08:42.860 --> 00:08:44.500 align:start position:0% too optimistic but that's our ago and so that's<00:08:43.070> a<00:08:43.280> really<00:08:43.580> really<00:08:43.610> quick<00:08:44.000> recap<00:08:44.450> of 00:08:44.500 --> 00:08:44.510 align:start position:0% that's a really really quick recap of 00:08:44.510 --> 00:08:47.740 align:start position:0% that's a really really quick recap of the<00:08:44.690> last<00:08:45.110> year<00:08:45.800> and<00:08:45.980> if<00:08:46.580> any<00:08:46.850> of<00:08:47.060> you<00:08:47.210> have<00:08:47.540> any 00:08:47.740 --> 00:08:47.750 align:start position:0% the last year and if any of you have any 00:08:47.750 --> 00:08:49.030 align:start position:0% the last year and if any of you have any suggestions<00:08:48.290> or<00:08:48.350> anything<00:08:48.560> you<00:08:48.860> would<00:08:49.010> like 00:08:49.030 --> 00:08:49.040 align:start position:0% suggestions or anything you would like 00:08:49.040 --> 00:08:50.680 align:start position:0% suggestions or anything you would like to<00:08:49.370> see<00:08:49.550> goey<00:08:49.730> theorem<00:08:50.090> support<00:08:50.450> in<00:08:50.570> the 00:08:50.680 --> 00:08:50.690 align:start position:0% to see goey theorem support in the 00:08:50.690 --> 00:08:53.050 align:start position:0% to see goey theorem support in the following<00:08:50.960> years<00:08:51.350> then<00:08:51.620> feel<00:08:51.980> free<00:08:52.190> to<00:08:52.220> find 00:08:53.050 --> 00:08:53.060 align:start position:0% following years then feel free to find 00:08:53.060 --> 00:08:54.670 align:start position:0% following years then feel free to find me<00:08:53.240> and<00:08:53.420> tell<00:08:53.750> me<00:08:53.900> what<00:08:54.020> your<00:08:54.170> pain<00:08:54.320> point<00:08:54.560> is 00:08:54.670 --> 00:08:54.680 align:start position:0% me and tell me what your pain point is 00:08:54.680 --> 00:08:57.810 align:start position:0% me and tell me what your pain point is thank<00:08:55.040> you 00:08:57.810 --> 00:08:57.820 align:start position:0% 00:08:57.820 --> 00:09:03.579 align:start position:0% [Applause] 00:09:03.579 --> 00:09:03.589 align:start position:0% 00:09:03.589 --> 00:09:06.649 align:start position:0% hello<00:09:04.589> everyone<00:09:04.979> I<00:09:05.249> am<00:09:05.309> George<00:09:05.939> featherly 00:09:06.649 --> 00:09:06.659 align:start position:0% hello everyone I am George featherly 00:09:06.659 --> 00:09:10.069 align:start position:0% hello everyone I am George featherly I'm<00:09:07.039> also<00:09:08.039> working<00:09:08.399> with<00:09:08.669> the<00:09:09.179> Foundation's 00:09:10.069 --> 00:09:10.079 align:start position:0% I'm also working with the Foundation's 00:09:10.079 --> 00:09:12.259 align:start position:0% I'm also working with the Foundation's Goethe<00:09:10.559> reom<00:09:10.769> team<00:09:11.009> I'm<00:09:11.489> mostly<00:09:11.879> responsible 00:09:12.259 --> 00:09:12.269 align:start position:0% Goethe reom team I'm mostly responsible 00:09:12.269 --> 00:09:15.799 align:start position:0% Goethe reom team I'm mostly responsible for<00:09:13.220> the<00:09:14.220> light<00:09:14.489> deterrence<00:09:15.029> a<00:09:15.179> protocol<00:09:15.509> and 00:09:15.799 --> 00:09:15.809 align:start position:0% for the light deterrence a protocol and 00:09:15.809 --> 00:09:19.369 align:start position:0% for the light deterrence a protocol and the<00:09:15.929> goal<00:09:16.289> ID<00:09:16.529> client<00:09:17.239> this<00:09:18.239> year<00:09:18.449> has<00:09:18.689> mostly 00:09:19.369 --> 00:09:19.379 align:start position:0% the goal ID client this year has mostly 00:09:19.379 --> 00:09:21.499 align:start position:0% the goal ID client this year has mostly been<00:09:19.499> about<00:09:20.099> under<00:09:20.549> the<00:09:20.669> hood<00:09:20.819> developments 00:09:21.499 --> 00:09:21.509 align:start position:0% been about under the hood developments 00:09:21.509 --> 00:09:24.469 align:start position:0% been about under the hood developments as<00:09:21.629> Peter<00:09:21.839> already<00:09:22.439> mentioned<00:09:23.069> we<00:09:23.279> have<00:09:24.209> just 00:09:24.469 --> 00:09:24.479 align:start position:0% as Peter already mentioned we have just 00:09:24.479 --> 00:09:27.379 align:start position:0% as Peter already mentioned we have just recently<00:09:24.749> merged<00:09:25.739> the<00:09:26.129> second<00:09:26.999> version<00:09:27.179> of 00:09:27.379 --> 00:09:27.389 align:start position:0% recently merged the second version of 00:09:27.389 --> 00:09:29.179 align:start position:0% recently merged the second version of the<00:09:27.629> NES<00:09:28.259> protocol<00:09:28.709> and<00:09:28.859> its<00:09:28.949> implementation 00:09:29.179 --> 00:09:29.189 align:start position:0% the NES protocol and its implementation 00:09:29.189 --> 00:09:32.809 align:start position:0% the NES protocol and its implementation in<00:09:29.999> our<00:09:30.119> code<00:09:30.389> base<00:09:30.569> we<00:09:31.470> are<00:09:31.499> soon<00:09:32.249> going<00:09:32.279> to 00:09:32.809 --> 00:09:32.819 align:start position:0% in our code base we are soon going to 00:09:32.819 --> 00:09:35.119 align:start position:0% in our code base we are soon going to have<00:09:33.029> a<00:09:33.059> lot<00:09:33.509> of<00:09:33.539> nice<00:09:33.809> new<00:09:34.199> features<00:09:34.919> and 00:09:35.119 --> 00:09:35.129 align:start position:0% have a lot of nice new features and 00:09:35.129 --> 00:09:37.279 align:start position:0% have a lot of nice new features and performance<00:09:35.329> improvements<00:09:36.329> we<00:09:36.869> are<00:09:36.959> going<00:09:37.199> to 00:09:37.279 --> 00:09:37.289 align:start position:0% performance improvements we are going to 00:09:37.289 --> 00:09:40.659 align:start position:0% performance improvements we are going to have<00:09:37.439> a<00:09:37.470> fast<00:09:38.009> lock<00:09:38.339> searching<00:09:38.819> and<00:09:39.409> and 00:09:40.659 --> 00:09:40.669 align:start position:0% have a fast lock searching and and 00:09:40.669 --> 00:09:43.460 align:start position:0% have a fast lock searching and and ultralight<00:09:41.669> clients<00:09:42.239> and<00:09:42.470> transactional 00:09:43.460 --> 00:09:43.470 align:start position:0% ultralight clients and transactional 00:09:43.470 --> 00:09:45.379 align:start position:0% ultralight clients and transactional status<00:09:43.859> which<00:09:44.009> we've<00:09:44.220> also<00:09:44.399> feature<00:09:44.789> wise<00:09:45.119> we 00:09:45.379 --> 00:09:45.389 align:start position:0% status which we've also feature wise we 00:09:45.389 --> 00:09:47.319 align:start position:0% status which we've also feature wise we are<00:09:45.419> already<00:09:45.809> quite<00:09:46.169> good<00:09:46.470> right<00:09:47.009> now<00:09:47.220> the 00:09:47.319 --> 00:09:47.329 align:start position:0% are already quite good right now the 00:09:47.329 --> 00:09:50.749 align:start position:0% are already quite good right now the biggest<00:09:48.329> challenge<00:09:48.629> is<00:09:49.139> to<00:09:49.470> expand<00:09:50.220> the<00:09:50.609> team 00:09:50.749 --> 00:09:50.759 align:start position:0% biggest challenge is to expand the team 00:09:50.759 --> 00:09:52.699 align:start position:0% biggest challenge is to expand the team with<00:09:51.059> more<00:09:51.209> people<00:09:51.599> to<00:09:51.809> work<00:09:52.019> on<00:09:52.259> the<00:09:52.409> light 00:09:52.699 --> 00:09:52.709 align:start position:0% with more people to work on the light 00:09:52.709 --> 00:09:55.460 align:start position:0% with more people to work on the light client<00:09:53.189> and<00:09:53.459> work<00:09:54.209> out<00:09:54.449> all<00:09:54.749> the<00:09:54.989> important 00:09:55.460 --> 00:09:55.470 align:start position:0% client and work out all the important 00:09:55.470 --> 00:09:58.309 align:start position:0% client and work out all the important details<00:09:55.619> and<00:09:56.039> finally<00:09:56.729> bring<00:09:57.569> this<00:09:57.869> project 00:09:58.309 --> 00:09:58.319 align:start position:0% details and finally bring this project 00:09:58.319 --> 00:10:00.739 align:start position:0% details and finally bring this project out<00:09:58.470> of<00:09:58.769> the<00:09:59.189> experimental<00:10:00.029> research<00:10:00.179> stage 00:10:00.739 --> 00:10:00.749 align:start position:0% out of the experimental research stage 00:10:00.749 --> 00:10:07.650 align:start position:0% out of the experimental research stage and<00:10:01.019> make<00:10:01.619> it<00:10:01.769> a<00:10:01.859> real<00:10:01.979> product<00:10:04.309> thank<00:10:05.309> you 00:10:07.650 --> 00:10:07.660 align:start position:0% 00:10:07.660 --> 00:10:12.380 align:start position:0% [Applause] 00:10:12.380 --> 00:10:12.390 align:start position:0% [Applause] 00:10:12.390 --> 00:10:14.269 align:start position:0% [Applause] hello<00:10:13.080> my<00:10:13.290> name<00:10:13.410> is<00:10:13.440> Christina<00:10:13.860> at<00:10:13.950> least<00:10:14.130> now 00:10:14.269 --> 00:10:14.279 align:start position:0% hello my name is Christina at least now 00:10:14.279 --> 00:10:19.040 align:start position:0% hello my name is Christina at least now I<00:10:14.690> yeah<00:10:15.690> I<00:10:15.720> participate<00:10:16.620> in<00:10:17.450> several<00:10:18.450> projects 00:10:19.040 --> 00:10:19.050 align:start position:0% I yeah I participate in several projects 00:10:19.050 --> 00:10:21.410 align:start position:0% I yeah I participate in several projects and<00:10:19.230> among<00:10:19.440> them<00:10:19.620> are<00:10:19.830> the<00:10:20.310> etherion<00:10:20.940> C++ 00:10:21.410 --> 00:10:21.420 align:start position:0% and among them are the etherion C++ 00:10:21.420 --> 00:10:25.720 align:start position:0% and among them are the etherion C++ client<00:10:21.839> the<00:10:22.830> solidity<00:10:23.190> project<00:10:23.839> project<00:10:24.839> and 00:10:25.720 --> 00:10:25.730 align:start position:0% client the solidity project project and 00:10:25.730 --> 00:10:31.160 align:start position:0% client the solidity project project and yeah<00:10:26.730> also<00:10:27.120> some<00:10:27.270> CK<00:10:27.690> snarks<00:10:28.110> and<00:10:30.080> over<00:10:31.080> the 00:10:31.160 --> 00:10:31.170 align:start position:0% yeah also some CK snarks and over the 00:10:31.170 --> 00:10:34.970 align:start position:0% yeah also some CK snarks and over the last<00:10:31.290> year<00:10:31.680> we<00:10:32.990> succeeded<00:10:33.990> to<00:10:34.110> get<00:10:34.290> CPP<00:10:34.770> if<00:10:34.860> you 00:10:34.970 --> 00:10:34.980 align:start position:0% last year we succeeded to get CPP if you 00:10:34.980 --> 00:10:38.440 align:start position:0% last year we succeeded to get CPP if you went<00:10:35.130> back<00:10:35.220> in<00:10:35.370> shape<00:10:35.580> and<00:10:36.920> Andre<00:10:37.920> and<00:10:38.070> Pavel 00:10:38.440 --> 00:10:38.450 align:start position:0% went back in shape and Andre and Pavel 00:10:38.450 --> 00:10:41.630 align:start position:0% went back in shape and Andre and Pavel mostly<00:10:39.450> worked<00:10:39.660> on<00:10:39.779> that<00:10:39.899> to<00:10:40.110> get<00:10:40.310> get<00:10:41.310> it<00:10:41.430> sync 00:10:41.630 --> 00:10:41.640 align:start position:0% mostly worked on that to get get it sync 00:10:41.640 --> 00:10:45.199 align:start position:0% mostly worked on that to get get it sync again<00:10:41.850> to<00:10:41.970> the<00:10:42.060> against<00:10:42.660> the<00:10:42.750> maenette<00:10:43.050> so<00:10:44.209> c+ 00:10:45.199 --> 00:10:45.209 align:start position:0% again to the against the maenette so c+ 00:10:45.209 --> 00:10:46.970 align:start position:0% again to the against the maenette so c+ theorem<00:10:45.720> if<00:10:45.959> you<00:10:46.230> remember<00:10:46.470> is<00:10:46.529> always<00:10:46.680> useful 00:10:46.970 --> 00:10:46.980 align:start position:0% theorem if you remember is always useful 00:10:46.980 --> 00:10:50.780 align:start position:0% theorem if you remember is always useful to<00:10:47.220> have<00:10:47.370> a<00:10:47.520> third<00:10:48.950> validating<00:10:49.950> client<00:10:50.370> to 00:10:50.780 --> 00:10:50.790 align:start position:0% to have a third validating client to 00:10:50.790 --> 00:10:54.880 align:start position:0% to have a third validating client to check<00:10:51.420> the<00:10:52.170> tests<00:10:52.560> and<00:10:52.709> consensus<00:10:53.130> rules<00:10:53.370> and 00:10:54.880 --> 00:10:54.890 align:start position:0% check the tests and consensus rules and 00:10:54.890 --> 00:10:57.680 align:start position:0% check the tests and consensus rules and we<00:10:55.890> now<00:10:56.220> implement<00:10:56.640> it<00:10:56.730> snapshot<00:10:57.089> sync<00:10:57.360> so<00:10:57.600> you 00:10:57.680 --> 00:10:57.690 align:start position:0% we now implement it snapshot sync so you 00:10:57.690 --> 00:11:01.430 align:start position:0% we now implement it snapshot sync so you can<00:10:58.050> sync<00:10:58.770> it<00:10:58.860> really<00:10:59.190> fast<00:10:59.399> and<00:10:59.700> we're<00:11:00.440> yeah 00:11:01.430 --> 00:11:01.440 align:start position:0% can sync it really fast and we're yeah 00:11:01.440 --> 00:11:03.620 align:start position:0% can sync it really fast and we're yeah removing<00:11:02.339> some<00:11:03.000> for<00:11:03.209> the<00:11:03.270> last<00:11:03.420> race 00:11:03.620 --> 00:11:03.630 align:start position:0% removing some for the last race 00:11:03.630 --> 00:11:05.780 align:start position:0% removing some for the last race condition<00:11:04.050> bugs<00:11:04.230> so<00:11:04.560> I<00:11:04.589> think<00:11:04.920> C++<00:11:05.580> is<00:11:05.700> Tea 00:11:05.780 --> 00:11:05.790 align:start position:0% condition bugs so I think C++ is Tea 00:11:05.790 --> 00:11:09.730 align:start position:0% condition bugs so I think C++ is Tea Room<00:11:05.970> should<00:11:06.149> be<00:11:06.209> usable<00:11:06.899> again<00:11:06.990> soon<00:11:07.440> and 00:11:09.730 --> 00:11:09.740 align:start position:0% 00:11:09.740 --> 00:11:12.139 align:start position:0% Greg<00:11:10.740> Colvin<00:11:11.070> is<00:11:11.160> also<00:11:11.399> working<00:11:11.610> on<00:11:11.880> an 00:11:12.139 --> 00:11:12.149 align:start position:0% Greg Colvin is also working on an 00:11:12.149 --> 00:11:13.760 align:start position:0% Greg Colvin is also working on an improvement<00:11:12.510> of<00:11:12.720> the<00:11:12.899> etherium<00:11:13.500> virtual 00:11:13.760 --> 00:11:13.770 align:start position:0% improvement of the etherium virtual 00:11:13.770 --> 00:11:16.220 align:start position:0% improvement of the etherium virtual machine<00:11:14.010> as<00:11:14.339> part<00:11:14.610> of<00:11:14.640> the<00:11:14.730> C++<00:11:15.180> project<00:11:15.600> which 00:11:16.220 --> 00:11:16.230 align:start position:0% machine as part of the C++ project which 00:11:16.230 --> 00:11:18.769 align:start position:0% machine as part of the C++ project which is<00:11:16.350> called<00:11:16.470> EVM<00:11:16.860> 1.5<00:11:17.670> and<00:11:18.000> he<00:11:18.330> will<00:11:18.450> give<00:11:18.750> a 00:11:18.769 --> 00:11:18.779 align:start position:0% is called EVM 1.5 and he will give a 00:11:18.779 --> 00:11:20.480 align:start position:0% is called EVM 1.5 and he will give a talk<00:11:19.080> at<00:11:19.290> some<00:11:19.440> point<00:11:19.680> but<00:11:19.800> I<00:11:19.860> don't<00:11:20.339> remember 00:11:20.480 --> 00:11:20.490 align:start position:0% talk at some point but I don't remember 00:11:20.490 --> 00:11:24.940 align:start position:0% talk at some point but I don't remember which<00:11:20.730> talk<00:11:20.970> which<00:11:21.330> date<00:11:21.510> will<00:11:21.690> be<00:11:21.810> on<00:11:21.930> and 00:11:24.940 --> 00:11:24.950 align:start position:0% 00:11:24.950 --> 00:11:31.150 align:start position:0% yeah<00:11:25.950> in<00:11:27.350> in<00:11:28.350> the<00:11:28.650> solidity<00:11:28.980> project<00:11:29.930> we<00:11:30.930> also 00:11:31.150 --> 00:11:31.160 align:start position:0% yeah in in the solidity project we also 00:11:31.160 --> 00:11:34.040 align:start position:0% yeah in in the solidity project we also did<00:11:32.160> some<00:11:32.779> improvements 00:11:34.040 --> 00:11:34.050 align:start position:0% did some improvements 00:11:34.050 --> 00:11:37.250 align:start position:0% did some improvements I<00:11:34.080> guess<00:11:34.800> the<00:11:35.790> there<00:11:36.089> will<00:11:36.270> be<00:11:36.300> talks<00:11:36.959> to 00:11:37.250 --> 00:11:37.260 align:start position:0% I guess the there will be talks to 00:11:37.260 --> 00:11:40.519 align:start position:0% I guess the there will be talks to explain<00:11:38.160> that<00:11:38.550> in<00:11:39.300> detail<00:11:39.360> and<00:11:39.959> especially 00:11:40.519 --> 00:11:40.529 align:start position:0% explain that in detail and especially 00:11:40.529 --> 00:11:42.880 align:start position:0% explain that in detail and especially we're<00:11:40.890> adding<00:11:41.250> a<00:11:41.339> new<00:11:41.550> form<00:11:41.940> verification 00:11:42.880 --> 00:11:42.890 align:start position:0% we're adding a new form verification 00:11:42.890 --> 00:11:45.590 align:start position:0% we're adding a new form verification framework<00:11:43.890> where<00:11:44.250> I<00:11:44.279> will<00:11:44.640> talk<00:11:45.000> about<00:11:45.060> on<00:11:45.570> day 00:11:45.590 --> 00:11:45.600 align:start position:0% framework where I will talk about on day 00:11:45.600 --> 00:11:46.850 align:start position:0% framework where I will talk about on day 3<00:11:46.410> I<00:11:46.440> think 00:11:46.850 --> 00:11:46.860 align:start position:0% 3 I think 00:11:46.860 --> 00:11:51.470 align:start position:0% 3 I think and<00:11:48.230> then<00:11:49.490> another<00:11:50.490> subject<00:11:50.790> I'm<00:11:51.120> working<00:11:51.390> on 00:11:51.470 --> 00:11:51.480 align:start position:0% and then another subject I'm working on 00:11:51.480 --> 00:11:56.300 align:start position:0% and then another subject I'm working on is<00:11:51.779> SDK<00:11:52.320> snarks<00:11:52.709> which<00:11:52.980> adds<00:11:54.709> privacy<00:11:55.709> but 00:11:56.300 --> 00:11:56.310 align:start position:0% is SDK snarks which adds privacy but 00:11:56.310 --> 00:11:59.510 align:start position:0% is SDK snarks which adds privacy but also<00:11:57.709> improve<00:11:58.709> verification<00:11:59.430> of 00:11:59.510 --> 00:11:59.520 align:start position:0% also improve verification of 00:11:59.520 --> 00:12:01.960 align:start position:0% also improve verification of computations<00:12:00.150> and<00:12:00.560> there<00:12:01.560> will<00:12:01.680> be<00:12:01.709> a 00:12:01.960 --> 00:12:01.970 align:start position:0% computations and there will be a 00:12:01.970 --> 00:12:05.750 align:start position:0% computations and there will be a separate<00:12:03.260> breakout<00:12:04.260> session<00:12:04.650> about<00:12:04.920> CAA 00:12:05.750 --> 00:12:05.760 align:start position:0% separate breakout session about CAA 00:12:05.760 --> 00:12:09.620 align:start position:0% separate breakout session about CAA snarks<00:12:06.089> and<00:12:06.170> also<00:12:07.170> a<00:12:07.620> talk<00:12:08.279> by<00:12:08.550> Jakob<00:12:09.180> Eva<00:12:09.390> hat 00:12:09.620 --> 00:12:09.630 align:start position:0% snarks and also a talk by Jakob Eva hat 00:12:09.630 --> 00:12:14.350 align:start position:0% snarks and also a talk by Jakob Eva hat I<00:12:10.200> think<00:12:10.680> on<00:12:10.770> day<00:12:10.890> 2<00:12:11.540> where<00:12:12.540> he<00:12:12.690> will<00:12:12.899> present<00:12:13.589> a 00:12:14.350 --> 00:12:14.360 align:start position:0% I think on day 2 where he will present a 00:12:14.360 --> 00:12:17.510 align:start position:0% I think on day 2 where he will present a framework<00:12:15.360> to<00:12:15.839> make<00:12:16.079> CK<00:12:16.529> snarks<00:12:16.920> more<00:12:17.190> easily 00:12:17.510 --> 00:12:17.520 align:start position:0% framework to make CK snarks more easily 00:12:17.520 --> 00:12:19.190 align:start position:0% framework to make CK snarks more easily accessible<00:12:18.390> and 00:12:19.190 --> 00:12:19.200 align:start position:0% accessible and 00:12:19.200 --> 00:12:30.889 align:start position:0% accessible and usable<00:12:19.910> thanks<00:12:28.070> my<00:12:29.070> name<00:12:29.610> is<00:12:29.790> yuuichi<00:12:30.089> Hawaii 00:12:30.889 --> 00:12:30.899 align:start position:0% usable thanks my name is yuuichi Hawaii 00:12:30.899 --> 00:12:35.829 align:start position:0% usable thanks my name is yuuichi Hawaii I<00:12:31.610> write<00:12:32.610> proofs<00:12:33.420> like<00:12:33.920> mathematical<00:12:34.920> proofs 00:12:35.829 --> 00:12:35.839 align:start position:0% I write proofs like mathematical proofs 00:12:35.839 --> 00:12:40.160 align:start position:0% I write proofs like mathematical proofs sometimes<00:12:36.839> I<00:12:37.050> prove<00:12:37.560> my<00:12:37.920> own<00:12:38.310> wallet<00:12:39.269> correct 00:12:40.160 --> 00:12:40.170 align:start position:0% sometimes I prove my own wallet correct 00:12:40.170 --> 00:12:44.360 align:start position:0% sometimes I prove my own wallet correct and<00:12:40.620> I<00:12:41.070> put<00:12:41.279> my<00:12:41.490> own<00:12:41.850> it<00:12:42.360> own<00:12:42.930> it<00:12:42.959> and<00:12:43.560> ask 00:12:44.360 --> 00:12:44.370 align:start position:0% and I put my own it own it and ask 00:12:44.370 --> 00:12:47.269 align:start position:0% and I put my own it own it and ask people<00:12:44.760> to<00:12:44.790> attack<00:12:45.120> it<00:12:45.360> and<00:12:45.570> steal<00:12:45.930> my<00:12:46.260> Itza 00:12:47.269 --> 00:12:47.279 align:start position:0% people to attack it and steal my Itza 00:12:47.279 --> 00:12:51.850 align:start position:0% people to attack it and steal my Itza because<00:12:49.399> mathematicians<00:12:50.399> proving<00:12:50.910> something 00:12:51.850 --> 00:12:51.860 align:start position:0% because mathematicians proving something 00:12:51.860 --> 00:12:55.009 align:start position:0% because mathematicians proving something doesn't<00:12:52.860> necessarily<00:12:53.570> guarantee<00:12:54.570> anything 00:12:55.009 --> 00:12:55.019 align:start position:0% doesn't necessarily guarantee anything 00:12:55.019 --> 00:12:58.040 align:start position:0% doesn't necessarily guarantee anything about<00:12:55.350> reality<00:12:56.329> to<00:12:57.329> know<00:12:57.449> the<00:12:57.570> reality<00:12:57.810> of 00:12:58.040 --> 00:12:58.050 align:start position:0% about reality to know the reality of 00:12:58.050 --> 00:13:01.460 align:start position:0% about reality to know the reality of SRAM<00:12:58.290> I<00:12:58.850> follow<00:12:59.850> the<00:13:00.209> metropolis<00:13:00.600> changes 00:13:01.460 --> 00:13:01.470 align:start position:0% SRAM I follow the metropolis changes 00:13:01.470 --> 00:13:05.110 align:start position:0% SRAM I follow the metropolis changes carefully<00:13:02.370> I<00:13:02.870> translated<00:13:03.870> the<00:13:04.050> Zips 00:13:05.110 --> 00:13:05.120 align:start position:0% carefully I translated the Zips 00:13:05.120 --> 00:13:07.670 align:start position:0% carefully I translated the Zips improvement<00:13:06.120> proposals<00:13:06.690> into<00:13:07.230> the 00:13:07.670 --> 00:13:07.680 align:start position:0% improvement proposals into the 00:13:07.680 --> 00:13:10.060 align:start position:0% improvement proposals into the specification<00:13:08.160> document<00:13:08.910> a<00:13:09.029> yellow<00:13:09.209> paper<00:13:09.510> I 00:13:10.060 --> 00:13:10.070 align:start position:0% specification document a yellow paper I 00:13:10.070 --> 00:13:14.120 align:start position:0% specification document a yellow paper I work<00:13:11.070> on<00:13:11.370> generating<00:13:12.029> test<00:13:12.360> cases<00:13:13.130> with 00:13:14.120 --> 00:13:14.130 align:start position:0% work on generating test cases with 00:13:14.130 --> 00:13:18.259 align:start position:0% work on generating test cases with Demetri<00:13:14.910> Martin's<00:13:15.779> Mindy<00:13:16.310> Jared<00:13:17.310> Guido 00:13:18.259 --> 00:13:18.269 align:start position:0% Demetri Martin's Mindy Jared Guido 00:13:18.269 --> 00:13:21.920 align:start position:0% Demetri Martin's Mindy Jared Guido Casey<00:13:18.779> I<00:13:19.550> also<00:13:20.550> work<00:13:20.880> on<00:13:21.149> the<00:13:21.209> ship<00:13:21.690> last 00:13:21.920 --> 00:13:21.930 align:start position:0% Casey I also work on the ship last 00:13:21.930 --> 00:13:24.889 align:start position:0% Casey I also work on the ship last breaths<00:13:22.880> framework<00:13:23.880> for<00:13:24.300> generating<00:13:24.779> these 00:13:24.889 --> 00:13:24.899 align:start position:0% breaths framework for generating these 00:13:24.899 --> 00:13:30.250 align:start position:0% breaths framework for generating these test<00:13:25.199> cases<00:13:27.560> on<00:13:28.560> the<00:13:28.709> sidelines<00:13:29.160> I<00:13:29.430> also<00:13:29.760> work 00:13:30.250 --> 00:13:30.260 align:start position:0% test cases on the sidelines I also work 00:13:30.260 --> 00:13:33.560 align:start position:0% test cases on the sidelines I also work improving<00:13:31.260> caspo<00:13:32.070> correct<00:13:32.970> I<00:13:33.269> talked<00:13:33.540> about 00:13:33.560 --> 00:13:33.570 align:start position:0% improving caspo correct I talked about 00:13:33.570 --> 00:13:35.720 align:start position:0% improving caspo correct I talked about that<00:13:34.110> this<00:13:34.769> afternoon 00:13:35.720 --> 00:13:35.730 align:start position:0% that this afternoon 00:13:35.730 --> 00:13:39.830 align:start position:0% that this afternoon thank<00:13:36.180> you 00:13:39.830 --> 00:13:39.840 align:start position:0% 00:13:39.840 --> 00:13:44.660 align:start position:0% [Applause] 00:13:44.660 --> 00:13:44.670 align:start position:0% [Applause] 00:13:44.670 --> 00:13:47.939 align:start position:0% [Applause] hi<00:13:45.670> my<00:13:45.880> name<00:13:46.029> is<00:13:46.060> Alex<00:13:46.389> barrack<00:13:46.600> sassy<00:13:46.990> or<00:13:47.170> x''k 00:13:47.939 --> 00:13:47.949 align:start position:0% hi my name is Alex barrack sassy or x''k 00:13:47.949 --> 00:13:50.430 align:start position:0% hi my name is Alex barrack sassy or x''k on<00:13:48.160> github<00:13:48.639> and<00:13:48.970> I'm<00:13:49.720> involved<00:13:50.019> with<00:13:50.170> three 00:13:50.430 --> 00:13:50.440 align:start position:0% on github and I'm involved with three 00:13:50.440 --> 00:13:53.639 align:start position:0% on github and I'm involved with three projects<00:13:51.130> the<00:13:51.339> solidity<00:13:52.029> atrium<00:13:53.019> Jas<00:13:53.350> and<00:13:53.560> he 00:13:53.639 --> 00:13:53.649 align:start position:0% projects the solidity atrium Jas and he 00:13:53.649 --> 00:13:55.560 align:start position:0% projects the solidity atrium Jas and he was<00:13:53.829> him<00:13:54.009> so<00:13:54.490> I'm<00:13:54.550> going<00:13:54.699> to<00:13:54.759> tell<00:13:55.120> you<00:13:55.240> a<00:13:55.269> bit 00:13:55.560 --> 00:13:55.570 align:start position:0% was him so I'm going to tell you a bit 00:13:55.570 --> 00:13:58.259 align:start position:0% was him so I'm going to tell you a bit of<00:13:55.690> each<00:13:55.990> of<00:13:56.230> them<00:13:56.410> and<00:13:56.589> so<00:13:57.459> solidity<00:13:57.910> just 00:13:58.259 --> 00:13:58.269 align:start position:0% of each of them and so solidity just 00:13:58.269 --> 00:14:01.559 align:start position:0% of each of them and so solidity just some<00:13:59.170> of<00:13:59.290> the<00:13:59.350> facts<00:13:59.769> from<00:13:59.889> the<00:13:59.980> last<00:14:00.250> year<00:14:00.569> we 00:14:01.559 --> 00:14:01.569 align:start position:0% some of the facts from the last year we 00:14:01.569 --> 00:14:03.960 align:start position:0% some of the facts from the last year we had<00:14:01.779> probably<00:14:02.110> 300<00:14:02.889> entries<00:14:03.699> on<00:14:03.880> the 00:14:03.960 --> 00:14:03.970 align:start position:0% had probably 300 entries on the 00:14:03.970 --> 00:14:07.559 align:start position:0% had probably 300 entries on the changelog<00:14:04.449> 15<00:14:05.350> releases<00:14:06.069> and<00:14:06.339> not<00:14:07.209> that<00:14:07.389> many 00:14:07.559 --> 00:14:07.569 align:start position:0% changelog 15 releases and not that many 00:14:07.569 --> 00:14:09.749 align:start position:0% changelog 15 releases and not that many bugs<00:14:07.810> or<00:14:08.500> at<00:14:08.889> least<00:14:09.100> not<00:14:09.339> many<00:14:09.490> bugs 00:14:09.749 --> 00:14:09.759 align:start position:0% bugs or at least not many bugs 00:14:09.759 --> 00:14:13.800 align:start position:0% bugs or at least not many bugs discovered<00:14:10.769> I<00:14:11.769> guess<00:14:12.399> the<00:14:12.639> major<00:14:13.029> changes<00:14:13.600> we 00:14:13.800 --> 00:14:13.810 align:start position:0% discovered I guess the major changes we 00:14:13.810 --> 00:14:18.480 align:start position:0% discovered I guess the major changes we had<00:14:14.019> from<00:14:14.970> Shanghai<00:14:16.079> includes<00:14:17.279> most<00:14:18.279> of<00:14:18.399> you 00:14:18.480 --> 00:14:18.490 align:start position:0% had from Shanghai includes most of you 00:14:18.490 --> 00:14:19.920 align:start position:0% had from Shanghai includes most of you have<00:14:18.639> seen<00:14:18.670> all<00:14:18.940> of<00:14:18.970> these<00:14:19.149> but<00:14:19.420> includes<00:14:19.750> like 00:14:19.920 --> 00:14:19.930 align:start position:0% have seen all of these but includes like 00:14:19.930 --> 00:14:22.829 align:start position:0% have seen all of these but includes like function<00:14:20.380> types<00:14:20.649> contract<00:14:21.579> metadata<00:14:22.000> which 00:14:22.829 --> 00:14:22.839 align:start position:0% function types contract metadata which 00:14:22.839 --> 00:14:26.460 align:start position:0% function types contract metadata which helps<00:14:23.230> verifying<00:14:23.860> contract<00:14:24.690> and<00:14:25.690> we<00:14:26.350> have 00:14:26.460 --> 00:14:26.470 align:start position:0% helps verifying contract and we have 00:14:26.470 --> 00:14:28.800 align:start position:0% helps verifying contract and we have also<00:14:26.620> added<00:14:26.860> a<00:14:27.279> new<00:14:27.910> compiler<00:14:28.240> interface 00:14:28.800 --> 00:14:28.810 align:start position:0% also added a new compiler interface 00:14:28.810 --> 00:14:31.650 align:start position:0% also added a new compiler interface which<00:14:29.470> would<00:14:29.680> help<00:14:29.889> in<00:14:30.660> retrieving 00:14:31.650 --> 00:14:31.660 align:start position:0% which would help in retrieving 00:14:31.660 --> 00:14:33.480 align:start position:0% which would help in retrieving everything<00:14:32.259> from<00:14:32.410> the<00:14:32.500> compiler<00:14:32.860> in<00:14:33.250> a<00:14:33.339> much 00:14:33.480 --> 00:14:33.490 align:start position:0% everything from the compiler in a much 00:14:33.490 --> 00:14:35.850 align:start position:0% everything from the compiler in a much better<00:14:33.639> way<00:14:33.759> than<00:14:34.060> it<00:14:34.149> was<00:14:34.329> before<00:14:34.529> now<00:14:35.529> for 00:14:35.850 --> 00:14:35.860 align:start position:0% better way than it was before now for 00:14:35.860 --> 00:14:39.660 align:start position:0% better way than it was before now for the<00:14:36.100> next<00:14:36.670> year<00:14:37.089> we<00:14:38.050> really<00:14:38.350> work<00:14:38.560> on<00:14:38.829> a<00:14:39.160> new 00:14:39.660 --> 00:14:39.670 align:start position:0% the next year we really work on a new 00:14:39.670 --> 00:14:42.360 align:start position:0% the next year we really work on a new intermediate<00:14:40.300> language<00:14:40.860> which<00:14:41.860> I<00:14:42.040> will<00:14:42.250> gonna 00:14:42.360 --> 00:14:42.370 align:start position:0% intermediate language which I will gonna 00:14:42.370 --> 00:14:44.790 align:start position:0% intermediate language which I will gonna have<00:14:42.579> a<00:14:42.610> talk<00:14:42.819> about<00:14:43.209> after<00:14:43.990> after<00:14:44.589> lunch 00:14:44.790 --> 00:14:44.800 align:start position:0% have a talk about after after lunch 00:14:44.800 --> 00:14:47.790 align:start position:0% have a talk about after after lunch today<00:14:45.100> and<00:14:45.490> as<00:14:46.360> Christian<00:14:47.139> has<00:14:47.260> mentioned<00:14:47.440> we 00:14:47.790 --> 00:14:47.800 align:start position:0% today and as Christian has mentioned we 00:14:47.800 --> 00:14:49.650 align:start position:0% today and as Christian has mentioned we have<00:14:48.100> a<00:14:48.430> new<00:14:49.209> form<00:14:49.449> of<00:14:49.510> verification 00:14:49.650 --> 00:14:49.660 align:start position:0% have a new form of verification 00:14:49.660 --> 00:14:52.949 align:start position:0% have a new form of verification framework<00:14:50.490> called<00:14:51.490> an<00:14:51.760> SMT<00:14:52.389> checker<00:14:52.690> and 00:14:52.949 --> 00:14:52.959 align:start position:0% framework called an SMT checker and 00:14:52.959 --> 00:14:55.199 align:start position:0% framework called an SMT checker and that's<00:14:53.709> almost<00:14:53.949> ready<00:14:54.190> as<00:14:54.339> well<00:14:54.550> but<00:14:55.000> this<00:14:55.149> is 00:14:55.199 --> 00:14:55.209 align:start position:0% that's almost ready as well but this is 00:14:55.209 --> 00:14:57.600 align:start position:0% that's almost ready as well but this is that<00:14:55.389> a<00:14:55.449> big<00:14:55.690> part<00:14:55.899> for<00:14:56.139> next<00:14:56.380> year<00:14:56.589> and<00:14:56.949> I 00:14:57.600 --> 00:14:57.610 align:start position:0% that a big part for next year and I 00:14:57.610 --> 00:14:59.250 align:start position:0% that a big part for next year and I would<00:14:57.790> like<00:14:57.910> to<00:14:58.000> thank<00:14:58.180> all<00:14:58.420> the<00:14:58.449> external 00:14:59.250 --> 00:14:59.260 align:start position:0% would like to thank all the external 00:14:59.260 --> 00:15:01.050 align:start position:0% would like to thank all the external contributors<00:14:59.529> all<00:15:00.040> the<00:15:00.130> volunteers<00:15:00.670> we<00:15:00.880> had 00:15:01.050 --> 00:15:01.060 align:start position:0% contributors all the volunteers we had 00:15:01.060 --> 00:15:03.329 align:start position:0% contributors all the volunteers we had for<00:15:01.269> solidity<00:15:01.660> because<00:15:02.350> the<00:15:02.440> numbers<00:15:02.829> is 00:15:03.329 --> 00:15:03.339 align:start position:0% for solidity because the numbers is 00:15:03.339 --> 00:15:06.059 align:start position:0% for solidity because the numbers is really<00:15:03.430> growing<00:15:04.000> and<00:15:04.360> we<00:15:05.019> have<00:15:05.139> a<00:15:05.170> lot<00:15:05.319> of<00:15:05.440> good 00:15:06.059 --> 00:15:06.069 align:start position:0% really growing and we have a lot of good 00:15:06.069 --> 00:15:08.460 align:start position:0% really growing and we have a lot of good people<00:15:06.190> helping<00:15:06.670> guide<00:15:06.990> now<00:15:07.990> with<00:15:08.170> it<00:15:08.290> here 00:15:08.460 --> 00:15:08.470 align:start position:0% people helping guide now with it here 00:15:08.470 --> 00:15:10.860 align:start position:0% people helping guide now with it here iam<00:15:08.589> j/s<00:15:08.920> we<00:15:09.670> also<00:15:09.880> received<00:15:10.480> a<00:15:10.569> lot<00:15:10.600> of 00:15:10.860 --> 00:15:10.870 align:start position:0% iam j/s we also received a lot of 00:15:10.870 --> 00:15:12.540 align:start position:0% iam j/s we also received a lot of volunteer<00:15:11.260> contributors<00:15:11.440> this<00:15:12.100> year<00:15:12.370> and 00:15:12.540 --> 00:15:12.550 align:start position:0% volunteer contributors this year and 00:15:12.550 --> 00:15:14.819 align:start position:0% volunteer contributors this year and with<00:15:13.420> the<00:15:13.510> help<00:15:13.690> of<00:15:13.779> them<00:15:14.019> they<00:15:14.230> were<00:15:14.380> able<00:15:14.500> to 00:15:14.819 --> 00:15:14.829 align:start position:0% with the help of them they were able to 00:15:14.829 --> 00:15:18.750 align:start position:0% with the help of them they were able to update<00:15:15.449> all<00:15:16.449> the<00:15:16.510> MGS<00:15:17.110> projects<00:15:17.620> to<00:15:18.130> be<00:15:18.519> up<00:15:18.639> to 00:15:18.750 --> 00:15:18.760 align:start position:0% update all the MGS projects to be up to 00:15:18.760 --> 00:15:21.720 align:start position:0% update all the MGS projects to be up to speed<00:15:18.880> and<00:15:19.300> support<00:15:19.990> Byzantium<00:15:20.709> this<00:15:21.610> is 00:15:21.720 --> 00:15:21.730 align:start position:0% speed and support Byzantium this is 00:15:21.730 --> 00:15:23.250 align:start position:0% speed and support Byzantium this is actually<00:15:22.060> very<00:15:22.089> important<00:15:22.750> not<00:15:22.870> many<00:15:23.079> people 00:15:23.250 --> 00:15:23.260 align:start position:0% actually very important not many people 00:15:23.260 --> 00:15:25.410 align:start position:0% actually very important not many people know<00:15:23.500> about<00:15:23.529> this<00:15:23.980> but<00:15:24.430> it<00:15:24.579> is<00:15:24.699> very<00:15:24.819> important 00:15:25.410 --> 00:15:25.420 align:start position:0% know about this but it is very important 00:15:25.420 --> 00:15:28.579 align:start position:0% know about this but it is very important because<00:15:25.630> it<00:15:25.870> really<00:15:25.990> is<00:15:26.350> is<00:15:26.920> used<00:15:27.399> in<00:15:27.699> many 00:15:28.579 --> 00:15:28.589 align:start position:0% because it really is is used in many 00:15:28.589 --> 00:15:31.410 align:start position:0% because it really is is used in many widely<00:15:29.589> used<00:15:29.920> projects<00:15:30.459> which<00:15:30.610> include<00:15:30.790> remix 00:15:31.410 --> 00:15:31.420 align:start position:0% widely used projects which include remix 00:15:31.420 --> 00:15:33.569 align:start position:0% widely used projects which include remix truffle<00:15:32.350> meta<00:15:33.130> mask 00:15:33.569 --> 00:15:33.579 align:start position:0% truffle meta mask 00:15:33.579 --> 00:15:36.809 align:start position:0% truffle meta mask and<00:15:33.730> many<00:15:34.209> others<00:15:34.680> now<00:15:35.680> regarding<00:15:36.189> II<00:15:36.430> was<00:15:36.610> him 00:15:36.809 --> 00:15:36.819 align:start position:0% and many others now regarding II was him 00:15:36.819 --> 00:15:38.939 align:start position:0% and many others now regarding II was him which<00:15:37.480> stands<00:15:37.899> for<00:15:37.930> a<00:15:38.230> tearing<00:15:38.500> webassembly 00:15:38.939 --> 00:15:38.949 align:start position:0% which stands for a tearing webassembly 00:15:38.949 --> 00:15:41.850 align:start position:0% which stands for a tearing webassembly there<00:15:39.790> hasn't<00:15:39.970> been<00:15:40.180> that<00:15:40.300> much<00:15:40.860> development 00:15:41.850 --> 00:15:41.860 align:start position:0% there hasn't been that much development 00:15:41.860 --> 00:15:44.189 align:start position:0% there hasn't been that much development in<00:15:41.980> the<00:15:42.069> last<00:15:42.250> year<00:15:42.459> mmm<00:15:43.389> but<00:15:43.660> that's<00:15:43.870> due<00:15:44.019> to<00:15:44.170> a 00:15:44.189 --> 00:15:44.199 align:start position:0% in the last year mmm but that's due to a 00:15:44.199 --> 00:15:46.759 align:start position:0% in the last year mmm but that's due to a few<00:15:44.470> reasons<00:15:44.649> the<00:15:45.459> specification<00:15:46.269> is<00:15:46.420> is 00:15:46.759 --> 00:15:46.769 align:start position:0% few reasons the specification is is 00:15:46.769 --> 00:15:48.240 align:start position:0% few reasons the specification is is practically<00:15:47.769> ready 00:15:48.240 --> 00:15:48.250 align:start position:0% practically ready 00:15:48.250 --> 00:15:50.400 align:start position:0% practically ready it<00:15:48.639> doesn't<00:15:49.029> include<00:15:49.180> Byzantium<00:15:50.019> but 00:15:50.400 --> 00:15:50.410 align:start position:0% it doesn't include Byzantium but 00:15:50.410 --> 00:15:52.019 align:start position:0% it doesn't include Byzantium but updating<00:15:50.829> it<00:15:50.980> to<00:15:51.069> Byzantium<00:15:51.250> shouldn't<00:15:51.910> take 00:15:52.019 --> 00:15:52.029 align:start position:0% updating it to Byzantium shouldn't take 00:15:52.029 --> 00:15:53.430 align:start position:0% updating it to Byzantium shouldn't take a<00:15:52.060> long<00:15:52.269> time 00:15:53.430 --> 00:15:53.440 align:start position:0% a long time 00:15:53.440 --> 00:15:56.680 align:start position:0% a long time secondly<00:15:54.440> the<00:15:55.180> intermediate<00:15:56.180> language<00:15:56.330> in 00:15:56.680 --> 00:15:56.690 align:start position:0% secondly the intermediate language in 00:15:56.690 --> 00:15:59.260 align:start position:0% secondly the intermediate language in solidity<00:15:57.110> which<00:15:57.589> I<00:15:57.740> mentioned<00:15:58.220> will<00:15:58.940> enable 00:15:59.260 --> 00:15:59.270 align:start position:0% solidity which I mentioned will enable 00:15:59.270 --> 00:16:01.660 align:start position:0% solidity which I mentioned will enable us<00:15:59.510> to<00:15:59.570> create<00:16:00.230> to<00:16:00.950> compile<00:16:01.279> solidity 00:16:01.660 --> 00:16:01.670 align:start position:0% us to create to compile solidity 00:16:01.670 --> 00:16:05.170 align:start position:0% us to create to compile solidity contracts<00:16:02.270> to<00:16:02.450> webassembly<00:16:03.170> um<00:16:03.620> and<00:16:04.610> also<00:16:05.089> we 00:16:05.170 --> 00:16:05.180 align:start position:0% contracts to webassembly um and also we 00:16:05.180 --> 00:16:07.030 align:start position:0% contracts to webassembly um and also we receive<00:16:05.450> a<00:16:05.510> lot<00:16:05.540> of<00:16:05.720> new<00:16:06.260> contributors<00:16:06.560> there 00:16:07.030 --> 00:16:07.040 align:start position:0% receive a lot of new contributors there 00:16:07.040 --> 00:16:09.519 align:start position:0% receive a lot of new contributors there which<00:16:07.880> seems<00:16:08.270> like<00:16:08.480> it<00:16:08.510> will<00:16:08.810> kick-start<00:16:09.200> the 00:16:09.519 --> 00:16:09.529 align:start position:0% which seems like it will kick-start the 00:16:09.529 --> 00:16:12.040 align:start position:0% which seems like it will kick-start the project<00:16:09.890> into<00:16:10.100> creating<00:16:10.580> a<00:16:10.640> new<00:16:10.760> client<00:16:11.149> where 00:16:12.040 --> 00:16:12.050 align:start position:0% project into creating a new client where 00:16:12.050 --> 00:16:24.880 align:start position:0% project into creating a new client where you<00:16:12.110> soon<00:16:12.320> thank<00:16:13.250> you<00:16:18.880> hello<00:16:19.880> everyone<00:16:23.890> so 00:16:24.880 --> 00:16:24.890 align:start position:0% you soon thank you hello everyone so 00:16:24.890 --> 00:16:28.090 align:start position:0% you soon thank you hello everyone so there's<00:16:25.130> a<00:16:25.190> lot<00:16:25.459> to<00:16:25.850> say<00:16:26.330> on<00:16:26.690> he<00:16:26.959> mix<00:16:27.170> so<00:16:27.800> he<00:16:27.920> mix 00:16:28.090 --> 00:16:28.100 align:start position:0% there's a lot to say on he mix so he mix 00:16:28.100 --> 00:16:32.050 align:start position:0% there's a lot to say on he mix so he mix is<00:16:28.399> web<00:16:29.270> ID<00:16:29.510> I<00:16:29.930> forgot<00:16:30.560> to<00:16:30.649> say<00:16:30.830> this<00:16:31.100> is<00:16:31.670> a<00:16:31.880> way 00:16:32.050 --> 00:16:32.060 align:start position:0% is web ID I forgot to say this is a way 00:16:32.060 --> 00:16:34.630 align:start position:0% is web ID I forgot to say this is a way to<00:16:32.120> develop<00:16:32.570> smart<00:16:33.140> contracts<00:16:33.680> and<00:16:33.860> then<00:16:34.430> to 00:16:34.630 --> 00:16:34.640 align:start position:0% to develop smart contracts and then to 00:16:34.640 --> 00:16:37.410 align:start position:0% to develop smart contracts and then to run<00:16:34.850> smart<00:16:35.270> contract<00:16:35.660> in<00:16:36.500> a<00:16:36.589> test<00:16:36.800> environment 00:16:37.410 --> 00:16:37.420 align:start position:0% run smart contract in a test environment 00:16:37.420 --> 00:16:40.810 align:start position:0% run smart contract in a test environment he<00:16:38.420> mix<00:16:38.600> has<00:16:38.779> been<00:16:39.020> I<00:16:39.560> started<00:16:40.459> development 00:16:40.810 --> 00:16:40.820 align:start position:0% he mix has been I started development 00:16:40.820 --> 00:16:45.699 align:start position:0% he mix has been I started development like<00:16:41.209> one<00:16:41.839> year<00:16:42.230> and<00:16:42.290> our<00:16:42.649> foe<00:16:42.920> and<00:16:44.290> we<00:16:45.290> are<00:16:45.410> now 00:16:45.699 --> 00:16:45.709 align:start position:0% like one year and our foe and we are now 00:16:45.709 --> 00:16:51.160 align:start position:0% like one year and our foe and we are now in<00:16:47.080> the<00:16:48.080> way<00:16:48.320> of<00:16:48.709> improving<00:16:49.459> the<00:16:49.790> UI<00:16:50.170> we 00:16:51.160 --> 00:16:51.170 align:start position:0% in the way of improving the UI we 00:16:51.170 --> 00:16:53.740 align:start position:0% in the way of improving the UI we already<00:16:51.560> improve<00:16:52.130> the<00:16:52.970> code<00:16:53.240> back-end<00:16:53.720> code 00:16:53.740 --> 00:16:53.750 align:start position:0% already improve the code back-end code 00:16:53.750 --> 00:16:57.190 align:start position:0% already improve the code back-end code and<00:16:54.850> we<00:16:55.850> have<00:16:55.940> what<00:16:56.060> to<00:16:56.149> say<00:16:56.209> so<00:16:56.750> I<00:16:56.779> will<00:16:56.870> be 00:16:57.190 --> 00:16:57.200 align:start position:0% and we have what to say so I will be 00:16:57.200 --> 00:17:02.230 align:start position:0% and we have what to say so I will be presenting<00:16:57.980> on<00:16:58.430> Friday<00:17:00.579> one<00:17:01.579> talk<00:17:01.880> about 00:17:02.230 --> 00:17:02.240 align:start position:0% presenting on Friday one talk about 00:17:02.240 --> 00:17:05.650 align:start position:0% presenting on Friday one talk about timox<00:17:02.950> one<00:17:03.950> important<00:17:04.670> thing<00:17:04.760> that<00:17:04.970> we<00:17:05.179> add 00:17:05.650 --> 00:17:05.660 align:start position:0% timox one important thing that we add 00:17:05.660 --> 00:17:09.340 align:start position:0% timox one important thing that we add since<00:17:06.589> last<00:17:06.800> year<00:17:07.189> is<00:17:07.850> this<00:17:08.240> new<00:17:08.510> why<00:17:08.809> does 00:17:09.340 --> 00:17:09.350 align:start position:0% since last year is this new why does 00:17:09.350 --> 00:17:13.090 align:start position:0% since last year is this new why does Abed<00:17:09.589> melt<00:17:10.189> like<00:17:10.579> few<00:17:11.360> weeks<00:17:11.569> ago<00:17:11.720> but<00:17:12.650> we<00:17:12.920> also 00:17:13.090 --> 00:17:13.100 align:start position:0% Abed melt like few weeks ago but we also 00:17:13.100 --> 00:17:19.569 align:start position:0% Abed melt like few weeks ago but we also add<00:17:13.660> new<00:17:14.660> users<00:17:15.110> since<00:17:15.910> few<00:17:16.910> months<00:17:17.829> we<00:17:18.829> have<00:17:18.860> a 00:17:19.569 --> 00:17:19.579 align:start position:0% add new users since few months we have a 00:17:19.579 --> 00:17:22.510 align:start position:0% add new users since few months we have a Makita<00:17:20.360> channel<00:17:20.870> that<00:17:21.079> allows<00:17:22.069> people<00:17:22.309> to 00:17:22.510 --> 00:17:22.520 align:start position:0% Makita channel that allows people to 00:17:22.520 --> 00:17:24.460 align:start position:0% Makita channel that allows people to give<00:17:22.850> feedback<00:17:23.030> about<00:17:23.449> the<00:17:23.660> you<00:17:23.870> I'll<00:17:24.020> give 00:17:24.460 --> 00:17:24.470 align:start position:0% give feedback about the you I'll give 00:17:24.470 --> 00:17:26.980 align:start position:0% give feedback about the you I'll give feedback<00:17:24.620> about<00:17:24.850> he<00:17:25.850> mix<00:17:26.059> the<00:17:26.480> application 00:17:26.980 --> 00:17:26.990 align:start position:0% feedback about he mix the application 00:17:26.990 --> 00:17:32.650 align:start position:0% feedback about he mix the application and<00:17:27.910> we<00:17:28.910> also<00:17:29.150> have<00:17:29.600> an<00:17:29.900> quite<00:17:30.559> importance<00:17:31.660> for 00:17:32.650 --> 00:17:32.660 align:start position:0% and we also have an quite importance for 00:17:32.660 --> 00:17:36.340 align:start position:0% and we also have an quite importance for a<00:17:32.720> free<00:17:33.080> three<00:17:33.380> new<00:17:33.860> contributors<00:17:35.050> so<00:17:36.050> we<00:17:36.200> have 00:17:36.340 --> 00:17:36.350 align:start position:0% a free three new contributors so we have 00:17:36.350 --> 00:17:39.490 align:start position:0% a free three new contributors so we have a<00:17:36.620> hub<00:17:36.950> which<00:17:37.309> is<00:17:37.550> everything<00:17:38.090> and<00:17:38.690> we<00:17:39.470> have 00:17:39.490 --> 00:17:39.500 align:start position:0% a hub which is everything and we have 00:17:39.500 --> 00:17:42.190 align:start position:0% a hub which is everything and we have Nina<00:17:39.980> and<00:17:40.220> Alex<00:17:40.520> with<00:17:40.970> us<00:17:41.510> walking<00:17:42.050> on 00:17:42.190 --> 00:17:42.200 align:start position:0% Nina and Alex with us walking on 00:17:42.200 --> 00:17:46.390 align:start position:0% Nina and Alex with us walking on hammocks<00:17:42.590> and<00:17:43.120> they<00:17:44.120> help<00:17:44.860> the<00:17:45.860> community<00:17:46.370> to 00:17:46.390 --> 00:17:46.400 align:start position:0% hammocks and they help the community to 00:17:46.400 --> 00:17:49.480 align:start position:0% hammocks and they help the community to improve<00:17:46.820> remix<00:17:47.240> and<00:17:47.540> to<00:17:48.230> go<00:17:48.380> further<00:17:48.620> under 00:17:49.480 --> 00:17:49.490 align:start position:0% improve remix and to go further under 00:17:49.490 --> 00:17:52.390 align:start position:0% improve remix and to go further under control<00:17:50.150> development<00:17:50.559> so<00:17:51.559> for<00:17:51.800> the<00:17:51.890> next<00:17:52.070> I 00:17:52.390 --> 00:17:52.400 align:start position:0% control development so for the next I 00:17:52.400 --> 00:17:54.780 align:start position:0% control development so for the next I will<00:17:52.520> be<00:17:52.610> giving<00:17:53.210> a<00:17:53.300> torque<00:17:53.570> then<00:17:53.900> on<00:17:54.470> Friday 00:17:54.780 --> 00:17:54.790 align:start position:0% will be giving a torque then on Friday 00:17:54.790 --> 00:17:59.020 align:start position:0% will be giving a torque then on Friday but<00:17:55.790> basically<00:17:56.480> we<00:17:56.870> are<00:17:57.050> in<00:17:57.440> a<00:17:57.950> point<00:17:58.250> where<00:17:58.700> we 00:17:59.020 --> 00:17:59.030 align:start position:0% but basically we are in a point where we 00:17:59.030 --> 00:18:02.919 align:start position:0% but basically we are in a point where we can<00:17:59.179> be<00:17:59.470> proud<00:18:00.470> of<00:18:00.890> what<00:18:01.370> chemists<00:18:01.730> do<00:18:01.910> now<00:18:02.120> but 00:18:02.919 --> 00:18:02.929 align:start position:0% can be proud of what chemists do now but 00:18:02.929 --> 00:18:05.200 align:start position:0% can be proud of what chemists do now but we<00:18:03.200> still<00:18:03.230> need<00:18:03.740> to<00:18:03.980> work<00:18:04.130> on<00:18:04.309> it<00:18:04.460> and<00:18:04.730> we<00:18:04.970> still 00:18:05.200 --> 00:18:05.210 align:start position:0% we still need to work on it and we still 00:18:05.210 --> 00:18:07.000 align:start position:0% we still need to work on it and we still need<00:18:05.900> to<00:18:06.050> improve 00:18:07.000 --> 00:18:07.010 align:start position:0% need to improve 00:18:07.010 --> 00:18:11.500 align:start position:0% need to improve some<00:18:08.980> some<00:18:09.980> stuff<00:18:10.220> in<00:18:10.370> hammocks<00:18:10.700> for<00:18:10.940> example 00:18:11.500 --> 00:18:11.510 align:start position:0% some some stuff in hammocks for example 00:18:11.510 --> 00:18:16.630 align:start position:0% some some stuff in hammocks for example we<00:18:12.200> need<00:18:12.380> to<00:18:14.050> split<00:18:15.050> down<00:18:15.320> the<00:18:15.740> code<00:18:16.100> of<00:18:16.250> remix 00:18:16.630 --> 00:18:16.640 align:start position:0% we need to split down the code of remix 00:18:16.640 --> 00:18:19.930 align:start position:0% we need to split down the code of remix so<00:18:17.150> it<00:18:17.300> can<00:18:17.450> be<00:18:17.600> used<00:18:17.840> by<00:18:18.290> the<00:18:18.350> community<00:18:18.940> we 00:18:19.930 --> 00:18:19.940 align:start position:0% so it can be used by the community we 00:18:19.940 --> 00:18:22.390 align:start position:0% so it can be used by the community we need<00:18:20.030> also<00:18:20.300> to<00:18:20.540> find<00:18:21.350> a<00:18:21.620> good<00:18:21.800> way<00:18:21.980> for<00:18:22.010> the 00:18:22.390 --> 00:18:22.400 align:start position:0% need also to find a good way for the 00:18:22.400 --> 00:18:25.810 align:start position:0% need also to find a good way for the community<00:18:22.910> to<00:18:22.940> be<00:18:23.060> able<00:18:23.420> to<00:18:23.600> have<00:18:24.820> continuous 00:18:25.810 --> 00:18:25.820 align:start position:0% community to be able to have continuous 00:18:25.820 --> 00:18:28.210 align:start position:0% community to be able to have continuous integration<00:18:26.000> on<00:18:26.600> hammocks<00:18:26.990> and<00:18:27.530> so<00:18:27.950> this<00:18:28.100> is<00:18:28.190> a 00:18:28.210 --> 00:18:28.220 align:start position:0% integration on hammocks and so this is a 00:18:28.220 --> 00:18:30.160 align:start position:0% integration on hammocks and so this is a bunch<00:18:28.430> of<00:18:28.580> walk<00:18:29.060> that<00:18:29.240> will<00:18:29.450> be<00:18:29.570> done<00:18:29.780> in<00:18:30.050> the 00:18:30.160 --> 00:18:30.170 align:start position:0% bunch of walk that will be done in the 00:18:30.170 --> 00:18:32.050 align:start position:0% bunch of walk that will be done in the in<00:18:30.470> the<00:18:30.560> next<00:18:30.710> year<00:18:31.070> and<00:18:31.280> I<00:18:31.790> will<00:18:31.940> be 00:18:32.050 --> 00:18:32.060 align:start position:0% in the next year and I will be 00:18:32.060 --> 00:18:34.660 align:start position:0% in the next year and I will be presenting<00:18:32.270> on<00:18:32.630> a<00:18:32.660> Friday<00:18:32.930> some<00:18:33.580> samosas<00:18:34.580> are 00:18:34.660 --> 00:18:34.670 align:start position:0% presenting on a Friday some samosas are 00:18:34.670 --> 00:18:37.000 align:start position:0% presenting on a Friday some samosas are features<00:18:35.030> that<00:18:35.060> we<00:18:35.330> have<00:18:35.450> made<00:18:35.720> last<00:18:36.500> year<00:18:36.800> and 00:18:37.000 --> 00:18:37.010 align:start position:0% features that we have made last year and 00:18:37.010 --> 00:18:38.860 align:start position:0% features that we have made last year and I<00:18:37.400> will<00:18:37.520> be<00:18:37.610> also<00:18:37.760> presenting<00:18:38.420> some<00:18:38.690> new 00:18:38.860 --> 00:18:38.870 align:start position:0% I will be also presenting some new 00:18:38.870 --> 00:18:42.040 align:start position:0% I will be also presenting some new features<00:18:39.320> that<00:18:39.560> have<00:18:39.890> been<00:18:40.240> merged<00:18:41.240> a<00:18:41.780> few 00:18:42.040 --> 00:18:42.050 align:start position:0% features that have been merged a few 00:18:42.050 --> 00:18:45.640 align:start position:0% features that have been merged a few weeks<00:18:42.230> ago<00:18:42.380> and<00:18:43.300> yeah<00:18:44.300> I<00:18:44.570> hope<00:18:45.200> to<00:18:45.350> see<00:18:45.530> you 00:18:45.640 --> 00:18:45.650 align:start position:0% weeks ago and yeah I hope to see you 00:18:45.650 --> 00:18:49.450 align:start position:0% weeks ago and yeah I hope to see you around<00:18:45.920> for<00:18:46.490> this<00:18:46.670> week<00:18:46.910> so<00:18:47.630> we<00:18:48.140> can<00:18:48.350> just<00:18:48.650> show 00:18:49.450 --> 00:18:49.460 align:start position:0% around for this week so we can just show 00:18:49.460 --> 00:18:53.020 align:start position:0% around for this week so we can just show you<00:18:49.490> how<00:18:49.760> it<00:18:49.910> works<00:18:50.090> and<00:18:51.340> we<00:18:52.340> can<00:18:52.520> just<00:18:52.760> show 00:18:53.020 --> 00:18:53.030 align:start position:0% you how it works and we can just show 00:18:53.030 --> 00:18:56.290 align:start position:0% you how it works and we can just show you<00:18:53.060> how<00:18:53.450> it's<00:18:54.260> now<00:18:54.580> become<00:18:55.580> easier<00:18:56.090> and 00:18:56.290 --> 00:18:56.300 align:start position:0% you how it's now become easier and 00:18:56.300 --> 00:19:00.230 align:start position:0% you how it's now become easier and easier<00:18:56.420> to<00:18:56.840> develop<00:18:57.020> smart<00:18:57.500> contracts<00:18:57.950> Thanks 00:19:00.230 --> 00:19:00.240 align:start position:0% easier to develop smart contracts Thanks 00:19:00.240 --> 00:19:03.870 align:start position:0% easier to develop smart contracts Thanks [Applause] 00:19:03.870 --> 00:19:03.880 align:start position:0% [Applause] 00:19:03.880 --> 00:19:07.230 align:start position:0% [Applause] hello<00:19:04.539> I'm<00:19:05.320> Piper<00:19:05.710> Miriam<00:19:06.280> and<00:19:06.549> I'm<00:19:07.030> the 00:19:07.230 --> 00:19:07.240 align:start position:0% hello I'm Piper Miriam and I'm the 00:19:07.240 --> 00:19:09.720 align:start position:0% hello I'm Piper Miriam and I'm the Python<00:19:07.750> team<00:19:08.260> lead<00:19:08.500> for<00:19:08.530> the<00:19:08.830> foundation 00:19:09.720 --> 00:19:09.730 align:start position:0% Python team lead for the foundation 00:19:09.730 --> 00:19:12.539 align:start position:0% Python team lead for the foundation let's<00:19:10.450> see<00:19:10.600> earlier<00:19:10.929> this<00:19:11.140> year<00:19:11.200> and<00:19:11.740> myself 00:19:12.539 --> 00:19:12.549 align:start position:0% let's see earlier this year and myself 00:19:12.549 --> 00:19:14.039 align:start position:0% let's see earlier this year and myself and<00:19:12.910> a<00:19:12.970> number<00:19:13.120> of<00:19:13.240> other<00:19:13.480> framework 00:19:14.039 --> 00:19:14.049 align:start position:0% and a number of other framework 00:19:14.049 --> 00:19:17.250 align:start position:0% and a number of other framework developers<00:19:14.880> came<00:19:15.880> together<00:19:16.090> and<00:19:16.570> established 00:19:17.250 --> 00:19:17.260 align:start position:0% developers came together and established 00:19:17.260 --> 00:19:19.289 align:start position:0% developers came together and established a<00:19:17.410> spec<00:19:17.679> for<00:19:18.010> packaging<00:19:18.549> smart<00:19:18.850> contracts 00:19:19.289 --> 00:19:19.299 align:start position:0% a spec for packaging smart contracts 00:19:19.299 --> 00:19:21.060 align:start position:0% a spec for packaging smart contracts I'll<00:19:19.630> be<00:19:19.990> talking<00:19:20.320> about<00:19:20.679> that<00:19:20.830> a<00:19:20.860> little 00:19:21.060 --> 00:19:21.070 align:start position:0% I'll be talking about that a little 00:19:21.070 --> 00:19:25.049 align:start position:0% I'll be talking about that a little later<00:19:21.190> today<00:19:21.549> shortly<00:19:22.090> after<00:19:22.330> lunch<00:19:22.980> I<00:19:24.059> am 00:19:25.049 --> 00:19:25.059 align:start position:0% later today shortly after lunch I am 00:19:25.059 --> 00:19:27.360 align:start position:0% later today shortly after lunch I am responsible<00:19:25.809> for<00:19:26.200> a<00:19:26.230> lot<00:19:26.410> of<00:19:26.440> the<00:19:26.830> Python 00:19:27.360 --> 00:19:27.370 align:start position:0% responsible for a lot of the Python 00:19:27.370 --> 00:19:28.980 align:start position:0% responsible for a lot of the Python tooling<00:19:27.730> in<00:19:27.820> the<00:19:27.880> ecosystem<00:19:28.450> and<00:19:28.720> this<00:19:28.809> year 00:19:28.980 --> 00:19:28.990 align:start position:0% tooling in the ecosystem and this year 00:19:28.990 --> 00:19:30.270 align:start position:0% tooling in the ecosystem and this year we've<00:19:29.140> been<00:19:29.169> working<00:19:29.620> on<00:19:29.740> maturing<00:19:30.250> that 00:19:30.270 --> 00:19:30.280 align:start position:0% we've been working on maturing that 00:19:30.280 --> 00:19:34.049 align:start position:0% we've been working on maturing that tooling<00:19:31.500> bringing<00:19:32.500> it<00:19:32.650> closer<00:19:33.340> to<00:19:33.520> being<00:19:33.910> up 00:19:34.049 --> 00:19:34.059 align:start position:0% tooling bringing it closer to being up 00:19:34.059 --> 00:19:37.520 align:start position:0% tooling bringing it closer to being up to<00:19:34.090> par<00:19:34.210> with<00:19:34.600> the<00:19:34.660> JavaScript<00:19:35.169> ecosystem<00:19:35.260> and 00:19:37.520 --> 00:19:37.530 align:start position:0% to par with the JavaScript ecosystem and 00:19:37.530 --> 00:19:40.289 align:start position:0% to par with the JavaScript ecosystem and I've<00:19:38.530> been<00:19:39.220> working<00:19:39.400> on<00:19:39.640> an<00:19:39.820> alternate 00:19:40.289 --> 00:19:40.299 align:start position:0% I've been working on an alternate 00:19:40.299 --> 00:19:42.000 align:start position:0% I've been working on an alternate implementation<00:19:40.929> of<00:19:41.049> the<00:19:41.140> EVM<00:19:41.470> and<00:19:41.650> Python 00:19:42.000 --> 00:19:42.010 align:start position:0% implementation of the EVM and Python 00:19:42.010 --> 00:19:44.580 align:start position:0% implementation of the EVM and Python called<00:19:42.370> PI<00:19:42.520> EVM<00:19:42.970> and<00:19:43.270> I<00:19:43.900> will<00:19:44.020> also<00:19:44.320> be<00:19:44.440> talking 00:19:44.580 --> 00:19:44.590 align:start position:0% called PI EVM and I will also be talking 00:19:44.590 --> 00:19:48.090 align:start position:0% called PI EVM and I will also be talking about<00:19:44.799> that<00:19:45.100> later<00:19:45.789> today<00:19:46.890> later<00:19:47.890> in<00:19:48.039> the 00:19:48.090 --> 00:19:48.100 align:start position:0% about that later today later in the 00:19:48.100 --> 00:19:50.820 align:start position:0% about that later today later in the afternoon<00:19:48.490> over<00:19:48.669> this<00:19:49.600> next<00:19:49.840> year<00:19:50.320> the<00:19:50.620> hope 00:19:50.820 --> 00:19:50.830 align:start position:0% afternoon over this next year the hope 00:19:50.830 --> 00:19:52.950 align:start position:0% afternoon over this next year the hope is<00:19:51.010> to<00:19:51.039> bring<00:19:51.789> that<00:19:51.940> implementation<00:19:52.480> online 00:19:52.950 --> 00:19:52.960 align:start position:0% is to bring that implementation online 00:19:52.960 --> 00:19:56.779 align:start position:0% is to bring that implementation online as<00:19:53.799> a<00:19:53.860> new<00:19:54.130> light<00:19:54.340> client<00:19:54.760> node<00:19:54.940> as<00:19:55.929> well<00:19:56.320> as 00:19:56.779 --> 00:19:56.789 align:start position:0% as a new light client node as well as 00:19:56.789 --> 00:19:59.490 align:start position:0% as a new light client node as well as getting<00:19:57.789> broader<00:19:58.270> support<00:19:58.600> and<00:19:58.990> adoption<00:19:59.470> of 00:19:59.490 --> 00:19:59.500 align:start position:0% getting broader support and adoption of 00:19:59.500 --> 00:20:01.580 align:start position:0% getting broader support and adoption of package<00:20:00.280> management<00:20:00.730> across<00:20:00.909> the<00:20:01.120> ecosystem 00:20:01.580 --> 00:20:01.590 align:start position:0% package management across the ecosystem 00:20:01.590 --> 00:20:03.890 align:start position:0% package management across the ecosystem thanks 00:20:03.890 --> 00:20:03.900 align:start position:0% thanks 00:20:03.900 --> 00:20:09.639 align:start position:0% thanks [Applause] 00:20:09.639 --> 00:20:09.649 align:start position:0% [Applause] 00:20:09.649 --> 00:20:13.159 align:start position:0% [Applause] welcome<00:20:10.649> I'm<00:20:11.580> not<00:20:11.940> the<00:20:12.120> victor<00:20:12.480> I'm<00:20:12.690> standing 00:20:13.159 --> 00:20:13.169 align:start position:0% welcome I'm not the victor I'm standing 00:20:13.169 --> 00:20:15.710 align:start position:0% welcome I'm not the victor I'm standing in<00:20:13.350> for<00:20:13.529> him<00:20:13.740> I'm<00:20:13.980> Daniel<00:20:14.700> and<00:20:14.909> I'm<00:20:15.450> the 00:20:15.710 --> 00:20:15.720 align:start position:0% in for him I'm Daniel and I'm the 00:20:15.720 --> 00:20:20.149 align:start position:0% in for him I'm Daniel and I'm the architect<00:20:16.080> of<00:20:16.529> swarm<00:20:17.419> our<00:20:18.419> project<00:20:19.140> has<00:20:19.470> grown 00:20:20.149 --> 00:20:20.159 align:start position:0% architect of swarm our project has grown 00:20:20.159 --> 00:20:23.000 align:start position:0% architect of swarm our project has grown a<00:20:20.640> little<00:20:21.090> bit<00:20:21.299> beyond<00:20:21.779> this<00:20:21.990> original<00:20:22.679> scope 00:20:23.000 --> 00:20:23.010 align:start position:0% a little bit beyond this original scope 00:20:23.010 --> 00:20:25.700 align:start position:0% a little bit beyond this original scope of<00:20:23.250> providing<00:20:23.850> mass<00:20:24.090> storage<00:20:24.710> decentralized 00:20:25.700 --> 00:20:25.710 align:start position:0% of providing mass storage decentralized 00:20:25.710 --> 00:20:28.789 align:start position:0% of providing mass storage decentralized mass<00:20:26.070> storage<00:20:26.309> for<00:20:26.850> aetherium<00:20:27.450> and<00:20:27.690> it<00:20:28.559> also 00:20:28.789 --> 00:20:28.799 align:start position:0% mass storage for aetherium and it also 00:20:28.799 --> 00:20:31.820 align:start position:0% mass storage for aetherium and it also now<00:20:29.460> includes<00:20:30.289> applications<00:20:31.289> like<00:20:31.590> high 00:20:31.820 --> 00:20:31.830 align:start position:0% now includes applications like high 00:20:31.830 --> 00:20:34.279 align:start position:0% now includes applications like high bandwidth<00:20:32.309> communication<00:20:33.149> between<00:20:33.870> the 00:20:34.279 --> 00:20:34.289 align:start position:0% bandwidth communication between the 00:20:34.289 --> 00:20:38.620 align:start position:0% bandwidth communication between the nodes<00:20:35.210> our<00:20:36.210> team<00:20:36.600> has<00:20:36.840> grown<00:20:36.870> considerably<00:20:37.559> to 00:20:38.620 --> 00:20:38.630 align:start position:0% nodes our team has grown considerably to 00:20:38.630 --> 00:20:43.330 align:start position:0% nodes our team has grown considerably to grow<00:20:39.630> up<00:20:39.840> to<00:20:40.169> today<00:20:41.039> to<00:20:41.970> the<00:20:42.090> new<00:20:42.240> challenge 00:20:43.330 --> 00:20:43.340 align:start position:0% grow up to today to the new challenge 00:20:43.340 --> 00:20:46.430 align:start position:0% grow up to today to the new challenge tomorrow<00:20:44.340> we're<00:20:44.909> going<00:20:45.179> to<00:20:45.389> give<00:20:45.600> you<00:20:45.840> a<00:20:46.080> more 00:20:46.430 --> 00:20:46.440 align:start position:0% tomorrow we're going to give you a more 00:20:46.440 --> 00:20:49.970 align:start position:0% tomorrow we're going to give you a more detailed<00:20:46.980> report<00:20:47.519> on<00:20:48.110> what<00:20:49.110> we<00:20:49.289> are<00:20:49.350> doing<00:20:49.559> and 00:20:49.970 --> 00:20:49.980 align:start position:0% detailed report on what we are doing and 00:20:49.980 --> 00:20:51.769 align:start position:0% detailed report on what we are doing and what<00:20:50.309> have<00:20:50.519> we<00:20:50.730> already<00:20:50.850> achieved<00:20:51.450> but 00:20:51.769 --> 00:20:51.779 align:start position:0% what have we already achieved but 00:20:51.779 --> 00:20:54.080 align:start position:0% what have we already achieved but briefly<00:20:52.200> I<00:20:52.470> would<00:20:52.799> like<00:20:53.010> to<00:20:53.279> mention<00:20:53.519> a<00:20:54.059> few 00:20:54.080 --> 00:20:54.090 align:start position:0% briefly I would like to mention a few 00:20:54.090 --> 00:20:56.960 align:start position:0% briefly I would like to mention a few cornerstones<00:20:54.929> so<00:20:55.769> first<00:20:56.070> of<00:20:56.279> all<00:20:56.429> we<00:20:56.669> have 00:20:56.960 --> 00:20:56.970 align:start position:0% cornerstones so first of all we have 00:20:56.970 --> 00:20:59.870 align:start position:0% cornerstones so first of all we have developed<00:20:57.750> a<00:20:57.990> simulation<00:20:58.620> framework<00:20:59.340> where 00:20:59.870 --> 00:20:59.880 align:start position:0% developed a simulation framework where 00:20:59.880 --> 00:21:02.629 align:start position:0% developed a simulation framework where we<00:20:59.909> can<00:21:00.269> test<00:21:00.570> how<00:21:01.260> our<00:21:01.590> network<00:21:02.070> and<00:21:02.429> how<00:21:02.580> the 00:21:02.629 --> 00:21:02.639 align:start position:0% we can test how our network and how the 00:21:02.639 --> 00:21:04.580 align:start position:0% we can test how our network and how the algorithms<00:21:03.269> that<00:21:03.419> we're<00:21:03.630> building<00:21:03.840> are<00:21:04.350> going 00:21:04.580 --> 00:21:04.590 align:start position:0% algorithms that we're building are going 00:21:04.590 --> 00:21:08.090 align:start position:0% algorithms that we're building are going to<00:21:04.830> cope<00:21:05.070> with<00:21:05.659> various<00:21:06.659> situations<00:21:07.409> at<00:21:07.769> scale 00:21:08.090 --> 00:21:08.100 align:start position:0% to cope with various situations at scale 00:21:08.100 --> 00:21:11.529 align:start position:0% to cope with various situations at scale like<00:21:08.850> network<00:21:09.389> partition<00:21:10.490> bandwidth 00:21:11.529 --> 00:21:11.539 align:start position:0% like network partition bandwidth 00:21:11.539 --> 00:21:15.350 align:start position:0% like network partition bandwidth bottlenecks<00:21:12.539> or<00:21:13.279> high<00:21:14.279> turn<00:21:14.669> so<00:21:15.090> nodes 00:21:15.350 --> 00:21:15.360 align:start position:0% bottlenecks or high turn so nodes 00:21:15.360 --> 00:21:18.460 align:start position:0% bottlenecks or high turn so nodes leaving<00:21:15.779> and<00:21:15.990> joining<00:21:16.559> the<00:21:16.799> network<00:21:16.919> rapidly 00:21:18.460 --> 00:21:18.470 align:start position:0% leaving and joining the network rapidly 00:21:18.470 --> 00:21:22.220 align:start position:0% leaving and joining the network rapidly the<00:21:19.470> first<00:21:19.970> practical<00:21:20.970> application<00:21:21.720> of<00:21:21.840> swarm 00:21:22.220 --> 00:21:22.230 align:start position:0% the first practical application of swarm 00:21:22.230 --> 00:21:24.470 align:start position:0% the first practical application of swarm is<00:21:22.440> being<00:21:22.740> in<00:21:22.919> development<00:21:23.070> it's<00:21:23.760> going<00:21:24.029> to<00:21:24.299> be 00:21:24.470 --> 00:21:24.480 align:start position:0% is being in development it's going to be 00:21:24.480 --> 00:21:27.649 align:start position:0% is being in development it's going to be a<00:21:25.039> cloud<00:21:26.039> storage<00:21:26.490> where<00:21:26.940> people<00:21:27.480> can 00:21:27.649 --> 00:21:27.659 align:start position:0% a cloud storage where people can 00:21:27.659 --> 00:21:29.570 align:start position:0% a cloud storage where people can synchronize<00:21:28.260> data<00:21:28.559> between<00:21:28.860> their<00:21:29.250> devices 00:21:29.570 --> 00:21:29.580 align:start position:0% synchronize data between their devices 00:21:29.580 --> 00:21:32.060 align:start position:0% synchronize data between their devices and<00:21:30.090> also<00:21:30.450> share<00:21:30.779> large<00:21:31.470> files<00:21:31.559> and 00:21:32.060 --> 00:21:32.070 align:start position:0% and also share large files and 00:21:32.070 --> 00:21:35.720 align:start position:0% and also share large files and directories<00:21:32.389> between<00:21:33.389> each<00:21:33.570> other<00:21:34.700> there<00:21:35.700> are 00:21:35.720 --> 00:21:35.730 align:start position:0% directories between each other there are 00:21:35.730 --> 00:21:37.669 align:start position:0% directories between each other there are third<00:21:36.090> party<00:21:36.480> applications<00:21:37.139> of<00:21:37.350> swarm 00:21:37.669 --> 00:21:37.679 align:start position:0% third party applications of swarm 00:21:37.679 --> 00:21:41.269 align:start position:0% third party applications of swarm emerging<00:21:38.450> such<00:21:39.450> as<00:21:39.779> life<00:21:40.380> beer<00:21:40.769> which<00:21:41.070> is 00:21:41.269 --> 00:21:41.279 align:start position:0% emerging such as life beer which is 00:21:41.279 --> 00:21:43.370 align:start position:0% emerging such as life beer which is going<00:21:41.519> to<00:21:41.789> be<00:21:41.940> live<00:21:42.389> video<00:21:42.960> and<00:21:43.200> audio 00:21:43.370 --> 00:21:43.380 align:start position:0% going to be live video and audio 00:21:43.380 --> 00:21:46.070 align:start position:0% going to be live video and audio streaming<00:21:43.889> using<00:21:44.279> swarm<00:21:44.909> as<00:21:45.149> a<00:21:45.480> transport 00:21:46.070 --> 00:21:46.080 align:start position:0% streaming using swarm as a transport 00:21:46.080 --> 00:21:50.299 align:start position:0% streaming using swarm as a transport layer<00:21:46.289> and<00:21:47.990> perhaps<00:21:48.990> it<00:21:49.529> is<00:21:49.740> also<00:21:49.919> worth 00:21:50.299 --> 00:21:50.309 align:start position:0% layer and perhaps it is also worth 00:21:50.309 --> 00:21:55.580 align:start position:0% layer and perhaps it is also worth mentioning<00:21:50.450> that<00:21:52.669> we<00:21:53.669> are<00:21:53.850> working<00:21:54.179> on<00:21:54.750> issues 00:21:55.580 --> 00:21:55.590 align:start position:0% mentioning that we are working on issues 00:21:55.590 --> 00:21:57.789 align:start position:0% mentioning that we are working on issues such<00:21:56.070> as<00:21:56.130> privacy<00:21:57.059> and<00:21:57.480> censorship 00:21:57.789 --> 00:21:57.799 align:start position:0% such as privacy and censorship 00:21:57.799 --> 00:22:02.649 align:start position:0% such as privacy and censorship resistance<00:21:58.799> so<00:21:59.250> that<00:22:00.710> we<00:22:01.710> can<00:22:01.950> actually 00:22:02.649 --> 00:22:02.659 align:start position:0% resistance so that we can actually 00:22:02.659 --> 00:22:08.690 align:start position:0% resistance so that we can actually support<00:22:04.610> sensitive<00:22:05.610> data<00:22:05.880> and<00:22:07.700> censorship 00:22:08.690 --> 00:22:08.700 align:start position:0% support sensitive data and censorship 00:22:08.700 --> 00:22:13.190 align:start position:0% support sensitive data and censorship resistant<00:22:09.389> communication<00:22:10.220> so<00:22:11.220> please<00:22:12.200> come 00:22:13.190 --> 00:22:13.200 align:start position:0% resistant communication so please come 00:22:13.200 --> 00:22:15.409 align:start position:0% resistant communication so please come to<00:22:13.230> our<00:22:13.440> talk<00:22:13.830> tomorrow 00:22:15.409 --> 00:22:15.419 align:start position:0% to our talk tomorrow 00:22:15.419 --> 00:22:18.080 align:start position:0% to our talk tomorrow and<00:22:15.750> also<00:22:16.289> our<00:22:16.620> breakout<00:22:17.070> session<00:22:17.580> is<00:22:17.789> on 00:22:18.080 --> 00:22:18.090 align:start position:0% and also our breakout session is on 00:22:18.090 --> 00:22:19.490 align:start position:0% and also our breakout session is on Saturday<00:22:18.510> I 00:22:19.490 --> 00:22:19.500 align:start position:0% Saturday I 00:22:19.500 --> 00:22:21.440 align:start position:0% Saturday I you 00:22:21.440 --> 00:22:21.450 align:start position:0% you 00:22:21.450 --> 00:22:26.290 align:start position:0% you [Applause] 00:22:26.290 --> 00:22:26.300 align:start position:0% [Applause] 00:22:26.300 --> 00:22:30.770 align:start position:0% [Applause] hello<00:22:27.300> I<00:22:27.570> am<00:22:28.380> vlog<00:22:28.710> Bukovsky<00:22:29.070> and<00:22:29.850> I<00:22:30.720> am 00:22:30.770 --> 00:22:30.780 align:start position:0% hello I am vlog Bukovsky and I am 00:22:30.780 --> 00:22:33.530 align:start position:0% hello I am vlog Bukovsky and I am working<00:22:30.990> on<00:22:31.170> whisper<00:22:31.940> which<00:22:32.940> is<00:22:33.180> a 00:22:33.530 --> 00:22:33.540 align:start position:0% working on whisper which is a 00:22:33.540 --> 00:22:36.860 align:start position:0% working on whisper which is a communication<00:22:34.380> protocol<00:22:34.830> for<00:22:35.870> distributed 00:22:36.860 --> 00:22:36.870 align:start position:0% communication protocol for distributed 00:22:36.870 --> 00:22:41.840 align:start position:0% communication protocol for distributed public<00:22:37.310> applications<00:22:38.310> and<00:22:40.070> it<00:22:41.070> it's<00:22:41.400> more 00:22:41.840 --> 00:22:41.850 align:start position:0% public applications and it it's more 00:22:41.850 --> 00:22:44.210 align:start position:0% public applications and it it's more secure<00:22:42.270> mode<00:22:42.570> of<00:22:42.750> operation<00:22:43.380> whisper<00:22:44.100> is 00:22:44.210 --> 00:22:44.220 align:start position:0% secure mode of operation whisper is 00:22:44.220 --> 00:22:48.530 align:start position:0% secure mode of operation whisper is supposed<00:22:44.580> to<00:22:44.730> deliver<00:22:45.390> darkness<00:22:47.300> which<00:22:48.300> means 00:22:48.530 --> 00:22:48.540 align:start position:0% supposed to deliver darkness which means 00:22:48.540 --> 00:22:51.760 align:start position:0% supposed to deliver darkness which means that<00:22:49.640> communication<00:22:50.640> is<00:22:50.760> not<00:22:50.940> only<00:22:51.180> encrypted 00:22:51.760 --> 00:22:51.770 align:start position:0% that communication is not only encrypted 00:22:51.770 --> 00:22:55.160 align:start position:0% that communication is not only encrypted but<00:22:52.770> also<00:22:53.010> not<00:22:53.640> no<00:22:54.120> meta<00:22:54.420> information<00:22:54.630> is 00:22:55.160 --> 00:22:55.170 align:start position:0% but also not no meta information is 00:22:55.170 --> 00:23:00.590 align:start position:0% but also not no meta information is being<00:22:55.350> leaked<00:22:56.060> and<00:22:58.760> this<00:22:59.760> is<00:22:59.910> very<00:23:00.120> important 00:23:00.590 --> 00:23:00.600 align:start position:0% being leaked and this is very important 00:23:00.600 --> 00:23:03.650 align:start position:0% being leaked and this is very important for<00:23:00.720> the<00:23:00.840> cause<00:23:01.020> of<00:23:01.050> Liberty<00:23:01.640> and<00:23:02.640> on<00:23:03.330> the<00:23:03.450> last 00:23:03.650 --> 00:23:03.660 align:start position:0% for the cause of Liberty and on the last 00:23:03.660 --> 00:23:06.260 align:start position:0% for the cause of Liberty and on the last day<00:23:03.900> I<00:23:04.200> am<00:23:04.860> going<00:23:05.160> to<00:23:05.280> talk<00:23:05.430> about<00:23:05.490> Liberty 00:23:06.260 --> 00:23:06.270 align:start position:0% day I am going to talk about Liberty 00:23:06.270 --> 00:23:09.440 align:start position:0% day I am going to talk about Liberty about<00:23:07.080> whisper<00:23:07.500> and<00:23:08.150> how<00:23:09.150> to<00:23:09.210> achieve 00:23:09.440 --> 00:23:09.450 align:start position:0% about whisper and how to achieve 00:23:09.450 --> 00:23:14.560 align:start position:0% about whisper and how to achieve darkness<00:23:09.990> with<00:23:10.170> it<00:23:10.320> thank<00:23:11.100> you 00:23:14.560 --> 00:23:14.570 align:start position:0% 00:23:14.570 --> 00:23:17.070 align:start position:0% [Applause] 00:23:17.070 --> 00:23:17.080 align:start position:0% [Applause] 00:23:17.080 --> 00:23:21.160 align:start position:0% [Applause] hi<00:23:18.080> everyone<00:23:18.380> I'm<00:23:18.770> Everton<00:23:19.430> I'm<00:23:20.000> from<00:23:20.270> Brazil 00:23:21.160 --> 00:23:21.170 align:start position:0% hi everyone I'm Everton I'm from Brazil 00:23:21.170 --> 00:23:24.340 align:start position:0% hi everyone I'm Everton I'm from Brazil I'm<00:23:21.710> from<00:23:21.980> the<00:23:22.070> maize<00:23:22.280> team<00:23:22.750> miss<00:23:23.750> was<00:23:24.020> first 00:23:24.340 --> 00:23:24.350 align:start position:0% I'm from the maize team miss was first 00:23:24.350 --> 00:23:26.620 align:start position:0% I'm from the maize team miss was first written<00:23:24.620> by<00:23:24.950> Fabian<00:23:25.490> bugger<00:23:25.820> stellar<00:23:26.120> here<00:23:26.540> am 00:23:26.620 --> 00:23:26.630 align:start position:0% written by Fabian bugger stellar here am 00:23:26.630 --> 00:23:27.820 align:start position:0% written by Fabian bugger stellar here am i<00:23:26.750> right 00:23:27.820 --> 00:23:27.830 align:start position:0% i right 00:23:27.830 --> 00:23:29.890 align:start position:0% i right and<00:23:28.160> alex<00:23:28.670> van<00:23:28.880> der<00:23:29.000> Sonny<00:23:29.240> who<00:23:29.480> couldn't<00:23:29.810> be 00:23:29.890 --> 00:23:29.900 align:start position:0% and alex van der Sonny who couldn't be 00:23:29.900 --> 00:23:31.900 align:start position:0% and alex van der Sonny who couldn't be here<00:23:29.930> for<00:23:30.500> personal<00:23:31.100> and<00:23:31.130> really<00:23:31.730> good 00:23:31.900 --> 00:23:31.910 align:start position:0% here for personal and really good 00:23:31.910 --> 00:23:36.970 align:start position:0% here for personal and really good reasons<00:23:32.350> I<00:23:33.460> work<00:23:34.460> this<00:23:35.300> year<00:23:35.690> on<00:23:35.980> bonding 00:23:36.970 --> 00:23:36.980 align:start position:0% reasons I work this year on bonding 00:23:36.980 --> 00:23:39.160 align:start position:0% reasons I work this year on bonding together<00:23:37.220> some<00:23:37.850> other<00:23:38.030> projects<00:23:38.720> into<00:23:39.050> the 00:23:39.160 --> 00:23:39.170 align:start position:0% together some other projects into the 00:23:39.170 --> 00:23:41.980 align:start position:0% together some other projects into the browser<00:23:39.410> and<00:23:40.330> dealing<00:23:41.330> with<00:23:41.360> some<00:23:41.690> security 00:23:41.980 --> 00:23:41.990 align:start position:0% browser and dealing with some security 00:23:41.990 --> 00:23:44.650 align:start position:0% browser and dealing with some security concerns<00:23:42.350> which<00:23:42.950> is<00:23:43.160> a<00:23:43.400> primary<00:23:43.790> one<00:23:44.240> for<00:23:44.570> us 00:23:44.650 --> 00:23:44.660 align:start position:0% concerns which is a primary one for us 00:23:44.660 --> 00:23:48.760 align:start position:0% concerns which is a primary one for us and<00:23:45.250> we<00:23:46.250> also<00:23:46.460> have<00:23:46.880> Victor<00:23:47.390> Maya<00:23:47.630> which<00:23:47.960> is<00:23:48.200> a 00:23:48.760 --> 00:23:48.770 align:start position:0% and we also have Victor Maya which is a 00:23:48.770 --> 00:23:51.040 align:start position:0% and we also have Victor Maya which is a really<00:23:49.370> skilled<00:23:49.730> developer<00:23:50.330> who<00:23:50.990> is 00:23:51.040 --> 00:23:51.050 align:start position:0% really skilled developer who is 00:23:51.050 --> 00:23:54.490 align:start position:0% really skilled developer who is presenting<00:23:51.800> a<00:23:52.160> new<00:23:53.020> experimental<00:23:54.020> project 00:23:54.490 --> 00:23:54.500 align:start position:0% presenting a new experimental project 00:23:54.500 --> 00:23:58.990 align:start position:0% presenting a new experimental project this<00:23:55.250> this<00:23:55.820> week<00:23:56.770> and<00:23:57.770> we<00:23:57.920> have<00:23:58.130> also<00:23:58.460> mark 00:23:58.990 --> 00:23:59.000 align:start position:0% this this week and we have also mark 00:23:59.000 --> 00:24:03.820 align:start position:0% this this week and we have also mark Guru<00:23:59.240> a<00:23:59.660> really<00:24:00.640> nice<00:24:01.640> guy<00:24:02.000> worked<00:24:02.720> with<00:24:03.020> Redux 00:24:03.820 --> 00:24:03.830 align:start position:0% Guru a really nice guy worked with Redux 00:24:03.830 --> 00:24:05.800 align:start position:0% Guru a really nice guy worked with Redux and<00:24:04.520> his<00:24:04.760> refactoring<00:24:05.420> mist 00:24:05.800 --> 00:24:05.810 align:start position:0% and his refactoring mist 00:24:05.810 --> 00:24:08.380 align:start position:0% and his refactoring mist to<00:24:06.140> to<00:24:06.980> be<00:24:07.100> more<00:24:07.280> scalable<00:24:07.670> one<00:24:08.000> for<00:24:08.300> the 00:24:08.380 --> 00:24:08.390 align:start position:0% to to be more scalable one for the 00:24:08.390 --> 00:24:09.870 align:start position:0% to to be more scalable one for the future 00:24:09.870 --> 00:24:09.880 align:start position:0% future 00:24:09.880 --> 00:24:12.970 align:start position:0% future well<00:24:10.880> I<00:24:11.090> invite<00:24:11.420> you<00:24:11.630> all<00:24:11.930> to<00:24:11.960> to<00:24:12.830> our 00:24:12.970 --> 00:24:12.980 align:start position:0% well I invite you all to to our 00:24:12.980 --> 00:24:16.620 align:start position:0% well I invite you all to to our presentation<00:24:13.580> on<00:24:13.940> the<00:24:14.240> main<00:24:14.270> hall<00:24:14.740> on<00:24:15.740> Friday 00:24:16.620 --> 00:24:16.630 align:start position:0% presentation on the main hall on Friday 00:24:16.630 --> 00:24:24.800 align:start position:0% presentation on the main hall on Friday 9:40<00:24:17.770> well<00:24:18.770> see<00:24:19.130> you<00:24:19.220> there 00:24:24.800 --> 00:24:24.810 align:start position:0% 00:24:24.810 --> 00:24:29.010 align:start position:0% hello<00:24:25.810> I'm<00:24:26.470> problem<00:24:26.800> for<00:24:26.980> estella<00:24:27.370> I<00:24:28.020> build 00:24:29.010 --> 00:24:29.020 align:start position:0% hello I'm problem for estella I build 00:24:29.020 --> 00:24:32.940 align:start position:0% hello I'm problem for estella I build the<00:24:29.380> initial<00:24:29.830> mist<00:24:30.370> and<00:24:30.840> working<00:24:31.840> on<00:24:31.960> web<00:24:32.170> 3GS 00:24:32.940 --> 00:24:32.950 align:start position:0% the initial mist and working on web 3GS 00:24:32.950 --> 00:24:34.740 align:start position:0% the initial mist and working on web 3GS I<00:24:32.980> also<00:24:33.370> built<00:24:33.580> a<00:24:33.760> fume<00:24:34.000> wallet<00:24:34.360> and<00:24:34.480> a<00:24:34.570> few 00:24:34.740 --> 00:24:34.750 align:start position:0% I also built a fume wallet and a few 00:24:34.750 --> 00:24:39.690 align:start position:0% I also built a fume wallet and a few other<00:24:34.900> things<00:24:36.900> probably<00:24:37.900> now<00:24:38.320> known<00:24:39.310> because 00:24:39.690 --> 00:24:39.700 align:start position:0% other things probably now known because 00:24:39.700 --> 00:24:43.760 align:start position:0% other things probably now known because of<00:24:39.730> the<00:24:40.180> ERC<00:24:41.170> 20<00:24:42.100> tokens<00:24:42.520> standard<00:24:42.910> I<00:24:43.090> took<00:24:43.450> a 00:24:43.760 --> 00:24:43.770 align:start position:0% of the ERC 20 tokens standard I took a 00:24:43.770 --> 00:24:48.810 align:start position:0% of the ERC 20 tokens standard I took a metallic<00:24:44.770> initiated<00:24:47.490> working<00:24:48.490> currently<00:24:48.760> in 00:24:48.810 --> 00:24:48.820 align:start position:0% metallic initiated working currently in 00:24:48.820 --> 00:24:50.730 align:start position:0% metallic initiated working currently in web<00:24:48.970> three.js<00:24:49.330> I<00:24:49.630> will<00:24:49.870> have<00:24:50.170> a<00:24:50.200> presentation 00:24:50.730 --> 00:24:50.740 align:start position:0% web three.js I will have a presentation 00:24:50.740 --> 00:24:54.960 align:start position:0% web three.js I will have a presentation on<00:24:51.070> the<00:24:51.250> third<00:24:51.550> at<00:24:51.940> 1:00<00:24:52.720> p.m.<00:24:52.750> about<00:24:53.650> the<00:24:54.160> 1.0 00:24:54.960 --> 00:24:54.970 align:start position:0% on the third at 1:00 p.m. about the 1.0 00:24:54.970 --> 00:24:57.120 align:start position:0% on the third at 1:00 p.m. about the 1.0 refactor<00:24:55.720> which<00:24:55.930> is<00:24:56.080> a<00:24:56.110> major<00:24:56.380> refactor<00:24:57.100> and 00:24:57.120 --> 00:24:57.130 align:start position:0% refactor which is a major refactor and 00:24:57.130 --> 00:24:58.680 align:start position:0% refactor which is a major refactor and it<00:24:57.460> actually<00:24:57.820> includes<00:24:58.000> a<00:24:58.270> lot<00:24:58.420> of<00:24:58.450> new 00:24:58.680 --> 00:24:58.690 align:start position:0% it actually includes a lot of new 00:24:58.690 --> 00:25:03.270 align:start position:0% it actually includes a lot of new features<00:24:58.870> and<00:24:59.490> it's<00:25:01.290> right<00:25:02.290> now<00:25:02.500> it's<00:25:02.860> I<00:25:03.220> think 00:25:03.270 --> 00:25:03.280 align:start position:0% features and it's right now it's I think 00:25:03.280 --> 00:25:06.470 align:start position:0% features and it's right now it's I think the<00:25:03.520> tool<00:25:04.350> which<00:25:05.350> I<00:25:05.470> always<00:25:05.740> wanted<00:25:06.040> to<00:25:06.100> have 00:25:06.470 --> 00:25:06.480 align:start position:0% the tool which I always wanted to have 00:25:06.480 --> 00:25:12.150 align:start position:0% the tool which I always wanted to have working<00:25:07.480> on<00:25:07.750> maps<00:25:08.170> and<00:25:09.330> I<00:25:10.680> will<00:25:11.680> also<00:25:11.980> present 00:25:12.150 --> 00:25:12.160 align:start position:0% working on maps and I will also present 00:25:12.160 --> 00:25:16.650 align:start position:0% working on maps and I will also present later<00:25:12.640> today<00:25:13.230> and<00:25:14.230> new<00:25:15.220> ERC<00:25:15.910> I<00:25:15.940> initiated 00:25:16.650 --> 00:25:16.660 align:start position:0% later today and new ERC I initiated 00:25:16.660 --> 00:25:20.400 align:start position:0% later today and new ERC I initiated called<00:25:17.470> ESC<00:25:18.160> 7<00:25:18.580> to<00:25:18.760> 5<00:25:19.000> it's<00:25:19.480> about<00:25:19.870> identity 00:25:20.400 --> 00:25:20.410 align:start position:0% called ESC 7 to 5 it's about identity 00:25:20.410 --> 00:25:23.550 align:start position:0% called ESC 7 to 5 it's about identity and<00:25:21.150> you're<00:25:22.150> welcome<00:25:22.360> to<00:25:22.510> join<00:25:22.630> the<00:25:23.170> breakout 00:25:23.550 --> 00:25:23.560 align:start position:0% and you're welcome to join the breakout 00:25:23.560 --> 00:25:30.110 align:start position:0% and you're welcome to join the breakout hall<00:25:23.860> at<00:25:24.270> 3:30<00:25:25.270> today<00:25:26.970> which<00:25:27.970> is<00:25:28.000> downstairs 00:25:30.110 --> 00:25:30.120 align:start position:0% hall at 3:30 today which is downstairs 00:25:30.120 --> 00:25:33.450 align:start position:0% hall at 3:30 today which is downstairs and<00:25:31.120> maybe<00:25:31.420> a<00:25:31.510> short<00:25:31.840> notice<00:25:32.020> the<00:25:32.560> the<00:25:33.040> Wi-Fi 00:25:33.450 --> 00:25:33.460 align:start position:0% and maybe a short notice the the Wi-Fi 00:25:33.460 --> 00:25:35.630 align:start position:0% and maybe a short notice the the Wi-Fi password<00:25:33.490> if<00:25:34.210> you<00:25:34.300> want<00:25:34.480> to<00:25:34.570> know<00:25:34.690> Wi-Fi<00:25:35.170> its 00:25:35.630 --> 00:25:35.640 align:start position:0% password if you want to know Wi-Fi its 00:25:35.640 --> 00:25:38.850 align:start position:0% password if you want to know Wi-Fi its attendee<00:25:36.640> is<00:25:36.880> the<00:25:37.150> Wi-Fi<00:25:37.840> name<00:25:38.110> and<00:25:38.410> it's<00:25:38.560> the 00:25:38.850 --> 00:25:38.860 align:start position:0% attendee is the Wi-Fi name and it's the 00:25:38.860 --> 00:25:43.260 align:start position:0% attendee is the Wi-Fi name and it's the uppercase<00:25:39.430> 3<00:25:40.210> attendee<00:25:40.810> lowercase<00:25:42.270> yeah 00:25:43.260 --> 00:25:43.270 align:start position:0% uppercase 3 attendee lowercase yeah 00:25:43.270 --> 00:25:45.720 align:start position:0% uppercase 3 attendee lowercase yeah thank<00:25:43.540> you 00:25:45.720 --> 00:25:45.730 align:start position:0% 00:25:45.730 --> 00:25:59.440 align:start position:0% [Applause] 00:25:59.440 --> 00:25:59.450 align:start position:0% 00:25:59.450 --> 00:26:02.300 align:start position:0% thank<00:26:00.450> you<00:26:00.600> all<00:26:00.840> and<00:26:01.230> thank<00:26:01.290> you<00:26:01.800> guys<00:26:02.250> for 00:26:02.300 --> 00:26:02.310 align:start position:0% thank you all and thank you guys for 00:26:02.310 --> 00:26:05.240 align:start position:0% thank you all and thank you guys for doing<00:26:02.640> this<00:26:03.210> on<00:26:03.420> time<00:26:03.660> we're<00:26:04.080> actually<00:26:04.980> we 00:26:05.240 --> 00:26:05.250 align:start position:0% doing this on time we're actually we 00:26:05.250 --> 00:26:07.360 align:start position:0% doing this on time we're actually we have<00:26:05.340> a<00:26:05.370> few<00:26:05.670> minutes<00:26:05.790> but<00:26:06.210> I'm<00:26:06.420> going<00:26:06.720> to 00:26:07.360 --> 00:26:07.370 align:start position:0% have a few minutes but I'm going to 00:26:07.370 --> 00:26:09.680 align:start position:0% have a few minutes but I'm going to invite<00:26:08.370> you<00:26:08.400> to<00:26:08.610> step<00:26:08.880> down<00:26:08.910> and<00:26:09.300> we'll<00:26:09.420> invite 00:26:09.680 --> 00:26:09.690 align:start position:0% invite you to step down and we'll invite 00:26:09.690 --> 00:26:13.070 align:start position:0% invite you to step down and we'll invite our<00:26:10.250> special<00:26:11.250> guest<00:26:11.520> speakers<00:26:11.970> for<00:26:12.450> to<00:26:12.810> start 00:26:13.070 --> 00:26:13.080 align:start position:0% our special guest speakers for to start 00:26:13.080 --> 00:26:16.490 align:start position:0% our special guest speakers for to start off<00:26:13.230> the<00:26:13.550> event<00:26:14.550> up<00:26:14.910> Jerry<00:26:15.780> Britt<00:26:16.080> oh<00:26:16.110> and 00:26:16.490 --> 00:26:16.500 align:start position:0% off the event up Jerry Britt oh and 00:26:16.500 --> 00:26:18.920 align:start position:0% off the event up Jerry Britt oh and Peter<00:26:16.830> Van<00:26:17.040> Valkenburg<00:26:17.220> of<00:26:17.850> coin<00:26:18.150> Center<00:26:18.630> are 00:26:18.920 --> 00:26:18.930 align:start position:0% Peter Van Valkenburg of coin Center are 00:26:18.930 --> 00:26:22.370 align:start position:0% Peter Van Valkenburg of coin Center are here<00:26:19.280> to<00:26:20.280> do<00:26:21.120> the<00:26:21.240> regulatory<00:26:21.630> update<00:26:22.230> and 00:26:22.370 --> 00:26:22.380 align:start position:0% here to do the regulatory update and 00:26:22.380 --> 00:26:24.590 align:start position:0% here to do the regulatory update and look<00:26:22.470> ahead<00:26:22.620> this<00:26:23.430> is<00:26:23.670> the<00:26:23.790> talk<00:26:24.030> by<00:26:24.270> coin 00:26:24.590 --> 00:26:24.600 align:start position:0% look ahead this is the talk by coin 00:26:24.600 --> 00:26:27.020 align:start position:0% look ahead this is the talk by coin Center<00:26:24.990> we<00:26:25.200> invited<00:26:25.710> them<00:26:25.920> last<00:26:26.220> year<00:26:26.400> to<00:26:26.700> also 00:26:27.020 --> 00:26:27.030 align:start position:0% Center we invited them last year to also 00:26:27.030 --> 00:26:29.300 align:start position:0% Center we invited them last year to also do<00:26:27.180> the<00:26:27.300> regulatory<00:26:27.690> talk<00:26:28.200> then<00:26:28.950> theorem 00:26:29.300 --> 00:26:29.310 align:start position:0% do the regulatory talk then theorem 00:26:29.310 --> 00:26:32.000 align:start position:0% do the regulatory talk then theorem foundation<00:26:30.000> takes<00:26:30.870> regulatory<00:26:31.650> and 00:26:32.000 --> 00:26:32.010 align:start position:0% foundation takes regulatory and 00:26:32.010 --> 00:26:34.850 align:start position:0% foundation takes regulatory and compliance<00:26:32.040> matters<00:26:32.790> very<00:26:33.120> seriously<00:26:33.470> so<00:26:34.470> we 00:26:34.850 --> 00:26:34.860 align:start position:0% compliance matters very seriously so we 00:26:34.860 --> 00:26:37.340 align:start position:0% compliance matters very seriously so we do<00:26:35.040> this<00:26:35.190> at<00:26:35.370> the<00:26:35.460> beginning<00:26:35.580> of<00:26:36.000> the<00:26:36.480> DEFCON 00:26:37.340 --> 00:26:37.350 align:start position:0% do this at the beginning of the DEFCON 00:26:37.350 --> 00:26:40.220 align:start position:0% do this at the beginning of the DEFCON event<00:26:37.650> and<00:26:37.980> then<00:26:38.580> after<00:26:38.970> that<00:26:39.150> we<00:26:39.510> have<00:26:39.720> a<00:26:39.750> full 00:26:40.220 --> 00:26:40.230 align:start position:0% event and then after that we have a full 00:26:40.230 --> 00:26:44.560 align:start position:0% event and then after that we have a full agenda<00:26:40.260> for<00:26:41.220> all<00:26:41.250> four<00:26:41.640> days<00:26:41.820> of<00:26:42.200> topics<00:26:43.200> on 00:26:44.560 --> 00:26:44.570 align:start position:0% agenda for all four days of topics on 00:26:44.570 --> 00:26:47.060 align:start position:0% agenda for all four days of topics on etherium<00:26:45.570> platform<00:26:46.050> development<00:26:46.470> base<00:26:46.800> layer 00:26:47.060 --> 00:26:47.070 align:start position:0% etherium platform development base layer 00:26:47.070 --> 00:26:50.270 align:start position:0% etherium platform development base layer development<00:26:47.900> researched<00:26:48.900> is<00:26:49.500> greatly 00:26:50.270 --> 00:26:50.280 align:start position:0% development researched is greatly 00:26:50.280 --> 00:26:53.000 align:start position:0% development researched is greatly happening<00:26:51.180> today<00:26:51.330> in<00:26:51.840> both<00:26:52.110> this<00:26:52.440> hall<00:26:52.710> and 00:26:53.000 --> 00:26:53.010 align:start position:0% happening today in both this hall and 00:26:53.010 --> 00:26:54.980 align:start position:0% happening today in both this hall and the<00:26:53.130> presentation<00:26:53.820> breakout<00:26:54.720> hall 00:26:54.980 --> 00:26:54.990 align:start position:0% the presentation breakout hall 00:26:54.990 --> 00:26:58.700 align:start position:0% the presentation breakout hall downstairs<00:26:55.590> on<00:26:55.830> the<00:26:55.920> second<00:26:56.250> floor<00:26:56.460> and<00:26:57.710> just 00:26:58.700 --> 00:26:58.710 align:start position:0% downstairs on the second floor and just 00:26:58.710 --> 00:27:00.560 align:start position:0% downstairs on the second floor and just generally<00:26:59.310> we<00:26:59.460> didn't<00:26:59.760> really<00:26:59.940> I<00:27:00.090> don't<00:27:00.420> will 00:27:00.560 --> 00:27:00.570 align:start position:0% generally we didn't really I don't will 00:27:00.570 --> 00:27:02.930 align:start position:0% generally we didn't really I don't will give<00:27:00.690> you<00:27:00.780> a<00:27:00.840> quick<00:27:01.170> overview<00:27:01.650> of<00:27:02.100> the<00:27:02.670> four 00:27:02.930 --> 00:27:02.940 align:start position:0% give you a quick overview of the four 00:27:02.940 --> 00:27:06.260 align:start position:0% give you a quick overview of the four days<00:27:03.180> so<00:27:03.660> today<00:27:04.620> many<00:27:05.220> of<00:27:05.340> its<00:27:05.550> the<00:27:05.880> subject 00:27:06.260 --> 00:27:06.270 align:start position:0% days so today many of its the subject 00:27:06.270 --> 00:27:08.890 align:start position:0% days so today many of its the subject the<00:27:06.330> subject<00:27:06.690> matter<00:27:06.840> of<00:27:06.990> the<00:27:07.440> talks<00:27:07.920> are 00:27:08.890 --> 00:27:08.900 align:start position:0% the subject matter of the talks are 00:27:08.900 --> 00:27:10.970 align:start position:0% the subject matter of the talks are there's<00:27:09.900> a<00:27:09.960> lot<00:27:10.110> of<00:27:10.230> research<00:27:10.560> there<00:27:10.890> are<00:27:10.950> a 00:27:10.970 --> 00:27:10.980 align:start position:0% there's a lot of research there are a 00:27:10.980 --> 00:27:12.290 align:start position:0% there's a lot of research there are a lot<00:27:11.070> of<00:27:11.190> research<00:27:11.460> talks<00:27:11.760> going<00:27:11.970> on<00:27:12.120> today 00:27:12.290 --> 00:27:12.300 align:start position:0% lot of research talks going on today 00:27:12.300 --> 00:27:16.130 align:start position:0% lot of research talks going on today tomorrow<00:27:13.260> we<00:27:13.740> have<00:27:13.980> core<00:27:14.760> development<00:27:15.360> and<00:27:15.630> a 00:27:16.130 --> 00:27:16.140 align:start position:0% tomorrow we have core development and a 00:27:16.140 --> 00:27:19.550 align:start position:0% tomorrow we have core development and a number<00:27:16.710> of<00:27:16.890> technical<00:27:17.340> talks<00:27:18.410> related<00:27:19.410> to 00:27:19.550 --> 00:27:19.560 align:start position:0% number of technical talks related to 00:27:19.560 --> 00:27:21.170 align:start position:0% number of technical talks related to core<00:27:19.770> development<00:27:20.130> platform<00:27:20.820> development 00:27:21.170 --> 00:27:21.180 align:start position:0% core development platform development 00:27:21.180 --> 00:27:23.510 align:start position:0% core development platform development and<00:27:21.600> base<00:27:22.290> layer<00:27:22.500> development<00:27:22.860> then<00:27:23.310> day 00:27:23.510 --> 00:27:23.520 align:start position:0% and base layer development then day 00:27:23.520 --> 00:27:26.090 align:start position:0% and base layer development then day three<00:27:23.910> we<00:27:24.120> have<00:27:24.390> we're<00:27:24.810> moving<00:27:25.170> into<00:27:25.320> DAPs<00:27:25.680> and 00:27:26.090 --> 00:27:26.100 align:start position:0% three we have we're moving into DAPs and 00:27:26.100 --> 00:27:31.010 align:start position:0% three we have we're moving into DAPs and tools<00:27:27.090> and<00:27:27.630> and<00:27:28.460> then<00:27:29.460> on<00:27:29.760> day<00:27:30.150> four<00:27:30.510> we<00:27:30.780> have<00:27:30.990> a 00:27:31.010 --> 00:27:31.020 align:start position:0% tools and and then on day four we have a 00:27:31.020 --> 00:27:33.590 align:start position:0% tools and and then on day four we have a number<00:27:31.530> of<00:27:31.770> topics<00:27:32.100> that<00:27:32.580> are<00:27:32.790> miscellaneous 00:27:33.590 --> 00:27:33.600 align:start position:0% number of topics that are miscellaneous 00:27:33.600 --> 00:27:35.720 align:start position:0% number of topics that are miscellaneous of<00:27:34.280> different<00:27:35.280> interests<00:27:35.580> and<00:27:35.640> different 00:27:35.720 --> 00:27:35.730 align:start position:0% of different interests and different 00:27:35.730 --> 00:27:38.480 align:start position:0% of different interests and different data<00:27:36.060> for<00:27:36.390> just<00:27:36.810> to<00:27:36.870> let<00:27:37.050> you<00:27:37.140> know<00:27:37.350> we<00:27:37.680> are 00:27:38.480 --> 00:27:38.490 align:start position:0% data for just to let you know we are 00:27:38.490 --> 00:27:41.150 align:start position:0% data for just to let you know we are moving<00:27:38.970> the<00:27:39.240> main<00:27:39.450> stage<00:27:39.860> downstairs<00:27:40.860> to<00:27:41.130> the 00:27:41.150 --> 00:27:41.160 align:start position:0% moving the main stage downstairs to the 00:27:41.160 --> 00:27:44.240 align:start position:0% moving the main stage downstairs to the Cozumel<00:27:41.640> so<00:27:42.540> we<00:27:42.960> have<00:27:43.170> this<00:27:43.380> room<00:27:43.680> today 00:27:44.240 --> 00:27:44.250 align:start position:0% Cozumel so we have this room today 00:27:44.250 --> 00:27:47.570 align:start position:0% Cozumel so we have this room today tomorrow<00:27:44.940> the<00:27:45.360> next<00:27:45.510> day<00:27:45.690> and<00:27:46.220> day<00:27:47.220> four<00:27:47.550> we 00:27:47.570 --> 00:27:47.580 align:start position:0% tomorrow the next day and day four we 00:27:47.580 --> 00:27:49.610 align:start position:0% tomorrow the next day and day four we will<00:27:47.970> be<00:27:48.060> self<00:27:48.330> contained<00:27:48.870> on<00:27:49.140> the<00:27:49.260> second 00:27:49.610 --> 00:27:49.620 align:start position:0% will be self contained on the second 00:27:49.620 --> 00:27:50.680 align:start position:0% will be self contained on the second floor<00:27:49.800> so 00:27:50.680 --> 00:27:50.690 align:start position:0% floor so 00:27:50.690 --> 00:27:58.049 align:start position:0% floor so [Music]