WEBVTT Kind: captions Language: en 00:00:11.309 --> 00:00:16.109 align:start position:0% thank<00:00:12.309> you<00:00:12.430> good<00:00:12.910> morning<00:00:13.470> so<00:00:15.029> it's<00:00:16.029> all<00:00:16.090> my 00:00:16.109 --> 00:00:16.119 align:start position:0% thank you good morning so it's all my 00:00:16.119 --> 00:00:18.329 align:start position:0% thank you good morning so it's all my inner<00:00:16.359> body<00:00:16.539> smart<00:00:16.750> contracts<00:00:17.260> at<00:00:17.710> 15<00:00:18.039> minutes 00:00:18.329 --> 00:00:18.339 align:start position:0% inner body smart contracts at 15 minutes 00:00:18.339 --> 00:00:21.689 align:start position:0% inner body smart contracts at 15 minutes it's<00:00:18.789> a<00:00:18.820> pretty<00:00:18.999> deep<00:00:19.179> topic<00:00:20.429> this<00:00:21.429> is<00:00:21.579> also 00:00:21.689 --> 00:00:21.699 align:start position:0% it's a pretty deep topic this is also 00:00:21.699 --> 00:00:23.429 align:start position:0% it's a pretty deep topic this is also known<00:00:22.029> as<00:00:22.179> scriptlets<00:00:22.720> if<00:00:23.079> my<00:00:23.230> smart 00:00:23.429 --> 00:00:23.439 align:start position:0% known as scriptlets if my smart 00:00:23.439 --> 00:00:25.589 align:start position:0% known as scriptlets if my smart contracts<00:00:23.859> is<00:00:23.980> a<00:00:24.099> nice<00:00:24.310> marketing<00:00:24.789> term<00:00:25.569> for 00:00:25.589 --> 00:00:25.599 align:start position:0% contracts is a nice marketing term for 00:00:25.599 --> 00:00:29.249 align:start position:0% contracts is a nice marketing term for people<00:00:25.929> that<00:00:26.140> aren't<00:00:26.349> very<00:00:27.220> technical<00:00:28.259> but 00:00:29.249 --> 00:00:29.259 align:start position:0% people that aren't very technical but 00:00:29.259 --> 00:00:30.839 align:start position:0% people that aren't very technical but let's<00:00:29.619> talk<00:00:29.739> about<00:00:29.859> some<00:00:30.130> background<00:00:30.489> first 00:00:30.839 --> 00:00:30.849 align:start position:0% let's talk about some background first 00:00:30.849 --> 00:00:33.060 align:start position:0% let's talk about some background first so<00:00:31.059> in<00:00:31.239> Azure<00:00:31.479> Microsoft's<00:00:32.410> cloud<00:00:32.500> platform 00:00:33.060 --> 00:00:33.070 align:start position:0% so in Azure Microsoft's cloud platform 00:00:33.070 --> 00:00:34.680 align:start position:0% so in Azure Microsoft's cloud platform we<00:00:33.190> have<00:00:33.309> some<00:00:33.489> pillars<00:00:34.060> that<00:00:34.210> we've<00:00:34.480> built 00:00:34.680 --> 00:00:34.690 align:start position:0% we have some pillars that we've built 00:00:34.690 --> 00:00:38.850 align:start position:0% we have some pillars that we've built upon<00:00:35.700> to<00:00:36.700> build<00:00:36.910> this<00:00:37.720> platform<00:00:37.960> the<00:00:38.500> first<00:00:38.710> of 00:00:38.850 --> 00:00:38.860 align:start position:0% upon to build this platform the first of 00:00:38.860 --> 00:00:40.950 align:start position:0% upon to build this platform the first of which<00:00:38.920> is<00:00:38.980> identity<00:00:39.550> Azure<00:00:40.510> Active<00:00:40.660> Directory 00:00:40.950 --> 00:00:40.960 align:start position:0% which is identity Azure Active Directory 00:00:40.960 --> 00:00:44.280 align:start position:0% which is identity Azure Active Directory is<00:00:41.320> an<00:00:41.470> open<00:00:41.770> federated<00:00:42.930> identity<00:00:43.930> system 00:00:44.280 --> 00:00:44.290 align:start position:0% is an open federated identity system 00:00:44.290 --> 00:00:47.880 align:start position:0% is an open federated identity system supports<00:00:45.160> open<00:00:45.580> authentication<00:00:46.530> it's<00:00:47.530> the 00:00:47.880 --> 00:00:47.890 align:start position:0% supports open authentication it's the 00:00:47.890 --> 00:00:50.730 align:start position:0% supports open authentication it's the dominant<00:00:48.810> identity<00:00:49.810> system<00:00:50.140> used<00:00:50.410> in<00:00:50.590> a 00:00:50.730 --> 00:00:50.740 align:start position:0% dominant identity system used in a 00:00:50.740 --> 00:00:53.370 align:start position:0% dominant identity system used in a crisis<00:00:51.070> today<00:00:51.510> it<00:00:52.510> allows<00:00:52.810> us<00:00:52.840> to<00:00:53.050> do<00:00:53.230> open 00:00:53.370 --> 00:00:53.380 align:start position:0% crisis today it allows us to do open 00:00:53.380 --> 00:00:56.730 align:start position:0% crisis today it allows us to do open Federation<00:00:54.360> second<00:00:55.360> is<00:00:55.450> a<00:00:55.480> secret<00:00:56.050> storage<00:00:56.320> or 00:00:56.730 --> 00:00:56.740 align:start position:0% Federation second is a secret storage or 00:00:56.740 --> 00:00:57.630 align:start position:0% Federation second is a secret storage or HSMs 00:00:57.630 --> 00:00:57.640 align:start position:0% HSMs 00:00:57.640 --> 00:01:00.390 align:start position:0% HSMs so<00:00:58.360> we<00:00:58.690> have<00:00:58.870> HSM<00:00:59.410> that<00:00:59.620> scale<00:00:59.890> and<00:01:00.220> so<00:01:00.310> they 00:01:00.390 --> 00:01:00.400 align:start position:0% so we have HSM that scale and so they 00:01:00.400 --> 00:01:02.760 align:start position:0% so we have HSM that scale and so they call<00:01:00.550> a<00:01:00.579> droid<00:01:00.850> key<00:01:01.030> vault<00:01:01.500> that<00:01:02.500> lets<00:01:02.650> you 00:01:02.760 --> 00:01:02.770 align:start position:0% call a droid key vault that lets you 00:01:02.770 --> 00:01:04.350 align:start position:0% call a droid key vault that lets you bring<00:01:02.920> your<00:01:03.070> own<00:01:03.160> keys<00:01:03.430> bringing<00:01:03.910> on<00:01:03.970> secrets 00:01:04.350 --> 00:01:04.360 align:start position:0% bring your own keys bringing on secrets 00:01:04.360 --> 00:01:07.410 align:start position:0% bring your own keys bringing on secrets and<00:01:04.570> things<00:01:04.689> like<00:01:04.780> that<00:01:06.030> recently<00:01:07.030> announced 00:01:07.410 --> 00:01:07.420 align:start position:0% and things like that recently announced 00:01:07.420 --> 00:01:09.690 align:start position:0% and things like that recently announced the<00:01:07.600> confidential<00:01:08.170> compute<00:01:08.590> platform<00:01:09.460> which 00:01:09.690 --> 00:01:09.700 align:start position:0% the confidential compute platform which 00:01:09.700 --> 00:01:13.830 align:start position:0% the confidential compute platform which is<00:01:10.109> essentially<00:01:11.109> describing<00:01:12.329> enclaves<00:01:13.329> at 00:01:13.830 --> 00:01:13.840 align:start position:0% is essentially describing enclaves at 00:01:13.840 --> 00:01:17.999 align:start position:0% is essentially describing enclaves at scale<00:01:14.560> in<00:01:14.859> the<00:01:15.189> cloud<00:01:15.429> both<00:01:15.999> SGX<00:01:16.869> and<00:01:17.049> what<00:01:17.920> we 00:01:17.999 --> 00:01:18.009 align:start position:0% scale in the cloud both SGX and what we 00:01:18.009 --> 00:01:20.730 align:start position:0% scale in the cloud both SGX and what we call<00:01:18.189> hypervisor<00:01:18.700> based<00:01:19.060> or<00:01:19.359> HSM<00:01:19.869> excuse<00:01:20.590> me 00:01:20.730 --> 00:01:20.740 align:start position:0% call hypervisor based or HSM excuse me 00:01:20.740 --> 00:01:24.330 align:start position:0% call hypervisor based or HSM excuse me VSM<00:01:21.600> based<00:01:22.600> on<00:01:22.960> claves<00:01:23.319> that<00:01:24.009> allow<00:01:24.159> you<00:01:24.219> to 00:01:24.330 --> 00:01:24.340 align:start position:0% VSM based on claves that allow you to 00:01:24.340 --> 00:01:27.870 align:start position:0% VSM based on claves that allow you to have<00:01:24.670> secure<00:01:25.389> confidential<00:01:26.039> compute<00:01:27.039> in<00:01:27.700> the 00:01:27.870 --> 00:01:27.880 align:start position:0% have secure confidential compute in the 00:01:27.880 --> 00:01:31.109 align:start position:0% have secure confidential compute in the cloud<00:01:28.119> and<00:01:28.659> then<00:01:29.319> lastly<00:01:29.740> hyper<00:01:30.189> scale<00:01:30.429> so<00:01:30.939> we 00:01:31.109 --> 00:01:31.119 align:start position:0% cloud and then lastly hyper scale so we 00:01:31.119 --> 00:01:33.149 align:start position:0% cloud and then lastly hyper scale so we have<00:01:31.240> a<00:01:31.270> platform<00:01:32.079> that<00:01:32.229> was<00:01:32.409> developed 00:01:33.149 --> 00:01:33.159 align:start position:0% have a platform that was developed 00:01:33.159 --> 00:01:37.050 align:start position:0% have a platform that was developed called<00:01:33.310> service<00:01:33.939> fabric<00:01:34.740> that<00:01:35.819> runs<00:01:36.819> things 00:01:37.050 --> 00:01:37.060 align:start position:0% called service fabric that runs things 00:01:37.060 --> 00:01:38.999 align:start position:0% called service fabric that runs things like<00:01:37.299> xbox<00:01:37.719> live<00:01:37.959> so<00:01:38.380> we<00:01:38.499> have<00:01:38.679> like<00:01:38.889> this 00:01:38.999 --> 00:01:39.009 align:start position:0% like xbox live so we have like this 00:01:39.009 --> 00:01:42.690 align:start position:0% like xbox live so we have like this massively<00:01:39.549> scalable<00:01:40.259> platform<00:01:41.369> that<00:01:42.369> we<00:01:42.520> can 00:01:42.690 --> 00:01:42.700 align:start position:0% massively scalable platform that we can 00:01:42.700 --> 00:01:45.599 align:start position:0% massively scalable platform that we can we<00:01:43.090> can<00:01:43.119> build<00:01:43.389> upon<00:01:43.979> so<00:01:44.979> let's<00:01:45.159> describe<00:01:45.369> what 00:01:45.599 --> 00:01:45.609 align:start position:0% we can build upon so let's describe what 00:01:45.609 --> 00:01:46.319 align:start position:0% we can build upon so let's describe what this<00:01:45.789> does 00:01:46.319 --> 00:01:46.329 align:start position:0% this does 00:01:46.329 --> 00:01:49.379 align:start position:0% this does so<00:01:47.100> ESC<00:01:48.100> is<00:01:48.159> the<00:01:48.279> acronym<00:01:48.429> reasoning<00:01:49.029> so<00:01:49.149> unify 00:01:49.379 --> 00:01:49.389 align:start position:0% so ESC is the acronym reasoning so unify 00:01:49.389 --> 00:01:52.830 align:start position:0% so ESC is the acronym reasoning so unify support<00:01:49.630> contracts<00:01:50.020> essentially<00:01:51.749> under<00:01:52.749> the 00:01:52.830 --> 00:01:52.840 align:start position:0% support contracts essentially under the 00:01:52.840 --> 00:01:54.840 align:start position:0% support contracts essentially under the covers<00:01:53.200> we<00:01:53.350> call<00:01:53.529> the<00:01:53.740> the<00:01:54.009> ESC<00:01:54.340> framework 00:01:54.840 --> 00:01:54.850 align:start position:0% covers we call the the ESC framework 00:01:54.850 --> 00:01:57.919 align:start position:0% covers we call the the ESC framework running<00:01:55.179> in<00:01:55.299> the<00:01:56.049> excuse<00:01:56.560> me<00:01:56.709> ESC<00:01:57.039> fabric 00:01:57.919 --> 00:01:57.929 align:start position:0% running in the excuse me ESC fabric 00:01:57.929 --> 00:02:00.029 align:start position:0% running in the excuse me ESC fabric running<00:01:58.929> has<00:01:59.139> some<00:01:59.289> core<00:01:59.560> infrastructure 00:02:00.029 --> 00:02:00.039 align:start position:0% running has some core infrastructure 00:02:00.039 --> 00:02:01.980 align:start position:0% running has some core infrastructure capabilities<00:02:00.399> the<00:02:01.240> first<00:02:01.450> of<00:02:01.599> which<00:02:01.689> is<00:02:01.749> we 00:02:01.980 --> 00:02:01.990 align:start position:0% capabilities the first of which is we 00:02:01.990 --> 00:02:04.980 align:start position:0% capabilities the first of which is we authenticate<00:02:02.409> users<00:02:03.389> so<00:02:04.389> we<00:02:04.539> use<00:02:04.659> Azure 00:02:04.980 --> 00:02:04.990 align:start position:0% authenticate users so we use Azure 00:02:04.990 --> 00:02:06.419 align:start position:0% authenticate users so we use Azure Active<00:02:05.139> Directory<00:02:05.349> to<00:02:05.649> authenticate<00:02:06.310> those 00:02:06.419 --> 00:02:06.429 align:start position:0% Active Directory to authenticate those 00:02:06.429 --> 00:02:08.969 align:start position:0% Active Directory to authenticate those users<00:02:06.789> now<00:02:06.999> don't<00:02:07.599> think<00:02:07.779> we<00:02:08.410> can<00:02:08.500> use<00:02:08.560> this<00:02:08.800> to 00:02:08.969 --> 00:02:08.979 align:start position:0% users now don't think we can use this to 00:02:08.979 --> 00:02:10.499 align:start position:0% users now don't think we can use this to authenticate<00:02:09.429> using<00:02:09.610> Facebook<00:02:10.150> if<00:02:10.300> you<00:02:10.390> want 00:02:10.499 --> 00:02:10.509 align:start position:0% authenticate using Facebook if you want 00:02:10.509 --> 00:02:13.560 align:start position:0% authenticate using Facebook if you want to<00:02:11.040> but<00:02:12.040> essentially<00:02:12.400> you<00:02:12.520> authenticate<00:02:13.150> the 00:02:13.560 --> 00:02:13.570 align:start position:0% to but essentially you authenticate the 00:02:13.570 --> 00:02:14.940 align:start position:0% to but essentially you authenticate the user<00:02:13.810> would<00:02:14.200> an<00:02:14.410> attached 00:02:14.940 --> 00:02:14.950 align:start position:0% user would an attached 00:02:14.950 --> 00:02:16.949 align:start position:0% user would an attached message<00:02:15.310> that<00:02:15.790> flows<00:02:16.150> into<00:02:16.360> the<00:02:16.510> system<00:02:16.840> to 00:02:16.949 --> 00:02:16.959 align:start position:0% message that flows into the system to 00:02:16.959 --> 00:02:19.740 align:start position:0% message that flows into the system to create<00:02:17.140> a<00:02:17.230> secure<00:02:17.560> session<00:02:19.660> it's 00:02:19.740 --> 00:02:19.750 align:start position:0% create a secure session it's 00:02:19.750 --> 00:02:21.990 align:start position:0% create a secure session it's themselves<00:02:20.379> have<00:02:20.560> dependencies<00:02:21.340> meaning 00:02:21.990 --> 00:02:22.000 align:start position:0% themselves have dependencies meaning 00:02:22.000 --> 00:02:24.240 align:start position:0% themselves have dependencies meaning this<00:02:22.540> is<00:02:22.720> what<00:02:22.870> are<00:02:22.989> required<00:02:23.410> or<00:02:23.680> require<00:02:24.129> an 00:02:24.240 --> 00:02:24.250 align:start position:0% this is what are required or require an 00:02:24.250 --> 00:02:26.309 align:start position:0% this is what are required or require an enclave<00:02:24.700> what<00:02:25.030> kind<00:02:25.209> of<00:02:25.269> runtime<00:02:25.569> environment 00:02:26.309 --> 00:02:26.319 align:start position:0% enclave what kind of runtime environment 00:02:26.319 --> 00:02:29.759 align:start position:0% enclave what kind of runtime environment do<00:02:26.379> I<00:02:26.440> need<00:02:26.739> my<00:02:27.069> dad<00:02:27.610> or<00:02:27.819> a<00:02:27.879> Java<00:02:28.319> or<00:02:29.319> a<00:02:29.379> rust 00:02:29.759 --> 00:02:29.769 align:start position:0% do I need my dad or a Java or a rust 00:02:29.769 --> 00:02:33.180 align:start position:0% do I need my dad or a Java or a rust it<00:02:31.380> so<00:02:32.380> those<00:02:32.530> dependencies<00:02:33.040> are 00:02:33.180 --> 00:02:33.190 align:start position:0% it so those dependencies are 00:02:33.190 --> 00:02:35.940 align:start position:0% it so those dependencies are inspected<00:02:33.730> and<00:02:34.450> then<00:02:34.599> the<00:02:35.470> infrastructure 00:02:35.940 --> 00:02:35.950 align:start position:0% inspected and then the infrastructure 00:02:35.950 --> 00:02:39.240 align:start position:0% inspected and then the infrastructure has<00:02:36.099> essentially<00:02:36.900> many<00:02:37.900> hsn's<00:02:38.680> available<00:02:39.130> to 00:02:39.240 --> 00:02:39.250 align:start position:0% has essentially many hsn's available to 00:02:39.250 --> 00:02:40.500 align:start position:0% has essentially many hsn's available to it<00:02:39.370> those<00:02:39.489> can<00:02:39.700> be<00:02:39.730> in<00:02:39.880> the<00:02:39.940> cloud<00:02:40.150> that<00:02:40.360> can 00:02:40.500 --> 00:02:40.510 align:start position:0% it those can be in the cloud that can 00:02:40.510 --> 00:02:43.199 align:start position:0% it those can be in the cloud that can also<00:02:40.630> be<00:02:40.720> on<00:02:40.870> prim<00:02:41.190> and<00:02:42.190> then<00:02:42.340> we<00:02:42.489> pool<00:02:42.790> scarce 00:02:43.199 --> 00:02:43.209 align:start position:0% also be on prim and then we pool scarce 00:02:43.209 --> 00:02:44.970 align:start position:0% also be on prim and then we pool scarce resources<00:02:43.720> enclaves<00:02:44.290> would<00:02:44.470> be<00:02:44.560> one<00:02:44.739> of<00:02:44.769> them 00:02:44.970 --> 00:02:44.980 align:start position:0% resources enclaves would be one of them 00:02:44.980 --> 00:02:47.100 align:start position:0% resources enclaves would be one of them but<00:02:45.700> we<00:02:45.819> envision<00:02:46.269> that<00:02:46.480> you<00:02:46.690> would<00:02:46.810> want<00:02:47.019> to 00:02:47.100 --> 00:02:47.110 align:start position:0% but we envision that you would want to 00:02:47.110 --> 00:02:49.140 align:start position:0% but we envision that you would want to use<00:02:47.230> things<00:02:47.440> like<00:02:47.560> FPGAs<00:02:48.340> to<00:02:48.580> accelerate<00:02:49.000> the 00:02:49.140 --> 00:02:49.150 align:start position:0% use things like FPGAs to accelerate the 00:02:49.150 --> 00:02:51.839 align:start position:0% use things like FPGAs to accelerate the zero<00:02:49.330> knowledge<00:02:49.480> proof<00:02:49.630> generation<00:02:50.319> a6<00:02:51.250> GPUs 00:02:51.839 --> 00:02:51.849 align:start position:0% zero knowledge proof generation a6 GPUs 00:02:51.849 --> 00:02:54.270 align:start position:0% zero knowledge proof generation a6 GPUs whatever<00:02:52.390> some<00:02:52.660> sort<00:02:52.870> of<00:02:52.900> combination<00:02:53.769> so<00:02:54.190> we 00:02:54.270 --> 00:02:54.280 align:start position:0% whatever some sort of combination so we 00:02:54.280 --> 00:02:57.449 align:start position:0% whatever some sort of combination so we allow<00:02:54.489> you<00:02:54.519> to<00:02:54.670> have<00:02:54.970> single<00:02:55.329> sort<00:02:55.780> of<00:02:56.310> we<00:02:57.310> call 00:02:57.449 --> 00:02:57.459 align:start position:0% allow you to have single sort of we call 00:02:57.459 --> 00:02:59.490 align:start position:0% allow you to have single sort of we call them<00:02:57.640> delegates<00:02:58.180> essentially<00:02:59.140> but<00:02:59.380> you're 00:02:59.490 --> 00:02:59.500 align:start position:0% them delegates essentially but you're 00:02:59.500 --> 00:03:01.220 align:start position:0% them delegates essentially but you're delegating<00:02:59.739> your<00:03:00.190> cryptographic<00:03:00.459> operations 00:03:01.220 --> 00:03:01.230 align:start position:0% delegating your cryptographic operations 00:03:01.230 --> 00:03:03.000 align:start position:0% delegating your cryptographic operations to<00:03:02.230> this<00:03:02.380> Enclave 00:03:03.000 --> 00:03:03.010 align:start position:0% to this Enclave 00:03:03.010 --> 00:03:05.280 align:start position:0% to this Enclave environment<00:03:03.849> so<00:03:04.390> what<00:03:04.599> happens<00:03:04.959> at<00:03:05.079> runtime 00:03:05.280 --> 00:03:05.290 align:start position:0% environment so what happens at runtime 00:03:05.290 --> 00:03:07.949 align:start position:0% environment so what happens at runtime is<00:03:06.099> a<00:03:06.160> crypto<00:03:06.519> delegate<00:03:06.940> gets<00:03:07.120> built<00:03:07.390> that 00:03:07.949 --> 00:03:07.959 align:start position:0% is a crypto delegate gets built that 00:03:07.959 --> 00:03:10.860 align:start position:0% is a crypto delegate gets built that will<00:03:08.380> be<00:03:08.530> injected<00:03:09.130> with<00:03:09.310> an<00:03:09.459> enclave<00:03:09.880> with 00:03:10.860 --> 00:03:10.870 align:start position:0% will be injected with an enclave with 00:03:10.870 --> 00:03:12.059 align:start position:0% will be injected with an enclave with the<00:03:10.959> appropriate<00:03:11.410> secrets<00:03:11.860> in<00:03:11.980> the 00:03:12.059 --> 00:03:12.069 align:start position:0% the appropriate secrets in the 00:03:12.069 --> 00:03:14.039 align:start position:0% the appropriate secrets in the appropriate<00:03:12.579> AP<00:03:12.940> is<00:03:13.090> that<00:03:13.540> you're<00:03:13.660> trying<00:03:13.959> to 00:03:14.039 --> 00:03:14.049 align:start position:0% appropriate AP is that you're trying to 00:03:14.049 --> 00:03:15.690 align:start position:0% appropriate AP is that you're trying to use<00:03:14.440> for<00:03:14.680> the<00:03:14.739> platforms<00:03:15.280> if<00:03:15.430> you're<00:03:15.549> using 00:03:15.690 --> 00:03:15.700 align:start position:0% use for the platforms if you're using 00:03:15.700 --> 00:03:19.860 align:start position:0% use for the platforms if you're using ECC<00:03:16.329> or<00:03:16.690> the<00:03:16.959> ECC<00:03:17.709> libraries<00:03:18.389> you<00:03:19.389> also<00:03:19.540> might 00:03:19.860 --> 00:03:19.870 align:start position:0% ECC or the ECC libraries you also might 00:03:19.870 --> 00:03:21.599 align:start position:0% ECC or the ECC libraries you also might get<00:03:20.019> a<00:03:20.079> composite<00:03:20.470> where<00:03:20.950> you<00:03:21.040> would<00:03:21.130> get<00:03:21.310> both 00:03:21.599 --> 00:03:21.609 align:start position:0% get a composite where you would get both 00:03:21.609 --> 00:03:23.910 align:start position:0% get a composite where you would get both an<00:03:21.790> enclave<00:03:22.150> and<00:03:22.389> an<00:03:22.690> FPGA<00:03:23.200> and<00:03:23.560> you<00:03:23.620> can<00:03:23.769> call 00:03:23.910 --> 00:03:23.920 align:start position:0% an enclave and an FPGA and you can call 00:03:23.920 --> 00:03:26.970 align:start position:0% an enclave and an FPGA and you can call this<00:03:24.069> thing<00:03:24.310> a<00:03:24.459> foo<00:03:25.079> and<00:03:26.079> give<00:03:26.380> me<00:03:26.530> a<00:03:26.560> food<00:03:26.829> at 00:03:26.970 --> 00:03:26.980 align:start position:0% this thing a foo and give me a food at 00:03:26.980 --> 00:03:29.309 align:start position:0% this thing a foo and give me a food at runtime<00:03:27.190> and<00:03:27.700> then<00:03:27.819> I'll<00:03:28.030> have<00:03:28.239> my<00:03:28.359> algorithms 00:03:29.309 --> 00:03:29.319 align:start position:0% runtime and then I'll have my algorithms 00:03:29.319 --> 00:03:30.890 align:start position:0% runtime and then I'll have my algorithms generators<00:03:29.769> err<00:03:29.920> knowledge<00:03:30.190> proof<00:03:30.430> or 00:03:30.890 --> 00:03:30.900 align:start position:0% generators err knowledge proof or 00:03:30.900 --> 00:03:33.599 align:start position:0% generators err knowledge proof or whatever<00:03:31.900> you<00:03:32.079> want<00:03:32.230> to<00:03:32.290> do<00:03:32.500> so<00:03:33.370> you<00:03:33.430> can 00:03:33.599 --> 00:03:33.609 align:start position:0% whatever you want to do so you can 00:03:33.609 --> 00:03:35.819 align:start position:0% whatever you want to do so you can really<00:03:33.760> compose<00:03:34.410> this<00:03:35.410> hardware 00:03:35.819 --> 00:03:35.829 align:start position:0% really compose this hardware 00:03:35.829 --> 00:03:40.229 align:start position:0% really compose this hardware acceleration<00:03:36.690> for<00:03:37.690> the<00:03:38.549> requirements<00:03:39.549> that 00:03:40.229 --> 00:03:40.239 align:start position:0% acceleration for the requirements that 00:03:40.239 --> 00:03:41.670 align:start position:0% acceleration for the requirements that you<00:03:40.420> have<00:03:40.540> to<00:03:40.660> allow<00:03:40.900> this<00:03:41.109> do<00:03:41.319> things<00:03:41.530> like 00:03:41.670 --> 00:03:41.680 align:start position:0% you have to allow this do things like 00:03:41.680 --> 00:03:44.160 align:start position:0% you have to allow this do things like dynamic<00:03:42.010> allocation<00:03:42.400> and<00:03:43.150> de-allocation<00:03:43.420> so 00:03:44.160 --> 00:03:44.170 align:start position:0% dynamic allocation and de-allocation so 00:03:44.170 --> 00:03:45.870 align:start position:0% dynamic allocation and de-allocation so we<00:03:44.260> pull<00:03:44.500> these<00:03:44.680> resources<00:03:45.130> to<00:03:45.340> get<00:03:45.430> massive 00:03:45.870 --> 00:03:45.880 align:start position:0% we pull these resources to get massive 00:03:45.880 --> 00:03:49.590 align:start position:0% we pull these resources to get massive scale<00:03:46.180> and<00:03:46.680> also<00:03:47.680> reduces<00:03:48.190> cost<00:03:48.459> so<00:03:49.150> you<00:03:49.239> can 00:03:49.590 --> 00:03:49.600 align:start position:0% scale and also reduces cost so you can 00:03:49.600 --> 00:03:51.090 align:start position:0% scale and also reduces cost so you can start<00:03:49.810> doing<00:03:49.900> very<00:03:50.200> innovative<00:03:50.470> things<00:03:50.920> with 00:03:51.090 --> 00:03:51.100 align:start position:0% start doing very innovative things with 00:03:51.100 --> 00:03:53.340 align:start position:0% start doing very innovative things with low<00:03:51.370> cost<00:03:51.700> you're<00:03:52.569> only<00:03:52.660> paying<00:03:52.930> for<00:03:53.230> what 00:03:53.340 --> 00:03:53.350 align:start position:0% low cost you're only paying for what 00:03:53.350 --> 00:03:54.870 align:start position:0% low cost you're only paying for what you're<00:03:53.500> using<00:03:53.530> so<00:03:54.250> you're<00:03:54.370> not<00:03:54.430> gonna<00:03:54.579> pay<00:03:54.850> for 00:03:54.870 --> 00:03:54.880 align:start position:0% you're using so you're not gonna pay for 00:03:54.880 --> 00:03:57.569 align:start position:0% you're using so you're not gonna pay for all<00:03:55.180> this<00:03:55.420> stuff<00:03:55.620> 24<00:03:56.620> by<00:03:56.739> 7<00:03:57.160> you're<00:03:57.310> gonna<00:03:57.400> pay 00:03:57.569 --> 00:03:57.579 align:start position:0% all this stuff 24 by 7 you're gonna pay 00:03:57.579 --> 00:03:59.670 align:start position:0% all this stuff 24 by 7 you're gonna pay for<00:03:57.609> it<00:03:57.819> for<00:03:58.000> the<00:03:58.060> second<00:03:58.660> or<00:03:58.810> two<00:03:59.019> if<00:03:59.440> anything 00:03:59.670 --> 00:03:59.680 align:start position:0% for it for the second or two if anything 00:03:59.680 --> 00:04:01.410 align:start position:0% for it for the second or two if anything what<00:03:59.769> you're<00:03:59.889> doing<00:04:00.130> that<00:04:01.000> you're<00:04:01.090> actually 00:04:01.410 --> 00:04:01.420 align:start position:0% what you're doing that you're actually 00:04:01.420 --> 00:04:05.009 align:start position:0% what you're doing that you're actually using<00:04:01.599> it<00:04:01.900> for<00:04:02.079> transaction<00:04:02.970> now<00:04:03.970> we'll<00:04:04.870> talk 00:04:05.009 --> 00:04:05.019 align:start position:0% using it for transaction now we'll talk 00:04:05.019 --> 00:04:06.990 align:start position:0% using it for transaction now we'll talk more<00:04:05.139> about<00:04:05.200> some<00:04:05.590> of<00:04:05.739> the<00:04:05.859> kid<00:04:06.250> around 00:04:06.990 --> 00:04:07.000 align:start position:0% more about some of the kid around 00:04:07.000 --> 00:04:09.750 align:start position:0% more about some of the kid around fication<00:04:07.389> zuv<00:04:07.750> this<00:04:07.930> but<00:04:08.549> you<00:04:09.549> can<00:04:09.670> do 00:04:09.750 --> 00:04:09.760 align:start position:0% fication zuv this but you can do 00:04:09.760 --> 00:04:11.670 align:start position:0% fication zuv this but you can do everything<00:04:09.940> from<00:04:10.299> just<00:04:10.540> basic<00:04:10.959> signatures<00:04:11.410> to 00:04:11.670 --> 00:04:11.680 align:start position:0% everything from just basic signatures to 00:04:11.680 --> 00:04:13.199 align:start position:0% everything from just basic signatures to threshold<00:04:12.220> encryption<00:04:12.669> so<00:04:12.940> you<00:04:13.030> can<00:04:13.120> do 00:04:13.199 --> 00:04:13.209 align:start position:0% threshold encryption so you can do 00:04:13.209 --> 00:04:15.690 align:start position:0% threshold encryption so you can do encryption<00:04:13.599> in<00:04:13.870> the<00:04:13.989> cloud<00:04:14.200> as<00:04:14.950> well<00:04:15.310> I'm 00:04:15.690 --> 00:04:15.700 align:start position:0% encryption in the cloud as well I'm 00:04:15.700 --> 00:04:19.469 align:start position:0% encryption in the cloud as well I'm using<00:04:16.180> these<00:04:16.590> so<00:04:17.590> the<00:04:17.919> broader<00:04:18.130> framework<00:04:18.669> we 00:04:19.469 --> 00:04:19.479 align:start position:0% using these so the broader framework we 00:04:19.479 --> 00:04:21.990 align:start position:0% using these so the broader framework we do<00:04:19.690> support<00:04:20.500> multiple<00:04:21.190> Ledger's<00:04:21.609> down<00:04:21.789> at<00:04:21.910> the 00:04:21.990 --> 00:04:22.000 align:start position:0% do support multiple Ledger's down at the 00:04:22.000 --> 00:04:24.450 align:start position:0% do support multiple Ledger's down at the bottom<00:04:22.150> we<00:04:22.660> have<00:04:22.690> a<00:04:23.229> couple<00:04:23.950> years<00:04:24.159> ago<00:04:24.250> we 00:04:24.450 --> 00:04:24.460 align:start position:0% bottom we have a couple years ago we 00:04:24.460 --> 00:04:26.580 align:start position:0% bottom we have a couple years ago we announced<00:04:24.520> blockchain<00:04:25.360> is<00:04:25.390> a<00:04:25.510> service 00:04:26.580 --> 00:04:26.590 align:start position:0% announced blockchain is a service 00:04:26.590 --> 00:04:28.379 align:start position:0% announced blockchain is a service just<00:04:26.949> unfortunately<00:04:27.639> named<00:04:27.850> it<00:04:27.970> that<00:04:28.090> for 00:04:28.379 --> 00:04:28.389 align:start position:0% just unfortunately named it that for 00:04:28.389 --> 00:04:30.060 align:start position:0% just unfortunately named it that for some<00:04:28.510> reason<00:04:28.540> it<00:04:29.320> seems<00:04:29.500> like<00:04:29.620> a<00:04:29.680> good<00:04:29.830> idea<00:04:29.919> at 00:04:30.060 --> 00:04:30.070 align:start position:0% some reason it seems like a good idea at 00:04:30.070 --> 00:04:31.620 align:start position:0% some reason it seems like a good idea at a<00:04:30.130> time<00:04:30.190> but<00:04:30.940> since<00:04:31.060> it<00:04:31.270> was<00:04:31.389> based<00:04:31.540> on 00:04:31.620 --> 00:04:31.630 align:start position:0% a time but since it was based on 00:04:31.630 --> 00:04:33.870 align:start position:0% a time but since it was based on etherium<00:04:32.169> everything<00:04:32.919> we<00:04:33.010> do<00:04:33.190> at<00:04:33.490> Microsoft 00:04:33.870 --> 00:04:33.880 align:start position:0% etherium everything we do at Microsoft 00:04:33.880 --> 00:04:35.909 align:start position:0% etherium everything we do at Microsoft really<00:04:34.330> starts<00:04:34.690> for<00:04:34.810> the<00:04:34.900> theory<00:04:35.139> when<00:04:35.830> we 00:04:35.909 --> 00:04:35.919 align:start position:0% really starts for the theory when we 00:04:35.919 --> 00:04:37.770 align:start position:0% really starts for the theory when we sort<00:04:36.100> of<00:04:36.130> branch<00:04:36.370> out<00:04:36.580> from<00:04:36.610> there<00:04:36.970> so<00:04:37.600> it 00:04:37.770 --> 00:04:37.780 align:start position:0% sort of branch out from there so it 00:04:37.780 --> 00:04:39.570 align:start position:0% sort of branch out from there so it applies<00:04:37.990> the<00:04:38.020> theorem<00:04:38.440> alliance<00:04:38.800> or<00:04:38.949> forum 00:04:39.570 --> 00:04:39.580 align:start position:0% applies the theorem alliance or forum 00:04:39.580 --> 00:04:41.520 align:start position:0% applies the theorem alliance or forum and<00:04:39.760> things<00:04:39.940> like<00:04:40.090> that<00:04:40.270> but<00:04:41.110> we<00:04:41.199> also<00:04:41.350> support 00:04:41.520 --> 00:04:41.530 align:start position:0% and things like that but we also support 00:04:41.530 --> 00:04:43.409 align:start position:0% and things like that but we also support court<00:04:41.949> on<00:04:42.070> these<00:04:42.220> others<00:04:42.580> because<00:04:43.270> we 00:04:43.409 --> 00:04:43.419 align:start position:0% court on these others because we 00:04:43.419 --> 00:04:45.780 align:start position:0% court on these others because we abstract<00:04:43.860> them<00:04:44.860> away<00:04:45.100> with<00:04:45.310> what<00:04:45.520> we<00:04:45.580> call<00:04:45.699> the 00:04:45.780 --> 00:04:45.790 align:start position:0% abstract them away with what we call the 00:04:45.790 --> 00:04:48.780 align:start position:0% abstract them away with what we call the blockchain<00:04:46.030> router<00:04:46.479> and<00:04:46.990> this<00:04:47.229> is<00:04:47.560> a<00:04:47.790> common 00:04:48.780 --> 00:04:48.790 align:start position:0% blockchain router and this is a common 00:04:48.790 --> 00:04:51.450 align:start position:0% blockchain router and this is a common abstraction<00:04:49.330> pattern<00:04:49.690> what<00:04:50.560> we<00:04:50.710> define<00:04:51.430> a 00:04:51.450 --> 00:04:51.460 align:start position:0% abstraction pattern what we define a 00:04:51.460 --> 00:04:53.400 align:start position:0% abstraction pattern what we define a basic<00:04:51.910> interface<00:04:52.479> where<00:04:52.810> anyone<00:04:53.110> can<00:04:53.260> do 00:04:53.400 --> 00:04:53.410 align:start position:0% basic interface where anyone can do 00:04:53.410 --> 00:04:55.920 align:start position:0% basic interface where anyone can do write<00:04:53.710> a<00:04:54.160> connector<00:04:55.150> that<00:04:55.389> plugs<00:04:55.449> into<00:04:55.810> the 00:04:55.920 --> 00:04:55.930 align:start position:0% write a connector that plugs into the 00:04:55.930 --> 00:04:58.320 align:start position:0% write a connector that plugs into the router<00:04:56.080> as<00:04:56.350> a<00:04:56.440> simple<00:04:57.160> interface<00:04:57.550> definition 00:04:58.320 --> 00:04:58.330 align:start position:0% router as a simple interface definition 00:04:58.330 --> 00:05:01.890 align:start position:0% router as a simple interface definition and<00:04:58.870> then<00:04:59.680> it<00:05:00.430> has<00:05:00.639> very<00:05:01.150> blotchy<00:05:01.720> and 00:05:01.890 --> 00:05:01.900 align:start position:0% and then it has very blotchy and 00:05:01.900 --> 00:05:04.469 align:start position:0% and then it has very blotchy and specific<00:05:02.440> I<00:05:02.680> knows<00:05:03.370> how<00:05:03.550> to<00:05:03.610> create<00:05:04.090> watching 00:05:04.469 --> 00:05:04.479 align:start position:0% specific I knows how to create watching 00:05:04.479 --> 00:05:06.750 align:start position:0% specific I knows how to create watching specific<00:05:04.960> transactions<00:05:05.560> you<00:05:06.430> will<00:05:06.580> create 00:05:06.750 --> 00:05:06.760 align:start position:0% specific transactions you will create 00:05:06.760 --> 00:05:08.670 align:start position:0% specific transactions you will create contract<00:05:07.360> proxies<00:05:07.780> which<00:05:07.990> is<00:05:08.110> essentially 00:05:08.670 --> 00:05:08.680 align:start position:0% contract proxies which is essentially 00:05:08.680 --> 00:05:10.710 align:start position:0% contract proxies which is essentially taking<00:05:09.610> that<00:05:09.729> next<00:05:09.940> step<00:05:10.210> where<00:05:10.450> we<00:05:10.479> talk 00:05:10.710 --> 00:05:10.720 align:start position:0% taking that next step where we talk 00:05:10.720 --> 00:05:12.540 align:start position:0% taking that next step where we talk about<00:05:10.840> a<00:05:10.990> type<00:05:11.290> system<00:05:11.560> CREP<00:05:12.130> let's<00:05:12.310> don't 00:05:12.540 --> 00:05:12.550 align:start position:0% about a type system CREP let's don't 00:05:12.550 --> 00:05:15.120 align:start position:0% about a type system CREP let's don't know<00:05:13.050> what<00:05:14.050> watching<00:05:14.500> they're<00:05:14.680> talking<00:05:15.010> to 00:05:15.120 --> 00:05:15.130 align:start position:0% know what watching they're talking to 00:05:15.130 --> 00:05:17.010 align:start position:0% know what watching they're talking to they<00:05:15.310> don't<00:05:15.400> care<00:05:15.790> they<00:05:16.210> deal<00:05:16.419> with<00:05:16.450> message 00:05:17.010 --> 00:05:17.020 align:start position:0% they don't care they deal with message 00:05:17.020 --> 00:05:19.529 align:start position:0% they don't care they deal with message types<00:05:17.380> so<00:05:18.310> strongly<00:05:18.700> typed<00:05:18.880> messages<00:05:19.120> are 00:05:19.529 --> 00:05:19.539 align:start position:0% types so strongly typed messages are 00:05:19.539 --> 00:05:21.540 align:start position:0% types so strongly typed messages are very<00:05:19.720> important<00:05:20.169> for<00:05:20.260> contractual<00:05:20.770> business 00:05:21.540 --> 00:05:21.550 align:start position:0% very important for contractual business 00:05:21.550 --> 00:05:23.580 align:start position:0% very important for contractual business we<00:05:21.729> need<00:05:21.910> to<00:05:22.060> know<00:05:22.210> not<00:05:22.960> only<00:05:23.020> what<00:05:23.260> a<00:05:23.289> message 00:05:23.580 --> 00:05:23.590 align:start position:0% we need to know not only what a message 00:05:23.590 --> 00:05:25.260 align:start position:0% we need to know not only what a message structure<00:05:23.889> is<00:05:24.130> but<00:05:24.370> what<00:05:24.580> data<00:05:24.789> types<00:05:25.090> are 00:05:25.260 --> 00:05:25.270 align:start position:0% structure is but what data types are 00:05:25.270 --> 00:05:28.170 align:start position:0% structure is but what data types are embedded<00:05:25.720> we<00:05:26.380> keep<00:05:26.560> don't<00:05:26.770> allow<00:05:26.979> variants<00:05:27.610> so 00:05:28.170 --> 00:05:28.180 align:start position:0% embedded we keep don't allow variants so 00:05:28.180 --> 00:05:29.790 align:start position:0% embedded we keep don't allow variants so they<00:05:28.270> need<00:05:28.419> to<00:05:28.510> be<00:05:28.600> declared<00:05:28.750> integers<00:05:29.560> or 00:05:29.790 --> 00:05:29.800 align:start position:0% they need to be declared integers or 00:05:29.800 --> 00:05:32.760 align:start position:0% they need to be declared integers or doubles<00:05:30.220> or<00:05:30.460> floats<00:05:30.490> or<00:05:31.000> whatever<00:05:31.770> or 00:05:32.760 --> 00:05:32.770 align:start position:0% doubles or floats or whatever or 00:05:32.770 --> 00:05:36.300 align:start position:0% doubles or floats or whatever or composite<00:05:33.400> types<00:05:35.860> 'its<00:05:35.950> will<00:05:36.160> then 00:05:36.300 --> 00:05:36.310 align:start position:0% composite types 'its will then 00:05:36.310 --> 00:05:39.000 align:start position:0% composite types 'its will then use<00:05:36.610> those<00:05:36.820> message<00:05:37.240> types<00:05:37.680> and<00:05:38.680> then<00:05:38.860> they 00:05:39.000 --> 00:05:39.010 align:start position:0% use those message types and then they 00:05:39.010 --> 00:05:40.650 align:start position:0% use those message types and then they pass<00:05:39.669> them<00:05:39.880> down<00:05:40.000> to<00:05:40.090> the<00:05:40.180> proxy<00:05:40.539> the<00:05:40.630> proxy 00:05:40.650 --> 00:05:40.660 align:start position:0% pass them down to the proxy the proxy 00:05:40.660 --> 00:05:43.589 align:start position:0% pass them down to the proxy the proxy can<00:05:41.169> ingest<00:05:41.729> those<00:05:42.729> message<00:05:43.120> types<00:05:43.330> and<00:05:43.510> then 00:05:43.589 --> 00:05:43.599 align:start position:0% can ingest those message types and then 00:05:43.599 --> 00:05:44.760 align:start position:0% can ingest those message types and then convert<00:05:43.930> them<00:05:44.139> into<00:05:44.289> the<00:05:44.470> appropriate 00:05:44.760 --> 00:05:44.770 align:start position:0% convert them into the appropriate 00:05:44.770 --> 00:05:47.640 align:start position:0% convert them into the appropriate watching<00:05:45.599> transaction<00:05:46.599> you<00:05:47.410> see<00:05:47.530> the 00:05:47.640 --> 00:05:47.650 align:start position:0% watching transaction you see the 00:05:47.650 --> 00:05:50.129 align:start position:0% watching transaction you see the scripted<00:05:47.979> gala<00:05:48.160> gets<00:05:48.750> attached<00:05:49.750> to<00:05:50.050> these 00:05:50.129 --> 00:05:50.139 align:start position:0% scripted gala gets attached to these 00:05:50.139 --> 00:05:52.290 align:start position:0% scripted gala gets attached to these various<00:05:50.560> locations<00:05:51.250> these<00:05:51.520> things<00:05:51.789> are<00:05:51.910> again 00:05:52.290 --> 00:05:52.300 align:start position:0% various locations these things are again 00:05:52.300 --> 00:05:54.930 align:start position:0% various locations these things are again generated<00:05:52.780> on<00:05:52.840> the<00:05:52.870> fly<00:05:53.250> we<00:05:54.250> support<00:05:54.700> multiple 00:05:54.930 --> 00:05:54.940 align:start position:0% generated on the fly we support multiple 00:05:54.940 --> 00:05:57.779 align:start position:0% generated on the fly we support multiple signatures<00:05:55.599> so<00:05:56.050> you<00:05:56.110> have<00:05:56.700> familiar<00:05:57.700> with 00:05:57.779 --> 00:05:57.789 align:start position:0% signatures so you have familiar with 00:05:57.789 --> 00:05:59.909 align:start position:0% signatures so you have familiar with certificate<00:05:58.240> chains<00:05:58.479> we<00:05:59.260> call<00:05:59.470> it<00:05:59.560> a<00:05:59.590> crippled 00:05:59.909 --> 00:05:59.919 align:start position:0% certificate chains we call it a crippled 00:05:59.919 --> 00:06:05.659 align:start position:0% certificate chains we call it a crippled onion<00:06:00.190> which<00:06:00.490> are<00:06:00.639> layers<00:06:00.910> of<00:06:01.470> of<00:06:03.060> crypto 00:06:05.659 --> 00:06:05.669 align:start position:0% onion which are layers of of crypto 00:06:05.669 --> 00:06:08.460 align:start position:0% onion which are layers of of crypto validations<00:06:06.669> of<00:06:06.940> each<00:06:07.300> operation<00:06:07.810> both<00:06:08.229> from 00:06:08.460 --> 00:06:08.470 align:start position:0% validations of each operation both from 00:06:08.470 --> 00:06:10.320 align:start position:0% validations of each operation both from an<00:06:08.620> attestation<00:06:09.130> standpoint<00:06:09.880> that<00:06:09.940> the<00:06:10.120> code 00:06:10.320 --> 00:06:10.330 align:start position:0% an attestation standpoint that the code 00:06:10.330 --> 00:06:12.629 align:start position:0% an attestation standpoint that the code ran<00:06:10.599> and<00:06:10.840> confident<00:06:11.260> confidentially<00:06:12.070> from 00:06:12.629 --> 00:06:12.639 align:start position:0% ran and confident confidentially from 00:06:12.639 --> 00:06:15.060 align:start position:0% ran and confident confidentially from the<00:06:12.760> Enclave<00:06:13.120> to<00:06:13.229> the<00:06:14.229> source<00:06:14.500> of<00:06:14.740> your<00:06:14.860> data 00:06:15.060 --> 00:06:15.070 align:start position:0% the Enclave to the source of your data 00:06:15.070 --> 00:06:16.440 align:start position:0% the Enclave to the source of your data actually<00:06:15.490> came<00:06:15.700> from<00:06:15.729> where<00:06:16.090> it<00:06:16.150> was<00:06:16.210> supposed 00:06:16.440 --> 00:06:16.450 align:start position:0% actually came from where it was supposed 00:06:16.450 --> 00:06:20.129 align:start position:0% actually came from where it was supposed to<00:06:16.510> come<00:06:17.039> so<00:06:18.039> we<00:06:18.510> create<00:06:19.510> this<00:06:19.630> signature 00:06:20.129 --> 00:06:20.139 align:start position:0% to come so we create this signature 00:06:20.139 --> 00:06:22.170 align:start position:0% to come so we create this signature onion<00:06:20.470> each<00:06:20.680> signature<00:06:21.099> validates<00:06:21.669> all<00:06:21.880> they 00:06:22.170 --> 00:06:22.180 align:start position:0% onion each signature validates all they 00:06:22.180 --> 00:06:24.960 align:start position:0% onion each signature validates all they nested<00:06:22.590> signatures<00:06:23.590> underneath<00:06:24.010> it<00:06:24.190> so<00:06:24.849> we 00:06:24.960 --> 00:06:24.970 align:start position:0% nested signatures underneath it so we 00:06:24.970 --> 00:06:26.520 align:start position:0% nested signatures underneath it so we sign<00:06:25.180> at<00:06:25.360> multiple<00:06:25.690> levels<00:06:25.840> we<00:06:26.200> also<00:06:26.349> have 00:06:26.520 --> 00:06:26.530 align:start position:0% sign at multiple levels we also have 00:06:26.530 --> 00:06:28.140 align:start position:0% sign at multiple levels we also have cypher<00:06:26.830> diversity<00:06:27.280> so<00:06:27.729> you<00:06:27.789> can<00:06:27.940> sign<00:06:28.120> with 00:06:28.140 --> 00:06:28.150 align:start position:0% cypher diversity so you can sign with 00:06:28.150 --> 00:06:32.400 align:start position:0% cypher diversity so you can sign with ECC<00:06:28.750> RSA<00:06:29.460> any<00:06:30.840> ciphers<00:06:31.840> that<00:06:32.050> you<00:06:32.139> want<00:06:32.289> to 00:06:32.400 --> 00:06:32.410 align:start position:0% ECC RSA any ciphers that you want to 00:06:32.410 --> 00:06:35.490 align:start position:0% ECC RSA any ciphers that you want to support<00:06:32.590> it's<00:06:32.979> very<00:06:33.160> flexible<00:06:33.340> platform<00:06:34.500> up 00:06:35.490 --> 00:06:35.500 align:start position:0% support it's very flexible platform up 00:06:35.500 --> 00:06:37.529 align:start position:0% support it's very flexible platform up at<00:06:35.710> the<00:06:35.800> top<00:06:36.039> so<00:06:36.820> these<00:06:36.940> cripples<00:06:37.330> we'll<00:06:37.419> talk 00:06:37.529 --> 00:06:37.539 align:start position:0% at the top so these cripples we'll talk 00:06:37.539 --> 00:06:38.940 align:start position:0% at the top so these cripples we'll talk about<00:06:37.780> them<00:06:37.930> a<00:06:38.110> little<00:06:38.440> bit<00:06:38.530> later<00:06:38.710> you<00:06:38.830> can 00:06:38.940 --> 00:06:38.950 align:start position:0% about them a little bit later you can 00:06:38.950 --> 00:06:40.080 align:start position:0% about them a little bit later you can write<00:06:39.099> them<00:06:39.250> in<00:06:39.340> dot 00:06:40.080 --> 00:06:40.090 align:start position:0% write them in dot 00:06:40.090 --> 00:06:44.420 align:start position:0% write them in dot Java<00:06:40.660> today<00:06:41.190> or<00:06:42.190> native<00:06:42.880> but<00:06:43.600> will<00:06:43.750> support 00:06:44.420 --> 00:06:44.430 align:start position:0% Java today or native but will support 00:06:44.430 --> 00:06:46.800 align:start position:0% Java today or native but will support any<00:06:45.430> sort<00:06:45.880> of<00:06:45.910> platforms<00:06:46.389> we're<00:06:46.540> agnostic 00:06:46.800 --> 00:06:46.810 align:start position:0% any sort of platforms we're agnostic 00:06:46.810 --> 00:06:49.680 align:start position:0% any sort of platforms we're agnostic what<00:06:47.620> you<00:06:47.740> want<00:06:47.889> to<00:06:47.950> do<00:06:48.070> you<00:06:48.700> it'll<00:06:49.060> be<00:06:49.120> open<00:06:49.360> so 00:06:49.680 --> 00:06:49.690 align:start position:0% what you want to do you it'll be open so 00:06:49.690 --> 00:06:52.290 align:start position:0% what you want to do you it'll be open so that<00:06:49.750> you<00:06:49.840> can<00:06:50.080> port<00:06:50.710> your<00:06:50.740> own<00:06:50.919> runtime<00:06:51.310> and 00:06:52.290 --> 00:06:52.300 align:start position:0% that you can port your own runtime and 00:06:52.300 --> 00:06:54.540 align:start position:0% that you can port your own runtime and create<00:06:52.630> your<00:06:52.720> own<00:06:52.840> container<00:06:53.169> that<00:06:54.130> runs<00:06:54.370> in 00:06:54.540 --> 00:06:54.550 align:start position:0% create your own container that runs in 00:06:54.550 --> 00:06:56.220 align:start position:0% create your own container that runs in this<00:06:54.639> platform<00:06:55.120> above<00:06:55.810> the<00:06:55.930> layer<00:06:56.110> we're 00:06:56.220 --> 00:06:56.230 align:start position:0% this platform above the layer we're 00:06:56.230 --> 00:06:57.870 align:start position:0% this platform above the layer we're using<00:06:56.380> standard<00:06:56.919> AMQP<00:06:57.520> if<00:06:57.639> you're<00:06:57.760> not 00:06:57.870 --> 00:06:57.880 align:start position:0% using standard AMQP if you're not 00:06:57.880 --> 00:07:00.090 align:start position:0% using standard AMQP if you're not familiar<00:06:58.000> with<00:06:58.210> that<00:06:58.270> that's<00:06:58.510> a<00:06:58.690> iso<00:06:59.590> standard 00:07:00.090 --> 00:07:00.100 align:start position:0% familiar with that that's a iso standard 00:07:00.100 --> 00:07:02.370 align:start position:0% familiar with that that's a iso standard for<00:07:00.460> for<00:07:01.300> messaging<00:07:01.750> that's<00:07:01.930> used<00:07:02.169> in<00:07:02.320> the 00:07:02.370 --> 00:07:02.380 align:start position:0% for for messaging that's used in the 00:07:02.380 --> 00:07:05.490 align:start position:0% for for messaging that's used in the enterprise<00:07:03.150> so<00:07:04.150> we're<00:07:04.270> using<00:07:04.419> AMQP<00:07:05.200> is<00:07:05.320> the 00:07:05.490 --> 00:07:05.500 align:start position:0% enterprise so we're using AMQP is the 00:07:05.500 --> 00:07:09.330 align:start position:0% enterprise so we're using AMQP is the basic<00:07:05.950> interface<00:07:06.900> and<00:07:07.900> those<00:07:08.530> messages<00:07:08.919> the 00:07:09.330 --> 00:07:09.340 align:start position:0% basic interface and those messages the 00:07:09.340 --> 00:07:10.560 align:start position:0% basic interface and those messages the strongly<00:07:09.610> typed<00:07:09.850> messages<00:07:09.970> are<00:07:10.360> what<00:07:10.480> are 00:07:10.560 --> 00:07:10.570 align:start position:0% strongly typed messages are what are 00:07:10.570 --> 00:07:12.900 align:start position:0% strongly typed messages are what are being<00:07:10.660> passed<00:07:10.930> back<00:07:11.260> and<00:07:11.320> forth<00:07:11.880> so<00:07:12.880> you 00:07:12.900 --> 00:07:12.910 align:start position:0% being passed back and forth so you 00:07:12.910 --> 00:07:15.540 align:start position:0% being passed back and forth so you define<00:07:13.389> your<00:07:13.600> API<00:07:13.930> with<00:07:14.200> their<00:07:14.350> types<00:07:14.620> and 00:07:15.540 --> 00:07:15.550 align:start position:0% define your API with their types and 00:07:15.550 --> 00:07:18.629 align:start position:0% define your API with their types and your<00:07:15.700> messages<00:07:16.560> you<00:07:17.560> can<00:07:17.710> stick<00:07:17.919> a<00:07:17.950> rest<00:07:18.250> or<00:07:18.490> an 00:07:18.629 --> 00:07:18.639 align:start position:0% your messages you can stick a rest or an 00:07:18.639 --> 00:07:22.950 align:start position:0% your messages you can stick a rest or an RPC<00:07:19.000> on<00:07:19.660> top<00:07:20.229> of<00:07:20.380> that<00:07:20.470> message<00:07:21.210> AMQP<00:07:22.210> very 00:07:22.950 --> 00:07:22.960 align:start position:0% RPC on top of that message AMQP very 00:07:22.960 --> 00:07:24.950 align:start position:0% RPC on top of that message AMQP very simply<00:07:23.350> and<00:07:23.530> easily<00:07:23.740> or<00:07:24.370> you<00:07:24.430> can<00:07:24.729> just 00:07:24.950 --> 00:07:24.960 align:start position:0% simply and easily or you can just 00:07:24.960 --> 00:07:27.600 align:start position:0% simply and easily or you can just serialize<00:07:25.960> your<00:07:26.169> messages<00:07:26.620> to<00:07:26.650> json<00:07:27.190> which<00:07:27.400> is 00:07:27.600 --> 00:07:27.610 align:start position:0% serialize your messages to json which is 00:07:27.610 --> 00:07:30.960 align:start position:0% serialize your messages to json which is the<00:07:27.729> default<00:07:28.560> so<00:07:29.560> it's<00:07:29.710> a<00:07:29.830> very<00:07:30.070> open<00:07:30.310> platform 00:07:30.960 --> 00:07:30.970 align:start position:0% the default so it's a very open platform 00:07:30.970 --> 00:07:32.850 align:start position:0% the default so it's a very open platform very<00:07:31.180> easy<00:07:31.540> to<00:07:31.750> integrate<00:07:31.960> into<00:07:32.169> any 00:07:32.850 --> 00:07:32.860 align:start position:0% very easy to integrate into any 00:07:32.860 --> 00:07:35.310 align:start position:0% very easy to integrate into any front-end<00:07:33.340> application<00:07:34.000> or<00:07:34.419> any<00:07:34.840> existing 00:07:35.310 --> 00:07:35.320 align:start position:0% front-end application or any existing 00:07:35.320 --> 00:07:37.980 align:start position:0% front-end application or any existing application<00:07:35.889> a<00:07:36.510> couple<00:07:37.510> of<00:07:37.570> things<00:07:37.660> that<00:07:37.900> you 00:07:37.980 --> 00:07:37.990 align:start position:0% application a couple of things that you 00:07:37.990 --> 00:07:39.450 align:start position:0% application a couple of things that you should<00:07:38.169> note<00:07:38.320> about<00:07:38.560> this<00:07:38.740> if<00:07:38.919> you<00:07:39.010> the 00:07:39.450 --> 00:07:39.460 align:start position:0% should note about this if you the 00:07:39.460 --> 00:07:41.550 align:start position:0% should note about this if you the cripples<00:07:39.790> are<00:07:39.880> running<00:07:40.180> above<00:07:40.930> the<00:07:41.080> law<00:07:41.229> chain 00:07:41.550 --> 00:07:41.560 align:start position:0% cripples are running above the law chain 00:07:41.560 --> 00:07:44.550 align:start position:0% cripples are running above the law chain they<00:07:42.400> can<00:07:42.580> run<00:07:42.790> in<00:07:43.090> a<00:07:43.240> singleton<00:07:43.750> pattern<00:07:43.990> you 00:07:44.550 --> 00:07:44.560 align:start position:0% they can run in a singleton pattern you 00:07:44.560 --> 00:07:47.219 align:start position:0% they can run in a singleton pattern you can<00:07:44.680> also<00:07:44.830> reach<00:07:45.190> out<00:07:46.990> 'its<00:07:47.110> can 00:07:47.219 --> 00:07:47.229 align:start position:0% can also reach out 'its can 00:07:47.229 --> 00:07:49.260 align:start position:0% can also reach out 'its can communicate<00:07:47.710> with<00:07:47.830> each<00:07:47.950> other<00:07:48.130> so<00:07:48.490> we<00:07:48.970> talked 00:07:49.260 --> 00:07:49.270 align:start position:0% communicate with each other so we talked 00:07:49.270 --> 00:07:51.930 align:start position:0% communicate with each other so we talked about<00:07:49.390> watching<00:07:49.900> Oracle's<00:07:50.760> you<00:07:51.760> can 00:07:51.930 --> 00:07:51.940 align:start position:0% about watching Oracle's you can 00:07:51.940 --> 00:07:53.550 align:start position:0% about watching Oracle's you can certainly<00:07:52.330> write<00:07:52.479> a<00:07:52.539> blockchain<00:07:52.780> Oracle<00:07:53.320> here 00:07:53.550 --> 00:07:53.560 align:start position:0% certainly write a blockchain Oracle here 00:07:53.560 --> 00:07:56.430 align:start position:0% certainly write a blockchain Oracle here and<00:07:53.740> write<00:07:54.300> attested<00:07:55.300> data<00:07:55.510> to<00:07:55.840> an<00:07:56.140> 80 00:07:56.430 --> 00:07:56.440 align:start position:0% and write attested data to an 80 00:07:56.440 --> 00:07:58.140 align:start position:0% and write attested data to an 80 underlying<00:07:56.919> blockchain<00:07:57.340> if<00:07:57.490> you're<00:07:57.610> thinking 00:07:58.140 --> 00:07:58.150 align:start position:0% underlying blockchain if you're thinking 00:07:58.150 --> 00:07:59.940 align:start position:0% underlying blockchain if you're thinking about<00:07:58.240> writing<00:07:58.570> an<00:07:58.780> Oracle<00:07:59.169> and<00:07:59.350> you're 00:07:59.940 --> 00:07:59.950 align:start position:0% about writing an Oracle and you're 00:07:59.950 --> 00:08:01.620 align:start position:0% about writing an Oracle and you're concerned<00:08:00.310> if<00:08:00.580> you<00:08:00.970> know<00:08:01.060> how<00:08:01.240> do<00:08:01.300> I<00:08:01.419> support 00:08:01.620 --> 00:08:01.630 align:start position:0% concerned if you know how do I support 00:08:01.630 --> 00:08:03.360 align:start position:0% concerned if you know how do I support Moulton<00:08:02.050> block<00:08:02.229> chains<00:08:02.500> this<00:08:02.680> is<00:08:02.740> one<00:08:03.010> way<00:08:03.160> for 00:08:03.360 --> 00:08:03.370 align:start position:0% Moulton block chains this is one way for 00:08:03.370 --> 00:08:05.400 align:start position:0% Moulton block chains this is one way for you<00:08:03.430> to<00:08:03.460> do<00:08:03.700> that<00:08:03.880> to<00:08:04.630> write<00:08:04.810> your<00:08:04.960> Oracle<00:08:05.200> once 00:08:05.400 --> 00:08:05.410 align:start position:0% you to do that to write your Oracle once 00:08:05.410 --> 00:08:07.879 align:start position:0% you to do that to write your Oracle once and<00:08:05.740> support<00:08:06.130> many<00:08:06.370> different<00:08:06.640> block<00:08:07.120> chains 00:08:07.879 --> 00:08:07.889 align:start position:0% and support many different block chains 00:08:07.889 --> 00:08:10.710 align:start position:0% and support many different block chains but<00:08:08.889> you<00:08:09.280> can<00:08:09.400> also<00:08:09.550> do<00:08:09.850> Oracle<00:08:10.270> services 00:08:10.710 --> 00:08:10.720 align:start position:0% but you can also do Oracle services 00:08:10.720 --> 00:08:12.240 align:start position:0% but you can also do Oracle services directly<00:08:11.050> from<00:08:11.260> crippling<00:08:11.470> to<00:08:11.979> it<00:08:12.070> so 00:08:12.240 --> 00:08:12.250 align:start position:0% directly from crippling to it so 00:08:12.250 --> 00:08:14.040 align:start position:0% directly from crippling to it so you<00:08:12.310> can<00:08:12.430> have<00:08:12.550> a<00:08:12.580> utility<00:08:13.840> it<00:08:13.900> which 00:08:14.040 --> 00:08:14.050 align:start position:0% you can have a utility it which 00:08:14.050 --> 00:08:15.930 align:start position:0% you can have a utility it which is<00:08:14.200> what<00:08:14.350> we<00:08:14.440> usually<00:08:14.590> call<00:08:14.740> an<00:08:15.010> Oracle<00:08:15.430> can<00:08:15.820> do 00:08:15.930 --> 00:08:15.940 align:start position:0% is what we usually call an Oracle can do 00:08:15.940 --> 00:08:18.990 align:start position:0% is what we usually call an Oracle can do more<00:08:16.120> than<00:08:16.270> that<00:08:16.530> actually<00:08:17.530> pass<00:08:17.770> a<00:08:18.280> tested 00:08:18.990 --> 00:08:19.000 align:start position:0% more than that actually pass a tested 00:08:19.000 --> 00:08:20.520 align:start position:0% more than that actually pass a tested data<00:08:19.150> to<00:08:19.360> another<00:08:20.080> that's<00:08:20.289> running 00:08:20.520 --> 00:08:20.530 align:start position:0% data to another that's running 00:08:20.530 --> 00:08:23.940 align:start position:0% data to another that's running at<00:08:20.620> a<00:08:20.650> contract<00:08:22.080> we<00:08:23.080> have<00:08:23.289> three<00:08:23.800> basic 00:08:23.940 --> 00:08:23.950 align:start position:0% at a contract we have three basic 00:08:23.950 --> 00:08:25.950 align:start position:0% at a contract we have three basic 'its<00:08:24.700> you<00:08:24.880> have<00:08:25.000> your<00:08:25.180> utility 00:08:25.950 --> 00:08:25.960 align:start position:0% 'its you have your utility 00:08:25.960 --> 00:08:27.529 align:start position:0% 'its you have your utility it's<00:08:26.320> those<00:08:26.650> are<00:08:26.800> the<00:08:26.919> ones<00:08:27.070> that<00:08:27.220> can 00:08:27.529 --> 00:08:27.539 align:start position:0% it's those are the ones that can 00:08:27.539 --> 00:08:29.909 align:start position:0% it's those are the ones that can provide<00:08:28.539> a<00:08:28.600> tested<00:08:29.139> data<00:08:29.320> but<00:08:29.590> you<00:08:29.620> can<00:08:29.800> also 00:08:29.909 --> 00:08:29.919 align:start position:0% provide a tested data but you can also 00:08:29.919 --> 00:08:33.120 align:start position:0% provide a tested data but you can also connect<00:08:30.310> to<00:08:30.370> an<00:08:30.490> ERP<00:08:30.940> system<00:08:31.110> you<00:08:32.110> could<00:08:32.289> react 00:08:33.120 --> 00:08:33.130 align:start position:0% connect to an ERP system you could react 00:08:33.130 --> 00:08:34.980 align:start position:0% connect to an ERP system you could react to<00:08:33.550> some<00:08:33.789> sort<00:08:34.000> of<00:08:34.060> event<00:08:34.360> that<00:08:34.419> happens<00:08:34.900> in 00:08:34.980 --> 00:08:34.990 align:start position:0% to some sort of event that happens in 00:08:34.990 --> 00:08:38.490 align:start position:0% to some sort of event that happens in the<00:08:35.110> outside<00:08:35.440> world<00:08:36.390> very<00:08:37.390> easily<00:08:37.659> and<00:08:38.140> then 00:08:38.490 --> 00:08:38.500 align:start position:0% the outside world very easily and then 00:08:38.500 --> 00:08:39.719 align:start position:0% the outside world very easily and then that<00:08:38.680> utility<00:08:39.070> Griphook<00:08:39.250> can<00:08:39.520> then 00:08:39.719 --> 00:08:39.729 align:start position:0% that utility Griphook can then 00:08:39.729 --> 00:08:41.880 align:start position:0% that utility Griphook can then communicate<00:08:39.909> with<00:08:40.300> what<00:08:40.419> we<00:08:40.510> call<00:08:40.690> a<00:08:41.200> contract 00:08:41.880 --> 00:08:41.890 align:start position:0% communicate with what we call a contract 00:08:41.890 --> 00:08:44.420 align:start position:0% communicate with what we call a contract triplet<00:08:42.219> which<00:08:42.880> represents<00:08:43.510> your<00:08:43.930> typical 00:08:44.420 --> 00:08:44.430 align:start position:0% triplet which represents your typical 00:08:44.430 --> 00:08:46.680 align:start position:0% triplet which represents your typical smart<00:08:45.430> contract<00:08:45.880> or<00:08:46.060> Enterprise<00:08:46.390> smart 00:08:46.680 --> 00:08:46.690 align:start position:0% smart contract or Enterprise smart 00:08:46.690 --> 00:08:48.960 align:start position:0% smart contract or Enterprise smart contract<00:08:47.080> so<00:08:47.200> what<00:08:47.320> we<00:08:47.380> call<00:08:47.560> it<00:08:47.680> but<00:08:48.520> we<00:08:48.850> also 00:08:48.960 --> 00:08:48.970 align:start position:0% contract so what we call it but we also 00:08:48.970 --> 00:08:51.900 align:start position:0% contract so what we call it but we also have<00:08:49.240> a<00:08:49.270> token<00:08:50.230> grip<00:08:50.530> what<00:08:50.680> as<00:08:50.800> well 00:08:51.900 --> 00:08:51.910 align:start position:0% have a token grip what as well 00:08:51.910 --> 00:08:53.160 align:start position:0% have a token grip what as well the<00:08:52.030> spirit<00:08:52.360> of<00:08:52.420> this<00:08:52.540> conference<00:08:52.930> which 00:08:53.160 --> 00:08:53.170 align:start position:0% the spirit of this conference which 00:08:53.170 --> 00:08:55.230 align:start position:0% the spirit of this conference which essentially<00:08:53.650> is<00:08:53.680> a<00:08:53.770> contract<00:08:54.310> triplet<00:08:54.670> with 00:08:55.230 --> 00:08:55.240 align:start position:0% essentially is a contract triplet with 00:08:55.240 --> 00:08:59.340 align:start position:0% essentially is a contract triplet with token<00:08:55.990> behaviors<00:08:56.470> exposed<00:08:57.130> as<00:08:57.310> well<00:08:57.990> and<00:08:58.990> it 00:08:59.340 --> 00:08:59.350 align:start position:0% token behaviors exposed as well and it 00:08:59.350 --> 00:09:01.580 align:start position:0% token behaviors exposed as well and it allows<00:08:59.650> you<00:08:59.830> to<00:08:59.860> create<00:09:00.250> these<00:09:00.850> types<00:09:01.120> of 00:09:01.580 --> 00:09:01.590 align:start position:0% allows you to create these types of 00:09:01.590 --> 00:09:04.170 align:start position:0% allows you to create these types of scenarios<00:09:02.590> so<00:09:03.160> the<00:09:03.340> toca<00:09:03.580> Chrome<00:09:03.820> for<00:09:04.090> example 00:09:04.170 --> 00:09:04.180 align:start position:0% scenarios so the toca Chrome for example 00:09:04.180 --> 00:09:06.390 align:start position:0% scenarios so the toca Chrome for example is<00:09:04.570> very<00:09:04.720> interesting<00:09:05.200> if<00:09:05.740> you<00:09:06.100> create<00:09:06.370> a 00:09:06.390 --> 00:09:06.400 align:start position:0% is very interesting if you create a 00:09:06.400 --> 00:09:07.800 align:start position:0% is very interesting if you create a token<00:09:07.000> the<00:09:07.450> it<00:09:07.540> actually 00:09:07.800 --> 00:09:07.810 align:start position:0% token the it actually 00:09:07.810 --> 00:09:11.610 align:start position:0% token the it actually controls<00:09:08.230> all<00:09:08.830> the<00:09:09.600> ERC<00:09:10.600> twenty<00:09:11.110> sort<00:09:11.560> of 00:09:11.610 --> 00:09:11.620 align:start position:0% controls all the ERC twenty sort of 00:09:11.620 --> 00:09:15.030 align:start position:0% controls all the ERC twenty sort of functions<00:09:12.010> so<00:09:12.790> the<00:09:13.120> the<00:09:14.020> issue<00:09:14.200> the<00:09:14.560> transfer 00:09:15.030 --> 00:09:15.040 align:start position:0% functions so the the issue the transfer 00:09:15.040 --> 00:09:20.160 align:start position:0% functions so the the issue the transfer the<00:09:15.280> burn<00:09:16.950> the<00:09:17.950> menteng<00:09:18.310> all<00:09:18.610> that<00:09:18.880> stuff<00:09:19.170> it's 00:09:20.160 --> 00:09:20.170 align:start position:0% the burn the menteng all that stuff it's 00:09:20.170 --> 00:09:21.780 align:start position:0% the burn the menteng all that stuff it's controlled<00:09:20.860> through<00:09:21.010> the<00:09:21.430> in<00:09:21.460> itself 00:09:21.780 --> 00:09:21.790 align:start position:0% controlled through the in itself 00:09:21.790 --> 00:09:24.630 align:start position:0% controlled through the in itself but<00:09:22.510> then<00:09:22.630> I<00:09:22.720> can<00:09:22.870> extend<00:09:23.290> the<00:09:23.560> behavior<00:09:24.040> so<00:09:24.610> I 00:09:24.630 --> 00:09:24.640 align:start position:0% but then I can extend the behavior so I 00:09:24.640 --> 00:09:27.450 align:start position:0% but then I can extend the behavior so I can<00:09:24.850> add<00:09:25.060> behavior<00:09:25.620> for<00:09:26.620> my<00:09:26.800> token<00:09:27.190> and<00:09:27.280> off 00:09:27.450 --> 00:09:27.460 align:start position:0% can add behavior for my token and off 00:09:27.460 --> 00:09:30.450 align:start position:0% can add behavior for my token and off chain<00:09:27.760> and<00:09:28.690> that<00:09:28.810> can<00:09:28.930> also<00:09:29.080> assume<00:09:29.560> the 00:09:30.450 --> 00:09:30.460 align:start position:0% chain and that can also assume the 00:09:30.460 --> 00:09:33.360 align:start position:0% chain and that can also assume the identity<00:09:30.760> and<00:09:31.240> use<00:09:31.810> the<00:09:32.560> identity<00:09:32.860> of<00:09:33.130> the 00:09:33.360 --> 00:09:33.370 align:start position:0% identity and use the identity of the 00:09:33.370 --> 00:09:35.640 align:start position:0% identity and use the identity of the person<00:09:33.850> that<00:09:34.120> has<00:09:34.240> a<00:09:34.270> balance<00:09:34.780> for<00:09:35.170> that<00:09:35.200> token 00:09:35.640 --> 00:09:35.650 align:start position:0% person that has a balance for that token 00:09:35.650 --> 00:09:37.050 align:start position:0% person that has a balance for that token so<00:09:35.770> you<00:09:35.860> do<00:09:35.950> some<00:09:36.130> very<00:09:36.400> interesting<00:09:36.490> things 00:09:37.050 --> 00:09:37.060 align:start position:0% so you do some very interesting things 00:09:37.060 --> 00:09:40.380 align:start position:0% so you do some very interesting things with<00:09:37.210> this<00:09:37.300> platform<00:09:38.700> as<00:09:39.700> well<00:09:40.060> so<00:09:40.210> we're<00:09:40.330> not 00:09:40.380 --> 00:09:40.390 align:start position:0% with this platform as well so we're not 00:09:40.390 --> 00:09:41.670 align:start position:0% with this platform as well so we're not really<00:09:40.570> sure<00:09:40.630> what<00:09:40.870> we're<00:09:41.140> customers<00:09:41.530> gonna 00:09:41.670 --> 00:09:41.680 align:start position:0% really sure what we're customers gonna 00:09:41.680 --> 00:09:42.870 align:start position:0% really sure what we're customers gonna do<00:09:41.890> but<00:09:42.040> the<00:09:42.130> interesting<00:09:42.370> thing<00:09:42.460> is<00:09:42.640> you<00:09:42.760> can 00:09:42.870 --> 00:09:42.880 align:start position:0% do but the interesting thing is you can 00:09:42.880 --> 00:09:45.030 align:start position:0% do but the interesting thing is you can do<00:09:43.210> attack<00:09:43.360> Riblet<00:09:43.770> go<00:09:44.770> up<00:09:44.830> on<00:09:44.920> the 00:09:45.030 --> 00:09:45.040 align:start position:0% do attack Riblet go up on the 00:09:45.040 --> 00:09:48.240 align:start position:0% do attack Riblet go up on the outside<00:09:45.430> and<00:09:45.760> then<00:09:46.120> also<00:09:46.450> you<00:09:46.720> can<00:09:47.250> create 00:09:48.240 --> 00:09:48.250 align:start position:0% outside and then also you can create 00:09:48.250 --> 00:09:49.740 align:start position:0% outside and then also you can create your<00:09:48.520> proxy<00:09:48.880> you<00:09:48.970> can<00:09:49.090> have<00:09:49.270> it<00:09:49.390> monitor 00:09:49.740 --> 00:09:49.750 align:start position:0% your proxy you can have it monitor 00:09:49.750 --> 00:09:51.330 align:start position:0% your proxy you can have it monitor events<00:09:50.230> of<00:09:50.320> the<00:09:50.410> local<00:09:50.680> watch<00:09:50.830> chain<00:09:51.070> and 00:09:51.330 --> 00:09:51.340 align:start position:0% events of the local watch chain and 00:09:51.340 --> 00:09:53.760 align:start position:0% events of the local watch chain and react<00:09:51.940> to<00:09:52.150> them<00:09:52.300> as<00:09:53.020> well<00:09:53.230> in<00:09:53.350> the<00:09:53.440> outside 00:09:53.760 --> 00:09:53.770 align:start position:0% react to them as well in the outside 00:09:53.770 --> 00:09:58.290 align:start position:0% react to them as well in the outside world<00:09:55.320> so<00:09:56.320> how<00:09:57.010> do<00:09:57.070> you<00:09:57.190> get<00:09:57.310> started<00:09:57.520> a<00:09:57.910> lot<00:09:58.270> of 00:09:58.290 --> 00:09:58.300 align:start position:0% world so how do you get started a lot of 00:09:58.300 --> 00:09:59.790 align:start position:0% world so how do you get started a lot of people<00:09:58.390> asked<00:09:59.260> we've<00:09:59.380> been<00:09:59.500> talking<00:09:59.770> about 00:09:59.790 --> 00:09:59.800 align:start position:0% people asked we've been talking about 00:09:59.800 --> 00:10:00.630 align:start position:0% people asked we've been talking about this<00:09:59.980> for<00:10:00.190> some<00:10:00.220> time 00:10:00.630 --> 00:10:00.640 align:start position:0% this for some time 00:10:00.640 --> 00:10:02.790 align:start position:0% this for some time when<00:10:01.270> do<00:10:01.360> I<00:10:01.390> get<00:10:01.480> to<00:10:01.600> see<00:10:01.780> code<00:10:02.080> when<00:10:02.380> do<00:10:02.470> i<00:10:02.500> when 00:10:02.790 --> 00:10:02.800 align:start position:0% when do I get to see code when do i when 00:10:02.800 --> 00:10:05.610 align:start position:0% when do I get to see code when do i when can<00:10:02.920> i<00:10:02.950> play<00:10:03.250> with<00:10:03.280> this<00:10:03.610> well<00:10:04.420> we<00:10:05.290> tried<00:10:05.530> to 00:10:05.610 --> 00:10:05.620 align:start position:0% can i play with this well we tried to 00:10:05.620 --> 00:10:07.230 align:start position:0% can i play with this well we tried to get<00:10:05.740> this<00:10:05.890> done<00:10:06.130> before<00:10:06.430> the<00:10:06.760> show<00:10:07.030> we're 00:10:07.230 --> 00:10:07.240 align:start position:0% get this done before the show we're 00:10:07.240 --> 00:10:08.340 align:start position:0% get this done before the show we're gonna<00:10:07.330> come<00:10:07.540> out<00:10:07.630> and<00:10:07.720> say<00:10:07.810> hey<00:10:07.930> it's<00:10:08.170> open 00:10:08.340 --> 00:10:08.350 align:start position:0% gonna come out and say hey it's open 00:10:08.350 --> 00:10:10.290 align:start position:0% gonna come out and say hey it's open here<00:10:08.680> go<00:10:08.830> run<00:10:09.040> this<00:10:09.250> go<00:10:09.460> this<00:10:09.490> URL<00:10:09.910> and<00:10:10.090> you<00:10:10.150> can 00:10:10.290 --> 00:10:10.300 align:start position:0% here go run this go this URL and you can 00:10:10.300 --> 00:10:12.390 align:start position:0% here go run this go this URL and you can get<00:10:10.960> a<00:10:10.990> test<00:10:11.290> drive<00:10:11.530> but<00:10:11.740> we<00:10:11.800> couldn't<00:10:12.100> pull 00:10:12.390 --> 00:10:12.400 align:start position:0% get a test drive but we couldn't pull 00:10:12.400 --> 00:10:15.540 align:start position:0% get a test drive but we couldn't pull that<00:10:12.520> off<00:10:12.700> in<00:10:12.730> time<00:10:13.530> but<00:10:14.530> as<00:10:14.620> soon<00:10:14.860> within<00:10:15.340> the 00:10:15.540 --> 00:10:15.550 align:start position:0% that off in time but as soon within the 00:10:15.550 --> 00:10:16.050 align:start position:0% that off in time but as soon within the next 00:10:16.050 --> 00:10:16.060 align:start position:0% next 00:10:16.060 --> 00:10:19.260 align:start position:0% next hope<00:10:16.620> two<00:10:17.620> weeks<00:10:17.860> we'll<00:10:18.520> be<00:10:18.550> able<00:10:18.790> to<00:10:18.880> have<00:10:19.060> an 00:10:19.260 --> 00:10:19.270 align:start position:0% hope two weeks we'll be able to have an 00:10:19.270 --> 00:10:21.030 align:start position:0% hope two weeks we'll be able to have an environment<00:10:19.870> where<00:10:20.260> you<00:10:20.350> can<00:10:20.380> go<00:10:20.650> out<00:10:20.800> and<00:10:20.830> do 00:10:21.030 --> 00:10:21.040 align:start position:0% environment where you can go out and do 00:10:21.040 --> 00:10:22.410 align:start position:0% environment where you can go out and do a<00:10:21.070> test<00:10:21.400> drive<00:10:21.610> where<00:10:21.850> you<00:10:21.910> couldn't<00:10:22.090> stand<00:10:22.300> up 00:10:22.410 --> 00:10:22.420 align:start position:0% a test drive where you couldn't stand up 00:10:22.420 --> 00:10:25.500 align:start position:0% a test drive where you couldn't stand up this<00:10:22.540> environment<00:10:23.110> and<00:10:23.260> you<00:10:23.800> can<00:10:23.950> build<00:10:24.510> an 00:10:25.500 --> 00:10:25.510 align:start position:0% this environment and you can build an 00:10:25.510 --> 00:10:27.060 align:start position:0% this environment and you can build an enterprise<00:10:25.750> smart<00:10:26.140> contract<00:10:26.620> and 00:10:27.060 --> 00:10:27.070 align:start position:0% enterprise smart contract and 00:10:27.070 --> 00:10:30.240 align:start position:0% enterprise smart contract and 'its<00:10:27.360> from<00:10:28.360> scratch<00:10:28.660> to<00:10:29.200> start<00:10:29.620> learning<00:10:29.800> and 00:10:30.240 --> 00:10:30.250 align:start position:0% 'its from scratch to start learning and 00:10:30.250 --> 00:10:32.100 align:start position:0% 'its from scratch to start learning and this<00:10:31.000> platform<00:10:31.240> is<00:10:31.450> currently<00:10:31.750> and<00:10:31.930> what<00:10:32.020> we 00:10:32.100 --> 00:10:32.110 align:start position:0% this platform is currently and what we 00:10:32.110 --> 00:10:34.050 align:start position:0% this platform is currently and what we call<00:10:32.260> early<00:10:32.500> adopter<00:10:33.040> or<00:10:33.460> private<00:10:33.820> early 00:10:34.050 --> 00:10:34.060 align:start position:0% call early adopter or private early 00:10:34.060 --> 00:10:35.700 align:start position:0% call early adopter or private early adopter<00:10:34.420> preview<00:10:34.780> private<00:10:35.230> preview<00:10:35.560> which 00:10:35.700 --> 00:10:35.710 align:start position:0% adopter preview private preview which 00:10:35.710 --> 00:10:37.650 align:start position:0% adopter preview private preview which we're<00:10:35.920> going<00:10:36.730> into<00:10:36.850> a<00:10:36.970> regular<00:10:37.270> cadence<00:10:37.450> I'll 00:10:37.650 --> 00:10:37.660 align:start position:0% we're going into a regular cadence I'll 00:10:37.660 --> 00:10:39.780 align:start position:0% we're going into a regular cadence I'll talk<00:10:37.810> about<00:10:37.990> that<00:10:38.140> in<00:10:38.350> a<00:10:38.650> little<00:10:38.770> bit<00:10:39.010> but<00:10:39.700> if 00:10:39.780 --> 00:10:39.790 align:start position:0% talk about that in a little bit but if 00:10:39.790 --> 00:10:41.130 align:start position:0% talk about that in a little bit but if you're<00:10:39.940> building<00:10:40.090> these<00:10:40.360> things<00:10:40.600> essentially 00:10:41.130 --> 00:10:41.140 align:start position:0% you're building these things essentially 00:10:41.140 --> 00:10:43.050 align:start position:0% you're building these things essentially all<00:10:41.260> you<00:10:41.380> have<00:10:41.530> to<00:10:41.650> do<00:10:41.800> the<00:10:42.460> infrastructure<00:10:42.940> is 00:10:43.050 --> 00:10:43.060 align:start position:0% all you have to do the infrastructure is 00:10:43.060 --> 00:10:45.330 align:start position:0% all you have to do the infrastructure is built<00:10:43.210> for<00:10:43.570> you<00:10:43.750> and<00:10:43.780> abstracted<00:10:44.500> from<00:10:44.860> me<00:10:45.010> so 00:10:45.330 --> 00:10:45.340 align:start position:0% built for you and abstracted from me so 00:10:45.340 --> 00:10:49.050 align:start position:0% built for you and abstracted from me so as<00:10:46.330> you<00:10:46.750> would<00:10:46.870> expect<00:10:46.960> you<00:10:47.830> simply<00:10:48.430> focus<00:10:48.760> on 00:10:49.050 --> 00:10:49.060 align:start position:0% as you would expect you simply focus on 00:10:49.060 --> 00:10:51.360 align:start position:0% as you would expect you simply focus on what<00:10:49.240> you're<00:10:49.360> trying<00:10:49.570> to<00:10:49.930> do<00:10:50.080> the<00:10:51.010> first<00:10:51.220> thing 00:10:51.360 --> 00:10:51.370 align:start position:0% what you're trying to do the first thing 00:10:51.370 --> 00:10:53.520 align:start position:0% what you're trying to do the first thing you<00:10:51.490> always<00:10:51.640> will<00:10:52.240> we'll<00:10:52.600> talk<00:10:52.810> about<00:10:52.960> us<00:10:53.230> you 00:10:53.520 --> 00:10:53.530 align:start position:0% you always will we'll talk about us you 00:10:53.530 --> 00:10:55.500 align:start position:0% you always will we'll talk about us you know<00:10:53.620> contract<00:10:54.160> first<00:10:54.370> development<00:10:55.180> so<00:10:55.420> you 00:10:55.500 --> 00:10:55.510 align:start position:0% know contract first development so you 00:10:55.510 --> 00:10:58.080 align:start position:0% know contract first development so you will<00:10:56.020> develop<00:10:56.350> your<00:10:56.470> message<00:10:56.800> types<00:10:57.130> so<00:10:58.030> you 00:10:58.080 --> 00:10:58.090 align:start position:0% will develop your message types so you 00:10:58.090 --> 00:10:59.580 align:start position:0% will develop your message types so you define<00:10:58.270> your<00:10:58.570> message<00:10:58.840> types<00:10:59.110> and<00:10:59.380> you<00:10:59.440> can 00:10:59.580 --> 00:10:59.590 align:start position:0% define your message types and you can 00:10:59.590 --> 00:11:01.680 align:start position:0% define your message types and you can pick<00:10:59.710> your<00:10:59.740> language<00:10:59.980> and<00:11:00.430> donors<00:11:00.850> job<00:11:01.570> and 00:11:01.680 --> 00:11:01.690 align:start position:0% pick your language and donors job and 00:11:01.690 --> 00:11:02.840 align:start position:0% pick your language and donors job and this<00:11:01.780> is<00:11:01.930> what<00:11:02.110> it<00:11:02.200> looks<00:11:02.380> like 00:11:02.840 --> 00:11:02.850 align:start position:0% this is what it looks like 00:11:02.850 --> 00:11:05.250 align:start position:0% this is what it looks like pretty<00:11:03.850> simple<00:11:04.060> getters<00:11:04.510> and<00:11:04.540> setters<00:11:04.720> or<00:11:05.200> the 00:11:05.250 --> 00:11:05.260 align:start position:0% pretty simple getters and setters or the 00:11:05.260 --> 00:11:05.550 align:start position:0% pretty simple getters and setters or the base 00:11:05.550 --> 00:11:05.560 align:start position:0% base 00:11:05.560 --> 00:11:08.790 align:start position:0% base properties<00:11:06.220> this<00:11:06.760> is<00:11:06.940> in<00:11:07.090> c-sharp<00:11:07.800> we're 00:11:08.790 --> 00:11:08.800 align:start position:0% properties this is in c-sharp we're 00:11:08.800 --> 00:11:10.440 align:start position:0% properties this is in c-sharp we're inheriting<00:11:09.250> this<00:11:09.550> is<00:11:09.700> the<00:11:09.820> token<00:11:10.000> Crippler 00:11:10.440 --> 00:11:10.450 align:start position:0% inheriting this is the token Crippler 00:11:10.450 --> 00:11:13.110 align:start position:0% inheriting this is the token Crippler inherits<00:11:11.440> from<00:11:11.470> the<00:11:11.650> base<00:11:11.770> token<00:11:12.220> and<00:11:12.460> then<00:11:13.000> it 00:11:13.110 --> 00:11:13.120 align:start position:0% inherits from the base token and then it 00:11:13.120 --> 00:11:15.330 align:start position:0% inherits from the base token and then it has<00:11:13.270> constructor<00:11:14.080> messages<00:11:14.529> create<00:11:14.950> token 00:11:15.330 --> 00:11:15.340 align:start position:0% has constructor messages create token 00:11:15.340 --> 00:11:17.070 align:start position:0% has constructor messages create token that<00:11:15.490> derives<00:11:15.970> from<00:11:16.210> the<00:11:16.570> base<00:11:16.720> token 00:11:17.070 --> 00:11:17.080 align:start position:0% that derives from the base token 00:11:17.080 --> 00:11:20.160 align:start position:0% that derives from the base token constructor<00:11:17.790> and<00:11:18.790> we<00:11:18.940> have<00:11:19.150> you<00:11:19.660> know<00:11:19.750> like 00:11:20.160 --> 00:11:20.170 align:start position:0% constructor and we have you know like 00:11:20.170 --> 00:11:23.430 align:start position:0% constructor and we have you know like return<00:11:20.529> types<00:11:20.890> now<00:11:21.490> here<00:11:21.730> you<00:11:21.820> can<00:11:21.940> see<00:11:22.440> others 00:11:23.430 --> 00:11:23.440 align:start position:0% return types now here you can see others 00:11:23.440 --> 00:11:25.620 align:start position:0% return types now here you can see others we<00:11:24.160> can<00:11:24.279> have<00:11:24.640> time<00:11:24.880> I'll<00:11:25.060> switch<00:11:25.270> over<00:11:25.420> and 00:11:25.620 --> 00:11:25.630 align:start position:0% we can have time I'll switch over and 00:11:25.630 --> 00:11:27.720 align:start position:0% we can have time I'll switch over and chase<00:11:25.810> them<00:11:25.990> some<00:11:26.620> more<00:11:26.770> of<00:11:26.830> the<00:11:26.890> code<00:11:27.100> but 00:11:27.720 --> 00:11:27.730 align:start position:0% chase them some more of the code but 00:11:27.730 --> 00:11:30.150 align:start position:0% chase them some more of the code but this<00:11:27.880> is<00:11:28.000> example<00:11:28.300> of<00:11:28.600> that<00:11:28.720> the<00:11:29.040> types<00:11:30.040> that 00:11:30.150 --> 00:11:30.160 align:start position:0% this is example of that the types that 00:11:30.160 --> 00:11:33.930 align:start position:0% this is example of that the types that you'll<00:11:30.370> do<00:11:30.810> see<00:11:31.810> really<00:11:32.380> simple<00:11:32.920> types<00:11:33.730> that 00:11:33.930 --> 00:11:33.940 align:start position:0% you'll do see really simple types that 00:11:33.940 --> 00:11:37.860 align:start position:0% you'll do see really simple types that serialize<00:11:34.600> to<00:11:34.779> JSON<00:11:35.230> so<00:11:36.570> you<00:11:37.570> just<00:11:37.660> kind<00:11:37.810> of 00:11:37.860 --> 00:11:37.870 align:start position:0% serialize to JSON so you just kind of 00:11:37.870 --> 00:11:39.450 align:start position:0% serialize to JSON so you just kind of pay<00:11:37.990> attention<00:11:38.020> to<00:11:38.470> that<00:11:38.589> you<00:11:38.650> really<00:11:39.100> the 00:11:39.450 --> 00:11:39.460 align:start position:0% pay attention to that you really the 00:11:39.460 --> 00:11:40.920 align:start position:0% pay attention to that you really the framework<00:11:40.000> takes<00:11:40.180> care<00:11:40.450> of<00:11:40.480> this<00:11:40.630> they're<00:11:40.839> all 00:11:40.920 --> 00:11:40.930 align:start position:0% framework takes care of this they're all 00:11:40.930 --> 00:11:42.630 align:start position:0% framework takes care of this they're all at<00:11:40.990> serialization<00:11:41.620> for<00:11:41.800> you<00:11:41.890> so<00:11:42.070> standardized 00:11:42.630 --> 00:11:42.640 align:start position:0% at serialization for you so standardized 00:11:42.640 --> 00:11:44.280 align:start position:0% at serialization for you so standardized if<00:11:43.270> you<00:11:43.450> ever<00:11:43.570> done<00:11:43.810> cross-platform 00:11:44.280 --> 00:11:44.290 align:start position:0% if you ever done cross-platform 00:11:44.290 --> 00:11:46.710 align:start position:0% if you ever done cross-platform serialization<00:11:45.160> with<00:11:45.279> JSON<00:11:45.640> it's<00:11:46.210> not<00:11:46.540> as 00:11:46.710 --> 00:11:46.720 align:start position:0% serialization with JSON it's not as 00:11:46.720 --> 00:11:49.079 align:start position:0% serialization with JSON it's not as smooth<00:11:46.960> as<00:11:47.110> it<00:11:47.260> always<00:11:47.860> seems<00:11:48.490> it<00:11:48.730> should<00:11:48.940> be 00:11:49.079 --> 00:11:49.089 align:start position:0% smooth as it always seems it should be 00:11:49.089 --> 00:11:51.920 align:start position:0% smooth as it always seems it should be but<00:11:50.080> we've<00:11:50.410> taken<00:11:51.130> care<00:11:51.370> of<00:11:51.430> that<00:11:51.580> for<00:11:51.730> you 00:11:51.920 --> 00:11:51.930 align:start position:0% but we've taken care of that for you 00:11:51.930 --> 00:11:54.960 align:start position:0% but we've taken care of that for you next<00:11:52.930> you<00:11:53.170> then<00:11:53.350> write<00:11:53.560> your<00:11:53.770> equipment<00:11:54.700> code 00:11:54.960 --> 00:11:54.970 align:start position:0% next you then write your equipment code 00:11:54.970 --> 00:11:57.360 align:start position:0% next you then write your equipment code utility<00:11:55.480> contractor<00:11:56.110> token<00:11:56.529> depending<00:11:57.279> what 00:11:57.360 --> 00:11:57.370 align:start position:0% utility contractor token depending what 00:11:57.370 --> 00:11:59.550 align:start position:0% utility contractor token depending what you're<00:11:57.520> writing<00:11:57.730> you'll<00:11:58.060> derive<00:11:58.240> from<00:11:58.660> you 00:11:59.550 --> 00:11:59.560 align:start position:0% you're writing you'll derive from you 00:11:59.560 --> 00:12:02.940 align:start position:0% you're writing you'll derive from you always<00:11:59.860> drive<00:12:00.130> for<00:12:00.310> the<00:12:00.400> basic<00:12:00.670> Riblet<00:12:01.950> class 00:12:02.940 --> 00:12:02.950 align:start position:0% always drive for the basic Riblet class 00:12:02.950 --> 00:12:04.500 align:start position:0% always drive for the basic Riblet class here<00:12:03.279> so<00:12:03.430> this<00:12:03.520> is<00:12:03.670> the<00:12:03.760> typical<00:12:04.029> then<00:12:04.450> you 00:12:04.500 --> 00:12:04.510 align:start position:0% here so this is the typical then you 00:12:04.510 --> 00:12:06.269 align:start position:0% here so this is the typical then you implement<00:12:04.960> the<00:12:05.050> interfaces<00:12:05.650> there's<00:12:06.190> a 00:12:06.269 --> 00:12:06.279 align:start position:0% implement the interfaces there's a 00:12:06.279 --> 00:12:08.730 align:start position:0% implement the interfaces there's a contract<00:12:06.700> to<00:12:06.790> put<00:12:06.940> in<00:12:07.089> the<00:12:07.150> face<00:12:07.300> by<00:12:08.200> default<00:12:08.589> a 00:12:08.730 --> 00:12:08.740 align:start position:0% contract to put in the face by default a 00:12:08.740 --> 00:12:10.980 align:start position:0% contract to put in the face by default a token<00:12:09.370> it<00:12:09.460> is<00:12:09.640> a<00:12:10.180> contract<00:12:10.630> triplet 00:12:10.980 --> 00:12:10.990 align:start position:0% token it is a contract triplet 00:12:10.990 --> 00:12:14.220 align:start position:0% token it is a contract triplet you<00:12:11.200> cannot<00:12:12.040> be<00:12:12.250> a<00:12:12.940> token<00:12:14.050> without 00:12:14.220 --> 00:12:14.230 align:start position:0% you cannot be a token without 00:12:14.230 --> 00:12:16.790 align:start position:0% you cannot be a token without being<00:12:14.470> a<00:12:14.530> contract<00:12:14.980> and<00:12:15.280> that<00:12:15.430> has<00:12:15.730> to<00:12:15.880> do<00:12:16.030> with 00:12:16.790 --> 00:12:16.800 align:start position:0% being a contract and that has to do with 00:12:16.800 --> 00:12:19.770 align:start position:0% being a contract and that has to do with the<00:12:17.800> isolation<00:12:18.430> level<00:12:18.490> that<00:12:19.150> the<00:12:19.330> code<00:12:19.540> runs 00:12:19.770 --> 00:12:19.780 align:start position:0% the isolation level that the code runs 00:12:19.780 --> 00:12:22.200 align:start position:0% the isolation level that the code runs in<00:12:20.070> whereas<00:12:21.070> a<00:12:21.160> utility<00:12:21.820> it<00:12:21.880> can<00:12:22.060> be 00:12:22.200 --> 00:12:22.210 align:start position:0% in whereas a utility it can be 00:12:22.210 --> 00:12:24.180 align:start position:0% in whereas a utility it can be multi-tenant<00:12:23.020> so<00:12:23.530> I<00:12:23.560> can<00:12:23.770> have<00:12:23.920> multiple 00:12:24.180 --> 00:12:24.190 align:start position:0% multi-tenant so I can have multiple 00:12:24.190 --> 00:12:26.820 align:start position:0% multi-tenant so I can have multiple subscribers<00:12:24.940> to<00:12:25.330> an<00:12:25.450> oracle<00:12:25.810> type<00:12:26.200> service<00:12:26.589> a 00:12:26.820 --> 00:12:26.830 align:start position:0% subscribers to an oracle type service a 00:12:26.830 --> 00:12:28.650 align:start position:0% subscribers to an oracle type service a contract<00:12:27.880> can<00:12:27.970> only<00:12:28.120> have<00:12:28.330> one 00:12:28.650 --> 00:12:28.660 align:start position:0% contract can only have one 00:12:28.660 --> 00:12:30.450 align:start position:0% contract can only have one binding<00:12:29.620> and<00:12:29.800> what<00:12:29.890> we<00:12:30.100> called<00:12:30.339> us 00:12:30.450 --> 00:12:30.460 align:start position:0% binding and what we called us 00:12:30.460 --> 00:12:33.420 align:start position:0% binding and what we called us essentially<00:12:31.180> a<00:12:31.270> binding<00:12:31.720> each<00:12:32.230> instance<00:12:33.220> of 00:12:33.420 --> 00:12:33.430 align:start position:0% essentially a binding each instance of 00:12:33.430 --> 00:12:37.650 align:start position:0% essentially a binding each instance of that<00:12:33.610> same<00:12:35.280> binding<00:12:36.280> gets<00:12:36.490> a<00:12:36.670> new<00:12:36.820> instance<00:12:37.390> of 00:12:37.650 --> 00:12:37.660 align:start position:0% that same binding gets a new instance of 00:12:37.660 --> 00:12:39.090 align:start position:0% that same binding gets a new instance of a<00:12:38.320> that's<00:12:38.500> either<00:12:38.620> running<00:12:38.860> in<00:12:39.040> a 00:12:39.090 --> 00:12:39.100 align:start position:0% a that's either running in a 00:12:39.100 --> 00:12:41.400 align:start position:0% a that's either running in a full-on<00:12:39.310> cleaved<00:12:39.760> environment<00:12:40.330> or<00:12:40.630> a<00:12:40.810> partial 00:12:41.400 --> 00:12:41.410 align:start position:0% full-on cleaved environment or a partial 00:12:41.410 --> 00:12:43.440 align:start position:0% full-on cleaved environment or a partial on<00:12:41.650> cleaved<00:12:41.920> environment<00:12:42.430> with<00:12:42.940> Krypton 00:12:43.440 --> 00:12:43.450 align:start position:0% on cleaved environment with Krypton 00:12:43.450 --> 00:12:48.180 align:start position:0% on cleaved environment with Krypton delegate<00:12:44.730> so<00:12:46.290> crippled<00:12:47.290> at<00:12:47.350> basic 00:12:48.180 --> 00:12:48.190 align:start position:0% delegate so crippled at basic 00:12:48.190 --> 00:12:49.740 align:start position:0% delegate so crippled at basic constructors<00:12:48.700> this<00:12:48.880> is<00:12:48.970> where<00:12:49.150> we<00:12:49.240> construct 00:12:49.740 --> 00:12:49.750 align:start position:0% constructors this is where we construct 00:12:49.750 --> 00:12:53.670 align:start position:0% constructors this is where we construct its<00:12:49.900> API<00:12:52.390> it's<00:12:52.480> can<00:12:52.750> be<00:12:52.780> inspected<00:12:53.350> by 00:12:53.670 --> 00:12:53.680 align:start position:0% its API it's can be inspected by 00:12:53.680 --> 00:12:55.470 align:start position:0% its API it's can be inspected by simply<00:12:54.040> passing<00:12:54.190> a<00:12:54.520> real<00:12:54.700> simple<00:12:54.910> message<00:12:55.300> and 00:12:55.470 --> 00:12:55.480 align:start position:0% simply passing a real simple message and 00:12:55.480 --> 00:12:57.210 align:start position:0% simply passing a real simple message and the<00:12:55.600> framework<00:12:55.990> and<00:12:56.170> saying<00:12:56.410> tell<00:12:57.070> me<00:12:57.160> about 00:12:57.210 --> 00:12:57.220 align:start position:0% the framework and saying tell me about 00:12:57.220 --> 00:12:58.949 align:start position:0% the framework and saying tell me about the<00:12:57.640> it's<00:12:57.730> you<00:12:57.820> have<00:12:57.970> registered<00:12:58.480> and 00:12:58.949 --> 00:12:58.959 align:start position:0% the it's you have registered and 00:12:58.959 --> 00:13:00.780 align:start position:0% the it's you have registered and you<00:12:58.990> can<00:12:59.200> pick<00:12:59.350> one<00:12:59.770> let's<00:12:59.950> say<00:13:00.130> tell<00:13:00.730> me 00:13:00.780 --> 00:13:00.790 align:start position:0% you can pick one let's say tell me 00:13:00.790 --> 00:13:03.120 align:start position:0% you can pick one let's say tell me what<00:13:00.910> your<00:13:01.060> API<00:13:01.330> is<00:13:01.660> what<00:13:01.900> that<00:13:02.050> means<00:13:02.290> is<00:13:02.589> it's 00:13:03.120 --> 00:13:03.130 align:start position:0% what your API is what that means is it's 00:13:03.130 --> 00:13:04.530 align:start position:0% what your API is what that means is it's going<00:13:03.279> to<00:13:03.339> take<00:13:03.550> care<00:13:03.790> of<00:13:03.880> its<00:13:04.060> functions 00:13:04.530 --> 00:13:04.540 align:start position:0% going to take care of its functions 00:13:04.540 --> 00:13:07.050 align:start position:0% going to take care of its functions these<00:13:05.470> are<00:13:05.680> these<00:13:05.830> message<00:13:06.310> types<00:13:06.550> I<00:13:06.730> defined 00:13:07.050 --> 00:13:07.060 align:start position:0% these are these message types I defined 00:13:07.060 --> 00:13:09.690 align:start position:0% these are these message types I defined as<00:13:07.240> the<00:13:07.390> types<00:13:07.709> when<00:13:08.709> I<00:13:08.740> say<00:13:09.040> these<00:13:09.459> all 00:13:09.690 --> 00:13:09.700 align:start position:0% as the types when I say these all 00:13:09.700 --> 00:13:12.060 align:start position:0% as the types when I say these all serialize<00:13:10.330> automatically<00:13:11.170> to<00:13:11.350> JSON<00:13:11.770> so<00:13:11.950> when 00:13:12.060 --> 00:13:12.070 align:start position:0% serialize automatically to JSON so when 00:13:12.070 --> 00:13:13.590 align:start position:0% serialize automatically to JSON so when I<00:13:12.100> query<00:13:12.459> it<00:13:12.580> it's<00:13:12.700> gonna<00:13:12.820> serialize<00:13:13.420> all 00:13:13.590 --> 00:13:13.600 align:start position:0% I query it it's gonna serialize all 00:13:13.600 --> 00:13:15.540 align:start position:0% I query it it's gonna serialize all these<00:13:13.750> things<00:13:13.959> here<00:13:14.230> my<00:13:14.380> functions<00:13:14.830> with 00:13:15.540 --> 00:13:15.550 align:start position:0% these things here my functions with 00:13:15.550 --> 00:13:17.550 align:start position:0% these things here my functions with their<00:13:15.670> JSON<00:13:16.060> structure<00:13:16.390> and<00:13:16.750> here<00:13:17.170> are<00:13:17.380> my 00:13:17.550 --> 00:13:17.560 align:start position:0% their JSON structure and here are my 00:13:17.560 --> 00:13:19.400 align:start position:0% their JSON structure and here are my returns<00:13:17.890> with 00:13:19.400 --> 00:13:19.410 align:start position:0% returns with 00:13:19.410 --> 00:13:21.530 align:start position:0% returns with so<00:13:19.920> you<00:13:19.980> know<00:13:20.190> exactly<00:13:20.730> how<00:13:20.970> to<00:13:21.000> communicate 00:13:21.530 --> 00:13:21.540 align:start position:0% so you know exactly how to communicate 00:13:21.540 --> 00:13:22.790 align:start position:0% so you know exactly how to communicate with<00:13:21.690> it<00:13:21.840> so<00:13:21.960> you<00:13:22.080> can<00:13:22.230> construct<00:13:22.500> your<00:13:22.740> own 00:13:22.790 --> 00:13:22.800 align:start position:0% with it so you can construct your own 00:13:22.800 --> 00:13:25.340 align:start position:0% with it so you can construct your own libraries<00:13:23.490> or<00:13:23.790> we<00:13:24.420> can<00:13:24.570> provide<00:13:24.780> you<00:13:25.020> a<00:13:25.050> jar 00:13:25.340 --> 00:13:25.350 align:start position:0% libraries or we can provide you a jar 00:13:25.350 --> 00:13:27.710 align:start position:0% libraries or we can provide you a jar file<00:13:25.590> or<00:13:25.800> a<00:13:25.830> DLL<00:13:26.250> for<00:13:26.490> you<00:13:26.580> to<00:13:26.730> work<00:13:26.970> with<00:13:27.270> those 00:13:27.710 --> 00:13:27.720 align:start position:0% file or a DLL for you to work with those 00:13:27.720 --> 00:13:33.470 align:start position:0% file or a DLL for you to work with those types<00:13:28.400> very<00:13:29.400> simple<00:13:29.760> stuff<00:13:31.520> then<00:13:32.520> last<00:13:33.360> thing 00:13:33.470 --> 00:13:33.480 align:start position:0% types very simple stuff then last thing 00:13:33.480 --> 00:13:36.800 align:start position:0% types very simple stuff then last thing you<00:13:33.630> need<00:13:33.780> to<00:13:33.810> generate<00:13:34.080> your<00:13:34.350> proxy<00:13:34.740> so<00:13:35.810> this 00:13:36.800 --> 00:13:36.810 align:start position:0% you need to generate your proxy so this 00:13:36.810 --> 00:13:39.890 align:start position:0% you need to generate your proxy so this is<00:13:36.990> where<00:13:37.140> the<00:13:38.150> we're<00:13:39.150> tooling<00:13:39.510> comes<00:13:39.690> into 00:13:39.890 --> 00:13:39.900 align:start position:0% is where the we're tooling comes into 00:13:39.900 --> 00:13:41.630 align:start position:0% is where the we're tooling comes into play<00:13:40.080> so<00:13:40.710> we're<00:13:40.860> doing<00:13:40.950> a<00:13:41.100> lot<00:13:41.220> of<00:13:41.340> work<00:13:41.490> around 00:13:41.630 --> 00:13:41.640 align:start position:0% play so we're doing a lot of work around 00:13:41.640 --> 00:13:43.790 align:start position:0% play so we're doing a lot of work around the<00:13:41.850> tooling<00:13:42.240> so<00:13:42.390> we'll<00:13:42.540> generate<00:13:43.050> as<00:13:43.290> much<00:13:43.560> of 00:13:43.790 --> 00:13:43.800 align:start position:0% the tooling so we'll generate as much of 00:13:43.800 --> 00:13:47.270 align:start position:0% the tooling so we'll generate as much of the<00:13:44.040> proxy<00:13:45.030> as<00:13:45.150> possible<00:13:45.750> for<00:13:45.990> you<00:13:46.200> so<00:13:47.130> there's 00:13:47.270 --> 00:13:47.280 align:start position:0% the proxy as possible for you so there's 00:13:47.280 --> 00:13:51.350 align:start position:0% the proxy as possible for you so there's two<00:13:47.550> types<00:13:47.880> of<00:13:48.120> ways<00:13:48.330> to<00:13:48.630> generate<00:13:50.360> object 00:13:51.350 --> 00:13:51.360 align:start position:0% two types of ways to generate object 00:13:51.360 --> 00:13:52.760 align:start position:0% two types of ways to generate object models<00:13:51.630> that<00:13:51.780> get<00:13:51.900> some<00:13:52.140> sort<00:13:52.320> of<00:13:52.410> underlying 00:13:52.760 --> 00:13:52.770 align:start position:0% models that get some sort of underlying 00:13:52.770 --> 00:13:55.280 align:start position:0% models that get some sort of underlying data<00:13:53.370> structure<00:13:53.880> you<00:13:54.450> can<00:13:54.600> do<00:13:54.690> a<00:13:54.720> what<00:13:55.050> we<00:13:55.140> call 00:13:55.280 --> 00:13:55.290 align:start position:0% data structure you can do a what we call 00:13:55.290 --> 00:13:56.510 align:start position:0% data structure you can do a what we call data<00:13:55.500> first<00:13:55.830> that's<00:13:56.190> where<00:13:56.370> you've 00:13:56.510 --> 00:13:56.520 align:start position:0% data first that's where you've 00:13:56.520 --> 00:13:58.190 align:start position:0% data first that's where you've established<00:13:56.700> the<00:13:57.180> database<00:13:57.600> like<00:13:57.840> a<00:13:57.870> sequel 00:13:58.190 --> 00:13:58.200 align:start position:0% established the database like a sequel 00:13:58.200 --> 00:14:00.620 align:start position:0% established the database like a sequel database<00:13:58.530> or<00:13:58.770> whatever<00:13:58.860> or<00:13:59.610> solidity<00:14:00.210> in<00:14:00.450> this 00:14:00.620 --> 00:14:00.630 align:start position:0% database or whatever or solidity in this 00:14:00.630 --> 00:14:04.480 align:start position:0% database or whatever or solidity in this case<00:14:00.840> and<00:14:01.230> then<00:14:02.010> I<00:14:02.310> can<00:14:02.640> use<00:14:03.000> that<00:14:03.780> to<00:14:04.110> then 00:14:04.480 --> 00:14:04.490 align:start position:0% case and then I can use that to then 00:14:04.490 --> 00:14:07.400 align:start position:0% case and then I can use that to then create<00:14:05.490> a<00:14:05.610> proxy<00:14:06.120> from<00:14:06.330> that<00:14:06.930> structure<00:14:07.380> so 00:14:07.400 --> 00:14:07.410 align:start position:0% create a proxy from that structure so 00:14:07.410 --> 00:14:08.810 align:start position:0% create a proxy from that structure so meaning<00:14:07.770> I<00:14:07.830> already<00:14:08.070> have<00:14:08.220> my<00:14:08.370> solidity 00:14:08.810 --> 00:14:08.820 align:start position:0% meaning I already have my solidity 00:14:08.820 --> 00:14:12.430 align:start position:0% meaning I already have my solidity defined<00:14:09.810> I<00:14:10.020> can<00:14:10.200> then<00:14:10.350> generate<00:14:10.740> a<00:14:10.800> proxy<00:14:11.370> now 00:14:12.430 --> 00:14:12.440 align:start position:0% defined I can then generate a proxy now 00:14:12.440 --> 00:14:14.120 align:start position:0% defined I can then generate a proxy now usually<00:14:13.440> when<00:14:13.650> you're<00:14:13.800> writing<00:14:13.980> your 00:14:14.120 --> 00:14:14.130 align:start position:0% usually when you're writing your 00:14:14.130 --> 00:14:17.000 align:start position:0% usually when you're writing your solidity<00:14:14.550> for<00:14:15.350> enterprise<00:14:16.350> smart<00:14:16.560> contractor 00:14:17.000 --> 00:14:17.010 align:start position:0% solidity for enterprise smart contractor 00:14:17.010 --> 00:14:18.440 align:start position:0% solidity for enterprise smart contractor you<00:14:17.070> only<00:14:17.250> want<00:14:17.490> to<00:14:17.550> put<00:14:17.610> the<00:14:17.730> logic<00:14:18.120> down<00:14:18.270> them 00:14:18.440 --> 00:14:18.450 align:start position:0% you only want to put the logic down them 00:14:18.450 --> 00:14:19.970 align:start position:0% you only want to put the logic down them it<00:14:18.540> makes<00:14:18.750> sense<00:14:19.020> to<00:14:19.260> put<00:14:19.440> down<00:14:19.650> in<00:14:19.830> your 00:14:19.970 --> 00:14:19.980 align:start position:0% it makes sense to put down in your 00:14:19.980 --> 00:14:22.640 align:start position:0% it makes sense to put down in your enterprise<00:14:20.700> smart<00:14:20.970> card<00:14:21.360> excuse<00:14:21.780> me<00:14:21.900> in<00:14:22.410> your 00:14:22.640 --> 00:14:22.650 align:start position:0% enterprise smart card excuse me in your 00:14:22.650 --> 00:14:25.010 align:start position:0% enterprise smart card excuse me in your smart<00:14:22.890> contract<00:14:23.370> so<00:14:24.090> you<00:14:24.480> want<00:14:24.630> to<00:14:24.720> do<00:14:24.810> things 00:14:25.010 --> 00:14:25.020 align:start position:0% smart contract so you want to do things 00:14:25.020 --> 00:14:28.430 align:start position:0% smart contract so you want to do things that<00:14:25.200> that<00:14:25.560> if<00:14:26.550> you're<00:14:26.760> transitioning<00:14:27.660> assets 00:14:28.430 --> 00:14:28.440 align:start position:0% that that if you're transitioning assets 00:14:28.440 --> 00:14:30.050 align:start position:0% that that if you're transitioning assets or<00:14:28.650> changing<00:14:29.040> ownership<00:14:29.190> for<00:14:29.550> assets<00:14:29.940> that 00:14:30.050 --> 00:14:30.060 align:start position:0% or changing ownership for assets that 00:14:30.060 --> 00:14:33.170 align:start position:0% or changing ownership for assets that are<00:14:30.210> Providence<00:14:30.690> on<00:14:30.900> that<00:14:31.320> blockchain<00:14:32.180> then 00:14:33.170 --> 00:14:33.180 align:start position:0% are Providence on that blockchain then 00:14:33.180 --> 00:14:35.000 align:start position:0% are Providence on that blockchain then you<00:14:33.330> want<00:14:33.510> to<00:14:33.600> do<00:14:33.750> that<00:14:34.020> and<00:14:34.290> perform<00:14:34.860> that 00:14:35.000 --> 00:14:35.010 align:start position:0% you want to do that and perform that 00:14:35.010 --> 00:14:38.050 align:start position:0% you want to do that and perform that logic<00:14:35.370> on<00:14:35.550> the<00:14:35.820> in<00:14:36.330> your<00:14:36.480> solidity<00:14:36.840> code 00:14:38.050 --> 00:14:38.060 align:start position:0% logic on the in your solidity code 00:14:38.060 --> 00:14:40.220 align:start position:0% logic on the in your solidity code there's<00:14:39.060> lots<00:14:39.240> of<00:14:39.330> nuances<00:14:39.840> there<00:14:39.990> but<00:14:40.140> it 00:14:40.220 --> 00:14:40.230 align:start position:0% there's lots of nuances there but it 00:14:40.230 --> 00:14:42.730 align:start position:0% there's lots of nuances there but it sensible<00:14:40.590> will<00:14:40.890> generate<00:14:41.190> the<00:14:41.310> proxy<00:14:41.700> first 00:14:42.730 --> 00:14:42.740 align:start position:0% sensible will generate the proxy first 00:14:42.740 --> 00:14:44.990 align:start position:0% sensible will generate the proxy first code<00:14:43.740> first<00:14:44.010> is<00:14:44.190> where<00:14:44.310> you<00:14:44.520> have<00:14:44.670> the<00:14:44.790> type 00:14:44.990 --> 00:14:45.000 align:start position:0% code first is where you have the type 00:14:45.000 --> 00:14:46.750 align:start position:0% code first is where you have the type system<00:14:45.240> that<00:14:45.540> you<00:14:45.600> defined<00:14:45.960> and<00:14:46.170> will<00:14:46.290> then 00:14:46.750 --> 00:14:46.760 align:start position:0% system that you defined and will then 00:14:46.760 --> 00:14:50.660 align:start position:0% system that you defined and will then create<00:14:47.760> the<00:14:47.880> solidity<00:14:48.240> for<00:14:48.540> you<00:14:48.920> but<00:14:49.920> you<00:14:50.550> do 00:14:50.660 --> 00:14:50.670 align:start position:0% create the solidity for you but you do 00:14:50.670 --> 00:14:53.090 align:start position:0% create the solidity for you but you do some<00:14:50.880> basic<00:14:51.030> customizations<00:14:51.960> these<00:14:52.230> proxies 00:14:53.090 --> 00:14:53.100 align:start position:0% some basic customizations these proxies 00:14:53.100 --> 00:14:54.620 align:start position:0% some basic customizations these proxies can<00:14:53.280> be<00:14:53.370> written<00:14:53.520> in<00:14:53.700> any<00:14:53.820> platform<00:14:54.090> as<00:14:54.450> well 00:14:54.620 --> 00:14:54.630 align:start position:0% can be written in any platform as well 00:14:54.630 --> 00:14:57.920 align:start position:0% can be written in any platform as well this<00:14:55.380> is<00:14:55.440> using<00:14:55.770> the<00:14:56.070> theorem<00:14:56.340> so<00:14:56.790> the<00:14:57.000> theorem 00:14:57.920 --> 00:14:57.930 align:start position:0% this is using the theorem so the theorem 00:14:57.930 --> 00:15:02.420 align:start position:0% this is using the theorem so the theorem team<00:14:58.190> the<00:14:59.190> guys<00:14:59.340> that<00:14:59.490> consensus<00:15:00.030> are<00:15:01.400> doing<00:15:02.400> a 00:15:02.420 --> 00:15:02.430 align:start position:0% team the guys that consensus are doing a 00:15:02.430 --> 00:15:05.300 align:start position:0% team the guys that consensus are doing a lot<00:15:02.550> of<00:15:02.670> work<00:15:02.930> for<00:15:03.930> generating<00:15:04.560> the<00:15:04.770> proxies 00:15:05.300 --> 00:15:05.310 align:start position:0% lot of work for generating the proxies 00:15:05.310 --> 00:15:08.510 align:start position:0% lot of work for generating the proxies for<00:15:05.640> this<00:15:06.600> platform<00:15:07.050> and<00:15:07.200> we<00:15:07.260> expect<00:15:07.680> each<00:15:08.280> of 00:15:08.510 --> 00:15:08.520 align:start position:0% for this platform and we expect each of 00:15:08.520 --> 00:15:10.579 align:start position:0% for this platform and we expect each of the<00:15:08.640> major<00:15:08.790> platform<00:15:09.600> providers<00:15:09.990> and<00:15:10.200> anyone 00:15:10.579 --> 00:15:10.589 align:start position:0% the major platform providers and anyone 00:15:10.589 --> 00:15:12.140 align:start position:0% the major platform providers and anyone will<00:15:10.920> be<00:15:11.040> able<00:15:11.070> to<00:15:11.460> take<00:15:11.670> the<00:15:11.790> standard 00:15:12.140 --> 00:15:12.150 align:start position:0% will be able to take the standard 00:15:12.150 --> 00:15:14.180 align:start position:0% will be able to take the standard interface<00:15:12.420> which<00:15:12.780> has<00:15:12.810> an<00:15:13.440> initialize 00:15:14.180 --> 00:15:14.190 align:start position:0% interface which has an initialize 00:15:14.190 --> 00:15:17.090 align:start position:0% interface which has an initialize function<00:15:14.430> and<00:15:15.140> execute<00:15:16.140> async<00:15:16.620> function 00:15:17.090 --> 00:15:17.100 align:start position:0% function and execute async function 00:15:17.100 --> 00:15:20.060 align:start position:0% function and execute async function that's<00:15:17.280> it<00:15:18.020> and<00:15:19.020> you<00:15:19.230> can<00:15:19.380> plug<00:15:19.589> it<00:15:19.710> into<00:15:19.860> the 00:15:20.060 --> 00:15:20.070 align:start position:0% that's it and you can plug it into the 00:15:20.070 --> 00:15:24.050 align:start position:0% that's it and you can plug it into the router<00:15:20.220> it<00:15:20.460> just<00:15:20.790> works<00:15:21.980> so<00:15:22.980> again<00:15:23.760> today 00:15:24.050 --> 00:15:24.060 align:start position:0% router it just works so again today 00:15:24.060 --> 00:15:26.300 align:start position:0% router it just works so again today we're<00:15:24.330> supporting<00:15:24.600> net<00:15:25.050> JVM<00:15:25.740> and<00:15:25.920> native 00:15:26.300 --> 00:15:26.310 align:start position:0% we're supporting net JVM and native 00:15:26.310 --> 00:15:28.130 align:start position:0% we're supporting net JVM and native we'll<00:15:26.580> listen<00:15:27.150> to<00:15:27.300> our<00:15:27.390> customers<00:15:27.540> if<00:15:28.050> you 00:15:28.130 --> 00:15:28.140 align:start position:0% we'll listen to our customers if you 00:15:28.140 --> 00:15:29.390 align:start position:0% we'll listen to our customers if you have<00:15:28.290> a<00:15:28.320> particular<00:15:28.800> one<00:15:28.980> time<00:15:29.190> you're 00:15:29.390 --> 00:15:29.400 align:start position:0% have a particular one time you're 00:15:29.400 --> 00:15:30.450 align:start position:0% have a particular one time you're interested<00:15:29.730> in<00:15:29.850> there's<00:15:30.089> enough 00:15:30.450 --> 00:15:30.460 align:start position:0% interested in there's enough 00:15:30.460 --> 00:15:32.460 align:start position:0% interested in there's enough and<00:15:30.580> we'll<00:15:31.180> do<00:15:31.330> the<00:15:31.450> workhorse<00:15:31.840> it'll<00:15:32.050> be<00:15:32.110> open 00:15:32.460 --> 00:15:32.470 align:start position:0% and we'll do the workhorse it'll be open 00:15:32.470 --> 00:15:34.530 align:start position:0% and we'll do the workhorse it'll be open so<00:15:32.650> that<00:15:32.680> you<00:15:32.950> will<00:15:33.070> be<00:15:33.220> able<00:15:33.430> to<00:15:33.580> create<00:15:34.450> your 00:15:34.530 --> 00:15:34.540 align:start position:0% so that you will be able to create your 00:15:34.540 --> 00:15:36.180 align:start position:0% so that you will be able to create your own<00:15:34.720> and<00:15:34.990> port<00:15:35.230> over<00:15:35.320> there<00:15:35.560> we're<00:15:35.950> gonna<00:15:36.040> do 00:15:36.180 --> 00:15:36.190 align:start position:0% own and port over there we're gonna do 00:15:36.190 --> 00:15:37.890 align:start position:0% own and port over there we're gonna do rich<00:15:36.340> tool<00:15:36.640> in<00:15:36.910> Visual<00:15:37.180> Studio<00:15:37.270> Visual<00:15:37.840> Studio 00:15:37.890 --> 00:15:37.900 align:start position:0% rich tool in Visual Studio Visual Studio 00:15:37.900 --> 00:15:40.860 align:start position:0% rich tool in Visual Studio Visual Studio code<00:15:38.350> as<00:15:38.740> well<00:15:39.460> will<00:15:39.760> you'll<00:15:40.240> see<00:15:40.480> that<00:15:40.630> and 00:15:40.860 --> 00:15:40.870 align:start position:0% code as well will you'll see that and 00:15:40.870 --> 00:15:42.960 align:start position:0% code as well will you'll see that and the<00:15:41.020> test-drive<00:15:42.010> when<00:15:42.400> you<00:15:42.490> start<00:15:42.730> to<00:15:42.820> play 00:15:42.960 --> 00:15:42.970 align:start position:0% the test-drive when you start to play 00:15:42.970 --> 00:15:46.680 align:start position:0% the test-drive when you start to play with<00:15:43.030> it<00:15:43.180> in<00:15:43.360> a<00:15:43.420> couple<00:15:43.660> weeks<00:15:43.830> so<00:15:45.510> follow<00:15:46.510> ups 00:15:46.680 --> 00:15:46.690 align:start position:0% with it in a couple weeks so follow ups 00:15:46.690 --> 00:15:48.120 align:start position:0% with it in a couple weeks so follow ups I'm<00:15:46.930> out<00:15:47.200> of<00:15:47.230> time<00:15:47.470> here<00:15:47.650> come<00:15:47.890> by<00:15:48.010> our<00:15:48.100> booth 00:15:48.120 --> 00:15:48.130 align:start position:0% I'm out of time here come by our booth 00:15:48.130 --> 00:15:50.220 align:start position:0% I'm out of time here come by our booth we're<00:15:48.520> just<00:15:48.640> outside<00:15:48.790> the<00:15:49.090> door<00:15:49.210> here<00:15:49.480> well 00:15:50.220 --> 00:15:50.230 align:start position:0% we're just outside the door here well 00:15:50.230 --> 00:15:52.380 align:start position:0% we're just outside the door here well doing<00:15:50.590> demos<00:15:50.950> you<00:15:51.160> can<00:15:51.310> go<00:15:51.430> more<00:15:52.000> in<00:15:52.060> depth<00:15:52.240> in 00:15:52.380 --> 00:15:52.390 align:start position:0% doing demos you can go more in depth in 00:15:52.390 --> 00:15:54.210 align:start position:0% doing demos you can go more in depth in code<00:15:52.600> you<00:15:52.900> get<00:15:52.990> hands-on<00:15:53.440> the<00:15:53.620> hands-on<00:15:53.950> labs 00:15:54.210 --> 00:15:54.220 align:start position:0% code you get hands-on the hands-on labs 00:15:54.220 --> 00:15:56.190 align:start position:0% code you get hands-on the hands-on labs actually<00:15:54.670> see<00:15:54.760> what<00:15:54.880> it<00:15:54.970> looks<00:15:55.090> like 00:15:56.190 --> 00:15:56.200 align:start position:0% actually see what it looks like 00:15:56.200 --> 00:15:58.200 align:start position:0% actually see what it looks like watch<00:15:56.740> for<00:15:56.920> the<00:15:57.070> the<00:15:57.370> test-drive<00:15:57.670> coming<00:15:58.120> out 00:15:58.200 --> 00:15:58.210 align:start position:0% watch for the the test-drive coming out 00:15:58.210 --> 00:15:59.610 align:start position:0% watch for the the test-drive coming out in<00:15:58.300> a<00:15:58.330> couple<00:15:58.450> of<00:15:58.570> weeks<00:15:58.720> they<00:15:59.350> don't<00:15:59.530> include 00:15:59.610 --> 00:15:59.620 align:start position:0% in a couple of weeks they don't include 00:15:59.620 --> 00:16:02.910 align:start position:0% in a couple of weeks they don't include the<00:16:00.100> hands-on<00:16:00.400> labs<00:16:00.670> the<00:16:01.450> extensions<00:16:02.020> and<00:16:02.410> the 00:16:02.910 --> 00:16:02.920 align:start position:0% the hands-on labs the extensions and the 00:16:02.920 --> 00:16:05.010 align:start position:0% the hands-on labs the extensions and the sample<00:16:03.280> source<00:16:03.490> will<00:16:03.700> be<00:16:03.730> released<00:16:04.090> at<00:16:04.450> the 00:16:05.010 --> 00:16:05.020 align:start position:0% sample source will be released at the 00:16:05.020 --> 00:16:07.470 align:start position:0% sample source will be released at the same<00:16:05.230> time<00:16:05.470> so<00:16:05.650> you<00:16:05.740> if<00:16:06.220> you<00:16:06.280> if<00:16:07.150> your<00:16:07.300> code<00:16:07.450> is 00:16:07.470 --> 00:16:07.480 align:start position:0% same time so you if you if your code is 00:16:07.480 --> 00:16:08.940 align:start position:0% same time so you if you if your code is not<00:16:07.630> working<00:16:07.690> and<00:16:08.140> go<00:16:08.260> look<00:16:08.470> at<00:16:08.560> the<00:16:08.650> finished 00:16:08.940 --> 00:16:08.950 align:start position:0% not working and go look at the finished 00:16:08.950 --> 00:16:10.530 align:start position:0% not working and go look at the finished code<00:16:09.190> to<00:16:09.340> see<00:16:09.490> what's<00:16:09.670> what<00:16:10.270> you've<00:16:10.420> done 00:16:10.530 --> 00:16:10.540 align:start position:0% code to see what's what you've done 00:16:10.540 --> 00:16:13.140 align:start position:0% code to see what's what you've done wrong<00:16:10.780> and<00:16:11.050> then<00:16:11.710> I<00:16:11.980> will<00:16:12.400> be<00:16:12.550> transitioning 00:16:13.140 --> 00:16:13.150 align:start position:0% wrong and then I will be transitioning 00:16:13.150 --> 00:16:15.600 align:start position:0% wrong and then I will be transitioning from<00:16:13.270> public<00:16:13.840> from<00:16:14.440> private<00:16:14.800> preview<00:16:14.980> to<00:16:15.340> more 00:16:15.600 --> 00:16:15.610 align:start position:0% from public from private preview to more 00:16:15.610 --> 00:16:19.130 align:start position:0% from public from private preview to more public<00:16:15.940> previews<00:16:16.300> in<00:16:16.600> the<00:16:16.930> coming<00:16:17.230> months 00:16:19.130 --> 00:16:19.140 align:start position:0% public previews in the coming months 00:16:19.140 --> 00:16:22.110 align:start position:0% public previews in the coming months [Applause] 00:16:22.110 --> 00:16:22.120 align:start position:0% [Applause] 00:16:22.120 --> 00:16:29.700 align:start position:0% [Applause] [Music]