WEBVTT Kind: captions Language: en 00:00:01.070 --> 00:00:17.550 align:start position:0% [Applause] 00:00:17.550 --> 00:00:17.560 align:start position:0% 00:00:17.560 --> 00:00:28.109 align:start position:0% good<00:00:18.560> morning<00:00:18.890> thank<00:00:19.700> you<00:00:19.970> for<00:00:20.960> coming<00:00:21.350> thank 00:00:28.109 --> 00:00:28.119 align:start position:0% 00:00:28.119 --> 00:00:31.600 align:start position:0% you<00:00:29.119> for<00:00:29.240> getting<00:00:29.600> up<00:00:30.050> so<00:00:30.080> early<00:00:30.380> to<00:00:31.010> attend<00:00:31.430> a 00:00:31.600 --> 00:00:31.610 align:start position:0% you for getting up so early to attend a 00:00:31.610 --> 00:00:40.060 align:start position:0% you for getting up so early to attend a breakout<00:00:32.559> so<00:00:35.590> so<00:00:36.590> the<00:00:37.720> 2.0<00:00:38.720> phase<00:00:39.020> one<00:00:39.290> is<00:00:39.770> two 00:00:40.060 --> 00:00:40.070 align:start position:0% breakout so so the 2.0 phase one is two 00:00:40.070 --> 00:00:44.110 align:start position:0% breakout so so the 2.0 phase one is two separate<00:00:40.850> experience<00:00:42.400> this<00:00:43.400> is<00:00:43.670> the<00:00:43.879> agenda 00:00:44.110 --> 00:00:44.120 align:start position:0% separate experience this is the agenda 00:00:44.120 --> 00:00:48.369 align:start position:0% separate experience this is the agenda today<00:00:44.600> so<00:00:46.000> for<00:00:47.000> the<00:00:47.089> first<00:00:47.360> two<00:00:47.870> minutes<00:00:48.050> in 00:00:48.369 --> 00:00:48.379 align:start position:0% today so for the first two minutes in 00:00:48.379 --> 00:00:52.479 align:start position:0% today so for the first two minutes in welcoming<00:00:48.920> and<00:00:50.500> is<00:00:51.500> to<00:00:51.710> design<00:00:52.100> construction 00:00:52.479 --> 00:00:52.489 align:start position:0% welcoming and is to design construction 00:00:52.489 --> 00:00:56.399 align:start position:0% welcoming and is to design construction and<00:00:52.879> other<00:00:53.600> minutes<00:00:54.500> we<00:00:54.739> have<00:00:54.920> our<00:00:55.519> and<00:00:55.940> very 00:00:56.399 --> 00:00:56.409 align:start position:0% and other minutes we have our and very 00:00:56.409 --> 00:00:59.920 align:start position:0% and other minutes we have our and very diffused<00:00:57.409> into<00:00:58.190> this<00:00:58.820> case<00:00:59.059> is<00:00:59.299> out<00:00:59.600> there 00:00:59.920 --> 00:00:59.930 align:start position:0% diffused into this case is out there 00:00:59.930 --> 00:01:03.670 align:start position:0% diffused into this case is out there there<00:01:00.320> are<00:01:00.379> two<00:01:00.830> new<00:01:01.010> associates<00:01:02.350> and<00:01:03.350> then<00:01:03.530> we 00:01:03.670 --> 00:01:03.680 align:start position:0% there are two new associates and then we 00:01:03.680 --> 00:01:07.030 align:start position:0% there are two new associates and then we have<00:01:03.830> about<00:01:04.780> 30<00:01:05.780> minutes<00:01:06.140> per<00:01:06.380> order<00:01:06.650> is<00:01:06.830> one 00:01:07.030 --> 00:01:07.040 align:start position:0% have about 30 minutes per order is one 00:01:07.040 --> 00:01:10.090 align:start position:0% have about 30 minutes per order is one discussion<00:01:07.610> and<00:01:07.909> then<00:01:08.840> hopefully<00:01:09.350> we'll<00:01:09.830> have 00:01:10.090 --> 00:01:10.100 align:start position:0% discussion and then hopefully we'll have 00:01:10.100 --> 00:01:15.790 align:start position:0% discussion and then hopefully we'll have a<00:01:10.159> little<00:01:10.880> break<00:01:11.890> and<00:01:12.890> then<00:01:13.660> we<00:01:14.660> will<00:01:14.800> protein 00:01:15.790 --> 00:01:15.800 align:start position:0% a little break and then we will protein 00:01:15.800 --> 00:01:17.740 align:start position:0% a little break and then we will protein they<00:01:16.070> were<00:01:16.130> thanking<00:01:16.820> us 00:01:17.740 --> 00:01:17.750 align:start position:0% they were thanking us 00:01:17.750 --> 00:01:21.810 align:start position:0% they were thanking us action<00:01:18.020> of<00:01:18.230> the<00:01:18.470> is<00:01:19.220> to<00:01:20.050> filter<00:01:21.050> experience 00:01:21.810 --> 00:01:21.820 align:start position:0% action of the is to filter experience 00:01:21.820 --> 00:01:28.630 align:start position:0% action of the is to filter experience then<00:01:24.310> 25<00:01:25.310> minutes<00:01:25.670> to<00:01:26.360> discuss<00:01:27.130> people<00:01:28.130> about 00:01:28.630 --> 00:01:28.640 align:start position:0% then 25 minutes to discuss people about 00:01:28.640 --> 00:01:32.860 align:start position:0% then 25 minutes to discuss people about the<00:01:29.590> experience<00:01:30.590> of<00:01:30.740> a<00:01:31.130> stream<00:01:31.820> and<00:01:32.660> in 00:01:32.860 --> 00:01:32.870 align:start position:0% the experience of a stream and in 00:01:32.870 --> 00:01:36.580 align:start position:0% the experience of a stream and in another<00:01:34.030> 25<00:01:35.030> minutes<00:01:35.240> things<00:01:35.690> about<00:01:35.930> parshat 00:01:36.580 --> 00:01:36.590 align:start position:0% another 25 minutes things about parshat 00:01:36.590 --> 00:01:42.060 align:start position:0% another 25 minutes things about parshat sensations<00:01:37.310> that<00:01:37.910> most<00:01:38.240> people<00:01:38.950> care<00:01:39.950> about 00:01:42.060 --> 00:01:42.070 align:start position:0% sensations that most people care about 00:01:42.070 --> 00:01:47.859 align:start position:0% sensations that most people care about anything<00:01:44.320> so<00:01:45.320> this<00:01:45.650> is<00:01:46.040> done<00:01:46.510> we<00:01:47.510> have<00:01:47.540> the 00:01:47.859 --> 00:01:47.869 align:start position:0% anything so this is done we have the 00:01:47.869 --> 00:01:53.920 align:start position:0% anything so this is done we have the collateral<00:01:48.740> red<00:01:49.340> signals<00:01:49.850> here<00:01:50.360> and<00:01:52.540> if<00:01:53.540> it 00:01:53.920 --> 00:01:53.930 align:start position:0% collateral red signals here and if it 00:01:53.930 --> 00:02:00.690 align:start position:0% collateral red signals here and if it was<00:01:54.140> here<00:01:54.440> and 00:02:00.690 --> 00:02:00.700 align:start position:0% 00:02:00.700 --> 00:02:03.520 align:start position:0% also<00:02:01.700> it<00:02:01.880> to<00:02:02.030> have<00:02:02.270> some<00:02:02.509> question<00:02:02.990> that<00:02:03.020> we 00:02:03.520 --> 00:02:03.530 align:start position:0% also it to have some question that we 00:02:03.530 --> 00:02:07.330 align:start position:0% also it to have some question that we might<00:02:03.920> not<00:02:04.369> have<00:02:04.430> time<00:02:04.940> during<00:02:05.950> the<00:02:06.950> breakout 00:02:07.330 --> 00:02:07.340 align:start position:0% might not have time during the breakout 00:02:07.340 --> 00:02:10.900 align:start position:0% might not have time during the breakout and<00:02:07.670> we<00:02:08.119> can<00:02:08.300> also<00:02:08.450> no<00:02:08.750> not<00:02:08.959> you<00:02:09.520> and<00:02:10.520> hopefully 00:02:10.900 --> 00:02:10.910 align:start position:0% and we can also no not you and hopefully 00:02:10.910 --> 00:02:16.210 align:start position:0% and we can also no not you and hopefully you<00:02:11.300> have<00:02:11.450> time<00:02:12.280> to<00:02:13.959> and<00:02:14.959> we<00:02:15.410> encourage<00:02:16.190> that 00:02:16.210 --> 00:02:16.220 align:start position:0% you have time to and we encourage that 00:02:16.220 --> 00:02:18.970 align:start position:0% you have time to and we encourage that have<00:02:16.880> can<00:02:17.300> have<00:02:17.570> more<00:02:17.800> conversations<00:02:18.800> and 00:02:18.970 --> 00:02:18.980 align:start position:0% have can have more conversations and 00:02:18.980 --> 00:02:22.960 align:start position:0% have can have more conversations and especially<00:02:19.790> this<00:02:19.940> room<00:02:20.239> and<00:02:21.190> so<00:02:22.190> on<00:02:22.610> we<00:02:22.940> have 00:02:22.960 --> 00:02:22.970 align:start position:0% especially this room and so on we have 00:02:22.970 --> 00:02:25.270 align:start position:0% especially this room and so on we have two<00:02:23.480> months<00:02:23.720> to<00:02:23.959> tell<00:02:24.320> you<00:02:24.620> so<00:02:24.860> if<00:02:25.070> you<00:02:25.250> have 00:02:25.270 --> 00:02:25.280 align:start position:0% two months to tell you so if you have 00:02:25.280 --> 00:02:26.199 align:start position:0% two months to tell you so if you have questions 00:02:26.199 --> 00:02:26.209 align:start position:0% questions 00:02:26.209 --> 00:02:34.180 align:start position:0% questions expecially<00:02:27.049> and<00:02:31.060> yes<00:02:32.530> we're<00:02:33.530> gonna<00:02:33.739> empty 00:02:34.180 --> 00:02:34.190 align:start position:0% expecially and yes we're gonna empty 00:02:34.190 --> 00:02:36.340 align:start position:0% expecially and yes we're gonna empty some<00:02:34.489> of<00:02:34.610> these<00:02:34.760> seats<00:02:35.360> up<00:02:35.750> here<00:02:35.780> in<00:02:36.170> front 00:02:36.340 --> 00:02:36.350 align:start position:0% some of these seats up here in front 00:02:36.350 --> 00:02:38.320 align:start position:0% some of these seats up here in front probably<00:02:36.709> education<00:02:37.700> that<00:02:37.850> you<00:02:37.940> want<00:02:38.090> to<00:02:38.209> like 00:02:38.320 --> 00:02:38.330 align:start position:0% probably education that you want to like 00:02:38.330 --> 00:02:41.949 align:start position:0% probably education that you want to like engage<00:02:38.750> that<00:02:39.250> slightly<00:02:40.250> longer<00:02:40.630> exchange<00:02:41.630> and 00:02:41.949 --> 00:02:41.959 align:start position:0% engage that slightly longer exchange and 00:02:41.959 --> 00:02:46.890 align:start position:0% engage that slightly longer exchange and feel<00:02:42.320> free<00:02:42.530> to<00:02:42.560> buy<00:02:42.830> travel<00:02:43.160> visa<00:02:43.850> frontier 00:02:46.890 --> 00:02:46.900 align:start position:0% 00:02:46.900 --> 00:02:51.160 align:start position:0% and<00:02:47.900> when<00:02:48.620> you<00:02:48.769> are<00:02:48.920> speaking<00:02:49.750> the<00:02:50.750> beginning 00:02:51.160 --> 00:02:51.170 align:start position:0% and when you are speaking the beginning 00:02:51.170 --> 00:02:53.050 align:start position:0% and when you are speaking the beginning please 00:02:53.050 --> 00:02:53.060 align:start position:0% please 00:02:53.060 --> 00:03:01.429 align:start position:0% please yeah<00:02:54.060> I<00:02:54.620> always<00:02:57.650> like<00:02:58.650> that<00:02:58.859> and<00:02:59.870> so<00:03:00.870> we<00:03:01.200> hope 00:03:01.429 --> 00:03:01.439 align:start position:0% yeah I always like that and so we hope 00:03:01.439 --> 00:03:03.380 align:start position:0% yeah I always like that and so we hope that<00:03:01.469> would<00:03:02.129> be<00:03:02.280> fun 00:03:03.380 --> 00:03:03.390 align:start position:0% that would be fun 00:03:03.390 --> 00:03:30.949 align:start position:0% that would be fun for<00:03:03.599> God<00:03:03.780> and<00:03:04.109> but<00:03:04.739> please<00:03:05.510> and<00:03:29.810> during<00:03:30.810> the 00:03:30.949 --> 00:03:30.959 align:start position:0% for God and but please and during the 00:03:30.959 --> 00:03:35.270 align:start position:0% for God and but please and during the day<00:03:31.139> I<00:03:31.829> work<00:03:32.430> for<00:03:32.700> status<00:03:33.090> good<00:03:33.659> night<00:03:34.280> dream 00:03:35.270 --> 00:03:35.280 align:start position:0% day I work for status good night dream 00:03:35.280 --> 00:03:41.000 align:start position:0% day I work for status good night dream of<00:03:38.780> so<00:03:39.780> just<00:03:39.989> quickly<00:03:40.260> about<00:03:40.560> what<00:03:40.769> we're 00:03:41.000 --> 00:03:41.010 align:start position:0% of so just quickly about what we're 00:03:41.010 --> 00:03:46.039 align:start position:0% of so just quickly about what we're about<00:03:42.500> by<00:03:43.500> now<00:03:43.739> maybe<00:03:44.609> you<00:03:44.909> are<00:03:44.939> it<00:03:45.269> is<00:03:45.450> like<00:03:45.510> my 00:03:46.039 --> 00:03:46.049 align:start position:0% about by now maybe you are it is like my 00:03:46.049 --> 00:03:49.670 align:start position:0% about by now maybe you are it is like my times<00:03:46.379> already<00:03:46.590> hearing<00:03:47.010> this<00:03:48.230> another<00:03:49.230> like 00:03:49.670 --> 00:03:49.680 align:start position:0% times already hearing this another like 00:03:49.680 --> 00:03:53.300 align:start position:0% times already hearing this another like is<00:03:49.889> to<00:03:50.129> thing<00:03:50.430> but<00:03:51.319> the<00:03:52.319> idea<00:03:52.349> is<00:03:52.709> that<00:03:53.069> these 00:03:53.300 --> 00:03:53.310 align:start position:0% is to thing but the idea is that these 00:03:53.310 --> 00:03:55.129 align:start position:0% is to thing but the idea is that these two<00:03:53.669> will<00:03:53.879> be<00:03:54.000> delivered<00:03:54.359> in<00:03:54.389> these<00:03:54.659> faces<00:03:55.109> and 00:03:55.129 --> 00:03:55.139 align:start position:0% two will be delivered in these faces and 00:03:55.139 --> 00:03:58.309 align:start position:0% two will be delivered in these faces and huge<00:03:55.469> face<00:03:55.709> sort<00:03:56.099> of<00:03:56.190> represents<00:03:56.729> a<00:03:57.319> little 00:03:58.309 --> 00:03:58.319 align:start position:0% huge face sort of represents a little 00:03:58.319 --> 00:04:01.759 align:start position:0% huge face sort of represents a little feature<00:03:58.530> sent<00:03:59.419> I<00:04:00.419> think<00:04:01.109> a<00:04:01.169> good<00:04:01.319> reason<00:04:01.739> for 00:04:01.759 --> 00:04:01.769 align:start position:0% feature sent I think a good reason for 00:04:01.769 --> 00:04:06.319 align:start position:0% feature sent I think a good reason for doing<00:04:02.010> it<00:04:02.280> this<00:04:02.459> way<00:04:02.519> is<00:04:02.970> because<00:04:03.780> we<00:04:04.169> can<00:04:05.329> live 00:04:06.319 --> 00:04:06.329 align:start position:0% doing it this way is because we can live 00:04:06.329 --> 00:04:10.159 align:start position:0% doing it this way is because we can live test<00:04:07.699> components<00:04:08.699> cook<00:04:09.000> and<00:04:09.239> we<00:04:09.419> release<00:04:09.720> like 00:04:10.159 --> 00:04:10.169 align:start position:0% test components cook and we release like 00:04:10.169 --> 00:04:12.080 align:start position:0% test components cook and we release like not<00:04:10.590> the<00:04:10.739> whole<00:04:10.859> thing<00:04:10.889> at<00:04:11.220> the<00:04:11.340> same<00:04:11.519> time<00:04:11.819> but 00:04:12.080 --> 00:04:12.090 align:start position:0% not the whole thing at the same time but 00:04:12.090 --> 00:04:16.069 align:start position:0% not the whole thing at the same time but we<00:04:12.720> will<00:04:12.840> start<00:04:13.229> with<00:04:14.150> the<00:04:15.150> beacon<00:04:15.449> chain<00:04:15.750> and 00:04:16.069 --> 00:04:16.079 align:start position:0% we will start with the beacon chain and 00:04:16.079 --> 00:04:19.039 align:start position:0% we will start with the beacon chain and the<00:04:16.199> beacon<00:04:16.470> chain<00:04:16.769> you<00:04:17.609> can<00:04:17.789> say<00:04:18.000> there<00:04:18.180> is<00:04:18.209> a 00:04:19.039 --> 00:04:19.049 align:start position:0% the beacon chain you can say there is a 00:04:19.049 --> 00:04:21.890 align:start position:0% the beacon chain you can say there is a and<00:04:19.859> in<00:04:20.549> light<00:04:20.759> of<00:04:20.789> everything<00:04:21.060> that<00:04:21.569> will<00:04:21.750> be 00:04:21.890 --> 00:04:21.900 align:start position:0% and in light of everything that will be 00:04:21.900 --> 00:04:25.879 align:start position:0% and in light of everything that will be released<00:04:22.229> as<00:04:22.470> easy<00:04:22.680> to<00:04:24.319> its<00:04:25.319> a<00:04:25.410> single<00:04:25.740> piece 00:04:25.879 --> 00:04:25.889 align:start position:0% released as easy to its a single piece 00:04:25.889 --> 00:04:30.830 align:start position:0% released as easy to its a single piece of<00:04:25.919> software<00:04:27.379> it's<00:04:28.379> a<00:04:28.470> single<00:04:28.860> chain<00:04:29.159> and<00:04:29.849> it 00:04:30.830 --> 00:04:30.840 align:start position:0% of software it's a single chain and it 00:04:30.840 --> 00:04:34.070 align:start position:0% of software it's a single chain and it starts<00:04:31.199> by<00:04:31.259> adding<00:04:32.180> two<00:04:33.180> crucial<00:04:33.569> features 00:04:34.070 --> 00:04:34.080 align:start position:0% starts by adding two crucial features 00:04:34.080 --> 00:04:36.770 align:start position:0% starts by adding two crucial features you<00:04:34.229> can<00:04:34.349> say<00:04:34.560> the<00:04:35.039> Google<00:04:35.220> State<00:04:35.669> Patrol<00:04:36.210> give 00:04:36.770 --> 00:04:36.780 align:start position:0% you can say the Google State Patrol give 00:04:36.780 --> 00:04:41.149 align:start position:0% you can say the Google State Patrol give us<00:04:36.930> security<00:04:39.110> everyplace<00:04:40.110> book<00:04:40.349> of<00:04:40.500> work<00:04:40.710> and 00:04:41.149 --> 00:04:41.159 align:start position:0% us security everyplace book of work and 00:04:41.159 --> 00:04:44.330 align:start position:0% us security everyplace book of work and then<00:04:41.430> the<00:04:41.639> randomness<00:04:42.379> that<00:04:43.379> sort<00:04:43.650> of<00:04:43.680> first 00:04:44.330 --> 00:04:44.340 align:start position:0% then the randomness that sort of first 00:04:44.340 --> 00:04:47.119 align:start position:0% then the randomness that sort of first of<00:04:44.550> all<00:04:44.669> yet<00:04:45.030> gives<00:04:45.419> legitimacy<00:04:46.409> to<00:04:47.099> that 00:04:47.119 --> 00:04:47.129 align:start position:0% of all yet gives legitimacy to that 00:04:47.129 --> 00:04:50.149 align:start position:0% of all yet gives legitimacy to that security<00:04:47.550> and<00:04:48.270> second<00:04:48.960> of<00:04:49.020> all<00:04:49.169> perhaps<00:04:49.949> is 00:04:50.149 --> 00:04:50.159 align:start position:0% security and second of all perhaps is 00:04:50.159 --> 00:04:56.149 align:start position:0% security and second of all perhaps is useful<00:04:50.520> if<00:04:50.610> you<00:04:50.639> like<00:04:54.620> the<00:04:55.620> other<00:04:55.740> thing<00:04:56.009> we're 00:04:56.149 --> 00:04:56.159 align:start position:0% useful if you like the other thing we're 00:04:56.159 --> 00:04:58.790 align:start position:0% useful if you like the other thing we're doing<00:04:56.190> is<00:04:56.639> that<00:04:57.050> we're<00:04:58.050> kind<00:04:58.199> of<00:04:58.289> shooting<00:04:58.680> an 00:04:58.790 --> 00:04:58.800 align:start position:0% doing is that we're kind of shooting an 00:04:58.800 --> 00:05:00.740 align:start position:0% doing is that we're kind of shooting an arrow<00:04:58.949> from<00:04:59.310> his<00:04:59.370> onesie<00:04:59.970> so<00:05:00.270> you<00:05:00.449> know<00:05:00.599> when 00:05:00.740 --> 00:05:00.750 align:start position:0% arrow from his onesie so you know when 00:05:00.750 --> 00:05:04.520 align:start position:0% arrow from his onesie so you know when you're<00:05:00.870> building<00:05:00.900> a<00:05:01.530> bridge<00:05:03.199> over<00:05:04.199> a<00:05:04.229> canyon 00:05:04.520 --> 00:05:04.530 align:start position:0% you're building a bridge over a canyon 00:05:04.530 --> 00:05:07.309 align:start position:0% you're building a bridge over a canyon that's<00:05:05.280> what<00:05:05.460> you<00:05:05.610> deserve<00:05:06.060> in<00:05:06.930> price<00:05:07.139> over 00:05:07.309 --> 00:05:07.319 align:start position:0% that's what you deserve in price over 00:05:07.319 --> 00:05:11.899 align:start position:0% that's what you deserve in price over right<00:05:09.680> this<00:05:10.680> is<00:05:10.800> the<00:05:10.949> one<00:05:11.099> way<00:05:11.340> picking<00:05:11.729> from 00:05:11.899 --> 00:05:11.909 align:start position:0% right this is the one way picking from 00:05:11.909 --> 00:05:14.870 align:start position:0% right this is the one way picking from east<00:05:12.150> ones<00:05:12.479> ethos<00:05:13.139> when<00:05:13.440> you<00:05:13.530> wanna<00:05:13.740> become<00:05:14.639> a 00:05:14.870 --> 00:05:14.880 align:start position:0% east ones ethos when you wanna become a 00:05:14.880 --> 00:05:19.040 align:start position:0% east ones ethos when you wanna become a validator<00:05:15.479> on<00:05:16.409> these<00:05:16.590> two<00:05:17.719> we<00:05:18.719> have<00:05:18.900> this 00:05:19.040 --> 00:05:19.050 align:start position:0% validator on these two we have this 00:05:19.050 --> 00:05:20.689 align:start position:0% validator on these two we have this bridge<00:05:19.379> that<00:05:19.680> sort<00:05:19.889> of<00:05:19.949> connects<00:05:20.280> the<00:05:20.520> two 00:05:20.689 --> 00:05:20.699 align:start position:0% bridge that sort of connects the two 00:05:20.699 --> 00:05:23.029 align:start position:0% bridge that sort of connects the two chains<00:05:21.060> in<00:05:21.810> this<00:05:21.960> direction<00:05:22.169> so<00:05:22.590> that<00:05:22.680> we<00:05:22.889> can 00:05:23.029 --> 00:05:23.039 align:start position:0% chains in this direction so that we can 00:05:23.039 --> 00:05:24.740 align:start position:0% chains in this direction so that we can keep<00:05:23.190> track<00:05:23.430> of<00:05:23.639> what's<00:05:23.789> happening 00:05:24.740 --> 00:05:24.750 align:start position:0% keep track of what's happening 00:05:24.750 --> 00:05:30.220 align:start position:0% keep track of what's happening the<00:05:25.130> positive<00:05:26.300> people<00:05:27.300> wanted<00:05:27.690> for<00:05:27.960> a<00:05:27.990> snake 00:05:30.220 --> 00:05:30.230 align:start position:0% the positive people wanted for a snake 00:05:30.230 --> 00:05:32.810 align:start position:0% the positive people wanted for a snake and<00:05:31.230> we're<00:05:31.410> launching<00:05:31.620> this<00:05:31.920> so<00:05:32.160> that<00:05:32.340> we<00:05:32.790> can 00:05:32.810 --> 00:05:32.820 align:start position:0% and we're launching this so that we can 00:05:32.820 --> 00:05:36.770 align:start position:0% and we're launching this so that we can validate<00:05:33.390> these<00:05:33.660> things<00:05:34.280> before<00:05:35.780> developers 00:05:36.770 --> 00:05:36.780 align:start position:0% validate these things before developers 00:05:36.780 --> 00:05:39.410 align:start position:0% validate these things before developers start<00:05:37.350> using<00:05:37.680> the<00:05:37.980> chain<00:05:38.220> right<00:05:38.520> so<00:05:39.300> it<00:05:39.360> is 00:05:39.410 --> 00:05:39.420 align:start position:0% start using the chain right so it is 00:05:39.420 --> 00:05:42.650 align:start position:0% start using the chain right so it is intended<00:05:40.260> Ruby<00:05:40.770> for<00:05:41.270> enthusiasts<00:05:42.270> and<00:05:42.390> people 00:05:42.650 --> 00:05:42.660 align:start position:0% intended Ruby for enthusiasts and people 00:05:42.660 --> 00:05:45.020 align:start position:0% intended Ruby for enthusiasts and people that<00:05:42.780> want<00:05:42.960> to<00:05:43.020> take<00:05:43.200> early<00:05:43.530> we<00:05:44.070> want<00:05:44.280> to<00:05:44.400> learn 00:05:45.020 --> 00:05:45.030 align:start position:0% that want to take early we want to learn 00:05:45.030 --> 00:05:47.270 align:start position:0% that want to take early we want to learn how<00:05:45.270> to<00:05:45.300> run<00:05:45.540> the<00:05:45.600> system<00:05:46.170> they<00:05:46.830> want<00:05:47.010> to<00:05:47.100> learn 00:05:47.270 --> 00:05:47.280 align:start position:0% how to run the system they want to learn 00:05:47.280 --> 00:05:49.460 align:start position:0% how to run the system they want to learn how<00:05:47.340> to<00:05:47.550> validate<00:05:48.000> our<00:05:48.060> client<00:05:48.600> software<00:05:49.170> it 00:05:49.460 --> 00:05:49.470 align:start position:0% how to validate our client software it 00:05:49.470 --> 00:05:51.110 align:start position:0% how to validate our client software it works<00:05:49.650> we<00:05:50.430> want<00:05:50.610> to<00:05:50.670> set<00:05:50.850> up<00:05:50.970> the 00:05:51.110 --> 00:05:51.120 align:start position:0% works we want to set up the 00:05:51.120 --> 00:05:52.670 align:start position:0% works we want to set up the infrastructure<00:05:51.720> so<00:05:52.020> that<00:05:52.050> we<00:05:52.170> have<00:05:52.380> time<00:05:52.620> to 00:05:52.670 --> 00:05:52.680 align:start position:0% infrastructure so that we have time to 00:05:52.680 --> 00:05:56.030 align:start position:0% infrastructure so that we have time to sort<00:05:53.070> of<00:05:53.190> Buddhist<00:05:54.380> without<00:05:55.380> the<00:05:55.530> pressure<00:05:55.800> of 00:05:56.030 --> 00:05:56.040 align:start position:0% sort of Buddhist without the pressure of 00:05:56.040 --> 00:06:03.530 align:start position:0% sort of Buddhist without the pressure of having<00:05:56.510> that<00:05:57.510> developers<00:05:58.350> on<00:05:59.040> the<00:05:59.100> chain<00:06:02.540> then 00:06:03.530 --> 00:06:03.540 align:start position:0% having that developers on the chain then 00:06:03.540 --> 00:06:06.800 align:start position:0% having that developers on the chain then we'll<00:06:03.750> move<00:06:04.290> into<00:06:04.500> phase<00:06:04.830> one<00:06:05.160> and<00:06:05.880> Phase<00:06:06.780> one 00:06:06.800 --> 00:06:06.810 align:start position:0% we'll move into phase one and Phase one 00:06:06.810 --> 00:06:09.320 align:start position:0% we'll move into phase one and Phase one work<00:06:07.290> is<00:06:07.919> sort<00:06:08.340> of<00:06:08.460> the<00:06:08.610> first<00:06:08.790> time<00:06:08.910> that<00:06:09.180> we 00:06:09.320 --> 00:06:09.330 align:start position:0% work is sort of the first time that we 00:06:09.330 --> 00:06:12.140 align:start position:0% work is sort of the first time that we had<00:06:09.450> a<00:06:09.480> bit<00:06:09.660> of<00:06:09.780> complexity<00:06:10.260> to<00:06:10.530> a<00:06:10.560> system<00:06:11.150> we 00:06:12.140 --> 00:06:12.150 align:start position:0% had a bit of complexity to a system we 00:06:12.150 --> 00:06:13.670 align:start position:0% had a bit of complexity to a system we had<00:06:12.470> charts 00:06:13.670 --> 00:06:13.680 align:start position:0% had charts 00:06:13.680 --> 00:06:16.130 align:start position:0% had charts how<00:06:13.830> many<00:06:14.190> would<00:06:14.370> say<00:06:14.610> maybe<00:06:14.850> 64<00:06:15.750> maybe<00:06:15.990> a 00:06:16.130 --> 00:06:16.140 align:start position:0% how many would say maybe 64 maybe a 00:06:16.140 --> 00:06:23.590 align:start position:0% how many would say maybe 64 maybe a thousand<00:06:18.710> and<00:06:20.030> it's<00:06:21.030> all<00:06:21.330> about<00:06:21.630> starting<00:06:22.620> to 00:06:23.590 --> 00:06:23.600 align:start position:0% thousand and it's all about starting to 00:06:23.600 --> 00:06:27.560 align:start position:0% thousand and it's all about starting to prepare<00:06:24.740> for<00:06:26.030> execution<00:06:27.030> but<00:06:27.180> still<00:06:27.419> not 00:06:27.560 --> 00:06:27.570 align:start position:0% prepare for execution but still not 00:06:27.570 --> 00:06:29.570 align:start position:0% prepare for execution but still not doing<00:06:27.870> it<00:06:27.960> so<00:06:28.800> we'll<00:06:28.979> have<00:06:29.010> a<00:06:29.190> couple<00:06:29.460> of 00:06:29.570 --> 00:06:29.580 align:start position:0% doing it so we'll have a couple of 00:06:29.580 --> 00:06:31.280 align:start position:0% doing it so we'll have a couple of examples<00:06:29.729> of<00:06:30.240> what<00:06:30.360> you<00:06:30.450> could<00:06:30.570> possibly<00:06:31.080> do 00:06:31.280 --> 00:06:31.290 align:start position:0% examples of what you could possibly do 00:06:31.290 --> 00:06:33.170 align:start position:0% examples of what you could possibly do when<00:06:31.470> you<00:06:31.560> have<00:06:31.740> shards<00:06:32.160> on<00:06:32.370> on<00:06:32.669> to<00:06:32.910> which<00:06:33.060> you 00:06:33.170 --> 00:06:33.180 align:start position:0% when you have shards on on to which you 00:06:33.180 --> 00:06:35.810 align:start position:0% when you have shards on on to which you complete<00:06:33.510> data<00:06:33.840> and<00:06:34.320> where<00:06:35.310> the<00:06:35.490> chain 00:06:35.810 --> 00:06:35.820 align:start position:0% complete data and where the chain 00:06:35.820 --> 00:06:37.460 align:start position:0% complete data and where the chain guarantees<00:06:36.419> that<00:06:36.450> this<00:06:36.750> data<00:06:37.020> will<00:06:37.260> stay 00:06:37.460 --> 00:06:37.470 align:start position:0% guarantees that this data will stay 00:06:37.470 --> 00:06:40.780 align:start position:0% guarantees that this data will stay around<00:06:37.560> for<00:06:37.979> one 00:06:40.780 --> 00:06:40.790 align:start position:0% 00:06:40.790 --> 00:06:44.230 align:start position:0% [Music] 00:06:44.230 --> 00:06:44.240 align:start position:0% 00:06:44.240 --> 00:06:51.610 align:start position:0% and<00:06:46.060> so<00:06:47.740> if<00:06:48.740> you<00:06:49.009> look<00:06:49.160> at<00:06:49.310> how<00:06:49.490> that<00:06:50.449> works<00:06:50.840> we 00:06:51.610 --> 00:06:51.620 align:start position:0% and so if you look at how that works we 00:06:51.620 --> 00:06:52.960 align:start position:0% and so if you look at how that works we have<00:06:51.800> to<00:06:51.919> click<00:06:52.099> in<00:06:52.280> chain<00:06:52.520> there<00:06:52.940> is 00:06:52.960 --> 00:06:52.970 align:start position:0% have to click in chain there is 00:06:52.970 --> 00:06:57.040 align:start position:0% have to click in chain there is coordinating<00:06:53.840> the<00:06:54.080> data<00:06:54.440> chains<00:06:55.449> post<00:06:56.449> it<00:06:56.870> on 00:06:57.040 --> 00:06:57.050 align:start position:0% coordinating the data chains post it on 00:06:57.050 --> 00:06:59.650 align:start position:0% coordinating the data chains post it on your<00:06:57.289> chain<00:06:57.560> on<00:06:58.160> your<00:06:58.220> defender<00:06:59.120> sharp<00:06:59.419> chain 00:06:59.650 --> 00:06:59.660 align:start position:0% your chain on your defender sharp chain 00:06:59.660 --> 00:07:02.580 align:start position:0% your chain on your defender sharp chain this<00:07:00.319> gets<00:07:00.560> recorded<00:07:01.310> on<00:07:01.729> the<00:07:01.910> beacon<00:07:02.180> chain 00:07:02.580 --> 00:07:02.590 align:start position:0% this gets recorded on the beacon chain 00:07:02.590 --> 00:07:05.350 align:start position:0% this gets recorded on the beacon chain regularly<00:07:03.590> and<00:07:04.430> it's<00:07:05.120> a<00:07:05.240> way<00:07:05.330> of 00:07:05.350 --> 00:07:05.360 align:start position:0% regularly and it's a way of 00:07:05.360 --> 00:07:06.219 align:start position:0% regularly and it's a way of communication 00:07:06.219 --> 00:07:06.229 align:start position:0% communication 00:07:06.229 --> 00:07:10.659 align:start position:0% communication basically<00:07:06.819> so<00:07:07.819> within<00:07:08.030> a<00:07:08.389> single<00:07:08.720> shard<00:07:09.669> you 00:07:10.659 --> 00:07:10.669 align:start position:0% basically so within a single shard you 00:07:10.669 --> 00:07:12.820 align:start position:0% basically so within a single shard you already<00:07:11.060> have<00:07:11.300> available<00:07:12.110> and<00:07:12.650> then<00:07:12.740> you 00:07:12.820 --> 00:07:12.830 align:start position:0% already have available and then you 00:07:12.830 --> 00:07:14.499 align:start position:0% already have available and then you cross<00:07:13.099> link<00:07:13.340> it<00:07:13.490> so<00:07:13.639> that<00:07:13.759> it's<00:07:13.910> available<00:07:14.150> on 00:07:14.499 --> 00:07:14.509 align:start position:0% cross link it so that it's available on 00:07:14.509 --> 00:07:17.020 align:start position:0% cross link it so that it's available on the<00:07:14.630> other<00:07:14.750> strands<00:07:15.020> as<00:07:15.259> well<00:07:15.669> in<00:07:16.669> terms<00:07:16.880> of 00:07:17.020 --> 00:07:17.030 align:start position:0% the other strands as well in terms of 00:07:17.030 --> 00:07:19.779 align:start position:0% the other strands as well in terms of security<00:07:18.130> but<00:07:19.130> you<00:07:19.250> could<00:07:19.400> say<00:07:19.580> that<00:07:19.759> each 00:07:19.779 --> 00:07:19.789 align:start position:0% security but you could say that each 00:07:19.789 --> 00:07:24.430 align:start position:0% security but you could say that each chart<00:07:20.210> lives<00:07:20.780> its<00:07:20.990> own<00:07:21.110> little<00:07:21.289> life<00:07:22.720> and<00:07:23.720> then 00:07:24.430 --> 00:07:24.440 align:start position:0% chart lives its own little life and then 00:07:24.440 --> 00:07:28.050 align:start position:0% chart lives its own little life and then finally<00:07:24.470> in<00:07:24.949> phase<00:07:25.190> two<00:07:26.199> we<00:07:27.199> had<00:07:27.319> the 00:07:28.050 --> 00:07:28.060 align:start position:0% finally in phase two we had the 00:07:28.060 --> 00:07:31.270 align:start position:0% finally in phase two we had the execution<00:07:29.060> engines<00:07:29.419> simple<00:07:29.960> or<00:07:30.050> not<00:07:30.280> Omega 00:07:31.270 --> 00:07:31.280 align:start position:0% execution engines simple or not Omega 00:07:31.280 --> 00:07:36.399 align:start position:0% execution engines simple or not Omega which<00:07:31.520> is<00:07:31.639> different<00:07:33.789> but<00:07:34.789> conceptually<00:07:35.569> that 00:07:36.399 --> 00:07:36.409 align:start position:0% which is different but conceptually that 00:07:36.409 --> 00:07:39.279 align:start position:0% which is different but conceptually that is<00:07:36.590> a<00:07:36.830> separate<00:07:37.340> piece<00:07:37.520> of<00:07:38.289> infrastructure 00:07:39.279 --> 00:07:39.289 align:start position:0% is a separate piece of infrastructure 00:07:39.289 --> 00:07:41.969 align:start position:0% is a separate piece of infrastructure that<00:07:40.220> will<00:07:40.430> enable<00:07:40.669> people<00:07:41.030> to<00:07:41.240> develop 00:07:41.969 --> 00:07:41.979 align:start position:0% that will enable people to develop 00:07:41.979 --> 00:07:47.409 align:start position:0% that will enable people to develop execution<00:07:42.979> engines<00:07:43.659> now<00:07:46.000> we<00:07:47.000> had<00:07:47.120> a<00:07:47.150> long 00:07:47.409 --> 00:07:47.419 align:start position:0% execution engines now we had a long 00:07:47.419 --> 00:07:49.629 align:start position:0% execution engines now we had a long conversations<00:07:48.320> about<00:07:48.380> like<00:07:49.039> to<00:07:49.159> present<00:07:49.310> this 00:07:49.629 --> 00:07:49.639 align:start position:0% conversations about like to present this 00:07:49.639 --> 00:07:51.370 align:start position:0% conversations about like to present this to<00:07:49.699> people<00:07:50.150> yesterday<00:07:50.330> like<00:07:50.780> one<00:07:50.960> of<00:07:51.080> the<00:07:51.199> ways 00:07:51.370 --> 00:07:51.380 align:start position:0% to people yesterday like one of the ways 00:07:51.380 --> 00:07:54.610 align:start position:0% to people yesterday like one of the ways that<00:07:51.530> we<00:07:51.710> came<00:07:51.860> up<00:07:52.009> with<00:07:52.250> it<00:07:52.370> is<00:07:52.490> very<00:07:53.620> dr. 00:07:54.610 --> 00:07:54.620 align:start position:0% that we came up with it is very dr. 00:07:54.620 --> 00:07:55.839 align:start position:0% that we came up with it is very dr. phase<00:07:54.800> one<00:07:55.039> that's<00:07:55.310> kind<00:07:55.490> of<00:07:55.520> like<00:07:55.639> when<00:07:55.759> you 00:07:55.839 --> 00:07:55.849 align:start position:0% phase one that's kind of like when you 00:07:55.849 --> 00:08:00.670 align:start position:0% phase one that's kind of like when you designed<00:07:56.210> a<00:07:56.360> computer<00:07:57.259> and<00:07:57.729> and<00:07:59.500> the<00:08:00.500> new 00:08:00.670 --> 00:08:00.680 align:start position:0% designed a computer and and the new 00:08:00.680 --> 00:08:02.439 align:start position:0% designed a computer and and the new computer<00:08:01.159> it<00:08:01.280> suddenly<00:08:01.580> it<00:08:01.759> is<00:08:02.030> a<00:08:02.060> multiple 00:08:02.439 --> 00:08:02.449 align:start position:0% computer it suddenly it is a multiple 00:08:02.449 --> 00:08:08.159 align:start position:0% computer it suddenly it is a multiple multi-core<00:08:03.440> processing<00:08:04.990> unit<00:08:05.990> and<00:08:06.940> then 00:08:08.159 --> 00:08:08.169 align:start position:0% multi-core processing unit and then 00:08:08.169 --> 00:08:13.600 align:start position:0% multi-core processing unit and then phase<00:08:09.169> two<00:08:09.580> is<00:08:10.580> like<00:08:12.130> somewhere<00:08:13.130> between<00:08:13.280> the 00:08:13.600 --> 00:08:13.610 align:start position:0% phase two is like somewhere between the 00:08:13.610 --> 00:08:15.689 align:start position:0% phase two is like somewhere between the operating<00:08:13.969> system<00:08:14.449> and<00:08:14.599> the<00:08:14.690> drivers<00:08:15.080> and 00:08:15.689 --> 00:08:15.699 align:start position:0% operating system and the drivers and 00:08:15.699 --> 00:08:18.730 align:start position:0% operating system and the drivers and parlor<00:08:16.699> it's<00:08:17.270> still<00:08:17.630> not<00:08:17.840> something<00:08:18.110> that<00:08:18.560> we 00:08:18.730 --> 00:08:18.740 align:start position:0% parlor it's still not something that we 00:08:18.740 --> 00:08:21.490 align:start position:0% parlor it's still not something that we expect<00:08:19.039> everybody<00:08:20.000> to<00:08:20.270> do<00:08:20.569> if<00:08:20.930> you're<00:08:21.259> that 00:08:21.490 --> 00:08:21.500 align:start position:0% expect everybody to do if you're that 00:08:21.500 --> 00:08:23.379 align:start position:0% expect everybody to do if you're that developer<00:08:22.069> you're<00:08:22.610> probably<00:08:22.819> not<00:08:23.150> gonna 00:08:23.379 --> 00:08:23.389 align:start position:0% developer you're probably not gonna 00:08:23.389 --> 00:08:28.719 align:start position:0% developer you're probably not gonna release<00:08:23.719> any<00:08:24.020> if<00:08:24.860> you're<00:08:25.870> designing<00:08:26.870> a<00:08:27.729> large 00:08:28.719 --> 00:08:28.729 align:start position:0% release any if you're designing a large 00:08:28.729 --> 00:08:32.319 align:start position:0% release any if you're designing a large contract<00:08:29.270> system<00:08:30.340> with<00:08:31.340> very<00:08:31.580> moving<00:08:31.940> parts 00:08:32.319 --> 00:08:32.329 align:start position:0% contract system with very moving parts 00:08:32.329 --> 00:08:35.310 align:start position:0% contract system with very moving parts then<00:08:32.599> yes<00:08:33.140> maybe<00:08:33.680> maybe<00:08:34.370> you<00:08:34.610> have<00:08:34.820> like 00:08:35.310 --> 00:08:35.320 align:start position:0% then yes maybe maybe you have like 00:08:35.320 --> 00:08:38.870 align:start position:0% then yes maybe maybe you have like special<00:08:36.330> need<00:08:37.330> for<00:08:37.600> it<00:08:37.690> through<00:08:38.410> designing 00:08:38.870 --> 00:08:38.880 align:start position:0% special need for it through designing 00:08:38.880 --> 00:08:42.840 align:start position:0% special need for it through designing the<00:08:39.880> EVM<00:08:40.350> replacement<00:08:41.350> for<00:08:41.500> aetherium<00:08:41.800> -<00:08:42.100> yeah 00:08:42.840 --> 00:08:42.850 align:start position:0% the EVM replacement for aetherium - yeah 00:08:42.850 --> 00:08:46.410 align:start position:0% the EVM replacement for aetherium - yeah then<00:08:43.300> you<00:08:43.930> will<00:08:44.020> design<00:08:44.380> the<00:08:44.560> me<00:08:44.740> if<00:08:45.730> maybe<00:08:46.180> you 00:08:46.410 --> 00:08:46.420 align:start position:0% then you will design the me if maybe you 00:08:46.420 --> 00:08:50.750 align:start position:0% then you will design the me if maybe you want<00:08:46.600> integrate<00:08:48.060> their<00:08:49.060> knowledge<00:08:49.450> groups<00:08:49.750> or 00:08:50.750 --> 00:08:50.760 align:start position:0% want integrate their knowledge groups or 00:08:50.760 --> 00:08:53.070 align:start position:0% want integrate their knowledge groups or let's<00:08:51.760> say<00:08:51.910> that<00:08:51.940> we<00:08:52.270> wanted<00:08:52.570> to<00:08:52.690> didn't 00:08:53.070 --> 00:08:53.080 align:start position:0% let's say that we wanted to didn't 00:08:53.080 --> 00:08:57.510 align:start position:0% let's say that we wanted to didn't something<00:08:54.010> like<00:08:54.280> the<00:08:54.700> cash<00:08:54.940> inside<00:08:55.420> of<00:08:56.520> their 00:08:57.510 --> 00:08:57.520 align:start position:0% something like the cash inside of their 00:08:57.520 --> 00:08:59.640 align:start position:0% something like the cash inside of their one<00:08:57.760> that<00:08:57.970> maybe<00:08:58.300> they<00:08:58.840> wanted<00:08:59.110> irrelevant 00:08:59.640 --> 00:08:59.650 align:start position:0% one that maybe they wanted irrelevant 00:08:59.650 --> 00:09:02.820 align:start position:0% one that maybe they wanted irrelevant fee<00:09:00.310> for<00:09:00.790> that<00:09:00.820> but<00:09:01.540> these<00:09:01.690> are<00:09:01.750> like<00:09:02.050> they're 00:09:02.820 --> 00:09:02.830 align:start position:0% fee for that but these are like they're 00:09:02.830 --> 00:09:07.710 align:start position:0% fee for that but these are like they're not<00:09:03.300> bob's<00:09:04.300> that<00:09:06.330> something<00:09:07.330> that<00:09:07.360> you<00:09:07.600> just 00:09:07.710 --> 00:09:07.720 align:start position:0% not bob's that something that you just 00:09:07.720 --> 00:09:10.320 align:start position:0% not bob's that something that you just deployed<00:09:08.110> like<00:09:08.320> me<00:09:08.560> like<00:09:09.250> refined<00:09:09.760> costly 00:09:10.320 --> 00:09:10.330 align:start position:0% deployed like me like refined costly 00:09:10.330 --> 00:09:12.990 align:start position:0% deployed like me like refined costly both<00:09:10.630> in<00:09:10.810> terms<00:09:11.020> of<00:09:11.170> development<00:09:11.680> and<00:09:12.000> in 00:09:12.990 --> 00:09:13.000 align:start position:0% both in terms of development and in 00:09:13.000 --> 00:09:15.150 align:start position:0% both in terms of development and in terms<00:09:13.240> of<00:09:13.390> the<00:09:13.480> community<00:09:13.990> change<00:09:14.470> within 00:09:15.150 --> 00:09:15.160 align:start position:0% terms of the community change within 00:09:15.160 --> 00:09:18.260 align:start position:0% terms of the community change within that<00:09:15.460> little<00:09:15.670> world<00:09:16.740> they<00:09:17.740> might<00:09:17.920> offer 00:09:18.260 --> 00:09:18.270 align:start position:0% that little world they might offer 00:09:18.270 --> 00:09:20.550 align:start position:0% that little world they might offer application<00:09:19.270> development<00:09:19.690> as<00:09:19.990> we<00:09:20.200> know<00:09:20.350> it<00:09:20.410> on 00:09:20.550 --> 00:09:20.560 align:start position:0% application development as we know it on 00:09:20.560 --> 00:09:26.810 align:start position:0% application development as we know it on the<00:09:20.680> third<00:09:20.920> one<00:09:21.160> today<00:09:23.520> we'll<00:09:24.600> start<00:09:25.600> with<00:09:25.810> two 00:09:26.810 --> 00:09:26.820 align:start position:0% the third one today we'll start with two 00:09:26.820 --> 00:09:29.070 align:start position:0% the third one today we'll start with two presentations<00:09:27.820> that<00:09:28.240> will<00:09:28.420> introduce<00:09:28.720> sort 00:09:29.070 --> 00:09:29.080 align:start position:0% presentations that will introduce sort 00:09:29.080 --> 00:09:30.720 align:start position:0% presentations that will introduce sort of<00:09:29.140> phase<00:09:29.380> one<00:09:29.590> and<00:09:29.770> one<00:09:29.920> what<00:09:30.610> you 00:09:30.720 --> 00:09:30.730 align:start position:0% of phase one and one what you 00:09:30.730 --> 00:09:34.980 align:start position:0% of phase one and one what you potentially<00:09:31.720> do<00:09:31.900> when<00:09:32.080> you<00:09:32.200> have<00:09:33.750> faced<00:09:34.750> one 00:09:34.980 --> 00:09:34.990 align:start position:0% potentially do when you have faced one 00:09:34.990 --> 00:09:44.690 align:start position:0% potentially do when you have faced one available<00:09:36.780> with<00:09:37.780> battery<00:09:43.200> we<00:09:44.200> can<00:09:44.230> be<00:09:44.470> just 00:09:44.690 --> 00:09:44.700 align:start position:0% available with battery we can be just 00:09:44.700 --> 00:09:49.440 align:start position:0% available with battery we can be just dizzy<00:09:45.700> cable<00:09:45.970> and<00:09:46.270> then<00:09:47.010> mr.<00:09:48.010> co-op<00:09:48.190> and<00:09:49.150> these 00:09:49.440 --> 00:09:49.450 align:start position:0% dizzy cable and then mr. co-op and these 00:09:49.450 --> 00:09:51.210 align:start position:0% dizzy cable and then mr. co-op and these are<00:09:49.600> two<00:09:49.810> kind<00:09:50.170> of<00:09:50.230> scalable<00:09:50.650> exclusions<00:09:51.160> that 00:09:51.210 --> 00:09:51.220 align:start position:0% are two kind of scalable exclusions that 00:09:51.220 --> 00:09:58.590 align:start position:0% are two kind of scalable exclusions that we<00:09:51.400> might<00:09:51.610> use<00:09:51.640> on<00:09:52.000> in<00:09:52.270> student<00:09:55.320> so 00:09:58.590 --> 00:09:58.600 align:start position:0% 00:09:58.600 --> 00:10:04.960 align:start position:0% [Music] 00:10:04.960 --> 00:10:04.970 align:start position:0% 00:10:04.970 --> 00:10:09.890 align:start position:0% all<00:10:05.970> right<00:10:07.880> so<00:10:08.880> okay<00:10:09.210> so<00:10:09.270> the<00:10:09.510> way<00:10:09.600> that<00:10:09.630> the 00:10:09.890 --> 00:10:09.900 align:start position:0% all right so okay so the way that the 00:10:09.900 --> 00:10:13.880 align:start position:0% all right so okay so the way that the role<00:10:10.650> of<00:10:10.680> courts<00:10:10.920> is<00:10:11.070> that<00:10:11.100> we<00:10:11.340> have<00:10:11.550> a<00:10:12.890> zero 00:10:13.880 --> 00:10:13.890 align:start position:0% role of courts is that we have a zero 00:10:13.890 --> 00:10:15.080 align:start position:0% role of courts is that we have a zero knowledge<00:10:14.010> proof<00:10:14.160> is<00:10:14.460> that<00:10:14.490> we<00:10:14.700> use<00:10:14.880> to 00:10:15.080 --> 00:10:15.090 align:start position:0% knowledge proof is that we use to 00:10:15.090 --> 00:10:16.820 align:start position:0% knowledge proof is that we use to compress<00:10:15.450> the<00:10:15.630> state<00:10:15.810> transition<00:10:16.290> so<00:10:16.710> the 00:10:16.820 --> 00:10:16.830 align:start position:0% compress the state transition so the 00:10:16.830 --> 00:10:18.560 align:start position:0% compress the state transition so the state<00:10:17.010> transition<00:10:17.490> includes<00:10:17.940> the<00:10:18.090> signature 00:10:18.560 --> 00:10:18.570 align:start position:0% state transition includes the signature 00:10:18.570 --> 00:10:21.680 align:start position:0% state transition includes the signature verification<00:10:18.890> and<00:10:19.890> the<00:10:19.950> Markov<00:10:20.490> will<00:10:21.030> treat 00:10:21.680 --> 00:10:21.690 align:start position:0% verification and the Markov will treat 00:10:21.690 --> 00:10:23.870 align:start position:0% verification and the Markov will treat all<00:10:21.780> things<00:10:22.050> because<00:10:23.040> we<00:10:23.160> do<00:10:23.280> this<00:10:23.430> inside<00:10:23.730> as 00:10:23.870 --> 00:10:23.880 align:start position:0% all things because we do this inside as 00:10:23.880 --> 00:10:26.480 align:start position:0% all things because we do this inside as they're<00:10:24.000> not<00:10:24.150> proof<00:10:24.450> we<00:10:24.660> have<00:10:24.840> a<00:10:25.490> northern 00:10:26.480 --> 00:10:26.490 align:start position:0% they're not proof we have a northern 00:10:26.490 --> 00:10:28.360 align:start position:0% they're not proof we have a northern system<00:10:26.880> cannot<00:10:27.180> enter<00:10:27.480> the<00:10:27.660> lingual<00:10:27.960> States 00:10:28.360 --> 00:10:28.370 align:start position:0% system cannot enter the lingual States 00:10:28.370 --> 00:10:30.860 align:start position:0% system cannot enter the lingual States so<00:10:29.370> if<00:10:29.580> someone<00:10:29.850> wants<00:10:30.090> to<00:10:30.150> steal<00:10:30.450> money<00:10:30.750> from 00:10:30.860 --> 00:10:30.870 align:start position:0% so if someone wants to steal money from 00:10:30.870 --> 00:10:33.050 align:start position:0% so if someone wants to steal money from someone<00:10:31.320> else<00:10:31.500> they<00:10:31.770> can't<00:10:32.640> do<00:10:32.760> know<00:10:32.940> that 00:10:33.050 --> 00:10:33.060 align:start position:0% someone else they can't do know that 00:10:33.060 --> 00:10:36.140 align:start position:0% someone else they can't do know that they<00:10:33.240> have<00:10:33.360> a<00:10:33.390> policy<00:10:33.630> that<00:10:33.930> you<00:10:34.200> think<00:10:35.160> or 00:10:36.140 --> 00:10:36.150 align:start position:0% they have a policy that you think or 00:10:36.150 --> 00:10:38.990 align:start position:0% they have a policy that you think or that's<00:10:36.930> better<00:10:37.170> said<00:10:37.440> by<00:10:37.590> saying<00:10:37.860> they<00:10:38.670> can't 00:10:38.990 --> 00:10:39.000 align:start position:0% that's better said by saying they can't 00:10:39.000 --> 00:10:41.450 align:start position:0% that's better said by saying they can't create<00:10:39.270> a<00:10:39.390> zero<00:10:39.630> knowledge<00:10:39.840> proof<00:10:40.310> unless<00:10:41.310> you 00:10:41.450 --> 00:10:41.460 align:start position:0% create a zero knowledge proof unless you 00:10:41.460 --> 00:10:43.730 align:start position:0% create a zero knowledge proof unless you have<00:10:41.610> some<00:10:41.730> signature<00:10:42.300> so<00:10:42.960> when<00:10:43.170> we<00:10:43.290> when<00:10:43.710> we 00:10:43.730 --> 00:10:43.740 align:start position:0% have some signature so when we when we 00:10:43.740 --> 00:10:45.320 align:start position:0% have some signature so when we when we create<00:10:44.040> the<00:10:44.130> zero<00:10:44.340> food<00:10:44.670> we<00:10:44.880> have<00:10:45.030> like<00:10:45.180> this 00:10:45.320 --> 00:10:45.330 align:start position:0% create the zero food we have like this 00:10:45.330 --> 00:10:48.260 align:start position:0% create the zero food we have like this inclusion<00:10:45.720> point<00:10:46.280> that's<00:10:47.280> you<00:10:48.090> have<00:10:48.210> an 00:10:48.260 --> 00:10:48.270 align:start position:0% inclusion point that's you have an 00:10:48.270 --> 00:10:50.900 align:start position:0% inclusion point that's you have an implicit<00:10:48.480> food<00:10:48.810> that<00:10:49.020> everyone's<00:10:49.910> an 00:10:50.900 --> 00:10:50.910 align:start position:0% implicit food that everyone's an 00:10:50.910 --> 00:10:53.300 align:start position:0% implicit food that everyone's an implicit<00:10:51.390> proof<00:10:51.840> that<00:10:52.410> the<00:10:52.620> signature<00:10:53.010> exists 00:10:53.300 --> 00:10:53.310 align:start position:0% implicit proof that the signature exists 00:10:53.310 --> 00:10:56.330 align:start position:0% implicit proof that the signature exists and<00:10:53.580> that<00:10:53.700> Hoover<00:10:53.940> has<00:10:54.560> so<00:10:55.560> inside<00:10:56.280> the 00:10:56.330 --> 00:10:56.340 align:start position:0% and that Hoover has so inside the 00:10:56.340 --> 00:11:11.030 align:start position:0% and that Hoover has so inside the stomach<00:10:56.550> we<00:10:57.150> do<00:10:58.340> oh<00:11:00.290> that's<00:11:01.290> right<00:11:09.800> -<00:11:10.800> sighs 00:11:11.030 --> 00:11:11.040 align:start position:0% stomach we do oh that's right - sighs 00:11:11.040 --> 00:11:15.890 align:start position:0% stomach we do oh that's right - sighs and<00:11:11.280> shall<00:11:11.580> we<00:11:11.670> say<00:11:12.080> complicated<00:11:14.570> so<00:11:15.570> these 00:11:15.890 --> 00:11:15.900 align:start position:0% and shall we say complicated so these 00:11:15.900 --> 00:11:23.840 align:start position:0% and shall we say complicated so these are<00:11:16.050> the<00:11:16.110> contents 00:11:23.840 --> 00:11:23.850 align:start position:0% 00:11:23.850 --> 00:11:27.480 align:start position:0% okay<00:11:24.850> so<00:11:25.270> did<00:11:25.540> you<00:11:25.660> see<00:11:25.840> here<00:11:26.080> this<00:11:26.230> is<00:11:26.290> our<00:11:26.590> as 00:11:27.480 --> 00:11:27.490 align:start position:0% okay so did you see here this is our as 00:11:27.490 --> 00:11:30.810 align:start position:0% okay so did you see here this is our as our<00:11:27.630> database<00:11:28.630> and<00:11:28.840> something<00:11:29.700> we<00:11:30.700> have<00:11:30.790> a 00:11:30.810 --> 00:11:30.820 align:start position:0% our database and something we have a 00:11:30.820 --> 00:11:32.940 align:start position:0% our database and something we have a virtual<00:11:31.030> business<00:11:31.530> everything<00:11:32.530> that<00:11:32.650> we<00:11:32.740> keep 00:11:32.940 --> 00:11:32.950 align:start position:0% virtual business everything that we keep 00:11:32.950 --> 00:11:35.640 align:start position:0% virtual business everything that we keep on<00:11:33.130> to<00:11:33.340> leave<00:11:34.330> the<00:11:34.510> snag<00:11:34.750> to<00:11:34.930> update<00:11:35.290> this<00:11:35.440> for 00:11:35.640 --> 00:11:35.650 align:start position:0% on to leave the snag to update this for 00:11:35.650 --> 00:11:36.270 align:start position:0% on to leave the snag to update this for commerce 00:11:36.270 --> 00:11:36.280 align:start position:0% commerce 00:11:36.280 --> 00:11:38.370 align:start position:0% commerce no<00:11:36.730> and<00:11:37.510> you<00:11:37.660> see<00:11:37.780> in<00:11:37.870> the<00:11:37.930> bottom<00:11:38.110> of<00:11:38.290> the 00:11:38.370 --> 00:11:38.380 align:start position:0% no and you see in the bottom of the 00:11:38.380 --> 00:11:40.740 align:start position:0% no and you see in the bottom of the chain<00:11:38.650> you<00:11:38.830> see<00:11:38.980> these<00:11:39.100> ABC<00:11:39.970> and<00:11:40.120> D<00:11:40.270> this<00:11:40.690> is 00:11:40.740 --> 00:11:40.750 align:start position:0% chain you see these ABC and D this is 00:11:40.750 --> 00:11:45.960 align:start position:0% chain you see these ABC and D this is like<00:11:41.110> the<00:11:42.810> this<00:11:43.810> is<00:11:44.020> like<00:11:44.050> the<00:11:44.700> compass<00:11:45.700> is<00:11:45.850> a 00:11:45.960 --> 00:11:45.970 align:start position:0% like the this is like the compass is a 00:11:45.970 --> 00:11:48.600 align:start position:0% like the this is like the compass is a separate<00:11:46.270> agency<00:11:46.890> and<00:11:47.890> each<00:11:48.010> amendment<00:11:48.340> has<00:11:48.580> a 00:11:48.600 --> 00:11:48.610 align:start position:0% separate agency and each amendment has a 00:11:48.610 --> 00:11:51.120 align:start position:0% separate agency and each amendment has a fully<00:11:48.850> canceled<00:11:49.240> field<00:11:49.450> with<00:11:49.570> it<00:11:49.750> as<00:11:49.890> well<00:11:50.890> as 00:11:51.120 --> 00:11:51.130 align:start position:0% fully canceled field with it as well as 00:11:51.130 --> 00:11:53.190 align:start position:0% fully canceled field with it as well as about<00:11:51.370> something<00:11:51.820> so<00:11:52.240> bu<00:11:52.630> people<00:11:52.960> to<00:11:53.080> the 00:11:53.190 --> 00:11:53.200 align:start position:0% about something so bu people to the 00:11:53.200 --> 00:11:54.360 align:start position:0% about something so bu people to the hatch<00:11:53.380> of<00:11:53.560> all<00:11:53.710> pieces 00:11:54.360 --> 00:11:54.370 align:start position:0% hatch of all pieces 00:11:54.370 --> 00:12:01.100 align:start position:0% hatch of all pieces yeah<00:11:55.380> it's<00:11:56.380> okay<00:11:58.380> yeah<00:11:59.380> so<00:11:59.800> we<00:11:59.950> use<00:12:00.070> that<00:12:00.100> to 00:12:01.100 --> 00:12:01.110 align:start position:0% yeah it's okay yeah so we use that to 00:12:01.110 --> 00:12:06.570 align:start position:0% yeah it's okay yeah so we use that to ninjas<00:12:03.390> and<00:12:04.390> so<00:12:04.540> this<00:12:04.690> is<00:12:04.900> like<00:12:05.430> you<00:12:06.430> have<00:12:06.550> a 00:12:06.570 --> 00:12:06.580 align:start position:0% ninjas and so this is like you have a 00:12:06.580 --> 00:12:08.670 align:start position:0% ninjas and so this is like you have a list<00:12:06.730> of<00:12:06.880> transactions<00:12:07.420> here<00:12:07.680> these 00:12:08.670 --> 00:12:08.680 align:start position:0% list of transactions here these 00:12:08.680 --> 00:12:12.000 align:start position:0% list of transactions here these transactions<00:12:09.310> in<00:12:10.140> this<00:12:11.140> red<00:12:11.320> box<00:12:11.350> is<00:12:11.800> like 00:12:12.000 --> 00:12:12.010 align:start position:0% transactions in this red box is like 00:12:12.010 --> 00:12:14.880 align:start position:0% transactions in this red box is like what's<00:12:12.730> happening<00:12:13.030> with<00:12:13.150> Israel<00:12:13.510> and<00:12:13.900> here<00:12:14.770> is 00:12:14.880 --> 00:12:14.890 align:start position:0% what's happening with Israel and here is 00:12:14.890 --> 00:12:16.560 align:start position:0% what's happening with Israel and here is what's<00:12:15.100> happening<00:12:15.160> with<00:12:15.520> is<00:12:15.640> my<00:12:15.790> contacts<00:12:16.270> so 00:12:16.560 --> 00:12:16.570 align:start position:0% what's happening with is my contacts so 00:12:16.570 --> 00:12:20.670 align:start position:0% what's happening with is my contacts so we<00:12:16.840> have<00:12:17.050> state<00:12:18.010> one<00:12:18.360> or<00:12:19.360> Marco<00:12:19.720> Rubio<00:12:20.290> comes 00:12:20.670 --> 00:12:20.680 align:start position:0% we have state one or Marco Rubio comes 00:12:20.680 --> 00:12:22.530 align:start position:0% we have state one or Marco Rubio comes in<00:12:20.800> here<00:12:21.010> and<00:12:21.610> then<00:12:21.790> we<00:12:21.910> make<00:12:22.060> approve<00:12:22.330> that 00:12:22.530 --> 00:12:22.540 align:start position:0% in here and then we make approve that 00:12:22.540 --> 00:12:25.110 align:start position:0% in here and then we make approve that updates<00:12:22.930> it<00:12:23.080> to<00:12:23.260> work<00:12:23.470> one<00:12:24.040> yeah<00:12:24.700> so<00:12:24.910> we<00:12:24.970> put 00:12:25.110 --> 00:12:25.120 align:start position:0% updates it to work one yeah so we put 00:12:25.120 --> 00:12:28.260 align:start position:0% updates it to work one yeah so we put the<00:12:25.180> put<00:12:25.330> one<00:12:25.480> chain<00:12:25.690> as<00:12:26.530> well<00:12:26.800> as<00:12:27.070> we<00:12:27.280> yeah<00:12:27.850> so 00:12:28.260 --> 00:12:28.270 align:start position:0% the put one chain as well as we yeah so 00:12:28.270 --> 00:12:30.030 align:start position:0% the put one chain as well as we yeah so we<00:12:28.390> put<00:12:28.900> a<00:12:28.930> bunch<00:12:29.260> a<00:12:29.410> but<00:12:29.620> we<00:12:29.710> have<00:12:29.830> a<00:12:29.860> problem 00:12:30.030 --> 00:12:30.040 align:start position:0% we put a bunch a but we have a problem 00:12:30.040 --> 00:12:34.980 align:start position:0% we put a bunch a but we have a problem is<00:12:30.580> like<00:12:30.760> this<00:12:31.080> ability<00:12:32.080> from<00:12:33.780> so<00:12:34.780> there's 00:12:34.980 --> 00:12:34.990 align:start position:0% is like this ability from so there's 00:12:34.990 --> 00:12:36.690 align:start position:0% is like this ability from so there's this<00:12:35.080> like<00:12:35.290> date<00:12:35.470> availability<00:12:35.860> problem<00:12:36.310> that 00:12:36.690 --> 00:12:36.700 align:start position:0% this like date availability problem that 00:12:36.700 --> 00:12:38.130 align:start position:0% this like date availability problem that someone<00:12:37.060> updates<00:12:37.360> on<00:12:37.480> worker<00:12:37.690> Ruth<00:12:37.870> you're 00:12:38.130 --> 00:12:38.140 align:start position:0% someone updates on worker Ruth you're 00:12:38.140 --> 00:12:39.760 align:start position:0% someone updates on worker Ruth you're not<00:12:38.290> able<00:12:38.410> to 00:12:39.760 --> 00:12:39.770 align:start position:0% not able to 00:12:39.770 --> 00:12:42.710 align:start position:0% not able to so<00:12:40.770> you're<00:12:41.640> not<00:12:41.760> able<00:12:41.910> to<00:12:42.030> sort<00:12:42.300> of<00:12:42.330> update<00:12:42.480> the 00:12:42.710 --> 00:12:42.720 align:start position:0% so you're not able to sort of update the 00:12:42.720 --> 00:12:44.150 align:start position:0% so you're not able to sort of update the system<00:12:43.050> because<00:12:43.320> we<00:12:43.410> want<00:12:43.590> to<00:12:43.620> have<00:12:43.740> multiple 00:12:44.150 --> 00:12:44.160 align:start position:0% system because we want to have multiple 00:12:44.160 --> 00:12:45.680 align:start position:0% system because we want to have multiple people<00:12:44.340> who<00:12:44.640> are<00:12:44.730> able<00:12:44.790> to<00:12:45.000> do<00:12:45.510> say 00:12:45.680 --> 00:12:45.690 align:start position:0% people who are able to do say 00:12:45.690 --> 00:12:47.990 align:start position:0% people who are able to do say transitions<00:12:46.170> so<00:12:46.800> what<00:12:46.950> we<00:12:47.040> do<00:12:47.190> is<00:12:47.400> we<00:12:47.640> also 00:12:47.990 --> 00:12:48.000 align:start position:0% transitions so what we do is we also 00:12:48.000 --> 00:12:51.050 align:start position:0% transitions so what we do is we also reveal<00:12:48.450> at<00:12:48.600> dinner<00:12:48.930> yeah<00:12:49.470> so<00:12:50.130> the<00:12:50.580> dip<00:12:50.820> is 00:12:51.050 --> 00:12:51.060 align:start position:0% reveal at dinner yeah so the dip is 00:12:51.060 --> 00:12:55.850 align:start position:0% reveal at dinner yeah so the dip is basically<00:12:53.450> invited<00:12:54.450> Alice<00:12:54.840> and<00:12:55.110> Deborah<00:12:55.560> and 00:12:55.850 --> 00:12:55.860 align:start position:0% basically invited Alice and Deborah and 00:12:55.860 --> 00:12:57.800 align:start position:0% basically invited Alice and Deborah and ever<00:12:56.040> since<00:12:56.280> we're<00:12:56.550> talking<00:12:56.700> from<00:12:57.060> Alice's 00:12:57.800 --> 00:12:57.810 align:start position:0% ever since we're talking from Alice's 00:12:57.810 --> 00:12:58.100 align:start position:0% ever since we're talking from Alice's ever 00:12:58.100 --> 00:12:58.110 align:start position:0% ever 00:12:58.110 --> 00:13:00.860 align:start position:0% ever so<00:12:58.950> if<00:12:59.100> Alice<00:12:59.400> has<00:12:59.520> a<00:12:59.550> talking<00:12:59.850> to<00:12:59.940> Debra<00:13:00.120> we 00:13:00.860 --> 00:13:00.870 align:start position:0% so if Alice has a talking to Debra we 00:13:00.870 --> 00:13:04.220 align:start position:0% so if Alice has a talking to Debra we the<00:13:01.230> dip<00:13:01.440> is<00:13:01.680> basically<00:13:02.100> the<00:13:02.820> the<00:13:03.060> to<00:13:03.300> address 00:13:04.220 --> 00:13:04.230 align:start position:0% the dip is basically the the to address 00:13:04.230 --> 00:13:06.680 align:start position:0% the dip is basically the the to address the<00:13:04.500> wrong<00:13:04.800> address<00:13:05.040> the<00:13:05.970> progress<00:13:06.420> the<00:13:06.540> to 00:13:06.680 --> 00:13:06.690 align:start position:0% the wrong address the progress the to 00:13:06.690 --> 00:13:10.100 align:start position:0% the wrong address the progress the to address<00:13:06.960> and<00:13:07.230> the<00:13:07.290> amount<00:13:07.790> yeah<00:13:08.790> and<00:13:09.110> and 00:13:10.100 --> 00:13:10.110 align:start position:0% address and the amount yeah and and 00:13:10.110 --> 00:13:11.930 align:start position:0% address and the amount yeah and and that's<00:13:10.260> a<00:13:10.320> lot<00:13:10.440> to<00:13:10.560> reconstruct<00:13:10.980> emotion<00:13:11.370> so 00:13:11.930 --> 00:13:11.940 align:start position:0% that's a lot to reconstruct emotion so 00:13:11.940 --> 00:13:13.850 align:start position:0% that's a lot to reconstruct emotion so it<00:13:12.450> turns<00:13:12.660> out<00:13:12.750> that<00:13:12.810> this<00:13:12.990> is<00:13:13.170> pretty<00:13:13.320> pretty 00:13:13.850 --> 00:13:13.860 align:start position:0% it turns out that this is pretty pretty 00:13:13.860 --> 00:13:15.500 align:start position:0% it turns out that this is pretty pretty compressible<00:13:14.610> because<00:13:14.940> we<00:13:15.060> just<00:13:15.210> use<00:13:15.390> the 00:13:15.500 --> 00:13:15.510 align:start position:0% compressible because we just use the 00:13:15.510 --> 00:13:18.110 align:start position:0% compressible because we just use the indexes<00:13:16.020> in<00:13:16.170> the<00:13:16.230> burger<00:13:16.470> tree<00:13:16.970> so<00:13:17.970> this 00:13:18.110 --> 00:13:18.120 align:start position:0% indexes in the burger tree so this 00:13:18.120 --> 00:13:19.940 align:start position:0% indexes in the burger tree so this becomes<00:13:18.510> very<00:13:18.750> sustained<00:13:19.290> for<00:13:19.560> Brenda<00:13:19.830> on<00:13:19.890> the 00:13:19.940 --> 00:13:19.950 align:start position:0% becomes very sustained for Brenda on the 00:13:19.950 --> 00:13:22.520 align:start position:0% becomes very sustained for Brenda on the bottom<00:13:20.280> so<00:13:21.060> we<00:13:21.180> put<00:13:21.330> a<00:13:21.360> snag<00:13:21.600> on<00:13:21.780> the<00:13:22.020> under 00:13:22.520 --> 00:13:22.530 align:start position:0% bottom so we put a snag on the under 00:13:22.530 --> 00:13:27.780 align:start position:0% bottom so we put a snag on the under like<00:13:22.740> if<00:13:23.370> between<00:13:24.030> the<00:13:24.180> two<00:13:24.540> states 00:13:27.780 --> 00:13:27.790 align:start position:0% 00:13:27.790 --> 00:13:36.490 align:start position:0% [Music] 00:13:36.490 --> 00:13:36.500 align:start position:0% 00:13:36.500 --> 00:13:39.270 align:start position:0% and<00:13:36.950> as<00:13:37.070> professional<00:13:37.670> desert<00:13:38.180> without 00:13:39.270 --> 00:13:39.280 align:start position:0% and as professional desert without 00:13:39.280 --> 00:13:42.610 align:start position:0% and as professional desert without remove<00:13:40.280> the<00:13:40.490> privacy<00:13:41.030> yes<00:13:41.960> this<00:13:42.140> completely 00:13:42.610 --> 00:13:42.620 align:start position:0% remove the privacy yes this completely 00:13:42.620 --> 00:13:44.560 align:start position:0% remove the privacy yes this completely ruins<00:13:42.830> friends<00:13:43.160> yeah<00:13:43.580> so<00:13:43.760> so<00:13:44.030> we<00:13:44.150> use<00:13:44.270> snacks 00:13:44.560 --> 00:13:44.570 align:start position:0% ruins friends yeah so so we use snacks 00:13:44.570 --> 00:13:48.160 align:start position:0% ruins friends yeah so so we use snacks here<00:13:44.750> for<00:13:44.960> there's<00:13:45.080> a<00:13:45.140> sickness<00:13:45.530> enough<00:13:47.170> yeah 00:13:48.160 --> 00:13:48.170 align:start position:0% here for there's a sickness enough yeah 00:13:48.170 --> 00:13:51.640 align:start position:0% here for there's a sickness enough yeah so<00:13:49.040> let<00:13:49.730> me<00:13:49.760> go<00:13:50.030> through<00:13:50.090> like<00:13:50.570> an<00:13:50.720> idea<00:13:51.320> that 00:13:51.640 --> 00:13:51.650 align:start position:0% so let me go through like an idea that 00:13:51.650 --> 00:13:53.920 align:start position:0% so let me go through like an idea that has<00:13:51.830> its<00:13:51.950> work<00:13:52.340> so<00:13:52.370> okay<00:13:53.180> so<00:13:53.210> inside<00:13:53.720> this<00:13:53.810> is 00:13:53.920 --> 00:13:53.930 align:start position:0% has its work so okay so inside this is 00:13:53.930 --> 00:13:55.420 align:start position:0% has its work so okay so inside this is argue<00:13:54.170> that<00:13:54.290> what<00:13:54.590> we<00:13:54.710> do<00:13:54.830> exactly<00:13:55.220> is<00:13:55.400> that 00:13:55.420 --> 00:13:55.430 align:start position:0% argue that what we do exactly is that 00:13:55.430 --> 00:13:57.310 align:start position:0% argue that what we do exactly is that when<00:13:55.700> we<00:13:55.820> seek<00:13:56.000> receive<00:13:56.270> introduction<00:13:56.870> we 00:13:57.310 --> 00:13:57.320 align:start position:0% when we seek receive introduction we 00:13:57.320 --> 00:13:59.290 align:start position:0% when we seek receive introduction we validate<00:13:57.710> the<00:13:57.800> signature<00:13:58.250> and<00:13:58.640> then<00:13:58.760> we<00:13:58.910> prove 00:13:59.290 --> 00:13:59.300 align:start position:0% validate the signature and then we prove 00:13:59.300 --> 00:14:01.990 align:start position:0% validate the signature and then we prove that<00:13:59.330> the<00:13:59.960> public<00:14:00.770> key<00:14:00.890> of<00:14:00.920> that<00:14:01.130> signature<00:14:01.520> is 00:14:01.990 --> 00:14:02.000 align:start position:0% that the public key of that signature is 00:14:02.000 --> 00:14:03.700 align:start position:0% that the public key of that signature is equal<00:14:02.330> to<00:14:02.420> the<00:14:02.510> public<00:14:02.810> key<00:14:02.960> about<00:14:03.260> us<00:14:03.410> asleep 00:14:03.700 --> 00:14:03.710 align:start position:0% equal to the public key about us asleep 00:14:03.710 --> 00:14:05.680 align:start position:0% equal to the public key about us asleep then<00:14:04.430> we<00:14:04.610> help 00:14:05.680 --> 00:14:05.690 align:start position:0% then we help 00:14:05.690 --> 00:14:07.570 align:start position:0% then we help then<00:14:06.320> we<00:14:06.470> prove<00:14:06.710> that<00:14:06.740> Alice<00:14:07.100> asleep<00:14:07.400> within 00:14:07.570 --> 00:14:07.580 align:start position:0% then we prove that Alice asleep within 00:14:07.580 --> 00:14:10.120 align:start position:0% then we prove that Alice asleep within the<00:14:07.790> current<00:14:08.000> vertical<00:14:08.390> tree<00:14:08.620> yeah<00:14:09.620> don't<00:14:10.070> we 00:14:10.120 --> 00:14:10.130 align:start position:0% the current vertical tree yeah don't we 00:14:10.130 --> 00:14:12.670 align:start position:0% the current vertical tree yeah don't we update<00:14:10.700> Alice<00:14:11.000> asleep<00:14:11.330> we<00:14:12.200> use<00:14:12.320> the<00:14:12.500> same 00:14:12.670 --> 00:14:12.680 align:start position:0% update Alice asleep we use the same 00:14:12.680 --> 00:14:14.920 align:start position:0% update Alice asleep we use the same vertical<00:14:13.160> path<00:14:13.370> to<00:14:14.060> include<00:14:14.420> that<00:14:14.570> new<00:14:14.720> leaf 00:14:14.920 --> 00:14:14.930 align:start position:0% vertical path to include that new leaf 00:14:14.930 --> 00:14:17.320 align:start position:0% vertical path to include that new leaf into<00:14:15.230> that<00:14:15.380> to<00:14:16.070> update<00:14:16.430> the<00:14:16.580> vocally 00:14:17.320 --> 00:14:17.330 align:start position:0% into that to update the vocally 00:14:17.330 --> 00:14:19.950 align:start position:0% into that to update the vocally yeah<00:14:17.930> so<00:14:18.440> so<00:14:18.770> what's<00:14:18.980> happening<00:14:19.280> here<00:14:19.580> is<00:14:19.700> is 00:14:19.950 --> 00:14:19.960 align:start position:0% yeah so so what's happening here is is 00:14:19.960 --> 00:14:22.690 align:start position:0% yeah so so what's happening here is is we're<00:14:20.960> changing<00:14:20.990> one<00:14:21.470> leaf<00:14:21.620> in<00:14:21.800> the<00:14:21.890> tree<00:14:22.100> how 00:14:22.690 --> 00:14:22.700 align:start position:0% we're changing one leaf in the tree how 00:14:22.700 --> 00:14:24.130 align:start position:0% we're changing one leaf in the tree how because<00:14:22.940> we<00:14:23.090> use<00:14:23.180> the<00:14:23.300> same<00:14:23.330> work<00:14:23.690> of<00:14:23.810> paths<00:14:23.990> we 00:14:24.130 --> 00:14:24.140 align:start position:0% because we use the same work of paths we 00:14:24.140 --> 00:14:28.920 align:start position:0% because we use the same work of paths we hold<00:14:24.410> all<00:14:24.830> the<00:14:25.220> rest<00:14:25.400> of<00:14:25.550> the<00:14:25.640> tree<00:14:25.820> the<00:14:25.940> same 00:14:28.920 --> 00:14:28.930 align:start position:0% 00:14:28.930 --> 00:14:35.260 align:start position:0% houses<00:14:29.930> leaves<00:14:31.390> by<00:14:32.390> removing<00:14:33.140> the<00:14:33.350> head<00:14:34.270> but 00:14:35.260 --> 00:14:35.270 align:start position:0% houses leaves by removing the head but 00:14:35.270 --> 00:14:38.380 align:start position:0% houses leaves by removing the head but by<00:14:35.450> removing<00:14:35.870> the<00:14:36.610> but<00:14:37.610> we<00:14:37.820> reduce<00:14:38.210> our 00:14:38.380 --> 00:14:38.390 align:start position:0% by removing the but we reduce our 00:14:38.390 --> 00:14:40.120 align:start position:0% by removing the but we reduce our pallets<00:14:38.750> that<00:14:38.780> we<00:14:38.900> don't<00:14:39.080> they<00:14:39.200> we<00:14:39.530> come<00:14:39.920> over 00:14:40.120 --> 00:14:40.130 align:start position:0% pallets that we don't they we come over 00:14:40.130 --> 00:14:42.250 align:start position:0% pallets that we don't they we come over like<00:14:40.250> an<00:14:40.370> intermediate<00:14:40.670> route<00:14:41.120> and<00:14:41.480> then<00:14:41.960> we 00:14:42.250 --> 00:14:42.260 align:start position:0% like an intermediate route and then we 00:14:42.260 --> 00:14:44.230 align:start position:0% like an intermediate route and then we have<00:14:42.560> some<00:14:42.740> money<00:14:43.010> that's<00:14:43.280> we've<00:14:43.790> taken<00:14:44.060> away 00:14:44.230 --> 00:14:44.240 align:start position:0% have some money that's we've taken away 00:14:44.240 --> 00:14:45.340 align:start position:0% have some money that's we've taken away from<00:14:44.360> Alice<00:14:44.690> and<00:14:44.720> you<00:14:44.930> want<00:14:45.080> to<00:14:45.140> give<00:14:45.230> it<00:14:45.320> to 00:14:45.340 --> 00:14:45.350 align:start position:0% from Alice and you want to give it to 00:14:45.350 --> 00:14:47.290 align:start position:0% from Alice and you want to give it to Deborah<00:14:45.590> so<00:14:46.220> we<00:14:46.400> use<00:14:46.550> the<00:14:46.700> signature<00:14:47.090> and<00:14:47.180> we 00:14:47.290 --> 00:14:47.300 align:start position:0% Deborah so we use the signature and we 00:14:47.300 --> 00:14:49.630 align:start position:0% Deborah so we use the signature and we look<00:14:47.480> up<00:14:47.630> the<00:14:47.660> to<00:14:48.470> leave<00:14:48.770> the<00:14:49.010> Invincibles 00:14:49.630 --> 00:14:49.640 align:start position:0% look up the to leave the Invincibles 00:14:49.640 --> 00:14:51.310 align:start position:0% look up the to leave the Invincibles receive<00:14:50.030> it<00:14:50.180> and<00:14:50.600> we<00:14:50.720> proved<00:14:51.020> that<00:14:51.050> that 00:14:51.310 --> 00:14:51.320 align:start position:0% receive it and we proved that that 00:14:51.320 --> 00:14:53.890 align:start position:0% receive it and we proved that that leaveth<00:14:51.650> in<00:14:51.770> the<00:14:51.950> updated<00:14:52.490> Merkle<00:14:52.940> tree<00:14:53.120> and 00:14:53.890 --> 00:14:53.900 align:start position:0% leaveth in the updated Merkle tree and 00:14:53.900 --> 00:14:56.440 align:start position:0% leaveth in the updated Merkle tree and then<00:14:54.110> we<00:14:54.290> hide<00:14:54.710> the<00:14:54.890> money<00:14:55.070> together<00:14:55.280> and<00:14:55.670> then 00:14:56.440 --> 00:14:56.450 align:start position:0% then we hide the money together and then 00:14:56.450 --> 00:14:57.910 align:start position:0% then we hide the money together and then we<00:14:56.570> do<00:14:56.690> another<00:14:56.900> work<00:14:57.110> approve<00:14:57.380> holding<00:14:57.770> the 00:14:57.910 --> 00:14:57.920 align:start position:0% we do another work approve holding the 00:14:57.920 --> 00:15:04.780 align:start position:0% we do another work approve holding the other<00:14:58.340> merkel<00:15:02.470> basically<00:15:03.470> how<00:15:03.710> that<00:15:04.100> works 00:15:04.780 --> 00:15:04.790 align:start position:0% other merkel basically how that works 00:15:04.790 --> 00:15:06.790 align:start position:0% other merkel basically how that works and<00:15:05.720> we<00:15:05.840> can<00:15:05.870> also<00:15:06.080> do<00:15:06.290> this<00:15:06.440> for<00:15:06.620> like<00:15:06.740> a 00:15:06.790 --> 00:15:06.800 align:start position:0% and we can also do this for like a 00:15:06.800 --> 00:15:09.250 align:start position:0% and we can also do this for like a global<00:15:07.610> state<00:15:07.790> or<00:15:07.970> different<00:15:08.450> kind<00:15:08.810> of<00:15:08.930> state 00:15:09.250 --> 00:15:09.260 align:start position:0% global state or different kind of state 00:15:09.260 --> 00:15:10.810 align:start position:0% global state or different kind of state transitions<00:15:09.710> so<00:15:09.920> instead<00:15:10.160> of<00:15:10.310> in<00:15:10.580> the 00:15:10.810 --> 00:15:10.820 align:start position:0% transitions so instead of in the 00:15:10.820 --> 00:15:12.460 align:start position:0% transitions so instead of in the previous<00:15:11.120> example<00:15:11.540> we<00:15:11.600> had<00:15:11.750> like<00:15:11.930> Alice<00:15:12.290> and 00:15:12.460 --> 00:15:12.470 align:start position:0% previous example we had like Alice and 00:15:12.470 --> 00:15:14.530 align:start position:0% previous example we had like Alice and Deborah<00:15:12.920> and<00:15:12.950> both<00:15:13.340> of<00:15:13.370> them<00:15:13.670> had<00:15:13.940> like<00:15:14.120> this 00:15:14.530 --> 00:15:14.540 align:start position:0% Deborah and both of them had like this 00:15:14.540 --> 00:15:17.500 align:start position:0% Deborah and both of them had like this constant<00:15:15.310> they<00:15:16.310> both<00:15:16.790> have<00:15:17.030> like<00:15:17.150> a<00:15:17.210> personal 00:15:17.500 --> 00:15:17.510 align:start position:0% constant they both have like a personal 00:15:17.510 --> 00:15:19.060 align:start position:0% constant they both have like a personal state<00:15:17.930> but<00:15:18.230> there<00:15:18.320> was<00:15:18.410> no<00:15:18.530> any<00:15:18.800> of<00:15:18.890> this 00:15:19.060 --> 00:15:19.070 align:start position:0% state but there was no any of this 00:15:19.070 --> 00:15:20.500 align:start position:0% state but there was no any of this global<00:15:19.400> state<00:15:19.790> so<00:15:20.090> if<00:15:20.150> you<00:15:20.240> want<00:15:20.390> to<00:15:20.450> do 00:15:20.500 --> 00:15:20.510 align:start position:0% global state so if you want to do 00:15:20.510 --> 00:15:21.760 align:start position:0% global state so if you want to do something<00:15:20.690> like<00:15:20.810> you<00:15:20.870> would<00:15:21.050> swap<00:15:21.350> you<00:15:21.620> need 00:15:21.760 --> 00:15:21.770 align:start position:0% something like you would swap you need 00:15:21.770 --> 00:15:23.080 align:start position:0% something like you would swap you need to<00:15:21.830> have<00:15:21.950> a<00:15:21.980> global<00:15:22.220> state<00:15:22.610> that<00:15:22.820> people<00:15:22.940> are 00:15:23.080 --> 00:15:23.090 align:start position:0% to have a global state that people are 00:15:23.090 --> 00:15:24.220 align:start position:0% to have a global state that people are able<00:15:23.180> to<00:15:23.420> update<00:15:23.540> on<00:15:23.840> their<00:15:23.960> certain 00:15:24.220 --> 00:15:24.230 align:start position:0% able to update on their certain 00:15:24.230 --> 00:15:26.650 align:start position:0% able to update on their certain conditions<00:15:24.730> so<00:15:25.730> that's<00:15:25.940> kind<00:15:26.150> of<00:15:26.180> that's 00:15:26.650 --> 00:15:26.660 align:start position:0% conditions so that's kind of that's 00:15:26.660 --> 00:15:28.000 align:start position:0% conditions so that's kind of that's something<00:15:27.020> else<00:15:27.170> that<00:15:27.350> we<00:15:27.440> can<00:15:27.470> do<00:15:27.710> we<00:15:27.860> can 00:15:28.000 --> 00:15:28.010 align:start position:0% something else that we can do we can 00:15:28.010 --> 00:15:28.480 align:start position:0% something else that we can do we can come<00:15:28.190> of<00:15:28.280> this 00:15:28.480 --> 00:15:28.490 align:start position:0% come of this 00:15:28.490 --> 00:15:30.220 align:start position:0% come of this almost<00:15:28.850> data<00:15:29.030> we<00:15:29.270> can<00:15:29.420> kind<00:15:29.630> of<00:15:29.690> store<00:15:29.900> it<00:15:30.080> and 00:15:30.220 --> 00:15:30.230 align:start position:0% almost data we can kind of store it and 00:15:30.230 --> 00:15:35.080 align:start position:0% almost data we can kind of store it and okay<00:15:31.180> so<00:15:32.620> then<00:15:33.620> we<00:15:33.770> can<00:15:33.950> kind<00:15:34.460> of<00:15:34.520> apply<00:15:35.000> these 00:15:35.080 --> 00:15:35.090 align:start position:0% okay so then we can kind of apply these 00:15:35.090 --> 00:15:41.280 align:start position:0% okay so then we can kind of apply these modifiers<00:15:35.600> to<00:15:35.960> other<00:15:36.470> things<00:15:37.690> yep<00:15:38.720> so<00:15:39.020> that's 00:15:41.280 --> 00:15:41.290 align:start position:0% modifiers to other things yep so that's 00:15:41.290 --> 00:15:43.510 align:start position:0% modifiers to other things yep so that's necessary<00:15:42.290> wasn't<00:15:42.590> it<00:15:42.710> yeah<00:15:43.040> I<00:15:43.070> should<00:15:43.430> say 00:15:43.510 --> 00:15:43.520 align:start position:0% necessary wasn't it yeah I should say 00:15:43.520 --> 00:15:45.640 align:start position:0% necessary wasn't it yeah I should say could<00:15:43.700> you<00:15:43.730> say<00:15:43.970> in<00:15:44.270> what<00:15:44.480> the<00:15:44.660> what<00:15:45.230> Dana 00:15:45.640 --> 00:15:45.650 align:start position:0% could you say in what the what Dana 00:15:45.650 --> 00:15:47.530 align:start position:0% could you say in what the what Dana you're<00:15:45.950> putting<00:15:46.220> on<00:15:46.310> Shane<00:15:46.550> fit<00:15:46.790> you 00:15:47.530 --> 00:15:47.540 align:start position:0% you're putting on Shane fit you 00:15:47.540 --> 00:15:50.350 align:start position:0% you're putting on Shane fit you you<00:15:47.990> say<00:15:48.110> between<00:15:48.860> the<00:15:49.100> two<00:15:49.280> yes<00:15:49.850> so<00:15:50.090> it's<00:15:50.240> the 00:15:50.350 --> 00:15:50.360 align:start position:0% you say between the two yes so it's the 00:15:50.360 --> 00:15:51.370 align:start position:0% you say between the two yes so it's the venerable<00:15:50.720> day<00:15:50.840> that<00:15:50.990> you<00:15:51.080> need<00:15:51.230> to 00:15:51.370 --> 00:15:51.380 align:start position:0% venerable day that you need to 00:15:51.380 --> 00:15:53.740 align:start position:0% venerable day that you need to reconstruct<00:15:51.740> the<00:15:52.010> state<00:15:52.220> and<00:15:52.490> for<00:15:53.450> the<00:15:53.480> token 00:15:53.740 --> 00:15:53.750 align:start position:0% reconstruct the state and for the token 00:15:53.750 --> 00:15:56.140 align:start position:0% reconstruct the state and for the token fronts<00:15:54.110> for<00:15:54.200> example<00:15:54.680> that<00:15:55.340> minimal<00:15:55.850> data<00:15:56.000> is 00:15:56.140 --> 00:15:56.150 align:start position:0% fronts for example that minimal data is 00:15:56.150 --> 00:15:58.750 align:start position:0% fronts for example that minimal data is the<00:15:56.270> two<00:15:56.510> from<00:15:57.470> the<00:15:57.800> to<00:15:57.950> address<00:15:58.220> the<00:15:58.430> problem 00:15:58.750 --> 00:15:58.760 align:start position:0% the two from the to address the problem 00:15:58.760 --> 00:16:00.880 align:start position:0% the two from the to address the problem Edison<00:15:59.090> the<00:15:59.180> amount<00:15:59.420> so<00:15:59.870> it's<00:15:59.960> the<00:16:00.050> only<00:16:00.410> ones 00:16:00.880 --> 00:16:00.890 align:start position:0% Edison the amount so it's the only ones 00:16:00.890 --> 00:16:04.030 align:start position:0% Edison the amount so it's the only ones that<00:16:01.070> were<00:16:01.160> touching<00:16:01.460> and<00:16:01.850> new<00:16:02.410> in<00:16:03.410> the<00:16:03.650> new<00:16:03.830> in 00:16:04.030 --> 00:16:04.040 align:start position:0% that were touching and new in the new in 00:16:04.040 --> 00:16:07.630 align:start position:0% that were touching and new in the new in that<00:16:04.220> state<00:16:04.430> transition<00:16:04.880> yes<00:16:05.060> okay<00:16:06.340> yeah<00:16:07.340> but 00:16:07.630 --> 00:16:07.640 align:start position:0% that state transition yes okay yeah but 00:16:07.640 --> 00:16:10.330 align:start position:0% that state transition yes okay yeah but it's<00:16:07.760> every<00:16:08.060> time<00:16:08.210> they<00:16:08.390> were<00:16:08.510> just<00:16:08.980> so<00:16:09.980> for 00:16:10.330 --> 00:16:10.340 align:start position:0% it's every time they were just so for 00:16:10.340 --> 00:16:12.070 align:start position:0% it's every time they were just so for example<00:16:10.730> if<00:16:10.820> I<00:16:10.970> it<00:16:11.030> said<00:16:11.300> to<00:16:11.540> advise 00:16:12.070 --> 00:16:12.080 align:start position:0% example if I it said to advise 00:16:12.080 --> 00:16:16.450 align:start position:0% example if I it said to advise intermediate<00:16:12.680> versions<00:16:13.100> yeah<00:16:15.040> why<00:16:16.040> is<00:16:16.100> the 00:16:16.450 --> 00:16:16.460 align:start position:0% intermediate versions yeah why is the 00:16:16.460 --> 00:16:19.420 align:start position:0% intermediate versions yeah why is the data<00:16:16.880> availability<00:16:17.680> guarantee<00:16:18.680> of<00:16:18.890> peace 00:16:19.420 --> 00:16:19.430 align:start position:0% data availability guarantee of peace 00:16:19.430 --> 00:16:24.880 align:start position:0% data availability guarantee of peace wonder<00:16:19.880> or<00:16:20.390> face-to-face<00:16:23.260> okay<00:16:24.260> so<00:16:24.320> what<00:16:24.800> we 00:16:24.880 --> 00:16:24.890 align:start position:0% wonder or face-to-face okay so what we 00:16:24.890 --> 00:16:28.630 align:start position:0% wonder or face-to-face okay so what we can<00:16:25.070> do<00:16:25.250> in<00:16:25.400> this<00:16:25.550> case<00:16:25.790> is<00:16:26.150> we<00:16:26.540> can<00:16:27.520> saw<00:16:28.520> the 00:16:28.630 --> 00:16:28.640 align:start position:0% can do in this case is we can saw the 00:16:28.640 --> 00:16:30.160 align:start position:0% can do in this case is we can saw the moment<00:16:28.970> we<00:16:29.060> can<00:16:29.210> put<00:16:29.390> all<00:16:29.480> that<00:16:29.630> we<00:16:29.780> have<00:16:29.900> all 00:16:30.160 --> 00:16:30.170 align:start position:0% moment we can put all that we have all 00:16:30.170 --> 00:16:31.480 align:start position:0% moment we can put all that we have all that<00:16:30.260> they<00:16:30.320> don't<00:16:30.560> chain<00:16:30.740> that<00:16:30.860> this<00:16:31.010> is<00:16:31.220> kind 00:16:31.480 --> 00:16:31.490 align:start position:0% that they don't chain that this is kind 00:16:31.490 --> 00:16:33.070 align:start position:0% that they don't chain that this is kind of<00:16:31.520> expensive<00:16:31.820> so<00:16:32.270> what<00:16:32.420> we<00:16:32.510> do<00:16:32.630> is<00:16:32.690> we<00:16:32.810> put<00:16:32.990> it 00:16:33.070 --> 00:16:33.080 align:start position:0% of expensive so what we do is we put it 00:16:33.080 --> 00:16:34.960 align:start position:0% of expensive so what we do is we put it on<00:16:33.170> change<00:16:33.470> these<00:16:34.010> one<00:16:34.310> and<00:16:34.490> as<00:16:34.580> we<00:16:34.700> get<00:16:34.850> to 00:16:34.960 --> 00:16:34.970 align:start position:0% on change these one and as we get to 00:16:34.970 --> 00:16:36.700 align:start position:0% on change these one and as we get to like<00:16:35.120> 500<00:16:35.330> times<00:16:35.720> per<00:16:35.930> second<00:16:36.380> and<00:16:36.530> what<00:16:36.620> we 00:16:36.700 --> 00:16:36.710 align:start position:0% like 500 times per second and what we 00:16:36.710 --> 00:16:39.730 align:start position:0% like 500 times per second and what we have<00:16:36.860> the<00:16:36.980> new<00:16:37.220> state<00:16:37.550> the<00:16:37.760> new<00:16:38.320> hard<00:16:39.320> work<00:16:39.500> you 00:16:39.730 --> 00:16:39.740 align:start position:0% have the new state the new hard work you 00:16:39.740 --> 00:16:41.620 align:start position:0% have the new state the new hard work you will<00:16:39.890> be<00:16:39.920> able<00:16:40.160> to<00:16:40.250> around<00:16:40.760> 2002<00:16:41.240> elections 00:16:41.620 --> 00:16:41.630 align:start position:0% will be able to around 2002 elections 00:16:41.630 --> 00:16:45.190 align:start position:0% will be able to around 2002 elections and<00:16:41.840> or<00:16:42.740> if<00:16:43.100> we<00:16:43.250> had<00:16:43.430> our<00:16:44.210> base<00:16:44.570> worn<00:16:44.900> because 00:16:45.190 --> 00:16:45.200 align:start position:0% and or if we had our base worn because 00:16:45.200 --> 00:16:46.840 align:start position:0% and or if we had our base worn because theoretically<00:16:45.530> what<00:16:46.130> they<00:16:46.310> say<00:16:46.550> on<00:16:46.730> the 00:16:46.840 --> 00:16:46.850 align:start position:0% theoretically what they say on the 00:16:46.850 --> 00:16:49.420 align:start position:0% theoretically what they say on the sheriff<00:16:47.230> and<00:16:48.230> then<00:16:48.530> just<00:16:48.770> look<00:16:48.980> at<00:16:49.160> you<00:16:49.310> know 00:16:49.420 --> 00:16:49.430 align:start position:0% sheriff and then just look at you know 00:16:49.430 --> 00:16:56.539 align:start position:0% sheriff and then just look at you know almost<00:16:50.390> my<00:16:50.510> project 00:16:56.539 --> 00:16:56.549 align:start position:0% 00:16:56.549 --> 00:17:00.659 align:start position:0% publish<00:16:57.839> transfer<00:16:58.839> same<00:16:59.409> time<00:16:59.679> one<00:17:00.399> of<00:17:00.429> them 00:17:00.659 --> 00:17:00.669 align:start position:0% publish transfer same time one of them 00:17:00.669 --> 00:17:03.899 align:start position:0% publish transfer same time one of them will<00:17:00.879> invalidate<00:17:01.119> the<00:17:01.509> other<00:17:01.659> right<00:17:02.339> so<00:17:03.339> in 00:17:03.899 --> 00:17:03.909 align:start position:0% will invalidate the other right so in 00:17:03.909 --> 00:17:05.309 align:start position:0% will invalidate the other right so in this<00:17:04.029> case<00:17:04.299> we<00:17:04.480> have<00:17:04.629> okay<00:17:04.870> so<00:17:04.929> we<00:17:05.079> have<00:17:05.199> like 00:17:05.309 --> 00:17:05.319 align:start position:0% this case we have okay so we have like 00:17:05.319 --> 00:17:08.610 align:start position:0% this case we have okay so we have like two<00:17:05.499> rolls<00:17:06.449> so<00:17:07.449> the<00:17:07.569> question<00:17:08.079> isn't<00:17:08.199> that 00:17:08.610 --> 00:17:08.620 align:start position:0% two rolls so the question isn't that 00:17:08.620 --> 00:17:10.889 align:start position:0% two rolls so the question isn't that means<00:17:08.799> no<00:17:08.919> this<00:17:09.189> is<00:17:09.309> correct<00:17:09.610> what<00:17:10.419> happens<00:17:10.779> if 00:17:10.889 --> 00:17:10.899 align:start position:0% means no this is correct what happens if 00:17:10.899 --> 00:17:12.569 align:start position:0% means no this is correct what happens if two<00:17:10.990> people<00:17:11.319> while<00:17:11.829> there's<00:17:12.039> a<00:17:12.129> transaction 00:17:12.569 --> 00:17:12.579 align:start position:0% two people while there's a transaction 00:17:12.579 --> 00:17:14.579 align:start position:0% two people while there's a transaction at<00:17:12.669> the<00:17:12.730> same<00:17:12.909> time<00:17:13.149> moving<00:17:13.779> some<00:17:14.259> state<00:17:14.499> of 00:17:14.579 --> 00:17:14.589 align:start position:0% at the same time moving some state of 00:17:14.589 --> 00:17:15.019 align:start position:0% at the same time moving some state of conflict 00:17:15.019 --> 00:17:15.029 align:start position:0% conflict 00:17:15.029 --> 00:17:17.579 align:start position:0% conflict okay<00:17:16.029> so<00:17:16.089> inside<00:17:16.720> what<00:17:16.870> we<00:17:17.079> have<00:17:17.199> these<00:17:17.289> kind 00:17:17.579 --> 00:17:17.589 align:start position:0% okay so inside what we have these kind 00:17:17.589 --> 00:17:19.139 align:start position:0% okay so inside what we have these kind of<00:17:17.679> two<00:17:17.769> states<00:17:18.039> we<00:17:18.339> have<00:17:18.370> the<00:17:18.549> users<00:17:18.909> and<00:17:19.089> we 00:17:19.139 --> 00:17:19.149 align:start position:0% of two states we have the users and we 00:17:19.149 --> 00:17:20.759 align:start position:0% of two states we have the users and we have<00:17:19.299> this<00:17:19.389> very<00:17:19.659> high<00:17:19.720> aggregator<00:17:20.199> call<00:17:20.649> them 00:17:20.759 --> 00:17:20.769 align:start position:0% have this very high aggregator call them 00:17:20.769 --> 00:17:23.249 align:start position:0% have this very high aggregator call them the<00:17:20.860> coordinator<00:17:21.399> and<00:17:21.909> coordinator<00:17:22.870> receives 00:17:23.249 --> 00:17:23.259 align:start position:0% the coordinator and coordinator receives 00:17:23.259 --> 00:17:25.230 align:start position:0% the coordinator and coordinator receives a<00:17:23.439> bunch<00:17:23.679> of<00:17:23.769> transactions<00:17:24.279> and<00:17:24.459> they<00:17:24.610> will 00:17:25.230 --> 00:17:25.240 align:start position:0% a bunch of transactions and they will 00:17:25.240 --> 00:17:29.430 align:start position:0% a bunch of transactions and they will send<00:17:25.389> them<00:17:25.569> to<00:17:27.299> another<00:17:28.299> department<00:17:29.049> wasn't 00:17:29.430 --> 00:17:29.440 align:start position:0% send them to another department wasn't 00:17:29.440 --> 00:17:32.700 align:start position:0% send them to another department wasn't better<00:17:29.590> when<00:17:30.340> they<00:17:30.429> put<00:17:30.580> that<00:17:30.700> widget<00:17:31.379> so<00:17:32.379> if 00:17:32.700 --> 00:17:32.710 align:start position:0% better when they put that widget so if 00:17:32.710 --> 00:17:34.139 align:start position:0% better when they put that widget so if it<00:17:32.830> was<00:17:32.950> to<00:17:33.100> these<00:17:33.279> coordinators<00:17:33.789> at<00:17:33.909> the<00:17:33.970> same 00:17:34.139 --> 00:17:34.149 align:start position:0% it was to these coordinators at the same 00:17:34.149 --> 00:17:36.029 align:start position:0% it was to these coordinators at the same time<00:17:34.389> it<00:17:34.570> would<00:17:34.659> be<00:17:34.779> wasting<00:17:35.080> work<00:17:35.230> so<00:17:35.769> we<00:17:35.919> use 00:17:36.029 --> 00:17:36.039 align:start position:0% time it would be wasting work so we use 00:17:36.039 --> 00:17:38.460 align:start position:0% time it would be wasting work so we use a<00:17:36.070> single<00:17:36.340> leader<00:17:36.580> we<00:17:37.090> use<00:17:37.240> a<00:17:37.389> leader<00:17:38.169> that<00:17:38.259> can 00:17:38.460 --> 00:17:38.470 align:start position:0% a single leader we use a leader that can 00:17:38.470 --> 00:17:40.950 align:start position:0% a single leader we use a leader that can manifest<00:17:38.830> assignment<00:17:39.490> one<00:17:40.450> example<00:17:40.720> of<00:17:40.840> what 00:17:40.950 --> 00:17:40.960 align:start position:0% manifest assignment one example of what 00:17:40.960 --> 00:17:42.450 align:start position:0% manifest assignment one example of what we<00:17:41.049> could<00:17:41.200> do<00:17:41.320> is<00:17:41.499> we<00:17:41.529> could<00:17:41.799> do<00:17:42.009> like<00:17:42.399> a 00:17:42.450 --> 00:17:42.460 align:start position:0% we could do is we could do like a 00:17:42.460 --> 00:17:44.220 align:start position:0% we could do is we could do like a mistake<00:17:43.149> and<00:17:43.330> rather<00:17:43.480> things<00:17:43.690> like<00:17:43.869> them<00:17:44.049> I 00:17:44.220 --> 00:17:44.230 align:start position:0% mistake and rather things like them I 00:17:44.230 --> 00:17:46.350 align:start position:0% mistake and rather things like them I mean<00:17:44.769> some<00:17:45.039> other<00:17:45.100> ideas<00:17:45.490> like<00:17:45.909> possibly<00:17:46.240> by 00:17:46.350 --> 00:17:46.360 align:start position:0% mean some other ideas like possibly by 00:17:46.360 --> 00:17:56.999 align:start position:0% mean some other ideas like possibly by the<00:17:46.419> way<00:17:52.919> is<00:17:53.919> it<00:17:54.159> possible<00:17:54.519> to<00:17:55.710> separate<00:17:56.710> the 00:17:56.999 --> 00:17:57.009 align:start position:0% the way is it possible to separate the 00:17:57.009 --> 00:17:59.519 align:start position:0% the way is it possible to separate the logic<00:17:57.730> for<00:17:58.029> the<00:17:58.210> token<00:17:58.690> transfers<00:17:59.169> and<00:17:59.499> the 00:17:59.519 --> 00:17:59.529 align:start position:0% logic for the token transfers and the 00:17:59.529 --> 00:18:03.869 align:start position:0% logic for the token transfers and the logic<00:18:00.039> that<00:18:00.269> verifies<00:18:01.269> the<00:18:02.490> formal<00:18:03.490> proofs<00:18:03.730> of 00:18:03.869 --> 00:18:03.879 align:start position:0% logic that verifies the formal proofs of 00:18:03.879 --> 00:18:10.080 align:start position:0% logic that verifies the formal proofs of the<00:18:04.090> police<00:18:05.730> term<00:18:06.730> sir<00:18:08.009> it's<00:18:09.009> impossible<00:18:09.669> to 00:18:10.080 --> 00:18:10.090 align:start position:0% the police term sir it's impossible to 00:18:10.090 --> 00:18:12.600 align:start position:0% the police term sir it's impossible to move<00:18:10.450> the<00:18:10.990> discipline<00:18:11.710> of<00:18:11.740> our<00:18:11.950> goal<00:18:12.129> proofs 00:18:12.600 --> 00:18:12.610 align:start position:0% move the discipline of our goal proofs 00:18:12.610 --> 00:18:14.129 align:start position:0% move the discipline of our goal proofs undistinguished<00:18:13.389> verifications<00:18:13.990> in 00:18:14.129 --> 00:18:14.139 align:start position:0% undistinguished verifications in 00:18:14.139 --> 00:18:16.049 align:start position:0% undistinguished verifications in separate<00:18:14.940> things 00:18:16.049 --> 00:18:16.059 align:start position:0% separate things 00:18:16.059 --> 00:18:19.499 align:start position:0% separate things well<00:18:16.720> you<00:18:17.470> can<00:18:17.740> like<00:18:18.220> that<00:18:18.429> could<00:18:18.580> be<00:18:18.700> kept<00:18:18.999> may 00:18:19.499 --> 00:18:19.509 align:start position:0% well you can like that could be kept may 00:18:19.509 --> 00:18:22.259 align:start position:0% well you can like that could be kept may be<00:18:19.570> the<00:18:19.929> signature<00:18:20.350> verification<00:18:20.529> is<00:18:21.369> not<00:18:22.119> in 00:18:22.259 --> 00:18:22.269 align:start position:0% be the signature verification is not in 00:18:22.269 --> 00:18:26.009 align:start position:0% be the signature verification is not in the<00:18:22.360> snark<00:18:22.600> circuit<00:18:23.019> and<00:18:23.399> only<00:18:24.399> the<00:18:24.899> verbs<00:18:25.899> are 00:18:26.009 --> 00:18:26.019 align:start position:0% the snark circuit and only the verbs are 00:18:26.019 --> 00:18:28.859 align:start position:0% the snark circuit and only the verbs are not<00:18:26.190> ever<00:18:27.190> find<00:18:27.429> the<00:18:27.610> that<00:18:27.940> the<00:18:28.149> leaves<00:18:28.600> are 00:18:28.859 --> 00:18:28.869 align:start position:0% not ever find the that the leaves are 00:18:28.869 --> 00:18:31.980 align:start position:0% not ever find the that the leaves are you<00:18:29.860> know<00:18:29.980> leaves<00:18:30.220> update<00:18:30.639> the<00:18:31.509> tree<00:18:31.720> grow 00:18:31.980 --> 00:18:31.990 align:start position:0% you know leaves update the tree grow 00:18:31.990 --> 00:18:34.259 align:start position:0% you know leaves update the tree grow okay<00:18:32.950> this<00:18:33.159> is<00:18:33.279> possible<00:18:33.730> but<00:18:33.879> would<00:18:34.090> likely 00:18:34.259 --> 00:18:34.269 align:start position:0% okay this is possible but would likely 00:18:34.269 --> 00:18:36.989 align:start position:0% okay this is possible but would likely have<00:18:34.509> some<00:18:34.629> overhead<00:18:35.080> so<00:18:35.919> for<00:18:36.340> example<00:18:36.759> if<00:18:36.850> you 00:18:36.989 --> 00:18:36.999 align:start position:0% have some overhead so for example if you 00:18:36.999 --> 00:18:38.430 align:start position:0% have some overhead so for example if you did<00:18:37.240> this<00:18:37.450> you<00:18:37.509> would<00:18:37.809> have<00:18:37.840> to<00:18:37.960> come<00:18:38.200> up<00:18:38.289> with 00:18:38.430 --> 00:18:38.440 align:start position:0% did this you would have to come up with 00:18:38.440 --> 00:18:43.710 align:start position:0% did this you would have to come up with a<00:18:38.559> list<00:18:41.129> okay<00:18:42.129> so<00:18:42.220> you<00:18:42.369> verify<00:18:42.789> this<00:18:42.850> signature 00:18:43.710 --> 00:18:43.720 align:start position:0% a list okay so you verify this signature 00:18:43.720 --> 00:18:45.450 align:start position:0% a list okay so you verify this signature somewhere<00:18:44.019> and<00:18:44.440> then<00:18:44.529> you<00:18:44.559> you<00:18:45.070> have<00:18:45.249> to<00:18:45.369> have 00:18:45.450 --> 00:18:45.460 align:start position:0% somewhere and then you you have to have 00:18:45.460 --> 00:18:48.239 align:start position:0% somewhere and then you you have to have a<00:18:45.549> list<00:18:45.759> of<00:18:45.940> the<00:18:46.570> of<00:18:47.379> the<00:18:47.559> correct<00:18:48.039> date 00:18:48.239 --> 00:18:48.249 align:start position:0% a list of the of the correct date 00:18:48.249 --> 00:18:50.070 align:start position:0% a list of the of the correct date renditions<00:18:48.730> and<00:18:48.879> apostle's<00:18:49.480> to<00:18:49.749> the<00:18:49.840> snark 00:18:50.070 --> 00:18:50.080 align:start position:0% renditions and apostle's to the snark 00:18:50.080 --> 00:18:52.019 align:start position:0% renditions and apostle's to the snark well<00:18:50.649> I<00:18:50.679> guess<00:18:50.950> we<00:18:51.070> already<00:18:51.190> do<00:18:51.490> that<00:18:51.519> because 00:18:52.019 --> 00:18:52.029 align:start position:0% well I guess we already do that because 00:18:52.029 --> 00:18:56.159 align:start position:0% well I guess we already do that because we<00:18:52.240> pass<00:18:52.419> the<00:18:52.600> difference<00:18:54.720> yeah<00:18:55.720> so<00:18:55.899> I<00:18:55.929> guess 00:18:56.159 --> 00:18:56.169 align:start position:0% we pass the difference yeah so I guess 00:18:56.169 --> 00:18:57.419 align:start position:0% we pass the difference yeah so I guess you<00:18:56.289> could<00:18:56.409> do<00:18:56.529> that<00:18:56.559> do<00:18:57.039> you<00:18:57.100> have<00:18:57.220> like<00:18:57.399> a 00:18:57.419 --> 00:18:57.429 align:start position:0% you could do that do you have like a 00:18:57.429 --> 00:19:00.180 align:start position:0% you could do that do you have like a case<00:18:58.240> where<00:18:58.480> that<00:18:58.509> would<00:18:58.720> be<00:18:58.809> yeah<00:18:59.740> just<00:19:00.070> in 00:19:00.180 --> 00:19:00.190 align:start position:0% case where that would be yeah just in 00:19:00.190 --> 00:19:03.180 align:start position:0% case where that would be yeah just in case<00:19:00.399> -<00:19:00.879> if<00:19:01.840> you<00:19:01.990> have<00:19:02.080> some<00:19:02.320> complicated<00:19:02.559> you 00:19:03.180 --> 00:19:03.190 align:start position:0% case - if you have some complicated you 00:19:03.190 --> 00:19:07.019 align:start position:0% case - if you have some complicated you know<00:19:03.279> business<00:19:03.700> or<00:19:04.149> whatever<00:19:04.419> for<00:19:04.750> the<00:19:05.639> token 00:19:07.019 --> 00:19:07.029 align:start position:0% know business or whatever for the token 00:19:07.029 --> 00:19:10.740 align:start position:0% know business or whatever for the token transfers<00:19:07.539> then<00:19:09.299> you<00:19:10.299> know<00:19:10.389> you<00:19:10.509> don't<00:19:10.659> have 00:19:10.740 --> 00:19:10.750 align:start position:0% transfers then you know you don't have 00:19:10.750 --> 00:19:12.940 align:start position:0% transfers then you know you don't have to<00:19:10.899> write<00:19:11.080> that<00:19:11.110> in<00:19:11.409> a<00:19:11.470> star<00:19:11.710> circuit 00:19:12.940 --> 00:19:12.950 align:start position:0% to write that in a star circuit 00:19:12.950 --> 00:19:15.450 align:start position:0% to write that in a star circuit instead<00:19:13.250> of<00:19:13.340> just<00:19:13.520> regular<00:19:13.700> contra<00:19:14.390> budget 00:19:15.450 --> 00:19:15.460 align:start position:0% instead of just regular contra budget 00:19:15.460 --> 00:19:17.620 align:start position:0% instead of just regular contra budget also<00:19:16.460> you<00:19:16.550> would<00:19:16.670> violate<00:19:16.850> this<00:19:17.150> image<00:19:17.450> means 00:19:17.620 --> 00:19:17.630 align:start position:0% also you would violate this image means 00:19:17.630 --> 00:19:19.030 align:start position:0% also you would violate this image means that<00:19:17.900> it's<00:19:18.050> not<00:19:18.080> going<00:19:18.200> to<00:19:18.500> have<00:19:18.620> reduced<00:19:18.830> in 00:19:19.030 --> 00:19:19.040 align:start position:0% that it's not going to have reduced in 00:19:19.040 --> 00:19:20.650 align:start position:0% that it's not going to have reduced in transition<00:19:19.460> and<00:19:20.000> you<00:19:20.060> would<00:19:20.240> take<00:19:20.540> advantage 00:19:20.650 --> 00:19:20.660 align:start position:0% transition and you would take advantage 00:19:20.660 --> 00:19:24.580 align:start position:0% transition and you would take advantage of<00:19:21.020> the<00:19:21.230> snark<00:19:21.710> ropes<00:19:21.980> to<00:19:22.220> reduce<00:19:22.580> the<00:19:23.590> the 00:19:24.580 --> 00:19:24.590 align:start position:0% of the snark ropes to reduce the the 00:19:24.590 --> 00:19:26.650 align:start position:0% of the snark ropes to reduce the the data<00:19:24.800> usage<00:19:25.190> and<00:19:25.370> have<00:19:25.790> you<00:19:26.180> know<00:19:26.300> it's<00:19:26.540> like 00:19:26.650 --> 00:19:26.660 align:start position:0% data usage and have you know it's like 00:19:26.660 --> 00:19:30.520 align:start position:0% data usage and have you know it's like an<00:19:26.780> EE<00:19:27.340> stateless<00:19:28.900> you<00:19:29.900> don't<00:19:30.080> have<00:19:30.230> to<00:19:30.320> test 00:19:30.520 --> 00:19:30.530 align:start position:0% an EE stateless you don't have to test 00:19:30.530 --> 00:19:33.400 align:start position:0% an EE stateless you don't have to test you<00:19:31.310> know<00:19:31.400> all<00:19:31.610> this<00:19:31.730> Merkel<00:19:32.120> group<00:19:32.510> data<00:19:32.720> and 00:19:33.400 --> 00:19:33.410 align:start position:0% you know all this Merkel group data and 00:19:33.410 --> 00:19:55.720 align:start position:0% you know all this Merkel group data and stuck<00:19:34.310> you<00:19:34.430> you<00:19:35.000> know<00:19:35.120> press<00:19:36.050> that<00:19:54.580> all<00:19:55.580> right 00:19:55.720 --> 00:19:55.730 align:start position:0% stuck you you know press that all right 00:19:55.730 --> 00:19:57.450 align:start position:0% stuck you you know press that all right next<00:19:56.090> up<00:19:56.300> Carl 00:19:57.450 --> 00:19:57.460 align:start position:0% next up Carl 00:19:57.460 --> 00:20:01.840 align:start position:0% next up Carl well<00:19:58.460> that<00:19:58.730> was<00:19:58.970> a<00:19:59.240> great<00:19:59.660> transition<00:20:00.730> one<00:20:01.730> of 00:20:01.840 --> 00:20:01.850 align:start position:0% well that was a great transition one of 00:20:01.850 --> 00:20:05.230 align:start position:0% well that was a great transition one of the<00:20:02.000> one<00:20:02.330> of<00:20:02.360> the<00:20:03.160> Casey's<00:20:04.160> kind<00:20:04.730> of<00:20:04.790> question 00:20:05.230 --> 00:20:05.240 align:start position:0% the one of the Casey's kind of question 00:20:05.240 --> 00:20:08.140 align:start position:0% the one of the Casey's kind of question can<00:20:05.270> you<00:20:05.930> just<00:20:06.740> use<00:20:06.980> a<00:20:07.010> snark<00:20:07.370> for<00:20:07.700> the<00:20:07.880> Merkel 00:20:08.140 --> 00:20:08.150 align:start position:0% can you just use a snark for the Merkel 00:20:08.150 --> 00:20:10.180 align:start position:0% can you just use a snark for the Merkel proof<00:20:08.330> and<00:20:08.570> then<00:20:09.200> calculate<00:20:09.890> the<00:20:10.040> actual 00:20:10.180 --> 00:20:10.190 align:start position:0% proof and then calculate the actual 00:20:10.190 --> 00:20:13.180 align:start position:0% proof and then calculate the actual state<00:20:10.640> transition<00:20:11.150> somewhere<00:20:11.900> else<00:20:12.080> well<00:20:12.470> in 00:20:13.180 --> 00:20:13.190 align:start position:0% state transition somewhere else well in 00:20:13.190 --> 00:20:15.070 align:start position:0% state transition somewhere else well in fact<00:20:13.370> you<00:20:13.550> can<00:20:13.760> in<00:20:14.030> one<00:20:14.150> of<00:20:14.240> those<00:20:14.360> places<00:20:14.660> is 00:20:15.070 --> 00:20:15.080 align:start position:0% fact you can in one of those places is 00:20:15.080 --> 00:20:17.530 align:start position:0% fact you can in one of those places is with<00:20:15.830> a<00:20:15.860> dispute<00:20:16.340> game<00:20:16.550> okay<00:20:17.090> so<00:20:17.210> I'm<00:20:17.360> going<00:20:17.510> to 00:20:17.530 --> 00:20:17.540 align:start position:0% with a dispute game okay so I'm going to 00:20:17.540 --> 00:20:19.420 align:start position:0% with a dispute game okay so I'm going to talk<00:20:17.690> about<00:20:17.840> optimistic<00:20:18.470> roll-up<00:20:18.770> how<00:20:19.250> many 00:20:19.420 --> 00:20:19.430 align:start position:0% talk about optimistic roll-up how many 00:20:19.430 --> 00:20:22.540 align:start position:0% talk about optimistic roll-up how many people<00:20:19.730> in<00:20:19.970> this<00:20:20.180> heat<00:20:20.510> room<00:20:21.320> have<00:20:22.190> heard 00:20:22.540 --> 00:20:22.550 align:start position:0% people in this heat room have heard 00:20:22.550 --> 00:20:26.290 align:start position:0% people in this heat room have heard about<00:20:22.820> to<00:20:23.090> mr.<00:20:23.330> roll-up<00:20:24.220> okay<00:20:25.250> medium<00:20:25.910> that's 00:20:26.290 --> 00:20:26.300 align:start position:0% about to mr. roll-up okay medium that's 00:20:26.300 --> 00:20:28.210 align:start position:0% about to mr. roll-up okay medium that's pretty<00:20:26.600> good<00:20:26.810> how<00:20:27.230> many<00:20:27.380> people<00:20:27.620> think<00:20:28.040> they 00:20:28.210 --> 00:20:28.220 align:start position:0% pretty good how many people think they 00:20:28.220 --> 00:20:32.680 align:start position:0% pretty good how many people think they understand<00:20:28.880> optimistic<00:20:29.570> rola<00:20:31.300> okay<00:20:32.300> that's<00:20:32.600> a 00:20:32.680 --> 00:20:32.690 align:start position:0% understand optimistic rola okay that's a 00:20:32.690 --> 00:20:34.900 align:start position:0% understand optimistic rola okay that's a lot<00:20:32.870> fewer<00:20:33.080> that's<00:20:33.590> unfortunate<00:20:34.280> but<00:20:34.550> it's 00:20:34.900 --> 00:20:34.910 align:start position:0% lot fewer that's unfortunate but it's 00:20:34.910 --> 00:20:36.670 align:start position:0% lot fewer that's unfortunate but it's support<00:20:35.360> you<00:20:35.450> actually<00:20:35.840> know<00:20:35.960> it's<00:20:36.170> important 00:20:36.670 --> 00:20:36.680 align:start position:0% support you actually know it's important 00:20:36.680 --> 00:20:37.500 align:start position:0% support you actually know it's important that<00:20:36.710> thing<00:20:37.010> because 00:20:37.500 --> 00:20:37.510 align:start position:0% that thing because 00:20:37.510 --> 00:20:44.880 align:start position:0% that thing because this<00:20:37.780> is<00:20:37.929> maximum<00:20:38.590> impact<00:20:43.710> optimistic<00:20:44.710> rola 00:20:44.880 --> 00:20:44.890 align:start position:0% this is maximum impact optimistic rola 00:20:44.890 --> 00:20:48.720 align:start position:0% this is maximum impact optimistic rola is<00:20:45.520> yet<00:20:46.360> another<00:20:46.540> way<00:20:47.320> to<00:20:47.350> scale<00:20:48.070> and<00:20:48.400> hiriam 00:20:48.720 --> 00:20:48.730 align:start position:0% is yet another way to scale and hiriam 00:20:48.730 --> 00:20:50.850 align:start position:0% is yet another way to scale and hiriam it<00:20:48.910> works<00:20:49.210> in<00:20:49.390> youth<00:20:49.570> one<00:20:49.809> it<00:20:50.110> works<00:20:50.260> in<00:20:50.440> two 00:20:50.850 --> 00:20:50.860 align:start position:0% it works in youth one it works in two 00:20:50.860 --> 00:20:53.730 align:start position:0% it works in youth one it works in two phase<00:20:51.100> water<00:20:51.460> it<00:20:51.850> is<00:20:52.299> one<00:20:53.049> one<00:20:53.470> of<00:20:53.590> these 00:20:53.730 --> 00:20:53.740 align:start position:0% phase water it is one one of these 00:20:53.740 --> 00:20:56.460 align:start position:0% phase water it is one one of these schemes<00:20:54.070> where<00:20:54.610> you<00:20:54.820> embed<00:20:55.570> a<00:20:55.900> block<00:20:56.200> chain 00:20:56.460 --> 00:20:56.470 align:start position:0% schemes where you embed a block chain 00:20:56.470 --> 00:20:59.549 align:start position:0% schemes where you embed a block chain inside<00:20:57.010> of<00:20:57.280> etherion<00:20:57.760> right<00:20:58.510> and<00:20:58.780> seek<00:20:59.410> a 00:20:59.549 --> 00:20:59.559 align:start position:0% inside of etherion right and seek a 00:20:59.559 --> 00:21:01.230 align:start position:0% inside of etherion right and seek a rollup<00:20:59.770> the<00:21:00.160> way<00:21:00.280> that<00:21:00.490> the<00:21:00.730> way<00:21:00.850> that<00:21:01.030> Barry 00:21:01.230 --> 00:21:01.240 align:start position:0% rollup the way that the way that Barry 00:21:01.240 --> 00:21:03.030 align:start position:0% rollup the way that the way that Barry was<00:21:01.419> just<00:21:01.660> talking<00:21:02.020> about<00:21:02.200> it<00:21:02.350> you<00:21:02.860> know<00:21:02.980> you 00:21:03.030 --> 00:21:03.040 align:start position:0% was just talking about it you know you 00:21:03.040 --> 00:21:04.919 align:start position:0% was just talking about it you know you can<00:21:03.370> kind<00:21:03.580> of<00:21:03.669> think<00:21:03.730> about<00:21:04.000> think<00:21:04.540> of<00:21:04.630> it<00:21:04.720> as 00:21:04.919 --> 00:21:04.929 align:start position:0% can kind of think about think of it as 00:21:04.929 --> 00:21:06.870 align:start position:0% can kind of think about think of it as here<00:21:05.260> is<00:21:05.440> the<00:21:05.650> etherium<00:21:06.040> lots<00:21:06.250> right<00:21:06.610> because 00:21:06.870 --> 00:21:06.880 align:start position:0% here is the etherium lots right because 00:21:06.880 --> 00:21:09.900 align:start position:0% here is the etherium lots right because here's<00:21:07.570> our<00:21:07.720> etherium<00:21:08.169> and<00:21:09.010> here's<00:21:09.850> our 00:21:09.900 --> 00:21:09.910 align:start position:0% here's our etherium and here's our 00:21:09.910 --> 00:21:13.680 align:start position:0% here's our etherium and here's our blacks<00:21:10.240> and<00:21:10.720> he<00:21:11.260> is<00:21:11.350> not<00:21:11.500> chained<00:21:11.770> and<00:21:12.690> z 00:21:13.680 --> 00:21:13.690 align:start position:0% blacks and he is not chained and z 00:21:13.690 --> 00:21:15.780 align:start position:0% blacks and he is not chained and z Carolla<00:21:14.080> what<00:21:14.470> Barry<00:21:14.710> was<00:21:14.890> talking<00:21:15.250> about<00:21:15.280> is 00:21:15.780 --> 00:21:15.790 align:start position:0% Carolla what Barry was talking about is 00:21:15.790 --> 00:21:17.640 align:start position:0% Carolla what Barry was talking about is kind<00:21:16.090> of<00:21:16.179> putting<00:21:16.390> these<00:21:16.690> like<00:21:16.929> other<00:21:17.260> blocks 00:21:17.640 --> 00:21:17.650 align:start position:0% kind of putting these like other blocks 00:21:17.650 --> 00:21:23.100 align:start position:0% kind of putting these like other blocks these<00:21:18.610> he<00:21:18.820> came<00:21:19.030> up<00:21:19.210> with<00:21:19.240> these<00:21:19.419> ZK<00:21:20.610> are<00:21:22.110> these 00:21:23.100 --> 00:21:23.110 align:start position:0% these he came up with these ZK are these 00:21:23.110 --> 00:21:26.240 align:start position:0% these he came up with these ZK are these ZK<00:21:23.500> roller<00:21:23.710> blocks<00:21:24.179> inside<00:21:25.179> of<00:21:25.600> these<00:21:25.960> guys 00:21:26.240 --> 00:21:26.250 align:start position:0% ZK roller blocks inside of these guys 00:21:26.250 --> 00:21:31.890 align:start position:0% ZK roller blocks inside of these guys right<00:21:27.250> and<00:21:29.820> building<00:21:30.820> up<00:21:31.000> its<00:21:31.330> own<00:21:31.600> chain 00:21:31.890 --> 00:21:31.900 align:start position:0% right and building up its own chain 00:21:31.900 --> 00:21:33.720 align:start position:0% right and building up its own chain which<00:21:32.169> has<00:21:32.380> its<00:21:32.620> own<00:21:32.740> properties<00:21:33.250> right<00:21:33.520> and 00:21:33.720 --> 00:21:33.730 align:start position:0% which has its own properties right and 00:21:33.730 --> 00:21:36.240 align:start position:0% which has its own properties right and so<00:21:33.880> it<00:21:34.000> turns<00:21:34.210> out<00:21:34.390> like<00:21:34.570> doing<00:21:35.380> this<00:21:35.650> can 00:21:36.240 --> 00:21:36.250 align:start position:0% so it turns out like doing this can 00:21:36.250 --> 00:21:38.640 align:start position:0% so it turns out like doing this can actually<00:21:36.580> be<00:21:36.730> more<00:21:37.450> efficient<00:21:37.960> and<00:21:38.140> that<00:21:38.440> is 00:21:38.640 --> 00:21:38.650 align:start position:0% actually be more efficient and that is 00:21:38.650 --> 00:21:41.940 align:start position:0% actually be more efficient and that is because<00:21:39.070> of<00:21:39.730> one<00:21:40.030> very<00:21:40.270> very<00:21:40.900> cool<00:21:41.350> thing<00:21:41.710> and 00:21:41.940 --> 00:21:41.950 align:start position:0% because of one very very cool thing and 00:21:41.950 --> 00:21:45.419 align:start position:0% because of one very very cool thing and that<00:21:42.130> is<00:21:42.280> that<00:21:42.520> the<00:21:43.650> commutation<00:21:44.650> is<00:21:44.890> not 00:21:45.419 --> 00:21:45.429 align:start position:0% that is that the commutation is not 00:21:45.429 --> 00:21:47.549 align:start position:0% that is that the commutation is not expanding<00:21:45.970> with<00:21:46.120> Morris<00:21:46.450> Moore's<00:21:46.840> Law<00:21:47.140> I 00:21:47.549 --> 00:21:47.559 align:start position:0% expanding with Morris Moore's Law I 00:21:47.559 --> 00:21:50.610 align:start position:0% expanding with Morris Moore's Law I really<00:21:48.040> like<00:21:48.220> this<00:21:48.400> but<00:21:48.970> bandwidth<00:21:49.660> is<00:21:50.020> so<00:21:50.530> it 00:21:50.610 --> 00:21:50.620 align:start position:0% really like this but bandwidth is so it 00:21:50.620 --> 00:21:52.620 align:start position:0% really like this but bandwidth is so it turns<00:21:50.799> out<00:21:50.919> that<00:21:50.980> data<00:21:51.400> availability<00:21:52.030> is<00:21:52.419> much 00:21:52.620 --> 00:21:52.630 align:start position:0% turns out that data availability is much 00:21:52.630 --> 00:21:55.789 align:start position:0% turns out that data availability is much cheaper<00:21:52.960> than<00:21:53.280> and<00:21:54.280> much<00:21:54.460> more<00:21:54.640> scalable<00:21:54.910> than 00:21:55.789 --> 00:21:55.799 align:start position:0% cheaper than and much more scalable than 00:21:55.799 --> 00:21:59.010 align:start position:0% cheaper than and much more scalable than computation<00:21:56.799> so<00:21:57.790> what<00:21:57.940> we're<00:21:58.090> doing<00:21:58.120> is<00:21:58.570> we're 00:21:59.010 --> 00:21:59.020 align:start position:0% computation so what we're doing is we're 00:21:59.020 --> 00:22:00.720 align:start position:0% computation so what we're doing is we're like<00:21:59.290> separating<00:21:59.950> the<00:22:00.190> kind<00:22:00.669> of 00:22:00.720 --> 00:22:00.730 align:start position:0% like separating the kind of 00:22:00.730 --> 00:22:04.409 align:start position:0% like separating the kind of communication<00:22:01.540> message<00:22:01.990> passing<00:22:02.970> logic<00:22:03.970> from 00:22:04.409 --> 00:22:04.419 align:start position:0% communication message passing logic from 00:22:04.419 --> 00:22:07.020 align:start position:0% communication message passing logic from the<00:22:04.480> actual<00:22:05.110> hard<00:22:05.410> like<00:22:05.790> computation<00:22:06.790> that 00:22:07.020 --> 00:22:07.030 align:start position:0% the actual hard like computation that 00:22:07.030 --> 00:22:09.360 align:start position:0% the actual hard like computation that all<00:22:07.210> of<00:22:07.360> the<00:22:07.480> nodes<00:22:07.690> are<00:22:07.900> doing<00:22:08.200> and<00:22:08.410> so<00:22:08.890> this 00:22:09.360 --> 00:22:09.370 align:start position:0% all of the nodes are doing and so this 00:22:09.370 --> 00:22:10.860 align:start position:0% all of the nodes are doing and so this is<00:22:09.520> he<00:22:09.640> can<00:22:09.850> roll<00:22:10.000> up<00:22:10.059> ZK<00:22:10.450> rolled<00:22:10.690> your 00:22:10.860 --> 00:22:10.870 align:start position:0% is he can roll up ZK rolled your 00:22:10.870 --> 00:22:12.270 align:start position:0% is he can roll up ZK rolled your building<00:22:11.169> up<00:22:11.260> this<00:22:11.410> chain<00:22:11.650> inside<00:22:12.040> of<00:22:12.160> this 00:22:12.270 --> 00:22:12.280 align:start position:0% building up this chain inside of this 00:22:12.280 --> 00:22:14.460 align:start position:0% building up this chain inside of this other<00:22:12.490> chain<00:22:12.790> and<00:22:13.059> it's<00:22:13.390> really<00:22:13.750> good<00:22:13.960> because 00:22:14.460 --> 00:22:14.470 align:start position:0% other chain and it's really good because 00:22:14.470 --> 00:22:17.520 align:start position:0% other chain and it's really good because you<00:22:15.220> can<00:22:15.429> prove<00:22:15.760> upfront<00:22:16.360> succinctly<00:22:17.230> with 00:22:17.520 --> 00:22:17.530 align:start position:0% you can prove upfront succinctly with 00:22:17.530 --> 00:22:19.890 align:start position:0% you can prove upfront succinctly with zero<00:22:17.740> knowledge<00:22:17.890> groups<00:22:18.309> that<00:22:18.910> each<00:22:19.419> one<00:22:19.780> of 00:22:19.890 --> 00:22:19.900 align:start position:0% zero knowledge groups that each one of 00:22:19.900 --> 00:22:21.750 align:start position:0% zero knowledge groups that each one of these<00:22:20.020> you<00:22:20.530> know<00:22:20.650> state<00:22:20.950> transitions<00:22:21.549> each 00:22:21.750 --> 00:22:21.760 align:start position:0% these you know state transitions each 00:22:21.760 --> 00:22:23.640 align:start position:0% these you know state transitions each one<00:22:22.000> of<00:22:22.090> these<00:22:22.210> commitments<00:22:22.600> are<00:22:22.990> correct 00:22:23.640 --> 00:22:23.650 align:start position:0% one of these commitments are correct 00:22:23.650 --> 00:22:26.580 align:start position:0% one of these commitments are correct that<00:22:24.010> is<00:22:24.700> a<00:22:24.880> very<00:22:25.600> very<00:22:25.870> nice<00:22:26.110> property 00:22:26.580 --> 00:22:26.590 align:start position:0% that is a very very nice property 00:22:26.590 --> 00:22:28.320 align:start position:0% that is a very very nice property however<00:22:27.340> you<00:22:27.580> don't<00:22:27.730> get<00:22:27.910> it<00:22:28.059> for<00:22:28.179> free 00:22:28.320 --> 00:22:28.330 align:start position:0% however you don't get it for free 00:22:28.330 --> 00:22:30.210 align:start position:0% however you don't get it for free because<00:22:28.990> zero-knowledge<00:22:29.590> proofs<00:22:30.010> are 00:22:30.210 --> 00:22:30.220 align:start position:0% because zero-knowledge proofs are 00:22:30.220 --> 00:22:31.740 align:start position:0% because zero-knowledge proofs are currently<00:22:30.790> and<00:22:31.090> this<00:22:31.210> doesn't 00:22:31.740 --> 00:22:31.750 align:start position:0% currently and this doesn't 00:22:31.750 --> 00:22:33.750 align:start position:0% currently and this doesn't this<00:22:32.020> may<00:22:32.200> not<00:22:32.380> be<00:22:32.440> the<00:22:32.650> case<00:22:32.770> forever<00:22:33.039> but<00:22:33.580> for 00:22:33.750 --> 00:22:33.760 align:start position:0% this may not be the case forever but for 00:22:33.760 --> 00:22:35.909 align:start position:0% this may not be the case forever but for the<00:22:33.909> next<00:22:34.150> you<00:22:34.270> know<00:22:34.330> five<00:22:34.570> years<00:22:34.929> or<00:22:35.110> so<00:22:35.289> we're 00:22:35.909 --> 00:22:35.919 align:start position:0% the next you know five years or so we're 00:22:35.919 --> 00:22:38.419 align:start position:0% the next you know five years or so we're not<00:22:36.280> going<00:22:36.610> to<00:22:36.730> see<00:22:36.940> easy<00:22:37.299> to<00:22:38.020> build 00:22:38.419 --> 00:22:38.429 align:start position:0% not going to see easy to build 00:22:38.429 --> 00:22:40.460 align:start position:0% not going to see easy to build general-purpose<00:22:39.429> their<00:22:39.820> knowledge<00:22:40.150> purse 00:22:40.460 --> 00:22:40.470 align:start position:0% general-purpose their knowledge purse 00:22:40.470 --> 00:22:44.250 align:start position:0% general-purpose their knowledge purse but<00:22:41.470> we<00:22:41.620> can<00:22:41.770> still<00:22:42.159> use<00:22:42.580> the<00:22:42.850> roll<00:22:43.390> up<00:22:43.630> scheme 00:22:44.250 --> 00:22:44.260 align:start position:0% but we can still use the roll up scheme 00:22:44.260 --> 00:22:47.250 align:start position:0% but we can still use the roll up scheme but<00:22:44.919> we<00:22:45.100> can<00:22:45.250> use<00:22:45.429> an<00:22:45.730> optimistic<00:22:46.390> scheme 00:22:47.250 --> 00:22:47.260 align:start position:0% but we can use an optimistic scheme 00:22:47.260 --> 00:22:49.560 align:start position:0% but we can use an optimistic scheme instead<00:22:47.679> so<00:22:48.370> optimistic<00:22:49.030> roll<00:22:49.210> up<00:22:49.330> here's 00:22:49.560 --> 00:22:49.570 align:start position:0% instead so optimistic roll up here's 00:22:49.570 --> 00:22:52.020 align:start position:0% instead so optimistic roll up here's what<00:22:49.780> we<00:22:49.900> do<00:22:50.049> we<00:22:50.950> say<00:22:51.130> okay<00:22:51.460> we're<00:22:51.640> gonna<00:22:51.760> put 00:22:52.020 --> 00:22:52.030 align:start position:0% what we do we say okay we're gonna put 00:22:52.030 --> 00:22:54.600 align:start position:0% what we do we say okay we're gonna put blocks<00:22:52.299> you<00:22:53.200> know<00:22:53.320> aetherium<00:22:53.950> style<00:22:54.280> blocks 00:22:54.600 --> 00:22:54.610 align:start position:0% blocks you know aetherium style blocks 00:22:54.610 --> 00:22:56.909 align:start position:0% blocks you know aetherium style blocks inside<00:22:55.150> of<00:22:55.299> aetherium<00:22:55.720> and<00:22:55.960> we're<00:22:56.650> going<00:22:56.890> to 00:22:56.909 --> 00:22:56.919 align:start position:0% inside of aetherium and we're going to 00:22:56.919 --> 00:22:58.950 align:start position:0% inside of aetherium and we're going to commit<00:22:57.429> them<00:22:57.640> but<00:22:58.150> we're<00:22:58.270> not<00:22:58.570> going<00:22:58.840> to 00:22:58.950 --> 00:22:58.960 align:start position:0% commit them but we're not going to 00:22:58.960 --> 00:23:00.480 align:start position:0% commit them but we're not going to validate<00:22:59.470> them<00:22:59.679> so<00:22:59.860> we're<00:23:00.010> going<00:23:00.100> to<00:23:00.190> commit 00:23:00.480 --> 00:23:00.490 align:start position:0% validate them so we're going to commit 00:23:00.490 --> 00:23:02.789 align:start position:0% validate them so we're going to commit all<00:23:00.640> of<00:23:00.820> the<00:23:00.909> transaction<00:23:01.570> data<00:23:01.840> we're<00:23:02.650> going 00:23:02.789 --> 00:23:02.799 align:start position:0% all of the transaction data we're going 00:23:02.799 --> 00:23:04.980 align:start position:0% all of the transaction data we're going to<00:23:02.860> commit<00:23:03.250> you<00:23:03.460> know<00:23:03.580> state<00:23:04.179> routes<00:23:04.480> you<00:23:04.870> know 00:23:04.980 --> 00:23:04.990 align:start position:0% to commit you know state routes you know 00:23:04.990 --> 00:23:06.120 align:start position:0% to commit you know state routes you know it's<00:23:05.110> okay<00:23:05.289> if<00:23:05.409> you<00:23:05.470> don't<00:23:05.590> know<00:23:05.740> what<00:23:05.830> a<00:23:05.919> savor 00:23:06.120 --> 00:23:06.130 align:start position:0% it's okay if you don't know what a savor 00:23:06.130 --> 00:23:07.620 align:start position:0% it's okay if you don't know what a savor it<00:23:06.220> is<00:23:06.340> but<00:23:06.520> you<00:23:06.970> know<00:23:07.000> committing 00:23:07.620 --> 00:23:07.630 align:start position:0% it is but you know committing 00:23:07.630 --> 00:23:09.779 align:start position:0% it is but you know committing transactions<00:23:08.289> state<00:23:08.620> routes<00:23:08.950> all<00:23:09.370> the 00:23:09.779 --> 00:23:09.789 align:start position:0% transactions state routes all the 00:23:09.789 --> 00:23:11.730 align:start position:0% transactions state routes all the information<00:23:10.299> you<00:23:10.450> need<00:23:10.630> to<00:23:10.960> compute<00:23:11.590> the 00:23:11.730 --> 00:23:11.740 align:start position:0% information you need to compute the 00:23:11.740 --> 00:23:14.330 align:start position:0% information you need to compute the block<00:23:11.980> you're<00:23:12.370> committing<00:23:12.850> it<00:23:12.970> right<00:23:13.690> and 00:23:14.330 --> 00:23:14.340 align:start position:0% block you're committing it right and 00:23:14.340 --> 00:23:17.399 align:start position:0% block you're committing it right and you're<00:23:15.340> not<00:23:15.549> computing<00:23:16.150> it<00:23:16.299> that's<00:23:17.080> a<00:23:17.200> very 00:23:17.399 --> 00:23:17.409 align:start position:0% you're not computing it that's a very 00:23:17.409 --> 00:23:18.840 align:start position:0% you're not computing it that's a very that's<00:23:17.740> kind<00:23:17.950> of<00:23:17.980> a<00:23:18.100> strange<00:23:18.610> thing<00:23:18.669> to 00:23:18.840 --> 00:23:18.850 align:start position:0% that's kind of a strange thing to 00:23:18.850 --> 00:23:21.090 align:start position:0% that's kind of a strange thing to believe<00:23:19.090> the<00:23:19.419> consensus<00:23:20.110> forming<00:23:20.500> nodes<00:23:20.740> of<00:23:21.010> a 00:23:21.090 --> 00:23:21.100 align:start position:0% believe the consensus forming nodes of a 00:23:21.100 --> 00:23:23.970 align:start position:0% believe the consensus forming nodes of a theorem<00:23:21.400> are<00:23:21.520> not<00:23:21.730> computing<00:23:22.240> it<00:23:22.360> but<00:23:23.080> an<00:23:23.380> off 00:23:23.970 --> 00:23:23.980 align:start position:0% theorem are not computing it but an off 00:23:23.980 --> 00:23:26.310 align:start position:0% theorem are not computing it but an off chain<00:23:24.400> that's<00:23:24.640> an<00:23:24.760> option<00:23:25.270> user<00:23:25.539> as<00:23:25.990> a<00:23:26.020> you 00:23:26.310 --> 00:23:26.320 align:start position:0% chain that's an option user as a you 00:23:26.320 --> 00:23:28.470 align:start position:0% chain that's an option user as a you know<00:23:26.440> a<00:23:26.470> company<00:23:26.799> as<00:23:27.250> someone<00:23:27.669> you<00:23:27.880> can 00:23:28.470 --> 00:23:28.480 align:start position:0% know a company as someone you can 00:23:28.480 --> 00:23:30.750 align:start position:0% know a company as someone you can compute<00:23:28.900> it<00:23:29.020> and<00:23:29.169> check<00:23:29.770> locally<00:23:30.280> whether<00:23:30.580> or 00:23:30.750 --> 00:23:30.760 align:start position:0% compute it and check locally whether or 00:23:30.760 --> 00:23:32.909 align:start position:0% compute it and check locally whether or not<00:23:30.940> those<00:23:31.419> state<00:23:31.809> routes<00:23:32.049> that<00:23:32.559> this 00:23:32.909 --> 00:23:32.919 align:start position:0% not those state routes that this 00:23:32.919 --> 00:23:35.340 align:start position:0% not those state routes that this computation<00:23:33.490> was<00:23:33.850> done<00:23:34.090> correctly<00:23:34.350> but 00:23:35.340 --> 00:23:35.350 align:start position:0% computation was done correctly but 00:23:35.350 --> 00:23:37.200 align:start position:0% computation was done correctly but because<00:23:35.799> we<00:23:36.130> are<00:23:36.250> doing<00:23:36.429> this<00:23:36.700> thing<00:23:37.030> where 00:23:37.200 --> 00:23:37.210 align:start position:0% because we are doing this thing where 00:23:37.210 --> 00:23:39.149 align:start position:0% because we are doing this thing where we're<00:23:37.390> not<00:23:37.659> computing<00:23:38.260> it<00:23:38.350> upfront<00:23:38.590> it's 00:23:39.149 --> 00:23:39.159 align:start position:0% we're not computing it upfront it's 00:23:39.159 --> 00:23:42.510 align:start position:0% we're not computing it upfront it's possible<00:23:40.080> that<00:23:41.080> something<00:23:41.530> invalid<00:23:42.280> gets 00:23:42.510 --> 00:23:42.520 align:start position:0% possible that something invalid gets 00:23:42.520 --> 00:23:45.390 align:start position:0% possible that something invalid gets through<00:23:42.820> that's<00:23:43.780> a<00:23:43.929> real<00:23:44.110> problem<00:23:44.650> but<00:23:45.220> it's 00:23:45.390 --> 00:23:45.400 align:start position:0% through that's a real problem but it's 00:23:45.400 --> 00:23:48.480 align:start position:0% through that's a real problem but it's not<00:23:46.000> the<00:23:46.150> worst<00:23:46.299> problem<00:23:46.600> because<00:23:47.309> anyone<00:23:48.309> who 00:23:48.480 --> 00:23:48.490 align:start position:0% not the worst problem because anyone who 00:23:48.490 --> 00:23:50.760 align:start position:0% not the worst problem because anyone who computes<00:23:48.940> this<00:23:49.150> can<00:23:49.750> prove<00:23:50.080> immediately 00:23:50.760 --> 00:23:50.770 align:start position:0% computes this can prove immediately 00:23:50.770 --> 00:23:52.799 align:start position:0% computes this can prove immediately without<00:23:51.250> a<00:23:51.280> single<00:23:51.880> you<00:23:52.299> know<00:23:52.419> it's<00:23:52.539> not<00:23:52.690> an 00:23:52.799 --> 00:23:52.809 align:start position:0% without a single you know it's not an 00:23:52.809 --> 00:23:55.020 align:start position:0% without a single you know it's not an interactive<00:23:53.440> protocol<00:23:53.919> it's<00:23:54.159> just<00:23:54.370> going<00:23:54.850> to 00:23:55.020 --> 00:23:55.030 align:start position:0% interactive protocol it's just going to 00:23:55.030 --> 00:23:57.409 align:start position:0% interactive protocol it's just going to the<00:23:55.150> main<00:23:55.299> chain<00:23:55.539> say<00:23:55.870> this<00:23:56.440> is<00:23:56.650> wrong<00:23:56.919> and 00:23:57.409 --> 00:23:57.419 align:start position:0% the main chain say this is wrong and 00:23:57.419 --> 00:24:00.240 align:start position:0% the main chain say this is wrong and then<00:23:58.419> what<00:23:58.809> we<00:23:58.929> can<00:23:59.049> do<00:23:59.169> is<00:23:59.260> we<00:23:59.380> can<00:23:59.500> say<00:23:59.710> okay 00:24:00.240 --> 00:24:00.250 align:start position:0% then what we can do is we can say okay 00:24:00.250 --> 00:24:03.029 align:start position:0% then what we can do is we can say okay we<00:24:00.280> committed<00:24:01.000> this<00:24:01.150> block<00:24:01.450> then<00:24:02.320> in<00:24:02.710> the<00:24:02.860> next 00:24:03.029 --> 00:24:03.039 align:start position:0% we committed this block then in the next 00:24:03.039 --> 00:24:06.810 align:start position:0% we committed this block then in the next block<00:24:03.460> right<00:24:04.559> this<00:24:05.559> is<00:24:05.770> maybe<00:24:06.070> maybe<00:24:06.549> a<00:24:06.640> little 00:24:06.810 --> 00:24:06.820 align:start position:0% block right this is maybe maybe a little 00:24:06.820 --> 00:24:09.570 align:start position:0% block right this is maybe maybe a little more<00:24:07.030> clear<00:24:07.330> public<00:24:07.870> in<00:24:08.049> this<00:24:08.650> block<00:24:08.950> so<00:24:09.370> here 00:24:09.570 --> 00:24:09.580 align:start position:0% more clear public in this block so here 00:24:09.580 --> 00:24:11.250 align:start position:0% more clear public in this block so here we<00:24:09.730> committed<00:24:10.179> this<00:24:10.360> block<00:24:10.600> right<00:24:10.780> here 00:24:11.250 --> 00:24:11.260 align:start position:0% we committed this block right here 00:24:11.260 --> 00:24:13.710 align:start position:0% we committed this block right here Boop<00:24:11.710> and<00:24:11.890> then<00:24:12.580> in<00:24:12.730> this<00:24:12.850> one<00:24:12.909> we're<00:24:13.299> like<00:24:13.510> oh 00:24:13.710 --> 00:24:13.720 align:start position:0% Boop and then in this one we're like oh 00:24:13.720 --> 00:24:18.419 align:start position:0% Boop and then in this one we're like oh there's<00:24:14.380> some<00:24:14.650> fraud<00:24:15.059> and<00:24:16.950> so<00:24:17.950> we<00:24:18.070> raise<00:24:18.280> the 00:24:18.419 --> 00:24:18.429 align:start position:0% there's some fraud and so we raise the 00:24:18.429 --> 00:24:21.510 align:start position:0% there's some fraud and so we raise the red<00:24:18.580> flag<00:24:18.610> and<00:24:19.289> we<00:24:20.289> delete<00:24:20.650> this<00:24:20.860> block<00:24:21.070> and 00:24:21.510 --> 00:24:21.520 align:start position:0% red flag and we delete this block and 00:24:21.520 --> 00:24:25.230 align:start position:0% red flag and we delete this block and then<00:24:22.120> in<00:24:22.299> the<00:24:22.419> next<00:24:22.539> block<00:24:23.220> we<00:24:24.220> build<00:24:24.490> another 00:24:25.230 --> 00:24:25.240 align:start position:0% then in the next block we build another 00:24:25.240 --> 00:24:27.390 align:start position:0% then in the next block we build another block<00:24:25.539> on<00:24:25.929> our<00:24:26.169> chain<00:24:26.409> starting<00:24:27.070> from<00:24:27.250> the 00:24:27.390 --> 00:24:27.400 align:start position:0% block on our chain starting from the 00:24:27.400 --> 00:24:30.419 align:start position:0% block on our chain starting from the last<00:24:27.640> value<00:24:27.970> block<00:24:28.770> and<00:24:29.770> it<00:24:29.919> turns<00:24:30.130> out 00:24:30.419 --> 00:24:30.429 align:start position:0% last value block and it turns out 00:24:30.429 --> 00:24:32.640 align:start position:0% last value block and it turns out they're<00:24:30.970> doing<00:24:31.270> this<00:24:31.419> very<00:24:31.720> like<00:24:32.020> relatively 00:24:32.640 --> 00:24:32.650 align:start position:0% they're doing this very like relatively 00:24:32.650 --> 00:24:35.220 align:start position:0% they're doing this very like relatively simple<00:24:32.980> scheme<00:24:33.460> it<00:24:33.610> we<00:24:34.210> actually<00:24:34.570> get<00:24:34.750> pretty 00:24:35.220 --> 00:24:35.230 align:start position:0% simple scheme it we actually get pretty 00:24:35.230 --> 00:24:37.830 align:start position:0% simple scheme it we actually get pretty significant<00:24:36.039> scaling<00:24:36.490> benefit<00:24:37.270> so<00:24:37.450> the<00:24:37.630> the 00:24:37.830 --> 00:24:37.840 align:start position:0% significant scaling benefit so the the 00:24:37.840 --> 00:24:40.289 align:start position:0% significant scaling benefit so the the scale<00:24:38.080> that<00:24:38.380> Barry<00:24:38.620> was<00:24:38.799> talking<00:24:39.190> about<00:24:39.299> we 00:24:40.289 --> 00:24:40.299 align:start position:0% scale that Barry was talking about we 00:24:40.299 --> 00:24:42.259 align:start position:0% scale that Barry was talking about we get<00:24:40.510> that<00:24:40.690> as<00:24:40.840> well<00:24:40.870> in<00:24:41.380> Optima 00:24:42.259 --> 00:24:42.269 align:start position:0% get that as well in Optima 00:24:42.269 --> 00:24:45.139 align:start position:0% get that as well in Optima Rolla<00:24:42.629> and<00:24:42.959> the<00:24:43.349> benefit<00:24:43.830> is<00:24:44.039> we<00:24:44.729> get<00:24:44.909> that 00:24:45.139 --> 00:24:45.149 align:start position:0% Rolla and the benefit is we get that 00:24:45.149 --> 00:24:47.899 align:start position:0% Rolla and the benefit is we get that with<00:24:45.599> general-purpose<00:24:46.379> computation<00:24:46.889> in<00:24:47.580> that 00:24:47.899 --> 00:24:47.909 align:start position:0% with general-purpose computation in that 00:24:47.909 --> 00:24:51.229 align:start position:0% with general-purpose computation in that we<00:24:48.330> can<00:24:48.570> build<00:24:48.869> an<00:24:49.200> EVM<00:24:49.769> you<00:24:50.159> know<00:24:50.279> a<00:24:50.549> real<00:24:50.849> you 00:24:51.229 --> 00:24:51.239 align:start position:0% we can build an EVM you know a real you 00:24:51.239 --> 00:24:52.909 align:start position:0% we can build an EVM you know a real you know<00:24:51.359> like<00:24:51.839> normal 00:24:52.909 --> 00:24:52.919 align:start position:0% know like normal 00:24:52.919 --> 00:24:55.820 align:start position:0% know like normal normal<00:24:53.820> solidity<00:24:54.690> developer<00:24:55.349> experience 00:24:55.820 --> 00:24:55.830 align:start position:0% normal solidity developer experience 00:24:55.830 --> 00:24:59.060 align:start position:0% normal solidity developer experience inside<00:24:56.609> of<00:24:56.789> aetherium<00:24:57.299> with<00:24:58.259> better<00:24:58.559> scaling 00:24:59.060 --> 00:24:59.070 align:start position:0% inside of aetherium with better scaling 00:24:59.070 --> 00:25:02.060 align:start position:0% inside of aetherium with better scaling properties<00:24:59.519> using<00:25:00.089> this<00:25:00.419> technique<00:25:00.899> so<00:25:01.289> this 00:25:02.060 --> 00:25:02.070 align:start position:0% properties using this technique so this 00:25:02.070 --> 00:25:03.859 align:start position:0% properties using this technique so this is<00:25:02.190> a<00:25:02.219> really<00:25:02.549> really<00:25:02.700> nice<00:25:02.969> thing<00:25:03.029> and<00:25:03.719> it 00:25:03.859 --> 00:25:03.869 align:start position:0% is a really really nice thing and it 00:25:03.869 --> 00:25:07.039 align:start position:0% is a really really nice thing and it actually<00:25:03.899> borrows<00:25:04.859> a<00:25:04.889> lot<00:25:05.279> of<00:25:05.580> you<00:25:06.149> know<00:25:06.179> kind 00:25:07.039 --> 00:25:07.049 align:start position:0% actually borrows a lot of you know kind 00:25:07.049 --> 00:25:10.579 align:start position:0% actually borrows a lot of you know kind of<00:25:07.200> inspiration<00:25:07.950> and<00:25:08.339> and<00:25:08.580> and<00:25:09.080> you<00:25:10.080> know<00:25:10.200> this 00:25:10.579 --> 00:25:10.589 align:start position:0% of inspiration and and and you know this 00:25:10.589 --> 00:25:12.229 align:start position:0% of inspiration and and and you know this is<00:25:10.799> this<00:25:10.979> is<00:25:11.159> very<00:25:11.190> similar<00:25:11.609> to<00:25:11.759> the<00:25:11.999> stuff 00:25:12.229 --> 00:25:12.239 align:start position:0% is this is very similar to the stuff 00:25:12.239 --> 00:25:14.029 align:start position:0% is this is very similar to the stuff that's<00:25:12.269> going<00:25:12.570> on<00:25:12.809> maybe<00:25:13.019> two<00:25:13.409> with<00:25:13.649> all<00:25:13.799> the 00:25:14.029 --> 00:25:14.039 align:start position:0% that's going on maybe two with all the 00:25:14.039 --> 00:25:15.319 align:start position:0% that's going on maybe two with all the sharding<00:25:14.489> and<00:25:14.669> data<00:25:14.879> availability 00:25:15.319 --> 00:25:15.329 align:start position:0% sharding and data availability 00:25:15.329 --> 00:25:17.209 align:start position:0% sharding and data availability separation<00:25:16.079> and<00:25:16.259> it<00:25:16.619> all<00:25:16.769> plays<00:25:17.009> really 00:25:17.209 --> 00:25:17.219 align:start position:0% separation and it all plays really 00:25:17.219 --> 00:25:19.849 align:start position:0% separation and it all plays really nicely<00:25:17.339> and<00:25:17.789> once<00:25:18.029> we<00:25:18.209> do<00:25:18.389> happy<00:25:18.719> to<00:25:19.200> then 00:25:19.849 --> 00:25:19.859 align:start position:0% nicely and once we do happy to then 00:25:19.859 --> 00:25:22.969 align:start position:0% nicely and once we do happy to then we'll<00:25:20.070> just<00:25:20.249> have<00:25:20.339> way<00:25:20.759> more<00:25:21.469> ability<00:25:22.469> to<00:25:22.499> kind 00:25:22.969 --> 00:25:22.979 align:start position:0% we'll just have way more ability to kind 00:25:22.979 --> 00:25:24.889 align:start position:0% we'll just have way more ability to kind of<00:25:23.099> post<00:25:23.339> data<00:25:23.789> so<00:25:24.059> it<00:25:24.149> just<00:25:24.329> kind<00:25:24.509> of<00:25:24.570> scales 00:25:24.889 --> 00:25:24.899 align:start position:0% of post data so it just kind of scales 00:25:24.899 --> 00:25:27.049 align:start position:0% of post data so it just kind of scales us<00:25:25.139> up<00:25:25.320> pretty<00:25:25.829> you<00:25:26.249> know<00:25:26.369> pretty 00:25:27.049 --> 00:25:27.059 align:start position:0% us up pretty you know pretty 00:25:27.059 --> 00:25:28.909 align:start position:0% us up pretty you know pretty significantly<00:25:27.719> maybe<00:25:28.079> linearly<00:25:28.589> with<00:25:28.739> the 00:25:28.909 --> 00:25:28.919 align:start position:0% significantly maybe linearly with the 00:25:28.919 --> 00:25:32.299 align:start position:0% significantly maybe linearly with the number<00:25:29.009> of<00:25:29.309> shots<00:25:30.589> so<00:25:31.589> I<00:25:31.619> think<00:25:31.739> that's<00:25:32.009> kind 00:25:32.299 --> 00:25:32.309 align:start position:0% number of shots so I think that's kind 00:25:32.309 --> 00:25:34.969 align:start position:0% number of shots so I think that's kind of<00:25:32.519> a<00:25:32.700> high-level<00:25:33.329> overview<00:25:33.749> the<00:25:34.529> benefits 00:25:34.969 --> 00:25:34.979 align:start position:0% of a high-level overview the benefits 00:25:34.979 --> 00:25:38.659 align:start position:0% of a high-level overview the benefits are<00:25:35.190> scale<00:25:36.029> the<00:25:36.839> downsides<00:25:37.709> are<00:25:38.039> over<00:25:38.459> then 00:25:38.659 --> 00:25:38.669 align:start position:0% are scale the downsides are over then 00:25:38.669 --> 00:25:41.509 align:start position:0% are scale the downsides are over then and<00:25:38.849> then<00:25:38.999> the<00:25:39.239> downsides<00:25:40.079> I<00:25:40.259> mean<00:25:40.619> I<00:25:40.889> don't 00:25:41.509 --> 00:25:41.519 align:start position:0% and then the downsides I mean I don't 00:25:41.519 --> 00:25:46.290 align:start position:0% and then the downsides I mean I don't know<00:25:41.789> there<00:25:42.059> are<00:25:42.119> no<00:25:42.209> downsides 00:25:46.290 --> 00:25:46.300 align:start position:0% 00:25:46.300 --> 00:25:50.130 align:start position:0% technology<00:25:47.290> was<00:25:47.740> a<00:25:47.800> quiz<00:25:48.340> question<00:25:49.140> what's 00:25:50.130 --> 00:25:50.140 align:start position:0% technology was a quiz question what's 00:25:50.140 --> 00:25:51.810 align:start position:0% technology was a quiz question what's the<00:25:50.290> size<00:25:50.680> of<00:25:50.860> the<00:25:50.950> park<00:25:51.160> groups<00:25:51.400> and<00:25:51.610> is<00:25:51.700> the 00:25:51.810 --> 00:25:51.820 align:start position:0% the size of the park groups and is the 00:25:51.820 --> 00:25:54.990 align:start position:0% the size of the park groups and is the scale<00:25:52.090> with<00:25:52.300> data<00:25:53.230> presentation<00:25:53.800> right<00:25:54.190> great 00:25:54.990 --> 00:25:55.000 align:start position:0% scale with data presentation right great 00:25:55.000 --> 00:25:57.210 align:start position:0% scale with data presentation right great question<00:25:55.390> so<00:25:55.750> basically<00:25:56.620> what<00:25:56.860> you<00:25:56.950> can<00:25:56.980> think 00:25:57.210 --> 00:25:57.220 align:start position:0% question so basically what you can think 00:25:57.220 --> 00:25:59.250 align:start position:0% question so basically what you can think of<00:25:57.340> the<00:25:57.490> Frog<00:25:57.940> groups<00:25:58.210> you<00:25:58.600> need<00:25:58.720> to<00:25:58.930> commit 00:25:59.250 --> 00:25:59.260 align:start position:0% of the Frog groups you need to commit 00:25:59.260 --> 00:26:01.680 align:start position:0% of the Frog groups you need to commit intermediate<00:25:59.980> state<00:26:00.220> routes<00:26:00.690> frequently 00:26:01.680 --> 00:26:01.690 align:start position:0% intermediate state routes frequently 00:26:01.690 --> 00:26:04.380 align:start position:0% intermediate state routes frequently enough<00:26:01.990> that<00:26:02.050> you<00:26:02.830> can<00:26:03.040> evaluate<00:26:03.370> that<00:26:03.970> full 00:26:04.380 --> 00:26:04.390 align:start position:0% enough that you can evaluate that full 00:26:04.390 --> 00:26:07.140 align:start position:0% enough that you can evaluate that full transition<00:26:05.230> in<00:26:05.590> one<00:26:05.800> lock<00:26:06.040> so<00:26:06.550> you<00:26:06.610> say<00:26:06.910> like 00:26:07.140 --> 00:26:07.150 align:start position:0% transition in one lock so you say like 00:26:07.150 --> 00:26:09.420 align:start position:0% transition in one lock so you say like okay<00:26:07.480> we're<00:26:07.720> going<00:26:07.870> to<00:26:07.990> you<00:26:08.500> know<00:26:08.530> cap<00:26:08.860> it<00:26:09.070> at<00:26:09.250> 2 00:26:09.420 --> 00:26:09.430 align:start position:0% okay we're going to you know cap it at 2 00:26:09.430 --> 00:26:12.810 align:start position:0% okay we're going to you know cap it at 2 million<00:26:09.640> gas<00:26:10.470> internally<00:26:11.470> and<00:26:11.710> so<00:26:12.190> we<00:26:12.520> we 00:26:12.810 --> 00:26:12.820 align:start position:0% million gas internally and so we we 00:26:12.820 --> 00:26:14.880 align:start position:0% million gas internally and so we we basically<00:26:13.270> you<00:26:13.690> know<00:26:13.810> can<00:26:13.990> only<00:26:14.170> do<00:26:14.530> two 00:26:14.880 --> 00:26:14.890 align:start position:0% basically you know can only do two 00:26:14.890 --> 00:26:16.950 align:start position:0% basically you know can only do two million<00:26:15.130> dollars<00:26:15.550> of<00:26:15.730> computation<00:26:16.030> so<00:26:16.780> you<00:26:16.840> do 00:26:16.950 --> 00:26:16.960 align:start position:0% million dollars of computation so you do 00:26:16.960 --> 00:26:19.050 align:start position:0% million dollars of computation so you do the<00:26:17.080> full<00:26:17.320> state<00:26:17.890> transition<00:26:18.370> in<00:26:18.490> the<00:26:18.640> case<00:26:18.910> of 00:26:19.050 --> 00:26:19.060 align:start position:0% the full state transition in the case of 00:26:19.060 --> 00:26:20.700 align:start position:0% the full state transition in the case of product<00:26:19.450> yes<00:26:19.750> we<00:26:20.020> do<00:26:20.140> the<00:26:20.260> full<00:26:20.440> stage 00:26:20.700 --> 00:26:20.710 align:start position:0% product yes we do the full stage 00:26:20.710 --> 00:26:22.080 align:start position:0% product yes we do the full stage incision<00:26:21.160> and<00:26:21.340> we<00:26:21.460> go<00:26:21.580> from<00:26:21.700> one<00:26:21.910> community 00:26:22.080 --> 00:26:22.090 align:start position:0% incision and we go from one community 00:26:22.090 --> 00:26:24.000 align:start position:0% incision and we go from one community root<00:26:22.600> to<00:26:22.750> the<00:26:22.780> nuts<00:26:23.020> and<00:26:23.260> are<00:26:23.410> there<00:26:23.560> timing 00:26:24.000 --> 00:26:24.010 align:start position:0% root to the nuts and are there timing 00:26:24.010 --> 00:26:26.940 align:start position:0% root to the nuts and are there timing assumptions<00:26:24.640> on<00:26:25.320> when<00:26:26.320> you<00:26:26.530> have<00:26:26.650> to<00:26:26.740> get<00:26:26.830> this 00:26:26.940 --> 00:26:26.950 align:start position:0% assumptions on when you have to get this 00:26:26.950 --> 00:26:28.920 align:start position:0% assumptions on when you have to get this property<00:26:27.220> a<00:26:27.670> great<00:26:28.180> question<00:26:28.600> so 00:26:28.920 --> 00:26:28.930 align:start position:0% property a great question so 00:26:28.930 --> 00:26:31.500 align:start position:0% property a great question so interestingly<00:26:29.380> this<00:26:30.280> is<00:26:30.340> almost<00:26:30.880> like<00:26:31.030> a<00:26:31.090> side 00:26:31.500 --> 00:26:31.510 align:start position:0% interestingly this is almost like a side 00:26:31.510 --> 00:26:33.420 align:start position:0% interestingly this is almost like a side chain<00:26:31.870> inside<00:26:32.320> of<00:26:32.500> an<00:26:32.590> area<00:26:32.860> or<00:26:33.010> like<00:26:33.220> you<00:26:33.400> know 00:26:33.420 --> 00:26:33.430 align:start position:0% chain inside of an area or like you know 00:26:33.430 --> 00:26:35.430 align:start position:0% chain inside of an area or like you know it's<00:26:33.640> like<00:26:33.760> it's<00:26:33.940> kind<00:26:34.150> of<00:26:34.180> like<00:26:34.330> a<00:26:34.480> weird<00:26:35.050> you 00:26:35.430 --> 00:26:35.440 align:start position:0% it's like it's kind of like a weird you 00:26:35.440 --> 00:26:38.730 align:start position:0% it's like it's kind of like a weird you know<00:26:35.470> it's<00:26:36.000> somehow<00:26:37.000> the<00:26:37.480> exit<00:26:37.960> procedure<00:26:38.470> is 00:26:38.730 --> 00:26:38.740 align:start position:0% know it's somehow the exit procedure is 00:26:38.740 --> 00:26:41.700 align:start position:0% know it's somehow the exit procedure is a<00:26:38.770> little<00:26:38.920> bit<00:26:39.280> like<00:26:39.880> you<00:26:40.450> know<00:26:40.710> reminiscent 00:26:41.700 --> 00:26:41.710 align:start position:0% a little bit like you know reminiscent 00:26:41.710 --> 00:26:44.310 align:start position:0% a little bit like you know reminiscent of<00:26:41.800> just<00:26:42.010> a<00:26:42.100> normal<00:26:42.490> you<00:26:42.850> know<00:26:42.880> bridge<00:26:43.390> where 00:26:44.310 --> 00:26:44.320 align:start position:0% of just a normal you know bridge where 00:26:44.320 --> 00:26:46.440 align:start position:0% of just a normal you know bridge where essentially<00:26:44.890> what<00:26:45.040> we<00:26:45.160> do<00:26:45.280> is<00:26:45.430> we<00:26:45.550> say<00:26:45.730> well 00:26:46.440 --> 00:26:46.450 align:start position:0% essentially what we do is we say well 00:26:46.450 --> 00:26:48.270 align:start position:0% essentially what we do is we say well for<00:26:47.020> one<00:26:47.170> we<00:26:47.200> don't<00:26:47.620> actually<00:26:47.860> need<00:26:48.220> a 00:26:48.270 --> 00:26:48.280 align:start position:0% for one we don't actually need a 00:26:48.280 --> 00:26:50.880 align:start position:0% for one we don't actually need a finality<00:26:48.820> period<00:26:49.450> baked-in<00:26:50.140> like<00:26:50.680> that's 00:26:50.880 --> 00:26:50.890 align:start position:0% finality period baked-in like that's 00:26:50.890 --> 00:26:52.890 align:start position:0% finality period baked-in like that's kind<00:26:51.250> of<00:26:51.310> something<00:26:51.610> that<00:26:51.820> you<00:26:51.970> could<00:26:52.270> add<00:26:52.570> you 00:26:52.890 --> 00:26:52.900 align:start position:0% kind of something that you could add you 00:26:52.900 --> 00:26:54.810 align:start position:0% kind of something that you could add you could<00:26:53.080> just<00:26:53.230> say<00:26:53.350> will<00:26:53.590> revert<00:26:54.100> infinitely 00:26:54.810 --> 00:26:54.820 align:start position:0% could just say will revert infinitely 00:26:54.820 --> 00:26:57.210 align:start position:0% could just say will revert infinitely far<00:26:55.090> back<00:26:55.330> but<00:26:55.840> that's<00:26:55.930> not<00:26:56.170> really<00:26:56.560> that 00:26:57.210 --> 00:26:57.220 align:start position:0% far back but that's not really that 00:26:57.220 --> 00:26:59.280 align:start position:0% far back but that's not really that realistic<00:26:57.970> considering<00:26:58.840> all<00:26:59.050> that<00:26:59.170> may 00:26:59.280 --> 00:26:59.290 align:start position:0% realistic considering all that may 00:26:59.290 --> 00:27:01.080 align:start position:0% realistic considering all that may change<00:26:59.500> you<00:26:59.680> might<00:26:59.860> want<00:27:00.130> to<00:27:00.220> say<00:27:00.580> you<00:27:01.060> know 00:27:01.080 --> 00:27:01.090 align:start position:0% change you might want to say you know 00:27:01.090 --> 00:27:03.750 align:start position:0% change you might want to say you know submit<00:27:01.480> a<00:27:01.510> transaction<00:27:02.200> which<00:27:02.740> then<00:27:03.010> deposits 00:27:03.750 --> 00:27:03.760 align:start position:0% submit a transaction which then deposits 00:27:03.760 --> 00:27:06.510 align:start position:0% submit a transaction which then deposits some<00:27:04.240> amount<00:27:04.540> of<00:27:04.630> evil<00:27:05.050> right<00:27:05.620> and<00:27:05.830> we<00:27:06.160> we 00:27:06.510 --> 00:27:06.520 align:start position:0% some amount of evil right and we we 00:27:06.520 --> 00:27:09.030 align:start position:0% some amount of evil right and we we basically<00:27:06.840> want<00:27:07.840> the<00:27:08.200> ability<00:27:08.350> to<00:27:08.620> then 00:27:09.030 --> 00:27:09.040 align:start position:0% basically want the ability to then 00:27:09.040 --> 00:27:11.430 align:start position:0% basically want the ability to then withdraw<00:27:09.610> that<00:27:09.880> even<00:27:10.120> eventually<00:27:10.570> and<00:27:10.750> to 00:27:11.430 --> 00:27:11.440 align:start position:0% withdraw that even eventually and to 00:27:11.440 --> 00:27:14.340 align:start position:0% withdraw that even eventually and to withdraw<00:27:11.620> the<00:27:12.070> eve<00:27:12.460> we<00:27:13.390> need<00:27:13.630> to<00:27:13.930> have<00:27:14.170> this 00:27:14.340 --> 00:27:14.350 align:start position:0% withdraw the eve we need to have this 00:27:14.350 --> 00:27:15.750 align:start position:0% withdraw the eve we need to have this lioness<00:27:14.830> assumption<00:27:15.310> that<00:27:15.340> you're<00:27:15.580> talking 00:27:15.750 --> 00:27:15.760 align:start position:0% lioness assumption that you're talking 00:27:15.760 --> 00:27:18.960 align:start position:0% lioness assumption that you're talking about<00:27:16.000> and<00:27:16.510> so<00:27:16.900> because<00:27:17.710> I<00:27:17.980> decided<00:27:18.370> it's<00:27:18.730> one 00:27:18.960 --> 00:27:18.970 align:start position:0% about and so because I decided it's one 00:27:18.970 --> 00:27:22.980 align:start position:0% about and so because I decided it's one week<00:27:19.320> so<00:27:20.320> one<00:27:20.500> week<00:27:20.680> that's<00:27:21.100> exactly<00:27:22.000> the<00:27:22.720> time 00:27:22.980 --> 00:27:22.990 align:start position:0% week so one week that's exactly the time 00:27:22.990 --> 00:27:25.380 align:start position:0% week so one week that's exactly the time that<00:27:23.020> it<00:27:23.560> will<00:27:23.710> take<00:27:23.770> to<00:27:24.580> find<00:27:24.820> the<00:27:24.910> front<00:27:25.090> a 00:27:25.380 --> 00:27:25.390 align:start position:0% that it will take to find the front a 00:27:25.390 --> 00:27:28.650 align:start position:0% that it will take to find the front a question<00:27:25.960> Solon's<00:27:26.440> yeah<00:27:27.160> yeah<00:27:28.090> so<00:27:28.270> property 00:27:28.650 --> 00:27:28.660 align:start position:0% question Solon's yeah yeah so property 00:27:28.660 --> 00:27:31.020 align:start position:0% question Solon's yeah yeah so property goes<00:27:28.840> in<00:27:29.020> and<00:27:29.350> we<00:27:29.830> now<00:27:29.980> build<00:27:30.310> on<00:27:30.490> it<00:27:30.670> basically 00:27:31.020 --> 00:27:31.030 align:start position:0% goes in and we now build on it basically 00:27:31.030 --> 00:27:32.350 align:start position:0% goes in and we now build on it basically delivery<00:27:31.660> is 00:27:32.350 --> 00:27:32.360 align:start position:0% delivery is 00:27:32.360 --> 00:27:34.330 align:start position:0% delivery is that<00:27:32.630> transaction<00:27:33.140> yeah<00:27:33.290> how<00:27:33.860> do<00:27:33.920> you<00:27:34.040> do<00:27:34.190> that 00:27:34.330 --> 00:27:34.340 align:start position:0% that transaction yeah how do you do that 00:27:34.340 --> 00:27:36.820 align:start position:0% that transaction yeah how do you do that without<00:27:34.660> halting<00:27:35.660> the<00:27:35.900> chain<00:27:36.140> let's<00:27:36.530> say<00:27:36.679> it 00:27:36.820 --> 00:27:36.830 align:start position:0% without halting the chain let's say it 00:27:36.830 --> 00:27:39.640 align:start position:0% without halting the chain let's say it comes<00:27:37.100> one<00:27:37.520> week<00:27:37.670> later<00:27:37.910> and<00:27:38.650> basically 00:27:39.640 --> 00:27:39.650 align:start position:0% comes one week later and basically 00:27:39.650 --> 00:27:43.270 align:start position:0% comes one week later and basically relation<00:27:40.640> eight<00:27:40.700> or<00:27:41.260> other<00:27:42.260> validators<00:27:43.130> or 00:27:43.270 --> 00:27:43.280 align:start position:0% relation eight or other validators or 00:27:43.280 --> 00:27:45.430 align:start position:0% relation eight or other validators or sequence<00:27:43.610> in<00:27:43.730> the<00:27:43.850> auditory<00:27:44.270> route<00:27:44.600> are<00:27:45.230> just 00:27:45.430 --> 00:27:45.440 align:start position:0% sequence in the auditory route are just 00:27:45.440 --> 00:27:46.780 align:start position:0% sequence in the auditory route are just not<00:27:45.590> going<00:27:45.740> to<00:27:45.799> build<00:27:45.950> on<00:27:46.040> top<00:27:46.100> of<00:27:46.280> this<00:27:46.429> state 00:27:46.780 --> 00:27:46.790 align:start position:0% not going to build on top of this state 00:27:46.790 --> 00:27:49.030 align:start position:0% not going to build on top of this state technically<00:27:47.210> know<00:27:47.360> that<00:27:47.510> it's<00:27:47.630> wrong<00:27:48.040> guess 00:27:49.030 --> 00:27:49.040 align:start position:0% technically know that it's wrong guess 00:27:49.040 --> 00:27:51.039 align:start position:0% technically know that it's wrong guess what<00:27:49.220> what<00:27:49.460> is<00:27:49.549> the<00:27:49.730> reorg<00:27:50.030> process<00:27:50.510> look<00:27:50.809> like 00:27:51.039 --> 00:27:51.049 align:start position:0% what what is the reorg process look like 00:27:51.049 --> 00:27:52.810 align:start position:0% what what is the reorg process look like and<00:27:51.350> what<00:27:51.620> happens<00:27:51.950> if<00:27:52.070> the<00:27:52.160> property<00:27:52.549> doesn't 00:27:52.810 --> 00:27:52.820 align:start position:0% and what happens if the property doesn't 00:27:52.820 --> 00:27:54.820 align:start position:0% and what happens if the property doesn't like<00:27:53.059> go<00:27:53.420> up<00:27:53.450> until<00:27:53.870> four<00:27:54.110> days<00:27:54.140> later 00:27:54.820 --> 00:27:54.830 align:start position:0% like go up until four days later 00:27:54.830 --> 00:27:57.549 align:start position:0% like go up until four days later great<00:27:55.429> question<00:27:55.880> okay<00:27:56.150> so<00:27:56.540> technically<00:27:57.380> I'm 00:27:57.549 --> 00:27:57.559 align:start position:0% great question okay so technically I'm 00:27:57.559 --> 00:27:59.350 align:start position:0% great question okay so technically I'm doing<00:27:57.890> some<00:27:58.100> some<00:27:58.460> simplifications<00:27:59.240> here 00:27:59.350 --> 00:27:59.360 align:start position:0% doing some some simplifications here 00:27:59.360 --> 00:28:02.169 align:start position:0% doing some some simplifications here right<00:28:00.580> realistically<00:28:01.580> there<00:28:01.760> are<00:28:01.820> two<00:28:01.910> things 00:28:02.169 --> 00:28:02.179 align:start position:0% right realistically there are two things 00:28:02.179 --> 00:28:04.600 align:start position:0% right realistically there are two things that<00:28:02.240> are<00:28:02.390> happening<00:28:02.540> there's<00:28:03.410> this<00:28:04.040> kind<00:28:04.460> of 00:28:04.600 --> 00:28:04.610 align:start position:0% that are happening there's this kind of 00:28:04.610 --> 00:28:07.570 align:start position:0% that are happening there's this kind of log<00:28:05.090> of<00:28:05.510> transactions<00:28:06.380> these<00:28:07.160> are<00:28:07.309> all<00:28:07.429> the 00:28:07.570 --> 00:28:07.580 align:start position:0% log of transactions these are all the 00:28:07.580 --> 00:28:11.080 align:start position:0% log of transactions these are all the different<00:28:07.669> transactions<00:28:08.650> right<00:28:09.850> tons<00:28:10.850> of 00:28:11.080 --> 00:28:11.090 align:start position:0% different transactions right tons of 00:28:11.090 --> 00:28:13.330 align:start position:0% different transactions right tons of tons<00:28:11.299> of<00:28:11.540> transactions<00:28:12.169> and<00:28:12.320> then<00:28:12.710> here's<00:28:12.980> the 00:28:13.330 --> 00:28:13.340 align:start position:0% tons of transactions and then here's the 00:28:13.340 --> 00:28:16.780 align:start position:0% tons of transactions and then here's the log<00:28:13.610> of<00:28:13.880> state<00:28:14.179> routes<00:28:15.160> right<00:28:16.160> and<00:28:16.460> here's<00:28:16.700> a 00:28:16.780 --> 00:28:16.790 align:start position:0% log of state routes right and here's a 00:28:16.790 --> 00:28:18.490 align:start position:0% log of state routes right and here's a bunch<00:28:17.030> of<00:28:17.150> state<00:28:17.419> routes<00:28:17.600> and<00:28:17.690> so<00:28:18.110> the<00:28:18.290> trick 00:28:18.490 --> 00:28:18.500 align:start position:0% bunch of state routes and so the trick 00:28:18.500 --> 00:28:20.740 align:start position:0% bunch of state routes and so the trick you<00:28:18.679> basically<00:28:19.370> use<00:28:19.730> some<00:28:20.150> set<00:28:20.419> of<00:28:20.450> these 00:28:20.740 --> 00:28:20.750 align:start position:0% you basically use some set of these 00:28:20.750 --> 00:28:22.750 align:start position:0% you basically use some set of these transactions<00:28:21.380> to<00:28:21.799> generate<00:28:22.220> one<00:28:22.460> of<00:28:22.490> these 00:28:22.750 --> 00:28:22.760 align:start position:0% transactions to generate one of these 00:28:22.760 --> 00:28:24.970 align:start position:0% transactions to generate one of these states<00:28:23.240> right<00:28:23.990> and<00:28:24.169> then<00:28:24.260> you<00:28:24.380> use<00:28:24.650> another 00:28:24.970 --> 00:28:24.980 align:start position:0% states right and then you use another 00:28:24.980 --> 00:28:26.740 align:start position:0% states right and then you use another set<00:28:25.280> and<00:28:25.549> you<00:28:25.610> generate<00:28:26.000> another<00:28:26.240> state<00:28:26.570> route 00:28:26.740 --> 00:28:26.750 align:start position:0% set and you generate another state route 00:28:26.750 --> 00:28:29.560 align:start position:0% set and you generate another state route and<00:28:27.020> so<00:28:27.350> if<00:28:27.799> they're<00:28:28.130> if<00:28:28.370> this<00:28:28.640> guy<00:28:28.850> is<00:28:28.910> invalid 00:28:29.560 --> 00:28:29.570 align:start position:0% and so if they're if this guy is invalid 00:28:29.570 --> 00:28:32.470 align:start position:0% and so if they're if this guy is invalid right<00:28:30.320> then<00:28:31.010> what<00:28:31.190> would<00:28:31.400> happen<00:28:31.610> is<00:28:31.970> we<00:28:32.179> would 00:28:32.470 --> 00:28:32.480 align:start position:0% right then what would happen is we would 00:28:32.480 --> 00:28:34.600 align:start position:0% right then what would happen is we would have<00:28:32.780> to<00:28:32.929> basically<00:28:33.280> reprocess<00:28:34.280> all<00:28:34.400> these 00:28:34.600 --> 00:28:34.610 align:start position:0% have to basically reprocess all these 00:28:34.610 --> 00:28:37.480 align:start position:0% have to basically reprocess all these transactions<00:28:35.270> based<00:28:35.900> on<00:28:36.260> you<00:28:36.919> know<00:28:36.980> the 00:28:37.480 --> 00:28:37.490 align:start position:0% transactions based on you know the 00:28:37.490 --> 00:28:39.070 align:start position:0% transactions based on you know the actually<00:28:38.030> you<00:28:38.059> know<00:28:38.210> reprocess<00:28:38.809> all<00:28:38.929> the 00:28:39.070 --> 00:28:39.080 align:start position:0% actually you know reprocess all the 00:28:39.080 --> 00:28:41.020 align:start position:0% actually you know reprocess all the transactions<00:28:39.620> after<00:28:40.010> this<00:28:40.190> state<00:28:40.460> route<00:28:40.669> so 00:28:41.020 --> 00:28:41.030 align:start position:0% transactions after this state route so 00:28:41.030 --> 00:28:43.090 align:start position:0% transactions after this state route so like<00:28:41.210> once<00:28:41.480> we<00:28:41.630> challenge<00:28:42.020> it<00:28:42.169> we<00:28:42.530> delete<00:28:42.950> the 00:28:43.090 --> 00:28:43.100 align:start position:0% like once we challenge it we delete the 00:28:43.100 --> 00:28:44.380 align:start position:0% like once we challenge it we delete the state<00:28:43.340> route<00:28:43.580> we<00:28:43.730> would<00:28:43.880> not<00:28:44.000> delete<00:28:44.360> the 00:28:44.380 --> 00:28:44.390 align:start position:0% state route we would not delete the 00:28:44.390 --> 00:28:46.659 align:start position:0% state route we would not delete the transactions<00:28:45.140> and<00:28:45.290> then<00:28:45.679> we<00:28:45.830> just<00:28:46.040> reprocess 00:28:46.659 --> 00:28:46.669 align:start position:0% transactions and then we just reprocess 00:28:46.669 --> 00:28:49.900 align:start position:0% transactions and then we just reprocess everything<00:28:47.410> so<00:28:48.410> it<00:28:48.679> but<00:28:49.280> it<00:28:49.370> does<00:28:49.520> require<00:28:49.730> a 00:28:49.900 --> 00:28:49.910 align:start position:0% everything so it but it does require a 00:28:49.910 --> 00:28:51.610 align:start position:0% everything so it but it does require a reorg<00:28:50.360> and<00:28:50.600> if<00:28:50.690> you're<00:28:50.870> like<00:28:51.110> it<00:28:51.290> because<00:28:51.500> if 00:28:51.610 --> 00:28:51.620 align:start position:0% reorg and if you're like it because if 00:28:51.620 --> 00:28:53.710 align:start position:0% reorg and if you're like it because if it<00:28:51.740> gets<00:28:51.830> in<00:28:52.070> four<00:28:52.280> days<00:28:52.490> ago<00:28:52.669> and<00:28:53.090> you<00:28:53.600> know 00:28:53.710 --> 00:28:53.720 align:start position:0% it gets in four days ago and you know 00:28:53.720 --> 00:28:56.560 align:start position:0% it gets in four days ago and you know you<00:28:53.780> bought<00:28:54.260> some<00:28:54.919> some<00:28:55.760> even<00:28:56.090> or<00:28:56.210> something 00:28:56.560 --> 00:28:56.570 align:start position:0% you bought some some even or something 00:28:56.570 --> 00:28:58.780 align:start position:0% you bought some some even or something or<00:28:56.690> you<00:28:56.780> bought<00:28:56.929> some<00:28:57.200> token<00:28:57.650> and<00:28:57.950> it's 00:28:58.780 --> 00:28:58.790 align:start position:0% or you bought some token and it's 00:28:58.790 --> 00:29:00.820 align:start position:0% or you bought some token and it's dependent<00:28:59.419> on<00:28:59.510> an<00:28:59.660> invalid<00:29:00.049> Sabre<00:29:00.290> then<00:29:00.620> yes 00:29:00.820 --> 00:29:00.830 align:start position:0% dependent on an invalid Sabre then yes 00:29:00.830 --> 00:29:02.680 align:start position:0% dependent on an invalid Sabre then yes you<00:29:01.100> you<00:29:01.370> will<00:29:01.549> you<00:29:01.850> may<00:29:02.000> not<00:29:02.179> have<00:29:02.360> your<00:29:02.510> money 00:29:02.680 --> 00:29:02.690 align:start position:0% you you will you may not have your money 00:29:02.690 --> 00:29:09.090 align:start position:0% you you will you may not have your money but<00:29:03.230> that's<00:29:03.440> why<00:29:03.590> someone<00:29:03.860> has<00:29:04.010> to<00:29:04.100> check 00:29:09.090 --> 00:29:09.100 align:start position:0% 00:29:09.100 --> 00:29:24.590 align:start position:0% [Music] 00:29:24.590 --> 00:29:24.600 align:start position:0% 00:29:24.600 --> 00:29:34.669 align:start position:0% but<00:29:24.750> I<00:29:24.840> mean<00:29:25.010> so<00:29:26.010> in<00:29:26.280> that<00:29:26.400> case<00:29:26.730> how<00:29:33.590> do<00:29:34.590> you 00:29:34.669 --> 00:29:34.679 align:start position:0% but I mean so in that case how do you 00:29:34.679 --> 00:29:36.830 align:start position:0% but I mean so in that case how do you mean<00:29:34.860> that<00:29:35.070> you<00:29:35.370> mean<00:29:35.580> a<00:29:35.790> fraud<00:29:36.059> here<00:29:36.390> or<00:29:36.570> fried 00:29:36.830 --> 00:29:36.840 align:start position:0% mean that you mean a fraud here or fried 00:29:36.840 --> 00:29:38.299 align:start position:0% mean that you mean a fraud here or fried I<00:29:37.080> mean<00:29:37.320> you<00:29:37.410> have<00:29:37.530> the<00:29:37.620> roller<00:29:37.919> exciting 00:29:38.299 --> 00:29:38.309 align:start position:0% I mean you have the roller exciting 00:29:38.309 --> 00:29:39.049 align:start position:0% I mean you have the roller exciting don't<00:29:38.730> worry 00:29:39.049 --> 00:29:39.059 align:start position:0% don't worry 00:29:39.059 --> 00:29:41.630 align:start position:0% don't worry Roger<00:29:39.510> rule<00:29:40.049> of<00:29:40.200> change<00:29:40.410> Mona<00:29:40.679> okay<00:29:41.220> so 00:29:41.630 --> 00:29:41.640 align:start position:0% Roger rule of change Mona okay so 00:29:41.640 --> 00:29:44.539 align:start position:0% Roger rule of change Mona okay so ethereal<00:29:42.330> thankfully<00:29:43.320> gives<00:29:43.770> us<00:29:43.980> a<00:29:44.190> total 00:29:44.539 --> 00:29:44.549 align:start position:0% ethereal thankfully gives us a total 00:29:44.549 --> 00:29:46.520 align:start position:0% ethereal thankfully gives us a total ordering<00:29:44.970> of<00:29:45.150> transactions<00:29:45.720> which<00:29:46.260> means 00:29:46.520 --> 00:29:46.530 align:start position:0% ordering of transactions which means 00:29:46.530 --> 00:29:48.049 align:start position:0% ordering of transactions which means that<00:29:46.770> there's<00:29:46.919> a<00:29:47.010> deterministic<00:29:47.850> way<00:29:48.000> to 00:29:48.049 --> 00:29:48.059 align:start position:0% that there's a deterministic way to 00:29:48.059 --> 00:29:50.210 align:start position:0% that there's a deterministic way to determine<00:29:48.750> the<00:29:48.900> form<00:29:49.110> and<00:29:49.410> so<00:29:49.679> really<00:29:49.890> you<00:29:50.040> can 00:29:50.210 --> 00:29:50.220 align:start position:0% determine the form and so really you can 00:29:50.220 --> 00:29:53.060 align:start position:0% determine the form and so really you can think<00:29:50.460> of<00:29:50.520> this<00:29:50.640> chain<00:29:50.910> has<00:29:51.230> literally<00:29:52.230> a<00:29:52.590> list 00:29:53.060 --> 00:29:53.070 align:start position:0% think of this chain has literally a list 00:29:53.070 --> 00:29:55.340 align:start position:0% think of this chain has literally a list of<00:29:53.340> blocks<00:29:53.700> like<00:29:54.090> like<00:29:54.570> the<00:29:54.720> data<00:29:54.900> structure 00:29:55.340 --> 00:29:55.350 align:start position:0% of blocks like like the data structure 00:29:55.350 --> 00:29:58.549 align:start position:0% of blocks like like the data structure that<00:29:55.380> we<00:29:55.679> use<00:29:55.710> is<00:29:56.400> just<00:29:56.730> an<00:29:56.970> array<00:29:57.450> and<00:29:57.929> so 00:29:58.549 --> 00:29:58.559 align:start position:0% that we use is just an array and so 00:29:58.559 --> 00:30:00.830 align:start position:0% that we use is just an array and so realistically<00:29:59.520> all<00:29:59.790> you're<00:29:59.970> doing<00:30:00.299> when<00:30:00.690> you 00:30:00.830 --> 00:30:00.840 align:start position:0% realistically all you're doing when you 00:30:00.840 --> 00:30:02.900 align:start position:0% realistically all you're doing when you when<00:30:01.080> you<00:30:01.200> say<00:30:01.410> like<00:30:01.740> have<00:30:01.950> a<00:30:02.040> Ford<00:30:02.340> you're 00:30:02.900 --> 00:30:02.910 align:start position:0% when you say like have a Ford you're 00:30:02.910 --> 00:30:05.330 align:start position:0% when you say like have a Ford you're just<00:30:03.120> like<00:30:03.470> destroying<00:30:04.470> one<00:30:04.740> of<00:30:04.830> the<00:30:04.919> elements 00:30:05.330 --> 00:30:05.340 align:start position:0% just like destroying one of the elements 00:30:05.340 --> 00:30:07.880 align:start position:0% just like destroying one of the elements and<00:30:05.490> then<00:30:06.030> reinserting<00:30:06.780> a<00:30:06.900> new<00:30:07.020> element<00:30:07.380> right 00:30:07.880 --> 00:30:07.890 align:start position:0% and then reinserting a new element right 00:30:07.890 --> 00:30:09.830 align:start position:0% and then reinserting a new element right so<00:30:08.100> there<00:30:08.280> there<00:30:08.520> is<00:30:08.640> there<00:30:09.059> isn't<00:30:09.390> this<00:30:09.630> isn't 00:30:09.830 --> 00:30:09.840 align:start position:0% so there there is there isn't this isn't 00:30:09.840 --> 00:30:11.570 align:start position:0% so there there is there isn't this isn't like<00:30:10.080> a<00:30:10.110> really<00:30:10.530> chlorophyll<00:30:11.040> thing<00:30:11.250> because 00:30:11.570 --> 00:30:11.580 align:start position:0% like a really chlorophyll thing because 00:30:11.580 --> 00:30:13.730 align:start position:0% like a really chlorophyll thing because we<00:30:11.700> don't<00:30:11.910> need<00:30:12.059> a<00:30:12.120> forkful<00:30:12.480> thing<00:30:12.809> because<00:30:13.530> we 00:30:13.730 --> 00:30:13.740 align:start position:0% we don't need a forkful thing because we 00:30:13.740 --> 00:30:19.010 align:start position:0% we don't need a forkful thing because we have<00:30:13.860> this<00:30:13.980> deterministic<00:30:14.520> theory<00:30:17.870> yes<00:30:18.870> I 00:30:19.010 --> 00:30:19.020 align:start position:0% have this deterministic theory yes I 00:30:19.020 --> 00:30:23.419 align:start position:0% have this deterministic theory yes I want<00:30:19.230> to<00:30:19.280> be<00:30:20.450> fake<00:30:21.450> but<00:30:22.169> well<00:30:22.860> what<00:30:23.130> is<00:30:23.280> the 00:30:23.419 --> 00:30:23.429 align:start position:0% want to be fake but well what is the 00:30:23.429 --> 00:30:29.950 align:start position:0% want to be fake but well what is the impact<00:30:23.940> if<00:30:24.840> someone<00:30:25.559> falsely<00:30:26.270> yells<00:30:27.270> fraud 00:30:29.950 --> 00:30:29.960 align:start position:0% 00:30:29.960 --> 00:30:32.780 align:start position:0% well<00:30:30.960> no<00:30:31.080> yes<00:30:31.290> thank<00:30:31.710> you<00:30:31.770> what<00:30:32.250> is<00:30:32.280> being<00:30:32.549> that 00:30:32.780 --> 00:30:32.790 align:start position:0% well no yes thank you what is being that 00:30:32.790 --> 00:30:37.730 align:start position:0% well no yes thank you what is being that sir<00:30:35.270> what<00:30:36.270> is<00:30:36.390> the<00:30:36.540> other<00:30:36.750> I<00:30:36.870> cannot<00:30:37.230> do<00:30:37.410> that 00:30:37.730 --> 00:30:37.740 align:start position:0% sir what is the other I cannot do that 00:30:37.740 --> 00:30:39.950 align:start position:0% sir what is the other I cannot do that what<00:30:38.460> is<00:30:38.580> the<00:30:38.730> impact<00:30:39.030> of<00:30:39.270> wait<00:30:39.600> sorry<00:30:39.840> I 00:30:39.950 --> 00:30:39.960 align:start position:0% what is the impact of wait sorry I 00:30:39.960 --> 00:30:42.570 align:start position:0% what is the impact of wait sorry I forgot<00:30:40.230> the<00:30:40.380> question 00:30:42.570 --> 00:30:42.580 align:start position:0% 00:30:42.580 --> 00:30:45.100 align:start position:0% they've<00:30:43.580> been<00:30:43.669> attack<00:30:44.059> you're<00:30:44.360> falsely 00:30:45.100 --> 00:30:45.110 align:start position:0% they've been attack you're falsely 00:30:45.110 --> 00:30:47.560 align:start position:0% they've been attack you're falsely claims<00:30:45.590> brought<00:30:46.039> them<00:30:46.220> up<00:30:46.519> and<00:30:47.090> what<00:30:47.299> is<00:30:47.419> the 00:30:47.560 --> 00:30:47.570 align:start position:0% claims brought them up and what is the 00:30:47.570 --> 00:30:49.720 align:start position:0% claims brought them up and what is the penalty<00:30:47.809> in<00:30:48.350> doing<00:30:48.679> three<00:30:48.889> so<00:30:49.429> this<00:30:49.549> is 00:30:49.720 --> 00:30:49.730 align:start position:0% penalty in doing three so this is 00:30:49.730 --> 00:30:51.129 align:start position:0% penalty in doing three so this is actually<00:30:50.000> related<00:30:50.120> to<00:30:50.389> a<00:30:50.509> question<00:30:50.779> I<00:30:50.870> didn't 00:30:51.129 --> 00:30:51.139 align:start position:0% actually related to a question I didn't 00:30:51.139 --> 00:30:53.799 align:start position:0% actually related to a question I didn't have<00:30:51.289> answer<00:30:51.649> from<00:30:52.279> you<00:30:52.519> and<00:30:52.879> also<00:30:53.240> I<00:30:53.480> forgot 00:30:53.799 --> 00:30:53.809 align:start position:0% have answer from you and also I forgot 00:30:53.809 --> 00:30:55.840 align:start position:0% have answer from you and also I forgot to<00:30:53.990> mention<00:30:54.559> the<00:30:54.889> first<00:30:55.100> thing<00:30:55.279> so<00:30:55.580> the 00:30:55.840 --> 00:30:55.850 align:start position:0% to mention the first thing so the 00:30:55.850 --> 00:30:57.879 align:start position:0% to mention the first thing so the question<00:30:56.179> is<00:30:56.330> what<00:30:56.750> is<00:30:56.840> the<00:30:56.929> impact<00:30:57.169> of<00:30:57.440> fraud 00:30:57.879 --> 00:30:57.889 align:start position:0% question is what is the impact of fraud 00:30:57.889 --> 00:30:59.470 align:start position:0% question is what is the impact of fraud and<00:30:58.129> the<00:30:58.250> question<00:30:58.519> that<00:30:58.549> if<00:30:58.730> it<00:30:58.850> was<00:30:59.090> what 00:30:59.470 --> 00:30:59.480 align:start position:0% and the question that if it was what 00:30:59.480 --> 00:31:01.330 align:start position:0% and the question that if it was what does<00:30:59.539> it<00:30:59.720> take<00:30:59.899> to<00:31:00.019> be<00:31:00.169> to<00:31:00.620> submit<00:31:01.129> one<00:31:01.309> of 00:31:01.330 --> 00:31:01.340 align:start position:0% does it take to be to submit one of 00:31:01.340 --> 00:31:03.909 align:start position:0% does it take to be to submit one of these<00:31:01.519> blocks<00:31:01.789> Utley<00:31:02.230> so<00:31:03.230> you<00:31:03.289> need<00:31:03.590> a<00:31:03.620> bond 00:31:03.909 --> 00:31:03.919 align:start position:0% these blocks Utley so you need a bond 00:31:03.919 --> 00:31:05.919 align:start position:0% these blocks Utley so you need a bond right<00:31:04.460> there's<00:31:04.759> no<00:31:04.909> question<00:31:05.360> that<00:31:05.570> we<00:31:05.750> need<00:31:05.779> a 00:31:05.919 --> 00:31:05.929 align:start position:0% right there's no question that we need a 00:31:05.929 --> 00:31:07.869 align:start position:0% right there's no question that we need a bond<00:31:06.139> so<00:31:06.409> essentially<00:31:06.830> when<00:31:07.460> you<00:31:07.580> submit<00:31:07.850> a 00:31:07.869 --> 00:31:07.879 align:start position:0% bond so essentially when you submit a 00:31:07.879 --> 00:31:09.669 align:start position:0% bond so essentially when you submit a block<00:31:08.120> there<00:31:08.600> needs<00:31:08.809> to<00:31:08.899> be<00:31:08.960> some<00:31:09.289> money<00:31:09.500> at 00:31:09.669 --> 00:31:09.679 align:start position:0% block there needs to be some money at 00:31:09.679 --> 00:31:12.369 align:start position:0% block there needs to be some money at stake<00:31:09.860> that<00:31:10.279> can<00:31:11.059> be<00:31:11.240> you<00:31:11.570> know<00:31:11.629> slashed<00:31:12.049> and 00:31:12.369 --> 00:31:12.379 align:start position:0% stake that can be you know slashed and 00:31:12.379 --> 00:31:15.129 align:start position:0% stake that can be you know slashed and so<00:31:12.590> what<00:31:12.769> we<00:31:12.919> do<00:31:13.070> is<00:31:13.309> we<00:31:13.460> burn<00:31:14.090> most<00:31:14.720> of<00:31:14.840> it<00:31:14.929> and 00:31:15.129 --> 00:31:15.139 align:start position:0% so what we do is we burn most of it and 00:31:15.139 --> 00:31:16.659 align:start position:0% so what we do is we burn most of it and give<00:31:15.289> some<00:31:15.710> to<00:31:15.830> the<00:31:15.860> rewards<00:31:16.250> that<00:31:16.399> are<00:31:16.549> your 00:31:16.659 --> 00:31:16.669 align:start position:0% give some to the rewards that are your 00:31:16.669 --> 00:31:19.779 align:start position:0% give some to the rewards that are your best<00:31:16.850> moment<00:31:17.210> myself<00:31:17.539> if<00:31:17.899> I<00:31:18.460> falsely<00:31:19.460> claimed 00:31:19.779 --> 00:31:19.789 align:start position:0% best moment myself if I falsely claimed 00:31:19.789 --> 00:31:22.210 align:start position:0% best moment myself if I falsely claimed that<00:31:20.149> something<00:31:20.600> is<00:31:20.690> a<00:31:20.720> problem<00:31:21.230> oh<00:31:21.350> you<00:31:22.100> just 00:31:22.210 --> 00:31:22.220 align:start position:0% that something is a problem oh you just 00:31:22.220 --> 00:31:24.220 align:start position:0% that something is a problem oh you just lose<00:31:22.460> your<00:31:22.580> gas<00:31:22.789> it's<00:31:23.149> great<00:31:23.389> because<00:31:23.870> it's 00:31:24.220 --> 00:31:24.230 align:start position:0% lose your gas it's great because it's 00:31:24.230 --> 00:31:25.570 align:start position:0% lose your gas it's great because it's all<00:31:24.379> deterministic<00:31:24.830> right<00:31:25.309> we're<00:31:25.460> not 00:31:25.570 --> 00:31:25.580 align:start position:0% all deterministic right we're not 00:31:25.580 --> 00:31:27.369 align:start position:0% all deterministic right we're not playing<00:31:25.820> this<00:31:25.909> interactive<00:31:26.450> game<00:31:26.629> you<00:31:27.230> are 00:31:27.369 --> 00:31:27.379 align:start position:0% playing this interactive game you are 00:31:27.379 --> 00:31:29.619 align:start position:0% playing this interactive game you are you<00:31:27.769> submit<00:31:28.100> an<00:31:28.220> invalid<00:31:28.610> frog<00:31:28.820> group<00:31:29.000> and<00:31:29.179> it 00:31:29.619 --> 00:31:29.629 align:start position:0% you submit an invalid frog group and it 00:31:29.629 --> 00:31:31.960 align:start position:0% you submit an invalid frog group and it literally<00:31:30.080> just<00:31:30.110> reverts<00:31:30.649> like<00:31:30.980> like<00:31:31.399> if<00:31:31.639> you 00:31:31.960 --> 00:31:31.970 align:start position:0% literally just reverts like like if you 00:31:31.970 --> 00:31:43.930 align:start position:0% literally just reverts like like if you know<00:31:32.059> aetherium<00:31:32.570> opcode<00:31:33.379> Roberta<00:31:34.840> so<00:31:42.940> the 00:31:43.930 --> 00:31:43.940 align:start position:0% know aetherium opcode Roberta so the 00:31:43.940 --> 00:31:45.789 align:start position:0% know aetherium opcode Roberta so the progress<00:31:44.179> will<00:31:44.600> excuse<00:31:44.929> my<00:31:45.110> blog<00:31:45.350> so<00:31:45.649> it's 00:31:45.789 --> 00:31:45.799 align:start position:0% progress will excuse my blog so it's 00:31:45.799 --> 00:31:47.710 align:start position:0% progress will excuse my blog so it's just<00:31:45.919> spending<00:31:46.370> two<00:31:46.580> million<00:31:46.850> gaspers<00:31:47.269> kind 00:31:47.710 --> 00:31:47.720 align:start position:0% just spending two million gaspers kind 00:31:47.720 --> 00:31:48.970 align:start position:0% just spending two million gaspers kind of<00:31:47.779> sucks<00:31:47.990> and<00:31:48.259> you<00:31:48.320> know<00:31:48.440> deterministic 00:31:48.970 --> 00:31:48.980 align:start position:0% of sucks and you know deterministic 00:31:48.980 --> 00:31:51.490 align:start position:0% of sucks and you know deterministic makes<00:31:49.159> a<00:31:49.279> large<00:31:49.490> do<00:31:49.700> have<00:31:50.509> a<00:31:50.570> question<00:31:50.929> though 00:31:51.490 --> 00:31:51.500 align:start position:0% makes a large do have a question though 00:31:51.500 --> 00:31:55.320 align:start position:0% makes a large do have a question though because<00:31:52.419> you<00:31:53.419> have<00:31:53.600> a<00:31:53.899> period<00:31:54.379> of<00:31:54.500> maximum 00:31:55.320 --> 00:31:55.330 align:start position:0% because you have a period of maximum 00:31:55.330 --> 00:31:58.659 align:start position:0% because you have a period of maximum perversion<00:31:56.330> facility<00:31:56.919> and<00:31:57.919> you<00:31:58.129> have<00:31:58.340> a 00:31:58.659 --> 00:31:58.669 align:start position:0% perversion facility and you have a 00:31:58.669 --> 00:32:01.810 align:start position:0% perversion facility and you have a swollen<00:31:58.909> gas<00:31:59.210> limit<00:31:59.509> on<00:31:59.990> chain<00:32:00.649> thank<00:32:01.129> you<00:32:01.250> you 00:32:01.810 --> 00:32:01.820 align:start position:0% swollen gas limit on chain thank you you 00:32:01.820 --> 00:32:05.320 align:start position:0% swollen gas limit on chain thank you you have<00:32:01.970> a<00:32:02.029> theoretical<00:32:02.600> mass<00:32:04.000> amount<00:32:05.000> of<00:32:05.120> these 00:32:05.320 --> 00:32:05.330 align:start position:0% have a theoretical mass amount of these 00:32:05.330 --> 00:32:08.909 align:start position:0% have a theoretical mass amount of these chains<00:32:05.690> that<00:32:05.840> you<00:32:05.899> can<00:32:06.080> support<00:32:07.070> on<00:32:07.389> correct<00:32:08.389> a 00:32:08.909 --> 00:32:08.919 align:start position:0% chains that you can support on correct a 00:32:08.919 --> 00:32:13.149 align:start position:0% chains that you can support on correct a great<00:32:09.919> question<00:32:10.429> so<00:32:10.460> you've<00:32:11.240> okay<00:32:11.620> I<00:32:12.620> don't 00:32:13.149 --> 00:32:13.159 align:start position:0% great question so you've okay I don't 00:32:13.159 --> 00:32:14.889 align:start position:0% great question so you've okay I don't know<00:32:13.399> if<00:32:13.519> I<00:32:13.669> believe<00:32:14.059> I<00:32:14.210> would<00:32:14.419> say<00:32:14.600> you<00:32:14.659> can 00:32:14.889 --> 00:32:14.899 align:start position:0% know if I believe I would say you can 00:32:14.899 --> 00:32:16.720 align:start position:0% know if I believe I would say you can only<00:32:14.960> refer<00:32:15.409> like<00:32:15.710> Senator<00:32:16.070> Burke<00:32:16.309> period<00:32:16.639> is 00:32:16.720 --> 00:32:16.730 align:start position:0% only refer like Senator Burke period is 00:32:16.730 --> 00:32:18.700 align:start position:0% only refer like Senator Burke period is one<00:32:16.909> lock<00:32:17.120> the<00:32:17.539> only<00:32:17.899> word<00:32:18.139> and<00:32:18.409> put<00:32:18.590> them 00:32:18.700 --> 00:32:18.710 align:start position:0% one lock the only word and put them 00:32:18.710 --> 00:32:20.110 align:start position:0% one lock the only word and put them above<00:32:18.830> see<00:32:19.190> like<00:32:19.370> ten<00:32:19.519> million<00:32:19.700> guests<00:32:20.059> to 00:32:20.110 --> 00:32:20.120 align:start position:0% above see like ten million guests to 00:32:20.120 --> 00:32:24.549 align:start position:0% above see like ten million guests to play<00:32:20.269> with<00:32:20.450> and<00:32:20.990> so<00:32:21.169> you<00:32:21.259> can't<00:32:21.830> support<00:32:23.559> up 00:32:24.549 --> 00:32:24.559 align:start position:0% play with and so you can't support up 00:32:24.559 --> 00:32:27.159 align:start position:0% play with and so you can't support up bow<00:32:25.009> are<00:32:25.220> chains<00:32:25.549> that<00:32:25.879> some<00:32:26.179> to<00:32:26.539> you<00:32:26.960> can 00:32:27.159 --> 00:32:27.169 align:start position:0% bow are chains that some to you can 00:32:27.169 --> 00:32:29.259 align:start position:0% bow are chains that some to you can securely<00:32:27.500> support<00:32:27.889> or<00:32:28.100> the<00:32:28.730> some<00:32:28.940> of<00:32:29.090> the<00:32:29.179> or 00:32:29.259 --> 00:32:29.269 align:start position:0% securely support or the some of the or 00:32:29.269 --> 00:32:30.410 align:start position:0% securely support or the some of the or chains<00:32:29.570> that<00:32:29.750> some 00:32:30.410 --> 00:32:30.420 align:start position:0% chains that some 00:32:30.420 --> 00:32:32.330 align:start position:0% chains that some gasps<00:32:30.870> because<00:32:31.260> within<00:32:31.440> the<00:32:31.650> one<00:32:31.770> block<00:32:32.010> or<00:32:32.190> a 00:32:32.330 --> 00:32:32.340 align:start position:0% gasps because within the one block or a 00:32:32.340 --> 00:32:34.310 align:start position:0% gasps because within the one block or a period<00:32:32.610> of<00:32:32.670> everyone<00:32:33.030> was<00:32:33.270> fraudulent<00:32:34.260> you 00:32:34.310 --> 00:32:34.320 align:start position:0% period of everyone was fraudulent you 00:32:34.320 --> 00:32:36.650 align:start position:0% period of everyone was fraudulent you can<00:32:34.530> you<00:32:35.190> can<00:32:35.340> support<00:32:35.670> roll<00:32:35.910> backs<00:32:36.150> of<00:32:36.390> all<00:32:36.540> of 00:32:36.650 --> 00:32:36.660 align:start position:0% can you can support roll backs of all of 00:32:36.660 --> 00:32:38.450 align:start position:0% can you can support roll backs of all of them<00:32:36.810> so<00:32:37.050> you<00:32:37.290> can<00:32:37.530> extend<00:32:37.950> that<00:32:38.070> to<00:32:38.310> like 00:32:38.450 --> 00:32:38.460 align:start position:0% them so you can extend that to like 00:32:38.460 --> 00:32:42.200 align:start position:0% them so you can extend that to like think<00:32:38.850> about<00:32:39.060> the<00:32:39.210> week<00:32:39.420> long<00:32:40.050> of<00:32:40.290> those<00:32:40.860> I<00:32:41.220> I'm 00:32:42.200 --> 00:32:42.210 align:start position:0% think about the week long of those I I'm 00:32:42.210 --> 00:32:44.720 align:start position:0% think about the week long of those I I'm not<00:32:42.450> I'm<00:32:42.840> not<00:32:42.870> sure<00:32:43.080> if<00:32:43.500> I<00:32:43.590> understand<00:32:44.100> but<00:32:44.460> I 00:32:44.720 --> 00:32:44.730 align:start position:0% not I'm not sure if I understand but I 00:32:44.730 --> 00:32:47.810 align:start position:0% not I'm not sure if I understand but I don't<00:32:45.150> believe<00:32:46.020> that<00:32:46.410> we<00:32:46.560> have<00:32:46.980> this<00:32:47.190> problem 00:32:47.810 --> 00:32:47.820 align:start position:0% don't believe that we have this problem 00:32:47.820 --> 00:32:50.570 align:start position:0% don't believe that we have this problem because<00:32:48.240> you<00:32:48.870> like<00:32:49.440> even<00:32:49.710> are<00:32:50.010> you<00:32:50.340> saying 00:32:50.570 --> 00:32:50.580 align:start position:0% because you like even are you saying 00:32:50.580 --> 00:32:53.960 align:start position:0% because you like even are you saying like<00:32:50.780> if<00:32:51.780> this<00:32:52.050> is<00:32:52.260> invalid<00:32:52.770> right<00:32:52.980> like<00:32:53.610> the 00:32:53.960 --> 00:32:53.970 align:start position:0% like if this is invalid right like the 00:32:53.970 --> 00:32:55.610 align:start position:0% like if this is invalid right like the way<00:32:54.090> that<00:32:54.270> I<00:32:54.300> prove<00:32:54.630> it<00:32:54.720> is<00:32:54.930> I<00:32:55.050> just<00:32:55.110> prove<00:32:55.470> this 00:32:55.610 --> 00:32:55.620 align:start position:0% way that I prove it is I just prove this 00:32:55.620 --> 00:32:56.990 align:start position:0% way that I prove it is I just prove this is<00:32:55.800> invalid<00:32:56.190> and<00:32:56.340> then<00:32:56.430> I<00:32:56.490> just<00:32:56.670> delete 00:32:56.990 --> 00:32:57.000 align:start position:0% is invalid and then I just delete 00:32:57.000 --> 00:33:00.650 align:start position:0% is invalid and then I just delete everything<00:32:57.300> here<00:32:57.950> right<00:32:58.950> yeah<00:32:59.760> but<00:33:00.120> if<00:33:00.240> you<00:33:00.390> I 00:33:00.650 --> 00:33:00.660 align:start position:0% everything here right yeah but if you I 00:33:00.660 --> 00:33:02.150 align:start position:0% everything here right yeah but if you I know<00:33:00.960> you're<00:33:01.170> saying<00:33:01.410> you're<00:33:01.800> saying<00:33:01.830> that<00:33:02.040> if 00:33:02.150 --> 00:33:02.160 align:start position:0% know you're saying you're saying that if 00:33:02.160 --> 00:33:04.280 align:start position:0% know you're saying you're saying that if you<00:33:02.250> have<00:33:02.430> a<00:33:02.460> block<00:33:02.850> on<00:33:03.390> your<00:33:03.480> side<00:33:03.870> chain<00:33:04.170> that 00:33:04.280 --> 00:33:04.290 align:start position:0% you have a block on your side chain that 00:33:04.290 --> 00:33:06.140 align:start position:0% you have a block on your side chain that has<00:33:04.440> they<00:33:04.740> take<00:33:04.950> more<00:33:05.190> computation<00:33:05.880> you<00:33:06.000> can 00:33:06.140 --> 00:33:06.150 align:start position:0% has they take more computation you can 00:33:06.150 --> 00:33:08.590 align:start position:0% has they take more computation you can do<00:33:06.300> on<00:33:06.600> the<00:33:06.780> main<00:33:06.960> chain<00:33:07.230> of<00:33:07.470> those<00:33:07.680> whims 00:33:08.590 --> 00:33:08.600 align:start position:0% do on the main chain of those whims 00:33:08.600 --> 00:33:11.420 align:start position:0% do on the main chain of those whims nobody's<00:33:09.600> chump<00:33:10.500> change<00:33:10.860> that's<00:33:11.010> okay 00:33:11.420 --> 00:33:11.430 align:start position:0% nobody's chump change that's okay 00:33:11.430 --> 00:33:14.570 align:start position:0% nobody's chump change that's okay usually<00:33:12.420> think<00:33:12.630> you're<00:33:12.780> insecure<00:33:13.290> so<00:33:14.040> but 00:33:14.570 --> 00:33:14.580 align:start position:0% usually think you're insecure so but 00:33:14.580 --> 00:33:16.070 align:start position:0% usually think you're insecure so but then<00:33:14.730> there's<00:33:14.910> not<00:33:15.060> enough<00:33:15.300> gas<00:33:15.450> on<00:33:15.720> came<00:33:15.930> to 00:33:16.070 --> 00:33:16.080 align:start position:0% then there's not enough gas on came to 00:33:16.080 --> 00:33:18.890 align:start position:0% then there's not enough gas on came to Rio<00:33:16.290> over<00:33:16.590> time<00:33:16.890> so<00:33:17.580> you<00:33:17.610> can<00:33:17.970> solve<00:33:18.270> this<00:33:18.540> in 00:33:18.890 --> 00:33:18.900 align:start position:0% Rio over time so you can solve this in 00:33:18.900 --> 00:33:26.750 align:start position:0% Rio over time so you can solve this in two<00:33:19.170> ways<00:33:22.130> one<00:33:24.710> you<00:33:25.710> can<00:33:25.860> this<00:33:26.520> is<00:33:26.730> something 00:33:26.750 --> 00:33:26.760 align:start position:0% two ways one you can this is something 00:33:26.760 --> 00:33:28.400 align:start position:0% two ways one you can this is something to<00:33:27.030> change<00:33:27.270> the<00:33:27.420> design<00:33:27.570> they<00:33:27.930> can<00:33:28.080> have<00:33:28.230> like 00:33:28.400 --> 00:33:28.410 align:start position:0% to change the design they can have like 00:33:28.410 --> 00:33:31.210 align:start position:0% to change the design they can have like a<00:33:28.440> higher<00:33:28.770> bond<00:33:29.160> and<00:33:30.000> a<00:33:30.150> longer<00:33:30.420> time<00:33:31.050> period 00:33:31.210 --> 00:33:31.220 align:start position:0% a higher bond and a longer time period 00:33:31.220 --> 00:33:33.350 align:start position:0% a higher bond and a longer time period yeah<00:33:32.220> so<00:33:32.430> if<00:33:32.490> you<00:33:32.550> have<00:33:32.760> a<00:33:32.790> if<00:33:33.150> you<00:33:33.180> have<00:33:33.270> a 00:33:33.350 --> 00:33:33.360 align:start position:0% yeah so if you have a if you have a 00:33:33.360 --> 00:33:35.000 align:start position:0% yeah so if you have a if you have a bigger<00:33:33.630> bomb<00:33:33.930> you<00:33:34.170> need<00:33:34.350> to<00:33:34.410> have<00:33:34.530> a<00:33:34.560> shorter 00:33:35.000 --> 00:33:35.010 align:start position:0% bigger bomb you need to have a shorter 00:33:35.010 --> 00:33:37.130 align:start position:0% bigger bomb you need to have a shorter time<00:33:35.220> out<00:33:35.370> period<00:33:35.550> so<00:33:36.180> this<00:33:36.330> is<00:33:36.480> like<00:33:36.660> a<00:33:36.690> this 00:33:37.130 --> 00:33:37.140 align:start position:0% time out period so this is like a this 00:33:37.140 --> 00:33:39.710 align:start position:0% time out period so this is like a this is<00:33:37.200> like<00:33:37.700> we<00:33:38.700> can<00:33:38.850> solve<00:33:39.060> this<00:33:39.210> by<00:33:39.270> any 00:33:39.710 --> 00:33:39.720 align:start position:0% is like we can solve this by any 00:33:39.720 --> 00:33:41.960 align:start position:0% is like we can solve this by any variable<00:33:40.230> on<00:33:40.440> like<00:33:40.710> our<00:33:40.980> time<00:33:41.280> outside<00:33:41.490> and 00:33:41.960 --> 00:33:41.970 align:start position:0% variable on like our time outside and 00:33:41.970 --> 00:33:45.140 align:start position:0% variable on like our time outside and I'm<00:33:42.270> variable<00:33:42.870> pause<00:33:43.640> because<00:33:44.640> if<00:33:44.880> you<00:33:44.970> think 00:33:45.140 --> 00:33:45.150 align:start position:0% I'm variable pause because if you think 00:33:45.150 --> 00:33:47.240 align:start position:0% I'm variable pause because if you think about<00:33:45.240> it<00:33:45.480> I<00:33:45.600> get<00:33:45.870> more<00:33:46.080> money<00:33:46.350> if<00:33:46.770> I<00:33:46.950> slash 00:33:47.240 --> 00:33:47.250 align:start position:0% about it I get more money if I slash 00:33:47.250 --> 00:33:48.830 align:start position:0% about it I get more money if I slash someone<00:33:47.610> on<00:33:47.940> a<00:33:47.970> chain<00:33:48.240> that<00:33:48.360> it's<00:33:48.570> a<00:33:48.630> bigger 00:33:48.830 --> 00:33:48.840 align:start position:0% someone on a chain that it's a bigger 00:33:48.840 --> 00:33:49.400 align:start position:0% someone on a chain that it's a bigger reward 00:33:49.400 --> 00:33:49.410 align:start position:0% reward 00:33:49.410 --> 00:34:04.870 align:start position:0% reward so<00:33:50.070> I'm<00:33:50.190> if<00:34:01.520> you<00:34:02.520> have<00:34:02.930> sorry<00:34:03.930> you<00:34:04.290> have<00:34:04.410> like 00:34:04.870 --> 00:34:04.880 align:start position:0% so I'm if you have sorry you have like 00:34:04.880 --> 00:34:08.570 align:start position:0% so I'm if you have sorry you have like five<00:34:05.880> chains<00:34:06.270> they<00:34:07.140> all<00:34:07.260> have<00:34:07.500> they'd<00:34:08.399> all 00:34:08.570 --> 00:34:08.580 align:start position:0% five chains they all have they'd all 00:34:08.580 --> 00:34:10.820 align:start position:0% five chains they all have they'd all have<00:34:08.700> a<00:34:08.760> max<00:34:08.970> of<00:34:09.120> two<00:34:09.300> million<00:34:09.540> guests<00:34:09.929> and 00:34:10.820 --> 00:34:10.830 align:start position:0% have a max of two million guests and 00:34:10.830 --> 00:34:13.040 align:start position:0% have a max of two million guests and they<00:34:11.010> can<00:34:11.190> all<00:34:11.310> revert<00:34:11.669> like<00:34:12.000> them<00:34:12.390> they<00:34:12.899> have 00:34:13.040 --> 00:34:13.050 align:start position:0% they can all revert like them they have 00:34:13.050 --> 00:34:14.990 align:start position:0% they can all revert like them they have one<00:34:13.260> block<00:34:13.500> with<00:34:14.070> which<00:34:14.280> they<00:34:14.520> can<00:34:14.580> do<00:34:14.970> a 00:34:14.990 --> 00:34:15.000 align:start position:0% one block with which they can do a 00:34:15.000 --> 00:34:18.139 align:start position:0% one block with which they can do a challenge<00:34:15.270> record<00:34:16.190> so<00:34:17.190> that<00:34:17.220> they<00:34:17.880> can<00:34:18.030> all 00:34:18.139 --> 00:34:18.149 align:start position:0% challenge record so that they can all 00:34:18.149 --> 00:34:19.640 align:start position:0% challenge record so that they can all they<00:34:18.450> can<00:34:18.570> all<00:34:18.630> fit<00:34:18.840> to<00:34:18.929> that<00:34:18.960> block 00:34:19.640 --> 00:34:19.650 align:start position:0% they can all fit to that block 00:34:19.650 --> 00:34:21.230 align:start position:0% they can all fit to that block Shayne<00:34:19.860> and<00:34:19.890> like<00:34:20.190> do<00:34:20.370> their<00:34:20.490> efforts<00:34:20.820> but<00:34:21.090> if 00:34:21.230 --> 00:34:21.240 align:start position:0% Shayne and like do their efforts but if 00:34:21.240 --> 00:34:23.930 align:start position:0% Shayne and like do their efforts but if you<00:34:21.360> now<00:34:21.510> have<00:34:21.750> six<00:34:21.990> chains<00:34:22.260> often<00:34:22.950> I'll<00:34:23.550> chain 00:34:23.930 --> 00:34:23.940 align:start position:0% you now have six chains often I'll chain 00:34:23.940 --> 00:34:25.430 align:start position:0% you now have six chains often I'll chain and<00:34:24.150> then<00:34:24.270> now<00:34:24.510> it's<00:34:24.690> calming<00:34:25.080> and<00:34:25.230> you<00:34:25.320> have 00:34:25.430 --> 00:34:25.440 align:start position:0% and then now it's calming and you have 00:34:25.440 --> 00:34:27.170 align:start position:0% and then now it's calming and you have one<00:34:25.620> block<00:34:25.830> to<00:34:26.100> be<00:34:26.190> able<00:34:26.340> to<00:34:26.400> do<00:34:26.550> the<00:34:26.730> actual 00:34:27.170 --> 00:34:27.180 align:start position:0% one block to be able to do the actual 00:34:27.180 --> 00:34:28.880 align:start position:0% one block to be able to do the actual workers<00:34:27.630> and<00:34:27.930> usually<00:34:28.350> you'd<00:34:28.440> have<00:34:28.530> much<00:34:28.740> more 00:34:28.880 --> 00:34:28.890 align:start position:0% workers and usually you'd have much more 00:34:28.890 --> 00:34:30.760 align:start position:0% workers and usually you'd have much more time<00:34:29.100> period<00:34:29.370> so<00:34:29.790> it's<00:34:29.910> all<00:34:30.000> I<00:34:30.030> think<00:34:30.270> yeah 00:34:30.760 --> 00:34:30.770 align:start position:0% time period so it's all I think yeah 00:34:30.770 --> 00:34:33.140 align:start position:0% time period so it's all I think yeah yeah<00:34:31.800> yeah<00:34:32.160> you<00:34:32.220> guy<00:34:32.520> don't<00:34:32.640> think<00:34:32.910> you<00:34:32.970> can 00:34:33.140 --> 00:34:33.150 align:start position:0% yeah yeah you guy don't think you can 00:34:33.150 --> 00:34:35.390 align:start position:0% yeah yeah you guy don't think you can because<00:34:33.570> even<00:34:34.560> if<00:34:34.680> they're<00:34:34.800> all<00:34:34.950> submitting 00:34:35.390 --> 00:34:35.400 align:start position:0% because even if they're all submitting 00:34:35.400 --> 00:34:37.040 align:start position:0% because even if they're all submitting blocks<00:34:35.640> and<00:34:35.910> like<00:34:36.090> let's<00:34:36.300> say<00:34:36.450> they're<00:34:36.630> all<00:34:36.840> of 00:34:37.040 --> 00:34:37.050 align:start position:0% blocks and like let's say they're all of 00:34:37.050 --> 00:34:38.840 align:start position:0% blocks and like let's say they're all of the<00:34:37.200> invalid<00:34:37.560> blocks<00:34:37.980> are<00:34:38.160> progressing<00:34:38.640> like 00:34:38.840 --> 00:34:38.850 align:start position:0% the invalid blocks are progressing like 00:34:38.850 --> 00:34:41.180 align:start position:0% the invalid blocks are progressing like one<00:34:39.450> honest<00:34:39.870> user<00:34:40.110> is<00:34:40.410> going<00:34:40.590> to<00:34:40.710> eventually 00:34:41.180 --> 00:34:41.190 align:start position:0% one honest user is going to eventually 00:34:41.190 --> 00:34:43.850 align:start position:0% one honest user is going to eventually before<00:34:41.730> one<00:34:41.940> week<00:34:42.150> submit<00:34:42.660> one<00:34:43.020> transaction 00:34:43.850 --> 00:34:43.860 align:start position:0% before one week submit one transaction 00:34:43.860 --> 00:34:46.160 align:start position:0% before one week submit one transaction to<00:34:44.130> delete<00:34:44.460> all<00:34:44.640> of<00:34:44.970> those<00:34:45.120> blocks<00:34:45.390> in<00:34:45.750> Ivanka 00:34:46.160 --> 00:34:46.170 align:start position:0% to delete all of those blocks in Ivanka 00:34:46.170 --> 00:34:47.450 align:start position:0% to delete all of those blocks in Ivanka know<00:34:46.380> Cal<00:34:46.590> he<00:34:46.740> has<00:34:46.830> like<00:34:46.980> a<00:34:47.010> hundred<00:34:47.190> five 00:34:47.450 --> 00:34:47.460 align:start position:0% know Cal he has like a hundred five 00:34:47.460 --> 00:34:49.310 align:start position:0% know Cal he has like a hundred five example<00:34:48.030> where<00:34:48.210> there's<00:34:48.390> like<00:34:48.600> one<00:34:48.840> day<00:34:49.020> and 00:34:49.310 --> 00:34:49.320 align:start position:0% example where there's like one day and 00:34:49.320 --> 00:34:52.670 align:start position:0% example where there's like one day and this<00:34:49.410> is<00:34:50.510> enough<00:34:51.510> time<00:34:51.690> I<00:34:51.750> get<00:34:51.990> it<00:34:52.140> he's<00:34:52.530> given 00:34:52.670 --> 00:34:52.680 align:start position:0% this is enough time I get it he's given 00:34:52.680 --> 00:34:55.040 align:start position:0% this is enough time I get it he's given the<00:34:52.860> example<00:34:53.190> of<00:34:53.280> hi<00:34:53.670> every<00:34:54.150> not<00:34:54.330> okay<00:34:54.540> I<00:34:54.720> see 00:34:55.040 --> 00:34:55.050 align:start position:0% the example of hi every not okay I see 00:34:55.050 --> 00:34:58.010 align:start position:0% the example of hi every not okay I see is<00:34:55.200> open<00:34:56.190> so<00:34:56.370> that's<00:34:57.090> definitely<00:34:57.420> okay<00:34:57.960> so 00:34:58.010 --> 00:34:58.020 align:start position:0% is open so that's definitely okay so 00:34:58.020 --> 00:34:59.870 align:start position:0% is open so that's definitely okay so there's<00:34:58.680> probably<00:34:58.950> within<00:34:59.550> that<00:34:59.670> week 00:34:59.870 --> 00:34:59.880 align:start position:0% there's probably within that week 00:34:59.880 --> 00:35:02.240 align:start position:0% there's probably within that week there's<00:35:00.120> also<00:35:00.300> a<00:35:00.480> maximum<00:35:01.020> I<00:35:01.470> said<00:35:01.830> maximum 00:35:02.240 --> 00:35:02.250 align:start position:0% there's also a maximum I said maximum 00:35:02.250 --> 00:35:04.010 align:start position:0% there's also a maximum I said maximum number<00:35:02.430> of<00:35:02.460> her<00:35:02.670> teaching<00:35:03.000> support<00:35:03.390> thus<00:35:03.750> a 00:35:04.010 --> 00:35:04.020 align:start position:0% number of her teaching support thus a 00:35:04.020 --> 00:35:08.480 align:start position:0% number of her teaching support thus a maximum<00:35:04.530> number<00:35:04.920> of<00:35:04.950> changing<00:35:06.980> all<00:35:07.980> the<00:35:08.040> hail 00:35:08.480 --> 00:35:08.490 align:start position:0% maximum number of changing all the hail 00:35:08.490 --> 00:35:14.440 align:start position:0% maximum number of changing all the hail the<00:35:08.820> one<00:35:09.060> optimistic<00:35:09.600> role<00:35:10.050> of<00:35:10.230> chain<00:35:10.500> I<00:35:12.620> think 00:35:14.440 --> 00:35:14.450 align:start position:0% the one optimistic role of chain I think 00:35:14.450 --> 00:35:16.610 align:start position:0% the one optimistic role of chain I think premature<00:35:15.450> ization<00:35:15.720> bullet<00:35:16.110> will<00:35:16.260> help<00:35:16.410> here 00:35:16.610 --> 00:35:16.620 align:start position:0% premature ization bullet will help here 00:35:16.620 --> 00:35:18.740 align:start position:0% premature ization bullet will help here I<00:35:16.830> think<00:35:17.490> I<00:35:17.670> think<00:35:18.030> during<00:35:18.360> this<00:35:18.480> conversation 00:35:18.740 --> 00:35:18.750 align:start position:0% I think I think during this conversation 00:35:18.750 --> 00:35:22.880 align:start position:0% I think I think during this conversation two<00:35:19.380> important<00:35:19.830> things<00:35:19.860> came<00:35:20.310> up<00:35:21.890> the 00:35:22.880 --> 00:35:22.890 align:start position:0% two important things came up the 00:35:22.890 --> 00:35:26.030 align:start position:0% two important things came up the guarantees<00:35:23.580> that<00:35:24.150> are<00:35:24.540> useful<00:35:24.810> for<00:35:25.440> for<00:35:25.890> these 00:35:26.030 --> 00:35:26.040 align:start position:0% guarantees that are useful for for these 00:35:26.040 --> 00:35:28.250 align:start position:0% guarantees that are useful for for these kind<00:35:26.370> of<00:35:26.400> set<00:35:26.640> ups<00:35:26.820> and<00:35:27.090> then<00:35:27.630> base<00:35:27.990> one 00:35:28.250 --> 00:35:28.260 align:start position:0% kind of set ups and then base one 00:35:28.260 --> 00:35:30.380 align:start position:0% kind of set ups and then base one numbers<00:35:28.680> is<00:35:29.310> first<00:35:29.610> of<00:35:29.790> all<00:35:29.910> that<00:35:30.090> you<00:35:30.150> can<00:35:30.240> get 00:35:30.380 --> 00:35:30.390 align:start position:0% numbers is first of all that you can get 00:35:30.390 --> 00:35:32.720 align:start position:0% numbers is first of all that you can get a<00:35:30.420> deterministic<00:35:31.260> ordering<00:35:31.740> of<00:35:31.860> blocks<00:35:32.130> right 00:35:32.720 --> 00:35:32.730 align:start position:0% a deterministic ordering of blocks right 00:35:32.730 --> 00:35:35.330 align:start position:0% a deterministic ordering of blocks right and<00:35:33.240> all<00:35:34.170> the<00:35:34.230> computation<00:35:35.040> of<00:35:35.160> this 00:35:35.330 --> 00:35:35.340 align:start position:0% and all the computation of this 00:35:35.340 --> 00:35:37.820 align:start position:0% and all the computation of this opportunity<00:35:36.090> but<00:35:36.390> but<00:35:36.630> that's<00:35:36.780> what<00:35:36.990> the 00:35:37.820 --> 00:35:37.830 align:start position:0% opportunity but but that's what the 00:35:37.830 --> 00:35:39.890 align:start position:0% opportunity but but that's what the critical<00:35:38.310> feature<00:35:38.550> that<00:35:38.850> phase<00:35:39.180> one<00:35:39.420> offers 00:35:39.890 --> 00:35:39.900 align:start position:0% critical feature that phase one offers 00:35:39.900 --> 00:35:43.100 align:start position:0% critical feature that phase one offers to<00:35:40.710> in<00:35:40.890> terms<00:35:41.160> of<00:35:41.540> if<00:35:42.540> you<00:35:42.660> want<00:35:42.840> to<00:35:42.930> develop 00:35:43.100 --> 00:35:43.110 align:start position:0% to in terms of if you want to develop 00:35:43.110 --> 00:35:44.810 align:start position:0% to in terms of if you want to develop your<00:35:43.320> own<00:35:43.440> application<00:35:44.130> this<00:35:44.280> is<00:35:44.400> like<00:35:44.550> one<00:35:44.790> of 00:35:44.810 --> 00:35:44.820 align:start position:0% your own application this is like one of 00:35:44.820 --> 00:35:46.580 align:start position:0% your own application this is like one of the<00:35:45.030> guarantees<00:35:45.480> that<00:35:45.510> you<00:35:45.900> suddenly<00:35:46.140> gain 00:35:46.580 --> 00:35:46.590 align:start position:0% the guarantees that you suddenly gain 00:35:46.590 --> 00:35:50.510 align:start position:0% the guarantees that you suddenly gain now<00:35:46.830> and<00:35:48.080> then<00:35:49.080> if<00:35:49.890> they're<00:35:50.100> in<00:35:50.190> one<00:35:50.340> already 00:35:50.510 --> 00:35:50.520 align:start position:0% now and then if they're in one already 00:35:50.520 --> 00:35:53.570 align:start position:0% now and then if they're in one already has<00:35:50.880> that<00:35:51.060> obviously<00:35:51.780> but<00:35:52.440> the<00:35:53.160> second 00:35:53.570 --> 00:35:53.580 align:start position:0% has that obviously but the second 00:35:53.580 --> 00:35:55.970 align:start position:0% has that obviously but the second feature<00:35:53.760> that<00:35:54.300> we<00:35:54.450> gain<00:35:54.660> here<00:35:54.960> that<00:35:55.740> it<00:35:55.860> was 00:35:55.970 --> 00:35:55.980 align:start position:0% feature that we gain here that it was 00:35:55.980 --> 00:35:58.640 align:start position:0% feature that we gain here that it was alluding<00:35:56.370> to<00:35:56.400> is<00:35:56.640> increased<00:35:57.060> bandwidth<00:35:57.650> right 00:35:58.640 --> 00:35:58.650 align:start position:0% alluding to is increased bandwidth right 00:35:58.650 --> 00:36:02.870 align:start position:0% alluding to is increased bandwidth right so<00:35:58.980> they're<00:35:59.550> suddenly<00:36:00.350> 64<00:36:01.350> or<00:36:01.890> thousand 00:36:02.870 --> 00:36:02.880 align:start position:0% so they're suddenly 64 or thousand 00:36:02.880 --> 00:36:06.830 align:start position:0% so they're suddenly 64 or thousand charts<00:36:04.670> that<00:36:05.670> you<00:36:05.790> can<00:36:05.970> submit<00:36:06.210> front<00:36:06.600> proofs 00:36:06.830 --> 00:36:06.840 align:start position:0% charts that you can submit front proofs 00:36:06.840 --> 00:36:09.980 align:start position:0% charts that you can submit front proofs for<00:36:07.050> example<00:36:07.500> so<00:36:08.010> you're<00:36:08.130> not<00:36:08.340> as<00:36:08.720> likely<00:36:09.720> to 00:36:09.980 --> 00:36:09.990 align:start position:0% for example so you're not as likely to 00:36:09.990 --> 00:36:12.780 align:start position:0% for example so you're not as likely to end<00:36:10.920> up<00:36:11.040> will<00:36:11.220> start<00:36:11.610> change 00:36:12.780 --> 00:36:12.790 align:start position:0% end up will start change 00:36:12.790 --> 00:36:16.500 align:start position:0% end up will start change right<00:36:13.410> I'll<00:36:14.410> just<00:36:14.650> be<00:36:15.390> highlighting<00:36:16.390> these 00:36:16.500 --> 00:36:16.510 align:start position:0% right I'll just be highlighting these 00:36:16.510 --> 00:36:27.200 align:start position:0% right I'll just be highlighting these little<00:36:16.840> points<00:36:17.800> along<00:36:18.160> the<00:36:18.340> way<00:36:18.370> like<00:36:19.920> what 00:36:27.200 --> 00:36:27.210 align:start position:0% 00:36:27.210 --> 00:36:45.180 align:start position:0% the<00:36:41.310> two<00:36:43.290> things<00:36:44.290> that<00:36:44.410> they<00:36:44.710> are<00:36:44.830> worried 00:36:45.180 --> 00:36:45.190 align:start position:0% the two things that they are worried 00:36:45.190 --> 00:36:48.000 align:start position:0% the two things that they are worried about<00:36:45.280> the<00:36:45.790> first<00:36:46.000> one<00:36:46.180> is<00:36:46.920> it's<00:36:47.920> not 00:36:48.000 --> 00:36:48.010 align:start position:0% about the first one is it's not 00:36:48.010 --> 00:36:50.460 align:start position:0% about the first one is it's not decentralized<00:36:48.730> enough<00:36:49.000> and<00:36:49.570> the<00:36:50.140> thing<00:36:50.320> is 00:36:50.460 --> 00:36:50.470 align:start position:0% decentralized enough and the thing is 00:36:50.470 --> 00:36:54.090 align:start position:0% decentralized enough and the thing is they<00:36:50.710> don't<00:36:50.860> see<00:36:50.980> it<00:36:51.760> is<00:36:51.940> not<00:36:52.150> security<00:36:53.100> and 00:36:54.090 --> 00:36:54.100 align:start position:0% they don't see it is not security and 00:36:54.100 --> 00:37:05.630 align:start position:0% they don't see it is not security and what<00:36:54.970> you<00:36:55.120> feel<00:36:55.480> about<00:36:57.150> about<00:36:58.150> the<00:36:58.480> security 00:37:05.630 --> 00:37:05.640 align:start position:0% 00:37:05.640 --> 00:37:09.030 align:start position:0% so<00:37:06.640> I<00:37:06.670> think<00:37:07.000> that<00:37:07.390> like<00:37:07.650> what<00:37:08.650> time<00:37:08.800> is 00:37:09.030 --> 00:37:09.040 align:start position:0% so I think that like what time is 00:37:09.040 --> 00:37:10.740 align:start position:0% so I think that like what time is getting<00:37:09.190> on<00:37:09.370> is<00:37:09.550> is<00:37:09.790> kind<00:37:10.000> of<00:37:10.030> close<00:37:10.300> to<00:37:10.480> a<00:37:10.540> nice 00:37:10.740 --> 00:37:10.750 align:start position:0% getting on is is kind of close to a nice 00:37:10.750 --> 00:37:12.690 align:start position:0% getting on is is kind of close to a nice differencing<00:37:11.380> in<00:37:11.470> fact<00:37:11.650> of<00:37:11.800> imaging<00:37:12.310> systems 00:37:12.690 --> 00:37:12.700 align:start position:0% differencing in fact of imaging systems 00:37:12.700 --> 00:37:15.780 align:start position:0% differencing in fact of imaging systems so<00:37:13.330> it's<00:37:13.690> quick<00:37:13.900> detail<00:37:14.470> although<00:37:14.680> you<00:37:15.400> fail 00:37:15.780 --> 00:37:15.790 align:start position:0% so it's quick detail although you fail 00:37:15.790 --> 00:37:18.270 align:start position:0% so it's quick detail although you fail when<00:37:16.630> when<00:37:16.840> you<00:37:16.930> have<00:37:17.080> too<00:37:17.350> many<00:37:17.530> transactions 00:37:18.270 --> 00:37:18.280 align:start position:0% when when you have too many transactions 00:37:18.280 --> 00:37:20.520 align:start position:0% when when you have too many transactions when<00:37:18.700> you<00:37:18.790> have<00:37:18.910> too<00:37:19.030> much<00:37:19.180> throughput<00:37:19.660> you 00:37:20.520 --> 00:37:20.530 align:start position:0% when you have too much throughput you 00:37:20.530 --> 00:37:23.730 align:start position:0% when you have too much throughput you just<00:37:21.520> can't<00:37:21.790> put<00:37:21.940> any<00:37:22.150> more<00:37:22.240> but<00:37:23.170> with<00:37:23.350> alpha 00:37:23.730 --> 00:37:23.740 align:start position:0% just can't put any more but with alpha 00:37:23.740 --> 00:37:26.040 align:start position:0% just can't put any more but with alpha is<00:37:23.860> equal<00:37:24.190> of<00:37:24.340> if<00:37:24.520> you<00:37:24.640> have<00:37:24.820> too<00:37:25.120> much<00:37:25.360> through 00:37:26.040 --> 00:37:26.050 align:start position:0% is equal of if you have too much through 00:37:26.050 --> 00:37:29.100 align:start position:0% is equal of if you have too much through but<00:37:26.260> then<00:37:27.040> you<00:37:27.220> have<00:37:27.400> this<00:37:27.520> kind<00:37:27.820> of<00:37:28.110> situation 00:37:29.100 --> 00:37:29.110 align:start position:0% but then you have this kind of situation 00:37:29.110 --> 00:37:31.710 align:start position:0% but then you have this kind of situation like<00:37:29.680> you<00:37:29.800> were<00:37:29.920> describing<00:37:30.420> where<00:37:31.420> you<00:37:31.540> don't 00:37:31.710 --> 00:37:31.720 align:start position:0% like you were describing where you don't 00:37:31.720 --> 00:37:33.630 align:start position:0% like you were describing where you don't have<00:37:31.840> enough<00:37:31.900> you<00:37:32.500> don't<00:37:33.010> have<00:37:33.160> enough<00:37:33.400> blog 00:37:33.630 --> 00:37:33.640 align:start position:0% have enough you don't have enough blog 00:37:33.640 --> 00:37:36.270 align:start position:0% have enough you don't have enough blog space<00:37:33.960> but<00:37:34.960> instead<00:37:35.350> of<00:37:35.410> just<00:37:35.740> not<00:37:35.950> being<00:37:35.980> able 00:37:36.270 --> 00:37:36.280 align:start position:0% space but instead of just not being able 00:37:36.280 --> 00:37:37.710 align:start position:0% space but instead of just not being able to<00:37:36.400> fill<00:37:36.640> it<00:37:36.760> all<00:37:36.850> you<00:37:37.090> have<00:37:37.300> this<00:37:37.420> kind<00:37:37.630> of 00:37:37.710 --> 00:37:37.720 align:start position:0% to fill it all you have this kind of 00:37:37.720 --> 00:37:39.750 align:start position:0% to fill it all you have this kind of weird<00:37:37.840> condition<00:37:38.530> where<00:37:38.770> someone<00:37:39.550> might<00:37:39.700> be 00:37:39.750 --> 00:37:39.760 align:start position:0% weird condition where someone might be 00:37:39.760 --> 00:37:40.980 align:start position:0% weird condition where someone might be able<00:37:40.030> to<00:37:40.150> attack<00:37:40.480> if<00:37:40.690> it's<00:37:40.840> like<00:37:40.960> a 00:37:40.980 --> 00:37:40.990 align:start position:0% able to attack if it's like a 00:37:40.990 --> 00:37:44.370 align:start position:0% able to attack if it's like a coordinated<00:37:41.830> attack<00:37:41.950> against<00:37:42.790> every<00:37:43.510> every 00:37:44.370 --> 00:37:44.380 align:start position:0% coordinated attack against every every 00:37:44.380 --> 00:37:46.140 align:start position:0% coordinated attack against every every every<00:37:44.950> often<00:37:45.250> is 00:37:46.140 --> 00:37:46.150 align:start position:0% every often is 00:37:46.150 --> 00:37:48.720 align:start position:0% every often is however<00:37:46.870> I<00:37:46.930> think<00:37:47.020> that<00:37:47.320> the<00:37:47.620> economics<00:37:48.580> of 00:37:48.720 --> 00:37:48.730 align:start position:0% however I think that the economics of 00:37:48.730 --> 00:37:52.530 align:start position:0% however I think that the economics of running<00:37:48.970> that<00:37:49.240> attack<00:37:49.510> could<00:37:49.660> be<00:37:49.870> the<00:37:51.390> kind<00:37:52.390> of 00:37:52.530 --> 00:37:52.540 align:start position:0% running that attack could be the kind of 00:37:52.540 --> 00:37:54.780 align:start position:0% running that attack could be the kind of it's<00:37:52.810> expensive<00:37:53.200> because<00:37:54.100> you<00:37:54.310> have<00:37:54.460> to<00:37:54.580> burn 00:37:54.780 --> 00:37:54.790 align:start position:0% it's expensive because you have to burn 00:37:54.790 --> 00:37:56.610 align:start position:0% it's expensive because you have to burn on<00:37:55.090> all<00:37:55.300> but<00:37:55.540> one<00:37:55.720> chain<00:37:55.930> and<00:37:55.960> you<00:37:56.290> could<00:37:56.440> you 00:37:56.610 --> 00:37:56.620 align:start position:0% on all but one chain and you could you 00:37:56.620 --> 00:37:58.080 align:start position:0% on all but one chain and you could you can<00:37:56.770> attack<00:37:57.010> one<00:37:57.280> chain<00:37:57.490> and<00:37:57.520> you<00:37:57.790> have<00:37:58.000> to 00:37:58.080 --> 00:37:58.090 align:start position:0% can attack one chain and you have to 00:37:58.090 --> 00:38:00.570 align:start position:0% can attack one chain and you have to burn<00:37:58.240> all<00:37:58.600> the<00:37:58.780> one<00:37:58.990> so<00:37:59.710> it<00:38:00.130> depends<00:38:00.460> on<00:38:00.520> the 00:38:00.570 --> 00:38:00.580 align:start position:0% burn all the one so it depends on the 00:38:00.580 --> 00:38:01.890 align:start position:0% burn all the one so it depends on the size<00:38:00.850> of<00:38:00.880> the<00:38:01.150> problems<00:38:01.420> that<00:38:01.450> you<00:38:01.660> have<00:38:01.690> and 00:38:01.890 --> 00:38:01.900 align:start position:0% size of the problems that you have and 00:38:01.900 --> 00:38:07.950 align:start position:0% size of the problems that you have and the<00:38:02.170> time<00:38:02.350> periods<00:38:04.230> when<00:38:05.230> I'm<00:38:05.350> done<00:38:05.560> okay<00:38:06.960> one 00:38:07.950 --> 00:38:07.960 align:start position:0% the time periods when I'm done okay one 00:38:07.960 --> 00:38:09.990 align:start position:0% the time periods when I'm done okay one I<00:38:08.170> think<00:38:08.500> that<00:38:08.680> generally<00:38:09.280> people<00:38:09.310> who<00:38:09.760> say 00:38:09.990 --> 00:38:10.000 align:start position:0% I think that generally people who say 00:38:10.000 --> 00:38:12.060 align:start position:0% I think that generally people who say this<00:38:10.300> is<00:38:10.360> a<00:38:10.540> great<00:38:10.780> layer<00:38:10.990> to<00:38:11.350> a<00:38:11.560> lot<00:38:11.830> of<00:38:11.980> the 00:38:12.060 --> 00:38:12.070 align:start position:0% this is a great layer to a lot of the 00:38:12.070 --> 00:38:14.790 align:start position:0% this is a great layer to a lot of the times<00:38:12.340> are<00:38:12.790> not<00:38:12.940> really<00:38:13.390> like<00:38:14.050> telling<00:38:14.680> you 00:38:14.790 --> 00:38:14.800 align:start position:0% times are not really like telling you 00:38:14.800 --> 00:38:16.530 align:start position:0% times are not really like telling you about<00:38:14.950> a<00:38:15.100> secure<00:38:15.520> protocol<00:38:15.970> and<00:38:16.240> so<00:38:16.420> I<00:38:16.450> think 00:38:16.530 --> 00:38:16.540 align:start position:0% about a secure protocol and so I think 00:38:16.540 --> 00:38:18.480 align:start position:0% about a secure protocol and so I think that<00:38:16.810> it's<00:38:16.960> a<00:38:17.050> very<00:38:17.080> well<00:38:17.410> founded<00:38:18.040> kind<00:38:18.340> of 00:38:18.480 --> 00:38:18.490 align:start position:0% that it's a very well founded kind of 00:38:18.490 --> 00:38:20.610 align:start position:0% that it's a very well founded kind of you<00:38:18.880> know<00:38:19.000> fear<00:38:19.420> it's<00:38:19.690> like<00:38:19.870> oh<00:38:20.050> this<00:38:20.410> is<00:38:20.590> a 00:38:20.610 --> 00:38:20.620 align:start position:0% you know fear it's like oh this is a 00:38:20.620 --> 00:38:22.470 align:start position:0% you know fear it's like oh this is a great<00:38:20.890> layer<00:38:21.070> -<00:38:21.310> it's<00:38:21.490> totally<00:38:21.700> secure<00:38:22.240> and 00:38:22.470 --> 00:38:22.480 align:start position:0% great layer - it's totally secure and 00:38:22.480 --> 00:38:24.060 align:start position:0% great layer - it's totally secure and they're<00:38:22.720> just<00:38:22.900> kind<00:38:23.110> of<00:38:23.170> like<00:38:23.230> you<00:38:24.040> know 00:38:24.060 --> 00:38:24.070 align:start position:0% they're just kind of like you know 00:38:24.070 --> 00:38:26.340 align:start position:0% they're just kind of like you know hand-waving<00:38:24.700> half<00:38:25.060> the<00:38:25.360> design<00:38:25.780> space<00:38:26.050> so<00:38:26.320> I 00:38:26.340 --> 00:38:26.350 align:start position:0% hand-waving half the design space so I 00:38:26.350 --> 00:38:27.840 align:start position:0% hand-waving half the design space so I think<00:38:26.590> that<00:38:26.710> that<00:38:26.860> is<00:38:27.070> absolutely<00:38:27.280> correct 00:38:27.840 --> 00:38:27.850 align:start position:0% think that that is absolutely correct 00:38:27.850 --> 00:38:31.770 align:start position:0% think that that is absolutely correct and<00:38:28.210> I<00:38:28.990> also<00:38:29.860> don't<00:38:30.280> think<00:38:30.430> that<00:38:30.670> this<00:38:31.120> be<00:38:31.390> kind 00:38:31.770 --> 00:38:31.780 align:start position:0% and I also don't think that this be kind 00:38:31.780 --> 00:38:35.880 align:start position:0% and I also don't think that this be kind of<00:38:31.900> like<00:38:32.310> block<00:38:33.900> congestion<00:38:34.900> problem<00:38:35.620> for 00:38:35.880 --> 00:38:35.890 align:start position:0% of like block congestion problem for 00:38:35.890 --> 00:38:37.500 align:start position:0% of like block congestion problem for generally<00:38:36.430> layer<00:38:36.640> two<00:38:36.880> because<00:38:37.120> this<00:38:37.270> is<00:38:37.390> a 00:38:37.500 --> 00:38:37.510 align:start position:0% generally layer two because this is a 00:38:37.510 --> 00:38:39.450 align:start position:0% generally layer two because this is a problem<00:38:37.720> of<00:38:37.930> you<00:38:38.170> know<00:38:38.200> state<00:38:38.590> channels<00:38:39.100> of 00:38:39.450 --> 00:38:39.460 align:start position:0% problem of you know state channels of 00:38:39.460 --> 00:38:41.160 align:start position:0% problem of you know state channels of every<00:38:39.850> layer<00:38:40.180> -<00:38:40.420> that's<00:38:40.660> based<00:38:40.870> on<00:38:41.050> the 00:38:41.160 --> 00:38:41.170 align:start position:0% every layer - that's based on the 00:38:41.170 --> 00:38:43.710 align:start position:0% every layer - that's based on the dispute<00:38:41.830> period<00:38:42.130> if<00:38:42.460> you<00:38:42.610> you<00:38:43.300> know<00:38:43.420> fill<00:38:43.630> up 00:38:43.710 --> 00:38:43.720 align:start position:0% dispute period if you you know fill up 00:38:43.720 --> 00:38:45.450 align:start position:0% dispute period if you you know fill up the<00:38:43.840> blocks<00:38:44.080> then<00:38:44.500> you're<00:38:44.740> then<00:38:45.070> you're<00:38:45.250> kind 00:38:45.450 --> 00:38:45.460 align:start position:0% the blocks then you're then you're kind 00:38:45.460 --> 00:38:47.550 align:start position:0% the blocks then you're then you're kind of<00:38:45.580> out<00:38:45.640> of<00:38:45.790> luck<00:38:45.940> however<00:38:46.540> I<00:38:46.990> want<00:38:47.320> to<00:38:47.410> just 00:38:47.550 --> 00:38:47.560 align:start position:0% of out of luck however I want to just 00:38:47.560 --> 00:38:49.110 align:start position:0% of out of luck however I want to just really<00:38:47.890> really<00:38:48.100> quickly<00:38:48.310> talk<00:38:48.730> about<00:38:48.760> the 00:38:49.110 --> 00:38:49.120 align:start position:0% really really quickly talk about the 00:38:49.120 --> 00:38:51.330 align:start position:0% really really quickly talk about the kind<00:38:49.540> of<00:38:49.570> asymmetry<00:38:49.900> and<00:38:50.620> the<00:38:50.710> attack/defense 00:38:51.330 --> 00:38:51.340 align:start position:0% kind of asymmetry and the attack/defense 00:38:51.340 --> 00:38:53.850 align:start position:0% kind of asymmetry and the attack/defense scheme<00:38:51.670> here<00:38:51.970> that<00:38:52.210> that<00:38:52.450> makes<00:38:52.750> this<00:38:53.290> dispute 00:38:53.850 --> 00:38:53.860 align:start position:0% scheme here that that makes this dispute 00:38:53.860 --> 00:38:57.990 align:start position:0% scheme here that that makes this dispute you<00:38:54.130> know<00:38:54.250> this<00:38:55.030> is<00:38:55.330> a<00:38:56.310> dispute<00:38:57.310> like 00:38:57.990 --> 00:38:58.000 align:start position:0% you know this is a dispute like 00:38:58.000 --> 00:39:01.080 align:start position:0% you know this is a dispute like censorship<00:38:58.840> problem<00:38:59.800> really<00:39:00.160> really<00:39:00.520> hard<00:39:00.820> to 00:39:01.080 --> 00:39:01.090 align:start position:0% censorship problem really really hard to 00:39:01.090 --> 00:39:04.980 align:start position:0% censorship problem really really hard to to<00:39:01.450> achieve<00:39:01.980> so<00:39:02.980> if<00:39:03.070> I<00:39:03.250> have<00:39:03.580> some<00:39:04.210> value<00:39:04.750> of 00:39:04.980 --> 00:39:04.990 align:start position:0% to achieve so if I have some value of 00:39:04.990 --> 00:39:07.890 align:start position:0% to achieve so if I have some value of you<00:39:05.620> know<00:39:05.650> let's<00:39:06.010> say<00:39:06.220> you<00:39:06.880> know<00:39:07.000> a<00:39:07.180> thousand 00:39:07.890 --> 00:39:07.900 align:start position:0% you know let's say you know a thousand 00:39:07.900 --> 00:39:10.620 align:start position:0% you know let's say you know a thousand right<00:39:08.590> that's<00:39:09.070> locked<00:39:09.430> up<00:39:09.640> in<00:39:09.790> a<00:39:09.880> dispute<00:39:10.330> that 00:39:10.620 --> 00:39:10.630 align:start position:0% right that's locked up in a dispute that 00:39:10.630 --> 00:39:12.170 align:start position:0% right that's locked up in a dispute that I'm<00:39:10.780> go<00:39:10.990> up<00:39:11.050> then<00:39:11.200> I'm<00:39:11.350> scared<00:39:11.830> of<00:39:11.950> losing 00:39:12.170 --> 00:39:12.180 align:start position:0% I'm go up then I'm scared of losing 00:39:12.180 --> 00:39:15.060 align:start position:0% I'm go up then I'm scared of losing right<00:39:13.180> then<00:39:13.630> I<00:39:13.840> will<00:39:14.110> like<00:39:14.260> to<00:39:14.410> sending<00:39:14.830> a 00:39:15.060 --> 00:39:15.070 align:start position:0% right then I will like to sending a 00:39:15.070 --> 00:39:17.460 align:start position:0% right then I will like to sending a transaction<00:39:15.820> and<00:39:16.480> like<00:39:16.930> aetherium 00:39:17.460 --> 00:39:17.470 align:start position:0% transaction and like aetherium 00:39:17.470 --> 00:39:20.170 align:start position:0% transaction and like aetherium transaction<00:39:18.040> that<00:39:18.490> pays<00:39:18.730> like<00:39:18.970> 99 00:39:20.170 --> 00:39:20.180 align:start position:0% transaction that pays like 99 00:39:20.180 --> 00:39:24.700 align:start position:0% transaction that pays like 99 you<00:39:20.329> know<00:39:20.450> like<00:39:21.170> contrived<00:39:21.890> but<00:39:22.220> 999<00:39:23.289> gas<00:39:24.289> to 00:39:24.700 --> 00:39:24.710 align:start position:0% you know like contrived but 999 gas to 00:39:24.710 --> 00:39:26.440 align:start position:0% you know like contrived but 999 gas to get<00:39:24.890> it<00:39:25.039> out<00:39:25.160> right<00:39:25.430> I'm<00:39:25.819> willing<00:39:26.180> to<00:39:26.210> burn<00:39:26.420> a 00:39:26.440 --> 00:39:26.450 align:start position:0% get it out right I'm willing to burn a 00:39:26.450 --> 00:39:29.319 align:start position:0% get it out right I'm willing to burn a lot<00:39:26.839> of<00:39:26.900> money<00:39:27.230> to<00:39:27.920> you<00:39:28.369> know<00:39:28.400> kind<00:39:29.000> of<00:39:29.059> save 00:39:29.319 --> 00:39:29.329 align:start position:0% lot of money to you know kind of save 00:39:29.329 --> 00:39:30.490 align:start position:0% lot of money to you know kind of save this<00:39:29.510> because<00:39:29.809> I'll<00:39:29.930> be<00:39:30.079> making<00:39:30.319> a<00:39:30.380> profit 00:39:30.490 --> 00:39:30.500 align:start position:0% this because I'll be making a profit 00:39:30.500 --> 00:39:32.740 align:start position:0% this because I'll be making a profit otherwise<00:39:30.920> I'm<00:39:31.099> going<00:39:31.190> to<00:39:31.250> lose<00:39:31.309> it<00:39:31.579> so<00:39:31.609> I<00:39:31.750> am 00:39:32.740 --> 00:39:32.750 align:start position:0% otherwise I'm going to lose it so I am 00:39:32.750 --> 00:39:34.809 align:start position:0% otherwise I'm going to lose it so I am trying<00:39:33.020> to<00:39:33.079> get<00:39:33.200> out<00:39:33.410> one<00:39:33.619> dollar<00:39:33.859> but<00:39:34.700> an 00:39:34.809 --> 00:39:34.819 align:start position:0% trying to get out one dollar but an 00:39:34.819 --> 00:39:37.359 align:start position:0% trying to get out one dollar but an attacker<00:39:35.150> has<00:39:36.020> to<00:39:36.230> fill<00:39:36.440> up<00:39:36.559> all<00:39:36.710> the<00:39:37.069> blocks 00:39:37.359 --> 00:39:37.369 align:start position:0% attacker has to fill up all the blocks 00:39:37.369 --> 00:39:40.510 align:start position:0% attacker has to fill up all the blocks right<00:39:37.930> for<00:39:38.930> some<00:39:39.410> time<00:39:39.650> period<00:39:40.010> of<00:39:40.130> like<00:39:40.309> you 00:39:40.510 --> 00:39:40.520 align:start position:0% right for some time period of like you 00:39:40.520 --> 00:39:46.329 align:start position:0% right for some time period of like you know<00:39:40.640> one<00:39:40.819> week<00:39:41.349> and<00:39:43.119> they<00:39:44.119> have<00:39:44.150> to<00:39:44.809> be<00:39:45.770> above 00:39:46.329 --> 00:39:46.339 align:start position:0% know one week and they have to be above 00:39:46.339 --> 00:39:50.200 align:start position:0% know one week and they have to be above my<00:39:46.970> maximum<00:39:47.960> price<00:39:48.529> the<00:39:49.190> entire<00:39:49.549> time<00:39:49.910> right 00:39:50.200 --> 00:39:50.210 align:start position:0% my maximum price the entire time right 00:39:50.210 --> 00:39:52.390 align:start position:0% my maximum price the entire time right or<00:39:50.900> it's<00:39:51.260> just<00:39:51.349> like<00:39:51.619> a<00:39:51.650> total<00:39:51.859> censorship 00:39:52.390 --> 00:39:52.400 align:start position:0% or it's just like a total censorship 00:39:52.400 --> 00:39:54.130 align:start position:0% or it's just like a total censorship tagging<00:39:53.000> approve<00:39:53.270> of<00:39:53.420> etherium<00:39:53.900> and<00:39:54.049> then 00:39:54.130 --> 00:39:54.140 align:start position:0% tagging approve of etherium and then 00:39:54.140 --> 00:39:57.309 align:start position:0% tagging approve of etherium and then we're<00:39:54.289> like<00:39:54.410> ad<00:39:54.819> appearances<00:39:55.819> security<00:39:56.809> so 00:39:57.309 --> 00:39:57.319 align:start position:0% we're like ad appearances security so 00:39:57.319 --> 00:40:00.549 align:start position:0% we're like ad appearances security so like<00:39:57.559> this<00:39:58.130> means<00:39:58.579> that<00:39:58.940> what<00:39:59.930> I'm<00:40:00.140> willing<00:40:00.319> to 00:40:00.549 --> 00:40:00.559 align:start position:0% like this means that what I'm willing to 00:40:00.559 --> 00:40:02.430 align:start position:0% like this means that what I'm willing to spend<00:40:00.799> one<00:40:01.069> time<00:40:01.309> they<00:40:01.849> have<00:40:02.089> to<00:40:02.240> spend 00:40:02.430 --> 00:40:02.440 align:start position:0% spend one time they have to spend 00:40:02.440 --> 00:40:04.870 align:start position:0% spend one time they have to spend continuously<00:40:03.440> for<00:40:03.799> the<00:40:03.890> entire<00:40:04.220> censorship 00:40:04.870 --> 00:40:04.880 align:start position:0% continuously for the entire censorship 00:40:04.880 --> 00:40:08.589 align:start position:0% continuously for the entire censorship period<00:40:05.470> which<00:40:06.470> is<00:40:06.650> you<00:40:07.220> know<00:40:07.339> I<00:40:07.609> think<00:40:08.329> a 00:40:08.589 --> 00:40:08.599 align:start position:0% period which is you know I think a 00:40:08.599 --> 00:40:18.400 align:start position:0% period which is you know I think a reasonable<00:40:09.470> attempt<00:40:09.710> defense<00:40:09.829> model<00:40:17.410> we 00:40:18.400 --> 00:40:18.410 align:start position:0% reasonable attempt defense model we 00:40:18.410 --> 00:40:20.440 align:start position:0% reasonable attempt defense model we definitely<00:40:18.829> want<00:40:19.130> layer<00:40:19.430> one<00:40:19.640> to<00:40:19.789> scale<00:40:20.059> this 00:40:20.440 --> 00:40:20.450 align:start position:0% definitely want layer one to scale this 00:40:20.450 --> 00:40:23.620 align:start position:0% definitely want layer one to scale this is<00:40:20.660> not<00:40:21.520> that's<00:40:22.520> what<00:40:22.700> you're<00:40:22.910> looking<00:40:23.180> for 00:40:23.620 --> 00:40:23.630 align:start position:0% is not that's what you're looking for 00:40:23.630 --> 00:40:30.190 align:start position:0% is not that's what you're looking for yes<00:40:25.510> oh<00:40:27.279> sorry<00:40:28.279> we're<00:40:28.520> like<00:40:28.910> in<00:40:29.599> the<00:40:29.720> back<00:40:29.839> I 00:40:30.190 --> 00:40:30.200 align:start position:0% yes oh sorry we're like in the back I 00:40:30.200 --> 00:40:35.280 align:start position:0% yes oh sorry we're like in the back I didn't<00:40:30.740> want<00:40:30.890> to<00:40:30.950> just<00:40:31.460> speak<00:40:31.640> up 00:40:35.280 --> 00:40:35.290 align:start position:0% 00:40:35.290 --> 00:40:39.810 align:start position:0% mr.<00:40:36.290> Gowda<00:40:36.820> moving<00:40:37.820> out<00:40:38.000> that<00:40:38.330> the<00:40:38.620> rate<00:40:39.620> of 00:40:39.810 --> 00:40:39.820 align:start position:0% mr. Gowda moving out that the rate of 00:40:39.820 --> 00:40:43.930 align:start position:0% mr. Gowda moving out that the rate of return<00:40:40.820> run<00:40:41.060> within<00:40:41.330> a<00:40:41.510> single<00:40:41.870> phone<00:40:42.940> is 00:40:43.930 --> 00:40:43.940 align:start position:0% return run within a single phone is 00:40:43.940 --> 00:40:46.000 align:start position:0% return run within a single phone is there<00:40:44.120> any<00:40:44.300> way<00:40:44.390> of<00:40:44.420> enforcing<00:40:44.930> that<00:40:45.320> I<00:40:45.620> mean 00:40:46.000 --> 00:40:46.010 align:start position:0% there any way of enforcing that I mean 00:40:46.010 --> 00:40:50.760 align:start position:0% there any way of enforcing that I mean if<00:40:46.310> I'm<00:40:46.460> found<00:40:46.730> operator<00:40:47.570> can<00:40:47.930> I<00:40:47.990> just<00:40:48.200> create 00:40:50.760 --> 00:40:50.770 align:start position:0% 00:40:50.770 --> 00:40:55.090 align:start position:0% this<00:40:51.790> one<00:40:53.590> yeah<00:40:54.590> that's<00:40:54.770> a<00:40:54.920> great<00:40:55.010> question 00:40:55.090 --> 00:40:55.100 align:start position:0% this one yeah that's a great question 00:40:55.100 --> 00:40:56.950 align:start position:0% this one yeah that's a great question it's<00:40:55.670> really<00:40:56.000> nice<00:40:56.150> this<00:40:56.360> is<00:40:56.420> enforced<00:40:56.900> in 00:40:56.950 --> 00:40:56.960 align:start position:0% it's really nice this is enforced in 00:40:56.960 --> 00:40:58.870 align:start position:0% it's really nice this is enforced in etherium<00:40:57.350> we<00:40:57.710> just<00:40:57.950> run<00:40:58.160> the<00:40:58.280> block<00:40:58.490> in<00:40:58.670> if<00:40:58.760> the 00:40:58.870 --> 00:40:58.880 align:start position:0% etherium we just run the block in if the 00:40:58.880 --> 00:41:03.450 align:start position:0% etherium we just run the block in if the block<00:40:59.060> runs<00:40:59.330> out<00:40:59.510> of<00:40:59.540> gas<00:40:59.960> and<00:41:00.230> it's<00:41:00.380> a<00:41:00.470> prophet 00:41:03.450 --> 00:41:03.460 align:start position:0% 00:41:03.460 --> 00:41:05.950 align:start position:0% can<00:41:04.460> you<00:41:04.580> explain<00:41:04.820> again<00:41:05.060> why<00:41:05.240> your<00:41:05.420> sanitizer 00:41:05.950 --> 00:41:05.960 align:start position:0% can you explain again why your sanitizer 00:41:05.960 --> 00:41:07.570 align:start position:0% can you explain again why your sanitizer has<00:41:06.200> to<00:41:06.320> pay<00:41:06.470> for<00:41:06.500> the<00:41:06.710> whole<00:41:06.980> week<00:41:07.250> cuz<00:41:07.460> I 00:41:07.570 --> 00:41:07.580 align:start position:0% has to pay for the whole week cuz I 00:41:07.580 --> 00:41:08.890 align:start position:0% has to pay for the whole week cuz I thought<00:41:07.730> that<00:41:07.970> by<00:41:08.090> going<00:41:08.240> to<00:41:08.330> be<00:41:08.420> me<00:41:08.630> and<00:41:08.840> you 00:41:08.890 --> 00:41:08.900 align:start position:0% thought that by going to be me and you 00:41:08.900 --> 00:41:10.630 align:start position:0% thought that by going to be me and you and<00:41:09.260> whoever<00:41:09.410> wants<00:41:09.650> to<00:41:09.800> spend<00:41:10.280> our<00:41:10.370> fraud 00:41:10.630 --> 00:41:10.640 align:start position:0% and whoever wants to spend our fraud 00:41:10.640 --> 00:41:13.390 align:start position:0% and whoever wants to spend our fraud proofs<00:41:10.970> against<00:41:11.690> attacker<00:41:12.050> so<00:41:12.470> we<00:41:12.590> can<00:41:12.890> try 00:41:13.390 --> 00:41:13.400 align:start position:0% proofs against attacker so we can try 00:41:13.400 --> 00:41:15.800 align:start position:0% proofs against attacker so we can try and<00:41:13.490> get<00:41:13.550> all<00:41:13.730> of<00:41:13.790> our<00:41:13.850> father's<00:41:14.240> down 00:41:15.800 --> 00:41:15.810 align:start position:0% and get all of our father's down 00:41:15.810 --> 00:41:16.860 align:start position:0% and get all of our father's down [Music] 00:41:16.860 --> 00:41:16.870 align:start position:0% [Music] 00:41:16.870 --> 00:41:19.150 align:start position:0% [Music] whoever's<00:41:17.870> paying<00:41:18.080> for<00:41:18.410> the<00:41:18.500> Frog<00:41:18.710> group<00:41:18.950> the 00:41:19.150 --> 00:41:19.160 align:start position:0% whoever's paying for the Frog group the 00:41:19.160 --> 00:41:20.800 align:start position:0% whoever's paying for the Frog group the Frog<00:41:19.340> group<00:41:19.610> is<00:41:19.790> going<00:41:20.000> to<00:41:20.060> be<00:41:20.150> like<00:41:20.330> this<00:41:20.540> and 00:41:20.800 --> 00:41:20.810 align:start position:0% Frog group is going to be like this and 00:41:20.810 --> 00:41:22.390 align:start position:0% Frog group is going to be like this and then<00:41:21.140> the<00:41:21.290> attacker<00:41:21.560> needs<00:41:21.800> to<00:41:21.950> fill<00:41:22.130> blocks 00:41:22.390 --> 00:41:22.400 align:start position:0% then the attacker needs to fill blocks 00:41:22.400 --> 00:41:24.970 align:start position:0% then the attacker needs to fill blocks that<00:41:23.000> are<00:41:23.300> you<00:41:23.810> know<00:41:23.900> people<00:41:24.080> gasp<00:41:24.440> above 00:41:24.970 --> 00:41:24.980 align:start position:0% that are you know people gasp above 00:41:24.980 --> 00:41:27.850 align:start position:0% that are you know people gasp above whatever<00:41:25.610> that<00:41:25.910> is<00:41:26.090> for<00:41:26.360> the<00:41:26.510> entire<00:41:26.540> week<00:41:26.990> of 00:41:27.850 --> 00:41:27.860 align:start position:0% whatever that is for the entire week of 00:41:27.860 --> 00:41:29.380 align:start position:0% whatever that is for the entire week of the<00:41:28.010> tiger<00:41:28.460> all<00:41:28.610> he<00:41:28.790> would<00:41:28.910> have<00:41:28.970> to<00:41:29.150> do<00:41:29.240> is 00:41:29.380 --> 00:41:29.390 align:start position:0% the tiger all he would have to do is 00:41:29.390 --> 00:41:31.000 align:start position:0% the tiger all he would have to do is submit<00:41:29.540> a<00:41:29.630> ball<00:41:29.840> on<00:41:29.990> an<00:41:30.110> invalid<00:41:30.560> race<00:41:30.710> that<00:41:30.890> we 00:41:31.000 --> 00:41:31.010 align:start position:0% submit a ball on an invalid race that we 00:41:31.010 --> 00:41:33.100 align:start position:0% submit a ball on an invalid race that we all<00:41:31.220> have<00:41:31.460> to<00:41:31.640> them<00:41:31.850> hey<00:41:32.390> guys<00:41:32.720> to<00:41:32.900> get<00:41:33.020> our 00:41:33.100 --> 00:41:33.110 align:start position:0% all have to them hey guys to get our 00:41:33.110 --> 00:41:35.920 align:start position:0% all have to them hey guys to get our blocks<00:41:33.380> in<00:41:33.620> I<00:41:34.030> think<00:41:35.030> yeah<00:41:35.330> probably<00:41:35.540> good 00:41:35.920 --> 00:41:35.930 align:start position:0% blocks in I think yeah probably good 00:41:35.930 --> 00:41:55.050 align:start position:0% blocks in I think yeah probably good today<00:41:36.110> take<00:41:36.560> it<00:41:36.680> offline<00:41:36.890> but 00:41:55.050 --> 00:41:55.060 align:start position:0% 00:41:55.060 --> 00:41:59.890 align:start position:0% as<00:41:56.060> for<00:41:56.360> mobile<00:41:57.010> so<00:41:58.010> I'll<00:41:58.130> have<00:41:58.280> two<00:41:58.900> people 00:41:59.890 --> 00:41:59.900 align:start position:0% as for mobile so I'll have two people 00:41:59.900 --> 00:42:04.420 align:start position:0% as for mobile so I'll have two people knowing<00:42:01.330> the<00:42:02.330> based<00:42:02.690> solutions<00:42:03.410> here<00:42:03.680> Paul 00:42:04.420 --> 00:42:04.430 align:start position:0% knowing the based solutions here Paul 00:42:04.430 --> 00:42:07.930 align:start position:0% knowing the based solutions here Paul Daniel<00:42:05.140> do<00:42:06.140> over<00:42:06.320> here<00:42:06.350> is<00:42:07.310> just<00:42:07.370> a<00:42:07.760> mean 00:42:07.930 --> 00:42:07.940 align:start position:0% Daniel do over here is just a mean 00:42:07.940 --> 00:42:11.530 align:start position:0% Daniel do over here is just a mean making<00:42:08.840> your<00:42:08.990> that's<00:42:09.700> above<00:42:10.700> there<00:42:11.360> two 00:42:11.530 --> 00:42:11.540 align:start position:0% making your that's above there two 00:42:11.540 --> 00:42:20.800 align:start position:0% making your that's above there two solutions<00:42:19.270> actually<00:42:20.270> being<00:42:20.480> able<00:42:20.600> to<00:42:20.750> use 00:42:20.800 --> 00:42:20.810 align:start position:0% solutions actually being able to use 00:42:20.810 --> 00:42:27.520 align:start position:0% solutions actually being able to use these<00:42:21.350> as<00:42:21.590> a<00:42:21.620> desk<00:42:21.950> developers<00:42:25.000> so<00:42:26.000> with<00:42:26.530> Z 00:42:27.520 --> 00:42:27.530 align:start position:0% these as a desk developers so with Z 00:42:27.530 --> 00:42:29.800 align:start position:0% these as a desk developers so with Z controller<00:42:27.890> we're<00:42:28.760> still<00:42:29.060> kind<00:42:29.420> of<00:42:29.480> focused 00:42:29.800 --> 00:42:29.810 align:start position:0% controller we're still kind of focused 00:42:29.810 --> 00:42:33.340 align:start position:0% controller we're still kind of focused on<00:42:29.960> the<00:42:30.550> events<00:42:31.550> of<00:42:31.790> the<00:42:32.270> first<00:42:32.480> movie<00:42:32.750> concept 00:42:33.340 --> 00:42:33.350 align:start position:0% on the events of the first movie concept 00:42:33.350 --> 00:42:35.350 align:start position:0% on the events of the first movie concept I<00:42:33.590> think<00:42:34.220> that<00:42:34.340> that<00:42:34.520> makes<00:42:34.730> a<00:42:34.880> lot<00:42:35.000> of<00:42:35.030> sense 00:42:35.350 --> 00:42:35.360 align:start position:0% I think that that makes a lot of sense 00:42:35.360 --> 00:42:37.420 align:start position:0% I think that that makes a lot of sense to<00:42:35.570> I<00:42:36.230> think<00:42:36.620> that<00:42:36.890> we<00:42:37.070> like<00:42:37.220> have<00:42:37.400> a 00:42:37.420 --> 00:42:37.430 align:start position:0% to I think that we like have a 00:42:37.430 --> 00:42:39.190 align:start position:0% to I think that we like have a responsibility<00:42:38.030> to<00:42:38.420> prove<00:42:38.660> the<00:42:38.840> people<00:42:39.080> that 00:42:39.190 --> 00:42:39.200 align:start position:0% responsibility to prove the people that 00:42:39.200 --> 00:42:41.680 align:start position:0% responsibility to prove the people that this<00:42:39.320> is<00:42:39.380> secure<00:42:39.800> at<00:42:40.520> least<00:42:40.760> in<00:42:40.970> in<00:42:41.270> like<00:42:41.510> a 00:42:41.680 --> 00:42:41.690 align:start position:0% this is secure at least in in like a 00:42:41.690 --> 00:42:44.440 align:start position:0% this is secure at least in in like a limited<00:42:42.650> version<00:42:42.800> before<00:42:43.340> we<00:42:43.460> start<00:42:43.700> to<00:42:43.880> kind 00:42:44.440 --> 00:42:44.450 align:start position:0% limited version before we start to kind 00:42:44.450 --> 00:42:45.820 align:start position:0% limited version before we start to kind of<00:42:44.510> try<00:42:44.750> and<00:42:44.780> push<00:42:45.050> more<00:42:45.320> people<00:42:45.590> instead<00:42:45.770> of 00:42:45.820 --> 00:42:45.830 align:start position:0% of try and push more people instead of 00:42:45.830 --> 00:42:48.040 align:start position:0% of try and push more people instead of build<00:42:46.010> on<00:42:46.160> it<00:42:46.280> or<00:42:46.400> support<00:42:46.640> them<00:42:46.910> so<00:42:47.630> that's 00:42:48.040 --> 00:42:48.050 align:start position:0% build on it or support them so that's 00:42:48.050 --> 00:42:49.690 align:start position:0% build on it or support them so that's that's<00:42:48.380> kind<00:42:48.620> of<00:42:48.650> what<00:42:48.800> we're<00:42:48.920> working<00:42:49.070> on<00:42:49.340> to 00:42:49.690 --> 00:42:49.700 align:start position:0% that's kind of what we're working on to 00:42:49.700 --> 00:42:52.300 align:start position:0% that's kind of what we're working on to just<00:42:49.880> do<00:42:50.060> a<00:42:50.090> stupid<00:42:50.780> concept<00:42:51.440> or<00:42:51.740> like<00:42:52.070> not<00:42:52.280> a 00:42:52.300 --> 00:42:52.310 align:start position:0% just do a stupid concept or like not a 00:42:52.310 --> 00:42:53.620 align:start position:0% just do a stupid concept or like not a group<00:42:52.520> concept<00:42:52.760> will<00:42:53.000> make<00:42:53.120> a<00:42:53.150> real<00:42:53.360> thing 00:42:53.620 --> 00:42:53.630 align:start position:0% group concept will make a real thing 00:42:53.630 --> 00:42:56.740 align:start position:0% group concept will make a real thing that<00:42:53.930> actually<00:42:54.620> works<00:42:55.010> and<00:42:55.310> stays<00:42:56.120> stable<00:42:56.420> for 00:42:56.740 --> 00:42:56.750 align:start position:0% that actually works and stays stable for 00:42:56.750 --> 00:42:58.990 align:start position:0% that actually works and stays stable for a<00:42:56.810> while<00:42:56.990> and<00:42:57.620> after<00:42:57.770> that<00:42:58.070> you<00:42:58.640> will<00:42:58.790> have<00:42:58.850> all 00:42:58.990 --> 00:42:59.000 align:start position:0% a while and after that you will have all 00:42:59.000 --> 00:43:00.670 align:start position:0% a while and after that you will have all the<00:42:59.180> tooling<00:42:59.510> that<00:42:59.540> we<00:42:59.720> need<00:42:59.900> to<00:43:00.140> make<00:43:00.560> my 00:43:00.670 --> 00:43:00.680 align:start position:0% the tooling that we need to make my 00:43:00.680 --> 00:43:02.920 align:start position:0% the tooling that we need to make my scenario<00:43:00.950> to<00:43:01.220> take<00:43:01.550> a<00:43:01.640> little<00:43:01.910> bit<00:43:02.120> we'd<00:43:02.840> be 00:43:02.920 --> 00:43:02.930 align:start position:0% scenario to take a little bit we'd be 00:43:02.930 --> 00:43:07.750 align:start position:0% scenario to take a little bit we'd be kind<00:43:03.050> of<00:43:03.200> exploring<00:43:03.770> that<00:43:06.400> this<00:43:07.400> is<00:43:07.550> also 00:43:07.750 --> 00:43:07.760 align:start position:0% kind of exploring that this is also 00:43:07.760 --> 00:43:10.300 align:start position:0% kind of exploring that this is also really<00:43:08.150> good<00:43:08.540> this<00:43:09.440> is<00:43:09.590> also<00:43:09.740> really<00:43:10.130> good 00:43:10.300 --> 00:43:10.310 align:start position:0% really good this is also really good 00:43:10.310 --> 00:43:14.140 align:start position:0% really good this is also really good time<00:43:10.610> if<00:43:11.390> you<00:43:11.630> have<00:43:11.840> an<00:43:11.930> idea<00:43:12.640> for<00:43:13.640> a<00:43:13.700> kind<00:43:14.060> of 00:43:14.140 --> 00:43:14.150 align:start position:0% time if you have an idea for a kind of 00:43:14.150 --> 00:43:17.980 align:start position:0% time if you have an idea for a kind of application<00:43:14.300> of<00:43:15.020> phase<00:43:15.890> one<00:43:16.190> you<00:43:16.600> could<00:43:17.600> now 00:43:17.980 --> 00:43:17.990 align:start position:0% application of phase one you could now 00:43:17.990 --> 00:43:21.970 align:start position:0% application of phase one you could now also<00:43:18.710> ask<00:43:18.920> people<00:43:19.070> like<00:43:19.750> these<00:43:20.750> people<00:43:21.680> that 00:43:21.970 --> 00:43:21.980 align:start position:0% also ask people like these people that 00:43:21.980 --> 00:43:24.190 align:start position:0% also ask people like these people that have<00:43:22.400> gone<00:43:22.580> through<00:43:22.640> the<00:43:22.940> motions<00:43:23.210> think<00:43:23.990> that 00:43:24.190 --> 00:43:24.200 align:start position:0% have gone through the motions think that 00:43:24.200 --> 00:43:26.680 align:start position:0% have gone through the motions think that it<00:43:24.290> could<00:43:24.470> work<00:43:24.680> with<00:43:25.640> the<00:43:25.850> properties<00:43:26.450> that 00:43:26.680 --> 00:43:26.690 align:start position:0% it could work with the properties that 00:43:26.690 --> 00:43:28.990 align:start position:0% it could work with the properties that you<00:43:27.080> get<00:43:27.350> on<00:43:27.500> the<00:43:27.590> face<00:43:27.770> ones<00:43:28.040> like<00:43:28.400> use<00:43:28.820> the 00:43:28.990 --> 00:43:29.000 align:start position:0% you get on the face ones like use the 00:43:29.000 --> 00:43:34.550 align:start position:0% you get on the face ones like use the time<00:43:30.340> so<00:43:31.340> just<00:43:31.670> a<00:43:31.930> question 00:43:34.550 --> 00:43:34.560 align:start position:0% time so just a question 00:43:34.560 --> 00:43:36.950 align:start position:0% time so just a question built<00:43:35.190> on<00:43:35.370> this<00:43:35.610> and<00:43:36.450> then<00:43:36.600> we're<00:43:36.720> really<00:43:36.810> a 00:43:36.950 --> 00:43:36.960 align:start position:0% built on this and then we're really a 00:43:36.960 --> 00:43:39.260 align:start position:0% built on this and then we're really a lot<00:43:37.260> of<00:43:37.350> hands<00:43:37.620> raised<00:43:38.010> and<00:43:38.280> listening<00:43:39.150> to 00:43:39.260 --> 00:43:39.270 align:start position:0% lot of hands raised and listening to 00:43:39.270 --> 00:43:41.240 align:start position:0% lot of hands raised and listening to this<00:43:39.450> I<00:43:39.720> got<00:43:39.990> a<00:43:40.050> lot<00:43:40.320> of<00:43:40.350> cognitive<00:43:40.890> fatigue 00:43:41.240 --> 00:43:41.250 align:start position:0% this I got a lot of cognitive fatigue 00:43:41.250 --> 00:43:43.310 align:start position:0% this I got a lot of cognitive fatigue because<00:43:42.150> it<00:43:42.270> seems<00:43:42.510> like<00:43:42.570> a<00:43:42.720> deep<00:43:42.930> technical 00:43:43.310 --> 00:43:43.320 align:start position:0% because it seems like a deep technical 00:43:43.320 --> 00:43:44.720 align:start position:0% because it seems like a deep technical knife<00:43:43.710> and<00:43:44.100> the<00:43:44.190> things<00:43:44.400> that<00:43:44.550> aren't 00:43:44.720 --> 00:43:44.730 align:start position:0% knife and the things that aren't 00:43:44.730 --> 00:43:47.600 align:start position:0% knife and the things that aren't confirmed<00:43:45.300> yet<00:43:45.660> on<00:43:45.900> your<00:43:46.050> bass<00:43:46.290> one<00:43:46.650> so<00:43:47.400> for 00:43:47.600 --> 00:43:47.610 align:start position:0% confirmed yet on your bass one so for 00:43:47.610 --> 00:43:49.070 align:start position:0% confirmed yet on your bass one so for example<00:43:48.060> running<00:43:48.450> a<00:43:48.480> little<00:43:48.630> bit<00:43:48.840> of<00:43:48.930> what<00:43:49.050> I 00:43:49.070 --> 00:43:49.080 align:start position:0% example running a little bit of what I 00:43:49.080 --> 00:43:51.620 align:start position:0% example running a little bit of what I was<00:43:49.230> trying<00:43:49.290> to<00:43:49.470> understand<00:43:49.830> plasma<00:43:50.490> and<00:43:50.700> and 00:43:51.620 --> 00:43:51.630 align:start position:0% was trying to understand plasma and and 00:43:51.630 --> 00:43:53.270 align:start position:0% was trying to understand plasma and and so<00:43:52.050> I<00:43:52.080> spent<00:43:52.500> a<00:43:52.530> tremendous<00:43:52.680> amount<00:43:53.070> of 00:43:53.270 --> 00:43:53.280 align:start position:0% so I spent a tremendous amount of 00:43:53.280 --> 00:43:55.250 align:start position:0% so I spent a tremendous amount of cognitive<00:43:53.730> load<00:43:53.940> trying<00:43:54.780> to<00:43:54.840> understand 00:43:55.250 --> 00:43:55.260 align:start position:0% cognitive load trying to understand 00:43:55.260 --> 00:43:58.010 align:start position:0% cognitive load trying to understand plasma<00:43:55.890> as<00:43:56.070> a<00:43:56.130> developer<00:43:56.850> and<00:43:57.210> it's<00:43:57.690> sort<00:43:57.930> of 00:43:58.010 --> 00:43:58.020 align:start position:0% plasma as a developer and it's sort of 00:43:58.020 --> 00:43:59.570 align:start position:0% plasma as a developer and it's sort of building<00:43:58.290> this<00:43:58.410> for<00:43:58.680> not<00:43:58.860> now 00:43:59.570 --> 00:43:59.580 align:start position:0% building this for not now 00:43:59.580 --> 00:44:02.120 align:start position:0% building this for not now so<00:43:59.970> in<00:44:00.420> this<00:44:00.600> discussion<00:44:00.870> it's<00:44:01.680> very<00:44:01.890> very 00:44:02.120 --> 00:44:02.130 align:start position:0% so in this discussion it's very very 00:44:02.130 --> 00:44:05.300 align:start position:0% so in this discussion it's very very interesting<00:44:02.390> however<00:44:03.390> as<00:44:04.140> a<00:44:04.200> developer<00:44:04.920> I 00:44:05.300 --> 00:44:05.310 align:start position:0% interesting however as a developer I 00:44:05.310 --> 00:44:06.920 align:start position:0% interesting however as a developer I have<00:44:05.760> a<00:44:05.790> certain<00:44:06.150> amount<00:44:06.300> of<00:44:06.450> bandwidth<00:44:06.900> for 00:44:06.920 --> 00:44:06.930 align:start position:0% have a certain amount of bandwidth for 00:44:06.930 --> 00:44:08.510 align:start position:0% have a certain amount of bandwidth for this<00:44:07.230> for<00:44:07.410> a<00:44:07.440> low-level<00:44:07.890> protocol 00:44:08.510 --> 00:44:08.520 align:start position:0% this for a low-level protocol 00:44:08.520 --> 00:44:11.360 align:start position:0% this for a low-level protocol understanding<00:44:09.330> and<00:44:09.600> so<00:44:10.230> I<00:44:10.260> think<00:44:10.590> maybe<00:44:10.770> if 00:44:11.360 --> 00:44:11.370 align:start position:0% understanding and so I think maybe if 00:44:11.370 --> 00:44:12.710 align:start position:0% understanding and so I think maybe if you<00:44:11.490> could<00:44:11.640> just<00:44:11.790> sort<00:44:11.940> of<00:44:12.060> say<00:44:12.120> the<00:44:12.510> stuff 00:44:12.710 --> 00:44:12.720 align:start position:0% you could just sort of say the stuff 00:44:12.720 --> 00:44:14.390 align:start position:0% you could just sort of say the stuff that<00:44:12.870> we've<00:44:13.020> talked<00:44:13.290> about<00:44:13.440> in<00:44:13.830> the<00:44:13.920> past<00:44:14.070> half 00:44:14.390 --> 00:44:14.400 align:start position:0% that we've talked about in the past half 00:44:14.400 --> 00:44:16.520 align:start position:0% that we've talked about in the past half hour<00:44:14.610> how<00:44:15.210> much<00:44:15.390> of<00:44:15.510> this<00:44:15.600> is<00:44:15.660> locked<00:44:16.080> in<00:44:16.350> and 00:44:16.520 --> 00:44:16.530 align:start position:0% hour how much of this is locked in and 00:44:16.530 --> 00:44:19.040 align:start position:0% hour how much of this is locked in and confirmed<00:44:17.010> that<00:44:17.130> it<00:44:17.190> won't<00:44:17.460> change<00:44:17.790> in<00:44:18.630> terms 00:44:19.040 --> 00:44:19.050 align:start position:0% confirmed that it won't change in terms 00:44:19.050 --> 00:44:23.800 align:start position:0% confirmed that it won't change in terms of<00:44:19.850> these<00:44:20.850> specs<00:44:21.180> you've<00:44:21.450> just<00:44:21.720> discussed<00:44:22.140> now 00:44:23.800 --> 00:44:23.810 align:start position:0% of these specs you've just discussed now 00:44:23.810 --> 00:44:30.700 align:start position:0% of these specs you've just discussed now okay<00:44:24.810> so<00:44:24.870> the<00:44:25.110> question<00:44:25.260> is<00:44:27.530> the<00:44:28.530> question<00:44:28.890> is 00:44:30.700 --> 00:44:30.710 align:start position:0% okay so the question is the question is 00:44:30.710 --> 00:44:33.110 align:start position:0% okay so the question is the question is let's<00:44:31.710> summarize<00:44:32.070> what<00:44:32.310> what<00:44:32.790> do<00:44:32.850> I<00:44:32.940> care 00:44:33.110 --> 00:44:33.120 align:start position:0% let's summarize what what do I care 00:44:33.120 --> 00:44:34.670 align:start position:0% let's summarize what what do I care about<00:44:33.360> is<00:44:33.510> a<00:44:33.540> developer<00:44:34.020> I<00:44:34.170> could<00:44:34.410> know<00:44:34.500> right 00:44:34.670 --> 00:44:34.680 align:start position:0% about is a developer I could know right 00:44:34.680 --> 00:44:36.170 align:start position:0% about is a developer I could know right now<00:44:34.830> so<00:44:34.980> just<00:44:35.130> to<00:44:35.250> say<00:44:35.430> how<00:44:35.730> much<00:44:35.850> of<00:44:36.000> this<00:44:36.120> is 00:44:36.170 --> 00:44:36.180 align:start position:0% now so just to say how much of this is 00:44:36.180 --> 00:44:37.910 align:start position:0% now so just to say how much of this is for<00:44:36.570> sure<00:44:36.720> not<00:44:36.780> going<00:44:37.110> to<00:44:37.230> change<00:44:37.500> in<00:44:37.740> the<00:44:37.800> next 00:44:37.910 --> 00:44:37.920 align:start position:0% for sure not going to change in the next 00:44:37.920 --> 00:44:40.280 align:start position:0% for sure not going to change in the next three<00:44:38.580> months<00:44:38.760> set<00:44:39.150> how<00:44:39.780> much<00:44:39.960> of<00:44:40.140> this<00:44:40.230> is 00:44:40.280 --> 00:44:40.290 align:start position:0% three months set how much of this is 00:44:40.290 --> 00:44:41.570 align:start position:0% three months set how much of this is voice<00:44:40.710> you<00:44:40.830> are<00:44:40.860> not<00:44:41.070> going<00:44:41.190> to<00:44:41.220> change<00:44:41.430> one 00:44:41.570 --> 00:44:41.580 align:start position:0% voice you are not going to change one 00:44:41.580 --> 00:44:43.250 align:start position:0% voice you are not going to change one three<00:44:41.760> one<00:44:41.880> and<00:44:42.180> three<00:44:42.300> let's<00:44:42.420> say<00:44:42.570> so<00:44:43.020> like 00:44:43.250 --> 00:44:43.260 align:start position:0% three one and three let's say so like 00:44:43.260 --> 00:44:44.930 align:start position:0% three one and three let's say so like the<00:44:43.560> kind<00:44:43.800> of<00:44:43.950> I<00:44:44.190> think<00:44:44.310> the<00:44:44.550> kind<00:44:44.700> of<00:44:44.730> trying 00:44:44.930 --> 00:44:44.940 align:start position:0% the kind of I think the kind of trying 00:44:44.940 --> 00:44:46.910 align:start position:0% the kind of I think the kind of trying to<00:44:44.970> be<00:44:45.090> mean<00:44:45.330> kind<00:44:45.540> of<00:44:45.570> loud<00:44:45.750> and<00:44:45.960> other<00:44:46.590> people 00:44:46.910 --> 00:44:46.920 align:start position:0% to be mean kind of loud and other people 00:44:46.920 --> 00:44:48.350 align:start position:0% to be mean kind of loud and other people who<00:44:47.070> work<00:44:47.280> on<00:44:47.370> this<00:44:47.490> stuff<00:44:47.670> happen<00:44:47.970> as<00:44:48.030> well<00:44:48.150> is 00:44:48.350 --> 00:44:48.360 align:start position:0% who work on this stuff happen as well is 00:44:48.360 --> 00:44:49.670 align:start position:0% who work on this stuff happen as well is to<00:44:48.450> try<00:44:48.720> and<00:44:48.780> build<00:44:48.900> things<00:44:49.170> that<00:44:49.380> will<00:44:49.530> work 00:44:49.670 --> 00:44:49.680 align:start position:0% to try and build things that will work 00:44:49.680 --> 00:44:52.160 align:start position:0% to try and build things that will work on<00:44:49.830> their<00:44:49.980> -<00:44:50.220> I<00:44:50.520> will<00:44:50.910> also<00:44:51.240> work<00:44:51.270> at<00:44:51.510> E<00:44:51.570> -<00:44:51.750> like 00:44:52.160 --> 00:44:52.170 align:start position:0% on their - I will also work at E - like 00:44:52.170 --> 00:44:54.080 align:start position:0% on their - I will also work at E - like whatever<00:44:52.680> my<00:44:52.890> work<00:44:53.100> is<00:44:53.250> all<00:44:53.400> focused<00:44:53.670> words 00:44:54.080 --> 00:44:54.090 align:start position:0% whatever my work is all focused words 00:44:54.090 --> 00:44:56.660 align:start position:0% whatever my work is all focused words there<00:44:54.330> -<00:44:54.540> Auggie's<00:44:55.200> one<00:44:55.470> just<00:44:56.010> because<00:44:56.100> I<00:44:56.310> have 00:44:56.660 --> 00:44:56.670 align:start position:0% there - Auggie's one just because I have 00:44:56.670 --> 00:44:58.520 align:start position:0% there - Auggie's one just because I have the<00:44:56.820> same<00:44:56.970> good<00:44:57.150> sizes<00:44:57.360> you<00:44:57.600> I<00:44:57.900> don't<00:44:58.350> want<00:44:58.470> to 00:44:58.520 --> 00:44:58.530 align:start position:0% the same good sizes you I don't want to 00:44:58.530 --> 00:44:59.570 align:start position:0% the same good sizes you I don't want to build<00:44:58.680> something<00:44:58.860> that<00:44:58.980> that's<00:44:59.370> going<00:44:59.520> to 00:44:59.570 --> 00:44:59.580 align:start position:0% build something that that's going to 00:44:59.580 --> 00:45:03.410 align:start position:0% build something that that's going to change<00:45:00.530> so<00:45:01.530> I<00:45:01.920> don't<00:45:02.550> know<00:45:02.610> maybe<00:45:03.030> we<00:45:03.270> can 00:45:03.410 --> 00:45:03.420 align:start position:0% change so I don't know maybe we can 00:45:03.420 --> 00:45:07.530 align:start position:0% change so I don't know maybe we can check<00:45:03.720> with<00:45:03.840> Danny 00:45:07.530 --> 00:45:07.540 align:start position:0% 00:45:07.540 --> 00:45:09.700 align:start position:0% specifically<00:45:08.540> means<00:45:08.690> regardless<00:45:09.350> of<00:45:09.500> which 00:45:09.700 --> 00:45:09.710 align:start position:0% specifically means regardless of which 00:45:09.710 --> 00:45:12.900 align:start position:0% specifically means regardless of which data<00:45:10.280> Larian<00:45:10.760> their<00:45:11.240> availability<00:45:11.630> like<00:45:12.020> is 00:45:12.900 --> 00:45:12.910 align:start position:0% data Larian their availability like is 00:45:12.910 --> 00:45:15.220 align:start position:0% data Larian their availability like is isn't<00:45:13.910> worth<00:45:14.120> actually<00:45:14.420> learning<00:45:14.990> as<00:45:15.110> you 00:45:15.220 --> 00:45:15.230 align:start position:0% isn't worth actually learning as you 00:45:15.230 --> 00:45:17.890 align:start position:0% isn't worth actually learning as you can't<00:45:15.440> roll<00:45:15.590> up<00:45:15.740> like<00:45:16.100> is<00:45:16.370> is<00:45:16.970> the<00:45:17.420> notion<00:45:17.630> of 00:45:17.890 --> 00:45:17.900 align:start position:0% can't roll up like is is the notion of 00:45:17.900 --> 00:45:19.390 align:start position:0% can't roll up like is is the notion of this<00:45:18.110> protocol<00:45:18.500> going<00:45:18.860> to<00:45:18.950> drastically 00:45:19.390 --> 00:45:19.400 align:start position:0% this protocol going to drastically 00:45:19.400 --> 00:45:21.490 align:start position:0% this protocol going to drastically change<00:45:19.700> to<00:45:20.060> the<00:45:20.120> next<00:45:20.360> four<00:45:20.540> months<00:45:20.690> such<00:45:21.290> that 00:45:21.490 --> 00:45:21.500 align:start position:0% change to the next four months such that 00:45:21.500 --> 00:45:22.660 align:start position:0% change to the next four months such that the<00:45:21.710> cognitive<00:45:22.070> about<00:45:22.220> realizing<00:45:22.460> about 00:45:22.660 --> 00:45:22.670 align:start position:0% the cognitive about realizing about 00:45:22.670 --> 00:45:23.950 align:start position:0% the cognitive about realizing about memory<00:45:23.060> that<00:45:23.180> you<00:45:23.240> might<00:45:23.390> spend<00:45:23.630> today<00:45:23.900> to 00:45:23.950 --> 00:45:23.960 align:start position:0% memory that you might spend today to 00:45:23.960 --> 00:45:25.840 align:start position:0% memory that you might spend today to learn<00:45:24.200> it<00:45:24.380> and<00:45:24.560> begin<00:45:25.160> thinking<00:45:25.460> about<00:45:25.610> how<00:45:25.730> to 00:45:25.840 --> 00:45:25.850 align:start position:0% learn it and begin thinking about how to 00:45:25.850 --> 00:45:27.670 align:start position:0% learn it and begin thinking about how to development<00:45:26.480> like<00:45:26.630> might<00:45:26.810> just<00:45:27.110> intron<00:45:27.530> the 00:45:27.670 --> 00:45:27.680 align:start position:0% development like might just intron the 00:45:27.680 --> 00:45:31.450 align:start position:0% development like might just intron the window<00:45:27.950> in<00:45:28.310> court<00:45:28.550> months<00:45:30.010> this<00:45:31.010> is<00:45:31.070> a<00:45:31.250> great 00:45:31.450 --> 00:45:31.460 align:start position:0% window in court months this is a great 00:45:31.460 --> 00:45:33.520 align:start position:0% window in court months this is a great question<00:45:31.910> and<00:45:32.120> i<00:45:32.540> think<00:45:32.570> that<00:45:32.990> people<00:45:33.350> should 00:45:33.520 --> 00:45:33.530 align:start position:0% question and i think that people should 00:45:33.530 --> 00:45:35.860 align:start position:0% question and i think that people should not<00:45:33.980> really<00:45:34.310> have<00:45:34.430> to<00:45:34.730> learn<00:45:34.880> this<00:45:35.120> at<00:45:35.360> all<00:45:35.600> in 00:45:35.860 --> 00:45:35.870 align:start position:0% not really have to learn this at all in 00:45:35.870 --> 00:45:37.870 align:start position:0% not really have to learn this at all in terms<00:45:36.290> of<00:45:36.560> answering<00:45:37.040> it<00:45:37.190> on<00:45:37.460> face<00:45:37.790> value 00:45:37.870 --> 00:45:37.880 align:start position:0% terms of answering it on face value 00:45:37.880 --> 00:45:41.260 align:start position:0% terms of answering it on face value about<00:45:38.240> say<00:45:38.420> like<00:45:38.600> a<00:45:38.780> solid<00:45:39.440> 90<00:45:39.920> percent<00:45:40.430> 95 00:45:41.260 --> 00:45:41.270 align:start position:0% about say like a solid 90 percent 95 00:45:41.270 --> 00:45:43.900 align:start position:0% about say like a solid 90 percent 95 percent<00:45:41.480> of<00:45:42.290> what<00:45:42.740> I<00:45:42.800> talked<00:45:43.130> about<00:45:43.250> here<00:45:43.430> is 00:45:43.900 --> 00:45:43.910 align:start position:0% percent of what I talked about here is 00:45:43.910 --> 00:45:45.970 align:start position:0% percent of what I talked about here is just<00:45:44.210> this<00:45:44.390> is<00:45:44.570> literally<00:45:44.900> how<00:45:45.200> optimistic 00:45:45.970 --> 00:45:45.980 align:start position:0% just this is literally how optimistic 00:45:45.980 --> 00:45:48.730 align:start position:0% just this is literally how optimistic roll-up<00:45:46.490> works<00:45:46.730> and<00:45:47.030> we<00:45:47.690> already<00:45:48.230> can<00:45:48.560> get 00:45:48.730 --> 00:45:48.740 align:start position:0% roll-up works and we already can get 00:45:48.740 --> 00:45:51.370 align:start position:0% roll-up works and we already can get smart<00:45:49.460> contracts<00:45:50.000> on<00:45:50.150> this<00:45:50.390> right<00:45:51.050> so<00:45:51.230> like 00:45:51.370 --> 00:45:51.380 align:start position:0% smart contracts on this right so like 00:45:51.380 --> 00:45:53.230 align:start position:0% smart contracts on this right so like this<00:45:51.650> the<00:45:52.130> the<00:45:52.400> I<00:45:52.430> think<00:45:52.790> that<00:45:52.910> the<00:45:53.030> big 00:45:53.230 --> 00:45:53.240 align:start position:0% this the the I think that the big 00:45:53.240 --> 00:45:55.930 align:start position:0% this the the I think that the big problem<00:45:53.840> with<00:45:53.960> layer<00:45:54.200> two<00:45:54.500> thus<00:45:55.310> far<00:45:55.640> it's 00:45:55.930 --> 00:45:55.940 align:start position:0% problem with layer two thus far it's 00:45:55.940 --> 00:45:58.540 align:start position:0% problem with layer two thus far it's been<00:45:56.030> we<00:45:56.750> have<00:45:56.900> been<00:45:57.350> talking<00:45:57.830> about<00:45:57.890> you<00:45:58.370> know 00:45:58.540 --> 00:45:58.550 align:start position:0% been we have been talking about you know 00:45:58.550 --> 00:46:01.210 align:start position:0% been we have been talking about you know protocols<00:45:59.210> incentive<00:46:00.020> reasoning<00:46:00.590> and<00:46:00.860> like 00:46:01.210 --> 00:46:01.220 align:start position:0% protocols incentive reasoning and like 00:46:01.220 --> 00:46:03.550 align:start position:0% protocols incentive reasoning and like expecting<00:46:01.880> developers<00:46:02.450> to<00:46:02.750> actually<00:46:03.290> you 00:46:03.550 --> 00:46:03.560 align:start position:0% expecting developers to actually you 00:46:03.560 --> 00:46:05.680 align:start position:0% expecting developers to actually you know<00:46:03.590> have<00:46:03.890> to<00:46:04.070> learn<00:46:04.310> about<00:46:04.580> how<00:46:05.210> these 00:46:05.680 --> 00:46:05.690 align:start position:0% know have to learn about how these 00:46:05.690 --> 00:46:07.390 align:start position:0% know have to learn about how these different<00:46:06.200> parties<00:46:06.620> are<00:46:06.800> going<00:46:06.950> to<00:46:07.040> interact 00:46:07.390 --> 00:46:07.400 align:start position:0% different parties are going to interact 00:46:07.400 --> 00:46:08.950 align:start position:0% different parties are going to interact in<00:46:07.730> these<00:46:07.850> different<00:46:08.090> worlds<00:46:08.720> and<00:46:08.870> how 00:46:08.950 --> 00:46:08.960 align:start position:0% in these different worlds and how 00:46:08.960 --> 00:46:11.920 align:start position:0% in these different worlds and how they're<00:46:09.170> going<00:46:09.320> to<00:46:09.560> you<00:46:09.680> know<00:46:09.740> you<00:46:10.460> do<00:46:10.970> play 00:46:11.920 --> 00:46:11.930 align:start position:0% they're going to you know you do play 00:46:11.930 --> 00:46:13.900 align:start position:0% they're going to you know you do play out<00:46:12.080> some<00:46:12.320> dispute<00:46:12.710> game<00:46:12.920> like<00:46:13.370> I<00:46:13.520> don't<00:46:13.640> want 00:46:13.900 --> 00:46:13.910 align:start position:0% out some dispute game like I don't want 00:46:13.910 --> 00:46:15.370 align:start position:0% out some dispute game like I don't want people<00:46:14.120> to<00:46:14.240> think<00:46:14.420> about<00:46:14.450> dispute<00:46:14.930> games<00:46:15.140> I 00:46:15.370 --> 00:46:15.380 align:start position:0% people to think about dispute games I 00:46:15.380 --> 00:46:16.750 align:start position:0% people to think about dispute games I just<00:46:15.530> want<00:46:15.950> people<00:46:16.070> to<00:46:16.220> write<00:46:16.490> smart 00:46:16.750 --> 00:46:16.760 align:start position:0% just want people to write smart 00:46:16.760 --> 00:46:18.010 align:start position:0% just want people to write smart contracts<00:46:17.180> because<00:46:17.330> that's<00:46:17.600> what<00:46:17.720> got<00:46:17.870> me 00:46:18.010 --> 00:46:18.020 align:start position:0% contracts because that's what got me 00:46:18.020 --> 00:46:20.740 align:start position:0% contracts because that's what got me into<00:46:18.410> aetherium<00:46:18.710> personally<00:46:19.220> and<00:46:20.090> so<00:46:20.300> this<00:46:20.540> is 00:46:20.740 --> 00:46:20.750 align:start position:0% into aetherium personally and so this is 00:46:20.750 --> 00:46:23.050 align:start position:0% into aetherium personally and so this is the<00:46:21.020> entire<00:46:21.500> reason<00:46:21.800> why<00:46:22.130> I'm<00:46:22.310> interested<00:46:22.970> in 00:46:23.050 --> 00:46:23.060 align:start position:0% the entire reason why I'm interested in 00:46:23.060 --> 00:46:25.510 align:start position:0% the entire reason why I'm interested in optimistic<00:46:23.630> role<00:46:23.780> is<00:46:23.990> it's<00:46:24.440> the<00:46:24.680> fastest<00:46:25.310> way 00:46:25.510 --> 00:46:25.520 align:start position:0% optimistic role is it's the fastest way 00:46:25.520 --> 00:46:27.820 align:start position:0% optimistic role is it's the fastest way to<00:46:25.790> start<00:46:26.450> scaling<00:46:26.780> and<00:46:27.140> improving<00:46:27.500> the<00:46:27.650> user 00:46:27.820 --> 00:46:27.830 align:start position:0% to start scaling and improving the user 00:46:27.830 --> 00:46:32.190 align:start position:0% to start scaling and improving the user experience<00:46:27.920> of<00:46:28.520> solidity<00:46:29.060> smart<00:46:29.420> contracts<00:46:29.930> I 00:46:32.190 --> 00:46:32.200 align:start position:0% 00:46:32.200 --> 00:46:34.660 align:start position:0% think<00:46:33.200> it's<00:46:33.350> an<00:46:33.500> interesting<00:46:33.650> observation<00:46:34.040> as 00:46:34.660 --> 00:46:34.670 align:start position:0% think it's an interesting observation as 00:46:34.670 --> 00:46:37.680 align:start position:0% think it's an interesting observation as well<00:46:34.820> like<00:46:34.970> it<00:46:35.150> when<00:46:35.960> I<00:46:35.990> at<00:46:36.770> the<00:46:37.010> beginning 00:46:37.680 --> 00:46:37.690 align:start position:0% well like it when I at the beginning 00:46:37.690 --> 00:46:41.580 align:start position:0% well like it when I at the beginning alluded<00:46:38.690> to<00:46:38.930> the<00:46:39.110> fairly<00:46:39.740> early<00:46:40.310> stages<00:46:40.760> yet 00:46:41.580 --> 00:46:41.590 align:start position:0% alluded to the fairly early stages yet 00:46:41.590 --> 00:46:45.850 align:start position:0% alluded to the fairly early stages yet it<00:46:42.590> was<00:46:42.770> also<00:46:42.980> to<00:46:43.250> raise<00:46:43.370> awareness<00:46:43.760> that<00:46:44.860> in 00:46:45.850 --> 00:46:45.860 align:start position:0% it was also to raise awareness that in 00:46:45.860 --> 00:46:49.000 align:start position:0% it was also to raise awareness that in entering<00:46:46.720> phase<00:46:47.720> one<00:46:48.470> or<00:46:48.710> even<00:46:48.830> two 00:46:49.000 --> 00:46:49.010 align:start position:0% entering phase one or even two 00:46:49.010 --> 00:46:51.370 align:start position:0% entering phase one or even two discussions<00:46:49.760> right<00:46:49.970> now<00:46:50.030> you<00:46:50.900> need<00:46:51.140> to<00:46:51.290> get 00:46:51.370 --> 00:46:51.380 align:start position:0% discussions right now you need to get 00:46:51.380 --> 00:46:53.320 align:start position:0% discussions right now you need to get fairly<00:46:51.800> deep<00:46:51.950> in<00:46:52.100> the<00:46:52.220> weeds<00:46:52.340> like<00:46:53.090> if<00:46:53.240> you 00:46:53.320 --> 00:46:53.330 align:start position:0% fairly deep in the weeds like if you 00:46:53.330 --> 00:46:54.650 align:start position:0% fairly deep in the weeds like if you want<00:46:53.510> to<00:46:53.570> develop<00:46:53.780> a<00:46:53.990> next 00:46:54.650 --> 00:46:54.660 align:start position:0% want to develop a next 00:46:54.660 --> 00:46:57.079 align:start position:0% want to develop a next apparently<00:46:55.500> deep<00:46:55.680> right<00:46:56.069> that's<00:46:56.789> a<00:46:56.880> bit<00:46:57.000> of 00:46:57.079 --> 00:46:57.089 align:start position:0% apparently deep right that's a bit of 00:46:57.089 --> 00:47:02.450 align:start position:0% apparently deep right that's a bit of work<00:46:58.339> however<00:47:00.259> we've<00:47:01.259> already<00:47:01.470> torn<00:47:02.250> out<00:47:02.430> a 00:47:02.450 --> 00:47:02.460 align:start position:0% work however we've already torn out a 00:47:02.460 --> 00:47:04.400 align:start position:0% work however we've already torn out a couple<00:47:02.849> of<00:47:02.940> these<00:47:03.059> simple<00:47:03.690> properties<00:47:04.200> that 00:47:04.400 --> 00:47:04.410 align:start position:0% couple of these simple properties that 00:47:04.410 --> 00:47:06.349 align:start position:0% couple of these simple properties that you<00:47:04.559> can<00:47:04.859> already<00:47:05.160> like<00:47:05.430> start<00:47:05.730> imagining 00:47:06.349 --> 00:47:06.359 align:start position:0% you can already like start imagining 00:47:06.359 --> 00:47:08.180 align:start position:0% you can already like start imagining what<00:47:06.869> kind<00:47:07.109> of<00:47:07.170> solutions<00:47:07.619> you<00:47:07.710> can<00:47:07.859> build<00:47:08.039> on 00:47:08.180 --> 00:47:08.190 align:start position:0% what kind of solutions you can build on 00:47:08.190 --> 00:47:14.829 align:start position:0% what kind of solutions you can build on this<00:47:08.369> if<00:47:09.470> if<00:47:10.470> you<00:47:11.099> were<00:47:11.279> to<00:47:11.309> do<00:47:11.670> that<00:47:11.720> right 00:47:14.829 --> 00:47:14.839 align:start position:0% 00:47:14.839 --> 00:47:17.150 align:start position:0% what<00:47:15.839> do<00:47:15.900> you<00:47:15.960> guys<00:47:16.049> think<00:47:16.109> of<00:47:16.380> lazy<00:47:16.650> Leger 00:47:17.150 --> 00:47:17.160 align:start position:0% what do you guys think of lazy Leger 00:47:17.160 --> 00:47:21.170 align:start position:0% what do you guys think of lazy Leger hmm<00:47:18.210> I<00:47:19.160> mean<00:47:20.160> I<00:47:20.250> just<00:47:20.279> really<00:47:20.700> like<00:47:20.849> it<00:47:20.880> because 00:47:21.170 --> 00:47:21.180 align:start position:0% hmm I mean I just really like it because 00:47:21.180 --> 00:47:22.700 align:start position:0% hmm I mean I just really like it because it<00:47:21.390> seems<00:47:21.569> like<00:47:21.660> a<00:47:21.900> nice<00:47:22.079> separation<00:47:22.289> of 00:47:22.700 --> 00:47:22.710 align:start position:0% it seems like a nice separation of 00:47:22.710 --> 00:47:25.099 align:start position:0% it seems like a nice separation of concerns 00:47:25.099 --> 00:47:25.109 align:start position:0% 00:47:25.109 --> 00:47:28.730 align:start position:0% Oh<00:47:26.099> lazy<00:47:26.490> ledger<00:47:26.880> is<00:47:27.150> like<00:47:27.420> ace<00:47:27.740> minimalistic 00:47:28.730 --> 00:47:28.740 align:start position:0% Oh lazy ledger is like ace minimalistic 00:47:28.740 --> 00:47:31.789 align:start position:0% Oh lazy ledger is like ace minimalistic data<00:47:29.099> availability<00:47:29.700> engine<00:47:30.509> and<00:47:30.779> says<00:47:31.440> okay 00:47:31.789 --> 00:47:31.799 align:start position:0% data availability engine and says okay 00:47:31.799 --> 00:47:33.769 align:start position:0% data availability engine and says okay we're<00:47:32.009> going<00:47:32.190> to<00:47:32.309> provide<00:47:32.670> availability<00:47:33.630> and 00:47:33.769 --> 00:47:33.779 align:start position:0% we're going to provide availability and 00:47:33.779 --> 00:47:36.140 align:start position:0% we're going to provide availability and ordering<00:47:34.289> for<00:47:34.559> transactions<00:47:35.160> but<00:47:35.670> we<00:47:35.849> are<00:47:35.970> not 00:47:36.140 --> 00:47:36.150 align:start position:0% ordering for transactions but we are not 00:47:36.150 --> 00:47:41.150 align:start position:0% ordering for transactions but we are not going<00:47:36.450> to<00:47:36.750> necessarily<00:47:37.579> do<00:47:38.579> a<00:47:40.160> execution 00:47:41.150 --> 00:47:41.160 align:start position:0% going to necessarily do a execution 00:47:41.160 --> 00:47:43.009 align:start position:0% going to necessarily do a execution thing<00:47:41.369> so<00:47:41.549> people<00:47:41.789> can<00:47:41.910> essentially<00:47:42.299> execute 00:47:43.009 --> 00:47:43.019 align:start position:0% thing so people can essentially execute 00:47:43.019 --> 00:47:46.130 align:start position:0% thing so people can essentially execute based<00:47:43.529> on<00:47:43.890> the<00:47:44.549> you<00:47:45.029> know<00:47:45.150> data<00:47:45.480> that<00:47:45.869> is 00:47:46.130 --> 00:47:46.140 align:start position:0% based on the you know data that is 00:47:46.140 --> 00:47:51.470 align:start position:0% based on the you know data that is provided<00:47:46.740> by<00:47:47.250> the<00:47:47.309> lazy<00:47:47.700> ledger 00:47:51.470 --> 00:47:51.480 align:start position:0% 00:47:51.480 --> 00:47:53.749 align:start position:0% it's<00:47:51.900> your<00:47:52.049> grace<00:47:52.289> your<00:47:52.440> encoding<00:47:52.769> and<00:47:53.279> some 00:47:53.749 --> 00:47:53.759 align:start position:0% it's your grace your encoding and some 00:47:53.759 --> 00:48:04.480 align:start position:0% it's your grace your encoding and some it's<00:47:54.059> like<00:47:54.210> a<00:47:54.240> pretty<00:47:55.079> nice<00:47:55.380> simple<00:47:55.859> scheme 00:48:04.480 --> 00:48:04.490 align:start position:0% 00:48:04.490 --> 00:48:06.950 align:start position:0% okay<00:48:05.490> so<00:48:05.549> in<00:48:06.150> general<00:48:06.569> I<00:48:06.660> think<00:48:06.720> that 00:48:06.950 --> 00:48:06.960 align:start position:0% okay so in general I think that 00:48:06.960 --> 00:48:08.569 align:start position:0% okay so in general I think that solutions<00:48:07.440> like<00:48:07.589> that<00:48:07.619> require<00:48:08.190> you<00:48:08.279> to<00:48:08.369> log 00:48:08.569 --> 00:48:08.579 align:start position:0% solutions like that require you to log 00:48:08.579 --> 00:48:11.150 align:start position:0% solutions like that require you to log over<00:48:08.819> as<00:48:09.329> much<00:48:09.599> capital<00:48:09.900> a<00:48:10.200> lot<00:48:10.589> of<00:48:10.680> capital 00:48:11.150 --> 00:48:11.160 align:start position:0% over as much capital a lot of capital 00:48:11.160 --> 00:48:13.039 align:start position:0% over as much capital a lot of capital and<00:48:11.400> they<00:48:11.819> don't<00:48:11.970> love<00:48:12.119> you<00:48:12.299> no<00:48:12.390> more<00:48:12.450> capital 00:48:13.039 --> 00:48:13.049 align:start position:0% and they don't love you no more capital 00:48:13.049 --> 00:48:14.900 align:start position:0% and they don't love you no more capital than<00:48:13.079> you<00:48:13.380> can<00:48:13.589> transmit<00:48:14.339> a<00:48:14.400> new<00:48:14.549> system 00:48:14.900 --> 00:48:14.910 align:start position:0% than you can transmit a new system 00:48:14.910 --> 00:48:17.749 align:start position:0% than you can transmit a new system because<00:48:15.779> otherwise<00:48:16.200> someone<00:48:16.589> can<00:48:16.769> just 00:48:17.749 --> 00:48:17.759 align:start position:0% because otherwise someone can just 00:48:17.759 --> 00:48:19.940 align:start position:0% because otherwise someone can just disappear<00:48:18.210> the<00:48:18.599> data<00:48:18.809> you<00:48:19.500> can<00:48:19.680> update<00:48:19.829> your 00:48:19.940 --> 00:48:19.950 align:start position:0% disappear the data you can update your 00:48:19.950 --> 00:48:22.400 align:start position:0% disappear the data you can update your sister<00:48:20.430> so<00:48:21.029> like<00:48:21.240> the<00:48:21.390> I<00:48:21.720> think<00:48:21.900> I<00:48:22.079> will<00:48:22.259> this 00:48:22.400 --> 00:48:22.410 align:start position:0% sister so like the I think I will this 00:48:22.410 --> 00:48:24.859 align:start position:0% sister so like the I think I will this conduits<00:48:22.859> logical<00:48:23.490> conclusion<00:48:24.000> is<00:48:24.150> is<00:48:24.630> you 00:48:24.859 --> 00:48:24.869 align:start position:0% conduits logical conclusion is is you 00:48:24.869 --> 00:48:26.900 align:start position:0% conduits logical conclusion is is you have<00:48:24.900> the<00:48:25.170> whole<00:48:25.380> world's<00:48:25.859> transact<00:48:26.400> economy 00:48:26.900 --> 00:48:26.910 align:start position:0% have the whole world's transact economy 00:48:26.910 --> 00:48:29.059 align:start position:0% have the whole world's transact economy has<00:48:27.029> built<00:48:27.240> upon<00:48:27.359> this<00:48:27.690> like<00:48:28.019> lazy<00:48:28.500> Nigeria 00:48:29.059 --> 00:48:29.069 align:start position:0% has built upon this like lazy Nigeria 00:48:29.069 --> 00:48:34.339 align:start position:0% has built upon this like lazy Nigeria application<00:48:31.910> the<00:48:32.910> other<00:48:33.059> half<00:48:33.329> is<00:48:33.509> on<00:48:33.720> the 00:48:34.339 --> 00:48:34.349 align:start position:0% application the other half is on the 00:48:34.349 --> 00:48:38.690 align:start position:0% application the other half is on the positive<00:48:34.589> side<00:48:36.710> so<00:48:37.710> I<00:48:37.799> was<00:48:38.039> a<00:48:38.130> different<00:48:38.279> east 00:48:38.690 --> 00:48:38.700 align:start position:0% positive side so I was a different east 00:48:38.700 --> 00:48:43.700 align:start position:0% positive side so I was a different east to<00:48:38.990> well<00:48:39.990> east<00:48:40.440> to<00:48:40.799> is<00:48:42.049> okay<00:48:43.049> alright<00:48:43.559> so 00:48:43.700 --> 00:48:43.710 align:start position:0% to well east to is okay alright so 00:48:43.710 --> 00:48:45.170 align:start position:0% to well east to is okay alright so here's<00:48:44.220> the<00:48:44.309> difference<00:48:44.640> difference 00:48:45.170 --> 00:48:45.180 align:start position:0% here's the difference difference 00:48:45.180 --> 00:48:47.890 align:start position:0% here's the difference difference so<00:48:45.329> ease<00:48:45.720> to<00:48:46.170> enthuse<00:48:46.740> the<00:48:46.890> date<00:48:47.069> availability 00:48:47.890 --> 00:48:47.900 align:start position:0% so ease to enthuse the date availability 00:48:47.900 --> 00:48:49.630 align:start position:0% so ease to enthuse the date availability there<00:48:48.049> you<00:48:48.349> roll<00:48:48.650> back<00:48:48.680> the<00:48:48.980> chain<00:48:49.220> you 00:48:49.630 --> 00:48:49.640 align:start position:0% there you roll back the chain you 00:48:49.640 --> 00:48:51.519 align:start position:0% there you roll back the chain you recover<00:48:50.029> from<00:48:50.180> a<00:48:50.329> failure<00:48:50.359> so<00:48:51.140> you<00:48:51.230> roll<00:48:51.500> back 00:48:51.519 --> 00:48:51.529 align:start position:0% recover from a failure so you roll back 00:48:51.529 --> 00:48:52.900 align:start position:0% recover from a failure so you roll back the<00:48:51.740> chain<00:48:52.010> plus<00:48:52.279> you<00:48:52.430> roll<00:48:52.640> like<00:48:52.670> the 00:48:52.900 --> 00:48:52.910 align:start position:0% the chain plus you roll like the 00:48:52.910 --> 00:48:55.120 align:start position:0% the chain plus you roll like the execution<00:48:53.210> inches<00:48:53.690> but<00:48:54.260> it<00:48:54.319> lazy<00:48:54.619> Lecter<00:48:54.980> has 00:48:55.120 --> 00:48:55.130 align:start position:0% execution inches but it lazy Lecter has 00:48:55.130 --> 00:48:56.529 align:start position:0% execution inches but it lazy Lecter has that<00:48:55.309> because<00:48:55.549> it's<00:48:55.700> not<00:48:55.789> this<00:48:55.940> time<00:48:56.150> complete 00:48:56.529 --> 00:48:56.539 align:start position:0% that because it's not this time complete 00:48:56.539 --> 00:48:58.569 align:start position:0% that because it's not this time complete between<00:48:56.869> the<00:48:57.079> execution<00:48:57.559> engine<00:48:57.829> inability 00:48:58.569 --> 00:48:58.579 align:start position:0% between the execution engine inability 00:48:58.579 --> 00:49:00.910 align:start position:0% between the execution engine inability engine<00:48:59.450> you<00:48:59.990> won't<00:49:00.140> be<00:49:00.260> able<00:49:00.349> to<00:49:00.440> roll<00:49:00.589> you 00:49:00.910 --> 00:49:00.920 align:start position:0% engine you won't be able to roll you 00:49:00.920 --> 00:49:02.140 align:start position:0% engine you won't be able to roll you roll<00:49:01.069> back<00:49:01.130> later<00:49:01.460> that<00:49:01.700> you're<00:49:01.819> a<00:49:01.970> good 00:49:02.140 --> 00:49:02.150 align:start position:0% roll back later that you're a good 00:49:02.150 --> 00:49:11.200 align:start position:0% roll back later that you're a good execution<00:49:02.510> and<00:49:02.839> you<00:49:08.529> do<00:49:09.529> that<00:49:10.029> if<00:49:11.029> you're 00:49:11.200 --> 00:49:11.210 align:start position:0% execution and you do that if you're 00:49:11.210 --> 00:49:14.170 align:start position:0% execution and you do that if you're talking<00:49:11.329> about<00:49:11.599> bass<00:49:12.289> one<00:49:12.559> on<00:49:12.680> e<00:49:12.799> 2<00:49:13.069> as<00:49:13.250> a<00:49:13.279> data 00:49:14.170 --> 00:49:14.180 align:start position:0% talking about bass one on e 2 as a data 00:49:14.180 --> 00:49:16.599 align:start position:0% talking about bass one on e 2 as a data view<00:49:14.329> ability<00:49:14.720> engine<00:49:15.079> with<00:49:15.609> without 00:49:16.599 --> 00:49:16.609 align:start position:0% view ability engine with without 00:49:16.609 --> 00:49:18.910 align:start position:0% view ability engine with without execution<00:49:17.270> and<00:49:17.869> this<00:49:17.990> rollback<00:49:18.380> is<00:49:18.529> happening 00:49:18.910 --> 00:49:18.920 align:start position:0% execution and this rollback is happening 00:49:18.920 --> 00:49:25.660 align:start position:0% execution and this rollback is happening an<00:49:19.190> e-form<00:49:20.029> contract<00:49:20.480> with<00:49:21.289> execution<00:49:24.670> all 00:49:25.660 --> 00:49:25.670 align:start position:0% an e-form contract with execution all 00:49:25.670 --> 00:49:28.210 align:start position:0% an e-form contract with execution all right<00:49:25.819> we're<00:49:26.240> gonna<00:49:26.390> take<00:49:26.660> you<00:49:26.750> short<00:49:26.990> break 00:49:28.210 --> 00:49:28.220 align:start position:0% right we're gonna take you short break 00:49:28.220 --> 00:49:31.539 align:start position:0% right we're gonna take you short break I<00:49:28.750> think<00:49:29.750> phase<00:49:30.559> 1<00:49:30.829> gives<00:49:31.250> you<00:49:31.369> data 00:49:31.539 --> 00:49:31.549 align:start position:0% I think phase 1 gives you data 00:49:31.549 --> 00:49:33.220 align:start position:0% I think phase 1 gives you data availability<00:49:32.089> all<00:49:32.630> right<00:49:32.779> it's<00:49:33.079> like<00:49:33.170> a 00:49:33.220 --> 00:49:33.230 align:start position:0% availability all right it's like a 00:49:33.230 --> 00:49:36.039 align:start position:0% availability all right it's like a stronger<00:49:33.770> and<00:49:34.069> even<00:49:34.569> they<00:49:35.569> know<00:49:35.750> that<00:49:35.930> you 00:49:36.039 --> 00:49:36.049 align:start position:0% stronger and even they know that you 00:49:36.049 --> 00:49:46.390 align:start position:0% stronger and even they know that you guys<00:49:36.319> order<00:49:37.279> stays<00:49:38.240> there<00:49:44.619> cool<00:49:45.619> so<00:49:45.890> this<00:49:46.250> is 00:49:46.390 --> 00:49:46.400 align:start position:0% guys order stays there cool so this is 00:49:46.400 --> 00:49:47.740 align:start position:0% guys order stays there cool so this is to<00:49:46.549> give<00:49:46.730> an<00:49:46.849> overview<00:49:47.089> so<00:49:47.240> you<00:49:47.359> guys<00:49:47.510> have<00:49:47.720> a 00:49:47.740 --> 00:49:47.750 align:start position:0% to give an overview so you guys have a 00:49:47.750 --> 00:49:49.329 align:start position:0% to give an overview so you guys have a general<00:49:48.109> understanding<00:49:48.200> things<00:49:48.770> too<00:49:49.099> and 00:49:49.329 --> 00:49:49.339 align:start position:0% general understanding things too and 00:49:49.339 --> 00:49:51.490 align:start position:0% general understanding things too and then<00:49:49.579> we'll<00:49:49.760> dive<00:49:49.970> into<00:49:50.029> the<00:49:50.500> Devex 00:49:51.490 --> 00:49:51.500 align:start position:0% then we'll dive into the Devex 00:49:51.500 --> 00:49:57.010 align:start position:0% then we'll dive into the Devex discussions<00:49:52.630> so<00:49:54.130> yeah<00:49:55.130> I<00:49:55.369> gave<00:49:55.940> it<00:49:56.329> talking 00:49:57.010 --> 00:49:57.020 align:start position:0% discussions so yeah I gave it talking 00:49:57.020 --> 00:49:58.720 align:start position:0% discussions so yeah I gave it talking day<00:49:57.200> one<00:49:57.410> just<00:49:57.559> kind<00:49:57.859> of<00:49:57.950> gonna<00:49:58.220> be<00:49:58.309> similar<00:49:58.670> to 00:49:58.720 --> 00:49:58.730 align:start position:0% day one just kind of gonna be similar to 00:49:58.730 --> 00:50:00.730 align:start position:0% day one just kind of gonna be similar to that<00:49:59.119> but<00:49:59.329> I'm<00:49:59.420> gonna<00:49:59.539> freeze<00:49:59.930> over<00:50:00.470> a<00:50:00.500> lot 00:50:00.730 --> 00:50:00.740 align:start position:0% that but I'm gonna freeze over a lot 00:50:00.740 --> 00:50:03.120 align:start position:0% that but I'm gonna freeze over a lot more<00:50:01.299> we<00:50:02.299> go<00:50:02.390> through 00:50:03.120 --> 00:50:03.130 align:start position:0% more we go through 00:50:03.130 --> 00:50:07.180 align:start position:0% more we go through so<00:50:04.600> we<00:50:05.600> talked<00:50:05.810> about<00:50:05.930> PC<00:50:06.380> already<00:50:06.680> I<00:50:06.890> don't 00:50:07.180 --> 00:50:07.190 align:start position:0% so we talked about PC already I don't 00:50:07.190 --> 00:50:10.420 align:start position:0% so we talked about PC already I don't feel<00:50:07.310> like<00:50:07.430> I<00:50:07.460> need<00:50:07.670> to<00:50:07.700> cover<00:50:08.090> this<00:50:09.220> yosik<00:50:10.220> dip 00:50:10.420 --> 00:50:10.430 align:start position:0% feel like I need to cover this yosik dip 00:50:10.430 --> 00:50:12.730 align:start position:0% feel like I need to cover this yosik dip so<00:50:10.880> bigger<00:50:11.420> chains<00:50:11.660> kind<00:50:11.990> of<00:50:12.050> this<00:50:12.140> organizing 00:50:12.730 --> 00:50:12.740 align:start position:0% so bigger chains kind of this organizing 00:50:12.740 --> 00:50:14.640 align:start position:0% so bigger chains kind of this organizing layer<00:50:12.890> manages<00:50:13.490> the<00:50:13.580> cross<00:50:13.790> links<00:50:14.240> the 00:50:14.640 --> 00:50:14.650 align:start position:0% layer manages the cross links the 00:50:14.650 --> 00:50:18.670 align:start position:0% layer manages the cross links the finality<00:50:15.650> of<00:50:15.890> each<00:50:16.070> of<00:50:16.190> the<00:50:16.250> charts<00:50:16.580> so<00:50:17.680> then 00:50:18.670 --> 00:50:18.680 align:start position:0% finality of each of the charts so then 00:50:18.680 --> 00:50:20.020 align:start position:0% finality of each of the charts so then face<00:50:19.130> one<00:50:19.340> we<00:50:19.460> already<00:50:19.640> just<00:50:19.670> talked<00:50:19.970> about 00:50:20.020 --> 00:50:20.030 align:start position:0% face one we already just talked about 00:50:20.030 --> 00:50:22.120 align:start position:0% face one we already just talked about this<00:50:20.300> shards<00:50:20.780> it's<00:50:20.930> date<00:50:21.140> availability<00:50:21.620> other 00:50:22.120 --> 00:50:22.130 align:start position:0% this shards it's date availability other 00:50:22.130 --> 00:50:27.970 align:start position:0% this shards it's date availability other players<00:50:23.110> so<00:50:24.110> we<00:50:24.470> get<00:50:24.890> that<00:50:25.690> on<00:50:26.690> phase<00:50:27.050> two<00:50:27.290> this 00:50:27.970 --> 00:50:27.980 align:start position:0% players so we get that on phase two this 00:50:27.980 --> 00:50:29.830 align:start position:0% players so we get that on phase two this is<00:50:28.070> where<00:50:28.220> I<00:50:28.250> say<00:50:28.460> it<00:50:28.520> brings<00:50:28.730> the<00:50:29.000> shards<00:50:29.360> to 00:50:29.830 --> 00:50:29.840 align:start position:0% is where I say it brings the shards to 00:50:29.840 --> 00:50:32.140 align:start position:0% is where I say it brings the shards to life<00:50:30.170> even<00:50:30.620> more<00:50:30.830> because<00:50:31.490> now<00:50:31.730> they<00:50:31.880> have 00:50:32.140 --> 00:50:32.150 align:start position:0% life even more because now they have 00:50:32.150 --> 00:50:34.600 align:start position:0% life even more because now they have stated<00:50:32.480> to<00:50:32.570> keep<00:50:32.810> it<00:50:33.040> enough<00:50:34.040> so<00:50:34.220> that<00:50:34.250> we<00:50:34.460> can 00:50:34.600 --> 00:50:34.610 align:start position:0% stated to keep it enough so that we can 00:50:34.610 --> 00:50:38.730 align:start position:0% stated to keep it enough so that we can do<00:50:35.030> generalize<00:50:36.020> computation<00:50:36.680> layer<00:50:37.070> protocol 00:50:38.730 --> 00:50:38.740 align:start position:0% do generalize computation layer protocol 00:50:38.740 --> 00:50:41.350 align:start position:0% do generalize computation layer protocol so<00:50:39.740> it<00:50:39.770> kind<00:50:40.130> of<00:50:40.190> give<00:50:40.310> you<00:50:40.400> guys<00:50:40.550> an<00:50:40.940> overview 00:50:41.350 --> 00:50:41.360 align:start position:0% so it kind of give you guys an overview 00:50:41.360 --> 00:50:44.350 align:start position:0% so it kind of give you guys an overview so<00:50:41.630> to<00:50:42.260> help<00:50:42.410> you<00:50:42.530> understand<00:50:42.980> that<00:50:43.340> new<00:50:43.730> I 00:50:44.350 --> 00:50:44.360 align:start position:0% so to help you understand that new I 00:50:44.360 --> 00:50:47.050 align:start position:0% so to help you understand that new I guess<00:50:44.780> framework<00:50:45.380> by<00:50:45.620> which<00:50:45.730> phase<00:50:46.730> two<00:50:47.000> is 00:50:47.050 --> 00:50:47.060 align:start position:0% guess framework by which phase two is 00:50:47.060 --> 00:50:49.510 align:start position:0% guess framework by which phase two is being<00:50:47.300> proposed<00:50:47.770> it's<00:50:48.770> all<00:50:48.920> about<00:50:49.130> these 00:50:49.510 --> 00:50:49.520 align:start position:0% being proposed it's all about these 00:50:49.520 --> 00:50:51.280 align:start position:0% being proposed it's all about these things<00:50:49.730> called<00:50:49.940> execution<00:50:50.510> environments<00:50:51.080> and 00:50:51.280 --> 00:50:51.290 align:start position:0% things called execution environments and 00:50:51.290 --> 00:50:52.630 align:start position:0% things called execution environments and so<00:50:51.470> I'm<00:50:51.650> going<00:50:51.800> to<00:50:51.830> give<00:50:51.980> you<00:50:52.040> an<00:50:52.130> example<00:50:52.370> from 00:50:52.630 --> 00:50:52.640 align:start position:0% so I'm going to give you an example from 00:50:52.640 --> 00:50:54.280 align:start position:0% so I'm going to give you an example from each<00:50:53.360> one 00:50:54.280 --> 00:50:54.290 align:start position:0% each one 00:50:54.290 --> 00:50:56.800 align:start position:0% each one hopefully<00:50:55.220> that<00:50:55.400> extends<00:50:56.060> your<00:50:56.090> mental<00:50:56.780> model 00:50:56.800 --> 00:50:56.810 align:start position:0% hopefully that extends your mental model 00:50:56.810 --> 00:51:00.280 align:start position:0% hopefully that extends your mental model appropriately<00:50:57.740> so<00:50:58.510> needs<00:50:59.510> why<00:50:59.720> we<00:50:59.930> can<00:51:00.080> say 00:51:00.280 --> 00:51:00.290 align:start position:0% appropriately so needs why we can say 00:51:00.290 --> 00:51:04.140 align:start position:0% appropriately so needs why we can say that<00:51:00.320> there<00:51:00.800> is<00:51:00.830> one<00:51:01.870> execution<00:51:02.870> framework<00:51:03.410> or 00:51:04.140 --> 00:51:04.150 align:start position:0% that there is one execution framework or 00:51:04.150 --> 00:51:06.790 align:start position:0% that there is one execution framework or one<00:51:05.150> execution<00:51:05.630> environment<00:51:06.230> and<00:51:06.350> it's<00:51:06.470> just 00:51:06.790 --> 00:51:06.800 align:start position:0% one execution environment and it's just 00:51:06.800 --> 00:51:08.950 align:start position:0% one execution environment and it's just enshrined<00:51:07.340> into<00:51:07.580> the<00:51:08.060> core<00:51:08.420> Keith's<00:51:08.690> one 00:51:08.950 --> 00:51:08.960 align:start position:0% enshrined into the core Keith's one 00:51:08.960 --> 00:51:12.430 align:start position:0% enshrined into the core Keith's one protocol<00:51:09.470> are<00:51:10.220> decoded<00:51:10.960> it's<00:51:11.960> hard<00:51:12.140> coded 00:51:12.430 --> 00:51:12.440 align:start position:0% protocol are decoded it's hard coded 00:51:12.440 --> 00:51:15.070 align:start position:0% protocol are decoded it's hard coded into<00:51:12.560> the<00:51:12.740> nodes<00:51:13.540> so<00:51:14.540> if<00:51:14.600> you<00:51:14.660> want<00:51:14.810> to<00:51:14.870> change 00:51:15.070 --> 00:51:15.080 align:start position:0% into the nodes so if you want to change 00:51:15.080 --> 00:51:17.440 align:start position:0% into the nodes so if you want to change it<00:51:15.290> you<00:51:15.320> have<00:51:16.070> to<00:51:16.190> fork<00:51:16.490> and<00:51:16.730> so<00:51:16.910> a<00:51:16.940> really<00:51:17.300> good 00:51:17.440 --> 00:51:17.450 align:start position:0% it you have to fork and so a really good 00:51:17.450 --> 00:51:20.470 align:start position:0% it you have to fork and so a really good example<00:51:17.510> is<00:51:18.080> a<00:51:18.200> transaction<00:51:18.710> anyone<00:51:19.480> has 00:51:20.470 --> 00:51:20.480 align:start position:0% example is a transaction anyone has 00:51:20.480 --> 00:51:22.510 align:start position:0% example is a transaction anyone has nonce<00:51:20.840> gas<00:51:21.140> price<00:51:21.440> guess<00:51:21.740> let<00:51:21.950> me<00:51:21.980> to<00:51:22.220> value 00:51:22.510 --> 00:51:22.520 align:start position:0% nonce gas price guess let me to value 00:51:22.520 --> 00:51:24.820 align:start position:0% nonce gas price guess let me to value data<00:51:22.820> all<00:51:23.120> these<00:51:23.270> fields<00:51:23.690> uses<00:51:24.500> our<00:51:24.590> LP 00:51:24.820 --> 00:51:24.830 align:start position:0% data all these fields uses our LP 00:51:24.830 --> 00:51:28.360 align:start position:0% data all these fields uses our LP encoding<00:51:25.450> and<00:51:26.620> if<00:51:27.620> you<00:51:27.740> want<00:51:27.890> to<00:51:27.980> change<00:51:28.070> any 00:51:28.360 --> 00:51:28.370 align:start position:0% encoding and if you want to change any 00:51:28.370 --> 00:51:29.980 align:start position:0% encoding and if you want to change any of<00:51:28.460> this<00:51:28.610> if<00:51:28.850> you<00:51:28.940> want<00:51:29.090> to<00:51:29.150> add<00:51:29.300> a<00:51:29.330> field<00:51:29.600> you 00:51:29.980 --> 00:51:29.990 align:start position:0% of this if you want to add a field you 00:51:29.990 --> 00:51:32.440 align:start position:0% of this if you want to add a field you want<00:51:30.170> to<00:51:30.290> pick<00:51:30.650> it<00:51:30.770> up<00:51:30.890> adjusts<00:51:31.430> use<00:51:32.180> some 00:51:32.440 --> 00:51:32.450 align:start position:0% want to pick it up adjusts use some 00:51:32.450 --> 00:51:35.350 align:start position:0% want to pick it up adjusts use some other<00:51:32.570> an<00:51:32.870> encoding<00:51:33.140> schema<00:51:34.180> the<00:51:35.180> way<00:51:35.300> to 00:51:35.350 --> 00:51:35.360 align:start position:0% other an encoding schema the way to 00:51:35.360 --> 00:51:37.410 align:start position:0% other an encoding schema the way to change<00:51:35.570> that<00:51:35.870> is<00:51:36.110> you<00:51:36.350> have<00:51:36.500> to<00:51:36.620> change<00:51:36.860> the 00:51:37.410 --> 00:51:37.420 align:start position:0% change that is you have to change the 00:51:37.420 --> 00:51:40.720 align:start position:0% change that is you have to change the big<00:51:38.420> Corp<00:51:38.950> protocol<00:51:39.950> right<00:51:40.070> imminent<00:51:40.520> so<00:51:40.640> you 00:51:40.720 --> 00:51:40.730 align:start position:0% big Corp protocol right imminent so you 00:51:40.730 --> 00:51:42.720 align:start position:0% big Corp protocol right imminent so you have<00:51:40.910> to<00:51:41.060> do<00:51:41.210> you<00:51:41.480> have<00:51:41.540> to<00:51:41.690> do<00:51:41.810> for<00:51:41.990> can<00:51:42.200> change 00:51:42.720 --> 00:51:42.730 align:start position:0% have to do you have to do for can change 00:51:42.730 --> 00:51:47.740 align:start position:0% have to do you have to do for can change chained<00:51:43.730> together<00:51:45.670> similarly<00:51:46.670> like<00:51:47.540> you<00:51:47.660> know 00:51:47.740 --> 00:51:47.750 align:start position:0% chained together similarly like you know 00:51:47.750 --> 00:51:52.450 align:start position:0% chained together similarly like you know in<00:51:47.930> he's<00:51:48.260> won<00:51:48.500> the<00:51:49.280> global<00:51:49.670> state<00:51:50.030> is<00:51:51.460> managed 00:51:52.450 --> 00:51:52.460 align:start position:0% in he's won the global state is managed 00:51:52.460 --> 00:51:56.530 align:start position:0% in he's won the global state is managed by<00:51:52.550> a<00:51:52.940> petitioner<00:51:53.570> or<00:51:53.930> golden<00:51:54.290> tree<00:51:54.530> and<00:51:55.540> each 00:51:56.530 --> 00:51:56.540 align:start position:0% by a petitioner or golden tree and each 00:51:56.540 --> 00:52:00.070 align:start position:0% by a petitioner or golden tree and each of<00:51:56.750> calories<00:51:57.230> leaf<00:51:58.180> kind<00:51:59.180> of<00:51:59.270> has<00:51:59.870> these 00:52:00.070 --> 00:52:00.080 align:start position:0% of calories leaf kind of has these 00:52:00.080 --> 00:52:01.820 align:start position:0% of calories leaf kind of has these fields<00:52:00.500> nonce<00:52:00.710> balance<00:52:01.190> storage 00:52:01.820 --> 00:52:01.830 align:start position:0% fields nonce balance storage 00:52:01.830 --> 00:52:05.660 align:start position:0% fields nonce balance storage Oh<00:52:01.860> -<00:52:03.080> so<00:52:04.080> if<00:52:04.170> you<00:52:04.230> want<00:52:04.380> to<00:52:04.440> change<00:52:04.680> that<00:52:05.280> is 00:52:05.660 --> 00:52:05.670 align:start position:0% Oh - so if you want to change that is 00:52:05.670 --> 00:52:06.980 align:start position:0% Oh - so if you want to change that is well<00:52:05.820> the<00:52:06.000> accounts<00:52:06.300> director<00:52:06.600> if<00:52:06.720> you<00:52:06.780> want 00:52:06.980 --> 00:52:06.990 align:start position:0% well the accounts director if you want 00:52:06.990 --> 00:52:10.790 align:start position:0% well the accounts director if you want to<00:52:07.110> add<00:52:07.530> field<00:52:08.040> use<00:52:08.940> different<00:52:09.800> different 00:52:10.790 --> 00:52:10.800 align:start position:0% to add field use different different 00:52:10.800 --> 00:52:12.320 align:start position:0% to add field use different different accumulators<00:52:11.370> so<00:52:11.550> it's<00:52:11.700> an<00:52:11.790> attrition<00:52:12.210> of 00:52:12.320 --> 00:52:12.330 align:start position:0% accumulators so it's an attrition of 00:52:12.330 --> 00:52:14.780 align:start position:0% accumulators so it's an attrition of Michael<00:52:12.600> tree<00:52:12.750> or<00:52:12.960> anything<00:52:13.710> like<00:52:13.890> that<00:52:13.950> again 00:52:14.780 --> 00:52:14.790 align:start position:0% Michael tree or anything like that again 00:52:14.790 --> 00:52:17.030 align:start position:0% Michael tree or anything like that again it's<00:52:15.180> the<00:52:15.330> same<00:52:15.840> thing<00:52:16.050> we<00:52:16.200> have<00:52:16.350> to<00:52:16.530> we<00:52:16.920> would 00:52:17.030 --> 00:52:17.040 align:start position:0% it's the same thing we have to we would 00:52:17.040 --> 00:52:19.400 align:start position:0% it's the same thing we have to we would have<00:52:17.190> to<00:52:17.310> do<00:52:17.460> you<00:52:17.850> know<00:52:17.970> before<00:52:18.330> on<00:52:18.660> and<00:52:19.170> want 00:52:19.400 --> 00:52:19.410 align:start position:0% have to do you know before on and want 00:52:19.410 --> 00:52:21.560 align:start position:0% have to do you know before on and want to<00:52:19.440> change<00:52:19.650> that<00:52:19.940> except<00:52:20.940> a<00:52:20.970> review<00:52:21.270> that<00:52:21.420> it's 00:52:21.560 --> 00:52:21.570 align:start position:0% to change that except a review that it's 00:52:21.570 --> 00:52:23.030 align:start position:0% to change that except a review that it's basically<00:52:21.870> each<00:52:22.110> one<00:52:22.140> we<00:52:22.470> just<00:52:22.500> have<00:52:22.770> one 00:52:23.030 --> 00:52:23.040 align:start position:0% basically each one we just have one 00:52:23.040 --> 00:52:24.890 align:start position:0% basically each one we just have one transaction<00:52:23.880> framework<00:52:24.480> we<00:52:24.630> have<00:52:24.720> one 00:52:24.890 --> 00:52:24.900 align:start position:0% transaction framework we have one 00:52:24.900 --> 00:52:26.900 align:start position:0% transaction framework we have one execution<00:52:25.380> framework<00:52:25.920> we<00:52:26.610> have<00:52:26.640> one 00:52:26.900 --> 00:52:26.910 align:start position:0% execution framework we have one 00:52:26.910 --> 00:52:28.310 align:start position:0% execution framework we have one execution<00:52:27.390> environment<00:52:27.990> that<00:52:28.140> is 00:52:28.310 --> 00:52:28.320 align:start position:0% execution environment that is 00:52:28.320 --> 00:52:32.860 align:start position:0% execution environment that is essentially<00:52:28.940> hard-coded<00:52:29.940> into<00:52:30.090> this<00:52:30.570> system 00:52:32.860 --> 00:52:32.870 align:start position:0% essentially hard-coded into this system 00:52:32.870 --> 00:52:37.250 align:start position:0% essentially hard-coded into this system so<00:52:34.100> if<00:52:35.100> two<00:52:35.580> kind<00:52:35.940> of<00:52:35.970> took<00:52:36.210> takes<00:52:36.780> more<00:52:37.080> of<00:52:37.140> a 00:52:37.250 --> 00:52:37.260 align:start position:0% so if two kind of took takes more of a 00:52:37.260 --> 00:52:40.970 align:start position:0% so if two kind of took takes more of a radical<00:52:37.650> shift<00:52:38.240> and<00:52:39.240> it<00:52:39.360> says<00:52:39.600> you<00:52:40.080> know<00:52:40.200> the 00:52:40.970 --> 00:52:40.980 align:start position:0% radical shift and it says you know the 00:52:40.980 --> 00:52:42.830 align:start position:0% radical shift and it says you know the core<00:52:41.430> consensus<00:52:41.940> doesn't<00:52:42.240> really<00:52:42.480> need<00:52:42.720> to 00:52:42.830 --> 00:52:42.840 align:start position:0% core consensus doesn't really need to 00:52:42.840 --> 00:52:45.350 align:start position:0% core consensus doesn't really need to have<00:52:43.050> a<00:52:43.380> strong<00:52:43.980> hard<00:52:44.460> coded<00:52:44.760> opinion<00:52:45.150> on 00:52:45.350 --> 00:52:45.360 align:start position:0% have a strong hard coded opinion on 00:52:45.360 --> 00:52:47.810 align:start position:0% have a strong hard coded opinion on transaction<00:52:45.930> structure<00:52:46.350> the<00:52:47.340> consensus 00:52:47.810 --> 00:52:47.820 align:start position:0% transaction structure the consensus 00:52:47.820 --> 00:52:49.670 align:start position:0% transaction structure the consensus layers<00:52:48.030> good<00:52:48.930> at<00:52:49.020> managing<00:52:49.170> a<00:52:49.440> lot<00:52:49.560> of 00:52:49.670 --> 00:52:49.680 align:start position:0% layers good at managing a lot of 00:52:49.680 --> 00:52:50.720 align:start position:0% layers good at managing a lot of overhead<00:52:50.010> logic 00:52:50.720 --> 00:52:50.730 align:start position:0% overhead logic 00:52:50.730 --> 00:52:53.450 align:start position:0% overhead logic this<00:52:51.420> is<00:52:51.600> ordering<00:52:52.350> of<00:52:52.470> blocks<00:52:52.770> for<00:52:53.250> choice 00:52:53.450 --> 00:52:53.460 align:start position:0% this is ordering of blocks for choice 00:52:53.460 --> 00:52:56.840 align:start position:0% this is ordering of blocks for choice rules<00:52:54.590> execution<00:52:55.590> tooling<00:52:55.980> right<00:52:56.280> so<00:52:56.550> this<00:52:56.700> is 00:52:56.840 --> 00:52:56.850 align:start position:0% rules execution tooling right so this is 00:52:56.850 --> 00:53:00.140 align:start position:0% rules execution tooling right so this is the<00:52:56.970> UI<00:52:57.120> zone<00:52:58.310> splashing<00:52:59.310> rewards<00:52:59.940> and<00:53:00.060> the 00:53:00.140 --> 00:53:00.150 align:start position:0% the UI zone splashing rewards and the 00:53:00.150 --> 00:53:02.180 align:start position:0% the UI zone splashing rewards and the validators<00:53:00.720> different<00:53:01.320> things<00:53:01.440> like<00:53:01.590> that 00:53:02.180 --> 00:53:02.190 align:start position:0% validators different things like that 00:53:02.190 --> 00:53:04.160 align:start position:0% validators different things like that and<00:53:03.000> so<00:53:03.210> it<00:53:03.420> takes<00:53:03.540> kind<00:53:03.810> of<00:53:03.870> this<00:53:03.960> radical 00:53:04.160 --> 00:53:04.170 align:start position:0% and so it takes kind of this radical 00:53:04.170 --> 00:53:05.690 align:start position:0% and so it takes kind of this radical shift<00:53:04.620> that<00:53:04.770> the<00:53:04.830> core<00:53:05.100> protocol<00:53:05.460> doesn't 00:53:05.690 --> 00:53:05.700 align:start position:0% shift that the core protocol doesn't 00:53:05.700 --> 00:53:07.460 align:start position:0% shift that the core protocol doesn't need<00:53:05.820> to<00:53:05.910> actually<00:53:06.060> have<00:53:06.570> a<00:53:06.600> strong<00:53:07.230> opinion 00:53:07.460 --> 00:53:07.470 align:start position:0% need to actually have a strong opinion 00:53:07.470 --> 00:53:09.320 align:start position:0% need to actually have a strong opinion on<00:53:07.800> what<00:53:08.070> a<00:53:08.100> transaction<00:53:08.700> structure<00:53:09.150> looks 00:53:09.320 --> 00:53:09.330 align:start position:0% on what a transaction structure looks 00:53:09.330 --> 00:53:12.860 align:start position:0% on what a transaction structure looks like<00:53:09.650> or<00:53:10.650> what<00:53:10.890> you<00:53:11.250> know<00:53:11.370> how<00:53:11.550> an<00:53:11.850> account<00:53:12.570> is 00:53:12.860 --> 00:53:12.870 align:start position:0% like or what you know how an account is 00:53:12.870 --> 00:53:16.190 align:start position:0% like or what you know how an account is organized<00:53:13.590> fields<00:53:14.190> or<00:53:14.310> accounts<00:53:14.850> in<00:53:15.660> fact<00:53:15.960> you 00:53:16.190 --> 00:53:16.200 align:start position:0% organized fields or accounts in fact you 00:53:16.200 --> 00:53:18.740 align:start position:0% organized fields or accounts in fact you can<00:53:16.410> you<00:53:16.710> can<00:53:16.890> support<00:53:17.220> multiple<00:53:17.430> in<00:53:18.390> the<00:53:18.540> same 00:53:18.740 --> 00:53:18.750 align:start position:0% can you can support multiple in the same 00:53:18.750 --> 00:53:23.660 align:start position:0% can you can support multiple in the same o<00:53:19.520> in<00:53:20.520> the<00:53:20.640> same<00:53:20.820> shard<00:53:21.120> and<00:53:22.010> so<00:53:23.010> this<00:53:23.250> is<00:53:23.580> the 00:53:23.660 --> 00:53:23.670 align:start position:0% o in the same shard and so this is the 00:53:23.670 --> 00:53:25.280 align:start position:0% o in the same shard and so this is the radical<00:53:23.820> shift<00:53:24.330> that<00:53:24.570> we<00:53:24.750> no<00:53:25.020> longer<00:53:25.050> just 00:53:25.280 --> 00:53:25.290 align:start position:0% radical shift that we no longer just 00:53:25.290 --> 00:53:27.970 align:start position:0% radical shift that we no longer just have<00:53:25.470> one<00:53:25.800> enshrined<00:53:26.340> hard-coded 00:53:27.970 --> 00:53:27.980 align:start position:0% have one enshrined hard-coded 00:53:27.980 --> 00:53:31.670 align:start position:0% have one enshrined hard-coded transaction<00:53:28.980> system<00:53:29.910> or<00:53:30.320> account<00:53:31.320> framework 00:53:31.670 --> 00:53:31.680 align:start position:0% transaction system or account framework 00:53:31.680 --> 00:53:36.380 align:start position:0% transaction system or account framework and<00:53:32.280> so<00:53:34.160> this<00:53:35.160> is<00:53:35.250> kind<00:53:35.460> of<00:53:35.490> a<00:53:35.580> goofy<00:53:35.940> little 00:53:36.380 --> 00:53:36.390 align:start position:0% and so this is kind of a goofy little 00:53:36.390 --> 00:53:38.180 align:start position:0% and so this is kind of a goofy little diagram<00:53:36.930> but<00:53:37.080> I<00:53:37.140> think<00:53:37.320> it<00:53:37.410> like<00:53:37.650> helps<00:53:37.950> people 00:53:38.180 --> 00:53:38.190 align:start position:0% diagram but I think it like helps people 00:53:38.190 --> 00:53:40.880 align:start position:0% diagram but I think it like helps people understand<00:53:38.720> so<00:53:39.720> on<00:53:39.840> a<00:53:39.870> shard<00:53:40.170> it<00:53:40.320> needs<00:53:40.530> to<00:53:40.740> you 00:53:40.880 --> 00:53:40.890 align:start position:0% understand so on a shard it needs to you 00:53:40.890 --> 00:53:42.530 align:start position:0% understand so on a shard it needs to you can<00:53:41.010> have<00:53:41.160> multiple<00:53:41.370> execution<00:53:42.030> environments 00:53:42.530 --> 00:53:42.540 align:start position:0% can have multiple execution environments 00:53:42.540 --> 00:53:46.490 align:start position:0% can have multiple execution environments so<00:53:43.250> example<00:53:44.300> we're<00:53:45.300> gonna<00:53:45.390> bring<00:53:45.600> each<00:53:45.870> one<00:53:46.110> to 00:53:46.490 --> 00:53:46.500 align:start position:0% so example we're gonna bring each one to 00:53:46.500 --> 00:53:47.060 align:start position:0% so example we're gonna bring each one to a<00:53:46.530> shard 00:53:47.060 --> 00:53:47.070 align:start position:0% a shard 00:53:47.070 --> 00:53:49.310 align:start position:0% a shard right<00:53:47.340> and<00:53:47.550> so<00:53:47.700> even<00:53:48.510> one<00:53:48.600> itself<00:53:48.960> would<00:53:49.140> be<00:53:49.230> an 00:53:49.310 --> 00:53:49.320 align:start position:0% right and so even one itself would be an 00:53:49.320 --> 00:53:50.720 align:start position:0% right and so even one itself would be an execution<00:53:49.800> environment<00:53:50.190> so<00:53:50.340> here<00:53:50.550> we're 00:53:50.720 --> 00:53:50.730 align:start position:0% execution environment so here we're 00:53:50.730 --> 00:53:52.130 align:start position:0% execution environment so here we're saying<00:53:50.910> this<00:53:51.060> is<00:53:51.210> just<00:53:51.420> all<00:53:51.570> in<00:53:51.690> one<00:53:51.720> shard 00:53:52.130 --> 00:53:52.140 align:start position:0% saying this is just all in one shard 00:53:52.140 --> 00:53:52.950 align:start position:0% saying this is just all in one shard right<00:53:52.290> now<00:53:52.410> we're<00:53:52.560> not 00:53:52.950 --> 00:53:52.960 align:start position:0% right now we're not 00:53:52.960 --> 00:53:55.260 align:start position:0% right now we're not the<00:53:53.109> systems<00:53:53.440> of<00:53:53.559> wool<00:53:53.770> in<00:53:54.460> one<00:53:54.760> block<00:53:54.970> in<00:53:55.150> one 00:53:55.260 --> 00:53:55.270 align:start position:0% the systems of wool in one block in one 00:53:55.270 --> 00:53:57.930 align:start position:0% the systems of wool in one block in one shard<00:53:55.540> we<00:53:55.720> could<00:53:55.839> have<00:53:55.930> eat<00:53:56.230> one<00:53:56.770> running 00:53:57.930 --> 00:53:57.940 align:start position:0% shard we could have eat one running 00:53:57.940 --> 00:53:59.760 align:start position:0% shard we could have eat one running we<00:53:58.240> could<00:53:58.359> have<00:53:58.540> an<00:53:58.809> eighth<00:53:59.020> to<00:53:59.050> eat<00:53:59.470> which 00:53:59.760 --> 00:53:59.770 align:start position:0% we could have an eighth to eat which 00:53:59.770 --> 00:54:01.230 align:start position:0% we could have an eighth to eat which I'll<00:53:59.859> talk<00:54:00.010> about<00:54:00.069> in<00:54:00.280> a<00:54:00.430> second<00:54:00.849> which<00:54:01.059> is<00:54:01.089> a 00:54:01.230 --> 00:54:01.240 align:start position:0% I'll talk about in a second which is a 00:54:01.240 --> 00:54:04.290 align:start position:0% I'll talk about in a second which is a iterated<00:54:02.140> cattle<00:54:02.710> we<00:54:03.220> could<00:54:03.339> have<00:54:03.460> a<00:54:03.490> UTF<00:54:04.089> so 00:54:04.290 --> 00:54:04.300 align:start position:0% iterated cattle we could have a UTF so 00:54:04.300 --> 00:54:07.440 align:start position:0% iterated cattle we could have a UTF so like<00:54:04.720> you<00:54:05.200> know<00:54:05.290> if<00:54:05.500> my<00:54:05.710> model<00:54:05.980> we'd<00:54:06.280> have<00:54:06.520> a<00:54:06.819> ZK 00:54:07.440 --> 00:54:07.450 align:start position:0% like you know if my model we'd have a ZK 00:54:07.450 --> 00:54:10.020 align:start position:0% like you know if my model we'd have a ZK roll-ups<00:54:07.869> focused<00:54:08.490> execution<00:54:09.490> environment 00:54:10.020 --> 00:54:10.030 align:start position:0% roll-ups focused execution environment 00:54:10.030 --> 00:54:11.870 align:start position:0% roll-ups focused execution environment we<00:54:10.720> could<00:54:10.839> have<00:54:10.960> the<00:54:11.079> Libre 00:54:11.870 --> 00:54:11.880 align:start position:0% we could have the Libre 00:54:11.880 --> 00:54:17.250 align:start position:0% we could have the Libre move<00:54:12.880> running<00:54:13.390> on<00:54:13.720> YouTube<00:54:14.440> so<00:54:15.809> not<00:54:16.809> me<00:54:16.960> laughs 00:54:17.250 --> 00:54:17.260 align:start position:0% move running on YouTube so not me laughs 00:54:17.260 --> 00:54:19.650 align:start position:0% move running on YouTube so not me laughs but<00:54:17.829> we<00:54:17.920> could<00:54:18.130> you<00:54:18.460> know<00:54:18.520> just<00:54:19.119> to<00:54:19.240> like<00:54:19.420> kind 00:54:19.650 --> 00:54:19.660 align:start position:0% but we could you know just to like kind 00:54:19.660 --> 00:54:21.870 align:start position:0% but we could you know just to like kind of<00:54:19.690> give<00:54:19.900> give<00:54:20.920> illustration<00:54:21.520> here<00:54:21.640> and<00:54:21.790> so 00:54:21.870 --> 00:54:21.880 align:start position:0% of give give illustration here and so 00:54:21.880 --> 00:54:23.940 align:start position:0% of give give illustration here and so within<00:54:22.119> each<00:54:22.359> of<00:54:22.420> these<00:54:22.630> ETS<00:54:23.079> you<00:54:23.589> get<00:54:23.800> this 00:54:23.940 --> 00:54:23.950 align:start position:0% within each of these ETS you get this 00:54:23.950 --> 00:54:25.470 align:start position:0% within each of these ETS you get this synchronous<00:54:24.730> communication<00:54:24.880> within 00:54:25.470 --> 00:54:25.480 align:start position:0% synchronous communication within 00:54:25.480 --> 00:54:28.829 align:start position:0% synchronous communication within yourself<00:54:25.930> so<00:54:26.130> in<00:54:27.130> the<00:54:27.190> eighth<00:54:27.309> one<00:54:27.550> EE<00:54:27.839> nothing 00:54:28.829 --> 00:54:28.839 align:start position:0% yourself so in the eighth one EE nothing 00:54:28.839 --> 00:54:30.809 align:start position:0% yourself so in the eighth one EE nothing really<00:54:28.990> changes<00:54:29.410> as<00:54:29.559> far<00:54:29.589> as<00:54:29.859> transactions<00:54:30.609> or 00:54:30.809 --> 00:54:30.819 align:start position:0% really changes as far as transactions or 00:54:30.819 --> 00:54:32.460 align:start position:0% really changes as far as transactions or contracts<00:54:31.329> meaningful<00:54:31.720> other<00:54:31.990> contracts 00:54:32.460 --> 00:54:32.470 align:start position:0% contracts meaningful other contracts 00:54:32.470 --> 00:54:35.040 align:start position:0% contracts meaningful other contracts synchronously<00:54:33.420> but<00:54:34.420> then<00:54:34.569> you<00:54:34.660> have<00:54:34.809> to<00:54:34.900> think 00:54:35.040 --> 00:54:35.050 align:start position:0% synchronously but then you have to think 00:54:35.050 --> 00:54:36.750 align:start position:0% synchronously but then you have to think about<00:54:35.170> these<00:54:35.440> communication<00:54:36.339> when<00:54:36.460> you<00:54:36.520> hop 00:54:36.750 --> 00:54:36.760 align:start position:0% about these communication when you hop 00:54:36.760 --> 00:54:39.359 align:start position:0% about these communication when you hop from<00:54:37.000> one<00:54:37.059> EEG<00:54:37.660> another<00:54:37.900> so<00:54:38.260> the<00:54:38.410> e20<00:54:38.920> es<00:54:39.160> that 00:54:39.359 --> 00:54:39.369 align:start position:0% from one EEG another so the e20 es that 00:54:39.369 --> 00:54:43.260 align:start position:0% from one EEG another so the e20 es that I<00:54:39.400> call<00:54:39.640> the<00:54:40.240> UTM<00:54:40.630> so<00:54:40.900> or<00:54:41.200> the<00:54:41.970> into<00:54:42.970> account 00:54:43.260 --> 00:54:43.270 align:start position:0% I call the UTM so or the into account 00:54:43.270 --> 00:54:47.670 align:start position:0% I call the UTM so or the into account Paulo<00:54:43.510> or<00:54:43.720> the<00:54:43.869> Libra<00:54:45.720> so<00:54:46.720> he<00:54:46.900> is<00:54:47.109> execution 00:54:47.670 --> 00:54:47.680 align:start position:0% Paulo or the Libra so he is execution 00:54:47.680 --> 00:54:49.260 align:start position:0% Paulo or the Libra so he is execution environment<00:54:48.160> like<00:54:48.819> I<00:54:48.849> said<00:54:49.059> you<00:54:49.150> definitely 00:54:49.260 --> 00:54:49.270 align:start position:0% environment like I said you definitely 00:54:49.270 --> 00:54:50.849 align:start position:0% environment like I said you definitely probably<00:54:49.690> have<00:54:50.050> a<00:54:50.290> lot<00:54:50.440> of<00:54:50.500> things<00:54:50.680> he<00:54:50.770> could 00:54:50.849 --> 00:54:50.859 align:start position:0% probably have a lot of things he could 00:54:50.859 --> 00:54:55.349 align:start position:0% probably have a lot of things he could hospital<00:54:51.849> interpreter<00:54:52.839> you<00:54:53.109> want<00:54:53.440> to<00:54:54.359> there's 00:54:55.349 --> 00:54:55.359 align:start position:0% hospital interpreter you want to there's 00:54:55.359 --> 00:54:57.559 align:start position:0% hospital interpreter you want to there's a<00:54:55.690> lot<00:54:56.140> you<00:54:56.170> can<00:54:56.349> do<00:54:56.500> this<00:54:56.619> left<00:54:56.829> flexibility 00:54:57.559 --> 00:54:57.569 align:start position:0% a lot you can do this left flexibility 00:54:57.569 --> 00:54:59.520 align:start position:0% a lot you can do this left flexibility so<00:54:58.569> tightly<00:54:58.780> deeper<00:54:59.140> what<00:54:59.319> does<00:54:59.440> this 00:54:59.520 --> 00:54:59.530 align:start position:0% so tightly deeper what does this 00:54:59.530 --> 00:55:00.839 align:start position:0% so tightly deeper what does this actually<00:54:59.740> look<00:54:59.920> like 00:55:00.839 --> 00:55:00.849 align:start position:0% actually look like 00:55:00.849 --> 00:55:03.030 align:start position:0% actually look like so<00:55:01.329> the<00:55:01.450> beacon<00:55:01.750> chain<00:55:01.960> stores<00:55:02.440> these<00:55:02.740> P 00:55:03.030 --> 00:55:03.040 align:start position:0% so the beacon chain stores these P 00:55:03.040 --> 00:55:06.359 align:start position:0% so the beacon chain stores these P reducing<00:55:03.490> functions<00:55:04.109> and<00:55:05.109> so<00:55:05.380> these<00:55:05.829> give<00:55:06.190> the 00:55:06.359 --> 00:55:06.369 align:start position:0% reducing functions and so these give the 00:55:06.369 --> 00:55:08.970 align:start position:0% reducing functions and so these give the rules<00:55:06.609> by<00:55:06.790> which<00:55:06.819> transactions<00:55:07.809> will<00:55:08.109> run<00:55:08.410> so 00:55:08.970 --> 00:55:08.980 align:start position:0% rules by which transactions will run so 00:55:08.980 --> 00:55:09.839 align:start position:0% rules by which transactions will run so this<00:55:09.220> gives<00:55:09.430> the<00:55:09.549> rules<00:55:09.700> by<00:55:09.819> which 00:55:09.839 --> 00:55:09.849 align:start position:0% this gives the rules by which 00:55:09.849 --> 00:55:14.280 align:start position:0% this gives the rules by which transactions<00:55:10.540> are<00:55:10.630> validated<00:55:11.339> and<00:55:12.339> will<00:55:13.290> it 00:55:14.280 --> 00:55:14.290 align:start position:0% transactions are validated and will it 00:55:14.290 --> 00:55:15.930 align:start position:0% transactions are validated and will it imbalance<00:55:14.950> what<00:55:15.220> the<00:55:15.339> actual<00:55:15.609> state 00:55:15.930 --> 00:55:15.940 align:start position:0% imbalance what the actual state 00:55:15.940 --> 00:55:18.180 align:start position:0% imbalance what the actual state transition<00:55:16.540> would<00:55:16.809> would<00:55:17.140> be<00:55:17.170> for<00:55:17.740> for<00:55:18.069> that 00:55:18.180 --> 00:55:18.190 align:start position:0% transition would would be for for that 00:55:18.190 --> 00:55:20.900 align:start position:0% transition would would be for for that EP<00:55:18.490> and<00:55:19.089> so<00:55:19.240> this<00:55:19.359> is<00:55:19.480> just<00:55:19.569> a<00:55:19.690> pure<00:55:19.990> wasn't 00:55:20.900 --> 00:55:20.910 align:start position:0% EP and so this is just a pure wasn't 00:55:20.910 --> 00:55:24.960 align:start position:0% EP and so this is just a pure wasn't wasn't<00:55:21.910> reducing<00:55:22.690> function<00:55:23.079> and<00:55:23.260> so<00:55:23.819> to<00:55:24.819> give 00:55:24.960 --> 00:55:24.970 align:start position:0% wasn't reducing function and so to give 00:55:24.970 --> 00:55:25.730 align:start position:0% wasn't reducing function and so to give an<00:55:25.059> example 00:55:25.730 --> 00:55:25.740 align:start position:0% an example 00:55:25.740 --> 00:55:28.920 align:start position:0% an example Keith<00:55:26.740> one<00:55:27.010> you<00:55:27.190> could<00:55:27.339> kind<00:55:27.549> of<00:55:27.609> consider<00:55:27.940> you 00:55:28.920 --> 00:55:28.930 align:start position:0% Keith one you could kind of consider you 00:55:28.930 --> 00:55:31.950 align:start position:0% Keith one you could kind of consider you have<00:55:29.079> a<00:55:29.109> state<00:55:29.410> right<00:55:30.480> even<00:55:31.480> function<00:55:31.839> never 00:55:31.950 --> 00:55:31.960 align:start position:0% have a state right even function never 00:55:31.960 --> 00:55:33.930 align:start position:0% have a state right even function never runs<00:55:32.200> that<00:55:32.650> function<00:55:33.099> has<00:55:33.309> a<00:55:33.609> bunch<00:55:33.849> of 00:55:33.930 --> 00:55:33.940 align:start position:0% runs that function has a bunch of 00:55:33.940 --> 00:55:37.470 align:start position:0% runs that function has a bunch of transaction<00:55:34.540> data<00:55:35.160> and<00:55:36.160> output<00:55:36.819> is<00:55:37.119> you<00:55:37.299> have 00:55:37.470 --> 00:55:37.480 align:start position:0% transaction data and output is you have 00:55:37.480 --> 00:55:41.700 align:start position:0% transaction data and output is you have a<00:55:37.599> new<00:55:37.720> state<00:55:37.960> state<00:55:38.290> price<00:55:38.520> as<00:55:39.520> Fred<00:55:40.500> and<00:55:41.500> Eve 00:55:41.700 --> 00:55:41.710 align:start position:0% a new state state price as Fred and Eve 00:55:41.710 --> 00:55:43.770 align:start position:0% a new state state price as Fred and Eve -<00:55:41.950> we<00:55:42.190> do<00:55:42.369> have<00:55:42.760> a<00:55:42.790> stateless<00:55:43.150> model<00:55:43.480> so<00:55:43.599> we<00:55:43.660> can 00:55:43.770 --> 00:55:43.780 align:start position:0% - we do have a stateless model so we can 00:55:43.780 --> 00:55:46.349 align:start position:0% - we do have a stateless model so we can say<00:55:43.900> this<00:55:44.020> is<00:55:44.170> actually<00:55:44.500> ported<00:55:45.030> because<00:55:46.030> now 00:55:46.349 --> 00:55:46.359 align:start position:0% say this is actually ported because now 00:55:46.359 --> 00:55:49.710 align:start position:0% say this is actually ported because now we<00:55:46.420> just<00:55:46.510> have<00:55:46.869> a<00:55:47.140> free<00:55:47.530> state<00:55:47.859> hash 00:55:49.710 --> 00:55:49.720 align:start position:0% we just have a free state hash 00:55:49.720 --> 00:55:51.340 align:start position:0% we just have a free state hash reduce<00:55:50.260> the<00:55:50.380> function 00:55:51.340 --> 00:55:51.350 align:start position:0% reduce the function 00:55:51.350 --> 00:55:56.140 align:start position:0% reduce the function it<00:55:51.410> produces<00:55:51.860> a<00:55:52.190> state<00:55:52.760> action<00:55:54.070> so<00:55:55.070> an<00:55:55.940> example 00:55:56.140 --> 00:55:56.150 align:start position:0% it produces a state action so an example 00:55:56.150 --> 00:55:59.530 align:start position:0% it produces a state action so an example here<00:55:56.510> each<00:55:57.440> shard<00:55:57.890> if<00:55:58.310> there's<00:55:58.790> a<00:55:58.880> transaction 00:55:59.530 --> 00:55:59.540 align:start position:0% here each shard if there's a transaction 00:55:59.540 --> 00:56:01.480 align:start position:0% here each shard if there's a transaction that<00:55:59.570> is<00:55:59.930> each<00:56:00.140> one<00:56:00.170> related<00:56:00.860> it<00:56:01.100> you<00:56:01.400> know 00:56:01.480 --> 00:56:01.490 align:start position:0% that is each one related it you know 00:56:01.490 --> 00:56:05.080 align:start position:0% that is each one related it you know pulls<00:56:02.060> down<00:56:02.360> the<00:56:02.780> watts<00:56:03.410> of<00:56:03.560> pure<00:56:04.460> reducible 00:56:05.080 --> 00:56:05.090 align:start position:0% pulls down the watts of pure reducible 00:56:05.090 --> 00:56:06.930 align:start position:0% pulls down the watts of pure reducible function<00:56:05.540> from<00:56:05.750> the<00:56:05.870> beacon<00:56:06.110> chain<00:56:06.350> and<00:56:06.620> then 00:56:06.930 --> 00:56:06.940 align:start position:0% function from the beacon chain and then 00:56:06.940 --> 00:56:09.940 align:start position:0% function from the beacon chain and then executes<00:56:07.940> this<00:56:08.240> package<00:56:09.140> of<00:56:09.260> transactions 00:56:09.940 --> 00:56:09.950 align:start position:0% executes this package of transactions 00:56:09.950 --> 00:56:13.060 align:start position:0% executes this package of transactions for<00:56:10.160> the<00:56:10.280> keys<00:56:10.460> one<00:56:10.700> EE<00:56:11.830> appropriately<00:56:12.830> and 00:56:13.060 --> 00:56:13.070 align:start position:0% for the keys one EE appropriately and 00:56:13.070 --> 00:56:15.940 align:start position:0% for the keys one EE appropriately and then<00:56:13.280> the<00:56:13.790> same<00:56:14.000> block<00:56:14.270> can<00:56:14.540> do<00:56:15.350> it<00:56:15.470> for<00:56:15.650> an 00:56:15.940 --> 00:56:15.950 align:start position:0% then the same block can do it for an 00:56:15.950 --> 00:56:17.620 align:start position:0% then the same block can do it for an account<00:56:16.280> model<00:56:16.610> and<00:56:17.120> I'll<00:56:17.210> talk<00:56:17.390> about<00:56:17.420> that 00:56:17.620 --> 00:56:17.630 align:start position:0% account model and I'll talk about that 00:56:17.630 --> 00:56:20.290 align:start position:0% account model and I'll talk about that in<00:56:17.870> a<00:56:17.900> second<00:56:18.320> or<00:56:18.470> fourth<00:56:18.830> and<00:56:19.760> you<00:56:19.850> can<00:56:20.060> still 00:56:20.290 --> 00:56:20.300 align:start position:0% in a second or fourth and you can still 00:56:20.300 --> 00:56:25.780 align:start position:0% in a second or fourth and you can still model<00:56:21.670> or<00:56:22.670> another<00:56:22.970> encounter<00:56:23.290> so<00:56:24.460> yeah<00:56:25.460> so 00:56:25.780 --> 00:56:25.790 align:start position:0% model or another encounter so yeah so 00:56:25.790 --> 00:56:28.150 align:start position:0% model or another encounter so yeah so we're<00:56:26.480> already<00:56:26.720> kind<00:56:27.230> of<00:56:27.350> you<00:56:27.590> know<00:56:27.710> play<00:56:27.920> with 00:56:28.150 --> 00:56:28.160 align:start position:0% we're already kind of you know play with 00:56:28.160 --> 00:56:32.560 align:start position:0% we're already kind of you know play with this<00:56:28.310> so<00:56:29.440> Alex<00:56:30.440> and<00:56:30.880> the<00:56:31.880> e<00:56:31.910> wasn't<00:56:32.360> team 00:56:32.560 --> 00:56:32.570 align:start position:0% this so Alex and the e wasn't team 00:56:32.570 --> 00:56:35.980 align:start position:0% this so Alex and the e wasn't team created<00:56:33.200> a<00:56:33.380> repo<00:56:34.070> called<00:56:34.430> scalp<00:56:35.240> which 00:56:35.980 --> 00:56:35.990 align:start position:0% created a repo called scalp which 00:56:35.990 --> 00:56:41.110 align:start position:0% created a repo called scalp which already<00:56:36.350> lets<00:56:36.620> you<00:56:37.240> to<00:56:38.740> prototyping<00:56:39.880> on<00:56:40.880> these 00:56:41.110 --> 00:56:41.120 align:start position:0% already lets you to prototyping on these 00:56:41.120 --> 00:56:43.060 align:start position:0% already lets you to prototyping on these execution<00:56:41.690> environments<00:56:42.170> and<00:56:42.320> again<00:56:42.740> this<00:56:42.890> is 00:56:43.060 --> 00:56:43.070 align:start position:0% execution environments and again this is 00:56:43.070 --> 00:56:44.260 align:start position:0% execution environments and again this is what<00:56:43.220> the<00:56:43.250> function<00:56:43.640> will<00:56:43.730> don't<00:56:43.880> like<00:56:44.060> it's 00:56:44.260 --> 00:56:44.270 align:start position:0% what the function will don't like it's 00:56:44.270 --> 00:56:46.500 align:start position:0% what the function will don't like it's across<00:56:44.750> this<00:56:44.960> block<00:56:45.200> takes<00:56:45.620> block<00:56:45.860> data 00:56:46.500 --> 00:56:46.510 align:start position:0% across this block takes block data 00:56:46.510 --> 00:56:49.270 align:start position:0% across this block takes block data pre-state<00:56:47.510> group<00:56:47.720> and<00:56:48.110> it<00:56:48.770> gives<00:56:48.890> you<00:56:49.010> a<00:56:49.070> post 00:56:49.270 --> 00:56:49.280 align:start position:0% pre-state group and it gives you a post 00:56:49.280 --> 00:56:53.550 align:start position:0% pre-state group and it gives you a post a<00:56:49.460> grid<00:56:49.640> hash<00:56:49.850> so<00:56:50.300> again<00:56:50.840> it's<00:56:50.990> exactly<00:56:51.530> this 00:56:53.550 --> 00:56:53.560 align:start position:0% a grid hash so again it's exactly this 00:56:53.560 --> 00:56:57.220 align:start position:0% a grid hash so again it's exactly this so<00:56:55.180> if<00:56:56.180> there's<00:56:56.390> something<00:56:56.720> here<00:56:57.080> and<00:56:57.170> maybe 00:56:57.220 --> 00:56:57.230 align:start position:0% so if there's something here and maybe 00:56:57.230 --> 00:56:58.780 align:start position:0% so if there's something here and maybe this<00:56:57.500> is<00:56:57.680> what<00:56:57.830> we<00:56:57.920> talked<00:56:58.310> about<00:56:58.340> today's 00:56:58.780 --> 00:56:58.790 align:start position:0% this is what we talked about today's 00:56:58.790 --> 00:57:00.160 align:start position:0% this is what we talked about today's execution<00:56:59.180> environments<00:56:59.930> they're<00:57:00.050> not 00:57:00.160 --> 00:57:00.170 align:start position:0% execution environments they're not 00:57:00.170 --> 00:57:02.470 align:start position:0% execution environments they're not necessarily<00:57:00.860> analogous<00:57:01.520> to<00:57:01.730> smart<00:57:02.000> contracts 00:57:02.470 --> 00:57:02.480 align:start position:0% necessarily analogous to smart contracts 00:57:02.480 --> 00:57:06.130 align:start position:0% necessarily analogous to smart contracts they<00:57:02.690> could<00:57:02.900> be<00:57:03.670> so<00:57:04.670> for<00:57:04.850> example<00:57:05.300> an 00:57:06.130 --> 00:57:06.140 align:start position:0% they could be so for example an 00:57:06.140 --> 00:57:08.680 align:start position:0% they could be so for example an execution<00:57:06.710> environment<00:57:07.160> is<00:57:07.460> one<00:57:07.730> EP<00:57:07.910> right 00:57:08.680 --> 00:57:08.690 align:start position:0% execution environment is one EP right 00:57:08.690 --> 00:57:10.900 align:start position:0% execution environment is one EP right defines<00:57:09.470> an<00:57:09.620> execution<00:57:10.220> environment<00:57:10.760> where 00:57:10.900 --> 00:57:10.910 align:start position:0% defines an execution environment where 00:57:10.910 --> 00:57:12.820 align:start position:0% defines an execution environment where like<00:57:11.360> more<00:57:11.660> code<00:57:11.870> can<00:57:12.110> rock<00:57:12.290> so<00:57:12.560> smart 00:57:12.820 --> 00:57:12.830 align:start position:0% like more code can rock so smart 00:57:12.830 --> 00:57:14.870 align:start position:0% like more code can rock so smart contracts<00:57:13.310> can<00:57:13.550> kind<00:57:13.730> of<00:57:13.760> run<00:57:14.030> in 00:57:14.870 --> 00:57:14.880 align:start position:0% contracts can kind of run in 00:57:14.880 --> 00:57:17.180 align:start position:0% contracts can kind of run in world<00:57:15.150> of<00:57:15.900> the<00:57:16.170> eath<00:57:16.319> one<00:57:16.559> you<00:57:16.829> use<00:57:17.009> that 00:57:17.180 --> 00:57:17.190 align:start position:0% world of the eath one you use that 00:57:17.190 --> 00:57:19.910 align:start position:0% world of the eath one you use that defines<00:57:17.579> how<00:57:18.390> continue<00:57:18.930> to<00:57:19.109> code<00:57:19.380> can<00:57:19.680> be 00:57:19.910 --> 00:57:19.920 align:start position:0% defines how continue to code can be 00:57:19.920 --> 00:57:22.249 align:start position:0% defines how continue to code can be executed<00:57:20.130> with<00:57:20.789> or<00:57:21.180> how<00:57:21.299> continued<00:57:21.809> contracts 00:57:22.249 --> 00:57:22.259 align:start position:0% executed with or how continued contracts 00:57:22.259 --> 00:57:23.630 align:start position:0% executed with or how continued contracts in<00:57:22.410> the<00:57:22.440> entity<00:57:22.829> did 00:57:23.630 --> 00:57:23.640 align:start position:0% in the entity did 00:57:23.640 --> 00:57:26.410 align:start position:0% in the entity did so<00:57:24.029> keep<00:57:24.390> defying<00:57:24.720> laws<00:57:25.079> many<00:57:25.440> more<00:57:25.650> wiser 00:57:26.410 --> 00:57:26.420 align:start position:0% so keep defying laws many more wiser 00:57:26.420 --> 00:57:29.809 align:start position:0% so keep defying laws many more wiser with<00:57:27.680> I<00:57:28.680> think<00:57:29.190> this<00:57:29.309> is<00:57:29.460> an<00:57:29.549> interesting 00:57:29.809 --> 00:57:29.819 align:start position:0% with I think this is an interesting 00:57:29.819 --> 00:57:33.920 align:start position:0% with I think this is an interesting quote<00:57:30.420> from<00:57:30.769> trust<00:57:31.769> with<00:57:32.579> easy-to-use<00:57:33.539> tracks 00:57:33.920 --> 00:57:33.930 align:start position:0% quote from trust with easy-to-use tracks 00:57:33.930 --> 00:57:35.870 align:start position:0% quote from trust with easy-to-use tracks that<00:57:34.109> fixed<00:57:34.410> execution<00:57:35.009> semantics<00:57:35.490> of<00:57:35.609> almost 00:57:35.870 --> 00:57:35.880 align:start position:0% that fixed execution semantics of almost 00:57:35.880 --> 00:57:38.539 align:start position:0% that fixed execution semantics of almost any<00:57:36.230> conceivable<00:57:37.230> programmable<00:57:38.039> blockchain 00:57:38.539 --> 00:57:38.549 align:start position:0% any conceivable programmable blockchain 00:57:38.549 --> 00:57:40.099 align:start position:0% any conceivable programmable blockchain in<00:57:38.730> a<00:57:38.819> similar<00:57:39.180> way<00:57:39.210> to<00:57:39.359> help<00:57:39.720> even<00:57:40.019> one 00:57:40.099 --> 00:57:40.109 align:start position:0% in a similar way to help even one 00:57:40.109 --> 00:57:41.569 align:start position:0% in a similar way to help even one abstract<00:57:40.559> to<00:57:40.680> the<00:57:40.710> fixed<00:57:41.039> semantics<00:57:41.460> with 00:57:41.569 --> 00:57:41.579 align:start position:0% abstract to the fixed semantics with 00:57:41.579 --> 00:57:43.450 align:start position:0% abstract to the fixed semantics with digital<00:57:41.940> tokens<00:57:42.059> currencies<00:57:42.809> in<00:57:43.019> the<00:57:43.109> early 00:57:43.450 --> 00:57:43.460 align:start position:0% digital tokens currencies in the early 00:57:43.460 --> 00:57:46.670 align:start position:0% digital tokens currencies in the early blockchain<00:57:44.460> Bitcoin<00:57:45.269> era<00:57:45.509> I<00:57:45.839> think<00:57:46.470> this<00:57:46.559> is 00:57:46.670 --> 00:57:46.680 align:start position:0% blockchain Bitcoin era I think this is 00:57:46.680 --> 00:57:50.029 align:start position:0% blockchain Bitcoin era I think this is cold<00:57:46.859> so<00:57:47.190> they<00:57:48.150> either<00:57:48.299> to<00:57:48.750> EE<00:57:49.019> what<00:57:49.559> we<00:57:49.829> talk 00:57:50.029 --> 00:57:50.039 align:start position:0% cold so they either to EE what we talk 00:57:50.039 --> 00:57:51.499 align:start position:0% cold so they either to EE what we talk about<00:57:50.190> this<00:57:50.549> is<00:57:50.700> still<00:57:50.849> under<00:57:50.880> today<00:57:51.269> because 00:57:51.499 --> 00:57:51.509 align:start position:0% about this is still under today because 00:57:51.509 --> 00:57:53.900 align:start position:0% about this is still under today because there's<00:57:51.690> some<00:57:52.349> other<00:57:52.650> perspectives<00:57:53.160> there's 00:57:53.900 --> 00:57:53.910 align:start position:0% there's some other perspectives there's 00:57:53.910 --> 00:57:56.569 align:start position:0% there's some other perspectives there's this<00:57:54.000> fella<00:57:54.480> model<00:57:54.900> or<00:57:55.049> an<00:57:55.710> on<00:57:55.920> umbrella<00:57:56.279> model 00:57:56.569 --> 00:57:56.579 align:start position:0% this fella model or an on umbrella model 00:57:56.579 --> 00:57:58.339 align:start position:0% this fella model or an on umbrella model and<00:57:56.670> we<00:57:56.730> could<00:57:56.849> go<00:57:56.970> into<00:57:57.119> that<00:57:57.210> a<00:57:57.269> bit<00:57:57.390> to<00:57:58.259> the 00:57:58.339 --> 00:57:58.349 align:start position:0% and we could go into that a bit to the 00:57:58.349 --> 00:58:00.559 align:start position:0% and we could go into that a bit to the eath<00:57:58.529> to<00:57:58.829> EE<00:57:59.039> is<00:57:59.400> saying<00:57:59.700> you<00:58:00.000> know<00:58:00.119> we're 00:58:00.559 --> 00:58:00.569 align:start position:0% eath to EE is saying you know we're 00:58:00.569 --> 00:58:02.980 align:start position:0% eath to EE is saying you know we're trying<00:58:00.869> to<00:58:00.990> do<00:58:01.109> a<00:58:01.140> lot<00:58:01.380> to<00:58:01.410> make<00:58:01.650> that<00:58:01.980> Eve<00:58:02.220> one 00:58:02.980 --> 00:58:02.990 align:start position:0% trying to do a lot to make that Eve one 00:58:02.990 --> 00:58:06.950 align:start position:0% trying to do a lot to make that Eve one compatible<00:58:03.990> and<00:58:04.230> bring<00:58:05.069> that<00:58:05.190> over<00:58:05.430> into<00:58:05.960> as 00:58:06.950 --> 00:58:06.960 align:start position:0% compatible and bring that over into as 00:58:06.960 --> 00:58:08.809 align:start position:0% compatible and bring that over into as an<00:58:07.170> execution<00:58:07.710> environment<00:58:08.190> and<00:58:08.309> it<00:58:08.430> to<00:58:08.700> you 00:58:08.809 --> 00:58:08.819 align:start position:0% an execution environment and it to you 00:58:08.819 --> 00:58:11.539 align:start position:0% an execution environment and it to you too<00:58:09.170> but<00:58:10.170> we<00:58:10.259> realized<00:58:10.710> they're<00:58:10.859> a<00:58:10.890> lot<00:58:11.039> better 00:58:11.539 --> 00:58:11.549 align:start position:0% too but we realized they're a lot better 00:58:11.549 --> 00:58:13.370 align:start position:0% too but we realized they're a lot better accumulator<00:58:12.329> formats<00:58:12.809> that<00:58:12.900> we<00:58:13.079> can<00:58:13.230> use 00:58:13.370 --> 00:58:13.380 align:start position:0% accumulator formats that we can use 00:58:13.380 --> 00:58:15.049 align:start position:0% accumulator formats that we can use there<00:58:13.619> are<00:58:13.680> a<00:58:13.710> lot<00:58:13.829> better<00:58:13.980> models<00:58:14.759> that<00:58:14.970> we 00:58:15.049 --> 00:58:15.059 align:start position:0% there are a lot better models that we 00:58:15.059 --> 00:58:16.940 align:start position:0% there are a lot better models that we can<00:58:15.089> follow<00:58:15.390> there<00:58:15.779> you<00:58:16.500> know<00:58:16.619> are<00:58:16.740> a<00:58:16.769> lot<00:58:16.920> of 00:58:16.940 --> 00:58:16.950 align:start position:0% can follow there you know are a lot of 00:58:16.950 --> 00:58:18.950 align:start position:0% can follow there you know are a lot of things<00:58:17.190> that<00:58:17.309> we<00:58:17.430> learned<00:58:17.670> and<00:58:17.940> so<00:58:18.269> we<00:58:18.779> can 00:58:18.950 --> 00:58:18.960 align:start position:0% things that we learned and so we can 00:58:18.960 --> 00:58:21.499 align:start position:0% things that we learned and so we can make<00:58:19.170> another<00:58:19.740> ee<00:58:19.950> that<00:58:20.369> is<00:58:20.609> focused<00:58:21.210> in 00:58:21.499 --> 00:58:21.509 align:start position:0% make another ee that is focused in 00:58:21.509 --> 00:58:23.359 align:start position:0% make another ee that is focused in generic<00:58:21.990> on<00:58:22.200> running<00:58:22.529> smart<00:58:22.890> contracts 00:58:23.359 --> 00:58:23.369 align:start position:0% generic on running smart contracts 00:58:23.369 --> 00:58:25.160 align:start position:0% generic on running smart contracts liking<00:58:23.730> one<00:58:24.119> that's<00:58:24.329> also<00:58:24.539> an<00:58:24.690> account<00:58:24.960> model 00:58:25.160 --> 00:58:25.170 align:start position:0% liking one that's also an account model 00:58:25.170 --> 00:58:27.740 align:start position:0% liking one that's also an account model but<00:58:26.130> we<00:58:26.220> can<00:58:26.339> make<00:58:26.430> it<00:58:26.490> you<00:58:26.640> know<00:58:26.819> even<00:58:27.180> better 00:58:27.740 --> 00:58:27.750 align:start position:0% but we can make it you know even better 00:58:27.750 --> 00:58:29.890 align:start position:0% but we can make it you know even better then<00:58:28.109> we<00:58:28.230> can<00:58:28.349> make<00:58:28.470> it<00:58:28.500> more<00:58:28.680> wise<00:58:28.920> obstetric 00:58:29.890 --> 00:58:29.900 align:start position:0% then we can make it more wise obstetric 00:58:29.900 --> 00:58:32.749 align:start position:0% then we can make it more wise obstetric and<00:58:30.900> so<00:58:31.230> this<00:58:31.440> is<00:58:31.589> the<00:58:31.710> concept<00:58:32.039> of<00:58:32.190> a<00:58:32.279> to<00:58:32.730> a 00:58:32.749 --> 00:58:32.759 align:start position:0% and so this is the concept of a to a 00:58:32.759 --> 00:58:39.999 align:start position:0% and so this is the concept of a to a meeting<00:58:35.420> I<00:58:36.420> think<00:58:37.079> he<00:58:37.470> was<00:58:37.619> I<00:58:37.829> mean<00:58:37.950> this<00:58:38.519> is<00:58:38.730> a 00:58:39.999 --> 00:58:40.009 align:start position:0% meeting I think he was I mean this is a 00:58:40.009 --> 00:58:42.470 align:start position:0% meeting I think he was I mean this is a state<00:58:41.009> execution<00:58:41.460> happens<00:58:41.819> within<00:58:42.089> the 00:58:42.470 --> 00:58:42.480 align:start position:0% state execution happens within the 00:58:42.480 --> 00:58:44.930 align:start position:0% state execution happens within the consents<00:58:42.900> to<00:58:42.930> be<00:58:43.079> shard<00:58:43.410> everything<00:58:43.950> is<00:58:44.099> all 00:58:44.930 --> 00:58:44.940 align:start position:0% consents to be shard everything is all 00:58:44.940 --> 00:58:47.650 align:start position:0% consents to be shard everything is all the<00:58:45.119> execution<00:58:45.630> is<00:58:45.750> centered<00:58:46.019> right<00:58:46.079> he<00:58:46.380> wasa 00:58:47.650 --> 00:58:47.660 align:start position:0% the execution is centered right he wasa 00:58:47.660 --> 00:58:51.750 align:start position:0% the execution is centered right he wasa he<00:58:48.660> wants<00:58:48.869> provides<00:58:49.529> me<00:58:49.799> a<00:58:50.480> concept<00:58:51.480> of 00:58:51.750 --> 00:58:51.760 align:start position:0% he wants provides me a concept of 00:58:51.760 --> 00:58:59.550 align:start position:0% he wants provides me a concept of Hanson<00:58:53.070> yeah<00:58:57.240> skip<00:58:58.240> that<00:58:58.390> for<00:58:58.540> now<00:58:58.600> so<00:58:58.930> this 00:58:59.550 --> 00:58:59.560 align:start position:0% Hanson yeah skip that for now so this 00:58:59.560 --> 00:59:03.720 align:start position:0% Hanson yeah skip that for now so this this<00:59:00.040> system<00:59:00.250> is<00:59:00.840> stateless<00:59:01.840> I<00:59:02.200> don't<00:59:02.890> know<00:59:02.980> if 00:59:03.720 --> 00:59:03.730 align:start position:0% this system is stateless I don't know if 00:59:03.730 --> 00:59:05.700 align:start position:0% this system is stateless I don't know if we<00:59:04.090> need<00:59:04.570> to<00:59:04.630> really<00:59:04.870> dive<00:59:05.170> into<00:59:05.350> that<00:59:05.530> too 00:59:05.700 --> 00:59:05.710 align:start position:0% we need to really dive into that too 00:59:05.710 --> 00:59:08.040 align:start position:0% we need to really dive into that too much<00:59:05.740> to<00:59:06.250> during<00:59:06.610> today's<00:59:06.880> session<00:59:07.120> but<00:59:07.570> in 00:59:08.040 --> 00:59:08.050 align:start position:0% much to during today's session but in 00:59:08.050 --> 00:59:10.380 align:start position:0% much to during today's session but in case<00:59:08.230> you're<00:59:08.380> curious<00:59:08.940> so<00:59:09.940> that<00:59:10.060> means<00:59:10.210> there 00:59:10.380 --> 00:59:10.390 align:start position:0% case you're curious so that means there 00:59:10.390 --> 00:59:12.420 align:start position:0% case you're curious so that means there are<00:59:10.570> actors<00:59:11.050> in<00:59:11.110> the<00:59:11.350> system<00:59:11.710> that<00:59:11.740> hold<00:59:12.100> state 00:59:12.420 --> 00:59:12.430 align:start position:0% are actors in the system that hold state 00:59:12.430 --> 00:59:15.320 align:start position:0% are actors in the system that hold state and<00:59:13.330> so<00:59:13.750> there's<00:59:13.900> a<00:59:13.960> lot<00:59:14.110> of<00:59:14.280> discussion 00:59:15.320 --> 00:59:15.330 align:start position:0% and so there's a lot of discussion 00:59:15.330 --> 00:59:17.730 align:start position:0% and so there's a lot of discussion discussion<00:59:16.330> about<00:59:16.660> this<00:59:16.870> the<00:59:17.140> the<00:59:17.530> best 00:59:17.730 --> 00:59:17.740 align:start position:0% discussion about this the the best 00:59:17.740 --> 00:59:19.290 align:start position:0% discussion about this the the best example<00:59:18.160> that<00:59:18.190> I<00:59:18.310> can<00:59:18.340> give<00:59:18.490> for<00:59:18.670> a<00:59:18.910> stateless 00:59:19.290 --> 00:59:19.300 align:start position:0% example that I can give for a stateless 00:59:19.300 --> 00:59:20.910 align:start position:0% example that I can give for a stateless system<00:59:19.690> is<00:59:19.840> with<00:59:20.140> your<00:59:20.290> transaction<00:59:20.830> you 00:59:20.910 --> 00:59:20.920 align:start position:0% system is with your transaction you 00:59:20.920 --> 00:59:24.000 align:start position:0% system is with your transaction you provide<00:59:21.250> the<00:59:21.400> database<00:59:21.760> so<00:59:22.380> if<00:59:23.380> I'm<00:59:23.560> you<00:59:23.980> know 00:59:24.000 --> 00:59:24.010 align:start position:0% provide the database so if I'm you know 00:59:24.010 --> 00:59:25.740 align:start position:0% provide the database so if I'm you know submitting<00:59:24.730> a<00:59:24.790> transaction<00:59:25.390> work<00:59:25.540> will 00:59:25.740 --> 00:59:25.750 align:start position:0% submitting a transaction work will 00:59:25.750 --> 00:59:29.580 align:start position:0% submitting a transaction work will Villanueva<00:59:26.530> is<00:59:27.540> transferring<00:59:28.540> 5e<00:59:28.780> to<00:59:29.230> shall 00:59:29.580 --> 00:59:29.590 align:start position:0% Villanueva is transferring 5e to shall 00:59:29.590 --> 00:59:30.150 align:start position:0% Villanueva is transferring 5e to shall we 00:59:30.150 --> 00:59:30.160 align:start position:0% we 00:59:30.160 --> 00:59:34.320 align:start position:0% we so<00:59:30.910> I<00:59:31.180> need<00:59:31.750> to<00:59:31.960> prove<00:59:32.520> what<00:59:33.520> my<00:59:33.670> account 00:59:34.320 --> 00:59:34.330 align:start position:0% so I need to prove what my account 00:59:34.330 --> 00:59:35.910 align:start position:0% so I need to prove what my account currently<00:59:34.840> looks<00:59:34.990> like<00:59:35.170> what<00:59:35.380> my<00:59:35.410> balance<00:59:35.800> is 00:59:35.910 --> 00:59:35.920 align:start position:0% currently looks like what my balance is 00:59:35.920 --> 00:59:39.000 align:start position:0% currently looks like what my balance is I<00:59:36.160> use<00:59:36.340> a<00:59:36.450> market<00:59:37.450> proof<00:59:37.660> to<00:59:37.840> do<00:59:37.960> that<00:59:38.110> and<00:59:38.920> I 00:59:39.000 --> 00:59:39.010 align:start position:0% I use a market proof to do that and I 00:59:39.010 --> 00:59:40.440 align:start position:0% I use a market proof to do that and I need<00:59:39.130> to<00:59:39.190> prove<00:59:39.370> what<00:59:39.700> her<00:59:39.970> account<00:59:40.270> looks 00:59:40.440 --> 00:59:40.450 align:start position:0% need to prove what her account looks 00:59:40.450 --> 00:59:43.860 align:start position:0% need to prove what her account looks like<00:59:40.660> as<00:59:41.020> well<00:59:41.260> so<00:59:41.770> I<00:59:41.800> in<00:59:42.790> this<00:59:42.940> case<00:59:43.180> I<00:59:43.600> show 00:59:43.860 --> 00:59:43.870 align:start position:0% like as well so I in this case I show 00:59:43.870 --> 00:59:46.770 align:start position:0% like as well so I in this case I show that<00:59:43.900> I<00:59:44.290> have<00:59:44.530> 16<00:59:44.950> and<00:59:45.220> shall<00:59:46.120> would<00:59:46.360> way<00:59:46.540> has 00:59:46.770 --> 00:59:46.780 align:start position:0% that I have 16 and shall would way has 00:59:46.780 --> 00:59:51.120 align:start position:0% that I have 16 and shall would way has three<00:59:47.400> and<00:59:48.400> so<00:59:49.090> now<00:59:49.420> when<00:59:49.720> the<00:59:49.960> block<00:59:50.680> producer 00:59:51.120 --> 00:59:51.130 align:start position:0% three and so now when the block producer 00:59:51.130 --> 00:59:53.610 align:start position:0% three and so now when the block producer exit<00:59:51.460> counts<00:59:51.730> the<00:59:51.820> transaction<00:59:52.480> it<00:59:52.990> basically 00:59:53.610 --> 00:59:53.620 align:start position:0% exit counts the transaction it basically 00:59:53.620 --> 00:59:55.530 align:start position:0% exit counts the transaction it basically just<00:59:53.710> pulls<00:59:54.130> from<00:59:54.310> the<00:59:54.370> proof<00:59:54.670> that<00:59:54.850> I<00:59:54.910> gave<00:59:55.210> it 00:59:55.530 --> 00:59:55.540 align:start position:0% just pulls from the proof that I gave it 00:59:55.540 --> 00:59:57.900 align:start position:0% just pulls from the proof that I gave it pulls<00:59:55.870> from<00:59:55.960> limited<00:59:56.770> database<00:59:57.460> that<00:59:57.640> I<00:59:57.730> gave 00:59:57.900 --> 00:59:57.910 align:start position:0% pulls from limited database that I gave 00:59:57.910 --> 01:00:00.510 align:start position:0% pulls from limited database that I gave with<00:59:58.000> my<00:59:58.180> transaction<00:59:58.800> so<00:59:59.800> definitely 01:00:00.510 --> 01:00:00.520 align:start position:0% with my transaction so definitely 01:00:00.520 --> 01:00:02.100 align:start position:0% with my transaction so definitely validators<01:00:01.120> block<01:00:01.360> producers<01:00:01.780> they<01:00:01.930> don't 01:00:02.100 --> 01:00:02.110 align:start position:0% validators block producers they don't 01:00:02.110 --> 01:00:04.620 align:start position:0% validators block producers they don't need<01:00:02.350> to<01:00:02.590> know<01:00:02.940> anything<01:00:03.940> about<01:00:04.150> the<01:00:04.390> state 01:00:04.620 --> 01:00:04.630 align:start position:0% need to know anything about the state 01:00:04.630 --> 01:00:07.320 align:start position:0% need to know anything about the state they<01:00:04.870> can<01:00:04.930> just<01:00:05.170> pull<01:00:05.440> from<01:00:05.740> the<01:00:06.330> this 01:00:07.320 --> 01:00:07.330 align:start position:0% they can just pull from the this 01:00:07.330 --> 01:00:09.480 align:start position:0% they can just pull from the this database<01:00:08.050> that<01:00:08.230> comes<01:00:08.470> with<01:00:08.680> each<01:00:09.250> of<01:00:09.400> your 01:00:09.480 --> 01:00:09.490 align:start position:0% database that comes with each of your 01:00:09.490 --> 01:00:11.120 align:start position:0% database that comes with each of your transactions 01:00:11.120 --> 01:00:11.130 align:start position:0% transactions 01:00:11.130 --> 01:00:15.510 align:start position:0% transactions I'm<01:00:12.130> switch<01:00:12.850> over<01:00:13.210> so<01:00:13.620> the<01:00:14.620> talented<01:00:15.130> a<01:00:15.190> really 01:00:15.510 --> 01:00:15.520 align:start position:0% I'm switch over so the talented a really 01:00:15.520 --> 01:00:17.970 align:start position:0% I'm switch over so the talented a really cool<01:00:15.730> post<01:00:15.940> on<01:00:16.180> this<01:00:16.360> just<01:00:16.990> recently<01:00:17.380> so<01:00:17.680> this 01:00:17.970 --> 01:00:17.980 align:start position:0% cool post on this just recently so this 01:00:17.980 --> 01:00:20.940 align:start position:0% cool post on this just recently so this is<01:00:18.100> what<01:00:18.280> we're<01:00:18.400> bringing<01:00:18.520> eath<01:00:19.000> 1<01:00:19.270> +<01:00:19.540> 2<01:00:19.690> e<01:00:19.720> 2<01:00:20.350> as 01:00:20.940 --> 01:00:20.950 align:start position:0% is what we're bringing eath 1 + 2 e 2 as 01:00:20.950 --> 01:00:23.160 align:start position:0% is what we're bringing eath 1 + 2 e 2 as an<01:00:21.190> execution<01:00:21.700> environment<01:00:22.240> this<01:00:22.750> means<01:00:23.020> that 01:00:23.160 --> 01:00:23.170 align:start position:0% an execution environment this means that 01:00:23.170 --> 01:00:26.180 align:start position:0% an execution environment this means that we<01:00:23.290> need<01:00:23.410> the<01:00:23.800> EDM<01:00:24.160> built-in<01:00:24.970> web<01:00:25.600> assembly 01:00:26.180 --> 01:00:26.190 align:start position:0% we need the EDM built-in web assembly 01:00:26.190 --> 01:00:29.250 align:start position:0% we need the EDM built-in web assembly and<01:00:27.190> this<01:00:27.460> would<01:00:27.670> be<01:00:27.850> defined<01:00:28.510> in<01:00:28.840> that<01:00:28.990> be 01:00:29.250 --> 01:00:29.260 align:start position:0% and this would be defined in that be 01:00:29.260 --> 01:00:32.760 align:start position:0% and this would be defined in that be script<01:00:29.770> that<01:00:30.130> we<01:00:30.580> talked<01:00:30.820> about<01:00:31.650> he'd<01:00:32.650> go<01:00:32.740> on 01:00:32.760 --> 01:00:32.770 align:start position:0% script that we talked about he'd go on 01:00:32.770 --> 01:00:34.520 align:start position:0% script that we talked about he'd go on that<01:00:33.070> he<01:00:33.250> was<01:00:33.370> this<01:00:33.580> one<01:00:33.820> has<01:00:33.940> been<01:00:34.120> doing 01:00:34.520 --> 01:00:34.530 align:start position:0% that he was this one has been doing 01:00:34.530 --> 01:00:39.090 align:start position:0% that he was this one has been doing really<01:00:35.530> really<01:00:36.310> good<01:00:36.990> working<01:00:37.990> not<01:00:38.710> as<01:00:38.860> well 01:00:39.090 --> 01:00:39.100 align:start position:0% really really good working not as well 01:00:39.100 --> 01:00:40.980 align:start position:0% really really good working not as well but<01:00:39.970> there's<01:00:40.120> a<01:00:40.180> lot<01:00:40.300> of<01:00:40.390> work<01:00:40.510> to<01:00:40.660> do<01:00:40.780> here 01:00:40.980 --> 01:00:40.990 align:start position:0% but there's a lot of work to do here 01:00:40.990 --> 01:00:42.840 align:start position:0% but there's a lot of work to do here there's<01:00:41.320> still<01:00:41.590> you<01:00:41.620> know<01:00:41.830> it 01:00:42.840 --> 01:00:42.850 align:start position:0% there's still you know it 01:00:42.850 --> 01:00:44.940 align:start position:0% there's still you know it prototype<01:00:43.390> that<01:00:43.540> still<01:00:43.750> needs<01:00:43.900> to<01:00:44.020> be<01:00:44.140> you 01:00:44.940 --> 01:00:44.950 align:start position:0% prototype that still needs to be you 01:00:44.950 --> 01:00:48.540 align:start position:0% prototype that still needs to be you know<01:00:45.100> kind<01:00:45.790> of<01:00:45.820> yeah<01:00:46.660> established<01:00:47.500> IV<01:00:48.310> tui 01:00:48.540 --> 01:00:48.550 align:start position:0% know kind of yeah established IV tui 01:00:48.550 --> 01:00:51.780 align:start position:0% know kind of yeah established IV tui talked<01:00:49.420> about<01:00:49.630> this<01:00:49.810> you<01:00:50.110> know<01:00:50.430> this<01:00:51.430> is<01:00:51.580> kind 01:00:51.780 --> 01:00:51.790 align:start position:0% talked about this you know this is kind 01:00:51.790 --> 01:00:53.430 align:start position:0% talked about this you know this is kind of<01:00:51.820> an<01:00:51.970> iterative<01:00:52.390> version<01:00:52.660> for<01:00:52.990> contract 01:00:53.430 --> 01:00:53.440 align:start position:0% of an iterative version for contract 01:00:53.440 --> 01:00:57.780 align:start position:0% of an iterative version for contract check<01:00:53.710> framework<01:00:54.390> it's<01:00:55.390> wasn't<01:00:55.660> centric<01:00:56.790> yeah 01:00:57.780 --> 01:00:57.790 align:start position:0% check framework it's wasn't centric yeah 01:00:57.790 --> 01:01:00.870 align:start position:0% check framework it's wasn't centric yeah and<01:00:58.060> and<01:00:58.360> so<01:00:59.160> then<01:01:00.160> we'll<01:01:00.250> go<01:01:00.370> to<01:01:00.400> crush<01:01:00.700> that 01:01:00.870 --> 01:01:00.880 align:start position:0% and and so then we'll go to crush that 01:01:00.880 --> 01:01:03.900 align:start position:0% and and so then we'll go to crush that transaction<01:01:01.480> so<01:01:02.400> you<01:01:03.400> know<01:01:03.520> there's<01:01:03.670> kind<01:01:03.820> of 01:01:03.900 --> 01:01:03.910 align:start position:0% transaction so you know there's kind of 01:01:03.910 --> 01:01:05.640 align:start position:0% transaction so you know there's kind of three<01:01:04.180> spaces<01:01:04.660> here<01:01:04.900> that<01:01:05.200> it<01:01:05.290> falls<01:01:05.440> under 01:01:05.640 --> 01:01:05.650 align:start position:0% three spaces here that it falls under 01:01:05.650 --> 01:01:07.470 align:start position:0% three spaces here that it falls under and<01:01:06.040> I<01:01:06.130> think<01:01:06.340> today<01:01:06.670> will<01:01:06.910> probably<01:01:07.330> just 01:01:07.470 --> 01:01:07.480 align:start position:0% and I think today will probably just 01:01:07.480 --> 01:01:08.640 align:start position:0% and I think today will probably just fill<01:01:07.690> this<01:01:07.780> in<01:01:07.960> the<01:01:08.020> first<01:01:08.200> one<01:01:08.440> that<01:01:08.590> a 01:01:08.640 --> 01:01:08.650 align:start position:0% fill this in the first one that a 01:01:08.650 --> 01:01:12.200 align:start position:0% fill this in the first one that a synchronous<01:01:09.190> support<01:01:09.490> protocol<01:01:10.470> so 01:01:12.200 --> 01:01:12.210 align:start position:0% synchronous support protocol so 01:01:12.210 --> 01:01:14.640 align:start position:0% synchronous support protocol so basically<01:01:13.210> that's<01:01:13.660> you<01:01:14.110> know<01:01:14.200> you<01:01:14.260> wait<01:01:14.500> until 01:01:14.640 --> 01:01:14.650 align:start position:0% basically that's you know you wait until 01:01:14.650 --> 01:01:17.970 align:start position:0% basically that's you know you wait until finality<01:01:15.120> once<01:01:16.120> you<01:01:16.210> get<01:01:16.330> finality<01:01:16.980> for 01:01:17.970 --> 01:01:17.980 align:start position:0% finality once you get finality for 01:01:17.980 --> 01:01:19.920 align:start position:0% finality once you get finality for another<01:01:18.160> chart<01:01:18.460> that<01:01:19.090> now<01:01:19.300> you<01:01:19.360> can<01:01:19.540> trust<01:01:19.780> a 01:01:19.920 --> 01:01:19.930 align:start position:0% another chart that now you can trust a 01:01:19.930 --> 01:01:21.570 align:start position:0% another chart that now you can trust a message<01:01:20.230> that<01:01:20.380> comes<01:01:20.590> from<01:01:20.800> a<01:01:20.890> chart<01:01:21.160> so 01:01:21.570 --> 01:01:21.580 align:start position:0% message that comes from a chart so 01:01:21.580 --> 01:01:24.510 align:start position:0% message that comes from a chart so that's<01:01:22.590> typically<01:01:23.590> would<01:01:23.830> be<01:01:24.070> considered 01:01:24.510 --> 01:01:24.520 align:start position:0% that's typically would be considered 01:01:24.520 --> 01:01:26.970 align:start position:0% that's typically would be considered slower<01:01:25.000> than<01:01:25.300> secured<01:01:25.840> state<01:01:26.230> you<01:01:26.650> know<01:01:26.830> it 01:01:26.970 --> 01:01:26.980 align:start position:0% slower than secured state you know it 01:01:26.980 --> 01:01:28.080 align:start position:0% slower than secured state you know it will<01:01:27.130> never<01:01:27.310> roll<01:01:27.490> back<01:01:27.700> through<01:01:27.820> the<01:01:27.910> never 01:01:28.080 --> 01:01:28.090 align:start position:0% will never roll back through the never 01:01:28.090 --> 01:01:31.050 align:start position:0% will never roll back through the never reorganize<01:01:29.010> there<01:01:30.010> is<01:01:30.130> a<01:01:30.160> new<01:01:30.370> proposal<01:01:30.730> that 01:01:31.050 --> 01:01:31.060 align:start position:0% reorganize there is a new proposal that 01:01:31.060 --> 01:01:36.030 align:start position:0% reorganize there is a new proposal that batalik<01:01:31.900> has<01:01:32.140> made<01:01:32.820> which<01:01:33.820> limits<01:01:34.660> so<01:01:35.170> crashed 01:01:36.030 --> 01:01:36.040 align:start position:0% batalik has made which limits so crashed 01:01:36.040 --> 01:01:37.770 align:start position:0% batalik has made which limits so crashed our<01:01:36.220> transactions<01:01:36.790> now<01:01:36.940> would<01:01:37.390> only<01:01:37.540> happen 01:01:37.770 --> 01:01:37.780 align:start position:0% our transactions now would only happen 01:01:37.780 --> 01:01:40.530 align:start position:0% our transactions now would only happen in<01:01:38.200> one<01:01:38.380> block<01:01:38.910> so<01:01:39.910> that's<01:01:40.090> actually<01:01:40.240> really 01:01:40.530 --> 01:01:40.540 align:start position:0% in one block so that's actually really 01:01:40.540 --> 01:01:44.310 align:start position:0% in one block so that's actually really cool<01:01:40.750> that<01:01:41.470> that's<01:01:41.890> so<01:01:42.160> unbearable<01:01:43.020> so<01:01:44.020> I 01:01:44.310 --> 01:01:44.320 align:start position:0% cool that that's so unbearable so I 01:01:44.320 --> 01:01:46.140 align:start position:0% cool that that's so unbearable so I think<01:01:44.440> before<01:01:44.650> finality<01:01:45.460> would<01:01:45.820> take<01:01:46.000> about 01:01:46.140 --> 01:01:46.150 align:start position:0% think before finality would take about 01:01:46.150 --> 01:01:49.170 align:start position:0% think before finality would take about six<01:01:46.480> to<01:01:46.630> 18<01:01:46.960> minutes<01:01:47.520> having<01:01:48.520> one<01:01:48.670> block<01:01:48.940> is 01:01:49.170 --> 01:01:49.180 align:start position:0% six to 18 minutes having one block is 01:01:49.180 --> 01:01:52.410 align:start position:0% six to 18 minutes having one block is you<01:01:49.750> know<01:01:49.870> six<01:01:50.140> seconds<01:01:50.560> to<01:01:50.760> make<01:01:51.760> a<01:01:51.910> call<01:01:52.150> to 01:01:52.410 --> 01:01:52.420 align:start position:0% you know six seconds to make a call to 01:01:52.420 --> 01:01:54.570 align:start position:0% you know six seconds to make a call to another<01:01:52.540> sharp<01:01:53.170> that's<01:01:53.590> that's<01:01:54.190> really<01:01:54.400> cool 01:01:54.570 --> 01:01:54.580 align:start position:0% another sharp that's that's really cool 01:01:54.580 --> 01:01:57.000 align:start position:0% another sharp that's that's really cool but<01:01:55.450> there's<01:01:55.990> always<01:01:56.140> with<01:01:56.560> every<01:01:56.800> proposal 01:01:57.000 --> 01:01:57.010 align:start position:0% but there's always with every proposal 01:01:57.010 --> 01:01:58.440 align:start position:0% but there's always with every proposal that<01:01:57.430> you<01:01:57.610> read<01:01:57.880> there's<01:01:58.090> always<01:01:58.180> going<01:01:58.330> to<01:01:58.390> be 01:01:58.440 --> 01:01:58.450 align:start position:0% that you read there's always going to be 01:01:58.450 --> 01:02:01.620 align:start position:0% that you read there's always going to be trade-offs<01:01:58.720> pros<01:01:59.260> cons<01:01:59.950> that<01:02:00.360> kind<01:02:01.360> of<01:02:01.480> it 01:02:01.620 --> 01:02:01.630 align:start position:0% trade-offs pros cons that kind of it 01:02:01.630 --> 01:02:04.020 align:start position:0% trade-offs pros cons that kind of it then<01:02:02.320> there's<01:02:02.500> this<01:02:02.620> whole<01:02:02.910> model<01:02:03.910> of 01:02:04.020 --> 01:02:04.030 align:start position:0% then there's this whole model of 01:02:04.030 --> 01:02:05.640 align:start position:0% then there's this whole model of optimistic<01:02:04.480> system<01:02:05.050> so<01:02:05.260> these<01:02:05.350> are<01:02:05.500> like 01:02:05.640 --> 01:02:05.650 align:start position:0% optimistic system so these are like 01:02:05.650 --> 01:02:07.440 align:start position:0% optimistic system so these are like dependency<01:02:06.250> graphs<01:02:06.520> that<01:02:06.700> kind<01:02:06.970> of<01:02:07.030> reward 01:02:07.440 --> 01:02:07.450 align:start position:0% dependency graphs that kind of reward 01:02:07.450 --> 01:02:10.500 align:start position:0% dependency graphs that kind of reward themselves<01:02:08.460> with<01:02:09.460> this<01:02:09.610> new<01:02:09.850> proposal<01:02:10.240> we 01:02:10.500 --> 01:02:10.510 align:start position:0% themselves with this new proposal we 01:02:10.510 --> 01:02:13.050 align:start position:0% themselves with this new proposal we wouldn't<01:02:10.750> need<01:02:10.810> those<01:02:11.020> anymore<01:02:11.290> but<01:02:12.250> these<01:02:12.400> do 01:02:13.050 --> 01:02:13.060 align:start position:0% wouldn't need those anymore but these do 01:02:13.060 --> 01:02:16.140 align:start position:0% wouldn't need those anymore but these do the<01:02:13.930> idea<01:02:14.260> is<01:02:14.500> you<01:02:14.710> can<01:02:14.740> use<01:02:15.040> basically<01:02:15.520> almost 01:02:16.140 --> 01:02:16.150 align:start position:0% the idea is you can use basically almost 01:02:16.150 --> 01:02:19.710 align:start position:0% the idea is you can use basically almost these<01:02:16.360> like<01:02:16.600> hybrid<01:02:17.050> systems<01:02:17.890> that<01:02:18.660> allow<01:02:19.660> you 01:02:19.710 --> 01:02:19.720 align:start position:0% these like hybrid systems that allow you 01:02:19.720 --> 01:02:21.360 align:start position:0% these like hybrid systems that allow you to<01:02:19.870> get<01:02:19.990> crossed<01:02:20.260> out<01:02:20.410> transactions<01:02:21.040> in<01:02:21.190> one 01:02:21.360 --> 01:02:21.370 align:start position:0% to get crossed out transactions in one 01:02:21.370 --> 01:02:23.970 align:start position:0% to get crossed out transactions in one block<01:02:21.840> assuming<01:02:22.840> that<01:02:22.990> it<01:02:23.170> will 01:02:23.970 --> 01:02:23.980 align:start position:0% block assuming that it will 01:02:23.980 --> 01:02:27.810 align:start position:0% block assuming that it will and<01:02:24.540> hopefully<01:02:25.540> that<01:02:26.430> we<01:02:27.430> won't<01:02:27.640> need<01:02:27.790> that 01:02:27.810 --> 01:02:27.820 align:start position:0% and hopefully that we won't need that 01:02:27.820 --> 01:02:28.890 align:start position:0% and hopefully that we won't need that anymore 01:02:28.890 --> 01:02:28.900 align:start position:0% anymore 01:02:28.900 --> 01:02:31.829 align:start position:0% anymore and<01:02:29.230> then<01:02:29.760> yeah<01:02:30.760> that<01:02:31.000> this<01:02:31.240> you<01:02:31.570> can<01:02:31.720> give 01:02:31.829 --> 01:02:31.839 align:start position:0% and then yeah that this you can give 01:02:31.839 --> 01:02:33.240 align:start position:0% and then yeah that this you can give like<01:02:32.050> a<01:02:32.170> synchronous<01:02:32.560> cross<01:02:32.800> judge<01:02:33.010> has 01:02:33.240 --> 01:02:33.250 align:start position:0% like a synchronous cross judge has 01:02:33.250 --> 01:02:36.420 align:start position:0% like a synchronous cross judge has actions<01:02:33.670> through<01:02:34.119> I<01:02:34.420> think<01:02:35.099> optimistic<01:02:36.099> Rolex 01:02:36.420 --> 01:02:36.430 align:start position:0% actions through I think optimistic Rolex 01:02:36.430 --> 01:02:38.069 align:start position:0% actions through I think optimistic Rolex is<01:02:36.550> a<01:02:36.579> really<01:02:36.820> good<01:02:36.970> example<01:02:37.060> so<01:02:37.720> this<01:02:37.900> is 01:02:38.069 --> 01:02:38.079 align:start position:0% is a really good example so this is 01:02:38.079 --> 01:02:42.120 align:start position:0% is a really good example so this is where<01:02:38.260> you<01:02:38.650> know<01:02:38.770> you<01:02:39.160> in<01:02:39.820> eighth<01:02:40.810> to<01:02:41.109> like<01:02:41.530> if 01:02:42.120 --> 01:02:42.130 align:start position:0% where you know you in eighth to like if 01:02:42.130 --> 01:02:44.910 align:start position:0% where you know you in eighth to like if you<01:02:42.280> bring<01:02:42.460> optimistic<01:02:43.150> roll<01:02:43.329> ups<01:02:43.480> to<01:02:43.599> to<01:02:43.960> you 01:02:44.910 --> 01:02:44.920 align:start position:0% you bring optimistic roll ups to to you 01:02:44.920 --> 01:02:47.910 align:start position:0% you bring optimistic roll ups to to you can<01:02:45.070> now<01:02:45.220> upload<01:02:46.210> your<01:02:46.540> data<01:02:46.720> on<01:02:47.290> four 01:02:47.910 --> 01:02:47.920 align:start position:0% can now upload your data on four 01:02:47.920 --> 01:02:50.069 align:start position:0% can now upload your data on four different<01:02:48.070> shards<01:02:48.430> so<01:02:48.579> user<01:02:48.910> if<01:02:49.540> they<01:02:49.780> want<01:02:49.990> to 01:02:50.069 --> 01:02:50.079 align:start position:0% different shards so user if they want to 01:02:50.079 --> 01:02:52.770 align:start position:0% different shards so user if they want to upload<01:02:50.560> their<01:02:50.710> transaction<01:02:51.339> they<01:02:51.579> can<01:02:51.790> they 01:02:52.770 --> 01:02:52.780 align:start position:0% upload their transaction they can they 01:02:52.780 --> 01:02:54.660 align:start position:0% upload their transaction they can they can<01:02:52.930> access<01:02:53.109> any<01:02:53.470> of<01:02:53.560> those<01:02:53.710> four<01:02:53.950> shards<01:02:54.430> and 01:02:54.660 --> 01:02:54.670 align:start position:0% can access any of those four shards and 01:02:54.670 --> 01:02:56.790 align:start position:0% can access any of those four shards and so<01:02:54.849> now<01:02:55.030> they're<01:02:55.300> not<01:02:55.480> you<01:02:56.260> know<01:02:56.290> they're<01:02:56.589> good 01:02:56.790 --> 01:02:56.800 align:start position:0% so now they're not you know they're good 01:02:56.800 --> 01:02:59.550 align:start position:0% so now they're not you know they're good it's<01:02:57.339> yeah<01:02:58.000> you<01:02:58.150> get<01:02:58.329> you<01:02:58.480> get<01:02:58.599> a<01:02:58.660> lot<01:02:58.869> extra 01:02:59.550 --> 01:02:59.560 align:start position:0% it's yeah you get you get a lot extra 01:02:59.560 --> 01:03:02.099 align:start position:0% it's yeah you get you get a lot extra there<01:02:59.800> as<01:02:59.920> well<01:03:00.160> that's<01:03:01.060> pretty<01:03:01.240> cool 01:03:02.099 --> 01:03:02.109 align:start position:0% there as well that's pretty cool 01:03:02.109 --> 01:03:05.130 align:start position:0% there as well that's pretty cool delays<01:03:02.740> data<01:03:03.040> execution<01:03:03.599> it's<01:03:04.599> kind<01:03:04.930> of<01:03:04.960> all 01:03:05.130 --> 01:03:05.140 align:start position:0% delays data execution it's kind of all 01:03:05.140 --> 01:03:08.099 align:start position:0% delays data execution it's kind of all falls<01:03:05.410> under<01:03:05.680> the<01:03:05.770> same<01:03:06.450> the<01:03:07.450> same<01:03:07.630> branch<01:03:07.960> of 01:03:08.099 --> 01:03:08.109 align:start position:0% falls under the same the same branch of 01:03:08.109 --> 01:03:10.620 align:start position:0% falls under the same the same branch of things<01:03:08.320> so<01:03:09.040> when<01:03:09.820> you<01:03:09.940> think<01:03:10.060> of<01:03:10.210> crossed<01:03:10.450> our 01:03:10.620 --> 01:03:10.630 align:start position:0% things so when you think of crossed our 01:03:10.630 --> 01:03:12.329 align:start position:0% things so when you think of crossed our transaction<01:03:11.170> that<01:03:11.260> substance<01:03:11.589> effect<01:03:11.920> Deb<01:03:12.130> X 01:03:12.329 --> 01:03:12.339 align:start position:0% transaction that substance effect Deb X 01:03:12.339 --> 01:03:15.450 align:start position:0% transaction that substance effect Deb X in<01:03:13.329> general<01:03:13.810> let's<01:03:14.530> just<01:03:14.740> like<01:03:14.859> focus<01:03:15.160> on<01:03:15.280> a 01:03:15.450 --> 01:03:15.460 align:start position:0% in general let's just like focus on a 01:03:15.460 --> 01:03:17.069 align:start position:0% in general let's just like focus on a sink<01:03:15.700> or<01:03:15.760> decide<01:03:16.060> the<01:03:16.240> synchronous<01:03:16.660> I'd<01:03:16.810> it 01:03:17.069 --> 01:03:17.079 align:start position:0% sink or decide the synchronous I'd it 01:03:17.079 --> 01:03:19.050 align:start position:0% sink or decide the synchronous I'd it really<01:03:17.440> shouldn't<01:03:17.710> change<01:03:18.040> that<01:03:18.190> much<01:03:18.760> and 01:03:19.050 --> 01:03:19.060 align:start position:0% really shouldn't change that much and 01:03:19.060 --> 01:03:21.720 align:start position:0% really shouldn't change that much and this<01:03:19.240> is<01:03:19.300> you<01:03:19.599> know<01:03:19.750> wet<01:03:20.380> like<01:03:20.619> Carlin<01:03:21.400> those 01:03:21.720 --> 01:03:21.730 align:start position:0% this is you know wet like Carlin those 01:03:21.730 --> 01:03:23.040 align:start position:0% this is you know wet like Carlin those guys<01:03:21.910> talk<01:03:22.180> to<01:03:22.329> you<01:03:22.390> about<01:03:22.480> that<01:03:22.720> a<01:03:22.750> little<01:03:22.900> bit 01:03:23.040 --> 01:03:23.050 align:start position:0% guys talk to you about that a little bit 01:03:23.050 --> 01:03:25.620 align:start position:0% guys talk to you about that a little bit more<01:03:23.290> on<01:03:24.220> the<01:03:24.339> easting<01:03:24.820> side<01:03:25.089> the<01:03:25.270> difference 01:03:25.620 --> 01:03:25.630 align:start position:0% more on the easting side the difference 01:03:25.630 --> 01:03:30.540 align:start position:0% more on the easting side the difference is<01:03:27.150> so<01:03:28.150> hll<01:03:28.839> is<01:03:28.990> our<01:03:29.200> higher<01:03:29.950> level<01:03:30.190> languages 01:03:30.540 --> 01:03:30.550 align:start position:0% is so hll is our higher level languages 01:03:30.550 --> 01:03:33.809 align:start position:0% is so hll is our higher level languages do<01:03:30.760> cells<01:03:31.079> so<01:03:32.079> right<01:03:32.859> very<01:03:33.069> different<01:03:33.520> things 01:03:33.809 --> 01:03:33.819 align:start position:0% do cells so right very different things 01:03:33.819 --> 01:03:37.290 align:start position:0% do cells so right very different things like<01:03:33.970> that<01:03:34.150> so<01:03:34.390> this<01:03:35.079> these<01:03:36.069> tools<01:03:36.430> should 01:03:37.290 --> 01:03:37.300 align:start position:0% like that so this these tools should 01:03:37.300 --> 01:03:39.510 align:start position:0% like that so this these tools should just<01:03:37.450> provide<01:03:37.750> property<01:03:38.140> right<01:03:38.410> now<01:03:38.530> so<01:03:39.339> what 01:03:39.510 --> 01:03:39.520 align:start position:0% just provide property right now so what 01:03:39.520 --> 01:03:44.490 align:start position:0% just provide property right now so what that<01:03:39.640> means<01:03:39.849> is<01:03:40.030> as<01:03:40.240> a<01:03:41.550> developer<01:03:43.200> you<01:03:44.200> now 01:03:44.490 --> 01:03:44.500 align:start position:0% that means is as a developer you now 01:03:44.500 --> 01:03:49.349 align:start position:0% that means is as a developer you now need<01:03:45.099> to<01:03:45.310> operate<01:03:46.240> under<01:03:47.190> this<01:03:48.190> idea<01:03:48.760> of<01:03:48.970> you 01:03:49.349 --> 01:03:49.359 align:start position:0% need to operate under this idea of you 01:03:49.359 --> 01:03:52.559 align:start position:0% need to operate under this idea of you are<01:03:49.450> gonna<01:03:49.599> make<01:03:49.780> asynchronous<01:03:50.349> calls<01:03:50.880> in<01:03:51.880> the 01:03:52.559 --> 01:03:52.569 align:start position:0% are gonna make asynchronous calls in the 01:03:52.569 --> 01:03:54.569 align:start position:0% are gonna make asynchronous calls in the smart<01:03:53.050> contracts<01:03:53.470> with<01:03:53.589> you<01:03:53.680> right<01:03:53.859> and<01:03:54.490> you 01:03:54.569 --> 01:03:54.579 align:start position:0% smart contracts with you right and you 01:03:54.579 --> 01:03:56.130 align:start position:0% smart contracts with you right and you need<01:03:54.730> to<01:03:54.880> be<01:03:55.210> aware<01:03:55.420> of<01:03:55.480> that<01:03:55.660> you<01:03:55.869> need<01:03:55.960> to<01:03:56.050> be 01:03:56.130 --> 01:03:56.140 align:start position:0% need to be aware of that you need to be 01:03:56.140 --> 01:03:59.069 align:start position:0% need to be aware of that you need to be open<01:03:56.440> to<01:03:56.530> that<01:03:56.790> and<01:03:57.790> then<01:03:58.150> there<01:03:58.300> may<01:03:58.660> be<01:03:58.690> even 01:03:59.069 --> 01:03:59.079 align:start position:0% open to that and then there may be even 01:03:59.079 --> 01:04:01.290 align:start position:0% open to that and then there may be even you<01:03:59.440> know<01:03:59.560> some<01:03:59.950> some<01:04:00.550> things<01:04:00.700> that<01:04:01.030> you<01:04:01.150> need 01:04:01.290 --> 01:04:01.300 align:start position:0% you know some some things that you need 01:04:01.300 --> 01:04:04.200 align:start position:0% you know some some things that you need that<01:04:02.010> require<01:04:03.010> more<01:04:03.250> than<01:04:03.310> just<01:04:03.460> easing<01:04:04.000> this 01:04:04.200 --> 01:04:04.210 align:start position:0% that require more than just easing this 01:04:04.210 --> 01:04:06.660 align:start position:0% that require more than just easing this call<01:04:04.420> so<01:04:04.720> a<01:04:05.020> different<01:04:05.710> tooling<01:04:06.010> that<01:04:06.220> should 01:04:06.660 --> 01:04:06.670 align:start position:0% call so a different tooling that should 01:04:06.670 --> 01:04:10.230 align:start position:0% call so a different tooling that should be<01:04:06.849> included<01:04:07.270> in<01:04:07.300> these<01:04:08.670> in<01:04:09.670> these<01:04:09.790> systems 01:04:10.230 --> 01:04:10.240 align:start position:0% be included in these in these systems 01:04:10.240 --> 01:04:12.180 align:start position:0% be included in these in these systems which<01:04:10.420> can<01:04:10.720> be<01:04:10.869> a<01:04:10.900> kid<01:04:11.140> to<01:04:11.380> programming<01:04:11.950> cross 01:04:12.180 --> 01:04:12.190 align:start position:0% which can be a kid to programming cross 01:04:12.190 --> 01:04:14.790 align:start position:0% which can be a kid to programming cross thread<01:04:12.520> so<01:04:12.849> if<01:04:13.690> you<01:04:13.869> need<01:04:14.050> to<01:04:14.260> make<01:04:14.410> an<01:04:14.560> atomic 01:04:14.790 --> 01:04:14.800 align:start position:0% thread so if you need to make an atomic 01:04:14.800 --> 01:04:18.859 align:start position:0% thread so if you need to make an atomic transaction<01:04:15.990> so<01:04:16.990> Terrell<01:04:17.319> training<01:04:17.650> problem 01:04:18.859 --> 01:04:18.869 align:start position:0% transaction so Terrell training problem 01:04:18.869 --> 01:04:21.809 align:start position:0% transaction so Terrell training problem you<01:04:19.869> mean<01:04:20.109> there<01:04:20.560> are<01:04:20.800> different<01:04:21.160> approaches 01:04:21.809 --> 01:04:21.819 align:start position:0% you mean there are different approaches 01:04:21.819 --> 01:04:23.099 align:start position:0% you mean there are different approaches that<01:04:21.970> you<01:04:22.060> can<01:04:22.089> go<01:04:22.300> with<01:04:22.329> you<01:04:22.660> can<01:04:22.810> go<01:04:22.930> with<01:04:23.050> a 01:04:23.099 --> 01:04:23.109 align:start position:0% that you can go with you can go with a 01:04:23.109 --> 01:04:24.870 align:start position:0% that you can go with you can go with a locking<01:04:23.530> system<01:04:23.950> readwrite<01:04:24.640> which 01:04:24.870 --> 01:04:24.880 align:start position:0% locking system readwrite which 01:04:24.880 --> 01:04:26.700 align:start position:0% locking system readwrite which essentially<01:04:25.540> rolls<01:04:25.780> down<01:04:26.109> into<01:04:26.380> this<01:04:26.500> that 01:04:26.700 --> 01:04:26.710 align:start position:0% essentially rolls down into this that 01:04:26.710 --> 01:04:29.670 align:start position:0% essentially rolls down into this that yanking<01:04:27.099> model<01:04:27.960> you<01:04:28.960> have<01:04:29.260> a<01:04:29.290> two-phase 01:04:29.670 --> 01:04:29.680 align:start position:0% yanking model you have a two-phase 01:04:29.680 --> 01:04:31.230 align:start position:0% yanking model you have a two-phase commit<01:04:29.920> email<01:04:30.520> which<01:04:30.700> could<01:04:30.910> essentially 01:04:31.230 --> 01:04:31.240 align:start position:0% commit email which could essentially 01:04:31.240 --> 01:04:33.720 align:start position:0% commit email which could essentially also<01:04:31.540> be<01:04:31.810> kind<01:04:31.930> of<01:04:32.020> a<01:04:32.140> messaging<01:04:32.619> model<01:04:32.980> you 01:04:33.720 --> 01:04:33.730 align:start position:0% also be kind of a messaging model you 01:04:33.730 --> 01:04:35.550 align:start position:0% also be kind of a messaging model you have<01:04:33.910> a<01:04:33.970> message<01:04:34.210> driven<01:04:34.540> approach<01:04:34.990> one<01:04:35.470> of 01:04:35.550 --> 01:04:35.560 align:start position:0% have a message driven approach one of 01:04:35.560 --> 01:04:38.309 align:start position:0% have a message driven approach one of those<01:04:35.770> ideas<01:04:36.609> is<01:04:36.849> like<01:04:36.880> the<01:04:37.150> actor<01:04:37.480> actor<01:04:38.109> and 01:04:38.309 --> 01:04:38.319 align:start position:0% those ideas is like the actor actor and 01:04:38.319 --> 01:04:41.220 align:start position:0% those ideas is like the actor actor and model<01:04:38.819> and<01:04:39.819> then<01:04:39.970> just<01:04:40.119> simple<01:04:40.660> asynchronous 01:04:41.220 --> 01:04:41.230 align:start position:0% model and then just simple asynchronous 01:04:41.230 --> 01:04:42.960 align:start position:0% model and then just simple asynchronous calls<01:04:41.470> so<01:04:41.770> kind<01:04:42.280> of<01:04:42.339> depends<01:04:42.609> what<01:04:42.700> you<01:04:42.790> need 01:04:42.960 --> 01:04:42.970 align:start position:0% calls so kind of depends what you need 01:04:42.970 --> 01:04:45.540 align:start position:0% calls so kind of depends what you need with<01:04:43.660> your<01:04:43.750> contract<01:04:44.170> you<01:04:44.430> developed<01:04:45.430> are 01:04:45.540 --> 01:04:45.550 align:start position:0% with your contract you developed are 01:04:45.550 --> 01:04:47.700 align:start position:0% with your contract you developed are going<01:04:45.730> to<01:04:45.790> need<01:04:45.910> to<01:04:46.060> understand<01:04:46.630> which<01:04:47.440> one<01:04:47.680> of 01:04:47.700 --> 01:04:47.710 align:start position:0% going to need to understand which one of 01:04:47.710 --> 01:04:49.950 align:start position:0% going to need to understand which one of these<01:04:47.890> tools<01:04:48.730> depending<01:04:49.210> on<01:04:49.329> you<01:04:49.660> know<01:04:49.690> what 01:04:49.950 --> 01:04:49.960 align:start position:0% these tools depending on you know what 01:04:49.960 --> 01:04:51.390 align:start position:0% these tools depending on you know what you<01:04:50.050> need<01:04:50.170> a<01:04:50.349> lot<01:04:50.710> of<01:04:50.800> developers<01:04:51.280> will 01:04:51.390 --> 01:04:51.400 align:start position:0% you need a lot of developers will 01:04:51.400 --> 01:04:52.829 align:start position:0% you need a lot of developers will probably<01:04:51.730> only<01:04:51.819> need<01:04:52.089> a<01:04:52.180> stand<01:04:52.480> as<01:04:52.569> calls 01:04:52.829 --> 01:04:52.839 align:start position:0% probably only need a stand as calls 01:04:52.839 --> 01:04:55.470 align:start position:0% probably only need a stand as calls others<01:04:53.200> may<01:04:53.380> need<01:04:53.560> some<01:04:53.920> type<01:04:54.099> of<01:04:54.280> concept<01:04:55.240> of 01:04:55.470 --> 01:04:55.480 align:start position:0% others may need some type of concept of 01:04:55.480 --> 01:04:58.020 align:start position:0% others may need some type of concept of an<01:04:55.900> atomic<01:04:56.520> transaction<01:04:57.520> across<01:04:57.760> multiple 01:04:58.020 --> 01:04:58.030 align:start position:0% an atomic transaction across multiple 01:04:58.030 --> 01:05:00.000 align:start position:0% an atomic transaction across multiple contracts<01:04:58.630> that's<01:04:59.319> why<01:04:59.470> you<01:04:59.589> just<01:04:59.710> need<01:04:59.890> to 01:05:00.000 --> 01:05:00.010 align:start position:0% contracts that's why you just need to 01:05:00.010 --> 01:05:01.680 align:start position:0% contracts that's why you just need to use<01:05:00.280> the<01:05:00.430> best<01:05:00.640> tool<01:05:00.940> I<01:05:01.119> mean<01:05:01.240> most<01:05:01.420> of<01:05:01.569> these 01:05:01.680 --> 01:05:01.690 align:start position:0% use the best tool I mean most of these 01:05:01.690 --> 01:05:03.329 align:start position:0% use the best tool I mean most of these toolings<01:05:02.170> should<01:05:02.500> be<01:05:02.619> provide 01:05:03.329 --> 01:05:03.339 align:start position:0% toolings should be provide 01:05:03.339 --> 01:05:05.849 align:start position:0% toolings should be provide provided<01:05:04.000> and<01:05:04.240> developed<01:05:04.660> within<01:05:05.589> things 01:05:05.849 --> 01:05:05.859 align:start position:0% provided and developed within things 01:05:05.859 --> 01:05:08.400 align:start position:0% provided and developed within things like<01:05:06.040> solidity<01:05:06.430> and<01:05:06.520> fiber<01:05:06.790> so<01:05:07.270> just<01:05:08.170> think<01:05:08.349> of 01:05:08.400 --> 01:05:08.410 align:start position:0% like solidity and fiber so just think of 01:05:08.410 --> 01:05:11.010 align:start position:0% like solidity and fiber so just think of it<01:05:08.560> as<01:05:08.710> you<01:05:09.670> know<01:05:09.760> you're<01:05:10.329> dealing<01:05:10.839> with 01:05:11.010 --> 01:05:11.020 align:start position:0% it as you know you're dealing with 01:05:11.020 --> 01:05:13.470 align:start position:0% it as you know you're dealing with asynchronous<01:05:11.680> calls<01:05:12.069> out<01:05:12.280> promises<01:05:13.030> whatever 01:05:13.470 --> 01:05:13.480 align:start position:0% asynchronous calls out promises whatever 01:05:13.480 --> 01:05:17.790 align:start position:0% asynchronous calls out promises whatever else<01:05:14.609> and<01:05:15.609> the<01:05:16.150> latency<01:05:16.480> depends<01:05:17.230> on<01:05:17.349> how<01:05:17.619> long 01:05:17.790 --> 01:05:17.800 align:start position:0% else and the latency depends on how long 01:05:17.800 --> 01:05:22.020 align:start position:0% else and the latency depends on how long it<01:05:17.859> takes<01:05:18.210> for<01:05:20.040> reduce<01:05:21.040> for<01:05:21.250> finality<01:05:21.640> time 01:05:22.020 --> 01:05:22.030 align:start position:0% it takes for reduce for finality time 01:05:22.030 --> 01:05:25.260 align:start position:0% it takes for reduce for finality time and<01:05:22.329> or<01:05:22.690> if<01:05:23.140> you<01:05:23.500> know<01:05:23.619> this<01:05:23.800> this<01:05:24.490> you<01:05:25.150> know 01:05:25.260 --> 01:05:25.270 align:start position:0% and or if you know this this you know 01:05:25.270 --> 01:05:28.470 align:start position:0% and or if you know this this you know new<01:05:25.690> direction<01:05:26.170> is<01:05:26.319> taken<01:05:26.700> you<01:05:27.700> could<01:05:27.940> get 01:05:28.470 --> 01:05:28.480 align:start position:0% new direction is taken you could get 01:05:28.480 --> 01:05:30.540 align:start position:0% new direction is taken you could get that<01:05:28.690> they<01:05:29.079> can<01:05:29.230> see<01:05:29.410> just<01:05:29.440> one<01:05:29.859> block<01:05:30.099> which 01:05:30.540 --> 01:05:30.550 align:start position:0% that they can see just one block which 01:05:30.550 --> 01:05:32.819 align:start position:0% that they can see just one block which is<01:05:30.579> actually<01:05:30.940> pretty<01:05:31.089> cool<01:05:31.300> I<01:05:31.569> think<01:05:31.930> that's<01:05:32.200> a 01:05:32.819 --> 01:05:32.829 align:start position:0% is actually pretty cool I think that's a 01:05:32.829 --> 01:05:35.180 align:start position:0% is actually pretty cool I think that's a lot<01:05:33.040> of<01:05:33.099> people<01:05:33.369> can<01:05:33.550> work<01:05:34.510> with<01:05:34.660> that 01:05:35.180 --> 01:05:35.190 align:start position:0% lot of people can work with that 01:05:35.190 --> 01:05:39.990 align:start position:0% lot of people can work with that other<01:05:36.190> changes<01:05:36.430> index<01:05:37.530> yeah<01:05:38.530> so<01:05:38.800> POS<01:05:39.430> provides 01:05:39.990 --> 01:05:40.000 align:start position:0% other changes index yeah so POS provides 01:05:40.000 --> 01:05:43.650 align:start position:0% other changes index yeah so POS provides them<01:05:40.300> some<01:05:40.599> things<01:05:41.369> you<01:05:42.369> know<01:05:42.490> there's<01:05:43.089> some 01:05:43.650 --> 01:05:43.660 align:start position:0% them some things you know there's some 01:05:43.660 --> 01:05:45.250 align:start position:0% them some things you know there's some speed<01:05:44.109> increases 01:05:45.250 --> 01:05:45.260 align:start position:0% speed increases 01:05:45.260 --> 01:05:47.740 align:start position:0% speed increases fusion<01:05:45.850> constantly<01:05:46.850> decrease<01:05:47.210> to<01:05:47.390> there 01:05:47.740 --> 01:05:47.750 align:start position:0% fusion constantly decrease to there 01:05:47.750 --> 01:05:49.120 align:start position:0% fusion constantly decrease to there being<01:05:47.960> multiple<01:05:48.170> shards<01:05:48.620> I<01:05:48.800> don't<01:05:48.950> want<01:05:49.070> to 01:05:49.120 --> 01:05:49.130 align:start position:0% being multiple shards I don't want to 01:05:49.130 --> 01:05:52.180 align:start position:0% being multiple shards I don't want to draw<01:05:49.250> too<01:05:49.430> much<01:05:49.520> attention<01:05:49.580> to<01:05:50.000> that<01:05:50.210> line<01:05:51.190> web 01:05:52.180 --> 01:05:52.190 align:start position:0% draw too much attention to that line web 01:05:52.190 --> 01:05:55.060 align:start position:0% draw too much attention to that line web 3<01:05:52.490> ethers<01:05:53.000> Jess<01:05:53.270> these<01:05:53.660> these<01:05:53.990> things<01:05:54.260> the<01:05:54.710> web 01:05:55.060 --> 01:05:55.070 align:start position:0% 3 ethers Jess these these things the web 01:05:55.070 --> 01:05:56.020 align:start position:0% 3 ethers Jess these these things the web through<01:05:55.250> Jess 01:05:56.020 --> 01:05:56.030 align:start position:0% through Jess 01:05:56.030 --> 01:05:57.670 align:start position:0% through Jess they<01:05:56.420> actually<01:05:56.540> shouldn't<01:05:57.020> change<01:05:57.260> that<01:05:57.380> much 01:05:57.670 --> 01:05:57.680 align:start position:0% they actually shouldn't change that much 01:05:57.680 --> 01:05:59.770 align:start position:0% they actually shouldn't change that much if<01:05:57.860> you're<01:05:58.010> doing<01:05:58.340> with<01:05:58.490> the<01:05:58.640> piece<01:05:58.880> one<01:05:59.120> that 01:05:59.770 --> 01:05:59.780 align:start position:0% if you're doing with the piece one that 01:05:59.780 --> 01:06:02.470 align:start position:0% if you're doing with the piece one that youth<01:05:59.900> one<01:06:00.140> eaten<01:06:00.520> their<01:06:01.520> coordination<01:06:02.030> area 01:06:02.470 --> 01:06:02.480 align:start position:0% youth one eaten their coordination area 01:06:02.480 --> 01:06:05.500 align:start position:0% youth one eaten their coordination area under<01:06:02.990> underneath<01:06:03.860> it<01:06:04.220> all<01:06:04.340> will<01:06:04.790> change<01:06:05.090> for 01:06:05.500 --> 01:06:05.510 align:start position:0% under underneath it all will change for 01:06:05.510 --> 01:06:08.380 align:start position:0% under underneath it all will change for sure<01:06:06.220> but<01:06:07.220> for<01:06:07.430> the<01:06:07.520> most<01:06:07.640> part<01:06:07.790> if<01:06:08.210> you're 01:06:08.380 --> 01:06:08.390 align:start position:0% sure but for the most part if you're 01:06:08.390 --> 01:06:10.180 align:start position:0% sure but for the most part if you're dealing<01:06:09.020> with<01:06:09.050> the<01:06:09.680> f1e 01:06:10.180 --> 01:06:10.190 align:start position:0% dealing with the f1e 01:06:10.190 --> 01:06:11.890 align:start position:0% dealing with the f1e it<01:06:10.340> shouldn't<01:06:10.730> change<01:06:10.820> drastically<01:06:11.360> there 01:06:11.890 --> 01:06:11.900 align:start position:0% it shouldn't change drastically there 01:06:11.900 --> 01:06:14.500 align:start position:0% it shouldn't change drastically there might<01:06:12.050> be<01:06:12.080> some<01:06:12.470> changes<01:06:13.330> from<01:06:14.330> your 01:06:14.500 --> 01:06:14.510 align:start position:0% might be some changes from your 01:06:14.510 --> 01:06:15.910 align:start position:0% might be some changes from your perspective<01:06:15.140> especially<01:06:15.440> if<01:06:15.710> you're<01:06:15.800> writing 01:06:15.910 --> 01:06:15.920 align:start position:0% perspective especially if you're writing 01:06:15.920 --> 01:06:18.030 align:start position:0% perspective especially if you're writing new<01:06:16.190> contracts<01:06:16.760> that<01:06:16.910> might<01:06:17.030> be<01:06:17.210> chard<01:06:17.540> aware 01:06:18.030 --> 01:06:18.040 align:start position:0% new contracts that might be chard aware 01:06:18.040 --> 01:06:21.370 align:start position:0% new contracts that might be chard aware but<01:06:19.040> again<01:06:19.340> it<01:06:19.670> shouldn't<01:06:20.090> ditch<01:06:20.420> much<01:06:20.720> and<01:06:21.050> in 01:06:21.370 --> 01:06:21.380 align:start position:0% but again it shouldn't ditch much and in 01:06:21.380 --> 01:06:23.920 align:start position:0% but again it shouldn't ditch much and in fact<01:06:22.040> I<01:06:22.400> imagine<01:06:23.150> that<01:06:23.360> there'll<01:06:23.540> be<01:06:23.570> this 01:06:23.920 --> 01:06:23.930 align:start position:0% fact I imagine that there'll be this 01:06:23.930 --> 01:06:26.320 align:start position:0% fact I imagine that there'll be this world<01:06:24.230> where<01:06:24.500> the<01:06:24.650> will<01:06:25.070> be<01:06:25.250> standards<01:06:25.880> around 01:06:26.320 --> 01:06:26.330 align:start position:0% world where the will be standards around 01:06:26.330 --> 01:06:28.810 align:start position:0% world where the will be standards around these<01:06:26.510> movies<01:06:27.020> that<01:06:27.050> are<01:06:27.350> built<01:06:27.560> and<01:06:27.800> so<01:06:28.520> web 01:06:28.810 --> 01:06:28.820 align:start position:0% these movies that are built and so web 01:06:28.820 --> 01:06:31.870 align:start position:0% these movies that are built and so web three<01:06:29.120> days<01:06:29.570> can<01:06:30.140> basically<01:06:30.620> be<01:06:31.070> portable<01:06:31.490> to 01:06:31.870 --> 01:06:31.880 align:start position:0% three days can basically be portable to 01:06:31.880 --> 01:06:34.600 align:start position:0% three days can basically be portable to these<01:06:32.870> different<01:06:33.290> edu<01:06:33.590> models<01:06:33.980> and<01:06:34.190> they<01:06:34.250> you 01:06:34.600 --> 01:06:34.610 align:start position:0% these different edu models and they you 01:06:34.610 --> 01:06:36.040 align:start position:0% these different edu models and they you know<01:06:34.700> I<01:06:34.730> think<01:06:35.030> this<01:06:35.240> is<01:06:35.420> like<01:06:35.570> a<01:06:35.600> really<01:06:35.840> cool 01:06:36.040 --> 01:06:36.050 align:start position:0% know I think this is like a really cool 01:06:36.050 --> 01:06:38.020 align:start position:0% know I think this is like a really cool space<01:06:36.380> and<01:06:36.650> I<01:06:36.710> just<01:06:37.040> would<01:06:37.310> love<01:06:37.490> to<01:06:37.640> see<01:06:37.790> more 01:06:38.020 --> 01:06:38.030 align:start position:0% space and I just would love to see more 01:06:38.030 --> 01:06:40.780 align:start position:0% space and I just would love to see more people<01:06:38.390> you<01:06:38.570> know<01:06:38.720> kind<01:06:39.380> of<01:06:39.440> idat<01:06:39.950> you<01:06:40.700> know 01:06:40.780 --> 01:06:40.790 align:start position:0% people you know kind of idat you know 01:06:40.790 --> 01:06:42.220 align:start position:0% people you know kind of idat you know get<01:06:41.060> involved<01:06:41.300> on<01:06:41.600> some<01:06:41.900> of<01:06:41.960> these<01:06:42.050> things 01:06:42.220 --> 01:06:42.230 align:start position:0% get involved on some of these things 01:06:42.230 --> 01:06:45.520 align:start position:0% get involved on some of these things over<01:06:42.410> time<01:06:43.480> it<01:06:44.480> we're<01:06:44.750> likely<01:06:45.020> to<01:06:45.230> have<01:06:45.320> more 01:06:45.520 --> 01:06:45.530 align:start position:0% over time it we're likely to have more 01:06:45.530 --> 01:06:47.650 align:start position:0% over time it we're likely to have more blossom<01:06:45.980> centric<01:06:46.400> smart<01:06:46.760> konchog<01:06:47.150> languages 01:06:47.650 --> 01:06:47.660 align:start position:0% blossom centric smart konchog languages 01:06:47.660 --> 01:06:50.800 align:start position:0% blossom centric smart konchog languages so<01:06:48.760> you<01:06:49.760> know<01:06:50.000> I<01:06:50.060> don't<01:06:50.240> think<01:06:50.450> you<01:06:50.690> know 01:06:50.800 --> 01:06:50.810 align:start position:0% so you know I don't think you know 01:06:50.810 --> 01:06:54.190 align:start position:0% so you know I don't think you know solidity<01:06:51.260> or<01:06:51.560> viper<01:06:52.370> were<01:06:52.900> necessarily<01:06:53.900> built 01:06:54.190 --> 01:06:54.200 align:start position:0% solidity or viper were necessarily built 01:06:54.200 --> 01:06:56.130 align:start position:0% solidity or viper were necessarily built with<01:06:54.320> there<01:06:54.440> was<01:06:54.590> no<01:06:54.770> centric<01:06:55.160> approach<01:06:55.400> so 01:06:56.130 --> 01:06:56.140 align:start position:0% with there was no centric approach so 01:06:56.140 --> 01:07:00.220 align:start position:0% with there was no centric approach so you<01:06:57.140> know<01:06:57.800> that<01:06:58.760> that<01:06:59.120> will<01:06:59.270> likely<01:06:59.480> you<01:07:00.200> know 01:07:00.220 --> 01:07:00.230 align:start position:0% you know that that will likely you know 01:07:00.230 --> 01:07:03.540 align:start position:0% you know that that will likely you know come<01:07:00.590> and<01:07:00.620> effect<01:07:01.250> its<01:07:01.370> developers<01:07:01.850> as<01:07:01.970> well 01:07:03.540 --> 01:07:03.550 align:start position:0% come and effect its developers as well 01:07:03.550 --> 01:07:06.610 align:start position:0% come and effect its developers as well so<01:07:04.550> which<01:07:04.910> should<01:07:05.060> I<01:07:05.120> build<01:07:05.360> an<01:07:05.480> ee<01:07:05.600> so<01:07:06.260> if<01:07:06.500> your 01:07:06.610 --> 01:07:06.620 align:start position:0% so which should I build an ee so if your 01:07:06.620 --> 01:07:08.800 align:start position:0% so which should I build an ee so if your protocol<01:07:07.070> researcher<01:07:07.550> developer<01:07:08.180> absolutely 01:07:08.800 --> 01:07:08.810 align:start position:0% protocol researcher developer absolutely 01:07:08.810 --> 01:07:10.150 align:start position:0% protocol researcher developer absolutely you<01:07:09.080> want<01:07:09.230> to<01:07:09.320> experiment<01:07:09.710> with<01:07:09.950> new 01:07:10.150 --> 01:07:10.160 align:start position:0% you want to experiment with new 01:07:10.160 --> 01:07:12.660 align:start position:0% you want to experiment with new accumulators<01:07:11.060> you<01:07:11.360> want<01:07:11.510> to<01:07:11.570> experiment<01:07:11.930> with 01:07:12.660 --> 01:07:12.670 align:start position:0% accumulators you want to experiment with 01:07:12.670 --> 01:07:16.150 align:start position:0% accumulators you want to experiment with you<01:07:13.670> know<01:07:13.790> different<01:07:14.290> different<01:07:15.290> approaches 01:07:16.150 --> 01:07:16.160 align:start position:0% you know different different approaches 01:07:16.160 --> 01:07:18.580 align:start position:0% you know different different approaches like<01:07:16.280> that<01:07:16.460> yet<01:07:16.700> you<01:07:16.940> should<01:07:17.350> do<01:07:18.350> you<01:07:18.440> think 01:07:18.580 --> 01:07:18.590 align:start position:0% like that yet you should do you think 01:07:18.590 --> 01:07:20.340 align:start position:0% like that yet you should do you think idea<01:07:18.710> which<01:07:18.920> only<01:07:19.070> makes<01:07:19.220> sense<01:07:19.430> as<01:07:19.610> a<01:07:19.640> Nene 01:07:20.340 --> 01:07:20.350 align:start position:0% idea which only makes sense as a Nene 01:07:20.350 --> 01:07:22.450 align:start position:0% idea which only makes sense as a Nene does<01:07:21.350> your<01:07:21.470> application<01:07:22.100> be<01:07:22.220> more 01:07:22.450 --> 01:07:22.460 align:start position:0% does your application be more 01:07:22.460 --> 01:07:25.240 align:start position:0% does your application be more flexibility<01:07:23.240> or<01:07:23.990> enhanced<01:07:24.590> scalability 01:07:25.240 --> 01:07:25.250 align:start position:0% flexibility or enhanced scalability 01:07:25.250 --> 01:07:27.610 align:start position:0% flexibility or enhanced scalability right<01:07:25.640> that<01:07:26.600> you<01:07:26.750> might<01:07:26.930> want<01:07:27.200> to<01:07:27.290> you<01:07:27.560> know 01:07:27.610 --> 01:07:27.620 align:start position:0% right that you might want to you know 01:07:27.620 --> 01:07:30.370 align:start position:0% right that you might want to you know work<01:07:28.010> out<01:07:28.160> any<01:07:28.370> need<01:07:28.670> for<01:07:29.290> for<01:07:30.290> the 01:07:30.370 --> 01:07:30.380 align:start position:0% work out any need for for the 01:07:30.380 --> 01:07:32.860 align:start position:0% work out any need for for the application<01:07:31.060> but<01:07:32.060> also<01:07:32.090> you<01:07:32.420> may<01:07:32.570> just<01:07:32.720> get 01:07:32.860 --> 01:07:32.870 align:start position:0% application but also you may just get 01:07:32.870 --> 01:07:34.870 align:start position:0% application but also you may just get left<01:07:33.020> behind<01:07:33.170> if<01:07:33.530> you<01:07:33.590> don't<01:07:33.770> learn<01:07:34.310> this<01:07:34.490> and 01:07:34.870 --> 01:07:34.880 align:start position:0% left behind if you don't learn this and 01:07:34.880 --> 01:07:36.310 align:start position:0% left behind if you don't learn this and you<01:07:35.450> don't<01:07:35.600> learn<01:07:35.720> too 01:07:36.310 --> 01:07:36.320 align:start position:0% you don't learn too 01:07:36.320 --> 01:07:37.930 align:start position:0% you don't learn too leverage<01:07:36.620> that<01:07:36.800> to<01:07:36.980> your<01:07:37.160> advantage<01:07:37.490> if<01:07:37.910> you 01:07:37.930 --> 01:07:37.940 align:start position:0% leverage that to your advantage if you 01:07:37.940 --> 01:07:40.360 align:start position:0% leverage that to your advantage if you don't<01:07:38.150> at<01:07:38.330> least<01:07:38.360> learn<01:07:38.750> to<01:07:39.370> understand 01:07:40.360 --> 01:07:40.370 align:start position:0% don't at least learn to understand 01:07:40.370 --> 01:07:42.100 align:start position:0% don't at least learn to understand what's<01:07:40.580> happening<01:07:40.970> behind<01:07:41.360> the<01:07:41.420> scenes<01:07:41.660> I 01:07:42.100 --> 01:07:42.110 align:start position:0% what's happening behind the scenes I 01:07:42.110 --> 01:07:43.720 align:start position:0% what's happening behind the scenes I think<01:07:42.950> there's<01:07:43.220> a<01:07:43.280> good<01:07:43.430> amount<01:07:43.640> of 01:07:43.720 --> 01:07:43.730 align:start position:0% think there's a good amount of 01:07:43.730 --> 01:07:46.450 align:start position:0% think there's a good amount of discussion<01:07:44.360> regarding<01:07:44.570> keys<01:07:45.080> some<01:07:45.470> some 01:07:46.450 --> 01:07:46.460 align:start position:0% discussion regarding keys some some 01:07:46.460 --> 01:07:48.640 align:start position:0% discussion regarding keys some some parties<01:07:47.090> believe<01:07:47.600> you<01:07:48.050> know<01:07:48.170> that<01:07:48.200> there 01:07:48.640 --> 01:07:48.650 align:start position:0% parties believe you know that there 01:07:48.650 --> 01:07:50.740 align:start position:0% parties believe you know that there should<01:07:48.800> just<01:07:48.830> be<01:07:49.010> you<01:07:49.820> know<01:07:49.940> three<01:07:50.180> or<01:07:50.390> four<01:07:50.420> or 01:07:50.740 --> 01:07:50.750 align:start position:0% should just be you know three or four or 01:07:50.750 --> 01:07:52.990 align:start position:0% should just be you know three or four or five<01:07:50.780> ETS<01:07:51.620> and<01:07:51.740> that's<01:07:51.920> what<01:07:52.100> everyone<01:07:52.520> uses 01:07:52.990 --> 01:07:53.000 align:start position:0% five ETS and that's what everyone uses 01:07:53.000 --> 01:07:55.600 align:start position:0% five ETS and that's what everyone uses others<01:07:53.930> believe<01:07:54.590> that<01:07:54.620> the<01:07:55.070> you<01:07:55.220> know<01:07:55.280> the 01:07:55.600 --> 01:07:55.610 align:start position:0% others believe that the you know the 01:07:55.610 --> 01:07:56.920 align:start position:0% others believe that the you know the amount<01:07:56.090> of<01:07:56.150> ease 01:07:56.920 --> 01:07:56.930 align:start position:0% amount of ease 01:07:56.930 --> 01:07:58.570 align:start position:0% amount of ease there<01:07:57.380> should<01:07:57.500> be<01:07:57.530> an<01:07:57.680> app<01:07:57.830> either 01:07:58.570 --> 01:07:58.580 align:start position:0% there should be an app either 01:07:58.580 --> 01:08:00.970 align:start position:0% there should be an app either application<01:07:59.390> and<01:07:59.690> then<01:07:59.870> we<01:08:00.020> build<01:08:00.410> a<01:08:00.530> model<01:08:00.830> by 01:08:00.970 --> 01:08:00.980 align:start position:0% application and then we build a model by 01:08:00.980 --> 01:08:02.710 align:start position:0% application and then we build a model by which<01:08:01.010> is<01:08:01.580> just<01:08:01.850> kind<01:08:01.970> of<01:08:02.090> communicate<01:08:02.600> with 01:08:02.710 --> 01:08:02.720 align:start position:0% which is just kind of communicate with 01:08:02.720 --> 01:08:04.780 align:start position:0% which is just kind of communicate with each<01:08:02.840> other<01:08:03.050> and<01:08:03.290> so<01:08:03.530> it's<01:08:04.160> kind<01:08:04.340> of<01:08:04.370> these<01:08:04.550> two 01:08:04.780 --> 01:08:04.790 align:start position:0% each other and so it's kind of these two 01:08:04.790 --> 01:08:06.820 align:start position:0% each other and so it's kind of these two camps<01:08:05.270> I<01:08:05.480> think<01:08:06.290> they<01:08:06.380> all<01:08:06.500> have<01:08:06.680> their 01:08:06.820 --> 01:08:06.830 align:start position:0% camps I think they all have their 01:08:06.830 --> 01:08:10.210 align:start position:0% camps I think they all have their trade-offs<01:08:07.280> pros<01:08:07.730> and<01:08:07.970> cons<01:08:08.180> and<01:08:09.220> whatever 01:08:10.210 --> 01:08:10.220 align:start position:0% trade-offs pros and cons and whatever 01:08:10.220 --> 01:08:13.240 align:start position:0% trade-offs pros and cons and whatever happens<01:08:10.880> they<01:08:11.120> don't<01:08:11.630> necessarily<01:08:11.870> think<01:08:12.290> the 01:08:13.240 --> 01:08:13.250 align:start position:0% happens they don't necessarily think the 01:08:13.250 --> 01:08:14.560 align:start position:0% happens they don't necessarily think the things<01:08:13.460> that<01:08:13.610> I<01:08:13.700> mentioned<01:08:14.060> just<01:08:14.090> prior 01:08:14.560 --> 01:08:14.570 align:start position:0% things that I mentioned just prior 01:08:14.570 --> 01:08:16.510 align:start position:0% things that I mentioned just prior should<01:08:14.870> actually<01:08:15.080> affect<01:08:15.590> that<01:08:15.860> duck 01:08:16.510 --> 01:08:16.520 align:start position:0% should actually affect that duck 01:08:16.520 --> 01:08:19.599 align:start position:0% should actually affect that duck developer<01:08:17.060> significant<01:08:17.839> angles<01:08:18.460> so<01:08:19.460> yeah 01:08:19.599 --> 01:08:19.609 align:start position:0% developer significant angles so yeah 01:08:19.609 --> 01:08:23.349 align:start position:0% developer significant angles so yeah that<01:08:20.030> I<01:08:20.270> hope<01:08:20.870> gives<01:08:21.320> a<01:08:21.620> like<01:08:22.370> good<01:08:22.910> overview 01:08:23.349 --> 01:08:23.359 align:start position:0% that I hope gives a like good overview 01:08:23.359 --> 01:08:25.750 align:start position:0% that I hope gives a like good overview for<01:08:23.660> everyone<01:08:24.050> of<01:08:24.290> what<01:08:24.350> phase<01:08:24.710> two<01:08:24.740> is<01:08:25.040> I'm 01:08:25.750 --> 01:08:25.760 align:start position:0% for everyone of what phase two is I'm 01:08:25.760 --> 01:08:30.730 align:start position:0% for everyone of what phase two is I'm generally<01:08:26.830> optimistic<01:08:27.830> about<01:08:28.250> things<01:08:29.710> yeah<01:08:30.710> I 01:08:30.730 --> 01:08:30.740 align:start position:0% generally optimistic about things yeah I 01:08:30.740 --> 01:08:34.870 align:start position:0% generally optimistic about things yeah I mean<01:08:31.010> there's<01:08:31.580> a<01:08:32.000> lot<01:08:32.300> of<01:08:32.420> people<01:08:33.100> much<01:08:34.100> much 01:08:34.870 --> 01:08:34.880 align:start position:0% mean there's a lot of people much much 01:08:34.880 --> 01:08:36.880 align:start position:0% mean there's a lot of people much much smarter<01:08:35.210> than<01:08:35.359> me<01:08:35.540> were<01:08:35.900> working<01:08:36.470> on<01:08:36.560> this<01:08:36.710> and 01:08:36.880 --> 01:08:36.890 align:start position:0% smarter than me were working on this and 01:08:36.890 --> 01:08:40.780 align:start position:0% smarter than me were working on this and building<01:08:37.570> building<01:08:38.570> using<01:08:39.670> again<01:08:40.670> I<01:08:40.760> just 01:08:40.780 --> 01:08:40.790 align:start position:0% building building using again I just 01:08:40.790 --> 01:08:43.120 align:start position:0% building building using again I just want<01:08:41.120> to<01:08:41.180> you<01:08:41.270> know<01:08:41.359> call<01:08:42.260> out<01:08:42.440> like<01:08:42.680> you<01:08:43.010> know 01:08:43.120 --> 01:08:43.130 align:start position:0% want to you know call out like you know 01:08:43.130 --> 01:08:46.270 align:start position:0% want to you know call out like you know Alex<01:08:43.850> Paul<01:08:44.210> Casey<01:08:44.900> Erin 01:08:46.270 --> 01:08:46.280 align:start position:0% Alex Paul Casey Erin 01:08:46.280 --> 01:08:48.430 align:start position:0% Alex Paul Casey Erin I<01:08:46.339> mean<01:08:46.880> phase<01:08:47.120> two<01:08:47.390> is<01:08:47.540> phase<01:08:47.750> two<01:08:48.020> because<01:08:48.320> of 01:08:48.430 --> 01:08:48.440 align:start position:0% I mean phase two is phase two because of 01:08:48.440 --> 01:08:52.210 align:start position:0% I mean phase two is phase two because of Casey<01:08:49.120> you<01:08:50.120> know<01:08:50.240> in<01:08:50.930> large<01:08:51.290> part<01:08:51.620> originally 01:08:52.210 --> 01:08:52.220 align:start position:0% Casey you know in large part originally 01:08:52.220 --> 01:08:55.720 align:start position:0% Casey you know in large part originally anyways<01:08:53.080> there<01:08:54.080> is<01:08:54.200> a<01:08:54.380> session<01:08:54.680> where<01:08:55.010> you 01:08:55.720 --> 01:08:55.730 align:start position:0% anyways there is a session where you 01:08:55.730 --> 01:08:59.200 align:start position:0% anyways there is a session where you know<01:08:56.330> the<01:08:56.690> US<01:08:57.230> team<01:08:57.530> has<01:08:57.920> worked<01:08:58.670> on<01:08:58.880> a<01:08:58.910> ton<01:08:59.150> of 01:08:59.200 --> 01:08:59.210 align:start position:0% know the US team has worked on a ton of 01:08:59.210 --> 01:09:02.349 align:start position:0% know the US team has worked on a ton of different<01:08:59.540> E's<01:09:00.020> and<01:09:00.730> it's<01:09:01.730> like<01:09:02.150> really 01:09:02.349 --> 01:09:02.359 align:start position:0% different E's and it's like really 01:09:02.359 --> 01:09:04.239 align:start position:0% different E's and it's like really really<01:09:02.720> cool<01:09:02.900> to<01:09:02.960> see<01:09:03.230> a<01:09:03.260> lot<01:09:03.440> of<01:09:03.470> the 01:09:04.239 --> 01:09:04.249 align:start position:0% really cool to see a lot of the 01:09:04.249 --> 01:09:06.669 align:start position:0% really cool to see a lot of the evasion<01:09:04.489> and<01:09:05.299> creativity<01:09:06.019> years<01:09:06.440> that's 01:09:06.669 --> 01:09:06.679 align:start position:0% evasion and creativity years that's 01:09:06.679 --> 01:09:09.430 align:start position:0% evasion and creativity years that's happening<01:09:07.130> is<01:09:07.279> really<01:09:08.059> exciting<01:09:08.479> a<01:09:08.690> lot<01:09:09.319> of 01:09:09.430 --> 01:09:09.440 align:start position:0% happening is really exciting a lot of 01:09:09.440 --> 01:09:12.160 align:start position:0% happening is really exciting a lot of smart<01:09:09.769> people<01:09:09.799> are<01:09:10.099> working<01:09:10.249> on<01:09:10.460> this<01:09:10.609> so<01:09:11.170> yeah 01:09:12.160 --> 01:09:12.170 align:start position:0% smart people are working on this so yeah 01:09:12.170 --> 01:09:14.229 align:start position:0% smart people are working on this so yeah I<01:09:12.349> does<01:09:12.949> anyone<01:09:13.219> have<01:09:13.369> any<01:09:13.519> like<01:09:13.699> overview 01:09:14.229 --> 01:09:14.239 align:start position:0% I does anyone have any like overview 01:09:14.239 --> 01:09:19.629 align:start position:0% I does anyone have any like overview questions<01:09:15.909> yeah<01:09:17.920> someone<01:09:18.920> who's<01:09:19.069> all<01:09:19.339> of<01:09:19.460> this 01:09:19.629 --> 01:09:19.639 align:start position:0% questions yeah someone who's all of this 01:09:19.639 --> 01:09:22.749 align:start position:0% questions yeah someone who's all of this from<01:09:19.880> really<01:09:20.329> far<01:09:21.279> actually<01:09:22.279> two<01:09:22.609> questions 01:09:22.749 --> 01:09:22.759 align:start position:0% from really far actually two questions 01:09:22.759 --> 01:09:25.509 align:start position:0% from really far actually two questions served<01:09:23.269> one<01:09:23.509> this<01:09:23.690> I<01:09:24.019> believe<01:09:24.829> that<01:09:25.159> back<01:09:25.339> to 01:09:25.509 --> 01:09:25.519 align:start position:0% served one this I believe that back to 01:09:25.519 --> 01:09:27.219 align:start position:0% served one this I believe that back to the<01:09:25.579> day<01:09:25.729> I<01:09:26.119> think<01:09:26.359> it<01:09:26.569> was<01:09:26.659> an<01:09:26.749> interview<01:09:27.079> with 01:09:27.219 --> 01:09:27.229 align:start position:0% the day I think it was an interview with 01:09:27.229 --> 01:09:28.779 align:start position:0% the day I think it was an interview with Justin<01:09:27.409> very<01:09:27.769> he<01:09:28.039> was<01:09:28.159> saying<01:09:28.400> that<01:09:28.609> there 01:09:28.779 --> 01:09:28.789 align:start position:0% Justin very he was saying that there 01:09:28.789 --> 01:09:30.700 align:start position:0% Justin very he was saying that there would<01:09:28.969> be<01:09:28.999> only<01:09:29.239> one<01:09:29.420> execution<01:09:30.139> engine 01:09:30.700 --> 01:09:30.710 align:start position:0% would be only one execution engine 01:09:30.710 --> 01:09:34.479 align:start position:0% would be only one execution engine across<01:09:31.069> all<01:09:31.279> charts<01:09:31.729> and<01:09:32.739> this<01:09:33.739> is<01:09:33.949> new<01:09:34.130> to<01:09:34.309> me 01:09:34.479 --> 01:09:34.489 align:start position:0% across all charts and this is new to me 01:09:34.489 --> 01:09:37.660 align:start position:0% across all charts and this is new to me so<01:09:34.519> I<01:09:34.699> was<01:09:34.789> wondering<01:09:35.119> well<01:09:36.049> they<01:09:36.349> shift<01:09:36.769> has 01:09:37.660 --> 01:09:37.670 align:start position:0% so I was wondering well they shift has 01:09:37.670 --> 01:09:39.549 align:start position:0% so I was wondering well they shift has happened<01:09:38.359> and<01:09:38.630> what<01:09:38.749> the<01:09:38.869> rationales<01:09:39.499> behind 01:09:39.549 --> 01:09:39.559 align:start position:0% happened and what the rationales behind 01:09:39.559 --> 01:09:42.579 align:start position:0% happened and what the rationales behind it<01:09:40.130> the<01:09:40.759> second<01:09:41.269> question<01:09:41.659> is<01:09:41.809> so<01:09:42.229> if<01:09:42.409> we 01:09:42.579 --> 01:09:42.589 align:start position:0% it the second question is so if we 01:09:42.589 --> 01:09:44.649 align:start position:0% it the second question is so if we imagine<01:09:42.859> different<01:09:43.579> shots<01:09:43.819> having<01:09:44.299> different 01:09:44.649 --> 01:09:44.659 align:start position:0% imagine different shots having different 01:09:44.659 --> 01:09:48.009 align:start position:0% imagine different shots having different execution<01:09:45.199> engines<01:09:45.759> how<01:09:46.759> do<01:09:47.239> they<01:09:47.420> come<01:09:47.749> back 01:09:48.009 --> 01:09:48.019 align:start position:0% execution engines how do they come back 01:09:48.019 --> 01:09:52.059 align:start position:0% execution engines how do they come back I<01:09:48.349> mean<01:09:48.559> does<01:09:49.400> the<01:09:49.759> foundation<01:09:50.769> decree<01:09:51.769> at 01:09:52.059 --> 01:09:52.069 align:start position:0% I mean does the foundation decree at 01:09:52.069 --> 01:09:54.399 align:start position:0% I mean does the foundation decree at some<01:09:52.339> point<01:09:52.639> you'll<01:09:52.940> have<01:09:53.109> thousands<01:09:54.109> of<01:09:54.170> your 01:09:54.399 --> 01:09:54.409 align:start position:0% some point you'll have thousands of your 01:09:54.409 --> 01:09:56.859 align:start position:0% some point you'll have thousands of your charts<01:09:54.889> and<01:09:55.099> five<01:09:55.999> of<01:09:56.210> them<01:09:56.329> have<01:09:56.570> this 01:09:56.859 --> 01:09:56.869 align:start position:0% charts and five of them have this 01:09:56.869 --> 01:09:59.200 align:start position:0% charts and five of them have this execution<01:09:57.499> engine<01:09:57.860> not<01:09:58.099> cetera<01:09:58.610> I<01:09:58.760> assume 01:09:59.200 --> 01:09:59.210 align:start position:0% execution engine not cetera I assume 01:09:59.210 --> 01:10:01.270 align:start position:0% execution engine not cetera I assume it's<01:09:59.360> not<01:09:59.449> the<01:09:59.780> case<01:09:59.989> but<01:10:00.260> how<01:10:01.010> do<01:10:01.070> you 01:10:01.270 --> 01:10:01.280 align:start position:0% it's not the case but how do you 01:10:01.280 --> 01:10:04.390 align:start position:0% it's not the case but how do you envision<01:10:01.699> that<01:10:02.090> to<01:10:02.840> come<01:10:03.289> about<01:10:03.499> yeah<01:10:04.099> so<01:10:04.369> I 01:10:04.390 --> 01:10:04.400 align:start position:0% envision that to come about yeah so I 01:10:04.400 --> 01:10:06.850 align:start position:0% envision that to come about yeah so I think<01:10:04.489> Justin<01:10:05.389> kind<01:10:05.719> of<01:10:05.809> takes<01:10:06.050> you<01:10:06.469> know<01:10:06.619> one 01:10:06.850 --> 01:10:06.860 align:start position:0% think Justin kind of takes you know one 01:10:06.860 --> 01:10:09.189 align:start position:0% think Justin kind of takes you know one one<01:10:07.579> side<01:10:07.820> that's<01:10:08.059> very<01:10:08.360> very<01:10:08.539> strong<01:10:08.900> and 01:10:09.189 --> 01:10:09.199 align:start position:0% one side that's very very strong and 01:10:09.199 --> 01:10:10.450 align:start position:0% one side that's very very strong and then<01:10:09.320> there's<01:10:09.559> kind<01:10:09.739> of<01:10:09.889> the<01:10:10.190> other<01:10:10.340> side 01:10:10.450 --> 01:10:10.460 align:start position:0% then there's kind of the other side 01:10:10.460 --> 01:10:13.239 align:start position:0% then there's kind of the other side which<01:10:11.059> is<01:10:11.300> just<01:10:12.139> let<01:10:12.320> everyone<01:10:12.619> every<01:10:13.070> top 01:10:13.239 --> 01:10:13.249 align:start position:0% which is just let everyone every top 01:10:13.249 --> 01:10:15.520 align:start position:0% which is just let everyone every top developer<01:10:13.849> right<01:10:14.300> and<01:10:14.449> II<01:10:14.510> mean<01:10:14.749> so<01:10:15.289> these<01:10:15.380> are 01:10:15.520 --> 01:10:15.530 align:start position:0% developer right and II mean so these are 01:10:15.530 --> 01:10:17.979 align:start position:0% developer right and II mean so these are kind<01:10:15.739> of<01:10:15.769> into<01:10:16.489> the<01:10:17.090> two<01:10:17.239> different<01:10:17.269> ends 01:10:17.979 --> 01:10:17.989 align:start position:0% kind of into the two different ends 01:10:17.989 --> 01:10:19.719 align:start position:0% kind of into the two different ends right<01:10:18.380> and<01:10:18.889> I<01:10:18.949> think<01:10:19.130> it<01:10:19.219> hasn't<01:10:19.429> been 01:10:19.719 --> 01:10:19.729 align:start position:0% right and I think it hasn't been 01:10:19.729 --> 01:10:21.370 align:start position:0% right and I think it hasn't been resolved<01:10:20.239> like<01:10:20.420> those<01:10:20.630> discussions<01:10:21.320> just 01:10:21.370 --> 01:10:21.380 align:start position:0% resolved like those discussions just 01:10:21.380 --> 01:10:22.750 align:start position:0% resolved like those discussions just need<01:10:21.590> to<01:10:21.710> happen<01:10:22.039> and<01:10:22.130> this<01:10:22.219> is<01:10:22.280> part<01:10:22.550> of<01:10:22.610> what 01:10:22.750 --> 01:10:22.760 align:start position:0% need to happen and this is part of what 01:10:22.760 --> 01:10:24.819 align:start position:0% need to happen and this is part of what we're<01:10:22.880> doing<01:10:23.119> by<01:10:23.239> prototyping<01:10:23.929> and<01:10:24.349> looking 01:10:24.819 --> 01:10:24.829 align:start position:0% we're doing by prototyping and looking 01:10:24.829 --> 01:10:26.290 align:start position:0% we're doing by prototyping and looking at<01:10:24.949> it<01:10:25.070> I<01:10:25.249> tend<01:10:25.729> to<01:10:25.760> think<01:10:25.940> that<01:10:26.119> there's 01:10:26.290 --> 01:10:26.300 align:start position:0% at it I tend to think that there's 01:10:26.300 --> 01:10:27.729 align:start position:0% at it I tend to think that there's probably<01:10:26.570> just<01:10:26.630> gonna<01:10:26.869> be<01:10:27.019> like<01:10:27.229> a<01:10:27.289> gentle 01:10:27.729 --> 01:10:27.739 align:start position:0% probably just gonna be like a gentle 01:10:27.739 --> 01:10:30.790 align:start position:0% probably just gonna be like a gentle balance<01:10:27.920> this<01:10:28.489> this<01:10:29.059> is<01:10:29.179> my<01:10:29.329> opinion<01:10:29.570> and<01:10:29.900> in 01:10:30.790 --> 01:10:30.800 align:start position:0% balance this this is my opinion and in 01:10:30.800 --> 01:10:33.310 align:start position:0% balance this this is my opinion and in no<01:10:31.010> way<01:10:31.039> is<01:10:31.190> that<01:10:31.519> you<01:10:31.760> know<01:10:31.880> you<01:10:32.210> know<01:10:32.329> all<01:10:32.749> the 01:10:33.310 --> 01:10:33.320 align:start position:0% no way is that you know you know all the 01:10:33.320 --> 01:10:37.270 align:start position:0% no way is that you know you know all the researchers<01:10:33.829> our<01:10:34.070> research<01:10:34.400> team<01:10:35.800> Alex<01:10:36.800> and 01:10:37.270 --> 01:10:37.280 align:start position:0% researchers our research team Alex and 01:10:37.280 --> 01:10:39.370 align:start position:0% researchers our research team Alex and Casey<01:10:37.460> and<01:10:37.789> Danny<01:10:38.179> and<01:10:38.479> everyone<01:10:39.110> here<01:10:39.260> might 01:10:39.370 --> 01:10:39.380 align:start position:0% Casey and Danny and everyone here might 01:10:39.380 --> 01:10:40.989 align:start position:0% Casey and Danny and everyone here might have<01:10:39.499> a<01:10:39.559> different<01:10:39.739> opinion<01:10:39.860> than<01:10:40.190> me<01:10:40.400> my 01:10:40.989 --> 01:10:40.999 align:start position:0% have a different opinion than me my 01:10:40.999 --> 01:10:42.399 align:start position:0% have a different opinion than me my general<01:10:41.630> opinion<01:10:41.749> is<01:10:42.019> that<01:10:42.050> there's<01:10:42.349> a 01:10:42.399 --> 01:10:42.409 align:start position:0% general opinion is that there's a 01:10:42.409 --> 01:10:44.680 align:start position:0% general opinion is that there's a delicate<01:10:43.010> balance<01:10:43.369> where<01:10:44.179> there<01:10:44.420> are<01:10:44.539> like 01:10:44.680 --> 01:10:44.690 align:start position:0% delicate balance where there are like 01:10:44.690 --> 01:10:48.520 align:start position:0% delicate balance where there are like four<01:10:45.050> es<01:10:45.679> that<01:10:46.039> are<01:10:47.030> kind<01:10:47.269> of<01:10:47.300> entries 01:10:48.520 --> 01:10:48.530 align:start position:0% four es that are kind of entries 01:10:48.530 --> 01:10:50.440 align:start position:0% four es that are kind of entries right<01:10:49.130> smart<01:10:49.460> contracts<01:10:49.910> for<01:10:50.060> they<01:10:50.240> already 01:10:50.440 --> 01:10:50.450 align:start position:0% right smart contracts for they already 01:10:50.450 --> 01:10:52.030 align:start position:0% right smart contracts for they already have<01:10:50.630> the<01:10:50.720> standards<01:10:51.170> they're<01:10:51.380> just<01:10:51.680> easy<01:10:51.950> to 01:10:52.030 --> 01:10:52.040 align:start position:0% have the standards they're just easy to 01:10:52.040 --> 01:10:53.440 align:start position:0% have the standards they're just easy to do<01:10:52.220> play<01:10:52.490> -<01:10:52.550> you<01:10:52.790> don't<01:10:52.880> have<01:10:53.120> to<01:10:53.210> think<01:10:53.360> about 01:10:53.440 --> 01:10:53.450 align:start position:0% do play - you don't have to think about 01:10:53.450 --> 01:10:55.690 align:start position:0% do play - you don't have to think about complexity<01:10:54.110> what<01:10:54.890> accumulators<01:10:55.520> you're 01:10:55.690 --> 01:10:55.700 align:start position:0% complexity what accumulators you're 01:10:55.700 --> 01:10:56.890 align:start position:0% complexity what accumulators you're gonna<01:10:55.820> use<01:10:56.060> you<01:10:56.330> don't<01:10:56.420> have<01:10:56.570> to<01:10:56.660> think<01:10:56.750> about 01:10:56.890 --> 01:10:56.900 align:start position:0% gonna use you don't have to think about 01:10:56.900 --> 01:10:59.470 align:start position:0% gonna use you don't have to think about these<01:10:57.140> things<01:10:57.320> right<01:10:57.500> but<01:10:58.460> if<01:10:58.730> you<01:10:58.970> want<01:10:59.240> to 01:10:59.470 --> 01:10:59.480 align:start position:0% these things right but if you want to 01:10:59.480 --> 01:11:01.870 align:start position:0% these things right but if you want to then<01:11:00.140> you're<01:11:00.290> free<01:11:00.590> to<01:11:00.680> launch<01:11:01.100> your<01:11:01.400> own<01:11:01.460> e 01:11:01.870 --> 01:11:01.880 align:start position:0% then you're free to launch your own e 01:11:01.880 --> 01:11:04.900 align:start position:0% then you're free to launch your own e that<01:11:02.690> can<01:11:02.840> then<01:11:03.220> integrate<01:11:04.220> with<01:11:04.730> these 01:11:04.900 --> 01:11:04.910 align:start position:0% that can then integrate with these 01:11:04.910 --> 01:11:07.540 align:start position:0% that can then integrate with these because<01:11:05.210> I<01:11:05.300> think<01:11:05.510> not<01:11:06.410> allowing<01:11:06.890> developers 01:11:07.540 --> 01:11:07.550 align:start position:0% because I think not allowing developers 01:11:07.550 --> 01:11:10.090 align:start position:0% because I think not allowing developers to<01:11:07.610> launching<01:11:08.390> eases<01:11:08.870> like<01:11:09.170> I<01:11:09.470> don't<01:11:09.950> know 01:11:10.090 --> 01:11:10.100 align:start position:0% to launching eases like I don't know 01:11:10.100 --> 01:11:11.410 align:start position:0% to launching eases like I don't know this<01:11:10.250> is<01:11:10.400> gonna<01:11:10.520> be<01:11:10.700> a<01:11:10.730> huge<01:11:11.060> area<01:11:11.390> of 01:11:11.410 --> 01:11:11.420 align:start position:0% this is gonna be a huge area of 01:11:11.420 --> 01:11:13.060 align:start position:0% this is gonna be a huge area of innovation<01:11:11.930> where<01:11:12.080> we<01:11:12.170> can<01:11:12.320> learn<01:11:12.470> so<01:11:12.830> much 01:11:13.060 --> 01:11:13.070 align:start position:0% innovation where we can learn so much 01:11:13.070 --> 01:11:14.860 align:start position:0% innovation where we can learn so much you<01:11:13.310> should<01:11:13.460> definitely<01:11:13.970> open<01:11:14.240> that<01:11:14.360> up 01:11:14.860 --> 01:11:14.870 align:start position:0% you should definitely open that up 01:11:14.870 --> 01:11:17.730 align:start position:0% you should definitely open that up so<01:11:15.170> that's<01:11:15.320> that's<01:11:15.530> my<01:11:15.740> general<01:11:15.980> like<01:11:16.670> thought 01:11:17.730 --> 01:11:17.740 align:start position:0% so that's that's my general like thought 01:11:17.740 --> 01:11:20.380 align:start position:0% so that's that's my general like thought although<01:11:18.740> I<01:11:18.770> think<01:11:18.920> most<01:11:19.130> DAP<01:11:19.820> developers 01:11:20.380 --> 01:11:20.390 align:start position:0% although I think most DAP developers 01:11:20.390 --> 01:11:22.930 align:start position:0% although I think most DAP developers will<01:11:20.600> be<01:11:20.720> operating<01:11:21.380> across<01:11:21.740> you<01:11:22.160> know<01:11:22.280> maybe 01:11:22.930 --> 01:11:22.940 align:start position:0% will be operating across you know maybe 01:11:22.940 --> 01:11:25.930 align:start position:0% will be operating across you know maybe four<01:11:23.390> major<01:11:23.840> ease<01:11:24.290> that<01:11:25.040> that<01:11:25.370> are<01:11:25.490> you<01:11:25.760> know 01:11:25.930 --> 01:11:25.940 align:start position:0% four major ease that that are you know 01:11:25.940 --> 01:11:29.050 align:start position:0% four major ease that that are you know the<01:11:26.240> most<01:11:26.420> popular<01:11:26.900> I<01:11:27.740> think<01:11:27.950> here<01:11:28.730> to<01:11:28.970> your 01:11:29.050 --> 01:11:29.060 align:start position:0% the most popular I think here to your 01:11:29.060 --> 01:11:32.320 align:start position:0% the most popular I think here to your question<01:11:29.510> for<01:11:30.230> DES<01:11:30.440> Moine<01:11:30.710> anything<01:11:31.160> the<01:11:32.060> idea 01:11:32.320 --> 01:11:32.330 align:start position:0% question for DES Moine anything the idea 01:11:32.330 --> 01:11:34.480 align:start position:0% question for DES Moine anything the idea is<01:11:32.420> that<01:11:32.450> you<01:11:32.720> have<01:11:33.110> to<01:11:33.260> pay<01:11:33.440> a<01:11:33.710> large<01:11:33.950> you<01:11:34.370> know 01:11:34.480 --> 01:11:34.490 align:start position:0% is that you have to pay a large you know 01:11:34.490 --> 01:11:38.050 align:start position:0% is that you have to pay a large you know a<01:11:34.520> fairly<01:11:34.820> large<01:11:35.090> sum<01:11:35.390> to<01:11:36.080> deploy<01:11:36.830> EE<01:11:37.130> onto<01:11:38.000> the 01:11:38.050 --> 01:11:38.060 align:start position:0% a fairly large sum to deploy EE onto the 01:11:38.060 --> 01:11:41.890 align:start position:0% a fairly large sum to deploy EE onto the beacon<01:11:38.330> shape<01:11:38.530> and<01:11:39.530> then<01:11:39.850> what<01:11:40.850> is<01:11:41.030> unknown<01:11:41.570> is 01:11:41.890 --> 01:11:41.900 align:start position:0% beacon shape and then what is unknown is 01:11:41.900 --> 01:11:44.110 align:start position:0% beacon shape and then what is unknown is whether<01:11:42.470> that<01:11:42.590> EE<01:11:43.190> is<01:11:43.430> now<01:11:43.610> just<01:11:43.880> available 01:11:44.110 --> 01:11:44.120 align:start position:0% whether that EE is now just available 01:11:44.120 --> 01:11:47.050 align:start position:0% whether that EE is now just available across<01:11:44.570> all<01:11:44.810> shards<01:11:45.260> or<01:11:45.490> whether<01:11:46.490> you<01:11:46.700> need<01:11:46.850> to 01:11:47.050 --> 01:11:47.060 align:start position:0% across all shards or whether you need to 01:11:47.060 --> 01:11:49.630 align:start position:0% across all shards or whether you need to you<01:11:47.540> need<01:11:48.230> to<01:11:48.380> pay<01:11:48.560> to<01:11:48.590> deploy<01:11:49.040> it<01:11:49.190> on<01:11:49.340> each 01:11:49.630 --> 01:11:49.640 align:start position:0% you need to pay to deploy it on each 01:11:49.640 --> 01:11:51.400 align:start position:0% you need to pay to deploy it on each shark<01:11:50.180> individually<01:11:50.840> that<01:11:50.960> you<01:11:51.080> want<01:11:51.260> to 01:11:51.400 --> 01:11:51.410 align:start position:0% shark individually that you want to 01:11:51.410 --> 01:11:53.470 align:start position:0% shark individually that you want to operate<01:11:51.770> on<01:11:51.950> so<01:11:52.670> like<01:11:52.880> a<01:11:52.910> shark<01:11:53.210> you<01:11:53.300> have 01:11:53.470 --> 01:11:53.480 align:start position:0% operate on so like a shark you have 01:11:53.480 --> 01:11:55.840 align:start position:0% operate on so like a shark you have multiple<01:11:53.870> e's<01:11:54.260> running<01:11:54.680> does<01:11:55.190> that<01:11:55.370> do<01:11:55.790> you 01:11:55.840 --> 01:11:55.850 align:start position:0% multiple e's running does that do you 01:11:55.850 --> 01:11:58.480 align:start position:0% multiple e's running does that do you have<01:11:56.000> access<01:11:56.210> to<01:11:56.720> all<01:11:57.020> the<01:11:57.260> Sharks<01:11:57.650> just<01:11:58.370> by 01:11:58.480 --> 01:11:58.490 align:start position:0% have access to all the Sharks just by 01:11:58.490 --> 01:11:59.890 align:start position:0% have access to all the Sharks just by the<01:11:58.550> point<01:11:58.820> what<01:11:59.030> something<01:11:59.330> the<01:11:59.630> beacon 01:11:59.890 --> 01:11:59.900 align:start position:0% the point what something the beacon 01:11:59.900 --> 01:12:01.690 align:start position:0% the point what something the beacon chain<01:12:00.080> or<01:12:00.320> do<01:12:00.440> you<01:12:00.530> have<01:12:00.650> to<01:12:00.830> also<01:12:01.100> deploy<01:12:01.550> on 01:12:01.690 --> 01:12:01.700 align:start position:0% chain or do you have to also deploy on 01:12:01.700 --> 01:12:03.340 align:start position:0% chain or do you have to also deploy on each<01:12:01.910> of<01:12:02.030> the<01:12:02.120> sharks<01:12:02.390> that<01:12:02.480> you<01:12:02.660> want<01:12:02.840> me<01:12:03.200> to 01:12:03.340 --> 01:12:03.350 align:start position:0% each of the sharks that you want me to 01:12:03.350 --> 01:12:05.350 align:start position:0% each of the sharks that you want me to write<01:12:03.530> on<01:12:03.740> so<01:12:04.520> I<01:12:04.550> think<01:12:04.670> again<01:12:04.970> these<01:12:05.240> are 01:12:05.350 --> 01:12:05.360 align:start position:0% write on so I think again these are 01:12:05.360 --> 01:12:07.090 align:start position:0% write on so I think again these are research<01:12:05.600> questions<01:12:06.140> we're<01:12:06.380> not<01:12:06.590> entirely 01:12:07.090 --> 01:12:07.100 align:start position:0% research questions we're not entirely 01:12:07.100 --> 01:12:09.940 align:start position:0% research questions we're not entirely sure<01:12:07.780> but<01:12:08.780> I<01:12:08.840> think<01:12:09.110> we'll<01:12:09.350> probably<01:12:09.560> have 01:12:09.940 --> 01:12:09.950 align:start position:0% sure but I think we'll probably have 01:12:09.950 --> 01:12:13.000 align:start position:0% sure but I think we'll probably have answers<01:12:10.370> you<01:12:10.610> know<01:12:10.730> hopefully<01:12:11.770> fairly<01:12:12.770> soon 01:12:13.000 --> 01:12:13.010 align:start position:0% answers you know hopefully fairly soon 01:12:13.010 --> 01:12:16.120 align:start position:0% answers you know hopefully fairly soon in<01:12:13.820> the<01:12:14.300> new<01:12:14.420> year's<01:12:14.690> time<01:12:15.170> as<01:12:15.410> we<01:12:15.590> continue<01:12:15.830> to 01:12:16.120 --> 01:12:16.130 align:start position:0% in the new year's time as we continue to 01:12:16.130 --> 01:12:19.560 align:start position:0% in the new year's time as we continue to just<01:12:16.450> prototype<01:12:17.450> these<01:12:17.660> things<01:12:17.930> yeah<01:12:18.560> so<01:12:19.100> as 01:12:19.560 --> 01:12:19.570 align:start position:0% just prototype these things yeah so as 01:12:19.570 --> 01:12:23.050 align:start position:0% just prototype these things yeah so as to<01:12:20.570> develop<01:12:20.720> among<01:12:21.260> EE<01:12:21.440> I<01:12:21.950> would<01:12:22.130> like<01:12:22.430> to<01:12:22.790> find 01:12:23.050 --> 01:12:23.060 align:start position:0% to develop among EE I would like to find 01:12:23.060 --> 01:12:23.910 align:start position:0% to develop among EE I would like to find other 01:12:23.910 --> 01:12:23.920 align:start position:0% other 01:12:23.920 --> 01:12:26.490 align:start position:0% other will<01:12:24.010> that<01:12:24.250> have<01:12:24.460> money<01:12:25.330> and<01:12:25.780> pulled<01:12:26.350> our 01:12:26.490 --> 01:12:26.500 align:start position:0% will that have money and pulled our 01:12:26.500 --> 01:12:29.790 align:start position:0% will that have money and pulled our resources<01:12:27.040> and<01:12:27.310> then<01:12:27.570> before<01:12:28.570> that<01:12:28.810> yeah<01:12:29.500> yeah 01:12:29.790 --> 01:12:29.800 align:start position:0% resources and then before that yeah yeah 01:12:29.800 --> 01:12:32.580 align:start position:0% resources and then before that yeah yeah so<01:12:30.220> maybe<01:12:30.700> you<01:12:31.210> know<01:12:31.300> one<01:12:31.540> one<01:12:31.960> really<01:12:32.500> good 01:12:32.580 --> 01:12:32.590 align:start position:0% so maybe you know one one really good 01:12:32.590 --> 01:12:34.770 align:start position:0% so maybe you know one one really good example<01:12:32.650> is<01:12:33.070> that<01:12:33.100> youth<01:12:33.310> 188<01:12:33.910> right<01:12:34.120> so 01:12:34.770 --> 01:12:34.780 align:start position:0% example is that youth 188 right so 01:12:34.780 --> 01:12:37.140 align:start position:0% example is that youth 188 right so that's<01:12:35.050> you<01:12:35.380> know<01:12:35.440> probably<01:12:35.850> that<01:12:36.850> there<01:12:37.060> in 01:12:37.140 --> 01:12:37.150 align:start position:0% that's you know probably that there in 01:12:37.150 --> 01:12:39.260 align:start position:0% that's you know probably that there in foundation<01:12:37.660> stands<01:12:37.960> behind<01:12:38.380> that<01:12:38.530> provides 01:12:39.260 --> 01:12:39.270 align:start position:0% foundation stands behind that provides 01:12:39.270 --> 01:12:42.750 align:start position:0% foundation stands behind that provides kind<01:12:40.270> of<01:12:40.330> the<01:12:40.420> funding<01:12:40.750> to<01:12:40.870> deploy<01:12:41.260> that<01:12:41.760> and 01:12:42.750 --> 01:12:42.760 align:start position:0% kind of the funding to deploy that and 01:12:42.760 --> 01:12:44.370 align:start position:0% kind of the funding to deploy that and there's<01:12:42.970> already<01:12:43.150> an<01:12:43.330> ecosystem<01:12:43.750> around<01:12:44.020> that 01:12:44.370 --> 01:12:44.380 align:start position:0% there's already an ecosystem around that 01:12:44.380 --> 01:12:45.930 align:start position:0% there's already an ecosystem around that but<01:12:44.590> now<01:12:44.740> let's<01:12:45.070> say<01:12:45.220> there's<01:12:45.430> a<01:12:45.520> new<01:12:45.640> account 01:12:45.930 --> 01:12:45.940 align:start position:0% but now let's say there's a new account 01:12:45.940 --> 01:12:47.370 align:start position:0% but now let's say there's a new account model<01:12:46.120> that<01:12:46.390> people<01:12:46.750> you<01:12:46.960> know<01:12:46.990> to<01:12:47.140> support 01:12:47.370 --> 01:12:47.380 align:start position:0% model that people you know to support 01:12:47.380 --> 01:12:49.380 align:start position:0% model that people you know to support case<01:12:47.830> is<01:12:47.980> gonna<01:12:48.160> say<01:12:48.850> something<01:12:49.150> in<01:12:49.240> a<01:12:49.300> moment 01:12:49.380 --> 01:12:49.390 align:start position:0% case is gonna say something in a moment 01:12:49.390 --> 01:12:51.830 align:start position:0% case is gonna say something in a moment a<01:12:49.960> new<01:12:50.170> account<01:12:50.470> model<01:12:50.620> that<01:12:50.890> people<01:12:51.310> support 01:12:51.830 --> 01:12:51.840 align:start position:0% a new account model that people support 01:12:51.840 --> 01:12:55.080 align:start position:0% a new account model that people support and<01:12:52.840> it<01:12:53.800> uses<01:12:54.010> this<01:12:54.220> cool<01:12:54.490> new<01:12:54.610> accumulator 01:12:55.080 --> 01:12:55.090 align:start position:0% and it uses this cool new accumulator 01:12:55.090 --> 01:12:56.880 align:start position:0% and it uses this cool new accumulator format<01:12:55.480> and<01:12:55.600> a<01:12:55.630> bunch<01:12:55.810> of<01:12:55.900> developers<01:12:56.230> want<01:12:56.830> to 01:12:56.880 --> 01:12:56.890 align:start position:0% format and a bunch of developers want to 01:12:56.890 --> 01:12:58.740 align:start position:0% format and a bunch of developers want to work<01:12:57.220> on<01:12:57.400> that<01:12:57.610> start<01:12:58.030> writing<01:12:58.210> contracts<01:12:58.660> for 01:12:58.740 --> 01:12:58.750 align:start position:0% work on that start writing contracts for 01:12:58.750 --> 01:13:00.930 align:start position:0% work on that start writing contracts for that<01:12:58.900> gap<01:12:59.170> you<01:12:59.410> kind<01:13:00.130> of<01:13:00.160> organize<01:13:00.550> zero 01:13:00.930 --> 01:13:00.940 align:start position:0% that gap you kind of organize zero 01:13:00.940 --> 01:13:03.450 align:start position:0% that gap you kind of organize zero you're<01:13:01.930> an<01:13:01.990> approach<01:13:02.260> to<01:13:02.470> do<01:13:02.590> that<01:13:02.740> but<01:13:03.370> you 01:13:03.450 --> 01:13:03.460 align:start position:0% you're an approach to do that but you 01:13:03.460 --> 01:13:06.000 align:start position:0% you're an approach to do that but you could<01:13:03.550> also<01:13:03.700> just<01:13:03.850> I<01:13:04.390> see<01:13:04.990> also<01:13:05.110> world<01:13:05.470> where<01:13:05.710> I 01:13:06.000 --> 01:13:06.010 align:start position:0% could also just I see also world where I 01:13:06.010 --> 01:13:09.000 align:start position:0% could also just I see also world where I can<01:13:06.190> just<01:13:06.370> you<01:13:06.670> know<01:13:06.700> play<01:13:07.450> if<01:13:08.050> I<01:13:08.260> want<01:13:08.620> to<01:13:08.710> you 01:13:09.000 --> 01:13:09.010 align:start position:0% can just you know play if I want to you 01:13:09.010 --> 01:13:11.010 align:start position:0% can just you know play if I want to you know<01:13:09.130> depending<01:13:09.730> on<01:13:09.850> how<01:13:10.150> much<01:13:10.330> costs<01:13:10.780> on<01:13:10.900> it 01:13:11.010 --> 01:13:11.020 align:start position:0% know depending on how much costs on it 01:13:11.020 --> 01:13:13.380 align:start position:0% know depending on how much costs on it employee<01:13:11.320> an<01:13:12.250> experiment<01:13:12.880> with<01:13:12.970> it<01:13:13.120> on<01:13:13.240> my<01:13:13.270> own 01:13:13.380 --> 01:13:13.390 align:start position:0% employee an experiment with it on my own 01:13:13.390 --> 01:13:16.200 align:start position:0% employee an experiment with it on my own and<01:13:13.750> I<01:13:13.870> could<01:13:14.320> do<01:13:14.440> that<01:13:14.590> but<01:13:15.580> again<01:13:15.820> I<01:13:16.120> think 01:13:16.200 --> 01:13:16.210 align:start position:0% and I could do that but again I think 01:13:16.210 --> 01:13:18.210 align:start position:0% and I could do that but again I think you<01:13:16.510> know<01:13:16.570> there's<01:13:16.930> a<01:13:16.990> lot<01:13:17.140> there<01:13:17.290> here<01:13:17.530> Casey 01:13:18.210 --> 01:13:18.220 align:start position:0% you know there's a lot there here Casey 01:13:18.220 --> 01:13:20.640 align:start position:0% you know there's a lot there here Casey wanted<01:13:18.520> a<01:13:18.700> comment<01:13:19.210> or<01:13:19.360> message<01:13:19.570> did<01:13:20.020> okay 01:13:20.640 --> 01:13:20.650 align:start position:0% wanted a comment or message did okay 01:13:20.650 --> 01:13:26.430 align:start position:0% wanted a comment or message did okay then<01:13:20.800> retires<01:13:21.190> the<01:13:21.400> members 01:13:26.430 --> 01:13:26.440 align:start position:0% 01:13:26.440 --> 01:13:30.570 align:start position:0% oh<01:13:27.180> yeah<01:13:28.770> you<01:13:29.770> kind<01:13:29.980> of<01:13:30.040> covered<01:13:30.280> it<01:13:30.400> but 01:13:30.570 --> 01:13:30.580 align:start position:0% oh yeah you kind of covered it but 01:13:30.580 --> 01:13:33.780 align:start position:0% oh yeah you kind of covered it but essentially<01:13:30.970> like<01:13:31.330> the<01:13:32.370> chain<01:13:33.370> is<01:13:33.610> this 01:13:33.780 --> 01:13:33.790 align:start position:0% essentially like the chain is this 01:13:33.790 --> 01:13:37.740 align:start position:0% essentially like the chain is this highly<01:13:34.510> available<01:13:35.190> in<01:13:36.190> the<01:13:36.370> system<01:13:36.520> if<01:13:37.390> you're 01:13:37.740 --> 01:13:37.750 align:start position:0% highly available in the system if you're 01:13:37.750 --> 01:13:39.480 align:start position:0% highly available in the system if you're syncing<01:13:38.140> any<01:13:38.290> sharks<01:13:38.710> you're<01:13:39.040> also<01:13:39.280> seem<01:13:39.460> to 01:13:39.480 --> 01:13:39.490 align:start position:0% syncing any sharks you're also seem to 01:13:39.490 --> 01:13:42.720 align:start position:0% syncing any sharks you're also seem to be<01:13:39.700> a<01:13:39.820> chain<01:13:40.090> and<01:13:40.510> so<01:13:40.690> having<01:13:41.320> having<01:13:42.040> data 01:13:42.720 --> 01:13:42.730 align:start position:0% be a chain and so having having data 01:13:42.730 --> 01:13:45.540 align:start position:0% be a chain and so having having data deployed<01:13:43.270> on<01:13:43.420> it<01:13:43.570> having<01:13:43.930> these<01:13:44.080> easily<01:13:44.550> can 01:13:45.540 --> 01:13:45.550 align:start position:0% deployed on it having these easily can 01:13:45.550 --> 01:13:50.460 align:start position:0% deployed on it having these easily can and<01:13:45.970> must<01:13:46.450> be<01:13:46.720> expensive<01:13:47.110> and<01:13:48.010> so<01:13:48.310> I<01:13:49.300> don't<01:13:50.200> I 01:13:50.460 --> 01:13:50.470 align:start position:0% and must be expensive and so I don't I 01:13:50.470 --> 01:13:53.460 align:start position:0% and must be expensive and so I don't I don't<01:13:51.460> see<01:13:51.880> a<01:13:51.910> world<01:13:52.210> on<01:13:52.300> my<01:13:52.390> team<01:13:52.600> it<01:13:52.960> makes 01:13:53.460 --> 01:13:53.470 align:start position:0% don't see a world on my team it makes 01:13:53.470 --> 01:13:55.140 align:start position:0% don't see a world on my team it makes sense<01:13:53.740> to<01:13:53.950> employ<01:13:54.250> and<01:13:54.580> in<01:13:54.760> a<01:13:54.820> world<01:13:55.000> in<01:13:55.120> which 01:13:55.140 --> 01:13:55.150 align:start position:0% sense to employ and in a world in which 01:13:55.150 --> 01:13:57.510 align:start position:0% sense to employ and in a world in which gaps<01:13:55.690> are<01:13:55.930> highly<01:13:56.320> used<01:13:56.470> across<01:13:56.710> across<01:13:57.400> the 01:13:57.510 --> 01:13:57.520 align:start position:0% gaps are highly used across across the 01:13:57.520 --> 01:13:59.660 align:start position:0% gaps are highly used across across the globe<01:13:57.700> the<01:13:58.210> cost<01:13:58.450> model<01:13:58.630> can't<01:13:58.960> be<01:13:59.110> such<01:13:59.320> that 01:13:59.660 --> 01:13:59.670 align:start position:0% globe the cost model can't be such that 01:13:59.670 --> 01:14:03.630 align:start position:0% globe the cost model can't be such that every<01:14:00.670> gap<01:14:00.850> is<01:14:01.120> deployed<01:14:01.510> right<01:14:02.400> you<01:14:03.400> might 01:14:03.630 --> 01:14:03.640 align:start position:0% every gap is deployed right you might 01:14:03.640 --> 01:14:05.790 align:start position:0% every gap is deployed right you might something<01:14:04.330> like<01:14:04.420> mega<01:14:04.780> casino<01:14:05.350> death<01:14:05.560> might 01:14:05.790 --> 01:14:05.800 align:start position:0% something like mega casino death might 01:14:05.800 --> 01:14:07.550 align:start position:0% something like mega casino death might deploy<01:14:06.070> their<01:14:06.250> army<01:14:06.460> is<01:14:06.490> there<01:14:06.910> some<01:14:07.120> strange 01:14:07.550 --> 01:14:07.560 align:start position:0% deploy their army is there some strange 01:14:07.560 --> 01:14:10.020 align:start position:0% deploy their army is there some strange advertising<01:14:08.560> thing<01:14:08.740> but<01:14:08.950> but<01:14:09.400> generally<01:14:09.880> in 01:14:10.020 --> 01:14:10.030 align:start position:0% advertising thing but but generally in 01:14:10.030 --> 01:14:13.680 align:start position:0% advertising thing but but generally in terms<01:14:10.060> of<01:14:10.420> like<01:14:10.600> hands<01:14:10.930> like<01:14:11.200> being<01:14:12.690> being 01:14:13.680 --> 01:14:13.690 align:start position:0% terms of like hands like being being 01:14:13.690 --> 01:14:15.840 align:start position:0% terms of like hands like being being close<01:14:14.050> to<01:14:14.290> other<01:14:14.410> gaps<01:14:14.740> and<01:14:15.070> like<01:14:15.190> operating<01:14:15.670> a 01:14:15.840 --> 01:14:15.850 align:start position:0% close to other gaps and like operating a 01:14:15.850 --> 01:14:18.330 align:start position:0% close to other gaps and like operating a hand<01:14:16.060> and<01:14:16.270> ways<01:14:16.480> of<01:14:16.720> scale<01:14:16.960> and<01:14:17.320> also<01:14:17.980> the<01:14:18.130> cost 01:14:18.330 --> 01:14:18.340 align:start position:0% hand and ways of scale and also the cost 01:14:18.340 --> 01:14:19.800 align:start position:0% hand and ways of scale and also the cost model<01:14:18.760> of<01:14:18.850> deploying<01:14:19.210> something<01:14:19.420> within<01:14:19.720> it 01:14:19.800 --> 01:14:19.810 align:start position:0% model of deploying something within it 01:14:19.810 --> 01:14:23.010 align:start position:0% model of deploying something within it would<01:14:20.170> be<01:14:20.230> such<01:14:20.500> so<01:14:20.920> much<01:14:21.070> less<01:14:21.580> that<01:14:21.910> Li<01:14:22.060> you 01:14:23.010 --> 01:14:23.020 align:start position:0% would be such so much less that Li you 01:14:23.020 --> 01:14:25.500 align:start position:0% would be such so much less that Li you you<01:14:23.050> likely<01:14:23.950> operate<01:14:24.370> within<01:14:24.610> Neath<01:14:24.910> my<01:14:25.030> ear 01:14:25.500 --> 01:14:25.510 align:start position:0% you likely operate within Neath my ear 01:14:25.510 --> 01:14:28.070 align:start position:0% you likely operate within Neath my ear in<01:14:25.810> need<01:14:26.080> to<01:14:26.320> e<01:14:26.350> or<01:14:26.770> or<01:14:27.040> within<01:14:27.520> some<01:14:27.820> other 01:14:28.070 --> 01:14:28.080 align:start position:0% in need to e or or within some other 01:14:28.080 --> 01:14:31.410 align:start position:0% in need to e or or within some other thought<01:14:29.080> oh<01:14:29.110> yeah<01:14:29.350> but<01:14:29.560> uh<01:14:29.590> whether<01:14:30.420> they're 01:14:31.410 --> 01:14:31.420 align:start position:0% thought oh yeah but uh whether they're 01:14:31.420 --> 01:14:33.630 align:start position:0% thought oh yeah but uh whether they're tools<01:14:31.750> for<01:14:32.140> developers<01:14:32.680> but<01:14:32.860> they're<01:14:33.280> they're 01:14:33.630 --> 01:14:33.640 align:start position:0% tools for developers but they're they're 01:14:33.640 --> 01:14:36.360 align:start position:0% tools for developers but they're they're more<01:14:33.910> alike<01:14:34.180> it<01:14:34.990> might<01:14:35.140> mean<01:14:35.380> more<01:14:35.980> akin<01:14:36.310> to 01:14:36.360 --> 01:14:36.370 align:start position:0% more alike it might mean more akin to 01:14:36.370 --> 01:14:38.670 align:start position:0% more alike it might mean more akin to protocol<01:14:36.790> development<01:14:37.240> in<01:14:38.230> traditional 01:14:38.670 --> 01:14:38.680 align:start position:0% protocol development in traditional 01:14:38.680 --> 01:14:46.830 align:start position:0% protocol development in traditional sense<01:14:38.920> than<01:14:39.070> they<01:14:39.160> are<01:14:39.190> to<01:14:39.520> death<01:14:39.670> Bowman<01:14:45.840> yeah 01:14:46.830 --> 01:14:46.840 align:start position:0% sense than they are to death Bowman yeah 01:14:46.840 --> 01:14:49.260 align:start position:0% sense than they are to death Bowman yeah I<01:14:46.870> think<01:14:47.020> this<01:14:47.260> question<01:14:47.440> about<01:14:48.270> weekend 01:14:49.260 --> 01:14:49.270 align:start position:0% I think this question about weekend 01:14:49.270 --> 01:14:51.750 align:start position:0% I think this question about weekend employees<01:14:49.840> and<01:14:50.380> how<01:14:50.440> many<01:14:50.620> keys<01:14:51.100> you<01:14:51.640> know 01:14:51.750 --> 01:14:51.760 align:start position:0% employees and how many keys you know 01:14:51.760 --> 01:14:55.770 align:start position:0% employees and how many keys you know there<01:14:52.240> might<01:14:52.420> be<01:14:52.480> is<01:14:53.880> biggest<01:14:54.880> you<01:14:55.690> know 01:14:55.770 --> 01:14:55.780 align:start position:0% there might be is biggest you know 01:14:55.780 --> 01:14:59.520 align:start position:0% there might be is biggest you know unresolved<01:14:58.020> question<01:14:59.020> if<01:14:59.080> I<01:14:59.140> was<01:14:59.260> there's<01:14:59.470> a 01:14:59.520 --> 01:14:59.530 align:start position:0% unresolved question if I was there's a 01:14:59.530 --> 01:15:05.130 align:start position:0% unresolved question if I was there's a range<01:14:59.770> of<01:14:59.890> opinions<01:15:00.310> and<01:15:03.330> ways<01:15:04.330> like<01:15:04.780> I<01:15:04.930> think 01:15:05.130 --> 01:15:05.140 align:start position:0% range of opinions and ways like I think 01:15:05.140 --> 01:15:12.330 align:start position:0% range of opinions and ways like I think the<01:15:05.290> split<01:15:05.650> came<01:15:06.100> from<01:15:06.990> the<01:15:09.720> heart<01:15:10.720> to<01:15:11.340> the 01:15:12.330 --> 01:15:12.340 align:start position:0% the split came from the heart to the 01:15:12.340 --> 01:15:14.430 align:start position:0% the split came from the heart to the idea<01:15:12.580> of<01:15:12.640> minimal<01:15:12.970> execution<01:15:13.540> when<01:15:14.200> you<01:15:14.290> had 01:15:14.430 --> 01:15:14.440 align:start position:0% idea of minimal execution when you had 01:15:14.440 --> 01:15:17.490 align:start position:0% idea of minimal execution when you had phase<01:15:14.890> one<01:15:15.130> and<01:15:15.400> then<01:15:16.200> and<01:15:17.200> there<01:15:17.320> was<01:15:17.410> no 01:15:17.490 --> 01:15:17.500 align:start position:0% phase one and then and there was no 01:15:17.500 --> 01:15:18.990 align:start position:0% phase one and then and there was no execution<01:15:17.980> phase<01:15:18.190> one 01:15:18.990 --> 01:15:19.000 align:start position:0% execution phase one 01:15:19.000 --> 01:15:20.700 align:start position:0% execution phase one there's<01:15:19.180> only<01:15:19.270> institutions<01:15:19.840> phase<01:15:20.080> 2<01:15:20.350> and 01:15:20.700 --> 01:15:20.710 align:start position:0% there's only institutions phase 2 and 01:15:20.710 --> 01:15:23.640 align:start position:0% there's only institutions phase 2 and phase<01:15:20.770> 2<01:15:22.020> was<01:15:23.020> supposed<01:15:23.320> to<01:15:23.380> be<01:15:23.470> this 01:15:23.640 --> 01:15:23.650 align:start position:0% phase 2 was supposed to be this 01:15:23.650 --> 01:15:26.160 align:start position:0% phase 2 was supposed to be this execution<01:15:24.130> that<01:15:24.490> was<01:15:24.550> maximally<01:15:25.360> similar<01:15:25.720> to 01:15:26.160 --> 01:15:26.170 align:start position:0% execution that was maximally similar to 01:15:26.170 --> 01:15:29.850 align:start position:0% execution that was maximally similar to each<01:15:26.320> one<01:15:26.560> and<01:15:26.890> so<01:15:27.580> shards<01:15:28.000> you'd<01:15:28.210> have<01:15:28.860> 1,000 01:15:29.850 --> 01:15:29.860 align:start position:0% each one and so shards you'd have 1,000 01:15:29.860 --> 01:15:33.540 align:start position:0% each one and so shards you'd have 1,000 copies<01:15:30.040> a<01:15:30.250> piece<01:15:30.430> of<01:15:30.760> each<01:15:31.030> one<01:15:31.300> and<01:15:32.550> the 01:15:33.540 --> 01:15:33.550 align:start position:0% copies a piece of each one and the 01:15:33.550 --> 01:15:36.030 align:start position:0% copies a piece of each one and the execution<01:15:34.450> would<01:15:34.750> be<01:15:34.870> stateful<01:15:35.470> like<01:15:35.860> each 01:15:36.030 --> 01:15:36.040 align:start position:0% execution would be stateful like each 01:15:36.040 --> 01:15:40.140 align:start position:0% execution would be stateful like each one<01:15:36.310> and<01:15:36.580> it<01:15:36.880> would<01:15:37.650> you<01:15:38.650> know<01:15:38.910> prescribe<01:15:39.910> it 01:15:40.140 --> 01:15:40.150 align:start position:0% one and it would you know prescribe it 01:15:40.150 --> 01:15:43.320 align:start position:0% one and it would you know prescribe it would<01:15:40.240> have<01:15:40.660> an<01:15:40.780> account<01:15:41.080> structure<01:15:42.210> you<01:15:43.210> know 01:15:43.320 --> 01:15:43.330 align:start position:0% would have an account structure you know 01:15:43.330 --> 01:15:45.360 align:start position:0% would have an account structure you know apartment<01:15:44.020> restructure<01:15:44.410> everything<01:15:44.800> like 01:15:45.360 --> 01:15:45.370 align:start position:0% apartment restructure everything like 01:15:45.370 --> 01:15:49.050 align:start position:0% apartment restructure everything like he's<01:15:46.740> you<01:15:47.740> know<01:15:47.860> like<01:15:48.010> he's<01:15:48.160> one<01:15:48.370> but<01:15:48.610> better 01:15:49.050 --> 01:15:49.060 align:start position:0% he's you know like he's one but better 01:15:49.060 --> 01:15:54.450 align:start position:0% he's you know like he's one but better and<01:15:50.730> the<01:15:51.730> shift<01:15:52.030> to<01:15:52.300> minimal<01:15:52.930> execution<01:15:53.500> said 01:15:54.450 --> 01:15:54.460 align:start position:0% and the shift to minimal execution said 01:15:54.460 --> 01:15:57.450 align:start position:0% and the shift to minimal execution said well<01:15:55.090> no<01:15:55.300> you<01:15:55.660> know<01:15:56.260> these<01:15:56.800> execution 01:15:57.450 --> 01:15:57.460 align:start position:0% well no you know these execution 01:15:57.460 --> 01:16:01.230 align:start position:0% well no you know these execution environments<01:15:59.370> the<01:16:00.370> execution<01:16:00.820> environments 01:16:01.230 --> 01:16:01.240 align:start position:0% environments the execution environments 01:16:01.240 --> 01:16:04.650 align:start position:0% environments the execution environments will<01:16:01.390> define<01:16:02.110> these<01:16:02.350> and<01:16:03.330> an<01:16:04.330> execution 01:16:04.650 --> 01:16:04.660 align:start position:0% will define these and an execution 01:16:04.660 --> 01:16:07.320 align:start position:0% will define these and an execution environment<01:16:05.290> it's<01:16:05.800> just<01:16:06.070> a<01:16:06.160> fancy<01:16:06.430> word<01:16:06.670> for<01:16:06.730> a 01:16:07.320 --> 01:16:07.330 align:start position:0% environment it's just a fancy word for a 01:16:07.330 --> 01:16:11.340 align:start position:0% environment it's just a fancy word for a contract<01:16:08.290> unease<01:16:08.830> -<01:16:09.070> the<01:16:09.520> way<01:16:09.610> I<01:16:09.670> see<01:16:09.880> it<01:16:10.320> had<01:16:11.320> a 01:16:11.340 --> 01:16:11.350 align:start position:0% contract unease - the way I see it had a 01:16:11.350 --> 01:16:13.050 align:start position:0% contract unease - the way I see it had a slide<01:16:11.620> that<01:16:11.650> said<01:16:12.070> not<01:16:12.880> necessarily 01:16:13.050 --> 01:16:13.060 align:start position:0% slide that said not necessarily 01:16:13.060 --> 01:16:18.270 align:start position:0% slide that said not necessarily analogous<01:16:14.020> to<01:16:14.820> smart<01:16:15.820> contracts<01:16:16.270> I<01:16:16.510> guess<01:16:17.320> the 01:16:18.270 --> 01:16:18.280 align:start position:0% analogous to smart contracts I guess the 01:16:18.280 --> 01:16:21.470 align:start position:0% analogous to smart contracts I guess the main<01:16:18.550> difference<01:16:19.060> here<01:16:19.330> is<01:16:19.510> underneath<01:16:20.200> won<01:16:20.560> a 01:16:21.470 --> 01:16:21.480 align:start position:0% main difference here is underneath won a 01:16:21.480 --> 01:16:26.370 align:start position:0% main difference here is underneath won a contract<01:16:22.650> cannot<01:16:24.090> run<01:16:25.090> IBM<01:16:25.540> code<01:16:25.840> but<01:16:26.170> there's 01:16:26.370 --> 01:16:26.380 align:start position:0% contract cannot run IBM code but there's 01:16:26.380 --> 01:16:28.920 align:start position:0% contract cannot run IBM code but there's an<01:16:26.530> old<01:16:26.650> EAP<01:16:27.100> like<01:16:27.730> from<01:16:28.000> metallic<01:16:28.450> to<01:16:28.660> add<01:16:28.900> a 01:16:28.920 --> 01:16:28.930 align:start position:0% an old EAP like from metallic to add a 01:16:28.930 --> 01:16:33.360 align:start position:0% an old EAP like from metallic to add a mouth<01:16:29.200> code<01:16:29.470> like<01:16:30.070> brownie<01:16:30.430> BM<01:16:30.970> so<01:16:31.930> when<01:16:32.800> an<01:16:33.100> EE 01:16:33.360 --> 01:16:33.370 align:start position:0% mouth code like brownie BM so when an EE 01:16:33.370 --> 01:16:36.990 align:start position:0% mouth code like brownie BM so when an EE and<01:16:33.940> analogous<01:16:34.840> to<01:16:35.080> a<01:16:35.440> contract<01:16:36.340> on<01:16:36.490> East<01:16:36.760> one 01:16:36.990 --> 01:16:37.000 align:start position:0% and analogous to a contract on East one 01:16:37.000 --> 01:16:40.290 align:start position:0% and analogous to a contract on East one with<01:16:37.510> the<01:16:37.900> extra<01:16:38.260> opcode<01:16:38.950> of<01:16:38.980> row<01:16:39.820> and<01:16:39.940> Wasson 01:16:40.290 --> 01:16:40.300 align:start position:0% with the extra opcode of row and Wasson 01:16:40.300 --> 01:16:50.060 align:start position:0% with the extra opcode of row and Wasson you<01:16:40.840> know<01:16:40.930> or<01:16:41.110> from<01:16:41.440> EBM<01:16:42.900> and<01:16:45.540> so<01:16:47.910> in<01:16:48.910> the<01:16:49.480> EE 01:16:50.060 --> 01:16:50.070 align:start position:0% you know or from EBM and so in the EE 01:16:50.070 --> 01:16:53.580 align:start position:0% you know or from EBM and so in the EE like<01:16:51.070> you<01:16:51.280> can<01:16:51.460> you<01:16:51.580> can<01:16:51.730> take<01:16:51.940> a<01:16:52.350> view<01:16:53.350> point 01:16:53.580 --> 01:16:53.590 align:start position:0% like you can you can take a view point 01:16:53.590 --> 01:16:57.840 align:start position:0% like you can you can take a view point where<01:16:54.570> the<01:16:55.570> EE<01:16:55.810> would<01:16:56.350> sort<01:16:56.590> of<01:16:56.650> define<01:16:57.100> all 01:16:57.840 --> 01:16:57.850 align:start position:0% where the EE would sort of define all 01:16:57.850 --> 01:16:59.820 align:start position:0% where the EE would sort of define all this<01:16:58.090> stuff<01:16:58.360> that<01:16:58.600> enables<01:16:59.260> people<01:16:59.440> to<01:16:59.590> have<01:16:59.800> a 01:16:59.820 --> 01:16:59.830 align:start position:0% this stuff that enables people to have a 01:16:59.830 --> 01:17:01.439 align:start position:0% this stuff that enables people to have a good<01:17:00.100> user<01:17:00.250> experiences<01:17:00.970> and 01:17:01.439 --> 01:17:01.449 align:start position:0% good user experiences and 01:17:01.449 --> 01:17:04.770 align:start position:0% good user experiences and and<01:17:01.860> defines<01:17:02.860> how<01:17:03.130> like<01:17:03.400> contracts<01:17:04.360> call<01:17:04.630> each 01:17:04.770 --> 01:17:04.780 align:start position:0% and defines how like contracts call each 01:17:04.780 --> 01:17:09.780 align:start position:0% and defines how like contracts call each other<01:17:04.900> and<01:17:05.050> so<01:17:05.350> forth<01:17:06.000> and<01:17:08.280> so<01:17:09.280> in<01:17:09.489> the<01:17:09.580> old 01:17:09.780 --> 01:17:09.790 align:start position:0% other and so forth and so in the old 01:17:09.790 --> 01:17:12.000 align:start position:0% other and so forth and so in the old model<01:17:10.030> it<01:17:10.239> was<01:17:10.300> like<01:17:10.449> for<01:17:10.900> developers<01:17:11.530> would 01:17:12.000 --> 01:17:12.010 align:start position:0% model it was like for developers would 01:17:12.010 --> 01:17:14.669 align:start position:0% model it was like for developers would develop<01:17:12.460> all<01:17:12.730> this<01:17:12.850> stuff<01:17:13.090> at<01:17:13.480> phase<01:17:13.989> two<01:17:14.020> and 01:17:14.669 --> 01:17:14.679 align:start position:0% develop all this stuff at phase two and 01:17:14.679 --> 01:17:16.709 align:start position:0% develop all this stuff at phase two and then<01:17:14.949> the<01:17:15.610> app<01:17:15.670> developers<01:17:16.210> would<01:17:16.330> come<01:17:16.570> on 01:17:16.709 --> 01:17:16.719 align:start position:0% then the app developers would come on 01:17:16.719 --> 01:17:20.820 align:start position:0% then the app developers would come on and<01:17:16.989> then<01:17:17.140> you<01:17:17.830> know<01:17:17.949> use<01:17:18.520> the<01:17:19.270> toy<01:17:19.480> depth<01:17:19.830> on 01:17:20.820 --> 01:17:20.830 align:start position:0% and then you know use the toy depth on 01:17:20.830 --> 01:17:24.390 align:start position:0% and then you know use the toy depth on these<01:17:21.070> two<01:17:21.570> with<01:17:22.570> minimal<01:17:22.960> execution<01:17:23.500> it's 01:17:24.390 --> 01:17:24.400 align:start position:0% these two with minimal execution it's 01:17:24.400 --> 01:17:28.650 align:start position:0% these two with minimal execution it's kind<01:17:25.330> of<01:17:25.390> like<01:17:26.880> we<01:17:27.880> spend<01:17:28.150> philosophy<01:17:28.540> with 01:17:28.650 --> 01:17:28.660 align:start position:0% kind of like we spend philosophy with 01:17:28.660 --> 01:17:31.229 align:start position:0% kind of like we spend philosophy with minimal<01:17:28.929> execution<01:17:29.380> ISM<01:17:29.650> this<01:17:30.219> is<01:17:30.429> a<01:17:30.460> massive 01:17:31.229 --> 01:17:31.239 align:start position:0% minimal execution ISM this is a massive 01:17:31.239 --> 01:17:36.090 align:start position:0% minimal execution ISM this is a massive -<01:17:31.480> challenge<01:17:31.719> -<01:17:32.610> and<01:17:34.650> it<01:17:35.650> not<01:17:35.830> only<01:17:35.860> is<01:17:36.010> a 01:17:36.090 --> 01:17:36.100 align:start position:0% - challenge - and it not only is a 01:17:36.100 --> 01:17:37.979 align:start position:0% - challenge - and it not only is a massive<01:17:36.400> challenge<01:17:36.550> but<01:17:36.910> if<01:17:37.270> it's<01:17:37.480> also<01:17:37.690> very 01:17:37.979 --> 01:17:37.989 align:start position:0% massive challenge but if it's also very 01:17:37.989 --> 01:17:41.939 align:start position:0% massive challenge but if it's also very opinionated<01:17:38.290> approach<01:17:38.860> and<01:17:39.160> in<01:17:40.530> my<01:17:41.530> opinion 01:17:41.939 --> 01:17:41.949 align:start position:0% opinionated approach and in my opinion 01:17:41.949 --> 01:17:45.360 align:start position:0% opinionated approach and in my opinion it's<01:17:42.310> it's<01:17:43.060> like<01:17:43.360> kind<01:17:43.870> of<01:17:43.989> authoritarian<01:17:44.890> and 01:17:45.360 --> 01:17:45.370 align:start position:0% it's it's like kind of authoritarian and 01:17:45.370 --> 01:17:50.130 align:start position:0% it's it's like kind of authoritarian and dictatorial<01:17:46.030> to<01:17:46.719> say<01:17:46.980> like<01:17:47.980> well<01:17:48.840> you<01:17:49.840> know<01:17:49.929> we 01:17:50.130 --> 01:17:50.140 align:start position:0% dictatorial to say like well you know we 01:17:50.140 --> 01:17:52.020 align:start position:0% dictatorial to say like well you know we want<01:17:50.320> to<01:17:50.350> restrict<01:17:50.679> the<01:17:51.219> EES<01:17:51.580> that<01:17:51.850> could<01:17:51.969> be 01:17:52.020 --> 01:17:52.030 align:start position:0% want to restrict the EES that could be 01:17:52.030 --> 01:17:54.689 align:start position:0% want to restrict the EES that could be to<01:17:52.120> put<01:17:52.330> immediate<01:17:52.929> response<01:17:53.350> encode<01:17:53.650> so<01:17:54.280> why 01:17:54.689 --> 01:17:54.699 align:start position:0% to put immediate response encode so why 01:17:54.699 --> 01:17:57.180 align:start position:0% to put immediate response encode so why would<01:17:54.880> you<01:17:54.910> restrict<01:17:55.480> what<01:17:56.320> was<01:17:56.530> in<01:17:56.679> code 01:17:57.180 --> 01:17:57.190 align:start position:0% would you restrict what was in code 01:17:57.190 --> 01:17:59.430 align:start position:0% would you restrict what was in code you<01:17:57.580> know<01:17:57.670> people<01:17:58.060> can<01:17:58.210> deploy<01:17:58.510> you<01:17:59.320> know 01:17:59.430 --> 01:17:59.440 align:start position:0% you know people can deploy you know 01:17:59.440 --> 01:18:01.290 align:start position:0% you know people can deploy you know people<01:17:59.739> shoot<01:17:59.949> some<01:18:00.250> fully<01:18:00.460> run<01:18:00.730> whatever 01:18:01.290 --> 01:18:01.300 align:start position:0% people shoot some fully run whatever 01:18:01.300 --> 01:18:03.120 align:start position:0% people shoot some fully run whatever wasn't<01:18:01.719> what<01:18:01.870> they<01:18:01.989> wanted<01:18:02.170> like<01:18:02.350> like<01:18:02.980> they 01:18:03.120 --> 01:18:03.130 align:start position:0% wasn't what they wanted like like they 01:18:03.130 --> 01:18:06.450 align:start position:0% wasn't what they wanted like like they can<01:18:03.280> run<01:18:03.460> any<01:18:03.640> PM<01:18:04.000> quote<01:18:04.239> they<01:18:04.390> want<01:18:05.460> he's 01:18:06.450 --> 01:18:06.460 align:start position:0% can run any PM quote they want he's 01:18:06.460 --> 01:18:06.900 align:start position:0% can run any PM quote they want he's funny 01:18:06.900 --> 01:18:06.910 align:start position:0% funny 01:18:06.910 --> 01:18:12.180 align:start position:0% funny I<01:18:08.010> will<01:18:09.010> and<01:18:09.370> I<01:18:09.429> like<01:18:09.699> when<01:18:09.940> I<01:18:09.969> uh<01:18:10.590> my<01:18:11.590> opinion 01:18:12.180 --> 01:18:12.190 align:start position:0% I will and I like when I uh my opinion 01:18:12.190 --> 01:18:17.700 align:start position:0% I will and I like when I uh my opinion and<01:18:12.460> weaknesses<01:18:13.060> like<01:18:13.300> broad<01:18:16.290> but<01:18:17.290> I<01:18:17.320> will<01:18:17.500> say 01:18:17.700 --> 01:18:17.710 align:start position:0% and weaknesses like broad but I will say 01:18:17.710 --> 01:18:20.979 align:start position:0% and weaknesses like broad but I will say the<01:18:17.980> opinion<01:18:18.340> of<01:18:18.489> Justice<01:18:19.179> which<01:18:19.480> interest 01:18:20.979 --> 01:18:20.989 align:start position:0% the opinion of Justice which interest 01:18:20.989 --> 01:18:24.790 align:start position:0% the opinion of Justice which interest Tiger<01:18:21.790> ease<01:18:23.110> we<01:18:24.110> have<01:18:24.230> this<01:18:24.380> world<01:18:24.590> in<01:18:24.739> which 01:18:24.790 --> 01:18:24.800 align:start position:0% Tiger ease we have this world in which 01:18:24.800 --> 01:18:27.970 align:start position:0% Tiger ease we have this world in which forget<01:18:25.040> we<01:18:25.160> want<01:18:25.370> you<01:18:25.550> to<01:18:25.760> be<01:18:25.940> into<01:18:26.600> E<01:18:26.630> and<01:18:27.140> a 01:18:27.970 --> 01:18:27.980 align:start position:0% forget we want you to be into E and a 01:18:27.980 --> 01:18:31.090 align:start position:0% forget we want you to be into E and a movie<01:18:28.820> E<01:18:28.850> and<01:18:29.270> at<01:18:29.360> this<01:18:29.450> he<01:18:29.660> and<01:18:30.200> some<01:18:30.739> other<01:18:30.890> EE 01:18:31.090 --> 01:18:31.100 align:start position:0% movie E and at this he and some other EE 01:18:31.100 --> 01:18:32.560 align:start position:0% movie E and at this he and some other EE and<01:18:31.310> then<01:18:31.430> another<01:18:31.670> one<01:18:31.910> that<01:18:32.150> looks<01:18:32.270> like<01:18:32.480> a 01:18:32.560 --> 01:18:32.570 align:start position:0% and then another one that looks like a 01:18:32.570 --> 01:18:34.420 align:start position:0% and then another one that looks like a llama<01:18:32.840> does<01:18:33.020> not<01:18:33.200> miss<01:18:33.440> definitely<01:18:33.860> we<01:18:34.280> have 01:18:34.420 --> 01:18:34.430 align:start position:0% llama does not miss definitely we have 01:18:34.430 --> 01:18:35.740 align:start position:0% llama does not miss definitely we have this<01:18:34.580> world<01:18:34.820> in<01:18:34.969> which<01:18:35.000> you<01:18:35.150> might<01:18:35.300> end<01:18:35.660> up 01:18:35.740 --> 01:18:35.750 align:start position:0% this world in which you might end up 01:18:35.750 --> 01:18:38.200 align:start position:0% this world in which you might end up having<01:18:35.810> like<01:18:36.110> a<01:18:36.230> very<01:18:36.380> fragmented<01:18:37.210> ecosystem 01:18:38.200 --> 01:18:38.210 align:start position:0% having like a very fragmented ecosystem 01:18:38.210 --> 01:18:42.070 align:start position:0% having like a very fragmented ecosystem where<01:18:38.710> if<01:18:39.710> you<01:18:40.010> instead<01:18:40.700> have<01:18:41.120> some<01:18:41.870> sort<01:18:42.050> of 01:18:42.070 --> 01:18:42.080 align:start position:0% where if you instead have some sort of 01:18:42.080 --> 01:18:43.810 align:start position:0% where if you instead have some sort of been<01:18:42.200> trying<01:18:42.350> to<01:18:42.590> start<01:18:43.190> and<01:18:43.430> this<01:18:43.489> is<01:18:43.670> like 01:18:43.810 --> 01:18:43.820 align:start position:0% been trying to start and this is like 01:18:43.820 --> 01:18:45.790 align:start position:0% been trying to start and this is like the<01:18:43.910> other<01:18:44.030> extreme<01:18:44.390> of<01:18:44.450> the<01:18:44.570> opinion<01:18:44.930> where 01:18:45.790 --> 01:18:45.800 align:start position:0% the other extreme of the opinion where 01:18:45.800 --> 01:18:48.820 align:start position:0% the other extreme of the opinion where it's<01:18:46.250> each<01:18:46.430> one<01:18:46.670> and<01:18:47.180> you<01:18:47.360> it<01:18:48.140> feels<01:18:48.469> like<01:18:48.680> each 01:18:48.820 --> 01:18:48.830 align:start position:0% it's each one and you it feels like each 01:18:48.830 --> 01:18:50.260 align:start position:0% it's each one and you it feels like each one<01:18:48.860> it<01:18:49.190> feels<01:18:49.310> like<01:18:49.550> being<01:18:49.700> how<01:18:49.880> models<01:18:50.180> that 01:18:50.260 --> 01:18:50.270 align:start position:0% one it feels like being how models that 01:18:50.270 --> 01:18:52.420 align:start position:0% one it feels like being how models that we<01:18:50.330> know<01:18:50.450> and<01:18:50.570> love<01:18:50.600> one<01:18:51.530> a<01:18:51.560> very<01:18:51.950> like<01:18:52.160> clear 01:18:52.420 --> 01:18:52.430 align:start position:0% we know and love one a very like clear 01:18:52.430 --> 01:18:54.310 align:start position:0% we know and love one a very like clear developers<01:18:53.030> story<01:18:53.540> on<01:18:53.719> how<01:18:53.840> to<01:18:53.900> build<01:18:54.080> on<01:18:54.230> this 01:18:54.310 --> 01:18:54.320 align:start position:0% developers story on how to build on this 01:18:54.320 --> 01:18:56.860 align:start position:0% developers story on how to build on this and<01:18:54.560> to<01:18:54.800> like<01:18:55.190> kind<01:18:55.760> of<01:18:55.790> creates<01:18:56.210> this<01:18:56.390> unified 01:18:56.860 --> 01:18:56.870 align:start position:0% and to like kind of creates this unified 01:18:56.870 --> 01:18:58.540 align:start position:0% and to like kind of creates this unified experience<01:18:57.140> where<01:18:57.680> everything<01:18:57.980> is<01:18:58.070> initially 01:18:58.540 --> 01:18:58.550 align:start position:0% experience where everything is initially 01:18:58.550 --> 01:19:00.100 align:start position:0% experience where everything is initially it<01:18:58.790> could<01:18:58.940> be<01:18:59.000> speaker<01:18:59.270> system<01:18:59.630> so<01:18:59.750> that's<01:18:59.930> the 01:19:00.100 --> 01:19:00.110 align:start position:0% it could be speaker system so that's the 01:19:00.110 --> 01:19:02.920 align:start position:0% it could be speaker system so that's the the<01:19:00.440> counter<01:19:00.800> to<01:19:00.950> the<01:19:01.040> dictatorial<01:19:01.810> view<01:19:02.810> of 01:19:02.920 --> 01:19:02.930 align:start position:0% the counter to the dictatorial view of 01:19:02.930 --> 01:19:03.430 align:start position:0% the counter to the dictatorial view of the<01:19:03.020> opinion 01:19:03.430 --> 01:19:03.440 align:start position:0% the opinion 01:19:03.440 --> 01:19:05.020 align:start position:0% the opinion I'm<01:19:03.620> not<01:19:03.860> certain<01:19:04.070> exactly<01:19:04.250> where<01:19:04.730> I<01:19:04.760> didn't 01:19:05.020 --> 01:19:05.030 align:start position:0% I'm not certain exactly where I didn't 01:19:05.030 --> 01:19:06.100 align:start position:0% I'm not certain exactly where I didn't where<01:19:05.120> I<01:19:05.150> live<01:19:05.390> but<01:19:05.480> I<01:19:05.570> just<01:19:05.660> wanted<01:19:05.840> to<01:19:05.930> get 01:19:06.100 --> 01:19:06.110 align:start position:0% where I live but I just wanted to get 01:19:06.110 --> 01:19:15.870 align:start position:0% where I live but I just wanted to get that<01:19:11.590> okay<01:19:13.600> since<01:19:14.600> you<01:19:14.719> cannot<01:19:14.930> update<01:19:15.200> these 01:19:15.870 --> 01:19:15.880 align:start position:0% that okay since you cannot update these 01:19:15.880 --> 01:19:19.240 align:start position:0% that okay since you cannot update these and<01:19:16.880> it's<01:19:17.030> fixed<01:19:17.270> if<01:19:17.960> you<01:19:18.440> do<01:19:18.590> end<01:19:18.770> up<01:19:18.920> with<01:19:19.190> a 01:19:19.240 --> 01:19:19.250 align:start position:0% and it's fixed if you do end up with a 01:19:19.250 --> 01:19:22.570 align:start position:0% and it's fixed if you do end up with a Chinese<01:19:19.940> and<01:19:20.440> you<01:19:21.440> keep<01:19:21.890> improving<01:19:22.040> those 01:19:22.570 --> 01:19:22.580 align:start position:0% Chinese and you keep improving those 01:19:22.580 --> 01:19:25.630 align:start position:0% Chinese and you keep improving those ease<01:19:22.790> and<01:19:23.719> even<01:19:23.960> at<01:19:24.080> the<01:19:24.140> point<01:19:24.340> is<01:19:25.340> it<01:19:25.460> going 01:19:25.630 --> 01:19:25.640 align:start position:0% ease and even at the point is it going 01:19:25.640 --> 01:19:29.830 align:start position:0% ease and even at the point is it going to<01:19:25.700> be<01:19:25.790> a<01:19:25.820> heart<01:19:26.030> or<01:19:26.270> earth<01:19:26.420> Lord<01:19:28.750> and<01:19:29.750> I'll 01:19:29.830 --> 01:19:29.840 align:start position:0% to be a heart or earth Lord and I'll 01:19:29.840 --> 01:19:32.350 align:start position:0% to be a heart or earth Lord and I'll give<01:19:30.020> the<01:19:30.110> mic<01:19:30.260> backgrounds<01:19:30.800> but<01:19:31.070> the<01:19:31.219> I<01:19:32.120> think 01:19:32.350 --> 01:19:32.360 align:start position:0% give the mic backgrounds but the I think 01:19:32.360 --> 01:19:34.450 align:start position:0% give the mic backgrounds but the I think it's<01:19:32.660> very<01:19:33.410> likely<01:19:33.590> that<01:19:33.950> at<01:19:34.130> least<01:19:34.250> one<01:19:34.430> of 01:19:34.450 --> 01:19:34.460 align:start position:0% it's very likely that at least one of 01:19:34.460 --> 01:19:36.990 align:start position:0% it's very likely that at least one of these<01:19:34.640> is<01:19:35.450> still<01:19:35.750> potentially<01:19:36.170> updated 01:19:36.990 --> 01:19:37.000 align:start position:0% these is still potentially updated 01:19:37.000 --> 01:19:39.300 align:start position:0% these is still potentially updated and<01:19:37.570> social<01:19:38.230> consensus<01:19:38.680> the<01:19:38.980> youth<01:19:39.130> won't 01:19:39.300 --> 01:19:39.310 align:start position:0% and social consensus the youth won't 01:19:39.310 --> 01:19:44.390 align:start position:0% and social consensus the youth won't leave<01:19:39.580> so<01:19:39.760> I<01:19:40.030> don't<01:19:40.210> think<01:19:40.300> that<01:19:40.420> is<01:19:42.810> ready<01:19:43.810> I 01:19:44.390 --> 01:19:44.400 align:start position:0% leave so I don't think that is ready I 01:19:44.400 --> 01:19:47.340 align:start position:0% leave so I don't think that is ready I think<01:19:45.400> that<01:19:45.910> I<01:19:46.300> think<01:19:46.870> that<01:19:46.960> it's<01:19:47.110> going<01:19:47.230> to<01:19:47.290> be 01:19:47.340 --> 01:19:47.350 align:start position:0% think that I think that it's going to be 01:19:47.350 --> 01:19:50.370 align:start position:0% think that I think that it's going to be very<01:19:47.470> hard<01:19:47.800> to<01:19:47.830> say<01:19:48.250> this<01:19:48.580> is<01:19:48.730> f1<01:19:48.940> now<01:19:49.300> and<01:19:49.630> you 01:19:50.370 --> 01:19:50.380 align:start position:0% very hard to say this is f1 now and you 01:19:50.380 --> 01:19:52.860 align:start position:0% very hard to say this is f1 now and you can<01:19:50.560> never<01:19:50.770> change<01:19:50.920> it<01:19:51.400> like<01:19:51.970> everyone<01:19:52.330> exists 01:19:52.860 --> 01:19:52.870 align:start position:0% can never change it like everyone exists 01:19:52.870 --> 01:19:54.000 align:start position:0% can never change it like everyone exists and<01:19:52.960> operates<01:19:53.290> in<01:19:53.350> this<01:19:53.500> there's<01:19:53.680> tons<01:19:53.920> of 01:19:54.000 --> 01:19:54.010 align:start position:0% and operates in this there's tons of 01:19:54.010 --> 01:19:55.620 align:start position:0% and operates in this there's tons of stuff<01:19:54.190> there<01:19:54.430> and<01:19:54.610> like<01:19:54.760> I<01:19:54.970> think<01:19:55.330> the<01:19:55.420> social 01:19:55.620 --> 01:19:55.630 align:start position:0% stuff there and like I think the social 01:19:55.630 --> 01:19:57.480 align:start position:0% stuff there and like I think the social consensus<01:19:56.260> is<01:19:56.410> still<01:19:56.620> hardcore<01:19:56.980> hand<01:19:57.160> might 01:19:57.480 --> 01:19:57.490 align:start position:0% consensus is still hardcore hand might 01:19:57.490 --> 01:20:00.600 align:start position:0% consensus is still hardcore hand might very<01:19:57.880> well<01:19:57.970> say<01:19:58.150> this<01:19:58.510> but<01:19:58.720> we<01:19:59.590> this<01:20:00.190> is<01:20:00.430> not 01:20:00.600 --> 01:20:00.610 align:start position:0% very well say this but we this is not 01:20:00.610 --> 01:20:06.090 align:start position:0% very well say this but we this is not quite<01:20:00.850> over<01:20:00.910> here<01:20:03.780> yeah<01:20:04.780> I<01:20:05.440> wanted<01:20:05.800> to<01:20:05.920> break 01:20:06.090 --> 01:20:06.100 align:start position:0% quite over here yeah I wanted to break 01:20:06.100 --> 01:20:07.620 align:start position:0% quite over here yeah I wanted to break the<01:20:06.160> especially<01:20:07.000> a<01:20:07.030> little<01:20:07.120> bit<01:20:07.360> here<01:20:07.510> because 01:20:07.620 --> 01:20:07.630 align:start position:0% the especially a little bit here because 01:20:07.630 --> 01:20:09.480 align:start position:0% the especially a little bit here because they<01:20:08.350> came<01:20:08.560> very<01:20:08.590> deep<01:20:09.010> and<01:20:09.190> I<01:20:09.250> actually 01:20:09.480 --> 01:20:09.490 align:start position:0% they came very deep and I actually 01:20:09.490 --> 01:20:13.680 align:start position:0% they came very deep and I actually wanted<01:20:09.880> to<01:20:09.940> give<01:20:10.920> the<01:20:11.920> microphone<01:20:12.160> to<01:20:12.690> you 01:20:13.680 --> 01:20:13.690 align:start position:0% wanted to give the microphone to you 01:20:13.690 --> 01:20:17.130 align:start position:0% wanted to give the microphone to you guys<01:20:13.870> and<01:20:14.190> I'd<01:20:15.190> listen<01:20:15.430> to<01:20:16.140> questions 01:20:17.130 --> 01:20:17.140 align:start position:0% guys and I'd listen to questions 01:20:17.140 --> 01:20:28.050 align:start position:0% guys and I'd listen to questions reactions<01:20:24.660> so<01:20:25.740> what<01:20:26.740> the<01:20:26.860> question<01:20:26.920> is<01:20:27.280> Miss<01:20:27.820> B 01:20:28.050 --> 01:20:28.060 align:start position:0% reactions so what the question is Miss B 01:20:28.060 --> 01:20:39.510 align:start position:0% reactions so what the question is Miss B the<01:20:28.540> earth<01:20:28.660> is<01:20:28.990> warming<01:20:30.360> but<01:20:38.520> tradition 01:20:39.510 --> 01:20:39.520 align:start position:0% the earth is warming but tradition 01:20:39.520 --> 01:20:42.150 align:start position:0% the earth is warming but tradition especially<01:20:40.030> we<01:20:40.450> have<01:20:40.570> different<01:20:41.230> ease<01:20:41.500> and 01:20:42.150 --> 01:20:42.160 align:start position:0% especially we have different ease and 01:20:42.160 --> 01:20:44.820 align:start position:0% especially we have different ease and different<01:20:42.790> states<01:20:43.060> and<01:20:43.330> how<01:20:43.720> this<01:20:44.050> even<01:20:44.590> deal 01:20:44.820 --> 01:20:44.830 align:start position:0% different states and how this even deal 01:20:44.830 --> 01:20:49.020 align:start position:0% different states and how this even deal with<01:20:44.980> that<01:20:45.250> all<01:20:46.290> already<01:20:47.290> destroying<01:20:48.070> more 01:20:49.020 --> 01:20:49.030 align:start position:0% with that all already destroying more 01:20:49.030 --> 01:20:50.750 align:start position:0% with that all already destroying more like 01:20:50.750 --> 01:20:50.760 align:start position:0% like 01:20:50.760 --> 01:20:55.850 align:start position:0% like change<01:20:51.150> them<01:20:51.540> or<01:20:51.870> comic-con<01:20:52.260> like<01:20:53.180> me<01:20:54.740> so<01:20:55.740> I'm 01:20:55.850 --> 01:20:55.860 align:start position:0% change them or comic-con like me so I'm 01:20:55.860 --> 01:21:00.470 align:start position:0% change them or comic-con like me so I'm not<01:20:56.040> sure<01:20:56.100> of<01:20:56.250> how<01:20:56.490> this<01:20:58.760> officially<01:20:59.760> looks 01:21:00.470 --> 01:21:00.480 align:start position:0% not sure of how this officially looks 01:21:00.480 --> 01:21:05.690 align:start position:0% not sure of how this officially looks like<01:21:02.720> yet<01:21:03.720> so<01:21:03.870> your<01:21:03.990> question<01:21:04.350> is<01:21:04.650> in<01:21:05.580> a 01:21:05.690 --> 01:21:05.700 align:start position:0% like yet so your question is in a 01:21:05.700 --> 01:21:07.250 align:start position:0% like yet so your question is in a Charlotte<01:21:06.030> model<01:21:06.390> with<01:21:06.780> cross<01:21:07.080> no 01:21:07.250 --> 01:21:07.260 align:start position:0% Charlotte model with cross no 01:21:07.260 --> 01:21:08.450 align:start position:0% Charlotte model with cross no transactions<01:21:07.860> you<01:21:08.040> end<01:21:08.190> up<01:21:08.250> getting<01:21:08.310> your 01:21:08.450 --> 01:21:08.460 align:start position:0% transactions you end up getting your 01:21:08.460 --> 01:21:10.190 align:start position:0% transactions you end up getting your state<01:21:08.730> fragmented<01:21:09.330> across<01:21:09.540> multiple<01:21:09.870> shards 01:21:10.190 --> 01:21:10.200 align:start position:0% state fragmented across multiple shards 01:21:10.200 --> 01:21:15.190 align:start position:0% state fragmented across multiple shards right<01:21:10.790> okay<01:21:11.790> and<01:21:12.030> how<01:21:12.300> do<01:21:12.360> you<01:21:12.420> deal<01:21:12.570> with<01:21:12.600> that 01:21:15.190 --> 01:21:15.200 align:start position:0% 01:21:15.200 --> 01:21:19.310 align:start position:0% especially<01:21:16.200> across<01:21:16.970> from<01:21:17.970> a<01:21:18.150> été<01:21:18.570> you're 01:21:19.310 --> 01:21:19.320 align:start position:0% especially across from a été you're 01:21:19.320 --> 01:21:26.570 align:start position:0% especially across from a été you're saying<01:21:23.930> so<01:21:24.930> first<01:21:25.170> we<01:21:25.440> have<01:21:25.560> what<01:21:25.740> if<01:21:26.310> I<01:21:26.460> had 01:21:26.570 --> 01:21:26.580 align:start position:0% saying so first we have what if I had 01:21:26.580 --> 01:21:28.910 align:start position:0% saying so first we have what if I had what<01:21:26.760> account<01:21:27.150> of<01:21:27.570> state<01:21:27.780> model<01:21:28.110> and<01:21:28.350> how<01:21:28.710> this 01:21:28.910 --> 01:21:28.920 align:start position:0% what account of state model and how this 01:21:28.920 --> 01:21:31.940 align:start position:0% what account of state model and how this edition<01:21:29.760> how<01:21:30.660> to<01:21:30.720> define<01:21:31.170> this<01:21:31.410> partition 01:21:31.940 --> 01:21:31.950 align:start position:0% edition how to define this partition 01:21:31.950 --> 01:21:35.600 align:start position:0% edition how to define this partition will<01:21:32.790> this<01:21:32.940> be<01:21:33.470> another<01:21:34.470> further<01:21:34.950> question<01:21:35.430> is 01:21:35.600 --> 01:21:35.610 align:start position:0% will this be another further question is 01:21:35.610 --> 01:21:38.660 align:start position:0% will this be another further question is is<01:21:35.880> possible<01:21:36.390> of<01:21:36.600> a<01:21:37.200> change<01:21:37.920> the<01:21:38.190> state<01:21:38.460> of<01:21:38.490> a 01:21:38.660 --> 01:21:38.670 align:start position:0% is possible of a change the state of a 01:21:38.670 --> 01:21:47.980 align:start position:0% is possible of a change the state of a mother<01:21:39.980> and<01:21:40.980> sister<01:21:41.730> so<01:21:41.970> and<01:21:42.270> because<01:21:42.690> this<01:21:43.020> to 01:21:47.980 --> 01:21:47.990 align:start position:0% 01:21:47.990 --> 01:21:50.780 align:start position:0% the<01:21:48.990> current<01:21:49.350> the<01:21:49.560> current<01:21:49.680> proposal<01:21:50.430> space 01:21:50.780 --> 01:21:50.790 align:start position:0% the current the current proposal space 01:21:50.790 --> 01:21:52.940 align:start position:0% the current the current proposal space didn't<01:21:51.210> again<01:21:51.540> things<01:21:52.170> are<01:21:52.290> all<01:21:52.680> under 01:21:52.940 --> 01:21:52.950 align:start position:0% didn't again things are all under 01:21:52.950 --> 01:21:57.290 align:start position:0% didn't again things are all under research<01:21:53.310> is<01:21:54.590> so<01:21:55.590> you<01:21:55.650> can<01:21:55.890> build<01:21:56.250> like<01:21:57.000> in 01:21:57.290 --> 01:21:57.300 align:start position:0% research is so you can build like in 01:21:57.300 --> 01:21:58.970 align:start position:0% research is so you can build like in building<01:21:57.840> you're<01:21:57.990> a<01:21:58.020> needy<01:21:58.200> you<01:21:58.650> can 01:21:58.970 --> 01:21:58.980 align:start position:0% building you're a needy you can 01:21:58.980 --> 01:22:00.980 align:start position:0% building you're a needy you can basically<01:21:59.730> have<01:22:00.060> standards<01:22:00.720> by<01:22:00.960> which 01:22:00.980 --> 01:22:00.990 align:start position:0% basically have standards by which 01:22:00.990 --> 01:22:05.810 align:start position:0% basically have standards by which another<01:22:02.990> you<01:22:03.990> know<01:22:04.110> some<01:22:04.890> probably<01:22:05.340> make<01:22:05.550> some 01:22:05.810 --> 01:22:05.820 align:start position:0% another you know some probably make some 01:22:05.820 --> 01:22:08.020 align:start position:0% another you know some probably make some type<01:22:05.970> of<01:22:06.000> message<01:22:06.240> loot<01:22:06.750> to<01:22:06.840> that<01:22:06.990> you<01:22:07.410> right 01:22:08.020 --> 01:22:08.030 align:start position:0% type of message loot to that you right 01:22:08.030 --> 01:22:11.750 align:start position:0% type of message loot to that you right but<01:22:09.030> it<01:22:09.440> again<01:22:10.440> this<01:22:10.590> would<01:22:11.220> be<01:22:11.280> like<01:22:11.580> an 01:22:11.750 --> 01:22:11.760 align:start position:0% but it again this would be like an 01:22:11.760 --> 01:22:13.820 align:start position:0% but it again this would be like an asynchronous<01:22:12.480> call<01:22:12.900> that<01:22:13.050> you<01:22:13.170> would<01:22:13.290> have<01:22:13.620> to 01:22:13.820 --> 01:22:13.830 align:start position:0% asynchronous call that you would have to 01:22:13.830 --> 01:22:16.100 align:start position:0% asynchronous call that you would have to make<01:22:14.460> it<01:22:14.520> to<01:22:14.730> Iggy<01:22:15.120> you're<01:22:15.570> not<01:22:15.720> guaranteed 01:22:16.100 --> 01:22:16.110 align:start position:0% make it to Iggy you're not guaranteed 01:22:16.110 --> 01:22:18.740 align:start position:0% make it to Iggy you're not guaranteed that<01:22:16.500> it<01:22:16.620> will<01:22:16.650> reach<01:22:17.460> that<01:22:17.700> separate<01:22:18.180> you<01:22:18.330> and 01:22:18.740 --> 01:22:18.750 align:start position:0% that it will reach that separate you and 01:22:18.750 --> 01:22:22.210 align:start position:0% that it will reach that separate you and you<01:22:19.380> know<01:22:19.730> until<01:22:20.730> maybe<01:22:21.090> a<01:22:21.210> couple<01:22:21.420> blocks<01:22:21.690> or 01:22:22.210 --> 01:22:22.220 align:start position:0% you know until maybe a couple blocks or 01:22:22.220 --> 01:22:25.310 align:start position:0% you know until maybe a couple blocks or whatever<01:22:23.220> else<01:22:23.970> is<01:22:24.150> there<01:22:24.360> but<01:22:24.720> I<01:22:24.780> think<01:22:25.080> that 01:22:25.310 --> 01:22:25.320 align:start position:0% whatever else is there but I think that 01:22:25.320 --> 01:22:30.060 align:start position:0% whatever else is there but I think that is<01:22:25.530> more<01:22:25.890> up<01:22:26.250> to<01:22:27.290> how<01:22:28.290> that<01:22:28.470> really<01:22:28.620> is<01:22:28.860> what 01:22:30.060 --> 01:22:30.070 align:start position:0% is more up to how that really is what 01:22:30.070 --> 01:22:33.780 align:start position:0% is more up to how that really is what is<01:22:30.730> how<01:22:31.119> it<01:22:31.360> allows<01:22:31.599> them<01:22:32.020> to<01:22:32.340> calm<01:22:33.340> it<01:22:33.460> to<01:22:33.670> it 01:22:33.780 --> 01:22:33.790 align:start position:0% is how it allows them to calm it to it 01:22:33.790 --> 01:22:35.640 align:start position:0% is how it allows them to calm it to it how<01:22:34.000> it<01:22:34.150> allows<01:22:34.360> them<01:22:34.659> to<01:22:34.840> integrate<01:22:35.230> into<01:22:35.440> it 01:22:35.640 --> 01:22:35.650 align:start position:0% how it allows them to integrate into it 01:22:35.650 --> 01:22:38.189 align:start position:0% how it allows them to integrate into it so<01:22:36.400> I<01:22:36.610> think<01:22:36.760> that's<01:22:37.449> that's<01:22:37.630> a<01:22:37.780> big<01:22:37.929> space 01:22:38.189 --> 01:22:38.199 align:start position:0% so I think that's that's a big space 01:22:38.199 --> 01:22:42.089 align:start position:0% so I think that's that's a big space that<01:22:38.230> needs<01:22:38.560> to<01:22:38.800> be<01:22:38.829> explored<01:22:40.170> within<01:22:41.170> 1e<01:22:41.590> the 01:22:42.089 --> 01:22:42.099 align:start position:0% that needs to be explored within 1e the 01:22:42.099 --> 01:22:44.459 align:start position:0% that needs to be explored within 1e the fragmentation<01:22:42.579> approach<01:22:43.239> if<01:22:43.540> we<01:22:43.570> get 01:22:44.459 --> 01:22:44.469 align:start position:0% fragmentation approach if we get 01:22:44.469 --> 01:22:46.620 align:start position:0% fragmentation approach if we get cautionary<01:22:45.070> calls<01:22:45.369> to<01:22:45.579> be<01:22:45.699> pretty<01:22:46.150> quick<01:22:46.270> then 01:22:46.620 --> 01:22:46.630 align:start position:0% cautionary calls to be pretty quick then 01:22:46.630 --> 01:22:48.720 align:start position:0% cautionary calls to be pretty quick then I<01:22:46.960> think<01:22:47.349> that<01:22:47.530> sort<01:22:48.099> of<01:22:48.159> solves<01:22:48.579> that<01:22:48.670> problem 01:22:48.720 --> 01:22:48.730 align:start position:0% I think that sort of solves that problem 01:22:48.730 --> 01:22:56.550 align:start position:0% I think that sort of solves that problem but 01:22:56.550 --> 01:22:56.560 align:start position:0% 01:22:56.560 --> 01:22:59.920 align:start position:0% yester<01:22:57.560> taking<01:22:58.400> a<01:22:58.460> step<01:22:58.700> back<01:22:58.940> here<01:22:59.360> have<01:22:59.900> a 01:22:59.920 --> 01:22:59.930 align:start position:0% yester taking a step back here have a 01:22:59.930 --> 01:23:03.700 align:start position:0% yester taking a step back here have a pragmatic<01:23:00.470> question<01:23:01.720> if<01:23:02.720> I<01:23:02.900> want<01:23:03.110> to<01:23:03.200> build<01:23:03.410> a 01:23:03.700 --> 01:23:03.710 align:start position:0% pragmatic question if I want to build a 01:23:03.710 --> 01:23:07.690 align:start position:0% pragmatic question if I want to build a needy<01:23:04.540> how<01:23:05.540> do<01:23:05.600> I<01:23:05.750> get<01:23:06.020> started<01:23:06.380> like<01:23:07.100> is<01:23:07.370> there 01:23:07.690 --> 01:23:07.700 align:start position:0% needy how do I get started like is there 01:23:07.700 --> 01:23:11.980 align:start position:0% needy how do I get started like is there a<01:23:08.470> document<01:23:09.470> epi<01:23:10.070> or<01:23:10.190> something<01:23:11.090> that<01:23:11.870> is 01:23:11.980 --> 01:23:11.990 align:start position:0% a document epi or something that is 01:23:11.990 --> 01:23:20.210 align:start position:0% a document epi or something that is available<01:23:14.920> how<01:23:15.920> do<01:23:15.980> I 01:23:20.210 --> 01:23:20.220 align:start position:0% 01:23:20.220 --> 01:23:23.540 align:start position:0% disabuse<01:23:21.180> discussion<01:23:21.810> you<01:23:21.960> may<01:23:22.140> not<01:23:22.680> would 01:23:23.540 --> 01:23:23.550 align:start position:0% disabuse discussion you may not would 01:23:23.550 --> 01:23:26.150 align:start position:0% disabuse discussion you may not would not<01:23:23.580> do<01:23:23.910> you<01:23:24.000> like<01:23:24.150> to<01:23:24.330> me<01:23:24.710> you<01:23:25.710> may<01:23:25.860> not<01:23:26.010> be 01:23:26.150 --> 01:23:26.160 align:start position:0% not do you like to me you may not be 01:23:26.160 --> 01:23:27.830 align:start position:0% not do you like to me you may not be allowed<01:23:26.370> to<01:23:26.400> do<01:23:26.670> because<01:23:27.060> there's<01:23:27.360> only<01:23:27.540> one 01:23:27.830 --> 01:23:27.840 align:start position:0% allowed to do because there's only one 01:23:27.840 --> 01:23:29.810 align:start position:0% allowed to do because there's only one in<01:23:27.930> Chinese<01:23:28.350> music<01:23:28.440> scallops<01:23:29.010> or<01:23:29.250> elements<01:23:29.760> of 01:23:29.810 --> 01:23:29.820 align:start position:0% in Chinese music scallops or elements of 01:23:29.820 --> 01:23:34.580 align:start position:0% in Chinese music scallops or elements of vegetation<01:23:30.770> but<01:23:32.360> subjected<01:23:33.360> to<01:23:33.510> will<01:23:34.350> mention 01:23:34.580 --> 01:23:34.590 align:start position:0% vegetation but subjected to will mention 01:23:34.590 --> 01:23:37.610 align:start position:0% vegetation but subjected to will mention scared<01:23:35.100> and<01:23:35.720> there's<01:23:36.720> an<01:23:36.900> entry<01:23:37.110> search<01:23:37.290> post 01:23:37.610 --> 01:23:37.620 align:start position:0% scared and there's an entry search post 01:23:37.620 --> 01:23:42.820 align:start position:0% scared and there's an entry search post which<01:23:38.190> explains<01:23:38.580> the<01:23:38.730> API<01:23:40.700> may<01:23:41.700> just<01:23:41.970> be<01:23:42.120> 32 01:23:42.820 --> 01:23:42.830 align:start position:0% which explains the API may just be 32 01:23:42.830 --> 01:23:47.930 align:start position:0% which explains the API may just be 32 aspect<01:23:43.830> with<01:23:44.640> this<01:23:44.910> kind<01:23:45.150> of<01:23:45.210> people<01:23:46.940> there's 01:23:47.930 --> 01:23:47.940 align:start position:0% aspect with this kind of people there's 01:23:47.940 --> 01:23:54.590 align:start position:0% aspect with this kind of people there's a<01:23:48.120> rabbit<01:23:48.450> except<01:23:48.840> mr.<01:23:49.230> Scout<01:23:50.130> is<01:23:52.940> it's<01:23:53.940> just<01:23:54.030> a 01:23:54.590 --> 01:23:54.600 align:start position:0% a rabbit except mr. Scout is it's just a 01:23:54.600 --> 01:23:57.860 align:start position:0% a rabbit except mr. Scout is it's just a prototype<01:23:55.020> we<01:23:55.650> have<01:23:55.860> four<01:23:56.310> V's<01:23:56.870> specifically 01:23:57.860 --> 01:23:57.870 align:start position:0% prototype we have four V's specifically 01:23:57.870 --> 01:24:00.620 align:start position:0% prototype we have four V's specifically and<01:23:58.830> in<01:23:58.950> his<01:23:59.130> examples<01:23:59.670> I<01:23:59.880> had<01:24:00.330> to<01:24:00.450> buy<01:24:00.570> the 01:24:00.620 --> 01:24:00.630 align:start position:0% and in his examples I had to buy the 01:24:00.630 --> 01:24:04.760 align:start position:0% and in his examples I had to buy the series<01:24:01.050> soon<01:24:01.230> as<01:24:01.350> the<01:24:01.500> best<01:24:01.680> source<01:24:01.890> to<01:24:02.100> do<01:24:03.770> so 01:24:04.760 --> 01:24:04.770 align:start position:0% series soon as the best source to do so 01:24:04.770 --> 01:24:07.070 align:start position:0% series soon as the best source to do so I<01:24:04.830> can<01:24:04.980> also<01:24:05.100> speak<01:24:05.430> from<01:24:05.610> a<01:24:05.760> perspective<01:24:06.630> like 01:24:07.070 --> 01:24:07.080 align:start position:0% I can also speak from a perspective like 01:24:07.080 --> 01:24:08.930 align:start position:0% I can also speak from a perspective like what's<01:24:07.260> gonna<01:24:07.380> happen<01:24:07.770> is<01:24:07.890> that<01:24:08.070> we<01:24:08.760> can 01:24:08.930 --> 01:24:08.940 align:start position:0% what's gonna happen is that we can 01:24:08.940 --> 01:24:13.940 align:start position:0% what's gonna happen is that we can change<01:24:09.120> it<01:24:11.060> deployed<01:24:12.060> first<01:24:12.420> and<01:24:12.800> around<01:24:13.800> that 01:24:13.940 --> 01:24:13.950 align:start position:0% change it deployed first and around that 01:24:13.950 --> 01:24:17.230 align:start position:0% change it deployed first and around that time<01:24:14.070> you<01:24:15.030> will<01:24:15.210> also<01:24:15.360> start<01:24:15.600> seeing<01:24:16.040> clients 01:24:17.230 --> 01:24:17.240 align:start position:0% time you will also start seeing clients 01:24:17.240 --> 01:24:21.020 align:start position:0% time you will also start seeing clients that<01:24:18.440> deliver<01:24:19.440> the<01:24:19.770> data<01:24:20.010> availability<01:24:20.550> right 01:24:21.020 --> 01:24:21.030 align:start position:0% that deliver the data availability right 01:24:21.030 --> 01:24:26.600 align:start position:0% that deliver the data availability right to<01:24:21.150> face<01:24:21.360> one<01:24:22.070> intestines<01:24:23.070> and<01:24:23.900> then<01:24:24.980> a<01:24:25.980> two 01:24:26.600 --> 01:24:26.610 align:start position:0% to face one intestines and then a two 01:24:26.610 --> 01:24:28.220 align:start position:0% to face one intestines and then a two legs<01:24:26.850> count<01:24:27.180> which<01:24:27.390> is<01:24:27.510> a<01:24:27.540> prototyping 01:24:28.220 --> 01:24:28.230 align:start position:0% legs count which is a prototyping 01:24:28.230 --> 01:24:31.880 align:start position:0% legs count which is a prototyping environment<01:24:29.930> basically<01:24:30.930> gives<01:24:31.470> you<01:24:31.620> access 01:24:31.880 --> 01:24:31.890 align:start position:0% environment basically gives you access 01:24:31.890 --> 01:24:35.240 align:start position:0% environment basically gives you access it<01:24:32.640> is<01:24:32.790> data<01:24:33.030> availability<01:24:33.510> and<01:24:34.020> a<01:24:34.980> little 01:24:35.240 --> 01:24:35.250 align:start position:0% it is data availability and a little 01:24:35.250 --> 01:24:38.200 align:start position:0% it is data availability and a little sandbox<01:24:35.520> in<01:24:36.480> which<01:24:36.750> you<01:24:36.900> can<01:24:37.050> play<01:24:37.260> with<01:24:37.500> aims 01:24:38.200 --> 01:24:38.210 align:start position:0% sandbox in which you can play with aims 01:24:38.210 --> 01:24:41.810 align:start position:0% sandbox in which you can play with aims right<01:24:39.240> so<01:24:39.990> that<01:24:40.590> is<01:24:40.740> kind<01:24:41.010> of<01:24:41.160> available<01:24:41.670> now 01:24:41.810 --> 01:24:41.820 align:start position:0% right so that is kind of available now 01:24:41.820 --> 01:24:43.580 align:start position:0% right so that is kind of available now to<01:24:42.300> start<01:24:42.510> playing<01:24:42.840> with<01:24:43.050> and<01:24:43.230> some<01:24:43.380> of<01:24:43.500> the 01:24:43.580 --> 01:24:43.590 align:start position:0% to start playing with and some of the 01:24:43.590 --> 01:24:46.460 align:start position:0% to start playing with and some of the primitives<01:24:44.130> are<01:24:44.370> being<01:24:44.640> developed<01:24:45.120> so<01:24:45.470> the 01:24:46.460 --> 01:24:46.470 align:start position:0% primitives are being developed so the 01:24:46.470 --> 01:24:48.560 align:start position:0% primitives are being developed so the idea<01:24:46.770> would<01:24:46.950> be<01:24:47.010> here<01:24:47.400> that<01:24:47.610> after<01:24:48.300> having 01:24:48.560 --> 01:24:48.570 align:start position:0% idea would be here that after having 01:24:48.570 --> 01:24:50.180 align:start position:0% idea would be here that after having heard<01:24:48.750> those<01:24:49.200> excellent<01:24:49.680> next 01:24:50.180 --> 01:24:50.190 align:start position:0% heard those excellent next 01:24:50.190 --> 01:24:52.610 align:start position:0% heard those excellent next the<01:24:50.610> new<01:24:50.760> toys<01:24:51.030> that<01:24:51.060> you'll<01:24:51.510> be<01:24:51.660> able<01:24:51.750> to<01:24:51.989> play 01:24:52.610 --> 01:24:52.620 align:start position:0% the new toys that you'll be able to play 01:24:52.620 --> 01:24:53.720 align:start position:0% the new toys that you'll be able to play with<01:24:52.890> life-threatening 01:24:53.720 --> 01:24:53.730 align:start position:0% with life-threatening 01:24:53.730 --> 01:24:56.900 align:start position:0% with life-threatening of<01:24:54.390> course<01:24:54.930> you<01:24:55.110> can<01:24:55.260> continue<01:24:55.739> to<01:24:55.890> work<01:24:56.010> like 01:24:56.900 --> 01:24:56.910 align:start position:0% of course you can continue to work like 01:24:56.910 --> 01:24:59.420 align:start position:0% of course you can continue to work like you<01:24:57.120> did<01:24:57.330> in<01:24:57.480> each<01:24:57.810> one<01:24:58.170> and<01:24:58.500> that<01:24:59.100> would<01:24:59.280> be 01:24:59.420 --> 01:24:59.430 align:start position:0% you did in each one and that would be 01:24:59.430 --> 01:25:01.250 align:start position:0% you did in each one and that would be like<01:24:59.610> you<01:24:59.760> buy<01:24:59.940> a<01:24:59.969> 16<01:25:00.270> core<01:25:00.660> criteria<01:25:00.810> just 01:25:01.250 --> 01:25:01.260 align:start position:0% like you buy a 16 core criteria just 01:25:01.260 --> 01:25:03.560 align:start position:0% like you buy a 16 core criteria just choose<01:25:01.680> one<01:25:01.920> of<01:25:01.949> them<01:25:02.219> right<01:25:02.400> but<01:25:02.640> then<01:25:02.850> you 01:25:03.560 --> 01:25:03.570 align:start position:0% choose one of them right but then you 01:25:03.570 --> 01:25:05.959 align:start position:0% choose one of them right but then you get<01:25:03.719> a<01:25:03.960> bunch<01:25:04.530> of<01:25:04.650> new<01:25:04.800> toys<01:25:04.830> and<01:25:05.370> the<01:25:05.489> idea<01:25:05.730> is 01:25:05.959 --> 01:25:05.969 align:start position:0% get a bunch of new toys and the idea is 01:25:05.969 --> 01:25:07.220 align:start position:0% get a bunch of new toys and the idea is then<01:25:06.239> that<01:25:06.270> you<01:25:06.570> can<01:25:06.719> start<01:25:06.960> experimenting 01:25:07.220 --> 01:25:07.230 align:start position:0% then that you can start experimenting 01:25:07.230 --> 01:25:09.650 align:start position:0% then that you can start experimenting with<01:25:07.620> developing<01:25:08.550> the<01:25:08.610> primitives<01:25:09.210> and 01:25:09.650 --> 01:25:09.660 align:start position:0% with developing the primitives and 01:25:09.660 --> 01:25:13.970 align:start position:0% with developing the primitives and without<01:25:10.080> that<01:25:10.320> end<01:25:10.530> user<01:25:11.390> developers<01:25:12.830> to<01:25:13.830> have 01:25:13.970 --> 01:25:13.980 align:start position:0% without that end user developers to have 01:25:13.980 --> 01:25:25.160 align:start position:0% without that end user developers to have a<01:25:14.040> nice<01:25:15.830> experience<01:25:23.390> so<01:25:24.390> would<01:25:24.840> make<01:25:25.110> a 01:25:25.160 --> 01:25:25.170 align:start position:0% a nice experience so would make a 01:25:25.170 --> 01:25:27.320 align:start position:0% a nice experience so would make a transaction<01:25:25.580> decide<01:25:26.580> that<01:25:26.699> I<01:25:26.820> have<01:25:27.090> to 01:25:27.320 --> 01:25:27.330 align:start position:0% transaction decide that I have to 01:25:27.330 --> 01:25:29.930 align:start position:0% transaction decide that I have to provide<01:25:27.900> the<01:25:28.380> men's<01:25:28.800> groups<01:25:29.130> right<01:25:29.610> for<01:25:29.820> this 01:25:29.930 --> 01:25:29.940 align:start position:0% provide the men's groups right for this 01:25:29.940 --> 01:25:33.229 align:start position:0% provide the men's groups right for this thing<01:25:30.440> so<01:25:31.440> but<01:25:31.739> how<01:25:32.010> do<01:25:32.070> I<01:25:32.250> know<01:25:32.460> what<01:25:33.000> the 01:25:33.229 --> 01:25:33.239 align:start position:0% thing so but how do I know what the 01:25:33.239 --> 01:25:46.990 align:start position:0% thing so but how do I know what the state<01:25:33.840> did<01:25:33.989> with<01:25:34.110> these<01:25:34.760> days<01:25:35.760> actually 01:25:46.990 --> 01:25:47.000 align:start position:0% 01:25:47.000 --> 01:25:52.160 align:start position:0% so<01:25:48.000> this<01:25:48.180> goes<01:25:48.330> back<01:25:48.390> to<01:25:48.540> the<01:25:49.310> API<01:25:50.310> and<01:25:51.170> what 01:25:52.160 --> 01:25:52.170 align:start position:0% so this goes back to the API and what 01:25:52.170 --> 01:25:56.660 align:start position:0% so this goes back to the API and what the<01:25:52.290> current<01:25:52.530> API<01:25:52.710> is<01:25:52.920> like<01:25:53.130> five<01:25:54.680> methods<01:25:55.680> for 01:25:56.660 --> 01:25:56.670 align:start position:0% the current API is like five methods for 01:25:56.670 --> 01:25:59.390 align:start position:0% the current API is like five methods for you<01:25:57.330> know<01:25:57.420> thanks<01:25:57.810> to<01:25:57.870> execution<01:25:58.770> you<01:25:59.280> know 01:25:59.390 --> 01:25:59.400 align:start position:0% you know thanks to execution you know 01:25:59.400 --> 01:26:04.760 align:start position:0% you know thanks to execution you know E's<01:26:00.199> one<01:26:01.199> of<01:26:01.290> them<01:26:01.410> is<01:26:02.150> get<01:26:03.150> get<01:26:04.140> current<01:26:04.530> get 01:26:04.760 --> 01:26:04.770 align:start position:0% E's one of them is get get current get 01:26:04.770 --> 01:26:08.180 align:start position:0% E's one of them is get get current get free<01:26:04.980> State<01:26:05.250> Road<01:26:05.719> so<01:26:06.719> you<01:26:07.620> know<01:26:07.710> this<01:26:07.949> is 01:26:08.180 --> 01:26:08.190 align:start position:0% free State Road so you know this is 01:26:08.190 --> 01:26:12.140 align:start position:0% free State Road so you know this is stored<01:26:08.969> on<01:26:09.120> the<01:26:09.360> on<01:26:10.290> the<01:26:10.380> shard<01:26:10.620> and<01:26:10.969> so<01:26:11.969> in<01:26:12.090> the 01:26:12.140 --> 01:26:12.150 align:start position:0% stored on the on the shard and so in the 01:26:12.150 --> 01:26:14.150 align:start position:0% stored on the on the shard and so in the wozmak<01:26:12.480> oh<01:26:12.570> you<01:26:12.750> Pig<01:26:13.020> get<01:26:13.500> the<01:26:13.590> priest<01:26:13.770> a<01:26:13.949> road 01:26:14.150 --> 01:26:14.160 align:start position:0% wozmak oh you Pig get the priest a road 01:26:14.160 --> 01:26:16.729 align:start position:0% wozmak oh you Pig get the priest a road and<01:26:14.760> then<01:26:15.330> the<01:26:15.750> other<01:26:15.900> one<01:26:16.050> is<01:26:16.080> return<01:26:16.530> across 01:26:16.729 --> 01:26:16.739 align:start position:0% and then the other one is return across 01:26:16.739 --> 01:26:18.439 align:start position:0% and then the other one is return across state<01:26:16.980> route<01:26:17.160> so<01:26:17.430> you<01:26:17.460> do<01:26:17.670> hydrologic<01:26:18.210> then 01:26:18.439 --> 01:26:18.449 align:start position:0% state route so you do hydrologic then 01:26:18.449 --> 01:26:21.110 align:start position:0% state route so you do hydrologic then you<01:26:19.050> return<01:26:19.320> the<01:26:19.469> new<01:26:19.560> post<01:26:19.800> a<01:26:20.010> true<01:26:20.190> the<01:26:20.760> next 01:26:21.110 --> 01:26:21.120 align:start position:0% you return the new post a true the next 01:26:21.120 --> 01:26:23.150 align:start position:0% you return the new post a true the next transaction<01:26:21.449> when<01:26:21.930> it<01:26:22.020> calls<01:26:22.170> yet<01:26:22.830> the<01:26:22.949> priest 01:26:23.150 --> 01:26:23.160 align:start position:0% transaction when it calls yet the priest 01:26:23.160 --> 01:26:27.170 align:start position:0% transaction when it calls yet the priest a<01:26:23.310> road<01:26:23.550> will<01:26:24.300> get<01:26:24.449> that<01:26:24.660> new<01:26:25.580> one<01:26:26.580> that<01:26:26.640> was 01:26:27.170 --> 01:26:27.180 align:start position:0% a road will get that new one that was 01:26:27.180 --> 01:26:29.840 align:start position:0% a road will get that new one that was from<01:26:27.420> the<01:26:27.600> previous<01:26:27.960> transaction<01:26:28.670> but<01:26:29.670> what's 01:26:29.840 --> 01:26:29.850 align:start position:0% from the previous transaction but what's 01:26:29.850 --> 01:26:31.910 align:start position:0% from the previous transaction but what's the<01:26:29.940> question<01:26:30.090> within<01:26:30.570> a<01:26:30.690> II<01:26:30.960> or<01:26:31.440> from<01:26:31.740> that 01:26:31.910 --> 01:26:31.920 align:start position:0% the question within a II or from that 01:26:31.920 --> 01:26:37.280 align:start position:0% the question within a II or from that site<01:26:35.090> but<01:26:36.090> Matt<01:26:36.270> it's<01:26:36.450> not<01:26:36.480> exactly<01:26:36.930> what<01:26:37.110> the 01:26:37.280 --> 01:26:37.290 align:start position:0% site but Matt it's not exactly what the 01:26:37.290 --> 01:26:40.600 align:start position:0% site but Matt it's not exactly what the actual<01:26:37.860> execution<01:26:38.430> of<01:26:38.520> each<01:26:38.700> yeah<01:26:38.940> so<01:26:39.300> this<01:26:39.960> is 01:26:40.600 --> 01:26:40.610 align:start position:0% actual execution of each yeah so this is 01:26:40.610 --> 01:26:44.780 align:start position:0% actual execution of each yeah so this is so<01:26:41.610> getting<01:26:41.910> the<01:26:42.000> state<01:26:42.240> group<01:26:42.500> you<01:26:43.500> can<01:26:43.790> but 01:26:44.780 --> 01:26:44.790 align:start position:0% so getting the state group you can but 01:26:44.790 --> 01:26:46.820 align:start position:0% so getting the state group you can but that's<01:26:45.000> available<01:26:45.300> from<01:26:45.870> the<01:26:46.440> system<01:26:46.710> that 01:26:46.820 --> 01:26:46.830 align:start position:0% that's available from the system that 01:26:46.830 --> 01:26:49.700 align:start position:0% that's available from the system that youth<01:26:46.950> to<01:26:47.190> provides<01:26:47.700> but<01:26:48.320> if<01:26:49.320> you're<01:26:49.470> wanting 01:26:49.700 --> 01:26:49.710 align:start position:0% youth to provides but if you're wanting 01:26:49.710 --> 01:26:52.010 align:start position:0% youth to provides but if you're wanting to<01:26:49.740> get<01:26:49.860> the<01:26:49.980> state<01:26:50.220> and<01:26:50.610> you<01:26:51.150> need<01:26:51.660> the<01:26:51.780> state 01:26:52.010 --> 01:26:52.020 align:start position:0% to get the state and you need the state 01:26:52.020 --> 01:26:54.190 align:start position:0% to get the state and you need the state to<01:26:52.050> in<01:26:52.890> order<01:26:53.070> to<01:26:53.190> generate<01:26:53.370> a<01:26:53.580> multi<01:26:53.880> booth 01:26:54.190 --> 01:26:54.200 align:start position:0% to in order to generate a multi booth 01:26:54.200 --> 01:26:56.750 align:start position:0% to in order to generate a multi booth this<01:26:55.200> introduces<01:26:55.800> it<01:26:55.980> basically<01:26:56.490> there's<01:26:56.730> a 01:26:56.750 --> 01:26:56.760 align:start position:0% this introduces it basically there's a 01:26:56.760 --> 01:26:59.810 align:start position:0% this introduces it basically there's a new<01:26:56.880> actor<01:26:57.390> in<01:26:57.870> their<01:26:58.080> system<01:26:58.520> these<01:26:59.520> would<01:26:59.670> be 01:26:59.810 --> 01:26:59.820 align:start position:0% new actor in their system these would be 01:26:59.820 --> 01:27:03.350 align:start position:0% new actor in their system these would be what<01:27:00.150> we<01:27:00.270> call<01:27:00.300> state<01:27:00.810> providers<01:27:01.580> and<01:27:02.580> there's 01:27:03.350 --> 01:27:03.360 align:start position:0% what we call state providers and there's 01:27:03.360 --> 01:27:05.900 align:start position:0% what we call state providers and there's you<01:27:04.350> know<01:27:04.380> right<01:27:04.680> now<01:27:04.800> three<01:27:05.610> different 01:27:05.900 --> 01:27:05.910 align:start position:0% you know right now three different 01:27:05.910 --> 01:27:08.840 align:start position:0% you know right now three different proposals<01:27:06.620> one<01:27:07.620> of<01:27:07.740> them<01:27:07.890> makes<01:27:08.370> a<01:27:08.610> state 01:27:08.840 --> 01:27:08.850 align:start position:0% proposals one of them makes a state 01:27:08.850 --> 01:27:11.870 align:start position:0% proposals one of them makes a state provider<01:27:09.180> is<01:27:09.410> even<01:27:10.410> more<01:27:10.650> essential<01:27:10.920> what<01:27:11.760> we 01:27:11.870 --> 01:27:11.880 align:start position:0% provider is even more essential what we 01:27:11.880 --> 01:27:14.090 align:start position:0% provider is even more essential what we call<01:27:12.090> real<01:27:12.300> layers<01:27:12.480> one<01:27:13.470> of<01:27:13.560> them<01:27:13.740> kind<01:27:14.070> of 01:27:14.090 --> 01:27:14.100 align:start position:0% call real layers one of them kind of 01:27:14.100 --> 01:27:16.160 align:start position:0% call real layers one of them kind of removes<01:27:14.550> the<01:27:14.790> relayer<01:27:15.120> aspect<01:27:15.720> and<01:27:15.900> we<01:27:15.960> just 01:27:16.160 --> 01:27:16.170 align:start position:0% removes the relayer aspect and we just 01:27:16.170 --> 01:27:18.230 align:start position:0% removes the relayer aspect and we just need<01:27:16.350> you<01:27:16.650> know<01:27:16.740> someone<01:27:17.460> will<01:27:17.670> provide<01:27:17.910> state 01:27:18.230 --> 01:27:18.240 align:start position:0% need you know someone will provide state 01:27:18.240 --> 01:27:20.120 align:start position:0% need you know someone will provide state to<01:27:18.420> you<01:27:18.510> and<01:27:19.200> so<01:27:19.320> this<01:27:19.440> is<01:27:19.560> an<01:27:19.650> open<01:27:19.860> area<01:27:20.070> of 01:27:20.120 --> 01:27:20.130 align:start position:0% to you and so this is an open area of 01:27:20.130 --> 01:27:22.430 align:start position:0% to you and so this is an open area of research<01:27:20.430> I<01:27:20.790> think<01:27:21.030> we're<01:27:21.360> all<01:27:21.570> going<01:27:22.260> to<01:27:22.350> be 01:27:22.430 --> 01:27:22.440 align:start position:0% research I think we're all going to be 01:27:22.440 --> 01:27:24.680 align:start position:0% research I think we're all going to be looking<01:27:22.740> at<01:27:22.860> this<01:27:23.070> start<01:27:23.880> getting<01:27:24.240> into<01:27:24.540> this 01:27:24.680 --> 01:27:24.690 align:start position:0% looking at this start getting into this 01:27:24.690 --> 01:27:27.470 align:start position:0% looking at this start getting into this after<01:27:25.170> DEFCON<01:27:26.120> collaboratively<01:27:27.120> and 01:27:27.470 --> 01:27:27.480 align:start position:0% after DEFCON collaboratively and 01:27:27.480 --> 01:27:31.670 align:start position:0% after DEFCON collaboratively and hopefully<01:27:28.470> we<01:27:28.590> will<01:27:28.620> be<01:27:28.770> writing<01:27:29.340> some<01:27:30.680> good 01:27:31.670 --> 01:27:31.680 align:start position:0% hopefully we will be writing some good 01:27:31.680 --> 01:27:34.990 align:start position:0% hopefully we will be writing some good research<01:27:32.100> posts<01:27:32.520> on<01:27:32.610> this<01:27:32.900> in<01:27:33.900> general<01:27:34.620> though 01:27:34.990 --> 01:27:35.000 align:start position:0% research posts on this in general though 01:27:35.000 --> 01:27:37.220 align:start position:0% research posts on this in general though from<01:27:36.000> the<01:27:36.180> simplest<01:27:36.570> model<01:27:36.750> there's<01:27:37.110> this 01:27:37.220 --> 01:27:37.230 align:start position:0% from the simplest model there's this 01:27:37.230 --> 01:27:40.300 align:start position:0% from the simplest model there's this idea<01:27:37.590> that<01:27:37.890> you<01:27:38.190> could<01:27:39.090> pay<01:27:39.420> to<01:27:39.480> access<01:27:39.750> state 01:27:40.300 --> 01:27:40.310 align:start position:0% idea that you could pay to access state 01:27:40.310 --> 01:27:42.800 align:start position:0% idea that you could pay to access state so<01:27:41.310> maybe<01:27:41.580> there<01:27:41.790> are<01:27:41.850> actors<01:27:42.180> in<01:27:42.360> the<01:27:42.450> system 01:27:42.800 --> 01:27:42.810 align:start position:0% so maybe there are actors in the system 01:27:42.810 --> 01:27:46.040 align:start position:0% so maybe there are actors in the system that<01:27:42.920> that<01:27:43.920> would<01:27:44.310> you<01:27:44.640> know<01:27:44.760> requires<01:27:45.600> some 01:27:46.040 --> 01:27:46.050 align:start position:0% that that would you know requires some 01:27:46.050 --> 01:27:49.430 align:start position:0% that that would you know requires some type<01:27:46.230> of<01:27:46.260> you<01:27:46.860> know<01:27:46.890> micro<01:27:47.820> transaction<01:27:48.510> in 01:27:49.430 --> 01:27:49.440 align:start position:0% type of you know micro transaction in 01:27:49.440 --> 01:27:52.310 align:start position:0% type of you know micro transaction in order<01:27:49.620> to<01:27:49.920> write<01:27:50.460> to<01:27:51.240> give<01:27:51.660> you<01:27:51.780> witness<01:27:52.140> that 01:27:52.310 --> 01:27:52.320 align:start position:0% order to write to give you witness that 01:27:52.320 --> 01:27:54.680 align:start position:0% order to write to give you witness that would<01:27:52.470> end<01:27:52.590> up<01:27:52.650> writing<01:27:53.040> state<01:27:53.670> that<01:27:54.510> gets 01:27:54.680 --> 01:27:54.690 align:start position:0% would end up writing state that gets 01:27:54.690 --> 01:27:57.050 align:start position:0% would end up writing state that gets submitted<01:27:55.260> as<01:27:55.500> part<01:27:55.560> of<01:27:55.770> a<01:27:55.860> transaction<01:27:56.250> maybe 01:27:57.050 --> 01:27:57.060 align:start position:0% submitted as part of a transaction maybe 01:27:57.060 --> 01:28:00.950 align:start position:0% submitted as part of a transaction maybe they<01:27:57.240> give<01:27:57.420> you<01:27:57.650> state<01:27:58.650> for<01:27:58.860> free<01:27:59.070> to<01:27:59.220> read<01:27:59.960> you 01:28:00.950 --> 01:28:00.960 align:start position:0% they give you state for free to read you 01:28:00.960 --> 01:28:02.840 align:start position:0% they give you state for free to read you know<01:28:01.080> then<01:28:01.710> in<01:28:02.070> order<01:28:02.220> to<01:28:02.370> kind<01:28:02.550> of<01:28:02.580> build<01:28:02.790> that 01:28:02.840 --> 01:28:02.850 align:start position:0% know then in order to kind of build that 01:28:02.850 --> 01:28:05.630 align:start position:0% know then in order to kind of build that model<01:28:03.270> we<01:28:04.140> already<01:28:04.380> have<01:28:04.560> like<01:28:04.920> generally 01:28:05.630 --> 01:28:05.640 align:start position:0% model we already have like generally 01:28:05.640 --> 01:28:07.880 align:start position:0% model we already have like generally altruistic<01:28:06.180> actors<01:28:06.930> right<01:28:07.230> now<01:28:07.260> he<01:28:07.410> needs<01:28:07.500> one 01:28:07.880 --> 01:28:07.890 align:start position:0% altruistic actors right now he needs one 01:28:07.890 --> 01:28:09.860 align:start position:0% altruistic actors right now he needs one I<01:28:08.130> think<01:28:08.760> in<01:28:08.880> general<01:28:09.030> the<01:28:09.300> idea<01:28:09.570> is<01:28:09.630> to 01:28:09.860 --> 01:28:09.870 align:start position:0% I think in general the idea is to 01:28:09.870 --> 01:28:12.050 align:start position:0% I think in general the idea is to eventually<01:28:10.350> go<01:28:11.190> away<01:28:11.220> from<01:28:11.580> the<01:28:11.700> altruistic 01:28:12.050 --> 01:28:12.060 align:start position:0% eventually go away from the altruistic 01:28:12.060 --> 01:28:15.500 align:start position:0% eventually go away from the altruistic model<01:28:13.070> you<01:28:14.070> know<01:28:14.190> these<01:28:14.640> one<01:28:14.880> is<01:28:15.060> generally 01:28:15.500 --> 01:28:15.510 align:start position:0% model you know these one is generally 01:28:15.510 --> 01:28:20.299 align:start position:0% model you know these one is generally supported<01:28:15.960> by<01:28:16.080> a<01:28:16.110> system<01:28:16.740> of<01:28:16.980> altruism<01:28:17.400> right 01:28:20.299 --> 01:28:20.309 align:start position:0% 01:28:20.309 --> 01:28:24.379 align:start position:0% I<01:28:20.340> think<01:28:21.150> there<01:28:21.329> is<01:28:21.360> some<01:28:22.369> ins<01:28:23.369> in<01:28:23.969> the<01:28:24.179> data 01:28:24.379 --> 01:28:24.389 align:start position:0% I think there is some ins in the data 01:28:24.389 --> 01:28:28.700 align:start position:0% I think there is some ins in the data flow<01:28:24.510> as<01:28:24.780> well<01:28:25.400> so<01:28:26.869> the<01:28:27.869> way<01:28:28.050> the<01:28:28.230> system<01:28:28.260> is 01:28:28.700 --> 01:28:28.710 align:start position:0% flow as well so the way the system is 01:28:28.710 --> 01:28:32.510 align:start position:0% flow as well so the way the system is built<01:28:29.179> is<01:28:30.179> that<01:28:30.659> you<01:28:30.900> go<01:28:31.050> from<01:28:31.230> a<01:28:31.380> pre<01:28:31.650> state<01:28:31.920> we 01:28:32.510 --> 01:28:32.520 align:start position:0% built is that you go from a pre state we 01:28:32.520 --> 01:28:34.220 align:start position:0% built is that you go from a pre state we execute<01:28:32.940> something<01:28:33.179> into<01:28:33.570> a<01:28:33.599> poor<01:28:33.809> state<01:28:34.020> and 01:28:34.220 --> 01:28:34.230 align:start position:0% execute something into a poor state and 01:28:34.230 --> 01:28:36.649 align:start position:0% execute something into a poor state and that<01:28:34.619> already<01:28:35.010> tells<01:28:35.250> you<01:28:35.520> them<01:28:35.699> from<01:28:36.539> the 01:28:36.649 --> 01:28:36.659 align:start position:0% that already tells you them from the 01:28:36.659 --> 01:28:39.169 align:start position:0% that already tells you them from the perspective<01:28:37.199> of<01:28:37.320> the<01:28:37.469> you<01:28:37.619> to<01:28:37.860> consensus<01:28:38.520> you 01:28:39.169 --> 01:28:39.179 align:start position:0% perspective of the you to consensus you 01:28:39.179 --> 01:28:40.879 align:start position:0% perspective of the you to consensus you have<01:28:39.300> to<01:28:39.449> provide<01:28:39.750> that<01:28:39.809> pre<01:28:40.199> state<01:28:40.469> to<01:28:40.770> the 01:28:40.879 --> 01:28:40.889 align:start position:0% have to provide that pre state to the 01:28:40.889 --> 01:28:43.580 align:start position:0% have to provide that pre state to the function<01:28:41.340> that<01:28:42.090> is<01:28:42.239> executing<01:28:42.869> and<01:28:43.079> then<01:28:43.260> need 01:28:43.580 --> 01:28:43.590 align:start position:0% function that is executing and then need 01:28:43.590 --> 01:28:47.600 align:start position:0% function that is executing and then need to<01:28:43.800> verify<01:28:44.039> sticky-up<01:28:44.670> is<01:28:45.289> correct<01:28:46.289> birth<01:28:46.739> or 01:28:47.600 --> 01:28:47.610 align:start position:0% to verify sticky-up is correct birth or 01:28:47.610 --> 01:28:51.350 align:start position:0% to verify sticky-up is correct birth or that<01:28:47.789> calculation<01:28:48.300> right<01:28:48.650> so<01:28:50.030> something<01:28:51.030> has 01:28:51.350 --> 01:28:51.360 align:start position:0% that calculation right so something has 01:28:51.360 --> 01:28:52.819 align:start position:0% that calculation right so something has to<01:28:51.510> provide<01:28:51.780> that<01:28:51.989> state<01:28:52.260> and<01:28:52.440> what<01:28:52.650> that 01:28:52.819 --> 01:28:52.829 align:start position:0% to provide that state and what that 01:28:52.829 --> 01:28:55.220 align:start position:0% to provide that state and what that something<01:28:53.039> is<01:28:53.599> up<01:28:54.599> for<01:28:54.929> debate 01:28:55.220 --> 01:28:55.230 align:start position:0% something is up for debate 01:28:55.230 --> 01:28:57.439 align:start position:0% something is up for debate you<01:28:55.949> may<01:28:56.159> somebody<01:28:56.579> to<01:28:56.760> keep<01:28:56.969> track<01:28:57.210> of<01:28:57.360> that 01:28:57.439 --> 01:28:57.449 align:start position:0% you may somebody to keep track of that 01:28:57.449 --> 01:29:00.919 align:start position:0% you may somebody to keep track of that yourself<01:28:58.940> you'd<01:28:59.940> have<01:29:00.090> to<01:29:00.210> have<01:29:00.300> nice 01:29:00.919 --> 01:29:00.929 align:start position:0% yourself you'd have to have nice 01:29:00.929 --> 01:29:05.089 align:start position:0% yourself you'd have to have nice configure<01:29:01.469> for<01:29:01.650> that<01:29:02.659> will<01:29:03.659> this<01:29:03.780> be<01:29:04.099> provided 01:29:05.089 --> 01:29:05.099 align:start position:0% configure for that will this be provided 01:29:05.099 --> 01:29:07.450 align:start position:0% configure for that will this be provided by<01:29:05.250> a<01:29:05.280> service<01:29:05.730> network<01:29:06.239> of<01:29:06.389> some<01:29:06.539> sort 01:29:07.450 --> 01:29:07.460 align:start position:0% by a service network of some sort 01:29:07.460 --> 01:29:12.049 align:start position:0% by a service network of some sort excellent<01:29:08.460> questions<01:29:10.159> I'm<01:29:11.159> destroying<01:29:11.880> one 01:29:12.049 --> 01:29:12.059 align:start position:0% excellent questions I'm destroying one 01:29:12.059 --> 01:29:14.859 align:start position:0% excellent questions I'm destroying one stage<01:29:12.420> one<01:29:13.199> of<01:29:13.289> the<01:29:13.380> possible<01:29:13.829> ramifications 01:29:14.859 --> 01:29:14.869 align:start position:0% stage one of the possible ramifications 01:29:14.869 --> 01:29:17.450 align:start position:0% stage one of the possible ramifications our<01:29:15.869> experience<01:29:16.440> with<01:29:16.619> things<01:29:16.710> like<01:29:17.159> a<01:29:17.219> sec 01:29:17.450 --> 01:29:17.460 align:start position:0% our experience with things like a sec 01:29:17.460 --> 01:29:17.989 align:start position:0% our experience with things like a sec one<01:29:17.699> sec 01:29:17.989 --> 01:29:17.999 align:start position:0% one sec 01:29:17.999 --> 01:29:26.179 align:start position:0% one sec you<01:29:18.389> have<01:29:18.869> to<01:29:19.019> be<01:29:19.110> aware 01:29:26.179 --> 01:29:26.189 align:start position:0% 01:29:26.189 --> 01:29:29.089 align:start position:0% I<01:29:26.219> mean<01:29:26.999> it<01:29:27.090> depends<01:29:27.389> what<01:29:27.659> your<01:29:28.439> your 01:29:29.089 --> 01:29:29.099 align:start position:0% I mean it depends what your your 01:29:29.099 --> 01:29:32.989 align:start position:0% I mean it depends what your your contracts<01:29:30.059> operate<01:29:30.929> with<01:29:31.139> right<01:29:31.800> so<01:29:32.099> you're 01:29:32.989 --> 01:29:32.999 align:start position:0% contracts operate with right so you're 01:29:32.999 --> 01:29:36.140 align:start position:0% contracts operate with right so you're working<01:29:33.479> with<01:29:33.949> engines<01:29:34.949> money<01:29:35.150> hopefully 01:29:36.140 --> 01:29:36.150 align:start position:0% working with engines money hopefully 01:29:36.150 --> 01:29:39.879 align:start position:0% working with engines money hopefully very<01:29:36.599> very<01:29:36.929> very<01:29:37.139> very<01:29:37.439> very<01:29:37.590> little<01:29:38.189> changes 01:29:39.879 --> 01:29:39.889 align:start position:0% very very very very very little changes 01:29:39.889 --> 01:29:42.350 align:start position:0% very very very very very little changes mostly<01:29:40.889> all<01:29:41.070> the<01:29:41.249> versatility<01:29:41.579> in<01:29:41.939> tooling 01:29:42.350 --> 01:29:42.360 align:start position:0% mostly all the versatility in tooling 01:29:42.360 --> 01:29:45.589 align:start position:0% mostly all the versatility in tooling behind<01:29:42.689> the<01:29:42.780> scenes<01:29:44.059> what<01:29:45.059> network<01:29:45.419> your 01:29:45.589 --> 01:29:45.599 align:start position:0% behind the scenes what network your 01:29:45.599 --> 01:29:48.890 align:start position:0% behind the scenes what network your wallets<01:29:45.900> connecting<01:29:46.380> to<01:29:46.639> you<01:29:47.639> know<01:29:47.789> but<01:29:48.599> the 01:29:48.890 --> 01:29:48.900 align:start position:0% wallets connecting to you know but the 01:29:48.900 --> 01:29:50.899 align:start position:0% wallets connecting to you know but the interface<01:29:49.139> very<01:29:49.949> few<01:29:50.280> wallet<01:29:50.610> shouldn't 01:29:50.899 --> 01:29:50.909 align:start position:0% interface very few wallet shouldn't 01:29:50.909 --> 01:29:52.459 align:start position:0% interface very few wallet shouldn't change<01:29:51.090> drastically<01:29:51.389> the<01:29:51.840> interface<01:29:52.260> between 01:29:52.459 --> 01:29:52.469 align:start position:0% change drastically the interface between 01:29:52.469 --> 01:29:54.500 align:start position:0% change drastically the interface between web<01:29:52.860> 3<01:29:53.159> Dodgers<01:29:53.519> ship<01:29:53.789> changed<01:29:54.179> drastically 01:29:54.500 --> 01:29:54.510 align:start position:0% web 3 Dodgers ship changed drastically 01:29:54.510 --> 01:29:57.140 align:start position:0% web 3 Dodgers ship changed drastically you're<01:29:54.989> still<01:29:55.289> using<01:29:55.949> solidity<01:29:56.519> you<01:29:56.969> might 01:29:57.140 --> 01:29:57.150 align:start position:0% you're still using solidity you might 01:29:57.150 --> 01:30:00.379 align:start position:0% you're still using solidity you might have<01:29:57.300> a<01:29:57.539> few<01:29:57.780> extra<01:29:58.079> tools<01:29:58.729> now<01:29:59.729> someone 01:30:00.379 --> 01:30:00.389 align:start position:0% have a few extra tools now someone 01:30:00.389 --> 01:30:03.439 align:start position:0% have a few extra tools now someone builds<01:30:00.749> you<01:30:01.079> know<01:30:01.199> do<01:30:01.949> the<01:30:02.280> count<01:30:02.519> model<01:30:02.820> EE<01:30:02.969> or 01:30:03.439 --> 01:30:03.449 align:start position:0% builds you know do the count model EE or 01:30:03.449 --> 01:30:05.689 align:start position:0% builds you know do the count model EE or something<01:30:04.289> else<01:30:04.469> that<01:30:04.829> has<01:30:05.280> some<01:30:05.579> new 01:30:05.689 --> 01:30:05.699 align:start position:0% something else that has some new 01:30:05.699 --> 01:30:07.699 align:start position:0% something else that has some new constructs<01:30:06.239> hopefully<01:30:07.019> there<01:30:07.199> are<01:30:07.260> standards 01:30:07.699 --> 01:30:07.709 align:start position:0% constructs hopefully there are standards 01:30:07.709 --> 01:30:12.379 align:start position:0% constructs hopefully there are standards that<01:30:07.829> are<01:30:08.219> built<01:30:08.489> that<01:30:09.169> kind<01:30:10.169> of<01:30:10.229> give<01:30:11.010> you<01:30:11.389> we 01:30:12.379 --> 01:30:12.389 align:start position:0% that are built that kind of give you we 01:30:12.389 --> 01:30:14.719 align:start position:0% that are built that kind of give you we continue<01:30:13.260> to<01:30:13.349> not<01:30:13.530> need<01:30:13.709> to<01:30:13.860> change<01:30:14.189> these<01:30:14.489> two 01:30:14.719 --> 01:30:14.729 align:start position:0% continue to not need to change these two 01:30:14.729 --> 01:30:18.140 align:start position:0% continue to not need to change these two lanes<01:30:14.939> drastic<01:30:15.510> that's<01:30:16.050> my<01:30:16.260> hope<01:30:16.860> I<01:30:17.280> think<01:30:17.880> we 01:30:18.140 --> 01:30:18.150 align:start position:0% lanes drastic that's my hope I think we 01:30:18.150 --> 01:30:24.960 align:start position:0% lanes drastic that's my hope I think we want<01:30:18.360> to<01:30:18.389> strive<01:30:18.659> for<01:30:18.689> that<01:30:19.309> yeah 01:30:24.960 --> 01:30:24.970 align:start position:0% 01:30:24.970 --> 01:30:27.040 align:start position:0% they've<01:30:25.970> been<01:30:26.120> suspect<01:30:26.330> an<01:30:26.630> earlier<01:30:26.900> question 01:30:27.040 --> 01:30:27.050 align:start position:0% they've been suspect an earlier question 01:30:27.050 --> 01:30:28.900 align:start position:0% they've been suspect an earlier question of<01:30:27.350> the<01:30:27.410> partitioned<01:30:27.950> with<01:30:28.190> how<01:30:28.670> to<01:30:28.730> be 01:30:28.900 --> 01:30:28.910 align:start position:0% of the partitioned with how to be 01:30:28.910 --> 01:30:31.750 align:start position:0% of the partitioned with how to be respect<01:30:29.420> to<01:30:29.660> maybe<01:30:30.230> speed<01:30:30.710> up<01:30:30.890> each<01:30:31.160> one<01:30:31.520> if 01:30:31.750 --> 01:30:31.760 align:start position:0% respect to maybe speed up each one if 01:30:31.760 --> 01:30:33.790 align:start position:0% respect to maybe speed up each one if they<01:30:31.880> assume<01:30:32.240> that<01:30:32.450> this<01:30:32.600> each<01:30:32.870> one<01:30:33.110> he<01:30:33.440> could 01:30:33.790 --> 01:30:33.800 align:start position:0% they assume that this each one he could 01:30:33.800 --> 01:30:35.500 align:start position:0% they assume that this each one he could have<01:30:33.920> had<01:30:34.070> bigger<01:30:34.250> the<01:30:34.370> same<01:30:34.550> triplets<01:30:35.000> s 01:30:35.500 --> 01:30:35.510 align:start position:0% have had bigger the same triplets s 01:30:35.510 --> 01:30:37.540 align:start position:0% have had bigger the same triplets s curtains<01:30:36.110> it's<01:30:36.530> your<01:30:36.770> one<01:30:36.920> point<01:30:37.070> over<01:30:37.280> giving 01:30:37.540 --> 01:30:37.550 align:start position:0% curtains it's your one point over giving 01:30:37.550 --> 01:30:39.970 align:start position:0% curtains it's your one point over giving your<01:30:37.910> level<01:30:38.180> higher<01:30:38.470> but<01:30:39.470> if<01:30:39.560> you<01:30:39.710> want<01:30:39.890> to 01:30:39.970 --> 01:30:39.980 align:start position:0% your level higher but if you want to 01:30:39.980 --> 01:31:00.580 align:start position:0% your level higher but if you want to significantly<01:30:40.610> improve<01:30:47.620> or<01:30:59.230> so<01:31:00.230> I<01:31:00.290> I 01:31:00.580 --> 01:31:00.590 align:start position:0% significantly improve or so I I 01:31:00.590 --> 01:31:02.800 align:start position:0% significantly improve or so I I generally<01:31:01.160> think<01:31:01.190> bringing<01:31:02.090> all<01:31:02.660> the 01:31:02.800 --> 01:31:02.810 align:start position:0% generally think bringing all the 01:31:02.810 --> 01:31:05.080 align:start position:0% generally think bringing all the contracts<01:31:03.290> that<01:31:03.380> exist<01:31:03.770> in<01:31:03.980> each<01:31:04.190> one<01:31:04.610> right 01:31:05.080 --> 01:31:05.090 align:start position:0% contracts that exist in each one right 01:31:05.090 --> 01:31:07.710 align:start position:0% contracts that exist in each one right now<01:31:05.300> when<01:31:05.690> you're<01:31:05.810> bigger<01:31:05.990> need<01:31:06.170> to<01:31:06.290> eat<01:31:06.440> to 01:31:07.710 --> 01:31:07.720 align:start position:0% now when you're bigger need to eat to 01:31:07.720 --> 01:31:10.510 align:start position:0% now when you're bigger need to eat to the<01:31:08.720> scalability<01:31:09.470> but<01:31:09.860> you<01:31:10.160> get<01:31:10.340> from<01:31:10.490> that 01:31:10.510 --> 01:31:10.520 align:start position:0% the scalability but you get from that 01:31:10.520 --> 01:31:13.240 align:start position:0% the scalability but you get from that won't<01:31:11.510> be<01:31:11.750> drastic<01:31:12.350> like<01:31:12.620> you're<01:31:12.860> still 01:31:13.240 --> 01:31:13.250 align:start position:0% won't be drastic like you're still 01:31:13.250 --> 01:31:16.780 align:start position:0% won't be drastic like you're still running<01:31:13.700> on<01:31:14.090> one<01:31:14.720> one<01:31:15.230> shard<01:31:15.790> because 01:31:16.780 --> 01:31:16.790 align:start position:0% running on one one shard because 01:31:16.790 --> 01:31:18.520 align:start position:0% running on one one shard because contracts<01:31:17.510> that<01:31:17.660> exist<01:31:17.960> are<01:31:18.080> immutable<01:31:18.260> and 01:31:18.520 --> 01:31:18.530 align:start position:0% contracts that exist are immutable and 01:31:18.530 --> 01:31:20.110 align:start position:0% contracts that exist are immutable and they're<01:31:18.620> not<01:31:18.710> showing<01:31:18.920> very<01:31:19.220> F<01:31:19.370> right<01:31:19.730> you 01:31:20.110 --> 01:31:20.120 align:start position:0% they're not showing very F right you 01:31:20.120 --> 01:31:21.610 align:start position:0% they're not showing very F right you can't<01:31:20.360> just<01:31:20.450> change<01:31:20.810> the<01:31:20.930> contract<01:31:21.350> to<01:31:21.500> make 01:31:21.610 --> 01:31:21.620 align:start position:0% can't just change the contract to make 01:31:21.620 --> 01:31:25.060 align:start position:0% can't just change the contract to make it<01:31:21.740> shareware<01:31:22.100> and<01:31:23.110> so<01:31:24.110> you<01:31:24.320> will<01:31:24.650> have<01:31:24.680> some 01:31:25.060 --> 01:31:25.070 align:start position:0% it shareware and so you will have some 01:31:25.070 --> 01:31:27.310 align:start position:0% it shareware and so you will have some speed<01:31:25.400> gains<01:31:25.610> from<01:31:25.820> through<01:31:26.090> mistake<01:31:26.480> and<01:31:26.810> the 01:31:27.310 --> 01:31:27.320 align:start position:0% speed gains from through mistake and the 01:31:27.320 --> 01:31:29.020 align:start position:0% speed gains from through mistake and the execution<01:31:27.860> time<01:31:28.100> that<01:31:28.400> you<01:31:28.550> know<01:31:28.670> we're 01:31:29.020 --> 01:31:29.030 align:start position:0% execution time that you know we're 01:31:29.030 --> 01:31:30.880 align:start position:0% execution time that you know we're shooting<01:31:29.300> for<01:31:29.480> I<01:31:30.230> think<01:31:30.620> where<01:31:30.770> the 01:31:30.880 --> 01:31:30.890 align:start position:0% shooting for I think where the 01:31:30.890 --> 01:31:34.360 align:start position:0% shooting for I think where the scalability<01:31:31.880> would<01:31:32.180> come<01:31:32.510> is<01:31:32.870> new<01:31:33.770> yz1 01:31:34.360 --> 01:31:34.370 align:start position:0% scalability would come is new yz1 01:31:34.370 --> 01:31:37.960 align:start position:0% scalability would come is new yz1 contracts<01:31:35.180> that<01:31:35.710> can<01:31:36.710> can<01:31:37.130> now<01:31:37.280> be<01:31:37.460> Sharda 01:31:37.960 --> 01:31:37.970 align:start position:0% contracts that can can now be Sharda 01:31:37.970 --> 01:31:40.150 align:start position:0% contracts that can can now be Sharda we're<01:31:38.120> certainly<01:31:38.780> needs<01:31:39.020> one<01:31:39.200> contracts<01:31:39.710> in<01:31:40.070> a 01:31:40.150 --> 01:31:40.160 align:start position:0% we're certainly needs one contracts in a 01:31:40.160 --> 01:31:43.270 align:start position:0% we're certainly needs one contracts in a face<01:31:40.340> of<01:31:40.490> old<01:31:40.730> ones<01:31:41.230> it<01:31:42.230> can<01:31:42.440> be<01:31:42.590> written<01:31:43.070> in 01:31:43.270 --> 01:31:43.280 align:start position:0% face of old ones it can be written in 01:31:43.280 --> 01:31:45.700 align:start position:0% face of old ones it can be written in this<01:31:43.460> approach<01:31:44.150> that<01:31:44.180> it<01:31:45.050> understands<01:31:45.530> that 01:31:45.700 --> 01:31:45.710 align:start position:0% this approach that it understands that 01:31:45.710 --> 01:31:47.560 align:start position:0% this approach that it understands that there<01:31:45.860> are<01:31:45.920> multiple<01:31:46.070> shards<01:31:46.490> so<01:31:46.700> maybe<01:31:47.330> a<01:31:47.420> lot 01:31:47.560 --> 01:31:47.570 align:start position:0% there are multiple shards so maybe a lot 01:31:47.570 --> 01:31:51.910 align:start position:0% there are multiple shards so maybe a lot of<01:31:47.690> gaps<01:31:48.250> are<01:31:49.250> ok<01:31:49.730> with<01:31:49.760> you<01:31:50.300> know<01:31:50.560> the<01:31:51.560> minor 01:31:51.910 --> 01:31:51.920 align:start position:0% of gaps are ok with you know the minor 01:31:51.920 --> 01:31:54.490 align:start position:0% of gaps are ok with you know the minor scalability<01:31:52.640> gains<01:31:52.850> by<01:31:53.510> moving<01:31:53.990> a<01:31:54.110> thorn<01:31:54.410> in 01:31:54.490 --> 01:31:54.500 align:start position:0% scalability gains by moving a thorn in 01:31:54.500 --> 01:31:56.530 align:start position:0% scalability gains by moving a thorn in to<01:31:54.590> you<01:31:54.740> two<01:31:55.010> but<01:31:55.250> now<01:31:55.880> they<01:31:56.150> want<01:31:56.270> to<01:31:56.420> take 01:31:56.530 --> 01:31:56.540 align:start position:0% to you two but now they want to take 01:31:56.540 --> 01:31:58.060 align:start position:0% to you two but now they want to take care<01:31:56.780> of<01:31:56.810> the<01:31:57.020> extra<01:31:57.290> tooling<01:31:57.620> so<01:31:57.770> they<01:31:57.890> might 01:31:58.060 --> 01:31:58.070 align:start position:0% care of the extra tooling so they might 01:31:58.070 --> 01:32:00.010 align:start position:0% care of the extra tooling so they might have<01:31:58.280> you<01:31:58.640> know<01:31:58.730> some<01:31:59.000> type<01:31:59.750> of<01:31:59.780> social 01:32:00.010 --> 01:32:00.020 align:start position:0% have you know some type of social 01:32:00.020 --> 01:32:02.470 align:start position:0% have you know some type of social consensus<01:32:00.650> to<01:32:00.920> move<01:32:00.950> to<01:32:01.400> in<01:32:01.460> contract<01:32:02.030> that 01:32:02.470 --> 01:32:02.480 align:start position:0% consensus to move to in contract that 01:32:02.480 --> 01:32:06.640 align:start position:0% consensus to move to in contract that now<01:32:03.230> utilizes<01:32:04.390> sharp<01:32:05.390> aware<01:32:05.900> specific<01:32:06.440> tools 01:32:06.640 --> 01:32:06.650 align:start position:0% now utilizes sharp aware specific tools 01:32:06.650 --> 01:32:08.149 align:start position:0% now utilizes sharp aware specific tools that<01:32:06.980> that's<01:32:07.250> my<01:32:07.370> general<01:32:07.580> time 01:32:08.149 --> 01:32:08.159 align:start position:0% that that's my general time 01:32:08.159 --> 01:32:10.010 align:start position:0% that that's my general time and<01:32:08.370> he<01:32:08.489> can<01:32:09.030> see<01:32:09.179> do<01:32:09.300> you<01:32:09.360> have<01:32:09.510> additional 01:32:10.010 --> 01:32:10.020 align:start position:0% and he can see do you have additional 01:32:10.020 --> 01:32:14.060 align:start position:0% and he can see do you have additional thoughts<01:32:11.870> right<01:32:12.870> so<01:32:13.080> moving<01:32:13.469> moving<01:32:13.860> you 01:32:14.060 --> 01:32:14.070 align:start position:0% thoughts right so moving moving you 01:32:14.070 --> 01:32:17.030 align:start position:0% thoughts right so moving moving you wanted<01:32:14.429> to<01:32:14.550> de<01:32:15.260> opens<01:32:16.260> up<01:32:16.440> a<01:32:16.620> number<01:32:16.949> of 01:32:17.030 --> 01:32:17.040 align:start position:0% wanted to de opens up a number of 01:32:17.040 --> 01:32:19.310 align:start position:0% wanted to de opens up a number of questions<01:32:17.219> like<01:32:17.639> what<01:32:18.000> do<01:32:18.179> you<01:32:18.270> change<01:32:19.080> what 01:32:19.310 --> 01:32:19.320 align:start position:0% questions like what do you change what 01:32:19.320 --> 01:32:20.899 align:start position:0% questions like what do you change what you<01:32:19.350> have<01:32:19.469> to<01:32:19.770> change<01:32:20.010> what<01:32:20.280> can<01:32:20.550> you<01:32:20.670> change 01:32:20.899 --> 01:32:20.909 align:start position:0% you have to change what can you change 01:32:20.909 --> 01:32:23.870 align:start position:0% you have to change what can you change there's<01:32:21.750> certain<01:32:21.989> things<01:32:22.020> like<01:32:22.320> a<01:32:22.620> knob<01:32:23.190> the 01:32:23.870 --> 01:32:23.880 align:start position:0% there's certain things like a knob the 01:32:23.880 --> 01:32:24.979 align:start position:0% there's certain things like a knob the difficulty<01:32:24.300> up<01:32:24.420> there<01:32:24.600> like<01:32:24.719> what<01:32:24.870> does<01:32:24.960> that 01:32:24.979 --> 01:32:24.989 align:start position:0% difficulty up there like what does that 01:32:24.989 --> 01:32:27.020 align:start position:0% difficulty up there like what does that mean<01:32:25.290> in<01:32:25.560> this<01:32:25.889> new<01:32:26.070> context<01:32:26.489> you<01:32:26.790> have<01:32:26.850> to 01:32:27.020 --> 01:32:27.030 align:start position:0% mean in this new context you have to 01:32:27.030 --> 01:32:28.910 align:start position:0% mean in this new context you have to define<01:32:27.270> those<01:32:27.510> those<01:32:27.840> things<01:32:28.050> those<01:32:28.739> other 01:32:28.910 --> 01:32:28.920 align:start position:0% define those those things those other 01:32:28.920 --> 01:32:30.410 align:start position:0% define those those things those other opportunities<01:32:29.520> potentially<01:32:29.670> migrate<01:32:30.330> from 01:32:30.410 --> 01:32:30.420 align:start position:0% opportunities potentially migrate from 01:32:30.420 --> 01:32:32.930 align:start position:0% opportunities potentially migrate from traditional<01:32:30.989> choose<01:32:31.650> a<01:32:31.679> binary<01:32:32.370> local<01:32:32.760> tree 01:32:32.930 --> 01:32:32.940 align:start position:0% traditional choose a binary local tree 01:32:32.940 --> 01:32:34.910 align:start position:0% traditional choose a binary local tree and<01:32:33.719> then<01:32:33.840> another<01:32:34.199> one<01:32:34.409> these<01:32:34.530> opportunities 01:32:34.910 --> 01:32:34.920 align:start position:0% and then another one these opportunities 01:32:34.920 --> 01:32:38.629 align:start position:0% and then another one these opportunities is<01:32:35.250> to<01:32:36.050> open<01:32:37.050> up<01:32:37.350> the<01:32:37.409> notion<01:32:37.860> of<01:32:37.980> char<01:32:38.460> because 01:32:38.629 --> 01:32:38.639 align:start position:0% is to open up the notion of char because 01:32:38.639 --> 01:32:40.250 align:start position:0% is to open up the notion of char because s/he<01:32:39.030> was<01:32:39.239> saying<01:32:39.480> so<01:32:39.659> you<01:32:39.719> could<01:32:40.020> you<01:32:40.139> could 01:32:40.250 --> 01:32:40.260 align:start position:0% s/he was saying so you could you could 01:32:40.260 --> 01:32:42.950 align:start position:0% s/he was saying so you could you could easily<01:32:40.350> just<01:32:40.530> deploy<01:32:40.889> it<01:32:41.010> on<01:32:41.150> one<01:32:42.150> shard<01:32:42.420> it 01:32:42.950 --> 01:32:42.960 align:start position:0% easily just deploy it on one shard it 01:32:42.960 --> 01:32:44.479 align:start position:0% easily just deploy it on one shard it doesn't<01:32:43.170> have<01:32:43.260> any<01:32:43.440> notion<01:32:43.560> of<01:32:43.739> charting<01:32:44.100> it 01:32:44.479 --> 01:32:44.489 align:start position:0% doesn't have any notion of charting it 01:32:44.489 --> 01:32:46.120 align:start position:0% doesn't have any notion of charting it now<01:32:44.639> exists<01:32:45.090> in 01:32:46.120 --> 01:32:46.130 align:start position:0% now exists in 01:32:46.130 --> 01:32:48.800 align:start position:0% now exists in eath<01:32:47.130> to<01:32:47.370> is<01:32:47.580> kind<01:32:47.820> of<01:32:47.850> a<01:32:47.940> signature<01:32:48.270> paradigm 01:32:48.800 --> 01:32:48.810 align:start position:0% eath to is kind of a signature paradigm 01:32:48.810 --> 01:32:51.320 align:start position:0% eath to is kind of a signature paradigm it<01:32:49.230> does<01:32:49.590> have<01:32:50.010> access<01:32:50.219> to<01:32:50.639> make<01:32:50.790> groups<01:32:51.090> about 01:32:51.320 --> 01:32:51.330 align:start position:0% it does have access to make groups about 01:32:51.330 --> 01:32:54.200 align:start position:0% it does have access to make groups about the<01:32:51.510> entire<01:32:51.920> data<01:32:52.920> layer<01:32:53.159> of<01:32:53.489> e<01:32:53.610> to<01:32:53.820> at<01:32:54.060> that 01:32:54.200 --> 01:32:54.210 align:start position:0% the entire data layer of e to at that 01:32:54.210 --> 01:32:56.689 align:start position:0% the entire data layer of e to at that point<01:32:54.480> so<01:32:55.139> you<01:32:55.199> could<01:32:55.440> could<01:32:56.040> get<01:32:56.489> a<01:32:56.520> lot<01:32:56.670> more 01:32:56.689 --> 01:32:56.699 align:start position:0% point so you could could get a lot more 01:32:56.699 --> 01:32:58.459 align:start position:0% point so you could could get a lot more scalability<01:32:57.270> of<01:32:57.300> some<01:32:57.929> of<01:32:57.989> these<01:32:58.050> layer<01:32:58.290> 2 01:32:58.459 --> 01:32:58.469 align:start position:0% scalability of some of these layer 2 01:32:58.469 --> 01:33:01.010 align:start position:0% scalability of some of these layer 2 schemes<01:32:58.739> that<01:32:59.520> were<01:32:59.639> discussed<01:32:59.909> earlier<01:33:00.270> but 01:33:01.010 --> 01:33:01.020 align:start position:0% schemes that were discussed earlier but 01:33:01.020 --> 01:33:03.860 align:start position:0% schemes that were discussed earlier but then<01:33:01.170> I<01:33:01.620> think<01:33:02.070> one<01:33:03.060> area<01:33:03.090> research<01:33:03.600> and<01:33:03.780> one 01:33:03.860 --> 01:33:03.870 align:start position:0% then I think one area research and one 01:33:03.870 --> 01:33:05.360 align:start position:0% then I think one area research and one thing<01:33:03.989> that<01:33:04.080> we'd<01:33:04.199> like<01:33:04.290> to<01:33:04.469> push<01:33:04.620> for<01:33:04.860> and<01:33:05.159> is 01:33:05.360 --> 01:33:05.370 align:start position:0% thing that we'd like to push for and is 01:33:05.370 --> 01:33:07.459 align:start position:0% thing that we'd like to push for and is to<01:33:05.730> open<01:33:06.060> up<01:33:06.179> the<01:33:06.510> Charter<01:33:06.929> paradigm<01:33:07.320> within 01:33:07.459 --> 01:33:07.469 align:start position:0% to open up the Charter paradigm within 01:33:07.469 --> 01:33:09.379 align:start position:0% to open up the Charter paradigm within eighth<01:33:07.679> one<01:33:07.889> and<01:33:08.159> as<01:33:08.250> he<01:33:08.370> said<01:33:08.580> existing 01:33:09.379 --> 01:33:09.389 align:start position:0% eighth one and as he said existing 01:33:09.389 --> 01:33:11.660 align:start position:0% eighth one and as he said existing condors<01:33:09.690> would<01:33:09.870> know<01:33:10.020> about<01:33:10.139> this<01:33:10.409> but<01:33:10.949> new 01:33:11.660 --> 01:33:11.670 align:start position:0% condors would know about this but new 01:33:11.670 --> 01:33:13.669 align:start position:0% condors would know about this but new ones<01:33:12.050> discovery 01:33:13.669 --> 01:33:13.679 align:start position:0% ones discovery 01:33:13.679 --> 01:33:16.879 align:start position:0% ones discovery still<01:33:14.639> definitely<01:33:15.239> up<01:33:15.480> for<01:33:15.510> debate<01:33:15.719> one<01:33:16.080> what 01:33:16.879 --> 01:33:16.889 align:start position:0% still definitely up for debate one what 01:33:16.889 --> 01:33:18.950 align:start position:0% still definitely up for debate one what would<01:33:17.639> change<01:33:17.969> during<01:33:18.389> that<01:33:18.630> migration 01:33:18.950 --> 01:33:18.960 align:start position:0% would change during that migration 01:33:18.960 --> 01:33:24.890 align:start position:0% would change during that migration process<01:33:19.440> with<01:33:19.560> anyone<01:33:20.010> that<01:33:23.900> other 01:33:24.890 --> 01:33:24.900 align:start position:0% process with anyone that other 01:33:24.900 --> 01:33:27.680 align:start position:0% process with anyone that other techniques<01:33:25.320> for<01:33:25.560> dealing<01:33:26.250> with<01:33:26.880> situations 01:33:27.680 --> 01:33:27.690 align:start position:0% techniques for dealing with situations 01:33:27.690 --> 01:33:28.750 align:start position:0% techniques for dealing with situations way 01:33:28.750 --> 01:33:28.760 align:start position:0% way 01:33:28.760 --> 01:33:32.049 align:start position:0% way provide<01:33:29.059> the<01:33:29.480> pre<01:33:29.780> data<01:33:30.230> that<01:33:31.130> data<01:33:31.340> changes 01:33:32.049 --> 01:33:32.059 align:start position:0% provide the pre data that data changes 01:33:32.059 --> 01:33:34.660 align:start position:0% provide the pre data that data changes before<01:33:32.269> your<01:33:32.599> transactions<01:33:33.260> need<01:33:33.440> mind<01:33:33.679> to 01:33:34.660 --> 01:33:34.670 align:start position:0% before your transactions need mind to 01:33:34.670 --> 01:33:37.779 align:start position:0% before your transactions need mind to say<01:33:34.849> I<01:33:34.880> went<01:33:35.030> to<01:33:35.119> send<01:33:35.420> your<01:33:35.539> transactions<01:33:36.789> my 01:33:37.779 --> 01:33:37.789 align:start position:0% say I went to send your transactions my 01:33:37.789 --> 01:33:41.740 align:start position:0% say I went to send your transactions my my<01:33:38.630> collection<01:33:39.380> isn't<01:33:40.070> mine<01:33:40.670> until<01:33:41.300> I<01:33:41.360> can't 01:33:41.740 --> 01:33:41.750 align:start position:0% my collection isn't mine until I can't 01:33:41.750 --> 01:33:43.720 align:start position:0% my collection isn't mine until I can't go<01:33:41.900> through<01:33:42.139> now<01:33:42.289> and<01:33:42.650> in<01:33:42.949> three<01:33:43.699> days 01:33:43.720 --> 01:33:43.730 align:start position:0% go through now and in three days 01:33:43.730 --> 01:33:45.669 align:start position:0% go through now and in three days immediate<01:33:44.449> profits<01:33:44.869> your<01:33:44.989> account<01:33:45.289> balance 01:33:45.669 --> 01:33:45.679 align:start position:0% immediate profits your account balance 01:33:45.679 --> 01:33:53.780 align:start position:0% immediate profits your account balance change<01:33:49.059> yeah 01:33:53.780 --> 01:33:53.790 align:start position:0% 01:33:53.790 --> 01:33:56.600 align:start position:0% yeah<01:33:54.330> that's<01:33:54.900> a<01:33:55.050> it's<01:33:55.350> actually<01:33:55.680> pretty<01:33:56.490> easy 01:33:56.600 --> 01:33:56.610 align:start position:0% yeah that's a it's actually pretty easy 01:33:56.610 --> 01:34:01.940 align:start position:0% yeah that's a it's actually pretty easy to<01:33:56.880> do<01:33:57.030> just<01:33:57.920> with<01:33:58.920> the<01:34:00.050> vertical<01:34:01.050> proof<01:34:01.620> a<01:34:01.800> tug 01:34:01.940 --> 01:34:01.950 align:start position:0% to do just with the vertical proof a tug 01:34:01.950 --> 01:34:04.460 align:start position:0% to do just with the vertical proof a tug up<01:34:02.100> to<01:34:02.250> Merkel<01:34:02.580> proofs<01:34:02.850> and<01:34:03.150> they<01:34:04.140> don't<01:34:04.320> know 01:34:04.460 --> 01:34:04.470 align:start position:0% up to Merkel proofs and they don't know 01:34:04.470 --> 01:34:05.990 align:start position:0% up to Merkel proofs and they don't know each<01:34:04.620> other<01:34:04.890> and<01:34:05.400> if<01:34:05.490> they<01:34:05.610> don't<01:34:05.760> know<01:34:05.880> about 01:34:05.990 --> 01:34:06.000 align:start position:0% each other and if they don't know about 01:34:06.000 --> 01:34:07.580 align:start position:0% each other and if they don't know about each<01:34:06.180> other<01:34:06.360> at<01:34:06.750> the<01:34:06.840> time<01:34:07.050> of<01:34:07.230> being 01:34:07.580 --> 01:34:07.590 align:start position:0% each other at the time of being 01:34:07.590 --> 01:34:11.030 align:start position:0% each other at the time of being submitted<01:34:07.950> and<01:34:08.310> then<01:34:09.030> one<01:34:09.990> transaction<01:34:10.410> gets 01:34:11.030 --> 01:34:11.040 align:start position:0% submitted and then one transaction gets 01:34:11.040 --> 01:34:13.820 align:start position:0% submitted and then one transaction gets processed<01:34:11.340> than<01:34:12.150> the<01:34:12.360> other<01:34:12.480> proof<01:34:12.810> as<01:34:13.110> is 01:34:13.820 --> 01:34:13.830 align:start position:0% processed than the other proof as is 01:34:13.830 --> 01:34:15.110 align:start position:0% processed than the other proof as is invalid<01:34:14.430> but<01:34:14.610> there's<01:34:14.790> already<01:34:14.910> the 01:34:15.110 --> 01:34:15.120 align:start position:0% invalid but there's already the 01:34:15.120 --> 01:34:17.270 align:start position:0% invalid but there's already the information<01:34:15.150> there<01:34:15.720> to<01:34:15.960> update<01:34:16.890> you<01:34:17.160> know 01:34:17.270 --> 01:34:17.280 align:start position:0% information there to update you know 01:34:17.280 --> 01:34:25.640 align:start position:0% information there to update you know refresh<01:34:17.640> the<01:34:17.790> proof<01:34:18.030> so<01:34:18.690> even<01:34:19.380> if<01:34:19.440> like<01:34:24.650> well 01:34:25.640 --> 01:34:25.650 align:start position:0% refresh the proof so even if like well 01:34:25.650 --> 01:34:28.430 align:start position:0% refresh the proof so even if like well if<01:34:26.550> it<01:34:26.760> several<01:34:27.030> days<01:34:27.210> you<01:34:27.540> would<01:34:27.780> need<01:34:27.960> you 01:34:28.430 --> 01:34:28.440 align:start position:0% if it several days you would need you 01:34:28.440 --> 01:34:30.440 align:start position:0% if it several days you would need you know<01:34:28.560> all<01:34:28.770> these<01:34:28.950> the<01:34:29.730> intermediate 01:34:30.440 --> 01:34:30.450 align:start position:0% know all these the intermediate 01:34:30.450 --> 01:34:32.360 align:start position:0% know all these the intermediate transactions<01:34:31.410> that<01:34:31.560> were<01:34:31.710> processed<01:34:32.160> in<01:34:32.280> the 01:34:32.360 --> 01:34:32.370 align:start position:0% transactions that were processed in the 01:34:32.370 --> 01:34:39.380 align:start position:0% transactions that were processed in the meantime<01:34:32.550> but<01:34:33.590> the<01:34:36.620> information<01:34:38.180> yeah<01:34:39.180> and 01:34:39.380 --> 01:34:39.390 align:start position:0% meantime but the information yeah and 01:34:39.390 --> 01:34:40.460 align:start position:0% meantime but the information yeah and that's<01:34:39.540> I<01:34:39.720> mean<01:34:39.900> that's<01:34:40.020> what<01:34:40.290> we've<01:34:40.440> been 01:34:40.460 --> 01:34:40.470 align:start position:0% that's I mean that's what we've been 01:34:40.470 --> 01:34:42.680 align:start position:0% that's I mean that's what we've been referring<01:34:40.890> to<01:34:41.010> as<01:34:41.100> maybe<01:34:41.430> stay<01:34:42.000> providers<01:34:42.480> or 01:34:42.680 --> 01:34:42.690 align:start position:0% referring to as maybe stay providers or 01:34:42.690 --> 01:34:44.690 align:start position:0% referring to as maybe stay providers or three<01:34:42.930> layers<01:34:43.170> and<01:34:43.320> that's<01:34:44.040> where<01:34:44.400> they<01:34:44.550> come 01:34:44.690 --> 01:34:44.700 align:start position:0% three layers and that's where they come 01:34:44.700 --> 01:34:48.080 align:start position:0% three layers and that's where they come in<01:34:44.850> not<01:34:45.090> as<01:34:45.270> a<01:34:45.300> day<01:34:45.510> of<01:34:45.570> oil<01:34:45.780> you<01:34:46.290> know<01:34:47.090> have 01:34:48.080 --> 01:34:48.090 align:start position:0% in not as a day of oil you know have 01:34:48.090 --> 01:34:50.570 align:start position:0% in not as a day of oil you know have this<01:34:48.240> role<01:34:48.450> of<01:34:48.480> like<01:34:48.870> updating<01:34:49.470> groups<01:34:50.220> and<01:34:50.460> so 01:34:50.570 --> 01:34:50.580 align:start position:0% this role of like updating groups and so 01:34:50.580 --> 01:34:56.050 align:start position:0% this role of like updating groups and so forth 01:34:56.050 --> 01:34:56.060 align:start position:0% 01:34:56.060 --> 01:34:59.470 align:start position:0% so<01:34:57.070> absolutely<01:34:58.070> to<01:34:58.370> the<01:34:58.490> smart<01:34:58.820> complaints 01:34:59.470 --> 01:34:59.480 align:start position:0% so absolutely to the smart complaints 01:34:59.480 --> 01:35:05.200 align:start position:0% so absolutely to the smart complaints associated<01:35:00.140> with<01:35:00.620> a<01:35:00.770> specific<01:35:01.040> team<01:35:03.250> or<01:35:04.250> can 01:35:05.200 --> 01:35:05.210 align:start position:0% associated with a specific team or can 01:35:05.210 --> 01:35:16.400 align:start position:0% associated with a specific team or can be<01:35:05.390> running<01:35:05.630> allergies 01:35:16.400 --> 01:35:16.410 align:start position:0% 01:35:16.410 --> 01:35:18.960 align:start position:0% in<01:35:17.410> all<01:35:17.620> cases<01:35:17.890> you<01:35:18.100> probably<01:35:18.400> have<01:35:18.730> like<01:35:18.940> a 01:35:18.960 --> 01:35:18.970 align:start position:0% in all cases you probably have like a 01:35:18.970 --> 01:35:20.760 align:start position:0% in all cases you probably have like a notion<01:35:19.660> of<01:35:19.780> a<01:35:20.020> smart<01:35:20.260> contract<01:35:20.410> being 01:35:20.760 --> 01:35:20.770 align:start position:0% notion of a smart contract being 01:35:20.770 --> 01:35:23.310 align:start position:0% notion of a smart contract being deployed<01:35:21.130> within<01:35:21.520> the<01:35:22.210> operating<01:35:23.110> in<01:35:23.260> that 01:35:23.310 --> 01:35:23.320 align:start position:0% deployed within the operating in that 01:35:23.320 --> 01:35:25.620 align:start position:0% deployed within the operating in that environment<01:35:23.560> you<01:35:23.950> do<01:35:24.520> probably<01:35:24.970> have<01:35:25.330> the 01:35:25.620 --> 01:35:25.630 align:start position:0% environment you do probably have the 01:35:25.630 --> 01:35:28.110 align:start position:0% environment you do probably have the opportunity<01:35:26.230> to<01:35:26.380> think<01:35:26.620> about<01:35:27.130> new<01:35:27.610> type<01:35:27.940> of 01:35:28.110 --> 01:35:28.120 align:start position:0% opportunity to think about new type of 01:35:28.120 --> 01:35:30.960 align:start position:0% opportunity to think about new type of layer<01:35:28.450> to<01:35:28.690> constructs<01:35:29.140> that<01:35:29.290> may<01:35:29.590> be<01:35:29.820> in<01:35:30.820> a 01:35:30.960 --> 01:35:30.970 align:start position:0% layer to constructs that may be in a 01:35:30.970 --> 01:35:33.350 align:start position:0% layer to constructs that may be in a layer<01:35:31.150> to<01:35:31.360> context<01:35:31.810> kind<01:35:32.080> of<01:35:32.140> exists<01:35:32.620> within 01:35:33.350 --> 01:35:33.360 align:start position:0% layer to context kind of exists within 01:35:33.360 --> 01:35:37.260 align:start position:0% layer to context kind of exists within multiple<01:35:34.360> ease<01:35:35.010> with<01:35:36.010> that<01:35:36.190> step<01:35:36.700> plane<01:35:36.910> I 01:35:37.260 --> 01:35:37.270 align:start position:0% multiple ease with that step plane I 01:35:37.270 --> 01:35:39.540 align:start position:0% multiple ease with that step plane I could<01:35:37.720> do<01:35:37.990> very<01:35:38.320> research<01:35:38.890> to<01:35:39.070> decide<01:35:39.340> that's 01:35:39.540 --> 01:35:39.550 align:start position:0% could do very research to decide that's 01:35:39.550 --> 01:35:48.530 align:start position:0% could do very research to decide that's not<01:35:39.790> goodness<01:35:40.240> that<01:35:40.900> much 01:35:48.530 --> 01:35:48.540 align:start position:0% 01:35:48.540 --> 01:35:54.170 align:start position:0% so<01:35:49.140> the<01:35:49.290> EE<01:35:49.470> would<01:35:49.920> define<01:35:51.620> in<01:35:52.620> most<01:35:53.310> contexts 01:35:54.170 --> 01:35:54.180 align:start position:0% so the EE would define in most contexts 01:35:54.180 --> 01:35:55.910 align:start position:0% so the EE would define in most contexts he<01:35:54.600> would<01:35:54.870> define<01:35:55.140> some<01:35:55.410> sort<01:35:55.590> of<01:35:55.650> account 01:35:55.910 --> 01:35:55.920 align:start position:0% he would define some sort of account 01:35:55.920 --> 01:35:58.520 align:start position:0% he would define some sort of account model<01:35:56.130> some<01:35:56.790> sort<01:35:57.000> of<01:35:57.200> deployment<01:35:58.200> models 01:35:58.520 --> 01:35:58.530 align:start position:0% model some sort of deployment models 01:35:58.530 --> 01:36:00.620 align:start position:0% model some sort of deployment models some<01:35:58.740> sort<01:35:58.980> of<01:35:59.070> it<01:35:59.430> just<01:35:59.820> all<01:36:00.090> the<01:36:00.210> things<01:36:00.240> that 01:36:00.620 --> 01:36:00.630 align:start position:0% some sort of it just all the things that 01:36:00.630 --> 01:36:02.660 align:start position:0% some sort of it just all the things that you<01:36:00.720> think<01:36:00.840> of<01:36:00.990> is<01:36:01.170> like<01:36:01.200> is<01:36:01.560> eath<01:36:01.740> one<01:36:01.980> like 01:36:02.660 --> 01:36:02.670 align:start position:0% you think of is like is eath one like 01:36:02.670 --> 01:36:04.340 align:start position:0% you think of is like is eath one like those<01:36:02.850> things<01:36:03.120> are<01:36:03.300> now<01:36:03.510> like<01:36:03.870> in<01:36:04.020> terms<01:36:04.200> of 01:36:04.340 --> 01:36:04.350 align:start position:0% those things are now like in terms of 01:36:04.350 --> 01:36:05.810 align:start position:0% those things are now like in terms of its<01:36:04.530> common<01:36:04.920> deployment<01:36:05.250> all<01:36:05.550> that<01:36:05.670> kind<01:36:05.790> of 01:36:05.810 --> 01:36:05.820 align:start position:0% its common deployment all that kind of 01:36:05.820 --> 01:36:07.700 align:start position:0% its common deployment all that kind of stuff<01:36:05.910> how<01:36:06.360> transactions<01:36:07.050> are<01:36:07.170> interpreted 01:36:07.700 --> 01:36:07.710 align:start position:0% stuff how transactions are interpreted 01:36:07.710 --> 01:36:10.160 align:start position:0% stuff how transactions are interpreted and<01:36:08.010> modify<01:36:08.550> the<01:36:08.610> state<01:36:08.850> that<01:36:09.390> would<01:36:09.540> be<01:36:09.720> then 01:36:10.160 --> 01:36:10.170 align:start position:0% and modify the state that would be then 01:36:10.170 --> 01:36:13.250 align:start position:0% and modify the state that would be then definable<01:36:10.860> reliably<01:36:11.430> so<01:36:12.150> within<01:36:12.480> within<01:36:13.050> an 01:36:13.250 --> 01:36:13.260 align:start position:0% definable reliably so within within an 01:36:13.260 --> 01:36:15.650 align:start position:0% definable reliably so within within an employee<01:36:13.640> the<01:36:14.640> mechanic<01:36:15.120> was<01:36:15.210> still<01:36:15.420> operate 01:36:15.650 --> 01:36:15.660 align:start position:0% employee the mechanic was still operate 01:36:15.660 --> 01:36:17.480 align:start position:0% employee the mechanic was still operate very<01:36:15.840> similar<01:36:16.170> but<01:36:16.350> if<01:36:16.470> you<01:36:16.560> grow<01:36:17.010> your<01:36:17.190> own<01:36:17.220> EE 01:36:17.480 --> 01:36:17.490 align:start position:0% very similar but if you grow your own EE 01:36:17.490 --> 01:36:19.430 align:start position:0% very similar but if you grow your own EE and<01:36:17.850> you<01:36:18.030> wanted<01:36:18.420> a<01:36:18.480> notion<01:36:18.810> of<01:36:18.900> contracts<01:36:19.320> you 01:36:19.430 --> 01:36:19.440 align:start position:0% and you wanted a notion of contracts you 01:36:19.440 --> 01:36:20.780 align:start position:0% and you wanted a notion of contracts you might<01:36:19.560> have<01:36:19.650> to<01:36:19.740> borrow<01:36:19.890> some<01:36:20.160> those<01:36:20.310> concepts 01:36:20.780 --> 01:36:20.790 align:start position:0% might have to borrow some those concepts 01:36:20.790 --> 01:36:24.050 align:start position:0% might have to borrow some those concepts or<01:36:21.120> make<01:36:21.540> new<01:36:22.230> modifications<01:36:23.190> and<01:36:23.400> new<01:36:23.460> new 01:36:24.050 --> 01:36:24.060 align:start position:0% or make new modifications and new new 01:36:24.060 --> 01:36:25.970 align:start position:0% or make new modifications and new new ways<01:36:24.300> in<01:36:24.570> which<01:36:24.660> things<01:36:25.260> might<01:36:25.470> exist 01:36:25.970 --> 01:36:25.980 align:start position:0% ways in which things might exist 01:36:25.980 --> 01:36:31.520 align:start position:0% ways in which things might exist operating<01:36:27.710> so<01:36:28.710> again<01:36:29.040> like<01:36:29.480> yes<01:36:30.480> these<01:36:31.170> in 01:36:31.520 --> 01:36:31.530 align:start position:0% operating so again like yes these in 01:36:31.530 --> 01:36:33.140 align:start position:0% operating so again like yes these in some<01:36:31.800> respects<01:36:32.220> look<01:36:32.340> like<01:36:32.490> contracts<01:36:32.940> but 01:36:33.140 --> 01:36:33.150 align:start position:0% some respects look like contracts but 01:36:33.150 --> 01:36:37.100 align:start position:0% some respects look like contracts but they<01:36:33.240> also<01:36:34.040> can<01:36:35.040> look<01:36:35.220> like<01:36:35.430> protocols<01:36:36.420> right 01:36:37.100 --> 01:36:37.110 align:start position:0% they also can look like protocols right 01:36:37.110 --> 01:36:40.400 align:start position:0% they also can look like protocols right there<01:36:37.350> they're<01:36:37.620> like<01:36:38.510> contract<01:36:39.510> proclick<01:36:40.110> you 01:36:40.400 --> 01:36:40.410 align:start position:0% there they're like contract proclick you 01:36:40.410 --> 01:36:42.380 align:start position:0% there they're like contract proclick you define<01:36:40.770> the<01:36:41.130> user<01:36:41.310> layer<01:36:41.580> kind<01:36:41.910> of<01:36:41.970> protocol 01:36:42.380 --> 01:36:42.390 align:start position:0% define the user layer kind of protocol 01:36:42.390 --> 01:36:45.530 align:start position:0% define the user layer kind of protocol via<01:36:42.690> these<01:36:42.960> this<01:36:43.470> new<01:36:43.860> type<01:36:44.130> of<01:36:44.180> you<01:36:45.180> can<01:36:45.360> chain 01:36:45.530 --> 01:36:45.540 align:start position:0% via these this new type of you can chain 01:36:45.540 --> 01:36:50.630 align:start position:0% via these this new type of you can chain contract<01:36:46.140> that's<01:36:46.950> I<01:36:48.680> think<01:36:49.680> one<01:36:50.040> of<01:36:50.070> the<01:36:50.220> I 01:36:50.630 --> 01:36:50.640 align:start position:0% contract that's I think one of the I 01:36:50.640 --> 01:36:54.100 align:start position:0% contract that's I think one of the I mean<01:36:51.240> the<01:36:51.390> biggest<01:36:51.570> difference<01:36:52.050> between 01:36:54.100 --> 01:36:54.110 align:start position:0% mean the biggest difference between 01:36:54.110 --> 01:36:57.650 align:start position:0% mean the biggest difference between deploying<01:36:55.110> your<01:36:55.260> own<01:36:55.380> EE<01:36:55.580> versus<01:36:56.660> deploying 01:36:57.650 --> 01:36:57.660 align:start position:0% deploying your own EE versus deploying 01:36:57.660 --> 01:37:00.650 align:start position:0% deploying your own EE versus deploying their<01:36:57.870> contract<01:36:59.090> you<01:37:00.090> know<01:37:00.180> like<01:37:00.330> a<01:37:00.420> child 01:37:00.650 --> 01:37:00.660 align:start position:0% their contract you know like a child 01:37:00.660 --> 01:37:04.220 align:start position:0% their contract you know like a child contract<01:37:01.200> of<01:37:01.380> some<01:37:02.040> parent<01:37:02.400> you<01:37:02.850> know<01:37:02.940> EE<01:37:03.270> is 01:37:04.220 --> 01:37:04.230 align:start position:0% contract of some parent you know EE is 01:37:04.230 --> 01:37:08.030 align:start position:0% contract of some parent you know EE is to<01:37:04.440> point<01:37:04.680> that<01:37:04.860> ye<01:37:05.250> might<01:37:06.240> cost<01:37:06.510> say<01:37:07.080> $1,000 01:37:08.030 --> 01:37:08.040 align:start position:0% to point that ye might cost say $1,000 01:37:08.040 --> 01:37:11.450 align:start position:0% to point that ye might cost say $1,000 that<01:37:08.460> was<01:37:08.580> like<01:37:08.730> never<01:37:09.290> telex<01:37:10.290> pull<01:37:11.220> out<01:37:11.370> of 01:37:11.450 --> 01:37:11.460 align:start position:0% that was like never telex pull out of 01:37:11.460 --> 01:37:15.590 align:start position:0% that was like never telex pull out of the<01:37:11.520> air<01:37:11.640> a<01:37:12.410> few<01:37:13.410> months<01:37:13.620> ago<01:37:14.600> whereas 01:37:15.590 --> 01:37:15.600 align:start position:0% the air a few months ago whereas 01:37:15.600 --> 01:37:19.130 align:start position:0% the air a few months ago whereas deploying<01:37:16.590> a<01:37:17.160> contract<01:37:18.060> you<01:37:18.720> know<01:37:18.840> child 01:37:19.130 --> 01:37:19.140 align:start position:0% deploying a contract you know child 01:37:19.140 --> 01:37:20.470 align:start position:0% deploying a contract you know child contracts 01:37:20.470 --> 01:37:20.480 align:start position:0% contracts 01:37:20.480 --> 01:37:25.140 align:start position:0% contracts under<01:37:20.870> Nene<01:37:21.310> with<01:37:22.310> us<01:37:22.520> maybe<01:37:23.420> a<01:37:23.570> few<01:37:24.020> cents<01:37:24.350> and 01:37:25.140 --> 01:37:25.150 align:start position:0% under Nene with us maybe a few cents and 01:37:25.150 --> 01:37:30.610 align:start position:0% under Nene with us maybe a few cents and having<01:37:26.920> paying<01:37:27.920> the<01:37:28.010> $1,000<01:37:28.850> to<01:37:29.500> deploy<01:37:30.500> the 01:37:30.610 --> 01:37:30.620 align:start position:0% having paying the $1,000 to deploy the 01:37:30.620 --> 01:37:33.580 align:start position:0% having paying the $1,000 to deploy the ease<01:37:30.980> just<01:37:31.940> means<01:37:32.210> that<01:37:32.540> the<01:37:32.989> code<01:37:33.230> is<01:37:33.410> like 01:37:33.580 --> 01:37:33.590 align:start position:0% ease just means that the code is like 01:37:33.590 --> 01:37:36.970 align:start position:0% ease just means that the code is like early<01:37:33.920> there<01:37:34.160> and<01:37:34.550> so<01:37:35.320> you<01:37:36.320> know<01:37:36.440> you<01:37:36.679> could<01:37:36.800> be 01:37:36.970 --> 01:37:36.980 align:start position:0% early there and so you know you could be 01:37:36.980 --> 01:37:40.090 align:start position:0% early there and so you know you could be able<01:37:37.160> to<01:37:37.280> run<01:37:37.790> transactions<01:37:38.660> within<01:37:39.500> it<01:37:39.830> you 01:37:40.090 --> 01:37:40.100 align:start position:0% able to run transactions within it you 01:37:40.100 --> 01:37:42.340 align:start position:0% able to run transactions within it you know<01:37:40.580> many<01:37:40.880> more<01:37:41.030> per<01:37:41.270> watt<01:37:41.480> for<01:37:41.810> as<01:37:41.900> if<01:37:42.050> it's<01:37:42.199> a 01:37:42.340 --> 01:37:42.350 align:start position:0% know many more per watt for as if it's a 01:37:42.350 --> 01:37:46.750 align:start position:0% know many more per watt for as if it's a child<01:37:43.630> contract<01:37:44.650> maybe<01:37:45.650> you<01:37:46.460> know<01:37:46.550> you<01:37:46.640> have 01:37:46.750 --> 01:37:46.760 align:start position:0% child contract maybe you know you have 01:37:46.760 --> 01:37:49.930 align:start position:0% child contract maybe you know you have to<01:37:46.880> pass<01:37:47.060> in<01:37:47.270> the<01:37:47.360> code<01:37:47.600> every<01:37:47.870> time<01:37:48.110> and<01:37:48.940> your 01:37:49.930 --> 01:37:49.940 align:start position:0% to pass in the code every time and your 01:37:49.940 --> 01:37:52.570 align:start position:0% to pass in the code every time and your circle<01:37:50.330> would<01:37:50.420> be<01:37:50.480> less<01:37:50.830> this<01:37:51.830> is<01:37:51.949> what<01:37:52.370> you 01:37:52.570 --> 01:37:52.580 align:start position:0% circle would be less this is what you 01:37:52.580 --> 01:37:53.680 align:start position:0% circle would be less this is what you know<01:37:52.670> where<01:37:52.820> the<01:37:52.910> trade<01:37:53.090> officer 01:37:53.680 --> 01:37:53.690 align:start position:0% know where the trade officer 01:37:53.690 --> 01:37:55.419 align:start position:0% know where the trade officer yeah<01:37:53.960> at<01:37:54.199> the<01:37:54.260> same<01:37:54.440> time<01:37:54.650> you've<01:37:54.800> also<01:37:54.980> you 01:37:55.419 --> 01:37:55.429 align:start position:0% yeah at the same time you've also you 01:37:55.429 --> 01:37:58.959 align:start position:0% yeah at the same time you've also you know<01:37:56.650> fragments<01:37:57.650> in<01:37:57.770> your<01:37:57.949> universe<01:37:58.460> from 01:37:58.959 --> 01:37:58.969 align:start position:0% know fragments in your universe from 01:37:58.969 --> 01:38:02.860 align:start position:0% know fragments in your universe from other<01:37:59.300> like<01:37:59.840> you<01:38:00.469> you<01:38:00.830> now<01:38:01.010> will<01:38:01.280> require<01:38:01.870> like 01:38:02.860 --> 01:38:02.870 align:start position:0% other like you you now will require like 01:38:02.870 --> 01:38:04.720 align:start position:0% other like you you now will require like a<01:38:03.110> synchronous<01:38:03.739> communication<01:38:03.860> to<01:38:04.580> another 01:38:04.720 --> 01:38:04.730 align:start position:0% a synchronous communication to another 01:38:04.730 --> 01:38:07.350 align:start position:0% a synchronous communication to another so<01:38:05.360> you're<01:38:05.510> missing<01:38:05.690> out<01:38:05.900> on<01:38:05.929> some<01:38:06.410> potential 01:38:07.350 --> 01:38:07.360 align:start position:0% so you're missing out on some potential 01:38:07.360 --> 01:38:10.419 align:start position:0% so you're missing out on some potential like<01:38:08.360> synergies<01:38:08.900> and<01:38:09.080> just<01:38:09.800> deploying<01:38:10.130> into 01:38:10.419 --> 01:38:10.429 align:start position:0% like synergies and just deploying into 01:38:10.429 --> 01:38:12.880 align:start position:0% like synergies and just deploying into an<01:38:10.520> existing<01:38:10.730> media<01:38:11.150> as<01:38:11.210> well<01:38:11.360> and<01:38:11.679> to<01:38:12.679> speak 01:38:12.880 --> 01:38:12.890 align:start position:0% an existing media as well and to speak 01:38:12.890 --> 01:38:15.070 align:start position:0% an existing media as well and to speak to<01:38:13.010> that<01:38:13.100> like<01:38:13.400> a<01:38:13.429> thousand<01:38:13.969> like<01:38:14.540> because<01:38:14.900> the 01:38:15.070 --> 01:38:15.080 align:start position:0% to that like a thousand like because the 01:38:15.080 --> 01:38:16.270 align:start position:0% to that like a thousand like because the beacon<01:38:15.320> chain<01:38:15.500> is<01:38:15.620> this<01:38:15.770> component<01:38:16.070> the 01:38:16.270 --> 01:38:16.280 align:start position:0% beacon chain is this component the 01:38:16.280 --> 01:38:18.850 align:start position:0% beacon chain is this component the system<01:38:16.610> image<01:38:16.760> an<01:38:16.969> earlier<01:38:17.239> that<01:38:17.780> like<01:38:18.020> every 01:38:18.850 --> 01:38:18.860 align:start position:0% system image an earlier that like every 01:38:18.860 --> 01:38:20.890 align:start position:0% system image an earlier that like every node<01:38:19.190> has<01:38:19.640> to<01:38:19.820> run<01:38:19.969> this<01:38:20.120> thing<01:38:20.360> to<01:38:20.600> be<01:38:20.690> able<01:38:20.780> to 01:38:20.890 --> 01:38:20.900 align:start position:0% node has to run this thing to be able to 01:38:20.900 --> 01:38:22.780 align:start position:0% node has to run this thing to be able to reverse<01:38:21.050> inca<01:38:21.380> run<01:38:21.590> shards<01:38:22.250> and<01:38:22.429> sync<01:38:22.640> data 01:38:22.780 --> 01:38:22.790 align:start position:0% reverse inca run shards and sync data 01:38:22.790 --> 01:38:26.680 align:start position:0% reverse inca run shards and sync data village<01:38:23.090> charts<01:38:23.890> it<01:38:24.890> we<01:38:25.340> have<01:38:25.489> to<01:38:25.640> bound<01:38:25.880> the 01:38:26.680 --> 01:38:26.690 align:start position:0% village charts it we have to bound the 01:38:26.690 --> 01:38:28.810 align:start position:0% village charts it we have to bound the state<01:38:26.960> size<01:38:27.170> and<01:38:27.380> so<01:38:27.500> like<01:38:27.830> this<01:38:28.130> capital<01:38:28.699> is 01:38:28.810 --> 01:38:28.820 align:start position:0% state size and so like this capital is 01:38:28.820 --> 01:38:35.720 align:start position:0% state size and so like this capital is like<01:38:29.000> likely<01:38:32.590> burned<01:38:33.590> or<01:38:34.040> locked<01:38:34.880> up<01:38:35.090> this 01:38:35.720 --> 01:38:35.730 align:start position:0% like likely burned or locked up this 01:38:35.730 --> 01:38:37.520 align:start position:0% like likely burned or locked up this economic<01:38:36.180> models<01:38:36.480> under<01:38:36.840> investigation<01:38:37.200> but 01:38:37.520 --> 01:38:37.530 align:start position:0% economic models under investigation but 01:38:37.530 --> 01:38:39.979 align:start position:0% economic models under investigation but would<01:38:37.680> be<01:38:37.850> capital-intensive<01:38:38.850> because<01:38:39.720> the 01:38:39.979 --> 01:38:39.989 align:start position:0% would be capital-intensive because the 01:38:39.989 --> 01:38:43.550 align:start position:0% would be capital-intensive because the state<01:38:40.290> needs<01:38:40.530> to<01:38:40.650> be<01:38:40.830> succinct<01:38:42.050> and<01:38:43.050> I<01:38:43.230> prefer 01:38:43.550 --> 01:38:43.560 align:start position:0% state needs to be succinct and I prefer 01:38:43.560 --> 01:38:45.410 align:start position:0% state needs to be succinct and I prefer locked<01:38:43.860> up<01:38:44.070> just<01:38:44.100> in<01:38:44.550> the<01:38:44.610> same<01:38:44.790> way<01:38:44.850> you<01:38:45.330> know 01:38:45.410 --> 01:38:45.420 align:start position:0% locked up just in the same way you know 01:38:45.420 --> 01:38:48.650 align:start position:0% locked up just in the same way you know if<01:38:46.020> you<01:38:46.170> want<01:38:46.350> to<01:38:46.410> become<01:38:46.680> a<01:38:46.920> validator<01:38:47.660> your 01:38:48.650 --> 01:38:48.660 align:start position:0% if you want to become a validator your 01:38:48.660 --> 01:38:51.440 align:start position:0% if you want to become a validator your validator<01:38:49.560> account<01:38:49.920> is<01:38:50.190> you<01:38:50.880> know<01:38:51.000> it's<01:38:51.239> an 01:38:51.440 --> 01:38:51.450 align:start position:0% validator account is you know it's an 01:38:51.450 --> 01:38:53.780 align:start position:0% validator account is you know it's an account<01:38:52.080> underneath<01:38:52.500> the<01:38:52.710> beacon<01:38:53.130> state<01:38:53.370> so<01:38:53.760> I 01:38:53.780 --> 01:38:53.790 align:start position:0% account underneath the beacon state so I 01:38:53.790 --> 01:38:56.330 align:start position:0% account underneath the beacon state so I revalidate<01:38:54.480> er<01:38:54.510> Lopes<01:38:55.110> the<01:38:55.290> beacon<01:38:55.560> state<01:38:55.800> so 01:38:56.330 --> 01:38:56.340 align:start position:0% revalidate er Lopes the beacon state so 01:38:56.340 --> 01:38:59.180 align:start position:0% revalidate er Lopes the beacon state so in<01:38:56.670> order<01:38:56.790> to<01:38:56.970> limit<01:38:57.150> the<01:38:57.270> glow<01:38:57.600> of<01:38:57.900> a<01:38:58.190> beacon 01:38:59.180 --> 01:38:59.190 align:start position:0% in order to limit the glow of a beacon 01:38:59.190 --> 01:39:01.520 align:start position:0% in order to limit the glow of a beacon state<01:38:59.460> it<01:39:00.120> costs<01:39:00.420> 32<01:39:00.930> litre<01:39:01.200> to<01:39:01.290> become<01:39:01.470> a 01:39:01.520 --> 01:39:01.530 align:start position:0% state it costs 32 litre to become a 01:39:01.530 --> 01:39:05.000 align:start position:0% state it costs 32 litre to become a validator<01:39:02.210> and<01:39:03.210> it's<01:39:03.750> not<01:39:03.900> burned<01:39:04.140> it's<01:39:04.650> just 01:39:05.000 --> 01:39:05.010 align:start position:0% validator and it's not burned it's just 01:39:05.010 --> 01:39:06.290 align:start position:0% validator and it's not burned it's just a<01:39:05.040> deposit<01:39:05.489> so<01:39:05.670> we<01:39:05.760> can<01:39:05.910> take<01:39:06.030> the<01:39:06.150> same 01:39:06.290 --> 01:39:06.300 align:start position:0% a deposit so we can take the same 01:39:06.300 --> 01:39:09.770 align:start position:0% a deposit so we can take the same approach<01:39:06.420> with<01:39:06.810> employees<01:39:08.450> all<01:39:09.450> right<01:39:09.540> then 01:39:09.770 --> 01:39:09.780 align:start position:0% approach with employees all right then 01:39:09.780 --> 01:39:12.350 align:start position:0% approach with employees all right then you<01:39:09.900> get<01:39:10.020> the<01:39:10.140> idea<01:39:10.170> of<01:39:10.500> any<01:39:11.460> disappearing<01:39:12.239> at 01:39:12.350 --> 01:39:12.360 align:start position:0% you get the idea of any disappearing at 01:39:12.360 --> 01:39:13.610 align:start position:0% you get the idea of any disappearing at some<01:39:12.510> point<01:39:12.750> so<01:39:12.960> there's<01:39:13.140> that<01:39:13.290> there's<01:39:13.500> the 01:39:13.610 --> 01:39:13.620 align:start position:0% some point so there's that there's the 01:39:13.620 --> 01:39:15.440 align:start position:0% some point so there's that there's the laser<01:39:13.950> everything<01:39:14.250> should<01:39:14.730> yeah<01:39:15.060> it's 01:39:15.440 --> 01:39:15.450 align:start position:0% laser everything should yeah it's 01:39:15.450 --> 01:39:20.740 align:start position:0% laser everything should yeah it's explored<01:39:18.260> in<01:39:19.260> the<01:39:19.560> in<01:39:19.770> the<01:39:19.890> minimal 01:39:20.740 --> 01:39:20.750 align:start position:0% explored in the in the minimal 01:39:20.750 --> 01:39:24.680 align:start position:0% explored in the in the minimal territorial<01:39:21.750> model<01:39:23.300> would<01:39:24.300> you<01:39:24.420> have 01:39:24.680 --> 01:39:24.690 align:start position:0% territorial model would you have 01:39:24.690 --> 01:39:26.330 align:start position:0% territorial model would you have arbitrary<01:39:25.290> state<01:39:25.560> and<01:39:25.830> arbitrary 01:39:26.330 --> 01:39:26.340 align:start position:0% arbitrary state and arbitrary 01:39:26.340 --> 01:39:27.800 align:start position:0% arbitrary state and arbitrary computation<01:39:26.970> on<01:39:27.090> that<01:39:27.270> state<01:39:27.510> just<01:39:27.750> like 01:39:27.800 --> 01:39:27.810 align:start position:0% computation on that state just like 01:39:27.810 --> 01:39:34.760 align:start position:0% computation on that state just like really<01:39:28.260> intense<01:39:28.560> a<01:39:28.830> trend<01:39:32.960> or<01:39:33.960> you<01:39:34.620> know 01:39:34.760 --> 01:39:34.770 align:start position:0% really intense a trend or you know 01:39:34.770 --> 01:39:37.010 align:start position:0% really intense a trend or you know you're<01:39:34.950> like<01:39:35.160> locking<01:39:35.430> up<01:39:35.790> some<01:39:36.660> amount<01:39:36.930> of 01:39:37.010 --> 01:39:37.020 align:start position:0% you're like locking up some amount of 01:39:37.020 --> 01:39:39.050 align:start position:0% you're like locking up some amount of capital<01:39:37.230> to<01:39:37.470> keep<01:39:38.100> some<01:39:38.489> kind<01:39:38.640> of<01:39:38.820> state 01:39:39.050 --> 01:39:39.060 align:start position:0% capital to keep some kind of state 01:39:39.060 --> 01:39:40.840 align:start position:0% capital to keep some kind of state because<01:39:39.420> everyone<01:39:39.870> needs<01:39:39.989> to<01:39:40.170> own<01:39:40.260> the<01:39:40.560> state 01:39:40.840 --> 01:39:40.850 align:start position:0% because everyone needs to own the state 01:39:40.850 --> 01:39:43.370 align:start position:0% because everyone needs to own the state and<01:39:41.850> I'm<01:39:41.940> just<01:39:42.180> curious<01:39:42.300> if<01:39:42.570> you<01:39:42.720> would<01:39:42.960> you 01:39:43.370 --> 01:39:43.380 align:start position:0% and I'm just curious if you would you 01:39:43.380 --> 01:39:46.640 align:start position:0% and I'm just curious if you would you know<01:39:43.500> allow<01:39:44.250> in<01:39:44.670> this<01:39:44.910> model<01:39:45.690> arbitrary<01:39:46.380> state 01:39:46.640 --> 01:39:46.650 align:start position:0% know allow in this model arbitrary state 01:39:46.650 --> 01:39:53.270 align:start position:0% know allow in this model arbitrary state and<01:39:46.950> arbitrary<01:39:47.430> state<01:39:48.170> regulations<01:39:51.860> yeah<01:39:52.860> so 01:39:53.270 --> 01:39:53.280 align:start position:0% and arbitrary state regulations yeah so 01:39:53.280 --> 01:39:58.120 align:start position:0% and arbitrary state regulations yeah so I<01:39:55.190> guess<01:39:56.190> I<01:39:56.280> should<01:39:56.460> qualify<01:39:56.670> within<01:39:57.510> the 01:39:58.120 --> 01:39:58.130 align:start position:0% I guess I should qualify within the 01:39:58.130 --> 01:40:05.810 align:start position:0% I guess I should qualify within the dictatorial<01:39:59.130> model<01:39:59.790> where 01:40:05.810 --> 01:40:05.820 align:start position:0% 01:40:05.820 --> 01:40:08.180 align:start position:0% the<01:40:06.360> architects<01:40:07.080> of<01:40:07.200> the<01:40:07.350> system<01:40:07.710> restrict 01:40:08.180 --> 01:40:08.190 align:start position:0% the architects of the system restrict 01:40:08.190 --> 01:40:13.730 align:start position:0% the architects of the system restrict what<01:40:09.120> ease<01:40:09.720> you<01:40:09.900> can<01:40:09.960> deploy<01:40:10.920> like<01:40:11.760> there<01:40:12.750> it 01:40:13.730 --> 01:40:13.740 align:start position:0% what ease you can deploy like there it 01:40:13.740 --> 01:40:15.860 align:start position:0% what ease you can deploy like there it might<01:40:14.070> not<01:40:14.340> make<01:40:14.550> a<01:40:14.610> difference<01:40:14.790> if<01:40:15.330> it's<01:40:15.750> the 01:40:15.860 --> 01:40:15.870 align:start position:0% might not make a difference if it's the 01:40:15.870 --> 01:40:20.990 align:start position:0% might not make a difference if it's the type<01:40:16.080> of<01:40:16.110> EE<01:40:16.470> where<01:40:18.110> users<01:40:19.110> can<01:40:19.410> deploy<01:40:20.280> any 01:40:20.990 --> 01:40:21.000 align:start position:0% type of EE where users can deploy any 01:40:21.000 --> 01:40:22.790 align:start position:0% type of EE where users can deploy any kind<01:40:21.300> of<01:40:21.330> code<01:40:21.600> they<01:40:21.780> want<01:40:21.990> under<01:40:22.260> that<01:40:22.410> Evie 01:40:22.790 --> 01:40:22.800 align:start position:0% kind of code they want under that Evie 01:40:22.800 --> 01:40:27.590 align:start position:0% kind of code they want under that Evie so<01:40:23.340> if<01:40:23.670> that<01:40:24.120> is<01:40:24.300> the<01:40:24.330> case<01:40:24.570> then<01:40:26.030> there's<01:40:27.030> you 01:40:27.590 --> 01:40:27.600 align:start position:0% so if that is the case then there's you 01:40:27.600 --> 01:40:30.560 align:start position:0% so if that is the case then there's you know<01:40:28.490> well<01:40:29.490> what<01:40:29.730> layer<01:40:30.000> are<01:40:30.120> you<01:40:30.240> operating 01:40:30.560 --> 01:40:30.570 align:start position:0% know well what layer are you operating 01:40:30.570 --> 01:40:32.360 align:start position:0% know well what layer are you operating at<01:40:30.900> and<01:40:31.170> maybe<01:40:31.380> it<01:40:31.800> doesn't<01:40:32.130> make<01:40:32.340> a 01:40:32.360 --> 01:40:32.370 align:start position:0% at and maybe it doesn't make a 01:40:32.370 --> 01:40:33.890 align:start position:0% at and maybe it doesn't make a difference<01:40:32.550> users<01:40:33.060> can<01:40:33.210> run<01:40:33.390> any<01:40:33.540> code<01:40:33.690> they 01:40:33.890 --> 01:40:33.900 align:start position:0% difference users can run any code they 01:40:33.900 --> 01:40:35.180 align:start position:0% difference users can run any code they want<01:40:34.080> anyway 01:40:35.180 --> 01:40:35.190 align:start position:0% want anyway 01:40:35.190 --> 01:40:38.090 align:start position:0% want anyway and<01:40:35.570> if<01:40:36.570> that<01:40:36.870> role<01:40:37.170> of<01:40:37.200> the<01:40:37.410> e<01:40:37.440> is<01:40:37.800> very 01:40:38.090 --> 01:40:38.100 align:start position:0% and if that role of the e is very 01:40:38.100 --> 01:40:41.650 align:start position:0% and if that role of the e is very minimal<01:40:38.730> but<01:40:39.090> if<01:40:39.270> it's<01:40:39.450> like<01:40:39.800> if<01:40:40.800> these 01:40:41.650 --> 01:40:41.660 align:start position:0% minimal but if it's like if these 01:40:41.660 --> 01:40:44.960 align:start position:0% minimal but if it's like if these sanction<01:40:42.660> II's<01:40:43.050> restrict<01:40:43.740> the<01:40:43.860> type<01:40:44.040> of<01:40:44.250> code 01:40:44.960 --> 01:40:44.970 align:start position:0% sanction II's restrict the type of code 01:40:44.970 --> 01:40:51.200 align:start position:0% sanction II's restrict the type of code that<01:40:45.000> people<01:40:45.600> can<01:40:46.290> deploy<01:40:49.340> then<01:40:50.340> you<01:40:51.150> know 01:40:51.200 --> 01:40:51.210 align:start position:0% that people can deploy then you know 01:40:51.210 --> 01:40:54.710 align:start position:0% that people can deploy then you know those<01:40:51.590> that'd<01:40:52.590> be<01:40:52.710> a<01:40:52.740> very<01:40:52.980> dictatorial<01:40:53.720> you 01:40:54.710 --> 01:40:54.720 align:start position:0% those that'd be a very dictatorial you 01:40:54.720 --> 01:40:56.690 align:start position:0% those that'd be a very dictatorial you know<01:40:55.050> certainly<01:40:55.560> not<01:40:55.830> the<01:40:56.010> intention<01:40:56.280> on<01:40:56.520> that 01:40:56.690 --> 01:40:56.700 align:start position:0% know certainly not the intention on that 01:40:56.700 --> 01:41:00.620 align:start position:0% know certainly not the intention on that extreme<01:40:57.740> yeah<01:40:59.000> all<01:41:00.000> right<01:41:00.150> we<01:41:00.330> have<01:41:00.450> good 01:41:00.620 --> 01:41:00.630 align:start position:0% extreme yeah all right we have good 01:41:00.630 --> 01:41:03.260 align:start position:0% extreme yeah all right we have good sorry<01:41:01.560> notices<01:41:02.040> just<01:41:02.490> materialize<01:41:03.000> I<01:41:03.150> also 01:41:03.260 --> 01:41:03.270 align:start position:0% sorry notices just materialize I also 01:41:03.270 --> 01:41:05.090 align:start position:0% sorry notices just materialize I also think<01:41:03.540> it'd<01:41:03.630> be<01:41:03.660> sad<01:41:03.990> if<01:41:04.230> that<01:41:04.860> were<01:41:04.980> the<01:41:05.010> case 01:41:05.090 --> 01:41:05.100 align:start position:0% think it'd be sad if that were the case 01:41:05.100 --> 01:41:07.610 align:start position:0% think it'd be sad if that were the case because<01:41:05.760> like<01:41:06.450> you<01:41:06.930> want<01:41:07.110> people<01:41:07.380> to<01:41:07.470> innovate 01:41:07.610 --> 01:41:07.620 align:start position:0% because like you want people to innovate 01:41:07.620 --> 01:41:09.270 align:start position:0% because like you want people to innovate and<01:41:08.040> try<01:41:08.250> a<01:41:08.670> lot 01:41:09.270 --> 01:41:09.280 align:start position:0% and try a lot 01:41:09.280 --> 01:41:12.840 align:start position:0% and try a lot I<01:41:10.140> think<01:41:11.140> that's<01:41:11.320> yeah<01:41:11.740> that's<01:41:11.770> our<01:41:12.370> goal<01:41:12.580> and 01:41:12.840 --> 01:41:12.850 align:start position:0% I think that's yeah that's our goal and 01:41:12.850 --> 01:41:17.460 align:start position:0% I think that's yeah that's our goal and still<01:41:13.240> Ravenna<01:41:15.510> soul<01:41:16.510> might<01:41:16.870> understand<01:41:17.350> is 01:41:17.460 --> 01:41:17.470 align:start position:0% still Ravenna soul might understand is 01:41:17.470 --> 01:41:20.010 align:start position:0% still Ravenna soul might understand is basically<01:41:17.920> that<01:41:18.400> Eve<01:41:18.760> has<01:41:19.660> it's 01:41:20.010 --> 01:41:20.020 align:start position:0% basically that Eve has it's 01:41:20.020 --> 01:41:22.290 align:start position:0% basically that Eve has it's basically<01:41:20.590> a<01:41:20.980> letter<01:41:21.130> moment<01:41:21.580> that<01:41:21.700> conveys 01:41:22.290 --> 01:41:22.300 align:start position:0% basically a letter moment that conveys 01:41:22.300 --> 01:41:25.490 align:start position:0% basically a letter moment that conveys EXO<01:41:23.290> and<01:41:23.500> also<01:41:23.830> had<01:41:24.010> defined<01:41:24.340> how<01:41:24.580> these 01:41:25.490 --> 01:41:25.500 align:start position:0% EXO and also had defined how these 01:41:25.500 --> 01:41:28.880 align:start position:0% EXO and also had defined how these transactions<01:41:26.500> can<01:41:26.830> modify<01:41:27.220> this<01:41:27.400> day<01:41:27.820> in<01:41:28.090> the 01:41:28.880 --> 01:41:28.890 align:start position:0% transactions can modify this day in the 01:41:28.890 --> 01:41:31.950 align:start position:0% transactions can modify this day in the past<01:41:29.890> my<01:41:30.130> culture<01:41:30.550> my<01:41:30.580> name<01:41:30.850> isn't<01:41:31.090> one<01:41:31.330> and 01:41:31.950 --> 01:41:31.960 align:start position:0% past my culture my name isn't one and 01:41:31.960 --> 01:41:34.560 align:start position:0% past my culture my name isn't one and also<01:41:32.170> in<01:41:32.620> technical<01:41:33.610> details<01:41:34.030> of<01:41:34.150> scripting 01:41:34.560 --> 01:41:34.570 align:start position:0% also in technical details of scripting 01:41:34.570 --> 01:41:37.380 align:start position:0% also in technical details of scripting work<01:41:34.780> so<01:41:35.290> one<01:41:35.530> question<01:41:35.860> is<01:41:36.390> supported 01:41:37.380 --> 01:41:37.390 align:start position:0% work so one question is supported 01:41:37.390 --> 01:41:39.240 align:start position:0% work so one question is supported possible<01:41:37.840> patterns<01:41:38.140> can<01:41:38.380> positive<01:41:38.770> qualities 01:41:39.240 --> 01:41:39.250 align:start position:0% possible patterns can positive qualities 01:41:39.250 --> 01:41:42.330 align:start position:0% possible patterns can positive qualities in<01:41:39.550> these<01:41:39.700> and<01:41:40.210> this<01:41:41.200> basically<01:41:41.860> Domino's 01:41:42.330 --> 01:41:42.340 align:start position:0% in these and this basically Domino's 01:41:42.340 --> 01:41:45.210 align:start position:0% in these and this basically Domino's also<01:41:42.730> scored<01:41:43.120> responding<01:41:43.810> at<01:41:44.050> a<01:41:44.200> survival<01:41:44.860> in 01:41:45.210 --> 01:41:45.220 align:start position:0% also scored responding at a survival in 01:41:45.220 --> 01:41:50.490 align:start position:0% also scored responding at a survival in HP<01:41:45.730> Israel<01:41:46.300> and<01:41:46.600> if<01:41:47.440> there's<01:41:48.010> a<01:41:48.660> person<01:41:49.660> in<01:41:50.260> a 01:41:50.490 --> 01:41:50.500 align:start position:0% HP Israel and if there's a person in a 01:41:50.500 --> 01:41:52.710 align:start position:0% HP Israel and if there's a person in a developer<01:41:51.100> that<01:41:51.370> curve<01:41:51.730> a<01:41:51.850> is<01:41:51.880> even<01:41:52.210> amount 01:41:52.710 --> 01:41:52.720 align:start position:0% developer that curve a is even amount 01:41:52.720 --> 01:41:58.440 align:start position:0% developer that curve a is even amount isn't<01:41:53.380> all<01:41:54.450> internationally<01:41:55.450> great<01:41:56.380> some<01:41:57.450> is 01:41:58.440 --> 01:41:58.450 align:start position:0% isn't all internationally great some is 01:41:58.450 --> 01:42:02.310 align:start position:0% isn't all internationally great some is actually<01:41:59.200> in<01:41:59.770> this<01:41:59.950> new<01:42:00.280> EEO<01:42:00.820> any<01:42:01.420> existing<01:42:02.020> in 01:42:02.310 --> 01:42:02.320 align:start position:0% actually in this new EEO any existing in 01:42:02.320 --> 01:42:06.870 align:start position:0% actually in this new EEO any existing in how<01:42:02.680> to<01:42:02.740> prevent<01:42:03.720> that<01:42:04.720> happening<01:42:05.880> because 01:42:06.870 --> 01:42:06.880 align:start position:0% how to prevent that happening because 01:42:06.880 --> 01:42:09.650 align:start position:0% how to prevent that happening because like<01:42:07.390> the<01:42:07.570> books<01:42:07.870> I<01:42:08.020> already<01:42:08.350> came 01:42:09.650 --> 01:42:09.660 align:start position:0% like the books I already came 01:42:09.660 --> 01:42:12.180 align:start position:0% like the books I already came defective<01:42:10.660> also<01:42:11.140> in<01:42:11.260> Canada<01:42:11.590> clients<01:42:12.100> of<01:42:12.160> a 01:42:12.180 --> 01:42:12.190 align:start position:0% defective also in Canada clients of a 01:42:12.190 --> 01:42:15.330 align:start position:0% defective also in Canada clients of a camera<01:42:13.020> yeah<01:42:14.020> I<01:42:14.050> think<01:42:14.230> so 01:42:15.330 --> 01:42:15.340 align:start position:0% camera yeah I think so 01:42:15.340 --> 01:42:18.270 align:start position:0% camera yeah I think so balances<01:42:15.910> of<01:42:16.030> the<01:42:16.060> EES<01:42:16.480> are<01:42:16.720> not<01:42:17.560> going<01:42:18.070> to<01:42:18.160> be 01:42:18.270 --> 01:42:18.280 align:start position:0% balances of the EES are not going to be 01:42:18.280 --> 01:42:19.320 align:start position:0% balances of the EES are not going to be significantly<01:42:18.850> different 01:42:19.320 --> 01:42:19.330 align:start position:0% significantly different 01:42:19.330 --> 01:42:21.240 align:start position:0% significantly different as<01:42:19.450> an<01:42:19.660> example<01:42:19.870> than<01:42:20.140> a<01:42:20.230> validator<01:42:20.650> balance 01:42:21.240 --> 01:42:21.250 align:start position:0% as an example than a validator balance 01:42:21.250 --> 01:42:25.230 align:start position:0% as an example than a validator balance they<01:42:21.550> have<01:42:21.730> the<01:42:22.060> ability<01:42:22.180> to<01:42:23.010> pass<01:42:24.240> there's 01:42:25.230 --> 01:42:25.240 align:start position:0% they have the ability to pass there's 01:42:25.240 --> 01:42:28.530 align:start position:0% they have the ability to pass there's the<01:42:25.360> ability<01:42:25.510> to<01:42:25.750> deposit<01:42:26.730> but<01:42:27.730> funds<01:42:28.000> to<01:42:28.420> be 01:42:28.530 --> 01:42:28.540 align:start position:0% the ability to deposit but funds to be 01:42:28.540 --> 01:42:30.690 align:start position:0% the ability to deposit but funds to be because<01:42:29.200> the<01:42:29.290> tariff<01:42:29.500> alligator<01:42:29.860> so<01:42:30.130> as<01:42:30.490> far 01:42:30.690 --> 01:42:30.700 align:start position:0% because the tariff alligator so as far 01:42:30.700 --> 01:42:32.550 align:start position:0% because the tariff alligator so as far as<01:42:30.760> like<01:42:30.880> funds<01:42:31.870> being<01:42:32.140> printed<01:42:32.380> out<01:42:32.500> of 01:42:32.550 --> 01:42:32.560 align:start position:0% as like funds being printed out of 01:42:32.560 --> 01:42:35.100 align:start position:0% as like funds being printed out of nowhere<01:42:32.800> that<01:42:33.700> would<01:42:33.880> be<01:42:34.030> an<01:42:34.120> issue<01:42:34.240> but<01:42:34.780> but 01:42:35.100 --> 01:42:35.110 align:start position:0% nowhere that would be an issue but but 01:42:35.110 --> 01:42:38.700 align:start position:0% nowhere that would be an issue but but what<01:42:35.320> could<01:42:35.560> happen<01:42:35.980> is<01:42:36.600> just<01:42:37.600> like<01:42:37.750> one<01:42:38.290> you 01:42:38.700 --> 01:42:38.710 align:start position:0% what could happen is just like one you 01:42:38.710 --> 01:42:41.190 align:start position:0% what could happen is just like one you need<01:42:39.100> to<01:42:39.220> have<01:42:39.250> a<01:42:39.670> very<01:42:40.120> significant<01:42:40.720> audit<01:42:40.990> on 01:42:41.190 --> 01:42:41.200 align:start position:0% need to have a very significant audit on 01:42:41.200 --> 01:42:43.860 align:start position:0% need to have a very significant audit on a<01:42:41.230> smart<01:42:41.530> contract<01:42:41.710> a<01:42:42.210> needy<01:42:43.210> would<01:42:43.450> also<01:42:43.600> need 01:42:43.860 --> 01:42:43.870 align:start position:0% a smart contract a needy would also need 01:42:43.870 --> 01:42:45.270 align:start position:0% a smart contract a needy would also need to<01:42:43.930> go<01:42:44.080> through<01:42:44.350> that<01:42:44.620> same<01:42:44.860> thing<01:42:44.920> because 01:42:45.270 --> 01:42:45.280 align:start position:0% to go through that same thing because 01:42:45.280 --> 01:42:47.910 align:start position:0% to go through that same thing because you<01:42:45.490> wouldn't<01:42:45.820> want<01:42:45.970> it<01:42:46.030> to<01:42:46.060> them<01:42:46.330> users<01:42:47.110> bring 01:42:47.910 --> 01:42:47.920 align:start position:0% you wouldn't want it to them users bring 01:42:47.920 --> 01:42:49.230 align:start position:0% you wouldn't want it to them users bring their<01:42:48.100> funds<01:42:48.310> into<01:42:48.640> it<01:42:48.760> and<01:42:48.910> then<01:42:49.000> you<01:42:49.120> would 01:42:49.230 --> 01:42:49.240 align:start position:0% their funds into it and then you would 01:42:49.240 --> 01:42:54.510 align:start position:0% their funds into it and then you would want<01:42:49.450> to<01:42:49.540> steal<01:42:50.080> your<01:42:50.230> files<01:42:53.250> right<01:42:54.250> so<01:42:54.370> just 01:42:54.510 --> 01:42:54.520 align:start position:0% want to steal your files right so just 01:42:54.520 --> 01:42:58.260 align:start position:0% want to steal your files right so just to<01:42:54.580> be<01:42:54.700> clear<01:42:55.650> from<01:42:56.650> the<01:42:56.740> notion<01:42:57.310> the<01:42:57.910> only 01:42:58.260 --> 01:42:58.270 align:start position:0% to be clear from the notion the only 01:42:58.270 --> 01:43:00.750 align:start position:0% to be clear from the notion the only thing<01:42:58.390> that<01:42:58.540> owns<01:42:58.750> ether<01:42:59.590> and<01:42:59.830> in<01:43:00.280> this<01:43:00.400> model 01:43:00.750 --> 01:43:00.760 align:start position:0% thing that owns ether and in this model 01:43:00.760 --> 01:43:02.490 align:start position:0% thing that owns ether and in this model is<01:43:00.940> validator<01:43:01.720> accounts<01:43:02.140> on<01:43:02.230> the<01:43:02.290> beacon 01:43:02.490 --> 01:43:02.500 align:start position:0% is validator accounts on the beacon 01:43:02.500 --> 01:43:04.050 align:start position:0% is validator accounts on the beacon chain<01:43:02.710> and<01:43:03.340> from<01:43:03.490> the<01:43:03.580> layer<01:43:03.730> one<01:43:03.910> perspective 01:43:04.050 --> 01:43:04.060 align:start position:0% chain and from the layer one perspective 01:43:04.060 --> 01:43:07.580 align:start position:0% chain and from the layer one perspective and<01:43:04.450> these<01:43:05.290> e's<01:43:05.740> they<01:43:06.430> have<01:43:06.640> they<01:43:07.090> have<01:43:07.300> a 01:43:07.580 --> 01:43:07.590 align:start position:0% and these e's they have they have a 01:43:07.590 --> 01:43:09.450 align:start position:0% and these e's they have they have a certain<01:43:08.590> amount<01:43:08.650> of<01:43:08.770> ether<01:43:09.010> assigned<01:43:09.250> to<01:43:09.340> them 01:43:09.450 --> 01:43:09.460 align:start position:0% certain amount of ether assigned to them 01:43:09.460 --> 01:43:11.340 align:start position:0% certain amount of ether assigned to them then<01:43:09.910> within<01:43:10.240> the<01:43:10.480> there's<01:43:10.990> some<01:43:11.140> sort<01:43:11.290> of 01:43:11.340 --> 01:43:11.350 align:start position:0% then within the there's some sort of 01:43:11.350 --> 01:43:12.480 align:start position:0% then within the there's some sort of account<01:43:11.590> structure<01:43:11.830> that<01:43:12.010> gives<01:43:12.190> you<01:43:12.280> right 01:43:12.480 --> 01:43:12.490 align:start position:0% account structure that gives you right 01:43:12.490 --> 01:43:14.550 align:start position:0% account structure that gives you right to<01:43:12.730> like<01:43:12.910> access<01:43:13.390> it<01:43:13.540> with<01:43:13.660> a<01:43:13.690> maybe<01:43:14.050> a<01:43:14.350> year 01:43:14.550 --> 01:43:14.560 align:start position:0% to like access it with a maybe a year 01:43:14.560 --> 01:43:16.890 align:start position:0% to like access it with a maybe a year initially<01:43:15.280> transfer<01:43:15.670> another<01:43:15.850> ee<01:43:16.090> or<01:43:16.420> become 01:43:16.890 --> 01:43:16.900 align:start position:0% initially transfer another ee or become 01:43:16.900 --> 01:43:21.990 align:start position:0% initially transfer another ee or become abouthere<01:43:17.340> so<01:43:18.340> the<01:43:18.910> minting<01:43:19.510> of<01:43:20.880> outside<01:43:21.880> of 01:43:21.990 --> 01:43:22.000 align:start position:0% abouthere so the minting of outside of 01:43:22.000 --> 01:43:23.580 align:start position:0% abouthere so the minting of outside of the<01:43:22.120> normal<01:43:22.510> like<01:43:22.780> validation<01:43:23.140> mechanism 01:43:23.580 --> 01:43:23.590 align:start position:0% the normal like validation mechanism 01:43:23.590 --> 01:43:25.920 align:start position:0% the normal like validation mechanism would<01:43:24.370> be<01:43:24.580> a<01:43:24.610> like<01:43:25.120> that<01:43:25.450> would<01:43:25.540> be<01:43:25.630> a<01:43:25.660> layer 01:43:25.920 --> 01:43:25.930 align:start position:0% would be a like that would be a layer 01:43:25.930 --> 01:43:27.930 align:start position:0% would be a like that would be a layer one<01:43:26.170> protocol<01:43:26.680> bug<01:43:27.010> like<01:43:27.610> that<01:43:27.760> would<01:43:27.910> be 01:43:27.930 --> 01:43:27.940 align:start position:0% one protocol bug like that would be 01:43:27.940 --> 01:43:30.270 align:start position:0% one protocol bug like that would be something<01:43:28.600> that<01:43:28.750> the<01:43:29.380> like<01:43:29.620> kind<01:43:29.830> of<01:43:29.860> sandbox 01:43:30.270 --> 01:43:30.280 align:start position:0% something that the like kind of sandbox 01:43:30.280 --> 01:43:32.160 align:start position:0% something that the like kind of sandbox world<01:43:30.700> of<01:43:30.790> an<01:43:30.880> ee<01:43:31.000> which<01:43:31.360> is<01:43:31.480> just<01:43:31.660> blossom 01:43:32.160 --> 01:43:32.170 align:start position:0% world of an ee which is just blossom 01:43:32.170 --> 01:43:34.050 align:start position:0% world of an ee which is just blossom code<01:43:32.350> should<01:43:33.010> not<01:43:33.160> be<01:43:33.310> able<01:43:33.370> to<01:43:33.520> do<01:43:33.670> and<01:43:33.850> if<01:43:33.910> it 01:43:34.050 --> 01:43:34.060 align:start position:0% code should not be able to do and if it 01:43:34.060 --> 01:43:35.910 align:start position:0% code should not be able to do and if it did<01:43:34.300> like<01:43:34.600> that<01:43:34.750> would<01:43:34.960> be<01:43:35.080> a<01:43:35.110> layer<01:43:35.410> one<01:43:35.710> bug 01:43:35.910 --> 01:43:35.920 align:start position:0% did like that would be a layer one bug 01:43:35.920 --> 01:43:40.260 align:start position:0% did like that would be a layer one bug which<01:43:36.280> we<01:43:36.490> would<01:43:37.500> work<01:43:38.500> I<01:43:39.000> guess<01:43:40.000> the<01:43:40.120> question 01:43:40.260 --> 01:43:40.270 align:start position:0% which we would work I guess the question 01:43:40.270 --> 01:43:43.929 align:start position:0% which we would work I guess the question was<01:43:40.720> like<01:43:40.750> if<01:43:41.470> inside 01:43:43.929 --> 01:43:43.939 align:start position:0% was like if inside 01:43:43.939 --> 01:43:47.319 align:start position:0% was like if inside some<01:43:44.179> maintain<01:43:45.189> right<01:43:46.189> and<01:43:46.519> I'm<01:43:46.699> saying<01:43:46.939> it's 01:43:47.319 --> 01:43:47.329 align:start position:0% some maintain right and I'm saying it's 01:43:47.329 --> 01:43:50.049 align:start position:0% some maintain right and I'm saying it's not<01:43:47.419> possible<01:43:47.769> a<01:43:48.769> muster<01:43:49.429> or<01:43:49.579> a<01:43:49.610> bug<01:43:49.789> in<01:43:49.969> the 01:43:50.049 --> 01:43:50.059 align:start position:0% not possible a muster or a bug in the 01:43:50.059 --> 01:43:54.279 align:start position:0% not possible a muster or a bug in the lair<01:43:50.239> one<01:43:50.479> protocol<01:43:52.030> no<01:43:53.030> because<01:43:53.749> the<01:43:53.900> e<01:43:53.929> only 01:43:54.279 --> 01:43:54.289 align:start position:0% lair one protocol no because the e only 01:43:54.289 --> 01:43:56.859 align:start position:0% lair one protocol no because the e only has<01:43:54.559> access<01:43:54.769> to<01:43:55.070> the<01:43:55.639> east<01:43:55.939> that<01:43:56.209> is<01:43:56.269> in<01:43:56.689> its 01:43:56.859 --> 01:43:56.869 align:start position:0% has access to the east that is in its 01:43:56.869 --> 01:44:00.250 align:start position:0% has access to the east that is in its account<01:43:57.309> so<01:43:58.309> there's<01:43:58.939> 10<01:43:59.209> 8th<01:43:59.360> in<01:43:59.570> the<01:43:59.599> CV<01:44:00.050> and 01:44:00.250 --> 01:44:00.260 align:start position:0% account so there's 10 8th in the CV and 01:44:00.260 --> 01:44:02.169 align:start position:0% account so there's 10 8th in the CV and there's<01:44:00.860> some<01:44:01.070> sort<01:44:01.309> of<01:44:01.429> stuff<01:44:01.669> like<01:44:01.880> a<01:44:01.909> count 01:44:02.169 --> 01:44:02.179 align:start position:0% there's some sort of stuff like a count 01:44:02.179 --> 01:44:04.239 align:start position:0% there's some sort of stuff like a count model<01:44:02.479> that<01:44:02.659> allows<01:44:02.869> to<01:44:03.260> move<01:44:03.439> around<01:44:03.559> but 01:44:04.239 --> 01:44:04.249 align:start position:0% model that allows to move around but 01:44:04.249 --> 01:44:06.669 align:start position:0% model that allows to move around but nothing<01:44:04.550> nothing<01:44:05.179> that's<01:44:05.630> moved<01:44:06.110> within<01:44:06.380> that 01:44:06.669 --> 01:44:06.679 align:start position:0% nothing nothing that's moved within that 01:44:06.679 --> 01:44:08.589 align:start position:0% nothing nothing that's moved within that he<01:44:06.829> actually<01:44:07.280> changes<01:44:07.939> the<01:44:08.119> view<01:44:08.300> of<01:44:08.479> the 01:44:08.589 --> 01:44:08.599 align:start position:0% he actually changes the view of the 01:44:08.599 --> 01:44:10.689 align:start position:0% he actually changes the view of the amount<01:44:08.840> of<01:44:08.900> Heath<01:44:09.139> within<01:44:09.619> the<01:44:09.829> that's<01:44:10.519> why 01:44:10.689 --> 01:44:10.699 align:start position:0% amount of Heath within the that's why 01:44:10.699 --> 01:44:12.159 align:start position:0% amount of Heath within the that's why the<01:44:10.760> entire<01:44:11.090> one<01:44:11.329> protocol<01:44:11.659> but<01:44:11.840> it<01:44:11.959> might 01:44:12.159 --> 01:44:12.169 align:start position:0% the entire one protocol but it might 01:44:12.169 --> 01:44:14.679 align:start position:0% the entire one protocol but it might suddenly<01:44:12.499> hit<01:44:12.889> 11<01:44:13.249> e<01:44:13.550> if<01:44:13.669> inside<01:44:14.389> its 01:44:14.679 --> 01:44:14.689 align:start position:0% suddenly hit 11 e if inside its 01:44:14.689 --> 01:44:17.469 align:start position:0% suddenly hit 11 e if inside its internals<01:44:15.679> ago<01:44:15.919> and<01:44:16.130> I'm<01:44:16.249> saying<01:44:16.459> the<01:44:16.909> only 01:44:17.469 --> 01:44:17.479 align:start position:0% internals ago and I'm saying the only 01:44:17.479 --> 01:44:20.169 align:start position:0% internals ago and I'm saying the only way<01:44:17.659> that<01:44:17.689> that<01:44:18.139> is<01:44:18.349> possible<01:44:18.619> would<01:44:19.610> be<01:44:19.669> if 01:44:20.169 --> 01:44:20.179 align:start position:0% way that that is possible would be if 01:44:20.179 --> 01:44:22.239 align:start position:0% way that that is possible would be if there<01:44:20.419> was<01:44:20.570> a<01:44:20.599> bug<01:44:20.929> in<01:44:21.139> the<01:44:21.229> lair<01:44:21.469> one<01:44:21.739> protocol 01:44:22.239 --> 01:44:22.249 align:start position:0% there was a bug in the lair one protocol 01:44:22.249 --> 01:44:40.000 align:start position:0% there was a bug in the lair one protocol not<01:44:22.579> within<01:44:22.969> the<01:44:37.360> there's<01:44:38.360> 10<01:44:38.900> accounts<01:44:39.409> all 01:44:40.000 --> 01:44:40.010 align:start position:0% not within the there's 10 accounts all 01:44:40.010 --> 01:44:41.979 align:start position:0% not within the there's 10 accounts all of<01:44:40.070> them<01:44:40.340> have<01:44:40.550> money<01:44:40.820> except<01:44:41.659> one<01:44:41.809> of<01:44:41.900> them 01:44:41.979 --> 01:44:41.989 align:start position:0% of them have money except one of them 01:44:41.989 --> 01:44:44.409 align:start position:0% of them have money except one of them that's<01:44:42.110> two<01:44:42.349> and<01:44:42.650> so<01:44:42.829> but<01:44:43.489> in<01:44:43.880> terms<01:44:44.150> of<01:44:44.300> their 01:44:44.409 --> 01:44:44.419 align:start position:0% that's two and so but in terms of their 01:44:44.419 --> 01:44:46.870 align:start position:0% that's two and so but in terms of their right<01:44:44.689> to<01:44:44.719> that<01:44:45.110> that<01:44:45.530> model<01:44:45.889> within<01:44:46.369> look 01:44:46.870 --> 01:44:46.880 align:start position:0% right to that that model within look 01:44:46.880 --> 01:44:49.390 align:start position:0% right to that that model within look that<01:44:47.539> that<01:44:47.780> eath<01:44:47.959> within<01:44:48.380> the<01:44:48.499> actual<01:44:48.829> retired 01:44:49.390 --> 01:44:49.400 align:start position:0% that that eath within the actual retired 01:44:49.400 --> 01:44:51.069 align:start position:0% that that eath within the actual retired emulator<01:44:49.909> one<01:44:50.059> system<01:44:50.389> there's<01:44:50.659> no<01:44:50.719> there's 01:44:51.069 --> 01:44:51.079 align:start position:0% emulator one system there's no there's 01:44:51.079 --> 01:44:54.729 align:start position:0% emulator one system there's no there's only<01:44:51.229> ten<01:44:51.499> so<01:44:52.419> yeah<01:44:53.419> there<01:44:53.869> if<01:44:54.380> you<01:44:54.559> write 01:44:54.729 --> 01:44:54.739 align:start position:0% only ten so yeah there if you write 01:44:54.739 --> 01:44:56.500 align:start position:0% only ten so yeah there if you write baddies<01:44:55.159> you<01:44:55.550> can<01:44:55.669> have<01:44:55.789> a<01:44:55.849> terrible<01:44:56.090> user 01:44:56.500 --> 01:44:56.510 align:start position:0% baddies you can have a terrible user 01:44:56.510 --> 01:44:58.379 align:start position:0% baddies you can have a terrible user experience 01:44:58.379 --> 01:44:58.389 align:start position:0% experience 01:44:58.389 --> 01:45:00.159 align:start position:0% experience you<01:44:59.389> haven't<01:44:59.689> been<01:44:59.749> said<01:44:59.929> it<01:45:00.019> wouldn't 01:45:00.159 --> 01:45:00.169 align:start position:0% you haven't been said it wouldn't 01:45:00.169 --> 01:45:02.500 align:start position:0% you haven't been said it wouldn't respect<01:45:00.499> to<01:45:00.650> layer<01:45:00.800> one<01:45:01.269> there<01:45:02.269> are 01:45:02.500 --> 01:45:02.510 align:start position:0% respect to layer one there are 01:45:02.510 --> 01:45:03.879 align:start position:0% respect to layer one there are interesting<01:45:02.840> questions<01:45:02.929> with<01:45:03.380> respect<01:45:03.709> to 01:45:03.879 --> 01:45:03.889 align:start position:0% interesting questions with respect to 01:45:03.889 --> 01:45:07.439 align:start position:0% interesting questions with respect to like<01:45:04.219> an<01:45:04.340> exchange<01:45:04.550> that<01:45:04.999> my<01:45:05.119> honor<01:45:05.360> the<01:45:05.689> I 01:45:07.439 --> 01:45:07.449 align:start position:0% like an exchange that my honor the I 01:45:07.449 --> 01:45:13.000 align:start position:0% like an exchange that my honor the I think<01:45:08.449> the<01:45:08.719> way<01:45:08.840> to<01:45:08.869> think<01:45:09.019> about<01:45:09.320> it<01:45:11.409> is<01:45:12.409> to<01:45:12.469> I 01:45:13.000 --> 01:45:13.010 align:start position:0% think the way to think about it is to I 01:45:13.010 --> 01:45:17.350 align:start position:0% think the way to think about it is to I think<01:45:14.409> that<01:45:15.409> within<01:45:15.979> the<01:45:16.280> EU<01:45:16.669> no<01:45:16.969> longer 01:45:17.350 --> 01:45:17.360 align:start position:0% think that within the EU no longer 01:45:17.360 --> 01:45:19.330 align:start position:0% think that within the EU no longer entities<01:45:18.039> basically<01:45:19.039> you<01:45:19.159> have 01:45:19.330 --> 01:45:19.340 align:start position:0% entities basically you have 01:45:19.340 --> 01:45:20.799 align:start position:0% entities basically you have representation 01:45:20.799 --> 01:45:20.809 align:start position:0% representation 01:45:20.809 --> 01:45:38.450 align:start position:0% representation there's<01:45:21.809> a<01:45:21.900> disconnect<01:45:22.409> there<01:45:23.599> yeah<01:45:37.190> it<01:45:38.190> turns 01:45:38.450 --> 01:45:38.460 align:start position:0% there's a disconnect there yeah it turns 01:45:38.460 --> 01:45:41.120 align:start position:0% there's a disconnect there yeah it turns out<01:45:38.670> also<01:45:38.969> that<01:45:39.449> these<01:45:40.050> is<01:45:40.679> what<01:45:41.010> we're 01:45:41.120 --> 01:45:41.130 align:start position:0% out also that these is what we're 01:45:41.130 --> 01:45:42.530 align:start position:0% out also that these is what we're talking<01:45:41.309> about 01:45:42.530 --> 01:45:42.540 align:start position:0% talking about 01:45:42.540 --> 01:45:45.470 align:start position:0% talking about you<01:45:42.780> can<01:45:42.989> basically<01:45:43.170> build<01:45:43.710> a<01:45:44.040> knee<01:45:44.329> inside<01:45:45.329> of 01:45:45.470 --> 01:45:45.480 align:start position:0% you can basically build a knee inside of 01:45:45.480 --> 01:45:47.330 align:start position:0% you can basically build a knee inside of it<01:45:45.570> there<01:45:45.690> in<01:45:45.809> one<01:45:45.840> and<01:45:46.440> that<01:45:47.010> is<01:45:47.159> actually 01:45:47.330 --> 01:45:47.340 align:start position:0% it there in one and that is actually 01:45:47.340 --> 01:45:49.189 align:start position:0% it there in one and that is actually what<01:45:47.639> these<01:45:47.820> roll-up<01:45:48.150> chains<01:45:48.420> are<01:45:48.630> in<01:45:48.989> reality 01:45:49.189 --> 01:45:49.199 align:start position:0% what these roll-up chains are in reality 01:45:49.199 --> 01:45:51.770 align:start position:0% what these roll-up chains are in reality because<01:45:49.920> you<01:45:50.489> know<01:45:50.610> we<01:45:50.940> have<01:45:51.119> these<01:45:51.239> balances 01:45:51.770 --> 01:45:51.780 align:start position:0% because you know we have these balances 01:45:51.780 --> 01:45:54.229 align:start position:0% because you know we have these balances you<01:45:51.989> go<01:45:52.170> into<01:45:52.469> an<01:45:52.590> ee<01:45:52.829> one<01:45:53.670> of<01:45:53.820> these<01:45:53.969> rollup 01:45:54.229 --> 01:45:54.239 align:start position:0% you go into an ee one of these rollup 01:45:54.239 --> 01:45:56.810 align:start position:0% you go into an ee one of these rollup chains<01:45:54.630> and<01:45:54.929> then<01:45:55.260> you<01:45:55.889> know<01:45:56.010> inside<01:45:56.550> of<01:45:56.730> the 01:45:56.810 --> 01:45:56.820 align:start position:0% chains and then you know inside of the 01:45:56.820 --> 01:45:58.160 align:start position:0% chains and then you know inside of the role<01:45:56.969> of<01:45:57.000> chain<01:45:57.300> you<01:45:57.480> might<01:45:57.630> have<01:45:57.750> coded<01:45:58.050> it 01:45:58.160 --> 01:45:58.170 align:start position:0% role of chain you might have coded it 01:45:58.170 --> 01:45:59.510 align:start position:0% role of chain you might have coded it wrong<01:45:58.349> you<01:45:58.559> might<01:45:58.679> have<01:45:58.829> you<01:45:59.070> know<01:45:59.099> something 01:45:59.510 --> 01:45:59.520 align:start position:0% wrong you might have you know something 01:45:59.520 --> 01:46:01.490 align:start position:0% wrong you might have you know something you<01:46:00.090> know<01:46:00.119> someone<01:46:00.510> some<01:46:00.690> issue<01:46:00.869> happen<01:46:01.260> and 01:46:01.490 --> 01:46:01.500 align:start position:0% you know someone some issue happen and 01:46:01.500 --> 01:46:03.709 align:start position:0% you know someone some issue happen and you<01:46:01.920> go<01:46:02.070> out<01:46:02.219> and<01:46:02.400> it<01:46:02.579> turns<01:46:02.760> out<01:46:02.969> that<01:46:03.449> there 01:46:03.709 --> 01:46:03.719 align:start position:0% you go out and it turns out that there 01:46:03.719 --> 01:46:07.370 align:start position:0% you go out and it turns out that there is<01:46:03.750> like<01:46:04.079> a<01:46:04.290> very<01:46:05.040> very<01:46:05.639> kind<01:46:06.630> of<01:46:06.750> one-to-one 01:46:07.370 --> 01:46:07.380 align:start position:0% is like a very very kind of one-to-one 01:46:07.380 --> 01:46:09.830 align:start position:0% is like a very very kind of one-to-one correspondence<01:46:08.030> however<01:46:09.030> if<01:46:09.300> you<01:46:09.420> do<01:46:09.599> it<01:46:09.719> in 01:46:09.830 --> 01:46:09.840 align:start position:0% correspondence however if you do it in 01:46:09.840 --> 01:46:11.689 align:start position:0% correspondence however if you do it in each<01:46:09.989> one<01:46:10.020> there<01:46:10.800> are<01:46:10.980> certain<01:46:11.429> things<01:46:11.550> that 01:46:11.689 --> 01:46:11.699 align:start position:0% each one there are certain things that 01:46:11.699 --> 01:46:14.450 align:start position:0% each one there are certain things that you<01:46:11.820> can<01:46:12.119> know<01:46:12.840> you<01:46:13.500> of<01:46:13.860> course<01:46:14.040> we<01:46:14.219> don't<01:46:14.340> have 01:46:14.450 --> 01:46:14.460 align:start position:0% you can know you of course we don't have 01:46:14.460 --> 01:46:16.370 align:start position:0% you can know you of course we don't have the<01:46:14.670> scale<01:46:14.969> and<01:46:15.329> also<01:46:15.780> it's<01:46:15.929> much<01:46:16.199> less 01:46:16.370 --> 01:46:16.380 align:start position:0% the scale and also it's much less 01:46:16.380 --> 01:46:19.250 align:start position:0% the scale and also it's much less efficient<01:46:16.860> but<01:46:17.309> there<01:46:17.489> is<01:46:17.579> like<01:46:17.790> a<01:46:18.260> these 01:46:19.250 --> 01:46:19.260 align:start position:0% efficient but there is like a these 01:46:19.260 --> 01:46:23.479 align:start position:0% efficient but there is like a these concepts<01:46:19.800> are<01:46:20.630> and<01:46:21.630> it's<01:46:21.960> about<01:46:22.110> not<01:46:22.500> not<01:46:22.860> not 01:46:23.479 --> 01:46:23.489 align:start position:0% concepts are and it's about not not not 01:46:23.489 --> 01:46:29.990 align:start position:0% concepts are and it's about not not not a<01:46:25.880> special<01:46:27.829> and<01:46:28.829> they're<01:46:29.460> not<01:46:29.610> made<01:46:29.820> like 01:46:29.990 --> 01:46:30.000 align:start position:0% a special and they're not made like 01:46:30.000 --> 01:46:32.180 align:start position:0% a special and they're not made like insurance<01:46:30.360> anyway<01:46:30.780> I<01:46:31.020> want<01:46:31.829> how<01:46:31.889> to<01:46:31.920> know<01:46:32.159> I 01:46:32.180 --> 01:46:32.190 align:start position:0% insurance anyway I want how to know I 01:46:32.190 --> 01:46:34.850 align:start position:0% insurance anyway I want how to know I don't<01:46:32.429> know<01:46:32.610> what<01:46:32.760> I'm<01:46:32.880> trying<01:46:33.300> to<01:46:33.449> say<01:46:33.860> but 01:46:34.850 --> 01:46:34.860 align:start position:0% don't know what I'm trying to say but 01:46:34.860 --> 01:46:36.200 align:start position:0% don't know what I'm trying to say but thank<01:46:35.099> you<01:46:35.159> for<01:46:35.250> listening 01:46:36.200 --> 01:46:36.210 align:start position:0% thank you for listening 01:46:36.210 --> 01:46:42.939 align:start position:0% thank you for listening a<01:46:39.920> human<01:46:40.920> is<01:46:41.040> less<01:46:41.309> like<01:46:41.550> one<01:46:41.730> or<01:46:41.849> two 01:46:42.939 --> 01:46:42.949 align:start position:0% a human is less like one or two 01:46:42.949 --> 01:46:46.339 align:start position:0% a human is less like one or two does<01:46:43.949> anybody<01:46:44.190> that<01:46:44.550> hasn't<01:46:44.849> spoken<01:46:45.300> yet<01:46:45.480> want 01:46:46.339 --> 01:46:46.349 align:start position:0% does anybody that hasn't spoken yet want 01:46:46.349 --> 01:46:49.430 align:start position:0% does anybody that hasn't spoken yet want to<01:46:46.500> speak<01:46:46.710> up<01:46:47.869> their<01:46:48.869> last<01:46:49.110> chance 01:46:49.430 --> 01:46:49.440 align:start position:0% to speak up their last chance 01:46:49.440 --> 01:46:54.480 align:start position:0% to speak up their last chance transformation 01:46:54.480 --> 01:46:54.490 align:start position:0% 01:46:54.490 --> 01:46:57.700 align:start position:0% so<01:46:55.490> my<01:46:55.760> understanding<01:46:55.910> about<01:46:56.390> ease<01:46:56.960> is<01:46:57.440> very 01:46:57.700 --> 01:46:57.710 align:start position:0% so my understanding about ease is very 01:46:57.710 --> 01:47:02.560 align:start position:0% so my understanding about ease is very rudimentary<01:47:00.400> Daan's<01:47:01.400> beacon<01:47:02.390> chain 01:47:02.560 --> 01:47:02.570 align:start position:0% rudimentary Daan's beacon chain 01:47:02.570 --> 01:47:04.000 align:start position:0% rudimentary Daan's beacon chain validators<01:47:03.050> catch<01:47:03.350> the<01:47:03.560> bug 01:47:04.000 --> 01:47:04.010 align:start position:0% validators catch the bug 01:47:04.010 --> 01:47:06.400 align:start position:0% validators catch the bug I<01:47:04.040> keep<01:47:04.370> there's<01:47:04.610> a<01:47:04.670> there's<01:47:05.510> a<01:47:05.570> bug<01:47:06.140> he's<01:47:06.260> an 01:47:06.400 --> 01:47:06.410 align:start position:0% I keep there's a there's a bug he's an 01:47:06.410 --> 01:47:08.860 align:start position:0% I keep there's a there's a bug he's an EE<01:47:06.590> which<01:47:07.510> inflates 01:47:08.860 --> 01:47:08.870 align:start position:0% EE which inflates 01:47:08.870 --> 01:47:13.090 align:start position:0% EE which inflates the<01:47:09.250> rapt<01:47:10.250> ether<01:47:10.610> or<01:47:11.300> the<01:47:11.570> EE<01:47:11.780> ether<01:47:12.320> within 01:47:13.090 --> 01:47:13.100 align:start position:0% the rapt ether or the EE ether within 01:47:13.100 --> 01:47:14.650 align:start position:0% the rapt ether or the EE ether within that<01:47:13.220> contract<01:47:13.610> shouldn't<01:47:14.030> they<01:47:14.210> just<01:47:14.270> say 01:47:14.650 --> 01:47:14.660 align:start position:0% that contract shouldn't they just say 01:47:14.660 --> 01:47:16.720 align:start position:0% that contract shouldn't they just say that<01:47:14.870> oh<01:47:15.650> there's<01:47:15.950> a<01:47:16.040> bug<01:47:16.250> they're<01:47:16.490> just 01:47:16.720 --> 01:47:16.730 align:start position:0% that oh there's a bug they're just 01:47:16.730 --> 01:47:20.380 align:start position:0% that oh there's a bug they're just trying<01:47:16.970> to<01:47:17.080> inflate<01:47:18.080> the<01:47:18.320> their<01:47:19.130> own<01:47:19.390> intercom 01:47:20.380 --> 01:47:20.390 align:start position:0% trying to inflate the their own intercom 01:47:20.390 --> 01:47:23.400 align:start position:0% trying to inflate the their own intercom thing<01:47:20.600> and<01:47:20.810> just<01:47:21.050> not<01:47:21.350> execute<01:47:22.010> that<01:47:22.220> that 01:47:23.400 --> 01:47:23.410 align:start position:0% thing and just not execute that that 01:47:23.410 --> 01:47:35.950 align:start position:0% thing and just not execute that that that<01:47:24.410> you<01:47:24.650> state<01:47:24.920> that's<01:47:25.580> the<01:47:25.970> proposes<01:47:34.960> yeah 01:47:35.950 --> 01:47:35.960 align:start position:0% that you state that's the proposes yeah 01:47:35.960 --> 01:47:40.330 align:start position:0% that you state that's the proposes yeah the<01:47:36.730> beacon<01:47:37.730> chain<01:47:38.080> would<01:47:39.080> catch<01:47:39.470> its 01:47:40.330 --> 01:47:40.340 align:start position:0% the beacon chain would catch its 01:47:40.340 --> 01:47:42.430 align:start position:0% the beacon chain would catch its validators<01:47:40.790> don't<01:47:41.000> actually<01:47:41.180> have<01:47:41.480> you<01:47:42.320> know 01:47:42.430 --> 01:47:42.440 align:start position:0% validators don't actually have you know 01:47:42.440 --> 01:47:44.380 align:start position:0% validators don't actually have you know go<01:47:42.950> from<01:47:43.190> 10<01:47:43.370> to<01:47:43.640> 11 01:47:44.380 --> 01:47:44.390 align:start position:0% go from 10 to 11 01:47:44.390 --> 01:47:48.910 align:start position:0% go from 10 to 11 he's<01:47:44.870> out<01:47:45.470> of<01:47:45.500> nowhere<01:47:46.030> but<01:47:47.030> if<01:47:47.900> the<01:47:48.140> EE<01:47:48.350> you 01:47:48.910 --> 01:47:48.920 align:start position:0% he's out of nowhere but if the EE you 01:47:48.920 --> 01:47:51.040 align:start position:0% he's out of nowhere but if the EE you know<01:47:49.040> has<01:47:49.250> a<01:47:49.280> feel<01:47:49.760> under<01:47:50.180> its<01:47:50.300> own<01:47:50.390> state<01:47:50.720> that 01:47:51.040 --> 01:47:51.050 align:start position:0% know has a feel under its own state that 01:47:51.050 --> 01:47:53.380 align:start position:0% know has a feel under its own state that says<01:47:51.560> wrapped<01:47:51.980> either<01:47:52.370> and<01:47:52.790> it<01:47:52.940> doesn't<01:47:53.210> check 01:47:53.380 --> 01:47:53.390 align:start position:0% says wrapped either and it doesn't check 01:47:53.390 --> 01:47:56.560 align:start position:0% says wrapped either and it doesn't check like<01:47:53.800> guarantee<01:47:54.800> that<01:47:55.010> rep<01:47:55.640> ether<01:47:56.000> amount<01:47:56.300> is 01:47:56.560 --> 01:47:56.570 align:start position:0% like guarantee that rep ether amount is 01:47:56.570 --> 01:48:00.460 align:start position:0% like guarantee that rep ether amount is equal<01:47:56.780> to<01:47:57.140> the<01:47:57.710> actual<01:47:57.860> ether<01:47:58.340> amount<01:47:59.470> you 01:48:00.460 --> 01:48:00.470 align:start position:0% equal to the actual ether amount you 01:48:00.470 --> 01:48:04.090 align:start position:0% equal to the actual ether amount you know<01:48:00.560> in<01:48:00.740> the<01:48:00.920> beacon<01:48:01.310> State<01:48:01.580> field<01:48:01.790> then<01:48:03.100> that 01:48:04.090 --> 01:48:04.100 align:start position:0% know in the beacon State field then that 01:48:04.100 --> 01:48:07.330 align:start position:0% know in the beacon State field then that E's<01:48:04.310> you<01:48:05.030> know<01:48:05.150> rapt<01:48:05.540> ether<01:48:05.750> balance<01:48:06.680> and<01:48:07.190> just 01:48:07.330 --> 01:48:07.340 align:start position:0% E's you know rapt ether balance and just 01:48:07.340 --> 01:48:09.850 align:start position:0% E's you know rapt ether balance and just a<01:48:07.490> plate<01:48:07.730> just<01:48:07.760> like<01:48:08.120> a<01:48:08.150> contract<01:48:08.630> anyone<01:48:09.110> the 01:48:09.850 --> 01:48:09.860 align:start position:0% a plate just like a contract anyone the 01:48:09.860 --> 01:48:12.880 align:start position:0% a plate just like a contract anyone the RAB<01:48:10.070> ether<01:48:10.460> doesn't<01:48:11.300> have<01:48:11.420> to<01:48:11.540> be<01:48:12.350> equal<01:48:12.710> to 01:48:12.880 --> 01:48:12.890 align:start position:0% RAB ether doesn't have to be equal to 01:48:12.890 --> 01:48:14.830 align:start position:0% RAB ether doesn't have to be equal to these<01:48:13.640> are<01:48:13.940> if<01:48:14.150> there's<01:48:14.390> book<01:48:14.600> in<01:48:14.720> the 01:48:14.830 --> 01:48:14.840 align:start position:0% these are if there's book in the 01:48:14.840 --> 01:48:17.170 align:start position:0% these are if there's book in the contract<01:48:15.260> okay<01:48:16.070> so<01:48:16.280> so<01:48:16.670> beacon<01:48:17.030> chief 01:48:17.170 --> 01:48:17.180 align:start position:0% contract okay so so beacon chief 01:48:17.180 --> 01:48:18.760 align:start position:0% contract okay so so beacon chief elevators<01:48:17.660> are<01:48:17.840> not<01:48:18.020> really<01:48:18.230> looking<01:48:18.500> out<01:48:18.620> for 01:48:18.760 --> 01:48:18.770 align:start position:0% elevators are not really looking out for 01:48:18.770 --> 01:48:20.490 align:start position:0% elevators are not really looking out for this<01:48:19.040> these<01:48:19.520> kind<01:48:19.790> of<01:48:19.850> issues 01:48:20.490 --> 01:48:20.500 align:start position:0% this these kind of issues 01:48:20.500 --> 01:48:23.350 align:start position:0% this these kind of issues I'm<01:48:21.500> learning<01:48:21.770> the<01:48:21.980> part<01:48:22.850> of<01:48:22.910> this<01:48:23.000> may<01:48:23.120> look 01:48:23.350 --> 01:48:23.360 align:start position:0% I'm learning the part of this may look 01:48:23.360 --> 01:48:25.500 align:start position:0% I'm learning the part of this may look like<01:48:23.570> part<01:48:23.810> of<01:48:23.840> the<01:48:23.930> system<01:48:24.260> is<01:48:24.380> such<01:48:24.620> that<01:48:24.650> and 01:48:25.500 --> 01:48:25.510 align:start position:0% like part of the system is such that and 01:48:25.510 --> 01:48:27.850 align:start position:0% like part of the system is such that and part<01:48:26.510> of<01:48:26.540> the<01:48:26.630> backbone<01:48:27.260> of<01:48:27.350> the<01:48:27.470> stateless 01:48:27.850 --> 01:48:27.860 align:start position:0% part of the backbone of the stateless 01:48:27.860 --> 01:48:30.520 align:start position:0% part of the backbone of the stateless system<01:48:28.250> the<01:48:28.790> validators<01:48:29.420> don't<01:48:29.750> have<01:48:30.080> to<01:48:30.290> know 01:48:30.520 --> 01:48:30.530 align:start position:0% system the validators don't have to know 01:48:30.530 --> 01:48:34.120 align:start position:0% system the validators don't have to know about<01:48:31.630> they<01:48:32.630> know<01:48:32.840> that<01:48:33.230> the 01:48:34.120 --> 01:48:34.130 align:start position:0% about they know that the 01:48:34.130 --> 01:48:36.430 align:start position:0% about they know that the they<01:48:34.639> know<01:48:34.820> that<01:48:35.120> given<01:48:35.780> a<01:48:35.840> block<01:48:36.080> they<01:48:36.290> can 01:48:36.430 --> 01:48:36.440 align:start position:0% they know that given a block they can 01:48:36.440 --> 01:48:38.379 align:start position:0% they know that given a block they can execute<01:48:36.710> on<01:48:37.070> three<01:48:37.340> state<01:48:37.580> route<01:48:37.760> the<01:48:38.179> block 01:48:38.379 --> 01:48:38.389 align:start position:0% execute on three state route the block 01:48:38.389 --> 01:48:39.970 align:start position:0% execute on three state route the block and<01:48:38.600> post<01:48:38.840> a<01:48:39.020> group<01:48:39.230> but<01:48:39.620> they<01:48:39.679> don't<01:48:39.860> take 01:48:39.970 --> 01:48:39.980 align:start position:0% and post a group but they don't take 01:48:39.980 --> 01:48:42.490 align:start position:0% and post a group but they don't take care<01:48:40.159> about<01:48:40.340> the<01:48:40.580> internals<01:48:41.060> to<01:48:41.750> validate<01:48:42.350> the 01:48:42.490 --> 01:48:42.500 align:start position:0% care about the internals to validate the 01:48:42.500 --> 01:48:46.000 align:start position:0% care about the internals to validate the protocol<01:48:42.889> and<01:48:43.250> if<01:48:43.400> they<01:48:43.580> did<01:48:44.469> this<01:48:45.469> this<01:48:45.830> is 01:48:46.000 --> 01:48:46.010 align:start position:0% protocol and if they did this this is 01:48:46.010 --> 01:48:47.200 align:start position:0% protocol and if they did this this is someone<01:48:46.190> likely<01:48:46.340> to<01:48:46.489> be<01:48:46.610> much<01:48:46.820> much<01:48:47.150> less 01:48:47.200 --> 01:48:47.210 align:start position:0% someone likely to be much much less 01:48:47.210 --> 01:48:48.399 align:start position:0% someone likely to be much much less scalable<01:48:47.540> because<01:48:47.960> they'd<01:48:48.080> have<01:48:48.199> to<01:48:48.290> know 01:48:48.399 --> 01:48:48.409 align:start position:0% scalable because they'd have to know 01:48:48.409 --> 01:48:52.060 align:start position:0% scalable because they'd have to know about<01:48:48.880> arbitrary<01:48:49.880> E's<01:48:50.330> that<01:48:50.600> existed<01:48:51.350> so<01:48:51.920> it's 01:48:52.060 --> 01:48:52.070 align:start position:0% about arbitrary E's that existed so it's 01:48:52.070 --> 01:48:54.879 align:start position:0% about arbitrary E's that existed so it's kind<01:48:52.520> of<01:48:52.550> like<01:48:52.719> definitely<01:48:53.719> segmented<01:48:54.710> in<01:48:54.800> a 01:48:54.879 --> 01:48:54.889 align:start position:0% kind of like definitely segmented in a 01:48:54.889 --> 01:48:57.100 align:start position:0% kind of like definitely segmented in a way<01:48:55.010> that<01:48:55.250> the<01:48:55.550> validating<01:48:56.389> participants 01:48:57.100 --> 01:48:57.110 align:start position:0% way that the validating participants 01:48:57.110 --> 01:48:59.080 align:start position:0% way that the validating participants don't<01:48:57.290> have<01:48:57.560> to<01:48:57.770> worry<01:48:58.429> about<01:48:58.520> the<01:48:58.699> internals 01:48:59.080 --> 01:48:59.090 align:start position:0% don't have to worry about the internals 01:48:59.090 --> 01:49:01.870 align:start position:0% don't have to worry about the internals and<01:48:59.120> thus<01:48:59.360> would<01:48:59.960> not<01:49:00.170> catch<01:49:01.159> that<01:49:01.400> like<01:49:01.639> part 01:49:01.870 --> 01:49:01.880 align:start position:0% and thus would not catch that like part 01:49:01.880 --> 01:49:03.189 align:start position:0% and thus would not catch that like part of<01:49:01.969> the<01:49:02.060> protocol<01:49:02.389> is<01:49:02.480> just<01:49:02.630> execute<01:49:02.989> the<01:49:03.080> code 01:49:03.189 --> 01:49:03.199 align:start position:0% of the protocol is just execute the code 01:49:03.199 --> 01:49:05.919 align:start position:0% of the protocol is just execute the code of<01:49:03.350> the<01:49:03.409> EE<01:49:03.560> not<01:49:03.949> to<01:49:04.280> look<01:49:05.270> at<01:49:05.360> the<01:49:05.449> he<01:49:05.630> and<01:49:05.810> be 01:49:05.919 --> 01:49:05.929 align:start position:0% of the EE not to look at the he and be 01:49:05.929 --> 01:49:09.280 align:start position:0% of the EE not to look at the he and be like<01:49:06.110> does<01:49:06.290> that<01:49:06.469> make<01:49:06.650> sense<01:49:07.929> it's<01:49:08.929> just<01:49:08.989> like 01:49:09.280 --> 01:49:09.290 align:start position:0% like does that make sense it's just like 01:49:09.290 --> 01:49:11.890 align:start position:0% like does that make sense it's just like thank<01:49:09.500> you<01:49:09.650> in<01:49:09.860> these<01:49:10.130> one<01:49:10.370> bucks<01:49:10.610> you<01:49:11.270> know<01:49:11.389> - 01:49:11.890 --> 01:49:11.900 align:start position:0% thank you in these one bucks you know - 01:49:11.900 --> 01:49:21.209 align:start position:0% thank you in these one bucks you know - just<01:49:12.139> from<01:49:12.320> DBM<01:49:12.739> code<01:49:14.590> thank<01:49:15.590> you<01:49:18.699> all<01:49:19.699> right 01:49:21.209 --> 01:49:21.219 align:start position:0% just from DBM code thank you all right 01:49:21.219 --> 01:49:31.600 align:start position:0% just from DBM code thank you all right buddy<01:49:22.219> house<01:49:22.370> that<01:49:22.550> hasn't<01:49:30.340> this<01:49:31.340> is<01:49:31.489> a 01:49:31.600 --> 01:49:31.610 align:start position:0% buddy house that hasn't this is a 01:49:31.610 --> 01:49:35.260 align:start position:0% buddy house that hasn't this is a challenge<01:49:31.969> and<01:49:32.120> researchers<01:49:32.659> here 01:49:35.260 --> 01:49:35.270 align:start position:0% 01:49:35.270 --> 01:49:36.980 align:start position:0% [Music] 01:49:36.980 --> 01:49:36.990 align:start position:0% [Music] 01:49:36.990 --> 01:49:40.290 align:start position:0% [Music] maybe<01:49:37.990> one<01:49:38.380> question<01:49:38.560> adding<01:49:39.040> to<01:49:39.160> this<01:49:39.250> so<01:49:40.090> now 01:49:40.290 --> 01:49:40.300 align:start position:0% maybe one question adding to this so now 01:49:40.300 --> 01:49:42.300 align:start position:0% maybe one question adding to this so now it<01:49:40.540> has<01:49:40.570> a<01:49:40.690> deep<01:49:40.930> develop<01:49:41.380> but<01:49:41.560> I<01:49:41.590> know<01:49:41.710> and<01:49:42.070> you 01:49:42.300 --> 01:49:42.310 align:start position:0% it has a deep develop but I know and you 01:49:42.310 --> 01:49:44.250 align:start position:0% it has a deep develop but I know and you have<01:49:42.520> to<01:49:42.550> trust<01:49:42.880> like<01:49:43.180> if<01:49:43.540> you<01:49:43.720> don't<01:49:44.020> change 01:49:44.250 --> 01:49:44.260 align:start position:0% have to trust like if you don't change 01:49:44.260 --> 01:49:50.580 align:start position:0% have to trust like if you don't change what<01:49:44.470> I<01:49:44.530> have<01:49:44.860> to<01:49:45.010> trust<01:49:48.840> so<01:49:49.840> they<01:49:50.110> can<01:49:50.410> help 01:49:50.580 --> 01:49:50.590 align:start position:0% what I have to trust so they can help 01:49:50.590 --> 01:49:54.450 align:start position:0% what I have to trust so they can help our<01:49:51.630> rookies<01:49:52.660> yeah<01:49:53.080> isn't<01:49:53.320> that<01:49:53.470> e<01:49:53.830> if<01:49:54.220> you're 01:49:54.450 --> 01:49:54.460 align:start position:0% our rookies yeah isn't that e if you're 01:49:54.460 --> 01:49:57.060 align:start position:0% our rookies yeah isn't that e if you're gonna<01:49:54.580> run<01:49:54.790> any<01:49:55.030> it<01:49:55.720> should<01:49:56.020> be<01:49:56.170> well<01:49:56.830> vetted 01:49:57.060 --> 01:49:57.070 align:start position:0% gonna run any it should be well vetted 01:49:57.070 --> 01:49:59.010 align:start position:0% gonna run any it should be well vetted it<01:49:57.490> should<01:49:57.670> be<01:49:57.760> before<01:49:58.060> my<01:49:58.180> verified<01:49:58.660> and<01:49:58.930> it 01:49:59.010 --> 01:49:59.020 align:start position:0% it should be before my verified and it 01:49:59.020 --> 01:50:00.660 align:start position:0% it should be before my verified and it should<01:49:59.200> be<01:49:59.290> something<01:49:59.980> that<01:50:00.010> like<01:50:00.340> makes 01:50:00.660 --> 01:50:00.670 align:start position:0% should be something that like makes 01:50:00.670 --> 01:50:03.290 align:start position:0% should be something that like makes sense<01:50:00.910> for<01:50:01.030> you<01:50:01.150> to<01:50:01.240> actually<01:50:01.420> operate<01:50:01.720> I 01:50:03.290 --> 01:50:03.300 align:start position:0% sense for you to actually operate I 01:50:03.300 --> 01:50:05.610 align:start position:0% sense for you to actually operate I expect<01:50:04.300> a<01:50:04.420> lot<01:50:04.570> of<01:50:04.750> activity<01:50:05.350> that<01:50:05.380> have 01:50:05.610 --> 01:50:05.620 align:start position:0% expect a lot of activity that have 01:50:05.620 --> 01:50:08.490 align:start position:0% expect a lot of activity that have happened<01:50:06.010> on<01:50:06.250> large<01:50:07.180> well<01:50:07.600> vetted<01:50:07.840> well<01:50:08.230> to 01:50:08.490 --> 01:50:08.500 align:start position:0% happened on large well vetted well to 01:50:08.500 --> 01:50:12.450 align:start position:0% happened on large well vetted well to Louise<01:50:10.380> even<01:50:11.380> if<01:50:11.500> there's<01:50:11.710> experimentation 01:50:12.450 --> 01:50:12.460 align:start position:0% Louise even if there's experimentation 01:50:12.460 --> 01:50:15.120 align:start position:0% Louise even if there's experimentation with<01:50:12.610> all<01:50:12.760> sorts<01:50:13.030> of<01:50:13.090> others<01:50:13.390> but<01:50:14.020> also<01:50:14.830> that's 01:50:15.120 --> 01:50:15.130 align:start position:0% with all sorts of others but also that's 01:50:15.130 --> 01:50:16.980 align:start position:0% with all sorts of others but also that's it<01:50:15.340> sounds<01:50:15.550> cool<01:50:15.820> I<01:50:16.090> mean<01:50:16.330> at<01:50:16.540> the<01:50:16.630> moment<01:50:16.660> you 01:50:16.980 --> 01:50:16.990 align:start position:0% it sounds cool I mean at the moment you 01:50:16.990 --> 01:50:19.200 align:start position:0% it sounds cool I mean at the moment you need<01:50:17.140> to<01:50:17.290> trust<01:50:17.620> easier<01:50:18.460> bought<01:50:18.670> a<01:50:18.850> know<01:50:19.120> the 01:50:19.200 --> 01:50:19.210 align:start position:0% need to trust easier bought a know the 01:50:19.210 --> 01:50:21.480 align:start position:0% need to trust easier bought a know the GBM<01:50:19.510> me<01:50:20.170> the<01:50:20.290> EVM<01:50:20.560> is<01:50:20.710> execution<01:50:21.070> apartment 01:50:21.480 --> 01:50:21.490 align:start position:0% GBM me the EVM is execution apartment 01:50:21.490 --> 01:50:24.930 align:start position:0% GBM me the EVM is execution apartment it's<01:50:22.090> a<01:50:22.150> sensible<01:50:23.430> you<01:50:24.430> don't<01:50:24.580> want<01:50:24.760> to<01:50:24.820> make 01:50:24.930 --> 01:50:24.940 align:start position:0% it's a sensible you don't want to make 01:50:24.940 --> 01:50:27.690 align:start position:0% it's a sensible you don't want to make sure<01:50:24.970> that<01:50:25.450> the<01:50:25.960> safe<01:50:26.530> I'm<01:50:26.830> just<01:50:27.310> speaking<01:50:27.550> to 01:50:27.690 --> 01:50:27.700 align:start position:0% sure that the safe I'm just speaking to 01:50:27.700 --> 01:50:35.100 align:start position:0% sure that the safe I'm just speaking to like<01:50:28.620> p.m.<01:50:29.620> because<01:50:33.690> right<01:50:34.690> now<01:50:34.810> there's<01:50:35.050> a 01:50:35.100 --> 01:50:35.110 align:start position:0% like p.m. because right now there's a 01:50:35.110 --> 01:50:38.370 align:start position:0% like p.m. because right now there's a bug<01:50:35.440> right<01:50:35.830> now<01:50:36.040> in<01:50:36.430> the<01:50:36.970> UVM<01:50:37.360> we<01:50:38.110> might 01:50:38.370 --> 01:50:38.380 align:start position:0% bug right now in the UVM we might 01:50:38.380 --> 01:50:40.380 align:start position:0% bug right now in the UVM we might socially<01:50:39.370> coordinate<01:50:39.730> to<01:50:39.850> fix<01:50:40.060> it 01:50:40.380 --> 01:50:40.390 align:start position:0% socially coordinate to fix it 01:50:40.390 --> 01:50:42.030 align:start position:0% socially coordinate to fix it whereas<01:50:40.630> if<01:50:40.900> there<01:50:41.110> was<01:50:41.200> a<01:50:41.230> bug<01:50:41.440> in<01:50:41.470> a<01:50:41.710> random 01:50:42.030 --> 01:50:42.040 align:start position:0% whereas if there was a bug in a random 01:50:42.040 --> 01:50:44.840 align:start position:0% whereas if there was a bug in a random EE<01:50:42.160> we're<01:50:42.880> very<01:50:43.120> low<01:50:43.300> likely<01:50:43.930> wouldn't<01:50:44.260> really 01:50:44.840 --> 01:50:44.850 align:start position:0% EE we're very low likely wouldn't really 01:50:44.850 --> 01:51:12.090 align:start position:0% EE we're very low likely wouldn't really well 01:51:12.090 --> 01:51:12.100 align:start position:0% 01:51:12.100 --> 01:51:24.480 align:start position:0% [Music] 01:51:24.480 --> 01:51:24.490 align:start position:0% 01:51:24.490 --> 01:51:31.030 align:start position:0% [Music] 01:51:31.030 --> 01:51:31.040 align:start position:0% 01:51:31.040 --> 01:51:35.570 align:start position:0% great<01:51:32.040> question<01:51:32.430> so<01:51:34.100> optimistic<01:51:35.100> roll-up<01:51:35.370> the 01:51:35.570 --> 01:51:35.580 align:start position:0% great question so optimistic roll-up the 01:51:35.580 --> 01:51:36.890 align:start position:0% great question so optimistic roll-up the biggest<01:51:36.000> thing<01:51:36.240> that<01:51:36.270> I<01:51:36.570> like<01:51:36.870> about 01:51:36.890 --> 01:51:36.900 align:start position:0% biggest thing that I like about 01:51:36.900 --> 01:51:39.140 align:start position:0% biggest thing that I like about optimistic<01:51:37.620> role<01:51:37.770> is<01:51:37.980> that<01:51:38.250> we<01:51:38.550> can<01:51:38.730> have<01:51:38.940> the 01:51:39.140 --> 01:51:39.150 align:start position:0% optimistic role is that we can have the 01:51:39.150 --> 01:51:41.060 align:start position:0% optimistic role is that we can have the same<01:51:39.360> developer<01:51:39.570> experience<01:51:40.290> like<01:51:40.380> as<01:51:40.590> as 01:51:41.060 --> 01:51:41.070 align:start position:0% same developer experience like as as 01:51:41.070 --> 01:51:43.070 align:start position:0% same developer experience like as as similar<01:51:41.730> and<01:51:41.910> the<01:51:42.120> kinds<01:51:42.450> of<01:51:42.510> changes<01:51:42.690> that 01:51:43.070 --> 01:51:43.080 align:start position:0% similar and the kinds of changes that 01:51:43.080 --> 01:51:44.780 align:start position:0% similar and the kinds of changes that Danny<01:51:43.320> was<01:51:43.500> talking<01:51:43.530> about<01:51:43.830> the<01:51:44.370> block<01:51:44.580> gap 01:51:44.780 --> 01:51:44.790 align:start position:0% Danny was talking about the block gap 01:51:44.790 --> 01:51:46.610 align:start position:0% Danny was talking about the block gap you<01:51:45.000> know<01:51:45.090> block<01:51:45.360> difficulty<01:51:45.960> and<01:51:46.350> you<01:51:46.500> know 01:51:46.610 --> 01:51:46.620 align:start position:0% you know block difficulty and you know 01:51:46.620 --> 01:51:48.050 align:start position:0% you know block difficulty and you know we<01:51:46.890> have<01:51:47.010> to<01:51:47.130> change<01:51:47.340> at<01:51:47.610> mean<01:51:47.760> you<01:51:47.970> know 01:51:48.050 --> 01:51:48.060 align:start position:0% we have to change at mean you know 01:51:48.060 --> 01:51:49.850 align:start position:0% we have to change at mean you know message<01:51:48.360> sender<01:51:48.930> we<01:51:49.080> have<01:51:49.320> to<01:51:49.470> do<01:51:49.560> a<01:51:49.590> count 01:51:49.850 --> 01:51:49.860 align:start position:0% message sender we have to do a count 01:51:49.860 --> 01:51:51.440 align:start position:0% message sender we have to do a count abstraction<01:51:50.340> it's<01:51:50.490> just<01:51:50.700> some<01:51:51.180> weird 01:51:51.440 --> 01:51:51.450 align:start position:0% abstraction it's just some weird 01:51:51.450 --> 01:51:53.690 align:start position:0% abstraction it's just some weird requirements<01:51:52.350> a<01:51:52.500> couple<01:51:53.310> things<01:51:53.490> will<01:51:53.670> change 01:51:53.690 --> 01:51:53.700 align:start position:0% requirements a couple things will change 01:51:53.700 --> 01:51:55.880 align:start position:0% requirements a couple things will change but<01:51:54.120> your<01:51:54.510> smart<01:51:54.810> contracts<01:51:55.200> will<01:51:55.410> work<01:51:55.620> kind 01:51:55.880 --> 01:51:55.890 align:start position:0% but your smart contracts will work kind 01:51:55.890 --> 01:51:58.190 align:start position:0% but your smart contracts will work kind of<01:51:55.950> as<01:51:56.130> they<01:51:56.400> do<01:51:56.460> today<01:51:56.910> and<01:51:57.240> then<01:51:57.750> you<01:51:57.990> know 01:51:58.190 --> 01:51:58.200 align:start position:0% of as they do today and then you know 01:51:58.200 --> 01:52:00.920 align:start position:0% of as they do today and then you know basically<01:51:58.830> would<01:51:59.010> require<01:51:59.370> forking<01:51:59.970> or<01:52:00.270> you 01:52:00.920 --> 01:52:00.930 align:start position:0% basically would require forking or you 01:52:00.930 --> 01:52:03.940 align:start position:0% basically would require forking or you know<01:52:01.050> forking<01:52:01.590> waffle<01:52:02.250> truffle<01:52:02.790> whatever<01:52:03.330> and 01:52:03.940 --> 01:52:03.950 align:start position:0% know forking waffle truffle whatever and 01:52:03.950 --> 01:52:06.590 align:start position:0% know forking waffle truffle whatever and you<01:52:04.950> know<01:52:05.070> adding<01:52:05.460> in<01:52:05.610> the<01:52:05.760> kind<01:52:05.970> of<01:52:06.030> little 01:52:06.590 --> 01:52:06.600 align:start position:0% you know adding in the kind of little 01:52:06.600 --> 01:52:08.570 align:start position:0% you know adding in the kind of little changes<01:52:07.050> but<01:52:07.500> you<01:52:07.530> would<01:52:07.830> you<01:52:08.160> know<01:52:08.280> write<01:52:08.550> a 01:52:08.570 --> 01:52:08.580 align:start position:0% changes but you would you know write a 01:52:08.580 --> 01:52:10.400 align:start position:0% changes but you would you know write a smart<01:52:08.910> contract<01:52:09.060> deploy<01:52:09.840> the<01:52:09.990> smart<01:52:10.260> contract 01:52:10.400 --> 01:52:10.410 align:start position:0% smart contract deploy the smart contract 01:52:10.410 --> 01:52:13.100 align:start position:0% smart contract deploy the smart contract and<01:52:10.980> you'd<01:52:11.100> have<01:52:11.310> a<01:52:11.640> you<01:52:12.210> know<01:52:12.240> quote<01:52:12.600> etherium 01:52:13.100 --> 01:52:13.110 align:start position:0% and you'd have a you know quote etherium 01:52:13.110 --> 01:52:17.270 align:start position:0% and you'd have a you know quote etherium unstoppable<01:52:13.860> smart<01:52:14.250> contract<01:52:15.950> you<01:52:16.950> know<01:52:17.070> in 01:52:17.270 --> 01:52:17.280 align:start position:0% unstoppable smart contract you know in 01:52:17.280 --> 01:52:18.980 align:start position:0% unstoppable smart contract you know in layer<01:52:17.580> two<01:52:17.820> and<01:52:18.060> then<01:52:18.300> that's<01:52:18.570> definitely 01:52:18.980 --> 01:52:18.990 align:start position:0% layer two and then that's definitely 01:52:18.990 --> 01:52:21.260 align:start position:0% layer two and then that's definitely that's<01:52:19.290> definitely<01:52:19.440> a<01:52:19.800> goal<01:52:20.190> a<01:52:20.430> goal<01:52:20.610> for<01:52:21.120> all 01:52:21.260 --> 01:52:21.270 align:start position:0% that's definitely a goal a goal for all 01:52:21.270 --> 01:52:29.160 align:start position:0% that's definitely a goal a goal for all of<01:52:21.300> us<01:52:21.420> I<01:52:21.740> have<01:52:22.740> a<01:52:22.800> question 01:52:29.160 --> 01:52:29.170 align:start position:0% 01:52:29.170 --> 01:52:32.790 align:start position:0% absolutely<01:52:29.800> yes<01:52:30.010> so<01:52:30.640> metallic<01:52:31.150> has<01:52:31.680> given<01:52:32.680> me 01:52:32.790 --> 01:52:32.800 align:start position:0% absolutely yes so metallic has given me 01:52:32.800 --> 01:52:34.140 align:start position:0% absolutely yes so metallic has given me and<01:52:33.280> he<01:52:33.370> gave<01:52:33.490> me<01:52:33.550> this<01:52:33.760> like<01:52:33.940> crazy 01:52:34.140 --> 01:52:34.150 align:start position:0% and he gave me this like crazy 01:52:34.150 --> 01:52:36.480 align:start position:0% and he gave me this like crazy mind-blowing<01:52:34.690> experience<01:52:35.280> where<01:52:36.280> he<01:52:36.310> was 01:52:36.480 --> 01:52:36.490 align:start position:0% mind-blowing experience where he was 01:52:36.490 --> 01:52:38.280 align:start position:0% mind-blowing experience where he was talking<01:52:36.670> about<01:52:36.700> he<01:52:36.880> was<01:52:36.970> like<01:52:37.090> okay<01:52:37.480> you<01:52:37.900> can 01:52:38.280 --> 01:52:38.290 align:start position:0% talking about he was like okay you can 01:52:38.290 --> 01:52:40.830 align:start position:0% talking about he was like okay you can think<01:52:38.530> of<01:52:38.620> optimistic<01:52:39.250> Rollem<01:52:39.580> as<01:52:39.840> different 01:52:40.830 --> 01:52:40.840 align:start position:0% think of optimistic Rollem as different 01:52:40.840 --> 01:52:44.490 align:start position:0% think of optimistic Rollem as different like<01:52:41.020> execution<01:52:41.890> zones<01:52:42.220> so<01:52:42.910> the<01:52:43.390> the<01:52:44.020> deeper 01:52:44.490 --> 01:52:44.500 align:start position:0% like execution zones so the the deeper 01:52:44.500 --> 01:52:46.530 align:start position:0% like execution zones so the the deeper you<01:52:44.650> get<01:52:44.890> in<01:52:45.160> this<01:52:45.310> recursive<01:52:45.700> optimistic 01:52:46.530 --> 01:52:46.540 align:start position:0% you get in this recursive optimistic 01:52:46.540 --> 01:52:48.660 align:start position:0% you get in this recursive optimistic roll-up<01:52:46.870> thing<01:52:47.080> the<01:52:47.530> more<01:52:47.800> execution 01:52:48.660 --> 01:52:48.670 align:start position:0% roll-up thing the more execution 01:52:48.670 --> 01:52:50.310 align:start position:0% roll-up thing the more execution computational<01:52:49.510> that<01:52:49.630> you<01:52:49.720> have<01:52:49.990> to<01:52:50.170> do 01:52:50.310 --> 01:52:50.320 align:start position:0% computational that you have to do 01:52:50.320 --> 01:52:51.630 align:start position:0% computational that you have to do because<01:52:50.530> you<01:52:50.740> have<01:52:50.830> to<01:52:50.950> do<01:52:51.070> the<01:52:51.370> the 01:52:51.630 --> 01:52:51.640 align:start position:0% because you have to do the the 01:52:51.640 --> 01:52:53.300 align:start position:0% because you have to do the the optimistic<01:52:52.390> role<01:52:52.690> of<01:52:52.750> at<01:52:52.840> the<01:52:52.930> bottom<01:52:53.140> level 01:52:53.300 --> 01:52:53.310 align:start position:0% optimistic role of at the bottom level 01:52:53.310 --> 01:52:55.290 align:start position:0% optimistic role of at the bottom level optimistic<01:52:54.310> role<01:52:54.430> of<01:52:54.550> above<01:52:54.760> an<01:52:54.910> optimistic 01:52:55.290 --> 01:52:55.300 align:start position:0% optimistic role of above an optimistic 01:52:55.300 --> 01:52:56.730 align:start position:0% optimistic role of above an optimistic world<01:52:55.450> above<01:52:55.750> about<01:52:56.050> you<01:52:56.200> know<01:52:56.320> and<01:52:56.470> then<01:52:56.590> up 01:52:56.730 --> 01:52:56.740 align:start position:0% world above about you know and then up 01:52:56.740 --> 01:52:58.290 align:start position:0% world above about you know and then up to<01:52:56.890> the<01:52:56.920> main<01:52:57.130> chain<01:52:57.370> so<01:52:57.820> it's<01:52:58.000> like<01:52:58.150> the 01:52:58.290 --> 01:52:58.300 align:start position:0% to the main chain so it's like the 01:52:58.300 --> 01:53:00.420 align:start position:0% to the main chain so it's like the massive<01:52:58.570> amount<01:52:59.110> of<01:52:59.230> computation<01:52:59.830> but<01:53:00.220> that 01:53:00.420 --> 01:53:00.430 align:start position:0% massive amount of computation but that 01:53:00.430 --> 01:53:01.980 align:start position:0% massive amount of computation but that gives<01:53:00.640> you<01:53:00.850> scale<01:53:01.210> right<01:53:01.510> because<01:53:01.810> you're 01:53:01.980 --> 01:53:01.990 align:start position:0% gives you scale right because you're 01:53:01.990 --> 01:53:03.870 align:start position:0% gives you scale right because you're you're<01:53:02.290> doing<01:53:02.620> more<01:53:02.950> compute<01:53:03.340> that<01:53:03.490> means<01:53:03.700> you 01:53:03.870 --> 01:53:03.880 align:start position:0% you're doing more compute that means you 01:53:03.880 --> 01:53:05.340 align:start position:0% you're doing more compute that means you can<01:53:04.060> scale<01:53:04.300> further<01:53:04.600> and<01:53:04.870> so<01:53:05.140> you<01:53:05.200> can 01:53:05.340 --> 01:53:05.350 align:start position:0% can scale further and so you can 01:53:05.350 --> 01:53:07.140 align:start position:0% can scale further and so you can actually<01:53:05.500> you<01:53:05.890> can<01:53:05.920> even<01:53:06.130> design<01:53:06.430> a<01:53:06.610> system 01:53:07.140 --> 01:53:07.150 align:start position:0% actually you can even design a system 01:53:07.150 --> 01:53:08.580 align:start position:0% actually you can even design a system where<01:53:07.570> you're<01:53:07.720> like<01:53:07.930> doing<01:53:08.350> this 01:53:08.580 --> 01:53:08.590 align:start position:0% where you're like doing this 01:53:08.590 --> 01:53:10.170 align:start position:0% where you're like doing this intentionally<01:53:08.920> were<01:53:09.340> you<01:53:09.460> segmenting 01:53:10.170 --> 01:53:10.180 align:start position:0% intentionally were you segmenting 01:53:10.180 --> 01:53:13.680 align:start position:0% intentionally were you segmenting different<01:53:10.570> levels<01:53:11.020> of<01:53:11.290> you<01:53:12.250> know<01:53:12.280> here's<01:53:12.690> the 01:53:13.680 --> 01:53:13.690 align:start position:0% different levels of you know here's the 01:53:13.690 --> 01:53:15.840 align:start position:0% different levels of you know here's the deepest<01:53:14.350> level<01:53:14.740> and<01:53:14.980> you<01:53:15.190> know<01:53:15.250> you<01:53:15.490> you<01:53:15.700> have 01:53:15.840 --> 01:53:15.850 align:start position:0% deepest level and you know you you have 01:53:15.850 --> 01:53:18.000 align:start position:0% deepest level and you know you you have some<01:53:16.060> some<01:53:16.720> amount<01:53:17.020> of<01:53:17.110> death<01:53:17.260> anyway<01:53:17.620> I<01:53:17.890> don't 01:53:18.000 --> 01:53:18.010 align:start position:0% some some amount of death anyway I don't 01:53:18.010 --> 01:53:19.380 align:start position:0% some some amount of death anyway I don't think<01:53:18.250> that<01:53:18.370> that's<01:53:18.490> like<01:53:18.730> really<01:53:19.060> that 01:53:19.380 --> 01:53:19.390 align:start position:0% think that that's like really that 01:53:19.390 --> 01:53:21.300 align:start position:0% think that that's like really that practical<01:53:19.960> I<01:53:20.080> think<01:53:20.290> will<01:53:20.380> again<01:53:20.590> like<01:53:20.800> one 01:53:21.300 --> 01:53:21.310 align:start position:0% practical I think will again like one 01:53:21.310 --> 01:53:23.970 align:start position:0% practical I think will again like one level<01:53:21.550> deep<01:53:21.910> and<01:53:22.210> we'll<01:53:22.540> probably<01:53:22.750> get<01:53:23.170> 90%<01:53:23.590> of 01:53:23.970 --> 01:53:23.980 align:start position:0% level deep and we'll probably get 90% of 01:53:23.980 --> 01:53:25.920 align:start position:0% level deep and we'll probably get 90% of the<01:53:24.070> way<01:53:24.160> there<01:53:24.480> 99%<01:53:25.480> of<01:53:25.510> the<01:53:25.600> way<01:53:25.690> there<01:53:25.900> and 01:53:25.920 --> 01:53:25.930 align:start position:0% the way there 99% of the way there and 01:53:25.930 --> 01:53:27.810 align:start position:0% the way there 99% of the way there and then<01:53:26.140> maybe<01:53:26.650> throw<01:53:26.950> another<01:53:27.190> level<01:53:27.490> because 01:53:27.810 --> 01:53:27.820 align:start position:0% then maybe throw another level because 01:53:27.820 --> 01:53:31.950 align:start position:0% then maybe throw another level because we're<01:53:28.180> like<01:53:28.390> crazy<01:53:29.700> but<01:53:30.700> you<01:53:31.030> know<01:53:31.150> we<01:53:31.360> can<01:53:31.570> and 01:53:31.950 --> 01:53:31.960 align:start position:0% we're like crazy but you know we can and 01:53:31.960 --> 01:53:33.930 align:start position:0% we're like crazy but you know we can and we<01:53:32.260> could<01:53:32.530> and<01:53:32.800> that's<01:53:33.100> kind<01:53:33.400> of<01:53:33.460> that's<01:53:33.820> I 01:53:33.930 --> 01:53:33.940 align:start position:0% we could and that's kind of that's I 01:53:33.940 --> 01:53:35.700 align:start position:0% we could and that's kind of that's I think<01:53:34.060> the<01:53:34.330> big<01:53:34.720> thing<01:53:34.750> that<01:53:34.960> I<01:53:35.080> was<01:53:35.260> you<01:53:35.680> know 01:53:35.700 --> 01:53:35.710 align:start position:0% think the big thing that I was you know 01:53:35.710 --> 01:53:37.770 align:start position:0% think the big thing that I was you know I<01:53:36.040> thought<01:53:36.370> I<01:53:36.430> really<01:53:36.970> want<01:53:37.180> to<01:53:37.300> communicate 01:53:37.770 --> 01:53:37.780 align:start position:0% I thought I really want to communicate 01:53:37.780 --> 01:53:40.800 align:start position:0% I thought I really want to communicate is<01:53:37.960> that<01:53:38.320> the<01:53:38.890> EVM<01:53:39.400> as<01:53:39.730> it<01:53:39.910> is<01:53:40.060> is<01:53:40.360> this<01:53:40.570> like 01:53:40.800 --> 01:53:40.810 align:start position:0% is that the EVM as it is is this like 01:53:40.810 --> 01:53:42.540 align:start position:0% is that the EVM as it is is this like Turing<01:53:41.260> complete<01:53:41.590> state<01:53:41.830> machine<01:53:42.130> and<01:53:42.370> we 01:53:42.540 --> 01:53:42.550 align:start position:0% Turing complete state machine and we 01:53:42.550 --> 01:53:44.370 align:start position:0% Turing complete state machine and we should<01:53:42.670> all<01:53:42.880> be<01:53:42.910> like<01:53:43.240> incredibly<01:53:43.990> grateful 01:53:44.370 --> 01:53:44.380 align:start position:0% should all be like incredibly grateful 01:53:44.380 --> 01:53:46.890 align:start position:0% should all be like incredibly grateful for<01:53:44.560> the<01:53:45.070> fact<01:53:45.280> how<01:53:45.700> general-purpose<01:53:46.540> it 01:53:46.890 --> 01:53:46.900 align:start position:0% for the fact how general-purpose it 01:53:46.900 --> 01:53:48.300 align:start position:0% for the fact how general-purpose it convenience<01:53:47.350> so<01:53:47.440> you<01:53:47.470> can<01:53:47.680> write<01:53:47.920> these 01:53:48.300 --> 01:53:48.310 align:start position:0% convenience so you can write these 01:53:48.310 --> 01:53:50.430 align:start position:0% convenience so you can write these amazing<01:53:48.970> systems<01:53:49.420> like<01:53:49.870> execution 01:53:50.430 --> 01:53:50.440 align:start position:0% amazing systems like execution 01:53:50.440 --> 01:53:51.990 align:start position:0% amazing systems like execution environments<01:53:50.890> like<01:53:50.980> optimistic<01:53:51.580> rolled<01:53:51.790> and 01:53:51.990 --> 01:53:52.000 align:start position:0% environments like optimistic rolled and 01:53:52.000 --> 01:53:53.850 align:start position:0% environments like optimistic rolled and then<01:53:52.330> you<01:53:52.450> can<01:53:52.630> write<01:53:52.810> those<01:53:53.080> systems<01:53:53.530> inside 01:53:53.850 --> 01:53:53.860 align:start position:0% then you can write those systems inside 01:53:53.860 --> 01:53:56.040 align:start position:0% then you can write those systems inside of<01:53:54.040> themselves<01:53:54.430> and<01:53:54.640> this<01:53:55.090> computation<01:53:55.810> stuff 01:53:56.040 --> 01:53:56.050 align:start position:0% of themselves and this computation stuff 01:53:56.050 --> 01:53:57.810 align:start position:0% of themselves and this computation stuff that<01:53:56.230> we're<01:53:56.350> dealing<01:53:56.530> with<01:53:56.710> is<01:53:57.010> pretty<01:53:57.250> wacky 01:53:57.810 --> 01:53:57.820 align:start position:0% that we're dealing with is pretty wacky 01:53:57.820 --> 01:54:02.640 align:start position:0% that we're dealing with is pretty wacky so<01:53:58.750> I<01:53:58.780> I<01:53:58.870> definitely<01:53:59.590> definitely<01:54:00.190> enjoy<01:54:01.650> all 01:54:02.640 --> 01:54:02.650 align:start position:0% so I I definitely definitely enjoy all 01:54:02.650 --> 01:54:04.720 align:start position:0% so I I definitely definitely enjoy all right<01:54:02.800> I<01:54:03.010> think 01:54:04.720 --> 01:54:04.730 align:start position:0% right I think 01:54:04.730 --> 01:54:11.140 align:start position:0% right I think they're<01:54:07.390> beautiful<01:54:08.390> words<01:54:10.150> general-purpose 01:54:11.140 --> 01:54:11.150 align:start position:0% they're beautiful words general-purpose 01:54:11.150 --> 01:54:15.520 align:start position:0% they're beautiful words general-purpose computing<01:54:13.300> as<01:54:14.300> you<01:54:14.450> may<01:54:14.600> have<01:54:14.630> noticed<01:54:14.780> during 01:54:15.520 --> 01:54:15.530 align:start position:0% computing as you may have noticed during 01:54:15.530 --> 01:54:17.790 align:start position:0% computing as you may have noticed during this<01:54:15.770> session<01:54:15.980> so<01:54:16.490> very<01:54:16.790> very<01:54:17.060> early<01:54:17.510> stages 01:54:17.790 --> 01:54:17.800 align:start position:0% this session so very very early stages 01:54:17.800 --> 01:54:21.130 align:start position:0% this session so very very early stages that<01:54:18.800> means<01:54:19.040> opportunities<01:54:19.940> to<01:54:20.600> thank<01:54:20.870> you 01:54:21.130 --> 01:54:21.140 align:start position:0% that means opportunities to thank you 01:54:21.140 --> 01:54:22.750 align:start position:0% that means opportunities to thank you where<01:54:21.320> we<01:54:21.440> go<01:54:21.590> with<01:54:21.740> the<01:54:21.890> system<01:54:22.310> it<01:54:22.610> also 01:54:22.750 --> 01:54:22.760 align:start position:0% where we go with the system it also 01:54:22.760 --> 01:54:25.540 align:start position:0% where we go with the system it also means<01:54:23.150> that<01:54:23.330> like<01:54:23.810> it's<01:54:24.020> not<01:54:24.170> ready<01:54:24.560> for<01:54:24.890> EM 01:54:25.540 --> 01:54:25.550 align:start position:0% means that like it's not ready for EM 01:54:25.550 --> 01:54:28.570 align:start position:0% means that like it's not ready for EM user<01:54:26.320> developers<01:54:27.320> or<01:54:27.560> end-user<01:54:27.770> applications 01:54:28.570 --> 01:54:28.580 align:start position:0% user developers or end-user applications 01:54:28.580 --> 01:54:30.060 align:start position:0% user developers or end-user applications yet 01:54:30.060 --> 01:54:30.070 align:start position:0% yet 01:54:30.070 --> 01:54:32.820 align:start position:0% yet however<01:54:31.070> I<01:54:31.190> would<01:54:31.340> encourage<01:54:31.820> you<01:54:32.060> to<01:54:32.090> join 01:54:32.820 --> 01:54:32.830 align:start position:0% however I would encourage you to join 01:54:32.830 --> 01:54:35.800 align:start position:0% however I would encourage you to join the<01:54:33.830> conversation<01:54:34.010> now<01:54:34.760> I<01:54:35.030> would<01:54:35.600> encourage 01:54:35.800 --> 01:54:35.810 align:start position:0% the conversation now I would encourage 01:54:35.810 --> 01:54:38.200 align:start position:0% the conversation now I would encourage you<01:54:36.050> to<01:54:36.080> explore<01:54:36.530> these<01:54:36.830> new<01:54:36.890> tools<01:54:37.340> and<01:54:37.730> think 01:54:38.200 --> 01:54:38.210 align:start position:0% you to explore these new tools and think 01:54:38.210 --> 01:54:42.700 align:start position:0% you to explore these new tools and think of<01:54:38.360> ways<01:54:38.540> that<01:54:38.780> we<01:54:38.900> used<01:54:40.210> once 01:54:42.700 --> 01:54:42.710 align:start position:0% of ways that we used once 01:54:42.710 --> 01:54:51.780 align:start position:0% of ways that we used once [Music] 01:54:51.780 --> 01:54:51.790 align:start position:0% 01:54:51.790 --> 01:54:56.239 align:start position:0% [Applause]