WEBVTT Kind: captions Language: en 00:00:13.269 --> 00:00:17.529 align:start position:0% hello<00:00:14.269> everyone<00:00:14.659> I'm<00:00:15.760> George<00:00:16.760> featherly<00:00:17.000> and 00:00:17.529 --> 00:00:17.539 align:start position:0% hello everyone I'm George featherly and 00:00:17.539 --> 00:00:19.990 align:start position:0% hello everyone I'm George featherly and today<00:00:18.200> I<00:00:18.230> would<00:00:18.650> like<00:00:18.890> to<00:00:19.100> talk<00:00:19.460> about<00:00:19.520> talk 00:00:19.990 --> 00:00:20.000 align:start position:0% today I would like to talk about talk 00:00:20.000 --> 00:00:23.440 align:start position:0% today I would like to talk about talk about<00:00:20.530> some<00:00:21.530> potential<00:00:22.210> applications<00:00:23.210> of 00:00:23.440 --> 00:00:23.450 align:start position:0% about some potential applications of 00:00:23.450 --> 00:00:25.300 align:start position:0% about some potential applications of offering<00:00:23.870> computation<00:00:24.320> in<00:00:24.680> the<00:00:24.710> light<00:00:24.920> client 00:00:25.300 --> 00:00:25.310 align:start position:0% offering computation in the light client 00:00:25.310 --> 00:00:28.480 align:start position:0% offering computation in the light client ecosystem<00:00:26.530> maybe<00:00:27.530> you<00:00:27.860> have<00:00:27.980> already<00:00:28.280> heard 00:00:28.480 --> 00:00:28.490 align:start position:0% ecosystem maybe you have already heard 00:00:28.490 --> 00:00:31.300 align:start position:0% ecosystem maybe you have already heard about<00:00:28.780> octane<00:00:29.780> computation<00:00:30.230> and<00:00:30.710> interactive 00:00:31.300 --> 00:00:31.310 align:start position:0% about octane computation and interactive 00:00:31.310 --> 00:00:33.459 align:start position:0% about octane computation and interactive validation<00:00:31.940> these<00:00:32.689> are<00:00:32.870> really<00:00:33.170> promising 00:00:33.459 --> 00:00:33.469 align:start position:0% validation these are really promising 00:00:33.469 --> 00:00:35.890 align:start position:0% validation these are really promising and<00:00:33.920> exciting<00:00:33.980> new<00:00:34.460> concepts<00:00:35.090> but<00:00:35.240> the<00:00:35.450> basic 00:00:35.890 --> 00:00:35.900 align:start position:0% and exciting new concepts but the basic 00:00:35.900 --> 00:00:41.250 align:start position:0% and exciting new concepts but the basic idea<00:00:36.200> is<00:00:36.410> really<00:00:37.130> simple<00:00:39.610> if<00:00:40.610> there's<00:00:41.060> a 00:00:41.250 --> 00:00:41.260 align:start position:0% idea is really simple if there's a 00:00:41.260 --> 00:00:43.750 align:start position:0% idea is really simple if there's a complex<00:00:42.260> but<00:00:42.440> deterministic<00:00:43.100> calculation 00:00:43.750 --> 00:00:43.760 align:start position:0% complex but deterministic calculation 00:00:43.760 --> 00:00:45.819 align:start position:0% complex but deterministic calculation that<00:00:43.790> would<00:00:44.060> be<00:00:44.150> too<00:00:44.329> expensive<00:00:44.690> to<00:00:44.960> diversity 00:00:45.819 --> 00:00:45.829 align:start position:0% that would be too expensive to diversity 00:00:45.829 --> 00:00:47.950 align:start position:0% that would be too expensive to diversity process<00:00:46.280> on<00:00:46.520> the<00:00:46.700> blockchain<00:00:46.940> it<00:00:47.329> is<00:00:47.450> still 00:00:47.950 --> 00:00:47.960 align:start position:0% process on the blockchain it is still 00:00:47.960 --> 00:00:50.560 align:start position:0% process on the blockchain it is still possible<00:00:48.170> to<00:00:48.770> have<00:00:49.040> multiple<00:00:49.570> parties 00:00:50.560 --> 00:00:50.570 align:start position:0% possible to have multiple parties 00:00:50.570 --> 00:00:53.290 align:start position:0% possible to have multiple parties evaluate<00:00:51.170> the<00:00:51.380> same<00:00:51.739> function<00:00:52.310> check<00:00:53.030> the 00:00:53.290 --> 00:00:53.300 align:start position:0% evaluate the same function check the 00:00:53.300 --> 00:00:55.150 align:start position:0% evaluate the same function check the results<00:00:53.750> against<00:00:53.989> each<00:00:54.170> other<00:00:54.350> and<00:00:54.590> only 00:00:55.150 --> 00:00:55.160 align:start position:0% results against each other and only 00:00:55.160 --> 00:00:57.190 align:start position:0% results against each other and only start<00:00:55.399> an<00:00:55.579> interactive<00:00:56.239> validation<00:00:56.809> process 00:00:57.190 --> 00:00:57.200 align:start position:0% start an interactive validation process 00:00:57.200 --> 00:00:59.470 align:start position:0% start an interactive validation process that<00:00:57.770> could<00:00:57.980> prove<00:00:58.250> one<00:00:58.910> of<00:00:59.030> the<00:00:59.120> parties 00:00:59.470 --> 00:00:59.480 align:start position:0% that could prove one of the parties 00:00:59.480 --> 00:01:01.840 align:start position:0% that could prove one of the parties wrong<00:00:59.750> if<00:00:59.989> there's<00:01:00.410> a<00:01:00.530> disagreement<00:01:00.829> and<00:01:01.399> this 00:01:01.840 --> 00:01:01.850 align:start position:0% wrong if there's a disagreement and this 00:01:01.850 --> 00:01:03.910 align:start position:0% wrong if there's a disagreement and this validation<00:01:02.210> process<00:01:02.690> can<00:01:03.290> be<00:01:03.500> realized 00:01:03.910 --> 00:01:03.920 align:start position:0% validation process can be realized 00:01:03.920 --> 00:01:05.740 align:start position:0% validation process can be realized inside<00:01:04.309> a<00:01:04.339> contract<00:01:04.879> so<00:01:05.030> eventually<00:01:05.299> the 00:01:05.740 --> 00:01:05.750 align:start position:0% inside a contract so eventually the 00:01:05.750 --> 00:01:07.750 align:start position:0% inside a contract so eventually the results<00:01:06.260> of<00:01:06.350> such<00:01:06.530> a<00:01:06.560> calculation<00:01:07.100> can<00:01:07.729> be 00:01:07.750 --> 00:01:07.760 align:start position:0% results of such a calculation can be 00:01:07.760 --> 00:01:10.240 align:start position:0% results of such a calculation can be canonized<00:01:08.240> on<00:01:08.570> the<00:01:08.720> blockchain<00:01:09.250> this 00:01:10.240 --> 00:01:10.250 align:start position:0% canonized on the blockchain this 00:01:10.250 --> 00:01:13.330 align:start position:0% canonized on the blockchain this technology<00:01:10.760> can<00:01:11.030> be<00:01:11.210> used<00:01:11.900> to<00:01:12.170> process<00:01:13.159> large 00:01:13.330 --> 00:01:13.340 align:start position:0% technology can be used to process large 00:01:13.340 --> 00:01:16.960 align:start position:0% technology can be used to process large amounts<00:01:13.820> of<00:01:13.880> external<00:01:14.450> data<00:01:14.630> but<00:01:15.790> which<00:01:16.790> could 00:01:16.960 --> 00:01:16.970 align:start position:0% amounts of external data but which could 00:01:16.970 --> 00:01:20.320 align:start position:0% amounts of external data but which could be<00:01:17.090> located<00:01:17.360> anywhere<00:01:17.750> like<00:01:18.229> a<00:01:18.500> swarm<00:01:18.830> but<00:01:19.610> in 00:01:20.320 --> 00:01:20.330 align:start position:0% be located anywhere like a swarm but in 00:01:20.330 --> 00:01:21.820 align:start position:0% be located anywhere like a swarm but in this<00:01:20.659> case<00:01:20.869> I<00:01:21.020> would<00:01:21.200> like<00:01:21.229> to<00:01:21.470> present<00:01:21.650> some 00:01:21.820 --> 00:01:21.830 align:start position:0% this case I would like to present some 00:01:21.830 --> 00:01:24.280 align:start position:0% this case I would like to present some use<00:01:22.070> cases<00:01:22.100> where<00:01:22.640> the<00:01:22.820> input<00:01:23.180> data<00:01:23.299> is<00:01:23.720> a 00:01:24.280 --> 00:01:24.290 align:start position:0% use cases where the input data is a 00:01:24.290 --> 00:01:26.260 align:start position:0% use cases where the input data is a blockchain<00:01:24.590> itself<00:01:25.159> either<00:01:25.369> the<00:01:25.700> same<00:01:25.970> chain 00:01:26.260 --> 00:01:26.270 align:start position:0% blockchain itself either the same chain 00:01:26.270 --> 00:01:28.300 align:start position:0% blockchain itself either the same chain where<00:01:26.479> the<00:01:26.630> validation<00:01:27.409> happens<00:01:27.770> or<00:01:27.950> can<00:01:28.190> be 00:01:28.300 --> 00:01:28.310 align:start position:0% where the validation happens or can be 00:01:28.310 --> 00:01:31.810 align:start position:0% where the validation happens or can be another<00:01:28.520> one<00:01:28.790> to<00:01:30.189> these<00:01:31.189> use<00:01:31.400> cases<00:01:31.670> are 00:01:31.810 --> 00:01:31.820 align:start position:0% another one to these use cases are 00:01:31.820 --> 00:01:35.020 align:start position:0% another one to these use cases are mostly<00:01:32.210> related<00:01:32.780> to<00:01:32.810> even<00:01:33.290> filtering<00:01:33.909> in<00:01:34.909> a 00:01:35.020 --> 00:01:35.030 align:start position:0% mostly related to even filtering in a 00:01:35.030 --> 00:01:37.240 align:start position:0% mostly related to even filtering in a current<00:01:35.750> single<00:01:36.049> blockchain<00:01:36.530> scenario<00:01:37.010> in 00:01:37.240 --> 00:01:37.250 align:start position:0% current single blockchain scenario in 00:01:37.250 --> 00:01:39.730 align:start position:0% current single blockchain scenario in even<00:01:37.670> filtering<00:01:38.150> is<00:01:38.299> quite<00:01:38.630> simple<00:01:39.049> we<00:01:39.590> have 00:01:39.730 --> 00:01:39.740 align:start position:0% even filtering is quite simple we have 00:01:39.740 --> 00:01:41.380 align:start position:0% even filtering is quite simple we have the<00:01:39.950> contract<00:01:40.460> log<00:01:40.610> events<00:01:41.000> and<00:01:41.150> bloom 00:01:41.380 --> 00:01:41.390 align:start position:0% the contract log events and bloom 00:01:41.390 --> 00:01:47.050 align:start position:0% the contract log events and bloom filters<00:01:41.840> but<00:01:43.479> in<00:01:44.479> order<00:01:44.840> to<00:01:45.070> do<00:01:46.070> a<00:01:46.280> full 00:01:47.050 --> 00:01:47.060 align:start position:0% filters but in order to do a full 00:01:47.060 --> 00:01:48.280 align:start position:0% filters but in order to do a full history<00:01:47.299> search<00:01:47.720> with<00:01:47.960> ghost<00:01:48.170> world 00:01:48.280 --> 00:01:48.290 align:start position:0% history search with ghost world 00:01:48.290 --> 00:01:50.320 align:start position:0% history search with ghost world performance<00:01:48.890> we<00:01:49.070> already<00:01:49.430> needed<00:01:50.030> some 00:01:50.320 --> 00:01:50.330 align:start position:0% performance we already needed some 00:01:50.330 --> 00:01:52.510 align:start position:0% performance we already needed some clever<00:01:50.810> performance<00:01:51.470> optimizations<00:01:52.189> which<00:01:52.369> I 00:01:52.510 --> 00:01:52.520 align:start position:0% clever performance optimizations which I 00:01:52.520 --> 00:01:55.630 align:start position:0% clever performance optimizations which I will<00:01:52.759> shortly<00:01:53.150> talk<00:01:53.600> about<00:01:54.220> later<00:01:55.220> I<00:01:55.460> would 00:01:55.630 --> 00:01:55.640 align:start position:0% will shortly talk about later I would 00:01:55.640 --> 00:01:59.140 align:start position:0% will shortly talk about later I would also<00:01:55.790> like<00:01:56.180> to<00:01:56.420> talk<00:01:56.930> about<00:01:57.310> the<00:01:58.310> future 00:01:59.140 --> 00:01:59.150 align:start position:0% also like to talk about the future 00:01:59.150 --> 00:02:03.039 align:start position:0% also like to talk about the future challenges<00:01:59.869> of<00:02:00.400> even<00:02:01.400> filtering<00:02:02.060> with<00:02:02.780> light 00:02:03.039 --> 00:02:03.049 align:start position:0% challenges of even filtering with light 00:02:03.049 --> 00:02:08.529 align:start position:0% challenges of even filtering with light clients<00:02:04.780> we<00:02:05.780> are<00:02:06.079> going<00:02:06.710> to<00:02:06.860> have<00:02:07.159> a<00:02:07.539> sharding 00:02:08.529 --> 00:02:08.539 align:start position:0% clients we are going to have a sharding 00:02:08.539 --> 00:02:11.559 align:start position:0% clients we are going to have a sharding and<00:02:09.190> stationer<00:02:10.190> technologies<00:02:10.849> like<00:02:11.090> plasma 00:02:11.559 --> 00:02:11.569 align:start position:0% and stationer technologies like plasma 00:02:11.569 --> 00:02:13.110 align:start position:0% and stationer technologies like plasma or<00:02:11.750> polka<00:02:12.140> dot<00:02:12.319> and 00:02:13.110 --> 00:02:13.120 align:start position:0% or polka dot and 00:02:13.120 --> 00:02:15.089 align:start position:0% or polka dot and eventually<00:02:13.690> we'll<00:02:13.959> end<00:02:14.200> up<00:02:14.319> with<00:02:14.379> a<00:02:14.560> massive 00:02:15.089 --> 00:02:15.099 align:start position:0% eventually we'll end up with a massive 00:02:15.099 --> 00:02:18.690 align:start position:0% eventually we'll end up with a massive hierarchy<00:02:15.879> of<00:02:16.030> chains<00:02:16.360> and<00:02:17.580> massive<00:02:18.580> amounts 00:02:18.690 --> 00:02:18.700 align:start position:0% hierarchy of chains and massive amounts 00:02:18.700 --> 00:02:21.479 align:start position:0% hierarchy of chains and massive amounts of<00:02:19.030> chain<00:02:19.660> data<00:02:19.870> and<00:02:20.319> we<00:02:20.560> will<00:02:20.980> definitely 00:02:21.479 --> 00:02:21.489 align:start position:0% of chain data and we will definitely 00:02:21.489 --> 00:02:23.160 align:start position:0% of chain data and we will definitely need<00:02:21.640> some<00:02:21.959> sophisticated<00:02:22.959> filtering 00:02:23.160 --> 00:02:23.170 align:start position:0% need some sophisticated filtering 00:02:23.170 --> 00:02:26.250 align:start position:0% need some sophisticated filtering methods<00:02:23.530> to<00:02:24.120> make<00:02:25.120> sense<00:02:25.360> of<00:02:25.510> all<00:02:25.629> this<00:02:25.780> data 00:02:26.250 --> 00:02:26.260 align:start position:0% methods to make sense of all this data 00:02:26.260 --> 00:02:29.940 align:start position:0% methods to make sense of all this data I<00:02:27.450> suppose<00:02:28.450> let<00:02:28.690> me<00:02:28.870> just<00:02:29.260> quickly<00:02:29.410> talk<00:02:29.920> about 00:02:29.940 --> 00:02:29.950 align:start position:0% I suppose let me just quickly talk about 00:02:29.950 --> 00:02:33.780 align:start position:0% I suppose let me just quickly talk about the<00:02:30.480> current<00:02:31.480> filtering<00:02:32.019> system<00:02:32.620> in<00:02:32.920> the<00:02:33.489> go 00:02:33.780 --> 00:02:33.790 align:start position:0% the current filtering system in the go 00:02:33.790 --> 00:02:37.559 align:start position:0% the current filtering system in the go ATM<00:02:34.269> client<00:02:35.580> you<00:02:36.580> probably<00:02:37.030> know<00:02:37.269> bloom 00:02:37.559 --> 00:02:37.569 align:start position:0% ATM client you probably know bloom 00:02:37.569 --> 00:02:39.119 align:start position:0% ATM client you probably know bloom filters<00:02:37.959> they<00:02:38.080> are<00:02:38.200> really<00:02:38.470> simple<00:02:38.830> data 00:02:39.119 --> 00:02:39.129 align:start position:0% filters they are really simple data 00:02:39.129 --> 00:02:41.699 align:start position:0% filters they are really simple data structures<00:02:39.670> just<00:02:39.700> a<00:02:40.120> 2048-bit<00:02:41.080> long<00:02:41.500> bit 00:02:41.699 --> 00:02:41.709 align:start position:0% structures just a 2048-bit long bit 00:02:41.709 --> 00:02:45.150 align:start position:0% structures just a 2048-bit long bit vector<00:02:42.069> and<00:02:42.310> for<00:02:43.239> every<00:02:43.560> log<00:02:44.560> address<00:02:45.010> on 00:02:45.150 --> 00:02:45.160 align:start position:0% vector and for every log address on 00:02:45.160 --> 00:02:47.520 align:start position:0% vector and for every log address on topic<00:02:45.489> three<00:02:45.730> quasi<00:02:46.420> random<00:02:46.870> bits<00:02:47.079> are<00:02:47.230> set 00:02:47.520 --> 00:02:47.530 align:start position:0% topic three quasi random bits are set 00:02:47.530 --> 00:02:49.440 align:start position:0% topic three quasi random bits are set and<00:02:47.799> if<00:02:48.190> someone<00:02:48.730> else<00:02:48.760> is<00:02:48.970> looking<00:02:49.090> for<00:02:49.390> the 00:02:49.440 --> 00:02:49.450 align:start position:0% and if someone else is looking for the 00:02:49.450 --> 00:02:51.300 align:start position:0% and if someone else is looking for the same<00:02:49.630> events<00:02:49.959> later<00:02:50.170> they<00:02:50.470> can<00:02:50.650> just<00:02:50.920> check 00:02:51.300 --> 00:02:51.310 align:start position:0% same events later they can just check 00:02:51.310 --> 00:02:53.130 align:start position:0% same events later they can just check for<00:02:51.340> these<00:02:51.640> three<00:02:51.880> bits<00:02:52.120> if<00:02:52.450> they<00:02:52.630> are<00:02:52.750> set<00:02:52.930> and 00:02:53.130 --> 00:02:53.140 align:start position:0% for these three bits if they are set and 00:02:53.140 --> 00:02:55.470 align:start position:0% for these three bits if they are set and only<00:02:53.200> check<00:02:53.470> the<00:02:53.530> work<00:02:53.860> receipts<00:02:54.190> if<00:02:54.370> bits<00:02:55.299> are 00:02:55.470 --> 00:02:55.480 align:start position:0% only check the work receipts if bits are 00:02:55.480 --> 00:02:57.960 align:start position:0% only check the work receipts if bits are set<00:02:55.690> and<00:02:56.049> this<00:02:56.620> is<00:02:56.680> already<00:02:57.099> a<00:02:57.340> good 00:02:57.960 --> 00:02:57.970 align:start position:0% set and this is already a good 00:02:57.970 --> 00:02:59.460 align:start position:0% set and this is already a good performance<00:02:58.480> improvement<00:02:59.049> compared<00:02:59.410> to 00:02:59.460 --> 00:02:59.470 align:start position:0% performance improvement compared to 00:02:59.470 --> 00:03:00.780 align:start position:0% performance improvement compared to checking<00:02:59.799> all<00:02:59.980> the<00:03:00.129> block<00:03:00.310> receipts<00:03:00.610> in<00:03:00.760> the 00:03:00.780 --> 00:03:00.790 align:start position:0% checking all the block receipts in the 00:03:00.790 --> 00:03:03.300 align:start position:0% checking all the block receipts in the entire<00:03:01.150> history<00:03:01.360> but<00:03:01.840> still<00:03:02.310> checking 00:03:03.300 --> 00:03:03.310 align:start position:0% entire history but still checking 00:03:03.310 --> 00:03:04.890 align:start position:0% entire history but still checking checking<00:03:03.459> them<00:03:03.940> means<00:03:04.299> that<00:03:04.390> you<00:03:04.599> have<00:03:04.750> to 00:03:04.890 --> 00:03:04.900 align:start position:0% checking them means that you have to 00:03:04.900 --> 00:03:06.750 align:start position:0% checking them means that you have to read<00:03:05.170> the<00:03:05.470> entire<00:03:05.829> header<00:03:06.250> chain<00:03:06.579> which<00:03:06.730> is 00:03:06.750 --> 00:03:06.760 align:start position:0% read the entire header chain which is 00:03:06.760 --> 00:03:08.910 align:start position:0% read the entire header chain which is already<00:03:07.180> more<00:03:07.299> than<00:03:07.450> two<00:03:07.660> gigabytes<00:03:08.140> and<00:03:08.440> it 00:03:08.910 --> 00:03:08.920 align:start position:0% already more than two gigabytes and it 00:03:08.920 --> 00:03:11.089 align:start position:0% already more than two gigabytes and it was<00:03:09.099> kind<00:03:09.310> of<00:03:09.430> slow<00:03:09.790> even<00:03:10.000> on<00:03:10.180> a<00:03:10.269> foo<00:03:10.480> node<00:03:10.720> and 00:03:11.089 --> 00:03:11.099 align:start position:0% was kind of slow even on a foo node and 00:03:11.099 --> 00:03:14.490 align:start position:0% was kind of slow even on a foo node and with<00:03:12.099> a<00:03:12.129> light<00:03:12.340> client<00:03:12.730> it<00:03:12.910> is<00:03:13.200> even<00:03:14.200> worse 00:03:14.490 --> 00:03:14.500 align:start position:0% with a light client it is even worse 00:03:14.500 --> 00:03:18.210 align:start position:0% with a light client it is even worse because<00:03:15.959> downloading<00:03:16.959> the<00:03:17.079> and<00:03:17.350> keeping<00:03:18.100> the 00:03:18.210 --> 00:03:18.220 align:start position:0% because downloading the and keeping the 00:03:18.220 --> 00:03:20.009 align:start position:0% because downloading the and keeping the entire<00:03:18.459> hydrogen<00:03:19.000> locally<00:03:19.480> is<00:03:19.600> something 00:03:20.009 --> 00:03:20.019 align:start position:0% entire hydrogen locally is something 00:03:20.019 --> 00:03:22.559 align:start position:0% entire hydrogen locally is something that<00:03:20.230> some<00:03:20.650> devices<00:03:20.920> just<00:03:21.340> don't<00:03:22.180> want<00:03:22.359> to<00:03:22.450> do 00:03:22.559 --> 00:03:22.569 align:start position:0% that some devices just don't want to do 00:03:22.569 --> 00:03:25.050 align:start position:0% that some devices just don't want to do cannot<00:03:22.840> do<00:03:23.019> and<00:03:23.340> that's<00:03:24.340> also<00:03:24.670> why<00:03:25.030> we 00:03:25.050 --> 00:03:25.060 align:start position:0% cannot do and that's also why we 00:03:25.060 --> 00:03:27.660 align:start position:0% cannot do and that's also why we implemented<00:03:25.989> the<00:03:26.109> checkpoint<00:03:26.530> syncing<00:03:26.980> so 00:03:27.660 --> 00:03:27.670 align:start position:0% implemented the checkpoint syncing so 00:03:27.670 --> 00:03:29.280 align:start position:0% implemented the checkpoint syncing so that<00:03:27.880> we<00:03:28.299> can<00:03:28.450> avoid<00:03:28.630> downloading<00:03:28.900> all<00:03:29.260> the 00:03:29.280 --> 00:03:29.290 align:start position:0% that we can avoid downloading all the 00:03:29.290 --> 00:03:30.750 align:start position:0% that we can avoid downloading all the headers<00:03:29.650> but<00:03:29.859> then<00:03:30.010> we<00:03:30.130> don't<00:03:30.310> have<00:03:30.489> all<00:03:30.609> the 00:03:30.750 --> 00:03:30.760 align:start position:0% headers but then we don't have all the 00:03:30.760 --> 00:03:33.449 align:start position:0% headers but then we don't have all the movie<00:03:31.329> theaters<00:03:31.660> either<00:03:31.959> so<00:03:32.349> we<00:03:32.769> needed<00:03:33.010> some 00:03:33.449 --> 00:03:33.459 align:start position:0% movie theaters either so we needed some 00:03:33.459 --> 00:03:37.500 align:start position:0% movie theaters either so we needed some flavor<00:03:33.849> travel<00:03:34.510> data<00:03:34.630> structure<00:03:35.620> and<00:03:36.359> what<00:03:37.359> we 00:03:37.500 --> 00:03:37.510 align:start position:0% flavor travel data structure and what we 00:03:37.510 --> 00:03:41.550 align:start position:0% flavor travel data structure and what we did<00:03:37.690> is<00:03:37.930> we<00:03:38.650> take<00:03:39.160> a<00:03:39.870> fixed<00:03:40.870> length<00:03:41.079> sections 00:03:41.550 --> 00:03:41.560 align:start position:0% did is we take a fixed length sections 00:03:41.560 --> 00:03:44.970 align:start position:0% did is we take a fixed length sections of<00:03:41.739> consecutive<00:03:42.370> blocks<00:03:42.549> and<00:03:43.500> put<00:03:44.500> the<00:03:44.739> bloom 00:03:44.970 --> 00:03:44.980 align:start position:0% of consecutive blocks and put the bloom 00:03:44.980 --> 00:03:47.550 align:start position:0% of consecutive blocks and put the bloom filters<00:03:45.340> of<00:03:45.609> them<00:03:45.910> under<00:03:46.359> each<00:03:46.510> other<00:03:46.750> imagine 00:03:47.550 --> 00:03:47.560 align:start position:0% filters of them under each other imagine 00:03:47.560 --> 00:03:50.039 align:start position:0% filters of them under each other imagine that<00:03:47.859> there's<00:03:48.010> a<00:03:48.069> bitmap<00:03:48.250> and<00:03:48.730> you<00:03:49.030> can<00:03:49.299> see<00:03:49.780> on 00:03:50.039 --> 00:03:50.049 align:start position:0% that there's a bitmap and you can see on 00:03:50.049 --> 00:03:53.220 align:start position:0% that there's a bitmap and you can see on the<00:03:50.260> left<00:03:50.889> blue<00:03:51.160> box<00:03:51.400> then<00:03:51.940> when<00:03:52.900> doing<00:03:53.109> a 00:03:53.220 --> 00:03:53.230 align:start position:0% the left blue box then when doing a 00:03:53.230 --> 00:03:55.319 align:start position:0% the left blue box then when doing a simple<00:03:53.739> search<00:03:54.069> we<00:03:54.370> are<00:03:54.459> interested<00:03:54.970> in<00:03:55.090> three 00:03:55.319 --> 00:03:55.329 align:start position:0% simple search we are interested in three 00:03:55.329 --> 00:03:57.690 align:start position:0% simple search we are interested in three vertical<00:03:55.810> columns<00:03:56.139> in<00:03:56.319> this<00:03:56.440> bitmap<00:03:56.859> which<00:03:57.459> is 00:03:57.690 --> 00:03:57.700 align:start position:0% vertical columns in this bitmap which is 00:03:57.700 --> 00:04:00.569 align:start position:0% vertical columns in this bitmap which is still<00:03:58.450> if<00:03:58.720> you<00:03:59.410> read<00:03:59.650> this<00:03:59.829> you<00:04:00.160> had<00:04:00.310> to<00:04:00.430> read 00:04:00.569 --> 00:04:00.579 align:start position:0% still if you read this you had to read 00:04:00.579 --> 00:04:02.390 align:start position:0% still if you read this you had to read all<00:04:00.700> the<00:04:00.819> bloom<00:04:01.000> filters<00:04:01.329> from<00:04:01.510> this<00:04:01.780> because 00:04:02.390 --> 00:04:02.400 align:start position:0% all the bloom filters from this because 00:04:02.400 --> 00:04:05.069 align:start position:0% all the bloom filters from this because it's<00:04:03.400> a<00:04:03.639> that<00:04:04.209> ties<00:04:04.389> it<00:04:04.630> back<00:04:04.660> to<00:04:04.959> the 00:04:05.069 --> 00:04:05.079 align:start position:0% it's a that ties it back to the 00:04:05.079 --> 00:04:06.539 align:start position:0% it's a that ties it back to the interesting<00:04:05.440> bits<00:04:05.620> are<00:04:05.799> not<00:04:05.829> tightly<00:04:06.250> packed 00:04:06.539 --> 00:04:06.549 align:start position:0% interesting bits are not tightly packed 00:04:06.549 --> 00:04:08.370 align:start position:0% interesting bits are not tightly packed together<00:04:06.639> but<00:04:07.090> if<00:04:07.239> we<00:04:07.359> do<00:04:07.510> a<00:04:07.540> 90<00:04:08.079> degree 00:04:08.370 --> 00:04:08.380 align:start position:0% together but if we do a 90 degree 00:04:08.380 --> 00:04:11.509 align:start position:0% together but if we do a 90 degree rotation<00:04:08.410> of<00:04:08.980> this<00:04:09.130> bitmap<00:04:09.370> we<00:04:10.329> will<00:04:11.079> get 00:04:11.509 --> 00:04:11.519 align:start position:0% rotation of this bitmap we will get 00:04:11.519 --> 00:04:13.680 align:start position:0% rotation of this bitmap we will get horizontal<00:04:12.519> lines<00:04:12.730> horizontal<00:04:13.359> lines<00:04:13.510> will 00:04:13.680 --> 00:04:13.690 align:start position:0% horizontal lines horizontal lines will 00:04:13.690 --> 00:04:15.539 align:start position:0% horizontal lines horizontal lines will be<00:04:13.840> interesting<00:04:14.290> for<00:04:14.470> us<00:04:14.500> just<00:04:15.130> three<00:04:15.370> lines 00:04:15.539 --> 00:04:15.549 align:start position:0% be interesting for us just three lines 00:04:15.549 --> 00:04:17.969 align:start position:0% be interesting for us just three lines out<00:04:15.790> of<00:04:15.819> the<00:04:15.970> mm<00:04:16.750> so<00:04:16.989> we<00:04:17.200> only<00:04:17.380> have<00:04:17.620> to<00:04:17.799> read 00:04:17.969 --> 00:04:17.979 align:start position:0% out of the mm so we only have to read 00:04:17.979 --> 00:04:20.729 align:start position:0% out of the mm so we only have to read those<00:04:18.220> and<00:04:18.549> this<00:04:19.269> optimization<00:04:19.959> already<00:04:20.440> used 00:04:20.729 --> 00:04:20.739 align:start position:0% those and this optimization already used 00:04:20.739 --> 00:04:22.560 align:start position:0% those and this optimization already used a<00:04:20.950> two<00:04:21.400> or<00:04:21.609> three<00:04:21.849> orders<00:04:22.390> of<00:04:22.510> magnitude 00:04:22.560 --> 00:04:22.570 align:start position:0% a two or three orders of magnitude 00:04:22.570 --> 00:04:24.510 align:start position:0% a two or three orders of magnitude performance<00:04:23.560> improvement<00:04:24.099> it<00:04:24.250> looks 00:04:24.510 --> 00:04:24.520 align:start position:0% performance improvement it looks 00:04:24.520 --> 00:04:27.480 align:start position:0% performance improvement it looks searching<00:04:24.879> and<00:04:25.229> it<00:04:26.229> also<00:04:26.500> verse<00:04:26.889> nicely<00:04:27.370> with 00:04:27.480 --> 00:04:27.490 align:start position:0% searching and it also verse nicely with 00:04:27.490 --> 00:04:30.180 align:start position:0% searching and it also verse nicely with life<00:04:27.729> science<00:04:27.970> by<00:04:28.270> the<00:04:28.330> way<00:04:28.590> this<00:04:29.590> requires 00:04:30.180 --> 00:04:30.190 align:start position:0% life science by the way this requires 00:04:30.190 --> 00:04:31.650 align:start position:0% life science by the way this requires the<00:04:30.460> second<00:04:30.879> version<00:04:31.030> of<00:04:31.300> the<00:04:31.449> earliest 00:04:31.650 --> 00:04:31.660 align:start position:0% the second version of the earliest 00:04:31.660 --> 00:04:33.360 align:start position:0% the second version of the earliest protocol<00:04:32.199> which<00:04:32.319> has<00:04:32.530> just<00:04:32.710> recently<00:04:32.860> been 00:04:33.360 --> 00:04:33.370 align:start position:0% protocol which has just recently been 00:04:33.370 --> 00:04:35.460 align:start position:0% protocol which has just recently been merged<00:04:33.759> into<00:04:33.940> the<00:04:34.120> GUI<00:04:34.569> terraeum<00:04:35.020> code<00:04:35.259> base 00:04:35.460 --> 00:04:35.470 align:start position:0% merged into the GUI terraeum code base 00:04:35.470 --> 00:04:40.649 align:start position:0% merged into the GUI terraeum code base and<00:04:36.509> and<00:04:37.919> it<00:04:38.919> also<00:04:39.099> works<00:04:39.400> very<00:04:39.490> nicely<00:04:39.940> it<00:04:40.419> can 00:04:40.649 --> 00:04:40.659 align:start position:0% and and it also works very nicely it can 00:04:40.659 --> 00:04:42.869 align:start position:0% and and it also works very nicely it can filter<00:04:40.900> the<00:04:41.080> entire<00:04:41.379> history<00:04:41.830> in<00:04:42.190> a<00:04:42.280> second 00:04:42.869 --> 00:04:42.879 align:start position:0% filter the entire history in a second 00:04:42.879 --> 00:04:44.670 align:start position:0% filter the entire history in a second few<00:04:43.240> seconds<00:04:43.720> but<00:04:44.139> there<00:04:44.349> was<00:04:44.470> another 00:04:44.670 --> 00:04:44.680 align:start position:0% few seconds but there was another 00:04:44.680 --> 00:04:46.619 align:start position:0% few seconds but there was another problem<00:04:44.979> we<00:04:45.250> had<00:04:45.370> to<00:04:45.400> solve<00:04:45.849> in<00:04:46.180> order<00:04:46.419> for 00:04:46.619 --> 00:04:46.629 align:start position:0% problem we had to solve in order for 00:04:46.629 --> 00:04:48.629 align:start position:0% problem we had to solve in order for this<00:04:46.720> to<00:04:46.780> work<00:04:46.900> namely<00:04:47.800> that<00:04:48.069> these<00:04:48.400> data 00:04:48.629 --> 00:04:48.639 align:start position:0% this to work namely that these data 00:04:48.639 --> 00:04:50.279 align:start position:0% this to work namely that these data structures<00:04:49.000> are<00:04:49.389> not<00:04:49.599> a<00:04:49.629> part<00:04:50.080> of<00:04:50.169> the 00:04:50.279 --> 00:04:50.289 align:start position:0% structures are not a part of the 00:04:50.289 --> 00:04:53.850 align:start position:0% structures are not a part of the consensus<00:04:50.979> so<00:04:51.520> we<00:04:52.270> needed<00:04:52.690> some<00:04:53.080> so<00:04:53.650> a<00:04:53.680> nice 00:04:53.850 --> 00:04:53.860 align:start position:0% consensus so we needed some so a nice 00:04:53.860 --> 00:04:55.499 align:start position:0% consensus so we needed some so a nice thing<00:04:54.069> is<00:04:54.159> going<00:04:54.310> to<00:04:54.400> directly<00:04:54.759> validate<00:04:55.330> it 00:04:55.499 --> 00:04:55.509 align:start position:0% thing is going to directly validate it 00:04:55.509 --> 00:04:57.360 align:start position:0% thing is going to directly validate it even<00:04:55.750> though<00:04:55.900> lightsabers<00:04:56.530> can<00:04:56.740> generate<00:04:57.039> and 00:04:57.360 --> 00:04:57.370 align:start position:0% even though lightsabers can generate and 00:04:57.370 --> 00:05:01.680 align:start position:0% even though lightsabers can generate and serve<00:04:57.610> it<00:04:57.819> and<00:04:58.530> in<00:04:59.530> order<00:04:59.919> to<00:05:00.190> solve<00:05:01.150> this<00:05:01.360> we 00:05:01.680 --> 00:05:01.690 align:start position:0% serve it and in order to solve this we 00:05:01.690 --> 00:05:03.659 align:start position:0% serve it and in order to solve this we created<00:05:02.139> a<00:05:02.349> special<00:05:02.530> try<00:05:03.190> the<00:05:03.250> bloom<00:05:03.639> filter 00:05:03.659 --> 00:05:03.669 align:start position:0% created a special try the bloom filter 00:05:03.669 --> 00:05:06.390 align:start position:0% created a special try the bloom filter try<00:05:04.330> and<00:05:04.659> organize<00:05:05.650> all<00:05:05.680> the<00:05:06.039> bits<00:05:06.250> between 00:05:06.390 --> 00:05:06.400 align:start position:0% try and organize all the bits between 00:05:06.400 --> 00:05:08.490 align:start position:0% try and organize all the bits between this<00:05:06.759> try<00:05:06.970> so<00:05:07.210> that<00:05:07.240> the<00:05:07.539> light<00:05:07.690> client<00:05:08.110> only 00:05:08.490 --> 00:05:08.500 align:start position:0% this try so that the light client only 00:05:08.500 --> 00:05:10.950 align:start position:0% this try so that the light client only needs<00:05:08.680> to<00:05:08.860> know<00:05:08.889> the<00:05:09.280> root<00:05:10.240> hash<00:05:10.419> of<00:05:10.569> the<00:05:10.720> bloom 00:05:10.950 --> 00:05:10.960 align:start position:0% needs to know the root hash of the bloom 00:05:10.960 --> 00:05:13.110 align:start position:0% needs to know the root hash of the bloom filter<00:05:10.990> try<00:05:11.530> and<00:05:11.800> use<00:05:11.979> math<00:05:12.220> to<00:05:12.430> validate 00:05:13.110 --> 00:05:13.120 align:start position:0% filter try and use math to validate 00:05:13.120 --> 00:05:13.980 align:start position:0% filter try and use math to validate everything<00:05:13.479> else 00:05:13.980 --> 00:05:13.990 align:start position:0% everything else 00:05:13.990 --> 00:05:15.959 align:start position:0% everything else of<00:05:14.229> course<00:05:14.560> the<00:05:14.710> question<00:05:14.949> still<00:05:15.430> remains<00:05:15.819> how 00:05:15.959 --> 00:05:15.969 align:start position:0% of course the question still remains how 00:05:15.969 --> 00:05:18.930 align:start position:0% of course the question still remains how a<00:05:16.419> light<00:05:16.659> client<00:05:17.080> can<00:05:18.039> trust<00:05:18.310> the<00:05:18.639> bloom 00:05:18.930 --> 00:05:18.940 align:start position:0% a light client can trust the bloom 00:05:18.940 --> 00:05:21.659 align:start position:0% a light client can trust the bloom filter<00:05:19.020> root<00:05:20.020> hash<00:05:20.259> computer<00:05:21.009> train<00:05:21.250> route<00:05:21.460> - 00:05:21.659 --> 00:05:21.669 align:start position:0% filter root hash computer train route - 00:05:21.669 --> 00:05:25.709 align:start position:0% filter root hash computer train route - and<00:05:23.159> currently<00:05:24.159> we<00:05:24.699> are<00:05:24.819> doing<00:05:25.120> checkpoint 00:05:25.709 --> 00:05:25.719 align:start position:0% and currently we are doing checkpoint 00:05:25.719 --> 00:05:28.140 align:start position:0% and currently we are doing checkpoint syncing<00:05:26.169> with<00:05:26.379> hard-coded<00:05:27.159> trusted 00:05:28.140 --> 00:05:28.150 align:start position:0% syncing with hard-coded trusted 00:05:28.150 --> 00:05:29.430 align:start position:0% syncing with hard-coded trusted checkpoints<00:05:28.690> which<00:05:28.810> is<00:05:28.960> only<00:05:29.139> a<00:05:29.229> temporary 00:05:29.430 --> 00:05:29.440 align:start position:0% checkpoints which is only a temporary 00:05:29.440 --> 00:05:32.100 align:start position:0% checkpoints which is only a temporary solution<00:05:29.889> and<00:05:30.460> right<00:05:30.639> now<00:05:30.819> the<00:05:31.080> bloom<00:05:32.080> filter 00:05:32.100 --> 00:05:32.110 align:start position:0% solution and right now the bloom filter 00:05:32.110 --> 00:05:33.990 align:start position:0% solution and right now the bloom filter tries<00:05:32.650> also<00:05:33.069> hard-coded<00:05:33.639> into<00:05:33.819> this 00:05:33.990 --> 00:05:34.000 align:start position:0% tries also hard-coded into this 00:05:34.000 --> 00:05:37.170 align:start position:0% tries also hard-coded into this checkpoint<00:05:34.240> but<00:05:35.280> soon<00:05:36.280> we<00:05:36.400> would<00:05:36.520> like<00:05:36.729> to<00:05:36.759> get 00:05:37.170 --> 00:05:37.180 align:start position:0% checkpoint but soon we would like to get 00:05:37.180 --> 00:05:39.659 align:start position:0% checkpoint but soon we would like to get rid<00:05:37.360> of<00:05:37.419> hat<00:05:37.719> for<00:05:37.900> the<00:05:37.990> checkpoint<00:05:38.440> and<00:05:38.740> use 00:05:39.659 --> 00:05:39.669 align:start position:0% rid of hat for the checkpoint and use 00:05:39.669 --> 00:05:43.700 align:start position:0% rid of hat for the checkpoint and use trustless<00:05:40.740> validation<00:05:41.740> of<00:05:41.830> checkpoints<00:05:42.639> and 00:05:43.700 --> 00:05:43.710 align:start position:0% trustless validation of checkpoints and 00:05:43.710 --> 00:05:46.019 align:start position:0% trustless validation of checkpoints and in<00:05:44.710> order<00:05:44.949> to<00:05:45.009> do<00:05:45.219> this<00:05:45.370> we<00:05:45.550> need<00:05:45.580> to<00:05:45.819> somehow 00:05:46.019 --> 00:05:46.029 align:start position:0% in order to do this we need to somehow 00:05:46.029 --> 00:05:48.180 align:start position:0% in order to do this we need to somehow validate<00:05:46.569> the<00:05:46.900> bloom<00:05:47.199> filter<00:05:47.229> try<00:05:47.740> on<00:05:47.919> chain 00:05:48.180 --> 00:05:48.190 align:start position:0% validate the bloom filter try on chain 00:05:48.190 --> 00:05:49.920 align:start position:0% validate the bloom filter try on chain and<00:05:48.400> this<00:05:48.490> is<00:05:48.639> where<00:05:48.880> of<00:05:49.090> chain<00:05:49.419> validation 00:05:49.920 --> 00:05:49.930 align:start position:0% and this is where of chain validation 00:05:49.930 --> 00:05:51.600 align:start position:0% and this is where of chain validation comes<00:05:50.080> into<00:05:50.349> the<00:05:50.440> picture<00:05:50.650> because<00:05:51.250> all<00:05:51.490> the 00:05:51.600 --> 00:05:51.610 align:start position:0% comes into the picture because all the 00:05:51.610 --> 00:05:53.279 align:start position:0% comes into the picture because all the light<00:05:51.759> servers<00:05:52.210> know<00:05:52.449> the<00:05:52.599> input<00:05:52.870> data<00:05:52.990> which 00:05:53.279 --> 00:05:53.289 align:start position:0% light servers know the input data which 00:05:53.289 --> 00:05:54.870 align:start position:0% light servers know the input data which is<00:05:53.440> the<00:05:53.529> header<00:05:53.710> chain<00:05:54.099> and<00:05:54.310> this<00:05:54.729> is<00:05:54.849> a 00:05:54.870 --> 00:05:54.880 align:start position:0% is the header chain and this is a 00:05:54.880 --> 00:05:57.330 align:start position:0% is the header chain and this is a deterministic<00:05:55.509> calculation<00:05:56.199> that<00:05:56.229> they<00:05:56.830> do 00:05:57.330 --> 00:05:57.340 align:start position:0% deterministic calculation that they do 00:05:57.340 --> 00:06:01.080 align:start position:0% deterministic calculation that they do anyway<00:05:57.699> so<00:05:57.969> servers<00:05:58.930> can<00:05:59.169> send<00:05:59.830> the<00:06:00.759> route<00:06:00.909> - 00:06:01.080 --> 00:06:01.090 align:start position:0% anyway so servers can send the route - 00:06:01.090 --> 00:06:03.300 align:start position:0% anyway so servers can send the route - new<00:06:01.330> route<00:06:01.509> hashes<00:06:01.870> to<00:06:01.900> a<00:06:02.050> judge<00:06:02.380> contract<00:06:02.889> and 00:06:03.300 --> 00:06:03.310 align:start position:0% new route hashes to a judge contract and 00:06:03.310 --> 00:06:06.870 align:start position:0% new route hashes to a judge contract and only<00:06:04.000> do<00:06:04.750> well<00:06:05.050> -<00:06:05.259> and<00:06:05.500> if<00:06:05.680> necessary<00:06:06.039> if<00:06:06.639> a 00:06:06.870 --> 00:06:06.880 align:start position:0% only do well - and if necessary if a 00:06:06.880 --> 00:06:08.610 align:start position:0% only do well - and if necessary if a route<00:06:07.270> has<00:06:07.509> remains<00:06:07.810> unchallenged<00:06:08.199> on<00:06:08.500> the 00:06:08.610 --> 00:06:08.620 align:start position:0% route has remains unchallenged on the 00:06:08.620 --> 00:06:11.189 align:start position:0% route has remains unchallenged on the chain<00:06:08.830> for<00:06:09.069> quite<00:06:09.310> good<00:06:10.120> Afghan<00:06:10.449> time<00:06:10.990> then 00:06:11.189 --> 00:06:11.199 align:start position:0% chain for quite good Afghan time then 00:06:11.199 --> 00:06:13.200 align:start position:0% chain for quite good Afghan time then the<00:06:11.380> clients<00:06:11.770> can<00:06:11.949> trust<00:06:12.219> it<00:06:12.430> of<00:06:12.789> course<00:06:13.000> we 00:06:13.200 --> 00:06:13.210 align:start position:0% the clients can trust it of course we 00:06:13.210 --> 00:06:16.529 align:start position:0% the clients can trust it of course we still<00:06:13.360> also<00:06:13.810> need<00:06:14.080> some<00:06:15.090> security<00:06:16.090> deposits 00:06:16.529 --> 00:06:16.539 align:start position:0% still also need some security deposits 00:06:16.539 --> 00:06:20.070 align:start position:0% still also need some security deposits and<00:06:17.099> other<00:06:18.099> incentives<00:06:18.759> to<00:06:19.060> make<00:06:19.719> the<00:06:19.900> system 00:06:20.070 --> 00:06:20.080 align:start position:0% and other incentives to make the system 00:06:20.080 --> 00:06:25.189 align:start position:0% and other incentives to make the system work<00:06:20.289> but<00:06:20.560> that's<00:06:20.680> also<00:06:21.130> part<00:06:21.460> of<00:06:21.639> the<00:06:21.849> plan 00:06:25.189 --> 00:06:25.199 align:start position:0% 00:06:25.199 --> 00:06:30.100 align:start position:0% now<00:06:26.199> let<00:06:26.620> me<00:06:26.800> also<00:06:27.599> talk<00:06:28.599> about 00:06:30.100 --> 00:06:30.110 align:start position:0% now let me also talk about 00:06:30.110 --> 00:06:33.480 align:start position:0% now let me also talk about how<00:06:31.100> I<00:06:31.130> imagine<00:06:31.970> the<00:06:32.150> future<00:06:32.390> challenges<00:06:33.110> the 00:06:33.480 --> 00:06:33.490 align:start position:0% how I imagine the future challenges the 00:06:33.490 --> 00:06:36.280 align:start position:0% how I imagine the future challenges the massive<00:06:34.490> chain<00:06:34.670> higher<00:06:34.880> his<00:06:35.270> and<00:06:35.600> scaling 00:06:36.280 --> 00:06:36.290 align:start position:0% massive chain higher his and scaling 00:06:36.290 --> 00:06:41.290 align:start position:0% massive chain higher his and scaling will<00:06:36.800> mean<00:06:37.460> for<00:06:37.670> life<00:06:37.820> lions<00:06:38.210> and<00:06:38.390> what<00:06:40.120> we<00:06:41.120> can 00:06:41.290 --> 00:06:41.300 align:start position:0% will mean for life lions and what we can 00:06:41.300 --> 00:06:45.460 align:start position:0% will mean for life lions and what we can do<00:06:41.720> about<00:06:41.990> it<00:06:42.850> here's<00:06:43.850> an<00:06:44.150> example<00:06:44.720> situation 00:06:45.460 --> 00:06:45.470 align:start position:0% do about it here's an example situation 00:06:45.470 --> 00:06:47.740 align:start position:0% do about it here's an example situation where<00:06:45.770> there's<00:06:46.220> a<00:06:46.280> user<00:06:47.150> who<00:06:47.450> wants<00:06:47.570> to 00:06:47.740 --> 00:06:47.750 align:start position:0% where there's a user who wants to 00:06:47.750 --> 00:06:49.720 align:start position:0% where there's a user who wants to observe<00:06:48.080> a<00:06:48.470> subset<00:06:48.920> of<00:06:49.070> the<00:06:49.250> change<00:06:49.490> in 00:06:49.720 --> 00:06:49.730 align:start position:0% observe a subset of the change in 00:06:49.730 --> 00:06:52.660 align:start position:0% observe a subset of the change in hierarchy<00:06:50.390> which<00:06:51.110> may<00:06:51.650> could<00:06:52.070> still<00:06:52.310> be<00:06:52.490> a 00:06:52.660 --> 00:06:52.670 align:start position:0% hierarchy which may could still be a 00:06:52.670 --> 00:06:55.690 align:start position:0% hierarchy which may could still be a quite<00:06:53.060> a<00:06:53.090> subset<00:06:53.870> right<00:06:54.290> now<00:06:54.530> our<00:06:54.860> imaginary 00:06:55.690 --> 00:06:55.700 align:start position:0% quite a subset right now our imaginary 00:06:55.700 --> 00:06:57.760 align:start position:0% quite a subset right now our imaginary user<00:06:56.060> uses<00:06:56.540> a<00:06:56.690> decentralized<00:06:57.560> the 00:06:57.760 --> 00:06:57.770 align:start position:0% user uses a decentralized the 00:06:57.770 --> 00:07:00.640 align:start position:0% user uses a decentralized the marketplace<00:06:58.370> which<00:06:58.700> has<00:06:59.330> a<00:06:59.360> multiple<00:07:00.350> state 00:07:00.640 --> 00:07:00.650 align:start position:0% marketplace which has a multiple state 00:07:00.650 --> 00:07:02.440 align:start position:0% marketplace which has a multiple state channels<00:07:01.040> for<00:07:01.280> listing<00:07:01.640> different<00:07:02.090> market 00:07:02.440 --> 00:07:02.450 align:start position:0% channels for listing different market 00:07:02.450 --> 00:07:04.630 align:start position:0% channels for listing different market offers<00:07:02.810> like<00:07:03.410> one<00:07:03.650> for<00:07:03.920> listing<00:07:04.250> crypto 00:07:04.630 --> 00:07:04.640 align:start position:0% offers like one for listing crypto 00:07:04.640 --> 00:07:06.460 align:start position:0% offers like one for listing crypto versus<00:07:05.090> the<00:07:05.240> administrator<00:07:05.810> first<00:07:06.170> and<00:07:06.350> other 00:07:06.460 --> 00:07:06.470 align:start position:0% versus the administrator first and other 00:07:06.470 --> 00:07:09.940 align:start position:0% versus the administrator first and other for<00:07:06.770> listing<00:07:07.100> secondhand<00:07:07.730> cars<00:07:08.090> and<00:07:08.480> the<00:07:09.260> new 00:07:09.940 --> 00:07:09.950 align:start position:0% for listing secondhand cars and the new 00:07:09.950 --> 00:07:11.970 align:start position:0% for listing secondhand cars and the new service<00:07:10.430> which<00:07:10.640> has<00:07:10.820> a<00:07:10.880> state<00:07:11.210> channel<00:07:11.540> for 00:07:11.970 --> 00:07:11.980 align:start position:0% service which has a state channel for 00:07:11.980 --> 00:07:15.840 align:start position:0% service which has a state channel for weather<00:07:12.980> alerts<00:07:13.400> and<00:07:13.700> the<00:07:14.330> user<00:07:14.540> wants<00:07:15.050> to 00:07:15.840 --> 00:07:15.850 align:start position:0% weather alerts and the user wants to 00:07:15.850 --> 00:07:19.000 align:start position:0% weather alerts and the user wants to observe<00:07:16.850> this<00:07:17.300> change<00:07:17.660> and<00:07:17.930> get<00:07:18.530> notified 00:07:19.000 --> 00:07:19.010 align:start position:0% observe this change and get notified 00:07:19.010 --> 00:07:21.970 align:start position:0% observe this change and get notified about<00:07:20.380> interesting<00:07:21.380> result 00:07:21.970 --> 00:07:21.980 align:start position:0% about interesting result 00:07:21.980 --> 00:07:25.210 align:start position:0% about interesting result and<00:07:22.360> if<00:07:23.440> filtering<00:07:24.440> criteria<00:07:24.620> for 00:07:25.210 --> 00:07:25.220 align:start position:0% and if filtering criteria for 00:07:25.220 --> 00:07:28.000 align:start position:0% and if filtering criteria for interesting<00:07:25.760> events<00:07:26.690> might<00:07:27.080> be<00:07:27.260> even<00:07:27.890> more 00:07:28.000 --> 00:07:28.010 align:start position:0% interesting events might be even more 00:07:28.010 --> 00:07:31.090 align:start position:0% interesting events might be even more complex<00:07:28.460> than<00:07:29.080> what<00:07:30.080> could<00:07:30.350> be<00:07:30.500> realized<00:07:30.890> with 00:07:31.090 --> 00:07:31.100 align:start position:0% complex than what could be realized with 00:07:31.100 --> 00:07:34.240 align:start position:0% complex than what could be realized with our<00:07:31.460> current<00:07:31.700> simple<00:07:32.360> log<00:07:33.170> address<00:07:33.830> and<00:07:33.980> topic 00:07:34.240 --> 00:07:34.250 align:start position:0% our current simple log address and topic 00:07:34.250 --> 00:07:39.550 align:start position:0% our current simple log address and topic systems<00:07:35.740> so<00:07:36.740> it<00:07:37.280> would<00:07:37.520> be<00:07:37.700> great<00:07:38.600> if<00:07:38.900> clients 00:07:39.550 --> 00:07:39.560 align:start position:0% systems so it would be great if clients 00:07:39.560 --> 00:07:43.330 align:start position:0% systems so it would be great if clients could<00:07:40.450> somehow<00:07:41.450> get<00:07:42.380> some<00:07:42.620> help<00:07:42.860> for 00:07:43.330 --> 00:07:43.340 align:start position:0% could somehow get some help for 00:07:43.340 --> 00:07:45.880 align:start position:0% could somehow get some help for filtering<00:07:44.060> also<00:07:44.540> it's<00:07:44.720> possible<00:07:45.290> with<00:07:45.680> some 00:07:45.880 --> 00:07:45.890 align:start position:0% filtering also it's possible with some 00:07:45.890 --> 00:07:47.860 align:start position:0% filtering also it's possible with some station<00:07:46.370> or<00:07:46.490> technologies<00:07:47.060> that<00:07:47.540> you<00:07:47.720> will 00:07:47.860 --> 00:07:47.870 align:start position:0% station or technologies that you will 00:07:47.870 --> 00:07:50.500 align:start position:0% station or technologies that you will all<00:07:47.990> redone<00:07:48.290> that<00:07:48.530> use<00:07:48.800> law<00:07:49.280> redundancy<00:07:49.790> that 00:07:50.500 --> 00:07:50.510 align:start position:0% all redone that use law redundancy that 00:07:50.510 --> 00:07:52.930 align:start position:0% all redone that use law redundancy that their<00:07:50.870> security<00:07:51.130> security<00:07:52.130> model<00:07:52.550> is<00:07:52.700> based 00:07:52.930 --> 00:07:52.940 align:start position:0% their security security model is based 00:07:52.940 --> 00:07:55.480 align:start position:0% their security security model is based on<00:07:53.210> an<00:07:53.480> assumption<00:07:53.900> that<00:07:54.110> some<00:07:55.100> interested 00:07:55.480 --> 00:07:55.490 align:start position:0% on an assumption that some interested 00:07:55.490 --> 00:07:57.460 align:start position:0% on an assumption that some interested parties<00:07:55.910> actually<00:07:56.510> do<00:07:56.690> validate<00:07:57.080> the<00:07:57.230> chain 00:07:57.460 --> 00:07:57.470 align:start position:0% parties actually do validate the chain 00:07:57.470 --> 00:07:58.780 align:start position:0% parties actually do validate the chain and<00:07:57.680> that's<00:07:57.800> also<00:07:58.010> something<00:07:58.160> that<00:07:58.640> like 00:07:58.780 --> 00:07:58.790 align:start position:0% and that's also something that like 00:07:58.790 --> 00:08:00.970 align:start position:0% and that's also something that like clients<00:07:59.210> cannot<00:07:59.480> do<00:07:59.600> so<00:07:59.810> they<00:08:00.650> would<00:08:00.800> also 00:08:00.970 --> 00:08:00.980 align:start position:0% clients cannot do so they would also 00:08:00.980 --> 00:08:05.920 align:start position:0% clients cannot do so they would also require<00:08:01.460> some<00:08:02.890> insurance<00:08:03.890> to<00:08:04.700> be<00:08:05.510> able<00:08:05.630> to 00:08:05.920 --> 00:08:05.930 align:start position:0% require some insurance to be able to 00:08:05.930 --> 00:08:08.380 align:start position:0% require some insurance to be able to trust<00:08:06.200> the<00:08:06.620> validity<00:08:07.280> of<00:08:07.550> these<00:08:07.760> chains<00:08:08.090> I 00:08:08.380 --> 00:08:08.390 align:start position:0% trust the validity of these chains I 00:08:08.390 --> 00:08:11.770 align:start position:0% trust the validity of these chains I think<00:08:09.320> it<00:08:09.650> is<00:08:09.860> possible<00:08:10.040> that<00:08:10.490> they<00:08:11.330> can<00:08:11.570> have 00:08:11.770 --> 00:08:11.780 align:start position:0% think it is possible that they can have 00:08:11.780 --> 00:08:14.470 align:start position:0% think it is possible that they can have the<00:08:12.230> higher<00:08:12.710> right<00:08:13.310> servers<00:08:13.760> to<00:08:13.970> do<00:08:14.180> all<00:08:14.450> of 00:08:14.470 --> 00:08:14.480 align:start position:0% the higher right servers to do all of 00:08:14.480 --> 00:08:19.120 align:start position:0% the higher right servers to do all of this<00:08:14.750> for<00:08:15.080> them<00:08:15.260> and<00:08:16.450> also<00:08:17.450> it<00:08:17.960> would<00:08:18.170> be<00:08:18.320> even 00:08:19.120 --> 00:08:19.130 align:start position:0% this for them and also it would be even 00:08:19.130 --> 00:08:21.180 align:start position:0% this for them and also it would be even better<00:08:19.160> and<00:08:19.490> still<00:08:19.610> possible<00:08:20.060> to<00:08:20.420> build<00:08:20.690> a 00:08:21.180 --> 00:08:21.190 align:start position:0% better and still possible to build a 00:08:21.190 --> 00:08:24.040 align:start position:0% better and still possible to build a filtering<00:08:22.190> and<00:08:22.310> observing<00:08:22.790> hierarchy<00:08:23.540> for 00:08:24.040 --> 00:08:24.050 align:start position:0% filtering and observing hierarchy for 00:08:24.050 --> 00:08:26.110 align:start position:0% filtering and observing hierarchy for each<00:08:24.230> client<00:08:24.650> who<00:08:25.010> is<00:08:25.070> running<00:08:25.610> complex 00:08:26.110 --> 00:08:26.120 align:start position:0% each client who is running complex 00:08:26.120 --> 00:08:28.870 align:start position:0% each client who is running complex applications<00:08:26.810> this<00:08:27.740> higher<00:08:28.070> he<00:08:28.370> could<00:08:28.520> run<00:08:28.700> on 00:08:28.870 --> 00:08:28.880 align:start position:0% applications this higher he could run on 00:08:28.880 --> 00:08:31.150 align:start position:0% applications this higher he could run on multiple<00:08:29.120> light<00:08:29.600> servers<00:08:30.110> and<00:08:30.380> the<00:08:30.770> deliver 00:08:31.150 --> 00:08:31.160 align:start position:0% multiple light servers and the deliver 00:08:31.160 --> 00:08:34.000 align:start position:0% multiple light servers and the deliver just<00:08:31.580> the<00:08:31.640> interesting<00:08:32.360> results<00:08:33.140> from<00:08:33.290> the 00:08:34.000 --> 00:08:34.010 align:start position:0% just the interesting results from the 00:08:34.010 --> 00:08:36.910 align:start position:0% just the interesting results from the entire<00:08:34.580> computer<00:08:35.240> to<00:08:35.630> a<00:08:35.660> clients<00:08:36.290> who<00:08:36.680> can 00:08:36.910 --> 00:08:36.920 align:start position:0% entire computer to a clients who can 00:08:36.920 --> 00:08:39.250 align:start position:0% entire computer to a clients who can them<00:08:37.160> run<00:08:38.030> with<00:08:38.210> very<00:08:38.510> low<00:08:38.870> resource 00:08:39.250 --> 00:08:39.260 align:start position:0% them run with very low resource 00:08:39.260 --> 00:08:42.269 align:start position:0% them run with very low resource requirements 00:08:42.269 --> 00:08:42.279 align:start position:0% 00:08:42.279 --> 00:08:45.059 align:start position:0% I<00:08:42.339> would<00:08:43.209> like<00:08:43.360> to<00:08:43.509> show<00:08:44.019> too<00:08:44.470> I<00:08:44.499> would<00:08:44.800> like<00:08:44.920> to 00:08:45.059 --> 00:08:45.069 align:start position:0% I would like to show too I would like to 00:08:45.069 --> 00:08:47.309 align:start position:0% I would like to show too I would like to show<00:08:45.249> how<00:08:45.430> I<00:08:45.459> think<00:08:45.879> this<00:08:45.999> is<00:08:46.120> passable<00:08:46.449> so<00:08:47.079> let 00:08:47.309 --> 00:08:47.319 align:start position:0% show how I think this is passable so let 00:08:47.319 --> 00:08:48.989 align:start position:0% show how I think this is passable so let me<00:08:47.470> just<00:08:47.740> define<00:08:48.040> two<00:08:48.430> very<00:08:48.670> simple 00:08:48.989 --> 00:08:48.999 align:start position:0% me just define two very simple 00:08:48.999 --> 00:08:52.079 align:start position:0% me just define two very simple primitives<00:08:49.629> that<00:08:49.899> could<00:08:50.259> achieve<00:08:50.350> this<00:08:51.089> one 00:08:52.079 --> 00:08:52.089 align:start position:0% primitives that could achieve this one 00:08:52.089 --> 00:08:54.509 align:start position:0% primitives that could achieve this one of<00:08:52.240> them<00:08:52.389> is<00:08:52.600> called<00:08:52.870> the<00:08:53.139> chain<00:08:53.769> theater<00:08:54.279> a 00:08:54.509 --> 00:08:54.519 align:start position:0% of them is called the chain theater a 00:08:54.519 --> 00:08:56.850 align:start position:0% of them is called the chain theater a chain<00:08:54.970> theater<00:08:55.420> is<00:08:55.600> a<00:08:55.629> deterministic<00:08:56.560> set<00:08:56.740> of 00:08:56.850 --> 00:08:56.860 align:start position:0% chain theater is a deterministic set of 00:08:56.860 --> 00:08:58.949 align:start position:0% chain theater is a deterministic set of operations<00:08:57.459> performed<00:08:57.759> on<00:08:58.209> an<00:08:58.329> input<00:08:58.749> block 00:08:58.949 --> 00:08:58.959 align:start position:0% operations performed on an input block 00:08:58.959 --> 00:09:02.220 align:start position:0% operations performed on an input block chain<00:08:59.259> and<00:08:59.999> it<00:09:00.999> is<00:09:01.180> specified<00:09:01.600> preferably<00:09:02.110> in 00:09:02.220 --> 00:09:02.230 align:start position:0% chain and it is specified preferably in 00:09:02.230 --> 00:09:04.439 align:start position:0% chain and it is specified preferably in a<00:09:02.350> virtual<00:09:02.889> machine<00:09:02.920> that<00:09:03.309> is<00:09:03.459> suitable<00:09:03.939> both 00:09:04.439 --> 00:09:04.449 align:start position:0% a virtual machine that is suitable both 00:09:04.449 --> 00:09:07.619 align:start position:0% a virtual machine that is suitable both for<00:09:05.730> just-in-time<00:09:06.730> compilation<00:09:07.029> and 00:09:07.619 --> 00:09:07.629 align:start position:0% for just-in-time compilation and 00:09:07.629 --> 00:09:10.470 align:start position:0% for just-in-time compilation and interactive<00:09:08.110> validation<00:09:08.829> and<00:09:09.120> hm<00:09:10.120> theater 00:09:10.470 --> 00:09:10.480 align:start position:0% interactive validation and hm theater 00:09:10.480 --> 00:09:12.660 align:start position:0% interactive validation and hm theater can<00:09:10.720> have<00:09:10.930> its<00:09:11.139> own<00:09:11.350> state<00:09:11.680> but<00:09:11.709> not<00:09:12.220> its<00:09:12.490> own 00:09:12.660 --> 00:09:12.670 align:start position:0% can have its own state but not its own 00:09:12.670 --> 00:09:15.540 align:start position:0% can have its own state but not its own consensus<00:09:13.360> mechanism<00:09:13.870> because<00:09:14.290> a<00:09:14.550> chain 00:09:15.540 --> 00:09:15.550 align:start position:0% consensus mechanism because a chain 00:09:15.550 --> 00:09:16.860 align:start position:0% consensus mechanism because a chain theater<00:09:15.879> blocks<00:09:16.120> are<00:09:16.300> deterministic 00:09:16.860 --> 00:09:16.870 align:start position:0% theater blocks are deterministic 00:09:16.870 --> 00:09:18.660 align:start position:0% theater blocks are deterministic functions<00:09:17.470> of<00:09:17.649> previous<00:09:18.069> chain<00:09:18.309> theater 00:09:18.660 --> 00:09:18.670 align:start position:0% functions of previous chain theater 00:09:18.670 --> 00:09:20.220 align:start position:0% functions of previous chain theater blocks<00:09:18.939> and<00:09:19.180> new<00:09:19.329> import<00:09:19.749> blocks 00:09:20.220 --> 00:09:20.230 align:start position:0% blocks and new import blocks 00:09:20.230 --> 00:09:22.170 align:start position:0% blocks and new import blocks so<00:09:20.769> whatever<00:09:20.980> consensus<00:09:21.670> marries<00:09:21.970> in<00:09:22.059> the 00:09:22.170 --> 00:09:22.180 align:start position:0% so whatever consensus marries in the 00:09:22.180 --> 00:09:24.360 align:start position:0% so whatever consensus marries in the input<00:09:22.420> chain<00:09:22.660> uses<00:09:23.529> the<00:09:23.559> chain<00:09:23.829> theater<00:09:24.189> will 00:09:24.360 --> 00:09:24.370 align:start position:0% input chain uses the chain theater will 00:09:24.370 --> 00:09:26.939 align:start position:0% input chain uses the chain theater will just<00:09:24.610> follow<00:09:24.910> and<00:09:25.180> these<00:09:26.139> chain<00:09:26.379> filters<00:09:26.740> can 00:09:26.939 --> 00:09:26.949 align:start position:0% just follow and these chain filters can 00:09:26.949 --> 00:09:31.590 align:start position:0% just follow and these chain filters can be<00:09:27.009> used<00:09:27.300> for<00:09:28.559> realizing<00:09:29.999> user<00:09:30.999> specific 00:09:31.590 --> 00:09:31.600 align:start position:0% be used for realizing user specific 00:09:31.600 --> 00:09:36.829 align:start position:0% be used for realizing user specific filtering<00:09:32.439> criteria<00:09:32.649> and<00:09:34.199> so<00:09:35.199> these<00:09:35.319> are<00:09:35.499> also 00:09:36.829 --> 00:09:36.839 align:start position:0% filtering criteria and so these are also 00:09:36.839 --> 00:09:39.600 align:start position:0% filtering criteria and so these are also costs<00:09:37.839> use<00:09:38.079> cases<00:09:38.350> of<00:09:38.589> efficient<00:09:39.279> computation 00:09:39.600 --> 00:09:39.610 align:start position:0% costs use cases of efficient computation 00:09:39.610 --> 00:09:42.929 align:start position:0% costs use cases of efficient computation but<00:09:40.199> alas<00:09:41.199> the<00:09:41.470> bloom<00:09:41.980> filter<00:09:42.009> try<00:09:42.490> they<00:09:42.759> are 00:09:42.929 --> 00:09:42.939 align:start position:0% but alas the bloom filter try they are 00:09:42.939 --> 00:09:48.389 align:start position:0% but alas the bloom filter try they are user<00:09:43.389> specific<00:09:45.600> and<00:09:46.600> the<00:09:47.259> other<00:09:47.559> primitive<00:09:48.129> I 00:09:48.389 --> 00:09:48.399 align:start position:0% user specific and the other primitive I 00:09:48.399 --> 00:09:50.809 align:start position:0% user specific and the other primitive I would<00:09:48.699> like<00:09:48.850> to<00:09:49.000> show<00:09:49.209> is<00:09:49.420> called<00:09:49.660> the 00:09:50.809 --> 00:09:50.819 align:start position:0% would like to show is called the 00:09:50.819 --> 00:09:53.910 align:start position:0% would like to show is called the observer<00:09:51.819> chain<00:09:52.269> an<00:09:52.569> observer<00:09:53.259> chain<00:09:53.529> belongs 00:09:53.910 --> 00:09:53.920 align:start position:0% observer chain an observer chain belongs 00:09:53.920 --> 00:09:56.160 align:start position:0% observer chain an observer chain belongs to<00:09:54.189> a<00:09:54.220> single<00:09:54.790> node<00:09:55.000> a<00:09:55.209> single<00:09:55.569> ice<00:09:55.689> light 00:09:56.160 --> 00:09:56.170 align:start position:0% to a single node a single ice light 00:09:56.170 --> 00:09:57.929 align:start position:0% to a single node a single ice light server<00:09:56.439> and<00:09:56.769> it<00:09:56.889> is<00:09:57.009> also<00:09:57.160> validated<00:09:57.790> by<00:09:57.910> a 00:09:57.929 --> 00:09:57.939 align:start position:0% server and it is also validated by a 00:09:57.939 --> 00:10:00.360 align:start position:0% server and it is also validated by a single<00:09:58.389> signature<00:09:58.750> and<00:09:59.110> what<00:09:59.949> an<00:10:00.040> observer 00:10:00.360 --> 00:10:00.370 align:start position:0% single signature and what an observer 00:10:00.370 --> 00:10:03.420 align:start position:0% single signature and what an observer does<00:10:00.759> is<00:10:00.970> that<00:10:01.240> it<00:10:01.949> processes<00:10:02.949> multiple 00:10:03.420 --> 00:10:03.430 align:start position:0% does is that it processes multiple 00:10:03.430 --> 00:10:07.410 align:start position:0% does is that it processes multiple observed<00:10:04.180> chance<00:10:04.629> and<00:10:05.970> create<00:10:06.970> observer 00:10:07.410 --> 00:10:07.420 align:start position:0% observed chance and create observer 00:10:07.420 --> 00:10:11.400 align:start position:0% observed chance and create observer blocks<00:10:07.839> that<00:10:08.410> contain<00:10:08.980> the<00:10:09.509> new<00:10:10.509> latest<00:10:10.959> heads 00:10:11.400 --> 00:10:11.410 align:start position:0% blocks that contain the new latest heads 00:10:11.410 --> 00:10:15.660 align:start position:0% blocks that contain the new latest heads of<00:10:11.649> these<00:10:11.829> chains<00:10:12.189> and<00:10:13.259> it<00:10:14.399> observer<00:10:15.399> chain<00:10:15.550> is 00:10:15.660 --> 00:10:15.670 align:start position:0% of these chains and it observer chain is 00:10:15.670 --> 00:10:17.970 align:start position:0% of these chains and it observer chain is also<00:10:15.970> backed<00:10:16.209> by<00:10:16.420> a<00:10:16.449> security<00:10:16.959> deposit<00:10:17.290> at<00:10:17.889> the 00:10:17.970 --> 00:10:17.980 align:start position:0% also backed by a security deposit at the 00:10:17.980 --> 00:10:21.740 align:start position:0% also backed by a security deposit at the a<00:10:18.160> judge<00:10:18.430> contract<00:10:18.970> and<00:10:19.240> the<00:10:19.870> observer<00:10:20.319> has<00:10:21.129> to 00:10:21.740 --> 00:10:21.750 align:start position:0% a judge contract and the observer has to 00:10:21.750 --> 00:10:25.319 align:start position:0% a judge contract and the observer has to defend<00:10:22.750> the<00:10:23.139> validity<00:10:23.769> and<00:10:24.100> availability<00:10:24.879> of 00:10:25.319 --> 00:10:25.329 align:start position:0% defend the validity and availability of 00:10:25.329 --> 00:10:27.360 align:start position:0% defend the validity and availability of these<00:10:25.870> chains<00:10:26.439> or<00:10:26.709> at<00:10:26.889> least<00:10:27.100> the<00:10:27.189> latest 00:10:27.360 --> 00:10:27.370 align:start position:0% these chains or at least the latest 00:10:27.370 --> 00:10:30.780 align:start position:0% these chains or at least the latest action<00:10:27.639> some<00:10:27.970> of<00:10:28.029> them<00:10:28.290> on<00:10:29.290> the<00:10:29.529> request<00:10:29.889> the 00:10:30.780 --> 00:10:30.790 align:start position:0% action some of them on the request the 00:10:30.790 --> 00:10:34.319 align:start position:0% action some of them on the request the observer<00:10:31.240> chain<00:10:31.509> can<00:10:32.040> follow<00:10:33.059> public<00:10:34.059> chains 00:10:34.319 --> 00:10:34.329 align:start position:0% observer chain can follow public chains 00:10:34.329 --> 00:10:36.809 align:start position:0% observer chain can follow public chains private<00:10:34.809> chains<00:10:35.189> state<00:10:36.189> channels 00:10:36.809 --> 00:10:36.819 align:start position:0% private chains state channels 00:10:36.819 --> 00:10:38.850 align:start position:0% private chains state channels chain<00:10:37.029> theaters<00:10:37.569> and<00:10:37.839> either<00:10:38.050> even<00:10:38.439> other 00:10:38.850 --> 00:10:38.860 align:start position:0% chain theaters and either even other 00:10:38.860 --> 00:10:44.449 align:start position:0% chain theaters and either even other observers<00:10:39.579> chains<00:10:41.519> and<00:10:42.519> now<00:10:42.759> let's<00:10:43.149> see<00:10:43.569> how 00:10:44.449 --> 00:10:44.459 align:start position:0% observers chains and now let's see how 00:10:44.459 --> 00:10:47.970 align:start position:0% observers chains and now let's see how we<00:10:45.459> can<00:10:45.639> realize<00:10:46.269> a<00:10:46.379> filtering<00:10:47.379> and<00:10:47.559> observing 00:10:47.970 --> 00:10:47.980 align:start position:0% we can realize a filtering and observing 00:10:47.980 --> 00:10:49.460 align:start position:0% we can realize a filtering and observing hierarchy<00:10:48.519> with<00:10:48.670> these<00:10:48.850> primitives 00:10:49.460 --> 00:10:49.470 align:start position:0% hierarchy with these primitives 00:10:49.470 --> 00:10:52.889 align:start position:0% hierarchy with these primitives here's<00:10:50.470> an<00:10:50.889> example<00:10:51.370> scenario<00:10:52.149> where<00:10:52.509> there's 00:10:52.889 --> 00:10:52.899 align:start position:0% here's an example scenario where there's 00:10:52.899 --> 00:10:55.530 align:start position:0% here's an example scenario where there's a<00:10:53.050> public<00:10:53.589> chain<00:10:53.800> and<00:10:54.100> two<00:10:54.309> state<00:10:54.670> channels 00:10:55.530 --> 00:10:55.540 align:start position:0% a public chain and two state channels 00:10:55.540 --> 00:11:00.199 align:start position:0% a public chain and two state channels and<00:10:55.630> the<00:10:55.959> user<00:10:56.860> has<00:10:57.370> its<00:10:58.240> own<00:10:58.570> change<00:10:59.440> filters 00:11:00.199 --> 00:11:00.209 align:start position:0% and the user has its own change filters 00:11:00.209 --> 00:11:02.730 align:start position:0% and the user has its own change filters defined<00:11:01.209> for<00:11:01.389> all<00:11:01.420> three<00:11:01.750> of<00:11:01.899> them<00:11:02.170> which<00:11:02.620> I 00:11:02.730 --> 00:11:02.740 align:start position:0% defined for all three of them which I 00:11:02.740 --> 00:11:06.509 align:start position:0% defined for all three of them which I called<00:11:02.980> my<00:11:03.190> event<00:11:03.610> and<00:11:04.800> these<00:11:05.800> chains<00:11:06.310> and 00:11:06.509 --> 00:11:06.519 align:start position:0% called my event and these chains and 00:11:06.519 --> 00:11:09.600 align:start position:0% called my event and these chains and chain<00:11:06.699> filters<00:11:07.180> are<00:11:07.839> processed<00:11:08.740> by<00:11:08.889> hired 00:11:09.600 --> 00:11:09.610 align:start position:0% chain filters are processed by hired 00:11:09.610 --> 00:11:11.850 align:start position:0% chain filters are processed by hired servers<00:11:10.300> servers<00:11:10.899> one<00:11:11.110> two<00:11:11.320> and<00:11:11.589> three<00:11:11.829> in 00:11:11.850 --> 00:11:11.860 align:start position:0% servers servers one two and three in 00:11:11.860 --> 00:11:15.300 align:start position:0% servers servers one two and three in this<00:11:12.130> case<00:11:12.899> who<00:11:13.899> gives<00:11:14.259> certificates<00:11:14.709> about 00:11:15.300 --> 00:11:15.310 align:start position:0% this case who gives certificates about 00:11:15.310 --> 00:11:17.519 align:start position:0% this case who gives certificates about the<00:11:16.180> validity<00:11:16.389> of<00:11:16.660> the<00:11:16.839> input<00:11:17.079> chains<00:11:17.319> and 00:11:17.519 --> 00:11:17.529 align:start position:0% the validity of the input chains and 00:11:17.529 --> 00:11:21.240 align:start position:0% the validity of the input chains and also<00:11:17.889> the<00:11:18.220> results<00:11:19.209> of<00:11:19.360> the<00:11:19.540> users<00:11:20.350> chain 00:11:21.240 --> 00:11:21.250 align:start position:0% also the results of the users chain 00:11:21.250 --> 00:11:25.910 align:start position:0% also the results of the users chain filters<00:11:23.100> may<00:11:24.100> be<00:11:24.160> in<00:11:24.459> some<00:11:24.670> case<00:11:24.910> it<00:11:24.940> would<00:11:25.630> be 00:11:25.910 --> 00:11:25.920 align:start position:0% filters may be in some case it would be 00:11:25.920 --> 00:11:28.769 align:start position:0% filters may be in some case it would be enough<00:11:26.920> to<00:11:26.949> just<00:11:27.550> hire<00:11:27.759> a<00:11:27.790> few<00:11:28.120> servers<00:11:28.389> and 00:11:28.769 --> 00:11:28.779 align:start position:0% enough to just hire a few servers and 00:11:28.779 --> 00:11:30.449 align:start position:0% enough to just hire a few servers and collect<00:11:29.079> the<00:11:29.170> results<00:11:29.350> but<00:11:29.769> it<00:11:29.889> is<00:11:30.040> possible 00:11:30.449 --> 00:11:30.459 align:start position:0% collect the results but it is possible 00:11:30.459 --> 00:11:32.189 align:start position:0% collect the results but it is possible that<00:11:30.490> we<00:11:30.790> have<00:11:30.819> such<00:11:31.120> a<00:11:31.149> huge<00:11:31.449> hire<00:11:31.720> he<00:11:32.079> had 00:11:32.189 --> 00:11:32.199 align:start position:0% that we have such a huge hire he had 00:11:32.199 --> 00:11:34.530 align:start position:0% that we have such a huge hire he had been<00:11:32.380> driven<00:11:32.589> to<00:11:32.910> observe<00:11:33.910> so<00:11:34.060> many<00:11:34.269> chains 00:11:34.530 --> 00:11:34.540 align:start position:0% been driven to observe so many chains 00:11:34.540 --> 00:11:37.199 align:start position:0% been driven to observe so many chains that<00:11:34.779> we<00:11:35.500> might<00:11:35.709> need<00:11:35.889> additional<00:11:36.279> layers<00:11:37.000> of 00:11:37.199 --> 00:11:37.209 align:start position:0% that we might need additional layers of 00:11:37.209 --> 00:11:39.389 align:start position:0% that we might need additional layers of servers<00:11:37.630> in<00:11:37.899> this<00:11:38.319> case<00:11:38.560> they<00:11:38.829> are<00:11:38.860> servers 00:11:39.389 --> 00:11:39.399 align:start position:0% servers in this case they are servers 00:11:39.399 --> 00:11:41.610 align:start position:0% servers in this case they are servers four<00:11:39.790> and<00:11:39.910> five<00:11:40.120> who<00:11:40.660> are<00:11:40.690> observing<00:11:41.470> the 00:11:41.610 --> 00:11:41.620 align:start position:0% four and five who are observing the 00:11:41.620 --> 00:11:43.319 align:start position:0% four and five who are observing the observer<00:11:41.949> chains<00:11:42.339> of<00:11:42.519> service<00:11:42.880> one<00:11:43.060> two<00:11:43.209> and 00:11:43.319 --> 00:11:43.329 align:start position:0% observer chains of service one two and 00:11:43.329 --> 00:11:44.910 align:start position:0% observer chains of service one two and three<00:11:43.569> and<00:11:43.750> run<00:11:43.959> their<00:11:44.110> own<00:11:44.170> chain<00:11:44.500> theater 00:11:44.910 --> 00:11:44.920 align:start position:0% three and run their own chain theater 00:11:44.920 --> 00:11:47.069 align:start position:0% three and run their own chain theater could<00:11:45.160> collect<00:11:45.550> events<00:11:45.970> that<00:11:46.420> could<00:11:46.600> filter 00:11:47.069 --> 00:11:47.079 align:start position:0% could collect events that could filter 00:11:47.079 --> 00:11:48.930 align:start position:0% could collect events that could filter and<00:11:47.440> collect<00:11:47.980> all<00:11:48.100> the<00:11:48.250> interesting<00:11:48.819> events 00:11:48.930 --> 00:11:48.940 align:start position:0% and collect all the interesting events 00:11:48.940 --> 00:11:51.540 align:start position:0% and collect all the interesting events for<00:11:49.329> our<00:11:49.569> client<00:11:50.019> so<00:11:50.740> they<00:11:50.889> find<00:11:51.100> can<00:11:51.339> very 00:11:51.540 --> 00:11:51.550 align:start position:0% for our client so they find can very 00:11:51.550 --> 00:11:53.610 align:start position:0% for our client so they find can very conveniently<00:11:51.790> just<00:11:52.389> contact<00:11:53.050> the<00:11:53.199> last<00:11:53.410> layer 00:11:53.610 --> 00:11:53.620 align:start position:0% conveniently just contact the last layer 00:11:53.620 --> 00:11:57.749 align:start position:0% conveniently just contact the last layer of<00:11:54.180> helping<00:11:55.180> servers<00:11:55.630> and<00:11:56.100> receive<00:11:57.100> just<00:11:57.639> the 00:11:57.749 --> 00:11:57.759 align:start position:0% of helping servers and receive just the 00:11:57.759 --> 00:12:02.430 align:start position:0% of helping servers and receive just the interesting<00:11:58.420> results<00:12:00.510> of<00:12:01.510> course<00:12:01.839> we<00:12:02.019> need 00:12:02.430 --> 00:12:02.440 align:start position:0% interesting results of course we need 00:12:02.440 --> 00:12:05.939 align:start position:0% interesting results of course we need some<00:12:02.470> redundancy<00:12:03.459> to<00:12:03.940> make<00:12:04.449> sure<00:12:04.660> this<00:12:04.949> system 00:12:05.939 --> 00:12:05.949 align:start position:0% some redundancy to make sure this system 00:12:05.949 --> 00:12:07.019 align:start position:0% some redundancy to make sure this system works<00:12:06.160> correctly 00:12:07.019 --> 00:12:07.029 align:start position:0% works correctly 00:12:07.029 --> 00:12:09.540 align:start position:0% works correctly so<00:12:07.480> if<00:12:07.660> we<00:12:07.779> have<00:12:07.990> multiple<00:12:08.470> paths<00:12:08.740> leading<00:12:09.250> to 00:12:09.540 --> 00:12:09.550 align:start position:0% so if we have multiple paths leading to 00:12:09.550 --> 00:12:11.790 align:start position:0% so if we have multiple paths leading to every<00:12:09.910> interesting<00:12:10.389> chain<00:12:10.899> or<00:12:11.139> chain<00:12:11.170> filter 00:12:11.790 --> 00:12:11.800 align:start position:0% every interesting chain or chain filter 00:12:11.800 --> 00:12:15.900 align:start position:0% every interesting chain or chain filter then<00:12:12.510> the<00:12:13.510> client<00:12:14.019> can<00:12:14.380> always<00:12:15.310> detect<00:12:15.579> if<00:12:15.760> it 00:12:15.900 --> 00:12:15.910 align:start position:0% then the client can always detect if it 00:12:15.910 --> 00:12:17.400 align:start position:0% then the client can always detect if it receives<00:12:16.269> different<00:12:16.480> results<00:12:17.199> from 00:12:17.400 --> 00:12:17.410 align:start position:0% receives different results from 00:12:17.410 --> 00:12:20.819 align:start position:0% receives different results from different<00:12:17.860> directions<00:12:18.699> and<00:12:18.970> then<00:12:19.540> it<00:12:20.410> can<00:12:20.589> try 00:12:20.819 --> 00:12:20.829 align:start position:0% different directions and then it can try 00:12:20.829 --> 00:12:24.629 align:start position:0% different directions and then it can try to<00:12:20.889> investigate<00:12:21.790> the<00:12:22.779> the<00:12:23.589> observer<00:12:24.310> chains 00:12:24.629 --> 00:12:24.639 align:start position:0% to investigate the the observer chains 00:12:24.639 --> 00:12:26.819 align:start position:0% to investigate the the observer chains and<00:12:24.940> the<00:12:25.120> three<00:12:25.300> filters<00:12:25.510> of<00:12:25.870> the<00:12:26.290> entire 00:12:26.819 --> 00:12:26.829 align:start position:0% and the three filters of the entire 00:12:26.829 --> 00:12:29.009 align:start position:0% and the three filters of the entire service<00:12:27.190> or<00:12:27.579> maybe<00:12:27.760> raise<00:12:28.329> an<00:12:28.480> alarm<00:12:28.720> and 00:12:29.009 --> 00:12:29.019 align:start position:0% service or maybe raise an alarm and 00:12:29.019 --> 00:12:32.030 align:start position:0% service or maybe raise an alarm and notify<00:12:29.740> about<00:12:29.860> other<00:12:30.339> clients<00:12:30.610> about<00:12:31.089> a 00:12:32.030 --> 00:12:32.040 align:start position:0% notify about other clients about a 00:12:32.040 --> 00:12:37.230 align:start position:0% notify about other clients about a suspected<00:12:33.040> fraud<00:12:33.930> and<00:12:34.980> eventually<00:12:35.980> if<00:12:36.240> there 00:12:37.230 --> 00:12:37.240 align:start position:0% suspected fraud and eventually if there 00:12:37.240 --> 00:12:38.610 align:start position:0% suspected fraud and eventually if there seems<00:12:37.569> to<00:12:37.660> be<00:12:37.720> a<00:12:37.839> fraud<00:12:37.990> and<00:12:38.260> start<00:12:38.470> an 00:12:38.610 --> 00:12:38.620 align:start position:0% seems to be a fraud and start an 00:12:38.620 --> 00:12:40.650 align:start position:0% seems to be a fraud and start an interactive<00:12:39.069> validation<00:12:39.610> process<00:12:39.970> to<00:12:40.209> try<00:12:40.630> to 00:12:40.650 --> 00:12:40.660 align:start position:0% interactive validation process to try to 00:12:40.660 --> 00:12:45.689 align:start position:0% interactive validation process to try to prove<00:12:40.959> it<00:12:43.410> all<00:12:44.410> of<00:12:44.649> this<00:12:44.769> is<00:12:44.829> of<00:12:45.100> course<00:12:45.279> quite 00:12:45.689 --> 00:12:45.699 align:start position:0% prove it all of this is of course quite 00:12:45.699 --> 00:12:47.879 align:start position:0% prove it all of this is of course quite far<00:12:46.000> from<00:12:46.029> the<00:12:46.269> original<00:12:46.959> idea<00:12:47.500> of<00:12:47.560> the<00:12:47.740> right 00:12:47.879 --> 00:12:47.889 align:start position:0% far from the original idea of the right 00:12:47.889 --> 00:12:51.269 align:start position:0% far from the original idea of the right client<00:12:48.339> but<00:12:48.760> I<00:12:48.790> believe<00:12:49.300> it<00:12:49.569> still<00:12:50.279> fits 00:12:51.269 --> 00:12:51.279 align:start position:0% client but I believe it still fits 00:12:51.279 --> 00:12:55.189 align:start position:0% client but I believe it still fits pretty<00:12:51.639> well<00:12:51.790> with<00:12:52.779> the<00:12:53.339> philosophy<00:12:54.339> of<00:12:54.519> what 00:12:55.189 --> 00:12:55.199 align:start position:0% pretty well with the philosophy of what 00:12:55.199 --> 00:12:58.550 align:start position:0% pretty well with the philosophy of what the<00:12:56.199> original<00:12:56.740> light<00:12:57.310> duty<00:12:57.519> call<00:12:57.759> is<00:12:57.970> based<00:12:58.269> on 00:12:58.550 --> 00:12:58.560 align:start position:0% the original light duty call is based on 00:12:58.560 --> 00:13:02.939 align:start position:0% the original light duty call is based on because<00:12:59.730> the<00:13:00.730> idea<00:13:01.060> is<00:13:01.240> that<00:13:01.389> in<00:13:01.569> this<00:13:01.949> massive 00:13:02.939 --> 00:13:02.949 align:start position:0% because the idea is that in this massive 00:13:02.949 --> 00:13:05.429 align:start position:0% because the idea is that in this massive computer<00:13:03.459> ecosystem<00:13:04.420> there<00:13:04.899> are<00:13:05.019> nodes<00:13:05.199> with 00:13:05.429 --> 00:13:05.439 align:start position:0% computer ecosystem there are nodes with 00:13:05.439 --> 00:13:07.590 align:start position:0% computer ecosystem there are nodes with very<00:13:05.800> different<00:13:05.980> capabilities<00:13:06.790> and<00:13:07.000> a<00:13:07.240> small 00:13:07.590 --> 00:13:07.600 align:start position:0% very different capabilities and a small 00:13:07.600 --> 00:13:09.840 align:start position:0% very different capabilities and a small and<00:13:07.810> it<00:13:07.990> is<00:13:08.140> we<00:13:08.320> always<00:13:08.530> try<00:13:09.310> or<00:13:09.460> have<00:13:09.640> from 00:13:09.840 --> 00:13:09.850 align:start position:0% and it is we always try or have from 00:13:09.850 --> 00:13:13.680 align:start position:0% and it is we always try or have from bigger<00:13:10.330> and<00:13:10.510> it<00:13:10.660> is<00:13:10.840> and<00:13:11.700> what<00:13:12.700> we<00:13:12.940> can<00:13:12.970> do<00:13:13.330> to 00:13:13.680 --> 00:13:13.690 align:start position:0% bigger and it is and what we can do to 00:13:13.690 --> 00:13:16.230 align:start position:0% bigger and it is and what we can do to avoid<00:13:13.930> the<00:13:14.440> concentration<00:13:15.250> of<00:13:15.370> power<00:13:15.580> is<00:13:15.910> that 00:13:16.230 --> 00:13:16.240 align:start position:0% avoid the concentration of power is that 00:13:16.240 --> 00:13:20.400 align:start position:0% avoid the concentration of power is that we<00:13:16.690> can<00:13:16.900> create<00:13:17.260> a<00:13:18.930> standardized<00:13:19.930> protocols 00:13:20.400 --> 00:13:20.410 align:start position:0% we can create a standardized protocols 00:13:20.410 --> 00:13:22.110 align:start position:0% we can create a standardized protocols that<00:13:20.620> make<00:13:20.890> the<00:13:21.100> bigger<00:13:21.370> happier<00:13:21.760> and<00:13:21.850> it<00:13:22.000> is 00:13:22.110 --> 00:13:22.120 align:start position:0% that make the bigger happier and it is 00:13:22.120 --> 00:13:24.810 align:start position:0% that make the bigger happier and it is interchangeable<00:13:22.450> and<00:13:23.200> therefore<00:13:23.650> create<00:13:24.640> a 00:13:24.810 --> 00:13:24.820 align:start position:0% interchangeable and therefore create a 00:13:24.820 --> 00:13:26.940 align:start position:0% interchangeable and therefore create a liquid<00:13:25.660> market<00:13:26.020> of<00:13:26.140> services<00:13:26.710> so<00:13:26.920> that 00:13:26.940 --> 00:13:26.950 align:start position:0% liquid market of services so that 00:13:26.950 --> 00:13:30.240 align:start position:0% liquid market of services so that whenever<00:13:27.910> someone<00:13:28.420> wants<00:13:29.230> to<00:13:29.260> stop<00:13:29.920> providing 00:13:30.240 --> 00:13:30.250 align:start position:0% whenever someone wants to stop providing 00:13:30.250 --> 00:13:32.640 align:start position:0% whenever someone wants to stop providing services<00:13:30.880> or<00:13:31.060> raise<00:13:31.240> the<00:13:31.630> price<00:13:32.170> is<00:13:32.380> very<00:13:32.440> high 00:13:32.640 --> 00:13:32.650 align:start position:0% services or raise the price is very high 00:13:32.650 --> 00:13:35.400 align:start position:0% services or raise the price is very high than<00:13:33.400> other<00:13:33.850> servers<00:13:34.570> can<00:13:34.840> just<00:13:35.080> take<00:13:35.380> over 00:13:35.400 --> 00:13:35.410 align:start position:0% than other servers can just take over 00:13:35.410 --> 00:13:39.290 align:start position:0% than other servers can just take over and<00:13:35.710> no<00:13:36.550> one<00:13:36.700> can<00:13:36.910> stop<00:13:37.360> them<00:13:37.510> from<00:13:37.660> doing<00:13:37.870> so 00:13:39.290 --> 00:13:39.300 align:start position:0% and no one can stop them from doing so 00:13:39.300 --> 00:13:44.160 align:start position:0% and no one can stop them from doing so so<00:13:40.300> we<00:13:40.450> can<00:13:40.480> ensure<00:13:40.720> a<00:13:42.750> continuous<00:13:43.750> service 00:13:44.160 --> 00:13:44.170 align:start position:0% so we can ensure a continuous service 00:13:44.170 --> 00:13:48.450 align:start position:0% so we can ensure a continuous service with<00:13:44.550> reasonable<00:13:45.550> prices<00:13:46.060> and<00:13:46.290> and<00:13:47.290> also<00:13:48.040> we 00:13:48.450 --> 00:13:48.460 align:start position:0% with reasonable prices and and also we 00:13:48.460 --> 00:13:52.610 align:start position:0% with reasonable prices and and also we can<00:13:48.640> still<00:13:49.000> provide<00:13:49.360> security<00:13:49.810> not<00:13:50.140> with<00:13:50.350> the 00:13:52.610 --> 00:13:52.620 align:start position:0% 00:13:52.620 --> 00:13:54.710 align:start position:0% Mercure<00:13:53.620> proof 00:13:54.710 --> 00:13:54.720 align:start position:0% Mercure proof 00:13:54.720 --> 00:13:57.270 align:start position:0% Mercure proof mirco<00:13:55.720> proofs<00:13:55.930> are<00:13:56.110> in<00:13:56.380> the<00:13:56.500> classical<00:13:56.950> I<00:13:57.040> try 00:13:57.270 --> 00:13:57.280 align:start position:0% mirco proofs are in the classical I try 00:13:57.280 --> 00:14:01.590 align:start position:0% mirco proofs are in the classical I try and<00:13:57.430> but<00:13:57.670> we<00:13:58.630> can<00:13:58.840> still<00:13:59.940> increase<00:14:00.940> the<00:14:01.180> cost 00:14:01.590 --> 00:14:01.600 align:start position:0% and but we can still increase the cost 00:14:01.600 --> 00:14:03.720 align:start position:0% and but we can still increase the cost of<00:14:01.720> an<00:14:01.870> attempted<00:14:02.290> fraud<00:14:02.530> by<00:14:02.800> using<00:14:03.250> security 00:14:03.720 --> 00:14:03.730 align:start position:0% of an attempted fraud by using security 00:14:03.730 --> 00:14:06.210 align:start position:0% of an attempted fraud by using security deposits<00:14:04.300> and<00:14:04.480> also<00:14:04.930> reduce<00:14:05.560> the<00:14:05.590> risk<00:14:05.770> of<00:14:06.070> a 00:14:06.210 --> 00:14:06.220 align:start position:0% deposits and also reduce the risk of a 00:14:06.220 --> 00:14:08.520 align:start position:0% deposits and also reduce the risk of a successful<00:14:06.700> fraud<00:14:07.180> by<00:14:07.420> using<00:14:07.780> multi-purpose 00:14:08.520 --> 00:14:08.530 align:start position:0% successful fraud by using multi-purpose 00:14:08.530 --> 00:14:11.160 align:start position:0% successful fraud by using multi-purpose and<00:14:08.760> detecting<00:14:09.760> any<00:14:09.910> attempted<00:14:10.570> fraud<00:14:10.750> right 00:14:11.160 --> 00:14:11.170 align:start position:0% and detecting any attempted fraud right 00:14:11.170 --> 00:14:18.570 align:start position:0% and detecting any attempted fraud right away<00:14:14.490> of<00:14:15.490> course<00:14:15.850> the<00:14:16.560> there<00:14:17.560> are<00:14:17.710> still<00:14:18.160> some 00:14:18.570 --> 00:14:18.580 align:start position:0% away of course the there are still some 00:14:18.580 --> 00:14:20.460 align:start position:0% away of course the there are still some details<00:14:19.060> that<00:14:19.150> are<00:14:19.420> not<00:14:19.570> worked<00:14:19.810> out<00:14:20.020> and 00:14:20.460 --> 00:14:20.470 align:start position:0% details that are not worked out and 00:14:20.470 --> 00:14:24.630 align:start position:0% details that are not worked out and right<00:14:20.980> now<00:14:21.190> our<00:14:22.590> main<00:14:23.590> development<00:14:24.160> priority 00:14:24.630 --> 00:14:24.640 align:start position:0% right now our main development priority 00:14:24.640 --> 00:14:27.300 align:start position:0% right now our main development priority is<00:14:24.970> still<00:14:25.300> the<00:14:25.570> making<00:14:26.380> the<00:14:26.530> classical<00:14:27.040> light 00:14:27.300 --> 00:14:27.310 align:start position:0% is still the making the classical light 00:14:27.310 --> 00:14:30.990 align:start position:0% is still the making the classical light client<00:14:28.110> reliable<00:14:29.110> and<00:14:29.230> usable<00:14:29.770> but<00:14:30.550> when 00:14:30.990 --> 00:14:31.000 align:start position:0% client reliable and usable but when 00:14:31.000 --> 00:14:32.820 align:start position:0% client reliable and usable but when setting<00:14:31.330> the<00:14:31.360> directions<00:14:32.020> of<00:14:32.290> a<00:14:32.680> new 00:14:32.820 --> 00:14:32.830 align:start position:0% setting the directions of a new 00:14:32.830 --> 00:14:34.740 align:start position:0% setting the directions of a new development<00:14:33.460> it<00:14:33.610> is<00:14:33.730> always<00:14:34.030> important<00:14:34.690> to 00:14:34.740 --> 00:14:34.750 align:start position:0% development it is always important to 00:14:34.750 --> 00:14:39.510 align:start position:0% development it is always important to keep<00:14:34.870> keep<00:14:36.390> the<00:14:37.470> future<00:14:38.470> challenges<00:14:38.680> in<00:14:39.220> mind 00:14:39.510 --> 00:14:39.520 align:start position:0% keep keep the future challenges in mind 00:14:39.520 --> 00:14:41.430 align:start position:0% keep keep the future challenges in mind and<00:14:39.850> the<00:14:40.210> long-term<00:14:40.360> goals<00:14:40.810> and<00:14:41.050> I<00:14:41.140> think<00:14:41.350> the 00:14:41.430 --> 00:14:41.440 align:start position:0% and the long-term goals and I think the 00:14:41.440 --> 00:14:44.370 align:start position:0% and the long-term goals and I think the long-term<00:14:41.740> goal<00:14:42.010> is<00:14:42.220> a<00:14:42.900> massively<00:14:43.900> scalable 00:14:44.370 --> 00:14:44.380 align:start position:0% long-term goal is a massively scalable 00:14:44.380 --> 00:14:46.680 align:start position:0% long-term goal is a massively scalable high<00:14:44.950> performance<00:14:45.520> per<00:14:45.640> computer<00:14:46.000> that<00:14:46.360> even 00:14:46.680 --> 00:14:46.690 align:start position:0% high performance per computer that even 00:14:46.690 --> 00:14:48.750 align:start position:0% high performance per computer that even small<00:14:47.050> embedded<00:14:47.650> and<00:14:47.800> mobile<00:14:48.070> devices<00:14:48.370> can 00:14:48.750 --> 00:14:48.760 align:start position:0% small embedded and mobile devices can 00:14:48.760 --> 00:14:55.290 align:start position:0% small embedded and mobile devices can safely<00:14:49.720> access<00:14:51.240> and<00:14:52.920> I<00:14:53.920> believe<00:14:54.820> that<00:14:55.000> in<00:14:55.150> this 00:14:55.290 --> 00:14:55.300 align:start position:0% safely access and I believe that in this 00:14:55.300 --> 00:14:58.110 align:start position:0% safely access and I believe that in this massive<00:14:56.080> in<00:14:56.950> addition<00:14:57.430> to<00:14:57.520> the<00:14:57.610> massive<00:14:57.910> chain 00:14:58.110 --> 00:14:58.120 align:start position:0% massive in addition to the massive chain 00:14:58.120 --> 00:15:00.630 align:start position:0% massive in addition to the massive chain hierarchy<00:14:58.720> that<00:14:59.010> provides<00:15:00.010> the<00:15:00.190> global 00:15:00.630 --> 00:15:00.640 align:start position:0% hierarchy that provides the global 00:15:00.640 --> 00:15:06.290 align:start position:0% hierarchy that provides the global consensus<00:15:01.890> the<00:15:03.210> the<00:15:04.210> client<00:15:05.200> specific 00:15:06.290 --> 00:15:06.300 align:start position:0% consensus the the client specific 00:15:06.300 --> 00:15:08.750 align:start position:0% consensus the the client specific observing<00:15:07.300> and<00:15:07.540> filtering<00:15:07.990> higher<00:15:08.260> he<00:15:08.680> is 00:15:08.750 --> 00:15:08.760 align:start position:0% observing and filtering higher he is 00:15:08.760 --> 00:15:11.970 align:start position:0% observing and filtering higher he is belonging<00:15:09.760> to<00:15:09.880> these<00:15:10.420> unique<00:15:11.050> perspectives 00:15:11.970 --> 00:15:11.980 align:start position:0% belonging to these unique perspectives 00:15:11.980 --> 00:15:15.150 align:start position:0% belonging to these unique perspectives of<00:15:12.100> some<00:15:12.730> applications<00:15:13.630> will<00:15:14.230> be<00:15:14.260> equally 00:15:15.150 --> 00:15:15.160 align:start position:0% of some applications will be equally 00:15:15.160 --> 00:15:19.200 align:start position:0% of some applications will be equally important<00:15:15.580> in<00:15:15.700> this<00:15:15.790> ecosystem<00:15:17.460> and<00:15:18.460> I<00:15:18.880> hope 00:15:19.200 --> 00:15:19.210 align:start position:0% important in this ecosystem and I hope 00:15:19.210 --> 00:15:21.300 align:start position:0% important in this ecosystem and I hope you<00:15:19.390> found<00:15:19.690> my<00:15:19.960> own<00:15:20.260> unique<00:15:20.710> perspective<00:15:20.980> on 00:15:21.300 --> 00:15:21.310 align:start position:0% you found my own unique perspective on 00:15:21.310 --> 00:15:21.960 align:start position:0% you found my own unique perspective on the<00:15:21.490> future 00:15:21.960 --> 00:15:21.970 align:start position:0% the future 00:15:21.970 --> 00:15:23.579 align:start position:0% the future deuterium<00:15:22.239> interesting<00:15:22.929> and<00:15:23.139> thank<00:15:23.349> you<00:15:23.409> for 00:15:23.579 --> 00:15:23.589 align:start position:0% deuterium interesting and thank you for 00:15:23.589 --> 00:15:30.860 align:start position:0% deuterium interesting and thank you for your<00:15:23.739> attention 00:15:30.860 --> 00:15:30.870 align:start position:0% 00:15:30.870 --> 00:15:32.210 align:start position:0% you 00:15:32.210 --> 00:15:32.220 align:start position:0% you 00:15:32.220 --> 00:15:39.809 align:start position:0% you [Music]