WEBVTT Kind: captions Language: en 00:00:05.200 --> 00:00:20.340 align:start position:0% you 00:00:20.340 --> 00:00:20.350 align:start position:0% 00:00:20.350 --> 00:00:27.550 align:start position:0% Thanks<00:00:23.230> all<00:00:24.230> right<00:00:24.820> ah<00:00:25.820> oh<00:00:25.970> I<00:00:26.840> still<00:00:27.290> have<00:00:27.410> one 00:00:27.550 --> 00:00:27.560 align:start position:0% Thanks all right ah oh I still have one 00:00:27.560 --> 00:00:29.499 align:start position:0% Thanks all right ah oh I still have one more<00:00:27.830> minute<00:00:28.310> bonus<00:00:28.610> that's<00:00:28.970> that's<00:00:29.240> awesome 00:00:29.499 --> 00:00:29.509 align:start position:0% more minute bonus that's that's awesome 00:00:29.509 --> 00:00:33.910 align:start position:0% more minute bonus that's that's awesome ah<00:00:29.660> what's<00:00:30.320> gone<00:00:30.529> all<00:00:31.250> right<00:00:31.960> so<00:00:32.960> thanks<00:00:33.860> so 00:00:33.910 --> 00:00:33.920 align:start position:0% ah what's gone all right so thanks so 00:00:33.920 --> 00:00:35.619 align:start position:0% ah what's gone all right so thanks so much<00:00:34.100> for<00:00:34.280> having<00:00:34.370> me<00:00:34.550> I'm<00:00:34.850> really<00:00:35.239> super 00:00:35.619 --> 00:00:35.629 align:start position:0% much for having me I'm really super 00:00:35.629 --> 00:00:39.100 align:start position:0% much for having me I'm really super excited<00:00:36.020> to<00:00:36.080> be<00:00:36.230> here<00:00:37.030> thanks<00:00:38.030> a<00:00:38.090> lot<00:00:38.239> for<00:00:38.690> Ming 00:00:39.100 --> 00:00:39.110 align:start position:0% excited to be here thanks a lot for Ming 00:00:39.110 --> 00:00:41.170 align:start position:0% excited to be here thanks a lot for Ming and<00:00:39.379> George<00:00:39.710> and<00:00:40.040> Laura<00:00:40.250> and<00:00:40.489> Hudson<00:00:40.879> and<00:00:41.000> all 00:00:41.170 --> 00:00:41.180 align:start position:0% and George and Laura and Hudson and all 00:00:41.180 --> 00:00:43.270 align:start position:0% and George and Laura and Hudson and all the<00:00:41.330> other<00:00:41.480> helpers<00:00:41.890> please<00:00:42.890> give<00:00:43.070> them<00:00:43.160> a 00:00:43.270 --> 00:00:43.280 align:start position:0% the other helpers please give them a 00:00:43.280 --> 00:00:45.580 align:start position:0% the other helpers please give them a hand<00:00:43.430> because<00:00:43.910> I<00:00:44.239> think<00:00:44.660> this<00:00:45.379> is<00:00:45.440> a<00:00:45.559> very 00:00:45.580 --> 00:00:45.590 align:start position:0% hand because I think this is a very 00:00:45.590 --> 00:00:48.940 align:start position:0% hand because I think this is a very unique<00:00:46.989> occasion<00:00:47.989> here<00:00:48.380> and<00:00:48.649> you're<00:00:48.829> making 00:00:48.940 --> 00:00:48.950 align:start position:0% unique occasion here and you're making 00:00:48.950 --> 00:00:51.370 align:start position:0% unique occasion here and you're making it<00:00:49.190> possible<00:00:49.370> thank<00:00:49.940> you<00:00:50.030> so<00:00:50.210> much<00:00:50.390> so<00:00:51.140> I'm 00:00:51.370 --> 00:00:51.380 align:start position:0% it possible thank you so much so I'm 00:00:51.380 --> 00:00:52.959 align:start position:0% it possible thank you so much so I'm talking<00:00:51.680> about<00:00:51.739> smart<00:00:52.309> contracts<00:00:52.879> as 00:00:52.959 --> 00:00:52.969 align:start position:0% talking about smart contracts as 00:00:52.969 --> 00:00:56.229 align:start position:0% talking about smart contracts as perimeter<00:00:53.450> ization<00:00:53.719> and<00:00:54.110> I<00:00:54.379> realized<00:00:55.210> when<00:00:56.210> I 00:00:56.229 --> 00:00:56.239 align:start position:0% perimeter ization and I realized when I 00:00:56.239 --> 00:00:58.270 align:start position:0% perimeter ization and I realized when I was<00:00:56.390> running<00:00:56.570> the<00:00:57.070> presentation<00:00:58.070> by 00:00:58.270 --> 00:00:58.280 align:start position:0% was running the presentation by 00:00:58.280 --> 00:01:02.170 align:start position:0% was running the presentation by Christian<00:00:59.590> ip's<00:01:00.590> know<00:01:00.770> that<00:01:00.950> he<00:01:01.399> wasn't 00:01:02.170 --> 00:01:02.180 align:start position:0% Christian ip's know that he wasn't 00:01:02.180 --> 00:01:05.020 align:start position:0% Christian ip's know that he wasn't really<00:01:02.360> sure<00:01:02.450> what<00:01:02.600> it<00:01:02.809> means<00:01:03.640> yes<00:01:04.640> he's<00:01:04.850> not 00:01:05.020 --> 00:01:05.030 align:start position:0% really sure what it means yes he's not 00:01:05.030 --> 00:01:07.660 align:start position:0% really sure what it means yes he's not the<00:01:05.149> only<00:01:05.180> one<00:01:05.420> but<00:01:06.080> I<00:01:06.350> am<00:01:06.590> going<00:01:06.979> to<00:01:07.220> try<00:01:07.369> my 00:01:07.660 --> 00:01:07.670 align:start position:0% the only one but I am going to try my 00:01:07.670 --> 00:01:10.630 align:start position:0% the only one but I am going to try my best<00:01:08.000> to<00:01:08.210> explain<00:01:08.240> exactly<00:01:09.050> that<00:01:09.259> so<00:01:10.160> i'm 00:01:10.630 --> 00:01:10.640 align:start position:0% best to explain exactly that so i'm 00:01:10.640 --> 00:01:13.120 align:start position:0% best to explain exactly that so i'm heading<00:01:11.060> dt<00:01:11.330> i'm<00:01:11.600> working<00:01:11.930> at<00:01:12.020> IBM<00:01:12.380> i'm 00:01:13.120 --> 00:01:13.130 align:start position:0% heading dt i'm working at IBM i'm 00:01:13.130 --> 00:01:16.290 align:start position:0% heading dt i'm working at IBM i'm working<00:01:13.460> in<00:01:13.550> the<00:01:13.880> project<00:01:14.270> blue<00:01:14.390> horizon<00:01:14.899> and 00:01:16.290 --> 00:01:16.300 align:start position:0% working in the project blue horizon and 00:01:16.300 --> 00:01:18.850 align:start position:0% working in the project blue horizon and we<00:01:17.300> are<00:01:17.390> i'm<00:01:17.930> very<00:01:18.350> proud<00:01:18.440> that<00:01:18.530> we're 00:01:18.850 --> 00:01:18.860 align:start position:0% we are i'm very proud that we're 00:01:18.860 --> 00:01:21.219 align:start position:0% we are i'm very proud that we're actually<00:01:19.070> really<00:01:19.570> having<00:01:20.570> a<00:01:20.630> product<00:01:21.020> there 00:01:21.219 --> 00:01:21.229 align:start position:0% actually really having a product there 00:01:21.229 --> 00:01:24.219 align:start position:0% actually really having a product there that<00:01:21.650> is<00:01:21.770> using<00:01:22.070> the<00:01:22.189> blockchain<00:01:23.080> it's<00:01:24.080> not 00:01:24.219 --> 00:01:24.229 align:start position:0% that is using the blockchain it's not 00:01:24.229 --> 00:01:25.960 align:start position:0% that is using the blockchain it's not just<00:01:24.290> a<00:01:24.500> project<00:01:24.950> it's<00:01:25.189> something<00:01:25.549> that<00:01:25.729> is 00:01:25.960 --> 00:01:25.970 align:start position:0% just a project it's something that is 00:01:25.970 --> 00:01:30.100 align:start position:0% just a project it's something that is actually<00:01:26.479> ready<00:01:27.200> for<00:01:27.439> production<00:01:27.640> so<00:01:28.640> and<00:01:29.110> i'm 00:01:30.100 --> 00:01:30.110 align:start position:0% actually ready for production so and i'm 00:01:30.110 --> 00:01:32.530 align:start position:0% actually ready for production so and i'm also<00:01:30.259> writing<00:01:30.470> a<00:01:30.650> book<00:01:30.770> about<00:01:31.009> a<00:01:31.880> serial<00:01:32.299> it's 00:01:32.530 --> 00:01:32.540 align:start position:0% also writing a book about a serial it's 00:01:32.540 --> 00:01:35.380 align:start position:0% also writing a book about a serial it's having<00:01:33.290> a<00:01:33.950> subtitle<00:01:34.850> a<00:01:34.939> serum<00:01:35.240> for 00:01:35.380 --> 00:01:35.390 align:start position:0% having a subtitle a serum for 00:01:35.390 --> 00:01:37.390 align:start position:0% having a subtitle a serum for non-technical<00:01:35.720> people<00:01:36.020> and<00:01:36.380> one<00:01:37.189> of<00:01:37.280> the 00:01:37.390 --> 00:01:37.400 align:start position:0% non-technical people and one of the 00:01:37.400 --> 00:01:38.980 align:start position:0% non-technical people and one of the things<00:01:37.430> that<00:01:37.670> i'm<00:01:37.850> taking<00:01:38.180> aim<00:01:38.299> is<00:01:38.479> that<00:01:38.509> the 00:01:38.980 --> 00:01:38.990 align:start position:0% things that i'm taking aim is that the 00:01:38.990 --> 00:01:41.350 align:start position:0% things that i'm taking aim is that the distributed<00:01:39.560> ledger<00:01:39.680> talk<00:01:40.130> is<00:01:40.880> something 00:01:41.350 --> 00:01:41.360 align:start position:0% distributed ledger talk is something 00:01:41.360 --> 00:01:43.359 align:start position:0% distributed ledger talk is something that<00:01:41.570> is<00:01:41.720> very<00:01:41.810> confusing<00:01:42.500> and<00:01:42.979> that<00:01:43.130> is 00:01:43.359 --> 00:01:43.369 align:start position:0% that is very confusing and that is 00:01:43.369 --> 00:01:44.859 align:start position:0% that is very confusing and that is giving<00:01:43.729> people<00:01:44.030> the<00:01:44.150> wrong<00:01:44.270> idea<00:01:44.420> what<00:01:44.750> to 00:01:44.859 --> 00:01:44.869 align:start position:0% giving people the wrong idea what to 00:01:44.869 --> 00:01:46.899 align:start position:0% giving people the wrong idea what to look<00:01:45.020> at<00:01:45.229> when<00:01:46.159> they're<00:01:46.280> looking<00:01:46.369> for<00:01:46.670> ideas 00:01:46.899 --> 00:01:46.909 align:start position:0% look at when they're looking for ideas 00:01:46.909 --> 00:01:50.230 align:start position:0% look at when they're looking for ideas for<00:01:47.060> block<00:01:47.210> chain<00:01:47.560> so<00:01:48.560> people<00:01:48.890> like<00:01:48.970> this<00:01:49.970> used 00:01:50.230 --> 00:01:50.240 align:start position:0% for block chain so people like this used 00:01:50.240 --> 00:01:51.609 align:start position:0% for block chain so people like this used to<00:01:50.270> be<00:01:50.390> the<00:01:50.420> ledger<00:01:50.659> thing<00:01:50.930> because<00:01:51.259> the 00:01:51.609 --> 00:01:51.619 align:start position:0% to be the ledger thing because the 00:01:51.619 --> 00:01:52.870 align:start position:0% to be the ledger thing because the letter<00:01:51.799> is<00:01:51.979> something<00:01:52.280> that's<00:01:52.369> around<00:01:52.610> for<00:01:52.820> a 00:01:52.870 --> 00:01:52.880 align:start position:0% letter is something that's around for a 00:01:52.880 --> 00:01:54.609 align:start position:0% letter is something that's around for a long<00:01:53.000> time<00:01:53.060> and<00:01:53.509> the<00:01:53.900> block<00:01:54.110> chain<00:01:54.140> obviously 00:01:54.609 --> 00:01:54.619 align:start position:0% long time and the block chain obviously 00:01:54.619 --> 00:01:57.580 align:start position:0% long time and the block chain obviously has<00:01:54.770> a<00:01:54.979> lot<00:01:55.130> of<00:01:55.299> very<00:01:56.299> good<00:01:56.390> features<00:01:57.350> that 00:01:57.580 --> 00:01:57.590 align:start position:0% has a lot of very good features that 00:01:57.590 --> 00:02:00.090 align:start position:0% has a lot of very good features that make<00:01:57.829> it<00:01:57.860> very<00:01:58.549> good<00:01:59.090> just<00:01:59.329> repeat<00:01:59.540> a<00:01:59.600> letter 00:02:00.090 --> 00:02:00.100 align:start position:0% make it very good just repeat a letter 00:02:00.100 --> 00:02:01.929 align:start position:0% make it very good just repeat a letter however<00:02:01.100> that's<00:02:01.430> completely<00:02:01.759> the<00:02:01.909> wrong 00:02:01.929 --> 00:02:01.939 align:start position:0% however that's completely the wrong 00:02:01.939 --> 00:02:03.910 align:start position:0% however that's completely the wrong track<00:02:02.390> and<00:02:02.659> where<00:02:03.110> you<00:02:03.470> actually<00:02:03.649> should 00:02:03.910 --> 00:02:03.920 align:start position:0% track and where you actually should 00:02:03.920 --> 00:02:06.490 align:start position:0% track and where you actually should looking<00:02:04.490> on<00:02:04.790> is<00:02:05.060> the<00:02:05.390> guarantee<00:02:05.570> of<00:02:05.810> execution 00:02:06.490 --> 00:02:06.500 align:start position:0% looking on is the guarantee of execution 00:02:06.500 --> 00:02:07.810 align:start position:0% looking on is the guarantee of execution because<00:02:06.649> that's<00:02:06.950> the<00:02:07.100> reason<00:02:07.369> why<00:02:07.399> for 00:02:07.810 --> 00:02:07.820 align:start position:0% because that's the reason why for 00:02:07.820 --> 00:02:09.400 align:start position:0% because that's the reason why for example<00:02:07.880> bitcoin<00:02:08.509> is<00:02:08.600> where<00:02:08.810> something<00:02:09.229> it's 00:02:09.400 --> 00:02:09.410 align:start position:0% example bitcoin is where something it's 00:02:09.410 --> 00:02:10.840 align:start position:0% example bitcoin is where something it's not<00:02:09.440> just<00:02:09.769> because<00:02:10.250> it<00:02:10.549> couldn't<00:02:10.700> be 00:02:10.840 --> 00:02:10.850 align:start position:0% not just because it couldn't be 00:02:10.850 --> 00:02:12.430 align:start position:0% not just because it couldn't be duplicated<00:02:11.360> in<00:02:11.450> the<00:02:11.540> past<00:02:11.840> or<00:02:12.110> you<00:02:12.200> can 00:02:12.430 --> 00:02:12.440 align:start position:0% duplicated in the past or you can 00:02:12.440 --> 00:02:14.949 align:start position:0% duplicated in the past or you can duplicate<00:02:12.799> it<00:02:13.100> now<00:02:13.340> it's<00:02:13.700> because<00:02:14.239> nobody 00:02:14.949 --> 00:02:14.959 align:start position:0% duplicate it now it's because nobody 00:02:14.959 --> 00:02:16.270 align:start position:0% duplicate it now it's because nobody will<00:02:15.110> be<00:02:15.260> able<00:02:15.290> to<00:02:15.530> duplicate<00:02:15.709> them<00:02:16.130> going 00:02:16.270 --> 00:02:16.280 align:start position:0% will be able to duplicate them going 00:02:16.280 --> 00:02:17.710 align:start position:0% will be able to duplicate them going into<00:02:16.459> the<00:02:16.610> future<00:02:16.850> that's<00:02:17.269> why<00:02:17.390> they<00:02:17.540> have<00:02:17.570> a 00:02:17.710 --> 00:02:17.720 align:start position:0% into the future that's why they have a 00:02:17.720 --> 00:02:22.060 align:start position:0% into the future that's why they have a value<00:02:17.989> and<00:02:19.989> if<00:02:20.989> we<00:02:21.230> look<00:02:21.350> at<00:02:21.470> the<00:02:21.590> theorem<00:02:21.920> as 00:02:22.060 --> 00:02:22.070 align:start position:0% value and if we look at the theorem as 00:02:22.070 --> 00:02:23.619 align:start position:0% value and if we look at the theorem as the<00:02:22.160> world<00:02:22.340> computer<00:02:22.970> it's<00:02:23.120> also<00:02:23.300> something 00:02:23.619 --> 00:02:23.629 align:start position:0% the world computer it's also something 00:02:23.629 --> 00:02:25.839 align:start position:0% the world computer it's also something where<00:02:23.989> you<00:02:24.110> think<00:02:24.860> of<00:02:24.950> moving<00:02:25.129> cogs<00:02:25.520> right<00:02:25.819> i 00:02:25.839 --> 00:02:25.849 align:start position:0% where you think of moving cogs right i 00:02:25.849 --> 00:02:28.120 align:start position:0% where you think of moving cogs right i means<00:02:26.120> if<00:02:26.330> you<00:02:26.450> you<00:02:26.720> put<00:02:26.900> something<00:02:27.140> into 00:02:28.120 --> 00:02:28.130 align:start position:0% means if you you put something into 00:02:28.130 --> 00:02:30.160 align:start position:0% means if you you put something into a<00:02:28.330> transaction<00:02:29.330> and<00:02:29.480> it's<00:02:29.600> going<00:02:29.750> to<00:02:29.870> eight 00:02:30.160 --> 00:02:30.170 align:start position:0% a transaction and it's going to eight 00:02:30.170 --> 00:02:32.920 align:start position:0% a transaction and it's going to eight thousand<00:02:30.590> computers<00:02:30.770> and<00:02:31.220> is<00:02:31.750> changing<00:02:32.750> bits 00:02:32.920 --> 00:02:32.930 align:start position:0% thousand computers and is changing bits 00:02:32.930 --> 00:02:36.610 align:start position:0% thousand computers and is changing bits and<00:02:33.110> bytes<00:02:33.260> there<00:02:33.560> so<00:02:35.230> it's<00:02:36.230> not<00:02:36.320> a<00:02:36.410> world 00:02:36.610 --> 00:02:36.620 align:start position:0% and bytes there so it's not a world 00:02:36.620 --> 00:02:38.170 align:start position:0% and bytes there so it's not a world ledger<00:02:36.860> that<00:02:36.980> we're<00:02:37.340> talking<00:02:37.460> about<00:02:37.700> although 00:02:38.170 --> 00:02:38.180 align:start position:0% ledger that we're talking about although 00:02:38.180 --> 00:02:40.660 align:start position:0% ledger that we're talking about although on<00:02:38.750> the<00:02:38.930> other<00:02:39.080> hand<00:02:39.200> that's<00:02:40.010> the<00:02:40.130> URL<00:02:40.370> for<00:02:40.400> my 00:02:40.660 --> 00:02:40.670 align:start position:0% on the other hand that's the URL for my 00:02:40.670 --> 00:02:43.660 align:start position:0% on the other hand that's the URL for my book<00:02:40.990> if<00:02:41.990> you<00:02:42.620> try<00:02:42.860> to<00:02:42.920> really<00:02:43.190> get<00:02:43.370> your<00:02:43.520> head 00:02:43.660 --> 00:02:43.670 align:start position:0% book if you try to really get your head 00:02:43.670 --> 00:02:45.070 align:start position:0% book if you try to really get your head around<00:02:43.790> it<00:02:44.150> you<00:02:44.330> look<00:02:44.480> at<00:02:44.660> stuff<00:02:44.930> from 00:02:45.070 --> 00:02:45.080 align:start position:0% around it you look at stuff from 00:02:45.080 --> 00:02:46.930 align:start position:0% around it you look at stuff from different<00:02:45.410> angles<00:02:45.740> and<00:02:46.010> that's<00:02:46.550> also<00:02:46.820> what 00:02:46.930 --> 00:02:46.940 align:start position:0% different angles and that's also what 00:02:46.940 --> 00:02:49.660 align:start position:0% different angles and that's also what I'm<00:02:47.030> trying<00:02:47.300> to<00:02:47.360> do<00:02:47.480> in<00:02:47.600> my<00:02:47.630> book<00:02:47.870> is<00:02:48.670> I'm 00:02:49.660 --> 00:02:49.670 align:start position:0% I'm trying to do in my book is I'm 00:02:49.670 --> 00:02:53.230 align:start position:0% I'm trying to do in my book is I'm explaining<00:02:50.180> where<00:02:50.540> you<00:02:50.840> could<00:02:51.050> actually<00:02:52.240> have 00:02:53.230 --> 00:02:53.240 align:start position:0% explaining where you could actually have 00:02:53.240 --> 00:02:55.480 align:start position:0% explaining where you could actually have by<00:02:53.570> taking<00:02:53.990> a<00:02:54.080> different<00:02:54.200> view<00:02:54.680> have<00:02:55.460> a 00:02:55.480 --> 00:02:55.490 align:start position:0% by taking a different view have a 00:02:55.490 --> 00:02:58.480 align:start position:0% by taking a different view have a different<00:02:56.060> inside<00:02:56.390> and<00:02:56.920> this<00:02:57.920> is<00:02:58.100> something 00:02:58.480 --> 00:02:58.490 align:start position:0% different inside and this is something 00:02:58.490 --> 00:03:01.150 align:start position:0% different inside and this is something in<00:02:59.180> games<00:02:59.660> development<00:03:00.080> there<00:03:00.350> is<00:03:00.440> that<00:03:00.890> book 00:03:01.150 --> 00:03:01.160 align:start position:0% in games development there is that book 00:03:01.160 --> 00:03:03.040 align:start position:0% in games development there is that book so<00:03:01.370> to<00:03:01.430> say<00:03:01.640> about<00:03:01.760> how<00:03:02.030> you<00:03:02.090> design<00:03:02.510> games<00:03:02.780> is 00:03:03.040 --> 00:03:03.050 align:start position:0% so to say about how you design games is 00:03:03.050 --> 00:03:05.110 align:start position:0% so to say about how you design games is called<00:03:03.320> book<00:03:03.530> of<00:03:03.650> lenses<00:03:04.070> so<00:03:04.220> I'm<00:03:04.340> not 00:03:05.110 --> 00:03:05.120 align:start position:0% called book of lenses so I'm not 00:03:05.120 --> 00:03:08.410 align:start position:0% called book of lenses so I'm not inventing<00:03:05.540> this<00:03:05.890> and<00:03:06.890> of<00:03:07.790> course<00:03:08.030> if<00:03:08.150> you<00:03:08.240> look 00:03:08.410 --> 00:03:08.420 align:start position:0% inventing this and of course if you look 00:03:08.420 --> 00:03:10.990 align:start position:0% inventing this and of course if you look at<00:03:08.570> Bitcoin<00:03:09.020> in<00:03:09.800> the<00:03:10.400> end<00:03:10.520> what<00:03:10.670> you<00:03:10.700> want<00:03:10.910> to 00:03:10.990 --> 00:03:11.000 align:start position:0% at Bitcoin in the end what you want to 00:03:11.000 --> 00:03:14.200 align:start position:0% at Bitcoin in the end what you want to know<00:03:11.180> is<00:03:11.510> what's<00:03:12.470> the<00:03:12.590> balance<00:03:12.740> of<00:03:13.070> my<00:03:13.730> account 00:03:14.200 --> 00:03:14.210 align:start position:0% know is what's the balance of my account 00:03:14.210 --> 00:03:16.270 align:start position:0% know is what's the balance of my account of<00:03:14.510> my<00:03:14.720> Bitcoin<00:03:15.050> account<00:03:15.290> but<00:03:15.920> where<00:03:16.100> are<00:03:16.190> the 00:03:16.270 --> 00:03:16.280 align:start position:0% of my Bitcoin account but where are the 00:03:16.280 --> 00:03:19.360 align:start position:0% of my Bitcoin account but where are the smart<00:03:16.520> contracts<00:03:16.880> there<00:03:17.150> so<00:03:18.050> there's<00:03:19.040> the 00:03:19.360 --> 00:03:19.370 align:start position:0% smart contracts there so there's the 00:03:19.370 --> 00:03:21.070 align:start position:0% smart contracts there so there's the question<00:03:19.520> of<00:03:19.790> course<00:03:20.060> our<00:03:20.300> smart<00:03:20.600> contracts 00:03:21.070 --> 00:03:21.080 align:start position:0% question of course our smart contracts 00:03:21.080 --> 00:03:22.210 align:start position:0% question of course our smart contracts really<00:03:21.290> something<00:03:21.650> that<00:03:21.740> you<00:03:21.830> can<00:03:21.920> do<00:03:22.070> with 00:03:22.210 --> 00:03:22.220 align:start position:0% really something that you can do with 00:03:22.220 --> 00:03:23.920 align:start position:0% really something that you can do with Bitcoin<00:03:22.580> and<00:03:22.730> we're<00:03:22.910> on<00:03:23.030> a<00:03:23.060> serum<00:03:23.420> conference 00:03:23.920 --> 00:03:23.930 align:start position:0% Bitcoin and we're on a serum conference 00:03:23.930 --> 00:03:28.090 align:start position:0% Bitcoin and we're on a serum conference here<00:03:24.140> so<00:03:24.320> I<00:03:24.380> can<00:03:24.440> be<00:03:24.680> critical<00:03:25.870> and<00:03:27.010> what<00:03:28.010> you 00:03:28.090 --> 00:03:28.100 align:start position:0% here so I can be critical and what you 00:03:28.100 --> 00:03:29.590 align:start position:0% here so I can be critical and what you can<00:03:28.220> do<00:03:28.340> is<00:03:28.430> multi<00:03:28.700> stick<00:03:28.880> with<00:03:29.030> Bitcoin<00:03:29.390> right 00:03:29.590 --> 00:03:29.600 align:start position:0% can do is multi stick with Bitcoin right 00:03:29.600 --> 00:03:31.690 align:start position:0% can do is multi stick with Bitcoin right and<00:03:29.810> then<00:03:30.260> everything<00:03:30.860> that<00:03:31.220> goes<00:03:31.310> beyond 00:03:31.690 --> 00:03:31.700 align:start position:0% and then everything that goes beyond 00:03:31.700 --> 00:03:33.700 align:start position:0% and then everything that goes beyond that<00:03:31.940> you<00:03:32.570> can<00:03:32.720> put<00:03:32.870> a<00:03:32.900> hash<00:03:33.230> in<00:03:33.560> the 00:03:33.700 --> 00:03:33.710 align:start position:0% that you can put a hash in the 00:03:33.710 --> 00:03:35.560 align:start position:0% that you can put a hash in the blockchain<00:03:33.920> and<00:03:34.310> Bitcoin<00:03:34.640> and<00:03:34.910> then<00:03:35.330> you<00:03:35.420> can 00:03:35.560 --> 00:03:35.570 align:start position:0% blockchain and Bitcoin and then you can 00:03:35.570 --> 00:03:37.390 align:start position:0% blockchain and Bitcoin and then you can say<00:03:35.720> okay<00:03:35.960> but<00:03:36.140> I<00:03:36.290> have<00:03:36.530> clients<00:03:36.860> that<00:03:37.100> all 00:03:37.390 --> 00:03:37.400 align:start position:0% say okay but I have clients that all 00:03:37.400 --> 00:03:39.010 align:start position:0% say okay but I have clients that all agree<00:03:37.670> that<00:03:37.700> a<00:03:37.880> certain<00:03:38.120> hash<00:03:38.420> is<00:03:38.660> going<00:03:38.870> to 00:03:39.010 --> 00:03:39.020 align:start position:0% agree that a certain hash is going to 00:03:39.020 --> 00:03:41.140 align:start position:0% agree that a certain hash is going to mean<00:03:39.470> a<00:03:39.500> certain<00:03:39.950> code<00:03:40.160> and<00:03:40.490> how<00:03:40.880> they<00:03:41.030> get 00:03:41.140 --> 00:03:41.150 align:start position:0% mean a certain code and how they get 00:03:41.150 --> 00:03:42.790 align:start position:0% mean a certain code and how they get that<00:03:41.300> code<00:03:41.510> doesn't<00:03:41.840> matter<00:03:41.990> and<00:03:42.260> then<00:03:42.680> they 00:03:42.790 --> 00:03:42.800 align:start position:0% that code doesn't matter and then they 00:03:42.800 --> 00:03:44.410 align:start position:0% that code doesn't matter and then they gonna<00:03:42.950> execute<00:03:43.250> it<00:03:43.550> and<00:03:43.670> that's<00:03:43.820> as<00:03:43.970> good<00:03:44.150> as 00:03:44.410 --> 00:03:44.420 align:start position:0% gonna execute it and that's as good as 00:03:44.420 --> 00:03:49.990 align:start position:0% gonna execute it and that's as good as having<00:03:44.960> the<00:03:45.140> code<00:03:45.470> on<00:03:45.680> chain<00:03:45.980> however<00:03:48.100> and<00:03:49.100> I<00:03:49.610> I 00:03:49.990 --> 00:03:50.000 align:start position:0% having the code on chain however and I I 00:03:50.000 --> 00:03:52.900 align:start position:0% having the code on chain however and I I oh<00:03:50.390> that<00:03:50.960> to<00:03:51.140> Jolla<00:03:51.410> Tony<00:03:51.710> one<00:03:52.040> researcher 00:03:52.900 --> 00:03:52.910 align:start position:0% oh that to Jolla Tony one researcher 00:03:52.910 --> 00:03:55.030 align:start position:0% oh that to Jolla Tony one researcher like<00:03:53.150> the<00:03:53.300> earliest<00:03:53.630> researcher<00:03:54.020> IBM<00:03:54.830> that 00:03:55.030 --> 00:03:55.040 align:start position:0% like the earliest researcher IBM that 00:03:55.040 --> 00:03:57.630 align:start position:0% like the earliest researcher IBM that was<00:03:55.400> looking<00:03:55.670> into<00:03:55.880> Bitcoin<00:03:56.360> and<00:03:56.630> blockchain 00:03:57.630 --> 00:03:57.640 align:start position:0% was looking into Bitcoin and blockchain 00:03:57.640 --> 00:04:00.280 align:start position:0% was looking into Bitcoin and blockchain there<00:03:58.640> is<00:03:58.730> an<00:03:58.820> analogy<00:03:59.030> here<00:03:59.600> that<00:03:59.990> could<00:04:00.140> be 00:04:00.280 --> 00:04:00.290 align:start position:0% there is an analogy here that could be 00:04:00.290 --> 00:04:03.370 align:start position:0% there is an analogy here that could be made<00:04:00.440> between<00:04:00.709> FTP<00:04:01.280> and<00:04:01.430> HTTP<00:04:01.990> so<00:04:02.990> there's<00:04:03.320> a 00:04:03.370 --> 00:04:03.380 align:start position:0% made between FTP and HTTP so there's a 00:04:03.380 --> 00:04:05.320 align:start position:0% made between FTP and HTTP so there's a story<00:04:03.680> that<00:04:03.770> at<00:04:04.040> IBM<00:04:04.400> when<00:04:04.640> somebody<00:04:05.150> came<00:04:05.270> up 00:04:05.320 --> 00:04:05.330 align:start position:0% story that at IBM when somebody came up 00:04:05.330 --> 00:04:07.270 align:start position:0% story that at IBM when somebody came up with<00:04:05.630> yeah<00:04:06.050> we<00:04:06.170> should<00:04:06.320> be<00:04:06.410> looking<00:04:06.500> at<00:04:06.740> a<00:04:06.860> PP 00:04:07.270 --> 00:04:07.280 align:start position:0% with yeah we should be looking at a PP 00:04:07.280 --> 00:04:10.360 align:start position:0% with yeah we should be looking at a PP HTTP<00:04:07.940> they<00:04:08.750> were<00:04:08.860> making<00:04:09.860> an<00:04:09.950> experiment 00:04:10.360 --> 00:04:10.370 align:start position:0% HTTP they were making an experiment 00:04:10.370 --> 00:04:12.430 align:start position:0% HTTP they were making an experiment because<00:04:10.910> technically<00:04:11.660> some<00:04:11.990> people<00:04:12.230> said 00:04:12.430 --> 00:04:12.440 align:start position:0% because technically some people said 00:04:12.440 --> 00:04:14.080 align:start position:0% because technically some people said well<00:04:12.590> HTTP<00:04:13.130> is<00:04:13.220> semantically<00:04:13.640> nothing 00:04:14.080 --> 00:04:14.090 align:start position:0% well HTTP is semantically nothing 00:04:14.090 --> 00:04:15.940 align:start position:0% well HTTP is semantically nothing different<00:04:14.240> there's<00:04:14.810> nothing<00:04:14.959> different<00:04:15.680> than 00:04:15.940 --> 00:04:15.950 align:start position:0% different there's nothing different than 00:04:15.950 --> 00:04:18.220 align:start position:0% different there's nothing different than ft<00:04:16.880> what<00:04:17.060> ftp<00:04:17.390> does<00:04:17.600> and<00:04:17.810> the<00:04:17.870> end<00:04:17.989> you<00:04:18.080> get<00:04:18.170> a 00:04:18.220 --> 00:04:18.230 align:start position:0% ft what ftp does and the end you get a 00:04:18.230 --> 00:04:21.340 align:start position:0% ft what ftp does and the end you get a file<00:04:18.500> right<00:04:18.830> that's<00:04:19.520> that's<00:04:19.760> it<00:04:19.940> and<00:04:20.200> so<00:04:21.200> they 00:04:21.340 --> 00:04:21.350 align:start position:0% file right that's that's it and so they 00:04:21.350 --> 00:04:22.960 align:start position:0% file right that's that's it and so they gave<00:04:21.620> them<00:04:21.859> the<00:04:21.950> task<00:04:22.220> who<00:04:22.520> write<00:04:22.760> a<00:04:22.790> web 00:04:22.960 --> 00:04:22.970 align:start position:0% gave them the task who write a web 00:04:22.970 --> 00:04:25.270 align:start position:0% gave them the task who write a web server<00:04:23.240> one<00:04:23.780> guy<00:04:24.050> was<00:04:24.290> writing<00:04:24.560> at<00:04:24.650> an<00:04:24.740> ftp<00:04:25.100> one 00:04:25.270 --> 00:04:25.280 align:start position:0% server one guy was writing at an ftp one 00:04:25.280 --> 00:04:28.450 align:start position:0% server one guy was writing at an ftp one was<00:04:25.730> writing<00:04:26.120> in<00:04:26.210> at<00:04:26.300> HTTP<00:04:26.780> and<00:04:27.040> after<00:04:28.040> a<00:04:28.070> day 00:04:28.450 --> 00:04:28.460 align:start position:0% was writing in at HTTP and after a day 00:04:28.460 --> 00:04:30.730 align:start position:0% was writing in at HTTP and after a day that<00:04:28.700> guy<00:04:28.940> with<00:04:29.090> four<00:04:29.300> HTTP<00:04:29.720> was<00:04:29.870> done<00:04:30.080> and<00:04:30.290> the 00:04:30.730 --> 00:04:30.740 align:start position:0% that guy with four HTTP was done and the 00:04:30.740 --> 00:04:33.010 align:start position:0% that guy with four HTTP was done and the guy<00:04:30.860> with<00:04:31.100> ftp<00:04:31.730> was<00:04:31.910> after<00:04:32.270> week<00:04:32.420> he<00:04:32.690> was<00:04:32.840> still 00:04:33.010 --> 00:04:33.020 align:start position:0% guy with ftp was after week he was still 00:04:33.020 --> 00:04:34.660 align:start position:0% guy with ftp was after week he was still not<00:04:33.110> done<00:04:33.290> so<00:04:33.620> they<00:04:33.860> canceled<00:04:34.190> the<00:04:34.250> experiment 00:04:34.660 --> 00:04:34.670 align:start position:0% not done so they canceled the experiment 00:04:34.670 --> 00:04:36.700 align:start position:0% not done so they canceled the experiment it<00:04:34.970> had<00:04:35.180> a<00:04:35.210> clear<00:04:35.450> result<00:04:35.750> and<00:04:35.990> IBM<00:04:36.320> started<00:04:36.620> to 00:04:36.700 --> 00:04:36.710 align:start position:0% it had a clear result and IBM started to 00:04:36.710 --> 00:04:40.120 align:start position:0% it had a clear result and IBM started to look<00:04:36.800> at<00:04:36.979> HTTP<00:04:37.490> and<00:04:37.669> this<00:04:38.419> could<00:04:38.660> be<00:04:38.900> taken<00:04:39.860> to 00:04:40.120 --> 00:04:40.130 align:start position:0% look at HTTP and this could be taken to 00:04:40.130 --> 00:04:41.680 align:start position:0% look at HTTP and this could be taken to the<00:04:40.160> difference<00:04:40.729> of<00:04:40.880> having<00:04:41.210> the<00:04:41.270> stuff<00:04:41.479> off 00:04:41.680 --> 00:04:41.690 align:start position:0% the difference of having the stuff off 00:04:41.690 --> 00:04:42.570 align:start position:0% the difference of having the stuff off chain<00:04:41.990> or<00:04:42.140> having 00:04:42.570 --> 00:04:42.580 align:start position:0% chain or having 00:04:42.580 --> 00:04:44.040 align:start position:0% chain or having unchain<00:04:42.939> because<00:04:43.360> of<00:04:43.479> various<00:04:43.780> attack 00:04:44.040 --> 00:04:44.050 align:start position:0% unchain because of various attack 00:04:44.050 --> 00:04:45.570 align:start position:0% unchain because of various attack vectors<00:04:44.409> that<00:04:44.439> we've<00:04:45.039> been<00:04:45.220> speaking<00:04:45.400> about 00:04:45.570 --> 00:04:45.580 align:start position:0% vectors that we've been speaking about 00:04:45.580 --> 00:04:49.619 align:start position:0% vectors that we've been speaking about this<00:04:45.909> week<00:04:46.289> these<00:04:47.289> days<00:04:47.500> so<00:04:48.310> blue<00:04:48.460> horizon<00:04:48.970> is 00:04:49.619 --> 00:04:49.629 align:start position:0% this week these days so blue horizon is 00:04:49.629 --> 00:04:52.140 align:start position:0% this week these days so blue horizon is something<00:04:50.169> that<00:04:50.860> informs<00:04:51.310> very<00:04:51.639> much<00:04:51.819> how<00:04:52.120> I 00:04:52.140 --> 00:04:52.150 align:start position:0% something that informs very much how I 00:04:52.150 --> 00:04:53.550 align:start position:0% something that informs very much how I look<00:04:52.569> at<00:04:52.659> the<00:04:52.750> blockchain<00:04:52.960> at<00:04:53.199> the<00:04:53.259> moment 00:04:53.550 --> 00:04:53.560 align:start position:0% look at the blockchain at the moment 00:04:53.560 --> 00:04:55.679 align:start position:0% look at the blockchain at the moment because<00:04:54.250> it's<00:04:54.430> something<00:04:55.330> we've<00:04:55.659> been 00:04:55.679 --> 00:04:55.689 align:start position:0% because it's something we've been 00:04:55.689 --> 00:04:59.100 align:start position:0% because it's something we've been working<00:04:55.840> on<00:04:56.229> very<00:04:56.500> hard<00:04:56.800> and<00:04:57.870> we've<00:04:58.870> also 00:04:59.100 --> 00:04:59.110 align:start position:0% working on very hard and we've also 00:04:59.110 --> 00:05:03.059 align:start position:0% working on very hard and we've also sometimes<00:04:59.680> run<00:04:59.889> into<00:05:01.560> insights<00:05:02.560> that<00:05:02.710> maybe 00:05:03.059 --> 00:05:03.069 align:start position:0% sometimes run into insights that maybe 00:05:03.069 --> 00:05:05.339 align:start position:0% sometimes run into insights that maybe we<00:05:03.310> hadn't<00:05:03.699> hoped<00:05:03.879> to<00:05:04.030> find<00:05:04.210> what's<00:05:05.199> blue 00:05:05.339 --> 00:05:05.349 align:start position:0% we hadn't hoped to find what's blue 00:05:05.349 --> 00:05:07.320 align:start position:0% we hadn't hoped to find what's blue horizon<00:05:05.770> Blue<00:05:05.889> Horizon<00:05:06.340> is<00:05:06.430> doing<00:05:06.729> analysis 00:05:07.320 --> 00:05:07.330 align:start position:0% horizon Blue Horizon is doing analysis 00:05:07.330 --> 00:05:09.629 align:start position:0% horizon Blue Horizon is doing analysis at<00:05:07.539> the<00:05:07.719> edge<00:05:07.840> that<00:05:08.409> means<00:05:08.650> that<00:05:09.400> we<00:05:09.610> are 00:05:09.629 --> 00:05:09.639 align:start position:0% at the edge that means that we are 00:05:09.639 --> 00:05:12.420 align:start position:0% at the edge that means that we are basically<00:05:10.449> making<00:05:10.990> possible<00:05:11.409> to<00:05:12.069> have<00:05:12.189> the 00:05:12.420 --> 00:05:12.430 align:start position:0% basically making possible to have the 00:05:12.430 --> 00:05:14.249 align:start position:0% basically making possible to have the analysis<00:05:12.939> code<00:05:13.210> running<00:05:13.479> as<00:05:13.689> close<00:05:13.960> to<00:05:14.139> the 00:05:14.249 --> 00:05:14.259 align:start position:0% analysis code running as close to the 00:05:14.259 --> 00:05:16.140 align:start position:0% analysis code running as close to the sensors<00:05:14.680> and<00:05:14.710> the<00:05:14.979> edge<00:05:15.159> as<00:05:15.460> possible<00:05:15.490> as 00:05:16.140 --> 00:05:16.150 align:start position:0% sensors and the edge as possible as 00:05:16.150 --> 00:05:18.600 align:start position:0% sensors and the edge as possible as opposed<00:05:16.629> to<00:05:16.719> having<00:05:16.870> it<00:05:16.990> in<00:05:17.110> the<00:05:17.169> cloud<00:05:17.379> so<00:05:18.219> a 00:05:18.600 --> 00:05:18.610 align:start position:0% opposed to having it in the cloud so a 00:05:18.610 --> 00:05:21.029 align:start position:0% opposed to having it in the cloud so a very<00:05:19.509> common<00:05:19.870> situation<00:05:20.289> is<00:05:20.409> something<00:05:20.919> like 00:05:21.029 --> 00:05:21.039 align:start position:0% very common situation is something like 00:05:21.039 --> 00:05:22.950 align:start position:0% very common situation is something like this<00:05:21.219> you<00:05:21.430> have<00:05:21.460> a<00:05:21.550> lot<00:05:21.729> of<00:05:21.759> sensors<00:05:22.240> those<00:05:22.810> are 00:05:22.950 --> 00:05:22.960 align:start position:0% this you have a lot of sensors those are 00:05:22.960 --> 00:05:25.320 align:start position:0% this you have a lot of sensors those are the<00:05:23.110> bubbles<00:05:23.680> at<00:05:24.039> the<00:05:24.129> top<00:05:24.370> and<00:05:24.580> then<00:05:25.060> those 00:05:25.320 --> 00:05:25.330 align:start position:0% the bubbles at the top and then those 00:05:25.330 --> 00:05:27.779 align:start position:0% the bubbles at the top and then those sensors<00:05:25.780> they<00:05:26.289> could<00:05:26.770> be<00:05:26.889> antennas<00:05:27.340> for<00:05:27.580> a 00:05:27.779 --> 00:05:27.789 align:start position:0% sensors they could be antennas for a 00:05:27.789 --> 00:05:29.490 align:start position:0% sensors they could be antennas for a software-defined<00:05:28.150> radio<00:05:28.659> or<00:05:28.960> a<00:05:28.990> temperature 00:05:29.490 --> 00:05:29.500 align:start position:0% software-defined radio or a temperature 00:05:29.500 --> 00:05:32.459 align:start position:0% software-defined radio or a temperature or<00:05:29.800> smoke<00:05:30.639> detectors<00:05:31.180> they<00:05:31.780> sending<00:05:32.169> a<00:05:32.229> lot<00:05:32.409> of 00:05:32.459 --> 00:05:32.469 align:start position:0% or smoke detectors they sending a lot of 00:05:32.469 --> 00:05:36.390 align:start position:0% or smoke detectors they sending a lot of data<00:05:32.770> to<00:05:32.919> the<00:05:33.159> cloud<00:05:33.400> and<00:05:33.849> that<00:05:34.539> is<00:05:35.159> very<00:05:36.159> high 00:05:36.390 --> 00:05:36.400 align:start position:0% data to the cloud and that is very high 00:05:36.400 --> 00:05:39.360 align:start position:0% data to the cloud and that is very high volume<00:05:36.849> data<00:05:37.029> with<00:05:37.659> a<00:05:37.690> very<00:05:38.110> low<00:05:38.740> individual 00:05:39.360 --> 00:05:39.370 align:start position:0% volume data with a very low individual 00:05:39.370 --> 00:05:42.540 align:start position:0% volume data with a very low individual value<00:05:39.819> that<00:05:40.509> is<00:05:40.629> then<00:05:40.810> analyzed<00:05:41.439> in<00:05:41.710> the<00:05:41.770> cloud 00:05:42.540 --> 00:05:42.550 align:start position:0% value that is then analyzed in the cloud 00:05:42.550 --> 00:05:46.409 align:start position:0% value that is then analyzed in the cloud to<00:05:42.819> make<00:05:43.330> high<00:05:43.659> value<00:05:43.960> out<00:05:44.110> of<00:05:44.139> it<00:05:44.289> so<00:05:45.300> what<00:05:46.300> we 00:05:46.409 --> 00:05:46.419 align:start position:0% to make high value out of it so what we 00:05:46.419 --> 00:05:48.089 align:start position:0% to make high value out of it so what we are<00:05:46.449> striving<00:05:46.810> to<00:05:47.080> do<00:05:47.229> is<00:05:47.440> to<00:05:47.740> reverse<00:05:48.069> that 00:05:48.089 --> 00:05:48.099 align:start position:0% are striving to do is to reverse that 00:05:48.099 --> 00:05:50.459 align:start position:0% are striving to do is to reverse that and<00:05:48.520> have<00:05:49.029> in<00:05:49.300> the<00:05:49.419> end<00:05:49.539> high<00:05:49.779> value<00:05:50.139> and<00:05:50.349> low 00:05:50.459 --> 00:05:50.469 align:start position:0% and have in the end high value and low 00:05:50.469 --> 00:05:54.059 align:start position:0% and have in the end high value and low volume<00:05:50.860> so<00:05:51.129> we're<00:05:51.310> sending<00:05:51.580> out<00:05:51.940> the<00:05:53.069> analysis 00:05:54.059 --> 00:05:54.069 align:start position:0% volume so we're sending out the analysis 00:05:54.069 --> 00:05:56.730 align:start position:0% volume so we're sending out the analysis code<00:05:54.400> into<00:05:54.940> in<00:05:55.090> dhaka<00:05:55.330> containers<00:05:55.900> to<00:05:56.590> the 00:05:56.730 --> 00:05:56.740 align:start position:0% code into in dhaka containers to the 00:05:56.740 --> 00:05:59.640 align:start position:0% code into in dhaka containers to the edge<00:05:56.889> and<00:05:57.219> at<00:05:57.940> the<00:05:58.180> edges<00:05:58.379> deployed<00:05:59.379> its 00:05:59.640 --> 00:05:59.650 align:start position:0% edge and at the edges deployed its 00:05:59.650 --> 00:06:02.700 align:start position:0% edge and at the edges deployed its unpacked<00:06:00.099> and<00:06:00.370> then<00:06:00.909> runs<00:06:01.180> and<00:06:01.419> the<00:06:01.539> edge<00:06:01.710> and 00:06:02.700 --> 00:06:02.710 align:start position:0% unpacked and then runs and the edge and 00:06:02.710 --> 00:06:04.290 align:start position:0% unpacked and then runs and the edge and what<00:06:02.889> it<00:06:03.009> sends<00:06:03.310> back<00:06:03.339> is<00:06:03.669> only<00:06:03.879> the<00:06:04.150> high 00:06:04.290 --> 00:06:04.300 align:start position:0% what it sends back is only the high 00:06:04.300 --> 00:06:06.659 align:start position:0% what it sends back is only the high value<00:06:04.750> low<00:06:04.930> volume<00:06:05.319> data<00:06:05.520> that's<00:06:06.520> in<00:06:06.610> a 00:06:06.659 --> 00:06:06.669 align:start position:0% value low volume data that's in a 00:06:06.669 --> 00:06:09.029 align:start position:0% value low volume data that's in a nutshell<00:06:06.759> what<00:06:07.240> we're<00:06:07.389> doing<00:06:07.629> and<00:06:07.800> you<00:06:08.800> could 00:06:09.029 --> 00:06:09.039 align:start position:0% nutshell what we're doing and you could 00:06:09.039 --> 00:06:11.760 align:start position:0% nutshell what we're doing and you could be<00:06:09.310> looking<00:06:09.610> up<00:06:09.759> much<00:06:10.690> more<00:06:10.719> explanation<00:06:11.529> and 00:06:11.760 --> 00:06:11.770 align:start position:0% be looking up much more explanation and 00:06:11.770 --> 00:06:13.619 align:start position:0% be looking up much more explanation and you<00:06:12.099> can<00:06:12.219> even<00:06:12.400> write<00:06:12.639> your<00:06:12.819> own<00:06:12.969> applications 00:06:13.619 --> 00:06:13.629 align:start position:0% you can even write your own applications 00:06:13.629 --> 00:06:15.959 align:start position:0% you can even write your own applications on<00:06:13.779> top<00:06:13.930> of<00:06:14.319> this<00:06:14.440> platform<00:06:14.710> and<00:06:15.279> this<00:06:15.789> is<00:06:15.879> the 00:06:15.959 --> 00:06:15.969 align:start position:0% on top of this platform and this is the 00:06:15.969 --> 00:06:17.879 align:start position:0% on top of this platform and this is the URL<00:06:16.089> when<00:06:16.509> you<00:06:16.629> can<00:06:16.779> go<00:06:16.930> to<00:06:16.990> and<00:06:17.379> check<00:06:17.740> out 00:06:17.879 --> 00:06:17.889 align:start position:0% URL when you can go to and check out 00:06:17.889 --> 00:06:19.469 align:start position:0% URL when you can go to and check out what<00:06:18.039> blue<00:06:18.219> horizon<00:06:18.639> can<00:06:18.759> do<00:06:18.879> for<00:06:19.029> you<00:06:19.120> we<00:06:19.270> will 00:06:19.469 --> 00:06:19.479 align:start position:0% what blue horizon can do for you we will 00:06:19.479 --> 00:06:21.329 align:start position:0% what blue horizon can do for you we will we<00:06:19.870> are<00:06:19.960> in<00:06:20.080> the<00:06:20.169> process<00:06:20.349> of<00:06:20.680> open<00:06:20.979> sourcing 00:06:21.329 --> 00:06:21.339 align:start position:0% we are in the process of open sourcing 00:06:21.339 --> 00:06:27.059 align:start position:0% we are in the process of open sourcing it<00:06:21.490> we<00:06:22.150> are<00:06:22.300> going<00:06:22.629> to<00:06:24.330> have<00:06:25.330> a<00:06:25.360> very<00:06:26.039> have<00:06:27.039> a 00:06:27.059 --> 00:06:27.069 align:start position:0% it we are going to have a very have a 00:06:27.069 --> 00:06:28.890 align:start position:0% it we are going to have a very have a new<00:06:27.250> website<00:06:27.460> to<00:06:27.789> where<00:06:28.389> we're<00:06:28.539> going<00:06:28.750> to 00:06:28.890 --> 00:06:28.900 align:start position:0% new website to where we're going to 00:06:28.900 --> 00:06:30.990 align:start position:0% new website to where we're going to explain<00:06:29.349> how<00:06:30.009> exactly<00:06:30.430> how<00:06:30.580> you<00:06:30.639> write<00:06:30.909> your 00:06:30.990 --> 00:06:31.000 align:start position:0% explain how exactly how you write your 00:06:31.000 --> 00:06:33.059 align:start position:0% explain how exactly how you write your platform<00:06:31.449> if<00:06:31.569> you<00:06:31.659> have<00:06:31.779> a<00:06:31.810> Raspberry<00:06:32.229> Pi<00:06:32.289> you 00:06:33.059 --> 00:06:33.069 align:start position:0% platform if you have a Raspberry Pi you 00:06:33.069 --> 00:06:34.649 align:start position:0% platform if you have a Raspberry Pi you can<00:06:33.250> immediately<00:06:33.430> take<00:06:34.060> part<00:06:34.300> in<00:06:34.419> the<00:06:34.479> use 00:06:34.649 --> 00:06:34.659 align:start position:0% can immediately take part in the use 00:06:34.659 --> 00:06:36.029 align:start position:0% can immediately take part in the use cases<00:06:34.900> that<00:06:35.169> we're<00:06:35.289> offering<00:06:35.620> their<00:06:35.830> we're 00:06:36.029 --> 00:06:36.039 align:start position:0% cases that we're offering their we're 00:06:36.039 --> 00:06:37.619 align:start position:0% cases that we're offering their we're doing<00:06:36.250> something<00:06:36.610> emulating<00:06:37.089> flightaware 00:06:37.619 --> 00:06:37.629 align:start position:0% doing something emulating flightaware 00:06:37.629 --> 00:06:40.079 align:start position:0% doing something emulating flightaware where<00:06:38.409> you<00:06:39.339> can<00:06:39.490> have<00:06:39.639> your<00:06:39.729> own<00:06:39.879> weather 00:06:40.079 --> 00:06:40.089 align:start position:0% where you can have your own weather 00:06:40.089 --> 00:06:43.079 align:start position:0% where you can have your own weather station<00:06:40.539> plugged<00:06:40.870> into<00:06:41.110> our<00:06:41.639> network<00:06:42.639> and 00:06:43.079 --> 00:06:43.089 align:start position:0% station plugged into our network and 00:06:43.089 --> 00:06:45.300 align:start position:0% station plugged into our network and what<00:06:44.020> we<00:06:44.110> have<00:06:44.229> now<00:06:44.409> is<00:06:44.440> a<00:06:44.650> map<00:06:44.889> where<00:06:45.129> you<00:06:45.190> can 00:06:45.300 --> 00:06:45.310 align:start position:0% what we have now is a map where you can 00:06:45.310 --> 00:06:47.820 align:start position:0% what we have now is a map where you can see<00:06:45.550> little<00:06:45.870> raspberry<00:06:46.870> PI's<00:06:47.289> running<00:06:47.680> all 00:06:47.820 --> 00:06:47.830 align:start position:0% see little raspberry PI's running all 00:06:47.830 --> 00:06:49.559 align:start position:0% see little raspberry PI's running all over<00:06:47.860> the<00:06:48.009> globe<00:06:48.159> and<00:06:48.460> picking<00:06:49.150> up<00:06:49.240> flight 00:06:49.559 --> 00:06:49.569 align:start position:0% over the globe and picking up flight 00:06:49.569 --> 00:06:53.670 align:start position:0% over the globe and picking up flight path<00:06:49.960> this<00:06:50.319> and<00:06:50.819> doing<00:06:51.819> networks<00:06:52.659> be<00:06:53.139> tests 00:06:53.670 --> 00:06:53.680 align:start position:0% path this and doing networks be tests 00:06:53.680 --> 00:06:55.559 align:start position:0% path this and doing networks be tests and<00:06:53.889> you<00:06:54.310> can<00:06:54.610> immediately<00:06:55.000> plug<00:06:55.419> your 00:06:55.559 --> 00:06:55.569 align:start position:0% and you can immediately plug your 00:06:55.569 --> 00:06:57.269 align:start position:0% and you can immediately plug your Raspberry<00:06:55.959> Pi<00:06:55.990> in<00:06:56.289> there<00:06:56.440> and<00:06:56.649> then<00:06:56.860> take<00:06:57.069> part 00:06:57.269 --> 00:06:57.279 align:start position:0% Raspberry Pi in there and then take part 00:06:57.279 --> 00:06:59.249 align:start position:0% Raspberry Pi in there and then take part in<00:06:57.339> this<00:06:57.490> and<00:06:57.699> we're<00:06:58.539> happy<00:06:58.659> about<00:06:58.810> everybody 00:06:59.249 --> 00:06:59.259 align:start position:0% in this and we're happy about everybody 00:06:59.259 --> 00:07:01.350 align:start position:0% in this and we're happy about everybody and<00:06:59.349> going<00:07:00.219> to<00:07:00.339> support<00:07:00.669> you<00:07:00.729> personally<00:07:00.909> to 00:07:01.350 --> 00:07:01.360 align:start position:0% and going to support you personally to 00:07:01.360 --> 00:07:05.820 align:start position:0% and going to support you personally to come<00:07:01.810> and<00:07:02.080> take<00:07:02.680> part<00:07:02.860> so<00:07:04.319> part<00:07:05.319> of<00:07:05.469> the<00:07:05.620> whole 00:07:05.820 --> 00:07:05.830 align:start position:0% come and take part so part of the whole 00:07:05.830 --> 00:07:08.760 align:start position:0% come and take part so part of the whole system<00:07:06.190> that<00:07:06.699> we<00:07:06.789> have<00:07:06.819> there<00:07:07.209> is<00:07:07.649> that<00:07:08.649> we 00:07:08.760 --> 00:07:08.770 align:start position:0% system that we have there is that we 00:07:08.770 --> 00:07:10.769 align:start position:0% system that we have there is that we have<00:07:08.919> a<00:07:08.949> sequence<00:07:09.339> that<00:07:09.639> is<00:07:09.969> going<00:07:10.419> through 00:07:10.769 --> 00:07:10.779 align:start position:0% have a sequence that is going through 00:07:10.779 --> 00:07:12.959 align:start position:0% have a sequence that is going through registration<00:07:11.110> of<00:07:11.709> Raspberry<00:07:12.099> Pi<00:07:12.159> and<00:07:12.610> the 00:07:12.959 --> 00:07:12.969 align:start position:0% registration of Raspberry Pi and the 00:07:12.969 --> 00:07:15.510 align:start position:0% registration of Raspberry Pi and the network<00:07:13.330> then<00:07:13.930> it<00:07:14.050> makes<00:07:14.229> an<00:07:14.380> offer<00:07:14.560> offering 00:07:15.510 --> 00:07:15.520 align:start position:0% network then it makes an offer offering 00:07:15.520 --> 00:07:17.820 align:start position:0% network then it makes an offer offering its<00:07:15.669> data<00:07:15.909> somebody<00:07:16.630> else<00:07:16.810> who's<00:07:17.229> playing<00:07:17.740> the 00:07:17.820 --> 00:07:17.830 align:start position:0% its data somebody else who's playing the 00:07:17.830 --> 00:07:20.430 align:start position:0% its data somebody else who's playing the entrepreneur<00:07:18.430> or<00:07:18.639> the<00:07:18.729> use<00:07:18.880> case<00:07:19.120> is<00:07:19.349> making<00:07:20.349> a 00:07:20.430 --> 00:07:20.440 align:start position:0% entrepreneur or the use case is making a 00:07:20.440 --> 00:07:22.199 align:start position:0% entrepreneur or the use case is making a bid<00:07:20.620> to<00:07:20.649> have<00:07:21.099> a<00:07:21.130> subscription<00:07:21.520> to<00:07:21.699> this<00:07:21.969> data 00:07:22.199 --> 00:07:22.209 align:start position:0% bid to have a subscription to this data 00:07:22.209 --> 00:07:23.490 align:start position:0% bid to have a subscription to this data stream<00:07:22.539> to<00:07:22.779> create<00:07:23.020> a<00:07:23.050> new<00:07:23.199> business<00:07:23.380> model 00:07:23.490 --> 00:07:23.500 align:start position:0% stream to create a new business model 00:07:23.500 --> 00:07:27.420 align:start position:0% stream to create a new business model format<00:07:24.130> or<00:07:24.310> make<00:07:25.089> a<00:07:25.120> new<00:07:25.270> offer<00:07:25.349> then<00:07:26.349> that<00:07:27.219> bid 00:07:27.420 --> 00:07:27.430 align:start position:0% format or make a new offer then that bid 00:07:27.430 --> 00:07:29.550 align:start position:0% format or make a new offer then that bid is<00:07:27.550> accepted<00:07:27.810> the<00:07:28.810> functionality<00:07:29.440> is 00:07:29.550 --> 00:07:29.560 align:start position:0% is accepted the functionality is 00:07:29.560 --> 00:07:32.249 align:start position:0% is accepted the functionality is deployed<00:07:29.979> the<00:07:30.849> analyzation<00:07:31.209> starts<00:07:31.959> and<00:07:32.139> then 00:07:32.249 --> 00:07:32.259 align:start position:0% deployed the analyzation starts and then 00:07:32.259 --> 00:07:34.379 align:start position:0% deployed the analyzation starts and then in<00:07:32.409> the<00:07:32.500> end<00:07:32.529> there's<00:07:32.770> payment<00:07:33.159> so<00:07:33.849> out<00:07:34.330> of 00:07:34.379 --> 00:07:34.389 align:start position:0% in the end there's payment so out of 00:07:34.389 --> 00:07:36.809 align:start position:0% in the end there's payment so out of these<00:07:34.719> things<00:07:35.050> the<00:07:35.979> deployment<00:07:36.580> and<00:07:36.669> then 00:07:36.809 --> 00:07:36.819 align:start position:0% these things the deployment and then 00:07:36.819 --> 00:07:38.999 align:start position:0% these things the deployment and then allah<00:07:37.060> is<00:07:37.120> analyzing<00:07:38.020> is<00:07:38.199> something<00:07:38.649> that<00:07:38.889> we 00:07:38.999 --> 00:07:39.009 align:start position:0% allah is analyzing is something that we 00:07:39.009 --> 00:07:40.469 align:start position:0% allah is analyzing is something that we do<00:07:39.130> completely<00:07:39.459> peer-to-peer<00:07:39.759> we<00:07:40.060> don't<00:07:40.240> need 00:07:40.469 --> 00:07:40.479 align:start position:0% do completely peer-to-peer we don't need 00:07:40.479 --> 00:07:42.269 align:start position:0% do completely peer-to-peer we don't need the<00:07:40.569> blockchain<00:07:40.779> for<00:07:41.139> that<00:07:41.289> and<00:07:41.500> the<00:07:42.130> reality 00:07:42.269 --> 00:07:42.279 align:start position:0% the blockchain for that and the reality 00:07:42.279 --> 00:07:44.909 align:start position:0% the blockchain for that and the reality is<00:07:42.759> that<00:07:43.449> even<00:07:43.839> now<00:07:44.080> we're<00:07:44.349> even<00:07:44.500> taking<00:07:44.889> the 00:07:44.909 --> 00:07:44.919 align:start position:0% is that even now we're even taking the 00:07:44.919 --> 00:07:46.559 align:start position:0% is that even now we're even taking the blockchain<00:07:45.190> out<00:07:45.520> of<00:07:45.669> the<00:07:45.789> equation<00:07:46.000> for<00:07:46.360> the 00:07:46.559 --> 00:07:46.569 align:start position:0% blockchain out of the equation for the 00:07:46.569 --> 00:07:48.449 align:start position:0% blockchain out of the equation for the offer<00:07:46.719> and<00:07:46.930> the<00:07:47.020> bid<00:07:47.199> and<00:07:47.409> creating<00:07:48.370> the 00:07:48.449 --> 00:07:48.459 align:start position:0% offer and the bid and creating the 00:07:48.459 --> 00:07:51.120 align:start position:0% offer and the bid and creating the centralized<00:07:48.940> because<00:07:49.870> it's<00:07:50.740> just<00:07:51.009> not 00:07:51.120 --> 00:07:51.130 align:start position:0% centralized because it's just not 00:07:51.130 --> 00:07:52.529 align:start position:0% centralized because it's just not scaling<00:07:51.520> it's<00:07:51.639> just<00:07:51.789> not<00:07:51.940> fast<00:07:52.089> enough<00:07:52.300> at 00:07:52.529 --> 00:07:52.539 align:start position:0% scaling it's just not fast enough at 00:07:52.539 --> 00:07:53.969 align:start position:0% scaling it's just not fast enough at this<00:07:52.630> point<00:07:52.719> and<00:07:53.110> because<00:07:53.529> we<00:07:53.649> want<00:07:53.800> to<00:07:53.860> have<00:07:53.949> a 00:07:53.969 --> 00:07:53.979 align:start position:0% this point and because we want to have a 00:07:53.979 --> 00:07:56.219 align:start position:0% this point and because we want to have a product<00:07:54.399> that<00:07:54.610> people<00:07:54.880> can<00:07:55.240> use<00:07:55.569> we're 00:07:56.219 --> 00:07:56.229 align:start position:0% product that people can use we're 00:07:56.229 --> 00:07:59.969 align:start position:0% product that people can use we're backtracking<00:07:56.589> at<00:07:56.919> that<00:07:57.190> point<00:07:58.349> if<00:07:59.349> we're 00:07:59.969 --> 00:07:59.979 align:start position:0% backtracking at that point if we're 00:07:59.979 --> 00:08:01.829 align:start position:0% backtracking at that point if we're looking<00:08:00.039> at<00:08:00.310> smart<00:08:00.580> contracts<00:08:01.120> ideally<00:08:01.659> to 00:08:01.829 --> 00:08:01.839 align:start position:0% looking at smart contracts ideally to 00:08:01.839 --> 00:08:04.110 align:start position:0% looking at smart contracts ideally to have<00:08:02.020> smart<00:08:02.409> contracts<00:08:02.800> full<00:08:03.009> circle<00:08:03.430> you 00:08:04.110 --> 00:08:04.120 align:start position:0% have smart contracts full circle you 00:08:04.120 --> 00:08:05.639 align:start position:0% have smart contracts full circle you want<00:08:04.300> to<00:08:04.360> have<00:08:04.509> something<00:08:04.839> that<00:08:05.289> goes<00:08:05.440> like 00:08:05.639 --> 00:08:05.649 align:start position:0% want to have something that goes like 00:08:05.649 --> 00:08:07.949 align:start position:0% want to have something that goes like this<00:08:05.800> you<00:08:06.039> have<00:08:06.310> an<00:08:06.520> offer<00:08:06.699> it<00:08:07.120> is<00:08:07.479> being<00:08:07.659> it's 00:08:07.949 --> 00:08:07.959 align:start position:0% this you have an offer it is being it's 00:08:07.959 --> 00:08:10.230 align:start position:0% this you have an offer it is being it's agreed<00:08:08.259> to<00:08:08.440> then<00:08:09.159> at<00:08:09.310> some<00:08:09.520> point<00:08:09.580> you<00:08:09.879> deliver 00:08:10.230 --> 00:08:10.240 align:start position:0% agreed to then at some point you deliver 00:08:10.240 --> 00:08:14.269 align:start position:0% agreed to then at some point you deliver the<00:08:10.449> data<00:08:10.800> thank<00:08:11.800> you<00:08:11.889> for<00:08:12.009> low<00:08:12.099> light<00:08:12.129> show 00:08:14.269 --> 00:08:14.279 align:start position:0% the data thank you for low light show 00:08:14.279 --> 00:08:16.889 align:start position:0% the data thank you for low light show then<00:08:15.279> you<00:08:15.430> then<00:08:15.759> at<00:08:15.940> some<00:08:16.089> point<00:08:16.149> you<00:08:16.479> confirm 00:08:16.889 --> 00:08:16.899 align:start position:0% then you then at some point you confirm 00:08:16.899 --> 00:08:19.260 align:start position:0% then you then at some point you confirm and<00:08:17.080> then<00:08:17.199> the<00:08:17.349> payment<00:08:17.740> comes<00:08:17.919> and<00:08:18.219> what<00:08:19.149> you 00:08:19.260 --> 00:08:19.270 align:start position:0% and then the payment comes and what you 00:08:19.270 --> 00:08:20.939 align:start position:0% and then the payment comes and what you really<00:08:19.449> want<00:08:19.690> to<00:08:19.750> have<00:08:20.020> to<00:08:20.199> have<00:08:20.319> a<00:08:20.349> real<00:08:20.589> smart 00:08:20.939 --> 00:08:20.949 align:start position:0% really want to have to have a real smart 00:08:20.949 --> 00:08:22.889 align:start position:0% really want to have to have a real smart contract<00:08:21.430> is<00:08:21.550> that<00:08:21.879> the<00:08:21.969> confirmation<00:08:22.629> comes 00:08:22.889 --> 00:08:22.899 align:start position:0% contract is that the confirmation comes 00:08:22.899 --> 00:08:25.159 align:start position:0% contract is that the confirmation comes from<00:08:23.469> a<00:08:23.560> third-party<00:08:23.919> trusted<00:08:24.520> Oracle<00:08:24.940> or 00:08:25.159 --> 00:08:25.169 align:start position:0% from a third-party trusted Oracle or 00:08:25.169 --> 00:08:27.839 align:start position:0% from a third-party trusted Oracle or ideally<00:08:26.169> even<00:08:26.440> you<00:08:26.529> can<00:08:26.740> have<00:08:26.949> in<00:08:27.159> solidity 00:08:27.839 --> 00:08:27.849 align:start position:0% ideally even you can have in solidity 00:08:27.849 --> 00:08:30.180 align:start position:0% ideally even you can have in solidity code<00:08:28.659> that<00:08:28.959> verifies<00:08:29.349> whether<00:08:29.560> the<00:08:29.770> data<00:08:29.889> that 00:08:30.180 --> 00:08:30.190 align:start position:0% code that verifies whether the data that 00:08:30.190 --> 00:08:31.409 align:start position:0% code that verifies whether the data that has<00:08:30.339> been<00:08:30.370> delivered<00:08:30.759> is<00:08:31.000> really<00:08:31.240> worth 00:08:31.409 --> 00:08:31.419 align:start position:0% has been delivered is really worth 00:08:31.419 --> 00:08:33.569 align:start position:0% has been delivered is really worth something<00:08:31.930> and<00:08:32.050> then<00:08:32.229> does<00:08:33.010> the<00:08:33.039> payment<00:08:33.459> or 00:08:33.569 --> 00:08:33.579 align:start position:0% something and then does the payment or 00:08:33.579 --> 00:08:36.000 align:start position:0% something and then does the payment or refund<00:08:34.000> this<00:08:34.719> could<00:08:34.899> be<00:08:34.930> thinkable<00:08:35.740> if<00:08:35.919> you 00:08:36.000 --> 00:08:36.010 align:start position:0% refund this could be thinkable if you 00:08:36.010 --> 00:08:37.709 align:start position:0% refund this could be thinkable if you have<00:08:36.130> weather<00:08:36.370> data<00:08:36.669> you<00:08:37.300> could<00:08:37.479> verify 00:08:37.709 --> 00:08:37.719 align:start position:0% have weather data you could verify 00:08:37.719 --> 00:08:40.709 align:start position:0% have weather data you could verify whether<00:08:38.380> it's<00:08:38.680> an<00:08:38.800> total<00:08:39.310> outlier<00:08:39.719> compared 00:08:40.709 --> 00:08:40.719 align:start position:0% whether it's an total outlier compared 00:08:40.719 --> 00:08:41.670 align:start position:0% whether it's an total outlier compared to<00:08:40.779> its<00:08:40.899> neighbors<00:08:41.169> then<00:08:41.409> it's<00:08:41.529> probably 00:08:41.670 --> 00:08:41.680 align:start position:0% to its neighbors then it's probably 00:08:41.680 --> 00:08:43.439 align:start position:0% to its neighbors then it's probably noise<00:08:41.949> and<00:08:42.219> then<00:08:42.310> you<00:08:42.399> don't<00:08:42.579> pay<00:08:42.789> but<00:08:43.360> the 00:08:43.439 --> 00:08:43.449 align:start position:0% noise and then you don't pay but the 00:08:43.449 --> 00:08:45.000 align:start position:0% noise and then you don't pay but the reality<00:08:43.779> of<00:08:43.810> it<00:08:43.959> is<00:08:44.019> as<00:08:44.290> it<00:08:44.709> is<00:08:44.740> right<00:08:44.949> now 00:08:45.000 --> 00:08:45.010 align:start position:0% reality of it is as it is right now 00:08:45.010 --> 00:08:46.559 align:start position:0% reality of it is as it is right now we're<00:08:45.490> cutting<00:08:45.790> this<00:08:45.910> out<00:08:46.089> and<00:08:46.300> what<00:08:46.420> we're 00:08:46.559 --> 00:08:46.569 align:start position:0% we're cutting this out and what we're 00:08:46.569 --> 00:08:48.240 align:start position:0% we're cutting this out and what we're really<00:08:46.690> using<00:08:46.930> of<00:08:47.290> smart<00:08:47.529> contracts<00:08:47.920> is<00:08:48.040> only 00:08:48.240 --> 00:08:48.250 align:start position:0% really using of smart contracts is only 00:08:48.250 --> 00:08:51.210 align:start position:0% really using of smart contracts is only this<00:08:48.490> they<00:08:49.209> offer<00:08:49.709> agreement<00:08:50.709> and<00:08:50.949> then<00:08:51.100> in 00:08:51.210 --> 00:08:51.220 align:start position:0% this they offer agreement and then in 00:08:51.220 --> 00:08:53.040 align:start position:0% this they offer agreement and then in the<00:08:51.310> NDP<00:08:51.670> and<00:08:51.850> again<00:08:52.149> we<00:08:52.300> have<00:08:52.480> this<00:08:52.600> gap<00:08:52.810> there 00:08:53.040 --> 00:08:53.050 align:start position:0% the NDP and again we have this gap there 00:08:53.050 --> 00:08:57.509 align:start position:0% the NDP and again we have this gap there so<00:08:53.769> in<00:08:54.250> a<00:08:55.000> sad<00:08:55.240> way<00:08:55.529> you<00:08:56.529> could<00:08:56.680> say<00:08:56.860> that<00:08:56.890> also 00:08:57.509 --> 00:08:57.519 align:start position:0% so in a sad way you could say that also 00:08:57.519 --> 00:08:59.370 align:start position:0% so in a sad way you could say that also at<00:08:57.730> Blue<00:08:57.880> Horizon<00:08:58.240> we're<00:08:58.360> just<00:08:58.540> using<00:08:58.750> the 00:08:59.370 --> 00:08:59.380 align:start position:0% at Blue Horizon we're just using the 00:08:59.380 --> 00:09:00.660 align:start position:0% at Blue Horizon we're just using the blockchain<00:08:59.620> very<00:08:59.949> much<00:09:00.100> as<00:09:00.309> a<00:09:00.339> distributor 00:09:00.660 --> 00:09:00.670 align:start position:0% blockchain very much as a distributor 00:09:00.670 --> 00:09:04.009 align:start position:0% blockchain very much as a distributor letter<00:09:01.059> and<00:09:01.770> we<00:09:02.770> are 00:09:04.009 --> 00:09:04.019 align:start position:0% letter and we are 00:09:04.019 --> 00:09:05.479 align:start position:0% letter and we are using<00:09:04.230> it<00:09:04.350> certainly<00:09:04.679> for<00:09:04.860> payment<00:09:05.249> than<00:09:05.339> in 00:09:05.479 --> 00:09:05.489 align:start position:0% using it certainly for payment than in 00:09:05.489 --> 00:09:07.609 align:start position:0% using it certainly for payment than in the<00:09:05.610> end<00:09:05.759> but<00:09:06.660> this<00:09:06.869> is<00:09:07.019> also<00:09:07.170> because<00:09:07.529> the 00:09:07.609 --> 00:09:07.619 align:start position:0% the end but this is also because the 00:09:07.619 --> 00:09:11.689 align:start position:0% the end but this is also because the reality<00:09:07.769> of<00:09:08.129> our<00:09:08.550> project<00:09:09.509> was<00:09:09.929> that<00:09:10.439> we<00:09:11.339> have 00:09:11.689 --> 00:09:11.699 align:start position:0% reality of our project was that we have 00:09:11.699 --> 00:09:13.519 align:start position:0% reality of our project was that we have technology<00:09:12.059> in<00:09:12.540> search<00:09:12.720> of<00:09:12.749> a<00:09:12.959> project<00:09:13.379> and 00:09:13.519 --> 00:09:13.529 align:start position:0% technology in search of a project and 00:09:13.529 --> 00:09:16.819 align:start position:0% technology in search of a project and not<00:09:13.649> the<00:09:13.769> other<00:09:13.920> way<00:09:14.040> around<00:09:14.689> and<00:09:15.709> we<00:09:16.709> were 00:09:16.819 --> 00:09:16.829 align:start position:0% not the other way around and we were 00:09:16.829 --> 00:09:18.769 align:start position:0% not the other way around and we were basically<00:09:16.980> given<00:09:17.579> a<00:09:17.610> lot<00:09:17.790> a<00:09:18.179> lot<00:09:18.389> of<00:09:18.540> stuff 00:09:18.769 --> 00:09:18.779 align:start position:0% basically given a lot a lot of stuff 00:09:18.779 --> 00:09:20.479 align:start position:0% basically given a lot a lot of stuff that<00:09:19.230> was<00:09:19.529> supposed<00:09:19.889> to<00:09:19.980> be<00:09:20.069> in<00:09:20.160> that<00:09:20.189> project 00:09:20.479 --> 00:09:20.489 align:start position:0% that was supposed to be in that project 00:09:20.489 --> 00:09:22.910 align:start position:0% that was supposed to be in that project and<00:09:20.879> this<00:09:21.149> way<00:09:21.329> it<00:09:21.509> was<00:09:21.689> initially<00:09:21.929> called<00:09:22.230> MTN 00:09:22.910 --> 00:09:22.920 align:start position:0% and this way it was initially called MTN 00:09:22.920 --> 00:09:27.710 align:start position:0% and this way it was initially called MTN or<00:09:23.339> multiplying<00:09:24.089> things<00:09:24.389> needlessly<00:09:24.839> I<00:09:26.720> want 00:09:27.710 --> 00:09:27.720 align:start position:0% or multiplying things needlessly I want 00:09:27.720 --> 00:09:30.739 align:start position:0% or multiplying things needlessly I want to<00:09:27.779> share<00:09:27.989> very<00:09:28.319> quickly<00:09:28.679> some<00:09:29.519> problems<00:09:30.360> that 00:09:30.739 --> 00:09:30.749 align:start position:0% to share very quickly some problems that 00:09:30.749 --> 00:09:32.720 align:start position:0% to share very quickly some problems that we<00:09:30.869> found<00:09:31.049> with<00:09:31.319> the<00:09:31.350> theorem<00:09:31.739> and<00:09:31.889> some<00:09:32.489> of<00:09:32.610> it 00:09:32.720 --> 00:09:32.730 align:start position:0% we found with the theorem and some of it 00:09:32.730 --> 00:09:34.910 align:start position:0% we found with the theorem and some of it is<00:09:32.819> not<00:09:32.999> so<00:09:33.149> surprising<00:09:33.660> speed<00:09:33.929> is<00:09:34.110> really 00:09:34.910 --> 00:09:34.920 align:start position:0% is not so surprising speed is really 00:09:34.920 --> 00:09:37.720 align:start position:0% is not so surprising speed is really standing<00:09:35.279> out<00:09:35.429> in<00:09:35.639> a<00:09:35.730> way<00:09:35.850> that<00:09:36.779> can<00:09:37.529> be 00:09:37.720 --> 00:09:37.730 align:start position:0% standing out in a way that can be 00:09:37.730 --> 00:09:41.900 align:start position:0% standing out in a way that can be pinpointed<00:09:38.730> to<00:09:39.209> it's<00:09:39.689> the<00:09:40.079> right<00:09:40.889> how<00:09:41.459> slow<00:09:41.759> it 00:09:41.900 --> 00:09:41.910 align:start position:0% pinpointed to it's the right how slow it 00:09:41.910 --> 00:09:44.689 align:start position:0% pinpointed to it's the right how slow it is<00:09:41.999> to<00:09:42.209> write<00:09:42.449> as<00:09:42.720> this<00:09:43.139> very<00:09:43.410> is<00:09:43.679> exactly<00:09:44.489> what 00:09:44.689 --> 00:09:44.699 align:start position:0% is to write as this very is exactly what 00:09:44.699 --> 00:09:46.939 align:start position:0% is to write as this very is exactly what making<00:09:45.089> the<00:09:45.269> problem<00:09:45.449> scalability<00:09:46.379> I<00:09:46.619> don't 00:09:46.939 --> 00:09:46.949 align:start position:0% making the problem scalability I don't 00:09:46.949 --> 00:09:48.829 align:start position:0% making the problem scalability I don't have<00:09:47.100> to<00:09:47.220> explain<00:09:47.399> that<00:09:47.579> but<00:09:48.389> of<00:09:48.569> course<00:09:48.749> we 00:09:48.829 --> 00:09:48.839 align:start position:0% have to explain that but of course we 00:09:48.839 --> 00:09:50.809 align:start position:0% have to explain that but of course we ran<00:09:48.989> into<00:09:49.110> this<00:09:49.350> somewhat<00:09:50.069> unexpected<00:09:50.699> we 00:09:50.809 --> 00:09:50.819 align:start position:0% ran into this somewhat unexpected we 00:09:50.819 --> 00:09:52.819 align:start position:0% ran into this somewhat unexpected we really<00:09:51.089> have<00:09:51.239> huge<00:09:51.509> bandwidth<00:09:51.839> problems<00:09:52.319> but 00:09:52.819 --> 00:09:52.829 align:start position:0% really have huge bandwidth problems but 00:09:52.829 --> 00:09:55.759 align:start position:0% really have huge bandwidth problems but event<00:09:53.129> that<00:09:53.429> I<00:09:53.839> healed<00:09:54.839> more<00:09:55.199> or<00:09:55.319> less<00:09:55.470> by<00:09:55.709> the 00:09:55.759 --> 00:09:55.769 align:start position:0% event that I healed more or less by the 00:09:55.769 --> 00:09:58.850 align:start position:0% event that I healed more or less by the light<00:09:56.429> client<00:09:56.850> and<00:09:57.029> then<00:09:57.660> of<00:09:57.779> course<00:09:57.860> yeah 00:09:58.850 --> 00:09:58.860 align:start position:0% light client and then of course yeah 00:09:58.860 --> 00:10:01.340 align:start position:0% light client and then of course yeah scale<00:09:59.189> I<00:09:59.369> said<00:09:59.579> that<00:09:59.730> before<00:10:00.019> so<00:10:01.019> and<00:10:01.259> it's 00:10:01.340 --> 00:10:01.350 align:start position:0% scale I said that before so and it's 00:10:01.350 --> 00:10:03.049 align:start position:0% scale I said that before so and it's also<00:10:01.529> a<00:10:01.619> little<00:10:01.799> bit<00:10:01.920> to<00:10:02.160> doge<00:10:02.399> I<00:10:02.670> won't<00:10:02.939> get 00:10:03.049 --> 00:10:03.059 align:start position:0% also a little bit to doge I won't get 00:10:03.059 --> 00:10:04.999 align:start position:0% also a little bit to doge I won't get into<00:10:03.179> into<00:10:03.720> that<00:10:03.869> but<00:10:04.139> sometimes<00:10:04.649> there<00:10:04.920> are 00:10:04.999 --> 00:10:05.009 align:start position:0% into into that but sometimes there are 00:10:05.009 --> 00:10:07.549 align:start position:0% into into that but sometimes there are inducing<00:10:05.399> crises<00:10:05.790> that<00:10:06.059> are<00:10:06.239> fun<00:10:07.110> for<00:10:07.410> the 00:10:07.549 --> 00:10:07.559 align:start position:0% inducing crises that are fun for the 00:10:07.559 --> 00:10:10.129 align:start position:0% inducing crises that are fun for the guys<00:10:07.920> who<00:10:08.249> make<00:10:08.459> it<00:10:08.639> but<00:10:08.879> to<00:10:09.269> use<00:10:09.449> it<00:10:09.629> it's<00:10:09.809> not 00:10:10.129 --> 00:10:10.139 align:start position:0% guys who make it but to use it it's not 00:10:10.139 --> 00:10:12.410 align:start position:0% guys who make it but to use it it's not sometimes<00:10:10.619> not<00:10:10.740> helpful<00:10:10.980> then<00:10:11.879> we<00:10:11.999> sometimes 00:10:12.410 --> 00:10:12.420 align:start position:0% sometimes not helpful then we sometimes 00:10:12.420 --> 00:10:14.600 align:start position:0% sometimes not helpful then we sometimes run<00:10:12.629> into<00:10:12.660> bugs<00:10:13.019> to<00:10:13.319> that<00:10:13.889> we<00:10:13.980> felt<00:10:14.160> like<00:10:14.399> if 00:10:14.600 --> 00:10:14.610 align:start position:0% run into bugs to that we felt like if 00:10:14.610 --> 00:10:18.079 align:start position:0% run into bugs to that we felt like if somebody<00:10:15.059> was<00:10:15.600> really<00:10:15.929> using<00:10:16.290> athyrium<00:10:17.089> how 00:10:18.079 --> 00:10:18.089 align:start position:0% somebody was really using athyrium how 00:10:18.089 --> 00:10:20.230 align:start position:0% somebody was really using athyrium how can<00:10:18.269> possibly<00:10:18.629> be<00:10:18.809> this<00:10:18.959> box<00:10:19.199> still<00:10:19.439> in<00:10:19.559> there 00:10:20.230 --> 00:10:20.240 align:start position:0% can possibly be this box still in there 00:10:20.240 --> 00:10:23.689 align:start position:0% can possibly be this box still in there the<00:10:21.240> strength<00:10:21.799> availability<00:10:22.799> that<00:10:23.399> we<00:10:23.490> have<00:10:23.670> a 00:10:23.689 --> 00:10:23.699 align:start position:0% the strength availability that we have a 00:10:23.699 --> 00:10:25.189 align:start position:0% the strength availability that we have a contract<00:10:24.149> language<00:10:24.389> that<00:10:24.749> you<00:10:24.869> can<00:10:25.019> actually 00:10:25.189 --> 00:10:25.199 align:start position:0% contract language that you can actually 00:10:25.199 --> 00:10:28.519 align:start position:0% contract language that you can actually use<00:10:25.850> and<00:10:26.850> to<00:10:27.119> write<00:10:27.269> complex<00:10:27.540> and<00:10:28.049> resilience 00:10:28.519 --> 00:10:28.529 align:start position:0% use and to write complex and resilience 00:10:28.529 --> 00:10:30.859 align:start position:0% use and to write complex and resilience you<00:10:28.769> can<00:10:28.949> knock<00:10:29.129> out<00:10:29.249> all<00:10:29.339> the<00:10:29.610> nodes<00:10:29.819> with<00:10:30.660> one 00:10:30.859 --> 00:10:30.869 align:start position:0% you can knock out all the nodes with one 00:10:30.869 --> 00:10:32.720 align:start position:0% you can knock out all the nodes with one load<00:10:31.079> survives<00:10:31.470> is<00:10:31.799> still<00:10:32.160> going<00:10:32.309> to<00:10:32.490> survive 00:10:32.720 --> 00:10:32.730 align:start position:0% load survives is still going to survive 00:10:32.730 --> 00:10:35.809 align:start position:0% load survives is still going to survive but<00:10:33.689> still<00:10:33.929> coming<00:10:34.290> back<00:10:34.470> to<00:10:34.589> the<00:10:34.709> DLT<00:10:34.949> on 00:10:35.809 --> 00:10:35.819 align:start position:0% but still coming back to the DLT on 00:10:35.819 --> 00:10:37.970 align:start position:0% but still coming back to the DLT on smart<00:10:36.629> contract<00:10:37.019> that<00:10:37.110> permit<00:10:37.470> realization 00:10:37.970 --> 00:10:37.980 align:start position:0% smart contract that permit realization 00:10:37.980 --> 00:10:41.539 align:start position:0% smart contract that permit realization if<00:10:38.790> you<00:10:38.939> have<00:10:39.089> functional<00:10:39.509> programming<00:10:40.549> then 00:10:41.539 --> 00:10:41.549 align:start position:0% if you have functional programming then 00:10:41.549 --> 00:10:43.489 align:start position:0% if you have functional programming then you<00:10:41.939> have<00:10:42.089> first-class<00:10:42.420> citizen<00:10:43.019> functions 00:10:43.489 --> 00:10:43.499 align:start position:0% you have first-class citizen functions 00:10:43.499 --> 00:10:45.379 align:start position:0% you have first-class citizen functions and<00:10:43.740> if<00:10:44.189> you<00:10:44.309> have<00:10:44.429> a<00:10:44.459> function<00:10:44.730> you<00:10:45.179> just 00:10:45.379 --> 00:10:45.389 align:start position:0% and if you have a function you just 00:10:45.389 --> 00:10:47.840 align:start position:0% and if you have a function you just don't<00:10:45.749> Merson<00:10:46.350> you<00:10:46.649> don't<00:10:46.829> just<00:10:47.160> throw<00:10:47.309> static 00:10:47.840 --> 00:10:47.850 align:start position:0% don't Merson you don't just throw static 00:10:47.850 --> 00:10:50.030 align:start position:0% don't Merson you don't just throw static parameters<00:10:48.389> in<00:10:48.600> there<00:10:48.779> you<00:10:49.290> want<00:10:49.799> to<00:10:49.889> have 00:10:50.030 --> 00:10:50.040 align:start position:0% parameters in there you want to have 00:10:50.040 --> 00:10:51.289 align:start position:0% parameters in there you want to have functions<00:10:50.429> going<00:10:50.639> in<00:10:50.730> there<00:10:50.879> if<00:10:51.029> this<00:10:51.179> is<00:10:51.269> a 00:10:51.289 --> 00:10:51.299 align:start position:0% functions going in there if this is a 00:10:51.299 --> 00:10:53.809 align:start position:0% functions going in there if this is a function<00:10:51.779> and<00:10:52.019> you<00:10:52.559> have<00:10:52.740> static<00:10:53.339> parameters 00:10:53.809 --> 00:10:53.819 align:start position:0% function and you have static parameters 00:10:53.819 --> 00:10:55.519 align:start position:0% function and you have static parameters you<00:10:53.970> can<00:10:53.999> define<00:10:54.629> a<00:10:54.689> car<00:10:54.959> but<00:10:55.199> if<00:10:55.290> you<00:10:55.350> can 00:10:55.519 --> 00:10:55.529 align:start position:0% you can define a car but if you can 00:10:55.529 --> 00:10:57.949 align:start position:0% you can define a car but if you can throw<00:10:55.949> other<00:10:56.189> functions<00:10:56.759> in<00:10:56.879> there<00:10:57.089> you<00:10:57.749> can 00:10:57.949 --> 00:10:57.959 align:start position:0% throw other functions in there you can 00:10:57.959 --> 00:10:59.689 align:start position:0% throw other functions in there you can have<00:10:58.169> a<00:10:58.199> whole<00:10:58.619> new<00:10:58.889> universe<00:10:59.309> of<00:10:59.490> stuff 00:10:59.689 --> 00:10:59.699 align:start position:0% have a whole new universe of stuff 00:10:59.699 --> 00:11:01.850 align:start position:0% have a whole new universe of stuff happening<00:11:00.119> just<00:11:00.389> from<00:11:00.600> one<00:11:00.779> starting<00:11:01.619> point 00:11:01.850 --> 00:11:01.860 align:start position:0% happening just from one starting point 00:11:01.860 --> 00:11:04.340 align:start position:0% happening just from one starting point and<00:11:02.069> so<00:11:02.610> what<00:11:03.209> you<00:11:03.299> can<00:11:03.419> do<00:11:03.569> now<00:11:03.779> is<00:11:03.809> if<00:11:04.259> you 00:11:04.340 --> 00:11:04.350 align:start position:0% and so what you can do now is if you 00:11:04.350 --> 00:11:06.289 align:start position:0% and so what you can do now is if you have<00:11:04.470> an<00:11:04.559> init<00:11:04.799> function<00:11:04.829> of<00:11:05.399> our<00:11:05.669> platform 00:11:06.289 --> 00:11:06.299 align:start position:0% have an init function of our platform 00:11:06.299 --> 00:11:07.879 align:start position:0% have an init function of our platform you<00:11:06.509> can<00:11:06.540> give<00:11:06.809> it<00:11:06.839> a<00:11:06.959> static<00:11:07.199> parameter<00:11:07.769> and 00:11:07.879 --> 00:11:07.889 align:start position:0% you can give it a static parameter and 00:11:07.889 --> 00:11:09.409 align:start position:0% you can give it a static parameter and that's<00:11:08.069> the<00:11:08.189> prize<00:11:08.399> in<00:11:08.610> this<00:11:08.699> case<00:11:08.939> this<00:11:09.239> could 00:11:09.409 --> 00:11:09.419 align:start position:0% that's the prize in this case this could 00:11:09.419 --> 00:11:11.659 align:start position:0% that's the prize in this case this could look<00:11:09.509> like<00:11:09.569> this<00:11:09.869> but<00:11:10.709> if<00:11:10.860> you<00:11:10.980> have<00:11:11.189> a<00:11:11.459> little 00:11:11.659 --> 00:11:11.669 align:start position:0% look like this but if you have a little 00:11:11.669 --> 00:11:13.189 align:start position:0% look like this but if you have a little bit<00:11:11.819> more<00:11:12.059> then<00:11:12.689> you<00:11:12.779> can<00:11:12.899> have<00:11:13.049> an 00:11:13.189 --> 00:11:13.199 align:start position:0% bit more then you can have an 00:11:13.199 --> 00:11:14.840 align:start position:0% bit more then you can have an acknowledgement<00:11:13.799> function<00:11:14.279> that<00:11:14.579> is<00:11:14.699> then 00:11:14.840 --> 00:11:14.850 align:start position:0% acknowledgement function that is then 00:11:14.850 --> 00:11:15.970 align:start position:0% acknowledgement function that is then called<00:11:15.119> in<00:11:15.419> the<00:11:15.509> last 00:11:15.970 --> 00:11:15.980 align:start position:0% called in the last 00:11:15.980 --> 00:11:18.070 align:start position:0% called in the last line<00:11:16.460> are<00:11:16.700> down<00:11:16.880> there<00:11:17.120> and<00:11:17.330> it's<00:11:17.660> giving<00:11:17.900> back 00:11:18.070 --> 00:11:18.080 align:start position:0% line are down there and it's giving back 00:11:18.080 --> 00:11:20.140 align:start position:0% line are down there and it's giving back as<00:11:18.290> status<00:11:18.650> to<00:11:19.130> the<00:11:19.250> app<00:11:19.400> developer<00:11:19.940> who<00:11:20.090> is 00:11:20.140 --> 00:11:20.150 align:start position:0% as status to the app developer who is 00:11:20.150 --> 00:11:22.570 align:start position:0% as status to the app developer who is using<00:11:20.330> our<00:11:20.540> platform<00:11:20.710> now<00:11:21.710> you<00:11:21.770> can<00:11:22.130> even<00:11:22.400> go 00:11:22.570 --> 00:11:22.580 align:start position:0% using our platform now you can even go 00:11:22.580 --> 00:11:25.000 align:start position:0% using our platform now you can even go faster<00:11:23.030> and<00:11:23.480> can<00:11:23.750> have<00:11:23.960> the<00:11:24.110> whole<00:11:24.320> my<00:11:24.710> init 00:11:25.000 --> 00:11:25.010 align:start position:0% faster and can have the whole my init 00:11:25.010 --> 00:11:26.950 align:start position:0% faster and can have the whole my init function<00:11:25.040> as<00:11:25.610> part<00:11:25.910> of<00:11:26.030> the<00:11:26.150> app<00:11:26.300> instead<00:11:26.840> of 00:11:26.950 --> 00:11:26.960 align:start position:0% function as part of the app instead of 00:11:26.960 --> 00:11:29.080 align:start position:0% function as part of the app instead of the<00:11:27.080> platform<00:11:27.530> so<00:11:28.010> the<00:11:28.430> whole<00:11:28.580> platform<00:11:28.850> is 00:11:29.080 --> 00:11:29.090 align:start position:0% the platform so the whole platform is 00:11:29.090 --> 00:11:30.760 align:start position:0% the platform so the whole platform is calling<00:11:29.420> back<00:11:29.540> into<00:11:29.780> the<00:11:29.900> app<00:11:29.990> and<00:11:30.260> now<00:11:30.680> it 00:11:30.760 --> 00:11:30.770 align:start position:0% calling back into the app and now it 00:11:30.770 --> 00:11:32.710 align:start position:0% calling back into the app and now it gets<00:11:30.860> interesting<00:11:31.040> because<00:11:31.550> you<00:11:31.910> can<00:11:32.540> also 00:11:32.710 --> 00:11:32.720 align:start position:0% gets interesting because you can also 00:11:32.720 --> 00:11:35.470 align:start position:0% gets interesting because you can also have<00:11:32.960> caused<00:11:33.230> get<00:11:33.680> beyond<00:11:34.160> the<00:11:34.550> convention<00:11:35.360> of 00:11:35.470 --> 00:11:35.480 align:start position:0% have caused get beyond the convention of 00:11:35.480 --> 00:11:37.210 align:start position:0% have caused get beyond the convention of having<00:11:35.750> an<00:11:35.810> init<00:11:36.020> function<00:11:36.050> you<00:11:36.830> could<00:11:36.980> do<00:11:37.100> it 00:11:37.210 --> 00:11:37.220 align:start position:0% having an init function you could do it 00:11:37.220 --> 00:11:40.840 align:start position:0% having an init function you could do it like<00:11:37.340> this<00:11:37.640> or<00:11:38.180> and<00:11:38.780> the<00:11:39.380> future<00:11:39.710> you<00:11:40.670> could 00:11:40.840 --> 00:11:40.850 align:start position:0% like this or and the future you could 00:11:40.850 --> 00:11:43.480 align:start position:0% like this or and the future you could also<00:11:41.000> hope<00:11:41.990> that<00:11:42.020> you<00:11:42.740> would<00:11:42.890> at<00:11:43.010> some<00:11:43.040> point 00:11:43.480 --> 00:11:43.490 align:start position:0% also hope that you would at some point 00:11:43.490 --> 00:11:45.760 align:start position:0% also hope that you would at some point have<00:11:44.030> the<00:11:44.180> possibility<00:11:44.540> to<00:11:44.780> have<00:11:45.170> this<00:11:45.470> which 00:11:45.760 --> 00:11:45.770 align:start position:0% have the possibility to have this which 00:11:45.770 --> 00:11:48.490 align:start position:0% have the possibility to have this which is<00:11:45.890> exactly<00:11:45.980> what<00:11:46.460> Krishnan<00:11:47.300> said<00:11:47.510> today<00:11:47.780> when 00:11:48.490 --> 00:11:48.500 align:start position:0% is exactly what Krishnan said today when 00:11:48.500 --> 00:11:50.080 align:start position:0% is exactly what Krishnan said today when solidity<00:11:48.890> comes<00:11:49.190> to<00:11:49.340> the<00:11:49.430> point<00:11:49.670> that<00:11:49.880> it 00:11:50.080 --> 00:11:50.090 align:start position:0% solidity comes to the point that it 00:11:50.090 --> 00:11:51.510 align:start position:0% solidity comes to the point that it actually<00:11:50.360> allows<00:11:50.630> you<00:11:50.870> to<00:11:50.960> have<00:11:51.050> first-class 00:11:51.510 --> 00:11:51.520 align:start position:0% actually allows you to have first-class 00:11:51.520 --> 00:11:55.330 align:start position:0% actually allows you to have first-class citizen<00:11:52.520> functions<00:11:53.440> this<00:11:54.440> syntax<00:11:54.950> does<00:11:55.190> not 00:11:55.330 --> 00:11:55.340 align:start position:0% citizen functions this syntax does not 00:11:55.340 --> 00:11:56.980 align:start position:0% citizen functions this syntax does not exist<00:11:55.700> yet<00:11:55.940> but<00:11:56.150> this<00:11:56.300> would<00:11:56.480> allow<00:11:56.690> you<00:11:56.750> to 00:11:56.980 --> 00:11:56.990 align:start position:0% exist yet but this would allow you to 00:11:56.990 --> 00:11:58.870 align:start position:0% exist yet but this would allow you to set<00:11:57.200> the<00:11:57.290> price<00:11:57.500> immediately<00:11:58.010> by<00:11:58.430> a<00:11:58.460> callback 00:11:58.870 --> 00:11:58.880 align:start position:0% set the price immediately by a callback 00:11:58.880 --> 00:12:01.360 align:start position:0% set the price immediately by a callback that<00:11:58.940> would<00:11:59.240> say<00:11:59.650> check<00:12:00.650> out<00:12:00.830> what<00:12:01.070> the<00:12:01.160> price 00:12:01.360 --> 00:12:01.370 align:start position:0% that would say check out what the price 00:12:01.370 --> 00:12:03.010 align:start position:0% that would say check out what the price of<00:12:01.520> the<00:12:01.610> dollar<00:12:01.730> is<00:12:02.000> at<00:12:02.210> a<00:12:02.240> certain<00:12:02.450> day<00:12:02.660> to<00:12:02.720> set 00:12:03.010 --> 00:12:03.020 align:start position:0% of the dollar is at a certain day to set 00:12:03.020 --> 00:12:05.560 align:start position:0% of the dollar is at a certain day to set a<00:12:03.050> price<00:12:03.350> that<00:12:03.650> is<00:12:04.010> not<00:12:04.220> a<00:12:04.250> static<00:12:04.640> number<00:12:05.090> but 00:12:05.560 --> 00:12:05.570 align:start position:0% a price that is not a static number but 00:12:05.570 --> 00:12:08.080 align:start position:0% a price that is not a static number but that<00:12:05.690> is<00:12:05.780> looked<00:12:05.990> up<00:12:06.140> in<00:12:06.260> that<00:12:06.350> moment<00:12:06.530> so<00:12:07.430> yeah 00:12:08.080 --> 00:12:08.090 align:start position:0% that is looked up in that moment so yeah 00:12:08.090 --> 00:12:10.240 align:start position:0% that is looked up in that moment so yeah this<00:12:08.480> is<00:12:08.630> yourself<00:12:08.900> the<00:12:09.590> distributed<00:12:10.070> letter 00:12:10.240 --> 00:12:10.250 align:start position:0% this is yourself the distributed letter 00:12:10.250 --> 00:12:14.410 align:start position:0% this is yourself the distributed letter I<00:12:10.750> really<00:12:11.750> hate<00:12:12.320> it<00:12:12.530> but<00:12:13.100> maybe<00:12:13.940> there's<00:12:14.360> more 00:12:14.410 --> 00:12:14.420 align:start position:0% I really hate it but maybe there's more 00:12:14.420 --> 00:12:16.150 align:start position:0% I really hate it but maybe there's more to<00:12:14.600> it<00:12:14.720> than<00:12:14.870> I<00:12:14.990> used<00:12:15.140> to<00:12:15.260> think<00:12:15.470> and<00:12:15.710> this<00:12:16.010> is 00:12:16.150 --> 00:12:16.160 align:start position:0% to it than I used to think and this is 00:12:16.160 --> 00:12:18.100 align:start position:0% to it than I used to think and this is just<00:12:16.340> the<00:12:16.640> current<00:12:17.210> thoughts<00:12:17.420> I<00:12:17.600> had<00:12:17.630> on<00:12:17.930> it 00:12:18.100 --> 00:12:18.110 align:start position:0% just the current thoughts I had on it 00:12:18.110 --> 00:12:21.130 align:start position:0% just the current thoughts I had on it this<00:12:18.770> is<00:12:18.950> my<00:12:19.370> twitter<00:12:19.610> handle<00:12:19.700> i'll<00:12:20.540> post<00:12:20.960> the 00:12:21.130 --> 00:12:21.140 align:start position:0% this is my twitter handle i'll post the 00:12:21.140 --> 00:12:24.250 align:start position:0% this is my twitter handle i'll post the links<00:12:21.410> there<00:12:21.440> thank<00:12:21.890> you<00:12:21.980> very<00:12:22.130> much