WEBVTT Kind: captions Language: en 00:00:00.550 --> 00:00:12.390 align:start position:0% [Music] 00:00:12.390 --> 00:00:12.400 align:start position:0% 00:00:12.400 --> 00:00:15.350 align:start position:0% okay<00:00:12.679> hi<00:00:13.160> my<00:00:13.280> name<00:00:13.440> is<00:00:13.559> Peter<00:00:14.000> I<00:00:14.120> work<00:00:14.400> at<00:00:14.599> imop 00:00:15.350 --> 00:00:15.360 align:start position:0% okay hi my name is Peter I work at imop 00:00:15.360 --> 00:00:17.470 align:start position:0% okay hi my name is Peter I work at imop in<00:00:15.880> waro 00:00:17.470 --> 00:00:17.480 align:start position:0% in waro 00:00:17.480 --> 00:00:21.150 align:start position:0% in waro and<00:00:18.480> we<00:00:19.160> met<00:00:19.480> with<00:00:19.680> gab<00:00:20.279> approximately<00:00:20.960> in 00:00:21.150 --> 00:00:21.160 align:start position:0% and we met with gab approximately in 00:00:21.160 --> 00:00:23.630 align:start position:0% and we met with gab approximately in February<00:00:21.760> I<00:00:21.880> suppose<00:00:22.680> and<00:00:22.800> we<00:00:22.960> had<00:00:23.199> a<00:00:23.359> short 00:00:23.630 --> 00:00:23.640 align:start position:0% February I suppose and we had a short 00:00:23.640 --> 00:00:25.870 align:start position:0% February I suppose and we had a short chat<00:00:24.439> uh<00:00:24.640> regarding<00:00:25.240> our<00:00:25.480> future 00:00:25.870 --> 00:00:25.880 align:start position:0% chat uh regarding our future 00:00:25.880 --> 00:00:28.790 align:start position:0% chat uh regarding our future collaboration<00:00:26.599> and<00:00:27.199> possibilities<00:00:27.760> of<00:00:28.480> us 00:00:28.790 --> 00:00:28.800 align:start position:0% collaboration and possibilities of us 00:00:28.800 --> 00:00:30.669 align:start position:0% collaboration and possibilities of us helping<00:00:29.720> you 00:00:30.669 --> 00:00:30.679 align:start position:0% helping you 00:00:30.679 --> 00:00:34.110 align:start position:0% helping you with<00:00:31.039> some<00:00:31.439> parts<00:00:31.759> of<00:00:32.000> the<00:00:32.200> etherum<00:00:33.120> project 00:00:34.110 --> 00:00:34.120 align:start position:0% with some parts of the etherum project 00:00:34.120 --> 00:00:36.470 align:start position:0% with some parts of the etherum project uh<00:00:34.920> it<00:00:35.079> happens<00:00:35.399> that<00:00:35.559> I<00:00:35.680> work<00:00:35.879> at<00:00:36.000> a<00:00:36.160> company 00:00:36.470 --> 00:00:36.480 align:start position:0% uh it happens that I work at a company 00:00:36.480 --> 00:00:39.110 align:start position:0% uh it happens that I work at a company that<00:00:36.640> specializes<00:00:37.120> in<00:00:37.800> compilers<00:00:38.800> it 00:00:39.110 --> 00:00:39.120 align:start position:0% that specializes in compilers it 00:00:39.120 --> 00:00:42.389 align:start position:0% that specializes in compilers it specialized<00:00:40.079> right<00:00:40.399> then<00:00:41.399> and<00:00:41.600> it<00:00:41.840> resulted 00:00:42.389 --> 00:00:42.399 align:start position:0% specialized right then and it resulted 00:00:42.399 --> 00:00:46.029 align:start position:0% specialized right then and it resulted in<00:00:43.239> lvm<00:00:43.879> implementation<00:00:44.680> of<00:00:44.840> evm<00:00:45.520> that<00:00:45.719> P<00:00:45.960> is 00:00:46.029 --> 00:00:46.039 align:start position:0% in lvm implementation of evm that P is 00:00:46.039 --> 00:00:49.029 align:start position:0% in lvm implementation of evm that P is going<00:00:46.239> to<00:00:46.480> describe<00:00:47.480> but<00:00:47.800> at<00:00:47.960> the<00:00:48.079> same<00:00:48.360> time 00:00:49.029 --> 00:00:49.039 align:start position:0% going to describe but at the same time 00:00:49.039 --> 00:00:52.310 align:start position:0% going to describe but at the same time we<00:00:49.320> had<00:00:49.680> a<00:00:50.440> little 00:00:52.310 --> 00:00:52.320 align:start position:0% we had a little 00:00:52.320 --> 00:00:55.869 align:start position:0% we had a little misunderstanding<00:00:53.320> uh<00:00:53.480> Among<00:00:53.760> Us<00:00:54.680> and<00:00:54.879> when<00:00:55.480> G 00:00:55.869 --> 00:00:55.879 align:start position:0% misunderstanding uh Among Us and when G 00:00:55.879 --> 00:01:00.910 align:start position:0% misunderstanding uh Among Us and when G described<00:00:56.480> the<00:00:56.640> eum<00:00:57.559> our<00:00:57.920> CEO<00:00:58.920> remembered<00:01:00.359> two 00:01:00.910 --> 00:01:00.920 align:start position:0% described the eum our CEO remembered two 00:01:00.920 --> 00:01:04.270 align:start position:0% described the eum our CEO remembered two phrases<00:01:01.920> during<00:01:02.399> completeness<00:01:02.920> and<00:01:03.760> virtual 00:01:04.270 --> 00:01:04.280 align:start position:0% phrases during completeness and virtual 00:01:04.280 --> 00:01:08.070 align:start position:0% phrases during completeness and virtual machine<00:01:05.280> so<00:01:06.240> after<00:01:07.240> I<00:01:07.320> don't<00:01:07.479> know<00:01:07.759> half<00:01:07.960> an 00:01:08.070 --> 00:01:08.080 align:start position:0% machine so after I don't know half an 00:01:08.080 --> 00:01:09.990 align:start position:0% machine so after I don't know half an hour<00:01:08.280> he<00:01:08.400> thought<00:01:08.799> well<00:01:09.200> great<00:01:09.560> that<00:01:09.680> may<00:01:09.840> be<00:01:09.920> a 00:01:09.990 --> 00:01:10.000 align:start position:0% hour he thought well great that may be a 00:01:10.000 --> 00:01:12.149 align:start position:0% hour he thought well great that may be a super<00:01:10.280> computer<00:01:11.000> that's<00:01:11.200> something<00:01:11.520> that<00:01:11.680> can 00:01:12.149 --> 00:01:12.159 align:start position:0% super computer that's something that can 00:01:12.159 --> 00:01:15.469 align:start position:0% super computer that's something that can distribute<00:01:12.640> computation<00:01:13.720> and<00:01:14.720> I<00:01:14.880> don't<00:01:15.000> know 00:01:15.469 --> 00:01:15.479 align:start position:0% distribute computation and I don't know 00:01:15.479 --> 00:01:18.870 align:start position:0% distribute computation and I don't know locally<00:01:16.280> run<00:01:16.560> it<00:01:17.280> so<00:01:17.840> no<00:01:18.040> not<00:01:18.280> exactly<00:01:18.640> it's 00:01:18.870 --> 00:01:18.880 align:start position:0% locally run it so no not exactly it's 00:01:18.880 --> 00:01:21.190 align:start position:0% locally run it so no not exactly it's more<00:01:19.080> about<00:01:19.280> the<00:01:19.439> consensus<00:01:20.040> and<00:01:20.759> keeping<00:01:21.040> a 00:01:21.190 --> 00:01:21.200 align:start position:0% more about the consensus and keeping a 00:01:21.200 --> 00:01:23.670 align:start position:0% more about the consensus and keeping a solid<00:01:22.040> compact<00:01:22.400> state<00:01:23.159> not<00:01:23.360> about 00:01:23.670 --> 00:01:23.680 align:start position:0% solid compact state not about 00:01:23.680 --> 00:01:24.749 align:start position:0% solid compact state not about Distributing 00:01:24.749 --> 00:01:24.759 align:start position:0% Distributing 00:01:24.759 --> 00:01:33.830 align:start position:0% Distributing computations<00:01:25.759> so<00:01:26.439> H<00:01:27.439> okay 00:01:33.830 --> 00:01:33.840 align:start position:0% 00:01:33.840 --> 00:01:35.910 align:start position:0% so<00:01:34.040> what<00:01:34.200> can<00:01:34.320> we<00:01:34.479> do<00:01:35.119> maybe<00:01:35.320> we<00:01:35.439> can<00:01:35.640> provide 00:01:35.910 --> 00:01:35.920 align:start position:0% so what can we do maybe we can provide 00:01:35.920 --> 00:01:37.870 align:start position:0% so what can we do maybe we can provide something<00:01:36.240> like<00:01:36.439> this<00:01:37.200> and<00:01:37.399> he<00:01:37.520> called<00:01:37.680> it 00:01:37.870 --> 00:01:37.880 align:start position:0% something like this and he called it 00:01:37.880 --> 00:01:42.789 align:start position:0% something like this and he called it Goen<00:01:38.560> from<00:01:39.479> Goen<00:01:39.799> 14<00:01:40.720> it<00:01:40.840> is<00:01:41.040> a<00:01:42.040> story<00:01:42.439> written 00:01:42.789 --> 00:01:42.799 align:start position:0% Goen from Goen 14 it is a story written 00:01:42.799 --> 00:01:49.350 align:start position:0% Goen from Goen 14 it is a story written by<00:01:43.240> stain<00:01:43.880> L<00:01:44.759> it's<00:01:44.920> a<00:01:45.399> machine<00:01:45.880> that<00:01:46.719> got<00:01:46.960> some 00:01:49.350 --> 00:01:49.360 align:start position:0% by stain L it's a machine that got some 00:01:49.360 --> 00:01:53.270 align:start position:0% by stain L it's a machine that got some so<00:01:50.360> large<00:01:51.040> and<00:01:51.280> complicated<00:01:51.799> that<00:01:51.960> it<00:01:52.600> gained 00:01:53.270 --> 00:01:53.280 align:start position:0% so large and complicated that it gained 00:01:53.280 --> 00:01:56.950 align:start position:0% so large and complicated that it gained awareness<00:01:53.880> of<00:01:54.079> itself<00:01:54.799> so<00:01:55.439> okay<00:01:56.439> nice<00:01:56.719> let's 00:01:56.950 --> 00:01:56.960 align:start position:0% awareness of itself so okay nice let's 00:01:56.960 --> 00:01:59.310 align:start position:0% awareness of itself so okay nice let's have<00:01:57.079> a<00:01:57.360> world<00:01:57.640> super<00:01:57.960> computer<00:01:58.799> if<00:01:58.920> we<00:01:59.079> cannot 00:01:59.310 --> 00:01:59.320 align:start position:0% have a world super computer if we cannot 00:01:59.320 --> 00:02:01.709 align:start position:0% have a world super computer if we cannot do<00:01:59.439> it<00:01:59.560> with<00:01:59.680> each<00:02:00.240> we<00:02:00.360> can<00:02:00.640> implement<00:02:01.039> it 00:02:01.709 --> 00:02:01.719 align:start position:0% do it with each we can implement it 00:02:01.719 --> 00:02:05.270 align:start position:0% do it with each we can implement it ourselves<00:02:02.719> U<00:02:03.280> after<00:02:03.560> another<00:02:04.119> thought<00:02:05.119> we 00:02:05.270 --> 00:02:05.280 align:start position:0% ourselves U after another thought we 00:02:05.280 --> 00:02:07.990 align:start position:0% ourselves U after another thought we come<00:02:05.479> to<00:02:05.600> a<00:02:05.680> conclusion<00:02:06.200> that<00:02:07.079> it<00:02:07.360> doesn't 00:02:07.990 --> 00:02:08.000 align:start position:0% come to a conclusion that it doesn't 00:02:08.000 --> 00:02:09.550 align:start position:0% come to a conclusion that it doesn't really<00:02:08.239> makes<00:02:08.520> sense<00:02:08.879> because<00:02:09.280> there<00:02:09.399> are 00:02:09.550 --> 00:02:09.560 align:start position:0% really makes sense because there are 00:02:09.560 --> 00:02:11.270 align:start position:0% really makes sense because there are some<00:02:09.800> attempts<00:02:10.399> to<00:02:10.599> implement<00:02:10.959> something 00:02:11.270 --> 00:02:11.280 align:start position:0% some attempts to implement something 00:02:11.280 --> 00:02:16.710 align:start position:0% some attempts to implement something like<00:02:11.640> this<00:02:12.640> and<00:02:13.520> they<00:02:13.680> do<00:02:14.040> not<00:02:15.040> work<00:02:15.519> so 00:02:16.710 --> 00:02:16.720 align:start position:0% like this and they do not work so 00:02:16.720 --> 00:02:19.589 align:start position:0% like this and they do not work so far<00:02:17.720> well<00:02:17.920> we<00:02:18.080> have<00:02:18.480> cloud<00:02:18.800> computing<00:02:19.319> but 00:02:19.589 --> 00:02:19.599 align:start position:0% far well we have cloud computing but 00:02:19.599 --> 00:02:21.790 align:start position:0% far well we have cloud computing but this<00:02:19.800> requires<00:02:20.519> some<00:02:20.760> structure<00:02:21.200> over<00:02:21.480> the 00:02:21.790 --> 00:02:21.800 align:start position:0% this requires some structure over the 00:02:21.800 --> 00:02:24.509 align:start position:0% this requires some structure over the machines<00:02:22.200> and<00:02:22.480> hardware<00:02:23.480> and<00:02:23.599> we<00:02:23.720> cannot 00:02:24.509 --> 00:02:24.519 align:start position:0% machines and hardware and we cannot 00:02:24.519 --> 00:02:26.390 align:start position:0% machines and hardware and we cannot build<00:02:24.840> a<00:02:25.000> super<00:02:25.360> computer<00:02:25.680> or<00:02:25.959> provide 00:02:26.390 --> 00:02:26.400 align:start position:0% build a super computer or provide 00:02:26.400 --> 00:02:29.470 align:start position:0% build a super computer or provide computing<00:02:26.879> power<00:02:27.560> out<00:02:27.720> of<00:02:27.879> the<00:02:28.000> box<00:02:28.480> using 00:02:29.470 --> 00:02:29.480 align:start position:0% computing power out of the box using 00:02:29.480 --> 00:02:32.350 align:start position:0% computing power out of the box using just 00:02:32.350 --> 00:02:32.360 align:start position:0% 00:02:32.360 --> 00:02:36.550 align:start position:0% would<00:02:32.560> stay<00:02:32.920> at<00:02:33.239> homes<00:02:33.640> of<00:02:34.280> any<00:02:35.239> people<00:02:35.959> who 00:02:36.550 --> 00:02:36.560 align:start position:0% would stay at homes of any people who 00:02:36.560 --> 00:02:39.550 align:start position:0% would stay at homes of any people who would<00:02:36.760> like<00:02:36.959> to<00:02:37.239> provide<00:02:37.959> computing 00:02:39.550 --> 00:02:39.560 align:start position:0% would like to provide computing 00:02:39.560 --> 00:02:42.509 align:start position:0% would like to provide computing power<00:02:40.560> so<00:02:40.800> what<00:02:40.920> to<00:02:41.080> do<00:02:41.480> we<00:02:41.599> should<00:02:42.159> give<00:02:42.319> some 00:02:42.509 --> 00:02:42.519 align:start position:0% power so what to do we should give some 00:02:42.519 --> 00:02:44.030 align:start position:0% power so what to do we should give some incentive<00:02:42.920> to<00:02:43.120> them<00:02:43.360> they<00:02:43.440> should<00:02:43.640> be<00:02:43.720> able<00:02:43.920> to 00:02:44.030 --> 00:02:44.040 align:start position:0% incentive to them they should be able to 00:02:44.040 --> 00:02:45.589 align:start position:0% incentive to them they should be able to make<00:02:44.239> money 00:02:45.589 --> 00:02:45.599 align:start position:0% make money 00:02:45.599 --> 00:02:48.430 align:start position:0% make money and<00:02:46.599> then<00:02:46.800> maybe<00:02:47.159> that<00:02:47.319> that<00:02:47.440> would<00:02:47.640> work<00:02:48.239> but 00:02:48.430 --> 00:02:48.440 align:start position:0% and then maybe that that would work but 00:02:48.440 --> 00:02:50.550 align:start position:0% and then maybe that that would work but still<00:02:48.720> that's<00:02:49.080> pretty<00:02:49.360> hard<00:02:49.640> because<00:02:50.440> that 00:02:50.550 --> 00:02:50.560 align:start position:0% still that's pretty hard because that 00:02:50.560 --> 00:02:52.630 align:start position:0% still that's pretty hard because that would<00:02:50.760> require<00:02:51.480> registering<00:02:52.200> into<00:02:52.440> some 00:02:52.630 --> 00:02:52.640 align:start position:0% would require registering into some 00:02:52.640 --> 00:02:54.309 align:start position:0% would require registering into some services<00:02:53.159> that<00:02:53.280> would<00:02:53.720> allow<00:02:54.040> them<00:02:54.159> to 00:02:54.309 --> 00:02:54.319 align:start position:0% services that would allow them to 00:02:54.319 --> 00:02:57.229 align:start position:0% services that would allow them to transfer<00:02:54.879> value<00:02:55.680> for<00:02:55.959> the<00:02:56.560> computing<00:02:56.959> power 00:02:57.229 --> 00:02:57.239 align:start position:0% transfer value for the computing power 00:02:57.239 --> 00:03:00.229 align:start position:0% transfer value for the computing power that<00:02:57.599> they<00:02:57.680> would<00:02:57.840> like<00:02:57.959> to<00:02:58.080> share<00:02:58.840> so<00:02:59.879> obvious 00:03:00.229 --> 00:03:00.239 align:start position:0% that they would like to share so obvious 00:03:00.239 --> 00:03:03.149 align:start position:0% that they would like to share so obvious idea<00:03:00.599> is<00:03:01.080> that<00:03:01.239> it<00:03:01.360> should<00:03:01.519> be<00:03:01.879> bued<00:03:02.200> up<00:03:02.400> Byer 00:03:03.149 --> 00:03:03.159 align:start position:0% idea is that it should be bued up Byer 00:03:03.159 --> 00:03:05.190 align:start position:0% idea is that it should be bued up Byer or 00:03:05.190 --> 00:03:05.200 align:start position:0% or 00:03:05.200 --> 00:03:07.949 align:start position:0% or ethereum<00:03:06.200> and<00:03:06.519> that<00:03:06.799> what<00:03:06.959> we<00:03:07.360> started<00:03:07.799> to 00:03:07.949 --> 00:03:07.959 align:start position:0% ethereum and that what we started to 00:03:07.959 --> 00:03:10.630 align:start position:0% ethereum and that what we started to think 00:03:10.630 --> 00:03:10.640 align:start position:0% 00:03:10.640 --> 00:03:12.229 align:start position:0% about 00:03:12.229 --> 00:03:12.239 align:start position:0% about 00:03:12.239 --> 00:03:17.830 align:start position:0% about so<00:03:13.239> the<00:03:13.599> main<00:03:13.879> idea<00:03:14.680> is<00:03:15.720> that<00:03:16.720> we<00:03:16.840> would<00:03:17.040> like 00:03:17.830 --> 00:03:17.840 align:start position:0% so the main idea is that we would like 00:03:17.840 --> 00:03:20.110 align:start position:0% so the main idea is that we would like to 00:03:20.110 --> 00:03:20.120 align:start position:0% to 00:03:20.120 --> 00:03:25.990 align:start position:0% to provide<00:03:21.120> users<00:03:21.959> of<00:03:22.760> regular<00:03:23.200> PCS<00:03:24.040> or<00:03:24.440> whatever 00:03:25.990 --> 00:03:26.000 align:start position:0% provide users of regular PCS or whatever 00:03:26.000 --> 00:03:29.149 align:start position:0% provide users of regular PCS or whatever computers<00:03:27.000> with<00:03:27.680> possibilities<00:03:28.319> of<00:03:28.840> either 00:03:29.149 --> 00:03:29.159 align:start position:0% computers with possibilities of either 00:03:29.159 --> 00:03:31.509 align:start position:0% computers with possibilities of either Distributing<00:03:29.799> their<00:03:29.959> computation<00:03:30.439> across<00:03:30.720> a 00:03:31.509 --> 00:03:31.519 align:start position:0% Distributing their computation across a 00:03:31.519 --> 00:03:35.589 align:start position:0% Distributing their computation across a peer<00:03:31.760> to-peer<00:03:32.360> Network<00:03:33.360> or<00:03:33.799> to<00:03:34.239> make<00:03:34.560> some 00:03:35.589 --> 00:03:35.599 align:start position:0% peer to-peer Network or to make some 00:03:35.599 --> 00:03:38.910 align:start position:0% peer to-peer Network or to make some value<00:03:36.599> by<00:03:36.879> providing<00:03:37.400> their<00:03:37.959> uh<00:03:38.120> resources 00:03:38.910 --> 00:03:38.920 align:start position:0% value by providing their uh resources 00:03:38.920 --> 00:03:41.710 align:start position:0% value by providing their uh resources either<00:03:39.200> computation<00:03:39.760> or<00:03:40.239> storage<00:03:41.239> or<00:03:41.480> I<00:03:41.560> don't 00:03:41.710 --> 00:03:41.720 align:start position:0% either computation or storage or I don't 00:03:41.720 --> 00:03:45.750 align:start position:0% either computation or storage or I don't know<00:03:41.920> bandwidth<00:03:42.799> for<00:03:43.040> that<00:03:43.599> matter<00:03:44.599> uh<00:03:45.120> and<00:03:45.400> it 00:03:45.750 --> 00:03:45.760 align:start position:0% know bandwidth for that matter uh and it 00:03:45.760 --> 00:03:48.949 align:start position:0% know bandwidth for that matter uh and it should<00:03:46.760> allow<00:03:47.080> them<00:03:47.239> to<00:03:47.400> do<00:03:47.599> it<00:03:48.319> pretty<00:03:48.599> easily 00:03:48.949 --> 00:03:48.959 align:start position:0% should allow them to do it pretty easily 00:03:48.959 --> 00:03:53.509 align:start position:0% should allow them to do it pretty easily on<00:03:49.159> both<00:03:49.560> sides<00:03:50.840> special<00:03:52.040> specifica<00:03:53.040> tasks 00:03:53.509 --> 00:03:53.519 align:start position:0% on both sides special specifica tasks 00:03:53.519 --> 00:03:56.789 align:start position:0% on both sides special specifica tasks may<00:03:53.799> not<00:03:54.040> be<00:03:54.200> so<00:03:54.640> easy<00:03:55.640> but<00:03:56.120> computation 00:03:56.789 --> 00:03:56.799 align:start position:0% may not be so easy but computation 00:03:56.799 --> 00:03:59.149 align:start position:0% may not be so easy but computation should<00:03:57.079> be<00:03:57.519> out<00:03:57.680> of<00:03:57.840> the<00:03:58.000> box<00:03:58.319> without<00:03:58.959> any 00:03:59.149 --> 00:03:59.159 align:start position:0% should be out of the box without any 00:03:59.159 --> 00:04:00.390 align:start position:0% should be out of the box without any additional<00:03:59.480> conf 00:04:00.390 --> 00:04:00.400 align:start position:0% additional conf 00:04:00.400 --> 00:04:04.509 align:start position:0% additional conf uration<00:04:01.400> and<00:04:01.599> they<00:04:01.760> should<00:04:02.599> get<00:04:03.599> remuneration 00:04:04.509 --> 00:04:04.519 align:start position:0% uration and they should get remuneration 00:04:04.519 --> 00:04:07.069 align:start position:0% uration and they should get remuneration for<00:04:05.239> computing 00:04:07.069 --> 00:04:07.079 align:start position:0% for computing 00:04:07.079 --> 00:04:10.110 align:start position:0% for computing something<00:04:08.079> uh<00:04:08.799> that's<00:04:09.239> what's<00:04:09.519> important<00:04:09.959> is 00:04:10.110 --> 00:04:10.120 align:start position:0% something uh that's what's important is 00:04:10.120 --> 00:04:12.750 align:start position:0% something uh that's what's important is that<00:04:10.879> we<00:04:11.040> don't<00:04:11.280> want<00:04:11.560> them 00:04:12.750 --> 00:04:12.760 align:start position:0% that we don't want them 00:04:12.760 --> 00:04:17.310 align:start position:0% that we don't want them to<00:04:13.760> uh 00:04:17.310 --> 00:04:17.320 align:start position:0% 00:04:17.320 --> 00:04:21.069 align:start position:0% get<00:04:18.320> threatened<00:04:18.880> by<00:04:19.160> malicious<00:04:20.040> nodes<00:04:20.759> inside 00:04:21.069 --> 00:04:21.079 align:start position:0% get threatened by malicious nodes inside 00:04:21.079 --> 00:04:23.430 align:start position:0% get threatened by malicious nodes inside the<00:04:21.239> network<00:04:22.040> so<00:04:22.240> all<00:04:22.440> computations<00:04:23.160> have<00:04:23.280> to 00:04:23.430 --> 00:04:23.440 align:start position:0% the network so all computations have to 00:04:23.440 --> 00:04:26.030 align:start position:0% the network so all computations have to be<00:04:23.759> separated<00:04:24.280> from<00:04:24.560> their<00:04:24.800> host<00:04:25.040> machines 00:04:26.030 --> 00:04:26.040 align:start position:0% be separated from their host machines 00:04:26.040 --> 00:04:28.870 align:start position:0% be separated from their host machines this<00:04:26.160> is<00:04:27.120> where<00:04:27.600> virtual<00:04:27.919> machines<00:04:28.320> come<00:04:28.600> into 00:04:28.870 --> 00:04:28.880 align:start position:0% this is where virtual machines come into 00:04:28.880 --> 00:04:30.590 align:start position:0% this is where virtual machines come into into<00:04:29.440> role 00:04:30.590 --> 00:04:30.600 align:start position:0% into role 00:04:30.600 --> 00:04:34.670 align:start position:0% into role and<00:04:31.520> in<00:04:31.639> general<00:04:32.039> the<00:04:32.199> task<00:04:32.479> is<00:04:33.440> some<00:04:33.880> code 00:04:34.670 --> 00:04:34.680 align:start position:0% and in general the task is some code 00:04:34.680 --> 00:04:36.629 align:start position:0% and in general the task is some code well<00:04:34.919> in<00:04:35.039> fact<00:04:35.240> any<00:04:35.440> code<00:04:36.240> that<00:04:36.360> can<00:04:36.520> be 00:04:36.629 --> 00:04:36.639 align:start position:0% well in fact any code that can be 00:04:36.639 --> 00:04:38.189 align:start position:0% well in fact any code that can be written<00:04:36.919> in<00:04:37.120> one<00:04:37.240> of<00:04:37.360> support<00:04:37.680> languages<00:04:38.080> that 00:04:38.189 --> 00:04:38.199 align:start position:0% written in one of support languages that 00:04:38.199 --> 00:04:40.469 align:start position:0% written in one of support languages that we<00:04:38.320> can<00:04:38.759> distribute<00:04:39.199> across<00:04:39.479> the<00:04:39.600> network<00:04:40.280> and 00:04:40.469 --> 00:04:40.479 align:start position:0% we can distribute across the network and 00:04:40.479 --> 00:04:42.590 align:start position:0% we can distribute across the network and run<00:04:40.800> inside<00:04:41.160> the<00:04:41.360> virtual 00:04:42.590 --> 00:04:42.600 align:start position:0% run inside the virtual 00:04:42.600 --> 00:04:45.909 align:start position:0% run inside the virtual machine<00:04:43.600> with<00:04:43.759> some<00:04:43.960> constraints<00:04:44.919> because 00:04:45.909 --> 00:04:45.919 align:start position:0% machine with some constraints because 00:04:45.919 --> 00:04:49.550 align:start position:0% machine with some constraints because first<00:04:46.120> of<00:04:46.240> all<00:04:46.400> we<00:04:46.479> don't<00:04:46.680> want<00:04:47.360> to<00:04:48.360> uh<00:04:49.039> thread 00:04:49.550 --> 00:04:49.560 align:start position:0% first of all we don't want to uh thread 00:04:49.560 --> 00:04:51.870 align:start position:0% first of all we don't want to uh thread that<00:04:50.080> Computing<00:04:50.560> node<00:04:51.240> and<00:04:51.400> on<00:04:51.520> the<00:04:51.680> other 00:04:51.870 --> 00:04:51.880 align:start position:0% that Computing node and on the other 00:04:51.880 --> 00:04:53.710 align:start position:0% that Computing node and on the other hand<00:04:52.080> we<00:04:52.199> wouldn't<00:04:52.560> like 00:04:53.710 --> 00:04:53.720 align:start position:0% hand we wouldn't like 00:04:53.720 --> 00:04:58.350 align:start position:0% hand we wouldn't like to<00:04:54.880> create<00:04:55.880> environment<00:04:56.479> which<00:04:56.759> would 00:04:58.350 --> 00:04:58.360 align:start position:0% to create environment which would 00:04:58.360 --> 00:05:01.390 align:start position:0% to create environment which would allow<00:04:59.360> attack<00:04:59.680> haers<00:05:00.000> hackers<00:05:00.400> I<00:05:00.479> don't<00:05:00.600> know 00:05:01.390 --> 00:05:01.400 align:start position:0% allow attack haers hackers I don't know 00:05:01.400 --> 00:05:03.629 align:start position:0% allow attack haers hackers I don't know whatever<00:05:01.880> malicious<00:05:02.320> Nots<00:05:02.639> they<00:05:02.800> may<00:05:03.360> be<00:05:03.520> in 00:05:03.629 --> 00:05:03.639 align:start position:0% whatever malicious Nots they may be in 00:05:03.639 --> 00:05:05.710 align:start position:0% whatever malicious Nots they may be in the<00:05:03.800> network<00:05:04.400> to<00:05:04.600> attack<00:05:04.919> other<00:05:05.160> computers 00:05:05.710 --> 00:05:05.720 align:start position:0% the network to attack other computers 00:05:05.720 --> 00:05:07.870 align:start position:0% the network to attack other computers not<00:05:05.880> necessarily<00:05:06.360> the<00:05:06.479> host<00:05:06.759> one<00:05:07.320> but<00:05:07.479> some 00:05:07.870 --> 00:05:07.880 align:start position:0% not necessarily the host one but some 00:05:07.880 --> 00:05:12.629 align:start position:0% not necessarily the host one but some other<00:05:08.880> we<00:05:09.120> can<00:05:10.120> imagine<00:05:10.440> a<00:05:10.600> scenario<00:05:11.280> when 00:05:12.629 --> 00:05:12.639 align:start position:0% other we can imagine a scenario when 00:05:12.639 --> 00:05:15.110 align:start position:0% other we can imagine a scenario when someone<00:05:13.639> prepares<00:05:14.080> a<00:05:14.240> Dos<00:05:14.680> attack 00:05:15.110 --> 00:05:15.120 align:start position:0% someone prepares a Dos attack 00:05:15.120 --> 00:05:17.710 align:start position:0% someone prepares a Dos attack distributed<00:05:15.600> D<00:05:15.800> of<00:05:15.919> service<00:05:16.840> just<00:05:17.080> by<00:05:17.280> sending 00:05:17.710 --> 00:05:17.720 align:start position:0% distributed D of service just by sending 00:05:17.720 --> 00:05:19.230 align:start position:0% distributed D of service just by sending a<00:05:17.840> million<00:05:18.160> tasks<00:05:18.560> that<00:05:18.680> would<00:05:18.919> try<00:05:19.120> to 00:05:19.230 --> 00:05:19.240 align:start position:0% a million tasks that would try to 00:05:19.240 --> 00:05:24.230 align:start position:0% a million tasks that would try to connect<00:05:19.560> to<00:05:19.680> some<00:05:20.000> server<00:05:21.000> so<00:05:21.520> this<00:05:21.720> cannot 00:05:24.230 --> 00:05:24.240 align:start position:0% 00:05:24.240 --> 00:05:27.230 align:start position:0% happen<00:05:25.240> uh<00:05:25.560> we<00:05:25.720> started<00:05:26.160> our<00:05:26.800> proof<00:05:27.039> of 00:05:27.230 --> 00:05:27.240 align:start position:0% happen uh we started our proof of 00:05:27.240 --> 00:05:31.550 align:start position:0% happen uh we started our proof of concept<00:05:28.120> right<00:05:28.280> now<00:05:28.560> we<00:05:29.039> implemented 00:05:31.550 --> 00:05:31.560 align:start position:0% concept right now we implemented 00:05:31.560 --> 00:05:35.029 align:start position:0% concept right now we implemented well<00:05:32.560> I<00:05:32.720> sorry<00:05:33.000> for<00:05:33.199> the<00:05:33.840> noty<00:05:34.280> graphics<00:05:34.720> but 00:05:35.029 --> 00:05:35.039 align:start position:0% well I sorry for the noty graphics but 00:05:35.039 --> 00:05:37.309 align:start position:0% well I sorry for the noty graphics but that's<00:05:35.199> how<00:05:35.360> it<00:05:35.440> looks<00:05:35.639> like<00:05:35.840> right<00:05:36.199> now<00:05:37.199> we 00:05:37.309 --> 00:05:37.319 align:start position:0% that's how it looks like right now we 00:05:37.319 --> 00:05:39.830 align:start position:0% that's how it looks like right now we implemented<00:05:37.800> a<00:05:37.919> few<00:05:38.160> renderers<00:05:39.160> as<00:05:39.280> a 00:05:39.830 --> 00:05:39.840 align:start position:0% implemented a few renderers as a 00:05:39.840 --> 00:05:43.790 align:start position:0% implemented a few renderers as a backends<00:05:40.840> and<00:05:41.080> right<00:05:41.240> now<00:05:41.479> we<00:05:42.000> have<00:05:43.000> both<00:05:43.520> open 00:05:43.790 --> 00:05:43.800 align:start position:0% backends and right now we have both open 00:05:43.800 --> 00:05:45.870 align:start position:0% backends and right now we have both open source<00:05:44.039> renderers<00:05:44.600> and 00:05:45.870 --> 00:05:45.880 align:start position:0% source renderers and 00:05:45.880 --> 00:05:49.590 align:start position:0% source renderers and commercial<00:05:46.880> production<00:05:47.759> renderers<00:05:48.759> added<00:05:49.039> to 00:05:49.590 --> 00:05:49.600 align:start position:0% commercial production renderers added to 00:05:49.600 --> 00:05:53.870 align:start position:0% commercial production renderers added to the<00:05:50.600> project<00:05:51.560> and<00:05:51.960> they<00:05:52.199> can<00:05:53.120> you<00:05:53.280> cannot<00:05:53.680> see 00:05:53.870 --> 00:05:53.880 align:start position:0% the project and they can you cannot see 00:05:53.880 --> 00:05:57.710 align:start position:0% the project and they can you cannot see this<00:05:54.199> here<00:05:55.440> but<00:05:56.440> right 00:05:57.710 --> 00:05:57.720 align:start position:0% this here but right 00:05:57.720 --> 00:06:01.270 align:start position:0% this here but right here<00:05:58.720> uh<00:05:59.240> there's<00:05:59.479> a<00:05:59.800> rank<00:06:00.039> of 00:06:01.270 --> 00:06:01.280 align:start position:0% here uh there's a rank of 00:06:01.280 --> 00:06:04.870 align:start position:0% here uh there's a rank of four<00:06:02.280> Images<00:06:03.080> the<00:06:03.199> one<00:06:03.440> shown<00:06:04.360> here<00:06:04.520> is<00:06:04.720> the 00:06:04.870 --> 00:06:04.880 align:start position:0% four Images the one shown here is the 00:06:04.880 --> 00:06:07.589 align:start position:0% four Images the one shown here is the last<00:06:05.080> one<00:06:05.639> the<00:06:05.800> last<00:06:05.960> one<00:06:06.160> is<00:06:06.720> mental<00:06:07.120> Ray<00:06:07.440> I 00:06:07.589 --> 00:06:07.599 align:start position:0% last one the last one is mental Ray I 00:06:07.599 --> 00:06:09.430 align:start position:0% last one the last one is mental Ray I don't<00:06:07.720> know<00:06:07.840> if<00:06:07.919> you<00:06:08.039> know<00:06:08.199> the<00:06:08.360> under<00:06:09.199> it's<00:06:09.280> a 00:06:09.430 --> 00:06:09.440 align:start position:0% don't know if you know the under it's a 00:06:09.440 --> 00:06:12.469 align:start position:0% don't know if you know the under it's a commercial<00:06:09.880> under<00:06:10.880> and<00:06:11.240> other<00:06:11.520> three<00:06:11.840> are<00:06:12.199> two 00:06:12.469 --> 00:06:12.479 align:start position:0% commercial under and other three are two 00:06:12.479 --> 00:06:15.510 align:start position:0% commercial under and other three are two pbts<00:06:13.120> and<00:06:13.400> one<00:06:13.919> vray<00:06:14.759> vray<00:06:15.120> is<00:06:15.240> also<00:06:15.400> a 00:06:15.510 --> 00:06:15.520 align:start position:0% pbts and one vray vray is also a 00:06:15.520 --> 00:06:18.350 align:start position:0% pbts and one vray vray is also a commercial<00:06:15.840> and<00:06:16.000> eror<00:06:16.800> on<00:06:16.960> the<00:06:17.120> right<00:06:17.360> P<00:06:17.639> we 00:06:18.350 --> 00:06:18.360 align:start position:0% commercial and eror on the right P we 00:06:18.360 --> 00:06:21.870 align:start position:0% commercial and eror on the right P we see<00:06:19.360> sap<00:06:19.720> tasks<00:06:20.319> which<00:06:20.479> means<00:06:20.759> that<00:06:21.560> small 00:06:21.870 --> 00:06:21.880 align:start position:0% see sap tasks which means that small 00:06:21.880 --> 00:06:23.350 align:start position:0% see sap tasks which means that small tasks<00:06:22.160> that<00:06:22.280> were<00:06:22.520> distributed<00:06:23.000> across<00:06:23.240> the 00:06:23.350 --> 00:06:23.360 align:start position:0% tasks that were distributed across the 00:06:23.360 --> 00:06:26.150 align:start position:0% tasks that were distributed across the network<00:06:23.759> and<00:06:24.400> are<00:06:24.599> being<00:06:24.880> gathered<00:06:25.759> into<00:06:25.960> a 00:06:26.150 --> 00:06:26.160 align:start position:0% network and are being gathered into a 00:06:26.160 --> 00:06:28.110 align:start position:0% network and are being gathered into a final 00:06:28.110 --> 00:06:28.120 align:start position:0% final 00:06:28.120 --> 00:06:33.589 align:start position:0% final picture<00:06:29.120> so<00:06:29.639> this<00:06:29.759> is<00:06:29.880> it<00:06:30.960> um<00:06:31.960> we<00:06:32.160> believe<00:06:32.680> that 00:06:33.589 --> 00:06:33.599 align:start position:0% picture so this is it um we believe that 00:06:33.599 --> 00:06:36.749 align:start position:0% picture so this is it um we believe that such<00:06:34.199> framework<00:06:34.800> can<00:06:34.960> be<00:06:35.160> used<00:06:36.120> for<00:06:36.440> something 00:06:36.749 --> 00:06:36.759 align:start position:0% such framework can be used for something 00:06:36.759 --> 00:06:38.550 align:start position:0% such framework can be used for something more<00:06:36.919> than<00:06:37.080> just<00:06:37.199> rendering<00:06:38.080> well<00:06:38.240> in<00:06:38.400> fact 00:06:38.550 --> 00:06:38.560 align:start position:0% more than just rendering well in fact 00:06:38.560 --> 00:06:41.029 align:start position:0% more than just rendering well in fact for<00:06:38.720> any<00:06:39.000> computation<00:06:39.599> that<00:06:39.800> can<00:06:39.960> be 00:06:41.029 --> 00:06:41.039 align:start position:0% for any computation that can be 00:06:41.039 --> 00:06:42.870 align:start position:0% for any computation that can be distributed 00:06:42.870 --> 00:06:42.880 align:start position:0% distributed 00:06:42.880 --> 00:06:47.230 align:start position:0% distributed and<00:06:43.880> in<00:06:44.759> in<00:06:45.000> principle<00:06:45.400> it<00:06:45.560> should<00:06:45.759> work<00:06:46.000> as<00:06:46.240> a 00:06:47.230 --> 00:06:47.240 align:start position:0% and in in principle it should work as a 00:06:47.240 --> 00:06:51.189 align:start position:0% and in in principle it should work as a map<00:06:47.599> reduce<00:06:48.400> computation<00:06:48.880> model<00:06:49.759> maybe<00:06:50.479> bit 00:06:51.189 --> 00:06:51.199 align:start position:0% map reduce computation model maybe bit 00:06:51.199 --> 00:06:53.350 align:start position:0% map reduce computation model maybe bit more<00:06:51.520> generic<00:06:52.080> because<00:06:52.680> we<00:06:52.800> don't<00:06:53.000> want<00:06:53.199> just 00:06:53.350 --> 00:06:53.360 align:start position:0% more generic because we don't want just 00:06:53.360 --> 00:06:56.469 align:start position:0% more generic because we don't want just to<00:06:53.599> distribute<00:06:54.000> and<00:06:54.199> gather<00:06:54.759> results<00:06:55.199> but<00:06:56.199> to 00:06:56.469 --> 00:06:56.479 align:start position:0% to distribute and gather results but to 00:06:56.479 --> 00:07:00.230 align:start position:0% to distribute and gather results but to prepare<00:06:57.039> a<00:06:58.039> graph<00:06:58.720> a<00:06:58.919> CYCC<00:06:59.280> graph<00:06:59.759> of<00:06:59.960> such 00:07:00.230 --> 00:07:00.240 align:start position:0% prepare a graph a CYCC graph of such 00:07:00.240 --> 00:07:03.869 align:start position:0% prepare a graph a CYCC graph of such tasks<00:07:01.039> that<00:07:01.199> can<00:07:01.599> distribute<00:07:02.599> their<00:07:02.919> subtasks 00:07:03.869 --> 00:07:03.879 align:start position:0% tasks that can distribute their subtasks 00:07:03.879 --> 00:07:05.670 align:start position:0% tasks that can distribute their subtasks gather<00:07:04.160> the<00:07:04.319> results<00:07:05.000> and<00:07:05.160> based<00:07:05.360> on<00:07:05.479> that 00:07:05.670 --> 00:07:05.680 align:start position:0% gather the results and based on that 00:07:05.680 --> 00:07:08.909 align:start position:0% gather the results and based on that results<00:07:06.479> send<00:07:06.840> another<00:07:07.280> list<00:07:07.560> of<00:07:07.759> tasks<00:07:08.080> to 00:07:08.909 --> 00:07:08.919 align:start position:0% results send another list of tasks to 00:07:08.919 --> 00:07:11.909 align:start position:0% results send another list of tasks to perform<00:07:09.240> under<00:07:10.000> computation<00:07:11.000> you<00:07:11.120> can<00:07:11.319> use<00:07:11.479> it 00:07:11.909 --> 00:07:11.919 align:start position:0% perform under computation you can use it 00:07:11.919 --> 00:07:14.070 align:start position:0% perform under computation you can use it we<00:07:12.080> we<00:07:12.199> used<00:07:12.440> it<00:07:12.599> for<00:07:13.120> rendering<00:07:13.680> in<00:07:13.840> for 00:07:14.070 --> 00:07:14.080 align:start position:0% we we used it for rendering in for 00:07:14.080 --> 00:07:16.749 align:start position:0% we we used it for rendering in for scientific<00:07:14.560> calculations<00:07:15.319> in 00:07:16.749 --> 00:07:16.759 align:start position:0% scientific calculations in 00:07:16.759 --> 00:07:18.909 align:start position:0% scientific calculations in hemistry<00:07:17.759> it<00:07:17.919> can<00:07:18.039> be<00:07:18.160> used<00:07:18.360> for<00:07:18.479> M 00:07:18.909 --> 00:07:18.919 align:start position:0% hemistry it can be used for M 00:07:18.919 --> 00:07:20.990 align:start position:0% hemistry it can be used for M integration<00:07:19.360> easily<00:07:20.199> even<00:07:20.400> for<00:07:20.599> Bitcoin 00:07:20.990 --> 00:07:21.000 align:start position:0% integration easily even for Bitcoin 00:07:21.000 --> 00:07:23.909 align:start position:0% integration easily even for Bitcoin mining<00:07:21.400> if<00:07:21.960> someone<00:07:22.280> would<00:07:22.440> like<00:07:22.599> to<00:07:22.720> do 00:07:23.909 --> 00:07:23.919 align:start position:0% mining if someone would like to do 00:07:23.919 --> 00:07:26.990 align:start position:0% mining if someone would like to do it<00:07:24.919> the<00:07:25.080> main<00:07:25.479> problem<00:07:25.960> with<00:07:26.400> this<00:07:26.639> approach 00:07:26.990 --> 00:07:27.000 align:start position:0% it the main problem with this approach 00:07:27.000 --> 00:07:29.230 align:start position:0% it the main problem with this approach is<00:07:27.199> that<00:07:27.599> it<00:07:27.759> require<00:07:28.160> means<00:07:28.360> of<00:07:28.520> validating 00:07:29.230 --> 00:07:29.240 align:start position:0% is that it require means of validating 00:07:29.240 --> 00:07:32.070 align:start position:0% is that it require means of validating and<00:07:29.520> Collective<00:07:30.199> results<00:07:31.199> because<00:07:31.479> one<00:07:31.879> once 00:07:32.070 --> 00:07:32.080 align:start position:0% and Collective results because one once 00:07:32.080 --> 00:07:36.070 align:start position:0% and Collective results because one once it's<00:07:32.240> set<00:07:32.599> to<00:07:33.280> a<00:07:33.680> network<00:07:34.680> we<00:07:34.879> have<00:07:35.280> no<00:07:35.560> idea 00:07:36.070 --> 00:07:36.080 align:start position:0% it's set to a network we have no idea 00:07:36.080 --> 00:07:39.550 align:start position:0% it's set to a network we have no idea who<00:07:36.240> may<00:07:36.400> be<00:07:36.840> calculating<00:07:37.479> and<00:07:38.120> what<00:07:39.120> value<00:07:39.400> of 00:07:39.550 --> 00:07:39.560 align:start position:0% who may be calculating and what value of 00:07:39.560 --> 00:07:42.790 align:start position:0% who may be calculating and what value of the<00:07:40.360> those<00:07:40.520> results<00:07:40.919> may<00:07:41.120> have<00:07:41.800> they<00:07:41.960> may<00:07:42.160> be 00:07:42.790 --> 00:07:42.800 align:start position:0% the those results may have they may be 00:07:42.800 --> 00:07:45.189 align:start position:0% the those results may have they may be completely<00:07:43.360> invalid<00:07:44.360> they<00:07:44.479> may<00:07:44.639> be<00:07:44.800> partially 00:07:45.189 --> 00:07:45.199 align:start position:0% completely invalid they may be partially 00:07:45.199 --> 00:07:48.550 align:start position:0% completely invalid they may be partially invalid<00:07:45.680> or<00:07:46.240> simply<00:07:46.599> valid<00:07:47.400> so<00:07:47.759> we<00:07:47.879> need<00:07:48.280> some 00:07:48.550 --> 00:07:48.560 align:start position:0% invalid or simply valid so we need some 00:07:48.560 --> 00:07:50.909 align:start position:0% invalid or simply valid so we need some means<00:07:48.879> of<00:07:49.360> getting<00:07:49.639> the<00:07:49.800> right<00:07:50.039> results<00:07:50.720> and 00:07:50.909 --> 00:07:50.919 align:start position:0% means of getting the right results and 00:07:50.919 --> 00:07:53.149 align:start position:0% means of getting the right results and collecting<00:07:51.319> them<00:07:51.479> into<00:07:52.199> our<00:07:52.560> the<00:07:52.720> result<00:07:53.039> that 00:07:53.149 --> 00:07:53.159 align:start position:0% collecting them into our the result that 00:07:53.159 --> 00:07:56.790 align:start position:0% collecting them into our the result that we<00:07:53.280> need<00:07:53.479> to<00:07:54.319> use<00:07:54.919> we<00:07:55.080> can 00:07:56.790 --> 00:07:56.800 align:start position:0% we need to use we can 00:07:56.800 --> 00:08:00.110 align:start position:0% we need to use we can use<00:07:57.800> so<00:07:58.080> what<00:07:58.680> they<00:07:58.840> have<00:07:59.000> in<00:07:59.159> common 00:08:00.110 --> 00:08:00.120 align:start position:0% use so what they have in common 00:08:00.120 --> 00:08:02.589 align:start position:0% use so what they have in common Golem<00:08:00.360> in<00:08:00.479> etherum<00:08:01.479> because<00:08:02.080> we<00:08:02.240> can<00:08:02.400> use 00:08:02.589 --> 00:08:02.599 align:start position:0% Golem in etherum because we can use 00:08:02.599 --> 00:08:05.869 align:start position:0% Golem in etherum because we can use ethereum<00:08:03.080> as<00:08:03.639> a<00:08:04.639> payment 00:08:05.869 --> 00:08:05.879 align:start position:0% ethereum as a payment 00:08:05.879 --> 00:08:08.749 align:start position:0% ethereum as a payment system<00:08:06.879> but<00:08:07.759> on<00:08:07.919> the<00:08:08.039> other<00:08:08.240> hand<00:08:08.440> there<00:08:08.560> are 00:08:08.749 --> 00:08:08.759 align:start position:0% system but on the other hand there are 00:08:08.759 --> 00:08:11.510 align:start position:0% system but on the other hand there are some<00:08:09.159> modules<00:08:09.639> and<00:08:10.280> parts<00:08:10.520> of<00:08:10.639> the<00:08:10.759> source 00:08:11.510 --> 00:08:11.520 align:start position:0% some modules and parts of the source 00:08:11.520 --> 00:08:14.029 align:start position:0% some modules and parts of the source code<00:08:12.520> that 00:08:14.029 --> 00:08:14.039 align:start position:0% code that 00:08:14.039 --> 00:08:17.550 align:start position:0% code that seem<00:08:15.039> pretty<00:08:15.360> similar<00:08:15.840> in<00:08:16.080> both<00:08:16.440> projects<00:08:17.440> we 00:08:17.550 --> 00:08:17.560 align:start position:0% seem pretty similar in both projects we 00:08:17.560 --> 00:08:20.230 align:start position:0% seem pretty similar in both projects we would<00:08:18.039> require<00:08:19.039> a<00:08:19.280> very<00:08:19.520> good<00:08:19.759> peer-to-peer 00:08:20.230 --> 00:08:20.240 align:start position:0% would require a very good peer-to-peer 00:08:20.240 --> 00:08:23.710 align:start position:0% would require a very good peer-to-peer module<00:08:21.240> and<00:08:21.479> transport<00:08:22.120> transport<00:08:22.720> layer 00:08:23.710 --> 00:08:23.720 align:start position:0% module and transport transport layer 00:08:23.720 --> 00:08:27.990 align:start position:0% module and transport transport layer along<00:08:24.080> with<00:08:24.639> node<00:08:25.199> Discovery<00:08:25.599> and<00:08:26.280> resource 00:08:27.990 --> 00:08:28.000 align:start position:0% along with node Discovery and resource 00:08:28.000 --> 00:08:31.309 align:start position:0% along with node Discovery and resource transfer<00:08:29.000> and<00:08:29.560> very<00:08:29.800> good<00:08:30.039> resource<00:08:30.479> sharing 00:08:31.309 --> 00:08:31.319 align:start position:0% transfer and very good resource sharing 00:08:31.319 --> 00:08:32.550 align:start position:0% transfer and very good resource sharing and<00:08:31.520> management 00:08:32.550 --> 00:08:32.560 align:start position:0% and management 00:08:32.560 --> 00:08:35.670 align:start position:0% and management Machinery<00:08:33.560> because<00:08:34.479> when<00:08:34.959> you<00:08:35.159> write<00:08:35.399> a 00:08:35.670 --> 00:08:35.680 align:start position:0% Machinery because when you write a 00:08:35.680 --> 00:08:39.550 align:start position:0% Machinery because when you write a program<00:08:36.680> you<00:08:36.839> don't<00:08:37.240> only<00:08:38.240> try<00:08:38.479> to<00:08:38.680> access 00:08:39.550 --> 00:08:39.560 align:start position:0% program you don't only try to access 00:08:39.560 --> 00:08:44.710 align:start position:0% program you don't only try to access local<00:08:39.959> files<00:08:40.880> or<00:08:41.159> web<00:08:42.000> and<00:08:43.120> servers<00:08:44.120> but<00:08:44.440> maybe 00:08:44.710 --> 00:08:44.720 align:start position:0% local files or web and servers but maybe 00:08:44.720 --> 00:08:46.550 align:start position:0% local files or web and servers but maybe other<00:08:44.920> computers<00:08:45.279> in<00:08:45.399> the<00:08:45.560> network<00:08:45.880> and<00:08:46.000> so<00:08:46.160> on 00:08:46.550 --> 00:08:46.560 align:start position:0% other computers in the network and so on 00:08:46.560 --> 00:08:48.310 align:start position:0% other computers in the network and so on so<00:08:46.760> it<00:08:46.880> should<00:08:47.160> all<00:08:47.320> be<00:08:47.480> worked 00:08:48.310 --> 00:08:48.320 align:start position:0% so it should all be worked 00:08:48.320 --> 00:08:50.630 align:start position:0% so it should all be worked out<00:08:49.320> but<00:08:49.519> this<00:08:49.839> that's<00:08:50.040> the<00:08:50.200> side<00:08:50.399> of<00:08:50.519> the 00:08:50.630 --> 00:08:50.640 align:start position:0% out but this that's the side of the 00:08:50.640 --> 00:08:53.310 align:start position:0% out but this that's the side of the Golem<00:08:51.560> although<00:08:51.880> I<00:08:52.000> believe<00:08:52.360> that<00:08:52.680> some 00:08:53.310 --> 00:08:53.320 align:start position:0% Golem although I believe that some 00:08:53.320 --> 00:08:56.870 align:start position:0% Golem although I believe that some resource<00:08:53.760> rank<00:08:54.120> would<00:08:54.279> be<00:08:54.440> also<00:08:55.120> required<00:08:55.600> in 00:08:56.870 --> 00:08:56.880 align:start position:0% resource rank would be also required in 00:08:56.880 --> 00:08:59.190 align:start position:0% resource rank would be also required in ethereum<00:08:57.880> if<00:08:58.120> parts<00:08:58.360> of<00:08:58.519> code<00:08:58.760> are<00:08:58.920> going<00:08:59.079> to 00:08:59.190 --> 00:08:59.200 align:start position:0% ethereum if parts of code are going to 00:08:59.200 --> 00:09:01.150 align:start position:0% ethereum if parts of code are going to be<00:08:59.480> sh<00:08:59.800> across<00:09:00.120> the 00:09:01.150 --> 00:09:01.160 align:start position:0% be sh across the 00:09:01.160 --> 00:09:03.470 align:start position:0% be sh across the network<00:09:02.160> but<00:09:02.399> from<00:09:02.560> our<00:09:02.880> perspective<00:09:03.360> the 00:09:03.470 --> 00:09:03.480 align:start position:0% network but from our perspective the 00:09:03.480 --> 00:09:05.230 align:start position:0% network but from our perspective the most<00:09:03.720> important<00:09:04.079> thing<00:09:04.279> is<00:09:04.519> to<00:09:04.680> use<00:09:04.880> it<00:09:05.040> room 00:09:05.230 --> 00:09:05.240 align:start position:0% most important thing is to use it room 00:09:05.240 --> 00:09:09.630 align:start position:0% most important thing is to use it room as<00:09:05.320> a<00:09:05.399> generic<00:09:05.720> payment<00:09:06.279> system<00:09:07.560> because<00:09:08.560> oh 00:09:09.630 --> 00:09:09.640 align:start position:0% as a generic payment system because oh 00:09:09.640 --> 00:09:11.750 align:start position:0% as a generic payment system because oh because<00:09:10.640> because<00:09:10.880> the<00:09:11.000> traditional<00:09:11.399> approach 00:09:11.750 --> 00:09:11.760 align:start position:0% because because the traditional approach 00:09:11.760 --> 00:09:14.870 align:start position:0% because because the traditional approach look<00:09:12.000> looks<00:09:12.240> like<00:09:12.800> this<00:09:13.800> a<00:09:13.920> user<00:09:14.360> have<00:09:14.560> have<00:09:14.720> to 00:09:14.870 --> 00:09:14.880 align:start position:0% look looks like this a user have have to 00:09:14.880 --> 00:09:18.110 align:start position:0% look looks like this a user have have to register<00:09:15.240> to<00:09:15.440> some<00:09:15.880> service<00:09:16.880> that<00:09:17.360> allows<00:09:17.800> him 00:09:18.110 --> 00:09:18.120 align:start position:0% register to some service that allows him 00:09:18.120 --> 00:09:21.550 align:start position:0% register to some service that allows him her<00:09:18.959> to<00:09:19.519> transfer 00:09:21.550 --> 00:09:21.560 align:start position:0% her to transfer 00:09:21.560 --> 00:09:23.750 align:start position:0% her to transfer value 00:09:23.750 --> 00:09:23.760 align:start position:0% value 00:09:23.760 --> 00:09:25.829 align:start position:0% value and<00:09:24.760> this<00:09:24.880> is<00:09:25.000> a 00:09:25.829 --> 00:09:25.839 align:start position:0% and this is a 00:09:25.839 --> 00:09:29.430 align:start position:0% and this is a centralized<00:09:26.839> solution<00:09:27.640> requires<00:09:28.640> giving<00:09:29.079> out 00:09:29.430 --> 00:09:29.440 align:start position:0% centralized solution requires giving out 00:09:29.440 --> 00:09:31.750 align:start position:0% centralized solution requires giving out some<00:09:29.720> private<00:09:30.079> data<00:09:30.839> that<00:09:30.959> would<00:09:31.120> be<00:09:31.240> stored 00:09:31.750 --> 00:09:31.760 align:start position:0% some private data that would be stored 00:09:31.760 --> 00:09:37.030 align:start position:0% some private data that would be stored somewhere<00:09:32.760> in<00:09:32.920> some<00:09:33.519> on<00:09:33.720> some<00:09:34.399> servers<00:09:35.640> and 00:09:37.030 --> 00:09:37.040 align:start position:0% somewhere in some on some servers and 00:09:37.040 --> 00:09:39.670 align:start position:0% somewhere in some on some servers and what<00:09:38.040> I<00:09:38.120> don't<00:09:38.320> know<00:09:38.720> should<00:09:38.959> be<00:09:39.079> a<00:09:39.279> problem 00:09:39.670 --> 00:09:39.680 align:start position:0% what I don't know should be a problem 00:09:39.680 --> 00:09:41.150 align:start position:0% what I don't know should be a problem maybe<00:09:39.880> it's<00:09:40.000> not<00:09:40.160> a<00:09:40.320> problem<00:09:40.640> you<00:09:40.800> believe<00:09:41.040> it 00:09:41.150 --> 00:09:41.160 align:start position:0% maybe it's not a problem you believe it 00:09:41.160 --> 00:09:42.990 align:start position:0% maybe it's not a problem you believe it is<00:09:41.800> that<00:09:42.000> microtransactions<00:09:42.720> are<00:09:42.839> not 00:09:42.990 --> 00:09:43.000 align:start position:0% is that microtransactions are not 00:09:43.000 --> 00:09:44.949 align:start position:0% is that microtransactions are not supported<00:09:43.720> when<00:09:43.880> we 00:09:44.949 --> 00:09:44.959 align:start position:0% supported when we 00:09:44.959 --> 00:09:49.190 align:start position:0% supported when we distribute<00:09:45.959> a<00:09:46.120> large<00:09:46.440> task<00:09:47.440> into<00:09:47.680> the<00:09:48.200> network 00:09:49.190 --> 00:09:49.200 align:start position:0% distribute a large task into the network 00:09:49.200 --> 00:09:52.430 align:start position:0% distribute a large task into the network it<00:09:49.399> may<00:09:50.079> be<00:09:50.640> distributed<00:09:51.240> across<00:09:51.480> a<00:09:51.920> bro 00:09:52.430 --> 00:09:52.440 align:start position:0% it may be distributed across a bro 00:09:52.440 --> 00:09:55.509 align:start position:0% it may be distributed across a bro subset<00:09:52.959> of<00:09:53.440> of<00:09:53.600> this<00:09:53.720> network<00:09:54.120> and<00:09:54.640> many 00:09:55.509 --> 00:09:55.519 align:start position:0% subset of of this network and many 00:09:55.519 --> 00:09:59.110 align:start position:0% subset of of this network and many nodes<00:09:56.519> which<00:09:56.760> may<00:09:57.040> be<00:09:57.959> well<00:09:58.279> which<00:09:58.519> is<00:09:58.720> very 00:09:59.110 --> 00:09:59.120 align:start position:0% nodes which may be well which is very 00:09:59.120 --> 00:10:01.470 align:start position:0% nodes which may be well which is very difficult<00:09:59.519> to<00:09:59.760> handle<00:10:00.120> when<00:10:00.240> you<00:10:00.360> use<00:10:01.079> paper 00:10:01.470 --> 00:10:01.480 align:start position:0% difficult to handle when you use paper 00:10:01.480 --> 00:10:05.750 align:start position:0% difficult to handle when you use paper or<00:10:01.640> similar<00:10:02.480> Solutions<00:10:03.720> and<00:10:04.720> should<00:10:05.000> be 00:10:05.750 --> 00:10:05.760 align:start position:0% or similar Solutions and should be 00:10:05.760 --> 00:10:09.150 align:start position:0% or similar Solutions and should be relatively<00:10:06.760> difficult<00:10:07.079> to<00:10:08.079> implement<00:10:08.839> with 00:10:09.150 --> 00:10:09.160 align:start position:0% relatively difficult to implement with 00:10:09.160 --> 00:10:10.430 align:start position:0% relatively difficult to implement with Bitcoin<00:10:09.600> for 00:10:10.430 --> 00:10:10.440 align:start position:0% Bitcoin for 00:10:10.440 --> 00:10:13.790 align:start position:0% Bitcoin for example<00:10:11.440> I<00:10:11.600> don't<00:10:11.880> know<00:10:12.240> what's<00:10:12.519> the<00:10:12.680> scale 00:10:13.790 --> 00:10:13.800 align:start position:0% example I don't know what's the scale 00:10:13.800 --> 00:10:16.030 align:start position:0% example I don't know what's the scale of<00:10:14.800> supported<00:10:15.360> granularity<00:10:15.880> of 00:10:16.030 --> 00:10:16.040 align:start position:0% of supported granularity of 00:10:16.040 --> 00:10:17.990 align:start position:0% of supported granularity of microtransactions<00:10:16.800> in<00:10:16.959> ethereum<00:10:17.680> what<00:10:17.800> is 00:10:17.990 --> 00:10:18.000 align:start position:0% microtransactions in ethereum what is 00:10:18.000 --> 00:10:20.750 align:start position:0% microtransactions in ethereum what is going<00:10:18.200> to<00:10:18.560> be<00:10:19.560> but<00:10:19.720> I<00:10:19.839> believe<00:10:20.160> that<00:10:20.360> it<00:10:20.560> might 00:10:20.750 --> 00:10:20.760 align:start position:0% going to be but I believe that it might 00:10:20.760 --> 00:10:23.870 align:start position:0% going to be but I believe that it might be<00:10:21.680> much<00:10:21.959> better<00:10:22.279> than<00:10:22.600> the<00:10:22.720> current 00:10:23.870 --> 00:10:23.880 align:start position:0% be much better than the current 00:10:23.880 --> 00:10:25.870 align:start position:0% be much better than the current Solutions<00:10:24.880> we<00:10:25.000> wouldn't<00:10:25.279> like<00:10:25.399> to<00:10:25.519> flood 00:10:25.870 --> 00:10:25.880 align:start position:0% Solutions we wouldn't like to flood 00:10:25.880 --> 00:10:28.310 align:start position:0% Solutions we wouldn't like to flood ethereum<00:10:26.399> with 00:10:28.310 --> 00:10:28.320 align:start position:0% ethereum with 00:10:28.320 --> 00:10:31.389 align:start position:0% ethereum with microtransactions<00:10:29.320> so<00:10:29.640> we<00:10:30.640> at<00:10:30.800> some<00:10:31.000> point<00:10:31.200> we 00:10:31.389 --> 00:10:31.399 align:start position:0% microtransactions so we at some point we 00:10:31.399 --> 00:10:35.230 align:start position:0% microtransactions so we at some point we have<00:10:31.519> to<00:10:31.959> decide<00:10:32.959> what<00:10:33.079> is<00:10:33.200> the<00:10:33.680> level<00:10:34.680> uh<00:10:35.079> at 00:10:35.230 --> 00:10:35.240 align:start position:0% have to decide what is the level uh at 00:10:35.240 --> 00:10:37.470 align:start position:0% have to decide what is the level uh at which<00:10:35.399> we<00:10:35.560> can<00:10:36.399> process<00:10:36.800> transactions 00:10:37.470 --> 00:10:37.480 align:start position:0% which we can process transactions 00:10:37.480 --> 00:10:40.190 align:start position:0% which we can process transactions because<00:10:38.360> if<00:10:38.519> it<00:10:38.800> works<00:10:39.079> out<00:10:39.279> then<00:10:39.440> it<00:10:39.560> may<00:10:39.720> be 00:10:40.190 --> 00:10:40.200 align:start position:0% because if it works out then it may be 00:10:40.200 --> 00:10:42.389 align:start position:0% because if it works out then it may be thousands<00:10:41.200> hundreds<00:10:41.480> of<00:10:41.639> thousands<00:10:41.920> a<00:10:42.079> second 00:10:42.389 --> 00:10:42.399 align:start position:0% thousands hundreds of thousands a second 00:10:42.399 --> 00:10:47.750 align:start position:0% thousands hundreds of thousands a second so<00:10:43.000> that<00:10:43.120> wouldn't<00:10:43.440> be<00:10:43.600> feasible<00:10:44.440> I 00:10:47.750 --> 00:10:47.760 align:start position:0% 00:10:47.760 --> 00:10:51.069 align:start position:0% suppose<00:10:48.760> that's<00:10:49.000> the<00:10:49.200> another<00:10:50.200> well<00:10:50.800> it's<00:10:50.920> not 00:10:51.069 --> 00:10:51.079 align:start position:0% suppose that's the another well it's not 00:10:51.079 --> 00:10:53.910 align:start position:0% suppose that's the another well it's not in<00:10:51.560> groundbreaking<00:10:52.560> neither<00:10:52.839> in<00:10:52.959> terms<00:10:53.320> of 00:10:53.910 --> 00:10:53.920 align:start position:0% in groundbreaking neither in terms of 00:10:53.920 --> 00:10:57.310 align:start position:0% in groundbreaking neither in terms of the<00:10:54.279> idea<00:10:55.279> well<00:10:55.760> although<00:10:56.440> putting<00:10:56.839> it<00:10:57.000> all 00:10:57.310 --> 00:10:57.320 align:start position:0% the idea well although putting it all 00:10:57.320 --> 00:11:00.110 align:start position:0% the idea well although putting it all together<00:10:57.600> is<00:10:57.880> seem<00:10:58.160> to<00:10:58.279> be<00:10:58.440> pretty<00:10:58.880> difficult 00:11:00.110 --> 00:11:00.120 align:start position:0% together is seem to be pretty difficult 00:11:00.120 --> 00:11:03.750 align:start position:0% together is seem to be pretty difficult and<00:11:00.639> in<00:11:00.760> terms<00:11:01.079> of<00:11:01.360> iter<00:11:01.760> contracts<00:11:02.200> it's<00:11:02.760> just 00:11:03.750 --> 00:11:03.760 align:start position:0% and in terms of iter contracts it's just 00:11:03.760 --> 00:11:05.389 align:start position:0% and in terms of iter contracts it's just I<00:11:03.839> don't<00:11:04.000> know 00:11:05.389 --> 00:11:05.399 align:start position:0% I don't know 00:11:05.399 --> 00:11:08.470 align:start position:0% I don't know vanilla<00:11:06.399> implementation<00:11:07.120> of<00:11:08.120> common 00:11:08.470 --> 00:11:08.480 align:start position:0% vanilla implementation of common 00:11:08.480 --> 00:11:10.990 align:start position:0% vanilla implementation of common contract<00:11:08.920> that<00:11:09.079> should<00:11:10.079> take<00:11:10.320> place<00:11:10.560> in 00:11:10.990 --> 00:11:11.000 align:start position:0% contract that should take place in 00:11:11.000 --> 00:11:14.030 align:start position:0% contract that should take place in etherum<00:11:12.000> it's<00:11:12.519> just<00:11:12.959> used 00:11:14.030 --> 00:11:14.040 align:start position:0% etherum it's just used 00:11:14.040 --> 00:11:17.350 align:start position:0% etherum it's just used to<00:11:15.040> uh<00:11:15.320> transfer<00:11:15.800> value<00:11:16.639> between 00:11:17.350 --> 00:11:17.360 align:start position:0% to uh transfer value between 00:11:17.360 --> 00:11:19.190 align:start position:0% to uh transfer value between participating<00:11:18.000> nodes<00:11:18.399> simple<00:11:18.760> contract<00:11:19.079> is 00:11:19.190 --> 00:11:19.200 align:start position:0% participating nodes simple contract is 00:11:19.200 --> 00:11:21.949 align:start position:0% participating nodes simple contract is as<00:11:19.320> a<00:11:19.440> contract<00:11:19.720> between<00:11:19.959> two<00:11:20.120> nodes<00:11:20.560> one<00:11:21.560> that 00:11:21.949 --> 00:11:21.959 align:start position:0% as a contract between two nodes one that 00:11:21.959 --> 00:11:23.829 align:start position:0% as a contract between two nodes one that distributes<00:11:22.480> task<00:11:22.760> and<00:11:22.959> the<00:11:23.040> other<00:11:23.480> that 00:11:23.829 --> 00:11:23.839 align:start position:0% distributes task and the other that 00:11:23.839 --> 00:11:26.629 align:start position:0% distributes task and the other that provides<00:11:24.240> some<00:11:24.800> resources<00:11:25.800> for<00:11:26.000> example 00:11:26.629 --> 00:11:26.639 align:start position:0% provides some resources for example 00:11:26.639 --> 00:11:28.949 align:start position:0% provides some resources for example computational<00:11:27.320> power<00:11:28.320> uh<00:11:28.440> software<00:11:28.800> as<00:11:28.880> a 00:11:28.949 --> 00:11:28.959 align:start position:0% computational power uh software as a 00:11:28.959 --> 00:11:30.949 align:start position:0% computational power uh software as a service<00:11:29.440> contracts<00:11:30.000> may<00:11:30.240> involve<00:11:30.600> another 00:11:30.949 --> 00:11:30.959 align:start position:0% service contracts may involve another 00:11:30.959 --> 00:11:33.190 align:start position:0% service contracts may involve another parties<00:11:31.480> for<00:11:31.680> example<00:11:32.279> programmers<00:11:32.880> who 00:11:33.190 --> 00:11:33.200 align:start position:0% parties for example programmers who 00:11:33.200 --> 00:11:36.509 align:start position:0% parties for example programmers who provide<00:11:33.839> their<00:11:34.120> parts<00:11:34.320> of<00:11:34.519> code<00:11:35.360> or<00:11:35.959> in<00:11:36.360> case 00:11:36.509 --> 00:11:36.519 align:start position:0% provide their parts of code or in case 00:11:36.519 --> 00:11:38.710 align:start position:0% provide their parts of code or in case of<00:11:36.680> renderers<00:11:37.519> companies<00:11:38.040> that<00:11:38.399> may 00:11:38.710 --> 00:11:38.720 align:start position:0% of renderers companies that may 00:11:38.720 --> 00:11:41.190 align:start position:0% of renderers companies that may distribute<00:11:39.160> their<00:11:39.320> rendering<00:11:39.800> engines<00:11:40.800> so 00:11:41.190 --> 00:11:41.200 align:start position:0% distribute their rendering engines so 00:11:41.200 --> 00:11:44.190 align:start position:0% distribute their rendering engines so that<00:11:42.200> that<00:11:42.720> that<00:11:42.920> company<00:11:43.240> or<00:11:43.480> person<00:11:43.880> also 00:11:44.190 --> 00:11:44.200 align:start position:0% that that that company or person also 00:11:44.200 --> 00:11:47.509 align:start position:0% that that that company or person also gets<00:11:44.880> remuneration<00:11:45.720> for<00:11:46.240> providing<00:11:46.959> solution 00:11:47.509 --> 00:11:47.519 align:start position:0% gets remuneration for providing solution 00:11:47.519 --> 00:11:49.670 align:start position:0% gets remuneration for providing solution and<00:11:47.720> time<00:11:47.920> dependent<00:11:48.320> contracts<00:11:48.760> for<00:11:48.880> example 00:11:49.670 --> 00:11:49.680 align:start position:0% and time dependent contracts for example 00:11:49.680 --> 00:11:51.389 align:start position:0% and time dependent contracts for example when<00:11:49.800> you<00:11:49.880> would<00:11:50.040> like<00:11:50.160> to<00:11:50.399> H<00:11:50.639> host<00:11:50.920> something 00:11:51.389 --> 00:11:51.399 align:start position:0% when you would like to H host something 00:11:51.399 --> 00:11:57.269 align:start position:0% when you would like to H host something for<00:11:51.600> some<00:11:52.160> time<00:11:53.160> and<00:11:54.160> we<00:11:54.360> have<00:11:54.760> to<00:11:55.760> pay<00:11:56.720> in 00:11:57.269 --> 00:11:57.279 align:start position:0% for some time and we have to pay in 00:11:57.279 --> 00:12:02.829 align:start position:0% for some time and we have to pay in timely<00:11:57.680> fashion<00:11:58.240> or<00:11:59.279> for 00:12:02.829 --> 00:12:02.839 align:start position:0% 00:12:02.839 --> 00:12:04.470 align:start position:0% hosting 00:12:04.470 --> 00:12:04.480 align:start position:0% hosting 00:12:04.480 --> 00:12:07.629 align:start position:0% hosting so<00:12:05.480> from<00:12:05.680> our<00:12:06.200> perspective<00:12:07.200> this<00:12:07.320> is<00:12:07.399> how<00:12:07.519> it 00:12:07.629 --> 00:12:07.639 align:start position:0% so from our perspective this is how it 00:12:07.639 --> 00:12:10.269 align:start position:0% so from our perspective this is how it looks<00:12:08.120> Golem<00:12:08.399> andum<00:12:08.880> are<00:12:09.040> independent 00:12:10.269 --> 00:12:10.279 align:start position:0% looks Golem andum are independent 00:12:10.279 --> 00:12:13.829 align:start position:0% looks Golem andum are independent Solutions<00:12:11.279> but<00:12:11.680> to<00:12:11.920> make<00:12:12.519> Golem<00:12:13.519> really 00:12:13.829 --> 00:12:13.839 align:start position:0% Solutions but to make Golem really 00:12:13.839 --> 00:12:17.350 align:start position:0% Solutions but to make Golem really attractive<00:12:14.560> you<00:12:14.800> have<00:12:14.920> to<00:12:15.040> be<00:12:15.480> fully 00:12:17.350 --> 00:12:17.360 align:start position:0% attractive you have to be fully 00:12:17.360 --> 00:12:19.990 align:start position:0% attractive you have to be fully decentralized<00:12:18.360> and<00:12:19.120> well<00:12:19.360> most<00:12:19.800> more 00:12:19.990 --> 00:12:20.000 align:start position:0% decentralized and well most more 00:12:20.000 --> 00:12:21.790 align:start position:0% decentralized and well most more important<00:12:20.519> easy<00:12:20.760> to<00:12:20.959> use<00:12:21.199> and<00:12:21.360> easy<00:12:21.560> to 00:12:21.790 --> 00:12:21.800 align:start position:0% important easy to use and easy to 00:12:21.800 --> 00:12:23.990 align:start position:0% important easy to use and easy to install 00:12:23.990 --> 00:12:24.000 align:start position:0% install 00:12:24.000 --> 00:12:27.470 align:start position:0% install so<00:12:25.000> forcing<00:12:25.480> users<00:12:25.839> to<00:12:26.120> give<00:12:26.279> out 00:12:27.470 --> 00:12:27.480 align:start position:0% so forcing users to give out 00:12:27.480 --> 00:12:29.710 align:start position:0% so forcing users to give out their<00:12:28.480> data 00:12:29.710 --> 00:12:29.720 align:start position:0% their data 00:12:29.720 --> 00:12:33.870 align:start position:0% their data credit<00:12:30.040> card<00:12:30.279> data<00:12:30.519> for<00:12:31.120> example<00:12:32.120> uh<00:12:32.880> doesn't 00:12:33.870 --> 00:12:33.880 align:start position:0% credit card data for example uh doesn't 00:12:33.880 --> 00:12:36.069 align:start position:0% credit card data for example uh doesn't seem<00:12:34.120> to<00:12:34.320> make<00:12:34.519> any<00:12:34.720> sense<00:12:35.279> well<00:12:35.760> at<00:12:35.880> least 00:12:36.069 --> 00:12:36.079 align:start position:0% seem to make any sense well at least 00:12:36.079 --> 00:12:39.150 align:start position:0% seem to make any sense well at least much<00:12:36.360> sense<00:12:37.040> existing<00:12:37.440> Solutions<00:12:38.399> requires 00:12:39.150 --> 00:12:39.160 align:start position:0% much sense existing Solutions requires 00:12:39.160 --> 00:12:40.790 align:start position:0% much sense existing Solutions requires such<00:12:39.399> registration 00:12:40.790 --> 00:12:40.800 align:start position:0% such registration 00:12:40.800 --> 00:12:44.509 align:start position:0% such registration and<00:12:41.800> they<00:12:42.000> doesn't<00:12:42.320> seem<00:12:42.560> to<00:12:43.199> make<00:12:44.199> uh<00:12:44.320> a 00:12:44.509 --> 00:12:44.519 align:start position:0% and they doesn't seem to make uh a 00:12:44.519 --> 00:12:46.750 align:start position:0% and they doesn't seem to make uh a success<00:12:45.160> with<00:12:45.320> this<00:12:45.560> attemp 00:12:46.750 --> 00:12:46.760 align:start position:0% success with this attemp 00:12:46.760 --> 00:12:49.750 align:start position:0% success with this attemp approach<00:12:47.760> and<00:12:48.120> as<00:12:48.279> for<00:12:48.480> ethereum<00:12:49.480> I<00:12:49.560> don't 00:12:49.750 --> 00:12:49.760 align:start position:0% approach and as for ethereum I don't 00:12:49.760 --> 00:12:53.069 align:start position:0% approach and as for ethereum I don't know<00:12:50.279> this<00:12:50.360> is<00:12:50.519> just<00:12:50.680> a<00:12:50.920> guess<00:12:51.920> but<00:12:52.600> it's<00:12:52.800> quite 00:12:53.069 --> 00:12:53.079 align:start position:0% know this is just a guess but it's quite 00:12:53.079 --> 00:12:55.629 align:start position:0% know this is just a guess but it's quite possible<00:12:53.560> that<00:12:54.399> that<00:12:54.760> software<00:12:55.120> as<00:12:55.240> a<00:12:55.320> service 00:12:55.629 --> 00:12:55.639 align:start position:0% possible that that software as a service 00:12:55.639 --> 00:12:59.269 align:start position:0% possible that that software as a service approach<00:12:56.000> May<00:12:56.600> attract<00:12:57.600> more<00:12:58.240> programmers<00:12:59.160> to 00:12:59.269 --> 00:12:59.279 align:start position:0% approach May attract more programmers to 00:12:59.279 --> 00:13:01.990 align:start position:0% approach May attract more programmers to our<00:12:59.600> eum<00:13:00.600> I<00:13:00.680> cannot<00:13:00.959> guarantee<00:13:01.360> that<00:13:01.560> but<00:13:01.800> it 00:13:01.990 --> 00:13:02.000 align:start position:0% our eum I cannot guarantee that but it 00:13:02.000 --> 00:13:03.110 align:start position:0% our eum I cannot guarantee that but it seems 00:13:03.110 --> 00:13:03.120 align:start position:0% seems 00:13:03.120 --> 00:13:05.710 align:start position:0% seems reasonable<00:13:04.120> and<00:13:04.560> that's<00:13:04.720> how<00:13:04.839> it<00:13:04.959> looks<00:13:05.440> if 00:13:05.710 --> 00:13:05.720 align:start position:0% reasonable and that's how it looks if 00:13:05.720 --> 00:13:08.750 align:start position:0% reasonable and that's how it looks if you<00:13:06.000> just<00:13:06.560> if<00:13:06.639> you're<00:13:06.800> not<00:13:06.959> Bor<00:13:07.639> with<00:13:07.800> it<00:13:08.480> I<00:13:08.560> can 00:13:08.750 --> 00:13:08.760 align:start position:0% you just if you're not Bor with it I can 00:13:08.760 --> 00:13:11.470 align:start position:0% you just if you're not Bor with it I can show<00:13:09.000> you<00:13:09.240> how<00:13:09.519> the<00:13:10.480> graphic<00:13:10.839> outline<00:13:11.240> of<00:13:11.360> the 00:13:11.470 --> 00:13:11.480 align:start position:0% show you how the graphic outline of the 00:13:11.480 --> 00:13:14.350 align:start position:0% show you how the graphic outline of the system<00:13:11.760> looks<00:13:12.519> like 00:13:14.350 --> 00:13:14.360 align:start position:0% system looks like 00:13:14.360 --> 00:13:16.790 align:start position:0% system looks like y 00:13:16.790 --> 00:13:16.800 align:start position:0% y 00:13:16.800 --> 00:13:20.350 align:start position:0% y so<00:13:17.800> it's<00:13:18.160> it's<00:13:18.320> not<00:13:18.680> that<00:13:19.240> complicated<00:13:19.839> but 00:13:20.350 --> 00:13:20.360 align:start position:0% so it's it's not that complicated but 00:13:20.360 --> 00:13:24.350 align:start position:0% so it's it's not that complicated but it's<00:13:20.519> not<00:13:20.760> easy<00:13:21.440> as<00:13:21.839> well<00:13:22.839> I<00:13:22.959> don't<00:13:23.160> know<00:13:24.160> if 00:13:24.350 --> 00:13:24.360 align:start position:0% it's not easy as well I don't know if 00:13:24.360 --> 00:13:26.470 align:start position:0% it's not easy as well I don't know if there<00:13:24.480> is<00:13:25.040> anything<00:13:25.560> similar<00:13:25.880> to<00:13:26.000> ethereum 00:13:26.470 --> 00:13:26.480 align:start position:0% there is anything similar to ethereum 00:13:26.480 --> 00:13:31.470 align:start position:0% there is anything similar to ethereum but<00:13:27.320> we<00:13:27.480> need<00:13:28.360> a<00:13:28.560> solid<00:13:28.880> p<00:13:29.199> top<00:13:30.199> layer<00:13:30.519> build<00:13:31.279> on 00:13:31.470 --> 00:13:31.480 align:start position:0% but we need a solid p top layer build on 00:13:31.480 --> 00:13:34.550 align:start position:0% but we need a solid p top layer build on top<00:13:31.639> of<00:13:31.720> some<00:13:31.880> transport<00:13:32.760> layer<00:13:33.760> uh<00:13:33.880> we<00:13:34.000> need 00:13:34.550 --> 00:13:34.560 align:start position:0% top of some transport layer uh we need 00:13:34.560 --> 00:13:37.430 align:start position:0% top of some transport layer uh we need network<00:13:35.040> adapter<00:13:36.040> to 00:13:37.430 --> 00:13:37.440 align:start position:0% network adapter to 00:13:37.440 --> 00:13:40.710 align:start position:0% network adapter to provide<00:13:38.440> resource<00:13:38.880> management<00:13:39.519> and<00:13:40.519> the 00:13:40.710 --> 00:13:40.720 align:start position:0% provide resource management and the 00:13:40.720 --> 00:13:43.189 align:start position:0% provide resource management and the global<00:13:41.120> IO<00:13:41.760> that<00:13:41.880> would<00:13:42.120> example<00:13:42.839> that<00:13:42.959> would 00:13:43.189 --> 00:13:43.199 align:start position:0% global IO that would example that would 00:13:43.199 --> 00:13:45.949 align:start position:0% global IO that would example that would allow<00:13:43.760> nodes<00:13:44.199> to<00:13:44.600> read<00:13:44.959> and<00:13:45.160> right 00:13:45.949 --> 00:13:45.959 align:start position:0% allow nodes to read and right 00:13:45.959 --> 00:13:49.629 align:start position:0% allow nodes to read and right data<00:13:46.959> in<00:13:47.240> a<00:13:47.440> safe<00:13:47.760> fashion<00:13:48.480> it<00:13:48.680> has<00:13:48.839> to<00:13:49.000> be 00:13:49.629 --> 00:13:49.639 align:start position:0% data in a safe fashion it has to be 00:13:49.639 --> 00:13:53.310 align:start position:0% data in a safe fashion it has to be really<00:13:49.880> well<00:13:50.120> took<00:13:50.399> over<00:13:50.920> and<00:13:52.320> implemented 00:13:53.310 --> 00:13:53.320 align:start position:0% really well took over and implemented 00:13:53.320 --> 00:13:55.829 align:start position:0% really well took over and implemented task<00:13:53.680> protocol<00:13:54.120> is<00:13:54.720> protocol<00:13:55.320> responsible 00:13:55.829 --> 00:13:55.839 align:start position:0% task protocol is protocol responsible 00:13:55.839 --> 00:13:58.150 align:start position:0% task protocol is protocol responsible for<00:13:56.399> Distributing<00:13:57.120> task<00:13:57.480> across<00:13:57.720> the<00:13:57.800> network 00:13:58.150 --> 00:13:58.160 align:start position:0% for Distributing task across the network 00:13:58.160 --> 00:14:02.110 align:start position:0% for Distributing task across the network and<00:13:59.079> gaing<00:13:59.399> the<00:14:00.000> results<00:14:01.000> as<00:14:01.160> well<00:14:01.399> as 00:14:02.110 --> 00:14:02.120 align:start position:0% and gaing the results as well as 00:14:02.120 --> 00:14:04.150 align:start position:0% and gaing the results as well as connecting<00:14:02.560> it<00:14:02.720> with<00:14:02.920> a<00:14:03.079> transaction<00:14:03.560> system 00:14:04.150 --> 00:14:04.160 align:start position:0% connecting it with a transaction system 00:14:04.160 --> 00:14:05.710 align:start position:0% connecting it with a transaction system that's<00:14:04.320> a<00:14:04.480> payment 00:14:05.710 --> 00:14:05.720 align:start position:0% that's a payment 00:14:05.720 --> 00:14:09.350 align:start position:0% that's a payment system<00:14:06.720> and<00:14:06.920> that's<00:14:07.480> this<00:14:07.800> layer<00:14:08.800> is<00:14:09.079> all 00:14:09.350 --> 00:14:09.360 align:start position:0% system and that's this layer is all 00:14:09.360 --> 00:14:11.749 align:start position:0% system and that's this layer is all about<00:14:10.160> the<00:14:10.360> peer<00:14:10.560> top 00:14:11.749 --> 00:14:11.759 align:start position:0% about the peer top 00:14:11.759 --> 00:14:16.509 align:start position:0% about the peer top Network 00:14:16.509 --> 00:14:16.519 align:start position:0% 00:14:16.519 --> 00:14:20.670 align:start position:0% sorry<00:14:17.519> the<00:14:17.639> upper<00:14:17.959> layer<00:14:18.279> is<00:14:18.680> a<00:14:19.680> client 00:14:20.670 --> 00:14:20.680 align:start position:0% sorry the upper layer is a client 00:14:20.680 --> 00:14:23.069 align:start position:0% sorry the upper layer is a client layer<00:14:21.680> the<00:14:21.839> center<00:14:22.199> integration<00:14:22.680> component 00:14:23.069 --> 00:14:23.079 align:start position:0% layer the center integration component 00:14:23.079 --> 00:14:25.310 align:start position:0% layer the center integration component was<00:14:23.240> called<00:14:23.440> the<00:14:23.720> client 00:14:25.310 --> 00:14:25.320 align:start position:0% was called the client 00:14:25.320 --> 00:14:27.749 align:start position:0% was called the client before<00:14:26.320> and<00:14:26.440> it's<00:14:26.680> responsible<00:14:27.120> for<00:14:27.320> defining 00:14:27.749 --> 00:14:27.759 align:start position:0% before and it's responsible for defining 00:14:27.759 --> 00:14:30.509 align:start position:0% before and it's responsible for defining tasks<00:14:28.240> and 00:14:30.509 --> 00:14:30.519 align:start position:0% tasks and 00:14:30.519 --> 00:14:32.629 align:start position:0% tasks and put<00:14:31.160> passing<00:14:31.560> them<00:14:31.720> to<00:14:31.880> the<00:14:32.000> layer<00:14:32.440> that 00:14:32.629 --> 00:14:32.639 align:start position:0% put passing them to the layer that 00:14:32.639 --> 00:14:34.509 align:start position:0% put passing them to the layer that that's<00:14:32.839> responsible<00:14:33.279> for<00:14:33.440> computation<00:14:34.360> we 00:14:34.509 --> 00:14:34.519 align:start position:0% that's responsible for computation we 00:14:34.519 --> 00:14:38.430 align:start position:0% that's responsible for computation we can<00:14:35.440> below<00:14:35.839> this<00:14:36.040> line<00:14:36.880> we<00:14:37.079> can<00:14:37.680> test<00:14:37.959> it<00:14:38.240> just 00:14:38.430 --> 00:14:38.440 align:start position:0% can below this line we can test it just 00:14:38.440 --> 00:14:42.470 align:start position:0% can below this line we can test it just on<00:14:38.600> a<00:14:39.480> single<00:14:39.880> machine<00:14:40.759> running<00:14:41.160> the<00:14:41.360> task<00:14:42.320> on 00:14:42.470 --> 00:14:42.480 align:start position:0% on a single machine running the task on 00:14:42.480 --> 00:14:45.430 align:start position:0% on a single machine running the task on a<00:14:42.600> few<00:14:42.839> processes<00:14:43.240> or<00:14:43.360> even<00:14:43.880> threads<00:14:44.880> so 00:14:45.430 --> 00:14:45.440 align:start position:0% a few processes or even threads so 00:14:45.440 --> 00:14:47.990 align:start position:0% a few processes or even threads so that's<00:14:45.680> good<00:14:45.839> for<00:14:46.040> testing<00:14:46.800> purposes<00:14:47.800> as<00:14:47.920> you 00:14:47.990 --> 00:14:48.000 align:start position:0% that's good for testing purposes as you 00:14:48.000 --> 00:14:49.949 align:start position:0% that's good for testing purposes as you can<00:14:48.120> see<00:14:48.279> there's<00:14:48.519> virtual<00:14:48.839> machine<00:14:49.240> that<00:14:49.759> is 00:14:49.949 --> 00:14:49.959 align:start position:0% can see there's virtual machine that is 00:14:49.959 --> 00:14:53.509 align:start position:0% can see there's virtual machine that is separated<00:14:50.440> by<00:14:50.839> another<00:14:52.160> border<00:14:53.160> because<00:14:53.399> we 00:14:53.509 --> 00:14:53.519 align:start position:0% separated by another border because we 00:14:53.519 --> 00:14:55.910 align:start position:0% separated by another border because we don't<00:14:53.759> want<00:14:53.959> to<00:14:54.880> give<00:14:55.199> direct<00:14:55.519> access<00:14:55.759> from 00:14:55.910 --> 00:14:55.920 align:start position:0% don't want to give direct access from 00:14:55.920 --> 00:14:59.829 align:start position:0% don't want to give direct access from the<00:14:56.040> virtual<00:14:56.360> machine<00:14:57.120> to<00:14:58.120> uh<00:14:58.279> external<00:14:58.720> world 00:14:59.829 --> 00:14:59.839 align:start position:0% the virtual machine to uh external world 00:14:59.839 --> 00:15:02.069 align:start position:0% the virtual machine to uh external world especially<00:15:00.279> we<00:15:00.399> wouldn't<00:15:00.720> like<00:15:00.920> to<00:15:01.320> allow 00:15:02.069 --> 00:15:02.079 align:start position:0% especially we wouldn't like to allow 00:15:02.079 --> 00:15:04.389 align:start position:0% especially we wouldn't like to allow processes<00:15:03.000> that<00:15:03.160> might<00:15:03.360> be<00:15:03.759> written<00:15:04.199> by 00:15:04.389 --> 00:15:04.399 align:start position:0% processes that might be written by 00:15:04.399 --> 00:15:08.389 align:start position:0% processes that might be written by someone<00:15:04.839> to<00:15:05.839> connect<00:15:06.279> with<00:15:07.160> any<00:15:07.920> computer<00:15:08.279> in 00:15:08.389 --> 00:15:08.399 align:start position:0% someone to connect with any computer in 00:15:08.399 --> 00:15:09.350 align:start position:0% someone to connect with any computer in the 00:15:09.350 --> 00:15:09.360 align:start position:0% the 00:15:09.360 --> 00:15:11.310 align:start position:0% the network<00:15:10.360> above<00:15:10.639> that<00:15:10.800> we<00:15:10.920> have<00:15:11.079> task 00:15:11.310 --> 00:15:11.320 align:start position:0% network above that we have task 00:15:11.320 --> 00:15:13.749 align:start position:0% network above that we have task definition<00:15:11.639> framework<00:15:12.120> which<00:15:12.560> describes<00:15:13.560> in 00:15:13.749 --> 00:15:13.759 align:start position:0% definition framework which describes in 00:15:13.759 --> 00:15:14.790 align:start position:0% definition framework which describes in detail<00:15:14.079> how 00:15:14.790 --> 00:15:14.800 align:start position:0% detail how 00:15:14.800 --> 00:15:18.710 align:start position:0% detail how tasks<00:15:15.800> are<00:15:16.160> specify<00:15:16.839> yeah<00:15:17.720> so<00:15:18.000> you<00:15:18.199> say<00:15:18.560> that 00:15:18.710 --> 00:15:18.720 align:start position:0% tasks are specify yeah so you say that 00:15:18.720 --> 00:15:20.030 align:start position:0% tasks are specify yeah so you say that the<00:15:18.880> individual 00:15:20.030 --> 00:15:20.040 align:start position:0% the individual 00:15:20.040 --> 00:15:22.269 align:start position:0% the individual instances<00:15:21.040> uh<00:15:21.199> cannot<00:15:21.600> connect<00:15:21.880> to<00:15:22.079> each 00:15:22.269 --> 00:15:22.279 align:start position:0% instances uh cannot connect to each 00:15:22.279 --> 00:15:24.870 align:start position:0% instances uh cannot connect to each other<00:15:23.279> so<00:15:23.519> there<00:15:23.600> are<00:15:23.800> no<00:15:23.920> shared<00:15:24.320> resources 00:15:24.870 --> 00:15:24.880 align:start position:0% other so there are no shared resources 00:15:24.880 --> 00:15:27.069 align:start position:0% other so there are no shared resources so<00:15:25.079> the<00:15:25.440> there<00:15:25.560> are<00:15:25.680> shared<00:15:26.000> resources<00:15:26.560> but 00:15:27.069 --> 00:15:27.079 align:start position:0% so the there are shared resources but 00:15:27.079 --> 00:15:29.550 align:start position:0% so the there are shared resources but well<00:15:27.920> I<00:15:28.040> didn't 00:15:29.550 --> 00:15:29.560 align:start position:0% well I didn't 00:15:29.560 --> 00:15:32.069 align:start position:0% well I didn't tell<00:15:29.839> that<00:15:30.399> explicitly<00:15:31.399> the<00:15:31.560> code<00:15:31.800> that<00:15:31.920> is 00:15:32.069 --> 00:15:32.079 align:start position:0% tell that explicitly the code that is 00:15:32.079 --> 00:15:34.790 align:start position:0% tell that explicitly the code that is run<00:15:32.440> is<00:15:33.000> just<00:15:33.240> about<00:15:33.519> any<00:15:33.680> code<00:15:33.880> you<00:15:33.959> can<00:15:34.160> write 00:15:34.790 --> 00:15:34.800 align:start position:0% run is just about any code you can write 00:15:34.800 --> 00:15:39.829 align:start position:0% run is just about any code you can write that<00:15:34.920> we<00:15:35.040> can<00:15:35.480> share<00:15:36.600> but<00:15:37.600> we<00:15:38.360> explicitly<00:15:39.000> have 00:15:39.829 --> 00:15:39.839 align:start position:0% that we can share but we explicitly have 00:15:39.839 --> 00:15:42.430 align:start position:0% that we can share but we explicitly have to<00:15:40.839> point<00:15:41.240> which<00:15:41.440> resources<00:15:42.040> should<00:15:42.240> be 00:15:42.430 --> 00:15:42.440 align:start position:0% to point which resources should be 00:15:42.440 --> 00:15:45.590 align:start position:0% to point which resources should be shared<00:15:43.440> because<00:15:43.800> we<00:15:43.959> can<00:15:44.199> for<00:15:44.399> example<00:15:45.160> try<00:15:45.399> to 00:15:45.590 --> 00:15:45.600 align:start position:0% shared because we can for example try to 00:15:45.600 --> 00:15:48.030 align:start position:0% shared because we can for example try to download<00:15:46.600> some<00:15:46.839> data<00:15:47.079> from<00:15:47.199> a 00:15:48.030 --> 00:15:48.040 align:start position:0% download some data from a 00:15:48.040 --> 00:15:51.110 align:start position:0% download some data from a server<00:15:49.160> and<00:15:50.160> that's<00:15:50.360> not<00:15:50.519> a<00:15:50.680> problem<00:15:50.920> if<00:15:51.040> you 00:15:51.110 --> 00:15:51.120 align:start position:0% server and that's not a problem if you 00:15:51.120 --> 00:15:52.790 align:start position:0% server and that's not a problem if you do<00:15:51.279> it<00:15:51.360> with<00:15:51.519> one<00:15:51.680> note<00:15:52.079> but<00:15:52.199> when<00:15:52.319> you<00:15:52.440> said 00:15:52.790 --> 00:15:52.800 align:start position:0% do it with one note but when you said 00:15:52.800 --> 00:15:54.949 align:start position:0% do it with one note but when you said distribute<00:15:53.240> it<00:15:53.319> over<00:15:53.480> the<00:15:53.639> network<00:15:54.000> and<00:15:54.720> every 00:15:54.949 --> 00:15:54.959 align:start position:0% distribute it over the network and every 00:15:54.959 --> 00:15:57.710 align:start position:0% distribute it over the network and every node<00:15:55.759> downloads<00:15:56.199> the<00:15:56.279> same<00:15:56.519> data<00:15:57.360> that<00:15:57.480> may<00:15:57.600> be 00:15:57.710 --> 00:15:57.720 align:start position:0% node downloads the same data that may be 00:15:57.720 --> 00:15:59.470 align:start position:0% node downloads the same data that may be a<00:15:57.839> threat<00:15:58.079> to<00:15:58.199> the<00:15:58.319> server 00:15:59.470 --> 00:15:59.480 align:start position:0% a threat to the server 00:15:59.480 --> 00:16:03.550 align:start position:0% a threat to the server so<00:16:00.040> in<00:16:00.240> this<00:16:00.399> case<00:16:00.639> we<00:16:00.720> can<00:16:00.959> simply<00:16:02.240> force<00:16:03.240> uh 00:16:03.550 --> 00:16:03.560 align:start position:0% so in this case we can simply force uh 00:16:03.560 --> 00:16:06.350 align:start position:0% so in this case we can simply force uh the<00:16:03.680> node<00:16:04.040> that<00:16:04.399> distributor<00:16:05.000> task<00:16:05.360> to 00:16:06.350 --> 00:16:06.360 align:start position:0% the node that distributor task to 00:16:06.360 --> 00:16:08.470 align:start position:0% the node that distributor task to download<00:16:06.720> the<00:16:06.880> data<00:16:07.519> and<00:16:07.759> then<00:16:08.160> just 00:16:08.470 --> 00:16:08.480 align:start position:0% download the data and then just 00:16:08.480 --> 00:16:10.629 align:start position:0% download the data and then just distribute<00:16:08.920> the<00:16:09.079> downloaded<00:16:09.600> data<00:16:10.360> to 00:16:10.629 --> 00:16:10.639 align:start position:0% distribute the downloaded data to 00:16:10.639 --> 00:16:12.389 align:start position:0% distribute the downloaded data to Computing 00:16:12.389 --> 00:16:12.399 align:start position:0% Computing 00:16:12.399 --> 00:16:15.030 align:start position:0% Computing notes<00:16:13.399> what's<00:16:13.800> sarting<00:16:14.240> and<00:16:14.399> grouping<00:16:14.720> task 00:16:15.030 --> 00:16:15.040 align:start position:0% notes what's sarting and grouping task 00:16:15.040 --> 00:16:17.150 align:start position:0% notes what's sarting and grouping task interface<00:16:15.480> is<00:16:15.680> that<00:16:15.880> interface<00:16:16.519> responsible 00:16:17.150 --> 00:16:17.160 align:start position:0% interface is that interface responsible 00:16:17.160 --> 00:16:21.590 align:start position:0% interface is that interface responsible for<00:16:18.160> creating<00:16:18.639> a<00:16:18.839> graph<00:16:19.800> of<00:16:20.199> map<00:16:20.480> redu 00:16:21.590 --> 00:16:21.600 align:start position:0% for creating a graph of map redu 00:16:21.600 --> 00:16:24.949 align:start position:0% for creating a graph of map redu tasks<00:16:22.600> and<00:16:22.800> above<00:16:23.120> that<00:16:23.279> we<00:16:23.399> have<00:16:23.639> either<00:16:23.920> user 00:16:24.949 --> 00:16:24.959 align:start position:0% tasks and above that we have either user 00:16:24.959 --> 00:16:27.309 align:start position:0% tasks and above that we have either user interface<00:16:25.959> not<00:16:26.199> similar<00:16:26.519> to<00:16:26.680> the<00:16:26.800> one<00:16:27.000> that<00:16:27.120> I 00:16:27.309 --> 00:16:27.319 align:start position:0% interface not similar to the one that I 00:16:27.319 --> 00:16:29.590 align:start position:0% interface not similar to the one that I presented<00:16:27.800> but<00:16:28.680> the<00:16:28.759> one<00:16:28.920> one<00:16:29.079> that<00:16:29.160> should<00:16:29.360> be 00:16:29.590 --> 00:16:29.600 align:start position:0% presented but the one one that should be 00:16:29.600 --> 00:16:32.350 align:start position:0% presented but the one one that should be easy<00:16:29.800> to<00:16:29.959> use<00:16:30.240> and<00:16:30.680> easy<00:16:30.920> to<00:16:31.079> specify<00:16:31.519> tasks 00:16:32.350 --> 00:16:32.360 align:start position:0% easy to use and easy to specify tasks 00:16:32.360 --> 00:16:34.269 align:start position:0% easy to use and easy to specify tasks and<00:16:32.639> multiprogramming<00:16:33.480> language<00:16:33.839> support 00:16:34.269 --> 00:16:34.279 align:start position:0% and multiprogramming language support 00:16:34.279 --> 00:16:35.150 align:start position:0% and multiprogramming language support which 00:16:35.150 --> 00:16:35.160 align:start position:0% which 00:16:35.160 --> 00:16:38.189 align:start position:0% which should<00:16:36.160> I<00:16:36.319> hope<00:16:37.120> allow<00:16:37.399> users<00:16:37.680> to<00:16:37.839> Simply 00:16:38.189 --> 00:16:38.199 align:start position:0% should I hope allow users to Simply 00:16:38.199 --> 00:16:41.710 align:start position:0% should I hope allow users to Simply write<00:16:38.519> code<00:16:39.399> using<00:16:40.199> structure<00:16:40.920> some<00:16:41.519> some 00:16:41.710 --> 00:16:41.720 align:start position:0% write code using structure some some 00:16:41.720 --> 00:16:45.910 align:start position:0% write code using structure some some sort<00:16:42.000> of<00:16:42.560> standard<00:16:43.240> standard<00:16:43.800> library<00:16:44.920> and 00:16:45.910 --> 00:16:45.920 align:start position:0% sort of standard standard library and 00:16:45.920 --> 00:16:49.829 align:start position:0% sort of standard standard library and control<00:16:46.639> structures<00:16:47.639> that<00:16:48.000> are<00:16:48.240> similar<00:16:48.839> to 00:16:49.829 --> 00:16:49.839 align:start position:0% control structures that are similar to 00:16:49.839 --> 00:16:52.990 align:start position:0% control structures that are similar to uh<00:16:50.040> existing<00:16:50.839> control<00:16:51.240> structures<00:16:52.000> in 00:16:52.990 --> 00:16:53.000 align:start position:0% uh existing control structures in 00:16:53.000 --> 00:16:55.590 align:start position:0% uh existing control structures in languages<00:16:53.440> for<00:16:53.560> example<00:16:54.040> parallel<00:16:54.440> 4<00:16:55.440> that 00:16:55.590 --> 00:16:55.600 align:start position:0% languages for example parallel 4 that 00:16:55.600 --> 00:16:58.350 align:start position:0% languages for example parallel 4 that should<00:16:55.839> be<00:16:56.040> a<00:16:56.440> distribute<00:16:56.959> the<00:16:57.160> tasks<00:16:57.800> and 00:16:58.350 --> 00:16:58.360 align:start position:0% should be a distribute the tasks and 00:16:58.360 --> 00:17:01.710 align:start position:0% should be a distribute the tasks and programmer<00:16:59.000> shouldn't<00:16:59.399> be<00:17:00.399> really<00:17:00.759> aware<00:17:01.120> of 00:17:01.710 --> 00:17:01.720 align:start position:0% programmer shouldn't be really aware of 00:17:01.720 --> 00:17:04.870 align:start position:0% programmer shouldn't be really aware of what's<00:17:02.000> going<00:17:02.639> on<00:17:02.920> down 00:17:04.870 --> 00:17:04.880 align:start position:0% what's going on down 00:17:04.880 --> 00:17:08.150 align:start position:0% what's going on down here<00:17:06.280> okay 00:17:08.150 --> 00:17:08.160 align:start position:0% here okay 00:17:08.160 --> 00:17:11.470 align:start position:0% here okay and<00:17:09.160> we<00:17:09.319> believe<00:17:09.720> that<00:17:10.400> there<00:17:10.600> may<00:17:10.839> be<00:17:11.120> many 00:17:11.470 --> 00:17:11.480 align:start position:0% and we believe that there may be many 00:17:11.480 --> 00:17:14.750 align:start position:0% and we believe that there may be many many<00:17:11.760> many<00:17:12.400> virtual<00:17:12.839> machine<00:17:13.559> flavors<00:17:14.559> or 00:17:14.750 --> 00:17:14.760 align:start position:0% many many virtual machine flavors or 00:17:14.760 --> 00:17:18.510 align:start position:0% many many virtual machine flavors or maybe<00:17:15.679> not<00:17:15.919> technically<00:17:16.439> but<00:17:17.199> in<00:17:17.319> terms<00:17:17.720> of 00:17:18.510 --> 00:17:18.520 align:start position:0% maybe not technically but in terms of 00:17:18.520 --> 00:17:20.949 align:start position:0% maybe not technically but in terms of compute<00:17:19.160> capabilities<00:17:20.160> and<00:17:20.360> that<00:17:20.600> virtual 00:17:20.949 --> 00:17:20.959 align:start position:0% compute capabilities and that virtual 00:17:20.959 --> 00:17:23.110 align:start position:0% compute capabilities and that virtual machines<00:17:21.319> should<00:17:21.520> be<00:17:21.720> defined<00:17:22.160> by 00:17:23.110 --> 00:17:23.120 align:start position:0% machines should be defined by 00:17:23.120 --> 00:17:26.429 align:start position:0% machines should be defined by users<00:17:24.120> which<00:17:24.319> poses<00:17:24.720> one<00:17:25.000> problem<00:17:25.400> that<00:17:26.199> this 00:17:26.429 --> 00:17:26.439 align:start position:0% users which poses one problem that this 00:17:26.439 --> 00:17:31.150 align:start position:0% users which poses one problem that this does<00:17:26.679> not<00:17:26.959> fit<00:17:27.559> the<00:17:27.720> whole<00:17:28.600> p<00:17:28.919> feure<00:17:29.880> as<00:17:30.120> virual 00:17:31.150 --> 00:17:31.160 align:start position:0% does not fit the whole p feure as virual 00:17:31.160 --> 00:17:34.669 align:start position:0% does not fit the whole p feure as virual machines<00:17:32.160> or<00:17:32.400> the<00:17:32.679> configuration<00:17:33.440> fact<00:17:34.440> uh 00:17:34.669 --> 00:17:34.679 align:start position:0% machines or the configuration fact uh 00:17:34.679 --> 00:17:37.070 align:start position:0% machines or the configuration fact uh would<00:17:34.960> have<00:17:35.080> to<00:17:35.280> be<00:17:35.799> distributed<00:17:36.799> in<00:17:36.960> a 00:17:37.070 --> 00:17:37.080 align:start position:0% would have to be distributed in a 00:17:37.080 --> 00:17:40.190 align:start position:0% would have to be distributed in a separate<00:17:37.400> Channel<00:17:37.960> not<00:17:38.160> as<00:17:38.280> a<00:17:38.440> part<00:17:38.600> of<00:17:38.799> the 00:17:40.190 --> 00:17:40.200 align:start position:0% separate Channel not as a part of the 00:17:40.200 --> 00:17:43.470 align:start position:0% separate Channel not as a part of the application<00:17:41.679> but<00:17:42.679> that<00:17:42.840> may<00:17:43.039> not<00:17:43.200> be<00:17:43.320> a 00:17:43.470 --> 00:17:43.480 align:start position:0% application but that may not be a 00:17:43.480 --> 00:17:46.710 align:start position:0% application but that may not be a problem<00:17:44.160> at<00:17:44.280> some<00:17:44.480> point<00:17:45.080> because<00:17:45.480> we<00:17:45.720> can 00:17:46.710 --> 00:17:46.720 align:start position:0% problem at some point because we can 00:17:46.720 --> 00:17:50.230 align:start position:0% problem at some point because we can allow<00:17:47.000> users<00:17:47.320> to<00:17:48.080> distribute<00:17:49.080> the<00:17:49.240> data<00:17:49.640> that 00:17:50.230 --> 00:17:50.240 align:start position:0% allow users to distribute the data that 00:17:50.240 --> 00:17:52.150 align:start position:0% allow users to distribute the data that messages<00:17:50.600> that<00:17:50.760> they<00:17:50.880> have<00:17:51.039> such<00:17:51.240> machines 00:17:52.150 --> 00:17:52.160 align:start position:0% messages that they have such machines 00:17:52.160 --> 00:17:53.830 align:start position:0% messages that they have such machines and<00:17:52.480> and<00:17:52.679> interested<00:17:53.160> party<00:17:53.400> would<00:17:53.559> be<00:17:53.640> able 00:17:53.830 --> 00:17:53.840 align:start position:0% and and interested party would be able 00:17:53.840 --> 00:17:59.350 align:start position:0% and and interested party would be able to<00:17:54.000> download<00:17:54.320> it<00:17:54.840> and<00:17:55.039> use<00:17:55.200> it 00:17:59.350 --> 00:17:59.360 align:start position:0% 00:17:59.360 --> 00:18:06.200 align:start position:0% okay<00:17:59.960> I<00:18:00.080> think<00:18:00.240> that's<00:18:00.640> it<00:18:01.640> thanks<00:18:01.919> pza 00:18:06.200 --> 00:18:06.210 align:start position:0% 00:18:06.210 --> 00:18:10.039 align:start position:0% [Applause]