WEBVTT Kind: captions Language: en 00:00:01.070 --> 00:00:09.959 align:start position:0% [Applause] 00:00:09.959 --> 00:00:09.969 align:start position:0% 00:00:09.969 --> 00:00:14.339 align:start position:0% a<00:00:11.280> bankrupt<00:00:12.280> 4G<00:00:13.030> I<00:00:13.240> think<00:00:13.570> very<00:00:13.690> much<00:00:13.900> for<00:00:14.199> the 00:00:14.339 --> 00:00:14.349 align:start position:0% a bankrupt 4G I think very much for the 00:00:14.349 --> 00:00:17.730 align:start position:0% a bankrupt 4G I think very much for the introduction<00:00:15.420> who<00:00:16.420> of<00:00:16.570> you<00:00:16.779> knows<00:00:17.080> what 00:00:17.730 --> 00:00:17.740 align:start position:0% introduction who of you knows what 00:00:17.740 --> 00:00:20.339 align:start position:0% introduction who of you knows what Socrates<00:00:18.369> is<00:00:18.700> roughly<00:00:19.240> so<00:00:19.599> just<00:00:19.840> that<00:00:19.990> we<00:00:20.110> kind 00:00:20.339 --> 00:00:20.349 align:start position:0% Socrates is roughly so just that we kind 00:00:20.349 --> 00:00:23.970 align:start position:0% Socrates is roughly so just that we kind of<00:00:20.470> just<00:00:21.300> okay<00:00:22.300> and<00:00:22.779> then<00:00:23.289> we<00:00:23.439> can<00:00:23.619> do<00:00:23.770> a<00:00:23.800> quick 00:00:23.970 --> 00:00:23.980 align:start position:0% of just okay and then we can do a quick 00:00:23.980 --> 00:00:25.650 align:start position:0% of just okay and then we can do a quick intro<00:00:24.460> I<00:00:24.489> guess<00:00:24.789> and<00:00:25.029> spend<00:00:25.239> a<00:00:25.300> bit<00:00:25.449> more<00:00:25.480> time 00:00:25.650 --> 00:00:25.660 align:start position:0% intro I guess and spend a bit more time 00:00:25.660 --> 00:00:27.990 align:start position:0% intro I guess and spend a bit more time on<00:00:26.110> on<00:00:26.349> the<00:00:26.469> later<00:00:26.649> slides<00:00:27.340> of<00:00:27.579> the 00:00:27.990 --> 00:00:28.000 align:start position:0% on on the later slides of the 00:00:28.000 --> 00:00:32.040 align:start position:0% on on the later slides of the presentation 00:00:32.040 --> 00:00:32.050 align:start position:0% 00:00:32.050 --> 00:00:37.500 align:start position:0% in<00:00:32.380> order 00:00:37.500 --> 00:00:37.510 align:start position:0% 00:00:37.510 --> 00:00:40.620 align:start position:0% so<00:00:38.110> something<00:00:38.680> started<00:00:39.280> as<00:00:39.730> my<00:00:40.210> research 00:00:40.620 --> 00:00:40.630 align:start position:0% so something started as my research 00:00:40.630 --> 00:00:43.140 align:start position:0% so something started as my research project<00:00:41.380> basically<00:00:41.680> at<00:00:42.010> to<00:00:42.190> you<00:00:42.280> Berlin<00:00:42.640> but 00:00:43.140 --> 00:00:43.150 align:start position:0% project basically at to you Berlin but 00:00:43.150 --> 00:00:46.049 align:start position:0% project basically at to you Berlin but by<00:00:43.450> now<00:00:43.630> we're<00:00:44.170> happy<00:00:44.590> to<00:00:44.829> develop<00:00:45.309> it<00:00:45.430> as<00:00:45.670> part 00:00:46.049 --> 00:00:46.059 align:start position:0% by now we're happy to develop it as part 00:00:46.059 --> 00:00:48.930 align:start position:0% by now we're happy to develop it as part of<00:00:46.210> the<00:00:46.420> serum<00:00:46.900> foundation<00:00:47.020> team<00:00:47.500> as<00:00:47.940> three 00:00:48.930 --> 00:00:48.940 align:start position:0% of the serum foundation team as three 00:00:48.940 --> 00:00:50.970 align:start position:0% of the serum foundation team as three people<00:00:49.360> at<00:00:49.480> the<00:00:49.600> moment<00:00:49.960> we're<00:00:50.410> looking<00:00:50.800> into 00:00:50.970 --> 00:00:50.980 align:start position:0% people at the moment we're looking into 00:00:50.980 --> 00:00:54.030 align:start position:0% people at the moment we're looking into growth<00:00:51.370> so<00:00:51.699> in<00:00:51.850> the<00:00:52.000> end<00:00:52.090> you're<00:00:52.690> free<00:00:52.930> to<00:00:53.260> to 00:00:54.030 --> 00:00:54.040 align:start position:0% growth so in the end you're free to to 00:00:54.040 --> 00:00:56.030 align:start position:0% growth so in the end you're free to to get<00:00:54.220> in<00:00:54.370> touch 00:00:56.030 --> 00:00:56.040 align:start position:0% get in touch 00:00:56.040 --> 00:00:58.650 align:start position:0% get in touch let's<00:00:57.040> start<00:00:57.309> with<00:00:57.580> introduction<00:00:58.269> vision 00:00:58.650 --> 00:00:58.660 align:start position:0% let's start with introduction vision 00:00:58.660 --> 00:01:03.150 align:start position:0% let's start with introduction vision before<00:00:59.170> we<00:00:59.320> dive<00:00:59.559> into<00:00:59.860> more<00:01:00.610> so<00:01:01.510> the<00:01:02.140> plan<00:01:02.920> of 00:01:03.150 --> 00:01:03.160 align:start position:0% before we dive into more so the plan of 00:01:03.160 --> 00:01:05.580 align:start position:0% before we dive into more so the plan of today's<00:01:03.550> talk<00:01:03.940> is<00:01:04.540> basically<00:01:05.019> three<00:01:05.530> things 00:01:05.580 --> 00:01:05.590 align:start position:0% today's talk is basically three things 00:01:05.590 --> 00:01:07.560 align:start position:0% today's talk is basically three things first<00:01:06.430> we<00:01:06.700> provide<00:01:07.090> a<00:01:07.119> bit<00:01:07.360> of<00:01:07.479> an 00:01:07.560 --> 00:01:07.570 align:start position:0% first we provide a bit of an 00:01:07.570 --> 00:01:09.630 align:start position:0% first we provide a bit of an introduction<00:01:07.960> back<00:01:08.350> from<00:01:08.590> those<00:01:09.159> that<00:01:09.580> are 00:01:09.630 --> 00:01:09.640 align:start position:0% introduction back from those that are 00:01:09.640 --> 00:01:11.850 align:start position:0% introduction back from those that are not<00:01:09.940> that<00:01:10.390> familiar<00:01:10.600> with<00:01:10.930> the<00:01:11.110> tool<00:01:11.410> but<00:01:11.710> we 00:01:11.850 --> 00:01:11.860 align:start position:0% not that familiar with the tool but we 00:01:11.860 --> 00:01:13.920 align:start position:0% not that familiar with the tool but we keep<00:01:12.009> it<00:01:12.190> short<00:01:12.430> and<00:01:12.640> we'll<00:01:13.240> give<00:01:13.450> you<00:01:13.600> a<00:01:13.630> bit 00:01:13.920 --> 00:01:13.930 align:start position:0% keep it short and we'll give you a bit 00:01:13.930 --> 00:01:16.050 align:start position:0% keep it short and we'll give you a bit of<00:01:13.960> an<00:01:14.320> update<00:01:14.500> on<00:01:15.009> what's<00:01:15.340> been<00:01:15.430> happening<00:01:15.940> in 00:01:16.050 --> 00:01:16.060 align:start position:0% of an update on what's been happening in 00:01:16.060 --> 00:01:17.969 align:start position:0% of an update on what's been happening in the<00:01:16.090> last<00:01:16.180> year<00:01:16.570> so<00:01:16.840> basically<00:01:17.200> a<00:01:17.320> dev<00:01:17.590> update 00:01:17.969 --> 00:01:17.979 align:start position:0% the last year so basically a dev update 00:01:17.979 --> 00:01:20.400 align:start position:0% the last year so basically a dev update those<00:01:18.550> new<00:01:18.729> features<00:01:19.149> we<00:01:19.360> have<00:01:19.390> where<00:01:20.110> we<00:01:20.259> were 00:01:20.400 --> 00:01:20.410 align:start position:0% those new features we have where we were 00:01:20.410 --> 00:01:22.920 align:start position:0% those new features we have where we were going<00:01:20.710> and<00:01:21.009> then<00:01:21.670> we<00:01:22.060> look<00:01:22.300> at<00:01:22.420> some<00:01:22.690> use<00:01:22.899> cases 00:01:22.920 --> 00:01:22.930 align:start position:0% going and then we look at some use cases 00:01:22.930 --> 00:01:25.230 align:start position:0% going and then we look at some use cases so<00:01:23.590> we<00:01:23.619> report<00:01:24.369> back<00:01:24.430> from<00:01:24.759> actual 00:01:25.230 --> 00:01:25.240 align:start position:0% so we report back from actual 00:01:25.240 --> 00:01:26.219 align:start position:0% so we report back from actual applications 00:01:26.219 --> 00:01:26.229 align:start position:0% applications 00:01:26.229 --> 00:01:29.340 align:start position:0% applications that's<00:01:26.470> that<00:01:27.190> include<00:01:27.910> improved<00:01:28.660> on<00:01:29.020> their 00:01:29.340 --> 00:01:29.350 align:start position:0% that's that include improved on their 00:01:29.350 --> 00:01:31.469 align:start position:0% that's that include improved on their privacy<00:01:29.800> properties<00:01:30.610> by<00:01:31.149> leveraging 00:01:31.469 --> 00:01:31.479 align:start position:0% privacy properties by leveraging 00:01:31.479 --> 00:01:34.770 align:start position:0% privacy properties by leveraging Socrates<00:01:32.470> bases<00:01:32.979> in<00:01:33.100> case<00:01:33.250> marks<00:01:33.610> and<00:01:33.820> as<00:01:34.750> a 00:01:34.770 --> 00:01:34.780 align:start position:0% Socrates bases in case marks and as a 00:01:34.780 --> 00:01:36.330 align:start position:0% Socrates bases in case marks and as a last<00:01:35.050> step<00:01:35.200> we'll<00:01:35.560> give<00:01:35.740> you<00:01:35.890> a<00:01:35.920> bit<00:01:36.100> of<00:01:36.130> an 00:01:36.330 --> 00:01:36.340 align:start position:0% last step we'll give you a bit of an 00:01:36.340 --> 00:01:38.130 align:start position:0% last step we'll give you a bit of an outlook<00:01:36.700> what<00:01:36.910> we<00:01:37.090> think<00:01:37.360> where<00:01:37.600> we<00:01:37.750> should<00:01:37.960> be 00:01:38.130 --> 00:01:38.140 align:start position:0% outlook what we think where we should be 00:01:38.140 --> 00:01:42.389 align:start position:0% outlook what we think where we should be going<00:01:38.350> in<00:01:38.710> the<00:01:39.190> next<00:01:39.490> year<00:01:39.729> so<00:01:40.800> Socrates<00:01:41.800> is 00:01:42.389 --> 00:01:42.399 align:start position:0% going in the next year so Socrates is 00:01:42.399 --> 00:01:44.520 align:start position:0% going in the next year so Socrates is basically<00:01:43.030> two<00:01:43.330> things<00:01:43.599> it's<00:01:44.020> a<00:01:44.140> high<00:01:44.289> level 00:01:44.520 --> 00:01:44.530 align:start position:0% basically two things it's a high level 00:01:44.530 --> 00:01:47.999 align:start position:0% basically two things it's a high level of<00:01:44.740> language<00:01:45.099> for<00:01:45.789> programming<00:01:46.179> CK<00:01:47.080> starts<00:01:47.530> in 00:01:47.999 --> 00:01:48.009 align:start position:0% of language for programming CK starts in 00:01:48.009 --> 00:01:50.730 align:start position:0% of language for programming CK starts in and<00:01:48.520> it's<00:01:48.700> a<00:01:48.849> bunch<00:01:49.060> of<00:01:49.270> fooling<00:01:49.840> around<00:01:50.530> all 00:01:50.730 --> 00:01:50.740 align:start position:0% and it's a bunch of fooling around all 00:01:50.740 --> 00:01:53.729 align:start position:0% and it's a bunch of fooling around all of<00:01:50.770> that<00:01:50.920> so<00:01:51.759> with<00:01:52.119> Socrates<00:01:52.569> in<00:01:53.020> the<00:01:53.289> language 00:01:53.729 --> 00:01:53.739 align:start position:0% of that so with Socrates in the language 00:01:53.739 --> 00:01:56.969 align:start position:0% of that so with Socrates in the language you<00:01:54.130> can<00:01:54.399> program<00:01:54.910> in<00:01:55.270> an<00:01:55.660> imprinted<00:01:56.380> style<00:01:56.679> as 00:01:56.969 --> 00:01:56.979 align:start position:0% you can program in an imprinted style as 00:01:56.979 --> 00:02:00.449 align:start position:0% you can program in an imprinted style as most<00:01:57.250> programmers<00:01:57.789> are<00:01:58.209> used<00:01:58.420> to<00:01:59.459> some 00:02:00.449 --> 00:02:00.459 align:start position:0% most programmers are used to some 00:02:00.459 --> 00:02:03.059 align:start position:0% most programmers are used to some program<00:02:00.880> and<00:02:01.179> then<00:02:01.660> it<00:02:01.959> provides<00:02:02.200> you<00:02:02.619> tooling 00:02:03.059 --> 00:02:03.069 align:start position:0% program and then it provides you tooling 00:02:03.069 --> 00:02:05.669 align:start position:0% program and then it provides you tooling so<00:02:03.369> you<00:02:03.459> can<00:02:03.670> compile<00:02:04.390> that<00:02:04.660> program<00:02:05.170> into<00:02:05.590> an 00:02:05.669 --> 00:02:05.679 align:start position:0% so you can compile that program into an 00:02:05.679 --> 00:02:08.999 align:start position:0% so you can compile that program into an abstraction<00:02:06.099> that<00:02:06.520> is<00:02:07.360> provable<00:02:08.110> through<00:02:08.590> CK 00:02:08.999 --> 00:02:09.009 align:start position:0% abstraction that is provable through CK 00:02:09.009 --> 00:02:10.889 align:start position:0% abstraction that is provable through CK snarks<00:02:09.369> and<00:02:09.399> then<00:02:10.000> you<00:02:10.149> can<00:02:10.330> use<00:02:10.479> this<00:02:10.690> art 00:02:10.889 --> 00:02:10.899 align:start position:0% snarks and then you can use this art 00:02:10.899 --> 00:02:14.240 align:start position:0% snarks and then you can use this art which<00:02:11.020> is<00:02:11.110> cooling<00:02:11.590> to<00:02:12.270> have<00:02:13.270> you<00:02:13.390> program 00:02:14.240 --> 00:02:14.250 align:start position:0% which is cooling to have you program 00:02:14.250 --> 00:02:16.410 align:start position:0% which is cooling to have you program execute<00:02:15.250> the<00:02:15.370> program 00:02:16.410 --> 00:02:16.420 align:start position:0% execute the program 00:02:16.420 --> 00:02:18.330 align:start position:0% execute the program generate<00:02:17.050> to<00:02:17.200> seek<00:02:17.380> a<00:02:17.560> stock<00:02:17.830> truth<00:02:18.100> that 00:02:18.330 --> 00:02:18.340 align:start position:0% generate to seek a stock truth that 00:02:18.340 --> 00:02:20.490 align:start position:0% generate to seek a stock truth that shows<00:02:18.580> you<00:02:18.790> that<00:02:18.819> this<00:02:19.240> execution<00:02:19.810> happened 00:02:20.490 --> 00:02:20.500 align:start position:0% shows you that this execution happened 00:02:20.500 --> 00:02:23.610 align:start position:0% shows you that this execution happened correctly<00:02:21.130> and<00:02:21.569> it<00:02:22.569> also<00:02:22.720> generates<00:02:23.350> use 00:02:23.610 --> 00:02:23.620 align:start position:0% correctly and it also generates use 00:02:23.620 --> 00:02:26.250 align:start position:0% correctly and it also generates use among<00:02:23.950> objects<00:02:24.490> solidity<00:02:25.270> contracts<00:02:25.900> that 00:02:26.250 --> 00:02:26.260 align:start position:0% among objects solidity contracts that 00:02:26.260 --> 00:02:28.440 align:start position:0% among objects solidity contracts that you<00:02:26.319> can<00:02:26.650> deploy<00:02:26.920> to<00:02:27.220> watching<00:02:27.550> so<00:02:28.150> you<00:02:28.240> can 00:02:28.440 --> 00:02:28.450 align:start position:0% you can deploy to watching so you can 00:02:28.450 --> 00:02:31.050 align:start position:0% you can deploy to watching so you can easily<00:02:28.870> verify<00:02:29.400> statistics<00:02:30.400> Augie<00:02:30.670> theorem 00:02:31.050 --> 00:02:31.060 align:start position:0% easily verify statistics Augie theorem 00:02:31.060 --> 00:02:34.190 align:start position:0% easily verify statistics Augie theorem without<00:02:31.660> having<00:02:32.290> to<00:02:32.500> bother<00:02:32.680> with<00:02:33.400> writing 00:02:34.190 --> 00:02:34.200 align:start position:0% without having to bother with writing 00:02:34.200 --> 00:02:36.960 align:start position:0% without having to bother with writing solidity<00:02:35.200> verify<00:02:35.800> as<00:02:35.860> for<00:02:36.310> the<00:02:36.370> specific 00:02:36.960 --> 00:02:36.970 align:start position:0% solidity verify as for the specific 00:02:36.970 --> 00:02:42.199 align:start position:0% solidity verify as for the specific secrets<00:02:37.480> are<00:02:37.660> effective 00:02:42.199 --> 00:02:42.209 align:start position:0% 00:02:42.209 --> 00:02:45.119 align:start position:0% so<00:02:43.209> what<00:02:43.810> are<00:02:43.930> the<00:02:44.019> main<00:02:44.230> goals<00:02:44.260> backs<00:02:44.890> our 00:02:45.119 --> 00:02:45.129 align:start position:0% so what are the main goals backs our 00:02:45.129 --> 00:02:46.770 align:start position:0% so what are the main goals backs our face<00:02:45.340> it's<00:02:45.549> basically<00:02:45.909> two<00:02:46.209> things<00:02:46.450> that<00:02:46.659> the 00:02:46.770 --> 00:02:46.780 align:start position:0% face it's basically two things that the 00:02:46.780 --> 00:02:49.649 align:start position:0% face it's basically two things that the first<00:02:46.989> is<00:02:47.310> enhancing<00:02:48.310> privacy<00:02:48.849> with<00:02:49.510> the 00:02:49.649 --> 00:02:49.659 align:start position:0% first is enhancing privacy with the 00:02:49.659 --> 00:02:52.199 align:start position:0% first is enhancing privacy with the serum<00:02:50.049> we<00:02:50.379> have<00:02:50.590> this<00:02:50.829> platform<00:02:51.400> that's<00:02:51.939> very 00:02:52.199 --> 00:02:52.209 align:start position:0% serum we have this platform that's very 00:02:52.209 --> 00:02:53.699 align:start position:0% serum we have this platform that's very general<00:02:52.659> we<00:02:52.840> can<00:02:53.049> do<00:02:53.170> general-purpose 00:02:53.699 --> 00:02:53.709 align:start position:0% general we can do general-purpose 00:02:53.709 --> 00:02:56.729 align:start position:0% general we can do general-purpose computations<00:02:54.640> it's<00:02:55.000> quite<00:02:55.239> powerful<00:02:55.450> but<00:02:56.409> for 00:02:56.729 --> 00:02:56.739 align:start position:0% computations it's quite powerful but for 00:02:56.739 --> 00:02:59.309 align:start position:0% computations it's quite powerful but for real<00:02:56.859> applications<00:02:57.700> to<00:02:57.939> take<00:02:58.150> off<00:02:58.390> we<00:02:58.900> require 00:02:59.309 --> 00:02:59.319 align:start position:0% real applications to take off we require 00:02:59.319 --> 00:03:01.679 align:start position:0% real applications to take off we require a<00:02:59.680> bit<00:02:59.829> more<00:03:00.069> privacy<00:03:00.430> I<00:03:00.579> think<00:03:00.670> because<00:03:01.239> there 00:03:01.679 --> 00:03:01.689 align:start position:0% a bit more privacy I think because there 00:03:01.689 --> 00:03:04.559 align:start position:0% a bit more privacy I think because there is<00:03:01.840> awareness<00:03:01.989> that<00:03:02.769> all<00:03:03.579> the<00:03:03.819> data<00:03:04.060> put<00:03:04.420> on 00:03:04.559 --> 00:03:04.569 align:start position:0% is awareness that all the data put on 00:03:04.569 --> 00:03:06.390 align:start position:0% is awareness that all the data put on the<00:03:04.629> blockchain<00:03:04.870> can<00:03:05.319> remind<00:03:05.650> the<00:03:05.859> news<00:03:06.099> band 00:03:06.390 --> 00:03:06.400 align:start position:0% the blockchain can remind the news band 00:03:06.400 --> 00:03:08.610 align:start position:0% the blockchain can remind the news band in<00:03:06.549> one<00:03:06.700> and<00:03:07.299> that's<00:03:07.510> a<00:03:07.629> showstopper<00:03:07.840> for<00:03:08.290> some 00:03:08.610 --> 00:03:08.620 align:start position:0% in one and that's a showstopper for some 00:03:08.620 --> 00:03:10.140 align:start position:0% in one and that's a showstopper for some applications<00:03:09.250> and<00:03:09.400> we've<00:03:09.609> seen<00:03:09.790> that<00:03:09.909> later 00:03:10.140 --> 00:03:10.150 align:start position:0% applications and we've seen that later 00:03:10.150 --> 00:03:12.869 align:start position:0% applications and we've seen that later when<00:03:10.480> we<00:03:10.599> look<00:03:10.719> at<00:03:10.900> the<00:03:11.079> use<00:03:11.260> cases<00:03:11.879> for 00:03:12.869 --> 00:03:12.879 align:start position:0% when we look at the use cases for 00:03:12.879 --> 00:03:14.759 align:start position:0% when we look at the use cases for Bitcoin<00:03:13.359> we've<00:03:13.750> seen<00:03:14.049> kind<00:03:14.379> of<00:03:14.590> an 00:03:14.759 --> 00:03:14.769 align:start position:0% Bitcoin we've seen kind of an 00:03:14.769 --> 00:03:16.860 align:start position:0% Bitcoin we've seen kind of an improvement<00:03:15.280> through<00:03:15.790> the<00:03:15.939> see<00:03:16.120> cash<00:03:16.389> that 00:03:16.860 --> 00:03:16.870 align:start position:0% improvement through the see cash that 00:03:16.870 --> 00:03:19.379 align:start position:0% improvement through the see cash that managed<00:03:17.319> to<00:03:17.439> do<00:03:17.650> fully<00:03:18.129> anonymous<00:03:18.609> payment 00:03:19.379 --> 00:03:19.389 align:start position:0% managed to do fully anonymous payment 00:03:19.389 --> 00:03:21.990 align:start position:0% managed to do fully anonymous payment schemes<00:03:19.689> on<00:03:20.019> top<00:03:20.260> of<00:03:20.439> CK<00:03:20.769> starts<00:03:21.099> and<00:03:21.310> of 00:03:21.990 --> 00:03:22.000 align:start position:0% schemes on top of CK starts and of 00:03:22.000 --> 00:03:24.149 align:start position:0% schemes on top of CK starts and of course<00:03:22.299> you<00:03:22.480> can't<00:03:22.750> simply<00:03:23.200> do<00:03:23.379> a<00:03:23.409> scheme<00:03:23.829> for 00:03:24.149 --> 00:03:24.159 align:start position:0% course you can't simply do a scheme for 00:03:24.159 --> 00:03:26.399 align:start position:0% course you can't simply do a scheme for a<00:03:24.459> theorem<00:03:25.000> because<00:03:25.569> the<00:03:25.750> theorems<00:03:26.169> too 00:03:26.399 --> 00:03:26.409 align:start position:0% a theorem because the theorems too 00:03:26.409 --> 00:03:28.500 align:start position:0% a theorem because the theorems too generic<00:03:26.560> for<00:03:27.040> that<00:03:27.189> so<00:03:27.519> our<00:03:27.669> approach<00:03:28.060> is<00:03:28.299> to 00:03:28.500 --> 00:03:28.510 align:start position:0% generic for that so our approach is to 00:03:28.510 --> 00:03:30.330 align:start position:0% generic for that so our approach is to provide<00:03:28.540> easy<00:03:29.169> to<00:03:29.409> use<00:03:29.590> and<00:03:29.859> convenient 00:03:30.330 --> 00:03:30.340 align:start position:0% provide easy to use and convenient 00:03:30.340 --> 00:03:33.059 align:start position:0% provide easy to use and convenient tooling<00:03:30.760> that<00:03:30.939> you<00:03:31.480> can<00:03:31.840> for<00:03:32.260> your<00:03:32.409> specific 00:03:33.059 --> 00:03:33.069 align:start position:0% tooling that you can for your specific 00:03:33.069 --> 00:03:34.979 align:start position:0% tooling that you can for your specific application<00:03:33.250> in<00:03:33.970> these<00:03:34.150> theorem<00:03:34.419> contexts 00:03:34.979 --> 00:03:34.989 align:start position:0% application in these theorem contexts 00:03:34.989 --> 00:03:37.050 align:start position:0% application in these theorem contexts whatever<00:03:35.409> interesting<00:03:35.889> case<00:03:36.099> arts<00:03:36.430> community 00:03:37.050 --> 00:03:37.060 align:start position:0% whatever interesting case arts community 00:03:37.060 --> 00:03:40.069 align:start position:0% whatever interesting case arts community to<00:03:37.569> improve<00:03:37.780> your<00:03:38.019> privacy<00:03:38.530> properties<00:03:39.040> and 00:03:40.069 --> 00:03:40.079 align:start position:0% to improve your privacy properties and 00:03:40.079 --> 00:03:44.909 align:start position:0% to improve your privacy properties and the<00:03:41.079> second<00:03:41.470> thing<00:03:41.650> is<00:03:41.859> scalability<00:03:43.139> so<00:03:44.139> we're 00:03:44.909 --> 00:03:44.919 align:start position:0% the second thing is scalability so we're 00:03:44.919 --> 00:03:47.129 align:start position:0% the second thing is scalability so we're in<00:03:45.069> the<00:03:45.220> word<00:03:45.430> on<00:03:45.790> the<00:03:45.940> Left<00:03:46.150> right<00:03:46.720> now<00:03:46.900> where 00:03:47.129 --> 00:03:47.139 align:start position:0% in the word on the Left right now where 00:03:47.139 --> 00:03:49.140 align:start position:0% in the word on the Left right now where we<00:03:47.349> redundantly<00:03:47.979> process<00:03:48.519> all<00:03:49.000> the 00:03:49.140 --> 00:03:49.150 align:start position:0% we redundantly process all the 00:03:49.150 --> 00:03:50.759 align:start position:0% we redundantly process all the transactions<00:03:49.780> that<00:03:49.900> are<00:03:50.049> submitted<00:03:50.590> to<00:03:50.620> the 00:03:50.759 --> 00:03:50.769 align:start position:0% transactions that are submitted to the 00:03:50.769 --> 00:03:53.490 align:start position:0% transactions that are submitted to the blockchain<00:03:51.040> on<00:03:51.430> every<00:03:51.699> node<00:03:51.909> and<00:03:52.349> we<00:03:53.349> would 00:03:53.490 --> 00:03:53.500 align:start position:0% blockchain on every node and we would 00:03:53.500 --> 00:03:55.559 align:start position:0% blockchain on every node and we would like<00:03:53.709> in<00:03:53.919> the<00:03:54.040> future<00:03:54.159> and<00:03:54.669> we<00:03:54.879> already<00:03:55.090> do<00:03:55.449> it 00:03:55.559 --> 00:03:55.569 align:start position:0% like in the future and we already do it 00:03:55.569 --> 00:03:57.390 align:start position:0% like in the future and we already do it in<00:03:55.690> some<00:03:55.870> cases<00:03:56.139> booth<00:03:56.769> to<00:03:56.949> the<00:03:56.979> world<00:03:57.250> and 00:03:57.390 --> 00:03:57.400 align:start position:0% in some cases booth to the world and 00:03:57.400 --> 00:04:01.050 align:start position:0% in some cases booth to the world and right<00:03:57.609> where<00:03:58.209> we<00:03:58.419> do<00:03:58.840> not<00:03:58.989> execute<00:04:00.060> complex 00:04:01.050 --> 00:04:01.060 align:start position:0% right where we do not execute complex 00:04:01.060 --> 00:04:03.119 align:start position:0% right where we do not execute complex things<00:04:01.479> on<00:04:01.720> the<00:04:01.840> blockchain<00:04:02.139> but<00:04:02.889> rather 00:04:03.119 --> 00:04:03.129 align:start position:0% things on the blockchain but rather 00:04:03.129 --> 00:04:05.550 align:start position:0% things on the blockchain but rather execute<00:04:03.909> complex<00:04:04.449> things<00:04:04.840> off<00:04:05.169> the<00:04:05.379> block 00:04:05.550 --> 00:04:05.560 align:start position:0% execute complex things off the block 00:04:05.560 --> 00:04:08.280 align:start position:0% execute complex things off the block chains<00:04:05.889> while<00:04:06.849> maintaining<00:04:07.090> privacy<00:04:07.419> because 00:04:08.280 --> 00:04:08.290 align:start position:0% chains while maintaining privacy because 00:04:08.290 --> 00:04:09.869 align:start position:0% chains while maintaining privacy because we<00:04:08.440> do<00:04:08.560> not<00:04:08.709> need<00:04:09.010> to<00:04:09.129> expose<00:04:09.549> all<00:04:09.849> the 00:04:09.869 --> 00:04:09.879 align:start position:0% we do not need to expose all the 00:04:09.879 --> 00:04:11.520 align:start position:0% we do not need to expose all the information<00:04:10.510> we<00:04:10.629> use<00:04:10.780> in<00:04:10.959> this<00:04:11.109> massive 00:04:11.520 --> 00:04:11.530 align:start position:0% information we use in this massive 00:04:11.530 --> 00:04:14.280 align:start position:0% information we use in this massive processing<00:04:11.949> then<00:04:12.669> send<00:04:13.510> the<00:04:13.659> result<00:04:13.989> of<00:04:14.139> that 00:04:14.280 --> 00:04:14.290 align:start position:0% processing then send the result of that 00:04:14.290 --> 00:04:17.039 align:start position:0% processing then send the result of that computation<00:04:14.639> plus<00:04:15.639> prove<00:04:16.090> that<00:04:16.359> tests<00:04:16.930> of 00:04:17.039 --> 00:04:17.049 align:start position:0% computation plus prove that tests of 00:04:17.049 --> 00:04:19.289 align:start position:0% computation plus prove that tests of correctness<00:04:17.500> back<00:04:17.859> to<00:04:18.039> blockchain<00:04:18.549> and<00:04:18.729> only 00:04:19.289 --> 00:04:19.299 align:start position:0% correctness back to blockchain and only 00:04:19.299 --> 00:04:22.140 align:start position:0% correctness back to blockchain and only check<00:04:19.539> that<00:04:19.810> as<00:04:20.320> long<00:04:20.829> as<00:04:21.220> the<00:04:21.459> verification 00:04:22.140 --> 00:04:22.150 align:start position:0% check that as long as the verification 00:04:22.150 --> 00:04:25.200 align:start position:0% check that as long as the verification step<00:04:22.300> on<00:04:22.750> chain<00:04:23.020> is<00:04:23.260> cheaper<00:04:24.070> than<00:04:24.310> the<00:04:24.820> native 00:04:25.200 --> 00:04:25.210 align:start position:0% step on chain is cheaper than the native 00:04:25.210 --> 00:04:27.320 align:start position:0% step on chain is cheaper than the native execution<00:04:26.020> on<00:04:26.199> chain 00:04:27.320 --> 00:04:27.330 align:start position:0% execution on chain 00:04:27.330 --> 00:04:29.360 align:start position:0% execution on chain we'll<00:04:27.539> be<00:04:27.900> able<00:04:28.020> to<00:04:28.319> scale<00:04:28.590> better<00:04:28.830> because<00:04:29.340> of 00:04:29.360 --> 00:04:29.370 align:start position:0% we'll be able to scale better because of 00:04:29.370 --> 00:04:31.629 align:start position:0% we'll be able to scale better because of one<00:04:29.639> plot<00:04:29.939> we<00:04:30.240> can<00:04:30.659> fit<00:04:30.900> more<00:04:31.169> computational 00:04:31.629 --> 00:04:31.639 align:start position:0% one plot we can fit more computational 00:04:31.639 --> 00:04:34.159 align:start position:0% one plot we can fit more computational complexity<00:04:32.639> that<00:04:32.879> way<00:04:33.090> so<00:04:33.659> that's<00:04:33.840> the<00:04:34.020> two 00:04:34.159 --> 00:04:34.169 align:start position:0% complexity that way so that's the two 00:04:34.169 --> 00:04:36.200 align:start position:0% complexity that way so that's the two main<00:04:34.439> drivers<00:04:34.620> behind<00:04:34.919> why<00:04:35.849> this<00:04:35.909> is 00:04:36.200 --> 00:04:36.210 align:start position:0% main drivers behind why this is 00:04:36.210 --> 00:04:38.350 align:start position:0% main drivers behind why this is meaningful<00:04:36.389> and<00:04:36.750> why<00:04:37.050> you<00:04:37.110> should<00:04:37.409> heaven 00:04:38.350 --> 00:04:38.360 align:start position:0% meaningful and why you should heaven 00:04:38.360 --> 00:04:42.080 align:start position:0% meaningful and why you should heaven the<00:04:39.360> language<00:04:39.689> itself<00:04:40.080> that<00:04:41.039> we<00:04:41.189> use<00:04:41.430> this<00:04:41.759> or 00:04:42.080 --> 00:04:42.090 align:start position:0% the language itself that we use this or 00:04:42.090 --> 00:04:44.959 align:start position:0% the language itself that we use this or built<00:04:42.479> as<00:04:42.900> an<00:04:43.110> input<00:04:43.409> to<00:04:43.620> the<00:04:44.520> main<00:04:44.699> specific 00:04:44.959 --> 00:04:44.969 align:start position:0% built as an input to the main specific 00:04:44.969 --> 00:04:47.059 align:start position:0% built as an input to the main specific language<00:04:45.689> which<00:04:45.960> means<00:04:46.259> that<00:04:46.469> this<00:04:46.590> tailor 00:04:47.059 --> 00:04:47.069 align:start position:0% language which means that this tailor 00:04:47.069 --> 00:04:49.159 align:start position:0% language which means that this tailor mate<00:04:47.340> sufficiently<00:04:48.330> compiled<00:04:48.930> into 00:04:49.159 --> 00:04:49.169 align:start position:0% mate sufficiently compiled into 00:04:49.169 --> 00:04:52.010 align:start position:0% mate sufficiently compiled into abstraction<00:04:49.680> CK<00:04:50.280> starts<00:04:50.639> music<00:04:50.819> sure<00:04:51.629> you<00:04:51.810> can 00:04:52.010 --> 00:04:52.020 align:start position:0% abstraction CK starts music sure you can 00:04:52.020 --> 00:04:53.959 align:start position:0% abstraction CK starts music sure you can use<00:04:52.229> a<00:04:52.259> generic<00:04:52.710> programming<00:04:53.460> language<00:04:53.939> like 00:04:53.959 --> 00:04:53.969 align:start position:0% use a generic programming language like 00:04:53.969 --> 00:04:56.600 align:start position:0% use a generic programming language like C<00:04:54.479> or<00:04:54.750> us<00:04:55.050> there's<00:04:55.439> also<00:04:55.650> compilers<00:04:56.219> for<00:04:56.250> that 00:04:56.600 --> 00:04:56.610 align:start position:0% C or us there's also compilers for that 00:04:56.610 --> 00:04:58.730 align:start position:0% C or us there's also compilers for that those<00:04:57.150> many<00:04:57.479> of<00:04:57.689> the<00:04:57.780> data<00:04:57.990> types<00:04:58.319> and<00:04:58.620> the 00:04:58.730 --> 00:04:58.740 align:start position:0% those many of the data types and the 00:04:58.740 --> 00:05:01.580 align:start position:0% those many of the data types and the syntactic<00:04:59.360> constructs<00:05:00.360> they<00:05:00.629> offer<00:05:00.810> yeah 00:05:01.580 --> 00:05:01.590 align:start position:0% syntactic constructs they offer yeah 00:05:01.590 --> 00:05:03.680 align:start position:0% syntactic constructs they offer yeah not<00:05:02.159> efficiently<00:05:02.849> translatable<00:05:03.539> into 00:05:03.680 --> 00:05:03.690 align:start position:0% not efficiently translatable into 00:05:03.690 --> 00:05:05.330 align:start position:0% not efficiently translatable into distinct<00:05:04.379> a<00:05:04.500> snark<00:05:04.800> improvement 00:05:05.330 --> 00:05:05.340 align:start position:0% distinct a snark improvement 00:05:05.340 --> 00:05:07.459 align:start position:0% distinct a snark improvement abstractions<00:05:05.940> so<00:05:06.360> that's<00:05:06.569> why<00:05:06.780> we<00:05:06.990> kind<00:05:07.319> of 00:05:07.459 --> 00:05:07.469 align:start position:0% abstractions so that's why we kind of 00:05:07.469 --> 00:05:10.760 align:start position:0% abstractions so that's why we kind of have<00:05:07.919> this<00:05:08.099> DSL<00:05:08.669> to<00:05:09.419> be<00:05:09.569> sure<00:05:09.840> that<00:05:10.319> what<00:05:10.620> to 00:05:10.760 --> 00:05:10.770 align:start position:0% have this DSL to be sure that what to 00:05:10.770 --> 00:05:13.670 align:start position:0% have this DSL to be sure that what to write<00:05:10.949> is<00:05:11.280> kind<00:05:11.610> of<00:05:11.729> efficient<00:05:12.330> at<00:05:12.569> least<00:05:12.780> it's 00:05:13.670 --> 00:05:13.680 align:start position:0% write is kind of efficient at least it's 00:05:13.680 --> 00:05:16.100 align:start position:0% write is kind of efficient at least it's Iceland<00:05:14.250> inspired<00:05:14.729> syntax<00:05:15.240> but<00:05:15.599> we<00:05:15.810> borrow 00:05:16.100 --> 00:05:16.110 align:start position:0% Iceland inspired syntax but we borrow 00:05:16.110 --> 00:05:18.110 align:start position:0% Iceland inspired syntax but we borrow like<00:05:16.440> the<00:05:16.620> best<00:05:16.800> pieces<00:05:17.159> from<00:05:17.759> whatever 00:05:18.110 --> 00:05:18.120 align:start position:0% like the best pieces from whatever 00:05:18.120 --> 00:05:21.110 align:start position:0% like the best pieces from whatever language<00:05:18.690> kind<00:05:19.169> of<00:05:19.289> but<00:05:19.590> it's<00:05:19.830> mostly<00:05:20.159> similar 00:05:21.110 --> 00:05:21.120 align:start position:0% language kind of but it's mostly similar 00:05:21.120 --> 00:05:24.800 align:start position:0% language kind of but it's mostly similar to<00:05:21.389> Python<00:05:21.599> and<00:05:22.219> the<00:05:23.219> thing<00:05:24.000> that<00:05:24.180> makes<00:05:24.419> CK 00:05:24.800 --> 00:05:24.810 align:start position:0% to Python and the thing that makes CK 00:05:24.810 --> 00:05:26.869 align:start position:0% to Python and the thing that makes CK start<00:05:25.139> programming<00:05:25.620> hard<00:05:25.949> or<00:05:26.250> one<00:05:26.580> of<00:05:26.729> the 00:05:26.869 --> 00:05:26.879 align:start position:0% start programming hard or one of the 00:05:26.879 --> 00:05:28.700 align:start position:0% start programming hard or one of the things<00:05:27.180> that<00:05:27.479> makes<00:05:27.719> it<00:05:27.870> hard<00:05:28.169> one<00:05:28.500> of<00:05:28.590> the 00:05:28.700 --> 00:05:28.710 align:start position:0% things that makes it hard one of the 00:05:28.710 --> 00:05:31.070 align:start position:0% things that makes it hard one of the scary<00:05:29.039> parts<00:05:29.550> our<00:05:29.699> program<00:05:30.180> is<00:05:30.599> this<00:05:30.870> non 00:05:31.070 --> 00:05:31.080 align:start position:0% scary parts our program is this non 00:05:31.080 --> 00:05:33.320 align:start position:0% scary parts our program is this non determinism<00:05:31.740> which<00:05:32.310> means<00:05:32.580> a<00:05:32.759> call<00:05:33.029> to<00:05:33.210> an 00:05:33.320 --> 00:05:33.330 align:start position:0% determinism which means a call to an 00:05:33.330 --> 00:05:35.689 align:start position:0% determinism which means a call to an outside<00:05:33.690> component<00:05:34.349> you<00:05:34.830> get<00:05:35.069> some<00:05:35.400> results 00:05:35.689 --> 00:05:35.699 align:start position:0% outside component you get some results 00:05:35.699 --> 00:05:38.119 align:start position:0% outside component you get some results and<00:05:36.240> anything<00:05:36.870> that<00:05:36.900> was<00:05:37.349> part<00:05:37.590> of<00:05:37.650> your<00:05:37.710> song 00:05:38.119 --> 00:05:38.129 align:start position:0% and anything that was part of your song 00:05:38.129 --> 00:05:40.790 align:start position:0% and anything that was part of your song and<00:05:38.400> as<00:05:38.879> you<00:05:39.060> maybe<00:05:39.539> feel<00:05:39.840> this<00:05:40.110> is<00:05:40.289> quite 00:05:40.790 --> 00:05:40.800 align:start position:0% and as you maybe feel this is quite 00:05:40.800 --> 00:05:43.010 align:start position:0% and as you maybe feel this is quite context<00:05:41.340> is<00:05:41.520> something<00:05:41.849> people<00:05:42.419> do<00:05:42.839> not<00:05:42.960> want 00:05:43.010 --> 00:05:43.020 align:start position:0% context is something people do not want 00:05:43.020 --> 00:05:45.619 align:start position:0% context is something people do not want to<00:05:43.229> take<00:05:43.379> care<00:05:43.620> of<00:05:43.680> so<00:05:44.310> Socrates<00:05:44.639> hides<00:05:45.419> away 00:05:45.619 --> 00:05:45.629 align:start position:0% to take care of so Socrates hides away 00:05:45.629 --> 00:05:48.619 align:start position:0% to take care of so Socrates hides away all<00:05:46.139> this<00:05:46.409> smart<00:05:47.339> specific<00:05:48.029> programming 00:05:48.619 --> 00:05:48.629 align:start position:0% all this smart specific programming 00:05:48.629 --> 00:05:51.110 align:start position:0% all this smart specific programming complexity<00:05:49.440> and<00:05:49.710> hides<00:05:50.159> non<00:05:50.460> determinism 00:05:51.110 --> 00:05:51.120 align:start position:0% complexity and hides non determinism 00:05:51.120 --> 00:05:55.159 align:start position:0% complexity and hides non determinism without<00:05:51.930> any<00:05:52.289> loss<00:05:52.650> of<00:05:53.389> extra<00:05:54.389> symmetry<00:05:54.629> or 00:05:55.159 --> 00:05:55.169 align:start position:0% without any loss of extra symmetry or 00:05:55.169 --> 00:05:59.059 align:start position:0% without any loss of extra symmetry or power<00:05:55.560> and<00:05:55.800> what<00:05:56.009> you<00:05:56.159> can<00:05:56.339> do<00:05:56.520> with<00:05:56.699> it 00:05:59.059 --> 00:05:59.069 align:start position:0% 00:05:59.069 --> 00:06:02.010 align:start position:0% if<00:06:00.069> you<00:06:00.310> want<00:06:00.580> to<00:06:00.669> check<00:06:00.879> it<00:06:01.060> out<00:06:01.240> thanks<00:06:01.900> to 00:06:02.010 --> 00:06:02.020 align:start position:0% if you want to check it out thanks to 00:06:02.020 --> 00:06:04.200 align:start position:0% if you want to check it out thanks to the<00:06:02.139> guys<00:06:02.319> in<00:06:02.349> the<00:06:02.590> back<00:06:02.860> and<00:06:03.190> good<00:06:03.789> work<00:06:04.000> by 00:06:04.200 --> 00:06:04.210 align:start position:0% the guys in the back and good work by 00:06:04.210 --> 00:06:07.290 align:start position:0% the guys in the back and good work by Tebow<00:06:04.690> there<00:06:04.990> is<00:06:05.110> now<00:06:05.379> remix<00:06:06.310> integration<00:06:07.030> off 00:06:07.290 --> 00:06:07.300 align:start position:0% Tebow there is now remix integration off 00:06:07.300 --> 00:06:09.990 align:start position:0% Tebow there is now remix integration off the<00:06:07.509> tooling<00:06:07.900> so<00:06:08.379> its<00:06:08.830> life<00:06:09.069> on<00:06:09.280> remakes<00:06:09.729> not<00:06:09.970> a 00:06:09.990 --> 00:06:10.000 align:start position:0% the tooling so its life on remakes not a 00:06:10.000 --> 00:06:11.670 align:start position:0% the tooling so its life on remakes not a very<00:06:10.300> dangerous<00:06:10.479> version<00:06:10.990> but<00:06:11.199> you<00:06:11.229> can<00:06:11.500> go 00:06:11.670 --> 00:06:11.680 align:start position:0% very dangerous version but you can go 00:06:11.680 --> 00:06:13.830 align:start position:0% very dangerous version but you can go play<00:06:11.979> around<00:06:12.129> with<00:06:12.430> it<00:06:12.639> to<00:06:12.819> get<00:06:13.180> a<00:06:13.240> feeling<00:06:13.690> and 00:06:13.830 --> 00:06:13.840 align:start position:0% play around with it to get a feeling and 00:06:13.840 --> 00:06:15.600 align:start position:0% play around with it to get a feeling and you<00:06:13.930> can<00:06:14.139> go<00:06:14.289> through<00:06:14.560> all<00:06:14.680> the<00:06:14.889> steps<00:06:15.099> writing 00:06:15.600 --> 00:06:15.610 align:start position:0% you can go through all the steps writing 00:06:15.610 --> 00:06:17.180 align:start position:0% you can go through all the steps writing the<00:06:15.669> program<00:06:15.879> compiling<00:06:16.599> executing 00:06:17.180 --> 00:06:17.190 align:start position:0% the program compiling executing 00:06:17.190 --> 00:06:20.399 align:start position:0% the program compiling executing absolutely<00:06:18.270> and<00:06:19.270> also<00:06:19.629> there's<00:06:20.020> going<00:06:20.259> to<00:06:20.349> be 00:06:20.399 --> 00:06:20.409 align:start position:0% absolutely and also there's going to be 00:06:20.409 --> 00:06:22.830 align:start position:0% absolutely and also there's going to be a<00:06:20.500> workshop<00:06:20.800> tomorrow<00:06:21.610> from<00:06:22.150> release<00:06:22.539> and 00:06:22.830 --> 00:06:22.840 align:start position:0% a workshop tomorrow from release and 00:06:22.840 --> 00:06:26.580 align:start position:0% a workshop tomorrow from release and then<00:06:22.990> go<00:06:23.169> into<00:06:23.349> more<00:06:23.620> details<00:06:24.099> about<00:06:24.340> that<00:06:25.590> and 00:06:26.580 --> 00:06:26.590 align:start position:0% then go into more details about that and 00:06:26.590 --> 00:06:29.010 align:start position:0% then go into more details about that and I<00:06:27.009> will<00:06:27.190> hand<00:06:27.460> over<00:06:27.520> to<00:06:27.729> Tebow<00:06:28.270> from<00:06:28.509> bit<00:06:28.659> of<00:06:28.870> a 00:06:29.010 --> 00:06:29.020 align:start position:0% I will hand over to Tebow from bit of a 00:06:29.020 --> 00:06:33.210 align:start position:0% I will hand over to Tebow from bit of a deaf<00:06:29.259> update<00:06:29.590> what<00:06:29.800> happened<00:06:30.159> s<00:06:30.340> here<00:06:32.220> right 00:06:33.210 --> 00:06:33.220 align:start position:0% deaf update what happened s here right 00:06:33.220 --> 00:06:37.830 align:start position:0% deaf update what happened s here right so<00:06:34.919> the<00:06:35.919> first<00:06:36.130> thing<00:06:36.370> that<00:06:36.400> we<00:06:36.819> focused<00:06:37.240> on<00:06:37.360> or 00:06:37.830 --> 00:06:37.840 align:start position:0% so the first thing that we focused on or 00:06:37.840 --> 00:06:40.830 align:start position:0% so the first thing that we focused on or last<00:06:38.169> month<00:06:38.409> is<00:06:38.770> adding<00:06:39.639> more<00:06:39.940> explicit<00:06:40.389> e<00:06:40.599> to 00:06:40.830 --> 00:06:40.840 align:start position:0% last month is adding more explicit e to 00:06:40.840 --> 00:06:44.460 align:start position:0% last month is adding more explicit e to the<00:06:40.960> syste<00:06:41.800> types<00:06:42.060> well<00:06:43.060> for<00:06:43.960> those<00:06:44.199> of<00:06:44.259> you 00:06:44.460 --> 00:06:44.470 align:start position:0% the syste types well for those of you 00:06:44.470 --> 00:06:47.010 align:start position:0% the syste types well for those of you who<00:06:44.620> actually<00:06:44.949> use<00:06:45.340> sort<00:06:45.699> is<00:06:45.849> before<00:06:46.210> we<00:06:46.900> have 00:06:47.010 --> 00:06:47.020 align:start position:0% who actually use sort is before we have 00:06:47.020 --> 00:06:49.110 align:start position:0% who actually use sort is before we have very<00:06:47.289> basic<00:06:47.860> times<00:06:48.310> that<00:06:48.580> were<00:06:48.699> basically 00:06:49.110 --> 00:06:49.120 align:start position:0% very basic times that were basically 00:06:49.120 --> 00:06:52.010 align:start position:0% very basic times that were basically chill<00:06:49.870> elements<00:06:50.349> which<00:06:50.650> you<00:06:50.680> can<00:06:50.919> think<00:06:50.949> as 00:06:52.010 --> 00:06:52.020 align:start position:0% chill elements which you can think as 00:06:52.020 --> 00:06:55.170 align:start position:0% chill elements which you can think as integers<00:06:53.020> and<00:06:53.530> we<00:06:53.680> have<00:06:53.860> boolean's<00:06:54.250> but 00:06:55.170 --> 00:06:55.180 align:start position:0% integers and we have boolean's but 00:06:55.180 --> 00:06:57.869 align:start position:0% integers and we have boolean's but within<00:06:55.389> we<00:06:55.659> have<00:06:55.960> complex<00:06:56.560> it<00:06:57.250> made<00:06:57.490> it<00:06:57.639> quite 00:06:57.869 --> 00:06:57.879 align:start position:0% within we have complex it made it quite 00:06:57.879 --> 00:06:59.939 align:start position:0% within we have complex it made it quite very<00:06:58.120> lowest<00:06:58.240> to<00:06:58.479> my<00:06:58.599> programs<00:06:59.050> so<00:06:59.710> what<00:06:59.830> we 00:06:59.939 --> 00:06:59.949 align:start position:0% very lowest to my programs so what we 00:06:59.949 --> 00:07:03.140 align:start position:0% very lowest to my programs so what we added<00:07:00.129> is<00:07:00.460> a<00:07:01.090> race<00:07:01.719> of<00:07:02.020> multiple<00:07:02.650> dimensions 00:07:03.140 --> 00:07:03.150 align:start position:0% added is a race of multiple dimensions 00:07:03.150 --> 00:07:05.820 align:start position:0% added is a race of multiple dimensions when<00:07:04.150> it<00:07:04.270> comes<00:07:04.690> to<00:07:04.960> create<00:07:05.380> them<00:07:05.560> with<00:07:05.590> a 00:07:05.820 --> 00:07:05.830 align:start position:0% when it comes to create them with a 00:07:05.830 --> 00:07:07.980 align:start position:0% when it comes to create them with a given<00:07:06.190> value<00:07:06.430> as<00:07:07.240> well<00:07:07.449> as<00:07:07.509> the<00:07:07.599> spread 00:07:07.980 --> 00:07:07.990 align:start position:0% given value as well as the spread 00:07:07.990 --> 00:07:09.749 align:start position:0% given value as well as the spread operators<00:07:08.530> actually<00:07:08.919> might<00:07:09.099> know<00:07:09.340> from 00:07:09.749 --> 00:07:09.759 align:start position:0% operators actually might know from 00:07:09.759 --> 00:07:12.540 align:start position:0% operators actually might know from Jasper<00:07:10.569> to<00:07:10.690> all<00:07:10.840> the<00:07:10.930> languages<00:07:11.349> as<00:07:12.280> well<00:07:12.340> as 00:07:12.540 --> 00:07:12.550 align:start position:0% Jasper to all the languages as well as 00:07:12.550 --> 00:07:14.249 align:start position:0% Jasper to all the languages as well as slice<00:07:12.909> things<00:07:13.180> against<00:07:13.539> the<00:07:13.719> part<00:07:13.990> of<00:07:14.080> the 00:07:14.249 --> 00:07:14.259 align:start position:0% slice things against the part of the 00:07:14.259 --> 00:07:17.749 align:start position:0% slice things against the part of the right<00:07:14.409> so<00:07:14.770> what<00:07:14.919> I'm<00:07:15.039> gonna<00:07:15.190> see 00:07:17.749 --> 00:07:17.759 align:start position:0% 00:07:17.759 --> 00:07:20.739 align:start position:0% in<00:07:18.539> the<00:07:18.929> same<00:07:19.199> sort<00:07:19.619> of<00:07:19.649> spirit<00:07:20.009> we<00:07:20.159> added 00:07:20.739 --> 00:07:20.749 align:start position:0% in the same sort of spirit we added 00:07:20.749 --> 00:07:25.100 align:start position:0% in the same sort of spirit we added structures<00:07:22.069> which<00:07:23.479> enable<00:07:24.479> you<00:07:24.599> to<00:07:24.629> create 00:07:25.100 --> 00:07:25.110 align:start position:0% structures which enable you to create 00:07:25.110 --> 00:07:27.350 align:start position:0% structures which enable you to create composite<00:07:25.619> types<00:07:25.979> to<00:07:26.369> represent<00:07:27.209> for<00:07:27.299> example 00:07:27.350 --> 00:07:27.360 align:start position:0% composite types to represent for example 00:07:27.360 --> 00:07:30.169 align:start position:0% composite types to represent for example at<00:07:27.809> point<00:07:28.049> of<00:07:28.169> an<00:07:28.289> entity<00:07:28.439> curve<00:07:28.789> like<00:07:29.789> you're 00:07:30.169 --> 00:07:30.179 align:start position:0% at point of an entity curve like you're 00:07:30.179 --> 00:07:31.819 align:start position:0% at point of an entity curve like you're useful<00:07:30.479> in<00:07:30.749> the<00:07:30.839> context<00:07:31.139> of<00:07:31.259> stars<00:07:31.499> if<00:07:31.679> you 00:07:31.819 --> 00:07:31.829 align:start position:0% useful in the context of stars if you 00:07:31.829 --> 00:07:33.919 align:start position:0% useful in the context of stars if you trying<00:07:32.399> to<00:07:32.519> verify<00:07:32.729> a<00:07:32.939> signature<00:07:33.449> inside<00:07:33.839> the 00:07:33.919 --> 00:07:33.929 align:start position:0% trying to verify a signature inside the 00:07:33.929 --> 00:07:37.999 align:start position:0% trying to verify a signature inside the Sun<00:07:35.269> and<00:07:36.269> while<00:07:36.989> the<00:07:37.079> things<00:07:37.289> here<00:07:37.709> we<00:07:37.860> also 00:07:37.999 --> 00:07:38.009 align:start position:0% Sun and while the things here we also 00:07:38.009 --> 00:07:40.579 align:start position:0% Sun and while the things here we also have<00:07:38.189> for<00:07:38.759> structures<00:07:39.119> and<00:07:39.629> mutation<00:07:40.349> and 00:07:40.579 --> 00:07:40.589 align:start position:0% have for structures and mutation and 00:07:40.589 --> 00:07:43.129 align:start position:0% have for structures and mutation and access<00:07:41.009> as<00:07:41.279> you<00:07:41.429> would<00:07:41.549> expect<00:07:41.809> as<00:07:42.809> you<00:07:42.989> have 00:07:43.129 --> 00:07:43.139 align:start position:0% access as you would expect as you have 00:07:43.139 --> 00:07:46.339 align:start position:0% access as you would expect as you have make<00:07:43.799> other<00:07:44.009> divisions<00:07:44.719> so<00:07:45.719> that's<00:07:45.929> right<00:07:46.139> now 00:07:46.339 --> 00:07:46.349 align:start position:0% make other divisions so that's right now 00:07:46.349 --> 00:07:54.079 align:start position:0% make other divisions so that's right now under<00:07:47.089> this<00:07:48.089> series<00:07:48.860> very<00:07:49.860> recently<00:07:53.089> this 00:07:54.079 --> 00:07:54.089 align:start position:0% under this series very recently this 00:07:54.089 --> 00:07:56.329 align:start position:0% under this series very recently this these<00:07:54.749> new<00:07:54.989> types<00:07:55.289> and<00:07:55.619> more<00:07:55.679> complex<00:07:56.099> types 00:07:56.329 --> 00:07:56.339 align:start position:0% these new types and more complex types 00:07:56.339 --> 00:07:59.559 align:start position:0% these new types and more complex types bring<00:07:56.909> us<00:07:57.059> even<00:07:57.329> closer<00:07:58.139> to<00:07:58.379> a<00:07:58.409> higher-level 00:07:59.559 --> 00:07:59.569 align:start position:0% bring us even closer to a higher-level 00:07:59.569 --> 00:08:03.109 align:start position:0% bring us even closer to a higher-level language<00:08:00.569> and<00:08:00.869> that's<00:08:01.349> what<00:08:01.619> this<00:08:02.009> is<00:08:02.279> and<00:08:02.610> it 00:08:03.109 --> 00:08:03.119 align:start position:0% language and that's what this is and it 00:08:03.119 --> 00:08:06.589 align:start position:0% language and that's what this is and it enables<00:08:03.689> you<00:08:04.469> developers<00:08:05.339> to<00:08:05.639> have<00:08:05.969> code 00:08:06.589 --> 00:08:06.599 align:start position:0% enables you developers to have code 00:08:06.599 --> 00:08:09.199 align:start position:0% enables you developers to have code that's<00:08:06.919> clearer<00:08:07.919> and<00:08:08.219> cleaner 00:08:09.199 --> 00:08:09.209 align:start position:0% that's clearer and cleaner 00:08:09.209 --> 00:08:11.649 align:start position:0% that's clearer and cleaner however<00:08:10.169> we<00:08:10.319> don't<00:08:10.469> want<00:08:10.709> to<00:08:10.860> sacrifice 00:08:11.649 --> 00:08:11.659 align:start position:0% however we don't want to sacrifice 00:08:11.659 --> 00:08:16.039 align:start position:0% however we don't want to sacrifice performance<00:08:13.429> in<00:08:14.429> terms<00:08:15.119> of<00:08:15.389> the<00:08:15.509> size<00:08:15.779> of<00:08:15.929> the 00:08:16.039 --> 00:08:16.049 align:start position:0% performance in terms of the size of the 00:08:16.049 --> 00:08:18.799 align:start position:0% performance in terms of the size of the circuit<00:08:16.349> that<00:08:16.499> gets<00:08:16.739> generated<00:08:17.329> so<00:08:18.329> in 00:08:18.799 --> 00:08:18.809 align:start position:0% circuit that gets generated so in 00:08:18.809 --> 00:08:21.409 align:start position:0% circuit that gets generated so in interviews<00:08:19.709> who<00:08:19.979> can<00:08:20.159> write<00:08:20.339> clear<00:08:21.059> school 00:08:21.409 --> 00:08:21.419 align:start position:0% interviews who can write clear school 00:08:21.419 --> 00:08:24.319 align:start position:0% interviews who can write clear school code<00:08:21.809> that's<00:08:22.229> okay<00:08:22.589> with<00:08:22.709> this<00:08:22.800> world<00:08:23.069> by<00:08:23.939> a 00:08:24.319 --> 00:08:24.329 align:start position:0% code that's okay with this world by a 00:08:24.329 --> 00:08:26.659 align:start position:0% code that's okay with this world by a number<00:08:24.929> of<00:08:25.259> simple<00:08:25.860> yet<00:08:26.429> powerful 00:08:26.659 --> 00:08:26.669 align:start position:0% number of simple yet powerful 00:08:26.669 --> 00:08:29.929 align:start position:0% number of simple yet powerful maximization<00:08:27.569> steps<00:08:27.869> to<00:08:28.559> program<00:08:28.979> in<00:08:29.849> order 00:08:29.929 --> 00:08:29.939 align:start position:0% maximization steps to program in order 00:08:29.939 --> 00:08:32.299 align:start position:0% maximization steps to program in order to<00:08:30.119> reduce<00:08:30.479> the<00:08:30.779> size<00:08:31.019> of<00:08:31.050> the<00:08:31.829> program<00:08:32.189> as 00:08:32.299 --> 00:08:32.309 align:start position:0% to reduce the size of the program as 00:08:32.309 --> 00:08:34.759 align:start position:0% to reduce the size of the program as much<00:08:32.430> as<00:08:32.579> possible<00:08:32.759> so<00:08:33.240> these<00:08:33.769> optimizations 00:08:34.759 --> 00:08:34.769 align:start position:0% much as possible so these optimizations 00:08:34.769 --> 00:08:36.679 align:start position:0% much as possible so these optimizations are<00:08:35.490> the<00:08:35.729> ones<00:08:35.909> you<00:08:36.029> would<00:08:36.149> find<00:08:36.389> in<00:08:36.569> many 00:08:36.679 --> 00:08:36.689 align:start position:0% are the ones you would find in many 00:08:36.689 --> 00:08:38.679 align:start position:0% are the ones you would find in many programming<00:08:37.110> languages<00:08:37.469> along<00:08:38.370> that 00:08:38.679 --> 00:08:38.689 align:start position:0% programming languages along that 00:08:38.689 --> 00:08:40.730 align:start position:0% programming languages along that constant<00:08:39.689> propagation<00:08:40.019> which<00:08:40.379> basically 00:08:40.730 --> 00:08:40.740 align:start position:0% constant propagation which basically 00:08:40.740 --> 00:08:42.649 align:start position:0% constant propagation which basically computes<00:08:41.309> as<00:08:41.579> much<00:08:41.849> as<00:08:42.059> possible<00:08:42.240> in<00:08:42.539> your 00:08:42.649 --> 00:08:42.659 align:start position:0% computes as much as possible in your 00:08:42.659 --> 00:08:45.350 align:start position:0% computes as much as possible in your program<00:08:43.019> at<00:08:43.620> compile<00:08:44.159> time<00:08:44.279> if<00:08:44.730> you<00:08:45.209> have 00:08:45.350 --> 00:08:45.360 align:start position:0% program at compile time if you have 00:08:45.360 --> 00:08:46.639 align:start position:0% program at compile time if you have constants<00:08:45.930> in<00:08:46.019> your<00:08:46.110> program<00:08:46.410> for<00:08:46.529> example 00:08:46.639 --> 00:08:46.649 align:start position:0% constants in your program for example 00:08:46.649 --> 00:08:53.030 align:start position:0% constants in your program for example all<00:08:47.160> of<00:08:47.279> this<00:08:47.399> is<00:08:47.579> going<00:08:47.819> to<00:08:47.910> be<00:08:48.089> already 00:08:53.030 --> 00:08:53.040 align:start position:0% 00:08:53.040 --> 00:08:55.620 align:start position:0% removing<00:08:54.040> old<00:08:54.160> linear<00:08:54.880> constraints<00:08:55.450> those 00:08:55.620 --> 00:08:55.630 align:start position:0% removing old linear constraints those 00:08:55.630 --> 00:08:56.940 align:start position:0% removing old linear constraints those thoughts<00:08:55.990> are<00:08:56.140> based<00:08:56.380> on<00:08:56.530> quadratic 00:08:56.940 --> 00:08:56.950 align:start position:0% thoughts are based on quadratic 00:08:56.950 --> 00:08:58.050 align:start position:0% thoughts are based on quadratic constraints<00:08:57.400> to<00:08:57.490> all<00:08:57.670> the<00:08:57.820> linear 00:08:58.050 --> 00:08:58.060 align:start position:0% constraints to all the linear 00:08:58.060 --> 00:09:00.510 align:start position:0% constraints to all the linear constraints<00:08:58.510> are<00:08:59.130> substituted<00:09:00.130> so<00:09:00.250> that<00:09:00.430> you 00:09:00.510 --> 00:09:00.520 align:start position:0% constraints are substituted so that you 00:09:00.520 --> 00:09:04.680 align:start position:0% constraints are substituted so that you only<00:09:00.790> have<00:09:01.090> to<00:09:01.270> cut<00:09:01.480> right<00:09:01.690> histories<00:09:02.400> and<00:09:03.690> few 00:09:04.680 --> 00:09:04.690 align:start position:0% only have to cut right histories and few 00:09:04.690 --> 00:09:06.630 align:start position:0% only have to cut right histories and few other<00:09:04.840> optimizations<00:09:05.530> that<00:09:05.590> we<00:09:05.920> network<00:09:06.400> for 00:09:06.630 --> 00:09:06.640 align:start position:0% other optimizations that we network for 00:09:06.640 --> 00:09:08.730 align:start position:0% other optimizations that we network for and<00:09:07.300> we<00:09:07.390> even<00:09:07.630> have<00:09:07.780> quite<00:09:08.050> good<00:09:08.080> results<00:09:08.620> in 00:09:08.730 --> 00:09:08.740 align:start position:0% and we even have quite good results in 00:09:08.740 --> 00:09:15.390 align:start position:0% and we even have quite good results in them<00:09:10.410> on<00:09:11.410> a<00:09:11.470> different<00:09:12.400> and<00:09:14.400> compiler 00:09:15.390 --> 00:09:15.400 align:start position:0% them on a different and compiler 00:09:15.400 --> 00:09:19.460 align:start position:0% them on a different and compiler pipeline<00:09:15.970> we<00:09:17.220> changed<00:09:18.220> from<00:09:18.310> a<00:09:18.760> hand-written 00:09:19.460 --> 00:09:19.470 align:start position:0% pipeline we changed from a hand-written 00:09:19.470 --> 00:09:22.020 align:start position:0% pipeline we changed from a hand-written pasta<00:09:20.470> that<00:09:20.620> we<00:09:20.770> were<00:09:20.890> using<00:09:21.130> and<00:09:21.460> the<00:09:21.820> first 00:09:22.020 --> 00:09:22.030 align:start position:0% pasta that we were using and the first 00:09:22.030 --> 00:09:23.550 align:start position:0% pasta that we were using and the first version<00:09:22.180> of<00:09:22.390> the<00:09:22.480> practice<00:09:22.600> to<00:09:22.780> a<00:09:23.110> pasta 00:09:23.550 --> 00:09:23.560 align:start position:0% version of the practice to a pasta 00:09:23.560 --> 00:09:26.970 align:start position:0% version of the practice to a pasta generator<00:09:24.210> so<00:09:25.210> this<00:09:25.360> is<00:09:25.510> quite<00:09:25.660> internal<00:09:26.230> but 00:09:26.970 --> 00:09:26.980 align:start position:0% generator so this is quite internal but 00:09:26.980 --> 00:09:29.970 align:start position:0% generator so this is quite internal but basically<00:09:27.430> the<00:09:28.390> idea<00:09:28.450> is<00:09:28.750> that<00:09:29.080> we<00:09:29.440> used<00:09:29.710> to 00:09:29.970 --> 00:09:29.980 align:start position:0% basically the idea is that we used to 00:09:29.980 --> 00:09:32.370 align:start position:0% basically the idea is that we used to have<00:09:30.220> a<00:09:30.280> positive<00:09:30.610> be<00:09:31.030> written<00:09:31.330> by<00:09:31.480> that<00:09:31.810> book 00:09:32.370 --> 00:09:32.380 align:start position:0% have a positive be written by that book 00:09:32.380 --> 00:09:34.560 align:start position:0% have a positive be written by that book by<00:09:32.560> hands<00:09:32.800> to<00:09:33.310> parse<00:09:33.730> from<00:09:33.940> source<00:09:34.180> code<00:09:34.240> to 00:09:34.560 --> 00:09:34.570 align:start position:0% by hands to parse from source code to 00:09:34.570 --> 00:09:37.260 align:start position:0% by hands to parse from source code to the<00:09:34.690> ast<00:09:35.320> and<00:09:35.590> now<00:09:36.190> we<00:09:36.250> have<00:09:36.700> the<00:09:36.940> formal 00:09:37.260 --> 00:09:37.270 align:start position:0% the ast and now we have the formal 00:09:37.270 --> 00:09:40.170 align:start position:0% the ast and now we have the formal formal<00:09:38.140> specification<00:09:38.890> of<00:09:39.400> our<00:09:39.550> grammar<00:09:39.760> that 00:09:40.170 --> 00:09:40.180 align:start position:0% formal specification of our grammar that 00:09:40.180 --> 00:09:43.710 align:start position:0% formal specification of our grammar that generates<00:09:40.900> a<00:09:41.110> pasta<00:09:41.590> automatically<00:09:42.720> which 00:09:43.710 --> 00:09:43.720 align:start position:0% generates a pasta automatically which 00:09:43.720 --> 00:09:45.750 align:start position:0% generates a pasta automatically which actually<00:09:44.260> gave<00:09:44.440> us<00:09:44.620> better<00:09:45.010> performance<00:09:45.580> in 00:09:45.750 --> 00:09:45.760 align:start position:0% actually gave us better performance in 00:09:45.760 --> 00:09:48.360 align:start position:0% actually gave us better performance in some<00:09:45.910> cases<00:09:46.320> which<00:09:47.320> would<00:09:47.650> signal<00:09:48.010> that<00:09:48.040> our 00:09:48.360 --> 00:09:48.370 align:start position:0% some cases which would signal that our 00:09:48.370 --> 00:09:50.430 align:start position:0% some cases which would signal that our handwritten<00:09:49.030> pasta<00:09:49.480> was<00:09:49.630> actually<00:09:49.930> that 00:09:50.430 --> 00:09:50.440 align:start position:0% handwritten pasta was actually that 00:09:50.440 --> 00:09:54.090 align:start position:0% handwritten pasta was actually that efficient<00:09:50.920> and<00:09:51.160> also<00:09:51.790> interestingly<00:09:52.920> made<00:09:53.920> it 00:09:54.090 --> 00:09:54.100 align:start position:0% efficient and also interestingly made it 00:09:54.100 --> 00:09:56.460 align:start position:0% efficient and also interestingly made it much<00:09:55.090> more<00:09:55.300> simpler<00:09:55.720> for<00:09:55.930> us<00:09:56.050> to<00:09:56.230> implement 00:09:56.460 --> 00:09:56.470 align:start position:0% much more simpler for us to implement 00:09:56.470 --> 00:09:59.280 align:start position:0% much more simpler for us to implement new<00:09:57.340> types<00:09:58.240> that<00:09:58.480> I<00:09:58.600> just<00:09:58.900> described 00:09:59.280 --> 00:09:59.290 align:start position:0% new types that I just described 00:09:59.290 --> 00:10:02.520 align:start position:0% new types that I just described structures<00:10:00.010> and<00:10:00.220> even<00:10:00.340> rice<00:10:00.940> so<00:10:01.660> we<00:10:02.380> would 00:10:02.520 --> 00:10:02.530 align:start position:0% structures and even rice so we would 00:10:02.530 --> 00:10:04.530 align:start position:0% structures and even rice so we would totally<00:10:02.890> encourage<00:10:03.700> anyone<00:10:04.000> working<00:10:04.450> on 00:10:04.530 --> 00:10:04.540 align:start position:0% totally encourage anyone working on 00:10:04.540 --> 00:10:06.870 align:start position:0% totally encourage anyone working on pregnant<00:10:05.020> which<00:10:05.200> is<00:10:05.410> in<00:10:05.950> the<00:10:06.130> early<00:10:06.430> steps<00:10:06.700> of 00:10:06.870 --> 00:10:06.880 align:start position:0% pregnant which is in the early steps of 00:10:06.880 --> 00:10:08.400 align:start position:0% pregnant which is in the early steps of the<00:10:06.970> process<00:10:07.150> to<00:10:07.450> use<00:10:07.600> fossil<00:10:07.780> devices 00:10:08.400 --> 00:10:08.410 align:start position:0% the process to use fossil devices 00:10:08.410 --> 00:10:10.640 align:start position:0% the process to use fossil devices especially<00:10:08.950> using<00:10:09.550> a<00:10:09.640> friend<00:10:09.910> a<00:10:10.090> femoral 00:10:10.640 --> 00:10:10.650 align:start position:0% especially using a friend a femoral 00:10:10.650 --> 00:10:18.420 align:start position:0% especially using a friend a femoral contest<00:10:11.650> it<00:10:12.070> was<00:10:12.310> within<00:10:13.650> creativity<00:10:17.430> then 00:10:18.420 --> 00:10:18.430 align:start position:0% contest it was within creativity then 00:10:18.430 --> 00:10:20.640 align:start position:0% contest it was within creativity then over<00:10:18.940> the<00:10:19.090> course<00:10:19.510> of<00:10:19.570> the<00:10:19.660> past<00:10:19.810> year<00:10:19.960> when<00:10:20.500> we 00:10:20.640 --> 00:10:20.650 align:start position:0% over the course of the past year when we 00:10:20.650 --> 00:10:21.090 align:start position:0% over the course of the past year when we were 00:10:21.090 --> 00:10:21.100 align:start position:0% were 00:10:21.100 --> 00:10:23.910 align:start position:0% were have<00:10:21.550> a<00:10:21.580> simple<00:10:22.210> examples<00:10:22.930> people<00:10:23.590> started 00:10:23.910 --> 00:10:23.920 align:start position:0% have a simple examples people started 00:10:23.920 --> 00:10:26.490 align:start position:0% have a simple examples people started those<00:10:24.040> parts<00:10:24.430> to<00:10:24.970> having<00:10:25.930> more<00:10:26.080> complex 00:10:26.490 --> 00:10:26.500 align:start position:0% those parts to having more complex 00:10:26.500 --> 00:10:28.500 align:start position:0% those parts to having more complex applications<00:10:27.130> we<00:10:27.460> realize<00:10:27.760> that<00:10:28.090> there's<00:10:28.450> a 00:10:28.500 --> 00:10:28.510 align:start position:0% applications we realize that there's a 00:10:28.510 --> 00:10:30.360 align:start position:0% applications we realize that there's a lot<00:10:28.600> of<00:10:28.870> building<00:10:29.440> blocks<00:10:29.680> that<00:10:29.920> people<00:10:30.220> end 00:10:30.360 --> 00:10:30.370 align:start position:0% lot of building blocks that people end 00:10:30.370 --> 00:10:33.360 align:start position:0% lot of building blocks that people end up<00:10:30.520> needing<00:10:30.790> over<00:10:31.600> and<00:10:31.720> over<00:10:31.930> again<00:10:32.020> and<00:10:32.470> that 00:10:33.360 --> 00:10:33.370 align:start position:0% up needing over and over again and that 00:10:33.370 --> 00:10:35.760 align:start position:0% up needing over and over again and that includes<00:10:34.090> suppose<00:10:34.390> the<00:10:34.570> hash<00:10:34.810> functions<00:10:35.260> the 00:10:35.760 --> 00:10:35.770 align:start position:0% includes suppose the hash functions the 00:10:35.770 --> 00:10:36.900 align:start position:0% includes suppose the hash functions the first<00:10:35.980> thing<00:10:36.100> that<00:10:36.250> people<00:10:36.310> want<00:10:36.610> to<00:10:36.640> do<00:10:36.820> is 00:10:36.900 --> 00:10:36.910 align:start position:0% first thing that people want to do is 00:10:36.910 --> 00:10:39.270 align:start position:0% first thing that people want to do is Holloway<00:10:37.540> common<00:10:38.320> computer<00:10:38.590> fashion<00:10:39.040> study 00:10:39.270 --> 00:10:39.280 align:start position:0% Holloway common computer fashion study 00:10:39.280 --> 00:10:43.050 align:start position:0% Holloway common computer fashion study is<00:10:39.430> done<00:10:39.610> as<00:10:40.510> well<00:10:40.780> as<00:10:41.340> amended<00:10:42.340> curves<00:10:42.610> so 00:10:43.050 --> 00:10:43.060 align:start position:0% is done as well as amended curves so 00:10:43.060 --> 00:10:44.430 align:start position:0% is done as well as amended curves so that<00:10:43.210> we<00:10:43.330> can<00:10:43.480> have<00:10:43.720> elliptic<00:10:44.230> curve 00:10:44.430 --> 00:10:44.440 align:start position:0% that we can have elliptic curve 00:10:44.440 --> 00:10:46.890 align:start position:0% that we can have elliptic curve cryptography<00:10:44.550> inside<00:10:45.550> of<00:10:45.700> this<00:10:45.790> table<00:10:46.030> which 00:10:46.890 --> 00:10:46.900 align:start position:0% cryptography inside of this table which 00:10:46.900 --> 00:10:48.660 align:start position:0% cryptography inside of this table which is<00:10:46.930> very<00:10:47.440> powerful<00:10:47.980> especially<00:10:48.100> for 00:10:48.660 --> 00:10:48.670 align:start position:0% is very powerful especially for 00:10:48.670 --> 00:10:51.540 align:start position:0% is very powerful especially for scalability<00:10:49.000> schemes<00:10:49.510> so<00:10:50.410> what<00:10:50.920> we<00:10:51.040> did<00:10:51.250> first 00:10:51.540 --> 00:10:51.550 align:start position:0% scalability schemes so what we did first 00:10:51.550 --> 00:10:54.570 align:start position:0% scalability schemes so what we did first was<00:10:51.910> to<00:10:52.330> use<00:10:52.690> sustaining<00:10:53.620> existing<00:10:54.310> other 00:10:54.570 --> 00:10:54.580 align:start position:0% was to use sustaining existing other 00:10:54.580 --> 00:10:57.690 align:start position:0% was to use sustaining existing other libraries<00:10:55.150> to<00:10:55.680> import<00:10:56.680> those<00:10:57.070> building 00:10:57.690 --> 00:10:57.700 align:start position:0% libraries to import those building 00:10:57.700 --> 00:11:00.600 align:start position:0% libraries to import those building blocks<00:10:57.730> but<00:10:58.560> we<00:10:59.560> we<00:11:00.070> changed<00:11:00.400> our<00:11:00.520> approach 00:11:00.600 --> 00:11:00.610 align:start position:0% blocks but we we changed our approach 00:11:00.610 --> 00:11:04.200 align:start position:0% blocks but we we changed our approach and<00:11:01.030> ended<00:11:01.390> up<00:11:01.770> rewriting<00:11:02.770> all<00:11:03.550> of<00:11:03.880> those 00:11:04.200 --> 00:11:04.210 align:start position:0% and ended up rewriting all of those 00:11:04.210 --> 00:11:07.350 align:start position:0% and ended up rewriting all of those building<00:11:05.080> blocks<00:11:05.110> interpreted<00:11:05.920> itself<00:11:06.360> to 00:11:07.350 --> 00:11:07.360 align:start position:0% building blocks interpreted itself to 00:11:07.360 --> 00:11:09.450 align:start position:0% building blocks interpreted itself to see<00:11:07.540> what<00:11:07.720> it<00:11:07.810> would<00:11:07.870> perform<00:11:08.110> and<00:11:09.010> also<00:11:09.310> to 00:11:09.450 --> 00:11:09.460 align:start position:0% see what it would perform and also to 00:11:09.460 --> 00:11:13.530 align:start position:0% see what it would perform and also to use<00:11:09.670> our<00:11:09.850> own<00:11:11.070> project<00:11:12.070> so<00:11:12.670> the<00:11:13.090> result<00:11:13.420> of 00:11:13.530 --> 00:11:13.540 align:start position:0% use our own project so the result of 00:11:13.540 --> 00:11:16.080 align:start position:0% use our own project so the result of that<00:11:13.660> is<00:11:13.840> that<00:11:13.990> now<00:11:14.170> as<00:11:14.890> Otis<00:11:15.130> ships<00:11:15.670> with<00:11:15.970> a 00:11:16.080 --> 00:11:16.090 align:start position:0% that is that now as Otis ships with a 00:11:16.090 --> 00:11:18.270 align:start position:0% that is that now as Otis ships with a standard<00:11:16.420> library<00:11:16.750> which<00:11:17.650> you<00:11:17.770> can<00:11:17.920> import 00:11:18.270 --> 00:11:18.280 align:start position:0% standard library which you can import 00:11:18.280 --> 00:11:20.220 align:start position:0% standard library which you can import directly<00:11:18.550> from<00:11:19.030> your<00:11:19.300> source<00:11:19.720> code<00:11:19.840> and<00:11:19.900> use 00:11:20.220 --> 00:11:20.230 align:start position:0% directly from your source code and use 00:11:20.230 --> 00:11:23.370 align:start position:0% directly from your source code and use directly<00:11:21.040> that<00:11:21.610> has<00:11:21.850> those<00:11:22.480> utilities<00:11:23.140> so 00:11:23.370 --> 00:11:23.380 align:start position:0% directly that has those utilities so 00:11:23.380 --> 00:11:25.500 align:start position:0% directly that has those utilities so some<00:11:23.650> cryptography<00:11:24.250> some<00:11:24.760> utilities<00:11:25.300> to<00:11:25.420> be 00:11:25.500 --> 00:11:25.510 align:start position:0% some cryptography some utilities to be 00:11:25.510 --> 00:11:27.750 align:start position:0% some cryptography some utilities to be packing<00:11:25.870> and<00:11:26.020> unpacking<00:11:26.110> if<00:11:26.650> you<00:11:26.740> wanna<00:11:26.890> go 00:11:27.750 --> 00:11:27.760 align:start position:0% packing and unpacking if you wanna go 00:11:27.760 --> 00:11:36.150 align:start position:0% packing and unpacking if you wanna go from<00:11:27.940> bits<00:11:28.180> to<00:11:29.550> etc<00:11:32.130> and<00:11:34.290> we<00:11:35.290> also<00:11:35.500> worked<00:11:35.860> on<00:11:36.100> a 00:11:36.150 --> 00:11:36.160 align:start position:0% from bits to etc and we also worked on a 00:11:36.160 --> 00:11:38.670 align:start position:0% from bits to etc and we also worked on a library<00:11:36.640> called<00:11:36.820> my<00:11:37.030> crypto<00:11:37.450> and<00:11:37.720> basically 00:11:38.670 --> 00:11:38.680 align:start position:0% library called my crypto and basically 00:11:38.680 --> 00:11:40.740 align:start position:0% library called my crypto and basically intuition<00:11:39.190> that<00:11:39.430> is<00:11:39.730> that<00:11:39.940> in<00:11:40.270> the<00:11:40.480> same 00:11:40.740 --> 00:11:40.750 align:start position:0% intuition that is that in the same 00:11:40.750 --> 00:11:43.050 align:start position:0% intuition that is that in the same library<00:11:40.960> for<00:11:41.380> example<00:11:41.470> I<00:11:42.130> mentioned<00:11:42.760> that<00:11:42.880> we 00:11:43.050 --> 00:11:43.060 align:start position:0% library for example I mentioned that we 00:11:43.060 --> 00:11:45.720 align:start position:0% library for example I mentioned that we have<00:11:43.270> a<00:11:43.420> curve<00:11:43.840> cryptography<00:11:44.130> so<00:11:45.130> with<00:11:45.520> the 00:11:45.720 --> 00:11:45.730 align:start position:0% have a curve cryptography so with the 00:11:45.730 --> 00:11:47.370 align:start position:0% have a curve cryptography so with the ticker<00:11:46.000> photography<00:11:46.690> you<00:11:46.810> want<00:11:47.020> to<00:11:47.140> be<00:11:47.290> able 00:11:47.370 --> 00:11:47.380 align:start position:0% ticker photography you want to be able 00:11:47.380 --> 00:11:50.700 align:start position:0% ticker photography you want to be able to<00:11:47.640> work<00:11:48.640> for<00:11:48.820> signatures<00:11:49.300> later<00:11:49.660> on<00:11:49.780> however 00:11:50.700 --> 00:11:50.710 align:start position:0% to work for signatures later on however 00:11:50.710 --> 00:11:53.640 align:start position:0% to work for signatures later on however inside<00:11:51.550> of<00:11:51.700> the<00:11:51.790> stock<00:11:52.120> you're<00:11:52.780> always<00:11:53.050> only 00:11:53.640 --> 00:11:53.650 align:start position:0% inside of the stock you're always only 00:11:53.650 --> 00:11:56.220 align:start position:0% inside of the stock you're always only going<00:11:54.190> to<00:11:54.400> verify<00:11:54.670> the<00:11:54.940> signature<00:11:55.510> you're<00:11:56.080> not 00:11:56.220 --> 00:11:56.230 align:start position:0% going to verify the signature you're not 00:11:56.230 --> 00:11:58.020 align:start position:0% going to verify the signature you're not going<00:11:56.440> to<00:11:56.530> generate<00:11:57.310> the<00:11:57.400> signatures<00:11:57.850> because 00:11:58.020 --> 00:11:58.030 align:start position:0% going to generate the signatures because 00:11:58.030 --> 00:12:00.480 align:start position:0% going to generate the signatures because generates<00:11:58.870> a<00:11:59.110> signature<00:11:59.560> look<00:12:00.160> at<00:12:00.310> that 00:12:00.480 --> 00:12:00.490 align:start position:0% generates a signature look at that 00:12:00.490 --> 00:12:03.930 align:start position:0% generates a signature look at that before<00:12:01.110> hitting<00:12:02.110> the<00:12:02.260> stock<00:12:02.860> itself<00:12:03.160> so<00:12:03.700> this 00:12:03.930 --> 00:12:03.940 align:start position:0% before hitting the stock itself so this 00:12:03.940 --> 00:12:06.750 align:start position:0% before hitting the stock itself so this high<00:12:04.600> crypto<00:12:05.050> is<00:12:05.290> our<00:12:05.500> current<00:12:05.950> approach<00:12:06.400> to 00:12:06.750 --> 00:12:06.760 align:start position:0% high crypto is our current approach to 00:12:06.760 --> 00:12:09.060 align:start position:0% high crypto is our current approach to this<00:12:06.850> missing<00:12:07.240> component<00:12:07.920> everything<00:12:08.920> that 00:12:09.060 --> 00:12:09.070 align:start position:0% this missing component everything that 00:12:09.070 --> 00:12:11.270 align:start position:0% this missing component everything that you<00:12:09.190> can<00:12:09.340> basically<00:12:09.550> do<00:12:10.000> before<00:12:10.660> you<00:12:10.840> install 00:12:11.270 --> 00:12:11.280 align:start position:0% you can basically do before you install 00:12:11.280 --> 00:12:14.280 align:start position:0% you can basically do before you install in<00:12:12.280> this<00:12:12.400> case<00:12:12.640> there<00:12:13.450> is<00:12:13.540> the<00:12:13.660> example<00:12:13.960> of 00:12:14.280 --> 00:12:14.290 align:start position:0% in this case there is the example of 00:12:14.290 --> 00:12:17.520 align:start position:0% in this case there is the example of Hollywood<00:12:14.950> sign<00:12:15.910> message<00:12:16.780> with<00:12:16.930> the<00:12:17.020> ETS<00:12:17.350> a 00:12:17.520 --> 00:12:17.530 align:start position:0% Hollywood sign message with the ETS a 00:12:17.530 --> 00:12:21.090 align:start position:0% Hollywood sign message with the ETS a and<00:12:17.860> then<00:12:18.820> based<00:12:19.060> on<00:12:19.300> on<00:12:19.600> this<00:12:20.020> piece<00:12:20.320> of<00:12:20.500> I 00:12:21.090 --> 00:12:21.100 align:start position:0% and then based on on this piece of I 00:12:21.100 --> 00:12:23.070 align:start position:0% and then based on on this piece of I think<00:12:21.580> code<00:12:21.730> you<00:12:21.940> can<00:12:22.090> take<00:12:22.300> output<00:12:22.750> of<00:12:22.870> that 00:12:23.070 --> 00:12:23.080 align:start position:0% think code you can take output of that 00:12:23.080 --> 00:12:25.470 align:start position:0% think code you can take output of that and<00:12:23.350> then<00:12:23.680> feed<00:12:24.430> that<00:12:24.550> into<00:12:24.760> the<00:12:24.940> stock<00:12:25.180> the 00:12:25.470 --> 00:12:25.480 align:start position:0% and then feed that into the stock the 00:12:25.480 --> 00:12:27.300 align:start position:0% and then feed that into the stock the stock<00:12:25.540> would<00:12:26.050> verify<00:12:26.500> that<00:12:26.860> the<00:12:27.160> signature 00:12:27.300 --> 00:12:27.310 align:start position:0% stock would verify that the signature 00:12:27.310 --> 00:12:34.050 align:start position:0% stock would verify that the signature you<00:12:28.090> created<00:12:28.720> is<00:12:28.810> actually<00:12:28.960> valid<00:12:29.680> to<00:12:33.060> finally 00:12:34.050 --> 00:12:34.060 align:start position:0% you created is actually valid to finally 00:12:34.060 --> 00:12:36.600 align:start position:0% you created is actually valid to finally we<00:12:34.930> worked<00:12:35.290> on<00:12:35.590> integrating<00:12:36.220> with<00:12:36.400> all 00:12:36.600 --> 00:12:36.610 align:start position:0% we worked on integrating with all 00:12:36.610 --> 00:12:38.220 align:start position:0% we worked on integrating with all backends<00:12:37.090> so<00:12:37.330> we<00:12:37.450> used<00:12:37.600> to<00:12:37.720> integrate<00:12:38.080> with 00:12:38.220 --> 00:12:38.230 align:start position:0% backends so we used to integrate with 00:12:38.230 --> 00:12:41.250 align:start position:0% backends so we used to integrate with only<00:12:38.590> this<00:12:38.890> not<00:12:39.130> which<00:12:39.430> is<00:12:40.020> super<00:12:41.020> specific 00:12:41.250 --> 00:12:41.260 align:start position:0% only this not which is super specific 00:12:41.260 --> 00:12:45.420 align:start position:0% only this not which is super specific limitation<00:12:41.980> of<00:12:42.510> pre-processing<00:12:43.510> stocks<00:12:44.430> we 00:12:45.420 --> 00:12:45.430 align:start position:0% limitation of pre-processing stocks we 00:12:45.430 --> 00:12:48.240 align:start position:0% limitation of pre-processing stocks we added<00:12:46.330> support<00:12:46.510> for<00:12:46.840> gamma<00:12:47.350> which<00:12:47.770> is<00:12:47.920> a<00:12:47.950> rust 00:12:48.240 --> 00:12:48.250 align:start position:0% added support for gamma which is a rust 00:12:48.250 --> 00:12:53.370 align:start position:0% added support for gamma which is a rust based<00:12:48.640> Hoover<00:12:49.600> test<00:12:49.840> we<00:12:50.290> use<00:12:50.500> by<00:12:50.970> cash<00:12:52.020> as<00:12:53.020> well 00:12:53.370 --> 00:12:53.380 align:start position:0% based Hoover test we use by cash as well 00:12:53.380 --> 00:12:56.820 align:start position:0% based Hoover test we use by cash as well as<00:12:53.680> we've<00:12:54.040> been<00:12:55.230> designing<00:12:56.230> and<00:12:56.470> also 00:12:56.820 --> 00:12:56.830 align:start position:0% as we've been designing and also 00:12:56.830 --> 00:12:59.340 align:start position:0% as we've been designing and also developing<00:12:57.580> integration<00:12:58.420> with<00:12:58.570> something 00:12:59.340 --> 00:12:59.350 align:start position:0% developing integration with something 00:12:59.350 --> 00:13:01.560 align:start position:0% developing integration with something called<00:12:59.500> Zika<00:12:59.710> interface<00:13:00.190> so<00:13:00.700> maybe<00:13:01.089> some<00:13:01.450> of 00:13:01.560 --> 00:13:01.570 align:start position:0% called Zika interface so maybe some of 00:13:01.570 --> 00:13:03.360 align:start position:0% called Zika interface so maybe some of you<00:13:01.660> have<00:13:01.810> heard<00:13:01.960> of<00:13:02.020> it<00:13:02.260> it<00:13:02.410> comes<00:13:03.130> from<00:13:03.220> the 00:13:03.360 --> 00:13:03.370 align:start position:0% you have heard of it it comes from the 00:13:03.370 --> 00:13:06.540 align:start position:0% you have heard of it it comes from the seek<00:13:03.550> a<00:13:03.670> proof<00:13:04.350> initiative<00:13:05.370> which<00:13:06.370> is 00:13:06.540 --> 00:13:06.550 align:start position:0% seek a proof initiative which is 00:13:06.550 --> 00:13:09.590 align:start position:0% seek a proof initiative which is basically<00:13:06.940> a<00:13:07.300> standard<00:13:07.839> for<00:13:08.560> backends<00:13:09.100> of 00:13:09.590 --> 00:13:09.600 align:start position:0% basically a standard for backends of 00:13:09.600 --> 00:13:12.660 align:start position:0% basically a standard for backends of reverse<00:13:10.600> proof<00:13:10.810> systems<00:13:11.230> and<00:13:11.470> basically<00:13:12.160> what 00:13:12.660 --> 00:13:12.670 align:start position:0% reverse proof systems and basically what 00:13:12.670 --> 00:13:16.200 align:start position:0% reverse proof systems and basically what this<00:13:12.790> means<00:13:12.850> is<00:13:13.240> that<00:13:13.300> using<00:13:14.260> Socrates<00:13:15.210> it 00:13:16.200 --> 00:13:16.210 align:start position:0% this means is that using Socrates it 00:13:16.210 --> 00:13:18.360 align:start position:0% this means is that using Socrates it will<00:13:16.600> soon<00:13:16.870> be<00:13:16.900> possible<00:13:17.650> to<00:13:17.800> integrate<00:13:18.010> with 00:13:18.360 --> 00:13:18.370 align:start position:0% will soon be possible to integrate with 00:13:18.370 --> 00:13:21.360 align:start position:0% will soon be possible to integrate with all<00:13:19.270> the<00:13:19.630> new<00:13:20.140> schemes<00:13:20.530> that<00:13:20.860> came<00:13:21.070> up<00:13:21.220> with 00:13:21.360 --> 00:13:21.370 align:start position:0% all the new schemes that came up with 00:13:21.370 --> 00:13:21.910 align:start position:0% all the new schemes that came up with Sibley's 00:13:21.910 --> 00:13:21.920 align:start position:0% Sibley's 00:13:21.920 --> 00:13:24.940 align:start position:0% Sibley's some<00:13:22.220> of<00:13:22.310> you<00:13:22.430> saw<00:13:22.639> long<00:13:23.269> and<00:13:23.660> SuperSonics<00:13:24.470> and 00:13:24.940 --> 00:13:24.950 align:start position:0% some of you saw long and SuperSonics and 00:13:24.950 --> 00:13:26.530 align:start position:0% some of you saw long and SuperSonics and all<00:13:25.160> this<00:13:25.279> is<00:13:25.519> Kingston<00:13:26.000> papa 00:13:26.530 --> 00:13:26.540 align:start position:0% all this is Kingston papa 00:13:26.540 --> 00:13:28.360 align:start position:0% all this is Kingston papa and<00:13:26.990> we<00:13:27.079> think<00:13:27.320> it<00:13:27.410> would<00:13:27.529> be<00:13:27.589> really<00:13:28.010> really 00:13:28.360 --> 00:13:28.370 align:start position:0% and we think it would be really really 00:13:28.370 --> 00:13:30.879 align:start position:0% and we think it would be really really valuable<00:13:28.700> as<00:13:29.360> you<00:13:29.480> could<00:13:29.630> just<00:13:29.839> write<00:13:30.589> your 00:13:30.879 --> 00:13:30.889 align:start position:0% valuable as you could just write your 00:13:30.889 --> 00:13:32.560 align:start position:0% valuable as you could just write your program<00:13:31.279> authorities<00:13:31.790> and<00:13:32.000> then<00:13:32.269> would 00:13:32.560 --> 00:13:32.570 align:start position:0% program authorities and then would 00:13:32.570 --> 00:13:34.180 align:start position:0% program authorities and then would completely<00:13:32.990> would<00:13:33.230> interoperate<00:13:33.800> with<00:13:33.829> any 00:13:34.180 --> 00:13:34.190 align:start position:0% completely would interoperate with any 00:13:34.190 --> 00:13:35.920 align:start position:0% completely would interoperate with any of<00:13:34.370> those<00:13:34.519> backends<00:13:35.029> because<00:13:35.570> they<00:13:35.720> always 00:13:35.920 --> 00:13:35.930 align:start position:0% of those backends because they always 00:13:35.930 --> 00:13:41.500 align:start position:0% of those backends because they always have<00:13:36.079> the<00:13:36.380> same<00:13:36.410> assumption<00:13:40.000> so<00:13:41.000> now<00:13:41.449> I'm 00:13:41.500 --> 00:13:41.510 align:start position:0% have the same assumption so now I'm 00:13:41.510 --> 00:13:43.689 align:start position:0% have the same assumption so now I'm going<00:13:41.839> to<00:13:42.110> go<00:13:42.440> through<00:13:42.860> much<00:13:43.040> the<00:13:43.160> obligations 00:13:43.689 --> 00:13:43.699 align:start position:0% going to go through much the obligations 00:13:43.699 --> 00:13:45.129 align:start position:0% going to go through much the obligations that<00:13:43.910> people<00:13:44.300> have<00:13:44.420> been<00:13:44.570> building<00:13:44.750> is<00:13:44.990> of 00:13:45.129 --> 00:13:45.139 align:start position:0% that people have been building is of 00:13:45.139 --> 00:13:51.090 align:start position:0% that people have been building is of these<00:13:45.350> I<00:13:45.730> had<00:13:46.730> to<00:13:46.850> actually<00:13:47.029> change<00:13:47.990> the<00:13:48.139> name 00:13:51.090 --> 00:13:51.100 align:start position:0% 00:13:51.100 --> 00:13:53.010 align:start position:0% okay<00:13:51.670> now<00:13:51.880> we<00:13:51.940> heard<00:13:52.210> a<00:13:52.270> bit<00:13:52.480> more<00:13:52.690> on<00:13:52.900> the 00:13:53.010 --> 00:13:53.020 align:start position:0% okay now we heard a bit more on the 00:13:53.020 --> 00:13:54.810 align:start position:0% okay now we heard a bit more on the background<00:13:53.440> and<00:13:53.650> in<00:13:53.770> turn<00:13:53.950> changes<00:13:54.400> now<00:13:54.760> we 00:13:54.810 --> 00:13:54.820 align:start position:0% background and in turn changes now we 00:13:54.820 --> 00:13:57.000 align:start position:0% background and in turn changes now we want<00:13:55.180> to<00:13:55.300> look<00:13:55.420> at<00:13:55.630> what's<00:13:55.870> actually<00:13:56.080> hasn't 00:13:57.000 --> 00:13:57.010 align:start position:0% want to look at what's actually hasn't 00:13:57.010 --> 00:13:58.920 align:start position:0% want to look at what's actually hasn't been<00:13:57.250> done<00:13:57.520> or<00:13:57.820> is<00:13:58.000> currently<00:13:58.420> being<00:13:58.690> done 00:13:58.920 --> 00:13:58.930 align:start position:0% been done or is currently being done 00:13:58.930 --> 00:14:01.830 align:start position:0% been done or is currently being done with<00:13:59.200> the<00:13:59.320> tooling<00:13:59.710> we<00:14:00.280> provide<00:14:00.670> so<00:14:01.270> first 00:14:01.830 --> 00:14:01.840 align:start position:0% with the tooling we provide so first 00:14:01.840 --> 00:14:06.720 align:start position:0% with the tooling we provide so first project<00:14:02.380> is<00:14:02.650> ey<00:14:03.550> nightfall<00:14:04.480> and<00:14:05.460> uni<00:14:06.460> Falls 00:14:06.720 --> 00:14:06.730 align:start position:0% project is ey nightfall and uni Falls 00:14:06.730 --> 00:14:08.640 align:start position:0% project is ey nightfall and uni Falls project<00:14:07.300> for<00:14:07.480> Christian<00:14:07.930> young<00:14:08.080> worldwide 00:14:08.640 --> 00:14:08.650 align:start position:0% project for Christian young worldwide 00:14:08.650 --> 00:14:11.270 align:start position:0% project for Christian young worldwide and<00:14:08.980> it's<00:14:09.580> basically<00:14:10.000> a<00:14:10.150> privacy-preserving 00:14:11.270 --> 00:14:11.280 align:start position:0% and it's basically a privacy-preserving 00:14:11.280 --> 00:14:14.670 align:start position:0% and it's basically a privacy-preserving implementation<00:14:12.280> of<00:14:12.430> piercing<00:14:12.850> 20<00:14:13.210> new<00:14:13.330> fc7<00:14:14.080> 21 00:14:14.670 --> 00:14:14.680 align:start position:0% implementation of piercing 20 new fc7 21 00:14:14.680 --> 00:14:17.370 align:start position:0% implementation of piercing 20 new fc7 21 to<00:14:14.860> open<00:14:15.130> standards<00:14:15.610> on<00:14:16.090> this<00:14:16.300> theorem<00:14:16.690> so 00:14:17.370 --> 00:14:17.380 align:start position:0% to open standards on this theorem so 00:14:17.380 --> 00:14:20.430 align:start position:0% to open standards on this theorem so that<00:14:17.620> you<00:14:17.800> can<00:14:18.040> have<00:14:18.250> these<00:14:18.610> tokens<00:14:18.970> in<00:14:19.600> and 00:14:20.430 --> 00:14:20.440 align:start position:0% that you can have these tokens in and 00:14:20.440 --> 00:14:23.190 align:start position:0% that you can have these tokens in and use<00:14:20.800> them<00:14:21.070> with<00:14:21.550> complete<00:14:22.090> privacy<00:14:22.540> on<00:14:23.140> e 00:14:23.190 --> 00:14:23.200 align:start position:0% use them with complete privacy on e 00:14:23.200 --> 00:14:26.700 align:start position:0% use them with complete privacy on e theorem<00:14:23.740> so<00:14:24.400> we<00:14:24.610> will<00:14:24.820> today<00:14:25.330> not<00:14:25.990> go<00:14:26.320> into 00:14:26.700 --> 00:14:26.710 align:start position:0% theorem so we will today not go into 00:14:26.710 --> 00:14:29.430 align:start position:0% theorem so we will today not go into much<00:14:27.310> detail<00:14:27.340> about<00:14:28.060> that<00:14:28.510> because<00:14:28.780> on<00:14:29.200> main 00:14:29.430 --> 00:14:29.440 align:start position:0% much detail about that because on main 00:14:29.440 --> 00:14:31.080 align:start position:0% much detail about that because on main stage<00:14:29.710> tomorrow<00:14:30.010> there's<00:14:30.550> going<00:14:30.820> to<00:14:30.910> be<00:14:30.970> a 00:14:31.080 --> 00:14:31.090 align:start position:0% stage tomorrow there's going to be a 00:14:31.090 --> 00:14:33.750 align:start position:0% stage tomorrow there's going to be a talk<00:14:31.420> about<00:14:31.870> the<00:14:32.020> project<00:14:32.500> by<00:14:33.130> the<00:14:33.190> UI<00:14:33.550> for 00:14:33.750 --> 00:14:33.760 align:start position:0% talk about the project by the UI for 00:14:33.760 --> 00:14:37.350 align:start position:0% talk about the project by the UI for stem<00:14:34.390> cells<00:14:34.750> and<00:14:35.640> what's<00:14:36.640> interesting<00:14:37.000> to 00:14:37.350 --> 00:14:37.360 align:start position:0% stem cells and what's interesting to 00:14:37.360 --> 00:14:39.720 align:start position:0% stem cells and what's interesting to note<00:14:37.390> though<00:14:37.750> is<00:14:37.780> that<00:14:38.020> was<00:14:38.560> not<00:14:38.740> like<00:14:39.010> us 00:14:39.720 --> 00:14:39.730 align:start position:0% note though is that was not like us 00:14:39.730 --> 00:14:41.940 align:start position:0% note though is that was not like us going<00:14:40.330> to<00:14:40.630> them<00:14:40.840> and<00:14:41.080> telling<00:14:41.290> them<00:14:41.410> please 00:14:41.940 --> 00:14:41.950 align:start position:0% going to them and telling them please 00:14:41.950 --> 00:14:43.890 align:start position:0% going to them and telling them please use<00:14:42.280> it<00:14:42.310> and<00:14:42.730> we'll<00:14:42.940> help<00:14:43.150> you<00:14:43.420> but<00:14:43.750> they 00:14:43.890 --> 00:14:43.900 align:start position:0% use it and we'll help you but they 00:14:43.900 --> 00:14:46.410 align:start position:0% use it and we'll help you but they picked<00:14:44.110> it<00:14:44.320> up<00:14:44.490> independently<00:14:45.490> and<00:14:45.910> actually 00:14:46.410 --> 00:14:46.420 align:start position:0% picked it up independently and actually 00:14:46.420 --> 00:14:48.390 align:start position:0% picked it up independently and actually built<00:14:46.810> it<00:14:47.050> and<00:14:47.380> we<00:14:47.830> didn't<00:14:48.040> really<00:14:48.130> know<00:14:48.370> that 00:14:48.390 --> 00:14:48.400 align:start position:0% built it and we didn't really know that 00:14:48.400 --> 00:14:50.790 align:start position:0% built it and we didn't really know that they<00:14:48.790> did<00:14:49.000> it<00:14:49.030> unless<00:14:49.540> they're<00:14:49.780> Indies<00:14:50.050> right 00:14:50.790 --> 00:14:50.800 align:start position:0% they did it unless they're Indies right 00:14:50.800 --> 00:14:53.250 align:start position:0% they did it unless they're Indies right so<00:14:51.370> that<00:14:51.580> was<00:14:51.760> for<00:14:52.060> us<00:14:52.180> cool<00:14:52.480> to<00:14:52.630> see<00:14:52.810> as<00:14:52.990> kind 00:14:53.250 --> 00:14:53.260 align:start position:0% so that was for us cool to see as kind 00:14:53.260 --> 00:14:55.800 align:start position:0% so that was for us cool to see as kind of<00:14:53.320> a<00:14:53.470> validation<00:14:53.890> that<00:14:54.610> cooling<00:14:55.210> is<00:14:55.360> actually 00:14:55.800 --> 00:14:55.810 align:start position:0% of a validation that cooling is actually 00:14:55.810 --> 00:14:58.200 align:start position:0% of a validation that cooling is actually useful<00:14:56.020> for<00:14:56.230> people<00:14:56.920> and<00:14:57.340> projects<00:14:57.880> are<00:14:58.030> a 00:14:58.200 --> 00:14:58.210 align:start position:0% useful for people and projects are a 00:14:58.210 --> 00:15:01.680 align:start position:0% useful for people and projects are a little<00:14:58.540> bit<00:14:59.640> something<00:15:00.640> else<00:15:00.850> is<00:15:01.090> a<00:15:01.120> joint 00:15:01.680 --> 00:15:01.690 align:start position:0% little bit something else is a joint 00:15:01.690 --> 00:15:05.750 align:start position:0% little bit something else is a joint project<00:15:01.920> we<00:15:02.920> did<00:15:03.130> with<00:15:03.420> centrifuge<00:15:04.420> so 00:15:05.750 --> 00:15:05.760 align:start position:0% project we did with centrifuge so 00:15:05.760 --> 00:15:09.090 align:start position:0% project we did with centrifuge so centrifuge<00:15:06.760> is<00:15:07.090> a<00:15:07.170> service<00:15:08.170> for<00:15:08.200> financial 00:15:09.090 --> 00:15:09.100 align:start position:0% centrifuge is a service for financial 00:15:09.100 --> 00:15:11.220 align:start position:0% centrifuge is a service for financial documents<00:15:09.820> and<00:15:09.910> it<00:15:10.120> basically<00:15:10.240> means<00:15:10.810> we<00:15:11.110> have 00:15:11.220 --> 00:15:11.230 align:start position:0% documents and it basically means we have 00:15:11.230 --> 00:15:14.640 align:start position:0% documents and it basically means we have an<00:15:11.440> apartment<00:15:11.830> that<00:15:12.730> two<00:15:13.390> people<00:15:13.780> or<00:15:14.110> a<00:15:14.350> bunch 00:15:14.640 --> 00:15:14.650 align:start position:0% an apartment that two people or a bunch 00:15:14.650 --> 00:15:17.430 align:start position:0% an apartment that two people or a bunch of<00:15:14.770> people<00:15:14.920> agree<00:15:15.670> on<00:15:16.000> off<00:15:16.420> change<00:15:16.990> its 00:15:17.430 --> 00:15:17.440 align:start position:0% of people agree on off change its 00:15:17.440 --> 00:15:19.710 align:start position:0% of people agree on off change its marching<00:15:17.890> protocol<00:15:18.340> but<00:15:18.940> these<00:15:19.360> documents 00:15:19.710 --> 00:15:19.720 align:start position:0% marching protocol but these documents 00:15:19.720 --> 00:15:22.050 align:start position:0% marching protocol but these documents financial<00:15:20.200> documents<00:15:20.920> for<00:15:21.040> example<00:15:21.070> invoices 00:15:22.050 --> 00:15:22.060 align:start position:0% financial documents for example invoices 00:15:22.060 --> 00:15:24.300 align:start position:0% financial documents for example invoices they<00:15:22.240> get<00:15:22.390> anchored<00:15:22.840> on<00:15:23.230> the<00:15:23.290> blockchain<00:15:23.800> and 00:15:24.300 --> 00:15:24.310 align:start position:0% they get anchored on the blockchain and 00:15:24.310 --> 00:15:28.050 align:start position:0% they get anchored on the blockchain and then<00:15:25.150> it<00:15:25.930> provides<00:15:26.500> a<00:15:27.010> single<00:15:27.700> reference 00:15:28.050 --> 00:15:28.060 align:start position:0% then it provides a single reference 00:15:28.060 --> 00:15:30.750 align:start position:0% then it provides a single reference point<00:15:28.600> everybody<00:15:29.260> can<00:15:29.650> point<00:15:29.920> to<00:15:30.160> right<00:15:30.550> so 00:15:30.750 --> 00:15:30.760 align:start position:0% point everybody can point to right so 00:15:30.760 --> 00:15:33.980 align:start position:0% point everybody can point to right so that<00:15:30.940> stood<00:15:31.330> of<00:15:31.660> centrifuge<00:15:32.380> model<00:15:32.850> but 00:15:33.980 --> 00:15:33.990 align:start position:0% that stood of centrifuge model but 00:15:33.990 --> 00:15:37.560 align:start position:0% that stood of centrifuge model but having<00:15:34.990> claims<00:15:35.650> that<00:15:36.520> means<00:15:36.820> if<00:15:37.120> there's<00:15:37.330> non 00:15:37.560 --> 00:15:37.570 align:start position:0% having claims that means if there's non 00:15:37.570 --> 00:15:40.350 align:start position:0% having claims that means if there's non poet<00:15:37.990> unpaid<00:15:38.590> invoice<00:15:39.070> and<00:15:39.400> I<00:15:39.730> have<00:15:39.970> to<00:15:40.150> write 00:15:40.350 --> 00:15:40.360 align:start position:0% poet unpaid invoice and I have to write 00:15:40.360 --> 00:15:42.180 align:start position:0% poet unpaid invoice and I have to write to<00:15:40.390> retrieve<00:15:40.930> that<00:15:41.170> payment<00:15:41.590> that's<00:15:41.710> actually 00:15:42.180 --> 00:15:42.190 align:start position:0% to retrieve that payment that's actually 00:15:42.190 --> 00:15:44.610 align:start position:0% to retrieve that payment that's actually valid<00:15:42.610> it<00:15:42.730> would<00:15:42.880> be<00:15:43.030> nice<00:15:43.240> to<00:15:43.270> unlock<00:15:43.870> that<00:15:44.110> on 00:15:44.610 --> 00:15:44.620 align:start position:0% valid it would be nice to unlock that on 00:15:44.620 --> 00:15:47.190 align:start position:0% valid it would be nice to unlock that on the<00:15:45.250> blockchain<00:15:45.490> right<00:15:45.910> bring<00:15:46.420> that<00:15:46.450> to 00:15:47.190 --> 00:15:47.200 align:start position:0% the blockchain right bring that to 00:15:47.200 --> 00:15:50.740 align:start position:0% the blockchain right bring that to theorem<00:15:48.040> as<00:15:48.340> kind<00:15:48.670> of<00:15:48.820> a<00:15:49.060> token<00:15:49.660> to<00:15:49.810> talk 00:15:50.740 --> 00:15:50.750 align:start position:0% theorem as kind of a token to talk 00:15:50.750 --> 00:15:54.430 align:start position:0% theorem as kind of a token to talk so<00:15:51.050> forget<00:15:51.460> centrifuge<00:15:52.460> wants<00:15:53.180> to<00:15:53.330> be<00:15:53.480> an<00:15:53.750> FTEs 00:15:54.430 --> 00:15:54.440 align:start position:0% so forget centrifuge wants to be an FTEs 00:15:54.440 --> 00:15:57.100 align:start position:0% so forget centrifuge wants to be an FTEs that<00:15:54.500> kind<00:15:54.860> of<00:15:55.300> tokenized<00:15:56.300> acclaim<00:15:56.810> to 00:15:57.100 --> 00:15:57.110 align:start position:0% that kind of tokenized acclaim to 00:15:57.110 --> 00:15:58.990 align:start position:0% that kind of tokenized acclaim to retrieve<00:15:57.500> the<00:15:57.650> payment<00:15:58.130> I<00:15:58.250> party<00:15:58.850> in<00:15:58.940> the 00:15:58.990 --> 00:15:59.000 align:start position:0% retrieve the payment I party in the 00:15:59.000 --> 00:16:01.600 align:start position:0% retrieve the payment I party in the future<00:15:59.390> and<00:15:59.660> of<00:15:59.990> course<00:16:00.290> what's<00:16:00.590> important<00:16:01.130> is 00:16:01.600 --> 00:16:01.610 align:start position:0% future and of course what's important is 00:16:01.610 --> 00:16:04.020 align:start position:0% future and of course what's important is credit<00:16:02.240> rating<00:16:02.660> of<00:16:02.900> that<00:16:03.230> counterparty 00:16:04.020 --> 00:16:04.030 align:start position:0% credit rating of that counterparty 00:16:04.030 --> 00:16:07.150 align:start position:0% credit rating of that counterparty because<00:16:05.030> it<00:16:05.450> kind<00:16:05.870> of<00:16:05.930> gives<00:16:06.260> you<00:16:06.410> an<00:16:06.980> estimate 00:16:07.150 --> 00:16:07.160 align:start position:0% because it kind of gives you an estimate 00:16:07.160 --> 00:16:09.670 align:start position:0% because it kind of gives you an estimate of<00:16:07.580> your<00:16:07.790> expected<00:16:08.330> value<00:16:08.360> that<00:16:08.990> you<00:16:09.260> will<00:16:09.470> be 00:16:09.670 --> 00:16:09.680 align:start position:0% of your expected value that you will be 00:16:09.680 --> 00:16:11.410 align:start position:0% of your expected value that you will be able<00:16:09.830> to<00:16:10.160> retrieve<00:16:10.550> after<00:16:11.000> you<00:16:11.060> can<00:16:11.210> purchase 00:16:11.410 --> 00:16:11.420 align:start position:0% able to retrieve after you can purchase 00:16:11.420 --> 00:16:15.310 align:start position:0% able to retrieve after you can purchase that<00:16:11.810> program<00:16:12.440> okay<00:16:13.070> so<00:16:13.850> they<00:16:14.210> built<00:16:14.510> this<00:16:14.660> but 00:16:15.310 --> 00:16:15.320 align:start position:0% that program okay so they built this but 00:16:15.320 --> 00:16:18.820 align:start position:0% that program okay so they built this but the<00:16:15.740> problem<00:16:16.160> is<00:16:16.370> to<00:16:16.970> minted<00:16:17.390> entities<00:16:17.990> in<00:16:18.320> the 00:16:18.820 --> 00:16:18.830 align:start position:0% the problem is to minted entities in the 00:16:18.830 --> 00:16:21.850 align:start position:0% the problem is to minted entities in the correct<00:16:19.190> way<00:16:19.460> to<00:16:20.200> make<00:16:21.200> sure<00:16:21.380> that<00:16:21.560> you<00:16:21.710> need 00:16:21.850 --> 00:16:21.860 align:start position:0% correct way to make sure that you need 00:16:21.860 --> 00:16:24.340 align:start position:0% correct way to make sure that you need to<00:16:22.010> expose<00:16:22.460> the<00:16:22.820> value<00:16:23.210> of<00:16:23.420> the<00:16:23.570> invoice<00:16:23.870> which 00:16:24.340 --> 00:16:24.350 align:start position:0% to expose the value of the invoice which 00:16:24.350 --> 00:16:27.100 align:start position:0% to expose the value of the invoice which can<00:16:24.710> be<00:16:24.950> initiatives<00:16:25.460> sometimes<00:16:25.910> and<00:16:26.240> you 00:16:27.100 --> 00:16:27.110 align:start position:0% can be initiatives sometimes and you 00:16:27.110 --> 00:16:28.900 align:start position:0% can be initiatives sometimes and you also<00:16:27.350> need<00:16:27.710> to<00:16:27.980> expose<00:16:28.310> the<00:16:28.670> buyers 00:16:28.900 --> 00:16:28.910 align:start position:0% also need to expose the buyers 00:16:28.910 --> 00:16:31.420 align:start position:0% also need to expose the buyers identities<00:16:29.690> or<00:16:30.050> the<00:16:30.860> counterparties 00:16:31.420 --> 00:16:31.430 align:start position:0% identities or the counterparties 00:16:31.430 --> 00:16:33.880 align:start position:0% identities or the counterparties identity<00:16:32.000> so<00:16:32.420> you<00:16:32.450> will<00:16:32.840> know<00:16:33.020> whether<00:16:33.380> yes 00:16:33.880 --> 00:16:33.890 align:start position:0% identity so you will know whether yes 00:16:33.890 --> 00:16:35.860 align:start position:0% identity so you will know whether yes with<00:16:34.190> credit<00:16:34.580> rating<00:16:34.910> or<00:16:35.030> not<00:16:35.150> and<00:16:35.450> otherwise 00:16:35.860 --> 00:16:35.870 align:start position:0% with credit rating or not and otherwise 00:16:35.870 --> 00:16:37.330 align:start position:0% with credit rating or not and otherwise you're<00:16:36.110> not<00:16:36.260> going<00:16:36.560> to<00:16:36.680> buy<00:16:36.830> the<00:16:36.890> circuit 00:16:37.330 --> 00:16:37.340 align:start position:0% you're not going to buy the circuit 00:16:37.340 --> 00:16:39.850 align:start position:0% you're not going to buy the circuit right<00:16:37.490> so<00:16:38.060> nice<00:16:38.570> idea<00:16:38.990> but<00:16:39.050> it's<00:16:39.470> not<00:16:39.500> really 00:16:39.850 --> 00:16:39.860 align:start position:0% right so nice idea but it's not really 00:16:39.860 --> 00:16:41.440 align:start position:0% right so nice idea but it's not really gonna<00:16:40.010> wear<00:16:40.190> it<00:16:40.340> out<00:16:40.460> because<00:16:40.820> this 00:16:41.440 --> 00:16:41.450 align:start position:0% gonna wear it out because this 00:16:41.450 --> 00:16:43.780 align:start position:0% gonna wear it out because this information<00:16:41.660> is<00:16:42.080> quite<00:16:42.380> sensitive<00:16:42.620> so<00:16:43.520> with 00:16:43.780 --> 00:16:43.790 align:start position:0% information is quite sensitive so with 00:16:43.790 --> 00:16:46.270 align:start position:0% information is quite sensitive so with the<00:16:43.940> Socrates<00:16:44.480> based<00:16:45.020> approach<00:16:45.410> we<00:16:45.770> were<00:16:45.860> able 00:16:46.270 --> 00:16:46.280 align:start position:0% the Socrates based approach we were able 00:16:46.280 --> 00:16:48.460 align:start position:0% the Socrates based approach we were able to<00:16:46.310> replace<00:16:46.850> these<00:16:47.150> checks<00:16:47.480> by<00:16:47.780> using<00:16:47.990> C<00:16:48.260> kiss 00:16:48.460 --> 00:16:48.470 align:start position:0% to replace these checks by using C kiss 00:16:48.470 --> 00:16:50.710 align:start position:0% to replace these checks by using C kiss arms<00:16:48.800> and<00:16:49.010> now<00:16:49.430> the<00:16:49.490> only<00:16:50.000> information<00:16:50.240> that's 00:16:50.710 --> 00:16:50.720 align:start position:0% arms and now the only information that's 00:16:50.720 --> 00:16:53.680 align:start position:0% arms and now the only information that's exposed<00:16:51.170> fermenting<00:16:51.950> Emma<00:16:52.100> teases<00:16:52.700> the<00:16:53.270> token 00:16:53.680 --> 00:16:53.690 align:start position:0% exposed fermenting Emma teases the token 00:16:53.690 --> 00:16:55.600 align:start position:0% exposed fermenting Emma teases the token amount<00:16:54.020> and<00:16:54.320> it's<00:16:54.500> guaranteed<00:16:54.710> to<00:16:55.010> be<00:16:55.310> smaller 00:16:55.600 --> 00:16:55.610 align:start position:0% amount and it's guaranteed to be smaller 00:16:55.610 --> 00:16:57.280 align:start position:0% amount and it's guaranteed to be smaller than<00:16:55.880> an<00:16:56.030> invoice<00:16:56.360> amount<00:16:56.750> that<00:16:56.960> allows<00:16:57.140> you 00:16:57.280 --> 00:16:57.290 align:start position:0% than an invoice amount that allows you 00:16:57.290 --> 00:16:59.290 align:start position:0% than an invoice amount that allows you to<00:16:57.350> also<00:16:57.650> set<00:16:58.040> up<00:16:58.190> an<00:16:58.400> invoice<00:16:58.670> into<00:16:59.060> several 00:16:59.290 --> 00:16:59.300 align:start position:0% to also set up an invoice into several 00:16:59.300 --> 00:17:02.380 align:start position:0% to also set up an invoice into several NF<00:16:59.690> T's<00:16:59.900> and<00:17:00.220> the<00:17:01.220> counterparties<00:17:02.000> credit 00:17:02.380 --> 00:17:02.390 align:start position:0% NF T's and the counterparties credit 00:17:02.390 --> 00:17:04.780 align:start position:0% NF T's and the counterparties credit rating<00:17:02.750> so<00:17:03.170> you<00:17:03.230> can<00:17:03.440> only<00:17:03.710> learn<00:17:04.100> the<00:17:04.640> key 00:17:04.780 --> 00:17:04.790 align:start position:0% rating so you can only learn the key 00:17:04.790 --> 00:17:06.820 align:start position:0% rating so you can only learn the key fact<00:17:05.120> that<00:17:05.480> you're<00:17:05.720> kind<00:17:06.020> of<00:17:06.110> talking<00:17:06.320> that 00:17:06.820 --> 00:17:06.830 align:start position:0% fact that you're kind of talking that 00:17:06.830 --> 00:17:10.180 align:start position:0% fact that you're kind of talking that you're<00:17:07.010> buying<00:17:07.280> a<00:17:07.880> claim<00:17:08.480> for<00:17:09.440> basically<00:17:09.980> is 00:17:10.180 --> 00:17:10.190 align:start position:0% you're buying a claim for basically is 00:17:10.190 --> 00:17:13.060 align:start position:0% you're buying a claim for basically is credit<00:17:11.090> worthy<00:17:11.480> but<00:17:11.900> you<00:17:12.080> do<00:17:12.230> not<00:17:12.410> learn<00:17:12.680> who 00:17:13.060 --> 00:17:13.070 align:start position:0% credit worthy but you do not learn who 00:17:13.070 --> 00:17:15.370 align:start position:0% credit worthy but you do not learn who exactly<00:17:13.610> it<00:17:13.910> is<00:17:13.940> and<00:17:14.240> that's<00:17:14.450> that's<00:17:14.870> key<00:17:15.200> in 00:17:15.370 --> 00:17:15.380 align:start position:0% exactly it is and that's that's key in 00:17:15.380 --> 00:17:19.090 align:start position:0% exactly it is and that's that's key in the<00:17:15.500> protocol<00:17:17.020> how<00:17:18.020> it<00:17:18.080> works<00:17:18.470> is<00:17:18.710> that<00:17:18.740> we 00:17:19.090 --> 00:17:19.100 align:start position:0% the protocol how it works is that we 00:17:19.100 --> 00:17:22.720 align:start position:0% the protocol how it works is that we basically<00:17:20.080> replace<00:17:21.080> a<00:17:21.110> traditional<00:17:21.920> NFT 00:17:22.720 --> 00:17:22.730 align:start position:0% basically replace a traditional NFT 00:17:22.730 --> 00:17:25.000 align:start position:0% basically replace a traditional NFT registry<00:17:23.420> that<00:17:23.720> does<00:17:23.930> these<00:17:24.170> checks<00:17:24.500> on<00:17:24.740> the 00:17:25.000 --> 00:17:25.010 align:start position:0% registry that does these checks on the 00:17:25.010 --> 00:17:27.820 align:start position:0% registry that does these checks on the blockchain<00:17:25.510> through<00:17:26.510> a<00:17:26.780> Socrates<00:17:27.320> program 00:17:27.820 --> 00:17:27.830 align:start position:0% blockchain through a Socrates program 00:17:27.830 --> 00:17:30.760 align:start position:0% blockchain through a Socrates program and<00:17:28.130> then<00:17:28.910> Socrates<00:17:29.210> program<00:17:29.900> does<00:17:30.260> all<00:17:30.530> these 00:17:30.760 --> 00:17:30.770 align:start position:0% and then Socrates program does all these 00:17:30.770 --> 00:17:33.040 align:start position:0% and then Socrates program does all these checks<00:17:31.100> as<00:17:31.370> part<00:17:31.820> of<00:17:31.970> the<00:17:32.090> C<00:17:32.240> case<00:17:32.480> mark<00:17:32.780> and 00:17:33.040 --> 00:17:33.050 align:start position:0% checks as part of the C case mark and 00:17:33.050 --> 00:17:35.770 align:start position:0% checks as part of the C case mark and after<00:17:33.770> it<00:17:33.890> did<00:17:34.100> that<00:17:34.310> hit<00:17:35.090> generate<00:17:35.270> you 00:17:35.770 --> 00:17:35.780 align:start position:0% after it did that hit generate you 00:17:35.780 --> 00:17:38.350 align:start position:0% after it did that hit generate you generate<00:17:36.170> two<00:17:36.320> CK's<00:17:36.650> not<00:17:36.860> proof<00:17:37.160> submitted<00:17:38.030> to 00:17:38.350 --> 00:17:38.360 align:start position:0% generate two CK's not proof submitted to 00:17:38.360 --> 00:17:40.360 align:start position:0% generate two CK's not proof submitted to a<00:17:38.390> non<00:17:38.570> chained<00:17:38.840> token<00:17:39.230> registry<00:17:39.740> and<00:17:40.160> that 00:17:40.360 --> 00:17:40.370 align:start position:0% a non chained token registry and that 00:17:40.370 --> 00:17:42.370 align:start position:0% a non chained token registry and that munching<00:17:40.760> token<00:17:41.120> registry<00:17:41.540> density<00:17:42.140> checks 00:17:42.370 --> 00:17:42.380 align:start position:0% munching token registry density checks 00:17:42.380 --> 00:17:44.590 align:start position:0% munching token registry density checks is<00:17:42.710> proof<00:17:43.130> correct<00:17:43.490> or<00:17:43.880> is<00:17:44.060> proved<00:17:44.390> not 00:17:44.590 --> 00:17:44.600 align:start position:0% is proof correct or is proved not 00:17:44.600 --> 00:17:47.470 align:start position:0% is proof correct or is proved not correct<00:17:44.930> and<00:17:45.170> if<00:17:45.860> successful<00:17:46.370> the<00:17:47.000> token<00:17:47.390> is 00:17:47.470 --> 00:17:47.480 align:start position:0% correct and if successful the token is 00:17:47.480 --> 00:17:49.660 align:start position:0% correct and if successful the token is mentioned<00:17:47.930> and<00:17:48.260> only<00:17:48.680> is<00:17:48.800> that<00:17:48.950> information<00:17:49.280> I 00:17:49.660 --> 00:17:49.670 align:start position:0% mentioned and only is that information I 00:17:49.670 --> 00:17:51.640 align:start position:0% mentioned and only is that information I mentioned<00:17:50.060> before<00:17:50.180> and<00:17:50.690> some 00:17:51.640 --> 00:17:51.650 align:start position:0% mentioned before and some 00:17:51.650 --> 00:17:53.049 align:start position:0% mentioned before and some just<00:17:51.800> to<00:17:51.890> make<00:17:52.040> sure<00:17:52.070> the<00:17:52.340> right<00:17:52.520> data<00:17:52.760> was 00:17:53.049 --> 00:17:53.059 align:start position:0% just to make sure the right data was 00:17:53.059 --> 00:17:55.750 align:start position:0% just to make sure the right data was news<00:17:53.240> are<00:17:53.780> exposed<00:17:54.559> in<00:17:54.830> the<00:17:54.980> process<00:17:55.400> so 00:17:55.750 --> 00:17:55.760 align:start position:0% news are exposed in the process so 00:17:55.760 --> 00:17:59.020 align:start position:0% news are exposed in the process so that's<00:17:55.910> quite<00:17:56.180> nice<00:17:56.710> the<00:17:57.710> implementation<00:17:58.700> the 00:17:59.020 --> 00:17:59.030 align:start position:0% that's quite nice the implementation the 00:17:59.030 --> 00:18:01.360 align:start position:0% that's quite nice the implementation the core<00:17:59.360> part<00:17:59.900> of<00:18:00.020> the<00:18:00.140> code<00:18:00.380> I<00:18:00.950> mean<00:18:01.160> there's 00:18:01.360 --> 00:18:01.370 align:start position:0% core part of the code I mean there's 00:18:01.370 --> 00:18:05.380 align:start position:0% core part of the code I mean there's some<00:18:01.550> utility<00:18:01.750> functions<00:18:02.750> and<00:18:03.280> stuff<00:18:04.280> is<00:18:04.490> 80 00:18:05.380 --> 00:18:05.390 align:start position:0% some utility functions and stuff is 80 00:18:05.390 --> 00:18:08.860 align:start position:0% some utility functions and stuff is 80 lines<00:18:05.690> of<00:18:05.900> Socrates<00:18:06.380> core<00:18:07.250> DSL<00:18:07.850> code<00:18:08.150> and<00:18:08.720> you 00:18:08.860 --> 00:18:08.870 align:start position:0% lines of Socrates core DSL code and you 00:18:08.870 --> 00:18:11.070 align:start position:0% lines of Socrates core DSL code and you can<00:18:08.900> find<00:18:09.320> it<00:18:09.470> here<00:18:09.500> on<00:18:10.190> get<00:18:10.460> up<00:18:10.610> and 00:18:11.070 --> 00:18:11.080 align:start position:0% can find it here on get up and 00:18:11.080 --> 00:18:15.030 align:start position:0% can find it here on get up and verification<00:18:12.080> cost<00:18:12.380> was<00:18:12.950> 900<00:18:13.700> K<00:18:13.880> gas<00:18:14.210> for<00:18:14.750> the 00:18:15.030 --> 00:18:15.040 align:start position:0% verification cost was 900 K gas for the 00:18:15.040 --> 00:18:17.110 align:start position:0% verification cost was 900 K gas for the prototypical<00:18:16.040> implementation<00:18:16.850> that<00:18:16.940> was 00:18:17.110 --> 00:18:17.120 align:start position:0% prototypical implementation that was 00:18:17.120 --> 00:18:19.270 align:start position:0% prototypical implementation that was done<00:18:17.330> which<00:18:17.840> was<00:18:17.990> not<00:18:18.230> highly<00:18:18.470> optimized<00:18:19.040> I 00:18:19.270 --> 00:18:19.280 align:start position:0% done which was not highly optimized I 00:18:19.280 --> 00:18:20.860 align:start position:0% done which was not highly optimized I mean<00:18:19.430> there<00:18:19.640> could<00:18:19.670> have<00:18:19.910> been<00:18:20.030> for<00:18:20.780> example 00:18:20.860 --> 00:18:20.870 align:start position:0% mean there could have been for example 00:18:20.870 --> 00:18:22.660 align:start position:0% mean there could have been for example we<00:18:21.230> could<00:18:21.440> have<00:18:21.500> used<00:18:21.830> Peters<00:18:22.490> and 00:18:22.660 --> 00:18:22.670 align:start position:0% we could have used Peters and 00:18:22.670 --> 00:18:25.930 align:start position:0% we could have used Peters and commitments<00:18:23.210> instead<00:18:23.600> of<00:18:23.750> sha<00:18:24.190> and<00:18:25.190> slight 00:18:25.930 --> 00:18:25.940 align:start position:0% commitments instead of sha and slight 00:18:25.940 --> 00:18:29.350 align:start position:0% commitments instead of sha and slight details<00:18:26.570> that<00:18:26.780> will<00:18:26.870> bring<00:18:27.140> down<00:18:27.380> the<00:18:28.220> cost<00:18:29.059> of 00:18:29.350 --> 00:18:29.360 align:start position:0% details that will bring down the cost of 00:18:29.360 --> 00:18:32.230 align:start position:0% details that will bring down the cost of proving<00:18:29.990> for<00:18:30.260> example<00:18:30.800> and<00:18:31.010> the<00:18:31.940> verification 00:18:32.230 --> 00:18:32.240 align:start position:0% proving for example and the verification 00:18:32.240 --> 00:18:35.440 align:start position:0% proving for example and the verification cost<00:18:32.900> will<00:18:33.260> probably<00:18:33.650> be<00:18:34.040> around<00:18:34.190> about<00:18:34.580> 300<00:18:34.970> K 00:18:35.440 --> 00:18:35.450 align:start position:0% cost will probably be around about 300 K 00:18:35.450 --> 00:18:36.310 align:start position:0% cost will probably be around about 300 K which<00:18:35.660> is<00:18:35.690> not<00:18:35.960> too<00:18:36.080> bad 00:18:36.310 --> 00:18:36.320 align:start position:0% which is not too bad 00:18:36.320 --> 00:18:39.640 align:start position:0% which is not too bad after<00:18:36.710> Kista<00:18:37.220> moon<00:18:37.429> half<00:18:37.970> for<00:18:38.350> improving<00:18:39.350> time 00:18:39.640 --> 00:18:39.650 align:start position:0% after Kista moon half for improving time 00:18:39.650 --> 00:18:43.150 align:start position:0% after Kista moon half for improving time in<00:18:39.980> that<00:18:40.490> an<00:18:40.760> optimized<00:18:41.240> version<00:18:41.929> was<00:18:42.860> two<00:18:43.070> and 00:18:43.150 --> 00:18:43.160 align:start position:0% in that an optimized version was two and 00:18:43.160 --> 00:18:45.400 align:start position:0% in that an optimized version was two and a<00:18:43.250> half<00:18:43.400> minutes<00:18:43.850> so<00:18:43.940> totally<00:18:44.510> practical<00:18:45.140> and 00:18:45.400 --> 00:18:45.410 align:start position:0% a half minutes so totally practical and 00:18:45.410 --> 00:18:47.799 align:start position:0% a half minutes so totally practical and auto<00:18:45.830> consumer<00:18:46.400> that<00:18:46.550> father's<00:18:47.150> very<00:18:47.540> happy 00:18:47.799 --> 00:18:47.809 align:start position:0% auto consumer that father's very happy 00:18:47.809 --> 00:18:53.470 align:start position:0% auto consumer that father's very happy really<00:18:48.200> initially<00:18:48.950> right<00:18:50.650> okay<00:18:51.850> I'm<00:18:52.850> also 00:18:53.470 --> 00:18:53.480 align:start position:0% really initially right okay I'm also 00:18:53.480 --> 00:18:56.380 align:start position:0% really initially right okay I'm also gonna<00:18:53.780> quickly<00:18:54.200> go<00:18:54.559> through<00:18:54.590> another<00:18:55.460> project 00:18:56.380 --> 00:18:56.390 align:start position:0% gonna quickly go through another project 00:18:56.390 --> 00:18:59.200 align:start position:0% gonna quickly go through another project that<00:18:56.870> I<00:18:57.290> personally<00:18:57.740> worked<00:18:58.130> on<00:18:58.340> as<00:18:58.610> part<00:18:59.090> of 00:18:59.200 --> 00:18:59.210 align:start position:0% that I personally worked on as part of 00:18:59.210 --> 00:19:01.810 align:start position:0% that I personally worked on as part of the<00:18:59.390> project<00:18:59.600> at<00:19:00.110> to<00:19:00.740> Berlin<00:19:01.130> in<00:19:01.370> this<00:19:01.700> is 00:19:01.810 --> 00:19:01.820 align:start position:0% the project at to Berlin in this is 00:19:01.820 --> 00:19:04.450 align:start position:0% the project at to Berlin in this is Socrates<00:19:02.000> as<00:19:02.330> well<00:19:02.540> and<00:19:02.780> the<00:19:03.230> problem<00:19:03.260> is<00:19:03.860> that 00:19:04.450 --> 00:19:04.460 align:start position:0% Socrates as well and the problem is that 00:19:04.460 --> 00:19:07.030 align:start position:0% Socrates as well and the problem is that currently<00:19:05.240> the<00:19:05.690> energy<00:19:06.230> system<00:19:06.679> and<00:19:06.890> East 00:19:07.030 --> 00:19:07.040 align:start position:0% currently the energy system and East 00:19:07.040 --> 00:19:09.160 align:start position:0% currently the energy system and East Germany<00:19:07.340> and<00:19:07.760> most<00:19:08.030> other<00:19:08.300> countries<00:19:08.540> kind<00:19:09.110> of 00:19:09.160 --> 00:19:09.170 align:start position:0% Germany and most other countries kind of 00:19:09.170 --> 00:19:11.380 align:start position:0% Germany and most other countries kind of works<00:19:09.320> like<00:19:09.410> this<00:19:09.850> households<00:19:10.850> are<00:19:11.000> in<00:19:11.270> the 00:19:11.380 --> 00:19:11.390 align:start position:0% works like this households are in the 00:19:11.390 --> 00:19:13.419 align:start position:0% works like this households are in the network<00:19:11.570> and<00:19:11.960> there's<00:19:12.140> a<00:19:12.200> electric<00:19:12.890> utility 00:19:13.419 --> 00:19:13.429 align:start position:0% network and there's a electric utility 00:19:13.429 --> 00:19:15.370 align:start position:0% network and there's a electric utility right<00:19:13.640> and<00:19:13.970> some<00:19:14.240> households<00:19:14.809> they<00:19:15.110> produce 00:19:15.370 --> 00:19:15.380 align:start position:0% right and some households they produce 00:19:15.380 --> 00:19:17.350 align:start position:0% right and some households they produce more<00:19:15.860> energy<00:19:16.100> than<00:19:16.400> it<00:19:16.700> consumes<00:19:16.730> because 00:19:17.350 --> 00:19:17.360 align:start position:0% more energy than it consumes because 00:19:17.360 --> 00:19:19.180 align:start position:0% more energy than it consumes because they<00:19:17.540> have<00:19:17.720> solar<00:19:18.020> solar<00:19:18.380> panels<00:19:18.920> on<00:19:19.070> their 00:19:19.180 --> 00:19:19.190 align:start position:0% they have solar solar panels on their 00:19:19.190 --> 00:19:21.340 align:start position:0% they have solar solar panels on their roofs<00:19:19.370> for<00:19:19.520> examples<00:19:19.970> and<00:19:20.150> others<00:19:20.750> consume 00:19:21.340 --> 00:19:21.350 align:start position:0% roofs for examples and others consume 00:19:21.350 --> 00:19:29.690 align:start position:0% roofs for examples and others consume more<00:19:22.630> these 00:19:29.690 --> 00:19:29.700 align:start position:0% 00:19:29.700 --> 00:19:32.240 align:start position:0% and<00:19:30.030> the<00:19:30.600> other<00:19:30.780> households<00:19:31.350> they<00:19:31.559> consume 00:19:32.240 --> 00:19:32.250 align:start position:0% and the other households they consume 00:19:32.250 --> 00:19:34.159 align:start position:0% and the other households they consume more<00:19:32.429> Dana<00:19:32.700> prefers<00:19:33.120> buts<00:19:33.570> problem<00:19:33.990> is 00:19:34.159 --> 00:19:34.169 align:start position:0% more Dana prefers buts problem is 00:19:34.169 --> 00:19:36.620 align:start position:0% more Dana prefers buts problem is everything<00:19:35.160> goes<00:19:35.400> through<00:19:35.760> that<00:19:36.179> electric 00:19:36.620 --> 00:19:36.630 align:start position:0% everything goes through that electric 00:19:36.630 --> 00:19:38.330 align:start position:0% everything goes through that electric utility<00:19:37.200> and<00:19:37.380> I'm<00:19:37.440> forced<00:19:37.770> to<00:19:37.830> make<00:19:37.890> a<00:19:38.039> profit 00:19:38.330 --> 00:19:38.340 align:start position:0% utility and I'm forced to make a profit 00:19:38.340 --> 00:19:40.190 align:start position:0% utility and I'm forced to make a profit from<00:19:38.610> the<00:19:38.820> right<00:19:39.030> they<00:19:39.240> make<00:19:39.419> a<00:19:39.450> market<00:19:39.870> they 00:19:40.190 --> 00:19:40.200 align:start position:0% from the right they make a market they 00:19:40.200 --> 00:19:43.700 align:start position:0% from the right they make a market they give<00:19:40.410> me<00:19:40.530> a<00:19:40.650> small<00:19:41.120> to<00:19:42.120> give<00:19:42.299> you<00:19:42.450> little<00:19:43.380> money 00:19:43.700 --> 00:19:43.710 align:start position:0% give me a small to give you little money 00:19:43.710 --> 00:19:45.590 align:start position:0% give me a small to give you little money for<00:19:44.039> the<00:19:44.160> energy<00:19:44.490> they<00:19:44.520> buy<00:19:44.820> and<00:19:45.030> they<00:19:45.179> resell 00:19:45.590 --> 00:19:45.600 align:start position:0% for the energy they buy and they resell 00:19:45.600 --> 00:19:47.060 align:start position:0% for the energy they buy and they resell it<00:19:45.750> at<00:19:45.870> a<00:19:45.900> higher<00:19:46.110> price<00:19:46.140> and<00:19:46.679> then<00:19:46.860> there's 00:19:47.060 --> 00:19:47.070 align:start position:0% it at a higher price and then there's 00:19:47.070 --> 00:19:48.950 align:start position:0% it at a higher price and then there's tax<00:19:47.340> effects<00:19:47.730> and<00:19:47.910> other<00:19:48.000> tax<00:19:48.390> white<00:19:48.600> could<00:19:48.840> be 00:19:48.950 --> 00:19:48.960 align:start position:0% tax effects and other tax white could be 00:19:48.960 --> 00:19:50.900 align:start position:0% tax effects and other tax white could be beneficial<00:19:49.470> to<00:19:49.679> not<00:19:49.919> do<00:19:50.160> it<00:19:50.190> that<00:19:50.460> way 00:19:50.900 --> 00:19:50.910 align:start position:0% beneficial to not do it that way 00:19:50.910 --> 00:19:52.700 align:start position:0% beneficial to not do it that way so<00:19:51.210> what<00:19:51.419> we<00:19:51.570> propose<00:19:51.960> how<00:19:52.230> you<00:19:52.289> would<00:19:52.559> do<00:19:52.679> it 00:19:52.700 --> 00:19:52.710 align:start position:0% so what we propose how you would do it 00:19:52.710 --> 00:19:55.610 align:start position:0% so what we propose how you would do it we<00:19:53.220> try<00:19:53.429> to<00:19:53.490> do<00:19:53.820> as<00:19:54.000> much<00:19:54.210> in<00:19:54.539> turn<00:19:54.929> me<00:19:55.200> in<00:19:55.440> the 00:19:55.610 --> 00:19:55.620 align:start position:0% we try to do as much in turn me in the 00:19:55.620 --> 00:19:57.980 align:start position:0% we try to do as much in turn me in the network<00:19:56.059> but<00:19:57.059> we<00:19:57.090> do<00:19:57.419> not<00:19:57.600> do<00:19:57.809> it 00:19:57.980 --> 00:19:57.990 align:start position:0% network but we do not do it 00:19:57.990 --> 00:20:00.080 align:start position:0% network but we do not do it one<00:19:58.230> market<00:19:58.679> base<00:19:58.860> where<00:19:59.159> you<00:19:59.190> fit<00:19:59.490> it<00:19:59.640> and<00:19:59.850> ask 00:20:00.080 --> 00:20:00.090 align:start position:0% one market base where you fit it and ask 00:20:00.090 --> 00:20:01.850 align:start position:0% one market base where you fit it and ask which<00:20:00.419> is<00:20:00.450> super<00:20:00.809> expensive<00:20:00.990> and<00:20:01.409> has<00:20:01.620> many 00:20:01.850 --> 00:20:01.860 align:start position:0% which is super expensive and has many 00:20:01.860 --> 00:20:04.399 align:start position:0% which is super expensive and has many problems<00:20:02.130> but<00:20:02.700> we<00:20:02.880> are<00:20:03.000> on<00:20:03.120> the<00:20:03.150> same<00:20:03.539> we<00:20:04.200> look 00:20:04.399 --> 00:20:04.409 align:start position:0% problems but we are on the same we look 00:20:04.409 --> 00:20:07.130 align:start position:0% problems but we are on the same we look back<00:20:04.710> in<00:20:05.039> time<00:20:05.070> after<00:20:05.880> everybody<00:20:06.419> produce<00:20:06.870> or 00:20:07.130 --> 00:20:07.140 align:start position:0% back in time after everybody produce or 00:20:07.140 --> 00:20:10.610 align:start position:0% back in time after everybody produce or consume<00:20:07.169> the<00:20:07.799> energy<00:20:07.830> and<00:20:08.610> then<00:20:09.230> we<00:20:10.230> basically 00:20:10.610 --> 00:20:10.620 align:start position:0% consume the energy and then we basically 00:20:10.620 --> 00:20:13.640 align:start position:0% consume the energy and then we basically make<00:20:11.159> the<00:20:11.340> matching<00:20:11.850> and<00:20:12.150> match<00:20:12.929> the<00:20:13.289> produced 00:20:13.640 --> 00:20:13.650 align:start position:0% make the matching and match the produced 00:20:13.650 --> 00:20:15.919 align:start position:0% make the matching and match the produced energy<00:20:14.190> by<00:20:14.520> households<00:20:15.150> with<00:20:15.330> consumed 00:20:15.919 --> 00:20:15.929 align:start position:0% energy by households with consumed 00:20:15.929 --> 00:20:17.510 align:start position:0% energy by households with consumed energy<00:20:16.140> by<00:20:16.470> household<00:20:16.860> and<00:20:17.159> kind<00:20:17.400> of 00:20:17.510 --> 00:20:17.520 align:start position:0% energy by household and kind of 00:20:17.520 --> 00:20:20.180 align:start position:0% energy by household and kind of minimized<00:20:18.000> the<00:20:18.659> amount<00:20:18.690> of<00:20:19.049> energy<00:20:19.500> that<00:20:19.740> ever 00:20:20.180 --> 00:20:20.190 align:start position:0% minimized the amount of energy that ever 00:20:20.190 --> 00:20:22.909 align:start position:0% minimized the amount of energy that ever goes<00:20:20.520> through<00:20:21.059> that<00:20:21.210> electric<00:20:21.750> utility<00:20:22.500> and 00:20:22.909 --> 00:20:22.919 align:start position:0% goes through that electric utility and 00:20:22.919 --> 00:20:25.720 align:start position:0% goes through that electric utility and that<00:20:22.950> takes<00:20:23.460> away<00:20:23.789> their<00:20:24.360> their<00:20:24.809> profit<00:20:25.320> and 00:20:25.720 --> 00:20:25.730 align:start position:0% that takes away their their profit and 00:20:25.730 --> 00:20:28.460 align:start position:0% that takes away their their profit and makes<00:20:26.730> it<00:20:26.909> more<00:20:27.090> profitable<00:20:27.630> for<00:20:27.809> households 00:20:28.460 --> 00:20:28.470 align:start position:0% makes it more profitable for households 00:20:28.470 --> 00:20:31.520 align:start position:0% makes it more profitable for households to<00:20:28.890> have<00:20:29.130> solar<00:20:29.600> panels<00:20:30.600> installed<00:20:31.110> because<00:20:31.380> a 00:20:31.520 --> 00:20:31.530 align:start position:0% to have solar panels installed because a 00:20:31.530 --> 00:20:33.380 align:start position:0% to have solar panels installed because a big<00:20:31.770> issue<00:20:31.950> that<00:20:32.130> in<00:20:32.429> many<00:20:32.610> cases<00:20:32.880> is 00:20:33.380 --> 00:20:33.390 align:start position:0% big issue that in many cases is 00:20:33.390 --> 00:20:35.960 align:start position:0% big issue that in many cases is unprofitable<00:20:33.750> it's<00:20:34.590> kind<00:20:34.830> of<00:20:34.919> bad<00:20:35.130> for<00:20:35.159> moving 00:20:35.960 --> 00:20:35.970 align:start position:0% unprofitable it's kind of bad for moving 00:20:35.970 --> 00:20:39.289 align:start position:0% unprofitable it's kind of bad for moving on<00:20:36.150> to<00:20:36.360> radial<00:20:36.750> directions<00:20:37.010> run<00:20:38.010> on<00:20:38.190> it<00:20:38.309> but 00:20:39.289 --> 00:20:39.299 align:start position:0% on to radial directions run on it but 00:20:39.299 --> 00:20:43.070 align:start position:0% on to radial directions run on it but meaning<00:20:39.600> okay<00:20:40.429> so<00:20:41.429> that's<00:20:41.669> the<00:20:41.909> idea<00:20:42.240> and<00:20:42.480> the 00:20:43.070 --> 00:20:43.080 align:start position:0% meaning okay so that's the idea and the 00:20:43.080 --> 00:20:45.380 align:start position:0% meaning okay so that's the idea and the core<00:20:43.320> problem<00:20:43.710> is<00:20:43.860> we<00:20:44.340> do<00:20:44.490> not<00:20:44.610> trust<00:20:44.880> the 00:20:45.380 --> 00:20:45.390 align:start position:0% core problem is we do not trust the 00:20:45.390 --> 00:20:48.529 align:start position:0% core problem is we do not trust the utility<00:20:46.140> with<00:20:46.710> doing<00:20:47.280> this<00:20:47.539> allocation 00:20:48.529 --> 00:20:48.539 align:start position:0% utility with doing this allocation 00:20:48.539 --> 00:20:50.720 align:start position:0% utility with doing this allocation algorithm<00:20:49.110> this<00:20:49.289> matching<00:20:49.740> right<00:20:49.890> so<00:20:50.400> we<00:20:50.490> want 00:20:50.720 --> 00:20:50.730 align:start position:0% algorithm this matching right so we want 00:20:50.730 --> 00:20:52.310 align:start position:0% algorithm this matching right so we want this<00:20:50.880> to<00:20:51.090> be<00:20:51.120> in<00:20:51.330> a<00:20:51.419> blockchain<00:20:51.630> because<00:20:52.140> then 00:20:52.310 --> 00:20:52.320 align:start position:0% this to be in a blockchain because then 00:20:52.320 --> 00:20:54.620 align:start position:0% this to be in a blockchain because then is<00:20:52.440> untrusted<00:20:53.039> but<00:20:53.580> that<00:20:53.789> means<00:20:53.970> hustles 00:20:54.620 --> 00:20:54.630 align:start position:0% is untrusted but that means hustles 00:20:54.630 --> 00:20:56.450 align:start position:0% is untrusted but that means hustles publish<00:20:55.110> their<00:20:55.350> energy<00:20:55.710> consumption<00:20:56.130> data 00:20:56.450 --> 00:20:56.460 align:start position:0% publish their energy consumption data 00:20:56.460 --> 00:20:58.370 align:start position:0% publish their energy consumption data and<00:20:56.789> the<00:20:57.240> blockchain<00:20:57.510> that<00:20:57.960> computes<00:20:58.289> to 00:20:58.370 --> 00:20:58.380 align:start position:0% and the blockchain that computes to 00:20:58.380 --> 00:21:02.120 align:start position:0% and the blockchain that computes to magic<00:20:58.830> but<00:20:59.360> publishing<00:21:00.360> that<00:21:00.510> beta<00:21:00.750> is<00:21:01.140> really 00:21:02.120 --> 00:21:02.130 align:start position:0% magic but publishing that beta is really 00:21:02.130 --> 00:21:04.669 align:start position:0% magic but publishing that beta is really bad<00:21:02.370> right<00:21:03.059> because<00:21:03.659> then<00:21:03.900> everybody<00:21:04.320> can<00:21:04.500> see 00:21:04.669 --> 00:21:04.679 align:start position:0% bad right because then everybody can see 00:21:04.679 --> 00:21:07.399 align:start position:0% bad right because then everybody can see how<00:21:05.070> much<00:21:05.250> energy<00:21:05.429> is<00:21:05.760> could<00:21:06.030> compute<00:21:06.659> used<00:21:07.260> by 00:21:07.399 --> 00:21:07.409 align:start position:0% how much energy is could compute used by 00:21:07.409 --> 00:21:09.799 align:start position:0% how much energy is could compute used by everybody<00:21:07.890> or<00:21:08.100> produced<00:21:08.880> by<00:21:08.970> anybody<00:21:09.360> this<00:21:09.630> is 00:21:09.799 --> 00:21:09.809 align:start position:0% everybody or produced by anybody this is 00:21:09.809 --> 00:21:12.169 align:start position:0% everybody or produced by anybody this is highly<00:21:10.140> sensitive<00:21:10.350> data<00:21:10.890> so<00:21:11.429> we<00:21:11.640> cannot<00:21:11.940> do 00:21:12.169 --> 00:21:12.179 align:start position:0% highly sensitive data so we cannot do 00:21:12.179 --> 00:21:14.210 align:start position:0% highly sensitive data so we cannot do that<00:21:12.419> that's<00:21:12.900> why<00:21:13.289> would<00:21:13.500> introduced<00:21:13.980> a 00:21:14.210 --> 00:21:14.220 align:start position:0% that that's why would introduced a 00:21:14.220 --> 00:21:15.919 align:start position:0% that that's why would introduced a Socrates<00:21:14.760> base<00:21:15.059> TK<00:21:15.480> snark 00:21:15.919 --> 00:21:15.929 align:start position:0% Socrates base TK snark 00:21:15.929 --> 00:21:18.860 align:start position:0% Socrates base TK snark then<00:21:16.350> does<00:21:16.620> that<00:21:17.130> matching<00:21:17.880> algorithm<00:21:18.659> and 00:21:18.860 --> 00:21:18.870 align:start position:0% then does that matching algorithm and 00:21:18.870 --> 00:21:22.850 align:start position:0% then does that matching algorithm and the<00:21:19.169> blockchain<00:21:19.409> only<00:21:19.950> verifies<00:21:20.370> that<00:21:20.400> match 00:21:22.850 --> 00:21:22.860 align:start position:0% the blockchain only verifies that match 00:21:22.860 --> 00:21:25.899 align:start position:0% the blockchain only verifies that match in<00:21:23.250> line<00:21:23.549> with<00:21:23.879> some<00:21:24.389> specific<00:21:25.049> requirements 00:21:25.899 --> 00:21:25.909 align:start position:0% in line with some specific requirements 00:21:25.909 --> 00:21:29.119 align:start position:0% in line with some specific requirements it's<00:21:26.909> fair<00:21:27.149> and<00:21:27.720> correct<00:21:28.259> the<00:21:28.500> same<00:21:28.740> amount 00:21:29.119 --> 00:21:29.129 align:start position:0% it's fair and correct the same amount 00:21:29.129 --> 00:21:32.149 align:start position:0% it's fair and correct the same amount like<00:21:30.120> yeah<00:21:30.419> the<00:21:30.629> amounts<00:21:31.019> work<00:21:31.320> out<00:21:31.559> it<00:21:31.889> puts 00:21:32.149 --> 00:21:32.159 align:start position:0% like yeah the amounts work out it puts 00:21:32.159 --> 00:21:34.610 align:start position:0% like yeah the amounts work out it puts up<00:21:32.340> with<00:21:32.580> or<00:21:32.850> equal<00:21:33.210> all<00:21:34.019> that<00:21:34.200> kind<00:21:34.440> of<00:21:34.500> stuff 00:21:34.610 --> 00:21:34.620 align:start position:0% up with or equal all that kind of stuff 00:21:34.620 --> 00:21:35.869 align:start position:0% up with or equal all that kind of stuff okay 00:21:35.869 --> 00:21:35.879 align:start position:0% okay 00:21:35.879 --> 00:21:38.389 align:start position:0% okay sneak<00:21:36.840> peek<00:21:37.110> in<00:21:37.289> the<00:21:37.379> future<00:21:37.710> in<00:21:37.980> one<00:21:38.220> minute 00:21:38.389 --> 00:21:38.399 align:start position:0% sneak peek in the future in one minute 00:21:38.399 --> 00:21:41.269 align:start position:0% sneak peek in the future in one minute so<00:21:39.299> we've<00:21:39.960> been<00:21:40.110> moving<00:21:40.320> very<00:21:40.529> fast<00:21:40.950> we've 00:21:41.269 --> 00:21:41.279 align:start position:0% so we've been moving very fast we've 00:21:41.279 --> 00:21:42.889 align:start position:0% so we've been moving very fast we've been<00:21:41.429> breaking<00:21:41.700> things<00:21:42.179> we've<00:21:42.389> been<00:21:42.600> changing 00:21:42.889 --> 00:21:42.899 align:start position:0% been breaking things we've been changing 00:21:42.899 --> 00:21:44.720 align:start position:0% been breaking things we've been changing specs<00:21:43.470> implementation<00:21:44.340> has<00:21:44.549> been 00:21:44.720 --> 00:21:44.730 align:start position:0% specs implementation has been 00:21:44.730 --> 00:21:47.990 align:start position:0% specs implementation has been progressing<00:21:45.419> rapidly<00:21:45.779> and<00:21:46.379> now<00:21:46.980> I<00:21:47.009> think<00:21:47.340> we 00:21:47.990 --> 00:21:48.000 align:start position:0% progressing rapidly and now I think we 00:21:48.000 --> 00:21:49.940 align:start position:0% progressing rapidly and now I think we need<00:21:48.029> to<00:21:48.419> slow<00:21:48.659> that<00:21:48.960> down<00:21:49.019> a<00:21:49.320> little<00:21:49.409> bit 00:21:49.940 --> 00:21:49.950 align:start position:0% need to slow that down a little bit 00:21:49.950 --> 00:21:52.970 align:start position:0% need to slow that down a little bit we<00:21:50.399> need<00:21:50.580> to<00:21:50.730> come<00:21:51.360> to<00:21:51.659> version<00:21:51.929> that<00:21:52.320> staples 00:21:52.970 --> 00:21:52.980 align:start position:0% we need to come to version that staples 00:21:52.980 --> 00:21:54.740 align:start position:0% we need to come to version that staples and<00:21:53.159> users<00:21:53.519> can<00:21:53.820> actually<00:21:54.029> rely<00:21:54.720> on 00:21:54.740 --> 00:21:54.750 align:start position:0% and users can actually rely on 00:21:54.750 --> 00:21:56.869 align:start position:0% and users can actually rely on subversion<00:21:55.200> start<00:21:56.129> building<00:21:56.549> with<00:21:56.700> it 00:21:56.869 --> 00:21:56.879 align:start position:0% subversion start building with it 00:21:56.879 --> 00:21:59.360 align:start position:0% subversion start building with it without<00:21:57.419> us<00:21:57.929> breaking<00:21:58.470> it<00:21:58.620> again<00:21:58.950> and<00:21:59.129> again 00:21:59.360 --> 00:21:59.370 align:start position:0% without us breaking it again and again 00:21:59.370 --> 00:22:01.909 align:start position:0% without us breaking it again and again through<00:21:59.669> disruptive<00:22:00.659> changes<00:22:01.139> and<00:22:01.500> it<00:22:01.740> would 00:22:01.909 --> 00:22:01.919 align:start position:0% through disruptive changes and it would 00:22:01.919 --> 00:22:03.259 align:start position:0% through disruptive changes and it would also<00:22:02.100> allow<00:22:02.429> us<00:22:02.639> to<00:22:02.820> do<00:22:02.970> further 00:22:03.259 --> 00:22:03.269 align:start position:0% also allow us to do further 00:22:03.269 --> 00:22:05.600 align:start position:0% also allow us to do further optimizations<00:22:04.049> to<00:22:04.139> code<00:22:04.529> base<00:22:04.740> and<00:22:05.070> crucially 00:22:05.600 --> 00:22:05.610 align:start position:0% optimizations to code base and crucially 00:22:05.610 --> 00:22:06.740 align:start position:0% optimizations to code base and crucially for<00:22:05.850> people<00:22:06.120> that<00:22:06.179> want<00:22:06.389> to<00:22:06.450> use<00:22:06.570> in 00:22:06.740 --> 00:22:06.750 align:start position:0% for people that want to use in 00:22:06.750 --> 00:22:08.990 align:start position:0% for people that want to use in production<00:22:07.049> get<00:22:07.860> some<00:22:08.129> audit<00:22:08.639> get 00:22:08.990 --> 00:22:09.000 align:start position:0% production get some audit get 00:22:09.000 --> 00:22:11.509 align:start position:0% production get some audit get potentially<00:22:09.629> some<00:22:09.899> form<00:22:10.320> of<00:22:10.409> verification<00:22:10.529> on 00:22:11.509 --> 00:22:11.519 align:start position:0% potentially some form of verification on 00:22:11.519 --> 00:22:13.850 align:start position:0% potentially some form of verification on the<00:22:11.669> optimization<00:22:12.090> steps<00:22:12.750> we<00:22:12.960> do<00:22:13.139> and<00:22:13.470> stuff 00:22:13.850 --> 00:22:13.860 align:start position:0% the optimization steps we do and stuff 00:22:13.860 --> 00:22:16.490 align:start position:0% the optimization steps we do and stuff like<00:22:14.039> that<00:22:14.279> so<00:22:14.820> that's<00:22:14.970> our<00:22:15.240> plan<00:22:15.480> for<00:22:16.110> the 00:22:16.490 --> 00:22:16.500 align:start position:0% like that so that's our plan for the 00:22:16.500 --> 00:22:18.350 align:start position:0% like that so that's our plan for the next<00:22:16.529> year<00:22:16.799> to<00:22:16.950> slow<00:22:17.490> down<00:22:17.700> with<00:22:17.909> it<00:22:18.059> with<00:22:18.269> the 00:22:18.350 --> 00:22:18.360 align:start position:0% next year to slow down with it with the 00:22:18.360 --> 00:22:20.840 align:start position:0% next year to slow down with it with the breaking<00:22:18.779> changes<00:22:19.440> and<00:22:19.649> to<00:22:20.129> move<00:22:20.309> to<00:22:20.580> a<00:22:20.610> more 00:22:20.840 --> 00:22:20.850 align:start position:0% breaking changes and to move to a more 00:22:20.850 --> 00:22:24.379 align:start position:0% breaking changes and to move to a more stable<00:22:21.539> release<00:22:22.259> hopefully<00:22:23.149> if<00:22:24.149> you're 00:22:24.379 --> 00:22:24.389 align:start position:0% stable release hopefully if you're 00:22:24.389 --> 00:22:25.879 align:start position:0% stable release hopefully if you're interested<00:22:24.929> in<00:22:24.990> the<00:22:25.080> rest<00:22:25.289> another<00:22:25.620> than 00:22:25.879 --> 00:22:25.889 align:start position:0% interested in the rest another than 00:22:25.889 --> 00:22:27.259 align:start position:0% interested in the rest another than programming<00:22:26.159> language<00:22:26.759> and<00:22:26.909> state<00:22:27.149> of 00:22:27.259 --> 00:22:27.269 align:start position:0% programming language and state of 00:22:27.269 --> 00:22:29.840 align:start position:0% programming language and state of geography<00:22:28.169> we're<00:22:28.769> looking<00:22:29.159> to<00:22:29.429> throw<00:22:29.669> the 00:22:29.840 --> 00:22:29.850 align:start position:0% geography we're looking to throw the 00:22:29.850 --> 00:22:32.389 align:start position:0% geography we're looking to throw the team<00:22:30.059> so<00:22:30.509> please<00:22:31.110> get<00:22:31.409> in<00:22:31.529> touch<00:22:31.559> and<00:22:31.980> thank 00:22:32.389 --> 00:22:32.399 align:start position:0% team so please get in touch and thank 00:22:32.399 --> 00:22:37.850 align:start position:0% team so please get in touch and thank you<00:22:32.549> very<00:22:32.580> much<00:22:32.940> for<00:22:33.269> your<00:22:33.389> attention 00:22:37.850 --> 00:22:37.860 align:start position:0% 00:22:37.860 --> 00:22:44.430 align:start position:0% [Applause]