WEBVTT Kind: captions Language: en 00:00:00.000 --> 00:00:04.350 align:start position:0% foreign 00:00:04.350 --> 00:00:04.360 align:start position:0% 00:00:04.360 --> 00:00:11.890 align:start position:0% [Music] 00:00:11.890 --> 00:00:11.900 align:start position:0% 00:00:11.900 --> 00:00:14.209 align:start position:0% my<00:00:12.900> name<00:00:12.960> is<00:00:13.080> David<00:00:13.259> Snyder<00:00:13.740> that's<00:00:14.040> Chris 00:00:14.209 --> 00:00:14.219 align:start position:0% my name is David Snyder that's Chris 00:00:14.219 --> 00:00:16.430 align:start position:0% my name is David Snyder that's Chris casano<00:00:14.880> and<00:00:15.120> as<00:00:15.360> you<00:00:15.480> can<00:00:15.660> see<00:00:15.839> we're<00:00:16.199> going<00:00:16.379> to 00:00:16.430 --> 00:00:16.440 align:start position:0% casano and as you can see we're going to 00:00:16.440 --> 00:00:18.710 align:start position:0% casano and as you can see we're going to talk<00:00:16.560> about<00:00:16.940> decentralized<00:00:17.940> programmable 00:00:18.710 --> 00:00:18.720 align:start position:0% talk about decentralized programmable 00:00:18.720 --> 00:00:21.650 align:start position:0% talk about decentralized programmable key<00:00:19.080> pairs<00:00:19.560> we<00:00:20.220> are<00:00:20.340> the<00:00:20.520> two<00:00:20.820> co-founders<00:00:21.359> of 00:00:21.650 --> 00:00:21.660 align:start position:0% key pairs we are the two co-founders of 00:00:21.660 --> 00:00:23.990 align:start position:0% key pairs we are the two co-founders of a<00:00:21.840> project<00:00:22.020> called<00:00:22.439> lit<00:00:22.800> protocol<00:00:23.100> and<00:00:23.880> to 00:00:23.990 --> 00:00:24.000 align:start position:0% a project called lit protocol and to 00:00:24.000 --> 00:00:26.269 align:start position:0% a project called lit protocol and to start<00:00:24.180> with<00:00:24.420> a<00:00:24.660> big<00:00:24.840> exciting<00:00:25.439> hook<00:00:25.680> we<00:00:26.160> are 00:00:26.269 --> 00:00:26.279 align:start position:0% start with a big exciting hook we are 00:00:26.279 --> 00:00:28.130 align:start position:0% start with a big exciting hook we are living<00:00:26.460> in<00:00:26.699> a<00:00:26.880> world<00:00:27.000> where<00:00:27.480> with<00:00:27.779> threshold 00:00:28.130 --> 00:00:28.140 align:start position:0% living in a world where with threshold 00:00:28.140 --> 00:00:30.170 align:start position:0% living in a world where with threshold cryptography<00:00:28.859> from<00:00:29.340> a<00:00:29.580> certain<00:00:29.760> point<00:00:30.000> of 00:00:30.170 --> 00:00:30.180 align:start position:0% cryptography from a certain point of 00:00:30.180 --> 00:00:33.350 align:start position:0% cryptography from a certain point of view<00:00:30.300> you<00:00:31.140> can<00:00:31.320> consider<00:00:31.920> that<00:00:32.340> private<00:00:32.880> Keys 00:00:33.350 --> 00:00:33.360 align:start position:0% view you can consider that private Keys 00:00:33.360 --> 00:00:35.330 align:start position:0% view you can consider that private Keys no<00:00:33.719> longer<00:00:33.960> exist<00:00:34.380> so<00:00:34.980> what<00:00:35.100> do<00:00:35.219> we 00:00:35.330 --> 00:00:35.340 align:start position:0% no longer exist so what do we 00:00:35.340 --> 00:00:38.150 align:start position:0% no longer exist so what do we specifically<00:00:35.820> mean<00:00:36.059> by<00:00:36.239> this<00:00:36.480> this<00:00:37.320> netlit 00:00:38.150 --> 00:00:38.160 align:start position:0% specifically mean by this this netlit 00:00:38.160 --> 00:00:41.090 align:start position:0% specifically mean by this this netlit network<00:00:38.399> is<00:00:39.360> essentially<00:00:39.899> a<00:00:40.559> distributed 00:00:41.090 --> 00:00:41.100 align:start position:0% network is essentially a distributed 00:00:41.100 --> 00:00:44.150 align:start position:0% network is essentially a distributed custody<00:00:41.840> programmable<00:00:42.840> key<00:00:43.260> and<00:00:43.739> one<00:00:43.980> of<00:00:44.040> the 00:00:44.150 --> 00:00:44.160 align:start position:0% custody programmable key and one of the 00:00:44.160 --> 00:00:46.250 align:start position:0% custody programmable key and one of the key<00:00:44.399> Technologies<00:00:45.000> at<00:00:45.239> the<00:00:45.360> heart<00:00:45.480> of<00:00:45.660> this<00:00:45.840> is 00:00:46.250 --> 00:00:46.260 align:start position:0% key Technologies at the heart of this is 00:00:46.260 --> 00:00:48.770 align:start position:0% key Technologies at the heart of this is something<00:00:46.440> called<00:00:46.800> a<00:00:47.160> dkg<00:00:47.640> a<00:00:48.120> distributed<00:00:48.539> key 00:00:48.770 --> 00:00:48.780 align:start position:0% something called a dkg a distributed key 00:00:48.780 --> 00:00:51.049 align:start position:0% something called a dkg a distributed key generation<00:00:49.379> and<00:00:50.039> so<00:00:50.219> what<00:00:50.520> lit<00:00:50.879> is 00:00:51.049 --> 00:00:51.059 align:start position:0% generation and so what lit is 00:00:51.059 --> 00:00:53.690 align:start position:0% generation and so what lit is specifically<00:00:51.719> is<00:00:52.379> a<00:00:52.620> distributed<00:00:53.100> network<00:00:53.340> of 00:00:53.690 --> 00:00:53.700 align:start position:0% specifically is a distributed network of 00:00:53.700 --> 00:00:56.750 align:start position:0% specifically is a distributed network of nodes<00:00:54.059> that<00:00:54.660> are<00:00:54.780> custodying<00:00:55.440> shares<00:00:56.100> of<00:00:56.520> an 00:00:56.750 --> 00:00:56.760 align:start position:0% nodes that are custodying shares of an 00:00:56.760 --> 00:00:59.090 align:start position:0% nodes that are custodying shares of an underlying<00:00:57.239> private<00:00:57.660> key<00:00:57.840> I'll<00:00:58.559> take<00:00:58.800> a<00:00:58.980> quick 00:00:59.090 --> 00:00:59.100 align:start position:0% underlying private key I'll take a quick 00:00:59.100 --> 00:01:01.069 align:start position:0% underlying private key I'll take a quick moment<00:00:59.399> to<00:00:59.640> talk<00:00:59.760> about<00:00:59.940> how<00:01:00.300> security<00:01:00.539> works 00:01:01.069 --> 00:01:01.079 align:start position:0% moment to talk about how security works 00:01:01.079 --> 00:01:03.110 align:start position:0% moment to talk about how security works on<00:01:01.199> this<00:01:01.440> network<00:01:01.620> and<00:01:02.340> then<00:01:02.460> we'll<00:01:02.699> get<00:01:02.940> into 00:01:03.110 --> 00:01:03.120 align:start position:0% on this network and then we'll get into 00:01:03.120 --> 00:01:05.750 align:start position:0% on this network and then we'll get into some<00:01:03.420> of<00:01:03.480> the<00:01:03.600> use<00:01:03.840> cases<00:01:04.280> but<00:01:05.280> essentially 00:01:05.750 --> 00:01:05.760 align:start position:0% some of the use cases but essentially 00:01:05.760 --> 00:01:08.750 align:start position:0% some of the use cases but essentially this<00:01:06.600> key<00:01:06.780> is<00:01:07.020> formed<00:01:07.439> in<00:01:08.159> this<00:01:08.340> distributed 00:01:08.750 --> 00:01:08.760 align:start position:0% this key is formed in this distributed 00:01:08.760 --> 00:01:10.910 align:start position:0% this key is formed in this distributed key<00:01:08.939> generation<00:01:09.420> context<00:01:09.960> and<00:01:10.439> stored<00:01:10.799> as 00:01:10.910 --> 00:01:10.920 align:start position:0% key generation context and stored as 00:01:10.920 --> 00:01:13.310 align:start position:0% key generation context and stored as shares<00:01:11.340> across<00:01:11.580> the<00:01:11.640> these<00:01:12.180> nodes<00:01:12.479> and<00:01:13.200> then 00:01:13.310 --> 00:01:13.320 align:start position:0% shares across the these nodes and then 00:01:13.320 --> 00:01:15.770 align:start position:0% shares across the these nodes and then all<00:01:13.500> the<00:01:13.740> nodes<00:01:14.040> operations<00:01:14.700> take<00:01:15.540> place 00:01:15.770 --> 00:01:15.780 align:start position:0% all the nodes operations take place 00:01:15.780 --> 00:01:17.690 align:start position:0% all the nodes operations take place inside<00:01:16.140> of<00:01:16.439> a<00:01:16.680> trusted<00:01:17.100> execution 00:01:17.690 --> 00:01:17.700 align:start position:0% inside of a trusted execution 00:01:17.700 --> 00:01:19.789 align:start position:0% inside of a trusted execution environment<00:01:18.240> and<00:01:18.900> then<00:01:19.020> there<00:01:19.320> are<00:01:19.500> named 00:01:19.789 --> 00:01:19.799 align:start position:0% environment and then there are named 00:01:19.799 --> 00:01:22.670 align:start position:0% environment and then there are named node<00:01:20.100> operators<00:01:20.580> who<00:01:20.939> are<00:01:21.060> staking<00:01:21.500> that<00:01:22.500> are 00:01:22.670 --> 00:01:22.680 align:start position:0% node operators who are staking that are 00:01:22.680 --> 00:01:24.770 align:start position:0% node operators who are staking that are running<00:01:22.920> the<00:01:23.280> programs<00:01:23.820> on<00:01:24.180> this<00:01:24.299> underlying 00:01:24.770 --> 00:01:24.780 align:start position:0% running the programs on this underlying 00:01:24.780 --> 00:01:26.690 align:start position:0% running the programs on this underlying key<00:01:24.960> and<00:01:25.619> so<00:01:25.799> now<00:01:25.920> let's<00:01:26.100> talk<00:01:26.280> about<00:01:26.400> what 00:01:26.690 --> 00:01:26.700 align:start position:0% key and so now let's talk about what 00:01:26.700 --> 00:01:29.990 align:start position:0% key and so now let's talk about what some<00:01:26.880> of<00:01:27.000> those<00:01:27.180> programs<00:01:28.020> can<00:01:28.619> be<00:01:28.799> so<00:01:29.580> as<00:01:29.880> you 00:01:29.990 --> 00:01:30.000 align:start position:0% some of those programs can be so as you 00:01:30.000 --> 00:01:32.690 align:start position:0% some of those programs can be so as you know<00:01:30.180> a<00:01:30.600> key<00:01:30.780> can<00:01:31.680> functionally<00:01:32.100> do<00:01:32.460> two 00:01:32.690 --> 00:01:32.700 align:start position:0% know a key can functionally do two 00:01:32.700 --> 00:01:35.870 align:start position:0% know a key can functionally do two things<00:01:32.939> it<00:01:33.479> can<00:01:33.659> read<00:01:34.080> or<00:01:34.500> encrypt<00:01:35.100> and<00:01:35.579> write 00:01:35.870 --> 00:01:35.880 align:start position:0% things it can read or encrypt and write 00:01:35.880 --> 00:01:38.330 align:start position:0% things it can read or encrypt and write and<00:01:36.600> this<00:01:36.780> network<00:01:37.020> provides<00:01:37.740> the<00:01:38.100> same 00:01:38.330 --> 00:01:38.340 align:start position:0% and this network provides the same 00:01:38.340 --> 00:01:41.569 align:start position:0% and this network provides the same functionality<00:01:39.180> in<00:01:39.900> a<00:01:40.020> programmatic<00:01:40.500> way<00:01:40.680> so 00:01:41.569 --> 00:01:41.579 align:start position:0% functionality in a programmatic way so 00:01:41.579 --> 00:01:43.130 align:start position:0% functionality in a programmatic way so let's<00:01:41.759> talk<00:01:41.939> about<00:01:42.119> how<00:01:42.420> the<00:01:42.540> read<00:01:42.720> works 00:01:43.130 --> 00:01:43.140 align:start position:0% let's talk about how the read works 00:01:43.140 --> 00:01:45.050 align:start position:0% let's talk about how the read works first<00:01:43.320> the<00:01:44.220> hexagons<00:01:44.640> in<00:01:44.820> the<00:01:44.939> middle 00:01:45.050 --> 00:01:45.060 align:start position:0% first the hexagons in the middle 00:01:45.060 --> 00:01:47.450 align:start position:0% first the hexagons in the middle represent<00:01:45.479> the<00:01:45.659> lit<00:01:45.900> nodes<00:01:46.200> in<00:01:47.159> this<00:01:47.280> case 00:01:47.450 --> 00:01:47.460 align:start position:0% represent the lit nodes in this case 00:01:47.460 --> 00:01:50.510 align:start position:0% represent the lit nodes in this case Alice<00:01:48.299> let's<00:01:48.659> say<00:01:48.840> is<00:01:49.259> a<00:01:49.500> Creator<00:01:49.799> and<00:01:50.220> wants 00:01:50.510 --> 00:01:50.520 align:start position:0% Alice let's say is a Creator and wants 00:01:50.520 --> 00:01:54.889 align:start position:0% Alice let's say is a Creator and wants to<00:01:50.640> say<00:01:50.939> anybody<00:01:51.720> who<00:01:52.079> owns<00:01:52.579> Alice's<00:01:53.579> nft<00:01:53.939> can 00:01:54.889 --> 00:01:54.899 align:start position:0% to say anybody who owns Alice's nft can 00:01:54.899 --> 00:01:57.469 align:start position:0% to say anybody who owns Alice's nft can see<00:01:55.560> her<00:01:55.799> video<00:01:56.100> she<00:01:56.759> would<00:01:56.939> encrypt<00:01:57.360> that 00:01:57.469 --> 00:01:57.479 align:start position:0% see her video she would encrypt that 00:01:57.479 --> 00:01:59.690 align:start position:0% see her video she would encrypt that video<00:01:57.720> client<00:01:58.200> side<00:01:58.439> and<00:01:58.920> store<00:01:59.100> it<00:01:59.280> somewhere 00:01:59.690 --> 00:01:59.700 align:start position:0% video client side and store it somewhere 00:01:59.700 --> 00:02:01.910 align:start position:0% video client side and store it somewhere in<00:01:59.939> public<00:02:00.119> whether<00:02:00.479> it's<00:02:00.659> on<00:02:00.960> a<00:02:01.439> blockchain 00:02:01.910 --> 00:02:01.920 align:start position:0% in public whether it's on a blockchain 00:02:01.920 --> 00:02:04.789 align:start position:0% in public whether it's on a blockchain or<00:02:02.399> a<00:02:02.520> storage<00:02:02.640> Network<00:02:03.000> like<00:02:03.360> ipfs<00:02:04.020> and<00:02:04.680> then 00:02:04.789 --> 00:02:04.799 align:start position:0% or a storage Network like ipfs and then 00:02:04.799 --> 00:02:07.249 align:start position:0% or a storage Network like ipfs and then create<00:02:05.040> a<00:02:05.219> set<00:02:05.399> of<00:02:05.520> rules<00:02:05.939> that<00:02:06.479> says<00:02:06.840> only 00:02:07.249 --> 00:02:07.259 align:start position:0% create a set of rules that says only 00:02:07.259 --> 00:02:10.790 align:start position:0% create a set of rules that says only somebody<00:02:07.680> who<00:02:08.039> owns<00:02:08.340> Alice's<00:02:08.880> nft<00:02:09.380> can<00:02:10.380> see 00:02:10.790 --> 00:02:10.800 align:start position:0% somebody who owns Alice's nft can see 00:02:10.800 --> 00:02:14.030 align:start position:0% somebody who owns Alice's nft can see that<00:02:11.039> video<00:02:11.700> Bob<00:02:12.239> owns<00:02:12.720> that<00:02:12.840> nft<00:02:13.140> he<00:02:13.680> shows<00:02:13.920> up 00:02:14.030 --> 00:02:14.040 align:start position:0% that video Bob owns that nft he shows up 00:02:14.040 --> 00:02:16.550 align:start position:0% that video Bob owns that nft he shows up later<00:02:14.280> he<00:02:14.640> signs<00:02:15.060> a<00:02:15.180> message<00:02:15.420> and<00:02:16.319> he 00:02:16.550 --> 00:02:16.560 align:start position:0% later he signs a message and he 00:02:16.560 --> 00:02:19.010 align:start position:0% later he signs a message and he broadcasts<00:02:17.099> that<00:02:17.220> to<00:02:17.520> the<00:02:17.700> nodes<00:02:17.940> each<00:02:18.720> of<00:02:18.840> the 00:02:19.010 --> 00:02:19.020 align:start position:0% broadcasts that to the nodes each of the 00:02:19.020 --> 00:02:20.930 align:start position:0% broadcasts that to the nodes each of the individual<00:02:19.379> nodes<00:02:19.800> validates<00:02:20.400> against<00:02:20.640> the 00:02:20.930 --> 00:02:20.940 align:start position:0% individual nodes validates against the 00:02:20.940 --> 00:02:24.229 align:start position:0% individual nodes validates against the blockchain<00:02:21.360> does<00:02:22.200> Bob<00:02:22.440> own<00:02:22.739> that<00:02:22.980> nft<00:02:23.340> and<00:02:24.120> the 00:02:24.229 --> 00:02:24.239 align:start position:0% blockchain does Bob own that nft and the 00:02:24.239 --> 00:02:26.030 align:start position:0% blockchain does Bob own that nft and the whole<00:02:24.420> kind<00:02:24.599> of<00:02:24.720> frame<00:02:25.140> of<00:02:25.319> view<00:02:25.500> here<00:02:25.680> is 00:02:26.030 --> 00:02:26.040 align:start position:0% whole kind of frame of view here is 00:02:26.040 --> 00:02:28.190 align:start position:0% whole kind of frame of view here is thinking<00:02:26.280> about<00:02:26.400> these<00:02:26.760> Public<00:02:26.940> Storage<00:02:27.420> uh 00:02:28.190 --> 00:02:28.200 align:start position:0% thinking about these Public Storage uh 00:02:28.200 --> 00:02:30.110 align:start position:0% thinking about these Public Storage uh excuse<00:02:28.500> me<00:02:28.620> public<00:02:28.860> State<00:02:29.099> machines<00:02:29.580> as 00:02:30.110 --> 00:02:30.120 align:start position:0% excuse me public State machines as 00:02:30.120 --> 00:02:32.330 align:start position:0% excuse me public State machines as Access<00:02:30.420> Control<00:02:30.900> lists<00:02:31.379> at<00:02:31.800> which<00:02:31.920> point<00:02:32.160> the 00:02:32.330 --> 00:02:32.340 align:start position:0% Access Control lists at which point the 00:02:32.340 --> 00:02:34.610 align:start position:0% Access Control lists at which point the nodes<00:02:32.520> verify<00:02:33.060> that<00:02:33.239> Bob<00:02:33.480> has<00:02:33.840> that<00:02:34.080> node<00:02:34.379> or 00:02:34.610 --> 00:02:34.620 align:start position:0% nodes verify that Bob has that node or 00:02:34.620 --> 00:02:36.770 align:start position:0% nodes verify that Bob has that node or excuse<00:02:34.920> me<00:02:34.980> has<00:02:35.160> that<00:02:35.340> nft<00:02:35.640> and<00:02:36.300> each<00:02:36.480> of<00:02:36.660> the 00:02:36.770 --> 00:02:36.780 align:start position:0% excuse me has that nft and each of the 00:02:36.780 --> 00:02:38.089 align:start position:0% excuse me has that nft and each of the individual<00:02:37.140> nodes<00:02:37.440> produces<00:02:37.920> something 00:02:38.089 --> 00:02:38.099 align:start position:0% individual nodes produces something 00:02:38.099 --> 00:02:40.010 align:start position:0% individual nodes produces something called<00:02:38.340> a<00:02:38.520> decryption<00:02:39.060> share<00:02:39.420> you<00:02:39.959> could 00:02:40.010 --> 00:02:40.020 align:start position:0% called a decryption share you could 00:02:40.020 --> 00:02:41.690 align:start position:0% called a decryption share you could think<00:02:40.200> about<00:02:40.379> this<00:02:40.620> like<00:02:40.860> an<00:02:41.099> authorization 00:02:41.690 --> 00:02:41.700 align:start position:0% think about this like an authorization 00:02:41.700 --> 00:02:44.930 align:start position:0% think about this like an authorization those<00:02:42.480> authorizations<00:02:43.200> are<00:02:44.040> then<00:02:44.220> sent<00:02:44.519> to 00:02:44.930 --> 00:02:44.940 align:start position:0% those authorizations are then sent to 00:02:44.940 --> 00:02:46.970 align:start position:0% those authorizations are then sent to Bob<00:02:45.180> who's<00:02:45.599> collecting<00:02:46.080> them<00:02:46.260> client-side 00:02:46.970 --> 00:02:46.980 align:start position:0% Bob who's collecting them client-side 00:02:46.980 --> 00:02:48.710 align:start position:0% Bob who's collecting them client-side and<00:02:47.519> a<00:02:47.640> good<00:02:47.760> mental<00:02:48.060> model<00:02:48.180> is<00:02:48.420> kind<00:02:48.599> of 00:02:48.710 --> 00:02:48.720 align:start position:0% and a good mental model is kind of 00:02:48.720 --> 00:02:49.850 align:start position:0% and a good mental model is kind of similar<00:02:48.959> to<00:02:49.080> the<00:02:49.260> way<00:02:49.379> that<00:02:49.500> you<00:02:49.620> may<00:02:49.680> think 00:02:49.850 --> 00:02:49.860 align:start position:0% similar to the way that you may think 00:02:49.860 --> 00:02:51.710 align:start position:0% similar to the way that you may think about<00:02:50.040> torrenting<00:02:50.760> you<00:02:51.180> know<00:02:51.239> torrenting 00:02:51.710 --> 00:02:51.720 align:start position:0% about torrenting you know torrenting 00:02:51.720 --> 00:02:53.210 align:start position:0% about torrenting you know torrenting you're<00:02:51.900> collecting<00:02:52.200> little<00:02:52.379> bits<00:02:52.680> of<00:02:52.860> media 00:02:53.210 --> 00:02:53.220 align:start position:0% you're collecting little bits of media 00:02:53.220 --> 00:02:55.309 align:start position:0% you're collecting little bits of media from<00:02:53.580> a<00:02:53.819> bunch<00:02:54.000> of<00:02:54.120> nodes<00:02:54.420> in<00:02:55.019> this<00:02:55.140> case 00:02:55.309 --> 00:02:55.319 align:start position:0% from a bunch of nodes in this case 00:02:55.319 --> 00:02:57.290 align:start position:0% from a bunch of nodes in this case you're<00:02:55.800> collecting<00:02:56.160> bits<00:02:56.519> of<00:02:56.640> authorization 00:02:57.290 --> 00:02:57.300 align:start position:0% you're collecting bits of authorization 00:02:57.300 --> 00:02:59.210 align:start position:0% you're collecting bits of authorization and<00:02:57.900> once<00:02:58.080> you've<00:02:58.200> collected<00:02:58.560> a<00:02:58.739> threshold<00:02:59.099> of 00:02:59.210 --> 00:02:59.220 align:start position:0% and once you've collected a threshold of 00:02:59.220 --> 00:03:01.009 align:start position:0% and once you've collected a threshold of those<00:02:59.400> authorizations<00:03:00.060> in<00:03:00.840> this<00:03:00.900> case 00:03:01.009 --> 00:03:01.019 align:start position:0% those authorizations in this case 00:03:01.019 --> 00:03:03.470 align:start position:0% those authorizations in this case decryption<00:03:01.680> shares<00:03:02.040> Bob<00:03:02.519> can<00:03:02.760> reproduce<00:03:03.239> that 00:03:03.470 --> 00:03:03.480 align:start position:0% decryption shares Bob can reproduce that 00:03:03.480 --> 00:03:05.330 align:start position:0% decryption shares Bob can reproduce that symmetric<00:03:03.959> key<00:03:04.200> associated<00:03:04.800> with<00:03:05.099> the<00:03:05.220> video 00:03:05.330 --> 00:03:05.340 align:start position:0% symmetric key associated with the video 00:03:05.340 --> 00:03:08.630 align:start position:0% symmetric key associated with the video or<00:03:05.700> that<00:03:05.879> content<00:03:06.300> and<00:03:07.080> decrypt<00:03:07.560> that<00:03:07.800> client 00:03:08.630 --> 00:03:08.640 align:start position:0% or that content and decrypt that client 00:03:08.640 --> 00:03:10.309 align:start position:0% or that content and decrypt that client side<00:03:08.940> and<00:03:09.360> so<00:03:09.480> some<00:03:09.660> of<00:03:09.780> the<00:03:09.900> applications 00:03:10.309 --> 00:03:10.319 align:start position:0% side and so some of the applications 00:03:10.319 --> 00:03:12.229 align:start position:0% side and so some of the applications that<00:03:10.680> we're<00:03:10.800> seeing<00:03:10.980> this<00:03:11.159> used<00:03:11.280> for<00:03:11.400> today<00:03:11.640> a 00:03:12.229 --> 00:03:12.239 align:start position:0% that we're seeing this used for today a 00:03:12.239 --> 00:03:14.990 align:start position:0% that we're seeing this used for today a are<00:03:12.540> things<00:03:12.780> like<00:03:12.959> token<00:03:13.440> gated<00:03:13.739> social<00:03:14.640> media 00:03:14.990 --> 00:03:15.000 align:start position:0% are things like token gated social media 00:03:15.000 --> 00:03:17.570 align:start position:0% are things like token gated social media like<00:03:15.180> tokengated<00:03:15.780> chat<00:03:16.260> this<00:03:16.980> technology<00:03:17.280> is 00:03:17.570 --> 00:03:17.580 align:start position:0% like tokengated chat this technology is 00:03:17.580 --> 00:03:19.009 align:start position:0% like tokengated chat this technology is used<00:03:17.760> hand<00:03:17.940> in<00:03:18.120> hand<00:03:18.239> a<00:03:18.480> lot<00:03:18.540> with<00:03:18.659> like<00:03:18.840> the 00:03:19.009 --> 00:03:19.019 align:start position:0% used hand in hand a lot with like the 00:03:19.019 --> 00:03:21.470 align:start position:0% used hand in hand a lot with like the lens<00:03:19.200> protocol<00:03:19.620> for<00:03:19.980> example<00:03:20.220> where<00:03:20.700> only<00:03:21.180> let 00:03:21.470 --> 00:03:21.480 align:start position:0% lens protocol for example where only let 00:03:21.480 --> 00:03:23.690 align:start position:0% lens protocol for example where only let somebody<00:03:21.720> who's<00:03:22.080> following<00:03:22.560> me<00:03:22.680> on<00:03:22.980> on<00:03:23.400> lens 00:03:23.690 --> 00:03:23.700 align:start position:0% somebody who's following me on on lens 00:03:23.700 --> 00:03:26.509 align:start position:0% somebody who's following me on on lens see<00:03:24.060> my<00:03:24.300> posts<00:03:24.720> we<00:03:25.379> also<00:03:25.560> see<00:03:25.739> this<00:03:25.920> in<00:03:26.159> uh 00:03:26.509 --> 00:03:26.519 align:start position:0% see my posts we also see this in uh 00:03:26.519 --> 00:03:28.190 align:start position:0% see my posts we also see this in uh happening<00:03:26.879> in<00:03:27.060> the<00:03:27.180> context<00:03:27.420> of<00:03:27.659> intellectual 00:03:28.190 --> 00:03:28.200 align:start position:0% happening in the context of intellectual 00:03:28.200 --> 00:03:30.070 align:start position:0% happening in the context of intellectual property<00:03:28.560> whether<00:03:28.860> it's<00:03:28.980> token<00:03:29.340> gated<00:03:29.580> videos 00:03:30.070 --> 00:03:30.080 align:start position:0% property whether it's token gated videos 00:03:30.080 --> 00:03:34.009 align:start position:0% property whether it's token gated videos or<00:03:31.080> various<00:03:31.500> other<00:03:31.739> content<00:03:32.340> and<00:03:33.060> then<00:03:33.180> really 00:03:34.009 --> 00:03:34.019 align:start position:0% or various other content and then really 00:03:34.019 --> 00:03:35.570 align:start position:0% or various other content and then really excitingly<00:03:34.500> there's<00:03:34.800> also<00:03:35.040> been<00:03:35.159> a<00:03:35.340> lot<00:03:35.459> of 00:03:35.570 --> 00:03:35.580 align:start position:0% excitingly there's also been a lot of 00:03:35.580 --> 00:03:37.729 align:start position:0% excitingly there's also been a lot of stuff<00:03:35.760> around<00:03:35.940> verifiable<00:03:36.720> credentials<00:03:37.440> and 00:03:37.729 --> 00:03:37.739 align:start position:0% stuff around verifiable credentials and 00:03:37.739 --> 00:03:39.949 align:start position:0% stuff around verifiable credentials and selective<00:03:38.220> disclosure<00:03:38.819> so<00:03:39.420> I'm<00:03:39.480> sure<00:03:39.659> you<00:03:39.780> all 00:03:39.949 --> 00:03:39.959 align:start position:0% selective disclosure so I'm sure you all 00:03:39.959 --> 00:03:41.270 align:start position:0% selective disclosure so I'm sure you all are<00:03:40.080> familiar<00:03:40.319> with<00:03:40.440> the<00:03:40.620> notion<00:03:40.920> of<00:03:41.099> like 00:03:41.270 --> 00:03:41.280 align:start position:0% are familiar with the notion of like 00:03:41.280 --> 00:03:42.949 align:start position:0% are familiar with the notion of like signing<00:03:41.760> in<00:03:41.819> with<00:03:42.060> Google<00:03:42.299> as<00:03:42.780> an 00:03:42.949 --> 00:03:42.959 align:start position:0% signing in with Google as an 00:03:42.959 --> 00:03:45.350 align:start position:0% signing in with Google as an authorization<00:03:43.560> method<00:03:44.099> for<00:03:44.519> how<00:03:44.700> one<00:03:44.879> logs 00:03:45.350 --> 00:03:45.360 align:start position:0% authorization method for how one logs 00:03:45.360 --> 00:03:47.390 align:start position:0% authorization method for how one logs into<00:03:45.420> a<00:03:45.840> site<00:03:46.019> what<00:03:46.799> we're<00:03:46.980> starting<00:03:47.099> to<00:03:47.280> see 00:03:47.390 --> 00:03:47.400 align:start position:0% into a site what we're starting to see 00:03:47.400 --> 00:03:49.610 align:start position:0% into a site what we're starting to see is<00:03:47.580> some<00:03:47.760> teams<00:03:48.060> build<00:03:48.299> this<00:03:48.480> out<00:03:48.720> in<00:03:49.319> a<00:03:49.500> much 00:03:49.610 --> 00:03:49.620 align:start position:0% is some teams build this out in a much 00:03:49.620 --> 00:03:51.890 align:start position:0% is some teams build this out in a much more<00:03:49.860> kind<00:03:50.099> of<00:03:50.220> user<00:03:50.760> Sovereign<00:03:51.180> type<00:03:51.420> of<00:03:51.599> way 00:03:51.890 --> 00:03:51.900 align:start position:0% more kind of user Sovereign type of way 00:03:51.900 --> 00:03:54.470 align:start position:0% more kind of user Sovereign type of way whereby<00:03:52.860> when<00:03:53.040> a<00:03:53.220> user<00:03:53.459> goes<00:03:53.700> logs<00:03:54.060> into<00:03:54.180> a 00:03:54.470 --> 00:03:54.480 align:start position:0% whereby when a user goes logs into a 00:03:54.480 --> 00:03:56.809 align:start position:0% whereby when a user goes logs into a site<00:03:54.659> they're<00:03:55.319> conveying<00:03:55.860> decryption<00:03:56.400> rights 00:03:56.809 --> 00:03:56.819 align:start position:0% site they're conveying decryption rights 00:03:56.819 --> 00:03:59.330 align:start position:0% site they're conveying decryption rights or<00:03:57.000> quote<00:03:57.360> the<00:03:57.540> read<00:03:57.780> writes<00:03:58.319> to<00:03:59.099> that 00:03:59.330 --> 00:03:59.340 align:start position:0% or quote the read writes to that 00:03:59.340 --> 00:04:01.850 align:start position:0% or quote the read writes to that application<00:03:59.879> to<00:04:00.720> see<00:04:00.959> their<00:04:01.440> private 00:04:01.850 --> 00:04:01.860 align:start position:0% application to see their private 00:04:01.860 --> 00:04:04.190 align:start position:0% application to see their private information<00:04:02.280> and<00:04:03.180> starts<00:04:03.480> to<00:04:03.540> become<00:04:03.780> like<00:04:03.959> a 00:04:04.190 --> 00:04:04.200 align:start position:0% information and starts to become like a 00:04:04.200 --> 00:04:05.210 align:start position:0% information and starts to become like a pretty<00:04:04.319> interesting<00:04:04.680> picture<00:04:04.860> and<00:04:05.099> we'll 00:04:05.210 --> 00:04:05.220 align:start position:0% pretty interesting picture and we'll 00:04:05.220 --> 00:04:07.190 align:start position:0% pretty interesting picture and we'll talk<00:04:05.340> more<00:04:05.459> about<00:04:05.900> what<00:04:06.900> this<00:04:07.019> this 00:04:07.190 --> 00:04:07.200 align:start position:0% talk more about what this this 00:04:07.200 --> 00:04:09.710 align:start position:0% talk more about what this this user-owned<00:04:07.799> web<00:04:07.920> looks<00:04:08.280> like<00:04:08.400> but<00:04:09.060> in<00:04:09.420> a<00:04:09.599> way 00:04:09.710 --> 00:04:09.720 align:start position:0% user-owned web looks like but in a way 00:04:09.720 --> 00:04:12.229 align:start position:0% user-owned web looks like but in a way this<00:04:10.019> is<00:04:10.200> kind<00:04:10.379> of<00:04:10.500> one<00:04:10.860> definition<00:04:11.099> of<00:04:11.580> web3 00:04:12.229 --> 00:04:12.239 align:start position:0% this is kind of one definition of web3 00:04:12.239 --> 00:04:14.390 align:start position:0% this is kind of one definition of web3 where<00:04:12.659> the<00:04:13.019> user<00:04:13.319> rather<00:04:13.680> than<00:04:13.860> necessarily 00:04:14.390 --> 00:04:14.400 align:start position:0% where the user rather than necessarily 00:04:14.400 --> 00:04:16.009 align:start position:0% where the user rather than necessarily showing<00:04:14.760> up<00:04:14.879> to<00:04:15.060> a<00:04:15.180> website<00:04:15.480> with<00:04:15.720> their<00:04:15.900> own 00:04:16.009 --> 00:04:16.019 align:start position:0% showing up to a website with their own 00:04:16.019 --> 00:04:17.750 align:start position:0% showing up to a website with their own kind<00:04:16.199> of<00:04:16.260> self-sovereign<00:04:16.919> server<00:04:17.280> they're 00:04:17.750 --> 00:04:17.760 align:start position:0% kind of self-sovereign server they're 00:04:17.760 --> 00:04:19.490 align:start position:0% kind of self-sovereign server they're arriving<00:04:18.120> with<00:04:18.419> their<00:04:18.600> own<00:04:18.720> encrypted<00:04:19.260> Shard 00:04:19.490 --> 00:04:19.500 align:start position:0% arriving with their own encrypted Shard 00:04:19.500 --> 00:04:21.710 align:start position:0% arriving with their own encrypted Shard of<00:04:19.739> the<00:04:19.859> open<00:04:19.979> web<00:04:20.280> and<00:04:20.940> then<00:04:21.120> selectively 00:04:21.710 --> 00:04:21.720 align:start position:0% of the open web and then selectively 00:04:21.720 --> 00:04:23.570 align:start position:0% of the open web and then selectively disclosing<00:04:22.380> two<00:04:22.680> various<00:04:23.100> friends<00:04:23.340> or 00:04:23.570 --> 00:04:23.580 align:start position:0% disclosing two various friends or 00:04:23.580 --> 00:04:26.210 align:start position:0% disclosing two various friends or applications<00:04:24.180> what<00:04:25.020> information<00:04:25.320> from<00:04:25.979> that 00:04:26.210 --> 00:04:26.220 align:start position:0% applications what information from that 00:04:26.220 --> 00:04:28.610 align:start position:0% applications what information from that Shard<00:04:26.520> they<00:04:26.880> can<00:04:27.000> decrypt<00:04:27.540> or<00:04:27.780> read 00:04:28.610 --> 00:04:28.620 align:start position:0% Shard they can decrypt or read 00:04:28.620 --> 00:04:30.710 align:start position:0% Shard they can decrypt or read and<00:04:28.979> so<00:04:29.100> this<00:04:29.340> product<00:04:29.699> has<00:04:29.940> been<00:04:30.180> out<00:04:30.419> since 00:04:30.710 --> 00:04:30.720 align:start position:0% and so this product has been out since 00:04:30.720 --> 00:04:32.810 align:start position:0% and so this product has been out since January<00:04:31.320> we<00:04:31.860> still<00:04:32.040> are<00:04:32.220> running<00:04:32.460> all<00:04:32.639> the 00:04:32.810 --> 00:04:32.820 align:start position:0% January we still are running all the 00:04:32.820 --> 00:04:34.010 align:start position:0% January we still are running all the nodes<00:04:33.000> centrally<00:04:33.360> and<00:04:33.600> we'll<00:04:33.720> have<00:04:33.840> those 00:04:34.010 --> 00:04:34.020 align:start position:0% nodes centrally and we'll have those 00:04:34.020 --> 00:04:36.590 align:start position:0% nodes centrally and we'll have those decentralized<00:04:34.620> by<00:04:34.740> the<00:04:34.919> end<00:04:35.040> of<00:04:35.160> the<00:04:35.340> year<00:04:35.600> and 00:04:36.590 --> 00:04:36.600 align:start position:0% decentralized by the end of the year and 00:04:36.600 --> 00:04:37.850 align:start position:0% decentralized by the end of the year and there's<00:04:36.780> hundreds<00:04:37.080> of<00:04:37.199> applications<00:04:37.620> that 00:04:37.850 --> 00:04:37.860 align:start position:0% there's hundreds of applications that 00:04:37.860 --> 00:04:40.129 align:start position:0% there's hundreds of applications that are<00:04:37.979> leveraging<00:04:38.340> this<00:04:38.580> but<00:04:39.180> just<00:04:39.479> last<00:04:39.780> week 00:04:40.129 --> 00:04:40.139 align:start position:0% are leveraging this but just last week 00:04:40.139 --> 00:04:41.749 align:start position:0% are leveraging this but just last week we<00:04:40.800> started 00:04:41.749 --> 00:04:41.759 align:start position:0% we started 00:04:41.759 --> 00:04:45.290 align:start position:0% we started um<00:04:42.240> talking<00:04:42.780> publicly<00:04:43.320> about<00:04:43.740> a<00:04:44.400> new<00:04:44.699> capacity 00:04:45.290 --> 00:04:45.300 align:start position:0% um talking publicly about a new capacity 00:04:45.300 --> 00:04:47.450 align:start position:0% um talking publicly about a new capacity which<00:04:45.780> is<00:04:45.900> the<00:04:46.080> ability<00:04:46.320> to<00:04:46.740> essentially<00:04:47.160> do 00:04:47.450 --> 00:04:47.460 align:start position:0% which is the ability to essentially do 00:04:47.460 --> 00:04:50.150 align:start position:0% which is the ability to essentially do distributed<00:04:48.360> custody<00:04:48.780> programmatic<00:04:49.620> signing 00:04:50.150 --> 00:04:50.160 align:start position:0% distributed custody programmatic signing 00:04:50.160 --> 00:04:52.550 align:start position:0% distributed custody programmatic signing and<00:04:50.940> as<00:04:51.180> you<00:04:51.300> can<00:04:51.360> see<00:04:51.479> the<00:04:51.780> architecture<00:04:52.259> is 00:04:52.550 --> 00:04:52.560 align:start position:0% and as you can see the architecture is 00:04:52.560 --> 00:04:55.370 align:start position:0% and as you can see the architecture is incredibly<00:04:53.040> similar<00:04:53.580> but<00:04:54.240> instead<00:04:54.720> of<00:04:55.080> the 00:04:55.370 --> 00:04:55.380 align:start position:0% incredibly similar but instead of the 00:04:55.380 --> 00:04:57.290 align:start position:0% incredibly similar but instead of the nodes<00:04:55.680> reading<00:04:56.160> the<00:04:56.280> blockchain<00:04:56.699> as<00:04:57.060> an 00:04:57.290 --> 00:04:57.300 align:start position:0% nodes reading the blockchain as an 00:04:57.300 --> 00:04:59.689 align:start position:0% nodes reading the blockchain as an access<00:04:57.479> control<00:04:57.960> list<00:04:58.320> they<00:04:59.040> are<00:04:59.220> reading 00:04:59.689 --> 00:04:59.699 align:start position:0% access control list they are reading 00:04:59.699 --> 00:05:02.330 align:start position:0% access control list they are reading programs<00:05:00.479> that<00:05:00.780> are<00:05:00.960> stored<00:05:01.380> at<00:05:01.800> a<00:05:02.040> specific 00:05:02.330 --> 00:05:02.340 align:start position:0% programs that are stored at a specific 00:05:02.340 --> 00:05:05.689 align:start position:0% programs that are stored at a specific CID<00:05:03.060> on<00:05:03.600> ipfs<00:05:04.259> each<00:05:04.919> of<00:05:05.100> those<00:05:05.220> nodes<00:05:05.460> is 00:05:05.689 --> 00:05:05.699 align:start position:0% CID on ipfs each of those nodes is 00:05:05.699 --> 00:05:07.610 align:start position:0% CID on ipfs each of those nodes is running<00:05:05.880> those<00:05:06.180> programs<00:05:06.720> and<00:05:07.199> now<00:05:07.320> in<00:05:07.500> this 00:05:07.610 --> 00:05:07.620 align:start position:0% running those programs and now in this 00:05:07.620 --> 00:05:09.350 align:start position:0% running those programs and now in this case<00:05:07.740> instead<00:05:08.100> of<00:05:08.220> producing<00:05:08.520> the<00:05:08.699> decryption 00:05:09.350 --> 00:05:09.360 align:start position:0% case instead of producing the decryption 00:05:09.360 --> 00:05:12.409 align:start position:0% case instead of producing the decryption share<00:05:09.720> which<00:05:10.259> lets<00:05:10.620> that<00:05:10.740> party<00:05:10.979> decrypt<00:05:11.820> some 00:05:12.409 --> 00:05:12.419 align:start position:0% share which lets that party decrypt some 00:05:12.419 --> 00:05:14.390 align:start position:0% share which lets that party decrypt some content<00:05:12.780> they're<00:05:13.259> producing<00:05:13.740> a<00:05:13.979> signature 00:05:14.390 --> 00:05:14.400 align:start position:0% content they're producing a signature 00:05:14.400 --> 00:05:16.370 align:start position:0% content they're producing a signature share<00:05:14.699> again<00:05:15.060> coming<00:05:15.540> back<00:05:15.720> to<00:05:15.840> the<00:05:15.960> idea<00:05:16.139> that 00:05:16.370 --> 00:05:16.380 align:start position:0% share again coming back to the idea that 00:05:16.380 --> 00:05:18.770 align:start position:0% share again coming back to the idea that keys<00:05:16.680> can<00:05:16.860> functionally<00:05:17.160> do<00:05:17.400> two<00:05:17.820> things<00:05:18.060> kind 00:05:18.770 --> 00:05:18.780 align:start position:0% keys can functionally do two things kind 00:05:18.780 --> 00:05:21.650 align:start position:0% keys can functionally do two things kind of<00:05:18.960> encryption<00:05:19.620> and<00:05:20.100> signing<00:05:20.580> and<00:05:21.240> then<00:05:21.360> those 00:05:21.650 --> 00:05:21.660 align:start position:0% of encryption and signing and then those 00:05:21.660 --> 00:05:24.170 align:start position:0% of encryption and signing and then those shares<00:05:22.199> can<00:05:22.380> be<00:05:22.500> aggregated<00:05:23.039> and<00:05:23.880> you<00:05:24.060> can 00:05:24.170 --> 00:05:24.180 align:start position:0% shares can be aggregated and you can 00:05:24.180 --> 00:05:25.990 align:start position:0% shares can be aggregated and you can make<00:05:24.360> a<00:05:24.539> right<00:05:24.720> to<00:05:25.139> your<00:05:25.800> favorite 00:05:25.990 --> 00:05:26.000 align:start position:0% make a right to your favorite 00:05:26.000 --> 00:05:27.830 align:start position:0% make a right to your favorite decentralized<00:05:27.000> state<00:05:27.120> machine<00:05:27.419> like 00:05:27.830 --> 00:05:27.840 align:start position:0% decentralized state machine like 00:05:27.840 --> 00:05:29.870 align:start position:0% decentralized state machine like ethereum<00:05:28.380> and<00:05:28.860> so<00:05:29.039> talking<00:05:29.280> about<00:05:29.460> some<00:05:29.759> of 00:05:29.870 --> 00:05:29.880 align:start position:0% ethereum and so talking about some of 00:05:29.880 --> 00:05:32.090 align:start position:0% ethereum and so talking about some of the<00:05:30.000> applications<00:05:30.479> for<00:05:30.840> this<00:05:31.080> there's<00:05:31.740> a<00:05:31.919> huge 00:05:32.090 --> 00:05:32.100 align:start position:0% the applications for this there's a huge 00:05:32.100 --> 00:05:34.790 align:start position:0% the applications for this there's a huge list<00:05:32.280> right<00:05:32.520> thinking<00:05:32.940> about<00:05:33.120> the<00:05:33.720> a<00:05:34.320> key<00:05:34.560> as 00:05:34.790 --> 00:05:34.800 align:start position:0% list right thinking about the a key as 00:05:34.800 --> 00:05:37.249 align:start position:0% list right thinking about the a key as an<00:05:34.979> application<00:05:35.340> development<00:05:35.880> platform<00:05:36.479> we 00:05:37.249 --> 00:05:37.259 align:start position:0% an application development platform we 00:05:37.259 --> 00:05:38.330 align:start position:0% an application development platform we kind<00:05:37.380> of<00:05:37.440> like<00:05:37.560> think<00:05:37.740> about<00:05:37.860> it<00:05:38.039> as<00:05:38.100> a 00:05:38.330 --> 00:05:38.340 align:start position:0% kind of like think about it as a 00:05:38.340 --> 00:05:40.010 align:start position:0% kind of like think about it as a paintbrush<00:05:38.759> we're<00:05:39.000> really<00:05:39.240> just<00:05:39.479> starting<00:05:39.660> to 00:05:40.010 --> 00:05:40.020 align:start position:0% paintbrush we're really just starting to 00:05:40.020 --> 00:05:41.570 align:start position:0% paintbrush we're really just starting to explore<00:05:40.380> some<00:05:40.680> of<00:05:40.800> the<00:05:41.039> application 00:05:41.570 --> 00:05:41.580 align:start position:0% explore some of the application 00:05:41.580 --> 00:05:43.610 align:start position:0% explore some of the application potential<00:05:42.000> here<00:05:42.180> but<00:05:42.960> I'll<00:05:43.080> run<00:05:43.259> through<00:05:43.440> a 00:05:43.610 --> 00:05:43.620 align:start position:0% potential here but I'll run through a 00:05:43.620 --> 00:05:44.689 align:start position:0% potential here but I'll run through a couple<00:05:43.740> right<00:05:43.979> now 00:05:44.689 --> 00:05:44.699 align:start position:0% couple right now 00:05:44.699 --> 00:05:47.210 align:start position:0% couple right now so<00:05:45.120> one<00:05:45.300> would<00:05:45.419> be<00:05:45.539> like<00:05:45.660> defy<00:05:46.139> automation<00:05:46.500> the 00:05:47.210 --> 00:05:47.220 align:start position:0% so one would be like defy automation the 00:05:47.220 --> 00:05:49.610 align:start position:0% so one would be like defy automation the state<00:05:47.400> of<00:05:47.520> the<00:05:47.699> art<00:05:47.820> for<00:05:48.300> self-custody<00:05:49.020> defy 00:05:49.610 --> 00:05:49.620 align:start position:0% state of the art for self-custody defy 00:05:49.620 --> 00:05:51.430 align:start position:0% state of the art for self-custody defy today<00:05:49.800> is<00:05:49.979> if<00:05:50.160> you<00:05:50.280> have<00:05:50.400> some<00:05:50.580> staked<00:05:51.000> tokens 00:05:51.430 --> 00:05:51.440 align:start position:0% today is if you have some staked tokens 00:05:51.440 --> 00:05:53.749 align:start position:0% today is if you have some staked tokens and<00:05:52.440> you<00:05:52.740> have<00:05:52.860> to<00:05:52.979> the<00:05:53.220> state<00:05:53.400> of<00:05:53.520> the<00:05:53.639> artist 00:05:53.749 --> 00:05:53.759 align:start position:0% and you have to the state of the artist 00:05:53.759 --> 00:05:55.370 align:start position:0% and you have to the state of the artist to<00:05:54.000> sign<00:05:54.120> up<00:05:54.240> for<00:05:54.419> some<00:05:54.539> defy<00:05:54.960> alerting 00:05:55.370 --> 00:05:55.380 align:start position:0% to sign up for some defy alerting 00:05:55.380 --> 00:05:57.170 align:start position:0% to sign up for some defy alerting Service<00:05:55.620> Such<00:05:56.220> that<00:05:56.460> when<00:05:56.639> the<00:05:56.759> price<00:05:56.880> starts 00:05:57.170 --> 00:05:57.180 align:start position:0% Service Such that when the price starts 00:05:57.180 --> 00:05:58.730 align:start position:0% Service Such that when the price starts to<00:05:57.300> drop<00:05:57.419> you<00:05:57.660> get<00:05:57.840> a<00:05:58.020> text<00:05:58.139> you<00:05:58.380> have<00:05:58.500> to<00:05:58.620> wake 00:05:58.730 --> 00:05:58.740 align:start position:0% to drop you get a text you have to wake 00:05:58.740 --> 00:06:00.050 align:start position:0% to drop you get a text you have to wake up<00:05:58.919> in<00:05:59.039> the<00:05:59.160> middle<00:05:59.280> of<00:05:59.340> the<00:05:59.460> night<00:05:59.580> and<00:05:59.759> push<00:05:59.880> a 00:06:00.050 --> 00:06:00.060 align:start position:0% up in the middle of the night and push a 00:06:00.060 --> 00:06:02.090 align:start position:0% up in the middle of the night and push a button<00:06:00.300> on<00:06:00.419> your<00:06:00.539> Ledger<00:06:00.900> but<00:06:01.800> in<00:06:01.919> a<00:06:02.039> world 00:06:02.090 --> 00:06:02.100 align:start position:0% button on your Ledger but in a world 00:06:02.100 --> 00:06:03.590 align:start position:0% button on your Ledger but in a world where<00:06:02.280> you've<00:06:02.520> staked<00:06:02.880> those<00:06:03.000> tokens<00:06:03.360> from 00:06:03.590 --> 00:06:03.600 align:start position:0% where you've staked those tokens from 00:06:03.600 --> 00:06:05.270 align:start position:0% where you've staked those tokens from one<00:06:03.720> of<00:06:03.840> these<00:06:04.020> Cloud<00:06:04.320> wallets<00:06:04.800> as<00:06:05.039> we<00:06:05.220> can 00:06:05.270 --> 00:06:05.280 align:start position:0% one of these Cloud wallets as we can 00:06:05.280 --> 00:06:08.210 align:start position:0% one of these Cloud wallets as we can kind<00:06:05.460> of<00:06:05.520> call<00:06:05.759> them<00:06:06.380> you<00:06:07.380> could<00:06:07.500> have<00:06:07.740> that 00:06:08.210 --> 00:06:08.220 align:start position:0% kind of call them you could have that 00:06:08.220 --> 00:06:10.490 align:start position:0% kind of call them you could have that program<00:06:08.460> listening<00:06:09.240> to<00:06:09.479> a<00:06:09.660> feed<00:06:09.840> and<00:06:10.259> when<00:06:10.380> the 00:06:10.490 --> 00:06:10.500 align:start position:0% program listening to a feed and when the 00:06:10.500 --> 00:06:12.770 align:start position:0% program listening to a feed and when the price<00:06:10.680> drops<00:06:11.160> have<00:06:11.699> a<00:06:11.940> program<00:06:12.060> that<00:06:12.479> kicks 00:06:12.770 --> 00:06:12.780 align:start position:0% price drops have a program that kicks 00:06:12.780 --> 00:06:14.930 align:start position:0% price drops have a program that kicks off<00:06:12.840> that<00:06:13.139> unstakes<00:06:13.620> the<00:06:13.800> tokens<00:06:14.160> sells<00:06:14.880> them 00:06:14.930 --> 00:06:14.940 align:start position:0% off that unstakes the tokens sells them 00:06:14.940 --> 00:06:17.510 align:start position:0% off that unstakes the tokens sells them for<00:06:15.120> usdc<00:06:15.660> on<00:06:15.900> a<00:06:16.020> decks<00:06:16.380> and<00:06:16.919> sends<00:06:17.280> them<00:06:17.340> to 00:06:17.510 --> 00:06:17.520 align:start position:0% for usdc on a decks and sends them to 00:06:17.520 --> 00:06:19.010 align:start position:0% for usdc on a decks and sends them to your<00:06:17.639> Ledger<00:06:18.000> and<00:06:18.419> this<00:06:18.539> is<00:06:18.600> all<00:06:18.780> happening 00:06:19.010 --> 00:06:19.020 align:start position:0% your Ledger and this is all happening 00:06:19.020 --> 00:06:20.749 align:start position:0% your Ledger and this is all happening kind<00:06:19.259> of<00:06:19.320> without<00:06:19.500> a<00:06:19.860> human<00:06:19.979> signer<00:06:20.520> in<00:06:20.639> the 00:06:20.749 --> 00:06:20.759 align:start position:0% kind of without a human signer in the 00:06:20.759 --> 00:06:23.150 align:start position:0% kind of without a human signer in the loop<00:06:21.000> because<00:06:21.720> the<00:06:22.080> key<00:06:22.259> is<00:06:22.440> custody<00:06:22.740> in<00:06:22.979> this 00:06:23.150 --> 00:06:23.160 align:start position:0% loop because the key is custody in this 00:06:23.160 --> 00:06:25.490 align:start position:0% loop because the key is custody in this distributed<00:06:23.639> context<00:06:24.240> at<00:06:24.960> the<00:06:25.020> network<00:06:25.199> level 00:06:25.490 --> 00:06:25.500 align:start position:0% distributed context at the network level 00:06:25.500 --> 00:06:27.409 align:start position:0% distributed context at the network level Chris<00:06:26.280> will<00:06:26.520> talk<00:06:26.699> a<00:06:26.819> little<00:06:26.940> bit<00:06:27.060> more<00:06:27.240> about 00:06:27.409 --> 00:06:27.419 align:start position:0% Chris will talk a little bit more about 00:06:27.419 --> 00:06:29.270 align:start position:0% Chris will talk a little bit more about vaults<00:06:28.080> but<00:06:28.440> in<00:06:28.560> a<00:06:28.680> way<00:06:28.800> what<00:06:29.039> we're<00:06:29.100> talking 00:06:29.270 --> 00:06:29.280 align:start position:0% vaults but in a way what we're talking 00:06:29.280 --> 00:06:31.790 align:start position:0% vaults but in a way what we're talking about<00:06:29.460> here<00:06:29.759> is<00:06:29.940> making<00:06:30.240> private<00:06:30.900> Keys<00:06:31.380> liquid 00:06:31.790 --> 00:06:31.800 align:start position:0% about here is making private Keys liquid 00:06:31.800 --> 00:06:34.249 align:start position:0% about here is making private Keys liquid so<00:06:32.340> you<00:06:32.520> could<00:06:32.639> send<00:06:33.120> a<00:06:33.300> bunch<00:06:33.419> of<00:06:33.539> nfts<00:06:34.139> and 00:06:34.249 --> 00:06:34.259 align:start position:0% so you could send a bunch of nfts and 00:06:34.259 --> 00:06:37.010 align:start position:0% so you could send a bunch of nfts and tokens<00:06:34.620> to<00:06:34.919> a<00:06:35.039> given<00:06:35.280> address<00:06:35.460> and<00:06:36.419> then<00:06:36.600> trade 00:06:37.010 --> 00:06:37.020 align:start position:0% tokens to a given address and then trade 00:06:37.020 --> 00:06:39.490 align:start position:0% tokens to a given address and then trade the<00:06:37.259> underlying<00:06:37.800> ownership<00:06:38.220> of<00:06:38.699> that<00:06:38.940> address 00:06:39.490 --> 00:06:39.500 align:start position:0% the underlying ownership of that address 00:06:39.500 --> 00:06:42.290 align:start position:0% the underlying ownership of that address there's<00:06:40.500> also<00:06:40.800> a<00:06:40.979> lot<00:06:41.100> to<00:06:41.280> explore<00:06:41.639> here<00:06:41.940> as<00:06:42.120> it 00:06:42.290 --> 00:06:42.300 align:start position:0% there's also a lot to explore here as it 00:06:42.300 --> 00:06:44.330 align:start position:0% there's also a lot to explore here as it relates<00:06:42.539> to<00:06:42.720> account<00:06:43.020> abstraction<00:06:43.740> doing 00:06:44.330 --> 00:06:44.340 align:start position:0% relates to account abstraction doing 00:06:44.340 --> 00:06:47.629 align:start position:0% relates to account abstraction doing things<00:06:44.520> like<00:06:44.639> cooking<00:06:45.360> up<00:06:45.539> a<00:06:46.160> biometric<00:06:47.160> auth 00:06:47.629 --> 00:06:47.639 align:start position:0% things like cooking up a biometric auth 00:06:47.639 --> 00:06:50.330 align:start position:0% things like cooking up a biometric auth like<00:06:47.940> apple<00:06:48.360> Pass<00:06:48.780> key<00:06:49.080> as<00:06:49.500> the<00:06:49.680> auth<00:06:49.919> method 00:06:50.330 --> 00:06:50.340 align:start position:0% like apple Pass key as the auth method 00:06:50.340 --> 00:06:53.090 align:start position:0% like apple Pass key as the auth method into<00:06:50.580> one<00:06:50.880> of<00:06:51.000> these<00:06:51.240> Cloud<00:06:51.660> keys<00:06:52.259> in<00:06:52.979> this 00:06:53.090 --> 00:06:53.100 align:start position:0% into one of these Cloud keys in this 00:06:53.100 --> 00:06:54.290 align:start position:0% into one of these Cloud keys in this whole<00:06:53.220> context<00:06:53.520> of<00:06:53.699> how<00:06:53.819> do<00:06:53.880> we<00:06:54.000> bring<00:06:54.120> the 00:06:54.290 --> 00:06:54.300 align:start position:0% whole context of how do we bring the 00:06:54.300 --> 00:06:56.210 align:start position:0% whole context of how do we bring the next<00:06:54.419> billion<00:06:54.840> users<00:06:55.199> into<00:06:55.440> this<00:06:55.680> ecosystem 00:06:56.210 --> 00:06:56.220 align:start position:0% next billion users into this ecosystem 00:06:56.220 --> 00:06:58.309 align:start position:0% next billion users into this ecosystem and<00:06:57.120> Abstract<00:06:57.419> away<00:06:57.600> the<00:06:57.900> complexity 00:06:58.309 --> 00:06:58.319 align:start position:0% and Abstract away the complexity 00:06:58.319 --> 00:07:00.050 align:start position:0% and Abstract away the complexity associated<00:06:58.800> with<00:06:59.039> the<00:06:59.220> seed<00:06:59.400> phrase<00:06:59.699> this<00:06:59.940> is 00:07:00.050 --> 00:07:00.060 align:start position:0% associated with the seed phrase this is 00:07:00.060 --> 00:07:01.969 align:start position:0% associated with the seed phrase this is really<00:07:00.240> exciting<00:07:00.720> and<00:07:01.319> certainly<00:07:01.560> a<00:07:01.680> lot<00:07:01.800> to 00:07:01.969 --> 00:07:01.979 align:start position:0% really exciting and certainly a lot to 00:07:01.979 --> 00:07:04.249 align:start position:0% really exciting and certainly a lot to explore<00:07:02.220> in<00:07:02.460> the<00:07:02.699> context<00:07:02.940> of<00:07:03.479> cross-chain 00:07:04.249 --> 00:07:04.259 align:start position:0% explore in the context of cross-chain 00:07:04.259 --> 00:07:07.249 align:start position:0% explore in the context of cross-chain messaging<00:07:04.860> and<00:07:05.460> bridging<00:07:05.880> as<00:07:06.060> well 00:07:07.249 --> 00:07:07.259 align:start position:0% messaging and bridging as well 00:07:07.259 --> 00:07:08.930 align:start position:0% messaging and bridging as well and<00:07:07.500> so<00:07:07.680> with<00:07:07.800> that<00:07:07.919> I'll<00:07:08.160> pass<00:07:08.400> this<00:07:08.580> clicker 00:07:08.930 --> 00:07:08.940 align:start position:0% and so with that I'll pass this clicker 00:07:08.940 --> 00:07:10.670 align:start position:0% and so with that I'll pass this clicker off<00:07:09.120> to<00:07:09.300> Chris 00:07:10.670 --> 00:07:10.680 align:start position:0% off to Chris 00:07:10.680 --> 00:07:12.170 align:start position:0% off to Chris thank<00:07:11.160> you<00:07:11.280> David 00:07:12.170 --> 00:07:12.180 align:start position:0% thank you David 00:07:12.180 --> 00:07:14.870 align:start position:0% thank you David uh<00:07:12.840> yeah<00:07:13.020> so<00:07:13.440> I'd<00:07:13.979> like<00:07:14.160> to<00:07:14.280> introduce<00:07:14.639> the 00:07:14.870 --> 00:07:14.880 align:start position:0% uh yeah so I'd like to introduce the 00:07:14.880 --> 00:07:17.150 align:start position:0% uh yeah so I'd like to introduce the idea<00:07:15.240> of<00:07:15.660> a<00:07:15.960> decentralized<00:07:16.500> programmable<00:07:16.919> key 00:07:17.150 --> 00:07:17.160 align:start position:0% idea of a decentralized programmable key 00:07:17.160 --> 00:07:20.029 align:start position:0% idea of a decentralized programmable key pair<00:07:17.819> which<00:07:18.419> we<00:07:18.600> call<00:07:18.720> pkps 00:07:20.029 --> 00:07:20.039 align:start position:0% pair which we call pkps 00:07:20.039 --> 00:07:23.749 align:start position:0% pair which we call pkps a<00:07:20.639> pkp<00:07:21.240> is<00:07:21.539> an<00:07:21.720> ecdsa<00:07:22.380> key<00:07:22.620> pair<00:07:22.800> that's<00:07:23.400> held 00:07:23.749 --> 00:07:23.759 align:start position:0% a pkp is an ecdsa key pair that's held 00:07:23.759 --> 00:07:25.570 align:start position:0% a pkp is an ecdsa key pair that's held as<00:07:23.880> private<00:07:24.240> key<00:07:24.360> shares 00:07:25.570 --> 00:07:25.580 align:start position:0% as private key shares 00:07:25.580 --> 00:07:28.969 align:start position:0% as private key shares custody<00:07:26.580> by<00:07:27.060> the<00:07:27.360> lit<00:07:27.660> nodes<00:07:27.960> you<00:07:28.740> can<00:07:28.800> create 00:07:28.969 --> 00:07:28.979 align:start position:0% custody by the lit nodes you can create 00:07:28.979 --> 00:07:32.629 align:start position:0% custody by the lit nodes you can create a<00:07:29.280> pkp<00:07:29.759> by<00:07:30.419> minting<00:07:30.840> an<00:07:30.960> nft<00:07:31.259> that<00:07:32.160> represents 00:07:32.629 --> 00:07:32.639 align:start position:0% a pkp by minting an nft that represents 00:07:32.639 --> 00:07:35.870 align:start position:0% a pkp by minting an nft that represents ownership<00:07:33.060> over<00:07:33.599> that<00:07:33.840> pkp<00:07:34.500> and<00:07:35.280> so<00:07:35.460> whoever 00:07:35.870 --> 00:07:35.880 align:start position:0% ownership over that pkp and so whoever 00:07:35.880 --> 00:07:39.170 align:start position:0% ownership over that pkp and so whoever owns<00:07:36.300> that<00:07:36.479> nft<00:07:36.780> can<00:07:37.620> ask<00:07:37.800> the<00:07:38.039> pkp<00:07:38.580> to<00:07:39.060> sign 00:07:39.170 --> 00:07:39.180 align:start position:0% owns that nft can ask the pkp to sign 00:07:39.180 --> 00:07:41.390 align:start position:0% owns that nft can ask the pkp to sign anything<00:07:39.479> on<00:07:39.900> their<00:07:40.020> behalf<00:07:40.440> including 00:07:41.390 --> 00:07:41.400 align:start position:0% anything on their behalf including 00:07:41.400 --> 00:07:44.150 align:start position:0% anything on their behalf including ethereum<00:07:42.000> or<00:07:42.300> even<00:07:42.419> Bitcoin<00:07:43.020> transactions 00:07:44.150 --> 00:07:44.160 align:start position:0% ethereum or even Bitcoin transactions 00:07:44.160 --> 00:07:45.650 align:start position:0% ethereum or even Bitcoin transactions you<00:07:44.639> can<00:07:44.699> do<00:07:44.880> this<00:07:45.000> by<00:07:45.240> writing<00:07:45.539> some 00:07:45.650 --> 00:07:45.660 align:start position:0% you can do this by writing some 00:07:45.660 --> 00:07:48.290 align:start position:0% you can do this by writing some JavaScript<00:07:46.080> code<00:07:46.380> that<00:07:47.160> we<00:07:47.340> call<00:07:47.580> a<00:07:48.000> lit 00:07:48.290 --> 00:07:48.300 align:start position:0% JavaScript code that we call a lit 00:07:48.300 --> 00:07:49.790 align:start position:0% JavaScript code that we call a lit action 00:07:49.790 --> 00:07:49.800 align:start position:0% action 00:07:49.800 --> 00:07:52.969 align:start position:0% action so<00:07:50.280> this<00:07:50.520> is<00:07:50.699> a<00:07:51.000> really<00:07:51.120> basic<00:07:51.539> hello<00:07:51.780> world<00:07:52.139> uh 00:07:52.969 --> 00:07:52.979 align:start position:0% so this is a really basic hello world uh 00:07:52.979 --> 00:07:56.089 align:start position:0% so this is a really basic hello world uh lit<00:07:53.280> action<00:07:53.520> it<00:07:54.479> literally<00:07:54.780> signs<00:07:55.380> the<00:07:55.680> string 00:07:56.089 --> 00:07:56.099 align:start position:0% lit action it literally signs the string 00:07:56.099 --> 00:07:59.150 align:start position:0% lit action it literally signs the string hello<00:07:56.460> world<00:07:56.819> uh<00:07:57.660> with<00:07:57.840> ecdsa 00:07:59.150 --> 00:07:59.160 align:start position:0% hello world uh with ecdsa 00:07:59.160 --> 00:08:00.830 align:start position:0% hello world uh with ecdsa and<00:07:59.520> what<00:07:59.639> happens<00:07:59.759> is<00:08:00.000> this<00:08:00.240> code<00:08:00.419> will<00:08:00.660> be 00:08:00.830 --> 00:08:00.840 align:start position:0% and what happens is this code will be 00:08:00.840 --> 00:08:04.129 align:start position:0% and what happens is this code will be run<00:08:01.020> on<00:08:01.620> all<00:08:01.800> the<00:08:01.919> lit<00:08:02.160> nodes<00:08:02.460> in<00:08:03.120> parallel 00:08:04.129 --> 00:08:04.139 align:start position:0% run on all the lit nodes in parallel 00:08:04.139 --> 00:08:07.610 align:start position:0% run on all the lit nodes in parallel lit<00:08:04.680> actions<00:08:05.220> live<00:08:05.819> on<00:08:06.120> itfs<00:08:06.840> and<00:08:07.500> are 00:08:07.610 --> 00:08:07.620 align:start position:0% lit actions live on itfs and are 00:08:07.620 --> 00:08:10.969 align:start position:0% lit actions live on itfs and are immutable<00:08:08.160> just<00:08:08.699> like<00:08:08.880> smart<00:08:09.120> contracts<00:08:09.979> and 00:08:10.969 --> 00:08:10.979 align:start position:0% immutable just like smart contracts and 00:08:10.979 --> 00:08:13.850 align:start position:0% immutable just like smart contracts and I<00:08:11.639> just<00:08:11.759> explained<00:08:12.300> that<00:08:13.080> whoever<00:08:13.440> owns<00:08:13.740> the 00:08:13.850 --> 00:08:13.860 align:start position:0% I just explained that whoever owns the 00:08:13.860 --> 00:08:16.850 align:start position:0% I just explained that whoever owns the pkp<00:08:14.460> nft<00:08:14.940> can<00:08:15.720> request<00:08:15.960> a<00:08:16.139> signature<00:08:16.560> using 00:08:16.850 --> 00:08:16.860 align:start position:0% pkp nft can request a signature using 00:08:16.860 --> 00:08:19.189 align:start position:0% pkp nft can request a signature using the<00:08:16.979> pkp<00:08:17.520> but<00:08:18.419> what's<00:08:18.660> actually<00:08:18.900> more 00:08:19.189 --> 00:08:19.199 align:start position:0% the pkp but what's actually more 00:08:19.199 --> 00:08:21.350 align:start position:0% the pkp but what's actually more interesting<00:08:19.620> is<00:08:20.460> that<00:08:20.580> you<00:08:20.759> can<00:08:20.819> also<00:08:21.060> Grant 00:08:21.350 --> 00:08:21.360 align:start position:0% interesting is that you can also Grant 00:08:21.360 --> 00:08:24.589 align:start position:0% interesting is that you can also Grant the<00:08:21.479> ability<00:08:21.780> to<00:08:22.139> sign<00:08:22.319> using<00:08:22.800> your<00:08:22.919> pkp<00:08:23.460> to<00:08:24.360> a 00:08:24.589 --> 00:08:24.599 align:start position:0% the ability to sign using your pkp to a 00:08:24.599 --> 00:08:25.790 align:start position:0% the ability to sign using your pkp to a lit<00:08:24.900> action 00:08:25.790 --> 00:08:25.800 align:start position:0% lit action 00:08:25.800 --> 00:08:28.070 align:start position:0% lit action this<00:08:26.400> is<00:08:26.520> very<00:08:26.759> similar<00:08:27.120> to<00:08:27.479> the<00:08:27.720> Token 00:08:28.070 --> 00:08:28.080 align:start position:0% this is very similar to the Token 00:08:28.080 --> 00:08:30.170 align:start position:0% this is very similar to the Token approval<00:08:28.560> pattern<00:08:29.099> that<00:08:29.340> we<00:08:29.460> use<00:08:29.520> on<00:08:29.699> ethereum 00:08:30.170 --> 00:08:30.180 align:start position:0% approval pattern that we use on ethereum 00:08:30.180 --> 00:08:33.230 align:start position:0% approval pattern that we use on ethereum where<00:08:30.960> you<00:08:31.080> can<00:08:31.199> grant<00:08:31.560> a<00:08:31.740> smart<00:08:31.979> contract<00:08:32.459> the 00:08:33.230 --> 00:08:33.240 align:start position:0% where you can grant a smart contract the 00:08:33.240 --> 00:08:35.510 align:start position:0% where you can grant a smart contract the ability<00:08:33.539> to<00:08:33.839> transfer<00:08:34.140> your<00:08:34.380> tokens<00:08:34.680> but 00:08:35.510 --> 00:08:35.520 align:start position:0% ability to transfer your tokens but 00:08:35.520 --> 00:08:37.190 align:start position:0% ability to transfer your tokens but instead<00:08:35.760> of<00:08:35.880> granting<00:08:36.240> the<00:08:36.360> ability<00:08:36.659> to 00:08:37.190 --> 00:08:37.200 align:start position:0% instead of granting the ability to 00:08:37.200 --> 00:08:38.870 align:start position:0% instead of granting the ability to transfer<00:08:37.560> tokens<00:08:37.979> you're<00:08:38.399> granting<00:08:38.760> the 00:08:38.870 --> 00:08:38.880 align:start position:0% transfer tokens you're granting the 00:08:38.880 --> 00:08:41.329 align:start position:0% transfer tokens you're granting the ability<00:08:39.120> to<00:08:39.539> sign<00:08:39.719> anything<00:08:40.080> with<00:08:41.039> this 00:08:41.329 --> 00:08:41.339 align:start position:0% ability to sign anything with this 00:08:41.339 --> 00:08:43.190 align:start position:0% ability to sign anything with this programmable<00:08:41.820> key<00:08:42.000> pair 00:08:43.190 --> 00:08:43.200 align:start position:0% programmable key pair 00:08:43.200 --> 00:08:45.769 align:start position:0% programmable key pair so<00:08:43.500> here's<00:08:43.800> how<00:08:44.039> it<00:08:44.399> actually<00:08:44.520> works 00:08:45.769 --> 00:08:45.779 align:start position:0% so here's how it actually works 00:08:45.779 --> 00:08:48.170 align:start position:0% so here's how it actually works the<00:08:46.620> user<00:08:46.920> can<00:08:47.100> create<00:08:47.339> a<00:08:47.700> lit<00:08:47.940> action 00:08:48.170 --> 00:08:48.180 align:start position:0% the user can create a lit action 00:08:48.180 --> 00:08:50.570 align:start position:0% the user can create a lit action execution<00:08:48.779> request<00:08:49.200> which<00:08:49.860> you<00:08:49.980> can<00:08:50.100> see<00:08:50.220> at 00:08:50.570 --> 00:08:50.580 align:start position:0% execution request which you can see at 00:08:50.580 --> 00:08:54.430 align:start position:0% execution request which you can see at the<00:08:50.700> top<00:08:50.820> there 00:08:54.430 --> 00:08:54.440 align:start position:0% 00:08:54.440 --> 00:08:57.310 align:start position:0% to<00:08:55.440> add<00:08:55.620> a<00:08:55.740> laser<00:08:55.980> cool 00:08:57.310 --> 00:08:57.320 align:start position:0% to add a laser cool 00:08:57.320 --> 00:09:01.970 align:start position:0% to add a laser cool and<00:08:58.320> they<00:08:59.279> pass<00:08:59.580> in<00:08:59.820> an<00:09:00.120> itfs<00:09:00.720> CID<00:09:01.260> which<00:09:01.860> is 00:09:01.970 --> 00:09:01.980 align:start position:0% and they pass in an itfs CID which is 00:09:01.980 --> 00:09:04.430 align:start position:0% and they pass in an itfs CID which is some<00:09:02.399> JavaScript<00:09:02.820> code<00:09:03.060> and<00:09:03.720> a<00:09:03.899> cryptographic 00:09:04.430 --> 00:09:04.440 align:start position:0% some JavaScript code and a cryptographic 00:09:04.440 --> 00:09:05.810 align:start position:0% some JavaScript code and a cryptographic signature<00:09:04.860> that<00:09:05.160> could<00:09:05.279> come<00:09:05.459> from<00:09:05.640> their 00:09:05.810 --> 00:09:05.820 align:start position:0% signature that could come from their 00:09:05.820 --> 00:09:09.290 align:start position:0% signature that could come from their ethereum<00:09:06.300> wallet<00:09:06.720> and<00:09:07.260> apple<00:09:07.440> Pass<00:09:07.800> key<00:09:08.300> or 00:09:09.290 --> 00:09:09.300 align:start position:0% ethereum wallet and apple Pass key or 00:09:09.300 --> 00:09:11.810 align:start position:0% ethereum wallet and apple Pass key or any<00:09:09.480> public<00:09:09.720> key<00:09:09.959> cryptography<00:09:10.620> scheme 00:09:11.810 --> 00:09:11.820 align:start position:0% any public key cryptography scheme 00:09:11.820 --> 00:09:14.930 align:start position:0% any public key cryptography scheme they<00:09:12.660> send<00:09:13.080> that<00:09:13.500> execution<00:09:13.800> request<00:09:14.220> to<00:09:14.700> all 00:09:14.930 --> 00:09:14.940 align:start position:0% they send that execution request to all 00:09:14.940 --> 00:09:17.150 align:start position:0% they send that execution request to all of<00:09:15.000> the<00:09:15.180> lit<00:09:15.420> nodes<00:09:15.720> in<00:09:16.080> parallel 00:09:17.150 --> 00:09:17.160 align:start position:0% of the lit nodes in parallel 00:09:17.160 --> 00:09:20.150 align:start position:0% of the lit nodes in parallel the<00:09:17.820> lit<00:09:18.180> nodes<00:09:18.480> use<00:09:19.140> a<00:09:19.320> JavaScript<00:09:19.680> runtime 00:09:20.150 --> 00:09:20.160 align:start position:0% the lit nodes use a JavaScript runtime 00:09:20.160 --> 00:09:24.050 align:start position:0% the lit nodes use a JavaScript runtime to<00:09:20.760> execute<00:09:21.120> the<00:09:21.240> lit<00:09:21.540> action<00:09:21.779> from<00:09:22.620> ipfs 00:09:24.050 --> 00:09:24.060 align:start position:0% to execute the lit action from ipfs 00:09:24.060 --> 00:09:28.370 align:start position:0% to execute the lit action from ipfs they<00:09:24.899> check<00:09:25.560> the<00:09:26.160> pkp<00:09:26.700> authentication<00:09:27.540> by 00:09:28.370 --> 00:09:28.380 align:start position:0% they check the pkp authentication by 00:09:28.380 --> 00:09:32.750 align:start position:0% they check the pkp authentication by talking<00:09:28.620> to<00:09:29.300> a<00:09:30.300> blockchain<00:09:31.200> where<00:09:31.980> the<00:09:32.220> pkp 00:09:32.750 --> 00:09:32.760 align:start position:0% talking to a blockchain where the pkp 00:09:32.760 --> 00:09:34.389 align:start position:0% talking to a blockchain where the pkp nft<00:09:33.060> lives 00:09:34.389 --> 00:09:34.399 align:start position:0% nft lives 00:09:34.399 --> 00:09:38.389 align:start position:0% nft lives and<00:09:35.399> the<00:09:35.820> lit<00:09:36.060> action<00:09:36.300> can<00:09:36.720> also<00:09:37.399> make 00:09:38.389 --> 00:09:38.399 align:start position:0% and the lit action can also make 00:09:38.399 --> 00:09:41.630 align:start position:0% and the lit action can also make arbitrary<00:09:39.000> HTTP<00:09:39.600> requests<00:09:40.080> so<00:09:40.860> it<00:09:41.279> can<00:09:41.459> also 00:09:41.630 --> 00:09:41.640 align:start position:0% arbitrary HTTP requests so it can also 00:09:41.640 --> 00:09:44.509 align:start position:0% arbitrary HTTP requests so it can also act<00:09:41.880> as<00:09:42.180> a<00:09:42.360> kind<00:09:42.480> of<00:09:42.600> Oracle 00:09:44.509 --> 00:09:44.519 align:start position:0% act as a kind of Oracle 00:09:44.519 --> 00:09:47.810 align:start position:0% act as a kind of Oracle um it<00:09:44.760> can<00:09:44.880> also<00:09:45.120> act<00:09:45.300> as<00:09:45.600> a<00:09:45.839> kind<00:09:46.019> of<00:09:46.140> Oracle 00:09:47.810 --> 00:09:47.820 align:start position:0% um it can also act as a kind of Oracle 00:09:47.820 --> 00:09:50.269 align:start position:0% um it can also act as a kind of Oracle um<00:09:47.940> so<00:09:48.240> you<00:09:48.420> can<00:09:48.600> pull<00:09:48.720> any<00:09:48.959> data<00:09:49.320> in<00:09:49.500> and<00:09:49.980> use 00:09:50.269 --> 00:09:50.279 align:start position:0% um so you can pull any data in and use 00:09:50.279 --> 00:09:53.590 align:start position:0% um so you can pull any data in and use it<00:09:50.459> in<00:09:50.760> your<00:09:50.940> JavaScript<00:09:51.480> lit<00:09:51.899> action 00:09:53.590 --> 00:09:53.600 align:start position:0% it in your JavaScript lit action 00:09:53.600 --> 00:09:56.630 align:start position:0% it in your JavaScript lit action the<00:09:54.600> lit<00:09:55.140> action<00:09:55.380> can<00:09:55.620> request<00:09:55.980> a<00:09:56.160> signature 00:09:56.630 --> 00:09:56.640 align:start position:0% the lit action can request a signature 00:09:56.640 --> 00:09:58.670 align:start position:0% the lit action can request a signature using<00:09:57.240> the<00:09:57.420> threshold<00:09:57.779> private<00:09:58.200> key<00:09:58.320> share 00:09:58.670 --> 00:09:58.680 align:start position:0% using the threshold private key share 00:09:58.680 --> 00:10:01.370 align:start position:0% using the threshold private key share that<00:09:59.459> creates<00:09:59.820> a<00:10:00.060> signature<00:10:00.540> share 00:10:01.370 --> 00:10:01.380 align:start position:0% that creates a signature share 00:10:01.380 --> 00:10:05.090 align:start position:0% that creates a signature share that<00:10:01.860> gets<00:10:02.160> sent<00:10:02.959> down<00:10:03.959> to<00:10:04.320> the<00:10:04.680> user<00:10:04.920> that 00:10:05.090 --> 00:10:05.100 align:start position:0% that gets sent down to the user that 00:10:05.100 --> 00:10:06.949 align:start position:0% that gets sent down to the user that initiated<00:10:05.519> the<00:10:05.760> request<00:10:06.060> they<00:10:06.660> could<00:10:06.839> be 00:10:06.949 --> 00:10:06.959 align:start position:0% initiated the request they could be 00:10:06.959 --> 00:10:08.870 align:start position:0% initiated the request they could be using<00:10:07.380> a<00:10:07.500> browser<00:10:07.860> or<00:10:08.100> this<00:10:08.220> could<00:10:08.399> be<00:10:08.519> like<00:10:08.700> a 00:10:08.870 --> 00:10:08.880 align:start position:0% using a browser or this could be like a 00:10:08.880 --> 00:10:10.690 align:start position:0% using a browser or this could be like a server-side<00:10:09.180> client 00:10:10.690 --> 00:10:10.700 align:start position:0% server-side client 00:10:10.700 --> 00:10:14.090 align:start position:0% server-side client they<00:10:11.700> combine<00:10:12.000> those<00:10:12.240> signature<00:10:12.720> shares<00:10:13.100> and 00:10:14.090 --> 00:10:14.100 align:start position:0% they combine those signature shares and 00:10:14.100 --> 00:10:16.490 align:start position:0% they combine those signature shares and they<00:10:14.580> broadcast<00:10:14.839> that<00:10:15.839> signed<00:10:16.200> transaction 00:10:16.490 --> 00:10:16.500 align:start position:0% they broadcast that signed transaction 00:10:16.500 --> 00:10:19.610 align:start position:0% they broadcast that signed transaction to<00:10:16.800> ethereum<00:10:17.279> or<00:10:17.459> any<00:10:17.580> ecdsa<00:10:18.300> blockchain<00:10:18.720> and 00:10:19.610 --> 00:10:19.620 align:start position:0% to ethereum or any ecdsa blockchain and 00:10:19.620 --> 00:10:21.290 align:start position:0% to ethereum or any ecdsa blockchain and I'm<00:10:19.800> talking<00:10:19.980> about<00:10:20.100> a<00:10:20.339> transaction<00:10:20.700> here<00:10:21.000> but 00:10:21.290 --> 00:10:21.300 align:start position:0% I'm talking about a transaction here but 00:10:21.300 --> 00:10:23.090 align:start position:0% I'm talking about a transaction here but it<00:10:22.019> doesn't<00:10:22.140> actually<00:10:22.380> have<00:10:22.680> to<00:10:22.800> be<00:10:22.920> a 00:10:23.090 --> 00:10:23.100 align:start position:0% it doesn't actually have to be a 00:10:23.100 --> 00:10:26.389 align:start position:0% it doesn't actually have to be a transaction<00:10:23.519> it<00:10:24.180> could<00:10:24.300> be<00:10:24.480> any<00:10:25.200> signed<00:10:25.980> data 00:10:26.389 --> 00:10:26.399 align:start position:0% transaction it could be any signed data 00:10:26.399 --> 00:10:30.050 align:start position:0% transaction it could be any signed data like<00:10:27.300> a<00:10:27.480> right<00:10:27.660> on<00:10:28.260> a<00:10:28.560> ceramic<00:10:29.100> or<00:10:29.820> anything 00:10:30.050 --> 00:10:30.060 align:start position:0% like a right on a ceramic or anything 00:10:30.060 --> 00:10:31.790 align:start position:0% like a right on a ceramic or anything else<00:10:30.420> like<00:10:30.899> that 00:10:31.790 --> 00:10:31.800 align:start position:0% else like that 00:10:31.800 --> 00:10:34.310 align:start position:0% else like that an<00:10:32.399> interesting<00:10:32.820> pattern<00:10:33.240> that<00:10:33.540> Lit<00:10:33.839> supports 00:10:34.310 --> 00:10:34.320 align:start position:0% an interesting pattern that Lit supports 00:10:34.320 --> 00:10:36.829 align:start position:0% an interesting pattern that Lit supports is<00:10:34.620> called<00:10:34.860> mint<00:10:35.279> Grant<00:10:35.820> burn 00:10:36.829 --> 00:10:36.839 align:start position:0% is called mint Grant burn 00:10:36.839 --> 00:10:38.210 align:start position:0% is called mint Grant burn the<00:10:37.320> idea 00:10:38.210 --> 00:10:38.220 align:start position:0% the idea 00:10:38.220 --> 00:10:42.650 align:start position:0% the idea is<00:10:39.000> that<00:10:39.660> you<00:10:39.959> mint<00:10:40.440> a<00:10:40.680> pkp<00:10:41.300> grant<00:10:42.300> it<00:10:42.420> the 00:10:42.650 --> 00:10:42.660 align:start position:0% is that you mint a pkp grant it the 00:10:42.660 --> 00:10:45.290 align:start position:0% is that you mint a pkp grant it the ability<00:10:42.899> to<00:10:43.260> use<00:10:43.380> a<00:10:43.560> lit<00:10:43.800> action<00:10:44.040> then<00:10:44.940> burn 00:10:45.290 --> 00:10:45.300 align:start position:0% ability to use a lit action then burn 00:10:45.300 --> 00:10:48.650 align:start position:0% ability to use a lit action then burn the<00:10:45.480> pkp<00:10:46.019> in<00:10:46.380> a<00:10:46.560> single<00:10:46.800> Atomic<00:10:47.279> transaction 00:10:48.650 --> 00:10:48.660 align:start position:0% the pkp in a single Atomic transaction 00:10:48.660 --> 00:10:51.170 align:start position:0% the pkp in a single Atomic transaction this<00:10:49.079> means<00:10:49.320> that<00:10:49.560> the<00:10:49.680> pkp<00:10:50.160> can<00:10:50.519> only<00:10:50.700> ever<00:10:50.940> be 00:10:51.170 --> 00:10:51.180 align:start position:0% this means that the pkp can only ever be 00:10:51.180 --> 00:10:53.630 align:start position:0% this means that the pkp can only ever be used<00:10:51.420> by<00:10:51.779> that<00:10:51.959> Lit<00:10:52.260> action<00:10:52.560> because<00:10:53.160> burning 00:10:53.630 --> 00:10:53.640 align:start position:0% used by that Lit action because burning 00:10:53.640 --> 00:10:56.269 align:start position:0% used by that Lit action because burning the<00:10:53.760> pkp<00:10:54.240> makes<00:10:54.899> it<00:10:55.079> impossible<00:10:55.500> to<00:10:55.800> use<00:10:55.920> the 00:10:56.269 --> 00:10:56.279 align:start position:0% the pkp makes it impossible to use the 00:10:56.279 --> 00:10:59.269 align:start position:0% the pkp makes it impossible to use the pkp<00:10:56.760> for<00:10:57.120> signing<00:10:57.779> anything<00:10:57.959> else 00:10:59.269 --> 00:10:59.279 align:start position:0% pkp for signing anything else 00:10:59.279 --> 00:11:01.670 align:start position:0% pkp for signing anything else a<00:10:59.940> kind<00:11:00.120> of<00:11:00.240> fun<00:11:00.420> toy<00:11:00.839> example<00:11:01.200> would<00:11:01.560> be 00:11:01.670 --> 00:11:01.680 align:start position:0% a kind of fun toy example would be 00:11:01.680 --> 00:11:04.069 align:start position:0% a kind of fun toy example would be creating<00:11:01.980> a<00:11:02.160> lit<00:11:02.399> action<00:11:03.060> that<00:11:03.600> takes<00:11:03.839> any 00:11:04.069 --> 00:11:04.079 align:start position:0% creating a lit action that takes any 00:11:04.079 --> 00:11:06.530 align:start position:0% creating a lit action that takes any number<00:11:04.320> as<00:11:04.620> input<00:11:04.980> but<00:11:05.640> will<00:11:05.820> only<00:11:06.000> sign<00:11:06.240> that 00:11:06.530 --> 00:11:06.540 align:start position:0% number as input but will only sign that 00:11:06.540 --> 00:11:08.509 align:start position:0% number as input but will only sign that number<00:11:06.720> if<00:11:07.140> it's<00:11:07.320> Prime 00:11:08.509 --> 00:11:08.519 align:start position:0% number if it's Prime 00:11:08.519 --> 00:11:10.370 align:start position:0% number if it's Prime since<00:11:09.000> anyone<00:11:09.420> can<00:11:09.600> check<00:11:09.839> that<00:11:10.200> the 00:11:10.370 --> 00:11:10.380 align:start position:0% since anyone can check that the 00:11:10.380 --> 00:11:12.530 align:start position:0% since anyone can check that the signature<00:11:10.860> matches<00:11:11.459> the<00:11:11.640> public<00:11:11.820> key<00:11:12.060> of<00:11:12.360> the 00:11:12.530 --> 00:11:12.540 align:start position:0% signature matches the public key of the 00:11:12.540 --> 00:11:16.009 align:start position:0% signature matches the public key of the pkp<00:11:13.040> they<00:11:14.040> know<00:11:14.220> that<00:11:14.519> any<00:11:14.700> number<00:11:14.940> signed<00:11:15.540> by 00:11:16.009 --> 00:11:16.019 align:start position:0% pkp they know that any number signed by 00:11:16.019 --> 00:11:18.110 align:start position:0% pkp they know that any number signed by the<00:11:16.200> corresponding<00:11:16.740> private<00:11:17.160> key<00:11:17.339> must<00:11:17.940> be 00:11:18.110 --> 00:11:18.120 align:start position:0% the corresponding private key must be 00:11:18.120 --> 00:11:19.009 align:start position:0% the corresponding private key must be Prime 00:11:19.009 --> 00:11:19.019 align:start position:0% Prime 00:11:19.019 --> 00:11:21.530 align:start position:0% Prime and<00:11:19.620> the<00:11:19.860> signature<00:11:20.279> acts<00:11:20.760> like<00:11:20.880> a<00:11:21.120> proof<00:11:21.360> that 00:11:21.530 --> 00:11:21.540 align:start position:0% and the signature acts like a proof that 00:11:21.540 --> 00:11:23.150 align:start position:0% and the signature acts like a proof that the<00:11:21.720> number<00:11:21.839> is<00:11:22.079> prime 00:11:23.150 --> 00:11:23.160 align:start position:0% the number is prime 00:11:23.160 --> 00:11:25.009 align:start position:0% the number is prime you<00:11:23.579> end<00:11:23.700> up<00:11:23.820> with<00:11:24.060> a<00:11:24.300> kind<00:11:24.420> of<00:11:24.600> prime<00:11:24.779> number 00:11:25.009 --> 00:11:25.019 align:start position:0% you end up with a kind of prime number 00:11:25.019 --> 00:11:26.930 align:start position:0% you end up with a kind of prime number certification<00:11:25.740> system 00:11:26.930 --> 00:11:26.940 align:start position:0% certification system 00:11:26.940 --> 00:11:29.870 align:start position:0% certification system this<00:11:27.480> can<00:11:27.660> be<00:11:27.839> used<00:11:28.320> to<00:11:28.740> create<00:11:28.800> a<00:11:29.100> proof<00:11:29.399> of 00:11:29.870 --> 00:11:29.880 align:start position:0% this can be used to create a proof of 00:11:29.880 --> 00:11:32.569 align:start position:0% this can be used to create a proof of any<00:11:30.420> JavaScript<00:11:30.959> code<00:11:31.260> execution 00:11:32.569 --> 00:11:32.579 align:start position:0% any JavaScript code execution 00:11:32.579 --> 00:11:35.870 align:start position:0% any JavaScript code execution and<00:11:33.180> this<00:11:33.420> is<00:11:33.540> kind<00:11:33.779> of<00:11:33.839> similar<00:11:34.339> to<00:11:35.339> how<00:11:35.579> ZK 00:11:35.870 --> 00:11:35.880 align:start position:0% and this is kind of similar to how ZK 00:11:35.880 --> 00:11:38.630 align:start position:0% and this is kind of similar to how ZK proofs<00:11:36.360> work<00:11:36.540> conceptually<00:11:37.320> but<00:11:38.160> instead<00:11:38.519> of 00:11:38.630 --> 00:11:38.640 align:start position:0% proofs work conceptually but instead of 00:11:38.640 --> 00:11:41.690 align:start position:0% proofs work conceptually but instead of being<00:11:38.880> proven<00:11:39.240> by<00:11:39.660> pure<00:11:39.899> math<00:11:40.200> it's<00:11:41.040> proven<00:11:41.399> by 00:11:41.690 --> 00:11:41.700 align:start position:0% being proven by pure math it's proven by 00:11:41.700 --> 00:11:43.790 align:start position:0% being proven by pure math it's proven by the<00:11:41.820> guarantees<00:11:42.360> provided<00:11:43.019> by<00:11:43.320> threshold 00:11:43.790 --> 00:11:43.800 align:start position:0% the guarantees provided by threshold 00:11:43.800 --> 00:11:46.550 align:start position:0% the guarantees provided by threshold threshold<00:11:44.339> cryptography<00:11:45.060> via<00:11:46.019> the<00:11:46.320> lit 00:11:46.550 --> 00:11:46.560 align:start position:0% threshold cryptography via the lit 00:11:46.560 --> 00:11:48.170 align:start position:0% threshold cryptography via the lit Network 00:11:48.170 --> 00:11:48.180 align:start position:0% Network 00:11:48.180 --> 00:11:51.949 align:start position:0% Network and<00:11:48.720> here's<00:11:49.019> kind<00:11:49.200> of<00:11:49.320> how<00:11:49.560> that<00:11:49.740> works<00:11:50.040> the<00:11:50.760> um 00:11:51.949 --> 00:11:51.959 align:start position:0% and here's kind of how that works the um 00:11:51.959 --> 00:11:54.650 align:start position:0% and here's kind of how that works the um the way<00:11:52.440> that<00:11:52.680> you<00:11:53.040> interact<00:11:53.700> with<00:11:54.060> and<00:11:54.360> Grant 00:11:54.650 --> 00:11:54.660 align:start position:0% the way that you interact with and Grant 00:11:54.660 --> 00:11:57.050 align:start position:0% the way that you interact with and Grant access<00:11:54.899> to<00:11:55.200> use<00:11:55.380> things<00:11:55.620> is<00:11:55.980> by<00:11:56.279> talking<00:11:56.640> to<00:11:56.880> a 00:11:57.050 --> 00:11:57.060 align:start position:0% access to use things is by talking to a 00:11:57.060 --> 00:12:00.170 align:start position:0% access to use things is by talking to a pkp<00:11:57.480> Smart<00:11:57.720> contract<00:11:58.700> that<00:11:59.700> currently<00:11:59.940> lives 00:12:00.170 --> 00:12:00.180 align:start position:0% pkp Smart contract that currently lives 00:12:00.180 --> 00:12:01.550 align:start position:0% pkp Smart contract that currently lives on<00:12:00.300> cello<00:12:00.720> but<00:12:00.839> we're<00:12:00.959> going<00:12:01.019> to<00:12:01.079> move<00:12:01.200> that<00:12:01.320> to 00:12:01.550 --> 00:12:01.560 align:start position:0% on cello but we're going to move that to 00:12:01.560 --> 00:12:05.990 align:start position:0% on cello but we're going to move that to polygon<00:12:02.100> soon<00:12:02.660> and<00:12:03.660> you<00:12:03.959> mint<00:12:04.260> the<00:12:04.560> pkp<00:12:05.160> grant 00:12:05.990 --> 00:12:06.000 align:start position:0% polygon soon and you mint the pkp grant 00:12:06.000 --> 00:12:08.509 align:start position:0% polygon soon and you mint the pkp grant access<00:12:06.180> for<00:12:06.540> it<00:12:06.660> to<00:12:06.839> use<00:12:06.959> the<00:12:07.140> lid<00:12:07.380> action<00:12:07.620> in 00:12:08.509 --> 00:12:08.519 align:start position:0% access for it to use the lid action in 00:12:08.519 --> 00:12:10.730 align:start position:0% access for it to use the lid action in this<00:12:08.760> authorized<00:12:09.420> lid<00:12:09.720> action<00:12:09.899> table<00:12:10.140> and 00:12:10.730 --> 00:12:10.740 align:start position:0% this authorized lid action table and 00:12:10.740 --> 00:12:13.550 align:start position:0% this authorized lid action table and then<00:12:10.860> you<00:12:10.980> burn<00:12:11.160> it<00:12:11.399> all<00:12:11.820> in<00:12:12.000> one<00:12:12.180> transaction 00:12:13.550 --> 00:12:13.560 align:start position:0% then you burn it all in one transaction 00:12:13.560 --> 00:12:15.350 align:start position:0% then you burn it all in one transaction uh<00:12:14.279> we<00:12:14.399> talked<00:12:14.579> a<00:12:14.700> little<00:12:14.760> bit<00:12:14.820> about<00:12:14.940> using<00:12:15.300> a 00:12:15.350 --> 00:12:15.360 align:start position:0% uh we talked a little bit about using a 00:12:15.360 --> 00:12:19.190 align:start position:0% uh we talked a little bit about using a pkp<00:12:15.839> as<00:12:16.019> a<00:12:16.140> vault<00:12:16.860> you<00:12:17.399> can<00:12:17.459> mint<00:12:17.700> a<00:12:17.940> pkp<00:12:18.420> then 00:12:19.190 --> 00:12:19.200 align:start position:0% pkp as a vault you can mint a pkp then 00:12:19.200 --> 00:12:21.470 align:start position:0% pkp as a vault you can mint a pkp then send<00:12:19.500> a<00:12:19.620> bunch<00:12:19.740> of<00:12:19.860> assets<00:12:20.160> to<00:12:20.339> it<00:12:20.519> like<00:12:20.820> nfts 00:12:21.470 --> 00:12:21.480 align:start position:0% send a bunch of assets to it like nfts 00:12:21.480 --> 00:12:24.470 align:start position:0% send a bunch of assets to it like nfts tokens<00:12:22.040> ethereum<00:12:23.040> and<00:12:23.640> even<00:12:23.760> ones<00:12:24.120> not<00:12:24.300> on 00:12:24.470 --> 00:12:24.480 align:start position:0% tokens ethereum and even ones not on 00:12:24.480 --> 00:12:27.650 align:start position:0% tokens ethereum and even ones not on ethereum<00:12:24.959> like<00:12:25.260> Bitcoin<00:12:25.860> or<00:12:26.160> Cosmos<00:12:26.700> tokens 00:12:27.650 --> 00:12:27.660 align:start position:0% ethereum like Bitcoin or Cosmos tokens 00:12:27.660 --> 00:12:30.650 align:start position:0% ethereum like Bitcoin or Cosmos tokens then<00:12:28.200> you<00:12:28.500> can<00:12:28.560> sell<00:12:28.860> the<00:12:29.100> pkp<00:12:29.519> nft<00:12:29.880> on<00:12:30.180> openc 00:12:30.650 --> 00:12:30.660 align:start position:0% then you can sell the pkp nft on openc 00:12:30.660 --> 00:12:33.410 align:start position:0% then you can sell the pkp nft on openc and<00:12:31.380> transfer<00:12:31.740> all<00:12:32.040> the<00:12:32.160> assets<00:12:32.399> at<00:12:32.579> once 00:12:33.410 --> 00:12:33.420 align:start position:0% and transfer all the assets at once 00:12:33.420 --> 00:12:35.750 align:start position:0% and transfer all the assets at once you<00:12:33.959> are<00:12:34.079> essentially<00:12:34.500> trustlessly<00:12:35.279> trading 00:12:35.750 --> 00:12:35.760 align:start position:0% you are essentially trustlessly trading 00:12:35.760 --> 00:12:38.030 align:start position:0% you are essentially trustlessly trading a<00:12:35.940> private<00:12:36.180> key<00:12:36.360> something<00:12:37.200> that<00:12:37.560> has<00:12:37.860> been 00:12:38.030 --> 00:12:38.040 align:start position:0% a private key something that has been 00:12:38.040 --> 00:12:40.009 align:start position:0% a private key something that has been impossible<00:12:38.519> until<00:12:39.000> now 00:12:40.009 --> 00:12:40.019 align:start position:0% impossible until now 00:12:40.019 --> 00:12:42.350 align:start position:0% impossible until now this<00:12:40.560> breaks<00:12:40.920> Soul<00:12:41.100> bound<00:12:41.339> tokens<00:12:41.760> because 00:12:42.350 --> 00:12:42.360 align:start position:0% this breaks Soul bound tokens because 00:12:42.360 --> 00:12:44.210 align:start position:0% this breaks Soul bound tokens because now<00:12:42.660> you<00:12:42.839> can<00:12:42.959> trustlessly<00:12:43.560> sell<00:12:43.740> the<00:12:43.920> wallet 00:12:44.210 --> 00:12:44.220 align:start position:0% now you can trustlessly sell the wallet 00:12:44.220 --> 00:12:46.670 align:start position:0% now you can trustlessly sell the wallet that<00:12:44.700> contains<00:12:45.120> your<00:12:45.240> soul<00:12:45.420> bound<00:12:45.720> tokens<00:12:46.079> in 00:12:46.670 --> 00:12:46.680 align:start position:0% that contains your soul bound tokens in 00:12:46.680 --> 00:12:48.290 align:start position:0% that contains your soul bound tokens in the<00:12:46.800> same<00:12:46.920> way<00:12:47.100> that<00:12:47.279> you<00:12:47.459> could<00:12:47.579> sell<00:12:47.880> a 00:12:48.290 --> 00:12:48.300 align:start position:0% the same way that you could sell a 00:12:48.300 --> 00:12:52.129 align:start position:0% the same way that you could sell a traditional<00:12:48.660> non-sol<00:12:49.380> bound<00:12:49.820> erc721<00:12:50.820> nft 00:12:52.129 --> 00:12:52.139 align:start position:0% traditional non-sol bound erc721 nft 00:12:52.139 --> 00:12:54.530 align:start position:0% traditional non-sol bound erc721 nft this<00:12:52.680> also<00:12:52.980> enables<00:12:53.339> things<00:12:53.639> like<00:12:53.940> liquid 00:12:54.530 --> 00:12:54.540 align:start position:0% this also enables things like liquid 00:12:54.540 --> 00:12:56.690 align:start position:0% this also enables things like liquid staking<00:12:54.899> for<00:12:55.500> chains<00:12:55.920> that<00:12:56.100> lock<00:12:56.279> up<00:12:56.519> the 00:12:56.690 --> 00:12:56.700 align:start position:0% staking for chains that lock up the 00:12:56.700 --> 00:12:59.329 align:start position:0% staking for chains that lock up the staked<00:12:57.060> tokens<00:12:57.360> like<00:12:57.779> ethereum<00:12:58.260> 2. 00:12:59.329 --> 00:12:59.339 align:start position:0% staked tokens like ethereum 2. 00:12:59.339 --> 00:13:02.810 align:start position:0% staked tokens like ethereum 2. you<00:12:59.880> could<00:13:00.000> use<00:13:00.300> a<00:13:00.720> pkp<00:13:01.260> as<00:13:01.980> an<00:13:02.279> eoa<00:13:02.639> Cloud 00:13:02.810 --> 00:13:02.820 align:start position:0% you could use a pkp as an eoa Cloud 00:13:02.820 --> 00:13:06.050 align:start position:0% you could use a pkp as an eoa Cloud wallet<00:13:03.500> because<00:13:04.500> a<00:13:04.860> pkp<00:13:05.399> can<00:13:05.639> grant<00:13:05.880> the 00:13:06.050 --> 00:13:06.060 align:start position:0% wallet because a pkp can grant the 00:13:06.060 --> 00:13:08.389 align:start position:0% wallet because a pkp can grant the ability<00:13:06.300> to<00:13:06.540> sign<00:13:06.899> to<00:13:07.260> a<00:13:07.380> lit<00:13:07.620> action 00:13:08.389 --> 00:13:08.399 align:start position:0% ability to sign to a lit action 00:13:08.399 --> 00:13:10.550 align:start position:0% ability to sign to a lit action you<00:13:08.880> can<00:13:08.940> create<00:13:09.180> any<00:13:09.660> auth<00:13:09.959> method<00:13:10.260> that<00:13:10.440> you 00:13:10.550 --> 00:13:10.560 align:start position:0% you can create any auth method that you 00:13:10.560 --> 00:13:12.470 align:start position:0% you can create any auth method that you want<00:13:10.740> as<00:13:11.399> long<00:13:11.519> as<00:13:11.639> it's<00:13:11.760> possible<00:13:12.060> to<00:13:12.360> express 00:13:12.470 --> 00:13:12.480 align:start position:0% want as long as it's possible to express 00:13:12.480 --> 00:13:14.629 align:start position:0% want as long as it's possible to express it<00:13:12.839> in<00:13:13.260> JavaScript 00:13:14.629 --> 00:13:14.639 align:start position:0% it in JavaScript 00:13:14.639 --> 00:13:16.190 align:start position:0% it in JavaScript you<00:13:15.000> could<00:13:15.060> create<00:13:15.240> a<00:13:15.480> wallet<00:13:15.720> that<00:13:15.899> will<00:13:16.019> only 00:13:16.190 --> 00:13:16.200 align:start position:0% you could create a wallet that will only 00:13:16.200 --> 00:13:18.470 align:start position:0% you could create a wallet that will only sign<00:13:16.500> if<00:13:17.040> the<00:13:17.160> user<00:13:17.459> calling<00:13:17.760> the<00:13:17.940> lit<00:13:18.240> action 00:13:18.470 --> 00:13:18.480 align:start position:0% sign if the user calling the lit action 00:13:18.480 --> 00:13:20.329 align:start position:0% sign if the user calling the lit action is<00:13:18.779> a<00:13:18.899> member<00:13:19.139> of<00:13:19.200> a<00:13:19.320> dow 00:13:20.329 --> 00:13:20.339 align:start position:0% is a member of a dow 00:13:20.339 --> 00:13:21.829 align:start position:0% is a member of a dow you<00:13:20.760> could<00:13:20.820> use<00:13:21.060> another<00:13:21.300> signature 00:13:21.829 --> 00:13:21.839 align:start position:0% you could use another signature 00:13:21.839 --> 00:13:23.509 align:start position:0% you could use another signature algorithm<00:13:22.200> for<00:13:22.440> verification<00:13:22.920> that's 00:13:23.509 --> 00:13:23.519 align:start position:0% algorithm for verification that's 00:13:23.519 --> 00:13:27.230 align:start position:0% algorithm for verification that's unsupported<00:13:24.060> by<00:13:24.180> ethereum<00:13:24.660> like<00:13:25.519> ed25519<00:13:26.519> or 00:13:27.230 --> 00:13:27.240 align:start position:0% unsupported by ethereum like ed25519 or 00:13:27.240 --> 00:13:28.610 align:start position:0% unsupported by ethereum like ed25519 or BLS 00:13:28.610 --> 00:13:28.620 align:start position:0% BLS 00:13:28.620 --> 00:13:30.590 align:start position:0% BLS you<00:13:29.100> could<00:13:29.160> even<00:13:29.279> create<00:13:29.519> a<00:13:29.700> wallet<00:13:30.000> that<00:13:30.420> will 00:13:30.590 --> 00:13:30.600 align:start position:0% you could even create a wallet that will 00:13:30.600 --> 00:13:32.870 align:start position:0% you could even create a wallet that will only<00:13:30.779> sign<00:13:31.019> transactions<00:13:31.620> on<00:13:31.800> Tuesdays 00:13:32.870 --> 00:13:32.880 align:start position:0% only sign transactions on Tuesdays 00:13:32.880 --> 00:13:36.530 align:start position:0% only sign transactions on Tuesdays you<00:13:33.480> can<00:13:33.600> use<00:13:33.839> a<00:13:34.139> pkp<00:13:34.680> for<00:13:34.860> automation<00:13:35.700> because 00:13:36.530 --> 00:13:36.540 align:start position:0% you can use a pkp for automation because 00:13:36.540 --> 00:13:39.110 align:start position:0% you can use a pkp for automation because the<00:13:36.899> lit<00:13:37.139> nodes<00:13:37.440> do<00:13:37.680> the<00:13:37.800> actual<00:13:38.040> signing<00:13:38.459> you 00:13:39.110 --> 00:13:39.120 align:start position:0% the lit nodes do the actual signing you 00:13:39.120 --> 00:13:40.550 align:start position:0% the lit nodes do the actual signing you could<00:13:39.240> create<00:13:39.360> a<00:13:39.540> lit<00:13:39.720> action<00:13:39.959> that<00:13:40.260> checks 00:13:40.550 --> 00:13:40.560 align:start position:0% could create a lit action that checks 00:13:40.560 --> 00:13:42.230 align:start position:0% could create a lit action that checks the<00:13:40.680> price<00:13:40.800> of<00:13:40.980> a<00:13:41.100> token<00:13:41.339> you're<00:13:41.519> staking<00:13:41.820> and 00:13:42.230 --> 00:13:42.240 align:start position:0% the price of a token you're staking and 00:13:42.240 --> 00:13:43.629 align:start position:0% the price of a token you're staking and if<00:13:42.360> it<00:13:42.480> drops<00:13:42.720> below<00:13:43.019> a<00:13:43.139> certain<00:13:43.260> price 00:13:43.629 --> 00:13:43.639 align:start position:0% if it drops below a certain price 00:13:43.639 --> 00:13:46.610 align:start position:0% if it drops below a certain price unstake<00:13:44.639> the<00:13:44.820> token<00:13:45.120> and<00:13:45.540> sell<00:13:45.720> it 00:13:46.610 --> 00:13:46.620 align:start position:0% unstake the token and sell it 00:13:46.620 --> 00:13:48.829 align:start position:0% unstake the token and sell it this<00:13:47.040> works<00:13:47.279> across<00:13:47.639> chains<00:13:48.000> and<00:13:48.420> could<00:13:48.660> run 00:13:48.829 --> 00:13:48.839 align:start position:0% this works across chains and could run 00:13:48.839 --> 00:13:50.389 align:start position:0% this works across chains and could run while<00:13:49.079> you're<00:13:49.260> asleep 00:13:50.389 --> 00:13:50.399 align:start position:0% while you're asleep 00:13:50.399 --> 00:13:52.310 align:start position:0% while you're asleep you<00:13:50.760> can<00:13:50.820> make<00:13:51.000> any<00:13:51.300> sort<00:13:51.540> of<00:13:51.779> complicated 00:13:52.310 --> 00:13:52.320 align:start position:0% you can make any sort of complicated 00:13:52.320 --> 00:13:54.590 align:start position:0% you can make any sort of complicated automated<00:13:52.800> trading<00:13:53.220> bot<00:13:53.399> without<00:13:54.000> needing<00:13:54.480> to 00:13:54.590 --> 00:13:54.600 align:start position:0% automated trading bot without needing to 00:13:54.600 --> 00:13:56.569 align:start position:0% automated trading bot without needing to have<00:13:54.720> a<00:13:54.899> hot<00:13:55.019> wallet<00:13:55.380> sitting<00:13:56.100> on<00:13:56.220> a<00:13:56.339> server 00:13:56.569 --> 00:13:56.579 align:start position:0% have a hot wallet sitting on a server 00:13:56.579 --> 00:13:58.730 align:start position:0% have a hot wallet sitting on a server somewhere<00:13:56.940> that<00:13:57.600> will<00:13:57.779> get<00:13:58.019> hacked<00:13:58.380> when<00:13:58.620> you 00:13:58.730 --> 00:13:58.740 align:start position:0% somewhere that will get hacked when you 00:13:58.740 --> 00:14:03.230 align:start position:0% somewhere that will get hacked when you forget<00:13:58.920> to<00:13:59.220> update<00:13:59.519> your<00:13:59.700> Linux<00:14:00.000> distribution 00:14:03.230 --> 00:14:03.240 align:start position:0% 00:14:03.240 --> 00:14:05.329 align:start position:0% and<00:14:03.899> here<00:14:04.200> are<00:14:04.380> some<00:14:04.500> ideas 00:14:05.329 --> 00:14:05.339 align:start position:0% and here are some ideas 00:14:05.339 --> 00:14:07.310 align:start position:0% and here are some ideas of<00:14:06.060> a<00:14:06.300> lot<00:14:06.480> of<00:14:06.600> different<00:14:06.660> things<00:14:06.899> that<00:14:07.139> you 00:14:07.310 --> 00:14:07.320 align:start position:0% of a lot of different things that you 00:14:07.320 --> 00:14:09.170 align:start position:0% of a lot of different things that you can<00:14:07.440> build<00:14:07.560> I<00:14:07.800> won't<00:14:07.980> read<00:14:08.160> them<00:14:08.339> all<00:14:08.459> but<00:14:08.820> yeah 00:14:09.170 --> 00:14:09.180 align:start position:0% can build I won't read them all but yeah 00:14:09.180 --> 00:14:10.970 align:start position:0% can build I won't read them all but yeah you<00:14:09.720> can<00:14:09.839> check<00:14:09.959> them<00:14:10.079> out<00:14:10.260> we<00:14:10.680> could<00:14:10.800> talk 00:14:10.970 --> 00:14:10.980 align:start position:0% you can check them out we could talk 00:14:10.980 --> 00:14:12.650 align:start position:0% you can check them out we could talk about<00:14:11.100> uh<00:14:11.579> some<00:14:11.760> of<00:14:11.880> these<00:14:12.000> ideas<00:14:12.120> I<00:14:12.420> think<00:14:12.540> is 00:14:12.650 --> 00:14:12.660 align:start position:0% about uh some of these ideas I think is 00:14:12.660 --> 00:14:15.410 align:start position:0% about uh some of these ideas I think is is<00:14:12.839> worth<00:14:13.079> pointing<00:14:13.440> to<00:14:13.500> but<00:14:13.800> maybe<00:14:14.160> just<00:14:14.519> uh 00:14:15.410 --> 00:14:15.420 align:start position:0% is worth pointing to but maybe just uh 00:14:15.420 --> 00:14:17.210 align:start position:0% is worth pointing to but maybe just uh um<00:14:15.480> a<00:14:16.139> few<00:14:16.200> more<00:14:16.260> metaphors<00:14:16.620> like<00:14:16.920> one<00:14:17.040> of<00:14:17.160> the 00:14:17.210 --> 00:14:17.220 align:start position:0% um a few more metaphors like one of the 00:14:17.220 --> 00:14:18.350 align:start position:0% um a few more metaphors like one of the ways<00:14:17.399> that<00:14:17.519> I<00:14:17.639> really<00:14:17.700> like<00:14:17.880> thinking<00:14:18.180> about 00:14:18.350 --> 00:14:18.360 align:start position:0% ways that I really like thinking about 00:14:18.360 --> 00:14:20.870 align:start position:0% ways that I really like thinking about uh<00:14:19.200> this<00:14:19.560> programmable<00:14:20.100> key<00:14:20.339> pair<00:14:20.519> notion 00:14:20.870 --> 00:14:20.880 align:start position:0% uh this programmable key pair notion 00:14:20.880 --> 00:14:23.090 align:start position:0% uh this programmable key pair notion what<00:14:21.000> we've<00:14:21.180> been<00:14:21.240> calling<00:14:21.480> a<00:14:21.600> pkp<00:14:22.139> in<00:14:22.860> a<00:14:22.980> way 00:14:23.090 --> 00:14:23.100 align:start position:0% what we've been calling a pkp in a way 00:14:23.100 --> 00:14:25.910 align:start position:0% what we've been calling a pkp in a way like<00:14:23.519> the<00:14:23.940> centralized<00:14:24.839> equivalent<00:14:25.440> is 00:14:25.910 --> 00:14:25.920 align:start position:0% like the centralized equivalent is 00:14:25.920 --> 00:14:27.470 align:start position:0% like the centralized equivalent is thinking<00:14:26.279> about<00:14:26.399> this<00:14:26.700> like<00:14:27.000> an<00:14:27.300> Amazon 00:14:27.470 --> 00:14:27.480 align:start position:0% thinking about this like an Amazon 00:14:27.480 --> 00:14:30.530 align:start position:0% thinking about this like an Amazon Lambda<00:14:28.079> function<00:14:28.440> plus<00:14:28.800> the<00:14:28.980> Amazon<00:14:29.220> KMS<00:14:29.940> but 00:14:30.530 --> 00:14:30.540 align:start position:0% Lambda function plus the Amazon KMS but 00:14:30.540 --> 00:14:32.389 align:start position:0% Lambda function plus the Amazon KMS but in<00:14:30.660> this<00:14:30.839> case<00:14:31.019> the<00:14:31.500> KMS<00:14:31.920> isn't<00:14:32.220> something 00:14:32.389 --> 00:14:32.399 align:start position:0% in this case the KMS isn't something 00:14:32.399 --> 00:14:34.970 align:start position:0% in this case the KMS isn't something that's<00:14:32.700> centralized<00:14:33.360> it's<00:14:34.079> uh<00:14:34.440> distributed 00:14:34.970 --> 00:14:34.980 align:start position:0% that's centralized it's uh distributed 00:14:34.980 --> 00:14:37.069 align:start position:0% that's centralized it's uh distributed across<00:14:35.459> this<00:14:35.639> threshold<00:14:36.000> cryptography<00:14:36.720> based 00:14:37.069 --> 00:14:37.079 align:start position:0% across this threshold cryptography based 00:14:37.079 --> 00:14:39.410 align:start position:0% across this threshold cryptography based Network<00:14:37.200> and<00:14:37.980> these<00:14:38.220> lit<00:14:38.519> actions<00:14:39.060> are<00:14:39.240> the 00:14:39.410 --> 00:14:39.420 align:start position:0% Network and these lit actions are the 00:14:39.420 --> 00:14:41.569 align:start position:0% Network and these lit actions are the equivalent<00:14:39.779> of<00:14:40.079> the<00:14:40.260> land<00:14:40.380> Lambda<00:14:41.040> functions 00:14:41.569 --> 00:14:41.579 align:start position:0% equivalent of the land Lambda functions 00:14:41.579 --> 00:14:43.790 align:start position:0% equivalent of the land Lambda functions and<00:14:42.060> so<00:14:42.240> it's<00:14:42.360> this<00:14:42.660> distributed<00:14:43.199> system<00:14:43.440> for 00:14:43.790 --> 00:14:43.800 align:start position:0% and so it's this distributed system for 00:14:43.800 --> 00:14:45.949 align:start position:0% and so it's this distributed system for doing<00:14:44.100> the<00:14:44.579> same<00:14:44.699> type<00:14:44.940> of<00:14:45.000> operations<00:14:45.540> that 00:14:45.949 --> 00:14:45.959 align:start position:0% doing the same type of operations that 00:14:45.959 --> 00:14:49.250 align:start position:0% doing the same type of operations that you<00:14:46.139> would<00:14:46.380> build<00:14:46.860> with<00:14:47.459> Lambda<00:14:48.180> function<00:14:48.600> and 00:14:49.250 --> 00:14:49.260 align:start position:0% you would build with Lambda function and 00:14:49.260 --> 00:14:53.030 align:start position:0% you would build with Lambda function and Amazon's<00:14:49.860> KMS<00:14:50.399> but<00:14:51.360> in<00:14:51.660> this<00:14:51.779> case<00:14:51.959> you<00:14:52.620> as<00:14:52.860> the 00:14:53.030 --> 00:14:53.040 align:start position:0% Amazon's KMS but in this case you as the 00:14:53.040 --> 00:14:54.710 align:start position:0% Amazon's KMS but in this case you as the application<00:14:53.459> developer<00:14:53.940> when<00:14:54.180> you<00:14:54.360> come<00:14:54.480> and 00:14:54.710 --> 00:14:54.720 align:start position:0% application developer when you come and 00:14:54.720 --> 00:14:56.930 align:start position:0% application developer when you come and bring<00:14:54.899> customers<00:14:55.320> on<00:14:55.560> board<00:14:55.740> you<00:14:56.399> have<00:14:56.699> this 00:14:56.930 --> 00:14:56.940 align:start position:0% bring customers on board you have this 00:14:56.940 --> 00:14:58.670 align:start position:0% bring customers on board you have this kind<00:14:57.180> of<00:14:57.300> distributed<00:14:57.839> back<00:14:58.139> end<00:14:58.260> where<00:14:58.500> you 00:14:58.670 --> 00:14:58.680 align:start position:0% kind of distributed back end where you 00:14:58.680 --> 00:15:00.470 align:start position:0% kind of distributed back end where you can't<00:14:58.800> get<00:14:58.980> access<00:14:59.220> to<00:14:59.579> the<00:14:59.699> keys<00:15:00.000> where<00:15:00.300> if 00:15:00.470 --> 00:15:00.480 align:start position:0% can't get access to the keys where if 00:15:00.480 --> 00:15:02.210 align:start position:0% can't get access to the keys where if you<00:15:00.540> like<00:15:00.720> build<00:15:00.899> the<00:15:01.079> defy<00:15:01.440> automation<00:15:01.800> bot 00:15:02.210 --> 00:15:02.220 align:start position:0% you like build the defy automation bot 00:15:02.220 --> 00:15:04.069 align:start position:0% you like build the defy automation bot and<00:15:02.579> start<00:15:02.820> selling<00:15:03.240> to<00:15:03.420> somebody<00:15:03.600> as<00:15:03.899> a 00:15:04.069 --> 00:15:04.079 align:start position:0% and start selling to somebody as a 00:15:04.079 --> 00:15:05.930 align:start position:0% and start selling to somebody as a subscription<00:15:04.440> today<00:15:04.800> you<00:15:05.279> you<00:15:05.639> could<00:15:05.760> jump 00:15:05.930 --> 00:15:05.940 align:start position:0% subscription today you you could jump 00:15:05.940 --> 00:15:08.090 align:start position:0% subscription today you you could jump into<00:15:06.060> Amazon's<00:15:06.600> KMS<00:15:07.019> and<00:15:07.260> grab<00:15:07.560> the<00:15:07.740> keys<00:15:07.980> and 00:15:08.090 --> 00:15:08.100 align:start position:0% into Amazon's KMS and grab the keys and 00:15:08.100 --> 00:15:09.769 align:start position:0% into Amazon's KMS and grab the keys and the<00:15:08.220> funds<00:15:08.459> out<00:15:08.579> at<00:15:08.760> any<00:15:08.940> point<00:15:09.180> a<00:15:09.660> couple 00:15:09.769 --> 00:15:09.779 align:start position:0% the funds out at any point a couple 00:15:09.779 --> 00:15:11.750 align:start position:0% the funds out at any point a couple other<00:15:10.260> interesting<00:15:10.740> things<00:15:11.040> that<00:15:11.459> I<00:15:11.639> think 00:15:11.750 --> 00:15:11.760 align:start position:0% other interesting things that I think 00:15:11.760 --> 00:15:13.730 align:start position:0% other interesting things that I think are<00:15:11.940> really<00:15:12.480> fun<00:15:12.779> to<00:15:12.959> think<00:15:13.139> about<00:15:13.260> when<00:15:13.620> we 00:15:13.730 --> 00:15:13.740 align:start position:0% are really fun to think about when we 00:15:13.740 --> 00:15:15.829 align:start position:0% are really fun to think about when we start<00:15:13.860> to<00:15:14.040> think<00:15:14.160> about<00:15:14.339> the<00:15:14.579> notion<00:15:14.880> of<00:15:15.360> kind 00:15:15.829 --> 00:15:15.839 align:start position:0% start to think about the notion of kind 00:15:15.839 --> 00:15:18.230 align:start position:0% start to think about the notion of kind of<00:15:15.959> this<00:15:16.380> Cloud<00:15:16.620> key<00:15:16.980> there's<00:15:17.760> a<00:15:18.000> lot<00:15:18.120> of 00:15:18.230 --> 00:15:18.240 align:start position:0% of this Cloud key there's a lot of 00:15:18.240 --> 00:15:21.650 align:start position:0% of this Cloud key there's a lot of implications<00:15:18.779> for<00:15:19.500> this<00:15:20.459> um<00:15:20.459> as<00:15:20.820> a<00:15:21.060> Dows<00:15:21.480> key 00:15:21.650 --> 00:15:21.660 align:start position:0% implications for this um as a Dows key 00:15:21.660 --> 00:15:24.170 align:start position:0% implications for this um as a Dows key so<00:15:22.320> we<00:15:22.560> could<00:15:22.680> talk<00:15:22.860> about<00:15:22.980> Dows<00:15:23.519> and<00:15:23.699> D<00:15:23.820> Phi 00:15:24.170 --> 00:15:24.180 align:start position:0% so we could talk about Dows and D Phi 00:15:24.180 --> 00:15:27.170 align:start position:0% so we could talk about Dows and D Phi and<00:15:24.600> and<00:15:25.019> use<00:15:25.440> our<00:15:25.680> own<00:15:25.800> social<00:15:26.040> media<00:15:26.519> but<00:15:27.000> in 00:15:27.170 --> 00:15:27.180 align:start position:0% and and use our own social media but in 00:15:27.180 --> 00:15:29.090 align:start position:0% and and use our own social media but in the<00:15:27.360> context<00:15:27.600> of<00:15:27.839> a<00:15:28.019> Dao<00:15:28.320> the<00:15:28.740> current<00:15:28.800> state 00:15:29.090 --> 00:15:29.100 align:start position:0% the context of a Dao the current state 00:15:29.100 --> 00:15:31.790 align:start position:0% the context of a Dao the current state of<00:15:29.279> the<00:15:29.399> art<00:15:29.519> for<00:15:29.940> Dows<00:15:30.600> is<00:15:30.779> of<00:15:30.959> course<00:15:31.079> to<00:15:31.560> use 00:15:31.790 --> 00:15:31.800 align:start position:0% of the art for Dows is of course to use 00:15:31.800 --> 00:15:34.189 align:start position:0% of the art for Dows is of course to use Smart<00:15:32.100> contract<00:15:32.579> wallets<00:15:33.060> to<00:15:33.540> manage<00:15:34.019> their 00:15:34.189 --> 00:15:34.199 align:start position:0% Smart contract wallets to manage their 00:15:34.199 --> 00:15:36.110 align:start position:0% Smart contract wallets to manage their treasury<00:15:34.560> but<00:15:35.279> more<00:15:35.399> and<00:15:35.579> more<00:15:35.699> especially 00:15:36.110 --> 00:15:36.120 align:start position:0% treasury but more and more especially 00:15:36.120 --> 00:15:37.730 align:start position:0% treasury but more and more especially protocol<00:15:36.540> dials<00:15:37.019> we're<00:15:37.139> seeing<00:15:37.320> things<00:15:37.560> that 00:15:37.730 --> 00:15:37.740 align:start position:0% protocol dials we're seeing things that 00:15:37.740 --> 00:15:39.710 align:start position:0% protocol dials we're seeing things that want<00:15:37.920> to<00:15:38.040> extend<00:15:38.399> across<00:15:38.940> chain<00:15:39.120> and<00:15:39.480> cross 00:15:39.710 --> 00:15:39.720 align:start position:0% want to extend across chain and cross 00:15:39.720 --> 00:15:42.170 align:start position:0% want to extend across chain and cross ecosystem<00:15:40.380> and<00:15:41.220> so<00:15:41.399> to<00:15:41.579> start<00:15:41.760> to<00:15:41.880> think<00:15:42.000> about 00:15:42.170 --> 00:15:42.180 align:start position:0% ecosystem and so to start to think about 00:15:42.180 --> 00:15:43.970 align:start position:0% ecosystem and so to start to think about the<00:15:42.420> account<00:15:42.600> abstraction<00:15:43.199> not<00:15:43.560> at<00:15:43.740> the<00:15:43.860> level 00:15:43.970 --> 00:15:43.980 align:start position:0% the account abstraction not at the level 00:15:43.980 --> 00:15:46.550 align:start position:0% the account abstraction not at the level of<00:15:44.519> the<00:15:44.820> blockchain<00:15:45.300> but<00:15:45.899> at<00:15:46.019> the<00:15:46.139> level<00:15:46.260> of 00:15:46.550 --> 00:15:46.560 align:start position:0% of the blockchain but at the level of 00:15:46.560 --> 00:15:48.530 align:start position:0% of the blockchain but at the level of Designing<00:15:47.100> algorithm<00:15:47.639> and<00:15:48.060> creating<00:15:48.300> the 00:15:48.530 --> 00:15:48.540 align:start position:0% Designing algorithm and creating the 00:15:48.540 --> 00:15:50.509 align:start position:0% Designing algorithm and creating the rules<00:15:48.779> and<00:15:49.019> the<00:15:49.139> governance<00:15:49.440> around<00:15:49.740> this<00:15:50.100> at 00:15:50.509 --> 00:15:50.519 align:start position:0% rules and the governance around this at 00:15:50.519 --> 00:15:51.710 align:start position:0% rules and the governance around this at the<00:15:50.579> level<00:15:50.699> of<00:15:50.880> the<00:15:50.940> signing<00:15:51.300> algorithm 00:15:51.710 --> 00:15:51.720 align:start position:0% the level of the signing algorithm 00:15:51.720 --> 00:15:53.569 align:start position:0% the level of the signing algorithm starts<00:15:52.320> to<00:15:52.440> get<00:15:52.560> really<00:15:52.800> interesting<00:15:53.220> because 00:15:53.569 --> 00:15:53.579 align:start position:0% starts to get really interesting because 00:15:53.579 --> 00:15:55.430 align:start position:0% starts to get really interesting because you<00:15:53.880> can<00:15:54.000> have<00:15:54.240> the<00:15:54.839> same<00:15:54.959> rules<00:15:55.320> around 00:15:55.430 --> 00:15:55.440 align:start position:0% you can have the same rules around 00:15:55.440 --> 00:15:57.230 align:start position:0% you can have the same rules around governance<00:15:56.040> issuing<00:15:56.699> verifiable 00:15:57.230 --> 00:15:57.240 align:start position:0% governance issuing verifiable 00:15:57.240 --> 00:15:58.850 align:start position:0% governance issuing verifiable credentials<00:15:57.779> for<00:15:57.959> your<00:15:58.079> Dao<00:15:58.440> making 00:15:58.850 --> 00:15:58.860 align:start position:0% credentials for your Dao making 00:15:58.860 --> 00:16:01.069 align:start position:0% credentials for your Dao making transactions<00:15:59.639> on<00:15:59.880> eth<00:16:00.240> doing<00:16:00.660> right<00:16:00.899> to 00:16:01.069 --> 00:16:01.079 align:start position:0% transactions on eth doing right to 00:16:01.079 --> 00:16:03.590 align:start position:0% transactions on eth doing right to rights<00:16:01.680> to<00:16:01.860> ceramic<00:16:02.339> all<00:16:02.940> from<00:16:03.180> the<00:16:03.420> same 00:16:03.590 --> 00:16:03.600 align:start position:0% rights to ceramic all from the same 00:16:03.600 --> 00:16:06.410 align:start position:0% rights to ceramic all from the same underlying<00:16:04.500> curve 00:16:06.410 --> 00:16:06.420 align:start position:0% underlying curve 00:16:06.420 --> 00:16:08.689 align:start position:0% underlying curve um<00:16:06.480> and<00:16:07.139> then<00:16:07.260> yeah<00:16:07.680> I<00:16:07.860> think<00:16:07.980> another<00:16:08.399> one 00:16:08.689 --> 00:16:08.699 align:start position:0% um and then yeah I think another one 00:16:08.699 --> 00:16:10.189 align:start position:0% um and then yeah I think another one that's<00:16:08.880> kind<00:16:09.120> of<00:16:09.240> really<00:16:09.360> uh<00:16:09.779> interesting 00:16:10.189 --> 00:16:10.199 align:start position:0% that's kind of really uh interesting 00:16:10.199 --> 00:16:14.090 align:start position:0% that's kind of really uh interesting here<00:16:10.620> is<00:16:11.339> thinking<00:16:11.820> about<00:16:12.260> uh<00:16:13.260> this<00:16:13.680> in<00:16:13.920> the 00:16:14.090 --> 00:16:14.100 align:start position:0% here is thinking about uh this in the 00:16:14.100 --> 00:16:17.090 align:start position:0% here is thinking about uh this in the context<00:16:14.459> of<00:16:15.260> mainstream<00:16:16.260> adoption<00:16:16.620> we 00:16:17.090 --> 00:16:17.100 align:start position:0% context of mainstream adoption we 00:16:17.100 --> 00:16:18.949 align:start position:0% context of mainstream adoption we touched<00:16:17.459> on<00:16:17.519> this<00:16:17.699> a<00:16:17.940> little 00:16:18.949 --> 00:16:18.959 align:start position:0% touched on this a little 00:16:18.959 --> 00:16:21.350 align:start position:0% touched on this a little um<00:16:19.079> but<00:16:19.560> you<00:16:20.040> know<00:16:20.160> there's<00:16:20.760> always 00:16:21.350 --> 00:16:21.360 align:start position:0% um but you know there's always 00:16:21.360 --> 00:16:24.230 align:start position:0% um but you know there's always capacities<00:16:22.199> to<00:16:22.680> add<00:16:22.920> different<00:16:23.399> levels<00:16:23.940> of 00:16:24.230 --> 00:16:24.240 align:start position:0% capacities to add different levels of 00:16:24.240 --> 00:16:26.449 align:start position:0% capacities to add different levels of authorization<00:16:24.899> and<00:16:25.260> security<00:16:25.500> to<00:16:25.980> wallets 00:16:26.449 --> 00:16:26.459 align:start position:0% authorization and security to wallets 00:16:26.459 --> 00:16:28.069 align:start position:0% authorization and security to wallets but<00:16:26.940> we've<00:16:27.180> been<00:16:27.300> really<00:16:27.480> really<00:16:27.600> excited 00:16:28.069 --> 00:16:28.079 align:start position:0% but we've been really really excited 00:16:28.079 --> 00:16:29.449 align:start position:0% but we've been really really excited about<00:16:28.260> groups<00:16:28.740> that<00:16:28.860> have<00:16:29.040> started<00:16:29.279> to 00:16:29.449 --> 00:16:29.459 align:start position:0% about groups that have started to 00:16:29.459 --> 00:16:31.250 align:start position:0% about groups that have started to integrate<00:16:29.820> this<00:16:30.060> with<00:16:30.300> the<00:16:30.420> likes<00:16:30.660> of<00:16:30.839> Discord 00:16:31.250 --> 00:16:31.260 align:start position:0% integrate this with the likes of Discord 00:16:31.260 --> 00:16:34.069 align:start position:0% integrate this with the likes of Discord and<00:16:31.680> apple<00:16:32.100> Pass<00:16:32.519> Key<00:16:32.899> and<00:16:33.899> there's 00:16:34.069 --> 00:16:34.079 align:start position:0% and apple Pass Key and there's 00:16:34.079 --> 00:16:36.350 align:start position:0% and apple Pass Key and there's definitely<00:16:34.380> a<00:16:34.620> lot<00:16:34.740> of<00:16:34.920> opportunity<00:16:35.579> to<00:16:36.240> build 00:16:36.350 --> 00:16:36.360 align:start position:0% definitely a lot of opportunity to build 00:16:36.360 --> 00:16:38.269 align:start position:0% definitely a lot of opportunity to build really<00:16:36.779> sophisticating<00:16:37.440> Tooling<00:16:37.980> in<00:16:38.160> this 00:16:38.269 --> 00:16:38.279 align:start position:0% really sophisticating Tooling in this 00:16:38.279 --> 00:16:39.710 align:start position:0% really sophisticating Tooling in this ecosystem<00:16:38.699> it's<00:16:39.000> one<00:16:39.180> of<00:16:39.300> the<00:16:39.360> reasons<00:16:39.540> that 00:16:39.710 --> 00:16:39.720 align:start position:0% ecosystem it's one of the reasons that 00:16:39.720 --> 00:16:41.150 align:start position:0% ecosystem it's one of the reasons that we're<00:16:39.839> really<00:16:40.079> excited<00:16:40.380> to<00:16:40.620> give<00:16:40.740> this<00:16:40.920> talk 00:16:41.150 --> 00:16:41.160 align:start position:0% we're really excited to give this talk 00:16:41.160 --> 00:16:43.490 align:start position:0% we're really excited to give this talk like<00:16:41.880> we<00:16:42.180> have<00:16:42.300> a<00:16:42.420> core<00:16:42.660> team<00:16:42.899> that's<00:16:43.320> super 00:16:43.490 --> 00:16:43.500 align:start position:0% like we have a core team that's super 00:16:43.500 --> 00:16:45.530 align:start position:0% like we have a core team that's super focused<00:16:44.040> on<00:16:44.220> this<00:16:44.399> threshold<00:16:44.820> cryptography 00:16:45.530 --> 00:16:45.540 align:start position:0% focused on this threshold cryptography 00:16:45.540 --> 00:16:47.629 align:start position:0% focused on this threshold cryptography component<00:16:46.079> but<00:16:46.740> there's<00:16:47.040> all<00:16:47.339> kinds<00:16:47.579> of 00:16:47.629 --> 00:16:47.639 align:start position:0% component but there's all kinds of 00:16:47.639 --> 00:16:49.610 align:start position:0% component but there's all kinds of opportunities<00:16:48.180> to<00:16:48.600> like<00:16:48.779> stick<00:16:49.259> an<00:16:49.440> email 00:16:49.610 --> 00:16:49.620 align:start position:0% opportunities to like stick an email 00:16:49.620 --> 00:16:52.189 align:start position:0% opportunities to like stick an email server<00:16:50.160> inside<00:16:50.459> of<00:16:50.759> an<00:16:50.940> enclave<00:16:51.420> and<00:16:51.779> use<00:16:51.959> that 00:16:52.189 --> 00:16:52.199 align:start position:0% server inside of an enclave and use that 00:16:52.199 --> 00:16:54.350 align:start position:0% server inside of an enclave and use that as<00:16:52.440> a<00:16:52.680> methodology<00:16:53.100> for<00:16:53.579> authorizing<00:16:54.180> this 00:16:54.350 --> 00:16:54.360 align:start position:0% as a methodology for authorizing this 00:16:54.360 --> 00:16:55.850 align:start position:0% as a methodology for authorizing this with<00:16:54.600> email<00:16:54.839> that's<00:16:55.320> something<00:16:55.500> that<00:16:55.740> we're 00:16:55.850 --> 00:16:55.860 align:start position:0% with email that's something that we're 00:16:55.860 --> 00:16:57.710 align:start position:0% with email that's something that we're not<00:16:56.040> going<00:16:56.160> to<00:16:56.279> build<00:16:56.399> internally<00:16:56.820> and<00:16:57.480> so<00:16:57.600> if 00:16:57.710 --> 00:16:57.720 align:start position:0% not going to build internally and so if 00:16:57.720 --> 00:16:59.389 align:start position:0% not going to build internally and so if that's<00:16:57.899> if<00:16:58.139> this<00:16:58.500> kind<00:16:58.620> of<00:16:58.740> tooling<00:16:59.160> and 00:16:59.389 --> 00:16:59.399 align:start position:0% that's if this kind of tooling and 00:16:59.399 --> 00:17:01.910 align:start position:0% that's if this kind of tooling and privacy<00:16:59.820> tooling<00:17:00.240> and<00:17:00.560> mainstream<00:17:01.560> adoption 00:17:01.910 --> 00:17:01.920 align:start position:0% privacy tooling and mainstream adoption 00:17:01.920 --> 00:17:03.050 align:start position:0% privacy tooling and mainstream adoption tooling<00:17:02.339> is<00:17:02.519> something<00:17:02.639> that<00:17:02.880> you're 00:17:03.050 --> 00:17:03.060 align:start position:0% tooling is something that you're 00:17:03.060 --> 00:17:05.390 align:start position:0% tooling is something that you're interested<00:17:03.420> in<00:17:03.600> definitely<00:17:04.500> come<00:17:04.980> talk<00:17:05.160> to<00:17:05.280> us 00:17:05.390 --> 00:17:05.400 align:start position:0% interested in definitely come talk to us 00:17:05.400 --> 00:17:08.030 align:start position:0% interested in definitely come talk to us us<00:17:05.939> but<00:17:06.900> yeah<00:17:07.020> maybe<00:17:07.140> we'll<00:17:07.380> keep<00:17:07.620> this<00:17:07.799> slide 00:17:08.030 --> 00:17:08.040 align:start position:0% us but yeah maybe we'll keep this slide 00:17:08.040 --> 00:17:11.390 align:start position:0% us but yeah maybe we'll keep this slide up<00:17:08.419> and<00:17:09.419> uh<00:17:09.900> we'll<00:17:10.260> take<00:17:10.559> questions<00:17:10.919> for<00:17:11.280> the 00:17:11.390 --> 00:17:11.400 align:start position:0% up and uh we'll take questions for the 00:17:11.400 --> 00:17:13.130 align:start position:0% up and uh we'll take questions for the next<00:17:11.520> 10<00:17:11.640> minutes<00:17:11.819> if<00:17:12.059> there<00:17:12.240> are<00:17:12.360> any<00:17:12.480> thanks 00:17:13.130 --> 00:17:13.140 align:start position:0% next 10 minutes if there are any thanks 00:17:13.140 --> 00:17:14.720 align:start position:0% next 10 minutes if there are any thanks so<00:17:13.319> much 00:17:14.720 --> 00:17:14.730 align:start position:0% so much 00:17:14.730 --> 00:17:20.990 align:start position:0% so much [Applause] 00:17:20.990 --> 00:17:21.000 align:start position:0% [Applause] 00:17:21.000 --> 00:17:23.809 align:start position:0% [Applause] how<00:17:21.360> do<00:17:21.480> we<00:17:21.600> establish<00:17:22.020> the<00:17:22.819> trust 00:17:23.809 --> 00:17:23.819 align:start position:0% how do we establish the trust 00:17:23.819 --> 00:17:28.429 align:start position:0% how do we establish the trust relationship<00:17:24.480> between<00:17:25.079> the<00:17:25.679> clients<00:17:26.600> and<00:17:27.600> the 00:17:28.429 --> 00:17:28.439 align:start position:0% relationship between the clients and the 00:17:28.439 --> 00:17:30.590 align:start position:0% relationship between the clients and the the<00:17:28.799> notes<00:17:29.220> because<00:17:29.400> like<00:17:29.820> anyone<00:17:30.240> kind<00:17:30.480> of 00:17:30.590 --> 00:17:30.600 align:start position:0% the notes because like anyone kind of 00:17:30.600 --> 00:17:32.690 align:start position:0% the notes because like anyone kind of like<00:17:30.720> snooping<00:17:31.320> on<00:17:31.559> that<00:17:31.740> can<00:17:32.220> essentially 00:17:32.690 --> 00:17:32.700 align:start position:0% like snooping on that can essentially 00:17:32.700 --> 00:17:35.830 align:start position:0% like snooping on that can essentially you<00:17:33.059> know<00:17:33.179> rebuild<00:17:33.600> the<00:17:34.020> uh<00:17:34.740> rebuild<00:17:35.340> the 00:17:35.830 --> 00:17:35.840 align:start position:0% you know rebuild the uh rebuild the 00:17:35.840 --> 00:17:39.070 align:start position:0% you know rebuild the uh rebuild the signing<00:17:36.840> or<00:17:37.080> the<00:17:37.260> Christian<00:17:37.500> key<00:17:37.919> yeah<00:17:38.580> I<00:17:38.940> mean 00:17:39.070 --> 00:17:39.080 align:start position:0% signing or the Christian key yeah I mean 00:17:39.080 --> 00:17:43.130 align:start position:0% signing or the Christian key yeah I mean uh<00:17:40.080> right<00:17:40.320> now<00:17:40.500> you<00:17:41.340> pass<00:17:42.059> a<00:17:42.539> cryptographic 00:17:43.130 --> 00:17:43.140 align:start position:0% uh right now you pass a cryptographic 00:17:43.140 --> 00:17:44.810 align:start position:0% uh right now you pass a cryptographic signature<00:17:43.620> with<00:17:43.919> your<00:17:44.039> request<00:17:44.340> to<00:17:44.460> the<00:17:44.580> lit 00:17:44.810 --> 00:17:44.820 align:start position:0% signature with your request to the lit 00:17:44.820 --> 00:17:46.909 align:start position:0% signature with your request to the lit nodes<00:17:45.059> so<00:17:45.600> that<00:17:45.780> could<00:17:46.020> be<00:17:46.140> a<00:17:46.320> signed<00:17:46.679> wallet 00:17:46.909 --> 00:17:46.919 align:start position:0% nodes so that could be a signed wallet 00:17:46.919 --> 00:17:48.409 align:start position:0% nodes so that could be a signed wallet message 00:17:48.409 --> 00:17:48.419 align:start position:0% message 00:17:48.419 --> 00:17:50.330 align:start position:0% message um<00:17:48.480> like<00:17:48.900> if<00:17:49.200> you<00:17:49.380> want<00:17:49.740> to<00:17:49.860> prove<00:17:50.160> something 00:17:50.330 --> 00:17:50.340 align:start position:0% um like if you want to prove something 00:17:50.340 --> 00:17:53.150 align:start position:0% um like if you want to prove something about<00:17:50.580> your<00:17:50.820> wallet<00:17:51.320> it<00:17:52.320> could<00:17:52.500> be<00:17:52.620> any<00:17:52.980> other 00:17:53.150 --> 00:17:53.160 align:start position:0% about your wallet it could be any other 00:17:53.160 --> 00:17:55.190 align:start position:0% about your wallet it could be any other cryptographic<00:17:53.820> signature<00:17:54.360> so<00:17:54.720> it<00:17:54.900> could<00:17:55.080> be 00:17:55.190 --> 00:17:55.200 align:start position:0% cryptographic signature so it could be 00:17:55.200 --> 00:17:57.409 align:start position:0% cryptographic signature so it could be you<00:17:55.620> know<00:17:55.679> you<00:17:55.860> need<00:17:56.100> some<00:17:56.220> encryption<00:17:56.640> right 00:17:57.409 --> 00:17:57.419 align:start position:0% you know you need some encryption right 00:17:57.419 --> 00:18:00.289 align:start position:0% you know you need some encryption right because<00:17:57.900> like<00:17:58.200> you<00:17:58.380> you<00:17:58.740> need<00:17:59.220> to<00:17:59.460> keep<00:17:59.820> this 00:18:00.289 --> 00:18:00.299 align:start position:0% because like you you need to keep this 00:18:00.299 --> 00:18:02.330 align:start position:0% because like you you need to keep this you<00:18:00.900> don't<00:18:00.960> need<00:18:01.080> encryption<00:18:01.500> just<00:18:02.220> a 00:18:02.330 --> 00:18:02.340 align:start position:0% you don't need encryption just a 00:18:02.340 --> 00:18:04.010 align:start position:0% you don't need encryption just a signature<00:18:02.760> and<00:18:03.059> the<00:18:03.179> nodes<00:18:03.419> verify<00:18:03.900> the 00:18:04.010 --> 00:18:04.020 align:start position:0% signature and the nodes verify the 00:18:04.020 --> 00:18:06.169 align:start position:0% signature and the nodes verify the signature<00:18:04.500> and<00:18:04.980> and<00:18:05.280> by<00:18:05.700> verifying<00:18:06.120> the 00:18:06.169 --> 00:18:06.179 align:start position:0% signature and and by verifying the 00:18:06.179 --> 00:18:07.970 align:start position:0% signature and and by verifying the signature<00:18:06.539> they<00:18:06.720> can<00:18:06.840> prove<00:18:07.080> that<00:18:07.320> you<00:18:07.860> own 00:18:07.970 --> 00:18:07.980 align:start position:0% signature they can prove that you own 00:18:07.980 --> 00:18:11.090 align:start position:0% signature they can prove that you own that<00:18:08.220> wallet<00:18:08.520> yes<00:18:09.419> but<00:18:10.080> they're<00:18:10.440> gonna<00:18:10.679> send 00:18:11.090 --> 00:18:11.100 align:start position:0% that wallet yes but they're gonna send 00:18:11.100 --> 00:18:14.390 align:start position:0% that wallet yes but they're gonna send you<00:18:11.340> in<00:18:11.940> exchange<00:18:12.360> like<00:18:13.140> a<00:18:13.320> key<00:18:13.500> share<00:18:13.799> right 00:18:14.390 --> 00:18:14.400 align:start position:0% you in exchange like a key share right 00:18:14.400 --> 00:18:16.549 align:start position:0% you in exchange like a key share right yeah<00:18:15.240> yeah<00:18:15.419> they<00:18:15.600> they<00:18:15.780> don't<00:18:16.020> actually<00:18:16.260> send 00:18:16.549 --> 00:18:16.559 align:start position:0% yeah yeah they they don't actually send 00:18:16.559 --> 00:18:19.130 align:start position:0% yeah yeah they they don't actually send a<00:18:16.740> key<00:18:16.919> share<00:18:17.220> they<00:18:17.760> send<00:18:18.000> a<00:18:18.240> decryption<00:18:18.780> share 00:18:19.130 --> 00:18:19.140 align:start position:0% a key share they send a decryption share 00:18:19.140 --> 00:18:22.310 align:start position:0% a key share they send a decryption share or<00:18:19.919> a<00:18:20.160> signature<00:18:20.580> share<00:18:20.880> so<00:18:21.539> the<00:18:21.780> the<00:18:21.960> key 00:18:22.310 --> 00:18:22.320 align:start position:0% or a signature share so the the key 00:18:22.320 --> 00:18:24.350 align:start position:0% or a signature share so the the key shares<00:18:22.679> themselves<00:18:23.100> never<00:18:23.460> uh<00:18:23.940> never<00:18:24.179> leave 00:18:24.350 --> 00:18:24.360 align:start position:0% shares themselves never uh never leave 00:18:24.360 --> 00:18:26.930 align:start position:0% shares themselves never uh never leave the<00:18:24.600> node<00:18:24.840> got<00:18:25.559> it<00:18:25.799> okay<00:18:26.039> I<00:18:26.340> think<00:18:26.460> that<00:18:26.580> like<00:18:26.760> I 00:18:26.930 --> 00:18:26.940 align:start position:0% the node got it okay I think that like I 00:18:26.940 --> 00:18:29.750 align:start position:0% the node got it okay I think that like I misunderstood<00:18:27.600> this<00:18:28.200> part<00:18:28.380> and<00:18:28.980> so<00:18:29.160> the<00:18:29.580> the 00:18:29.750 --> 00:18:29.760 align:start position:0% misunderstood this part and so the the 00:18:29.760 --> 00:18:31.430 align:start position:0% misunderstood this part and so the the second<00:18:30.120> question<00:18:30.780> that<00:18:31.020> I<00:18:31.200> have<00:18:31.260> is 00:18:31.430 --> 00:18:31.440 align:start position:0% second question that I have is 00:18:31.440 --> 00:18:34.250 align:start position:0% second question that I have is essentially<00:18:32.100> like<00:18:32.520> can<00:18:32.880> you<00:18:33.120> do<00:18:33.299> in<00:18:33.539> for<00:18:33.840> any 00:18:34.250 --> 00:18:34.260 align:start position:0% essentially like can you do in for any 00:18:34.260 --> 00:18:36.529 align:start position:0% essentially like can you do in for any form<00:18:34.500> of<00:18:34.740> resizing 00:18:36.529 --> 00:18:36.539 align:start position:0% form of resizing 00:18:36.539 --> 00:18:38.690 align:start position:0% form of resizing of<00:18:37.380> you<00:18:37.740> know<00:18:37.860> this 00:18:38.690 --> 00:18:38.700 align:start position:0% of you know this 00:18:38.700 --> 00:18:40.789 align:start position:0% of you know this I<00:18:39.179> wouldn't<00:18:39.299> call<00:18:39.480> it<00:18:39.660> like<00:18:39.840> a<00:18:40.020> quorum<00:18:40.440> but 00:18:40.789 --> 00:18:40.799 align:start position:0% I wouldn't call it like a quorum but 00:18:40.799 --> 00:18:44.090 align:start position:0% I wouldn't call it like a quorum but like<00:18:41.100> you<00:18:41.760> know<00:18:41.880> just<00:18:42.299> this<00:18:42.600> uh<00:18:42.900> this<00:18:43.380> set 00:18:44.090 --> 00:18:44.100 align:start position:0% like you know just this uh this set 00:18:44.100 --> 00:18:46.130 align:start position:0% like you know just this uh this set oh<00:18:44.460> like<00:18:44.760> uh<00:18:44.940> changing<00:18:45.240> the<00:18:45.419> set<00:18:45.539> of<00:18:45.660> nodes<00:18:45.900> and 00:18:46.130 --> 00:18:46.140 align:start position:0% oh like uh changing the set of nodes and 00:18:46.140 --> 00:18:47.450 align:start position:0% oh like uh changing the set of nodes and changing<00:18:46.500> the<00:18:46.679> threshold<00:18:46.980> for<00:18:47.280> example 00:18:47.450 --> 00:18:47.460 align:start position:0% changing the threshold for example 00:18:47.460 --> 00:18:50.570 align:start position:0% changing the threshold for example exactly<00:18:47.820> yeah<00:18:48.539> absolutely<00:18:49.200> yeah<00:18:49.620> so<00:18:50.039> we<00:18:50.160> use<00:18:50.340> a 00:18:50.570 --> 00:18:50.580 align:start position:0% exactly yeah absolutely yeah so we use a 00:18:50.580 --> 00:18:52.070 align:start position:0% exactly yeah absolutely yeah so we use a technology<00:18:51.000> called<00:18:51.360> proactive<00:18:51.840> secret 00:18:52.070 --> 00:18:52.080 align:start position:0% technology called proactive secret 00:18:52.080 --> 00:18:53.570 align:start position:0% technology called proactive secret sharing 00:18:53.570 --> 00:18:53.580 align:start position:0% sharing 00:18:53.580 --> 00:18:57.049 align:start position:0% sharing um<00:18:53.700> and<00:18:53.940> what<00:18:54.120> that<00:18:54.419> uh<00:18:55.140> lets<00:18:55.740> us<00:18:56.039> do<00:18:56.280> is<00:18:56.880> it 00:18:57.049 --> 00:18:57.059 align:start position:0% um and what that uh lets us do is it 00:18:57.059 --> 00:18:59.930 align:start position:0% um and what that uh lets us do is it lets<00:18:57.480> the<00:18:57.720> uh<00:18:58.140> the<00:18:58.440> nodes<00:18:58.679> like<00:18:59.340> new<00:18:59.580> nodes 00:18:59.930 --> 00:18:59.940 align:start position:0% lets the uh the nodes like new nodes 00:18:59.940 --> 00:19:02.450 align:start position:0% lets the uh the nodes like new nodes join<00:19:00.660> and<00:19:00.840> leave<00:19:01.020> the<00:19:01.260> network 00:19:02.450 --> 00:19:02.460 align:start position:0% join and leave the network 00:19:02.460 --> 00:19:04.310 align:start position:0% join and leave the network um<00:19:02.520> and<00:19:02.820> keep<00:19:03.000> the<00:19:03.240> underlying<00:19:03.720> secret<00:19:03.960> the 00:19:04.310 --> 00:19:04.320 align:start position:0% um and keep the underlying secret the 00:19:04.320 --> 00:19:06.890 align:start position:0% um and keep the underlying secret the same<00:19:04.500> but<00:19:05.280> the<00:19:05.640> private<00:19:05.940> key<00:19:06.120> Shares<00:19:06.600> are 00:19:06.890 --> 00:19:06.900 align:start position:0% same but the private key Shares are 00:19:06.900 --> 00:19:10.669 align:start position:0% same but the private key Shares are incompatible<00:19:07.440> uh<00:19:08.400> between<00:19:08.820> like<00:19:09.780> epochs<00:19:10.559> when 00:19:10.669 --> 00:19:10.679 align:start position:0% incompatible uh between like epochs when 00:19:10.679 --> 00:19:12.409 align:start position:0% incompatible uh between like epochs when it<00:19:10.860> when<00:19:11.039> nodes<00:19:11.280> leave<00:19:11.520> and<00:19:11.640> when<00:19:11.760> nodes<00:19:12.059> join 00:19:12.409 --> 00:19:12.419 align:start position:0% it when nodes leave and when nodes join 00:19:12.419 --> 00:19:14.750 align:start position:0% it when nodes leave and when nodes join basically<00:19:13.080> the<00:19:13.440> this<00:19:13.740> process<00:19:14.160> of<00:19:14.340> proactive 00:19:14.750 --> 00:19:14.760 align:start position:0% basically the this process of proactive 00:19:14.760 --> 00:19:16.490 align:start position:0% basically the this process of proactive secretaring<00:19:15.360> is<00:19:15.480> quite<00:19:15.720> similar<00:19:16.020> to<00:19:16.320> the 00:19:16.490 --> 00:19:16.500 align:start position:0% secretaring is quite similar to the 00:19:16.500 --> 00:19:19.070 align:start position:0% secretaring is quite similar to the distributed<00:19:16.980> key<00:19:17.220> generation<00:19:17.640> process 00:19:19.070 --> 00:19:19.080 align:start position:0% distributed key generation process 00:19:19.080 --> 00:19:22.669 align:start position:0% distributed key generation process um and<00:19:19.740> you<00:19:20.039> know<00:19:20.100> the<00:19:20.580> the<00:19:20.640> secret<00:19:21.140> uh<00:19:22.140> is 00:19:22.669 --> 00:19:22.679 align:start position:0% um and you know the the secret uh is 00:19:22.679 --> 00:19:25.070 align:start position:0% um and you know the the secret uh is very<00:19:23.280> very<00:19:23.460> simply<00:19:23.820> put<00:19:24.000> right<00:19:24.299> a<00:19:24.539> line<00:19:24.720> on<00:19:24.900> a 00:19:25.070 --> 00:19:25.080 align:start position:0% very very simply put right a line on a 00:19:25.080 --> 00:19:27.529 align:start position:0% very very simply put right a line on a graph<00:19:25.320> and<00:19:26.100> in<00:19:26.340> this<00:19:26.520> key<00:19:26.760> refresh<00:19:27.179> process 00:19:27.529 --> 00:19:27.539 align:start position:0% graph and in this key refresh process 00:19:27.539 --> 00:19:30.470 align:start position:0% graph and in this key refresh process you're<00:19:28.140> signing<00:19:28.620> new<00:19:28.919> points<00:19:29.340> along<00:19:29.820> the<00:19:30.360> same 00:19:30.470 --> 00:19:30.480 align:start position:0% you're signing new points along the same 00:19:30.480 --> 00:19:32.930 align:start position:0% you're signing new points along the same underlying<00:19:31.080> secret<00:19:31.320> such<00:19:32.039> that<00:19:32.280> the<00:19:32.640> shares 00:19:32.930 --> 00:19:32.940 align:start position:0% underlying secret such that the shares 00:19:32.940 --> 00:19:34.970 align:start position:0% underlying secret such that the shares in<00:19:33.059> Epoch<00:19:33.480> 2<00:19:33.600> are<00:19:33.780> incompatible<00:19:34.260> with<00:19:34.440> Epoch 00:19:34.970 --> 00:19:34.980 align:start position:0% in Epoch 2 are incompatible with Epoch 00:19:34.980 --> 00:19:37.310 align:start position:0% in Epoch 2 are incompatible with Epoch one<00:19:35.100> but<00:19:35.580> they<00:19:35.760> still<00:19:35.940> represent<00:19:36.539> the<00:19:37.200> same 00:19:37.310 --> 00:19:37.320 align:start position:0% one but they still represent the same 00:19:37.320 --> 00:19:39.830 align:start position:0% one but they still represent the same underlying<00:19:37.919> secret<00:19:38.580> and<00:19:39.360> that's 00:19:39.830 --> 00:19:39.840 align:start position:0% underlying secret and that's 00:19:39.840 --> 00:19:41.930 align:start position:0% underlying secret and that's functionally<00:19:40.500> the<00:19:40.799> goal<00:19:41.100> of<00:19:41.220> this<00:19:41.340> network<00:19:41.520> is 00:19:41.930 --> 00:19:41.940 align:start position:0% functionally the goal of this network is 00:19:41.940 --> 00:19:44.750 align:start position:0% functionally the goal of this network is to<00:19:42.240> persist<00:19:42.660> a<00:19:43.140> shared<00:19:43.679> Crypt<00:19:44.039> photographic 00:19:44.750 --> 00:19:44.760 align:start position:0% to persist a shared Crypt photographic 00:19:44.760 --> 00:19:47.510 align:start position:0% to persist a shared Crypt photographic Secret<00:19:45.000> in<00:19:45.299> perpetuity<00:19:46.320> okay<00:19:46.799> I<00:19:47.100> think<00:19:47.280> that 00:19:47.510 --> 00:19:47.520 align:start position:0% Secret in perpetuity okay I think that 00:19:47.520 --> 00:19:50.210 align:start position:0% Secret in perpetuity okay I think that that<00:19:47.820> ties<00:19:48.299> into<00:19:48.539> my<00:19:48.960> third<00:19:49.080> question<00:19:49.500> which 00:19:50.210 --> 00:19:50.220 align:start position:0% that ties into my third question which 00:19:50.220 --> 00:19:53.390 align:start position:0% that ties into my third question which is<00:19:50.400> how<00:19:51.059> do<00:19:51.240> you<00:19:51.360> ensure<00:19:51.840> kind<00:19:52.260> of<00:19:52.440> like<00:19:52.620> the 00:19:53.390 --> 00:19:53.400 align:start position:0% is how do you ensure kind of like the 00:19:53.400 --> 00:19:56.390 align:start position:0% is how do you ensure kind of like the any<00:19:53.760> form<00:19:54.059> of<00:19:54.179> like<00:19:54.419> non-so<00:19:55.140> like<00:19:55.320> counters<00:19:55.980> so 00:19:56.390 --> 00:19:56.400 align:start position:0% any form of like non-so like counters so 00:19:56.400 --> 00:19:58.010 align:start position:0% any form of like non-so like counters so that<00:19:56.640> you<00:19:56.880> know<00:19:57.000> essentially<00:19:57.539> like<00:19:57.840> the 00:19:58.010 --> 00:19:58.020 align:start position:0% that you know essentially like the 00:19:58.020 --> 00:19:59.690 align:start position:0% that you know essentially like the number<00:19:58.140> of<00:19:58.320> time<00:19:58.559> that<00:19:58.860> this<00:19:59.039> thing<00:19:59.220> has<00:19:59.520> been 00:19:59.690 --> 00:19:59.700 align:start position:0% number of time that this thing has been 00:19:59.700 --> 00:20:02.270 align:start position:0% number of time that this thing has been signed<00:20:00.120> or<00:20:00.240> like<00:20:00.480> decrypted<00:20:01.140> uh<00:20:01.799> maybe<00:20:02.039> you 00:20:02.270 --> 00:20:02.280 align:start position:0% signed or like decrypted uh maybe you 00:20:02.280 --> 00:20:04.070 align:start position:0% signed or like decrypted uh maybe you want<00:20:02.400> to<00:20:02.580> like<00:20:02.700> ensure<00:20:03.120> it<00:20:03.240> that<00:20:03.419> like<00:20:03.720> you 00:20:04.070 --> 00:20:04.080 align:start position:0% want to like ensure it that like you 00:20:04.080 --> 00:20:06.470 align:start position:0% want to like ensure it that like you know<00:20:04.140> you<00:20:04.440> can<00:20:04.500> decrypt<00:20:05.100> it<00:20:05.340> x<00:20:06.000> amount<00:20:06.240> of 00:20:06.470 --> 00:20:06.480 align:start position:0% know you can decrypt it x amount of 00:20:06.480 --> 00:20:08.990 align:start position:0% know you can decrypt it x amount of times<00:20:06.720> you<00:20:07.140> don't<00:20:07.260> want<00:20:07.500> to<00:20:07.620> you<00:20:08.220> know<00:20:08.340> you<00:20:08.640> you 00:20:08.990 --> 00:20:09.000 align:start position:0% times you don't want to you know you you 00:20:09.000 --> 00:20:11.150 align:start position:0% times you don't want to you know you you may<00:20:09.240> want<00:20:09.419> to<00:20:09.539> like<00:20:09.780> sequence<00:20:10.559> essentially 00:20:11.150 --> 00:20:11.160 align:start position:0% may want to like sequence essentially 00:20:11.160 --> 00:20:13.549 align:start position:0% may want to like sequence essentially especially<00:20:11.940> for<00:20:12.120> vaults<00:20:12.660> like<00:20:13.020> operations 00:20:13.549 --> 00:20:13.559 align:start position:0% especially for vaults like operations 00:20:13.559 --> 00:20:16.190 align:start position:0% especially for vaults like operations right<00:20:14.160> like<00:20:14.580> the<00:20:14.880> signing<00:20:15.480> of<00:20:15.660> like<00:20:15.900> specific 00:20:16.190 --> 00:20:16.200 align:start position:0% right like the signing of like specific 00:20:16.200 --> 00:20:19.190 align:start position:0% right like the signing of like specific nonsense<00:20:16.940> uh<00:20:17.940> or<00:20:18.120> like<00:20:18.299> just<00:20:18.480> ensuring<00:20:18.960> that 00:20:19.190 --> 00:20:19.200 align:start position:0% nonsense uh or like just ensuring that 00:20:19.200 --> 00:20:21.650 align:start position:0% nonsense uh or like just ensuring that like<00:20:19.860> you<00:20:20.460> you<00:20:20.640> don't<00:20:20.820> have<00:20:21.000> is<00:20:21.179> essentially 00:20:21.650 --> 00:20:21.660 align:start position:0% like you you don't have is essentially 00:20:21.660 --> 00:20:24.710 align:start position:0% like you you don't have is essentially just<00:20:22.020> like<00:20:22.640> resigning<00:20:23.640> operations<00:20:24.299> with 00:20:24.710 --> 00:20:24.720 align:start position:0% just like resigning operations with 00:20:24.720 --> 00:20:26.690 align:start position:0% just like resigning operations with different<00:20:24.840> announces<00:20:25.500> either<00:20:25.919> I'm<00:20:26.460> actually 00:20:26.690 --> 00:20:26.700 align:start position:0% different announces either I'm actually 00:20:26.700 --> 00:20:28.669 align:start position:0% different announces either I'm actually curious<00:20:27.120> how<00:20:27.299> do<00:20:27.419> you<00:20:27.539> think<00:20:27.660> about<00:20:27.840> that 00:20:28.669 --> 00:20:28.679 align:start position:0% curious how do you think about that 00:20:28.679 --> 00:20:30.169 align:start position:0% curious how do you think about that yeah 00:20:30.169 --> 00:20:30.179 align:start position:0% yeah 00:20:30.179 --> 00:20:32.510 align:start position:0% yeah um<00:20:30.299> so<00:20:30.900> what<00:20:31.200> you<00:20:31.320> could<00:20:31.440> do<00:20:31.620> so<00:20:31.919> the<00:20:32.039> the<00:20:32.220> lit 00:20:32.510 --> 00:20:32.520 align:start position:0% um so what you could do so the the lit 00:20:32.520 --> 00:20:34.070 align:start position:0% um so what you could do so the the lit nodes<00:20:32.760> themselves<00:20:33.179> are<00:20:33.360> mostly<00:20:33.660> stateless 00:20:34.070 --> 00:20:34.080 align:start position:0% nodes themselves are mostly stateless 00:20:34.080 --> 00:20:35.630 align:start position:0% nodes themselves are mostly stateless okay<00:20:34.559> so<00:20:34.740> they<00:20:34.860> don't<00:20:35.039> necessarily<00:20:35.280> have<00:20:35.460> a 00:20:35.630 --> 00:20:35.640 align:start position:0% okay so they don't necessarily have a 00:20:35.640 --> 00:20:37.789 align:start position:0% okay so they don't necessarily have a place<00:20:35.760> to<00:20:35.940> store<00:20:36.120> anything<00:20:36.360> like<00:20:36.720> that 00:20:37.789 --> 00:20:37.799 align:start position:0% place to store anything like that 00:20:37.799 --> 00:20:39.590 align:start position:0% place to store anything like that um but<00:20:38.039> what<00:20:38.220> you<00:20:38.340> can<00:20:38.460> do<00:20:38.640> in<00:20:39.179> the<00:20:39.360> lit 00:20:39.590 --> 00:20:39.600 align:start position:0% um but what you can do in the lit 00:20:39.600 --> 00:20:40.970 align:start position:0% um but what you can do in the lit actions<00:20:39.900> is<00:20:40.020> you<00:20:40.200> can<00:20:40.260> read<00:20:40.380> and<00:20:40.559> write<00:20:40.740> from 00:20:40.970 --> 00:20:40.980 align:start position:0% actions is you can read and write from 00:20:40.980 --> 00:20:44.870 align:start position:0% actions is you can read and write from blockchains<00:20:41.700> or<00:20:41.820> from<00:20:42.000> ipfs<00:20:42.600> or<00:20:42.780> wherever<00:20:43.080> so 00:20:44.870 --> 00:20:44.880 align:start position:0% blockchains or from ipfs or wherever so 00:20:44.880 --> 00:20:47.690 align:start position:0% blockchains or from ipfs or wherever so um you<00:20:45.240> could<00:20:45.419> like<00:20:46.140> at<00:20:46.860> the<00:20:46.980> end<00:20:47.160> of<00:20:47.340> a<00:20:47.460> lit 00:20:47.690 --> 00:20:47.700 align:start position:0% um you could like at the end of a lit 00:20:47.700 --> 00:20:49.250 align:start position:0% um you could like at the end of a lit action<00:20:47.940> after<00:20:48.240> you<00:20:48.539> create<00:20:48.660> the<00:20:48.840> signature 00:20:49.250 --> 00:20:49.260 align:start position:0% action after you create the signature 00:20:49.260 --> 00:20:52.909 align:start position:0% action after you create the signature share<00:20:49.500> you<00:20:49.919> could<00:20:50.039> uh<00:20:51.000> write<00:20:51.299> to<00:20:51.539> a<00:20:51.720> chain<00:20:51.919> to 00:20:52.909 --> 00:20:52.919 align:start position:0% share you could uh write to a chain to 00:20:52.919 --> 00:20:54.650 align:start position:0% share you could uh write to a chain to record<00:20:53.160> that<00:20:53.640> a<00:20:53.880> transaction<00:20:54.240> has<00:20:54.480> already 00:20:54.650 --> 00:20:54.660 align:start position:0% record that a transaction has already 00:20:54.660 --> 00:20:56.270 align:start position:0% record that a transaction has already happened 00:20:56.270 --> 00:20:56.280 align:start position:0% happened 00:20:56.280 --> 00:20:59.690 align:start position:0% happened um<00:20:56.419> and<00:20:57.419> then<00:20:58.020> if<00:20:58.980> somebody<00:20:59.160> tries<00:20:59.460> to<00:20:59.580> run 00:20:59.690 --> 00:20:59.700 align:start position:0% um and then if somebody tries to run 00:20:59.700 --> 00:21:02.510 align:start position:0% um and then if somebody tries to run that<00:20:59.880> Lit<00:21:00.179> action<00:21:00.419> again<00:21:01.039> it<00:21:02.039> could<00:21:02.220> you<00:21:02.460> know 00:21:02.510 --> 00:21:02.520 align:start position:0% that Lit action again it could you know 00:21:02.520 --> 00:21:04.370 align:start position:0% that Lit action again it could you know check<00:21:02.760> and<00:21:03.000> see<00:21:03.179> like<00:21:03.539> you<00:21:03.960> know<00:21:04.020> did<00:21:04.200> this 00:21:04.370 --> 00:21:04.380 align:start position:0% check and see like you know did this 00:21:04.380 --> 00:21:06.590 align:start position:0% check and see like you know did this transaction<00:21:04.679> already<00:21:04.919> happen<00:21:05.160> or<00:21:05.460> not<00:21:05.580> and<00:21:06.419> if 00:21:06.590 --> 00:21:06.600 align:start position:0% transaction already happen or not and if 00:21:06.600 --> 00:21:08.630 align:start position:0% transaction already happen or not and if so<00:21:06.780> it<00:21:07.020> wouldn't<00:21:07.320> sign 00:21:08.630 --> 00:21:08.640 align:start position:0% so it wouldn't sign 00:21:08.640 --> 00:21:09.770 align:start position:0% so it wouldn't sign um<00:21:08.760> and<00:21:09.000> that<00:21:09.120> that's<00:21:09.299> like<00:21:09.419> how<00:21:09.539> it<00:21:09.660> works 00:21:09.770 --> 00:21:09.780 align:start position:0% um and that that's like how it works 00:21:09.780 --> 00:21:12.830 align:start position:0% um and that that's like how it works within<00:21:10.020> the<00:21:10.140> lit<00:21:10.380> system<00:21:10.559> uh<00:21:11.520> within<00:21:11.940> like<00:21:12.240> you 00:21:12.830 --> 00:21:12.840 align:start position:0% within the lit system uh within like you 00:21:12.840 --> 00:21:14.270 align:start position:0% within the lit system uh within like you know<00:21:12.960> the<00:21:13.260> if<00:21:13.500> you're<00:21:13.620> signing<00:21:13.860> an<00:21:13.980> ethereum 00:21:14.270 --> 00:21:14.280 align:start position:0% know the if you're signing an ethereum 00:21:14.280 --> 00:21:16.669 align:start position:0% know the if you're signing an ethereum transaction<00:21:14.700> for<00:21:15.000> example<00:21:15.240> right<00:21:16.020> you<00:21:16.559> would 00:21:16.669 --> 00:21:16.679 align:start position:0% transaction for example right you would 00:21:16.679 --> 00:21:18.650 align:start position:0% transaction for example right you would just<00:21:16.860> include<00:21:17.160> the<00:21:17.340> nonce<00:21:17.760> in<00:21:18.240> the<00:21:18.360> thing<00:21:18.480> to 00:21:18.650 --> 00:21:18.660 align:start position:0% just include the nonce in the thing to 00:21:18.660 --> 00:21:20.029 align:start position:0% just include the nonce in the thing to be<00:21:18.780> signed 00:21:20.029 --> 00:21:20.039 align:start position:0% be signed 00:21:20.039 --> 00:21:21.830 align:start position:0% be signed um<00:21:20.160> when<00:21:20.340> you<00:21:20.460> send<00:21:20.640> up<00:21:20.880> like<00:21:21.299> whatever<00:21:21.480> you 00:21:21.830 --> 00:21:21.840 align:start position:0% um when you send up like whatever you 00:21:21.840 --> 00:21:24.110 align:start position:0% um when you send up like whatever you want<00:21:21.900> the<00:21:22.200> lit<00:21:22.440> action<00:21:22.620> to<00:21:22.799> be<00:21:22.980> signed 00:21:24.110 --> 00:21:24.120 align:start position:0% want the lit action to be signed 00:21:24.120 --> 00:21:25.789 align:start position:0% want the lit action to be signed um<00:21:24.179> and<00:21:24.419> so<00:21:24.600> then<00:21:24.840> you<00:21:25.020> couldn't<00:21:25.140> reuse<00:21:25.559> that 00:21:25.789 --> 00:21:25.799 align:start position:0% um and so then you couldn't reuse that 00:21:25.799 --> 00:21:27.470 align:start position:0% um and so then you couldn't reuse that signature<00:21:26.280> right 00:21:27.470 --> 00:21:27.480 align:start position:0% signature right 00:21:27.480 --> 00:21:28.610 align:start position:0% signature right um because<00:21:27.720> it<00:21:28.080> has<00:21:28.200> already<00:21:28.260> been<00:21:28.440> broadcast 00:21:28.610 --> 00:21:28.620 align:start position:0% um because it has already been broadcast 00:21:28.620 --> 00:21:31.070 align:start position:0% um because it has already been broadcast cast<00:21:28.980> with<00:21:29.280> that<00:21:29.460> nonce<00:21:29.880> maybe<00:21:30.539> I<00:21:30.720> missed<00:21:30.960> how 00:21:31.070 --> 00:21:31.080 align:start position:0% cast with that nonce maybe I missed how 00:21:31.080 --> 00:21:33.409 align:start position:0% cast with that nonce maybe I missed how you<00:21:31.260> explained<00:21:31.679> how<00:21:31.860> to<00:21:32.039> create<00:21:32.340> a<00:21:32.640> pkp 00:21:33.409 --> 00:21:33.419 align:start position:0% you explained how to create a pkp 00:21:33.419 --> 00:21:35.870 align:start position:0% you explained how to create a pkp without<00:21:33.840> any<00:21:34.260> keys<00:21:34.679> but<00:21:34.860> how<00:21:35.159> does<00:21:35.340> that<00:21:35.520> work 00:21:35.870 --> 00:21:35.880 align:start position:0% without any keys but how does that work 00:21:35.880 --> 00:21:38.690 align:start position:0% without any keys but how does that work and<00:21:36.600> how<00:21:37.140> does<00:21:37.260> the<00:21:37.380> user<00:21:37.679> not<00:21:37.919> have<00:21:38.159> a<00:21:38.400> key<00:21:38.460> and 00:21:38.690 --> 00:21:38.700 align:start position:0% and how does the user not have a key and 00:21:38.700 --> 00:21:40.549 align:start position:0% and how does the user not have a key and how<00:21:38.880> do<00:21:39.000> they<00:21:39.059> authenticate<00:21:39.659> what<00:21:40.320> things 00:21:40.549 --> 00:21:40.559 align:start position:0% how do they authenticate what things 00:21:40.559 --> 00:21:43.130 align:start position:0% how do they authenticate what things they<00:21:40.860> want<00:21:41.039> the<00:21:41.280> network<00:21:41.460> to<00:21:41.760> do<00:21:41.880> yeah<00:21:42.659> I<00:21:42.960> mean 00:21:43.130 --> 00:21:43.140 align:start position:0% they want the network to do yeah I mean 00:21:43.140 --> 00:21:45.590 align:start position:0% they want the network to do yeah I mean they<00:21:43.620> need<00:21:43.799> some<00:21:44.039> kind<00:21:44.220> of<00:21:44.400> key 00:21:45.590 --> 00:21:45.600 align:start position:0% they need some kind of key 00:21:45.600 --> 00:21:47.270 align:start position:0% they need some kind of key um<00:21:45.659> right<00:21:45.900> it<00:21:46.260> could<00:21:46.380> be<00:21:46.500> an<00:21:46.559> ethereum<00:21:46.919> wallet 00:21:47.270 --> 00:21:47.280 align:start position:0% um right it could be an ethereum wallet 00:21:47.280 --> 00:21:49.730 align:start position:0% um right it could be an ethereum wallet or<00:21:47.520> it<00:21:47.700> could<00:21:47.820> be<00:21:48.000> like<00:21:48.419> apple<00:21:48.659> passkey<00:21:49.260> which 00:21:49.730 --> 00:21:49.740 align:start position:0% or it could be like apple passkey which 00:21:49.740 --> 00:21:51.890 align:start position:0% or it could be like apple passkey which is<00:21:49.860> like<00:21:50.039> one<00:21:50.280> click<00:21:50.640> and<00:21:51.179> they<00:21:51.360> generate<00:21:51.720> a 00:21:51.890 --> 00:21:51.900 align:start position:0% is like one click and they generate a 00:21:51.900 --> 00:21:53.570 align:start position:0% is like one click and they generate a public<00:21:52.020> private<00:21:52.380> key<00:21:52.500> pair<00:21:52.679> for<00:21:52.980> you<00:21:53.159> that's 00:21:53.570 --> 00:21:53.580 align:start position:0% public private key pair for you that's 00:21:53.580 --> 00:21:55.370 align:start position:0% public private key pair for you that's backed<00:21:53.940> up<00:21:54.000> to<00:21:54.120> your<00:21:54.240> iCloud<00:21:54.539> in<00:21:54.840> an<00:21:54.960> encrypted 00:21:55.370 --> 00:21:55.380 align:start position:0% backed up to your iCloud in an encrypted 00:21:55.380 --> 00:21:58.010 align:start position:0% backed up to your iCloud in an encrypted way<00:21:55.500> it<00:21:56.460> could<00:21:56.580> also<00:21:56.880> be<00:21:57.120> like<00:21:57.419> potentially<00:21:57.780> a 00:21:58.010 --> 00:21:58.020 align:start position:0% way it could also be like potentially a 00:21:58.020 --> 00:22:01.029 align:start position:0% way it could also be like potentially a web<00:21:58.140> 2<00:21:58.320> auth<00:21:58.679> method<00:21:59.039> like<00:21:59.640> Discord<00:22:00.000> login 00:22:01.029 --> 00:22:01.039 align:start position:0% web 2 auth method like Discord login 00:22:01.039 --> 00:22:04.070 align:start position:0% web 2 auth method like Discord login anything<00:22:02.039> like<00:22:02.340> that<00:22:02.580> it<00:22:03.360> just<00:22:03.539> needs<00:22:03.780> to<00:22:03.840> be 00:22:04.070 --> 00:22:04.080 align:start position:0% anything like that it just needs to be 00:22:04.080 --> 00:22:06.649 align:start position:0% anything like that it just needs to be basically<00:22:04.700> an<00:22:05.700> authentication<00:22:06.120> method<00:22:06.480> that 00:22:06.649 --> 00:22:06.659 align:start position:0% basically an authentication method that 00:22:06.659 --> 00:22:08.870 align:start position:0% basically an authentication method that can<00:22:06.780> be<00:22:06.900> verified<00:22:07.320> by<00:22:07.679> the<00:22:07.860> lit<00:22:08.100> nodes 00:22:08.870 --> 00:22:08.880 align:start position:0% can be verified by the lit nodes 00:22:08.880 --> 00:22:11.570 align:start position:0% can be verified by the lit nodes every<00:22:09.419> time<00:22:09.659> someone<00:22:09.900> creates<00:22:10.320> a<00:22:10.500> pkp<00:22:10.980> do<00:22:11.400> you 00:22:11.570 --> 00:22:11.580 align:start position:0% every time someone creates a pkp do you 00:22:11.580 --> 00:22:14.450 align:start position:0% every time someone creates a pkp do you generate<00:22:12.000> a<00:22:12.539> new<00:22:12.720> threshold<00:22:13.320> key 00:22:14.450 --> 00:22:14.460 align:start position:0% generate a new threshold key 00:22:14.460 --> 00:22:16.310 align:start position:0% generate a new threshold key and<00:22:14.940> where<00:22:15.120> is<00:22:15.299> that<00:22:15.419> key<00:22:15.600> stored<00:22:16.020> are<00:22:16.200> you 00:22:16.310 --> 00:22:16.320 align:start position:0% and where is that key stored are you 00:22:16.320 --> 00:22:18.169 align:start position:0% and where is that key stored are you spinning<00:22:16.500> up<00:22:16.679> new<00:22:16.919> Cloud<00:22:17.159> nodes<00:22:17.520> to<00:22:18.000> store 00:22:18.169 --> 00:22:18.179 align:start position:0% spinning up new Cloud nodes to store 00:22:18.179 --> 00:22:21.529 align:start position:0% spinning up new Cloud nodes to store those<00:22:18.480> keys<00:22:19.200> so<00:22:19.320> the<00:22:19.740> lit<00:22:20.039> nodes<00:22:20.280> uh<00:22:20.880> each<00:22:21.120> node 00:22:21.529 --> 00:22:21.539 align:start position:0% those keys so the lit nodes uh each node 00:22:21.539 --> 00:22:24.830 align:start position:0% those keys so the lit nodes uh each node support<00:22:21.840> like<00:22:22.440> stores<00:22:23.039> multiple<00:22:23.580> key<00:22:23.820> shares 00:22:24.830 --> 00:22:24.840 align:start position:0% support like stores multiple key shares 00:22:24.840 --> 00:22:26.930 align:start position:0% support like stores multiple key shares um<00:22:24.900> so<00:22:25.140> there's<00:22:25.799> a<00:22:26.100> million<00:22:26.400> keys<00:22:26.700> on<00:22:26.820> the 00:22:26.930 --> 00:22:26.940 align:start position:0% um so there's a million keys on the 00:22:26.940 --> 00:22:30.169 align:start position:0% um so there's a million keys on the network<00:22:27.059> and<00:22:28.020> 100<00:22:28.260> nodes<00:22:28.860> uh<00:22:29.700> each<00:22:29.940> of<00:22:30.120> the 00:22:30.169 --> 00:22:30.179 align:start position:0% network and 100 nodes uh each of the 00:22:30.179 --> 00:22:31.909 align:start position:0% network and 100 nodes uh each of the nodes<00:22:30.360> would<00:22:30.600> store<00:22:30.780> million<00:22:31.260> key<00:22:31.440> shares 00:22:31.909 --> 00:22:31.919 align:start position:0% nodes would store million key shares 00:22:31.919 --> 00:22:34.610 align:start position:0% nodes would store million key shares representing<00:22:32.700> one<00:22:33.360> share<00:22:33.720> from<00:22:33.960> each<00:22:34.260> of<00:22:34.380> the 00:22:34.610 --> 00:22:34.620 align:start position:0% representing one share from each of the 00:22:34.620 --> 00:22:36.770 align:start position:0% representing one share from each of the underlying<00:22:35.280> Cloud<00:22:35.580> wallets<00:22:36.000> or<00:22:36.179> Cloud<00:22:36.360> keys 00:22:36.770 --> 00:22:36.780 align:start position:0% underlying Cloud wallets or Cloud keys 00:22:36.780 --> 00:22:39.230 align:start position:0% underlying Cloud wallets or Cloud keys and<00:22:37.500> what<00:22:37.740> kinds<00:22:38.039> of<00:22:38.100> thresholds<00:22:38.700> are<00:22:39.059> you 00:22:39.230 --> 00:22:39.240 align:start position:0% and what kinds of thresholds are you 00:22:39.240 --> 00:22:42.649 align:start position:0% and what kinds of thresholds are you guys<00:22:39.480> using<00:22:39.960> in<00:22:40.500> production<00:22:40.860> in<00:22:41.520> test<00:22:41.880> like 00:22:42.649 --> 00:22:42.659 align:start position:0% guys using in production in test like 00:22:42.659 --> 00:22:44.810 align:start position:0% guys using in production in test like like<00:22:42.900> the<00:22:43.200> number<00:22:43.440> threshold<00:22:43.980> like<00:22:44.700> yeah 00:22:44.810 --> 00:22:44.820 align:start position:0% like the number threshold like yeah 00:22:44.820 --> 00:22:47.810 align:start position:0% like the number threshold like yeah we're<00:22:45.419> using<00:22:45.900> two-thirds<00:22:46.440> right<00:22:46.620> now<00:22:46.820> and 00:22:47.810 --> 00:22:47.820 align:start position:0% we're using two-thirds right now and 00:22:47.820 --> 00:22:49.130 align:start position:0% we're using two-thirds right now and that's<00:22:48.000> like<00:22:48.120> hard-coded<00:22:48.659> across<00:22:49.080> the 00:22:49.130 --> 00:22:49.140 align:start position:0% that's like hard-coded across the 00:22:49.140 --> 00:22:52.070 align:start position:0% that's like hard-coded across the network<00:22:49.320> so<00:22:49.799> it's<00:22:50.039> not<00:22:50.280> user<00:22:50.580> changeable 00:22:52.070 --> 00:22:52.080 align:start position:0% network so it's not user changeable 00:22:52.080 --> 00:22:55.669 align:start position:0% network so it's not user changeable um<00:22:52.140> and<00:22:52.980> uh<00:22:53.400> yeah<00:22:53.880> and<00:22:54.240> we're<00:22:54.419> using<00:22:54.780> uh<00:22:55.320> you 00:22:55.669 --> 00:22:55.679 align:start position:0% um and uh yeah and we're using uh you 00:22:55.679 --> 00:22:58.669 align:start position:0% um and uh yeah and we're using uh you know<00:22:55.740> ecdsa<00:22:56.460> non-interactive<00:22:57.360> signing<00:22:57.960> on 00:22:58.669 --> 00:22:58.679 align:start position:0% know ecdsa non-interactive signing on 00:22:58.679 --> 00:23:01.909 align:start position:0% know ecdsa non-interactive signing on the<00:22:59.280> um<00:22:59.340> the<00:23:00.240> signing<00:23:00.720> side<00:23:00.900> and<00:23:01.260> then<00:23:01.380> on<00:23:01.620> the 00:23:01.909 --> 00:23:01.919 align:start position:0% the um the signing side and then on the 00:23:01.919 --> 00:23:03.649 align:start position:0% the um the signing side and then on the encryption<00:23:02.700> and<00:23:02.880> decryption<00:23:03.240> side<00:23:03.419> we're 00:23:03.649 --> 00:23:03.659 align:start position:0% encryption and decryption side we're 00:23:03.659 --> 00:23:07.190 align:start position:0% encryption and decryption side we're using<00:23:03.960> BLS<00:23:04.919> keys<00:23:05.940> super<00:23:06.419> we<00:23:06.840> have<00:23:06.960> some<00:23:07.080> more 00:23:07.190 --> 00:23:07.200 align:start position:0% using BLS keys super we have some more 00:23:07.200 --> 00:23:08.510 align:start position:0% using BLS keys super we have some more questions<00:23:07.380> in<00:23:07.740> the<00:23:07.860> middle<00:23:07.919> of<00:23:08.100> our<00:23:08.220> area 00:23:08.510 --> 00:23:08.520 align:start position:0% questions in the middle of our area 00:23:08.520 --> 00:23:09.590 align:start position:0% questions in the middle of our area still<00:23:08.760> do<00:23:08.940> you<00:23:09.000> mind<00:23:09.059> if<00:23:09.179> I<00:23:09.299> have<00:23:09.360> one<00:23:09.480> more 00:23:09.590 --> 00:23:09.600 align:start position:0% still do you mind if I have one more 00:23:09.600 --> 00:23:11.630 align:start position:0% still do you mind if I have one more question<00:23:09.780> uh<00:23:10.500> that's<00:23:10.860> our<00:23:11.100> fourth<00:23:11.340> one<00:23:11.400> right 00:23:11.630 --> 00:23:11.640 align:start position:0% question uh that's our fourth one right 00:23:11.640 --> 00:23:13.909 align:start position:0% question uh that's our fourth one right super<00:23:12.419> uh<00:23:13.080> what<00:23:13.320> are<00:23:13.440> your<00:23:13.500> plans<00:23:13.679> for 00:23:13.909 --> 00:23:13.919 align:start position:0% super uh what are your plans for 00:23:13.919 --> 00:23:16.490 align:start position:0% super uh what are your plans for decentralization<00:23:14.580> and<00:23:15.059> how<00:23:15.480> do<00:23:15.659> you<00:23:15.840> plan<00:23:16.140> to 00:23:16.490 --> 00:23:16.500 align:start position:0% decentralization and how do you plan to 00:23:16.500 --> 00:23:18.649 align:start position:0% decentralization and how do you plan to grow<00:23:16.740> this<00:23:17.039> network<00:23:17.220> it<00:23:18.000> sounds<00:23:18.120> like<00:23:18.299> it's<00:23:18.480> a 00:23:18.649 --> 00:23:18.659 align:start position:0% grow this network it sounds like it's a 00:23:18.659 --> 00:23:21.110 align:start position:0% grow this network it sounds like it's a pretty<00:23:18.780> fixed<00:23:19.260> set<00:23:19.620> and<00:23:20.220> you<00:23:20.340> do<00:23:20.460> no<00:23:20.640> rotations 00:23:21.110 --> 00:23:21.120 align:start position:0% pretty fixed set and you do no rotations 00:23:21.120 --> 00:23:23.090 align:start position:0% pretty fixed set and you do no rotations well<00:23:22.020> so<00:23:22.140> there's<00:23:22.380> this<00:23:22.559> notion<00:23:22.860> of<00:23:22.980> the 00:23:23.090 --> 00:23:23.100 align:start position:0% well so there's this notion of the 00:23:23.100 --> 00:23:26.270 align:start position:0% well so there's this notion of the proactive<00:23:23.460> secret<00:23:23.640> fairing<00:23:24.659> um<00:23:24.780> which<00:23:24.960> is<00:23:25.280> not 00:23:26.270 --> 00:23:26.280 align:start position:0% proactive secret fairing um which is not 00:23:26.280 --> 00:23:27.890 align:start position:0% proactive secret fairing um which is not I<00:23:26.640> guess<00:23:26.760> not<00:23:27.000> quite<00:23:27.240> a<00:23:27.360> rotation<00:23:27.659> because 00:23:27.890 --> 00:23:27.900 align:start position:0% I guess not quite a rotation because 00:23:27.900 --> 00:23:30.350 align:start position:0% I guess not quite a rotation because it's<00:23:28.020> the<00:23:28.200> same<00:23:28.380> underlying<00:23:28.919> secret 00:23:30.350 --> 00:23:30.360 align:start position:0% it's the same underlying secret 00:23:30.360 --> 00:23:32.630 align:start position:0% it's the same underlying secret um but<00:23:31.080> yeah<00:23:31.440> some<00:23:31.740> of<00:23:31.860> our<00:23:32.220> Cutting<00:23:32.580> Edge 00:23:32.630 --> 00:23:32.640 align:start position:0% um but yeah some of our Cutting Edge 00:23:32.640 --> 00:23:35.270 align:start position:0% um but yeah some of our Cutting Edge work<00:23:32.940> is<00:23:33.240> right<00:23:33.539> at<00:23:33.960> the<00:23:34.260> notion<00:23:34.620> of<00:23:34.799> changing 00:23:35.270 --> 00:23:35.280 align:start position:0% work is right at the notion of changing 00:23:35.280 --> 00:23:37.430 align:start position:0% work is right at the notion of changing the<00:23:35.460> threshold<00:23:35.820> oh<00:23:36.360> it's<00:23:36.600> just<00:23:36.780> people<00:23:37.020> makes 00:23:37.430 --> 00:23:37.440 align:start position:0% the threshold oh it's just people makes 00:23:37.440 --> 00:23:38.750 align:start position:0% the threshold oh it's just people makes the<00:23:37.559> network<00:23:37.679> be<00:23:37.919> able<00:23:38.039> to<00:23:38.100> become<00:23:38.340> like<00:23:38.520> more 00:23:38.750 --> 00:23:38.760 align:start position:0% the network be able to become like more 00:23:38.760 --> 00:23:40.970 align:start position:0% the network be able to become like more Dynamic<00:23:39.120> over<00:23:39.299> time<00:23:39.600> but<00:23:40.380> currently<00:23:40.620> there<00:23:40.799> is 00:23:40.970 --> 00:23:40.980 align:start position:0% Dynamic over time but currently there is 00:23:40.980 --> 00:23:43.549 align:start position:0% Dynamic over time but currently there is the<00:23:41.100> capacity<00:23:41.520> for<00:23:42.120> new<00:23:42.659> nodes<00:23:42.960> to<00:23:43.200> join<00:23:43.380> the 00:23:43.549 --> 00:23:43.559 align:start position:0% the capacity for new nodes to join the 00:23:43.559 --> 00:23:46.010 align:start position:0% the capacity for new nodes to join the network<00:23:43.740> and<00:23:44.400> for<00:23:44.640> the<00:23:44.880> key<00:23:45.059> to<00:23:45.299> be<00:23:45.419> refreshed 00:23:46.010 --> 00:23:46.020 align:start position:0% network and for the key to be refreshed 00:23:46.020 --> 00:23:48.529 align:start position:0% network and for the key to be refreshed creating<00:23:46.380> those<00:23:46.620> new<00:23:46.860> shares<00:23:47.280> in<00:23:47.640> Epoch<00:23:48.179> two 00:23:48.529 --> 00:23:48.539 align:start position:0% creating those new shares in Epoch two 00:23:48.539 --> 00:23:50.330 align:start position:0% creating those new shares in Epoch two three<00:23:48.780> four<00:23:49.020> and<00:23:49.200> so<00:23:49.380> on<00:23:49.500> and<00:23:50.159> then 00:23:50.330 --> 00:23:50.340 align:start position:0% three four and so on and then 00:23:50.340 --> 00:23:52.970 align:start position:0% three four and so on and then practically<00:23:50.820> in<00:23:51.179> terms<00:23:51.419> of<00:23:51.600> the<00:23:51.900> plan 00:23:52.970 --> 00:23:52.980 align:start position:0% practically in terms of the plan 00:23:52.980 --> 00:23:54.710 align:start position:0% practically in terms of the plan um<00:23:53.039> by<00:23:53.280> the<00:23:53.400> end<00:23:53.520> of<00:23:53.580> the<00:23:53.760> year<00:23:53.820> this<00:23:54.480> network 00:23:54.710 --> 00:23:54.720 align:start position:0% um by the end of the year this network 00:23:54.720 --> 00:23:57.529 align:start position:0% um by the end of the year this network will<00:23:55.020> be<00:23:55.140> up<00:23:55.320> with<00:23:55.559> a<00:23:56.100> handful<00:23:56.460> of<00:23:56.700> named<00:23:57.240> node 00:23:57.529 --> 00:23:57.539 align:start position:0% will be up with a handful of named node 00:23:57.539 --> 00:23:59.930 align:start position:0% will be up with a handful of named node operators<00:23:58.020> and<00:23:58.740> then<00:23:58.860> those<00:23:59.159> node<00:23:59.400> operators 00:23:59.930 --> 00:23:59.940 align:start position:0% operators and then those node operators 00:23:59.940 --> 00:24:02.149 align:start position:0% operators and then those node operators are<00:24:00.360> functionally<00:24:00.780> a<00:24:01.080> Dao<00:24:01.380> of<00:24:01.500> sorts<00:24:01.919> that 00:24:02.149 --> 00:24:02.159 align:start position:0% are functionally a Dao of sorts that 00:24:02.159 --> 00:24:05.149 align:start position:0% are functionally a Dao of sorts that decide<00:24:02.580> who<00:24:03.179> comes<00:24:03.419> in<00:24:03.539> and<00:24:03.659> who<00:24:03.900> comes<00:24:04.200> out<00:24:04.320> uh 00:24:05.149 --> 00:24:05.159 align:start position:0% decide who comes in and who comes out uh 00:24:05.159 --> 00:24:07.800 align:start position:0% decide who comes in and who comes out uh to<00:24:05.400> the<00:24:05.580> system<00:24:06.240> thanks<00:24:06.720> everybody<00:24:06.840> Applause 00:24:07.800 --> 00:24:07.810 align:start position:0% to the system thanks everybody Applause 00:24:07.810 --> 00:24:12.670 align:start position:0% to the system thanks everybody Applause [Applause]