WEBVTT Kind: captions Language: en 00:00:01.070 --> 00:00:12.839 align:start position:0% [Applause] 00:00:12.839 --> 00:00:12.849 align:start position:0% 00:00:12.849 --> 00:00:22.390 align:start position:0% hey<00:00:13.849> everyone<00:00:14.150> my<00:00:14.480> name<00:00:15.379> is<00:00:16.240> Maxime<00:00:17.240> that<00:00:21.400> they 00:00:22.390 --> 00:00:22.400 align:start position:0% hey everyone my name is Maxime that they 00:00:22.400 --> 00:00:24.339 align:start position:0% hey everyone my name is Maxime that they talk<00:00:22.660> super<00:00:23.660> excited<00:00:23.930> to<00:00:23.989> talk<00:00:24.079> about<00:00:24.199> this 00:00:24.339 --> 00:00:24.349 align:start position:0% talk super excited to talk about this 00:00:24.349 --> 00:00:26.380 align:start position:0% talk super excited to talk about this make<00:00:25.250> some<00:00:25.400> of<00:00:25.460> the<00:00:25.520> most<00:00:25.579> frustrating<00:00:26.150> things 00:00:26.380 --> 00:00:26.390 align:start position:0% make some of the most frustrating things 00:00:26.390 --> 00:00:29.290 align:start position:0% make some of the most frustrating things to<00:00:26.630> attract<00:00:27.410> developers<00:00:27.859> a<00:00:28.460> lot<00:00:29.029> of<00:00:29.089> people 00:00:29.290 --> 00:00:29.300 align:start position:0% to attract developers a lot of people 00:00:29.300 --> 00:00:33.180 align:start position:0% to attract developers a lot of people building<00:00:29.419> on<00:00:29.630> etherion<00:00:31.629> being<00:00:32.629> on<00:00:32.720> set<00:00:32.900> but 00:00:33.180 --> 00:00:33.190 align:start position:0% building on etherion being on set but 00:00:33.190 --> 00:00:34.990 align:start position:0% building on etherion being on set but really<00:00:34.190> not<00:00:34.280> the<00:00:34.370> case 00:00:34.990 --> 00:00:35.000 align:start position:0% really not the case 00:00:35.000 --> 00:00:36.549 align:start position:0% really not the case totally<00:00:35.600> will<00:00:35.720> affect<00:00:35.900> through<00:00:35.989> the<00:00:36.110> day 00:00:36.549 --> 00:00:36.559 align:start position:0% totally will affect through the day 00:00:36.559 --> 00:00:38.049 align:start position:0% totally will affect through the day background<00:00:37.070> nonsense<00:00:37.610> what<00:00:37.790> they<00:00:37.879> are 00:00:38.049 --> 00:00:38.059 align:start position:0% background nonsense what they are 00:00:38.059 --> 00:00:43.270 align:start position:0% background nonsense what they are probably<00:00:38.900> cause<00:00:41.590> start<00:00:42.590> to<00:00:42.710> notice<00:00:42.890> all<00:00:43.160> those 00:00:43.270 --> 00:00:43.280 align:start position:0% probably cause start to notice all those 00:00:43.280 --> 00:00:48.040 align:start position:0% probably cause start to notice all those frustrations<00:00:44.320> out<00:00:46.090> before<00:00:47.090> you<00:00:47.149> started<00:00:47.510> no 00:00:48.040 --> 00:00:48.050 align:start position:0% frustrations out before you started no 00:00:48.050 --> 00:00:49.599 align:start position:0% frustrations out before you started no no<00:00:48.620> worries<00:00:48.800> if<00:00:48.949> you<00:00:48.980> don't<00:00:49.190> we've<00:00:49.370> been<00:00:49.489> very 00:00:49.599 --> 00:00:49.609 align:start position:0% no worries if you don't we've been very 00:00:49.609 --> 00:00:51.400 align:start position:0% no worries if you don't we've been very quiet<00:00:49.910> building<00:00:50.899> things<00:00:51.050> for<00:00:51.140> about<00:00:51.289> two 00:00:51.400 --> 00:00:51.410 align:start position:0% quiet building things for about two 00:00:51.410 --> 00:00:54.220 align:start position:0% quiet building things for about two years<00:00:51.440> in<00:00:51.649> the<00:00:51.710> lefthand<00:00:51.949> space<00:00:52.190> but<00:00:52.989> no<00:00:53.989> PR 00:00:54.220 --> 00:00:54.230 align:start position:0% years in the lefthand space but no PR 00:00:54.230 --> 00:00:56.200 align:start position:0% years in the lefthand space but no PR marketing<00:00:54.410> we<00:00:55.309> empower<00:00:55.609> us<00:00:55.820> a<00:00:56.000> deeper 00:00:56.200 --> 00:00:56.210 align:start position:0% marketing we empower us a deeper 00:00:56.210 --> 00:00:57.160 align:start position:0% marketing we empower us a deeper structure<00:00:56.510> for<00:00:56.719> a<00:00:56.750> bunch<00:00:56.899> of<00:00:56.930> awesome 00:00:57.160 --> 00:00:57.170 align:start position:0% structure for a bunch of awesome 00:00:57.170 --> 00:01:00.150 align:start position:0% structure for a bunch of awesome companies<00:00:57.530> like<00:00:58.250> auger<00:00:58.460> 0s<00:00:58.969> for<00:00:59.239> bikinis 00:01:00.150 --> 00:01:00.160 align:start position:0% companies like auger 0s for bikinis 00:01:00.160 --> 00:01:02.139 align:start position:0% companies like auger 0s for bikinis building<00:01:01.160> all<00:01:01.309> the<00:01:01.429> tools<00:01:01.640> on<00:01:01.760> top<00:01:01.940> of<00:01:02.059> that 00:01:02.139 --> 00:01:02.149 align:start position:0% building all the tools on top of that 00:01:02.149 --> 00:01:04.600 align:start position:0% building all the tools on top of that evil<00:01:02.690> is<00:01:02.780> really<00:01:03.009> developers<00:01:04.009> focus<00:01:04.129> on<00:01:04.460> the 00:01:04.600 --> 00:01:04.610 align:start position:0% evil is really developers focus on the 00:01:04.610 --> 00:01:06.550 align:start position:0% evil is really developers focus on the things<00:01:04.820> that<00:01:04.879> matter<00:01:05.089> building<00:01:05.960> either<00:01:06.080> a<00:01:06.170> key 00:01:06.550 --> 00:01:06.560 align:start position:0% things that matter building either a key 00:01:06.560 --> 00:01:10.300 align:start position:0% things that matter building either a key your<00:01:07.009> own<00:01:07.100> green<00:01:07.340> spaces<00:01:07.899> and<00:01:08.899> so<00:01:09.530> to<00:01:09.590> have 00:01:10.300 --> 00:01:10.310 align:start position:0% your own green spaces and so to have 00:01:10.310 --> 00:01:11.620 align:start position:0% your own green spaces and so to have really<00:01:10.520> been<00:01:10.610> working<00:01:10.759> let<00:01:11.179> me<00:01:11.270> have<00:01:11.390> to<00:01:11.479> work 00:01:11.620 --> 00:01:11.630 align:start position:0% really been working let me have to work 00:01:11.630 --> 00:01:15.100 align:start position:0% really been working let me have to work with<00:01:11.780> some<00:01:11.960> awesome<00:01:12.080> folks<00:01:12.350> doing<00:01:12.649> that<00:01:14.110> now 00:01:15.100 --> 00:01:15.110 align:start position:0% with some awesome folks doing that now 00:01:15.110 --> 00:01:18.580 align:start position:0% with some awesome folks doing that now let's<00:01:15.649> start<00:01:15.830> with<00:01:15.860> onset<00:01:16.990> flavor<00:01:17.990> there<00:01:18.410> will 00:01:18.580 --> 00:01:18.590 align:start position:0% let's start with onset flavor there will 00:01:18.590 --> 00:01:20.800 align:start position:0% let's start with onset flavor there will be<00:01:18.619> a<00:01:18.950> lot<00:01:19.220> of<00:01:19.250> nice<00:01:19.490> space<00:01:19.789> funds<00:01:20.119> in<00:01:20.630> this 00:01:20.800 --> 00:01:20.810 align:start position:0% be a lot of nice space funds in this 00:01:20.810 --> 00:01:25.240 align:start position:0% be a lot of nice space funds in this presentation<00:01:22.810> this<00:01:23.810> nonsense<00:01:24.319> talk<00:01:25.099> about 00:01:25.240 --> 00:01:25.250 align:start position:0% presentation this nonsense talk about 00:01:25.250 --> 00:01:26.469 align:start position:0% presentation this nonsense talk about the<00:01:25.310> theory<00:01:25.520> mountains<00:01:25.970> they're<00:01:26.090> really<00:01:26.300> two 00:01:26.469 --> 00:01:26.479 align:start position:0% the theory mountains they're really two 00:01:26.479 --> 00:01:28.270 align:start position:0% the theory mountains they're really two things<00:01:26.509> we're<00:01:26.840> talking<00:01:26.959> about<00:01:27.349> I<00:01:27.619> don't<00:01:28.220> know 00:01:28.270 --> 00:01:28.280 align:start position:0% things we're talking about I don't know 00:01:28.280 --> 00:01:30.040 align:start position:0% things we're talking about I don't know long<00:01:28.459> is<00:01:28.610> nonsense<00:01:28.970> for<00:01:29.060> miners<00:01:29.450> this<00:01:29.630> is<00:01:29.810> the 00:01:30.040 --> 00:01:30.050 align:start position:0% long is nonsense for miners this is the 00:01:30.050 --> 00:01:33.550 align:start position:0% long is nonsense for miners this is the way<00:01:30.140> they<00:01:30.259> will<00:01:30.380> block<00:01:31.369> Awards<00:01:32.560> incrementing 00:01:33.550 --> 00:01:33.560 align:start position:0% way they will block Awards incrementing 00:01:33.560 --> 00:01:36.510 align:start position:0% way they will block Awards incrementing this<00:01:33.739> not<00:01:34.069> stupid<00:01:34.489> the<00:01:34.729> graphical<00:01:35.539> puzzle 00:01:36.510 --> 00:01:36.520 align:start position:0% this not stupid the graphical puzzle 00:01:36.520 --> 00:01:39.010 align:start position:0% this not stupid the graphical puzzle proof<00:01:37.520> of<00:01:37.640> concept<00:01:38.149> foremost<00:01:38.539> you<00:01:38.690> really 00:01:39.010 --> 00:01:39.020 align:start position:0% proof of concept foremost you really 00:01:39.020 --> 00:01:41.529 align:start position:0% proof of concept foremost you really with<00:01:39.229> the<00:01:40.099> other<00:01:40.250> thing<00:01:40.399> is<00:01:40.539> applications 00:01:41.529 --> 00:01:41.539 align:start position:0% with the other thing is applications 00:01:41.539 --> 00:01:42.639 align:start position:0% with the other thing is applications grand<00:01:41.780> users<00:01:42.140> when<00:01:42.380> you're<00:01:42.470> submitting 00:01:42.639 --> 00:01:42.649 align:start position:0% grand users when you're submitting 00:01:42.649 --> 00:01:44.650 align:start position:0% grand users when you're submitting transactions<00:01:43.429> I<00:01:43.759> mean<00:01:44.060> this<00:01:44.179> is<00:01:44.300> given<00:01:44.509> with<00:01:44.599> a 00:01:44.650 --> 00:01:44.660 align:start position:0% transactions I mean this is given with a 00:01:44.660 --> 00:01:46.560 align:start position:0% transactions I mean this is given with a nonce<00:01:44.840> is<00:01:45.349> basically 00:01:46.560 --> 00:01:46.570 align:start position:0% nonce is basically 00:01:46.570 --> 00:01:48.210 align:start position:0% nonce is basically the<00:01:46.690> number<00:01:46.900> of<00:01:46.990> transactions<00:01:47.620> that<00:01:48.160> are 00:01:48.210 --> 00:01:48.220 align:start position:0% the number of transactions that are 00:01:48.220 --> 00:01:51.000 align:start position:0% the number of transactions that are confirmed<00:01:48.700> from<00:01:49.240> the<00:01:49.300> address<00:01:49.750> and<00:01:50.740> they<00:01:50.890> are 00:01:51.000 --> 00:01:51.010 align:start position:0% confirmed from the address and they are 00:01:51.010 --> 00:01:53.340 align:start position:0% confirmed from the address and they are submitting<00:01:51.340> them<00:01:51.460> from<00:01:51.930> if<00:01:52.930> they<00:01:53.080> stood<00:01:53.260> the 00:01:53.340 --> 00:01:53.350 align:start position:0% submitting them from if they stood the 00:01:53.350 --> 00:01:54.840 align:start position:0% submitting them from if they stood the way<00:01:53.440> that<00:01:53.650> you're<00:01:53.770> in<00:01:53.890> with<00:01:53.950> the<00:01:54.070> Semites<00:01:54.580> that 00:01:54.840 --> 00:01:54.850 align:start position:0% way that you're in with the Semites that 00:01:54.850 --> 00:01:57.570 align:start position:0% way that you're in with the Semites that it<00:01:54.940> works<00:01:56.010> that's<00:01:57.010> what<00:01:57.160> we're<00:01:57.250> going<00:01:57.370> to<00:01:57.460> talk 00:01:57.570 --> 00:01:57.580 align:start position:0% it works that's what we're going to talk 00:01:57.580 --> 00:01:59.160 align:start position:0% it works that's what we're going to talk about<00:01:57.610> today<00:01:57.940> I<00:01:58.270> don't<00:01:58.810> know<00:01:58.900> too<00:01:58.960> much<00:01:59.110> about 00:01:59.160 --> 00:01:59.170 align:start position:0% about today I don't know too much about 00:01:59.170 --> 00:02:00.810 align:start position:0% about today I don't know too much about the<00:01:59.440> my<00:01:59.560> excitement<00:01:59.890> that's<00:02:00.310> spent<00:02:00.580> a<00:02:00.610> lot<00:02:00.790> of 00:02:00.810 --> 00:02:00.820 align:start position:0% the my excitement that's spent a lot of 00:02:00.820 --> 00:02:03.210 align:start position:0% the my excitement that's spent a lot of time<00:02:01.060> with<00:02:01.240> developers<00:02:01.690> during<00:02:02.020> a<00:02:02.140> stuff<00:02:03.100> on 00:02:03.210 --> 00:02:03.220 align:start position:0% time with developers during a stuff on 00:02:03.220 --> 00:02:05.220 align:start position:0% time with developers during a stuff on the<00:02:03.370> application<00:02:04.330> side<00:02:04.510> and<00:02:04.930> then<00:02:05.050> either 00:02:05.220 --> 00:02:05.230 align:start position:0% the application side and then either 00:02:05.230 --> 00:02:08.430 align:start position:0% the application side and then either side<00:02:05.500> that's<00:02:05.830> that's<00:02:06.100> look<00:02:06.250> again<00:02:07.350> so<00:02:08.350> you 00:02:08.430 --> 00:02:08.440 align:start position:0% side that's that's look again so you 00:02:08.440 --> 00:02:10.550 align:start position:0% side that's that's look again so you sort<00:02:08.619> of<00:02:08.740> it<00:02:08.830> for<00:02:09.580> single<00:02:09.940> word<00:02:10.119> announces 00:02:10.550 --> 00:02:10.560 align:start position:0% sort of it for single word announces 00:02:10.560 --> 00:02:13.650 align:start position:0% sort of it for single word announces number<00:02:11.560> one<00:02:11.880> you're<00:02:12.880> starting<00:02:13.210> from<00:02:13.390> scratch 00:02:13.650 --> 00:02:13.660 align:start position:0% number one you're starting from scratch 00:02:13.660 --> 00:02:16.080 align:start position:0% number one you're starting from scratch super<00:02:14.260> easy<00:02:14.320> you're<00:02:15.100> not<00:02:15.220> sincere<00:02:15.400> oh<00:02:15.580> that's 00:02:16.080 --> 00:02:16.090 align:start position:0% super easy you're not sincere oh that's 00:02:16.090 --> 00:02:16.530 align:start position:0% super easy you're not sincere oh that's great 00:02:16.530 --> 00:02:16.540 align:start position:0% great 00:02:16.540 --> 00:02:19.290 align:start position:0% great real<00:02:17.050> straightforward<00:02:17.310> so<00:02:18.310> then<00:02:18.490> those<00:02:19.150> get 00:02:19.290 --> 00:02:19.300 align:start position:0% real straightforward so then those get 00:02:19.300 --> 00:02:21.210 align:start position:0% real straightforward so then those get to<00:02:19.420> much<00:02:19.540> more<00:02:19.690> difficult<00:02:20.110> PSD<00:02:20.650> permit<00:02:20.860> my<00:02:20.980> one 00:02:21.210 --> 00:02:21.220 align:start position:0% to much more difficult PSD permit my one 00:02:21.220 --> 00:02:23.250 align:start position:0% to much more difficult PSD permit my one it's<00:02:21.910> a<00:02:21.970> counter<00:02:22.240> straightforward<00:02:22.959> you<00:02:23.170> all 00:02:23.250 --> 00:02:23.260 align:start position:0% it's a counter straightforward you all 00:02:23.260 --> 00:02:26.610 align:start position:0% it's a counter straightforward you all know<00:02:23.380> if<00:02:23.500> I<00:02:23.650> don't<00:02:23.830> have<00:02:25.230> the<00:02:26.230> rules<00:02:26.470> that 00:02:26.610 --> 00:02:26.620 align:start position:0% know if I don't have the rules that 00:02:26.620 --> 00:02:28.410 align:start position:0% know if I don't have the rules that started<00:02:27.190> its<00:02:27.280> estimator<00:02:27.820> what<00:02:28.060> happens<00:02:28.300> and 00:02:28.410 --> 00:02:28.420 align:start position:0% started its estimator what happens and 00:02:28.420 --> 00:02:29.850 align:start position:0% started its estimator what happens and things<00:02:28.480> go<00:02:28.690> wrong<00:02:28.900> so<00:02:29.290> if<00:02:29.350> your<00:02:29.440> boss<00:02:29.560> is<00:02:29.620> too 00:02:29.850 --> 00:02:29.860 align:start position:0% things go wrong so if your boss is too 00:02:29.860 --> 00:02:32.190 align:start position:0% things go wrong so if your boss is too low<00:02:30.070> you<00:02:30.970> know<00:02:31.120> anyway<00:02:31.450> it's<00:02:31.690> not<00:02:31.840> a<00:02:31.870> big<00:02:31.990> deal 00:02:32.190 --> 00:02:32.200 align:start position:0% low you know anyway it's not a big deal 00:02:32.200 --> 00:02:33.690 align:start position:0% low you know anyway it's not a big deal the<00:02:32.740> node<00:02:32.890> will<00:02:33.040> reject<00:02:33.370> it 00:02:33.690 --> 00:02:33.700 align:start position:0% the node will reject it 00:02:33.700 --> 00:02:35.910 align:start position:0% the node will reject it your<00:02:34.060> request<00:02:34.420> will<00:02:34.600> fail<00:02:34.780> it'll<00:02:35.560> say<00:02:35.709> knots 00:02:35.910 --> 00:02:35.920 align:start position:0% your request will fail it'll say knots 00:02:35.920 --> 00:02:37.910 align:start position:0% your request will fail it'll say knots to<00:02:36.070> Lois<00:02:36.400> you<00:02:36.520> very<00:02:36.760> easily<00:02:36.790> remember<00:02:37.510> submit 00:02:37.910 --> 00:02:37.920 align:start position:0% to Lois you very easily remember submit 00:02:37.920 --> 00:02:39.930 align:start position:0% to Lois you very easily remember submit where<00:02:38.920> it's<00:02:39.070> interesting<00:02:39.250> in<00:02:39.610> the<00:02:39.670> soup<00:02:39.850> and 00:02:39.930 --> 00:02:39.940 align:start position:0% where it's interesting in the soup and 00:02:39.940 --> 00:02:41.970 align:start position:0% where it's interesting in the soup and on<00:02:40.060> system<00:02:40.390> hi<00:02:40.600> your<00:02:41.350> suppress<00:02:41.560> actually 00:02:41.970 --> 00:02:41.980 align:start position:0% on system hi your suppress actually 00:02:41.980 --> 00:02:44.850 align:start position:0% on system hi your suppress actually basically<00:02:42.160> sit<00:02:43.000> around<00:02:43.180> the<00:02:43.480> men<00:02:43.600> pool<00:02:43.860> it 00:02:44.850 --> 00:02:44.860 align:start position:0% basically sit around the men pool it 00:02:44.860 --> 00:02:47.370 align:start position:0% basically sit around the men pool it won't<00:02:45.070> get<00:02:45.190> mind<00:02:45.540> so<00:02:46.540> that<00:02:46.570> so<00:02:46.900> basically<00:02:47.170> your 00:02:47.370 --> 00:02:47.380 align:start position:0% won't get mind so that so basically your 00:02:47.380 --> 00:02:49.320 align:start position:0% won't get mind so that so basically your mouse<00:02:47.530> counter<00:02:47.890> matches<00:02:48.250> up<00:02:48.430> which<00:02:49.090> will<00:02:49.209> out 00:02:49.320 --> 00:02:49.330 align:start position:0% mouse counter matches up which will out 00:02:49.330 --> 00:02:51.090 align:start position:0% mouse counter matches up which will out of<00:02:49.360> cases<00:02:49.720> is<00:02:49.900> hard<00:02:50.110> to<00:02:50.230> do<00:02:50.380> because<00:02:50.620> you<00:02:50.860> as<00:02:50.980> a 00:02:51.090 --> 00:02:51.100 align:start position:0% of cases is hard to do because you as a 00:02:51.100 --> 00:02:52.740 align:start position:0% of cases is hard to do because you as a human<00:02:51.130> you're<00:02:51.519> not<00:02:51.640> sitting<00:02:51.820> there<00:02:51.940> he 00:02:52.740 --> 00:02:52.750 align:start position:0% human you're not sitting there he 00:02:52.750 --> 00:02:54.150 align:start position:0% human you're not sitting there he announces<00:02:53.380> their<00:02:53.620> happenings<00:02:53.980> your 00:02:54.150 --> 00:02:54.160 align:start position:0% announces their happenings your 00:02:54.160 --> 00:02:57.330 align:start position:0% announces their happenings your application<00:02:54.670> test<00:02:55.660> adjusts<00:02:55.989> all<00:02:56.220> the<00:02:57.220> other 00:02:57.330 --> 00:02:57.340 align:start position:0% application test adjusts all the other 00:02:57.340 --> 00:03:00.300 align:start position:0% application test adjusts all the other problem<00:02:57.670> is<00:02:57.850> a<00:02:58.350> starts<00:02:59.350> to<00:02:59.440> give<00:02:59.560> the<00:02:59.769> two<00:03:00.160> main 00:03:00.300 --> 00:03:00.310 align:start position:0% problem is a starts to give the two main 00:03:00.310 --> 00:03:03.360 align:start position:0% problem is a starts to give the two main purposes<00:03:00.459> for<00:03:00.850> us<00:03:00.970> as<00:03:01.620> you<00:03:02.620> know<00:03:02.739> digging<00:03:03.100> line 00:03:03.360 --> 00:03:03.370 align:start position:0% purposes for us as you know digging line 00:03:03.370 --> 00:03:06.270 align:start position:0% purposes for us as you know digging line exists<00:03:03.730> in<00:03:03.790> the<00:03:03.850> first<00:03:04.030> place<00:03:04.799> what<00:03:05.799> is<00:03:05.950> for<00:03:06.100> or 00:03:06.270 --> 00:03:06.280 align:start position:0% exists in the first place what is for or 00:03:06.280 --> 00:03:08.190 align:start position:0% exists in the first place what is for or even<00:03:06.459> transactions<00:03:07.000> the<00:03:07.600> others<00:03:07.810> to<00:03:07.930> prevent 00:03:08.190 --> 00:03:08.200 align:start position:0% even transactions the others to prevent 00:03:08.200 --> 00:03:10.770 align:start position:0% even transactions the others to prevent certain<00:03:08.470> kind<00:03:08.680> of<00:03:08.769> tanked<00:03:09.390> so<00:03:10.390> you're<00:03:10.540> really 00:03:10.770 --> 00:03:10.780 align:start position:0% certain kind of tanked so you're really 00:03:10.780 --> 00:03:12.479 align:start position:0% certain kind of tanked so you're really a<00:03:11.380> simple<00:03:11.769> example 00:03:12.479 --> 00:03:12.489 align:start position:0% a simple example 00:03:12.489 --> 00:03:14.040 align:start position:0% a simple example Lucido<00:03:13.000> smart<00:03:13.390> contract 00:03:14.040 --> 00:03:14.050 align:start position:0% Lucido smart contract 00:03:14.050 --> 00:03:16.590 align:start position:0% Lucido smart contract my<00:03:14.920> social<00:03:15.310> network<00:03:15.610> I'm<00:03:16.150> gonna<00:03:16.270> be<00:03:16.390> able<00:03:16.540> to 00:03:16.590 --> 00:03:16.600 align:start position:0% my social network I'm gonna be able to 00:03:16.600 --> 00:03:18.300 align:start position:0% my social network I'm gonna be able to do<00:03:16.720> things<00:03:16.900> like<00:03:16.990> create<00:03:17.260> users<00:03:17.800> having 00:03:18.300 --> 00:03:18.310 align:start position:0% do things like create users having 00:03:18.310 --> 00:03:20.100 align:start position:0% do things like create users having friend<00:03:18.670> people<00:03:18.880> deep<00:03:19.420> in<00:03:19.570> accounts<00:03:19.990> if<00:03:20.050> you 00:03:20.100 --> 00:03:20.110 align:start position:0% friend people deep in accounts if you 00:03:20.110 --> 00:03:23.520 align:start position:0% friend people deep in accounts if you want<00:03:20.350> unless<00:03:21.280> let's<00:03:21.880> get<00:03:22.090> ended<00:03:22.450> these<00:03:23.290> are 00:03:23.520 --> 00:03:23.530 align:start position:0% want unless let's get ended these are 00:03:23.530 --> 00:03:25.230 align:start position:0% want unless let's get ended these are creating<00:03:23.830> account<00:03:24.130> they<00:03:24.580> find<00:03:24.850> somebody 00:03:25.230 --> 00:03:25.240 align:start position:0% creating account they find somebody 00:03:25.240 --> 00:03:27.210 align:start position:0% creating account they find somebody sometime<00:03:25.990> later<00:03:26.230> on<00:03:26.260> they<00:03:26.650> delete<00:03:27.100> their 00:03:27.210 --> 00:03:27.220 align:start position:0% sometime later on they delete their 00:03:27.220 --> 00:03:29.880 align:start position:0% sometime later on they delete their account<00:03:27.570> all<00:03:28.570> the<00:03:28.660> right<00:03:28.840> is<00:03:29.080> time<00:03:29.680> what<00:03:29.800> can 00:03:29.880 --> 00:03:29.890 align:start position:0% account all the right is time what can 00:03:29.890 --> 00:03:32.220 align:start position:0% account all the right is time what can happen<00:03:30.040> if<00:03:30.250> you<00:03:30.340> don't<00:03:30.460> have<00:03:30.580> proper<00:03:30.850> ring<00:03:31.450> and 00:03:32.220 --> 00:03:32.230 align:start position:0% happen if you don't have proper ring and 00:03:32.230 --> 00:03:33.270 align:start position:0% happen if you don't have proper ring and really<00:03:32.410> honest<00:03:32.710> is<00:03:32.830> a<00:03:32.860> way<00:03:33.010> that<00:03:33.100> this<00:03:33.220> is 00:03:33.270 --> 00:03:33.280 align:start position:0% really honest is a way that this is 00:03:33.280 --> 00:03:36.060 align:start position:0% really honest is a way that this is ensure<00:03:33.610> the<00:03:33.940> appearing<00:03:34.300> the<00:03:34.390> world<00:03:35.070> initially 00:03:36.060 --> 00:03:36.070 align:start position:0% ensure the appearing the world initially 00:03:36.070 --> 00:03:37.800 align:start position:0% ensure the appearing the world initially mentioned<00:03:36.250> you<00:03:36.790> know<00:03:36.910> the<00:03:37.150> right<00:03:37.600> side 00:03:37.800 --> 00:03:37.810 align:start position:0% mentioned you know the right side 00:03:37.810 --> 00:03:41.100 align:start position:0% mentioned you know the right side everything's<00:03:38.410> gonna<00:03:38.730> with<00:03:39.730> you<00:03:40.720> know<00:03:40.810> how<00:03:40.900> it 00:03:41.100 --> 00:03:41.110 align:start position:0% everything's gonna with you know how it 00:03:41.110 --> 00:03:42.720 align:start position:0% everything's gonna with you know how it feels<00:03:41.290> once<00:03:41.770> you've<00:03:42.160> number<00:03:42.370> three<00:03:42.580> of<00:03:42.670> the 00:03:42.720 --> 00:03:42.730 align:start position:0% feels once you've number three of the 00:03:42.730 --> 00:03:45.770 align:start position:0% feels once you've number three of the user<00:03:42.850> into<00:03:43.680> account<00:03:44.680> when<00:03:44.860> you<00:03:44.920> expect<00:03:45.310> one 00:03:45.770 --> 00:03:45.780 align:start position:0% user into account when you expect one 00:03:45.780 --> 00:03:48.870 align:start position:0% user into account when you expect one possibly<00:03:46.780> from<00:03:46.990> here<00:03:47.670> then<00:03:48.670> there's<00:03:48.820> the 00:03:48.870 --> 00:03:48.880 align:start position:0% possibly from here then there's the 00:03:48.880 --> 00:03:52.160 align:start position:0% possibly from here then there's the attack<00:03:49.120> side<00:03:49.530> so<00:03:50.530> single-pane<00:03:51.520> example 00:03:52.160 --> 00:03:52.170 align:start position:0% attack side so single-pane example 00:03:52.170 --> 00:03:55.290 align:start position:0% attack side so single-pane example witnesses<00:03:53.190> in<00:03:54.190> all<00:03:54.370> strands<00:03:54.670> to<00:03:54.850> survive 00:03:55.290 --> 00:03:55.300 align:start position:0% witnesses in all strands to survive 00:03:55.300 --> 00:03:57.350 align:start position:0% witnesses in all strands to survive nonsense<00:03:55.600> a<00:03:55.690> mousetrap<00:03:55.900> a<00:03:56.320> bottle<00:03:56.590> we<00:03:56.650> need 00:03:57.350 --> 00:03:57.360 align:start position:0% nonsense a mousetrap a bottle we need 00:03:57.360 --> 00:03:59.730 align:start position:0% nonsense a mousetrap a bottle we need optimistic<00:03:58.360> grab<00:03:58.570> that<00:03:58.780> transaction<00:03:59.470> and 00:03:59.730 --> 00:03:59.740 align:start position:0% optimistic grab that transaction and 00:03:59.740 --> 00:04:01.380 align:start position:0% optimistic grab that transaction and send<00:04:00.520> it<00:04:00.610> as<00:04:00.760> many<00:04:00.910> times<00:04:00.970> as<00:04:01.240> he<00:04:01.300> wants 00:04:01.380 --> 00:04:01.390 align:start position:0% send it as many times as he wants 00:04:01.390 --> 00:04:03.240 align:start position:0% send it as many times as he wants because<00:04:02.200> there's<00:04:02.470> nothing<00:04:02.590> that<00:04:02.740> distinguish 00:04:03.240 --> 00:04:03.250 align:start position:0% because there's nothing that distinguish 00:04:03.250 --> 00:04:05.520 align:start position:0% because there's nothing that distinguish should<00:04:03.400> be<00:04:03.570> leisure<00:04:04.570> to<00:04:04.660> a<00:04:04.720> transaction<00:04:05.050> from 00:04:05.520 --> 00:04:05.530 align:start position:0% should be leisure to a transaction from 00:04:05.530 --> 00:04:09.860 align:start position:0% should be leisure to a transaction from the<00:04:06.570> bat<00:04:07.570> one<00:04:08.010> and<00:04:09.010> so<00:04:09.130> the<00:04:09.220> outcome<00:04:09.340> here<00:04:09.640> is 00:04:09.860 --> 00:04:09.870 align:start position:0% the bat one and so the outcome here is 00:04:09.870 --> 00:04:12.030 align:start position:0% the bat one and so the outcome here is basically<00:04:10.870> on<00:04:11.110> replay<00:04:11.500> it's<00:04:11.620> half<00:04:11.800> can 00:04:12.030 --> 00:04:12.040 align:start position:0% basically on replay it's half can 00:04:12.040 --> 00:04:13.560 align:start position:0% basically on replay it's half can basically<00:04:12.160> just<00:04:12.370> repeat<00:04:12.790> this<00:04:12.940> transaction 00:04:13.560 --> 00:04:13.570 align:start position:0% basically just repeat this transaction 00:04:13.570 --> 00:04:15.210 align:start position:0% basically just repeat this transaction over<00:04:13.840> and<00:04:13.990> over<00:04:14.200> until<00:04:14.410> I<00:04:14.590> lost<00:04:14.770> have<00:04:14.980> more 00:04:15.210 --> 00:04:15.220 align:start position:0% over and over until I lost have more 00:04:15.220 --> 00:04:17.390 align:start position:0% over and over until I lost have more money<00:04:15.400> and<00:04:15.700> Bob<00:04:16.209> has<00:04:16.420> profited<00:04:16.720> massively 00:04:17.390 --> 00:04:17.400 align:start position:0% money and Bob has profited massively 00:04:17.400 --> 00:04:20.610 align:start position:0% money and Bob has profited massively with<00:04:18.400> Hudson's<00:04:18.910> Alex<00:04:19.750> submissive<00:04:20.169> that<00:04:20.410> same 00:04:20.610 --> 00:04:20.620 align:start position:0% with Hudson's Alex submissive that same 00:04:20.620 --> 00:04:22.260 align:start position:0% with Hudson's Alex submissive that same original<00:04:20.950> transaction<00:04:21.310> with<00:04:22.000> announced 00:04:22.260 --> 00:04:22.270 align:start position:0% original transaction with announced 00:04:22.270 --> 00:04:25.320 align:start position:0% original transaction with announced let's<00:04:22.690> say<00:04:22.780> number<00:04:22.960> seven<00:04:23.850> when<00:04:24.850> the<00:04:25.150> liner 00:04:25.320 --> 00:04:25.330 align:start position:0% let's say number seven when the liner 00:04:25.330 --> 00:04:28.320 align:start position:0% let's say number seven when the liner gets<00:04:25.710> Alice's<00:04:26.710> actual<00:04:27.340> transaction<00:04:27.880> and<00:04:28.090> the 00:04:28.320 --> 00:04:28.330 align:start position:0% gets Alice's actual transaction and the 00:04:28.330 --> 00:04:30.870 align:start position:0% gets Alice's actual transaction and the counterfeit<00:04:28.780> one<00:04:29.550> doesn't<00:04:30.550> really<00:04:30.669> matter 00:04:30.870 --> 00:04:30.880 align:start position:0% counterfeit one doesn't really matter 00:04:30.880 --> 00:04:32.310 align:start position:0% counterfeit one doesn't really matter which<00:04:30.970> one<00:04:31.120> is<00:04:31.210> mine<00:04:31.419> both<00:04:31.780> of<00:04:31.960> them<00:04:32.110> will 00:04:32.310 --> 00:04:32.320 align:start position:0% which one is mine both of them will 00:04:32.320 --> 00:04:33.659 align:start position:0% which one is mine both of them will result<00:04:32.680> in<00:04:32.770> the<00:04:32.830> same<00:04:32.980> thing<00:04:33.040> just<00:04:33.610> that 00:04:33.659 --> 00:04:33.669 align:start position:0% result in the same thing just that 00:04:33.669 --> 00:04:36.480 align:start position:0% result in the same thing just that obvious<00:04:34.240> we<00:04:34.330> need<00:04:34.360> from<00:04:34.570> Alice<00:04:35.070> but<00:04:36.070> when<00:04:36.400> the 00:04:36.480 --> 00:04:36.490 align:start position:0% obvious we need from Alice but when the 00:04:36.490 --> 00:04:37.360 align:start position:0% obvious we need from Alice but when the second 00:04:37.360 --> 00:04:37.370 align:start position:0% second 00:04:37.370 --> 00:04:39.490 align:start position:0% second something<00:04:37.760> to<00:04:37.850> be<00:04:37.910> mind<00:04:38.150> it<00:04:38.570> see<00:04:38.750> that<00:04:39.050> the 00:04:39.490 --> 00:04:39.500 align:start position:0% something to be mind it see that the 00:04:39.500 --> 00:04:41.530 align:start position:0% something to be mind it see that the nonsence<00:04:39.860> still<00:04:40.070> seven<00:04:40.520> excessive<00:04:41.180> on<00:04:41.300> speed 00:04:41.530 --> 00:04:41.540 align:start position:0% nonsence still seven excessive on speed 00:04:41.540 --> 00:04:43.420 align:start position:0% nonsence still seven excessive on speed eight<00:04:41.690> now<00:04:41.870> so<00:04:42.140> that<00:04:42.290> connection<00:04:42.650> fails<00:04:43.010> and 00:04:43.420 --> 00:04:43.430 align:start position:0% eight now so that connection fails and 00:04:43.430 --> 00:04:44.680 align:start position:0% eight now so that connection fails and you<00:04:43.490> can't<00:04:43.700> kind<00:04:43.790> of<00:04:43.880> like<00:04:44.060> repeat<00:04:44.510> this 00:04:44.680 --> 00:04:44.690 align:start position:0% you can't kind of like repeat this 00:04:44.690 --> 00:04:50.320 align:start position:0% you can't kind of like repeat this motion<00:04:45.200> attack<00:04:45.620> or<00:04:45.830> over<00:04:47.860> so<00:04:49.060> you<00:04:50.060> know<00:04:50.150> all 00:04:50.320 --> 00:04:50.330 align:start position:0% motion attack or over so you know all 00:04:50.330 --> 00:04:52.630 align:start position:0% motion attack or over so you know all these<00:04:50.480> things<00:04:50.540> need<00:04:50.930> us<00:04:51.050> to<00:04:51.290> where<00:04:52.220> he<00:04:52.250> does 00:04:52.630 --> 00:04:52.640 align:start position:0% these things need us to where he does 00:04:52.640 --> 00:04:56.110 align:start position:0% these things need us to where he does they're<00:04:52.880> not<00:04:53.000> secret<00:04:53.330> formula<00:04:53.780> nasa's<00:04:55.060> so<00:04:56.060> you 00:04:56.110 --> 00:04:56.120 align:start position:0% they're not secret formula nasa's so you 00:04:56.120 --> 00:04:57.430 align:start position:0% they're not secret formula nasa's so you saw<00:04:56.360> the<00:04:56.420> question<00:04:56.660> is<00:04:57.170> this<00:04:57.320> your 00:04:57.430 --> 00:04:57.440 align:start position:0% saw the question is this your 00:04:57.440 --> 00:04:59.620 align:start position:0% saw the question is this your personality<00:04:57.920> if<00:04:58.430> so<00:04:58.640> you're<00:04:59.150> not<00:04:59.240> some<00:04:59.420> zero 00:04:59.620 --> 00:04:59.630 align:start position:0% personality if so you're not some zero 00:04:59.630 --> 00:05:01.840 align:start position:0% personality if so you're not some zero you're<00:04:59.990> going<00:05:00.020> to<00:05:00.200> go<00:05:00.290> no<00:05:01.280> problems<00:05:01.640> there 00:05:01.840 --> 00:05:01.850 align:start position:0% you're going to go no problems there 00:05:01.850 --> 00:05:04.600 align:start position:0% you're going to go no problems there we've<00:05:02.390> not<00:05:02.920> either<00:05:03.920> keeping<00:05:04.160> track<00:05:04.370> of<00:05:04.400> your 00:05:04.600 --> 00:05:04.610 align:start position:0% we've not either keeping track of your 00:05:04.610 --> 00:05:05.650 align:start position:0% we've not either keeping track of your thoughts<00:05:04.790> if<00:05:05.030> you<00:05:05.060> know<00:05:05.330> how<00:05:05.600> many 00:05:05.650 --> 00:05:05.660 align:start position:0% thoughts if you know how many 00:05:05.660 --> 00:05:07.510 align:start position:0% thoughts if you know how many transactions<00:05:06.290> you've<00:05:06.470> sense<00:05:06.740> you're<00:05:07.370> also 00:05:07.510 --> 00:05:07.520 align:start position:0% transactions you've sense you're also 00:05:07.520 --> 00:05:09.460 align:start position:0% transactions you've sense you're also good<00:05:07.760> to<00:05:07.850> go<00:05:08.000> so<00:05:08.630> just<00:05:08.870> an<00:05:08.990> expanded 00:05:09.460 --> 00:05:09.470 align:start position:0% good to go so just an expanded 00:05:09.470 --> 00:05:11.820 align:start position:0% good to go so just an expanded transactions<00:05:10.100> awesome<00:05:11.120> you're<00:05:11.390> not<00:05:11.510> saying 00:05:11.820 --> 00:05:11.830 align:start position:0% transactions awesome you're not saying 00:05:11.830 --> 00:05:14.410 align:start position:0% transactions awesome you're not saying it's<00:05:12.830> not<00:05:12.890> no<00:05:13.430> worries<00:05:13.610> there's<00:05:13.940> backup<00:05:14.240> plan 00:05:14.410 --> 00:05:14.420 align:start position:0% it's not no worries there's backup plan 00:05:14.420 --> 00:05:16.210 align:start position:0% it's not no worries there's backup plan you<00:05:14.990> can<00:05:15.110> call<00:05:15.260> something<00:05:15.440> like<00:05:15.560> get<00:05:16.010> some<00:05:16.130> is 00:05:16.210 --> 00:05:16.220 align:start position:0% you can call something like get some is 00:05:16.220 --> 00:05:18.310 align:start position:0% you can call something like get some is actually<00:05:16.460> pending<00:05:16.940> the<00:05:17.510> result<00:05:17.810> is<00:05:18.200> you're 00:05:18.310 --> 00:05:18.320 align:start position:0% actually pending the result is you're 00:05:18.320 --> 00:05:20.590 align:start position:0% actually pending the result is you're nuts<00:05:18.590> super<00:05:19.220> simple<00:05:19.340> it's<00:05:19.850> a<00:05:19.910> repeat<00:05:20.180> your 00:05:20.590 --> 00:05:20.600 align:start position:0% nuts super simple it's a repeat your 00:05:20.600 --> 00:05:21.910 align:start position:0% nuts super simple it's a repeat your applications<00:05:21.080> while<00:05:21.230> functioning<00:05:21.410> you're 00:05:21.910 --> 00:05:21.920 align:start position:0% applications while functioning you're 00:05:21.920 --> 00:05:25.000 align:start position:0% applications while functioning you're often<00:05:22.220> and<00:05:22.490> probably<00:05:23.410> will<00:05:24.410> cross<00:05:24.590> the<00:05:24.770> drug 00:05:25.000 --> 00:05:25.010 align:start position:0% often and probably will cross the drug 00:05:25.010 --> 00:05:30.250 align:start position:0% often and probably will cross the drug as<00:05:25.730> it<00:05:25.880> turns<00:05:26.090> out<00:05:26.240> a<00:05:26.540> lot<00:05:26.960> can<00:05:27.320> go<00:05:27.350> wrong<00:05:28.600> so<00:05:29.600> as 00:05:30.250 --> 00:05:30.260 align:start position:0% as it turns out a lot can go wrong so as 00:05:30.260 --> 00:05:31.960 align:start position:0% as it turns out a lot can go wrong so as I<00:05:30.320> started<00:05:30.620> to<00:05:30.770> get<00:05:30.860> here<00:05:31.130> let's<00:05:31.430> let's<00:05:31.670> go<00:05:31.850> in 00:05:31.960 --> 00:05:31.970 align:start position:0% I started to get here let's let's go in 00:05:31.970 --> 00:05:33.940 align:start position:0% I started to get here let's let's go in on<00:05:32.090> one<00:05:32.540> of<00:05:32.570> these<00:05:32.660> in<00:05:32.810> that<00:05:32.930> step<00:05:33.170> so<00:05:33.200> come<00:05:33.770> to 00:05:33.940 --> 00:05:33.950 align:start position:0% on one of these in that step so come to 00:05:33.950 --> 00:05:36.640 align:start position:0% on one of these in that step so come to a<00:05:34.600> you<00:05:35.600> know<00:05:35.750> the<00:05:35.900> number<00:05:36.080> of<00:05:36.140> transactions 00:05:36.640 --> 00:05:36.650 align:start position:0% a you know the number of transactions 00:05:36.650 --> 00:05:38.470 align:start position:0% a you know the number of transactions you<00:05:36.740> have<00:05:36.770> that's<00:05:37.670> supposed<00:05:38.270> to<00:05:38.300> be<00:05:38.390> your 00:05:38.470 --> 00:05:38.480 align:start position:0% you have that's supposed to be your 00:05:38.480 --> 00:05:40.570 align:start position:0% you have that's supposed to be your knots<00:05:38.690> that's<00:05:38.900> where<00:05:39.080> knots<00:05:39.260> means<00:05:39.550> so<00:05:40.550> you 00:05:40.570 --> 00:05:40.580 align:start position:0% knots that's where knots means so you 00:05:40.580 --> 00:05:43.330 align:start position:0% knots that's where knots means so you should<00:05:40.790> know<00:05:40.880> that<00:05:41.030> house<00:05:41.500> turns<00:05:42.500> out<00:05:42.680> it's 00:05:43.330 --> 00:05:43.340 align:start position:0% should know that house turns out it's 00:05:43.340 --> 00:05:45.340 align:start position:0% should know that house turns out it's not<00:05:43.430> actually<00:05:43.790> all<00:05:43.940> the<00:05:44.240> time<00:05:44.300> probably<00:05:44.870> isn't 00:05:45.340 --> 00:05:45.350 align:start position:0% not actually all the time probably isn't 00:05:45.350 --> 00:05:47.010 align:start position:0% not actually all the time probably isn't a<00:05:45.530> lot<00:05:45.950> of<00:05:46.040> times<00:05:46.190> it's<00:05:46.340> been<00:05:46.460> fail<00:05:46.640> on<00:05:46.790> you 00:05:47.010 --> 00:05:47.020 align:start position:0% a lot of times it's been fail on you 00:05:47.020 --> 00:05:50.140 align:start position:0% a lot of times it's been fail on you three<00:05:48.020> years<00:05:48.290> that<00:05:48.530> most<00:05:48.890> applications<00:05:49.190> are 00:05:50.140 --> 00:05:50.150 align:start position:0% three years that most applications are 00:05:50.150 --> 00:05:52.120 align:start position:0% three years that most applications are sending<00:05:50.570> multiple<00:05:51.080> transactions<00:05:51.800> at<00:05:51.890> a<00:05:51.920> time 00:05:52.120 --> 00:05:52.130 align:start position:0% sending multiple transactions at a time 00:05:52.130 --> 00:05:53.320 align:start position:0% sending multiple transactions at a time so<00:05:52.400> they<00:05:52.490> intended<00:05:52.850> for<00:05:53.030> multiple 00:05:53.320 --> 00:05:53.330 align:start position:0% so they intended for multiple 00:05:53.330 --> 00:05:55.590 align:start position:0% so they intended for multiple transactions<00:05:53.870> to<00:05:54.020> appear<00:05:54.350> in<00:05:54.890> a<00:05:54.920> single<00:05:55.340> block 00:05:55.590 --> 00:05:55.600 align:start position:0% transactions to appear in a single block 00:05:55.600 --> 00:05:57.610 align:start position:0% transactions to appear in a single block when<00:05:56.600> you<00:05:56.660> do<00:05:56.750> that<00:05:56.870> they're<00:05:57.140> submitting<00:05:57.500> them 00:05:57.610 --> 00:05:57.620 align:start position:0% when you do that they're submitting them 00:05:57.620 --> 00:06:01.030 align:start position:0% when you do that they're submitting them with<00:05:57.770> in<00:05:57.980> commencing<00:05:58.340> analysis<00:05:59.380> let's<00:06:00.380> say<00:06:00.470> 0 00:06:01.030 --> 00:06:01.040 align:start position:0% with in commencing analysis let's say 0 00:06:01.040 --> 00:06:03.310 align:start position:0% with in commencing analysis let's say 0 to<00:06:01.130> n<00:06:01.400> in<00:06:01.490> this<00:06:01.580> case<00:06:01.850> now<00:06:02.630> suppose<00:06:02.960> what 00:06:03.310 --> 00:06:03.320 align:start position:0% to n in this case now suppose what 00:06:03.320 --> 00:06:05.020 align:start position:0% to n in this case now suppose what happens<00:06:03.650> if<00:06:03.860> one<00:06:04.250> of<00:06:04.280> those<00:06:04.400> nonsense<00:06:04.610> fails 00:06:05.020 --> 00:06:05.030 align:start position:0% happens if one of those nonsense fails 00:06:05.030 --> 00:06:07.270 align:start position:0% happens if one of those nonsense fails so<00:06:05.720> the<00:06:05.810> same<00:06:05.990> transaction<00:06:06.290> transaction<00:06:07.070> the 00:06:07.270 --> 00:06:07.280 align:start position:0% so the same transaction transaction the 00:06:07.280 --> 00:06:10.420 align:start position:0% so the same transaction transaction the gospel<00:06:08.440> we<00:06:09.440> go<00:06:09.530> matter<00:06:09.740> was<00:06:09.980> earlier<00:06:10.250> we're 00:06:10.420 --> 00:06:10.430 align:start position:0% gospel we go matter was earlier we're 00:06:10.430 --> 00:06:11.190 align:start position:0% gospel we go matter was earlier we're not 00:06:11.190 --> 00:06:11.200 align:start position:0% not 00:06:11.200 --> 00:06:12.900 align:start position:0% not there's<00:06:11.830> something<00:06:12.310> else<00:06:12.340> that's<00:06:12.610> too<00:06:12.760> high 00:06:12.900 --> 00:06:12.910 align:start position:0% there's something else that's too high 00:06:12.910 --> 00:06:15.090 align:start position:0% there's something else that's too high it<00:06:13.330> hangs<00:06:13.710> and<00:06:14.710> since<00:06:14.890> there's<00:06:15.040> no 00:06:15.090 --> 00:06:15.100 align:start position:0% it hangs and since there's no 00:06:15.100 --> 00:06:16.680 align:start position:0% it hangs and since there's no transaction<00:06:15.760> that's<00:06:15.850> succeeded<00:06:16.360> with<00:06:16.480> nonce 00:06:16.680 --> 00:06:16.690 align:start position:0% transaction that's succeeded with nonce 00:06:16.690 --> 00:06:18.240 align:start position:0% transaction that's succeeded with nonce one<00:06:16.870> at<00:06:16.990> this<00:06:17.080> point<00:06:17.380> all<00:06:17.650> your<00:06:18.070> other 00:06:18.240 --> 00:06:18.250 align:start position:0% one at this point all your other 00:06:18.250 --> 00:06:21.120 align:start position:0% one at this point all your other transactions<00:06:18.820> are<00:06:18.940> having<00:06:19.650> effectively<00:06:20.650> done 00:06:21.120 --> 00:06:21.130 align:start position:0% transactions are having effectively done 00:06:21.130 --> 00:06:26.700 align:start position:0% transactions are having effectively done you<00:06:21.250> might<00:06:21.460> ask<00:06:21.730> for<00:06:21.970> mine<00:06:24.540> so<00:06:25.590> there<00:06:26.590> are<00:06:26.650> a 00:06:26.700 --> 00:06:26.710 align:start position:0% you might ask for mine so there are a 00:06:26.710 --> 00:06:29.760 align:start position:0% you might ask for mine so there are a couple<00:06:26.860> of<00:06:27.010> ways<00:06:27.130> this<00:06:27.370> can<00:06:27.580> happen<00:06:28.650> some<00:06:29.650> that 00:06:29.760 --> 00:06:29.770 align:start position:0% couple of ways this can happen some that 00:06:29.770 --> 00:06:31.500 align:start position:0% couple of ways this can happen some that are<00:06:29.890> failures<00:06:30.700> so<00:06:30.820> they're<00:06:30.970> not<00:06:31.150> like<00:06:31.420> the 00:06:31.500 --> 00:06:31.510 align:start position:0% are failures so they're not like the 00:06:31.510 --> 00:06:33.890 align:start position:0% are failures so they're not like the most<00:06:31.630> common<00:06:31.870> way<00:06:32.080> this<00:06:32.200> happens<00:06:32.530> is<00:06:32.650> also 00:06:33.890 --> 00:06:33.900 align:start position:0% most common way this happens is also 00:06:33.900 --> 00:06:36.600 align:start position:0% most common way this happens is also transactions<00:06:34.900> one<00:06:35.230> one<00:06:35.500> high<00:06:35.680> in<00:06:36.310> X<00:06:36.520> for 00:06:36.600 --> 00:06:36.610 align:start position:0% transactions one one high in X for 00:06:36.610 --> 00:06:38.520 align:start position:0% transactions one one high in X for instance<00:06:36.870> certain<00:06:37.870> traits<00:06:38.080> product<00:06:38.380> passed 00:06:38.520 --> 00:06:38.530 align:start position:0% instance certain traits product passed 00:06:38.530 --> 00:06:41.220 align:start position:0% instance certain traits product passed so<00:06:38.860> failure<00:06:39.640> in<00:06:39.850> this<00:06:39.970> case<00:06:40.150> means<00:06:40.420> a<00:06:40.600> failure 00:06:41.220 --> 00:06:41.230 align:start position:0% so failure in this case means a failure 00:06:41.230 --> 00:06:44.670 align:start position:0% so failure in this case means a failure if<00:06:41.560> we<00:06:41.680> properly<00:06:41.860> bypass<00:06:42.400> the<00:06:42.580> mind<00:06:42.870> or<00:06:43.870> even 00:06:44.670 --> 00:06:44.680 align:start position:0% if we properly bypass the mind or even 00:06:44.680 --> 00:06:49.200 align:start position:0% if we properly bypass the mind or even some<00:06:44.860> basis<00:06:45.130> for<00:06:45.160> outright<00:06:45.520> failures<00:06:47.370> so<00:06:48.370> as<00:06:49.150> a 00:06:49.200 --> 00:06:49.210 align:start position:0% some basis for outright failures so as a 00:06:49.210 --> 00:06:51.870 align:start position:0% some basis for outright failures so as a river<00:06:49.510> from<00:06:49.660> our<00:06:49.840> around<00:06:50.470> earlier<00:06:50.950> you<00:06:51.790> go 00:06:51.870 --> 00:06:51.880 align:start position:0% river from our around earlier you go 00:06:51.880 --> 00:06:53.220 align:start position:0% river from our around earlier you go back<00:06:52.090> a<00:06:52.120> plan<00:06:52.390> you<00:06:52.570> can<00:06:52.690> call<00:06:52.840> get<00:06:52.930> turns<00:06:53.110> at 00:06:53.220 --> 00:06:53.230 align:start position:0% back a plan you can call get turns at 00:06:53.230 --> 00:06:55.440 align:start position:0% back a plan you can call get turns at impending<00:06:53.860> snow<00:06:53.980> worries<00:06:54.340> expand<00:06:54.880> we<00:06:55.300> have<00:06:55.420> a 00:06:55.440 --> 00:06:55.450 align:start position:0% impending snow worries expand we have a 00:06:55.450 --> 00:06:59.490 align:start position:0% impending snow worries expand we have a plan<00:06:56.220> problem<00:06:57.220> is<00:06:57.420> this<00:06:58.420> also<00:06:58.750> fails<00:06:58.960> the<00:06:59.260> huge 00:06:59.490 --> 00:06:59.500 align:start position:0% plan problem is this also fails the huge 00:06:59.500 --> 00:07:01.290 align:start position:0% plan problem is this also fails the huge chunk<00:06:59.770> of<00:06:59.830> the<00:06:59.890> time<00:07:00.070> for<00:07:01.000> completely 00:07:01.290 --> 00:07:01.300 align:start position:0% chunk of the time for completely 00:07:01.300 --> 00:07:03.150 align:start position:0% chunk of the time for completely different<00:07:01.390> reasons<00:07:01.630> so<00:07:02.140> that's<00:07:02.620> sort<00:07:02.770> of<00:07:03.070> an 00:07:03.150 --> 00:07:03.160 align:start position:0% different reasons so that's sort of an 00:07:03.160 --> 00:07:05.490 align:start position:0% different reasons so that's sort of an architectural<00:07:03.580> reason<00:07:03.940> most<00:07:04.930> apps<00:07:05.170> we're 00:07:05.490 --> 00:07:05.500 align:start position:0% architectural reason most apps we're 00:07:05.500 --> 00:07:07.230 align:start position:0% architectural reason most apps we're building<00:07:05.800> out<00:07:05.890> here<00:07:05.920> you<00:07:06.250> need<00:07:06.880> to<00:07:07.030> scale 00:07:07.230 --> 00:07:07.240 align:start position:0% building out here you need to scale 00:07:07.240 --> 00:07:09.240 align:start position:0% building out here you need to scale beyond<00:07:07.600> the<00:07:07.750> single<00:07:07.930> node<00:07:08.230> we<00:07:09.010> do<00:07:09.070> any 00:07:09.240 --> 00:07:09.250 align:start position:0% beyond the single node we do any 00:07:09.250 --> 00:07:11.010 align:start position:0% beyond the single node we do any multiple<00:07:09.520> nodes<00:07:09.730> in<00:07:10.270> the<00:07:10.390> webserver<00:07:10.720> world 00:07:11.010 --> 00:07:11.020 align:start position:0% multiple nodes in the webserver world 00:07:11.020 --> 00:07:12.660 align:start position:0% multiple nodes in the webserver world usable<00:07:11.620> a<00:07:11.740> balancer<00:07:12.130> nice<00:07:12.520> and 00:07:12.660 --> 00:07:12.670 align:start position:0% usable a balancer nice and 00:07:12.670 --> 00:07:14.880 align:start position:0% usable a balancer nice and straightforward<00:07:13.200> turns<00:07:14.200> out<00:07:14.320> we<00:07:14.440> do<00:07:14.590> that<00:07:14.770> we 00:07:14.880 --> 00:07:14.890 align:start position:0% straightforward turns out we do that we 00:07:14.890 --> 00:07:16.410 align:start position:0% straightforward turns out we do that we have<00:07:14.980> a<00:07:15.130> theory<00:07:15.370> on<00:07:15.460> thanks<00:07:16.030> for<00:07:16.150> it<00:07:16.210> to<00:07:16.270> break 00:07:16.410 --> 00:07:16.420 align:start position:0% have a theory on thanks for it to break 00:07:16.420 --> 00:07:19.110 align:start position:0% have a theory on thanks for it to break pretty<00:07:16.780> quickly<00:07:16.960> a<00:07:17.890> lot<00:07:18.370> of<00:07:18.520> people<00:07:18.790> we<00:07:18.910> talk 00:07:19.110 --> 00:07:19.120 align:start position:0% pretty quickly a lot of people we talk 00:07:19.120 --> 00:07:20.520 align:start position:0% pretty quickly a lot of people we talk to<00:07:19.150> when<00:07:19.570> they're<00:07:19.690> really<00:07:19.840> under<00:07:20.050> in-house 00:07:20.520 --> 00:07:20.530 align:start position:0% to when they're really under in-house 00:07:20.530 --> 00:07:22.980 align:start position:0% to when they're really under in-house infrastructure<00:07:21.160> this<00:07:21.820> is<00:07:21.880> exactly<00:07:22.270> they<00:07:22.480> do<00:07:22.540> a 00:07:22.980 --> 00:07:22.990 align:start position:0% infrastructure this is exactly they do a 00:07:22.990 --> 00:07:25.200 align:start position:0% infrastructure this is exactly they do a lot<00:07:23.200> of<00:07:23.230> third<00:07:23.440> party<00:07:23.470> API<00:07:23.950> know<00:07:24.820> things<00:07:25.090> in 00:07:25.200 --> 00:07:25.210 align:start position:0% lot of third party API know things in 00:07:25.210 --> 00:07:27.510 align:start position:0% lot of third party API know things in this<00:07:25.300> way<00:07:25.480> it<00:07:26.140> makes<00:07:26.320> managing<00:07:26.650> ounces<00:07:27.070> bucket 00:07:27.510 --> 00:07:27.520 align:start position:0% this way it makes managing ounces bucket 00:07:27.520 --> 00:07:30.810 align:start position:0% this way it makes managing ounces bucket are<00:07:27.730> so<00:07:28.540> pretty<00:07:28.750> table<00:07:29.110> here<00:07:29.400> fire<00:07:30.400> got<00:07:30.610> bunch 00:07:30.810 --> 00:07:30.820 align:start position:0% are so pretty table here fire got bunch 00:07:30.820 --> 00:07:33.150 align:start position:0% are so pretty table here fire got bunch of<00:07:30.910> transactions<00:07:31.650> theories<00:07:32.650> getting<00:07:32.890> routed 00:07:33.150 --> 00:07:33.160 align:start position:0% of transactions theories getting routed 00:07:33.160 --> 00:07:34.680 align:start position:0% of transactions theories getting routed into<00:07:33.280> one<00:07:33.730> of<00:07:33.820> the<00:07:33.910> many<00:07:34.090> knows 00:07:34.680 --> 00:07:34.690 align:start position:0% into one of the many knows 00:07:34.690 --> 00:07:37.670 align:start position:0% into one of the many knows low<00:07:34.810> bouncer<00:07:35.370> and<00:07:36.370> oh<00:07:36.460> my<00:07:36.580> you<00:07:36.640> to<00:07:37.150> call 00:07:37.670 --> 00:07:37.680 align:start position:0% low bouncer and oh my you to call 00:07:37.680 --> 00:07:40.410 align:start position:0% low bouncer and oh my you to call pendant<00:07:38.680> it<00:07:39.130> might<00:07:39.310> not<00:07:39.460> what<00:07:40.030> happens<00:07:40.330> is 00:07:40.410 --> 00:07:40.420 align:start position:0% pendant it might not what happens is 00:07:40.420 --> 00:07:42.120 align:start position:0% pendant it might not what happens is this<00:07:40.600> also<00:07:40.930> gets<00:07:41.110> routed<00:07:41.320> to<00:07:41.590> only<00:07:41.800> one<00:07:41.980> with 00:07:42.120 --> 00:07:42.130 align:start position:0% this also gets routed to only one with 00:07:42.130 --> 00:07:44.760 align:start position:0% this also gets routed to only one with three<00:07:42.310> nodes<00:07:43.200> and<00:07:44.200> I<00:07:44.320> have<00:07:44.440> three<00:07:44.620> different 00:07:44.760 --> 00:07:44.770 align:start position:0% three nodes and I have three different 00:07:44.770 --> 00:07:46.650 align:start position:0% three nodes and I have three different options<00:07:45.010> depending<00:07:45.610> on<00:07:45.760> where<00:07:46.120> exactly<00:07:46.390> my 00:07:46.650 --> 00:07:46.660 align:start position:0% options depending on where exactly my 00:07:46.660 --> 00:07:48.870 align:start position:0% options depending on where exactly my career<00:07:46.900> gets<00:07:47.110> travel<00:07:47.440> to<00:07:47.620> so<00:07:48.430> this<00:07:48.520> is<00:07:48.670> kinda 00:07:48.870 --> 00:07:48.880 align:start position:0% career gets travel to so this is kinda 00:07:48.880 --> 00:07:52.200 align:start position:0% career gets travel to so this is kinda getting<00:07:48.940> consistency<00:07:49.570> problem<00:07:51.060> here<00:07:52.060> is<00:07:52.180> that 00:07:52.200 --> 00:07:52.210 align:start position:0% getting consistency problem here is that 00:07:52.210 --> 00:07:53.760 align:start position:0% getting consistency problem here is that none<00:07:52.690> of<00:07:52.720> these<00:07:52.840> mountains<00:07:53.260> are<00:07:53.320> correct 00:07:53.760 --> 00:07:53.770 align:start position:0% none of these mountains are correct 00:07:53.770 --> 00:07:56.550 align:start position:0% none of these mountains are correct should<00:07:54.730> be<00:07:54.850> three<00:07:54.990> two<00:07:55.990> and<00:07:56.110> all<00:07:56.200> these<00:07:56.350> cases 00:07:56.550 --> 00:07:56.560 align:start position:0% should be three two and all these cases 00:07:56.560 --> 00:07:59.250 align:start position:0% should be three two and all these cases we<00:07:56.770> actually<00:07:56.830> battering<00:07:57.690> this<00:07:58.690> isn't<00:07:58.930> a<00:07:58.990> race 00:07:59.250 --> 00:07:59.260 align:start position:0% we actually battering this isn't a race 00:07:59.260 --> 00:08:01.590 align:start position:0% we actually battering this isn't a race condition<00:07:59.470> so<00:07:59.980> you<00:08:00.940> know<00:08:01.000> eventually<00:08:01.390> these 00:08:01.590 --> 00:08:01.600 align:start position:0% condition so you know eventually these 00:08:01.600 --> 00:08:03.240 align:start position:0% condition so you know eventually these transactions<00:08:02.230> will<00:08:02.410> propagate<00:08:02.680> to<00:08:03.070> the<00:08:03.130> other 00:08:03.240 --> 00:08:03.250 align:start position:0% transactions will propagate to the other 00:08:03.250 --> 00:08:03.750 align:start position:0% transactions will propagate to the other nodes 00:08:03.750 --> 00:08:03.760 align:start position:0% nodes 00:08:03.760 --> 00:08:06.570 align:start position:0% nodes -<00:08:04.420> little<00:08:04.630> bouncer<00:08:04.990> so<00:08:05.230> if<00:08:05.290> you<00:08:05.440> wait<00:08:06.040> retry 00:08:06.570 --> 00:08:06.580 align:start position:0% - little bouncer so if you wait retry 00:08:06.580 --> 00:08:08.250 align:start position:0% - little bouncer so if you wait retry eventually<00:08:07.510> it<00:08:07.570> might<00:08:07.660> work<00:08:07.810> so<00:08:07.990> that's<00:08:08.050> one 00:08:08.250 --> 00:08:08.260 align:start position:0% eventually it might work so that's one 00:08:08.260 --> 00:08:10.430 align:start position:0% eventually it might work so that's one way<00:08:08.350> of<00:08:08.380> handling<00:08:08.530> this<00:08:08.890> but<00:08:09.220> it's<00:08:10.090> not<00:08:10.240> super 00:08:10.430 --> 00:08:10.440 align:start position:0% way of handling this but it's not super 00:08:10.440 --> 00:08:12.840 align:start position:0% way of handling this but it's not super super<00:08:11.440> well<00:08:11.530> functioning<00:08:11.980> for<00:08:12.190> applications 00:08:12.840 --> 00:08:12.850 align:start position:0% super well functioning for applications 00:08:12.850 --> 00:08:16.920 align:start position:0% super well functioning for applications that<00:08:12.970> have<00:08:13.150> got<00:08:13.450> like<00:08:13.630> latency<00:08:14.050> concerns<00:08:15.930> so 00:08:16.920 --> 00:08:16.930 align:start position:0% that have got like latency concerns so 00:08:16.930 --> 00:08:19.620 align:start position:0% that have got like latency concerns so then<00:08:17.080> there's<00:08:17.920> concern<00:08:18.670> here<00:08:19.000> that<00:08:19.030> makes<00:08:19.570> me 00:08:19.620 --> 00:08:19.630 align:start position:0% then there's concern here that makes me 00:08:19.630 --> 00:08:21.300 align:start position:0% then there's concern here that makes me this<00:08:20.020> is<00:08:20.230> more<00:08:20.440> difficult<00:08:20.590> to<00:08:20.800> deal<00:08:20.920> with 00:08:21.300 --> 00:08:21.310 align:start position:0% this is more difficult to deal with 00:08:21.310 --> 00:08:23.490 align:start position:0% this is more difficult to deal with again<00:08:22.000> the<00:08:22.090> parry<00:08:22.300> actually<00:08:22.660> define<00:08:22.960> anything 00:08:23.490 --> 00:08:23.500 align:start position:0% again the parry actually define anything 00:08:23.500 --> 00:08:26.610 align:start position:0% again the parry actually define anything differently<00:08:24.450> this<00:08:25.450> takes<00:08:25.690> a<00:08:25.750> lot<00:08:25.870> of<00:08:25.930> people<00:08:26.110> a 00:08:26.610 --> 00:08:26.620 align:start position:0% differently this takes a lot of people a 00:08:26.620 --> 00:08:28.500 align:start position:0% differently this takes a lot of people a long<00:08:27.040> time<00:08:27.400> to<00:08:27.670> find<00:08:27.880> out<00:08:28.060> and<00:08:28.270> when<00:08:28.360> they<00:08:28.450> do 00:08:28.500 --> 00:08:28.510 align:start position:0% long time to find out and when they do 00:08:28.510 --> 00:08:30.990 align:start position:0% long time to find out and when they do it's<00:08:28.870> usually<00:08:28.990> after<00:08:29.520> probably<00:08:30.520> a<00:08:30.550> week<00:08:30.730> of 00:08:30.990 --> 00:08:31.000 align:start position:0% it's usually after probably a week of 00:08:31.000 --> 00:08:33.839 align:start position:0% it's usually after probably a week of really<00:08:31.360> really<00:08:31.960> frustrating<00:08:32.530> debugging<00:08:32.919> so 00:08:33.839 --> 00:08:33.849 align:start position:0% really really frustrating debugging so 00:08:33.849 --> 00:08:35.339 align:start position:0% really really frustrating debugging so yeah<00:08:34.000> when<00:08:34.539> they<00:08:34.630> talk<00:08:34.780> about<00:08:34.810> endings 00:08:35.339 --> 00:08:35.349 align:start position:0% yeah when they talk about endings 00:08:35.349 --> 00:08:36.930 align:start position:0% yeah when they talk about endings basically<00:08:35.620> anything<00:08:35.830> in<00:08:36.010> the<00:08:36.070> mempool<00:08:36.400> so<00:08:36.789> you 00:08:36.930 --> 00:08:36.940 align:start position:0% basically anything in the mempool so you 00:08:36.940 --> 00:08:38.550 align:start position:0% basically anything in the mempool so you spit<00:08:37.150> a<00:08:37.180> transaction<00:08:37.539> it<00:08:37.990> hasn't<00:08:38.260> been<00:08:38.320> mined 00:08:38.550 --> 00:08:38.560 align:start position:0% spit a transaction it hasn't been mined 00:08:38.560 --> 00:08:41.010 align:start position:0% spit a transaction it hasn't been mined yet<00:08:38.770> it's<00:08:39.130> considered<00:08:39.520> ending<00:08:39.880> the<00:08:40.840> therapy 00:08:41.010 --> 00:08:41.020 align:start position:0% yet it's considered ending the therapy 00:08:41.020 --> 00:08:42.300 align:start position:0% yet it's considered ending the therapy there's<00:08:41.410> actually<00:08:41.650> this<00:08:41.740> idea<00:08:42.039> of<00:08:42.160> like<00:08:42.280> a 00:08:42.300 --> 00:08:42.310 align:start position:0% there's actually this idea of like a 00:08:42.310 --> 00:08:44.730 align:start position:0% there's actually this idea of like a virtual<00:08:42.969> ending<00:08:43.630> block<00:08:43.870> so<00:08:44.290> it<00:08:44.410> seems<00:08:44.650> that 00:08:44.730 --> 00:08:44.740 align:start position:0% virtual ending block so it seems that 00:08:44.740 --> 00:08:46.890 align:start position:0% virtual ending block so it seems that the<00:08:44.950> new<00:08:45.130> thanks<00:08:46.000> we'll<00:08:46.180> be<00:08:46.270> buying<00:08:46.450> in<00:08:46.810> the 00:08:46.890 --> 00:08:46.900 align:start position:0% the new thanks we'll be buying in the 00:08:46.900 --> 00:08:49.020 align:start position:0% the new thanks we'll be buying in the next<00:08:47.110> block<00:08:47.230> of<00:08:47.560> network<00:08:47.950> shows<00:08:48.790> only<00:08:48.940> a 00:08:49.020 --> 00:08:49.030 align:start position:0% next block of network shows only a 00:08:49.030 --> 00:08:50.910 align:start position:0% next block of network shows only a subset<00:08:49.510> of<00:08:49.570> the<00:08:49.810> things<00:08:50.020> that<00:08:50.230> gets<00:08:50.410> consider 00:08:50.910 --> 00:08:50.920 align:start position:0% subset of the things that gets consider 00:08:50.920 --> 00:08:52.890 align:start position:0% subset of the things that gets consider spending<00:08:51.270> which<00:08:52.270> is<00:08:52.390> that<00:08:52.630> you<00:08:52.750> might 00:08:52.890 --> 00:08:52.900 align:start position:0% spending which is that you might 00:08:52.900 --> 00:08:54.990 align:start position:0% spending which is that you might actually<00:08:53.020> end<00:08:53.200> up<00:08:53.320> with<00:08:53.380> the<00:08:53.530> wrong<00:08:53.710> note<00:08:54.000> the 00:08:54.990 --> 00:08:55.000 align:start position:0% actually end up with the wrong note the 00:08:55.000 --> 00:08:57.450 align:start position:0% actually end up with the wrong note the wrong<00:08:55.150> house<00:08:55.530> prepared<00:08:56.530> when<00:08:56.830> you<00:08:56.860> would<00:08:57.130> have 00:08:57.450 --> 00:08:57.460 align:start position:0% wrong house prepared when you would have 00:08:57.460 --> 00:08:59.610 align:start position:0% wrong house prepared when you would have gotten<00:08:57.700> the<00:08:57.790> wrapper<00:08:58.120> from<00:08:58.240> fungi<00:08:58.870> so<00:08:59.500> go 00:08:59.610 --> 00:08:59.620 align:start position:0% gotten the wrapper from fungi so go 00:08:59.620 --> 00:09:01.170 align:start position:0% gotten the wrapper from fungi so go beyond<00:08:59.830> our<00:08:59.950> table<00:09:00.280> here 00:09:01.170 --> 00:09:01.180 align:start position:0% beyond our table here 00:09:01.180 --> 00:09:04.140 align:start position:0% beyond our table here that's<00:09:02.170> where<00:09:02.290> Perry<00:09:02.530> said<00:09:02.950> you<00:09:03.550> get<00:09:03.730> zero<00:09:04.000> in 00:09:04.140 --> 00:09:04.150 align:start position:0% that's where Perry said you get zero in 00:09:04.150 --> 00:09:06.270 align:start position:0% that's where Perry said you get zero in all<00:09:04.270> cases<00:09:04.510> so<00:09:05.380> again<00:09:05.560> things<00:09:06.070> are<00:09:06.160> not 00:09:06.270 --> 00:09:06.280 align:start position:0% all cases so again things are not 00:09:06.280 --> 00:09:09.030 align:start position:0% all cases so again things are not working<00:09:07.410> there<00:09:08.410> are<00:09:08.500> other<00:09:08.590> things<00:09:08.800> that<00:09:08.920> are 00:09:09.030 --> 00:09:09.040 align:start position:0% working there are other things that are 00:09:09.040 --> 00:09:12.030 align:start position:0% working there are other things that are going<00:09:09.130> on<00:09:09.340> here<00:09:09.790> that<00:09:10.540> you<00:09:11.440> know<00:09:11.560> biggest 00:09:12.030 --> 00:09:12.040 align:start position:0% going on here that you know biggest 00:09:12.040 --> 00:09:14.700 align:start position:0% going on here that you know biggest again<00:09:12.670> more<00:09:13.000> complicated<00:09:13.420> things<00:09:14.410> like<00:09:14.470> race 00:09:14.700 --> 00:09:14.710 align:start position:0% again more complicated things like race 00:09:14.710 --> 00:09:15.420 align:start position:0% again more complicated things like race conditions 00:09:15.420 --> 00:09:15.430 align:start position:0% conditions 00:09:15.430 --> 00:09:17.790 align:start position:0% conditions there's<00:09:15.880> no<00:09:16.000> way<00:09:16.090> show<00:09:16.210> up<00:09:16.390> everywhere<00:09:16.720> if<00:09:17.680> you 00:09:17.790 --> 00:09:17.800 align:start position:0% there's no way show up everywhere if you 00:09:17.800 --> 00:09:20.370 align:start position:0% there's no way show up everywhere if you submit<00:09:18.160> a<00:09:18.190> transaction<00:09:18.940> than<00:09:19.150> all<00:09:19.360> X<00:09:20.080> mounts 00:09:20.370 --> 00:09:20.380 align:start position:0% submit a transaction than all X mounts 00:09:20.380 --> 00:09:22.830 align:start position:0% submit a transaction than all X mounts or<00:09:21.250> get<00:09:21.670> your<00:09:21.820> next<00:09:22.000> encounter<00:09:22.210> very<00:09:22.600> quickly 00:09:22.830 --> 00:09:22.840 align:start position:0% or get your next encounter very quickly 00:09:22.840 --> 00:09:25.440 align:start position:0% or get your next encounter very quickly you<00:09:23.830> don't<00:09:23.890> actually<00:09:24.070> agree<00:09:24.340> on<00:09:24.430> so<00:09:24.970> you<00:09:25.360> know 00:09:25.440 --> 00:09:25.450 align:start position:0% you don't actually agree on so you know 00:09:25.450 --> 00:09:26.880 align:start position:0% you don't actually agree on so you know things<00:09:25.690> are<00:09:25.780> possibly<00:09:26.170> happening<00:09:26.470> it's<00:09:26.830> a 00:09:26.880 --> 00:09:26.890 align:start position:0% things are possibly happening it's a 00:09:26.890 --> 00:09:28.650 align:start position:0% things are possibly happening it's a pretty<00:09:27.010> complicated<00:09:27.340> problem<00:09:27.910> and<00:09:28.000> so<00:09:28.180> things 00:09:28.650 --> 00:09:28.660 align:start position:0% pretty complicated problem and so things 00:09:28.660 --> 00:09:33.630 align:start position:0% pretty complicated problem and so things break<00:09:28.870> apart<00:09:29.140> and<00:09:30.070> eventually<00:09:30.730> fix<00:09:32.190> so<00:09:33.190> you 00:09:33.630 --> 00:09:33.640 align:start position:0% break apart and eventually fix so you 00:09:33.640 --> 00:09:35.220 align:start position:0% break apart and eventually fix so you know<00:09:33.730> we've<00:09:34.000> got<00:09:34.120> two<00:09:34.270> points<00:09:34.600> of<00:09:34.690> contention 00:09:35.220 --> 00:09:35.230 align:start position:0% know we've got two points of contention 00:09:35.230 --> 00:09:40.020 align:start position:0% know we've got two points of contention a<00:09:36.120> few<00:09:37.120> steps<00:09:37.300> that<00:09:37.420> theoretically<00:09:38.200> work<00:09:39.030> but 00:09:40.020 --> 00:09:40.030 align:start position:0% a few steps that theoretically work but 00:09:40.030 --> 00:09:42.720 align:start position:0% a few steps that theoretically work but only<00:09:40.090> sometimes<00:09:40.980> but<00:09:41.980> actually<00:09:42.250> not<00:09:42.370> this<00:09:42.580> is 00:09:42.720 --> 00:09:42.730 align:start position:0% only sometimes but actually not this is 00:09:42.730 --> 00:09:44.220 align:start position:0% only sometimes but actually not this is the<00:09:42.790> one<00:09:42.910> case<00:09:43.090> like<00:09:43.360> the<00:09:43.480> only<00:09:43.750> mounts<00:09:44.080> to<00:09:44.140> be 00:09:44.220 --> 00:09:44.230 align:start position:0% the one case like the only mounts to be 00:09:44.230 --> 00:09:45.750 align:start position:0% the one case like the only mounts to be able<00:09:44.380> to<00:09:44.470> be<00:09:44.590> really<00:09:44.920> amounted<00:09:45.250> about<00:09:45.490> all<00:09:45.670> the 00:09:45.750 --> 00:09:45.760 align:start position:0% able to be really amounted about all the 00:09:45.760 --> 00:09:48.210 align:start position:0% able to be really amounted about all the time<00:09:46.030> is<00:09:46.270> with<00:09:46.480> non<00:09:46.810> zero<00:09:47.110> you<00:09:47.740> can<00:09:47.860> start<00:09:48.070> at<00:09:48.190> a 00:09:48.210 --> 00:09:48.220 align:start position:0% time is with non zero you can start at a 00:09:48.220 --> 00:09:51.650 align:start position:0% time is with non zero you can start at a common<00:09:49.000> area<00:09:49.450> so<00:09:50.020> that<00:09:50.050> it<00:09:50.470> gets<00:09:50.590> complicated 00:09:51.650 --> 00:09:51.660 align:start position:0% common area so that it gets complicated 00:09:51.660 --> 00:09:53.670 align:start position:0% common area so that it gets complicated but<00:09:52.660> there<00:09:52.810> are<00:09:52.930> a<00:09:52.960> lot<00:09:53.050> of<00:09:53.200> other<00:09:53.380> things<00:09:53.620> that 00:09:53.670 --> 00:09:53.680 align:start position:0% but there are a lot of other things that 00:09:53.680 --> 00:09:55.110 align:start position:0% but there are a lot of other things that go<00:09:53.890> wrong<00:09:54.130> so<00:09:54.490> the<00:09:54.580> things<00:09:54.760> we<00:09:54.790> talked<00:09:55.000> about 00:09:55.110 --> 00:09:55.120 align:start position:0% go wrong so the things we talked about 00:09:55.120 --> 00:09:56.520 align:start position:0% go wrong so the things we talked about already<00:09:55.300> there's<00:09:55.810> also<00:09:55.930> problems<00:09:56.230> with 00:09:56.520 --> 00:09:56.530 align:start position:0% already there's also problems with 00:09:56.530 --> 00:09:58.620 align:start position:0% already there's also problems with multiple<00:09:57.490> services<00:09:57.910> managing<00:09:58.360> the<00:09:58.450> same 00:09:58.620 --> 00:09:58.630 align:start position:0% multiple services managing the same 00:09:58.630 --> 00:09:59.700 align:start position:0% multiple services managing the same address 00:09:59.700 --> 00:09:59.710 align:start position:0% address 00:09:59.710 --> 00:10:02.280 align:start position:0% address when<00:10:00.310> nodes<00:10:00.550> we<00:10:00.820> start<00:10:01.120> the<00:10:01.300> menfolk<00:10:02.050> and<00:10:02.170> get 00:10:02.280 --> 00:10:02.290 align:start position:0% when nodes we start the menfolk and get 00:10:02.290 --> 00:10:04.560 align:start position:0% when nodes we start the menfolk and get cleared<00:10:02.560> which<00:10:02.740> can<00:10:02.920> affect<00:10:03.130> nonces<00:10:03.640> changing 00:10:04.560 --> 00:10:04.570 align:start position:0% cleared which can affect nonces changing 00:10:04.570 --> 00:10:06.210 align:start position:0% cleared which can affect nonces changing the<00:10:04.660> organization's<00:10:05.290> have<00:10:05.560> a<00:10:05.590> huge<00:10:05.770> impact<00:10:05.890> on 00:10:06.210 --> 00:10:06.220 align:start position:0% the organization's have a huge impact on 00:10:06.220 --> 00:10:07.860 align:start position:0% the organization's have a huge impact on this<00:10:06.400> so<00:10:06.580> there's<00:10:06.970> a<00:10:07.060> lot<00:10:07.270> to<00:10:07.420> worry<00:10:07.570> about<00:10:07.630> as 00:10:07.860 --> 00:10:07.870 align:start position:0% this so there's a lot to worry about as 00:10:07.870 --> 00:10:09.350 align:start position:0% this so there's a lot to worry about as a<00:10:07.900> developer<00:10:08.350> when<00:10:08.440> it<00:10:08.590> comes<00:10:08.740> to<00:10:08.830> this<00:10:08.950> single 00:10:09.350 --> 00:10:09.360 align:start position:0% a developer when it comes to this single 00:10:09.360 --> 00:10:11.400 align:start position:0% a developer when it comes to this single bitsy<00:10:10.360> claim<00:10:10.570> we<00:10:10.780> released<00:10:11.080> it<00:10:11.230> gets<00:10:11.350> very 00:10:11.400 --> 00:10:11.410 align:start position:0% bitsy claim we released it gets very 00:10:11.410 --> 00:10:14.520 align:start position:0% bitsy claim we released it gets very good<00:10:12.450> so<00:10:13.450> what<00:10:13.570> we<00:10:13.660> do<00:10:13.810> like<00:10:14.260> how<00:10:14.410> do<00:10:14.470> we 00:10:14.520 --> 00:10:14.530 align:start position:0% good so what we do like how do we 00:10:14.530 --> 00:10:17.220 align:start position:0% good so what we do like how do we actually<00:10:14.680> start<00:10:14.890> the<00:10:15.100> analyst<00:10:15.370> problem<00:10:16.230> one 00:10:17.220 --> 00:10:17.230 align:start position:0% actually start the analyst problem one 00:10:17.230 --> 00:10:18.900 align:start position:0% actually start the analyst problem one thing<00:10:17.380> is<00:10:17.470> wait<00:10:17.620> for<00:10:17.800> you<00:10:17.860> to<00:10:18.010> point<00:10:18.160> out<00:10:18.340> they 00:10:18.900 --> 00:10:18.910 align:start position:0% thing is wait for you to point out they 00:10:18.910 --> 00:10:19.970 align:start position:0% thing is wait for you to point out they don't<00:10:19.120> think<00:10:19.360> that's<00:10:19.510> the<00:10:19.630> right<00:10:19.750> solution 00:10:19.970 --> 00:10:19.980 align:start position:0% don't think that's the right solution 00:10:19.980 --> 00:10:21.870 align:start position:0% don't think that's the right solution I'm<00:10:20.980> guessing<00:10:21.310> a<00:10:21.340> lot<00:10:21.430> of<00:10:21.520> people<00:10:21.760> in<00:10:21.820> this 00:10:21.870 --> 00:10:21.880 align:start position:0% I'm guessing a lot of people in this 00:10:21.880 --> 00:10:23.700 align:start position:0% I'm guessing a lot of people in this room<00:10:22.090> have<00:10:22.360> issues<00:10:22.930> they're<00:10:23.140> building<00:10:23.470> right 00:10:23.700 --> 00:10:23.710 align:start position:0% room have issues they're building right 00:10:23.710 --> 00:10:25.890 align:start position:0% room have issues they're building right now<00:10:23.890> they<00:10:24.220> have<00:10:24.430> users<00:10:24.850> they<00:10:25.480> need<00:10:25.660> a<00:10:25.750> solution 00:10:25.890 --> 00:10:25.900 align:start position:0% now they have users they need a solution 00:10:25.900 --> 00:10:29.270 align:start position:0% now they have users they need a solution for<00:10:26.200> this<00:10:26.320> in<00:10:26.500> short-term<00:10:26.770> and<00:10:27.760> waiting<00:10:28.060> for 00:10:29.270 --> 00:10:29.280 align:start position:0% for this in short-term and waiting for 00:10:29.280 --> 00:10:32.090 align:start position:0% for this in short-term and waiting for is<00:10:30.280> not<00:10:30.490> going<00:10:30.640> to<00:10:30.700> do<00:10:30.790> that 00:10:32.090 --> 00:10:32.100 align:start position:0% is not going to do that 00:10:32.100 --> 00:10:35.049 align:start position:0% is not going to do that so<00:10:32.759> let's<00:10:32.910> start<00:10:33.059> on<00:10:33.179> the<00:10:33.239> right<00:10:33.389> without<00:10:33.509> us 00:10:35.049 --> 00:10:35.059 align:start position:0% so let's start on the right without us 00:10:35.059 --> 00:10:37.220 align:start position:0% so let's start on the right without us except<00:10:36.059> one<00:10:36.239> it's<00:10:36.509> really<00:10:36.779> know<00:10:37.079> your 00:10:37.220 --> 00:10:37.230 align:start position:0% except one it's really know your 00:10:37.230 --> 00:10:38.809 align:start position:0% except one it's really know your infrastructure<00:10:37.709> it<00:10:38.189> doesn't<00:10:38.459> seem<00:10:38.639> like 00:10:38.809 --> 00:10:38.819 align:start position:0% infrastructure it doesn't seem like 00:10:38.819 --> 00:10:40.789 align:start position:0% infrastructure it doesn't seem like alcohol<00:10:39.569> like<00:10:39.749> this<00:10:39.929> or<00:10:40.199> I<00:10:40.439> want<00:10:40.649> the 00:10:40.789 --> 00:10:40.799 align:start position:0% alcohol like this or I want the 00:10:40.799 --> 00:10:42.199 align:start position:0% alcohol like this or I want the traditional<00:10:41.309> ways<00:10:41.399> of<00:10:41.429> handling<00:10:41.639> this<00:10:41.939> should 00:10:42.199 --> 00:10:42.209 align:start position:0% traditional ways of handling this should 00:10:42.209 --> 00:10:45.109 align:start position:0% traditional ways of handling this should instruct<00:10:42.869> urban<00:10:43.230> actually<00:10:43.499> do<00:10:43.850> so<00:10:44.850> you<00:10:44.970> know 00:10:45.109 --> 00:10:45.119 align:start position:0% instruct urban actually do so you know 00:10:45.119 --> 00:10:46.970 align:start position:0% instruct urban actually do so you know you<00:10:45.509> know<00:10:45.600> is<00:10:46.019> your<00:10:46.170> in-house<00:10:46.439> system<00:10:46.769> good 00:10:46.970 --> 00:10:46.980 align:start position:0% you know is your in-house system good 00:10:46.980 --> 00:10:48.799 align:start position:0% you know is your in-house system good balancing<00:10:47.309> those<00:10:47.489> is<00:10:47.850> the<00:10:47.970> API<00:10:48.179> abusing<00:10:48.660> doing 00:10:48.799 --> 00:10:48.809 align:start position:0% balancing those is the API abusing doing 00:10:48.809 --> 00:10:51.619 align:start position:0% balancing those is the API abusing doing that<00:10:49.100> it<00:10:50.100> is<00:10:50.309> you<00:10:50.970> can<00:10:51.119> still<00:10:51.269> make<00:10:51.480> this<00:10:51.569> work 00:10:51.619 --> 00:10:51.629 align:start position:0% that it is you can still make this work 00:10:51.629 --> 00:10:53.090 align:start position:0% that it is you can still make this work it's<00:10:52.079> just<00:10:52.199> going<00:10:52.290> to<00:10:52.350> look<00:10:52.559> harder<00:10:52.889> and<00:10:53.009> you 00:10:53.090 --> 00:10:53.100 align:start position:0% it's just going to look harder and you 00:10:53.100 --> 00:10:54.049 align:start position:0% it's just going to look harder and you need<00:10:53.220> to<00:10:53.309> have<00:10:53.429> this<00:10:53.549> in<00:10:53.699> the<00:10:53.759> back<00:10:53.879> your<00:10:54.029> mind 00:10:54.049 --> 00:10:54.059 align:start position:0% need to have this in the back your mind 00:10:54.059 --> 00:10:55.729 align:start position:0% need to have this in the back your mind when<00:10:54.600> you're<00:10:54.720> building<00:10:54.959> things<00:10:55.230> out<00:10:55.410> things 00:10:55.729 --> 00:10:55.739 align:start position:0% when you're building things out things 00:10:55.739 --> 00:10:57.159 align:start position:0% when you're building things out things that<00:10:55.799> are<00:10:55.949> in<00:10:56.009> Hana<00:10:56.160> kotti<00:10:56.369> any<00:10:56.669> losses 00:10:57.159 --> 00:10:57.169 align:start position:0% that are in Hana kotti any losses 00:10:57.169 --> 00:10:59.150 align:start position:0% that are in Hana kotti any losses the<00:10:58.169> other<00:10:58.319> thing<00:10:58.439> is<00:10:58.529> to<00:10:58.679> do<00:10:58.799> the<00:10:58.919> excess 00:10:59.150 --> 00:10:59.160 align:start position:0% the other thing is to do the excess 00:10:59.160 --> 00:11:00.889 align:start position:0% the other thing is to do the excess depending<00:10:59.549> State<00:10:59.759> so<00:11:00.089> nonces<00:11:00.809> are 00:11:00.889 --> 00:11:00.899 align:start position:0% depending State so nonces are 00:11:00.899 --> 00:11:02.479 align:start position:0% depending State so nonces are effectively<00:11:01.290> the<00:11:01.439> way<00:11:01.589> that<00:11:01.889> Henning<00:11:02.399> State 00:11:02.479 --> 00:11:02.489 align:start position:0% effectively the way that Henning State 00:11:02.489 --> 00:11:04.849 align:start position:0% effectively the way that Henning State become<00:11:02.939> this<00:11:03.179> design<00:11:03.419> state<00:11:03.779> so<00:11:04.589> being<00:11:04.769> able 00:11:04.849 --> 00:11:04.859 align:start position:0% become this design state so being able 00:11:04.859 --> 00:11:06.889 align:start position:0% become this design state so being able to<00:11:04.980> see<00:11:05.160> what<00:11:05.609> spending<00:11:06.059> must<00:11:06.329> drop<00:11:06.569> to<00:11:06.779> all 00:11:06.889 --> 00:11:06.899 align:start position:0% to see what spending must drop to all 00:11:06.899 --> 00:11:08.239 align:start position:0% to see what spending must drop to all these<00:11:07.049> kind<00:11:07.259> of<00:11:07.290> things<00:11:07.499> is<00:11:07.709> gonna<00:11:07.859> be<00:11:07.949> really 00:11:08.239 --> 00:11:08.249 align:start position:0% these kind of things is gonna be really 00:11:08.249 --> 00:11:10.369 align:start position:0% these kind of things is gonna be really really<00:11:08.429> helpful<00:11:08.689> some<00:11:09.689> services<00:11:10.049> don't<00:11:10.230> allow 00:11:10.369 --> 00:11:10.379 align:start position:0% really helpful some services don't allow 00:11:10.379 --> 00:11:12.079 align:start position:0% really helpful some services don't allow you<00:11:10.470> can<00:11:10.589> do<00:11:10.679> that<00:11:10.829> if<00:11:11.309> you're<00:11:11.429> we<00:11:11.910> don't 00:11:12.079 --> 00:11:12.089 align:start position:0% you can do that if you're we don't 00:11:12.089 --> 00:11:13.340 align:start position:0% you can do that if you're we don't manage<00:11:12.209> to<00:11:12.299> probably<00:11:12.660> pendency<00:11:13.049> or<00:11:13.139> good 00:11:13.340 --> 00:11:13.350 align:start position:0% manage to probably pendency or good 00:11:13.350 --> 00:11:16.159 align:start position:0% manage to probably pendency or good shape<00:11:14.509> and<00:11:15.509> then<00:11:15.629> are<00:11:15.779> you<00:11:15.869> writing<00:11:16.049> any 00:11:16.159 --> 00:11:16.169 align:start position:0% shape and then are you writing any 00:11:16.169 --> 00:11:18.439 align:start position:0% shape and then are you writing any parity<00:11:16.499> so<00:11:16.739> I<00:11:17.309> want<00:11:17.699> to<00:11:17.730> say<00:11:17.819> for<00:11:17.999> people<00:11:18.269> who 00:11:18.439 --> 00:11:18.449 align:start position:0% parity so I want to say for people who 00:11:18.449 --> 00:11:21.079 align:start position:0% parity so I want to say for people who are<00:11:18.540> using<00:11:18.720> parity<00:11:19.169> is<00:11:20.040> a<00:11:20.069> super<00:11:20.369> quick<00:11:20.519> switch 00:11:21.079 --> 00:11:21.089 align:start position:0% are using parity is a super quick switch 00:11:21.089 --> 00:11:23.269 align:start position:0% are using parity is a super quick switch that<00:11:21.359> use<00:11:21.600> parity<00:11:21.959> next<00:11:22.169> nonsence<00:11:22.709> to<00:11:22.889> get 00:11:23.269 --> 00:11:23.279 align:start position:0% that use parity next nonsence to get 00:11:23.279 --> 00:11:25.220 align:start position:0% that use parity next nonsence to get transaction<00:11:23.759> pending<00:11:24.119> behaves<00:11:24.899> like<00:11:25.049> you 00:11:25.220 --> 00:11:25.230 align:start position:0% transaction pending behaves like you 00:11:25.230 --> 00:11:26.359 align:start position:0% transaction pending behaves like you would<00:11:25.350> expect<00:11:25.439> it<00:11:25.769> to 00:11:26.359 --> 00:11:26.369 align:start position:0% would expect it to 00:11:26.369 --> 00:11:31.879 align:start position:0% would expect it to so<00:11:26.910> work<00:11:27.179> the<00:11:27.749> same<00:11:27.959> way<00:11:27.989> that<00:11:30.649> some<00:11:31.649> are<00:11:31.769> doing 00:11:31.879 --> 00:11:31.889 align:start position:0% so work the same way that some are doing 00:11:31.889 --> 00:11:35.059 align:start position:0% so work the same way that some are doing transaction<00:11:32.819> this<00:11:33.359> basically<00:11:34.069> understand 00:11:35.059 --> 00:11:35.069 align:start position:0% transaction this basically understand 00:11:35.069 --> 00:11:36.979 align:start position:0% transaction this basically understand your<00:11:35.220> new<00:11:35.309> space<00:11:35.610> so<00:11:36.480> today<00:11:36.660> you're<00:11:36.929> doing 00:11:36.979 --> 00:11:36.989 align:start position:0% your new space so today you're doing 00:11:36.989 --> 00:11:38.720 align:start position:0% your new space so today you're doing with<00:11:37.319> those<00:11:37.410> transactions<00:11:38.040> ordering<00:11:38.549> might 00:11:38.720 --> 00:11:38.730 align:start position:0% with those transactions ordering might 00:11:38.730 --> 00:11:40.069 align:start position:0% with those transactions ordering might matter<00:11:38.910> the<00:11:39.239> number<00:11:39.360> of<00:11:39.509> transactions 00:11:40.069 --> 00:11:40.079 align:start position:0% matter the number of transactions 00:11:40.079 --> 00:11:41.629 align:start position:0% matter the number of transactions transactions<00:11:40.980> throughput<00:11:41.309> might<00:11:41.489> matter 00:11:41.629 --> 00:11:41.639 align:start position:0% transactions throughput might matter 00:11:41.639 --> 00:11:44.239 align:start position:0% transactions throughput might matter lates<00:11:42.119> of<00:11:42.299> all<00:11:42.509> these<00:11:42.600> kinds<00:11:42.839> of<00:11:42.869> things<00:11:43.249> so 00:11:44.239 --> 00:11:44.249 align:start position:0% lates of all these kinds of things so 00:11:44.249 --> 00:11:45.559 align:start position:0% lates of all these kinds of things so you<00:11:44.339> need<00:11:44.459> to<00:11:44.549> come<00:11:44.790> up<00:11:44.939> understanding<00:11:45.299> you 00:11:45.559 --> 00:11:45.569 align:start position:0% you need to come up understanding you 00:11:45.569 --> 00:11:47.840 align:start position:0% you need to come up understanding you space<00:11:45.839> to<00:11:45.869> know<00:11:46.559> how<00:11:46.679> you're<00:11:46.799> gonna<00:11:46.860> Bridget 00:11:47.840 --> 00:11:47.850 align:start position:0% space to know how you're gonna Bridget 00:11:47.850 --> 00:11:51.139 align:start position:0% space to know how you're gonna Bridget gnosis<00:11:48.559> and<00:11:49.559> the<00:11:50.100> one<00:11:50.249> what<00:11:50.519> kind<00:11:50.669> of<00:11:50.699> Lea<00:11:50.939> had 00:11:51.139 --> 00:11:51.149 align:start position:0% gnosis and the one what kind of Lea had 00:11:51.149 --> 00:11:53.269 align:start position:0% gnosis and the one what kind of Lea had this<00:11:51.299> consider<00:11:51.959> respecting<00:11:52.529> earlier<00:11:52.919> on<00:11:53.100> it's 00:11:53.269 --> 00:11:53.279 align:start position:0% this consider respecting earlier on it's 00:11:53.279 --> 00:11:55.309 align:start position:0% this consider respecting earlier on it's more<00:11:53.399> a<00:11:53.459> contract<00:11:53.819> development<00:11:54.360> I'd<00:11:55.169> ever 00:11:55.309 --> 00:11:55.319 align:start position:0% more a contract development I'd ever 00:11:55.319 --> 00:11:57.679 align:start position:0% more a contract development I'd ever trade-offs<00:11:55.769> in<00:11:55.980> doing<00:11:56.489> this<00:11:56.639> I<00:11:57.119> think<00:11:57.509> a<00:11:57.600> lot 00:11:57.679 --> 00:11:57.689 align:start position:0% trade-offs in doing this I think a lot 00:11:57.689 --> 00:11:59.479 align:start position:0% trade-offs in doing this I think a lot of<00:11:57.749> people<00:11:58.079> don't<00:11:58.679> end<00:11:58.949> up<00:11:59.069> getting<00:11:59.220> announced 00:11:59.479 --> 00:11:59.489 align:start position:0% of people don't end up getting announced 00:11:59.489 --> 00:12:01.100 align:start position:0% of people don't end up getting announced problems<00:11:59.939> until<00:12:00.179> things<00:12:00.449> are<00:12:00.569> deployed<00:12:00.869> they 00:12:01.100 --> 00:12:01.110 align:start position:0% problems until things are deployed they 00:12:01.110 --> 00:12:02.929 align:start position:0% problems until things are deployed they have<00:12:01.290> users<00:12:01.709> users<00:12:02.189> start<00:12:02.399> complaining<00:12:02.699> or 00:12:02.929 --> 00:12:02.939 align:start position:0% have users users start complaining or 00:12:02.939 --> 00:12:05.269 align:start position:0% have users users start complaining or they're<00:12:03.059> throwing<00:12:03.389> developers<00:12:03.779> do<00:12:04.160> suppose<00:12:05.160> I 00:12:05.269 --> 00:12:05.279 align:start position:0% they're throwing developers do suppose I 00:12:05.279 --> 00:12:08.490 align:start position:0% they're throwing developers do suppose I think<00:12:05.429> through<00:12:05.519> these<00:12:05.639> problems<00:12:05.819> early 00:12:08.490 --> 00:12:08.500 align:start position:0% 00:12:08.500 --> 00:12:11.230 align:start position:0% cool<00:12:09.500> so<00:12:09.650> extraordinary<00:12:10.310> solutions 00:12:11.230 --> 00:12:11.240 align:start position:0% cool so extraordinary solutions 00:12:11.240 --> 00:12:13.630 align:start position:0% cool so extraordinary solutions number<00:12:11.600> one<00:12:11.780> is<00:12:11.930> mutating<00:12:12.770> analysis<00:12:13.160> state<00:12:13.400> is 00:12:13.630 --> 00:12:13.640 align:start position:0% number one is mutating analysis state is 00:12:13.640 --> 00:12:15.520 align:start position:0% number one is mutating analysis state is super<00:12:14.030> super<00:12:14.300> comfortable<00:12:14.420> that<00:12:15.230> way<00:12:15.320> you<00:12:15.410> can 00:12:15.520 --> 00:12:15.530 align:start position:0% super super comfortable that way you can 00:12:15.530 --> 00:12:17.620 align:start position:0% super super comfortable that way you can minimize<00:12:15.800> your<00:12:15.830> dependency<00:12:16.370> on<00:12:16.400> these<00:12:16.640> these 00:12:17.620 --> 00:12:17.630 align:start position:0% minimize your dependency on these these 00:12:17.630 --> 00:12:19.660 align:start position:0% minimize your dependency on these these big<00:12:17.900> guy<00:12:18.050> calls<00:12:18.350> that<00:12:18.590> tend<00:12:18.800> to<00:12:18.830> have<00:12:19.040> their 00:12:19.660 --> 00:12:19.670 align:start position:0% big guy calls that tend to have their 00:12:19.670 --> 00:12:22.060 align:start position:0% big guy calls that tend to have their own<00:12:19.820> set<00:12:19.970> of<00:12:20.000> problems<00:12:20.380> we<00:12:21.380> store<00:12:21.590> knots<00:12:21.860> as<00:12:22.040> a 00:12:22.060 --> 00:12:22.070 align:start position:0% own set of problems we store knots as a 00:12:22.070 --> 00:12:23.710 align:start position:0% own set of problems we store knots as a single<00:12:22.370> atomic<00:12:22.550> counter<00:12:22.970> putting<00:12:23.510> something 00:12:23.710 --> 00:12:23.720 align:start position:0% single atomic counter putting something 00:12:23.720 --> 00:12:25.870 align:start position:0% single atomic counter putting something like<00:12:23.810> Redis<00:12:24.260> all<00:12:24.530> your<00:12:24.740> services<00:12:25.100> can<00:12:25.400> access 00:12:25.870 --> 00:12:25.880 align:start position:0% like Redis all your services can access 00:12:25.880 --> 00:12:27.580 align:start position:0% like Redis all your services can access it<00:12:26.030> increments<00:12:26.360> it<00:12:26.690> you're<00:12:27.290> going<00:12:27.440> pretty 00:12:27.580 --> 00:12:27.590 align:start position:0% it increments it you're going pretty 00:12:27.590 --> 00:12:29.920 align:start position:0% it increments it you're going pretty well<00:12:27.700> and<00:12:28.700> then<00:12:28.820> we<00:12:29.150> can<00:12:29.180> you<00:12:29.390> to<00:12:29.540> when<00:12:29.840> you're 00:12:29.920 --> 00:12:29.930 align:start position:0% well and then we can you to when you're 00:12:29.930 --> 00:12:31.990 align:start position:0% well and then we can you to when you're reserving<00:12:30.200> things<00:12:30.560> you<00:12:30.800> can<00:12:30.920> use<00:12:30.950> those<00:12:31.700> API 00:12:31.990 --> 00:12:32.000 align:start position:0% reserving things you can use those API 00:12:32.000 --> 00:12:35.710 align:start position:0% reserving things you can use those API calls<00:12:32.360> to<00:12:32.510> get<00:12:32.630> the<00:12:33.940> kind<00:12:34.940> of<00:12:35.000> see<00:12:35.360> things<00:12:35.600> to 00:12:35.710 --> 00:12:35.720 align:start position:0% calls to get the kind of see things to 00:12:35.720 --> 00:12:39.340 align:start position:0% calls to get the kind of see things to be<00:12:35.810> done<00:12:35.930> with<00:12:36.850> the<00:12:37.850> next<00:12:38.090> is<00:12:38.210> these<00:12:39.020> know<00:12:39.200> up 00:12:39.340 --> 00:12:39.350 align:start position:0% be done with the next is these know up 00:12:39.350 --> 00:12:41.170 align:start position:0% be done with the next is these know up fillers<00:12:39.740> so<00:12:40.310> this<00:12:40.430> way<00:12:40.580> of<00:12:40.610> handling<00:12:40.970> they 00:12:41.170 --> 00:12:41.180 align:start position:0% fillers so this way of handling they 00:12:41.180 --> 00:12:42.940 align:start position:0% fillers so this way of handling they kind<00:12:41.360> of<00:12:41.390> like<00:12:41.510> hanging<00:12:41.960> transactions 00:12:42.940 --> 00:12:42.950 align:start position:0% kind of like hanging transactions 00:12:42.950 --> 00:12:45.160 align:start position:0% kind of like hanging transactions problem<00:12:43.520> so<00:12:44.330> let's<00:12:44.480> say<00:12:44.600> you<00:12:44.660> submit<00:12:44.930> five 00:12:45.160 --> 00:12:45.170 align:start position:0% problem so let's say you submit five 00:12:45.170 --> 00:12:46.990 align:start position:0% problem so let's say you submit five transactions<00:12:45.770> all<00:12:46.130> once<00:12:46.370> week<00:12:46.700> romantic 00:12:46.990 --> 00:12:47.000 align:start position:0% transactions all once week romantic 00:12:47.000 --> 00:12:49.210 align:start position:0% transactions all once week romantic nonsense<00:12:47.560> thanks<00:12:48.560> for<00:12:48.650> going<00:12:48.710> well<00:12:48.980> initially 00:12:49.210 --> 00:12:49.220 align:start position:0% nonsense thanks for going well initially 00:12:49.220 --> 00:12:51.100 align:start position:0% nonsense thanks for going well initially they're<00:12:49.820> gonna<00:12:49.910> mind<00:12:50.150> successfully<00:12:50.720> and<00:12:51.020> then 00:12:51.100 --> 00:12:51.110 align:start position:0% they're gonna mind successfully and then 00:12:51.110 --> 00:12:52.690 align:start position:0% they're gonna mind successfully and then eventually<00:12:51.290> one<00:12:51.590> fails<00:12:51.830> let<00:12:52.460> me<00:12:52.520> talk<00:12:52.670> about 00:12:52.690 --> 00:12:52.700 align:start position:0% eventually one fails let me talk about 00:12:52.700 --> 00:12:55.750 align:start position:0% eventually one fails let me talk about before<00:12:52.880> the<00:12:53.630> next<00:12:53.780> two<00:12:53.990> in<00:12:54.110> hang<00:12:54.550> what<00:12:55.550> we<00:12:55.640> can 00:12:55.750 --> 00:12:55.760 align:start position:0% before the next two in hang what we can 00:12:55.760 --> 00:12:57.370 align:start position:0% before the next two in hang what we can do<00:12:55.850> this<00:12:56.030> basically<00:12:56.240> greatest<00:12:56.960> called<00:12:57.140> Anila 00:12:57.370 --> 00:12:57.380 align:start position:0% do this basically greatest called Anila 00:12:57.380 --> 00:12:59.410 align:start position:0% do this basically greatest called Anila zeroing<00:12:58.250> transfer<00:12:58.730> to<00:12:58.790> are<00:12:59.000> going<00:12:59.150> to<00:12:59.240> address 00:12:59.410 --> 00:12:59.420 align:start position:0% zeroing transfer to are going to address 00:12:59.420 --> 00:13:02.490 align:start position:0% zeroing transfer to are going to address submit<00:13:00.230> back<00:13:00.380> with<00:13:00.590> the<00:13:00.680> same<00:13:00.860> knots<00:13:01.190> that<00:13:01.490> the 00:13:02.490 --> 00:13:02.500 align:start position:0% submit back with the same knots that the 00:13:02.500 --> 00:13:04.810 align:start position:0% submit back with the same knots that the transaction<00:13:03.500> that<00:13:03.530> fail<00:13:03.800> there's<00:13:04.520> a<00:13:04.580> really 00:13:04.810 --> 00:13:04.820 align:start position:0% transaction that fail there's a really 00:13:04.820 --> 00:13:06.660 align:start position:0% transaction that fail there's a really quick<00:13:05.030> way<00:13:05.240> of<00:13:05.270> jump-starting<00:13:06.140> the<00:13:06.170> system 00:13:06.660 --> 00:13:06.670 align:start position:0% quick way of jump-starting the system 00:13:06.670 --> 00:13:09.730 align:start position:0% quick way of jump-starting the system again<00:13:07.670> this<00:13:07.880> is<00:13:08.090> pretty<00:13:08.930> space<00:13:09.230> dependent 00:13:09.730 --> 00:13:09.740 align:start position:0% again this is pretty space dependent 00:13:09.740 --> 00:13:12.940 align:start position:0% again this is pretty space dependent because<00:13:09.830> it<00:13:10.040> means<00:13:10.790> that<00:13:10.940> your<00:13:11.950> transactions 00:13:12.940 --> 00:13:12.950 align:start position:0% because it means that your transactions 00:13:12.950 --> 00:13:14.830 align:start position:0% because it means that your transactions can't<00:13:13.130> be<00:13:13.220> dependent<00:13:13.640> on<00:13:13.730> ordering<00:13:14.450> let<00:13:14.750> me 00:13:14.830 --> 00:13:14.840 align:start position:0% can't be dependent on ordering let me 00:13:14.840 --> 00:13:17.620 align:start position:0% can't be dependent on ordering let me talk<00:13:14.960> about<00:13:14.990> earlier<00:13:15.410> but<00:13:16.400> if<00:13:16.640> you<00:13:17.000> don't<00:13:17.480> have 00:13:17.620 --> 00:13:17.630 align:start position:0% talk about earlier but if you don't have 00:13:17.630 --> 00:13:19.120 align:start position:0% talk about earlier but if you don't have that<00:13:17.750> apartment<00:13:18.110> that's<00:13:18.380> a<00:13:18.500> really<00:13:18.680> solid<00:13:18.830> way 00:13:19.120 --> 00:13:19.130 align:start position:0% that apartment that's a really solid way 00:13:19.130 --> 00:13:22.690 align:start position:0% that apartment that's a really solid way to<00:13:19.160> keep<00:13:19.430> things<00:13:19.580> have<00:13:19.910> well-functioning<00:13:21.700> so 00:13:22.690 --> 00:13:22.700 align:start position:0% to keep things have well-functioning so 00:13:22.700 --> 00:13:24.040 align:start position:0% to keep things have well-functioning so other<00:13:22.880> things<00:13:22.940> just<00:13:23.270> quickly<00:13:23.690> running<00:13:23.960> out 00:13:24.040 --> 00:13:24.050 align:start position:0% other things just quickly running out 00:13:24.050 --> 00:13:26.920 align:start position:0% other things just quickly running out list<00:13:24.350> this<00:13:24.650> is<00:13:24.800> a<00:13:24.830> 20-minute<00:13:25.520> talk<00:13:25.930> make 00:13:26.920 --> 00:13:26.930 align:start position:0% list this is a 20-minute talk make 00:13:26.930 --> 00:13:27.840 align:start position:0% list this is a 20-minute talk make transactions 00:13:27.840 --> 00:13:27.850 align:start position:0% transactions 00:13:27.850 --> 00:13:29.939 align:start position:0% transactions experience<00:13:28.720> with<00:13:28.810> would've<00:13:29.050> heard<00:13:29.259> things 00:13:29.939 --> 00:13:29.949 align:start position:0% experience with would've heard things 00:13:29.949 --> 00:13:31.559 align:start position:0% experience with would've heard things about<00:13:30.100> if<00:13:30.430> we're<00:13:30.639> ring<00:13:30.850> is<00:13:30.970> really<00:13:31.089> important 00:13:31.559 --> 00:13:31.569 align:start position:0% about if we're ring is really important 00:13:31.569 --> 00:13:33.120 align:start position:0% about if we're ring is really important for<00:13:31.720> you<00:13:31.870> you<00:13:32.170> basically<00:13:32.319> patch<00:13:32.680> so<00:13:32.889> much<00:13:33.040> of 00:13:33.120 --> 00:13:33.130 align:start position:0% for you you basically patch so much of 00:13:33.130 --> 00:13:35.400 align:start position:0% for you you basically patch so much of operations<00:13:33.670> into<00:13:33.910> a<00:13:33.940> single<00:13:34.300> transaction<00:13:34.660> as 00:13:35.400 --> 00:13:35.410 align:start position:0% operations into a single transaction as 00:13:35.410 --> 00:13:37.170 align:start position:0% operations into a single transaction as our<00:13:35.829> contract<00:13:36.310> kind<00:13:36.550> of<00:13:36.610> distribute<00:13:37.000> them 00:13:37.170 --> 00:13:37.180 align:start position:0% our contract kind of distribute them 00:13:37.180 --> 00:13:40.230 align:start position:0% our contract kind of distribute them effectively<00:13:38.339> using<00:13:39.339> one<00:13:39.459> transaction<00:13:39.759> for 00:13:40.230 --> 00:13:40.240 align:start position:0% effectively using one transaction for 00:13:40.240 --> 00:13:41.460 align:start position:0% effectively using one transaction for address<00:13:40.480> per<00:13:40.660> block<00:13:40.899> this<00:13:41.110> is<00:13:41.259> basically 00:13:41.460 --> 00:13:41.470 align:start position:0% address per block this is basically 00:13:41.470 --> 00:13:42.930 align:start position:0% address per block this is basically ideal<00:13:41.800> like<00:13:41.980> you<00:13:42.220> submit<00:13:42.490> one<00:13:42.610> transaction 00:13:42.930 --> 00:13:42.940 align:start position:0% ideal like you submit one transaction 00:13:42.940 --> 00:13:44.850 align:start position:0% ideal like you submit one transaction and<00:13:43.449> you<00:13:43.509> wait<00:13:43.690> for<00:13:43.870> it<00:13:43.959> to<00:13:44.019> be<00:13:44.110> mine<00:13:44.319> until<00:13:44.649> you 00:13:44.850 --> 00:13:44.860 align:start position:0% and you wait for it to be mine until you 00:13:44.860 --> 00:13:46.680 align:start position:0% and you wait for it to be mine until you submit<00:13:45.009> another<00:13:45.279> transaction<00:13:45.639> that's<00:13:46.540> not 00:13:46.680 --> 00:13:46.690 align:start position:0% submit another transaction that's not 00:13:46.690 --> 00:13:47.819 align:start position:0% submit another transaction that's not gonna<00:13:46.810> work<00:13:46.930> for<00:13:47.050> a<00:13:47.110> lot<00:13:47.230> of<00:13:47.290> people<00:13:47.529> to<00:13:47.680> do<00:13:47.740> is 00:13:47.819 --> 00:13:47.829 align:start position:0% gonna work for a lot of people to do is 00:13:47.829 --> 00:13:51.269 align:start position:0% gonna work for a lot of people to do is very<00:13:48.069> slow<00:13:48.459> but<00:13:48.850> you<00:13:49.300> care<00:13:49.930> about<00:13:50.279> minimizing 00:13:51.269 --> 00:13:51.279 align:start position:0% very slow but you care about minimizing 00:13:51.279 --> 00:13:54.030 align:start position:0% very slow but you care about minimizing failures<00:13:51.880> much<00:13:52.269> more<00:13:52.509> than<00:13:52.829> maybe<00:13:53.829> my<00:13:53.889> some 00:13:54.030 --> 00:13:54.040 align:start position:0% failures much more than maybe my some 00:13:54.040 --> 00:13:55.350 align:start position:0% failures much more than maybe my some latency<00:13:54.310> than<00:13:54.610> this<00:13:54.699> might<00:13:54.880> work<00:13:55.000> for<00:13:55.180> each 00:13:55.350 --> 00:13:55.360 align:start position:0% latency than this might work for each 00:13:55.360 --> 00:13:58.019 align:start position:0% latency than this might work for each case<00:13:56.160> it<00:13:57.160> also<00:13:57.310> gave<00:13:57.490> you<00:13:57.639> a<00:13:57.670> nice<00:13:57.790> day 00:13:58.019 --> 00:13:58.029 align:start position:0% case it also gave you a nice day 00:13:58.029 --> 00:13:59.999 align:start position:0% case it also gave you a nice day addresses<00:13:58.509> so<00:13:58.839> one<00:13:59.230> of<00:13:59.259> the<00:13:59.380> things<00:13:59.560> that's 00:13:59.999 --> 00:14:00.009 align:start position:0% addresses so one of the things that's 00:14:00.009 --> 00:14:02.189 align:start position:0% addresses so one of the things that's how<00:14:00.190> big<00:14:00.430> here's<00:14:00.699> a<00:14:00.759> bunch<00:14:01.000> of<00:14:01.120> services<00:14:01.329> using 00:14:02.189 --> 00:14:02.199 align:start position:0% how big here's a bunch of services using 00:14:02.199 --> 00:14:03.389 align:start position:0% how big here's a bunch of services using the<00:14:02.290> same<00:14:02.470> address<00:14:02.589> which<00:14:03.100> are<00:14:03.250> hauling 00:14:03.389 --> 00:14:03.399 align:start position:0% the same address which are hauling 00:14:03.399 --> 00:14:05.160 align:start position:0% the same address which are hauling phonetic<00:14:03.790> nonsense<00:14:04.180> which<00:14:04.360> makes<00:14:04.569> this<00:14:04.660> world 00:14:05.160 --> 00:14:05.170 align:start position:0% phonetic nonsense which makes this world 00:14:05.170 --> 00:14:07.980 align:start position:0% phonetic nonsense which makes this world much<00:14:05.410> more<00:14:05.459> to<00:14:06.459> deal<00:14:06.610> with<00:14:06.720> you<00:14:07.720> can<00:14:07.839> isolate 00:14:07.980 --> 00:14:07.990 align:start position:0% much more to deal with you can isolate 00:14:07.990 --> 00:14:10.110 align:start position:0% much more to deal with you can isolate each<00:14:08.470> service<00:14:08.800> to<00:14:08.920> use<00:14:09.009> its<00:14:09.130> own<00:14:09.190> address<00:14:09.459> you 00:14:10.110 --> 00:14:10.120 align:start position:0% each service to use its own address you 00:14:10.120 --> 00:14:11.910 align:start position:0% each service to use its own address you can<00:14:10.240> kind<00:14:10.420> of<00:14:10.449> make<00:14:10.569> place<00:14:10.899> before<00:14:11.589> much 00:14:11.910 --> 00:14:11.920 align:start position:0% can kind of make place before much 00:14:11.920 --> 00:14:13.079 align:start position:0% can kind of make place before much easier<00:14:12.190> for<00:14:12.310> yourself<00:14:12.610> we're<00:14:12.790> not<00:14:12.850> things 00:14:13.079 --> 00:14:13.089 align:start position:0% easier for yourself we're not things 00:14:13.089 --> 00:14:16.290 align:start position:0% easier for yourself we're not things from<00:14:13.329> stopping<00:14:14.259> on<00:14:14.350> each<00:14:14.440> other<00:14:15.180> and<00:14:16.180> then 00:14:16.290 --> 00:14:16.300 align:start position:0% from stopping on each other and then 00:14:16.300 --> 00:14:18.900 align:start position:0% from stopping on each other and then resets<00:14:17.170> us<00:14:17.319> were<00:14:17.769> super<00:14:18.279> super<00:14:18.399> happy<00:14:18.639> to<00:14:18.759> help 00:14:18.900 --> 00:14:18.910 align:start position:0% resets us were super super happy to help 00:14:18.910 --> 00:14:20.730 align:start position:0% resets us were super super happy to help this<00:14:19.089> is<00:14:19.149> something<00:14:19.449> we<00:14:19.600> helped<00:14:20.230> with<00:14:20.319> online 00:14:20.730 --> 00:14:20.740 align:start position:0% this is something we helped with online 00:14:20.740 --> 00:14:22.259 align:start position:0% this is something we helped with online ad<00:14:20.860> space<00:14:21.100> and<00:14:21.310> sitting<00:14:21.519> basis<00:14:21.850> for<00:14:22.029> a<00:14:22.089> lot<00:14:22.240> of 00:14:22.259 --> 00:14:22.269 align:start position:0% ad space and sitting basis for a lot of 00:14:22.269 --> 00:14:24.960 align:start position:0% ad space and sitting basis for a lot of our<00:14:22.389> users<00:14:22.949> again<00:14:23.949> like<00:14:24.430> a<00:14:24.459> lot<00:14:24.639> of<00:14:24.699> this<00:14:24.819> is 00:14:24.960 --> 00:14:24.970 align:start position:0% our users again like a lot of this is 00:14:24.970 --> 00:14:26.519 align:start position:0% our users again like a lot of this is super<00:14:25.240> you<00:14:25.329> space<00:14:25.540> dependent<00:14:26.019> we're<00:14:26.170> happy<00:14:26.350> to 00:14:26.519 --> 00:14:26.529 align:start position:0% super you space dependent we're happy to 00:14:26.529 --> 00:14:27.720 align:start position:0% super you space dependent we're happy to think<00:14:26.740> through<00:14:26.860> these<00:14:27.009> things<00:14:27.069> with<00:14:27.399> you<00:14:27.519> so 00:14:27.720 --> 00:14:27.730 align:start position:0% think through these things with you so 00:14:27.730 --> 00:14:28.590 align:start position:0% think through these things with you so let's<00:14:27.910> go<00:14:28.029> you're<00:14:28.180> running<00:14:28.360> into<00:14:28.480> those 00:14:28.590 --> 00:14:28.600 align:start position:0% let's go you're running into those 00:14:28.600 --> 00:14:30.090 align:start position:0% let's go you're running into those problems<00:14:28.870> we're<00:14:29.290> not<00:14:29.410> the<00:14:29.500> kind<00:14:29.649> of<00:14:29.769> talk<00:14:29.920> for 00:14:30.090 --> 00:14:30.100 align:start position:0% problems we're not the kind of talk for 00:14:30.100 --> 00:14:31.920 align:start position:0% problems we're not the kind of talk for you<00:14:30.160> a<00:14:30.190> lot<00:14:30.310> of<00:14:30.430> that<00:14:30.550> spaces<00:14:30.940> we've<00:14:31.120> we<00:14:31.720> talk 00:14:31.920 --> 00:14:31.930 align:start position:0% you a lot of that spaces we've we talk 00:14:31.930 --> 00:14:34.670 align:start position:0% you a lot of that spaces we've we talk through<00:14:32.170> and<00:14:33.069> then<00:14:33.160> finally<00:14:33.519> open<00:14:34.389> source 00:14:34.670 --> 00:14:34.680 align:start position:0% through and then finally open source 00:14:34.680 --> 00:14:37.530 align:start position:0% through and then finally open source source<00:14:35.680> talk<00:14:36.459> behind<00:14:36.639> you<00:14:37.029> will<00:14:37.209> this<00:14:37.300> week 00:14:37.530 --> 00:14:37.540 align:start position:0% source talk behind you will this week 00:14:37.540 --> 00:14:39.559 align:start position:0% source talk behind you will this week that<00:14:37.750> are<00:14:37.839> tackling<00:14:38.199> exactly<00:14:38.740> this<00:14:38.860> problem 00:14:39.559 --> 00:14:39.569 align:start position:0% that are tackling exactly this problem 00:14:39.569 --> 00:14:42.090 align:start position:0% that are tackling exactly this problem which<00:14:40.569> is<00:14:40.689> really<00:14:40.720> lovely<00:14:41.079> so<00:14:41.589> we<00:14:41.649> got<00:14:41.769> bloom 00:14:42.090 --> 00:14:42.100 align:start position:0% which is really lovely so we got bloom 00:14:42.100 --> 00:14:46.139 align:start position:0% which is really lovely so we got bloom earlier<00:14:43.089> really<00:14:44.079> cool<00:14:44.350> stuff<00:14:44.560> in<00:14:44.889> tribute<00:14:45.639> pay 00:14:46.139 --> 00:14:46.149 align:start position:0% earlier really cool stuff in tribute pay 00:14:46.149 --> 00:14:48.179 align:start position:0% earlier really cool stuff in tribute pay attention<00:14:46.439> and<00:14:47.439> hopefully<00:14:47.740> we<00:14:47.800> can<00:14:47.920> all<00:14:47.949> solve 00:14:48.179 --> 00:14:48.189 align:start position:0% attention and hopefully we can all solve 00:14:48.189 --> 00:14:49.490 align:start position:0% attention and hopefully we can all solve these<00:14:48.250> problems<00:14:48.579> together 00:14:49.490 --> 00:14:49.500 align:start position:0% these problems together 00:14:49.500 --> 00:14:52.180 align:start position:0% these problems together Thanks 00:14:52.180 --> 00:14:52.190 align:start position:0% Thanks 00:14:52.190 --> 00:14:58.779 align:start position:0% Thanks [Applause]