WEBVTT Kind: captions Language: en 00:00:01.070 --> 00:00:10.810 align:start position:0% [Applause] 00:00:10.810 --> 00:00:10.820 align:start position:0% 00:00:10.820 --> 00:00:13.730 align:start position:0% so<00:00:11.820> here's<00:00:12.240> talk<00:00:12.480> about<00:00:12.720> spark<00:00:13.320> on<00:00:13.440> Texas 00:00:13.730 --> 00:00:13.740 align:start position:0% so here's talk about spark on Texas 00:00:13.740 --> 00:00:16.720 align:start position:0% so here's talk about spark on Texas service<00:00:14.330> earlier<00:00:15.330> better<00:00:15.930> title<00:00:16.440> would<00:00:16.620> be 00:00:16.720 --> 00:00:16.730 align:start position:0% service earlier better title would be 00:00:16.730 --> 00:00:21.730 align:start position:0% service earlier better title would be smart<00:00:17.730> contract<00:00:18.150> might<00:00:18.570> remember<00:00:18.840> services 00:00:21.730 --> 00:00:21.740 align:start position:0% 00:00:21.740 --> 00:00:25.220 align:start position:0% so<00:00:22.740> my<00:00:22.980> name<00:00:23.160> is<00:00:23.189> broken<00:00:24.119> silica<00:00:24.540> I<00:00:24.689> speak 00:00:25.220 --> 00:00:25.230 align:start position:0% so my name is broken silica I speak 00:00:25.230 --> 00:00:26.570 align:start position:0% so my name is broken silica I speak basically<00:00:25.680> in<00:00:25.740> everywhere<00:00:26.070> on<00:00:26.160> the<00:00:26.250> internet 00:00:26.570 --> 00:00:26.580 align:start position:0% basically in everywhere on the internet 00:00:26.580 --> 00:00:29.480 align:start position:0% basically in everywhere on the internet I<00:00:27.330> am<00:00:27.930> the<00:00:28.080> co-founder<00:00:28.289> and<00:00:28.680> CTO<00:00:28.770> at<00:00:29.130> fission 00:00:29.480 --> 00:00:29.490 align:start position:0% I am the co-founder and CTO at fission 00:00:29.490 --> 00:00:31.670 align:start position:0% I am the co-founder and CTO at fission where<00:00:30.240> we're<00:00:30.390> building<00:00:30.510> a<00:00:30.960> such<00:00:31.650> a 00:00:31.670 --> 00:00:31.680 align:start position:0% where we're building a such a 00:00:31.680 --> 00:00:33.410 align:start position:0% where we're building a such a decentralized<00:00:32.400> firebase<00:00:32.760> with<00:00:32.940> user<00:00:33.150> control 00:00:33.410 --> 00:00:33.420 align:start position:0% decentralized firebase with user control 00:00:33.420 --> 00:00:36.920 align:start position:0% decentralized firebase with user control data<00:00:33.949> or<00:00:34.949> not<00:00:35.640> about<00:00:35.879> three<00:00:36.090> jobs<00:00:36.300> or<00:00:36.900> a 00:00:36.920 --> 00:00:36.930 align:start position:0% data or not about three jobs or a 00:00:36.930 --> 00:00:38.420 align:start position:0% data or not about three jobs or a dependence<00:00:37.470> of<00:00:37.500> about<00:00:37.710> three<00:00:37.949> it's<00:00:38.190> all<00:00:38.309> about 00:00:38.420 --> 00:00:38.430 align:start position:0% dependence of about three it's all about 00:00:38.430 --> 00:00:40.130 align:start position:0% dependence of about three it's all about three<00:00:38.610> tuck<00:00:38.790> underneath<00:00:39.030> so<00:00:39.750> that<00:00:39.780> people 00:00:40.130 --> 00:00:40.140 align:start position:0% three tuck underneath so that people 00:00:40.140 --> 00:00:43.130 align:start position:0% three tuck underneath so that people don't<00:00:40.290> have<00:00:40.350> to<00:00:40.470> worry<00:00:40.739> about<00:00:41.630> learning<00:00:42.630> all 00:00:43.130 --> 00:00:43.140 align:start position:0% don't have to worry about learning all 00:00:43.140 --> 00:00:45.100 align:start position:0% don't have to worry about learning all of<00:00:43.260> a<00:00:43.350> sudden<00:00:43.680> super<00:00:43.920> system<00:00:44.190> in<00:00:44.340> two<00:00:44.489> seasons 00:00:45.100 --> 00:00:45.110 align:start position:0% of a sudden super system in two seasons 00:00:45.110 --> 00:00:48.830 align:start position:0% of a sudden super system in two seasons I<00:00:46.280> used<00:00:47.280> a<00:00:47.340> little<00:00:47.460> bit<00:00:47.520> of<00:00:47.670> Sapa<00:00:47.850> I<00:00:48.270> love<00:00:48.720> it 00:00:48.830 --> 00:00:48.840 align:start position:0% I used a little bit of Sapa I love it 00:00:48.840 --> 00:00:51.229 align:start position:0% I used a little bit of Sapa I love it here<00:00:48.989> and<00:00:49.170> so<00:00:49.530> it<00:00:49.710> to<00:00:49.800> be<00:00:49.890> back<00:00:50.160> I'm<00:00:50.430> so<00:00:51.090> happy 00:00:51.229 --> 00:00:51.239 align:start position:0% here and so it to be back I'm so happy 00:00:51.239 --> 00:00:52.700 align:start position:0% here and so it to be back I'm so happy when<00:00:51.450> I<00:00:51.480> saw<00:00:51.660> that<00:00:51.809> I<00:00:51.930> was<00:00:52.140> going<00:00:52.260> to<00:00:52.350> be<00:00:52.500> here 00:00:52.700 --> 00:00:52.710 align:start position:0% when I saw that I was going to be here 00:00:52.710 --> 00:00:57.040 align:start position:0% when I saw that I was going to be here and<00:00:52.800> have<00:00:53.010> a<00:00:53.040> chance<00:00:53.100> to<00:00:53.340> sit<00:00:54.120> again<00:00:54.950> I'm<00:00:55.950> a 00:00:57.040 --> 00:00:57.050 align:start position:0% and have a chance to sit again I'm a 00:00:57.050 --> 00:00:59.450 align:start position:0% and have a chance to sit again I'm a programming<00:00:58.050> language<00:00:58.079> theory<00:00:58.590> and<00:00:58.890> person 00:00:59.450 --> 00:00:59.460 align:start position:0% programming language theory and person 00:00:59.460 --> 00:01:03.350 align:start position:0% programming language theory and person she<00:00:59.579> an<00:00:59.670> enthusiast<00:01:00.649> and<00:01:01.649> I<00:01:01.950> used<00:01:02.250> to<00:01:02.370> do<00:01:02.520> R&D 00:01:03.350 --> 00:01:03.360 align:start position:0% she an enthusiast and I used to do R&D 00:01:03.360 --> 00:01:07.820 align:start position:0% she an enthusiast and I used to do R&D full-time<00:01:04.070> on<00:01:05.070> a<00:01:05.100> grant<00:01:05.339> basis<00:01:06.619> but<00:01:07.619> these 00:01:07.820 --> 00:01:07.830 align:start position:0% full-time on a grant basis but these 00:01:07.830 --> 00:01:10.609 align:start position:0% full-time on a grant basis but these days<00:01:08.100> we're<00:01:08.430> doing<00:01:08.640> primarily<00:01:09.470> desktops<00:01:10.470> when 00:01:10.609 --> 00:01:10.619 align:start position:0% days we're doing primarily desktops when 00:01:10.619 --> 00:01:12.050 align:start position:0% days we're doing primarily desktops when listening<00:01:10.920> from<00:01:11.039> I<00:01:11.340> had<00:01:11.700> less<00:01:11.850> in<00:01:12.000> the 00:01:12.050 --> 00:01:12.060 align:start position:0% listening from I had less in the 00:01:12.060 --> 00:01:15.680 align:start position:0% listening from I had less in the services<00:01:12.600> land<00:01:12.890> I'm<00:01:13.890> the<00:01:14.220> co-author<00:01:14.790> of<00:01:15.150> a 00:01:15.680 --> 00:01:15.690 align:start position:0% services land I'm the co-author of a 00:01:15.690 --> 00:01:17.780 align:start position:0% services land I'm the co-author of a number<00:01:15.930> of<00:01:16.049> yeah<00:01:16.320> he<00:01:16.590> is<00:01:16.650> including<00:01:17.190> the 00:01:17.780 --> 00:01:17.790 align:start position:0% number of yeah he is including the 00:01:17.790 --> 00:01:21.590 align:start position:0% number of yeah he is including the emails<00:01:18.330> or<00:01:18.479> taste<00:01:18.750> attack<00:01:19.020> jobs<00:01:19.409> which<00:01:20.600> we 00:01:21.590 --> 00:01:21.600 align:start position:0% emails or taste attack jobs which we 00:01:21.600 --> 00:01:24.109 align:start position:0% emails or taste attack jobs which we hope<00:01:21.810> to<00:01:21.930> get<00:01:22.020> into<00:01:22.350> this<00:01:22.650> artwork<00:01:23.119> that 00:01:24.109 --> 00:01:24.119 align:start position:0% hope to get into this artwork that 00:01:24.119 --> 00:01:25.760 align:start position:0% hope to get into this artwork that didn't<00:01:24.420> happen<00:01:24.720> but<00:01:24.840> there's<00:01:25.020> a<00:01:25.110> resurgence 00:01:25.760 --> 00:01:25.770 align:start position:0% didn't happen but there's a resurgence 00:01:25.770 --> 00:01:27.350 align:start position:0% didn't happen but there's a resurgence of<00:01:25.830> interest<00:01:25.979> so<00:01:26.369> maybe<00:01:26.610> that'll<00:01:26.820> happen<00:01:27.000> soon 00:01:27.350 --> 00:01:27.360 align:start position:0% of interest so maybe that'll happen soon 00:01:27.360 --> 00:01:31.399 align:start position:0% of interest so maybe that'll happen soon and<00:01:28.939> also<00:01:29.939> the<00:01:30.270> other<00:01:30.420> ones<00:01:30.630> really<00:01:30.960> didn't 00:01:31.399 --> 00:01:31.409 align:start position:0% and also the other ones really didn't 00:01:31.409 --> 00:01:33.140 align:start position:0% and also the other ones really didn't know<00:01:31.500> here's<00:01:31.799> Tennessee<00:01:32.310> six<00:01:32.580> which<00:01:32.880> of<00:01:33.030> the 00:01:33.140 --> 00:01:33.150 align:start position:0% know here's Tennessee six which of the 00:01:33.150 --> 00:01:36.710 align:start position:0% know here's Tennessee six which of the most<00:01:33.360> often<00:01:33.780> will<00:01:33.869> be<00:01:33.990> on<00:01:34.200> the<00:01:35.210> stack<00:01:36.210> standard 00:01:36.710 --> 00:01:36.720 align:start position:0% most often will be on the stack standard 00:01:36.720 --> 00:01:39.219 align:start position:0% most often will be on the stack standard US<00:01:36.840> house<00:01:37.020> goes<00:01:37.320> for 00:01:39.219 --> 00:01:39.229 align:start position:0% US house goes for 00:01:39.229 --> 00:01:44.410 align:start position:0% US house goes for mutation<00:01:40.450> in<00:01:42.579> if<00:01:43.579> they're<00:01:43.759> in<00:01:43.909> classic<00:01:44.240> lamp 00:01:44.410 --> 00:01:44.420 align:start position:0% mutation in if they're in classic lamp 00:01:44.420 --> 00:01:46.330 align:start position:0% mutation in if they're in classic lamp or<00:01:44.750> the<00:01:44.810> studying<00:01:45.140> further<00:01:45.350> over<00:01:45.500> as<00:01:45.680> well 00:01:46.330 --> 00:01:46.340 align:start position:0% or the studying further over as well 00:01:46.340 --> 00:01:52.840 align:start position:0% or the studying further over as well this<00:01:46.789> is<00:01:47.289> 1050<00:01:49.479> the<00:01:50.479> other<00:01:51.610> thing<00:01:52.610> to<00:01:52.729> note 00:01:52.840 --> 00:01:52.850 align:start position:0% this is 1050 the other thing to note 00:01:52.850 --> 00:01:54.490 align:start position:0% this is 1050 the other thing to note here<00:01:53.060> as<00:01:53.210> well<00:01:53.420> is<00:01:53.689> this<00:01:53.869> event<00:01:54.140> you<00:01:54.259> know<00:01:54.320> in<00:01:54.469> a 00:01:54.490 --> 00:01:54.500 align:start position:0% here as well is this event you know in a 00:01:54.500 --> 00:01:56.830 align:start position:0% here as well is this event you know in a lot<00:01:54.710> of<00:01:54.740> other<00:01:54.920> standards<00:01:55.189> so<00:01:55.780> people<00:01:56.780> the 00:01:56.830 --> 00:01:56.840 align:start position:0% lot of other standards so people the 00:01:56.840 --> 00:01:58.029 align:start position:0% lot of other standards so people the situation<00:01:57.259> understand<00:01:57.649> there's<00:01:57.799> going<00:01:57.920> to<00:01:57.979> be 00:01:58.029 --> 00:01:58.039 align:start position:0% situation understand there's going to be 00:01:58.039 --> 00:02:02.740 align:start position:0% situation understand there's going to be a<00:01:58.130> penalty<00:01:58.579> 1,400<00:01:59.360> secure<00:02:00.289> children's<00:02:01.750> use 00:02:02.740 --> 00:02:02.750 align:start position:0% a penalty 1,400 secure children's use 00:02:02.750 --> 00:02:04.300 align:start position:0% a penalty 1,400 secure children's use this<00:02:02.929> as<00:02:03.110> a<00:02:03.140> dependency<00:02:03.649> as<00:02:03.770> well<00:02:03.920> so<00:02:04.069> this<00:02:04.159> is 00:02:04.300 --> 00:02:04.310 align:start position:0% this as a dependency as well so this is 00:02:04.310 --> 00:02:05.999 align:start position:0% this as a dependency as well so this is already<00:02:04.429> finance<00:02:04.880> way<00:02:05.000> out<00:02:05.210> into<00:02:05.420> industry 00:02:05.999 --> 00:02:06.009 align:start position:0% already finance way out into industry 00:02:06.009 --> 00:02:09.999 align:start position:0% already finance way out into industry refuse<00:02:07.009> material<00:02:07.369> regulation<00:02:07.909> Sarah<00:02:09.009> last 00:02:09.999 --> 00:02:10.009 align:start position:0% refuse material regulation Sarah last 00:02:10.009 --> 00:02:11.949 align:start position:0% refuse material regulation Sarah last night<00:02:10.369> I<00:02:10.580> hope<00:02:10.849> use<00:02:11.030> Twitter<00:02:11.269> and<00:02:11.569> saw<00:02:11.750> this 00:02:11.949 --> 00:02:11.959 align:start position:0% night I hope use Twitter and saw this 00:02:11.959 --> 00:02:15.130 align:start position:0% night I hope use Twitter and saw this tweet<00:02:13.000> so<00:02:14.000> it<00:02:14.060> sounds<00:02:14.269> like<00:02:14.299> there's 00:02:15.130 --> 00:02:15.140 align:start position:0% tweet so it sounds like there's 00:02:15.140 --> 00:02:17.589 align:start position:0% tweet so it sounds like there's interesting<00:02:15.709> getting<00:02:16.250> with<00:02:16.400> this<00:02:16.549> I<00:02:16.819> embedded 00:02:17.589 --> 00:02:17.599 align:start position:0% interesting getting with this I embedded 00:02:17.599 --> 00:02:19.449 align:start position:0% interesting getting with this I embedded directly<00:02:17.780> in<00:02:18.110> my<00:02:18.290> career<00:02:18.530> in<00:02:18.829> solidity<00:02:19.160> and 00:02:19.449 --> 00:02:19.459 align:start position:0% directly in my career in solidity and 00:02:19.459 --> 00:02:21.970 align:start position:0% directly in my career in solidity and doing<00:02:20.120> on<00:02:20.720> training<00:02:21.049> translation<00:02:21.590> reviews<00:02:21.860> as 00:02:21.970 --> 00:02:21.980 align:start position:0% doing on training translation reviews as 00:02:21.980 --> 00:02:25.150 align:start position:0% doing on training translation reviews as well<00:02:22.010> which<00:02:22.459> we<00:02:22.610> have<00:02:23.680> people<00:02:24.680> contact<00:02:25.040> code 00:02:25.150 --> 00:02:25.160 align:start position:0% well which we have people contact code 00:02:25.160 --> 00:02:29.050 align:start position:0% well which we have people contact code for<00:02:25.459> on<00:02:25.670> github<00:02:26.060> so<00:02:27.880> let's<00:02:28.880> talk<00:02:29.000> about 00:02:29.050 --> 00:02:29.060 align:start position:0% for on github so let's talk about 00:02:29.060 --> 00:02:36.010 align:start position:0% for on github so let's talk about whether<00:02:29.959> contracts 00:02:36.010 --> 00:02:36.020 align:start position:0% 00:02:36.020 --> 00:02:39.310 align:start position:0% so<00:02:36.590> the<00:02:36.740> goal<00:02:37.400> of<00:02:38.360> this<00:02:38.480> project<00:02:38.660> broadly<00:02:39.260> is 00:02:39.310 --> 00:02:39.320 align:start position:0% so the goal of this project broadly is 00:02:39.320 --> 00:02:41.800 align:start position:0% so the goal of this project broadly is in<00:02:39.470> three<00:02:39.650> parts<00:02:39.680> first<00:02:40.280> write<00:02:41.270> your<00:02:41.450> lines<00:02:41.660> of 00:02:41.800 --> 00:02:41.810 align:start position:0% in three parts first write your lines of 00:02:41.810 --> 00:02:43.420 align:start position:0% in three parts first write your lines of code<00:02:41.990> we<00:02:42.590> are<00:02:42.710> going<00:02:42.920> to<00:02:43.010> write<00:02:43.190> the<00:02:43.310> more 00:02:43.420 --> 00:02:43.430 align:start position:0% code we are going to write the more 00:02:43.430 --> 00:02:46.570 align:start position:0% code we are going to write the more lengthy<00:02:43.730> or<00:02:43.760> to<00:02:43.970> introduce<00:02:44.150> about<00:02:45.430> it's<00:02:46.430> also 00:02:46.570 --> 00:02:46.580 align:start position:0% lengthy or to introduce about it's also 00:02:46.580 --> 00:02:51.070 align:start position:0% lengthy or to introduce about it's also a<00:02:46.700> gentleman<00:02:47.090> I'm<00:02:47.890> testing<00:02:49.870> expensive<00:02:50.870> to<00:02:50.960> do 00:02:51.070 --> 00:02:51.080 align:start position:0% a gentleman I'm testing expensive to do 00:02:51.080 --> 00:02:54.370 align:start position:0% a gentleman I'm testing expensive to do occasionally<00:02:51.740> etcetera<00:02:53.050> so<00:02:54.050> you<00:02:54.110> can<00:02:54.290> have 00:02:54.370 --> 00:02:54.380 align:start position:0% occasionally etcetera so you can have 00:02:54.380 --> 00:02:56.350 align:start position:0% occasionally etcetera so you can have higher<00:02:54.590> confidence<00:02:54.920> in<00:02:55.400> code<00:02:55.880> that<00:02:55.910> lives 00:02:56.350 --> 00:02:56.360 align:start position:0% higher confidence in code that lives 00:02:56.360 --> 00:02:59.310 align:start position:0% higher confidence in code that lives munching<00:02:56.870> they<00:02:57.320> do<00:02:57.470> call<00:02:57.710> into<00:02:58.130> that<00:02:58.730> has<00:02:58.850> been 00:02:59.310 --> 00:02:59.320 align:start position:0% munching they do call into that has been 00:02:59.320 --> 00:03:04.090 align:start position:0% munching they do call into that has been audited<00:03:00.320> by<00:03:00.610> say<00:03:01.610> Boston<00:03:01.970> or<00:03:03.100> consensus 00:03:04.090 --> 00:03:04.100 align:start position:0% audited by say Boston or consensus 00:03:04.100 --> 00:03:06.250 align:start position:0% audited by say Boston or consensus diligence<00:03:04.550> and<00:03:04.940> isn't<00:03:05.300> signed<00:03:05.540> off<00:03:05.690> and<00:03:05.990> the 00:03:06.250 --> 00:03:06.260 align:start position:0% diligence and isn't signed off and the 00:03:06.260 --> 00:03:09.090 align:start position:0% diligence and isn't signed off and the community<00:03:06.620> understands<00:03:07.130> how<00:03:07.310> it<00:03:07.430> works<00:03:07.730> and 00:03:09.090 --> 00:03:09.100 align:start position:0% community understands how it works and 00:03:09.100 --> 00:03:11.620 align:start position:0% community understands how it works and last<00:03:10.100> goal<00:03:10.310> is<00:03:10.400> to<00:03:10.490> make<00:03:10.640> theory<00:03:11.480> more 00:03:11.620 --> 00:03:11.630 align:start position:0% last goal is to make theory more 00:03:11.630 --> 00:03:15.070 align:start position:0% last goal is to make theory more accessible<00:03:12.200> we<00:03:13.160> have<00:03:13.390> your<00:03:14.390> semantic<00:03:14.810> codes 00:03:15.070 --> 00:03:15.080 align:start position:0% accessible we have your semantic codes 00:03:15.080 --> 00:03:18.190 align:start position:0% accessible we have your semantic codes now<00:03:15.290> that<00:03:15.830> can<00:03:16.210> eat<00:03:17.210> understood<00:03:17.720> you<00:03:18.080> can 00:03:18.190 --> 00:03:18.200 align:start position:0% now that can eat understood you can 00:03:18.200 --> 00:03:20.290 align:start position:0% now that can eat understood you can build<00:03:18.380> up<00:03:18.500> the<00:03:18.740> flow<00:03:19.220> of<00:03:19.250> East<00:03:19.700> Coast<00:03:19.940> through 00:03:20.290 --> 00:03:20.300 align:start position:0% build up the flow of East Coast through 00:03:20.300 --> 00:03:24.340 align:start position:0% build up the flow of East Coast through the<00:03:20.480> contract<00:03:20.870> through<00:03:21.670> web<00:03:22.670> of<00:03:22.790> contracts<00:03:23.390> or 00:03:24.340 --> 00:03:24.350 align:start position:0% the contract through web of contracts or 00:03:24.350 --> 00:03:26.470 align:start position:0% the contract through web of contracts or probably<00:03:25.160> come<00:03:25.340> back<00:03:25.490> out<00:03:25.670> to<00:03:25.700> a<00:03:25.880> user<00:03:26.090> and 00:03:26.470 --> 00:03:26.480 align:start position:0% probably come back out to a user and 00:03:26.480 --> 00:03:29.230 align:start position:0% probably come back out to a user and then<00:03:26.570> translate<00:03:27.020> them<00:03:27.170> into<00:03:27.910> human<00:03:28.910> readable 00:03:29.230 --> 00:03:29.240 align:start position:0% then translate them into human readable 00:03:29.240 --> 00:03:31.540 align:start position:0% then translate them into human readable language<00:03:29.420> which<00:03:30.140> times<00:03:30.650> winning<00:03:30.920> and<00:03:31.250> we<00:03:31.430> may 00:03:31.540 --> 00:03:31.550 align:start position:0% language which times winning and we may 00:03:31.550 --> 00:03:35.140 align:start position:0% language which times winning and we may take<00:03:31.730> a<00:03:31.790> look<00:03:31.910> at<00:03:32.510> at<00:03:32.630> the<00:03:32.750> very<00:03:32.780> end<00:03:34.150> high 00:03:35.140 --> 00:03:35.150 align:start position:0% take a look at at the very end high 00:03:35.150 --> 00:03:38.770 align:start position:0% take a look at at the very end high level<00:03:35.450> idea<00:03:36.490> just<00:03:37.490> kind<00:03:37.760> like<00:03:37.910> how<00:03:38.090> on<00:03:38.390> the<00:03:38.630> web 00:03:38.770 --> 00:03:38.780 align:start position:0% level idea just kind like how on the web 00:03:38.780 --> 00:03:40.630 align:start position:0% level idea just kind like how on the web we<00:03:39.170> have<00:03:39.200> satisfy<00:03:40.100> those<00:03:40.160> that<00:03:40.370> came<00:03:40.460> along 00:03:40.630 --> 00:03:40.640 align:start position:0% we have satisfy those that came along 00:03:40.640 --> 00:03:42.720 align:start position:0% we have satisfy those that came along with<00:03:40.700> every<00:03:41.060> request<00:03:41.330> like<00:03:42.050> a<00:03:42.080> floor<00:03:42.320> to<00:03:42.410> floor 00:03:42.720 --> 00:03:42.730 align:start position:0% with every request like a floor to floor 00:03:42.730 --> 00:03:45.150 align:start position:0% with every request like a floor to floor we<00:03:43.730> should<00:03:43.880> have<00:03:44.060> these<00:03:44.240> as<00:03:44.390> well<00:03:44.570> for 00:03:45.150 --> 00:03:45.160 align:start position:0% we should have these as well for 00:03:45.160 --> 00:03:48.190 align:start position:0% we should have these as well for Starbucks<00:03:46.160> right<00:03:47.000> especially<00:03:47.570> automated 00:03:48.190 --> 00:03:48.200 align:start position:0% Starbucks right especially automated 00:03:48.200 --> 00:03:52.240 align:start position:0% Starbucks right especially automated behavior<00:03:48.680> or<00:03:49.220> react<00:03:49.580> to<00:03:49.610> things<00:03:50.000> in<00:03:50.540> a<00:03:51.250> smarter 00:03:52.240 --> 00:03:52.250 align:start position:0% behavior or react to things in a smarter 00:03:52.250 --> 00:03:53.950 align:start position:0% behavior or react to things in a smarter or<00:03:52.490> contextual<00:03:52.820> way<00:03:53.090> than<00:03:53.300> just<00:03:53.480> to<00:03:53.630> our<00:03:53.750> halls 00:03:53.950 --> 00:03:53.960 align:start position:0% or contextual way than just to our halls 00:03:53.960 --> 00:03:58.810 align:start position:0% or contextual way than just to our halls or<00:03:54.200> having<00:03:54.500> some<00:03:55.390> custom<00:03:57.040> response<00:03:58.040> type<00:03:58.340> for 00:03:58.810 --> 00:03:58.820 align:start position:0% or having some custom response type for 00:03:58.820 --> 00:04:01.570 align:start position:0% or having some custom response type for every<00:03:59.120> request<00:03:59.420> and<00:04:00.230> the<00:04:01.040> other<00:04:01.280> nice<00:04:01.550> thing 00:04:01.570 --> 00:04:01.580 align:start position:0% every request and the other nice thing 00:04:01.580 --> 00:04:03.610 align:start position:0% every request and the other nice thing because<00:04:02.210> this<00:04:02.330> is<00:04:02.510> it<00:04:02.810> all<00:04:03.020> fits<00:04:03.320> into<00:04:03.500> a 00:04:03.610 --> 00:04:03.620 align:start position:0% because this is it all fits into a 00:04:03.620 --> 00:04:04.840 align:start position:0% because this is it all fits into a single<00:04:03.920> bite<00:04:04.100> which<00:04:04.310> means<00:04:04.490> very<00:04:04.790> very 00:04:04.840 --> 00:04:04.850 align:start position:0% single bite which means very very 00:04:04.850 --> 00:04:07.750 align:start position:0% single bite which means very very portable<00:04:05.270> is<00:04:05.990> that<00:04:06.200> we<00:04:06.290> can<00:04:06.410> do<00:04:06.500> things<00:04:06.800> across 00:04:07.750 --> 00:04:07.760 align:start position:0% portable is that we can do things across 00:04:07.760 --> 00:04:09.430 align:start position:0% portable is that we can do things across different<00:04:08.240> chains<00:04:08.480> if<00:04:08.780> we<00:04:08.900> have 00:04:09.430 --> 00:04:09.440 align:start position:0% different chains if we have 00:04:09.440 --> 00:04:12.660 align:start position:0% different chains if we have occasionally<00:04:10.160> with<00:04:10.490> the<00:04:10.670> et<00:04:11.060> CET<00:04:11.300> HP's<00:04:12.110> bridge 00:04:12.660 --> 00:04:12.670 align:start position:0% occasionally with the et CET HP's bridge 00:04:12.670 --> 00:04:16.720 align:start position:0% occasionally with the et CET HP's bridge and<00:04:13.840> cross<00:04:14.840> our<00:04:14.900> communication<00:04:15.740> with<00:04:16.280> me<00:04:16.430> too 00:04:16.720 --> 00:04:16.730 align:start position:0% and cross our communication with me too 00:04:16.730 --> 00:04:20.199 align:start position:0% and cross our communication with me too so<00:04:18.700> obviously<00:04:19.700> this<00:04:19.820> draw<00:04:19.970> a<00:04:20.000> lot<00:04:20.180> of 00:04:20.199 --> 00:04:20.209 align:start position:0% so obviously this draw a lot of 00:04:20.209 --> 00:04:22.540 align:start position:0% so obviously this draw a lot of inspiration<00:04:20.330> from<00:04:20.810> you<00:04:21.110> then<00:04:21.260> HTTP<00:04:22.010> and<00:04:22.460> the 00:04:22.540 --> 00:04:22.550 align:start position:0% inspiration from you then HTTP and the 00:04:22.550 --> 00:04:25.810 align:start position:0% inspiration from you then HTTP and the actor<00:04:22.850> model<00:04:24.280> what's<00:04:25.280> all<00:04:25.370> these<00:04:25.490> things<00:04:25.700> home 00:04:25.810 --> 00:04:25.820 align:start position:0% actor model what's all these things home 00:04:25.820 --> 00:04:28.240 align:start position:0% actor model what's all these things home incoming<00:04:26.630> composition<00:04:27.440> we<00:04:27.860> want<00:04:28.010> to<00:04:28.100> have 00:04:28.240 --> 00:04:28.250 align:start position:0% incoming composition we want to have 00:04:28.250 --> 00:04:29.710 align:start position:0% incoming composition we want to have contractor<00:04:28.970> come<00:04:29.120> visit<00:04:29.330> shouldn't<00:04:29.570> rather 00:04:29.710 --> 00:04:29.720 align:start position:0% contractor come visit shouldn't rather 00:04:29.720 --> 00:04:33.490 align:start position:0% contractor come visit shouldn't rather than<00:04:30.010> taking<00:04:31.180> existing<00:04:32.180> contract<00:04:32.780> anything 00:04:33.490 --> 00:04:33.500 align:start position:0% than taking existing contract anything 00:04:33.500 --> 00:04:35.710 align:start position:0% than taking existing contract anything in<00:04:33.620> a<00:04:33.650> bunch<00:04:33.980> and<00:04:34.160> hoping<00:04:35.090> that<00:04:35.210> still<00:04:35.540> roughs 00:04:35.710 --> 00:04:35.720 align:start position:0% in a bunch and hoping that still roughs 00:04:35.720 --> 00:04:36.970 align:start position:0% in a bunch and hoping that still roughs the<00:04:35.810> way<00:04:35.870> that<00:04:36.020> we<00:04:36.110> have<00:04:36.290> students<00:04:36.650> before 00:04:36.970 --> 00:04:36.980 align:start position:0% the way that we have students before 00:04:36.980 --> 00:04:39.420 align:start position:0% the way that we have students before right<00:04:37.790> even<00:04:38.120> if<00:04:38.180> you<00:04:38.240> have<00:04:38.330> a<00:04:38.420> fully<00:04:38.690> audited 00:04:39.420 --> 00:04:39.430 align:start position:0% right even if you have a fully audited 00:04:39.430 --> 00:04:43.090 align:start position:0% right even if you have a fully audited library<00:04:40.430> and<00:04:40.700> then<00:04:40.940> you<00:04:41.030> go<00:04:41.530> audits<00:04:42.530> and 00:04:43.090 --> 00:04:43.100 align:start position:0% library and then you go audits and 00:04:43.100 --> 00:04:44.800 align:start position:0% library and then you go audits and deploy<00:04:43.460> it<00:04:43.490> you've<00:04:44.150> broken<00:04:44.360> a<00:04:44.540> lot<00:04:44.630> of<00:04:44.750> the 00:04:44.800 --> 00:04:44.810 align:start position:0% deploy it you've broken a lot of the 00:04:44.810 --> 00:04:46.690 align:start position:0% deploy it you've broken a lot of the core<00:04:44.990> assumptions<00:04:45.530> you<00:04:45.920> have<00:04:46.010> to<00:04:46.130> get<00:04:46.250> me<00:04:46.520> out 00:04:46.690 --> 00:04:46.700 align:start position:0% core assumptions you have to get me out 00:04:46.700 --> 00:04:47.520 align:start position:0% core assumptions you have to get me out of<00:04:46.730> it 00:04:47.520 --> 00:04:47.530 align:start position:0% of it 00:04:47.530 --> 00:04:50.530 align:start position:0% of it in<00:04:48.530> theory<00:04:48.770> it's<00:04:48.980> a<00:04:49.040> shared<00:04:49.250> system<00:04:49.850> why<00:04:50.390> are 00:04:50.530 --> 00:04:50.540 align:start position:0% in theory it's a shared system why are 00:04:50.540 --> 00:04:52.060 align:start position:0% in theory it's a shared system why are three<00:04:50.630> leveraging<00:04:51.110> each<00:04:51.200> other's<00:04:51.470> code<00:04:51.710> why 00:04:52.060 --> 00:04:52.070 align:start position:0% three leveraging each other's code why 00:04:52.070 --> 00:04:54.130 align:start position:0% three leveraging each other's code why do<00:04:52.130> we<00:04:52.280> have<00:04:52.490> 15<00:04:52.910> million<00:04:53.120> years<00:04:53.390> to<00:04:53.540> 2012<00:04:53.960> B's 00:04:54.130 --> 00:04:54.140 align:start position:0% do we have 15 million years to 2012 B's 00:04:54.140 --> 00:04:55.750 align:start position:0% do we have 15 million years to 2012 B's and<00:04:54.290> so<00:04:54.380> most<00:04:54.800> of<00:04:54.920> that<00:04:54.980> logically<00:04:55.400> counsel 00:04:55.750 --> 00:04:55.760 align:start position:0% and so most of that logically counsel 00:04:55.760 --> 00:05:00.610 align:start position:0% and so most of that logically counsel into<00:04:55.970> single<00:04:56.300> contract<00:04:56.720> and<00:04:59.080> if<00:05:00.080> we<00:05:00.320> can<00:05:00.470> build 00:05:00.610 --> 00:05:00.620 align:start position:0% into single contract and if we can build 00:05:00.620 --> 00:05:03.580 align:start position:0% into single contract and if we can build these<00:05:00.890> high<00:05:01.130> value<00:05:01.640> of<00:05:01.850> highly<00:05:02.360> use<00:05:02.590> contracts 00:05:03.580 --> 00:05:03.590 align:start position:0% these high value of highly use contracts 00:05:03.590 --> 00:05:06.960 align:start position:0% these high value of highly use contracts as<00:05:03.710> they're<00:05:03.830> always<00:05:03.950> make<00:05:04.160> money<00:05:04.310> doing<00:05:04.880> that 00:05:06.960 --> 00:05:06.970 align:start position:0% as they're always make money doing that 00:05:06.970 --> 00:05:11.680 align:start position:0% as they're always make money doing that so<00:05:07.970> on<00:05:08.630> to<00:05:08.840> many<00:05:09.050> services<00:05:10.540> something<00:05:11.540> you 00:05:11.680 --> 00:05:11.690 align:start position:0% so on to many services something you 00:05:11.690 --> 00:05:12.820 align:start position:0% so on to many services something you know<00:05:11.930> a<00:05:11.990> little<00:05:12.020> bit<00:05:12.230> like<00:05:12.380> this<00:05:12.590> where<00:05:12.770> you 00:05:12.820 --> 00:05:12.830 align:start position:0% know a little bit like this where you 00:05:12.830 --> 00:05:14.470 align:start position:0% know a little bit like this where you can<00:05:12.980> count<00:05:13.130> contracts<00:05:13.490> come<00:05:13.700> to<00:05:13.880> contracts 00:05:14.470 --> 00:05:14.480 align:start position:0% can count contracts come to contracts 00:05:14.480 --> 00:05:15.850 align:start position:0% can count contracts come to contracts that<00:05:14.750> are<00:05:14.840> all<00:05:14.900> fairly<00:05:15.110> lightweight<00:05:15.350> and<00:05:15.710> thin 00:05:15.850 --> 00:05:15.860 align:start position:0% that are all fairly lightweight and thin 00:05:15.860 --> 00:05:21.130 align:start position:0% that are all fairly lightweight and thin and<00:05:16.070> do<00:05:16.130> single<00:05:16.490> thing<00:05:19.810> yeah<00:05:20.810> it<00:05:21.020> was 00:05:21.130 --> 00:05:21.140 align:start position:0% and do single thing yeah it was 00:05:21.140 --> 00:05:23.430 align:start position:0% and do single thing yeah it was basically<00:05:21.260> what<00:05:21.590> I<00:05:21.650> just<00:05:21.680> said<00:05:21.980> some<00:05:22.580> apple 00:05:23.430 --> 00:05:23.440 align:start position:0% basically what I just said some apple 00:05:23.440 --> 00:05:27.580 align:start position:0% basically what I just said some apple core<00:05:24.440> technical<00:05:24.770> idea<00:05:25.419> so<00:05:26.419> today<00:05:26.930> you<00:05:26.990> deploy 00:05:27.580 --> 00:05:27.590 align:start position:0% core technical idea so today you deploy 00:05:27.590 --> 00:05:29.770 align:start position:0% core technical idea so today you deploy since<00:05:28.580> our<00:05:28.730> contracts<00:05:29.090> especially<00:05:29.510> some<00:05:29.720> of 00:05:29.770 --> 00:05:29.780 align:start position:0% since our contracts especially some of 00:05:29.780 --> 00:05:31.690 align:start position:0% since our contracts especially some of my<00:05:29.870> chain<00:05:30.080> that<00:05:30.320> they're<00:05:30.440> pretty<00:05:30.560> much<00:05:30.680> silent 00:05:31.690 --> 00:05:31.700 align:start position:0% my chain that they're pretty much silent 00:05:31.700 --> 00:05:34.840 align:start position:0% my chain that they're pretty much silent system<00:05:32.330> you'd<00:05:32.900> employ<00:05:33.140> one<00:05:33.950> maybe<00:05:34.490> two<00:05:34.700> or 00:05:34.840 --> 00:05:34.850 align:start position:0% system you'd employ one maybe two or 00:05:34.850 --> 00:05:36.070 align:start position:0% system you'd employ one maybe two or three<00:05:34.880> contracts<00:05:35.510> and<00:05:35.690> they<00:05:35.750> talk<00:05:35.930> to<00:05:35.960> each 00:05:36.070 --> 00:05:36.080 align:start position:0% three contracts and they talk to each 00:05:36.080 --> 00:05:38.800 align:start position:0% three contracts and they talk to each other<00:05:36.320> in<00:05:36.710> some<00:05:37.040> special<00:05:37.640> way<00:05:37.670> and<00:05:38.180> it'll 00:05:38.800 --> 00:05:38.810 align:start position:0% other in some special way and it'll 00:05:38.810 --> 00:05:40.360 align:start position:0% other in some special way and it'll really<00:05:38.960> talk<00:05:39.200> to<00:05:39.290> each<00:05:39.320> other<00:05:39.530> right<00:05:40.010> so<00:05:40.070> we've 00:05:40.360 --> 00:05:40.370 align:start position:0% really talk to each other right so we've 00:05:40.370 --> 00:05:42.100 align:start position:0% really talk to each other right so we've grown<00:05:40.520> the<00:05:40.730> shared<00:05:40.940> system<00:05:41.120> but<00:05:41.810> we<00:05:41.900> really 00:05:42.100 --> 00:05:42.110 align:start position:0% grown the shared system but we really 00:05:42.110 --> 00:05:43.840 align:start position:0% grown the shared system but we really fell<00:05:42.260> into<00:05:42.470> a<00:05:42.560> small<00:05:42.830> mini<00:05:43.130> blockchain<00:05:43.700> see 00:05:43.840 --> 00:05:43.850 align:start position:0% fell into a small mini blockchain see 00:05:43.850 --> 00:05:45.910 align:start position:0% fell into a small mini blockchain see some<00:05:44.030> are<00:05:44.180> watching<00:05:44.570> and<00:05:44.810> you<00:05:45.440> know<00:05:45.590> sometimes 00:05:45.910 --> 00:05:45.920 align:start position:0% some are watching and you know sometimes 00:05:45.920 --> 00:05:49.030 align:start position:0% some are watching and you know sometimes sure<00:05:46.310> maybe<00:05:46.550> they<00:05:46.730> do<00:05:46.880> talk<00:05:47.150> to<00:05:47.960> another<00:05:48.770> like 00:05:49.030 --> 00:05:49.040 align:start position:0% sure maybe they do talk to another like 00:05:49.040 --> 00:05:50.260 align:start position:0% sure maybe they do talk to another like maybe<00:05:49.220> that's<00:05:49.400> what<00:05:49.520> took<00:05:49.610> it<00:05:49.760> ease<00:05:49.910> and<00:05:50.180> you 00:05:50.260 --> 00:05:50.270 align:start position:0% maybe that's what took it ease and you 00:05:50.270 --> 00:05:52.090 align:start position:0% maybe that's what took it ease and you know<00:05:50.480> you're<00:05:50.630> falling<00:05:50.900> into<00:05:51.020> it<00:05:51.200> but<00:05:51.890> for<00:05:52.010> the 00:05:52.090 --> 00:05:52.100 align:start position:0% know you're falling into it but for the 00:05:52.100 --> 00:05:53.980 align:start position:0% know you're falling into it but for the most<00:05:52.220> part<00:05:52.310> they're<00:05:52.640> just<00:05:52.850> kind<00:05:53.090> of<00:05:53.240> there's<00:05:53.930> a 00:05:53.980 --> 00:05:53.990 align:start position:0% most part they're just kind of there's a 00:05:53.990 --> 00:05:56.110 align:start position:0% most part they're just kind of there's a lot<00:05:54.140> of<00:05:54.260> duplication<00:05:55.190> and<00:05:55.580> a<00:05:55.640> lot<00:05:55.820> of<00:05:55.910> things 00:05:56.110 --> 00:05:56.120 align:start position:0% lot of duplication and a lot of things 00:05:56.120 --> 00:05:58.150 align:start position:0% lot of duplication and a lot of things being<00:05:56.270> redeployed<00:05:56.720> onto<00:05:57.560> the<00:05:57.680> channel<00:05:58.070> all 00:05:58.150 --> 00:05:58.160 align:start position:0% being redeployed onto the channel all 00:05:58.160 --> 00:05:58.480 align:start position:0% being redeployed onto the channel all the<00:05:58.250> time 00:05:58.480 --> 00:05:58.490 align:start position:0% the time 00:05:58.490 --> 00:06:01.980 align:start position:0% the time so<00:05:58.880> what<00:05:59.240> we<00:05:59.450> can<00:06:00.010> break<00:06:01.010> those<00:06:01.250> barriers<00:06:01.580> and 00:06:01.980 --> 00:06:01.990 align:start position:0% so what we can break those barriers and 00:06:01.990 --> 00:06:05.520 align:start position:0% so what we can break those barriers and call<00:06:02.990> tuna<00:06:03.580> so<00:06:04.580> in<00:06:04.730> this<00:06:04.820> case<00:06:05.030> the<00:06:05.270> two 00:06:05.520 --> 00:06:05.530 align:start position:0% call tuna so in this case the two 00:06:05.530 --> 00:06:08.560 align:start position:0% call tuna so in this case the two multicolored<00:06:06.530> ones<00:06:06.740> here<00:06:06.950> are<00:06:07.480> you<00:06:08.480> know 00:06:08.560 --> 00:06:08.570 align:start position:0% multicolored ones here are you know 00:06:08.570 --> 00:06:12.040 align:start position:0% multicolored ones here are you know secure<00:06:08.990> verify<00:06:09.440> on<00:06:09.680> chain<00:06:09.950> services<00:06:10.720> they<00:06:11.720> can 00:06:12.040 --> 00:06:12.050 align:start position:0% secure verify on chain services they can 00:06:12.050 --> 00:06:14.140 align:start position:0% secure verify on chain services they can maybe<00:06:12.260> talk<00:06:12.500> to<00:06:12.650> each<00:06:12.740> other<00:06:12.950> and<00:06:13.310> other 00:06:14.140 --> 00:06:14.150 align:start position:0% maybe talk to each other and other 00:06:14.150 --> 00:06:17.110 align:start position:0% maybe talk to each other and other contracts<00:06:14.660> can<00:06:14.840> talk<00:06:14.990> about<00:06:15.140> as<00:06:15.530> well<00:06:16.120> use 00:06:17.110 --> 00:06:17.120 align:start position:0% contracts can talk about as well use 00:06:17.120 --> 00:06:19.800 align:start position:0% contracts can talk about as well use them<00:06:17.150> as<00:06:17.360> proxy<00:06:17.950> publish<00:06:18.950> them<00:06:19.190> for 00:06:19.800 --> 00:06:19.810 align:start position:0% them as proxy publish them for 00:06:19.810 --> 00:06:25.510 align:start position:0% them as proxy publish them for authentication<00:06:21.340> or<00:06:22.340> to<00:06:22.850> do<00:06:23.180> some<00:06:24.190> juicing<00:06:25.190> you 00:06:25.510 --> 00:06:25.520 align:start position:0% authentication or to do some juicing you 00:06:25.520 --> 00:06:27.580 align:start position:0% authentication or to do some juicing you know<00:06:25.610> computation<00:06:26.600> deal<00:06:27.260> of<00:06:27.440> difference 00:06:27.580 --> 00:06:27.590 align:start position:0% know computation deal of difference 00:06:27.590 --> 00:06:32.770 align:start position:0% know computation deal of difference cetera<00:06:30.250> so<00:06:31.250> what<00:06:31.790> these<00:06:32.000> folks<00:06:32.210> actually<00:06:32.480> look 00:06:32.770 --> 00:06:32.780 align:start position:0% cetera so what these folks actually look 00:06:32.780 --> 00:06:38.740 align:start position:0% cetera so what these folks actually look like<00:06:35.950> as<00:06:36.950> I<00:06:37.070> said<00:06:37.100> before<00:06:37.340> they<00:06:37.670> are<00:06:37.700> a<00:06:38.180> single 00:06:38.740 --> 00:06:38.750 align:start position:0% like as I said before they are a single 00:06:38.750 --> 00:06:40.450 align:start position:0% like as I said before they are a single byte<00:06:38.900> and<00:06:39.170> if<00:06:39.530> you've<00:06:39.650> read<00:06:39.770> about<00:06:39.920> it<00:06:40.220> how<00:06:40.400> to 00:06:40.450 --> 00:06:40.460 align:start position:0% byte and if you've read about it how to 00:06:40.460 --> 00:06:41.350 align:start position:0% byte and if you've read about it how to get<00:06:40.760> a<00:06:40.820> nibble 00:06:41.350 --> 00:06:41.360 align:start position:0% get a nibble 00:06:41.360 --> 00:06:45.130 align:start position:0% get a nibble so<00:06:42.290> the<00:06:43.010> just<00:06:43.580> say<00:06:43.670> how<00:06:43.790> in<00:06:44.090> HTTP<00:06:44.690> you<00:06:44.810> have<00:06:44.990> say 00:06:45.130 --> 00:06:45.140 align:start position:0% so the just say how in HTTP you have say 00:06:45.140 --> 00:06:48.940 align:start position:0% so the just say how in HTTP you have say 492<00:06:45.950> our<00:06:46.070> 200<00:06:46.490> range<00:06:47.230> we<00:06:48.230> hadn't<00:06:48.470> saying<00:06:48.710> that 00:06:48.940 --> 00:06:48.950 align:start position:0% 492 our 200 range we hadn't saying that 00:06:48.950 --> 00:06:50.860 align:start position:0% 492 our 200 range we hadn't saying that they<00:06:49.070> are<00:06:49.280> flipped<00:06:49.910> around<00:06:50.090> and<00:06:50.630> that's 00:06:50.860 --> 00:06:50.870 align:start position:0% they are flipped around and that's 00:06:50.870 --> 00:06:53.440 align:start position:0% they are flipped around and that's mainly<00:06:51.500> to<00:06:51.830> make<00:06:51.860> it<00:06:52.130> easy<00:06:52.370> to<00:06:52.490> decompose<00:06:53.210> them 00:06:53.440 --> 00:06:53.450 align:start position:0% mainly to make it easy to decompose them 00:06:53.450 --> 00:06:57.910 align:start position:0% mainly to make it easy to decompose them programmatically<00:06:55.060> so<00:06:56.060> here<00:06:56.390> is<00:06:56.600> 0<00:06:56.900> X<00:06:57.020> or<00:06:57.260> Y<00:06:57.440> the 00:06:57.910 --> 00:06:57.920 align:start position:0% programmatically so here is 0 X or Y the 00:06:57.920 --> 00:07:02.440 align:start position:0% programmatically so here is 0 X or Y the first<00:06:58.790> 4<00:06:59.150> bits<00:06:59.860> right<00:07:00.860> the<00:07:01.010> category<00:07:01.490> the<00:07:02.240> last 00:07:02.440 --> 00:07:02.450 align:start position:0% first 4 bits right the category the last 00:07:02.450 --> 00:07:11.060 align:start position:0% first 4 bits right the category the last four<00:07:02.690> risk<00:07:02.870> or<00:07:03.200> the<00:07:03.230> reason 00:07:11.060 --> 00:07:11.070 align:start position:0% 00:07:11.070 --> 00:07:13.280 align:start position:0% and<00:07:11.490> if<00:07:12.030> you<00:07:12.150> have<00:07:12.360> something<00:07:12.720> where<00:07:13.139> the 00:07:13.280 --> 00:07:13.290 align:start position:0% and if you have something where the 00:07:13.290 --> 00:07:17.150 align:start position:0% and if you have something where the caliber<00:07:13.770> is<00:07:13.800> 0<00:07:14.660> this<00:07:15.660> is<00:07:15.720> the<00:07:16.560> same<00:07:16.770> case<00:07:16.950> is 00:07:17.150 --> 00:07:17.160 align:start position:0% caliber is 0 this is the same case is 00:07:17.160 --> 00:07:20.420 align:start position:0% caliber is 0 this is the same case is having<00:07:17.790> or<00:07:18.360> 100<00:07:18.870> in<00:07:19.050> HTTP<00:07:19.650> but<00:07:19.889> it<00:07:20.070> just<00:07:20.220> tells 00:07:20.420 --> 00:07:20.430 align:start position:0% having or 100 in HTTP but it just tells 00:07:20.430 --> 00:07:23.690 align:start position:0% having or 100 in HTTP but it just tells you<00:07:20.520> that<00:07:20.669> this<00:07:20.880> is<00:07:20.940> a<00:07:21.889> user<00:07:22.889> generated<00:07:23.370> or 00:07:23.690 --> 00:07:23.700 align:start position:0% you that this is a user generated or 00:07:23.700 --> 00:07:27.350 align:start position:0% you that this is a user generated or user<00:07:24.480> sign<00:07:24.780> error<00:07:25.110> pointer<00:07:26.210> with<00:07:27.210> no 00:07:27.350 --> 00:07:27.360 align:start position:0% user sign error pointer with no 00:07:27.360 --> 00:07:29.360 align:start position:0% user sign error pointer with no additional<00:07:27.720> context<00:07:28.590> so<00:07:28.770> this<00:07:28.919> one<00:07:29.100> just<00:07:29.130> like 00:07:29.360 --> 00:07:29.370 align:start position:0% additional context so this one just like 00:07:29.370 --> 00:07:31.909 align:start position:0% additional context so this one just like that<00:07:29.550> you<00:07:29.639> know<00:07:29.700> so<00:07:29.900> the<00:07:30.900> sheriff<00:07:31.230> takes<00:07:31.560> for 00:07:31.909 --> 00:07:31.919 align:start position:0% that you know so the sheriff takes for 00:07:31.919 --> 00:07:38.330 align:start position:0% that you know so the sheriff takes for the<00:07:32.130> reason 00:07:38.330 --> 00:07:38.340 align:start position:0% 00:07:38.340 --> 00:07:43.070 align:start position:0% this<00:07:39.060> rates<00:07:39.330> going<00:07:39.480> into<00:07:39.900> mini<00:07:40.200> table<00:07:41.300> so<00:07:42.300> it's 00:07:43.070 --> 00:07:43.080 align:start position:0% this rates going into mini table so it's 00:07:43.080 --> 00:07:45.770 align:start position:0% this rates going into mini table so it's actually<00:07:43.200> more<00:07:43.560> charging<00:07:43.980> this<00:07:44.160> is<00:07:44.460> all<00:07:45.150> odd 00:07:45.770 --> 00:07:45.780 align:start position:0% actually more charging this is all odd 00:07:45.780 --> 00:07:46.280 align:start position:0% actually more charging this is all odd numbers 00:07:46.280 --> 00:07:46.290 align:start position:0% numbers 00:07:46.290 --> 00:07:49.910 align:start position:0% numbers our<00:07:47.750> success<00:07:48.750> among<00:07:49.050> even<00:07:49.380> numbers<00:07:49.650> are 00:07:49.910 --> 00:07:49.920 align:start position:0% our success among even numbers are 00:07:49.920 --> 00:07:54.500 align:start position:0% our success among even numbers are failure<00:07:50.930> so<00:07:51.930> the<00:07:52.310> callings<00:07:53.310> are<00:07:53.580> categories 00:07:54.500 --> 00:07:54.510 align:start position:0% failure so the callings are categories 00:07:54.510 --> 00:07:56.470 align:start position:0% failure so the callings are categories so<00:07:54.810> things<00:07:55.020> like<00:07:55.200> time<00:07:55.470> logic<00:07:55.920> or 00:07:56.470 --> 00:07:56.480 align:start position:0% so things like time logic or 00:07:56.480 --> 00:07:59.600 align:start position:0% so things like time logic or authentication<00:07:57.480> or<00:07:58.410> negotiation<00:07:59.160> governance 00:07:59.600 --> 00:07:59.610 align:start position:0% authentication or negotiation governance 00:07:59.610 --> 00:08:01.760 align:start position:0% authentication or negotiation governance even<00:08:00.540> of<00:08:00.720> change<00:08:00.990> those<00:08:01.200> are<00:08:01.380> captured<00:08:01.680> on 00:08:01.760 --> 00:08:01.770 align:start position:0% even of change those are captured on 00:08:01.770 --> 00:08:05.660 align:start position:0% even of change those are captured on here<00:08:02.240> and<00:08:03.240> the<00:08:04.230> rows<00:08:04.530> are<00:08:04.560> really<00:08:05.130> so<00:08:05.190> you<00:08:05.430> can 00:08:05.660 --> 00:08:05.670 align:start position:0% here and the rows are really so you can 00:08:05.670 --> 00:08:08.990 align:start position:0% here and the rows are really so you can say<00:08:06.030> for<00:08:06.270> example<00:08:06.980> we<00:08:07.980> have<00:08:08.160> the<00:08:08.370> two<00:08:08.790> row 00:08:08.990 --> 00:08:09.000 align:start position:0% say for example we have the two row 00:08:09.000 --> 00:08:12.070 align:start position:0% say for example we have the two row which<00:08:09.330> is<00:08:09.920> searching<00:08:10.920> and<00:08:11.010> matching<00:08:11.400> and 00:08:12.070 --> 00:08:12.080 align:start position:0% which is searching and matching and 00:08:12.080 --> 00:08:16.240 align:start position:0% which is searching and matching and waiting<00:08:13.640> and<00:08:14.640> together<00:08:14.850> we<00:08:15.210> guess<00:08:15.390> that 00:08:16.240 --> 00:08:16.250 align:start position:0% waiting and together we guess that 00:08:16.250 --> 00:08:17.930 align:start position:0% waiting and together we guess that you're<00:08:17.250> awaiting<00:08:17.430> a<00:08:17.580> match 00:08:17.930 --> 00:08:17.940 align:start position:0% you're awaiting a match 00:08:17.940 --> 00:08:19.790 align:start position:0% you're awaiting a match so<00:08:18.030> both<00:08:18.330> we<00:08:18.600> can<00:08:18.630> do<00:08:18.810> this<00:08:19.020> you'll<00:08:19.500> read<00:08:19.770> that 00:08:19.790 --> 00:08:19.800 align:start position:0% so both we can do this you'll read that 00:08:19.800 --> 00:08:22.670 align:start position:0% so both we can do this you'll read that note<00:08:20.930> decompose<00:08:21.930> them<00:08:22.080> you<00:08:22.260> might<00:08:22.410> have<00:08:22.560> to 00:08:22.670 --> 00:08:22.680 align:start position:0% note decompose them you might have to 00:08:22.680 --> 00:08:27.320 align:start position:0% note decompose them you might have to memorize<00:08:23.840> 16<00:08:24.840> by<00:08:25.050> 16<00:08:25.340> so<00:08:26.340> 32<00:08:26.700> and<00:08:27.120> that's<00:08:27.180> why 00:08:27.320 --> 00:08:27.330 align:start position:0% memorize 16 by 16 so 32 and that's why 00:08:27.330 --> 00:08:31.420 align:start position:0% memorize 16 by 16 so 32 and that's why we<00:08:27.630> memorize<00:08:27.930> the<00:08:28.170> whole<00:08:28.200> 256<00:08:29.180> good<00:08:30.180> space 00:08:31.420 --> 00:08:31.430 align:start position:0% we memorize the whole 256 good space 00:08:31.430 --> 00:08:36.610 align:start position:0% we memorize the whole 256 good space there's<00:08:32.430> a<00:08:32.490> helper<00:08:32.730> library<00:08:33.090> as<00:08:33.720> well<00:08:34.430> on<00:08:35.430> NPM 00:08:36.610 --> 00:08:36.620 align:start position:0% there's a helper library as well on NPM 00:08:36.620 --> 00:08:40.160 align:start position:0% there's a helper library as well on NPM is<00:08:37.620> lets<00:08:38.340> you<00:08:38.520> write<00:08:38.910> these<00:08:39.210> in<00:08:39.540> a<00:08:39.900> more 00:08:40.160 --> 00:08:40.170 align:start position:0% is lets you write these in a more 00:08:40.170 --> 00:08:43.130 align:start position:0% is lets you write these in a more general<00:08:40.410> way<00:08:40.800> and<00:08:41.160> process<00:08:41.760> them<00:08:42.140> more 00:08:43.130 --> 00:08:43.140 align:start position:0% general way and process them more 00:08:43.140 --> 00:08:44.420 align:start position:0% general way and process them more programmatically<00:08:43.710> a<00:08:43.830> little<00:08:44.160> bit<00:08:44.280> more 00:08:44.420 --> 00:08:44.430 align:start position:0% programmatically a little bit more 00:08:44.430 --> 00:08:46.790 align:start position:0% programmatically a little bit more information<00:08:44.580> out<00:08:45.060> of<00:08:45.090> them<00:08:45.360> so<00:08:46.080> here<00:08:46.620> are<00:08:46.680> some 00:08:46.790 --> 00:08:46.800 align:start position:0% information out of them so here are some 00:08:46.800 --> 00:08:48.680 align:start position:0% information out of them so here are some emails<00:08:47.190> for<00:08:47.460> February<00:08:47.850> reason<00:08:48.270> that<00:08:48.390> you<00:08:48.540> can 00:08:48.680 --> 00:08:48.690 align:start position:0% emails for February reason that you can 00:08:48.690 --> 00:08:53.150 align:start position:0% emails for February reason that you can then<00:08:48.890> stick<00:08:49.890> together<00:08:51.470> pull<00:08:52.470> apart<00:08:52.800> and 00:08:53.150 --> 00:08:53.160 align:start position:0% then stick together pull apart and 00:08:53.160 --> 00:08:55.430 align:start position:0% then stick together pull apart and you're<00:08:54.150> just<00:08:54.330> going<00:08:54.480> to<00:08:54.510> also<00:08:54.810> say<00:08:54.990> like<00:08:55.200> you 00:08:55.430 --> 00:08:55.440 align:start position:0% you're just going to also say like you 00:08:55.440 --> 00:08:59.030 align:start position:0% you're just going to also say like you know<00:08:55.470> this<00:08:55.800> needs<00:08:56.040> to<00:08:56.190> be<00:08:57.200> category<00:08:58.200> four<00:08:58.620> and 00:08:59.030 --> 00:08:59.040 align:start position:0% know this needs to be category four and 00:08:59.040 --> 00:09:01.300 align:start position:0% know this needs to be category four and one<00:08:59.430> of<00:08:59.550> the<00:08:59.730> following<00:09:00.120> reasons<00:09:00.360> for<00:09:00.990> example 00:09:01.300 --> 00:09:01.310 align:start position:0% one of the following reasons for example 00:09:01.310 --> 00:09:06.230 align:start position:0% one of the following reasons for example and<00:09:02.310> you<00:09:02.580> can<00:09:02.610> also<00:09:02.910> automate<00:09:05.150> reverting<00:09:06.150> this 00:09:06.230 --> 00:09:06.240 align:start position:0% and you can also automate reverting this 00:09:06.240 --> 00:09:09.860 align:start position:0% and you can also automate reverting this also<00:09:06.450> reverse<00:09:07.110> are<00:09:07.610> built<00:09:08.610> right<00:09:08.790> in<00:09:09.030> full 00:09:09.860 --> 00:09:09.870 align:start position:0% also reverse are built right in full 00:09:09.870 --> 00:09:12.680 align:start position:0% also reverse are built right in full supports<00:09:10.430> in<00:09:11.430> this<00:09:11.610> case<00:09:11.790> this<00:09:11.970> require<00:09:12.330> okay 00:09:12.680 --> 00:09:12.690 align:start position:0% supports in this case this require okay 00:09:12.690 --> 00:09:14.960 align:start position:0% supports in this case this require okay says<00:09:13.020> it<00:09:13.290> needs<00:09:13.380> to<00:09:13.620> be<00:09:13.770> a<00:09:13.800> Ottoman<00:09:14.490> otherwise 00:09:14.960 --> 00:09:14.970 align:start position:0% says it needs to be a Ottoman otherwise 00:09:14.970 --> 00:09:17.330 align:start position:0% says it needs to be a Ottoman otherwise it<00:09:15.210> will<00:09:15.330> reverse<00:09:15.650> when<00:09:16.650> it<00:09:16.740> responds<00:09:17.160> back 00:09:17.330 --> 00:09:17.340 align:start position:0% it will reverse when it responds back 00:09:17.340 --> 00:09:19.220 align:start position:0% it will reverse when it responds back with<00:09:17.400> a<00:09:17.970> hardwood<00:09:18.330> message<00:09:18.720> we<00:09:18.930> can<00:09:19.050> also 00:09:19.220 --> 00:09:19.230 align:start position:0% with a hardwood message we can also 00:09:19.230 --> 00:09:22.390 align:start position:0% with a hardwood message we can also allow<00:09:19.560> any<00:09:19.770> messages<00:09:20.220> as<00:09:20.850> well<00:09:21.090> with 00:09:22.390 --> 00:09:22.400 align:start position:0% allow any messages as well with 00:09:22.400 --> 00:09:24.650 align:start position:0% allow any messages as well with localized<00:09:23.400> won't<00:09:23.730> change<00:09:23.880> my<00:09:24.030> station<00:09:24.450> which 00:09:24.650 --> 00:09:24.660 align:start position:0% localized won't change my station which 00:09:24.660 --> 00:09:25.340 align:start position:0% localized won't change my station which again 00:09:25.340 --> 00:09:25.350 align:start position:0% again 00:09:25.350 --> 00:09:29.820 align:start position:0% again the<00:09:26.350> end<00:09:27.030> so<00:09:28.030> a<00:09:28.450> toy<00:09:28.780> flow<00:09:29.260> for<00:09:29.500> contract 00:09:29.820 --> 00:09:29.830 align:start position:0% the end so a toy flow for contract 00:09:29.830 --> 00:09:37.710 align:start position:0% the end so a toy flow for contract messaging<00:09:33.600> so<00:09:34.600> we<00:09:34.690> have<00:09:34.870> 3d<00:09:36.390> three<00:09:37.390> players<00:09:37.630> in 00:09:37.710 --> 00:09:37.720 align:start position:0% messaging so we have 3d three players in 00:09:37.720 --> 00:09:40.590 align:start position:0% messaging so we have 3d three players in the<00:09:37.990> scenario<00:09:38.440> we<00:09:38.770> have<00:09:38.800> a<00:09:39.430> user<00:09:39.760> this<00:09:40.270> the 00:09:40.590 --> 00:09:40.600 align:start position:0% the scenario we have a user this the 00:09:40.600 --> 00:09:42.300 align:start position:0% the scenario we have a user this the robot<00:09:40.750> may<00:09:41.020> be<00:09:41.080> a<00:09:41.200> proxy<00:09:41.710> contractor<00:09:42.190> engaged 00:09:42.300 --> 00:09:42.310 align:start position:0% robot may be a proxy contractor engaged 00:09:42.310 --> 00:09:45.290 align:start position:0% robot may be a proxy contractor engaged themselves<00:09:42.870> to<00:09:43.870> intermediary<00:09:44.530> and<00:09:44.800> then<00:09:45.010> a 00:09:45.290 --> 00:09:45.300 align:start position:0% themselves to intermediary and then a 00:09:45.300 --> 00:09:50.580 align:start position:0% themselves to intermediary and then a token<00:09:46.350> we<00:09:47.350> ask<00:09:47.530> for<00:09:47.890> sending<00:09:48.790> my<00:09:48.940> request 00:09:50.580 --> 00:09:50.590 align:start position:0% token we ask for sending my request 00:09:50.590 --> 00:09:54.000 align:start position:0% token we ask for sending my request I<00:09:50.620> dropped<00:09:51.310> it<00:09:51.430> across<00:09:51.820> and<00:09:52.350> sashes<00:09:53.350> that<00:09:53.740> was 00:09:54.000 --> 00:09:54.010 align:start position:0% I dropped it across and sashes that was 00:09:54.010 --> 00:09:58.050 align:start position:0% I dropped it across and sashes that was something<00:09:54.250> you<00:09:54.280> know<00:09:54.460> this<00:09:56.640> this<00:09:57.640> drops<00:09:57.940> he 00:09:58.050 --> 00:09:58.060 align:start position:0% something you know this this drops he 00:09:58.060 --> 00:10:01.350 align:start position:0% something you know this this drops he asks<00:09:58.450> for<00:09:58.780> a<00:09:59.140> by<00:09:59.650> and<00:09:59.980> this<00:10:00.100> amounts<00:10:00.520> but<00:10:01.150> every 00:10:01.350 --> 00:10:01.360 align:start position:0% asks for a by and this amounts but every 00:10:01.360 --> 00:10:03.420 align:start position:0% asks for a by and this amounts but every consummate<00:10:01.810> you<00:10:02.230> know<00:10:02.350> we're<00:10:02.590> not<00:10:02.950> ready<00:10:03.160> yes 00:10:03.420 --> 00:10:03.430 align:start position:0% consummate you know we're not ready yes 00:10:03.430 --> 00:10:05.040 align:start position:0% consummate you know we're not ready yes but<00:10:03.880> we<00:10:04.000> will<00:10:04.150> pay<00:10:04.360> you<00:10:04.420> back<00:10:04.660> when<00:10:04.930> we're 00:10:05.040 --> 00:10:05.050 align:start position:0% but we will pay you back when we're 00:10:05.050 --> 00:10:05.310 align:start position:0% but we will pay you back when we're ready 00:10:05.310 --> 00:10:05.320 align:start position:0% ready 00:10:05.320 --> 00:10:06.930 align:start position:0% ready it's<00:10:05.410> just<00:10:05.620> all<00:10:05.830> Unchained<00:10:06.400> I'm<00:10:06.610> not<00:10:06.700> waiting 00:10:06.930 --> 00:10:06.940 align:start position:0% it's just all Unchained I'm not waiting 00:10:06.940 --> 00:10:10.350 align:start position:0% it's just all Unchained I'm not waiting for<00:10:08.190> events<00:10:09.190> or<00:10:09.280> anything<00:10:09.460> on<00:10:09.760> you<00:10:10.300> know 00:10:10.350 --> 00:10:10.360 align:start position:0% for events or anything on you know 00:10:10.360 --> 00:10:12.810 align:start position:0% for events or anything on you know keying<00:10:10.660> it<00:10:10.900> pulling<00:10:11.140> it<00:10:11.350> with<00:10:11.380> the<00:10:11.530> server<00:10:11.820> or 00:10:12.810 --> 00:10:12.820 align:start position:0% keying it pulling it with the server or 00:10:12.820 --> 00:10:15.270 align:start position:0% keying it pulling it with the server or staying<00:10:13.150> open<00:10:13.270> when<00:10:14.110> I'm<00:10:14.200> ready 00:10:15.270 --> 00:10:15.280 align:start position:0% staying open when I'm ready 00:10:15.280 --> 00:10:17.790 align:start position:0% staying open when I'm ready proxy<00:10:16.000> hold<00:10:16.570> on<00:10:16.720> to<00:10:16.810> that<00:10:16.930> and<00:10:17.200> then<00:10:17.260> probably 00:10:17.790 --> 00:10:17.800 align:start position:0% proxy hold on to that and then probably 00:10:17.800 --> 00:10:19.190 align:start position:0% proxy hold on to that and then probably guess<00:10:18.010> that<00:10:18.040> that<00:10:18.250> hurts<00:10:18.490> the<00:10:18.610> user 00:10:19.190 --> 00:10:19.200 align:start position:0% guess that that hurts the user 00:10:19.200 --> 00:10:24.090 align:start position:0% guess that that hurts the user sometimes<00:10:20.200> my<00:10:20.530> user<00:10:21.460> it<00:10:21.670> gets<00:10:23.100> gets 00:10:24.090 --> 00:10:24.100 align:start position:0% sometimes my user it gets gets 00:10:24.100 --> 00:10:25.680 align:start position:0% sometimes my user it gets gets interesting<00:10:24.640> as<00:10:24.730> it<00:10:24.850> is<00:10:24.940> this<00:10:25.090> done<00:10:25.450> yesterday 00:10:25.680 --> 00:10:25.690 align:start position:0% interesting as it is this done yesterday 00:10:25.690 --> 00:10:28.380 align:start position:0% interesting as it is this done yesterday saying<00:10:26.170> you<00:10:26.320> know<00:10:26.470> it's<00:10:27.370> done<00:10:27.580> yet<00:10:27.790> spend<00:10:28.120> says 00:10:28.380 --> 00:10:28.390 align:start position:0% saying you know it's done yet spend says 00:10:28.390 --> 00:10:29.610 align:start position:0% saying you know it's done yet spend says you<00:10:28.480> know<00:10:28.570> I<00:10:28.600> don't<00:10:28.870> have<00:10:29.110> to<00:10:29.200> go<00:10:29.290> and<00:10:29.440> check 00:10:29.610 --> 00:10:29.620 align:start position:0% you know I don't have to go and check 00:10:29.620 --> 00:10:31.980 align:start position:0% you know I don't have to go and check luscious<00:10:30.430> perverts<00:10:30.820> preparedness<00:10:31.720> this 00:10:31.980 --> 00:10:31.990 align:start position:0% luscious perverts preparedness this 00:10:31.990 --> 00:10:34.550 align:start position:0% luscious perverts preparedness this transaction<00:10:32.350> ever<00:10:32.560> happened<00:10:32.950> and<00:10:33.220> also<00:10:33.400> know 00:10:34.550 --> 00:10:34.560 align:start position:0% transaction ever happened and also know 00:10:34.560 --> 00:10:38.100 align:start position:0% transaction ever happened and also know sometimes<00:10:35.560> later<00:10:36.450> we<00:10:37.450> come<00:10:37.660> over<00:10:37.750> there<00:10:37.990> is 00:10:38.100 --> 00:10:38.110 align:start position:0% sometimes later we come over there is 00:10:38.110 --> 00:10:42.820 align:start position:0% sometimes later we come over there is maybe<00:10:40.380> were 00:10:42.820 --> 00:10:42.830 align:start position:0% maybe were 00:10:42.830 --> 00:10:45.640 align:start position:0% maybe were actually<00:10:43.160> watch<00:10:43.340> the<00:10:43.610> thing<00:10:43.850> and<00:10:44.470> it<00:10:45.470> says 00:10:45.640 --> 00:10:45.650 align:start position:0% actually watch the thing and it says 00:10:45.650 --> 00:10:47.770 align:start position:0% actually watch the thing and it says ready<00:10:46.130> you<00:10:46.610> know<00:10:46.730> are<00:10:47.030> you<00:10:47.090> still<00:10:47.150> interested 00:10:47.770 --> 00:10:47.780 align:start position:0% ready you know are you still interested 00:10:47.780 --> 00:10:49.930 align:start position:0% ready you know are you still interested and<00:10:48.380> yeah<00:10:48.590> I<00:10:48.620> mean<00:10:49.160> time<00:10:49.370> I<00:10:49.490> kind<00:10:49.760> of<00:10:49.820> much 00:10:49.930 --> 00:10:49.940 align:start position:0% and yeah I mean time I kind of much 00:10:49.940 --> 00:10:54.520 align:start position:0% and yeah I mean time I kind of much worse<00:10:50.240> come<00:10:50.510> in<00:10:51.040> rates<00:10:52.270> less<00:10:53.380> before<00:10:54.380> that 00:10:54.520 --> 00:10:54.530 align:start position:0% worse come in rates less before that 00:10:54.530 --> 00:10:56.740 align:start position:0% worse come in rates less before that that's<00:10:54.770> a<00:10:54.830> really<00:10:55.040> completed<00:10:55.520> and<00:10:55.910> probably 00:10:56.740 --> 00:10:56.750 align:start position:0% that's a really completed and probably 00:10:56.750 --> 00:10:59.320 align:start position:0% that's a really completed and probably assess<00:10:56.960> the<00:10:57.230> user<00:10:57.910> distancing<00:10:58.910> discussing 00:10:59.320 --> 00:10:59.330 align:start position:0% assess the user distancing discussing 00:10:59.330 --> 00:11:02.320 align:start position:0% assess the user distancing discussing recently<00:10:59.420> about<00:10:59.900> adding<00:11:00.910> messaging<00:11:01.910> like 00:11:02.320 --> 00:11:02.330 align:start position:0% recently about adding messaging like 00:11:02.330 --> 00:11:04.600 align:start position:0% recently about adding messaging like this<00:11:02.780> you<00:11:03.110> know<00:11:03.200> an<00:11:03.410> inbox<00:11:03.830> or<00:11:04.160> while<00:11:04.340> you<00:11:04.490> were 00:11:04.600 --> 00:11:04.610 align:start position:0% this you know an inbox or while you were 00:11:04.610 --> 00:11:08.850 align:start position:0% this you know an inbox or while you were away<00:11:04.730> from<00:11:05.000> the<00:11:05.060> chain<00:11:05.300> to<00:11:06.050> the<00:11:06.580> chibok<00:11:07.580> chain 00:11:08.850 --> 00:11:08.860 align:start position:0% away from the chain to the chibok chain 00:11:08.860 --> 00:11:12.070 align:start position:0% away from the chain to the chibok chain or<00:11:09.860> into<00:11:10.430> wallets<00:11:10.730> rather<00:11:10.940> and<00:11:11.570> then<00:11:11.690> we<00:11:11.960> can 00:11:12.070 --> 00:11:12.080 align:start position:0% or into wallets rather and then we can 00:11:12.080 --> 00:11:13.930 align:start position:0% or into wallets rather and then we can then<00:11:12.230> propagate<00:11:12.680> that<00:11:12.830> into<00:11:13.640> that<00:11:13.730> system 00:11:13.930 --> 00:11:13.940 align:start position:0% then propagate that into that system 00:11:13.940 --> 00:11:19.420 align:start position:0% then propagate that into that system school<00:11:17.050> or<00:11:18.050> stateless<00:11:18.620> service<00:11:18.890> contracts 00:11:19.420 --> 00:11:19.430 align:start position:0% school or stateless service contracts 00:11:19.430 --> 00:11:25.720 align:start position:0% school or stateless service contracts against<00:11:20.240> Ivan<00:11:20.750> Bishop<00:11:21.410> library<00:11:21.770> code<00:11:24.730> either 00:11:25.720 --> 00:11:25.730 align:start position:0% against Ivan Bishop library code either 00:11:25.730 --> 00:11:26.800 align:start position:0% against Ivan Bishop library code either actually<00:11:26.090> before<00:11:26.210> if<00:11:26.450> you<00:11:26.540> override 00:11:26.800 --> 00:11:26.810 align:start position:0% actually before if you override 00:11:26.810 --> 00:11:29.980 align:start position:0% actually before if you override functions<00:11:27.380> on<00:11:27.650> a<00:11:28.480> library<00:11:29.480> you<00:11:29.660> just<00:11:29.720> guess 00:11:29.980 --> 00:11:29.990 align:start position:0% functions on a library you just guess 00:11:29.990 --> 00:11:31.750 align:start position:0% functions on a library you just guess women<00:11:30.290> absolutely<00:11:30.560> library<00:11:31.310> they<00:11:31.550> say<00:11:31.700> you 00:11:31.750 --> 00:11:31.760 align:start position:0% women absolutely library they say you 00:11:31.760 --> 00:11:33.940 align:start position:0% women absolutely library they say you know<00:11:31.880> it's<00:11:32.000> been<00:11:32.180> all<00:11:32.480> I'll<00:11:33.320> check<00:11:33.590> -<00:11:33.740> no<00:11:33.830> I'm 00:11:33.940 --> 00:11:33.950 align:start position:0% know it's been all I'll check - no I'm 00:11:33.950 --> 00:11:35.770 align:start position:0% know it's been all I'll check - no I'm good<00:11:34.130> and<00:11:34.370> then<00:11:34.460> it<00:11:34.550> starts<00:11:34.880> overriding 00:11:35.770 --> 00:11:35.780 align:start position:0% good and then it starts overriding 00:11:35.780 --> 00:11:39.310 align:start position:0% good and then it starts overriding methods<00:11:36.370> that<00:11:37.370> audit<00:11:37.880> you<00:11:38.120> no<00:11:38.210> longer<00:11:38.390> wolves 00:11:39.310 --> 00:11:39.320 align:start position:0% methods that audit you no longer wolves 00:11:39.320 --> 00:11:42.460 align:start position:0% methods that audit you no longer wolves he<00:11:39.590> may<00:11:40.100> have<00:11:40.280> broken<00:11:40.430> something<00:11:41.140> he<00:11:42.140> made<00:11:42.440> a 00:11:42.460 --> 00:11:42.470 align:start position:0% he may have broken something he made a 00:11:42.470 --> 00:11:44.140 align:start position:0% he may have broken something he made a small<00:11:42.830> change<00:11:42.890> like<00:11:43.430> changing<00:11:43.580> the<00:11:43.940> name<00:11:44.090> of 00:11:44.140 --> 00:11:44.150 align:start position:0% small change like changing the name of 00:11:44.150 --> 00:11:46.000 align:start position:0% small change like changing the name of the<00:11:44.240> token<00:11:44.570> that's<00:11:45.020> probably<00:11:45.470> fine<00:11:45.710> I<00:11:45.740> see 00:11:46.000 --> 00:11:46.010 align:start position:0% the token that's probably fine I see 00:11:46.010 --> 00:11:50.350 align:start position:0% the token that's probably fine I see start<00:11:46.220> taking<00:11:46.550> behavior<00:11:47.030> a<00:11:47.330> few<00:11:48.110> notes<00:11:49.330> if<00:11:50.330> you 00:11:50.350 --> 00:11:50.360 align:start position:0% start taking behavior a few notes if you 00:11:50.360 --> 00:11:52.660 align:start position:0% start taking behavior a few notes if you deploy<00:11:50.930> these<00:11:51.200> on<00:11:51.710> chains<00:11:52.040> that<00:11:52.370> people 00:11:52.660 --> 00:11:52.670 align:start position:0% deploy these on chains that people 00:11:52.670 --> 00:11:55.540 align:start position:0% deploy these on chains that people high-value<00:11:53.390> components<00:11:54.320> we're<00:11:55.160> doing<00:11:55.340> things 00:11:55.540 --> 00:11:55.550 align:start position:0% high-value components we're doing things 00:11:55.550 --> 00:11:59.580 align:start position:0% high-value components we're doing things with<00:11:56.000> finance<00:11:56.420> and<00:11:56.780> criticism<00:11:57.650> installers 00:11:59.580 --> 00:11:59.590 align:start position:0% with finance and criticism installers 00:11:59.590 --> 00:12:02.370 align:start position:0% with finance and criticism installers then<00:12:00.590> we've<00:12:00.890> met<00:12:01.130> use<00:12:01.310> as<00:12:01.640> a<00:12:01.760> community 00:12:02.370 --> 00:12:02.380 align:start position:0% then we've met use as a community 00:12:02.380 --> 00:12:05.710 align:start position:0% then we've met use as a community verified<00:12:03.380> and<00:12:03.710> checked<00:12:04.240> and<00:12:05.240> then<00:12:05.390> they<00:12:05.510> live 00:12:05.710 --> 00:12:05.720 align:start position:0% verified and checked and then they live 00:12:05.720 --> 00:12:08.980 align:start position:0% verified and checked and then they live on<00:12:05.990> chain<00:12:06.320> and<00:12:06.850> don't<00:12:07.850> get<00:12:08.030> changed<00:12:08.600> so<00:12:08.810> we 00:12:08.980 --> 00:12:08.990 align:start position:0% on chain and don't get changed so we 00:12:08.990 --> 00:12:11.200 align:start position:0% on chain and don't get changed so we know<00:12:09.320> that<00:12:09.500> this<00:12:09.680> is<00:12:09.830> the<00:12:09.950> exact<00:12:10.280> code<00:12:10.640> that<00:12:11.120> we 00:12:11.200 --> 00:12:11.210 align:start position:0% know that this is the exact code that we 00:12:11.210 --> 00:12:15.820 align:start position:0% know that this is the exact code that we expect<00:12:13.180> why<00:12:14.180> not<00:12:14.480> interesting<00:12:15.260> I'm<00:12:15.680> not 00:12:15.820 --> 00:12:15.830 align:start position:0% expect why not interesting I'm not 00:12:15.830 --> 00:12:17.770 align:start position:0% expect why not interesting I'm not really<00:12:16.010> play<00:12:16.190> safe<00:12:16.370> out<00:12:16.550> safe<00:12:16.790> and<00:12:17.360> this<00:12:17.570> gives 00:12:17.770 --> 00:12:17.780 align:start position:0% really play safe out safe and this gives 00:12:17.780 --> 00:12:19.000 align:start position:0% really play safe out safe and this gives us<00:12:17.930> so<00:12:18.080> much 00:12:19.000 --> 00:12:19.010 align:start position:0% us so much 00:12:19.010 --> 00:12:21.490 align:start position:0% us so much it's<00:12:19.880> intractable<00:12:20.630> because<00:12:20.960> don't<00:12:21.230> feel 00:12:21.490 --> 00:12:21.500 align:start position:0% it's intractable because don't feel 00:12:21.500 --> 00:12:23.530 align:start position:0% it's intractable because don't feel cheap<00:12:21.710> and<00:12:21.980> a<00:12:22.220> call<00:12:22.430> out<00:12:22.640> is<00:12:22.940> more<00:12:23.240> expensive 00:12:23.530 --> 00:12:23.540 align:start position:0% cheap and a call out is more expensive 00:12:23.540 --> 00:12:29.850 align:start position:0% cheap and a call out is more expensive but<00:12:24.230> for<00:12:24.410> anything<00:12:24.650> more<00:12:27.310> involved<00:12:28.310> that's 00:12:29.850 --> 00:12:29.860 align:start position:0% but for anything more involved that's 00:12:29.860 --> 00:12:34.960 align:start position:0% but for anything more involved that's effectively<00:12:32.050> so<00:12:33.050> here's<00:12:33.440> a<00:12:33.730> simple<00:12:34.730> toy 00:12:34.960 --> 00:12:34.970 align:start position:0% effectively so here's a simple toy 00:12:34.970 --> 00:12:37.960 align:start position:0% effectively so here's a simple toy example<00:12:35.480> so<00:12:35.630> we<00:12:35.750> have<00:12:35.780> a<00:12:36.320> token<00:12:37.310> which<00:12:37.490> is<00:12:37.730> just 00:12:37.960 --> 00:12:37.970 align:start position:0% example so we have a token which is just 00:12:37.970 --> 00:12:39.360 align:start position:0% example so we have a token which is just the<00:12:38.060> things<00:12:38.270> that<00:12:38.390> do<00:12:38.480> normally<00:12:38.840> override 00:12:39.360 --> 00:12:39.370 align:start position:0% the things that do normally override 00:12:39.370 --> 00:12:43.900 align:start position:0% the things that do normally override calls<00:12:40.370> out<00:12:40.520> into<00:12:40.820> a<00:12:40.850> stateless<00:12:41.270> your<00:12:41.690> 20<00:12:42.910> makes 00:12:43.900 --> 00:12:43.910 align:start position:0% calls out into a stateless your 20 makes 00:12:43.910 --> 00:12:47.530 align:start position:0% calls out into a stateless your 20 makes requests<00:12:44.480> well<00:12:45.440> you<00:12:45.710> have<00:12:46.060> you're<00:12:47.060> in<00:12:47.390> the 00:12:47.530 --> 00:12:47.540 align:start position:0% requests well you have you're in the 00:12:47.540 --> 00:12:54.670 align:start position:0% requests well you have you're in the range<00:12:47.720> to<00:12:48.170> do<00:12:48.290> that<00:12:51.220> and<00:12:52.220> then<00:12:53.350> we<00:12:54.350> can<00:12:54.500> check 00:12:54.670 --> 00:12:54.680 align:start position:0% range to do that and then we can check 00:12:54.680 --> 00:12:57.820 align:start position:0% range to do that and then we can check with<00:12:55.100> say<00:12:55.850> here's<00:12:56.390> the<00:12:56.480> number<00:12:56.720> two<00:12:56.960> is<00:12:57.560> the 00:12:57.820 --> 00:12:57.830 align:start position:0% with say here's the number two is the 00:12:57.830 --> 00:12:59.800 align:start position:0% with say here's the number two is the distress<00:12:58.280> were<00:12:58.460> restricted<00:12:58.940> and<00:12:59.180> is<00:12:59.630> saying 00:12:59.800 --> 00:12:59.810 align:start position:0% distress were restricted and is saying 00:12:59.810 --> 00:13:03.130 align:start position:0% distress were restricted and is saying actually<00:13:00.020> this<00:13:01.600> the<00:13:02.600> person<00:13:02.900> trying<00:13:03.080> to 00:13:03.130 --> 00:13:03.140 align:start position:0% actually this the person trying to 00:13:03.140 --> 00:13:05.740 align:start position:0% actually this the person trying to transfer<00:13:03.530> students<00:13:03.950> the<00:13:04.130> bands<00:13:04.630> love<00:13:05.630> to 00:13:05.740 --> 00:13:05.750 align:start position:0% transfer students the bands love to 00:13:05.750 --> 00:13:07.510 align:start position:0% transfer students the bands love to transactions<00:13:06.350> were<00:13:06.470> a<00:13:06.650> few<00:13:06.800> things<00:13:06.980> out<00:13:07.160> into 00:13:07.510 --> 00:13:07.520 align:start position:0% transactions were a few things out into 00:13:07.520 --> 00:13:10.630 align:start position:0% transactions were a few things out into reusable<00:13:07.670> components<00:13:08.530> that<00:13:09.530> neither<00:13:09.830> to<00:13:10.100> even 00:13:10.630 --> 00:13:10.640 align:start position:0% reusable components that neither to even 00:13:10.640 --> 00:13:16.750 align:start position:0% reusable components that neither to even be<00:13:11.440> which<00:13:12.440> will<00:13:12.560> look<00:13:12.650> at<00:13:12.830> annoyance<00:13:13.250> a<00:13:15.760> you 00:13:16.750 --> 00:13:16.760 align:start position:0% be which will look at annoyance a you 00:13:16.760 --> 00:13:18.520 align:start position:0% be which will look at annoyance a you know<00:13:16.850> a<00:13:16.910> pricey<00:13:17.420> service<00:13:17.750> let's<00:13:17.960> say<00:13:18.140> it's<00:13:18.380> but 00:13:18.520 --> 00:13:18.530 align:start position:0% know a pricey service let's say it's but 00:13:18.530 --> 00:13:20.050 align:start position:0% know a pricey service let's say it's but you<00:13:18.650> don't<00:13:18.800> have<00:13:18.890> to<00:13:18.980> give<00:13:19.100> us<00:13:19.220> the<00:13:19.340> in<00:13:19.640> each<00:13:19.880> to 00:13:20.050 --> 00:13:20.060 align:start position:0% you don't have to give us the in each to 00:13:20.060 --> 00:13:22.750 align:start position:0% you don't have to give us the in each to our<00:13:20.150> contract<00:13:20.630> you<00:13:20.900> can<00:13:21.080> just<00:13:21.610> send<00:13:22.610> that<00:13:22.640> out 00:13:22.750 --> 00:13:22.760 align:start position:0% our contract you can just send that out 00:13:22.760 --> 00:13:26.640 align:start position:0% our contract you can just send that out to<00:13:22.880> another<00:13:23.740> another<00:13:24.740> service<00:13:25.040> provider 00:13:26.640 --> 00:13:26.650 align:start position:0% to another another service provider 00:13:26.650 --> 00:13:31.090 align:start position:0% to another another service provider which<00:13:27.650> is<00:13:27.680> a<00:13:28.130> staple<00:13:28.430> service<00:13:29.180> contract<00:13:30.100> so 00:13:31.090 --> 00:13:31.100 align:start position:0% which is a staple service contract so 00:13:31.100 --> 00:13:32.590 align:start position:0% which is a staple service contract so sometimes<00:13:31.430> it's<00:13:31.610> not<00:13:31.640> the<00:13:31.760> behavior<00:13:32.120> that's 00:13:32.590 --> 00:13:32.600 align:start position:0% sometimes it's not the behavior that's 00:13:32.600 --> 00:13:34.270 align:start position:0% sometimes it's not the behavior that's deeper<00:13:32.900> than<00:13:32.930> smart<00:13:33.470> contract<00:13:33.830> with<00:13:33.950> the<00:13:34.040> data 00:13:34.270 --> 00:13:34.280 align:start position:0% deeper than smart contract with the data 00:13:34.280 --> 00:13:38.940 align:start position:0% deeper than smart contract with the data inside<00:13:34.730> us<00:13:34.910> and<00:13:35.350> calling<00:13:36.350> into<00:13:36.680> that<00:13:36.830> might<00:13:37.070> be 00:13:38.940 --> 00:13:38.950 align:start position:0% inside us and calling into that might be 00:13:38.950 --> 00:13:42.240 align:start position:0% inside us and calling into that might be valuable<00:13:40.000> not<00:13:41.000> just<00:13:41.240> that<00:13:41.390> you<00:13:41.510> don't<00:13:41.630> have<00:13:41.780> to 00:13:42.240 --> 00:13:42.250 align:start position:0% valuable not just that you don't have to 00:13:42.250 --> 00:13:44.710 align:start position:0% valuable not just that you don't have to you<00:13:43.250> know<00:13:43.370> okay<00:13:43.550> let's<00:13:43.730> see<00:13:43.850> users<00:13:44.150> running 00:13:44.710 --> 00:13:44.720 align:start position:0% you know okay let's see users running 00:13:44.720 --> 00:13:51.880 align:start position:0% you know okay let's see users running her<00:13:46.540> purse<00:13:47.540> hoping<00:13:47.900> basis<00:13:48.290> but<00:13:49.600> so<00:13:50.600> that's<00:13:50.890> you 00:13:51.880 --> 00:13:51.890 align:start position:0% her purse hoping basis but so that's you 00:13:51.890 --> 00:13:53.500 align:start position:0% her purse hoping basis but so that's you have<00:13:52.040> to<00:13:52.220> do<00:13:52.310> that<00:13:52.460> all<00:13:52.670> you<00:13:52.700> worry<00:13:53.270> about<00:13:53.300> is 00:13:53.500 --> 00:13:53.510 align:start position:0% have to do that all you worry about is 00:13:53.510 --> 00:13:56.910 align:start position:0% have to do that all you worry about is amazement<00:13:54.020> kose<00:13:54.440> once<00:13:54.680> they're<00:13:55.190> good<00:13:55.340> to<00:13:55.430> go 00:13:56.910 --> 00:13:56.920 align:start position:0% amazement kose once they're good to go 00:13:56.920 --> 00:14:00.760 align:start position:0% amazement kose once they're good to go so<00:13:58.510> in<00:13:59.510> this<00:13:59.630> development<00:13:59.840> okay 00:14:00.760 --> 00:14:00.770 align:start position:0% so in this development okay 00:14:00.770 --> 00:14:02.530 align:start position:0% so in this development okay it<00:14:00.980> checks<00:14:01.250> upon<00:14:01.580> these<00:14:01.730> halloweeners<00:14:02.180> of 00:14:02.530 --> 00:14:02.540 align:start position:0% it checks upon these halloweeners of 00:14:02.540 --> 00:14:05.650 align:start position:0% it checks upon these halloweeners of thinking<00:14:02.810> a<00:14:02.870> message<00:14:03.490> and<00:14:04.490> it's<00:14:05.270> actually<00:14:05.630> a 00:14:05.650 --> 00:14:05.660 align:start position:0% thinking a message and it's actually a 00:14:05.660 --> 00:14:08.860 align:start position:0% thinking a message and it's actually a real-world<00:14:05.900> scenario<00:14:06.760> from 00:14:08.860 --> 00:14:08.870 align:start position:0% real-world scenario from 00:14:08.870 --> 00:14:11.340 align:start position:0% real-world scenario from so<00:14:09.320> we<00:14:09.410> have<00:14:09.590> prosper<00:14:10.250> or<00:14:10.280> trade<00:14:10.640> each<00:14:10.940> pain 00:14:11.340 --> 00:14:11.350 align:start position:0% so we have prosper or trade each pain 00:14:11.350 --> 00:14:15.040 align:start position:0% so we have prosper or trade each pain Canada<00:14:12.350> and<00:14:12.730> South<00:14:13.730> Korea<00:14:14.000> and<00:14:14.240> they<00:14:14.840> both 00:14:15.040 --> 00:14:15.050 align:start position:0% Canada and South Korea and they both 00:14:15.050 --> 00:14:16.840 align:start position:0% Canada and South Korea and they both have<00:14:15.290> different<00:14:15.620> regulatory<00:14:16.070> requirements 00:14:16.840 --> 00:14:16.850 align:start position:0% have different regulatory requirements 00:14:16.850 --> 00:14:18.100 align:start position:0% have different regulatory requirements and<00:14:16.910> you<00:14:17.030> need<00:14:17.150> to<00:14:17.240> be<00:14:17.300> able<00:14:17.360> to<00:14:17.450> match<00:14:17.630> both<00:14:17.900> of 00:14:18.100 --> 00:14:18.110 align:start position:0% and you need to be able to match both of 00:14:18.110 --> 00:14:19.690 align:start position:0% and you need to be able to match both of them<00:14:18.260> and<00:14:18.740> this<00:14:18.920> requirement<00:14:19.220> sometimes 00:14:19.690 --> 00:14:19.700 align:start position:0% them and this requirement sometimes 00:14:19.700 --> 00:14:24.660 align:start position:0% them and this requirement sometimes change<00:14:20.060> so<00:14:20.990> you<00:14:21.320> need<00:14:21.590> to<00:14:21.770> be<00:14:21.920> able<00:14:22.010> to<00:14:22.220> keep 00:14:24.660 --> 00:14:24.670 align:start position:0% 00:14:24.670 --> 00:14:28.870 align:start position:0% just<00:14:25.670> call<00:14:25.880> out<00:14:26.120> to<00:14:26.600> a<00:14:27.320> contract<00:14:28.310> rate<00:14:28.460> the 00:14:28.870 --> 00:14:28.880 align:start position:0% just call out to a contract rate the 00:14:28.880 --> 00:14:30.990 align:start position:0% just call out to a contract rate the independent<00:14:29.510> logic<00:14:29.780> is<00:14:29.900> is<00:14:30.140> kept<00:14:30.410> separately 00:14:30.990 --> 00:14:31.000 align:start position:0% independent logic is is kept separately 00:14:31.000 --> 00:14:34.150 align:start position:0% independent logic is is kept separately so<00:14:32.000> you<00:14:32.030> call<00:14:32.600> upstream<00:14:33.080> money<00:14:33.350> comes<00:14:34.100> back 00:14:34.150 --> 00:14:34.160 align:start position:0% so you call upstream money comes back 00:14:34.160 --> 00:14:37.560 align:start position:0% so you call upstream money comes back and<00:14:34.490> says<00:14:34.610> yes<00:14:35.000> you<00:14:35.750> know<00:14:35.960> you're<00:14:36.230> in<00:14:36.590> the 00:14:37.560 --> 00:14:37.570 align:start position:0% and says yes you know you're in the 00:14:37.570 --> 00:14:40.540 align:start position:0% and says yes you know you're in the meantime<00:14:38.570> they're<00:14:39.050> about<00:14:39.170> to<00:14:39.290> expire<00:14:39.620> don't 00:14:40.540 --> 00:14:40.550 align:start position:0% meantime they're about to expire don't 00:14:40.550 --> 00:14:42.040 align:start position:0% meantime they're about to expire don't worry<00:14:40.760> about<00:14:40.880> checking<00:14:41.180> this<00:14:41.450> other<00:14:41.660> service 00:14:42.040 --> 00:14:42.050 align:start position:0% worry about checking this other service 00:14:42.050 --> 00:14:43.450 align:start position:0% worry about checking this other service now<00:14:42.200> because<00:14:42.560> we<00:14:42.680> don't<00:14:42.770> mean<00:14:42.980> to<00:14:43.010> check<00:14:43.310> for 00:14:43.450 --> 00:14:43.460 align:start position:0% now because we don't mean to check for 00:14:43.460 --> 00:14:45.700 align:start position:0% now because we don't mean to check for override<00:14:43.940> they're<00:14:44.720> actually<00:14:45.260> you<00:14:45.650> know 00:14:45.700 --> 00:14:45.710 align:start position:0% override they're actually you know 00:14:45.710 --> 00:14:47.950 align:start position:0% override they're actually you know they're<00:14:46.010> they're<00:14:46.490> okay<00:14:46.790> and<00:14:47.000> then<00:14:47.630> we<00:14:47.750> each 00:14:47.950 --> 00:14:47.960 align:start position:0% they're they're okay and then we each 00:14:47.960 --> 00:14:49.870 align:start position:0% they're they're okay and then we each other<00:14:48.200> the<00:14:48.410> other<00:14:48.440> regulator<00:14:49.070> which<00:14:49.520> calls<00:14:49.760> me 00:14:49.870 --> 00:14:49.880 align:start position:0% other the other regulator which calls me 00:14:49.880 --> 00:14:54.310 align:start position:0% other the other regulator which calls me to<00:14:50.060> do<00:14:50.150> some<00:14:51.190> some<00:14:52.190> database<00:14:52.900> you<00:14:53.900> know<00:14:53.990> we<00:14:54.230> get 00:14:54.310 --> 00:14:54.320 align:start position:0% to do some some database you know we get 00:14:54.320 --> 00:14:55.150 align:start position:0% to do some some database you know we get back<00:14:54.530> yes 00:14:55.150 --> 00:14:55.160 align:start position:0% back yes 00:14:55.160 --> 00:14:56.700 align:start position:0% back yes you<00:14:55.310> know<00:14:55.400> they're<00:14:55.700> in<00:14:55.850> the<00:14:55.940> database 00:14:56.700 --> 00:14:56.710 align:start position:0% you know they're in the database 00:14:56.710 --> 00:15:00.550 align:start position:0% you know they're in the database probably<00:14:57.710> a<00:14:57.800> more<00:14:58.460> specific<00:14:59.360> error<00:14:59.780> for<00:15:00.260> this 00:15:00.550 --> 00:15:00.560 align:start position:0% probably a more specific error for this 00:15:00.560 --> 00:15:02.800 align:start position:0% probably a more specific error for this use<00:15:01.040> case<00:15:01.070> so<00:15:02.030> doesn't<00:15:02.330> have<00:15:02.420> to<00:15:02.510> probably<00:15:02.660> get 00:15:02.800 --> 00:15:02.810 align:start position:0% use case so doesn't have to probably get 00:15:02.810 --> 00:15:04.630 align:start position:0% use case so doesn't have to probably get the<00:15:02.960> exact<00:15:03.290> same<00:15:03.470> message<00:15:03.680> we<00:15:04.040> can<00:15:04.220> change<00:15:04.520> it 00:15:04.630 --> 00:15:04.640 align:start position:0% the exact same message we can change it 00:15:04.640 --> 00:15:14.210 align:start position:0% the exact same message we can change it as<00:15:04.730> we<00:15:04.820> go<00:15:05.000> and<00:15:05.450> then<00:15:06.230> come<00:15:06.380> back<00:15:06.410> with<00:15:06.740> yes 00:15:14.210 --> 00:15:14.220 align:start position:0% 00:15:14.220 --> 00:15:17.790 align:start position:0% some<00:15:15.220> quick<00:15:15.790> thoughts<00:15:15.940> on<00:15:16.149> making<00:15:16.510> money<00:15:16.800> with 00:15:17.790 --> 00:15:17.800 align:start position:0% some quick thoughts on making money with 00:15:17.800 --> 00:15:20.730 align:start position:0% some quick thoughts on making money with this<00:15:18.010> so<00:15:18.459> it's<00:15:19.029> a<00:15:19.149> thick<00:15:19.300> you<00:15:19.420> camps<00:15:19.899> or<00:15:20.529> that 00:15:20.730 --> 00:15:20.740 align:start position:0% this so it's a thick you camps or that 00:15:20.740 --> 00:15:22.290 align:start position:0% this so it's a thick you camps or that people<00:15:20.890> aren't<00:15:21.220> charging<00:15:21.730> for<00:15:21.970> a<00:15:22.000> bunch<00:15:22.209> of 00:15:22.290 --> 00:15:22.300 align:start position:0% people aren't charging for a bunch of 00:15:22.300 --> 00:15:25.440 align:start position:0% people aren't charging for a bunch of calls<00:15:22.480> today<00:15:22.660> you<00:15:23.320> can<00:15:23.740> in<00:15:24.279> people<00:15:24.519> are<00:15:24.820> as 00:15:25.440 --> 00:15:25.450 align:start position:0% calls today you can in people are as 00:15:25.450 --> 00:15:28.160 align:start position:0% calls today you can in people are as presidents<00:15:25.930> don't<00:15:26.050> have<00:15:26.200> any<00:15:26.410> more<00:15:26.560> often 00:15:28.160 --> 00:15:28.170 align:start position:0% presidents don't have any more often 00:15:28.170 --> 00:15:31.800 align:start position:0% presidents don't have any more often especially<00:15:29.170> with<00:15:29.709> I've<00:15:30.310> heard<00:15:30.810> fairly 00:15:31.800 --> 00:15:31.810 align:start position:0% especially with I've heard fairly 00:15:31.810 --> 00:15:33.630 align:start position:0% especially with I've heard fairly recently<00:15:32.170> that<00:15:32.350> state<00:15:32.529> rent<00:15:32.709> is<00:15:32.920> now<00:15:33.130> not 00:15:33.630 --> 00:15:33.640 align:start position:0% recently that state rent is now not 00:15:33.640 --> 00:15:38.420 align:start position:0% recently that state rent is now not happening<00:15:34.029> but<00:15:34.750> it's<00:15:35.050> not<00:15:35.410> entirely<00:15:36.690> a 00:15:38.420 --> 00:15:38.430 align:start position:0% happening but it's not entirely a 00:15:38.430 --> 00:15:40.980 align:start position:0% happening but it's not entirely a terrible<00:15:39.430> idea<00:15:39.519> in<00:15:40.029> collecting<00:15:40.570> things<00:15:40.720> off 00:15:40.980 --> 00:15:40.990 align:start position:0% terrible idea in collecting things off 00:15:40.990 --> 00:15:43.350 align:start position:0% terrible idea in collecting things off chain<00:15:41.350> or<00:15:42.070> getting<00:15:42.640> things<00:15:42.760> off<00:15:43.000> chain<00:15:43.209> that 00:15:43.350 --> 00:15:43.360 align:start position:0% chain or getting things off chain that 00:15:43.360 --> 00:15:45.690 align:start position:0% chain or getting things off chain that hard<00:15:43.540> to<00:15:43.660> use<00:15:43.720> very<00:15:44.050> much<00:15:44.230> or<00:15:44.649> I<00:15:45.010> don't<00:15:45.490> know 00:15:45.690 --> 00:15:45.700 align:start position:0% hard to use very much or I don't know 00:15:45.700 --> 00:15:47.310 align:start position:0% hard to use very much or I don't know high<00:15:45.910> value<00:15:46.209> so<00:15:46.390> in<00:15:46.510> the<00:15:46.570> money<00:15:46.779> like<00:15:47.019> this<00:15:47.170> we 00:15:47.310 --> 00:15:47.320 align:start position:0% high value so in the money like this we 00:15:47.320 --> 00:15:49.259 align:start position:0% high value so in the money like this we makes<00:15:47.560> sense<00:15:48.250> to<00:15:48.490> some<00:15:48.670> degree<00:15:48.940> where<00:15:49.120> you 00:15:49.259 --> 00:15:49.269 align:start position:0% makes sense to some degree where you 00:15:49.269 --> 00:15:52.740 align:start position:0% makes sense to some degree where you collect<00:15:49.829> value<00:15:51.060> to<00:15:52.060> prove<00:15:52.360> that<00:15:52.570> you<00:15:52.720> are 00:15:52.740 --> 00:15:52.750 align:start position:0% collect value to prove that you are 00:15:52.750 --> 00:15:55.850 align:start position:0% collect value to prove that you are valuable<00:15:53.350> but<00:15:53.800> even<00:15:54.100> without<00:15:54.310> us<00:15:54.610> we<00:15:55.329> can 00:15:55.850 --> 00:15:55.860 align:start position:0% valuable but even without us we can 00:15:55.860 --> 00:15:59.400 align:start position:0% valuable but even without us we can support<00:15:56.860> the<00:15:57.510> development<00:15:58.510> efforts<00:15:58.870> of<00:15:59.050> high 00:15:59.400 --> 00:15:59.410 align:start position:0% support the development efforts of high 00:15:59.410 --> 00:16:02.069 align:start position:0% support the development efforts of high quality<00:15:59.890> good<00:16:00.130> Ottoman<00:16:00.640> and<00:16:00.820> pay<00:16:01.450> for<00:16:01.510> the 00:16:02.069 --> 00:16:02.079 align:start position:0% quality good Ottoman and pay for the 00:16:02.079 --> 00:16:05.300 align:start position:0% quality good Ottoman and pay for the auditing<00:16:02.470> of<00:16:02.769> these<00:16:03.339> shared<00:16:03.640> smart<00:16:03.910> contracts 00:16:05.300 --> 00:16:05.310 align:start position:0% auditing of these shared smart contracts 00:16:05.310 --> 00:16:09.990 align:start position:0% auditing of these shared smart contracts so<00:16:06.310> that's<00:16:07.410> we<00:16:08.410> have<00:16:08.620> a<00:16:08.740> better<00:16:09.459> oil<00:16:09.640> secure 00:16:09.990 --> 00:16:10.000 align:start position:0% so that's we have a better oil secure 00:16:10.000 --> 00:16:11.699 align:start position:0% so that's we have a better oil secure chain<00:16:10.240> overall<00:16:10.720> rate<00:16:11.019> of<00:16:11.050> benefits<00:16:11.470> everybody 00:16:11.699 --> 00:16:11.709 align:start position:0% chain overall rate of benefits everybody 00:16:11.709 --> 00:16:14.280 align:start position:0% chain overall rate of benefits everybody and<00:16:12.190> welcome<00:16:12.940> to<00:16:13.390> try<00:16:13.540> to<00:16:13.570> be<00:16:13.750> the<00:16:13.870> luminous 00:16:14.280 --> 00:16:14.290 align:start position:0% and welcome to try to be the luminous 00:16:14.290 --> 00:16:16.259 align:start position:0% and welcome to try to be the luminous because<00:16:14.620> we're<00:16:14.950> not<00:16:15.040> anywhere<00:16:15.670> saying<00:16:15.940> ultra 00:16:16.259 --> 00:16:16.269 align:start position:0% because we're not anywhere saying ultra 00:16:16.269 --> 00:16:18.930 align:start position:0% because we're not anywhere saying ultra mystically<00:16:16.750> please<00:16:17.350> get<00:16:17.560> us<00:16:17.649> audited<00:16:17.890> and<00:16:18.760> put 00:16:18.930 --> 00:16:18.940 align:start position:0% mystically please get us audited and put 00:16:18.940 --> 00:16:20.760 align:start position:0% mystically please get us audited and put it<00:16:19.029> on<00:16:19.120> chain<00:16:19.390> we're<00:16:19.899> saying<00:16:20.079> we'll<00:16:20.500> get<00:16:20.680> us 00:16:20.760 --> 00:16:20.770 align:start position:0% it on chain we're saying we'll get us 00:16:20.770 --> 00:16:22.110 align:start position:0% it on chain we're saying we'll get us audited<00:16:20.950> and<00:16:21.279> put<00:16:21.399> it<00:16:21.490> there<00:16:21.579> and<00:16:21.640> we<00:16:22.000> will 00:16:22.110 --> 00:16:22.120 align:start position:0% audited and put it there and we will 00:16:22.120 --> 00:16:31.639 align:start position:0% audited and put it there and we will recuperate<00:16:22.630> that<00:16:23.010> initial<00:16:24.010> investment 00:16:31.639 --> 00:16:31.649 align:start position:0% 00:16:31.649 --> 00:16:33.259 align:start position:0% so<00:16:32.130> the<00:16:32.250> Mississippi<00:16:32.550> Valley<00:16:32.579> all<00:16:32.940> different 00:16:33.259 --> 00:16:33.269 align:start position:0% so the Mississippi Valley all different 00:16:33.269 --> 00:16:35.540 align:start position:0% so the Mississippi Valley all different ways<00:16:33.389> you<00:16:33.930> have<00:16:34.050> permutations<00:16:34.920> rhythm<00:16:35.490> you 00:16:35.540 --> 00:16:35.550 align:start position:0% ways you have permutations rhythm you 00:16:35.550 --> 00:16:37.879 align:start position:0% ways you have permutations rhythm you know<00:16:35.579> like<00:16:35.790> a<00:16:36.120> tomatoes<00:16:36.570> -<00:16:36.899> I'll<00:16:37.139> charge<00:16:37.529> which 00:16:37.879 --> 00:16:37.889 align:start position:0% know like a tomatoes - I'll charge which 00:16:37.889 --> 00:16:40.009 align:start position:0% know like a tomatoes - I'll charge which is<00:16:37.920> mostly<00:16:38.339> what<00:16:38.490> you<00:16:38.579> see<00:16:38.730> today 00:16:40.009 --> 00:16:40.019 align:start position:0% is mostly what you see today 00:16:40.019 --> 00:16:42.259 align:start position:0% is mostly what you see today warning<00:16:40.829> violence<00:16:41.490> doesn't<00:16:41.759> change<00:16:41.970> this 00:16:42.259 --> 00:16:42.269 align:start position:0% warning violence doesn't change this 00:16:42.269 --> 00:16:43.999 align:start position:0% warning violence doesn't change this might<00:16:42.420> be<00:16:42.540> pro<00:16:42.720> contract<00:16:43.139> or<00:16:43.380> prefer<00:16:43.680> per 00:16:43.999 --> 00:16:44.009 align:start position:0% might be pro contract or prefer per 00:16:44.009 --> 00:16:45.650 align:start position:0% might be pro contract or prefer per provider<00:16:44.250> even<00:16:44.730> buying<00:16:45.149> a<00:16:45.360> subscription 00:16:45.650 --> 00:16:45.660 align:start position:0% provider even buying a subscription 00:16:45.660 --> 00:16:49.189 align:start position:0% provider even buying a subscription model<00:16:46.399> may<00:16:47.399> have<00:16:47.579> permanent<00:16:48.029> okay<00:16:48.990> for 00:16:49.189 --> 00:16:49.199 align:start position:0% model may have permanent okay for 00:16:49.199 --> 00:16:51.949 align:start position:0% model may have permanent okay for certain<00:16:49.440> number<00:16:49.589> of<00:16:49.649> calls<00:16:49.949> or<00:16:50.959> certain 00:16:51.949 --> 00:16:51.959 align:start position:0% certain number of calls or certain 00:16:51.959 --> 00:16:54.559 align:start position:0% certain number of calls or certain number<00:16:52.199> of<00:16:52.230> blocks<00:16:52.889> let's<00:16:53.310> say<00:16:53.519> it's<00:16:54.300> a<00:16:54.420> girl 00:16:54.559 --> 00:16:54.569 align:start position:0% number of blocks let's say it's a girl 00:16:54.569 --> 00:17:00.860 align:start position:0% number of blocks let's say it's a girl okay<00:16:54.899> for<00:16:55.050> the<00:16:55.110> next<00:16:55.290> month<00:16:57.410> I<00:16:58.410> have<00:16:59.870> three 00:17:00.860 --> 00:17:00.870 align:start position:0% okay for the next month I have three 00:17:00.870 --> 00:17:02.319 align:start position:0% okay for the next month I have three minutes<00:17:01.170> to<00:17:01.529> get<00:17:01.649> through<00:17:01.889> the<00:17:02.040> user 00:17:02.319 --> 00:17:02.329 align:start position:0% minutes to get through the user 00:17:02.329 --> 00:17:06.799 align:start position:0% minutes to get through the user localized<00:17:03.329> feedback<00:17:03.690> parts<00:17:04.650> so<00:17:05.660> this<00:17:06.660> is 00:17:06.799 --> 00:17:06.809 align:start position:0% localized feedback parts so this is 00:17:06.809 --> 00:17:08.329 align:start position:0% localized feedback parts so this is something<00:17:07.049> that<00:17:07.079> we<00:17:07.260> were<00:17:07.410> talking<00:17:07.709> to<00:17:08.069> if<00:17:08.220> you 00:17:08.329 --> 00:17:08.339 align:start position:0% something that we were talking to if you 00:17:08.339 --> 00:17:09.380 align:start position:0% something that we were talking to if you alternate<00:17:08.730> integrating<00:17:09.150> but<00:17:09.270> know<00:17:09.360> that 00:17:09.380 --> 00:17:09.390 align:start position:0% alternate integrating but know that 00:17:09.390 --> 00:17:12.620 align:start position:0% alternate integrating but know that madam<00:17:09.720> asked<00:17:09.990> has<00:17:10.169> a<00:17:10.890> system<00:17:11.630> which 00:17:12.620 --> 00:17:12.630 align:start position:0% madam asked has a system which 00:17:12.630 --> 00:17:15.289 align:start position:0% madam asked has a system which we<00:17:12.870> heard<00:17:12.990> about<00:17:13.079> yesterday<00:17:13.970> this<00:17:14.970> might<00:17:15.150> be 00:17:15.289 --> 00:17:15.299 align:start position:0% we heard about yesterday this might be 00:17:15.299 --> 00:17:16.189 align:start position:0% we heard about yesterday this might be something<00:17:15.480> that<00:17:15.600> we<00:17:15.780> can<00:17:15.870> just<00:17:15.929> implement 00:17:16.189 --> 00:17:16.199 align:start position:0% something that we can just implement 00:17:16.199 --> 00:17:19.549 align:start position:0% something that we can just implement ourselves<00:17:16.799> so<00:17:17.870> Unchained<00:17:18.870> localization 00:17:19.549 --> 00:17:19.559 align:start position:0% ourselves so Unchained localization 00:17:19.559 --> 00:17:25.460 align:start position:0% ourselves so Unchained localization improve<00:17:22.850> back<00:17:23.850> one<00:17:24.390> here<00:17:24.569> so<00:17:24.870> we<00:17:25.079> have<00:17:25.260> a 00:17:25.460 --> 00:17:25.470 align:start position:0% improve back one here so we have a 00:17:25.470 --> 00:17:27.799 align:start position:0% improve back one here so we have a localization<00:17:25.890> preferences<00:17:26.630> single<00:17:27.630> table 00:17:27.799 --> 00:17:27.809 align:start position:0% localization preferences single table 00:17:27.809 --> 00:17:31.270 align:start position:0% localization preferences single table one<00:17:28.079> chain<00:17:28.319> which<00:17:29.220> actually<00:17:29.549> exists<00:17:30.179> and<00:17:30.330> then 00:17:31.270 --> 00:17:31.280 align:start position:0% one chain which actually exists and then 00:17:31.280 --> 00:17:35.180 align:start position:0% one chain which actually exists and then localization<00:17:32.280> for<00:17:32.490> these<00:17:33.080> 256<00:17:34.080> codes<00:17:34.320> that's 00:17:35.180 --> 00:17:35.190 align:start position:0% localization for these 256 codes that's 00:17:35.190 --> 00:17:38.570 align:start position:0% localization for these 256 codes that's a<00:17:35.419> reasonable<00:17:36.419> number<00:17:36.450> to<00:17:36.870> get<00:17:36.960> translated<00:17:37.580> we 00:17:38.570 --> 00:17:38.580 align:start position:0% a reasonable number to get translated we 00:17:38.580 --> 00:17:40.520 align:start position:0% a reasonable number to get translated we have<00:17:38.760> first<00:17:39.090> translations<00:17:39.780> and<00:17:40.260> it's<00:17:40.409> through 00:17:40.520 --> 00:17:40.530 align:start position:0% have first translations and it's through 00:17:40.530 --> 00:17:42.890 align:start position:0% have first translations and it's through the<00:17:40.620> concept<00:17:41.040> in<00:17:41.220> English<00:17:41.730> Spanish<00:17:42.480> and 00:17:42.890 --> 00:17:42.900 align:start position:0% the concept in English Spanish and 00:17:42.900 --> 00:17:47.060 align:start position:0% the concept in English Spanish and pirate<00:17:43.610> and<00:17:44.610> to<00:17:45.510> get<00:17:46.020> more<00:17:46.260> as<00:17:46.409> a<00:17:46.710> zombie<00:17:46.830> have 00:17:47.060 --> 00:17:47.070 align:start position:0% pirate and to get more as a zombie have 00:17:47.070 --> 00:17:48.620 align:start position:0% pirate and to get more as a zombie have a<00:17:47.100> couple<00:17:47.400> partial<00:17:47.850> translations<00:17:48.390> other 00:17:48.620 --> 00:17:48.630 align:start position:0% a couple partial translations other 00:17:48.630 --> 00:17:51.640 align:start position:0% a couple partial translations other languages<00:17:49.110> not<00:17:49.260> the<00:17:49.530> whole<00:17:49.740> booth<00:17:50.490> set<00:17:50.700> yet<00:17:50.880> so 00:17:51.640 --> 00:17:51.650 align:start position:0% languages not the whole booth set yet so 00:17:51.650 --> 00:17:54.590 align:start position:0% languages not the whole booth set yet so if<00:17:52.650> they're<00:17:52.770> going<00:17:52.860> to<00:17:52.919> successful<00:17:53.460> oh<00:17:53.600> you're 00:17:54.590 --> 00:17:54.600 align:start position:0% if they're going to successful oh you're 00:17:54.600 --> 00:17:56.840 align:start position:0% if they're going to successful oh you're a<00:17:54.720> Japanese<00:17:55.320> speaker<00:17:55.740> and<00:17:56.100> you<00:17:56.549> want<00:17:56.730> to 00:17:56.840 --> 00:17:56.850 align:start position:0% a Japanese speaker and you want to 00:17:56.850 --> 00:17:59.149 align:start position:0% a Japanese speaker and you want to interact<00:17:57.090> with<00:17:57.210> this<00:17:57.450> contract<00:17:58.100> through<00:17:59.100> a 00:17:59.149 --> 00:17:59.159 align:start position:0% interact with this contract through a 00:17:59.159 --> 00:18:01.399 align:start position:0% interact with this contract through a wall<00:17:59.340> that's<00:17:59.490> it's<00:17:59.730> a<00:17:59.820> transaction<00:18:00.260> it<00:18:01.260> does 00:18:01.399 --> 00:18:01.409 align:start position:0% wall that's it's a transaction it does 00:18:01.409 --> 00:18:03.830 align:start position:0% wall that's it's a transaction it does something<00:18:01.590> and<00:18:02.010> returns<00:18:02.880> back<00:18:03.000> so<00:18:03.360> soon<00:18:03.570> and 00:18:03.830 --> 00:18:03.840 align:start position:0% something and returns back so soon and 00:18:03.840 --> 00:18:06.980 align:start position:0% something and returns back so soon and now<00:18:04.470> we're<00:18:04.770> done<00:18:05.400> right<00:18:06.120> this<00:18:06.510> is<00:18:06.659> come<00:18:06.840> back 00:18:06.980 --> 00:18:06.990 align:start position:0% now we're done right this is come back 00:18:06.990 --> 00:18:09.380 align:start position:0% now we're done right this is come back in<00:18:07.230> the<00:18:07.380> response<00:18:07.790> we<00:18:08.790> don't<00:18:09.000> have<00:18:09.090> to<00:18:09.179> pay<00:18:09.330> for 00:18:09.380 --> 00:18:09.390 align:start position:0% in the response we don't have to pay for 00:18:09.390 --> 00:18:11.649 align:start position:0% in the response we don't have to pay for the<00:18:09.600> rest<00:18:09.780> of<00:18:09.900> this<00:18:10.020> because<00:18:10.350> is<00:18:10.470> truly<00:18:10.919> a<00:18:10.950> read 00:18:11.649 --> 00:18:11.659 align:start position:0% the rest of this because is truly a read 00:18:11.659 --> 00:18:17.210 align:start position:0% the rest of this because is truly a read so<00:18:12.659> we<00:18:12.870> go<00:18:13.080> to<00:18:13.110> the<00:18:15.290> translations<00:18:16.290> contractor 00:18:17.210 --> 00:18:17.220 align:start position:0% so we go to the translations contractor 00:18:17.220 --> 00:18:20.870 align:start position:0% so we go to the translations contractor there<00:18:17.400> forever<00:18:18.470> essentially<00:18:19.470> look<00:18:20.250> up<00:18:20.400> the<00:18:20.580> TX 00:18:20.870 --> 00:18:20.880 align:start position:0% there forever essentially look up the TX 00:18:20.880 --> 00:18:23.210 align:start position:0% there forever essentially look up the TX origin<00:18:21.419> transactional<00:18:22.140> urgent<00:18:22.470> user<00:18:22.770> and 00:18:23.210 --> 00:18:23.220 align:start position:0% origin transactional urgent user and 00:18:23.220 --> 00:18:25.130 align:start position:0% origin transactional urgent user and look<00:18:23.880> at<00:18:23.970> the<00:18:24.090> role<00:18:24.210> for<00:18:24.419> them<00:18:24.570> which<00:18:24.929> says 00:18:25.130 --> 00:18:25.140 align:start position:0% look at the role for them which says 00:18:25.140 --> 00:18:28.340 align:start position:0% look at the role for them which says that<00:18:25.320> they<00:18:25.440> want<00:18:26.030> Japanese<00:18:27.030> they<00:18:27.809> grab<00:18:28.080> the 00:18:28.340 --> 00:18:28.350 align:start position:0% that they want Japanese they grab the 00:18:28.350 --> 00:18:33.500 align:start position:0% that they want Japanese they grab the text<00:18:30.080> 411<00:18:31.490> return<00:18:32.490> the<00:18:32.610> text<00:18:32.760> back<00:18:33.030> up<00:18:33.270> and 00:18:33.500 --> 00:18:33.510 align:start position:0% text 411 return the text back up and 00:18:33.510 --> 00:18:40.280 align:start position:0% text 411 return the text back up and display<00:18:34.230> it<00:18:34.380> and<00:18:34.530> Eli<00:18:38.600> Loker<00:18:39.600> overflows 00:18:40.280 --> 00:18:40.290 align:start position:0% display it and Eli Loker overflows 00:18:40.290 --> 00:18:43.100 align:start position:0% display it and Eli Loker overflows management<00:18:40.799> really<00:18:40.980> earn<00:18:41.690> in<00:18:42.690> certain<00:18:42.990> are 00:18:43.100 --> 00:18:43.110 align:start position:0% management really earn in certain are 00:18:43.110 --> 00:18:44.899 align:start position:0% management really earn in certain are putting<00:18:43.409> strange<00:18:43.679> River<00:18:44.070> we<00:18:44.280> can<00:18:44.429> do<00:18:44.520> a<00:18:44.549> lookup 00:18:44.899 --> 00:18:44.909 align:start position:0% putting strange River we can do a lookup 00:18:44.909 --> 00:18:48.289 align:start position:0% putting strange River we can do a lookup and<00:18:45.330> then<00:18:45.450> reversed<00:18:46.100> so<00:18:47.100> similar<00:18:47.549> flow<00:18:47.790> maybe 00:18:48.289 --> 00:18:48.299 align:start position:0% and then reversed so similar flow maybe 00:18:48.299 --> 00:18:51.289 align:start position:0% and then reversed so similar flow maybe we<00:18:48.450> send<00:18:48.960> the<00:18:49.049> transaction<00:18:49.290> and<00:18:49.860> then<00:18:50.790> this 00:18:51.289 --> 00:18:51.299 align:start position:0% we send the transaction and then this 00:18:51.299 --> 00:18:53.149 align:start position:0% we send the transaction and then this contract<00:18:51.900> that<00:18:51.960> needs<00:18:52.200> to<00:18:52.440> revert<00:18:52.679> so<00:18:53.040> we're 00:18:53.149 --> 00:18:53.159 align:start position:0% contract that needs to revert so we're 00:18:53.159 --> 00:18:56.870 align:start position:0% contract that needs to revert so we're gonna<00:18:53.280> revert<00:18:53.520> with<00:18:53.669> fluoro<00:18:55.520> we<00:18:56.520> hook<00:18:56.669> up<00:18:56.760> the 00:18:56.870 --> 00:18:56.880 align:start position:0% gonna revert with fluoro we hook up the 00:18:56.880 --> 00:18:59.990 align:start position:0% gonna revert with fluoro we hook up the text<00:18:57.150> from<00:18:57.270> out<00:18:57.590> again<00:18:58.590> look<00:18:58.770> at<00:18:58.860> the<00:18:59.040> TX<00:18:59.790> for 00:18:59.990 --> 00:19:00.000 align:start position:0% text from out again look at the TX for 00:19:00.000 --> 00:19:05.390 align:start position:0% text from out again look at the TX for Jimmy<00:19:02.120> grab<00:19:03.120> the<00:19:03.540> text<00:19:04.080> and<00:19:04.860> probably<00:19:05.159> get<00:19:05.280> it 00:19:05.390 --> 00:19:05.400 align:start position:0% Jimmy grab the text and probably get it 00:19:05.400 --> 00:19:09.770 align:start position:0% Jimmy grab the text and probably get it back<00:19:05.580> up<00:19:05.820> and<00:19:06.679> we'll<00:19:07.679> show<00:19:07.830> like<00:19:07.980> that<00:19:08.010> so<00:19:08.429> I<00:19:08.780> as 00:19:09.770 --> 00:19:09.780 align:start position:0% back up and we'll show like that so I as 00:19:09.780 --> 00:19:11.090 align:start position:0% back up and we'll show like that so I as the<00:19:09.990> developer<00:19:10.350> don't<00:19:10.559> have<00:19:10.799> to<00:19:10.919> write<00:19:11.070> all 00:19:11.090 --> 00:19:11.100 align:start position:0% the developer don't have to write all 00:19:11.100 --> 00:19:13.399 align:start position:0% the developer don't have to write all the<00:19:11.250> transitions<00:19:11.730> myself<00:19:12.090> they<00:19:12.600> exist<00:19:13.020> people 00:19:13.399 --> 00:19:13.409 align:start position:0% the transitions myself they exist people 00:19:13.409 --> 00:19:16.280 align:start position:0% the transitions myself they exist people can<00:19:13.500> register<00:19:13.679> their<00:19:14.010> own<00:19:14.190> and<00:19:14.549> then<00:19:14.669> say<00:19:15.290> you 00:19:16.280 --> 00:19:16.290 align:start position:0% can register their own and then say you 00:19:16.290 --> 00:19:18.710 align:start position:0% can register their own and then say you know<00:19:16.350> I<00:19:16.559> would<00:19:16.620> use<00:19:17.280> this<00:19:17.940> translation<00:19:18.540> for 00:19:18.710 --> 00:19:18.720 align:start position:0% know I would use this translation for 00:19:18.720 --> 00:19:21.710 align:start position:0% know I would use this translation for all<00:19:18.870> my<00:19:19.049> messaging<00:19:19.500> right<00:19:19.860> if<00:19:20.640> you<00:19:20.850> want 00:19:21.710 --> 00:19:21.720 align:start position:0% all my messaging right if you want 00:19:21.720 --> 00:19:23.990 align:start position:0% all my messaging right if you want etherium<00:19:22.380> totally<00:19:22.770> widely<00:19:23.370> used<00:19:23.580> and 00:19:23.990 --> 00:19:24.000 align:start position:0% etherium totally widely used and 00:19:24.000 --> 00:19:26.000 align:start position:0% etherium totally widely used and accessible<00:19:24.390> to<00:19:24.540> everybody<00:19:24.809> like<00:19:25.230> my<00:19:25.710> check 00:19:26.000 --> 00:19:26.010 align:start position:0% accessible to everybody like my check 00:19:26.010 --> 00:19:28.280 align:start position:0% accessible to everybody like my check grandmother<00:19:26.490> doesn't<00:19:26.970> speak<00:19:27.210> English<00:19:27.570> we<00:19:28.169> did 00:19:28.280 --> 00:19:28.290 align:start position:0% grandmother doesn't speak English we did 00:19:28.290 --> 00:19:33.020 align:start position:0% grandmother doesn't speak English we did a<00:19:28.320> quick<00:19:28.679> analysis<00:19:29.250> of<00:19:31.520> why<00:19:32.520> are<00:19:32.580> the<00:19:32.760> reverts 00:19:33.020 --> 00:19:33.030 align:start position:0% a quick analysis of why are the reverts 00:19:33.030 --> 00:19:35.390 align:start position:0% a quick analysis of why are the reverts rating<00:19:33.450> in<00:19:33.630> on<00:19:34.440> chain<00:19:34.799> and<00:19:35.159> they're 00:19:35.390 --> 00:19:35.400 align:start position:0% rating in on chain and they're 00:19:35.400 --> 00:19:37.159 align:start position:0% rating in on chain and they're predominantly<00:19:35.730> English<00:19:36.390> like<00:19:36.659> like 00:19:37.159 --> 00:19:37.169 align:start position:0% predominantly English like like 00:19:37.169 --> 00:19:39.409 align:start position:0% predominantly English like like overwhelmingly<00:19:37.860> with<00:19:38.400> a<00:19:38.429> bit<00:19:39.030> of<00:19:39.059> Chinese 00:19:39.409 --> 00:19:39.419 align:start position:0% overwhelmingly with a bit of Chinese 00:19:39.419 --> 00:19:41.919 align:start position:0% overwhelmingly with a bit of Chinese right<00:19:40.110> so<00:19:40.350> that's<00:19:40.470> to<00:19:40.679> really<00:19:40.919> hold<00:19:41.100> her<00:19:41.280> much 00:19:41.919 --> 00:19:41.929 align:start position:0% right so that's to really hold her much 00:19:41.929 --> 00:19:43.630 align:start position:0% right so that's to really hold her much and 00:19:43.630 --> 00:19:43.640 align:start position:0% and 00:19:43.640 --> 00:19:47.310 align:start position:0% and we<00:19:43.880> can<00:19:44.030> absolutely<00:19:44.210> get<00:19:44.690> that<00:19:44.870> get<00:19:45.740> that<00:19:45.770> done 00:19:47.310 --> 00:19:47.320 align:start position:0% we can absolutely get that get that done 00:19:47.320 --> 00:19:49.600 align:start position:0% we can absolutely get that get that done yeah<00:19:48.460> probably 00:19:49.600 --> 00:19:49.610 align:start position:0% yeah probably 00:19:49.610 --> 00:19:53.740 align:start position:0% yeah probably like<00:19:49.850> that<00:19:50.710> and<00:19:51.710> that's<00:19:52.309> all<00:19:52.490> for<00:19:52.670> me<00:19:52.760> thank 00:19:53.740 --> 00:19:53.750 align:start position:0% like that and that's all for me thank 00:19:53.750 --> 00:19:57.350 align:start position:0% like that and that's all for me thank you 00:19:57.350 --> 00:19:57.360 align:start position:0% 00:19:57.360 --> 00:20:07.190 align:start position:0% [Applause] 00:20:07.190 --> 00:20:07.200 align:start position:0% 00:20:07.200 --> 00:20:09.260 align:start position:0% you