WEBVTT Kind: captions Language: en 00:00:01.160 --> 00:00:06.690 align:start position:0% [Music] 00:00:06.690 --> 00:00:06.700 align:start position:0% 00:00:06.700 --> 00:00:09.070 align:start position:0% [Music] 00:00:09.070 --> 00:00:09.080 align:start position:0% [Music] 00:00:09.080 --> 00:00:11.230 align:start position:0% [Music] and<00:00:09.200> I<00:00:09.320> also<00:00:09.519> lead<00:00:09.880> the<00:00:10.400> uh<00:00:10.519> War<00:00:10.800> Games 00:00:11.230 --> 00:00:11.240 align:start position:0% and I also lead the uh War Games 00:00:11.240 --> 00:00:13.470 align:start position:0% and I also lead the uh War Games Initiative<00:00:11.679> for<00:00:11.920> the<00:00:12.040> security<00:00:12.440> Alliance<00:00:13.360> um 00:00:13.470 --> 00:00:13.480 align:start position:0% Initiative for the security Alliance um 00:00:13.480 --> 00:00:15.350 align:start position:0% Initiative for the security Alliance um I'll<00:00:13.639> give<00:00:13.759> a<00:00:13.960> brief<00:00:14.360> introduction<00:00:14.879> to<00:00:15.160> just 00:00:15.350 --> 00:00:15.360 align:start position:0% I'll give a brief introduction to just 00:00:15.360 --> 00:00:16.870 align:start position:0% I'll give a brief introduction to just what<00:00:15.480> the<00:00:15.599> security<00:00:16.039> Alliance<00:00:16.440> is<00:00:16.600> and<00:00:16.760> what 00:00:16.870 --> 00:00:16.880 align:start position:0% what the security Alliance is and what 00:00:16.880 --> 00:00:18.910 align:start position:0% what the security Alliance is and what the<00:00:17.000> various<00:00:17.439> initiatives<00:00:17.920> are<00:00:18.520> um<00:00:18.640> because<00:00:18.840> I 00:00:18.910 --> 00:00:18.920 align:start position:0% the various initiatives are um because I 00:00:18.920 --> 00:00:20.390 align:start position:0% the various initiatives are um because I think<00:00:19.039> it's<00:00:19.240> actually<00:00:19.439> pretty<00:00:19.720> relevant<00:00:20.160> also 00:00:20.390 --> 00:00:20.400 align:start position:0% think it's actually pretty relevant also 00:00:20.400 --> 00:00:22.429 align:start position:0% think it's actually pretty relevant also after<00:00:20.600> the<00:00:20.720> first<00:00:21.000> talk<00:00:21.600> um<00:00:21.720> about<00:00:21.920> ens<00:00:22.279> and 00:00:22.429 --> 00:00:22.439 align:start position:0% after the first talk um about ens and 00:00:22.439 --> 00:00:24.750 align:start position:0% after the first talk um about ens and data<00:00:22.680> sharing<00:00:23.560> and<00:00:23.640> so<00:00:23.760> the<00:00:23.880> top<00:00:24.160> initiative 00:00:24.750 --> 00:00:24.760 align:start position:0% data sharing and so the top initiative 00:00:24.760 --> 00:00:26.509 align:start position:0% data sharing and so the top initiative here<00:00:25.000> is<00:00:25.160> actually<00:00:25.400> called<00:00:25.560> the<00:00:25.680> seal<00:00:26.080> ISAC 00:00:26.509 --> 00:00:26.519 align:start position:0% here is actually called the seal ISAC 00:00:26.519 --> 00:00:28.589 align:start position:0% here is actually called the seal ISAC which<00:00:26.599> is<00:00:26.760> not<00:00:27.000> me<00:00:27.240> I'm<00:00:27.359> seal<00:00:27.720> Isaac<00:00:28.359> this<00:00:28.480> is 00:00:28.589 --> 00:00:28.599 align:start position:0% which is not me I'm seal Isaac this is 00:00:28.599 --> 00:00:32.190 align:start position:0% which is not me I'm seal Isaac this is the<00:00:28.840> information<00:00:29.840> uh<00:00:30.160> uh<00:00:30.840> security<00:00:31.800> something 00:00:32.190 --> 00:00:32.200 align:start position:0% the information uh uh security something 00:00:32.200 --> 00:00:34.310 align:start position:0% the information uh uh security something something<00:00:32.520> which<00:00:32.680> basically<00:00:33.040> this<00:00:33.120> is<00:00:33.320> like<00:00:33.520> a 00:00:34.310 --> 00:00:34.320 align:start position:0% something which basically this is like a 00:00:34.320 --> 00:00:36.950 align:start position:0% something which basically this is like a uh<00:00:34.600> a<00:00:35.360> shared<00:00:35.840> database<00:00:36.320> between<00:00:36.719> many 00:00:36.950 --> 00:00:36.960 align:start position:0% uh a shared database between many 00:00:36.960 --> 00:00:38.590 align:start position:0% uh a shared database between many different<00:00:37.200> companies<00:00:37.520> where<00:00:37.680> they<00:00:37.760> can<00:00:37.960> share 00:00:38.590 --> 00:00:38.600 align:start position:0% different companies where they can share 00:00:38.600 --> 00:00:42.029 align:start position:0% different companies where they can share data<00:00:38.960> on<00:00:39.719> uh<00:00:39.879> like<00:00:40.000> dprk<00:00:40.760> threat<00:00:41.120> actors<00:00:41.840> or 00:00:42.029 --> 00:00:42.039 align:start position:0% data on uh like dprk threat actors or 00:00:42.039 --> 00:00:44.270 align:start position:0% data on uh like dprk threat actors or fishing<00:00:42.440> data<00:00:42.760> or<00:00:42.960> bad<00:00:43.160> domains<00:00:44.000> um<00:00:44.120> there's 00:00:44.270 --> 00:00:44.280 align:start position:0% fishing data or bad domains um there's 00:00:44.280 --> 00:00:45.709 align:start position:0% fishing data or bad domains um there's seal<00:00:44.559> war<00:00:44.760> games<00:00:45.000> which<00:00:45.079> is<00:00:45.200> the<00:00:45.280> initiative 00:00:45.709 --> 00:00:45.719 align:start position:0% seal war games which is the initiative 00:00:45.719 --> 00:00:48.029 align:start position:0% seal war games which is the initiative that<00:00:45.840> I<00:00:46.079> lead<00:00:46.399> where<00:00:46.879> uh<00:00:47.000> we<00:00:47.199> prepare<00:00:47.600> protocol 00:00:48.029 --> 00:00:48.039 align:start position:0% that I lead where uh we prepare protocol 00:00:48.039 --> 00:00:50.069 align:start position:0% that I lead where uh we prepare protocol teams<00:00:48.280> for<00:00:48.480> incident<00:00:48.879> response<00:00:49.360> through<00:00:49.879> both 00:00:50.069 --> 00:00:50.079 align:start position:0% teams for incident response through both 00:00:50.079 --> 00:00:51.830 align:start position:0% teams for incident response through both tabletop<00:00:50.640> simulations<00:00:51.239> and<00:00:51.399> then<00:00:51.559> live 00:00:51.830 --> 00:00:51.840 align:start position:0% tabletop simulations and then live 00:00:51.840 --> 00:00:53.950 align:start position:0% tabletop simulations and then live simulations<00:00:52.280> on<00:00:52.399> forked<00:00:52.800> environments<00:00:53.800> um 00:00:53.950 --> 00:00:53.960 align:start position:0% simulations on forked environments um 00:00:53.960 --> 00:00:55.709 align:start position:0% simulations on forked environments um seal<00:00:54.280> also<00:00:54.480> operates<00:00:54.840> seal<00:00:55.079> 911<00:00:55.600> the 00:00:55.709 --> 00:00:55.719 align:start position:0% seal also operates seal 911 the 00:00:55.719 --> 00:00:57.270 align:start position:0% seal also operates seal 911 the emergency<00:00:56.199> hotline<00:00:56.600> if<00:00:56.680> your<00:00:56.840> protocol<00:00:57.199> is 00:00:57.270 --> 00:00:57.280 align:start position:0% emergency hotline if your protocol is 00:00:57.280 --> 00:00:59.389 align:start position:0% emergency hotline if your protocol is under<00:00:57.600> attack<00:00:57.920> or<00:00:58.120> if<00:00:58.239> you<00:00:58.760> have<00:00:59.079> discovered<00:00:59.320> a 00:00:59.389 --> 00:00:59.399 align:start position:0% under attack or if you have discovered a 00:00:59.399 --> 00:01:01.150 align:start position:0% under attack or if you have discovered a vulnerability<00:01:00.120> a<00:01:00.239> protocol<00:01:00.680> and<00:01:00.760> need<00:01:00.920> to<00:01:01.039> get 00:01:01.150 --> 00:01:01.160 align:start position:0% vulnerability a protocol and need to get 00:01:01.160 --> 00:01:03.709 align:start position:0% vulnerability a protocol and need to get in<00:01:01.320> touch<00:01:01.680> with<00:01:02.199> um<00:01:02.320> a<00:01:02.480> security<00:01:02.920> expert<00:01:03.600> as 00:01:03.709 --> 00:01:03.719 align:start position:0% in touch with um a security expert as 00:01:03.719 --> 00:01:06.670 align:start position:0% in touch with um a security expert as fast<00:01:03.920> as<00:01:04.119> possible<00:01:05.119> um<00:01:05.320> The<00:01:05.479> Safe<00:01:05.799> Harbor<00:01:06.520> uh 00:01:06.670 --> 00:01:06.680 align:start position:0% fast as possible um The Safe Harbor uh 00:01:06.680 --> 00:01:08.990 align:start position:0% fast as possible um The Safe Harbor uh agreement<00:01:07.560> um<00:01:07.680> which<00:01:07.799> is<00:01:08.040> legal<00:01:08.400> protection 00:01:08.990 --> 00:01:09.000 align:start position:0% agreement um which is legal protection 00:01:09.000 --> 00:01:10.469 align:start position:0% agreement um which is legal protection if<00:01:09.080> you're<00:01:09.240> a<00:01:09.360> wh<00:01:09.640> hat<00:01:09.840> hacker<00:01:10.159> and<00:01:10.280> you're 00:01:10.469 --> 00:01:10.479 align:start position:0% if you're a wh hat hacker and you're 00:01:10.479 --> 00:01:12.350 align:start position:0% if you're a wh hat hacker and you're acting<00:01:10.759> benevolently<00:01:11.600> in<00:01:11.759> an<00:01:11.920> urgent 00:01:12.350 --> 00:01:12.360 align:start position:0% acting benevolently in an urgent 00:01:12.360 --> 00:01:14.789 align:start position:0% acting benevolently in an urgent situation<00:01:13.040> to<00:01:13.680> uh<00:01:13.799> rescue<00:01:14.200> funds<00:01:14.520> from<00:01:14.640> a 00:01:14.789 --> 00:01:14.799 align:start position:0% situation to uh rescue funds from a 00:01:14.799 --> 00:01:17.749 align:start position:0% situation to uh rescue funds from a protocol<00:01:15.560> think<00:01:16.520> uh<00:01:16.720> Nomad<00:01:17.159> Bridge<00:01:17.479> hack<00:01:17.680> a 00:01:17.749 --> 00:01:17.759 align:start position:0% protocol think uh Nomad Bridge hack a 00:01:17.759 --> 00:01:19.710 align:start position:0% protocol think uh Nomad Bridge hack a few<00:01:17.960> years<00:01:18.159> ago<00:01:18.400> if<00:01:18.520> you<00:01:18.560> were<00:01:18.720> trying<00:01:18.960> to<00:01:19.119> save 00:01:19.710 --> 00:01:19.720 align:start position:0% few years ago if you were trying to save 00:01:19.720 --> 00:01:21.870 align:start position:0% few years ago if you were trying to save uh<00:01:19.920> money<00:01:20.280> but<00:01:20.680> maybe<00:01:20.920> you<00:01:21.040> were<00:01:21.439> worried 00:01:21.870 --> 00:01:21.880 align:start position:0% uh money but maybe you were worried 00:01:21.880 --> 00:01:23.109 align:start position:0% uh money but maybe you were worried because<00:01:22.079> you<00:01:22.240> thought<00:01:22.400> that<00:01:22.520> you'd<00:01:22.720> be<00:01:22.799> sued 00:01:23.109 --> 00:01:23.119 align:start position:0% because you thought that you'd be sued 00:01:23.119 --> 00:01:25.830 align:start position:0% because you thought that you'd be sued for<00:01:23.320> hacking<00:01:23.720> during<00:01:24.680> uh<00:01:24.920> because<00:01:25.159> you<00:01:25.360> it<00:01:25.600> be 00:01:25.830 --> 00:01:25.840 align:start position:0% for hacking during uh because you it be 00:01:25.840 --> 00:01:27.630 align:start position:0% for hacking during uh because you it be impossible<00:01:26.240> to<00:01:26.439> distinguish<00:01:27.159> the<00:01:27.280> white<00:01:27.520> hat 00:01:27.630 --> 00:01:27.640 align:start position:0% impossible to distinguish the white hat 00:01:27.640 --> 00:01:29.350 align:start position:0% impossible to distinguish the white hat Safe<00:01:27.880> Harbor<00:01:28.119> agreement<00:01:28.520> exists<00:01:28.840> to<00:01:29.000> protect 00:01:29.350 --> 00:01:29.360 align:start position:0% Safe Harbor agreement exists to protect 00:01:29.360 --> 00:01:31.590 align:start position:0% Safe Harbor agreement exists to protect white<00:01:29.640> hat<00:01:29.960> uh<00:01:30.119> hackers<00:01:31.079> uh<00:01:31.240> in<00:01:31.400> those 00:01:31.590 --> 00:01:31.600 align:start position:0% white hat uh hackers uh in those 00:01:31.600 --> 00:01:33.469 align:start position:0% white hat uh hackers uh in those situations<00:01:32.280> and<00:01:32.399> a<00:01:32.520> legal<00:01:32.799> defense<00:01:33.119> Fund<00:01:33.360> in 00:01:33.469 --> 00:01:33.479 align:start position:0% situations and a legal defense Fund in 00:01:33.479 --> 00:01:36.429 align:start position:0% situations and a legal defense Fund in case<00:01:33.640> they<00:01:33.759> sue<00:01:34.000> you<00:01:34.520> anyway<00:01:35.520> um<00:01:35.799> so<00:01:36.159> today 00:01:36.429 --> 00:01:36.439 align:start position:0% case they sue you anyway um so today 00:01:36.439 --> 00:01:37.950 align:start position:0% case they sue you anyway um so today what<00:01:36.560> we'll<00:01:36.720> talk<00:01:36.880> about<00:01:37.119> primarily<00:01:37.560> is<00:01:37.680> war 00:01:37.950 --> 00:01:37.960 align:start position:0% what we'll talk about primarily is war 00:01:37.960 --> 00:01:39.429 align:start position:0% what we'll talk about primarily is war games<00:01:38.200> so<00:01:38.399> what<00:01:38.520> are<00:01:38.640> these<00:01:38.799> war<00:01:39.000> games<00:01:39.200> and 00:01:39.429 --> 00:01:39.439 align:start position:0% games so what are these war games and 00:01:39.439 --> 00:01:41.389 align:start position:0% games so what are these war games and why<00:01:39.600> do<00:01:39.720> we<00:01:39.880> do<00:01:40.079> them<00:01:40.759> um<00:01:40.960> I'll<00:01:41.119> have<00:01:41.280> some 00:01:41.389 --> 00:01:41.399 align:start position:0% why do we do them um I'll have some 00:01:41.399 --> 00:01:43.149 align:start position:0% why do we do them um I'll have some links<00:01:41.680> to<00:01:41.840> resources<00:01:42.240> on<00:01:42.439> how<00:01:42.600> you<00:01:42.720> can<00:01:42.880> work 00:01:43.149 --> 00:01:43.159 align:start position:0% links to resources on how you can work 00:01:43.159 --> 00:01:44.749 align:start position:0% links to resources on how you can work with<00:01:43.320> us<00:01:43.720> uh<00:01:43.799> there's<00:01:43.960> a<00:01:44.040> lot<00:01:44.159> of<00:01:44.280> open<00:01:44.560> source 00:01:44.749 --> 00:01:44.759 align:start position:0% with us uh there's a lot of open source 00:01:44.759 --> 00:01:47.550 align:start position:0% with us uh there's a lot of open source toolkits<00:01:45.240> and<00:01:45.360> we<00:01:45.520> also<00:01:45.880> run<00:01:46.159> these<00:01:46.920> um<00:01:47.200> as<00:01:47.320> a 00:01:47.550 --> 00:01:47.560 align:start position:0% toolkits and we also run these um as a 00:01:47.560 --> 00:01:49.550 align:start position:0% toolkits and we also run these um as a as<00:01:47.680> like<00:01:47.799> a<00:01:47.960> public<00:01:48.240> good<00:01:49.000> uh<00:01:49.119> throughout<00:01:49.439> the 00:01:49.550 --> 00:01:49.560 align:start position:0% as like a public good uh throughout the 00:01:49.560 --> 00:01:52.069 align:start position:0% as like a public good uh throughout the space<00:01:50.360> um<00:01:50.520> we'll<00:01:50.719> be<00:01:51.320> talking<00:01:51.640> through<00:01:51.880> some 00:01:52.069 --> 00:01:52.079 align:start position:0% space um we'll be talking through some 00:01:52.079 --> 00:01:53.749 align:start position:0% space um we'll be talking through some best<00:01:52.360> practices<00:01:52.840> that<00:01:53.040> I've<00:01:53.240> learned<00:01:53.600> from 00:01:53.749 --> 00:01:53.759 align:start position:0% best practices that I've learned from 00:01:53.759 --> 00:01:55.830 align:start position:0% best practices that I've learned from working<00:01:54.119> with<00:01:54.240> some<00:01:54.399> of<00:01:54.560> the<00:01:55.159> major<00:01:55.439> protocols 00:01:55.830 --> 00:01:55.840 align:start position:0% working with some of the major protocols 00:01:55.840 --> 00:01:57.789 align:start position:0% working with some of the major protocols in<00:01:55.920> the<00:01:56.119> ecosystem<00:01:57.119> um<00:01:57.240> and<00:01:57.360> then<00:01:57.520> just 00:01:57.789 --> 00:01:57.799 align:start position:0% in the ecosystem um and then just 00:01:57.799 --> 00:01:59.429 align:start position:0% in the ecosystem um and then just briefly<00:01:58.119> show<00:01:58.360> you<00:01:58.560> what<00:01:58.680> this<00:01:58.840> new<00:01:59.000> toolkit 00:01:59.429 --> 00:01:59.439 align:start position:0% briefly show you what this new toolkit 00:01:59.439 --> 00:02:00.950 align:start position:0% briefly show you what this new toolkit is<00:01:59.520> that<00:01:59.640> we<00:01:59.920> released<00:02:00.240> so<00:02:00.360> you<00:02:00.439> can<00:02:00.560> run<00:02:00.759> these 00:02:00.950 --> 00:02:00.960 align:start position:0% is that we released so you can run these 00:02:00.960 --> 00:02:03.709 align:start position:0% is that we released so you can run these yourself<00:02:01.759> uh<00:02:01.880> if<00:02:01.960> you<00:02:02.039> would<00:02:02.280> like<00:02:03.280> so<00:02:03.600> what 00:02:03.709 --> 00:02:03.719 align:start position:0% yourself uh if you would like so what 00:02:03.719 --> 00:02:05.429 align:start position:0% yourself uh if you would like so what are<00:02:03.880> war<00:02:04.119> games<00:02:04.399> these<00:02:04.479> are<00:02:04.719> cyber<00:02:05.000> secur 00:02:05.429 --> 00:02:05.439 align:start position:0% are war games these are cyber secur 00:02:05.439 --> 00:02:08.469 align:start position:0% are war games these are cyber secur exercises<00:02:06.039> for<00:02:06.280> web<00:02:06.560> 3<00:02:07.320> um<00:02:07.479> I've<00:02:07.600> heard<00:02:08.319> uh 00:02:08.469 --> 00:02:08.479 align:start position:0% exercises for web 3 um I've heard uh 00:02:08.479 --> 00:02:09.949 align:start position:0% exercises for web 3 um I've heard uh traditional<00:02:08.920> cyber<00:02:09.200> security<00:02:09.520> folks<00:02:09.759> call 00:02:09.949 --> 00:02:09.959 align:start position:0% traditional cyber security folks call 00:02:09.959 --> 00:02:11.270 align:start position:0% traditional cyber security folks call these<00:02:10.160> something<00:02:10.479> like<00:02:10.560> a<00:02:10.679> purple<00:02:10.959> team 00:02:11.270 --> 00:02:11.280 align:start position:0% these something like a purple team 00:02:11.280 --> 00:02:12.790 align:start position:0% these something like a purple team exercise<00:02:11.720> where<00:02:11.879> we're<00:02:12.040> not<00:02:12.239> exactly<00:02:12.599> red 00:02:12.790 --> 00:02:12.800 align:start position:0% exercise where we're not exactly red 00:02:12.800 --> 00:02:14.670 align:start position:0% exercise where we're not exactly red team<00:02:13.120> blue<00:02:13.360> team<00:02:13.680> but<00:02:13.959> we're<00:02:14.160> basically<00:02:14.560> just 00:02:14.670 --> 00:02:14.680 align:start position:0% team blue team but we're basically just 00:02:14.680 --> 00:02:16.509 align:start position:0% team blue team but we're basically just trying<00:02:14.920> to<00:02:15.080> stress<00:02:15.440> test<00:02:15.640> these<00:02:15.879> teams<00:02:16.080> and 00:02:16.509 --> 00:02:16.519 align:start position:0% trying to stress test these teams and 00:02:16.519 --> 00:02:18.070 align:start position:0% trying to stress test these teams and understand<00:02:16.760> how<00:02:16.920> they<00:02:17.080> behave<00:02:17.760> under 00:02:18.070 --> 00:02:18.080 align:start position:0% understand how they behave under 00:02:18.080 --> 00:02:20.470 align:start position:0% understand how they behave under pressure<00:02:18.800> and<00:02:18.920> so<00:02:19.080> we<00:02:19.200> want<00:02:19.480> to<00:02:19.800> help<00:02:20.040> teams 00:02:20.470 --> 00:02:20.480 align:start position:0% pressure and so we want to help teams 00:02:20.480 --> 00:02:22.509 align:start position:0% pressure and so we want to help teams practice<00:02:20.840> for<00:02:21.160> these<00:02:21.760> um<00:02:21.920> high<00:02:22.160> pressure 00:02:22.509 --> 00:02:22.519 align:start position:0% practice for these um high pressure 00:02:22.519 --> 00:02:24.790 align:start position:0% practice for these um high pressure situations<00:02:23.120> before<00:02:23.360> they<00:02:23.560> actually<00:02:23.959> happen 00:02:24.790 --> 00:02:24.800 align:start position:0% situations before they actually happen 00:02:24.800 --> 00:02:26.430 align:start position:0% situations before they actually happen um<00:02:24.920> we<00:02:25.040> want<00:02:25.200> to<00:02:25.319> be<00:02:25.400> able<00:02:25.560> to<00:02:25.680> like<00:02:25.879> test<00:02:26.239> both 00:02:26.430 --> 00:02:26.440 align:start position:0% um we want to be able to like test both 00:02:26.440 --> 00:02:28.070 align:start position:0% um we want to be able to like test both the<00:02:26.599> technical<00:02:27.080> side<00:02:27.239> of<00:02:27.360> their<00:02:27.519> team<00:02:27.920> and 00:02:28.070 --> 00:02:28.080 align:start position:0% the technical side of their team and 00:02:28.080 --> 00:02:29.990 align:start position:0% the technical side of their team and their<00:02:28.280> social<00:02:28.640> resilience<00:02:29.400> and<00:02:29.480> we're<00:02:29.599> not 00:02:29.990 --> 00:02:30.000 align:start position:0% their social resilience and we're not 00:02:30.000 --> 00:02:31.430 align:start position:0% their social resilience and we're not just<00:02:30.120> trying<00:02:30.360> to<00:02:30.480> help<00:02:30.760> like<00:02:30.879> cause<00:02:31.120> them<00:02:31.239> to 00:02:31.430 --> 00:02:31.440 align:start position:0% just trying to help like cause them to 00:02:31.440 --> 00:02:32.750 align:start position:0% just trying to help like cause them to panic<00:02:31.720> but<00:02:31.840> we<00:02:31.959> want<00:02:32.080> them<00:02:32.200> to<00:02:32.400> practice 00:02:32.750 --> 00:02:32.760 align:start position:0% panic but we want them to practice 00:02:32.760 --> 00:02:35.910 align:start position:0% panic but we want them to practice emergency<00:02:33.280> response<00:02:34.120> um<00:02:34.280> a<00:02:34.400> lot<00:02:34.519> of<00:02:34.760> the<00:02:35.519> uh<00:02:35.840> a 00:02:35.910 --> 00:02:35.920 align:start position:0% emergency response um a lot of the uh a 00:02:35.920 --> 00:02:37.470 align:start position:0% emergency response um a lot of the uh a lot<00:02:36.040> of<00:02:36.160> the<00:02:36.239> reason<00:02:36.560> why<00:02:36.720> we<00:02:36.800> started<00:02:37.080> doing 00:02:37.470 --> 00:02:37.480 align:start position:0% lot of the reason why we started doing 00:02:37.480 --> 00:02:40.110 align:start position:0% lot of the reason why we started doing this<00:02:38.080> um<00:02:38.239> was<00:02:38.400> a<00:02:38.560> few<00:02:38.760> years<00:02:39.000> ago<00:02:39.720> um<00:02:39.840> so<00:02:40.000> the 00:02:40.110 --> 00:02:40.120 align:start position:0% this um was a few years ago um so the 00:02:40.120 --> 00:02:42.030 align:start position:0% this um was a few years ago um so the security<00:02:40.440> lines<00:02:40.720> was<00:02:40.840> started<00:02:41.120> by<00:02:41.239> Sam<00:02:41.519> sun 00:02:42.030 --> 00:02:42.040 align:start position:0% security lines was started by Sam sun 00:02:42.040 --> 00:02:43.710 align:start position:0% security lines was started by Sam sun and<00:02:42.159> he<00:02:42.280> was<00:02:42.400> pulled<00:02:42.640> into<00:02:42.840> so<00:02:43.000> many<00:02:43.159> War<00:02:43.400> rooms 00:02:43.710 --> 00:02:43.720 align:start position:0% and he was pulled into so many War rooms 00:02:43.720 --> 00:02:47.149 align:start position:0% and he was pulled into so many War rooms where<00:02:43.840> it<00:02:43.959> seemed<00:02:44.879> uh<00:02:45.159> like<00:02:45.720> I<00:02:45.879> guess<00:02:46.040> in<00:02:46.640> uh<00:02:47.040> uh 00:02:47.149 --> 00:02:47.159 align:start position:0% where it seemed uh like I guess in uh uh 00:02:47.159 --> 00:02:48.790 align:start position:0% where it seemed uh like I guess in uh uh from<00:02:47.319> what<00:02:47.440> I've<00:02:47.599> heard<00:02:48.159> uh<00:02:48.280> teams<00:02:48.599> just 00:02:48.790 --> 00:02:48.800 align:start position:0% from what I've heard uh teams just 00:02:48.800 --> 00:02:50.390 align:start position:0% from what I've heard uh teams just completely<00:02:49.120> melting<00:02:49.560> down<00:02:49.840> and<00:02:50.000> not<00:02:50.159> really 00:02:50.390 --> 00:02:50.400 align:start position:0% completely melting down and not really 00:02:50.400 --> 00:02:52.589 align:start position:0% completely melting down and not really being<00:02:50.879> exactly<00:02:51.599> uh<00:02:51.760> prepared<00:02:52.120> for<00:02:52.280> what<00:02:52.360> would 00:02:52.589 --> 00:02:52.599 align:start position:0% being exactly uh prepared for what would 00:02:52.599 --> 00:02:54.270 align:start position:0% being exactly uh prepared for what would happen<00:02:53.000> so<00:02:53.200> what<00:02:53.319> could<00:02:53.440> we<00:02:53.599> actually<00:02:53.879> do<00:02:54.120> to 00:02:54.270 --> 00:02:54.280 align:start position:0% happen so what could we actually do to 00:02:54.280 --> 00:02:55.990 align:start position:0% happen so what could we actually do to help<00:02:54.480> put<00:02:54.599> them<00:02:54.720> in<00:02:54.879> that<00:02:55.040> situation<00:02:55.640> before 00:02:55.990 --> 00:02:56.000 align:start position:0% help put them in that situation before 00:02:56.000 --> 00:02:58.309 align:start position:0% help put them in that situation before that<00:02:56.200> inevitably<00:02:56.760> happens<00:02:57.560> um<00:02:57.640> so<00:02:57.800> War<00:02:58.040> Games 00:02:58.309 --> 00:02:58.319 align:start position:0% that inevitably happens um so War Games 00:02:58.319 --> 00:03:00.710 align:start position:0% that inevitably happens um so War Games take<00:02:58.519> place<00:02:58.760> through<00:02:59.040> three<00:02:59.280> phases<00:03:00.080> um<00:03:00.319> I<00:03:00.400> do 00:03:00.710 --> 00:03:00.720 align:start position:0% take place through three phases um I do 00:03:00.720 --> 00:03:02.910 align:start position:0% take place through three phases um I do a<00:03:00.840> lot<00:03:00.959> of<00:03:01.280> uh<00:03:01.760> uh<00:03:01.920> intelligence<00:03:02.519> gathering 00:03:02.910 --> 00:03:02.920 align:start position:0% a lot of uh uh intelligence gathering 00:03:02.920 --> 00:03:04.430 align:start position:0% a lot of uh uh intelligence gathering which<00:03:03.080> really<00:03:03.280> just<00:03:03.400> means<00:03:03.680> reading<00:03:04.120> every 00:03:04.430 --> 00:03:04.440 align:start position:0% which really just means reading every 00:03:04.440 --> 00:03:06.030 align:start position:0% which really just means reading every document<00:03:04.959> that<00:03:05.120> the<00:03:05.280> protocols<00:03:05.760> ever 00:03:06.030 --> 00:03:06.040 align:start position:0% document that the protocols ever 00:03:06.040 --> 00:03:08.110 align:start position:0% document that the protocols ever published<00:03:06.959> understand<00:03:07.120> their<00:03:07.319> contracts 00:03:08.110 --> 00:03:08.120 align:start position:0% published understand their contracts 00:03:08.120 --> 00:03:09.670 align:start position:0% published understand their contracts understand<00:03:08.239> how<00:03:08.360> it<00:03:08.519> works<00:03:09.200> uh<00:03:09.319> we<00:03:09.400> do<00:03:09.519> a 00:03:09.670 --> 00:03:09.680 align:start position:0% understand how it works uh we do a 00:03:09.680 --> 00:03:11.470 align:start position:0% understand how it works uh we do a tabletop<00:03:10.239> exercise<00:03:10.640> where<00:03:10.799> we<00:03:10.959> talk<00:03:11.200> through 00:03:11.470 --> 00:03:11.480 align:start position:0% tabletop exercise where we talk through 00:03:11.480 --> 00:03:13.630 align:start position:0% tabletop exercise where we talk through various<00:03:11.760> scenarios<00:03:12.239> with<00:03:12.400> them<00:03:12.959> um<00:03:13.120> and 00:03:13.630 --> 00:03:13.640 align:start position:0% various scenarios with them um and 00:03:13.640 --> 00:03:15.030 align:start position:0% various scenarios with them um and understand<00:03:13.959> how<00:03:14.159> they<00:03:14.280> would<00:03:14.440> have<00:03:14.599> detected 00:03:15.030 --> 00:03:15.040 align:start position:0% understand how they would have detected 00:03:15.040 --> 00:03:17.350 align:start position:0% understand how they would have detected them<00:03:15.400> what<00:03:15.519> they<00:03:15.640> would<00:03:15.879> do<00:03:16.159> who's<00:03:16.440> in<00:03:16.640> charge 00:03:17.350 --> 00:03:17.360 align:start position:0% them what they would do who's in charge 00:03:17.360 --> 00:03:18.430 align:start position:0% them what they would do who's in charge um<00:03:17.480> and<00:03:17.640> how<00:03:17.760> would<00:03:17.879> they<00:03:18.000> have<00:03:18.159> fixed 00:03:18.430 --> 00:03:18.440 align:start position:0% um and how would they have fixed 00:03:18.440 --> 00:03:20.229 align:start position:0% um and how would they have fixed something<00:03:19.080> and<00:03:19.239> then<00:03:19.480> what<00:03:19.720> I<00:03:19.799> think<00:03:19.959> is<00:03:20.120> the 00:03:20.229 --> 00:03:20.239 align:start position:0% something and then what I think is the 00:03:20.239 --> 00:03:21.990 align:start position:0% something and then what I think is the most<00:03:20.440> fun<00:03:20.599> is<00:03:20.720> we<00:03:20.840> do<00:03:20.959> a<00:03:21.080> live<00:03:21.319> simulation<00:03:21.879> so 00:03:21.990 --> 00:03:22.000 align:start position:0% most fun is we do a live simulation so 00:03:22.000 --> 00:03:24.190 align:start position:0% most fun is we do a live simulation so we<00:03:22.159> set<00:03:22.319> up<00:03:22.640> a<00:03:22.760> forked<00:03:23.159> environment<00:03:23.799> we<00:03:24.000> run 00:03:24.190 --> 00:03:24.200 align:start position:0% we set up a forked environment we run 00:03:24.200 --> 00:03:25.670 align:start position:0% we set up a forked environment we run all<00:03:24.319> of<00:03:24.440> their<00:03:24.640> contracts<00:03:25.120> we<00:03:25.239> run<00:03:25.480> all<00:03:25.560> of 00:03:25.670 --> 00:03:25.680 align:start position:0% all of their contracts we run all of 00:03:25.680 --> 00:03:28.229 align:start position:0% all of their contracts we run all of their<00:03:25.840> uis<00:03:26.519> we<00:03:26.640> run<00:03:26.840> all<00:03:26.959> of<00:03:27.080> their<00:03:27.239> monitoring 00:03:28.229 --> 00:03:28.239 align:start position:0% their uis we run all of their monitoring 00:03:28.239 --> 00:03:30.070 align:start position:0% their uis we run all of their monitoring um<00:03:28.439> and<00:03:28.599> then<00:03:28.879> they<00:03:29.040> actually<00:03:29.239> have<00:03:29.319> to<00:03:29.480> coord 00:03:30.070 --> 00:03:30.080 align:start position:0% um and then they actually have to coord 00:03:30.080 --> 00:03:33.270 align:start position:0% um and then they actually have to coord in<00:03:30.239> real<00:03:30.560> time<00:03:30.920> to<00:03:31.560> uh<00:03:32.120> uh<00:03:32.239> defend<00:03:32.680> and<00:03:32.879> respond 00:03:33.270 --> 00:03:33.280 align:start position:0% in real time to uh uh defend and respond 00:03:33.280 --> 00:03:35.350 align:start position:0% in real time to uh uh defend and respond as<00:03:33.400> if<00:03:33.480> it<00:03:33.599> was<00:03:33.720> a<00:03:33.840> real<00:03:34.040> incident<00:03:34.720> and<00:03:34.879> we<00:03:35.159> tend 00:03:35.350 --> 00:03:35.360 align:start position:0% as if it was a real incident and we tend 00:03:35.360 --> 00:03:36.910 align:start position:0% as if it was a real incident and we tend to<00:03:35.519> find<00:03:35.760> a<00:03:35.879> lot<00:03:36.000> of<00:03:36.200> things<00:03:36.480> that<00:03:36.640> they<00:03:36.760> can 00:03:36.910 --> 00:03:36.920 align:start position:0% to find a lot of things that they can 00:03:36.920 --> 00:03:38.670 align:start position:0% to find a lot of things that they can improve<00:03:37.319> through<00:03:37.519> that<00:03:37.760> process<00:03:38.200> and<00:03:38.319> it<00:03:38.480> also 00:03:38.670 --> 00:03:38.680 align:start position:0% improve through that process and it also 00:03:38.680 --> 00:03:40.589 align:start position:0% improve through that process and it also just<00:03:38.840> helps<00:03:39.040> a<00:03:39.200> team<00:03:39.680> build<00:03:40.000> trust<00:03:40.239> in<00:03:40.439> each 00:03:40.589 --> 00:03:40.599 align:start position:0% just helps a team build trust in each 00:03:40.599 --> 00:03:42.309 align:start position:0% just helps a team build trust in each other<00:03:41.040> so<00:03:41.159> that<00:03:41.360> they<00:03:41.480> know<00:03:41.680> when<00:03:41.840> an<00:03:41.959> incident 00:03:42.309 --> 00:03:42.319 align:start position:0% other so that they know when an incident 00:03:42.319 --> 00:03:44.869 align:start position:0% other so that they know when an incident goes<00:03:42.480> down<00:03:42.680> for<00:03:42.879> real<00:03:43.360> I<00:03:43.439> can<00:03:43.599> trust<00:03:43.879> my<00:03:44.040> team 00:03:44.869 --> 00:03:44.879 align:start position:0% goes down for real I can trust my team 00:03:44.879 --> 00:03:48.550 align:start position:0% goes down for real I can trust my team uh<00:03:45.239> uh<00:03:45.319> to<00:03:45.439> be<00:03:46.040> there<00:03:47.040> so<00:03:47.720> a<00:03:47.840> big<00:03:48.040> reason<00:03:48.280> why<00:03:48.400> we 00:03:48.550 --> 00:03:48.560 align:start position:0% uh uh to be there so a big reason why we 00:03:48.560 --> 00:03:50.270 align:start position:0% uh uh to be there so a big reason why we do<00:03:48.760> this<00:03:48.959> is<00:03:49.120> because<00:03:49.360> more<00:03:49.519> and<00:03:49.680> more<00:03:49.959> hacks 00:03:50.270 --> 00:03:50.280 align:start position:0% do this is because more and more hacks 00:03:50.280 --> 00:03:52.350 align:start position:0% do this is because more and more hacks are<00:03:50.439> due<00:03:50.680> to<00:03:51.000> operational<00:03:51.560> failures<00:03:52.159> not 00:03:52.350 --> 00:03:52.360 align:start position:0% are due to operational failures not 00:03:52.360 --> 00:03:54.030 align:start position:0% are due to operational failures not smart<00:03:52.720> contract<00:03:53.040> bugs<00:03:53.400> that's<00:03:53.519> a<00:03:53.640> really<00:03:53.959> I 00:03:54.030 --> 00:03:54.040 align:start position:0% smart contract bugs that's a really I 00:03:54.040 --> 00:03:56.589 align:start position:0% smart contract bugs that's a really I think<00:03:54.439> good<00:03:54.760> sign<00:03:55.480> that<00:03:55.760> we're<00:03:55.959> making<00:03:56.280> fewer 00:03:56.589 --> 00:03:56.599 align:start position:0% think good sign that we're making fewer 00:03:56.599 --> 00:03:58.470 align:start position:0% think good sign that we're making fewer and<00:03:56.760> fewer<00:03:57.079> dumb<00:03:57.400> mistakes<00:03:57.879> on<00:03:58.040> the<00:03:58.159> smart 00:03:58.470 --> 00:03:58.480 align:start position:0% and fewer dumb mistakes on the smart 00:03:58.480 --> 00:04:01.429 align:start position:0% and fewer dumb mistakes on the smart contract<00:03:58.959> side<00:03:59.519> how<00:03:59.920> however<00:04:00.439> as<00:04:00.959> all<00:04:01.120> of<00:04:01.239> the 00:04:01.429 --> 00:04:01.439 align:start position:0% contract side how however as all of the 00:04:01.439 --> 00:04:03.270 align:start position:0% contract side how however as all of the stuff<00:04:01.640> that<00:04:01.720> we're<00:04:01.879> building<00:04:02.239> is<00:04:02.480> becoming 00:04:03.270 --> 00:04:03.280 align:start position:0% stuff that we're building is becoming 00:04:03.280 --> 00:04:04.869 align:start position:0% stuff that we're building is becoming such<00:04:03.439> a<00:04:03.640> critical<00:04:04.079> component<00:04:04.439> of<00:04:04.599> Global 00:04:04.869 --> 00:04:04.879 align:start position:0% such a critical component of Global 00:04:04.879 --> 00:04:06.910 align:start position:0% such a critical component of Global Financial<00:04:05.360> infrastructure<00:04:06.239> the<00:04:06.400> stakes<00:04:06.720> are 00:04:06.910 --> 00:04:06.920 align:start position:0% Financial infrastructure the stakes are 00:04:06.920 --> 00:04:08.949 align:start position:0% Financial infrastructure the stakes are higher<00:04:07.200> to<00:04:07.400> actually<00:04:07.799> operationally<00:04:08.599> be 00:04:08.949 --> 00:04:08.959 align:start position:0% higher to actually operationally be 00:04:08.959 --> 00:04:11.229 align:start position:0% higher to actually operationally be strong<00:04:09.200> as<00:04:09.360> well<00:04:09.879> and<00:04:10.000> so<00:04:10.239> whether<00:04:10.560> that's<00:04:11.000> uh 00:04:11.229 --> 00:04:11.239 align:start position:0% strong as well and so whether that's uh 00:04:11.239 --> 00:04:12.750 align:start position:0% strong as well and so whether that's uh whether<00:04:11.480> that's<00:04:11.680> things<00:04:11.920> like<00:04:12.120> supply<00:04:12.439> chain 00:04:12.750 --> 00:04:12.760 align:start position:0% whether that's things like supply chain 00:04:12.760 --> 00:04:15.750 align:start position:0% whether that's things like supply chain attacks<00:04:13.280> or<00:04:13.920> uh<00:04:14.040> or<00:04:14.200> social<00:04:14.560> engineering<00:04:15.560> uh 00:04:15.750 --> 00:04:15.760 align:start position:0% attacks or uh or social engineering uh 00:04:15.760 --> 00:04:19.270 align:start position:0% attacks or uh or social engineering uh it's<00:04:16.000> much<00:04:16.359> harder<00:04:16.919> now<00:04:17.359> than<00:04:17.639> just<00:04:18.400> like<00:04:18.600> not 00:04:19.270 --> 00:04:19.280 align:start position:0% it's much harder now than just like not 00:04:19.280 --> 00:04:21.990 align:start position:0% it's much harder now than just like not uh<00:04:19.560> including<00:04:20.120> dumb<00:04:20.440> bugs<00:04:20.840> in<00:04:20.959> your<00:04:21.079> smart 00:04:21.990 --> 00:04:22.000 align:start position:0% uh including dumb bugs in your smart 00:04:22.000 --> 00:04:24.390 align:start position:0% uh including dumb bugs in your smart contracts<00:04:23.000> so<00:04:23.280> these<00:04:23.400> are<00:04:23.600> cross<00:04:23.960> functional 00:04:24.390 --> 00:04:24.400 align:start position:0% contracts so these are cross functional 00:04:24.400 --> 00:04:26.110 align:start position:0% contracts so these are cross functional exercises<00:04:25.080> we're<00:04:25.240> not<00:04:25.440> just<00:04:25.600> working<00:04:25.880> with<00:04:26.000> a 00:04:26.110 --> 00:04:26.120 align:start position:0% exercises we're not just working with a 00:04:26.120 --> 00:04:27.710 align:start position:0% exercises we're not just working with a development<00:04:26.560> team<00:04:26.840> they're<00:04:27.000> of<00:04:27.160> course<00:04:27.600> a 00:04:27.710 --> 00:04:27.720 align:start position:0% development team they're of course a 00:04:27.720 --> 00:04:29.870 align:start position:0% development team they're of course a core<00:04:28.040> part<00:04:28.199> of<00:04:28.320> it<00:04:28.880> but<00:04:29.000> we're<00:04:29.160> also<00:04:29.440> tending 00:04:29.870 --> 00:04:29.880 align:start position:0% core part of it but we're also tending 00:04:29.880 --> 00:04:31.469 align:start position:0% core part of it but we're also tending to<00:04:30.000> work<00:04:30.199> with<00:04:30.400> their<00:04:30.759> with<00:04:30.960> work<00:04:31.160> with<00:04:31.280> their 00:04:31.469 --> 00:04:31.479 align:start position:0% to work with their with work with their 00:04:31.479 --> 00:04:33.670 align:start position:0% to work with their with work with their Auditors<00:04:32.120> if<00:04:32.280> they're<00:04:32.400> a<00:04:32.560> big<00:04:32.800> protocol<00:04:33.520> that 00:04:33.670 --> 00:04:33.680 align:start position:0% Auditors if they're a big protocol that 00:04:33.680 --> 00:04:35.510 align:start position:0% Auditors if they're a big protocol that has<00:04:33.800> a<00:04:34.000> guardian<00:04:34.360> multisig<00:04:35.000> that's<00:04:35.120> in<00:04:35.280> charge 00:04:35.510 --> 00:04:35.520 align:start position:0% has a guardian multisig that's in charge 00:04:35.520 --> 00:04:36.950 align:start position:0% has a guardian multisig that's in charge of<00:04:35.680> pausing<00:04:36.039> the<00:04:36.160> protocol<00:04:36.560> in<00:04:36.639> case<00:04:36.800> of 00:04:36.950 --> 00:04:36.960 align:start position:0% of pausing the protocol in case of 00:04:36.960 --> 00:04:39.189 align:start position:0% of pausing the protocol in case of emergency<00:04:37.479> we<00:04:37.639> of<00:04:37.759> course<00:04:37.960> work<00:04:38.160> with<00:04:38.360> them<00:04:39.000> um 00:04:39.189 --> 00:04:39.199 align:start position:0% emergency we of course work with them um 00:04:39.199 --> 00:04:40.670 align:start position:0% emergency we of course work with them um Communications<00:04:39.840> team<00:04:40.080> is<00:04:40.280> actually 00:04:40.670 --> 00:04:40.680 align:start position:0% Communications team is actually 00:04:40.680 --> 00:04:42.830 align:start position:0% Communications team is actually essential<00:04:41.199> so<00:04:41.360> that<00:04:41.840> we<00:04:42.000> know<00:04:42.400> like<00:04:42.680> what 00:04:42.830 --> 00:04:42.840 align:start position:0% essential so that we know like what 00:04:42.840 --> 00:04:44.390 align:start position:0% essential so that we know like what would<00:04:43.039> they<00:04:43.199> be<00:04:43.360> communicating<00:04:43.960> out<00:04:44.120> to<00:04:44.280> the 00:04:44.390 --> 00:04:44.400 align:start position:0% would they be communicating out to the 00:04:44.400 --> 00:04:46.469 align:start position:0% would they be communicating out to the public<00:04:44.680> and<00:04:44.919> when<00:04:45.160> during<00:04:45.440> an<00:04:45.680> incident<00:04:46.320> and 00:04:46.469 --> 00:04:46.479 align:start position:0% public and when during an incident and 00:04:46.479 --> 00:04:48.670 align:start position:0% public and when during an incident and legal<00:04:47.000> so<00:04:47.199> that<00:04:47.440> they<00:04:47.560> can<00:04:47.720> say<00:04:48.039> okay<00:04:48.440> if<00:04:48.560> we 00:04:48.670 --> 00:04:48.680 align:start position:0% legal so that they can say okay if we 00:04:48.680 --> 00:04:50.510 align:start position:0% legal so that they can say okay if we were<00:04:48.840> to<00:04:49.000> take<00:04:49.199> this<00:04:49.440> action<00:04:49.840> perhap<00:04:50.240> to 00:04:50.510 --> 00:04:50.520 align:start position:0% were to take this action perhap to 00:04:50.520 --> 00:04:52.230 align:start position:0% were to take this action perhap to perhaps<00:04:50.919> to<00:04:51.320> protect<00:04:51.639> the<00:04:51.720> users<00:04:51.960> of<00:04:52.080> our 00:04:52.230 --> 00:04:52.240 align:start position:0% perhaps to protect the users of our 00:04:52.240 --> 00:04:54.189 align:start position:0% perhaps to protect the users of our protocol<00:04:52.919> can<00:04:53.080> we<00:04:53.240> do<00:04:53.440> that<00:04:53.680> should<00:04:53.880> we<00:04:54.000> do 00:04:54.189 --> 00:04:54.199 align:start position:0% protocol can we do that should we do 00:04:54.199 --> 00:04:56.070 align:start position:0% protocol can we do that should we do that<00:04:54.600> and<00:04:54.800> what<00:04:54.880> should<00:04:55.039> we<00:04:55.199> be<00:04:55.320> saying<00:04:55.919> the 00:04:56.070 --> 00:04:56.080 align:start position:0% that and what should we be saying the 00:04:56.080 --> 00:04:57.830 align:start position:0% that and what should we be saying the conversations<00:04:56.720> between<00:04:57.039> Communications 00:04:57.830 --> 00:04:57.840 align:start position:0% conversations between Communications 00:04:57.840 --> 00:04:59.950 align:start position:0% conversations between Communications legal<00:04:58.199> and<00:04:58.400> devs<00:04:58.880> should<00:04:59.120> really<00:04:59.280> be<00:04:59.800> that<00:04:59.880> are 00:04:59.950 --> 00:04:59.960 align:start position:0% legal and devs should really be that are 00:04:59.960 --> 00:05:01.870 align:start position:0% legal and devs should really be that are figured<00:05:00.240> out<00:05:00.400> in<00:05:00.560> advance<00:05:01.280> so<00:05:01.440> that<00:05:01.600> during 00:05:01.870 --> 00:05:01.880 align:start position:0% figured out in advance so that during 00:05:01.880 --> 00:05:03.670 align:start position:0% figured out in advance so that during the<00:05:02.000> incident<00:05:02.400> you're<00:05:02.560> not<00:05:02.720> thinking<00:05:03.160> like<00:05:03.520> do 00:05:03.670 --> 00:05:03.680 align:start position:0% the incident you're not thinking like do 00:05:03.680 --> 00:05:05.150 align:start position:0% the incident you're not thinking like do we<00:05:03.840> tweet<00:05:04.120> out<00:05:04.280> that<00:05:04.360> we're<00:05:04.520> under<00:05:04.800> attack 00:05:05.150 --> 00:05:05.160 align:start position:0% we tweet out that we're under attack 00:05:05.160 --> 00:05:06.830 align:start position:0% we tweet out that we're under attack right<00:05:05.280> now<00:05:05.520> or<00:05:05.680> do<00:05:05.800> we<00:05:05.919> say<00:05:06.120> something<00:05:06.440> cryptic 00:05:06.830 --> 00:05:06.840 align:start position:0% right now or do we say something cryptic 00:05:06.840 --> 00:05:08.350 align:start position:0% right now or do we say something cryptic or<00:05:06.960> what<00:05:07.039> do<00:05:07.160> we<00:05:07.280> say<00:05:07.520> like<00:05:07.800> these<00:05:08.000> are<00:05:08.199> things 00:05:08.350 --> 00:05:08.360 align:start position:0% or what do we say like these are things 00:05:08.360 --> 00:05:09.830 align:start position:0% or what do we say like these are things that<00:05:08.479> you<00:05:08.560> can<00:05:08.720> just<00:05:08.880> have<00:05:09.039> in<00:05:09.160> a<00:05:09.280> Playbook<00:05:09.680> so 00:05:09.830 --> 00:05:09.840 align:start position:0% that you can just have in a Playbook so 00:05:09.840 --> 00:05:11.469 align:start position:0% that you can just have in a Playbook so that<00:05:09.919> you<00:05:10.000> don't<00:05:10.199> have<00:05:10.320> to<00:05:10.440> think<00:05:10.639> about<00:05:10.840> it<00:05:11.360> uh 00:05:11.469 --> 00:05:11.479 align:start position:0% that you don't have to think about it uh 00:05:11.479 --> 00:05:13.950 align:start position:0% that you don't have to think about it uh in<00:05:11.600> the<00:05:12.160> moment<00:05:13.160> we've<00:05:13.320> worked<00:05:13.560> with<00:05:13.639> a<00:05:13.759> number 00:05:13.950 --> 00:05:13.960 align:start position:0% in the moment we've worked with a number 00:05:13.960 --> 00:05:17.029 align:start position:0% in the moment we've worked with a number of<00:05:14.160> products<00:05:14.759> uh<00:05:15.120> of<00:05:15.240> protocols<00:05:16.000> uh<00:05:16.120> so<00:05:16.360> far<00:05:16.919> uh 00:05:17.029 --> 00:05:17.039 align:start position:0% of products uh of protocols uh so far uh 00:05:17.039 --> 00:05:18.510 align:start position:0% of products uh of protocols uh so far uh but<00:05:17.160> the<00:05:17.240> purpose<00:05:17.479> of<00:05:17.639> this<00:05:17.880> slide<00:05:18.120> is<00:05:18.280> also 00:05:18.510 --> 00:05:18.520 align:start position:0% but the purpose of this slide is also 00:05:18.520 --> 00:05:20.629 align:start position:0% but the purpose of this slide is also just<00:05:18.639> to<00:05:19.039> show<00:05:19.280> you<00:05:19.560> like<00:05:20.039> why<00:05:20.240> teams<00:05:20.479> are 00:05:20.629 --> 00:05:20.639 align:start position:0% just to show you like why teams are 00:05:20.639 --> 00:05:21.990 align:start position:0% just to show you like why teams are working<00:05:20.880> with<00:05:21.039> us<00:05:21.199> it's<00:05:21.360> because<00:05:21.600> like<00:05:21.720> teams 00:05:21.990 --> 00:05:22.000 align:start position:0% working with us it's because like teams 00:05:22.000 --> 00:05:24.430 align:start position:0% working with us it's because like teams are<00:05:22.160> growing<00:05:23.120> uh<00:05:23.400> these<00:05:23.560> are<00:05:23.800> Global<00:05:24.080> teams 00:05:24.430 --> 00:05:24.440 align:start position:0% are growing uh these are Global teams 00:05:24.440 --> 00:05:25.870 align:start position:0% are growing uh these are Global teams and<00:05:24.680> like<00:05:24.800> it's<00:05:25.000> really<00:05:25.240> hard<00:05:25.479> to<00:05:25.680> like 00:05:25.870 --> 00:05:25.880 align:start position:0% and like it's really hard to like 00:05:25.880 --> 00:05:28.110 align:start position:0% and like it's really hard to like prepare<00:05:26.160> for<00:05:26.400> this<00:05:26.600> type<00:05:26.759> of<00:05:27.400> uh<00:05:27.639> this<00:05:27.759> type<00:05:27.960> of 00:05:28.110 --> 00:05:28.120 align:start position:0% prepare for this type of uh this type of 00:05:28.120 --> 00:05:29.870 align:start position:0% prepare for this type of uh this type of thing<00:05:28.560> um<00:05:28.680> there's<00:05:28.880> many<00:05:29.080> ways<00:05:29.240> to<00:05:29.400> engage 00:05:29.870 --> 00:05:29.880 align:start position:0% thing um there's many ways to engage 00:05:29.880 --> 00:05:31.189 align:start position:0% thing um there's many ways to engage with<00:05:30.000> us<00:05:30.160> if<00:05:30.240> you're<00:05:30.400> a<00:05:30.520> protocol<00:05:30.919> that<00:05:31.000> wants 00:05:31.189 --> 00:05:31.199 align:start position:0% with us if you're a protocol that wants 00:05:31.199 --> 00:05:32.629 align:start position:0% with us if you're a protocol that wants to<00:05:31.360> work<00:05:31.520> with<00:05:31.639> a<00:05:31.800> security<00:05:32.160> Alliance<00:05:32.520> and 00:05:32.629 --> 00:05:32.639 align:start position:0% to work with a security Alliance and 00:05:32.639 --> 00:05:35.070 align:start position:0% to work with a security Alliance and have<00:05:32.720> a<00:05:32.880> drill<00:05:33.680> performed<00:05:34.120> with<00:05:34.280> you<00:05:34.600> you<00:05:34.720> can 00:05:35.070 --> 00:05:35.080 align:start position:0% have a drill performed with you you can 00:05:35.080 --> 00:05:36.870 align:start position:0% have a drill performed with you you can uh<00:05:35.160> there's<00:05:35.280> a<00:05:35.400> form<00:05:35.680> on<00:05:35.880> the<00:05:36.039> on<00:05:36.160> the<00:05:36.280> website 00:05:36.870 --> 00:05:36.880 align:start position:0% uh there's a form on the on the website 00:05:36.880 --> 00:05:39.070 align:start position:0% uh there's a form on the on the website and<00:05:37.000> there's<00:05:37.280> also<00:05:37.680> open<00:05:37.919> source<00:05:38.400> uh<00:05:38.960> uh 00:05:39.070 --> 00:05:39.080 align:start position:0% and there's also open source uh uh 00:05:39.080 --> 00:05:40.430 align:start position:0% and there's also open source uh uh resources<00:05:39.560> for<00:05:39.680> you<00:05:39.759> to<00:05:39.880> be<00:05:39.960> able<00:05:40.080> to<00:05:40.199> run 00:05:40.430 --> 00:05:40.440 align:start position:0% resources for you to be able to run 00:05:40.440 --> 00:05:43.309 align:start position:0% resources for you to be able to run these<00:05:41.039> yourself<00:05:42.039> so<00:05:42.560> uh<00:05:42.680> this<00:05:42.759> is<00:05:42.880> a<00:05:43.039> quote 00:05:43.309 --> 00:05:43.319 align:start position:0% these yourself so uh this is a quote 00:05:43.319 --> 00:05:44.830 align:start position:0% these yourself so uh this is a quote that<00:05:43.440> I<00:05:43.520> had<00:05:43.639> a<00:05:43.840> really<00:05:44.120> hard<00:05:44.400> time 00:05:44.830 --> 00:05:44.840 align:start position:0% that I had a really hard time 00:05:44.840 --> 00:05:46.990 align:start position:0% that I had a really hard time attributing<00:05:45.800> uh<00:05:46.120> the<00:05:46.199> internet<00:05:46.479> said<00:05:46.639> it<00:05:46.759> was 00:05:46.990 --> 00:05:47.000 align:start position:0% attributing uh the internet said it was 00:05:47.000 --> 00:05:48.830 align:start position:0% attributing uh the internet said it was either<00:05:47.319> like<00:05:47.440> a<00:05:47.600> Greek<00:05:48.000> poet<00:05:48.280> or<00:05:48.400> the<00:05:48.520> Navy 00:05:48.830 --> 00:05:48.840 align:start position:0% either like a Greek poet or the Navy 00:05:48.840 --> 00:05:50.830 align:start position:0% either like a Greek poet or the Navy Seals<00:05:49.440> but<00:05:49.560> I<00:05:49.639> think<00:05:49.800> that<00:05:49.919> it<00:05:50.120> really<00:05:50.400> like<00:05:50.720> uh 00:05:50.830 --> 00:05:50.840 align:start position:0% Seals but I think that it really like uh 00:05:50.840 --> 00:05:53.430 align:start position:0% Seals but I think that it really like uh stands<00:05:51.280> to<00:05:51.960> to<00:05:52.080> show<00:05:52.400> like<00:05:52.680> why<00:05:52.880> we<00:05:53.039> do<00:05:53.319> this 00:05:53.430 --> 00:05:53.440 align:start position:0% stands to to show like why we do this 00:05:53.440 --> 00:05:55.390 align:start position:0% stands to to show like why we do this and<00:05:53.600> it's<00:05:54.039> uh<00:05:54.160> that<00:05:54.360> Under<00:05:54.639> Pressure<00:05:55.000> we<00:05:55.120> don't 00:05:55.390 --> 00:05:55.400 align:start position:0% and it's uh that Under Pressure we don't 00:05:55.400 --> 00:05:57.390 align:start position:0% and it's uh that Under Pressure we don't rise<00:05:55.759> to<00:05:56.120> the<00:05:56.280> occasion<00:05:56.720> we<00:05:56.840> sink<00:05:57.120> to<00:05:57.240> our 00:05:57.390 --> 00:05:57.400 align:start position:0% rise to the occasion we sink to our 00:05:57.400 --> 00:06:00.350 align:start position:0% rise to the occasion we sink to our level<00:05:57.600> of<00:05:57.919> training<00:05:58.919> uh<00:05:59.440> yeah<00:05:59.840> I<00:05:59.960> think<00:06:00.160> that 00:06:00.350 --> 00:06:00.360 align:start position:0% level of training uh yeah I think that 00:06:00.360 --> 00:06:04.029 align:start position:0% level of training uh yeah I think that that<00:06:00.680> speaks<00:06:01.280> uh<00:06:01.560> to<00:06:01.960> why<00:06:02.120> we<00:06:02.240> do<00:06:02.520> this<00:06:03.520> so<00:06:03.840> each 00:06:04.029 --> 00:06:04.039 align:start position:0% that speaks uh to why we do this so each 00:06:04.039 --> 00:06:06.710 align:start position:0% that speaks uh to why we do this so each one<00:06:04.240> of<00:06:04.440> these<00:06:04.800> builds<00:06:05.280> is<00:06:05.560> quite<00:06:05.840> different 00:06:06.710 --> 00:06:06.720 align:start position:0% one of these builds is quite different 00:06:06.720 --> 00:06:09.029 align:start position:0% one of these builds is quite different um<00:06:07.080> a<00:06:07.280> lot<00:06:07.440> of<00:06:07.720> protocols<00:06:08.639> uh<00:06:08.759> a<00:06:08.800> lot<00:06:08.919> of 00:06:09.029 --> 00:06:09.039 align:start position:0% um a lot of protocols uh a lot of 00:06:09.039 --> 00:06:10.510 align:start position:0% um a lot of protocols uh a lot of protocols<00:06:09.479> have<00:06:09.680> like<00:06:09.840> various<00:06:10.080> sorts<00:06:10.360> of 00:06:10.510 --> 00:06:10.520 align:start position:0% protocols have like various sorts of 00:06:10.520 --> 00:06:11.790 align:start position:0% protocols have like various sorts of like<00:06:10.680> custom<00:06:11.039> infrastructure<00:06:11.639> and 00:06:11.790 --> 00:06:11.800 align:start position:0% like custom infrastructure and 00:06:11.800 --> 00:06:13.589 align:start position:0% like custom infrastructure and monitoring<00:06:12.479> so<00:06:12.680> every<00:06:12.840> time<00:06:13.000> we<00:06:13.160> do<00:06:13.319> this<00:06:13.479> we 00:06:13.589 --> 00:06:13.599 align:start position:0% monitoring so every time we do this we 00:06:13.599 --> 00:06:15.110 align:start position:0% monitoring so every time we do this we end<00:06:13.720> up<00:06:13.880> having<00:06:14.039> to<00:06:14.199> like<00:06:14.360> build<00:06:14.680> a<00:06:14.800> lot<00:06:14.960> of 00:06:15.110 --> 00:06:15.120 align:start position:0% end up having to like build a lot of 00:06:15.120 --> 00:06:17.070 align:start position:0% end up having to like build a lot of things<00:06:15.680> and<00:06:15.759> we've<00:06:15.919> tried<00:06:16.120> to<00:06:16.319> combine<00:06:16.840> all<00:06:16.960> of 00:06:17.070 --> 00:06:17.080 align:start position:0% things and we've tried to combine all of 00:06:17.080 --> 00:06:18.270 align:start position:0% things and we've tried to combine all of those<00:06:17.280> tools<00:06:17.560> and<00:06:17.759> things<00:06:17.960> that<00:06:18.120> we've 00:06:18.270 --> 00:06:18.280 align:start position:0% those tools and things that we've 00:06:18.280 --> 00:06:20.550 align:start position:0% those tools and things that we've learned<00:06:18.599> on<00:06:18.759> how<00:06:18.840> to<00:06:19.000> run<00:06:19.240> these<00:06:19.560> simulations 00:06:20.550 --> 00:06:20.560 align:start position:0% learned on how to run these simulations 00:06:20.560 --> 00:06:22.749 align:start position:0% learned on how to run these simulations um<00:06:20.759> into<00:06:21.280> this<00:06:21.680> uh<00:06:21.800> drill<00:06:22.120> template<00:06:22.520> that<00:06:22.639> you 00:06:22.749 --> 00:06:22.759 align:start position:0% um into this uh drill template that you 00:06:22.759 --> 00:06:24.510 align:start position:0% um into this uh drill template that you can<00:06:22.880> see<00:06:23.199> here<00:06:23.759> it's<00:06:23.880> on<00:06:24.000> the<00:06:24.120> security 00:06:24.510 --> 00:06:24.520 align:start position:0% can see here it's on the security 00:06:24.520 --> 00:06:26.870 align:start position:0% can see here it's on the security Alliance<00:06:24.919> GitHub<00:06:25.360> repository<00:06:26.360> but<00:06:26.639> what<00:06:26.720> are 00:06:26.870 --> 00:06:26.880 align:start position:0% Alliance GitHub repository but what are 00:06:26.880 --> 00:06:27.990 align:start position:0% Alliance GitHub repository but what are the<00:06:27.000> things<00:06:27.160> that<00:06:27.280> we<00:06:27.400> do<00:06:27.560> to<00:06:27.720> make<00:06:27.880> the 00:06:27.990 --> 00:06:28.000 align:start position:0% the things that we do to make the 00:06:28.000 --> 00:06:29.790 align:start position:0% the things that we do to make the environment<00:06:28.440> feel<00:06:28.759> realistic<00:06:29.560> so<00:06:29.639> we<00:06:29.720> of 00:06:29.790 --> 00:06:29.800 align:start position:0% environment feel realistic so we of 00:06:29.800 --> 00:06:31.189 align:start position:0% environment feel realistic so we of course<00:06:29.960> have<00:06:30.039> to<00:06:30.160> run<00:06:30.280> a<00:06:30.400> network<00:06:30.720> Fork<00:06:31.039> we're 00:06:31.189 --> 00:06:31.199 align:start position:0% course have to run a network Fork we're 00:06:31.199 --> 00:06:33.350 align:start position:0% course have to run a network Fork we're usually<00:06:31.840> either<00:06:32.000> doing<00:06:32.280> that<00:06:32.400> with<00:06:32.599> Anvil<00:06:33.120> or 00:06:33.350 --> 00:06:33.360 align:start position:0% usually either doing that with Anvil or 00:06:33.360 --> 00:06:35.350 align:start position:0% usually either doing that with Anvil or with<00:06:33.599> uh<00:06:33.720> tenderly<00:06:34.520> we<00:06:34.599> have<00:06:34.720> to<00:06:34.800> run<00:06:34.960> a<00:06:35.080> block 00:06:35.350 --> 00:06:35.360 align:start position:0% with uh tenderly we have to run a block 00:06:35.360 --> 00:06:36.990 align:start position:0% with uh tenderly we have to run a block Explorer<00:06:35.840> so<00:06:35.960> we're<00:06:36.160> either<00:06:36.319> running<00:06:36.639> block 00:06:36.990 --> 00:06:37.000 align:start position:0% Explorer so we're either running block 00:06:37.000 --> 00:06:39.909 align:start position:0% Explorer so we're either running block Scout<00:06:37.720> um<00:06:37.800> or<00:06:37.960> using<00:06:38.199> a<00:06:38.319> virtual<00:06:38.720> test<00:06:39.000> net<00:06:39.800> um 00:06:39.909 --> 00:06:39.919 align:start position:0% Scout um or using a virtual test net um 00:06:39.919 --> 00:06:41.230 align:start position:0% Scout um or using a virtual test net um we're<00:06:40.080> running<00:06:40.440> monitoring<00:06:40.919> so<00:06:41.080> it's 00:06:41.230 --> 00:06:41.240 align:start position:0% we're running monitoring so it's 00:06:41.240 --> 00:06:43.430 align:start position:0% we're running monitoring so it's essential<00:06:41.560> to<00:06:41.759> mirror<00:06:42.560> the<00:06:42.759> same<00:06:43.000> monitoring 00:06:43.430 --> 00:06:43.440 align:start position:0% essential to mirror the same monitoring 00:06:43.440 --> 00:06:44.830 align:start position:0% essential to mirror the same monitoring that<00:06:43.560> you<00:06:43.639> would<00:06:43.759> have<00:06:43.880> on<00:06:44.000> Main<00:06:44.280> net<00:06:44.599> so<00:06:44.759> if 00:06:44.830 --> 00:06:44.840 align:start position:0% that you would have on Main net so if 00:06:44.840 --> 00:06:46.550 align:start position:0% that you would have on Main net so if you're<00:06:45.000> using<00:06:45.280> a<00:06:45.400> product<00:06:45.759> like<00:06:45.919> hyper<00:06:46.240> native 00:06:46.550 --> 00:06:46.560 align:start position:0% you're using a product like hyper native 00:06:46.560 --> 00:06:48.749 align:start position:0% you're using a product like hyper native hexag<00:06:47.080> or<00:06:47.199> Forida<00:06:47.919> you<00:06:48.039> should<00:06:48.240> be<00:06:48.520> we<00:06:48.599> should 00:06:48.749 --> 00:06:48.759 align:start position:0% hexag or Forida you should be we should 00:06:48.759 --> 00:06:50.550 align:start position:0% hexag or Forida you should be we should be<00:06:48.880> setting<00:06:49.280> all<00:06:49.400> of<00:06:49.599> that<00:06:49.759> same<00:06:50.039> stuff<00:06:50.280> up 00:06:50.550 --> 00:06:50.560 align:start position:0% be setting all of that same stuff up 00:06:50.560 --> 00:06:52.670 align:start position:0% be setting all of that same stuff up against<00:06:50.800> our<00:06:50.919> forked<00:06:51.360> environment<00:06:52.240> we<00:06:52.400> write 00:06:52.670 --> 00:06:52.680 align:start position:0% against our forked environment we write 00:06:52.680 --> 00:06:54.589 align:start position:0% against our forked environment we write Bots<00:06:53.039> to<00:06:53.199> behave<00:06:53.560> like<00:06:53.759> users<00:06:54.120> so<00:06:54.280> if<00:06:54.400> it's<00:06:54.479> a 00:06:54.589 --> 00:06:54.599 align:start position:0% Bots to behave like users so if it's a 00:06:54.599 --> 00:06:56.790 align:start position:0% Bots to behave like users so if it's a lending<00:06:54.960> protocol<00:06:55.440> we<00:06:55.560> have<00:06:55.960> a<00:06:56.080> lot<00:06:56.199> of<00:06:56.400> noisy 00:06:56.790 --> 00:06:56.800 align:start position:0% lending protocol we have a lot of noisy 00:06:56.800 --> 00:06:58.469 align:start position:0% lending protocol we have a lot of noisy transactions<00:06:57.319> of<00:06:57.479> users<00:06:57.840> depositing 00:06:58.469 --> 00:06:58.479 align:start position:0% transactions of users depositing 00:06:58.479 --> 00:07:00.629 align:start position:0% transactions of users depositing borrowing<00:06:58.960> Lending<00:06:59.560> spping<00:07:00.240> um<00:07:00.360> doing 00:07:00.629 --> 00:07:00.639 align:start position:0% borrowing Lending spping um doing 00:07:00.639 --> 00:07:02.309 align:start position:0% borrowing Lending spping um doing everything<00:07:00.919> that<00:07:01.039> would<00:07:01.240> exist<00:07:01.479> on<00:07:01.639> mainnet 00:07:02.309 --> 00:07:02.319 align:start position:0% everything that would exist on mainnet 00:07:02.319 --> 00:07:03.909 align:start position:0% everything that would exist on mainnet so<00:07:02.479> that<00:07:02.639> the<00:07:02.759> only<00:07:03.000> TR<00:07:03.280> so<00:07:03.400> it's<00:07:03.520> not<00:07:03.680> like<00:07:03.840> the 00:07:03.909 --> 00:07:03.919 align:start position:0% so that the only TR so it's not like the 00:07:03.919 --> 00:07:05.670 align:start position:0% so that the only TR so it's not like the team<00:07:04.199> only<00:07:04.440> sees<00:07:04.759> like<00:07:04.879> two<00:07:05.080> transactions<00:07:05.560> and 00:07:05.670 --> 00:07:05.680 align:start position:0% team only sees like two transactions and 00:07:05.680 --> 00:07:06.909 align:start position:0% team only sees like two transactions and they're<00:07:05.800> an<00:07:06.000> exploit<00:07:06.360> and<00:07:06.440> then<00:07:06.560> it's<00:07:06.720> too 00:07:06.909 --> 00:07:06.919 align:start position:0% they're an exploit and then it's too 00:07:06.919 --> 00:07:08.390 align:start position:0% they're an exploit and then it's too easy<00:07:07.400> we<00:07:07.560> try<00:07:07.680> to<00:07:07.800> make<00:07:07.919> it<00:07:08.000> a<00:07:08.080> little<00:07:08.240> bit 00:07:08.390 --> 00:07:08.400 align:start position:0% easy we try to make it a little bit 00:07:08.400 --> 00:07:11.110 align:start position:0% easy we try to make it a little bit harder<00:07:09.240> um<00:07:09.360> we<00:07:09.479> have<00:07:09.599> an<00:07:09.800> exploit<00:07:10.400> which<00:07:10.680> uh<00:07:10.960> an 00:07:11.110 --> 00:07:11.120 align:start position:0% harder um we have an exploit which uh an 00:07:11.120 --> 00:07:13.150 align:start position:0% harder um we have an exploit which uh an exploit<00:07:11.520> bot<00:07:11.840> which<00:07:12.120> ramps<00:07:12.479> up<00:07:12.639> intensity 00:07:13.150 --> 00:07:13.160 align:start position:0% exploit bot which ramps up intensity 00:07:13.160 --> 00:07:15.309 align:start position:0% exploit bot which ramps up intensity over<00:07:13.440> time<00:07:14.240> and<00:07:14.319> then<00:07:14.560> if<00:07:14.720> there's<00:07:14.960> any<00:07:15.120> sort 00:07:15.309 --> 00:07:15.319 align:start position:0% over time and then if there's any sort 00:07:15.319 --> 00:07:16.550 align:start position:0% over time and then if there's any sort of<00:07:15.479> miscellaneous<00:07:16.039> things<00:07:16.199> that<00:07:16.319> they<00:07:16.440> need 00:07:16.550 --> 00:07:16.560 align:start position:0% of miscellaneous things that they need 00:07:16.560 --> 00:07:19.070 align:start position:0% of miscellaneous things that they need to<00:07:16.680> pull<00:07:16.919> in<00:07:17.560> we<00:07:17.680> try<00:07:17.840> to<00:07:18.039> provide<00:07:18.400> that<00:07:18.720> um<00:07:18.960> as 00:07:19.070 --> 00:07:19.080 align:start position:0% to pull in we try to provide that um as 00:07:19.080 --> 00:07:20.710 align:start position:0% to pull in we try to provide that um as well<00:07:19.479> so<00:07:19.639> this<00:07:19.759> takes<00:07:19.960> us<00:07:20.120> usually<00:07:20.400> a<00:07:20.479> couple 00:07:20.710 --> 00:07:20.720 align:start position:0% well so this takes us usually a couple 00:07:20.720 --> 00:07:22.189 align:start position:0% well so this takes us usually a couple weeks<00:07:20.919> to<00:07:21.080> build<00:07:21.319> for<00:07:21.479> each<00:07:21.680> protocol<00:07:22.120> but 00:07:22.189 --> 00:07:22.199 align:start position:0% weeks to build for each protocol but 00:07:22.199 --> 00:07:23.950 align:start position:0% weeks to build for each protocol but we're<00:07:22.319> trying<00:07:22.560> to<00:07:22.720> get<00:07:23.120> faster<00:07:23.400> and<00:07:23.639> faster 00:07:23.950 --> 00:07:23.960 align:start position:0% we're trying to get faster and faster 00:07:23.960 --> 00:07:26.189 align:start position:0% we're trying to get faster and faster each<00:07:24.160> time<00:07:24.360> and<00:07:24.520> part<00:07:24.680> of<00:07:24.840> that<00:07:24.960> is<00:07:25.240> uh<00:07:25.960> uh 00:07:26.189 --> 00:07:26.199 align:start position:0% each time and part of that is uh uh 00:07:26.199 --> 00:07:28.029 align:start position:0% each time and part of that is uh uh thanks<00:07:26.400> to<00:07:26.560> this<00:07:26.800> uh<00:07:26.919> open<00:07:27.199> source<00:07:27.639> template 00:07:28.029 --> 00:07:28.039 align:start position:0% thanks to this uh open source template 00:07:28.039 --> 00:07:31.390 align:start position:0% thanks to this uh open source template that<00:07:28.160> we're<00:07:28.479> that<00:07:28.560> we're<00:07:28.720> working<00:07:28.960> on 00:07:31.390 --> 00:07:31.400 align:start position:0% that we're that we're working on 00:07:31.400 --> 00:07:33.070 align:start position:0% that we're that we're working on so<00:07:31.680> what<00:07:31.759> are<00:07:31.879> some<00:07:32.000> of<00:07:32.080> the<00:07:32.199> scenarios<00:07:32.919> that 00:07:33.070 --> 00:07:33.080 align:start position:0% so what are some of the scenarios that 00:07:33.080 --> 00:07:35.350 align:start position:0% so what are some of the scenarios that we've<00:07:33.440> uh<00:07:33.560> that<00:07:33.639> we've<00:07:33.840> worked<00:07:34.039> on<00:07:34.319> so<00:07:34.919> uh<00:07:35.280> as 00:07:35.350 --> 00:07:35.360 align:start position:0% we've uh that we've worked on so uh as 00:07:35.360 --> 00:07:36.430 align:start position:0% we've uh that we've worked on so uh as you've<00:07:35.520> seen<00:07:35.680> we've<00:07:35.840> worked<00:07:36.000> with<00:07:36.160> various 00:07:36.430 --> 00:07:36.440 align:start position:0% you've seen we've worked with various 00:07:36.440 --> 00:07:38.029 align:start position:0% you've seen we've worked with various like<00:07:36.560> lending<00:07:36.879> protocols<00:07:37.319> and<00:07:37.479> decentralized 00:07:38.029 --> 00:07:38.039 align:start position:0% like lending protocols and decentralized 00:07:38.039 --> 00:07:40.270 align:start position:0% like lending protocols and decentralized exchanges<00:07:38.560> and<00:07:38.720> l2s<00:07:39.479> and<00:07:39.560> so<00:07:39.759> the<00:07:39.879> things<00:07:40.120> that 00:07:40.270 --> 00:07:40.280 align:start position:0% exchanges and l2s and so the things that 00:07:40.280 --> 00:07:42.589 align:start position:0% exchanges and l2s and so the things that we're<00:07:40.479> work<00:07:40.800> that<00:07:40.960> we<00:07:41.160> like<00:07:41.319> try<00:07:41.800> simulate<00:07:42.400> are 00:07:42.589 --> 00:07:42.599 align:start position:0% we're work that we like try simulate are 00:07:42.599 --> 00:07:45.710 align:start position:0% we're work that we like try simulate are not<00:07:42.919> necessarily<00:07:43.919> uh<00:07:44.360> like<00:07:44.759> bugs<00:07:45.319> as<00:07:45.479> in<00:07:45.599> like 00:07:45.710 --> 00:07:45.720 align:start position:0% not necessarily uh like bugs as in like 00:07:45.720 --> 00:07:47.430 align:start position:0% not necessarily uh like bugs as in like a<00:07:45.800> smart<00:07:46.120> contract<00:07:46.440> bug<00:07:46.919> because<00:07:47.120> we're<00:07:47.280> not 00:07:47.430 --> 00:07:47.440 align:start position:0% a smart contract bug because we're not 00:07:47.440 --> 00:07:49.390 align:start position:0% a smart contract bug because we're not Auditors<00:07:48.039> we're<00:07:48.199> not<00:07:48.400> trying<00:07:48.639> to<00:07:48.840> just<00:07:49.000> find 00:07:49.390 --> 00:07:49.400 align:start position:0% Auditors we're not trying to just find 00:07:49.400 --> 00:07:51.909 align:start position:0% Auditors we're not trying to just find like<00:07:49.720> a<00:07:49.879> mistake<00:07:50.159> in<00:07:50.319> your<00:07:50.520> code<00:07:51.400> um<00:07:51.639> and<00:07:51.800> in 00:07:51.909 --> 00:07:51.919 align:start position:0% like a mistake in your code um and in 00:07:51.919 --> 00:07:53.230 align:start position:0% like a mistake in your code um and in fact<00:07:52.120> like<00:07:52.280> if<00:07:52.360> we<00:07:52.479> do<00:07:52.759> that's<00:07:52.919> like<00:07:53.080> that's 00:07:53.230 --> 00:07:53.240 align:start position:0% fact like if we do that's like that's 00:07:53.240 --> 00:07:54.749 align:start position:0% fact like if we do that's like that's like<00:07:53.599> not<00:07:53.800> what<00:07:53.960> we're<00:07:54.280> that<00:07:54.360> would<00:07:54.479> not<00:07:54.639> be 00:07:54.749 --> 00:07:54.759 align:start position:0% like not what we're that would not be 00:07:54.759 --> 00:07:56.189 align:start position:0% like not what we're that would not be the<00:07:54.919> goal<00:07:55.280> we're<00:07:55.440> trying<00:07:55.599> to<00:07:55.720> figure<00:07:55.919> out<00:07:56.080> what 00:07:56.189 --> 00:07:56.199 align:start position:0% the goal we're trying to figure out what 00:07:56.199 --> 00:07:58.710 align:start position:0% the goal we're trying to figure out what are<00:07:56.319> the<00:07:56.440> things<00:07:56.639> that<00:07:56.800> can<00:07:57.000> happen<00:07:57.840> in<00:07:58.360> if<00:07:58.560> the 00:07:58.710 --> 00:07:58.720 align:start position:0% are the things that can happen in if the 00:07:58.720 --> 00:08:00.909 align:start position:0% are the things that can happen in if the protocol<00:07:59.120> works<00:07:59.639> even<00:07:59.840> how<00:08:00.000> you<00:08:00.199> designed<00:08:00.560> it 00:08:00.909 --> 00:08:00.919 align:start position:0% protocol works even how you designed it 00:08:00.919 --> 00:08:02.790 align:start position:0% protocol works even how you designed it so<00:08:01.120> what<00:08:01.199> if<00:08:01.360> some<00:08:01.520> sort<00:08:01.680> of<00:08:01.879> external<00:08:02.639> uh 00:08:02.790 --> 00:08:02.800 align:start position:0% so what if some sort of external uh 00:08:02.800 --> 00:08:04.749 align:start position:0% so what if some sort of external uh dependency<00:08:03.280> fails<00:08:03.759> what<00:08:03.879> if<00:08:04.319> the<00:08:04.440> way<00:08:04.639> that 00:08:04.749 --> 00:08:04.759 align:start position:0% dependency fails what if the way that 00:08:04.759 --> 00:08:06.710 align:start position:0% dependency fails what if the way that you're<00:08:04.960> importing<00:08:05.440> Oracle<00:08:05.879> data<00:08:06.120> is<00:08:06.240> weird<00:08:06.520> or 00:08:06.710 --> 00:08:06.720 align:start position:0% you're importing Oracle data is weird or 00:08:06.720 --> 00:08:09.189 align:start position:0% you're importing Oracle data is weird or what<00:08:06.800> if<00:08:07.000> like<00:08:07.159> some<00:08:07.520> token<00:08:08.520> uh<00:08:08.680> some<00:08:08.840> token 00:08:09.189 --> 00:08:09.199 align:start position:0% what if like some token uh some token 00:08:09.199 --> 00:08:10.670 align:start position:0% what if like some token uh some token contract<00:08:09.599> gets<00:08:09.800> upgraded<00:08:10.280> and<00:08:10.400> starts 00:08:10.670 --> 00:08:10.680 align:start position:0% contract gets upgraded and starts 00:08:10.680 --> 00:08:12.230 align:start position:0% contract gets upgraded and starts behaving<00:08:11.120> differently<00:08:11.720> so<00:08:11.879> what<00:08:12.000> are<00:08:12.120> the 00:08:12.230 --> 00:08:12.240 align:start position:0% behaving differently so what are the 00:08:12.240 --> 00:08:13.430 align:start position:0% behaving differently so what are the things<00:08:12.400> that<00:08:12.520> are<00:08:12.720> outside<00:08:13.080> of<00:08:13.199> your 00:08:13.430 --> 00:08:13.440 align:start position:0% things that are outside of your 00:08:13.440 --> 00:08:15.670 align:start position:0% things that are outside of your protocols<00:08:14.039> control<00:08:14.800> that<00:08:14.960> can<00:08:15.240> uh<00:08:15.360> that<00:08:15.520> can 00:08:15.670 --> 00:08:15.680 align:start position:0% protocols control that can uh that can 00:08:15.680 --> 00:08:18.070 align:start position:0% protocols control that can uh that can change<00:08:16.479> what<00:08:16.599> if<00:08:16.720> your<00:08:17.000> upgrade<00:08:17.400> goes<00:08:17.639> poorly 00:08:18.070 --> 00:08:18.080 align:start position:0% change what if your upgrade goes poorly 00:08:18.080 --> 00:08:19.790 align:start position:0% change what if your upgrade goes poorly how<00:08:18.199> would<00:08:18.319> you<00:08:18.520> detect<00:08:18.919> that<00:08:19.479> um<00:08:19.599> what<00:08:19.680> if 00:08:19.790 --> 00:08:19.800 align:start position:0% how would you detect that um what if 00:08:19.800 --> 00:08:21.510 align:start position:0% how would you detect that um what if there's<00:08:20.000> something<00:08:20.319> strange<00:08:20.720> happening<00:08:21.120> with 00:08:21.510 --> 00:08:21.520 align:start position:0% there's something strange happening with 00:08:21.520 --> 00:08:24.350 align:start position:0% there's something strange happening with oracles<00:08:22.520> and<00:08:22.759> also<00:08:23.720> uh<00:08:23.840> one<00:08:24.000> thing<00:08:24.159> that<00:08:24.280> I 00:08:24.350 --> 00:08:24.360 align:start position:0% oracles and also uh one thing that I 00:08:24.360 --> 00:08:26.029 align:start position:0% oracles and also uh one thing that I think<00:08:24.479> was<00:08:24.639> actually<00:08:24.840> pretty<00:08:25.080> fun<00:08:25.560> is<00:08:25.680> in<00:08:25.840> some 00:08:26.029 --> 00:08:26.039 align:start position:0% think was actually pretty fun is in some 00:08:26.039 --> 00:08:27.670 align:start position:0% think was actually pretty fun is in some cases<00:08:26.360> we<00:08:26.479> did<00:08:26.680> like<00:08:26.800> a<00:08:27.159> a<00:08:27.240> malicious 00:08:27.670 --> 00:08:27.680 align:start position:0% cases we did like a a malicious 00:08:27.680 --> 00:08:30.149 align:start position:0% cases we did like a a malicious governance<00:08:28.199> proposal<00:08:29.000> uh<00:08:29.120> C<00:08:29.639> f<00:08:29.840> with<00:08:29.960> some 00:08:30.149 --> 00:08:30.159 align:start position:0% governance proposal uh C f with some 00:08:30.159 --> 00:08:31.749 align:start position:0% governance proposal uh C f with some protocols<00:08:30.919> where<00:08:31.080> we<00:08:31.240> just<00:08:31.400> like<00:08:31.520> kind<00:08:31.639> of 00:08:31.749 --> 00:08:31.759 align:start position:0% protocols where we just like kind of 00:08:31.759 --> 00:08:33.230 align:start position:0% protocols where we just like kind of flooded<00:08:32.159> them<00:08:32.320> with<00:08:32.399> a<00:08:32.519> bunch<00:08:32.680> of<00:08:32.800> governance 00:08:33.230 --> 00:08:33.240 align:start position:0% flooded them with a bunch of governance 00:08:33.240 --> 00:08:34.430 align:start position:0% flooded them with a bunch of governance proposals<00:08:33.640> that<00:08:33.760> looked<00:08:33.959> like<00:08:34.120> normal 00:08:34.430 --> 00:08:34.440 align:start position:0% proposals that looked like normal 00:08:34.440 --> 00:08:36.589 align:start position:0% proposals that looked like normal funding<00:08:34.880> requests<00:08:35.320> for<00:08:35.919> events<00:08:36.360> or 00:08:36.589 --> 00:08:36.599 align:start position:0% funding requests for events or 00:08:36.599 --> 00:08:38.630 align:start position:0% funding requests for events or sponsorships<00:08:37.320> or<00:08:37.560> just<00:08:38.080> uh<00:08:38.200> parameter 00:08:38.630 --> 00:08:38.640 align:start position:0% sponsorships or just uh parameter 00:08:38.640 --> 00:08:40.750 align:start position:0% sponsorships or just uh parameter updates<00:08:39.080> but<00:08:39.240> some<00:08:39.399> of<00:08:39.560> them<00:08:39.839> also<00:08:40.200> included 00:08:40.750 --> 00:08:40.760 align:start position:0% updates but some of them also included 00:08:40.760 --> 00:08:43.070 align:start position:0% updates but some of them also included like<00:08:40.919> malicious<00:08:41.440> data<00:08:42.159> um<00:08:42.279> like<00:08:42.440> how<00:08:42.560> tornado 00:08:43.070 --> 00:08:43.080 align:start position:0% like malicious data um like how tornado 00:08:43.080 --> 00:08:45.030 align:start position:0% like malicious data um like how tornado got<00:08:43.479> uh<00:08:43.599> hacked<00:08:43.959> or<00:08:44.200> I<00:08:44.279> think<00:08:44.600> a<00:08:44.680> number<00:08:44.880> of 00:08:45.030 --> 00:08:45.040 align:start position:0% got uh hacked or I think a number of 00:08:45.040 --> 00:08:46.750 align:start position:0% got uh hacked or I think a number of protocols<00:08:45.519> how<00:08:45.920> how<00:08:46.040> they<00:08:46.160> got<00:08:46.320> hacked<00:08:46.600> just 00:08:46.750 --> 00:08:46.760 align:start position:0% protocols how how they got hacked just 00:08:46.760 --> 00:08:48.910 align:start position:0% protocols how how they got hacked just by<00:08:46.920> having<00:08:47.200> like<00:08:47.440> sneaky<00:08:48.040> additional<00:08:48.560> call 00:08:48.910 --> 00:08:48.920 align:start position:0% by having like sneaky additional call 00:08:48.920 --> 00:08:51.949 align:start position:0% by having like sneaky additional call data<00:08:49.760> um<00:08:50.080> that<00:08:50.560> uh<00:08:50.839> that<00:08:50.959> ended<00:08:51.200> up<00:08:51.440> having 00:08:51.949 --> 00:08:51.959 align:start position:0% data um that uh that ended up having 00:08:51.959 --> 00:08:55.150 align:start position:0% data um that uh that ended up having wide<00:08:52.680> uh<00:08:52.839> bad 00:08:55.150 --> 00:08:55.160 align:start position:0% 00:08:55.160 --> 00:08:57.430 align:start position:0% implications<00:08:56.160> uh<00:08:56.279> I've<00:08:56.440> pulled<00:08:56.680> out<00:08:56.800> a<00:08:56.959> few 00:08:57.430 --> 00:08:57.440 align:start position:0% implications uh I've pulled out a few 00:08:57.440 --> 00:08:59.030 align:start position:0% implications uh I've pulled out a few best<00:08:57.680> practices<00:08:58.120> of<00:08:58.279> what<00:08:58.399> I've<00:08:58.560> learned<00:08:58.880> from 00:08:59.030 --> 00:08:59.040 align:start position:0% best practices of what I've learned from 00:08:59.040 --> 00:09:00.829 align:start position:0% best practices of what I've learned from working<00:08:59.279> with<00:08:59.480> with<00:09:00.160> uh<00:09:00.279> working<00:09:00.560> with<00:09:00.680> these 00:09:00.829 --> 00:09:00.839 align:start position:0% working with with uh working with these 00:09:00.839 --> 00:09:02.190 align:start position:0% working with with uh working with these teams<00:09:01.079> that<00:09:01.200> I<00:09:01.320> just<00:09:01.399> want<00:09:01.519> to<00:09:01.760> go<00:09:01.920> over 00:09:02.190 --> 00:09:02.200 align:start position:0% teams that I just want to go over 00:09:02.200 --> 00:09:04.590 align:start position:0% teams that I just want to go over briefly<00:09:03.000> and<00:09:03.120> so<00:09:03.399> one<00:09:03.680> is<00:09:03.839> just<00:09:04.000> maintaining 00:09:04.590 --> 00:09:04.600 align:start position:0% briefly and so one is just maintaining 00:09:04.600 --> 00:09:06.509 align:start position:0% briefly and so one is just maintaining multiple<00:09:05.160> communication<00:09:05.800> channels<00:09:06.160> to<00:09:06.320> reach 00:09:06.509 --> 00:09:06.519 align:start position:0% multiple communication channels to reach 00:09:06.519 --> 00:09:08.949 align:start position:0% multiple communication channels to reach your<00:09:06.680> teams<00:09:07.680> uh<00:09:07.839> one<00:09:08.000> thing<00:09:08.160> I<00:09:08.279> like<00:09:08.440> to<00:09:08.720> tell 00:09:08.949 --> 00:09:08.959 align:start position:0% your teams uh one thing I like to tell 00:09:08.959 --> 00:09:11.269 align:start position:0% your teams uh one thing I like to tell teams<00:09:09.240> is<00:09:09.399> like<00:09:09.640> imagine<00:09:10.640> uh<00:09:10.839> like<00:09:10.959> during<00:09:11.160> a 00:09:11.269 --> 00:09:11.279 align:start position:0% teams is like imagine uh like during a 00:09:11.279 --> 00:09:13.509 align:start position:0% teams is like imagine uh like during a tabletop<00:09:11.880> like<00:09:12.360> imagine<00:09:12.760> this<00:09:13.000> scenario 00:09:13.509 --> 00:09:13.519 align:start position:0% tabletop like imagine this scenario 00:09:13.519 --> 00:09:15.030 align:start position:0% tabletop like imagine this scenario happens<00:09:13.920> but<00:09:14.079> now<00:09:14.399> imagine<00:09:14.760> that<00:09:14.880> this 00:09:15.030 --> 00:09:15.040 align:start position:0% happens but now imagine that this 00:09:15.040 --> 00:09:16.829 align:start position:0% happens but now imagine that this happened<00:09:15.399> and<00:09:15.640> telegram<00:09:16.200> is<00:09:16.360> down<00:09:16.600> on<00:09:16.720> the 00:09:16.829 --> 00:09:16.839 align:start position:0% happened and telegram is down on the 00:09:16.839 --> 00:09:18.430 align:start position:0% happened and telegram is down on the same<00:09:17.079> day<00:09:17.200> that<00:09:17.360> this<00:09:17.519> happened<00:09:18.120> can<00:09:18.240> you 00:09:18.430 --> 00:09:18.440 align:start position:0% same day that this happened can you 00:09:18.440 --> 00:09:20.350 align:start position:0% same day that this happened can you actually<00:09:18.720> reach<00:09:19.079> the<00:09:19.200> Guardians<00:09:19.680> do<00:09:19.800> you<00:09:19.959> have 00:09:20.350 --> 00:09:20.360 align:start position:0% actually reach the Guardians do you have 00:09:20.360 --> 00:09:21.710 align:start position:0% actually reach the Guardians do you have another<00:09:20.640> way<00:09:20.760> to<00:09:20.920> reach<00:09:21.160> them<00:09:21.320> can<00:09:21.440> you<00:09:21.519> reach 00:09:21.710 --> 00:09:21.720 align:start position:0% another way to reach them can you reach 00:09:21.720 --> 00:09:24.430 align:start position:0% another way to reach them can you reach them<00:09:21.880> on<00:09:22.240> slack<00:09:22.839> Discord<00:09:23.279> can<00:09:23.440> you<00:09:23.600> page<00:09:23.959> them 00:09:24.430 --> 00:09:24.440 align:start position:0% them on slack Discord can you page them 00:09:24.440 --> 00:09:25.990 align:start position:0% them on slack Discord can you page them uh<00:09:24.680> sometimes<00:09:24.920> we<00:09:25.079> find<00:09:25.440> that<00:09:25.640> like<00:09:25.760> when<00:09:25.880> we 00:09:25.990 --> 00:09:26.000 align:start position:0% uh sometimes we find that like when we 00:09:26.000 --> 00:09:28.230 align:start position:0% uh sometimes we find that like when we work<00:09:26.160> with<00:09:26.279> a<00:09:26.399> team<00:09:27.000> like<00:09:27.240> a<00:09:27.440> a<00:09:27.560> paging<00:09:27.959> system 00:09:28.230 --> 00:09:28.240 align:start position:0% work with a team like a a paging system 00:09:28.240 --> 00:09:29.910 align:start position:0% work with a team like a a paging system that<00:09:28.399> they<00:09:28.519> think<00:09:28.720> is<00:09:28.880> set<00:09:29.079> up<00:09:29.399> is<00:09:29.560> just 00:09:29.910 --> 00:09:29.920 align:start position:0% that they think is set up is just 00:09:29.920 --> 00:09:31.829 align:start position:0% that they think is set up is just deprecated<00:09:30.519> and<00:09:30.880> hasn't<00:09:31.120> been<00:09:31.279> working<00:09:31.560> in<00:09:31.680> a 00:09:31.829 --> 00:09:31.839 align:start position:0% deprecated and hasn't been working in a 00:09:31.839 --> 00:09:33.470 align:start position:0% deprecated and hasn't been working in a while<00:09:32.079> and<00:09:32.200> they<00:09:32.560> can't<00:09:32.839> actually<00:09:33.120> reach<00:09:33.360> the 00:09:33.470 --> 00:09:33.480 align:start position:0% while and they can't actually reach the 00:09:33.480 --> 00:09:35.430 align:start position:0% while and they can't actually reach the teams<00:09:33.760> that<00:09:33.920> they<00:09:34.040> want<00:09:34.200> to<00:09:34.760> or<00:09:35.000> they<00:09:35.120> reach 00:09:35.430 --> 00:09:35.440 align:start position:0% teams that they want to or they reach 00:09:35.440 --> 00:09:37.350 align:start position:0% teams that they want to or they reach the<00:09:35.560> team<00:09:36.440> uh<00:09:36.560> and<00:09:36.680> they<00:09:36.800> don't<00:09:36.959> have<00:09:37.120> their 00:09:37.350 --> 00:09:37.360 align:start position:0% the team uh and they don't have their 00:09:37.360 --> 00:09:39.550 align:start position:0% the team uh and they don't have their Ledger<00:09:37.640> with<00:09:37.800> them<00:09:37.959> and<00:09:38.079> so<00:09:38.360> like<00:09:38.880> okay<00:09:39.320> cool 00:09:39.550 --> 00:09:39.560 align:start position:0% Ledger with them and so like okay cool 00:09:39.560 --> 00:09:40.870 align:start position:0% Ledger with them and so like okay cool we<00:09:39.680> got<00:09:39.800> in<00:09:39.959> touch<00:09:40.120> with<00:09:40.279> you<00:09:40.399> but<00:09:40.519> you<00:09:40.640> can't 00:09:40.870 --> 00:09:40.880 align:start position:0% we got in touch with you but you can't 00:09:40.880 --> 00:09:42.230 align:start position:0% we got in touch with you but you can't actually<00:09:41.079> sign<00:09:41.320> the<00:09:41.440> pause<00:09:41.720> transaction 00:09:42.230 --> 00:09:42.240 align:start position:0% actually sign the pause transaction 00:09:42.240 --> 00:09:43.750 align:start position:0% actually sign the pause transaction because<00:09:42.440> you're<00:09:42.640> camping<00:09:43.160> like<00:09:43.440> these<00:09:43.600> are 00:09:43.750 --> 00:09:43.760 align:start position:0% because you're camping like these are 00:09:43.760 --> 00:09:46.350 align:start position:0% because you're camping like these are things<00:09:43.920> that<00:09:44.040> you<00:09:44.120> want<00:09:44.240> to<00:09:44.600> test<00:09:45.600> um<00:09:46.000> also 00:09:46.350 --> 00:09:46.360 align:start position:0% things that you want to test um also 00:09:46.360 --> 00:09:48.310 align:start position:0% things that you want to test um also risk<00:09:46.720> isolation<00:09:47.320> this<00:09:47.440> is<00:09:47.640> a<00:09:47.800> we<00:09:47.920> learned<00:09:48.200> a 00:09:48.310 --> 00:09:48.320 align:start position:0% risk isolation this is a we learned a 00:09:48.320 --> 00:09:50.630 align:start position:0% risk isolation this is a we learned a lot<00:09:48.560> I<00:09:48.640> think<00:09:48.839> from<00:09:49.120> the<00:09:49.720> uh<00:09:49.880> from<00:09:50.079> how<00:09:50.240> the<00:09:50.320> UR 00:09:50.630 --> 00:09:50.640 align:start position:0% lot I think from the uh from how the UR 00:09:50.640 --> 00:09:52.870 align:start position:0% lot I think from the uh from how the UR team<00:09:51.399> um<00:09:51.560> prepares<00:09:51.920> and<00:09:52.120> isolates<00:09:52.600> risk 00:09:52.870 --> 00:09:52.880 align:start position:0% team um prepares and isolates risk 00:09:52.880 --> 00:09:54.790 align:start position:0% team um prepares and isolates risk between<00:09:53.120> the<00:09:53.240> different<00:09:53.560> strategies<00:09:54.480> and<00:09:54.600> so 00:09:54.790 --> 00:09:54.800 align:start position:0% between the different strategies and so 00:09:54.800 --> 00:09:56.910 align:start position:0% between the different strategies and so there's<00:09:55.240> there's<00:09:55.440> a<00:09:55.760> a<00:09:55.920> big<00:09:56.160> lesson<00:09:56.519> in<00:09:56.720> like 00:09:56.910 --> 00:09:56.920 align:start position:0% there's there's a a big lesson in like 00:09:56.920 --> 00:09:58.790 align:start position:0% there's there's a a big lesson in like minimizing<00:09:57.560> the<00:09:57.680> amount<00:09:57.880> of<00:09:58.120> contagion<00:09:58.680> that 00:09:58.790 --> 00:09:58.800 align:start position:0% minimizing the amount of contagion that 00:09:58.800 --> 00:10:00.030 align:start position:0% minimizing the amount of contagion that can<00:09:58.959> spread 00:10:00.030 --> 00:10:00.040 align:start position:0% can spread 00:10:00.040 --> 00:10:02.870 align:start position:0% can spread uh<00:10:00.200> from<00:10:00.480> like<00:10:00.720> one<00:10:01.200> strategy<00:10:01.800> to<00:10:02.079> another<00:10:02.720> and 00:10:02.870 --> 00:10:02.880 align:start position:0% uh from like one strategy to another and 00:10:02.880 --> 00:10:04.750 align:start position:0% uh from like one strategy to another and also<00:10:03.120> the<00:10:03.279> diligence<00:10:03.839> process<00:10:04.200> before<00:10:04.480> any 00:10:04.750 --> 00:10:04.760 align:start position:0% also the diligence process before any 00:10:04.760 --> 00:10:06.670 align:start position:0% also the diligence process before any strategy<00:10:05.200> was<00:10:05.399> employed<00:10:06.079> there<00:10:06.200> was<00:10:06.440> always 00:10:06.670 --> 00:10:06.680 align:start position:0% strategy was employed there was always 00:10:06.680 --> 00:10:09.150 align:start position:0% strategy was employed there was always an<00:10:06.839> emergency<00:10:07.480> response<00:10:07.800> of<00:10:08.000> like<00:10:08.519> with<00:10:08.839> this 00:10:09.150 --> 00:10:09.160 align:start position:0% an emergency response of like with this 00:10:09.160 --> 00:10:10.949 align:start position:0% an emergency response of like with this change<00:10:09.800> these<00:10:09.920> are<00:10:10.079> the<00:10:10.200> things<00:10:10.399> that<00:10:10.519> can<00:10:10.720> go 00:10:10.949 --> 00:10:10.959 align:start position:0% change these are the things that can go 00:10:10.959 --> 00:10:12.590 align:start position:0% change these are the things that can go wrong<00:10:11.399> and<00:10:11.560> these<00:10:11.680> are<00:10:11.839> the<00:10:11.959> steps<00:10:12.240> you<00:10:12.360> would 00:10:12.590 --> 00:10:12.600 align:start position:0% wrong and these are the steps you would 00:10:12.600 --> 00:10:15.470 align:start position:0% wrong and these are the steps you would take<00:10:13.360> to<00:10:13.560> recover<00:10:13.959> funds<00:10:14.480> before<00:10:14.760> they<00:10:14.920> become 00:10:15.470 --> 00:10:15.480 align:start position:0% take to recover funds before they become 00:10:15.480 --> 00:10:18.110 align:start position:0% take to recover funds before they become uh<00:10:15.600> unrecoverable<00:10:16.560> so<00:10:16.760> like<00:10:16.959> Risk<00:10:17.360> isolation 00:10:18.110 --> 00:10:18.120 align:start position:0% uh unrecoverable so like Risk isolation 00:10:18.120 --> 00:10:20.949 align:start position:0% uh unrecoverable so like Risk isolation with<00:10:18.279> urine<00:10:19.200> uh<00:10:19.360> similarly<00:10:19.959> like<00:10:20.399> Asset<00:10:20.680> Risk 00:10:20.949 --> 00:10:20.959 align:start position:0% with urine uh similarly like Asset Risk 00:10:20.959 --> 00:10:22.590 align:start position:0% with urine uh similarly like Asset Risk isolation<00:10:21.399> with<00:10:21.560> a<00:10:21.920> we<00:10:22.040> found<00:10:22.240> was<00:10:22.399> very 00:10:22.590 --> 00:10:22.600 align:start position:0% isolation with a we found was very 00:10:22.600 --> 00:10:24.389 align:start position:0% isolation with a we found was very interesting<00:10:23.079> how<00:10:23.519> you<00:10:23.640> can<00:10:23.800> see<00:10:24.040> how<00:10:24.200> there's 00:10:24.389 --> 00:10:24.399 align:start position:0% interesting how you can see how there's 00:10:24.399 --> 00:10:26.150 align:start position:0% interesting how you can see how there's all<00:10:24.560> these<00:10:24.760> different<00:10:25.000> configuration<00:10:25.640> Flags 00:10:26.150 --> 00:10:26.160 align:start position:0% all these different configuration Flags 00:10:26.160 --> 00:10:28.190 align:start position:0% all these different configuration Flags based<00:10:26.440> on<00:10:27.000> how<00:10:27.240> potentially<00:10:27.760> risky<00:10:28.079> a 00:10:28.190 --> 00:10:28.200 align:start position:0% based on how potentially risky a 00:10:28.200 --> 00:10:30.230 align:start position:0% based on how potentially risky a different<00:10:28.480> collateral<00:10:28.959> asset<00:10:29.200> is<00:10:29.399> is<00:10:30.120> they 00:10:30.230 --> 00:10:30.240 align:start position:0% different collateral asset is is they 00:10:30.240 --> 00:10:31.829 align:start position:0% different collateral asset is is they have<00:10:30.440> different<00:10:30.800> properties<00:10:31.240> as<00:10:31.360> far<00:10:31.519> as<00:10:31.680> how 00:10:31.829 --> 00:10:31.839 align:start position:0% have different properties as far as how 00:10:31.839 --> 00:10:33.829 align:start position:0% have different properties as far as how they<00:10:31.959> can<00:10:32.120> be<00:10:32.760> uh<00:10:32.959> how<00:10:33.079> they<00:10:33.200> can<00:10:33.320> be<00:10:33.440> used<00:10:33.720> in 00:10:33.829 --> 00:10:33.839 align:start position:0% they can be uh how they can be used in 00:10:33.839 --> 00:10:35.430 align:start position:0% they can be uh how they can be used in the<00:10:34.000> protocol<00:10:34.680> so<00:10:34.839> I<00:10:34.920> think<00:10:35.040> that<00:10:35.160> these<00:10:35.279> are 00:10:35.430 --> 00:10:35.440 align:start position:0% the protocol so I think that these are 00:10:35.440 --> 00:10:36.829 align:start position:0% the protocol so I think that these are all<00:10:35.639> really<00:10:35.880> interesting<00:10:36.279> lessons<00:10:36.639> from 00:10:36.829 --> 00:10:36.839 align:start position:0% all really interesting lessons from 00:10:36.839 --> 00:10:38.790 align:start position:0% all really interesting lessons from different<00:10:37.120> like<00:10:37.279> larger<00:10:37.560> dii<00:10:38.000> protocols 00:10:38.790 --> 00:10:38.800 align:start position:0% different like larger dii protocols 00:10:38.800 --> 00:10:40.829 align:start position:0% different like larger dii protocols about<00:10:39.079> like<00:10:39.200> how<00:10:39.360> you<00:10:39.560> minimize<00:10:40.399> potential 00:10:40.829 --> 00:10:40.839 align:start position:0% about like how you minimize potential 00:10:40.839 --> 00:10:42.990 align:start position:0% about like how you minimize potential contagion<00:10:41.399> and<00:10:41.680> and<00:10:41.920> and<00:10:42.120> things<00:10:42.360> from<00:10:42.680> uh 00:10:42.990 --> 00:10:43.000 align:start position:0% contagion and and and things from uh 00:10:43.000 --> 00:10:44.069 align:start position:0% contagion and and and things from uh things<00:10:43.200> from 00:10:44.069 --> 00:10:44.079 align:start position:0% things from 00:10:44.079 --> 00:10:47.509 align:start position:0% things from spreading<00:10:45.079> uh<00:10:45.279> finally<00:10:45.880> uh<00:10:46.079> or<00:10:46.639> additionally 00:10:47.509 --> 00:10:47.519 align:start position:0% spreading uh finally uh or additionally 00:10:47.519 --> 00:10:48.949 align:start position:0% spreading uh finally uh or additionally um<00:10:47.680> incident<00:10:48.040> post-mortems<00:10:48.600> are<00:10:48.760> really 00:10:48.949 --> 00:10:48.959 align:start position:0% um incident post-mortems are really 00:10:48.959 --> 00:10:50.790 align:start position:0% um incident post-mortems are really important<00:10:49.399> so<00:10:49.880> uh<00:10:50.000> this<00:10:50.079> is<00:10:50.200> another<00:10:50.480> call<00:10:50.639> out 00:10:50.790 --> 00:10:50.800 align:start position:0% important so uh this is another call out 00:10:50.800 --> 00:10:52.310 align:start position:0% important so uh this is another call out to<00:10:50.920> like<00:10:51.040> the<00:10:51.120> urine<00:10:51.360> GitHub<00:10:51.720> repository 00:10:52.310 --> 00:10:52.320 align:start position:0% to like the urine GitHub repository 00:10:52.320 --> 00:10:53.829 align:start position:0% to like the urine GitHub repository where<00:10:52.560> you<00:10:52.680> can<00:10:52.800> see<00:10:53.040> that<00:10:53.440> every<00:10:53.680> time 00:10:53.829 --> 00:10:53.839 align:start position:0% where you can see that every time 00:10:53.839 --> 00:10:55.110 align:start position:0% where you can see that every time there's<00:10:54.079> been<00:10:54.240> something<00:10:54.480> that<00:10:54.600> has<00:10:54.800> happened 00:10:55.110 --> 00:10:55.120 align:start position:0% there's been something that has happened 00:10:55.120 --> 00:10:57.350 align:start position:0% there's been something that has happened you<00:10:55.200> can<00:10:55.560> uh<00:10:55.680> see<00:10:56.399> what<00:10:56.639> they<00:10:56.880> what<00:10:56.959> the<00:10:57.079> team 00:10:57.350 --> 00:10:57.360 align:start position:0% you can uh see what they what the team 00:10:57.360 --> 00:10:59.670 align:start position:0% you can uh see what they what the team did<00:10:57.600> how<00:10:57.760> they<00:10:57.880> found<00:10:58.160> out<00:10:58.440> and<00:10:58.560> then<00:10:58.760> also<00:10:59.040> how 00:10:59.670 --> 00:10:59.680 align:start position:0% did how they found out and then also how 00:10:59.680 --> 00:11:01.990 align:start position:0% did how they found out and then also how they'll<00:10:59.920> be<00:11:00.120> improving<00:11:00.560> in<00:11:00.639> the<00:11:00.760> future<00:11:01.160> to<00:11:01.880> uh 00:11:01.990 --> 00:11:02.000 align:start position:0% they'll be improving in the future to uh 00:11:02.000 --> 00:11:04.030 align:start position:0% they'll be improving in the future to uh to<00:11:02.200> avoid<00:11:02.560> that<00:11:02.680> sort<00:11:02.839> of 00:11:04.030 --> 00:11:04.040 align:start position:0% to avoid that sort of 00:11:04.040 --> 00:11:06.670 align:start position:0% to avoid that sort of issue<00:11:05.040> and<00:11:05.399> monitoring<00:11:06.040> uh<00:11:06.160> mirroring 00:11:06.670 --> 00:11:06.680 align:start position:0% issue and monitoring uh mirroring 00:11:06.680 --> 00:11:08.190 align:start position:0% issue and monitoring uh mirroring monitoring<00:11:07.279> I<00:11:07.320> think<00:11:07.440> is<00:11:07.600> quite<00:11:07.800> important 00:11:08.190 --> 00:11:08.200 align:start position:0% monitoring I think is quite important 00:11:08.200 --> 00:11:10.190 align:start position:0% monitoring I think is quite important like<00:11:08.320> a<00:11:08.399> lot<00:11:08.519> of<00:11:08.639> teams<00:11:09.040> only<00:11:09.440> will<00:11:09.680> run<00:11:10.040> like 00:11:10.190 --> 00:11:10.200 align:start position:0% like a lot of teams only will run like 00:11:10.200 --> 00:11:11.990 align:start position:0% like a lot of teams only will run like their<00:11:10.399> critical<00:11:10.839> monitoring<00:11:11.519> against<00:11:11.839> their 00:11:11.990 --> 00:11:12.000 align:start position:0% their critical monitoring against their 00:11:12.000 --> 00:11:14.269 align:start position:0% their critical monitoring against their main<00:11:12.279> net<00:11:12.480> smart<00:11:12.800> contracts<00:11:13.600> um<00:11:13.720> and<00:11:13.880> that's 00:11:14.269 --> 00:11:14.279 align:start position:0% main net smart contracts um and that's 00:11:14.279 --> 00:11:16.710 align:start position:0% main net smart contracts um and that's handy<00:11:14.920> but<00:11:15.720> uh<00:11:15.920> the<00:11:16.120> things<00:11:16.360> that<00:11:16.519> are 00:11:16.710 --> 00:11:16.720 align:start position:0% handy but uh the things that are 00:11:16.720 --> 00:11:18.190 align:start position:0% handy but uh the things that are actually<00:11:16.920> going<00:11:17.120> to<00:11:17.279> trigger<00:11:17.600> to<00:11:17.760> maybe<00:11:18.040> like 00:11:18.190 --> 00:11:18.200 align:start position:0% actually going to trigger to maybe like 00:11:18.200 --> 00:11:19.750 align:start position:0% actually going to trigger to maybe like pause<00:11:18.480> your<00:11:18.680> smart<00:11:19.000> contract<00:11:19.360> in<00:11:19.440> the<00:11:19.560> event 00:11:19.750 --> 00:11:19.760 align:start position:0% pause your smart contract in the event 00:11:19.760 --> 00:11:21.870 align:start position:0% pause your smart contract in the event of<00:11:19.920> emergency<00:11:20.680> maybe<00:11:20.920> it<00:11:21.000> will<00:11:21.240> never<00:11:21.600> happen 00:11:21.870 --> 00:11:21.880 align:start position:0% of emergency maybe it will never happen 00:11:21.880 --> 00:11:23.829 align:start position:0% of emergency maybe it will never happen or<00:11:22.040> maybe<00:11:22.240> it<00:11:22.279> will<00:11:22.519> happen<00:11:22.800> like<00:11:22.959> once<00:11:23.200> a<00:11:23.399> year 00:11:23.829 --> 00:11:23.839 align:start position:0% or maybe it will happen like once a year 00:11:23.839 --> 00:11:25.829 align:start position:0% or maybe it will happen like once a year and<00:11:23.959> so<00:11:24.120> how<00:11:24.240> can<00:11:24.360> you<00:11:24.560> really<00:11:24.839> be<00:11:25.079> sure<00:11:25.720> that 00:11:25.829 --> 00:11:25.839 align:start position:0% and so how can you really be sure that 00:11:25.839 --> 00:11:27.710 align:start position:0% and so how can you really be sure that it's<00:11:26.000> going<00:11:26.160> to<00:11:26.320> be<00:11:26.519> there<00:11:26.839> the<00:11:26.959> moment<00:11:27.240> of<00:11:27.560> and 00:11:27.710 --> 00:11:27.720 align:start position:0% it's going to be there the moment of and 00:11:27.720 --> 00:11:29.670 align:start position:0% it's going to be there the moment of and a<00:11:27.800> lot<00:11:27.920> of<00:11:28.079> the<00:11:28.279> these<00:11:28.600> these<00:11:28.760> tools<00:11:29.000> are<00:11:29.360> great 00:11:29.670 --> 00:11:29.680 align:start position:0% a lot of the these these tools are great 00:11:29.680 --> 00:11:30.550 align:start position:0% a lot of the these these tools are great and<00:11:29.760> I'm<00:11:29.880> sure<00:11:30.040> that<00:11:30.160> they<00:11:30.279> have<00:11:30.399> some 00:11:30.550 --> 00:11:30.560 align:start position:0% and I'm sure that they have some 00:11:30.560 --> 00:11:32.590 align:start position:0% and I'm sure that they have some internal<00:11:30.959> simulation<00:11:31.519> capabilities<00:11:32.320> but<00:11:32.440> if 00:11:32.590 --> 00:11:32.600 align:start position:0% internal simulation capabilities but if 00:11:32.600 --> 00:11:34.829 align:start position:0% internal simulation capabilities but if you<00:11:32.720> can<00:11:32.959> also<00:11:33.240> run<00:11:33.480> your<00:11:33.680> monitoring<00:11:34.360> against 00:11:34.829 --> 00:11:34.839 align:start position:0% you can also run your monitoring against 00:11:34.839 --> 00:11:36.629 align:start position:0% you can also run your monitoring against these<00:11:35.040> like<00:11:35.240> simulated<00:11:35.760> networks<00:11:36.360> so<00:11:36.519> that 00:11:36.629 --> 00:11:36.639 align:start position:0% these like simulated networks so that 00:11:36.639 --> 00:11:38.509 align:start position:0% these like simulated networks so that you<00:11:36.720> can<00:11:36.920> make<00:11:37.120> sure<00:11:37.920> um<00:11:38.040> that<00:11:38.160> it's<00:11:38.320> all 00:11:38.509 --> 00:11:38.519 align:start position:0% you can make sure um that it's all 00:11:38.519 --> 00:11:39.710 align:start position:0% you can make sure um that it's all functioning<00:11:38.920> the<00:11:39.000> way<00:11:39.120> that<00:11:39.240> you<00:11:39.360> think<00:11:39.519> it's 00:11:39.710 --> 00:11:39.720 align:start position:0% functioning the way that you think it's 00:11:39.720 --> 00:11:41.470 align:start position:0% functioning the way that you think it's functioning<00:11:40.480> um<00:11:40.639> I<00:11:40.720> think<00:11:40.920> that's<00:11:41.279> that's 00:11:41.470 --> 00:11:41.480 align:start position:0% functioning um I think that's that's 00:11:41.480 --> 00:11:42.350 align:start position:0% functioning um I think that's that's pretty 00:11:42.350 --> 00:11:42.360 align:start position:0% pretty 00:11:42.360 --> 00:11:44.590 align:start position:0% pretty key<00:11:43.360> so<00:11:43.480> in<00:11:43.600> the<00:11:43.680> final<00:11:43.920> few<00:11:44.120> minutes<00:11:44.480> um 00:11:44.590 --> 00:11:44.600 align:start position:0% key so in the final few minutes um 00:11:44.600 --> 00:11:46.629 align:start position:0% key so in the final few minutes um before<00:11:45.120> I'll<00:11:45.360> leave<00:11:45.560> a<00:11:45.639> few<00:11:45.760> minutes<00:11:46.279> uh<00:11:46.480> we'll 00:11:46.629 --> 00:11:46.639 align:start position:0% before I'll leave a few minutes uh we'll 00:11:46.639 --> 00:11:48.110 align:start position:0% before I'll leave a few minutes uh we'll have<00:11:46.760> a<00:11:46.800> few<00:11:46.959> minutes<00:11:47.160> for<00:11:47.360> questions<00:11:47.920> I<00:11:48.040> just 00:11:48.110 --> 00:11:48.120 align:start position:0% have a few minutes for questions I just 00:11:48.120 --> 00:11:49.790 align:start position:0% have a few minutes for questions I just wanted<00:11:48.360> to<00:11:48.440> show<00:11:48.600> you<00:11:48.760> the<00:11:49.000> the<00:11:49.120> open<00:11:49.360> source 00:11:49.790 --> 00:11:49.800 align:start position:0% wanted to show you the the open source 00:11:49.800 --> 00:11:52.030 align:start position:0% wanted to show you the the open source repository<00:11:50.800> uh<00:11:50.920> that<00:11:51.040> I<00:11:51.200> la<00:11:51.480> that<00:11:51.560> I<00:11:51.680> released 00:11:52.030 --> 00:11:52.040 align:start position:0% repository uh that I la that I released 00:11:52.040 --> 00:11:53.990 align:start position:0% repository uh that I la that I released a<00:11:52.120> couple<00:11:52.360> weeks<00:11:52.560> ago<00:11:53.079> with<00:11:53.360> all<00:11:53.519> the<00:11:53.639> tools 00:11:53.990 --> 00:11:54.000 align:start position:0% a couple weeks ago with all the tools 00:11:54.000 --> 00:11:56.350 align:start position:0% a couple weeks ago with all the tools that<00:11:54.160> I<00:11:54.320> use<00:11:54.600> to<00:11:54.720> run<00:11:54.959> these<00:11:55.079> for<00:11:55.320> protocols<00:11:56.279> um 00:11:56.350 --> 00:11:56.360 align:start position:0% that I use to run these for protocols um 00:11:56.360 --> 00:11:58.190 align:start position:0% that I use to run these for protocols um so<00:11:56.519> it<00:11:56.639> includes<00:11:57.120> like<00:11:57.200> a<00:11:57.320> Foundry<00:11:57.720> and<00:11:57.880> hard 00:11:58.190 --> 00:11:58.200 align:start position:0% so it includes like a Foundry and hard 00:11:58.200 --> 00:12:00.269 align:start position:0% so it includes like a Foundry and hard hat<00:11:58.360> setup<00:11:58.680> for<00:11:58.880> like<00:11:59.279> validating<00:11:59.959> different 00:12:00.269 --> 00:12:00.279 align:start position:0% hat setup for like validating different 00:12:00.279 --> 00:12:02.470 align:start position:0% hat setup for like validating different like<00:12:00.440> war<00:12:00.639> game<00:12:00.880> scenarios<00:12:01.880> um<00:12:01.959> on<00:12:02.079> a<00:12:02.240> local 00:12:02.470 --> 00:12:02.480 align:start position:0% like war game scenarios um on a local 00:12:02.480 --> 00:12:03.870 align:start position:0% like war game scenarios um on a local Fork<00:12:03.079> it<00:12:03.200> contains<00:12:03.480> a<00:12:03.600> bunch<00:12:03.760> of 00:12:03.870 --> 00:12:03.880 align:start position:0% Fork it contains a bunch of 00:12:03.880 --> 00:12:05.310 align:start position:0% Fork it contains a bunch of configuration<00:12:04.399> scripts<00:12:04.760> for<00:12:04.880> setting<00:12:05.160> up 00:12:05.310 --> 00:12:05.320 align:start position:0% configuration scripts for setting up 00:12:05.320 --> 00:12:07.509 align:start position:0% configuration scripts for setting up virtual<00:12:05.680> test<00:12:05.959> Nets<00:12:06.360> with<00:12:06.720> block<00:12:07.040> explorers 00:12:07.509 --> 00:12:07.519 align:start position:0% virtual test Nets with block explorers 00:12:07.519 --> 00:12:09.629 align:start position:0% virtual test Nets with block explorers to<00:12:07.680> run<00:12:07.959> these<00:12:08.720> uh<00:12:08.959> templates<00:12:09.399> for<00:12:09.519> the 00:12:09.629 --> 00:12:09.639 align:start position:0% to run these uh templates for the 00:12:09.639 --> 00:12:12.750 align:start position:0% to run these uh templates for the tabletop<00:12:10.360> exercise<00:12:11.360> uh<00:12:11.519> monitoring<00:12:12.200> and<00:12:12.399> Bot 00:12:12.750 --> 00:12:12.760 align:start position:0% tabletop exercise uh monitoring and Bot 00:12:12.760 --> 00:12:14.910 align:start position:0% tabletop exercise uh monitoring and Bot Services<00:12:13.360> which<00:12:13.519> we<00:12:13.639> forked<00:12:14.040> from<00:12:14.639> um<00:12:14.760> an 00:12:14.910 --> 00:12:14.920 align:start position:0% Services which we forked from um an 00:12:14.920 --> 00:12:17.430 align:start position:0% Services which we forked from um an optimism<00:12:15.480> repository<00:12:16.480> and<00:12:16.680> also<00:12:17.040> like<00:12:17.199> a 00:12:17.430 --> 00:12:17.440 align:start position:0% optimism repository and also like a 00:12:17.440 --> 00:12:19.550 align:start position:0% optimism repository and also like a stack<00:12:17.920> for<00:12:18.279> setting<00:12:18.600> up<00:12:18.800> like<00:12:18.880> a<00:12:19.000> Prometheus 00:12:19.550 --> 00:12:19.560 align:start position:0% stack for setting up like a Prometheus 00:12:19.560 --> 00:12:22.030 align:start position:0% stack for setting up like a Prometheus grafana<00:12:20.360> instance<00:12:20.800> so<00:12:21.000> like<00:12:21.160> this<00:12:21.240> is<00:12:21.480> all 00:12:22.030 --> 00:12:22.040 align:start position:0% grafana instance so like this is all 00:12:22.040 --> 00:12:24.590 align:start position:0% grafana instance so like this is all that<00:12:22.240> I<00:12:22.440> use<00:12:22.800> when<00:12:22.959> I<00:12:23.079> run<00:12:23.360> a<00:12:23.680> when<00:12:23.800> I<00:12:23.920> run<00:12:24.279> a<00:12:24.399> war 00:12:24.590 --> 00:12:24.600 align:start position:0% that I use when I run a when I run a war 00:12:24.600 --> 00:12:26.430 align:start position:0% that I use when I run a when I run a war game<00:12:24.800> so<00:12:24.959> this<00:12:25.079> should<00:12:25.240> be<00:12:25.399> all<00:12:26.079> uh<00:12:26.199> that<00:12:26.320> you 00:12:26.430 --> 00:12:26.440 align:start position:0% game so this should be all uh that you 00:12:26.440 --> 00:12:28.069 align:start position:0% game so this should be all uh that you would<00:12:26.760> need<00:12:27.000> to<00:12:27.199> potentially<00:12:27.639> use<00:12:27.880> if<00:12:28.000> you 00:12:28.069 --> 00:12:28.079 align:start position:0% would need to potentially use if you 00:12:28.079 --> 00:12:29.870 align:start position:0% would need to potentially use if you want<00:12:28.240> to<00:12:28.399> run<00:12:28.560> one<00:12:28.680> of<00:12:28.800> these<00:12:28.920> with<00:12:29.040> your<00:12:29.279> own 00:12:29.870 --> 00:12:29.880 align:start position:0% want to run one of these with your own 00:12:29.880 --> 00:12:31.790 align:start position:0% want to run one of these with your own uh<00:12:30.000> with<00:12:30.079> your<00:12:30.199> own 00:12:31.790 --> 00:12:31.800 align:start position:0% uh with your own 00:12:31.800 --> 00:12:34.389 align:start position:0% uh with your own protocols<00:12:32.800> so<00:12:33.079> this<00:12:33.160> is<00:12:33.320> just<00:12:33.480> a<00:12:33.760> a<00:12:33.920> brief<00:12:34.199> look 00:12:34.389 --> 00:12:34.399 align:start position:0% protocols so this is just a a brief look 00:12:34.399 --> 00:12:36.030 align:start position:0% protocols so this is just a a brief look at<00:12:34.560> like<00:12:34.720> what<00:12:34.839> the<00:12:34.959> tabletop<00:12:35.440> script<00:12:35.760> looks 00:12:36.030 --> 00:12:36.040 align:start position:0% at like what the tabletop script looks 00:12:36.040 --> 00:12:38.470 align:start position:0% at like what the tabletop script looks like<00:12:36.399> and<00:12:36.480> so<00:12:36.600> we'll<00:12:36.760> be<00:12:36.880> on<00:12:36.959> a<00:12:37.199> call<00:12:37.560> usually 00:12:38.470 --> 00:12:38.480 align:start position:0% like and so we'll be on a call usually 00:12:38.480 --> 00:12:40.069 align:start position:0% like and so we'll be on a call usually uh<00:12:38.560> it's<00:12:38.720> like<00:12:38.839> an<00:12:39.000> hour<00:12:39.360> hour<00:12:39.519> and<00:12:39.639> a<00:12:39.760> half 00:12:40.069 --> 00:12:40.079 align:start position:0% uh it's like an hour hour and a half 00:12:40.079 --> 00:12:41.389 align:start position:0% uh it's like an hour hour and a half with<00:12:40.240> like<00:12:40.360> the<00:12:40.519> whole<00:12:40.959> with<00:12:41.079> the<00:12:41.199> whole 00:12:41.389 --> 00:12:41.399 align:start position:0% with like the whole with the whole 00:12:41.399 --> 00:12:42.990 align:start position:0% with like the whole with the whole protocol<00:12:41.839> team<00:12:42.120> or<00:12:42.320> with<00:12:42.519> like<00:12:42.639> if<00:12:42.720> it's<00:12:42.839> a 00:12:42.990 --> 00:12:43.000 align:start position:0% protocol team or with like if it's a 00:12:43.000 --> 00:12:44.590 align:start position:0% protocol team or with like if it's a very<00:12:43.160> large<00:12:43.440> protocol<00:12:43.839> maybe<00:12:44.040> it's<00:12:44.120> a<00:12:44.279> subset 00:12:44.590 --> 00:12:44.600 align:start position:0% very large protocol maybe it's a subset 00:12:44.600 --> 00:12:47.310 align:start position:0% very large protocol maybe it's a subset of<00:12:44.720> the<00:12:44.800> protocol<00:12:45.600> uh<00:12:45.880> a<00:12:46.040> subset<00:12:46.399> of<00:12:46.519> the<00:12:46.639> team 00:12:47.310 --> 00:12:47.320 align:start position:0% of the protocol uh a subset of the team 00:12:47.320 --> 00:12:48.990 align:start position:0% of the protocol uh a subset of the team um<00:12:47.440> but<00:12:47.560> always<00:12:47.880> cross<00:12:48.199> functional<00:12:48.800> and<00:12:48.880> we 00:12:48.990 --> 00:12:49.000 align:start position:0% um but always cross functional and we 00:12:49.000 --> 00:12:51.470 align:start position:0% um but always cross functional and we just<00:12:49.160> talk<00:12:49.480> through<00:12:50.360> like<00:12:50.519> in<00:12:50.680> this<00:12:50.920> exercise 00:12:51.470 --> 00:12:51.480 align:start position:0% just talk through like in this exercise 00:12:51.480 --> 00:12:53.430 align:start position:0% just talk through like in this exercise we're<00:12:51.680> going<00:12:51.920> to<00:12:52.639> um<00:12:52.760> discuss<00:12:53.199> various 00:12:53.430 --> 00:12:53.440 align:start position:0% we're going to um discuss various 00:12:53.440 --> 00:12:54.910 align:start position:0% we're going to um discuss various scenarios<00:12:53.880> that<00:12:54.000> you'll<00:12:54.160> need<00:12:54.320> to<00:12:54.480> detect<00:12:54.760> and 00:12:54.910 --> 00:12:54.920 align:start position:0% scenarios that you'll need to detect and 00:12:54.920 --> 00:12:57.629 align:start position:0% scenarios that you'll need to detect and respond<00:12:55.240> to<00:12:55.399> issues<00:12:56.160> what<00:12:56.279> we<00:12:56.440> want<00:12:56.600> to<00:12:56.880> like 00:12:57.629 --> 00:12:57.639 align:start position:0% respond to issues what we want to like 00:12:57.639 --> 00:13:00.269 align:start position:0% respond to issues what we want to like uh<00:12:58.240> understand<00:12:58.560> is<00:12:58.760> typically<00:12:59.399> like<00:12:59.880> uh<00:13:00.160> do 00:13:00.269 --> 00:13:00.279 align:start position:0% uh understand is typically like uh do 00:13:00.279 --> 00:13:02.069 align:start position:0% uh understand is typically like uh do you<00:13:00.480> know<00:13:00.720> what<00:13:00.839> the<00:13:00.959> key<00:13:01.160> dependency<00:13:01.800> of<00:13:01.920> your 00:13:02.069 --> 00:13:02.079 align:start position:0% you know what the key dependency of your 00:13:02.079 --> 00:13:03.910 align:start position:0% you know what the key dependency of your protocol<00:13:02.639> is<00:13:03.079> and<00:13:03.240> you<00:13:03.399> know<00:13:03.639> what<00:13:03.760> would 00:13:03.910 --> 00:13:03.920 align:start position:0% protocol is and you know what would 00:13:03.920 --> 00:13:05.990 align:start position:0% protocol is and you know what would happen<00:13:04.160> if<00:13:04.279> it<00:13:04.440> fails<00:13:05.240> is<00:13:05.360> there<00:13:05.560> sufficient 00:13:05.990 --> 00:13:06.000 align:start position:0% happen if it fails is there sufficient 00:13:06.000 --> 00:13:07.629 align:start position:0% happen if it fails is there sufficient monitoring<00:13:06.440> in<00:13:06.560> infra<00:13:06.880> to<00:13:07.199> detect<00:13:07.480> and 00:13:07.629 --> 00:13:07.639 align:start position:0% monitoring in infra to detect and 00:13:07.639 --> 00:13:09.790 align:start position:0% monitoring in infra to detect and respond<00:13:07.959> to<00:13:08.079> these<00:13:08.240> failures<00:13:09.120> um<00:13:09.240> do<00:13:09.360> you 00:13:09.790 --> 00:13:09.800 align:start position:0% respond to these failures um do you 00:13:09.800 --> 00:13:11.949 align:start position:0% respond to these failures um do you understand<00:13:10.000> who<00:13:10.279> has<00:13:10.519> admin<00:13:11.240> capabilities 00:13:11.949 --> 00:13:11.959 align:start position:0% understand who has admin capabilities 00:13:11.959 --> 00:13:14.310 align:start position:0% understand who has admin capabilities within<00:13:12.240> your<00:13:12.600> within<00:13:12.839> your<00:13:13.040> protocol<00:13:14.040> um<00:13:14.160> are 00:13:14.310 --> 00:13:14.320 align:start position:0% within your within your protocol um are 00:13:14.320 --> 00:13:16.350 align:start position:0% within your within your protocol um are there<00:13:14.519> backups<00:13:14.920> in<00:13:15.160> place<00:13:15.480> so<00:13:15.839> these<00:13:15.959> are<00:13:16.160> the 00:13:16.350 --> 00:13:16.360 align:start position:0% there backups in place so these are the 00:13:16.360 --> 00:13:18.350 align:start position:0% there backups in place so these are the this<00:13:16.480> is<00:13:16.639> almost<00:13:17.120> an<00:13:17.279> additional<00:13:17.760> information 00:13:18.350 --> 00:13:18.360 align:start position:0% this is almost an additional information 00:13:18.360 --> 00:13:20.710 align:start position:0% this is almost an additional information gathering<00:13:18.720> step<00:13:19.000> for<00:13:19.240> us<00:13:19.880> um<00:13:20.040> so<00:13:20.240> that<00:13:20.360> we<00:13:20.480> can 00:13:20.710 --> 00:13:20.720 align:start position:0% gathering step for us um so that we can 00:13:20.720 --> 00:13:23.550 align:start position:0% gathering step for us um so that we can design<00:13:21.120> the<00:13:21.320> best<00:13:21.880> uh<00:13:22.000> live<00:13:22.440> scenario<00:13:23.440> and 00:13:23.550 --> 00:13:23.560 align:start position:0% design the best uh live scenario and 00:13:23.560 --> 00:13:25.069 align:start position:0% design the best uh live scenario and then<00:13:23.680> the<00:13:23.880> questions<00:13:24.240> that<00:13:24.360> we<00:13:24.560> ask<00:13:24.760> in<00:13:24.920> each 00:13:25.069 --> 00:13:25.079 align:start position:0% then the questions that we ask in each 00:13:25.079 --> 00:13:27.590 align:start position:0% then the questions that we ask in each one<00:13:25.199> of<00:13:25.320> these<00:13:25.480> scenarios<00:13:25.959> is<00:13:26.160> always<00:13:27.040> um<00:13:27.440> like 00:13:27.590 --> 00:13:27.600 align:start position:0% one of these scenarios is always um like 00:13:27.600 --> 00:13:29.269 align:start position:0% one of these scenarios is always um like how<00:13:27.760> did<00:13:27.880> you<00:13:28.240> discover<00:13:28.519> this<00:13:28.680> issue<00:13:29.120> so<00:13:29.199> if 00:13:29.269 --> 00:13:29.279 align:start position:0% how did you discover this issue so if 00:13:29.279 --> 00:13:31.550 align:start position:0% how did you discover this issue so if we're<00:13:29.440> looking<00:13:29.680> at<00:13:29.880> maybe<00:13:30.120> an<00:13:30.440> an<00:13:30.560> L2<00:13:31.399> and 00:13:31.550 --> 00:13:31.560 align:start position:0% we're looking at maybe an an L2 and 00:13:31.560 --> 00:13:33.470 align:start position:0% we're looking at maybe an an L2 and somebody<00:13:31.880> submits<00:13:32.320> some<00:13:32.440> sort<00:13:32.600> of<00:13:32.720> fraudulent 00:13:33.470 --> 00:13:33.480 align:start position:0% somebody submits some sort of fraudulent 00:13:33.480 --> 00:13:35.790 align:start position:0% somebody submits some sort of fraudulent uh<00:13:33.560> withdrawal<00:13:34.040> proof<00:13:34.560> how<00:13:34.680> did<00:13:34.839> you<00:13:35.040> find<00:13:35.279> out 00:13:35.790 --> 00:13:35.800 align:start position:0% uh withdrawal proof how did you find out 00:13:35.800 --> 00:13:37.990 align:start position:0% uh withdrawal proof how did you find out did<00:13:35.959> you<00:13:36.160> wait<00:13:36.360> until<00:13:36.639> somebody<00:13:37.079> rate<00:13:37.399> like<00:13:37.839> uh 00:13:37.990 --> 00:13:38.000 align:start position:0% did you wait until somebody rate like uh 00:13:38.000 --> 00:13:39.949 align:start position:0% did you wait until somebody rate like uh reached<00:13:38.480> out<00:13:38.680> on<00:13:38.920> Twitter<00:13:39.279> or<00:13:39.480> Discord<00:13:39.839> and 00:13:39.949 --> 00:13:39.959 align:start position:0% reached out on Twitter or Discord and 00:13:39.959 --> 00:13:42.150 align:start position:0% reached out on Twitter or Discord and said<00:13:40.199> hey<00:13:40.399> it<00:13:40.560> looks<00:13:40.760> like<00:13:41.160> you<00:13:41.279> know<00:13:41.440> XLT<00:13:42.079> is 00:13:42.150 --> 00:13:42.160 align:start position:0% said hey it looks like you know XLT is 00:13:42.160 --> 00:13:43.910 align:start position:0% said hey it looks like you know XLT is under<00:13:42.399> attack<00:13:42.720> right<00:13:42.880> now<00:13:43.279> or<00:13:43.480> did<00:13:43.600> you<00:13:43.760> have 00:13:43.910 --> 00:13:43.920 align:start position:0% under attack right now or did you have 00:13:43.920 --> 00:13:45.230 align:start position:0% under attack right now or did you have some<00:13:44.120> internal<00:13:44.600> system<00:13:44.880> that<00:13:45.000> would<00:13:45.120> have 00:13:45.230 --> 00:13:45.240 align:start position:0% some internal system that would have 00:13:45.240 --> 00:13:47.710 align:start position:0% some internal system that would have alerted<00:13:45.639> you<00:13:45.760> within<00:13:46.120> seconds<00:13:46.959> and<00:13:47.079> so<00:13:47.440> first 00:13:47.710 --> 00:13:47.720 align:start position:0% alerted you within seconds and so first 00:13:47.720 --> 00:13:49.670 align:start position:0% alerted you within seconds and so first how<00:13:47.839> did<00:13:47.959> you<00:13:48.120> find<00:13:48.360> out<00:13:48.839> do<00:13:48.959> you<00:13:49.079> know<00:13:49.279> who<00:13:49.399> to 00:13:49.670 --> 00:13:49.680 align:start position:0% how did you find out do you know who to 00:13:49.680 --> 00:13:51.990 align:start position:0% how did you find out do you know who to gather<00:13:50.320> do<00:13:50.560> like<00:13:50.720> does<00:13:50.880> somebody<00:13:51.600> become<00:13:51.880> an 00:13:51.990 --> 00:13:52.000 align:start position:0% gather do like does somebody become an 00:13:52.000 --> 00:13:54.310 align:start position:0% gather do like does somebody become an Incident<00:13:52.360> Commander<00:13:52.839> here<00:13:53.440> do<00:13:53.560> you<00:13:53.800> have<00:13:54.040> like 00:13:54.310 --> 00:13:54.320 align:start position:0% Incident Commander here do you have like 00:13:54.320 --> 00:13:56.829 align:start position:0% Incident Commander here do you have like an<00:13:54.440> on<00:13:54.800> call<00:13:55.040> team<00:13:55.600> or<00:13:55.759> is<00:13:55.880> it<00:13:56.079> like<00:13:56.519> whichever 00:13:56.829 --> 00:13:56.839 align:start position:0% an on call team or is it like whichever 00:13:56.839 --> 00:13:58.310 align:start position:0% an on call team or is it like whichever Engineers<00:13:57.320> awake<00:13:57.639> somewhere<00:13:57.920> in<00:13:58.000> the<00:13:58.079> world 00:13:58.310 --> 00:13:58.320 align:start position:0% Engineers awake somewhere in the world 00:13:58.320 --> 00:14:00.710 align:start position:0% Engineers awake somewhere in the world is<00:13:58.480> the<00:13:58.560> one<00:13:58.680> that<00:13:58.800> has<00:13:59.160> to<00:13:59.680> to<00:13:59.880> deal<00:14:00.120> with<00:14:00.320> this 00:14:00.710 --> 00:14:00.720 align:start position:0% is the one that has to to deal with this 00:14:00.720 --> 00:14:03.069 align:start position:0% is the one that has to to deal with this like<00:14:00.920> is<00:14:01.160> that<00:14:01.560> uh<00:14:01.720> how<00:14:01.880> does<00:14:02.079> that<00:14:02.240> work<00:14:03.000> do 00:14:03.069 --> 00:14:03.079 align:start position:0% like is that uh how does that work do 00:14:03.079 --> 00:14:05.629 align:start position:0% like is that uh how does that work do you<00:14:03.240> have<00:14:03.320> a<00:14:03.519> response<00:14:03.959> plan<00:14:04.240> for<00:14:04.560> this<00:14:05.120> if<00:14:05.320> not 00:14:05.629 --> 00:14:05.639 align:start position:0% you have a response plan for this if not 00:14:05.639 --> 00:14:08.790 align:start position:0% you have a response plan for this if not why<00:14:05.839> not<00:14:06.079> is<00:14:06.199> it<00:14:06.320> just<00:14:06.480> too<00:14:07.160> rare<00:14:08.160> um<00:14:08.440> and<00:14:08.560> then 00:14:08.790 --> 00:14:08.800 align:start position:0% why not is it just too rare um and then 00:14:08.800 --> 00:14:11.150 align:start position:0% why not is it just too rare um and then who<00:14:09.000> took<00:14:09.279> action<00:14:09.560> and<00:14:09.800> how<00:14:10.360> and<00:14:10.440> so<00:14:10.800> all<00:14:10.959> of 00:14:11.150 --> 00:14:11.160 align:start position:0% who took action and how and so all of 00:14:11.160 --> 00:14:12.550 align:start position:0% who took action and how and so all of these<00:14:11.399> questions<00:14:11.720> are<00:14:11.920> how<00:14:12.040> we<00:14:12.160> can 00:14:12.550 --> 00:14:12.560 align:start position:0% these questions are how we can 00:14:12.560 --> 00:14:14.269 align:start position:0% these questions are how we can understand<00:14:12.759> like<00:14:13.160> how<00:14:13.399> well<00:14:13.759> positioned<00:14:14.120> a 00:14:14.269 --> 00:14:14.279 align:start position:0% understand like how well positioned a 00:14:14.279 --> 00:14:18.230 align:start position:0% understand like how well positioned a protocol<00:14:14.839> is<00:14:15.639> um<00:14:15.880> to<00:14:16.600> uh<00:14:16.759> actually<00:14:17.399> uh<00:14:17.480> to 00:14:18.230 --> 00:14:18.240 align:start position:0% protocol is um to uh actually uh to 00:14:18.240 --> 00:14:21.030 align:start position:0% protocol is um to uh actually uh to respond<00:14:19.240> uh<00:14:19.360> and<00:14:19.480> then<00:14:19.600> for<00:14:19.720> the<00:14:19.880> live<00:14:20.160> drill 00:14:21.030 --> 00:14:21.040 align:start position:0% respond uh and then for the live drill 00:14:21.040 --> 00:14:23.230 align:start position:0% respond uh and then for the live drill um<00:14:21.519> the<00:14:21.680> setup<00:14:22.079> steps<00:14:22.480> this<00:14:22.600> is<00:14:22.839> always<00:14:23.120> the 00:14:23.230 --> 00:14:23.240 align:start position:0% um the setup steps this is always the 00:14:23.240 --> 00:14:24.710 align:start position:0% um the setup steps this is always the part<00:14:23.360> that<00:14:23.480> takes<00:14:23.639> me<00:14:23.759> the<00:14:23.920> longest<00:14:24.480> but<00:14:24.600> we 00:14:24.710 --> 00:14:24.720 align:start position:0% part that takes me the longest but we 00:14:24.720 --> 00:14:26.629 align:start position:0% part that takes me the longest but we create<00:14:24.959> the<00:14:25.079> fork<00:14:25.440> run<00:14:25.639> the<00:14:25.800> Bots<00:14:26.160> brief<00:14:26.480> the 00:14:26.629 --> 00:14:26.639 align:start position:0% create the fork run the Bots brief the 00:14:26.639 --> 00:14:29.230 align:start position:0% create the fork run the Bots brief the team<00:14:27.240> I'll<00:14:27.360> send<00:14:27.600> them<00:14:27.800> some<00:14:28.000> sort<00:14:28.160> of<00:14:28.399> like<00:14:28.720> uh 00:14:29.230 --> 00:14:29.240 align:start position:0% team I'll send them some sort of like uh 00:14:29.240 --> 00:14:30.910 align:start position:0% team I'll send them some sort of like uh atic<00:14:29.480> message<00:14:29.800> of<00:14:30.000> like<00:14:30.079> you<00:14:30.199> know<00:14:30.519> you're<00:14:30.720> now 00:14:30.910 --> 00:14:30.920 align:start position:0% atic message of like you know you're now 00:14:30.920 --> 00:14:32.470 align:start position:0% atic message of like you know you're now in<00:14:31.079> like<00:14:31.199> a<00:14:31.399> very<00:14:31.759> you're<00:14:31.880> now<00:14:32.040> in<00:14:32.120> a<00:14:32.279> very 00:14:32.470 --> 00:14:32.480 align:start position:0% in like a very you're now in a very 00:14:32.480 --> 00:14:34.550 align:start position:0% in like a very you're now in a very realistic<00:14:33.000> simulation<00:14:33.720> where<00:14:34.160> this<00:14:34.360> really 00:14:34.550 --> 00:14:34.560 align:start position:0% realistic simulation where this really 00:14:34.560 --> 00:14:35.910 align:start position:0% realistic simulation where this really bad<00:14:34.720> thing's<00:14:34.959> about<00:14:35.120> to<00:14:35.279> happen<00:14:35.600> you<00:14:35.720> have<00:14:35.800> to 00:14:35.910 --> 00:14:35.920 align:start position:0% bad thing's about to happen you have to 00:14:35.920 --> 00:14:38.790 align:start position:0% bad thing's about to happen you have to treat<00:14:36.160> it<00:14:36.320> as<00:14:36.480> if<00:14:36.759> like<00:14:36.920> a<00:14:37.720> everything<00:14:38.120> was<00:14:38.519> uh 00:14:38.790 --> 00:14:38.800 align:start position:0% treat it as if like a everything was uh 00:14:38.800 --> 00:14:41.310 align:start position:0% treat it as if like a everything was uh as<00:14:38.920> if<00:14:39.040> it's<00:14:39.199> all<00:14:39.519> real<00:14:39.800> life<00:14:40.560> um<00:14:40.800> but<00:14:41.120> you 00:14:41.310 --> 00:14:41.320 align:start position:0% as if it's all real life um but you 00:14:41.320 --> 00:14:43.269 align:start position:0% as if it's all real life um but you typically<00:14:41.639> don't<00:14:41.839> need<00:14:42.040> to<00:14:42.600> encourage<00:14:43.079> that 00:14:43.269 --> 00:14:43.279 align:start position:0% typically don't need to encourage that 00:14:43.279 --> 00:14:46.189 align:start position:0% typically don't need to encourage that like<00:14:43.720> they'll<00:14:43.959> go<00:14:44.120> into<00:14:44.360> stressful<00:14:44.959> mode<00:14:45.440> and 00:14:46.189 --> 00:14:46.199 align:start position:0% like they'll go into stressful mode and 00:14:46.199 --> 00:14:47.710 align:start position:0% like they'll go into stressful mode and uh<00:14:46.440> everybody<00:14:46.759> wants<00:14:46.959> to<00:14:47.079> show<00:14:47.360> that<00:14:47.480> their 00:14:47.710 --> 00:14:47.720 align:start position:0% uh everybody wants to show that their 00:14:47.720 --> 00:14:49.150 align:start position:0% uh everybody wants to show that their internal<00:14:48.079> tooling<00:14:48.440> really<00:14:48.600> works<00:14:48.920> really 00:14:49.150 --> 00:14:49.160 align:start position:0% internal tooling really works really 00:14:49.160 --> 00:14:52.829 align:start position:0% internal tooling really works really well<00:14:49.759> and<00:14:49.920> so<00:14:50.360> um<00:14:51.160> uh<00:14:51.320> and<00:14:51.480> so<00:14:51.920> yeah<00:14:52.199> teams<00:14:52.639> we 00:14:52.829 --> 00:14:52.839 align:start position:0% well and so um uh and so yeah teams we 00:14:52.839 --> 00:14:55.350 align:start position:0% well and so um uh and so yeah teams we found<00:14:53.240> always<00:14:53.880> take<00:14:54.000> it<00:14:54.240> very<00:14:54.759> uh<00:14:54.959> very 00:14:55.350 --> 00:14:55.360 align:start position:0% found always take it very uh very 00:14:55.360 --> 00:14:58.110 align:start position:0% found always take it very uh very seriously<00:14:56.360> um<00:14:56.680> I<00:14:56.839> always<00:14:57.480> love<00:14:57.759> love<00:14:57.959> to 00:14:58.110 --> 00:14:58.120 align:start position:0% seriously um I always love love to 00:14:58.120 --> 00:15:00.350 align:start position:0% seriously um I always love love to observe<00:14:58.519> kind<00:14:58.639> of<00:14:58.800> the<00:14:59.199> especially<00:14:59.800> just<00:15:00.199> the 00:15:00.350 --> 00:15:00.360 align:start position:0% observe kind of the especially just the 00:15:00.360 --> 00:15:02.749 align:start position:0% observe kind of the especially just the conversations<00:15:01.040> between<00:15:01.360> like<00:15:01.519> Dev<00:15:01.920> and<00:15:02.360> comms 00:15:02.749 --> 00:15:02.759 align:start position:0% conversations between like Dev and comms 00:15:02.759 --> 00:15:04.509 align:start position:0% conversations between like Dev and comms where<00:15:02.880> it's<00:15:03.079> like<00:15:03.399> Communications<00:15:04.040> prepar<00:15:04.399> is 00:15:04.509 --> 00:15:04.519 align:start position:0% where it's like Communications prepar is 00:15:04.519 --> 00:15:06.150 align:start position:0% where it's like Communications prepar is like<00:15:04.639> a<00:15:04.759> statement<00:15:05.399> developers<00:15:05.759> are<00:15:05.880> like<00:15:06.040> no 00:15:06.150 --> 00:15:06.160 align:start position:0% like a statement developers are like no 00:15:06.160 --> 00:15:07.590 align:start position:0% like a statement developers are like no we<00:15:06.279> can't<00:15:06.399> say<00:15:06.600> that<00:15:06.759> at<00:15:06.839> all<00:15:07.040> or<00:15:07.199> developers 00:15:07.590 --> 00:15:07.600 align:start position:0% we can't say that at all or developers 00:15:07.600 --> 00:15:08.910 align:start position:0% we can't say that at all or developers want<00:15:07.720> to<00:15:07.839> say<00:15:07.959> we're<00:15:08.120> pausing<00:15:08.399> the<00:15:08.519> protocol 00:15:08.910 --> 00:15:08.920 align:start position:0% want to say we're pausing the protocol 00:15:08.920 --> 00:15:10.710 align:start position:0% want to say we're pausing the protocol and<00:15:09.040> Communications<00:15:09.759> is<00:15:09.920> like<00:15:10.240> no<00:15:10.399> we<00:15:10.519> can't 00:15:10.710 --> 00:15:10.720 align:start position:0% and Communications is like no we can't 00:15:10.720 --> 00:15:12.870 align:start position:0% and Communications is like no we can't say<00:15:10.959> that<00:15:11.240> like<00:15:11.600> so<00:15:12.040> that's<00:15:12.240> always<00:15:12.600> really 00:15:12.870 --> 00:15:12.880 align:start position:0% say that like so that's always really 00:15:12.880 --> 00:15:15.470 align:start position:0% say that like so that's always really interesting<00:15:13.600> uh<00:15:13.839> to<00:15:14.079> to<00:15:14.240> observe<00:15:14.560> how<00:15:14.680> that 00:15:15.470 --> 00:15:15.480 align:start position:0% interesting uh to to observe how that 00:15:15.480 --> 00:15:19.670 align:start position:0% interesting uh to to observe how that works<00:15:16.480> uh<00:15:16.639> we<00:15:17.160> have<00:15:18.160> um<00:15:18.959> uh<00:15:19.079> this<00:15:19.160> is<00:15:19.279> just<00:15:19.560> a 00:15:19.670 --> 00:15:19.680 align:start position:0% works uh we have um uh this is just a 00:15:19.680 --> 00:15:21.670 align:start position:0% works uh we have um uh this is just a view<00:15:19.880> of<00:15:20.040> like<00:15:20.160> a<00:15:20.279> tenderly<00:15:20.720> virtual<00:15:21.079> test<00:15:21.360> net 00:15:21.670 --> 00:15:21.680 align:start position:0% view of like a tenderly virtual test net 00:15:21.680 --> 00:15:23.550 align:start position:0% view of like a tenderly virtual test net so<00:15:22.040> I<00:15:22.160> found<00:15:22.399> that<00:15:22.560> this<00:15:22.639> is<00:15:22.839> like<00:15:23.160> I<00:15:23.240> used<00:15:23.440> to 00:15:23.550 --> 00:15:23.560 align:start position:0% so I found that this is like I used to 00:15:23.560 --> 00:15:25.590 align:start position:0% so I found that this is like I used to set<00:15:23.759> up<00:15:23.920> like<00:15:24.000> an<00:15:24.160> anvil<00:15:24.519> fork<00:15:25.079> and<00:15:25.199> a<00:15:25.320> block 00:15:25.590 --> 00:15:25.600 align:start position:0% set up like an anvil fork and a block 00:15:25.600 --> 00:15:27.870 align:start position:0% set up like an anvil fork and a block Scout<00:15:26.440> uh<00:15:26.560> drop<00:15:27.040> uh<00:15:27.120> and<00:15:27.240> a<00:15:27.320> block<00:15:27.560> Scout 00:15:27.870 --> 00:15:27.880 align:start position:0% Scout uh drop uh and a block Scout 00:15:27.880 --> 00:15:29.670 align:start position:0% Scout uh drop uh and a block Scout Explorer<00:15:28.759> um<00:15:29.079> that<00:15:29.120> would<00:15:29.279> always<00:15:29.440> take<00:15:29.560> me 00:15:29.670 --> 00:15:29.680 align:start position:0% Explorer um that would always take me 00:15:29.680 --> 00:15:32.230 align:start position:0% Explorer um that would always take me like<00:15:29.800> two<00:15:30.040> days<00:15:30.399> um<00:15:30.519> So<00:15:30.759> lately<00:15:31.079> I've<00:15:31.240> been<00:15:32.040> uh 00:15:32.230 --> 00:15:32.240 align:start position:0% like two days um So lately I've been uh 00:15:32.240 --> 00:15:34.269 align:start position:0% like two days um So lately I've been uh using<00:15:33.040> these<00:15:33.240> tools<00:15:33.600> but<00:15:33.720> you<00:15:33.800> can<00:15:33.920> run<00:15:34.160> these 00:15:34.269 --> 00:15:34.279 align:start position:0% using these tools but you can run these 00:15:34.279 --> 00:15:36.790 align:start position:0% using these tools but you can run these Forks<00:15:34.639> using<00:15:35.000> any<00:15:35.519> any<00:15:35.680> tools<00:15:36.440> but<00:15:36.560> this<00:15:36.639> is 00:15:36.790 --> 00:15:36.800 align:start position:0% Forks using any any tools but this is 00:15:36.800 --> 00:15:38.470 align:start position:0% Forks using any any tools but this is like<00:15:37.079> what<00:15:37.199> it<00:15:37.319> looks<00:15:37.519> like<00:15:37.680> when<00:15:37.800> I<00:15:37.920> set<00:15:38.079> up<00:15:38.319> a 00:15:38.470 --> 00:15:38.480 align:start position:0% like what it looks like when I set up a 00:15:38.480 --> 00:15:40.629 align:start position:0% like what it looks like when I set up a a<00:15:38.560> fork<00:15:38.839> of<00:15:38.959> main<00:15:39.240> net<00:15:40.000> um<00:15:40.160> and<00:15:40.279> then<00:15:40.399> this<00:15:40.480> is 00:15:40.629 --> 00:15:40.639 align:start position:0% a fork of main net um and then this is 00:15:40.639 --> 00:15:42.990 align:start position:0% a fork of main net um and then this is like<00:15:40.759> my<00:15:40.920> grafana<00:15:41.480> setup<00:15:41.920> where<00:15:42.560> um<00:15:42.680> I'll<00:15:42.839> have 00:15:42.990 --> 00:15:43.000 align:start position:0% like my grafana setup where um I'll have 00:15:43.000 --> 00:15:44.949 align:start position:0% like my grafana setup where um I'll have like<00:15:43.120> an<00:15:43.279> in<00:15:43.800> just<00:15:43.920> a<00:15:44.079> basic<00:15:44.440> invariant 00:15:44.949 --> 00:15:44.959 align:start position:0% like an in just a basic invariant 00:15:44.959 --> 00:15:47.069 align:start position:0% like an in just a basic invariant monitoring<00:15:45.480> thing<00:15:45.800> where<00:15:46.440> um<00:15:46.560> we're<00:15:46.759> checking 00:15:47.069 --> 00:15:47.079 align:start position:0% monitoring thing where um we're checking 00:15:47.079 --> 00:15:48.870 align:start position:0% monitoring thing where um we're checking for<00:15:47.319> certain<00:15:47.839> conditions<00:15:48.319> like<00:15:48.639> you<00:15:48.720> know 00:15:48.870 --> 00:15:48.880 align:start position:0% for certain conditions like you know 00:15:48.880 --> 00:15:50.790 align:start position:0% for certain conditions like you know more<00:15:49.120> tokens<00:15:49.480> were<00:15:49.680> withdrawn<00:15:50.120> from<00:15:50.240> an<00:15:50.399> escro 00:15:50.790 --> 00:15:50.800 align:start position:0% more tokens were withdrawn from an escro 00:15:50.800 --> 00:15:52.470 align:start position:0% more tokens were withdrawn from an escro contract<00:15:51.160> than<00:15:51.279> we're<00:15:51.519> actually<00:15:52.040> locked<00:15:52.360> up 00:15:52.470 --> 00:15:52.480 align:start position:0% contract than we're actually locked up 00:15:52.480 --> 00:15:54.509 align:start position:0% contract than we're actually locked up for<00:15:52.600> a<00:15:52.720> user<00:15:53.279> and<00:15:53.440> why<00:15:53.600> would<00:15:53.759> that<00:15:53.959> happen<00:15:54.279> and 00:15:54.509 --> 00:15:54.519 align:start position:0% for a user and why would that happen and 00:15:54.519 --> 00:15:55.910 align:start position:0% for a user and why would that happen and and<00:15:54.639> how<00:15:54.759> would<00:15:54.920> we<00:15:55.040> fix 00:15:55.910 --> 00:15:55.920 align:start position:0% and how would we fix 00:15:55.920 --> 00:15:59.150 align:start position:0% and how would we fix it<00:15:56.920> uh<00:15:57.040> and<00:15:57.199> then<00:15:57.440> the<00:15:57.839> uh<00:15:58.000> we<00:15:58.360> the<00:15:58.600> team 00:15:59.150 --> 00:15:59.160 align:start position:0% it uh and then the uh we the team 00:15:59.160 --> 00:16:00.790 align:start position:0% it uh and then the uh we the team actually<00:15:59.440> has<00:15:59.560> to<00:15:59.800> submit<00:16:00.120> the<00:16:00.279> transactions 00:16:00.790 --> 00:16:00.800 align:start position:0% actually has to submit the transactions 00:16:00.800 --> 00:16:03.309 align:start position:0% actually has to submit the transactions on<00:16:00.920> the<00:16:01.040> test<00:16:01.319> net<00:16:01.800> um<00:16:01.959> we<00:16:02.160> try<00:16:02.519> not<00:16:02.720> to<00:16:03.040> we<00:16:03.160> try 00:16:03.309 --> 00:16:03.319 align:start position:0% on the test net um we try not to we try 00:16:03.319 --> 00:16:05.110 align:start position:0% on the test net um we try not to we try to<00:16:03.720> uh<00:16:03.800> do<00:16:03.959> a<00:16:04.040> couple<00:16:04.279> things<00:16:04.399> to<00:16:04.560> keep<00:16:04.839> safe 00:16:05.110 --> 00:16:05.120 align:start position:0% to uh do a couple things to keep safe 00:16:05.120 --> 00:16:07.269 align:start position:0% to uh do a couple things to keep safe like<00:16:05.279> change<00:16:05.600> the<00:16:05.720> chain<00:16:06.000> ID<00:16:06.319> of<00:16:06.519> the<00:16:06.720> test<00:16:07.079> net 00:16:07.269 --> 00:16:07.279 align:start position:0% like change the chain ID of the test net 00:16:07.279 --> 00:16:09.350 align:start position:0% like change the chain ID of the test net so<00:16:07.440> that<00:16:07.680> the<00:16:08.199> um<00:16:08.319> so<00:16:08.440> that<00:16:08.600> the<00:16:08.720> actual<00:16:09.040> like 00:16:09.350 --> 00:16:09.360 align:start position:0% so that the um so that the actual like 00:16:09.360 --> 00:16:11.030 align:start position:0% so that the um so that the actual like response<00:16:09.839> transactions<00:16:10.440> couldn't<00:16:10.800> actually 00:16:11.030 --> 00:16:11.040 align:start position:0% response transactions couldn't actually 00:16:11.040 --> 00:16:12.590 align:start position:0% response transactions couldn't actually be<00:16:11.199> replayed<00:16:11.639> on<00:16:11.720> Main<00:16:11.959> net<00:16:12.360> because<00:16:12.480> we 00:16:12.590 --> 00:16:12.600 align:start position:0% be replayed on Main net because we 00:16:12.600 --> 00:16:13.910 align:start position:0% be replayed on Main net because we wouldn't<00:16:12.800> want<00:16:12.959> to<00:16:13.040> be<00:16:13.160> able<00:16:13.279> to<00:16:13.399> like<00:16:13.560> take<00:16:13.720> a 00:16:13.910 --> 00:16:13.920 align:start position:0% wouldn't want to be able to like take a 00:16:13.920 --> 00:16:15.829 align:start position:0% wouldn't want to be able to like take a pause<00:16:14.279> transaction<00:16:14.720> from<00:16:14.959> our<00:16:15.079> test<00:16:15.319> net<00:16:15.720> and 00:16:15.829 --> 00:16:15.839 align:start position:0% pause transaction from our test net and 00:16:15.839 --> 00:16:17.470 align:start position:0% pause transaction from our test net and then<00:16:16.040> actually<00:16:16.360> pause<00:16:16.639> a<00:16:16.720> major<00:16:17.000> protocol<00:16:17.360> on 00:16:17.470 --> 00:16:17.480 align:start position:0% then actually pause a major protocol on 00:16:17.480 --> 00:16:20.189 align:start position:0% then actually pause a major protocol on Main<00:16:17.759> net<00:16:18.199> and<00:16:18.319> so<00:16:18.440> we<00:16:18.560> change<00:16:18.839> the<00:16:18.959> chain<00:16:19.240> ID 00:16:20.189 --> 00:16:20.199 align:start position:0% Main net and so we change the chain ID 00:16:20.199 --> 00:16:22.590 align:start position:0% Main net and so we change the chain ID um<00:16:20.399> and<00:16:20.519> then<00:16:20.680> we<00:16:20.839> also<00:16:21.079> try<00:16:21.360> not<00:16:21.519> to<00:16:22.279> uh<00:16:22.399> make 00:16:22.590 --> 00:16:22.600 align:start position:0% um and then we also try not to uh make 00:16:22.600 --> 00:16:25.189 align:start position:0% um and then we also try not to uh make them<00:16:23.000> access<00:16:23.519> like<00:16:23.800> keys<00:16:24.160> for<00:16:24.560> safes<00:16:25.000> and 00:16:25.189 --> 00:16:25.199 align:start position:0% them access like keys for safes and 00:16:25.199 --> 00:16:26.910 align:start position:0% them access like keys for safes and stuff<00:16:25.399> if<00:16:25.519> they<00:16:25.759> really<00:16:25.920> don't<00:16:26.079> need<00:16:26.319> to<00:16:26.800> and 00:16:26.910 --> 00:16:26.920 align:start position:0% stuff if they really don't need to and 00:16:26.920 --> 00:16:29.509 align:start position:0% stuff if they really don't need to and so<00:16:27.040> we'll<00:16:27.279> kind<00:16:27.399> of<00:16:27.600> spoof<00:16:28.079> the<00:16:28.360> process<00:16:28.680> of 00:16:29.509 --> 00:16:29.519 align:start position:0% so we'll kind of spoof the process of 00:16:29.519 --> 00:16:31.949 align:start position:0% so we'll kind of spoof the process of uh<00:16:29.680> of<00:16:29.839> doing<00:16:30.160> like<00:16:30.480> a<00:16:30.560> multi<00:16:31.120> transaction 00:16:31.949 --> 00:16:31.959 align:start position:0% uh of doing like a multi transaction 00:16:31.959 --> 00:16:33.710 align:start position:0% uh of doing like a multi transaction just<00:16:32.120> in<00:16:32.319> case<00:16:32.680> like<00:16:32.920> there's<00:16:33.199> all<00:16:33.319> sorts<00:16:33.519> of 00:16:33.710 --> 00:16:33.720 align:start position:0% just in case like there's all sorts of 00:16:33.720 --> 00:16:35.230 align:start position:0% just in case like there's all sorts of security<00:16:34.120> procedures<00:16:34.560> around<00:16:34.839> accessing 00:16:35.230 --> 00:16:35.240 align:start position:0% security procedures around accessing 00:16:35.240 --> 00:16:37.670 align:start position:0% security procedures around accessing these<00:16:35.440> Keys<00:16:36.360> um<00:16:36.639> yeah<00:16:36.880> so<00:16:36.959> we<00:16:37.079> try<00:16:37.199> to<00:16:37.440> try<00:16:37.600> to 00:16:37.670 --> 00:16:37.680 align:start position:0% these Keys um yeah so we try to try to 00:16:37.680 --> 00:16:39.870 align:start position:0% these Keys um yeah so we try to try to keep<00:16:37.839> team<00:16:38.160> safe<00:16:38.560> doing<00:16:38.880> that<00:16:39.560> uh<00:16:39.680> here's<00:16:39.800> a 00:16:39.870 --> 00:16:39.880 align:start position:0% keep team safe doing that uh here's a 00:16:39.880 --> 00:16:42.030 align:start position:0% keep team safe doing that uh here's a link<00:16:40.079> to<00:16:40.160> a<00:16:40.240> few<00:16:40.399> resources<00:16:40.959> the<00:16:41.120> first<00:16:41.319> one<00:16:41.600> is 00:16:42.030 --> 00:16:42.040 align:start position:0% link to a few resources the first one is 00:16:42.040 --> 00:16:43.829 align:start position:0% link to a few resources the first one is uh<00:16:42.480> actually<00:16:42.680> related<00:16:43.040> to<00:16:43.199> an<00:16:43.319> event<00:16:43.600> that<00:16:43.720> was 00:16:43.829 --> 00:16:43.839 align:start position:0% uh actually related to an event that was 00:16:43.839 --> 00:16:46.189 align:start position:0% uh actually related to an event that was two<00:16:44.079> days<00:16:44.279> ago<00:16:44.560> that<00:16:44.680> we<00:16:44.880> hosted<00:16:45.680> uh<00:16:45.800> here<00:16:46.000> in 00:16:46.189 --> 00:16:46.199 align:start position:0% two days ago that we hosted uh here in 00:16:46.199 --> 00:16:48.269 align:start position:0% two days ago that we hosted uh here in in<00:16:46.319> Bangkok<00:16:46.839> but<00:16:46.959> I<00:16:47.079> left<00:16:47.240> it<00:16:47.440> there<00:16:47.680> because 00:16:48.269 --> 00:16:48.279 align:start position:0% in Bangkok but I left it there because 00:16:48.279 --> 00:16:49.590 align:start position:0% in Bangkok but I left it there because we<00:16:48.440> I<00:16:48.480> think<00:16:48.600> we'll<00:16:48.759> be<00:16:48.880> doing<00:16:49.120> more<00:16:49.279> of<00:16:49.440> these 00:16:49.590 --> 00:16:49.600 align:start position:0% we I think we'll be doing more of these 00:16:49.600 --> 00:16:51.629 align:start position:0% we I think we'll be doing more of these like<00:16:49.839> Live<00:16:50.399> Events<00:16:50.839> where<00:16:50.959> you<00:16:51.040> can<00:16:51.279> compete 00:16:51.629 --> 00:16:51.639 align:start position:0% like Live Events where you can compete 00:16:51.639 --> 00:16:53.550 align:start position:0% like Live Events where you can compete with<00:16:51.800> each<00:16:51.920> other<00:16:52.600> uh<00:16:52.720> to<00:16:52.880> try<00:16:53.040> to<00:16:53.199> white<00:16:53.440> hat 00:16:53.550 --> 00:16:53.560 align:start position:0% with each other uh to try to white hat 00:16:53.560 --> 00:16:56.030 align:start position:0% with each other uh to try to white hat rescue<00:16:53.839> funds<00:16:54.079> from<00:16:54.399> protocols<00:16:55.399> uh<00:16:55.639> the 00:16:56.030 --> 00:16:56.040 align:start position:0% rescue funds from protocols uh the 00:16:56.040 --> 00:16:58.350 align:start position:0% rescue funds from protocols uh the second<00:16:56.360> is<00:16:56.519> the<00:16:56.680> GitHub<00:16:57.160> repository<00:16:58.160> uh<00:16:58.240> we 00:16:58.350 --> 00:16:58.360 align:start position:0% second is the GitHub repository uh we 00:16:58.360 --> 00:16:59.949 align:start position:0% second is the GitHub repository uh we have<00:16:58.440> the<00:16:58.519> security<00:16:59.079> Alliance<00:16:59.440> website<00:16:59.839> where 00:16:59.949 --> 00:16:59.959 align:start position:0% have the security Alliance website where 00:16:59.959 --> 00:17:02.470 align:start position:0% have the security Alliance website where you<00:17:00.079> can<00:17:00.639> uh<00:17:00.800> sign<00:17:01.000> up<00:17:01.160> for<00:17:01.480> a<00:17:01.600> drill<00:17:02.000> sponsored 00:17:02.470 --> 00:17:02.480 align:start position:0% you can uh sign up for a drill sponsored 00:17:02.480 --> 00:17:04.390 align:start position:0% you can uh sign up for a drill sponsored by<00:17:02.600> the<00:17:02.759> security<00:17:03.120> Alliance<00:17:03.920> um<00:17:04.039> and<00:17:04.160> you<00:17:04.240> can 00:17:04.390 --> 00:17:04.400 align:start position:0% by the security Alliance um and you can 00:17:04.400 --> 00:17:06.429 align:start position:0% by the security Alliance um and you can also<00:17:04.640> sign<00:17:04.839> up<00:17:05.000> for<00:17:05.160> drills<00:17:06.000> um<00:17:06.120> on<00:17:06.280> my 00:17:06.429 --> 00:17:06.439 align:start position:0% also sign up for drills um on my 00:17:06.439 --> 00:17:08.470 align:start position:0% also sign up for drills um on my company's<00:17:06.880> website<00:17:07.160> Shield<00:17:07.480> 3<00:17:08.120> uh<00:17:08.240> if<00:17:08.319> you're 00:17:08.470 --> 00:17:08.480 align:start position:0% company's website Shield 3 uh if you're 00:17:08.480 --> 00:17:11.150 align:start position:0% company's website Shield 3 uh if you're on<00:17:08.640> a<00:17:08.880> an<00:17:09.039> accelerated<00:17:09.679> timeline<00:17:10.679> uh<00:17:10.799> or<00:17:10.959> feel 00:17:11.150 --> 00:17:11.160 align:start position:0% on a an accelerated timeline uh or feel 00:17:11.160 --> 00:17:12.470 align:start position:0% on a an accelerated timeline uh or feel free<00:17:11.360> to<00:17:11.480> chat<00:17:11.679> with<00:17:11.799> me<00:17:11.919> if<00:17:12.000> you're<00:17:12.160> just<00:17:12.280> like 00:17:12.470 --> 00:17:12.480 align:start position:0% free to chat with me if you're just like 00:17:12.480 --> 00:17:14.350 align:start position:0% free to chat with me if you're just like hey<00:17:12.640> I<00:17:12.720> want<00:17:12.799> to<00:17:12.959> run<00:17:13.480> war<00:17:13.799> games<00:17:13.959> for 00:17:14.350 --> 00:17:14.360 align:start position:0% hey I want to run war games for 00:17:14.360 --> 00:17:17.069 align:start position:0% hey I want to run war games for protocols<00:17:15.360> uh<00:17:15.679> I'm<00:17:16.079> happy<00:17:16.280> to 00:17:17.069 --> 00:17:17.079 align:start position:0% protocols uh I'm happy to 00:17:17.079 --> 00:17:20.230 align:start position:0% protocols uh I'm happy to share<00:17:18.079> so<00:17:18.400> thank<00:17:18.559> you<00:17:19.559> all<00:17:19.760> right<00:17:20.000> thank<00:17:20.120> you 00:17:20.230 --> 00:17:20.240 align:start position:0% share so thank you all right thank you 00:17:20.240 --> 00:17:23.309 align:start position:0% share so thank you all right thank you very<00:17:20.439> much 00:17:23.309 --> 00:17:23.319 align:start position:0% 00:17:23.319 --> 00:17:25.350 align:start position:0% Isaac<00:17:24.319> appreciate<00:17:24.799> it<00:17:24.959> even<00:17:25.120> though<00:17:25.240> we 00:17:25.350 --> 00:17:25.360 align:start position:0% Isaac appreciate it even though we 00:17:25.360 --> 00:17:26.829 align:start position:0% Isaac appreciate it even though we started<00:17:25.640> late<00:17:25.799> you<00:17:25.919> finished<00:17:26.360> well<00:17:26.600> within 00:17:26.829 --> 00:17:26.839 align:start position:0% started late you finished well within 00:17:26.839 --> 00:17:28.549 align:start position:0% started late you finished well within your<00:17:27.039> time<00:17:27.280> I<00:17:27.400> really<00:17:27.640> appreciate<00:17:28.199> that<00:17:28.439> and 00:17:28.549 --> 00:17:28.559 align:start position:0% your time I really appreciate that and 00:17:28.559 --> 00:17:31.070 align:start position:0% your time I really appreciate that and I'm<00:17:28.919> happy<00:17:29.120> to<00:17:29.280> say<00:17:29.720> that<00:17:29.919> our<00:17:30.440> questions<00:17:30.880> are 00:17:31.070 --> 00:17:31.080 align:start position:0% I'm happy to say that our questions are 00:17:31.080 --> 00:17:33.190 align:start position:0% I'm happy to say that our questions are now<00:17:31.320> working<00:17:31.679> so<00:17:31.919> let's<00:17:32.120> turn<00:17:32.360> our<00:17:32.840> attention 00:17:33.190 --> 00:17:33.200 align:start position:0% now working so let's turn our attention 00:17:33.200 --> 00:17:34.510 align:start position:0% now working so let's turn our attention to<00:17:33.360> the<00:17:33.480> screen<00:17:33.799> I'm<00:17:33.880> going<00:17:33.960> to<00:17:34.080> read<00:17:34.240> out<00:17:34.400> the 00:17:34.510 --> 00:17:34.520 align:start position:0% to the screen I'm going to read out the 00:17:34.520 --> 00:17:36.870 align:start position:0% to the screen I'm going to read out the first<00:17:34.799> question<00:17:35.320> with<00:17:35.480> the<00:17:35.600> most<00:17:35.840> votes<00:17:36.440> is<00:17:36.520> it 00:17:36.870 --> 00:17:36.880 align:start position:0% first question with the most votes is it 00:17:36.880 --> 00:17:39.710 align:start position:0% first question with the most votes is it possible<00:17:37.360> to<00:17:37.559> have<00:17:37.799> a<00:17:38.000> Seal<00:17:38.480> Team<00:17:38.760> Member<00:17:39.440> be 00:17:39.710 --> 00:17:39.720 align:start position:0% possible to have a Seal Team Member be 00:17:39.720 --> 00:17:42.710 align:start position:0% possible to have a Seal Team Member be part<00:17:39.919> of<00:17:40.039> a<00:17:40.240> protocol<00:17:41.080> Guardians<00:17:42.080> multii 00:17:42.710 --> 00:17:42.720 align:start position:0% part of a protocol Guardians multii 00:17:42.720 --> 00:17:45.430 align:start position:0% part of a protocol Guardians multii somehow<00:17:43.400> y<00:17:43.799> yeah<00:17:44.080> um<00:17:44.240> a<00:17:44.360> lot<00:17:44.480> of<00:17:44.600> us<00:17:44.880> are<00:17:45.200> on 00:17:45.430 --> 00:17:45.440 align:start position:0% somehow y yeah um a lot of us are on 00:17:45.440 --> 00:17:47.549 align:start position:0% somehow y yeah um a lot of us are on some<00:17:45.600> of<00:17:45.840> these<00:17:46.240> uh<00:17:46.320> multisig<00:17:46.880> or<00:17:47.000> on<00:17:47.200> security 00:17:47.549 --> 00:17:47.559 align:start position:0% some of these uh multisig or on security 00:17:47.559 --> 00:17:49.230 align:start position:0% some of these uh multisig or on security councils<00:17:48.240> we<00:17:48.400> actually<00:17:48.640> talked<00:17:48.880> about<00:17:49.039> this 00:17:49.230 --> 00:17:49.240 align:start position:0% councils we actually talked about this 00:17:49.240 --> 00:17:51.430 align:start position:0% councils we actually talked about this recently<00:17:49.720> like<00:17:49.880> if<00:17:50.039> seal<00:17:50.679> itself<00:17:51.039> should<00:17:51.240> be 00:17:51.430 --> 00:17:51.440 align:start position:0% recently like if seal itself should be 00:17:51.440 --> 00:17:53.390 align:start position:0% recently like if seal itself should be like<00:17:51.640> members<00:17:52.000> of<00:17:52.200> security<00:17:52.559> councils<00:17:53.240> we 00:17:53.390 --> 00:17:53.400 align:start position:0% like members of security councils we 00:17:53.400 --> 00:17:55.590 align:start position:0% like members of security councils we came<00:17:53.559> to<00:17:53.720> the<00:17:54.039> conclusion<00:17:55.039> I<00:17:55.080> mean<00:17:55.320> this<00:17:55.440> might 00:17:55.590 --> 00:17:55.600 align:start position:0% came to the conclusion I mean this might 00:17:55.600 --> 00:17:57.830 align:start position:0% came to the conclusion I mean this might change<00:17:55.840> in<00:17:55.919> the<00:17:56.080> future<00:17:56.640> that<00:17:56.880> like<00:17:57.240> us 00:17:57.830 --> 00:17:57.840 align:start position:0% change in the future that like us 00:17:57.840 --> 00:18:00.270 align:start position:0% change in the future that like us individually<00:17:58.919> can<00:17:59.280> also<00:17:59.600> be<00:17:59.880> like<00:18:00.000> on 00:18:00.270 --> 00:18:00.280 align:start position:0% individually can also be like on 00:18:00.280 --> 00:18:02.470 align:start position:0% individually can also be like on security<00:18:00.640> councils<00:18:01.400> uh<00:18:01.520> but<00:18:01.640> seal<00:18:02.000> itself<00:18:02.320> is 00:18:02.470 --> 00:18:02.480 align:start position:0% security councils uh but seal itself is 00:18:02.480 --> 00:18:04.510 align:start position:0% security councils uh but seal itself is not<00:18:02.679> but<00:18:02.799> like<00:18:02.960> many<00:18:03.200> many<00:18:03.400> seal<00:18:03.760> members<00:18:04.240> are 00:18:04.510 --> 00:18:04.520 align:start position:0% not but like many many seal members are 00:18:04.520 --> 00:18:06.909 align:start position:0% not but like many many seal members are open<00:18:04.799> to<00:18:05.000> being<00:18:05.320> like<00:18:05.480> on<00:18:05.720> these<00:18:06.120> uh<00:18:06.600> uh<00:18:06.720> on 00:18:06.909 --> 00:18:06.919 align:start position:0% open to being like on these uh uh on 00:18:06.919 --> 00:18:08.789 align:start position:0% open to being like on these uh uh on guardian<00:18:07.240> multisig<00:18:07.880> and<00:18:08.159> uh<00:18:08.280> and<00:18:08.440> stuff<00:18:08.640> like 00:18:08.789 --> 00:18:08.799 align:start position:0% guardian multisig and uh and stuff like 00:18:08.799 --> 00:18:11.070 align:start position:0% guardian multisig and uh and stuff like that<00:18:09.039> so<00:18:09.240> feel<00:18:09.600> yeah<00:18:09.919> just<00:18:10.280> find<00:18:10.520> me<00:18:10.720> and<00:18:10.960> we 00:18:11.070 --> 00:18:11.080 align:start position:0% that so feel yeah just find me and we 00:18:11.080 --> 00:18:13.590 align:start position:0% that so feel yeah just find me and we can<00:18:11.360> we<00:18:11.440> can<00:18:11.799> help<00:18:12.799> all<00:18:12.919> right<00:18:13.120> thanks<00:18:13.320> for<00:18:13.440> the 00:18:13.590 --> 00:18:13.600 align:start position:0% can we can help all right thanks for the 00:18:13.600 --> 00:18:15.149 align:start position:0% can we can help all right thanks for the answer<00:18:13.919> thanks<00:18:14.120> for<00:18:14.240> the<00:18:14.400> question<00:18:14.880> next 00:18:15.149 --> 00:18:15.159 align:start position:0% answer thanks for the question next 00:18:15.159 --> 00:18:17.190 align:start position:0% answer thanks for the question next question<00:18:15.480> that<00:18:15.640> got<00:18:15.840> voted<00:18:16.200> to<00:18:16.360> the<00:18:16.559> top<00:18:17.000> do 00:18:17.190 --> 00:18:17.200 align:start position:0% question that got voted to the top do 00:18:17.200 --> 00:18:19.510 align:start position:0% question that got voted to the top do you<00:18:17.400> share<00:18:17.880> threat<00:18:18.360> intelligence<00:18:19.000> data<00:18:19.320> on 00:18:19.510 --> 00:18:19.520 align:start position:0% you share threat intelligence data on 00:18:19.520 --> 00:18:22.070 align:start position:0% you share threat intelligence data on chain<00:18:20.000> if<00:18:20.159> no<00:18:20.720> how<00:18:20.919> or<00:18:21.159> where<00:18:21.360> do<00:18:21.480> you<00:18:21.600> share 00:18:22.070 --> 00:18:22.080 align:start position:0% chain if no how or where do you share 00:18:22.080 --> 00:18:24.830 align:start position:0% chain if no how or where do you share threat<00:18:22.440> intelligence<00:18:23.280> data<00:18:23.919> yes<00:18:24.280> so<00:18:24.600> the 00:18:24.830 --> 00:18:24.840 align:start position:0% threat intelligence data yes so the 00:18:24.840 --> 00:18:26.310 align:start position:0% threat intelligence data yes so the security<00:18:25.240> Alliance<00:18:25.640> website<00:18:25.960> should<00:18:26.120> have<00:18:26.200> a 00:18:26.310 --> 00:18:26.320 align:start position:0% security Alliance website should have a 00:18:26.320 --> 00:18:29.430 align:start position:0% security Alliance website should have a link<00:18:26.520> to<00:18:26.679> the<00:18:26.799> cal-<00:18:27.640> ISAC<00:18:28.880> which<00:18:29.000> is<00:18:29.159> the 00:18:29.430 --> 00:18:29.440 align:start position:0% link to the cal- ISAC which is the 00:18:29.440 --> 00:18:31.830 align:start position:0% link to the cal- ISAC which is the information<00:18:29.919> sharing<00:18:30.360> tool<00:18:31.200> um<00:18:31.360> there's<00:18:31.559> a 00:18:31.830 --> 00:18:31.840 align:start position:0% information sharing tool um there's a 00:18:31.840 --> 00:18:33.430 align:start position:0% information sharing tool um there's a there's<00:18:32.000> a<00:18:32.320> a<00:18:32.440> large<00:18:32.679> amount<00:18:32.880> of<00:18:33.039> data<00:18:33.280> that 00:18:33.430 --> 00:18:33.440 align:start position:0% there's a a large amount of data that 00:18:33.440 --> 00:18:35.549 align:start position:0% there's a a large amount of data that actually<00:18:33.720> is<00:18:33.919> available<00:18:34.520> publicly<00:18:35.240> but<00:18:35.360> then 00:18:35.549 --> 00:18:35.559 align:start position:0% actually is available publicly but then 00:18:35.559 --> 00:18:37.070 align:start position:0% actually is available publicly but then also<00:18:35.799> if<00:18:35.880> you're<00:18:36.039> like<00:18:36.200> a<00:18:36.320> wallet<00:18:36.640> company<00:18:36.960> or 00:18:37.070 --> 00:18:37.080 align:start position:0% also if you're like a wallet company or 00:18:37.080 --> 00:18:39.029 align:start position:0% also if you're like a wallet company or an<00:18:37.280> exchange<00:18:37.720> where<00:18:37.919> also<00:18:38.559> um<00:18:38.679> there's<00:18:38.880> like 00:18:39.029 --> 00:18:39.039 align:start position:0% an exchange where also um there's like 00:18:39.039 --> 00:18:40.549 align:start position:0% an exchange where also um there's like even<00:18:39.280> more<00:18:39.520> sensitive<00:18:40.000> data<00:18:40.240> that<00:18:40.360> can<00:18:40.440> be 00:18:40.549 --> 00:18:40.559 align:start position:0% even more sensitive data that can be 00:18:40.559 --> 00:18:42.630 align:start position:0% even more sensitive data that can be shared<00:18:40.840> in<00:18:40.960> a<00:18:41.080> more<00:18:41.280> private<00:18:41.640> way<00:18:42.159> um<00:18:42.320> so 00:18:42.630 --> 00:18:42.640 align:start position:0% shared in a more private way um so 00:18:42.640 --> 00:18:44.430 align:start position:0% shared in a more private way um so that's<00:18:42.799> the<00:18:42.960> best<00:18:43.159> place<00:18:43.320> to<00:18:43.520> look<00:18:43.679> for<00:18:44.080> like 00:18:44.430 --> 00:18:44.440 align:start position:0% that's the best place to look for like 00:18:44.440 --> 00:18:46.750 align:start position:0% that's the best place to look for like uh<00:18:44.799> for<00:18:45.159> just<00:18:45.480> data<00:18:45.799> being<00:18:46.000> shared<00:18:46.440> across 00:18:46.750 --> 00:18:46.760 align:start position:0% uh for just data being shared across 00:18:46.760 --> 00:18:48.830 align:start position:0% uh for just data being shared across teams<00:18:47.320> it<00:18:47.400> can<00:18:47.559> be<00:18:47.960> it<00:18:48.200> there's<00:18:48.480> they're<00:18:48.640> even 00:18:48.830 --> 00:18:48.840 align:start position:0% teams it can be it there's they're even 00:18:48.840 --> 00:18:50.510 align:start position:0% teams it can be it there's they're even starting<00:18:49.120> to<00:18:49.360> gather<00:18:49.640> a<00:18:49.720> lot<00:18:49.880> of<00:18:50.039> information 00:18:50.510 --> 00:18:50.520 align:start position:0% starting to gather a lot of information 00:18:50.520 --> 00:18:52.909 align:start position:0% starting to gather a lot of information just<00:18:50.720> about<00:18:51.280> every<00:18:51.559> time<00:18:51.880> like<00:18:52.120> a<00:18:52.559> a<00:18:52.679> North 00:18:52.909 --> 00:18:52.919 align:start position:0% just about every time like a a North 00:18:52.919 --> 00:18:54.870 align:start position:0% just about every time like a a North Korean<00:18:53.200> developer<00:18:53.600> applies<00:18:53.919> to<00:18:54.039> a<00:18:54.240> protocol 00:18:54.870 --> 00:18:54.880 align:start position:0% Korean developer applies to a protocol 00:18:54.880 --> 00:18:56.430 align:start position:0% Korean developer applies to a protocol they<00:18:54.960> try<00:18:55.120> to<00:18:55.240> just<00:18:55.360> like<00:18:55.559> profile<00:18:55.919> it<00:18:56.039> and 00:18:56.430 --> 00:18:56.440 align:start position:0% they try to just like profile it and 00:18:56.440 --> 00:18:57.630 align:start position:0% they try to just like profile it and understand<00:18:56.640> like<00:18:56.799> how<00:18:57.000> they're<00:18:57.159> doing<00:18:57.440> it 00:18:57.630 --> 00:18:57.640 align:start position:0% understand like how they're doing it 00:18:57.640 --> 00:18:59.190 align:start position:0% understand like how they're doing it who's<00:18:57.960> getting<00:18:58.200> in<00:18:58.480> just<00:18:58.799> so<00:18:58.880> that<00:18:59.000> we<00:18:59.080> can 00:18:59.190 --> 00:18:59.200 align:start position:0% who's getting in just so that we can 00:18:59.200 --> 00:19:01.630 align:start position:0% who's getting in just so that we can like<00:18:59.320> share<00:18:59.640> data<00:18:59.960> on<00:19:00.200> like<00:19:00.320> how<00:19:00.559> teams<00:19:00.880> are<00:19:01.520> uh 00:19:01.630 --> 00:19:01.640 align:start position:0% like share data on like how teams are uh 00:19:01.640 --> 00:19:03.390 align:start position:0% like share data on like how teams are uh how<00:19:01.760> teams<00:19:02.000> are<00:19:02.200> being<00:19:02.440> like<00:19:02.559> trying<00:19:02.760> to<00:19:02.880> be 00:19:03.390 --> 00:19:03.400 align:start position:0% how teams are being like trying to be 00:19:03.400 --> 00:19:07.110 align:start position:0% how teams are being like trying to be infiltrated<00:19:04.400> thanks<00:19:05.159> seal<00:19:05.480> ISAC<00:19:06.480> yeah<00:19:06.880> thanks 00:19:07.110 --> 00:19:07.120 align:start position:0% infiltrated thanks seal ISAC yeah thanks 00:19:07.120 --> 00:19:09.350 align:start position:0% infiltrated thanks seal ISAC yeah thanks for<00:19:07.280> the<00:19:07.440> answer<00:19:08.080> great<00:19:08.600> all<00:19:08.799> right<00:19:09.000> let's<00:19:09.240> go 00:19:09.350 --> 00:19:09.360 align:start position:0% for the answer great all right let's go 00:19:09.360 --> 00:19:11.350 align:start position:0% for the answer great all right let's go on<00:19:09.600> we've<00:19:09.760> got<00:19:09.960> time<00:19:10.120> for<00:19:10.320> more<00:19:10.559> questions 00:19:11.350 --> 00:19:11.360 align:start position:0% on we've got time for more questions 00:19:11.360 --> 00:19:14.270 align:start position:0% on we've got time for more questions does<00:19:11.640> the<00:19:11.799> drill<00:19:12.240> occur<00:19:12.679> unexpectedly<00:19:13.679> I.E 00:19:14.270 --> 00:19:14.280 align:start position:0% does the drill occur unexpectedly I.E 00:19:14.280 --> 00:19:16.390 align:start position:0% does the drill occur unexpectedly I.E the<00:19:14.440> team<00:19:14.799> knows<00:19:15.080> it'll<00:19:15.280> be<00:19:15.440> happening<00:19:16.080> or<00:19:16.240> but 00:19:16.390 --> 00:19:16.400 align:start position:0% the team knows it'll be happening or but 00:19:16.400 --> 00:19:18.310 align:start position:0% the team knows it'll be happening or but doesn't<00:19:16.600> know<00:19:16.840> when<00:19:17.640> uh<00:19:17.720> I've<00:19:17.840> gone<00:19:18.080> back<00:19:18.200> and 00:19:18.310 --> 00:19:18.320 align:start position:0% doesn't know when uh I've gone back and 00:19:18.320 --> 00:19:20.310 align:start position:0% doesn't know when uh I've gone back and forth<00:19:18.520> on<00:19:18.679> this<00:19:18.840> a<00:19:18.919> few<00:19:19.120> times<00:19:19.440> initially<00:19:20.200> it 00:19:20.310 --> 00:19:20.320 align:start position:0% forth on this a few times initially it 00:19:20.320 --> 00:19:21.750 align:start position:0% forth on this a few times initially it was<00:19:20.480> like<00:19:20.600> we<00:19:20.679> would<00:19:20.880> give<00:19:21.000> them<00:19:21.120> an<00:19:21.240> 8<00:19:21.520> Hour 00:19:21.750 --> 00:19:21.760 align:start position:0% was like we would give them an 8 Hour 00:19:21.760 --> 00:19:23.149 align:start position:0% was like we would give them an 8 Hour window<00:19:22.159> and<00:19:22.280> then<00:19:22.400> say<00:19:22.640> like<00:19:22.840> okay<00:19:22.960> it's<00:19:23.080> going 00:19:23.149 --> 00:19:23.159 align:start position:0% window and then say like okay it's going 00:19:23.159 --> 00:19:24.669 align:start position:0% window and then say like okay it's going to<00:19:23.320> happen<00:19:23.559> at<00:19:23.679> some<00:19:23.799> point<00:19:24.000> in<00:19:24.080> this<00:19:24.159> 8<00:19:24.440> Hour 00:19:24.669 --> 00:19:24.679 align:start position:0% to happen at some point in this 8 Hour 00:19:24.679 --> 00:19:26.630 align:start position:0% to happen at some point in this 8 Hour window<00:19:25.440> um<00:19:25.559> but<00:19:25.679> then<00:19:25.840> I<00:19:25.960> was<00:19:26.159> just<00:19:26.320> sitting 00:19:26.630 --> 00:19:26.640 align:start position:0% window um but then I was just sitting 00:19:26.640 --> 00:19:27.950 align:start position:0% window um but then I was just sitting there<00:19:26.880> like<00:19:27.000> stressed<00:19:27.400> waiting<00:19:27.640> for<00:19:27.760> it<00:19:27.840> to 00:19:27.950 --> 00:19:27.960 align:start position:0% there like stressed waiting for it to 00:19:27.960 --> 00:19:29.549 align:start position:0% there like stressed waiting for it to start<00:19:28.200> so<00:19:28.360> I<00:19:28.480> always<00:19:28.799> just<00:19:28.919> started<00:19:29.200> it<00:19:29.400> right 00:19:29.549 --> 00:19:29.559 align:start position:0% start so I always just started it right 00:19:29.559 --> 00:19:31.390 align:start position:0% start so I always just started it right at<00:19:29.640> the<00:19:29.760> beginning<00:19:30.039> of<00:19:30.159> the<00:19:30.280> window<00:19:31.039> um<00:19:31.159> so<00:19:31.320> I 00:19:31.390 --> 00:19:31.400 align:start position:0% at the beginning of the window um so I 00:19:31.400 --> 00:19:33.990 align:start position:0% at the beginning of the window um so I don't<00:19:31.600> know<00:19:31.799> if<00:19:32.039> like<00:19:32.720> uh<00:19:33.159> it<00:19:33.280> might<00:19:33.480> be<00:19:33.640> fun<00:19:33.840> to 00:19:33.990 --> 00:19:34.000 align:start position:0% don't know if like uh it might be fun to 00:19:34.000 --> 00:19:35.830 align:start position:0% don't know if like uh it might be fun to do<00:19:34.159> that<00:19:34.320> I<00:19:34.400> think<00:19:34.600> at<00:19:34.760> at<00:19:34.880> some<00:19:35.080> point<00:19:35.640> we're 00:19:35.830 --> 00:19:35.840 align:start position:0% do that I think at at some point we're 00:19:35.840 --> 00:19:37.390 align:start position:0% do that I think at at some point we're talking<00:19:36.159> we're<00:19:36.320> thinking<00:19:36.600> about<00:19:36.880> like<00:19:37.080> can<00:19:37.240> we 00:19:37.390 --> 00:19:37.400 align:start position:0% talking we're thinking about like can we 00:19:37.400 --> 00:19:40.310 align:start position:0% talking we're thinking about like can we do<00:19:37.720> like<00:19:38.080> more<00:19:38.400> surprise<00:19:38.960> drills<00:19:39.919> um<00:19:40.039> on<00:19:40.200> these 00:19:40.310 --> 00:19:40.320 align:start position:0% do like more surprise drills um on these 00:19:40.320 --> 00:19:41.830 align:start position:0% do like more surprise drills um on these longer<00:19:40.600> running<00:19:40.919> test<00:19:41.159> Nets<00:19:41.440> where<00:19:41.559> we<00:19:41.679> like 00:19:41.830 --> 00:19:41.840 align:start position:0% longer running test Nets where we like 00:19:41.840 --> 00:19:44.190 align:start position:0% longer running test Nets where we like submit<00:19:42.120> a<00:19:42.240> faulty<00:19:42.840> or<00:19:43.120> like<00:19:43.240> we<00:19:43.440> submit<00:19:43.840> like<00:19:44.000> a 00:19:44.190 --> 00:19:44.200 align:start position:0% submit a faulty or like we submit like a 00:19:44.200 --> 00:19:46.270 align:start position:0% submit a faulty or like we submit like a a<00:19:44.320> faulty<00:19:44.760> proof<00:19:45.000> to<00:19:45.159> like<00:19:45.280> an<00:19:45.400> L2<00:19:45.760> rollup<00:19:46.120> or 00:19:46.270 --> 00:19:46.280 align:start position:0% a faulty proof to like an L2 rollup or 00:19:46.280 --> 00:19:48.470 align:start position:0% a faulty proof to like an L2 rollup or something<00:19:46.559> like<00:19:46.720> that<00:19:47.080> just<00:19:47.240> out<00:19:47.360> of<00:19:47.520> nowhere 00:19:48.470 --> 00:19:48.480 align:start position:0% something like that just out of nowhere 00:19:48.480 --> 00:19:50.549 align:start position:0% something like that just out of nowhere um<00:19:48.640> just<00:19:48.760> to<00:19:48.919> surprise<00:19:49.280> a<00:19:49.440> team<00:19:50.120> um<00:19:50.240> but<00:19:50.400> yeah 00:19:50.549 --> 00:19:50.559 align:start position:0% um just to surprise a team um but yeah 00:19:50.559 --> 00:19:52.110 align:start position:0% um just to surprise a team um but yeah typically<00:19:51.000> they<00:19:51.120> know<00:19:51.360> that<00:19:51.480> it's<00:19:51.679> going<00:19:51.880> to 00:19:52.110 --> 00:19:52.120 align:start position:0% typically they know that it's going to 00:19:52.120 --> 00:19:54.590 align:start position:0% typically they know that it's going to happen<00:19:52.440> on<00:19:52.679> a<00:19:52.840> certain<00:19:53.240> date<00:19:53.880> um<00:19:54.039> but<00:19:54.200> it<00:19:54.360> I<00:19:54.480> it 00:19:54.590 --> 00:19:54.600 align:start position:0% happen on a certain date um but it I it 00:19:54.600 --> 00:19:56.230 align:start position:0% happen on a certain date um but it I it still<00:19:54.840> maintains<00:19:55.240> a<00:19:55.400> pretty<00:19:55.600> good<00:19:55.799> amount<00:19:56.039> of 00:19:56.230 --> 00:19:56.240 align:start position:0% still maintains a pretty good amount of 00:19:56.240 --> 00:19:58.230 align:start position:0% still maintains a pretty good amount of realism<00:19:57.240> right<00:19:57.480> thank<00:19:57.600> you<00:19:57.760> very<00:19:57.919> much 00:19:58.230 --> 00:19:58.240 align:start position:0% realism right thank you very much 00:19:58.240 --> 00:20:00.830 align:start position:0% realism right thank you very much surprise<00:19:58.960> you've<00:19:59.120> been<00:19:59.280> compromised<00:20:00.159> anyway 00:20:00.830 --> 00:20:00.840 align:start position:0% surprise you've been compromised anyway 00:20:00.840 --> 00:20:02.430 align:start position:0% surprise you've been compromised anyway uh<00:20:01.120> let's<00:20:01.320> move<00:20:01.480> on<00:20:01.600> to<00:20:01.720> the<00:20:01.840> next<00:20:02.080> question<00:20:02.360> I 00:20:02.430 --> 00:20:02.440 align:start position:0% uh let's move on to the next question I 00:20:02.440 --> 00:20:04.149 align:start position:0% uh let's move on to the next question I think<00:20:02.600> this<00:20:02.679> is<00:20:02.799> an<00:20:02.960> important<00:20:03.400> question<00:20:03.960> it's 00:20:04.149 --> 00:20:04.159 align:start position:0% think this is an important question it's 00:20:04.159 --> 00:20:06.070 align:start position:0% think this is an important question it's got<00:20:04.320> quite<00:20:04.480> a<00:20:04.559> few<00:20:04.720> votes<00:20:05.039> as<00:20:05.159> well<00:20:05.640> what's<00:20:05.919> the 00:20:06.070 --> 00:20:06.080 align:start position:0% got quite a few votes as well what's the 00:20:06.080 --> 00:20:09.070 align:start position:0% got quite a few votes as well what's the most<00:20:06.360> common<00:20:06.840> way<00:20:07.280> teams<00:20:07.880> fall<00:20:08.240> over<00:20:08.880> I<00:20:08.960> think 00:20:09.070 --> 00:20:09.080 align:start position:0% most common way teams fall over I think 00:20:09.080 --> 00:20:10.870 align:start position:0% most common way teams fall over I think one<00:20:09.200> of<00:20:09.320> the<00:20:09.440> most<00:20:09.640> common<00:20:09.919> things<00:20:10.159> is<00:20:10.440> like 00:20:10.870 --> 00:20:10.880 align:start position:0% one of the most common things is like 00:20:10.880 --> 00:20:13.149 align:start position:0% one of the most common things is like having<00:20:11.120> your<00:20:11.400> internal<00:20:11.840> tooling<00:20:12.400> just<00:20:12.559> not<00:20:12.840> be 00:20:13.149 --> 00:20:13.159 align:start position:0% having your internal tooling just not be 00:20:13.159 --> 00:20:15.990 align:start position:0% having your internal tooling just not be up<00:20:13.360> toate<00:20:14.080> um<00:20:14.200> so<00:20:14.600> it's<00:20:14.840> very<00:20:15.200> like<00:20:15.480> maybe<00:20:15.840> like 00:20:15.990 --> 00:20:16.000 align:start position:0% up toate um so it's very like maybe like 00:20:16.000 --> 00:20:18.270 align:start position:0% up toate um so it's very like maybe like one<00:20:16.240> developer<00:20:16.720> got<00:20:16.880> on<00:20:17.039> a<00:20:17.320> was<00:20:17.520> very<00:20:17.760> inspired 00:20:18.270 --> 00:20:18.280 align:start position:0% one developer got on a was very inspired 00:20:18.280 --> 00:20:19.990 align:start position:0% one developer got on a was very inspired a<00:20:18.400> year<00:20:18.559> ago<00:20:18.799> to<00:20:18.960> make<00:20:19.200> all<00:20:19.480> of<00:20:19.640> like<00:20:19.799> these 00:20:19.990 --> 00:20:20.000 align:start position:0% a year ago to make all of like these 00:20:20.000 --> 00:20:21.909 align:start position:0% a year ago to make all of like these really<00:20:20.280> great<00:20:20.720> internal<00:20:21.200> tools<00:20:21.600> but<00:20:21.760> then 00:20:21.909 --> 00:20:21.919 align:start position:0% really great internal tools but then 00:20:21.919 --> 00:20:23.590 align:start position:0% really great internal tools but then like<00:20:22.080> the<00:20:22.200> protocols<00:20:22.760> changed<00:20:23.120> a<00:20:23.200> bit<00:20:23.400> over 00:20:23.590 --> 00:20:23.600 align:start position:0% like the protocols changed a bit over 00:20:23.600 --> 00:20:24.990 align:start position:0% like the protocols changed a bit over the<00:20:23.760> last<00:20:23.960> year<00:20:24.120> and<00:20:24.240> the<00:20:24.360> internal<00:20:24.679> tools 00:20:24.990 --> 00:20:25.000 align:start position:0% the last year and the internal tools 00:20:25.000 --> 00:20:27.230 align:start position:0% the last year and the internal tools don't<00:20:25.200> work<00:20:25.480> so<00:20:25.919> I<00:20:26.000> think<00:20:26.159> like<00:20:26.360> maintaining 00:20:27.230 --> 00:20:27.240 align:start position:0% don't work so I think like maintaining 00:20:27.240 --> 00:20:28.870 align:start position:0% don't work so I think like maintaining the<00:20:27.400> internal<00:20:27.840> tooling<00:20:28.240> that<00:20:28.320> you<00:20:28.440> need<00:20:28.679> need 00:20:28.870 --> 00:20:28.880 align:start position:0% the internal tooling that you need need 00:20:28.880 --> 00:20:31.230 align:start position:0% the internal tooling that you need need for<00:20:29.080> these<00:20:29.240> scenarios<00:20:29.919> is<00:20:30.159> is<00:20:30.360> very<00:20:30.600> important 00:20:31.230 --> 00:20:31.240 align:start position:0% for these scenarios is is very important 00:20:31.240 --> 00:20:33.149 align:start position:0% for these scenarios is is very important and<00:20:31.440> dedicating<00:20:31.960> engineering<00:20:32.440> resources<00:20:32.960> to 00:20:33.149 --> 00:20:33.159 align:start position:0% and dedicating engineering resources to 00:20:33.159 --> 00:20:34.950 align:start position:0% and dedicating engineering resources to doing<00:20:33.520> that<00:20:33.919> so<00:20:34.120> that<00:20:34.280> like<00:20:34.400> it's<00:20:34.520> not<00:20:34.679> like<00:20:34.799> oh 00:20:34.950 --> 00:20:34.960 align:start position:0% doing that so that like it's not like oh 00:20:34.960 --> 00:20:37.470 align:start position:0% doing that so that like it's not like oh I<00:20:35.120> really<00:20:35.280> hope<00:20:35.520> this<00:20:35.679> tool<00:20:36.000> Works<00:20:36.960> um<00:20:37.320> when 00:20:37.470 --> 00:20:37.480 align:start position:0% I really hope this tool Works um when 00:20:37.480 --> 00:20:39.390 align:start position:0% I really hope this tool Works um when you're<00:20:37.679> actually<00:20:37.919> in<00:20:38.039> the<00:20:38.400> incident 00:20:39.390 --> 00:20:39.400 align:start position:0% you're actually in the incident 00:20:39.400 --> 00:20:41.350 align:start position:0% you're actually in the incident excellent<00:20:39.840> answer<00:20:40.240> fantastic<00:20:40.760> we<00:20:40.880> got<00:20:41.000> a<00:20:41.120> few 00:20:41.350 --> 00:20:41.360 align:start position:0% excellent answer fantastic we got a few 00:20:41.360 --> 00:20:42.590 align:start position:0% excellent answer fantastic we got a few a<00:20:41.480> little<00:20:41.640> a<00:20:41.720> little<00:20:41.880> bit<00:20:42.000> more<00:20:42.159> time<00:20:42.440> let's 00:20:42.590 --> 00:20:42.600 align:start position:0% a little a little bit more time let's 00:20:42.600 --> 00:20:44.390 align:start position:0% a little a little bit more time let's try<00:20:42.720> and<00:20:42.840> do<00:20:42.960> one<00:20:43.080> or<00:20:43.200> two<00:20:43.360> more<00:20:43.799> any<00:20:44.039> way<00:20:44.200> to 00:20:44.390 --> 00:20:44.400 align:start position:0% try and do one or two more any way to 00:20:44.400 --> 00:20:47.149 align:start position:0% try and do one or two more any way to react<00:20:44.720> to<00:20:44.880> layer<00:20:45.200> one<00:20:45.480> protocol<00:20:46.000> incidents<00:20:46.919> uh 00:20:47.149 --> 00:20:47.159 align:start position:0% react to layer one protocol incidents uh 00:20:47.159 --> 00:20:48.789 align:start position:0% react to layer one protocol incidents uh yes<00:20:47.320> so<00:20:47.600> I<00:20:47.679> think<00:20:47.880> that<00:20:48.240> we<00:20:48.480> want<00:20:48.600> we're 00:20:48.789 --> 00:20:48.799 align:start position:0% yes so I think that we want we're 00:20:48.799 --> 00:20:50.669 align:start position:0% yes so I think that we want we're thinking<00:20:49.080> about<00:20:49.320> some<00:20:49.520> fun<00:20:49.840> things<00:20:50.080> to<00:20:50.240> do<00:20:50.520> on 00:20:50.669 --> 00:20:50.679 align:start position:0% thinking about some fun things to do on 00:20:50.679 --> 00:20:53.789 align:start position:0% thinking about some fun things to do on the<00:20:50.880> layer<00:20:51.200> one<00:20:51.559> like<00:20:51.720> maybe<00:20:52.000> related<00:20:52.400> to<00:20:53.360> um 00:20:53.789 --> 00:20:53.799 align:start position:0% the layer one like maybe related to um 00:20:53.799 --> 00:20:56.070 align:start position:0% the layer one like maybe related to um like<00:20:54.120> major<00:20:54.760> protocol<00:20:55.280> major<00:20:55.559> like<00:20:55.720> L1 00:20:56.070 --> 00:20:56.080 align:start position:0% like major protocol major like L1 00:20:56.080 --> 00:20:58.029 align:start position:0% like major protocol major like L1 protocol<00:20:56.520> upgrades<00:20:57.080> thinking<00:20:57.400> about<00:20:57.919> what 00:20:58.029 --> 00:20:58.039 align:start position:0% protocol upgrades thinking about what 00:20:58.039 --> 00:20:59.669 align:start position:0% protocol upgrades thinking about what could<00:20:58.240> happen<00:20:58.640> if<00:20:58.760> there's<00:20:58.960> major<00:20:59.280> chain 00:20:59.669 --> 00:20:59.679 align:start position:0% could happen if there's major chain 00:20:59.679 --> 00:21:01.870 align:start position:0% could happen if there's major chain splits<00:21:00.039> or<00:21:00.159> Forks<00:21:00.559> or<00:21:00.720> bugs<00:21:00.960> in<00:21:01.120> a<00:21:01.240> certain 00:21:01.870 --> 00:21:01.880 align:start position:0% splits or Forks or bugs in a certain 00:21:01.880 --> 00:21:03.870 align:start position:0% splits or Forks or bugs in a certain consensus<00:21:02.360> client<00:21:02.640> but<00:21:02.760> not<00:21:02.960> another<00:21:03.280> one 00:21:03.870 --> 00:21:03.880 align:start position:0% consensus client but not another one 00:21:03.880 --> 00:21:06.990 align:start position:0% consensus client but not another one like<00:21:04.120> what<00:21:04.679> chaos<00:21:05.200> could<00:21:05.400> we<00:21:05.919> simulate<00:21:06.679> across 00:21:06.990 --> 00:21:07.000 align:start position:0% like what chaos could we simulate across 00:21:07.000 --> 00:21:09.110 align:start position:0% like what chaos could we simulate across the<00:21:07.240> whole<00:21:07.440> ecosystem<00:21:08.039> if<00:21:08.280> upgrades<00:21:08.799> perhaps 00:21:09.110 --> 00:21:09.120 align:start position:0% the whole ecosystem if upgrades perhaps 00:21:09.120 --> 00:21:11.350 align:start position:0% the whole ecosystem if upgrades perhaps go<00:21:09.320> really<00:21:09.600> poorly<00:21:10.360> or<00:21:10.520> if<00:21:10.679> there's<00:21:10.880> bugs<00:21:11.159> or 00:21:11.350 --> 00:21:11.360 align:start position:0% go really poorly or if there's bugs or 00:21:11.360 --> 00:21:13.269 align:start position:0% go really poorly or if there's bugs or supply<00:21:11.640> chain<00:21:11.880> attacks<00:21:12.240> into<00:21:12.480> major<00:21:12.880> like<00:21:13.159> uh 00:21:13.269 --> 00:21:13.279 align:start position:0% supply chain attacks into major like uh 00:21:13.279 --> 00:21:15.750 align:start position:0% supply chain attacks into major like uh validator<00:21:13.840> code<00:21:14.720> um<00:21:14.919> of<00:21:15.039> course<00:21:15.320> like<00:21:15.600> these 00:21:15.750 --> 00:21:15.760 align:start position:0% validator code um of course like these 00:21:15.760 --> 00:21:17.230 align:start position:0% validator code um of course like these are<00:21:15.919> things<00:21:16.120> that<00:21:16.520> shouldn't<00:21:16.840> and<00:21:17.000> probably 00:21:17.230 --> 00:21:17.240 align:start position:0% are things that shouldn't and probably 00:21:17.240 --> 00:21:18.750 align:start position:0% are things that shouldn't and probably won't<00:21:17.440> ever<00:21:17.640> happen<00:21:17.919> but<00:21:18.039> it's<00:21:18.240> fun<00:21:18.480> to 00:21:18.750 --> 00:21:18.760 align:start position:0% won't ever happen but it's fun to 00:21:18.760 --> 00:21:20.909 align:start position:0% won't ever happen but it's fun to practice<00:21:19.760> uh<00:21:19.880> and<00:21:20.000> I<00:21:20.080> think<00:21:20.240> worthwhile<00:21:20.720> to 00:21:20.909 --> 00:21:20.919 align:start position:0% practice uh and I think worthwhile to 00:21:20.919 --> 00:21:23.950 align:start position:0% practice uh and I think worthwhile to practice<00:21:21.480> uh<00:21:21.880> the<00:21:22.240> response<00:21:23.240> excellent<00:21:23.679> Isa 00:21:23.950 --> 00:21:23.960 align:start position:0% practice uh the response excellent Isa 00:21:23.960 --> 00:21:25.470 align:start position:0% practice uh the response excellent Isa you<00:21:24.080> got<00:21:24.200> one<00:21:24.320> minute<00:21:24.520> for<00:21:24.640> the<00:21:24.799> last<00:21:25.000> question 00:21:25.470 --> 00:21:25.480 align:start position:0% you got one minute for the last question 00:21:25.480 --> 00:21:26.669 align:start position:0% you got one minute for the last question do<00:21:25.600> you<00:21:25.760> go<00:21:25.960> through<00:21:26.120> the<00:21:26.240> worst<00:21:26.559> case 00:21:26.669 --> 00:21:26.679 align:start position:0% do you go through the worst case 00:21:26.679 --> 00:21:28.350 align:start position:0% do you go through the worst case scenarios<00:21:27.080> in<00:21:27.240> war<00:21:27.440> games<00:21:27.720> for<00:21:27.880> example<00:21:28.200> you 00:21:28.350 --> 00:21:28.360 align:start position:0% scenarios in war games for example you 00:21:28.360 --> 00:21:30.350 align:start position:0% scenarios in war games for example you got<00:21:28.640> hack<00:21:28.960> money's<00:21:29.320> lost<00:21:29.679> what<00:21:29.840> now<00:21:30.000> do<00:21:30.120> you<00:21:30.240> go 00:21:30.350 --> 00:21:30.360 align:start position:0% got hack money's lost what now do you go 00:21:30.360 --> 00:21:32.029 align:start position:0% got hack money's lost what now do you go to<00:21:30.679> contact<00:21:31.120> Law<00:21:31.440> contact<00:21:31.760> with<00:21:31.880> law 00:21:32.029 --> 00:21:32.039 align:start position:0% to contact Law contact with law 00:21:32.039 --> 00:21:34.510 align:start position:0% to contact Law contact with law enforcement<00:21:32.960> uh<00:21:33.200> typically<00:21:34.000> I<00:21:34.320> actually 00:21:34.510 --> 00:21:34.520 align:start position:0% enforcement uh typically I actually 00:21:34.520 --> 00:21:35.630 align:start position:0% enforcement uh typically I actually that's<00:21:34.640> a<00:21:34.760> really<00:21:34.919> good<00:21:35.080> question<00:21:35.440> which<00:21:35.559> I 00:21:35.630 --> 00:21:35.640 align:start position:0% that's a really good question which I 00:21:35.640 --> 00:21:37.470 align:start position:0% that's a really good question which I didn't<00:21:35.840> touch<00:21:36.039> on<00:21:36.240> which<00:21:36.360> is<00:21:36.480> like<00:21:36.919> we<00:21:37.080> try<00:21:37.320> not 00:21:37.470 --> 00:21:37.480 align:start position:0% didn't touch on which is like we try not 00:21:37.480 --> 00:21:38.950 align:start position:0% didn't touch on which is like we try not to<00:21:37.640> just<00:21:37.799> make<00:21:38.000> these<00:21:38.200> like<00:21:38.320> an<00:21:38.559> instant 00:21:38.950 --> 00:21:38.960 align:start position:0% to just make these like an instant 00:21:38.960 --> 00:21:41.230 align:start position:0% to just make these like an instant wrecked<00:21:39.400> scenario<00:21:40.080> because<00:21:40.200> it's<00:21:40.400> no<00:21:40.600> fun<00:21:41.120> if 00:21:41.230 --> 00:21:41.240 align:start position:0% wrecked scenario because it's no fun if 00:21:41.240 --> 00:21:43.430 align:start position:0% wrecked scenario because it's no fun if we<00:21:41.440> just<00:21:41.640> say<00:21:42.279> protocol<00:21:42.679> was<00:21:42.840> upgraded 00:21:43.430 --> 00:21:43.440 align:start position:0% we just say protocol was upgraded 00:21:43.440 --> 00:21:45.390 align:start position:0% we just say protocol was upgraded there's<00:21:43.600> a<00:21:43.799> bug<00:21:44.279> all<00:21:44.440> the<00:21:44.559> money's<00:21:44.919> lost<00:21:45.240> you 00:21:45.390 --> 00:21:45.400 align:start position:0% there's a bug all the money's lost you 00:21:45.400 --> 00:21:47.310 align:start position:0% there's a bug all the money's lost you can't<00:21:45.600> do<00:21:45.799> anything<00:21:46.440> like<00:21:46.600> that's<00:21:46.760> no<00:21:46.880> fun<00:21:47.120> for 00:21:47.310 --> 00:21:47.320 align:start position:0% can't do anything like that's no fun for 00:21:47.320 --> 00:21:49.070 align:start position:0% can't do anything like that's no fun for anybody<00:21:47.919> so<00:21:48.080> we<00:21:48.200> try<00:21:48.400> to<00:21:48.520> make<00:21:48.640> it<00:21:48.799> something 00:21:49.070 --> 00:21:49.080 align:start position:0% anybody so we try to make it something 00:21:49.080 --> 00:21:51.230 align:start position:0% anybody so we try to make it something that's<00:21:49.320> like<00:21:49.720> recoverable<00:21:50.720> that<00:21:50.840> they<00:21:50.960> could 00:21:51.230 --> 00:21:51.240 align:start position:0% that's like recoverable that they could 00:21:51.240 --> 00:21:54.390 align:start position:0% that's like recoverable that they could actually<00:21:51.679> respond<00:21:52.120> to<00:21:53.039> um<00:21:53.520> but<00:21:53.919> uh<00:21:54.039> I<00:21:54.159> think 00:21:54.390 --> 00:21:54.400 align:start position:0% actually respond to um but uh I think 00:21:54.400 --> 00:21:57.269 align:start position:0% actually respond to um but uh I think yeah<00:21:54.559> actually<00:21:54.799> on<00:21:55.000> the<00:21:55.279> last<00:21:55.559> one<00:21:56.400> um<00:21:57.039> uh 00:21:57.269 --> 00:21:57.279 align:start position:0% yeah actually on the last one um uh 00:21:57.279 --> 00:21:59.789 align:start position:0% yeah actually on the last one um uh where<00:21:57.880> we<00:21:58.080> had<00:21:58.240> like<00:21:58.640> some<00:21:58.840> money<00:21:59.120> stolen<00:21:59.720> they 00:21:59.789 --> 00:21:59.799 align:start position:0% where we had like some money stolen they 00:21:59.799 --> 00:22:01.310 align:start position:0% where we had like some money stolen they were<00:21:59.960> like<00:22:00.200> okay<00:22:00.400> now<00:22:00.679> what<00:22:00.799> we<00:22:00.960> would<00:22:01.200> how 00:22:01.310 --> 00:22:01.320 align:start position:0% were like okay now what we would how 00:22:01.320 --> 00:22:02.830 align:start position:0% were like okay now what we would how would<00:22:01.480> we<00:22:01.640> actually<00:22:01.880> try<00:22:02.039> to<00:22:02.200> like<00:22:02.320> Chase<00:22:02.600> down 00:22:02.830 --> 00:22:02.840 align:start position:0% would we actually try to like Chase down 00:22:02.840 --> 00:22:05.029 align:start position:0% would we actually try to like Chase down this<00:22:02.960> money<00:22:03.240> that<00:22:03.360> we<00:22:03.480> got<00:22:03.960> that<00:22:04.200> was<00:22:04.440> that<00:22:04.760> was 00:22:05.029 --> 00:22:05.039 align:start position:0% this money that we got that was that was 00:22:05.039 --> 00:22:06.950 align:start position:0% this money that we got that was that was uh<00:22:05.240> was<00:22:05.360> stolen<00:22:06.000> and<00:22:06.120> the<00:22:06.200> answer<00:22:06.400> is<00:22:06.559> like 00:22:06.950 --> 00:22:06.960 align:start position:0% uh was stolen and the answer is like 00:22:06.960 --> 00:22:08.549 align:start position:0% uh was stolen and the answer is like that's<00:22:07.080> something<00:22:07.320> you<00:22:07.400> can<00:22:07.520> go<00:22:07.600> to<00:22:07.720> seal<00:22:08.000> 911 00:22:08.549 --> 00:22:08.559 align:start position:0% that's something you can go to seal 911 00:22:08.559 --> 00:22:10.190 align:start position:0% that's something you can go to seal 911 for<00:22:09.039> uh<00:22:09.200> because<00:22:09.360> they<00:22:09.480> have<00:22:09.679> really<00:22:09.919> good 00:22:10.190 --> 00:22:10.200 align:start position:0% for uh because they have really good 00:22:10.200 --> 00:22:12.310 align:start position:0% for uh because they have really good like<00:22:10.400> tracing<00:22:11.200> people<00:22:11.559> that<00:22:11.679> can<00:22:11.880> like<00:22:12.000> say 00:22:12.310 --> 00:22:12.320 align:start position:0% like tracing people that can like say 00:22:12.320 --> 00:22:13.669 align:start position:0% like tracing people that can like say okay<00:22:12.679> now<00:22:12.840> we're<00:22:12.960> going<00:22:13.080> to<00:22:13.200> see<00:22:13.440> where<00:22:13.600> the 00:22:13.669 --> 00:22:13.679 align:start position:0% okay now we're going to see where the 00:22:13.679 --> 00:22:15.390 align:start position:0% okay now we're going to see where the money's<00:22:14.080> gone<00:22:14.360> and<00:22:14.559> try<00:22:14.679> to<00:22:14.799> recover<00:22:15.120> it<00:22:15.240> in 00:22:15.390 --> 00:22:15.400 align:start position:0% money's gone and try to recover it in 00:22:15.400 --> 00:22:17.990 align:start position:0% money's gone and try to recover it in other<00:22:15.640> ways<00:22:16.240> um<00:22:16.400> and<00:22:16.559> so<00:22:17.240> uh<00:22:17.400> yeah<00:22:17.559> if<00:22:17.640> you<00:22:17.760> get 00:22:17.990 --> 00:22:18.000 align:start position:0% other ways um and so uh yeah if you get 00:22:18.000 --> 00:22:20.710 align:start position:0% other ways um and so uh yeah if you get hacked<00:22:18.760> uh<00:22:19.279> uh<00:22:19.440> first<00:22:19.720> fix<00:22:20.000> the<00:22:20.159> protocol<00:22:20.600> but 00:22:20.710 --> 00:22:20.720 align:start position:0% hacked uh uh first fix the protocol but 00:22:20.720 --> 00:22:22.750 align:start position:0% hacked uh uh first fix the protocol but then<00:22:20.919> yeah<00:22:21.080> we<00:22:21.159> can<00:22:21.320> also<00:22:21.559> help<00:22:21.760> you<00:22:22.279> uh<00:22:22.400> track 00:22:22.750 --> 00:22:22.760 align:start position:0% then yeah we can also help you uh track 00:22:22.760 --> 00:22:25.549 align:start position:0% then yeah we can also help you uh track down<00:22:22.880> the<00:22:23.159> money<00:22:24.159> excellent<00:22:24.799> wow<00:22:25.039> we<00:22:25.159> finished 00:22:25.549 --> 00:22:25.559 align:start position:0% down the money excellent wow we finished 00:22:25.559 --> 00:22:27.149 align:start position:0% down the money excellent wow we finished all<00:22:25.760> the<00:22:25.919> questions<00:22:26.240> in<00:22:26.400> record<00:22:26.799> time<00:22:27.000> let's 00:22:27.149 --> 00:22:27.159 align:start position:0% all the questions in record time let's 00:22:27.159 --> 00:22:29.029 align:start position:0% all the questions in record time let's give<00:22:27.320> Isaac<00:22:27.600> a<00:22:27.679> big<00:22:27.840> round<00:22:28.000> of<00:22:28.120> applause<00:22:28.840> well 00:22:29.029 --> 00:22:29.039 align:start position:0% give Isaac a big round of applause well 00:22:29.039 --> 00:22:32.559 align:start position:0% give Isaac a big round of applause well done<00:22:29.360> thank<00:22:29.520> you<00:22:29.640> so<00:22:29.760> much<00:22:30.000> Isaac<00:22:30.360> well