WEBVTT Kind: captions Language: en 00:00:01.070 --> 00:00:11.400 align:start position:0% [Applause] 00:00:11.400 --> 00:00:11.410 align:start position:0% 00:00:11.410 --> 00:00:15.190 align:start position:0% how<00:00:12.410> many<00:00:12.590> of<00:00:12.710> you<00:00:12.920> have<00:00:13.190> built<00:00:13.400> an<00:00:13.580> app<00:00:14.200> been 00:00:15.190 --> 00:00:15.200 align:start position:0% how many of you have built an app been 00:00:15.200 --> 00:00:18.880 align:start position:0% how many of you have built an app been used<00:00:15.410> by<00:00:15.530> thousands<00:00:16.100> of<00:00:16.220> users<00:00:17.619> okay 00:00:18.880 --> 00:00:18.890 align:start position:0% used by thousands of users okay 00:00:18.890 --> 00:00:21.580 align:start position:0% used by thousands of users okay amazing<00:00:19.790> guy<00:00:20.300> could<00:00:20.510> develop<00:00:20.720> a<00:00:20.930> problem<00:00:21.140> keep 00:00:21.580 --> 00:00:21.590 align:start position:0% amazing guy could develop a problem keep 00:00:21.590 --> 00:00:22.600 align:start position:0% amazing guy could develop a problem keep your<00:00:21.710> hands<00:00:21.860> up<00:00:21.980> and<00:00:22.100> you<00:00:22.220> built<00:00:22.460> a 00:00:22.600 --> 00:00:22.610 align:start position:0% your hands up and you built a 00:00:22.610 --> 00:00:25.150 align:start position:0% your hands up and you built a decentralized<00:00:23.450> app<00:00:23.689> where<00:00:23.990> free<00:00:24.260> app<00:00:24.470> has 00:00:25.150 --> 00:00:25.160 align:start position:0% decentralized app where free app has 00:00:25.160 --> 00:00:28.570 align:start position:0% decentralized app where free app has been<00:00:25.369> used<00:00:25.550> by<00:00:25.610> thousands<00:00:26.090> of<00:00:26.150> users<00:00:27.190> great<00:00:28.190> we 00:00:28.570 --> 00:00:28.580 align:start position:0% been used by thousands of users great we 00:00:28.580 --> 00:00:30.670 align:start position:0% been used by thousands of users great we still<00:00:28.789> have<00:00:28.970> a<00:00:29.000> few<00:00:29.210> minutes 00:00:30.670 --> 00:00:30.680 align:start position:0% still have a few minutes 00:00:30.680 --> 00:00:33.820 align:start position:0% still have a few minutes this<00:00:31.070> talk<00:00:31.280> is<00:00:31.310> designed<00:00:31.760> for<00:00:32.119> developers<00:00:32.870> who 00:00:33.820 --> 00:00:33.830 align:start position:0% this talk is designed for developers who 00:00:33.830 --> 00:00:39.010 align:start position:0% this talk is designed for developers who may<00:00:34.400> be<00:00:34.460> due<00:00:34.670> to<00:00:34.720> read<00:00:35.720> free<00:00:35.870> space<00:00:36.140> and<00:00:37.390> I<00:00:38.390> want 00:00:39.010 --> 00:00:39.020 align:start position:0% may be due to read free space and I want 00:00:39.020 --> 00:00:40.299 align:start position:0% may be due to read free space and I want to<00:00:39.110> share<00:00:39.260> some<00:00:39.500> of<00:00:39.620> the<00:00:39.710> lessons<00:00:39.739> we've 00:00:40.299 --> 00:00:40.309 align:start position:0% to share some of the lessons we've 00:00:40.309 --> 00:00:43.869 align:start position:0% to share some of the lessons we've learned<00:00:40.340> from<00:00:40.760> building<00:00:41.500> origin<00:00:42.500> so<00:00:42.949> for<00:00:43.699> both 00:00:43.869 --> 00:00:43.879 align:start position:0% learned from building origin so for both 00:00:43.879 --> 00:00:47.200 align:start position:0% learned from building origin so for both of<00:00:44.059> you<00:00:44.180> who<00:00:44.449> are<00:00:44.510> not<00:00:44.960> familiar<00:00:45.489> origin<00:00:46.489> is<00:00:46.640> a 00:00:47.200 --> 00:00:47.210 align:start position:0% of you who are not familiar origin is a 00:00:47.210 --> 00:00:49.509 align:start position:0% of you who are not familiar origin is a decentralized<00:00:47.780> market<00:00:48.470> place<00:00:48.860> on<00:00:49.190> the 00:00:49.509 --> 00:00:49.519 align:start position:0% decentralized market place on the 00:00:49.519 --> 00:00:51.660 align:start position:0% decentralized market place on the blockchain<00:00:49.760> for<00:00:50.330> enabling<00:00:50.500> peer-to-peer 00:00:51.660 --> 00:00:51.670 align:start position:0% blockchain for enabling peer-to-peer 00:00:51.670 --> 00:00:54.910 align:start position:0% blockchain for enabling peer-to-peer commerce<00:00:52.670> and<00:00:53.479> without<00:00:53.809> any<00:00:54.140> middleman<00:00:54.620> or 00:00:54.910 --> 00:00:54.920 align:start position:0% commerce and without any middleman or 00:00:54.920 --> 00:00:57.490 align:start position:0% commerce and without any middleman or intermediaries<00:00:55.809> we've<00:00:56.809> been<00:00:56.960> working<00:00:57.260> on<00:00:57.379> it 00:00:57.490 --> 00:00:57.500 align:start position:0% intermediaries we've been working on it 00:00:57.500 --> 00:00:59.289 align:start position:0% intermediaries we've been working on it for<00:00:57.530> about<00:00:58.370> two<00:00:58.729> years<00:00:58.760> now 00:00:59.289 --> 00:00:59.299 align:start position:0% for about two years now 00:00:59.299 --> 00:01:01.780 align:start position:0% for about two years now our<00:01:00.199> team<00:01:00.530> includes<00:01:00.890> people<00:01:01.100> like<00:01:01.250> one<00:01:01.640> of<00:01:01.699> the 00:01:01.780 --> 00:01:01.790 align:start position:0% our team includes people like one of the 00:01:01.790 --> 00:01:02.649 align:start position:0% our team includes people like one of the founders<00:01:02.120> of<00:01:02.239> PayPal 00:01:02.649 --> 00:01:02.659 align:start position:0% founders of PayPal 00:01:02.659 --> 00:01:04.780 align:start position:0% founders of PayPal the<00:01:02.930> first<00:01:03.140> special<00:01:03.290> YouTube<00:01:04.250> bunch<00:01:04.670> of 00:01:04.780 --> 00:01:04.790 align:start position:0% the first special YouTube bunch of 00:01:04.790 --> 00:01:06.520 align:start position:0% the first special YouTube bunch of engineering<00:01:05.210> managers<00:01:05.600> from<00:01:05.690> Google<00:01:06.229> and 00:01:06.520 --> 00:01:06.530 align:start position:0% engineering managers from Google and 00:01:06.530 --> 00:01:09.940 align:start position:0% engineering managers from Google and Dropbox<00:01:07.340> and<00:01:08.090> we've<00:01:08.690> got<00:01:08.930> as<00:01:09.170> of<00:01:09.380> today<00:01:09.680> we 00:01:09.940 --> 00:01:09.950 align:start position:0% Dropbox and we've got as of today we 00:01:09.950 --> 00:01:12.609 align:start position:0% Dropbox and we've got as of today we have<00:01:09.979> of<00:01:10.159> 69<00:01:10.670> thousand<00:01:11.150> unique<00:01:11.900> wallets<00:01:12.290> that 00:01:12.609 --> 00:01:12.619 align:start position:0% have of 69 thousand unique wallets that 00:01:12.619 --> 00:01:15.220 align:start position:0% have of 69 thousand unique wallets that are<00:01:12.740> using<00:01:13.070> the<00:01:13.700> marketplace<00:01:14.180> and<00:01:14.450> so<00:01:15.050> I'm 00:01:15.220 --> 00:01:15.230 align:start position:0% are using the marketplace and so I'm 00:01:15.230 --> 00:01:16.840 align:start position:0% are using the marketplace and so I'm going<00:01:15.440> to<00:01:15.500> share<00:01:15.770> some<00:01:16.310> of<00:01:16.340> the<00:01:16.490> tips<00:01:16.700> and 00:01:16.840 --> 00:01:16.850 align:start position:0% going to share some of the tips and 00:01:16.850 --> 00:01:18.400 align:start position:0% going to share some of the tips and tricks<00:01:16.940> that<00:01:17.240> we've<00:01:17.390> learned<00:01:17.630> from<00:01:17.750> from 00:01:18.400 --> 00:01:18.410 align:start position:0% tricks that we've learned from from 00:01:18.410 --> 00:01:20.830 align:start position:0% tricks that we've learned from from building<00:01:18.740> that<00:01:18.920> and<00:01:19.790> are<00:01:19.910> relying<00:01:20.330> heavily<00:01:20.600> on 00:01:20.830 --> 00:01:20.840 align:start position:0% building that and are relying heavily on 00:01:20.840 --> 00:01:23.320 align:start position:0% building that and are relying heavily on my<00:01:21.380> experience<00:01:21.800> fair<00:01:21.980> for<00:01:22.940> some<00:01:23.120> of<00:01:23.240> the 00:01:23.320 --> 00:01:23.330 align:start position:0% my experience fair for some of the 00:01:23.330 --> 00:01:25.540 align:start position:0% my experience fair for some of the examples<00:01:23.810> on<00:01:24.020> how<00:01:24.050> you<00:01:24.290> can<00:01:24.590> apply<00:01:24.710> these 00:01:25.540 --> 00:01:25.550 align:start position:0% examples on how you can apply these 00:01:25.550 --> 00:01:29.820 align:start position:0% examples on how you can apply these design<00:01:26.000> patterns<00:01:26.210> to<00:01:26.780> your<00:01:27.260> own<00:01:27.500> applications 00:01:29.820 --> 00:01:29.830 align:start position:0% design patterns to your own applications 00:01:29.830 --> 00:01:32.620 align:start position:0% design patterns to your own applications so<00:01:30.830> what's<00:01:31.280> unique<00:01:31.490> about<00:01:31.790> Bennett<00:01:32.240> building 00:01:32.620 --> 00:01:32.630 align:start position:0% so what's unique about Bennett building 00:01:32.630 --> 00:01:34.480 align:start position:0% so what's unique about Bennett building on<00:01:32.900> inferior<00:01:33.380> well<00:01:33.830> some<00:01:33.980> of<00:01:34.010> these<00:01:34.130> are<00:01:34.280> quite 00:01:34.480 --> 00:01:34.490 align:start position:0% on inferior well some of these are quite 00:01:34.490 --> 00:01:37.660 align:start position:0% on inferior well some of these are quite obvious<00:01:34.910> gasps<00:01:36.040> it's<00:01:37.040> not<00:01:37.220> something<00:01:37.550> you 00:01:37.660 --> 00:01:37.670 align:start position:0% obvious gasps it's not something you 00:01:37.670 --> 00:01:39.190 align:start position:0% obvious gasps it's not something you have 00:01:39.190 --> 00:01:39.200 align:start position:0% have 00:01:39.200 --> 00:01:41.990 align:start position:0% have application<00:01:40.340> you<00:01:41.340> don't<00:01:41.520> have<00:01:41.640> to<00:01:41.759> worry 00:01:41.990 --> 00:01:42.000 align:start position:0% application you don't have to worry 00:01:42.000 --> 00:01:42.950 align:start position:0% application you don't have to worry about<00:01:42.060> the<00:01:42.330> mutability 00:01:42.950 --> 00:01:42.960 align:start position:0% about the mutability 00:01:42.960 --> 00:01:45.260 align:start position:0% about the mutability as<00:01:43.110> developers<00:01:43.979> one<00:01:44.220> thing<00:01:44.490> we<00:01:44.909> know<00:01:45.030> for<00:01:45.210> sure 00:01:45.260 --> 00:01:45.270 align:start position:0% as developers one thing we know for sure 00:01:45.270 --> 00:01:46.280 align:start position:0% as developers one thing we know for sure is<00:01:45.570> you're<00:01:45.659> not<00:01:45.750> going<00:01:45.900> to<00:01:45.990> get<00:01:46.140> everything 00:01:46.280 --> 00:01:46.290 align:start position:0% is you're not going to get everything 00:01:46.290 --> 00:01:48.859 align:start position:0% is you're not going to get everything right<00:01:46.530> first<00:01:47.070> try<00:01:47.310> but<00:01:48.060> how<00:01:48.180> do<00:01:48.240> you<00:01:48.420> deal<00:01:48.840> with 00:01:48.859 --> 00:01:48.869 align:start position:0% right first try but how do you deal with 00:01:48.869 --> 00:01:50.450 align:start position:0% right first try but how do you deal with that<00:01:49.020> in<00:01:49.320> wrong<00:01:49.470> way<00:01:49.740> you<00:01:49.799> can't<00:01:50.159> change 00:01:50.450 --> 00:01:50.460 align:start position:0% that in wrong way you can't change 00:01:50.460 --> 00:01:51.410 align:start position:0% that in wrong way you can't change anything 00:01:51.410 --> 00:01:51.420 align:start position:0% anything 00:01:51.420 --> 00:01:53.330 align:start position:0% anything in<00:01:51.960> fact<00:01:52.170> it's<00:01:52.409> written<00:01:52.619> to<00:01:52.920> the<00:01:53.100> blockchain 00:01:53.330 --> 00:01:53.340 align:start position:0% in fact it's written to the blockchain 00:01:53.340 --> 00:01:55.609 align:start position:0% in fact it's written to the blockchain for<00:01:53.729> all<00:01:53.790> eternity<00:01:54.090> and<00:01:54.780> how<00:01:55.229> do<00:01:55.289> we<00:01:55.380> deal<00:01:55.590> with 00:01:55.609 --> 00:01:55.619 align:start position:0% for all eternity and how do we deal with 00:01:55.619 --> 00:01:57.740 align:start position:0% for all eternity and how do we deal with some<00:01:55.890> of<00:01:55.920> our<00:01:56.100> unfamiliar<00:01:56.789> usability 00:01:57.740 --> 00:01:57.750 align:start position:0% some of our unfamiliar usability 00:01:57.750 --> 00:02:01.279 align:start position:0% some of our unfamiliar usability challenges<00:01:58.320> of<00:01:58.729> the<00:01:59.729> blockchain<00:02:00.289> because 00:02:01.279 --> 00:02:01.289 align:start position:0% challenges of the blockchain because 00:02:01.289 --> 00:02:03.109 align:start position:0% challenges of the blockchain because like<00:02:01.439> why<00:02:01.649> do<00:02:01.710> we<00:02:01.799> need<00:02:01.950> gas<00:02:02.159> right<00:02:02.610> well<00:02:02.939> it's 00:02:03.109 --> 00:02:03.119 align:start position:0% like why do we need gas right well it's 00:02:03.119 --> 00:02:06.310 align:start position:0% like why do we need gas right well it's fairly<00:02:03.420> to<00:02:04.070> allocate<00:02:05.070> scarce<00:02:05.340> resources 00:02:06.310 --> 00:02:06.320 align:start position:0% fairly to allocate scarce resources 00:02:06.320 --> 00:02:09.710 align:start position:0% fairly to allocate scarce resources against<00:02:07.320> miners<00:02:07.770> an<00:02:07.950> incentive<00:02:08.489> to<00:02:08.759> secure<00:02:09.690> a 00:02:09.710 --> 00:02:09.720 align:start position:0% against miners an incentive to secure a 00:02:09.720 --> 00:02:12.680 align:start position:0% against miners an incentive to secure a network<00:02:10.250> and<00:02:11.250> this<00:02:11.459> is<00:02:11.610> deterrent<00:02:12.239> for<00:02:12.390> abuse 00:02:12.680 --> 00:02:12.690 align:start position:0% network and this is deterrent for abuse 00:02:12.690 --> 00:02:13.970 align:start position:0% network and this is deterrent for abuse it's<00:02:12.989> actually<00:02:13.230> this<00:02:13.319> really<00:02:13.560> important 00:02:13.970 --> 00:02:13.980 align:start position:0% it's actually this really important 00:02:13.980 --> 00:02:19.610 align:start position:0% it's actually this really important concept<00:02:15.050> but<00:02:16.050> also<00:02:16.230> it<00:02:16.470> really<00:02:16.890> sucks<00:02:18.620> users 00:02:19.610 --> 00:02:19.620 align:start position:0% concept but also it really sucks users 00:02:19.620 --> 00:02:21.559 align:start position:0% concept but also it really sucks users aren't<00:02:19.860> used<00:02:20.010> to<00:02:20.100> paint<00:02:20.370> the<00:02:20.580> gas<00:02:20.790> you've<00:02:21.330> got 00:02:21.559 --> 00:02:21.569 align:start position:0% aren't used to paint the gas you've got 00:02:21.569 --> 00:02:24.680 align:start position:0% aren't used to paint the gas you've got things<00:02:21.840> like<00:02:22.250> tammer<00:02:23.250> and<00:02:23.760> crypto<00:02:24.090> kitties<00:02:24.450> or 00:02:24.680 --> 00:02:24.690 align:start position:0% things like tammer and crypto kitties or 00:02:24.690 --> 00:02:26.360 align:start position:0% things like tammer and crypto kitties or fairway<00:02:25.110> and<00:02:25.230> clogging<00:02:25.620> up<00:02:25.709> the<00:02:25.739> network<00:02:26.160> and 00:02:26.360 --> 00:02:26.370 align:start position:0% fairway and clogging up the network and 00:02:26.370 --> 00:02:28.670 align:start position:0% fairway and clogging up the network and making<00:02:26.640> your<00:02:27.030> app<00:02:27.269> really<00:02:27.780> expensive<00:02:28.200> or 00:02:28.670 --> 00:02:28.680 align:start position:0% making your app really expensive or 00:02:28.680 --> 00:02:31.160 align:start position:0% making your app really expensive or broken<00:02:29.130> to<00:02:29.280> use<00:02:29.519> and<00:02:30.060> then<00:02:30.630> most<00:02:30.840> people<00:02:30.989> on 00:02:31.160 --> 00:02:31.170 align:start position:0% broken to use and then most people on 00:02:31.170 --> 00:02:33.740 align:start position:0% broken to use and then most people on this<00:02:31.230> planet<00:02:31.410> don't<00:02:31.860> have<00:02:32.220> a<00:02:32.250> fake<00:02:32.670> so<00:02:33.510> how<00:02:33.690> do 00:02:33.740 --> 00:02:33.750 align:start position:0% this planet don't have a fake so how do 00:02:33.750 --> 00:02:35.870 align:start position:0% this planet don't have a fake so how do you<00:02:33.900> deal<00:02:34.110> with<00:02:34.140> that<00:02:34.260> and<00:02:35.250> when<00:02:35.430> we<00:02:35.459> look<00:02:35.700> at 00:02:35.870 --> 00:02:35.880 align:start position:0% you deal with that and when we look at 00:02:35.880 --> 00:02:37.490 align:start position:0% you deal with that and when we look at what<00:02:36.330> we've<00:02:36.540> spent<00:02:36.840> most<00:02:37.200> of<00:02:37.319> our<00:02:37.440> time 00:02:37.490 --> 00:02:37.500 align:start position:0% what we've spent most of our time 00:02:37.500 --> 00:02:40.100 align:start position:0% what we've spent most of our time working<00:02:37.980> on<00:02:38.190> at<00:02:38.430> origin<00:02:38.880> over<00:02:39.480> the<00:02:39.780> last<00:02:39.900> two 00:02:40.100 --> 00:02:40.110 align:start position:0% working on at origin over the last two 00:02:40.110 --> 00:02:43.250 align:start position:0% working on at origin over the last two years<00:02:40.140> it's<00:02:41.130> all<00:02:41.459> related<00:02:42.000> to<00:02:42.030> that<00:02:42.180> or<00:02:42.720> one<00:02:43.170> of 00:02:43.250 --> 00:02:43.260 align:start position:0% years it's all related to that or one of 00:02:43.260 --> 00:02:44.900 align:start position:0% years it's all related to that or one of them<00:02:43.380> a<00:02:43.560> lot<00:02:43.950> of<00:02:44.070> these<00:02:44.130> problems<00:02:44.459> are<00:02:44.549> related 00:02:44.900 --> 00:02:44.910 align:start position:0% them a lot of these problems are related 00:02:44.910 --> 00:02:47.720 align:start position:0% them a lot of these problems are related to<00:02:45.030> this<00:02:45.690> concept<00:02:46.170> of<00:02:46.530> gas<00:02:46.799> how<00:02:47.519> do<00:02:47.579> we 00:02:47.720 --> 00:02:47.730 align:start position:0% to this concept of gas how do we 00:02:47.730 --> 00:02:49.789 align:start position:0% to this concept of gas how do we minimize<00:02:48.000> the<00:02:48.390> gas<00:02:48.570> cost<00:02:48.870> or<00:02:49.109> how<00:02:49.260> to<00:02:49.320> get<00:02:49.530> rid 00:02:49.789 --> 00:02:49.799 align:start position:0% minimize the gas cost or how to get rid 00:02:49.799 --> 00:02:53.760 align:start position:0% minimize the gas cost or how to get rid of<00:02:49.829> it<00:02:50.010> altogether 00:02:53.760 --> 00:02:53.770 align:start position:0% 00:02:53.770 --> 00:02:56.070 align:start position:0% so<00:02:54.340> the<00:02:54.490> first<00:02:54.700> thing<00:02:54.850> you<00:02:54.940> can<00:02:55.000> do<00:02:55.270> is<00:02:55.570> just 00:02:56.070 --> 00:02:56.080 align:start position:0% so the first thing you can do is just 00:02:56.080 --> 00:02:59.840 align:start position:0% so the first thing you can do is just fill<00:02:56.440> ins<00:02:56.590> the<00:02:56.860> word<00:02:57.040> as<00:02:57.370> much<00:02:57.580> data<00:02:57.850> contain 00:02:59.840 --> 00:02:59.850 align:start position:0% fill ins the word as much data contain 00:02:59.850 --> 00:03:02.790 align:start position:0% fill ins the word as much data contain what<00:03:00.850> you<00:03:00.970> can<00:03:01.180> do<00:03:01.360> here<00:03:01.660> is<00:03:01.690> I<00:03:02.050> said<00:03:02.320> strong<00:03:02.650> on 00:03:02.790 --> 00:03:02.800 align:start position:0% what you can do here is I said strong on 00:03:02.800 --> 00:03:04.080 align:start position:0% what you can do here is I said strong on a<00:03:02.830> Content<00:03:03.280> Hatcher 00:03:04.080 --> 00:03:04.090 align:start position:0% a Content Hatcher 00:03:04.090 --> 00:03:07.110 align:start position:0% a Content Hatcher this<00:03:04.390> is<00:03:04.480> a<00:03:04.570> very<00:03:04.870> basic<00:03:05.230> technique<00:03:05.970> which<00:03:06.970> we 00:03:07.110 --> 00:03:07.120 align:start position:0% this is a very basic technique which we 00:03:07.120 --> 00:03:10.770 align:start position:0% this is a very basic technique which we use<00:03:07.360> for<00:03:08.100> storing<00:03:09.100> all<00:03:09.220> of<00:03:09.340> the<00:03:09.520> data<00:03:09.730> that<00:03:10.180> our 00:03:10.770 --> 00:03:10.780 align:start position:0% use for storing all of the data that our 00:03:10.780 --> 00:03:13.830 align:start position:0% use for storing all of the data that our application<00:03:11.500> needs<00:03:11.680> we<00:03:11.920> store<00:03:12.160> on<00:03:12.460> ipfs<00:03:13.270> the 00:03:13.830 --> 00:03:13.840 align:start position:0% application needs we store on ipfs the 00:03:13.840 --> 00:03:17.220 align:start position:0% application needs we store on ipfs the content-addressable<00:03:15.060> peer-to-peer<00:03:16.230> file 00:03:17.220 --> 00:03:17.230 align:start position:0% content-addressable peer-to-peer file 00:03:17.230 --> 00:03:20.250 align:start position:0% content-addressable peer-to-peer file system<00:03:17.740> and<00:03:17.980> this<00:03:18.880> is<00:03:18.940> still<00:03:19.600> secure<00:03:19.870> because 00:03:20.250 --> 00:03:20.260 align:start position:0% system and this is still secure because 00:03:20.260 --> 00:03:23.150 align:start position:0% system and this is still secure because if<00:03:20.620> you<00:03:20.710> change<00:03:20.920> one<00:03:21.430> bite<00:03:21.700> of<00:03:21.910> that<00:03:22.000> content 00:03:23.150 --> 00:03:23.160 align:start position:0% if you change one bite of that content 00:03:23.160 --> 00:03:25.980 align:start position:0% if you change one bite of that content it<00:03:24.160> will<00:03:24.700> get<00:03:24.820> a<00:03:24.850> completely<00:03:25.390> different<00:03:25.600> hash 00:03:25.980 --> 00:03:25.990 align:start position:0% it will get a completely different hash 00:03:25.990 --> 00:03:29.640 align:start position:0% it will get a completely different hash mr<00:03:26.890> allows<00:03:27.160> us<00:03:27.400> to<00:03:27.730> save<00:03:28.420> a<00:03:28.720> lot<00:03:28.930> of<00:03:28.990> money<00:03:29.080> on 00:03:29.640 --> 00:03:29.650 align:start position:0% mr allows us to save a lot of money on 00:03:29.650 --> 00:03:32.670 align:start position:0% mr allows us to save a lot of money on gas<00:03:29.890> goes<00:03:30.480> by<00:03:31.480> storing<00:03:32.110> just<00:03:32.350> content 00:03:32.670 --> 00:03:32.680 align:start position:0% gas goes by storing just content 00:03:32.680 --> 00:03:34.710 align:start position:0% gas goes by storing just content Harrison<00:03:33.040> instead<00:03:33.430> now<00:03:34.150> you<00:03:34.240> do<00:03:34.390> have<00:03:34.540> to 00:03:34.710 --> 00:03:34.720 align:start position:0% Harrison instead now you do have to 00:03:34.720 --> 00:03:37.680 align:start position:0% Harrison instead now you do have to worry<00:03:34.960> about<00:03:35.460> the<00:03:36.460> deed<00:03:36.880> of<00:03:36.910> surviving<00:03:37.540> might 00:03:37.680 --> 00:03:37.690 align:start position:0% worry about the deed of surviving might 00:03:37.690 --> 00:03:41.190 align:start position:0% worry about the deed of surviving might have<00:03:38.350> a<00:03:38.380> risk<00:03:39.010> of<00:03:39.190> data<00:03:39.520> loss<00:03:39.780> if<00:03:40.780> you're<00:03:41.020> not 00:03:41.190 --> 00:03:41.200 align:start position:0% have a risk of data loss if you're not 00:03:41.200 --> 00:03:44.130 align:start position:0% have a risk of data loss if you're not replicating<00:03:42.190> that<00:03:42.310> data<00:03:42.520> there's<00:03:43.390> no<00:03:43.570> risk<00:03:43.990> of 00:03:44.130 --> 00:03:44.140 align:start position:0% replicating that data there's no risk of 00:03:44.140 --> 00:03:45.540 align:start position:0% replicating that data there's no risk of that<00:03:44.260> gonna<00:03:44.500> be<00:03:44.710> tampered<00:03:45.370> with 00:03:45.540 --> 00:03:45.550 align:start position:0% that gonna be tampered with 00:03:45.550 --> 00:03:49.770 align:start position:0% that gonna be tampered with it's<00:03:45.700> still<00:03:45.910> secure<00:03:47.820> so<00:03:48.820> take<00:03:49.060> a<00:03:49.090> quick<00:03:49.420> look 00:03:49.770 --> 00:03:49.780 align:start position:0% it's still secure so take a quick look 00:03:49.780 --> 00:03:53.300 align:start position:0% it's still secure so take a quick look at<00:03:50.140> what<00:03:50.860> our<00:03:50.890> tap<00:03:51.280> looks<00:03:51.610> like<00:03:51.850> so<00:03:52.750> this<00:03:52.900> is 00:03:53.300 --> 00:03:53.310 align:start position:0% at what our tap looks like so this is 00:03:53.310 --> 00:03:56.400 align:start position:0% at what our tap looks like so this is the<00:03:54.310> origin<00:03:54.690> marketplace<00:03:55.690> this<00:03:55.930> is<00:03:56.110> live<00:03:56.380> on 00:03:56.400 --> 00:03:56.410 align:start position:0% the origin marketplace this is live on 00:03:56.410 --> 00:03:58.560 align:start position:0% the origin marketplace this is live on main<00:03:56.770> app<00:03:56.980> on<00:03:57.190> Ethernet<00:03:57.460> has<00:03:58.060> been<00:03:58.240> ported 00:03:58.560 --> 00:03:58.570 align:start position:0% main app on Ethernet has been ported 00:03:58.570 --> 00:04:02.280 align:start position:0% main app on Ethernet has been ported twice<00:03:58.780> of<00:03:58.960> time<00:03:59.250> you<00:04:00.250> can<00:04:00.400> see<00:04:00.520> you<00:04:00.610> can<00:04:00.790> buy<00:04:01.290> or 00:04:02.280 --> 00:04:02.290 align:start position:0% twice of time you can see you can buy or 00:04:02.290 --> 00:04:04.470 align:start position:0% twice of time you can see you can buy or rent<00:04:02.590> all<00:04:02.920> sorts<00:04:03.250> of<00:04:03.370> different<00:04:03.640> items<00:04:03.970> on 00:04:04.470 --> 00:04:04.480 align:start position:0% rent all sorts of different items on 00:04:04.480 --> 00:04:06.570 align:start position:0% rent all sorts of different items on this<00:04:05.260> market<00:04:05.710> based<00:04:05.950> on<00:04:06.040> all<00:04:06.160> these<00:04:06.370> assets 00:04:06.570 --> 00:04:06.580 align:start position:0% this market based on all these assets 00:04:06.580 --> 00:04:08.820 align:start position:0% this market based on all these assets are<00:04:06.880> being<00:04:06.940> fetched<00:04:07.390> from<00:04:07.690> a<00:04:08.110> fearin 00:04:08.820 --> 00:04:08.830 align:start position:0% are being fetched from a fearin 00:04:08.830 --> 00:04:12.990 align:start position:0% are being fetched from a fearin blockchain<00:04:09.790> and<00:04:10.060> from<00:04:10.450> EMS<00:04:11.640> so<00:04:12.640> here's<00:04:12.820> my 00:04:12.990 --> 00:04:13.000 align:start position:0% blockchain and from EMS so here's my 00:04:13.000 --> 00:04:15.390 align:start position:0% blockchain and from EMS so here's my apartment<00:04:13.810> and<00:04:14.320> Sam<00:04:14.710> Cisco<00:04:15.100> you're<00:04:15.280> all 00:04:15.390 --> 00:04:15.400 align:start position:0% apartment and Sam Cisco you're all 00:04:15.400 --> 00:04:17.160 align:start position:0% apartment and Sam Cisco you're all welcome<00:04:15.610> to<00:04:15.760> come<00:04:15.850> state<00:04:16.210> any<00:04:16.540> time<00:04:16.840> you<00:04:17.020> can 00:04:17.160 --> 00:04:17.170 align:start position:0% welcome to come state any time you can 00:04:17.170 --> 00:04:20.550 align:start position:0% welcome to come state any time you can Lucas<00:04:17.470> on<00:04:17.710> watching<00:04:18.190> this<00:04:18.820> go<00:04:19.060> okay<00:04:19.750> what's 00:04:20.550 --> 00:04:20.560 align:start position:0% Lucas on watching this go okay what's 00:04:20.560 --> 00:04:23.880 align:start position:0% Lucas on watching this go okay what's that<00:04:20.650> any<00:04:20.950> discord<00:04:21.570> with<00:04:22.570> it<00:04:22.720> well<00:04:22.930> it's<00:04:23.560> quite 00:04:23.880 --> 00:04:23.890 align:start position:0% that any discord with it well it's quite 00:04:23.890 --> 00:04:25.230 align:start position:0% that any discord with it well it's quite it<00:04:24.040> just<00:04:24.190> kind<00:04:24.370> of<00:04:24.430> phrase<00:04:24.670> actually<00:04:24.940> if 00:04:25.230 --> 00:04:25.240 align:start position:0% it just kind of phrase actually if 00:04:25.240 --> 00:04:27.260 align:start position:0% it just kind of phrase actually if you've<00:04:25.420> ever<00:04:25.600> written<00:04:25.900> a<00:04:26.170> confidence 00:04:27.260 --> 00:04:27.270 align:start position:0% you've ever written a confidence 00:04:27.270 --> 00:04:30.589 align:start position:0% you've ever written a confidence section<00:04:28.050> 14<00:04:28.460> you<00:04:29.460> can<00:04:29.580> pay<00:04:29.759> with<00:04:29.910> Imperium<00:04:30.449> or 00:04:30.589 --> 00:04:30.599 align:start position:0% section 14 you can pay with Imperium or 00:04:30.599 --> 00:04:35.899 align:start position:0% section 14 you can pay with Imperium or die<00:04:30.780> and<00:04:32.539> ending<00:04:33.539> seniors<00:04:34.250> you<00:04:35.250> know<00:04:35.370> a<00:04:35.400> real 00:04:35.899 --> 00:04:35.909 align:start position:0% die and ending seniors you know a real 00:04:35.909 --> 00:04:43.040 align:start position:0% die and ending seniors you know a real nice<00:04:36.090> party<00:04:36.270> to<00:04:36.509> Sean<00:04:36.780> Penn<00:04:36.960> State<00:04:41.780> in<00:04:42.780> such 00:04:43.040 --> 00:04:43.050 align:start position:0% nice party to Sean Penn State in such 00:04:43.050 --> 00:04:45.409 align:start position:0% nice party to Sean Penn State in such Bailey<00:04:43.409> the<00:04:43.740> scenes<00:04:43.979> missus<00:04:44.490> the<00:04:44.849> data<00:04:45.120> of<00:04:45.300> it 00:04:45.409 --> 00:04:45.419 align:start position:0% Bailey the scenes missus the data of it 00:04:45.419 --> 00:04:48.320 align:start position:0% Bailey the scenes missus the data of it represents<00:04:46.169> that<00:04:46.800> listing<00:04:47.310> it's<00:04:47.970> just<00:04:48.150> a<00:04:48.210> big 00:04:48.320 --> 00:04:48.330 align:start position:0% represents that listing it's just a big 00:04:48.330 --> 00:04:50.960 align:start position:0% represents that listing it's just a big blob<00:04:48.659> of<00:04:48.690> JSON<00:04:49.020> has<00:04:49.560> all<00:04:50.159> the<00:04:50.400> details<00:04:50.789> about 00:04:50.960 --> 00:04:50.970 align:start position:0% blob of JSON has all the details about 00:04:50.970 --> 00:04:53.390 align:start position:0% blob of JSON has all the details about this<00:04:51.210> apartment<00:04:51.840> it's<00:04:52.379> got<00:04:52.650> some<00:04:52.889> links<00:04:53.340> to 00:04:53.390 --> 00:04:53.400 align:start position:0% this apartment it's got some links to 00:04:53.400 --> 00:04:57.409 align:start position:0% this apartment it's got some links to you<00:04:54.389> know<00:04:54.509> the<00:04:54.840> pictures<00:04:55.229> here<00:04:55.470> on<00:04:55.620> ipfs<00:04:56.419> but 00:04:57.409 --> 00:04:57.419 align:start position:0% you know the pictures here on ipfs but 00:04:57.419 --> 00:04:59.149 align:start position:0% you know the pictures here on ipfs but what<00:04:57.569> we<00:04:57.690> actually<00:04:58.050> store<00:04:58.319> on<00:04:58.500> chain 00:04:59.149 --> 00:04:59.159 align:start position:0% what we actually store on chain 00:04:59.159 --> 00:05:02.149 align:start position:0% what we actually store on chain it's<00:04:59.880> just<00:05:00.180> this<00:05:00.330> little<00:05:00.990> part<00:05:01.199> of<00:05:01.319> URL<00:05:01.740> right 00:05:02.149 --> 00:05:02.159 align:start position:0% it's just this little part of URL right 00:05:02.159 --> 00:05:04.670 align:start position:0% it's just this little part of URL right here<00:05:02.220> for<00:05:02.789> entry<00:05:03.090> characters<00:05:03.630> of<00:05:04.020> a<00:05:04.080> 19-minute 00:05:04.670 --> 00:05:04.680 align:start position:0% here for entry characters of a 19-minute 00:05:04.680 --> 00:05:06.950 align:start position:0% here for entry characters of a 19-minute slash<00:05:04.919> and<00:05:05.220> if<00:05:05.849> you<00:05:05.940> change<00:05:06.180> one<00:05:06.419> character<00:05:06.840> it 00:05:06.950 --> 00:05:06.960 align:start position:0% slash and if you change one character it 00:05:06.960 --> 00:05:09.140 align:start position:0% slash and if you change one character it is<00:05:07.050> JSON<00:05:07.409> blog<00:05:07.650> all<00:05:08.310> that<00:05:08.580> goes<00:05:08.729> away<00:05:08.759> so<00:05:09.030> this 00:05:09.140 --> 00:05:09.150 align:start position:0% is JSON blog all that goes away so this 00:05:09.150 --> 00:05:13.990 align:start position:0% is JSON blog all that goes away so this saves<00:05:09.330> us<00:05:09.539> a<00:05:09.780> lot<00:05:10.470> of<00:05:10.710> money<00:05:10.919> by<00:05:11.270> sorting<00:05:12.470> in 00:05:13.990 --> 00:05:14.000 align:start position:0% saves us a lot of money by sorting in 00:05:14.000 --> 00:05:18.020 align:start position:0% saves us a lot of money by sorting in instead<00:05:15.000> of<00:05:15.259> doing<00:05:16.259> it<00:05:16.409> sort<00:05:17.310> of<00:05:17.400> always<00:05:17.849> walk 00:05:18.020 --> 00:05:18.030 align:start position:0% instead of doing it sort of always walk 00:05:18.030 --> 00:05:20.439 align:start position:0% instead of doing it sort of always walk it<00:05:18.270> off 00:05:20.439 --> 00:05:20.449 align:start position:0% 00:05:20.449 --> 00:05:22.909 align:start position:0% so<00:05:21.449> actually<00:05:21.690> put<00:05:21.870> some<00:05:21.990> numbers<00:05:22.289> to<00:05:22.469> this<00:05:22.590> you 00:05:22.909 --> 00:05:22.919 align:start position:0% so actually put some numbers to this you 00:05:22.919 --> 00:05:25.339 align:start position:0% so actually put some numbers to this you actually<00:05:23.310> look<00:05:23.520> at<00:05:23.729> how<00:05:24.330> much<00:05:24.389> gas<00:05:24.780> it<00:05:25.020> costs 00:05:25.339 --> 00:05:25.349 align:start position:0% actually look at how much gas it costs 00:05:25.349 --> 00:05:27.320 align:start position:0% actually look at how much gas it costs to<00:05:25.500> store<00:05:25.710> data<00:05:25.860> across<00:05:26.430> twenty<00:05:26.819> thousand<00:05:27.150> gas 00:05:27.320 --> 00:05:27.330 align:start position:0% to store data across twenty thousand gas 00:05:27.330 --> 00:05:29.659 align:start position:0% to store data across twenty thousand gas to<00:05:27.750> store<00:05:27.990> Freddy<00:05:28.259> two<00:05:28.409> bytes<00:05:28.680> for<00:05:29.340> a<00:05:29.400> thirty 00:05:29.659 --> 00:05:29.669 align:start position:0% to store Freddy two bytes for a thirty 00:05:29.669 --> 00:05:32.830 align:start position:0% to store Freddy two bytes for a thirty two<00:05:29.849> small<00:05:30.180> pipe<00:05:30.710> afraid<00:05:31.710> to<00:05:31.860> quite<00:05:32.069> slow<00:05:32.400> on 00:05:32.830 --> 00:05:32.840 align:start position:0% two small pipe afraid to quite slow on 00:05:32.840 --> 00:05:35.779 align:start position:0% two small pipe afraid to quite slow on the<00:05:33.840> very<00:05:34.050> I'm<00:05:34.139> even<00:05:34.889> modifying<00:05:35.310> data<00:05:35.430> caused 00:05:35.779 --> 00:05:35.789 align:start position:0% the very I'm even modifying data caused 00:05:35.789 --> 00:05:38.510 align:start position:0% the very I'm even modifying data caused by<00:05:36.030> thousand<00:05:36.449> gas<00:05:36.630> if<00:05:37.380> you<00:05:37.530> delete<00:05:37.860> data<00:05:38.069> it 00:05:38.510 --> 00:05:38.520 align:start position:0% by thousand gas if you delete data it 00:05:38.520 --> 00:05:39.950 align:start position:0% by thousand gas if you delete data it cost<00:05:38.789> five<00:05:38.969> thousand<00:05:39.270> gas<00:05:39.419> but<00:05:39.690> then<00:05:39.780> you<00:05:39.870> get 00:05:39.950 --> 00:05:39.960 align:start position:0% cost five thousand gas but then you get 00:05:39.960 --> 00:05:43.519 align:start position:0% cost five thousand gas but then you get a<00:05:40.020> 15<00:05:40.469> thousand<00:05:40.949> gas<00:05:41.550> refund<00:05:42.150> from<00:05:42.690> when<00:05:43.409> you 00:05:43.519 --> 00:05:43.529 align:start position:0% a 15 thousand gas refund from when you 00:05:43.529 --> 00:05:46.370 align:start position:0% a 15 thousand gas refund from when you first<00:05:43.560> stored<00:05:44.490> it<00:05:44.930> but<00:05:45.930> one<00:05:46.080> thing<00:05:46.229> you'll 00:05:46.370 --> 00:05:46.380 align:start position:0% first stored it but one thing you'll 00:05:46.380 --> 00:05:48.649 align:start position:0% first stored it but one thing you'll notice<00:05:46.620> here<00:05:46.770> on<00:05:46.919> the<00:05:47.039> right<00:05:47.069> we<00:05:47.490> have<00:05:47.520> log<00:05:48.060> and 00:05:48.649 --> 00:05:48.659 align:start position:0% notice here on the right we have log and 00:05:48.659 --> 00:05:51.800 align:start position:0% notice here on the right we have log and so<00:05:48.930> it's<00:05:49.409> way<00:05:49.740> cheaper<00:05:49.770> for<00:05:50.460> us<00:05:50.490> to<00:05:50.599> write<00:05:51.599> to 00:05:51.800 --> 00:05:51.810 align:start position:0% so it's way cheaper for us to write to 00:05:51.810 --> 00:05:54.950 align:start position:0% so it's way cheaper for us to write to logs<00:05:52.080> and<00:05:52.380> is<00:05:52.590> to<00:05:52.830> store<00:05:53.069> data<00:05:53.279> on<00:05:54.000> a<00:05:54.090> chain<00:05:54.389> so 00:05:54.950 --> 00:05:54.960 align:start position:0% logs and is to store data on a chain so 00:05:54.960 --> 00:05:57.050 align:start position:0% logs and is to store data on a chain so whatever<00:05:55.139> tricks<00:05:55.529> that<00:05:55.710> we've<00:05:55.949> leaned<00:05:56.909> on 00:05:57.050 --> 00:05:57.060 align:start position:0% whatever tricks that we've leaned on 00:05:57.060 --> 00:05:57.980 align:start position:0% whatever tricks that we've leaned on very<00:05:57.539> handily 00:05:57.980 --> 00:05:57.990 align:start position:0% very handily 00:05:57.990 --> 00:06:00.740 align:start position:0% very handily at<00:05:58.319> our<00:05:58.560> gym<00:05:58.710> is<00:05:58.889> just<00:05:59.400> emitting<00:06:00.029> events 00:06:00.740 --> 00:06:00.750 align:start position:0% at our gym is just emitting events 00:06:00.750 --> 00:06:03.620 align:start position:0% at our gym is just emitting events instead<00:06:01.289> of<00:06:01.409> actually<00:06:01.770> storing<00:06:02.130> a<00:06:02.630> tentative 00:06:03.620 --> 00:06:03.630 align:start position:0% instead of actually storing a tentative 00:06:03.630 --> 00:06:06.360 align:start position:0% instead of actually storing a tentative variables 00:06:06.360 --> 00:06:06.370 align:start position:0% 00:06:06.370 --> 00:06:09.060 align:start position:0% so<00:06:06.970> pearls<00:06:07.660> are<00:06:07.780> pretty<00:06:07.960> obvious<00:06:08.050> seen<00:06:08.440> save<00:06:08.830> a 00:06:09.060 --> 00:06:09.070 align:start position:0% so pearls are pretty obvious seen save a 00:06:09.070 --> 00:06:11.189 align:start position:0% so pearls are pretty obvious seen save a lot<00:06:09.280> of<00:06:09.310> gas<00:06:09.520> that's<00:06:09.760> far<00:06:10.030> more<00:06:10.060> gas<00:06:10.690> efficient 00:06:11.189 --> 00:06:11.199 align:start position:0% lot of gas that's far more gas efficient 00:06:11.199 --> 00:06:14.730 align:start position:0% lot of gas that's far more gas efficient to<00:06:11.440> use<00:06:11.940> events<00:06:12.940> the<00:06:13.720> only<00:06:13.840> problem<00:06:14.169> is<00:06:14.290> that 00:06:14.730 --> 00:06:14.740 align:start position:0% to use events the only problem is that 00:06:14.740 --> 00:06:16.820 align:start position:0% to use events the only problem is that smart<00:06:14.979> contracts<00:06:15.490> can't<00:06:15.790> read<00:06:15.970> the<00:06:16.120> locks<00:06:16.360> so 00:06:16.820 --> 00:06:16.830 align:start position:0% smart contracts can't read the locks so 00:06:16.830 --> 00:06:19.350 align:start position:0% smart contracts can't read the locks so you<00:06:17.830> have<00:06:18.070> a<00:06:18.310> nice<00:06:18.610> database<00:06:18.970> of<00:06:19.240> all<00:06:19.300> the 00:06:19.350 --> 00:06:19.360 align:start position:0% you have a nice database of all the 00:06:19.360 --> 00:06:21.570 align:start position:0% you have a nice database of all the different<00:06:19.870> events<00:06:20.350> but<00:06:20.530> you<00:06:21.190> have<00:06:21.310> to<00:06:21.490> have 00:06:21.570 --> 00:06:21.580 align:start position:0% different events but you have to have 00:06:21.580 --> 00:06:24.090 align:start position:0% different events but you have to have someone<00:06:21.940> willing<00:06:22.120> to<00:06:22.330> be<00:06:22.510> able<00:06:22.570> to<00:06:23.100> index 00:06:24.090 --> 00:06:24.100 align:start position:0% someone willing to be able to index 00:06:24.100 --> 00:06:28.620 align:start position:0% someone willing to be able to index those<00:06:25.410> events<00:06:26.410> from<00:06:26.800> the<00:06:26.949> locks<00:06:27.160> and<00:06:27.540> you<00:06:28.540> know 00:06:28.620 --> 00:06:28.630 align:start position:0% those events from the locks and you know 00:06:28.630 --> 00:06:30.629 align:start position:0% those events from the locks and you know things<00:06:28.900> like<00:06:28.990> if<00:06:29.680> you<00:06:29.889> are<00:06:30.070> you<00:06:30.190> have<00:06:30.250> to<00:06:30.460> pay 00:06:30.629 --> 00:06:30.639 align:start position:0% things like if you are you have to pay 00:06:30.639 --> 00:06:32.010 align:start position:0% things like if you are you have to pay extra<00:06:30.850> for<00:06:31.090> it<00:06:31.150> if<00:06:31.389> you<00:06:31.479> have<00:06:31.570> the<00:06:31.840> full 00:06:32.010 --> 00:06:32.020 align:start position:0% extra for it if you have the full 00:06:32.020 --> 00:06:33.870 align:start position:0% extra for it if you have the full mobility<00:06:32.139> running<00:06:32.770> to<00:06:33.430> have<00:06:33.520> some<00:06:33.729> way<00:06:33.850> of 00:06:33.870 --> 00:06:33.880 align:start position:0% mobility running to have some way of 00:06:33.880 --> 00:06:36.689 align:start position:0% mobility running to have some way of indexing<00:06:34.300> ballistic<00:06:35.260> sensitive<00:06:35.710> but<00:06:36.430> is 00:06:36.689 --> 00:06:36.699 align:start position:0% indexing ballistic sensitive but is 00:06:36.699 --> 00:06:39.770 align:start position:0% indexing ballistic sensitive but is worth<00:06:37.030> doing<00:06:37.270> if<00:06:38.110> you<00:06:38.320> can 00:06:39.770 --> 00:06:39.780 align:start position:0% worth doing if you can 00:06:39.780 --> 00:06:42.390 align:start position:0% worth doing if you can another<00:06:40.780> trick<00:06:41.110> if<00:06:41.260> you<00:06:41.290> are<00:06:41.500> storing<00:06:41.770> data<00:06:42.040> on 00:06:42.390 --> 00:06:42.400 align:start position:0% another trick if you are storing data on 00:06:42.400 --> 00:06:44.129 align:start position:0% another trick if you are storing data on the<00:06:42.700> blockchain<00:06:42.910> it's<00:06:43.330> helpful<00:06:43.990> to 00:06:44.129 --> 00:06:44.139 align:start position:0% the blockchain it's helpful to 00:06:44.139 --> 00:06:46.830 align:start position:0% the blockchain it's helpful to understand<00:06:44.710> how<00:06:45.610> big<00:06:45.669> EVM<00:06:46.150> is<00:06:46.300> storing<00:06:46.690> data 00:06:46.830 --> 00:06:46.840 align:start position:0% understand how big EVM is storing data 00:06:46.840 --> 00:06:49.379 align:start position:0% understand how big EVM is storing data under<00:06:47.410> cover<00:06:47.710> so<00:06:48.100> those<00:06:48.430> ready<00:06:48.729> to<00:06:48.790> fight 00:06:49.379 --> 00:06:49.389 align:start position:0% under cover so those ready to fight 00:06:49.389 --> 00:06:51.750 align:start position:0% under cover so those ready to fight slots<00:06:49.830> actually<00:06:50.830> matter<00:06:51.040> so<00:06:51.340> you<00:06:51.370> knew<00:06:51.580> things 00:06:51.750 --> 00:06:51.760 align:start position:0% slots actually matter so you knew things 00:06:51.760 --> 00:06:54.090 align:start position:0% slots actually matter so you knew things like<00:06:51.970> variable<00:06:52.510> packet<00:06:52.870> where<00:06:53.650> you<00:06:53.830> take 00:06:54.090 --> 00:06:54.100 align:start position:0% like variable packet where you take 00:06:54.100 --> 00:06:55.740 align:start position:0% like variable packet where you take before<00:06:54.310> during<00:06:54.880> which<00:06:55.030> you<00:06:55.210> analyze<00:06:55.570> these 00:06:55.740 --> 00:06:55.750 align:start position:0% before during which you analyze these 00:06:55.750 --> 00:06:57.870 align:start position:0% before during which you analyze these variables<00:06:56.229> and<00:06:56.350> actual<00:06:56.650> matters<00:06:57.040> so<00:06:57.760> if 00:06:57.870 --> 00:06:57.880 align:start position:0% variables and actual matters so if 00:06:57.880 --> 00:07:00.840 align:start position:0% variables and actual matters so if you've<00:06:58.000> got<00:06:58.240> you<00:06:58.990> know<00:06:59.110> be<00:06:59.350> a<00:06:59.650> B<00:07:00.160> and<00:07:00.340> C<00:07:00.550> these 00:07:00.840 --> 00:07:00.850 align:start position:0% you've got you know be a B and C these 00:07:00.850 --> 00:07:04.170 align:start position:0% you've got you know be a B and C these three<00:07:01.060> variables<00:07:01.300> to<00:07:02.289> around<00:07:02.590> 128<00:07:03.490> back<00:07:03.729> one 00:07:04.170 --> 00:07:04.180 align:start position:0% three variables to around 128 back one 00:07:04.180 --> 00:07:07.680 align:start position:0% three variables to around 128 back one is<00:07:04.330> 256<00:07:05.110> pence<00:07:05.770> now<00:07:06.669> you<00:07:06.729> can<00:07:07.120> either<00:07:07.210> pack<00:07:07.510> it 00:07:07.680 --> 00:07:07.690 align:start position:0% is 256 pence now you can either pack it 00:07:07.690 --> 00:07:10.560 align:start position:0% is 256 pence now you can either pack it into<00:07:07.840> two<00:07:08.560> slots<00:07:08.919> or<00:07:09.430> free<00:07:09.789> slots<00:07:10.090> depending 00:07:10.560 --> 00:07:10.570 align:start position:0% into two slots or free slots depending 00:07:10.570 --> 00:07:12.270 align:start position:0% into two slots or free slots depending on<00:07:10.690> the<00:07:10.960> order<00:07:11.289> those<00:07:11.620> variables<00:07:12.100> as<00:07:12.250> a 00:07:12.270 --> 00:07:12.280 align:start position:0% on the order those variables as a 00:07:12.280 --> 00:07:14.400 align:start position:0% on the order those variables as a difference<00:07:12.700> of<00:07:12.789> my<00:07:12.970> thousand<00:07:13.389> yes<00:07:13.570> just<00:07:14.260> by 00:07:14.400 --> 00:07:14.410 align:start position:0% difference of my thousand yes just by 00:07:14.410 --> 00:07:16.230 align:start position:0% difference of my thousand yes just by swapping<00:07:14.650> the<00:07:14.889> order<00:07:15.010> of<00:07:15.669> high<00:07:15.910> a<00:07:15.940> might 00:07:16.230 --> 00:07:16.240 align:start position:0% swapping the order of high a might 00:07:16.240 --> 00:07:20.219 align:start position:0% swapping the order of high a might include<00:07:18.360> how<00:07:19.360> many<00:07:19.539> of<00:07:19.630> you<00:07:19.780> know<00:07:19.930> what<00:07:20.110> you 00:07:20.219 --> 00:07:20.229 align:start position:0% include how many of you know what you 00:07:20.229 --> 00:07:22.770 align:start position:0% include how many of you know what you meant<00:07:20.350> sourcing<00:07:20.800> is<00:07:20.830> the<00:07:21.460> introduced<00:07:21.849> time<00:07:22.090> so 00:07:22.770 --> 00:07:22.780 align:start position:0% meant sourcing is the introduced time so 00:07:22.780 --> 00:07:25.350 align:start position:0% meant sourcing is the introduced time so some<00:07:23.169> of<00:07:23.200> you<00:07:23.470> okay<00:07:23.889> so<00:07:24.310> I<00:07:24.340> guarantee<00:07:25.030> even<00:07:25.210> if 00:07:25.350 --> 00:07:25.360 align:start position:0% some of you okay so I guarantee even if 00:07:25.360 --> 00:07:27.510 align:start position:0% some of you okay so I guarantee even if you<00:07:25.510> don't<00:07:25.780> know<00:07:25.960> the<00:07:26.470> term<00:07:26.770> all<00:07:27.099> of<00:07:27.310> you<00:07:27.400> know 00:07:27.510 --> 00:07:27.520 align:start position:0% you don't know the term all of you know 00:07:27.520 --> 00:07:29.610 align:start position:0% you don't know the term all of you know this<00:07:27.639> concept<00:07:28.120> it's<00:07:28.750> essentially<00:07:29.320> what<00:07:29.500> the 00:07:29.610 --> 00:07:29.620 align:start position:0% this concept it's essentially what the 00:07:29.620 --> 00:07:31.320 align:start position:0% this concept it's essentially what the blockchain<00:07:29.860> does<00:07:30.250> if<00:07:30.400> you<00:07:30.520> were<00:07:30.610> to<00:07:30.760> fire<00:07:31.060> off 00:07:31.320 --> 00:07:31.330 align:start position:0% blockchain does if you were to fire off 00:07:31.330 --> 00:07:34.409 align:start position:0% blockchain does if you were to fire off a<00:07:31.990> film<00:07:32.860> node<00:07:33.099> and<00:07:33.340> started<00:07:33.729> a<00:07:33.820> Genesis<00:07:34.240> block 00:07:34.409 --> 00:07:34.419 align:start position:0% a film node and started a Genesis block 00:07:34.419 --> 00:07:37.529 align:start position:0% a film node and started a Genesis block and<00:07:34.810> work<00:07:34.990> your<00:07:35.200> way<00:07:35.260> to<00:07:35.410> today<00:07:36.400> to<00:07:37.240> get<00:07:37.389> the 00:07:37.529 --> 00:07:37.539 align:start position:0% and work your way to today to get the 00:07:37.539 --> 00:07:39.839 align:start position:0% and work your way to today to get the current<00:07:37.780> state<00:07:38.110> of<00:07:38.139> how<00:07:38.979> much<00:07:39.160> money<00:07:39.400> we<00:07:39.550> all 00:07:39.839 --> 00:07:39.849 align:start position:0% current state of how much money we all 00:07:39.849 --> 00:07:42.480 align:start position:0% current state of how much money we all have<00:07:40.289> lots<00:07:41.289> events<00:07:41.770> or<00:07:41.889> some<00:07:42.070> where<00:07:42.310> you're 00:07:42.480 --> 00:07:42.490 align:start position:0% have lots events or some where you're 00:07:42.490 --> 00:07:45.060 align:start position:0% have lots events or some where you're actually<00:07:42.700> building<00:07:43.120> up<00:07:43.419> a<00:07:43.599> state<00:07:43.930> based<00:07:44.530> on<00:07:44.770> a 00:07:45.060 --> 00:07:45.070 align:start position:0% actually building up a state based on a 00:07:45.070 --> 00:07:45.600 align:start position:0% actually building up a state based on a list<00:07:45.370> of 00:07:45.600 --> 00:07:45.610 align:start position:0% list of 00:07:45.610 --> 00:07:48.659 align:start position:0% list of events<00:07:46.060> instead<00:07:46.960> of<00:07:47.289> doing<00:07:47.680> it<00:07:47.830> as<00:07:48.159> the 00:07:48.659 --> 00:07:48.669 align:start position:0% events instead of doing it as the 00:07:48.669 --> 00:07:50.909 align:start position:0% events instead of doing it as the current<00:07:49.000> state<00:07:49.240> distorting<00:07:49.960> a<00:07:50.050> snapshot<00:07:50.379> of 00:07:50.909 --> 00:07:50.919 align:start position:0% current state distorting a snapshot of 00:07:50.919 --> 00:07:53.189 align:start position:0% current state distorting a snapshot of the<00:07:51.280> current<00:07:51.639> state<00:07:52.060> doesn't<00:07:52.810> need<00:07:52.960> to<00:07:53.139> the 00:07:53.189 --> 00:07:53.199 align:start position:0% the current state doesn't need to the 00:07:53.199 --> 00:07:55.439 align:start position:0% the current state doesn't need to the concept<00:07:53.650> to<00:07:53.889> blockchains<00:07:54.370> it's<00:07:55.270> also 00:07:55.439 --> 00:07:55.449 align:start position:0% concept to blockchains it's also 00:07:55.449 --> 00:07:57.540 align:start position:0% concept to blockchains it's also something<00:07:55.780> that's<00:07:55.960> really<00:07:56.080> helpful<00:07:56.770> when 00:07:57.540 --> 00:07:57.550 align:start position:0% something that's really helpful when 00:07:57.550 --> 00:08:01.649 align:start position:0% something that's really helpful when you're<00:07:57.699> actually<00:07:57.849> designing<00:07:58.330> an<00:07:58.509> app<00:08:00.659> so 00:08:01.649 --> 00:08:01.659 align:start position:0% you're actually designing an app so 00:08:01.659 --> 00:08:04.770 align:start position:0% you're actually designing an app so here's<00:08:01.990> how<00:08:02.199> we<00:08:02.319> do<00:08:02.500> it<00:08:03.060> and<00:08:04.060> ordinance<00:08:04.509> so 00:08:04.770 --> 00:08:04.780 align:start position:0% here's how we do it and ordinance so 00:08:04.780 --> 00:08:08.249 align:start position:0% here's how we do it and ordinance so here's<00:08:05.050> an<00:08:05.889> idiot<00:08:06.610> so<00:08:07.449> this<00:08:07.569> is<00:08:07.750> a<00:08:07.780> tool<00:08:08.080> we 00:08:08.249 --> 00:08:08.259 align:start position:0% here's an idiot so this is a tool we 00:08:08.259 --> 00:08:10.080 align:start position:0% here's an idiot so this is a tool we built<00:08:08.289> that<00:08:08.680> lets<00:08:08.919> you<00:08:09.069> sort<00:08:09.250> of<00:08:09.340> wonderful 00:08:10.080 --> 00:08:10.090 align:start position:0% built that lets you sort of wonderful 00:08:10.090 --> 00:08:12.899 align:start position:0% built that lets you sort of wonderful covers<00:08:10.539> of<00:08:10.810> our<00:08:11.229> marketplace<00:08:11.860> and<00:08:12.159> actually 00:08:12.899 --> 00:08:12.909 align:start position:0% covers of our marketplace and actually 00:08:12.909 --> 00:08:15.209 align:start position:0% covers of our marketplace and actually look<00:08:13.090> at<00:08:13.270> all<00:08:13.479> of<00:08:13.539> the<00:08:13.780> IP<00:08:13.960> advantages<00:08:14.860> and 00:08:15.209 --> 00:08:15.219 align:start position:0% look at all of the IP advantages and 00:08:15.219 --> 00:08:17.399 align:start position:0% look at all of the IP advantages and natural<00:08:15.669> actions<00:08:16.120> and<00:08:16.659> all<00:08:16.750> the<00:08:16.900> data<00:08:17.110> that<00:08:17.229> we 00:08:17.399 --> 00:08:17.409 align:start position:0% natural actions and all the data that we 00:08:17.409 --> 00:08:19.230 align:start position:0% natural actions and all the data that we point<00:08:17.860> to<00:08:17.919> generally<00:08:18.460> hide<00:08:18.729> away<00:08:18.909> from<00:08:19.029> the 00:08:19.230 --> 00:08:19.240 align:start position:0% point to generally hide away from the 00:08:19.240 --> 00:08:22.950 align:start position:0% point to generally hide away from the users<00:08:20.139> and<00:08:20.590> so<00:08:21.189> you<00:08:21.310> can<00:08:21.400> see<00:08:21.610> here<00:08:21.849> this<00:08:22.090> list 00:08:22.950 --> 00:08:22.960 align:start position:0% users and so you can see here this list 00:08:22.960 --> 00:08:25.909 align:start position:0% users and so you can see here this list of<00:08:23.770> all<00:08:24.099> the<00:08:24.279> events<00:08:24.550> have<00:08:24.879> been<00:08:25.000> happening<00:08:25.539> on 00:08:25.909 --> 00:08:25.919 align:start position:0% of all the events have been happening on 00:08:25.919 --> 00:08:28.260 align:start position:0% of all the events have been happening on my<00:08:26.919> apartment<00:08:27.490> so<00:08:27.729> you<00:08:27.819> can<00:08:27.909> see<00:08:28.029> when<00:08:28.180> I<00:08:28.210> first 00:08:28.260 --> 00:08:28.270 align:start position:0% my apartment so you can see when I first 00:08:28.270 --> 00:08:29.189 align:start position:0% my apartment so you can see when I first created<00:08:28.810> it 00:08:29.189 --> 00:08:29.199 align:start position:0% created it 00:08:29.199 --> 00:08:32.399 align:start position:0% created it and<00:08:30.009> the<00:08:30.129> blob<00:08:30.400> of<00:08:30.430> JSON<00:08:30.789> it<00:08:31.120> was<00:08:31.240> created<00:08:31.750> and 00:08:32.399 --> 00:08:32.409 align:start position:0% and the blob of JSON it was created and 00:08:32.409 --> 00:08:35.040 align:start position:0% and the blob of JSON it was created and then<00:08:32.620> I<00:08:32.709> updated<00:08:33.190> it<00:08:33.279> a<00:08:33.399> few<00:08:33.760> times<00:08:33.969> and<00:08:34.930> then 00:08:35.040 --> 00:08:35.050 align:start position:0% then I updated it a few times and then 00:08:35.050 --> 00:08:37.050 align:start position:0% then I updated it a few times and then some<00:08:35.229> of<00:08:35.320> made<00:08:35.440> an<00:08:35.529> offer<00:08:35.649> on<00:08:35.800> it<00:08:35.919> and<00:08:36.729> then<00:08:37.000> I 00:08:37.050 --> 00:08:37.060 align:start position:0% some of made an offer on it and then I 00:08:37.060 --> 00:08:40.079 align:start position:0% some of made an offer on it and then I accepted<00:08:37.539> that<00:08:37.659> offer<00:08:37.719> and<00:08:38.380> then<00:08:39.310> they<00:08:39.849> left 00:08:40.079 --> 00:08:40.089 align:start position:0% accepted that offer and then they left 00:08:40.089 --> 00:08:42.690 align:start position:0% accepted that offer and then they left to<00:08:40.240> review<00:08:40.659> it<00:08:40.779> after<00:08:41.050> it<00:08:41.349> was<00:08:41.409> the<00:08:42.250> offer<00:08:42.459> was 00:08:42.690 --> 00:08:42.700 align:start position:0% to review it after it was the offer was 00:08:42.700 --> 00:08:44.280 align:start position:0% to review it after it was the offer was completely<00:08:43.240> after<00:08:43.419> the<00:08:43.719> cooking<00:08:44.200> was 00:08:44.280 --> 00:08:44.290 align:start position:0% completely after the cooking was 00:08:44.290 --> 00:08:47.190 align:start position:0% completely after the cooking was completed<00:08:45.120> we've<00:08:46.120> got<00:08:46.269> some<00:08:46.480> some<00:08:47.079> more 00:08:47.190 --> 00:08:47.200 align:start position:0% completed we've got some some more 00:08:47.200 --> 00:08:49.769 align:start position:0% completed we've got some some more offers<00:08:47.529> coming<00:08:47.829> in<00:08:48.010> and<00:08:48.250> I<00:08:48.850> said<00:08:49.240> to<00:08:49.510> those<00:08:49.660> as 00:08:49.769 --> 00:08:49.779 align:start position:0% offers coming in and I said to those as 00:08:49.779 --> 00:08:53.280 align:start position:0% offers coming in and I said to those as well<00:08:49.899> and<00:08:50.589> so<00:08:51.370> instead<00:08:51.670> of<00:08:52.110> storing<00:08:53.110> a 00:08:53.280 --> 00:08:53.290 align:start position:0% well and so instead of storing a 00:08:53.290 --> 00:08:56.160 align:start position:0% well and so instead of storing a calendar<00:08:53.860> on<00:08:54.100> the<00:08:54.279> blockchain<00:08:54.870> about<00:08:55.870> which 00:08:56.160 --> 00:08:56.170 align:start position:0% calendar on the blockchain about which 00:08:56.170 --> 00:08:58.500 align:start position:0% calendar on the blockchain about which days<00:08:56.470> my<00:08:57.040> apartment<00:08:57.880> is<00:08:57.970> available<00:08:58.089> can<00:08:58.420> you 00:08:58.500 --> 00:08:58.510 align:start position:0% days my apartment is available can you 00:08:58.510 --> 00:09:00.930 align:start position:0% days my apartment is available can you think<00:08:58.660> about<00:08:58.779> doing<00:08:59.560> that<00:08:59.709> in<00:08:59.890> salinity<00:09:00.190> the 00:09:00.930 --> 00:09:00.940 align:start position:0% think about doing that in salinity the 00:09:00.940 --> 00:09:02.610 align:start position:0% think about doing that in salinity the amount<00:09:01.300> of<00:09:01.360> complexity<00:09:01.930> of<00:09:02.079> writing<00:09:02.470> that 00:09:02.610 --> 00:09:02.620 align:start position:0% amount of complexity of writing that 00:09:02.620 --> 00:09:05.639 align:start position:0% amount of complexity of writing that code<00:09:03.600> like<00:09:04.600> word<00:09:04.810> if<00:09:04.990> you<00:09:05.050> want<00:09:05.260> to<00:09:05.380> come<00:09:05.500> in 00:09:05.639 --> 00:09:05.649 align:start position:0% code like word if you want to come in 00:09:05.649 --> 00:09:07.590 align:start position:0% code like word if you want to come in and<00:09:05.800> block<00:09:06.010> off<00:09:06.250> the<00:09:06.640> month<00:09:06.850> of<00:09:07.000> July 00:09:07.590 --> 00:09:07.600 align:start position:0% and block off the month of July 00:09:07.600 --> 00:09:09.630 align:start position:0% and block off the month of July well<00:09:08.019> do<00:09:08.110> you<00:09:08.170> put<00:09:08.350> that<00:09:08.380> in<00:09:08.589> for<00:09:08.860> lit<00:09:09.070> up<00:09:09.370> and 00:09:09.630 --> 00:09:09.640 align:start position:0% well do you put that in for lit up and 00:09:09.640 --> 00:09:12.300 align:start position:0% well do you put that in for lit up and do<00:09:09.850> it<00:09:10.120> like<00:09:10.420> how<00:09:11.019> expensive<00:09:11.649> is<00:09:11.980> that<00:09:12.010> going 00:09:12.300 --> 00:09:12.310 align:start position:0% do it like how expensive is that going 00:09:12.310 --> 00:09:15.180 align:start position:0% do it like how expensive is that going to<00:09:12.399> be<00:09:12.519> to<00:09:12.820> update<00:09:13.149> that<00:09:13.660> all<00:09:14.079> of<00:09:14.589> your<00:09:14.740> storing 00:09:15.180 --> 00:09:15.190 align:start position:0% to be to update that all of your storing 00:09:15.190 --> 00:09:17.699 align:start position:0% to be to update that all of your storing all<00:09:15.310> I<00:09:15.339> didn't<00:09:15.699> love<00:09:15.910> Gina<00:09:16.120> is<00:09:16.240> crazy<00:09:16.709> so 00:09:17.699 --> 00:09:17.709 align:start position:0% all I didn't love Gina is crazy so 00:09:17.709 --> 00:09:19.259 align:start position:0% all I didn't love Gina is crazy so instead<00:09:18.040> what<00:09:18.279> we<00:09:18.399> do<00:09:18.519> is<00:09:18.550> we<00:09:18.760> don't<00:09:18.880> don't 00:09:19.259 --> 00:09:19.269 align:start position:0% instead what we do is we don't don't 00:09:19.269 --> 00:09:22.110 align:start position:0% instead what we do is we don't don't even<00:09:19.510> try<00:09:19.779> we<00:09:19.959> just<00:09:20.170> omit<00:09:20.470> these<00:09:20.680> events<00:09:21.120> with 00:09:22.110 --> 00:09:22.120 align:start position:0% even try we just omit these events with 00:09:22.120 --> 00:09:24.120 align:start position:0% even try we just omit these events with each<00:09:22.480> of<00:09:22.630> the<00:09:22.720> offers<00:09:23.019> of<00:09:23.140> command<00:09:23.529> when<00:09:24.100> I 00:09:24.120 --> 00:09:24.130 align:start position:0% each of the offers of command when I 00:09:24.130 --> 00:09:26.100 align:start position:0% each of the offers of command when I accept<00:09:24.699> them<00:09:24.880> and<00:09:25.149> then<00:09:25.720> you<00:09:25.810> can<00:09:25.990> use 00:09:26.100 --> 00:09:26.110 align:start position:0% accept them and then you can use 00:09:26.110 --> 00:09:28.800 align:start position:0% accept them and then you can use JavaScript<00:09:26.529> you<00:09:27.010> can<00:09:27.070> is<00:09:27.430> very<00:09:27.459> easy<00:09:27.760> to<00:09:27.940> walk 00:09:28.800 --> 00:09:28.810 align:start position:0% JavaScript you can is very easy to walk 00:09:28.810 --> 00:09:30.180 align:start position:0% JavaScript you can is very easy to walk through<00:09:29.140> this<00:09:29.320> list<00:09:29.560> of<00:09:29.740> events<00:09:30.040> with 00:09:30.180 --> 00:09:30.190 align:start position:0% through this list of events with 00:09:30.190 --> 00:09:32.579 align:start position:0% through this list of events with JavaScript<00:09:30.699> and<00:09:30.940> rebuild<00:09:31.870> the<00:09:32.110> state<00:09:32.380> of<00:09:32.500> the 00:09:32.579 --> 00:09:32.589 align:start position:0% JavaScript and rebuild the state of the 00:09:32.589 --> 00:09:34.199 align:start position:0% JavaScript and rebuild the state of the world<00:09:32.829> so<00:09:33.430> if<00:09:33.490> you<00:09:33.579> want<00:09:33.790> to<00:09:33.880> know<00:09:34.000> if<00:09:34.089> my 00:09:34.199 --> 00:09:34.209 align:start position:0% world so if you want to know if my 00:09:34.209 --> 00:09:36.180 align:start position:0% world so if you want to know if my apartment<00:09:34.630> is<00:09:34.690> available<00:09:35.079> or<00:09:35.140> not<00:09:35.199> the<00:09:35.920> only 00:09:36.180 --> 00:09:36.190 align:start position:0% apartment is available or not the only 00:09:36.190 --> 00:09:38.670 align:start position:0% apartment is available or not the only way<00:09:36.279> to<00:09:36.310> do<00:09:36.550> is<00:09:36.670> go<00:09:36.910> back<00:09:37.149> to<00:09:37.570> the<00:09:37.630> star<00:09:37.930> walk 00:09:38.670 --> 00:09:38.680 align:start position:0% way to do is go back to the star walk 00:09:38.680 --> 00:09:40.439 align:start position:0% way to do is go back to the star walk through<00:09:38.980> all<00:09:39.100> of<00:09:39.220> them<00:09:39.339> see<00:09:39.850> which<00:09:39.970> offers<00:09:40.329> I 00:09:40.439 --> 00:09:40.449 align:start position:0% through all of them see which offers I 00:09:40.449 --> 00:09:41.049 align:start position:0% through all of them see which offers I accept 00:09:41.049 --> 00:09:41.059 align:start position:0% accept 00:09:41.059 --> 00:09:43.359 align:start position:0% accept I<00:09:41.089> turn<00:09:41.569> down<00:09:41.659> and<00:09:42.349> now<00:09:42.529> you've<00:09:42.769> got<00:09:43.009> the<00:09:43.129> sense 00:09:43.359 --> 00:09:43.369 align:start position:0% I turn down and now you've got the sense 00:09:43.369 --> 00:09:45.459 align:start position:0% I turn down and now you've got the sense of<00:09:43.549> the<00:09:43.639> state<00:09:43.849> of<00:09:43.939> the<00:09:43.999> world<00:09:44.239> and<00:09:44.539> as<00:09:44.929> way<00:09:45.259> way 00:09:45.459 --> 00:09:45.469 align:start position:0% of the state of the world and as way way 00:09:45.469 --> 00:09:48.219 align:start position:0% of the state of the world and as way way cheaper<00:09:45.499> as<00:09:46.189> Whaley<00:09:46.849> easier<00:09:47.209> than<00:09:47.809> trying<00:09:48.139> to 00:09:48.219 --> 00:09:48.229 align:start position:0% cheaper as Whaley easier than trying to 00:09:48.229 --> 00:09:54.240 align:start position:0% cheaper as Whaley easier than trying to do<00:09:48.409> everything<00:09:49.099> my<00:09:49.249> chain 00:09:54.240 --> 00:09:54.250 align:start position:0% 00:09:54.250 --> 00:09:57.430 align:start position:0% [Music] 00:09:57.430 --> 00:09:57.440 align:start position:0% [Music] 00:09:57.440 --> 00:10:01.550 align:start position:0% [Music] so<00:09:58.440> named<00:09:58.890> registries<00:09:59.459> is<00:09:59.550> another<00:10:00.560> concept 00:10:01.550 --> 00:10:01.560 align:start position:0% so named registries is another concept 00:10:01.560 --> 00:10:04.280 align:start position:0% so named registries is another concept you<00:10:01.770> should<00:10:01.800> be<00:10:02.370> aware<00:10:02.490> of<00:10:02.700> ENS<00:10:03.690> is<00:10:03.870> probably 00:10:04.280 --> 00:10:04.290 align:start position:0% you should be aware of ENS is probably 00:10:04.290 --> 00:10:06.680 align:start position:0% you should be aware of ENS is probably the<00:10:04.560> best<00:10:05.040> known<00:10:05.250> example<00:10:05.820> like<00:10:06.060> take<00:10:06.390> some 00:10:06.680 --> 00:10:06.690 align:start position:0% the best known example like take some 00:10:06.690 --> 00:10:09.019 align:start position:0% the best known example like take some when<00:10:07.649> you<00:10:07.709> want<00:10:07.890> to<00:10:08.010> map<00:10:08.220> two<00:10:08.520> things<00:10:08.820> together 00:10:09.019 --> 00:10:09.029 align:start position:0% when you want to map two things together 00:10:09.029 --> 00:10:11.930 align:start position:0% when you want to map two things together so<00:10:09.510> you<00:10:09.690> take<00:10:10.050> Josh<00:10:10.620> phaser<00:10:11.040> gives<00:10:11.490> a<00:10:11.700> nice 00:10:11.930 --> 00:10:11.940 align:start position:0% so you take Josh phaser gives a nice 00:10:11.940 --> 00:10:15.050 align:start position:0% so you take Josh phaser gives a nice friendly<00:10:12.420> name<00:10:12.750> and<00:10:12.930> you<00:10:12.990> can<00:10:13.140> map<00:10:13.350> it<00:10:13.589> to<00:10:14.060> an 00:10:15.050 --> 00:10:15.060 align:start position:0% friendly name and you can map it to an 00:10:15.060 --> 00:10:18.320 align:start position:0% friendly name and you can map it to an address<00:10:15.890> Burton<00:10:16.890> has<00:10:17.100> one<00:10:17.339> we<00:10:18.060> have<00:10:18.209> an 00:10:18.320 --> 00:10:18.330 align:start position:0% address Burton has one we have an 00:10:18.330 --> 00:10:22.040 align:start position:0% address Burton has one we have an identity<00:10:19.459> contract<00:10:20.459> where<00:10:21.149> we<00:10:21.300> publish 00:10:22.040 --> 00:10:22.050 align:start position:0% identity contract where we publish 00:10:22.050 --> 00:10:24.650 align:start position:0% identity contract where we publish identity<00:10:22.860> access<00:10:23.160> stations<00:10:23.580> for<00:10:24.209> all<00:10:24.420> of<00:10:24.570> the 00:10:24.650 --> 00:10:24.660 align:start position:0% identity access stations for all of the 00:10:24.660 --> 00:10:28.790 align:start position:0% identity access stations for all of the users<00:10:25.050> on<00:10:26.360> marketplace<00:10:27.410> but<00:10:28.410> as<00:10:28.529> you<00:10:28.620> might 00:10:28.790 --> 00:10:28.800 align:start position:0% users on marketplace but as you might 00:10:28.800 --> 00:10:31.280 align:start position:0% users on marketplace but as you might guess<00:10:28.950> by<00:10:29.010> now<00:10:29.220> we<00:10:29.820> don't<00:10:30.420> actually<00:10:30.870> store 00:10:31.280 --> 00:10:31.290 align:start position:0% guess by now we don't actually store 00:10:31.290 --> 00:10:35.300 align:start position:0% guess by now we don't actually store that<00:10:31.470> data<00:10:31.620> we<00:10:32.580> just<00:10:32.880> emit<00:10:33.390> events<00:10:34.160> and<00:10:35.160> what 00:10:35.300 --> 00:10:35.310 align:start position:0% that data we just emit events and what 00:10:35.310 --> 00:10:37.430 align:start position:0% that data we just emit events and what might<00:10:35.459> be<00:10:35.610> was<00:10:35.820> simply<00:10:36.480> smart<00:10:36.839> contracts<00:10:37.380> you 00:10:37.430 --> 00:10:37.440 align:start position:0% might be was simply smart contracts you 00:10:37.440 --> 00:10:40.310 align:start position:0% might be was simply smart contracts you can<00:10:37.589> have<00:10:37.800> basically<00:10:38.760> two<00:10:39.209> functions<00:10:39.690> they 00:10:40.310 --> 00:10:40.320 align:start position:0% can have basically two functions they 00:10:40.320 --> 00:10:44.660 align:start position:0% can have basically two functions they met<00:10:41.300> identity<00:10:42.300> updated<00:10:42.779> it's<00:10:43.410> you<00:10:44.399> know<00:10:44.610> the 00:10:44.660 --> 00:10:44.670 align:start position:0% met identity updated it's you know the 00:10:44.670 --> 00:10:47.660 align:start position:0% met identity updated it's you know the first<00:10:44.940> message<00:10:45.750> sender<00:10:46.350> of<00:10:46.529> your<00:10:46.800> wallet<00:10:47.010> and 00:10:47.660 --> 00:10:47.670 align:start position:0% first message sender of your wallet and 00:10:47.670 --> 00:10:50.180 align:start position:0% first message sender of your wallet and an<00:10:47.970> idea<00:10:48.300> pass<00:10:48.480> hash<00:10:48.720> with<00:10:49.320> the<00:10:49.529> artist 00:10:50.180 --> 00:10:50.190 align:start position:0% an idea pass hash with the artist 00:10:50.190 --> 00:10:52.460 align:start position:0% an idea pass hash with the artist stations<00:10:50.550> on<00:10:50.850> your<00:10:51.029> profile<00:10:51.450> and<00:10:52.140> then<00:10:52.350> we 00:10:52.460 --> 00:10:52.470 align:start position:0% stations on your profile and then we 00:10:52.470 --> 00:10:54.980 align:start position:0% stations on your profile and then we have<00:10:52.649> identity<00:10:53.430> deleted<00:10:53.970> which<00:10:54.570> if<00:10:54.720> you<00:10:54.839> ask 00:10:54.980 --> 00:10:54.990 align:start position:0% have identity deleted which if you ask 00:10:54.990 --> 00:10:58.220 align:start position:0% have identity deleted which if you ask nicely<00:10:55.260> we<00:10:55.860> will<00:10:56.070> delete<00:10:56.430> your<00:10:57.149> rule<00:10:57.630> unpin 00:10:58.220 --> 00:10:58.230 align:start position:0% nicely we will delete your rule unpin 00:10:58.230 --> 00:11:03.970 align:start position:0% nicely we will delete your rule unpin your<00:10:58.470> data<00:10:59.360> if<00:11:00.360> you<00:11:00.630> ask<00:11:00.839> us<00:11:00.990> to<00:11:01.050> from<00:11:02.040> ipfs 00:11:03.970 --> 00:11:03.980 align:start position:0% your data if you ask us to from ipfs 00:11:03.980 --> 00:11:07.010 align:start position:0% your data if you ask us to from ipfs factory<00:11:04.980> contracts<00:11:05.550> so<00:11:06.420> these<00:11:06.570> are<00:11:06.750> super 00:11:07.010 --> 00:11:07.020 align:start position:0% factory contracts so these are super 00:11:07.020 --> 00:11:09.860 align:start position:0% factory contracts so these are super useful<00:11:07.410> and<00:11:08.040> another<00:11:08.700> way<00:11:08.880> to<00:11:08.940> save<00:11:09.570> on<00:11:09.839> gas 00:11:09.860 --> 00:11:09.870 align:start position:0% useful and another way to save on gas 00:11:09.870 --> 00:11:12.410 align:start position:0% useful and another way to save on gas costs<00:11:10.589> they<00:11:11.070> allow<00:11:11.310> you<00:11:11.370> to<00:11:11.520> basically<00:11:11.640> clone 00:11:12.410 --> 00:11:12.420 align:start position:0% costs they allow you to basically clone 00:11:12.420 --> 00:11:14.990 align:start position:0% costs they allow you to basically clone an<00:11:12.899> existing<00:11:13.290> smart<00:11:14.070> contract<00:11:14.550> to<00:11:14.670> use<00:11:14.820> that 00:11:14.990 --> 00:11:15.000 align:start position:0% an existing smart contract to use that 00:11:15.000 --> 00:11:17.389 align:start position:0% an existing smart contract to use that as<00:11:15.120> a<00:11:15.149> template<00:11:15.630> for<00:11:16.350> the<00:11:16.410> code<00:11:16.709> that<00:11:16.860> you<00:11:17.130> want 00:11:17.389 --> 00:11:17.399 align:start position:0% as a template for the code that you want 00:11:17.399 --> 00:11:20.210 align:start position:0% as a template for the code that you want to<00:11:17.610> have<00:11:18.209> run<00:11:18.480> a<00:11:18.750> great<00:11:19.380> example<00:11:19.649> of<00:11:19.829> a<00:11:19.950> server 00:11:20.210 --> 00:11:20.220 align:start position:0% to have run a great example of a server 00:11:20.220 --> 00:11:22.819 align:start position:0% to have run a great example of a server enosis<00:11:20.730> multi-sig<00:11:21.300> watts<00:11:21.570> so<00:11:21.870> you<00:11:22.290> can<00:11:22.560> deploy 00:11:22.819 --> 00:11:22.829 align:start position:0% enosis multi-sig watts so you can deploy 00:11:22.829 --> 00:11:25.250 align:start position:0% enosis multi-sig watts so you can deploy your<00:11:22.950> own<00:11:23.279> multi<00:11:23.940> sync<00:11:24.240> with<00:11:24.600> your<00:11:24.779> own<00:11:24.899> funds 00:11:25.250 --> 00:11:25.260 align:start position:0% your own multi sync with your own funds 00:11:25.260 --> 00:11:27.920 align:start position:0% your own multi sync with your own funds and<00:11:25.500> patrol<00:11:25.860> it<00:11:26.010> but<00:11:26.910> it<00:11:27.029> uses<00:11:27.180> all<00:11:27.570> of<00:11:27.600> their 00:11:27.920 --> 00:11:27.930 align:start position:0% and patrol it but it uses all of their 00:11:27.930 --> 00:11:30.699 align:start position:0% and patrol it but it uses all of their code<00:11:28.170> and<00:11:28.620> you<00:11:28.980> can<00:11:29.010> deploy<00:11:29.940> that<00:11:29.970> in<00:11:30.209> a<00:11:30.270> very 00:11:30.699 --> 00:11:30.709 align:start position:0% code and you can deploy that in a very 00:11:30.709 --> 00:11:33.110 align:start position:0% code and you can deploy that in a very cost-efficient<00:11:31.709> way<00:11:31.920> and<00:11:32.700> we<00:11:32.820> do<00:11:32.940> this<00:11:33.060> for 00:11:33.110 --> 00:11:33.120 align:start position:0% cost-efficient way and we do this for 00:11:33.120 --> 00:11:36.019 align:start position:0% cost-efficient way and we do this for deploying<00:11:34.110> our<00:11:34.410> proxy<00:11:35.010> contracts<00:11:35.490> which 00:11:36.019 --> 00:11:36.029 align:start position:0% deploying our proxy contracts which 00:11:36.029 --> 00:11:38.720 align:start position:0% deploying our proxy contracts which we'll<00:11:36.209> get<00:11:36.360> into<00:11:36.420> a<00:11:37.050> little<00:11:37.380> bit<00:11:37.529> the<00:11:38.399> court<00:11:38.640> is 00:11:38.720 --> 00:11:38.730 align:start position:0% we'll get into a little bit the court is 00:11:38.730 --> 00:11:41.000 align:start position:0% we'll get into a little bit the court is really<00:11:38.820> simple<00:11:39.270> you<00:11:39.570> just<00:11:39.600> use<00:11:39.990> this<00:11:40.170> master 00:11:41.000 --> 00:11:41.010 align:start position:0% really simple you just use this master 00:11:41.010 --> 00:11:43.100 align:start position:0% really simple you just use this master coffee<00:11:41.430> you<00:11:41.700> pass<00:11:41.910> in<00:11:42.149> the<00:11:42.329> master<00:11:42.690> operative 00:11:43.100 --> 00:11:43.110 align:start position:0% coffee you pass in the master operative 00:11:43.110 --> 00:11:45.590 align:start position:0% coffee you pass in the master operative contract<00:11:43.560> you<00:11:43.709> want<00:11:43.829> to<00:11:44.040> call<00:11:44.700> and<00:11:45.329> then<00:11:45.450> use 00:11:45.590 --> 00:11:45.600 align:start position:0% contract you want to call and then use 00:11:45.600 --> 00:11:46.460 align:start position:0% contract you want to call and then use the<00:11:45.779> magical 00:11:46.460 --> 00:11:46.470 align:start position:0% the magical 00:11:46.470 --> 00:11:49.790 align:start position:0% the magical like<00:11:46.710> over<00:11:46.890> here<00:11:47.160> and<00:11:47.550> you<00:11:48.540> have<00:11:48.570> a<00:11:49.080> copy<00:11:49.350> of 00:11:49.790 --> 00:11:49.800 align:start position:0% like over here and you have a copy of 00:11:49.800 --> 00:11:54.620 align:start position:0% like over here and you have a copy of that<00:11:50.070> smart<00:11:50.640> contract<00:11:52.400> yes<00:11:53.450> what<00:11:54.450> are<00:11:54.480> the 00:11:54.620 --> 00:11:54.630 align:start position:0% that smart contract yes what are the 00:11:54.630 --> 00:11:58.430 align:start position:0% that smart contract yes what are the tricks<00:11:54.990> with<00:11:55.790> you<00:11:56.790> think<00:11:57.210> Museum<00:11:57.720> it's 00:11:58.430 --> 00:11:58.440 align:start position:0% tricks with you think Museum it's 00:11:58.440 --> 00:12:01.280 align:start position:0% tricks with you think Museum it's predictable<00:11:59.010> smart<00:11:59.370> contract<00:11:59.820> addresses<00:12:00.600> and 00:12:01.280 --> 00:12:01.290 align:start position:0% predictable smart contract addresses and 00:12:01.290 --> 00:12:03.350 align:start position:0% predictable smart contract addresses and so<00:12:01.470> you<00:12:01.560> can<00:12:01.740> actually<00:12:02.010> know<00:12:02.430> the<00:12:02.820> address<00:12:03.180> of 00:12:03.350 --> 00:12:03.360 align:start position:0% so you can actually know the address of 00:12:03.360 --> 00:12:06.020 align:start position:0% so you can actually know the address of a<00:12:03.450> smart<00:12:03.750> contract<00:12:04.160> reliably<00:12:05.160> before<00:12:05.850> it's 00:12:06.020 --> 00:12:06.030 align:start position:0% a smart contract reliably before it's 00:12:06.030 --> 00:12:08.410 align:start position:0% a smart contract reliably before it's even<00:12:06.180> enlightened<00:12:06.780> on<00:12:07.170> the<00:12:07.590> blockchain<00:12:07.860> and 00:12:08.410 --> 00:12:08.420 align:start position:0% even enlightened on the blockchain and 00:12:08.420 --> 00:12:10.610 align:start position:0% even enlightened on the blockchain and so<00:12:09.420> you<00:12:09.540> can<00:12:09.720> know<00:12:09.840> it<00:12:09.960> before<00:12:10.140> where<00:12:10.560> it 00:12:10.610 --> 00:12:10.620 align:start position:0% so you can know it before where it 00:12:10.620 --> 00:12:13.190 align:start position:0% so you can know it before where it exists<00:12:11.130> and<00:12:11.730> this<00:12:11.910> is<00:12:12.120> really<00:12:12.690> useful<00:12:13.080> for 00:12:13.190 --> 00:12:13.200 align:start position:0% exists and this is really useful for 00:12:13.200 --> 00:12:16.870 align:start position:0% exists and this is really useful for eliminating<00:12:14.010> the<00:12:14.160> need<00:12:14.460> for<00:12:14.820> a<00:12:15.420> name<00:12:15.810> registry 00:12:16.870 --> 00:12:16.880 align:start position:0% eliminating the need for a name registry 00:12:16.880 --> 00:12:23.600 align:start position:0% eliminating the need for a name registry so<00:12:17.880> we<00:12:18.240> can<00:12:18.510> do<00:12:18.720> is<00:12:19.140> pass<00:12:19.920> the<00:12:21.170> order<00:12:22.170> of<00:12:22.610> proxy 00:12:23.600 --> 00:12:23.610 align:start position:0% so we can do is pass the order of proxy 00:12:23.610 --> 00:12:27.250 align:start position:0% so we can do is pass the order of proxy contract<00:12:24.090> and<00:12:24.360> a<00:12:25.140> nonce<00:12:25.520> and<00:12:26.520> optional<00:12:26.970> bonds 00:12:27.250 --> 00:12:27.260 align:start position:0% contract and a nonce and optional bonds 00:12:27.260 --> 00:12:30.410 align:start position:0% contract and a nonce and optional bonds to<00:12:28.260> create<00:12:28.740> two<00:12:29.010> and<00:12:29.400> then<00:12:29.970> that<00:12:30.120> will<00:12:30.270> give 00:12:30.410 --> 00:12:30.420 align:start position:0% to create two and then that will give 00:12:30.420 --> 00:12:32.570 align:start position:0% to create two and then that will give you<00:12:30.510> the<00:12:30.660> address<00:12:30.930> of<00:12:31.350> where<00:12:32.040> that<00:12:32.190> proxy 00:12:32.570 --> 00:12:32.580 align:start position:0% you the address of where that proxy 00:12:32.580 --> 00:12:34.430 align:start position:0% you the address of where that proxy contractor<00:12:33.150> is<00:12:33.450> going<00:12:33.510> to<00:12:33.810> live<00:12:33.990> so<00:12:34.020> for 00:12:34.430 --> 00:12:34.440 align:start position:0% contractor is going to live so for 00:12:34.440 --> 00:12:37.430 align:start position:0% contractor is going to live so for origin<00:12:34.890> we<00:12:35.760> create<00:12:36.210> a<00:12:36.360> proxy<00:12:36.840> contract<00:12:37.260> for 00:12:37.430 --> 00:12:37.440 align:start position:0% origin we create a proxy contract for 00:12:37.440 --> 00:12:39.580 align:start position:0% origin we create a proxy contract for each<00:12:37.590> of<00:12:37.770> our<00:12:37.830> users<00:12:38.250> and<00:12:38.490> then<00:12:39.210> we 00:12:39.580 --> 00:12:39.590 align:start position:0% each of our users and then we 00:12:39.590 --> 00:12:41.600 align:start position:0% each of our users and then we deterministic<00:12:40.590> we<00:12:40.740> figure<00:12:41.010> out<00:12:41.160> where<00:12:41.430> that 00:12:41.600 --> 00:12:41.610 align:start position:0% deterministic we figure out where that 00:12:41.610 --> 00:12:44.240 align:start position:0% deterministic we figure out where that contract<00:12:42.180> is<00:12:42.690> going<00:12:42.750> to<00:12:43.080> live<00:12:43.260> and<00:12:43.560> that<00:12:44.070> way 00:12:44.240 --> 00:12:44.250 align:start position:0% contract is going to live and that way 00:12:44.250 --> 00:12:47.690 align:start position:0% contract is going to live and that way we<00:12:44.370> don't<00:12:44.400> have<00:12:44.640> to<00:12:44.970> use<00:12:45.350> a<00:12:46.350> name<00:12:46.980> registry<00:12:47.490> at 00:12:47.690 --> 00:12:47.700 align:start position:0% we don't have to use a name registry at 00:12:47.700 --> 00:12:50.090 align:start position:0% we don't have to use a name registry at all<00:12:47.970> for<00:12:48.360> doing<00:12:48.660> that<00:12:48.780> look<00:12:49.020> up<00:12:49.230> and<00:12:49.710> figuring 00:12:50.090 --> 00:12:50.100 align:start position:0% all for doing that look up and figuring 00:12:50.100 --> 00:12:52.610 align:start position:0% all for doing that look up and figuring out<00:12:50.220> who<00:12:51.060> we<00:12:51.240> are<00:12:51.390> we<00:12:51.630> are<00:12:51.660> a<00:12:51.780> proxy<00:12:52.170> contract 00:12:52.610 --> 00:12:52.620 align:start position:0% out who we are we are a proxy contract 00:12:52.620 --> 00:12:55.340 align:start position:0% out who we are we are a proxy contract will<00:12:53.100> actually<00:12:53.460> live<00:12:53.730> to<00:12:54.210> see<00:12:54.510> that<00:12:55.110> code 00:12:55.340 --> 00:12:55.350 align:start position:0% will actually live to see that code 00:12:55.350 --> 00:13:00.160 align:start position:0% will actually live to see that code right<00:12:55.380> here<00:12:55.620> on<00:12:56.130> how<00:12:56.610> you<00:12:57.180> do<00:12:57.390> that 00:13:00.160 --> 00:13:00.170 align:start position:0% 00:13:00.170 --> 00:13:02.920 align:start position:0% so<00:13:00.740> many<00:13:00.980> transactions<00:13:01.700> mentioned<00:13:02.600> it<00:13:02.690> in<00:13:02.810> the 00:13:02.920 --> 00:13:02.930 align:start position:0% so many transactions mentioned it in the 00:13:02.930 --> 00:13:05.740 align:start position:0% so many transactions mentioned it in the last<00:13:02.960> talk<00:13:04.000> manage<00:13:05.000> transactions<00:13:05.510> the<00:13:05.600> high 00:13:05.740 --> 00:13:05.750 align:start position:0% last talk manage transactions the high 00:13:05.750 --> 00:13:08.260 align:start position:0% last talk manage transactions the high levels<00:13:06.110> is<00:13:06.290> the<00:13:06.410> way<00:13:06.560> for<00:13:06.830> you<00:13:07.340> to<00:13:07.370> sponsor<00:13:07.940> the 00:13:08.260 --> 00:13:08.270 align:start position:0% levels is the way for you to sponsor the 00:13:08.270 --> 00:13:12.880 align:start position:0% levels is the way for you to sponsor the gas<00:13:08.480> on<00:13:09.200> behalf<00:13:09.710> of<00:13:10.010> your<00:13:10.730> users<00:13:11.440> and<00:13:12.440> this<00:13:12.770> is 00:13:12.880 --> 00:13:12.890 align:start position:0% gas on behalf of your users and this is 00:13:12.890 --> 00:13:14.790 align:start position:0% gas on behalf of your users and this is something<00:13:13.130> that<00:13:13.160> we<00:13:13.400> rolled<00:13:13.610> out<00:13:13.730> at<00:13:14.000> origin 00:13:14.790 --> 00:13:14.800 align:start position:0% something that we rolled out at origin 00:13:14.800 --> 00:13:18.520 align:start position:0% something that we rolled out at origin because<00:13:16.240> one<00:13:17.240> our<00:13:17.540> first-time<00:13:17.960> users<00:13:18.320> to<00:13:18.470> be 00:13:18.520 --> 00:13:18.530 align:start position:0% because one our first-time users to be 00:13:18.530 --> 00:13:20.020 align:start position:0% because one our first-time users to be able<00:13:18.560> to<00:13:18.740> get<00:13:18.860> up<00:13:19.040> and<00:13:19.280> create<00:13:19.610> a<00:13:19.640> listing 00:13:20.020 --> 00:13:20.030 align:start position:0% able to get up and create a listing 00:13:20.030 --> 00:13:22.270 align:start position:0% able to get up and create a listing without<00:13:20.330> having<00:13:20.660> to<00:13:20.840> have<00:13:21.050> a<00:13:21.350> few<00:13:21.830> pennies<00:13:22.010> of 00:13:22.270 --> 00:13:22.280 align:start position:0% without having to have a few pennies of 00:13:22.280 --> 00:13:25.510 align:start position:0% without having to have a few pennies of gas<00:13:22.460> in<00:13:22.700> their<00:13:23.120> wallet<00:13:23.740> the<00:13:24.740> challenges<00:13:25.250> the 00:13:25.510 --> 00:13:25.520 align:start position:0% gas in their wallet the challenges the 00:13:25.520 --> 00:13:28.930 align:start position:0% gas in their wallet the challenges the theorem<00:13:25.960> says<00:13:26.960> the<00:13:27.410> person<00:13:27.950> who<00:13:28.160> signs<00:13:28.790> a 00:13:28.930 --> 00:13:28.940 align:start position:0% theorem says the person who signs a 00:13:28.940 --> 00:13:31.330 align:start position:0% theorem says the person who signs a transaction<00:13:29.570> is<00:13:29.750> a<00:13:30.200> person<00:13:30.740> who<00:13:30.800> has<00:13:30.890> to<00:13:31.100> pay 00:13:31.330 --> 00:13:31.340 align:start position:0% transaction is a person who has to pay 00:13:31.340 --> 00:13:33.520 align:start position:0% transaction is a person who has to pay the<00:13:31.700> gas<00:13:31.850> you<00:13:32.120> can't<00:13:32.360> have<00:13:32.570> two<00:13:33.140> different 00:13:33.520 --> 00:13:33.530 align:start position:0% the gas you can't have two different 00:13:33.530 --> 00:13:35.740 align:start position:0% the gas you can't have two different signatures<00:13:33.800> on<00:13:34.310> a<00:13:34.340> transaction<00:13:35.000> and<00:13:35.570> so<00:13:35.600> you 00:13:35.740 --> 00:13:35.750 align:start position:0% signatures on a transaction and so you 00:13:35.750 --> 00:13:36.910 align:start position:0% signatures on a transaction and so you have<00:13:35.870> to<00:13:35.960> jump<00:13:36.140> through<00:13:36.320> all<00:13:36.410> these<00:13:36.620> crazy 00:13:36.910 --> 00:13:36.920 align:start position:0% have to jump through all these crazy 00:13:36.920 --> 00:13:39.250 align:start position:0% have to jump through all these crazy hoops<00:13:37.250> in<00:13:37.460> order<00:13:37.580> to<00:13:37.970> do<00:13:38.630> something<00:13:38.900> as<00:13:39.080> simple 00:13:39.250 --> 00:13:39.260 align:start position:0% hoops in order to do something as simple 00:13:39.260 --> 00:13:42.010 align:start position:0% hoops in order to do something as simple as<00:13:39.470> paying<00:13:39.770> the<00:13:40.010> gas<00:13:40.160> for<00:13:40.850> someone<00:13:41.180> else<00:13:41.360> and 00:13:42.010 --> 00:13:42.020 align:start position:0% as paying the gas for someone else and 00:13:42.020 --> 00:13:43.810 align:start position:0% as paying the gas for someone else and so<00:13:42.140> that's<00:13:42.290> what<00:13:42.470> we<00:13:42.560> use<00:13:42.710> our<00:13:43.040> proxy 00:13:43.810 --> 00:13:43.820 align:start position:0% so that's what we use our proxy 00:13:43.820 --> 00:13:46.180 align:start position:0% so that's what we use our proxy contracts<00:13:44.240> for<00:13:44.390> a<00:13:44.720> sign<00:13:45.230> of<00:13:45.380> transaction<00:13:45.950> you 00:13:46.180 --> 00:13:46.190 align:start position:0% contracts for a sign of transaction you 00:13:46.190 --> 00:13:48.730 align:start position:0% contracts for a sign of transaction you send<00:13:46.430> into<00:13:46.640> our<00:13:46.760> relay<00:13:47.090> our<00:13:47.780> relayer<00:13:48.290> then 00:13:48.730 --> 00:13:48.740 align:start position:0% send into our relay our relayer then 00:13:48.740 --> 00:13:50.500 align:start position:0% send into our relay our relayer then deploys<00:13:49.220> that<00:13:49.460> proxy<00:13:49.820> contract<00:13:50.240> if<00:13:50.390> it 00:13:50.500 --> 00:13:50.510 align:start position:0% deploys that proxy contract if it 00:13:50.510 --> 00:13:52.540 align:start position:0% deploys that proxy contract if it doesn't<00:13:50.720> already<00:13:50.810> exist<00:13:50.990> and<00:13:51.590> then<00:13:52.160> since 00:13:52.540 --> 00:13:52.550 align:start position:0% doesn't already exist and then since 00:13:52.550 --> 00:13:54.820 align:start position:0% doesn't already exist and then since that<00:13:52.910> you're<00:13:53.480> saying<00:13:53.750> to<00:13:53.990> contract<00:13:54.440> or<00:13:54.620> your 00:13:54.820 --> 00:13:54.830 align:start position:0% that you're saying to contract or your 00:13:54.830 --> 00:13:57.130 align:start position:0% that you're saying to contract or your signed<00:13:55.070> transaction<00:13:55.580> -<00:13:56.240> of<00:13:56.330> a<00:13:56.390> proxy<00:13:56.720> contract 00:13:57.130 --> 00:13:57.140 align:start position:0% signed transaction - of a proxy contract 00:13:57.140 --> 00:13:59.590 align:start position:0% signed transaction - of a proxy contract any<00:13:57.500> relays<00:13:57.860> along<00:13:58.100> to<00:13:58.820> the<00:13:58.970> destination 00:13:59.590 --> 00:13:59.600 align:start position:0% any relays along to the destination 00:13:59.600 --> 00:14:02.140 align:start position:0% any relays along to the destination contract<00:14:00.110> we<00:14:00.290> want<00:14:00.590> that<00:14:01.070> code<00:14:01.310> to<00:14:01.940> actually 00:14:02.140 --> 00:14:02.150 align:start position:0% contract we want that code to actually 00:14:02.150 --> 00:14:06.390 align:start position:0% contract we want that code to actually be<00:14:02.480> executed<00:14:03.220> and<00:14:04.220> so<00:14:04.790> the<00:14:04.880> end<00:14:05.090> result<00:14:05.210> is 00:14:06.390 --> 00:14:06.400 align:start position:0% be executed and so the end result is 00:14:06.400 --> 00:14:09.400 align:start position:0% be executed and so the end result is pop-up<00:14:07.400> it<00:14:07.580> looks<00:14:07.730> like<00:14:07.910> this<00:14:08.090> it<00:14:08.930> says<00:14:09.110> your 00:14:09.400 --> 00:14:09.410 align:start position:0% pop-up it looks like this it says your 00:14:09.410 --> 00:14:10.900 align:start position:0% pop-up it looks like this it says your signatures<00:14:09.770> being<00:14:09.950> requested<00:14:10.250> but<00:14:10.700> nope 00:14:10.900 --> 00:14:10.910 align:start position:0% signatures being requested but nope 00:14:10.910 --> 00:14:14.050 align:start position:0% signatures being requested but nope there's<00:14:11.720> no<00:14:11.780> gas<00:14:12.530> associated<00:14:13.520> with<00:14:13.610> it<00:14:13.730> so<00:14:13.910> now 00:14:14.050 --> 00:14:14.060 align:start position:0% there's no gas associated with it so now 00:14:14.060 --> 00:14:15.460 align:start position:0% there's no gas associated with it so now you<00:14:14.120> can<00:14:14.390> actually<00:14:14.510> write<00:14:14.900> the<00:14:15.110> other<00:14:15.170> to<00:14:15.380> the 00:14:15.460 --> 00:14:15.470 align:start position:0% you can actually write the other to the 00:14:15.470 --> 00:14:17.920 align:start position:0% you can actually write the other to the wall<00:14:15.620> chaining<00:14:16.040> thanks<00:14:16.370> acute<00:14:16.580> code<00:14:16.820> and<00:14:17.120> in 00:14:17.920 --> 00:14:17.930 align:start position:0% wall chaining thanks acute code and in 00:14:17.930 --> 00:14:19.930 align:start position:0% wall chaining thanks acute code and in yes<00:14:18.380> you<00:14:18.410> need<00:14:18.680> to<00:14:18.740> sign<00:14:19.040> it<00:14:19.190> to<00:14:19.340> prove<00:14:19.610> it<00:14:19.760> you 00:14:19.930 --> 00:14:19.940 align:start position:0% yes you need to sign it to prove it you 00:14:19.940 --> 00:14:22.150 align:start position:0% yes you need to sign it to prove it you control<00:14:20.450> of<00:14:20.630> wallet<00:14:20.930> you<00:14:21.410> don't<00:14:21.620> have<00:14:21.830> to<00:14:21.950> pay 00:14:22.150 --> 00:14:22.160 align:start position:0% control of wallet you don't have to pay 00:14:22.160 --> 00:14:27.270 align:start position:0% control of wallet you don't have to pay any<00:14:22.850> gas<00:14:24.730> so<00:14:25.730> let's<00:14:25.880> talk<00:14:26.000> a<00:14:26.060> little<00:14:26.270> bit<00:14:26.390> about 00:14:27.270 --> 00:14:27.280 align:start position:0% any gas so let's talk a little bit about 00:14:27.280 --> 00:14:29.770 align:start position:0% any gas so let's talk a little bit about different<00:14:28.280> options<00:14:28.550> for<00:14:28.970> upgrading<00:14:29.570> your 00:14:29.770 --> 00:14:29.780 align:start position:0% different options for upgrading your 00:14:29.780 --> 00:14:31.750 align:start position:0% different options for upgrading your code<00:14:30.170> all<00:14:30.890> right<00:14:31.010> we<00:14:31.220> don't<00:14:31.340> have<00:14:31.520> this 00:14:31.750 --> 00:14:31.760 align:start position:0% code all right we don't have this 00:14:31.760 --> 00:14:34.030 align:start position:0% code all right we don't have this problem<00:14:31.820> in<00:14:32.540> centralized<00:14:33.440> application<00:14:33.950> is 00:14:34.030 --> 00:14:34.040 align:start position:0% problem in centralized application is 00:14:34.040 --> 00:14:36.520 align:start position:0% problem in centralized application is very<00:14:34.070> easy<00:14:34.460> to<00:14:34.610> operate<00:14:34.730> your<00:14:35.120> code<00:14:35.380> but<00:14:36.380> in 00:14:36.520 --> 00:14:36.530 align:start position:0% very easy to operate your code but in 00:14:36.530 --> 00:14:38.110 align:start position:0% very easy to operate your code but in this<00:14:36.650> world<00:14:36.950> that<00:14:37.100> everything<00:14:37.370> is<00:14:37.760> immutable 00:14:38.110 --> 00:14:38.120 align:start position:0% this world that everything is immutable 00:14:38.120 --> 00:14:41.140 align:start position:0% this world that everything is immutable so<00:14:38.960> one<00:14:39.110> option<00:14:39.460> some<00:14:40.460> goes<00:14:40.940> by<00:14:41.090> different 00:14:41.140 --> 00:14:41.150 align:start position:0% so one option some goes by different 00:14:41.150 --> 00:14:44.020 align:start position:0% so one option some goes by different names<00:14:41.450> we<00:14:41.870> call<00:14:42.140> master<00:14:42.620> slave<00:14:42.890> you<00:14:43.640> have<00:14:43.790> one 00:14:44.020 --> 00:14:44.030 align:start position:0% names we call master slave you have one 00:14:44.030 --> 00:14:45.100 align:start position:0% names we call master slave you have one smart<00:14:44.450> contract 00:14:45.100 --> 00:14:45.110 align:start position:0% smart contract 00:14:45.110 --> 00:14:47.740 align:start position:0% smart contract it's<00:14:45.260> just<00:14:45.950> Italian<00:14:46.640> proxy<00:14:47.000> contract<00:14:47.450> to<00:14:47.570> tell 00:14:47.740 --> 00:14:47.750 align:start position:0% it's just Italian proxy contract to tell 00:14:47.750 --> 00:14:50.110 align:start position:0% it's just Italian proxy contract to tell everyone<00:14:47.960> hey<00:14:48.230> here's<00:14:48.650> our<00:14:48.800> proxy<00:14:49.190> here's<00:14:49.940> our 00:14:50.110 --> 00:14:50.120 align:start position:0% everyone hey here's our proxy here's our 00:14:50.120 --> 00:14:51.079 align:start position:0% everyone hey here's our proxy here's our code 00:14:51.079 --> 00:14:51.089 align:start position:0% code 00:14:51.089 --> 00:14:53.090 align:start position:0% code just<00:14:51.420> update<00:14:51.749> available<00:14:52.019> with<00:14:52.439> the<00:14:52.800> smart 00:14:53.090 --> 00:14:53.100 align:start position:0% just update available with the smart 00:14:53.100 --> 00:14:54.679 align:start position:0% just update available with the smart contract<00:14:53.309> but<00:14:53.670> actually<00:14:54.240> being<00:14:54.420> called 00:14:54.679 --> 00:14:54.689 align:start position:0% contract but actually being called 00:14:54.689 --> 00:14:56.989 align:start position:0% contract but actually being called behind<00:14:54.990> the<00:14:55.079> scenes<00:14:55.379> from<00:14:56.339> of<00:14:56.579> us<00:14:56.699> of<00:14:56.850> course 00:14:56.989 --> 00:14:56.999 align:start position:0% behind the scenes from of us of course 00:14:56.999 --> 00:14:58.519 align:start position:0% behind the scenes from of us of course is<00:14:57.240> you<00:14:57.360> have<00:14:57.480> to<00:14:57.629> interview<00:14:57.899> users<00:14:58.139> have<00:14:58.410> to 00:14:58.519 --> 00:14:58.529 align:start position:0% is you have to interview users have to 00:14:58.529 --> 00:15:00.319 align:start position:0% is you have to interview users have to trust<00:14:58.800> your<00:14:59.100> operators<00:14:59.490> be<00:14:59.639> delicious 00:15:00.319 --> 00:15:00.329 align:start position:0% trust your operators be delicious 00:15:00.329 --> 00:15:03.619 align:start position:0% trust your operators be delicious it's<00:15:00.779> well<00:15:01.079> been<00:15:01.850> malicious<00:15:02.850> smart<00:15:03.149> contract 00:15:03.619 --> 00:15:03.629 align:start position:0% it's well been malicious smart contract 00:15:03.629 --> 00:15:04.850 align:start position:0% it's well been malicious smart contract in<00:15:03.809> place<00:15:03.839> today 00:15:04.850 --> 00:15:04.860 align:start position:0% in place today 00:15:04.860 --> 00:15:06.650 align:start position:0% in place today yosef<00:15:05.490> is<00:15:05.610> probably<00:15:05.970> wreck<00:15:06.209> data<00:15:06.420> gets 00:15:06.650 --> 00:15:06.660 align:start position:0% yosef is probably wreck data gets 00:15:06.660 --> 00:15:08.689 align:start position:0% yosef is probably wreck data gets fragmented<00:15:07.110> because<00:15:07.410> every<00:15:07.769> time<00:15:08.009> you<00:15:08.550> update 00:15:08.689 --> 00:15:08.699 align:start position:0% fragmented because every time you update 00:15:08.699 --> 00:15:10.429 align:start position:0% fragmented because every time you update your<00:15:08.939> smart<00:15:09.180> contract<00:15:09.600> the<00:15:09.720> data<00:15:09.930> starts 00:15:10.429 --> 00:15:10.439 align:start position:0% your smart contract the data starts 00:15:10.439 --> 00:15:12.559 align:start position:0% your smart contract the data starts living<00:15:10.589> on<00:15:10.949> both<00:15:11.430> of<00:15:11.730> our<00:15:11.819> smart<00:15:12.120> contracts 00:15:12.559 --> 00:15:12.569 align:start position:0% living on both of our smart contracts 00:15:12.569 --> 00:15:17.090 align:start position:0% living on both of our smart contracts instead<00:15:12.889> okay<00:15:13.889> not<00:15:14.370> a<00:15:14.399> great<00:15:14.670> model<00:15:16.009> that<00:15:17.009> we 00:15:17.090 --> 00:15:17.100 align:start position:0% instead okay not a great model that we 00:15:17.100 --> 00:15:19.129 align:start position:0% instead okay not a great model that we do<00:15:17.459> it<00:15:17.550> is<00:15:17.670> store<00:15:18.029> your<00:15:18.240> data<00:15:18.420> your<00:15:18.779> logic 00:15:19.129 --> 00:15:19.139 align:start position:0% do it is store your data your logic 00:15:19.139 --> 00:15:21.499 align:start position:0% do it is store your data your logic separately<00:15:19.559> so<00:15:19.920> you<00:15:20.309> take<00:15:20.490> approximation<00:15:21.240> so 00:15:21.499 --> 00:15:21.509 align:start position:0% separately so you take approximation so 00:15:21.509 --> 00:15:23.689 align:start position:0% separately so you take approximation so cable<00:15:21.870> over<00:15:22.019> heaven<00:15:22.410> will<00:15:23.279> keep<00:15:23.399> all<00:15:23.490> the<00:15:23.550> data 00:15:23.689 --> 00:15:23.699 align:start position:0% cable over heaven will keep all the data 00:15:23.699 --> 00:15:25.400 align:start position:0% cable over heaven will keep all the data on<00:15:23.879> this<00:15:23.999> contract<00:15:24.480> but<00:15:24.600> will<00:15:24.720> just<00:15:24.749> bring<00:15:25.170> in 00:15:25.400 --> 00:15:25.410 align:start position:0% on this contract but will just bring in 00:15:25.410 --> 00:15:28.429 align:start position:0% on this contract but will just bring in new<00:15:25.680> smart<00:15:25.980> contracts<00:15:26.519> for<00:15:26.759> the<00:15:27.389> logic<00:15:27.839> and 00:15:28.429 --> 00:15:28.439 align:start position:0% new smart contracts for the logic and 00:15:28.439 --> 00:15:30.949 align:start position:0% new smart contracts for the logic and that<00:15:28.559> helps<00:15:28.889> quite<00:15:29.189> a<00:15:29.220> bit<00:15:29.509> but<00:15:30.509> you<00:15:30.660> still 00:15:30.949 --> 00:15:30.959 align:start position:0% that helps quite a bit but you still 00:15:30.959 --> 00:15:33.290 align:start position:0% that helps quite a bit but you still have<00:15:31.170> a<00:15:31.199> problem<00:15:31.410> what<00:15:32.069> if<00:15:32.220> we<00:15:32.370> change<00:15:32.699> the 00:15:33.290 --> 00:15:33.300 align:start position:0% have a problem what if we change the 00:15:33.300 --> 00:15:36.049 align:start position:0% have a problem what if we change the data<00:15:33.509> structure<00:15:34.249> so<00:15:35.249> how<00:15:35.610> do<00:15:35.670> you<00:15:35.790> do<00:15:35.910> that 00:15:36.049 --> 00:15:36.059 align:start position:0% data structure so how do you do that 00:15:36.059 --> 00:15:38.509 align:start position:0% data structure so how do you do that well<00:15:36.300> you<00:15:36.569> can<00:15:36.749> use<00:15:36.870> a<00:15:36.899> few<00:15:37.259> value<00:15:37.589> type 00:15:38.509 --> 00:15:38.519 align:start position:0% well you can use a few value type 00:15:38.519 --> 00:15:40.699 align:start position:0% well you can use a few value type structure<00:15:39.300> where<00:15:39.569> you<00:15:39.749> just<00:15:39.930> say<00:15:40.170> okay<00:15:40.559> we 00:15:40.699 --> 00:15:40.709 align:start position:0% structure where you just say okay we 00:15:40.709 --> 00:15:43.400 align:start position:0% structure where you just say okay we just<00:15:40.980> add<00:15:41.160> on<00:15:41.399> new<00:15:41.430> deals<00:15:41.910> and<00:15:42.240> anytime<00:15:42.480> that 00:15:43.400 --> 00:15:43.410 align:start position:0% just add on new deals and anytime that 00:15:43.410 --> 00:15:45.350 align:start position:0% just add on new deals and anytime that works<00:15:43.589> pretty<00:15:43.829> well<00:15:43.949> the<00:15:44.699> only<00:15:44.879> downside<00:15:45.329> is 00:15:45.350 --> 00:15:45.360 align:start position:0% works pretty well the only downside is 00:15:45.360 --> 00:15:47.809 align:start position:0% works pretty well the only downside is that<00:15:45.809> costs<00:15:46.470> a<00:15:46.499> lot<00:15:46.620> more<00:15:46.829> gas<00:15:47.040> to<00:15:47.490> all<00:15:47.579> that 00:15:47.809 --> 00:15:47.819 align:start position:0% that costs a lot more gas to all that 00:15:47.819 --> 00:15:51.369 align:start position:0% that costs a lot more gas to all that sort<00:15:48.089> of<00:15:48.149> computation<00:15:48.930> and<00:15:49.110> remapping<00:15:49.740> stuff 00:15:51.369 --> 00:15:51.379 align:start position:0% sort of computation and remapping stuff 00:15:51.379 --> 00:15:53.869 align:start position:0% sort of computation and remapping stuff the<00:15:52.379> other<00:15:52.410> day<00:15:52.800> you<00:15:53.279> can<00:15:53.370> just<00:15:53.519> pause<00:15:53.699> the 00:15:53.869 --> 00:15:53.879 align:start position:0% the other day you can just pause the 00:15:53.879 --> 00:15:55.249 align:start position:0% the other day you can just pause the contracting<00:15:54.420> to<00:15:54.509> start<00:15:54.779> over 00:15:55.249 --> 00:15:55.259 align:start position:0% contracting to start over 00:15:55.259 --> 00:15:58.939 align:start position:0% contracting to start over thank<00:15:55.559> poor<00:15:55.860> everything<00:15:56.309> over<00:15:56.660> and<00:15:57.660> just<00:15:58.559> do 00:15:58.939 --> 00:15:58.949 align:start position:0% thank poor everything over and just do 00:15:58.949 --> 00:16:00.759 align:start position:0% thank poor everything over and just do it<00:15:59.069> again<00:15:59.129> it's<00:15:59.759> depending<00:16:00.300> on<00:16:00.389> your<00:16:00.480> scenario 00:16:00.759 --> 00:16:00.769 align:start position:0% it again it's depending on your scenario 00:16:00.769 --> 00:16:03.639 align:start position:0% it again it's depending on your scenario sometimes<00:16:01.769> that<00:16:02.309> makes<00:16:02.550> sense 00:16:03.639 --> 00:16:03.649 align:start position:0% sometimes that makes sense 00:16:03.649 --> 00:16:06.819 align:start position:0% sometimes that makes sense so<00:16:04.649> what<00:16:05.069> we<00:16:05.189> do<00:16:05.339> at<00:16:05.429> our<00:16:05.519> origin<00:16:05.910> is<00:16:05.939> we<00:16:06.179> say 00:16:06.819 --> 00:16:06.829 align:start position:0% so what we do at our origin is we say 00:16:06.829 --> 00:16:09.919 align:start position:0% so what we do at our origin is we say like<00:16:07.829> a<00:16:08.069> lot<00:16:08.429> of<00:16:08.459> things<00:16:08.579> we'll<00:16:09.209> just<00:16:09.389> do<00:16:09.540> it<00:16:09.569> in 00:16:09.919 --> 00:16:09.929 align:start position:0% like a lot of things we'll just do it in 00:16:09.929 --> 00:16:12.860 align:start position:0% like a lot of things we'll just do it in JavaScript<00:16:10.319> instead<00:16:11.059> keep<00:16:12.059> our<00:16:12.240> smart 00:16:12.860 --> 00:16:12.870 align:start position:0% JavaScript instead keep our smart 00:16:12.870 --> 00:16:15.079 align:start position:0% JavaScript instead keep our smart contracts<00:16:13.379> is<00:16:13.620> DOM<00:16:14.309> and<00:16:14.339> as<00:16:14.670> simple<00:16:14.910> as 00:16:15.079 --> 00:16:15.089 align:start position:0% contracts is DOM and as simple as 00:16:15.089 --> 00:16:18.350 align:start position:0% contracts is DOM and as simple as possible<00:16:15.179> and<00:16:16.309> instead<00:16:17.309> will<00:16:17.490> write<00:16:17.670> adapters 00:16:18.350 --> 00:16:18.360 align:start position:0% possible and instead will write adapters 00:16:18.360 --> 00:16:21.019 align:start position:0% possible and instead will write adapters and<00:16:18.689> know<00:16:18.870> how<00:16:19.050> to<00:16:19.110> transform<00:16:19.800> between<00:16:20.519> each 00:16:21.019 --> 00:16:21.029 align:start position:0% and know how to transform between each 00:16:21.029 --> 00:16:22.730 align:start position:0% and know how to transform between each of<00:16:21.059> a<00:16:21.269> different<00:16:21.300> versions<00:16:22.110> of<00:16:22.170> our<00:16:22.439> smart 00:16:22.730 --> 00:16:22.740 align:start position:0% of a different versions of our smart 00:16:22.740 --> 00:16:24.259 align:start position:0% of a different versions of our smart contract<00:16:23.220> and<00:16:23.670> you<00:16:23.790> can<00:16:23.939> apply<00:16:24.209> these 00:16:24.259 --> 00:16:24.269 align:start position:0% contract and you can apply these 00:16:24.269 --> 00:16:26.929 align:start position:0% contract and you can apply these adapters<00:16:24.959> recursively<00:16:25.679> so<00:16:25.980> every<00:16:26.279> version 00:16:26.929 --> 00:16:26.939 align:start position:0% adapters recursively so every version 00:16:26.939 --> 00:16:28.639 align:start position:0% adapters recursively so every version knows<00:16:27.329> how<00:16:27.480> to<00:16:27.540> get<00:16:27.720> back<00:16:27.899> to<00:16:28.110> the<00:16:28.439> previous 00:16:28.639 --> 00:16:28.649 align:start position:0% knows how to get back to the previous 00:16:28.649 --> 00:16:32.449 align:start position:0% knows how to get back to the previous version<00:16:29.189> and<00:16:29.309> you<00:16:29.819> can<00:16:30.029> very<00:16:30.509> simply<00:16:31.459> adapt 00:16:32.449 --> 00:16:32.459 align:start position:0% version and you can very simply adapt 00:16:32.459 --> 00:16:36.210 align:start position:0% version and you can very simply adapt your<00:16:32.929> gap<00:16:34.040> across<00:16:35.040> these<00:16:35.220> different<00:16:35.399> versions 00:16:36.210 --> 00:16:36.220 align:start position:0% your gap across these different versions 00:16:36.220 --> 00:16:39.420 align:start position:0% your gap across these different versions you're<00:16:36.370> smart<00:16:36.670> contract<00:16:38.100> so<00:16:39.100> let's<00:16:39.250> talk<00:16:39.370> a 00:16:39.420 --> 00:16:39.430 align:start position:0% you're smart contract so let's talk a 00:16:39.430 --> 00:16:41.760 align:start position:0% you're smart contract so let's talk a little<00:16:39.640> bit<00:16:39.790> about<00:16:39.820> UX<00:16:40.660> how<00:16:41.110> many<00:16:41.290> of<00:16:41.440> you<00:16:41.620> have 00:16:41.760 --> 00:16:41.770 align:start position:0% little bit about UX how many of you have 00:16:41.770 --> 00:16:45.230 align:start position:0% little bit about UX how many of you have seen<00:16:42.490> this<00:16:42.670> type<00:16:42.940> of<00:16:43.050> pop-up<00:16:44.130> common 00:16:45.230 --> 00:16:45.240 align:start position:0% seen this type of pop-up common 00:16:45.240 --> 00:16:51.840 align:start position:0% seen this type of pop-up common manifested<00:16:46.240> for<00:16:46.480> what<00:16:47.700> what<00:16:49.920> makes<00:16:50.920> no<00:16:51.370> sense 00:16:51.840 --> 00:16:51.850 align:start position:0% manifested for what what makes no sense 00:16:51.850 --> 00:16:56.010 align:start position:0% manifested for what what makes no sense to<00:16:52.180> me<00:16:52.540> let<00:16:53.530> alone<00:16:53.560> the<00:16:54.220> average<00:16:54.250> user<00:16:54.760> what<00:16:55.690> is 00:16:56.010 --> 00:16:56.020 align:start position:0% to me let alone the average user what is 00:16:56.020 --> 00:16:58.230 align:start position:0% to me let alone the average user what is this<00:16:56.410> why<00:16:56.860> is<00:16:56.890> this<00:16:57.340> popping<00:16:57.730> out<00:16:57.850> the<00:16:57.970> minute 00:16:58.230 --> 00:16:58.240 align:start position:0% this why is this popping out the minute 00:16:58.240 --> 00:17:01.010 align:start position:0% this why is this popping out the minute I<00:16:58.420> tried<00:16:59.110> and<00:16:59.410> there's<00:16:59.560> any<00:16:59.920> sort<00:17:00.160> of 00:17:01.010 --> 00:17:01.020 align:start position:0% I tried and there's any sort of 00:17:01.020 --> 00:17:04.350 align:start position:0% I tried and there's any sort of decentralized<00:17:02.020> exchange<00:17:03.000> and<00:17:04.000> so<00:17:04.089> reason 00:17:04.350 --> 00:17:04.360 align:start position:0% decentralized exchange and so reason 00:17:04.360 --> 00:17:06.870 align:start position:0% decentralized exchange and so reason you're<00:17:04.510> seeing<00:17:04.689> this<00:17:04.930> is<00:17:05.079> because<00:17:05.530> of<00:17:05.949> the 00:17:06.870 --> 00:17:06.880 align:start position:0% you're seeing this is because of the 00:17:06.880 --> 00:17:09.240 align:start position:0% you're seeing this is because of the fact<00:17:07.120> that<00:17:07.270> you<00:17:07.600> have<00:17:07.810> to<00:17:08.020> move<00:17:08.439> in<00:17:08.620> your<00:17:08.770> c28 00:17:09.240 --> 00:17:09.250 align:start position:0% fact that you have to move in your c28 00:17:09.250 --> 00:17:11.280 align:start position:0% fact that you have to move in your c28 token<00:17:09.850> or<00:17:10.209> for<00:17:10.449> a<00:17:10.480> smart<00:17:10.720> contract<00:17:10.870> to<00:17:11.170> move 00:17:11.280 --> 00:17:11.290 align:start position:0% token or for a smart contract to move 00:17:11.290 --> 00:17:13.829 align:start position:0% token or for a smart contract to move near<00:17:11.470> c22<00:17:11.980> okay<00:17:12.280> it<00:17:12.819> first<00:17:13.209> has<00:17:13.480> to<00:17:13.510> have 00:17:13.829 --> 00:17:13.839 align:start position:0% near c22 okay it first has to have 00:17:13.839 --> 00:17:16.500 align:start position:0% near c22 okay it first has to have approval<00:17:14.770> from<00:17:15.339> user<00:17:15.640> that<00:17:16.000> makes<00:17:16.240> sense 00:17:16.500 --> 00:17:16.510 align:start position:0% approval from user that makes sense 00:17:16.510 --> 00:17:19.910 align:start position:0% approval from user that makes sense these<00:17:16.810> they<00:17:16.990> have<00:17:17.020> an<00:17:17.260> allowance<00:17:17.880> on<00:17:18.880> how<00:17:19.270> much 00:17:19.910 --> 00:17:19.920 align:start position:0% these they have an allowance on how much 00:17:19.920 --> 00:17:24.960 align:start position:0% these they have an allowance on how much how<00:17:20.920> many<00:17:20.980> tokens<00:17:21.490> is<00:17:21.880> allowed<00:17:22.180> to<00:17:22.540> do<00:17:23.520> so<00:17:24.520> the 00:17:24.960 --> 00:17:24.970 align:start position:0% how many tokens is allowed to do so the 00:17:24.970 --> 00:17:27.630 align:start position:0% how many tokens is allowed to do so the problem<00:17:25.300> is<00:17:25.329> is<00:17:25.510> that<00:17:25.620> you<00:17:26.620> have<00:17:26.860> two 00:17:27.630 --> 00:17:27.640 align:start position:0% problem is is that you have two 00:17:27.640 --> 00:17:29.640 align:start position:0% problem is is that you have two different<00:17:27.670> meta<00:17:28.569> max<00:17:28.780> pop-ups<00:17:29.290> that's<00:17:29.530> how 00:17:29.640 --> 00:17:29.650 align:start position:0% different meta max pop-ups that's how 00:17:29.650 --> 00:17:32.250 align:start position:0% different meta max pop-ups that's how you<00:17:29.710> have<00:17:30.490> to<00:17:30.610> do<00:17:30.730> to<00:17:30.910> do<00:17:31.060> anything<00:17:31.480> related<00:17:32.230> to 00:17:32.250 --> 00:17:32.260 align:start position:0% you have to do to do anything related to 00:17:32.260 --> 00:17:34.790 align:start position:0% you have to do to do anything related to tokens<00:17:32.770> one<00:17:33.040> you<00:17:33.610> have<00:17:33.730> this<00:17:33.850> crazy<00:17:34.120> thing<00:17:34.450> and 00:17:34.790 --> 00:17:34.800 align:start position:0% tokens one you have this crazy thing and 00:17:34.800 --> 00:17:36.870 align:start position:0% tokens one you have this crazy thing and then<00:17:35.800> you<00:17:35.950> have<00:17:36.070> a<00:17:36.100> second<00:17:36.460> one<00:17:36.610> which 00:17:36.870 --> 00:17:36.880 align:start position:0% then you have a second one which 00:17:36.880 --> 00:17:38.520 align:start position:0% then you have a second one which actually<00:17:37.270> pokes<00:17:37.510> a<00:17:37.660> smart<00:17:37.930> contract<00:17:38.140> to 00:17:38.520 --> 00:17:38.530 align:start position:0% actually pokes a smart contract to 00:17:38.530 --> 00:17:41.460 align:start position:0% actually pokes a smart contract to actually<00:17:38.830> move<00:17:39.130> the<00:17:40.030> tokens<00:17:40.750> to<00:17:40.930> where<00:17:41.110> they 00:17:41.460 --> 00:17:41.470 align:start position:0% actually move the tokens to where they 00:17:41.470 --> 00:17:43.710 align:start position:0% actually move the tokens to where they need<00:17:41.620> to<00:17:41.650> be<00:17:41.770> the<00:17:42.760> reason<00:17:43.000> you're<00:17:43.270> seeing<00:17:43.480> this 00:17:43.710 --> 00:17:43.720 align:start position:0% need to be the reason you're seeing this 00:17:43.720 --> 00:17:46.170 align:start position:0% need to be the reason you're seeing this that's<00:17:44.200> pretty<00:17:44.500> easy<00:17:44.530> pop<00:17:44.950> out<00:17:45.130> is<00:17:45.250> very<00:17:45.430> they 00:17:46.170 --> 00:17:46.180 align:start position:0% that's pretty easy pop out is very they 00:17:46.180 --> 00:17:47.880 align:start position:0% that's pretty easy pop out is very they don't<00:17:46.360> want<00:17:46.600> to<00:17:46.690> show<00:17:46.840> us<00:17:46.990> to<00:17:47.140> you<00:17:47.230> once<00:17:47.470> and<00:17:47.770> so 00:17:47.880 --> 00:17:47.890 align:start position:0% don't want to show us to you once and so 00:17:47.890 --> 00:17:49.500 align:start position:0% don't want to show us to you once and so we<00:17:47.980> just<00:17:48.160> go<00:17:48.280> ahead<00:17:48.550> and<00:17:48.640> ask<00:17:48.730> for<00:17:49.000> like<00:17:49.210> and 00:17:49.500 --> 00:17:49.510 align:start position:0% we just go ahead and ask for like and 00:17:49.510 --> 00:17:52.140 align:start position:0% we just go ahead and ask for like and basically<00:17:50.200> in<00:17:50.590> phenomena<00:17:51.100> of<00:17:51.340> tokens<00:17:51.850> that 00:17:52.140 --> 00:17:52.150 align:start position:0% basically in phenomena of tokens that 00:17:52.150 --> 00:17:54.960 align:start position:0% basically in phenomena of tokens that they<00:17:52.930> should<00:17:53.170> want<00:17:53.380> to<00:17:53.500> be<00:17:53.590> able<00:17:53.680> to<00:17:53.800> move<00:17:53.980> but 00:17:54.960 --> 00:17:54.970 align:start position:0% they should want to be able to move but 00:17:54.970 --> 00:17:57.830 align:start position:0% they should want to be able to move but it<00:17:55.390> was<00:17:55.600> very<00:17:56.080> confusing<00:17:56.380> user<00:17:57.100> experience 00:17:57.830 --> 00:17:57.840 align:start position:0% it was very confusing user experience 00:17:57.840 --> 00:17:59.610 align:start position:0% it was very confusing user experience and<00:17:58.840> now<00:17:58.960> we're<00:17:59.110> going<00:17:59.230> to<00:17:59.290> be<00:17:59.350> more<00:17:59.470> lenient 00:17:59.610 --> 00:17:59.620 align:start position:0% and now we're going to be more lenient 00:17:59.620 --> 00:18:02.730 align:start position:0% and now we're going to be more lenient but<00:18:00.520> an<00:18:00.730> Orangeman<00:18:01.000> like<00:18:01.240> how<00:18:02.050> do<00:18:02.110> we<00:18:02.230> get<00:18:02.470> rid 00:18:02.730 --> 00:18:02.740 align:start position:0% but an Orangeman like how do we get rid 00:18:02.740 --> 00:18:05.820 align:start position:0% but an Orangeman like how do we get rid of<00:18:02.770> that<00:18:02.890> right<00:18:03.340> huh<00:18:03.670> me<00:18:03.850> we<00:18:04.780> how<00:18:05.140> do<00:18:05.200> we<00:18:05.380> live 00:18:05.820 --> 00:18:05.830 align:start position:0% of that right huh me we how do we live 00:18:05.830 --> 00:18:08.190 align:start position:0% of that right huh me we how do we live our<00:18:06.190> tokens<00:18:06.610> from<00:18:06.790> our<00:18:07.150> marketplace<00:18:07.630> contract 00:18:08.190 --> 00:18:08.200 align:start position:0% our tokens from our marketplace contract 00:18:08.200 --> 00:18:10.140 align:start position:0% our tokens from our marketplace contract without<00:18:08.620> having<00:18:09.040> to<00:18:09.100> show<00:18:09.160> that<00:18:09.580> mana<00:18:09.940> mass 00:18:10.140 --> 00:18:10.150 align:start position:0% without having to show that mana mass 00:18:10.150 --> 00:18:13.320 align:start position:0% without having to show that mana mass pop<00:18:10.420> up<00:18:10.660> every<00:18:11.320> time<00:18:11.580> and<00:18:12.580> so<00:18:12.730> looks<00:18:13.240> like 00:18:13.320 --> 00:18:13.330 align:start position:0% pop up every time and so looks like 00:18:13.330 --> 00:18:14.640 align:start position:0% pop up every time and so looks like there's<00:18:13.630> prior<00:18:13.840> to<00:18:13.930> working<00:18:14.110> on<00:18:14.260> this<00:18:14.440> first 00:18:14.640 --> 00:18:14.650 align:start position:0% there's prior to working on this first 00:18:14.650 --> 00:18:16.590 align:start position:0% there's prior to working on this first GRC<00:18:15.390> 8:27 00:18:16.590 --> 00:18:16.600 align:start position:0% GRC 8:27 00:18:16.600 --> 00:18:19.830 align:start position:0% GRC 8:27 which<00:18:18.360> proposed 00:18:19.830 --> 00:18:19.840 align:start position:0% which proposed 00:18:19.840 --> 00:18:21.660 align:start position:0% which proposed combining<00:18:20.800> these<00:18:20.860> into<00:18:21.130> a<00:18:21.160> single<00:18:21.490> step 00:18:21.660 --> 00:18:21.670 align:start position:0% combining these into a single step 00:18:21.670 --> 00:18:24.270 align:start position:0% combining these into a single step approved<00:18:22.270> and<00:18:22.600> called<00:18:23.170> let's<00:18:23.740> just<00:18:23.920> do<00:18:24.070> them 00:18:24.270 --> 00:18:24.280 align:start position:0% approved and called let's just do them 00:18:24.280 --> 00:18:26.430 align:start position:0% approved and called let's just do them both<00:18:24.490> at<00:18:24.700> the<00:18:24.790> same<00:18:24.850> time<00:18:25.300> I<00:18:25.660> would<00:18:26.110> say<00:18:26.200> great 00:18:26.430 --> 00:18:26.440 align:start position:0% both at the same time I would say great 00:18:26.440 --> 00:18:28.110 align:start position:0% both at the same time I would say great this<00:18:26.650> is<00:18:26.860> this<00:18:27.280> is<00:18:27.400> awesome<00:18:27.730> this<00:18:27.760> is<00:18:28.000> what 00:18:28.110 --> 00:18:28.120 align:start position:0% this is this is awesome this is what 00:18:28.120 --> 00:18:28.800 align:start position:0% this is this is awesome this is what we're<00:18:28.300> looking<00:18:28.330> for 00:18:28.800 --> 00:18:28.810 align:start position:0% we're looking for 00:18:28.810 --> 00:18:30.780 align:start position:0% we're looking for and<00:18:29.110> then<00:18:29.740> we<00:18:29.830> started<00:18:30.100> reading<00:18:30.340> the<00:18:30.400> comments 00:18:30.780 --> 00:18:30.790 align:start position:0% and then we started reading the comments 00:18:30.790 --> 00:18:31.460 align:start position:0% and then we started reading the comments on<00:18:30.910> it 00:18:31.460 --> 00:18:31.470 align:start position:0% on it 00:18:31.470 --> 00:18:33.560 align:start position:0% on it it's<00:18:31.860> acceptable<00:18:32.730> to<00:18:32.850> every<00:18:33.390> inch<00:18:33.480> the 00:18:33.560 --> 00:18:33.570 align:start position:0% it's acceptable to every inch the 00:18:33.570 --> 00:18:39.740 align:start position:0% it's acceptable to every inch the attacks<00:18:34.880> but<00:18:36.530> we<00:18:37.530> realized<00:18:37.919> that<00:18:38.690> the<00:18:39.690> only 00:18:39.740 --> 00:18:39.750 align:start position:0% attacks but we realized that the only 00:18:39.750 --> 00:18:43.640 align:start position:0% attacks but we realized that the only problem<00:18:40.380> but<00:18:40.679> you<00:18:41.130> can't<00:18:41.370> use<00:18:41.909> that<00:18:41.940> with<00:18:42.650> any 00:18:43.640 --> 00:18:43.650 align:start position:0% problem but you can't use that with any 00:18:43.650 --> 00:18:46.159 align:start position:0% problem but you can't use that with any untrusted<00:18:44.280> smart<00:18:44.549> contract<00:18:45.030> but<00:18:45.750> if<00:18:45.870> you<00:18:45.990> have 00:18:46.159 --> 00:18:46.169 align:start position:0% untrusted smart contract but if you have 00:18:46.169 --> 00:18:48.649 align:start position:0% untrusted smart contract but if you have your<00:18:46.350> own<00:18:46.559> trusted<00:18:47.130> smart<00:18:47.400> contract<00:18:47.940> you<00:18:48.480> can 00:18:48.649 --> 00:18:48.659 align:start position:0% your own trusted smart contract you can 00:18:48.659 --> 00:18:50.450 align:start position:0% your own trusted smart contract you can actually<00:18:48.960> lock<00:18:49.230> this<00:18:49.470> down<00:18:49.740> you<00:18:50.100> can<00:18:50.159> actually 00:18:50.450 --> 00:18:50.460 align:start position:0% actually lock this down you can actually 00:18:50.460 --> 00:18:54.860 align:start position:0% actually lock this down you can actually have<00:18:51.000> a<00:18:51.360> protocol<00:18:52.350> Westerner<00:18:53.309> and<00:18:53.970> so<00:18:54.210> what<00:18:54.690> we 00:18:54.860 --> 00:18:54.870 align:start position:0% have a protocol Westerner and so what we 00:18:54.870 --> 00:18:57.620 align:start position:0% have a protocol Westerner and so what we did<00:18:55.080> our<00:18:55.559> tame<00:18:55.890> this<00:18:56.130> is<00:18:56.340> live<00:18:56.520> on<00:18:56.760> our<00:18:56.940> you 00:18:57.620 --> 00:18:57.630 align:start position:0% did our tame this is live on our you 00:18:57.630 --> 00:18:59.990 align:start position:0% did our tame this is live on our you know<00:18:57.710> c20<00:18:58.710> contract<00:18:59.250> has<00:18:59.400> been<00:18:59.429> audited<00:18:59.970> by 00:18:59.990 --> 00:19:00.000 align:start position:0% know c20 contract has been audited by 00:19:00.000 --> 00:19:03.169 align:start position:0% know c20 contract has been audited by kilobits<00:19:00.690> you<00:19:01.559> can<00:19:01.740> actually<00:19:01.919> safely<00:19:02.549> buying 00:19:03.169 --> 00:19:03.179 align:start position:0% kilobits you can actually safely buying 00:19:03.179 --> 00:19:07.270 align:start position:0% kilobits you can actually safely buying those<00:19:03.390> two<00:19:03.659> into<00:19:04.500> one<00:19:04.530> step<00:19:05.100> and<00:19:05.400> so<00:19:06.049> your 00:19:07.270 --> 00:19:07.280 align:start position:0% those two into one step and so your 00:19:07.280 --> 00:19:10.190 align:start position:0% those two into one step and so your users<00:19:08.280> only<00:19:08.520> prompted<00:19:08.970> one<00:19:09.090> time<00:19:09.360> to<00:19:09.990> both 00:19:10.190 --> 00:19:10.200 align:start position:0% users only prompted one time to both 00:19:10.200 --> 00:19:14.180 align:start position:0% users only prompted one time to both approve<00:19:10.650> and<00:19:11.150> call<00:19:12.409> whenever<00:19:13.409> we<00:19:13.559> use<00:19:13.740> order 00:19:14.180 --> 00:19:14.190 align:start position:0% approve and call whenever we use order 00:19:14.190 --> 00:19:18.260 align:start position:0% approve and call whenever we use order tool<00:19:14.400> kits<00:19:14.669> on<00:19:14.970> or<00:19:15.360> is<00:19:15.480> this<00:19:15.630> marketplace<00:19:17.270> and 00:19:18.260 --> 00:19:18.270 align:start position:0% tool kits on or is this marketplace and 00:19:18.270 --> 00:19:21.140 align:start position:0% tool kits on or is this marketplace and here<00:19:18.510> is<00:19:18.659> the<00:19:19.320> code<00:19:19.500> of<00:19:19.950> how<00:19:20.490> you<00:19:20.549> do<00:19:20.880> that's 00:19:21.140 --> 00:19:21.150 align:start position:0% here is the code of how you do that's 00:19:21.150 --> 00:19:22.700 align:start position:0% here is the code of how you do that's very<00:19:21.570> simple<00:19:21.809> the<00:19:22.049> only<00:19:22.230> thing<00:19:22.380> we<00:19:22.500> really 00:19:22.700 --> 00:19:22.710 align:start position:0% very simple the only thing we really 00:19:22.710 --> 00:19:27.560 align:start position:0% very simple the only thing we really added<00:19:23.280> to<00:19:25.549> say<00:19:26.549> this<00:19:26.730> was<00:19:26.970> just<00:19:27.150> put<00:19:27.360> the 00:19:27.560 --> 00:19:27.570 align:start position:0% added to say this was just put the 00:19:27.570 --> 00:19:31.310 align:start position:0% added to say this was just put the whitelist<00:19:27.960> and<00:19:29.090> so<00:19:30.090> I<00:19:30.120> think<00:19:30.419> I'm<00:19:30.720> pretty<00:19:31.200> much 00:19:31.310 --> 00:19:31.320 align:start position:0% whitelist and so I think I'm pretty much 00:19:31.320 --> 00:19:33.440 align:start position:0% whitelist and so I think I'm pretty much out<00:19:31.530> of<00:19:31.590> time<00:19:31.679> here<00:19:32.039> but<00:19:32.280> last<00:19:32.970> time<00:19:33.150> I'll<00:19:33.270> say 00:19:33.440 --> 00:19:33.450 align:start position:0% out of time here but last time I'll say 00:19:33.450 --> 00:19:38.120 align:start position:0% out of time here but last time I'll say towards<00:19:34.169> is<00:19:34.260> 100%<00:19:34.710> open<00:19:35.429> source<00:19:35.730> and<00:19:36.169> and<00:19:37.169> all 00:19:38.120 --> 00:19:38.130 align:start position:0% towards is 100% open source and and all 00:19:38.130 --> 00:19:40.700 align:start position:0% towards is 100% open source and and all over<00:19:38.370> do<00:19:38.880> all<00:19:39.120> our<00:19:39.270> work<00:19:39.299> in<00:19:39.539> public<00:19:39.900> so<00:19:40.320> you 00:19:40.700 --> 00:19:40.710 align:start position:0% over do all our work in public so you 00:19:40.710 --> 00:19:44.000 align:start position:0% over do all our work in public so you know<00:19:41.549> come<00:19:41.820> join<00:19:42.030> us<00:19:42.270> in<00:19:43.049> our<00:19:43.200> escort<00:19:43.770> we<00:19:43.890> have 00:19:44.000 --> 00:19:44.010 align:start position:0% know come join us in our escort we have 00:19:44.010 --> 00:19:46.100 align:start position:0% know come join us in our escort we have over<00:19:44.220> 160<00:19:44.700> contributors<00:19:45.450> to<00:19:45.570> our<00:19:45.659> code<00:19:45.929> base 00:19:46.100 --> 00:19:46.110 align:start position:0% over 160 contributors to our code base 00:19:46.110 --> 00:19:49.880 align:start position:0% over 160 contributors to our code base and<00:19:46.950> we'd<00:19:47.100> love<00:19:47.220> to<00:19:47.480> have<00:19:48.480> more<00:19:48.750> so<00:19:49.380> thanks<00:19:49.740> for 00:19:49.880 --> 00:19:49.890 align:start position:0% and we'd love to have more so thanks for 00:19:49.890 --> 00:19:56.840 align:start position:0% and we'd love to have more so thanks for your<00:19:50.190> time<00:19:50.669> and<00:19:50.730> hope<00:19:51.330> to<00:19:51.570> see<00:19:51.990> you<00:19:52.440> guys 00:19:56.840 --> 00:19:56.850 align:start position:0% 00:19:56.850 --> 00:20:03.390 align:start position:0% [Applause]