WEBVTT Kind: captions Language: en 00:00:00.030 --> 00:00:02.960 align:start position:0% okay<00:00:00.659> hello<00:00:00.930> guys<00:00:01.380> well<00:00:01.829> first<00:00:02.340> of<00:00:02.460> all<00:00:02.580> thank 00:00:02.960 --> 00:00:02.970 align:start position:0% okay hello guys well first of all thank 00:00:02.970 --> 00:00:05.539 align:start position:0% okay hello guys well first of all thank you<00:00:03.030> for<00:00:03.270> being<00:00:03.600> here<00:00:03.840> today<00:00:03.990> and<00:00:04.259> also<00:00:05.040> thanks 00:00:05.539 --> 00:00:05.549 align:start position:0% you for being here today and also thanks 00:00:05.549 --> 00:00:07.610 align:start position:0% you for being here today and also thanks for<00:00:05.910> the<00:00:06.000> to<00:00:06.390> the<00:00:06.509> organizers<00:00:07.020> for<00:00:07.200> taking 00:00:07.610 --> 00:00:07.620 align:start position:0% for the to the organizers for taking 00:00:07.620 --> 00:00:11.360 align:start position:0% for the to the organizers for taking care<00:00:07.740> of<00:00:07.799> such<00:00:08.250> an<00:00:08.370> amazing<00:00:08.730> event<00:00:09.469> so<00:00:10.469> today 00:00:11.360 --> 00:00:11.370 align:start position:0% care of such an amazing event so today 00:00:11.370 --> 00:00:12.560 align:start position:0% care of such an amazing event so today we're<00:00:11.519> going<00:00:11.639> to<00:00:11.759> talk<00:00:11.880> about<00:00:11.910> a<00:00:12.360> great 00:00:12.560 --> 00:00:12.570 align:start position:0% we're going to talk about a great 00:00:12.570 --> 00:00:16.220 align:start position:0% we're going to talk about a great ability<00:00:12.809> and<00:00:13.200> evm<00:00:13.799> packages<00:00:14.219> and<00:00:14.750> it<00:00:15.750> is<00:00:15.960> to 00:00:16.220 --> 00:00:16.230 align:start position:0% ability and evm packages and it is to 00:00:16.230 --> 00:00:18.470 align:start position:0% ability and evm packages and it is to learn<00:00:16.859> some<00:00:17.580> some<00:00:17.970> things<00:00:18.060> about<00:00:18.240> these 00:00:18.470 --> 00:00:18.480 align:start position:0% learn some some things about these 00:00:18.480 --> 00:00:21.500 align:start position:0% learn some some things about these concepts<00:00:18.930> and<00:00:19.140> of<00:00:19.830> course<00:00:20.100> to<00:00:20.789> see<00:00:20.939> how<00:00:21.300> we<00:00:21.359> can 00:00:21.500 --> 00:00:21.510 align:start position:0% concepts and of course to see how we can 00:00:21.510 --> 00:00:23.450 align:start position:0% concepts and of course to see how we can leverage<00:00:21.720> these<00:00:22.050> concepts<00:00:22.470> using<00:00:22.740> somebody 00:00:23.450 --> 00:00:23.460 align:start position:0% leverage these concepts using somebody 00:00:23.460 --> 00:00:26.660 align:start position:0% leverage these concepts using somebody know<00:00:23.580> us<00:00:23.900> but<00:00:24.900> before<00:00:25.740> we<00:00:25.859> begin<00:00:26.010> I<00:00:26.369> would<00:00:26.550> like 00:00:26.660 --> 00:00:26.670 align:start position:0% know us but before we begin I would like 00:00:26.670 --> 00:00:28.790 align:start position:0% know us but before we begin I would like to<00:00:26.970> talk<00:00:27.119> a<00:00:27.359> little<00:00:27.539> bit<00:00:27.720> about<00:00:27.750> us<00:00:28.199> we<00:00:28.769> are 00:00:28.790 --> 00:00:28.800 align:start position:0% to talk a little bit about us we are 00:00:28.800 --> 00:00:31.250 align:start position:0% to talk a little bit about us we are sapling<00:00:29.250> and<00:00:29.460> at<00:00:30.179> sapling<00:00:30.539> we<00:00:30.660> will<00:00:30.810> key 00:00:31.250 --> 00:00:31.260 align:start position:0% sapling and at sapling we will key 00:00:31.260 --> 00:00:34.010 align:start position:0% sapling and at sapling we will key technology<00:00:32.219> and<00:00:32.340> infrastructure<00:00:32.850> to<00:00:33.239> build 00:00:34.010 --> 00:00:34.020 align:start position:0% technology and infrastructure to build 00:00:34.020 --> 00:00:36.799 align:start position:0% technology and infrastructure to build develop<00:00:34.590> and<00:00:34.800> manage<00:00:35.450> smart<00:00:36.450> contract 00:00:36.799 --> 00:00:36.809 align:start position:0% develop and manage smart contract 00:00:36.809 --> 00:00:40.400 align:start position:0% develop and manage smart contract systems<00:00:37.820> my<00:00:38.820> name<00:00:39.000> is<00:00:39.120> Fabrice<00:00:39.540> paniolo<00:00:39.870> I'm<00:00:40.260> a 00:00:40.400 --> 00:00:40.410 align:start position:0% systems my name is Fabrice paniolo I'm a 00:00:40.410 --> 00:00:42.110 align:start position:0% systems my name is Fabrice paniolo I'm a core<00:00:40.620> developer<00:00:40.710> and<00:00:41.340> security<00:00:41.760> researcher 00:00:42.110 --> 00:00:42.120 align:start position:0% core developer and security researcher 00:00:42.120 --> 00:00:44.750 align:start position:0% core developer and security researcher at<00:00:42.210> sublime<00:00:42.600> and<00:00:43.129> currently<00:00:44.129> I'm<00:00:44.309> leading<00:00:44.610> the 00:00:44.750 --> 00:00:44.760 align:start position:0% at sublime and currently I'm leading the 00:00:44.760 --> 00:00:48.110 align:start position:0% at sublime and currently I'm leading the efforts<00:00:45.059> of<00:00:45.239> subway<00:00:45.960> novice<00:00:46.789> maybe<00:00:47.789> some<00:00:47.969> of 00:00:48.110 --> 00:00:48.120 align:start position:0% efforts of subway novice maybe some of 00:00:48.120 --> 00:00:50.360 align:start position:0% efforts of subway novice maybe some of you<00:00:48.329> may<00:00:48.629> know<00:00:48.750> us<00:00:48.870> because<00:00:49.079> of<00:00:49.379> open<00:00:49.800> sibling 00:00:50.360 --> 00:00:50.370 align:start position:0% you may know us because of open sibling 00:00:50.370 --> 00:00:53.529 align:start position:0% you may know us because of open sibling open<00:00:51.000> subline<00:00:51.329> it's<00:00:51.539> a<00:00:51.600> community<00:00:52.350> driven 00:00:53.529 --> 00:00:53.539 align:start position:0% open subline it's a community driven 00:00:53.539 --> 00:00:56.000 align:start position:0% open subline it's a community driven open-source<00:00:54.539> framework<00:00:54.780> of<00:00:55.289> useful<00:00:55.800> modules 00:00:56.000 --> 00:00:56.010 align:start position:0% open-source framework of useful modules 00:00:56.010 --> 00:00:58.400 align:start position:0% open-source framework of useful modules of<00:00:56.340> my<00:00:56.670> contracts<00:00:57.120> that<00:00:57.329> you<00:00:57.390> can<00:00:57.690> install<00:00:58.170> and 00:00:58.400 --> 00:00:58.410 align:start position:0% of my contracts that you can install and 00:00:58.410 --> 00:01:01.790 align:start position:0% of my contracts that you can install and so<00:00:58.859> using<00:00:59.190> directly<00:00:59.640> in<00:00:59.789> your<00:00:59.820> own<00:01:00.180> projects 00:01:01.790 --> 00:01:01.800 align:start position:0% so using directly in your own projects 00:01:01.800 --> 00:01:06.020 align:start position:0% so using directly in your own projects you<00:01:02.250> also<00:01:02.430> do<00:01:02.730> security<00:01:03.270> audits<00:01:03.710> a<00:01:04.880> few<00:01:05.880> weeks 00:01:06.020 --> 00:01:06.030 align:start position:0% you also do security audits a few weeks 00:01:06.030 --> 00:01:07.730 align:start position:0% you also do security audits a few weeks ago<00:01:06.150> we<00:01:06.390> finished<00:01:06.720> the<00:01:07.229> other<00:01:07.350> four<00:01:07.650> the 00:01:07.730 --> 00:01:07.740 align:start position:0% ago we finished the other four the 00:01:07.740 --> 00:01:10.130 align:start position:0% ago we finished the other four the solidity<00:01:08.130> compiler<00:01:08.549> we<00:01:09.270> receive<00:01:09.570> a<00:01:09.900> grant 00:01:10.130 --> 00:01:10.140 align:start position:0% solidity compiler we receive a grant 00:01:10.140 --> 00:01:11.660 align:start position:0% solidity compiler we receive a grant from<00:01:10.260> the<00:01:10.350> Athenian<00:01:11.010> foundation<00:01:11.430> it<00:01:11.549> was 00:01:11.660 --> 00:01:11.670 align:start position:0% from the Athenian foundation it was 00:01:11.670 --> 00:01:14.719 align:start position:0% from the Athenian foundation it was really<00:01:12.000> great<00:01:12.119> and<00:01:13.280> well<00:01:14.280> as<00:01:14.400> I<00:01:14.520> said<00:01:14.580> before 00:01:14.719 --> 00:01:14.729 align:start position:0% really great and well as I said before 00:01:14.729 --> 00:01:16.429 align:start position:0% really great and well as I said before we're<00:01:15.180> here<00:01:15.360> today<00:01:15.479> to<00:01:15.630> talk<00:01:16.020> a<00:01:16.080> little<00:01:16.229> bit 00:01:16.429 --> 00:01:16.439 align:start position:0% we're here today to talk a little bit 00:01:16.439 --> 00:01:18.770 align:start position:0% we're here today to talk a little bit about<00:01:16.470> subbing<00:01:16.979> OS<00:01:17.299> sublimates<00:01:18.299> is<00:01:18.420> an<00:01:18.540> open 00:01:18.770 --> 00:01:18.780 align:start position:0% about subbing OS sublimates is an open 00:01:18.780 --> 00:01:20.990 align:start position:0% about subbing OS sublimates is an open source<00:01:18.960> platform<00:01:19.170> to<00:01:19.740> help<00:01:20.310> you<00:01:20.430> building 00:01:20.990 --> 00:01:21.000 align:start position:0% source platform to help you building 00:01:21.000 --> 00:01:23.030 align:start position:0% source platform to help you building develop<00:01:21.450> and<00:01:21.600> manage<00:01:21.780> smart<00:01:22.770> contract 00:01:23.030 --> 00:01:23.040 align:start position:0% develop and manage smart contract 00:01:23.040 --> 00:01:27.080 align:start position:0% develop and manage smart contract systems<00:01:23.369> so<00:01:24.650> let's<00:01:25.650> begin<00:01:25.830> with<00:01:25.979> the<00:01:26.430> first 00:01:27.080 --> 00:01:27.090 align:start position:0% systems so let's begin with the first 00:01:27.090 --> 00:01:31.039 align:start position:0% systems so let's begin with the first topic<00:01:27.240> a<00:01:27.540> great<00:01:28.290> ability<00:01:28.939> so<00:01:29.939> of<00:01:30.750> course<00:01:30.960> that 00:01:31.039 --> 00:01:31.049 align:start position:0% topic a great ability so of course that 00:01:31.049 --> 00:01:33.170 align:start position:0% topic a great ability so of course that mere<00:01:31.950> ability<00:01:32.250> is<00:01:32.310> one<00:01:32.520> of<00:01:32.610> the<00:01:32.729> main<00:01:33.000> features 00:01:33.170 --> 00:01:33.180 align:start position:0% mere ability is one of the main features 00:01:33.180 --> 00:01:37.330 align:start position:0% mere ability is one of the main features of<00:01:33.360> aetherium<00:01:34.200> however<00:01:35.540> several<00:01:36.540> qualities 00:01:37.330 --> 00:01:37.340 align:start position:0% of aetherium however several qualities 00:01:37.340 --> 00:01:40.700 align:start position:0% of aetherium however several qualities really<00:01:38.340> much<00:01:38.579> depends<00:01:39.090> on<00:01:39.210> on<00:01:39.479> a<00:01:39.960> development 00:01:40.700 --> 00:01:40.710 align:start position:0% really much depends on on a development 00:01:40.710 --> 00:01:42.050 align:start position:0% really much depends on on a development that<00:01:40.770> needs<00:01:41.070> to<00:01:41.189> be<00:01:41.220> iterative<00:01:41.700> and 00:01:42.050 --> 00:01:42.060 align:start position:0% that needs to be iterative and 00:01:42.060 --> 00:01:44.450 align:start position:0% that needs to be iterative and incremental<00:01:42.180> and<00:01:42.930> this<00:01:43.290> means<00:01:43.470> that<00:01:43.770> we<00:01:44.369> need 00:01:44.450 --> 00:01:44.460 align:start position:0% incremental and this means that we need 00:01:44.460 --> 00:01:46.010 align:start position:0% incremental and this means that we need to<00:01:44.579> have<00:01:44.790> the<00:01:44.909> chance<00:01:45.119> to<00:01:45.180> update<00:01:45.450> or<00:01:45.810> patch 00:01:46.010 --> 00:01:46.020 align:start position:0% to have the chance to update or patch 00:01:46.020 --> 00:01:48.920 align:start position:0% to have the chance to update or patch our<00:01:46.259> code<00:01:46.500> if<00:01:46.890> you<00:01:47.040> need<00:01:47.189> to<00:01:47.340> and<00:01:47.899> we're<00:01:48.899> not 00:01:48.920 --> 00:01:48.930 align:start position:0% our code if you need to and we're not 00:01:48.930 --> 00:01:51.789 align:start position:0% our code if you need to and we're not just<00:01:49.140> talking<00:01:50.070> about<00:01:50.130> bags<00:01:50.520> we<00:01:51.119> may<00:01:51.270> need<00:01:51.420> to 00:01:51.789 --> 00:01:51.799 align:start position:0% just talking about bags we may need to 00:01:51.799 --> 00:01:54.700 align:start position:0% just talking about bags we may need to optimize<00:01:52.799> our<00:01:53.189> solutions<00:01:53.790> we<00:01:54.090> may<00:01:54.210> need<00:01:54.420> to 00:01:54.700 --> 00:01:54.710 align:start position:0% optimize our solutions we may need to 00:01:54.710 --> 00:01:56.870 align:start position:0% optimize our solutions we may need to provide<00:01:55.710> new<00:01:55.890> functionality<00:01:56.490> because<00:01:56.610> the 00:01:56.870 --> 00:01:56.880 align:start position:0% provide new functionality because the 00:01:56.880 --> 00:01:59.260 align:start position:0% provide new functionality because the community's<00:01:57.329> requiring<00:01:57.780> it<00:01:57.990> or<00:01:58.140> whatever<00:01:58.619> and 00:01:59.260 --> 00:01:59.270 align:start position:0% community's requiring it or whatever and 00:01:59.270 --> 00:02:02.420 align:start position:0% community's requiring it or whatever and the<00:02:00.270> thing<00:02:00.450> is<00:02:00.570> that<00:02:00.719> we've<00:02:01.530> seen<00:02:01.770> many<00:02:02.159> other 00:02:02.420 --> 00:02:02.430 align:start position:0% the thing is that we've seen many other 00:02:02.430 --> 00:02:05.800 align:start position:0% the thing is that we've seen many other projects<00:02:03.030> building<00:02:03.840> their<00:02:04.079> own 00:02:05.800 --> 00:02:05.810 align:start position:0% projects building their own 00:02:05.810 --> 00:02:08.919 align:start position:0% projects building their own implementations<00:02:06.810> of<00:02:07.020> availability<00:02:07.979> and 00:02:08.919 --> 00:02:08.929 align:start position:0% implementations of availability and 00:02:08.929 --> 00:02:11.390 align:start position:0% implementations of availability and suppling<00:02:09.929> alas<00:02:10.170> is<00:02:10.410> providing<00:02:11.099> a<00:02:11.220> standard 00:02:11.390 --> 00:02:11.400 align:start position:0% suppling alas is providing a standard 00:02:11.400 --> 00:02:14.000 align:start position:0% suppling alas is providing a standard and<00:02:11.819> really<00:02:12.500> flexible<00:02:13.500> way<00:02:13.739> to 00:02:14.000 --> 00:02:14.010 align:start position:0% and really flexible way to 00:02:14.010 --> 00:02:16.429 align:start position:0% and really flexible way to to<00:02:14.220> do<00:02:14.310> this<00:02:14.459> so<00:02:14.730> I<00:02:15.000> would<00:02:15.750> like<00:02:15.870> to<00:02:16.019> introduce 00:02:16.429 --> 00:02:16.439 align:start position:0% to do this so I would like to introduce 00:02:16.439 --> 00:02:19.280 align:start position:0% to do this so I would like to introduce an<00:02:16.709> example<00:02:17.099> of<00:02:17.189> how<00:02:17.519> we<00:02:17.580> can<00:02:17.819> easily<00:02:18.269> have<00:02:18.780> a 00:02:19.280 --> 00:02:19.290 align:start position:0% an example of how we can easily have a 00:02:19.290 --> 00:02:21.559 align:start position:0% an example of how we can easily have a well<00:02:19.560> with<00:02:19.769> my<00:02:19.950> contracts<00:02:20.430> in<00:02:20.970> our<00:02:21.150> projects 00:02:21.559 --> 00:02:21.569 align:start position:0% well with my contracts in our projects 00:02:21.569 --> 00:02:25.280 align:start position:0% well with my contracts in our projects using<00:02:21.870> sub<00:02:22.170> Nova's<00:02:23.000> so<00:02:24.000> the<00:02:24.720> first<00:02:24.930> thing 00:02:25.280 --> 00:02:25.290 align:start position:0% using sub Nova's so the first thing 00:02:25.290 --> 00:02:28.100 align:start position:0% using sub Nova's so the first thing we'll<00:02:25.500> need<00:02:25.590> to<00:02:25.739> do<00:02:25.920> is<00:02:25.950> to<00:02:26.159> install<00:02:26.689> sub<00:02:27.689> in<00:02:27.810> OS 00:02:28.100 --> 00:02:28.110 align:start position:0% we'll need to do is to install sub in OS 00:02:28.110 --> 00:02:30.890 align:start position:0% we'll need to do is to install sub in OS in<00:02:28.409> this<00:02:28.530> case<00:02:28.709> we're<00:02:28.950> using<00:02:28.980> NPM<00:02:29.610> and<00:02:29.900> sibling 00:02:30.890 --> 00:02:30.900 align:start position:0% in this case we're using NPM and sibling 00:02:30.900 --> 00:02:33.380 align:start position:0% in this case we're using NPM and sibling OS<00:02:31.140> comes<00:02:31.409> with<00:02:31.680> a<00:02:31.709> common<00:02:32.459> line<00:02:32.640> tool<00:02:32.849> and<00:02:33.060> in 00:02:33.380 --> 00:02:33.390 align:start position:0% OS comes with a common line tool and in 00:02:33.390 --> 00:02:35.059 align:start position:0% OS comes with a common line tool and in this<00:02:33.450> case<00:02:33.690> for<00:02:33.900> example<00:02:33.959> we<00:02:34.349> have<00:02:34.530> a<00:02:34.680> need 00:02:35.059 --> 00:02:35.069 align:start position:0% this case for example we have a need 00:02:35.069 --> 00:02:36.920 align:start position:0% this case for example we have a need command<00:02:35.430> that<00:02:35.640> we<00:02:35.790> can<00:02:35.940> use<00:02:36.090> to<00:02:36.120> start<00:02:36.569> a<00:02:36.750> new 00:02:36.920 --> 00:02:36.930 align:start position:0% command that we can use to start a new 00:02:36.930 --> 00:02:39.440 align:start position:0% command that we can use to start a new project<00:02:37.200> just<00:02:37.700> personally<00:02:38.700> the<00:02:38.970> name<00:02:39.150> of<00:02:39.329> our 00:02:39.440 --> 00:02:39.450 align:start position:0% project just personally the name of our 00:02:39.450 --> 00:02:43.369 align:start position:0% project just personally the name of our project<00:02:39.840> and<00:02:41.209> let's<00:02:42.209> say<00:02:42.329> that<00:02:42.480> we<00:02:42.599> start 00:02:43.369 --> 00:02:43.379 align:start position:0% project and let's say that we start 00:02:43.379 --> 00:02:46.039 align:start position:0% project and let's say that we start writing<00:02:44.040> our<00:02:44.159> first<00:02:44.700> smart<00:02:45.269> contract<00:02:45.750> in<00:02:45.930> this 00:02:46.039 --> 00:02:46.049 align:start position:0% writing our first smart contract in this 00:02:46.049 --> 00:02:48.530 align:start position:0% writing our first smart contract in this case<00:02:46.319> a<00:02:46.590> wallet<00:02:47.220> as<00:02:47.670> you<00:02:47.790> can<00:02:47.909> see<00:02:48.090> has<00:02:48.359> an 00:02:48.530 --> 00:02:48.540 align:start position:0% case a wallet as you can see has an 00:02:48.540 --> 00:02:51.349 align:start position:0% case a wallet as you can see has an owner<00:02:48.720> I<00:02:49.049> guess<00:02:49.890> an<00:02:50.129> initialization<00:02:50.879> function 00:02:51.349 --> 00:02:51.359 align:start position:0% owner I guess an initialization function 00:02:51.359 --> 00:02:53.210 align:start position:0% owner I guess an initialization function where<00:02:51.959> we<00:02:52.049> received<00:02:52.440> the<00:02:52.560> owner<00:02:52.709> you<00:02:53.040> know<00:02:53.159> you 00:02:53.210 --> 00:02:53.220 align:start position:0% where we received the owner you know you 00:02:53.220 --> 00:02:54.830 align:start position:0% where we received the owner you know you set<00:02:53.489> the<00:02:53.549> owner<00:02:53.670> of<00:02:53.940> the<00:02:54.030> contract 00:02:54.830 --> 00:02:54.840 align:start position:0% set the owner of the contract 00:02:54.840 --> 00:02:56.539 align:start position:0% set the owner of the contract because<00:02:55.290> we<00:02:55.620> draw<00:02:55.829> a<00:02:55.859> function<00:02:56.010> in<00:02:56.370> order<00:02:56.459> to 00:02:56.539 --> 00:02:56.549 align:start position:0% because we draw a function in order to 00:02:56.549 --> 00:02:58.729 align:start position:0% because we draw a function in order to withdraw<00:02:57.450> some<00:02:57.599> funds<00:02:57.989> from<00:02:58.200> the<00:02:58.349> contract 00:02:58.729 --> 00:02:58.739 align:start position:0% withdraw some funds from the contract 00:02:58.739 --> 00:03:03.259 align:start position:0% withdraw some funds from the contract and<00:02:58.889> so<00:02:59.459> on<00:03:00.079> so<00:03:01.549> let's<00:03:02.549> see<00:03:02.670> how<00:03:02.790> we<00:03:02.879> can<00:03:02.970> employ 00:03:03.259 --> 00:03:03.269 align:start position:0% and so on so let's see how we can employ 00:03:03.269 --> 00:03:05.599 align:start position:0% and so on so let's see how we can employ an<00:03:03.599> agreeable<00:03:03.959> instance<00:03:04.560> of<00:03:04.799> this<00:03:05.010> smart 00:03:05.599 --> 00:03:05.609 align:start position:0% an agreeable instance of this smart 00:03:05.609 --> 00:03:09.530 align:start position:0% an agreeable instance of this smart contract<00:03:06.090> using<00:03:06.359> sub<00:03:06.659> us<00:03:07.400> so<00:03:08.400> the<00:03:09.180> common<00:03:09.420> line 00:03:09.530 --> 00:03:09.540 align:start position:0% contract using sub us so the common line 00:03:09.540 --> 00:03:12.349 align:start position:0% contract using sub us so the common line tool<00:03:09.720> has<00:03:09.989> some<00:03:10.799> comments<00:03:11.370> that<00:03:11.670> are<00:03:11.790> pretty 00:03:12.349 --> 00:03:12.359 align:start position:0% tool has some comments that are pretty 00:03:12.359 --> 00:03:14.780 align:start position:0% tool has some comments that are pretty much<00:03:12.810> similar<00:03:13.079> to<00:03:13.379> the<00:03:13.500> ones<00:03:13.739> we<00:03:13.920> use<00:03:13.950> in<00:03:14.370> get 00:03:14.780 --> 00:03:14.790 align:start position:0% much similar to the ones we use in get 00:03:14.790 --> 00:03:16.789 align:start position:0% much similar to the ones we use in get so<00:03:15.060> I<00:03:15.090> think<00:03:15.420> it<00:03:15.510> will<00:03:15.659> sound<00:03:15.900> familiar<00:03:16.049> to<00:03:16.470> you 00:03:16.789 --> 00:03:16.799 align:start position:0% so I think it will sound familiar to you 00:03:16.799 --> 00:03:19.099 align:start position:0% so I think it will sound familiar to you in<00:03:16.980> this<00:03:17.099> case<00:03:17.310> we're<00:03:18.239> running<00:03:18.540> the<00:03:18.720> first 00:03:19.099 --> 00:03:19.109 align:start position:0% in this case we're running the first 00:03:19.109 --> 00:03:21.470 align:start position:0% in this case we're running the first command<00:03:19.440> the<00:03:19.799> add<00:03:19.919> command<00:03:20.250> it's<00:03:20.760> the<00:03:21.120> way<00:03:21.269> we 00:03:21.470 --> 00:03:21.480 align:start position:0% command the add command it's the way we 00:03:21.480 --> 00:03:23.629 align:start position:0% command the add command it's the way we tell<00:03:21.930> separately<00:03:22.349> the<00:03:22.709> way<00:03:22.829> we<00:03:22.949> tell<00:03:23.099> supplies 00:03:23.629 --> 00:03:23.639 align:start position:0% tell separately the way we tell supplies 00:03:23.639 --> 00:03:26.240 align:start position:0% tell separately the way we tell supplies in<00:03:23.849> order<00:03:23.910> to<00:03:24.150> add<00:03:24.329> a<00:03:24.480> new<00:03:24.989> smart<00:03:25.709> contract<00:03:26.129> in 00:03:26.240 --> 00:03:26.250 align:start position:0% in order to add a new smart contract in 00:03:26.250 --> 00:03:27.559 align:start position:0% in order to add a new smart contract in our<00:03:26.340> brushing<00:03:26.699> this<00:03:26.849> case<00:03:27.090> were<00:03:27.269> changed 00:03:27.559 --> 00:03:27.569 align:start position:0% our brushing this case were changed 00:03:27.569 --> 00:03:29.420 align:start position:0% our brushing this case were changed seven<00:03:27.810> ways<00:03:27.989> that<00:03:28.169> we<00:03:28.260> want<00:03:28.470> to<00:03:28.500> add<00:03:28.709> the 00:03:29.420 --> 00:03:29.430 align:start position:0% seven ways that we want to add the 00:03:29.430 --> 00:03:31.869 align:start position:0% seven ways that we want to add the manual<00:03:29.760> contract<00:03:30.299> that<00:03:30.480> we<00:03:30.629> wrote<00:03:31.019> before<00:03:31.199> and 00:03:31.869 --> 00:03:31.879 align:start position:0% manual contract that we wrote before and 00:03:31.879 --> 00:03:34.909 align:start position:0% manual contract that we wrote before and the<00:03:32.879> second<00:03:33.209> step<00:03:33.359> is<00:03:33.629> the<00:03:33.930> push<00:03:34.169> command<00:03:34.349> this 00:03:34.909 --> 00:03:34.919 align:start position:0% the second step is the push command this 00:03:34.919 --> 00:03:37.640 align:start position:0% the second step is the push command this is<00:03:35.069> how<00:03:35.220> we<00:03:35.400> upload<00:03:35.959> the<00:03:36.959> back<00:03:37.139> of<00:03:37.319> our 00:03:37.640 --> 00:03:37.650 align:start position:0% is how we upload the back of our 00:03:37.650 --> 00:03:39.500 align:start position:0% is how we upload the back of our contract<00:03:38.160> to<00:03:38.250> the<00:03:38.370> node<00:03:38.489> to<00:03:38.760> network<00:03:39.150> in<00:03:39.359> this 00:03:39.500 --> 00:03:39.510 align:start position:0% contract to the node to network in this 00:03:39.510 --> 00:03:42.319 align:start position:0% contract to the node to network in this case<00:03:39.690> for<00:03:39.900> example<00:03:39.989> we<00:03:40.260> were<00:03:40.349> pushing<00:03:41.329> the 00:03:42.319 --> 00:03:42.329 align:start position:0% case for example we were pushing the 00:03:42.329 --> 00:03:44.089 align:start position:0% case for example we were pushing the source<00:03:42.540> code<00:03:42.750> of<00:03:42.870> the<00:03:42.959> my<00:03:43.379> wallet<00:03:43.680> contract<00:03:44.010> to 00:03:44.089 --> 00:03:44.099 align:start position:0% source code of the my wallet contract to 00:03:44.099 --> 00:03:46.550 align:start position:0% source code of the my wallet contract to the<00:03:44.190> raphson<00:03:44.609> Network<00:03:44.970> and<00:03:45.260> finally<00:03:46.260> we<00:03:46.379> have 00:03:46.550 --> 00:03:46.560 align:start position:0% the raphson Network and finally we have 00:03:46.560 --> 00:03:48.409 align:start position:0% the raphson Network and finally we have the<00:03:46.680> create<00:03:47.069> command<00:03:47.250> the<00:03:48.030> create<00:03:48.299> command 00:03:48.409 --> 00:03:48.419 align:start position:0% the create command the create command 00:03:48.419 --> 00:03:50.839 align:start position:0% the create command the create command will<00:03:49.049> create<00:03:49.079> an<00:03:49.590> agreeable<00:03:49.889> instance<00:03:50.459> of<00:03:50.639> the 00:03:50.839 --> 00:03:50.849 align:start position:0% will create an agreeable instance of the 00:03:50.849 --> 00:03:53.300 align:start position:0% will create an agreeable instance of the my<00:03:50.970> wallet<00:03:51.269> contract<00:03:51.629> and<00:03:51.919> the<00:03:52.919> others<00:03:53.129> that 00:03:53.300 --> 00:03:53.310 align:start position:0% my wallet contract and the others that 00:03:53.310 --> 00:03:55.400 align:start position:0% my wallet contract and the others that we<00:03:53.430> receive<00:03:53.879> there<00:03:54.060> is<00:03:54.239> the<00:03:54.419> the<00:03:54.720> new<00:03:55.079> instance 00:03:55.400 --> 00:03:55.410 align:start position:0% we receive there is the the new instance 00:03:55.410 --> 00:03:58.189 align:start position:0% we receive there is the the new instance that<00:03:55.560> we<00:03:55.620> have<00:03:55.799> just<00:03:55.980> created<00:03:56.069> and<00:03:56.989> maybe<00:03:57.989> some 00:03:58.189 --> 00:03:58.199 align:start position:0% that we have just created and maybe some 00:03:58.199 --> 00:03:59.659 align:start position:0% that we have just created and maybe some of<00:03:58.290> you<00:03:58.440> may<00:03:58.590> be<00:03:58.620> wondering<00:03:59.069> why<00:03:59.250> do<00:03:59.310> we<00:03:59.519> need 00:03:59.659 --> 00:03:59.669 align:start position:0% of you may be wondering why do we need 00:03:59.669 --> 00:04:01.759 align:start position:0% of you may be wondering why do we need to<00:03:59.790> run<00:04:00.239> these<00:04:00.449> three<00:04:00.989> steps<00:04:01.199> in<00:04:01.409> order<00:04:01.650> to 00:04:01.759 --> 00:04:01.769 align:start position:0% to run these three steps in order to 00:04:01.769 --> 00:04:03.979 align:start position:0% to run these three steps in order to create<00:04:02.400> an<00:04:02.549> available<00:04:02.909> instance<00:04:03.269> well<00:04:03.900> the 00:04:03.979 --> 00:04:03.989 align:start position:0% create an available instance well the 00:04:03.989 --> 00:04:06.020 align:start position:0% create an available instance well the thing<00:04:04.169> is<00:04:04.199> that<00:04:04.560> this<00:04:04.949> is<00:04:05.010> no<00:04:05.639> regular 00:04:06.020 --> 00:04:06.030 align:start position:0% thing is that this is no regular 00:04:06.030 --> 00:04:07.789 align:start position:0% thing is that this is no regular instance<00:04:06.389> obviously<00:04:06.840> this<00:04:07.139> is<00:04:07.290> an<00:04:07.409> available 00:04:07.789 --> 00:04:07.799 align:start position:0% instance obviously this is an available 00:04:07.799 --> 00:04:09.949 align:start position:0% instance obviously this is an available instance<00:04:08.159> and<00:04:08.310> the<00:04:08.699> thing<00:04:08.879> is<00:04:09.030> that<00:04:09.209> we<00:04:09.840> can 00:04:09.949 --> 00:04:09.959 align:start position:0% instance and the thing is that we can 00:04:09.959 --> 00:04:12.259 align:start position:0% instance and the thing is that we can run<00:04:10.229> the<00:04:10.440> create<00:04:10.739> command<00:04:10.889> as<00:04:11.340> many<00:04:11.639> times<00:04:11.879> as 00:04:12.259 --> 00:04:12.269 align:start position:0% run the create command as many times as 00:04:12.269 --> 00:04:14.899 align:start position:0% run the create command as many times as we<00:04:12.569> want<00:04:12.599> I<00:04:12.989> will<00:04:13.260> be<00:04:13.739> always<00:04:14.069> reusing<00:04:14.790> the 00:04:14.899 --> 00:04:14.909 align:start position:0% we want I will be always reusing the 00:04:14.909 --> 00:04:17.870 align:start position:0% we want I will be always reusing the same<00:04:14.940> logic<00:04:15.540> that<00:04:15.720> we<00:04:15.959> uploaded<00:04:16.289> just<00:04:16.590> once<00:04:17.130> so 00:04:17.870 --> 00:04:17.880 align:start position:0% same logic that we uploaded just once so 00:04:17.880 --> 00:04:21.500 align:start position:0% same logic that we uploaded just once so it's<00:04:18.419> RIT<00:04:18.690> and<00:04:19.370> let's<00:04:20.370> say<00:04:20.489> that<00:04:20.519> after<00:04:20.940> we 00:04:21.500 --> 00:04:21.510 align:start position:0% it's RIT and let's say that after we 00:04:21.510 --> 00:04:24.469 align:start position:0% it's RIT and let's say that after we created<00:04:21.900> the<00:04:22.469> first<00:04:22.620> instance<00:04:23.240> our<00:04:24.240> build 00:04:24.469 --> 00:04:24.479 align:start position:0% created the first instance our build 00:04:24.479 --> 00:04:27.260 align:start position:0% created the first instance our build instance<00:04:24.870> of<00:04:25.020> my<00:04:25.289> wallet<00:04:25.560> contract<00:04:25.979> we<00:04:26.940> found 00:04:27.260 --> 00:04:27.270 align:start position:0% instance of my wallet contract we found 00:04:27.270 --> 00:04:29.740 align:start position:0% instance of my wallet contract we found back<00:04:27.470> as<00:04:28.470> you<00:04:28.650> can<00:04:28.770> see<00:04:28.949> they<00:04:29.220> need<00:04:29.400> wallet 00:04:29.740 --> 00:04:29.750 align:start position:0% back as you can see they need wallet 00:04:29.750 --> 00:04:32.480 align:start position:0% back as you can see they need wallet function<00:04:30.750> can<00:04:31.500> be<00:04:31.530> called<00:04:31.710> by<00:04:31.830> anyone<00:04:32.310> and 00:04:32.480 --> 00:04:32.490 align:start position:0% function can be called by anyone and 00:04:32.490 --> 00:04:34.790 align:start position:0% function can be called by anyone and this<00:04:33.030> means<00:04:33.270> that<00:04:33.449> for<00:04:34.110> example<00:04:34.319> an<00:04:34.530> attacker 00:04:34.790 --> 00:04:34.800 align:start position:0% this means that for example an attacker 00:04:34.800 --> 00:04:36.499 align:start position:0% this means that for example an attacker can<00:04:35.099> call<00:04:35.430> they<00:04:35.550> need<00:04:35.580> wallet<00:04:35.970> function<00:04:36.360> to 00:04:36.499 --> 00:04:36.509 align:start position:0% can call they need wallet function to 00:04:36.509 --> 00:04:38.270 align:start position:0% can call they need wallet function to withdraw<00:04:36.840> some<00:04:36.870> funds<00:04:37.199> from<00:04:37.349> it 00:04:38.270 --> 00:04:38.280 align:start position:0% withdraw some funds from it 00:04:38.280 --> 00:04:40.189 align:start position:0% withdraw some funds from it any<00:04:38.490> resemblance<00:04:39.150> with<00:04:39.479> reality<00:04:39.900> here<00:04:40.110> is 00:04:40.189 --> 00:04:40.199 align:start position:0% any resemblance with reality here is 00:04:40.199 --> 00:04:43.580 align:start position:0% any resemblance with reality here is perkiness<00:04:41.009> and<00:04:41.960> let's<00:04:42.960> say<00:04:43.050> that<00:04:43.199> we<00:04:43.289> want<00:04:43.500> to 00:04:43.580 --> 00:04:43.590 align:start position:0% perkiness and let's say that we want to 00:04:43.590 --> 00:04:46.159 align:start position:0% perkiness and let's say that we want to fix<00:04:43.770> this<00:04:43.889> bag<00:04:44.099> so<00:04:44.460> let's<00:04:44.819> see<00:04:45.599> how<00:04:45.900> we<00:04:45.960> can<00:04:46.080> do 00:04:46.159 --> 00:04:46.169 align:start position:0% fix this bag so let's see how we can do 00:04:46.169 --> 00:04:47.719 align:start position:0% fix this bag so let's see how we can do this<00:04:46.289> with<00:04:46.470> subenoy's<00:04:47.159> I<00:04:47.280> promise<00:04:47.550> it's 00:04:47.719 --> 00:04:47.729 align:start position:0% this with subenoy's I promise it's 00:04:47.729 --> 00:04:50.749 align:start position:0% this with subenoy's I promise it's really<00:04:48.180> simple<00:04:48.360> so<00:04:49.289> the<00:04:50.009> first<00:04:50.220> thing<00:04:50.580> we'll 00:04:50.749 --> 00:04:50.759 align:start position:0% really simple so the first thing we'll 00:04:50.759 --> 00:04:52.790 align:start position:0% really simple so the first thing we'll need<00:04:50.789> to<00:04:51.000> do<00:04:51.150> is<00:04:51.180> just<00:04:51.539> to<00:04:51.720> edit<00:04:52.259> the<00:04:52.409> the 00:04:52.790 --> 00:04:52.800 align:start position:0% need to do is just to edit the the 00:04:52.800 --> 00:04:54.710 align:start position:0% need to do is just to edit the the source<00:04:53.129> code<00:04:53.310> of<00:04:53.490> our<00:04:53.669> contracts<00:04:54.030> for<00:04:54.449> example 00:04:54.710 --> 00:04:54.720 align:start position:0% source code of our contracts for example 00:04:54.720 --> 00:04:56.510 align:start position:0% source code of our contracts for example in<00:04:54.810> this<00:04:54.930> case<00:04:55.080> we're<00:04:55.229> adding<00:04:55.560> an<00:04:55.919> only<00:04:56.220> own<00:04:56.310> or 00:04:56.510 --> 00:04:56.520 align:start position:0% in this case we're adding an only own or 00:04:56.520 --> 00:04:59.839 align:start position:0% in this case we're adding an only own or modifier<00:04:56.909> in<00:04:57.150> order<00:04:57.360> to<00:04:57.479> restrict<00:04:58.400> the<00:04:59.400> person 00:04:59.839 --> 00:04:59.849 align:start position:0% modifier in order to restrict the person 00:04:59.849 --> 00:05:03.249 align:start position:0% modifier in order to restrict the person they<00:05:00.240> can<00:05:00.389> call<00:05:00.569> this<00:05:00.750> this<00:05:01.349> function<00:05:02.159> and 00:05:03.249 --> 00:05:03.259 align:start position:0% they can call this this function and 00:05:03.259 --> 00:05:06.290 align:start position:0% they can call this this function and once<00:05:04.259> again<00:05:04.530> as<00:05:04.680> we<00:05:04.710> did<00:05:04.889> before<00:05:05.130> we<00:05:05.940> just<00:05:06.120> need 00:05:06.290 --> 00:05:06.300 align:start position:0% once again as we did before we just need 00:05:06.300 --> 00:05:08.420 align:start position:0% once again as we did before we just need to<00:05:06.509> run<00:05:06.720> the<00:05:06.870> add<00:05:06.990> command<00:05:07.319> to<00:05:07.770> tell<00:05:08.280> us<00:05:08.340> how 00:05:08.420 --> 00:05:08.430 align:start position:0% to run the add command to tell us how 00:05:08.430 --> 00:05:11.570 align:start position:0% to run the add command to tell us how many<00:05:08.520> ways<00:05:08.729> to<00:05:08.849> add<00:05:08.970> the<00:05:09.120> new<00:05:09.419> fixed<00:05:10.319> my<00:05:11.280> wallet 00:05:11.570 --> 00:05:11.580 align:start position:0% many ways to add the new fixed my wallet 00:05:11.580 --> 00:05:14.659 align:start position:0% many ways to add the new fixed my wallet contract<00:05:12.050> we're<00:05:13.050> pushing<00:05:13.409> that<00:05:14.099> fix<00:05:14.340> to<00:05:14.580> the 00:05:14.659 --> 00:05:14.669 align:start position:0% contract we're pushing that fix to the 00:05:14.669 --> 00:05:17.089 align:start position:0% contract we're pushing that fix to the network<00:05:15.030> and<00:05:15.210> finally<00:05:16.020> we're<00:05:16.380> running<00:05:16.680> a<00:05:16.800> new 00:05:17.089 --> 00:05:17.099 align:start position:0% network and finally we're running a new 00:05:17.099 --> 00:05:18.980 align:start position:0% network and finally we're running a new command<00:05:17.370> here<00:05:17.580> the<00:05:17.759> update<00:05:18.120> command<00:05:18.270> is<00:05:18.780> the 00:05:18.980 --> 00:05:18.990 align:start position:0% command here the update command is the 00:05:18.990 --> 00:05:21.490 align:start position:0% command here the update command is the way<00:05:19.139> to<00:05:19.199> tell<00:05:19.469> something<00:05:19.680> less<00:05:20.009> to<00:05:20.759> operate 00:05:21.490 --> 00:05:21.500 align:start position:0% way to tell something less to operate 00:05:21.500 --> 00:05:23.749 align:start position:0% way to tell something less to operate there<00:05:22.500> willow<00:05:22.680> instance<00:05:23.130> that<00:05:23.280> we<00:05:23.400> created 00:05:23.749 --> 00:05:23.759 align:start position:0% there willow instance that we created 00:05:23.759 --> 00:05:25.399 align:start position:0% there willow instance that we created before<00:05:23.849> and<00:05:24.210> it<00:05:24.389> will<00:05:24.479> be<00:05:24.599> a<00:05:24.780> simple<00:05:25.080> as<00:05:25.229> that 00:05:25.399 --> 00:05:25.409 align:start position:0% before and it will be a simple as that 00:05:25.409 --> 00:05:27.980 align:start position:0% before and it will be a simple as that as<00:05:26.219> you<00:05:26.340> can<00:05:26.460> see<00:05:26.639> an<00:05:26.879> attacker<00:05:27.449> cannot<00:05:27.690> call 00:05:27.980 --> 00:05:27.990 align:start position:0% as you can see an attacker cannot call 00:05:27.990 --> 00:05:29.930 align:start position:0% as you can see an attacker cannot call any<00:05:28.169> more<00:05:28.379> than<00:05:28.560> in<00:05:28.680> wallet<00:05:28.979> function<00:05:29.340> and<00:05:29.520> our 00:05:29.930 --> 00:05:29.940 align:start position:0% any more than in wallet function and our 00:05:29.940 --> 00:05:33.260 align:start position:0% any more than in wallet function and our bug<00:05:30.389> has<00:05:30.840> been<00:05:30.960> fixed<00:05:31.190> so<00:05:32.190> it<00:05:32.610> was<00:05:32.729> pretty 00:05:33.260 --> 00:05:33.270 align:start position:0% bug has been fixed so it was pretty 00:05:33.270 --> 00:05:35.450 align:start position:0% bug has been fixed so it was pretty simple<00:05:33.539> we<00:05:34.080> didn't<00:05:34.319> have<00:05:34.500> to<00:05:34.650> modify<00:05:35.039> our 00:05:35.450 --> 00:05:35.460 align:start position:0% simple we didn't have to modify our 00:05:35.460 --> 00:05:37.550 align:start position:0% simple we didn't have to modify our source<00:05:35.880> code<00:05:36.090> in<00:05:36.389> order<00:05:36.599> to<00:05:36.719> make<00:05:37.349> our 00:05:37.550 --> 00:05:37.560 align:start position:0% source code in order to make our 00:05:37.560 --> 00:05:40.129 align:start position:0% source code in order to make our contracts<00:05:38.099> available<00:05:38.250> and<00:05:38.969> as<00:05:39.810> you<00:05:39.990> can<00:05:40.080> see 00:05:40.129 --> 00:05:40.139 align:start position:0% contracts available and as you can see 00:05:40.139 --> 00:05:42.290 align:start position:0% contracts available and as you can see where<00:05:40.500> you<00:05:40.650> were<00:05:41.039> using<00:05:41.340> the<00:05:41.460> same<00:05:41.639> address<00:05:42.000> it 00:05:42.290 --> 00:05:42.300 align:start position:0% where you were using the same address it 00:05:42.300 --> 00:05:44.719 align:start position:0% where you were using the same address it was<00:05:42.479> an<00:05:42.750> upgrade<00:05:43.529> per<00:05:43.710> set<00:05:43.919> we<00:05:44.190> didn't<00:05:44.400> have<00:05:44.580> to 00:05:44.719 --> 00:05:44.729 align:start position:0% was an upgrade per set we didn't have to 00:05:44.729 --> 00:05:47.689 align:start position:0% was an upgrade per set we didn't have to like<00:05:45.360> migrate<00:05:45.960> data<00:05:46.620> from<00:05:47.099> the<00:05:47.550> previous 00:05:47.689 --> 00:05:47.699 align:start position:0% like migrate data from the previous 00:05:47.699 --> 00:05:49.040 align:start position:0% like migrate data from the previous wallet<00:05:48.150> contract<00:05:48.449> to<00:05:48.509> the<00:05:48.599> new<00:05:48.719> one<00:05:48.870> were 00:05:49.040 --> 00:05:49.050 align:start position:0% wallet contract to the new one were 00:05:49.050 --> 00:05:52.249 align:start position:0% wallet contract to the new one were really<00:05:49.529> operating<00:05:49.650> it<00:05:50.009> so<00:05:50.940> how<00:05:51.870> was<00:05:52.020> that 00:05:52.249 --> 00:05:52.259 align:start position:0% really operating it so how was that 00:05:52.259 --> 00:05:56.059 align:start position:0% really operating it so how was that possible<00:05:53.060> I<00:05:54.060> think<00:05:54.509> that<00:05:54.750> many<00:05:55.529> many<00:05:55.889> of<00:05:55.979> you 00:05:56.059 --> 00:05:56.069 align:start position:0% possible I think that many many of you 00:05:56.069 --> 00:05:58.219 align:start position:0% possible I think that many many of you may<00:05:56.310> know<00:05:56.460> already<00:05:56.639> this<00:05:57.150> but<00:05:57.449> we're<00:05:58.020> using 00:05:58.219 --> 00:05:58.229 align:start position:0% may know already this but we're using 00:05:58.229 --> 00:06:01.570 align:start position:0% may know already this but we're using proxies<00:05:58.650> in<00:05:58.860> order<00:05:59.039> to<00:05:59.159> make<00:05:59.849> that<00:06:00.060> happen<00:06:00.210> and 00:06:01.570 --> 00:06:01.580 align:start position:0% proxies in order to make that happen and 00:06:01.580 --> 00:06:04.850 align:start position:0% proxies in order to make that happen and the<00:06:02.580> way<00:06:02.729> a<00:06:02.759> proxy<00:06:03.210> works<00:06:03.419> is<00:06:03.740> it's<00:06:04.740> a 00:06:04.850 --> 00:06:04.860 align:start position:0% the way a proxy works is it's a 00:06:04.860 --> 00:06:06.320 align:start position:0% the way a proxy works is it's a particular<00:06:05.279> contract<00:06:05.729> that<00:06:05.940> basically 00:06:06.320 --> 00:06:06.330 align:start position:0% particular contract that basically 00:06:06.330 --> 00:06:08.629 align:start position:0% particular contract that basically delegates<00:06:06.990> every<00:06:07.319> call<00:06:07.500> it<00:06:07.590> receives<00:06:08.159> to 00:06:08.629 --> 00:06:08.639 align:start position:0% delegates every call it receives to 00:06:08.639 --> 00:06:09.950 align:start position:0% delegates every call it receives to another<00:06:08.849> contract<00:06:09.270> that<00:06:09.389> is<00:06:09.479> called<00:06:09.690> logic 00:06:09.950 --> 00:06:09.960 align:start position:0% another contract that is called logic 00:06:09.960 --> 00:06:13.339 align:start position:0% another contract that is called logic contract<00:06:10.610> and<00:06:11.610> the<00:06:12.000> thing<00:06:12.120> is<00:06:12.240> that<00:06:12.270> logic<00:06:13.199> on 00:06:13.339 --> 00:06:13.349 align:start position:0% contract and the thing is that logic on 00:06:13.349 --> 00:06:15.290 align:start position:0% contract and the thing is that logic on the<00:06:13.380> others<00:06:13.740> of<00:06:13.949> the<00:06:13.979> logic<00:06:14.340> contract<00:06:14.789> can<00:06:15.150> be 00:06:15.290 --> 00:06:15.300 align:start position:0% the others of the logic contract can be 00:06:15.300 --> 00:06:19.610 align:start position:0% the others of the logic contract can be changed<00:06:15.659> and<00:06:15.810> this<00:06:15.990> is<00:06:16.110> how<00:06:16.289> every<00:06:16.560> W<00:06:16.860> works<00:06:18.620> as 00:06:19.610 --> 00:06:19.620 align:start position:0% changed and this is how every W works as 00:06:19.620 --> 00:06:21.980 align:start position:0% changed and this is how every W works as you<00:06:20.039> can<00:06:20.159> see<00:06:20.310> this<00:06:20.490> tourist<00:06:20.880> layer<00:06:21.120> layer<00:06:21.539> is 00:06:21.980 --> 00:06:21.990 align:start position:0% you can see this tourist layer layer is 00:06:21.990 --> 00:06:24.320 align:start position:0% you can see this tourist layer layer is always<00:06:22.289> kept<00:06:22.949> in<00:06:23.099> the<00:06:23.250> in<00:06:23.430> the<00:06:23.610> proxy<00:06:23.969> contract 00:06:24.320 --> 00:06:24.330 align:start position:0% always kept in the in the proxy contract 00:06:24.330 --> 00:06:25.939 align:start position:0% always kept in the in the proxy contract and<00:06:24.479> this<00:06:24.630> is<00:06:24.750> why<00:06:24.930> we<00:06:25.169> don't<00:06:25.289> need<00:06:25.409> to<00:06:25.710> migrate 00:06:25.939 --> 00:06:25.949 align:start position:0% and this is why we don't need to migrate 00:06:25.949 --> 00:06:29.749 align:start position:0% and this is why we don't need to migrate or<00:06:26.520> pay<00:06:27.270> any<00:06:27.599> like<00:06:28.469> spensive<00:06:29.039> migrations<00:06:29.669> of 00:06:29.749 --> 00:06:29.759 align:start position:0% or pay any like spensive migrations of 00:06:29.759 --> 00:06:32.719 align:start position:0% or pay any like spensive migrations of data<00:06:30.029> when<00:06:30.599> we<00:06:30.750> want<00:06:31.469> to<00:06:31.560> do<00:06:31.680> an<00:06:31.800> average<00:06:31.949> of<00:06:32.279> a 00:06:32.719 --> 00:06:32.729 align:start position:0% data when we want to do an average of a 00:06:32.729 --> 00:06:37.399 align:start position:0% data when we want to do an average of a contract<00:06:33.349> we're<00:06:34.349> not<00:06:34.529> going<00:06:34.949> to<00:06:35.479> so<00:06:36.479> much<00:06:36.990> even 00:06:37.399 --> 00:06:37.409 align:start position:0% contract we're not going to so much even 00:06:37.409 --> 00:06:40.580 align:start position:0% contract we're not going to so much even in<00:06:37.620> the<00:06:37.740> in<00:06:37.949> the<00:06:38.159> process<00:06:38.699> stuff<00:06:39.120> but<00:06:39.659> you<00:06:39.779> can 00:06:40.580 --> 00:06:40.590 align:start position:0% in the in the process stuff but you can 00:06:40.590 --> 00:06:42.890 align:start position:0% in the in the process stuff but you can more<00:06:41.070> about<00:06:41.610> it<00:06:41.730> in<00:06:41.910> you<00:06:42.090> know<00:06:42.180> documentation 00:06:42.890 --> 00:06:42.900 align:start position:0% more about it in you know documentation 00:06:42.900 --> 00:06:46.670 align:start position:0% more about it in you know documentation if<00:06:42.990> you<00:06:43.080> want<00:06:43.790> so<00:06:44.790> summing<00:06:45.450> things<00:06:45.630> up<00:06:45.840> subbing 00:06:46.670 --> 00:06:46.680 align:start position:0% if you want so summing things up subbing 00:06:46.680 --> 00:06:49.190 align:start position:0% if you want so summing things up subbing us<00:06:47.040> provides<00:06:47.520> a<00:06:47.730> standard<00:06:48.300> way<00:06:48.450> in<00:06:48.690> order<00:06:49.050> to 00:06:49.190 --> 00:06:49.200 align:start position:0% us provides a standard way in order to 00:06:49.200 --> 00:06:51.620 align:start position:0% us provides a standard way in order to have<00:06:49.950> a<00:06:50.130> grade<00:06:50.370> of<00:06:50.400> a<00:06:50.670> gorilla's<00:06:51.120> my<00:06:51.300> contracts 00:06:51.620 --> 00:06:51.630 align:start position:0% have a grade of a gorilla's my contracts 00:06:51.630 --> 00:06:53.150 align:start position:0% have a grade of a gorilla's my contracts in<00:06:51.750> your<00:06:51.870> projects<00:06:52.230> that<00:06:52.770> will<00:06:52.920> basically 00:06:53.150 --> 00:06:53.160 align:start position:0% in your projects that will basically 00:06:53.160 --> 00:06:54.830 align:start position:0% in your projects that will basically allow<00:06:53.520> you<00:06:53.640> to<00:06:53.910> fix<00:06:54.120> box<00:06:54.360> or<00:06:54.600> add 00:06:54.830 --> 00:06:54.840 align:start position:0% allow you to fix box or add 00:06:54.840 --> 00:06:59.060 align:start position:0% allow you to fix box or add functionality<00:06:55.260> for<00:06:55.650> example<00:06:57.200> so<00:06:58.200> let's<00:06:58.920> move 00:06:59.060 --> 00:06:59.070 align:start position:0% functionality for example so let's move 00:06:59.070 --> 00:07:01.310 align:start position:0% functionality for example so let's move to<00:06:59.130> the<00:06:59.310> second<00:06:59.700> topic<00:06:59.850> EVM<00:07:00.810> packages 00:07:01.310 --> 00:07:01.320 align:start position:0% to the second topic EVM packages 00:07:01.320 --> 00:07:03.710 align:start position:0% to the second topic EVM packages vivianne<00:07:02.220> packages<00:07:02.580> this<00:07:03.120> is<00:07:03.240> a<00:07:03.270> new<00:07:03.480> concept 00:07:03.710 --> 00:07:03.720 align:start position:0% vivianne packages this is a new concept 00:07:03.720 --> 00:07:07.340 align:start position:0% vivianne packages this is a new concept we<00:07:04.080> interviews<00:07:04.670> some<00:07:05.670> weeks<00:07:05.880> ago<00:07:06.350> evening 00:07:07.340 --> 00:07:07.350 align:start position:0% we interviews some weeks ago evening 00:07:07.350 --> 00:07:09.290 align:start position:0% we interviews some weeks ago evening packages<00:07:07.770> are<00:07:07.980> upgradeable<00:07:08.850> on<00:07:09.000> chain 00:07:09.290 --> 00:07:09.300 align:start position:0% packages are upgradeable on chain 00:07:09.300 --> 00:07:11.480 align:start position:0% packages are upgradeable on chain packages<00:07:09.750> of<00:07:09.960> smart<00:07:10.500> contracts<00:07:10.890> code<00:07:11.130> and 00:07:11.480 --> 00:07:11.490 align:start position:0% packages of smart contracts code and 00:07:11.490 --> 00:07:15.770 align:start position:0% packages of smart contracts code and this<00:07:12.030> means<00:07:13.340> code<00:07:14.340> that<00:07:14.520> is<00:07:14.910> already<00:07:15.270> on<00:07:15.510> chain 00:07:15.770 --> 00:07:15.780 align:start position:0% this means code that is already on chain 00:07:15.780 --> 00:07:17.960 align:start position:0% this means code that is already on chain deployed<00:07:16.470> by<00:07:16.680> another<00:07:17.040> developer<00:07:17.520> team<00:07:17.700> that 00:07:17.960 --> 00:07:17.970 align:start position:0% deployed by another developer team that 00:07:17.970 --> 00:07:19.520 align:start position:0% deployed by another developer team that it's<00:07:18.060> being<00:07:18.270> maintained<00:07:18.870> but<00:07:19.050> by<00:07:19.350> another 00:07:19.520 --> 00:07:19.530 align:start position:0% it's being maintained but by another 00:07:19.530 --> 00:07:21.290 align:start position:0% it's being maintained but by another developer<00:07:20.130> team<00:07:20.280> that<00:07:20.790> doing<00:07:21.060> any 00:07:21.290 --> 00:07:21.300 align:start position:0% developer team that doing any 00:07:21.300 --> 00:07:24.080 align:start position:0% developer team that doing any application<00:07:22.080> can<00:07:22.470> link<00:07:22.740> directly<00:07:23.400> through 00:07:24.080 --> 00:07:24.090 align:start position:0% application can link directly through 00:07:24.090 --> 00:07:26.120 align:start position:0% application can link directly through your<00:07:24.240> own<00:07:24.360> projects<00:07:24.840> in<00:07:25.200> order<00:07:25.350> to<00:07:25.530> reuse<00:07:25.770> it 00:07:26.120 --> 00:07:26.130 align:start position:0% your own projects in order to reuse it 00:07:26.130 --> 00:07:28.550 align:start position:0% your own projects in order to reuse it directly<00:07:26.760> on<00:07:26.910> chain<00:07:27.150> and<00:07:27.810> it<00:07:28.020> comes<00:07:28.290> off<00:07:28.440> of 00:07:28.550 --> 00:07:28.560 align:start position:0% directly on chain and it comes off of 00:07:28.560 --> 00:07:30.530 align:start position:0% directly on chain and it comes off of course<00:07:28.890> with<00:07:29.100> obscene<00:07:29.730> average<00:07:30.090> and<00:07:30.360> this 00:07:30.530 --> 00:07:30.540 align:start position:0% course with obscene average and this 00:07:30.540 --> 00:07:33.170 align:start position:0% course with obscene average and this means<00:07:30.690> that<00:07:30.860> if<00:07:31.860> the<00:07:32.130> developer<00:07:32.760> team<00:07:32.940> that<00:07:33.120> is 00:07:33.170 --> 00:07:33.180 align:start position:0% means that if the developer team that is 00:07:33.180 --> 00:07:35.450 align:start position:0% means that if the developer team that is developing<00:07:33.720> an<00:07:33.930> EVM<00:07:34.470> package<00:07:34.800> comes<00:07:35.160> with<00:07:35.430> a 00:07:35.450 --> 00:07:35.460 align:start position:0% developing an EVM package comes with a 00:07:35.460 --> 00:07:37.700 align:start position:0% developing an EVM package comes with a new<00:07:35.670> version<00:07:35.880> of<00:07:36.150> the<00:07:36.330> vm<00:07:36.600> package<00:07:36.900> you<00:07:37.530> can 00:07:37.700 --> 00:07:37.710 align:start position:0% new version of the vm package you can 00:07:37.710 --> 00:07:40.280 align:start position:0% new version of the vm package you can decide<00:07:38.070> where<00:07:38.310> to<00:07:38.490> operate<00:07:38.790> your<00:07:39.120> code<00:07:39.540> to<00:07:39.810> use 00:07:40.280 --> 00:07:40.290 align:start position:0% decide where to operate your code to use 00:07:40.290 --> 00:07:41.720 align:start position:0% decide where to operate your code to use the<00:07:40.320> new<00:07:40.560> version<00:07:40.770> that<00:07:41.100> they<00:07:41.190> are<00:07:41.250> providing 00:07:41.720 --> 00:07:41.730 align:start position:0% the new version that they are providing 00:07:41.730 --> 00:07:47.420 align:start position:0% the new version that they are providing or<00:07:42.090> not<00:07:42.330> so<00:07:44.720> why<00:07:45.720> do<00:07:45.780> we<00:07:45.930> need<00:07:46.050> IBM<00:07:46.470> packages<00:07:46.890> we 00:07:47.420 --> 00:07:47.430 align:start position:0% or not so why do we need IBM packages we 00:07:47.430 --> 00:07:48.980 align:start position:0% or not so why do we need IBM packages we do<00:07:47.520> think<00:07:47.790> that<00:07:47.940> this<00:07:48.120> is<00:07:48.270> a<00:07:48.300> way<00:07:48.540> in<00:07:48.570> order<00:07:48.870> to 00:07:48.980 --> 00:07:48.990 align:start position:0% do think that this is a way in order to 00:07:48.990 --> 00:07:51.560 align:start position:0% do think that this is a way in order to encourage<00:07:49.490> modular<00:07:50.490> development<00:07:50.670> the<00:07:51.390> thing 00:07:51.560 --> 00:07:51.570 align:start position:0% encourage modular development the thing 00:07:51.570 --> 00:07:53.780 align:start position:0% encourage modular development the thing this<00:07:51.990> is<00:07:52.170> you<00:07:52.860> can<00:07:52.980> you<00:07:53.100> can<00:07:53.220> start<00:07:53.460> focusing 00:07:53.780 --> 00:07:53.790 align:start position:0% this is you can you can start focusing 00:07:53.790 --> 00:07:56.950 align:start position:0% this is you can you can start focusing on<00:07:54.240> what<00:07:54.840> you<00:07:54.990> do<00:07:55.140> best<00:07:55.260> and<00:07:55.950> start<00:07:56.640> reusing 00:07:56.950 --> 00:07:56.960 align:start position:0% on what you do best and start reusing 00:07:56.960 --> 00:08:00.580 align:start position:0% on what you do best and start reusing the<00:07:57.960> work<00:07:58.110> that<00:07:58.290> your<00:07:58.560> college<00:07:58.800> has<00:07:59.520> done<00:07:59.730> so 00:08:00.580 --> 00:08:00.590 align:start position:0% the work that your college has done so 00:08:00.590 --> 00:08:02.780 align:start position:0% the work that your college has done so with<00:08:01.590> we<00:08:01.860> just<00:08:02.160> don't<00:08:02.370> need<00:08:02.490> to<00:08:02.550> build 00:08:02.780 --> 00:08:02.790 align:start position:0% with we just don't need to build 00:08:02.790 --> 00:08:04.700 align:start position:0% with we just don't need to build everything<00:08:03.330> if<00:08:03.480> you<00:08:03.810> want<00:08:03.840> to<00:08:04.110> build 00:08:04.700 --> 00:08:04.710 align:start position:0% everything if you want to build 00:08:04.710 --> 00:08:07.010 align:start position:0% everything if you want to build something<00:08:05.160> we<00:08:05.310> can<00:08:05.730> start<00:08:05.970> reusing<00:08:06.120> some<00:08:06.810> code 00:08:07.010 --> 00:08:07.020 align:start position:0% something we can start reusing some code 00:08:07.020 --> 00:08:08.900 align:start position:0% something we can start reusing some code that<00:08:07.170> is<00:08:07.290> already<00:08:07.650> deployed<00:08:07.950> on<00:08:08.130> chain<00:08:08.340> and<00:08:08.550> as 00:08:08.900 --> 00:08:08.910 align:start position:0% that is already deployed on chain and as 00:08:08.910 --> 00:08:10.700 align:start position:0% that is already deployed on chain and as I<00:08:08.940> said<00:08:09.150> before<00:08:09.210> EVM<00:08:10.140> packages<00:08:10.530> are 00:08:10.700 --> 00:08:10.710 align:start position:0% I said before EVM packages are 00:08:10.710 --> 00:08:12.890 align:start position:0% I said before EVM packages are upgradeable<00:08:11.460> by<00:08:11.640> definition<00:08:12.120> and<00:08:12.570> this<00:08:12.720> means 00:08:12.890 --> 00:08:12.900 align:start position:0% upgradeable by definition and this means 00:08:12.900 --> 00:08:14.930 align:start position:0% upgradeable by definition and this means that<00:08:12.990> their<00:08:13.710> developers<00:08:14.160> can<00:08:14.400> provide<00:08:14.670> new 00:08:14.930 --> 00:08:14.940 align:start position:0% that their developers can provide new 00:08:14.940 --> 00:08:17.330 align:start position:0% that their developers can provide new versions<00:08:15.390> of<00:08:15.630> the<00:08:15.810> ocbn<00:08:16.410> packages<00:08:16.800> and<00:08:16.950> you 00:08:17.330 --> 00:08:17.340 align:start position:0% versions of the ocbn packages and you 00:08:17.340 --> 00:08:20.360 align:start position:0% versions of the ocbn packages and you can<00:08:17.630> opt<00:08:18.630> in<00:08:18.930> decide<00:08:19.320> where<00:08:19.680> you<00:08:19.980> want<00:08:20.190> those 00:08:20.360 --> 00:08:20.370 align:start position:0% can opt in decide where you want those 00:08:20.370 --> 00:08:22.310 align:start position:0% can opt in decide where you want those upgrades<00:08:20.850> in<00:08:21.000> your<00:08:21.180> projects<00:08:21.720> or<00:08:21.780> not<00:08:21.990> it's 00:08:22.310 --> 00:08:22.320 align:start position:0% upgrades in your projects or not it's 00:08:22.320 --> 00:08:24.530 align:start position:0% upgrades in your projects or not it's like<00:08:22.620> any<00:08:22.890> other<00:08:23.210> dependency<00:08:24.210> management 00:08:24.530 --> 00:08:24.540 align:start position:0% like any other dependency management 00:08:24.540 --> 00:08:27.740 align:start position:0% like any other dependency management system<00:08:25.110> and<00:08:25.320> of<00:08:25.950> course<00:08:26.220> we're<00:08:26.880> saving<00:08:27.420> a<00:08:27.570> lot 00:08:27.740 --> 00:08:27.750 align:start position:0% system and of course we're saving a lot 00:08:27.750 --> 00:08:29.990 align:start position:0% system and of course we're saving a lot of<00:08:27.870> gas<00:08:28.200> costs<00:08:28.620> because<00:08:29.100> we're<00:08:29.310> reusing<00:08:29.520> some 00:08:29.990 --> 00:08:30.000 align:start position:0% of gas costs because we're reusing some 00:08:30.000 --> 00:08:31.400 align:start position:0% of gas costs because we're reusing some logic<00:08:30.330> that<00:08:30.360> is<00:08:30.570> already<00:08:30.840> deployed<00:08:31.050> on 00:08:31.400 --> 00:08:31.410 align:start position:0% logic that is already deployed on 00:08:31.410 --> 00:08:33.470 align:start position:0% logic that is already deployed on chained<00:08:31.710> by<00:08:31.980> those<00:08:32.220> developer<00:08:32.730> teams<00:08:32.940> and<00:08:33.390> we 00:08:33.470 --> 00:08:33.480 align:start position:0% chained by those developer teams and we 00:08:33.480 --> 00:08:35.510 align:start position:0% chained by those developer teams and we don't<00:08:33.630> have<00:08:33.750> to<00:08:33.870> redeploy<00:08:34.200> the<00:08:34.860> logic<00:08:35.220> every 00:08:35.510 --> 00:08:35.520 align:start position:0% don't have to redeploy the logic every 00:08:35.520 --> 00:08:39.320 align:start position:0% don't have to redeploy the logic every time<00:08:35.700> if<00:08:35.880> we<00:08:35.970> want<00:08:36.180> to<00:08:36.270> reuse<00:08:36.480> it<00:08:37.790> let's<00:08:38.790> take<00:08:39.300> a 00:08:39.320 --> 00:08:39.330 align:start position:0% time if we want to reuse it let's take a 00:08:39.330 --> 00:08:42.440 align:start position:0% time if we want to reuse it let's take a look<00:08:39.510> at<00:08:39.600> another<00:08:40.410> example<00:08:41.300> let's<00:08:42.300> say<00:08:42.420> that 00:08:42.440 --> 00:08:42.450 align:start position:0% look at another example let's say that 00:08:42.450 --> 00:08:45.110 align:start position:0% look at another example let's say that we<00:08:42.570> have<00:08:42.780> a<00:08:43.080> deck<00:08:43.740> contract<00:08:44.340> in<00:08:44.550> our<00:08:44.700> project 00:08:45.110 --> 00:08:45.120 align:start position:0% we have a deck contract in our project 00:08:45.120 --> 00:08:48.770 align:start position:0% we have a deck contract in our project and<00:08:45.270> as<00:08:45.570> you<00:08:45.690> can<00:08:45.780> see<00:08:46.100> because<00:08:47.100> an<00:08:47.610> ESD<00:08:48.210> 7:21 00:08:48.770 --> 00:08:48.780 align:start position:0% and as you can see because an ESD 7:21 00:08:48.780 --> 00:08:51.260 align:start position:0% and as you can see because an ESD 7:21 dependency<00:08:49.320> it<00:08:50.280> has<00:08:50.490> an<00:08:50.700> initialized 00:08:51.260 --> 00:08:51.270 align:start position:0% dependency it has an initialized 00:08:51.270 --> 00:08:53.930 align:start position:0% dependency it has an initialized function<00:08:51.720> in<00:08:51.870> order<00:08:52.050> to<00:08:52.170> receive<00:08:52.500> the 00:08:53.930 --> 00:08:53.940 align:start position:0% function in order to receive the 00:08:53.940 --> 00:08:55.940 align:start position:0% function in order to receive the you<00:08:53.970> see<00:08:54.180> 7:21<00:08:54.750> dependency<00:08:55.260> and<00:08:55.620> he<00:08:55.740> has 00:08:55.940 --> 00:08:55.950 align:start position:0% you see 7:21 dependency and he has 00:08:55.950 --> 00:08:58.670 align:start position:0% you see 7:21 dependency and he has another<00:08:56.310> function<00:08:56.810> called<00:08:57.810> peak<00:08:58.050> that<00:08:58.500> will 00:08:58.670 --> 00:08:58.680 align:start position:0% another function called peak that will 00:08:58.680 --> 00:09:01.220 align:start position:0% another function called peak that will basically<00:08:58.890> allow<00:08:59.160> any<00:08:59.580> users<00:09:00.060> to<00:09:00.270> pick<00:09:00.450> cards 00:09:01.220 --> 00:09:01.230 align:start position:0% basically allow any users to pick cards 00:09:01.230 --> 00:09:03.230 align:start position:0% basically allow any users to pick cards from<00:09:01.500> the<00:09:01.710> from<00:09:02.250> the<00:09:02.340> contract<00:09:02.760> and<00:09:02.940> you<00:09:03.060> will 00:09:03.230 --> 00:09:03.240 align:start position:0% from the from the contract and you will 00:09:03.240 --> 00:09:05.720 align:start position:0% from the from the contract and you will be<00:09:03.360> minting<00:09:03.870> New<00:09:04.080> Year<00:09:04.350> seats<00:09:04.590> 1701<00:09:05.250> tokens 00:09:05.720 --> 00:09:05.730 align:start position:0% be minting New Year seats 1701 tokens 00:09:05.730 --> 00:09:08.330 align:start position:0% be minting New Year seats 1701 tokens every<00:09:06.240> time<00:09:06.390> and<00:09:06.540> users<00:09:06.780> a<00:09:07.020> user<00:09:07.650> picks<00:09:07.920> a<00:09:08.130> new 00:09:08.330 --> 00:09:08.340 align:start position:0% every time and users a user picks a new 00:09:08.340 --> 00:09:12.200 align:start position:0% every time and users a user picks a new card<00:09:08.750> so<00:09:10.220> havecome<00:09:11.220> create<00:09:11.760> an<00:09:11.970> array<00:09:12.180> of 00:09:12.200 --> 00:09:12.210 align:start position:0% card so havecome create an array of 00:09:12.210 --> 00:09:15.170 align:start position:0% card so havecome create an array of instance<00:09:12.630> of<00:09:12.840> this<00:09:13.110> contract<00:09:13.490> reusing<00:09:14.490> an<00:09:14.730> EVM 00:09:15.170 --> 00:09:15.180 align:start position:0% instance of this contract reusing an EVM 00:09:15.180 --> 00:09:17.360 align:start position:0% instance of this contract reusing an EVM package<00:09:15.540> for<00:09:16.260> the<00:09:16.350> Year<00:09:16.620> season<00:09:16.770> you<00:09:17.100> want<00:09:17.220> to 00:09:17.360 --> 00:09:17.370 align:start position:0% package for the Year season you want to 00:09:17.370 --> 00:09:20.000 align:start position:0% package for the Year season you want to turn<00:09:17.550> 21<00:09:18.030> dependency<00:09:18.570> using<00:09:18.990> southern<00:09:19.260> OS<00:09:19.560> so 00:09:20.000 --> 00:09:20.010 align:start position:0% turn 21 dependency using southern OS so 00:09:20.010 --> 00:09:23.420 align:start position:0% turn 21 dependency using southern OS so it<00:09:20.880> will<00:09:21.000> be<00:09:21.120> reasonable<00:09:21.690> once<00:09:21.840> again<00:09:22.430> the 00:09:23.420 --> 00:09:23.430 align:start position:0% it will be reasonable once again the 00:09:23.430 --> 00:09:25.730 align:start position:0% it will be reasonable once again the first<00:09:23.670> thing<00:09:24.120> we<00:09:24.330> should<00:09:24.570> do<00:09:24.840> is<00:09:24.870> thank<00:09:25.530> yous 00:09:25.730 --> 00:09:25.740 align:start position:0% first thing we should do is thank yous 00:09:25.740 --> 00:09:29.090 align:start position:0% first thing we should do is thank yous when<00:09:26.370> it<00:09:26.460> comes<00:09:26.610> to<00:09:26.700> the<00:09:26.820> new<00:09:27.810> part<00:09:28.080> the<00:09:28.620> link 00:09:29.090 --> 00:09:29.100 align:start position:0% when it comes to the new part the link 00:09:29.100 --> 00:09:31.460 align:start position:0% when it comes to the new part the link command<00:09:29.400> will<00:09:29.580> allow<00:09:29.790> you<00:09:30.330> to<00:09:30.360> link<00:09:30.870> to<00:09:31.320> any 00:09:31.460 --> 00:09:31.470 align:start position:0% command will allow you to link to any 00:09:31.470 --> 00:09:33.350 align:start position:0% command will allow you to link to any other<00:09:31.860> AVM<00:09:32.520> package<00:09:32.880> that<00:09:33.060> is<00:09:33.180> already 00:09:33.350 --> 00:09:33.360 align:start position:0% other AVM package that is already 00:09:33.360 --> 00:09:35.750 align:start position:0% other AVM package that is already deployed<00:09:33.630> on<00:09:34.080> chain<00:09:34.410> in<00:09:34.920> this<00:09:35.100> case<00:09:35.340> we're 00:09:35.750 --> 00:09:35.760 align:start position:0% deployed on chain in this case we're 00:09:35.760 --> 00:09:38.240 align:start position:0% deployed on chain in this case we're linking<00:09:35.970> our<00:09:36.390> projects<00:09:37.110> to<00:09:37.560> the<00:09:37.710> open<00:09:38.100> sea 00:09:38.240 --> 00:09:38.250 align:start position:0% linking our projects to the open sea 00:09:38.250 --> 00:09:40.790 align:start position:0% linking our projects to the open sea beneath<00:09:38.370> a<00:09:39.000> VM<00:09:39.390> package<00:09:39.720> and<00:09:40.020> this<00:09:40.350> package<00:09:40.560> is 00:09:40.790 --> 00:09:40.800 align:start position:0% beneath a VM package and this package is 00:09:40.800 --> 00:09:42.650 align:start position:0% beneath a VM package and this package is the<00:09:41.010> VM<00:09:41.310> package<00:09:41.610> that<00:09:41.820> the<00:09:41.970> open<00:09:42.360> sibling 00:09:42.650 --> 00:09:42.660 align:start position:0% the VM package that the open sibling 00:09:42.660 --> 00:09:45.800 align:start position:0% the VM package that the open sibling team<00:09:42.840> has<00:09:43.770> provided<00:09:44.010> on<00:09:44.460> chain<00:09:44.880> in<00:09:45.390> this<00:09:45.630> case 00:09:45.800 --> 00:09:45.810 align:start position:0% team has provided on chain in this case 00:09:45.810 --> 00:09:48.920 align:start position:0% team has provided on chain in this case we're<00:09:45.990> linking<00:09:46.170> to<00:09:46.470> the<00:09:46.620> 2.0<00:09:47.250> version<00:09:47.490> and<00:09:48.150> as 00:09:48.920 --> 00:09:48.930 align:start position:0% we're linking to the 2.0 version and as 00:09:48.930 --> 00:09:51.290 align:start position:0% we're linking to the 2.0 version and as we<00:09:49.110> did<00:09:49.260> before<00:09:49.410> we<00:09:50.040> just<00:09:50.220> need<00:09:50.400> to<00:09:50.550> put<00:09:50.820> those 00:09:51.290 --> 00:09:51.300 align:start position:0% we did before we just need to put those 00:09:51.300 --> 00:09:54.020 align:start position:0% we did before we just need to put those changes<00:09:51.720> to<00:09:51.840> the<00:09:51.930> network<00:09:52.230> and<00:09:52.850> finally<00:09:53.850> we 00:09:54.020 --> 00:09:54.030 align:start position:0% changes to the network and finally we 00:09:54.030 --> 00:09:55.880 align:start position:0% changes to the network and finally we can<00:09:54.180> run<00:09:54.510> the<00:09:54.660> create<00:09:54.870> command<00:09:55.110> and<00:09:55.470> as<00:09:55.770> you 00:09:55.880 --> 00:09:55.890 align:start position:0% can run the create command and as you 00:09:55.890 --> 00:09:58.090 align:start position:0% can run the create command and as you can<00:09:56.010> see<00:09:56.190> here<00:09:56.430> we're<00:09:56.640> creating<00:09:57.030> an<00:09:57.450> instance 00:09:58.090 --> 00:09:58.100 align:start position:0% can see here we're creating an instance 00:09:58.100 --> 00:10:01.460 align:start position:0% can see here we're creating an instance reusing<00:09:59.100> the<00:09:59.280> logic<00:09:59.610> of<00:09:59.760> the<00:09:59.880> Year<00:10:00.270> c7<00:10:00.690> 21<00:10:01.140> that 00:10:01.460 --> 00:10:01.470 align:start position:0% reusing the logic of the Year c7 21 that 00:10:01.470 --> 00:10:03.140 align:start position:0% reusing the logic of the Year c7 21 that has<00:10:01.650> been<00:10:01.860> already<00:10:02.130> employed<00:10:02.610> by<00:10:02.790> the<00:10:02.850> open 00:10:03.140 --> 00:10:03.150 align:start position:0% has been already employed by the open 00:10:03.150 --> 00:10:06.050 align:start position:0% has been already employed by the open sibling<00:10:03.480> team<00:10:03.690> we<00:10:04.260> haven't<00:10:04.790> added<00:10:05.790> that 00:10:06.050 --> 00:10:06.060 align:start position:0% sibling team we haven't added that 00:10:06.060 --> 00:10:07.670 align:start position:0% sibling team we haven't added that contract<00:10:06.510> in<00:10:06.690> your<00:10:06.840> inner<00:10:07.080> projects<00:10:07.470> we<00:10:07.650> are 00:10:07.670 --> 00:10:07.680 align:start position:0% contract in your inner projects we are 00:10:07.680 --> 00:10:09.920 align:start position:0% contract in your inner projects we are reusing<00:10:08.220> the<00:10:08.820> same<00:10:08.850> logic<00:10:09.270> that<00:10:09.450> the<00:10:09.690> open 00:10:09.920 --> 00:10:09.930 align:start position:0% reusing the same logic that the open 00:10:09.930 --> 00:10:11.840 align:start position:0% reusing the same logic that the open sailing<00:10:10.200> team<00:10:10.320> has<00:10:10.650> provided<00:10:10.950> on<00:10:11.250> shame<00:10:11.640> for 00:10:11.840 --> 00:10:11.850 align:start position:0% sailing team has provided on shame for 00:10:11.850 --> 00:10:14.360 align:start position:0% sailing team has provided on shame for us<00:10:11.970> and<00:10:12.210> we'll<00:10:13.050> receive<00:10:13.440> of<00:10:13.680> course<00:10:14.220> the 00:10:14.360 --> 00:10:14.370 align:start position:0% us and we'll receive of course the 00:10:14.370 --> 00:10:16.610 align:start position:0% us and we'll receive of course the others<00:10:14.670> of<00:10:14.850> our<00:10:15.060> available<00:10:15.810> instance<00:10:16.320> of<00:10:16.500> the 00:10:16.610 --> 00:10:16.620 align:start position:0% others of our available instance of the 00:10:16.620 --> 00:10:18.890 align:start position:0% others of our available instance of the Year<00:10:16.800> system<00:10:17.190> and<00:10:17.280> 21<00:10:17.580> there 00:10:18.890 --> 00:10:18.900 align:start position:0% Year system and 21 there 00:10:18.900 --> 00:10:22.640 align:start position:0% Year system and 21 there so<00:10:19.710> let's<00:10:20.130> now<00:10:20.430> create<00:10:20.790> let's<00:10:21.480> use<00:10:21.840> this<00:10:22.050> new 00:10:22.640 --> 00:10:22.650 align:start position:0% so let's now create let's use this new 00:10:22.650 --> 00:10:24.830 align:start position:0% so let's now create let's use this new year<00:10:23.220> Cicero<00:10:23.820> instance<00:10:24.180> in<00:10:24.330> order<00:10:24.450> to<00:10:24.570> create 00:10:24.830 --> 00:10:24.840 align:start position:0% year Cicero instance in order to create 00:10:24.840 --> 00:10:27.140 align:start position:0% year Cicero instance in order to create an<00:10:25.170> instance<00:10:25.920> of<00:10:26.040> our<00:10:26.280> contract<00:10:26.880> the<00:10:26.970> deck 00:10:27.140 --> 00:10:27.150 align:start position:0% an instance of our contract the deck 00:10:27.150 --> 00:10:29.390 align:start position:0% an instance of our contract the deck contract<00:10:27.750> as<00:10:28.350> we<00:10:28.560> did<00:10:28.710> before<00:10:28.800> in<00:10:29.070> this<00:10:29.160> case 00:10:29.390 --> 00:10:29.400 align:start position:0% contract as we did before in this case 00:10:29.400 --> 00:10:32.450 align:start position:0% contract as we did before in this case we<00:10:29.610> do<00:10:29.730> need<00:10:29.940> to<00:10:30.120> add<00:10:30.270> the<00:10:30.750> deck<00:10:31.470> contract<00:10:32.100> so 00:10:32.450 --> 00:10:32.460 align:start position:0% we do need to add the deck contract so 00:10:32.460 --> 00:10:34.580 align:start position:0% we do need to add the deck contract so we<00:10:33.090> were<00:10:33.390> running<00:10:33.540> there<00:10:33.840> D<00:10:33.990> I've<00:10:34.200> come<00:10:34.440> and 00:10:34.580 --> 00:10:34.590 align:start position:0% we were running there D I've come and 00:10:34.590 --> 00:10:37.790 align:start position:0% we were running there D I've come and then<00:10:35.400> we're<00:10:35.580> pushing<00:10:35.850> the<00:10:36.300> the<00:10:36.620> source<00:10:37.620> code 00:10:37.790 --> 00:10:37.800 align:start position:0% then we're pushing the the source code 00:10:37.800 --> 00:10:39.470 align:start position:0% then we're pushing the the source code of<00:10:37.950> the<00:10:38.100> deck<00:10:38.280> contract<00:10:38.700> to<00:10:38.820> the<00:10:38.910> network<00:10:39.270> and 00:10:39.470 --> 00:10:39.480 align:start position:0% of the deck contract to the network and 00:10:39.480 --> 00:10:41.690 align:start position:0% of the deck contract to the network and finally<00:10:40.380> we<00:10:40.890> are<00:10:40.920> running<00:10:41.190> the<00:10:41.400> create 00:10:41.690 --> 00:10:41.700 align:start position:0% finally we are running the create 00:10:41.700 --> 00:10:43.310 align:start position:0% finally we are running the create command<00:10:41.880> in<00:10:42.480> order<00:10:42.660> to<00:10:42.780> create<00:10:43.020> a<00:10:43.080> new 00:10:43.310 --> 00:10:43.320 align:start position:0% command in order to create a new 00:10:43.320 --> 00:10:45.320 align:start position:0% command in order to create a new instance<00:10:43.500> of<00:10:43.830> the<00:10:44.130> deck<00:10:44.550> contract<00:10:45.150> and 00:10:45.320 --> 00:10:45.330 align:start position:0% instance of the deck contract and 00:10:45.330 --> 00:10:47.210 align:start position:0% instance of the deck contract and passing<00:10:45.900> through<00:10:46.050> the<00:10:46.290> address<00:10:46.650> of<00:10:46.830> the<00:10:46.980> USC 00:10:47.210 --> 00:10:47.220 align:start position:0% passing through the address of the USC 00:10:47.220 --> 00:10:49.760 align:start position:0% passing through the address of the USC 7:21<00:10:47.910> instance<00:10:48.330> that<00:10:48.480> we<00:10:48.630> created<00:10:48.960> before<00:10:49.080> and 00:10:49.760 --> 00:10:49.770 align:start position:0% 7:21 instance that we created before and 00:10:49.770 --> 00:10:52.570 align:start position:0% 7:21 instance that we created before and we<00:10:49.920> will<00:10:50.580> receive<00:10:50.910> their<00:10:51.150> the<00:10:51.360> address<00:10:51.660> of<00:10:51.839> our 00:10:52.570 --> 00:10:52.580 align:start position:0% we will receive their the address of our 00:10:52.580 --> 00:10:54.980 align:start position:0% we will receive their the address of our available<00:10:53.580> instance<00:10:53.940> of<00:10:54.089> the<00:10:54.240> deck<00:10:54.390> contract 00:10:54.980 --> 00:10:54.990 align:start position:0% available instance of the deck contract 00:10:54.990 --> 00:10:57.850 align:start position:0% available instance of the deck contract so<00:10:55.589> as<00:10:56.040> you<00:10:56.190> can<00:10:56.280> see<00:10:56.460> we<00:10:56.670> can<00:10:56.790> start<00:10:57.060> reusing 00:10:57.850 --> 00:10:57.860 align:start position:0% so as you can see we can start reusing 00:10:57.860 --> 00:11:02.420 align:start position:0% so as you can see we can start reusing the<00:10:58.860> deck<00:10:59.040> contract<00:10:59.630> and<00:11:00.680> and<00:11:01.680> it<00:11:01.890> will<00:11:02.040> be<00:11:02.160> we 00:11:02.420 --> 00:11:02.430 align:start position:0% the deck contract and and it will be we 00:11:02.430 --> 00:11:03.890 align:start position:0% the deck contract and and it will be we can<00:11:02.460> start<00:11:02.760> picking<00:11:02.880> cards<00:11:03.180> will<00:11:03.780> be 00:11:03.890 --> 00:11:03.900 align:start position:0% can start picking cards will be 00:11:03.900 --> 00:11:06.889 align:start position:0% can start picking cards will be maintained<00:11:04.500> year<00:11:04.680> season<00:11:05.040> 21 00:11:06.889 --> 00:11:06.899 align:start position:0% maintained year season 21 00:11:06.899 --> 00:11:09.819 align:start position:0% maintained year season 21 tokens<00:11:07.709> it<00:11:08.279> will<00:11:08.430> be<00:11:08.579> as<00:11:08.699> simple<00:11:09.149> as<00:11:09.269> that<00:11:09.420> so 00:11:09.819 --> 00:11:09.829 align:start position:0% tokens it will be as simple as that so 00:11:09.829 --> 00:11:13.160 align:start position:0% tokens it will be as simple as that so this<00:11:10.829> is<00:11:10.889> amazing<00:11:11.689> we<00:11:12.689> think<00:11:12.869> it<00:11:12.930> have<00:11:13.019> to 00:11:13.160 --> 00:11:13.170 align:start position:0% this is amazing we think it have to 00:11:13.170 --> 00:11:16.280 align:start position:0% this is amazing we think it have to deploy<00:11:13.589> an<00:11:13.920> ESD<00:11:14.279> CERN<00:11:14.459> you<00:11:14.579> turn<00:11:14.999> 21<00:11:15.329> contract 00:11:16.280 --> 00:11:16.290 align:start position:0% deploy an ESD CERN you turn 21 contract 00:11:16.290 --> 00:11:17.989 align:start position:0% deploy an ESD CERN you turn 21 contract in<00:11:16.379> order<00:11:16.499> to<00:11:16.709> reuse<00:11:17.160> it<00:11:17.279> where<00:11:17.730> it<00:11:17.819> just 00:11:17.989 --> 00:11:17.999 align:start position:0% in order to reuse it where it just 00:11:17.999 --> 00:11:19.609 align:start position:0% in order to reuse it where it just reusing<00:11:18.540> the<00:11:18.629> one<00:11:18.779> that<00:11:18.959> the<00:11:19.050> open<00:11:19.290> supplying 00:11:19.609 --> 00:11:19.619 align:start position:0% reusing the one that the open supplying 00:11:19.619 --> 00:11:21.499 align:start position:0% reusing the one that the open supplying team<00:11:19.800> has<00:11:19.980> provided<00:11:20.279> for<00:11:20.579> us<00:11:20.639> and<00:11:21.119> this<00:11:21.389> is 00:11:21.499 --> 00:11:21.509 align:start position:0% team has provided for us and this is 00:11:21.509 --> 00:11:25.970 align:start position:0% team has provided for us and this is really<00:11:22.079> cool<00:11:22.379> so<00:11:23.309> I<00:11:23.639> said<00:11:24.449> before<00:11:24.689> that<00:11:24.980> EVM 00:11:25.970 --> 00:11:25.980 align:start position:0% really cool so I said before that EVM 00:11:25.980 --> 00:11:28.100 align:start position:0% really cool so I said before that EVM packages<00:11:26.429> are<00:11:26.670> available<00:11:27.300> by<00:11:27.420> definition<00:11:27.839> now 00:11:28.100 --> 00:11:28.110 align:start position:0% packages are available by definition now 00:11:28.110 --> 00:11:30.199 align:start position:0% packages are available by definition now let's<00:11:28.679> see<00:11:28.800> an<00:11:28.889> example<00:11:29.129> of<00:11:29.279> what<00:11:29.730> does<00:11:30.089> it 00:11:30.199 --> 00:11:30.209 align:start position:0% let's see an example of what does it 00:11:30.209 --> 00:11:32.030 align:start position:0% let's see an example of what does it mean<00:11:30.329> let's<00:11:31.139> say<00:11:31.259> that<00:11:31.379> the<00:11:31.470> open<00:11:31.679> seven<00:11:31.889> team 00:11:32.030 --> 00:11:32.040 align:start position:0% mean let's say that the open seven team 00:11:32.040 --> 00:11:34.460 align:start position:0% mean let's say that the open seven team comes<00:11:32.369> with<00:11:32.610> a<00:11:32.639> new<00:11:32.879> version<00:11:33.089> of<00:11:33.449> their<00:11:33.839> EVM 00:11:34.460 --> 00:11:34.470 align:start position:0% comes with a new version of their EVM 00:11:34.470 --> 00:11:36.530 align:start position:0% comes with a new version of their EVM package<00:11:34.829> in<00:11:35.069> this<00:11:35.279> case<00:11:35.459> the<00:11:35.759> open<00:11:36.179> civilian 00:11:36.530 --> 00:11:36.540 align:start position:0% package in this case the open civilian 00:11:36.540 --> 00:11:39.169 align:start position:0% package in this case the open civilian if<00:11:36.809> as<00:11:37.499> I<00:11:37.829> said<00:11:38.009> before<00:11:38.160> and<00:11:38.639> let's<00:11:39.059> say<00:11:39.149> that 00:11:39.169 --> 00:11:39.179 align:start position:0% if as I said before and let's say that 00:11:39.179 --> 00:11:41.689 align:start position:0% if as I said before and let's say that we<00:11:39.600> want<00:11:39.809> to<00:11:39.869> use<00:11:40.110> use<00:11:40.649> it<00:11:40.829> in<00:11:40.980> our<00:11:41.069> project<00:11:41.309> and 00:11:41.689 --> 00:11:41.699 align:start position:0% we want to use use it in our project and 00:11:41.699 --> 00:11:44.629 align:start position:0% we want to use use it in our project and as<00:11:42.240> you<00:11:42.389> can<00:11:42.509> see<00:11:43.100> this<00:11:44.100> is<00:11:44.249> an<00:11:44.369> opt-in 00:11:44.629 --> 00:11:44.639 align:start position:0% as you can see this is an opt-in 00:11:44.639 --> 00:11:47.660 align:start position:0% as you can see this is an opt-in decision<00:11:45.059> I<00:11:45.149> said<00:11:45.329> before<00:11:45.920> so<00:11:46.920> in<00:11:47.309> order<00:11:47.429> to 00:11:47.660 --> 00:11:47.670 align:start position:0% decision I said before so in order to 00:11:47.670 --> 00:11:49.639 align:start position:0% decision I said before so in order to tell<00:11:48.119> us<00:11:48.209> upon<00:11:48.449> us<00:11:48.660> that<00:11:48.839> we<00:11:48.990> want<00:11:49.170> to<00:11:49.290> use<00:11:49.439> that 00:11:49.639 --> 00:11:49.649 align:start position:0% tell us upon us that we want to use that 00:11:49.649 --> 00:11:52.009 align:start position:0% tell us upon us that we want to use that up<00:11:49.829> with<00:11:50.160> that<00:11:50.490> new<00:11:50.699> version<00:11:50.910> in<00:11:51.360> our<00:11:51.509> project 00:11:52.009 --> 00:11:52.019 align:start position:0% up with that new version in our project 00:11:52.019 --> 00:11:54.319 align:start position:0% up with that new version in our project we<00:11:52.259> need<00:11:52.379> to<00:11:52.529> tell<00:11:52.709> us<00:11:53.220> that<00:11:53.399> we<00:11:53.759> want<00:11:53.939> to<00:11:54.059> link 00:11:54.319 --> 00:11:54.329 align:start position:0% we need to tell us that we want to link 00:11:54.329 --> 00:11:55.910 align:start position:0% we need to tell us that we want to link our<00:11:54.540> project<00:11:54.990> to<00:11:55.079> the<00:11:55.199> new<00:11:55.319> version<00:11:55.499> as<00:11:55.889> you 00:11:55.910 --> 00:11:55.920 align:start position:0% our project to the new version as you 00:11:55.920 --> 00:11:58.639 align:start position:0% our project to the new version as you can<00:11:56.009> see<00:11:56.249> here<00:11:56.429> were<00:11:56.579> linking<00:11:57.059> our<00:11:57.540> project<00:11:58.170> to 00:11:58.639 --> 00:11:58.649 align:start position:0% can see here were linking our project to 00:11:58.649 --> 00:12:02.150 align:start position:0% can see here were linking our project to the<00:11:58.800> 2.1<00:11:59.309> version<00:12:00.029> of<00:12:00.149> the<00:12:00.269> open<00:12:00.540> 17<00:12:00.959> if<00:12:01.160> EVM 00:12:02.150 --> 00:12:02.160 align:start position:0% the 2.1 version of the open 17 if EVM 00:12:02.160 --> 00:12:06.230 align:start position:0% the 2.1 version of the open 17 if EVM package<00:12:02.959> once<00:12:03.959> again<00:12:04.230> we're<00:12:04.470> pushing<00:12:05.240> those 00:12:06.230 --> 00:12:06.240 align:start position:0% package once again we're pushing those 00:12:06.240 --> 00:12:08.780 align:start position:0% package once again we're pushing those changes<00:12:06.629> to<00:12:06.809> the<00:12:06.899> network<00:12:07.050> and<00:12:07.410> finally<00:12:08.100> we 00:12:08.780 --> 00:12:08.790 align:start position:0% changes to the network and finally we 00:12:08.790 --> 00:12:11.119 align:start position:0% changes to the network and finally we can<00:12:08.939> run<00:12:09.149> run<00:12:09.839> in<00:12:10.019> this<00:12:10.139> case<00:12:10.350> the<00:12:10.589> update 00:12:11.119 --> 00:12:11.129 align:start position:0% can run run in this case the update 00:12:11.129 --> 00:12:13.189 align:start position:0% can run run in this case the update command<00:12:11.490> in<00:12:11.699> order<00:12:11.790> to<00:12:11.939> update<00:12:12.209> the<00:12:12.749> available 00:12:13.189 --> 00:12:13.199 align:start position:0% command in order to update the available 00:12:13.199 --> 00:12:14.900 align:start position:0% command in order to update the available instance<00:12:13.559> that<00:12:13.709> we<00:12:13.829> created<00:12:14.220> before<00:12:14.339> of<00:12:14.759> the 00:12:14.900 --> 00:12:14.910 align:start position:0% instance that we created before of the 00:12:14.910 --> 00:12:18.470 align:start position:0% instance that we created before of the USC<00:12:15.179> 7:21<00:12:15.959> contract<00:12:16.439> and<00:12:17.179> as<00:12:18.179> you<00:12:18.329> can<00:12:18.420> see 00:12:18.470 --> 00:12:18.480 align:start position:0% USC 7:21 contract and as you can see 00:12:18.480 --> 00:12:21.860 align:start position:0% USC 7:21 contract and as you can see will<00:12:19.439> be<00:12:19.470> pink<00:12:20.309> picking<00:12:20.819> new<00:12:21.059> carts<00:12:21.689> again 00:12:21.860 --> 00:12:21.870 align:start position:0% will be pink picking new carts again 00:12:21.870 --> 00:12:23.900 align:start position:0% will be pink picking new carts again with<00:12:22.050> the<00:12:22.230> same<00:12:22.529> thing<00:12:22.920> that<00:12:23.249> contract<00:12:23.850> that 00:12:23.900 --> 00:12:23.910 align:start position:0% with the same thing that contract that 00:12:23.910 --> 00:12:25.549 align:start position:0% with the same thing that contract that we<00:12:24.059> created<00:12:24.420> before<00:12:24.509> the<00:12:24.720> address<00:12:25.230> of<00:12:25.439> the 00:12:25.549 --> 00:12:25.559 align:start position:0% we created before the address of the 00:12:25.559 --> 00:12:27.439 align:start position:0% we created before the address of the deck<00:12:25.709> contract<00:12:26.220> hasn't<00:12:26.429> changed<00:12:26.910> and<00:12:27.269> we'll 00:12:27.439 --> 00:12:27.449 align:start position:0% deck contract hasn't changed and we'll 00:12:27.449 --> 00:12:30.799 align:start position:0% deck contract hasn't changed and we'll be<00:12:27.660> using<00:12:28.620> this<00:12:29.189> new<00:12:30.029> version<00:12:30.269> of<00:12:30.540> the<00:12:30.660> year 00:12:30.799 --> 00:12:30.809 align:start position:0% be using this new version of the year 00:12:30.809 --> 00:12:34.340 align:start position:0% be using this new version of the year since<00:12:30.990> 7:21<00:12:32.269> it<00:12:33.269> will<00:12:33.480> be<00:12:33.600> as<00:12:33.870> simple<00:12:34.079> as<00:12:34.199> that 00:12:34.340 --> 00:12:34.350 align:start position:0% since 7:21 it will be as simple as that 00:12:34.350 --> 00:12:36.470 align:start position:0% since 7:21 it will be as simple as that once<00:12:34.709> again<00:12:34.949> and<00:12:35.129> as<00:12:35.790> you<00:12:35.910> can<00:12:36.029> see<00:12:36.179> we<00:12:36.329> didn't 00:12:36.470 --> 00:12:36.480 align:start position:0% once again and as you can see we didn't 00:12:36.480 --> 00:12:39.169 align:start position:0% once again and as you can see we didn't have<00:12:36.689> to<00:12:36.839> update<00:12:37.170> our<00:12:37.550> contract<00:12:38.550> we<00:12:38.790> just<00:12:38.999> need 00:12:39.169 --> 00:12:39.179 align:start position:0% have to update our contract we just need 00:12:39.179 --> 00:12:40.730 align:start position:0% have to update our contract we just need to<00:12:39.389> update<00:12:39.569> the<00:12:39.870> dependency<00:12:40.439> that<00:12:40.559> we're 00:12:40.730 --> 00:12:40.740 align:start position:0% to update the dependency that we're 00:12:40.740 --> 00:12:42.439 align:start position:0% to update the dependency that we're using<00:12:40.920> in<00:12:41.220> our<00:12:41.279> project<00:12:41.790> in<00:12:41.910> this<00:12:41.999> case<00:12:42.209> the 00:12:42.439 --> 00:12:42.449 align:start position:0% using in our project in this case the 00:12:42.449 --> 00:12:47.619 align:start position:0% using in our project in this case the USC<00:12:42.779> 7:21<00:12:44.209> so<00:12:45.209> summing<00:12:46.019> things<00:12:46.170> up<00:12:46.379> even 00:12:47.619 --> 00:12:47.629 align:start position:0% USC 7:21 so summing things up even 00:12:47.629 --> 00:12:50.869 align:start position:0% USC 7:21 so summing things up even packages<00:12:48.629> allows<00:12:49.079> us<00:12:49.410> to<00:12:49.679> reuse<00:12:50.160> code<00:12:50.490> that<00:12:50.759> is 00:12:50.869 --> 00:12:50.879 align:start position:0% packages allows us to reuse code that is 00:12:50.879 --> 00:12:53.150 align:start position:0% packages allows us to reuse code that is already<00:12:51.420> deploying<00:12:51.779> on<00:12:52.019> chain<00:12:52.439> that<00:12:52.920> we<00:12:53.009> don't 00:12:53.150 --> 00:12:53.160 align:start position:0% already deploying on chain that we don't 00:12:53.160 --> 00:12:55.009 align:start position:0% already deploying on chain that we don't have<00:12:53.309> to<00:12:53.459> redeploy<00:12:53.790> it<00:12:54.120> every<00:12:54.509> time<00:12:54.720> we<00:12:54.839> want 00:12:55.009 --> 00:12:55.019 align:start position:0% have to redeploy it every time we want 00:12:55.019 --> 00:12:58.009 align:start position:0% have to redeploy it every time we want to<00:12:55.110> use<00:12:55.290> it<00:12:55.470> and<00:12:55.620> of<00:12:56.399> course<00:12:56.459> we<00:12:56.970> can<00:12:57.149> as<00:12:57.420> we<00:12:57.870> saw 00:12:58.009 --> 00:12:58.019 align:start position:0% to use it and of course we can as we saw 00:12:58.019 --> 00:13:00.350 align:start position:0% to use it and of course we can as we saw before<00:12:58.170> we<00:12:58.529> can<00:12:58.649> opt<00:12:58.920> in<00:12:59.179> update<00:13:00.179> our 00:13:00.350 --> 00:13:00.360 align:start position:0% before we can opt in update our 00:13:00.360 --> 00:13:03.289 align:start position:0% before we can opt in update our dependencies<00:13:01.110> if<00:13:01.439> the<00:13:02.040> developers<00:13:02.910> of<00:13:03.059> those 00:13:03.289 --> 00:13:03.299 align:start position:0% dependencies if the developers of those 00:13:03.299 --> 00:13:04.999 align:start position:0% dependencies if the developers of those EVM<00:13:03.720> packages<00:13:04.110> that<00:13:04.350> were<00:13:04.529> linking<00:13:04.860> to 00:13:04.999 --> 00:13:05.009 align:start position:0% EVM packages that were linking to 00:13:05.009 --> 00:13:07.819 align:start position:0% EVM packages that were linking to provide<00:13:05.369> new<00:13:05.670> versions<00:13:06.089> so<00:13:06.689> this<00:13:07.110> is<00:13:07.259> really 00:13:07.819 --> 00:13:07.829 align:start position:0% provide new versions so this is really 00:13:07.829 --> 00:13:12.019 align:start position:0% provide new versions so this is really good<00:13:07.920> and<00:13:09.079> let's<00:13:10.079> go<00:13:10.499> a<00:13:10.709> little<00:13:10.769> bit<00:13:11.029> further 00:13:12.019 --> 00:13:12.029 align:start position:0% good and let's go a little bit further 00:13:12.029 --> 00:13:14.809 align:start position:0% good and let's go a little bit further on<00:13:12.329> the<00:13:12.480> EVM<00:13:12.899> packages<00:13:13.350> thing<00:13:13.769> maybe<00:13:14.249> some<00:13:14.730> of 00:13:14.809 --> 00:13:14.819 align:start position:0% on the EVM packages thing maybe some of 00:13:14.819 --> 00:13:17.059 align:start position:0% on the EVM packages thing maybe some of you<00:13:14.939> may<00:13:15.089> be<00:13:15.120> wondering<00:13:15.470> how<00:13:16.470> we<00:13:16.529> can<00:13:16.740> actually 00:13:17.059 --> 00:13:17.069 align:start position:0% you may be wondering how we can actually 00:13:17.069 --> 00:13:19.650 align:start position:0% you may be wondering how we can actually make<00:13:17.399> sure<00:13:17.459> that<00:13:17.670> they<00:13:18.449> call<00:13:18.660> what<00:13:18.899> we're 00:13:19.650 --> 00:13:19.660 align:start position:0% make sure that they call what we're 00:13:19.660 --> 00:13:21.960 align:start position:0% make sure that they call what we're sharing<00:13:19.960> and<00:13:20.140> reusing<00:13:20.530> on<00:13:20.950> chain<00:13:21.400> directly<00:13:21.820> is 00:13:21.960 --> 00:13:21.970 align:start position:0% sharing and reusing on chain directly is 00:13:21.970 --> 00:13:24.210 align:start position:0% sharing and reusing on chain directly is actually<00:13:22.480> safe<00:13:22.720> we<00:13:23.290> can<00:13:23.440> trust<00:13:23.740> the<00:13:23.920> code<00:13:24.100> that 00:13:24.210 --> 00:13:24.220 align:start position:0% actually safe we can trust the code that 00:13:24.220 --> 00:13:28.110 align:start position:0% actually safe we can trust the code that is<00:13:24.340> already<00:13:24.700> deployed<00:13:24.880> on<00:13:25.240> chain<00:13:25.480> so<00:13:27.120> before 00:13:28.110 --> 00:13:28.120 align:start position:0% is already deployed on chain so before 00:13:28.120 --> 00:13:29.970 align:start position:0% is already deployed on chain so before we<00:13:28.240> answer<00:13:28.360> that<00:13:28.510> let's<00:13:28.990> think<00:13:29.350> how<00:13:29.710> we<00:13:29.770> should 00:13:29.970 --> 00:13:29.980 align:start position:0% we answer that let's think how we should 00:13:29.980 --> 00:13:33.630 align:start position:0% we answer that let's think how we should how<00:13:30.370> we<00:13:30.700> probably<00:13:31.000> do<00:13:31.240> this<00:13:31.420> these<00:13:32.050> days<00:13:32.640> we 00:13:33.630 --> 00:13:33.640 align:start position:0% how we probably do this these days we 00:13:33.640 --> 00:13:36.360 align:start position:0% how we probably do this these days we may<00:13:33.820> for<00:13:34.510> example<00:13:34.540> hire<00:13:35.020> an<00:13:35.350> auditor<00:13:35.800> in<00:13:36.190> order 00:13:36.360 --> 00:13:36.370 align:start position:0% may for example hire an auditor in order 00:13:36.370 --> 00:13:38.790 align:start position:0% may for example hire an auditor in order to<00:13:36.550> audit<00:13:36.970> that<00:13:37.120> code<00:13:37.540> that<00:13:37.720> was<00:13:38.020> deployed<00:13:38.590> and 00:13:38.790 --> 00:13:38.800 align:start position:0% to audit that code that was deployed and 00:13:38.800 --> 00:13:41.460 align:start position:0% to audit that code that was deployed and chain<00:13:39.010> and<00:13:39.240> the<00:13:40.240> auditor<00:13:40.510> may<00:13:40.750> raise<00:13:41.080> some 00:13:41.460 --> 00:13:41.470 align:start position:0% chain and the auditor may raise some 00:13:41.470 --> 00:13:44.430 align:start position:0% chain and the auditor may raise some findings<00:13:42.310> on<00:13:42.580> that<00:13:43.210> code<00:13:43.630> and<00:13:43.870> we<00:13:44.020> will<00:13:44.110> tell 00:13:44.430 --> 00:13:44.440 align:start position:0% findings on that code and we will tell 00:13:44.440 --> 00:13:46.440 align:start position:0% findings on that code and we will tell the<00:13:44.620> developer<00:13:45.400> team<00:13:45.580> to<00:13:45.790> you<00:13:45.880> know<00:13:46.030> to<00:13:46.210> fix 00:13:46.440 --> 00:13:46.450 align:start position:0% the developer team to you know to fix 00:13:46.450 --> 00:13:49.170 align:start position:0% the developer team to you know to fix those<00:13:46.660> those<00:13:47.080> backs<00:13:47.380> or<00:13:47.680> to<00:13:48.580> improve<00:13:48.820> that<00:13:49.000> the 00:13:49.170 --> 00:13:49.180 align:start position:0% those those backs or to improve that the 00:13:49.180 --> 00:13:50.870 align:start position:0% those those backs or to improve that the things<00:13:49.360> that<00:13:49.420> we<00:13:49.600> that<00:13:50.110> we<00:13:50.260> found<00:13:50.410> there<00:13:50.650> and 00:13:50.870 --> 00:13:50.880 align:start position:0% things that we that we found there and 00:13:50.880 --> 00:13:54.600 align:start position:0% things that we that we found there and it<00:13:51.880> will<00:13:52.000> be<00:13:52.120> kind<00:13:52.960> of<00:13:53.080> expensive<00:13:53.950> in<00:13:54.370> order<00:13:54.550> to 00:13:54.600 --> 00:13:54.610 align:start position:0% it will be kind of expensive in order to 00:13:54.610 --> 00:13:56.190 align:start position:0% it will be kind of expensive in order to hire<00:13:54.790> an<00:13:54.910> auditor<00:13:55.210> to<00:13:55.450> do<00:13:55.570> that<00:13:55.750> every<00:13:55.960> time<00:13:55.990> we 00:13:56.190 --> 00:13:56.200 align:start position:0% hire an auditor to do that every time we 00:13:56.200 --> 00:13:59.130 align:start position:0% hire an auditor to do that every time we want<00:13:56.380> to<00:13:56.410> use<00:13:56.500> a<00:13:56.800> new<00:13:56.920> dependency<00:13:57.310> and<00:13:58.140> that's 00:13:59.130 --> 00:13:59.140 align:start position:0% want to use a new dependency and that's 00:13:59.140 --> 00:14:00.900 align:start position:0% want to use a new dependency and that's why<00:13:59.320> we<00:13:59.470> decided<00:13:59.530> to<00:14:00.130> start<00:14:00.340> working<00:14:00.490> on<00:14:00.730> the 00:14:00.900 --> 00:14:00.910 align:start position:0% why we decided to start working on the 00:14:00.910 --> 00:14:02.780 align:start position:0% why we decided to start working on the on<00:14:01.090> the<00:14:01.240> bow<00:14:01.360> chain<00:14:01.540> system<00:14:01.900> of<00:14:02.080> supply<00:14:02.470> Noah's 00:14:02.780 --> 00:14:02.790 align:start position:0% on the bow chain system of supply Noah's 00:14:02.790 --> 00:14:05.400 align:start position:0% on the bow chain system of supply Noah's this<00:14:03.790> is<00:14:03.910> a<00:14:03.970> way<00:14:04.120> to<00:14:04.150> decentralize<00:14:04.840> that<00:14:05.200> those 00:14:05.400 --> 00:14:05.410 align:start position:0% this is a way to decentralize that those 00:14:05.410 --> 00:14:07.440 align:start position:0% this is a way to decentralize that those decisions<00:14:05.830> and<00:14:06.010> this<00:14:06.580> is<00:14:06.670> our<00:14:06.790> first<00:14:07.210> step 00:14:07.440 --> 00:14:07.450 align:start position:0% decisions and this is our first step 00:14:07.450 --> 00:14:09.570 align:start position:0% decisions and this is our first step towards<00:14:08.320> that<00:14:08.380> the<00:14:08.680> toka<00:14:08.950> mechanics<00:14:09.430> that 00:14:09.570 --> 00:14:09.580 align:start position:0% towards that the toka mechanics that 00:14:09.580 --> 00:14:11.370 align:start position:0% towards that the toka mechanics that we've<00:14:09.700> been<00:14:09.820> announcing<00:14:10.240> things<00:14:10.570> since<00:14:11.230> we 00:14:11.370 --> 00:14:11.380 align:start position:0% we've been announcing things since we 00:14:11.380 --> 00:14:14.640 align:start position:0% we've been announcing things since we start<00:14:11.590> this<00:14:11.680> project<00:14:13.440> the<00:14:14.440> first 00:14:14.640 --> 00:14:14.650 align:start position:0% start this project the first 00:14:14.650 --> 00:14:16.320 align:start position:0% start this project the first implementation<00:14:14.920> of<00:14:15.370> the<00:14:15.550> of<00:14:15.700> the<00:14:15.970> bouchy 00:14:16.320 --> 00:14:16.330 align:start position:0% implementation of the of the bouchy 00:14:16.330 --> 00:14:18.960 align:start position:0% implementation of the of the bouchy system<00:14:17.040> we're<00:14:18.040> happy<00:14:18.340> to<00:14:18.430> announce<00:14:18.490> that<00:14:18.730> it's 00:14:18.960 --> 00:14:18.970 align:start position:0% system we're happy to announce that it's 00:14:18.970 --> 00:14:20.550 align:start position:0% system we're happy to announce that it's already<00:14:19.240> included<00:14:19.450> in<00:14:19.810> the<00:14:19.990> in<00:14:20.110> the<00:14:20.260> second 00:14:20.550 --> 00:14:20.560 align:start position:0% already included in the in the second 00:14:20.560 --> 00:14:24.270 align:start position:0% already included in the in the second version<00:14:20.710> of<00:14:20.950> WS<00:14:21.550> we<00:14:21.790> launched<00:14:22.470> this<00:14:23.470> week<00:14:23.740> so 00:14:24.270 --> 00:14:24.280 align:start position:0% version of WS we launched this week so 00:14:24.280 --> 00:14:28.710 align:start position:0% version of WS we launched this week so let's<00:14:24.640> see<00:14:25.710> what<00:14:26.710> we<00:14:27.370> have<00:14:27.490> what<00:14:28.420> do<00:14:28.480> we<00:14:28.570> have 00:14:28.710 --> 00:14:28.720 align:start position:0% let's see what we have what do we have 00:14:28.720 --> 00:14:31.560 align:start position:0% let's see what we have what do we have to<00:14:28.840> say<00:14:28.990> about<00:14:29.080> the<00:14:29.290> about<00:14:29.830> this<00:14:30.450> so<00:14:31.450> the 00:14:31.560 --> 00:14:31.570 align:start position:0% to say about the about this so the 00:14:31.570 --> 00:14:33.180 align:start position:0% to say about the about this so the budget<00:14:31.720> budgeting<00:14:32.260> system<00:14:32.380> basically<00:14:32.860> allows 00:14:33.180 --> 00:14:33.190 align:start position:0% budget budgeting system basically allows 00:14:33.190 --> 00:14:36.300 align:start position:0% budget budgeting system basically allows users<00:14:33.880> to<00:14:34.090> back<00:14:34.450> the<00:14:34.990> quality<00:14:35.200> of<00:14:35.530> an<00:14:35.950> EVM 00:14:36.300 --> 00:14:36.310 align:start position:0% users to back the quality of an EVM 00:14:36.310 --> 00:14:37.860 align:start position:0% users to back the quality of an EVM package<00:14:36.700> that<00:14:36.880> is<00:14:37.000> already<00:14:37.270> deployed<00:14:37.630> a 00:14:37.860 --> 00:14:37.870 align:start position:0% package that is already deployed a 00:14:37.870 --> 00:14:39.510 align:start position:0% package that is already deployed a second<00:14:38.470> as<00:14:38.650> you<00:14:38.740> can<00:14:38.860> see<00:14:39.040> this<00:14:39.190> is<00:14:39.340> something 00:14:39.510 --> 00:14:39.520 align:start position:0% second as you can see this is something 00:14:39.520 --> 00:14:41.160 align:start position:0% second as you can see this is something complementary<00:14:40.180> to<00:14:40.360> the<00:14:40.480> Union<00:14:40.750> package<00:14:41.050> this 00:14:41.160 --> 00:14:41.170 align:start position:0% complementary to the Union package this 00:14:41.170 --> 00:14:43.050 align:start position:0% complementary to the Union package this thing<00:14:41.500> it<00:14:41.770> doesn't<00:14:41.980> mean<00:14:42.190> that<00:14:42.220> you<00:14:42.610> need<00:14:42.850> to 00:14:43.050 --> 00:14:43.060 align:start position:0% thing it doesn't mean that you need to 00:14:43.060 --> 00:14:45.420 align:start position:0% thing it doesn't mean that you need to use<00:14:44.020> the<00:14:44.170> voting<00:14:44.470> system<00:14:44.740> in<00:14:44.860> order<00:14:45.070> to<00:14:45.190> create 00:14:45.420 --> 00:14:45.430 align:start position:0% use the voting system in order to create 00:14:45.430 --> 00:14:47.670 align:start position:0% use the voting system in order to create an<00:14:46.060> EVM<00:14:46.390> package<00:14:46.660> but<00:14:46.900> this<00:14:47.020> is<00:14:47.110> the<00:14:47.230> way<00:14:47.410> that 00:14:47.670 --> 00:14:47.680 align:start position:0% an EVM package but this is the way that 00:14:47.680 --> 00:14:49.680 align:start position:0% an EVM package but this is the way that this<00:14:48.100> is<00:14:48.250> the<00:14:48.310> way<00:14:48.430> that<00:14:48.550> you<00:14:48.670> can<00:14:48.820> use<00:14:49.480> in 00:14:49.680 --> 00:14:49.690 align:start position:0% this is the way that you can use in 00:14:49.690 --> 00:14:51.720 align:start position:0% this is the way that you can use in order<00:14:49.780> to<00:14:49.930> sign<00:14:50.230> saying<00:14:50.740> all<00:14:50.860> your<00:14:51.100> the 00:14:51.720 --> 00:14:51.730 align:start position:0% order to sign saying all your the 00:14:51.730 --> 00:14:53.310 align:start position:0% order to sign saying all your the security<00:14:52.240> of<00:14:52.270> an<00:14:52.480> EVM<00:14:52.780> package<00:14:53.050> that<00:14:53.230> is 00:14:53.310 --> 00:14:53.320 align:start position:0% security of an EVM package that is 00:14:53.320 --> 00:14:55.560 align:start position:0% security of an EVM package that is already<00:14:53.620> deployed<00:14:53.880> as<00:14:54.880> you<00:14:55.060> can<00:14:55.180> see<00:14:55.300> this<00:14:55.420> is 00:14:55.560 --> 00:14:55.570 align:start position:0% already deployed as you can see this is 00:14:55.570 --> 00:14:58.980 align:start position:0% already deployed as you can see this is our<00:14:55.840> first<00:14:56.230> step<00:14:56.860> towards<00:14:57.400> I<00:14:57.820> create<00:14:58.330> a<00:14:58.480> great 00:14:58.980 --> 00:14:58.990 align:start position:0% our first step towards I create a great 00:14:58.990 --> 00:15:03.450 align:start position:0% our first step towards I create a great list<00:14:59.320> of<00:14:59.470> secure<00:15:00.250> EVM<00:15:00.760> packages<00:15:01.240> and<00:15:02.460> let's 00:15:03.450 --> 00:15:03.460 align:start position:0% list of secure EVM packages and let's 00:15:03.460 --> 00:15:05.160 align:start position:0% list of secure EVM packages and let's see<00:15:03.610> a<00:15:03.640> quick<00:15:03.850> sample<00:15:04.450> of<00:15:04.510> the<00:15:04.780> things<00:15:04.960> that<00:15:05.080> we 00:15:05.160 --> 00:15:05.170 align:start position:0% see a quick sample of the things that we 00:15:05.170 --> 00:15:07.260 align:start position:0% see a quick sample of the things that we can<00:15:05.320> do<00:15:05.410> with<00:15:05.560> the<00:15:05.890> bouton<00:15:06.310> system<00:15:06.760> for 00:15:07.260 --> 00:15:07.270 align:start position:0% can do with the bouton system for 00:15:07.270 --> 00:15:10.110 align:start position:0% can do with the bouton system for example<00:15:07.650> racing<00:15:08.650> here<00:15:08.830> a<00:15:08.860> way<00:15:09.160> to<00:15:09.190> register<00:15:09.910> a 00:15:10.110 --> 00:15:10.120 align:start position:0% example racing here a way to register a 00:15:10.120 --> 00:15:12.600 align:start position:0% example racing here a way to register a new<00:15:10.270> EVM<00:15:10.930> package<00:15:11.260> on<00:15:11.470> the<00:15:11.680> bouton<00:15:11.950> system<00:15:12.430> of 00:15:12.600 --> 00:15:12.610 align:start position:0% new EVM package on the bouton system of 00:15:12.610 --> 00:15:15.330 align:start position:0% new EVM package on the bouton system of suppling<00:15:13.030> us<00:15:13.270> it's<00:15:13.810> pretty<00:15:14.470> much<00:15:14.620> very<00:15:15.040> simple 00:15:15.330 --> 00:15:15.340 align:start position:0% suppling us it's pretty much very simple 00:15:15.340 --> 00:15:18.330 align:start position:0% suppling us it's pretty much very simple you<00:15:15.880> just<00:15:15.940> need<00:15:16.240> to<00:15:16.480> pass<00:15:16.750> the<00:15:16.900> the<00:15:17.140> the<00:15:17.830> name 00:15:18.330 --> 00:15:18.340 align:start position:0% you just need to pass the the the name 00:15:18.340 --> 00:15:20.610 align:start position:0% you just need to pass the the the name of<00:15:18.550> your<00:15:18.700> EVM<00:15:19.480> package<00:15:19.780> and<00:15:20.020> the<00:15:20.110> others<00:15:20.350> where 00:15:20.610 --> 00:15:20.620 align:start position:0% of your EVM package and the others where 00:15:20.620 --> 00:15:22.170 align:start position:0% of your EVM package and the others where it's<00:15:20.740> deployed<00:15:21.070> and<00:15:21.370> will<00:15:21.580> be<00:15:21.700> a<00:15:21.730> simple<00:15:22.090> as 00:15:22.170 --> 00:15:22.180 align:start position:0% it's deployed and will be a simple as 00:15:22.180 --> 00:15:25.170 align:start position:0% it's deployed and will be a simple as that<00:15:22.330> and<00:15:23.010> of<00:15:24.010> course<00:15:24.070> that<00:15:24.580> you<00:15:24.610> can<00:15:24.880> also 00:15:25.170 --> 00:15:25.180 align:start position:0% that and of course that you can also 00:15:25.180 --> 00:15:28.530 align:start position:0% that and of course that you can also start<00:15:25.810> voting<00:15:26.050> some<00:15:26.890> amounts<00:15:27.280> for<00:15:27.540> EVM 00:15:28.530 --> 00:15:28.540 align:start position:0% start voting some amounts for EVM 00:15:28.540 --> 00:15:30.690 align:start position:0% start voting some amounts for EVM packages<00:15:28.960> that<00:15:29.080> are<00:15:29.230> already<00:15:29.520> registered<00:15:30.520> in 00:15:30.690 --> 00:15:30.700 align:start position:0% packages that are already registered in 00:15:30.700 --> 00:15:32.740 align:start position:0% packages that are already registered in the<00:15:30.940> in<00:15:31.150> the<00:15:31.390> bouton<00:15:31.570> system 00:15:32.740 --> 00:15:32.750 align:start position:0% the in the bouton system 00:15:32.750 --> 00:15:34.780 align:start position:0% the in the bouton system and<00:15:32.870> the<00:15:33.710> amounts<00:15:33.980> that<00:15:34.130> we<00:15:34.340> were<00:15:34.400> about<00:15:34.580> in 00:15:34.780 --> 00:15:34.790 align:start position:0% and the amounts that we were about in 00:15:34.790 --> 00:15:36.700 align:start position:0% and the amounts that we were about in here<00:15:35.030> are<00:15:35.240> not<00:15:35.420> just<00:15:35.660> numbers<00:15:35.810> and<00:15:36.290> this<00:15:36.560> is 00:15:36.700 --> 00:15:36.710 align:start position:0% here are not just numbers and this is 00:15:36.710 --> 00:15:39.910 align:start position:0% here are not just numbers and this is where<00:15:37.130> the<00:15:37.280> sub<00:15:37.520> talking<00:15:37.910> is<00:15:38.000> born<00:15:38.740> the<00:15:39.740> sub 00:15:39.910 --> 00:15:39.920 align:start position:0% where the sub talking is born the sub 00:15:39.920 --> 00:15:41.470 align:start position:0% where the sub talking is born the sub talking<00:15:40.190> is<00:15:40.280> the<00:15:40.430> native<00:15:40.880> talking<00:15:41.240> of<00:15:41.330> the 00:15:41.470 --> 00:15:41.480 align:start position:0% talking is the native talking of the 00:15:41.480 --> 00:15:43.510 align:start position:0% talking is the native talking of the bouton<00:15:41.660> system<00:15:42.200> and<00:15:42.380> it's<00:15:42.800> basically<00:15:43.310> what 00:15:43.510 --> 00:15:43.520 align:start position:0% bouton system and it's basically what 00:15:43.520 --> 00:15:45.940 align:start position:0% bouton system and it's basically what allows<00:15:43.790> us<00:15:43.820> to<00:15:44.270> align<00:15:44.870> the<00:15:45.110> incentives<00:15:45.350> in 00:15:45.940 --> 00:15:45.950 align:start position:0% allows us to align the incentives in 00:15:45.950 --> 00:15:48.490 align:start position:0% allows us to align the incentives in order<00:15:46.100> to<00:15:46.220> create<00:15:46.460> a<00:15:46.780> healthy<00:15:47.780> ecosystem<00:15:47.870> of 00:15:48.490 --> 00:15:48.500 align:start position:0% order to create a healthy ecosystem of 00:15:48.500 --> 00:15:50.680 align:start position:0% order to create a healthy ecosystem of Sakura<00:15:48.950> smart<00:15:49.250> contracts<00:15:49.640> projects<00:15:50.120> and<00:15:50.420> it 00:15:50.680 --> 00:15:50.690 align:start position:0% Sakura smart contracts projects and it 00:15:50.690 --> 00:15:53.230 align:start position:0% Sakura smart contracts projects and it was<00:15:50.920> also<00:15:51.920> lunch<00:15:52.340> with<00:15:52.580> the<00:15:52.730> second<00:15:53.090> version 00:15:53.230 --> 00:15:53.240 align:start position:0% was also lunch with the second version 00:15:53.240 --> 00:15:55.870 align:start position:0% was also lunch with the second version of<00:15:53.540> Subway<00:15:53.900> Noah's<00:15:54.260> along<00:15:54.950> with<00:15:55.100> with<00:15:55.790> the 00:15:55.870 --> 00:15:55.880 align:start position:0% of Subway Noah's along with with the 00:15:55.880 --> 00:16:01.330 align:start position:0% of Subway Noah's along with with the bouton<00:15:56.090> system<00:15:56.630> and<00:15:59.590> one<00:16:00.590> more<00:16:00.710> thing<00:16:00.860> we're 00:16:01.330 --> 00:16:01.340 align:start position:0% bouton system and one more thing we're 00:16:01.340 --> 00:16:02.710 align:start position:0% bouton system and one more thing we're not<00:16:01.490> alone<00:16:01.730> there's<00:16:02.000> a<00:16:02.090> lot<00:16:02.240> of<00:16:02.360> amazing 00:16:02.710 --> 00:16:02.720 align:start position:0% not alone there's a lot of amazing 00:16:02.720 --> 00:16:04.540 align:start position:0% not alone there's a lot of amazing projects<00:16:03.350> that<00:16:03.500> already<00:16:03.620> decided<00:16:04.190> to<00:16:04.280> start 00:16:04.540 --> 00:16:04.550 align:start position:0% projects that already decided to start 00:16:04.550 --> 00:16:07.660 align:start position:0% projects that already decided to start building<00:16:04.670> their<00:16:04.970> own<00:16:05.060> EVM<00:16:05.930> packages<00:16:06.440> and<00:16:06.670> many 00:16:07.660 --> 00:16:07.670 align:start position:0% building their own EVM packages and many 00:16:07.670 --> 00:16:10.450 align:start position:0% building their own EVM packages and many of<00:16:07.790> them<00:16:08.000> are<00:16:08.210> already<00:16:08.440> on<00:16:09.440> chain<00:16:09.890> they're 00:16:10.450 --> 00:16:10.460 align:start position:0% of them are already on chain they're 00:16:10.460 --> 00:16:12.310 align:start position:0% of them are already on chain they're already<00:16:10.760> on<00:16:10.910> the<00:16:11.210> minute<00:16:11.540> so<00:16:11.750> you<00:16:11.810> can<00:16:12.050> start 00:16:12.310 --> 00:16:12.320 align:start position:0% already on the minute so you can start 00:16:12.320 --> 00:16:14.230 align:start position:0% already on the minute so you can start reducing<00:16:12.470> their<00:16:12.860> code<00:16:13.130> in<00:16:13.400> your<00:16:13.460> own<00:16:13.730> projects 00:16:14.230 --> 00:16:14.240 align:start position:0% reducing their code in your own projects 00:16:14.240 --> 00:16:17.950 align:start position:0% reducing their code in your own projects through<00:16:15.080> sibling<00:16:15.500> OS<00:16:15.800> and<00:16:16.150> you<00:16:17.150> can<00:16:17.330> be<00:16:17.450> one<00:16:17.840> of 00:16:17.950 --> 00:16:17.960 align:start position:0% through sibling OS and you can be one of 00:16:17.960 --> 00:16:20.080 align:start position:0% through sibling OS and you can be one of them<00:16:18.110> too<00:16:18.290> so<00:16:18.620> that's<00:16:19.280> why<00:16:19.430> we<00:16:19.610> decided<00:16:19.970> to 00:16:20.080 --> 00:16:20.090 align:start position:0% them too so that's why we decided to 00:16:20.090 --> 00:16:22.300 align:start position:0% them too so that's why we decided to start<00:16:20.420> a<00:16:20.540> private<00:16:20.960> beta<00:16:21.140> period<00:16:21.470> this<00:16:21.950> is<00:16:22.100> a 00:16:22.300 --> 00:16:22.310 align:start position:0% start a private beta period this is a 00:16:22.310 --> 00:16:25.720 align:start position:0% start a private beta period this is a way<00:16:22.880> to<00:16:23.140> that<00:16:24.140> we<00:16:24.260> say<00:16:24.500> together<00:16:25.040> and<00:16:25.400> a<00:16:25.490> small 00:16:25.720 --> 00:16:25.730 align:start position:0% way to that we say together and a small 00:16:25.730 --> 00:16:27.400 align:start position:0% way to that we say together and a small group<00:16:25.910> of<00:16:26.000> people<00:16:26.180> in<00:16:26.480> order<00:16:26.570> to<00:16:26.720> validate<00:16:26.930> all 00:16:27.400 --> 00:16:27.410 align:start position:0% group of people in order to validate all 00:16:27.410 --> 00:16:29.730 align:start position:0% group of people in order to validate all these<00:16:27.590> ideas<00:16:28.010> and<00:16:28.190> all<00:16:29.120> the<00:16:29.180> partners<00:16:29.540> that 00:16:29.730 --> 00:16:29.740 align:start position:0% these ideas and all the partners that 00:16:29.740 --> 00:16:31.690 align:start position:0% these ideas and all the partners that all<00:16:30.740> the<00:16:30.830> projects<00:16:31.160> that<00:16:31.190> I<00:16:31.280> mentioned<00:16:31.340> before 00:16:31.690 --> 00:16:31.700 align:start position:0% all the projects that I mentioned before 00:16:31.700 --> 00:16:33.970 align:start position:0% all the projects that I mentioned before I<00:16:31.910> going<00:16:32.180> to<00:16:32.300> receive<00:16:32.990> some<00:16:33.230> cept<00:16:33.470> organs<00:16:33.830> in 00:16:33.970 --> 00:16:33.980 align:start position:0% I going to receive some cept organs in 00:16:33.980 --> 00:16:36.100 align:start position:0% I going to receive some cept organs in order<00:16:34.160> to<00:16:34.280> start<00:16:34.580> testing<00:16:35.060> the<00:16:35.420> bouton<00:16:35.600> system 00:16:36.100 --> 00:16:36.110 align:start position:0% order to start testing the bouton system 00:16:36.110 --> 00:16:38.740 align:start position:0% order to start testing the bouton system and<00:16:36.350> you<00:16:36.740> can<00:16:36.890> be<00:16:37.010> one<00:16:37.339> of<00:16:37.400> them<00:16:37.640> too 00:16:38.740 --> 00:16:38.750 align:start position:0% and you can be one of them too 00:16:38.750 --> 00:16:45.700 align:start position:0% and you can be one of them too oh<00:16:40.030> just<00:16:41.030> a<00:16:41.530> quick<00:16:43.600> clarification<00:16:44.600> here<00:16:45.170> this 00:16:45.700 --> 00:16:45.710 align:start position:0% oh just a quick clarification here this 00:16:45.710 --> 00:16:47.980 align:start position:0% oh just a quick clarification here this doesn't<00:16:46.040> mean<00:16:46.100> that<00:16:46.160> WMS<00:16:46.760> is<00:16:46.790> not<00:16:47.120> available 00:16:47.980 --> 00:16:47.990 align:start position:0% doesn't mean that WMS is not available 00:16:47.990 --> 00:16:49.420 align:start position:0% doesn't mean that WMS is not available for<00:16:48.050> everyone<00:16:48.410> seven<00:16:48.830> years<00:16:48.980> as<00:16:49.100> I<00:16:49.220> said 00:16:49.420 --> 00:16:49.430 align:start position:0% for everyone seven years as I said 00:16:49.430 --> 00:16:51.640 align:start position:0% for everyone seven years as I said before<00:16:49.550> it's<00:16:49.880> open<00:16:50.150> source<00:16:50.360> and<00:16:50.540> you<00:16:50.600> can<00:16:50.810> use 00:16:51.640 --> 00:16:51.650 align:start position:0% before it's open source and you can use 00:16:51.650 --> 00:16:53.650 align:start position:0% before it's open source and you can use it<00:16:51.830> right<00:16:51.860> now<00:16:52.160> if<00:16:52.310> you<00:16:52.430> want<00:16:52.610> just<00:16:53.180> it<00:16:53.330> does<00:16:53.450> it 00:16:53.650 --> 00:16:53.660 align:start position:0% it right now if you want just it does it 00:16:53.660 --> 00:16:55.000 align:start position:0% it right now if you want just it does it does<00:16:53.810> means<00:16:53.990> that<00:16:54.140> the<00:16:54.260> beta<00:16:54.530> participants 00:16:55.000 --> 00:16:55.010 align:start position:0% does means that the beta participants 00:16:55.010 --> 00:16:56.800 align:start position:0% does means that the beta participants are<00:16:55.250> the<00:16:55.370> only<00:16:55.520> ones<00:16:56.030> that<00:16:56.330> are<00:16:56.360> going<00:16:56.480> to<00:16:56.720> be 00:16:56.800 --> 00:16:56.810 align:start position:0% are the only ones that are going to be 00:16:56.810 --> 00:16:58.530 align:start position:0% are the only ones that are going to be allowed<00:16:56.990> to<00:16:57.050> start<00:16:57.680> testing<00:16:58.100> the<00:16:58.220> bouton 00:16:58.530 --> 00:16:58.540 align:start position:0% allowed to start testing the bouton 00:16:58.540 --> 00:17:00.610 align:start position:0% allowed to start testing the bouton system<00:16:59.540> those<00:16:59.810> are<00:16:59.839> the<00:17:00.080> ones<00:17:00.260> that<00:17:00.350> will 00:17:00.610 --> 00:17:00.620 align:start position:0% system those are the ones that will 00:17:00.620 --> 00:17:02.950 align:start position:0% system those are the ones that will receive<00:17:01.040> some<00:17:01.700> SAP<00:17:02.000> tokens<00:17:02.420> that<00:17:02.510> the<00:17:02.810> ones 00:17:02.950 --> 00:17:02.960 align:start position:0% receive some SAP tokens that the ones 00:17:02.960 --> 00:17:05.500 align:start position:0% receive some SAP tokens that the ones that<00:17:03.020> can<00:17:03.620> start<00:17:04.010> watching<00:17:04.280> for<00:17:05.030> some<00:17:05.150> EVM 00:17:05.500 --> 00:17:05.510 align:start position:0% that can start watching for some EVM 00:17:05.510 --> 00:17:07.510 align:start position:0% that can start watching for some EVM packages<00:17:05.900> that<00:17:06.020> are<00:17:06.110> already<00:17:06.280> deployed<00:17:07.280> the 00:17:07.510 --> 00:17:07.520 align:start position:0% packages that are already deployed the 00:17:07.520 --> 00:17:09.040 align:start position:0% packages that are already deployed the ones<00:17:07.670> that<00:17:07.880> will<00:17:08.120> be<00:17:08.150> allowed<00:17:08.630> to<00:17:08.660> register 00:17:09.040 --> 00:17:09.050 align:start position:0% ones that will be allowed to register 00:17:09.050 --> 00:17:11.829 align:start position:0% ones that will be allowed to register EVM<00:17:09.740> packages<00:17:10.100> on<00:17:10.280> our<00:17:10.430> patent<00:17:10.819> system<00:17:10.970> and<00:17:11.390> so 00:17:11.829 --> 00:17:11.839 align:start position:0% EVM packages on our patent system and so 00:17:11.839 --> 00:17:16.210 align:start position:0% EVM packages on our patent system and so on<00:17:12.020> and<00:17:13.270> you<00:17:14.270> can<00:17:14.990> follow<00:17:15.290> this<00:17:15.470> link<00:17:15.530> where 00:17:16.210 --> 00:17:16.220 align:start position:0% on and you can follow this link where 00:17:16.220 --> 00:17:18.550 align:start position:0% on and you can follow this link where you<00:17:16.400> will<00:17:16.579> find<00:17:16.730> a<00:17:16.910> registration<00:17:17.240> form<00:17:17.959> in 00:17:18.550 --> 00:17:18.560 align:start position:0% you will find a registration form in 00:17:18.560 --> 00:17:20.380 align:start position:0% you will find a registration form in order<00:17:18.709> to<00:17:18.890> sign<00:17:19.100> up<00:17:19.280> for<00:17:19.310> for<00:17:19.760> the<00:17:19.880> for<00:17:20.270> the 00:17:20.380 --> 00:17:20.390 align:start position:0% order to sign up for for the for the 00:17:20.390 --> 00:17:22.960 align:start position:0% order to sign up for for the for the beta<00:17:20.569> period<00:17:20.810> as<00:17:21.500> I<00:17:21.680> said<00:17:21.829> before<00:17:21.949> it's<00:17:22.610> open 00:17:22.960 --> 00:17:22.970 align:start position:0% beta period as I said before it's open 00:17:22.970 --> 00:17:25.990 align:start position:0% beta period as I said before it's open for<00:17:23.120> everyone<00:17:23.360> so<00:17:23.839> feel<00:17:24.079> free<00:17:24.110> to<00:17:24.760> apply<00:17:25.760> and 00:17:25.990 --> 00:17:26.000 align:start position:0% for everyone so feel free to apply and 00:17:26.000 --> 00:17:28.630 align:start position:0% for everyone so feel free to apply and we<00:17:26.900> hope<00:17:27.079> you<00:17:27.199> do<00:17:27.350> and 00:17:28.630 --> 00:17:28.640 align:start position:0% we hope you do and 00:17:28.640 --> 00:17:31.300 align:start position:0% we hope you do and the<00:17:29.000> registration<00:17:29.750> is<00:17:29.840> finishing<00:17:30.620> by<00:17:30.830> mid 00:17:31.300 --> 00:17:31.310 align:start position:0% the registration is finishing by mid 00:17:31.310 --> 00:17:34.500 align:start position:0% the registration is finishing by mid November<00:17:31.460> so<00:17:32.090> please<00:17:32.840> come<00:17:33.110> and<00:17:33.140> join<00:17:33.290> us<00:17:33.590> and 00:17:34.500 --> 00:17:34.510 align:start position:0% November so please come and join us and 00:17:34.510 --> 00:17:40.030 align:start position:0% November so please come and join us and thank<00:17:35.510> you<00:17:35.600> so<00:17:35.750> much<00:17:35.900> guys<00:17:36.080> for<00:17:36.140> Hugh<00:17:36.710> me<00:17:36.860> today 00:17:40.030 --> 00:17:40.040 align:start position:0% 00:17:40.040 --> 00:17:48.790 align:start position:0% you 00:17:48.790 --> 00:17:48.800 align:start position:0% 00:17:48.800 --> 00:17:50.860 align:start position:0% you