WEBVTT Kind: captions Language: en 00:00:00.000 --> 00:00:04.350 align:start position:0% foreign 00:00:04.350 --> 00:00:04.360 align:start position:0% 00:00:04.360 --> 00:00:20.769 align:start position:0% [Music] 00:00:20.769 --> 00:00:20.779 align:start position:0% 00:00:20.779 --> 00:00:23.330 align:start position:0% recovery<00:00:21.779> factors 00:00:23.330 --> 00:00:23.340 align:start position:0% recovery factors 00:00:23.340 --> 00:00:25.849 align:start position:0% recovery factors um<00:00:23.400> it's<00:00:23.820> going<00:00:24.060> to<00:00:24.180> be<00:00:24.240> kind<00:00:24.480> of<00:00:24.660> interactive 00:00:25.849 --> 00:00:25.859 align:start position:0% um it's going to be kind of interactive 00:00:25.859 --> 00:00:28.130 align:start position:0% um it's going to be kind of interactive um<00:00:25.920> we'll<00:00:26.100> do<00:00:26.340> some<00:00:26.580> thought<00:00:27.359> experiments<00:00:28.019> and 00:00:28.130 --> 00:00:28.140 align:start position:0% um we'll do some thought experiments and 00:00:28.140 --> 00:00:29.330 align:start position:0% um we'll do some thought experiments and we're<00:00:28.320> going<00:00:28.439> to<00:00:28.500> start<00:00:28.560> with<00:00:28.740> like<00:00:28.920> a<00:00:29.039> toy 00:00:29.330 --> 00:00:29.340 align:start position:0% we're going to start with like a toy 00:00:29.340 --> 00:00:31.550 align:start position:0% we're going to start with like a toy problem<00:00:29.519> and<00:00:30.119> then<00:00:30.240> a<00:00:30.420> toy<00:00:30.720> solution<00:00:31.019> and 00:00:31.550 --> 00:00:31.560 align:start position:0% problem and then a toy solution and 00:00:31.560 --> 00:00:33.049 align:start position:0% problem and then a toy solution and let's<00:00:31.740> see<00:00:32.040> whether<00:00:32.279> we<00:00:32.520> get<00:00:32.640> something<00:00:32.820> that 00:00:33.049 --> 00:00:33.059 align:start position:0% let's see whether we get something that 00:00:33.059 --> 00:00:36.530 align:start position:0% let's see whether we get something that works<00:00:33.420> so<00:00:34.760> what<00:00:35.760> are<00:00:35.940> we<00:00:36.120> really<00:00:36.300> talking 00:00:36.530 --> 00:00:36.540 align:start position:0% works so what are we really talking 00:00:36.540 --> 00:00:37.790 align:start position:0% works so what are we really talking about<00:00:36.660> what<00:00:36.899> we're<00:00:37.079> trying<00:00:37.260> to<00:00:37.380> solve<00:00:37.620> right 00:00:37.790 --> 00:00:37.800 align:start position:0% about what we're trying to solve right 00:00:37.800 --> 00:00:39.709 align:start position:0% about what we're trying to solve right the<00:00:38.100> main<00:00:38.340> problem<00:00:38.579> I'm<00:00:38.760> trying<00:00:38.940> to<00:00:39.059> solve<00:00:39.300> is 00:00:39.709 --> 00:00:39.719 align:start position:0% the main problem I'm trying to solve is 00:00:39.719 --> 00:00:43.729 align:start position:0% the main problem I'm trying to solve is that<00:00:40.020> c<00:00:40.379> phrases<00:00:40.860> are<00:00:41.040> bad<00:00:41.219> right<00:00:42.079> and<00:00:43.079> C 00:00:43.729 --> 00:00:43.739 align:start position:0% that c phrases are bad right and C 00:00:43.739 --> 00:00:47.270 align:start position:0% that c phrases are bad right and C phrases<00:00:44.160> contribute<00:00:44.579> to<00:00:44.760> loss<00:00:45.180> teff<00:00:45.899> and<00:00:46.680> even 00:00:47.270 --> 00:00:47.280 align:start position:0% phrases contribute to loss teff and even 00:00:47.280 --> 00:00:49.790 align:start position:0% phrases contribute to loss teff and even terrorism<00:00:47.760> and<00:00:48.600> seafrases<00:00:49.200> are<00:00:49.320> like<00:00:49.440> a<00:00:49.620> very 00:00:49.790 --> 00:00:49.800 align:start position:0% terrorism and seafrases are like a very 00:00:49.800 --> 00:00:51.470 align:start position:0% terrorism and seafrases are like a very long<00:00:49.920> password<00:00:50.219> right<00:00:50.640> they're<00:00:50.820> easy<00:00:51.059> to<00:00:51.300> use 00:00:51.470 --> 00:00:51.480 align:start position:0% long password right they're easy to use 00:00:51.480 --> 00:00:54.049 align:start position:0% long password right they're easy to use uh<00:00:52.140> easy<00:00:52.379> to<00:00:52.559> lose<00:00:52.739> sorry<00:00:52.980> easy<00:00:53.340> to<00:00:53.579> compromise 00:00:54.049 --> 00:00:54.059 align:start position:0% uh easy to lose sorry easy to compromise 00:00:54.059 --> 00:00:56.450 align:start position:0% uh easy to lose sorry easy to compromise and<00:00:54.840> basically<00:00:55.140> we<00:00:55.379> write<00:00:55.620> it<00:00:55.800> down<00:00:55.860> it's<00:00:56.219> like 00:00:56.450 --> 00:00:56.460 align:start position:0% and basically we write it down it's like 00:00:56.460 --> 00:00:57.529 align:start position:0% and basically we write it down it's like you<00:00:56.760> know 00:00:57.529 --> 00:00:57.539 align:start position:0% you know 00:00:57.539 --> 00:00:59.569 align:start position:0% you know um<00:00:57.600> writing<00:00:58.260> a<00:00:58.320> Post-It<00:00:58.739> note<00:00:58.920> that's<00:00:59.280> you 00:00:59.569 --> 00:00:59.579 align:start position:0% um writing a Post-It note that's you 00:00:59.579 --> 00:01:02.810 align:start position:0% um writing a Post-It note that's you basically<00:00:59.940> when<00:01:00.180> you<00:01:00.360> run<00:01:00.480> out<00:01:00.600> of<00:01:00.719> C<00:01:00.840> freeze 00:01:02.810 --> 00:01:02.820 align:start position:0% basically when you run out of C freeze 00:01:02.820 --> 00:01:05.390 align:start position:0% basically when you run out of C freeze and<00:01:03.600> what<00:01:03.960> we<00:01:04.260> should<00:01:04.440> really<00:01:04.619> be<00:01:04.860> using<00:01:05.100> is 00:01:05.390 --> 00:01:05.400 align:start position:0% and what we should really be using is 00:01:05.400 --> 00:01:08.030 align:start position:0% and what we should really be using is multi-factor<00:01:06.060> authentication<00:01:06.540> right<00:01:07.020> NPC<00:01:07.680> or 00:01:08.030 --> 00:01:08.040 align:start position:0% multi-factor authentication right NPC or 00:01:08.040 --> 00:01:11.690 align:start position:0% multi-factor authentication right NPC or multi-6<00:01:08.780> and<00:01:09.780> why<00:01:10.500> we<00:01:10.740> should<00:01:10.860> use<00:01:11.040> it<00:01:11.159> is<00:01:11.460> the 00:01:11.690 --> 00:01:11.700 align:start position:0% multi-6 and why we should use it is the 00:01:11.700 --> 00:01:13.910 align:start position:0% multi-6 and why we should use it is the outcome<00:01:12.000> of<00:01:12.180> Decades<00:01:12.659> of<00:01:12.840> evolution<00:01:13.260> and<00:01:13.619> user 00:01:13.910 --> 00:01:13.920 align:start position:0% outcome of Decades of evolution and user 00:01:13.920 --> 00:01:16.130 align:start position:0% outcome of Decades of evolution and user authentication<00:01:14.460> right<00:01:15.000> since<00:01:15.240> 1986<00:01:15.900> people 00:01:16.130 --> 00:01:16.140 align:start position:0% authentication right since 1986 people 00:01:16.140 --> 00:01:18.410 align:start position:0% authentication right since 1986 people have<00:01:16.320> been<00:01:16.439> trying<00:01:16.560> to<00:01:16.680> push<00:01:16.979> uh<00:01:17.880> multi-factor 00:01:18.410 --> 00:01:18.420 align:start position:0% have been trying to push uh multi-factor 00:01:18.420 --> 00:01:20.749 align:start position:0% have been trying to push uh multi-factor authentication<00:01:18.840> and<00:01:19.380> it<00:01:19.500> works<00:01:19.860> it<00:01:20.340> provides 00:01:20.749 --> 00:01:20.759 align:start position:0% authentication and it works it provides 00:01:20.759 --> 00:01:22.609 align:start position:0% authentication and it works it provides better<00:01:20.939> security<00:01:21.240> prevents<00:01:22.200> phishing 00:01:22.609 --> 00:01:22.619 align:start position:0% better security prevents phishing 00:01:22.619 --> 00:01:24.830 align:start position:0% better security prevents phishing attacks<00:01:22.979> and<00:01:23.220> is<00:01:23.340> relatively<00:01:23.820> easy<00:01:24.180> to<00:01:24.540> set<00:01:24.659> up 00:01:24.830 --> 00:01:24.840 align:start position:0% attacks and is relatively easy to set up 00:01:24.840 --> 00:01:27.830 align:start position:0% attacks and is relatively easy to set up so<00:01:25.619> hopefully<00:01:25.979> you<00:01:26.520> also<00:01:26.939> use<00:01:27.060> this<00:01:27.299> after 00:01:27.830 --> 00:01:27.840 align:start position:0% so hopefully you also use this after 00:01:27.840 --> 00:01:29.810 align:start position:0% so hopefully you also use this after this<00:01:28.080> talk 00:01:29.810 --> 00:01:29.820 align:start position:0% this talk 00:01:29.820 --> 00:01:32.390 align:start position:0% this talk and<00:01:30.540> let's<00:01:30.659> just<00:01:30.840> talk<00:01:31.020> a<00:01:31.140> bit<00:01:31.259> about<00:01:31.439> NPC<00:01:32.159> and 00:01:32.390 --> 00:01:32.400 align:start position:0% and let's just talk a bit about NPC and 00:01:32.400 --> 00:01:35.030 align:start position:0% and let's just talk a bit about NPC and multi-6<00:01:33.180> so<00:01:34.080> um<00:01:34.080> most<00:01:34.439> of<00:01:34.619> you<00:01:34.740> guys<00:01:34.860> are 00:01:35.030 --> 00:01:35.040 align:start position:0% multi-6 so um most of you guys are 00:01:35.040 --> 00:01:36.770 align:start position:0% multi-6 so um most of you guys are probably<00:01:35.159> familiar<00:01:35.579> multi-6<00:01:36.119> and<00:01:36.420> maybe<00:01:36.540> a 00:01:36.770 --> 00:01:36.780 align:start position:0% probably familiar multi-6 and maybe a 00:01:36.780 --> 00:01:39.410 align:start position:0% probably familiar multi-6 and maybe a bit<00:01:36.900> about<00:01:37.020> NPC<00:01:37.500> and<00:01:38.400> both<00:01:38.579> of<00:01:38.759> them<00:01:38.880> have<00:01:39.119> very 00:01:39.410 --> 00:01:39.420 align:start position:0% bit about NPC and both of them have very 00:01:39.420 --> 00:01:41.450 align:start position:0% bit about NPC and both of them have very similar<00:01:39.900> properties<00:01:40.380> right 00:01:41.450 --> 00:01:41.460 align:start position:0% similar properties right 00:01:41.460 --> 00:01:43.010 align:start position:0% similar properties right um they're<00:01:41.820> both<00:01:42.000> better<00:01:42.180> than<00:01:42.420> C<00:01:42.600> phrase 00:01:43.010 --> 00:01:43.020 align:start position:0% um they're both better than C phrase 00:01:43.020 --> 00:01:45.109 align:start position:0% um they're both better than C phrase they<00:01:43.680> are<00:01:43.799> more<00:01:43.920> hack<00:01:44.159> resistant<00:01:44.640> you<00:01:44.880> have<00:01:45.000> to 00:01:45.109 --> 00:01:45.119 align:start position:0% they are more hack resistant you have to 00:01:45.119 --> 00:01:46.789 align:start position:0% they are more hack resistant you have to compromise<00:01:45.479> multiple<00:01:45.900> factors<00:01:46.259> before<00:01:46.560> you 00:01:46.789 --> 00:01:46.799 align:start position:0% compromise multiple factors before you 00:01:46.799 --> 00:01:48.050 align:start position:0% compromise multiple factors before you lose<00:01:46.920> your<00:01:47.100> account 00:01:48.050 --> 00:01:48.060 align:start position:0% lose your account 00:01:48.060 --> 00:01:49.789 align:start position:0% lose your account um there's<00:01:48.240> better<00:01:48.479> redundancy<00:01:49.259> so<00:01:49.560> if<00:01:49.680> you 00:01:49.789 --> 00:01:49.799 align:start position:0% um there's better redundancy so if you 00:01:49.799 --> 00:01:51.950 align:start position:0% um there's better redundancy so if you lose<00:01:49.920> one<00:01:50.159> factor<00:01:50.460> you're<00:01:50.640> still<00:01:50.759> okay<00:01:50.960> and 00:01:51.950 --> 00:01:51.960 align:start position:0% lose one factor you're still okay and 00:01:51.960 --> 00:01:53.330 align:start position:0% lose one factor you're still okay and that's<00:01:52.200> also<00:01:52.560> the<00:01:52.799> possibility<00:01:53.100> of 00:01:53.330 --> 00:01:53.340 align:start position:0% that's also the possibility of 00:01:53.340 --> 00:01:55.310 align:start position:0% that's also the possibility of additional<00:01:53.820> checks<00:01:54.299> right<00:01:54.600> like<00:01:54.899> a<00:01:55.140> daily 00:01:55.310 --> 00:01:55.320 align:start position:0% additional checks right like a daily 00:01:55.320 --> 00:01:57.649 align:start position:0% additional checks right like a daily spending<00:01:55.799> limits<00:01:56.159> for<00:01:56.340> example<00:01:56.640> but<00:01:57.420> there 00:01:57.649 --> 00:01:57.659 align:start position:0% spending limits for example but there 00:01:57.659 --> 00:02:00.230 align:start position:0% spending limits for example but there are<00:01:57.840> some<00:01:58.079> differences<00:01:58.560> so<00:01:58.979> NPC<00:01:59.460> is<00:01:59.759> off<00:02:00.000> chain 00:02:00.230 --> 00:02:00.240 align:start position:0% are some differences so NPC is off chain 00:02:00.240 --> 00:02:02.810 align:start position:0% are some differences so NPC is off chain multi-6<00:02:01.079> usually<00:02:01.380> on<00:02:01.860> chain<00:02:02.159> as<00:02:02.460> a<00:02:02.640> smart 00:02:02.810 --> 00:02:02.820 align:start position:0% multi-6 usually on chain as a smart 00:02:02.820 --> 00:02:04.370 align:start position:0% multi-6 usually on chain as a smart contract 00:02:04.370 --> 00:02:04.380 align:start position:0% contract 00:02:04.380 --> 00:02:06.530 align:start position:0% contract um so<00:02:04.920> multi-six<00:02:05.460> can<00:02:05.700> support<00:02:05.880> much<00:02:06.360> more 00:02:06.530 --> 00:02:06.540 align:start position:0% um so multi-six can support much more 00:02:06.540 --> 00:02:08.870 align:start position:0% um so multi-six can support much more complex<00:02:06.899> access<00:02:07.259> structures<00:02:07.860> think<00:02:08.580> like 00:02:08.870 --> 00:02:08.880 align:start position:0% complex access structures think like 00:02:08.880 --> 00:02:10.490 align:start position:0% complex access structures think like organizations<00:02:09.539> right<00:02:09.840> thousands<00:02:10.259> of<00:02:10.380> people 00:02:10.490 --> 00:02:10.500 align:start position:0% organizations right thousands of people 00:02:10.500 --> 00:02:12.410 align:start position:0% organizations right thousands of people trying<00:02:10.860> to<00:02:10.979> vote<00:02:11.099> for<00:02:11.280> something 00:02:12.410 --> 00:02:12.420 align:start position:0% trying to vote for something 00:02:12.420 --> 00:02:14.330 align:start position:0% trying to vote for something um<00:02:12.480> whereas<00:02:12.840> NPC<00:02:13.260> usually<00:02:13.620> costs<00:02:13.920> less<00:02:14.040> to 00:02:14.330 --> 00:02:14.340 align:start position:0% um whereas NPC usually costs less to 00:02:14.340 --> 00:02:17.030 align:start position:0% um whereas NPC usually costs less to deploy<00:02:14.700> and<00:02:15.360> operate<00:02:15.780> because<00:02:16.080> of<00:02:16.319> chain<00:02:16.620> so 00:02:17.030 --> 00:02:17.040 align:start position:0% deploy and operate because of chain so 00:02:17.040 --> 00:02:19.309 align:start position:0% deploy and operate because of chain so there's<00:02:17.160> no<00:02:17.340> gas<00:02:17.900> multi-6<00:02:18.900> also<00:02:19.200> have 00:02:19.309 --> 00:02:19.319 align:start position:0% there's no gas multi-6 also have 00:02:19.319 --> 00:02:22.250 align:start position:0% there's no gas multi-6 also have trustless<00:02:19.800> access<00:02:20.099> to<00:02:20.640> on-chain<00:02:21.360> state<00:02:21.599> for 00:02:22.250 --> 00:02:22.260 align:start position:0% trustless access to on-chain state for 00:02:22.260 --> 00:02:23.030 align:start position:0% trustless access to on-chain state for example 00:02:23.030 --> 00:02:23.040 align:start position:0% example 00:02:23.040 --> 00:02:25.010 align:start position:0% example um<00:02:23.099> pricing<00:02:23.520> from<00:02:23.879> dexes<00:02:24.420> as<00:02:24.599> well<00:02:24.780> as<00:02:24.840> like 00:02:25.010 --> 00:02:25.020 align:start position:0% um pricing from dexes as well as like 00:02:25.020 --> 00:02:27.410 align:start position:0% um pricing from dexes as well as like limits<00:02:25.620> based<00:02:26.040> on<00:02:26.099> block<00:02:26.220> time 00:02:27.410 --> 00:02:27.420 align:start position:0% limits based on block time 00:02:27.420 --> 00:02:29.869 align:start position:0% limits based on block time um<00:02:27.480> whereas<00:02:27.780> NPCs<00:02:28.379> cross<00:02:28.620> chain 00:02:29.869 --> 00:02:29.879 align:start position:0% um whereas NPCs cross chain 00:02:29.879 --> 00:02:32.750 align:start position:0% um whereas NPCs cross chain but<00:02:30.660> actually<00:02:30.900> you<00:02:31.319> can<00:02:31.440> use<00:02:31.620> both<00:02:31.860> right<00:02:32.700> um 00:02:32.750 --> 00:02:32.760 align:start position:0% but actually you can use both right um 00:02:32.760 --> 00:02:34.850 align:start position:0% but actually you can use both right um one<00:02:33.060> is<00:02:33.239> probably<00:02:33.480> more<00:02:34.020> useful<00:02:34.319> in<00:02:34.500> like<00:02:34.680> a 00:02:34.850 --> 00:02:34.860 align:start position:0% one is probably more useful in like a 00:02:34.860 --> 00:02:36.110 align:start position:0% one is probably more useful in like a large<00:02:34.980> setup<00:02:35.340> and<00:02:35.459> one's<00:02:35.760> probably<00:02:35.879> more 00:02:36.110 --> 00:02:36.120 align:start position:0% large setup and one's probably more 00:02:36.120 --> 00:02:38.030 align:start position:0% large setup and one's probably more useful<00:02:36.480> for<00:02:36.660> personal<00:02:36.900> setup<00:02:37.379> so<00:02:37.560> NPC<00:02:37.920> is 00:02:38.030 --> 00:02:38.040 align:start position:0% useful for personal setup so NPC is 00:02:38.040 --> 00:02:39.530 align:start position:0% useful for personal setup so NPC is probably<00:02:38.220> more<00:02:38.400> useful<00:02:38.640> for<00:02:38.760> personal<00:02:38.940> setup 00:02:39.530 --> 00:02:39.540 align:start position:0% probably more useful for personal setup 00:02:39.540 --> 00:02:41.330 align:start position:0% probably more useful for personal setup so<00:02:39.900> I'll<00:02:40.020> talk<00:02:40.200> a<00:02:40.319> bit<00:02:40.440> very<00:02:40.860> briefly<00:02:41.099> about 00:02:41.330 --> 00:02:41.340 align:start position:0% so I'll talk a bit very briefly about 00:02:41.340 --> 00:02:43.369 align:start position:0% so I'll talk a bit very briefly about NPC<00:02:41.760> because<00:02:42.239> we<00:02:42.540> need<00:02:42.660> to<00:02:42.840> understand<00:02:43.019> this 00:02:43.369 --> 00:02:43.379 align:start position:0% NPC because we need to understand this 00:02:43.379 --> 00:02:45.290 align:start position:0% NPC because we need to understand this before<00:02:43.739> we<00:02:44.040> talk<00:02:44.280> about 00:02:45.290 --> 00:02:45.300 align:start position:0% before we talk about 00:02:45.300 --> 00:02:47.990 align:start position:0% before we talk about um<00:02:45.360> even<00:02:45.599> multi-6<00:02:46.260> and<00:02:46.680> how<00:02:47.280> to<00:02:47.400> use<00:02:47.519> recovery 00:02:47.990 --> 00:02:48.000 align:start position:0% um even multi-6 and how to use recovery 00:02:48.000 --> 00:02:48.949 align:start position:0% um even multi-6 and how to use recovery factors 00:02:48.949 --> 00:02:48.959 align:start position:0% factors 00:02:48.959 --> 00:02:51.470 align:start position:0% factors so<00:02:49.560> first<00:02:49.860> we<00:02:50.220> need<00:02:50.340> to<00:02:50.459> understand<00:02:50.640> how<00:02:51.360> to 00:02:51.470 --> 00:02:51.480 align:start position:0% so first we need to understand how to 00:02:51.480 --> 00:02:53.990 align:start position:0% so first we need to understand how to share<00:02:51.660> a<00:02:51.840> secret<00:02:52.019> key<00:02:52.319> right<00:02:52.980> imagine<00:02:53.640> you 00:02:53.990 --> 00:02:54.000 align:start position:0% share a secret key right imagine you 00:02:54.000 --> 00:02:55.670 align:start position:0% share a secret key right imagine you drew<00:02:54.300> a<00:02:54.360> line<00:02:54.480> and<00:02:54.900> the<00:02:55.080> Y<00:02:55.200> intercept 00:02:55.670 --> 00:02:55.680 align:start position:0% drew a line and the Y intercept 00:02:55.680 --> 00:02:58.430 align:start position:0% drew a line and the Y intercept represents<00:02:56.340> your<00:02:56.459> private<00:02:56.819> key<00:02:56.940> right 00:02:58.430 --> 00:02:58.440 align:start position:0% represents your private key right 00:02:58.440 --> 00:03:00.949 align:start position:0% represents your private key right now<00:02:58.920> you<00:02:59.099> draw<00:02:59.220> three<00:02:59.459> points<00:02:59.700> in<00:02:59.819> a<00:02:59.940> line 00:03:00.949 --> 00:03:00.959 align:start position:0% now you draw three points in a line 00:03:00.959 --> 00:03:03.890 align:start position:0% now you draw three points in a line and<00:03:01.440> then<00:03:01.560> you<00:03:01.739> erase<00:03:02.099> the<00:03:02.280> line<00:03:02.459> right 00:03:03.890 --> 00:03:03.900 align:start position:0% and then you erase the line right 00:03:03.900 --> 00:03:06.229 align:start position:0% and then you erase the line right and<00:03:04.800> with<00:03:05.160> one<00:03:05.340> point<00:03:05.519> if<00:03:05.760> you<00:03:05.879> only<00:03:06.000> have<00:03:06.120> one 00:03:06.229 --> 00:03:06.239 align:start position:0% and with one point if you only have one 00:03:06.239 --> 00:03:07.910 align:start position:0% and with one point if you only have one of<00:03:06.360> the<00:03:06.480> points<00:03:06.720> you<00:03:07.080> can't<00:03:07.200> redraw<00:03:07.680> the<00:03:07.800> line 00:03:07.910 --> 00:03:07.920 align:start position:0% of the points you can't redraw the line 00:03:07.920 --> 00:03:09.350 align:start position:0% of the points you can't redraw the line right<00:03:08.160> it's<00:03:08.280> not<00:03:08.459> possible<00:03:08.700> any<00:03:09.000> number<00:03:09.239> of 00:03:09.350 --> 00:03:09.360 align:start position:0% right it's not possible any number of 00:03:09.360 --> 00:03:11.570 align:start position:0% right it's not possible any number of lines<00:03:09.599> could<00:03:09.840> pass<00:03:10.019> through<00:03:10.200> it<00:03:10.379> on<00:03:11.040> by<00:03:11.220> two 00:03:11.570 --> 00:03:11.580 align:start position:0% lines could pass through it on by two 00:03:11.580 --> 00:03:13.369 align:start position:0% lines could pass through it on by two you<00:03:12.000> can<00:03:12.120> you<00:03:12.480> can<00:03:12.599> redraw<00:03:12.959> the<00:03:13.080> line<00:03:13.200> and 00:03:13.369 --> 00:03:13.379 align:start position:0% you can you can redraw the line and 00:03:13.379 --> 00:03:15.589 align:start position:0% you can you can redraw the line and recover<00:03:13.680> your<00:03:14.040> key<00:03:14.640> this<00:03:15.060> is<00:03:15.180> basically 00:03:15.589 --> 00:03:15.599 align:start position:0% recover your key this is basically 00:03:15.599 --> 00:03:17.630 align:start position:0% recover your key this is basically xiaomi's<00:03:16.379> secret<00:03:16.500> sharing 00:03:17.630 --> 00:03:17.640 align:start position:0% xiaomi's secret sharing 00:03:17.640 --> 00:03:19.070 align:start position:0% xiaomi's secret sharing um<00:03:17.700> which<00:03:17.879> splits<00:03:18.300> a<00:03:18.420> private<00:03:18.720> key<00:03:18.840> into 00:03:19.070 --> 00:03:19.080 align:start position:0% um which splits a private key into 00:03:19.080 --> 00:03:21.710 align:start position:0% um which splits a private key into multiple<00:03:19.560> shares<00:03:20.040> and<00:03:20.700> by<00:03:20.819> tying<00:03:21.239> each<00:03:21.420> share 00:03:21.710 --> 00:03:21.720 align:start position:0% multiple shares and by tying each share 00:03:21.720 --> 00:03:23.690 align:start position:0% multiple shares and by tying each share to<00:03:21.900> some<00:03:22.080> user<00:03:22.560> Factor<00:03:22.920> we<00:03:23.459> can<00:03:23.580> get 00:03:23.690 --> 00:03:23.700 align:start position:0% to some user Factor we can get 00:03:23.700 --> 00:03:25.970 align:start position:0% to some user Factor we can get multi-factor<00:03:24.420> authentication<00:03:24.959> on<00:03:25.560> private 00:03:25.970 --> 00:03:25.980 align:start position:0% multi-factor authentication on private 00:03:25.980 --> 00:03:27.350 align:start position:0% multi-factor authentication on private keys 00:03:27.350 --> 00:03:27.360 align:start position:0% keys 00:03:27.360 --> 00:03:31.070 align:start position:0% keys and<00:03:28.319> where<00:03:28.620> does<00:03:28.739> NPC<00:03:29.159> come<00:03:29.400> in<00:03:29.580> NPC<00:03:30.480> does<00:03:30.780> all 00:03:31.070 --> 00:03:31.080 align:start position:0% and where does NPC come in NPC does all 00:03:31.080 --> 00:03:32.990 align:start position:0% and where does NPC come in NPC does all of<00:03:31.200> this<00:03:31.379> except<00:03:31.800> there's<00:03:32.040> no<00:03:32.340> line<00:03:32.519> drawing 00:03:32.990 --> 00:03:33.000 align:start position:0% of this except there's no line drawing 00:03:33.000 --> 00:03:35.570 align:start position:0% of this except there's no line drawing and<00:03:33.599> basically<00:03:34.019> it<00:03:34.200> avoids<00:03:34.739> a<00:03:35.220> single<00:03:35.459> point 00:03:35.570 --> 00:03:35.580 align:start position:0% and basically it avoids a single point 00:03:35.580 --> 00:03:36.949 align:start position:0% and basically it avoids a single point of<00:03:35.760> failure<00:03:36.120> because<00:03:36.540> when<00:03:36.840> you're 00:03:36.949 --> 00:03:36.959 align:start position:0% of failure because when you're 00:03:36.959 --> 00:03:39.589 align:start position:0% of failure because when you're generating<00:03:37.319> a<00:03:37.620> key<00:03:37.800> if<00:03:38.640> you're<00:03:38.879> if<00:03:39.360> your 00:03:39.589 --> 00:03:39.599 align:start position:0% generating a key if you're if your 00:03:39.599 --> 00:03:41.270 align:start position:0% generating a key if you're if your device<00:03:39.840> is<00:03:40.200> compromised<00:03:40.739> at<00:03:40.860> that<00:03:40.980> point<00:03:41.159> in 00:03:41.270 --> 00:03:41.280 align:start position:0% device is compromised at that point in 00:03:41.280 --> 00:03:43.850 align:start position:0% device is compromised at that point in time<00:03:41.400> the<00:03:41.700> key<00:03:41.819> could<00:03:42.120> be<00:03:42.299> stolen<00:03:42.720> whereas<00:03:43.500> NPC 00:03:43.850 --> 00:03:43.860 align:start position:0% time the key could be stolen whereas NPC 00:03:43.860 --> 00:03:46.130 align:start position:0% time the key could be stolen whereas NPC just<00:03:44.040> does<00:03:44.220> that<00:03:44.400> in<00:03:44.640> a<00:03:44.819> distributed<00:03:45.239> way<00:03:45.480> for 00:03:46.130 --> 00:03:46.140 align:start position:0% just does that in a distributed way for 00:03:46.140 --> 00:03:47.869 align:start position:0% just does that in a distributed way for today<00:03:46.319> we'll<00:03:46.620> just<00:03:46.799> limit<00:03:46.920> the<00:03:47.280> scope<00:03:47.459> to 00:03:47.869 --> 00:03:47.879 align:start position:0% today we'll just limit the scope to 00:03:47.879 --> 00:03:49.369 align:start position:0% today we'll just limit the scope to personal<00:03:48.120> key<00:03:48.480> management<00:03:48.659> but<00:03:49.019> of<00:03:49.260> course 00:03:49.369 --> 00:03:49.379 align:start position:0% personal key management but of course 00:03:49.379 --> 00:03:51.410 align:start position:0% personal key management but of course you<00:03:49.620> can<00:03:49.739> use<00:03:49.799> NPC<00:03:50.280> for<00:03:50.519> other<00:03:50.819> things<00:03:51.000> as<00:03:51.239> well 00:03:51.410 --> 00:03:51.420 align:start position:0% you can use NPC for other things as well 00:03:51.420 --> 00:03:53.449 align:start position:0% you can use NPC for other things as well managing<00:03:52.200> it<00:03:52.319> in<00:03:52.500> like<00:03:52.560> an<00:03:52.739> organization<00:03:53.220> if 00:03:53.449 --> 00:03:53.459 align:start position:0% managing it in like an organization if 00:03:53.459 --> 00:03:55.309 align:start position:0% managing it in like an organization if you<00:03:53.580> wanted 00:03:55.309 --> 00:03:55.319 align:start position:0% you wanted 00:03:55.319 --> 00:03:58.430 align:start position:0% you wanted so<00:03:56.159> the<00:03:56.400> Crux<00:03:57.000> of<00:03:57.120> the<00:03:57.239> problem<00:03:57.480> and<00:03:58.019> what<00:03:58.260> my 00:03:58.430 --> 00:03:58.440 align:start position:0% so the Crux of the problem and what my 00:03:58.440 --> 00:04:00.949 align:start position:0% so the Crux of the problem and what my talk<00:03:58.560> is<00:03:58.799> mainly<00:03:59.220> about<00:03:59.400> is<00:04:00.360> there's<00:04:00.720> this 00:04:00.949 --> 00:04:00.959 align:start position:0% talk is mainly about is there's this 00:04:00.959 --> 00:04:03.130 align:start position:0% talk is mainly about is there's this binary<00:04:01.379> dilemma<00:04:02.040> right<00:04:02.459> between 00:04:03.130 --> 00:04:03.140 align:start position:0% binary dilemma right between 00:04:03.140 --> 00:04:06.470 align:start position:0% binary dilemma right between non-custodiality<00:04:04.140> and<00:04:04.860> custodiality<00:04:05.700> what 00:04:06.470 --> 00:04:06.480 align:start position:0% non-custodiality and custodiality what 00:04:06.480 --> 00:04:08.089 align:start position:0% non-custodiality and custodiality what do<00:04:06.599> I<00:04:06.720> mean<00:04:06.900> right 00:04:08.089 --> 00:04:08.099 align:start position:0% do I mean right 00:04:08.099 --> 00:04:11.570 align:start position:0% do I mean right we<00:04:08.879> say<00:04:09.120> a<00:04:09.420> key<00:04:09.540> is<00:04:09.780> non-custodial<00:04:10.560> if<00:04:11.099> a<00:04:11.280> user 00:04:11.570 --> 00:04:11.580 align:start position:0% we say a key is non-custodial if a user 00:04:11.580 --> 00:04:13.850 align:start position:0% we say a key is non-custodial if a user has<00:04:12.000> full<00:04:12.299> control<00:04:12.540> of<00:04:12.900> the<00:04:13.019> majority<00:04:13.379> shares 00:04:13.850 --> 00:04:13.860 align:start position:0% has full control of the majority shares 00:04:13.860 --> 00:04:15.710 align:start position:0% has full control of the majority shares so<00:04:14.040> let's<00:04:14.159> say<00:04:14.280> you<00:04:14.459> had<00:04:14.700> three<00:04:14.879> shares<00:04:15.299> right 00:04:15.710 --> 00:04:15.720 align:start position:0% so let's say you had three shares right 00:04:15.720 --> 00:04:17.150 align:start position:0% so let's say you had three shares right and<00:04:15.959> you<00:04:16.139> require<00:04:16.320> two<00:04:16.680> of<00:04:16.859> them<00:04:16.979> to 00:04:17.150 --> 00:04:17.160 align:start position:0% and you require two of them to 00:04:17.160 --> 00:04:19.129 align:start position:0% and you require two of them to reconstruct<00:04:17.579> a<00:04:17.760> key<00:04:17.880> as<00:04:18.419> long<00:04:18.600> as<00:04:18.720> two<00:04:18.840> of<00:04:19.019> them 00:04:19.129 --> 00:04:19.139 align:start position:0% reconstruct a key as long as two of them 00:04:19.139 --> 00:04:20.569 align:start position:0% reconstruct a key as long as two of them are<00:04:19.320> fully<00:04:19.560> owned<00:04:19.799> by<00:04:19.919> the<00:04:20.040> user<00:04:20.340> it's 00:04:20.569 --> 00:04:20.579 align:start position:0% are fully owned by the user it's 00:04:20.579 --> 00:04:22.909 align:start position:0% are fully owned by the user it's considered<00:04:21.000> non-custodial<00:04:21.780> since<00:04:22.320> the<00:04:22.620> user 00:04:22.909 --> 00:04:22.919 align:start position:0% considered non-custodial since the user 00:04:22.919 --> 00:04:25.070 align:start position:0% considered non-custodial since the user can<00:04:23.100> easily<00:04:23.520> move<00:04:23.699> his<00:04:23.940> key<00:04:24.180> as<00:04:24.600> well<00:04:24.780> as<00:04:24.900> use 00:04:25.070 --> 00:04:25.080 align:start position:0% can easily move his key as well as use 00:04:25.080 --> 00:04:27.230 align:start position:0% can easily move his key as well as use it<00:04:25.259> but<00:04:25.380> no<00:04:25.620> other<00:04:25.800> person<00:04:26.100> can<00:04:26.639> control<00:04:26.880> the 00:04:27.230 --> 00:04:27.240 align:start position:0% it but no other person can control the 00:04:27.240 --> 00:04:27.969 align:start position:0% it but no other person can control the key 00:04:27.969 --> 00:04:27.979 align:start position:0% key 00:04:27.979 --> 00:04:30.590 align:start position:0% key whereas<00:04:28.979> aqui<00:04:29.520> is<00:04:29.639> custodial<00:04:30.120> of<00:04:30.419> third 00:04:30.590 --> 00:04:30.600 align:start position:0% whereas aqui is custodial of third 00:04:30.600 --> 00:04:32.990 align:start position:0% whereas aqui is custodial of third parties<00:04:31.020> which<00:04:31.380> we<00:04:31.560> call<00:04:31.680> custodians<00:04:32.460> right 00:04:32.990 --> 00:04:33.000 align:start position:0% parties which we call custodians right 00:04:33.000 --> 00:04:34.730 align:start position:0% parties which we call custodians right have<00:04:33.360> control<00:04:33.660> over<00:04:33.900> a<00:04:34.139> majority<00:04:34.440> of<00:04:34.560> the 00:04:34.730 --> 00:04:34.740 align:start position:0% have control over a majority of the 00:04:34.740 --> 00:04:38.150 align:start position:0% have control over a majority of the shares<00:04:35.460> and<00:04:35.940> it's<00:04:36.060> pretty<00:04:36.240> obvious<00:04:36.600> that<00:04:37.199> the 00:04:38.150 --> 00:04:38.160 align:start position:0% shares and it's pretty obvious that the 00:04:38.160 --> 00:04:40.310 align:start position:0% shares and it's pretty obvious that the above<00:04:38.460> are<00:04:38.820> exclusive<00:04:39.419> properties<00:04:39.840> right<00:04:40.080> you 00:04:40.310 --> 00:04:40.320 align:start position:0% above are exclusive properties right you 00:04:40.320 --> 00:04:43.189 align:start position:0% above are exclusive properties right you kind<00:04:40.560> of<00:04:40.680> like<00:04:40.860> two<00:04:41.100> majorities<00:04:41.580> so<00:04:42.479> either 00:04:43.189 --> 00:04:43.199 align:start position:0% kind of like two majorities so either 00:04:43.199 --> 00:04:45.950 align:start position:0% kind of like two majorities so either get<00:04:43.639> non-custodiality<00:04:44.639> or<00:04:45.479> you<00:04:45.660> get<00:04:45.780> full 00:04:45.950 --> 00:04:45.960 align:start position:0% get non-custodiality or you get full 00:04:45.960 --> 00:04:48.409 align:start position:0% get non-custodiality or you get full custodiality<00:04:46.759> and<00:04:47.759> there's<00:04:48.000> some<00:04:48.180> special 00:04:48.409 --> 00:04:48.419 align:start position:0% custodiality and there's some special 00:04:48.419 --> 00:04:50.510 align:start position:0% custodiality and there's some special cases<00:04:48.840> like<00:04:49.199> if<00:04:49.620> the<00:04:49.800> user<00:04:50.040> owns<00:04:50.280> a<00:04:50.340> share 00:04:50.510 --> 00:04:50.520 align:start position:0% cases like if the user owns a share 00:04:50.520 --> 00:04:52.850 align:start position:0% cases like if the user owns a share Enterprise<00:04:50.759> share<00:04:51.600> but<00:04:51.780> let's<00:04:52.320> not<00:04:52.560> think 00:04:52.850 --> 00:04:52.860 align:start position:0% Enterprise share but let's not think 00:04:52.860 --> 00:04:55.670 align:start position:0% Enterprise share but let's not think about<00:04:53.040> that<00:04:53.280> for<00:04:53.520> now<00:04:53.720> but<00:04:54.720> realistically 00:04:55.670 --> 00:04:55.680 align:start position:0% about that for now but realistically 00:04:55.680 --> 00:04:57.110 align:start position:0% about that for now but realistically would<00:04:56.040> it<00:04:56.220> be<00:04:56.340> nice<00:04:56.520> if<00:04:56.699> we<00:04:56.820> have<00:04:57.000> something 00:04:57.110 --> 00:04:57.120 align:start position:0% would it be nice if we have something 00:04:57.120 --> 00:04:58.730 align:start position:0% would it be nice if we have something better 00:04:58.730 --> 00:04:58.740 align:start position:0% better 00:04:58.740 --> 00:05:02.270 align:start position:0% better ideally<00:04:59.639> right<00:05:00.300> what<00:05:00.660> I<00:05:00.900> really<00:05:01.020> want<00:05:01.380> is<00:05:02.160> that 00:05:02.270 --> 00:05:02.280 align:start position:0% ideally right what I really want is that 00:05:02.280 --> 00:05:03.710 align:start position:0% ideally right what I really want is that my<00:05:02.460> private<00:05:02.699> key<00:05:02.820> should<00:05:03.000> be<00:05:03.060> non-custodial 00:05:03.710 --> 00:05:03.720 align:start position:0% my private key should be non-custodial 00:05:03.720 --> 00:05:06.290 align:start position:0% my private key should be non-custodial all<00:05:04.380> the<00:05:04.560> time<00:05:05.100> until<00:05:05.580> I've<00:05:05.940> accidentally 00:05:06.290 --> 00:05:06.300 align:start position:0% all the time until I've accidentally 00:05:06.300 --> 00:05:08.150 align:start position:0% all the time until I've accidentally lost<00:05:06.540> all<00:05:06.780> my<00:05:06.900> factors<00:05:07.259> or<00:05:07.620> you<00:05:07.919> know<00:05:07.979> touch 00:05:08.150 --> 00:05:08.160 align:start position:0% lost all my factors or you know touch 00:05:08.160 --> 00:05:10.909 align:start position:0% lost all my factors or you know touch food<00:05:08.520> I<00:05:08.880> die<00:05:09.060> then<00:05:09.720> it's<00:05:10.020> somehow<00:05:10.500> you<00:05:10.860> know 00:05:10.909 --> 00:05:10.919 align:start position:0% food I die then it's somehow you know 00:05:10.919 --> 00:05:13.670 align:start position:0% food I die then it's somehow you know transitions<00:05:11.580> to<00:05:11.759> become<00:05:12.060> custodial<00:05:13.020> right<00:05:13.380> so 00:05:13.670 --> 00:05:13.680 align:start position:0% transitions to become custodial right so 00:05:13.680 --> 00:05:15.590 align:start position:0% transitions to become custodial right so that<00:05:13.919> at<00:05:14.160> least<00:05:14.220> macro<00:05:14.940> to<00:05:15.060> assets<00:05:15.300> can<00:05:15.540> be 00:05:15.590 --> 00:05:15.600 align:start position:0% that at least macro to assets can be 00:05:15.600 --> 00:05:16.790 align:start position:0% that at least macro to assets can be retrieved 00:05:16.790 --> 00:05:16.800 align:start position:0% retrieved 00:05:16.800 --> 00:05:19.010 align:start position:0% retrieved sounds<00:05:17.160> impossible<00:05:17.699> right 00:05:19.010 --> 00:05:19.020 align:start position:0% sounds impossible right 00:05:19.020 --> 00:05:21.950 align:start position:0% sounds impossible right okay<00:05:19.500> let's<00:05:20.160> try<00:05:20.400> and<00:05:20.520> solve<00:05:20.639> The<00:05:20.820> Impossible 00:05:21.950 --> 00:05:21.960 align:start position:0% okay let's try and solve The Impossible 00:05:21.960 --> 00:05:23.689 align:start position:0% okay let's try and solve The Impossible time<00:05:22.259> lost<00:05:22.440> secret<00:05:22.680> shares 00:05:23.689 --> 00:05:23.699 align:start position:0% time lost secret shares 00:05:23.699 --> 00:05:26.450 align:start position:0% time lost secret shares so<00:05:24.320> firstly<00:05:25.320> before<00:05:25.560> we<00:05:25.740> get<00:05:25.919> into<00:05:26.039> that<00:05:26.220> right 00:05:26.450 --> 00:05:26.460 align:start position:0% so firstly before we get into that right 00:05:26.460 --> 00:05:29.210 align:start position:0% so firstly before we get into that right what<00:05:27.000> is<00:05:27.180> a<00:05:27.419> Time<00:05:27.539> long 00:05:29.210 --> 00:05:29.220 align:start position:0% what is a Time long 00:05:29.220 --> 00:05:30.950 align:start position:0% what is a Time long um<00:05:29.280> it's<00:05:29.580> basically<00:05:29.880> something<00:05:30.120> that<00:05:30.419> takes<00:05:30.600> a 00:05:30.950 --> 00:05:30.960 align:start position:0% um it's basically something that takes a 00:05:30.960 --> 00:05:33.230 align:start position:0% um it's basically something that takes a long<00:05:31.139> time<00:05:31.440> to<00:05:31.620> decrypt<00:05:32.280> the<00:05:32.880> multiple 00:05:33.230 --> 00:05:33.240 align:start position:0% long time to decrypt the multiple 00:05:33.240 --> 00:05:34.969 align:start position:0% long time to decrypt the multiple variants<00:05:33.660> right<00:05:33.960> if<00:05:34.320> you<00:05:34.440> guys<00:05:34.560> have<00:05:34.800> been 00:05:34.969 --> 00:05:34.979 align:start position:0% variants right if you guys have been 00:05:34.979 --> 00:05:36.590 align:start position:0% variants right if you guys have been following<00:05:35.280> the<00:05:35.520> merch<00:05:36.240> um<00:05:36.240> they<00:05:36.479> use 00:05:36.590 --> 00:05:36.600 align:start position:0% following the merch um they use 00:05:36.600 --> 00:05:39.230 align:start position:0% following the merch um they use verifiable<00:05:37.139> delete<00:05:37.440> functions<00:05:38.160> uh<00:05:38.460> and<00:05:39.060> all 00:05:39.230 --> 00:05:39.240 align:start position:0% verifiable delete functions uh and all 00:05:39.240 --> 00:05:41.090 align:start position:0% verifiable delete functions uh and all that<00:05:39.479> but<00:05:39.900> we<00:05:40.320> are<00:05:40.500> just<00:05:40.620> going<00:05:40.860> to<00:05:40.860> use<00:05:40.979> the 00:05:41.090 --> 00:05:41.100 align:start position:0% that but we are just going to use the 00:05:41.100 --> 00:05:42.529 align:start position:0% that but we are just going to use the most<00:05:41.280> basic<00:05:41.520> one<00:05:41.759> which<00:05:42.000> is<00:05:42.120> repeated 00:05:42.529 --> 00:05:42.539 align:start position:0% most basic one which is repeated 00:05:42.539 --> 00:05:45.529 align:start position:0% most basic one which is repeated squaring<00:05:43.100> and<00:05:44.100> realistically<00:05:44.940> it<00:05:45.300> really 00:05:45.529 --> 00:05:45.539 align:start position:0% squaring and realistically it really 00:05:45.539 --> 00:05:47.210 align:start position:0% squaring and realistically it really doesn't<00:05:45.720> matter<00:05:45.960> what<00:05:46.320> you<00:05:46.500> use<00:05:46.680> just<00:05:46.979> think 00:05:47.210 --> 00:05:47.220 align:start position:0% doesn't matter what you use just think 00:05:47.220 --> 00:05:49.249 align:start position:0% doesn't matter what you use just think it's<00:05:47.820> locked<00:05:48.240> for<00:05:48.360> a<00:05:48.479> long<00:05:48.600> time<00:05:48.780> that's<00:05:49.020> what 00:05:49.249 --> 00:05:49.259 align:start position:0% it's locked for a long time that's what 00:05:49.259 --> 00:05:50.150 align:start position:0% it's locked for a long time that's what matters 00:05:50.150 --> 00:05:50.160 align:start position:0% matters 00:05:50.160 --> 00:05:53.029 align:start position:0% matters right<00:05:50.720> and<00:05:51.720> you<00:05:52.080> know<00:05:52.139> what<00:05:52.259> let's<00:05:52.560> just<00:05:52.860> do 00:05:53.029 --> 00:05:53.039 align:start position:0% right and you know what let's just do 00:05:53.039 --> 00:05:54.350 align:start position:0% right and you know what let's just do this<00:05:53.100> right<00:05:53.280> let's<00:05:53.460> just<00:05:53.699> have<00:05:53.880> an<00:05:54.180> extra 00:05:54.350 --> 00:05:54.360 align:start position:0% this right let's just have an extra 00:05:54.360 --> 00:05:56.390 align:start position:0% this right let's just have an extra share<00:05:54.660> right<00:05:54.840> we<00:05:55.020> have<00:05:55.139> three<00:05:55.320> just<00:05:55.500> now<00:05:55.680> you 00:05:56.390 --> 00:05:56.400 align:start position:0% share right we have three just now you 00:05:56.400 --> 00:05:58.490 align:start position:0% share right we have three just now you require<00:05:56.580> two<00:05:57.060> to<00:05:57.300> redraw<00:05:57.660> the<00:05:57.840> line<00:05:57.960> let's 00:05:58.490 --> 00:05:58.500 align:start position:0% require two to redraw the line let's 00:05:58.500 --> 00:06:00.290 align:start position:0% require two to redraw the line let's just<00:05:58.680> have<00:05:58.860> one<00:05:59.039> more<00:05:59.220> right<00:05:59.520> one<00:05:59.940> more<00:06:00.060> this 00:06:00.290 --> 00:06:00.300 align:start position:0% just have one more right one more this 00:06:00.300 --> 00:06:01.670 align:start position:0% just have one more right one more this time<00:06:00.479> log 00:06:01.670 --> 00:06:01.680 align:start position:0% time log 00:06:01.680 --> 00:06:04.550 align:start position:0% time log and<00:06:02.340> let's<00:06:02.639> say<00:06:02.820> your<00:06:03.120> house<00:06:03.360> caught<00:06:03.600> fire<00:06:03.900> you 00:06:04.550 --> 00:06:04.560 align:start position:0% and let's say your house caught fire you 00:06:04.560 --> 00:06:05.990 align:start position:0% and let's say your house caught fire you know<00:06:04.680> and<00:06:04.860> you've<00:06:05.100> lost<00:06:05.220> both<00:06:05.520> your<00:06:05.699> laptop 00:06:05.990 --> 00:06:06.000 align:start position:0% know and you've lost both your laptop 00:06:06.000 --> 00:06:08.090 align:start position:0% know and you've lost both your laptop and<00:06:06.180> your<00:06:06.360> phone<00:06:06.479> so<00:06:06.600> you<00:06:06.780> lost<00:06:06.900> two<00:06:07.139> factors 00:06:08.090 --> 00:06:08.100 align:start position:0% and your phone so you lost two factors 00:06:08.100 --> 00:06:11.090 align:start position:0% and your phone so you lost two factors uh<00:06:08.520> they're<00:06:08.699> now<00:06:08.880> Ash<00:06:09.180> and<00:06:10.139> but<00:06:10.380> luckily<00:06:10.919> right 00:06:11.090 --> 00:06:11.100 align:start position:0% uh they're now Ash and but luckily right 00:06:11.100 --> 00:06:12.770 align:start position:0% uh they're now Ash and but luckily right you've<00:06:11.400> prepared<00:06:11.699> ahead<00:06:12.000> of<00:06:12.120> time<00:06:12.240> you 00:06:12.770 --> 00:06:12.780 align:start position:0% you've prepared ahead of time you 00:06:12.780 --> 00:06:14.510 align:start position:0% you've prepared ahead of time you generated<00:06:13.199> a<00:06:13.440> four<00:06:13.560> share<00:06:13.860> the<00:06:13.979> time<00:06:14.160> lock<00:06:14.280> for 00:06:14.510 --> 00:06:14.520 align:start position:0% generated a four share the time lock for 00:06:14.520 --> 00:06:15.529 align:start position:0% generated a four share the time lock for like<00:06:14.639> one<00:06:14.820> month 00:06:15.529 --> 00:06:15.539 align:start position:0% like one month 00:06:15.539 --> 00:06:17.810 align:start position:0% like one month and<00:06:16.259> you<00:06:16.500> put<00:06:16.680> it<00:06:16.800> somewhere<00:06:17.100> other<00:06:17.340> than<00:06:17.520> your 00:06:17.810 --> 00:06:17.820 align:start position:0% and you put it somewhere other than your 00:06:17.820 --> 00:06:19.790 align:start position:0% and you put it somewhere other than your house<00:06:18.000> so<00:06:18.300> it<00:06:18.419> didn't<00:06:18.539> catch<00:06:18.840> on<00:06:18.900> fire<00:06:19.139> you<00:06:19.620> put 00:06:19.790 --> 00:06:19.800 align:start position:0% house so it didn't catch on fire you put 00:06:19.800 --> 00:06:21.350 align:start position:0% house so it didn't catch on fire you put it<00:06:19.919> in<00:06:20.039> public 00:06:21.350 --> 00:06:21.360 align:start position:0% it in public 00:06:21.360 --> 00:06:25.249 align:start position:0% it in public um<00:06:21.479> in<00:06:22.380> a<00:06:22.560> month's<00:06:22.860> time<00:06:22.979> it<00:06:23.280> unlocks<00:06:23.819> and<00:06:24.660> with 00:06:25.249 --> 00:06:25.259 align:start position:0% um in a month's time it unlocks and with 00:06:25.259 --> 00:06:26.749 align:start position:0% um in a month's time it unlocks and with your<00:06:25.500> other<00:06:25.680> share<00:06:26.100> which<00:06:26.220> is<00:06:26.400> like<00:06:26.520> an<00:06:26.639> email 00:06:26.749 --> 00:06:26.759 align:start position:0% your other share which is like an email 00:06:26.759 --> 00:06:30.529 align:start position:0% your other share which is like an email share<00:06:27.180> you<00:06:27.900> can<00:06:28.020> get<00:06:28.199> back<00:06:28.380> your<00:06:28.620> key<00:06:28.860> perfect 00:06:30.529 --> 00:06:30.539 align:start position:0% share you can get back your key perfect 00:06:30.539 --> 00:06:33.350 align:start position:0% share you can get back your key perfect not<00:06:31.080> really<00:06:31.500> that<00:06:31.740> doesn't<00:06:31.919> work<00:06:32.160> so<00:06:32.580> let's 00:06:33.350 --> 00:06:33.360 align:start position:0% not really that doesn't work so let's 00:06:33.360 --> 00:06:36.050 align:start position:0% not really that doesn't work so let's see<00:06:33.539> why<00:06:33.780> right<00:06:34.199> the<00:06:34.979> problem<00:06:35.100> is<00:06:35.520> that<00:06:35.759> now 00:06:36.050 --> 00:06:36.060 align:start position:0% see why right the problem is that now 00:06:36.060 --> 00:06:38.570 align:start position:0% see why right the problem is that now you're<00:06:36.539> just<00:06:36.720> one<00:06:37.319> compromise<00:06:37.919> Factor<00:06:38.340> away 00:06:38.570 --> 00:06:38.580 align:start position:0% you're just one compromise Factor away 00:06:38.580 --> 00:06:39.830 align:start position:0% you're just one compromise Factor away from<00:06:38.759> losing<00:06:39.060> a<00:06:39.180> key 00:06:39.830 --> 00:06:39.840 align:start position:0% from losing a key 00:06:39.840 --> 00:06:42.650 align:start position:0% from losing a key so<00:06:40.319> let's<00:06:40.740> say<00:06:40.919> it<00:06:41.100> as<00:06:41.280> a<00:06:41.460> patient<00:06:41.819> attacker 00:06:42.650 --> 00:06:42.660 align:start position:0% so let's say it as a patient attacker 00:06:42.660 --> 00:06:44.809 align:start position:0% so let's say it as a patient attacker adversary<00:06:43.440> just<00:06:43.919> waiting<00:06:44.340> right<00:06:44.520> he<00:06:44.699> just 00:06:44.809 --> 00:06:44.819 align:start position:0% adversary just waiting right he just 00:06:44.819 --> 00:06:46.909 align:start position:0% adversary just waiting right he just Waits<00:06:45.180> a<00:06:45.300> month<00:06:45.419> well<00:06:46.080> your<00:06:46.380> time<00:06:46.500> of<00:06:46.740> share 00:06:46.909 --> 00:06:46.919 align:start position:0% Waits a month well your time of share 00:06:46.919 --> 00:06:48.890 align:start position:0% Waits a month well your time of share will<00:06:47.100> eventually<00:06:47.340> unlock<00:06:47.580> right<00:06:48.000> after<00:06:48.600> a 00:06:48.890 --> 00:06:48.900 align:start position:0% will eventually unlock right after a 00:06:48.900 --> 00:06:50.990 align:start position:0% will eventually unlock right after a month<00:06:49.020> and<00:06:49.860> remember<00:06:50.100> it's<00:06:50.520> in<00:06:50.699> the<00:06:50.880> public 00:06:50.990 --> 00:06:51.000 align:start position:0% month and remember it's in the public 00:06:51.000 --> 00:06:52.309 align:start position:0% month and remember it's in the public domain<00:06:51.419> because<00:06:51.600> it's<00:06:51.840> not<00:06:51.960> your<00:06:52.139> house 00:06:52.309 --> 00:06:52.319 align:start position:0% domain because it's not your house 00:06:52.319 --> 00:06:54.770 align:start position:0% domain because it's not your house someone<00:06:52.680> could<00:06:52.919> access<00:06:53.280> it 00:06:54.770 --> 00:06:54.780 align:start position:0% someone could access it 00:06:54.780 --> 00:06:56.689 align:start position:0% someone could access it and<00:06:55.139> then<00:06:55.319> they<00:06:55.680> just<00:06:55.860> need<00:06:55.979> to<00:06:56.100> steal<00:06:56.280> any<00:06:56.520> one 00:06:56.689 --> 00:06:56.699 align:start position:0% and then they just need to steal any one 00:06:56.699 --> 00:06:58.309 align:start position:0% and then they just need to steal any one of<00:06:56.819> the<00:06:56.940> factors<00:06:57.300> right<00:06:57.479> to<00:06:57.660> get<00:06:57.840> a<00:06:57.960> key<00:06:58.080> so 00:06:58.309 --> 00:06:58.319 align:start position:0% of the factors right to get a key so 00:06:58.319 --> 00:07:01.430 align:start position:0% of the factors right to get a key so basically<00:06:58.740> you<00:06:59.100> go<00:06:59.460> for<00:06:59.639> 2fa<00:07:00.240> to<00:07:00.479> really<00:07:01.020> one 00:07:01.430 --> 00:07:01.440 align:start position:0% basically you go for 2fa to really one 00:07:01.440 --> 00:07:04.790 align:start position:0% basically you go for 2fa to really one fa<00:07:01.919> so<00:07:02.759> that's<00:07:03.240> no<00:07:03.479> good 00:07:04.790 --> 00:07:04.800 align:start position:0% fa so that's no good 00:07:04.800 --> 00:07:07.610 align:start position:0% fa so that's no good solution<00:07:05.340> two<00:07:05.600> let's<00:07:06.600> improve<00:07:07.080> that<00:07:07.199> right 00:07:07.610 --> 00:07:07.620 align:start position:0% solution two let's improve that right 00:07:07.620 --> 00:07:09.830 align:start position:0% solution two let's improve that right let's<00:07:08.340> do<00:07:08.580> time<00:07:08.759> log<00:07:09.000> shares<00:07:09.419> with<00:07:09.660> key 00:07:09.830 --> 00:07:09.840 align:start position:0% let's do time log shares with key 00:07:09.840 --> 00:07:11.090 align:start position:0% let's do time log shares with key refresh 00:07:11.090 --> 00:07:11.100 align:start position:0% refresh 00:07:11.100 --> 00:07:13.430 align:start position:0% refresh so<00:07:11.699> once<00:07:12.060> again<00:07:12.120> new<00:07:12.479> content<00:07:12.840> right<00:07:13.020> what<00:07:13.259> is 00:07:13.430 --> 00:07:13.440 align:start position:0% so once again new content right what is 00:07:13.440 --> 00:07:14.990 align:start position:0% so once again new content right what is key<00:07:13.560> refresh 00:07:14.990 --> 00:07:15.000 align:start position:0% key refresh 00:07:15.000 --> 00:07:17.029 align:start position:0% key refresh um for<00:07:15.479> those<00:07:15.600> who<00:07:15.840> don't<00:07:16.020> know<00:07:16.259> basically<00:07:16.860> a 00:07:17.029 --> 00:07:17.039 align:start position:0% um for those who don't know basically a 00:07:17.039 --> 00:07:19.309 align:start position:0% um for those who don't know basically a key<00:07:17.220> refresh<00:07:17.580> is<00:07:17.759> a<00:07:18.000> way<00:07:18.120> to<00:07:18.720> refresh<00:07:19.139> the 00:07:19.309 --> 00:07:19.319 align:start position:0% key refresh is a way to refresh the 00:07:19.319 --> 00:07:21.890 align:start position:0% key refresh is a way to refresh the shares<00:07:19.680> of<00:07:19.919> a<00:07:20.039> SQL<00:07:20.340> share<00:07:20.580> secret<00:07:21.360> sharing 00:07:21.890 --> 00:07:21.900 align:start position:0% shares of a SQL share secret sharing 00:07:21.900 --> 00:07:23.990 align:start position:0% shares of a SQL share secret sharing while<00:07:22.620> keeping<00:07:23.039> the<00:07:23.220> private<00:07:23.520> key<00:07:23.639> the<00:07:23.880> same 00:07:23.990 --> 00:07:24.000 align:start position:0% while keeping the private key the same 00:07:24.000 --> 00:07:26.089 align:start position:0% while keeping the private key the same the<00:07:24.180> private<00:07:24.479> key<00:07:24.599> here<00:07:24.840> is<00:07:25.199> the<00:07:25.440> star<00:07:25.680> right 00:07:26.089 --> 00:07:26.099 align:start position:0% the private key here is the star right 00:07:26.099 --> 00:07:28.129 align:start position:0% the private key here is the star right it's<00:07:26.699> the<00:07:26.819> star<00:07:27.000> so<00:07:27.240> there's<00:07:27.360> a<00:07:27.479> private<00:07:27.720> qcm 00:07:28.129 --> 00:07:28.139 align:start position:0% it's the star so there's a private qcm 00:07:28.139 --> 00:07:30.770 align:start position:0% it's the star so there's a private qcm and<00:07:28.440> the<00:07:28.560> way<00:07:28.680> we<00:07:28.800> do<00:07:28.979> it<00:07:29.160> is<00:07:29.400> kind<00:07:29.759> of<00:07:29.880> you<00:07:30.599> just 00:07:30.770 --> 00:07:30.780 align:start position:0% and the way we do it is kind of you just 00:07:30.780 --> 00:07:32.510 align:start position:0% and the way we do it is kind of you just draw<00:07:31.020> another<00:07:31.259> line<00:07:31.620> that<00:07:31.919> goes<00:07:32.220> through<00:07:32.280> the 00:07:32.510 --> 00:07:32.520 align:start position:0% draw another line that goes through the 00:07:32.520 --> 00:07:34.309 align:start position:0% draw another line that goes through the same<00:07:32.639> point<00:07:32.880> the<00:07:33.240> same<00:07:33.360> y-intercept<00:07:33.960> which<00:07:34.199> is 00:07:34.309 --> 00:07:34.319 align:start position:0% same point the same y-intercept which is 00:07:34.319 --> 00:07:36.950 align:start position:0% same point the same y-intercept which is a<00:07:34.560> key<00:07:34.680> and<00:07:35.580> then<00:07:35.699> you<00:07:36.120> get<00:07:36.300> rid<00:07:36.479> of<00:07:36.660> the<00:07:36.840> old 00:07:36.950 --> 00:07:36.960 align:start position:0% a key and then you get rid of the old 00:07:36.960 --> 00:07:39.050 align:start position:0% a key and then you get rid of the old shares<00:07:37.319> basically<00:07:37.919> all<00:07:38.520> the<00:07:38.699> shares<00:07:38.940> are 00:07:39.050 --> 00:07:39.060 align:start position:0% shares basically all the shares are 00:07:39.060 --> 00:07:39.710 align:start position:0% shares basically all the shares are different 00:07:39.710 --> 00:07:39.720 align:start position:0% different 00:07:39.720 --> 00:07:41.749 align:start position:0% different but<00:07:40.380> your<00:07:40.680> key<00:07:40.860> is<00:07:40.979> the<00:07:41.099> same 00:07:41.749 --> 00:07:41.759 align:start position:0% but your key is the same 00:07:41.759 --> 00:07:44.749 align:start position:0% but your key is the same and<00:07:42.660> the<00:07:42.960> point<00:07:43.139> here<00:07:43.440> is<00:07:43.800> that<00:07:43.979> as<00:07:44.280> long<00:07:44.460> as 00:07:44.749 --> 00:07:44.759 align:start position:0% and the point here is that as long as 00:07:44.759 --> 00:07:47.210 align:start position:0% and the point here is that as long as you<00:07:45.180> don't<00:07:45.300> lose<00:07:45.539> two<00:07:45.900> factors<00:07:46.380> on<00:07:46.979> the<00:07:47.099> same 00:07:47.210 --> 00:07:47.220 align:start position:0% you don't lose two factors on the same 00:07:47.220 --> 00:07:48.890 align:start position:0% you don't lose two factors on the same line<00:07:47.460> right<00:07:47.940> you<00:07:48.120> don't<00:07:48.240> lose<00:07:48.360> two<00:07:48.539> factors 00:07:48.890 --> 00:07:48.900 align:start position:0% line right you don't lose two factors 00:07:48.900 --> 00:07:50.809 align:start position:0% line right you don't lose two factors before<00:07:49.139> you<00:07:49.380> did<00:07:49.500> a<00:07:49.620> q<00:07:49.740> refresh<00:07:50.099> your<00:07:50.460> key<00:07:50.699> is 00:07:50.809 --> 00:07:50.819 align:start position:0% before you did a q refresh your key is 00:07:50.819 --> 00:07:52.249 align:start position:0% before you did a q refresh your key is safe<00:07:51.000> right<00:07:51.240> because<00:07:51.419> even<00:07:51.900> if<00:07:52.139> they 00:07:52.249 --> 00:07:52.259 align:start position:0% safe right because even if they 00:07:52.259 --> 00:07:53.689 align:start position:0% safe right because even if they compromise<00:07:52.740> these<00:07:53.099> factors<00:07:53.400> they<00:07:53.639> can't 00:07:53.689 --> 00:07:53.699 align:start position:0% compromise these factors they can't 00:07:53.699 --> 00:07:55.909 align:start position:0% compromise these factors they can't redraw<00:07:54.120> the<00:07:54.240> line<00:07:54.360> impossible<00:07:55.139> and<00:07:55.680> the<00:07:55.800> two 00:07:55.909 --> 00:07:55.919 align:start position:0% redraw the line impossible and the two 00:07:55.919 --> 00:07:58.370 align:start position:0% redraw the line impossible and the two lines<00:07:56.340> are<00:07:56.460> completely<00:07:56.819> unrelated<00:07:57.360> so<00:07:58.259> that's 00:07:58.370 --> 00:07:58.380 align:start position:0% lines are completely unrelated so that's 00:07:58.380 --> 00:07:59.930 align:start position:0% lines are completely unrelated so that's what<00:07:58.560> key<00:07:58.800> refresh<00:07:59.160> does 00:07:59.930 --> 00:07:59.940 align:start position:0% what key refresh does 00:07:59.940 --> 00:08:01.129 align:start position:0% what key refresh does um<00:08:00.000> there<00:08:00.240> are<00:08:00.360> a<00:08:00.419> lot<00:08:00.419> of<00:08:00.539> protocols<00:08:00.900> that<00:08:00.960> do 00:08:01.129 --> 00:08:01.139 align:start position:0% um there are a lot of protocols that do 00:08:01.139 --> 00:08:02.089 align:start position:0% um there are a lot of protocols that do that<00:08:01.259> today 00:08:02.089 --> 00:08:02.099 align:start position:0% that today 00:08:02.099 --> 00:08:04.309 align:start position:0% that today but<00:08:02.639> please<00:08:02.819> don't<00:08:03.180> do<00:08:03.599> it<00:08:03.720> like<00:08:03.840> this<00:08:03.960> there's 00:08:04.309 --> 00:08:04.319 align:start position:0% but please don't do it like this there's 00:08:04.319 --> 00:08:05.689 align:start position:0% but please don't do it like this there's a<00:08:04.500> lot<00:08:04.620> of<00:08:04.680> other<00:08:04.800> stuff<00:08:04.979> you<00:08:05.160> can<00:08:05.280> do<00:08:05.400> please 00:08:05.689 --> 00:08:05.699 align:start position:0% a lot of other stuff you can do please 00:08:05.699 --> 00:08:07.909 align:start position:0% a lot of other stuff you can do please don't<00:08:05.940> do<00:08:06.000> that<00:08:06.180> in<00:08:06.360> production 00:08:07.909 --> 00:08:07.919 align:start position:0% don't do that in production 00:08:07.919 --> 00:08:10.189 align:start position:0% don't do that in production so<00:08:08.639> now<00:08:09.120> we<00:08:09.360> have<00:08:09.479> some<00:08:09.599> idea<00:08:09.840> what<00:08:10.020> key 00:08:10.189 --> 00:08:10.199 align:start position:0% so now we have some idea what key 00:08:10.199 --> 00:08:11.930 align:start position:0% so now we have some idea what key refresh<00:08:10.560> does<00:08:10.740> what<00:08:11.160> if<00:08:11.340> we<00:08:11.580> just<00:08:11.759> keep 00:08:11.930 --> 00:08:11.940 align:start position:0% refresh does what if we just keep 00:08:11.940 --> 00:08:14.029 align:start position:0% refresh does what if we just keep refresh<00:08:12.240> before<00:08:12.419> the<00:08:12.599> time<00:08:12.720> locks<00:08:13.080> up<00:08:13.620> right 00:08:14.029 --> 00:08:14.039 align:start position:0% refresh before the time locks up right 00:08:14.039 --> 00:08:16.249 align:start position:0% refresh before the time locks up right so<00:08:14.280> we<00:08:14.400> do<00:08:14.580> a<00:08:14.699> key<00:08:14.759> refresh<00:08:15.240> whenever<00:08:16.080> you<00:08:16.199> use 00:08:16.249 --> 00:08:16.259 align:start position:0% so we do a key refresh whenever you use 00:08:16.259 --> 00:08:18.469 align:start position:0% so we do a key refresh whenever you use a<00:08:16.440> wallet<00:08:16.740> maybe<00:08:17.160> once<00:08:17.580> a<00:08:17.699> week<00:08:17.819> the<00:08:18.060> time<00:08:18.180> loss 00:08:18.469 --> 00:08:18.479 align:start position:0% a wallet maybe once a week the time loss 00:08:18.479 --> 00:08:20.089 align:start position:0% a wallet maybe once a week the time loss one<00:08:18.660> is<00:08:18.960> like<00:08:19.080> a<00:08:19.199> month<00:08:19.319> right<00:08:19.500> so<00:08:19.740> as<00:08:19.860> long<00:08:20.039> as 00:08:20.089 --> 00:08:20.099 align:start position:0% one is like a month right so as long as 00:08:20.099 --> 00:08:21.950 align:start position:0% one is like a month right so as long as you<00:08:20.160> use<00:08:20.280> it<00:08:20.400> once<00:08:20.580> a<00:08:20.639> week<00:08:20.759> you're<00:08:20.940> fine<00:08:21.180> so 00:08:21.950 --> 00:08:21.960 align:start position:0% you use it once a week you're fine so 00:08:21.960 --> 00:08:24.170 align:start position:0% you use it once a week you're fine so when<00:08:22.199> you<00:08:22.319> use<00:08:22.500> it<00:08:22.680> you<00:08:23.160> do<00:08:23.340> a<00:08:23.460> key<00:08:23.520> refresh<00:08:24.000> you 00:08:24.170 --> 00:08:24.180 align:start position:0% when you use it you do a key refresh you 00:08:24.180 --> 00:08:26.270 align:start position:0% when you use it you do a key refresh you give<00:08:24.360> out<00:08:24.599> the<00:08:24.780> shares 00:08:26.270 --> 00:08:26.280 align:start position:0% give out the shares 00:08:26.280 --> 00:08:29.150 align:start position:0% give out the shares even<00:08:26.759> when<00:08:27.240> the<00:08:28.080> time<00:08:28.199> lock<00:08:28.379> share<00:08:28.680> unlocks 00:08:29.150 --> 00:08:29.160 align:start position:0% even when the time lock share unlocks 00:08:29.160 --> 00:08:30.890 align:start position:0% even when the time lock share unlocks right<00:08:29.460> the<00:08:29.819> attacker<00:08:30.240> can't<00:08:30.479> get<00:08:30.660> anything 00:08:30.890 --> 00:08:30.900 align:start position:0% right the attacker can't get anything 00:08:30.900 --> 00:08:33.529 align:start position:0% right the attacker can't get anything even<00:08:31.319> if<00:08:31.500> it<00:08:31.680> steals<00:08:32.159> another<00:08:32.520> Factor<00:08:33.060> right 00:08:33.529 --> 00:08:33.539 align:start position:0% even if it steals another Factor right 00:08:33.539 --> 00:08:36.170 align:start position:0% even if it steals another Factor right because<00:08:33.719> he<00:08:33.959> can't<00:08:34.140> get<00:08:34.440> back<00:08:35.099> um<00:08:35.099> the<00:08:35.459> line 00:08:36.170 --> 00:08:36.180 align:start position:0% because he can't get back um the line 00:08:36.180 --> 00:08:37.850 align:start position:0% because he can't get back um the line so<00:08:36.479> you<00:08:36.539> can't<00:08:36.659> get<00:08:36.779> back<00:08:36.959> the<00:08:37.080> same<00:08:37.200> line<00:08:37.380> so 00:08:37.850 --> 00:08:37.860 align:start position:0% so you can't get back the same line so 00:08:37.860 --> 00:08:40.790 align:start position:0% so you can't get back the same line so it<00:08:38.159> seems<00:08:38.399> like<00:08:38.520> a<00:08:38.640> safe<00:08:38.820> right<00:08:39.899> and<00:08:40.500> this 00:08:40.790 --> 00:08:40.800 align:start position:0% it seems like a safe right and this 00:08:40.800 --> 00:08:43.310 align:start position:0% it seems like a safe right and this seems<00:08:41.219> to<00:08:41.339> work<00:08:41.580> right<00:08:42.000> the<00:08:42.599> setup<00:08:42.899> seems<00:08:43.260> to 00:08:43.310 --> 00:08:43.320 align:start position:0% seems to work right the setup seems to 00:08:43.320 --> 00:08:45.170 align:start position:0% seems to work right the setup seems to have<00:08:43.380> a<00:08:43.500> lot<00:08:43.560> of<00:08:43.680> properties<00:08:43.979> that<00:08:44.339> we<00:08:44.459> want 00:08:45.170 --> 00:08:45.180 align:start position:0% have a lot of properties that we want 00:08:45.180 --> 00:08:47.570 align:start position:0% have a lot of properties that we want during<00:08:45.660> normal<00:08:45.959> operation<00:08:46.500> attacker<00:08:47.399> can 00:08:47.570 --> 00:08:47.580 align:start position:0% during normal operation attacker can 00:08:47.580 --> 00:08:49.610 align:start position:0% during normal operation attacker can solve<00:08:47.880> the<00:08:48.000> time<00:08:48.180> log<00:08:48.360> but<00:08:48.959> I<00:08:49.140> cannot<00:08:49.380> use<00:08:49.440> the 00:08:49.610 --> 00:08:49.620 align:start position:0% solve the time log but I cannot use the 00:08:49.620 --> 00:08:50.930 align:start position:0% solve the time log but I cannot use the other<00:08:49.800> shares<00:08:50.160> since<00:08:50.339> key<00:08:50.519> refreshes 00:08:50.930 --> 00:08:50.940 align:start position:0% other shares since key refreshes 00:08:50.940 --> 00:08:51.949 align:start position:0% other shares since key refreshes occurred<00:08:51.240> it's<00:08:51.360> on<00:08:51.480> a<00:08:51.600> different<00:08:51.720> line 00:08:51.949 --> 00:08:51.959 align:start position:0% occurred it's on a different line 00:08:51.959 --> 00:08:54.170 align:start position:0% occurred it's on a different line there's<00:08:52.920> an<00:08:53.100> interesting<00:08:53.279> property<00:08:53.700> here<00:08:53.940> so 00:08:54.170 --> 00:08:54.180 align:start position:0% there's an interesting property here so 00:08:54.180 --> 00:08:56.210 align:start position:0% there's an interesting property here so if<00:08:54.420> you<00:08:54.540> guys<00:08:54.720> have<00:08:55.200> been<00:08:55.380> following<00:08:55.680> time 00:08:56.210 --> 00:08:56.220 align:start position:0% if you guys have been following time 00:08:56.220 --> 00:08:58.310 align:start position:0% if you guys have been following time timeline<00:08:57.060> research<00:08:57.420> and<00:08:57.660> like<00:08:57.839> verifiable 00:08:58.310 --> 00:08:58.320 align:start position:0% timeline research and like verifiable 00:08:58.320 --> 00:09:00.050 align:start position:0% timeline research and like verifiable delay<00:08:58.740> encryption 00:09:00.050 --> 00:09:00.060 align:start position:0% delay encryption 00:09:00.060 --> 00:09:01.850 align:start position:0% delay encryption um you'll<00:09:00.420> know<00:09:00.600> that<00:09:00.839> there<00:09:01.440> are<00:09:01.620> some 00:09:01.850 --> 00:09:01.860 align:start position:0% um you'll know that there are some 00:09:01.860 --> 00:09:03.110 align:start position:0% um you'll know that there are some research<00:09:02.279> being<00:09:02.519> done<00:09:02.760> there's<00:09:03.000> some 00:09:03.110 --> 00:09:03.120 align:start position:0% research being done there's some 00:09:03.120 --> 00:09:05.030 align:start position:0% research being done there's some research<00:09:03.420> being<00:09:03.540> done<00:09:03.779> on<00:09:04.080> homorphic<00:09:04.680> Tunnel 00:09:05.030 --> 00:09:05.040 align:start position:0% research being done on homorphic Tunnel 00:09:05.040 --> 00:09:06.530 align:start position:0% research being done on homorphic Tunnel puzzles<00:09:05.339> and<00:09:05.519> all<00:09:05.700> that 00:09:06.530 --> 00:09:06.540 align:start position:0% puzzles and all that 00:09:06.540 --> 00:09:08.930 align:start position:0% puzzles and all that um because<00:09:06.779> it<00:09:07.200> makes<00:09:07.380> it<00:09:07.560> cheaper<00:09:07.980> but<00:09:08.640> in 00:09:08.930 --> 00:09:08.940 align:start position:0% um because it makes it cheaper but in 00:09:08.940 --> 00:09:10.670 align:start position:0% um because it makes it cheaper but in our<00:09:09.060> case<00:09:09.300> actually<00:09:09.540> it's<00:09:09.899> good<00:09:10.200> that<00:09:10.500> it's 00:09:10.670 --> 00:09:10.680 align:start position:0% our case actually it's good that it's 00:09:10.680 --> 00:09:12.590 align:start position:0% our case actually it's good that it's expensive<00:09:11.040> it's<00:09:11.220> a<00:09:11.399> feature<00:09:11.700> we<00:09:12.120> want<00:09:12.300> it<00:09:12.480> to 00:09:12.590 --> 00:09:12.600 align:start position:0% expensive it's a feature we want it to 00:09:12.600 --> 00:09:14.090 align:start position:0% expensive it's a feature we want it to be<00:09:12.660> expensive<00:09:13.080> because<00:09:13.440> we<00:09:13.800> don't<00:09:13.920> want 00:09:14.090 --> 00:09:14.100 align:start position:0% be expensive because we don't want 00:09:14.100 --> 00:09:16.130 align:start position:0% be expensive because we don't want attackers<00:09:14.519> to<00:09:14.820> be<00:09:14.940> getting<00:09:15.600> through<00:09:15.959> the 00:09:16.130 --> 00:09:16.140 align:start position:0% attackers to be getting through the 00:09:16.140 --> 00:09:17.930 align:start position:0% attackers to be getting through the timelock<00:09:16.500> easily<00:09:16.920> or<00:09:17.160> even<00:09:17.339> people<00:09:17.580> do<00:09:17.820> it 00:09:17.930 --> 00:09:17.940 align:start position:0% timelock easily or even people do it 00:09:17.940 --> 00:09:20.030 align:start position:0% timelock easily or even people do it parallely<00:09:18.360> and<00:09:19.019> in<00:09:19.200> the<00:09:19.320> case<00:09:19.440> when<00:09:19.680> you<00:09:19.860> lose 00:09:20.030 --> 00:09:20.040 align:start position:0% parallely and in the case when you lose 00:09:20.040 --> 00:09:22.070 align:start position:0% parallely and in the case when you lose your<00:09:20.339> key<00:09:20.519> you<00:09:21.120> won't<00:09:21.300> mind<00:09:21.480> doing<00:09:21.779> the<00:09:21.959> work 00:09:22.070 --> 00:09:22.080 align:start position:0% your key you won't mind doing the work 00:09:22.080 --> 00:09:23.870 align:start position:0% your key you won't mind doing the work so<00:09:22.380> it<00:09:22.500> doesn't<00:09:22.620> matter<00:09:22.800> the<00:09:23.100> expense<00:09:23.459> is<00:09:23.640> not 00:09:23.870 --> 00:09:23.880 align:start position:0% so it doesn't matter the expense is not 00:09:23.880 --> 00:09:25.670 align:start position:0% so it doesn't matter the expense is not wfdo 00:09:25.670 --> 00:09:25.680 align:start position:0% wfdo 00:09:25.680 --> 00:09:27.110 align:start position:0% wfdo um<00:09:25.740> so<00:09:26.100> during<00:09:26.220> normal<00:09:26.459> operation<00:09:26.820> you're 00:09:27.110 --> 00:09:27.120 align:start position:0% um so during normal operation you're 00:09:27.120 --> 00:09:27.949 align:start position:0% um so during normal operation you're fine 00:09:27.949 --> 00:09:27.959 align:start position:0% fine 00:09:27.959 --> 00:09:30.050 align:start position:0% fine but<00:09:28.620> if<00:09:28.860> you're<00:09:28.980> a<00:09:29.100> catastrophic<00:09:29.640> loss<00:09:29.940> right 00:09:30.050 --> 00:09:30.060 align:start position:0% but if you're a catastrophic loss right 00:09:30.060 --> 00:09:32.870 align:start position:0% but if you're a catastrophic loss right you<00:09:30.300> lose<00:09:30.480> all<00:09:30.899> your<00:09:31.080> user<00:09:31.380> factors<00:09:31.680> you<00:09:32.040> I 00:09:32.870 --> 00:09:32.880 align:start position:0% you lose all your user factors you I 00:09:32.880 --> 00:09:34.490 align:start position:0% you lose all your user factors you I don't<00:09:33.000> know<00:09:33.120> somehow<00:09:33.720> lose<00:09:33.959> all<00:09:34.140> your<00:09:34.260> user 00:09:34.490 --> 00:09:34.500 align:start position:0% don't know somehow lose all your user 00:09:34.500 --> 00:09:36.410 align:start position:0% don't know somehow lose all your user factors<00:09:34.800> then<00:09:35.100> if<00:09:35.580> the<00:09:35.760> time<00:09:35.820> loss<00:09:36.180> share<00:09:36.300> is 00:09:36.410 --> 00:09:36.420 align:start position:0% factors then if the time loss share is 00:09:36.420 --> 00:09:38.690 align:start position:0% factors then if the time loss share is reviewed<00:09:36.839> and 00:09:38.690 --> 00:09:38.700 align:start position:0% reviewed and 00:09:38.700 --> 00:09:40.250 align:start position:0% reviewed and um share<00:09:39.000> refresh<00:09:39.420> won't<00:09:39.600> happen<00:09:39.899> right 00:09:40.250 --> 00:09:40.260 align:start position:0% um share refresh won't happen right 00:09:40.260 --> 00:09:41.630 align:start position:0% um share refresh won't happen right because<00:09:40.440> you<00:09:40.680> didn't<00:09:40.800> have<00:09:41.040> your<00:09:41.220> shares<00:09:41.519> so 00:09:41.630 --> 00:09:41.640 align:start position:0% because you didn't have your shares so 00:09:41.640 --> 00:09:44.210 align:start position:0% because you didn't have your shares so you<00:09:41.760> can't<00:09:41.880> share<00:09:42.180> refresh<00:09:42.600> then<00:09:43.560> you<00:09:43.920> can<00:09:44.040> use 00:09:44.210 --> 00:09:44.220 align:start position:0% you can't share refresh then you can use 00:09:44.220 --> 00:09:46.130 align:start position:0% you can't share refresh then you can use the<00:09:44.459> custodial<00:09:44.940> share<00:09:45.240> with<00:09:45.360> the<00:09:45.480> email<00:09:45.660> share 00:09:46.130 --> 00:09:46.140 align:start position:0% the custodial share with the email share 00:09:46.140 --> 00:09:47.990 align:start position:0% the custodial share with the email share and<00:09:46.680> the<00:09:46.800> timelock<00:09:47.160> share<00:09:47.339> to<00:09:47.580> reconstruct 00:09:47.990 --> 00:09:48.000 align:start position:0% and the timelock share to reconstruct 00:09:48.000 --> 00:09:49.970 align:start position:0% and the timelock share to reconstruct the<00:09:48.180> key<00:09:48.360> so<00:09:48.959> it's<00:09:49.200> kind<00:09:49.320> of<00:09:49.440> like<00:09:49.500> a<00:09:49.620> Deadman 00:09:49.970 --> 00:09:49.980 align:start position:0% the key so it's kind of like a Deadman 00:09:49.980 --> 00:09:52.970 align:start position:0% the key so it's kind of like a Deadman switch<00:09:50.279> of<00:09:51.180> a<00:09:51.360> smart<00:09:51.540> contract<00:09:51.899> wallet<00:09:52.260> except 00:09:52.970 --> 00:09:52.980 align:start position:0% switch of a smart contract wallet except 00:09:52.980 --> 00:09:55.550 align:start position:0% switch of a smart contract wallet except it's<00:09:53.220> done<00:09:53.459> in<00:09:53.640> NPC<00:09:54.600> so<00:09:55.019> we've<00:09:55.200> created<00:09:55.380> a 00:09:55.550 --> 00:09:55.560 align:start position:0% it's done in NPC so we've created a 00:09:55.560 --> 00:09:57.170 align:start position:0% it's done in NPC so we've created a non-custorial<00:09:56.160> setup<00:09:56.459> that<00:09:56.580> degrades<00:09:57.000> in<00:09:57.120> the 00:09:57.170 --> 00:09:57.180 align:start position:0% non-custorial setup that degrades in the 00:09:57.180 --> 00:09:59.329 align:start position:0% non-custorial setup that degrades in the custodial<00:09:57.600> setup<00:09:57.899> on<00:09:58.080> loss 00:09:59.329 --> 00:09:59.339 align:start position:0% custodial setup on loss 00:09:59.339 --> 00:10:01.550 align:start position:0% custodial setup on loss but<00:09:59.820> that's<00:10:00.000> it<00:10:00.180> thank<00:10:00.540> you 00:10:01.550 --> 00:10:01.560 align:start position:0% but that's it thank you 00:10:01.560 --> 00:10:03.310 align:start position:0% but that's it thank you no<00:10:02.160> I'm<00:10:02.399> kidding 00:10:03.310 --> 00:10:03.320 align:start position:0% no I'm kidding 00:10:03.320 --> 00:10:05.630 align:start position:0% no I'm kidding this<00:10:04.320> this<00:10:04.380> kid<00:10:04.680> there's<00:10:04.920> this<00:10:05.100> four<00:10:05.279> holes 00:10:05.630 --> 00:10:05.640 align:start position:0% this this kid there's this four holes 00:10:05.640 --> 00:10:06.650 align:start position:0% this this kid there's this four holes there's<00:10:05.820> no<00:10:05.940> way<00:10:06.060> that's<00:10:06.180> gonna<00:10:06.360> work<00:10:06.480> right 00:10:06.650 --> 00:10:06.660 align:start position:0% there's no way that's gonna work right 00:10:06.660 --> 00:10:10.310 align:start position:0% there's no way that's gonna work right so<00:10:06.959> firstly<00:10:07.380> what<00:10:08.220> happens<00:10:08.519> if<00:10:09.180> a<00:10:09.839> phone<00:10:09.959> share 00:10:10.310 --> 00:10:10.320 align:start position:0% so firstly what happens if a phone share 00:10:10.320 --> 00:10:12.889 align:start position:0% so firstly what happens if a phone share is<00:10:10.440> stolen<00:10:10.860> then<00:10:11.640> the<00:10:11.940> timelot<00:10:12.360> shot<00:10:12.480> unlocks 00:10:12.889 --> 00:10:12.899 align:start position:0% is stolen then the timelot shot unlocks 00:10:12.899 --> 00:10:14.990 align:start position:0% is stolen then the timelot shot unlocks let's<00:10:13.080> consider<00:10:13.380> that<00:10:13.560> right 00:10:14.990 --> 00:10:15.000 align:start position:0% let's consider that right 00:10:15.000 --> 00:10:16.670 align:start position:0% let's consider that right so<00:10:15.420> your<00:10:15.720> phone<00:10:15.839> chair<00:10:16.019> is<00:10:16.200> there<00:10:16.320> it's<00:10:16.500> been 00:10:16.670 --> 00:10:16.680 align:start position:0% so your phone chair is there it's been 00:10:16.680 --> 00:10:17.990 align:start position:0% so your phone chair is there it's been stolen<00:10:17.040> right<00:10:17.220> someone<00:10:17.399> just<00:10:17.640> stole<00:10:17.820> your 00:10:17.990 --> 00:10:18.000 align:start position:0% stolen right someone just stole your 00:10:18.000 --> 00:10:18.769 align:start position:0% stolen right someone just stole your phone 00:10:18.769 --> 00:10:18.779 align:start position:0% phone 00:10:18.779 --> 00:10:20.930 align:start position:0% phone well<00:10:19.500> what<00:10:20.040> are<00:10:20.399> you<00:10:20.459> going<00:10:20.580> to<00:10:20.640> do<00:10:20.760> well 00:10:20.930 --> 00:10:20.940 align:start position:0% well what are you going to do well 00:10:20.940 --> 00:10:22.370 align:start position:0% well what are you going to do well you're<00:10:21.120> going<00:10:21.300> to<00:10:21.360> key<00:10:21.600> refresh<00:10:22.019> right<00:10:22.200> that's 00:10:22.370 --> 00:10:22.380 align:start position:0% you're going to key refresh right that's 00:10:22.380 --> 00:10:23.630 align:start position:0% you're going to key refresh right that's the<00:10:22.560> only<00:10:22.680> thing<00:10:22.860> you<00:10:23.040> have<00:10:23.160> protecting<00:10:23.580> your 00:10:23.630 --> 00:10:23.640 align:start position:0% the only thing you have protecting your 00:10:23.640 --> 00:10:24.829 align:start position:0% the only thing you have protecting your shares<00:10:23.940> you're<00:10:24.120> going<00:10:24.240> to<00:10:24.300> keep<00:10:24.420> refreshed 00:10:24.829 --> 00:10:24.839 align:start position:0% shares you're going to keep refreshed 00:10:24.839 --> 00:10:26.389 align:start position:0% shares you're going to keep refreshed you<00:10:25.019> bought<00:10:25.140> a<00:10:25.380> new<00:10:25.500> phone<00:10:25.740> so<00:10:25.980> you're<00:10:26.160> a<00:10:26.279> new 00:10:26.389 --> 00:10:26.399 align:start position:0% you bought a new phone so you're a new 00:10:26.399 --> 00:10:28.070 align:start position:0% you bought a new phone so you're a new show<00:10:26.580> on<00:10:26.700> that<00:10:26.820> phone<00:10:26.940> perfect 00:10:28.070 --> 00:10:28.080 align:start position:0% show on that phone perfect 00:10:28.080 --> 00:10:31.310 align:start position:0% show on that phone perfect but<00:10:28.920> the<00:10:29.399> attacker<00:10:29.880> and<00:10:30.120> the<00:10:30.300> hacker<00:10:30.600> who<00:10:30.779> like 00:10:31.310 --> 00:10:31.320 align:start position:0% but the attacker and the hacker who like 00:10:31.320 --> 00:10:32.990 align:start position:0% but the attacker and the hacker who like and<00:10:31.500> hood<00:10:31.800> and<00:10:32.040> teeth<00:10:32.220> who<00:10:32.519> stole<00:10:32.700> your<00:10:32.820> phone 00:10:32.990 --> 00:10:33.000 align:start position:0% and hood and teeth who stole your phone 00:10:33.000 --> 00:10:34.910 align:start position:0% and hood and teeth who stole your phone is<00:10:33.600> not<00:10:33.779> going<00:10:33.959> to<00:10:34.140> actually<00:10:34.380> delete<00:10:34.680> the 00:10:34.910 --> 00:10:34.920 align:start position:0% is not going to actually delete the 00:10:34.920 --> 00:10:37.670 align:start position:0% is not going to actually delete the shares<00:10:35.160> there's<00:10:35.279> no<00:10:35.459> one<00:10:35.760> turn<00:10:35.959> and<00:10:36.959> when<00:10:37.440> a 00:10:37.670 --> 00:10:37.680 align:start position:0% shares there's no one turn and when a 00:10:37.680 --> 00:10:40.550 align:start position:0% shares there's no one turn and when a month<00:10:37.860> passes<00:10:38.399> and<00:10:38.640> the<00:10:38.820> timeline<00:10:39.180> expires 00:10:40.550 --> 00:10:40.560 align:start position:0% month passes and the timeline expires 00:10:40.560 --> 00:10:43.430 align:start position:0% month passes and the timeline expires he's<00:10:41.040> going<00:10:41.339> to<00:10:41.399> be<00:10:41.519> able<00:10:41.640> to<00:10:41.760> steer<00:10:42.120> key<00:10:42.300> gone 00:10:43.430 --> 00:10:43.440 align:start position:0% he's going to be able to steer key gone 00:10:43.440 --> 00:10:45.050 align:start position:0% he's going to be able to steer key gone terrible 00:10:45.050 --> 00:10:45.060 align:start position:0% terrible 00:10:45.060 --> 00:10:47.630 align:start position:0% terrible okay<00:10:45.600> maybe<00:10:46.320> what<00:10:46.680> we<00:10:46.800> can<00:10:46.920> do<00:10:47.040> is<00:10:47.220> stop<00:10:47.459> making 00:10:47.630 --> 00:10:47.640 align:start position:0% okay maybe what we can do is stop making 00:10:47.640 --> 00:10:50.030 align:start position:0% okay maybe what we can do is stop making more<00:10:47.940> shares<00:10:48.300> right<00:10:48.480> the<00:10:48.660> reason<00:10:48.839> why<00:10:49.320> this 00:10:50.030 --> 00:10:50.040 align:start position:0% more shares right the reason why this 00:10:50.040 --> 00:10:51.889 align:start position:0% more shares right the reason why this person<00:10:50.160> was<00:10:50.399> able<00:10:50.640> to<00:10:50.760> get<00:10:50.940> a<00:10:51.180> key<00:10:51.420> was<00:10:51.720> because 00:10:51.889 --> 00:10:51.899 align:start position:0% person was able to get a key was because 00:10:51.899 --> 00:10:54.230 align:start position:0% person was able to get a key was because he<00:10:52.260> had<00:10:52.440> more<00:10:52.680> cryptographic<00:10:53.399> material<00:10:53.760> so 00:10:54.230 --> 00:10:54.240 align:start position:0% he had more cryptographic material so 00:10:54.240 --> 00:10:56.630 align:start position:0% he had more cryptographic material so we're<00:10:54.420> going<00:10:54.540> to<00:10:54.660> do<00:10:54.899> is<00:10:55.500> instead<00:10:56.160> of<00:10:56.220> having 00:10:56.630 --> 00:10:56.640 align:start position:0% we're going to do is instead of having 00:10:56.640 --> 00:10:59.150 align:start position:0% we're going to do is instead of having more<00:10:57.240> shares<00:10:57.720> the<00:10:58.079> time<00:10:58.200> of<00:10:58.440> share<00:10:58.740> itself<00:10:58.980> is 00:10:59.150 --> 00:10:59.160 align:start position:0% more shares the time of share itself is 00:10:59.160 --> 00:11:00.769 align:start position:0% more shares the time of share itself is just<00:10:59.339> going<00:10:59.459> to<00:10:59.579> be<00:10:59.640> my<00:10:59.760> phone<00:10:59.940> share<00:11:00.240> right<00:11:00.420> so 00:11:00.769 --> 00:11:00.779 align:start position:0% just going to be my phone share right so 00:11:00.779 --> 00:11:03.230 align:start position:0% just going to be my phone share right so this<00:11:01.320> person<00:11:01.500> stole<00:11:01.920> my<00:11:02.100> phone<00:11:02.220> and<00:11:02.940> then<00:11:03.120> he 00:11:03.230 --> 00:11:03.240 align:start position:0% this person stole my phone and then he 00:11:03.240 --> 00:11:04.790 align:start position:0% this person stole my phone and then he gets<00:11:03.420> the<00:11:03.540> timeline<00:11:03.899> service<00:11:04.019> is<00:11:04.380> also<00:11:04.620> my 00:11:04.790 --> 00:11:04.800 align:start position:0% gets the timeline service is also my 00:11:04.800 --> 00:11:06.170 align:start position:0% gets the timeline service is also my phone<00:11:04.920> share<00:11:05.220> so<00:11:05.399> he<00:11:05.579> doesn't<00:11:05.700> really<00:11:05.880> get 00:11:06.170 --> 00:11:06.180 align:start position:0% phone share so he doesn't really get 00:11:06.180 --> 00:11:10.190 align:start position:0% phone share so he doesn't really get anything<00:11:06.779> new<00:11:07.200> so<00:11:07.860> I'm<00:11:08.040> safe 00:11:10.190 --> 00:11:10.200 align:start position:0% anything new so I'm safe 00:11:10.200 --> 00:11:12.290 align:start position:0% anything new so I'm safe uh<00:11:10.860> not<00:11:11.160> really 00:11:12.290 --> 00:11:12.300 align:start position:0% uh not really 00:11:12.300 --> 00:11:14.210 align:start position:0% uh not really um if<00:11:12.540> you<00:11:12.660> store<00:11:12.839> your<00:11:13.019> laptop<00:11:13.440> right<00:11:13.920> and 00:11:14.210 --> 00:11:14.220 align:start position:0% um if you store your laptop right and 00:11:14.220 --> 00:11:15.829 align:start position:0% um if you store your laptop right and the<00:11:14.399> timeline<00:11:14.700> unlocks<00:11:15.240> you're<00:11:15.420> running<00:11:15.600> the 00:11:15.829 --> 00:11:15.839 align:start position:0% the timeline unlocks you're running the 00:11:15.839 --> 00:11:18.170 align:start position:0% the timeline unlocks you're running the same<00:11:16.019> problem<00:11:16.220> so<00:11:17.220> it<00:11:17.459> looks<00:11:17.700> like<00:11:17.760> we're<00:11:17.940> in<00:11:18.120> a 00:11:18.170 --> 00:11:18.180 align:start position:0% same problem so it looks like we're in a 00:11:18.180 --> 00:11:22.730 align:start position:0% same problem so it looks like we're in a dilemma<00:11:18.540> here<00:11:18.779> right<00:11:18.959> what<00:11:19.320> really<00:11:19.620> can<00:11:19.980> we<00:11:20.100> do 00:11:22.730 --> 00:11:22.740 align:start position:0% 00:11:22.740 --> 00:11:25.069 align:start position:0% um a<00:11:23.040> new<00:11:23.220> solution<00:11:23.579> right<00:11:24.000> let's<00:11:24.480> split<00:11:24.899> the 00:11:25.069 --> 00:11:25.079 align:start position:0% um a new solution right let's split the 00:11:25.079 --> 00:11:26.990 align:start position:0% um a new solution right let's split the device<00:11:25.200> share<00:11:25.620> into 00:11:26.990 --> 00:11:27.000 align:start position:0% device share into 00:11:27.000 --> 00:11:30.170 align:start position:0% device share into a<00:11:27.540> time<00:11:27.660> lock<00:11:27.839> share<00:11:28.200> and<00:11:28.920> then<00:11:29.040> a<00:11:29.279> custodial 00:11:30.170 --> 00:11:30.180 align:start position:0% a time lock share and then a custodial 00:11:30.180 --> 00:11:32.210 align:start position:0% a time lock share and then a custodial sub-share<00:11:30.779> right<00:11:31.260> so<00:11:31.440> how<00:11:31.620> does<00:11:31.920> that<00:11:32.040> look 00:11:32.210 --> 00:11:32.220 align:start position:0% sub-share right so how does that look 00:11:32.220 --> 00:11:34.069 align:start position:0% sub-share right so how does that look like<00:11:32.339> how<00:11:32.519> does<00:11:32.640> that<00:11:32.820> look<00:11:32.940> like 00:11:34.069 --> 00:11:34.079 align:start position:0% like how does that look like 00:11:34.079 --> 00:11:35.870 align:start position:0% like how does that look like so<00:11:34.680> what<00:11:34.860> we're<00:11:34.980> going<00:11:35.100> to<00:11:35.220> do<00:11:35.339> is<00:11:35.459> we<00:11:35.760> have 00:11:35.870 --> 00:11:35.880 align:start position:0% so what we're going to do is we have 00:11:35.880 --> 00:11:37.970 align:start position:0% so what we're going to do is we have this<00:11:35.940> initial<00:11:36.360> setup<00:11:36.660> right<00:11:36.899> two<00:11:37.680> out<00:11:37.860> of 00:11:37.970 --> 00:11:37.980 align:start position:0% this initial setup right two out of 00:11:37.980 --> 00:11:40.610 align:start position:0% this initial setup right two out of three<00:11:38.160> factors<00:11:38.519> you<00:11:38.880> have<00:11:39.000> an<00:11:39.060> email<00:11:39.240> login<00:11:39.620> a 00:11:40.610 --> 00:11:40.620 align:start position:0% three factors you have an email login a 00:11:40.620 --> 00:11:43.009 align:start position:0% three factors you have an email login a phone<00:11:40.860> uh<00:11:41.700> and<00:11:41.880> a<00:11:41.940> laptop<00:11:42.180> share<00:11:42.480> so<00:11:42.660> that<00:11:42.779> they 00:11:43.009 --> 00:11:43.019 align:start position:0% phone uh and a laptop share so that they 00:11:43.019 --> 00:11:44.389 align:start position:0% phone uh and a laptop share so that they actually<00:11:43.200> start<00:11:43.440> based<00:11:43.800> on<00:11:43.860> these<00:11:44.040> factors 00:11:44.389 --> 00:11:44.399 align:start position:0% actually start based on these factors 00:11:44.399 --> 00:11:46.910 align:start position:0% actually start based on these factors and<00:11:45.060> we're<00:11:45.300> going<00:11:45.540> to<00:11:45.600> split<00:11:46.380> the<00:11:46.740> phone 00:11:46.910 --> 00:11:46.920 align:start position:0% and we're going to split the phone 00:11:46.920 --> 00:11:49.130 align:start position:0% and we're going to split the phone factor<00:11:47.459> into<00:11:47.640> two<00:11:48.000> sub<00:11:48.300> shares<00:11:48.720> let's<00:11:49.019> explain 00:11:49.130 --> 00:11:49.140 align:start position:0% factor into two sub shares let's explain 00:11:49.140 --> 00:11:52.130 align:start position:0% factor into two sub shares let's explain it<00:11:49.440> to<00:11:50.100> and<00:11:50.579> one<00:11:50.760> will<00:11:50.940> be<00:11:51.060> time<00:11:51.240> locked 00:11:52.130 --> 00:11:52.140 align:start position:0% it to and one will be time locked 00:11:52.140 --> 00:11:54.769 align:start position:0% it to and one will be time locked and<00:11:52.860> the<00:11:53.040> other<00:11:53.220> will<00:11:53.579> be<00:11:53.760> encrypted<00:11:54.360> in<00:11:54.660> your 00:11:54.769 --> 00:11:54.779 align:start position:0% and the other will be encrypted in your 00:11:54.779 --> 00:11:55.730 align:start position:0% and the other will be encrypted in your email 00:11:55.730 --> 00:11:55.740 align:start position:0% email 00:11:55.740 --> 00:11:59.690 align:start position:0% email right<00:11:56.279> so<00:11:57.120> this<00:11:57.420> way<00:11:57.660> let's<00:11:58.140> say<00:11:58.380> if<00:11:58.980> someone's 00:11:59.690 --> 00:11:59.700 align:start position:0% right so this way let's say if someone's 00:11:59.700 --> 00:12:01.850 align:start position:0% right so this way let's say if someone's used<00:11:59.940> any<00:12:00.180> of<00:12:00.300> the<00:12:00.420> factors<00:12:00.779> and<00:12:01.500> they<00:12:01.620> get<00:12:01.800> a 00:12:01.850 --> 00:12:01.860 align:start position:0% used any of the factors and they get a 00:12:01.860 --> 00:12:03.350 align:start position:0% used any of the factors and they get a time<00:12:01.980> of<00:12:02.220> share<00:12:02.459> they<00:12:02.820> still<00:12:03.000> have<00:12:03.240> to 00:12:03.350 --> 00:12:03.360 align:start position:0% time of share they still have to 00:12:03.360 --> 00:12:05.329 align:start position:0% time of share they still have to compromise<00:12:03.839> another<00:12:04.320> factor<00:12:04.860> which<00:12:05.100> is<00:12:05.220> your 00:12:05.329 --> 00:12:05.339 align:start position:0% compromise another factor which is your 00:12:05.339 --> 00:12:06.170 align:start position:0% compromise another factor which is your email 00:12:06.170 --> 00:12:06.180 align:start position:0% email 00:12:06.180 --> 00:12:09.889 align:start position:0% email right<00:12:06.660> so<00:12:07.140> key<00:12:08.040> recovery<00:12:08.640> still<00:12:08.880> works<00:12:09.300> if<00:12:09.779> you 00:12:09.889 --> 00:12:09.899 align:start position:0% right so key recovery still works if you 00:12:09.899 --> 00:12:12.650 align:start position:0% right so key recovery still works if you lose<00:12:10.019> everything<00:12:10.440> you<00:12:11.399> still<00:12:11.640> have 00:12:12.650 --> 00:12:12.660 align:start position:0% lose everything you still have 00:12:12.660 --> 00:12:14.870 align:start position:0% lose everything you still have let's<00:12:13.079> say<00:12:13.200> you<00:12:13.380> lose<00:12:13.500> both<00:12:13.800> your<00:12:14.279> phone<00:12:14.640> and 00:12:14.870 --> 00:12:14.880 align:start position:0% let's say you lose both your phone and 00:12:14.880 --> 00:12:16.610 align:start position:0% let's say you lose both your phone and your<00:12:15.000> laptop<00:12:15.240> it<00:12:15.480> caught<00:12:15.660> fire<00:12:15.959> in<00:12:16.320> the<00:12:16.500> house 00:12:16.610 --> 00:12:16.620 align:start position:0% your laptop it caught fire in the house 00:12:16.620 --> 00:12:17.750 align:start position:0% your laptop it caught fire in the house right 00:12:17.750 --> 00:12:17.760 align:start position:0% right 00:12:17.760 --> 00:12:19.610 align:start position:0% right um<00:12:17.820> you<00:12:18.060> still<00:12:18.180> have<00:12:18.480> the<00:12:18.839> time<00:12:19.079> lock<00:12:19.260> share 00:12:19.610 --> 00:12:19.620 align:start position:0% um you still have the time lock share 00:12:19.620 --> 00:12:21.350 align:start position:0% um you still have the time lock share and<00:12:20.160> the<00:12:20.279> email<00:12:20.399> share<00:12:20.760> which<00:12:20.940> you<00:12:21.060> can<00:12:21.120> use<00:12:21.240> to 00:12:21.350 --> 00:12:21.360 align:start position:0% and the email share which you can use to 00:12:21.360 --> 00:12:23.569 align:start position:0% and the email share which you can use to reconstruct<00:12:21.779> your<00:12:21.899> phone<00:12:22.079> share<00:12:22.380> and<00:12:23.100> and<00:12:23.339> you 00:12:23.569 --> 00:12:23.579 align:start position:0% reconstruct your phone share and and you 00:12:23.579 --> 00:12:24.889 align:start position:0% reconstruct your phone share and and you already<00:12:23.700> have<00:12:23.880> emotion<00:12:24.240> so<00:12:24.480> you<00:12:24.540> can<00:12:24.600> redraw 00:12:24.889 --> 00:12:24.899 align:start position:0% already have emotion so you can redraw 00:12:24.899 --> 00:12:27.069 align:start position:0% already have emotion so you can redraw the<00:12:25.019> line<00:12:25.140> right<00:12:25.320> so<00:12:25.500> you're<00:12:25.620> still<00:12:25.920> safe<00:12:26.160> from 00:12:27.069 --> 00:12:27.079 align:start position:0% the line right so you're still safe from 00:12:27.079 --> 00:12:30.050 align:start position:0% the line right so you're still safe from catastrophic<00:12:28.079> loss<00:12:28.500> but<00:12:29.100> adversary<00:12:29.640> can't 00:12:30.050 --> 00:12:30.060 align:start position:0% catastrophic loss but adversary can't 00:12:30.060 --> 00:12:32.329 align:start position:0% catastrophic loss but adversary can't actually<00:12:30.360> get<00:12:30.899> your<00:12:31.140> key<00:12:31.380> unless<00:12:31.800> he<00:12:32.040> also 00:12:32.329 --> 00:12:32.339 align:start position:0% actually get your key unless he also 00:12:32.339 --> 00:12:34.550 align:start position:0% actually get your key unless he also compromises<00:12:33.000> another<00:12:33.300> Factor<00:12:33.899> so<00:12:34.320> you<00:12:34.440> still 00:12:34.550 --> 00:12:34.560 align:start position:0% compromises another Factor so you still 00:12:34.560 --> 00:12:38.110 align:start position:0% compromises another Factor so you still get<00:12:34.740> the<00:12:34.860> two<00:12:34.980> fa<00:12:35.279> properties<00:12:35.579> perfect 00:12:38.110 --> 00:12:38.120 align:start position:0% 00:12:38.120 --> 00:12:40.670 align:start position:0% but<00:12:39.120> it's<00:12:39.300> also<00:12:39.600> another<00:12:39.720> problem 00:12:40.670 --> 00:12:40.680 align:start position:0% but it's also another problem 00:12:40.680 --> 00:12:42.829 align:start position:0% but it's also another problem the<00:12:41.160> email<00:12:41.279> provider<00:12:41.940> might<00:12:42.480> not<00:12:42.660> delete 00:12:42.829 --> 00:12:42.839 align:start position:0% the email provider might not delete 00:12:42.839 --> 00:12:45.650 align:start position:0% the email provider might not delete shares<00:12:43.320> during<00:12:43.440> key<00:12:43.680> refresh<00:12:44.100> let's<00:12:44.519> see<00:12:44.820> why 00:12:45.650 --> 00:12:45.660 align:start position:0% shares during key refresh let's see why 00:12:45.660 --> 00:12:48.170 align:start position:0% shares during key refresh let's see why that's<00:12:45.839> a<00:12:46.079> problem 00:12:48.170 --> 00:12:48.180 align:start position:0% that's a problem 00:12:48.180 --> 00:12:50.509 align:start position:0% that's a problem what<00:12:48.720> happens<00:12:48.899> if<00:12:49.620> let's<00:12:49.980> say<00:12:50.160> the<00:12:50.339> email 00:12:50.509 --> 00:12:50.519 align:start position:0% what happens if let's say the email 00:12:50.519 --> 00:12:53.870 align:start position:0% what happens if let's say the email provider<00:12:51.120> doesn't<00:12:51.899> delete<00:12:52.260> shares<00:12:53.100> right<00:12:53.399> so 00:12:53.870 --> 00:12:53.880 align:start position:0% provider doesn't delete shares right so 00:12:53.880 --> 00:12:55.069 align:start position:0% provider doesn't delete shares right so let's<00:12:53.940> go<00:12:54.120> back<00:12:54.240> to<00:12:54.360> the<00:12:54.480> scenario<00:12:54.779> right<00:12:54.899> you 00:12:55.069 --> 00:12:55.079 align:start position:0% let's go back to the scenario right you 00:12:55.079 --> 00:12:59.629 align:start position:0% let's go back to the scenario right you do<00:12:55.320> key<00:12:55.440> refresh<00:12:55.920> right<00:12:56.760> and 00:12:59.629 --> 00:12:59.639 align:start position:0% do key refresh right and 00:12:59.639 --> 00:13:01.970 align:start position:0% do key refresh right and the<00:13:00.060> email<00:13:00.180> provider<00:13:00.899> instead<00:13:01.500> of<00:13:01.620> doing<00:13:01.800> key 00:13:01.970 --> 00:13:01.980 align:start position:0% the email provider instead of doing key 00:13:01.980 --> 00:13:04.009 align:start position:0% the email provider instead of doing key refresh<00:13:02.459> properly<00:13:02.820> and<00:13:03.180> during<00:13:03.360> key<00:13:03.600> refresh 00:13:04.009 --> 00:13:04.019 align:start position:0% refresh properly and during key refresh 00:13:04.019 --> 00:13:05.449 align:start position:0% refresh properly and during key refresh you're<00:13:04.200> supposed<00:13:04.320> to<00:13:04.500> discard<00:13:04.980> the<00:13:05.279> old 00:13:05.449 --> 00:13:05.459 align:start position:0% you're supposed to discard the old 00:13:05.459 --> 00:13:07.310 align:start position:0% you're supposed to discard the old shares<00:13:05.880> he<00:13:06.480> doesn't 00:13:07.310 --> 00:13:07.320 align:start position:0% shares he doesn't 00:13:07.320 --> 00:13:10.430 align:start position:0% shares he doesn't just<00:13:07.860> keeps<00:13:08.220> the<00:13:08.279> evil<00:13:08.579> share 00:13:10.430 --> 00:13:10.440 align:start position:0% just keeps the evil share 00:13:10.440 --> 00:13:12.170 align:start position:0% just keeps the evil share after<00:13:10.740> all<00:13:11.040> why<00:13:11.220> not<00:13:11.339> why<00:13:11.579> shouldn't<00:13:11.880> he<00:13:12.000> keep 00:13:12.170 --> 00:13:12.180 align:start position:0% after all why not why shouldn't he keep 00:13:12.180 --> 00:13:13.310 align:start position:0% after all why not why shouldn't he keep it 00:13:13.310 --> 00:13:13.320 align:start position:0% it 00:13:13.320 --> 00:13:15.050 align:start position:0% it well 00:13:15.050 --> 00:13:15.060 align:start position:0% well 00:13:15.060 --> 00:13:17.389 align:start position:0% well after<00:13:15.540> a<00:13:15.720> month<00:13:15.839> passes<00:13:16.320> right<00:13:16.620> so<00:13:17.040> let's<00:13:17.160> go 00:13:17.389 --> 00:13:17.399 align:start position:0% after a month passes right so let's go 00:13:17.399 --> 00:13:19.730 align:start position:0% after a month passes right so let's go back<00:13:17.519> a<00:13:17.700> bit<00:13:17.880> after<00:13:18.540> a<00:13:18.779> month<00:13:18.899> passes<00:13:19.380> right 00:13:19.730 --> 00:13:19.740 align:start position:0% back a bit after a month passes right 00:13:19.740 --> 00:13:21.650 align:start position:0% back a bit after a month passes right this<00:13:20.579> is<00:13:20.700> going<00:13:20.820> to<00:13:20.940> unlock<00:13:21.060> right<00:13:21.360> the<00:13:21.540> time 00:13:21.650 --> 00:13:21.660 align:start position:0% this is going to unlock right the time 00:13:21.660 --> 00:13:22.910 align:start position:0% this is going to unlock right the time launcher<00:13:21.959> is<00:13:22.019> going<00:13:22.139> to<00:13:22.200> unlock 00:13:22.910 --> 00:13:22.920 align:start position:0% launcher is going to unlock 00:13:22.920 --> 00:13:24.769 align:start position:0% launcher is going to unlock and<00:13:23.160> it's<00:13:23.279> going<00:13:23.459> to<00:13:23.579> reconstruct<00:13:24.180> the<00:13:24.660> phone 00:13:24.769 --> 00:13:24.779 align:start position:0% and it's going to reconstruct the phone 00:13:24.779 --> 00:13:27.470 align:start position:0% and it's going to reconstruct the phone share<00:13:25.320> on<00:13:25.740> the<00:13:25.920> previous<00:13:26.160> secret<00:13:27.000> sharing 00:13:27.470 --> 00:13:27.480 align:start position:0% share on the previous secret sharing 00:13:27.480 --> 00:13:29.690 align:start position:0% share on the previous secret sharing polynomial<00:13:28.019> and<00:13:28.740> reconstruct<00:13:29.220> your<00:13:29.339> key<00:13:29.519> so 00:13:29.690 --> 00:13:29.700 align:start position:0% polynomial and reconstruct your key so 00:13:29.700 --> 00:13:31.910 align:start position:0% polynomial and reconstruct your key so even<00:13:29.880> though<00:13:30.060> you<00:13:30.240> refresh<00:13:30.660> your<00:13:30.779> shares<00:13:31.200> this 00:13:31.910 --> 00:13:31.920 align:start position:0% even though you refresh your shares this 00:13:31.920 --> 00:13:34.430 align:start position:0% even though you refresh your shares this is<00:13:32.100> still<00:13:32.220> a<00:13:32.399> problem<00:13:32.579> as<00:13:33.480> long<00:13:33.720> as<00:13:34.079> the 00:13:34.430 --> 00:13:34.440 align:start position:0% is still a problem as long as the 00:13:34.440 --> 00:13:36.790 align:start position:0% is still a problem as long as the custodian<00:13:34.920> doesn't<00:13:35.279> delete<00:13:35.579> the<00:13:35.880> share<00:13:36.120> right 00:13:36.790 --> 00:13:36.800 align:start position:0% custodian doesn't delete the share right 00:13:36.800 --> 00:13:39.350 align:start position:0% custodian doesn't delete the share right you<00:13:37.800> still<00:13:37.980> have<00:13:38.100> this<00:13:38.279> problem<00:13:38.459> where<00:13:38.940> when 00:13:39.350 --> 00:13:39.360 align:start position:0% you still have this problem where when 00:13:39.360 --> 00:13:41.750 align:start position:0% you still have this problem where when the<00:13:39.540> time<00:13:39.660> log<00:13:39.899> expires<00:13:40.560> the<00:13:41.100> custodian<00:13:41.579> can 00:13:41.750 --> 00:13:41.760 align:start position:0% the time log expires the custodian can 00:13:41.760 --> 00:13:43.550 align:start position:0% the time log expires the custodian can get<00:13:41.880> your<00:13:42.060> key 00:13:43.550 --> 00:13:43.560 align:start position:0% get your key 00:13:43.560 --> 00:13:46.990 align:start position:0% get your key foreign 00:13:46.990 --> 00:13:47.000 align:start position:0% 00:13:47.000 --> 00:13:49.430 align:start position:0% no<00:13:48.000> custodial<00:13:48.360> factors<00:13:48.720> let's<00:13:48.899> just<00:13:49.079> get<00:13:49.260> rid 00:13:49.430 --> 00:13:49.440 align:start position:0% no custodial factors let's just get rid 00:13:49.440 --> 00:13:51.710 align:start position:0% no custodial factors let's just get rid of<00:13:49.620> all<00:13:49.800> the<00:13:49.920> custodians<00:13:50.459> and<00:13:50.519> third<00:13:50.760> parties 00:13:51.710 --> 00:13:51.720 align:start position:0% of all the custodians and third parties 00:13:51.720 --> 00:13:54.050 align:start position:0% of all the custodians and third parties there's<00:13:52.320> a<00:13:52.440> problem<00:13:52.620> there<00:13:52.860> though<00:13:53.639> we're 00:13:54.050 --> 00:13:54.060 align:start position:0% there's a problem there though we're 00:13:54.060 --> 00:13:56.030 align:start position:0% there's a problem there though we're trying<00:13:54.300> to<00:13:54.480> solve<00:13:54.839> for<00:13:55.139> the<00:13:55.260> disaster<00:13:55.680> case 00:13:56.030 --> 00:13:56.040 align:start position:0% trying to solve for the disaster case 00:13:56.040 --> 00:13:58.430 align:start position:0% trying to solve for the disaster case when<00:13:56.279> you<00:13:56.459> lose<00:13:56.700> all<00:13:57.360> your<00:13:57.540> user<00:13:57.839> own<00:13:58.019> factors 00:13:58.430 --> 00:13:58.440 align:start position:0% when you lose all your user own factors 00:13:58.440 --> 00:14:00.889 align:start position:0% when you lose all your user own factors do<00:13:58.980> you<00:13:59.220> really<00:13:59.339> want<00:13:59.820> all<00:14:00.240> your<00:14:00.480> factors<00:14:00.779> to 00:14:00.889 --> 00:14:00.899 align:start position:0% do you really want all your factors to 00:14:00.899 --> 00:14:02.269 align:start position:0% do you really want all your factors to be<00:14:01.019> lost<00:14:01.139> because<00:14:01.380> if<00:14:01.560> they're<00:14:01.740> all<00:14:01.920> user 00:14:02.269 --> 00:14:02.279 align:start position:0% be lost because if they're all user 00:14:02.279 --> 00:14:04.550 align:start position:0% be lost because if they're all user owned<00:14:02.639> and<00:14:03.300> something<00:14:03.420> happens<00:14:03.779> to<00:14:04.079> you<00:14:04.260> such 00:14:04.550 --> 00:14:04.560 align:start position:0% owned and something happens to you such 00:14:04.560 --> 00:14:06.470 align:start position:0% owned and something happens to you such that<00:14:04.800> all<00:14:05.040> the<00:14:05.220> factors<00:14:05.519> go<00:14:05.639> away<00:14:05.820> there's 00:14:06.470 --> 00:14:06.480 align:start position:0% that all the factors go away there's 00:14:06.480 --> 00:14:08.990 align:start position:0% that all the factors go away there's going<00:14:06.660> to<00:14:06.720> be<00:14:06.839> no<00:14:07.019> way<00:14:07.139> to<00:14:07.380> recover<00:14:07.680> a<00:14:07.860> key<00:14:08.040> and 00:14:08.990 --> 00:14:09.000 align:start position:0% going to be no way to recover a key and 00:14:09.000 --> 00:14:10.550 align:start position:0% going to be no way to recover a key and this<00:14:09.300> problem<00:14:09.480> is<00:14:09.720> really<00:14:09.899> less<00:14:10.079> of<00:14:10.320> a<00:14:10.440> problem 00:14:10.550 --> 00:14:10.560 align:start position:0% this problem is really less of a problem 00:14:10.560 --> 00:14:13.430 align:start position:0% this problem is really less of a problem than<00:14:10.860> a<00:14:11.160> statement<00:14:11.519> it's<00:14:12.180> not<00:14:12.480> possible<00:14:13.019> to 00:14:13.430 --> 00:14:13.440 align:start position:0% than a statement it's not possible to 00:14:13.440 --> 00:14:15.530 align:start position:0% than a statement it's not possible to get<00:14:13.560> recovery<00:14:14.040> from<00:14:14.519> catastrophic<00:14:15.180> loss 00:14:15.530 --> 00:14:15.540 align:start position:0% get recovery from catastrophic loss 00:14:15.540 --> 00:14:17.509 align:start position:0% get recovery from catastrophic loss without<00:14:16.079> third<00:14:16.380> parties<00:14:16.740> having<00:14:16.980> at<00:14:17.399> least 00:14:17.509 --> 00:14:17.519 align:start position:0% without third parties having at least 00:14:17.519 --> 00:14:20.210 align:start position:0% without third parties having at least threshold<00:14:18.300> minus<00:14:18.660> one<00:14:18.779> shares 00:14:20.210 --> 00:14:20.220 align:start position:0% threshold minus one shares 00:14:20.220 --> 00:14:22.610 align:start position:0% threshold minus one shares let's<00:14:20.700> see<00:14:20.940> why<00:14:21.180> right 00:14:22.610 --> 00:14:22.620 align:start position:0% let's see why right 00:14:22.620 --> 00:14:25.250 align:start position:0% let's see why right um<00:14:22.680> fundamentally<00:14:23.579> if<00:14:24.420> custodians<00:14:25.139> only 00:14:25.250 --> 00:14:25.260 align:start position:0% um fundamentally if custodians only 00:14:25.260 --> 00:14:27.410 align:start position:0% um fundamentally if custodians only control<00:14:25.620> let's<00:14:26.279> say<00:14:26.399> threshold<00:14:26.880> minus<00:14:27.240> two 00:14:27.410 --> 00:14:27.420 align:start position:0% control let's say threshold minus two 00:14:27.420 --> 00:14:29.449 align:start position:0% control let's say threshold minus two Which<00:14:27.600> is<00:14:27.720> less<00:14:27.839> than<00:14:27.959> threshold<00:14:28.320> minus<00:14:28.560> one 00:14:29.449 --> 00:14:29.459 align:start position:0% Which is less than threshold minus one 00:14:29.459 --> 00:14:31.009 align:start position:0% Which is less than threshold minus one um<00:14:29.519> with<00:14:29.760> a<00:14:29.880> Time<00:14:30.060> log<00:14:30.240> shared<00:14:30.600> that<00:14:30.660> unlocks 00:14:31.009 --> 00:14:31.019 align:start position:0% um with a Time log shared that unlocks 00:14:31.019 --> 00:14:33.230 align:start position:0% um with a Time log shared that unlocks after<00:14:31.139> one<00:14:31.380> month<00:14:31.620> they<00:14:32.519> will<00:14:32.700> only<00:14:32.880> have 00:14:33.230 --> 00:14:33.240 align:start position:0% after one month they will only have 00:14:33.240 --> 00:14:35.030 align:start position:0% after one month they will only have threshold<00:14:33.720> minus<00:14:34.079> one<00:14:34.200> right<00:14:34.380> so<00:14:34.620> threshold 00:14:35.030 --> 00:14:35.040 align:start position:0% threshold minus one right so threshold 00:14:35.040 --> 00:14:36.410 align:start position:0% threshold minus one right so threshold minus<00:14:35.220> two<00:14:35.399> plus<00:14:35.639> one<00:14:35.820> so<00:14:36.060> we<00:14:36.180> only<00:14:36.360> have 00:14:36.410 --> 00:14:36.420 align:start position:0% minus two plus one so we only have 00:14:36.420 --> 00:14:38.509 align:start position:0% minus two plus one so we only have special<00:14:36.600> minus<00:14:36.959> one<00:14:37.019> shares<00:14:37.380> which<00:14:37.860> is<00:14:38.100> not 00:14:38.509 --> 00:14:38.519 align:start position:0% special minus one shares which is not 00:14:38.519 --> 00:14:39.710 align:start position:0% special minus one shares which is not sufficient<00:14:38.940> it's<00:14:39.120> not<00:14:39.240> going<00:14:39.360> to<00:14:39.420> meet<00:14:39.540> a 00:14:39.710 --> 00:14:39.720 align:start position:0% sufficient it's not going to meet a 00:14:39.720 --> 00:14:42.050 align:start position:0% sufficient it's not going to meet a threshold<00:14:40.079> so<00:14:40.980> because<00:14:41.279> it<00:14:41.519> doesn't<00:14:41.639> mean<00:14:41.880> the 00:14:42.050 --> 00:14:42.060 align:start position:0% threshold so because it doesn't mean the 00:14:42.060 --> 00:14:43.970 align:start position:0% threshold so because it doesn't mean the threshold<00:14:42.360> you<00:14:42.540> need<00:14:42.720> some<00:14:43.019> other<00:14:43.199> Factor<00:14:43.680> you 00:14:43.970 --> 00:14:43.980 align:start position:0% threshold you need some other Factor you 00:14:43.980 --> 00:14:46.610 align:start position:0% threshold you need some other Factor you need<00:14:44.160> some<00:14:44.399> user<00:14:44.699> owned<00:14:45.060> factor<00:14:45.480> and<00:14:46.380> that's 00:14:46.610 --> 00:14:46.620 align:start position:0% need some user owned factor and that's 00:14:46.620 --> 00:14:48.410 align:start position:0% need some user owned factor and that's impossible<00:14:47.160> in<00:14:47.459> this<00:14:47.579> scenario<00:14:47.880> since<00:14:48.180> we're 00:14:48.410 --> 00:14:48.420 align:start position:0% impossible in this scenario since we're 00:14:48.420 --> 00:14:49.970 align:start position:0% impossible in this scenario since we're assuming<00:14:48.839> that<00:14:49.079> the<00:14:49.139> users<00:14:49.380> lost<00:14:49.620> all<00:14:49.800> their 00:14:49.970 --> 00:14:49.980 align:start position:0% assuming that the users lost all their 00:14:49.980 --> 00:14:52.250 align:start position:0% assuming that the users lost all their shares<00:14:50.339> so<00:14:50.699> they<00:14:50.880> can't<00:14:51.000> access<00:14:51.180> anything 00:14:52.250 --> 00:14:52.260 align:start position:0% shares so they can't access anything 00:14:52.260 --> 00:14:54.590 align:start position:0% shares so they can't access anything so<00:14:53.040> we<00:14:53.519> haven't<00:14:53.699> really<00:14:54.000> solved<00:14:54.480> a 00:14:54.590 --> 00:14:54.600 align:start position:0% so we haven't really solved a 00:14:54.600 --> 00:14:56.030 align:start position:0% so we haven't really solved a non-dilution<00:14:55.079> problem<00:14:55.320> remember<00:14:55.620> this 00:14:56.030 --> 00:14:56.040 align:start position:0% non-dilution problem remember this 00:14:56.040 --> 00:14:58.189 align:start position:0% non-dilution problem remember this solution<00:14:56.339> of<00:14:56.519> removing<00:14:56.880> custodians<00:14:57.540> was<00:14:58.019> to 00:14:58.189 --> 00:14:58.199 align:start position:0% solution of removing custodians was to 00:14:58.199 --> 00:14:59.810 align:start position:0% solution of removing custodians was to get<00:14:58.320> rid<00:14:58.440> of<00:14:58.500> the<00:14:58.680> non-delision<00:14:59.100> problem<00:14:59.339> but 00:14:59.810 --> 00:14:59.820 align:start position:0% get rid of the non-delision problem but 00:14:59.820 --> 00:15:01.970 align:start position:0% get rid of the non-delision problem but it's<00:15:00.180> a<00:15:00.300> non-solution<00:15:00.779> so<00:15:01.500> we<00:15:01.620> haven't<00:15:01.740> really 00:15:01.970 --> 00:15:01.980 align:start position:0% it's a non-solution so we haven't really 00:15:01.980 --> 00:15:04.670 align:start position:0% it's a non-solution so we haven't really solved<00:15:02.399> the<00:15:02.579> non-dilusion<00:15:03.180> problem<00:15:03.360> right 00:15:04.670 --> 00:15:04.680 align:start position:0% solved the non-dilusion problem right 00:15:04.680 --> 00:15:06.410 align:start position:0% solved the non-dilusion problem right um we<00:15:05.040> still<00:15:05.220> need<00:15:05.399> third<00:15:05.639> parties<00:15:06.000> to<00:15:06.240> hold 00:15:06.410 --> 00:15:06.420 align:start position:0% um we still need third parties to hold 00:15:06.420 --> 00:15:08.870 align:start position:0% um we still need third parties to hold threshold<00:15:06.899> minus<00:15:07.199> one<00:15:07.440> of<00:15:07.680> the<00:15:07.800> shares<00:15:08.160> but<00:15:08.699> we 00:15:08.870 --> 00:15:08.880 align:start position:0% threshold minus one of the shares but we 00:15:08.880 --> 00:15:10.550 align:start position:0% threshold minus one of the shares but we can't<00:15:09.000> guarantee<00:15:09.360> deletion 00:15:10.550 --> 00:15:10.560 align:start position:0% can't guarantee deletion 00:15:10.560 --> 00:15:13.490 align:start position:0% can't guarantee deletion so<00:15:11.160> in<00:15:11.760> one<00:15:11.940> month<00:15:12.120> the<00:15:12.540> custodian<00:15:13.079> might<00:15:13.380> be 00:15:13.490 --> 00:15:13.500 align:start position:0% so in one month the custodian might be 00:15:13.500 --> 00:15:17.210 align:start position:0% so in one month the custodian might be malicious<00:15:13.920> and<00:15:14.040> it'll<00:15:14.279> still<00:15:14.399> the<00:15:14.639> key 00:15:17.210 --> 00:15:17.220 align:start position:0% 00:15:17.220 --> 00:15:19.790 align:start position:0% we<00:15:17.579> have<00:15:17.760> a<00:15:17.880> final<00:15:18.000> solution<00:15:18.420> for<00:15:18.660> now<00:15:18.839> one<00:15:19.560> of 00:15:19.790 --> 00:15:19.800 align:start position:0% we have a final solution for now one of 00:15:19.800 --> 00:15:21.230 align:start position:0% we have a final solution for now one of end<00:15:20.040> deletion 00:15:21.230 --> 00:15:21.240 align:start position:0% end deletion 00:15:21.240 --> 00:15:25.550 align:start position:0% end deletion so<00:15:22.639> there<00:15:23.639> are<00:15:23.820> many<00:15:24.000> forms<00:15:24.540> of<00:15:24.720> trust<00:15:25.079> right 00:15:25.550 --> 00:15:25.560 align:start position:0% so there are many forms of trust right 00:15:25.560 --> 00:15:27.470 align:start position:0% so there are many forms of trust right and<00:15:26.040> the<00:15:26.160> best<00:15:26.279> kind<00:15:26.459> of<00:15:26.579> trust<00:15:26.880> is<00:15:27.180> like 00:15:27.470 --> 00:15:27.480 align:start position:0% and the best kind of trust is like 00:15:27.480 --> 00:15:30.110 align:start position:0% and the best kind of trust is like trustless<00:15:28.199> right<00:15:28.500> zero<00:15:28.920> of<00:15:29.040> n<00:15:29.220> but<00:15:29.760> there<00:15:29.940> are 00:15:30.110 --> 00:15:30.120 align:start position:0% trustless right zero of n but there are 00:15:30.120 --> 00:15:33.290 align:start position:0% trustless right zero of n but there are also<00:15:30.300> other<00:15:30.480> trust<00:15:30.959> factors<00:15:31.380> like<00:15:31.740> U<00:15:32.339> of<00:15:32.519> N<00:15:32.699> and 00:15:33.290 --> 00:15:33.300 align:start position:0% also other trust factors like U of N and 00:15:33.300 --> 00:15:36.170 align:start position:0% also other trust factors like U of N and one<00:15:33.480> of<00:15:33.660> N<00:15:33.899> and<00:15:34.500> maybe<00:15:34.680> so<00:15:34.980> like<00:15:35.279> half<00:15:35.639> you<00:15:36.060> know 00:15:36.170 --> 00:15:36.180 align:start position:0% one of N and maybe so like half you know 00:15:36.180 --> 00:15:38.269 align:start position:0% one of N and maybe so like half you know majority<00:15:36.779> of<00:15:37.079> n 00:15:38.269 --> 00:15:38.279 align:start position:0% majority of n 00:15:38.279 --> 00:15:40.370 align:start position:0% majority of n um<00:15:38.459> and<00:15:39.000> one<00:15:39.180> way<00:15:39.360> to<00:15:39.480> do<00:15:39.600> that<00:15:39.779> is<00:15:40.019> maybe 00:15:40.370 --> 00:15:40.380 align:start position:0% um and one way to do that is maybe 00:15:40.380 --> 00:15:42.590 align:start position:0% um and one way to do that is maybe there's<00:15:40.800> a<00:15:41.040> way<00:15:41.160> to<00:15:41.820> make<00:15:42.000> it<00:15:42.120> such<00:15:42.240> that<00:15:42.420> we 00:15:42.590 --> 00:15:42.600 align:start position:0% there's a way to make it such that we 00:15:42.600 --> 00:15:44.810 align:start position:0% there's a way to make it such that we can<00:15:42.720> delete<00:15:42.899> the<00:15:43.139> factor<00:15:43.500> if<00:15:43.680> at<00:15:43.920> least<00:15:44.040> one<00:15:44.519> of 00:15:44.810 --> 00:15:44.820 align:start position:0% can delete the factor if at least one of 00:15:44.820 --> 00:15:46.790 align:start position:0% can delete the factor if at least one of the<00:15:45.000> end<00:15:45.240> of<00:15:45.420> the<00:15:45.540> parties<00:15:45.959> follow<00:15:46.320> the<00:15:46.560> rules 00:15:46.790 --> 00:15:46.800 align:start position:0% the end of the parties follow the rules 00:15:46.800 --> 00:15:49.009 align:start position:0% the end of the parties follow the rules so<00:15:47.399> what<00:15:47.519> we<00:15:47.639> could<00:15:47.820> do<00:15:48.000> is<00:15:48.420> right<00:15:48.600> we<00:15:48.899> could 00:15:49.009 --> 00:15:49.019 align:start position:0% so what we could do is right we could 00:15:49.019 --> 00:15:51.590 align:start position:0% so what we could do is right we could have<00:15:49.199> the<00:15:49.380> custodial<00:15:49.860> software<00:15:50.279> be<00:15:51.240> further 00:15:51.590 --> 00:15:51.600 align:start position:0% have the custodial software be further 00:15:51.600 --> 00:15:53.509 align:start position:0% have the custodial software be further split<00:15:51.899> across<00:15:52.260> a<00:15:52.560> hundred<00:15:52.800> independent 00:15:53.509 --> 00:15:53.519 align:start position:0% split across a hundred independent 00:15:53.519 --> 00:15:56.449 align:start position:0% split across a hundred independent custodians<00:15:54.300> like<00:15:54.720> Guardians<00:15:55.320> and<00:15:55.920> trust<00:15:56.220> that 00:15:56.449 --> 00:15:56.459 align:start position:0% custodians like Guardians and trust that 00:15:56.459 --> 00:15:58.009 align:start position:0% custodians like Guardians and trust that one<00:15:56.699> of<00:15:56.820> them<00:15:56.880> will<00:15:57.120> delete<00:15:57.300> it<00:15:57.540> during<00:15:57.779> the 00:15:58.009 --> 00:15:58.019 align:start position:0% one of them will delete it during the 00:15:58.019 --> 00:16:00.710 align:start position:0% one of them will delete it during the refresh<00:15:58.500> as<00:15:58.980> long<00:15:59.160> as<00:15:59.279> they<00:15:59.399> do<00:15:59.639> the<00:16:00.540> key 00:16:00.710 --> 00:16:00.720 align:start position:0% refresh as long as they do the key 00:16:00.720 --> 00:16:03.710 align:start position:0% refresh as long as they do the key material<00:16:01.079> is<00:16:01.260> gone<00:16:01.500> this<00:16:02.399> isn't<00:16:02.699> ideal<00:16:03.060> right 00:16:03.710 --> 00:16:03.720 align:start position:0% material is gone this isn't ideal right 00:16:03.720 --> 00:16:06.410 align:start position:0% material is gone this isn't ideal right one<00:16:04.019> or<00:16:04.260> n<00:16:04.440> is<00:16:04.860> not<00:16:05.279> as<00:16:05.399> good<00:16:05.579> as<00:16:05.699> zero<00:16:06.060> and 00:16:06.410 --> 00:16:06.420 align:start position:0% one or n is not as good as zero and 00:16:06.420 --> 00:16:08.689 align:start position:0% one or n is not as good as zero and trustless<00:16:06.959> but<00:16:07.500> it's<00:16:07.740> close<00:16:07.920> enough<00:16:08.160> and<00:16:08.519> the 00:16:08.689 --> 00:16:08.699 align:start position:0% trustless but it's close enough and the 00:16:08.699 --> 00:16:11.210 align:start position:0% trustless but it's close enough and the cell<00:16:08.820> gets<00:16:09.180> bigger<00:16:09.360> 100<00:16:10.260> 000<00:16:10.260> is<00:16:10.980> actually 00:16:11.210 --> 00:16:11.220 align:start position:0% cell gets bigger 100 000 is actually 00:16:11.220 --> 00:16:13.910 align:start position:0% cell gets bigger 100 000 is actually pretty<00:16:11.459> close<00:16:11.639> to<00:16:11.820> trustless<00:16:12.320> and<00:16:13.320> also<00:16:13.620> doing 00:16:13.910 --> 00:16:13.920 align:start position:0% pretty close to trustless and also doing 00:16:13.920 --> 00:16:15.710 align:start position:0% pretty close to trustless and also doing NL<00:16:14.339> and<00:16:14.459> SQL<00:16:14.760> sharing<00:16:15.060> is<00:16:15.120> very<00:16:15.300> fast<00:16:15.480> it's 00:16:15.710 --> 00:16:15.720 align:start position:0% NL and SQL sharing is very fast it's 00:16:15.720 --> 00:16:17.629 align:start position:0% NL and SQL sharing is very fast it's quite<00:16:15.959> practical 00:16:17.629 --> 00:16:17.639 align:start position:0% quite practical 00:16:17.639 --> 00:16:20.329 align:start position:0% quite practical so<00:16:18.540> this<00:16:19.199> is<00:16:19.260> what<00:16:19.380> a<00:16:19.500> setup<00:16:19.800> looks<00:16:20.040> like<00:16:20.100> right 00:16:20.329 --> 00:16:20.339 align:start position:0% so this is what a setup looks like right 00:16:20.339 --> 00:16:22.430 align:start position:0% so this is what a setup looks like right we<00:16:20.699> have<00:16:20.820> the<00:16:21.060> two<00:16:21.180> or<00:16:21.360> three<00:16:21.480> setting<00:16:21.899> we 00:16:22.430 --> 00:16:22.440 align:start position:0% we have the two or three setting we 00:16:22.440 --> 00:16:24.470 align:start position:0% we have the two or three setting we split<00:16:22.740> it<00:16:22.860> into<00:16:23.100> two<00:16:23.399> one<00:16:23.699> is<00:16:23.880> time<00:16:24.120> locked 00:16:24.470 --> 00:16:24.480 align:start position:0% split it into two one is time locked 00:16:24.480 --> 00:16:26.269 align:start position:0% split it into two one is time locked like<00:16:24.660> I<00:16:24.779> saw<00:16:24.899> earlier<00:16:25.260> and<00:16:25.680> then<00:16:25.800> this<00:16:25.980> one<00:16:26.100> is 00:16:26.269 --> 00:16:26.279 align:start position:0% like I saw earlier and then this one is 00:16:26.279 --> 00:16:28.189 align:start position:0% like I saw earlier and then this one is split<00:16:26.579> in<00:16:26.699> amongst<00:16:27.240> a<00:16:27.480> bunch<00:16:27.600> of<00:16:27.720> Guardians 00:16:28.189 --> 00:16:28.199 align:start position:0% split in amongst a bunch of Guardians 00:16:28.199 --> 00:16:30.530 align:start position:0% split in amongst a bunch of Guardians right<00:16:28.380> however<00:16:29.160> many<00:16:29.339> you<00:16:29.519> want<00:16:29.699> and<00:16:30.360> doing 00:16:30.530 --> 00:16:30.540 align:start position:0% right however many you want and doing 00:16:30.540 --> 00:16:32.389 align:start position:0% right however many you want and doing normal<00:16:30.779> operation<00:16:31.260> right<00:16:31.800> if<00:16:31.980> you<00:16:32.100> do<00:16:32.220> key 00:16:32.389 --> 00:16:32.399 align:start position:0% normal operation right if you do key 00:16:32.399 --> 00:16:34.310 align:start position:0% normal operation right if you do key refresh<00:16:32.880> and<00:16:33.240> at<00:16:33.420> least<00:16:33.540> one<00:16:33.899> of<00:16:34.019> these 00:16:34.310 --> 00:16:34.320 align:start position:0% refresh and at least one of these 00:16:34.320 --> 00:16:36.290 align:start position:0% refresh and at least one of these Guardians<00:16:34.680> deletes<00:16:35.160> the<00:16:35.339> share<00:16:35.579> you're<00:16:36.120> not 00:16:36.290 --> 00:16:36.300 align:start position:0% Guardians deletes the share you're not 00:16:36.300 --> 00:16:37.910 align:start position:0% Guardians deletes the share you're not going<00:16:36.420> to<00:16:36.540> have<00:16:36.660> enough<00:16:36.899> pieces<00:16:37.680> to 00:16:37.910 --> 00:16:37.920 align:start position:0% going to have enough pieces to 00:16:37.920 --> 00:16:39.530 align:start position:0% going to have enough pieces to reconstruct<00:16:38.339> the<00:16:38.459> phone<00:16:38.579> share<00:16:38.940> so<00:16:39.300> it's<00:16:39.420> good 00:16:39.530 --> 00:16:39.540 align:start position:0% reconstruct the phone share so it's good 00:16:39.540 --> 00:16:41.749 align:start position:0% reconstruct the phone share so it's good enough<00:16:39.720> so<00:16:40.259> adversary<00:16:40.800> can<00:16:40.980> get<00:16:41.100> it<00:16:41.220> and 00:16:41.749 --> 00:16:41.759 align:start position:0% enough so adversary can get it and 00:16:41.759 --> 00:16:45.829 align:start position:0% enough so adversary can get it and neither<00:16:42.060> can<00:16:42.480> the<00:16:43.079> custodial<00:16:43.620> provider 00:16:45.829 --> 00:16:45.839 align:start position:0% neither can the custodial provider 00:16:45.839 --> 00:16:49.550 align:start position:0% neither can the custodial provider um<00:16:46.019> but<00:16:46.740> during<00:16:47.040> catastrophic<00:16:47.820> loss<00:16:48.600> when<00:16:49.320> all 00:16:49.550 --> 00:16:49.560 align:start position:0% um but during catastrophic loss when all 00:16:49.560 --> 00:16:51.650 align:start position:0% um but during catastrophic loss when all user<00:16:49.980> factors<00:16:50.279> are<00:16:50.519> gone<00:16:50.699> so<00:16:51.060> your<00:16:51.480> phone 00:16:51.650 --> 00:16:51.660 align:start position:0% user factors are gone so your phone 00:16:51.660 --> 00:16:53.389 align:start position:0% user factors are gone so your phone factor<00:16:52.079> and<00:16:52.259> your<00:16:52.440> platform<00:16:52.800> factor<00:16:53.100> is<00:16:53.220> gone 00:16:53.389 --> 00:16:53.399 align:start position:0% factor and your platform factor is gone 00:16:53.399 --> 00:16:55.550 align:start position:0% factor and your platform factor is gone at<00:16:54.180> least<00:16:54.300> there's<00:16:54.540> some<00:16:54.779> way<00:16:54.959> to<00:16:55.139> recover<00:16:55.380> it 00:16:55.550 --> 00:16:55.560 align:start position:0% at least there's some way to recover it 00:16:55.560 --> 00:16:57.350 align:start position:0% at least there's some way to recover it because<00:16:55.800> your<00:16:56.220> email<00:16:56.519> factor<00:16:56.940> is<00:16:57.000> still<00:16:57.120> there 00:16:57.350 --> 00:16:57.360 align:start position:0% because your email factor is still there 00:16:57.360 --> 00:17:00.290 align:start position:0% because your email factor is still there the<00:16:57.899> tunnel<00:16:58.259> Factor<00:16:58.680> will<00:16:58.980> unlock<00:16:59.279> and<00:17:00.120> the 00:17:00.290 --> 00:17:00.300 align:start position:0% the tunnel Factor will unlock and the 00:17:00.300 --> 00:17:02.569 align:start position:0% the tunnel Factor will unlock and the Guardians<00:17:00.779> should<00:17:01.199> in<00:17:01.740> this<00:17:01.860> scenario<00:17:02.279> return 00:17:02.569 --> 00:17:02.579 align:start position:0% Guardians should in this scenario return 00:17:02.579 --> 00:17:04.610 align:start position:0% Guardians should in this scenario return the<00:17:02.880> shares<00:17:03.240> to<00:17:03.360> you<00:17:03.540> so<00:17:03.899> you<00:17:04.079> can<00:17:04.140> reconstruct 00:17:04.610 --> 00:17:04.620 align:start position:0% the shares to you so you can reconstruct 00:17:04.620 --> 00:17:07.610 align:start position:0% the shares to you so you can reconstruct reconstruct<00:17:05.339> your<00:17:05.520> key 00:17:07.610 --> 00:17:07.620 align:start position:0% reconstruct your key 00:17:07.620 --> 00:17:10.429 align:start position:0% reconstruct your key there<00:17:08.280> a<00:17:08.880> bit<00:17:09.000> more<00:17:09.120> complex<00:17:09.540> but<00:17:10.020> much<00:17:10.319> better 00:17:10.429 --> 00:17:10.439 align:start position:0% there a bit more complex but much better 00:17:10.439 --> 00:17:12.829 align:start position:0% there a bit more complex but much better than<00:17:10.740> what<00:17:10.980> we<00:17:11.160> started<00:17:11.459> with<00:17:12.059> so<00:17:12.480> I<00:17:12.540> have<00:17:12.660> a 00:17:12.829 --> 00:17:12.839 align:start position:0% than what we started with so I have a 00:17:12.839 --> 00:17:14.329 align:start position:0% than what we started with so I have a demo<00:17:13.079> but<00:17:13.260> it<00:17:13.439> doesn't<00:17:13.559> work<00:17:13.740> very<00:17:13.980> well<00:17:14.160> on 00:17:14.329 --> 00:17:14.339 align:start position:0% demo but it doesn't work very well on 00:17:14.339 --> 00:17:15.650 align:start position:0% demo but it doesn't work very well on still<00:17:14.520> internet<00:17:14.699> so<00:17:15.059> you<00:17:15.179> guys<00:17:15.240> can<00:17:15.360> check<00:17:15.540> it 00:17:15.650 --> 00:17:15.660 align:start position:0% still internet so you guys can check it 00:17:15.660 --> 00:17:19.010 align:start position:0% still internet so you guys can check it out<00:17:15.780> on<00:17:16.020> slides<00:17:16.439> below<00:17:16.799> or<00:17:17.339> the<00:17:17.520> link<00:17:17.640> there 00:17:19.010 --> 00:17:19.020 align:start position:0% out on slides below or the link there 00:17:19.020 --> 00:17:19.809 align:start position:0% out on slides below or the link there um 00:17:19.809 --> 00:17:19.819 align:start position:0% um 00:17:19.819 --> 00:17:22.730 align:start position:0% um and<00:17:20.819> if<00:17:21.360> you<00:17:21.540> don't<00:17:21.720> like<00:17:22.020> the<00:17:22.199> solution<00:17:22.500> you 00:17:22.730 --> 00:17:22.740 align:start position:0% and if you don't like the solution you 00:17:22.740 --> 00:17:23.990 align:start position:0% and if you don't like the solution you can<00:17:22.860> also<00:17:23.040> just<00:17:23.160> use<00:17:23.400> a<00:17:23.520> Smart<00:17:23.699> contract 00:17:23.990 --> 00:17:24.000 align:start position:0% can also just use a Smart contract 00:17:24.000 --> 00:17:26.809 align:start position:0% can also just use a Smart contract wallet<00:17:24.480> with<00:17:24.660> a<00:17:24.900> message<00:17:25.079> is<00:17:25.620> much<00:17:25.799> simpler 00:17:26.809 --> 00:17:26.819 align:start position:0% wallet with a message is much simpler 00:17:26.819 --> 00:17:29.450 align:start position:0% wallet with a message is much simpler not<00:17:27.299> everything<00:17:27.480> is<00:17:27.900> NPC<00:17:28.380> really 00:17:29.450 --> 00:17:29.460 align:start position:0% not everything is NPC really 00:17:29.460 --> 00:17:32.330 align:start position:0% not everything is NPC really so<00:17:30.120> some<00:17:30.360> open<00:17:30.540> problems 00:17:32.330 --> 00:17:32.340 align:start position:0% so some open problems 00:17:32.340 --> 00:17:34.190 align:start position:0% so some open problems um<00:17:32.400> the<00:17:32.640> Guardians<00:17:33.000> can<00:17:33.120> maybe<00:17:33.299> grief<00:17:33.780> you<00:17:33.960> so 00:17:34.190 --> 00:17:34.200 align:start position:0% um the Guardians can maybe grief you so 00:17:34.200 --> 00:17:35.690 align:start position:0% um the Guardians can maybe grief you so that's<00:17:34.440> your<00:17:34.559> catastrophic<00:17:35.160> loss<00:17:35.520> the 00:17:35.690 --> 00:17:35.700 align:start position:0% that's your catastrophic loss the 00:17:35.700 --> 00:17:37.430 align:start position:0% that's your catastrophic loss the guidance<00:17:36.059> can<00:17:36.240> just<00:17:36.419> refuse<00:17:36.780> to<00:17:36.960> return<00:17:37.140> their 00:17:37.430 --> 00:17:37.440 align:start position:0% guidance can just refuse to return their 00:17:37.440 --> 00:17:38.810 align:start position:0% guidance can just refuse to return their shares<00:17:37.679> to<00:17:37.799> you<00:17:37.919> unless<00:17:38.280> you<00:17:38.400> pay<00:17:38.520> them<00:17:38.700> an 00:17:38.810 --> 00:17:38.820 align:start position:0% shares to you unless you pay them an 00:17:38.820 --> 00:17:40.310 align:start position:0% shares to you unless you pay them an exorbitant<00:17:39.299> fee 00:17:40.310 --> 00:17:40.320 align:start position:0% exorbitant fee 00:17:40.320 --> 00:17:42.529 align:start position:0% exorbitant fee um<00:17:40.380> it's<00:17:40.559> also<00:17:40.799> a<00:17:40.860> problem<00:17:41.039> of<00:17:41.400> how<00:17:42.179> should<00:17:42.419> the 00:17:42.529 --> 00:17:42.539 align:start position:0% um it's also a problem of how should the 00:17:42.539 --> 00:17:44.990 align:start position:0% um it's also a problem of how should the Guardians<00:17:43.020> know<00:17:43.320> when<00:17:43.740> what's<00:17:44.220> the<00:17:44.460> key<00:17:44.580> and 00:17:44.990 --> 00:17:45.000 align:start position:0% Guardians know when what's the key and 00:17:45.000 --> 00:17:46.730 align:start position:0% Guardians know when what's the key and return<00:17:45.120> the<00:17:45.360> shares<00:17:45.720> to<00:17:45.840> you<00:17:45.960> so<00:17:46.500> these<00:17:46.679> are 00:17:46.730 --> 00:17:46.740 align:start position:0% return the shares to you so these are 00:17:46.740 --> 00:17:49.190 align:start position:0% return the shares to you so these are some<00:17:46.799> open<00:17:47.039> problems<00:17:47.460> we're<00:17:47.580> exploring 00:17:49.190 --> 00:17:49.200 align:start position:0% some open problems we're exploring 00:17:49.200 --> 00:17:50.870 align:start position:0% some open problems we're exploring so<00:17:49.679> that's<00:17:49.860> all<00:17:50.039> thank<00:17:50.400> you<00:17:50.520> very<00:17:50.640> much<00:17:50.700> for 00:17:50.870 --> 00:17:50.880 align:start position:0% so that's all thank you very much for 00:17:50.880 --> 00:17:52.850 align:start position:0% so that's all thank you very much for coming<00:17:51.059> to<00:17:51.240> my<00:17:51.360> talk 00:17:52.850 --> 00:17:52.860 align:start position:0% coming to my talk 00:17:52.860 --> 00:17:56.870 align:start position:0% coming to my talk thank<00:17:52.980> you 00:17:56.870 --> 00:17:56.880 align:start position:0% 00:17:56.880 --> 00:18:00.049 align:start position:0% hello<00:17:57.360> I<00:17:58.080> think<00:17:58.200> I'm<00:17:58.320> a<00:17:58.380> bit<00:17:58.500> early<00:17:58.679> so<00:17:59.760> um<00:17:59.820> does 00:18:00.049 --> 00:18:00.059 align:start position:0% hello I think I'm a bit early so um does 00:18:00.059 --> 00:18:02.990 align:start position:0% hello I think I'm a bit early so um does anyone<00:18:00.360> have<00:18:00.419> any<00:18:00.539> questions 00:18:02.990 --> 00:18:03.000 align:start position:0% 00:18:03.000 --> 00:18:06.590 align:start position:0% yes<00:18:03.539> go<00:18:03.780> ahead 00:18:06.590 --> 00:18:06.600 align:start position:0% 00:18:06.600 --> 00:18:08.990 align:start position:0% hello<00:18:07.140> oh<00:18:07.559> hi 00:18:08.990 --> 00:18:09.000 align:start position:0% hello oh hi 00:18:09.000 --> 00:18:11.390 align:start position:0% hello oh hi um<00:18:09.120> so<00:18:09.480> the<00:18:09.900> time<00:18:10.080> locked<00:18:10.500> piece<00:18:10.799> is<00:18:11.039> a<00:18:11.160> bit<00:18:11.280> of 00:18:11.390 --> 00:18:11.400 align:start position:0% um so the time locked piece is a bit of 00:18:11.400 --> 00:18:14.150 align:start position:0% um so the time locked piece is a bit of a<00:18:11.640> magic<00:18:11.940> box<00:18:12.539> that<00:18:12.960> just<00:18:13.200> works<00:18:13.620> are<00:18:13.980> there 00:18:14.150 --> 00:18:14.160 align:start position:0% a magic box that just works are there 00:18:14.160 --> 00:18:17.110 align:start position:0% a magic box that just works are there any<00:18:14.280> like<00:18:14.520> practical<00:18:15.000> algorithms<00:18:15.840> yeah 00:18:17.110 --> 00:18:17.120 align:start position:0% any like practical algorithms yeah 00:18:17.120 --> 00:18:19.430 align:start position:0% any like practical algorithms yeah just<00:18:18.120> that<00:18:18.480> I've 00:18:19.430 --> 00:18:19.440 align:start position:0% just that I've 00:18:19.440 --> 00:18:21.710 align:start position:0% just that I've um I<00:18:19.860> need<00:18:19.980> the 00:18:21.710 --> 00:18:21.720 align:start position:0% um I need the 00:18:21.720 --> 00:18:24.409 align:start position:0% um I need the oh<00:18:22.140> mistake<00:18:22.799> anyway<00:18:23.039> but<00:18:23.700> anyway<00:18:23.880> if<00:18:24.179> you<00:18:24.299> go 00:18:24.409 --> 00:18:24.419 align:start position:0% oh mistake anyway but anyway if you go 00:18:24.419 --> 00:18:25.789 align:start position:0% oh mistake anyway but anyway if you go check<00:18:24.539> out<00:18:24.660> slides<00:18:25.020> online<00:18:25.140> they<00:18:25.440> said<00:18:25.620> just 00:18:25.789 --> 00:18:25.799 align:start position:0% check out slides online they said just 00:18:25.799 --> 00:18:28.310 align:start position:0% check out slides online they said just uh<00:18:26.100> it's<00:18:26.640> implemented<00:18:27.179> in<00:18:27.600> JavaScript<00:18:28.020> so 00:18:28.310 --> 00:18:28.320 align:start position:0% uh it's implemented in JavaScript so 00:18:28.320 --> 00:18:32.990 align:start position:0% uh it's implemented in JavaScript so you're<00:18:28.380> running<00:18:28.700> faster<00:18:29.700> but<00:18:30.480> is<00:18:30.780> the<00:18:31.440> most 00:18:32.990 --> 00:18:33.000 align:start position:0% you're running faster but is the most 00:18:33.000 --> 00:18:35.450 align:start position:0% you're running faster but is the most um<00:18:33.120> far<00:18:33.480> the<00:18:33.960> most<00:18:34.080> common<00:18:34.980> and<00:18:35.280> simple 00:18:35.450 --> 00:18:35.460 align:start position:0% um far the most common and simple 00:18:35.460 --> 00:18:37.570 align:start position:0% um far the most common and simple algorithm<00:18:36.000> is<00:18:36.240> a<00:18:36.480> repeated<00:18:36.840> squaring 00:18:37.570 --> 00:18:37.580 align:start position:0% algorithm is a repeated squaring 00:18:37.580 --> 00:18:39.710 align:start position:0% algorithm is a repeated squaring algorithm<00:18:38.580> so<00:18:38.940> you<00:18:39.120> can<00:18:39.179> just<00:18:39.299> look<00:18:39.419> it<00:18:39.539> up 00:18:39.710 --> 00:18:39.720 align:start position:0% algorithm so you can just look it up 00:18:39.720 --> 00:18:43.250 align:start position:0% algorithm so you can just look it up it's<00:18:40.020> quite<00:18:40.380> popular<00:18:40.980> and<00:18:41.580> and<00:18:41.820> it<00:18:42.720> works<00:18:43.020> in 00:18:43.250 --> 00:18:43.260 align:start position:0% it's quite popular and and it works in 00:18:43.260 --> 00:18:45.049 align:start position:0% it's quite popular and and it works in this<00:18:43.380> case<00:18:43.620> yeah<00:18:43.980> it<00:18:44.220> was<00:18:44.340> for<00:18:44.520> just<00:18:44.640> this<00:18:44.880> use 00:18:45.049 --> 00:18:45.059 align:start position:0% this case yeah it was for just this use 00:18:45.059 --> 00:18:46.490 align:start position:0% this case yeah it was for just this use case<00:18:45.179> you<00:18:45.419> don't<00:18:45.539> need<00:18:45.660> anything<00:18:45.840> very 00:18:46.490 --> 00:18:46.500 align:start position:0% case you don't need anything very 00:18:46.500 --> 00:18:47.930 align:start position:0% case you don't need anything very complex 00:18:47.930 --> 00:18:47.940 align:start position:0% complex 00:18:47.940 --> 00:18:50.330 align:start position:0% complex uh<00:18:48.720> yes<00:18:48.960> it's<00:18:49.200> Asic<00:18:49.559> resistant<00:18:49.919> in<00:18:50.160> a<00:18:50.220> sense 00:18:50.330 --> 00:18:50.340 align:start position:0% uh yes it's Asic resistant in a sense 00:18:50.340 --> 00:18:52.250 align:start position:0% uh yes it's Asic resistant in a sense that<00:18:50.460> it<00:18:50.640> requires<00:18:51.000> sequential<00:18:51.539> steps<00:18:51.900> you 00:18:52.250 --> 00:18:52.260 align:start position:0% that it requires sequential steps you 00:18:52.260 --> 00:18:55.070 align:start position:0% that it requires sequential steps you can't<00:18:52.320> paralyze<00:18:52.980> it<00:18:53.100> so<00:18:54.480> um 00:18:55.070 --> 00:18:55.080 align:start position:0% can't paralyze it so um 00:18:55.080 --> 00:18:57.289 align:start position:0% can't paralyze it so um you<00:18:55.740> could<00:18:55.860> maybe<00:18:56.100> build<00:18:56.400> an<00:18:56.580> Asic<00:18:57.000> for 00:18:57.289 --> 00:18:57.299 align:start position:0% you could maybe build an Asic for 00:18:57.299 --> 00:18:59.510 align:start position:0% you could maybe build an Asic for squaring<00:18:57.960> but<00:18:58.440> it's<00:18:58.740> not<00:18:58.919> possible<00:18:59.280> to 00:18:59.510 --> 00:18:59.520 align:start position:0% squaring but it's not possible to 00:18:59.520 --> 00:19:01.370 align:start position:0% squaring but it's not possible to paralyze<00:19:00.059> the<00:19:00.179> computation<00:19:00.660> so<00:19:00.900> it's 00:19:01.370 --> 00:19:01.380 align:start position:0% paralyze the computation so it's 00:19:01.380 --> 00:19:03.650 align:start position:0% paralyze the computation so it's sequential<00:19:02.220> yeah 00:19:03.650 --> 00:19:03.660 align:start position:0% sequential yeah 00:19:03.660 --> 00:19:06.049 align:start position:0% sequential yeah any<00:19:04.140> other<00:19:04.320> questions<00:19:04.740> yes 00:19:06.049 --> 00:19:06.059 align:start position:0% any other questions yes 00:19:06.059 --> 00:19:09.350 align:start position:0% any other questions yes ah<00:19:06.660> okay<00:19:06.960> so<00:19:07.620> we're<00:19:08.340> considering<00:19:08.940> the 00:19:09.350 --> 00:19:09.360 align:start position:0% ah okay so we're considering the 00:19:09.360 --> 00:19:11.150 align:start position:0% ah okay so we're considering the scenario<00:19:09.720> the<00:19:09.960> whole<00:19:10.320> point<00:19:10.500> of<00:19:10.679> this<00:19:10.860> setup 00:19:11.150 --> 00:19:11.160 align:start position:0% scenario the whole point of this setup 00:19:11.160 --> 00:19:12.830 align:start position:0% scenario the whole point of this setup right<00:19:11.400> is<00:19:11.640> complex<00:19:12.000> but<00:19:12.240> the<00:19:12.360> whole<00:19:12.480> point<00:19:12.660> of 00:19:12.830 --> 00:19:12.840 align:start position:0% right is complex but the whole point of 00:19:12.840 --> 00:19:14.990 align:start position:0% right is complex but the whole point of this<00:19:12.960> is<00:19:13.260> to<00:19:13.679> protect<00:19:13.980> against<00:19:14.220> catastrophic 00:19:14.990 --> 00:19:15.000 align:start position:0% this is to protect against catastrophic 00:19:15.000 --> 00:19:17.330 align:start position:0% this is to protect against catastrophic loss<00:19:15.360> right<00:19:15.600> so<00:19:16.080> during<00:19:16.260> catastrophic<00:19:16.980> loss 00:19:17.330 --> 00:19:17.340 align:start position:0% loss right so during catastrophic loss 00:19:17.340 --> 00:19:19.789 align:start position:0% loss right so during catastrophic loss you're<00:19:18.000> going<00:19:18.179> to<00:19:18.360> have<00:19:18.600> this<00:19:18.900> issue<00:19:19.320> where 00:19:19.789 --> 00:19:19.799 align:start position:0% you're going to have this issue where 00:19:19.799 --> 00:19:22.549 align:start position:0% you're going to have this issue where you've<00:19:20.280> lost<00:19:20.520> basically<00:19:21.059> all<00:19:21.600> your<00:19:21.840> user<00:19:22.380> own 00:19:22.549 --> 00:19:22.559 align:start position:0% you've lost basically all your user own 00:19:22.559 --> 00:19:25.070 align:start position:0% you've lost basically all your user own factors<00:19:22.919> like<00:19:23.160> phone<00:19:23.340> and<00:19:23.580> laptop<00:19:23.960> the<00:19:24.960> email 00:19:25.070 --> 00:19:25.080 align:start position:0% factors like phone and laptop the email 00:19:25.080 --> 00:19:26.690 align:start position:0% factors like phone and laptop the email we're<00:19:25.440> just<00:19:25.620> assuming<00:19:25.919> it's<00:19:26.160> custodial 00:19:26.690 --> 00:19:26.700 align:start position:0% we're just assuming it's custodial 00:19:26.700 --> 00:19:28.549 align:start position:0% we're just assuming it's custodial there's<00:19:26.940> always<00:19:27.120> some<00:19:27.419> way<00:19:27.660> a<00:19:27.900> subpoena<00:19:28.320> the 00:19:28.549 --> 00:19:28.559 align:start position:0% there's always some way a subpoena the 00:19:28.559 --> 00:19:30.049 align:start position:0% there's always some way a subpoena the guy<00:19:28.679> you<00:19:28.860> know<00:19:28.980> there's<00:19:29.340> always<00:19:29.580> some<00:19:29.760> way<00:19:29.880> to 00:19:30.049 --> 00:19:30.059 align:start position:0% guy you know there's always some way to 00:19:30.059 --> 00:19:32.270 align:start position:0% guy you know there's always some way to get<00:19:30.120> it<00:19:30.299> but<00:19:30.780> what<00:19:31.080> what<00:19:31.320> might<00:19:31.559> happen<00:19:31.860> right 00:19:32.270 --> 00:19:32.280 align:start position:0% get it but what what might happen right 00:19:32.280 --> 00:19:33.409 align:start position:0% get it but what what might happen right is 00:19:33.409 --> 00:19:33.419 align:start position:0% is 00:19:33.419 --> 00:19:35.150 align:start position:0% is um<00:19:33.480> the<00:19:33.660> time<00:19:33.840> not<00:19:34.020> show<00:19:34.200> unlocked<00:19:34.679> but<00:19:34.860> the 00:19:35.150 --> 00:19:35.160 align:start position:0% um the time not show unlocked but the 00:19:35.160 --> 00:19:37.430 align:start position:0% um the time not show unlocked but the Guardians<00:19:35.700> knowing<00:19:36.480> that<00:19:37.140> you<00:19:37.320> didn't 00:19:37.430 --> 00:19:37.440 align:start position:0% Guardians knowing that you didn't 00:19:37.440 --> 00:19:39.230 align:start position:0% Guardians knowing that you didn't refresh<00:19:37.799> your<00:19:37.919> shares<00:19:38.220> have<00:19:38.520> now<00:19:38.700> detected 00:19:39.230 --> 00:19:39.240 align:start position:0% refresh your shares have now detected 00:19:39.240 --> 00:19:41.750 align:start position:0% refresh your shares have now detected that<00:19:39.780> you've<00:19:40.080> lost<00:19:40.260> your<00:19:40.679> factors<00:19:41.039> and<00:19:41.580> now 00:19:41.750 --> 00:19:41.760 align:start position:0% that you've lost your factors and now 00:19:41.760 --> 00:19:43.190 align:start position:0% that you've lost your factors and now they're<00:19:42.059> gonna<00:19:42.240> grieve<00:19:42.780> you<00:19:42.900> right<00:19:43.020> they're 00:19:43.190 --> 00:19:43.200 align:start position:0% they're gonna grieve you right they're 00:19:43.200 --> 00:19:45.049 align:start position:0% they're gonna grieve you right they're gonna<00:19:43.380> be<00:19:43.500> like<00:19:43.559> if<00:19:43.740> you<00:19:43.860> don't<00:19:43.980> pay<00:19:44.160> me<00:19:44.340> you 00:19:45.049 --> 00:19:45.059 align:start position:0% gonna be like if you don't pay me you 00:19:45.059 --> 00:19:46.549 align:start position:0% gonna be like if you don't pay me you know<00:19:45.120> half<00:19:45.360> of<00:19:45.600> what's<00:19:45.780> owned<00:19:46.320> by<00:19:46.380> this 00:19:46.549 --> 00:19:46.559 align:start position:0% know half of what's owned by this 00:19:46.559 --> 00:19:47.750 align:start position:0% know half of what's owned by this account<00:19:46.740> I'm<00:19:47.039> not<00:19:47.160> going<00:19:47.280> to<00:19:47.340> give<00:19:47.460> you<00:19:47.580> back 00:19:47.750 --> 00:19:47.760 align:start position:0% account I'm not going to give you back 00:19:47.760 --> 00:19:51.950 align:start position:0% account I'm not going to give you back the<00:19:47.880> shares<00:19:48.240> and<00:19:48.840> and<00:19:49.080> this<00:19:49.440> is<00:19:49.940> extra<00:19:50.960> extra 00:19:51.950 --> 00:19:51.960 align:start position:0% the shares and and this is extra extra 00:19:51.960 --> 00:19:54.049 align:start position:0% the shares and and this is extra extra challenging<00:19:52.620> hero<00:19:52.919> because<00:19:53.100> you<00:19:53.640> only<00:19:53.760> need 00:19:54.049 --> 00:19:54.059 align:start position:0% challenging hero because you only need 00:19:54.059 --> 00:19:56.210 align:start position:0% challenging hero because you only need one<00:19:54.299> Garden<00:19:54.480> to<00:19:54.840> grieve<00:19:55.200> since<00:19:55.500> there<00:19:55.799> is<00:19:55.980> no 00:19:56.210 --> 00:19:56.220 align:start position:0% one Garden to grieve since there is no 00:19:56.220 --> 00:19:58.370 align:start position:0% one Garden to grieve since there is no redundancy<00:19:56.940> here<00:19:57.120> yeah<00:19:57.660> so<00:19:57.840> there's<00:19:58.020> one<00:19:58.200> one 00:19:58.370 --> 00:19:58.380 align:start position:0% redundancy here yeah so there's one one 00:19:58.380 --> 00:20:01.430 align:start position:0% redundancy here yeah so there's one one problem<00:19:58.679> there's<00:19:59.100> an<00:19:59.280> open<00:19:59.340> problem<00:19:59.640> to<00:19:59.940> solve 00:20:01.430 --> 00:20:01.440 align:start position:0% problem there's an open problem to solve 00:20:01.440 --> 00:20:04.130 align:start position:0% problem there's an open problem to solve any<00:20:01.919> other<00:20:02.100> questions 00:20:04.130 --> 00:20:04.140 align:start position:0% any other questions 00:20:04.140 --> 00:20:06.350 align:start position:0% any other questions go<00:20:04.559> ahead<00:20:04.679> yeah 00:20:06.350 --> 00:20:06.360 align:start position:0% go ahead yeah 00:20:06.360 --> 00:20:08.029 align:start position:0% go ahead yeah um<00:20:06.419> someone<00:20:06.600> not<00:20:06.960> deleting<00:20:07.380> a<00:20:07.559> share<00:20:07.799> and 00:20:08.029 --> 00:20:08.039 align:start position:0% um someone not deleting a share and 00:20:08.039 --> 00:20:11.330 align:start position:0% um someone not deleting a share and someone<00:20:08.340> keeping<00:20:09.059> the<00:20:09.360> share 00:20:11.330 --> 00:20:11.340 align:start position:0% someone keeping the share 00:20:11.340 --> 00:20:13.630 align:start position:0% someone keeping the share um<00:20:11.460> the<00:20:11.700> problem<00:20:12.059> here<00:20:12.360> is<00:20:12.600> that<00:20:12.840> the<00:20:13.380> the 00:20:13.630 --> 00:20:13.640 align:start position:0% um the problem here is that the the 00:20:13.640 --> 00:20:16.250 align:start position:0% um the problem here is that the the actors<00:20:14.640> here<00:20:14.880> are<00:20:15.240> Dynamic<00:20:15.780> they're<00:20:16.020> not 00:20:16.250 --> 00:20:16.260 align:start position:0% actors here are Dynamic they're not 00:20:16.260 --> 00:20:20.270 align:start position:0% actors here are Dynamic they're not static<00:20:16.679> so<00:20:17.160> do<00:20:17.660> I<00:20:18.660> will<00:20:18.900> delete<00:20:19.380> my<00:20:19.740> share<00:20:19.980> if 00:20:20.270 --> 00:20:20.280 align:start position:0% static so do I will delete my share if 00:20:20.280 --> 00:20:22.070 align:start position:0% static so do I will delete my share if I'm<00:20:20.820> pretty<00:20:21.000> sure<00:20:21.179> you're<00:20:21.360> refreshed<00:20:21.900> right 00:20:22.070 --> 00:20:22.080 align:start position:0% I'm pretty sure you're refreshed right 00:20:22.080 --> 00:20:23.750 align:start position:0% I'm pretty sure you're refreshed right then<00:20:22.380> you're<00:20:22.620> not<00:20:22.740> going<00:20:22.919> to<00:20:23.100> be<00:20:23.340> you<00:20:23.640> haven't 00:20:23.750 --> 00:20:23.760 align:start position:0% then you're not going to be you haven't 00:20:23.760 --> 00:20:26.090 align:start position:0% then you're not going to be you haven't lost<00:20:23.940> your<00:20:24.120> account<00:20:24.299> so<00:20:25.140> my<00:20:25.679> share<00:20:25.919> is 00:20:26.090 --> 00:20:26.100 align:start position:0% lost your account so my share is 00:20:26.100 --> 00:20:27.950 align:start position:0% lost your account so my share is actually<00:20:26.220> worthless<00:20:26.640> but<00:20:27.120> when<00:20:27.299> I<00:20:27.480> do<00:20:27.539> detect 00:20:27.950 --> 00:20:27.960 align:start position:0% actually worthless but when I do detect 00:20:27.960 --> 00:20:29.450 align:start position:0% actually worthless but when I do detect right<00:20:28.140> maybe<00:20:28.380> you<00:20:28.679> have<00:20:28.860> no<00:20:28.980> on-check 00:20:29.450 --> 00:20:29.460 align:start position:0% right maybe you have no on-check 00:20:29.460 --> 00:20:31.909 align:start position:0% right maybe you have no on-check activity<00:20:29.820> for<00:20:30.059> like<00:20:30.539> um<00:20:30.539> like<00:20:30.960> three<00:20:31.500> weeks 00:20:31.909 --> 00:20:31.919 align:start position:0% activity for like um like three weeks 00:20:31.919 --> 00:20:34.610 align:start position:0% activity for like um like three weeks right<00:20:32.280> a<00:20:32.580> little<00:20:32.700> suspicious<00:20:33.240> three<00:20:33.539> weeks 00:20:34.610 --> 00:20:34.620 align:start position:0% right a little suspicious three weeks 00:20:34.620 --> 00:20:37.789 align:start position:0% right a little suspicious three weeks um<00:20:34.679> then<00:20:34.980> I'm<00:20:35.400> gonna<00:20:35.840> modify<00:20:36.840> my<00:20:37.080> behavior<00:20:37.440> in 00:20:37.789 --> 00:20:37.799 align:start position:0% um then I'm gonna modify my behavior in 00:20:37.799 --> 00:20:39.289 align:start position:0% um then I'm gonna modify my behavior in in<00:20:37.980> accordance<00:20:38.280> to<00:20:38.520> that<00:20:38.640> so<00:20:38.940> it's<00:20:39.059> kind<00:20:39.179> of 00:20:39.289 --> 00:20:39.299 align:start position:0% in accordance to that so it's kind of 00:20:39.299 --> 00:20:41.630 align:start position:0% in accordance to that so it's kind of hard<00:20:39.419> to<00:20:39.539> model<00:20:39.720> it<00:20:39.960> that<00:20:40.140> way<00:20:40.320> I<00:20:40.860> I<00:20:41.039> think<00:20:41.280> a 00:20:41.630 --> 00:20:41.640 align:start position:0% hard to model it that way I I think a 00:20:41.640 --> 00:20:43.250 align:start position:0% hard to model it that way I I think a much<00:20:41.940> more<00:20:42.120> comprehensive<00:20:42.720> way<00:20:42.900> to<00:20:43.080> think 00:20:43.250 --> 00:20:43.260 align:start position:0% much more comprehensive way to think 00:20:43.260 --> 00:20:44.750 align:start position:0% much more comprehensive way to think about<00:20:43.320> a<00:20:43.500> threat<00:20:43.740> model<00:20:43.919> is<00:20:44.280> to<00:20:44.400> think<00:20:44.580> about 00:20:44.750 --> 00:20:44.760 align:start position:0% about a threat model is to think about 00:20:44.760 --> 00:20:46.730 align:start position:0% about a threat model is to think about the<00:20:45.179> different<00:20:45.299> types<00:20:45.780> of<00:20:45.840> attacks<00:20:46.260> because 00:20:46.730 --> 00:20:46.740 align:start position:0% the different types of attacks because 00:20:46.740 --> 00:20:50.150 align:start position:0% the different types of attacks because the<00:20:47.520> number<00:20:47.700> of<00:20:47.940> ways<00:20:48.600> you<00:20:48.660> can<00:20:48.840> attack<00:20:48.960> is<00:20:49.440> uh 00:20:50.150 --> 00:20:50.160 align:start position:0% the number of ways you can attack is uh 00:20:50.160 --> 00:20:51.470 align:start position:0% the number of ways you can attack is uh limited<00:20:50.580> since<00:20:50.820> there<00:20:51.059> isn't<00:20:51.360> much 00:20:51.470 --> 00:20:51.480 align:start position:0% limited since there isn't much 00:20:51.480 --> 00:20:53.150 align:start position:0% limited since there isn't much interaction<00:20:51.900> between<00:20:52.260> the<00:20:52.620> parties<00:20:52.919> it's 00:20:53.150 --> 00:20:53.160 align:start position:0% interaction between the parties it's 00:20:53.160 --> 00:20:56.450 align:start position:0% interaction between the parties it's really<00:20:53.400> just<00:20:53.760> about<00:20:54.059> factors<00:20:54.660> yeah 00:20:56.450 --> 00:20:56.460 align:start position:0% really just about factors yeah 00:20:56.460 --> 00:21:02.289 align:start position:0% really just about factors yeah any<00:20:56.940> other<00:20:57.179> questions 00:21:02.289 --> 00:21:02.299 align:start position:0% 00:21:02.299 --> 00:21:05.300 align:start position:0% all<00:21:03.299> right<00:21:03.419> thank<00:21:03.960> you<00:21:04.080> very<00:21:04.320> much 00:21:05.300 --> 00:21:05.310 align:start position:0% all right thank you very much 00:21:05.310 --> 00:21:09.170 align:start position:0% all right thank you very much [Applause]