WEBVTT Kind: captions Language: en 00:00:04.690 --> 00:00:07.590 align:start position:0% I'm<00:00:05.440> Mohammed<00:00:06.279> Simba's<00:00:06.609> Effie<00:00:06.910> I've<00:00:07.359> been 00:00:07.590 --> 00:00:07.600 align:start position:0% I'm Mohammed Simba's Effie I've been 00:00:07.600 --> 00:00:11.010 align:start position:0% I'm Mohammed Simba's Effie I've been working<00:00:07.990> on<00:00:08.250> ephraim<00:00:09.250> since<00:00:09.730> two<00:00:10.360> years<00:00:10.389> ago 00:00:11.010 --> 00:00:11.020 align:start position:0% working on ephraim since two years ago 00:00:11.020 --> 00:00:14.490 align:start position:0% working on ephraim since two years ago and<00:00:11.490> first<00:00:12.490> on<00:00:12.879> ephraim<00:00:13.299> one<00:00:13.510> and<00:00:13.779> now<00:00:14.080> if<00:00:14.320> I<00:00:14.469> am 00:00:14.490 --> 00:00:14.500 align:start position:0% and first on ephraim one and now if I am 00:00:14.500 --> 00:00:19.230 align:start position:0% and first on ephraim one and now if I am to<00:00:14.889> and<00:00:15.279> I'm<00:00:16.209> part<00:00:16.900> of<00:00:17.369> terrorists<00:00:18.369> the<00:00:19.090> name 00:00:19.230 --> 00:00:19.240 align:start position:0% to and I'm part of terrorists the name 00:00:19.240 --> 00:00:23.029 align:start position:0% to and I'm part of terrorists the name is<00:00:19.359> team<00:00:19.539> so<00:00:20.410> most<00:00:21.370> of<00:00:21.490> you<00:00:21.700> know<00:00:22.180> studies<00:00:22.660> us 00:00:23.029 --> 00:00:23.039 align:start position:0% is team so most of you know studies us 00:00:23.039 --> 00:00:27.120 align:start position:0% is team so most of you know studies us for<00:00:24.039> free<00:00:24.190> things<00:00:24.570> the<00:00:25.570> messenger<00:00:26.020> the<00:00:26.800> web 00:00:27.120 --> 00:00:27.130 align:start position:0% for free things the messenger the web 00:00:27.130 --> 00:00:30.350 align:start position:0% for free things the messenger the web free<00:00:27.490> browser<00:00:27.850> and<00:00:28.720> also<00:00:28.930> the<00:00:29.260> browser<00:00:29.560> and 00:00:30.350 --> 00:00:30.360 align:start position:0% free browser and also the browser and 00:00:30.360 --> 00:00:33.869 align:start position:0% free browser and also the browser and the<00:00:31.360> wallet<00:00:31.690> on<00:00:31.960> mobile<00:00:32.680> but<00:00:33.399> we're<00:00:33.760> also 00:00:33.869 --> 00:00:33.879 align:start position:0% the wallet on mobile but we're also 00:00:33.879 --> 00:00:36.599 align:start position:0% the wallet on mobile but we're also involving<00:00:34.539> in<00:00:35.230> core<00:00:35.530> infrastructure<00:00:36.010> as<00:00:36.280> we 00:00:36.599 --> 00:00:36.609 align:start position:0% involving in core infrastructure as we 00:00:36.609 --> 00:00:41.299 align:start position:0% involving in core infrastructure as we eat<00:00:37.589> new<00:00:38.589> challenges<00:00:39.190> within<00:00:39.579> the<00:00:39.909> African 00:00:41.299 --> 00:00:41.309 align:start position:0% eat new challenges within the African 00:00:41.309 --> 00:00:45.419 align:start position:0% eat new challenges within the African ecosystem<00:00:42.309> so<00:00:43.409> the<00:00:44.409> main<00:00:44.620> one<00:00:44.859> I<00:00:45.100> will<00:00:45.280> be 00:00:45.419 --> 00:00:45.429 align:start position:0% ecosystem so the main one I will be 00:00:45.429 --> 00:00:50.009 align:start position:0% ecosystem so the main one I will be talking<00:00:45.839> today<00:00:46.839> is<00:00:47.229> a<00:00:47.559> frame<00:00:47.769> m2<00:00:48.179> so<00:00:49.179> at<00:00:49.659> first 00:00:50.009 --> 00:00:50.019 align:start position:0% talking today is a frame m2 so at first 00:00:50.019 --> 00:00:53.279 align:start position:0% talking today is a frame m2 so at first for<00:00:50.949> this<00:00:51.100> talk<00:00:51.370> I<00:00:51.609> had<00:00:51.909> a<00:00:51.940> big<00:00:52.329> plan<00:00:52.749> secret 00:00:53.279 --> 00:00:53.289 align:start position:0% for this talk I had a big plan secret 00:00:53.289 --> 00:00:56.610 align:start position:0% for this talk I had a big plan secret plan<00:00:53.589> to<00:00:54.059> come<00:00:55.059> like<00:00:55.329> Steve<00:00:55.629> Jobs<00:00:55.659> with<00:00:56.170> the 00:00:56.610 --> 00:00:56.620 align:start position:0% plan to come like Steve Jobs with the 00:00:56.620 --> 00:01:00.000 align:start position:0% plan to come like Steve Jobs with the new<00:00:56.739> iPhone<00:00:57.190> and<00:00:57.429> show<00:00:57.699> you<00:00:58.710> frm<00:00:59.710> to<00:00:59.859> on 00:01:00.000 --> 00:01:00.010 align:start position:0% new iPhone and show you frm to on 00:01:00.010 --> 00:01:02.329 align:start position:0% new iPhone and show you frm to on Raspberry<00:01:00.399> Pi<00:01:00.429> there's<00:01:01.329> another<00:01:01.600> one<00:01:01.870> behind 00:01:02.329 --> 00:01:02.339 align:start position:0% Raspberry Pi there's another one behind 00:01:02.339 --> 00:01:05.550 align:start position:0% Raspberry Pi there's another one behind but<00:01:03.339> this<00:01:04.059> was<00:01:04.269> revealed<00:01:04.629> one<00:01:05.170> month<00:01:05.379> ago 00:01:05.550 --> 00:01:05.560 align:start position:0% but this was revealed one month ago 00:01:05.560 --> 00:01:08.160 align:start position:0% but this was revealed one month ago drains<00:01:05.979> the<00:01:06.130> inter<00:01:06.430> up<00:01:06.549> in<00:01:06.729> Canada<00:01:07.090> and<00:01:07.299> all 00:01:08.160 --> 00:01:08.170 align:start position:0% drains the inter up in Canada and all 00:01:08.170 --> 00:01:11.039 align:start position:0% drains the inter up in Canada and all the<00:01:08.500> Twitter<00:01:09.009> sphere<00:01:09.820> was<00:01:10.240> all<00:01:10.659> over<00:01:10.899> the 00:01:11.039 --> 00:01:11.049 align:start position:0% the Twitter sphere was all over the 00:01:11.049 --> 00:01:13.350 align:start position:0% the Twitter sphere was all over the place<00:01:11.259> with<00:01:11.560> this<00:01:11.759> plus<00:01:12.759> what<00:01:13.060> happened<00:01:13.299> at 00:01:13.350 --> 00:01:13.360 align:start position:0% place with this plus what happened at 00:01:13.360 --> 00:01:15.929 align:start position:0% place with this plus what happened at the<00:01:13.479> interrupt<00:01:13.899> so<00:01:14.439> instead<00:01:15.250> of<00:01:15.310> talking 00:01:15.929 --> 00:01:15.939 align:start position:0% the interrupt so instead of talking 00:01:15.939 --> 00:01:20.969 align:start position:0% the interrupt so instead of talking about<00:01:16.439> that<00:01:17.439> I<00:01:18.299> want<00:01:19.299> to<00:01:19.539> take<00:01:20.409> a<00:01:20.439> step<00:01:20.770> back 00:01:20.969 --> 00:01:20.979 align:start position:0% about that I want to take a step back 00:01:20.979 --> 00:01:26.940 align:start position:0% about that I want to take a step back and<00:01:22.079> explain<00:01:24.539> why<00:01:25.539> this<00:01:25.600> is<00:01:25.960> important<00:01:26.409> for 00:01:26.940 --> 00:01:26.950 align:start position:0% and explain why this is important for 00:01:26.950 --> 00:01:29.370 align:start position:0% and explain why this is important for Ephraim<00:01:27.430> for<00:01:27.909> blockchain<00:01:28.390> and<00:01:28.570> also<00:01:29.109> for 00:01:29.370 --> 00:01:29.380 align:start position:0% Ephraim for blockchain and also for 00:01:29.380 --> 00:01:34.039 align:start position:0% Ephraim for blockchain and also for society<00:01:30.030> so<00:01:31.409> the<00:01:32.409> real<00:01:32.590> program<00:01:33.009> today<00:01:33.280> is 00:01:34.039 --> 00:01:34.049 align:start position:0% society so the real program today is 00:01:34.049 --> 00:01:36.529 align:start position:0% society so the real program today is while<00:01:35.049> running<00:01:35.229> on<00:01:35.469> the<00:01:35.530> PI<00:01:35.710> is<00:01:35.770> significant 00:01:36.529 --> 00:01:36.539 align:start position:0% while running on the PI is significant 00:01:36.539 --> 00:01:40.080 align:start position:0% while running on the PI is significant some<00:01:37.539> experiments<00:01:38.500> and<00:01:38.649> outcomes<00:01:39.640> feature 00:01:40.080 --> 00:01:40.090 align:start position:0% some experiments and outcomes feature 00:01:40.090 --> 00:01:43.620 align:start position:0% some experiments and outcomes feature and<00:01:40.450> unknowns<00:01:40.869> so<00:01:41.850> the<00:01:42.850> main<00:01:43.030> focus<00:01:43.390> will<00:01:43.600> be 00:01:43.620 --> 00:01:43.630 align:start position:0% and unknowns so the main focus will be 00:01:43.630 --> 00:01:46.230 align:start position:0% and unknowns so the main focus will be on<00:01:43.829> sustainability<00:01:44.829> and<00:01:45.399> energy<00:01:45.549> consumption 00:01:46.230 --> 00:01:46.240 align:start position:0% on sustainability and energy consumption 00:01:46.240 --> 00:01:50.130 align:start position:0% on sustainability and energy consumption which<00:01:46.990> one<00:01:47.229> which<00:01:47.679> was<00:01:48.359> one<00:01:49.359> of<00:01:49.390> the<00:01:49.810> main 00:01:50.130 --> 00:01:50.140 align:start position:0% which one which was one of the main 00:01:50.140 --> 00:01:52.050 align:start position:0% which one which was one of the main critic<00:01:50.590> of<00:01:50.770> blockchain<00:01:51.520> and<00:01:51.789> especially 00:01:52.050 --> 00:01:52.060 align:start position:0% critic of blockchain and especially 00:01:52.060 --> 00:01:57.029 align:start position:0% critic of blockchain and especially proof-of-work<00:01:53.189> so<00:01:54.189> without<00:01:54.909> further<00:01:55.119> ado<00:01:56.039> if 00:01:57.029 --> 00:01:57.039 align:start position:0% proof-of-work so without further ado if 00:01:57.039 --> 00:01:58.709 align:start position:0% proof-of-work so without further ado if you<00:01:57.249> were<00:01:57.429> this<00:01:57.909> morning<00:01:58.119> at<00:01:58.509> the 00:01:58.709 --> 00:01:58.719 align:start position:0% you were this morning at the 00:01:58.719 --> 00:02:01.260 align:start position:0% you were this morning at the introduction<00:01:59.409> talk<00:01:59.679> by<00:01:59.979> photonic<00:02:00.549> we<00:02:00.969> talked 00:02:01.260 --> 00:02:01.270 align:start position:0% introduction talk by photonic we talked 00:02:01.270 --> 00:02:03.239 align:start position:0% introduction talk by photonic we talked about<00:02:01.390> Byzantine<00:02:01.990> fault<00:02:02.259> tolerance<00:02:02.710> and<00:02:02.920> this 00:02:03.239 --> 00:02:03.249 align:start position:0% about Byzantine fault tolerance and this 00:02:03.249 --> 00:02:06.059 align:start position:0% about Byzantine fault tolerance and this paper<00:02:03.460> from<00:02:03.939> Lamport<00:02:04.659> in<00:02:04.749> 1982<00:02:05.560> which 00:02:06.059 --> 00:02:06.069 align:start position:0% paper from Lamport in 1982 which 00:02:06.069 --> 00:02:08.210 align:start position:0% paper from Lamport in 1982 which presented<00:02:06.340> the<00:02:06.789> Byzantine<00:02:07.359> general<00:02:07.689> problem 00:02:08.210 --> 00:02:08.220 align:start position:0% presented the Byzantine general problem 00:02:08.220 --> 00:02:12.210 align:start position:0% presented the Byzantine general problem which<00:02:09.220> was<00:02:09.429> about<00:02:10.170> how<00:02:11.170> to<00:02:11.230> reach<00:02:11.560> consensus 00:02:12.210 --> 00:02:12.220 align:start position:0% which was about how to reach consensus 00:02:12.220 --> 00:02:16.590 align:start position:0% which was about how to reach consensus between<00:02:13.650> life<00:02:14.650> if<00:02:14.980> you<00:02:15.280> all<00:02:15.550> are<00:02:15.820> generals<00:02:16.390> of 00:02:16.590 --> 00:02:16.600 align:start position:0% between life if you all are generals of 00:02:16.600 --> 00:02:17.360 align:start position:0% between life if you all are generals of an 00:02:17.360 --> 00:02:17.370 align:start position:0% an 00:02:17.370 --> 00:02:21.020 align:start position:0% an you<00:02:17.670> have<00:02:17.879> to<00:02:18.030> attack<00:02:18.299> a<00:02:18.510> city<00:02:18.780> and<00:02:19.459> maybe<00:02:20.459> you 00:02:21.020 --> 00:02:21.030 align:start position:0% you have to attack a city and maybe you 00:02:21.030 --> 00:02:23.720 align:start position:0% you have to attack a city and maybe you have<00:02:21.150> to<00:02:21.180> communicate<00:02:21.540> so<00:02:22.530> that<00:02:22.560> not<00:02:23.280> half<00:02:23.579> of 00:02:23.720 --> 00:02:23.730 align:start position:0% have to communicate so that not half of 00:02:23.730 --> 00:02:26.929 align:start position:0% have to communicate so that not half of you<00:02:24.349> attack<00:02:25.349> the<00:02:25.470> city<00:02:25.650> while<00:02:25.950> half<00:02:26.220> of<00:02:26.670> the 00:02:26.929 --> 00:02:26.939 align:start position:0% you attack the city while half of the 00:02:26.939 --> 00:02:29.690 align:start position:0% you attack the city while half of the other<00:02:27.090> retreat<00:02:27.599> and<00:02:27.780> you<00:02:28.349> come<00:02:28.769> to<00:02:29.069> a<00:02:29.340> strong 00:02:29.690 --> 00:02:29.700 align:start position:0% other retreat and you come to a strong 00:02:29.700 --> 00:02:32.899 align:start position:0% other retreat and you come to a strong decision<00:02:30.000> despite<00:02:30.920> spice<00:02:31.920> maybe<00:02:32.370> messenger 00:02:32.899 --> 00:02:32.909 align:start position:0% decision despite spice maybe messenger 00:02:32.909 --> 00:02:39.080 align:start position:0% decision despite spice maybe messenger dying<00:02:33.239> or<00:02:33.540> flee<00:02:34.290> and<00:02:37.010> one<00:02:38.010> of<00:02:38.220> the<00:02:38.940> main 00:02:39.080 --> 00:02:39.090 align:start position:0% dying or flee and one of the main 00:02:39.090 --> 00:02:42.229 align:start position:0% dying or flee and one of the main advancement<00:02:39.599> of<00:02:39.810> Bitcoin<00:02:40.319> was<00:02:40.799> using<00:02:41.670> proof 00:02:42.229 --> 00:02:42.239 align:start position:0% advancement of Bitcoin was using proof 00:02:42.239 --> 00:02:48.170 align:start position:0% advancement of Bitcoin was using proof of<00:02:42.739> costly<00:02:43.739> resources<00:02:44.370> work<00:02:46.099> to<00:02:47.099> help<00:02:47.760> solve 00:02:48.170 --> 00:02:48.180 align:start position:0% of costly resources work to help solve 00:02:48.180 --> 00:02:52.699 align:start position:0% of costly resources work to help solve this<00:02:48.620> this<00:02:49.620> general<00:02:50.040> problem<00:02:50.340> so<00:02:51.090> here<00:02:51.709> you 00:02:52.699 --> 00:02:52.709 align:start position:0% this this general problem so here you 00:02:52.709 --> 00:02:55.940 align:start position:0% this this general problem so here you have<00:02:52.890> I<00:02:53.579> suppose<00:02:54.450> one<00:02:54.930> of<00:02:54.959> the<00:02:55.290> first<00:02:55.709> mail 00:02:55.940 --> 00:02:55.950 align:start position:0% have I suppose one of the first mail 00:02:55.950 --> 00:03:00.140 align:start position:0% have I suppose one of the first mail that<00:02:56.159> introduced<00:02:57.739> Satoshi's<00:02:58.739> work<00:02:59.010> with<00:02:59.970> an 00:03:00.140 --> 00:03:00.150 align:start position:0% that introduced Satoshi's work with an 00:03:00.150 --> 00:03:05.059 align:start position:0% that introduced Satoshi's work with an example<00:03:00.450> of<00:03:01.099> attacking<00:03:02.389> I<00:03:03.470> don't<00:03:04.470> know<00:03:04.560> maybe 00:03:05.059 --> 00:03:05.069 align:start position:0% example of attacking I don't know maybe 00:03:05.069 --> 00:03:08.690 align:start position:0% example of attacking I don't know maybe your<00:03:05.370> company<00:03:06.230> through<00:03:07.230> and<00:03:07.590> trying<00:03:08.250> to<00:03:08.430> crack 00:03:08.690 --> 00:03:08.700 align:start position:0% your company through and trying to crack 00:03:08.700 --> 00:03:13.849 align:start position:0% your company through and trying to crack the<00:03:08.940> crypto<00:03:09.720> hashes<00:03:11.030> and<00:03:12.620> consulting<00:03:13.620> many 00:03:13.849 --> 00:03:13.859 align:start position:0% the crypto hashes and consulting many 00:03:13.859 --> 00:03:17.629 align:start position:0% the crypto hashes and consulting many attackers<00:03:14.310> for<00:03:14.549> that<00:03:16.099> the<00:03:17.099> main<00:03:17.250> point<00:03:17.489> is 00:03:17.629 --> 00:03:17.639 align:start position:0% attackers for that the main point is 00:03:17.639 --> 00:03:20.270 align:start position:0% attackers for that the main point is that<00:03:17.909> you<00:03:18.690> need<00:03:18.840> a<00:03:18.989> lot<00:03:19.139> of<00:03:19.170> compute<00:03:19.709> so<00:03:19.950> a<00:03:19.980> lot 00:03:20.270 --> 00:03:20.280 align:start position:0% that you need a lot of compute so a lot 00:03:20.280 --> 00:03:25.879 align:start position:0% that you need a lot of compute so a lot of<00:03:20.400> energy<00:03:20.909> to<00:03:21.060> do<00:03:21.180> that<00:03:21.359> and<00:03:24.739> to<00:03:25.739> introduce 00:03:25.879 --> 00:03:25.889 align:start position:0% of energy to do that and to introduce 00:03:25.889 --> 00:03:28.270 align:start position:0% of energy to do that and to introduce more<00:03:26.340> context<00:03:26.879> I<00:03:27.060> want<00:03:27.449> to<00:03:27.599> talk<00:03:27.810> about 00:03:28.270 --> 00:03:28.280 align:start position:0% more context I want to talk about 00:03:28.280 --> 00:03:32.210 align:start position:0% more context I want to talk about externalities<00:03:29.280> and<00:03:29.970> also<00:03:30.449> sustainability<00:03:31.319> so 00:03:32.210 --> 00:03:32.220 align:start position:0% externalities and also sustainability so 00:03:32.220 --> 00:03:35.720 align:start position:0% externalities and also sustainability so externality<00:03:33.030> is<00:03:33.269> an<00:03:34.109> economic<00:03:34.620> term<00:03:34.829> that 00:03:35.720 --> 00:03:35.730 align:start position:0% externality is an economic term that 00:03:35.730 --> 00:03:40.849 align:start position:0% externality is an economic term that explain<00:03:37.010> that<00:03:38.010> tells<00:03:38.280> you<00:03:39.109> it's<00:03:40.109> a<00:03:40.290> cost<00:03:40.560> or 00:03:40.849 --> 00:03:40.859 align:start position:0% explain that tells you it's a cost or 00:03:40.859 --> 00:03:43.460 align:start position:0% explain that tells you it's a cost or benefit<00:03:41.579> that<00:03:42.090> affects<00:03:42.419> a<00:03:42.540> party<00:03:42.930> who<00:03:43.199> did<00:03:43.319> not 00:03:43.460 --> 00:03:43.470 align:start position:0% benefit that affects a party who did not 00:03:43.470 --> 00:03:46.550 align:start position:0% benefit that affects a party who did not choose<00:03:43.769> to<00:03:43.799> incur<00:03:44.489> that<00:03:44.549> cost<00:03:44.730> or<00:03:45.239> benefit<00:03:45.690> so 00:03:46.550 --> 00:03:46.560 align:start position:0% choose to incur that cost or benefit so 00:03:46.560 --> 00:03:48.860 align:start position:0% choose to incur that cost or benefit so to<00:03:46.620> give<00:03:47.010> you<00:03:47.040> a<00:03:47.099> concrete<00:03:47.340> example<00:03:47.870> suppose 00:03:48.860 --> 00:03:48.870 align:start position:0% to give you a concrete example suppose 00:03:48.870 --> 00:03:51.680 align:start position:0% to give you a concrete example suppose there<00:03:49.530> is<00:03:49.650> a<00:03:49.680> factory<00:03:50.190> somewhere<00:03:50.519> that<00:03:51.329> pumps 00:03:51.680 --> 00:03:51.690 align:start position:0% there is a factory somewhere that pumps 00:03:51.690 --> 00:03:56.180 align:start position:0% there is a factory somewhere that pumps in<00:03:51.900> clean<00:03:52.650> water<00:03:52.919> and<00:03:54.410> exhausts<00:03:55.410> dirty<00:03:55.829> water 00:03:56.180 --> 00:03:56.190 align:start position:0% in clean water and exhausts dirty water 00:03:56.190 --> 00:03:59.030 align:start position:0% in clean water and exhausts dirty water downstream<00:03:57.049> people<00:03:58.049> downstream<00:03:58.470> didn't 00:03:59.030 --> 00:03:59.040 align:start position:0% downstream people downstream didn't 00:03:59.040 --> 00:04:01.729 align:start position:0% downstream people downstream didn't choose<00:03:59.340> to<00:03:59.579> have<00:03:59.819> dirty<00:04:00.030> water<00:04:00.359> and<00:04:00.650> they<00:04:01.650> are 00:04:01.729 --> 00:04:01.739 align:start position:0% choose to have dirty water and they are 00:04:01.739 --> 00:04:05.000 align:start position:0% choose to have dirty water and they are not<00:04:01.919> paid<00:04:02.250> to<00:04:02.720> clean<00:04:03.720> it<00:04:03.870> so<00:04:04.590> this<00:04:04.829> is<00:04:04.889> a 00:04:05.000 --> 00:04:05.010 align:start position:0% not paid to clean it so this is a 00:04:05.010 --> 00:04:08.210 align:start position:0% not paid to clean it so this is a negative<00:04:05.489> externality<00:04:05.970> on<00:04:06.690> the<00:04:07.440> other<00:04:07.709> hand<00:04:07.919> a 00:04:08.210 --> 00:04:08.220 align:start position:0% negative externality on the other hand a 00:04:08.220 --> 00:04:10.369 align:start position:0% negative externality on the other hand a positive<00:04:09.120> externality<00:04:09.329> would<00:04:09.840> be<00:04:09.989> the<00:04:10.199> same 00:04:10.369 --> 00:04:10.379 align:start position:0% positive externality would be the same 00:04:10.379 --> 00:04:14.390 align:start position:0% positive externality would be the same Factory<00:04:10.799> is<00:04:11.099> building<00:04:11.760> a<00:04:12.299> road<00:04:13.159> where<00:04:14.159> there 00:04:14.390 --> 00:04:14.400 align:start position:0% Factory is building a road where there 00:04:14.400 --> 00:04:16.640 align:start position:0% Factory is building a road where there were<00:04:14.549> none<00:04:14.879> before<00:04:15.030> and<00:04:15.569> all<00:04:15.989> the<00:04:16.199> villages 00:04:16.640 --> 00:04:16.650 align:start position:0% were none before and all the villages 00:04:16.650 --> 00:04:19.580 align:start position:0% were none before and all the villages and<00:04:16.799> the<00:04:16.889> city<00:04:17.479> along<00:04:18.479> those<00:04:18.750> road<00:04:18.989> benefits 00:04:19.580 --> 00:04:19.590 align:start position:0% and the city along those road benefits 00:04:19.590 --> 00:04:22.370 align:start position:0% and the city along those road benefits form<00:04:19.919> much<00:04:20.430> better<00:04:20.699> transportation<00:04:21.199> so<00:04:22.199> this 00:04:22.370 --> 00:04:22.380 align:start position:0% form much better transportation so this 00:04:22.380 --> 00:04:24.070 align:start position:0% form much better transportation so this is<00:04:22.470> a<00:04:22.500> positivist<00:04:22.979> analogy<00:04:23.490> and 00:04:24.070 --> 00:04:24.080 align:start position:0% is a positivist analogy and 00:04:24.080 --> 00:04:26.290 align:start position:0% is a positivist analogy and sustainability<00:04:25.080> I<00:04:25.200> guess 00:04:26.290 --> 00:04:26.300 align:start position:0% sustainability I guess 00:04:26.300 --> 00:04:29.000 align:start position:0% sustainability I guess now<00:04:27.300> everyone<00:04:27.810> is<00:04:28.020> familiar<00:04:28.230> with<00:04:28.500> the<00:04:28.680> term 00:04:29.000 --> 00:04:29.010 align:start position:0% now everyone is familiar with the term 00:04:29.010 --> 00:04:31.580 align:start position:0% now everyone is familiar with the term so<00:04:29.730> the<00:04:30.090> idea<00:04:30.420> is<00:04:30.600> that<00:04:30.780> it's<00:04:31.020> meeting<00:04:31.440> the 00:04:31.580 --> 00:04:31.590 align:start position:0% so the idea is that it's meeting the 00:04:31.590 --> 00:04:33.110 align:start position:0% so the idea is that it's meeting the needs<00:04:31.950> of<00:04:32.040> the<00:04:32.310> present<00:04:32.520> without 00:04:33.110 --> 00:04:33.120 align:start position:0% needs of the present without 00:04:33.120 --> 00:04:35.330 align:start position:0% needs of the present without compromising<00:04:34.110> the<00:04:34.140> ability<00:04:34.800> of<00:04:35.220> future 00:04:35.330 --> 00:04:35.340 align:start position:0% compromising the ability of future 00:04:35.340 --> 00:04:37.660 align:start position:0% compromising the ability of future generations<00:04:35.610> to<00:04:36.240> meet<00:04:36.690> the<00:04:36.960> needs 00:04:37.660 --> 00:04:37.670 align:start position:0% generations to meet the needs 00:04:37.670 --> 00:04:43.340 align:start position:0% generations to meet the needs how<00:04:38.670> does<00:04:38.850> that<00:04:38.880> play<00:04:39.240> in<00:04:39.510> a<00:04:39.870> frame<00:04:41.180> so<00:04:42.350> the 00:04:43.340 --> 00:04:43.350 align:start position:0% how does that play in a frame so the 00:04:43.350 --> 00:04:49.220 align:start position:0% how does that play in a frame so the public<00:04:44.660> opinion<00:04:45.660> is<00:04:45.870> that<00:04:46.620> a<00:04:47.270> lot<00:04:48.270> of<00:04:48.450> the 00:04:49.220 --> 00:04:49.230 align:start position:0% public opinion is that a lot of the 00:04:49.230 --> 00:04:53.260 align:start position:0% public opinion is that a lot of the proof<00:04:49.680> of<00:04:49.800> work<00:04:50.070> is<00:04:50.310> a<00:04:50.790> waste<00:04:51.090> of<00:04:51.300> energy<00:04:51.540> and 00:04:53.260 --> 00:04:53.270 align:start position:0% proof of work is a waste of energy and 00:04:53.270 --> 00:04:57.140 align:start position:0% proof of work is a waste of energy and that's<00:04:54.270> an<00:04:54.480> issue<00:04:54.770> there<00:04:55.770> is<00:04:55.890> this<00:04:56.340> EU 00:04:57.140 --> 00:04:57.150 align:start position:0% that's an issue there is this EU 00:04:57.150 --> 00:05:00.080 align:start position:0% that's an issue there is this EU blockchain<00:04:57.630> Observatory<00:04:58.350> report<00:04:58.880> that<00:04:59.880> was 00:05:00.080 --> 00:05:00.090 align:start position:0% blockchain Observatory report that was 00:05:00.090 --> 00:05:01.880 align:start position:0% blockchain Observatory report that was sent<00:05:00.450> to<00:05:00.540> the<00:05:00.690> European<00:05:01.170> Commission<00:05:01.680> that 00:05:01.880 --> 00:05:01.890 align:start position:0% sent to the European Commission that 00:05:01.890 --> 00:05:05.480 align:start position:0% sent to the European Commission that said<00:05:02.340> that<00:05:02.690> proof-of-work<00:05:04.010> consumes<00:05:05.010> as<00:05:05.280> much 00:05:05.480 --> 00:05:05.490 align:start position:0% said that proof-of-work consumes as much 00:05:05.490 --> 00:05:07.520 align:start position:0% said that proof-of-work consumes as much energy<00:05:05.910> per<00:05:06.390> day<00:05:06.570> as<00:05:06.810> the<00:05:07.080> country<00:05:07.410> of 00:05:07.520 --> 00:05:07.530 align:start position:0% energy per day as the country of 00:05:07.530 --> 00:05:10.970 align:start position:0% energy per day as the country of Singapore<00:05:08.690> it's<00:05:09.690> not<00:05:09.900> shown<00:05:10.170> in<00:05:10.440> the<00:05:10.710> slide 00:05:10.970 --> 00:05:10.980 align:start position:0% Singapore it's not shown in the slide 00:05:10.980 --> 00:05:14.720 align:start position:0% Singapore it's not shown in the slide but<00:05:12.260> they<00:05:13.260> said<00:05:13.500> that<00:05:13.680> there<00:05:13.980> are<00:05:14.070> lots<00:05:14.610> of 00:05:14.720 --> 00:05:14.730 align:start position:0% but they said that there are lots of 00:05:14.730 --> 00:05:16.670 align:start position:0% but they said that there are lots of work<00:05:15.000> in<00:05:15.030> progress<00:05:15.390> to<00:05:15.780> improve<00:05:16.200> that<00:05:16.440> and 00:05:16.670 --> 00:05:16.680 align:start position:0% work in progress to improve that and 00:05:16.680 --> 00:05:19.070 align:start position:0% work in progress to improve that and that<00:05:17.400> thankfully<00:05:18.000> the<00:05:18.270> blockchain<00:05:18.480> community 00:05:19.070 --> 00:05:19.080 align:start position:0% that thankfully the blockchain community 00:05:19.080 --> 00:05:21.490 align:start position:0% that thankfully the blockchain community is<00:05:19.230> aware<00:05:19.710> of<00:05:19.740> the<00:05:20.280> energy<00:05:20.640> consumption<00:05:21.120> and 00:05:21.490 --> 00:05:21.500 align:start position:0% is aware of the energy consumption and 00:05:21.500 --> 00:05:27.530 align:start position:0% is aware of the energy consumption and wants<00:05:22.500> to<00:05:22.620> tackle<00:05:22.830> that<00:05:24.170> another<00:05:26.030> paper<00:05:27.030> was 00:05:27.530 --> 00:05:27.540 align:start position:0% wants to tackle that another paper was 00:05:27.540 --> 00:05:31.159 align:start position:0% wants to tackle that another paper was in<00:05:28.100> magazine<00:05:29.100> nature<00:05:29.340> and<00:05:29.820> that<00:05:30.690> said<00:05:30.960> that 00:05:31.159 --> 00:05:31.169 align:start position:0% in magazine nature and that said that 00:05:31.169 --> 00:05:34.730 align:start position:0% in magazine nature and that said that blockchain<00:05:31.860> may<00:05:32.160> might<00:05:32.669> contribute<00:05:33.740> to 00:05:34.730 --> 00:05:34.740 align:start position:0% blockchain may might contribute to 00:05:34.740 --> 00:05:39.050 align:start position:0% blockchain may might contribute to global<00:05:35.070> warming<00:05:35.640> by<00:05:35.880> 2<00:05:36.270> degrees<00:05:36.750> Celsius<00:05:38.060> the 00:05:39.050 --> 00:05:39.060 align:start position:0% global warming by 2 degrees Celsius the 00:05:39.060 --> 00:05:41.690 align:start position:0% global warming by 2 degrees Celsius the paper<00:05:39.270> is<00:05:39.600> the<00:05:40.500> code<00:05:40.740> behind<00:05:40.980> the<00:05:41.250> paper<00:05:41.430> is 00:05:41.690 --> 00:05:41.700 align:start position:0% paper is the code behind the paper is 00:05:41.700 --> 00:05:43.640 align:start position:0% paper is the code behind the paper is actually<00:05:42.090> public<00:05:42.419> which<00:05:42.870> is<00:05:42.900> a<00:05:43.290> very<00:05:43.470> good 00:05:43.640 --> 00:05:43.650 align:start position:0% actually public which is a very good 00:05:43.650 --> 00:05:46.909 align:start position:0% actually public which is a very good thing<00:05:43.890> and<00:05:44.070> if<00:05:44.940> you<00:05:45.120> want<00:05:45.360> you<00:05:46.260> can<00:05:46.470> check<00:05:46.740> out 00:05:46.909 --> 00:05:46.919 align:start position:0% thing and if you want you can check out 00:05:46.919 --> 00:05:50.780 align:start position:0% thing and if you want you can check out how<00:05:47.220> they<00:05:48.080> arrive<00:05:49.080> to<00:05:49.110> those<00:05:49.500> estimates<00:05:50.100> you 00:05:50.780 --> 00:05:50.790 align:start position:0% how they arrive to those estimates you 00:05:50.790 --> 00:05:53.000 align:start position:0% how they arrive to those estimates you can<00:05:50.940> also<00:05:51.120> do<00:05:51.360> your<00:05:51.510> own<00:05:51.750> you<00:05:52.470> can<00:05:52.710> criticize 00:05:53.000 --> 00:05:53.010 align:start position:0% can also do your own you can criticize 00:05:53.010 --> 00:05:56.570 align:start position:0% can also do your own you can criticize it<00:05:53.490> put<00:05:53.880> a<00:05:53.910> PR<00:05:54.360> or<00:05:54.600> an<00:05:54.840> issue<00:05:55.070> but<00:05:56.070> I'm<00:05:56.250> not<00:05:56.370> here 00:05:56.570 --> 00:05:56.580 align:start position:0% it put a PR or an issue but I'm not here 00:05:56.580 --> 00:05:59.900 align:start position:0% it put a PR or an issue but I'm not here to<00:05:56.610> talk<00:05:57.060> about<00:05:57.450> if<00:05:57.840> it's<00:05:58.470> to<00:05:58.890> degree<00:05:59.190> or<00:05:59.430> 1.5 00:05:59.900 --> 00:05:59.910 align:start position:0% to talk about if it's to degree or 1.5 00:05:59.910 --> 00:06:02.720 align:start position:0% to talk about if it's to degree or 1.5 or<00:06:00.270> maybe<00:06:00.419> one<00:06:00.750> or<00:06:01.050> maybe<00:06:01.230> three<00:06:01.620> I<00:06:01.919> want<00:06:02.430> it<00:06:02.610> to 00:06:02.720 --> 00:06:02.730 align:start position:0% or maybe one or maybe three I want it to 00:06:02.730 --> 00:06:06.320 align:start position:0% or maybe one or maybe three I want it to be<00:06:02.850> zero<00:06:03.150> or<00:06:03.419> maybe<00:06:03.780> even<00:06:03.870> negative<00:06:04.669> like<00:06:05.669> if 00:06:06.320 --> 00:06:06.330 align:start position:0% be zero or maybe even negative like if 00:06:06.330 --> 00:06:07.970 align:start position:0% be zero or maybe even negative like if we<00:06:06.540> have<00:06:06.630> more<00:06:06.810> efficient<00:06:07.169> carbon<00:06:07.500> market 00:06:07.970 --> 00:06:07.980 align:start position:0% we have more efficient carbon market 00:06:07.980 --> 00:06:14.470 align:start position:0% we have more efficient carbon market with<00:06:08.340> the<00:06:08.460> blockchain<00:06:12.980> another<00:06:13.980> negative 00:06:14.470 --> 00:06:14.480 align:start position:0% with the blockchain another negative 00:06:14.480 --> 00:06:18.290 align:start position:0% with the blockchain another negative externality<00:06:15.480> is<00:06:15.950> the<00:06:16.950> space<00:06:17.220> used<00:06:17.580> so<00:06:18.000> this<00:06:18.180> is 00:06:18.290 --> 00:06:18.300 align:start position:0% externality is the space used so this is 00:06:18.300 --> 00:06:21.860 align:start position:0% externality is the space used so this is an<00:06:18.419> image<00:06:18.690> of<00:06:19.100> Iceland<00:06:20.100> US<00:06:21.000> Air<00:06:21.240> Force<00:06:21.600> Base 00:06:21.860 --> 00:06:21.870 align:start position:0% an image of Iceland US Air Force Base 00:06:21.870 --> 00:06:24.020 align:start position:0% an image of Iceland US Air Force Base that<00:06:22.200> was<00:06:22.860> completely<00:06:23.250> transformed<00:06:23.730> into<00:06:23.910> a 00:06:24.020 --> 00:06:24.030 align:start position:0% that was completely transformed into a 00:06:24.030 --> 00:06:28.790 align:start position:0% that was completely transformed into a Bitcoin<00:06:24.480> farm<00:06:24.780> and<00:06:25.970> I<00:06:26.970> guess<00:06:27.540> space<00:06:28.169> today<00:06:28.500> is 00:06:28.790 --> 00:06:28.800 align:start position:0% Bitcoin farm and I guess space today is 00:06:28.800 --> 00:06:30.770 align:start position:0% Bitcoin farm and I guess space today is at<00:06:29.010> a<00:06:29.040> premium<00:06:29.340> with<00:06:29.760> many<00:06:29.970> country<00:06:30.419> like 00:06:30.770 --> 00:06:30.780 align:start position:0% at a premium with many country like 00:06:30.780 --> 00:06:33.110 align:start position:0% at a premium with many country like Japan<00:06:31.020> who<00:06:31.710> are<00:06:31.860> struggling<00:06:32.160> to<00:06:32.520> get<00:06:32.760> space 00:06:33.110 --> 00:06:33.120 align:start position:0% Japan who are struggling to get space 00:06:33.120 --> 00:06:38.100 align:start position:0% Japan who are struggling to get space either<00:06:33.480> for<00:06:33.900> food<00:06:34.140> or<00:06:34.350> for<00:06:34.410> people 00:06:38.100 --> 00:06:38.110 align:start position:0% 00:06:38.110 --> 00:06:43.439 align:start position:0% so<00:06:39.960> just<00:06:40.960> to<00:06:41.229> not<00:06:41.800> be<00:06:42.009> always<00:06:42.340> negative<00:06:42.729> there 00:06:43.439 --> 00:06:43.449 align:start position:0% so just to not be always negative there 00:06:43.449 --> 00:06:46.290 align:start position:0% so just to not be always negative there are<00:06:43.539> also<00:06:43.810> positive<00:06:44.199> externalities<00:06:45.039> in<00:06:45.300> the 00:06:46.290 --> 00:06:46.300 align:start position:0% are also positive externalities in the 00:06:46.300 --> 00:06:48.480 align:start position:0% are also positive externalities in the blockchain<00:06:46.539> space<00:06:46.960> so<00:06:47.620> we<00:06:47.770> have<00:06:47.919> all<00:06:48.159> these 00:06:48.480 --> 00:06:48.490 align:start position:0% blockchain space so we have all these 00:06:48.490 --> 00:06:51.059 align:start position:0% blockchain space so we have all these permissionless<00:06:49.150> trustless<00:06:50.169> decentralized 00:06:51.059 --> 00:06:51.069 align:start position:0% permissionless trustless decentralized 00:06:51.069 --> 00:06:53.339 align:start position:0% permissionless trustless decentralized transparent<00:06:52.060> and<00:06:52.240> so<00:06:52.419> ship<00:06:52.750> resistant<00:06:53.169> that 00:06:53.339 --> 00:06:53.349 align:start position:0% transparent and so ship resistant that 00:06:53.349 --> 00:06:58.050 align:start position:0% transparent and so ship resistant that everyone<00:06:54.340> knows<00:06:54.750> but<00:06:55.750> also<00:06:56.050> who<00:06:57.039> heard<00:06:57.879> about 00:06:58.050 --> 00:06:58.060 align:start position:0% everyone knows but also who heard about 00:06:58.060 --> 00:07:00.959 align:start position:0% everyone knows but also who heard about formal<00:06:58.659> verification<00:06:58.840> before<00:06:59.680> hearing<00:07:00.490> about 00:07:00.959 --> 00:07:00.969 align:start position:0% formal verification before hearing about 00:07:00.969 --> 00:07:01.980 align:start position:0% formal verification before hearing about blockchain<00:07:01.270> here 00:07:01.980 --> 00:07:01.990 align:start position:0% blockchain here 00:07:01.990 --> 00:07:07.200 align:start position:0% blockchain here Oh<00:07:02.370> first<00:07:03.370> one<00:07:04.349> well<00:07:05.430> blockchain<00:07:06.430> is<00:07:06.669> also 00:07:07.200 --> 00:07:07.210 align:start position:0% Oh first one well blockchain is also 00:07:07.210 --> 00:07:10.080 align:start position:0% Oh first one well blockchain is also driving<00:07:07.750> all<00:07:07.960> the<00:07:08.229> innovation<00:07:08.860> in<00:07:09.729> formal 00:07:10.080 --> 00:07:10.090 align:start position:0% driving all the innovation in formal 00:07:10.090 --> 00:07:12.240 align:start position:0% driving all the innovation in formal verification<00:07:10.270> for<00:07:10.870> software<00:07:11.250> formal 00:07:12.240 --> 00:07:12.250 align:start position:0% verification for software formal 00:07:12.250 --> 00:07:14.309 align:start position:0% verification for software formal verification<00:07:12.400> has<00:07:12.819> been<00:07:13.030> used<00:07:13.360> by<00:07:13.509> Intel<00:07:14.139> for 00:07:14.309 --> 00:07:14.319 align:start position:0% verification has been used by Intel for 00:07:14.319 --> 00:07:16.860 align:start position:0% verification has been used by Intel for example<00:07:14.710> for<00:07:15.009> the<00:07:15.580> past<00:07:15.849> 20<00:07:16.300> years<00:07:16.330> for 00:07:16.860 --> 00:07:16.870 align:start position:0% example for the past 20 years for 00:07:16.870 --> 00:07:21.209 align:start position:0% example for the past 20 years for hardware<00:07:17.620> but<00:07:18.219> this<00:07:18.520> is<00:07:18.639> very<00:07:18.879> new<00:07:19.180> and<00:07:20.219> thanks 00:07:21.209 --> 00:07:21.219 align:start position:0% hardware but this is very new and thanks 00:07:21.219 --> 00:07:22.320 align:start position:0% hardware but this is very new and thanks to<00:07:21.340> blockchain<00:07:21.669> that<00:07:21.849> formal<00:07:22.150> verification 00:07:22.320 --> 00:07:22.330 align:start position:0% to blockchain that formal verification 00:07:22.330 --> 00:07:24.240 align:start position:0% to blockchain that formal verification is<00:07:22.750> used<00:07:23.050> for<00:07:23.440> software<00:07:23.770> and<00:07:24.039> there<00:07:24.159> are 00:07:24.240 --> 00:07:24.250 align:start position:0% is used for software and there are 00:07:24.250 --> 00:07:26.909 align:start position:0% is used for software and there are others<00:07:24.610> like<00:07:24.759> game<00:07:25.360> theory<00:07:25.919> cryptography 00:07:26.909 --> 00:07:26.919 align:start position:0% others like game theory cryptography 00:07:26.919 --> 00:07:31.170 align:start position:0% others like game theory cryptography that<00:07:27.099> are<00:07:27.400> being<00:07:27.610> driven<00:07:27.909> by<00:07:28.330> blockchain<00:07:30.180> so 00:07:31.170 --> 00:07:31.180 align:start position:0% that are being driven by blockchain so 00:07:31.180 --> 00:07:34.649 align:start position:0% that are being driven by blockchain so now<00:07:31.750> let's<00:07:32.500> go<00:07:32.650> back<00:07:32.800> to<00:07:32.919> a<00:07:32.979> frame<00:07:33.190> -<00:07:33.520> if<00:07:34.060> I<00:07:34.300> am<00:07:34.389> - 00:07:34.649 --> 00:07:34.659 align:start position:0% now let's go back to a frame - if I am - 00:07:34.659 --> 00:07:38.300 align:start position:0% now let's go back to a frame - if I am - we<00:07:35.590> change<00:07:35.949> is<00:07:36.219> the<00:07:36.400> proof<00:07:36.699> of<00:07:36.849> work<00:07:37.090> the 00:07:38.300 --> 00:07:38.310 align:start position:0% we change is the proof of work the 00:07:38.310 --> 00:07:41.550 align:start position:0% we change is the proof of work the wasteful<00:07:39.310> algorithm<00:07:40.150> like<00:07:40.569> the<00:07:40.719> public<00:07:41.080> may 00:07:41.550 --> 00:07:41.560 align:start position:0% wasteful algorithm like the public may 00:07:41.560 --> 00:07:46.830 align:start position:0% wasteful algorithm like the public may want<00:07:42.009> to<00:07:42.099> call<00:07:42.340> it<00:07:42.490> -<00:07:43.389> ever<00:07:43.960> itself<00:07:44.469> so<00:07:45.270> now<00:07:46.270> we 00:07:46.830 --> 00:07:46.840 align:start position:0% want to call it - ever itself so now we 00:07:46.840 --> 00:07:49.980 align:start position:0% want to call it - ever itself so now we can<00:07:46.990> run<00:07:47.110> it<00:07:47.259> on<00:07:47.469> that<00:07:48.029> something<00:07:49.029> that<00:07:49.240> can 00:07:49.980 --> 00:07:49.990 align:start position:0% can run it on that something that can 00:07:49.990 --> 00:07:52.820 align:start position:0% can run it on that something that can fit<00:07:50.319> into<00:07:50.680> my<00:07:50.979> hand 00:07:52.820 --> 00:07:52.830 align:start position:0% fit into my hand 00:07:52.830 --> 00:07:56.459 align:start position:0% fit into my hand we<00:07:53.830> go<00:07:53.979> from<00:07:54.250> a<00:07:54.310> big<00:07:54.699> data<00:07:55.029> center<00:07:55.479> to<00:07:56.349> the 00:07:56.459 --> 00:07:56.469 align:start position:0% we go from a big data center to the 00:07:56.469 --> 00:08:01.529 align:start position:0% we go from a big data center to the small<00:07:56.680> frame<00:07:58.949> I've<00:07:59.949> been<00:08:00.219> running<00:08:00.550> tests<00:08:01.029> in 00:08:01.529 --> 00:08:01.539 align:start position:0% small frame I've been running tests in 00:08:01.539 --> 00:08:02.129 align:start position:0% small frame I've been running tests in the<00:08:01.779> past 00:08:02.129 --> 00:08:02.139 align:start position:0% the past 00:08:02.139 --> 00:08:06.089 align:start position:0% the past Monza's<00:08:02.710> on<00:08:02.979> the<00:08:03.339> raspberry<00:08:03.789> pi<00:08:03.819> 4<00:08:04.360> so<00:08:05.099> this 00:08:06.089 --> 00:08:06.099 align:start position:0% Monza's on the raspberry pi 4 so this 00:08:06.099 --> 00:08:09.300 align:start position:0% Monza's on the raspberry pi 4 so this one<00:08:06.250> is<00:08:06.339> raspberry<00:08:06.639> pi<00:08:07.000> 3<00:08:07.389> and<00:08:07.860> raspberry<00:08:08.860> pi<00:08:09.009> 4 00:08:09.300 --> 00:08:09.310 align:start position:0% one is raspberry pi 3 and raspberry pi 4 00:08:09.310 --> 00:08:12.089 align:start position:0% one is raspberry pi 3 and raspberry pi 4 was<00:08:09.550> out<00:08:10.029> in<00:08:10.479> june<00:08:10.930> i<00:08:11.139> think<00:08:11.379> a<00:08:11.589> bit<00:08:11.860> more 00:08:12.089 --> 00:08:12.099 align:start position:0% was out in june i think a bit more 00:08:12.099 --> 00:08:16.740 align:start position:0% was out in june i think a bit more powerful<00:08:12.990> -<00:08:13.990> gigabyte<00:08:14.379> of<00:08:14.560> ram<00:08:14.919> i<00:08:15.539> use<00:08:16.539> the 00:08:16.740 --> 00:08:16.750 align:start position:0% powerful - gigabyte of ram i use the 00:08:16.750 --> 00:08:20.040 align:start position:0% powerful - gigabyte of ram i use the default<00:08:17.259> distribution<00:08:17.919> so<00:08:18.610> that<00:08:18.839> people<00:08:19.839> can 00:08:20.040 --> 00:08:20.050 align:start position:0% default distribution so that people can 00:08:20.050 --> 00:08:24.719 align:start position:0% default distribution so that people can reproduce<00:08:20.409> it<00:08:20.770> and<00:08:22.589> Nimbus<00:08:23.589> Zoe<00:08:24.250> for<00:08:24.460> him<00:08:24.580> to 00:08:24.719 --> 00:08:24.729 align:start position:0% reproduce it and Nimbus Zoe for him to 00:08:24.729 --> 00:08:27.809 align:start position:0% reproduce it and Nimbus Zoe for him to client<00:08:25.089> called<00:08:25.330> name<00:08:25.539> becomes<00:08:25.839> in<00:08:26.819> the 00:08:27.809 --> 00:08:27.819 align:start position:0% client called name becomes in the 00:08:27.819 --> 00:08:30.329 align:start position:0% client called name becomes in the configuration<00:08:28.360> I<00:08:28.479> used<00:08:28.779> was<00:08:29.169> called<00:08:29.339> minimal 00:08:30.329 --> 00:08:30.339 align:start position:0% configuration I used was called minimal 00:08:30.339 --> 00:08:33.659 align:start position:0% configuration I used was called minimal this<00:08:30.759> is<00:08:30.909> what<00:08:31.060> we<00:08:31.210> use<00:08:31.360> for<00:08:31.389> interrupts<00:08:32.669> we 00:08:33.659 --> 00:08:33.669 align:start position:0% this is what we use for interrupts we 00:08:33.669 --> 00:08:36.029 align:start position:0% this is what we use for interrupts we also<00:08:33.849> have<00:08:34.089> a<00:08:34.120> main<00:08:34.419> net<00:08:34.630> one<00:08:34.839> I<00:08:35.079> used<00:08:35.589> minimal 00:08:36.029 --> 00:08:36.039 align:start position:0% also have a main net one I used minimal 00:08:36.039 --> 00:08:39.870 align:start position:0% also have a main net one I used minimal because<00:08:36.779> unfortunately<00:08:37.829> we're<00:08:38.829> not<00:08:39.370> yet<00:08:39.699> at 00:08:39.870 --> 00:08:39.880 align:start position:0% because unfortunately we're not yet at 00:08:39.880 --> 00:08:42.750 align:start position:0% because unfortunately we're not yet at the<00:08:40.089> stage<00:08:40.329> we're<00:08:40.870> missing<00:08:41.260> a<00:08:41.469> bit<00:08:41.949> of<00:08:42.250> extra 00:08:42.750 --> 00:08:42.760 align:start position:0% the stage we're missing a bit of extra 00:08:42.760 --> 00:08:47.579 align:start position:0% the stage we're missing a bit of extra step<00:08:43.029> to<00:08:43.779> get<00:08:44.320> magnet<00:08:45.130> for<00:08:45.579> performance<00:08:46.420> but<00:08:47.380> I 00:08:47.579 --> 00:08:47.589 align:start position:0% step to get magnet for performance but I 00:08:47.589 --> 00:08:51.990 align:start position:0% step to get magnet for performance but I did<00:08:47.829> try<00:08:48.130> to<00:08:48.160> make<00:08:48.760> it<00:08:50.310> harder<00:08:51.310> than<00:08:51.550> minimum 00:08:51.990 --> 00:08:52.000 align:start position:0% did try to make it harder than minimum 00:08:52.000 --> 00:08:54.600 align:start position:0% did try to make it harder than minimum so<00:08:52.209> instead<00:08:52.839> of<00:08:52.899> interrupts<00:08:53.680> which<00:08:54.069> was<00:08:54.250> using 00:08:54.600 --> 00:08:54.610 align:start position:0% so instead of interrupts which was using 00:08:54.610 --> 00:08:59.360 align:start position:0% so instead of interrupts which was using sixteen<00:08:55.029> validators<00:08:55.569> I<00:08:55.839> use<00:08:56.939> 192<00:08:57.939> which<00:08:58.569> means 00:08:59.360 --> 00:08:59.370 align:start position:0% sixteen validators I use 192 which means 00:08:59.370 --> 00:09:05.960 align:start position:0% sixteen validators I use 192 which means 992<00:09:00.370> times<00:09:00.699> 42<00:09:01.180> if<00:09:01.540> state<00:09:02.139> on<00:09:02.500> this<00:09:04.319> 64<00:09:05.319> shards 00:09:05.960 --> 00:09:05.970 align:start position:0% 992 times 42 if state on this 64 shards 00:09:05.970 --> 00:09:10.769 align:start position:0% 992 times 42 if state on this 64 shards eight<00:09:06.970> slots<00:09:07.360> per<00:09:07.629> epoch<00:09:08.670> so<00:09:09.670> one<00:09:10.480> thing<00:09:10.750> is 00:09:10.769 --> 00:09:10.779 align:start position:0% eight slots per epoch so one thing is 00:09:10.779 --> 00:09:12.509 align:start position:0% eight slots per epoch so one thing is that<00:09:10.959> you<00:09:11.439> might<00:09:11.589> think<00:09:11.620> that<00:09:11.889> minimal<00:09:12.370> is 00:09:12.509 --> 00:09:12.519 align:start position:0% that you might think that minimal is 00:09:12.519 --> 00:09:15.749 align:start position:0% that you might think that minimal is really<00:09:12.910> a<00:09:13.089> dumbed<00:09:13.389> down<00:09:13.480> version<00:09:13.629> but<00:09:14.759> an 00:09:15.749 --> 00:09:15.759 align:start position:0% really a dumbed down version but an 00:09:15.759 --> 00:09:18.929 align:start position:0% really a dumbed down version but an epoch<00:09:16.240> so<00:09:16.660> if<00:09:17.529> you're<00:09:17.740> not<00:09:17.889> aware<00:09:18.250> of<00:09:18.310> a 00:09:18.929 --> 00:09:18.939 align:start position:0% epoch so if you're not aware of a 00:09:18.939 --> 00:09:21.389 align:start position:0% epoch so if you're not aware of a freedom<00:09:19.269> to<00:09:19.420> terminology<00:09:20.050> a<00:09:20.230> slot<00:09:20.680> is<00:09:20.980> six 00:09:21.389 --> 00:09:21.399 align:start position:0% freedom to terminology a slot is six 00:09:21.399 --> 00:09:25.079 align:start position:0% freedom to terminology a slot is six second<00:09:21.730> it's<00:09:22.170> how<00:09:23.170> fast<00:09:23.410> we<00:09:23.709> create<00:09:24.670> new<00:09:24.850> block 00:09:25.079 --> 00:09:25.089 align:start position:0% second it's how fast we create new block 00:09:25.089 --> 00:09:28.939 align:start position:0% second it's how fast we create new block on<00:09:25.600> the<00:09:25.779> blockchain<00:09:25.959> and<00:09:26.319> an<00:09:26.800> epoch<00:09:27.100> is<00:09:27.540> a 00:09:28.939 --> 00:09:28.949 align:start position:0% on the blockchain and an epoch is a 00:09:28.949 --> 00:09:32.309 align:start position:0% on the blockchain and an epoch is a group<00:09:29.949> of<00:09:30.160> blocks<00:09:30.970> a<00:09:31.240> group<00:09:31.569> of<00:09:31.720> slots<00:09:32.079> that 00:09:32.309 --> 00:09:32.319 align:start position:0% group of blocks a group of slots that 00:09:32.319 --> 00:09:33.990 align:start position:0% group of blocks a group of slots that make<00:09:32.709> sense<00:09:32.949> together<00:09:33.160> and<00:09:33.579> we<00:09:33.730> will<00:09:33.879> have 00:09:33.990 --> 00:09:34.000 align:start position:0% make sense together and we will have 00:09:34.000 --> 00:09:37.460 align:start position:0% make sense together and we will have special<00:09:34.449> processing<00:09:34.990> after<00:09:35.110> each<00:09:35.470> epoch<00:09:36.389> so 00:09:37.460 --> 00:09:37.470 align:start position:0% special processing after each epoch so 00:09:37.470 --> 00:09:40.259 align:start position:0% special processing after each epoch so that<00:09:38.470> brings<00:09:38.800> each<00:09:39.040> equal<00:09:39.399> to<00:09:39.550> 48<00:09:39.850> second 00:09:40.259 --> 00:09:40.269 align:start position:0% that brings each equal to 48 second 00:09:40.269 --> 00:09:43.650 align:start position:0% that brings each equal to 48 second instead<00:09:40.509> of<00:09:40.569> six<00:09:41.019> minutes<00:09:41.170> and<00:09:41.470> so<00:09:42.329> when<00:09:43.329> I<00:09:43.360> say 00:09:43.650 --> 00:09:43.660 align:start position:0% instead of six minutes and so when I say 00:09:43.660 --> 00:09:46.050 align:start position:0% instead of six minutes and so when I say processing<00:09:44.500> is<00:09:44.620> costly<00:09:45.100> this<00:09:45.459> is<00:09:45.579> the<00:09:45.730> lists 00:09:46.050 --> 00:09:46.060 align:start position:0% processing is costly this is the lists 00:09:46.060 --> 00:09:46.949 align:start position:0% processing is costly this is the lists of<00:09:46.180> what<00:09:46.509> we<00:09:46.629> do 00:09:46.949 --> 00:09:46.959 align:start position:0% of what we do 00:09:46.959 --> 00:09:49.410 align:start position:0% of what we do justification<00:09:47.639> finalization<00:09:48.639> so<00:09:49.029> this<00:09:49.240> means 00:09:49.410 --> 00:09:49.420 align:start position:0% justification finalization so this means 00:09:49.420 --> 00:09:51.030 align:start position:0% justification finalization so this means making<00:09:49.660> sure<00:09:49.810> that<00:09:50.079> the<00:09:50.230> blockchain<00:09:50.500> cannot 00:09:51.030 --> 00:09:51.040 align:start position:0% making sure that the blockchain cannot 00:09:51.040 --> 00:09:53.730 align:start position:0% making sure that the blockchain cannot go<00:09:51.250> back<00:09:51.579> in<00:09:51.819> time<00:09:52.110> cross-links<00:09:53.110> rewards<00:09:53.649> and 00:09:53.730 --> 00:09:53.740 align:start position:0% go back in time cross-links rewards and 00:09:53.740 --> 00:09:57.210 align:start position:0% go back in time cross-links rewards and penalties<00:09:53.920> slashing<00:09:54.730> validators<00:09:56.220> inducing 00:09:57.210 --> 00:09:57.220 align:start position:0% penalties slashing validators inducing 00:09:57.220 --> 00:10:00.749 align:start position:0% penalties slashing validators inducing no<00:09:57.490> new<00:09:57.790> validators<00:09:58.470> removing<00:09:59.519> roles<00:10:00.519> that 00:10:00.749 --> 00:10:00.759 align:start position:0% no new validators removing roles that 00:10:00.759 --> 00:10:07.590 align:start position:0% no new validators removing roles that are<00:10:00.939> bad<00:10:01.149> and<00:10:02.129> updating<00:10:03.129> balances<00:10:06.059> also<00:10:07.059> what 00:10:07.590 --> 00:10:07.600 align:start position:0% are bad and updating balances also what 00:10:07.600 --> 00:10:09.840 align:start position:0% are bad and updating balances also what I<00:10:07.629> wanted<00:10:07.990> to<00:10:08.170> do<00:10:08.350> was<00:10:08.709> giving<00:10:09.189> you<00:10:09.370> very 00:10:09.840 --> 00:10:09.850 align:start position:0% I wanted to do was giving you very 00:10:09.850 --> 00:10:13.559 align:start position:0% I wanted to do was giving you very precise<00:10:10.389> power<00:10:10.899> consumption<00:10:11.589> figures<00:10:12.059> and<00:10:13.059> it 00:10:13.559 --> 00:10:13.569 align:start position:0% precise power consumption figures and it 00:10:13.569 --> 00:10:15.030 align:start position:0% precise power consumption figures and it happened<00:10:13.990> that<00:10:14.170> I<00:10:14.230> had<00:10:14.410> the<00:10:14.680> initiative 00:10:15.030 --> 00:10:15.040 align:start position:0% happened that I had the initiative 00:10:15.040 --> 00:10:17.879 align:start position:0% happened that I had the initiative electrical<00:10:15.639> issue<00:10:15.850> at<00:10:16.120> home<00:10:16.329> a<00:10:16.899> week<00:10:17.319> ago<00:10:17.589> so 00:10:17.879 --> 00:10:17.889 align:start position:0% electrical issue at home a week ago so 00:10:17.889 --> 00:10:21.059 align:start position:0% electrical issue at home a week ago so about<00:10:18.339> this<00:10:18.759> fancy<00:10:19.329> equipment<00:10:19.889> but<00:10:20.889> I 00:10:21.059 --> 00:10:21.069 align:start position:0% about this fancy equipment but I 00:10:21.069 --> 00:10:23.549 align:start position:0% about this fancy equipment but I couldn't<00:10:21.399> use<00:10:21.579> it<00:10:21.610> because<00:10:22.029> I<00:10:22.449> needed<00:10:22.870> a<00:10:23.230> cable 00:10:23.549 --> 00:10:23.559 align:start position:0% couldn't use it because I needed a cable 00:10:23.559 --> 00:10:26.670 align:start position:0% couldn't use it because I needed a cable with<00:10:23.949> a<00:10:24.220> different<00:10:25.110> electricity<00:10:26.110> in<00:10:26.290> and<00:10:26.529> if 00:10:26.670 --> 00:10:26.680 align:start position:0% with a different electricity in and if 00:10:26.680 --> 00:10:32.730 align:start position:0% with a different electricity in and if electricity<00:10:27.339> out<00:10:27.490> so<00:10:27.990> I'm<00:10:28.990> sorry<00:10:30.720> now<00:10:31.720> for<00:10:32.649> the 00:10:32.730 --> 00:10:32.740 align:start position:0% electricity out so I'm sorry now for the 00:10:32.740 --> 00:10:37.110 align:start position:0% electricity out so I'm sorry now for the actual<00:10:33.100> demo<00:10:33.899> this<00:10:34.899> is<00:10:35.110> output<00:10:36.040> life<00:10:36.579> from<00:10:36.910> the 00:10:37.110 --> 00:10:37.120 align:start position:0% actual demo this is output life from the 00:10:37.120 --> 00:10:40.230 align:start position:0% actual demo this is output life from the Raspberry<00:10:37.750> Pi<00:10:37.809> that<00:10:38.170> is<00:10:38.350> behind<00:10:38.740> you<00:10:38.980> and<00:10:39.279> it 00:10:40.230 --> 00:10:40.240 align:start position:0% Raspberry Pi that is behind you and it 00:10:40.240 --> 00:10:42.689 align:start position:0% Raspberry Pi that is behind you and it shows<00:10:40.540> you<00:10:40.809> it<00:10:41.050> has<00:10:41.199> been<00:10:41.350> running<00:10:41.649> for<00:10:41.699> 40 00:10:42.689 --> 00:10:42.699 align:start position:0% shows you it has been running for 40 00:10:42.699 --> 00:10:45.059 align:start position:0% shows you it has been running for 40 minutes<00:10:42.879> now<00:10:43.240> and<00:10:43.569> show<00:10:44.379> you<00:10:44.439> that<00:10:44.680> first 00:10:45.059 --> 00:10:45.069 align:start position:0% minutes now and show you that first 00:10:45.069 --> 00:10:47.759 align:start position:0% minutes now and show you that first didn't<00:10:45.519> crash<00:10:45.850> and<00:10:46.209> it's<00:10:46.930> also<00:10:47.110> running<00:10:47.410> and 00:10:47.759 --> 00:10:47.769 align:start position:0% didn't crash and it's also running and 00:10:47.769 --> 00:10:49.829 align:start position:0% didn't crash and it's also running and you<00:10:48.069> have<00:10:48.189> the<00:10:48.309> output<00:10:48.459> of<00:10:48.790> three<00:10:48.970> nodes<00:10:49.180> so 00:10:49.829 --> 00:10:49.839 align:start position:0% you have the output of three nodes so 00:10:49.839 --> 00:10:53.249 align:start position:0% you have the output of three nodes so it's<00:10:50.259> a<00:10:50.410> bit<00:10:50.790> fast<00:10:51.790> and<00:10:52.089> this<00:10:52.509> was<00:10:52.720> a<00:10:52.990> video 00:10:53.249 --> 00:10:53.259 align:start position:0% it's a bit fast and this was a video 00:10:53.259 --> 00:10:56.369 align:start position:0% it's a bit fast and this was a video backup<00:10:53.860> that<00:10:54.430> I<00:10:54.490> used<00:10:54.850> just<00:10:55.059> in<00:10:55.300> case<00:10:55.540> the<00:10:56.050> live 00:10:56.369 --> 00:10:56.379 align:start position:0% backup that I used just in case the live 00:10:56.379 --> 00:11:02.460 align:start position:0% backup that I used just in case the live demo<00:10:56.740> didn't<00:10:57.100> work<00:11:00.360> now<00:11:01.360> some<00:11:01.870> key<00:11:02.110> figures 00:11:02.460 --> 00:11:02.470 align:start position:0% demo didn't work now some key figures 00:11:02.470 --> 00:11:05.249 align:start position:0% demo didn't work now some key figures about<00:11:02.889> running<00:11:03.399> affion<00:11:04.240> and<00:11:04.630> Nimbus<00:11:04.959> on<00:11:05.170> the 00:11:05.249 --> 00:11:05.259 align:start position:0% about running affion and Nimbus on the 00:11:05.259 --> 00:11:05.580 align:start position:0% about running affion and Nimbus on the rest 00:11:05.580 --> 00:11:05.590 align:start position:0% rest 00:11:05.590 --> 00:11:08.580 align:start position:0% rest pi<00:11:06.130> sorry<00:11:06.910> pi<00:11:07.180> maximum<00:11:07.720> power<00:11:07.900> consumption 00:11:08.580 --> 00:11:08.590 align:start position:0% pi sorry pi maximum power consumption 00:11:08.590 --> 00:11:11.730 align:start position:0% pi sorry pi maximum power consumption per<00:11:08.980> draw<00:11:09.340> is<00:11:09.550> seven<00:11:09.940> point<00:11:10.180> six<00:11:10.390> watts<00:11:10.740> to 00:11:11.730 --> 00:11:11.740 align:start position:0% per draw is seven point six watts to 00:11:11.740 --> 00:11:14.930 align:start position:0% per draw is seven point six watts to give<00:11:11.920> you<00:11:12.130> an<00:11:12.310> idea<00:11:12.840> for<00:11:13.840> a<00:11:13.900> typical<00:11:14.470> laptop 00:11:14.930 --> 00:11:14.940 align:start position:0% give you an idea for a typical laptop 00:11:14.940 --> 00:11:20.100 align:start position:0% give you an idea for a typical laptop nowadays<00:11:15.940> it's<00:11:16.570> about<00:11:16.920> 30<00:11:17.920> watt<00:11:18.100> so<00:11:18.880> it's<00:11:19.390> four 00:11:20.100 --> 00:11:20.110 align:start position:0% nowadays it's about 30 watt so it's four 00:11:20.110 --> 00:11:23.340 align:start position:0% nowadays it's about 30 watt so it's four to<00:11:20.350> five<00:11:20.710> times<00:11:21.130> less<00:11:21.670> power<00:11:22.030> consumed<00:11:22.690> and 00:11:23.340 --> 00:11:23.350 align:start position:0% to five times less power consumed and 00:11:23.350 --> 00:11:26.370 align:start position:0% to five times less power consumed and also<00:11:24.070> a<00:11:24.370> Raspberry<00:11:24.790> Pi<00:11:24.850> is<00:11:25.300> about<00:11:25.660> ten<00:11:26.080> times 00:11:26.370 --> 00:11:26.380 align:start position:0% also a Raspberry Pi is about ten times 00:11:26.380 --> 00:11:29.430 align:start position:0% also a Raspberry Pi is about ten times slower<00:11:26.530> than<00:11:27.070> an<00:11:27.190> entry-level<00:11:27.580> CPU<00:11:28.360> for<00:11:29.020> a 00:11:29.430 --> 00:11:29.440 align:start position:0% slower than an entry-level CPU for a 00:11:29.440 --> 00:11:34.040 align:start position:0% slower than an entry-level CPU for a desktop<00:11:30.240> so<00:11:31.240> this<00:11:31.570> means<00:11:31.810> that<00:11:32.340> and<00:11:33.340> it<00:11:33.700> runs 00:11:34.040 --> 00:11:34.050 align:start position:0% desktop so this means that and it runs 00:11:34.050 --> 00:11:37.800 align:start position:0% desktop so this means that and it runs into<00:11:35.050> runs<00:11:35.380> perfectly<00:11:35.860> on<00:11:36.160> this<00:11:37.000> kind<00:11:37.240> of<00:11:37.420> CPU 00:11:37.800 --> 00:11:37.810 align:start position:0% into runs perfectly on this kind of CPU 00:11:37.810 --> 00:11:40.080 align:start position:0% into runs perfectly on this kind of CPU so<00:11:38.050> if<00:11:38.170> we<00:11:38.320> can<00:11:38.470> get<00:11:38.650> to<00:11:39.220> three<00:11:39.730> times<00:11:39.970> more 00:11:40.080 --> 00:11:40.090 align:start position:0% so if we can get to three times more 00:11:40.090 --> 00:11:41.910 align:start position:0% so if we can get to three times more performance<00:11:40.780> we<00:11:41.320> would<00:11:41.440> be<00:11:41.560> okay<00:11:41.710> for 00:11:41.910 --> 00:11:41.920 align:start position:0% performance we would be okay for 00:11:41.920 --> 00:11:47.460 align:start position:0% performance we would be okay for maintenance<00:11:42.340> and<00:11:43.350> also<00:11:44.970> if<00:11:46.110> people<00:11:47.110> were 00:11:47.460 --> 00:11:47.470 align:start position:0% maintenance and also if people were 00:11:47.470 --> 00:11:49.620 align:start position:0% maintenance and also if people were worrying<00:11:47.920> because<00:11:48.100> they<00:11:48.430> are<00:11:48.550> ten<00:11:49.210> thousand 00:11:49.620 --> 00:11:49.630 align:start position:0% worrying because they are ten thousand 00:11:49.630 --> 00:11:51.660 align:start position:0% worrying because they are ten thousand if<00:11:49.810> to<00:11:50.110> stake<00:11:50.380> and<00:11:50.650> we<00:11:50.950> didn't<00:11:51.190> know<00:11:51.340> what<00:11:51.520> kind 00:11:51.660 --> 00:11:51.670 align:start position:0% if to stake and we didn't know what kind 00:11:51.670 --> 00:11:58.280 align:start position:0% if to stake and we didn't know what kind of<00:11:51.850> hardware<00:11:52.210> they<00:11:52.390> needed<00:11:52.800> well<00:11:54.360> it's<00:11:55.360> easy 00:11:58.280 --> 00:11:58.290 align:start position:0% 00:11:58.290 --> 00:12:02.610 align:start position:0% so<00:11:59.290> in<00:11:59.920> summary<00:12:00.510> outcomes<00:12:01.510> of<00:12:01.780> those 00:12:02.610 --> 00:12:02.620 align:start position:0% so in summary outcomes of those 00:12:02.620 --> 00:12:07.590 align:start position:0% so in summary outcomes of those experiments<00:12:04.170> it<00:12:05.170> runs<00:12:05.560> even<00:12:05.830> and<00:12:06.760> optimize<00:12:07.300> on 00:12:07.590 --> 00:12:07.600 align:start position:0% experiments it runs even and optimize on 00:12:07.600 --> 00:12:10.140 align:start position:0% experiments it runs even and optimize on representative<00:12:08.230> workloads<00:12:08.850> you<00:12:09.850> don't<00:12:10.000> need 00:12:10.140 --> 00:12:10.150 align:start position:0% representative workloads you don't need 00:12:10.150 --> 00:12:12.570 align:start position:0% representative workloads you don't need the<00:12:10.270> power<00:12:10.480> plant<00:12:10.810> in<00:12:10.960> your<00:12:11.080> backyard<00:12:11.290> just<00:12:11.890> to 00:12:12.570 --> 00:12:12.580 align:start position:0% the power plant in your backyard just to 00:12:12.580 --> 00:12:14.340 align:start position:0% the power plant in your backyard just to ensure<00:12:12.880> that<00:12:12.940> you<00:12:13.210> always<00:12:13.360> have<00:12:13.690> electricity 00:12:14.340 --> 00:12:14.350 align:start position:0% ensure that you always have electricity 00:12:14.350 --> 00:12:16.380 align:start position:0% ensure that you always have electricity and<00:12:14.560> you<00:12:14.650> don't<00:12:14.890> black<00:12:15.130> out<00:12:15.310> the<00:12:16.180> wall 00:12:16.380 --> 00:12:16.390 align:start position:0% and you don't black out the wall 00:12:16.390 --> 00:12:20.460 align:start position:0% and you don't black out the wall district<00:12:17.110> and<00:12:18.270> we<00:12:19.270> also<00:12:19.450> have<00:12:19.750> clear<00:12:19.990> targets 00:12:20.460 --> 00:12:20.470 align:start position:0% district and we also have clear targets 00:12:20.470 --> 00:12:25.320 align:start position:0% district and we also have clear targets because<00:12:20.950> has<00:12:21.790> Danny<00:12:22.060> said<00:12:22.420> this<00:12:23.230> morning<00:12:24.330> the 00:12:25.320 --> 00:12:25.330 align:start position:0% because has Danny said this morning the 00:12:25.330 --> 00:12:28.020 align:start position:0% because has Danny said this morning the main<00:12:25.650> blocker<00:12:26.650> and<00:12:26.920> most<00:12:27.400> of<00:12:27.550> the<00:12:27.640> time<00:12:27.820> is 00:12:28.020 --> 00:12:28.030 align:start position:0% main blocker and most of the time is 00:12:28.030 --> 00:12:30.210 align:start position:0% main blocker and most of the time is spent<00:12:28.120> on<00:12:28.480> cryptography<00:12:28.930> and<00:12:29.410> the 00:12:30.210 --> 00:12:30.220 align:start position:0% spent on cryptography and the 00:12:30.220 --> 00:12:32.340 align:start position:0% spent on cryptography and the cryptography<00:12:30.850> that<00:12:30.880> we<00:12:31.150> use<00:12:31.330> on<00:12:31.480> a<00:12:31.570> forum<00:12:31.870> -<00:12:32.110> is 00:12:32.340 --> 00:12:32.350 align:start position:0% cryptography that we use on a forum - is 00:12:32.350 --> 00:12:35.850 align:start position:0% cryptography that we use on a forum - is very<00:12:32.680> young<00:12:32.950> it<00:12:33.220> was<00:12:33.580> developed<00:12:34.030> by<00:12:34.560> Dan<00:12:35.560> boney 00:12:35.850 --> 00:12:35.860 align:start position:0% very young it was developed by Dan boney 00:12:35.860 --> 00:12:38.460 align:start position:0% very young it was developed by Dan boney at<00:12:36.040> Stanford<00:12:36.550> but<00:12:37.390> there<00:12:37.870> is<00:12:37.990> no<00:12:38.200> either 00:12:38.460 --> 00:12:38.470 align:start position:0% at Stanford but there is no either 00:12:38.470 --> 00:12:40.950 align:start position:0% at Stanford but there is no either hardware<00:12:39.160> or<00:12:39.310> software<00:12:39.550> optimization<00:12:40.330> yet 00:12:40.950 --> 00:12:40.960 align:start position:0% hardware or software optimization yet 00:12:40.960 --> 00:12:43.670 align:start position:0% hardware or software optimization yet and<00:12:41.230> everyone<00:12:42.040> also<00:12:42.310> a<00:12:42.520> frame<00:12:42.880> to<00:12:43.030> team 00:12:43.670 --> 00:12:43.680 align:start position:0% and everyone also a frame to team 00:12:43.680 --> 00:12:48.420 align:start position:0% and everyone also a frame to team currently<00:12:44.680> have<00:12:45.510> an<00:12:46.620> optimized<00:12:47.620> and<00:12:48.010> very 00:12:48.420 --> 00:12:48.430 align:start position:0% currently have an optimized and very 00:12:48.430 --> 00:12:50.130 align:start position:0% currently have an optimized and very young<00:12:48.700> library<00:12:49.090> but<00:12:49.300> as<00:12:49.480> the<00:12:49.600> ecosystem 00:12:50.130 --> 00:12:50.140 align:start position:0% young library but as the ecosystem 00:12:50.140 --> 00:12:52.710 align:start position:0% young library but as the ecosystem mature<00:12:50.560> it<00:12:50.980> will<00:12:51.250> get<00:12:51.430> much<00:12:51.730> better<00:12:52.000> also 00:12:52.710 --> 00:12:52.720 align:start position:0% mature it will get much better also 00:12:52.720 --> 00:12:54.600 align:start position:0% mature it will get much better also there<00:12:53.290> is<00:12:53.350> an<00:12:53.440> effort<00:12:53.770> to<00:12:53.800> standardize<00:12:54.220> across 00:12:54.600 --> 00:12:54.610 align:start position:0% there is an effort to standardize across 00:12:54.610 --> 00:12:57.000 align:start position:0% there is an effort to standardize across many<00:12:55.000> blockchain<00:12:55.510> like<00:12:55.870> a<00:12:56.050> friend<00:12:56.350> on<00:12:56.470> C<00:12:56.740> cash 00:12:57.000 --> 00:12:57.010 align:start position:0% many blockchain like a friend on C cash 00:12:57.010 --> 00:12:59.700 align:start position:0% many blockchain like a friend on C cash cycle<00:12:57.370> Al<00:12:57.790> Gore<00:12:58.030> indefinite<00:12:58.690> each<00:12:58.840> network<00:12:59.560> I 00:12:59.700 --> 00:12:59.710 align:start position:0% cycle Al Gore indefinite each network I 00:12:59.710 --> 00:13:03.030 align:start position:0% cycle Al Gore indefinite each network I guess<00:13:00.670> one<00:13:00.880> or<00:13:00.970> two<00:13:01.120> over<00:13:01.390> I<00:13:01.630> forget<00:13:02.440> so<00:13:02.770> varies 00:13:03.030 --> 00:13:03.040 align:start position:0% guess one or two over I forget so varies 00:13:03.040 --> 00:13:05.490 align:start position:0% guess one or two over I forget so varies an<00:13:03.250> incentive<00:13:03.730> across<00:13:04.540> all<00:13:04.780> blockchain<00:13:05.350> to 00:13:05.490 --> 00:13:05.500 align:start position:0% an incentive across all blockchain to 00:13:05.500 --> 00:13:07.230 align:start position:0% an incentive across all blockchain to collaborate<00:13:05.950> and<00:13:06.130> get<00:13:06.430> something<00:13:06.880> really 00:13:07.230 --> 00:13:07.240 align:start position:0% collaborate and get something really 00:13:07.240 --> 00:13:13.380 align:start position:0% collaborate and get something really strong<00:13:09.450> so<00:13:10.450> bad<00:13:11.070> so<00:13:12.070> as<00:13:12.340> I<00:13:12.460> said<00:13:12.700> we<00:13:13.090> can<00:13:13.240> run 00:13:13.380 --> 00:13:13.390 align:start position:0% strong so bad so as I said we can run 00:13:13.390 --> 00:13:18.000 align:start position:0% strong so bad so as I said we can run minimal<00:13:13.780> we<00:13:14.110> cannot<00:13:14.290> run<00:13:14.470> main<00:13:14.710> net<00:13:14.920> and<00:13:16.230> well 00:13:18.000 --> 00:13:18.010 align:start position:0% minimal we cannot run main net and well 00:13:18.010 --> 00:13:21.270 align:start position:0% minimal we cannot run main net and well processing<00:13:18.760> takes<00:13:18.910> over<00:13:19.240> six<00:13:19.570> second<00:13:20.280> maybe 00:13:21.270 --> 00:13:21.280 align:start position:0% processing takes over six second maybe 00:13:21.280 --> 00:13:24.390 align:start position:0% processing takes over six second maybe ten<00:13:21.790> or<00:13:21.820> something<00:13:22.560> we<00:13:23.560> need<00:13:23.710> to<00:13:23.830> get<00:13:23.980> twice 00:13:24.390 --> 00:13:24.400 align:start position:0% ten or something we need to get twice 00:13:24.400 --> 00:13:28.830 align:start position:0% ten or something we need to get twice faster<00:13:25.380> so<00:13:26.380> ugly<00:13:26.730> I'm<00:13:27.730> sorry<00:13:28.090> but<00:13:28.300> if<00:13:28.510> you<00:13:28.690> want 00:13:28.830 --> 00:13:28.840 align:start position:0% faster so ugly I'm sorry but if you want 00:13:28.840 --> 00:13:30.840 align:start position:0% faster so ugly I'm sorry but if you want it<00:13:28.960> to<00:13:29.050> hit<00:13:29.200> your<00:13:29.260> home<00:13:29.590> in<00:13:29.800> the<00:13:29.830> winter<00:13:30.070> you 00:13:30.840 --> 00:13:30.850 align:start position:0% it to hit your home in the winter you 00:13:30.850 --> 00:13:33.150 align:start position:0% it to hit your home in the winter you will<00:13:31.090> not<00:13:31.300> be<00:13:31.420> able<00:13:31.510> to<00:13:31.780> do<00:13:31.930> it<00:13:32.470> with<00:13:32.770> proof<00:13:33.070> of 00:13:33.150 --> 00:13:33.160 align:start position:0% will not be able to do it with proof of 00:13:33.160 --> 00:13:34.950 align:start position:0% will not be able to do it with proof of state<00:13:33.370> so<00:13:33.700> you<00:13:33.730> will<00:13:34.510> have<00:13:34.600> to<00:13:34.720> stay<00:13:34.930> with 00:13:34.950 --> 00:13:34.960 align:start position:0% state so you will have to stay with 00:13:34.960 --> 00:13:42.930 align:start position:0% state so you will have to stay with Bitcoin<00:13:35.590> or<00:13:35.770> something<00:13:36.100> else<00:13:38.760> now<00:13:41.430> some<00:13:42.430> ideas 00:13:42.930 --> 00:13:42.940 align:start position:0% Bitcoin or something else now some ideas 00:13:42.940 --> 00:13:45.260 align:start position:0% Bitcoin or something else now some ideas I<00:13:43.120> have<00:13:43.270> for<00:13:43.300> the<00:13:43.570> future<00:13:43.900> to<00:13:44.200> optimize<00:13:44.830> this 00:13:45.260 --> 00:13:45.270 align:start position:0% I have for the future to optimize this 00:13:45.270 --> 00:13:48.630 align:start position:0% I have for the future to optimize this the<00:13:46.270> Raspberry<00:13:46.630> Pi<00:13:46.890> default<00:13:47.890> distribution<00:13:48.520> is 00:13:48.630 --> 00:13:48.640 align:start position:0% the Raspberry Pi default distribution is 00:13:48.640 --> 00:13:51.000 align:start position:0% the Raspberry Pi default distribution is run<00:13:48.910> in<00:13:49.030> 32-bit<00:13:49.450> mode<00:13:49.840> but<00:13:50.200> cryptography<00:13:50.860> in 00:13:51.000 --> 00:13:51.010 align:start position:0% run in 32-bit mode but cryptography in 00:13:51.010 --> 00:13:53.180 align:start position:0% run in 32-bit mode but cryptography in 64-bit<00:13:51.670> is<00:13:51.850> much<00:13:52.210> faster 00:13:53.180 --> 00:13:53.190 align:start position:0% 64-bit is much faster 00:13:53.190 --> 00:13:56.520 align:start position:0% 64-bit is much faster we<00:13:54.190> had<00:13:54.370> no<00:13:54.940> multi-threading<00:13:55.570> yet<00:13:55.750> even 00:13:56.520 --> 00:13:56.530 align:start position:0% we had no multi-threading yet even 00:13:56.530 --> 00:13:58.800 align:start position:0% we had no multi-threading yet even though<00:13:56.740> this<00:13:57.070> has<00:13:57.370> four<00:13:57.700> cores<00:13:57.940> we<00:13:58.300> only<00:13:58.510> use 00:13:58.800 --> 00:13:58.810 align:start position:0% though this has four cores we only use 00:13:58.810 --> 00:14:03.540 align:start position:0% though this has four cores we only use one<00:13:59.140> and<00:14:00.330> as<00:14:01.330> I<00:14:01.510> said<00:14:01.690> before<00:14:02.250> we<00:14:03.250> have<00:14:03.400> an 00:14:03.540 --> 00:14:03.550 align:start position:0% one and as I said before we have an 00:14:03.550 --> 00:14:06.270 align:start position:0% one and as I said before we have an optimized<00:14:04.000> crypto<00:14:04.750> library<00:14:05.140> like<00:14:05.830> Bitcoin 00:14:06.270 --> 00:14:06.280 align:start position:0% optimized crypto library like Bitcoin 00:14:06.280 --> 00:14:12.140 align:start position:0% optimized crypto library like Bitcoin has<00:14:06.520> for<00:14:06.910> the<00:14:07.810> curve<00:14:08.110> called<00:14:08.380> SEC<00:14:08.680> P<00:14:08.890> 256<00:14:09.730> k1 00:14:12.140 --> 00:14:12.150 align:start position:0% has for the curve called SEC P 256 k1 00:14:12.150 --> 00:14:16.200 align:start position:0% has for the curve called SEC P 256 k1 also<00:14:13.150> at<00:14:13.300> Nimbus<00:14:13.690> even<00:14:13.990> though<00:14:14.200> we<00:14:14.620> are<00:14:15.030> one<00:14:16.030> of 00:14:16.200 --> 00:14:16.210 align:start position:0% also at Nimbus even though we are one of 00:14:16.210 --> 00:14:18.020 align:start position:0% also at Nimbus even though we are one of the<00:14:16.330> team<00:14:16.540> targeting<00:14:17.080> low-power<00:14:17.470> devices 00:14:18.020 --> 00:14:18.030 align:start position:0% the team targeting low-power devices 00:14:18.030 --> 00:14:21.150 align:start position:0% the team targeting low-power devices there<00:14:19.030> is<00:14:19.060> an<00:14:19.240> over<00:14:19.450> team<00:14:19.680> lodestar<00:14:20.680> who's 00:14:21.150 --> 00:14:21.160 align:start position:0% there is an over team lodestar who's 00:14:21.160 --> 00:14:25.650 align:start position:0% there is an over team lodestar who's trying<00:14:21.520> to<00:14:21.610> run<00:14:21.910> as<00:14:22.180> a<00:14:22.720> friend<00:14:23.170> to<00:14:23.380> on<00:14:24.660> the 00:14:25.650 --> 00:14:25.660 align:start position:0% trying to run as a friend to on the 00:14:25.660 --> 00:14:29.130 align:start position:0% trying to run as a friend to on the browser<00:14:25.930> on<00:14:26.620> Chrome<00:14:27.190> or<00:14:27.460> Firefox<00:14:27.690> so<00:14:28.690> we<00:14:28.990> also 00:14:29.130 --> 00:14:29.140 align:start position:0% browser on Chrome or Firefox so we also 00:14:29.140 --> 00:14:34.350 align:start position:0% browser on Chrome or Firefox so we also have<00:14:29.440> huge<00:14:30.430> challenges<00:14:30.670> ahead<00:14:31.360> so<00:14:32.020> it's<00:14:33.360> kind 00:14:34.350 --> 00:14:34.360 align:start position:0% have huge challenges ahead so it's kind 00:14:34.360 --> 00:14:38.310 align:start position:0% have huge challenges ahead so it's kind of<00:14:34.480> a<00:14:34.510> team<00:14:34.870> effort<00:14:36.210> also<00:14:37.210> what's<00:14:37.570> coming<00:14:37.900> next 00:14:38.310 --> 00:14:38.320 align:start position:0% of a team effort also what's coming next 00:14:38.320 --> 00:14:42.330 align:start position:0% of a team effort also what's coming next Raspberry<00:14:39.010> Pi<00:14:39.250> 5<00:14:40.290> so<00:14:41.290> maybe<00:14:41.920> it's<00:14:42.130> twice 00:14:42.330 --> 00:14:42.340 align:start position:0% Raspberry Pi 5 so maybe it's twice 00:14:42.340 --> 00:14:47.150 align:start position:0% Raspberry Pi 5 so maybe it's twice faster<00:14:42.520> and<00:14:43.000> we<00:14:43.480> can<00:14:43.690> sit<00:14:44.080> and<00:14:44.830> do<00:14:45.160> nothing<00:14:45.750> and 00:14:47.150 --> 00:14:47.160 align:start position:0% faster and we can sit and do nothing and 00:14:47.160 --> 00:14:50.520 align:start position:0% faster and we can sit and do nothing and for<00:14:48.160> use<00:14:48.400> cases<00:14:48.520> for<00:14:49.060> people<00:14:49.240> I<00:14:49.690> didn't<00:14:50.200> expect 00:14:50.520 --> 00:14:50.530 align:start position:0% for use cases for people I didn't expect 00:14:50.530 --> 00:14:53.010 align:start position:0% for use cases for people I didn't expect actually<00:14:50.920> to<00:14:51.100> for<00:14:51.430> people<00:14:51.550> to<00:14:52.000> run<00:14:52.450> that<00:14:52.780> on 00:14:53.010 --> 00:14:53.020 align:start position:0% actually to for people to run that on 00:14:53.020 --> 00:14:55.680 align:start position:0% actually to for people to run that on the<00:14:53.080> Raspberry<00:14:53.590> Pi<00:14:53.650> maybe<00:14:54.490> we<00:14:54.730> will<00:14:54.880> rent<00:14:55.390> an 00:14:55.680 --> 00:14:55.690 align:start position:0% the Raspberry Pi maybe we will rent an 00:14:55.690 --> 00:14:58.500 align:start position:0% the Raspberry Pi maybe we will rent an instance<00:14:56.230> like<00:14:56.380> the<00:14:56.650> rent<00:14:56.860> WordPress<00:14:57.510> today 00:14:58.500 --> 00:14:58.510 align:start position:0% instance like the rent WordPress today 00:14:58.510 --> 00:15:02.430 align:start position:0% instance like the rent WordPress today and<00:14:58.810> people<00:14:59.740> will<00:14:59.860> be<00:14:59.950> able<00:15:00.040> to<00:15:00.340> just<00:15:01.440> launch 00:15:02.430 --> 00:15:02.440 align:start position:0% and people will be able to just launch 00:15:02.440 --> 00:15:04.440 align:start position:0% and people will be able to just launch some<00:15:02.860> kind<00:15:03.070> of<00:15:03.310> always<00:15:03.700> with<00:15:04.090> a<00:15:04.240> freedom 00:15:04.440 --> 00:15:04.450 align:start position:0% some kind of always with a freedom 00:15:04.450 --> 00:15:06.240 align:start position:0% some kind of always with a freedom installed<00:15:05.020> and<00:15:05.260> everything<00:15:05.800> will<00:15:05.950> be<00:15:06.070> done 00:15:06.240 --> 00:15:06.250 align:start position:0% installed and everything will be done 00:15:06.250 --> 00:15:10.020 align:start position:0% installed and everything will be done for<00:15:06.460> them<00:15:06.580> and<00:15:06.930> the<00:15:07.930> consumption<00:15:08.640> the<00:15:09.640> CPU 00:15:10.020 --> 00:15:10.030 align:start position:0% for them and the consumption the CPU 00:15:10.030 --> 00:15:11.640 align:start position:0% for them and the consumption the CPU that<00:15:10.210> would<00:15:10.420> be<00:15:10.570> rented<00:15:10.960> would<00:15:11.110> be<00:15:11.230> just 00:15:11.640 --> 00:15:11.650 align:start position:0% that would be rented would be just 00:15:11.650 --> 00:15:14.930 align:start position:0% that would be rented would be just powerful<00:15:11.890> enough<00:15:12.250> to<00:15:12.310> run<00:15:12.610> Efram 00:15:14.930 --> 00:15:14.940 align:start position:0% powerful enough to run Efram 00:15:14.940 --> 00:15:18.660 align:start position:0% powerful enough to run Efram so<00:15:15.940> regarding<00:15:16.900> the<00:15:16.930> unknowns<00:15:17.500> for<00:15:18.010> a<00:15:18.310> freedom 00:15:18.660 --> 00:15:18.670 align:start position:0% so regarding the unknowns for a freedom 00:15:18.670 --> 00:15:22.650 align:start position:0% so regarding the unknowns for a freedom to<00:15:18.940> performance<00:15:19.600> in<00:15:20.110> the<00:15:20.290> future<00:15:21.240> as<00:15:22.240> I<00:15:22.450> said 00:15:22.650 --> 00:15:22.660 align:start position:0% to performance in the future as I said 00:15:22.660 --> 00:15:25.110 align:start position:0% to performance in the future as I said verifying<00:15:23.410> validators<00:15:24.220> attestation<00:15:24.730> is 00:15:25.110 --> 00:15:25.120 align:start position:0% verifying validators attestation is 00:15:25.120 --> 00:15:27.090 align:start position:0% verifying validators attestation is quite<00:15:25.450> costly<00:15:25.750> this<00:15:25.990> is<00:15:26.110> cryptography<00:15:26.770> it's 00:15:27.090 --> 00:15:27.100 align:start position:0% quite costly this is cryptography it's 00:15:27.100 --> 00:15:29.199 align:start position:0% quite costly this is cryptography it's about<00:15:27.850> 42 00:15:29.199 --> 00:15:29.209 align:start position:0% about 42 00:15:29.209 --> 00:15:33.220 align:start position:0% about 42 50%<00:15:29.660> of<00:15:30.170> the<00:15:30.319> time<00:15:30.499> spent<00:15:30.920> in<00:15:31.129> that<00:15:32.019> if<00:15:33.019> you 00:15:33.220 --> 00:15:33.230 align:start position:0% 50% of the time spent in that if you 00:15:33.230 --> 00:15:38.079 align:start position:0% 50% of the time spent in that if you read<00:15:33.499> prismatic<00:15:34.309> lab<00:15:34.819> news<00:15:35.470> from<00:15:36.470> a<00:15:37.129> week<00:15:38.059> ago 00:15:38.079 --> 00:15:38.089 align:start position:0% read prismatic lab news from a week ago 00:15:38.089 --> 00:15:40.960 align:start position:0% read prismatic lab news from a week ago apparently<00:15:38.569> if<00:15:38.839> I<00:15:38.929> spend<00:15:39.259> 99%<00:15:39.920> of<00:15:40.369> a<00:15:40.490> time<00:15:40.759> on 00:15:40.960 --> 00:15:40.970 align:start position:0% apparently if I spend 99% of a time on 00:15:40.970 --> 00:15:44.530 align:start position:0% apparently if I spend 99% of a time on BLS<00:15:41.569> signature<00:15:42.199> and<00:15:42.410> now<00:15:43.249> it's<00:15:43.399> only<00:15:43.550> 20%<00:15:43.970> so 00:15:44.530 --> 00:15:44.540 align:start position:0% BLS signature and now it's only 20% so 00:15:44.540 --> 00:15:49.239 align:start position:0% BLS signature and now it's only 20% so we<00:15:45.170> can<00:15:45.410> get<00:15:46.399> lots<00:15:47.240> of<00:15:47.329> improvement 00:15:49.239 --> 00:15:49.249 align:start position:0% we can get lots of improvement 00:15:49.249 --> 00:15:52.749 align:start position:0% we can get lots of improvement another<00:15:49.939> issue<00:15:50.089> is<00:15:50.509> when<00:15:51.439> we<00:15:51.589> scaled<00:15:51.889> 100,000 00:15:52.749 --> 00:15:52.759 align:start position:0% another issue is when we scaled 100,000 00:15:52.759 --> 00:15:54.129 align:start position:0% another issue is when we scaled 100,000 validators<00:15:53.269> we<00:15:53.720> have<00:15:53.839> an<00:15:54.019> aggregation 00:15:54.129 --> 00:15:54.139 align:start position:0% validators we have an aggregation 00:15:54.139 --> 00:15:57.970 align:start position:0% validators we have an aggregation protocols<00:15:54.889> in<00:15:55.040> research<00:15:56.439> we<00:15:57.439> have<00:15:57.589> no<00:15:57.769> need<00:15:57.920> to 00:15:57.970 --> 00:15:57.980 align:start position:0% protocols in research we have no need to 00:15:57.980 --> 00:16:02.019 align:start position:0% protocols in research we have no need to connect<00:15:58.459> to<00:15:58.550> every<00:15:58.879> peer<00:15:59.709> so<00:16:00.709> a<00:16:01.160> lot<00:16:01.999> of 00:16:02.019 --> 00:16:02.029 align:start position:0% connect to every peer so a lot of 00:16:02.029 --> 00:16:05.439 align:start position:0% connect to every peer so a lot of optimizations<00:16:02.720> where<00:16:02.899> as<00:16:03.019> well<00:16:03.699> so<00:16:04.699> for<00:16:05.240> me<00:16:05.329> is 00:16:05.439 --> 00:16:05.449 align:start position:0% optimizations where as well so for me is 00:16:05.449 --> 00:16:09.009 align:start position:0% optimizations where as well so for me is a<00:16:05.540> big<00:16:05.689> unknowns<00:16:06.139> of<00:16:06.379> phase<00:16:07.279> one<00:16:07.999> and<00:16:08.269> phase 00:16:09.009 --> 00:16:09.019 align:start position:0% a big unknowns of phase one and phase 00:16:09.019 --> 00:16:11.259 align:start position:0% a big unknowns of phase one and phase two<00:16:09.050> is<00:16:09.589> the<00:16:09.740> execution<00:16:10.160> layer<00:16:10.339> which<00:16:11.119> is 00:16:11.259 --> 00:16:11.269 align:start position:0% two is the execution layer which is 00:16:11.269 --> 00:16:14.470 align:start position:0% two is the execution layer which is equivalent<00:16:11.569> to<00:16:12.339> EVM<00:16:13.339> and<00:16:13.579> what<00:16:13.850> solidity 00:16:14.470 --> 00:16:14.480 align:start position:0% equivalent to EVM and what solidity 00:16:14.480 --> 00:16:17.379 align:start position:0% equivalent to EVM and what solidity compiles<00:16:15.199> to<00:16:15.290> I<00:16:16.160> don't<00:16:16.730> know<00:16:16.819> how<00:16:16.970> heavy<00:16:17.209> it 00:16:17.379 --> 00:16:17.389 align:start position:0% compiles to I don't know how heavy it 00:16:17.389 --> 00:16:23.340 align:start position:0% compiles to I don't know how heavy it will<00:16:17.569> be<00:16:19.600> so<00:16:20.600> key<00:16:21.139> takeaways<00:16:21.559> after<00:16:21.889> this<00:16:22.069> talk 00:16:23.340 --> 00:16:23.350 align:start position:0% will be so key takeaways after this talk 00:16:23.350 --> 00:16:25.660 align:start position:0% will be so key takeaways after this talk there<00:16:24.350> are<00:16:24.499> a<00:16:24.679> couple<00:16:24.860> of<00:16:25.040> teams<00:16:25.309> that<00:16:25.399> have<00:16:25.639> a 00:16:25.660 --> 00:16:25.670 align:start position:0% there are a couple of teams that have a 00:16:25.670 --> 00:16:27.910 align:start position:0% there are a couple of teams that have a vested<00:16:25.939> interest<00:16:26.600> to<00:16:26.720> make<00:16:26.990> a<00:16:27.199> frame<00:16:27.499> to<00:16:27.709> as 00:16:27.910 --> 00:16:27.920 align:start position:0% vested interest to make a frame to as 00:16:27.920 --> 00:16:31.869 align:start position:0% vested interest to make a frame to as efficient<00:16:28.429> as<00:16:28.579> possible<00:16:29.889> also<00:16:30.889> it<00:16:31.429> will<00:16:31.610> be<00:16:31.730> a 00:16:31.869 --> 00:16:31.879 align:start position:0% efficient as possible also it will be a 00:16:31.879 --> 00:16:34.119 align:start position:0% efficient as possible also it will be a significant<00:16:32.660> upgrade<00:16:32.869> in<00:16:33.379> terms<00:16:33.679> of<00:16:33.860> carbon 00:16:34.119 --> 00:16:34.129 align:start position:0% significant upgrade in terms of carbon 00:16:34.129 --> 00:16:36.639 align:start position:0% significant upgrade in terms of carbon footprint<00:16:34.759> so<00:16:35.119> no<00:16:35.509> one<00:16:35.689> will<00:16:35.899> be<00:16:36.019> able<00:16:36.079> to<00:16:36.379> say 00:16:36.639 --> 00:16:36.649 align:start position:0% footprint so no one will be able to say 00:16:36.649 --> 00:16:38.999 align:start position:0% footprint so no one will be able to say anymore<00:16:37.040> blockchain<00:16:37.670> is<00:16:37.819> wasting<00:16:38.299> energy 00:16:38.999 --> 00:16:39.009 align:start position:0% anymore blockchain is wasting energy 00:16:39.009 --> 00:16:42.429 align:start position:0% anymore blockchain is wasting energy even<00:16:40.009> though<00:16:40.160> we<00:16:40.399> we<00:16:41.329> know<00:16:41.540> that<00:16:41.839> it's<00:16:42.170> used 00:16:42.429 --> 00:16:42.439 align:start position:0% even though we we know that it's used 00:16:42.439 --> 00:16:45.239 align:start position:0% even though we we know that it's used for<00:16:42.589> securing<00:16:43.540> some<00:16:44.540> so<00:16:44.689> ship<00:16:44.869> resistance 00:16:45.239 --> 00:16:45.249 align:start position:0% for securing some so ship resistance 00:16:45.249 --> 00:16:47.139 align:start position:0% for securing some so ship resistance permissionless<00:16:46.249> and<00:16:46.730> stuff 00:16:47.139 --> 00:16:47.149 align:start position:0% permissionless and stuff 00:16:47.149 --> 00:16:51.669 align:start position:0% permissionless and stuff the<00:16:48.110> consensus<00:16:48.769> layer<00:16:48.949> is<00:16:49.309> quite<00:16:50.089> solid<00:16:50.679> we 00:16:51.669 --> 00:16:51.679 align:start position:0% the consensus layer is quite solid we 00:16:51.679 --> 00:16:56.559 align:start position:0% the consensus layer is quite solid we need<00:16:52.009> only<00:16:52.189> just<00:16:52.759> focus<00:16:53.749> effort<00:16:54.230> and<00:16:55.569> the 00:16:56.559 --> 00:16:56.569 align:start position:0% need only just focus effort and the 00:16:56.569 --> 00:16:58.629 align:start position:0% need only just focus effort and the unknowns<00:16:56.929> that<00:16:57.170> I<00:16:57.199> talked<00:16:57.499> about<00:16:57.639> natural 00:16:58.629 --> 00:16:58.639 align:start position:0% unknowns that I talked about natural 00:16:58.639 --> 00:17:02.819 align:start position:0% unknowns that I talked about natural radiation<00:16:59.119> phase<00:16:59.600> one<00:16:59.839> and<00:17:00.019> phase<00:17:00.259> two 00:17:02.819 --> 00:17:02.829 align:start position:0% 00:17:02.829 --> 00:17:05.410 align:start position:0% thank<00:17:03.829> you<00:17:03.949> very<00:17:04.130> much 00:17:05.410 --> 00:17:05.420 align:start position:0% thank you very much 00:17:05.420 --> 00:17:15.340 align:start position:0% thank you very much [Applause] 00:17:15.340 --> 00:17:15.350 align:start position:0% 00:17:15.350 --> 00:17:17.410 align:start position:0% you