WEBVTT Kind: captions Language: en 00:00:04.620 --> 00:00:15.789 align:start position:0% [Music] 00:00:15.789 --> 00:00:15.799 align:start position:0% 00:00:15.799 --> 00:00:17.230 align:start position:0% so<00:00:16.000> what<00:00:16.080> I<00:00:16.160> wanted<00:00:16.359> to<00:00:16.600> so<00:00:16.760> what<00:00:16.880> I'm<00:00:17.000> planning 00:00:17.230 --> 00:00:17.240 align:start position:0% so what I wanted to so what I'm planning 00:00:17.240 --> 00:00:20.550 align:start position:0% so what I wanted to so what I'm planning on<00:00:17.439> talking<00:00:17.800> about<00:00:18.080> today<00:00:18.680> is<00:00:19.560> basically 00:00:20.550 --> 00:00:20.560 align:start position:0% on talking about today is basically 00:00:20.560 --> 00:00:24.269 align:start position:0% on talking about today is basically scalability<00:00:21.880> and<00:00:22.880> particularly<00:00:23.640> some<00:00:23.840> of<00:00:24.080> the 00:00:24.269 --> 00:00:24.279 align:start position:0% scalability and particularly some of the 00:00:24.279 --> 00:00:26.310 align:start position:0% scalability and particularly some of the more<00:00:24.519> detailed<00:00:25.119> implications<00:00:25.840> that<00:00:26.039> this<00:00:26.160> is 00:00:26.310 --> 00:00:26.320 align:start position:0% more detailed implications that this is 00:00:26.320 --> 00:00:28.790 align:start position:0% more detailed implications that this is going<00:00:26.480> to<00:00:26.760> have<00:00:27.119> for<00:00:28.039> how<00:00:28.279> ethereum 00:00:28.790 --> 00:00:28.800 align:start position:0% going to have for how ethereum 00:00:28.800 --> 00:00:30.189 align:start position:0% going to have for how ethereum developers<00:00:29.160> are<00:00:29.279> going<00:00:29.400> to<00:00:29.519> write<00:00:29.640> their<00:00:29.759> cont 00:00:30.189 --> 00:00:30.199 align:start position:0% developers are going to write their cont 00:00:30.199 --> 00:00:32.630 align:start position:0% developers are going to write their cont contracts<00:00:31.199> so<00:00:31.720> we've<00:00:31.960> already<00:00:32.160> talked<00:00:32.439> about 00:00:32.630 --> 00:00:32.640 align:start position:0% contracts so we've already talked about 00:00:32.640 --> 00:00:34.389 align:start position:0% contracts so we've already talked about scalability<00:00:33.320> quite<00:00:33.440> a<00:00:33.600> lot<00:00:33.800> this<00:00:33.920> morning<00:00:34.200> for 00:00:34.389 --> 00:00:34.399 align:start position:0% scalability quite a lot this morning for 00:00:34.399 --> 00:00:36.790 align:start position:0% scalability quite a lot this morning for about<00:00:34.559> an<00:00:34.719> hour<00:00:35.160> we've<00:00:35.600> uh<00:00:36.200> talked<00:00:36.480> about 00:00:36.790 --> 00:00:36.800 align:start position:0% about an hour we've uh talked about 00:00:36.800 --> 00:00:39.590 align:start position:0% about an hour we've uh talked about Casper<00:00:37.399> consensus<00:00:38.079> problems<00:00:38.960> some<00:00:39.120> of<00:00:39.320> the 00:00:39.590 --> 00:00:39.600 align:start position:0% Casper consensus problems some of the 00:00:39.600 --> 00:00:42.590 align:start position:0% Casper consensus problems some of the issues<00:00:40.280> that<00:00:40.800> making<00:00:41.480> ethereum<00:00:42.039> scale<00:00:42.399> is 00:00:42.590 --> 00:00:42.600 align:start position:0% issues that making ethereum scale is 00:00:42.600 --> 00:00:45.790 align:start position:0% issues that making ethereum scale is necessarily<00:00:43.160> going<00:00:43.320> to<00:00:43.800> entail<00:00:44.800> so<00:00:45.480> you<00:00:45.600> know 00:00:45.790 --> 00:00:45.800 align:start position:0% necessarily going to entail so you know 00:00:45.800 --> 00:00:47.750 align:start position:0% necessarily going to entail so you know just<00:00:45.960> to<00:00:46.120> sort<00:00:46.239> of<00:00:46.399> recap<00:00:46.800> all<00:00:46.879> of<00:00:47.039> that<00:00:47.239> very 00:00:47.750 --> 00:00:47.760 align:start position:0% just to sort of recap all of that very 00:00:47.760 --> 00:00:51.229 align:start position:0% just to sort of recap all of that very quickly<00:00:48.760> ethereum<00:00:49.320> right<00:00:49.480> now<00:00:50.160> every<00:00:50.399> single 00:00:51.229 --> 00:00:51.239 align:start position:0% quickly ethereum right now every single 00:00:51.239 --> 00:00:52.670 align:start position:0% quickly ethereum right now every single computer<00:00:51.640> in<00:00:51.719> the<00:00:51.840> ethereum<00:00:52.239> network 00:00:52.670 --> 00:00:52.680 align:start position:0% computer in the ethereum network 00:00:52.680 --> 00:00:54.830 align:start position:0% computer in the ethereum network processes<00:00:53.160> every<00:00:53.399> transaction<00:00:54.359> every<00:00:54.520> single 00:00:54.830 --> 00:00:54.840 align:start position:0% processes every transaction every single 00:00:54.840 --> 00:00:56.069 align:start position:0% processes every transaction every single computer<00:00:55.120> in<00:00:55.239> the<00:00:55.320> ethereum<00:00:55.719> network 00:00:56.069 --> 00:00:56.079 align:start position:0% computer in the ethereum network 00:00:56.079 --> 00:00:59.150 align:start position:0% computer in the ethereum network maintains<00:00:56.520> the<00:00:56.680> entire<00:00:57.239> State<00:00:58.239> and<00:00:58.800> that<00:00:58.920> is 00:00:59.150 --> 00:00:59.160 align:start position:0% maintains the entire State and that is 00:00:59.160 --> 00:01:03.670 align:start position:0% maintains the entire State and that is very<00:00:59.480> slow<00:00:59.960> so<00:01:00.920> on<00:01:01.239> the<00:01:02.039> Olympic<00:01:02.879> test<00:01:03.199> debt<00:01:03.480> we 00:01:03.670 --> 00:01:03.680 align:start position:0% very slow so on the Olympic test debt we 00:01:03.680 --> 00:01:06.830 align:start position:0% very slow so on the Olympic test debt we achieved<00:01:04.280> a<00:01:04.640> an<00:01:04.879> impressive<00:01:05.560> 20<00:01:06.159> transactions 00:01:06.830 --> 00:01:06.840 align:start position:0% achieved a an impressive 20 transactions 00:01:06.840 --> 00:01:07.870 align:start position:0% achieved a an impressive 20 transactions per 00:01:07.870 --> 00:01:07.880 align:start position:0% per 00:01:07.880 --> 00:01:10.070 align:start position:0% per second<00:01:08.880> which<00:01:09.040> I<00:01:09.200> believe<00:01:09.439> is<00:01:09.640> roughly<00:01:09.920> what 00:01:10.070 --> 00:01:10.080 align:start position:0% second which I believe is roughly what 00:01:10.080 --> 00:01:11.870 align:start position:0% second which I believe is roughly what normal<00:01:10.400> computers<00:01:10.759> were<00:01:10.920> able<00:01:11.119> to<00:01:11.240> do<00:01:11.479> at<00:01:11.640> some 00:01:11.870 --> 00:01:11.880 align:start position:0% normal computers were able to do at some 00:01:11.880 --> 00:01:13.350 align:start position:0% normal computers were able to do at some point<00:01:12.159> in<00:01:12.240> the 00:01:13.350 --> 00:01:13.360 align:start position:0% point in the 00:01:13.360 --> 00:01:15.390 align:start position:0% point in the 1980s 00:01:15.390 --> 00:01:15.400 align:start position:0% 1980s 00:01:15.400 --> 00:01:18.789 align:start position:0% 1980s so<00:01:16.400> yeah<00:01:16.920> but<00:01:17.280> unlike<00:01:17.759> nearly<00:01:18.159> all<00:01:18.439> other 00:01:18.789 --> 00:01:18.799 align:start position:0% so yeah but unlike nearly all other 00:01:18.799 --> 00:01:21.670 align:start position:0% so yeah but unlike nearly all other systems<00:01:19.280> in<00:01:19.400> the<00:01:19.560> real<00:01:19.960> world<00:01:20.960> this<00:01:21.119> also<00:01:21.479> does 00:01:21.670 --> 00:01:21.680 align:start position:0% systems in the real world this also does 00:01:21.680 --> 00:01:23.910 align:start position:0% systems in the real world this also does not<00:01:21.920> get<00:01:22.119> more<00:01:22.360> powerful<00:01:23.280> the<00:01:23.400> more<00:01:23.560> nodes 00:01:23.910 --> 00:01:23.920 align:start position:0% not get more powerful the more nodes 00:01:23.920 --> 00:01:26.190 align:start position:0% not get more powerful the more nodes join<00:01:24.159> the<00:01:24.280> network<00:01:24.680> surprisingly<00:01:25.320> enough<00:01:26.040> in 00:01:26.190 --> 00:01:26.200 align:start position:0% join the network surprisingly enough in 00:01:26.200 --> 00:01:27.990 align:start position:0% join the network surprisingly enough in fact<00:01:26.439> it<00:01:26.680> actually<00:01:27.040> should<00:01:27.320> get<00:01:27.520> slightly 00:01:27.990 --> 00:01:28.000 align:start position:0% fact it actually should get slightly 00:01:28.000 --> 00:01:29.350 align:start position:0% fact it actually should get slightly less<00:01:28.240> powerful<00:01:28.720> with<00:01:28.799> the<00:01:28.920> universal 00:01:29.350 --> 00:01:29.360 align:start position:0% less powerful with the universal 00:01:29.360 --> 00:01:32.190 align:start position:0% less powerful with the universal logarithm<00:01:29.720> of<00:01:29.960> the<00:01:30.040> size<00:01:30.240> of<00:01:30.360> the<00:01:30.479> network<00:01:31.400> but 00:01:32.190 --> 00:01:32.200 align:start position:0% logarithm of the size of the network but 00:01:32.200 --> 00:01:34.510 align:start position:0% logarithm of the size of the network but the<00:01:32.320> basic<00:01:32.640> reason<00:01:33.000> is<00:01:33.640> if<00:01:33.759> you<00:01:33.880> have<00:01:34.079> 10<00:01:34.280> times 00:01:34.510 --> 00:01:34.520 align:start position:0% the basic reason is if you have 10 times 00:01:34.520 --> 00:01:35.870 align:start position:0% the basic reason is if you have 10 times more<00:01:34.680> nodes<00:01:35.079> guess<00:01:35.320> what<00:01:35.439> each<00:01:35.600> and<00:01:35.720> every 00:01:35.870 --> 00:01:35.880 align:start position:0% more nodes guess what each and every 00:01:35.880 --> 00:01:37.749 align:start position:0% more nodes guess what each and every node<00:01:36.159> still<00:01:36.520> processes<00:01:37.119> processes<00:01:37.560> every 00:01:37.749 --> 00:01:37.759 align:start position:0% node still processes processes every 00:01:37.759 --> 00:01:39.190 align:start position:0% node still processes processes every transaction<00:01:38.320> you<00:01:38.439> still<00:01:38.680> are<00:01:38.880> where<00:01:39.000> you 00:01:39.190 --> 00:01:39.200 align:start position:0% transaction you still are where you 00:01:39.200 --> 00:01:41.069 align:start position:0% transaction you still are where you started<00:01:39.759> you<00:01:39.920> just<00:01:40.119> have<00:01:40.280> even<00:01:40.439> more<00:01:40.640> in 00:01:41.069 --> 00:01:41.079 align:start position:0% started you just have even more in 00:01:41.079 --> 00:01:44.830 align:start position:0% started you just have even more in efficiency<00:01:42.280> so<00:01:43.280> the<00:01:43.439> basic<00:01:43.720> vision<00:01:44.000> for<00:01:44.159> 2.0 00:01:44.830 --> 00:01:44.840 align:start position:0% efficiency so the basic vision for 2.0 00:01:44.840 --> 00:01:47.590 align:start position:0% efficiency so the basic vision for 2.0 is<00:01:45.040> this<00:01:45.240> concept<00:01:45.560> of<00:01:45.680> sharting<00:01:46.520> so<00:01:47.159> instead 00:01:47.590 --> 00:01:47.600 align:start position:0% is this concept of sharting so instead 00:01:47.600 --> 00:01:50.190 align:start position:0% is this concept of sharting so instead of<00:01:47.920> having<00:01:48.320> one<00:01:48.640> Global<00:01:49.079> State<00:01:49.640> that's<00:01:49.840> seen 00:01:50.190 --> 00:01:50.200 align:start position:0% of having one Global State that's seen 00:01:50.200 --> 00:01:53.109 align:start position:0% of having one Global State that's seen by<00:01:50.399> absolutely<00:01:51.000> everyone<00:01:52.000> you<00:01:52.640> it's<00:01:52.880> you 00:01:53.109 --> 00:01:53.119 align:start position:0% by absolutely everyone you it's you 00:01:53.119 --> 00:01:54.789 align:start position:0% by absolutely everyone you it's you split<00:01:53.479> the<00:01:53.600> state<00:01:53.880> up<00:01:54.079> into<00:01:54.360> these<00:01:54.520> sort<00:01:54.640> of 00:01:54.789 --> 00:01:54.799 align:start position:0% split the state up into these sort of 00:01:54.799 --> 00:01:58.149 align:start position:0% split the state up into these sort of chunks<00:01:55.119> that<00:01:55.240> you<00:01:55.320> can<00:01:55.520> call<00:01:56.119> shards<00:01:57.119> and<00:01:58.000> each 00:01:58.149 --> 00:01:58.159 align:start position:0% chunks that you can call shards and each 00:01:58.159 --> 00:01:59.510 align:start position:0% chunks that you can call shards and each of<00:01:58.320> these<00:01:58.439> shards<00:01:58.799> is<00:01:58.920> going<00:01:59.039> to<00:01:59.159> contain<00:01:59.399> its 00:01:59.510 --> 00:01:59.520 align:start position:0% of these shards is going to contain its 00:01:59.520 --> 00:02:01.670 align:start position:0% of these shards is going to contain its own<00:01:59.880> state<00:02:00.320> so<00:02:00.479> you<00:02:00.560> can<00:02:00.719> imagine<00:02:01.119> each<00:02:01.280> Shard 00:02:01.670 --> 00:02:01.680 align:start position:0% own state so you can imagine each Shard 00:02:01.680 --> 00:02:04.029 align:start position:0% own state so you can imagine each Shard containing<00:02:02.280> some<00:02:02.960> some<00:02:03.200> portion<00:02:03.479> of<00:02:03.640> all<00:02:03.840> the 00:02:04.029 --> 00:02:04.039 align:start position:0% containing some some portion of all the 00:02:04.039 --> 00:02:06.069 align:start position:0% containing some some portion of all the accounts<00:02:05.000> and<00:02:05.119> then<00:02:05.240> you<00:02:05.399> have<00:02:05.600> some<00:02:05.840> number 00:02:06.069 --> 00:02:06.079 align:start position:0% accounts and then you have some number 00:02:06.079 --> 00:02:07.590 align:start position:0% accounts and then you have some number of<00:02:06.200> shards<00:02:06.640> you<00:02:06.960> you<00:02:07.039> can<00:02:07.240> imagine 00:02:07.590 --> 00:02:07.600 align:start position:0% of shards you you can imagine 00:02:07.600 --> 00:02:09.070 align:start position:0% of shards you you can imagine potentially<00:02:08.080> having<00:02:08.239> a<00:02:08.360> few<00:02:08.560> hundred<00:02:08.800> a<00:02:08.879> few 00:02:09.070 --> 00:02:09.080 align:start position:0% potentially having a few hundred a few 00:02:09.080 --> 00:02:12.070 align:start position:0% potentially having a few hundred a few thousand<00:02:09.399> of<00:02:09.599> these<00:02:10.560> and<00:02:11.360> the<00:02:11.560> state<00:02:11.879> is 00:02:12.070 --> 00:02:12.080 align:start position:0% thousand of these and the state is 00:02:12.080 --> 00:02:14.070 align:start position:0% thousand of these and the state is represented<00:02:12.599> in<00:02:12.680> a<00:02:13.000> in<00:02:13.040> a<00:02:13.160> Merkel<00:02:13.520> tree<00:02:13.920> as 00:02:14.070 --> 00:02:14.080 align:start position:0% represented in a in a Merkel tree as 00:02:14.080 --> 00:02:16.670 align:start position:0% represented in a in a Merkel tree as usual<00:02:14.959> Merkel<00:02:15.360> roots<00:02:15.640> of<00:02:16.040> of<00:02:16.160> the<00:02:16.319> state 00:02:16.670 --> 00:02:16.680 align:start position:0% usual Merkel roots of of the state 00:02:16.680 --> 00:02:18.710 align:start position:0% usual Merkel roots of of the state represented<00:02:17.160> in<00:02:17.280> The<00:02:17.360> Shard<00:02:17.680> roots<00:02:18.440> and<00:02:18.599> then 00:02:18.710 --> 00:02:18.720 align:start position:0% represented in The Shard roots and then 00:02:18.720 --> 00:02:20.309 align:start position:0% represented in The Shard roots and then you<00:02:18.840> build<00:02:19.280> another<00:02:19.519> mle<00:02:19.840> tree<00:02:20.080> out<00:02:20.160> of<00:02:20.280> The 00:02:20.309 --> 00:02:20.319 align:start position:0% you build another mle tree out of The 00:02:20.319 --> 00:02:24.350 align:start position:0% you build another mle tree out of The Shard<00:02:20.640> roots<00:02:21.200> and<00:02:21.879> you<00:02:22.480> get<00:02:22.800> the<00:02:23.800> global<00:02:24.080> state 00:02:24.350 --> 00:02:24.360 align:start position:0% Shard roots and you get the global state 00:02:24.360 --> 00:02:27.790 align:start position:0% Shard roots and you get the global state route<00:02:24.599> of<00:02:24.720> the<00:02:24.840> entire<00:02:25.160> theorum<00:02:25.959> system<00:02:26.959> so<00:02:27.720> as 00:02:27.790 --> 00:02:27.800 align:start position:0% route of the entire theorum system so as 00:02:27.800 --> 00:02:30.550 align:start position:0% route of the entire theorum system so as you<00:02:27.920> can<00:02:28.040> see<00:02:28.480> yes<00:02:28.680> you<00:02:28.760> can<00:02:28.959> still<00:02:29.319> have<00:02:30.160> some 00:02:30.550 --> 00:02:30.560 align:start position:0% you can see yes you can still have some 00:02:30.560 --> 00:02:32.589 align:start position:0% you can see yes you can still have some concept<00:02:30.959> of<00:02:31.080> sort<00:02:31.239> of<00:02:31.440> global<00:02:31.760> truth<00:02:32.200> even<00:02:32.440> in 00:02:32.589 --> 00:02:32.599 align:start position:0% concept of sort of global truth even in 00:02:32.599 --> 00:02:35.430 align:start position:0% concept of sort of global truth even in a<00:02:32.720> scalable<00:02:33.680> context 00:02:35.430 --> 00:02:35.440 align:start position:0% a scalable context 00:02:35.440 --> 00:02:39.149 align:start position:0% a scalable context so<00:02:36.440> State<00:02:37.120> split<00:02:37.400> into<00:02:37.560> shards<00:02:38.360> each<00:02:38.680> account 00:02:39.149 --> 00:02:39.159 align:start position:0% so State split into shards each account 00:02:39.159 --> 00:02:42.910 align:start position:0% so State split into shards each account is<00:02:39.319> only<00:02:39.560> in<00:02:39.760> one<00:02:40.120> Shard<00:02:41.519> and<00:02:42.519> just<00:02:42.760> the 00:02:42.910 --> 00:02:42.920 align:start position:0% is only in one Shard and just the 00:02:42.920 --> 00:02:44.990 align:start position:0% is only in one Shard and just the simplest<00:02:43.360> case<00:02:43.800> accounts<00:02:44.239> can<00:02:44.440> only<00:02:44.640> send 00:02:44.990 --> 00:02:45.000 align:start position:0% simplest case accounts can only send 00:02:45.000 --> 00:02:48.750 align:start position:0% simplest case accounts can only send transactions<00:02:45.599> to<00:02:46.360> or<00:02:46.760> call<00:02:47.360> call<00:02:47.879> Accounts 00:02:48.750 --> 00:02:48.760 align:start position:0% transactions to or call call Accounts 00:02:48.760 --> 00:02:51.110 align:start position:0% transactions to or call call Accounts within<00:02:49.000> the<00:02:49.120> same<00:02:49.319> Shard<00:02:50.239> so<00:02:50.519> this<00:02:50.599> is<00:02:50.800> one 00:02:51.110 --> 00:02:51.120 align:start position:0% within the same Shard so this is one 00:02:51.120 --> 00:02:54.030 align:start position:0% within the same Shard so this is one fairly<00:02:51.440> simple<00:02:51.680> way<00:02:51.800> to<00:02:51.959> do<00:02:52.120> it<00:02:52.760> so<00:02:53.040> basically 00:02:54.030 --> 00:02:54.040 align:start position:0% fairly simple way to do it so basically 00:02:54.040 --> 00:02:56.350 align:start position:0% fairly simple way to do it so basically you<00:02:54.159> know<00:02:54.840> you<00:02:55.000> just<00:02:55.159> sort<00:02:55.319> of<00:02:55.480> split<00:02:55.800> ethereum 00:02:56.350 --> 00:02:56.360 align:start position:0% you know you just sort of split ethereum 00:02:56.360 --> 00:02:59.270 align:start position:0% you know you just sort of split ethereum up<00:02:56.680> into<00:02:57.280> a<00:02:57.400> few<00:02:57.680> thousand<00:02:58.040> different<00:02:58.360> islands 00:02:59.270 --> 00:02:59.280 align:start position:0% up into a few thousand different islands 00:02:59.280 --> 00:03:01.589 align:start position:0% up into a few thousand different islands and<00:02:59.519> if<00:02:59.840> he<00:03:00.000> wants<00:03:00.239> to<00:03:00.640> do<00:03:00.920> stuff<00:03:01.200> that<00:03:01.319> kind<00:03:01.440> of 00:03:01.589 --> 00:03:01.599 align:start position:0% and if he wants to do stuff that kind of 00:03:01.599 --> 00:03:03.350 align:start position:0% and if he wants to do stuff that kind of interoperates<00:03:02.319> between<00:03:02.599> islands<00:03:03.040> while<00:03:03.159> you 00:03:03.350 --> 00:03:03.360 align:start position:0% interoperates between islands while you 00:03:03.360 --> 00:03:05.350 align:start position:0% interoperates between islands while you just<00:03:03.519> have<00:03:03.640> to<00:03:03.799> figure<00:03:04.080> out<00:03:04.400> some<00:03:05.040> sort<00:03:05.200> of 00:03:05.350 --> 00:03:05.360 align:start position:0% just have to figure out some sort of 00:03:05.360 --> 00:03:08.270 align:start position:0% just have to figure out some sort of super<00:03:05.799> protocol<00:03:06.799> way<00:03:06.959> to<00:03:07.159> do<00:03:07.319> it<00:03:07.840> but<00:03:08.080> in 00:03:08.270 --> 00:03:08.280 align:start position:0% super protocol way to do it but in 00:03:08.280 --> 00:03:10.190 align:start position:0% super protocol way to do it but in theory<00:03:08.879> you<00:03:09.000> know<00:03:09.159> you<00:03:09.319> Pro<00:03:09.519> you<00:03:09.599> can<00:03:09.840> probably 00:03:10.190 --> 00:03:10.200 align:start position:0% theory you know you Pro you can probably 00:03:10.200 --> 00:03:11.789 align:start position:0% theory you know you Pro you can probably have<00:03:10.360> a<00:03:10.480> few<00:03:11.040> thousand<00:03:11.360> different 00:03:11.789 --> 00:03:11.799 align:start position:0% have a few thousand different 00:03:11.799 --> 00:03:13.990 align:start position:0% have a few thousand different applications<00:03:12.799> and<00:03:13.040> each<00:03:13.319> application<00:03:13.799> can 00:03:13.990 --> 00:03:14.000 align:start position:0% applications and each application can 00:03:14.000 --> 00:03:16.070 align:start position:0% applications and each application can kind<00:03:14.120> of<00:03:14.239> do<00:03:14.400> its<00:03:14.560> own<00:03:14.840> thing<00:03:15.440> you<00:03:15.599> could<00:03:15.920> have 00:03:16.070 --> 00:03:16.080 align:start position:0% kind of do its own thing you could have 00:03:16.080 --> 00:03:18.229 align:start position:0% kind of do its own thing you could have you<00:03:16.200> know<00:03:16.599> A<00:03:16.680> Shard<00:03:17.080> that<00:03:17.239> has<00:03:17.480> gnosis<00:03:17.959> on<00:03:18.080> it 00:03:18.229 --> 00:03:18.239 align:start position:0% you know A Shard that has gnosis on it 00:03:18.239 --> 00:03:19.430 align:start position:0% you know A Shard that has gnosis on it you<00:03:18.319> could<00:03:18.440> have<00:03:18.519> a<00:03:18.599> Shard<00:03:18.879> that<00:03:19.040> has<00:03:19.200> like 00:03:19.430 --> 00:03:19.440 align:start position:0% you could have a Shard that has like 00:03:19.440 --> 00:03:21.670 align:start position:0% you could have a Shard that has like augur<00:03:20.000> and<00:03:20.440> potentially<00:03:21.000> three<00:03:21.200> other<00:03:21.440> things 00:03:21.670 --> 00:03:21.680 align:start position:0% augur and potentially three other things 00:03:21.680 --> 00:03:24.110 align:start position:0% augur and potentially three other things on<00:03:21.840> it<00:03:22.360> you<00:03:22.480> could<00:03:22.720> have<00:03:22.959> a<00:03:23.319> A<00:03:23.400> Shard<00:03:23.760> that<00:03:23.920> has 00:03:24.110 --> 00:03:24.120 align:start position:0% on it you could have a A Shard that has 00:03:24.120 --> 00:03:26.430 align:start position:0% on it you could have a A Shard that has five<00:03:24.360> other<00:03:24.599> things<00:03:25.360> so<00:03:25.799> this<00:03:25.920> is<00:03:26.080> one<00:03:26.280> place 00:03:26.430 --> 00:03:26.440 align:start position:0% five other things so this is one place 00:03:26.440 --> 00:03:27.910 align:start position:0% five other things so this is one place to 00:03:27.910 --> 00:03:27.920 align:start position:0% to 00:03:27.920 --> 00:03:31.070 align:start position:0% to start<00:03:28.920> so<00:03:29.360> just<00:03:30.120> go<00:03:30.280> into<00:03:30.480> this<00:03:30.640> in<00:03:30.760> sort<00:03:30.879> of 00:03:31.070 --> 00:03:31.080 align:start position:0% start so just go into this in sort of 00:03:31.080 --> 00:03:33.429 align:start position:0% start so just go into this in sort of much<00:03:31.239> more<00:03:31.640> detail<00:03:32.640> the<00:03:32.760> way<00:03:32.920> that<00:03:33.080> this<00:03:33.239> would 00:03:33.429 --> 00:03:33.439 align:start position:0% much more detail the way that this would 00:03:33.439 --> 00:03:35.509 align:start position:0% much more detail the way that this would work<00:03:33.959> from<00:03:34.120> a<00:03:34.280> transaction<00:03:34.920> standpoint<00:03:35.400> is 00:03:35.509 --> 00:03:35.519 align:start position:0% work from a transaction standpoint is 00:03:35.519 --> 00:03:38.589 align:start position:0% work from a transaction standpoint is you<00:03:35.680> have<00:03:35.879> two<00:03:36.120> levels<00:03:37.000> so<00:03:37.840> in<00:03:38.040> Bitcoin<00:03:38.439> in 00:03:38.589 --> 00:03:38.599 align:start position:0% you have two levels so in Bitcoin in 00:03:38.599 --> 00:03:40.869 align:start position:0% you have two levels so in Bitcoin in ethereum<00:03:39.400> you<00:03:39.640> have<00:03:39.879> a<00:03:40.040> block<00:03:40.360> header<00:03:40.760> which 00:03:40.869 --> 00:03:40.879 align:start position:0% ethereum you have a block header which 00:03:40.879 --> 00:03:42.949 align:start position:0% ethereum you have a block header which is<00:03:41.080> small<00:03:42.000> then<00:03:42.120> you<00:03:42.319> have<00:03:42.519> the<00:03:42.640> set<00:03:42.799> of 00:03:42.949 --> 00:03:42.959 align:start position:0% is small then you have the set of 00:03:42.959 --> 00:03:45.630 align:start position:0% is small then you have the set of transactions<00:03:43.640> which<00:03:43.760> is<00:03:44.040> large<00:03:45.040> and<00:03:45.319> in<00:03:45.480> the 00:03:45.630 --> 00:03:45.640 align:start position:0% transactions which is large and in the 00:03:45.640 --> 00:03:47.589 align:start position:0% transactions which is large and in the block<00:03:45.959> header<00:03:46.280> the<00:03:46.360> set<00:03:46.519> of<00:03:46.680> transactions<00:03:47.360> is 00:03:47.589 --> 00:03:47.599 align:start position:0% block header the set of transactions is 00:03:47.599 --> 00:03:51.789 align:start position:0% block header the set of transactions is represented<00:03:48.360> by<00:03:48.879> a<00:03:49.040> mirle<00:03:49.439> route<00:03:50.560> so<00:03:51.560> here 00:03:51.789 --> 00:03:51.799 align:start position:0% represented by a mirle route so here 00:03:51.799 --> 00:03:53.390 align:start position:0% represented by a mirle route so here we're<00:03:52.040> instead<00:03:52.319> we're<00:03:52.439> going<00:03:52.560> to<00:03:52.640> do<00:03:52.760> a<00:03:52.879> two-l 00:03:53.390 --> 00:03:53.400 align:start position:0% we're instead we're going to do a two-l 00:03:53.400 --> 00:03:54.869 align:start position:0% we're instead we're going to do a two-l thing<00:03:53.640> so<00:03:53.799> we're<00:03:53.920> going<00:03:54.040> to<00:03:54.200> create<00:03:54.599> this 00:03:54.869 --> 00:03:54.879 align:start position:0% thing so we're going to create this 00:03:54.879 --> 00:03:58.910 align:start position:0% thing so we're going to create this object<00:03:55.319> called<00:03:55.519> a<00:03:55.680> transaction<00:03:56.400> group<00:03:57.400> and<00:03:58.360> so 00:03:58.910 --> 00:03:58.920 align:start position:0% object called a transaction group and so 00:03:58.920 --> 00:04:00.429 align:start position:0% object called a transaction group and so you<00:03:59.079> know<00:03:59.400> the<00:03:59.480> way<00:03:59.760> you<00:03:59.840> can<00:03:59.959> think<00:04:00.159> about 00:04:00.429 --> 00:04:00.439 align:start position:0% you know the way you can think about 00:04:00.439 --> 00:04:01.949 align:start position:0% you know the way you can think about this<00:04:00.640> sort<00:04:00.799> of<00:04:01.159> from<00:04:01.280> a<00:04:01.400> big<00:04:01.599> picture 00:04:01.949 --> 00:04:01.959 align:start position:0% this sort of from a big picture 00:04:01.959 --> 00:04:04.270 align:start position:0% this sort of from a big picture standpoint<00:04:02.560> is<00:04:03.159> theoretically<00:04:03.879> even<00:04:04.079> in 00:04:04.270 --> 00:04:04.280 align:start position:0% standpoint is theoretically even in 00:04:04.280 --> 00:04:06.190 align:start position:0% standpoint is theoretically even in Bitcoin<00:04:04.680> you<00:04:04.840> don't<00:04:05.200> or<00:04:05.400> even<00:04:05.599> for<00:04:05.840> something 00:04:06.190 --> 00:04:06.200 align:start position:0% Bitcoin you don't or even for something 00:04:06.200 --> 00:04:07.710 align:start position:0% Bitcoin you don't or even for something like<00:04:06.400> Bitcoin<00:04:06.760> you<00:04:06.840> don't<00:04:06.959> need<00:04:07.280> to<00:04:07.439> have 00:04:07.710 --> 00:04:07.720 align:start position:0% like Bitcoin you don't need to have 00:04:07.720 --> 00:04:09.910 align:start position:0% like Bitcoin you don't need to have blocks<00:04:08.599> you<00:04:08.760> could<00:04:08.920> have<00:04:09.120> just<00:04:09.360> required 00:04:09.910 --> 00:04:09.920 align:start position:0% blocks you could have just required 00:04:09.920 --> 00:04:11.470 align:start position:0% blocks you could have just required transactions<00:04:10.480> to<00:04:10.640> just<00:04:10.799> have<00:04:11.000> proof<00:04:11.200> of<00:04:11.319> work 00:04:11.470 --> 00:04:11.480 align:start position:0% transactions to just have proof of work 00:04:11.480 --> 00:04:12.630 align:start position:0% transactions to just have proof of work on<00:04:11.599> their<00:04:11.720> own<00:04:11.959> and<00:04:12.079> you<00:04:12.159> could<00:04:12.280> have<00:04:12.439> just 00:04:12.630 --> 00:04:12.640 align:start position:0% on their own and you could have just 00:04:12.640 --> 00:04:14.670 align:start position:0% on their own and you could have just made<00:04:13.239> every<00:04:13.480> transaction<00:04:14.040> reference<00:04:14.480> one 00:04:14.670 --> 00:04:14.680 align:start position:0% made every transaction reference one 00:04:14.680 --> 00:04:16.110 align:start position:0% made every transaction reference one previous<00:04:15.040> transaction<00:04:15.640> and<00:04:15.760> just<00:04:15.879> made<00:04:16.000> a 00:04:16.110 --> 00:04:16.120 align:start position:0% previous transaction and just made a 00:04:16.120 --> 00:04:18.949 align:start position:0% previous transaction and just made a Chan<00:04:16.479> of<00:04:17.040> transactions<00:04:18.040> as<00:04:18.120> it<00:04:18.280> turns<00:04:18.560> out<00:04:18.799> by 00:04:18.949 --> 00:04:18.959 align:start position:0% Chan of transactions as it turns out by 00:04:18.959 --> 00:04:20.949 align:start position:0% Chan of transactions as it turns out by introducing<00:04:19.600> one<00:04:19.840> level<00:04:20.120> of<00:04:20.280> inter 00:04:20.949 --> 00:04:20.959 align:start position:0% introducing one level of inter 00:04:20.959 --> 00:04:22.870 align:start position:0% introducing one level of inter interaction<00:04:21.519> with<00:04:21.720> blocks<00:04:22.360> you<00:04:22.479> can<00:04:22.639> make 00:04:22.870 --> 00:04:22.880 align:start position:0% interaction with blocks you can make 00:04:22.880 --> 00:04:24.150 align:start position:0% interaction with blocks you can make things<00:04:23.160> somewhat<00:04:23.479> more<00:04:23.720> efficient<00:04:24.040> and 00:04:24.150 --> 00:04:24.160 align:start position:0% things somewhat more efficient and 00:04:24.160 --> 00:04:26.030 align:start position:0% things somewhat more efficient and somewhat<00:04:24.479> more<00:04:24.639> scalable<00:04:25.639> here<00:04:25.840> we're 00:04:26.030 --> 00:04:26.040 align:start position:0% somewhat more scalable here we're 00:04:26.040 --> 00:04:28.030 align:start position:0% somewhat more scalable here we're introducing<00:04:26.600> two<00:04:26.759> levels<00:04:27.040> of<00:04:27.199> indirection 00:04:28.030 --> 00:04:28.040 align:start position:0% introducing two levels of indirection 00:04:28.040 --> 00:04:30.270 align:start position:0% introducing two levels of indirection you<00:04:28.160> have<00:04:28.360> transactions<00:04:29.280> trans<00:04:29.759> actions<00:04:30.080> get 00:04:30.270 --> 00:04:30.280 align:start position:0% you have transactions trans actions get 00:04:30.280 --> 00:04:32.629 align:start position:0% you have transactions trans actions get cated<00:04:30.759> into<00:04:31.000> transaction<00:04:31.600> groups<00:04:32.440> and<00:04:32.520> then 00:04:32.629 --> 00:04:32.639 align:start position:0% cated into transaction groups and then 00:04:32.639 --> 00:04:34.590 align:start position:0% cated into transaction groups and then it's<00:04:32.800> going<00:04:32.880> to<00:04:32.960> be<00:04:33.080> the<00:04:33.240> transaction<00:04:33.919> groups 00:04:34.590 --> 00:04:34.600 align:start position:0% it's going to be the transaction groups 00:04:34.600 --> 00:04:37.230 align:start position:0% it's going to be the transaction groups that<00:04:34.759> go<00:04:34.919> into<00:04:35.160> the<00:04:35.240> main<00:04:35.479> header<00:04:35.759> chain<00:04:36.520> so 00:04:37.230 --> 00:04:37.240 align:start position:0% that go into the main header chain so 00:04:37.240 --> 00:04:39.270 align:start position:0% that go into the main header chain so transaction<00:04:38.039> transactions<00:04:38.840> what<00:04:39.039> they 00:04:39.270 --> 00:04:39.280 align:start position:0% transaction transactions what they 00:04:39.280 --> 00:04:40.350 align:start position:0% transaction transactions what they groups<00:04:39.600> what<00:04:39.720> do<00:04:39.840> they<00:04:39.960> have<00:04:40.080> they<00:04:40.199> have<00:04:40.280> a 00:04:40.350 --> 00:04:40.360 align:start position:0% groups what do they have they have a 00:04:40.360 --> 00:04:42.790 align:start position:0% groups what do they have they have a header<00:04:40.560> and<00:04:40.680> a<00:04:40.840> body<00:04:41.720> the<00:04:41.840> header<00:04:42.199> contains 00:04:42.790 --> 00:04:42.800 align:start position:0% header and a body the header contains 00:04:42.800 --> 00:04:46.590 align:start position:0% header and a body the header contains two<00:04:43.320> main<00:04:44.320> components<00:04:44.840> to<00:04:45.000> it<00:04:45.440> the<00:04:45.680> left<00:04:46.000> side 00:04:46.590 --> 00:04:46.600 align:start position:0% two main components to it the left side 00:04:46.600 --> 00:04:50.430 align:start position:0% two main components to it the left side contains<00:04:47.160> A<00:04:47.280> Shard<00:04:48.280> ID<00:04:49.280> uh<00:04:49.479> then<00:04:49.680> a<00:04:49.919> pre-state 00:04:50.430 --> 00:04:50.440 align:start position:0% contains A Shard ID uh then a pre-state 00:04:50.440 --> 00:04:52.629 align:start position:0% contains A Shard ID uh then a pre-state route<00:04:51.080> a<00:04:51.280> post-state<00:04:51.759> route<00:04:52.039> and<00:04:52.160> a<00:04:52.320> receipt 00:04:52.629 --> 00:04:52.639 align:start position:0% route a post-state route and a receipt 00:04:52.639 --> 00:04:54.749 align:start position:0% route a post-state route and a receipt route<00:04:53.280> so<00:04:53.520> the<00:04:53.720> pre-state<00:04:54.080> route<00:04:54.360> basically 00:04:54.749 --> 00:04:54.759 align:start position:0% route so the pre-state route basically 00:04:54.759 --> 00:04:57.270 align:start position:0% route so the pre-state route basically says<00:04:55.639> hey<00:04:55.840> look<00:04:56.160> before<00:04:56.520> these<00:04:56.720> transactions 00:04:57.270 --> 00:04:57.280 align:start position:0% says hey look before these transactions 00:04:57.280 --> 00:04:59.870 align:start position:0% says hey look before these transactions were<00:04:57.520> applied<00:04:58.240> the<00:04:58.400> state<00:04:58.680> route<00:04:58.919> of<00:04:59.400> of<00:04:59.600> Shard 00:04:59.870 --> 00:04:59.880 align:start position:0% were applied the state route of of Shard 00:04:59.880 --> 00:05:03.830 align:start position:0% were applied the state route of of Shard 43<00:05:00.600> was<00:05:01.080> this<00:05:01.880> the<00:05:02.080> postate<00:05:02.600> says<00:05:03.440> after 00:05:03.830 --> 00:05:03.840 align:start position:0% 43 was this the postate says after 00:05:03.840 --> 00:05:06.350 align:start position:0% 43 was this the postate says after applying<00:05:04.240> all<00:05:04.360> of<00:05:04.479> these<00:05:04.960> transactions<00:05:05.960> the 00:05:06.350 --> 00:05:06.360 align:start position:0% applying all of these transactions the 00:05:06.360 --> 00:05:08.110 align:start position:0% applying all of these transactions the the<00:05:06.479> state<00:05:06.720> root<00:05:06.960> of<00:05:07.039> Shard<00:05:07.320> 43<00:05:07.759> is<00:05:07.880> going<00:05:08.000> to 00:05:08.110 --> 00:05:08.120 align:start position:0% the state root of Shard 43 is going to 00:05:08.120 --> 00:05:10.590 align:start position:0% the state root of Shard 43 is going to be<00:05:08.360> this<00:05:09.280> and<00:05:09.440> then<00:05:09.600> you<00:05:09.800> also<00:05:10.080> say<00:05:10.280> you<00:05:10.400> know 00:05:10.590 --> 00:05:10.600 align:start position:0% be this and then you also say you know 00:05:10.600 --> 00:05:12.670 align:start position:0% be this and then you also say you know because<00:05:10.840> ethereum<00:05:11.400> has<00:05:11.600> this<00:05:11.800> concept<00:05:12.160> of 00:05:12.670 --> 00:05:12.680 align:start position:0% because ethereum has this concept of 00:05:12.680 --> 00:05:14.710 align:start position:0% because ethereum has this concept of receipts<00:05:13.680> if<00:05:13.800> you<00:05:14.000> apply<00:05:14.280> all<00:05:14.520> these 00:05:14.710 --> 00:05:14.720 align:start position:0% receipts if you apply all these 00:05:14.720 --> 00:05:16.749 align:start position:0% receipts if you apply all these transactions<00:05:15.720> the<00:05:15.880> root<00:05:16.160> of<00:05:16.280> the<00:05:16.360> tree<00:05:16.600> of 00:05:16.749 --> 00:05:16.759 align:start position:0% transactions the root of the tree of 00:05:16.759 --> 00:05:18.070 align:start position:0% transactions the root of the tree of receipts<00:05:17.080> that<00:05:17.160> they're<00:05:17.280> going<00:05:17.400> to<00:05:17.560> emit<00:05:17.919> is 00:05:18.070 --> 00:05:18.080 align:start position:0% receipts that they're going to emit is 00:05:18.080 --> 00:05:20.550 align:start position:0% receipts that they're going to emit is going<00:05:18.199> to<00:05:18.360> be<00:05:18.800> this<00:05:19.800> and<00:05:20.039> each<00:05:20.240> of<00:05:20.400> these 00:05:20.550 --> 00:05:20.560 align:start position:0% going to be this and each of these 00:05:20.560 --> 00:05:22.430 align:start position:0% going to be this and each of these transactions<00:05:21.240> has<00:05:21.360> to<00:05:21.479> have<00:05:21.560> a<00:05:21.639> Shard<00:05:21.919> ID<00:05:22.280> as 00:05:22.430 --> 00:05:22.440 align:start position:0% transactions has to have a Shard ID as 00:05:22.440 --> 00:05:24.189 align:start position:0% transactions has to have a Shard ID as well<00:05:22.919> so<00:05:23.120> you<00:05:23.199> know<00:05:23.360> all<00:05:23.560> these<00:05:23.720> transactions 00:05:24.189 --> 00:05:24.199 align:start position:0% well so you know all these transactions 00:05:24.199 --> 00:05:25.950 align:start position:0% well so you know all these transactions are<00:05:24.319> going<00:05:24.400> to<00:05:24.479> have<00:05:24.600> Shard<00:05:24.880> ID<00:05:25.120> 43<00:05:25.600> and<00:05:25.720> so<00:05:25.840> the 00:05:25.950 --> 00:05:25.960 align:start position:0% are going to have Shard ID 43 and so the 00:05:25.960 --> 00:05:29.110 align:start position:0% are going to have Shard ID 43 and so the whole<00:05:26.080> thing<00:05:26.199> has<00:05:26.360> Shard<00:05:26.560> ID<00:05:27.160> 43<00:05:28.160> over<00:05:28.520> here 00:05:29.110 --> 00:05:29.120 align:start position:0% whole thing has Shard ID 43 over here 00:05:29.120 --> 00:05:31.830 align:start position:0% whole thing has Shard ID 43 over here you<00:05:29.319> have<00:05:29.759> you<00:05:29.840> know<00:05:30.160> the<00:05:30.319> idea<00:05:30.880> that<00:05:31.400> in<00:05:31.520> order 00:05:31.830 --> 00:05:31.840 align:start position:0% you have you know the idea that in order 00:05:31.840 --> 00:05:34.309 align:start position:0% you have you know the idea that in order for<00:05:32.160> this<00:05:32.479> header<00:05:32.759> to<00:05:32.919> be<00:05:33.120> valid<00:05:33.720> it<00:05:33.880> has<00:05:34.000> to<00:05:34.120> be 00:05:34.309 --> 00:05:34.319 align:start position:0% for this header to be valid it has to be 00:05:34.319 --> 00:05:35.990 align:start position:0% for this header to be valid it has to be validated<00:05:34.880> by<00:05:35.039> this<00:05:35.199> sort<00:05:35.319> of<00:05:35.479> randomly 00:05:35.990 --> 00:05:36.000 align:start position:0% validated by this sort of randomly 00:05:36.000 --> 00:05:38.430 align:start position:0% validated by this sort of randomly selected<00:05:36.479> Global<00:05:36.840> sample<00:05:37.160> of<00:05:37.280> validators<00:05:38.280> so 00:05:38.430 --> 00:05:38.440 align:start position:0% selected Global sample of validators so 00:05:38.440 --> 00:05:40.469 align:start position:0% selected Global sample of validators so we<00:05:38.560> could<00:05:38.720> imagine<00:05:39.120> you'll<00:05:39.360> have<00:05:39.639> like<00:05:40.240> some 00:05:40.469 --> 00:05:40.479 align:start position:0% we could imagine you'll have like some 00:05:40.479 --> 00:05:42.909 align:start position:0% we could imagine you'll have like some you<00:05:40.600> know<00:05:40.759> 400<00:05:41.479> 1,000<00:05:42.120> whatever<00:05:42.520> number<00:05:42.759> of 00:05:42.909 --> 00:05:42.919 align:start position:0% you know 400 1,000 whatever number of 00:05:42.919 --> 00:05:45.350 align:start position:0% you know 400 1,000 whatever number of idas<00:05:43.319> of<00:05:43.520> validators<00:05:44.240> inside<00:05:44.639> the<00:05:44.800> entire 00:05:45.350 --> 00:05:45.360 align:start position:0% idas of validators inside the entire 00:05:45.360 --> 00:05:48.390 align:start position:0% idas of validators inside the entire system<00:05:46.360> and<00:05:47.160> theoretically<00:05:47.919> these<00:05:48.160> don't 00:05:48.390 --> 00:05:48.400 align:start position:0% system and theoretically these don't 00:05:48.400 --> 00:05:50.790 align:start position:0% system and theoretically these don't even<00:05:48.680> need<00:05:49.000> to<00:05:49.160> be<00:05:49.400> the<00:05:49.560> same<00:05:49.880> validators<00:05:50.600> as 00:05:50.790 --> 00:05:50.800 align:start position:0% even need to be the same validators as 00:05:50.800 --> 00:05:52.550 align:start position:0% even need to be the same validators as the<00:05:50.919> ones<00:05:51.199> that<00:05:51.360> maintain<00:05:51.880> that<00:05:52.360> that 00:05:52.550 --> 00:05:52.560 align:start position:0% the ones that maintain that that 00:05:52.560 --> 00:05:53.830 align:start position:0% the ones that maintain that that actually<00:05:52.800> maintain<00:05:53.160> the<00:05:53.280> top<00:05:53.560> level 00:05:53.830 --> 00:05:53.840 align:start position:0% actually maintain the top level 00:05:53.840 --> 00:05:55.510 align:start position:0% actually maintain the top level consensus<00:05:54.840> so<00:05:55.039> you<00:05:55.120> know<00:05:55.240> if<00:05:55.319> you're 00:05:55.510 --> 00:05:55.520 align:start position:0% consensus so you know if you're 00:05:55.520 --> 00:05:57.390 align:start position:0% consensus so you know if you're concerned<00:05:55.960> about<00:05:56.199> sort<00:05:56.360> of<00:05:56.479> O<00:05:56.639> ofn<00:05:56.919> squared 00:05:57.390 --> 00:05:57.400 align:start position:0% concerned about sort of O ofn squared 00:05:57.400 --> 00:05:59.430 align:start position:0% concerned about sort of O ofn squared stuff<00:05:57.639> slowing<00:05:58.080> down<00:05:58.360> Casper<00:05:58.880> or<00:05:59.000> you<00:05:59.080> know 00:05:59.430 --> 00:05:59.440 align:start position:0% stuff slowing down Casper or you know 00:05:59.440 --> 00:06:01.230 align:start position:0% stuff slowing down Casper or you know slowing<00:05:59.759> down<00:06:00.280> whatever<00:06:00.560> other<00:06:00.759> consensus 00:06:01.230 --> 00:06:01.240 align:start position:0% slowing down whatever other consensus 00:06:01.240 --> 00:06:03.070 align:start position:0% slowing down whatever other consensus algorithm<00:06:01.759> that's<00:06:01.960> fine<00:06:02.479> you<00:06:02.639> can<00:06:02.840> have<00:06:03.000> you 00:06:03.070 --> 00:06:03.080 align:start position:0% algorithm that's fine you can have you 00:06:03.080 --> 00:06:04.990 align:start position:0% algorithm that's fine you can have you can<00:06:03.240> stick<00:06:03.479> to<00:06:03.680> you<00:06:03.759> know<00:06:03.919> 400<00:06:04.319> validators<00:06:04.800> for 00:06:04.990 --> 00:06:05.000 align:start position:0% can stick to you know 400 validators for 00:06:05.000 --> 00:06:09.110 align:start position:0% can stick to you know 400 validators for Casper<00:06:05.960> and<00:06:06.319> have<00:06:06.560> 40,000<00:06:07.199> validators<00:06:08.120> for 00:06:09.110 --> 00:06:09.120 align:start position:0% Casper and have 40,000 validators for 00:06:09.120 --> 00:06:12.670 align:start position:0% Casper and have 40,000 validators for the<00:06:09.400> the<00:06:09.520> bottom<00:06:09.919> level<00:06:11.160> now<00:06:12.160> you<00:06:12.280> know<00:06:12.400> every 00:06:12.670 --> 00:06:12.680 align:start position:0% the the bottom level now you know every 00:06:12.680 --> 00:06:14.469 align:start position:0% the the bottom level now you know every transaction<00:06:13.160> specifi<00:06:13.520> as<00:06:13.599> an<00:06:13.759> ID<00:06:14.319> a 00:06:14.469 --> 00:06:14.479 align:start position:0% transaction specifi as an ID a 00:06:14.479 --> 00:06:16.510 align:start position:0% transaction specifi as an ID a transaction<00:06:15.039> in<00:06:15.240> Shard<00:06:15.680> X<00:06:15.960> means<00:06:16.240> that<00:06:16.400> it 00:06:16.510 --> 00:06:16.520 align:start position:0% transaction in Shard X means that it 00:06:16.520 --> 00:06:19.070 align:start position:0% transaction in Shard X means that it does<00:06:16.800> stuff<00:06:17.080> only<00:06:17.319> in<00:06:17.440> chard<00:06:17.800> x<00:06:18.400> a<00:06:18.560> transaction 00:06:19.070 --> 00:06:19.080 align:start position:0% does stuff only in chard x a transaction 00:06:19.080 --> 00:06:20.870 align:start position:0% does stuff only in chard x a transaction grouping<00:06:19.400> in<00:06:19.479> chard<00:06:19.800> X<00:06:20.000> contains<00:06:20.440> zero<00:06:20.720> or 00:06:20.870 --> 00:06:20.880 align:start position:0% grouping in chard X contains zero or 00:06:20.880 --> 00:06:22.790 align:start position:0% grouping in chard X contains zero or more<00:06:21.080> transactions<00:06:21.560> in<00:06:21.680> chard<00:06:22.000> X<00:06:22.560> and 00:06:22.790 --> 00:06:22.800 align:start position:0% more transactions in chard X and 00:06:22.800 --> 00:06:25.230 align:start position:0% more transactions in chard X and specifies<00:06:23.160> the<00:06:23.280> pre-post<00:06:23.759> state<00:06:24.000> route<00:06:24.960> top 00:06:25.230 --> 00:06:25.240 align:start position:0% specifies the pre-post state route top 00:06:25.240 --> 00:06:27.710 align:start position:0% specifies the pre-post state route top level<00:06:25.599> looks<00:06:25.880> like<00:06:26.120> this<00:06:26.840> so<00:06:27.160> this<00:06:27.280> is 00:06:27.710 --> 00:06:27.720 align:start position:0% level looks like this so this is 00:06:27.720 --> 00:06:29.749 align:start position:0% level looks like this so this is probably<00:06:28.160> one<00:06:28.280> of<00:06:28.400> the<00:06:28.560> more<00:06:28.880> complicated 00:06:29.749 --> 00:06:29.759 align:start position:0% probably one of the more complicated 00:06:29.759 --> 00:06:31.629 align:start position:0% probably one of the more complicated blockchain<00:06:30.199> diagrams<00:06:30.639> you're<00:06:30.759> going<00:06:30.840> to<00:06:30.960> see 00:06:31.629 --> 00:06:31.639 align:start position:0% blockchain diagrams you're going to see 00:06:31.639 --> 00:06:33.909 align:start position:0% blockchain diagrams you're going to see this<00:06:31.840> week<00:06:32.720> probably<00:06:33.000> the<00:06:33.120> major<00:06:33.479> competitor 00:06:33.909 --> 00:06:33.919 align:start position:0% this week probably the major competitor 00:06:33.919 --> 00:06:35.189 align:start position:0% this week probably the major competitor here<00:06:34.039> is<00:06:34.199> going<00:06:34.280> to<00:06:34.400> be<00:06:34.599> Jeff<00:06:34.800> Coleman's 00:06:35.189 --> 00:06:35.199 align:start position:0% here is going to be Jeff Coleman's 00:06:35.199 --> 00:06:39.350 align:start position:0% here is going to be Jeff Coleman's Universal<00:06:35.720> hash<00:06:35.960> time<00:06:36.599> graph<00:06:37.599> um<00:06:38.440> so 00:06:39.350 --> 00:06:39.360 align:start position:0% Universal hash time graph um so 00:06:39.360 --> 00:06:41.629 align:start position:0% Universal hash time graph um so basically<00:06:40.039> you<00:06:40.240> still<00:06:40.599> have<00:06:40.840> a<00:06:41.000> blockchain<00:06:41.520> at 00:06:41.629 --> 00:06:41.639 align:start position:0% basically you still have a blockchain at 00:06:41.639 --> 00:06:43.469 align:start position:0% basically you still have a blockchain at the<00:06:41.800> top<00:06:42.440> so<00:06:42.639> you<00:06:42.759> know<00:06:42.880> you<00:06:42.960> can<00:06:43.160> call<00:06:43.360> this 00:06:43.469 --> 00:06:43.479 align:start position:0% the top so you know you can call this 00:06:43.479 --> 00:06:46.150 align:start position:0% the top so you know you can call this the<00:06:43.639> header<00:06:44.000> chain<00:06:45.000> and<00:06:45.240> it<00:06:45.440> contains<00:06:46.000> you 00:06:46.150 --> 00:06:46.160 align:start position:0% the header chain and it contains you 00:06:46.160 --> 00:06:48.469 align:start position:0% the header chain and it contains you know<00:06:46.599> a<00:06:46.759> state<00:06:47.000> route<00:06:47.520> it<00:06:47.639> contains<00:06:48.000> a<00:06:48.160> hash<00:06:48.319> of 00:06:48.469 --> 00:06:48.479 align:start position:0% know a state route it contains a hash of 00:06:48.479 --> 00:06:50.350 align:start position:0% know a state route it contains a hash of the<00:06:48.560> previous<00:06:48.880> block<00:06:49.160> it<00:06:49.280> contains<00:06:49.720> metadata 00:06:50.350 --> 00:06:50.360 align:start position:0% the previous block it contains metadata 00:06:50.360 --> 00:06:51.870 align:start position:0% the previous block it contains metadata just<00:06:50.599> like<00:06:50.759> you<00:06:50.880> know<00:06:51.039> all<00:06:51.160> the<00:06:51.280> metadata<00:06:51.800> we 00:06:51.870 --> 00:06:51.880 align:start position:0% just like you know all the metadata we 00:06:51.880 --> 00:06:55.029 align:start position:0% just like you know all the metadata we all<00:06:52.000> know<00:06:52.160> and<00:06:52.440> love<00:06:53.440> but<00:06:53.759> it<00:06:53.960> contains<00:06:54.639> two 00:06:55.029 --> 00:06:55.039 align:start position:0% all know and love but it contains two 00:06:55.039 --> 00:06:57.510 align:start position:0% all know and love but it contains two primary<00:06:55.520> Roots<00:06:56.520> one<00:06:56.680> of<00:06:56.840> them<00:06:57.000> is<00:06:57.120> a<00:06:57.240> state 00:06:57.510 --> 00:06:57.520 align:start position:0% primary Roots one of them is a state 00:06:57.520 --> 00:06:59.110 align:start position:0% primary Roots one of them is a state route<00:06:58.240> and<00:06:58.360> the<00:06:58.479> state<00:06:58.680> route<00:06:58.919> basically 00:06:59.110 --> 00:06:59.120 align:start position:0% route and the state route basically 00:06:59.120 --> 00:07:01.469 align:start position:0% route and the state route basically repres<00:06:59.400> represents<00:07:00.120> the<00:07:00.280> entire<00:07:00.599> state<00:07:01.240> so 00:07:01.469 --> 00:07:01.479 align:start position:0% repres represents the entire state so 00:07:01.479 --> 00:07:03.150 align:start position:0% repres represents the entire state so here<00:07:01.599> you<00:07:01.720> have<00:07:01.840> The<00:07:01.919> Shard<00:07:02.280> Roots<00:07:02.599> each<00:07:02.759> Shard 00:07:03.150 --> 00:07:03.160 align:start position:0% here you have The Shard Roots each Shard 00:07:03.160 --> 00:07:05.309 align:start position:0% here you have The Shard Roots each Shard itself<00:07:03.479> points<00:07:03.759> to<00:07:03.879> a<00:07:04.000> tree<00:07:05.000> and<00:07:05.120> then<00:07:05.199> you 00:07:05.309 --> 00:07:05.319 align:start position:0% itself points to a tree and then you 00:07:05.319 --> 00:07:08.070 align:start position:0% itself points to a tree and then you have<00:07:05.479> a<00:07:05.639> transaction<00:07:06.360> group<00:07:06.840> route<00:07:07.800> so 00:07:08.070 --> 00:07:08.080 align:start position:0% have a transaction group route so 00:07:08.080 --> 00:07:10.029 align:start position:0% have a transaction group route so instead<00:07:08.400> of<00:07:08.680> just<00:07:08.919> being<00:07:09.199> a<00:07:09.319> Merkel<00:07:09.680> tree<00:07:09.919> of 00:07:10.029 --> 00:07:10.039 align:start position:0% instead of just being a Merkel tree of 00:07:10.039 --> 00:07:12.070 align:start position:0% instead of just being a Merkel tree of transactions<00:07:10.919> you<00:07:11.080> have<00:07:11.199> a<00:07:11.280> Merkel<00:07:11.680> tree<00:07:11.919> of 00:07:12.070 --> 00:07:12.080 align:start position:0% transactions you have a Merkel tree of 00:07:12.080 --> 00:07:14.070 align:start position:0% transactions you have a Merkel tree of transaction<00:07:12.800> groups<00:07:13.520> and<00:07:13.680> then<00:07:13.879> each 00:07:14.070 --> 00:07:14.080 align:start position:0% transaction groups and then each 00:07:14.080 --> 00:07:16.710 align:start position:0% transaction groups and then each transaction<00:07:14.680> group<00:07:15.000> as<00:07:15.160> usual<00:07:15.720> contains 00:07:16.710 --> 00:07:16.720 align:start position:0% transaction group as usual contains 00:07:16.720 --> 00:07:19.950 align:start position:0% transaction group as usual contains pre-state<00:07:17.680> postate<00:07:18.599> of<00:07:18.800> The<00:07:18.879> Shard<00:07:19.680> not<00:07:19.840> of 00:07:19.950 --> 00:07:19.960 align:start position:0% pre-state postate of The Shard not of 00:07:19.960 --> 00:07:22.469 align:start position:0% pre-state postate of The Shard not of the<00:07:20.080> whole<00:07:20.400> not<00:07:20.560> of<00:07:20.720> the<00:07:20.840> entire<00:07:21.160> Global<00:07:21.520> thing 00:07:22.469 --> 00:07:22.479 align:start position:0% the whole not of the entire Global thing 00:07:22.479 --> 00:07:25.990 align:start position:0% the whole not of the entire Global thing and<00:07:22.759> a<00:07:22.960> transaction<00:07:23.599> route<00:07:24.400> and<00:07:24.720> a<00:07:24.919> re<00:07:25.840> with 00:07:25.990 --> 00:07:26.000 align:start position:0% and a transaction route and a re with 00:07:26.000 --> 00:07:27.749 align:start position:0% and a transaction route and a re with the<00:07:26.120> transaction<00:07:26.560> tree<00:07:26.960> and<00:07:27.120> a<00:07:27.240> receipt<00:07:27.560> route 00:07:27.749 --> 00:07:27.759 align:start position:0% the transaction tree and a receipt route 00:07:27.759 --> 00:07:30.670 align:start position:0% the transaction tree and a receipt route for<00:07:27.919> the<00:07:28.000> receipt<00:07:28.319> tree 00:07:30.670 --> 00:07:30.680 align:start position:0% for the receipt tree 00:07:30.680 --> 00:07:33.029 align:start position:0% for the receipt tree so<00:07:31.680> one<00:07:31.879> way<00:07:32.039> to<00:07:32.199> think<00:07:32.400> about<00:07:32.639> this<00:07:32.759> sort<00:07:32.879> of 00:07:33.029 --> 00:07:33.039 align:start position:0% so one way to think about this sort of 00:07:33.039 --> 00:07:34.830 align:start position:0% so one way to think about this sort of intuitively<00:07:33.639> is<00:07:33.800> you<00:07:33.919> can<00:07:34.039> think<00:07:34.199> of<00:07:34.360> the<00:07:34.520> top 00:07:34.830 --> 00:07:34.840 align:start position:0% intuitively is you can think of the top 00:07:34.840 --> 00:07:37.430 align:start position:0% intuitively is you can think of the top level<00:07:35.360> as<00:07:36.080> a<00:07:36.319> the<00:07:36.520> top<00:07:36.800> level<00:07:37.080> as<00:07:37.240> a 00:07:37.430 --> 00:07:37.440 align:start position:0% level as a the top level as a 00:07:37.440 --> 00:07:39.990 align:start position:0% level as a the top level as a non-scalable<00:07:38.319> ethereum<00:07:38.879> 1.0<00:07:39.599> style 00:07:39.990 --> 00:07:40.000 align:start position:0% non-scalable ethereum 1.0 style 00:07:40.000 --> 00:07:41.990 align:start position:0% non-scalable ethereum 1.0 style blockchain<00:07:40.960> except<00:07:41.240> it<00:07:41.400> has<00:07:41.560> these<00:07:41.720> funny 00:07:41.990 --> 00:07:42.000 align:start position:0% blockchain except it has these funny 00:07:42.000 --> 00:07:44.309 align:start position:0% blockchain except it has these funny state<00:07:42.280> transition<00:07:42.800> rules<00:07:43.280> where<00:07:43.800> instead<00:07:44.080> of 00:07:44.309 --> 00:07:44.319 align:start position:0% state transition rules where instead of 00:07:44.319 --> 00:07:46.869 align:start position:0% state transition rules where instead of validating<00:07:45.240> transactions<00:07:46.240> it<00:07:46.400> validates 00:07:46.869 --> 00:07:46.879 align:start position:0% validating transactions it validates 00:07:46.879 --> 00:07:49.629 align:start position:0% validating transactions it validates transaction<00:07:47.560> groups<00:07:48.560> and<00:07:48.800> a<00:07:48.960> transaction 00:07:49.629 --> 00:07:49.639 align:start position:0% transaction groups and a transaction 00:07:49.639 --> 00:07:52.510 align:start position:0% transaction groups and a transaction group<00:07:50.000> is<00:07:50.280> valid<00:07:50.800> if<00:07:51.599> basically<00:07:52.360> the 00:07:52.510 --> 00:07:52.520 align:start position:0% group is valid if basically the 00:07:52.520 --> 00:07:55.710 align:start position:0% group is valid if basically the pre-state<00:07:52.919> rout<00:07:53.479> matches<00:07:54.479> and<00:07:55.280> if<00:07:55.599> the 00:07:55.710 --> 00:07:55.720 align:start position:0% pre-state rout matches and if the 00:07:55.720 --> 00:07:58.309 align:start position:0% pre-state rout matches and if the signatures<00:07:56.159> are<00:07:56.479> valid<00:07:57.479> and<00:07:57.759> if<00:07:57.960> those<00:07:58.120> two 00:07:58.309 --> 00:07:58.319 align:start position:0% signatures are valid and if those two 00:07:58.319 --> 00:08:00.149 align:start position:0% signatures are valid and if those two things<00:07:58.599> line<00:07:58.840> up<00:07:59.440> then<00:07:59.560> it<00:07:59.720> takes<00:08:00.000> the 00:08:00.149 --> 00:08:00.159 align:start position:0% things line up then it takes the 00:08:00.159 --> 00:08:02.070 align:start position:0% things line up then it takes the signatures<00:08:00.800> as<00:08:01.039> kind<00:08:01.159> of<00:08:01.319> proxy<00:08:01.759> evidence 00:08:02.070 --> 00:08:02.080 align:start position:0% signatures as kind of proxy evidence 00:08:02.080 --> 00:08:04.469 align:start position:0% signatures as kind of proxy evidence that<00:08:02.240> everything<00:08:02.520> else<00:08:02.720> was<00:08:02.879> done<00:08:03.479> correctly 00:08:04.469 --> 00:08:04.479 align:start position:0% that everything else was done correctly 00:08:04.479 --> 00:08:06.629 align:start position:0% that everything else was done correctly and<00:08:04.680> then<00:08:05.319> if<00:08:05.479> this<00:08:05.639> transaction<00:08:06.159> group<00:08:06.440> gets 00:08:06.629 --> 00:08:06.639 align:start position:0% and then if this transaction group gets 00:08:06.639 --> 00:08:09.469 align:start position:0% and then if this transaction group gets in<00:08:07.120> then<00:08:07.360> the<00:08:07.479> post<00:08:07.720> State<00:08:07.960> Route<00:08:08.400> becomes<00:08:09.400> the 00:08:09.469 --> 00:08:09.479 align:start position:0% in then the post State Route becomes the 00:08:09.479 --> 00:08:11.189 align:start position:0% in then the post State Route becomes the state<00:08:09.720> route<00:08:09.919> of<00:08:10.039> that<00:08:10.199> particular 00:08:11.189 --> 00:08:11.199 align:start position:0% state route of that particular 00:08:11.199 --> 00:08:15.510 align:start position:0% state route of that particular Shard<00:08:12.479> so<00:08:13.479> question<00:08:14.039> how<00:08:14.280> getting<00:08:14.639> back<00:08:14.800> to 00:08:15.510 --> 00:08:15.520 align:start position:0% Shard so question how getting back to 00:08:15.520 --> 00:08:18.790 align:start position:0% Shard so question how getting back to how<00:08:15.720> do<00:08:16.000> we<00:08:16.199> do<00:08:16.759> cross<00:08:17.080> Shard<00:08:17.639> transactions<00:08:18.639> so 00:08:18.790 --> 00:08:18.800 align:start position:0% how do we do cross Shard transactions so 00:08:18.800 --> 00:08:21.790 align:start position:0% how do we do cross Shard transactions so the<00:08:18.960> problem<00:08:19.360> is<00:08:20.000> if<00:08:20.199> we<00:08:20.400> allow<00:08:21.120> just<00:08:21.280> sort<00:08:21.440> of 00:08:21.790 --> 00:08:21.800 align:start position:0% the problem is if we allow just sort of 00:08:21.800 --> 00:08:24.309 align:start position:0% the problem is if we allow just sort of Rand<00:08:22.240> random<00:08:22.759> arbitrary<00:08:23.440> cross<00:08:23.759> cross 00:08:24.309 --> 00:08:24.319 align:start position:0% Rand random arbitrary cross cross 00:08:24.319 --> 00:08:26.430 align:start position:0% Rand random arbitrary cross cross calling<00:08:25.039> then<00:08:25.240> parallelization<00:08:25.919> becomes 00:08:26.430 --> 00:08:26.440 align:start position:0% calling then parallelization becomes 00:08:26.440 --> 00:08:28.670 align:start position:0% calling then parallelization becomes impossible<00:08:27.440> you<00:08:27.560> know<00:08:28.240> you<00:08:28.440> could 00:08:28.670 --> 00:08:28.680 align:start position:0% impossible you know you could 00:08:28.680 --> 00:08:31.550 align:start position:0% impossible you know you could potentially<00:08:29.479> have<00:08:30.280> contracts<00:08:31.000> in<00:08:31.199> 20 00:08:31.550 --> 00:08:31.560 align:start position:0% potentially have contracts in 20 00:08:31.560 --> 00:08:34.829 align:start position:0% potentially have contracts in 20 different<00:08:31.759> shards<00:08:32.719> all<00:08:33.719> access<00:08:34.039> or<00:08:34.320> modify 00:08:34.829 --> 00:08:34.839 align:start position:0% different shards all access or modify 00:08:34.839 --> 00:08:36.870 align:start position:0% different shards all access or modify accounts<00:08:35.200> in<00:08:35.360> 20<00:08:35.680> other<00:08:35.880> different<00:08:36.080> shards 00:08:36.870 --> 00:08:36.880 align:start position:0% accounts in 20 other different shards 00:08:36.880 --> 00:08:38.350 align:start position:0% accounts in 20 other different shards and<00:08:37.000> it<00:08:37.080> could<00:08:37.279> be<00:08:37.399> done<00:08:37.599> in<00:08:37.719> some<00:08:37.959> way<00:08:38.159> that's 00:08:38.350 --> 00:08:38.360 align:start position:0% and it could be done in some way that's 00:08:38.360 --> 00:08:41.149 align:start position:0% and it could be done in some way that's like<00:08:38.599> completely<00:08:39.599> you<00:08:39.719> know<00:08:40.240> not<00:08:40.519> friendly<00:08:40.919> to 00:08:41.149 --> 00:08:41.159 align:start position:0% like completely you know not friendly to 00:08:41.159 --> 00:08:42.790 align:start position:0% like completely you know not friendly to any<00:08:41.360> kind<00:08:41.479> of<00:08:41.640> parallel<00:08:42.080> analysis<00:08:42.519> it<00:08:42.640> could 00:08:42.790 --> 00:08:42.800 align:start position:0% any kind of parallel analysis it could 00:08:42.800 --> 00:08:44.389 align:start position:0% any kind of parallel analysis it could you<00:08:42.880> know<00:08:43.000> it<00:08:43.080> could<00:08:43.200> be<00:08:43.279> non-cut<00:08:43.919> commutative 00:08:44.389 --> 00:08:44.399 align:start position:0% you know it could be non-cut commutative 00:08:44.399 --> 00:08:47.630 align:start position:0% you know it could be non-cut commutative and<00:08:44.519> a<00:08:44.600> whole<00:08:44.760> bunch<00:08:44.959> of<00:08:45.560> intractable<00:08:46.320> ways 00:08:47.630 --> 00:08:47.640 align:start position:0% and a whole bunch of intractable ways 00:08:47.640 --> 00:08:50.310 align:start position:0% and a whole bunch of intractable ways so<00:08:48.640> solution<00:08:49.040> is<00:08:49.200> to<00:08:49.320> make<00:08:49.440> it<00:08:49.560> asynchronous 00:08:50.310 --> 00:08:50.320 align:start position:0% so solution is to make it asynchronous 00:08:50.320 --> 00:08:54.350 align:start position:0% so solution is to make it asynchronous but<00:08:50.839> how<00:08:51.839> so<00:08:52.279> the<00:08:52.480> basic<00:08:52.800> ingredient<00:08:53.480> here<00:08:53.800> is 00:08:54.350 --> 00:08:54.360 align:start position:0% but how so the basic ingredient here is 00:08:54.360 --> 00:08:56.829 align:start position:0% but how so the basic ingredient here is mer<00:08:54.800> Merkel<00:08:55.120> tree<00:08:55.399> receipts 00:08:56.829 --> 00:08:56.839 align:start position:0% mer Merkel tree receipts 00:08:56.839 --> 00:09:00.230 align:start position:0% mer Merkel tree receipts so<00:08:57.839> if<00:08:57.959> you<00:08:58.200> look<00:08:58.560> at<00:08:58.959> just<00:08:59.440> one<00:08:59.720> particular 00:09:00.230 --> 00:09:00.240 align:start position:0% so if you look at just one particular 00:09:00.240 --> 00:09:02.190 align:start position:0% so if you look at just one particular receipt<00:09:01.160> you<00:09:01.360> you<00:09:01.480> might<00:09:01.640> notice<00:09:01.959> that<00:09:02.079> this 00:09:02.190 --> 00:09:02.200 align:start position:0% receipt you you might notice that this 00:09:02.200 --> 00:09:04.590 align:start position:0% receipt you you might notice that this receipt<00:09:02.560> is<00:09:02.680> part<00:09:02.839> of<00:09:02.920> a<00:09:03.160> tree<00:09:04.160> and<00:09:04.440> this 00:09:04.590 --> 00:09:04.600 align:start position:0% receipt is part of a tree and this 00:09:04.600 --> 00:09:07.509 align:start position:0% receipt is part of a tree and this miracle<00:09:04.920> tree<00:09:05.200> has<00:09:05.320> a<00:09:05.519> root<00:09:05.839> over<00:09:06.120> here<00:09:07.079> and 00:09:07.509 --> 00:09:07.519 align:start position:0% miracle tree has a root over here and 00:09:07.519 --> 00:09:09.670 align:start position:0% miracle tree has a root over here and this<00:09:07.640> thing<00:09:07.800> is<00:09:08.000> itself<00:09:08.360> part<00:09:08.480> of<00:09:08.600> a<00:09:08.720> tree<00:09:09.440> or 00:09:09.670 --> 00:09:09.680 align:start position:0% this thing is itself part of a tree or 00:09:09.680 --> 00:09:12.030 align:start position:0% this thing is itself part of a tree or rather<00:09:10.560> and<00:09:10.720> then<00:09:10.959> this<00:09:11.120> thing<00:09:11.360> itself<00:09:11.839> is 00:09:12.030 --> 00:09:12.040 align:start position:0% rather and then this thing itself is 00:09:12.040 --> 00:09:13.470 align:start position:0% rather and then this thing itself is part<00:09:12.160> of<00:09:12.279> a<00:09:12.360> tree<00:09:12.600> which<00:09:12.720> has<00:09:12.839> a<00:09:13.000> mirle<00:09:13.279> root 00:09:13.470 --> 00:09:13.480 align:start position:0% part of a tree which has a mirle root 00:09:13.480 --> 00:09:16.949 align:start position:0% part of a tree which has a mirle root over<00:09:13.720> here<00:09:14.600> so<00:09:15.440> ultimately<00:09:16.440> you<00:09:16.600> could<00:09:16.800> come 00:09:16.949 --> 00:09:16.959 align:start position:0% over here so ultimately you could come 00:09:16.959 --> 00:09:20.790 align:start position:0% over here so ultimately you could come up<00:09:17.200> with<00:09:17.360> a<00:09:17.560> fairly<00:09:17.959> compact<00:09:18.880> branch<00:09:19.880> and<00:09:20.600> that 00:09:20.790 --> 00:09:20.800 align:start position:0% up with a fairly compact branch and that 00:09:20.800 --> 00:09:24.350 align:start position:0% up with a fairly compact branch and that Branch<00:09:21.279> would<00:09:21.800> ultimately<00:09:22.720> you<00:09:22.880> know<00:09:23.760> have 00:09:24.350 --> 00:09:24.360 align:start position:0% Branch would ultimately you know have 00:09:24.360 --> 00:09:27.269 align:start position:0% Branch would ultimately you know have basically<00:09:24.800> be<00:09:25.000> a<00:09:25.240> proof<00:09:26.120> that<00:09:26.600> the<00:09:26.760> receipt 00:09:27.269 --> 00:09:27.279 align:start position:0% basically be a proof that the receipt 00:09:27.279 --> 00:09:29.269 align:start position:0% basically be a proof that the receipt actually<00:09:27.640> was<00:09:27.839> included<00:09:28.279> at<00:09:28.480> this<00:09:28.600> particular 00:09:29.269 --> 00:09:29.279 align:start position:0% actually was included at this particular 00:09:29.279 --> 00:09:31.110 align:start position:0% actually was included at this particular time<00:09:30.079> so<00:09:30.279> this<00:09:30.440> gives<00:09:30.600> you<00:09:30.720> proof<00:09:30.920> of 00:09:31.110 --> 00:09:31.120 align:start position:0% time so this gives you proof of 00:09:31.120 --> 00:09:33.110 align:start position:0% time so this gives you proof of existence<00:09:31.720> it<00:09:31.880> does<00:09:32.120> not<00:09:32.440> give<00:09:32.600> you<00:09:32.800> sort<00:09:32.959> of 00:09:33.110 --> 00:09:33.120 align:start position:0% existence it does not give you sort of 00:09:33.120 --> 00:09:35.389 align:start position:0% existence it does not give you sort of proof<00:09:33.320> of<00:09:33.480> non-<00:09:33.760> double<00:09:34.160> spending<00:09:35.160> but<00:09:35.320> what 00:09:35.389 --> 00:09:35.399 align:start position:0% proof of non- double spending but what 00:09:35.399 --> 00:09:36.590 align:start position:0% proof of non- double spending but what we're<00:09:35.560> going<00:09:35.640> to<00:09:35.760> do<00:09:35.920> is<00:09:36.000> we're<00:09:36.120> going<00:09:36.240> to<00:09:36.399> add 00:09:36.590 --> 00:09:36.600 align:start position:0% we're going to do is we're going to add 00:09:36.600 --> 00:09:37.630 align:start position:0% we're going to do is we're going to add that<00:09:36.760> in<00:09:36.920> but<00:09:37.040> we're<00:09:37.200> going<00:09:37.279> to<00:09:37.399> sort<00:09:37.519> of 00:09:37.630 --> 00:09:37.640 align:start position:0% that in but we're going to sort of 00:09:37.640 --> 00:09:39.310 align:start position:0% that in but we're going to sort of cleverly<00:09:38.120> add<00:09:38.320> that<00:09:38.480> in<00:09:38.680> in<00:09:38.839> the<00:09:38.959> correct 00:09:39.310 --> 00:09:39.320 align:start position:0% cleverly add that in in the correct 00:09:39.320 --> 00:09:43.150 align:start position:0% cleverly add that in in the correct Shard<00:09:40.640> so<00:09:41.640> what<00:09:41.800> I'm<00:09:42.120> basically<00:09:42.519> describing 00:09:43.150 --> 00:09:43.160 align:start position:0% Shard so what I'm basically describing 00:09:43.160 --> 00:09:47.750 align:start position:0% Shard so what I'm basically describing here<00:09:43.600> is<00:09:44.000> a<00:09:44.320> fairly<00:09:45.279> kind<00:09:45.399> of 00:09:47.750 --> 00:09:47.760 align:start position:0% 00:09:47.760 --> 00:09:51.190 align:start position:0% simple<00:09:48.760> sort<00:09:48.959> of<00:09:49.160> standard<00:09:50.000> approach<00:09:51.000> that 00:09:51.190 --> 00:09:51.200 align:start position:0% simple sort of standard approach that 00:09:51.200 --> 00:09:53.790 align:start position:0% simple sort of standard approach that lets<00:09:51.519> you<00:09:52.160> implement<00:09:52.680> a<00:09:52.800> sort<00:09:53.000> of<00:09:53.160> no.<00:09:53.360> JS 00:09:53.790 --> 00:09:53.800 align:start position:0% lets you implement a sort of no. JS 00:09:53.800 --> 00:09:55.949 align:start position:0% lets you implement a sort of no. JS style<00:09:54.360> asynchronous<00:09:54.959> programming<00:09:55.399> language 00:09:55.949 --> 00:09:55.959 align:start position:0% style asynchronous programming language 00:09:55.959 --> 00:09:59.509 align:start position:0% style asynchronous programming language on<00:09:56.160> top<00:09:56.560> on<00:09:56.800> top<00:09:57.000> of<00:09:57.680> this<00:09:57.800> sort<00:09:57.959> of<00:09:58.279> eum<00:09:58.680> 2.0 00:09:59.509 --> 00:09:59.519 align:start position:0% on top on top of this sort of eum 2.0 00:09:59.519 --> 00:10:02.710 align:start position:0% on top on top of this sort of eum 2.0 infrastructure<00:10:00.519> and<00:10:01.200> the<00:10:01.480> key<00:10:02.279> piece<00:10:02.600> that 00:10:02.710 --> 00:10:02.720 align:start position:0% infrastructure and the key piece that 00:10:02.720 --> 00:10:06.790 align:start position:0% infrastructure and the key piece that you<00:10:03.079> require<00:10:04.079> is<00:10:04.800> you<00:10:05.040> need<00:10:05.360> to<00:10:05.760> have 00:10:06.790 --> 00:10:06.800 align:start position:0% you require is you need to have 00:10:06.800 --> 00:10:10.069 align:start position:0% you require is you need to have transactions<00:10:07.800> have<00:10:08.160> access<00:10:08.600> to<00:10:09.200> Merkel<00:10:09.680> roots 00:10:10.069 --> 00:10:10.079 align:start position:0% transactions have access to Merkel roots 00:10:10.079 --> 00:10:13.269 align:start position:0% transactions have access to Merkel roots from<00:10:10.399> previous<00:10:10.839> blocks<00:10:11.800> so<00:10:12.440> transactions 00:10:13.269 --> 00:10:13.279 align:start position:0% from previous blocks so transactions 00:10:13.279 --> 00:10:15.630 align:start position:0% from previous blocks so transactions here<00:10:13.480> should<00:10:13.720> be<00:10:13.880> able<00:10:14.040> to<00:10:14.320> read<00:10:15.079> pre<00:10:15.440> the 00:10:15.630 --> 00:10:15.640 align:start position:0% here should be able to read pre the 00:10:15.640 --> 00:10:18.430 align:start position:0% here should be able to read pre the global<00:10:16.560> previous<00:10:16.920> state<00:10:17.160> route<00:10:17.480> Global<00:10:17.760> pre 00:10:18.430 --> 00:10:18.440 align:start position:0% global previous state route Global pre 00:10:18.440 --> 00:10:20.389 align:start position:0% global previous state route Global pre previous<00:10:18.800> transaction<00:10:19.279> group<00:10:19.519> route<00:10:20.240> now 00:10:20.389 --> 00:10:20.399 align:start position:0% previous transaction group route now 00:10:20.399 --> 00:10:21.829 align:start position:0% previous transaction group route now they<00:10:20.519> don't<00:10:20.680> need<00:10:20.880> to<00:10:21.040> be<00:10:21.120> able<00:10:21.279> to<00:10:21.440> modify 00:10:21.829 --> 00:10:21.839 align:start position:0% they don't need to be able to modify 00:10:21.839 --> 00:10:23.590 align:start position:0% they don't need to be able to modify anything<00:10:22.200> globally<00:10:22.760> they<00:10:22.920> just<00:10:23.120> needs<00:10:23.360> to 00:10:23.590 --> 00:10:23.600 align:start position:0% anything globally they just needs to 00:10:23.600 --> 00:10:26.829 align:start position:0% anything globally they just needs to read<00:10:24.200> a<00:10:24.399> historical<00:10:25.040> route<00:10:26.040> and<00:10:26.600> that's 00:10:26.829 --> 00:10:26.839 align:start position:0% read a historical route and that's 00:10:26.839 --> 00:10:28.710 align:start position:0% read a historical route and that's fairly<00:10:27.360> fairly<00:10:27.839> okay<00:10:28.079> it<00:10:28.200> doesn't<00:10:28.480> sort<00:10:28.600> of 00:10:28.710 --> 00:10:28.720 align:start position:0% fairly fairly okay it doesn't sort of 00:10:28.720 --> 00:10:30.829 align:start position:0% fairly fairly okay it doesn't sort of prevent<00:10:29.120> parallel<00:10:29.519> analysis<00:10:30.240> or<00:10:30.399> parallel 00:10:30.829 --> 00:10:30.839 align:start position:0% prevent parallel analysis or parallel 00:10:30.839 --> 00:10:34.630 align:start position:0% prevent parallel analysis or parallel computation<00:10:31.519> at<00:10:31.880> all<00:10:33.040> now<00:10:34.040> what<00:10:34.160> you<00:10:34.360> have 00:10:34.630 --> 00:10:34.640 align:start position:0% computation at all now what you have 00:10:34.640 --> 00:10:37.310 align:start position:0% computation at all now what you have here<00:10:34.920> is<00:10:35.519> let's<00:10:35.839> just<00:10:36.040> go<00:10:36.200> through<00:10:36.399> a<00:10:36.560> fairly<00:10:37.160> a 00:10:37.310 --> 00:10:37.320 align:start position:0% here is let's just go through a fairly a 00:10:37.320 --> 00:10:39.990 align:start position:0% here is let's just go through a fairly a fairly<00:10:37.720> sort<00:10:37.880> of<00:10:38.279> uh<00:10:39.040> somewhat<00:10:39.440> involved 00:10:39.990 --> 00:10:40.000 align:start position:0% fairly sort of uh somewhat involved 00:10:40.000 --> 00:10:42.269 align:start position:0% fairly sort of uh somewhat involved example<00:10:40.519> it's<00:10:40.800> involved<00:10:41.399> enough<00:10:41.639> to<00:10:41.880> capture 00:10:42.269 --> 00:10:42.279 align:start position:0% example it's involved enough to capture 00:10:42.279 --> 00:10:44.150 align:start position:0% example it's involved enough to capture all<00:10:42.399> the<00:10:42.560> nuances<00:10:43.240> but<00:10:43.360> it's<00:10:43.560> still<00:10:43.760> sort<00:10:43.959> of 00:10:44.150 --> 00:10:44.160 align:start position:0% all the nuances but it's still sort of 00:10:44.160 --> 00:10:45.629 align:start position:0% all the nuances but it's still sort of as<00:10:44.279> simple<00:10:44.600> as<00:10:44.680> it<00:10:44.839> can<00:10:45.000> be<00:10:45.200> within<00:10:45.440> that 00:10:45.629 --> 00:10:45.639 align:start position:0% as simple as it can be within that 00:10:45.639 --> 00:10:49.110 align:start position:0% as simple as it can be within that context<00:10:46.600> so<00:10:47.560> suppose<00:10:48.040> that<00:10:48.160> you're<00:10:48.440> trying<00:10:48.760> to 00:10:49.110 --> 00:10:49.120 align:start position:0% context so suppose that you're trying to 00:10:49.120 --> 00:10:51.670 align:start position:0% context so suppose that you're trying to register<00:10:49.519> a<00:10:49.720> domain<00:10:50.040> name<00:10:50.839> and<00:10:51.160> this<00:10:51.320> domain 00:10:51.670 --> 00:10:51.680 align:start position:0% register a domain name and this domain 00:10:51.680 --> 00:10:55.269 align:start position:0% register a domain name and this domain regist<00:10:52.600> is<00:10:53.440> so<00:10:54.000> devilishly<00:10:54.600> evil<00:10:54.959> that<00:10:55.079> it 00:10:55.269 --> 00:10:55.279 align:start position:0% regist is so devilishly evil that it 00:10:55.279 --> 00:10:59.190 align:start position:0% regist is so devilishly evil that it only<00:10:55.639> accepts<00:10:56.120> gaav<00:10:56.399> coin<00:10:56.639> as<00:10:57.200> payment<00:10:58.200> so<00:10:59.040> the 00:10:59.190 --> 00:10:59.200 align:start position:0% only accepts gaav coin as payment so the 00:10:59.200 --> 00:11:02.829 align:start position:0% only accepts gaav coin as payment so the domain<00:10:59.519> regist<00:11:00.079> lives<00:11:00.320> in<00:11:00.440> Shard<00:11:01.160> 43<00:11:02.160> and<00:11:02.480> Gaff 00:11:02.829 --> 00:11:02.839 align:start position:0% domain regist lives in Shard 43 and Gaff 00:11:02.839 --> 00:11:05.110 align:start position:0% domain regist lives in Shard 43 and Gaff coin<00:11:03.120> lives<00:11:03.360> in<00:11:03.519> Shard 00:11:05.110 --> 00:11:05.120 align:start position:0% coin lives in Shard 00:11:05.120 --> 00:11:07.470 align:start position:0% coin lives in Shard 666 00:11:07.470 --> 00:11:07.480 align:start position:0% 666 00:11:07.480 --> 00:11:10.710 align:start position:0% 666 so<00:11:08.480> so<00:11:08.720> the<00:11:08.880> problem<00:11:09.279> is<00:11:09.600> that<00:11:09.880> now<00:11:10.519> this 00:11:10.710 --> 00:11:10.720 align:start position:0% so so the problem is that now this 00:11:10.720 --> 00:11:16.389 align:start position:0% so so the problem is that now this registar<00:11:11.480> charges<00:11:12.079> a<00:11:12.720> fee<00:11:14.160> and<00:11:15.160> so<00:11:15.920> problem<00:11:16.279> is 00:11:16.389 --> 00:11:16.399 align:start position:0% registar charges a fee and so problem is 00:11:16.399 --> 00:11:18.190 align:start position:0% registar charges a fee and so problem is you<00:11:16.560> know<00:11:16.760> let's<00:11:16.959> say<00:11:17.279> I<00:11:17.480> want<00:11:17.760> let's<00:11:17.920> say<00:11:18.079> the 00:11:18.190 --> 00:11:18.200 align:start position:0% you know let's say I want let's say the 00:11:18.200 --> 00:11:21.030 align:start position:0% you know let's say I want let's say the fee<00:11:18.480> is<00:11:18.639> 20<00:11:18.959> Gaff<00:11:19.200> coin<00:11:19.800> let's<00:11:20.000> say<00:11:20.320> I<00:11:20.480> wants<00:11:20.760> to 00:11:21.030 --> 00:11:21.040 align:start position:0% fee is 20 Gaff coin let's say I wants to 00:11:21.040 --> 00:11:23.949 align:start position:0% fee is 20 Gaff coin let's say I wants to make<00:11:21.160> a<00:11:21.360> transaction<00:11:22.200> which<00:11:23.160> you<00:11:23.279> know<00:11:23.519> pay 00:11:23.949 --> 00:11:23.959 align:start position:0% make a transaction which you know pay 00:11:23.959 --> 00:11:27.190 align:start position:0% make a transaction which you know pay reg<00:11:24.720> pays<00:11:24.959> the<00:11:25.120> 20<00:11:25.440> Gaff<00:11:25.639> coin<00:11:25.920> registers<00:11:26.360> a<00:11:26.600> do 00:11:27.190 --> 00:11:27.200 align:start position:0% reg pays the 20 Gaff coin registers a do 00:11:27.200 --> 00:11:29.790 align:start position:0% reg pays the 20 Gaff coin registers a do and<00:11:27.480> registers<00:11:27.920> the<00:11:28.120> domain<00:11:29.120> how<00:11:29.279> does<00:11:29.519> this 00:11:29.790 --> 00:11:29.800 align:start position:0% and registers the domain how does this 00:11:29.800 --> 00:11:32.509 align:start position:0% and registers the domain how does this this<00:11:29.959> sort<00:11:30.079> of<00:11:30.279> Ensemble<00:11:31.000> of<00:11:31.560> the<00:11:31.839> registar 00:11:32.509 --> 00:11:32.519 align:start position:0% this sort of Ensemble of the registar 00:11:32.519 --> 00:11:35.110 align:start position:0% this sort of Ensemble of the registar and<00:11:32.800> Gaff<00:11:33.079> coin<00:11:33.440> actually<00:11:33.720> verify<00:11:34.200> everything 00:11:35.110 --> 00:11:35.120 align:start position:0% and Gaff coin actually verify everything 00:11:35.120 --> 00:11:39.470 align:start position:0% and Gaff coin actually verify everything so<00:11:36.120> in<00:11:36.360> general<00:11:36.839> the<00:11:37.000> sort<00:11:37.399> of<00:11:38.399> the<00:11:38.839> the<00:11:39.040> most 00:11:39.470 --> 00:11:39.480 align:start position:0% so in general the sort of the the most 00:11:39.480 --> 00:11:41.990 align:start position:0% so in general the sort of the the most kind<00:11:39.600> of<00:11:39.800> standard<00:11:40.320> approach<00:11:40.720> so<00:11:41.000> far<00:11:41.200> for 00:11:41.990 --> 00:11:42.000 align:start position:0% kind of standard approach so far for 00:11:42.000 --> 00:11:45.509 align:start position:0% kind of standard approach so far for contracts<00:11:42.680> charging<00:11:43.639> users<00:11:44.200> crypto<00:11:45.200> sub 00:11:45.509 --> 00:11:45.519 align:start position:0% contracts charging users crypto sub 00:11:45.519 --> 00:11:46.990 align:start position:0% contracts charging users crypto sub currencies<00:11:46.040> in<00:11:46.160> order<00:11:46.360> to<00:11:46.560> actually<00:11:46.800> make 00:11:46.990 --> 00:11:47.000 align:start position:0% currencies in order to actually make 00:11:47.000 --> 00:11:48.910 align:start position:0% currencies in order to actually make payments<00:11:47.440> is<00:11:47.560> a<00:11:47.720> sort<00:11:47.880> of<00:11:48.040> two-step<00:11:48.519> receipt 00:11:48.910 --> 00:11:48.920 align:start position:0% payments is a sort of two-step receipt 00:11:48.920 --> 00:11:51.030 align:start position:0% payments is a sort of two-step receipt approach<00:11:49.880> where<00:11:50.079> fir<00:11:50.320> where<00:11:50.480> the<00:11:50.600> first<00:11:50.800> step 00:11:51.030 --> 00:11:51.040 align:start position:0% approach where fir where the first step 00:11:51.040 --> 00:11:52.590 align:start position:0% approach where fir where the first step is<00:11:51.160> you<00:11:51.279> send<00:11:51.560> a<00:11:51.760> transaction<00:11:52.279> to<00:11:52.440> the 00:11:52.590 --> 00:11:52.600 align:start position:0% is you send a transaction to the 00:11:52.600 --> 00:11:55.069 align:start position:0% is you send a transaction to the currency<00:11:53.600> and<00:11:53.720> you<00:11:53.880> kind<00:11:54.000> of<00:11:54.279> authorize<00:11:54.959> the 00:11:55.069 --> 00:11:55.079 align:start position:0% currency and you kind of authorize the 00:11:55.079 --> 00:11:57.230 align:start position:0% currency and you kind of authorize the other<00:11:55.399> contract<00:11:55.800> as<00:11:55.920> a<00:11:56.079> withdrawer<00:11:57.040> and<00:11:57.120> then 00:11:57.230 --> 00:11:57.240 align:start position:0% other contract as a withdrawer and then 00:11:57.240 --> 00:11:59.430 align:start position:0% other contract as a withdrawer and then you<00:11:57.320> send<00:11:57.600> another<00:11:57.880> transaction<00:11:58.320> to<00:11:58.519> withdraw 00:11:59.430 --> 00:11:59.440 align:start position:0% you send another transaction to withdraw 00:11:59.440 --> 00:12:00.910 align:start position:0% you send another transaction to withdraw and<00:11:59.519> then<00:11:59.680> the<00:11:59.839> contract<00:12:00.320> sort<00:12:00.440> of<00:12:00.639> actually 00:12:00.910 --> 00:12:00.920 align:start position:0% and then the contract sort of actually 00:12:00.920 --> 00:12:02.470 align:start position:0% and then the contract sort of actually debits<00:12:01.279> out<00:12:01.519> sort<00:12:01.680> of<00:12:01.800> debits<00:12:02.120> out<00:12:02.240> of<00:12:02.360> your 00:12:02.470 --> 00:12:02.480 align:start position:0% debits out sort of debits out of your 00:12:02.480 --> 00:12:05.430 align:start position:0% debits out sort of debits out of your bank<00:12:02.760> account<00:12:03.760> so<00:12:04.760> this<00:12:04.880> is<00:12:05.079> something<00:12:05.320> that 00:12:05.430 --> 00:12:05.440 align:start position:0% bank account so this is something that 00:12:05.440 --> 00:12:07.190 align:start position:0% bank account so this is something that we're<00:12:05.560> going<00:12:05.639> to<00:12:05.760> be<00:12:06.279> discussing<00:12:06.800> probably<00:12:07.079> in 00:12:07.190 --> 00:12:07.200 align:start position:0% we're going to be discussing probably in 00:12:07.200 --> 00:12:09.509 align:start position:0% we're going to be discussing probably in more<00:12:07.480> detail<00:12:08.240> uh<00:12:08.519> over<00:12:08.680> the<00:12:08.839> next<00:12:09.040> few<00:12:09.279> days 00:12:09.509 --> 00:12:09.519 align:start position:0% more detail uh over the next few days 00:12:09.519 --> 00:12:11.110 align:start position:0% more detail uh over the next few days and<00:12:09.720> things<00:12:10.000> like<00:12:10.120> the<00:12:10.279> standard<00:12:10.680> contract 00:12:11.110 --> 00:12:11.120 align:start position:0% and things like the standard contract 00:12:11.120 --> 00:12:14.150 align:start position:0% and things like the standard contract interfaces<00:12:11.680> panel<00:12:12.160> but<00:12:12.920> it's<00:12:13.720> roughly<00:12:14.040> the 00:12:14.150 --> 00:12:14.160 align:start position:0% interfaces panel but it's roughly the 00:12:14.160 --> 00:12:16.629 align:start position:0% interfaces panel but it's roughly the approach<00:12:14.519> right<00:12:14.680> now<00:12:15.079> so<00:12:16.040> over<00:12:16.320> here<00:12:16.519> what 00:12:16.629 --> 00:12:16.639 align:start position:0% approach right now so over here what 00:12:16.639 --> 00:12:19.110 align:start position:0% approach right now so over here what we're<00:12:16.760> going<00:12:16.839> to<00:12:17.040> do<00:12:17.399> is<00:12:17.720> we're<00:12:17.920> going<00:12:18.079> to<00:12:18.440> call 00:12:19.110 --> 00:12:19.120 align:start position:0% we're going to do is we're going to call 00:12:19.120 --> 00:12:22.430 align:start position:0% we're going to do is we're going to call the<00:12:19.279> function<00:12:19.800> of<00:12:20.000> the<00:12:20.120> name<00:12:20.720> register<00:12:21.720> and 00:12:22.430 --> 00:12:22.440 align:start position:0% the function of the name register and 00:12:22.440 --> 00:12:24.710 align:start position:0% the function of the name register and you<00:12:22.560> know<00:12:22.680> we're<00:12:22.839> going<00:12:22.959> to<00:12:23.279> say<00:12:24.279> what<00:12:24.639> what 00:12:24.710 --> 00:12:24.720 align:start position:0% you know we're going to say what what 00:12:24.720 --> 00:12:25.870 align:start position:0% you know we're going to say what what we're<00:12:24.880> going<00:12:24.959> to<00:12:25.079> say<00:12:25.240> is<00:12:25.360> we<00:12:25.480> want<00:12:25.680> to 00:12:25.870 --> 00:12:25.880 align:start position:0% we're going to say is we want to 00:12:25.880 --> 00:12:27.990 align:start position:0% we're going to say is we want to register<00:12:26.360> a<00:12:26.560> domain<00:12:26.880> with<00:12:27.040> some<00:12:27.320> name<00:12:27.760> we<00:12:27.880> want 00:12:27.990 --> 00:12:28.000 align:start position:0% register a domain with some name we want 00:12:28.000 --> 00:12:30.110 align:start position:0% register a domain with some name we want to<00:12:28.199> provide<00:12:28.600> you<00:12:28.680> know<00:12:29.000> what<00:12:29.160> fee<00:12:29.480> we<00:12:29.639> want<00:12:29.920> to 00:12:30.110 --> 00:12:30.120 align:start position:0% to provide you know what fee we want to 00:12:30.120 --> 00:12:32.189 align:start position:0% to provide you know what fee we want to provide<00:12:31.120> and<00:12:31.320> we're<00:12:31.480> going<00:12:31.560> to<00:12:31.760> provide<00:12:32.079> the 00:12:32.189 --> 00:12:32.199 align:start position:0% provide and we're going to provide the 00:12:32.199 --> 00:12:34.110 align:start position:0% provide and we're going to provide the currency<00:12:32.519> Shard<00:12:32.800> and<00:12:32.880> the<00:12:32.959> currency<00:12:33.440> address 00:12:34.110 --> 00:12:34.120 align:start position:0% currency Shard and the currency address 00:12:34.120 --> 00:12:36.110 align:start position:0% currency Shard and the currency address so<00:12:34.320> basically<00:12:34.720> where<00:12:34.959> Gaff<00:12:35.199> coin 00:12:36.110 --> 00:12:36.120 align:start position:0% so basically where Gaff coin 00:12:36.120 --> 00:12:39.189 align:start position:0% so basically where Gaff coin lives<00:12:37.199> so<00:12:38.199> what<00:12:38.279> it's<00:12:38.440> going<00:12:38.519> to<00:12:38.680> do<00:12:38.880> is<00:12:39.000> it's 00:12:39.189 --> 00:12:39.199 align:start position:0% lives so what it's going to do is it's 00:12:39.199 --> 00:12:41.710 align:start position:0% lives so what it's going to do is it's going<00:12:39.320> to<00:12:39.560> register<00:12:39.959> a<00:12:40.120> call<00:12:40.360> back<00:12:40.600> ID<00:12:41.560> and 00:12:41.710 --> 00:12:41.720 align:start position:0% going to register a call back ID and 00:12:41.720 --> 00:12:44.030 align:start position:0% going to register a call back ID and then<00:12:41.880> it's<00:12:42.000> going<00:12:42.160> to<00:12:42.320> create<00:12:42.600> a<00:12:42.800> log<00:12:43.600> and<00:12:43.800> this 00:12:44.030 --> 00:12:44.040 align:start position:0% then it's going to create a log and this 00:12:44.040 --> 00:12:45.870 align:start position:0% then it's going to create a log and this log<00:12:44.440> is<00:12:44.639> basically<00:12:45.079> going<00:12:45.199> to<00:12:45.360> contain<00:12:45.720> all 00:12:45.870 --> 00:12:45.880 align:start position:0% log is basically going to contain all 00:12:45.880 --> 00:12:48.269 align:start position:0% log is basically going to contain all the<00:12:46.040> information<00:12:46.920> so<00:12:47.079> it's<00:12:47.199> going<00:12:47.279> to<00:12:47.480> contain 00:12:48.269 --> 00:12:48.279 align:start position:0% the information so it's going to contain 00:12:48.279 --> 00:12:50.350 align:start position:0% the information so it's going to contain the<00:12:48.440> destination<00:12:48.959> Shard<00:12:49.639> the<00:12:49.760> destination 00:12:50.350 --> 00:12:50.360 align:start position:0% the destination Shard the destination 00:12:50.360 --> 00:12:52.350 align:start position:0% the destination Shard the destination address<00:12:51.000> so<00:12:51.120> it's<00:12:51.320> basically<00:12:51.680> so<00:12:51.839> the<00:12:52.000> log<00:12:52.240> is 00:12:52.350 --> 00:12:52.360 align:start position:0% address so it's basically so the log is 00:12:52.360 --> 00:12:54.710 align:start position:0% address so it's basically so the log is going<00:12:52.480> to<00:12:52.639> say<00:12:53.040> this<00:12:53.199> log<00:12:53.480> is<00:12:53.639> addressed<00:12:53.959> to 00:12:54.710 --> 00:12:54.720 align:start position:0% going to say this log is addressed to 00:12:54.720 --> 00:12:57.990 align:start position:0% going to say this log is addressed to gcoin<00:12:55.720> then<00:12:55.839> it's<00:12:56.000> going<00:12:56.160> to<00:12:56.360> say<00:12:57.000> what<00:12:57.240> method 00:12:57.990 --> 00:12:58.000 align:start position:0% gcoin then it's going to say what method 00:12:58.000 --> 00:13:00.310 align:start position:0% gcoin then it's going to say what method is<00:12:58.199> being<00:12:58.560> is<00:12:58.680> being<00:12:58.839> being<00:12:59.040> called<00:12:59.399> here<00:12:59.760> so 00:13:00.310 --> 00:13:00.320 align:start position:0% is being is being being called here so 00:13:00.320 --> 00:13:02.710 align:start position:0% is being is being being called here so in<00:13:00.519> this<00:13:00.720> case<00:13:01.320> this<00:13:01.519> contract<00:13:02.040> wants<00:13:02.279> to<00:13:02.480> call 00:13:02.710 --> 00:13:02.720 align:start position:0% in this case this contract wants to call 00:13:02.720 --> 00:13:04.629 align:start position:0% in this case this contract wants to call the<00:13:02.839> method<00:13:03.120> withdraw<00:13:03.680> it<00:13:03.760> wants<00:13:03.959> to<00:13:04.160> withdraw 00:13:04.629 --> 00:13:04.639 align:start position:0% the method withdraw it wants to withdraw 00:13:04.639 --> 00:13:07.430 align:start position:0% the method withdraw it wants to withdraw 20<00:13:05.000> Gaff<00:13:05.240> coin<00:13:05.600> from<00:13:05.880> my<00:13:06.079> account<00:13:07.079> and<00:13:07.279> the 00:13:07.430 --> 00:13:07.440 align:start position:0% 20 Gaff coin from my account and the 00:13:07.440 --> 00:13:10.910 align:start position:0% 20 Gaff coin from my account and the arguments<00:13:07.959> are<00:13:08.639> from<00:13:09.240> me<00:13:10.040> to<00:13:10.519> the<00:13:10.639> name 00:13:10.910 --> 00:13:10.920 align:start position:0% arguments are from me to the name 00:13:10.920 --> 00:13:14.269 align:start position:0% arguments are from me to the name registry<00:13:11.639> and<00:13:11.800> the<00:13:11.959> value<00:13:12.360> 20<00:13:12.720> Gaff<00:13:13.120> coin<00:13:14.120> and 00:13:14.269 --> 00:13:14.279 align:start position:0% registry and the value 20 Gaff coin and 00:13:14.279 --> 00:13:16.350 align:start position:0% registry and the value 20 Gaff coin and it's<00:13:14.399> going<00:13:14.480> to<00:13:14.639> say<00:13:15.160> if<00:13:15.360> this<00:13:15.519> suce<00:13:16.000> after 00:13:16.350 --> 00:13:16.360 align:start position:0% it's going to say if this suce after 00:13:16.360 --> 00:13:18.189 align:start position:0% it's going to say if this suce after this<00:13:16.480> is<00:13:16.639> all<00:13:16.920> this<00:13:17.040> all<00:13:17.240> happens<00:13:17.920> it's<00:13:18.079> going 00:13:18.189 --> 00:13:18.199 align:start position:0% this is all this all happens it's going 00:13:18.199 --> 00:13:19.750 align:start position:0% this is all this all happens it's going to<00:13:18.320> go<00:13:18.399> to<00:13:18.519> a<00:13:18.680> call<00:13:18.920> back<00:13:19.120> method<00:13:19.399> which<00:13:19.519> is<00:13:19.639> the 00:13:19.750 --> 00:13:19.760 align:start position:0% to go to a call back method which is the 00:13:19.760 --> 00:13:22.350 align:start position:0% to go to a call back method which is the withdraw<00:13:20.240> call<00:13:20.600> back<00:13:21.600> and<00:13:21.839> it's<00:13:22.000> going<00:13:22.079> to 00:13:22.350 --> 00:13:22.360 align:start position:0% withdraw call back and it's going to 00:13:22.360 --> 00:13:24.910 align:start position:0% withdraw call back and it's going to give<00:13:22.480> it<00:13:22.600> the<00:13:22.800> Callback<00:13:23.160> ID<00:13:24.040> now<00:13:24.279> over<00:13:24.560> here 00:13:24.910 --> 00:13:24.920 align:start position:0% give it the Callback ID now over here 00:13:24.920 --> 00:13:27.590 align:start position:0% give it the Callback ID now over here I'm<00:13:25.120> also<00:13:25.480> going<00:13:25.680> to<00:13:26.360> in<00:13:26.639> the<00:13:26.760> name<00:13:27.000> register's 00:13:27.590 --> 00:13:27.600 align:start position:0% I'm also going to in the name register's 00:13:27.600 --> 00:13:29.389 align:start position:0% I'm also going to in the name register's own<00:13:27.959> storage 00:13:29.389 --> 00:13:29.399 align:start position:0% own storage 00:13:29.399 --> 00:13:31.269 align:start position:0% own storage basically<00:13:29.880> provide<00:13:30.320> some<00:13:30.600> information 00:13:31.269 --> 00:13:31.279 align:start position:0% basically provide some information 00:13:31.279 --> 00:13:33.790 align:start position:0% basically provide some information saying<00:13:32.240> hey<00:13:32.440> look<00:13:32.720> there<00:13:32.920> is<00:13:33.160> this<00:13:33.360> call<00:13:33.560> back 00:13:33.790 --> 00:13:33.800 align:start position:0% saying hey look there is this call back 00:13:33.800 --> 00:13:35.990 align:start position:0% saying hey look there is this call back that's<00:13:34.000> in<00:13:34.360> that<00:13:34.639> that's<00:13:35.160> being<00:13:35.639> happening 00:13:35.990 --> 00:13:36.000 align:start position:0% that's in that that's being happening 00:13:36.000 --> 00:13:39.269 align:start position:0% that's in that that's being happening and<00:13:36.120> it's<00:13:36.279> in<00:13:36.480> progress<00:13:36.959> right<00:13:37.440> now<00:13:38.440> step<00:13:38.720> two 00:13:39.269 --> 00:13:39.279 align:start position:0% and it's in progress right now step two 00:13:39.279 --> 00:13:42.310 align:start position:0% and it's in progress right now step two on<00:13:39.440> the<00:13:39.639> Gaff<00:13:39.880> coin<00:13:40.160> side<00:13:40.680> so<00:13:40.959> I<00:13:41.160> made<00:13:41.720> step<00:13:41.959> one 00:13:42.310 --> 00:13:42.320 align:start position:0% on the Gaff coin side so I made step one 00:13:42.320 --> 00:13:45.110 align:start position:0% on the Gaff coin side so I made step one I<00:13:42.399> set<00:13:42.639> this<00:13:42.800> transaction<00:13:43.399> on<00:13:43.560> Shard<00:13:43.959> 43<00:13:44.959> it 00:13:45.110 --> 00:13:45.120 align:start position:0% I set this transaction on Shard 43 it 00:13:45.120 --> 00:13:48.350 align:start position:0% I set this transaction on Shard 43 it happened<00:13:45.480> it<00:13:45.600> created<00:13:45.880> a<00:13:46.040> log<00:13:46.920> now<00:13:47.639> now 00:13:48.350 --> 00:13:48.360 align:start position:0% happened it created a log now now 00:13:48.360 --> 00:13:50.749 align:start position:0% happened it created a log now now unfortunately<00:13:49.360> this<00:13:49.519> isn't<00:13:49.760> a<00:13:49.880> theorem<00:13:50.240> 1.0 00:13:50.749 --> 00:13:50.759 align:start position:0% unfortunately this isn't a theorem 1.0 00:13:50.759 --> 00:13:52.230 align:start position:0% unfortunately this isn't a theorem 1.0 anymore<00:13:51.120> where<00:13:51.279> like<00:13:51.440> all<00:13:51.560> the<00:13:51.680> messages 00:13:52.230 --> 00:13:52.240 align:start position:0% anymore where like all the messages 00:13:52.240 --> 00:13:55.189 align:start position:0% anymore where like all the messages happen<00:13:52.880> automatically<00:13:53.880> in<00:13:54.519> asynchronous 00:13:55.189 --> 00:13:55.199 align:start position:0% happen automatically in asynchronous 00:13:55.199 --> 00:13:57.150 align:start position:0% happen automatically in asynchronous programming<00:13:56.079> this<00:13:56.320> is<00:13:56.480> also<00:13:56.680> going<00:13:56.839> to<00:13:56.959> be<00:13:57.040> a 00:13:57.150 --> 00:13:57.160 align:start position:0% programming this is also going to be a 00:13:57.160 --> 00:13:59.590 align:start position:0% programming this is also going to be a second<00:13:57.480> transaction<00:13:58.079> you<00:13:58.240> have<00:13:58.360> to<00:13:58.480> send<00:13:58.920> it 00:13:59.590 --> 00:13:59.600 align:start position:0% second transaction you have to send it 00:13:59.600 --> 00:14:02.550 align:start position:0% second transaction you have to send it so<00:14:00.279> you<00:14:00.480> send<00:14:00.680> a<00:14:01.000> transaction<00:14:02.000> and<00:14:02.199> what<00:14:02.360> this 00:14:02.550 --> 00:14:02.560 align:start position:0% so you send a transaction and what this 00:14:02.560 --> 00:14:04.550 align:start position:0% so you send a transaction and what this transaction<00:14:03.199> is<00:14:03.440> is<00:14:03.600> it's<00:14:03.759> going<00:14:03.920> to 00:14:04.550 --> 00:14:04.560 align:start position:0% transaction is is it's going to 00:14:04.560 --> 00:14:07.910 align:start position:0% transaction is is it's going to basically<00:14:05.560> all<00:14:05.720> that<00:14:05.880> it<00:14:06.120> contains<00:14:07.120> is<00:14:07.399> a<00:14:07.560> log 00:14:07.910 --> 00:14:07.920 align:start position:0% basically all that it contains is a log 00:14:07.920 --> 00:14:09.910 align:start position:0% basically all that it contains is a log proof<00:14:08.240> it's<00:14:08.399> just<00:14:08.560> going<00:14:08.639> to<00:14:08.839> contain<00:14:09.720> this 00:14:09.910 --> 00:14:09.920 align:start position:0% proof it's just going to contain this 00:14:09.920 --> 00:14:12.389 align:start position:0% proof it's just going to contain this Merkel<00:14:10.399> proof<00:14:11.040> of<00:14:11.240> the<00:14:11.440> log<00:14:11.800> that<00:14:11.920> was<00:14:12.040> created 00:14:12.389 --> 00:14:12.399 align:start position:0% Merkel proof of the log that was created 00:14:12.399 --> 00:14:14.870 align:start position:0% Merkel proof of the log that was created in<00:14:12.560> step<00:14:13.040> one 00:14:14.870 --> 00:14:14.880 align:start position:0% in step one 00:14:14.880 --> 00:14:17.230 align:start position:0% in step one so<00:14:15.880> what<00:14:16.040> this<00:14:16.199> contract<00:14:16.560> is<00:14:16.680> going<00:14:16.759> to<00:14:16.920> do<00:14:17.120> is 00:14:17.230 --> 00:14:17.240 align:start position:0% so what this contract is going to do is 00:14:17.240 --> 00:14:20.069 align:start position:0% so what this contract is going to do is it's<00:14:17.360> going<00:14:17.480> to<00:14:17.639> check<00:14:17.839> the<00:14:17.920> Merle<00:14:18.360> proof<00:14:19.360> and 00:14:20.069 --> 00:14:20.079 align:start position:0% it's going to check the Merle proof and 00:14:20.079 --> 00:14:21.870 align:start position:0% it's going to check the Merle proof and it's<00:14:20.320> going<00:14:20.440> to<00:14:20.720> verify<00:14:21.279> that<00:14:21.399> the<00:14:21.480> Merle 00:14:21.870 --> 00:14:21.880 align:start position:0% it's going to verify that the Merle 00:14:21.880 --> 00:14:23.910 align:start position:0% it's going to verify that the Merle proof<00:14:22.160> is 00:14:23.910 --> 00:14:23.920 align:start position:0% proof is 00:14:23.920 --> 00:14:27.910 align:start position:0% proof is actually<00:14:24.920> is<00:14:25.560> actually<00:14:26.199> addressed<00:14:27.079> to<00:14:27.600> Gaff 00:14:27.910 --> 00:14:27.920 align:start position:0% actually is actually addressed to Gaff 00:14:27.920 --> 00:14:31.350 align:start position:0% actually is actually addressed to Gaff coin<00:14:29.120> and<00:14:29.720> it's<00:14:29.959> also<00:14:30.279> going<00:14:30.399> to<00:14:30.600> verify<00:14:31.160> that 00:14:31.350 --> 00:14:31.360 align:start position:0% coin and it's also going to verify that 00:14:31.360 --> 00:14:33.230 align:start position:0% coin and it's also going to verify that this<00:14:31.600> particular<00:14:32.079> log<00:14:32.440> has<00:14:32.639> not<00:14:32.839> yet<00:14:33.040> been 00:14:33.230 --> 00:14:33.240 align:start position:0% this particular log has not yet been 00:14:33.240 --> 00:14:36.710 align:start position:0% this particular log has not yet been submitted<00:14:34.199> so<00:14:34.440> in<00:14:34.639> Shard<00:14:35.360> 666<00:14:36.360> it<00:14:36.480> now 00:14:36.710 --> 00:14:36.720 align:start position:0% submitted so in Shard 666 it now 00:14:36.720 --> 00:14:38.670 align:start position:0% submitted so in Shard 666 it now maintains<00:14:37.079> a<00:14:37.279> record<00:14:37.639> of<00:14:37.800> whether<00:14:38.000> or<00:14:38.199> not 00:14:38.670 --> 00:14:38.680 align:start position:0% maintains a record of whether or not 00:14:38.680 --> 00:14:41.189 align:start position:0% maintains a record of whether or not this<00:14:38.880> particular<00:14:39.680> callback<00:14:40.120> ID<00:14:40.519> has<00:14:40.680> been 00:14:41.189 --> 00:14:41.199 align:start position:0% this particular callback ID has been 00:14:41.199 --> 00:14:45.590 align:start position:0% this particular callback ID has been spent<00:14:42.279> so<00:14:43.279> then<00:14:43.440> it<00:14:43.600> said<00:14:43.839> spent<00:14:44.199> to<00:14:44.399> true<00:14:45.360> and 00:14:45.590 --> 00:14:45.600 align:start position:0% spent so then it said spent to true and 00:14:45.600 --> 00:14:47.710 align:start position:0% spent so then it said spent to true and it<00:14:45.759> calls<00:14:46.079> its<00:14:46.199> own<00:14:46.440> method<00:14:46.959> so<00:14:47.399> in<00:14:47.519> this 00:14:47.710 --> 00:14:47.720 align:start position:0% it calls its own method so in this 00:14:47.720 --> 00:14:49.110 align:start position:0% it calls its own method so in this particular<00:14:48.199> case<00:14:48.399> you<00:14:48.519> know<00:14:48.639> the<00:14:48.759> method 00:14:49.110 --> 00:14:49.120 align:start position:0% particular case you know the method 00:14:49.120 --> 00:14:51.629 align:start position:0% particular case you know the method could<00:14:49.320> be<00:14:49.920> could<00:14:50.079> be<00:14:50.240> whatever<00:14:50.600> it<00:14:50.800> could<00:14:51.040> be 00:14:51.629 --> 00:14:51.639 align:start position:0% could be could be whatever it could be 00:14:51.639 --> 00:14:53.030 align:start position:0% could be could be whatever it could be well<00:14:51.920> in<00:14:52.040> this<00:14:52.199> case<00:14:52.399> it's<00:14:52.560> actually<00:14:52.839> going<00:14:52.959> to 00:14:53.030 --> 00:14:53.040 align:start position:0% well in this case it's actually going to 00:14:53.040 --> 00:14:54.910 align:start position:0% well in this case it's actually going to be<00:14:53.199> processing<00:14:53.639> the<00:14:53.759> withdrawal<00:14:54.600> so<00:14:54.759> it's 00:14:54.910 --> 00:14:54.920 align:start position:0% be processing the withdrawal so it's 00:14:54.920 --> 00:14:57.430 align:start position:0% be processing the withdrawal so it's going<00:14:55.040> to<00:14:55.160> be<00:14:55.320> checking<00:14:56.160> number<00:14:56.480> one<00:14:56.800> is<00:14:57.000> the 00:14:57.430 --> 00:14:57.440 align:start position:0% going to be checking number one is the 00:14:57.440 --> 00:15:00.110 align:start position:0% going to be checking number one is the have<00:14:57.759> I<00:14:58.040> authorized<00:14:58.519> the<00:14:58.759> registra<00:14:59.320> to<00:14:59.519> todraw 00:15:00.110 --> 00:15:00.120 align:start position:0% have I authorized the registra to todraw 00:15:00.120 --> 00:15:02.430 align:start position:0% have I authorized the registra to todraw my<00:15:00.279> Gaff<00:15:00.519> coin<00:15:01.279> number<00:15:01.519> two<00:15:01.759> do<00:15:01.880> I<00:15:02.000> have<00:15:02.199> enough 00:15:02.430 --> 00:15:02.440 align:start position:0% my Gaff coin number two do I have enough 00:15:02.440 --> 00:15:04.870 align:start position:0% my Gaff coin number two do I have enough balance<00:15:03.279> and<00:15:03.440> if<00:15:03.600> both<00:15:03.759> of<00:15:03.880> those<00:15:04.040> are<00:15:04.240> true 00:15:04.870 --> 00:15:04.880 align:start position:0% balance and if both of those are true 00:15:04.880 --> 00:15:06.389 align:start position:0% balance and if both of those are true then<00:15:05.040> it's<00:15:05.240> going<00:15:05.360> to<00:15:05.720> it's<00:15:05.839> going<00:15:05.959> to<00:15:06.120> debit 00:15:06.389 --> 00:15:06.399 align:start position:0% then it's going to it's going to debit 00:15:06.399 --> 00:15:07.949 align:start position:0% then it's going to it's going to debit my<00:15:06.560> gcoin<00:15:07.000> balance<00:15:07.360> it's<00:15:07.480> going<00:15:07.600> to<00:15:07.720> give<00:15:07.880> the 00:15:07.949 --> 00:15:07.959 align:start position:0% my gcoin balance it's going to give the 00:15:07.959 --> 00:15:11.269 align:start position:0% my gcoin balance it's going to give the name<00:15:08.160> register<00:15:08.519> on<00:15:08.680> my<00:15:08.839> Gaff<00:15:09.079> coin<00:15:09.959> and 00:15:11.269 --> 00:15:11.279 align:start position:0% name register on my Gaff coin and 00:15:11.279 --> 00:15:14.870 align:start position:0% name register on my Gaff coin and I'm<00:15:12.279> it's<00:15:13.240> going<00:15:13.440> to<00:15:13.759> return<00:15:14.079> success 00:15:14.870 --> 00:15:14.880 align:start position:0% I'm it's going to return success 00:15:14.880 --> 00:15:20.749 align:start position:0% I'm it's going to return success otherwise<00:15:15.279> it<00:15:15.600> returns<00:15:16.720> fail<00:15:17.920> so<00:15:18.920> then<00:15:19.279> it's 00:15:20.749 --> 00:15:20.759 align:start position:0% otherwise it returns fail so then it's 00:15:20.759 --> 00:15:24.629 align:start position:0% otherwise it returns fail so then it's going<00:15:21.759> it's<00:15:21.959> going<00:15:22.120> to<00:15:22.800> step<00:15:23.240> three<00:15:24.240> and<00:15:24.399> then 00:15:24.629 --> 00:15:24.639 align:start position:0% going it's going to step three and then 00:15:24.639 --> 00:15:26.389 align:start position:0% going it's going to step three and then if<00:15:24.839> that<00:15:25.000> succeeds<00:15:25.839> then<00:15:25.920> you<00:15:26.040> know<00:15:26.160> so<00:15:26.279> it's 00:15:26.389 --> 00:15:26.399 align:start position:0% if that succeeds then you know so it's 00:15:26.399 --> 00:15:28.069 align:start position:0% if that succeeds then you know so it's going<00:15:26.519> to<00:15:26.680> call<00:15:27.160> and<00:15:27.320> it's<00:15:27.480> going<00:15:27.600> to<00:15:27.759> create 00:15:28.069 --> 00:15:28.079 align:start position:0% going to call and it's going to create 00:15:28.079 --> 00:15:31.430 align:start position:0% going to call and it's going to create yet<00:15:28.240> another<00:15:28.680> Reed<00:15:29.680> this<00:15:29.800> time<00:15:29.959> in<00:15:30.079> chard<00:15:30.440> 666 00:15:31.430 --> 00:15:31.440 align:start position:0% yet another Reed this time in chard 666 00:15:31.440 --> 00:15:33.470 align:start position:0% yet another Reed this time in chard 666 and<00:15:31.600> this<00:15:31.759> receipt<00:15:32.120> basically<00:15:32.519> says<00:15:33.240> okay 00:15:33.470 --> 00:15:33.480 align:start position:0% and this receipt basically says okay 00:15:33.480 --> 00:15:35.829 align:start position:0% and this receipt basically says okay this<00:15:33.639> computation<00:15:34.240> happened<00:15:34.720> and<00:15:34.839> you<00:15:34.959> have<00:15:35.079> a 00:15:35.829 --> 00:15:35.839 align:start position:0% this computation happened and you have a 00:15:35.839 --> 00:15:38.269 align:start position:0% this computation happened and you have a response<00:15:36.839> step<00:15:37.160> three<00:15:37.519> is<00:15:37.720> basically<00:15:38.160> the 00:15:38.269 --> 00:15:38.279 align:start position:0% response step three is basically the 00:15:38.279 --> 00:15:40.670 align:start position:0% response step three is basically the same<00:15:38.639> almost<00:15:38.880> the<00:15:39.000> same<00:15:39.240> thing<00:15:39.399> as<00:15:39.560> step<00:15:39.800> two 00:15:40.670 --> 00:15:40.680 align:start position:0% same almost the same thing as step two 00:15:40.680 --> 00:15:43.629 align:start position:0% same almost the same thing as step two except<00:15:41.639> in<00:15:41.800> the<00:15:42.079> in<00:15:42.240> step<00:15:42.519> two<00:15:43.079> you<00:15:43.199> were 00:15:43.629 --> 00:15:43.639 align:start position:0% except in the in step two you were 00:15:43.639 --> 00:15:46.350 align:start position:0% except in the in step two you were verifying<00:15:44.639> that<00:15:45.120> a<00:15:45.279> log<00:15:45.639> proof<00:15:46.040> of<00:15:46.199> the 00:15:46.350 --> 00:15:46.360 align:start position:0% verifying that a log proof of the 00:15:46.360 --> 00:15:48.670 align:start position:0% verifying that a log proof of the original<00:15:46.800> call<00:15:47.680> and<00:15:47.839> you're<00:15:48.079> verifying<00:15:48.480> that 00:15:48.670 --> 00:15:48.680 align:start position:0% original call and you're verifying that 00:15:48.680 --> 00:15:50.110 align:start position:0% original call and you're verifying that hasn't<00:15:48.920> yet<00:15:49.079> been<00:15:49.199> spent<00:15:49.639> and<00:15:49.720> you're<00:15:49.920> also 00:15:50.110 --> 00:15:50.120 align:start position:0% hasn't yet been spent and you're also 00:15:50.120 --> 00:15:52.629 align:start position:0% hasn't yet been spent and you're also creating<00:15:50.399> a<00:15:50.600> receipt<00:15:51.560> here<00:15:51.800> you're<00:15:52.079> verifying 00:15:52.629 --> 00:15:52.639 align:start position:0% creating a receipt here you're verifying 00:15:52.639 --> 00:15:54.269 align:start position:0% creating a receipt here you're verifying the<00:15:52.800> call<00:15:53.000> back<00:15:53.199> you're<00:15:53.360> verifying<00:15:53.800> a<00:15:53.920> miracle 00:15:54.269 --> 00:15:54.279 align:start position:0% the call back you're verifying a miracle 00:15:54.279 --> 00:15:56.189 align:start position:0% the call back you're verifying a miracle proof<00:15:54.519> of<00:15:54.639> the<00:15:54.759> call<00:15:55.000> back<00:15:55.639> so<00:15:55.920> you're<00:15:56.040> in<00:15:56.120> the 00:15:56.189 --> 00:15:56.199 align:start position:0% proof of the call back so you're in the 00:15:56.199 --> 00:15:58.829 align:start position:0% proof of the call back so you're in the neighbor<00:15:56.680> Shard<00:15:56.920> you're<00:15:57.040> back<00:15:57.160> in<00:15:57.279> chard<00:15:57.600> 43 00:15:58.829 --> 00:15:58.839 align:start position:0% neighbor Shard you're back in chard 43 00:15:58.839 --> 00:16:01.949 align:start position:0% neighbor Shard you're back in chard 43 now<00:15:58.959> you're<00:15:59.160> just<00:15:59.399> verifying<00:16:00.120> a<00:16:00.360> proof<00:16:01.120> that 00:16:01.949 --> 00:16:01.959 align:start position:0% now you're just verifying a proof that 00:16:01.959 --> 00:16:04.870 align:start position:0% now you're just verifying a proof that Gaff<00:16:02.680> that<00:16:02.880> a<00:16:03.120> log<00:16:03.519> has<00:16:03.680> been<00:16:03.920> created<00:16:04.720> has 00:16:04.870 --> 00:16:04.880 align:start position:0% Gaff that a log has been created has 00:16:04.880 --> 00:16:08.030 align:start position:0% Gaff that a log has been created has been<00:16:05.160> emitted<00:16:05.800> by<00:16:06.040> the<00:16:06.240> Gaff<00:16:06.440> coin<00:16:07.040> contract 00:16:08.030 --> 00:16:08.040 align:start position:0% been emitted by the Gaff coin contract 00:16:08.040 --> 00:16:11.230 align:start position:0% been emitted by the Gaff coin contract and<00:16:08.720> has<00:16:08.880> been<00:16:09.360> is<00:16:09.560> directed<00:16:10.319> at<00:16:10.720> the<00:16:10.880> name 00:16:11.230 --> 00:16:11.240 align:start position:0% and has been is directed at the name 00:16:11.240 --> 00:16:14.790 align:start position:0% and has been is directed at the name register<00:16:12.240> if<00:16:12.440> that's<00:16:12.720> true<00:16:13.680> and<00:16:14.360> if<00:16:14.600> this 00:16:14.790 --> 00:16:14.800 align:start position:0% register if that's true and if this 00:16:14.800 --> 00:16:17.629 align:start position:0% register if that's true and if this particular<00:16:15.240> log<00:16:15.560> has<00:16:15.800> not<00:16:16.040> yet<00:16:16.240> been<00:16:16.639> spent 00:16:17.629 --> 00:16:17.639 align:start position:0% particular log has not yet been spent 00:16:17.639 --> 00:16:19.350 align:start position:0% particular log has not yet been spent then<00:16:18.079> I'm<00:16:18.240> going<00:16:18.319> to<00:16:18.440> say<00:16:18.680> see<00:16:19.000> it's<00:16:19.199> been 00:16:19.350 --> 00:16:19.360 align:start position:0% then I'm going to say see it's been 00:16:19.360 --> 00:16:22.389 align:start position:0% then I'm going to say see it's been spent<00:16:20.000> and<00:16:20.160> I'm<00:16:20.279> going<00:16:20.360> to<00:16:20.480> call<00:16:20.720> the<00:16:21.000> method 00:16:22.389 --> 00:16:22.399 align:start position:0% spent and I'm going to call the method 00:16:22.399 --> 00:16:25.189 align:start position:0% spent and I'm going to call the method so<00:16:23.399> the<00:16:23.560> method<00:16:23.839> in<00:16:23.959> this<00:16:24.079> case<00:16:24.319> is<00:16:24.720> withdraw<00:16:25.079> a 00:16:25.189 --> 00:16:25.199 align:start position:0% so the method in this case is withdraw a 00:16:25.199 --> 00:16:27.030 align:start position:0% so the method in this case is withdraw a call<00:16:25.440> back<00:16:25.920> and<00:16:26.040> the<00:16:26.160> withdraw<00:16:26.560> a<00:16:26.639> call<00:16:26.839> back 00:16:27.030 --> 00:16:27.040 align:start position:0% call back and the withdraw a call back 00:16:27.040 --> 00:16:30.069 align:start position:0% call back and the withdraw a call back basically<00:16:27.480> says<00:16:28.120> if<00:16:28.279> there<00:16:28.600> response<00:16:29.040> is<00:16:29.279> true 00:16:30.069 --> 00:16:30.079 align:start position:0% basically says if there response is true 00:16:30.079 --> 00:16:32.030 align:start position:0% basically says if there response is true then<00:16:30.519> set<00:16:30.839> the<00:16:30.959> owner<00:16:31.240> of<00:16:31.360> this<00:16:31.560> particular 00:16:32.030 --> 00:16:32.040 align:start position:0% then set the owner of this particular 00:16:32.040 --> 00:16:34.590 align:start position:0% then set the owner of this particular domain<00:16:33.040> now<00:16:33.639> over<00:16:33.839> here<00:16:34.040> I<00:16:34.199> probably<00:16:34.440> should 00:16:34.590 --> 00:16:34.600 align:start position:0% domain now over here I probably should 00:16:34.600 --> 00:16:36.749 align:start position:0% domain now over here I probably should have<00:16:34.800> also<00:16:35.040> added<00:16:35.720> that<00:16:35.959> if<00:16:36.120> the<00:16:36.240> O<00:16:36.440> if<00:16:36.600> the 00:16:36.749 --> 00:16:36.759 align:start position:0% have also added that if the O if the 00:16:36.759 --> 00:16:38.230 align:start position:0% have also added that if the O if the domain<00:16:37.040> doesn't<00:16:37.319> have<00:16:37.440> an<00:16:37.800> doesn't<00:16:38.040> have<00:16:38.120> an 00:16:38.230 --> 00:16:38.240 align:start position:0% domain doesn't have an doesn't have an 00:16:38.240 --> 00:16:41.189 align:start position:0% domain doesn't have an doesn't have an owner<00:16:38.560> yet<00:16:38.720> or<00:16:38.839> something<00:16:39.160> similar<00:16:40.199> so 00:16:41.189 --> 00:16:41.199 align:start position:0% owner yet or something similar so 00:16:41.199 --> 00:16:43.590 align:start position:0% owner yet or something similar so basically<00:16:41.600> you<00:16:41.759> know<00:16:42.079> if<00:16:42.600> the<00:16:42.759> entire<00:16:43.120> payment 00:16:43.590 --> 00:16:43.600 align:start position:0% basically you know if the entire payment 00:16:43.600 --> 00:16:46.269 align:start position:0% basically you know if the entire payment process<00:16:44.040> including<00:16:44.839> initial 00:16:46.269 --> 00:16:46.279 align:start position:0% process including initial 00:16:46.279 --> 00:16:48.590 align:start position:0% process including initial transaction<00:16:47.279> processing<00:16:47.720> on<00:16:47.839> the<00:16:48.000> Gaff<00:16:48.240> coin 00:16:48.590 --> 00:16:48.600 align:start position:0% transaction processing on the Gaff coin 00:16:48.600 --> 00:16:50.389 align:start position:0% transaction processing on the Gaff coin side<00:16:49.160> and<00:16:49.279> the<00:16:49.440> call<00:16:49.720> back<00:16:49.959> if<00:16:50.120> everything 00:16:50.389 --> 00:16:50.399 align:start position:0% side and the call back if everything 00:16:50.399 --> 00:16:52.030 align:start position:0% side and the call back if everything works<00:16:50.639> out<00:16:50.880> fine<00:16:51.560> then<00:16:51.720> I'm<00:16:51.839> going<00:16:51.920> to 00:16:52.030 --> 00:16:52.040 align:start position:0% works out fine then I'm going to 00:16:52.040 --> 00:16:54.949 align:start position:0% works out fine then I'm going to register<00:16:52.560> the<00:16:52.680> domain<00:16:53.000> name<00:16:53.279> in<00:16:53.440> chard<00:16:53.759> 43<00:16:54.759> and 00:16:54.949 --> 00:16:54.959 align:start position:0% register the domain name in chard 43 and 00:16:54.959 --> 00:16:56.710 align:start position:0% register the domain name in chard 43 and there<00:16:55.079> you<00:16:55.240> go<00:16:55.399> you<00:16:55.560> have<00:16:55.800> an<00:16:55.959> entire<00:16:56.360> kind<00:16:56.480> of 00:16:56.710 --> 00:16:56.720 align:start position:0% there you go you have an entire kind of 00:16:56.720 --> 00:16:59.230 align:start position:0% there you go you have an entire kind of pathway<00:16:57.199> of<00:16:57.839> asynchronous<00:16:58.560> function 00:16:59.230 --> 00:16:59.240 align:start position:0% pathway of asynchronous function 00:16:59.240 --> 00:17:03.030 align:start position:0% pathway of asynchronous function execution<00:17:00.240> so<00:17:01.160> in<00:17:01.600> practice<00:17:02.600> there<00:17:02.680> are<00:17:02.839> three 00:17:03.030 --> 00:17:03.040 align:start position:0% execution so in practice there are three 00:17:03.040 --> 00:17:04.710 align:start position:0% execution so in practice there are three main<00:17:03.240> use<00:17:03.560> cases<00:17:03.759> for<00:17:04.000> cross<00:17:04.319> contract 00:17:04.710 --> 00:17:04.720 align:start position:0% main use cases for cross contract 00:17:04.720 --> 00:17:07.549 align:start position:0% main use cases for cross contract calling<00:17:05.600> number<00:17:05.839> one<00:17:06.000> is<00:17:06.120> to<00:17:06.319> get<00:17:06.600> information 00:17:07.549 --> 00:17:07.559 align:start position:0% calling number one is to get information 00:17:07.559 --> 00:17:10.350 align:start position:0% calling number one is to get information so<00:17:07.839> getting<00:17:08.160> information<00:17:08.720> basically<00:17:09.199> means<00:17:10.199> I 00:17:10.350 --> 00:17:10.360 align:start position:0% so getting information basically means I 00:17:10.360 --> 00:17:13.669 align:start position:0% so getting information basically means I wants<00:17:10.640> to<00:17:10.880> call<00:17:11.400> the<00:17:12.240> Bloomberg<00:17:12.919> contract<00:17:13.520> and 00:17:13.669 --> 00:17:13.679 align:start position:0% wants to call the Bloomberg contract and 00:17:13.679 --> 00:17:15.549 align:start position:0% wants to call the Bloomberg contract and I<00:17:13.799> wants<00:17:14.039> to<00:17:14.240> find<00:17:14.600> out<00:17:14.839> what<00:17:15.000> the<00:17:15.160> exchange 00:17:15.549 --> 00:17:15.559 align:start position:0% I wants to find out what the exchange 00:17:15.559 --> 00:17:17.309 align:start position:0% I wants to find out what the exchange rate<00:17:15.760> is<00:17:15.880> of<00:17:16.039> USD<00:17:16.400> to 00:17:17.309 --> 00:17:17.319 align:start position:0% rate is of USD to 00:17:17.319 --> 00:17:19.829 align:start position:0% rate is of USD to Euro<00:17:18.319> the<00:17:18.439> second<00:17:18.720> one<00:17:18.880> is<00:17:19.039> send<00:17:19.280> an<00:17:19.480> action 00:17:19.829 --> 00:17:19.839 align:start position:0% Euro the second one is send an action 00:17:19.839 --> 00:17:22.470 align:start position:0% Euro the second one is send an action without<00:17:20.160> response<00:17:21.079> so<00:17:21.360> one<00:17:21.559> simple<00:17:21.880> use<00:17:22.199> case 00:17:22.470 --> 00:17:22.480 align:start position:0% without response so one simple use case 00:17:22.480 --> 00:17:24.909 align:start position:0% without response so one simple use case is<00:17:23.120> let's<00:17:23.360> say<00:17:23.679> I<00:17:23.760> am<00:17:23.959> making<00:17:24.199> a<00:17:24.360> crowd<00:17:24.839> you 00:17:24.909 --> 00:17:24.919 align:start position:0% is let's say I am making a crowd you 00:17:24.919 --> 00:17:26.270 align:start position:0% is let's say I am making a crowd you know<00:17:25.199> I'm<00:17:25.319> building<00:17:25.559> a<00:17:25.679> crowdfunding 00:17:26.270 --> 00:17:26.280 align:start position:0% know I'm building a crowdfunding 00:17:26.280 --> 00:17:28.549 align:start position:0% know I'm building a crowdfunding application<00:17:26.799> I'm<00:17:26.919> building<00:17:27.240> way<00:17:27.480> fund<00:17:28.240> and 00:17:28.549 --> 00:17:28.559 align:start position:0% application I'm building way fund and 00:17:28.559 --> 00:17:31.029 align:start position:0% application I'm building way fund and and<00:17:29.400> the<00:17:29.559> way<00:17:29.720> funds<00:17:30.039> campaign<00:17:30.440> Su<00:17:30.760> a<00:17:30.840> way 00:17:31.029 --> 00:17:31.039 align:start position:0% and the way funds campaign Su a way 00:17:31.039 --> 00:17:33.669 align:start position:0% and the way funds campaign Su a way funds<00:17:31.320> campaign<00:17:32.120> let's<00:17:32.280> say<00:17:32.559> fails<00:17:33.280> and<00:17:33.400> so<00:17:33.600> I 00:17:33.669 --> 00:17:33.679 align:start position:0% funds campaign let's say fails and so I 00:17:33.679 --> 00:17:35.029 align:start position:0% funds campaign let's say fails and so I have<00:17:33.799> to<00:17:33.919> refund<00:17:34.280> all<00:17:34.400> the<00:17:34.480> money<00:17:34.720> so<00:17:34.840> I'm<00:17:34.960> just 00:17:35.029 --> 00:17:35.039 align:start position:0% have to refund all the money so I'm just 00:17:35.039 --> 00:17:37.029 align:start position:0% have to refund all the money so I'm just going<00:17:35.160> to<00:17:35.520> do<00:17:35.679> a<00:17:35.799> big<00:17:36.000> huge<00:17:36.240> multi<00:17:36.640> Cent<00:17:36.919> give 00:17:37.029 --> 00:17:37.039 align:start position:0% going to do a big huge multi Cent give 00:17:37.039 --> 00:17:39.070 align:start position:0% going to do a big huge multi Cent give everyone<00:17:37.320> their<00:17:37.440> money<00:17:37.760> back<00:17:38.600> that's<00:17:38.880> just 00:17:39.070 --> 00:17:39.080 align:start position:0% everyone their money back that's just 00:17:39.080 --> 00:17:40.870 align:start position:0% everyone their money back that's just asynchronous<00:17:39.640> sense<00:17:40.000> does<00:17:40.160> not<00:17:40.400> even<00:17:40.600> require 00:17:40.870 --> 00:17:40.880 align:start position:0% asynchronous sense does not even require 00:17:40.880 --> 00:17:43.990 align:start position:0% asynchronous sense does not even require a<00:17:41.039> call<00:17:41.360> back<00:17:42.360> the<00:17:42.520> third<00:17:42.760> one<00:17:43.000> is<00:17:43.440> send<00:17:43.799> an 00:17:43.990 --> 00:17:44.000 align:start position:0% a call back the third one is send an 00:17:44.000 --> 00:17:46.590 align:start position:0% a call back the third one is send an action<00:17:44.360> with<00:17:44.520> a<00:17:44.720> response<00:17:45.720> and<00:17:46.000> Gaff<00:17:46.280> coin<00:17:46.440> is 00:17:46.590 --> 00:17:46.600 align:start position:0% action with a response and Gaff coin is 00:17:46.600 --> 00:17:48.750 align:start position:0% action with a response and Gaff coin is one<00:17:46.799> example<00:17:47.200> you<00:17:47.360> have<00:17:47.440> to<00:17:47.840> send<00:17:48.120> an<00:17:48.360> action 00:17:48.750 --> 00:17:48.760 align:start position:0% one example you have to send an action 00:17:48.760 --> 00:17:50.950 align:start position:0% one example you have to send an action tell<00:17:49.039> Gaff<00:17:49.280> coin<00:17:49.480> to<00:17:49.600> withdraw<00:17:50.400> Gaff<00:17:50.679> coin 00:17:50.950 --> 00:17:50.960 align:start position:0% tell Gaff coin to withdraw Gaff coin 00:17:50.960 --> 00:17:52.710 align:start position:0% tell Gaff coin to withdraw Gaff coin does<00:17:51.200> something<00:17:51.919> and<00:17:52.039> it<00:17:52.160> might<00:17:52.480> return 00:17:52.710 --> 00:17:52.720 align:start position:0% does something and it might return 00:17:52.720 --> 00:17:55.110 align:start position:0% does something and it might return success<00:17:53.039> or<00:17:53.200> might<00:17:53.480> return<00:17:53.760> failure<00:17:54.760> so<00:17:54.960> the 00:17:55.110 --> 00:17:55.120 align:start position:0% success or might return failure so the 00:17:55.120 --> 00:17:56.750 align:start position:0% success or might return failure so the second<00:17:55.400> is<00:17:55.600> actually<00:17:55.880> like<00:17:56.039> not<00:17:56.320> problematic 00:17:56.750 --> 00:17:56.760 align:start position:0% second is actually like not problematic 00:17:56.760 --> 00:17:58.950 align:start position:0% second is actually like not problematic at<00:17:56.880> all<00:17:57.080> the<00:17:57.159> first<00:17:57.360> and<00:17:57.600> third<00:17:57.960> Maybe 00:17:58.950 --> 00:17:58.960 align:start position:0% at all the first and third Maybe 00:17:58.960 --> 00:18:01.230 align:start position:0% at all the first and third Maybe so<00:17:59.720> once<00:17:59.919> you<00:18:00.120> get<00:18:00.280> into<00:18:00.559> asynchronous 00:18:01.230 --> 00:18:01.240 align:start position:0% so once you get into asynchronous 00:18:01.240 --> 00:18:02.990 align:start position:0% so once you get into asynchronous programming<00:18:01.960> as<00:18:02.280> everyone<00:18:02.559> who<00:18:02.720> has<00:18:02.840> done 00:18:02.990 --> 00:18:03.000 align:start position:0% programming as everyone who has done 00:18:03.000 --> 00:18:04.750 align:start position:0% programming as everyone who has done asynchronous<00:18:03.520> programming<00:18:03.919> will<00:18:04.080> know<00:18:04.600> you 00:18:04.750 --> 00:18:04.760 align:start position:0% asynchronous programming will know you 00:18:04.760 --> 00:18:06.750 align:start position:0% asynchronous programming will know you run<00:18:04.960> into<00:18:05.240> race<00:18:05.640> conditions<00:18:06.000> you<00:18:06.120> have<00:18:06.240> to 00:18:06.750 --> 00:18:06.760 align:start position:0% run into race conditions you have to 00:18:06.760 --> 00:18:09.669 align:start position:0% run into race conditions you have to think<00:18:07.000> about<00:18:07.240> Mutual<00:18:07.679> exclusion<00:18:08.400> issues<00:18:09.400> and 00:18:09.669 --> 00:18:09.679 align:start position:0% think about Mutual exclusion issues and 00:18:09.679 --> 00:18:12.029 align:start position:0% think about Mutual exclusion issues and even<00:18:10.000> without<00:18:10.360> that<00:18:10.799> you<00:18:10.919> know<00:18:11.440> JavaScript 00:18:12.029 --> 00:18:12.039 align:start position:0% even without that you know JavaScript 00:18:12.039 --> 00:18:13.990 align:start position:0% even without that you know JavaScript callback<00:18:12.480> Towers<00:18:13.080> look<00:18:13.320> ugly<00:18:13.640> and<00:18:13.760> they<00:18:13.840> are 00:18:13.990 --> 00:18:14.000 align:start position:0% callback Towers look ugly and they are 00:18:14.000 --> 00:18:16.950 align:start position:0% callback Towers look ugly and they are annoying<00:18:15.000> and<00:18:15.240> so<00:18:16.000> you<00:18:16.120> know<00:18:16.520> you<00:18:16.720> might<00:18:16.880> want 00:18:16.950 --> 00:18:16.960 align:start position:0% annoying and so you know you might want 00:18:16.960 --> 00:18:19.270 align:start position:0% annoying and so you know you might want to<00:18:17.120> think<00:18:17.320> about<00:18:17.640> promises<00:18:18.280> you<00:18:18.440> know<00:18:18.840> a 00:18:19.270 --> 00:18:19.280 align:start position:0% to think about promises you know a 00:18:19.280 --> 00:18:22.549 align:start position:0% to think about promises you know a things<00:18:19.559> like<00:18:19.760> async<00:18:20.280> map<00:18:21.120> so<00:18:21.760> in<00:18:21.960> general<00:18:22.400> you 00:18:22.549 --> 00:18:22.559 align:start position:0% things like async map so in general you 00:18:22.559 --> 00:18:25.350 align:start position:0% things like async map so in general you want<00:18:22.840> kind<00:18:22.960> of<00:18:23.520> programming<00:18:24.520> paradigms<00:18:25.200> that 00:18:25.350 --> 00:18:25.360 align:start position:0% want kind of programming paradigms that 00:18:25.360 --> 00:18:29.750 align:start position:0% want kind of programming paradigms that make<00:18:25.640> this<00:18:25.760> kind<00:18:25.919> of<00:18:26.080> stuff<00:18:26.480> easier<00:18:27.480> now 00:18:29.750 --> 00:18:29.760 align:start position:0% make this kind of stuff easier now 00:18:29.760 --> 00:18:31.669 align:start position:0% make this kind of stuff easier now skip<00:18:30.039> the<00:18:30.240> E<00:18:30.760> economics<00:18:31.280> because<00:18:31.400> I<00:18:31.480> don't 00:18:31.669 --> 00:18:31.679 align:start position:0% skip the E economics because I don't 00:18:31.679 --> 00:18:33.549 align:start position:0% skip the E economics because I don't have<00:18:31.799> too<00:18:32.000> much<00:18:32.240> time<00:18:32.559> but<00:18:32.720> that<00:18:32.919> side's<00:18:33.240> also 00:18:33.549 --> 00:18:33.559 align:start position:0% have too much time but that side's also 00:18:33.559 --> 00:18:35.710 align:start position:0% have too much time but that side's also interesting<00:18:34.360> the<00:18:34.520> basic<00:18:34.840> summary<00:18:35.320> is<00:18:35.520> that 00:18:35.710 --> 00:18:35.720 align:start position:0% interesting the basic summary is that 00:18:35.720 --> 00:18:38.270 align:start position:0% interesting the basic summary is that yes<00:18:35.880> you<00:18:36.000> can<00:18:36.120> do<00:18:36.320> it<00:18:36.559> yes<00:18:36.720> it's<00:18:37.000> fine<00:18:37.720> and<00:18:38.000> in 00:18:38.270 --> 00:18:38.280 align:start position:0% yes you can do it yes it's fine and in 00:18:38.280 --> 00:18:40.190 align:start position:0% yes you can do it yes it's fine and in fact<00:18:38.960> even<00:18:39.280> though<00:18:39.440> you<00:18:39.559> need<00:18:39.799> multiple 00:18:40.190 --> 00:18:40.200 align:start position:0% fact even though you need multiple 00:18:40.200 --> 00:18:41.870 align:start position:0% fact even though you need multiple transactions<00:18:40.840> you<00:18:40.960> can<00:18:41.240> actually<00:18:41.559> make<00:18:41.679> it 00:18:41.870 --> 00:18:41.880 align:start position:0% transactions you can actually make it 00:18:41.880 --> 00:18:44.630 align:start position:0% transactions you can actually make it censorship<00:18:42.400> resistant<00:18:43.080> because<00:18:43.960> basically 00:18:44.630 --> 00:18:44.640 align:start position:0% censorship resistant because basically 00:18:44.640 --> 00:18:47.230 align:start position:0% censorship resistant because basically because<00:18:44.960> the<00:18:45.120> log<00:18:45.480> was<00:18:45.720> created<00:18:46.720> you<00:18:46.960> have 00:18:47.230 --> 00:18:47.240 align:start position:0% because the log was created you have 00:18:47.240 --> 00:18:48.710 align:start position:0% because the log was created you have common<00:18:47.559> knowledge<00:18:47.880> of<00:18:48.080> the<00:18:48.240> facts<00:18:48.520> that 00:18:48.710 --> 00:18:48.720 align:start position:0% common knowledge of the facts that 00:18:48.720 --> 00:18:50.950 align:start position:0% common knowledge of the facts that theoretically<00:18:49.679> a<00:18:49.880> transaction<00:18:50.520> completing 00:18:50.950 --> 00:18:50.960 align:start position:0% theoretically a transaction completing 00:18:50.960 --> 00:18:53.149 align:start position:0% theoretically a transaction completing the<00:18:51.159> process<00:18:51.559> can<00:18:51.799> be<00:18:52.000> made<00:18:52.600> and<00:18:52.679> so<00:18:52.840> he<00:18:52.960> can 00:18:53.149 --> 00:18:53.159 align:start position:0% the process can be made and so he can 00:18:53.159 --> 00:18:54.750 align:start position:0% the process can be made and so he can punish<00:18:53.480> validators<00:18:54.000> for<00:18:54.159> not<00:18:54.360> making<00:18:54.600> it 00:18:54.750 --> 00:18:54.760 align:start position:0% punish validators for not making it 00:18:54.760 --> 00:18:57.590 align:start position:0% punish validators for not making it within<00:18:55.000> some<00:18:55.200> number<00:18:55.400> of<00:18:55.559> blocks<00:18:56.520> so<00:18:57.320> more 00:18:57.590 --> 00:18:57.600 align:start position:0% within some number of blocks so more 00:18:57.600 --> 00:19:00.390 align:start position:0% within some number of blocks so more generality<00:18:58.799> here's<00:18:59.080> one<00:18:59.360> possible<00:18:59.720> model 00:19:00.390 --> 00:19:00.400 align:start position:0% generality here's one possible model 00:19:00.400 --> 00:19:03.470 align:start position:0% generality here's one possible model first<00:19:00.760> K<00:19:00.960> bits<00:19:01.159> of<00:19:01.280> an<00:19:01.480> address<00:19:01.840> is<00:19:01.960> a<00:19:02.039> Shard<00:19:02.480> ID 00:19:03.470 --> 00:19:03.480 align:start position:0% first K bits of an address is a Shard ID 00:19:03.480 --> 00:19:06.549 align:start position:0% first K bits of an address is a Shard ID and<00:19:03.880> K<00:19:04.200> is<00:19:04.360> said<00:19:04.679> by<00:19:04.799> the<00:19:05.240> transaction<00:19:06.240> so 00:19:06.549 --> 00:19:06.559 align:start position:0% and K is said by the transaction so 00:19:06.559 --> 00:19:08.630 align:start position:0% and K is said by the transaction so every<00:19:06.799> transaction<00:19:07.360> sets<00:19:07.600> its<00:19:07.720> own<00:19:08.000> K<00:19:08.520> you 00:19:08.630 --> 00:19:08.640 align:start position:0% every transaction sets its own K you 00:19:08.640 --> 00:19:10.310 align:start position:0% every transaction sets its own K you know<00:19:08.760> you<00:19:08.880> could<00:19:09.000> set<00:19:09.280> k<00:19:09.440> equals<00:19:09.799> zero<00:19:10.080> means 00:19:10.310 --> 00:19:10.320 align:start position:0% know you could set k equals zero means 00:19:10.320 --> 00:19:11.909 align:start position:0% know you could set k equals zero means that<00:19:10.440> your<00:19:10.679> transaction<00:19:11.320> can<00:19:11.559> like<00:19:11.679> do 00:19:11.909 --> 00:19:11.919 align:start position:0% that your transaction can like do 00:19:11.919 --> 00:19:14.510 align:start position:0% that your transaction can like do everything<00:19:12.400> globally<00:19:13.400> uh<00:19:13.520> setting<00:19:13.960> k<00:19:14.159> equals 00:19:14.510 --> 00:19:14.520 align:start position:0% everything globally uh setting k equals 00:19:14.520 --> 00:19:16.230 align:start position:0% everything globally uh setting k equals 10<00:19:14.760> means<00:19:14.960> your<00:19:15.159> transaction<00:19:15.679> only<00:19:15.919> affects 00:19:16.230 --> 00:19:16.240 align:start position:0% 10 means your transaction only affects 00:19:16.240 --> 00:19:17.590 align:start position:0% 10 means your transaction only affects things<00:19:16.440> that<00:19:16.559> have<00:19:16.679> a<00:19:16.799> particular<00:19:17.159> 10<00:19:17.400> bit 00:19:17.590 --> 00:19:17.600 align:start position:0% things that have a particular 10 bit 00:19:17.600 --> 00:19:20.190 align:start position:0% things that have a particular 10 bit prefix<00:19:18.000> and<00:19:18.120> so<00:19:18.520> forth<00:19:19.520> attempting<00:19:19.960> to 00:19:20.190 --> 00:19:20.200 align:start position:0% prefix and so forth attempting to 00:19:20.200 --> 00:19:22.669 align:start position:0% prefix and so forth attempting to synchronously<00:19:20.960> call<00:19:21.400> a<00:19:21.600> contract<00:19:22.280> outside<00:19:22.600> of 00:19:22.669 --> 00:19:22.679 align:start position:0% synchronously call a contract outside of 00:19:22.679 --> 00:19:24.789 align:start position:0% synchronously call a contract outside of a<00:19:22.760> Shard<00:19:23.640> and<00:19:23.799> The<00:19:23.880> Shard<00:19:24.280> is<00:19:24.440> kind<00:19:24.520> of<00:19:24.679> this 00:19:24.789 --> 00:19:24.799 align:start position:0% a Shard and The Shard is kind of this 00:19:24.799 --> 00:19:26.230 align:start position:0% a Shard and The Shard is kind of this sort<00:19:24.919> of<00:19:25.080> much<00:19:25.200> more<00:19:25.440> fuzzy<00:19:25.799> concept<00:19:26.120> where 00:19:26.230 --> 00:19:26.240 align:start position:0% sort of much more fuzzy concept where 00:19:26.240 --> 00:19:28.750 align:start position:0% sort of much more fuzzy concept where it's<00:19:26.400> kind<00:19:26.480> of<00:19:26.640> defined<00:19:27.039> by<00:19:27.240> K<00:19:28.320> basically<00:19:28.640> you 00:19:28.750 --> 00:19:28.760 align:start position:0% it's kind of defined by K basically you 00:19:28.760 --> 00:19:32.029 align:start position:0% it's kind of defined by K basically you know<00:19:29.000> if<00:19:29.120> your<00:19:29.320> transaction<00:19:29.880> sets<00:19:30.240> K<00:19:30.440> to<00:19:30.799> to<00:19:31.039> 13 00:19:32.029 --> 00:19:32.039 align:start position:0% know if your transaction sets K to to 13 00:19:32.039 --> 00:19:34.789 align:start position:0% know if your transaction sets K to to 13 then<00:19:32.320> if<00:19:32.440> you<00:19:32.600> try<00:19:32.760> to<00:19:32.960> do<00:19:33.200> something<00:19:34.080> if<00:19:34.520> one 00:19:34.789 --> 00:19:34.799 align:start position:0% then if you try to do something if one 00:19:34.799 --> 00:19:36.390 align:start position:0% then if you try to do something if one contract<00:19:35.159> tries<00:19:35.360> to<00:19:35.480> call<00:19:35.679> another<00:19:35.919> contract 00:19:36.390 --> 00:19:36.400 align:start position:0% contract tries to call another contract 00:19:36.400 --> 00:19:38.110 align:start position:0% contract tries to call another contract where<00:19:36.559> one<00:19:36.679> of<00:19:36.799> the<00:19:37.159> first<00:19:37.360> 13<00:19:37.720> bits<00:19:37.960> is 00:19:38.110 --> 00:19:38.120 align:start position:0% where one of the first 13 bits is 00:19:38.120 --> 00:19:39.950 align:start position:0% where one of the first 13 bits is different<00:19:38.960> then<00:19:39.120> that<00:19:39.240> triggers<00:19:39.559> an<00:19:39.640> out<00:19:39.799> of 00:19:39.950 --> 00:19:39.960 align:start position:0% different then that triggers an out of 00:19:39.960 --> 00:19:40.710 align:start position:0% different then that triggers an out of gas 00:19:40.710 --> 00:19:40.720 align:start position:0% gas 00:19:40.720 --> 00:19:44.510 align:start position:0% gas exception<00:19:41.720> and<00:19:42.760> so<00:19:43.760> the<00:19:43.960> key<00:19:44.159> Point 00:19:44.510 --> 00:19:44.520 align:start position:0% exception and so the key Point 00:19:44.520 --> 00:19:46.950 align:start position:0% exception and so the key Point economically<00:19:45.200> is<00:19:45.320> that<00:19:45.559> transaction<00:19:46.280> groups 00:19:46.950 --> 00:19:46.960 align:start position:0% economically is that transaction groups 00:19:46.960 --> 00:19:48.870 align:start position:0% economically is that transaction groups on<00:19:47.200> all<00:19:47.480> no<00:19:47.640> matter<00:19:47.919> what<00:19:48.080> the<00:19:48.280> k<00:19:48.480> is<00:19:48.640> going<00:19:48.720> to 00:19:48.870 --> 00:19:48.880 align:start position:0% on all no matter what the k is going to 00:19:48.880 --> 00:19:51.990 align:start position:0% on all no matter what the k is going to have<00:19:49.039> the<00:19:49.159> same<00:19:49.480> gas<00:19:49.760> limit<00:19:50.440> so<00:19:51.080> if<00:19:51.200> you<00:19:51.440> want 00:19:51.990 --> 00:19:52.000 align:start position:0% have the same gas limit so if you want 00:19:52.000 --> 00:19:53.789 align:start position:0% have the same gas limit so if you want you<00:19:52.159> can<00:19:52.360> make<00:19:52.480> a<00:19:52.600> transaction<00:19:53.120> set<00:19:53.320> the<00:19:53.440> K<00:19:53.600> to 00:19:53.789 --> 00:19:53.799 align:start position:0% you can make a transaction set the K to 00:19:53.799 --> 00:19:56.630 align:start position:0% you can make a transaction set the K to zero<00:19:54.640> and<00:19:54.840> someone<00:19:55.200> can<00:19:55.559> can<00:19:56.039> callate<00:19:56.480> all 00:19:56.630 --> 00:19:56.640 align:start position:0% zero and someone can can callate all 00:19:56.640 --> 00:19:58.230 align:start position:0% zero and someone can can callate all these<00:19:56.799> transactions<00:19:57.720> put<00:19:57.880> them<00:19:58.080> together 00:19:58.230 --> 00:19:58.240 align:start position:0% these transactions put them together 00:19:58.240 --> 00:19:59.710 align:start position:0% these transactions put them together together<00:19:58.400> into<00:19:58.520> a<00:19:58.640> transaction<00:19:59.240> group<00:19:59.559> that 00:19:59.710 --> 00:19:59.720 align:start position:0% together into a transaction group that 00:19:59.720 --> 00:20:02.470 align:start position:0% together into a transaction group that has<00:19:59.880> k<00:20:00.039> equals<00:20:00.360> z<00:20:01.039> but<00:20:01.200> here's<00:20:01.400> the<00:20:01.600> thing<00:20:02.360> if 00:20:02.470 --> 00:20:02.480 align:start position:0% has k equals z but here's the thing if 00:20:02.480 --> 00:20:05.270 align:start position:0% has k equals z but here's the thing if you<00:20:02.600> are<00:20:02.799> a<00:20:03.000> top<00:20:03.360> if<00:20:03.520> you<00:20:03.720> are<00:20:04.159> one<00:20:04.320> of<00:20:04.960> someone 00:20:05.270 --> 00:20:05.280 align:start position:0% you are a top if you are one of someone 00:20:05.280 --> 00:20:07.630 align:start position:0% you are a top if you are one of someone creating<00:20:05.559> a<00:20:05.720> top<00:20:05.919> level<00:20:06.200> block<00:20:07.080> then<00:20:07.280> you 00:20:07.630 --> 00:20:07.640 align:start position:0% creating a top level block then you 00:20:07.640 --> 00:20:10.510 align:start position:0% creating a top level block then you could<00:20:08.640> get<00:20:08.880> one<00:20:09.280> one<00:20:09.520> transaction<00:20:10.039> group<00:20:10.240> at<00:20:10.360> k 00:20:10.510 --> 00:20:10.520 align:start position:0% could get one one transaction group at k 00:20:10.520 --> 00:20:13.149 align:start position:0% could get one one transaction group at k equals<00:20:10.799> 0<00:20:11.480> or<00:20:11.720> you<00:20:11.799> can<00:20:12.039> get<00:20:12.200> 32<00:20:12.720> transaction 00:20:13.149 --> 00:20:13.159 align:start position:0% equals 0 or you can get 32 transaction 00:20:13.159 --> 00:20:16.149 align:start position:0% equals 0 or you can get 32 transaction groups<00:20:13.440> at<00:20:13.559> k<00:20:13.720> equals<00:20:14.000> 5<00:20:14.880> or<00:20:15.080> you<00:20:15.159> can<00:20:15.360> get 00:20:16.149 --> 00:20:16.159 align:start position:0% groups at k equals 5 or you can get 00:20:16.159 --> 00:20:19.470 align:start position:0% groups at k equals 5 or you can get 65,536<00:20:17.159> transaction<00:20:17.600> groups<00:20:17.840> at<00:20:18.000> k<00:20:18.120> equal<00:20:18.480> 16 00:20:19.470 --> 00:20:19.480 align:start position:0% 65,536 transaction groups at k equal 16 00:20:19.480 --> 00:20:21.549 align:start position:0% 65,536 transaction groups at k equal 16 so<00:20:19.679> in<00:20:19.880> equilibrium<00:20:20.559> the<00:20:20.679> lower<00:20:20.960> your<00:20:21.159> K<00:20:21.360> is 00:20:21.549 --> 00:20:21.559 align:start position:0% so in equilibrium the lower your K is 00:20:21.559 --> 00:20:23.590 align:start position:0% so in equilibrium the lower your K is the<00:20:21.679> more<00:20:21.880> expensive<00:20:22.280> it's<00:20:22.440> going<00:20:22.559> to<00:20:22.720> be<00:20:23.400> and 00:20:23.590 --> 00:20:23.600 align:start position:0% the more expensive it's going to be and 00:20:23.600 --> 00:20:25.669 align:start position:0% the more expensive it's going to be and that's<00:20:23.919> kind<00:20:24.080> of<00:20:24.480> a<00:20:24.679> way<00:20:24.840> of<00:20:25.000> making<00:20:25.360> this<00:20:25.520> sort 00:20:25.669 --> 00:20:25.679 align:start position:0% that's kind of a way of making this sort 00:20:25.679 --> 00:20:27.070 align:start position:0% that's kind of a way of making this sort of<00:20:25.840> balance<00:20:26.159> and<00:20:26.320> letting<00:20:26.559> people<00:20:26.760> sort<00:20:26.919> of 00:20:27.070 --> 00:20:27.080 align:start position:0% of balance and letting people sort of 00:20:27.080 --> 00:20:29.350 align:start position:0% of balance and letting people sort of choose<00:20:27.520> along<00:20:27.760> the<00:20:27.880> Curve<00:20:28.320> between<00:20:28.880> synchrony 00:20:29.350 --> 00:20:29.360 align:start position:0% choose along the Curve between synchrony 00:20:29.360 --> 00:20:32.990 align:start position:0% choose along the Curve between synchrony and<00:20:29.559> cost<00:20:30.720> so<00:20:31.720> that's<00:20:31.960> basically<00:20:32.360> it<00:20:32.480> you<00:20:32.600> know 00:20:32.990 --> 00:20:33.000 align:start position:0% and cost so that's basically it you know 00:20:33.000 --> 00:20:35.789 align:start position:0% and cost so that's basically it you know welcome<00:20:33.400> to<00:20:34.039> asynchronous<00:20:34.919> theam<00:20:35.280> 2.0 00:20:35.789 --> 00:20:35.799 align:start position:0% welcome to asynchronous theam 2.0 00:20:35.799 --> 00:20:45.590 align:start position:0% welcome to asynchronous theam 2.0 contracts 00:20:45.590 --> 00:20:45.600 align:start position:0% 00:20:45.600 --> 00:20:49.950 align:start position:0% [Music] 00:20:49.950 --> 00:20:49.960 align:start position:0% 00:20:49.960 --> 00:20:52.960 align:start position:0% programming