WEBVTT Kind: captions Language: en 00:00:00.480 --> 00:00:03.309 align:start position:0% okay<00:00:00.719> hi<00:00:01.200> everyone<00:00:02.200> okay<00:00:02.560> I 00:00:03.309 --> 00:00:03.319 align:start position:0% okay hi everyone okay I 00:00:03.319 --> 00:00:06.030 align:start position:0% okay hi everyone okay I didn't<00:00:04.319> think<00:00:04.600> it<00:00:04.799> was<00:00:05.040> so<00:00:05.279> emotional<00:00:05.720> to<00:00:05.879> talk 00:00:06.030 --> 00:00:06.040 align:start position:0% didn't think it was so emotional to talk 00:00:06.040 --> 00:00:07.590 align:start position:0% didn't think it was so emotional to talk about<00:00:06.279> Java<00:00:06.640> but<00:00:06.759> I<00:00:06.879> hope<00:00:07.040> it's<00:00:07.240> okay<00:00:07.399> for 00:00:07.590 --> 00:00:07.600 align:start position:0% about Java but I hope it's okay for 00:00:07.600 --> 00:00:08.669 align:start position:0% about Java but I hope it's okay for everybody 00:00:08.669 --> 00:00:08.679 align:start position:0% everybody 00:00:08.679 --> 00:00:12.950 align:start position:0% everybody else<00:00:09.840> um<00:00:10.840> so<00:00:11.840> I<00:00:12.080> hope<00:00:12.240> it<00:00:12.360> will<00:00:12.519> be<00:00:12.759> okay 00:00:12.950 --> 00:00:12.960 align:start position:0% else um so I hope it will be okay 00:00:12.960 --> 00:00:17.830 align:start position:0% else um so I hope it will be okay because<00:00:13.160> I<00:00:13.240> see<00:00:13.440> it's<00:00:13.519> a<00:00:13.839> bit<00:00:14.839> too<00:00:15.200> large<00:00:15.839> but 00:00:17.830 --> 00:00:17.840 align:start position:0% because I see it's a bit too large but 00:00:17.840 --> 00:00:21.550 align:start position:0% because I see it's a bit too large but uh<00:00:18.840> yeah<00:00:19.000> maybe<00:00:19.320> we<00:00:19.439> can 00:00:21.550 --> 00:00:21.560 align:start position:0% uh yeah maybe we can 00:00:21.560 --> 00:00:28.630 align:start position:0% uh yeah maybe we can just<00:00:22.560> oh<00:00:22.840> I 00:00:28.630 --> 00:00:28.640 align:start position:0% 00:00:28.640 --> 00:00:31.990 align:start position:0% see<00:00:29.640> yeah<00:00:30.240> okay<00:00:30.439> like<00:00:30.599> that<00:00:30.759> should<00:00:30.920> be 00:00:31.990 --> 00:00:32.000 align:start position:0% see yeah okay like that should be 00:00:32.000 --> 00:00:36.910 align:start position:0% see yeah okay like that should be okay<00:00:33.320> okay<00:00:34.320> so<00:00:34.879> hi<00:00:35.160> again<00:00:35.399> everyone<00:00:36.000> and<00:00:36.399> um 00:00:36.910 --> 00:00:36.920 align:start position:0% okay okay so hi again everyone and um 00:00:36.920 --> 00:00:39.110 align:start position:0% okay okay so hi again everyone and um I'm<00:00:37.800> going<00:00:37.879> to<00:00:38.120> talk<00:00:38.320> today<00:00:38.600> about<00:00:38.800> smart 00:00:39.110 --> 00:00:39.120 align:start position:0% I'm going to talk today about smart 00:00:39.120 --> 00:00:41.990 align:start position:0% I'm going to talk today about smart contracts<00:00:39.480> in<00:00:39.800> Java<00:00:40.800> and<00:00:41.039> the<00:00:41.399> work<00:00:41.640> I've<00:00:41.840> been 00:00:41.990 --> 00:00:42.000 align:start position:0% contracts in Java and the work I've been 00:00:42.000 --> 00:00:45.750 align:start position:0% contracts in Java and the work I've been doing<00:00:42.760> lately<00:00:43.760> so<00:00:44.039> just<00:00:44.200> to<00:00:44.680> give<00:00:45.039> um<00:00:45.559> a 00:00:45.750 --> 00:00:45.760 align:start position:0% doing lately so just to give um a 00:00:45.760 --> 00:00:48.910 align:start position:0% doing lately so just to give um a context<00:00:46.199> of<00:00:46.559> who<00:00:46.760> I<00:00:46.879> am<00:00:47.120> where<00:00:47.199> I<00:00:47.360> come<00:00:47.559> from<00:00:47.960> so 00:00:48.910 --> 00:00:48.920 align:start position:0% context of who I am where I come from so 00:00:48.920 --> 00:00:50.470 align:start position:0% context of who I am where I come from so I'm<00:00:49.039> on<00:00:49.280> the<00:00:49.440> functional<00:00:49.840> programming<00:00:50.280> and 00:00:50.470 --> 00:00:50.480 align:start position:0% I'm on the functional programming and 00:00:50.480 --> 00:00:53.150 align:start position:0% I'm on the functional programming and type<00:00:50.719> system<00:00:51.000> lover<00:00:51.879> I<00:00:52.039> like<00:00:52.239> my<00:00:52.440> types<00:00:52.760> I<00:00:52.920> like 00:00:53.150 --> 00:00:53.160 align:start position:0% type system lover I like my types I like 00:00:53.160 --> 00:00:56.310 align:start position:0% type system lover I like my types I like the<00:00:53.320> compiler<00:00:53.719> working<00:00:54.039> for<00:00:54.559> me<00:00:55.559> um<00:00:55.960> really 00:00:56.310 --> 00:00:56.320 align:start position:0% the compiler working for me um really 00:00:56.320 --> 00:00:58.910 align:start position:0% the compiler working for me um really into<00:00:56.640> distributed<00:00:57.280> system<00:00:58.199> and<00:00:58.440> this<00:00:58.559> is 00:00:58.910 --> 00:00:58.920 align:start position:0% into distributed system and this is 00:00:58.920 --> 00:01:01.549 align:start position:0% into distributed system and this is actually<00:00:59.320> what<00:00:59.680> uh<00:01:00.280> brought<00:01:00.600> me<00:01:00.800> to<00:01:01.000> ethereum 00:01:01.549 --> 00:01:01.559 align:start position:0% actually what uh brought me to ethereum 00:01:01.559 --> 00:01:05.149 align:start position:0% actually what uh brought me to ethereum was<00:01:01.719> working<00:01:02.000> on<00:01:02.120> a<00:01:02.960> distributed<00:01:03.879> open<00:01:04.280> data 00:01:05.149 --> 00:01:05.159 align:start position:0% was working on a distributed open data 00:01:05.159 --> 00:01:07.550 align:start position:0% was working on a distributed open data um<00:01:05.560> application<00:01:06.280> I<00:01:06.400> was<00:01:06.600> looking<00:01:06.920> for<00:01:07.159> a<00:01:07.360> way 00:01:07.550 --> 00:01:07.560 align:start position:0% um application I was looking for a way 00:01:07.560 --> 00:01:10.390 align:start position:0% um application I was looking for a way to<00:01:07.799> have<00:01:08.040> distributed<00:01:08.799> metadata<00:01:09.799> management 00:01:10.390 --> 00:01:10.400 align:start position:0% to have distributed metadata management 00:01:10.400 --> 00:01:13.749 align:start position:0% to have distributed metadata management system<00:01:11.400> with<00:01:11.560> a<00:01:12.040> Provence<00:01:12.920> um 00:01:13.749 --> 00:01:13.759 align:start position:0% system with a Provence um 00:01:13.759 --> 00:01:16.789 align:start position:0% system with a Provence um verification<00:01:14.759> and<00:01:15.000> while<00:01:15.200> looking<00:01:15.479> for<00:01:15.759> it<00:01:16.280> I 00:01:16.789 --> 00:01:16.799 align:start position:0% verification and while looking for it I 00:01:16.799 --> 00:01:20.510 align:start position:0% verification and while looking for it I discovered<00:01:17.479> ethereum<00:01:18.320> about<00:01:18.840> um<00:01:19.759> year<00:01:19.960> and<00:01:20.200> so 00:01:20.510 --> 00:01:20.520 align:start position:0% discovered ethereum about um year and so 00:01:20.520 --> 00:01:23.190 align:start position:0% discovered ethereum about um year and so ago<00:01:21.240> and<00:01:21.640> that<00:01:21.840> made<00:01:22.040> me<00:01:22.159> a<00:01:22.280> blockchain<00:01:22.720> addict 00:01:23.190 --> 00:01:23.200 align:start position:0% ago and that made me a blockchain addict 00:01:23.200 --> 00:01:25.390 align:start position:0% ago and that made me a blockchain addict because<00:01:23.439> it<00:01:23.560> was<00:01:23.720> so<00:01:23.960> great<00:01:24.320> to<00:01:24.759> suddenly<00:01:25.280> you 00:01:25.390 --> 00:01:25.400 align:start position:0% because it was so great to suddenly you 00:01:25.400 --> 00:01:29.270 align:start position:0% because it was so great to suddenly you can<00:01:25.600> do<00:01:25.799> all<00:01:26.040> this<00:01:26.759> security<00:01:27.560> and<00:01:28.280> proof<00:01:28.960> and 00:01:29.270 --> 00:01:29.280 align:start position:0% can do all this security and proof and 00:01:29.280 --> 00:01:34.510 align:start position:0% can do all this security and proof and uh<00:01:30.040> just<00:01:30.680> amazing<00:01:32.040> and<00:01:33.040> what<00:01:33.240> I<00:01:33.439> want<00:01:34.079> is<00:01:34.240> a 00:01:34.510 --> 00:01:34.520 align:start position:0% uh just amazing and what I want is a 00:01:34.520 --> 00:01:36.190 align:start position:0% uh just amazing and what I want is a strong<00:01:34.799> Java<00:01:35.119> community<00:01:35.479> on<00:01:35.600> ethereum<00:01:36.079> I 00:01:36.190 --> 00:01:36.200 align:start position:0% strong Java community on ethereum I 00:01:36.200 --> 00:01:39.630 align:start position:0% strong Java community on ethereum I think<00:01:36.479> that<00:01:37.479> us<00:01:37.880> the<00:01:38.040> Java<00:01:38.399> people<00:01:39.159> are<00:01:39.320> a<00:01:39.399> bit 00:01:39.630 --> 00:01:39.640 align:start position:0% think that us the Java people are a bit 00:01:39.640 --> 00:01:42.230 align:start position:0% think that us the Java people are a bit alone<00:01:40.079> in<00:01:40.399> in<00:01:41.040> in<00:01:41.200> all<00:01:41.360> the<00:01:41.479> ethereum<00:01:41.960> stuff 00:01:42.230 --> 00:01:42.240 align:start position:0% alone in in in all the ethereum stuff 00:01:42.240 --> 00:01:44.749 align:start position:0% alone in in in all the ethereum stuff and<00:01:42.360> it<00:01:42.439> would<00:01:42.640> be<00:01:42.920> nice<00:01:43.159> to<00:01:43.840> come<00:01:44.040> along<00:01:44.399> and 00:01:44.749 --> 00:01:44.759 align:start position:0% and it would be nice to come along and 00:01:44.759 --> 00:01:47.990 align:start position:0% and it would be nice to come along and do<00:01:45.759> uh<00:01:45.960> aome<00:01:46.360> application 00:01:47.990 --> 00:01:48.000 align:start position:0% do uh aome application 00:01:48.000 --> 00:01:50.950 align:start position:0% do uh aome application together<00:01:49.000> so<00:01:49.399> what<00:01:49.560> is<00:01:49.759> this<00:01:50.159> library<00:01:50.600> and<00:01:50.799> why 00:01:50.950 --> 00:01:50.960 align:start position:0% together so what is this library and why 00:01:50.960 --> 00:01:53.990 align:start position:0% together so what is this library and why it<00:01:51.159> exists<00:01:51.719> so<00:01:51.960> as<00:01:52.119> I<00:01:52.240> said<00:01:52.640> I<00:01:52.920> um<00:01:53.640> when<00:01:53.880> I 00:01:53.990 --> 00:01:54.000 align:start position:0% it exists so as I said I um when I 00:01:54.000 --> 00:01:56.389 align:start position:0% it exists so as I said I um when I started<00:01:54.320> to<00:01:54.520> try<00:01:54.799> to<00:01:54.960> do<00:01:55.159> stuff<00:01:55.399> with<00:01:55.560> ethereum 00:01:56.389 --> 00:01:56.399 align:start position:0% started to try to do stuff with ethereum 00:01:56.399 --> 00:01:59.990 align:start position:0% started to try to do stuff with ethereum I<00:01:57.399> I<00:01:57.520> looked<00:01:57.759> at<00:01:57.920> ethereum<00:01:58.360> J<00:01:58.759> for<00:01:59.039> any<00:01:59.399> Java 00:01:59.990 --> 00:02:00.000 align:start position:0% I I looked at ethereum J for any Java 00:02:00.000 --> 00:02:02.590 align:start position:0% I I looked at ethereum J for any Java guys<00:02:00.200> who<00:02:00.439> tried<00:02:00.840> it<00:02:01.399> it's<00:02:01.840> great<00:02:02.320> but<00:02:02.439> it's 00:02:02.590 --> 00:02:02.600 align:start position:0% guys who tried it it's great but it's 00:02:02.600 --> 00:02:04.709 align:start position:0% guys who tried it it's great but it's not<00:02:02.719> so<00:02:02.920> easy<00:02:03.119> to<00:02:03.320> use<00:02:03.840> it<00:02:04.000> was<00:02:04.200> really<00:02:04.399> hard<00:02:04.560> to 00:02:04.709 --> 00:02:04.719 align:start position:0% not so easy to use it was really hard to 00:02:04.719 --> 00:02:06.630 align:start position:0% not so easy to use it was really hard to set<00:02:04.920> up<00:02:05.200> it's<00:02:05.399> really<00:02:05.600> hard<00:02:05.759> to<00:02:05.960> connect<00:02:06.240> to<00:02:06.360> a 00:02:06.630 --> 00:02:06.640 align:start position:0% set up it's really hard to connect to a 00:02:06.640 --> 00:02:09.270 align:start position:0% set up it's really hard to connect to a network<00:02:07.439> really<00:02:07.680> hard<00:02:07.920> to<00:02:08.080> have<00:02:08.360> a<00:02:08.599> a<00:02:08.800> key<00:02:09.039> pair 00:02:09.270 --> 00:02:09.280 align:start position:0% network really hard to have a a key pair 00:02:09.280 --> 00:02:11.229 align:start position:0% network really hard to have a a key pair on<00:02:09.440> it<00:02:09.840> it<00:02:10.000> was<00:02:10.160> really 00:02:11.229 --> 00:02:11.239 align:start position:0% on it it was really 00:02:11.239 --> 00:02:13.630 align:start position:0% on it it was really frustrating<00:02:12.239> and<00:02:12.520> so<00:02:12.720> I<00:02:12.800> started<00:02:13.080> to<00:02:13.239> build<00:02:13.480> on 00:02:13.630 --> 00:02:13.640 align:start position:0% frustrating and so I started to build on 00:02:13.640 --> 00:02:15.750 align:start position:0% frustrating and so I started to build on that<00:02:13.800> trying<00:02:14.080> to<00:02:14.280> build<00:02:14.599> stuff<00:02:14.920> with<00:02:15.080> it<00:02:15.640> and 00:02:15.750 --> 00:02:15.760 align:start position:0% that trying to build stuff with it and 00:02:15.760 --> 00:02:17.630 align:start position:0% that trying to build stuff with it and it<00:02:15.959> became<00:02:16.280> slowly<00:02:16.720> my<00:02:16.959> personal<00:02:17.319> learning 00:02:17.630 --> 00:02:17.640 align:start position:0% it became slowly my personal learning 00:02:17.640 --> 00:02:20.110 align:start position:0% it became slowly my personal learning tool<00:02:18.040> I<00:02:18.120> learned<00:02:18.400> a<00:02:18.519> lot<00:02:18.720> with<00:02:19.040> ethereum<00:02:20.040> uh 00:02:20.110 --> 00:02:20.120 align:start position:0% tool I learned a lot with ethereum uh 00:02:20.120 --> 00:02:21.910 align:start position:0% tool I learned a lot with ethereum uh with<00:02:20.280> this<00:02:20.519> library<00:02:20.879> on<00:02:21.080> ethereum<00:02:21.640> how<00:02:21.800> it 00:02:21.910 --> 00:02:21.920 align:start position:0% with this library on ethereum how it 00:02:21.920 --> 00:02:25.030 align:start position:0% with this library on ethereum how it works<00:02:22.400> the<00:02:22.760> internals<00:02:23.640> how<00:02:23.959> you<00:02:24.519> create<00:02:24.840> your 00:02:25.030 --> 00:02:25.040 align:start position:0% works the internals how you create your 00:02:25.040 --> 00:02:28.309 align:start position:0% works the internals how you create your transaction<00:02:25.519> and<00:02:25.640> so<00:02:25.760> on<00:02:25.840> and<00:02:25.959> so<00:02:26.440> forth<00:02:27.440> and 00:02:28.309 --> 00:02:28.319 align:start position:0% transaction and so on and so forth and 00:02:28.319 --> 00:02:30.550 align:start position:0% transaction and so on and so forth and so<00:02:28.680> it<00:02:28.920> became<00:02:29.440> more<00:02:29.599> and<00:02:29.680> more<00:02:30.040> important<00:02:30.360> for 00:02:30.550 --> 00:02:30.560 align:start position:0% so it became more and more important for 00:02:30.560 --> 00:02:33.309 align:start position:0% so it became more and more important for me<00:02:30.840> to<00:02:31.120> have<00:02:31.519> to<00:02:31.720> help<00:02:32.000> other<00:02:32.319> people<00:02:33.080> trying 00:02:33.309 --> 00:02:33.319 align:start position:0% me to have to help other people trying 00:02:33.319 --> 00:02:35.350 align:start position:0% me to have to help other people trying to<00:02:33.519> experiment<00:02:33.920> with<00:02:34.080> ethereum<00:02:34.560> and 00:02:35.350 --> 00:02:35.360 align:start position:0% to experiment with ethereum and 00:02:35.360 --> 00:02:37.869 align:start position:0% to experiment with ethereum and doing<00:02:36.360> DBS<00:02:36.680> on 00:02:37.869 --> 00:02:37.879 align:start position:0% doing DBS on 00:02:37.879 --> 00:02:41.910 align:start position:0% doing DBS on it<00:02:38.879> so<00:02:39.200> what<00:02:39.360> is<00:02:39.599> this<00:02:39.959> uh<00:02:40.159> eth<00:02:40.519> contract<00:02:40.959> API 00:02:41.910 --> 00:02:41.920 align:start position:0% it so what is this uh eth contract API 00:02:41.920 --> 00:02:44.270 align:start position:0% it so what is this uh eth contract API so<00:02:42.239> it's<00:02:42.720> more<00:02:42.920> of<00:02:43.000> an<00:02:43.200> integration<00:02:43.760> Library 00:02:44.270 --> 00:02:44.280 align:start position:0% so it's more of an integration Library 00:02:44.280 --> 00:02:46.630 align:start position:0% so it's more of an integration Library it's<00:02:44.760> a<00:02:45.000> way<00:02:45.239> to<00:02:45.400> have<00:02:45.560> in<00:02:45.680> your<00:02:45.920> Java<00:02:46.319> some 00:02:46.630 --> 00:02:46.640 align:start position:0% it's a way to have in your Java some 00:02:46.640 --> 00:02:48.830 align:start position:0% it's a way to have in your Java some smart<00:02:47.040> contracts<00:02:47.440> as<00:02:47.560> a<00:02:47.720> service<00:02:48.400> same<00:02:48.680> way 00:02:48.830 --> 00:02:48.840 align:start position:0% smart contracts as a service same way 00:02:48.840 --> 00:02:51.750 align:start position:0% smart contracts as a service same way you<00:02:48.920> have<00:02:49.120> red<00:02:49.400> services<00:02:50.280> or<00:02:51.280> I<00:02:51.400> don't<00:02:51.560> know 00:02:51.750 --> 00:02:51.760 align:start position:0% you have red services or I don't know 00:02:51.760 --> 00:02:53.470 align:start position:0% you have red services or I don't know which<00:02:51.920> services<00:02:52.280> that<00:02:52.440> you<00:02:52.560> know<00:02:52.959> in<00:02:53.080> the<00:02:53.200> Java 00:02:53.470 --> 00:02:53.480 align:start position:0% which services that you know in the Java 00:02:53.480 --> 00:02:55.030 align:start position:0% which services that you know in the Java world<00:02:53.760> then<00:02:53.920> you<00:02:54.040> can<00:02:54.159> have<00:02:54.319> Smart<00:02:54.599> contracts 00:02:55.030 --> 00:02:55.040 align:start position:0% world then you can have Smart contracts 00:02:55.040 --> 00:02:58.830 align:start position:0% world then you can have Smart contracts as<00:02:55.519> well<00:02:56.519> uh<00:02:56.720> with<00:02:56.879> an<00:02:57.120> emphasis<00:02:57.760> on<00:02:58.280> the<00:02:58.519> type 00:02:58.830 --> 00:02:58.840 align:start position:0% as well uh with an emphasis on the type 00:02:58.840 --> 00:03:01.430 align:start position:0% as well uh with an emphasis on the type safety<00:02:59.840> so<00:03:00.000> that<00:03:00.239> the<00:03:00.480> compiler<00:03:01.040> helps<00:03:01.280> you 00:03:01.430 --> 00:03:01.440 align:start position:0% safety so that the compiler helps you 00:03:01.440 --> 00:03:04.070 align:start position:0% safety so that the compiler helps you and<00:03:01.560> works<00:03:01.800> for<00:03:02.200> you<00:03:03.200> and<00:03:03.440> the<00:03:03.560> easy 00:03:04.070 --> 00:03:04.080 align:start position:0% and works for you and the easy 00:03:04.080 --> 00:03:06.350 align:start position:0% and works for you and the easy integration<00:03:05.080> so<00:03:05.319> that<00:03:05.519> you<00:03:05.680> shouldn't<00:03:06.200> have 00:03:06.350 --> 00:03:06.360 align:start position:0% integration so that you shouldn't have 00:03:06.360 --> 00:03:08.990 align:start position:0% integration so that you shouldn't have to<00:03:06.720> think<00:03:07.080> about<00:03:08.040> okay<00:03:08.239> what<00:03:08.360> are<00:03:08.560> the<00:03:08.680> kind<00:03:08.840> of 00:03:08.990 --> 00:03:09.000 align:start position:0% to think about okay what are the kind of 00:03:09.000 --> 00:03:11.470 align:start position:0% to think about okay what are the kind of types<00:03:09.239> that<00:03:09.360> you<00:03:09.440> have<00:03:09.599> in<00:03:09.720> solidity<00:03:10.680> and<00:03:11.319> how 00:03:11.470 --> 00:03:11.480 align:start position:0% types that you have in solidity and how 00:03:11.480 --> 00:03:15.390 align:start position:0% types that you have in solidity and how do<00:03:11.760> they<00:03:11.959> translate<00:03:12.400> in<00:03:12.560> Java<00:03:12.879> it<00:03:12.959> should<00:03:13.120> be 00:03:15.390 --> 00:03:15.400 align:start position:0% 00:03:15.400 --> 00:03:19.390 align:start position:0% automatic<00:03:16.680> so<00:03:17.680> I've<00:03:17.840> been<00:03:18.040> working<00:03:18.319> on<00:03:18.480> it<00:03:19.120> for 00:03:19.390 --> 00:03:19.400 align:start position:0% automatic so I've been working on it for 00:03:19.400 --> 00:03:20.990 align:start position:0% automatic so I've been working on it for quite<00:03:19.599> some<00:03:19.840> time<00:03:20.080> and<00:03:20.239> today<00:03:20.599> what<00:03:20.720> you<00:03:20.799> can 00:03:20.990 --> 00:03:21.000 align:start position:0% quite some time and today what you can 00:03:21.000 --> 00:03:23.149 align:start position:0% quite some time and today what you can already<00:03:21.280> do<00:03:21.560> is<00:03:21.760> that<00:03:22.239> your<00:03:22.400> smart<00:03:22.720> contract 00:03:23.149 --> 00:03:23.159 align:start position:0% already do is that your smart contract 00:03:23.159 --> 00:03:25.990 align:start position:0% already do is that your smart contract is<00:03:23.599> uh<00:03:23.799> represented<00:03:24.480> by<00:03:24.640> an<00:03:24.840> interface<00:03:25.560> a<00:03:25.720> Java 00:03:25.990 --> 00:03:26.000 align:start position:0% is uh represented by an interface a Java 00:03:26.000 --> 00:03:27.789 align:start position:0% is uh represented by an interface a Java interface<00:03:26.879> that<00:03:27.080> has<00:03:27.360> that<00:03:27.480> will<00:03:27.640> be 00:03:27.789 --> 00:03:27.799 align:start position:0% interface that has that will be 00:03:27.799 --> 00:03:30.070 align:start position:0% interface that has that will be validated<00:03:28.319> against<00:03:28.640> the<00:03:28.720> AI<00:03:29.480> so<00:03:29.640> that<00:03:29.920> the 00:03:30.070 --> 00:03:30.080 align:start position:0% validated against the AI so that the 00:03:30.080 --> 00:03:33.270 align:start position:0% validated against the AI so that the parameters<00:03:30.799> input<00:03:31.120> and<00:03:31.280> output<00:03:32.159> uh<00:03:32.959> are 00:03:33.270 --> 00:03:33.280 align:start position:0% parameters input and output uh are 00:03:33.280 --> 00:03:35.750 align:start position:0% parameters input and output uh are correct<00:03:33.680> and<00:03:33.879> work<00:03:34.200> with<00:03:34.439> it<00:03:35.439> all<00:03:35.599> the 00:03:35.750 --> 00:03:35.760 align:start position:0% correct and work with it all the 00:03:35.760 --> 00:03:37.869 align:start position:0% correct and work with it all the communication<00:03:36.439> is<00:03:36.680> abstracted<00:03:37.239> away<00:03:37.760> so 00:03:37.869 --> 00:03:37.879 align:start position:0% communication is abstracted away so 00:03:37.879 --> 00:03:41.110 align:start position:0% communication is abstracted away so means<00:03:38.120> that<00:03:38.280> you<00:03:38.439> don't<00:03:38.720> need<00:03:39.480> to<00:03:40.480> think<00:03:40.760> about 00:03:41.110 --> 00:03:41.120 align:start position:0% means that you don't need to think about 00:03:41.120 --> 00:03:43.630 align:start position:0% means that you don't need to think about how<00:03:41.439> to<00:03:41.879> to<00:03:42.080> set<00:03:42.280> up<00:03:42.439> your<00:03:42.640> node<00:03:43.120> or<00:03:43.319> how<00:03:43.439> to 00:03:43.630 --> 00:03:43.640 align:start position:0% how to to set up your node or how to 00:03:43.640 --> 00:03:46.190 align:start position:0% how to to set up your node or how to connect<00:03:43.959> on<00:03:44.120> RPC<00:03:44.799> all<00:03:45.000> these<00:03:45.239> things<00:03:45.879> you<00:03:46.000> will 00:03:46.190 --> 00:03:46.200 align:start position:0% connect on RPC all these things you will 00:03:46.200 --> 00:03:49.110 align:start position:0% connect on RPC all these things you will have<00:03:46.400> a<00:03:46.760> a<00:03:47.080> provider<00:03:47.560> to<00:03:47.840> to<00:03:48.000> connect<00:03:48.319> to<00:03:48.480> it 00:03:49.110 --> 00:03:49.120 align:start position:0% have a a provider to to connect to it 00:03:49.120 --> 00:03:50.470 align:start position:0% have a a provider to to connect to it and<00:03:49.280> then<00:03:49.400> you<00:03:49.560> simply<00:03:49.879> use<00:03:50.040> it<00:03:50.200> you<00:03:50.319> don't 00:03:50.470 --> 00:03:50.480 align:start position:0% and then you simply use it you don't 00:03:50.480 --> 00:03:52.429 align:start position:0% and then you simply use it you don't have<00:03:50.599> to<00:03:50.760> think<00:03:51.040> about 00:03:52.429 --> 00:03:52.439 align:start position:0% have to think about 00:03:52.439 --> 00:03:55.429 align:start position:0% have to think about it<00:03:53.439> because<00:03:53.879> I<00:03:54.239> I<00:03:54.319> was<00:03:54.480> working<00:03:54.840> with<00:03:55.040> the 00:03:55.429 --> 00:03:55.439 align:start position:0% it because I I was working with the 00:03:55.439 --> 00:03:58.750 align:start position:0% it because I I was working with the existing<00:03:55.879> networks<00:03:56.480> there<00:03:56.599> is<00:03:56.879> um<00:03:57.280> a<00:03:57.760> pre 00:03:58.750 --> 00:03:58.760 align:start position:0% existing networks there is um a pre 00:03:58.760 --> 00:04:01.429 align:start position:0% existing networks there is um a pre defined<00:03:59.319> provider<00:04:00.040> for<00:04:00.239> The<00:04:00.519> Ether<00:04:00.920> cam<00:04:01.200> test 00:04:01.429 --> 00:04:01.439 align:start position:0% defined provider for The Ether cam test 00:04:01.439 --> 00:04:04.350 align:start position:0% defined provider for The Ether cam test net<00:04:02.000> the<00:04:02.120> mod<00:04:02.640> test<00:04:02.879> net<00:04:03.079> and<00:04:03.200> the<00:04:03.319> main 00:04:04.350 --> 00:04:04.360 align:start position:0% net the mod test net and the main 00:04:04.360 --> 00:04:07.030 align:start position:0% net the mod test net and the main net<00:04:05.360> it's<00:04:05.519> fully<00:04:05.799> nonblocking<00:04:06.519> so<00:04:06.680> you<00:04:06.760> don't 00:04:07.030 --> 00:04:07.040 align:start position:0% net it's fully nonblocking so you don't 00:04:07.040 --> 00:04:09.069 align:start position:0% net it's fully nonblocking so you don't have<00:04:07.159> to<00:04:07.319> do<00:04:07.480> all<00:04:07.640> the<00:04:08.079> synchronization 00:04:09.069 --> 00:04:09.079 align:start position:0% have to do all the synchronization 00:04:09.079 --> 00:04:10.470 align:start position:0% have to do all the synchronization whether<00:04:09.319> your<00:04:09.480> transaction<00:04:09.920> has<00:04:10.040> been<00:04:10.239> mine 00:04:10.470 --> 00:04:10.480 align:start position:0% whether your transaction has been mine 00:04:10.480 --> 00:04:12.830 align:start position:0% whether your transaction has been mine or<00:04:10.640> anything<00:04:11.200> you<00:04:11.400> get<00:04:11.720> a<00:04:11.840> future<00:04:12.280> back<00:04:12.640> and 00:04:12.830 --> 00:04:12.840 align:start position:0% or anything you get a future back and 00:04:12.840 --> 00:04:14.670 align:start position:0% or anything you get a future back and then<00:04:13.319> when<00:04:13.480> it's<00:04:13.680> done<00:04:13.920> it's 00:04:14.670 --> 00:04:14.680 align:start position:0% then when it's done it's 00:04:14.680 --> 00:04:18.189 align:start position:0% then when it's done it's done<00:04:15.680> and<00:04:16.519> as<00:04:16.680> much<00:04:16.880> as<00:04:17.120> possible<00:04:17.639> implicit 00:04:18.189 --> 00:04:18.199 align:start position:0% done and as much as possible implicit 00:04:18.199 --> 00:04:22.590 align:start position:0% done and as much as possible implicit data<00:04:18.519> fun<00:04:18.880> uh 00:04:22.590 --> 00:04:22.600 align:start position:0% 00:04:22.600 --> 00:04:25.230 align:start position:0% conversion<00:04:23.600> so<00:04:23.960> let's<00:04:24.160> see<00:04:24.320> some<00:04:24.520> codes<00:04:24.919> of 00:04:25.230 --> 00:04:25.240 align:start position:0% conversion so let's see some codes of 00:04:25.240 --> 00:04:27.110 align:start position:0% conversion so let's see some codes of how<00:04:25.479> does<00:04:25.639> it<00:04:25.840> work<00:04:26.040> and<00:04:26.240> how<00:04:26.400> you<00:04:26.600> do 00:04:27.110 --> 00:04:27.120 align:start position:0% how does it work and how you do 00:04:27.120 --> 00:04:30.189 align:start position:0% how does it work and how you do something<00:04:27.520> on<00:04:27.680> it<00:04:28.520> so<00:04:29.320> basically<00:04:29.840> you<00:04:29.960> create 00:04:30.189 --> 00:04:30.199 align:start position:0% something on it so basically you create 00:04:30.199 --> 00:04:31.990 align:start position:0% something on it so basically you create your<00:04:30.360> environment<00:04:30.919> here<00:04:31.280> so<00:04:31.479> it's<00:04:31.680> this 00:04:31.990 --> 00:04:32.000 align:start position:0% your environment here so it's this 00:04:32.000 --> 00:04:33.350 align:start position:0% your environment here so it's this ethereum 00:04:33.350 --> 00:04:33.360 align:start position:0% ethereum 00:04:33.360 --> 00:04:37.510 align:start position:0% ethereum facade<00:04:34.360> um<00:04:35.080> and<00:04:35.280> then<00:04:35.440> you<00:04:35.600> get<00:04:35.759> your<00:04:36.240> key<00:04:37.240> um 00:04:37.510 --> 00:04:37.520 align:start position:0% facade um and then you get your key um 00:04:37.520 --> 00:04:39.110 align:start position:0% facade um and then you get your key um of<00:04:37.720> course<00:04:38.000> because<00:04:38.400> I<00:04:38.479> don't<00:04:38.600> know<00:04:38.759> if<00:04:38.880> you 00:04:39.110 --> 00:04:39.120 align:start position:0% of course because I don't know if you 00:04:39.120 --> 00:04:42.110 align:start position:0% of course because I don't know if you guys<00:04:39.400> have<00:04:39.600> done<00:04:39.800> something<00:04:40.039> on<00:04:40.600> ether<00:04:41.600> uh<00:04:41.840> but 00:04:42.110 --> 00:04:42.120 align:start position:0% guys have done something on ether uh but 00:04:42.120 --> 00:04:44.670 align:start position:0% guys have done something on ether uh but they<00:04:42.520> all<00:04:43.520> they're<00:04:43.759> using<00:04:44.120> always<00:04:44.479> this 00:04:44.670 --> 00:04:44.680 align:start position:0% they all they're using always this 00:04:44.680 --> 00:04:47.070 align:start position:0% they all they're using always this spring<00:04:45.560> uh<00:04:45.800> wallet<00:04:46.400> so<00:04:46.560> you<00:04:46.680> don't<00:04:46.880> really 00:04:47.070 --> 00:04:47.080 align:start position:0% spring uh wallet so you don't really 00:04:47.080 --> 00:04:48.990 align:start position:0% spring uh wallet so you don't really have<00:04:47.199> a<00:04:47.320> key<00:04:47.560> store<00:04:48.199> but<00:04:48.360> you<00:04:48.440> can<00:04:48.600> use<00:04:48.840> the 00:04:48.990 --> 00:04:49.000 align:start position:0% have a key store but you can use the 00:04:49.000 --> 00:04:51.150 align:start position:0% have a key store but you can use the same<00:04:49.440> concept<00:04:49.840> to<00:04:50.199> take<00:04:50.400> your<00:04:50.560> key<00:04:50.759> store<00:04:50.960> from 00:04:51.150 --> 00:04:51.160 align:start position:0% same concept to take your key store from 00:04:51.160 --> 00:04:54.189 align:start position:0% same concept to take your key store from M<00:04:51.919> so<00:04:52.080> you<00:04:52.240> will<00:04:52.759> you<00:04:52.919> would<00:04:53.160> have<00:04:53.320> to<00:04:53.479> give<00:04:53.800> the 00:04:54.189 --> 00:04:54.199 align:start position:0% M so you will you would have to give the 00:04:54.199 --> 00:04:56.469 align:start position:0% M so you will you would have to give the the<00:04:54.400> K<00:04:54.759> ID<00:04:55.120> here<00:04:55.400> and<00:04:55.520> get<00:04:55.720> the<00:04:55.919> password 00:04:56.469 --> 00:04:56.479 align:start position:0% the K ID here and get the password 00:04:56.479 --> 00:04:58.590 align:start position:0% the K ID here and get the password afterwards<00:04:57.479> and<00:04:57.639> then<00:04:57.759> you<00:04:57.919> start<00:04:58.280> your 00:04:58.590 --> 00:04:58.600 align:start position:0% afterwards and then you start your 00:04:58.600 --> 00:05:00.430 align:start position:0% afterwards and then you start your ethereum<00:04:59.160> net<00:04:59.479> uh 00:05:00.430 --> 00:05:00.440 align:start position:0% ethereum net uh 00:05:00.440 --> 00:05:01.790 align:start position:0% ethereum net uh or 00:05:01.790 --> 00:05:01.800 align:start position:0% or 00:05:01.800 --> 00:05:04.710 align:start position:0% or environment<00:05:02.800> you<00:05:03.000> read<00:05:03.560> your<00:05:03.800> solidity<00:05:04.479> code 00:05:04.710 --> 00:05:04.720 align:start position:0% environment you read your solidity code 00:05:04.720 --> 00:05:07.950 align:start position:0% environment you read your solidity code you<00:05:04.840> want<00:05:05.000> to<00:05:05.240> work<00:05:06.120> against<00:05:07.120> in<00:05:07.280> this<00:05:07.440> case<00:05:07.759> I 00:05:07.950 --> 00:05:07.960 align:start position:0% you want to work against in this case I 00:05:07.960 --> 00:05:09.390 align:start position:0% you want to work against in this case I published<00:05:08.360> the<00:05:08.520> contract<00:05:08.960> but<00:05:09.080> you<00:05:09.160> don't 00:05:09.390 --> 00:05:09.400 align:start position:0% published the contract but you don't 00:05:09.400 --> 00:05:12.749 align:start position:0% published the contract but you don't have<00:05:09.520> to<00:05:09.720> you<00:05:09.840> can<00:05:10.039> also<00:05:10.960> simply<00:05:11.639> um<00:05:11.960> use<00:05:12.280> the 00:05:12.749 --> 00:05:12.759 align:start position:0% have to you can also simply um use the 00:05:12.759 --> 00:05:15.749 align:start position:0% have to you can also simply um use the the<00:05:12.960> existing<00:05:13.880> address<00:05:14.880> and<00:05:15.000> then<00:05:15.160> you<00:05:15.320> create 00:05:15.749 --> 00:05:15.759 align:start position:0% the existing address and then you create 00:05:15.759 --> 00:05:19.430 align:start position:0% the existing address and then you create the<00:05:15.919> proy<00:05:16.680> object<00:05:17.680> and<00:05:17.840> then<00:05:17.960> you<00:05:18.160> use<00:05:18.400> it<00:05:19.120> here 00:05:19.430 --> 00:05:19.440 align:start position:0% the proy object and then you use it here 00:05:19.440 --> 00:05:21.029 align:start position:0% the proy object and then you use it here for<00:05:19.639> example<00:05:19.919> I've<00:05:20.120> created<00:05:20.479> a<00:05:20.639> function 00:05:21.029 --> 00:05:21.039 align:start position:0% for example I've created a function 00:05:21.039 --> 00:05:24.590 align:start position:0% for example I've created a function called<00:05:21.759> register<00:05:22.759> this<00:05:22.840> is<00:05:23.240> a<00:05:24.240> another 00:05:24.590 --> 00:05:24.600 align:start position:0% called register this is a another 00:05:24.600 --> 00:05:27.029 align:start position:0% called register this is a another project<00:05:24.919> I'm<00:05:25.080> working<00:05:25.360> on<00:05:25.680> to<00:05:26.360> have<00:05:26.520> a 00:05:27.029 --> 00:05:27.039 align:start position:0% project I'm working on to have a 00:05:27.039 --> 00:05:29.950 align:start position:0% project I'm working on to have a distributed<00:05:28.000> App<00:05:28.240> Store<00:05:28.800> so<00:05:29.080> here<00:05:29.240> you<00:05:29.360> would 00:05:29.950 --> 00:05:29.960 align:start position:0% distributed App Store so here you would 00:05:29.960 --> 00:05:33.029 align:start position:0% distributed App Store so here you would publish<00:05:30.360> your<00:05:30.759> your<00:05:31.000> new<00:05:31.360> app<00:05:32.160> and<00:05:32.319> a<00:05:32.560> way<00:05:32.759> to 00:05:33.029 --> 00:05:33.039 align:start position:0% publish your your new app and a way to 00:05:33.039 --> 00:05:36.150 align:start position:0% publish your your new app and a way to get<00:05:33.240> it<00:05:34.080> with<00:05:34.240> a<00:05:34.400> check<00:05:34.680> s<00:05:35.000> to<00:05:35.160> make<00:05:35.319> sure<00:05:35.600> that 00:05:36.150 --> 00:05:36.160 align:start position:0% get it with a check s to make sure that 00:05:36.160 --> 00:05:37.870 align:start position:0% get it with a check s to make sure that when<00:05:36.360> people<00:05:36.639> download<00:05:37.000> it<00:05:37.160> they<00:05:37.319> download 00:05:37.870 --> 00:05:37.880 align:start position:0% when people download it they download 00:05:37.880 --> 00:05:39.950 align:start position:0% when people download it they download The<00:05:38.080> Right<00:05:38.319> Stuff<00:05:38.919> and<00:05:39.120> here<00:05:39.319> you<00:05:39.440> will<00:05:39.680> have 00:05:39.950 --> 00:05:39.960 align:start position:0% The Right Stuff and here you will have 00:05:39.960 --> 00:05:42.950 align:start position:0% The Right Stuff and here you will have the<00:05:40.120> the<00:05:40.280> interface<00:05:41.199> so<00:05:41.600> I<00:05:41.840> I'm<00:05:41.960> not<00:05:42.160> going<00:05:42.319> to 00:05:42.950 --> 00:05:42.960 align:start position:0% the the interface so I I'm not going to 00:05:42.960 --> 00:05:45.350 align:start position:0% the the interface so I I'm not going to show<00:05:43.400> the<00:05:43.880> exact<00:05:44.280> interface<00:05:44.800> but<00:05:44.960> I<00:05:45.000> will<00:05:45.160> show 00:05:45.350 --> 00:05:45.360 align:start position:0% show the exact interface but I will show 00:05:45.360 --> 00:05:47.990 align:start position:0% show the exact interface but I will show another<00:05:45.560> one<00:05:45.919> and<00:05:46.120> explain<00:05:46.440> a<00:05:46.639> bit<00:05:46.960> the<00:05:47.759> the 00:05:47.990 --> 00:05:48.000 align:start position:0% another one and explain a bit the the 00:05:48.000 --> 00:05:49.710 align:start position:0% another one and explain a bit the the the<00:05:48.160> convention<00:05:48.680> of<00:05:48.880> how<00:05:49.000> an<00:05:49.160> interface<00:05:49.600> has 00:05:49.710 --> 00:05:49.720 align:start position:0% the convention of how an interface has 00:05:49.720 --> 00:05:51.629 align:start position:0% the convention of how an interface has to<00:05:49.880> be 00:05:51.629 --> 00:05:51.639 align:start position:0% to be 00:05:51.639 --> 00:05:54.430 align:start position:0% to be written<00:05:52.639> so<00:05:53.000> basically<00:05:53.479> the<00:05:53.680> rule<00:05:54.000> is<00:05:54.199> like 00:05:54.430 --> 00:05:54.440 align:start position:0% written so basically the rule is like 00:05:54.440 --> 00:05:57.990 align:start position:0% written so basically the rule is like that<00:05:55.319> if<00:05:55.479> you<00:05:56.120> give<00:05:56.520> back<00:05:56.880> a<00:05:57.400> completable 00:05:57.990 --> 00:05:58.000 align:start position:0% that if you give back a completable 00:05:58.000 --> 00:05:59.950 align:start position:0% that if you give back a completable future<00:05:58.520> it<00:05:58.639> means<00:05:58.880> that<00:05:59.000> it<00:05:59.120> won't<00:05:59.280> be<00:05:59.400> a 00:05:59.950 --> 00:05:59.960 align:start position:0% future it means that it won't be a 00:05:59.960 --> 00:06:01.990 align:start position:0% future it means that it won't be a called<00:06:00.360> but<00:06:00.919> one<00:06:01.199> that<00:06:01.319> will<00:06:01.520> create<00:06:01.800> a 00:06:01.990 --> 00:06:02.000 align:start position:0% called but one that will create a 00:06:02.000 --> 00:06:04.510 align:start position:0% called but one that will create a transaction<00:06:03.000> and<00:06:03.120> you<00:06:03.360> define<00:06:03.960> what<00:06:04.160> kind<00:06:04.319> of 00:06:04.510 --> 00:06:04.520 align:start position:0% transaction and you define what kind of 00:06:04.520 --> 00:06:07.909 align:start position:0% transaction and you define what kind of value<00:06:04.759> you<00:06:04.880> want<00:06:05.039> to<00:06:05.280> get<00:06:05.960> in<00:06:06.440> return<00:06:07.440> if<00:06:07.639> it's 00:06:07.909 --> 00:06:07.919 align:start position:0% value you want to get in return if it's 00:06:07.919 --> 00:06:10.309 align:start position:0% value you want to get in return if it's void<00:06:08.360> it's<00:06:08.520> a<00:06:08.680> fire<00:06:08.960> and<00:06:09.120> forget<00:06:09.880> it<00:06:10.000> means 00:06:10.309 --> 00:06:10.319 align:start position:0% void it's a fire and forget it means 00:06:10.319 --> 00:06:11.909 align:start position:0% void it's a fire and forget it means that<00:06:10.520> you<00:06:10.639> want<00:06:10.759> to<00:06:10.880> create<00:06:11.120> transaction<00:06:11.800> you 00:06:11.909 --> 00:06:11.919 align:start position:0% that you want to create transaction you 00:06:11.919 --> 00:06:14.189 align:start position:0% that you want to create transaction you don't<00:06:12.080> really<00:06:12.319> care<00:06:12.639> when<00:06:13.199> it's<00:06:13.440> going<00:06:13.599> to 00:06:14.189 --> 00:06:14.199 align:start position:0% don't really care when it's going to 00:06:14.199 --> 00:06:17.870 align:start position:0% don't really care when it's going to happen<00:06:15.199> and<00:06:15.360> otherwise<00:06:15.919> you<00:06:16.080> have<00:06:16.280> all<00:06:16.880> the 00:06:17.870 --> 00:06:17.880 align:start position:0% happen and otherwise you have all the 00:06:17.880 --> 00:06:20.309 align:start position:0% happen and otherwise you have all the constant<00:06:18.319> calls<00:06:19.199> and<00:06:19.479> here<00:06:19.720> as<00:06:19.800> I<00:06:19.960> said<00:06:20.199> there 00:06:20.309 --> 00:06:20.319 align:start position:0% constant calls and here as I said there 00:06:20.319 --> 00:06:22.589 align:start position:0% constant calls and here as I said there was<00:06:20.560> there<00:06:20.680> is<00:06:20.880> this<00:06:21.199> um<00:06:21.919> uh<00:06:22.120> implicit 00:06:22.589 --> 00:06:22.599 align:start position:0% was there is this um uh implicit 00:06:22.599 --> 00:06:25.110 align:start position:0% was there is this um uh implicit conversion<00:06:23.160> so<00:06:23.639> string<00:06:24.000> is<00:06:24.160> string<00:06:24.840> you<00:06:24.960> can 00:06:25.110 --> 00:06:25.120 align:start position:0% conversion so string is string you can 00:06:25.120 --> 00:06:28.150 align:start position:0% conversion so string is string you can also<00:06:25.360> have<00:06:25.800> the<00:06:26.039> arrays<00:06:26.680> will<00:06:26.919> give<00:06:27.080> you<00:06:27.360> list 00:06:28.150 --> 00:06:28.160 align:start position:0% also have the arrays will give you list 00:06:28.160 --> 00:06:30.430 align:start position:0% also have the arrays will give you list and<00:06:28.319> if<00:06:28.440> you<00:06:28.560> have<00:06:28.720> your<00:06:28.840> own<00:06:29.240> return<00:06:29.680> type<00:06:30.280> it 00:06:30.430 --> 00:06:30.440 align:start position:0% and if you have your own return type it 00:06:30.440 --> 00:06:33.150 align:start position:0% and if you have your own return type it will<00:06:30.840> take<00:06:31.080> all<00:06:31.319> the<00:06:31.520> parameters<00:06:32.240> that<00:06:32.960> you 00:06:33.150 --> 00:06:33.160 align:start position:0% will take all the parameters that you 00:06:33.160 --> 00:06:35.230 align:start position:0% will take all the parameters that you get<00:06:33.440> back<00:06:33.880> find<00:06:34.080> the<00:06:34.280> Constructor<00:06:34.960> and<00:06:35.120> if 00:06:35.230 --> 00:06:35.240 align:start position:0% get back find the Constructor and if 00:06:35.240 --> 00:06:37.870 align:start position:0% get back find the Constructor and if there<00:06:35.360> is<00:06:35.479> one<00:06:35.720> matching<00:06:36.440> we<00:06:36.680> create<00:06:37.120> the<00:06:37.599> the 00:06:37.870 --> 00:06:37.880 align:start position:0% there is one matching we create the the 00:06:37.880 --> 00:06:41.950 align:start position:0% there is one matching we create the the object<00:06:38.880> so<00:06:39.280> this<00:06:39.520> way<00:06:40.160> all<00:06:40.400> these<00:06:40.840> things 00:06:41.950 --> 00:06:41.960 align:start position:0% object so this way all these things 00:06:41.960 --> 00:06:44.790 align:start position:0% object so this way all these things that<00:06:42.960> can<00:06:43.160> be<00:06:43.639> sometimes<00:06:43.919> frustrating<00:06:44.639> that 00:06:44.790 --> 00:06:44.800 align:start position:0% that can be sometimes frustrating that 00:06:44.800 --> 00:06:47.070 align:start position:0% that can be sometimes frustrating that you<00:06:44.960> cannot<00:06:45.919> return<00:06:46.199> struct<00:06:46.680> and<00:06:46.840> then<00:06:46.960> you 00:06:47.070 --> 00:06:47.080 align:start position:0% you cannot return struct and then you 00:06:47.080 --> 00:06:48.150 align:start position:0% you cannot return struct and then you have 00:06:48.150 --> 00:06:48.160 align:start position:0% have 00:06:48.160 --> 00:06:51.110 align:start position:0% have to<00:06:49.160> uh<00:06:49.400> make<00:06:49.639> them<00:06:49.960> back<00:06:50.240> again<00:06:50.680> here<00:06:50.880> it's 00:06:51.110 --> 00:06:51.120 align:start position:0% to uh make them back again here it's 00:06:51.120 --> 00:06:54.550 align:start position:0% to uh make them back again here it's done 00:06:54.550 --> 00:06:54.560 align:start position:0% 00:06:54.560 --> 00:06:57.469 align:start position:0% automatically<00:06:55.560> and<00:06:56.120> so<00:06:56.479> where<00:06:56.759> do<00:06:56.919> I<00:06:57.080> want<00:06:57.240> to 00:06:57.469 --> 00:06:57.479 align:start position:0% automatically and so where do I want to 00:06:57.479 --> 00:07:00.110 align:start position:0% automatically and so where do I want to go<00:06:57.720> with<00:06:57.879> this<00:06:58.039> Library<00:06:58.960> my<00:06:59.720> the<00:06:59.840> biggest 00:07:00.110 --> 00:07:00.120 align:start position:0% go with this Library my the biggest 00:07:00.120 --> 00:07:02.150 align:start position:0% go with this Library my the biggest dream<00:07:00.440> would<00:07:00.599> be<00:07:00.840> that<00:07:01.280> it's<00:07:01.520> compatible<00:07:02.000> with 00:07:02.150 --> 00:07:02.160 align:start position:0% dream would be that it's compatible with 00:07:02.160 --> 00:07:05.390 align:start position:0% dream would be that it's compatible with Android<00:07:02.840> we<00:07:03.000> going<00:07:03.120> to<00:07:03.280> think<00:07:03.680> that<00:07:03.840> doing<00:07:04.240> a<00:07:05.199> a 00:07:05.390 --> 00:07:05.400 align:start position:0% Android we going to think that doing a a 00:07:05.400 --> 00:07:08.270 align:start position:0% Android we going to think that doing a a mobile<00:07:05.800> apps<00:07:06.639> could<00:07:06.840> be<00:07:07.039> really<00:07:07.240> really 00:07:08.270 --> 00:07:08.280 align:start position:0% mobile apps could be really really 00:07:08.280 --> 00:07:11.670 align:start position:0% mobile apps could be really really cool<00:07:09.280> um<00:07:09.840> better<00:07:10.400> error<00:07:10.759> handling<00:07:11.280> because 00:07:11.670 --> 00:07:11.680 align:start position:0% cool um better error handling because 00:07:11.680 --> 00:07:14.029 align:start position:0% cool um better error handling because I've<00:07:11.800> been<00:07:11.960> doing<00:07:12.240> that<00:07:12.400> for<00:07:12.560> not<00:07:12.680> so<00:07:12.879> long<00:07:13.160> so 00:07:14.029 --> 00:07:14.039 align:start position:0% I've been doing that for not so long so 00:07:14.039 --> 00:07:16.309 align:start position:0% I've been doing that for not so long so some<00:07:14.360> errors<00:07:14.800> are<00:07:15.039> still<00:07:15.319> silent<00:07:15.800> it<00:07:15.919> is<00:07:16.080> not 00:07:16.309 --> 00:07:16.319 align:start position:0% some errors are still silent it is not 00:07:16.319 --> 00:07:19.950 align:start position:0% some errors are still silent it is not that<00:07:16.520> good<00:07:17.319> sometimes<00:07:17.560> also<00:07:18.080> tricky<00:07:18.479> to<00:07:18.680> find 00:07:19.950 --> 00:07:19.960 align:start position:0% that good sometimes also tricky to find 00:07:19.960 --> 00:07:22.990 align:start position:0% that good sometimes also tricky to find them<00:07:20.960> the<00:07:21.160> usual<00:07:21.639> suspect<00:07:22.639> better 00:07:22.990 --> 00:07:23.000 align:start position:0% them the usual suspect better 00:07:23.000 --> 00:07:25.550 align:start position:0% them the usual suspect better documentation<00:07:23.759> so<00:07:23.919> that<00:07:24.120> people<00:07:24.400> can<00:07:25.080> jump<00:07:25.400> on 00:07:25.550 --> 00:07:25.560 align:start position:0% documentation so that people can jump on 00:07:25.560 --> 00:07:28.309 align:start position:0% documentation so that people can jump on it<00:07:26.039> even<00:07:26.440> faster<00:07:27.360> easier<00:07:27.759> setup<00:07:28.120> in 00:07:28.309 --> 00:07:28.319 align:start position:0% it even faster easier setup in 00:07:28.319 --> 00:07:30.550 align:start position:0% it even faster easier setup in configuration<00:07:29.120> especially 00:07:30.550 --> 00:07:30.560 align:start position:0% configuration especially 00:07:30.560 --> 00:07:32.790 align:start position:0% configuration especially with<00:07:30.879> the<00:07:31.240> the<00:07:31.400> configuration<00:07:31.960> etherum<00:07:32.319> J<00:07:32.599> is 00:07:32.790 --> 00:07:32.800 align:start position:0% with the the configuration etherum J is 00:07:32.800 --> 00:07:35.070 align:start position:0% with the the configuration etherum J is not<00:07:33.039> so<00:07:33.479> it's<00:07:33.720> can<00:07:33.879> be<00:07:34.000> a<00:07:34.120> bit<00:07:34.280> tricky<00:07:34.639> so<00:07:34.919> like 00:07:35.070 --> 00:07:35.080 align:start position:0% not so it's can be a bit tricky so like 00:07:35.080 --> 00:07:37.550 align:start position:0% not so it's can be a bit tricky so like to<00:07:35.560> help<00:07:35.800> people<00:07:36.080> do<00:07:36.360> that<00:07:36.879> and<00:07:37.039> whatever<00:07:37.360> you 00:07:37.550 --> 00:07:37.560 align:start position:0% to help people do that and whatever you 00:07:37.560 --> 00:07:40.029 align:start position:0% to help people do that and whatever you need<00:07:37.960> I<00:07:38.039> mean<00:07:38.560> I<00:07:38.800> start<00:07:39.080> already<00:07:39.639> talking<00:07:39.960> with 00:07:40.029 --> 00:07:40.039 align:start position:0% need I mean I start already talking with 00:07:40.039 --> 00:07:42.230 align:start position:0% need I mean I start already talking with a<00:07:40.120> lot<00:07:40.280> of<00:07:40.560> developers<00:07:41.440> people<00:07:41.720> have<00:07:41.960> great 00:07:42.230 --> 00:07:42.240 align:start position:0% a lot of developers people have great 00:07:42.240 --> 00:07:44.589 align:start position:0% a lot of developers people have great ideas<00:07:43.000> different<00:07:43.280> needs<00:07:43.639> also<00:07:44.159> sometimes<00:07:44.360> you 00:07:44.589 --> 00:07:44.599 align:start position:0% ideas different needs also sometimes you 00:07:44.599 --> 00:07:46.950 align:start position:0% ideas different needs also sometimes you do<00:07:45.159> an<00:07:45.360> application<00:07:46.000> that<00:07:46.120> will<00:07:46.280> be<00:07:46.440> mobile 00:07:46.950 --> 00:07:46.960 align:start position:0% do an application that will be mobile 00:07:46.960 --> 00:07:49.110 align:start position:0% do an application that will be mobile some<00:07:47.360> people<00:07:47.599> will<00:07:47.800> do<00:07:48.039> data<00:07:48.319> analysis<00:07:48.919> some 00:07:49.110 --> 00:07:49.120 align:start position:0% some people will do data analysis some 00:07:49.120 --> 00:07:53.070 align:start position:0% some people will do data analysis some people<00:07:49.360> would<00:07:49.720> do<00:07:51.039> some<00:07:52.039> any<00:07:52.280> other<00:07:52.639> business 00:07:53.070 --> 00:07:53.080 align:start position:0% people would do some any other business 00:07:53.080 --> 00:07:55.430 align:start position:0% people would do some any other business needs<00:07:53.800> that<00:07:54.159> they<00:07:54.319> they<00:07:54.440> would<00:07:54.680> have<00:07:54.840> in<00:07:55.039> their 00:07:55.430 --> 00:07:55.440 align:start position:0% needs that they they would have in their 00:07:55.440 --> 00:08:00.110 align:start position:0% needs that they they would have in their company<00:07:55.840> big<00:07:56.000> or<00:07:56.159> small 00:08:00.110 --> 00:08:00.120 align:start position:0% 00:08:00.120 --> 00:08:03.909 align:start position:0% and<00:08:00.599> so<00:08:01.199> the<00:08:01.400> vision<00:08:02.080> of<00:08:02.360> the<00:08:02.919> this<00:08:03.080> library<00:08:03.680> is 00:08:03.909 --> 00:08:03.919 align:start position:0% and so the vision of the this library is 00:08:03.919 --> 00:08:06.110 align:start position:0% and so the vision of the this library is that<00:08:04.240> it<00:08:04.400> has<00:08:04.520> to<00:08:04.639> be<00:08:04.759> focused<00:08:05.080> on<00:08:05.199> ease<00:08:05.400> of<00:08:05.560> use 00:08:06.110 --> 00:08:06.120 align:start position:0% that it has to be focused on ease of use 00:08:06.120 --> 00:08:10.110 align:start position:0% that it has to be focused on ease of use should<00:08:06.319> be<00:08:06.520> easy<00:08:06.800> for<00:08:07.039> any<00:08:07.639> one<00:08:08.520> even<00:08:08.840> if<00:08:09.120> he 00:08:10.110 --> 00:08:10.120 align:start position:0% should be easy for any one even if he 00:08:10.120 --> 00:08:12.149 align:start position:0% should be easy for any one even if he doesn't<00:08:10.479> have<00:08:10.599> a<00:08:10.759> PhD<00:08:11.159> in 00:08:12.149 --> 00:08:12.159 align:start position:0% doesn't have a PhD in 00:08:12.159 --> 00:08:14.629 align:start position:0% doesn't have a PhD in ethereum<00:08:13.159> meaning<00:08:13.720> if<00:08:13.879> he<00:08:14.039> is<00:08:14.199> not<00:08:14.400> really 00:08:14.629 --> 00:08:14.639 align:start position:0% ethereum meaning if he is not really 00:08:14.639 --> 00:08:16.990 align:start position:0% ethereum meaning if he is not really vers<00:08:14.960> in<00:08:15.120> it<00:08:15.360> it<00:08:15.520> doesn't<00:08:16.080> understand<00:08:16.680> all<00:08:16.879> the 00:08:16.990 --> 00:08:17.000 align:start position:0% vers in it it doesn't understand all the 00:08:17.000 --> 00:08:18.589 align:start position:0% vers in it it doesn't understand all the mining<00:08:17.400> process<00:08:17.720> and<00:08:17.879> everything<00:08:18.199> should<00:08:18.440> be 00:08:18.589 --> 00:08:18.599 align:start position:0% mining process and everything should be 00:08:18.599 --> 00:08:21.589 align:start position:0% mining process and everything should be still<00:08:19.199> uh<00:08:19.360> able<00:08:19.599> to<00:08:19.800> use<00:08:20.039> it<00:08:20.879> and<00:08:21.039> always<00:08:21.319> open 00:08:21.589 --> 00:08:21.599 align:start position:0% still uh able to use it and always open 00:08:21.599 --> 00:08:24.550 align:start position:0% still uh able to use it and always open to<00:08:22.240> ideas<00:08:23.240> always<00:08:23.599> interesting<00:08:24.039> to<00:08:24.159> see<00:08:24.360> how 00:08:24.550 --> 00:08:24.560 align:start position:0% to ideas always interesting to see how 00:08:24.560 --> 00:08:26.909 align:start position:0% to ideas always interesting to see how people<00:08:24.840> use<00:08:25.120> the<00:08:25.280> system<00:08:25.680> in<00:08:25.879> different<00:08:26.240> ways 00:08:26.909 --> 00:08:26.919 align:start position:0% people use the system in different ways 00:08:26.919 --> 00:08:30.110 align:start position:0% people use the system in different ways different<00:08:27.240> needs<00:08:27.759> different<00:08:28.120> ideas 00:08:30.110 --> 00:08:30.120 align:start position:0% different needs different ideas 00:08:30.120 --> 00:08:31.790 align:start position:0% different needs different ideas and<00:08:30.199> so<00:08:30.360> my<00:08:30.520> dream<00:08:30.759> is<00:08:30.960> that<00:08:31.400> a<00:08:31.520> lot<00:08:31.639> of 00:08:31.790 --> 00:08:31.800 align:start position:0% and so my dream is that a lot of 00:08:31.800 --> 00:08:34.029 align:start position:0% and so my dream is that a lot of projects<00:08:32.120> are<00:08:32.320> cing<00:08:32.719> in<00:08:32.839> the<00:08:33.000> GBM<00:08:33.760> and<00:08:33.919> we 00:08:34.029 --> 00:08:34.039 align:start position:0% projects are cing in the GBM and we 00:08:34.039 --> 00:08:36.070 align:start position:0% projects are cing in the GBM and we should<00:08:34.320> help<00:08:34.560> them<00:08:34.760> use<00:08:35.159> the<00:08:35.320> ethereum<00:08:35.760> to<00:08:35.880> do 00:08:36.070 --> 00:08:36.080 align:start position:0% should help them use the ethereum to do 00:08:36.080 --> 00:08:38.190 align:start position:0% should help them use the ethereum to do that<00:08:36.680> and<00:08:36.800> a<00:08:36.959> lot<00:08:37.080> of<00:08:37.240> companies<00:08:37.640> are<00:08:37.800> using 00:08:38.190 --> 00:08:38.200 align:start position:0% that and a lot of companies are using 00:08:38.200 --> 00:08:40.230 align:start position:0% that and a lot of companies are using Java<00:08:38.599> and<00:08:38.800> we<00:08:39.080> we<00:08:39.200> should<00:08:39.440> help<00:08:39.640> them<00:08:39.839> do<00:08:40.039> that 00:08:40.230 --> 00:08:40.240 align:start position:0% Java and we we should help them do that 00:08:40.240 --> 00:08:43.350 align:start position:0% Java and we we should help them do that as<00:08:40.399> well<00:08:40.880> use<00:08:41.399> ethereum<00:08:42.399> and<00:08:42.760> I<00:08:42.880> know<00:08:43.080> that<00:08:43.240> a 00:08:43.350 --> 00:08:43.360 align:start position:0% as well use ethereum and I know that a 00:08:43.360 --> 00:08:45.670 align:start position:0% as well use ethereum and I know that a lot<00:08:43.519> of<00:08:43.719> developers<00:08:44.519> love<00:08:44.760> the<00:08:44.880> gvm<00:08:45.480> and<00:08:45.560> they 00:08:45.670 --> 00:08:45.680 align:start position:0% lot of developers love the gvm and they 00:08:45.680 --> 00:08:48.670 align:start position:0% lot of developers love the gvm and they also<00:08:45.880> love<00:08:46.279> ethereum<00:08:47.279> they<00:08:47.600> we<00:08:47.800> need<00:08:48.080> to<00:08:48.360> help 00:08:48.670 --> 00:08:48.680 align:start position:0% also love ethereum they we need to help 00:08:48.680 --> 00:08:51.310 align:start position:0% also love ethereum they we need to help them<00:08:49.399> join<00:08:49.720> the<00:08:49.920> club<00:08:50.240> and<00:08:50.440> have<00:08:50.600> fun<00:08:50.880> with<00:08:51.080> the 00:08:51.310 --> 00:08:51.320 align:start position:0% them join the club and have fun with the 00:08:51.320 --> 00:08:53.910 align:start position:0% them join the club and have fun with the with<00:08:51.480> all<00:08:51.600> of 00:08:53.910 --> 00:08:53.920 align:start position:0% 00:08:53.920 --> 00:08:56.870 align:start position:0% us<00:08:54.920> and<00:08:55.240> for<00:08:55.480> that<00:08:55.680> I<00:08:55.800> will<00:08:56.080> try<00:08:56.320> to<00:08:56.519> create<00:08:56.720> a 00:08:56.870 --> 00:08:56.880 align:start position:0% us and for that I will try to create a 00:08:56.880 --> 00:08:58.710 align:start position:0% us and for that I will try to create a Java<00:08:57.120> Community<00:08:57.680> I<00:08:57.800> would<00:08:57.959> like<00:08:58.120> to<00:08:58.360> have<00:08:58.560> more 00:08:58.710 --> 00:08:58.720 align:start position:0% Java Community I would like to have more 00:08:58.720 --> 00:09:02.910 align:start position:0% Java Community I would like to have more and<00:08:58.839> more<00:08:59.079> Java<00:08:59.480> developers<00:09:00.480> come<00:09:01.079> do<00:09:01.440> dabs<00:09:02.440> do 00:09:02.910 --> 00:09:02.920 align:start position:0% and more Java developers come do dabs do 00:09:02.920 --> 00:09:04.550 align:start position:0% and more Java developers come do dabs do things<00:09:03.200> in<00:09:03.360> the<00:09:03.519> ethereum<00:09:03.959> community<00:09:04.360> and 00:09:04.550 --> 00:09:04.560 align:start position:0% things in the ethereum community and 00:09:04.560 --> 00:09:08.509 align:start position:0% things in the ethereum community and ethereum<00:09:05.839> ecosystem<00:09:06.839> and<00:09:07.600> yeah<00:09:07.720> do<00:09:07.959> things 00:09:08.509 --> 00:09:08.519 align:start position:0% ethereum ecosystem and yeah do things 00:09:08.519 --> 00:09:11.870 align:start position:0% ethereum ecosystem and yeah do things together<00:09:09.519> and<00:09:09.640> for<00:09:09.920> that<00:09:10.160> I<00:09:10.279> know<00:09:10.600> it's<00:09:11.079> always 00:09:11.870 --> 00:09:11.880 align:start position:0% together and for that I know it's always 00:09:11.880 --> 00:09:13.630 align:start position:0% together and for that I know it's always if<00:09:12.040> you<00:09:12.320> try<00:09:12.519> to<00:09:12.640> do<00:09:12.800> something<00:09:13.079> at<00:09:13.279> work<00:09:13.519> they 00:09:13.630 --> 00:09:13.640 align:start position:0% if you try to do something at work they 00:09:13.640 --> 00:09:15.430 align:start position:0% if you try to do something at work they always<00:09:13.839> look<00:09:14.000> at<00:09:14.160> the<00:09:14.279> licensing<00:09:14.880> so 00:09:15.430 --> 00:09:15.440 align:start position:0% always look at the licensing so 00:09:15.440 --> 00:09:17.949 align:start position:0% always look at the licensing so licensing<00:09:15.880> should<00:09:16.120> be<00:09:16.560> as<00:09:17.240> friendly<00:09:17.720> as 00:09:17.949 --> 00:09:17.959 align:start position:0% licensing should be as friendly as 00:09:17.959 --> 00:09:21.350 align:start position:0% licensing should be as friendly as possible<00:09:18.360> for<00:09:18.720> people<00:09:19.000> to<00:09:19.160> do<00:09:19.480> stuff<00:09:19.800> with<00:09:20.360> it 00:09:21.350 --> 00:09:21.360 align:start position:0% possible for people to do stuff with it 00:09:21.360 --> 00:09:23.870 align:start position:0% possible for people to do stuff with it and<00:09:21.800> my<00:09:21.920> dream<00:09:22.200> is<00:09:22.320> to<00:09:22.480> see<00:09:22.920> many<00:09:23.440> companies 00:09:23.870 --> 00:09:23.880 align:start position:0% and my dream is to see many companies 00:09:23.880 --> 00:09:27.230 align:start position:0% and my dream is to see many companies big<00:09:24.079> and<00:09:24.240> small<00:09:24.560> to<00:09:24.760> adapt<00:09:25.040> ethereum<00:09:26.240> because 00:09:27.230 --> 00:09:27.240 align:start position:0% big and small to adapt ethereum because 00:09:27.240 --> 00:09:28.870 align:start position:0% big and small to adapt ethereum because because<00:09:27.560> of<00:09:27.800> all<00:09:27.959> the<00:09:28.079> work<00:09:28.279> we<00:09:28.399> will<00:09:28.560> do 00:09:28.870 --> 00:09:28.880 align:start position:0% because of all the work we will do 00:09:28.880 --> 00:09:34.509 align:start position:0% because of all the work we will do together 00:09:34.509 --> 00:09:34.519 align:start position:0% 00:09:34.519 --> 00:09:37.630 align:start position:0% and<00:09:34.640> for<00:09:34.880> that<00:09:35.200> we<00:09:35.760> we<00:09:35.880> need<00:09:36.160> you<00:09:36.399> we<00:09:36.519> need<00:09:37.079> the 00:09:37.630 --> 00:09:37.640 align:start position:0% and for that we we need you we need the 00:09:37.640 --> 00:09:40.190 align:start position:0% and for that we we need you we need the the<00:09:37.800> developers<00:09:38.360> to<00:09:38.560> do<00:09:38.839> stuff<00:09:39.120> on<00:09:39.279> it<00:09:40.040> you 00:09:40.190 --> 00:09:40.200 align:start position:0% the developers to do stuff on it you 00:09:40.200 --> 00:09:43.829 align:start position:0% the developers to do stuff on it you need<00:09:40.600> feedback<00:09:41.600> for<00:09:41.800> people<00:09:42.120> who<00:09:42.519> try<00:09:42.880> the<00:09:43.680> the 00:09:43.829 --> 00:09:43.839 align:start position:0% need feedback for people who try the the 00:09:43.839 --> 00:09:46.470 align:start position:0% need feedback for people who try the the library<00:09:44.320> to<00:09:44.519> try<00:09:44.800> it<00:09:44.920> to<00:09:45.120> tell 00:09:46.470 --> 00:09:46.480 align:start position:0% library to try it to tell 00:09:46.480 --> 00:09:49.230 align:start position:0% library to try it to tell me<00:09:47.480> what<00:09:47.600> is<00:09:47.839> good<00:09:48.079> what<00:09:48.200> is<00:09:48.440> bad<00:09:48.880> what<00:09:49.000> should 00:09:49.230 --> 00:09:49.240 align:start position:0% me what is good what is bad what should 00:09:49.240 --> 00:09:53.110 align:start position:0% me what is good what is bad what should be<00:09:49.399> changed<00:09:50.120> what<00:09:50.279> is<00:09:50.720> missing<00:09:51.720> so<00:09:51.880> on<00:09:52.040> and<00:09:52.200> so 00:09:53.110 --> 00:09:53.120 align:start position:0% be changed what is missing so on and so 00:09:53.120 --> 00:09:56.389 align:start position:0% be changed what is missing so on and so forth<00:09:54.120> actually<00:09:54.720> creating<00:09:55.279> dabs<00:09:56.040> I<00:09:56.160> think 00:09:56.389 --> 00:09:56.399 align:start position:0% forth actually creating dabs I think 00:09:56.399 --> 00:09:58.430 align:start position:0% forth actually creating dabs I think that<00:09:56.760> the<00:09:56.959> the<00:09:57.160> best<00:09:57.360> way<00:09:57.519> to<00:09:57.959> understand<00:09:58.160> how 00:09:58.430 --> 00:09:58.440 align:start position:0% that the the best way to understand how 00:09:58.440 --> 00:10:00.269 align:start position:0% that the the best way to understand how everything<00:09:58.760> works<00:09:59.000> is<00:09:59.480> to<00:09:59.640> actually<00:09:59.920> do 00:10:00.269 --> 00:10:00.279 align:start position:0% everything works is to actually do 00:10:00.279 --> 00:10:02.910 align:start position:0% everything works is to actually do something<00:10:01.279> so 00:10:02.910 --> 00:10:02.920 align:start position:0% something so 00:10:02.920 --> 00:10:06.030 align:start position:0% something so uh<00:10:03.920> the<00:10:04.240> the<00:10:04.480> the<00:10:04.600> thing<00:10:04.800> is<00:10:04.959> done<00:10:05.160> in<00:10:05.320> Java<00:10:05.720> but 00:10:06.030 --> 00:10:06.040 align:start position:0% uh the the the thing is done in Java but 00:10:06.040 --> 00:10:08.509 align:start position:0% uh the the the thing is done in Java but actually<00:10:06.279> I'm<00:10:06.399> a<00:10:06.519> Scala<00:10:06.880> lover<00:10:07.279> so<00:10:08.160> I<00:10:08.240> can 00:10:08.509 --> 00:10:08.519 align:start position:0% actually I'm a Scala lover so I can 00:10:08.519 --> 00:10:11.310 align:start position:0% actually I'm a Scala lover so I can guarantee<00:10:08.920> you<00:10:09.040> it<00:10:09.160> works<00:10:09.399> with<00:10:09.560> Scala<00:10:09.920> as 00:10:11.310 --> 00:10:11.320 align:start position:0% guarantee you it works with Scala as 00:10:11.320 --> 00:10:14.269 align:start position:0% guarantee you it works with Scala as well<00:10:12.320> um<00:10:12.600> and<00:10:12.760> be<00:10:13.000> active<00:10:13.360> talk<00:10:13.600> about<00:10:13.880> it<00:10:14.040> show 00:10:14.269 --> 00:10:14.279 align:start position:0% well um and be active talk about it show 00:10:14.279 --> 00:10:16.310 align:start position:0% well um and be active talk about it show it<00:10:14.399> to<00:10:14.560> everyone<00:10:15.240> I<00:10:15.360> think<00:10:15.560> it's<00:10:15.760> something 00:10:16.310 --> 00:10:16.320 align:start position:0% it to everyone I think it's something 00:10:16.320 --> 00:10:19.670 align:start position:0% it to everyone I think it's something that<00:10:17.320> the<00:10:17.600> livelier<00:10:18.240> we're<00:10:18.440> going<00:10:18.560> to<00:10:18.839> get 00:10:19.670 --> 00:10:19.680 align:start position:0% that the livelier we're going to get 00:10:19.680 --> 00:10:24.430 align:start position:0% that the livelier we're going to get more<00:10:20.040> productive<00:10:20.560> and<00:10:21.160> we're<00:10:21.360> going<00:10:21.440> to<00:10:21.640> be 00:10:24.430 --> 00:10:24.440 align:start position:0% 00:10:24.440 --> 00:10:27.030 align:start position:0% together<00:10:25.440> um<00:10:25.600> as<00:10:25.720> I<00:10:25.880> not<00:10:26.079> there<00:10:26.160> will<00:10:26.440> be<00:10:26.880> a 00:10:27.030 --> 00:10:27.040 align:start position:0% together um as I not there will be a 00:10:27.040 --> 00:10:30.910 align:start position:0% together um as I not there will be a next<00:10:27.360> event<00:10:28.079> end<00:10:28.320> of<00:10:28.760> uh<00:10:28.959> November<00:10:29.519> 26<00:10:29.959> and<00:10:30.120> 27 00:10:30.910 --> 00:10:30.920 align:start position:0% next event end of uh November 26 and 27 00:10:30.920 --> 00:10:33.829 align:start position:0% next event end of uh November 26 and 27 the<00:10:31.200> da<00:10:31.560> pack<00:10:32.000> in<00:10:32.160> Berlin<00:10:33.120> so<00:10:33.240> it<00:10:33.360> will<00:10:33.519> be<00:10:33.640> a 00:10:33.829 --> 00:10:33.839 align:start position:0% the da pack in Berlin so it will be a 00:10:33.839 --> 00:10:36.310 align:start position:0% the da pack in Berlin so it will be a two-day<00:10:34.320> long<00:10:34.920> event<00:10:35.360> where<00:10:35.519> people<00:10:35.800> can<00:10:36.040> both 00:10:36.310 --> 00:10:36.320 align:start position:0% two-day long event where people can both 00:10:36.320 --> 00:10:39.230 align:start position:0% two-day long event where people can both found<00:10:36.560> out<00:10:36.760> about<00:10:36.959> new<00:10:37.279> technologies<00:10:38.279> and<00:10:39.079> and 00:10:39.230 --> 00:10:39.240 align:start position:0% found out about new technologies and and 00:10:39.240 --> 00:10:42.670 align:start position:0% found out about new technologies and and also<00:10:39.600> try<00:10:40.040> and<00:10:40.279> write<00:10:40.560> some<00:10:41.079> apps<00:10:42.079> I<00:10:42.200> will<00:10:42.399> be 00:10:42.670 --> 00:10:42.680 align:start position:0% also try and write some apps I will be 00:10:42.680 --> 00:10:45.269 align:start position:0% also try and write some apps I will be there<00:10:42.920> there<00:10:43.040> will<00:10:43.160> be<00:10:43.320> also<00:10:43.639> other 00:10:45.269 --> 00:10:45.279 align:start position:0% there there will be also other 00:10:45.279 --> 00:10:47.629 align:start position:0% there there will be also other other<00:10:46.279> projects<00:10:46.760> there<00:10:46.959> that<00:10:47.120> will<00:10:47.279> show<00:10:47.519> what 00:10:47.629 --> 00:10:47.639 align:start position:0% other projects there that will show what 00:10:47.639 --> 00:10:50.030 align:start position:0% other projects there that will show what they're<00:10:47.880> doing<00:10:48.320> and<00:10:48.480> show<00:10:49.240> how<00:10:49.399> you<00:10:49.519> can<00:10:49.760> play 00:10:50.030 --> 00:10:50.040 align:start position:0% they're doing and show how you can play 00:10:50.040 --> 00:10:53.430 align:start position:0% they're doing and show how you can play with<00:10:50.240> them<00:10:50.959> senya<00:10:51.399> is<00:10:51.639> here<00:10:52.000> you<00:10:52.120> can<00:10:52.399> ask<00:10:52.639> her 00:10:53.430 --> 00:10:53.440 align:start position:0% with them senya is here you can ask her 00:10:53.440 --> 00:10:56.710 align:start position:0% with them senya is here you can ask her everything<00:10:54.440> if<00:10:54.600> you<00:10:54.920> want<00:10:55.160> to<00:10:55.360> know<00:10:56.160> anything 00:10:56.710 --> 00:10:56.720 align:start position:0% everything if you want to know anything 00:10:56.720 --> 00:10:59.470 align:start position:0% everything if you want to know anything else<00:10:57.079> on<00:10:57.360> that 00:10:59.470 --> 00:10:59.480 align:start position:0% else on that 00:10:59.480 --> 00:11:00.750 align:start position:0% else on that and<00:10:59.720> to 00:11:00.750 --> 00:11:00.760 align:start position:0% and to 00:11:00.760 --> 00:11:03.870 align:start position:0% and to finish<00:11:01.760> all<00:11:02.040> the<00:11:02.279> usual<00:11:02.760> suspect<00:11:03.480> how<00:11:03.639> to 00:11:03.870 --> 00:11:03.880 align:start position:0% finish all the usual suspect how to 00:11:03.880 --> 00:11:07.269 align:start position:0% finish all the usual suspect how to contact<00:11:04.240> me<00:11:04.440> if<00:11:04.560> you<00:11:04.680> want<00:11:04.880> to<00:11:05.440> follow<00:11:06.279> write 00:11:07.269 --> 00:11:07.279 align:start position:0% contact me if you want to follow write 00:11:07.279 --> 00:11:11.350 align:start position:0% contact me if you want to follow write send<00:11:07.800> issues<00:11:08.800> or<00:11:09.000> try<00:11:09.800> something<00:11:10.800> please<00:11:11.040> feel 00:11:11.350 --> 00:11:11.360 align:start position:0% send issues or try something please feel 00:11:11.360 --> 00:11:15.509 align:start position:0% send issues or try something please feel free<00:11:12.360> I<00:11:12.519> try<00:11:12.720> to<00:11:12.880> be<00:11:13.040> friendly<00:11:13.480> I<00:11:13.639> hope<00:11:13.880> I<00:11:13.959> will 00:11:15.509 --> 00:11:15.519 align:start position:0% free I try to be friendly I hope I will 00:11:15.519 --> 00:11:21.540 align:start position:0% free I try to be friendly I hope I will be<00:11:16.519> and<00:11:17.079> um<00:11:18.079> so<00:11:18.320> thank<00:11:18.440> you<00:11:18.600> very 00:11:21.540 --> 00:11:21.550 align:start position:0% 00:11:21.550 --> 00:11:25.829 align:start position:0% [Applause] 00:11:25.829 --> 00:11:25.839 align:start position:0% [Applause] 00:11:25.839 --> 00:11:31.069 align:start position:0% [Applause] much<00:11:26.839> are<00:11:27.000> there<00:11:27.240> any<00:11:27.519> questions 00:11:31.069 --> 00:11:31.079 align:start position:0% 00:11:31.079 --> 00:11:33.430 align:start position:0% how<00:11:31.320> tightly<00:11:31.639> are<00:11:31.720> you<00:11:31.839> bound<00:11:32.079> to<00:11:32.320> ethereum<00:11:32.839> J 00:11:33.430 --> 00:11:33.440 align:start position:0% how tightly are you bound to ethereum J 00:11:33.440 --> 00:11:35.389 align:start position:0% how tightly are you bound to ethereum J like<00:11:33.519> you<00:11:33.680> said<00:11:33.839> you<00:11:33.959> use<00:11:34.200> RPC<00:11:34.720> in<00:11:34.839> between 00:11:35.389 --> 00:11:35.399 align:start position:0% like you said you use RPC in between 00:11:35.399 --> 00:11:36.910 align:start position:0% like you said you use RPC in between like<00:11:35.680> because<00:11:35.959> there<00:11:36.040> is<00:11:36.200> no<00:11:36.480> light<00:11:36.680> light 00:11:36.910 --> 00:11:36.920 align:start position:0% like because there is no light light 00:11:36.920 --> 00:11:39.710 align:start position:0% like because there is no light light line<00:11:37.200> for<00:11:37.600> eum<00:11:38.519> yeah<00:11:38.639> so<00:11:38.880> right<00:11:39.079> now<00:11:39.480> it's 00:11:39.710 --> 00:11:39.720 align:start position:0% line for eum yeah so right now it's 00:11:39.720 --> 00:11:43.430 align:start position:0% line for eum yeah so right now it's working<00:11:40.200> mainly<00:11:40.480> on<00:11:40.639> eum<00:11:41.200> J<00:11:42.200> and<00:11:42.680> I<00:11:43.000> started 00:11:43.430 --> 00:11:43.440 align:start position:0% working mainly on eum J and I started 00:11:43.440 --> 00:11:46.790 align:start position:0% working mainly on eum J and I started our<00:11:43.760> Branch<00:11:44.079> to<00:11:44.279> work<00:11:44.560> with<00:11:44.720> a<00:11:44.959> w<00:11:45.480> web<00:11:45.800> 3j<00:11:46.680> which 00:11:46.790 --> 00:11:46.800 align:start position:0% our Branch to work with a w web 3j which 00:11:46.800 --> 00:11:50.310 align:start position:0% our Branch to work with a w web 3j which is<00:11:46.920> an<00:11:47.120> RPC<00:11:48.120> uh<00:11:48.360> implementation<00:11:49.000> in<00:11:49.200> Java<00:11:50.200> and 00:11:50.310 --> 00:11:50.320 align:start position:0% is an RPC uh implementation in Java and 00:11:50.320 --> 00:11:52.389 align:start position:0% is an RPC uh implementation in Java and the<00:11:50.480> idea<00:11:50.760> is<00:11:50.920> that<00:11:51.200> for<00:11:51.639> anyone<00:11:52.000> using<00:11:52.279> the 00:11:52.389 --> 00:11:52.399 align:start position:0% the idea is that for anyone using the 00:11:52.399 --> 00:11:54.990 align:start position:0% the idea is that for anyone using the library<00:11:52.959> shouldn't<00:11:53.440> make<00:11:53.639> any<00:11:53.880> difference<00:11:54.800> so 00:11:54.990 --> 00:11:55.000 align:start position:0% library shouldn't make any difference so 00:11:55.000 --> 00:11:58.030 align:start position:0% library shouldn't make any difference so they<00:11:55.120> can<00:11:55.360> still<00:11:55.639> use<00:11:56.079> this<00:11:57.079> interface<00:11:57.800> to 00:11:58.030 --> 00:11:58.040 align:start position:0% they can still use this interface to 00:11:58.040 --> 00:12:00.110 align:start position:0% they can still use this interface to talk<00:11:58.279> with<00:11:58.399> a<00:11:58.560> smart<00:11:58.800> contract 00:12:00.110 --> 00:12:00.120 align:start position:0% talk with a smart contract 00:12:00.120 --> 00:12:02.750 align:start position:0% talk with a smart contract just<00:12:00.720> it<00:12:01.320> just<00:12:01.480> so<00:12:01.760> happen<00:12:02.200> that<00:12:02.320> it<00:12:02.519> goes 00:12:02.750 --> 00:12:02.760 align:start position:0% just it just so happen that it goes 00:12:02.760 --> 00:12:05.269 align:start position:0% just it just so happen that it goes through<00:12:03.000> the<00:12:03.200> RPC<00:12:03.680> and<00:12:03.800> not<00:12:03.959> through<00:12:04.120> the<00:12:04.279> note 00:12:05.269 --> 00:12:05.279 align:start position:0% through the RPC and not through the note 00:12:05.279 --> 00:12:06.350 align:start position:0% through the RPC and not through the note so<00:12:05.480> of<00:12:05.600> course<00:12:05.760> there<00:12:05.880> will<00:12:06.040> be<00:12:06.160> some 00:12:06.350 --> 00:12:06.360 align:start position:0% so of course there will be some 00:12:06.360 --> 00:12:08.590 align:start position:0% so of course there will be some limitation<00:12:07.000> because<00:12:07.600> today<00:12:08.079> there<00:12:08.160> are<00:12:08.320> some 00:12:08.590 --> 00:12:08.600 align:start position:0% limitation because today there are some 00:12:08.600 --> 00:12:10.710 align:start position:0% limitation because today there are some stuff<00:12:08.920> that<00:12:09.040> are<00:12:09.200> not<00:12:09.399> coming<00:12:09.800> back<00:12:10.440> from<00:12:10.600> the 00:12:10.710 --> 00:12:10.720 align:start position:0% stuff that are not coming back from the 00:12:10.720 --> 00:12:13.910 align:start position:0% stuff that are not coming back from the RPC<00:12:11.240> for<00:12:11.399> example<00:12:11.720> the<00:12:12.040> return<00:12:12.399> value<00:12:13.160> is<00:12:13.399> not 00:12:13.910 --> 00:12:13.920 align:start position:0% RPC for example the return value is not 00:12:13.920 --> 00:12:16.670 align:start position:0% RPC for example the return value is not uh<00:12:14.600> available<00:12:15.560> if<00:12:15.720> it's<00:12:16.079> a<00:12:16.240> true<00:12:16.519> a 00:12:16.670 --> 00:12:16.680 align:start position:0% uh available if it's a true a 00:12:16.680 --> 00:12:18.350 align:start position:0% uh available if it's a true a transaction<00:12:17.160> with<00:12:17.320> the 00:12:18.350 --> 00:12:18.360 align:start position:0% transaction with the 00:12:18.360 --> 00:12:24.470 align:start position:0% transaction with the RPC<00:12:19.360> but<00:12:20.120> otherwise<00:12:20.880> it<00:12:20.959> would<00:12:21.160> be<00:12:21.320> totally 00:12:24.470 --> 00:12:24.480 align:start position:0% 00:12:24.480 --> 00:12:26.750 align:start position:0% transparent<00:12:25.480> do<00:12:25.560> you<00:12:25.760> use<00:12:25.920> it<00:12:26.079> in<00:12:26.360> production 00:12:26.750 --> 00:12:26.760 align:start position:0% transparent do you use it in production 00:12:26.760 --> 00:12:29.990 align:start position:0% transparent do you use it in production ckey<00:12:27.399> or<00:12:28.320> no<00:12:28.760> right<00:12:28.880> now<00:12:29.240> is<00:12:29.560> not<00:12:29.800> in 00:12:29.990 --> 00:12:30.000 align:start position:0% ckey or no right now is not in 00:12:30.000 --> 00:12:33.470 align:start position:0% ckey or no right now is not in production<00:12:30.680> but<00:12:31.560> hopefully<00:12:32.560> there<00:12:32.680> will<00:12:32.920> be<00:12:33.320> a 00:12:33.470 --> 00:12:33.480 align:start position:0% production but hopefully there will be a 00:12:33.480 --> 00:12:38.550 align:start position:0% production but hopefully there will be a lot<00:12:33.680> of<00:12:34.399> project<00:12:34.720> in 00:12:38.550 --> 00:12:38.560 align:start position:0% 00:12:38.560 --> 00:12:41.470 align:start position:0% production<00:12:39.560> so<00:12:39.760> no<00:12:40.240> it<00:12:40.720> it<00:12:40.839> is<00:12:40.959> written<00:12:41.279> in 00:12:41.470 --> 00:12:41.480 align:start position:0% production so no it it is written in 00:12:41.480 --> 00:12:45.350 align:start position:0% production so no it it is written in Java<00:12:42.079> the<00:12:42.279> reason<00:12:42.600> is<00:12:42.920> that<00:12:43.880> so<00:12:44.199> that<00:12:44.839> as<00:12:45.160> many 00:12:45.350 --> 00:12:45.360 align:start position:0% Java the reason is that so that as many 00:12:45.360 --> 00:12:47.310 align:start position:0% Java the reason is that so that as many people<00:12:45.639> as<00:12:45.800> possible<00:12:46.120> can<00:12:46.279> use<00:12:46.480> it<00:12:47.000> but<00:12:47.199> yeah 00:12:47.310 --> 00:12:47.320 align:start position:0% people as possible can use it but yeah 00:12:47.320 --> 00:12:49.310 align:start position:0% people as possible can use it but yeah I'm<00:12:47.399> a<00:12:47.519> Scala<00:12:47.800> L<00:12:48.079> if<00:12:48.240> I<00:12:48.440> could<00:12:48.680> have<00:12:49.000> written 00:12:49.310 --> 00:12:49.320 align:start position:0% I'm a Scala L if I could have written 00:12:49.320 --> 00:12:56.910 align:start position:0% I'm a Scala L if I could have written that<00:12:49.480> in<00:12:49.600> Scala<00:12:49.920> I<00:12:50.040> would 00:12:56.910 --> 00:12:56.920 align:start position:0% 00:12:56.920 --> 00:12:59.870 align:start position:0% have<00:12:57.920> okay 00:12:59.870 --> 00:12:59.880 align:start position:0% have okay 00:12:59.880 --> 00:13:03.750 align:start position:0% have okay yes<00:13:00.680> the<00:13:00.839> cont<00:13:01.600> interfaces<00:13:02.600> um<00:13:02.959> you<00:13:03.120> need<00:13:03.279> to 00:13:03.750 --> 00:13:03.760 align:start position:0% yes the cont interfaces um you need to 00:13:03.760 --> 00:13:06.949 align:start position:0% yes the cont interfaces um you need to provide<00:13:04.120> them<00:13:04.399> or<00:13:04.639> is<00:13:05.440> the<00:13:05.600> system<00:13:06.240> capable<00:13:06.720> of 00:13:06.949 --> 00:13:06.959 align:start position:0% provide them or is the system capable of 00:13:06.959 --> 00:13:09.069 align:start position:0% provide them or is the system capable of of<00:13:07.160> generating<00:13:08.120> so<00:13:08.240> you<00:13:08.360> have<00:13:08.480> to<00:13:08.680> provide 00:13:09.069 --> 00:13:09.079 align:start position:0% of generating so you have to provide 00:13:09.079 --> 00:13:11.949 align:start position:0% of generating so you have to provide them<00:13:09.519> the<00:13:09.959> the<00:13:10.079> main<00:13:10.360> reason<00:13:11.279> it<00:13:11.440> is<00:13:11.600> done<00:13:11.800> like 00:13:11.949 --> 00:13:11.959 align:start position:0% them the the main reason it is done like 00:13:11.959 --> 00:13:13.750 align:start position:0% them the the main reason it is done like that<00:13:12.120> for<00:13:12.279> example<00:13:12.600> web<00:13:12.800> 3j<00:13:13.440> they<00:13:13.600> have 00:13:13.750 --> 00:13:13.760 align:start position:0% that for example web 3j they have 00:13:13.760 --> 00:13:16.430 align:start position:0% that for example web 3j they have generators<00:13:14.360> to<00:13:14.480> do<00:13:14.720> that<00:13:15.600> the<00:13:15.760> reason<00:13:16.240> I 00:13:16.430 --> 00:13:16.440 align:start position:0% generators to do that the reason I 00:13:16.440 --> 00:13:18.710 align:start position:0% generators to do that the reason I prefer<00:13:16.839> that<00:13:17.079> you<00:13:17.600> define<00:13:18.000> them<00:13:18.240> is<00:13:18.399> that<00:13:18.560> you 00:13:18.710 --> 00:13:18.720 align:start position:0% prefer that you define them is that you 00:13:18.720 --> 00:13:21.509 align:start position:0% prefer that you define them is that you can<00:13:19.120> Define<00:13:19.639> what<00:13:19.839> kind<00:13:20.040> of<00:13:20.880> value<00:13:21.199> you 00:13:21.509 --> 00:13:21.519 align:start position:0% can Define what kind of value you 00:13:21.519 --> 00:13:23.150 align:start position:0% can Define what kind of value you expecting<00:13:22.000> and<00:13:22.120> then<00:13:22.279> the<00:13:22.399> conversion<00:13:22.839> will 00:13:23.150 --> 00:13:23.160 align:start position:0% expecting and then the conversion will 00:13:23.160 --> 00:13:25.509 align:start position:0% expecting and then the conversion will take<00:13:23.480> place<00:13:24.199> that<00:13:24.399> when<00:13:24.519> it's<00:13:24.680> generating<00:13:25.360> you 00:13:25.509 --> 00:13:25.519 align:start position:0% take place that when it's generating you 00:13:25.519 --> 00:13:27.110 align:start position:0% take place that when it's generating you you 00:13:27.110 --> 00:13:27.120 align:start position:0% you 00:13:27.120 --> 00:13:29.790 align:start position:0% you cannot<00:13:28.120> so<00:13:28.360> are<00:13:28.519> you<00:13:28.720> basically<00:13:29.320> implementing 00:13:29.790 --> 00:13:29.800 align:start position:0% cannot so are you basically implementing 00:13:29.800 --> 00:13:32.550 align:start position:0% cannot so are you basically implementing on<00:13:30.040> ethereum<00:13:30.800> what<00:13:31.240> Lisk<00:13:31.639> is<00:13:31.880> doing<00:13:32.199> on<00:13:32.399> their 00:13:32.550 --> 00:13:32.560 align:start position:0% on ethereum what Lisk is doing on their 00:13:32.560 --> 00:13:34.470 align:start position:0% on ethereum what Lisk is doing on their own<00:13:32.839> blockchain<00:13:33.360> or<00:13:33.600> how<00:13:33.880> does<00:13:34.000> it 00:13:34.470 --> 00:13:34.480 align:start position:0% own blockchain or how does it 00:13:34.480 --> 00:13:37.550 align:start position:0% own blockchain or how does it differentiate<00:13:35.480> no<00:13:35.760> not<00:13:35.959> really<00:13:36.320> because<00:13:36.760> here 00:13:37.550 --> 00:13:37.560 align:start position:0% differentiate no not really because here 00:13:37.560 --> 00:13:40.670 align:start position:0% differentiate no not really because here solidity<00:13:38.199> is<00:13:38.399> still<00:13:39.320> here<00:13:39.920> I<00:13:39.959> mean<00:13:40.240> on<00:13:40.440> the 00:13:40.670 --> 00:13:40.680 align:start position:0% solidity is still here I mean on the 00:13:40.680 --> 00:13:44.269 align:start position:0% solidity is still here I mean on the ethereum<00:13:41.320> part<00:13:42.120> I<00:13:42.360> haven't<00:13:42.920> changed<00:13:43.399> anything 00:13:44.269 --> 00:13:44.279 align:start position:0% ethereum part I haven't changed anything 00:13:44.279 --> 00:13:46.550 align:start position:0% ethereum part I haven't changed anything here<00:13:44.440> is<00:13:44.600> the<00:13:44.760> integration<00:13:45.399> part<00:13:45.639> that<00:13:45.760> is 00:13:46.550 --> 00:13:46.560 align:start position:0% here is the integration part that is 00:13:46.560 --> 00:13:49.910 align:start position:0% here is the integration part that is different<00:13:47.560> let's<00:13:47.760> say<00:13:48.000> that<00:13:48.680> it's<00:13:49.040> more<00:13:49.560> an 00:13:49.910 --> 00:13:49.920 align:start position:0% different let's say that it's more an 00:13:49.920 --> 00:13:53.829 align:start position:0% different let's say that it's more an alternative<00:13:50.519> to<00:13:50.759> web<00:13:51.000> 3js<00:13:51.839> kind<00:13:52.079> of<00:13:53.079> today 00:13:53.829 --> 00:13:53.839 align:start position:0% alternative to web 3js kind of today 00:13:53.839 --> 00:13:56.350 align:start position:0% alternative to web 3js kind of today usually<00:13:54.519> people<00:13:54.839> will<00:13:55.160> integrate<00:13:55.600> with<00:13:55.839> that 00:13:56.350 --> 00:13:56.360 align:start position:0% usually people will integrate with that 00:13:56.360 --> 00:13:59.749 align:start position:0% usually people will integrate with that and<00:13:56.519> here<00:13:56.680> it's<00:13:56.880> another<00:13:57.199> way<00:13:57.399> in<00:13:57.880> Java<00:13:58.880> that 00:13:59.749 --> 00:13:59.759 align:start position:0% and here it's another way in Java that 00:13:59.759 --> 00:14:01.350 align:start position:0% and here it's another way in Java that I<00:13:59.880> think<00:14:00.120> is<00:14:00.320> also<00:14:00.600> nice<00:14:00.839> because<00:14:01.079> you<00:14:01.199> have 00:14:01.350 --> 00:14:01.360 align:start position:0% I think is also nice because you have 00:14:01.360 --> 00:14:04.069 align:start position:0% I think is also nice because you have all<00:14:01.519> the<00:14:01.720> J<00:14:02.240> like<00:14:02.519> the<00:14:03.440> you<00:14:03.560> are<00:14:03.720> in<00:14:03.880> your 00:14:04.069 --> 00:14:04.079 align:start position:0% all the J like the you are in your 00:14:04.079 --> 00:14:05.710 align:start position:0% all the J like the you are in your environment<00:14:04.560> with<00:14:04.720> the<00:14:04.959> type<00:14:05.240> system<00:14:05.600> that 00:14:05.710 --> 00:14:05.720 align:start position:0% environment with the type system that 00:14:05.720 --> 00:14:16.389 align:start position:0% environment with the type system that you<00:14:05.839> don't<00:14:06.000> have 00:14:16.389 --> 00:14:16.399 align:start position:0% 00:14:16.399 --> 00:14:20.509 align:start position:0% 3js<00:14:17.399> what<00:14:17.600> what<00:14:17.839> what<00:14:18.560> on 00:14:20.509 --> 00:14:20.519 align:start position:0% 3js what what what on 00:14:20.519 --> 00:14:26.629 align:start position:0% 3js what what what on the<00:14:21.519> uh<00:14:21.759> yes<00:14:22.639> uh<00:14:22.920> there<00:14:23.199> a<00:14:23.839> meod<00:14:24.600> cont 00:14:26.629 --> 00:14:26.639 align:start position:0% the uh yes uh there a meod cont 00:14:26.639 --> 00:14:29.230 align:start position:0% the uh yes uh there a meod cont and<00:14:27.639> the 00:14:29.230 --> 00:14:29.240 align:start position:0% and the 00:14:29.240 --> 00:14:31.710 align:start position:0% and the uh<00:14:29.360> so<00:14:29.639> here<00:14:29.880> it's<00:14:30.160> just<00:14:30.320> an<00:14:30.519> example<00:14:31.519> because 00:14:31.710 --> 00:14:31.720 align:start position:0% uh so here it's just an example because 00:14:31.720 --> 00:14:34.230 align:start position:0% uh so here it's just an example because I'm<00:14:31.880> working<00:14:32.120> on<00:14:32.920> this<00:14:33.360> decentralized<00:14:34.040> app 00:14:34.230 --> 00:14:34.240 align:start position:0% I'm working on this decentralized app 00:14:34.240 --> 00:14:36.590 align:start position:0% I'm working on this decentralized app store<00:14:35.079> and<00:14:35.240> the<00:14:35.360> idea<00:14:35.600> is<00:14:35.720> that<00:14:35.920> you<00:14:36.040> have<00:14:36.199> your 00:14:36.590 --> 00:14:36.600 align:start position:0% store and the idea is that you have your 00:14:36.600 --> 00:14:38.550 align:start position:0% store and the idea is that you have your organization<00:14:37.399> you<00:14:37.519> can<00:14:37.759> publish<00:14:38.240> publish 00:14:38.550 --> 00:14:38.560 align:start position:0% organization you can publish publish 00:14:38.560 --> 00:14:41.150 align:start position:0% organization you can publish publish their<00:14:38.920> way<00:14:39.079> to<00:14:39.360> get<00:14:39.600> it<00:14:40.360> so<00:14:40.600> here<00:14:40.759> would<00:14:40.959> be 00:14:41.150 --> 00:14:41.160 align:start position:0% their way to get it so here would be 00:14:41.160 --> 00:14:45.350 align:start position:0% their way to get it so here would be like<00:14:41.440> the<00:14:42.160> sorry<00:14:43.160> the<00:14:43.320> HTTP<00:14:44.120> like<00:14:44.240> the<00:14:44.680> URL<00:14:45.160> to 00:14:45.350 --> 00:14:45.360 align:start position:0% like the sorry the HTTP like the URL to 00:14:45.360 --> 00:14:47.590 align:start position:0% like the sorry the HTTP like the URL to download<00:14:45.839> the<00:14:46.120> application<00:14:47.120> the<00:14:47.240> idea<00:14:47.480> is 00:14:47.590 --> 00:14:47.600 align:start position:0% download the application the idea is 00:14:47.600 --> 00:14:50.430 align:start position:0% download the application the idea is that<00:14:47.720> you<00:14:48.000> can<00:14:49.000> you<00:14:49.079> can<00:14:49.279> put<00:14:49.519> HB<00:14:50.120> and<00:14:50.199> then<00:14:50.320> you 00:14:50.430 --> 00:14:50.440 align:start position:0% that you can you can put HB and then you 00:14:50.440 --> 00:14:52.870 align:start position:0% that you can you can put HB and then you could<00:14:50.600> put<00:14:50.839> ipfs<00:14:51.480> you<00:14:51.600> can<00:14:51.759> put<00:14:52.000> P<00:14:52.600> whatever 00:14:52.870 --> 00:14:52.880 align:start position:0% could put ipfs you can put P whatever 00:14:52.880 --> 00:14:54.990 align:start position:0% could put ipfs you can put P whatever you<00:14:52.959> want<00:14:53.800> but<00:14:53.920> it's<00:14:54.120> always<00:14:54.399> the<00:14:54.519> same<00:14:54.759> check 00:14:54.990 --> 00:14:55.000 align:start position:0% you want but it's always the same check 00:14:55.000 --> 00:14:57.629 align:start position:0% you want but it's always the same check s<00:14:55.240> to<00:14:55.399> make<00:14:55.519> sure<00:14:55.800> that<00:14:56.720> we're<00:14:57.000> talking<00:14:57.360> always 00:14:57.629 --> 00:14:57.639 align:start position:0% s to make sure that we're talking always 00:14:57.639 --> 00:15:02.749 align:start position:0% s to make sure that we're talking always about<00:14:57.920> the<00:14:58.079> same<00:14:58.639> uh<00:14:59.240> the<00:14:59.440> same 00:15:02.749 --> 00:15:02.759 align:start position:0% 00:15:02.759 --> 00:15:06.710 align:start position:0% B 00:15:06.710 --> 00:15:06.720 align:start position:0% 00:15:06.720 --> 00:15:09.910 align:start position:0% yes<00:15:07.720> the<00:15:07.880> node<00:15:08.240> which<00:15:08.399> is<00:15:08.600> connected<00:15:09.160> is<00:15:09.440> is<00:15:09.639> an 00:15:09.910 --> 00:15:09.920 align:start position:0% yes the node which is connected is is an 00:15:09.920 --> 00:15:13.389 align:start position:0% yes the node which is connected is is an LPC<00:15:10.480> node<00:15:11.480> so<00:15:11.800> the<00:15:12.079> so<00:15:12.279> the<00:15:12.440> question<00:15:12.720> is<00:15:13.120> about 00:15:13.389 --> 00:15:13.399 align:start position:0% LPC node so the so the question is about 00:15:13.399 --> 00:15:17.350 align:start position:0% LPC node so the so the question is about the<00:15:13.560> nodes<00:15:14.279> it<00:15:14.560> the<00:15:14.720> the<00:15:14.880> back<00:15:15.360> end<00:15:16.360> is<00:15:17.240> the 00:15:17.350 --> 00:15:17.360 align:start position:0% the nodes it the the back end is the 00:15:17.360 --> 00:15:19.230 align:start position:0% the nodes it the the back end is the idea<00:15:17.600> is<00:15:17.680> that<00:15:18.079> the<00:15:18.199> back<00:15:18.320> end<00:15:18.519> is<00:15:18.680> abstracted 00:15:19.230 --> 00:15:19.240 align:start position:0% idea is that the back end is abstracted 00:15:19.240 --> 00:15:22.670 align:start position:0% idea is that the back end is abstracted away<00:15:19.680> so<00:15:20.240> the<00:15:20.399> back<00:15:20.560> end<00:15:20.800> can<00:15:20.959> be<00:15:21.399> RPC<00:15:22.399> if<00:15:22.519> you 00:15:22.670 --> 00:15:22.680 align:start position:0% away so the back end can be RPC if you 00:15:22.680 --> 00:15:25.470 align:start position:0% away so the back end can be RPC if you choose<00:15:23.040> it<00:15:23.199> to<00:15:23.360> be<00:15:24.000> but<00:15:24.360> to<00:15:24.560> for<00:15:24.720> example<00:15:25.079> today 00:15:25.470 --> 00:15:25.480 align:start position:0% choose it to be but to for example today 00:15:25.480 --> 00:15:28.829 align:start position:0% choose it to be but to for example today it's<00:15:25.720> an<00:15:26.040> actual<00:15:26.399> node<00:15:27.399> using<00:15:27.720> eum<00:15:28.160> J<00:15:28.600> so<00:15:28.759> you 00:15:28.829 --> 00:15:28.839 align:start position:0% it's an actual node using eum J so you 00:15:28.839 --> 00:15:30.670 align:start position:0% it's an actual node using eum J so you have<00:15:29.040> an<00:15:29.160> actual<00:15:29.480> node<00:15:29.839> that<00:15:30.000> is<00:15:30.160> sying 00:15:30.670 --> 00:15:30.680 align:start position:0% have an actual node that is sying 00:15:30.680 --> 00:15:33.509 align:start position:0% have an actual node that is sying locally<00:15:31.680> but<00:15:31.800> you<00:15:31.920> can<00:15:32.160> choose<00:15:32.720> which<00:15:32.920> one<00:15:33.160> you 00:15:33.509 --> 00:15:33.519 align:start position:0% locally but you can choose which one you 00:15:33.519 --> 00:15:38.240 align:start position:0% locally but you can choose which one you want<00:15:34.519> depending<00:15:34.920> on<00:15:35.040> your<00:15:35.240> needs