WEBVTT Kind: captions Language: en 00:00:00.000 --> 00:00:04.350 align:start position:0% foreign 00:00:04.350 --> 00:00:04.360 align:start position:0% 00:00:04.360 --> 00:00:13.930 align:start position:0% [Music] 00:00:13.930 --> 00:00:13.940 align:start position:0% 00:00:13.940 --> 00:00:17.630 align:start position:0% driving<00:00:14.940> principles<00:00:15.980> behind<00:00:16.980> development 00:00:17.630 --> 00:00:17.640 align:start position:0% driving principles behind development 00:00:17.640 --> 00:00:18.710 align:start position:0% driving principles behind development Road<00:00:17.940> key 00:00:18.710 --> 00:00:18.720 align:start position:0% Road key 00:00:18.720 --> 00:00:22.490 align:start position:0% Road key so<00:00:19.680> let's<00:00:19.920> start<00:00:20.160> so<00:00:20.820> who<00:00:21.060> am<00:00:21.240> I<00:00:21.420> I<00:00:22.080> have<00:00:22.320> been 00:00:22.490 --> 00:00:22.500 align:start position:0% so let's start so who am I I have been 00:00:22.500 --> 00:00:25.490 align:start position:0% so let's start so who am I I have been doing<00:00:22.880> application<00:00:23.880> development<00:00:24.500> local 00:00:25.490 --> 00:00:25.500 align:start position:0% doing application development local 00:00:25.500 --> 00:00:29.150 align:start position:0% doing application development local mobile<00:00:26.160> and<00:00:26.760> web<00:00:27.180> since<00:00:27.720> 2010<00:00:28.380> most<00:00:28.920> of<00:00:29.099> the 00:00:29.150 --> 00:00:29.160 align:start position:0% mobile and web since 2010 most of the 00:00:29.160 --> 00:00:31.370 align:start position:0% mobile and web since 2010 most of the time<00:00:29.340> of<00:00:29.820> the<00:00:30.060> most<00:00:30.300> the<00:00:30.480> time<00:00:30.660> of<00:00:30.779> this<00:00:30.960> was 00:00:31.370 --> 00:00:31.380 align:start position:0% time of the most the time of this was 00:00:31.380 --> 00:00:33.950 align:start position:0% time of the most the time of this was doing<00:00:31.679> open<00:00:31.859> source<00:00:32.399> and<00:00:33.120> have<00:00:33.360> I<00:00:33.600> have<00:00:33.719> been 00:00:33.950 --> 00:00:33.960 align:start position:0% doing open source and have I have been 00:00:33.960 --> 00:00:38.030 align:start position:0% doing open source and have I have been the<00:00:34.140> erotic<00:00:34.980> contributor<00:00:35.520> since<00:00:35.700> 2018 00:00:38.030 --> 00:00:38.040 align:start position:0% 00:00:38.040 --> 00:00:40.209 align:start position:0% um handling<00:00:38.579> parts<00:00:39.000> of<00:00:39.300> the<00:00:39.780> front-end 00:00:40.209 --> 00:00:40.219 align:start position:0% um handling parts of the front-end 00:00:40.219 --> 00:00:43.069 align:start position:0% um handling parts of the front-end infrastructure<00:00:41.219> packaging<00:00:41.820> so<00:00:42.480> what<00:00:42.780> you<00:00:42.899> do 00:00:43.069 --> 00:00:43.079 align:start position:0% infrastructure packaging so what you do 00:00:43.079 --> 00:00:45.650 align:start position:0% infrastructure packaging so what you do in<00:00:43.200> startup<00:00:43.680> pretty<00:00:44.399> much<00:00:44.640> touching<00:00:45.300> all<00:00:45.480> over 00:00:45.650 --> 00:00:45.660 align:start position:0% in startup pretty much touching all over 00:00:45.660 --> 00:00:49.569 align:start position:0% in startup pretty much touching all over uh<00:00:46.079> the<00:00:46.500> code<00:00:46.559> base 00:00:49.569 --> 00:00:49.579 align:start position:0% 00:00:49.579 --> 00:00:52.310 align:start position:0% so<00:00:50.579> let's<00:00:50.700> start<00:00:50.879> with<00:00:51.059> the<00:00:51.239> problem<00:00:51.360> today 00:00:52.310 --> 00:00:52.320 align:start position:0% so let's start with the problem today 00:00:52.320 --> 00:00:55.310 align:start position:0% so let's start with the problem today the<00:00:52.559> problem<00:00:52.800> today<00:00:53.160> is<00:00:53.640> that<00:00:54.020> we<00:00:55.020> don't<00:00:55.140> have 00:00:55.310 --> 00:00:55.320 align:start position:0% the problem today is that we don't have 00:00:55.320 --> 00:00:56.869 align:start position:0% the problem today is that we don't have enough<00:00:55.440> decentralization 00:00:56.869 --> 00:00:56.879 align:start position:0% enough decentralization 00:00:56.879 --> 00:00:59.510 align:start position:0% enough decentralization a<00:00:57.120> lot<00:00:57.239> of<00:00:57.360> the<00:00:57.480> software<00:00:57.719> we<00:00:57.899> use<00:00:58.320> daily<00:00:58.559> is<00:00:59.160> uh 00:00:59.510 --> 00:00:59.520 align:start position:0% a lot of the software we use daily is uh 00:00:59.520 --> 00:01:02.810 align:start position:0% a lot of the software we use daily is uh closers<00:01:00.199> it<00:01:01.199> runs<00:01:01.500> some<00:01:01.559> data<00:01:01.920> centers 00:01:02.810 --> 00:01:02.820 align:start position:0% closers it runs some data centers 00:01:02.820 --> 00:01:05.630 align:start position:0% closers it runs some data centers and<00:01:03.660> there<00:01:04.080> you<00:01:04.440> don't<00:01:04.619> have<00:01:04.860> ownership<00:01:05.339> or 00:01:05.630 --> 00:01:05.640 align:start position:0% and there you don't have ownership or 00:01:05.640 --> 00:01:07.850 align:start position:0% and there you don't have ownership or control<00:01:05.880> of<00:01:06.119> your<00:01:06.240> data<00:01:06.600> they<00:01:07.320> can<00:01:07.439> use<00:01:07.560> it<00:01:07.680> to 00:01:07.850 --> 00:01:07.860 align:start position:0% control of your data they can use it to 00:01:07.860 --> 00:01:10.969 align:start position:0% control of your data they can use it to train<00:01:08.040> muscle<00:01:08.520> learning<00:01:09.060> algorithms 00:01:10.969 --> 00:01:10.979 align:start position:0% train muscle learning algorithms 00:01:10.979 --> 00:01:13.609 align:start position:0% train muscle learning algorithms use<00:01:11.820> it<00:01:12.000> for<00:01:12.180> whatever<00:01:12.360> reason<00:01:13.020> there<00:01:13.380> is<00:01:13.500> no 00:01:13.609 --> 00:01:13.619 align:start position:0% use it for whatever reason there is no 00:01:13.619 --> 00:01:15.649 align:start position:0% use it for whatever reason there is no transparency<00:01:14.100> and<00:01:14.400> you<00:01:14.520> have<00:01:14.640> to<00:01:14.760> trust 00:01:15.649 --> 00:01:15.659 align:start position:0% transparency and you have to trust 00:01:15.659 --> 00:01:19.850 align:start position:0% transparency and you have to trust that<00:01:16.200> they<00:01:16.320> use<00:01:16.560> it<00:01:16.740> as<00:01:17.340> they<00:01:17.520> claim<00:01:18.299> uh 00:01:19.850 --> 00:01:19.860 align:start position:0% that they use it as they claim uh 00:01:19.860 --> 00:01:21.109 align:start position:0% that they use it as they claim uh they<00:01:20.340> might<00:01:20.460> claim<00:01:20.700> that<00:01:20.820> they<00:01:20.939> have 00:01:21.109 --> 00:01:21.119 align:start position:0% they might claim that they have 00:01:21.119 --> 00:01:23.510 align:start position:0% they might claim that they have encryption<00:01:21.600> but<00:01:22.200> you<00:01:22.380> don't<00:01:22.619> have<00:01:22.860> any<00:01:23.159> way<00:01:23.400> to 00:01:23.510 --> 00:01:23.520 align:start position:0% encryption but you don't have any way to 00:01:23.520 --> 00:01:26.030 align:start position:0% encryption but you don't have any way to verify<00:01:23.880> that<00:01:24.060> there<00:01:24.180> is<00:01:24.299> no<00:01:24.420> master<00:01:24.659> key<00:01:25.040> and 00:01:26.030 --> 00:01:26.040 align:start position:0% verify that there is no master key and 00:01:26.040 --> 00:01:29.690 align:start position:0% verify that there is no master key and there<00:01:26.220> is<00:01:26.400> no<00:01:26.640> way<00:01:27.420> to<00:01:27.960> be<00:01:28.140> sure<00:01:28.320> that<00:01:28.680> all<00:01:29.460> the 00:01:29.690 --> 00:01:29.700 align:start position:0% there is no way to be sure that all the 00:01:29.700 --> 00:01:32.810 align:start position:0% there is no way to be sure that all the claims<00:01:29.939> are<00:01:30.119> true<00:01:30.299> then<00:01:31.080> your<00:01:31.320> data<00:01:31.680> can<00:01:31.860> leak 00:01:32.810 --> 00:01:32.820 align:start position:0% claims are true then your data can leak 00:01:32.820 --> 00:01:35.210 align:start position:0% claims are true then your data can leak this<00:01:33.479> can<00:01:33.600> happen<00:01:33.780> with<00:01:34.259> different<00:01:34.500> ways<00:01:34.920> like 00:01:35.210 --> 00:01:35.220 align:start position:0% this can happen with different ways like 00:01:35.220 --> 00:01:38.630 align:start position:0% this can happen with different ways like for<00:01:35.640> example<00:01:35.880> accidents<00:01:36.900> and<00:01:37.799> in<00:01:37.979> turn<00:01:38.159> go<00:01:38.460> to 00:01:38.630 --> 00:01:38.640 align:start position:0% for example accidents and in turn go to 00:01:38.640 --> 00:01:40.730 align:start position:0% for example accidents and in turn go to much<00:01:38.880> success<00:01:39.299> uh<00:01:39.900> didn't<00:01:40.200> know<00:01:40.380> what<00:01:40.560> they 00:01:40.730 --> 00:01:40.740 align:start position:0% much success uh didn't know what they 00:01:40.740 --> 00:01:43.130 align:start position:0% much success uh didn't know what they were<00:01:40.920> doing<00:01:41.299> and<00:01:42.299> all<00:01:42.659> your<00:01:42.840> private 00:01:43.130 --> 00:01:43.140 align:start position:0% were doing and all your private 00:01:43.140 --> 00:01:47.270 align:start position:0% were doing and all your private information<00:01:43.259> is<00:01:43.740> public<00:01:44.040> or<00:01:44.880> hacks<00:01:45.860> uh<00:01:46.860> or 00:01:47.270 --> 00:01:47.280 align:start position:0% information is public or hacks uh or 00:01:47.280 --> 00:01:49.850 align:start position:0% information is public or hacks uh or some<00:01:47.880> companies<00:01:48.240> just<00:01:48.540> outright<00:01:49.140> sell<00:01:49.320> data 00:01:49.850 --> 00:01:49.860 align:start position:0% some companies just outright sell data 00:01:49.860 --> 00:01:51.950 align:start position:0% some companies just outright sell data uh<00:01:50.520> there<00:01:50.700> was<00:01:50.880> a<00:01:51.000> nice<00:01:51.180> John<00:01:51.360> Oliver<00:01:51.659> episode 00:01:51.950 --> 00:01:51.960 align:start position:0% uh there was a nice John Oliver episode 00:01:51.960 --> 00:01:53.810 align:start position:0% uh there was a nice John Oliver episode about<00:01:52.200> data<00:01:52.560> Brokers<00:01:52.860> that<00:01:53.100> was<00:01:53.280> really<00:01:53.579> scary 00:01:53.810 --> 00:01:53.820 align:start position:0% about data Brokers that was really scary 00:01:53.820 --> 00:01:55.910 align:start position:0% about data Brokers that was really scary on<00:01:54.420> how<00:01:54.659> much<00:01:54.780> information<00:01:55.020> they<00:01:55.619> could<00:01:55.740> get 00:01:55.910 --> 00:01:55.920 align:start position:0% on how much information they could get 00:01:55.920 --> 00:01:57.789 align:start position:0% on how much information they could get about<00:01:56.100> people<00:01:56.399> even<00:01:57.000> sensitive<00:01:57.540> information 00:01:57.789 --> 00:01:57.799 align:start position:0% about people even sensitive information 00:01:57.799 --> 00:02:02.090 align:start position:0% about people even sensitive information like<00:01:58.799> healthcare<00:01:59.399> and<00:02:00.360> uh<00:02:00.780> the<00:02:01.619> exact<00:02:01.860> point 00:02:02.090 --> 00:02:02.100 align:start position:0% like healthcare and uh the exact point 00:02:02.100 --> 00:02:04.969 align:start position:0% like healthcare and uh the exact point where<00:02:02.340> people<00:02:02.520> uh<00:02:03.060> were<00:02:03.420> living 00:02:04.969 --> 00:02:04.979 align:start position:0% where people uh were living 00:02:04.979 --> 00:02:06.469 align:start position:0% where people uh were living um<00:02:05.040> then<00:02:05.460> other<00:02:05.700> problems<00:02:06.060> are<00:02:06.240> that 00:02:06.469 --> 00:02:06.479 align:start position:0% um then other problems are that 00:02:06.479 --> 00:02:08.389 align:start position:0% um then other problems are that companies<00:02:06.960> can<00:02:07.140> go<00:02:07.259> out<00:02:07.380> of<00:02:07.500> business<00:02:07.680> and 00:02:08.389 --> 00:02:08.399 align:start position:0% companies can go out of business and 00:02:08.399 --> 00:02:10.249 align:start position:0% companies can go out of business and then<00:02:08.640> basically<00:02:09.420> you<00:02:09.539> lose<00:02:09.720> access<00:02:09.899> to<00:02:10.140> all 00:02:10.249 --> 00:02:10.259 align:start position:0% then basically you lose access to all 00:02:10.259 --> 00:02:12.710 align:start position:0% then basically you lose access to all your<00:02:10.440> data<00:02:10.879> another<00:02:11.879> problem<00:02:12.120> can<00:02:12.420> be<00:02:12.540> that 00:02:12.710 --> 00:02:12.720 align:start position:0% your data another problem can be that 00:02:12.720 --> 00:02:14.270 align:start position:0% your data another problem can be that they<00:02:12.840> come<00:02:13.020> to<00:02:13.140> platform<00:02:13.500> you<00:02:13.680> uh<00:02:14.099> something 00:02:14.270 --> 00:02:14.280 align:start position:0% they come to platform you uh something 00:02:14.280 --> 00:02:15.229 align:start position:0% they come to platform you uh something happens 00:02:15.229 --> 00:02:15.239 align:start position:0% happens 00:02:15.239 --> 00:02:18.170 align:start position:0% happens your<00:02:15.840> account<00:02:15.959> is<00:02:16.260> locked<00:02:16.680> and<00:02:17.340> then<00:02:17.580> put<00:02:17.940> for 00:02:18.170 --> 00:02:18.180 align:start position:0% your account is locked and then put for 00:02:18.180 --> 00:02:19.670 align:start position:0% your account is locked and then put for your<00:02:18.360> data<00:02:18.780> is<00:02:18.900> gone 00:02:19.670 --> 00:02:19.680 align:start position:0% your data is gone 00:02:19.680 --> 00:02:23.330 align:start position:0% your data is gone uh<00:02:20.340> we<00:02:20.700> can<00:02:20.879> see<00:02:21.060> some<00:02:21.420> examples 00:02:23.330 --> 00:02:23.340 align:start position:0% uh we can see some examples 00:02:23.340 --> 00:02:26.270 align:start position:0% uh we can see some examples so<00:02:23.879> for<00:02:24.120> example<00:02:24.360> uh<00:02:24.980> deeper<00:02:25.980> started 00:02:26.270 --> 00:02:26.280 align:start position:0% so for example uh deeper started 00:02:26.280 --> 00:02:28.250 align:start position:0% so for example uh deeper started blocking<00:02:26.700> all<00:02:27.000> the<00:02:27.120> Russian<00:02:27.420> users<00:02:27.780> so 00:02:28.250 --> 00:02:28.260 align:start position:0% blocking all the Russian users so 00:02:28.260 --> 00:02:29.390 align:start position:0% blocking all the Russian users so basically<00:02:28.560> they<00:02:28.680> lost<00:02:28.860> access<00:02:29.040> to<00:02:29.280> their 00:02:29.390 --> 00:02:29.400 align:start position:0% basically they lost access to their 00:02:29.400 --> 00:02:30.490 align:start position:0% basically they lost access to their funds 00:02:30.490 --> 00:02:30.500 align:start position:0% funds 00:02:30.500 --> 00:02:32.930 align:start position:0% funds then<00:02:31.500> we<00:02:31.739> had<00:02:31.920> the<00:02:32.040> case<00:02:32.160> of<00:02:32.340> snapshot<00:02:32.760> where 00:02:32.930 --> 00:02:32.940 align:start position:0% then we had the case of snapshot where 00:02:32.940 --> 00:02:36.290 align:start position:0% then we had the case of snapshot where employees<00:02:33.360> were<00:02:33.540> abusing<00:02:34.020> uh<00:02:34.680> data<00:02:35.280> access<00:02:35.400> to 00:02:36.290 --> 00:02:36.300 align:start position:0% employees were abusing uh data access to 00:02:36.300 --> 00:02:37.910 align:start position:0% employees were abusing uh data access to justify<00:02:36.660> on<00:02:36.959> users 00:02:37.910 --> 00:02:37.920 align:start position:0% justify on users 00:02:37.920 --> 00:02:40.729 align:start position:0% justify on users and<00:02:38.580> as<00:02:39.000> we<00:02:39.180> saw<00:02:39.360> like<00:02:39.660> uber<00:02:40.080> was<00:02:40.319> hacked 00:02:40.729 --> 00:02:40.739 align:start position:0% and as we saw like uber was hacked 00:02:40.739 --> 00:02:43.190 align:start position:0% and as we saw like uber was hacked recently<00:02:41.099> by<00:02:41.819> a<00:02:41.940> teenager 00:02:43.190 --> 00:02:43.200 align:start position:0% recently by a teenager 00:02:43.200 --> 00:02:47.809 align:start position:0% recently by a teenager so<00:02:44.060> it's<00:02:45.060> easy<00:02:45.360> to<00:02:45.900> you<00:02:46.440> know<00:02:46.500> if<00:02:47.459> your<00:02:47.640> public 00:02:47.809 --> 00:02:47.819 align:start position:0% so it's easy to you know if your public 00:02:47.819 --> 00:02:49.910 align:start position:0% so it's easy to you know if your public information<00:02:48.060> goes<00:02:48.660> out<00:02:48.780> then<00:02:49.440> there<00:02:49.620> is<00:02:49.800> no 00:02:49.910 --> 00:02:49.920 align:start position:0% information goes out then there is no 00:02:49.920 --> 00:02:50.990 align:start position:0% information goes out then there is no way<00:02:50.099> back 00:02:50.990 --> 00:02:51.000 align:start position:0% way back 00:02:51.000 --> 00:02:53.509 align:start position:0% way back uh<00:02:51.780> then<00:02:52.019> we<00:02:52.260> had<00:02:52.379> the<00:02:52.560> leather<00:02:52.860> hack<00:02:53.099> like 00:02:53.509 --> 00:02:53.519 align:start position:0% uh then we had the leather hack like 00:02:53.519 --> 00:02:55.369 align:start position:0% uh then we had the leather hack like people<00:02:53.940> were<00:02:54.300> receiving<00:02:54.660> mail<00:02:54.959> at<00:02:55.260> their 00:02:55.369 --> 00:02:55.379 align:start position:0% people were receiving mail at their 00:02:55.379 --> 00:02:57.350 align:start position:0% people were receiving mail at their homes<00:02:55.620> which<00:02:56.160> can<00:02:56.459> be<00:02:56.640> really<00:02:56.760> scary<00:02:57.000> because 00:02:57.350 --> 00:02:57.360 align:start position:0% homes which can be really scary because 00:02:57.360 --> 00:02:59.630 align:start position:0% homes which can be really scary because their<00:02:57.599> public<00:02:57.840> addresses<00:02:58.379> uh<00:02:58.980> their<00:02:59.160> private 00:02:59.630 --> 00:02:59.640 align:start position:0% their public addresses uh their private 00:02:59.640 --> 00:03:01.070 align:start position:0% their public addresses uh their private addresses<00:02:59.940> the<00:03:00.120> home<00:03:00.239> addresses<00:03:00.720> were 00:03:01.070 --> 00:03:01.080 align:start position:0% addresses the home addresses were 00:03:01.080 --> 00:03:02.990 align:start position:0% addresses the home addresses were outside<00:03:01.500> in<00:03:01.980> public 00:03:02.990 --> 00:03:03.000 align:start position:0% outside in public 00:03:03.000 --> 00:03:05.449 align:start position:0% outside in public so<00:03:03.420> let's<00:03:03.599> talk<00:03:03.780> about<00:03:03.900> open<00:03:04.140> source 00:03:05.449 --> 00:03:05.459 align:start position:0% so let's talk about open source 00:03:05.459 --> 00:03:09.050 align:start position:0% so let's talk about open source uh<00:03:06.180> what<00:03:06.420> is<00:03:06.540> open<00:03:06.720> source<00:03:07.200> like<00:03:07.500> there<00:03:08.040> are<00:03:08.160> 10 00:03:09.050 --> 00:03:09.060 align:start position:0% uh what is open source like there are 10 00:03:09.060 --> 00:03:12.190 align:start position:0% uh what is open source like there are 10 10<00:03:09.420> criteria<00:03:10.019> that<00:03:10.379> uh<00:03:10.739> Define<00:03:11.159> open<00:03:11.580> source 00:03:12.190 --> 00:03:12.200 align:start position:0% 10 criteria that uh Define open source 00:03:12.200 --> 00:03:15.229 align:start position:0% 10 criteria that uh Define open source uh<00:03:13.200> the<00:03:13.680> main<00:03:13.800> idea<00:03:14.159> is<00:03:14.400> that<00:03:14.640> open<00:03:14.940> source 00:03:15.229 --> 00:03:15.239 align:start position:0% uh the main idea is that open source 00:03:15.239 --> 00:03:16.130 align:start position:0% uh the main idea is that open source software 00:03:16.130 --> 00:03:16.140 align:start position:0% software 00:03:16.140 --> 00:03:18.470 align:start position:0% software is<00:03:16.680> freely<00:03:16.980> distributed<00:03:17.519> along<00:03:18.120> with<00:03:18.360> the 00:03:18.470 --> 00:03:18.480 align:start position:0% is freely distributed along with the 00:03:18.480 --> 00:03:21.410 align:start position:0% is freely distributed along with the source<00:03:18.780> code<00:03:18.900> and<00:03:19.560> it<00:03:19.739> doesn't<00:03:20.340> limit<00:03:20.819> the 00:03:21.410 --> 00:03:21.420 align:start position:0% source code and it doesn't limit the 00:03:21.420 --> 00:03:22.369 align:start position:0% source code and it doesn't limit the usage 00:03:22.369 --> 00:03:22.379 align:start position:0% usage 00:03:22.379 --> 00:03:24.649 align:start position:0% usage uh<00:03:23.040> there<00:03:23.280> is<00:03:23.400> no<00:03:23.519> discrimination<00:03:24.060> against 00:03:24.649 --> 00:03:24.659 align:start position:0% uh there is no discrimination against 00:03:24.659 --> 00:03:27.649 align:start position:0% uh there is no discrimination against people<00:03:25.080> and<00:03:25.440> guess<00:03:25.680> against<00:03:25.980> us 00:03:27.649 --> 00:03:27.659 align:start position:0% people and guess against us 00:03:27.659 --> 00:03:31.250 align:start position:0% people and guess against us everyone<00:03:28.200> can<00:03:28.500> use<00:03:28.620> a<00:03:28.739> software<00:03:29.819> uh 00:03:31.250 --> 00:03:31.260 align:start position:0% everyone can use a software uh 00:03:31.260 --> 00:03:33.710 align:start position:0% everyone can use a software uh we<00:03:31.739> also<00:03:31.920> have<00:03:32.040> cases<00:03:32.459> of<00:03:32.760> uh 00:03:33.710 --> 00:03:33.720 align:start position:0% we also have cases of uh 00:03:33.720 --> 00:03:35.690 align:start position:0% we also have cases of uh software<00:03:34.319> that<00:03:34.500> has<00:03:34.680> public<00:03:34.920> available<00:03:35.280> code 00:03:35.690 --> 00:03:35.700 align:start position:0% software that has public available code 00:03:35.700 --> 00:03:38.690 align:start position:0% software that has public available code but<00:03:36.540> it<00:03:36.780> is<00:03:36.900> endometristers<00:03:37.560> uh<00:03:38.459> some 00:03:38.690 --> 00:03:38.700 align:start position:0% but it is endometristers uh some 00:03:38.700 --> 00:03:41.570 align:start position:0% but it is endometristers uh some examples<00:03:39.120> uh<00:03:39.720> include<00:03:40.680> you<00:03:41.099> know<00:03:41.159> the<00:03:41.280> delayed 00:03:41.570 --> 00:03:41.580 align:start position:0% examples uh include you know the delayed 00:03:41.580 --> 00:03:44.449 align:start position:0% examples uh include you know the delayed open<00:03:41.700> source<00:03:42.000> lines<00:03:42.239> license<00:03:42.780> that<00:03:43.260> a<00:03:43.980> uniswap 00:03:44.449 --> 00:03:44.459 align:start position:0% open source lines license that a uniswap 00:03:44.459 --> 00:03:45.589 align:start position:0% open source lines license that a uniswap another<00:03:44.640> have 00:03:45.589 --> 00:03:45.599 align:start position:0% another have 00:03:45.599 --> 00:03:48.530 align:start position:0% another have and<00:03:46.140> uh<00:03:46.920> maybe<00:03:47.159> mongodb<00:03:47.760> server-side<00:03:48.299> public 00:03:48.530 --> 00:03:48.540 align:start position:0% and uh maybe mongodb server-side public 00:03:48.540 --> 00:03:52.309 align:start position:0% and uh maybe mongodb server-side public license<00:03:48.860> and<00:03:49.860> uh<00:03:50.459> in<00:03:51.360> a<00:03:51.420> lot<00:03:51.480> of<00:03:51.540> cases<00:03:51.959> I<00:03:52.200> can 00:03:52.309 --> 00:03:52.319 align:start position:0% license and uh in a lot of cases I can 00:03:52.319 --> 00:03:53.990 align:start position:0% license and uh in a lot of cases I can understand<00:03:52.440> the<00:03:52.739> reason<00:03:52.920> behind<00:03:53.280> that 00:03:53.990 --> 00:03:54.000 align:start position:0% understand the reason behind that 00:03:54.000 --> 00:03:56.449 align:start position:0% understand the reason behind that because<00:03:54.480> it's<00:03:55.140> really<00:03:55.379> hard<00:03:55.620> for<00:03:55.799> open<00:03:56.040> source 00:03:56.449 --> 00:03:56.459 align:start position:0% because it's really hard for open source 00:03:56.459 --> 00:03:58.970 align:start position:0% because it's really hard for open source projects<00:03:56.819> to<00:03:57.299> fight<00:03:57.480> against<00:03:57.659> big<00:03:58.019> companies 00:03:58.970 --> 00:03:58.980 align:start position:0% projects to fight against big companies 00:03:58.980 --> 00:04:01.070 align:start position:0% projects to fight against big companies you<00:03:59.400> know<00:03:59.459> like<00:03:59.760> uh<00:04:00.060> the<00:04:00.599> reason<00:04:00.720> for<00:04:00.959> the 00:04:01.070 --> 00:04:01.080 align:start position:0% you know like uh the reason for the 00:04:01.080 --> 00:04:04.070 align:start position:0% you know like uh the reason for the server-side<00:04:01.440> public<00:04:01.680> license<00:04:01.980> is<00:04:02.459> that 00:04:04.070 --> 00:04:04.080 align:start position:0% server-side public license is that 00:04:04.080 --> 00:04:07.070 align:start position:0% server-side public license is that AWS<00:04:04.860> was<00:04:05.220> taking<00:04:05.519> all<00:04:06.299> of 00:04:07.070 --> 00:04:07.080 align:start position:0% AWS was taking all of 00:04:07.080 --> 00:04:08.210 align:start position:0% AWS was taking all of um 00:04:08.210 --> 00:04:08.220 align:start position:0% um 00:04:08.220 --> 00:04:10.910 align:start position:0% um mongodb<00:04:09.120> selling<00:04:09.840> it<00:04:09.900> as<00:04:10.019> a<00:04:10.200> service<00:04:10.379> and<00:04:10.799> then 00:04:10.910 --> 00:04:10.920 align:start position:0% mongodb selling it as a service and then 00:04:10.920 --> 00:04:14.030 align:start position:0% mongodb selling it as a service and then the<00:04:11.099> developers<00:04:11.519> didn't<00:04:12.060> have<00:04:12.480> the<00:04:13.080> funds<00:04:13.439> and 00:04:14.030 --> 00:04:14.040 align:start position:0% the developers didn't have the funds and 00:04:14.040 --> 00:04:17.750 align:start position:0% the developers didn't have the funds and they<00:04:14.220> had<00:04:14.459> to<00:04:14.700> maintain<00:04:15.120> and<00:04:15.360> fix<00:04:15.599> the<00:04:15.780> issues 00:04:17.750 --> 00:04:17.760 align:start position:0% they had to maintain and fix the issues 00:04:17.760 --> 00:04:18.710 align:start position:0% they had to maintain and fix the issues um 00:04:18.710 --> 00:04:18.720 align:start position:0% um 00:04:18.720 --> 00:04:21.289 align:start position:0% um so<00:04:19.139> why<00:04:19.380> open<00:04:19.620> source 00:04:21.289 --> 00:04:21.299 align:start position:0% so why open source 00:04:21.299 --> 00:04:23.689 align:start position:0% so why open source there<00:04:21.959> are<00:04:22.139> some<00:04:22.800> strong<00:04:22.979> benefits<00:04:23.400> Building 00:04:23.689 --> 00:04:23.699 align:start position:0% there are some strong benefits Building 00:04:23.699 --> 00:04:25.490 align:start position:0% there are some strong benefits Building open<00:04:24.000> source<00:04:24.479> you<00:04:24.960> can<00:04:25.080> have<00:04:25.199> a<00:04:25.320> strong 00:04:25.490 --> 00:04:25.500 align:start position:0% open source you can have a strong 00:04:25.500 --> 00:04:27.170 align:start position:0% open source you can have a strong Community<00:04:25.680> involvement<00:04:26.280> you<00:04:26.880> can<00:04:27.000> have 00:04:27.170 --> 00:04:27.180 align:start position:0% Community involvement you can have 00:04:27.180 --> 00:04:30.770 align:start position:0% Community involvement you can have transparency<00:04:28.160> reliability<00:04:29.160> security<00:04:29.660> and<00:04:30.660> it 00:04:30.770 --> 00:04:30.780 align:start position:0% transparency reliability security and it 00:04:30.780 --> 00:04:33.590 align:start position:0% transparency reliability security and it also<00:04:31.259> makes<00:04:31.440> it<00:04:31.740> attracting<00:04:32.639> Talent<00:04:33.300> easier 00:04:33.590 --> 00:04:33.600 align:start position:0% also makes it attracting Talent easier 00:04:33.600 --> 00:04:35.210 align:start position:0% also makes it attracting Talent easier and<00:04:34.020> uh 00:04:35.210 --> 00:04:35.220 align:start position:0% and uh 00:04:35.220 --> 00:04:37.550 align:start position:0% and uh it<00:04:35.699> avoids<00:04:36.060> also<00:04:36.300> a<00:04:36.419> vendor<00:04:36.660> login 00:04:37.550 --> 00:04:37.560 align:start position:0% it avoids also a vendor login 00:04:37.560 --> 00:04:40.850 align:start position:0% it avoids also a vendor login so<00:04:38.040> like<00:04:38.280> Community<00:04:38.460> involvement<00:04:39.199> uh<00:04:40.199> there 00:04:40.850 --> 00:04:40.860 align:start position:0% so like Community involvement uh there 00:04:40.860 --> 00:04:43.430 align:start position:0% so like Community involvement uh there are<00:04:40.979> people<00:04:41.220> around<00:04:41.580> like<00:04:42.120> someone<00:04:42.720> needs<00:04:43.320> a 00:04:43.430 --> 00:04:43.440 align:start position:0% are people around like someone needs a 00:04:43.440 --> 00:04:46.189 align:start position:0% are people around like someone needs a feature<00:04:43.800> we<00:04:44.460> might<00:04:44.639> be<00:04:44.820> overwhelmed<00:04:45.540> and 00:04:46.189 --> 00:04:46.199 align:start position:0% feature we might be overwhelmed and 00:04:46.199 --> 00:04:47.689 align:start position:0% feature we might be overwhelmed and someone<00:04:46.380> with<00:04:46.680> technical<00:04:46.979> Technologies<00:04:47.520> can 00:04:47.689 --> 00:04:47.699 align:start position:0% someone with technical Technologies can 00:04:47.699 --> 00:04:49.490 align:start position:0% someone with technical Technologies can come<00:04:47.820> and<00:04:48.000> contribute<00:04:48.300> to<00:04:48.360> the<00:04:48.540> code<00:04:48.600> base<00:04:48.840> and 00:04:49.490 --> 00:04:49.500 align:start position:0% come and contribute to the code base and 00:04:49.500 --> 00:04:52.070 align:start position:0% come and contribute to the code base and not<00:04:49.620> their<00:04:49.800> future<00:04:50.040> that<00:04:50.940> they<00:04:51.120> want<00:04:51.240> to<00:04:51.360> use 00:04:52.070 --> 00:04:52.080 align:start position:0% not their future that they want to use 00:04:52.080 --> 00:04:54.650 align:start position:0% not their future that they want to use so<00:04:52.440> other<00:04:52.680> people<00:04:52.800> can<00:04:53.040> also<00:04:53.280> use<00:04:53.460> it<00:04:53.639> uh<00:04:54.479> the 00:04:54.650 --> 00:04:54.660 align:start position:0% so other people can also use it uh the 00:04:54.660 --> 00:04:57.409 align:start position:0% so other people can also use it uh the non-technical<00:04:55.259> people<00:04:55.759> can<00:04:56.759> contribute<00:04:57.180> with 00:04:57.409 --> 00:04:57.419 align:start position:0% non-technical people can contribute with 00:04:57.419 --> 00:04:59.689 align:start position:0% non-technical people can contribute with translations<00:04:57.979> uh<00:04:58.979> making<00:04:59.220> the<00:04:59.340> app<00:04:59.520> available 00:04:59.689 --> 00:04:59.699 align:start position:0% translations uh making the app available 00:04:59.699 --> 00:05:02.230 align:start position:0% translations uh making the app available to<00:05:00.360> bigger<00:05:00.780> amount<00:05:00.960> of<00:05:01.080> people<00:05:01.259> or 00:05:02.230 --> 00:05:02.240 align:start position:0% to bigger amount of people or 00:05:02.240 --> 00:05:06.050 align:start position:0% to bigger amount of people or documentation<00:05:03.560> or<00:05:04.560> just<00:05:04.740> open<00:05:04.919> issues<00:05:05.460> the 00:05:06.050 --> 00:05:06.060 align:start position:0% documentation or just open issues the 00:05:06.060 --> 00:05:08.030 align:start position:0% documentation or just open issues the code<00:05:06.240> is<00:05:06.419> really<00:05:06.660> transparent<00:05:07.259> like<00:05:07.680> you 00:05:08.030 --> 00:05:08.040 align:start position:0% code is really transparent like you 00:05:08.040 --> 00:05:10.249 align:start position:0% code is really transparent like you don't<00:05:08.220> have<00:05:08.460> to<00:05:08.759> trust<00:05:09.120> what<00:05:09.660> the<00:05:09.840> developer 00:05:10.249 --> 00:05:10.259 align:start position:0% don't have to trust what the developer 00:05:10.259 --> 00:05:12.110 align:start position:0% don't have to trust what the developer claims<00:05:10.620> that<00:05:10.740> the<00:05:10.860> software<00:05:11.160> does<00:05:11.340> you<00:05:12.060> can 00:05:12.110 --> 00:05:12.120 align:start position:0% claims that the software does you can 00:05:12.120 --> 00:05:13.909 align:start position:0% claims that the software does you can easily<00:05:12.419> read<00:05:12.780> the<00:05:12.960> code<00:05:13.139> or<00:05:13.380> other<00:05:13.500> people<00:05:13.740> can 00:05:13.909 --> 00:05:13.919 align:start position:0% easily read the code or other people can 00:05:13.919 --> 00:05:15.710 align:start position:0% easily read the code or other people can read<00:05:14.100> the<00:05:14.220> code<00:05:14.400> and<00:05:14.820> verify<00:05:15.180> that<00:05:15.360> these 00:05:15.710 --> 00:05:15.720 align:start position:0% read the code and verify that these 00:05:15.720 --> 00:05:18.530 align:start position:0% read the code and verify that these claims<00:05:15.960> are<00:05:16.139> actually<00:05:16.320> true<00:05:16.639> and<00:05:17.639> uh<00:05:18.120> open 00:05:18.530 --> 00:05:18.540 align:start position:0% claims are actually true and uh open 00:05:18.540 --> 00:05:20.030 align:start position:0% claims are actually true and uh open source<00:05:18.840> software<00:05:19.080> tends<00:05:19.500> to<00:05:19.560> be<00:05:19.680> more 00:05:20.030 --> 00:05:20.040 align:start position:0% source software tends to be more 00:05:20.040 --> 00:05:22.189 align:start position:0% source software tends to be more reliable<00:05:20.460> and<00:05:20.820> secure<00:05:21.300> it's<00:05:21.479> pretty<00:05:21.780> viewed 00:05:22.189 --> 00:05:22.199 align:start position:0% reliable and secure it's pretty viewed 00:05:22.199 --> 00:05:24.590 align:start position:0% reliable and secure it's pretty viewed so<00:05:22.620> anyone<00:05:22.979> can<00:05:23.160> read<00:05:23.280> the<00:05:23.460> code<00:05:23.639> and<00:05:24.419> it's 00:05:24.590 --> 00:05:24.600 align:start position:0% so anyone can read the code and it's 00:05:24.600 --> 00:05:28.969 align:start position:0% so anyone can read the code and it's easier<00:05:25.020> to<00:05:25.919> spot<00:05:26.220> flaws<00:05:26.759> earlier 00:05:28.969 --> 00:05:28.979 align:start position:0% easier to spot flaws earlier 00:05:28.979 --> 00:05:32.330 align:start position:0% easier to spot flaws earlier um run<00:05:29.580> closed<00:05:30.060> Source<00:05:30.560> we<00:05:31.560> have<00:05:31.740> like<00:05:32.039> a 00:05:32.330 --> 00:05:32.340 align:start position:0% um run closed Source we have like a 00:05:32.340 --> 00:05:34.490 align:start position:0% um run closed Source we have like a software<00:05:32.880> we<00:05:33.120> always<00:05:33.240> use<00:05:33.539> that<00:05:33.900> is<00:05:34.259> really 00:05:34.490 --> 00:05:34.500 align:start position:0% software we always use that is really 00:05:34.500 --> 00:05:37.070 align:start position:0% software we always use that is really robust<00:05:34.979> like<00:05:35.520> example<00:05:35.940> for<00:05:36.240> example<00:05:36.419> Firefox 00:05:37.070 --> 00:05:37.080 align:start position:0% robust like example for example Firefox 00:05:37.080 --> 00:05:40.730 align:start position:0% robust like example for example Firefox the<00:05:37.620> Linux<00:05:37.919> kernel<00:05:38.419> uh<00:05:39.419> ethereum<00:05:40.139> clients<00:05:40.500> and 00:05:40.730 --> 00:05:40.740 align:start position:0% the Linux kernel uh ethereum clients and 00:05:40.740 --> 00:05:42.830 align:start position:0% the Linux kernel uh ethereum clients and Unix<00:05:41.160> and<00:05:41.639> this<00:05:41.820> is<00:05:42.000> highly<00:05:42.419> Reliable 00:05:42.830 --> 00:05:42.840 align:start position:0% Unix and this is highly Reliable 00:05:42.840 --> 00:05:45.710 align:start position:0% Unix and this is highly Reliable Software<00:05:43.560> we<00:05:43.860> use<00:05:44.039> everywhere<00:05:44.580> and<00:05:45.419> it's<00:05:45.600> all 00:05:45.710 --> 00:05:45.720 align:start position:0% Software we use everywhere and it's all 00:05:45.720 --> 00:05:49.909 align:start position:0% Software we use everywhere and it's all open<00:05:45.900> source<00:05:46.460> uh<00:05:47.460> then<00:05:47.759> uh<00:05:48.720> open<00:05:49.320> source<00:05:49.680> can 00:05:49.909 --> 00:05:49.919 align:start position:0% open source uh then uh open source can 00:05:49.919 --> 00:05:52.490 align:start position:0% open source uh then uh open source can make<00:05:50.160> attracting<00:05:50.940> Talent<00:05:51.300> really<00:05:51.600> easy 00:05:52.490 --> 00:05:52.500 align:start position:0% make attracting Talent really easy 00:05:52.500 --> 00:05:54.650 align:start position:0% make attracting Talent really easy because<00:05:53.340> it's<00:05:53.699> always<00:05:53.940> easier<00:05:54.360> to<00:05:54.539> hire 00:05:54.650 --> 00:05:54.660 align:start position:0% because it's always easier to hire 00:05:54.660 --> 00:05:56.990 align:start position:0% because it's always easier to hire someone<00:05:54.960> that<00:05:55.500> you<00:05:55.800> have<00:05:55.979> previously<00:05:56.460> worked 00:05:56.990 --> 00:05:57.000 align:start position:0% someone that you have previously worked 00:05:57.000 --> 00:05:58.909 align:start position:0% someone that you have previously worked with<00:05:57.120> you<00:05:57.419> had<00:05:57.600> the<00:05:57.720> good<00:05:57.840> interaction<00:05:58.199> and 00:05:58.909 --> 00:05:58.919 align:start position:0% with you had the good interaction and 00:05:58.919 --> 00:06:01.430 align:start position:0% with you had the good interaction and then<00:05:59.220> maybe<00:05:59.520> you<00:06:00.000> also<00:06:00.300> text<00:06:00.479> your<00:06:00.720> code<00:06:00.900> and 00:06:01.430 --> 00:06:01.440 align:start position:0% then maybe you also text your code and 00:06:01.440 --> 00:06:03.590 align:start position:0% then maybe you also text your code and you<00:06:01.560> can<00:06:01.740> see<00:06:01.979> in<00:06:02.820> an<00:06:03.000> easier<00:06:03.240> way<00:06:03.419> that 00:06:03.590 --> 00:06:03.600 align:start position:0% you can see in an easier way that 00:06:03.600 --> 00:06:05.450 align:start position:0% you can see in an easier way that someone<00:06:03.720> is<00:06:03.960> a<00:06:04.080> good<00:06:04.199> fit<00:06:04.380> for<00:06:04.620> your<00:06:05.100> culture 00:06:05.450 --> 00:06:05.460 align:start position:0% someone is a good fit for your culture 00:06:05.460 --> 00:06:08.270 align:start position:0% someone is a good fit for your culture which<00:06:06.300> is<00:06:06.539> not<00:06:06.780> always<00:06:06.960> the<00:06:07.199> case<00:06:07.380> uh<00:06:07.979> when 00:06:08.270 --> 00:06:08.280 align:start position:0% which is not always the case uh when 00:06:08.280 --> 00:06:10.909 align:start position:0% which is not always the case uh when doing<00:06:08.759> some<00:06:09.120> small<00:06:09.300> interviews<00:06:09.840> and<00:06:10.500> uh<00:06:10.740> you 00:06:10.909 --> 00:06:10.919 align:start position:0% doing some small interviews and uh you 00:06:10.919 --> 00:06:13.670 align:start position:0% doing some small interviews and uh you know<00:06:10.979> like<00:06:11.100> giving<00:06:11.580> some<00:06:12.060> kind<00:06:12.240> of<00:06:12.360> task<00:06:12.680> and 00:06:13.670 --> 00:06:13.680 align:start position:0% know like giving some kind of task and 00:06:13.680 --> 00:06:15.590 align:start position:0% know like giving some kind of task and then<00:06:13.919> uh<00:06:14.520> like<00:06:14.759> I<00:06:14.880> said<00:06:15.000> you<00:06:15.180> can<00:06:15.300> avoid 00:06:15.590 --> 00:06:15.600 align:start position:0% then uh like I said you can avoid 00:06:15.600 --> 00:06:17.629 align:start position:0% then uh like I said you can avoid ventral<00:06:16.080> login<00:06:16.500> uh<00:06:17.039> you<00:06:17.220> always<00:06:17.340> have<00:06:17.520> access 00:06:17.629 --> 00:06:17.639 align:start position:0% ventral login uh you always have access 00:06:17.639 --> 00:06:19.189 align:start position:0% ventral login uh you always have access to<00:06:17.880> the<00:06:18.000> source<00:06:18.240> code<00:06:18.360> you<00:06:18.720> always<00:06:18.960> have 00:06:19.189 --> 00:06:19.199 align:start position:0% to the source code you always have 00:06:19.199 --> 00:06:21.350 align:start position:0% to the source code you always have access<00:06:19.320> to<00:06:19.560> the<00:06:19.680> application<00:06:20.100> you<00:06:20.940> can<00:06:21.060> check 00:06:21.350 --> 00:06:21.360 align:start position:0% access to the application you can check 00:06:21.360 --> 00:06:24.050 align:start position:0% access to the application you can check the<00:06:21.600> data<00:06:22.080> you<00:06:22.259> can<00:06:22.380> access<00:06:22.500> the<00:06:22.740> data<00:06:23.100> so<00:06:23.639> uh 00:06:24.050 --> 00:06:24.060 align:start position:0% the data you can access the data so uh 00:06:24.060 --> 00:06:25.790 align:start position:0% the data you can access the data so uh in<00:06:24.300> case<00:06:24.419> you<00:06:24.720> want<00:06:24.960> to<00:06:25.139> move<00:06:25.259> and<00:06:25.440> migrate 00:06:25.790 --> 00:06:25.800 align:start position:0% in case you want to move and migrate 00:06:25.800 --> 00:06:29.390 align:start position:0% in case you want to move and migrate from<00:06:25.919> the<00:06:26.100> platform<00:06:26.819> uh<00:06:27.840> it<00:06:28.440> becomes<00:06:28.860> really 00:06:29.390 --> 00:06:29.400 align:start position:0% from the platform uh it becomes really 00:06:29.400 --> 00:06:32.870 align:start position:0% from the platform uh it becomes really easy<00:06:29.639> because<00:06:30.380> you<00:06:31.380> can<00:06:31.440> access<00:06:31.560> everything 00:06:32.870 --> 00:06:32.880 align:start position:0% easy because you can access everything 00:06:32.880 --> 00:06:34.969 align:start position:0% easy because you can access everything so<00:06:33.780> the<00:06:33.900> biggest<00:06:34.020> problem<00:06:34.199> with<00:06:34.440> open<00:06:34.560> source 00:06:34.969 --> 00:06:34.979 align:start position:0% so the biggest problem with open source 00:06:34.979 --> 00:06:37.550 align:start position:0% so the biggest problem with open source is<00:06:35.039> funding<00:06:35.400> because<00:06:36.300> it's<00:06:36.660> hard<00:06:36.900> to<00:06:37.080> want<00:06:37.319> to 00:06:37.550 --> 00:06:37.560 align:start position:0% is funding because it's hard to want to 00:06:37.560 --> 00:06:40.129 align:start position:0% is funding because it's hard to want to monetize<00:06:37.860> the<00:06:38.100> openness<00:06:38.340> of<00:06:38.460> software 00:06:40.129 --> 00:06:40.139 align:start position:0% monetize the openness of software 00:06:40.139 --> 00:06:43.430 align:start position:0% monetize the openness of software um we<00:06:40.979> had<00:06:41.220> like<00:06:42.000> some<00:06:42.240> major<00:06:42.539> incidents<00:06:43.199> for 00:06:43.430 --> 00:06:43.440 align:start position:0% um we had like some major incidents for 00:06:43.440 --> 00:06:46.550 align:start position:0% um we had like some major incidents for example<00:06:43.620> there<00:06:44.100> was<00:06:44.460> the<00:06:44.759> look<00:06:44.880> for<00:06:45.060> j-hack<00:06:45.660> uh 00:06:46.550 --> 00:06:46.560 align:start position:0% example there was the look for j-hack uh 00:06:46.560 --> 00:06:48.650 align:start position:0% example there was the look for j-hack uh or<00:06:46.680> the<00:06:46.919> opening<00:06:47.280> system<00:06:47.400> had<00:06:47.699> bleed<00:06:48.120> and<00:06:48.539> we 00:06:48.650 --> 00:06:48.660 align:start position:0% or the opening system had bleed and we 00:06:48.660 --> 00:06:51.230 align:start position:0% or the opening system had bleed and we what<00:06:48.900> we<00:06:49.259> found<00:06:49.440> out<00:06:49.620> out<00:06:49.860> of<00:06:50.039> this<00:06:50.160> is<00:06:50.580> that 00:06:51.230 --> 00:06:51.240 align:start position:0% what we found out out of this is that 00:06:51.240 --> 00:06:53.809 align:start position:0% what we found out out of this is that you<00:06:51.780> had<00:06:51.900> a<00:06:52.139> couple<00:06:52.259> of<00:06:52.440> overwhelmed<00:06:53.220> software 00:06:53.809 --> 00:06:53.819 align:start position:0% you had a couple of overwhelmed software 00:06:53.819 --> 00:06:55.909 align:start position:0% you had a couple of overwhelmed software developers<00:06:54.380> maintaining<00:06:55.380> infrastructure 00:06:55.909 --> 00:06:55.919 align:start position:0% developers maintaining infrastructure 00:06:55.919 --> 00:06:57.409 align:start position:0% developers maintaining infrastructure critical<00:06:56.460> software 00:06:57.409 --> 00:06:57.419 align:start position:0% critical software 00:06:57.419 --> 00:06:59.930 align:start position:0% critical software and<00:06:58.139> everyone<00:06:58.440> using<00:06:58.979> it<00:06:59.100> but<00:06:59.580> they<00:06:59.819> were 00:06:59.930 --> 00:06:59.940 align:start position:0% and everyone using it but they were 00:06:59.940 --> 00:07:02.029 align:start position:0% and everyone using it but they were always<00:07:00.120> underfunded<00:07:00.780> no<00:07:01.139> one<00:07:01.380> was<00:07:01.500> paying<00:07:01.919> for 00:07:02.029 --> 00:07:02.039 align:start position:0% always underfunded no one was paying for 00:07:02.039 --> 00:07:02.749 align:start position:0% always underfunded no one was paying for that 00:07:02.749 --> 00:07:02.759 align:start position:0% that 00:07:02.759 --> 00:07:03.950 align:start position:0% that and 00:07:03.950 --> 00:07:03.960 align:start position:0% and 00:07:03.960 --> 00:07:07.850 align:start position:0% and these<00:07:04.919> uh<00:07:05.580> led<00:07:05.759> to<00:07:05.940> huge<00:07:06.300> security<00:07:06.479> problems 00:07:07.850 --> 00:07:07.860 align:start position:0% these uh led to huge security problems 00:07:07.860 --> 00:07:10.790 align:start position:0% these uh led to huge security problems uh<00:07:08.639> so<00:07:08.940> there<00:07:09.720> are<00:07:09.840> different<00:07:10.020> ways<00:07:10.380> to<00:07:10.500> fund 00:07:10.790 --> 00:07:10.800 align:start position:0% uh so there are different ways to fund 00:07:10.800 --> 00:07:13.129 align:start position:0% uh so there are different ways to fund but<00:07:10.919> it's<00:07:11.100> always<00:07:11.280> uh<00:07:11.819> difficult<00:07:12.240> uh<00:07:12.900> for 00:07:13.129 --> 00:07:13.139 align:start position:0% but it's always uh difficult uh for 00:07:13.139 --> 00:07:15.590 align:start position:0% but it's always uh difficult uh for example<00:07:13.380> you<00:07:14.039> can<00:07:14.100> accept<00:07:14.340> donations<00:07:14.880> you<00:07:15.479> can 00:07:15.590 --> 00:07:15.600 align:start position:0% example you can accept donations you can 00:07:15.600 --> 00:07:16.430 align:start position:0% example you can accept donations you can have 00:07:16.430 --> 00:07:16.440 align:start position:0% have 00:07:16.440 --> 00:07:20.390 align:start position:0% have as<00:07:16.800> we<00:07:17.039> do<00:07:17.160> in<00:07:17.280> Rocky<00:07:17.639> uh<00:07:18.180> we<00:07:18.479> can<00:07:18.660> get<00:07:19.440> uh 00:07:20.390 --> 00:07:20.400 align:start position:0% as we do in Rocky uh we can get uh 00:07:20.400 --> 00:07:22.189 align:start position:0% as we do in Rocky uh we can get uh grants<00:07:21.180> for<00:07:21.300> Integrations<00:07:21.720> with<00:07:22.080> other 00:07:22.189 --> 00:07:22.199 align:start position:0% grants for Integrations with other 00:07:22.199 --> 00:07:24.469 align:start position:0% grants for Integrations with other protocols<00:07:22.860> uh<00:07:23.699> git<00:07:23.940> concurrence<00:07:24.360> is 00:07:24.469 --> 00:07:24.479 align:start position:0% protocols uh git concurrence is 00:07:24.479 --> 00:07:25.969 align:start position:0% protocols uh git concurrence is something<00:07:24.660> that<00:07:24.900> help<00:07:25.139> us<00:07:25.319> a<00:07:25.500> lot<00:07:25.620> to<00:07:25.800> build 00:07:25.969 --> 00:07:25.979 align:start position:0% something that help us a lot to build 00:07:25.979 --> 00:07:28.010 align:start position:0% something that help us a lot to build the<00:07:26.220> software<00:07:26.580> and<00:07:27.240> then<00:07:27.360> we<00:07:27.539> have<00:07:27.660> premium 00:07:28.010 --> 00:07:28.020 align:start position:0% the software and then we have premium 00:07:28.020 --> 00:07:30.770 align:start position:0% the software and then we have premium subscriptions<00:07:28.560> but<00:07:28.979> uh<00:07:29.400> this<00:07:30.240> doesn't<00:07:30.479> really 00:07:30.770 --> 00:07:30.780 align:start position:0% subscriptions but uh this doesn't really 00:07:30.780 --> 00:07:32.749 align:start position:0% subscriptions but uh this doesn't really work<00:07:31.080> because<00:07:31.380> it's<00:07:31.740> hard<00:07:32.039> to<00:07:32.340> monetize 00:07:32.749 --> 00:07:32.759 align:start position:0% work because it's hard to monetize 00:07:32.759 --> 00:07:34.129 align:start position:0% work because it's hard to monetize retail 00:07:34.129 --> 00:07:34.139 align:start position:0% retail 00:07:34.139 --> 00:07:37.249 align:start position:0% retail and<00:07:35.099> uh<00:07:35.580> you<00:07:35.819> know<00:07:35.880> as<00:07:36.060> a<00:07:36.300> nice<00:07:36.479> small<00:07:36.780> software 00:07:37.249 --> 00:07:37.259 align:start position:0% and uh you know as a nice small software 00:07:37.259 --> 00:07:38.930 align:start position:0% and uh you know as a nice small software it's<00:07:37.680> hard<00:07:37.860> for<00:07:38.099> us 00:07:38.930 --> 00:07:38.940 align:start position:0% it's hard for us 00:07:38.940 --> 00:07:41.629 align:start position:0% it's hard for us to<00:07:39.360> actually<00:07:39.479> have<00:07:39.840> the<00:07:40.199> amount<00:07:40.380> of<00:07:40.500> people<00:07:40.680> uh 00:07:41.629 --> 00:07:41.639 align:start position:0% to actually have the amount of people uh 00:07:41.639 --> 00:07:43.969 align:start position:0% to actually have the amount of people uh that<00:07:41.819> we<00:07:42.060> would<00:07:42.240> need<00:07:42.599> to<00:07:43.139> uh<00:07:43.560> have<00:07:43.860> a 00:07:43.969 --> 00:07:43.979 align:start position:0% that we would need to uh have a 00:07:43.979 --> 00:07:46.070 align:start position:0% that we would need to uh have a sustainable<00:07:44.340> source<00:07:44.639> of<00:07:44.699> income 00:07:46.070 --> 00:07:46.080 align:start position:0% sustainable source of income 00:07:46.080 --> 00:07:48.589 align:start position:0% sustainable source of income uh<00:07:46.919> so<00:07:47.280> let's<00:07:47.759> talk<00:07:47.880> about<00:07:48.000> local<00:07:48.300> first 00:07:48.589 --> 00:07:48.599 align:start position:0% uh so let's talk about local first 00:07:48.599 --> 00:07:50.089 align:start position:0% uh so let's talk about local first software 00:07:50.089 --> 00:07:50.099 align:start position:0% software 00:07:50.099 --> 00:07:52.850 align:start position:0% software uh<00:07:50.759> in<00:07:51.060> local<00:07:51.180> first<00:07:51.479> software<00:07:51.840> you<00:07:52.620> control 00:07:52.850 --> 00:07:52.860 align:start position:0% uh in local first software you control 00:07:52.860 --> 00:07:54.110 align:start position:0% uh in local first software you control your<00:07:53.160> data 00:07:54.110 --> 00:07:54.120 align:start position:0% your data 00:07:54.120 --> 00:07:56.089 align:start position:0% your data everything<00:07:54.660> happens<00:07:55.080> on<00:07:55.560> the<00:07:55.680> machine<00:07:55.800> you 00:07:56.089 --> 00:07:56.099 align:start position:0% everything happens on the machine you 00:07:56.099 --> 00:07:57.170 align:start position:0% everything happens on the machine you control 00:07:57.170 --> 00:07:57.180 align:start position:0% control 00:07:57.180 --> 00:07:59.029 align:start position:0% control uh 00:07:59.029 --> 00:07:59.039 align:start position:0% uh 00:07:59.039 --> 00:08:00.969 align:start position:0% uh there<00:07:59.639> are 00:08:00.969 --> 00:08:00.979 align:start position:0% there are 00:08:00.979 --> 00:08:04.189 align:start position:0% there are three<00:08:01.979> major<00:08:02.220> principles<00:08:02.940> so<00:08:03.419> the<00:08:03.720> network<00:08:03.840> is 00:08:04.189 --> 00:08:04.199 align:start position:0% three major principles so the network is 00:08:04.199 --> 00:08:06.950 align:start position:0% three major principles so the network is optional<00:08:04.819> uh<00:08:05.819> local<00:08:06.120> data<00:08:06.539> is<00:08:06.599> the<00:08:06.720> primary 00:08:06.950 --> 00:08:06.960 align:start position:0% optional uh local data is the primary 00:08:06.960 --> 00:08:09.589 align:start position:0% optional uh local data is the primary data<00:08:07.440> and<00:08:08.160> security<00:08:08.400> and<00:08:08.819> privacy<00:08:09.180> are<00:08:09.419> really 00:08:09.589 --> 00:08:09.599 align:start position:0% data and security and privacy are really 00:08:09.599 --> 00:08:11.029 align:start position:0% data and security and privacy are really fundamental 00:08:11.029 --> 00:08:11.039 align:start position:0% fundamental 00:08:11.039 --> 00:08:13.550 align:start position:0% fundamental so<00:08:11.580> by<00:08:11.759> network<00:08:12.000> is<00:08:12.479> optional<00:08:12.900> we<00:08:13.080> don't<00:08:13.380> mean 00:08:13.550 --> 00:08:13.560 align:start position:0% so by network is optional we don't mean 00:08:13.560 --> 00:08:14.510 align:start position:0% so by network is optional we don't mean that<00:08:13.740> you<00:08:13.800> don't<00:08:13.979> have<00:08:14.099> access<00:08:14.220> to<00:08:14.400> the 00:08:14.510 --> 00:08:14.520 align:start position:0% that you don't have access to the 00:08:14.520 --> 00:08:17.150 align:start position:0% that you don't have access to the network<00:08:14.699> like<00:08:15.120> you<00:08:15.300> can<00:08:15.479> use<00:08:15.599> your<00:08:15.900> Wi-Fi<00:08:16.319> uh 00:08:17.150 --> 00:08:17.160 align:start position:0% network like you can use your Wi-Fi uh 00:08:17.160 --> 00:08:19.730 align:start position:0% network like you can use your Wi-Fi uh you<00:08:17.460> can<00:08:17.580> use<00:08:18.120> your<00:08:18.300> local<00:08:18.479> network<00:08:19.080> to<00:08:19.560> access 00:08:19.730 --> 00:08:19.740 align:start position:0% you can use your local network to access 00:08:19.740 --> 00:08:23.330 align:start position:0% you can use your local network to access to<00:08:20.160> access<00:08:20.400> blockchain<00:08:21.000> data<00:08:21.500> maybe<00:08:22.500> get<00:08:22.979> some 00:08:23.330 --> 00:08:23.340 align:start position:0% to access blockchain data maybe get some 00:08:23.340 --> 00:08:25.010 align:start position:0% to access blockchain data maybe get some uh<00:08:23.639> your<00:08:23.940> trades<00:08:24.240> from<00:08:24.419> centralized 00:08:25.010 --> 00:08:25.020 align:start position:0% uh your trades from centralized 00:08:25.020 --> 00:08:28.670 align:start position:0% uh your trades from centralized exchanges<00:08:25.500> what<00:08:26.400> this<00:08:27.120> means<00:08:27.419> is<00:08:27.780> that 00:08:28.670 --> 00:08:28.680 align:start position:0% exchanges what this means is that 00:08:28.680 --> 00:08:30.529 align:start position:0% exchanges what this means is that all<00:08:28.979> the<00:08:29.160> processing<00:08:29.580> of<00:08:29.879> this<00:08:30.180> data<00:08:30.419> happens 00:08:30.529 --> 00:08:30.539 align:start position:0% all the processing of this data happens 00:08:30.539 --> 00:08:33.290 align:start position:0% all the processing of this data happens locally<00:08:30.960> on<00:08:31.139> your<00:08:31.259> machine 00:08:33.290 --> 00:08:33.300 align:start position:0% locally on your machine 00:08:33.300 --> 00:08:35.149 align:start position:0% locally on your machine data<00:08:33.779> is<00:08:33.899> not<00:08:34.020> pushed<00:08:34.320> to<00:08:34.380> a<00:08:34.500> remote<00:08:34.620> server 00:08:35.149 --> 00:08:35.159 align:start position:0% data is not pushed to a remote server 00:08:35.159 --> 00:08:36.769 align:start position:0% data is not pushed to a remote server it's<00:08:35.459> not<00:08:35.640> pushed<00:08:36.000> to<00:08:36.120> a<00:08:36.180> remote<00:08:36.300> API 00:08:36.769 --> 00:08:36.779 align:start position:0% it's not pushed to a remote API 00:08:36.779 --> 00:08:39.050 align:start position:0% it's not pushed to a remote API everything<00:08:37.620> happens<00:08:37.979> transparently<00:08:38.640> on<00:08:38.880> your 00:08:39.050 --> 00:08:39.060 align:start position:0% everything happens transparently on your 00:08:39.060 --> 00:08:40.810 align:start position:0% everything happens transparently on your machine 00:08:40.810 --> 00:08:40.820 align:start position:0% machine 00:08:40.820 --> 00:08:44.630 align:start position:0% machine uh<00:08:41.820> so<00:08:42.539> uh<00:08:43.020> your<00:08:43.740> local<00:08:43.919> data<00:08:44.279> is<00:08:44.339> primary 00:08:44.630 --> 00:08:44.640 align:start position:0% uh so uh your local data is primary 00:08:44.640 --> 00:08:46.850 align:start position:0% uh so uh your local data is primary unlike<00:08:45.600> uh 00:08:46.850 --> 00:08:46.860 align:start position:0% unlike uh 00:08:46.860 --> 00:08:48.710 align:start position:0% unlike uh you<00:08:47.339> know<00:08:47.459> all<00:08:47.580> these<00:08:47.760> clouds<00:08:48.000> are<00:08:48.180> like<00:08:48.420> using 00:08:48.710 --> 00:08:48.720 align:start position:0% you know all these clouds are like using 00:08:48.720 --> 00:08:51.230 align:start position:0% you know all these clouds are like using Google<00:08:48.839> Drive<00:08:49.560> the<00:08:50.040> primary<00:08:50.459> source<00:08:50.880> of<00:08:50.940> data 00:08:51.230 --> 00:08:51.240 align:start position:0% Google Drive the primary source of data 00:08:51.240 --> 00:08:53.329 align:start position:0% Google Drive the primary source of data is<00:08:51.480> Google<00:08:51.660> Drive<00:08:51.899> any<00:08:52.440> copies<00:08:52.860> if<00:08:53.040> you<00:08:53.160> have 00:08:53.329 --> 00:08:53.339 align:start position:0% is Google Drive any copies if you have 00:08:53.339 --> 00:08:55.750 align:start position:0% is Google Drive any copies if you have are<00:08:54.000> usually<00:08:54.360> some<00:08:54.720> kind<00:08:54.899> of<00:08:55.019> cars<00:08:55.380> some 00:08:55.750 --> 00:08:55.760 align:start position:0% are usually some kind of cars some 00:08:55.760 --> 00:08:58.070 align:start position:0% are usually some kind of cars some secondary<00:08:56.760> copy 00:08:58.070 --> 00:08:58.080 align:start position:0% secondary copy 00:08:58.080 --> 00:08:59.150 align:start position:0% secondary copy and 00:08:59.150 --> 00:08:59.160 align:start position:0% and 00:08:59.160 --> 00:09:02.030 align:start position:0% and while<00:08:59.700> it's<00:08:59.880> unlikely<00:09:00.360> in<00:09:00.839> the<00:09:01.019> the<00:09:01.740> case<00:09:01.920> of 00:09:02.030 --> 00:09:02.040 align:start position:0% while it's unlikely in the the case of 00:09:02.040 --> 00:09:04.430 align:start position:0% while it's unlikely in the the case of Google<00:09:02.160> Drive<00:09:02.459> if<00:09:03.300> your<00:09:03.480> cloud<00:09:03.660> provider<00:09:04.140> goes 00:09:04.430 --> 00:09:04.440 align:start position:0% Google Drive if your cloud provider goes 00:09:04.440 --> 00:09:06.170 align:start position:0% Google Drive if your cloud provider goes out<00:09:04.560> of<00:09:04.680> business<00:09:04.860> then<00:09:05.580> you<00:09:05.760> might<00:09:05.940> lose 00:09:06.170 --> 00:09:06.180 align:start position:0% out of business then you might lose 00:09:06.180 --> 00:09:07.670 align:start position:0% out of business then you might lose everything 00:09:07.670 --> 00:09:07.680 align:start position:0% everything 00:09:07.680 --> 00:09:10.250 align:start position:0% everything uh<00:09:08.820> then 00:09:10.250 --> 00:09:10.260 align:start position:0% uh then 00:09:10.260 --> 00:09:12.470 align:start position:0% uh then because<00:09:10.680> everything<00:09:11.580> is<00:09:11.820> stored<00:09:12.120> locally<00:09:12.360> on 00:09:12.470 --> 00:09:12.480 align:start position:0% because everything is stored locally on 00:09:12.480 --> 00:09:14.150 align:start position:0% because everything is stored locally on your<00:09:12.660> machine 00:09:14.150 --> 00:09:14.160 align:start position:0% your machine 00:09:14.160 --> 00:09:16.370 align:start position:0% your machine it's<00:09:14.820> more<00:09:15.060> secure<00:09:15.240> and<00:09:15.540> it's<00:09:15.660> harder<00:09:15.959> to<00:09:16.019> leak 00:09:16.370 --> 00:09:16.380 align:start position:0% it's more secure and it's harder to leak 00:09:16.380 --> 00:09:19.370 align:start position:0% it's more secure and it's harder to leak than<00:09:16.500> if<00:09:17.220> you<00:09:17.339> had<00:09:17.519> everything<00:09:17.839> on<00:09:18.839> a<00:09:19.019> data 00:09:19.370 --> 00:09:19.380 align:start position:0% than if you had everything on a data 00:09:19.380 --> 00:09:21.769 align:start position:0% than if you had everything on a data center<00:09:19.440> because<00:09:20.399> you<00:09:20.940> are<00:09:21.120> the<00:09:21.300> owner<00:09:21.600> you 00:09:21.769 --> 00:09:21.779 align:start position:0% center because you are the owner you 00:09:21.779 --> 00:09:22.970 align:start position:0% center because you are the owner you control<00:09:21.899> the<00:09:22.200> machine 00:09:22.970 --> 00:09:22.980 align:start position:0% control the machine 00:09:22.980 --> 00:09:24.710 align:start position:0% control the machine and<00:09:23.459> you<00:09:23.580> can<00:09:23.760> actually 00:09:24.710 --> 00:09:24.720 align:start position:0% and you can actually 00:09:24.720 --> 00:09:26.509 align:start position:0% and you can actually better<00:09:25.200> protect<00:09:25.680> them 00:09:26.509 --> 00:09:26.519 align:start position:0% better protect them 00:09:26.519 --> 00:09:29.210 align:start position:0% better protect them so<00:09:27.180> let's<00:09:27.360> talk<00:09:27.540> about<00:09:27.660> large<00:09:27.899> game<00:09:28.560> that's<00:09:29.040> a 00:09:29.210 --> 00:09:29.220 align:start position:0% so let's talk about large game that's a 00:09:29.220 --> 00:09:31.790 align:start position:0% so let's talk about large game that's a nice<00:09:29.339> project<00:09:29.519> we<00:09:29.820> are<00:09:30.000> building<00:09:30.380> rotkey<00:09:31.380> is<00:09:31.620> a 00:09:31.790 --> 00:09:31.800 align:start position:0% nice project we are building rotkey is a 00:09:31.800 --> 00:09:33.650 align:start position:0% nice project we are building rotkey is a portfolio<00:09:32.220> tracker<00:09:32.820> an<00:09:33.060> accounting<00:09:33.420> tool 00:09:33.650 --> 00:09:33.660 align:start position:0% portfolio tracker an accounting tool 00:09:33.660 --> 00:09:36.470 align:start position:0% portfolio tracker an accounting tool that<00:09:33.839> is<00:09:34.080> uh<00:09:34.440> open<00:09:34.740> source<00:09:35.160> local<00:09:35.279> first<00:09:36.060> and 00:09:36.470 --> 00:09:36.480 align:start position:0% that is uh open source local first and 00:09:36.480 --> 00:09:38.990 align:start position:0% that is uh open source local first and it's<00:09:36.600> focused<00:09:36.959> on<00:09:37.080> privacy 00:09:38.990 --> 00:09:39.000 align:start position:0% it's focused on privacy 00:09:39.000 --> 00:09:40.009 align:start position:0% it's focused on privacy and 00:09:40.009 --> 00:09:40.019 align:start position:0% and 00:09:40.019 --> 00:09:43.190 align:start position:0% and and<00:09:40.380> like<00:09:40.680> what<00:09:41.220> some<00:09:41.339> people<00:09:41.519> believe 00:09:43.190 --> 00:09:43.200 align:start position:0% and like what some people believe 00:09:43.200 --> 00:09:45.470 align:start position:0% and like what some people believe the<00:09:43.500> lucky<00:09:43.740> team<00:09:43.980> is<00:09:44.100> not<00:09:44.220> only<00:09:44.339> Lefteris 00:09:45.470 --> 00:09:45.480 align:start position:0% the lucky team is not only Lefteris 00:09:45.480 --> 00:09:48.230 align:start position:0% the lucky team is not only Lefteris like<00:09:45.899> we<00:09:46.140> know<00:09:46.320> he's<00:09:46.560> kind<00:09:46.800> of<00:09:46.920> superhumor<00:09:47.880> but 00:09:48.230 --> 00:09:48.240 align:start position:0% like we know he's kind of superhumor but 00:09:48.240 --> 00:09:50.810 align:start position:0% like we know he's kind of superhumor but he<00:09:48.360> cannot<00:09:48.600> do<00:09:48.779> everything<00:09:48.959> on<00:09:49.260> his<00:09:49.380> own<00:09:49.820> uh 00:09:50.810 --> 00:09:50.820 align:start position:0% he cannot do everything on his own uh 00:09:50.820 --> 00:09:52.370 align:start position:0% he cannot do everything on his own uh currently<00:09:51.180> the<00:09:51.420> rocky<00:09:51.720> team<00:09:51.899> consists<00:09:52.260> of 00:09:52.370 --> 00:09:52.380 align:start position:0% currently the rocky team consists of 00:09:52.380 --> 00:09:55.130 align:start position:0% currently the rocky team consists of seven<00:09:52.680> people<00:09:52.920> uh<00:09:53.640> six<00:09:54.120> Developers 00:09:55.130 --> 00:09:55.140 align:start position:0% seven people uh six Developers 00:09:55.140 --> 00:09:57.829 align:start position:0% seven people uh six Developers and<00:09:55.860> one<00:09:56.160> person<00:09:56.279> handling<00:09:56.760> operations 00:09:57.829 --> 00:09:57.839 align:start position:0% and one person handling operations 00:09:57.839 --> 00:10:01.009 align:start position:0% and one person handling operations uh<00:09:58.560> from<00:09:58.740> the<00:09:58.860> developers<00:09:59.360> uh<00:10:00.360> who<00:10:00.540> have<00:10:00.720> lift 00:10:01.009 --> 00:10:01.019 align:start position:0% uh from the developers uh who have lift 00:10:01.019 --> 00:10:03.829 align:start position:0% uh from the developers uh who have lift teres<00:10:01.320> which<00:10:02.160> most<00:10:02.459> of<00:10:02.640> you<00:10:02.880> if<00:10:03.480> not<00:10:03.600> everyone 00:10:03.829 --> 00:10:03.839 align:start position:0% teres which most of you if not everyone 00:10:03.839 --> 00:10:07.910 align:start position:0% teres which most of you if not everyone knows<00:10:04.399> uh<00:10:05.399> then<00:10:05.760> I'm<00:10:06.120> doing<00:10:06.540> he<00:10:07.140> does<00:10:07.380> back-end 00:10:07.910 --> 00:10:07.920 align:start position:0% knows uh then I'm doing he does back-end 00:10:07.920 --> 00:10:09.889 align:start position:0% knows uh then I'm doing he does back-end uh<00:10:08.399> you<00:10:08.580> know<00:10:08.640> Business<00:10:08.760> Development<00:10:09.240> he<00:10:09.660> does 00:10:09.889 --> 00:10:09.899 align:start position:0% uh you know Business Development he does 00:10:09.899 --> 00:10:13.430 align:start position:0% uh you know Business Development he does a<00:10:10.019> lot<00:10:10.080> of<00:10:10.200> stuff<00:10:10.580> uh<00:10:11.580> then<00:10:12.240> I'm<00:10:12.600> doing<00:10:12.899> mostly 00:10:13.430 --> 00:10:13.440 align:start position:0% a lot of stuff uh then I'm doing mostly 00:10:13.440 --> 00:10:15.290 align:start position:0% a lot of stuff uh then I'm doing mostly front-end<00:10:13.920> back-end<00:10:14.459> infrastructure<00:10:14.940> like<00:10:15.120> I 00:10:15.290 --> 00:10:15.300 align:start position:0% front-end back-end infrastructure like I 00:10:15.300 --> 00:10:17.210 align:start position:0% front-end back-end infrastructure like I said<00:10:15.420> then<00:10:15.720> we<00:10:15.899> have<00:10:16.019> jabir<00:10:16.560> that<00:10:16.860> handles 00:10:17.210 --> 00:10:17.220 align:start position:0% said then we have jabir that handles 00:10:17.220 --> 00:10:19.070 align:start position:0% said then we have jabir that handles also<00:10:17.760> backend 00:10:19.070 --> 00:10:19.080 align:start position:0% also backend 00:10:19.080 --> 00:10:23.690 align:start position:0% also backend uh<00:10:19.980> lucky<00:10:20.339> is<00:10:21.060> working<00:10:21.420> with<00:10:21.720> me<00:10:21.839> on<00:10:22.019> front<00:10:22.200> end 00:10:23.690 --> 00:10:23.700 align:start position:0% uh lucky is working with me on front end 00:10:23.700 --> 00:10:26.449 align:start position:0% uh lucky is working with me on front end and<00:10:24.360> his<00:10:24.600> has<00:10:24.839> been<00:10:25.019> a<00:10:25.140> really<00:10:25.320> great<00:10:25.500> help<00:10:26.040> and 00:10:26.449 --> 00:10:26.459 align:start position:0% and his has been a really great help and 00:10:26.459 --> 00:10:29.150 align:start position:0% and his has been a really great help and then<00:10:26.580> we<00:10:26.820> have<00:10:27.000> Isaac<00:10:27.600> and<00:10:27.959> Alexi<00:10:28.680> which<00:10:28.920> are 00:10:29.150 --> 00:10:29.160 align:start position:0% then we have Isaac and Alexi which are 00:10:29.160 --> 00:10:30.949 align:start position:0% then we have Isaac and Alexi which are our<00:10:29.279> newest<00:10:29.640> members 00:10:30.949 --> 00:10:30.959 align:start position:0% our newest members 00:10:30.959 --> 00:10:34.310 align:start position:0% our newest members um that<00:10:31.500> uh<00:10:31.800> also<00:10:32.040> do<00:10:32.160> backend<00:10:32.519> and<00:10:33.060> finally 00:10:34.310 --> 00:10:34.320 align:start position:0% um that uh also do backend and finally 00:10:34.320 --> 00:10:36.949 align:start position:0% um that uh also do backend and finally uh<00:10:34.800> Selena<00:10:35.160> left<00:10:35.399> there<00:10:35.519> is<00:10:35.640> wife<00:10:35.820> that<00:10:36.300> really 00:10:36.949 --> 00:10:36.959 align:start position:0% uh Selena left there is wife that really 00:10:36.959 --> 00:10:38.750 align:start position:0% uh Selena left there is wife that really helps<00:10:37.380> us<00:10:37.560> with<00:10:38.160> uh<00:10:38.339> you<00:10:38.519> know<00:10:38.640> the 00:10:38.750 --> 00:10:38.760 align:start position:0% helps us with uh you know the 00:10:38.760 --> 00:10:39.889 align:start position:0% helps us with uh you know the non-technical<00:10:39.240> stuff<00:10:39.420> that<00:10:39.660> the<00:10:39.779> company 00:10:39.889 --> 00:10:39.899 align:start position:0% non-technical stuff that the company 00:10:39.899 --> 00:10:43.070 align:start position:0% non-technical stuff that the company needs<00:10:40.800> and<00:10:41.279> we<00:10:41.519> are<00:10:41.640> really<00:10:41.760> glad<00:10:42.120> to<00:10:42.360> have<00:10:42.480> her 00:10:43.070 --> 00:10:43.080 align:start position:0% needs and we are really glad to have her 00:10:43.080 --> 00:10:44.630 align:start position:0% needs and we are really glad to have her uh<00:10:43.800> so 00:10:44.630 --> 00:10:44.640 align:start position:0% uh so 00:10:44.640 --> 00:10:45.230 align:start position:0% uh so um 00:10:45.230 --> 00:10:45.240 align:start position:0% um 00:10:45.240 --> 00:10:47.329 align:start position:0% um we<00:10:45.720> are<00:10:45.779> building<00:10:45.899> the<00:10:46.079> road<00:10:46.260> key<00:10:46.500> across<00:10:47.040> some 00:10:47.329 --> 00:10:47.339 align:start position:0% we are building the road key across some 00:10:47.339 --> 00:10:50.090 align:start position:0% we are building the road key across some uh<00:10:47.880> like<00:10:48.120> three<00:10:48.360> basic<00:10:48.720> principles 00:10:50.090 --> 00:10:50.100 align:start position:0% uh like three basic principles 00:10:50.100 --> 00:10:52.610 align:start position:0% uh like three basic principles key<00:10:51.000> is<00:10:51.240> open<00:10:51.360> source 00:10:52.610 --> 00:10:52.620 align:start position:0% key is open source 00:10:52.620 --> 00:10:55.910 align:start position:0% key is open source local<00:10:53.220> first<00:10:53.640> and<00:10:54.420> it<00:10:54.540> uses<00:10:54.839> encryption<00:10:55.440> to 00:10:55.910 --> 00:10:55.920 align:start position:0% local first and it uses encryption to 00:10:55.920 --> 00:10:57.290 align:start position:0% local first and it uses encryption to store<00:10:56.040> the<00:10:56.279> data 00:10:57.290 --> 00:10:57.300 align:start position:0% store the data 00:10:57.300 --> 00:11:00.949 align:start position:0% store the data uh<00:10:58.140> with<00:10:58.380> this<00:10:58.620> we<00:10:58.860> can<00:10:59.100> uh<00:11:00.000> guarantee<00:11:00.779> that 00:11:00.949 --> 00:11:00.959 align:start position:0% uh with this we can uh guarantee that 00:11:00.959 --> 00:11:03.350 align:start position:0% uh with this we can uh guarantee that the<00:11:01.260> functionality<00:11:02.220> is<00:11:02.399> transparent<00:11:02.880> like 00:11:03.350 --> 00:11:03.360 align:start position:0% the functionality is transparent like 00:11:03.360 --> 00:11:06.829 align:start position:0% the functionality is transparent like you<00:11:03.959> don't<00:11:04.140> have<00:11:04.560> to<00:11:04.920> actually<00:11:05.100> trust<00:11:05.940> us<00:11:06.120> you 00:11:06.829 --> 00:11:06.839 align:start position:0% you don't have to actually trust us you 00:11:06.839 --> 00:11:09.230 align:start position:0% you don't have to actually trust us you can<00:11:06.899> verify<00:11:07.320> on<00:11:07.740> how<00:11:08.279> we<00:11:08.399> handle<00:11:08.700> your<00:11:08.880> data 00:11:09.230 --> 00:11:09.240 align:start position:0% can verify on how we handle your data 00:11:09.240 --> 00:11:11.930 align:start position:0% can verify on how we handle your data and<00:11:09.899> how<00:11:10.019> the<00:11:10.200> app<00:11:10.320> works<00:11:11.220> because<00:11:11.579> it's<00:11:11.760> a 00:11:11.930 --> 00:11:11.940 align:start position:0% and how the app works because it's a 00:11:11.940 --> 00:11:13.370 align:start position:0% and how the app works because it's a local<00:11:12.060> lab 00:11:13.370 --> 00:11:13.380 align:start position:0% local lab 00:11:13.380 --> 00:11:15.530 align:start position:0% local lab is<00:11:13.620> beyond<00:11:13.980> the<00:11:14.160> data<00:11:14.519> we<00:11:15.060> don't<00:11:15.180> have<00:11:15.360> access 00:11:15.530 --> 00:11:15.540 align:start position:0% is beyond the data we don't have access 00:11:15.540 --> 00:11:17.210 align:start position:0% is beyond the data we don't have access to<00:11:15.779> your<00:11:15.959> data<00:11:16.260> we<00:11:16.440> don't<00:11:16.620> know<00:11:16.860> anything 00:11:17.210 --> 00:11:17.220 align:start position:0% to your data we don't know anything 00:11:17.220 --> 00:11:20.449 align:start position:0% to your data we don't know anything about<00:11:17.519> your<00:11:17.760> data<00:11:18.300> any<00:11:19.260> address<00:11:19.500> any<00:11:20.279> account 00:11:20.449 --> 00:11:20.459 align:start position:0% about your data any address any account 00:11:20.459 --> 00:11:22.550 align:start position:0% about your data any address any account anything<00:11:20.820> you<00:11:21.120> put<00:11:21.300> on<00:11:21.360> rotkey<00:11:21.720> stays<00:11:22.320> locally 00:11:22.550 --> 00:11:22.560 align:start position:0% anything you put on rotkey stays locally 00:11:22.560 --> 00:11:24.170 align:start position:0% anything you put on rotkey stays locally encrypted<00:11:23.220> in<00:11:23.339> the<00:11:23.459> database<00:11:23.820> in<00:11:24.060> your 00:11:24.170 --> 00:11:24.180 align:start position:0% encrypted in the database in your 00:11:24.180 --> 00:11:24.949 align:start position:0% encrypted in the database in your machine 00:11:24.949 --> 00:11:24.959 align:start position:0% machine 00:11:24.959 --> 00:11:27.710 align:start position:0% machine we<00:11:25.620> don't<00:11:25.740> have<00:11:25.920> access<00:11:26.100> to<00:11:26.339> any<00:11:26.519> of<00:11:26.640> that 00:11:27.710 --> 00:11:27.720 align:start position:0% we don't have access to any of that 00:11:27.720 --> 00:11:29.870 align:start position:0% we don't have access to any of that and<00:11:28.200> also<00:11:28.440> you<00:11:28.560> have<00:11:28.740> access<00:11:28.860> to<00:11:29.100> the<00:11:29.220> code<00:11:29.399> if 00:11:29.870 --> 00:11:29.880 align:start position:0% and also you have access to the code if 00:11:29.880 --> 00:11:32.090 align:start position:0% and also you have access to the code if anything<00:11:30.000> happens<00:11:30.300> to<00:11:30.600> us<00:11:30.779> hopefully<00:11:31.740> it<00:11:31.920> will 00:11:32.090 --> 00:11:32.100 align:start position:0% anything happens to us hopefully it will 00:11:32.100 --> 00:11:33.290 align:start position:0% anything happens to us hopefully it will not<00:11:32.220> but<00:11:32.339> if<00:11:32.519> anything<00:11:32.700> happens<00:11:32.940> to<00:11:33.180> us 00:11:33.290 --> 00:11:33.300 align:start position:0% not but if anything happens to us 00:11:33.300 --> 00:11:35.090 align:start position:0% not but if anything happens to us someone<00:11:33.720> can<00:11:34.019> pick<00:11:34.140> up<00:11:34.260> the<00:11:34.440> software<00:11:34.680> and 00:11:35.090 --> 00:11:35.100 align:start position:0% someone can pick up the software and 00:11:35.100 --> 00:11:37.610 align:start position:0% someone can pick up the software and keep<00:11:35.220> providing<00:11:35.640> value<00:11:35.760> to<00:11:35.940> the<00:11:36.120> users 00:11:37.610 --> 00:11:37.620 align:start position:0% keep providing value to the users 00:11:37.620 --> 00:11:39.050 align:start position:0% keep providing value to the users um<00:11:37.680> so<00:11:37.980> let's<00:11:38.220> talk<00:11:38.399> about<00:11:38.519> terrific 00:11:39.050 --> 00:11:39.060 align:start position:0% um so let's talk about terrific 00:11:39.060 --> 00:11:41.449 align:start position:0% um so let's talk about terrific architecture<00:11:39.660> uh<00:11:40.440> rodkey<00:11:40.920> is<00:11:41.100> split<00:11:41.399> into 00:11:41.449 --> 00:11:41.459 align:start position:0% architecture uh rodkey is split into 00:11:41.459 --> 00:11:42.829 align:start position:0% architecture uh rodkey is split into parts 00:11:42.829 --> 00:11:42.839 align:start position:0% parts 00:11:42.839 --> 00:11:44.870 align:start position:0% parts one<00:11:43.200> is<00:11:43.320> the<00:11:43.440> python<00:11:43.740> backend<00:11:44.160> and<00:11:44.640> the<00:11:44.760> other 00:11:44.870 --> 00:11:44.880 align:start position:0% one is the python backend and the other 00:11:44.880 --> 00:11:46.490 align:start position:0% one is the python backend and the other is<00:11:45.060> the<00:11:45.180> front<00:11:45.360> end<00:11:45.540> the<00:11:45.899> front<00:11:46.079> is<00:11:46.260> really 00:11:46.490 --> 00:11:46.500 align:start position:0% is the front end the front is really 00:11:46.500 --> 00:11:49.069 align:start position:0% is the front end the front is really simple<00:11:46.740> just<00:11:47.040> calls<00:11:47.459> the<00:11:47.579> back<00:11:47.700> end<00:11:47.880> and<00:11:48.720> it's 00:11:49.069 --> 00:11:49.079 align:start position:0% simple just calls the back end and it's 00:11:49.079 --> 00:11:51.110 align:start position:0% simple just calls the back end and it's what<00:11:49.260> you<00:11:49.380> see<00:11:49.560> when<00:11:49.740> you<00:11:49.860> open<00:11:49.980> the<00:11:50.160> app<00:11:50.339> uh 00:11:51.110 --> 00:11:51.120 align:start position:0% what you see when you open the app uh 00:11:51.120 --> 00:11:52.970 align:start position:0% what you see when you open the app uh the<00:11:51.300> backend<00:11:51.660> does<00:11:51.899> all<00:11:52.140> the<00:11:52.260> data<00:11:52.560> processing 00:11:52.970 --> 00:11:52.980 align:start position:0% the backend does all the data processing 00:11:52.980 --> 00:11:56.810 align:start position:0% the backend does all the data processing it<00:11:53.519> calls<00:11:54.060> open<00:11:54.420> apis<00:11:54.959> uh<00:11:55.920> open<00:11:56.100> nodes<00:11:56.519> or 00:11:56.810 --> 00:11:56.820 align:start position:0% it calls open apis uh open nodes or 00:11:56.820 --> 00:11:58.910 align:start position:0% it calls open apis uh open nodes or maybe<00:11:56.940> you<00:11:57.180> can<00:11:57.300> also<00:11:57.720> add<00:11:58.140> your<00:11:58.320> local<00:11:58.560> nodes 00:11:58.910 --> 00:11:58.920 align:start position:0% maybe you can also add your local nodes 00:11:58.920 --> 00:12:01.490 align:start position:0% maybe you can also add your local nodes so<00:11:59.459> if<00:11:59.640> you<00:11:59.700> run<00:11:59.880> in<00:12:00.120> your<00:12:00.480> own<00:12:00.600> ethereum<00:12:01.079> node 00:12:01.490 --> 00:12:01.500 align:start position:0% so if you run in your own ethereum node 00:12:01.500 --> 00:12:03.889 align:start position:0% so if you run in your own ethereum node uh<00:12:02.220> a<00:12:02.399> lot<00:12:02.640> he<00:12:02.820> can<00:12:02.940> hit<00:12:03.120> it<00:12:03.300> and<00:12:03.480> it<00:12:03.660> will<00:12:03.779> be 00:12:03.889 --> 00:12:03.899 align:start position:0% uh a lot he can hit it and it will be 00:12:03.899 --> 00:12:05.509 align:start position:0% uh a lot he can hit it and it will be immensely<00:12:04.560> faster<00:12:04.800> than<00:12:05.040> hitting<00:12:05.399> public 00:12:05.509 --> 00:12:05.519 align:start position:0% immensely faster than hitting public 00:12:05.519 --> 00:12:06.829 align:start position:0% immensely faster than hitting public notes 00:12:06.829 --> 00:12:06.839 align:start position:0% notes 00:12:06.839 --> 00:12:09.710 align:start position:0% notes uh<00:12:07.800> and<00:12:08.100> then<00:12:08.160> you<00:12:08.399> have<00:12:08.640> uh<00:12:08.880> two<00:12:09.120> databases 00:12:09.710 --> 00:12:09.720 align:start position:0% uh and then you have uh two databases 00:12:09.720 --> 00:12:11.990 align:start position:0% uh and then you have uh two databases one<00:12:10.440> is<00:12:10.560> the<00:12:10.680> encrypted<00:12:11.040> user<00:12:11.339> DB<00:12:11.579> that<00:12:11.760> uses 00:12:11.990 --> 00:12:12.000 align:start position:0% one is the encrypted user DB that uses 00:12:12.000 --> 00:12:16.730 align:start position:0% one is the encrypted user DB that uses SQL<00:12:12.779> Cipher<00:12:13.200> to<00:12:13.440> uh<00:12:13.980> encrypt<00:12:15.060> and<00:12:15.660> this 00:12:16.730 --> 00:12:16.740 align:start position:0% SQL Cipher to uh encrypt and this 00:12:16.740 --> 00:12:19.730 align:start position:0% SQL Cipher to uh encrypt and this is<00:12:17.220> where<00:12:17.519> your<00:12:17.700> private<00:12:18.000> data<00:12:18.420> stays<00:12:19.260> and 00:12:19.730 --> 00:12:19.740 align:start position:0% is where your private data stays and 00:12:19.740 --> 00:12:21.290 align:start position:0% is where your private data stays and then<00:12:19.860> we<00:12:19.980> have<00:12:20.100> the<00:12:20.160> global<00:12:20.399> DB<00:12:20.700> that<00:12:20.880> usually 00:12:21.290 --> 00:12:21.300 align:start position:0% then we have the global DB that usually 00:12:21.300 --> 00:12:22.910 align:start position:0% then we have the global DB that usually has<00:12:21.480> asset<00:12:21.839> information 00:12:22.910 --> 00:12:22.920 align:start position:0% has asset information 00:12:22.920 --> 00:12:26.810 align:start position:0% has asset information uh<00:12:23.760> the<00:12:24.060> way<00:12:24.120> we<00:12:24.240> package<00:12:24.800> uh<00:12:25.800> is<00:12:25.980> the<00:12:26.100> wa<00:12:26.279> so<00:12:26.640> we 00:12:26.810 --> 00:12:26.820 align:start position:0% uh the way we package uh is the wa so we 00:12:26.820 --> 00:12:28.009 align:start position:0% uh the way we package uh is the wa so we have<00:12:26.880> an<00:12:27.000> electron<00:12:27.300> app<00:12:27.540> that<00:12:27.720> is<00:12:27.839> available 00:12:28.009 --> 00:12:28.019 align:start position:0% have an electron app that is available 00:12:28.019 --> 00:12:29.690 align:start position:0% have an electron app that is available for<00:12:28.380> Mac<00:12:28.680> OS 00:12:29.690 --> 00:12:29.700 align:start position:0% for Mac OS 00:12:29.700 --> 00:12:32.630 align:start position:0% for Mac OS Linux<00:12:30.660> and<00:12:30.959> windows<00:12:31.500> and<00:12:32.040> we<00:12:32.220> now<00:12:32.399> Support 00:12:32.630 --> 00:12:32.640 align:start position:0% Linux and windows and we now Support 00:12:32.640 --> 00:12:34.190 align:start position:0% Linux and windows and we now Support also 00:12:34.190 --> 00:12:34.200 align:start position:0% also 00:12:34.200 --> 00:12:38.569 align:start position:0% also um<00:12:34.339> arms<00:12:35.339> uh<00:12:36.000> Apple<00:12:36.420> silicon<00:12:36.959> Max 00:12:38.569 --> 00:12:38.579 align:start position:0% um arms uh Apple silicon Max 00:12:38.579 --> 00:12:41.269 align:start position:0% um arms uh Apple silicon Max um<00:12:38.640> and<00:12:39.000> then<00:12:39.120> we<00:12:39.360> have<00:12:39.540> uh<00:12:40.079> the<00:12:40.620> Dockery<00:12:40.920> mods 00:12:41.269 --> 00:12:41.279 align:start position:0% um and then we have uh the Dockery mods 00:12:41.279 --> 00:12:43.009 align:start position:0% um and then we have uh the Dockery mods where<00:12:41.700> you<00:12:42.000> can<00:12:42.120> deploy<00:12:42.360> on<00:12:42.480> a<00:12:42.600> machine<00:12:42.779> you 00:12:43.009 --> 00:12:43.019 align:start position:0% where you can deploy on a machine you 00:12:43.019 --> 00:12:44.990 align:start position:0% where you can deploy on a machine you control<00:12:43.200> and<00:12:43.680> you<00:12:43.740> can<00:12:43.920> access<00:12:44.040> it<00:12:44.339> via<00:12:44.820> web 00:12:44.990 --> 00:12:45.000 align:start position:0% control and you can access it via web 00:12:45.000 --> 00:12:46.850 align:start position:0% control and you can access it via web although<00:12:45.779> you<00:12:45.899> should<00:12:46.139> be<00:12:46.440> careful<00:12:46.680> there 00:12:46.850 --> 00:12:46.860 align:start position:0% although you should be careful there 00:12:46.860 --> 00:12:49.670 align:start position:0% although you should be careful there because<00:12:47.040> rotkey<00:12:47.579> was<00:12:47.959> foremostly<00:12:48.959> designed 00:12:49.670 --> 00:12:49.680 align:start position:0% because rotkey was foremostly designed 00:12:49.680 --> 00:12:51.530 align:start position:0% because rotkey was foremostly designed as<00:12:49.980> a<00:12:50.160> local<00:12:50.279> app 00:12:51.530 --> 00:12:51.540 align:start position:0% as a local app 00:12:51.540 --> 00:12:53.030 align:start position:0% as a local app so<00:12:51.899> it<00:12:52.019> would<00:12:52.139> be<00:12:52.260> better<00:12:52.440> if<00:12:52.680> you<00:12:52.800> have<00:12:52.920> a 00:12:53.030 --> 00:12:53.040 align:start position:0% so it would be better if you have a 00:12:53.040 --> 00:12:55.250 align:start position:0% so it would be better if you have a proxy<00:12:53.339> in<00:12:53.459> the<00:12:53.639> front<00:12:53.899> uh<00:12:54.899> for<00:12:55.079> security 00:12:55.250 --> 00:12:55.260 align:start position:0% proxy in the front uh for security 00:12:55.260 --> 00:12:58.430 align:start position:0% proxy in the front uh for security reasons<00:12:56.279> uh<00:12:56.940> and<00:12:57.180> then<00:12:57.360> there<00:12:57.660> is<00:12:57.839> another<00:12:58.019> way 00:12:58.430 --> 00:12:58.440 align:start position:0% reasons uh and then there is another way 00:12:58.440 --> 00:13:01.069 align:start position:0% reasons uh and then there is another way to<00:12:58.740> bar<00:12:58.920> and<00:12:59.220> rotkey<00:12:59.519> if<00:13:00.300> you<00:13:00.420> own<00:13:00.720> the<00:13:00.899> dub 00:13:01.069 --> 00:13:01.079 align:start position:0% to bar and rotkey if you own the dub 00:13:01.079 --> 00:13:03.050 align:start position:0% to bar and rotkey if you own the dub node<00:13:01.320> there<00:13:01.560> is<00:13:01.620> a<00:13:01.740> top<00:13:01.800> note<00:13:02.040> packets<00:13:02.399> and<00:13:02.880> we 00:13:03.050 --> 00:13:03.060 align:start position:0% node there is a top note packets and we 00:13:03.060 --> 00:13:04.790 align:start position:0% node there is a top note packets and we are<00:13:03.180> in<00:13:03.300> close<00:13:03.480> collaboration<00:13:03.959> with<00:13:04.200> dubnod 00:13:04.790 --> 00:13:04.800 align:start position:0% are in close collaboration with dubnod 00:13:04.800 --> 00:13:07.910 align:start position:0% are in close collaboration with dubnod which<00:13:05.519> makes<00:13:05.880> things<00:13:06.120> really<00:13:06.420> easier<00:13:06.959> and<00:13:07.800> we 00:13:07.910 --> 00:13:07.920 align:start position:0% which makes things really easier and we 00:13:07.920 --> 00:13:09.650 align:start position:0% which makes things really easier and we want<00:13:08.040> to<00:13:08.160> improve<00:13:08.459> the<00:13:08.579> experience<00:13:09.120> there<00:13:09.300> so 00:13:09.650 --> 00:13:09.660 align:start position:0% want to improve the experience there so 00:13:09.660 --> 00:13:11.990 align:start position:0% want to improve the experience there so for<00:13:09.839> example<00:13:10.079> we<00:13:10.680> are<00:13:10.860> working<00:13:11.040> to<00:13:11.339> make<00:13:11.519> Auto 00:13:11.990 --> 00:13:12.000 align:start position:0% for example we are working to make Auto 00:13:12.000 --> 00:13:14.389 align:start position:0% for example we are working to make Auto configuring<00:13:12.600> your<00:13:13.019> local<00:13:13.440> nodes<00:13:13.800> in<00:13:13.980> rodkey 00:13:14.389 --> 00:13:14.399 align:start position:0% configuring your local nodes in rodkey 00:13:14.399 --> 00:13:18.410 align:start position:0% configuring your local nodes in rodkey uh<00:13:15.240> automatic<00:13:15.980> uh<00:13:16.980> so<00:13:17.279> uh<00:13:17.880> rodky<00:13:18.360> does 00:13:18.410 --> 00:13:18.420 align:start position:0% uh automatic uh so uh rodky does 00:13:18.420 --> 00:13:19.870 align:start position:0% uh automatic uh so uh rodky does portfolio<00:13:18.839> tracking 00:13:19.870 --> 00:13:19.880 align:start position:0% portfolio tracking 00:13:19.880 --> 00:13:22.730 align:start position:0% portfolio tracking at<00:13:20.880> the<00:13:21.000> moment<00:13:21.120> we<00:13:21.420> support<00:13:21.600> ethereum<00:13:22.200> kusama 00:13:22.730 --> 00:13:22.740 align:start position:0% at the moment we support ethereum kusama 00:13:22.740 --> 00:13:26.030 align:start position:0% at the moment we support ethereum kusama polka<00:13:23.279> dot<00:13:23.579> Avalanche<00:13:24.240> uh<00:13:25.139> Bitcoin<00:13:25.620> cast<00:13:25.740> and 00:13:26.030 --> 00:13:26.040 align:start position:0% polka dot Avalanche uh Bitcoin cast and 00:13:26.040 --> 00:13:27.650 align:start position:0% polka dot Avalanche uh Bitcoin cast and Bitcoin<00:13:26.459> along<00:13:27.000> with<00:13:27.240> a<00:13:27.420> number<00:13:27.540> of 00:13:27.650 --> 00:13:27.660 align:start position:0% Bitcoin along with a number of 00:13:27.660 --> 00:13:30.590 align:start position:0% Bitcoin along with a number of centralized<00:13:28.200> extensions<00:13:28.680> nd5<00:13:29.040> protocols 00:13:30.590 --> 00:13:30.600 align:start position:0% centralized extensions nd5 protocols 00:13:30.600 --> 00:13:34.250 align:start position:0% centralized extensions nd5 protocols uh<00:13:31.440> in<00:13:31.620> the<00:13:31.800> next<00:13:31.920> release<00:13:32.160> uh<00:13:33.000> in<00:13:33.360> this<00:13:33.540> we<00:13:34.139> are 00:13:34.250 --> 00:13:34.260 align:start position:0% uh in the next release uh in this we are 00:13:34.260 --> 00:13:36.710 align:start position:0% uh in the next release uh in this we are doing<00:13:34.380> work<00:13:34.620> so<00:13:35.220> that<00:13:35.459> it<00:13:35.700> makes<00:13:36.240> it<00:13:36.420> easier 00:13:36.710 --> 00:13:36.720 align:start position:0% doing work so that it makes it easier 00:13:36.720 --> 00:13:39.829 align:start position:0% doing work so that it makes it easier for<00:13:36.899> us<00:13:37.019> to<00:13:37.320> support<00:13:37.500> multiple<00:13:38.220> VM<00:13:38.639> chains<00:13:39.060> so 00:13:39.829 --> 00:13:39.839 align:start position:0% for us to support multiple VM chains so 00:13:39.839 --> 00:13:42.350 align:start position:0% for us to support multiple VM chains so slowly<00:13:40.260> we<00:13:40.560> will<00:13:40.740> start<00:13:41.040> adding<00:13:41.459> support<00:13:41.760> for 00:13:42.350 --> 00:13:42.360 align:start position:0% slowly we will start adding support for 00:13:42.360 --> 00:13:44.329 align:start position:0% slowly we will start adding support for multiple<00:13:43.019> VM<00:13:43.320> chains<00:13:43.680> starting<00:13:44.100> with 00:13:44.329 --> 00:13:44.339 align:start position:0% multiple VM chains starting with 00:13:44.339 --> 00:13:45.829 align:start position:0% multiple VM chains starting with optimism 00:13:45.829 --> 00:13:45.839 align:start position:0% optimism 00:13:45.839 --> 00:13:47.690 align:start position:0% optimism so<00:13:46.320> uh<00:13:46.620> indirectly<00:13:47.160> you<00:13:47.279> can<00:13:47.399> see<00:13:47.519> your 00:13:47.690 --> 00:13:47.700 align:start position:0% so uh indirectly you can see your 00:13:47.700 --> 00:13:49.610 align:start position:0% so uh indirectly you can see your account<00:13:47.880> history<00:13:48.120> Lefteris<00:13:48.899> had<00:13:49.079> the<00:13:49.260> token 00:13:49.610 --> 00:13:49.620 align:start position:0% account history Lefteris had the token 00:13:49.620 --> 00:13:52.610 align:start position:0% account history Lefteris had the token uh<00:13:50.220> Tuesday<00:13:50.940> talking<00:13:51.600> about<00:13:51.899> how<00:13:52.320> we<00:13:52.440> do 00:13:52.610 --> 00:13:52.620 align:start position:0% uh Tuesday talking about how we do 00:13:52.620 --> 00:13:55.310 align:start position:0% uh Tuesday talking about how we do transaction<00:13:52.980> decoding<00:13:53.579> here<00:13:54.240> you<00:13:54.480> can<00:13:54.600> see 00:13:55.310 --> 00:13:55.320 align:start position:0% transaction decoding here you can see 00:13:55.320 --> 00:13:59.210 align:start position:0% transaction decoding here you can see how<00:13:56.160> this<00:13:56.459> looks<00:13:56.880> inside<00:13:57.120> the<00:13:57.420> app 00:13:59.210 --> 00:13:59.220 align:start position:0% how this looks inside the app 00:13:59.220 --> 00:14:02.389 align:start position:0% how this looks inside the app in<00:13:59.820> this<00:13:59.880> example<00:14:00.180> you<00:14:00.600> can<00:14:00.720> see<00:14:00.899> me<00:14:01.399> basically 00:14:02.389 --> 00:14:02.399 align:start position:0% in this example you can see me basically 00:14:02.399 --> 00:14:05.389 align:start position:0% in this example you can see me basically migrating<00:14:03.079> 400<00:14:04.079> side<00:14:04.380> to<00:14:04.740> die<00:14:04.920> and<00:14:05.160> then 00:14:05.389 --> 00:14:05.399 align:start position:0% migrating 400 side to die and then 00:14:05.399 --> 00:14:09.889 align:start position:0% migrating 400 side to die and then selling<00:14:06.180> them<00:14:06.300> for<00:14:06.480> 1.7<00:14:07.380> nif<00:14:07.920> on<00:14:08.160> kyber 00:14:09.889 --> 00:14:09.899 align:start position:0% selling them for 1.7 nif on kyber 00:14:09.899 --> 00:14:13.069 align:start position:0% selling them for 1.7 nif on kyber uh<00:14:10.560> then<00:14:10.800> we<00:14:10.980> have<00:14:11.100> accounting<00:14:11.579> uh 00:14:13.069 --> 00:14:13.079 align:start position:0% uh then we have accounting uh 00:14:13.079 --> 00:14:16.370 align:start position:0% uh then we have accounting uh Accounting<00:14:13.680> in<00:14:13.800> red<00:14:13.980> key<00:14:14.220> is<00:14:14.399> customizable<00:14:15.380> uh 00:14:16.370 --> 00:14:16.380 align:start position:0% Accounting in red key is customizable uh 00:14:16.380 --> 00:14:19.190 align:start position:0% Accounting in red key is customizable uh we<00:14:16.800> try<00:14:16.980> to<00:14:17.279> be<00:14:17.639> as<00:14:18.120> general<00:14:18.300> as<00:14:18.600> we<00:14:18.779> can<00:14:18.899> so 00:14:19.190 --> 00:14:19.200 align:start position:0% we try to be as general as we can so 00:14:19.200 --> 00:14:20.569 align:start position:0% we try to be as general as we can so that<00:14:19.380> we<00:14:19.680> can<00:14:19.860> support<00:14:19.980> as<00:14:20.339> many 00:14:20.569 --> 00:14:20.579 align:start position:0% that we can support as many 00:14:20.579 --> 00:14:22.970 align:start position:0% that we can support as many jurisdictions<00:14:21.180> uh<00:14:22.139> you<00:14:22.320> can<00:14:22.440> parameterize 00:14:22.970 --> 00:14:22.980 align:start position:0% jurisdictions uh you can parameterize 00:14:22.980 --> 00:14:25.490 align:start position:0% jurisdictions uh you can parameterize how<00:14:23.399> you<00:14:23.519> generate<00:14:23.880> your<00:14:24.000> p<00:14:24.180> l<00:14:24.420> report 00:14:25.490 --> 00:14:25.500 align:start position:0% how you generate your p l report 00:14:25.500 --> 00:14:28.129 align:start position:0% how you generate your p l report and<00:14:25.860> then<00:14:25.980> you<00:14:26.160> can<00:14:26.279> export<00:14:26.639> the<00:14:26.820> CSV<00:14:27.240> that<00:14:28.019> you 00:14:28.129 --> 00:14:28.139 align:start position:0% and then you can export the CSV that you 00:14:28.139 --> 00:14:30.170 align:start position:0% and then you can export the CSV that you can<00:14:28.260> pass<00:14:28.620> to<00:14:28.800> your<00:14:28.980> accountant<00:14:29.339> and<00:14:29.880> do<00:14:30.000> your 00:14:30.170 --> 00:14:30.180 align:start position:0% can pass to your accountant and do your 00:14:30.180 --> 00:14:31.750 align:start position:0% can pass to your accountant and do your tax<00:14:30.300> record 00:14:31.750 --> 00:14:31.760 align:start position:0% tax record 00:14:31.760 --> 00:14:34.670 align:start position:0% tax record another<00:14:32.760> great<00:14:33.420> feature<00:14:33.720> we<00:14:33.839> have<00:14:34.019> is<00:14:34.380> uh 00:14:34.670 --> 00:14:34.680 align:start position:0% another great feature we have is uh 00:14:34.680 --> 00:14:38.230 align:start position:0% another great feature we have is uh ethereum<00:14:35.220> selecting<00:14:35.639> you<00:14:36.540> can<00:14:36.660> see<00:14:36.959> your 00:14:38.230 --> 00:14:38.240 align:start position:0% ethereum selecting you can see your 00:14:38.240 --> 00:14:40.670 align:start position:0% ethereum selecting you can see your stickers<00:14:39.240> performance<00:14:39.720> you<00:14:40.199> can<00:14:40.320> see<00:14:40.440> your 00:14:40.670 --> 00:14:40.680 align:start position:0% stickers performance you can see your 00:14:40.680 --> 00:14:43.129 align:start position:0% stickers performance you can see your daily<00:14:40.800> stats<00:14:41.339> and<00:14:42.180> you<00:14:42.360> can<00:14:42.420> see<00:14:42.600> aggregated 00:14:43.129 --> 00:14:43.139 align:start position:0% daily stats and you can see aggregated 00:14:43.139 --> 00:14:45.290 align:start position:0% daily stats and you can see aggregated information<00:14:43.440> about<00:14:43.860> everything<00:14:44.100> and<00:14:45.060> another 00:14:45.290 --> 00:14:45.300 align:start position:0% information about everything and another 00:14:45.300 --> 00:14:48.170 align:start position:0% information about everything and another part<00:14:45.660> of<00:14:45.779> rotkey<00:14:46.199> is<00:14:46.500> insights<00:14:47.519> um 00:14:48.170 --> 00:14:48.180 align:start position:0% part of rotkey is insights um 00:14:48.180 --> 00:14:51.470 align:start position:0% part of rotkey is insights um so<00:14:48.720> we<00:14:49.019> have<00:14:49.139> graphs<00:14:49.620> for<00:14:49.800> statistics<00:14:50.480> uh 00:14:51.470 --> 00:14:51.480 align:start position:0% so we have graphs for statistics uh 00:14:51.480 --> 00:14:53.150 align:start position:0% so we have graphs for statistics uh although<00:14:52.019> they<00:14:52.260> are<00:14:52.380> a<00:14:52.500> bit<00:14:52.560> problematic 00:14:53.150 --> 00:14:53.160 align:start position:0% although they are a bit problematic 00:14:53.160 --> 00:14:55.069 align:start position:0% although they are a bit problematic because<00:14:53.699> you<00:14:53.940> have<00:14:54.060> to<00:14:54.180> open<00:14:54.300> the<00:14:54.540> app<00:14:54.779> every 00:14:55.069 --> 00:14:55.079 align:start position:0% because you have to open the app every 00:14:55.079 --> 00:14:58.490 align:start position:0% because you have to open the app every day<00:14:55.320> so<00:14:55.800> that<00:14:56.000> we<00:14:57.000> don't<00:14:57.240> rely<00:14:57.959> at<00:14:58.199> the<00:14:58.320> moment 00:14:58.490 --> 00:14:58.500 align:start position:0% day so that we don't rely at the moment 00:14:58.500 --> 00:15:01.310 align:start position:0% day so that we don't rely at the moment on<00:14:59.339> uh<00:14:59.880> tank<00:15:00.120> history<00:15:00.360> because<00:15:00.720> that's<00:15:01.019> quite 00:15:01.310 --> 00:15:01.320 align:start position:0% on uh tank history because that's quite 00:15:01.320 --> 00:15:03.110 align:start position:0% on uh tank history because that's quite hard<00:15:01.560> although<00:15:02.220> we<00:15:02.339> want<00:15:02.519> to<00:15:02.639> do<00:15:02.760> that<00:15:02.880> in<00:15:03.000> the 00:15:03.110 --> 00:15:03.120 align:start position:0% hard although we want to do that in the 00:15:03.120 --> 00:15:05.329 align:start position:0% hard although we want to do that in the future<00:15:03.240> but<00:15:04.079> at<00:15:04.260> the<00:15:04.380> moment<00:15:04.500> we<00:15:04.920> depend<00:15:05.220> on 00:15:05.329 --> 00:15:05.339 align:start position:0% future but at the moment we depend on 00:15:05.339 --> 00:15:07.670 align:start position:0% future but at the moment we depend on snapshots<00:15:05.820> so<00:15:06.300> you<00:15:06.480> have<00:15:06.660> to<00:15:06.899> open<00:15:07.320> the<00:15:07.500> app 00:15:07.670 --> 00:15:07.680 align:start position:0% snapshots so you have to open the app 00:15:07.680 --> 00:15:11.509 align:start position:0% snapshots so you have to open the app every<00:15:07.920> day<00:15:08.180> so<00:15:09.180> that<00:15:09.360> the<00:15:09.540> app<00:15:09.720> can<00:15:10.019> uh<00:15:10.560> collect 00:15:11.509 --> 00:15:11.519 align:start position:0% every day so that the app can uh collect 00:15:11.519 --> 00:15:12.769 align:start position:0% every day so that the app can uh collect this<00:15:11.639> snapshots 00:15:12.769 --> 00:15:12.779 align:start position:0% this snapshots 00:15:12.779 --> 00:15:15.530 align:start position:0% this snapshots this<00:15:13.560> is<00:15:13.680> important<00:15:14.220> like 00:15:15.530 --> 00:15:15.540 align:start position:0% this is important like 00:15:15.540 --> 00:15:18.170 align:start position:0% this is important like if<00:15:16.019> you<00:15:16.199> value<00:15:16.380> your<00:15:16.740> privacy<00:15:17.100> please<00:15:17.699> run<00:15:18.060> the 00:15:18.170 --> 00:15:18.180 align:start position:0% if you value your privacy please run the 00:15:18.180 --> 00:15:21.170 align:start position:0% if you value your privacy please run the full<00:15:18.360> node<00:15:18.660> like<00:15:19.199> it's<00:15:20.160> really<00:15:20.699> important<00:15:21.000> for 00:15:21.170 --> 00:15:21.180 align:start position:0% full node like it's really important for 00:15:21.180 --> 00:15:23.750 align:start position:0% full node like it's really important for us<00:15:21.300> and<00:15:21.899> you<00:15:22.500> know<00:15:22.620> like<00:15:22.800> an<00:15:23.220> easy<00:15:23.339> way<00:15:23.579> would 00:15:23.750 --> 00:15:23.760 align:start position:0% us and you know like an easy way would 00:15:23.760 --> 00:15:26.150 align:start position:0% us and you know like an easy way would be<00:15:23.880> to<00:15:24.120> you<00:15:24.360> know<00:15:24.420> get<00:15:24.660> your<00:15:24.839> dub<00:15:25.199> node<00:15:25.500> uh<00:15:25.920> have 00:15:26.150 --> 00:15:26.160 align:start position:0% be to you know get your dub node uh have 00:15:26.160 --> 00:15:28.189 align:start position:0% be to you know get your dub node uh have your<00:15:26.339> full<00:15:26.579> node<00:15:27.000> like<00:15:27.180> running<00:15:27.420> GIF<00:15:28.019> or 00:15:28.189 --> 00:15:28.199 align:start position:0% your full node like running GIF or 00:15:28.199 --> 00:15:31.129 align:start position:0% your full node like running GIF or rarely<00:15:28.620> gone<00:15:28.800> or<00:15:29.339> never<00:15:29.519> mind<00:15:29.760> and<00:15:30.480> then<00:15:30.600> you 00:15:31.129 --> 00:15:31.139 align:start position:0% rarely gone or never mind and then you 00:15:31.139 --> 00:15:32.930 align:start position:0% rarely gone or never mind and then you can<00:15:31.260> use<00:15:31.440> true<00:15:31.740> blocks<00:15:32.160> as<00:15:32.399> an<00:15:32.519> indexer 00:15:32.930 --> 00:15:32.940 align:start position:0% can use true blocks as an indexer 00:15:32.940 --> 00:15:34.310 align:start position:0% can use true blocks as an indexer because 00:15:34.310 --> 00:15:34.320 align:start position:0% because 00:15:34.320 --> 00:15:35.810 align:start position:0% because I<00:15:34.800> mean<00:15:34.920> look<00:15:35.040> at<00:15:35.220> the<00:15:35.339> moment<00:15:35.399> we<00:15:35.639> have<00:15:35.760> a 00:15:35.810 --> 00:15:35.820 align:start position:0% I mean look at the moment we have a 00:15:35.820 --> 00:15:36.530 align:start position:0% I mean look at the moment we have a problem 00:15:36.530 --> 00:15:36.540 align:start position:0% problem 00:15:36.540 --> 00:15:38.689 align:start position:0% problem uh<00:15:37.079> because<00:15:37.320> there<00:15:37.560> is<00:15:37.740> no<00:15:37.860> easy<00:15:38.040> way<00:15:38.279> to<00:15:38.519> get 00:15:38.689 --> 00:15:38.699 align:start position:0% uh because there is no easy way to get 00:15:38.699 --> 00:15:41.509 align:start position:0% uh because there is no easy way to get an<00:15:39.060> account<00:15:39.240> transactions 00:15:41.509 --> 00:15:41.519 align:start position:0% an account transactions 00:15:41.519 --> 00:15:44.090 align:start position:0% an account transactions we<00:15:41.940> have<00:15:42.060> to<00:15:42.180> rely<00:15:42.300> on<00:15:42.480> either<00:15:42.660> scan 00:15:44.090 --> 00:15:44.100 align:start position:0% we have to rely on either scan 00:15:44.100 --> 00:15:45.170 align:start position:0% we have to rely on either scan and 00:15:45.170 --> 00:15:45.180 align:start position:0% and 00:15:45.180 --> 00:15:47.930 align:start position:0% and this<00:15:45.660> can<00:15:45.779> be<00:15:45.899> problematic<00:15:46.440> from<00:15:46.800> a<00:15:46.940> privacy 00:15:47.930 --> 00:15:47.940 align:start position:0% this can be problematic from a privacy 00:15:47.940 --> 00:15:49.069 align:start position:0% this can be problematic from a privacy perspective 00:15:49.069 --> 00:15:49.079 align:start position:0% perspective 00:15:49.079 --> 00:15:52.910 align:start position:0% perspective because<00:15:49.500> if<00:15:50.279> there's<00:15:50.459> the<00:15:51.180> rate<00:15:51.480> limits<00:15:51.959> you 00:15:52.910 --> 00:15:52.920 align:start position:0% because if there's the rate limits you 00:15:52.920 --> 00:15:54.829 align:start position:0% because if there's the rate limits you and<00:15:53.160> you<00:15:53.339> have<00:15:53.459> to<00:15:53.519> put<00:15:53.639> an<00:15:53.760> API<00:15:54.060> key 00:15:54.829 --> 00:15:54.839 align:start position:0% and you have to put an API key 00:15:54.839 --> 00:15:57.530 align:start position:0% and you have to put an API key and<00:15:55.440> if<00:15:55.860> you<00:15:55.980> put<00:15:56.100> an<00:15:56.220> API<00:15:56.519> key<00:15:56.699> you<00:15:57.060> basically 00:15:57.530 --> 00:15:57.540 align:start position:0% and if you put an API key you basically 00:15:57.540 --> 00:15:59.269 align:start position:0% and if you put an API key you basically connect<00:15:57.720> all<00:15:57.959> your<00:15:58.199> information<00:15:58.500> like<00:15:58.980> your 00:15:59.269 --> 00:15:59.279 align:start position:0% connect all your information like your 00:15:59.279 --> 00:16:00.490 align:start position:0% connect all your information like your email<00:15:59.459> address 00:16:00.490 --> 00:16:00.500 align:start position:0% email address 00:16:00.500 --> 00:16:03.769 align:start position:0% email address your<00:16:01.500> IP<00:16:01.740> address<00:16:01.980> your<00:16:02.579> account<00:16:02.779> and 00:16:03.769 --> 00:16:03.779 align:start position:0% your IP address your account and 00:16:03.779 --> 00:16:06.470 align:start position:0% your IP address your account and probably<00:16:04.019> they<00:16:04.440> they<00:16:05.100> have<00:16:05.820> a<00:16:06.000> good<00:16:06.060> privacy 00:16:06.470 --> 00:16:06.480 align:start position:0% probably they they have a good privacy 00:16:06.480 --> 00:16:07.670 align:start position:0% probably they they have a good privacy policy<00:16:06.779> but<00:16:06.899> you<00:16:07.019> have<00:16:07.079> to<00:16:07.199> trust<00:16:07.380> them<00:16:07.560> for 00:16:07.670 --> 00:16:07.680 align:start position:0% policy but you have to trust them for 00:16:07.680 --> 00:16:10.430 align:start position:0% policy but you have to trust them for that<00:16:07.860> because<00:16:08.100> they<00:16:08.579> are<00:16:08.760> closer<00:16:09.060> software 00:16:10.430 --> 00:16:10.440 align:start position:0% that because they are closer software 00:16:10.440 --> 00:16:12.710 align:start position:0% that because they are closer software so<00:16:10.920> the<00:16:11.160> best<00:16:11.279> idea<00:16:11.579> I<00:16:11.760> would<00:16:11.940> be<00:16:12.420> to<00:16:12.600> have 00:16:12.710 --> 00:16:12.720 align:start position:0% so the best idea I would be to have 00:16:12.720 --> 00:16:14.569 align:start position:0% so the best idea I would be to have something<00:16:12.899> like<00:16:13.079> true<00:16:13.260> blocks<00:16:13.620> running<00:16:13.800> uh 00:16:14.569 --> 00:16:14.579 align:start position:0% something like true blocks running uh 00:16:14.579 --> 00:16:16.790 align:start position:0% something like true blocks running uh and<00:16:14.760> true<00:16:14.940> blocks<00:16:15.300> can<00:16:15.420> index<00:16:15.779> the<00:16:16.019> chain<00:16:16.260> and 00:16:16.790 --> 00:16:16.800 align:start position:0% and true blocks can index the chain and 00:16:16.800 --> 00:16:18.230 align:start position:0% and true blocks can index the chain and can<00:16:16.980> detect<00:16:17.279> a<00:16:17.459> lot<00:16:17.519> of<00:16:17.639> these<00:16:18.060> uh 00:16:18.230 --> 00:16:18.240 align:start position:0% can detect a lot of these uh 00:16:18.240 --> 00:16:20.990 align:start position:0% can detect a lot of these uh transactions<00:16:18.959> uh<00:16:19.680> which<00:16:19.980> content<00:16:20.339> fit<00:16:20.579> to 00:16:20.990 --> 00:16:21.000 align:start position:0% transactions uh which content fit to 00:16:21.000 --> 00:16:24.290 align:start position:0% transactions uh which content fit to rotkey<00:16:21.360> and<00:16:22.079> this<00:16:22.620> way<00:16:22.860> you<00:16:23.160> could<00:16:23.279> do<00:16:23.639> a 00:16:24.290 --> 00:16:24.300 align:start position:0% rotkey and this way you could do a 00:16:24.300 --> 00:16:27.170 align:start position:0% rotkey and this way you could do a really<00:16:24.420> privacy<00:16:25.139> focused<00:16:26.180> portfolio 00:16:27.170 --> 00:16:27.180 align:start position:0% really privacy focused portfolio 00:16:27.180 --> 00:16:29.150 align:start position:0% really privacy focused portfolio tracking<00:16:27.779> and<00:16:27.899> accounting 00:16:29.150 --> 00:16:29.160 align:start position:0% tracking and accounting 00:16:29.160 --> 00:16:30.590 align:start position:0% tracking and accounting just<00:16:29.279> as<00:16:29.579> a<00:16:29.699> bonus 00:16:30.590 --> 00:16:30.600 align:start position:0% just as a bonus 00:16:30.600 --> 00:16:32.870 align:start position:0% just as a bonus you<00:16:31.079> can<00:16:31.260> act<00:16:31.500> if<00:16:31.860> you<00:16:31.980> run<00:16:32.160> Road<00:16:32.399> key<00:16:32.579> on<00:16:32.760> that 00:16:32.870 --> 00:16:32.880 align:start position:0% you can act if you run Road key on that 00:16:32.880 --> 00:16:34.310 align:start position:0% you can act if you run Road key on that note 00:16:34.310 --> 00:16:34.320 align:start position:0% note 00:16:34.320 --> 00:16:36.170 align:start position:0% note if<00:16:34.680> you<00:16:34.860> can<00:16:34.920> access<00:16:35.100> your<00:16:35.399> portfolio<00:16:35.880> through 00:16:36.170 --> 00:16:36.180 align:start position:0% if you can access your portfolio through 00:16:36.180 --> 00:16:40.069 align:start position:0% if you can access your portfolio through the<00:16:36.300> VPN<00:16:36.720> locally<00:16:37.680> in<00:16:37.800> your<00:16:37.980> mobile<00:16:38.220> device 00:16:40.069 --> 00:16:40.079 align:start position:0% the VPN locally in your mobile device 00:16:40.079 --> 00:16:42.590 align:start position:0% the VPN locally in your mobile device so<00:16:40.620> that's<00:16:40.860> uh<00:16:41.339> you<00:16:41.639> know<00:16:41.759> like<00:16:42.000> we<00:16:42.240> met<00:16:42.420> the 00:16:42.590 --> 00:16:42.600 align:start position:0% so that's uh you know like we met the 00:16:42.600 --> 00:16:45.889 align:start position:0% so that's uh you know like we met the user<00:16:42.899> using<00:16:43.800> uh<00:16:44.160> in<00:16:44.940> such<00:16:45.000> a<00:16:45.120> way<00:16:45.240> in<00:16:45.300> efficacy 00:16:45.889 --> 00:16:45.899 align:start position:0% user using uh in such a way in efficacy 00:16:45.899 --> 00:16:48.470 align:start position:0% user using uh in such a way in efficacy and<00:16:46.560> it<00:16:46.800> was<00:16:46.920> a<00:16:47.100> really<00:16:47.279> happy<00:16:47.519> moment<00:16:47.880> because 00:16:48.470 --> 00:16:48.480 align:start position:0% and it was a really happy moment because 00:16:48.480 --> 00:16:50.689 align:start position:0% and it was a really happy moment because we<00:16:48.899> don't<00:16:49.079> actually<00:16:49.320> have<00:16:49.740> any<00:16:50.220> documentation 00:16:50.689 --> 00:16:50.699 align:start position:0% we don't actually have any documentation 00:16:50.699 --> 00:16:52.430 align:start position:0% we don't actually have any documentation on<00:16:50.820> how<00:16:51.000> to<00:16:51.120> do<00:16:51.240> that 00:16:52.430 --> 00:16:52.440 align:start position:0% on how to do that 00:16:52.440 --> 00:16:56.930 align:start position:0% on how to do that so<00:16:53.160> it<00:16:53.759> was<00:16:54.120> really<00:16:54.300> nice 00:16:56.930 --> 00:16:56.940 align:start position:0% 00:16:56.940 --> 00:17:01.610 align:start position:0% I<00:16:57.600> just<00:16:57.660> went<00:16:57.839> a<00:16:58.019> bit<00:16:58.079> fast 00:17:01.610 --> 00:17:01.620 align:start position:0% 00:17:01.620 --> 00:17:04.610 align:start position:0% so<00:17:02.220> yes<00:17:02.579> so<00:17:03.120> if<00:17:03.300> you<00:17:03.420> want<00:17:03.540> to<00:17:03.660> reach<00:17:03.899> out 00:17:04.610 --> 00:17:04.620 align:start position:0% so yes so if you want to reach out 00:17:04.620 --> 00:17:05.449 align:start position:0% so yes so if you want to reach out um 00:17:05.449 --> 00:17:05.459 align:start position:0% um 00:17:05.459 --> 00:17:06.590 align:start position:0% um that<00:17:05.760> you<00:17:05.939> can<00:17:06.059> already<00:17:06.120> talk<00:17:06.360> through 00:17:06.590 --> 00:17:06.600 align:start position:0% that you can already talk through 00:17:06.600 --> 00:17:09.049 align:start position:0% that you can already talk through Discord 00:17:09.049 --> 00:17:09.059 align:start position:0% 00:17:09.059 --> 00:17:12.110 align:start position:0% and<00:17:09.720> please<00:17:10.439> please<00:17:10.860> really<00:17:11.339> like<00:17:11.640> we<00:17:11.880> built 00:17:12.110 --> 00:17:12.120 align:start position:0% and please please really like we built 00:17:12.120 --> 00:17:14.449 align:start position:0% and please please really like we built Rocky<00:17:12.600> for<00:17:12.720> the<00:17:12.839> community<00:17:13.079> we<00:17:13.799> build<00:17:13.980> it<00:17:14.220> for 00:17:14.449 --> 00:17:14.459 align:start position:0% Rocky for the community we build it for 00:17:14.459 --> 00:17:16.970 align:start position:0% Rocky for the community we build it for us<00:17:14.640> and<00:17:14.819> for<00:17:14.939> other<00:17:15.120> people<00:17:15.360> so<00:17:16.199> it<00:17:16.559> would<00:17:16.740> be 00:17:16.970 --> 00:17:16.980 align:start position:0% us and for other people so it would be 00:17:16.980 --> 00:17:19.010 align:start position:0% us and for other people so it would be nice<00:17:17.280> if<00:17:17.640> you<00:17:17.819> uh<00:17:18.240> give<00:17:18.480> it<00:17:18.600> a<00:17:18.720> try<00:17:18.839> like 00:17:19.010 --> 00:17:19.020 align:start position:0% nice if you uh give it a try like 00:17:19.020 --> 00:17:21.829 align:start position:0% nice if you uh give it a try like download<00:17:19.380> the<00:17:19.679> app<00:17:19.799> uh<00:17:20.640> run<00:17:20.939> it<00:17:21.120> test<00:17:21.360> it<00:17:21.600> give 00:17:21.829 --> 00:17:21.839 align:start position:0% download the app uh run it test it give 00:17:21.839 --> 00:17:24.230 align:start position:0% download the app uh run it test it give us<00:17:21.959> feedback<00:17:22.380> we<00:17:23.040> always<00:17:23.220> hear<00:17:23.640> feedback<00:17:24.059> and 00:17:24.230 --> 00:17:24.240 align:start position:0% us feedback we always hear feedback and 00:17:24.240 --> 00:17:26.569 align:start position:0% us feedback we always hear feedback and the<00:17:24.720> way<00:17:24.839> we<00:17:25.020> build<00:17:25.140> the<00:17:25.380> app<00:17:25.559> is<00:17:26.040> based<00:17:26.339> on<00:17:26.400> the 00:17:26.569 --> 00:17:26.579 align:start position:0% the way we build the app is based on the 00:17:26.579 --> 00:17:27.710 align:start position:0% the way we build the app is based on the user<00:17:26.880> feedback 00:17:27.710 --> 00:17:27.720 align:start position:0% user feedback 00:17:27.720 --> 00:17:32.090 align:start position:0% user feedback so<00:17:28.439> uh<00:17:29.040> please<00:17:29.340> do<00:17:29.580> and<00:17:29.760> let<00:17:29.940> us<00:17:30.059> know<00:17:30.380> uh<00:17:31.380> then 00:17:32.090 --> 00:17:32.100 align:start position:0% so uh please do and let us know uh then 00:17:32.100 --> 00:17:34.190 align:start position:0% so uh please do and let us know uh then you<00:17:32.460> can<00:17:32.580> follow<00:17:32.760> the<00:17:33.000> barot<00:17:33.419> Gap<00:17:33.660> account<00:17:33.840> on 00:17:34.190 --> 00:17:34.200 align:start position:0% you can follow the barot Gap account on 00:17:34.200 --> 00:17:36.049 align:start position:0% you can follow the barot Gap account on Twitter 00:17:36.049 --> 00:17:36.059 align:start position:0% Twitter 00:17:36.059 --> 00:17:37.850 align:start position:0% Twitter most<00:17:36.539> of<00:17:36.720> the<00:17:36.780> time<00:17:36.900> since<00:17:37.020> left<00:17:37.260> is<00:17:37.559> tweeting 00:17:37.850 --> 00:17:37.860 align:start position:0% most of the time since left is tweeting 00:17:37.860 --> 00:17:38.930 align:start position:0% most of the time since left is tweeting from<00:17:37.980> there 00:17:38.930 --> 00:17:38.940 align:start position:0% from there 00:17:38.940 --> 00:17:40.310 align:start position:0% from there not<00:17:39.360> always 00:17:40.310 --> 00:17:40.320 align:start position:0% not always 00:17:40.320 --> 00:17:44.150 align:start position:0% not always and<00:17:41.039> uh<00:17:41.700> yeah<00:17:42.480> you<00:17:43.200> can<00:17:43.320> also<00:17:43.559> buy<00:17:43.679> a<00:17:43.860> premium 00:17:44.150 --> 00:17:44.160 align:start position:0% and uh yeah you can also buy a premium 00:17:44.160 --> 00:17:46.370 align:start position:0% and uh yeah you can also buy a premium subscription<00:17:44.580> it<00:17:45.480> is<00:17:45.600> a<00:17:45.720> bit<00:17:45.840> of<00:17:45.900> support<00:17:46.080> to 00:17:46.370 --> 00:17:46.380 align:start position:0% subscription it is a bit of support to 00:17:46.380 --> 00:17:49.490 align:start position:0% subscription it is a bit of support to us<00:17:46.559> doesn't<00:17:47.160> help<00:17:47.580> sustain<00:17:48.299> the<00:17:48.480> project<00:17:48.660> but 00:17:49.490 --> 00:17:49.500 align:start position:0% us doesn't help sustain the project but 00:17:49.500 --> 00:17:52.070 align:start position:0% us doesn't help sustain the project but it<00:17:49.740> still<00:17:49.919> helps<00:17:50.220> helps<00:17:50.880> us<00:17:51.000> a<00:17:51.120> lot<00:17:51.240> and<00:17:51.840> with 00:17:52.070 --> 00:17:52.080 align:start position:0% it still helps helps us a lot and with 00:17:52.080 --> 00:17:53.390 align:start position:0% it still helps helps us a lot and with this<00:17:52.200> you<00:17:52.440> can<00:17:52.559> actually<00:17:52.740> unlock<00:17:52.980> the<00:17:53.220> full 00:17:53.390 --> 00:17:53.400 align:start position:0% this you can actually unlock the full 00:17:53.400 --> 00:17:55.789 align:start position:0% this you can actually unlock the full Roti<00:17:53.880> experience<00:17:54.240> because<00:17:54.600> the<00:17:54.960> free<00:17:55.080> free 00:17:55.789 --> 00:17:55.799 align:start position:0% Roti experience because the free free 00:17:55.799 --> 00:17:57.890 align:start position:0% Roti experience because the free free version<00:17:56.039> has<00:17:56.340> some<00:17:56.520> limitations 00:17:57.890 --> 00:17:57.900 align:start position:0% version has some limitations 00:17:57.900 --> 00:18:00.650 align:start position:0% version has some limitations yes<00:17:58.860> so<00:17:59.100> it<00:17:59.400> was<00:17:59.520> a<00:17:59.640> bit<00:17:59.700> fast<00:17:59.940> thank<00:18:00.539> you 00:18:00.650 --> 00:18:00.660 align:start position:0% yes so it was a bit fast thank you 00:18:00.660 --> 00:18:02.210 align:start position:0% yes so it was a bit fast thank you kelsos<00:18:01.080> do<00:18:01.320> we<00:18:01.440> have<00:18:01.500> questions<00:18:01.679> in<00:18:02.160> the 00:18:02.210 --> 00:18:02.220 align:start position:0% kelsos do we have questions in the 00:18:02.220 --> 00:18:04.669 align:start position:0% kelsos do we have questions in the ambulance<00:18:02.640> I'm<00:18:03.419> liking<00:18:03.900> a<00:18:04.200> lot<00:18:04.320> of<00:18:04.440> these 00:18:04.669 --> 00:18:04.679 align:start position:0% ambulance I'm liking a lot of these 00:18:04.679 --> 00:18:06.650 align:start position:0% ambulance I'm liking a lot of these small<00:18:04.919> projects<00:18:05.460> and<00:18:05.640> I'm<00:18:05.820> liking<00:18:06.360> a<00:18:06.480> lot<00:18:06.539> of 00:18:06.650 --> 00:18:06.660 align:start position:0% small projects and I'm liking a lot of 00:18:06.660 --> 00:18:10.549 align:start position:0% small projects and I'm liking a lot of them<00:18:06.780> but<00:18:07.020> I<00:18:07.679> find<00:18:07.980> them<00:18:08.220> uh<00:18:09.000> I<00:18:09.480> have<00:18:09.600> I 00:18:10.549 --> 00:18:10.559 align:start position:0% them but I find them uh I have I 00:18:10.559 --> 00:18:13.190 align:start position:0% them but I find them uh I have I how<00:18:11.160> do<00:18:11.340> you<00:18:11.520> finance<00:18:11.880> radki<00:18:12.480> that's<00:18:12.900> my 00:18:13.190 --> 00:18:13.200 align:start position:0% how do you finance radki that's my 00:18:13.200 --> 00:18:15.710 align:start position:0% how do you finance radki that's my question<00:18:13.440> uh<00:18:14.160> the<00:18:14.400> funding<00:18:14.760> yeah<00:18:15.120> the<00:18:15.419> funding 00:18:15.710 --> 00:18:15.720 align:start position:0% question uh the funding yeah the funding 00:18:15.720 --> 00:18:20.210 align:start position:0% question uh the funding yeah the funding how<00:18:16.679> how<00:18:16.980> is<00:18:17.220> your<00:18:17.900> are<00:18:18.900> you<00:18:19.140> in<00:18:19.320> are<00:18:19.679> you<00:18:20.039> in 00:18:20.210 --> 00:18:20.220 align:start position:0% how how is your are you in are you in 00:18:20.220 --> 00:18:21.890 align:start position:0% how how is your are you in are you in Freedom<00:18:20.700> to<00:18:20.820> release<00:18:21.120> the<00:18:21.419> business<00:18:21.600> model 00:18:21.890 --> 00:18:21.900 align:start position:0% Freedom to release the business model 00:18:21.900 --> 00:18:24.409 align:start position:0% Freedom to release the business model because<00:18:22.380> at<00:18:23.220> the<00:18:23.340> end<00:18:23.460> of<00:18:23.580> the<00:18:23.640> day 00:18:24.409 --> 00:18:24.419 align:start position:0% because at the end of the day 00:18:24.419 --> 00:18:26.750 align:start position:0% because at the end of the day you<00:18:25.080> all<00:18:25.260> have<00:18:25.500> to<00:18:25.679> eat<00:18:25.860> I<00:18:26.220> know<00:18:26.400> you<00:18:26.520> have<00:18:26.640> to 00:18:26.750 --> 00:18:26.760 align:start position:0% you all have to eat I know you have to 00:18:26.760 --> 00:18:29.029 align:start position:0% you all have to eat I know you have to eat<00:18:26.880> yeah<00:18:27.179> exactly<00:18:27.480> exactly<00:18:27.840> so<00:18:28.440> funding<00:18:28.860> is 00:18:29.029 --> 00:18:29.039 align:start position:0% eat yeah exactly exactly so funding is 00:18:29.039 --> 00:18:31.070 align:start position:0% eat yeah exactly exactly so funding is really<00:18:29.220> hard<00:18:29.460> like<00:18:29.640> I<00:18:29.820> said<00:18:29.940> uh 00:18:31.070 --> 00:18:31.080 align:start position:0% really hard like I said uh 00:18:31.080 --> 00:18:33.950 align:start position:0% really hard like I said uh we<00:18:31.980> currently<00:18:32.700> have<00:18:33.179> uh<00:18:33.419> funding<00:18:33.780> through 00:18:33.950 --> 00:18:33.960 align:start position:0% we currently have uh funding through 00:18:33.960 --> 00:18:37.010 align:start position:0% we currently have uh funding through Bitcoin<00:18:34.380> grants<00:18:34.620> which<00:18:35.160> is<00:18:36.000> one<00:18:36.600> of<00:18:36.660> the<00:18:36.780> our 00:18:37.010 --> 00:18:37.020 align:start position:0% Bitcoin grants which is one of the our 00:18:37.020 --> 00:18:38.930 align:start position:0% Bitcoin grants which is one of the our biggest<00:18:37.260> source<00:18:37.799> of<00:18:37.860> support 00:18:38.930 --> 00:18:38.940 align:start position:0% biggest source of support 00:18:38.940 --> 00:18:41.270 align:start position:0% biggest source of support and<00:18:39.539> then<00:18:39.720> if<00:18:40.320> there<00:18:40.559> is 00:18:41.270 --> 00:18:41.280 align:start position:0% and then if there is 00:18:41.280 --> 00:18:43.730 align:start position:0% and then if there is he's<00:18:41.760> trying<00:18:42.000> to<00:18:42.179> find<00:18:42.299> ways<00:18:43.020> so<00:18:43.260> that<00:18:43.380> we<00:18:43.559> can 00:18:43.730 --> 00:18:43.740 align:start position:0% he's trying to find ways so that we can 00:18:43.740 --> 00:18:45.350 align:start position:0% he's trying to find ways so that we can get<00:18:44.220> grants<00:18:44.520> for<00:18:44.700> integrating<00:18:45.120> with 00:18:45.350 --> 00:18:45.360 align:start position:0% get grants for integrating with 00:18:45.360 --> 00:18:47.630 align:start position:0% get grants for integrating with different<00:18:45.539> protocols<00:18:46.140> so<00:18:46.799> these<00:18:47.160> I<00:18:47.280> think<00:18:47.400> are 00:18:47.630 --> 00:18:47.640 align:start position:0% different protocols so these I think are 00:18:47.640 --> 00:18:49.430 align:start position:0% different protocols so these I think are the<00:18:47.820> our<00:18:48.120> main<00:18:48.419> ways<00:18:48.720> of<00:18:48.780> funding<00:18:49.080> and<00:18:49.140> paying 00:18:49.430 --> 00:18:49.440 align:start position:0% the our main ways of funding and paying 00:18:49.440 --> 00:18:51.230 align:start position:0% the our main ways of funding and paying salaries<00:18:49.740> of<00:18:50.160> course<00:18:50.280> you<00:18:50.580> know<00:18:50.640> it's<00:18:50.760> as<00:18:51.059> an 00:18:51.230 --> 00:18:51.240 align:start position:0% salaries of course you know it's as an 00:18:51.240 --> 00:18:53.870 align:start position:0% salaries of course you know it's as an open<00:18:51.299> source<00:18:51.720> uh<00:18:52.080> project<00:18:52.380> we<00:18:53.039> do<00:18:53.220> it<00:18:53.400> out<00:18:53.700> of 00:18:53.870 --> 00:18:53.880 align:start position:0% open source uh project we do it out of 00:18:53.880 --> 00:18:56.390 align:start position:0% open source uh project we do it out of fashion<00:18:54.179> so<00:18:54.419> our<00:18:55.140> salaries<00:18:55.559> are<00:18:55.799> not<00:18:55.980> the<00:18:56.220> best 00:18:56.390 --> 00:18:56.400 align:start position:0% fashion so our salaries are not the best 00:18:56.400 --> 00:18:58.490 align:start position:0% fashion so our salaries are not the best like<00:18:56.700> we<00:18:57.000> are<00:18:57.179> below<00:18:57.419> market<00:18:57.600> rate 00:18:58.490 --> 00:18:58.500 align:start position:0% like we are below market rate 00:18:58.500 --> 00:19:00.529 align:start position:0% like we are below market rate but<00:18:58.980> uh<00:18:59.160> you<00:18:59.340> know<00:18:59.460> it's<00:18:59.640> something<00:18:59.880> we<00:19:00.360> love 00:19:00.529 --> 00:19:00.539 align:start position:0% but uh you know it's something we love 00:19:00.539 --> 00:19:03.289 align:start position:0% but uh you know it's something we love to<00:19:00.720> do<00:19:00.900> so<00:19:01.440> yeah<00:19:01.679> it's<00:19:01.919> hard<00:19:02.160> it's<00:19:02.400> hard<00:19:02.640> and 00:19:03.289 --> 00:19:03.299 align:start position:0% to do so yeah it's hard it's hard and 00:19:03.299 --> 00:19:04.490 align:start position:0% to do so yeah it's hard it's hard and then<00:19:03.419> we<00:19:03.539> have<00:19:03.720> the<00:19:03.840> premium<00:19:04.140> subscription 00:19:04.490 --> 00:19:04.500 align:start position:0% then we have the premium subscription 00:19:04.500 --> 00:19:07.070 align:start position:0% then we have the premium subscription but<00:19:04.860> uh<00:19:05.280> at<00:19:06.000> the<00:19:06.120> moment<00:19:06.179> our<00:19:06.539> premium 00:19:07.070 --> 00:19:07.080 align:start position:0% but uh at the moment our premium 00:19:07.080 --> 00:19:09.289 align:start position:0% but uh at the moment our premium subscription<00:19:07.380> is<00:19:07.679> 10<00:19:08.039> euros<00:19:08.400> per<00:19:08.580> month 00:19:09.289 --> 00:19:09.299 align:start position:0% subscription is 10 euros per month 00:19:09.299 --> 00:19:12.350 align:start position:0% subscription is 10 euros per month which<00:19:10.080> you<00:19:10.740> can<00:19:10.860> imagine<00:19:10.980> how<00:19:11.400> many<00:19:11.520> users<00:19:11.940> you 00:19:12.350 --> 00:19:12.360 align:start position:0% which you can imagine how many users you 00:19:12.360 --> 00:19:14.330 align:start position:0% which you can imagine how many users you would<00:19:12.539> want<00:19:12.840> to<00:19:13.559> be<00:19:13.620> able<00:19:13.799> to<00:19:13.919> sustain<00:19:14.160> the 00:19:14.330 --> 00:19:14.340 align:start position:0% would want to be able to sustain the 00:19:14.340 --> 00:19:17.029 align:start position:0% would want to be able to sustain the project<00:19:14.580> out<00:19:15.179> of<00:19:15.440> this<00:19:16.440> subscription<00:19:16.799> model 00:19:17.029 --> 00:19:17.039 align:start position:0% project out of this subscription model 00:19:17.039 --> 00:19:18.650 align:start position:0% project out of this subscription model hi 00:19:18.650 --> 00:19:18.660 align:start position:0% hi 00:19:18.660 --> 00:19:20.570 align:start position:0% hi um<00:19:18.720> this<00:19:19.140> might<00:19:19.260> have<00:19:19.380> been<00:19:19.500> covered<00:19:19.919> in<00:19:20.100> the 00:19:20.570 --> 00:19:20.580 align:start position:0% um this might have been covered in the 00:19:20.580 --> 00:19:23.029 align:start position:0% um this might have been covered in the other<00:19:20.760> presentation<00:19:21.240> the<00:19:21.600> left<00:19:21.840> Terrace<00:19:22.320> did 00:19:23.029 --> 00:19:23.039 align:start position:0% other presentation the left Terrace did 00:19:23.039 --> 00:19:25.310 align:start position:0% other presentation the left Terrace did um<00:19:23.100> you<00:19:23.460> said<00:19:23.580> you<00:19:23.760> rely<00:19:24.000> on<00:19:24.120> etherscan<00:19:24.900> for 00:19:25.310 --> 00:19:25.320 align:start position:0% um you said you rely on etherscan for 00:19:25.320 --> 00:19:27.650 align:start position:0% um you said you rely on etherscan for transactions<00:19:25.980> but<00:19:26.400> you<00:19:26.880> I<00:19:27.240> assume<00:19:27.480> you've 00:19:27.650 --> 00:19:27.660 align:start position:0% transactions but you I assume you've 00:19:27.660 --> 00:19:29.090 align:start position:0% transactions but you I assume you've looked<00:19:27.900> at<00:19:27.960> things<00:19:28.140> like<00:19:28.320> the<00:19:28.500> graph<00:19:28.740> which<00:19:28.980> is 00:19:29.090 --> 00:19:29.100 align:start position:0% looked at things like the graph which is 00:19:29.100 --> 00:19:30.710 align:start position:0% looked at things like the graph which is like<00:19:29.340> more<00:19:29.580> decentralized<00:19:30.240> what<00:19:30.480> do<00:19:30.660> you 00:19:30.710 --> 00:19:30.720 align:start position:0% like more decentralized what do you 00:19:30.720 --> 00:19:32.810 align:start position:0% like more decentralized what do you think<00:19:30.780> of<00:19:30.900> that<00:19:31.080> ah<00:19:31.620> yeah<00:19:31.799> so<00:19:32.039> we<00:19:32.400> use<00:19:32.640> the 00:19:32.810 --> 00:19:32.820 align:start position:0% think of that ah yeah so we use the 00:19:32.820 --> 00:19:35.930 align:start position:0% think of that ah yeah so we use the graph<00:19:33.120> but<00:19:34.020> in<00:19:34.559> our<00:19:34.679> use<00:19:34.860> case<00:19:35.100> it's<00:19:35.640> not<00:19:35.820> a 00:19:35.930 --> 00:19:35.940 align:start position:0% graph but in our use case it's not a 00:19:35.940 --> 00:19:38.150 align:start position:0% graph but in our use case it's not a perfect<00:19:36.059> fit<00:19:36.299> because<00:19:36.720> you<00:19:37.260> know<00:19:37.380> like<00:19:37.620> there 00:19:38.150 --> 00:19:38.160 align:start position:0% perfect fit because you know like there 00:19:38.160 --> 00:19:40.730 align:start position:0% perfect fit because you know like there is<00:19:38.340> a<00:19:38.580> no<00:19:39.000> unified<00:19:39.360> model<00:19:39.780> of<00:19:40.080> the<00:19:40.140> subgraphs 00:19:40.730 --> 00:19:40.740 align:start position:0% is a no unified model of the subgraphs 00:19:40.740 --> 00:19:43.070 align:start position:0% is a no unified model of the subgraphs so<00:19:41.220> for<00:19:41.400> every<00:19:41.580> protocol<00:19:41.880> we<00:19:42.120> support<00:19:42.299> we<00:19:42.900> have 00:19:43.070 --> 00:19:43.080 align:start position:0% so for every protocol we support we have 00:19:43.080 --> 00:19:45.289 align:start position:0% so for every protocol we support we have to<00:19:43.200> add<00:19:43.380> the<00:19:43.500> new<00:19:43.679> subgraph<00:19:44.039> and<00:19:45.000> this 00:19:45.289 --> 00:19:45.299 align:start position:0% to add the new subgraph and this 00:19:45.299 --> 00:19:47.390 align:start position:0% to add the new subgraph and this actually<00:19:45.900> gives<00:19:46.500> us<00:19:46.620> a<00:19:46.860> huge<00:19:47.100> maintenance 00:19:47.390 --> 00:19:47.400 align:start position:0% actually gives us a huge maintenance 00:19:47.400 --> 00:19:49.610 align:start position:0% actually gives us a huge maintenance host<00:19:47.700> because<00:19:47.940> we<00:19:48.120> have<00:19:48.299> to<00:19:48.419> go<00:19:48.660> and<00:19:49.320> you<00:19:49.559> know 00:19:49.610 --> 00:19:49.620 align:start position:0% host because we have to go and you know 00:19:49.620 --> 00:19:52.190 align:start position:0% host because we have to go and you know like<00:19:50.220> Implement<00:19:51.000> on<00:19:51.240> our<00:19:51.360> site<00:19:51.600> the<00:19:51.780> schema 00:19:52.190 --> 00:19:52.200 align:start position:0% like Implement on our site the schema 00:19:52.200 --> 00:19:53.830 align:start position:0% like Implement on our site the schema handle<00:19:52.500> every<00:19:52.679> subject<00:19:53.039> in<00:19:53.280> a<00:19:53.400> different<00:19:53.520> way 00:19:53.830 --> 00:19:53.840 align:start position:0% handle every subject in a different way 00:19:53.840 --> 00:19:56.870 align:start position:0% handle every subject in a different way and<00:19:54.840> uh<00:19:55.200> then<00:19:55.919> like<00:19:56.220> as<00:19:56.340> soon<00:19:56.520> as<00:19:56.580> the<00:19:56.760> sub 00:19:56.870 --> 00:19:56.880 align:start position:0% and uh then like as soon as the sub 00:19:56.880 --> 00:19:58.730 align:start position:0% and uh then like as soon as the sub graph<00:19:57.240> breaks 00:19:58.730 --> 00:19:58.740 align:start position:0% graph breaks 00:19:58.740 --> 00:20:01.549 align:start position:0% graph breaks we<00:19:59.220> have<00:19:59.400> to<00:19:59.580> fix<00:19:59.940> it<00:20:00.120> like<00:20:00.900> communicate<00:20:01.380> with 00:20:01.549 --> 00:20:01.559 align:start position:0% we have to fix it like communicate with 00:20:01.559 --> 00:20:03.529 align:start position:0% we have to fix it like communicate with people<00:20:01.860> that<00:20:02.220> are<00:20:02.340> limiting<00:20:02.820> the<00:20:02.940> subgraphs 00:20:03.529 --> 00:20:03.539 align:start position:0% people that are limiting the subgraphs 00:20:03.539 --> 00:20:05.029 align:start position:0% people that are limiting the subgraphs and<00:20:03.960> then<00:20:04.020> we<00:20:04.200> have<00:20:04.320> to<00:20:04.440> release<00:20:04.620> the<00:20:04.860> path 00:20:05.029 --> 00:20:05.039 align:start position:0% and then we have to release the path 00:20:05.039 --> 00:20:06.590 align:start position:0% and then we have to release the path that's<00:20:05.220> the<00:20:05.460> release<00:20:05.580> to<00:20:06.000> fix<00:20:06.059> that<00:20:06.240> for<00:20:06.419> our 00:20:06.590 --> 00:20:06.600 align:start position:0% that's the release to fix that for our 00:20:06.600 --> 00:20:08.570 align:start position:0% that's the release to fix that for our users<00:20:06.900> because<00:20:07.080> the<00:20:07.320> app<00:20:07.440> is<00:20:07.620> broken 00:20:08.570 --> 00:20:08.580 align:start position:0% users because the app is broken 00:20:08.580 --> 00:20:11.750 align:start position:0% users because the app is broken and<00:20:09.240> uh<00:20:09.600> this<00:20:10.140> is<00:20:10.260> why<00:20:10.559> we're<00:20:11.100> trying<00:20:11.340> to<00:20:11.520> find 00:20:11.750 --> 00:20:11.760 align:start position:0% and uh this is why we're trying to find 00:20:11.760 --> 00:20:14.450 align:start position:0% and uh this is why we're trying to find the<00:20:12.059> way<00:20:12.360> that<00:20:12.600> is<00:20:12.780> more<00:20:13.020> unified<00:20:13.380> and<00:20:14.280> more 00:20:14.450 --> 00:20:14.460 align:start position:0% the way that is more unified and more 00:20:14.460 --> 00:20:16.190 align:start position:0% the way that is more unified and more generic<00:20:14.880> and<00:20:15.000> that<00:20:15.299> doesn't<00:20:15.600> need<00:20:15.840> the<00:20:16.080> extra 00:20:16.190 --> 00:20:16.200 align:start position:0% generic and that doesn't need the extra 00:20:16.200 --> 00:20:17.870 align:start position:0% generic and that doesn't need the extra maintenance<00:20:16.679> cost<00:20:16.860> because<00:20:17.160> you<00:20:17.640> know<00:20:17.700> like 00:20:17.870 --> 00:20:17.880 align:start position:0% maintenance cost because you know like 00:20:17.880 --> 00:20:20.150 align:start position:0% maintenance cost because you know like uh<00:20:18.120> the<00:20:18.480> way<00:20:18.539> the<00:20:18.780> ecosystem<00:20:19.320> works<00:20:19.740> new 00:20:20.150 --> 00:20:20.160 align:start position:0% uh the way the ecosystem works new 00:20:20.160 --> 00:20:22.070 align:start position:0% uh the way the ecosystem works new protocols<00:20:20.700> pop<00:20:20.820> up<00:20:21.000> and<00:20:21.600> we<00:20:21.720> have<00:20:21.840> to<00:20:21.960> support 00:20:22.070 --> 00:20:22.080 align:start position:0% protocols pop up and we have to support 00:20:22.080 --> 00:20:23.029 align:start position:0% protocols pop up and we have to support them 00:20:23.029 --> 00:20:23.039 align:start position:0% them 00:20:23.039 --> 00:20:26.270 align:start position:0% them because<00:20:23.700> our<00:20:24.179> users<00:20:24.600> also<00:20:24.900> want<00:20:25.080> the<00:20:25.320> want<00:20:26.100> the 00:20:26.270 --> 00:20:26.280 align:start position:0% because our users also want the want the 00:20:26.280 --> 00:20:28.310 align:start position:0% because our users also want the want the support<00:20:26.400> for<00:20:26.580> these<00:20:26.760> protocols<00:20:27.179> so<00:20:27.780> it's<00:20:28.080> uh 00:20:28.310 --> 00:20:28.320 align:start position:0% support for these protocols so it's uh 00:20:28.320 --> 00:20:30.770 align:start position:0% support for these protocols so it's uh really<00:20:28.620> hard<00:20:28.799> for<00:20:29.039> us<00:20:29.160> to<00:20:29.940> go<00:20:30.299> and<00:20:30.419> Implement 00:20:30.770 --> 00:20:30.780 align:start position:0% really hard for us to go and Implement 00:20:30.780 --> 00:20:32.750 align:start position:0% really hard for us to go and Implement each<00:20:31.080> subgraph<00:20:31.440> for<00:20:31.620> its<00:20:31.799> protocol<00:20:32.039> and<00:20:32.640> it 00:20:32.750 --> 00:20:32.760 align:start position:0% each subgraph for its protocol and it 00:20:32.760 --> 00:20:35.090 align:start position:0% each subgraph for its protocol and it becomes<00:20:33.059> the<00:20:33.179> maintenance<00:20:33.539> help<00:20:33.780> for<00:20:34.080> uh<00:20:34.500> our 00:20:35.090 --> 00:20:35.100 align:start position:0% becomes the maintenance help for uh our 00:20:35.100 --> 00:20:38.029 align:start position:0% becomes the maintenance help for uh our small<00:20:35.340> thing<00:20:36.059> thank<00:20:36.299> you<00:20:36.419> again<00:20:36.539> kelsos 00:20:38.029 --> 00:20:38.039 align:start position:0% small thing thank you again kelsos 00:20:38.039 --> 00:20:40.580 align:start position:0% small thing thank you again kelsos thank<00:20:38.400> you