WEBVTT Kind: captions Language: en 00:00:16.900 --> 00:00:20.410 align:start position:0% next<00:00:17.900> person<00:00:18.110> up<00:00:18.410> is<00:00:18.650> John 00:00:20.410 --> 00:00:20.420 align:start position:0% next person up is John 00:00:20.420 --> 00:00:25.410 align:start position:0% next person up is John he<00:00:20.870> is<00:00:20.990> going<00:00:21.260> to<00:00:21.380> speak<00:00:21.650> on<00:00:21.860> a<00:00:22.340> cerium<00:00:22.850> on<00:00:23.150> Ruby 00:00:25.410 --> 00:00:25.420 align:start position:0% he is going to speak on a cerium on Ruby 00:00:25.420 --> 00:00:42.040 align:start position:0% he is going to speak on a cerium on Ruby welcome<00:00:26.420> Jan<00:00:27.640> thank<00:00:28.640> you<00:00:39.610> so<00:00:40.610> thank<00:00:40.940> you<00:00:41.450> for 00:00:42.040 --> 00:00:42.050 align:start position:0% welcome Jan thank you so thank you for 00:00:42.050 --> 00:00:45.370 align:start position:0% welcome Jan thank you so thank you for coming<00:00:42.380> to<00:00:42.500> this<00:00:42.680> talk<00:00:42.920> and<00:00:44.079> it's<00:00:45.079> time<00:00:45.350> for 00:00:45.370 --> 00:00:45.380 align:start position:0% coming to this talk and it's time for 00:00:45.380 --> 00:00:48.550 align:start position:0% coming to this talk and it's time for some<00:00:45.649> simple<00:00:46.460> stuff<00:00:46.670> I<00:00:46.910> think<00:00:47.180> I<00:00:47.360> believe<00:00:48.230> the 00:00:48.550 --> 00:00:48.560 align:start position:0% some simple stuff I think I believe the 00:00:48.560 --> 00:00:51.640 align:start position:0% some simple stuff I think I believe the organizer<00:00:49.340> arranged<00:00:50.180> me<00:00:50.420> after<00:00:50.870> blood<00:00:51.260> for 00:00:51.640 --> 00:00:51.650 align:start position:0% organizer arranged me after blood for 00:00:51.650 --> 00:00:56.890 align:start position:0% organizer arranged me after blood for some<00:00:51.980> reason<00:00:53.740> so<00:00:54.740> yeah<00:00:55.030> okay<00:00:56.030> in<00:00:56.210> in<00:00:56.600> the<00:00:56.750> next 00:00:56.890 --> 00:00:56.900 align:start position:0% some reason so yeah okay in in the next 00:00:56.900 --> 00:00:59.410 align:start position:0% some reason so yeah okay in in the next in<00:00:57.410> the<00:00:57.530> next<00:00:57.590> 15<00:00:58.160> minutes<00:00:58.190> I<00:00:58.730> will<00:00:59.030> introduce 00:00:59.410 --> 00:00:59.420 align:start position:0% in the next 15 minutes I will introduce 00:00:59.420 --> 00:01:01.660 align:start position:0% in the next 15 minutes I will introduce you<00:00:59.780> to<00:00:59.840> his<00:01:00.050> sermon<00:01:00.500> Ruby<00:01:00.860> which<00:01:01.310> is<00:01:01.490> the 00:01:01.660 --> 00:01:01.670 align:start position:0% you to his sermon Ruby which is the 00:01:01.670 --> 00:01:03.820 align:start position:0% you to his sermon Ruby which is the intersection<00:01:02.180> of<00:01:02.540> his<00:01:02.780> serum<00:01:03.110> community<00:01:03.650> and 00:01:03.820 --> 00:01:03.830 align:start position:0% intersection of his serum community and 00:01:03.830 --> 00:01:11.890 align:start position:0% intersection of his serum community and Ruby<00:01:04.159> community<00:01:10.060> before<00:01:11.060> that<00:01:11.360> a<00:01:11.390> little<00:01:11.780> bit 00:01:11.890 --> 00:01:11.900 align:start position:0% Ruby community before that a little bit 00:01:11.900 --> 00:01:15.060 align:start position:0% Ruby community before that a little bit about<00:01:12.170> myself<00:01:12.670> my<00:01:13.670> name<00:01:13.880> is<00:01:14.060> Shahenshah<00:01:14.479> and 00:01:15.060 --> 00:01:15.070 align:start position:0% about myself my name is Shahenshah and 00:01:15.070 --> 00:01:19.420 align:start position:0% about myself my name is Shahenshah and I'm<00:01:16.070> a<00:01:16.130> serum<00:01:17.000> developer<00:01:17.570> I<00:01:17.980> in<00:01:18.980> last<00:01:19.190> year<00:01:19.400> I 00:01:19.420 --> 00:01:19.430 align:start position:0% I'm a serum developer I in last year I 00:01:19.430 --> 00:01:22.570 align:start position:0% I'm a serum developer I in last year I created<00:01:19.520> the<00:01:20.510> Ruby<00:01:21.050> certain<00:01:21.560> project<00:01:22.070> which 00:01:22.570 --> 00:01:22.580 align:start position:0% created the Ruby certain project which 00:01:22.580 --> 00:01:25.870 align:start position:0% created the Ruby certain project which is<00:01:22.790> a<00:01:22.820> full<00:01:23.420> implementation<00:01:24.230> of<00:01:24.830> cerium<00:01:25.490> in 00:01:25.870 --> 00:01:25.880 align:start position:0% is a full implementation of cerium in 00:01:25.880 --> 00:01:28.780 align:start position:0% is a full implementation of cerium in Ruby<00:01:26.210> and<00:01:26.450> I'm<00:01:26.690> also<00:01:26.900> working<00:01:27.230> on<00:01:27.440> pi<00:01:28.280> serum 00:01:28.780 --> 00:01:28.790 align:start position:0% Ruby and I'm also working on pi serum 00:01:28.790 --> 00:01:32.170 align:start position:0% Ruby and I'm also working on pi serum and<00:01:29.620> I'm<00:01:30.620> running<00:01:30.860> a<00:01:31.159> blockchain<00:01:31.430> technology 00:01:32.170 --> 00:01:32.180 align:start position:0% and I'm running a blockchain technology 00:01:32.180 --> 00:01:35.050 align:start position:0% and I'm running a blockchain technology startup<00:01:32.659> named<00:01:33.440> tape<00:01:33.650> and<00:01:33.890> we<00:01:34.400> we<00:01:34.970> are 00:01:35.050 --> 00:01:35.060 align:start position:0% startup named tape and we we are 00:01:35.060 --> 00:01:37.240 align:start position:0% startup named tape and we we are building<00:01:35.390> underlying<00:01:36.290> permission<00:01:37.040> ledger 00:01:37.240 --> 00:01:37.250 align:start position:0% building underlying permission ledger 00:01:37.250 --> 00:01:39.850 align:start position:0% building underlying permission ledger and<00:01:37.610> we<00:01:37.909> also<00:01:38.210> providing<00:01:38.930> some<00:01:39.110> consultancies 00:01:39.850 --> 00:01:39.860 align:start position:0% and we also providing some consultancies 00:01:39.860 --> 00:01:43.630 align:start position:0% and we also providing some consultancies to<00:01:40.070> our<00:01:40.190> customers<00:01:40.700> and<00:01:41.110> during<00:01:42.110> our<00:01:42.640> daily 00:01:43.630 --> 00:01:43.640 align:start position:0% to our customers and during our daily 00:01:43.640 --> 00:01:49.570 align:start position:0% to our customers and during our daily job<00:01:44.440> we<00:01:45.440> build<00:01:46.960> some<00:01:47.960> tools<00:01:48.350> to<00:01:48.620> help<00:01:49.190> me 00:01:49.570 --> 00:01:49.580 align:start position:0% job we build some tools to help me 00:01:49.580 --> 00:01:53.830 align:start position:0% job we build some tools to help me develop<00:01:50.030> taps<00:01:50.860> okay<00:01:51.860> so<00:01:52.040> a<00:01:52.490> little<00:01:53.479> bit<00:01:53.600> about 00:01:53.830 --> 00:01:53.840 align:start position:0% develop taps okay so a little bit about 00:01:53.840 --> 00:01:57.160 align:start position:0% develop taps okay so a little bit about Ruby<00:01:54.170> Ruby<00:01:54.799> is<00:01:54.950> a<00:01:55.310> language<00:01:55.840> created<00:01:56.840> by<00:01:56.990> a 00:01:57.160 --> 00:01:57.170 align:start position:0% Ruby Ruby is a language created by a 00:01:57.170 --> 00:02:01.030 align:start position:0% Ruby Ruby is a language created by a japanese<00:01:57.650> named<00:01:58.270> Yukihiro<00:01:59.270> Matsumoto<00:02:00.200> whose 00:02:01.030 --> 00:02:01.040 align:start position:0% japanese named Yukihiro Matsumoto whose 00:02:01.040 --> 00:02:06.250 align:start position:0% japanese named Yukihiro Matsumoto whose nickname<00:02:01.310> is<00:02:01.520> Matz<00:02:02.060> and<00:02:04.390> the<00:02:05.390> core<00:02:05.659> principle 00:02:06.250 --> 00:02:06.260 align:start position:0% nickname is Matz and the core principle 00:02:06.260 --> 00:02:08.680 align:start position:0% nickname is Matz and the core principle of<00:02:06.409> Ruby<00:02:06.860> language<00:02:07.040> I<00:02:07.580> think<00:02:08.239> you<00:02:08.330> can<00:02:08.479> get 00:02:08.680 --> 00:02:08.690 align:start position:0% of Ruby language I think you can get 00:02:08.690 --> 00:02:11.110 align:start position:0% of Ruby language I think you can get from<00:02:08.959> this<00:02:09.200> guy's<00:02:09.440> face<00:02:09.769> right<00:02:10.429> that's 00:02:11.110 --> 00:02:11.120 align:start position:0% from this guy's face right that's 00:02:11.120 --> 00:02:17.110 align:start position:0% from this guy's face right that's happiness<00:02:13.750> so<00:02:14.950> Ruby<00:02:15.950> is<00:02:15.980> a<00:02:16.129> language<00:02:16.549> designed 00:02:17.110 --> 00:02:17.120 align:start position:0% happiness so Ruby is a language designed 00:02:17.120 --> 00:02:20.940 align:start position:0% happiness so Ruby is a language designed for<00:02:17.540> human<00:02:18.110> it<00:02:19.000> it's<00:02:20.000> very<00:02:20.239> focused<00:02:20.510> on 00:02:20.940 --> 00:02:20.950 align:start position:0% for human it it's very focused on 00:02:20.950 --> 00:02:24.910 align:start position:0% for human it it's very focused on readability<00:02:21.950> so<00:02:22.640> in<00:02:23.330> one<00:02:23.900> of<00:02:23.930> his<00:02:24.260> talk<00:02:24.500> in<00:02:24.770> one 00:02:24.910 --> 00:02:24.920 align:start position:0% readability so in one of his talk in one 00:02:24.920 --> 00:02:26.420 align:start position:0% readability so in one of his talk in one of<00:02:25.010> math<00:02:25.310> talk 00:02:26.420 --> 00:02:26.430 align:start position:0% of math talk 00:02:26.430 --> 00:02:29.050 align:start position:0% of math talk the<00:02:26.780> presentation<00:02:27.780> title<00:02:28.170> is<00:02:28.290> optimized<00:02:28.860> for 00:02:29.050 --> 00:02:29.060 align:start position:0% the presentation title is optimized for 00:02:29.060 --> 00:02:30.740 align:start position:0% the presentation title is optimized for programmer<00:02:30.060> happiness 00:02:30.740 --> 00:02:30.750 align:start position:0% programmer happiness 00:02:30.750 --> 00:02:35.089 align:start position:0% programmer happiness so<00:02:31.140> if<00:02:31.260> you<00:02:32.540> make<00:02:33.540> a<00:02:33.720> spectrum<00:02:34.260> of<00:02:34.439> languages 00:02:35.089 --> 00:02:35.099 align:start position:0% so if you make a spectrum of languages 00:02:35.099 --> 00:02:40.429 align:start position:0% so if you make a spectrum of languages in<00:02:35.489> the<00:02:36.060> one<00:02:36.209> side<00:02:36.510> maybe<00:02:37.819> maybe<00:02:38.819> west<00:02:39.750> right 00:02:40.429 --> 00:02:40.439 align:start position:0% in the one side maybe maybe west right 00:02:40.439 --> 00:02:44.149 align:start position:0% in the one side maybe maybe west right the<00:02:41.040> ASM<00:02:41.790> and<00:02:42.000> in<00:02:42.510> in<00:02:43.049> the<00:02:43.230> other<00:02:43.349> side<00:02:43.620> is<00:02:43.799> Ruby 00:02:44.149 --> 00:02:44.159 align:start position:0% the ASM and in in the other side is Ruby 00:02:44.159 --> 00:02:47.179 align:start position:0% the ASM and in in the other side is Ruby I<00:02:44.340> believe<00:02:44.959> so<00:02:45.959> it's<00:02:46.140> all<00:02:46.290> optimized<00:02:46.920> for 00:02:47.179 --> 00:02:47.189 align:start position:0% I believe so it's all optimized for 00:02:47.189 --> 00:02:50.960 align:start position:0% I believe so it's all optimized for human<00:02:48.000> and<00:02:48.680> the<00:02:49.680> source<00:02:50.220> code<00:02:50.430> written<00:02:50.670> in 00:02:50.960 --> 00:02:50.970 align:start position:0% human and the source code written in 00:02:50.970 --> 00:02:54.050 align:start position:0% human and the source code written in rubies<00:02:51.299> will<00:02:51.780> read<00:02:52.140> very<00:02:52.620> naturally<00:02:53.340> and<00:02:53.459> we 00:02:54.050 --> 00:02:54.060 align:start position:0% rubies will read very naturally and we 00:02:54.060 --> 00:02:57.890 align:start position:0% rubies will read very naturally and we will<00:02:54.269> see<00:02:54.510> that<00:02:54.689> later<00:02:54.900> and<00:02:55.379> the<00:02:55.459> other<00:02:56.900> good 00:02:57.890 --> 00:02:57.900 align:start position:0% will see that later and the other good 00:02:57.900 --> 00:03:00.319 align:start position:0% will see that later and the other good point<00:02:58.170> of<00:02:58.379> Ruby's<00:02:58.980> flexibility<00:02:59.819> so<00:03:00.030> a<00:03:00.060> lot<00:03:00.299> of 00:03:00.319 --> 00:03:00.329 align:start position:0% point of Ruby's flexibility so a lot of 00:03:00.329 --> 00:03:02.899 align:start position:0% point of Ruby's flexibility so a lot of people<00:03:00.629> is<00:03:00.900> using<00:03:01.139> Ruby<00:03:01.620> to<00:03:02.069> define<00:03:02.459> her<00:03:02.730> no 00:03:02.899 --> 00:03:02.909 align:start position:0% people is using Ruby to define her no 00:03:02.909 --> 00:03:05.899 align:start position:0% people is using Ruby to define her no DSL<00:03:03.510> the<00:03:03.900> main<00:03:04.079> specific<00:03:04.349> language<00:03:05.220> so<00:03:05.879> that 00:03:05.899 --> 00:03:05.909 align:start position:0% DSL the main specific language so that 00:03:05.909 --> 00:03:08.449 align:start position:0% DSL the main specific language so that the<00:03:06.239> most<00:03:06.480> famous<00:03:06.750> one<00:03:07.049> is<00:03:07.170> rels<00:03:07.470> right<00:03:08.159> so 00:03:08.449 --> 00:03:08.459 align:start position:0% the most famous one is rels right so 00:03:08.459 --> 00:03:12.379 align:start position:0% the most famous one is rels right so real<00:03:08.760> see<00:03:09.000> is<00:03:09.769> DSL<00:03:10.769> for<00:03:11.159> web<00:03:11.579> development<00:03:12.090> and 00:03:12.379 --> 00:03:12.389 align:start position:0% real see is DSL for web development and 00:03:12.389 --> 00:03:17.390 align:start position:0% real see is DSL for web development and I<00:03:12.900> believe<00:03:13.170> we<00:03:13.349> can<00:03:13.530> also<00:03:14.189> use<00:03:14.670> Ruby<00:03:15.090> to<00:03:16.400> define 00:03:17.390 --> 00:03:17.400 align:start position:0% I believe we can also use Ruby to define 00:03:17.400 --> 00:03:25.819 align:start position:0% I believe we can also use Ruby to define some<00:03:17.700> DSL<00:03:18.420> for<00:03:18.689> smart<00:03:19.349> culture<00:03:23.540> so<00:03:24.540> we<00:03:25.349> created 00:03:25.819 --> 00:03:25.829 align:start position:0% some DSL for smart culture so we created 00:03:25.829 --> 00:03:28.580 align:start position:0% some DSL for smart culture so we created thethe<00:03:26.420> testing<00:03:27.420> and<00:03:27.569> deployment<00:03:28.019> framework 00:03:28.580 --> 00:03:28.590 align:start position:0% thethe testing and deployment framework 00:03:28.590 --> 00:03:33.379 align:start position:0% thethe testing and deployment framework for<00:03:29.519> smart<00:03:29.790> contract<00:03:31.190> after<00:03:32.190> you<00:03:32.849> install 00:03:33.379 --> 00:03:33.389 align:start position:0% for smart contract after you install 00:03:33.389 --> 00:03:38.119 align:start position:0% for smart contract after you install tests<00:03:34.579> you<00:03:35.579> can<00:03:35.910> open<00:03:36.780> your<00:03:36.840> console<00:03:37.379> and<00:03:37.590> type 00:03:38.119 --> 00:03:38.129 align:start position:0% tests you can open your console and type 00:03:38.129 --> 00:03:40.189 align:start position:0% tests you can open your console and type some<00:03:38.400> command<00:03:38.790> line<00:03:38.940> like<00:03:39.150> this<00:03:39.359> like<00:03:39.870> test 00:03:40.189 --> 00:03:40.199 align:start position:0% some command line like this like test 00:03:40.199 --> 00:03:42.439 align:start position:0% some command line like this like test new<00:03:40.530> big<00:03:40.859> thing<00:03:40.889> big<00:03:41.310> things<00:03:41.549> the<00:03:41.909> name<00:03:42.180> of 00:03:42.439 --> 00:03:42.449 align:start position:0% new big thing big things the name of 00:03:42.449 --> 00:03:45.979 align:start position:0% new big thing big things the name of your<00:03:43.199> next<00:03:44.010> big<00:03:44.340> project<00:03:44.639> okay<00:03:45.569> and<00:03:45.780> this 00:03:45.979 --> 00:03:45.989 align:start position:0% your next big project okay and this 00:03:45.989 --> 00:03:48.649 align:start position:0% your next big project okay and this command<00:03:46.560> will<00:03:46.739> generate<00:03:47.220> you<00:03:47.489> a<00:03:47.699> lot<00:03:48.180> of<00:03:48.209> files 00:03:48.649 --> 00:03:48.659 align:start position:0% command will generate you a lot of files 00:03:48.659 --> 00:03:57.890 align:start position:0% command will generate you a lot of files and<00:03:48.959> directories<00:03:55.639> an<00:03:56.639> amount<00:03:57.239> of<00:03:57.419> directories 00:03:57.890 --> 00:03:57.900 align:start position:0% and directories an amount of directories 00:03:57.900 --> 00:03:59.780 align:start position:0% and directories an amount of directories the<00:03:58.019> most<00:03:58.260> important<00:03:58.739> one<00:03:58.949> are<00:03:59.040> contracts<00:03:59.609> and 00:03:59.780 --> 00:03:59.790 align:start position:0% the most important one are contracts and 00:03:59.790 --> 00:04:02.479 align:start position:0% the most important one are contracts and tests<00:04:00.359> contracts<00:04:00.989> will<00:04:01.739> include<00:04:02.159> the 00:04:02.479 --> 00:04:02.489 align:start position:0% tests contracts will include the 00:04:02.489 --> 00:04:05.360 align:start position:0% tests contracts will include the generated<00:04:03.269> country<00:04:03.930> template<00:04:04.349> and<00:04:04.620> test<00:04:05.159> will 00:04:05.360 --> 00:04:05.370 align:start position:0% generated country template and test will 00:04:05.370 --> 00:04:08.420 align:start position:0% generated country template and test will include<00:04:05.870> will<00:04:06.870> have<00:04:07.049> to<00:04:07.260> generate<00:04:08.010> a<00:04:08.069> test 00:04:08.420 --> 00:04:08.430 align:start position:0% include will have to generate a test 00:04:08.430 --> 00:04:13.250 align:start position:0% include will have to generate a test template<00:04:09.979> and<00:04:11.359> then<00:04:12.359> you<00:04:12.510> can<00:04:12.690> do<00:04:12.870> tests 00:04:13.250 --> 00:04:13.260 align:start position:0% template and then you can do tests 00:04:13.260 --> 00:04:15.860 align:start position:0% template and then you can do tests generate<00:04:13.709> token<00:04:14.159> tokens<00:04:14.760> the<00:04:15.030> name<00:04:15.389> of<00:04:15.659> your 00:04:15.860 --> 00:04:15.870 align:start position:0% generate token tokens the name of your 00:04:15.870 --> 00:04:19.819 align:start position:0% generate token tokens the name of your smart<00:04:16.139> contract<00:04:17.900> so<00:04:18.900> you<00:04:19.169> can<00:04:19.470> name<00:04:19.799> it 00:04:19.819 --> 00:04:19.829 align:start position:0% smart contract so you can name it 00:04:19.829 --> 00:04:22.550 align:start position:0% smart contract so you can name it whatever<00:04:20.370> but<00:04:20.970> we<00:04:21.120> use<00:04:21.539> token<00:04:21.959> for<00:04:22.139> example 00:04:22.550 --> 00:04:22.560 align:start position:0% whatever but we use token for example 00:04:22.560 --> 00:04:26.560 align:start position:0% whatever but we use token for example and<00:04:22.740> here's<00:04:23.340> the<00:04:23.610> here's<00:04:24.389> the<00:04:24.539> generated<00:04:25.199> file 00:04:26.560 --> 00:04:26.570 align:start position:0% and here's the here's the generated file 00:04:26.570 --> 00:04:29.870 align:start position:0% and here's the here's the generated file in<00:04:27.570> the<00:04:27.870> on<00:04:28.139> your<00:04:28.470> left<00:04:28.740> side<00:04:28.860> you<00:04:29.310> can<00:04:29.580> see 00:04:29.870 --> 00:04:29.880 align:start position:0% in the on your left side you can see 00:04:29.880 --> 00:04:33.080 align:start position:0% in the on your left side you can see there's<00:04:30.449> a<00:04:30.630> solidity<00:04:31.020> contract<00:04:31.560> is<00:04:32.099> empty<00:04:32.880> and 00:04:33.080 --> 00:04:33.090 align:start position:0% there's a solidity contract is empty and 00:04:33.090 --> 00:04:36.610 align:start position:0% there's a solidity contract is empty and on<00:04:33.930> your<00:04:34.110> right<00:04:34.440> hand<00:04:34.680> is<00:04:34.950> the<00:04:35.310> generated<00:04:36.090> test 00:04:36.610 --> 00:04:36.620 align:start position:0% on your right hand is the generated test 00:04:36.620 --> 00:04:40.310 align:start position:0% on your right hand is the generated test for<00:04:37.620> the<00:04:37.770> left<00:04:37.950> side<00:04:38.570> smart<00:04:39.570> contract 00:04:40.310 --> 00:04:40.320 align:start position:0% for the left side smart contract 00:04:40.320 --> 00:04:43.880 align:start position:0% for the left side smart contract and<00:04:41.060> the<00:04:42.060> generated<00:04:42.540> test<00:04:42.780> is<00:04:43.020> very<00:04:43.350> simple 00:04:43.880 --> 00:04:43.890 align:start position:0% and the generated test is very simple 00:04:43.890 --> 00:04:48.380 align:start position:0% and the generated test is very simple it<00:04:44.430> includes<00:04:45.150> an<00:04:45.810> example<00:04:46.560> test<00:04:47.220> so<00:04:48.060> it<00:04:48.180> just 00:04:48.380 --> 00:04:48.390 align:start position:0% it includes an example test so it just 00:04:48.390 --> 00:04:54.200 align:start position:0% it includes an example test so it just says<00:04:48.540> assert<00:04:49.440> a<00:04:49.770> third<00:04:51.200> equation<00:04:52.200> of<00:04:53.210> assert 00:04:54.200 --> 00:04:54.210 align:start position:0% says assert a third equation of assert 00:04:54.210 --> 00:04:55.970 align:start position:0% says assert a third equation of assert that<00:04:54.240> the<00:04:54.540> counter<00:04:54.900> at<00:04:54.990> address<00:04:55.500> is<00:04:55.770> not 00:04:55.970 --> 00:04:55.980 align:start position:0% that the counter at address is not 00:04:55.980 --> 00:04:58.010 align:start position:0% that the counter at address is not kneeled<00:04:56.340> assert<00:04:56.970> that<00:04:57.000> the<00:04:57.300> contract<00:04:57.780> has 00:04:58.010 --> 00:04:58.020 align:start position:0% kneeled assert that the contract has 00:04:58.020 --> 00:05:04.130 align:start position:0% kneeled assert that the contract has been<00:04:58.590> deployed<00:05:01.490> okay<00:05:02.490> so<00:05:02.940> this<00:05:03.630> is<00:05:03.840> just 00:05:04.130 --> 00:05:04.140 align:start position:0% been deployed okay so this is just 00:05:04.140 --> 00:05:14.450 align:start position:0% been deployed okay so this is just generated<00:05:04.890> out<00:05:05.220> from<00:05:05.580> the<00:05:05.760> tool<00:05:13.280> okay<00:05:14.280> before 00:05:14.450 --> 00:05:14.460 align:start position:0% generated out from the tool okay before 00:05:14.460 --> 00:05:19.270 align:start position:0% generated out from the tool okay before we<00:05:14.760> jump<00:05:15.060> into<00:05:15.210> a<00:05:15.630> real<00:05:16.250> smart<00:05:17.250> contract<00:05:17.700> test 00:05:19.270 --> 00:05:19.280 align:start position:0% we jump into a real smart contract test 00:05:19.280 --> 00:05:23.270 align:start position:0% we jump into a real smart contract test you<00:05:20.280> need<00:05:20.460> to<00:05:20.580> know<00:05:20.760> some<00:05:21.500> tools<00:05:22.500> at<00:05:22.800> your<00:05:23.010> hand 00:05:23.270 --> 00:05:23.280 align:start position:0% you need to know some tools at your hand 00:05:23.280 --> 00:05:25.730 align:start position:0% you need to know some tools at your hand you<00:05:23.550> can<00:05:23.700> use<00:05:23.760> these<00:05:24.540> keywords<00:05:24.810> in<00:05:25.320> your<00:05:25.500> test 00:05:25.730 --> 00:05:25.740 align:start position:0% you can use these keywords in your test 00:05:25.740 --> 00:05:29.060 align:start position:0% you can use these keywords in your test so<00:05:26.610> we<00:05:26.850> have<00:05:27.060> some<00:05:27.450> we<00:05:28.380> have<00:05:28.410> some<00:05:28.830> tools 00:05:29.060 --> 00:05:29.070 align:start position:0% so we have some we have some tools 00:05:29.070 --> 00:05:32.390 align:start position:0% so we have some we have some tools relate<00:05:29.430> you<00:05:29.520> to<00:05:29.670> count<00:05:29.940> X<00:05:30.440> you<00:05:31.440> can<00:05:31.680> you<00:05:31.980> have 00:05:32.390 --> 00:05:32.400 align:start position:0% relate you to count X you can you have 00:05:32.400 --> 00:05:34.760 align:start position:0% relate you to count X you can you have access<00:05:32.850> to<00:05:33.060> state<00:05:33.330> state<00:05:33.870> is<00:05:34.050> a<00:05:34.080> collection<00:05:34.500> of 00:05:34.760 --> 00:05:34.770 align:start position:0% access to state state is a collection of 00:05:34.770 --> 00:05:37.460 align:start position:0% access to state state is a collection of accounts<00:05:35.070> and<00:05:35.460> you<00:05:36.330> have<00:05:36.510> access<00:05:36.960> to<00:05:37.140> head 00:05:37.460 --> 00:05:37.470 align:start position:0% accounts and you have access to head 00:05:37.470 --> 00:05:41.990 align:start position:0% accounts and you have access to head head<00:05:38.100> is<00:05:38.280> the<00:05:38.580> the<00:05:39.680> the<00:05:40.680> most<00:05:40.920> recent<00:05:41.460> block<00:05:41.730> of 00:05:41.990 --> 00:05:42.000 align:start position:0% head is the the the most recent block of 00:05:42.000 --> 00:05:45.290 align:start position:0% head is the the the most recent block of the<00:05:42.390> chain<00:05:42.630> the<00:05:43.040> the<00:05:44.040> current<00:05:44.400> block<00:05:44.490> and<00:05:44.850> you 00:05:45.290 --> 00:05:45.300 align:start position:0% the chain the the current block and you 00:05:45.300 --> 00:05:48.260 align:start position:0% the chain the the current block and you have<00:05:45.510> access<00:05:45.990> to<00:05:46.020> contract<00:05:46.980> contract<00:05:47.520> is<00:05:47.970> the 00:05:48.260 --> 00:05:48.270 align:start position:0% have access to contract contract is the 00:05:48.270 --> 00:05:52.100 align:start position:0% have access to contract contract is the Ruby<00:05:48.780> object<00:05:49.550> the<00:05:50.550> test<00:05:51.000> framework<00:05:51.540> built<00:05:51.840> for 00:05:52.100 --> 00:05:52.110 align:start position:0% Ruby object the test framework built for 00:05:52.110 --> 00:05:57.410 align:start position:0% Ruby object the test framework built for you<00:05:53.930> it's<00:05:54.930> compiled<00:05:55.680> from<00:05:56.010> the<00:05:56.490> solidity 00:05:57.410 --> 00:05:57.420 align:start position:0% you it's compiled from the solidity 00:05:57.420 --> 00:06:02.210 align:start position:0% you it's compiled from the solidity contract<00:05:57.990> it<00:05:58.730> it<00:05:59.730> extract<00:06:00.480> the<00:06:00.870> ABI<00:06:01.650> interface 00:06:02.210 --> 00:06:02.220 align:start position:0% contract it it extract the ABI interface 00:06:02.220 --> 00:06:05.480 align:start position:0% contract it it extract the ABI interface from<00:06:02.670> the<00:06:02.730> contract<00:06:03.420> and<00:06:03.800> the<00:06:04.800> test<00:06:05.070> framework 00:06:05.480 --> 00:06:05.490 align:start position:0% from the contract and the test framework 00:06:05.490 --> 00:06:07.160 align:start position:0% from the contract and the test framework we<00:06:05.640> have<00:06:05.670> you<00:06:05.910> the<00:06:06.090> cowshed<00:06:06.270> object<00:06:06.900> for<00:06:07.080> you 00:06:07.160 --> 00:06:07.170 align:start position:0% we have you the cowshed object for you 00:06:07.170 --> 00:06:09.860 align:start position:0% we have you the cowshed object for you so<00:06:07.350> you<00:06:07.440> can<00:06:07.620> use<00:06:08.130> the<00:06:08.370> object<00:06:08.640> to<00:06:09.150> do 00:06:09.860 --> 00:06:09.870 align:start position:0% so you can use the object to do 00:06:09.870 --> 00:06:12.260 align:start position:0% so you can use the object to do everything<00:06:10.230> to<00:06:11.040> do<00:06:11.190> all<00:06:11.430> kinds<00:06:11.760> of<00:06:11.820> scenes<00:06:12.120> on 00:06:12.260 --> 00:06:12.270 align:start position:0% everything to do all kinds of scenes on 00:06:12.270 --> 00:06:15.950 align:start position:0% everything to do all kinds of scenes on the<00:06:12.420> contract<00:06:12.810> and<00:06:12.960> you<00:06:13.500> can<00:06:14.930> take<00:06:15.930> some 00:06:15.950 --> 00:06:15.960 align:start position:0% the contract and you can take some 00:06:15.960 --> 00:06:19.610 align:start position:0% the contract and you can take some actions<00:06:16.620> so<00:06:16.800> you<00:06:16.860> can<00:06:17.160> transfer<00:06:18.170> Balan<00:06:19.170> you 00:06:19.610 --> 00:06:19.620 align:start position:0% actions so you can transfer Balan you 00:06:19.620 --> 00:06:21.890 align:start position:0% actions so you can transfer Balan you can<00:06:19.770> transfer<00:06:20.100> user<00:06:20.310> between<00:06:20.820> accounts<00:06:21.360> you 00:06:21.890 --> 00:06:21.900 align:start position:0% can transfer user between accounts you 00:06:21.900 --> 00:06:26.780 align:start position:0% can transfer user between accounts you can<00:06:22.170> deploy<00:06:23.420> contracts<00:06:24.420> to<00:06:24.660> the<00:06:24.960> state<00:06:25.790> deploy 00:06:26.780 --> 00:06:26.790 align:start position:0% can deploy contracts to the state deploy 00:06:26.790 --> 00:06:29.840 align:start position:0% can deploy contracts to the state deploy is<00:06:26.850> not<00:06:27.120> implemented<00:06:27.750> yet<00:06:27.780> so<00:06:28.110> is<00:06:28.230> in<00:06:28.410> grey<00:06:28.850> and 00:06:29.840 --> 00:06:29.850 align:start position:0% is not implemented yet so is in grey and 00:06:29.850 --> 00:06:32.450 align:start position:0% is not implemented yet so is in grey and you<00:06:30.480> can<00:06:30.720> call<00:06:30.960> all<00:06:31.260> kinds<00:06:31.680> of<00:06:31.770> functions<00:06:32.220> on 00:06:32.450 --> 00:06:32.460 align:start position:0% you can call all kinds of functions on 00:06:32.460 --> 00:06:35.570 align:start position:0% you can call all kinds of functions on the<00:06:32.750> counter<00:06:33.780> object<00:06:34.200> and<00:06:34.350> they<00:06:35.010> I<00:06:35.040> they<00:06:35.550> are 00:06:35.570 --> 00:06:35.580 align:start position:0% the counter object and they I they are 00:06:35.580 --> 00:06:37.970 align:start position:0% the counter object and they I they are some<00:06:35.970> pre<00:06:36.210> generated<00:06:36.810> randomly<00:06:37.320> generated 00:06:37.970 --> 00:06:37.980 align:start position:0% some pre generated randomly generated 00:06:37.980 --> 00:06:42.050 align:start position:0% some pre generated randomly generated accounts<00:06:39.410> you<00:06:40.410> can<00:06:40.590> reference<00:06:40.800> to<00:06:41.370> them<00:06:41.670> by 00:06:42.050 --> 00:06:42.060 align:start position:0% accounts you can reference to them by 00:06:42.060 --> 00:06:44.540 align:start position:0% accounts you can reference to them by using<00:06:42.090> private<00:06:42.930> keys<00:06:43.260> pop<00:06:43.590> keys<00:06:43.800> addresses 00:06:44.540 --> 00:06:44.550 align:start position:0% using private keys pop keys addresses 00:06:44.550 --> 00:06:49.430 align:start position:0% using private keys pop keys addresses and<00:06:46.520> as<00:06:47.520> a<00:06:47.610> tester<00:06:48.180> yourself<00:06:48.660> you<00:06:49.200> can 00:06:49.430 --> 00:06:49.440 align:start position:0% and as a tester yourself you can 00:06:49.440 --> 00:06:51.920 align:start position:0% and as a tester yourself you can reference<00:06:49.650> to<00:06:50.040> your<00:06:50.160> own<00:06:50.400> private<00:06:51.330> key<00:06:51.510> using 00:06:51.920 --> 00:06:51.930 align:start position:0% reference to your own private key using 00:06:51.930 --> 00:06:53.270 align:start position:0% reference to your own private key using private<00:06:52.140> key<00:06:52.350> pop<00:06:52.620> key<00:06:52.800> energy 00:06:53.270 --> 00:06:53.280 align:start position:0% private key pop key energy 00:06:53.280 --> 00:06:56.680 align:start position:0% private key pop key energy and<00:06:53.550> we<00:06:54.450> also<00:06:54.660> define<00:06:55.140> aliases<00:06:55.890> to<00:06:56.160> these 00:06:56.680 --> 00:06:56.690 align:start position:0% and we also define aliases to these 00:06:56.690 --> 00:07:00.380 align:start position:0% and we also define aliases to these randomly<00:06:57.690> generated<00:06:58.350> accounts<00:06:59.040> so<00:06:59.760> you<00:06:59.820> can 00:07:00.380 --> 00:07:00.390 align:start position:0% randomly generated accounts so you can 00:07:00.390 --> 00:07:04.640 align:start position:0% randomly generated accounts so you can use<00:07:02.330> well-known<00:07:03.330> names<00:07:03.570> like<00:07:03.930> Alice<00:07:04.350> Bob 00:07:04.640 --> 00:07:04.650 align:start position:0% use well-known names like Alice Bob 00:07:04.650 --> 00:07:08.830 align:start position:0% use well-known names like Alice Bob Carol<00:07:04.940> to<00:07:05.940> reference<00:07:06.570> to<00:07:07.170> those<00:07:07.410> generated 00:07:08.830 --> 00:07:08.840 align:start position:0% Carol to reference to those generated 00:07:08.840 --> 00:07:17.570 align:start position:0% Carol to reference to those generated accounts<00:07:11.450> so<00:07:12.450> here's<00:07:13.290> a<00:07:14.010> real<00:07:14.820> test<00:07:16.430> in<00:07:17.430> the 00:07:17.570 --> 00:07:17.580 align:start position:0% accounts so here's a real test in the 00:07:17.580 --> 00:07:22.550 align:start position:0% accounts so here's a real test in the left<00:07:17.760> its<00:07:19.160> standard<00:07:20.160> token<00:07:20.780> contracts<00:07:21.780> the 00:07:22.550 --> 00:07:22.560 align:start position:0% left its standard token contracts the 00:07:22.560 --> 00:07:24.890 align:start position:0% left its standard token contracts the token<00:07:22.920> council<00:07:23.310> has<00:07:23.520> issue<00:07:23.910> function<00:07:24.540> chance 00:07:24.890 --> 00:07:24.900 align:start position:0% token council has issue function chance 00:07:24.900 --> 00:07:27.440 align:start position:0% token council has issue function chance for<00:07:25.110> function<00:07:25.530> and<00:07:25.650> get<00:07:25.980> balance<00:07:26.370> and<00:07:26.640> on<00:07:27.270> your 00:07:27.440 --> 00:07:27.450 align:start position:0% for function and get balance and on your 00:07:27.450 --> 00:07:29.960 align:start position:0% for function and get balance and on your right<00:07:27.630> hand<00:07:27.930> is<00:07:28.350> the<00:07:28.860> test<00:07:29.190> for<00:07:29.490> the 00:07:29.960 --> 00:07:29.970 align:start position:0% right hand is the test for the 00:07:29.970 --> 00:07:32.690 align:start position:0% right hand is the test for the corresponding<00:07:30.720> contract<00:07:31.620> and<00:07:31.890> you<00:07:32.400> can<00:07:32.550> say 00:07:32.690 --> 00:07:32.700 align:start position:0% corresponding contract and you can say 00:07:32.700 --> 00:07:35.960 align:start position:0% corresponding contract and you can say at<00:07:33.120> the<00:07:33.330> first<00:07:33.570> line<00:07:33.780> we<00:07:34.050> we<00:07:34.740> use<00:07:35.040> contract 00:07:35.960 --> 00:07:35.970 align:start position:0% at the first line we we use contract 00:07:35.970 --> 00:07:41.660 align:start position:0% at the first line we we use contract issue<00:07:36.330> Bob<00:07:37.130> 100<00:07:38.130> and<00:07:38.340> that<00:07:39.000> means<00:07:40.130> we<00:07:41.130> invoke 00:07:41.660 --> 00:07:41.670 align:start position:0% issue Bob 100 and that means we invoke 00:07:41.670 --> 00:07:44.240 align:start position:0% issue Bob 100 and that means we invoke the<00:07:41.850> issue<00:07:42.060> function<00:07:42.720> to<00:07:43.140> issue<00:07:43.320> Bob<00:07:43.650> 100 00:07:44.240 --> 00:07:44.250 align:start position:0% the issue function to issue Bob 100 00:07:44.250 --> 00:07:47.150 align:start position:0% the issue function to issue Bob 100 tokens<00:07:44.430> and<00:07:44.850> then<00:07:45.750> we<00:07:45.960> transfer<00:07:46.200> Carol<00:07:46.770> 90 00:07:47.150 --> 00:07:47.160 align:start position:0% tokens and then we transfer Carol 90 00:07:47.160 --> 00:07:51.770 align:start position:0% tokens and then we transfer Carol 90 tokens<00:07:47.660> from<00:07:48.660> Bob<00:07:48.900> and<00:07:49.110> then<00:07:49.800> we<00:07:50.480> make<00:07:51.480> sure 00:07:51.770 --> 00:07:51.780 align:start position:0% tokens from Bob and then we make sure 00:07:51.780 --> 00:07:56.810 align:start position:0% tokens from Bob and then we make sure that<00:07:52.110> the<00:07:53.510> the<00:07:54.510> Carrows<00:07:55.200> account<00:07:55.650> has<00:07:56.310> 19 00:07:56.810 --> 00:07:56.820 align:start position:0% that the the Carrows account has 19 00:07:56.820 --> 00:08:01.460 align:start position:0% that the the Carrows account has 19 token<00:07:57.500> tokens<00:07:58.500> in<00:07:58.800> it<00:07:59.040> and<00:07:59.510> then<00:08:00.510> we<00:08:00.720> we<00:08:01.200> do<00:08:01.350> the 00:08:01.460 --> 00:08:01.470 align:start position:0% token tokens in it and then we we do the 00:08:01.470 --> 00:08:04.370 align:start position:0% token tokens in it and then we we do the chance<00:08:01.680> for<00:08:01.800> again<00:08:02.100> we<00:08:02.520> we<00:08:03.330> we<00:08:04.050> want<00:08:04.230> to<00:08:04.290> make 00:08:04.370 --> 00:08:04.380 align:start position:0% chance for again we we we want to make 00:08:04.380 --> 00:08:07.010 align:start position:0% chance for again we we we want to make sure<00:08:04.740> that<00:08:04.950> it<00:08:05.760> can<00:08:05.970> be<00:08:06.030> done<00:08:06.300> it<00:08:06.660> will<00:08:06.810> raise 00:08:07.010 --> 00:08:07.020 align:start position:0% sure that it can be done it will raise 00:08:07.020 --> 00:08:14.420 align:start position:0% sure that it can be done it will raise some<00:08:07.050> exceptions<00:08:07.950> so<00:08:09.890> in<00:08:11.570> in<00:08:12.570> the<00:08:13.430> contract 00:08:14.420 --> 00:08:14.430 align:start position:0% some exceptions so in in the contract 00:08:14.430 --> 00:08:16.969 align:start position:0% some exceptions so in in the contract has<00:08:14.610> you<00:08:14.850> can<00:08:15.090> you<00:08:15.900> can<00:08:16.080> find<00:08:16.110> one<00:08:16.560> thing<00:08:16.800> is 00:08:16.969 --> 00:08:16.979 align:start position:0% has you can you can find one thing is 00:08:16.979 --> 00:08:20.030 align:start position:0% has you can you can find one thing is that<00:08:17.280> it's<00:08:18.120> really<00:08:18.510> the<00:08:19.290> test<00:08:19.500> is<00:08:19.710> really 00:08:20.030 --> 00:08:20.040 align:start position:0% that it's really the test is really 00:08:20.040 --> 00:08:24.170 align:start position:0% that it's really the test is really compact<00:08:20.430> right<00:08:21.200> you<00:08:22.200> you<00:08:22.800> don't<00:08:23.100> just<00:08:23.910> know 00:08:24.170 --> 00:08:24.180 align:start position:0% compact right you you don't just know 00:08:24.180 --> 00:08:26.330 align:start position:0% compact right you you don't just know asynchronous<00:08:25.110> in<00:08:25.530> this<00:08:25.860> test 00:08:26.330 --> 00:08:26.340 align:start position:0% asynchronous in this test 00:08:26.340 --> 00:08:28.640 align:start position:0% asynchronous in this test there's<00:08:26.669> no<00:08:26.850> callbacks<00:08:27.330> there's<00:08:28.200> no<00:08:28.380> money 00:08:28.640 --> 00:08:28.650 align:start position:0% there's no callbacks there's no money 00:08:28.650 --> 00:08:31.550 align:start position:0% there's no callbacks there's no money you<00:08:29.490> don't<00:08:29.729> need<00:08:29.880> to<00:08:30.030> do<00:08:30.180> that<00:08:30.390> you<00:08:31.080> just<00:08:31.110> write 00:08:31.550 --> 00:08:31.560 align:start position:0% you don't need to do that you just write 00:08:31.560 --> 00:08:34.490 align:start position:0% you don't need to do that you just write the<00:08:31.770> test<00:08:32.039> and<00:08:32.310> you<00:08:32.419> run<00:08:33.419> the<00:08:33.630> test<00:08:33.839> just<00:08:34.200> just 00:08:34.490 --> 00:08:34.500 align:start position:0% the test and you run the test just just 00:08:34.500 --> 00:08:39.200 align:start position:0% the test and you run the test just just like<00:08:34.680> you<00:08:35.089> do<00:08:36.089> in<00:08:36.360> Java<00:08:36.750> or<00:08:37.110> C++<00:08:37.969> if<00:08:38.969> we<00:08:39.120> are 00:08:39.200 --> 00:08:39.210 align:start position:0% like you do in Java or C++ if we are 00:08:39.210 --> 00:08:43.780 align:start position:0% like you do in Java or C++ if we are wrong<00:08:39.419> is<00:08:40.099> instantly<00:08:41.099> and<00:08:41.310> give<00:08:41.729> you<00:08:41.880> feedback 00:08:43.780 --> 00:08:43.790 align:start position:0% wrong is instantly and give you feedback 00:08:43.790 --> 00:08:49.310 align:start position:0% wrong is instantly and give you feedback so<00:08:45.890> we<00:08:46.890> find<00:08:47.370> this<00:08:47.670> will<00:08:48.080> speed<00:08:49.080> up<00:08:49.290> your 00:08:49.310 --> 00:08:49.320 align:start position:0% so we find this will speed up your 00:08:49.320 --> 00:08:53.570 align:start position:0% so we find this will speed up your development<00:08:50.250> cycle<00:08:51.620> largely<00:08:52.620> because<00:08:53.310> now 00:08:53.570 --> 00:08:53.580 align:start position:0% development cycle largely because now 00:08:53.580 --> 00:08:56.480 align:start position:0% development cycle largely because now you<00:08:53.640> can<00:08:54.030> trick<00:08:54.600> with<00:08:54.870> the<00:08:55.230> contract<00:08:56.190> on<00:08:56.370> the 00:08:56.480 --> 00:08:56.490 align:start position:0% you can trick with the contract on the 00:08:56.490 --> 00:08:59.510 align:start position:0% you can trick with the contract on the left<00:08:56.670> side<00:08:56.940> and<00:08:57.290> then<00:08:58.290> you<00:08:58.620> just<00:08:59.280> run<00:08:59.400> your 00:08:59.510 --> 00:08:59.520 align:start position:0% left side and then you just run your 00:08:59.520 --> 00:09:00.290 align:start position:0% left side and then you just run your test<00:08:59.790> and<00:09:00.030> you 00:09:00.290 --> 00:09:00.300 align:start position:0% test and you 00:09:00.300 --> 00:09:04.010 align:start position:0% test and you boom<00:09:00.780> get<00:09:01.080> get<00:09:01.709> the<00:09:01.800> result<00:09:02.190> from<00:09:03.000> your<00:09:03.330> from 00:09:04.010 --> 00:09:04.020 align:start position:0% boom get get the result from your from 00:09:04.020 --> 00:09:06.170 align:start position:0% boom get get the result from your from your<00:09:04.170> code<00:09:04.350> you<00:09:04.589> you<00:09:04.980> just<00:09:05.250> written<00:09:05.430> in 00:09:06.170 --> 00:09:06.180 align:start position:0% your code you you just written in 00:09:06.180 --> 00:09:08.720 align:start position:0% your code you you just written in instantly<00:09:06.600> and<00:09:06.990> when<00:09:07.770> there's<00:09:08.220> something 00:09:08.720 --> 00:09:08.730 align:start position:0% instantly and when there's something 00:09:08.730 --> 00:09:11.500 align:start position:0% instantly and when there's something wrong<00:09:09.210> you<00:09:09.480> can<00:09:09.690> go<00:09:09.930> back<00:09:10.140> to<00:09:10.440> your<00:09:10.560> code<00:09:10.800> and 00:09:11.500 --> 00:09:11.510 align:start position:0% wrong you can go back to your code and 00:09:11.510 --> 00:09:16.579 align:start position:0% wrong you can go back to your code and do<00:09:12.510> something<00:09:13.910> this<00:09:14.910> feedback<00:09:15.510> circle<00:09:16.410> is 00:09:16.579 --> 00:09:16.589 align:start position:0% do something this feedback circle is 00:09:16.589 --> 00:09:19.730 align:start position:0% do something this feedback circle is much<00:09:17.279> shorter<00:09:17.610> than<00:09:18.000> if<00:09:18.690> you<00:09:18.960> deploy<00:09:19.710> a 00:09:19.730 --> 00:09:19.740 align:start position:0% much shorter than if you deploy a 00:09:19.740 --> 00:09:23.510 align:start position:0% much shorter than if you deploy a contract<00:09:20.250> to<00:09:20.430> test<00:09:21.029> net<00:09:21.270> or<00:09:21.480> if<00:09:21.839> you<00:09:22.250> use<00:09:23.250> other 00:09:23.510 --> 00:09:23.520 align:start position:0% contract to test net or if you use other 00:09:23.520 --> 00:09:32.780 align:start position:0% contract to test net or if you use other things<00:09:27.140> and<00:09:29.089> there's<00:09:30.089> better<00:09:30.990> stuff<00:09:31.610> what<00:09:32.610> if 00:09:32.780 --> 00:09:32.790 align:start position:0% things and there's better stuff what if 00:09:32.790 --> 00:09:35.060 align:start position:0% things and there's better stuff what if what<00:09:33.450> if<00:09:33.630> you<00:09:33.899> forget<00:09:34.260> to<00:09:34.320> write<00:09:34.709> the<00:09:34.890> first 00:09:35.060 --> 00:09:35.070 align:start position:0% what if you forget to write the first 00:09:35.070 --> 00:09:38.210 align:start position:0% what if you forget to write the first line<00:09:35.339> you<00:09:35.820> forget<00:09:36.209> to<00:09:36.390> issue<00:09:36.959> Bob<00:09:37.380> 100<00:09:38.040> tokens 00:09:38.210 --> 00:09:38.220 align:start position:0% line you forget to issue Bob 100 tokens 00:09:38.220 --> 00:09:41.230 align:start position:0% line you forget to issue Bob 100 tokens at<00:09:38.550> first<00:09:38.850> but<00:09:39.120> you<00:09:39.600> just<00:09:39.839> chance<00:09:40.290> for<00:09:40.529> Carol 00:09:41.230 --> 00:09:41.240 align:start position:0% at first but you just chance for Carol 00:09:41.240 --> 00:09:44.480 align:start position:0% at first but you just chance for Carol now<00:09:42.240> you<00:09:42.300> will<00:09:42.540> you<00:09:42.930> will<00:09:43.110> get<00:09:43.290> a<00:09:43.500> failure<00:09:43.770> in 00:09:44.480 --> 00:09:44.490 align:start position:0% now you will you will get a failure in 00:09:44.490 --> 00:09:48.410 align:start position:0% now you will you will get a failure in test<00:09:44.990> then<00:09:45.990> then<00:09:46.740> what<00:09:46.920> you<00:09:47.040> do<00:09:47.250> how<00:09:47.940> do<00:09:48.000> you<00:09:48.240> do 00:09:48.410 --> 00:09:48.420 align:start position:0% test then then what you do how do you do 00:09:48.420 --> 00:09:54.530 align:start position:0% test then then what you do how do you do bugger<00:09:48.660> how<00:09:49.320> do<00:09:49.380> you<00:09:49.620> bug<00:09:49.800> this<00:09:50.399> problem<00:09:53.029> in<00:09:54.029> in 00:09:54.530 --> 00:09:54.540 align:start position:0% bugger how do you bug this problem in in 00:09:54.540 --> 00:09:56.990 align:start position:0% bugger how do you bug this problem in in traditional<00:09:55.230> programming<00:09:55.649> contacts<00:09:56.339> we<00:09:56.820> may 00:09:56.990 --> 00:09:57.000 align:start position:0% traditional programming contacts we may 00:09:57.000 --> 00:09:59.800 align:start position:0% traditional programming contacts we may find<00:09:57.270> we<00:09:57.570> may<00:09:57.810> open<00:09:58.110> semantic<00:09:58.470> bugger<00:09:58.620> right 00:09:59.800 --> 00:09:59.810 align:start position:0% find we may open semantic bugger right 00:09:59.810 --> 00:10:04.400 align:start position:0% find we may open semantic bugger right but<00:10:01.310> someone<00:10:02.310> said<00:10:02.580> logger<00:10:03.270> is<00:10:03.540> the<00:10:03.810> ultimate 00:10:04.400 --> 00:10:04.410 align:start position:0% but someone said logger is the ultimate 00:10:04.410 --> 00:10:09.769 align:start position:0% but someone said logger is the ultimate debugger<00:10:04.860> I<00:10:05.040> don't<00:10:06.000> remember<00:10:06.149> whom<00:10:06.600> and<00:10:08.779> we 00:10:09.769 --> 00:10:09.779 align:start position:0% debugger I don't remember whom and we 00:10:09.779 --> 00:10:13.090 align:start position:0% debugger I don't remember whom and we found<00:10:10.080> that<00:10:10.260> in<00:10:10.620> in<00:10:10.980> solidity<00:10:11.580> we<00:10:12.089> have<00:10:12.390> log 00:10:13.090 --> 00:10:13.100 align:start position:0% found that in in solidity we have log 00:10:13.100 --> 00:10:16.160 align:start position:0% found that in in solidity we have log although<00:10:14.100> the<00:10:14.160> law<00:10:14.400> is<00:10:14.670> some<00:10:15.089> it<00:10:15.510> is<00:10:15.720> some<00:10:15.930> kind 00:10:16.160 --> 00:10:16.170 align:start position:0% although the law is some it is some kind 00:10:16.170 --> 00:10:19.760 align:start position:0% although the law is some it is some kind different<00:10:16.589> than<00:10:16.830> the<00:10:17.720> loggers<00:10:18.720> log<00:10:19.020> in 00:10:19.760 --> 00:10:19.770 align:start position:0% different than the loggers log in 00:10:19.770 --> 00:10:22.360 align:start position:0% different than the loggers log in traditional<00:10:20.700> programming<00:10:21.120> world<00:10:21.360> but 00:10:22.360 --> 00:10:22.370 align:start position:0% traditional programming world but 00:10:22.370 --> 00:10:28.660 align:start position:0% traditional programming world but there's<00:10:23.370> logger<00:10:23.670> right<00:10:24.380> so<00:10:25.940> we<00:10:26.940> can<00:10:26.970> add<00:10:27.480> a<00:10:27.540> lot 00:10:28.660 --> 00:10:28.670 align:start position:0% there's logger right so we can add a lot 00:10:28.670 --> 00:10:33.140 align:start position:0% there's logger right so we can add a lot we<00:10:29.670> can<00:10:29.910> write<00:10:30.690> a<00:10:30.720> log<00:10:31.020> in<00:10:31.290> contracts<00:10:32.070> and<00:10:32.160> the 00:10:33.140 --> 00:10:33.150 align:start position:0% we can write a log in contracts and the 00:10:33.150 --> 00:10:35.420 align:start position:0% we can write a log in contracts and the test<00:10:33.390> framework<00:10:33.900> when<00:10:34.200> when<00:10:34.740> you<00:10:34.860> run<00:10:35.100> in<00:10:35.279> the 00:10:35.420 --> 00:10:35.430 align:start position:0% test framework when when you run in the 00:10:35.430 --> 00:10:39.260 align:start position:0% test framework when when you run in the the<00:10:36.209> test<00:10:36.480> the<00:10:37.200> test<00:10:37.380> framework<00:10:37.890> will<00:10:38.270> print 00:10:39.260 --> 00:10:39.270 align:start position:0% the test the test framework will print 00:10:39.270 --> 00:10:42.980 align:start position:0% the test the test framework will print the<00:10:39.420> log<00:10:39.630> in<00:10:40.440> your<00:10:40.529> council<00:10:41.240> so<00:10:42.240> you<00:10:42.300> can<00:10:42.630> know 00:10:42.980 --> 00:10:42.990 align:start position:0% the log in your council so you can know 00:10:42.990 --> 00:10:45.970 align:start position:0% the log in your council so you can know what's<00:10:43.380> happening<00:10:44.040> in<00:10:44.580> your<00:10:44.760> contract<00:10:45.270> you 00:10:45.970 --> 00:10:45.980 align:start position:0% what's happening in your contract you 00:10:45.980 --> 00:10:50.600 align:start position:0% what's happening in your contract you can<00:10:46.980> know<00:10:47.130> you<00:10:47.970> can<00:10:48.000> know<00:10:48.380> immediately<00:10:49.380> if<00:10:49.890> the 00:10:50.600 --> 00:10:50.610 align:start position:0% can know you can know immediately if the 00:10:50.610 --> 00:10:54.140 align:start position:0% can know you can know immediately if the address<00:10:51.360> to<00:10:51.810> is<00:10:52.200> correct<00:10:52.709> passed<00:10:53.220> in<00:10:53.550> right 00:10:54.140 --> 00:10:54.150 align:start position:0% address to is correct passed in right 00:10:54.150 --> 00:10:58.940 align:start position:0% address to is correct passed in right you<00:10:54.660> can<00:10:55.370> do<00:10:56.370> it<00:10:56.579> to<00:10:57.180> all<00:10:57.750> kinds<00:10:58.110> of<00:10:58.170> things<00:10:58.230> to 00:10:58.940 --> 00:10:58.950 align:start position:0% you can do it to all kinds of things to 00:10:58.950 --> 00:11:03.769 align:start position:0% you can do it to all kinds of things to inspect<00:10:59.790> your<00:11:00.720> contract<00:11:01.230> and<00:11:02.300> this<00:11:03.300> is<00:11:03.510> very 00:11:03.769 --> 00:11:03.779 align:start position:0% inspect your contract and this is very 00:11:03.779 --> 00:11:07.250 align:start position:0% inspect your contract and this is very important<00:11:04.350> important<00:11:05.190> for<00:11:05.690> for<00:11:06.690> debugging<00:11:06.990> I 00:11:07.250 --> 00:11:07.260 align:start position:0% important important for for debugging I 00:11:07.260 --> 00:11:12.249 align:start position:0% important important for for debugging I believe 00:11:12.249 --> 00:11:12.259 align:start position:0% 00:11:12.259 --> 00:11:17.499 align:start position:0% an<00:11:12.319> interest<00:11:13.249> by<00:11:13.519> default<00:11:16.209> locks<00:11:17.209> will<00:11:17.479> be 00:11:17.499 --> 00:11:17.509 align:start position:0% an interest by default locks will be 00:11:17.509 --> 00:11:19.780 align:start position:0% an interest by default locks will be print<00:11:18.019> to<00:11:18.169> cancel<00:11:18.589> but<00:11:18.799> events<00:11:19.249> won't 00:11:19.780 --> 00:11:19.790 align:start position:0% print to cancel but events won't 00:11:19.790 --> 00:11:22.509 align:start position:0% print to cancel but events won't although<00:11:20.419> events<00:11:20.929> are<00:11:21.499> also<00:11:21.709> some<00:11:22.100> kinds<00:11:22.429> of 00:11:22.509 --> 00:11:22.519 align:start position:0% although events are also some kinds of 00:11:22.519 --> 00:11:25.389 align:start position:0% although events are also some kinds of locks<00:11:22.729> but<00:11:23.629> you<00:11:23.720> can<00:11:23.929> trick<00:11:24.589> those<00:11:24.799> options<00:11:25.309> to 00:11:25.389 --> 00:11:25.399 align:start position:0% locks but you can trick those options to 00:11:25.399 --> 00:11:31.059 align:start position:0% locks but you can trick those options to enable<00:11:26.109> events<00:11:27.109> printing<00:11:29.259> so<00:11:30.259> if<00:11:30.589> you<00:11:30.799> set 00:11:31.059 --> 00:11:31.069 align:start position:0% enable events printing so if you set 00:11:31.069 --> 00:11:33.969 align:start position:0% enable events printing so if you set print<00:11:31.369> events<00:11:31.819> to<00:11:31.970> chew<00:11:32.269> then<00:11:32.899> if<00:11:33.109> you<00:11:33.319> if 00:11:33.969 --> 00:11:33.979 align:start position:0% print events to chew then if you if 00:11:33.979 --> 00:11:36.849 align:start position:0% print events to chew then if you if there<00:11:34.309> is<00:11:34.399> an<00:11:34.519> event<00:11:34.850> in<00:11:35.539> your<00:11:35.600> contract<00:11:36.199> you 00:11:36.849 --> 00:11:36.859 align:start position:0% there is an event in your contract you 00:11:36.859 --> 00:11:40.569 align:start position:0% there is an event in your contract you will<00:11:37.039> see<00:11:37.959> the<00:11:38.959> below<00:11:39.259> lines<00:11:39.499> like<00:11:39.949> this<00:11:40.129> in 00:11:40.569 --> 00:11:40.579 align:start position:0% will see the below lines like this in 00:11:40.579 --> 00:11:45.369 align:start position:0% will see the below lines like this in your<00:11:40.699> council<00:11:41.259> and<00:11:42.879> here<00:11:43.879> you<00:11:43.970> can<00:11:44.119> see<00:11:44.379> the 00:11:45.369 --> 00:11:45.379 align:start position:0% your council and here you can see the 00:11:45.379 --> 00:11:55.109 align:start position:0% your council and here you can see the issue<00:11:45.529> from<00:11:46.429> account<00:11:46.999> and<00:11:47.649> amount<00:11:50.739> and<00:11:52.509> better 00:11:55.109 --> 00:11:55.119 align:start position:0% issue from account and amount and better 00:11:55.119 --> 00:11:59.289 align:start position:0% issue from account and amount and better test<00:11:56.119> is<00:11:56.389> a<00:11:56.749> language<00:11:57.499> agnostic<00:11:57.819> framework<00:11:58.819> so 00:11:59.289 --> 00:11:59.299 align:start position:0% test is a language agnostic framework so 00:11:59.299 --> 00:12:03.460 align:start position:0% test is a language agnostic framework so it<00:11:59.569> also<00:11:59.779> supports<00:12:00.289> serpent<00:12:01.749> and<00:12:02.749> I<00:12:03.109> don't 00:12:03.460 --> 00:12:03.470 align:start position:0% it also supports serpent and I don't 00:12:03.470 --> 00:12:05.939 align:start position:0% it also supports serpent and I don't know<00:12:03.679> how<00:12:03.859> many<00:12:03.919> server<00:12:04.369> and<00:12:04.489> developers<00:12:04.939> here 00:12:05.939 --> 00:12:05.949 align:start position:0% know how many server and developers here 00:12:05.949 --> 00:12:07.419 align:start position:0% know how many server and developers here whoa 00:12:07.419 --> 00:12:07.429 align:start position:0% whoa 00:12:07.429 --> 00:12:15.729 align:start position:0% whoa italic<00:12:11.229> okay<00:12:12.229> but<00:12:12.649> sir<00:12:13.160> burn<00:12:13.339> is<00:12:14.379> also<00:12:15.379> very 00:12:15.729 --> 00:12:15.739 align:start position:0% italic okay but sir burn is also very 00:12:15.739 --> 00:12:22.840 align:start position:0% italic okay but sir burn is also very good<00:12:16.069> smart<00:12:16.609> country<00:12:16.970> language<00:12:18.160> yeah<00:12:20.799> so<00:12:21.850> the 00:12:22.840 --> 00:12:22.850 align:start position:0% good smart country language yeah so the 00:12:22.850 --> 00:12:25.809 align:start position:0% good smart country language yeah so the test<00:12:23.119> is<00:12:23.299> possible<00:12:23.929> because<00:12:24.350> we<00:12:24.730> created<00:12:25.730> a 00:12:25.809 --> 00:12:25.819 align:start position:0% test is possible because we created a 00:12:25.819 --> 00:12:28.389 align:start position:0% test is possible because we created a ruby<00:12:26.089> serum<00:12:26.539> which<00:12:27.139> is<00:12:27.169> a<00:12:27.649> full 00:12:28.389 --> 00:12:28.399 align:start position:0% ruby serum which is a full 00:12:28.399 --> 00:12:33.009 align:start position:0% ruby serum which is a full implementation<00:12:29.179> of<00:12:29.839> Assyrian<00:12:31.600> protocol<00:12:32.600> it 00:12:33.009 --> 00:12:33.019 align:start position:0% implementation of Assyrian protocol it 00:12:33.019 --> 00:12:36.879 align:start position:0% implementation of Assyrian protocol it it<00:12:33.889> includes<00:12:34.369> a<00:12:34.579> lot<00:12:34.759> of<00:12:34.879> sins<00:12:35.269> so<00:12:35.629> what<00:12:36.410> behind 00:12:36.879 --> 00:12:36.889 align:start position:0% it includes a lot of sins so what behind 00:12:36.889 --> 00:12:39.789 align:start position:0% it includes a lot of sins so what behind has<00:12:37.189> is<00:12:37.489> test<00:12:37.879> will<00:12:38.149> compile<00:12:39.049> the<00:12:39.230> contracts 00:12:39.789 --> 00:12:39.799 align:start position:0% has is test will compile the contracts 00:12:39.799 --> 00:12:44.499 align:start position:0% has is test will compile the contracts and<00:12:40.119> run<00:12:41.119> the<00:12:41.419> bytecode<00:12:42.079> on<00:12:42.589> Ruby's<00:12:43.579> virtual 00:12:44.499 --> 00:12:44.509 align:start position:0% and run the bytecode on Ruby's virtual 00:12:44.509 --> 00:12:47.859 align:start position:0% and run the bytecode on Ruby's virtual machine<00:12:44.869> and<00:12:45.579> it<00:12:46.579> doesn't<00:12:47.269> involve<00:12:47.629> any 00:12:47.859 --> 00:12:47.869 align:start position:0% machine and it doesn't involve any 00:12:47.869 --> 00:12:52.090 align:start position:0% machine and it doesn't involve any mining<00:12:48.679> and<00:12:49.660> block<00:12:50.660> creation<00:12:51.289> it<00:12:51.499> just<00:12:51.799> run 00:12:52.090 --> 00:12:52.100 align:start position:0% mining and block creation it just run 00:12:52.100 --> 00:12:55.269 align:start position:0% mining and block creation it just run the<00:12:52.279> code<00:12:52.489> on<00:12:52.699> VM<00:12:53.169> that's<00:12:54.169> very<00:12:54.439> simple<00:12:54.889> right 00:12:55.269 --> 00:12:55.279 align:start position:0% the code on VM that's very simple right 00:12:55.279 --> 00:12:58.499 align:start position:0% the code on VM that's very simple right so<00:12:55.549> so<00:12:56.119> you<00:12:56.179> can<00:12:56.389> get<00:12:56.739> instantaneous<00:12:57.739> feedback 00:12:58.499 --> 00:12:58.509 align:start position:0% so so you can get instantaneous feedback 00:12:58.509 --> 00:13:05.799 align:start position:0% so so you can get instantaneous feedback and<00:13:02.709> at<00:13:03.709> this<00:13:03.949> time<00:13:04.220> ruby<00:13:04.579> sermon<00:13:04.999> has<00:13:05.119> evolved 00:13:05.799 --> 00:13:05.809 align:start position:0% and at this time ruby sermon has evolved 00:13:05.809 --> 00:13:09.729 align:start position:0% and at this time ruby sermon has evolved into<00:13:05.989> many<00:13:06.980> has<00:13:07.939> inspired<00:13:08.389> many<00:13:08.720> projects<00:13:09.350> so 00:13:09.729 --> 00:13:09.739 align:start position:0% into many has inspired many projects so 00:13:09.739 --> 00:13:14.499 align:start position:0% into many has inspired many projects so inside<00:13:10.749> inside<00:13:11.749> Ruby<00:13:12.109> sermon<00:13:12.559> we<00:13:12.679> have<00:13:13.509> we 00:13:14.499 --> 00:13:14.509 align:start position:0% inside inside Ruby sermon we have we 00:13:14.509 --> 00:13:19.929 align:start position:0% inside inside Ruby sermon we have we have<00:13:16.179> modules<00:13:17.739> in<00:13:18.739> charge<00:13:19.039> of<00:13:19.189> data<00:13:19.459> like 00:13:19.929 --> 00:13:19.939 align:start position:0% have modules in charge of data like 00:13:19.939 --> 00:13:23.800 align:start position:0% have modules in charge of data like block<00:13:20.209> transaction<00:13:20.869> etc<00:13:21.559> and<00:13:22.149> EVM 00:13:23.800 --> 00:13:23.810 align:start position:0% block transaction etc and EVM 00:13:23.810 --> 00:13:27.910 align:start position:0% block transaction etc and EVM it's<00:13:24.290> a<00:13:24.439> full<00:13:24.769> implementation<00:13:25.279> of<00:13:25.699> EVM<00:13:26.920> so 00:13:27.910 --> 00:13:27.920 align:start position:0% it's a full implementation of EVM so 00:13:27.920 --> 00:13:30.280 align:start position:0% it's a full implementation of EVM so there's<00:13:28.490> people<00:13:28.759> using<00:13:29.300> the<00:13:29.720> code<00:13:29.959> inside 00:13:30.280 --> 00:13:30.290 align:start position:0% there's people using the code inside 00:13:30.290 --> 00:13:33.579 align:start position:0% there's people using the code inside Ruby<00:13:30.920> seven<00:13:31.279> to<00:13:31.430> extract<00:13:32.029> ABI<00:13:32.600> from<00:13:33.079> contract 00:13:33.579 --> 00:13:33.589 align:start position:0% Ruby seven to extract ABI from contract 00:13:33.589 --> 00:13:36.509 align:start position:0% Ruby seven to extract ABI from contract and<00:13:33.910> there<00:13:34.910> are<00:13:35.029> also<00:13:35.240> utilities<00:13:35.959> like 00:13:36.509 --> 00:13:36.519 align:start position:0% and there are also utilities like 00:13:36.519 --> 00:13:40.600 align:start position:0% and there are also utilities like address<00:13:37.519> public<00:13:37.790> key<00:13:38.180> private<00:13:38.720> key<00:13:39.490> they<00:13:40.490> are 00:13:40.600 --> 00:13:40.610 align:start position:0% address public key private key they are 00:13:40.610 --> 00:13:42.879 align:start position:0% address public key private key they are very<00:13:40.850> convenient<00:13:41.329> tools<00:13:41.839> to<00:13:42.470> help<00:13:42.649> you 00:13:42.879 --> 00:13:42.889 align:start position:0% very convenient tools to help you 00:13:42.889 --> 00:13:46.509 align:start position:0% very convenient tools to help you convert<00:13:43.959> data<00:13:44.959> between<00:13:45.290> address<00:13:45.920> public<00:13:46.160> key 00:13:46.509 --> 00:13:46.519 align:start position:0% convert data between address public key 00:13:46.519 --> 00:13:50.379 align:start position:0% convert data between address public key and<00:13:46.610> private<00:13:46.670> key<00:13:47.059> and<00:13:48.339> Ruby<00:13:49.339> Sarah<00:13:49.670> also<00:13:50.209> has 00:13:50.379 --> 00:13:50.389 align:start position:0% and private key and Ruby Sarah also has 00:13:50.389 --> 00:13:53.499 align:start position:0% and private key and Ruby Sarah also has many<00:13:50.749> dependencies<00:13:51.559> like<00:13:51.620> our<00:13:52.189> LPS<00:13:52.370> -<00:13:52.999> serpent 00:13:53.499 --> 00:13:53.509 align:start position:0% many dependencies like our LPS - serpent 00:13:53.509 --> 00:14:00.999 align:start position:0% many dependencies like our LPS - serpent and<00:13:55.329> SEC<00:13:56.329> P<00:13:57.009> and<00:13:58.629> based<00:13:59.629> on<00:13:59.870> Ruby<00:14:00.170> serum<00:14:00.649> we<00:14:00.889> are 00:14:00.999 --> 00:14:01.009 align:start position:0% and SEC P and based on Ruby serum we are 00:14:01.009 --> 00:14:07.600 align:start position:0% and SEC P and based on Ruby serum we are now<00:14:01.360> building<00:14:02.360> wrath<00:14:03.100> ressies<00:14:04.100> a<00:14:06.249> full<00:14:07.249> ruby 00:14:07.600 --> 00:14:07.610 align:start position:0% now building wrath ressies a full ruby 00:14:07.610 --> 00:14:11.350 align:start position:0% now building wrath ressies a full ruby client<00:14:08.029> so<00:14:08.629> it's<00:14:09.529> some<00:14:09.800> kind<00:14:09.829> like<00:14:10.360> Joey 00:14:11.350 --> 00:14:11.360 align:start position:0% client so it's some kind like Joey 00:14:11.360 --> 00:14:11.980 align:start position:0% client so it's some kind like Joey cerium 00:14:11.980 --> 00:14:11.990 align:start position:0% cerium 00:14:11.990 --> 00:14:16.960 align:start position:0% cerium so<00:14:12.699> besides<00:14:13.699> Ruby<00:14:14.300> sermon<00:14:14.689> we<00:14:14.809> also<00:14:15.050> need<00:14:15.970> Ruby 00:14:16.960 --> 00:14:16.970 align:start position:0% so besides Ruby sermon we also need Ruby 00:14:16.970 --> 00:14:20.530 align:start position:0% so besides Ruby sermon we also need Ruby Tempe<00:14:17.480> to<00:14:17.629> P<00:14:17.809> the<00:14:18.079> network<00:14:18.470> layer<00:14:19.449> combined<00:14:20.449> a 00:14:20.530 --> 00:14:20.540 align:start position:0% Tempe to P the network layer combined a 00:14:20.540 --> 00:14:23.079 align:start position:0% Tempe to P the network layer combined a network<00:14:20.870> layer<00:14:21.050> with<00:14:21.379> Ruby<00:14:21.709> sermon<00:14:22.189> we<00:14:22.339> we<00:14:22.939> can 00:14:23.079 --> 00:14:23.089 align:start position:0% network layer with Ruby sermon we we can 00:14:23.089 --> 00:14:25.480 align:start position:0% network layer with Ruby sermon we we can build<00:14:23.269> rest<00:14:23.600> and<00:14:23.899> then<00:14:24.410> we<00:14:24.529> have<00:14:24.680> test<00:14:24.980> the 00:14:25.480 --> 00:14:25.490 align:start position:0% build rest and then we have test the 00:14:25.490 --> 00:14:29.639 align:start position:0% build rest and then we have test the testing<00:14:26.300> framework<00:14:26.779> and<00:14:26.990> we<00:14:27.709> have<00:14:27.949> Ruby<00:14:28.329> eath 00:14:29.639 --> 00:14:29.649 align:start position:0% testing framework and we have Ruby eath 00:14:29.649 --> 00:14:32.860 align:start position:0% testing framework and we have Ruby eath Ruby's<00:14:30.649> is<00:14:30.980> a<00:14:31.360> small<00:14:32.360> tool 00:14:32.860 --> 00:14:32.870 align:start position:0% Ruby's is a small tool 00:14:32.870 --> 00:14:36.189 align:start position:0% Ruby's is a small tool extracted<00:14:33.529> from<00:14:33.819> not<00:14:34.819> extracted<00:14:35.389> but<00:14:35.600> built 00:14:36.189 --> 00:14:36.199 align:start position:0% extracted from not extracted but built 00:14:36.199 --> 00:14:39.100 align:start position:0% extracted from not extracted but built based<00:14:36.470> on<00:14:36.709> ruby<00:14:37.100> serum<00:14:37.550> to<00:14:37.850> help<00:14:38.509> you<00:14:38.660> create 00:14:39.100 --> 00:14:39.110 align:start position:0% based on ruby serum to help you create 00:14:39.110 --> 00:14:42.160 align:start position:0% based on ruby serum to help you create and<00:14:39.649> sign<00:14:40.069> transactions<00:14:40.850> and<00:14:41.089> we<00:14:41.300> have<00:14:41.509> is 00:14:42.160 --> 00:14:42.170 align:start position:0% and sign transactions and we have is 00:14:42.170 --> 00:14:46.540 align:start position:0% and sign transactions and we have is JSON<00:14:42.559> RPC<00:14:42.800> which<00:14:43.370> is<00:14:43.579> a<00:14:43.990> JSON<00:14:44.990> RPC<00:14:45.139> kind<00:14:45.800> talked 00:14:46.540 --> 00:14:46.550 align:start position:0% JSON RPC which is a JSON RPC kind talked 00:14:46.550 --> 00:14:53.259 align:start position:0% JSON RPC which is a JSON RPC kind talked to<00:14:46.850> a<00:14:47.540> serum<00:14:48.290> server<00:14:48.649> a<00:14:49.269> serum<00:14:50.269> note<00:14:51.170> and<00:14:52.269> there 00:14:53.259 --> 00:14:53.269 align:start position:0% to a serum server a serum note and there 00:14:53.269 --> 00:14:56.980 align:start position:0% to a serum server a serum note and there are<00:14:53.329> some<00:14:53.569> projects<00:14:54.170> extracted<00:14:55.009> from<00:14:55.990> Ruby's 00:14:56.980 --> 00:14:56.990 align:start position:0% are some projects extracted from Ruby's 00:14:56.990 --> 00:15:04.389 align:start position:0% are some projects extracted from Ruby's area<00:15:00.879> so<00:15:01.879> thank<00:15:02.269> you