WEBVTT Kind: captions Language: en 00:00:01.610 --> 00:00:19.090 align:start position:0% ah<00:00:16.150> cancun<00:00:17.150> what<00:00:17.690> an<00:00:17.840> epic<00:00:18.170> def<00:00:18.410> con<00:00:18.650> this<00:00:18.800> was 00:00:19.090 --> 00:00:19.100 align:start position:0% ah cancun what an epic def con this was 00:00:19.100 --> 00:00:21.640 align:start position:0% ah cancun what an epic def con this was can<00:00:19.670> we<00:00:19.820> agree<00:00:20.030> let's<00:00:20.840> give<00:00:21.020> it<00:00:21.050> up<00:00:21.290> for<00:00:21.350> a 00:00:21.640 --> 00:00:21.650 align:start position:0% can we agree let's give it up for a 00:00:21.650 --> 00:00:23.500 align:start position:0% can we agree let's give it up for a Tyrian<00:00:21.950> foundation<00:00:22.610> and<00:00:22.760> everyone<00:00:23.120> making 00:00:23.500 --> 00:00:23.510 align:start position:0% Tyrian foundation and everyone making 00:00:23.510 --> 00:00:27.840 align:start position:0% Tyrian foundation and everyone making this<00:00:23.660> happen<00:00:23.930> yeah<00:00:25.150> thank<00:00:26.150> you 00:00:27.840 --> 00:00:27.850 align:start position:0% this happen yeah thank you 00:00:27.850 --> 00:00:53.650 align:start position:0% this happen yeah thank you so<00:00:28.850> let<00:00:29.480> me<00:00:29.630> play<00:00:30.320> this<00:00:49.000> technology<00:00:52.300> okay 00:00:53.650 --> 00:00:53.660 align:start position:0% so let me play this technology okay 00:00:53.660 --> 00:00:56.650 align:start position:0% so let me play this technology okay so<00:00:54.190> before<00:00:55.190> we<00:00:55.340> begin<00:00:55.460> I<00:00:55.910> would<00:00:56.030> like<00:00:56.180> to<00:00:56.480> ask 00:00:56.650 --> 00:00:56.660 align:start position:0% so before we begin I would like to ask 00:00:56.660 --> 00:00:58.120 align:start position:0% so before we begin I would like to ask how<00:00:56.930> many<00:00:56.989> of<00:00:57.200> you<00:00:57.350> have<00:00:57.559> heard<00:00:57.710> of<00:00:57.890> Akasha 00:00:58.120 --> 00:00:58.130 align:start position:0% how many of you have heard of Akasha 00:00:58.130 --> 00:01:02.530 align:start position:0% how many of you have heard of Akasha before<00:00:58.579> can<00:00:58.910> we<00:00:58.940> see<00:00:59.180> a<00:00:59.210> show<00:00:59.300> of<00:01:01.300> okay<00:01:02.300> that's 00:01:02.530 --> 00:01:02.540 align:start position:0% before can we see a show of okay that's 00:01:02.540 --> 00:01:04.869 align:start position:0% before can we see a show of okay that's that<00:01:02.870> is<00:01:03.110> impressive<00:01:03.710> and<00:01:03.890> I'm<00:01:04.460> just<00:01:04.699> curious 00:01:04.869 --> 00:01:04.879 align:start position:0% that is impressive and I'm just curious 00:01:04.879 --> 00:01:06.789 align:start position:0% that is impressive and I'm just curious how<00:01:05.210> many<00:01:05.239> of<00:01:05.509> you<00:01:05.720> have<00:01:05.960> actually<00:01:06.290> tried<00:01:06.590> the 00:01:06.789 --> 00:01:06.799 align:start position:0% how many of you have actually tried the 00:01:06.799 --> 00:01:10.510 align:start position:0% how many of you have actually tried the Alpha<00:01:07.900> Wow<00:01:08.900> okay<00:01:09.590> so<00:01:09.620> we<00:01:09.860> have<00:01:10.010> quite<00:01:10.340> a<00:01:10.370> few 00:01:10.510 --> 00:01:10.520 align:start position:0% Alpha Wow okay so we have quite a few 00:01:10.520 --> 00:01:13.870 align:start position:0% Alpha Wow okay so we have quite a few alpha<00:01:11.240> veterans<00:01:11.870> thank<00:01:12.740> you<00:01:12.920> for<00:01:13.370> taking<00:01:13.760> the 00:01:13.870 --> 00:01:13.880 align:start position:0% alpha veterans thank you for taking the 00:01:13.880 --> 00:01:18.430 align:start position:0% alpha veterans thank you for taking the time<00:01:14.150> to<00:01:14.420> play<00:01:15.110> with<00:01:15.320> the<00:01:15.950> app<00:01:17.140> for<00:01:18.140> those<00:01:18.290> of 00:01:18.430 --> 00:01:18.440 align:start position:0% time to play with the app for those of 00:01:18.440 --> 00:01:20.620 align:start position:0% time to play with the app for those of you<00:01:18.560> who<00:01:18.770> haven't<00:01:19.340> heard<00:01:19.490> of<00:01:19.700> Akasha<00:01:20.030> before 00:01:20.620 --> 00:01:20.630 align:start position:0% you who haven't heard of Akasha before 00:01:20.630 --> 00:01:23.800 align:start position:0% you who haven't heard of Akasha before as<00:01:20.930> a<00:01:21.290> word<00:01:21.710> it<00:01:21.950> comes<00:01:22.190> from<00:01:22.520> Sanskrit<00:01:23.240> and<00:01:23.630> it 00:01:23.800 --> 00:01:23.810 align:start position:0% as a word it comes from Sanskrit and it 00:01:23.810 --> 00:01:27.490 align:start position:0% as a word it comes from Sanskrit and it means<00:01:23.990> eater<00:01:24.610> but<00:01:25.610> it<00:01:25.729> also<00:01:26.200> stands<00:01:27.200> as<00:01:27.350> an 00:01:27.490 --> 00:01:27.500 align:start position:0% means eater but it also stands as an 00:01:27.500 --> 00:01:28.899 align:start position:0% means eater but it also stands as an acronym<00:01:27.890> for<00:01:27.950> advanced<00:01:28.790> knowledge 00:01:28.899 --> 00:01:28.909 align:start position:0% acronym for advanced knowledge 00:01:28.909 --> 00:01:32.109 align:start position:0% acronym for advanced knowledge architecture<00:01:29.750> for<00:01:30.260> social<00:01:30.740> human<00:01:31.130> advocacy 00:01:32.109 --> 00:01:32.119 align:start position:0% architecture for social human advocacy 00:01:32.119 --> 00:01:34.359 align:start position:0% architecture for social human advocacy and<00:01:32.720> what<00:01:33.200> we<00:01:33.350> are<00:01:33.439> trying<00:01:33.680> to<00:01:33.860> build<00:01:34.010> is<00:01:34.340> a 00:01:34.359 --> 00:01:34.369 align:start position:0% and what we are trying to build is a 00:01:34.369 --> 00:01:36.460 align:start position:0% and what we are trying to build is a peer-to-peer<00:01:34.760> alternative<00:01:35.659> in<00:01:35.990> a<00:01:36.049> world 00:01:36.460 --> 00:01:36.470 align:start position:0% peer-to-peer alternative in a world 00:01:36.470 --> 00:01:38.950 align:start position:0% peer-to-peer alternative in a world where<00:01:36.799> the<00:01:37.580> social<00:01:37.820> media<00:01:38.240> networks<00:01:38.659> are 00:01:38.950 --> 00:01:38.960 align:start position:0% where the social media networks are 00:01:38.960 --> 00:01:41.320 align:start position:0% where the social media networks are modeled<00:01:39.530> after<00:01:39.680> the<00:01:40.040> Napster<00:01:40.490> architecture 00:01:41.320 --> 00:01:41.330 align:start position:0% modeled after the Napster architecture 00:01:41.330 --> 00:01:44.380 align:start position:0% modeled after the Napster architecture where<00:01:41.840> the<00:01:42.049> user<00:01:42.260> depends<00:01:42.890> on<00:01:43.010> a<00:01:43.040> server<00:01:43.580> or<00:01:43.939> a 00:01:44.380 --> 00:01:44.390 align:start position:0% where the user depends on a server or a 00:01:44.390 --> 00:01:49.300 align:start position:0% where the user depends on a server or a server<00:01:44.960> operator<00:01:45.470> or<00:01:45.950> an<00:01:46.100> entity<00:01:46.810> and<00:01:47.810> we<00:01:48.310> want 00:01:49.300 --> 00:01:49.310 align:start position:0% server operator or an entity and we want 00:01:49.310 --> 00:01:51.190 align:start position:0% server operator or an entity and we want to<00:01:49.460> tackle<00:01:49.820> this<00:01:49.939> problem<00:01:50.840> from<00:01:51.020> a<00:01:51.170> different 00:01:51.190 --> 00:01:51.200 align:start position:0% to tackle this problem from a different 00:01:51.200 --> 00:01:53.920 align:start position:0% to tackle this problem from a different perspective<00:01:51.770> using<00:01:52.490> different<00:01:53.240> technologies 00:01:53.920 --> 00:01:53.930 align:start position:0% perspective using different technologies 00:01:53.930 --> 00:01:56.740 align:start position:0% perspective using different technologies so<00:01:54.710> in<00:01:55.280> a<00:01:55.430> word<00:01:55.610> we<00:01:55.820> want<00:01:56.000> to<00:01:56.180> showcase<00:01:56.600> the 00:01:56.740 --> 00:01:56.750 align:start position:0% so in a word we want to showcase the 00:01:56.750 --> 00:01:59.170 align:start position:0% so in a word we want to showcase the potential<00:01:57.290> of<00:01:57.409> etherium<00:01:57.950> combined<00:01:58.369> with<00:01:58.549> ipfs 00:01:59.170 --> 00:01:59.180 align:start position:0% potential of etherium combined with ipfs 00:01:59.180 --> 00:02:02.170 align:start position:0% potential of etherium combined with ipfs to<00:02:00.110> solve<00:02:00.439> all<00:02:00.799> problems<00:02:00.909> using<00:02:01.909> new 00:02:02.170 --> 00:02:02.180 align:start position:0% to solve all problems using new 00:02:02.180 --> 00:02:05.469 align:start position:0% to solve all problems using new technologies<00:02:02.869> and<00:02:03.610> the<00:02:04.610> thing<00:02:04.820> we<00:02:04.970> want<00:02:05.329> to 00:02:05.469 --> 00:02:05.479 align:start position:0% technologies and the thing we want to 00:02:05.479 --> 00:02:07.149 align:start position:0% technologies and the thing we want to achieve<00:02:05.630> is<00:02:06.020> a<00:02:06.049> shared<00:02:06.439> and<00:02:06.650> persistent 00:02:07.149 --> 00:02:07.159 align:start position:0% achieve is a shared and persistent 00:02:07.159 --> 00:02:09.550 align:start position:0% achieve is a shared and persistent information<00:02:07.670> Commons<00:02:08.179> that<00:02:08.810> can<00:02:09.079> help<00:02:09.319> people 00:02:09.550 --> 00:02:09.560 align:start position:0% information Commons that can help people 00:02:09.560 --> 00:02:13.479 align:start position:0% information Commons that can help people put<00:02:10.310> the<00:02:10.789> key<00:02:11.150> that<00:02:11.989> can<00:02:12.230> help<00:02:12.530> people<00:02:13.010> regain 00:02:13.479 --> 00:02:13.489 align:start position:0% put the key that can help people regain 00:02:13.489 --> 00:02:15.430 align:start position:0% put the key that can help people regain their<00:02:13.870> collective<00:02:14.870> memory 00:02:15.430 --> 00:02:15.440 align:start position:0% their collective memory 00:02:15.440 --> 00:02:17.920 align:start position:0% their collective memory and<00:02:15.530> freedom<00:02:16.040> of<00:02:16.220> expression<00:02:16.450> back<00:02:17.450> from<00:02:17.810> the 00:02:17.920 --> 00:02:17.930 align:start position:0% and freedom of expression back from the 00:02:17.930 --> 00:02:20.170 align:start position:0% and freedom of expression back from the clause<00:02:18.170> of<00:02:18.340> corporations<00:02:19.340> that<00:02:19.460> monetize 00:02:20.170 --> 00:02:20.180 align:start position:0% clause of corporations that monetize 00:02:20.180 --> 00:02:23.620 align:start position:0% clause of corporations that monetize each<00:02:20.480> click<00:02:20.900> and<00:02:21.850> really<00:02:22.850> everything<00:02:23.330> it's 00:02:23.620 --> 00:02:23.630 align:start position:0% each click and really everything it's 00:02:23.630 --> 00:02:27.970 align:start position:0% each click and really everything it's really<00:02:23.720> bad<00:02:24.110> so<00:02:24.940> to<00:02:25.940> put<00:02:26.150> it<00:02:26.180> visually<00:02:27.170> the 00:02:27.970 --> 00:02:27.980 align:start position:0% really bad so to put it visually the 00:02:27.980 --> 00:02:30.790 align:start position:0% really bad so to put it visually the Napster<00:02:28.250> web<00:02:28.520> apps<00:02:28.850> are<00:02:29.260> Napster<00:02:30.260> like<00:02:30.470> web 00:02:30.790 --> 00:02:30.800 align:start position:0% Napster web apps are Napster like web 00:02:30.800 --> 00:02:33.640 align:start position:0% Napster web apps are Napster like web apps<00:02:31.010> rely<00:02:31.910> on<00:02:31.940> the<00:02:32.180> server<00:02:32.390> admin<00:02:32.810> or<00:02:33.110> the 00:02:33.640 --> 00:02:33.650 align:start position:0% apps rely on the server admin or the 00:02:33.650 --> 00:02:37.240 align:start position:0% apps rely on the server admin or the server<00:02:34.310> itself<00:02:34.790> and<00:02:35.120> if<00:02:35.870> for<00:02:36.380> some<00:02:36.440> reason<00:02:37.040> the 00:02:37.240 --> 00:02:37.250 align:start position:0% server itself and if for some reason the 00:02:37.250 --> 00:02:39.880 align:start position:0% server itself and if for some reason the user<00:02:37.430> does<00:02:37.910> not<00:02:37.940> comply<00:02:38.540> or<00:02:38.930> respect<00:02:39.650> whatever 00:02:39.880 --> 00:02:39.890 align:start position:0% user does not comply or respect whatever 00:02:39.890 --> 00:02:42.820 align:start position:0% user does not comply or respect whatever the<00:02:40.250> server<00:02:40.600> operator<00:02:41.600> once<00:02:42.110> they<00:02:42.770> lose 00:02:42.820 --> 00:02:42.830 align:start position:0% the server operator once they lose 00:02:42.830 --> 00:02:45.670 align:start position:0% the server operator once they lose access<00:02:43.430> to<00:02:43.640> the<00:02:43.910> service<00:02:44.300> in<00:02:44.900> the<00:02:45.110> Alpha<00:02:45.470> we 00:02:45.670 --> 00:02:45.680 align:start position:0% access to the service in the Alpha we 00:02:45.680 --> 00:02:47.860 align:start position:0% access to the service in the Alpha we took<00:02:45.920> the<00:02:46.220> hardest<00:02:46.730> challenge<00:02:47.210> we<00:02:47.330> could<00:02:47.540> find 00:02:47.860 --> 00:02:47.870 align:start position:0% took the hardest challenge we could find 00:02:47.870 --> 00:02:49.420 align:start position:0% took the hardest challenge we could find which<00:02:48.170> was<00:02:48.410> to<00:02:48.620> build<00:02:48.710> a<00:02:48.920> fully<00:02:49.190> decentralized 00:02:49.420 --> 00:02:49.430 align:start position:0% which was to build a fully decentralized 00:02:49.430 --> 00:02:52.840 align:start position:0% which was to build a fully decentralized desktop<00:02:50.360> app<00:02:50.710> meaning<00:02:51.710> that<00:02:51.860> each<00:02:52.130> user<00:02:52.490> when 00:02:52.840 --> 00:02:52.850 align:start position:0% desktop app meaning that each user when 00:02:52.850 --> 00:02:54.790 align:start position:0% desktop app meaning that each user when they<00:02:52.880> downloaded<00:02:53.720> and<00:02:53.870> installed<00:02:54.260> the<00:02:54.440> Akasha 00:02:54.790 --> 00:02:54.800 align:start position:0% they downloaded and installed the Akasha 00:02:54.800 --> 00:02:56.140 align:start position:0% they downloaded and installed the Akasha application<00:02:55.460> they<00:02:55.580> were<00:02:55.670> actually 00:02:56.140 --> 00:02:56.150 align:start position:0% application they were actually 00:02:56.150 --> 00:02:59.050 align:start position:0% application they were actually installing<00:02:57.020> bundled<00:02:57.860> and<00:02:58.100> etherium<00:02:58.610> node<00:02:58.820> and 00:02:59.050 --> 00:02:59.060 align:start position:0% installing bundled and etherium node and 00:02:59.060 --> 00:03:02.500 align:start position:0% installing bundled and etherium node and an<00:02:59.150> IP<00:02:59.330> FS<00:02:59.780> node<00:03:00.020> so<00:03:00.830> in<00:03:01.310> the<00:03:01.490> beta<00:03:01.700> thanks<00:03:02.360> to 00:03:02.500 --> 00:03:02.510 align:start position:0% an IP FS node so in the beta thanks to 00:03:02.510 --> 00:03:04.450 align:start position:0% an IP FS node so in the beta thanks to hard<00:03:03.020> work<00:03:03.080> of<00:03:03.530> the<00:03:03.740> team<00:03:03.950> we<00:03:04.130> will<00:03:04.280> also 00:03:04.450 --> 00:03:04.460 align:start position:0% hard work of the team we will also 00:03:04.460 --> 00:03:07.210 align:start position:0% hard work of the team we will also introduce<00:03:04.880> a<00:03:05.270> fully<00:03:05.540> functional<00:03:06.170> web<00:03:06.710> version 00:03:07.210 --> 00:03:07.220 align:start position:0% introduce a fully functional web version 00:03:07.220 --> 00:03:09.160 align:start position:0% introduce a fully functional web version which<00:03:07.520> will<00:03:07.730> remove<00:03:08.000> the<00:03:08.210> need<00:03:08.390> to<00:03:08.600> sync<00:03:08.900> with 00:03:09.160 --> 00:03:09.170 align:start position:0% which will remove the need to sync with 00:03:09.170 --> 00:03:12.210 align:start position:0% which will remove the need to sync with with<00:03:09.770> a<00:03:09.800> chain<00:03:10.160> and<00:03:10.400> the<00:03:11.300> users<00:03:11.630> will<00:03:11.870> then 00:03:12.210 --> 00:03:12.220 align:start position:0% with a chain and the users will then 00:03:12.220 --> 00:03:15.670 align:start position:0% with a chain and the users will then rely<00:03:13.220> on<00:03:13.250> meta<00:03:13.730> mask<00:03:14.030> or<00:03:14.360> any<00:03:14.840> other<00:03:15.140> way<00:03:15.440> tree 00:03:15.670 --> 00:03:15.680 align:start position:0% rely on meta mask or any other way tree 00:03:15.680 --> 00:03:18.190 align:start position:0% rely on meta mask or any other way tree service<00:03:15.980> provider<00:03:16.340> like<00:03:16.580> status<00:03:17.180> or<00:03:17.600> or 00:03:18.190 --> 00:03:18.200 align:start position:0% service provider like status or or 00:03:18.200 --> 00:03:20.740 align:start position:0% service provider like status or or missed<00:03:18.770> and<00:03:19.310> when<00:03:19.700> we<00:03:19.850> say<00:03:20.030> that<00:03:20.209> free<00:03:20.450> speech 00:03:20.740 --> 00:03:20.750 align:start position:0% missed and when we say that free speech 00:03:20.750 --> 00:03:22.720 align:start position:0% missed and when we say that free speech is<00:03:20.930> embedded<00:03:21.380> in<00:03:21.500> software<00:03:21.860> what<00:03:22.190> we<00:03:22.340> mean<00:03:22.520> is 00:03:22.720 --> 00:03:22.730 align:start position:0% is embedded in software what we mean is 00:03:22.730 --> 00:03:26.140 align:start position:0% is embedded in software what we mean is that<00:03:23.200> whereas<00:03:24.200> the<00:03:24.500> user<00:03:24.739> can<00:03:25.160> be<00:03:25.310> kicked<00:03:25.550> for 00:03:26.140 --> 00:03:26.150 align:start position:0% that whereas the user can be kicked for 00:03:26.150 --> 00:03:28.390 align:start position:0% that whereas the user can be kicked for whatever<00:03:26.570> reason<00:03:27.140> from<00:03:27.410> the<00:03:27.650> Napster<00:03:28.100> like 00:03:28.390 --> 00:03:28.400 align:start position:0% whatever reason from the Napster like 00:03:28.400 --> 00:03:31.840 align:start position:0% whatever reason from the Napster like web<00:03:29.180> apps<00:03:29.420> on<00:03:30.050> Akasha<00:03:30.650> the<00:03:30.980> users<00:03:31.310> are<00:03:31.489> in<00:03:31.610> full 00:03:31.840 --> 00:03:31.850 align:start position:0% web apps on Akasha the users are in full 00:03:31.850 --> 00:03:33.910 align:start position:0% web apps on Akasha the users are in full control<00:03:32.060> over<00:03:32.300> their<00:03:32.690> identity<00:03:33.290> and<00:03:33.560> the 00:03:33.910 --> 00:03:33.920 align:start position:0% control over their identity and the 00:03:33.920 --> 00:03:36.520 align:start position:0% control over their identity and the content<00:03:34.340> they<00:03:34.459> are<00:03:34.489> posting<00:03:35.090> so<00:03:35.840> our<00:03:36.200> story 00:03:36.520 --> 00:03:36.530 align:start position:0% content they are posting so our story 00:03:36.530 --> 00:03:41.220 align:start position:0% content they are posting so our story began<00:03:36.860> on<00:03:37.070> May<00:03:37.280> 6th<00:03:38.209> mater<00:03:39.010> 2016<00:03:40.010> on<00:03:40.760> World 00:03:41.220 --> 00:03:41.230 align:start position:0% began on May 6th mater 2016 on World 00:03:41.230 --> 00:03:44.340 align:start position:0% began on May 6th mater 2016 on World Press<00:03:42.230> Freedom<00:03:42.440> Day<00:03:42.709> and<00:03:43.250> this<00:03:43.850> is<00:03:43.970> when<00:03:44.180> we 00:03:44.340 --> 00:03:44.350 align:start position:0% Press Freedom Day and this is when we 00:03:44.350 --> 00:03:46.449 align:start position:0% Press Freedom Day and this is when we basically<00:03:45.350> announced<00:03:45.739> that<00:03:46.040> we've<00:03:46.250> been 00:03:46.449 --> 00:03:46.459 align:start position:0% basically announced that we've been 00:03:46.459 --> 00:03:47.920 align:start position:0% basically announced that we've been working<00:03:46.850> for<00:03:47.000> quite<00:03:47.150> some<00:03:47.420> time<00:03:47.450> on<00:03:47.810> the 00:03:47.920 --> 00:03:47.930 align:start position:0% working for quite some time on the 00:03:47.930 --> 00:03:50.199 align:start position:0% working for quite some time on the Akasha<00:03:48.230> alpha<00:03:48.680> it<00:03:49.040> was<00:03:49.250> a<00:03:49.280> total<00:03:49.700> shot<00:03:49.910> in<00:03:50.090> the 00:03:50.199 --> 00:03:50.209 align:start position:0% Akasha alpha it was a total shot in the 00:03:50.209 --> 00:03:53.110 align:start position:0% Akasha alpha it was a total shot in the dark<00:03:50.390> for<00:03:50.810> us<00:03:50.959> we<00:03:51.320> weren't<00:03:52.190> sure<00:03:52.459> exactly<00:03:52.610> what 00:03:53.110 --> 00:03:53.120 align:start position:0% dark for us we weren't sure exactly what 00:03:53.120 --> 00:03:55.300 align:start position:0% dark for us we weren't sure exactly what we<00:03:53.300> expect<00:03:53.720> so<00:03:53.900> it<00:03:53.989> was<00:03:54.200> kind<00:03:54.440> of<00:03:54.500> a<00:03:54.650> test<00:03:55.220> to 00:03:55.300 --> 00:03:55.310 align:start position:0% we expect so it was kind of a test to 00:03:55.310 --> 00:03:57.759 align:start position:0% we expect so it was kind of a test to see<00:03:55.519> how<00:03:55.670> it<00:03:55.820> will<00:03:56.030> be<00:03:56.090> received<00:03:56.769> among 00:03:57.759 --> 00:03:57.769 align:start position:0% see how it will be received among 00:03:57.769 --> 00:03:59.890 align:start position:0% see how it will be received among ourselves<00:03:57.950> before<00:03:58.910> we<00:03:58.940> release<00:03:59.360> the<00:03:59.510> website 00:03:59.890 --> 00:03:59.900 align:start position:0% ourselves before we release the website 00:03:59.900 --> 00:04:03.759 align:start position:0% ourselves before we release the website we<00:04:00.170> we<00:04:00.470> talked<00:04:00.769> and<00:04:00.920> we<00:04:01.010> say<00:04:01.190> ok<00:04:01.580> man<00:04:01.760> what<00:04:02.769> we 00:04:03.759 --> 00:04:03.769 align:start position:0% we we talked and we say ok man what we 00:04:03.769 --> 00:04:06.280 align:start position:0% we we talked and we say ok man what we consider<00:04:04.400> a<00:04:04.430> success<00:04:04.970> you<00:04:05.269> know<00:04:05.390> just<00:04:05.690> to<00:04:05.870> have 00:04:06.280 --> 00:04:06.290 align:start position:0% consider a success you know just to have 00:04:06.290 --> 00:04:08.979 align:start position:0% consider a success you know just to have some<00:04:06.590> some<00:04:07.489> numbers<00:04:07.940> and<00:04:08.090> Mario's<00:04:08.390> here<00:04:08.660> said 00:04:08.979 --> 00:04:08.989 align:start position:0% some some numbers and Mario's here said 00:04:08.989 --> 00:04:11.170 align:start position:0% some some numbers and Mario's here said like<00:04:09.200> 30<00:04:09.590> people<00:04:09.890> in<00:04:10.340> the<00:04:10.489> first<00:04:10.730> 24<00:04:11.150> hours 00:04:11.170 --> 00:04:11.180 align:start position:0% like 30 people in the first 24 hours 00:04:11.180 --> 00:04:12.370 align:start position:0% like 30 people in the first 24 hours would<00:04:11.780> be<00:04:11.840> cool 00:04:12.370 --> 00:04:12.380 align:start position:0% would be cool 00:04:12.380 --> 00:04:14.770 align:start position:0% would be cool roxanna<00:04:13.010> here<00:04:13.340> more<00:04:13.519> optimistic<00:04:14.150> 50<00:04:14.570> people 00:04:14.770 --> 00:04:14.780 align:start position:0% roxanna here more optimistic 50 people 00:04:14.780 --> 00:04:20.710 align:start position:0% roxanna here more optimistic 50 people and<00:04:15.380> I<00:04:15.560> was<00:04:15.680> secretly<00:04:18.790> 24<00:04:19.790> hours<00:04:20.090> later<00:04:20.359> we 00:04:20.710 --> 00:04:20.720 align:start position:0% and I was secretly 24 hours later we 00:04:20.720 --> 00:04:24.110 align:start position:0% and I was secretly 24 hours later we surpassed<00:04:21.230> 200<00:04:21.769> I<00:04:21.980> now<00:04:22.040> switch<00:04:22.250> was<00:04:22.669> like<00:04:22.820> whoa 00:04:24.110 --> 00:04:24.120 align:start position:0% surpassed 200 I now switch was like whoa 00:04:24.120 --> 00:04:26.629 align:start position:0% surpassed 200 I now switch was like whoa and<00:04:24.389> then<00:04:25.139> in<00:04:25.560> less<00:04:25.830> than<00:04:25.980> a<00:04:26.130> month<00:04:26.370> we 00:04:26.629 --> 00:04:26.639 align:start position:0% and then in less than a month we 00:04:26.639 --> 00:04:30.140 align:start position:0% and then in less than a month we surpassed<00:04:27.060> 2,000<00:04:27.660> people<00:04:27.870> so<00:04:28.770> it<00:04:29.669> became 00:04:30.140 --> 00:04:30.150 align:start position:0% surpassed 2,000 people so it became 00:04:30.150 --> 00:04:32.480 align:start position:0% surpassed 2,000 people so it became clear<00:04:30.360> that<00:04:30.750> we<00:04:30.870> weren't<00:04:31.169> crazy<00:04:31.380> or<00:04:31.830> that<00:04:32.340> we 00:04:32.480 --> 00:04:32.490 align:start position:0% clear that we weren't crazy or that we 00:04:32.490 --> 00:04:35.480 align:start position:0% clear that we weren't crazy or that we weren't<00:04:32.760> the<00:04:32.850> only<00:04:32.880> ones<00:04:33.410> so<00:04:34.410> Disney<00:04:35.160> these 00:04:35.480 --> 00:04:35.490 align:start position:0% weren't the only ones so Disney these 00:04:35.490 --> 00:04:37.820 align:start position:0% weren't the only ones so Disney these numbers<00:04:35.850> might<00:04:36.060> not<00:04:36.330> seem<00:04:36.690> much<00:04:36.870> at<00:04:37.080> first<00:04:37.320> but 00:04:37.820 --> 00:04:37.830 align:start position:0% numbers might not seem much at first but 00:04:37.830 --> 00:04:40.190 align:start position:0% numbers might not seem much at first but it's<00:04:38.040> worth<00:04:38.250> mentioning<00:04:38.280> that<00:04:38.850> every<00:04:39.750> single 00:04:40.190 --> 00:04:40.200 align:start position:0% it's worth mentioning that every single 00:04:40.200 --> 00:04:42.140 align:start position:0% it's worth mentioning that every single person<00:04:40.680> that<00:04:40.710> sign<00:04:41.130> up<00:04:41.340> for<00:04:41.550> the<00:04:41.669> Alpha 00:04:42.140 --> 00:04:42.150 align:start position:0% person that sign up for the Alpha 00:04:42.150 --> 00:04:45.170 align:start position:0% person that sign up for the Alpha reached<00:04:42.870> organically<00:04:43.770> our<00:04:43.860> website<00:04:44.400> so<00:04:44.730> we 00:04:45.170 --> 00:04:45.180 align:start position:0% reached organically our website so we 00:04:45.180 --> 00:04:47.659 align:start position:0% reached organically our website so we just<00:04:45.389> published<00:04:45.840> blog<00:04:46.110> post<00:04:46.410> linked<00:04:47.400> them<00:04:47.520> on 00:04:47.659 --> 00:04:47.669 align:start position:0% just published blog post linked them on 00:04:47.669 --> 00:04:50.780 align:start position:0% just published blog post linked them on reddit<00:04:48.090> or<00:04:48.360> tweeted<00:04:49.050> them<00:04:49.230> so<00:04:49.530> what<00:04:50.220> we<00:04:50.370> wanted 00:04:50.780 --> 00:04:50.790 align:start position:0% reddit or tweeted them so what we wanted 00:04:50.790 --> 00:04:52.700 align:start position:0% reddit or tweeted them so what we wanted was<00:04:51.000> to<00:04:51.180> measure<00:04:51.389> the<00:04:51.540> real<00:04:51.990> interest<00:04:52.440> in<00:04:52.620> the 00:04:52.700 --> 00:04:52.710 align:start position:0% was to measure the real interest in the 00:04:52.710 --> 00:04:55.129 align:start position:0% was to measure the real interest in the application<00:04:53.340> and<00:04:54.330> we<00:04:54.480> felt<00:04:54.750> that<00:04:54.810> paid 00:04:55.129 --> 00:04:55.139 align:start position:0% application and we felt that paid 00:04:55.139 --> 00:04:57.469 align:start position:0% application and we felt that paid advertising<00:04:55.770> would<00:04:56.100> taint<00:04:56.340> those<00:04:56.580> results<00:04:57.120> we 00:04:57.469 --> 00:04:57.479 align:start position:0% advertising would taint those results we 00:04:57.479 --> 00:04:59.270 align:start position:0% advertising would taint those results we would<00:04:57.660> end<00:04:57.810> up<00:04:57.960> measuring<00:04:58.260> the<00:04:58.620> efficiency<00:04:59.040> of 00:04:59.270 --> 00:04:59.280 align:start position:0% would end up measuring the efficiency of 00:04:59.280 --> 00:05:01.550 align:start position:0% would end up measuring the efficiency of targeted<00:04:59.760> ads<00:04:59.940> rather<00:05:00.570> than<00:05:00.870> the<00:05:01.110> real 00:05:01.550 --> 00:05:01.560 align:start position:0% targeted ads rather than the real 00:05:01.560 --> 00:05:03.890 align:start position:0% targeted ads rather than the real interest<00:05:02.010> in<00:05:02.280> in<00:05:02.790> the<00:05:02.940> application<00:05:03.419> and<00:05:03.510> idea 00:05:03.890 --> 00:05:03.900 align:start position:0% interest in in the application and idea 00:05:03.900 --> 00:05:07.820 align:start position:0% interest in in the application and idea so<00:05:04.590> fast<00:05:04.950> forwarding<00:05:05.520> until<00:05:05.940> early<00:05:06.240> 2017<00:05:07.050> one 00:05:07.820 --> 00:05:07.830 align:start position:0% so fast forwarding until early 2017 one 00:05:07.830 --> 00:05:10.280 align:start position:0% so fast forwarding until early 2017 one year<00:05:08.160> after<00:05:08.610> it<00:05:08.760> helium<00:05:09.180> we<00:05:09.810> launched<00:05:10.050> the 00:05:10.280 --> 00:05:10.290 align:start position:0% year after it helium we launched the 00:05:10.290 --> 00:05:13.129 align:start position:0% year after it helium we launched the first<00:05:10.560> public<00:05:10.979> version<00:05:11.160> of<00:05:11.430> the<00:05:11.610> Alpha<00:05:12.020> and<00:05:13.020> it 00:05:13.129 --> 00:05:13.139 align:start position:0% first public version of the Alpha and it 00:05:13.139 --> 00:05:15.170 align:start position:0% first public version of the Alpha and it was<00:05:13.320> called<00:05:13.620> into<00:05:13.860> the<00:05:14.040> ether<00:05:14.250> it<00:05:14.880> was 00:05:15.170 --> 00:05:15.180 align:start position:0% was called into the ether it was 00:05:15.180 --> 00:05:17.150 align:start position:0% was called into the ether it was received<00:05:15.540> very<00:05:15.690> well<00:05:15.930> by<00:05:16.080> the<00:05:16.260> community<00:05:16.830> and 00:05:17.150 --> 00:05:17.160 align:start position:0% received very well by the community and 00:05:17.160 --> 00:05:20.900 align:start position:0% received very well by the community and I<00:05:18.150> suppose<00:05:18.780> you<00:05:19.320> guys<00:05:19.530> also<00:05:19.800> tried<00:05:20.220> it<00:05:20.400> hope 00:05:20.900 --> 00:05:20.910 align:start position:0% I suppose you guys also tried it hope 00:05:20.910 --> 00:05:23.330 align:start position:0% I suppose you guys also tried it hope you<00:05:21.600> had<00:05:21.840> a<00:05:21.870> pleasant<00:05:21.960> experience<00:05:22.440> when<00:05:23.040> when 00:05:23.330 --> 00:05:23.340 align:start position:0% you had a pleasant experience when when 00:05:23.340 --> 00:05:25.850 align:start position:0% you had a pleasant experience when when you<00:05:23.520> when<00:05:24.210> you<00:05:24.300> tried<00:05:24.570> it<00:05:24.750> and<00:05:25.139> basically<00:05:25.530> in 00:05:25.850 --> 00:05:25.860 align:start position:0% you when you tried it and basically in 00:05:25.860 --> 00:05:28.640 align:start position:0% you when you tried it and basically in the<00:05:25.950> Alpha<00:05:26.220> we<00:05:26.570> tried<00:05:27.570> to<00:05:27.750> have<00:05:28.050> a<00:05:28.110> basic 00:05:28.640 --> 00:05:28.650 align:start position:0% the Alpha we tried to have a basic 00:05:28.650 --> 00:05:30.440 align:start position:0% the Alpha we tried to have a basic functionality<00:05:29.340> you<00:05:29.460> find<00:05:29.729> in<00:05:29.910> a<00:05:30.000> social 00:05:30.440 --> 00:05:30.450 align:start position:0% functionality you find in a social 00:05:30.450 --> 00:05:32.570 align:start position:0% functionality you find in a social network<00:05:30.479> which<00:05:31.440> was<00:05:31.650> to<00:05:31.800> publish<00:05:32.250> something 00:05:32.570 --> 00:05:32.580 align:start position:0% network which was to publish something 00:05:32.580 --> 00:05:34.310 align:start position:0% network which was to publish something to<00:05:33.000> comment<00:05:33.419> on<00:05:33.570> something<00:05:33.840> to<00:05:34.140> read 00:05:34.310 --> 00:05:34.320 align:start position:0% to comment on something to read 00:05:34.320 --> 00:05:36.820 align:start position:0% to comment on something to read something<00:05:34.890> to<00:05:35.070> vote<00:05:35.310> and<00:05:35.610> to<00:05:35.940> follow<00:05:36.150> people 00:05:36.820 --> 00:05:36.830 align:start position:0% something to vote and to follow people 00:05:36.830 --> 00:05:39.290 align:start position:0% something to vote and to follow people combined<00:05:37.830> also<00:05:38.039> with<00:05:38.370> things<00:05:38.640> like<00:05:38.820> since<00:05:39.120> we 00:05:39.290 --> 00:05:39.300 align:start position:0% combined also with things like since we 00:05:39.300 --> 00:05:40.790 align:start position:0% combined also with things like since we are<00:05:39.390> using<00:05:39.479> aetherium<00:05:40.140> one<00:05:40.289> of<00:05:40.410> the<00:05:40.560> side 00:05:40.790 --> 00:05:40.800 align:start position:0% are using aetherium one of the side 00:05:40.800 --> 00:05:43.159 align:start position:0% are using aetherium one of the side effects<00:05:41.160> is<00:05:41.460> that<00:05:41.520> each<00:05:42.060> identity<00:05:42.630> is<00:05:42.810> also<00:05:43.140> a 00:05:43.159 --> 00:05:43.169 align:start position:0% effects is that each identity is also a 00:05:43.169 --> 00:05:45.380 align:start position:0% effects is that each identity is also a wallet<00:05:43.680> so<00:05:44.160> people<00:05:44.460> can<00:05:44.610> also<00:05:44.789> send<00:05:45.210> resources 00:05:45.380 --> 00:05:45.390 align:start position:0% wallet so people can also send resources 00:05:45.390 --> 00:05:47.870 align:start position:0% wallet so people can also send resources to<00:05:46.140> each<00:05:46.289> other<00:05:46.560> and<00:05:46.919> so<00:05:47.520> forth 00:05:47.870 --> 00:05:47.880 align:start position:0% to each other and so forth 00:05:47.880 --> 00:05:50.900 align:start position:0% to each other and so forth and<00:05:48.060> after<00:05:49.050> the<00:05:49.200> release<00:05:49.470> one<00:05:49.860> of<00:05:50.160> this<00:05:50.820> is 00:05:50.900 --> 00:05:50.910 align:start position:0% and after the release one of this is 00:05:50.910 --> 00:05:53.719 align:start position:0% and after the release one of this is actually<00:05:51.300> a<00:05:51.330> screen<00:05:52.260> from<00:05:53.130> the<00:05:53.280> Akasha 00:05:53.719 --> 00:05:53.729 align:start position:0% actually a screen from the Akasha 00:05:53.729 --> 00:05:56.480 align:start position:0% actually a screen from the Akasha application<00:05:54.360> a<00:05:54.510> comment<00:05:54.990> and<00:05:55.169> on<00:05:56.039> the<00:05:56.250> first 00:05:56.480 --> 00:05:56.490 align:start position:0% application a comment and on the first 00:05:56.490 --> 00:05:58.969 align:start position:0% application a comment and on the first row<00:05:56.700> you<00:05:56.729> can<00:05:57.030> see<00:05:57.270> that<00:05:57.479> someone<00:05:58.139> it<00:05:58.500> was<00:05:58.620> like 00:05:58.969 --> 00:05:58.979 align:start position:0% row you can see that someone it was like 00:05:58.979 --> 00:06:01.850 align:start position:0% row you can see that someone it was like excited<00:05:59.970> that<00:06:00.210> there's<00:06:00.780> a<00:06:00.870> tab<00:06:01.169> that<00:06:01.200> normal 00:06:01.850 --> 00:06:01.860 align:start position:0% excited that there's a tab that normal 00:06:01.860 --> 00:06:04.879 align:start position:0% excited that there's a tab that normal people<00:06:02.250> can<00:06:02.460> use<00:06:02.700> and<00:06:02.940> for<00:06:03.810> us<00:06:03.960> I<00:06:04.260> was<00:06:04.710> like 00:06:04.879 --> 00:06:04.889 align:start position:0% people can use and for us I was like 00:06:04.889 --> 00:06:07.909 align:start position:0% people can use and for us I was like exactly<00:06:05.729> what<00:06:05.850> we<00:06:06.090> were<00:06:06.240> aiming<00:06:06.419> for<00:06:06.840> but<00:06:07.590> I 00:06:07.909 --> 00:06:07.919 align:start position:0% exactly what we were aiming for but I 00:06:07.919 --> 00:06:10.040 align:start position:0% exactly what we were aiming for but I think<00:06:08.280> the<00:06:08.430> big<00:06:08.639> point<00:06:08.970> here<00:06:09.090> was<00:06:09.539> that<00:06:09.570> with 00:06:10.040 --> 00:06:10.050 align:start position:0% think the big point here was that with 00:06:10.050 --> 00:06:12.379 align:start position:0% think the big point here was that with all<00:06:10.229> these<00:06:10.410> people<00:06:10.830> you<00:06:11.100> and<00:06:11.370> the<00:06:12.000> others<00:06:12.270> that 00:06:12.379 --> 00:06:12.389 align:start position:0% all these people you and the others that 00:06:12.389 --> 00:06:14.360 align:start position:0% all these people you and the others that might<00:06:12.660> be<00:06:12.840> watching<00:06:13.020> this<00:06:13.440> this<00:06:13.950> conference 00:06:14.360 --> 00:06:14.370 align:start position:0% might be watching this this conference 00:06:14.370 --> 00:06:17.450 align:start position:0% might be watching this this conference we<00:06:15.300> proved<00:06:15.690> that<00:06:16.020> it<00:06:16.169> is<00:06:16.530> possible<00:06:16.710> it<00:06:17.400> is 00:06:17.450 --> 00:06:17.460 align:start position:0% we proved that it is possible it is 00:06:17.460 --> 00:06:19.460 align:start position:0% we proved that it is possible it is possible<00:06:17.850> to<00:06:18.419> have<00:06:18.630> an<00:06:18.780> application<00:06:18.930> that 00:06:19.460 --> 00:06:19.470 align:start position:0% possible to have an application that 00:06:19.470 --> 00:06:21.830 align:start position:0% possible to have an application that does<00:06:19.530> not<00:06:19.860> rely<00:06:20.190> on<00:06:20.220> servers<00:06:20.789> for<00:06:21.389> people<00:06:21.720> to 00:06:21.830 --> 00:06:21.840 align:start position:0% does not rely on servers for people to 00:06:21.840 --> 00:06:24.830 align:start position:0% does not rely on servers for people to communicate<00:06:22.200> among<00:06:23.130> themselves<00:06:23.190> and<00:06:23.840> thanks 00:06:24.830 --> 00:06:24.840 align:start position:0% communicate among themselves and thanks 00:06:24.840 --> 00:06:26.719 align:start position:0% communicate among themselves and thanks to<00:06:24.960> your<00:06:25.139> playfulness<00:06:25.680> in<00:06:26.070> your<00:06:26.190> time<00:06:26.460> put 00:06:26.719 --> 00:06:26.729 align:start position:0% to your playfulness in your time put 00:06:26.729 --> 00:06:28.159 align:start position:0% to your playfulness in your time put into<00:06:26.880> testing<00:06:27.419> the<00:06:27.510> application<00:06:28.050> we 00:06:28.159 --> 00:06:28.169 align:start position:0% into testing the application we 00:06:28.169 --> 00:06:30.170 align:start position:0% into testing the application we identified<00:06:28.710> some<00:06:28.950> bugs<00:06:29.280> and<00:06:29.610> we<00:06:30.030> also 00:06:30.170 --> 00:06:30.180 align:start position:0% identified some bugs and we also 00:06:30.180 --> 00:06:32.890 align:start position:0% identified some bugs and we also identified<00:06:31.080> what<00:06:31.320> can<00:06:31.530> be<00:06:31.650> done<00:06:31.860> better<00:06:32.070> and 00:06:32.890 --> 00:06:32.900 align:start position:0% identified what can be done better and 00:06:32.900 --> 00:06:36.020 align:start position:0% identified what can be done better and Mario's<00:06:33.900> now<00:06:34.080> is<00:06:34.320> going<00:06:34.500> to<00:06:34.669> explain<00:06:35.669> one<00:06:35.909> of 00:06:36.020 --> 00:06:36.030 align:start position:0% Mario's now is going to explain one of 00:06:36.030 --> 00:06:37.230 align:start position:0% Mario's now is going to explain one of the<00:06:36.150> lessons<00:06:36.330> we<00:06:36.510> learn<00:06:36.780> in 00:06:37.230 --> 00:06:37.240 align:start position:0% the lessons we learn in 00:06:37.240 --> 00:06:39.330 align:start position:0% the lessons we learn in alpha<00:06:37.780> and<00:06:38.110> that<00:06:38.410> be<00:06:38.590> applied<00:06:38.889> in<00:06:39.039> the<00:06:39.130> beta 00:06:39.330 --> 00:06:39.340 align:start position:0% alpha and that be applied in the beta 00:06:39.340 --> 00:06:40.290 align:start position:0% alpha and that be applied in the beta Marius 00:06:40.290 --> 00:06:40.300 align:start position:0% Marius 00:06:40.300 --> 00:06:45.059 align:start position:0% Marius thank<00:06:40.840> you<00:06:41.370> yeah<00:06:42.720> so<00:06:43.720> what<00:06:44.020> is<00:06:44.169> this<00:06:44.289> yeah<00:06:44.800> I 00:06:45.059 --> 00:06:45.069 align:start position:0% thank you yeah so what is this yeah I 00:06:45.069 --> 00:06:48.779 align:start position:0% thank you yeah so what is this yeah I think<00:06:45.729> all<00:06:46.150> the<00:06:47.110> Alpha<00:06:47.440> users<00:06:47.919> got<00:06:48.250> stuck<00:06:48.550> at<00:06:48.759> a 00:06:48.779 --> 00:06:48.789 align:start position:0% think all the Alpha users got stuck at a 00:06:48.789 --> 00:06:52.409 align:start position:0% think all the Alpha users got stuck at a given<00:06:49.449> time<00:06:49.660> in<00:06:49.990> this<00:06:50.280> loading<00:06:51.419> loading 00:06:52.409 --> 00:06:52.419 align:start position:0% given time in this loading loading 00:06:52.419 --> 00:06:57.749 align:start position:0% given time in this loading loading screen<00:06:55.380> this<00:06:56.380> was<00:06:56.590> happening<00:06:57.039> because<00:06:57.220> of<00:06:57.490> the 00:06:57.749 --> 00:06:57.759 align:start position:0% screen this was happening because of the 00:06:57.759 --> 00:07:01.110 align:start position:0% screen this was happening because of the way<00:06:57.970> we<00:06:58.479> used<00:06:58.810> to<00:06:59.050> load<00:06:59.199> the<00:06:59.440> resources<00:07:00.130> we 00:07:01.110 --> 00:07:01.120 align:start position:0% way we used to load the resources we 00:07:01.120 --> 00:07:04.640 align:start position:0% way we used to load the resources we were<00:07:01.270> trying<00:07:01.599> to<00:07:01.780> get<00:07:01.960> all<00:07:02.319> of<00:07:02.560> them<00:07:02.740> at<00:07:02.919> once 00:07:04.640 --> 00:07:04.650 align:start position:0% were trying to get all of them at once 00:07:04.650 --> 00:07:09.360 align:start position:0% were trying to get all of them at once so<00:07:05.650> if<00:07:06.630> given<00:07:07.630> time<00:07:07.860> one<00:07:08.860> of<00:07:08.889> the<00:07:09.130> resources 00:07:09.360 --> 00:07:09.370 align:start position:0% so if given time one of the resources 00:07:09.370 --> 00:07:13.439 align:start position:0% so if given time one of the resources would<00:07:10.240> would<00:07:10.810> be<00:07:10.840> unavailable<00:07:11.440> the<00:07:12.449> other 00:07:13.439 --> 00:07:13.449 align:start position:0% would would be unavailable the other 00:07:13.449 --> 00:07:15.689 align:start position:0% would would be unavailable the other resources<00:07:14.050> would<00:07:14.470> have<00:07:14.740> to<00:07:14.919> wait<00:07:15.099> for<00:07:15.550> that 00:07:15.689 --> 00:07:15.699 align:start position:0% resources would have to wait for that 00:07:15.699 --> 00:07:18.330 align:start position:0% resources would have to wait for that one<00:07:15.909> to<00:07:16.030> become<00:07:16.300> online<00:07:16.599> before<00:07:17.340> fetching 00:07:18.330 --> 00:07:18.340 align:start position:0% one to become online before fetching 00:07:18.340 --> 00:07:20.089 align:start position:0% one to become online before fetching them<00:07:18.490> to<00:07:19.210> the<00:07:19.330> user 00:07:20.089 --> 00:07:20.099 align:start position:0% them to the user 00:07:20.099 --> 00:07:25.080 align:start position:0% them to the user so<00:07:21.539> in<00:07:22.539> the<00:07:22.780> beta<00:07:23.020> version<00:07:23.280> this<00:07:24.280> was<00:07:24.610> one<00:07:24.970> of 00:07:25.080 --> 00:07:25.090 align:start position:0% so in the beta version this was one of 00:07:25.090 --> 00:07:29.600 align:start position:0% so in the beta version this was one of the<00:07:25.210> biggest<00:07:25.419> challenge<00:07:25.870> we<00:07:26.500> we<00:07:27.250> had<00:07:27.460> to<00:07:27.699> solve 00:07:29.600 --> 00:07:29.610 align:start position:0% the biggest challenge we we had to solve 00:07:29.610 --> 00:07:33.029 align:start position:0% the biggest challenge we we had to solve we've<00:07:30.610> done<00:07:30.970> this<00:07:31.120> by<00:07:31.360> loading<00:07:31.810> every<00:07:32.680> single 00:07:33.029 --> 00:07:33.039 align:start position:0% we've done this by loading every single 00:07:33.039 --> 00:07:35.399 align:start position:0% we've done this by loading every single resource<00:07:33.400> individually<00:07:34.270> as<00:07:34.509> you<00:07:34.930> can<00:07:35.080> see<00:07:35.289> in 00:07:35.399 --> 00:07:35.409 align:start position:0% resource individually as you can see in 00:07:35.409 --> 00:07:38.580 align:start position:0% resource individually as you can see in this<00:07:35.620> demo<00:07:36.159> yeah<00:07:36.759> so<00:07:37.569> it<00:07:37.960> comes<00:07:38.199> with<00:07:38.349> a<00:07:38.470> great 00:07:38.580 --> 00:07:38.590 align:start position:0% this demo yeah so it comes with a great 00:07:38.590 --> 00:07:45.300 align:start position:0% this demo yeah so it comes with a great improvement<00:07:39.490> on<00:07:39.909> the<00:07:40.419> UX<00:07:41.310> side<00:07:43.380> so<00:07:44.380> enough 00:07:45.300 --> 00:07:45.310 align:start position:0% improvement on the UX side so enough 00:07:45.310 --> 00:07:48.029 align:start position:0% improvement on the UX side so enough with<00:07:45.340> this<00:07:45.750> so<00:07:46.750> another<00:07:46.990> highlight<00:07:47.440> of<00:07:47.469> the<00:07:47.740> of 00:07:48.029 --> 00:07:48.039 align:start position:0% with this so another highlight of the of 00:07:48.039 --> 00:07:50.399 align:start position:0% with this so another highlight of the of the<00:07:48.250> beta<00:07:48.460> is<00:07:48.820> the<00:07:49.120> first<00:07:49.539> token<00:07:49.750> experiment 00:07:50.399 --> 00:07:50.409 align:start position:0% the beta is the first token experiment 00:07:50.409 --> 00:07:52.920 align:start position:0% the beta is the first token experiment in<00:07:50.620> the<00:07:50.740> alpha<00:07:51.039> we<00:07:51.159> had<00:07:51.370> a<00:07:51.580> ETH<00:07:52.120> which<00:07:52.449> served 00:07:52.920 --> 00:07:52.930 align:start position:0% in the alpha we had a ETH which served 00:07:52.930 --> 00:07:55.589 align:start position:0% in the alpha we had a ETH which served as<00:07:53.080> a<00:07:53.139> placeholder<00:07:53.500> token<00:07:54.219> and<00:07:54.400> I<00:07:55.210> just<00:07:55.419> want 00:07:55.589 --> 00:07:55.599 align:start position:0% as a placeholder token and I just want 00:07:55.599 --> 00:07:58.740 align:start position:0% as a placeholder token and I just want to<00:07:55.780> make<00:07:56.320> something<00:07:56.680> clear<00:07:56.830> this<00:07:57.729> is<00:07:58.030> there<00:07:58.630> is 00:07:58.740 --> 00:07:58.750 align:start position:0% to make something clear this is there is 00:07:58.750 --> 00:08:00.870 align:start position:0% to make something clear this is there is just<00:07:58.990> one<00:07:59.199> token<00:07:59.590> which<00:07:59.860> is<00:08:00.070> this<00:08:00.340> currently 00:08:00.870 --> 00:08:00.880 align:start position:0% just one token which is this currently 00:08:00.880 --> 00:08:03.300 align:start position:0% just one token which is this currently in<00:08:01.000> nicknamed<00:08:01.960> n-eth<00:08:02.380> we<00:08:02.830> are<00:08:02.919> open<00:08:03.190> to 00:08:03.300 --> 00:08:03.310 align:start position:0% in nicknamed n-eth we are open to 00:08:03.310 --> 00:08:04.020 align:start position:0% in nicknamed n-eth we are open to suggestions 00:08:04.020 --> 00:08:04.030 align:start position:0% suggestions 00:08:04.030 --> 00:08:06.390 align:start position:0% suggestions regarding<00:08:04.930> the<00:08:05.050> name<00:08:05.229> we<00:08:05.650> want<00:08:05.860> to<00:08:06.009> avoid 00:08:06.390 --> 00:08:06.400 align:start position:0% regarding the name we want to avoid 00:08:06.400 --> 00:08:08.820 align:start position:0% regarding the name we want to avoid confusion<00:08:06.940> with<00:08:07.060> other<00:08:07.240> projects<00:08:07.840> like<00:08:07.990> idiom 00:08:08.820 --> 00:08:08.830 align:start position:0% confusion with other projects like idiom 00:08:08.830 --> 00:08:16.050 align:start position:0% confusion with other projects like idiom if<00:08:08.979> any<00:08:12.750> and<00:08:13.800> this<00:08:14.800> is<00:08:15.009> just<00:08:15.219> an<00:08:15.370> experiment<00:08:15.669> to 00:08:16.050 --> 00:08:16.060 align:start position:0% if any and this is just an experiment to 00:08:16.060 --> 00:08:18.480 align:start position:0% if any and this is just an experiment to get<00:08:16.210> the<00:08:16.270> power<00:08:16.539> running<00:08:16.810> right<00:08:17.199> so<00:08:17.500> we<00:08:17.710> fully 00:08:18.480 --> 00:08:18.490 align:start position:0% get the power running right so we fully 00:08:18.490 --> 00:08:21.839 align:start position:0% get the power running right so we fully assume<00:08:19.060> that<00:08:19.270> we<00:08:19.690> are<00:08:20.159> we<00:08:21.159> don't<00:08:21.370> have<00:08:21.520> all<00:08:21.699> the 00:08:21.839 --> 00:08:21.849 align:start position:0% assume that we are we don't have all the 00:08:21.849 --> 00:08:24.439 align:start position:0% assume that we are we don't have all the answers<00:08:21.880> but<00:08:22.750> we<00:08:23.020> invite<00:08:23.319> everyone<00:08:23.830> to 00:08:24.439 --> 00:08:24.449 align:start position:0% answers but we invite everyone to 00:08:24.449 --> 00:08:26.790 align:start position:0% answers but we invite everyone to collaborate<00:08:25.449> on<00:08:25.479> finding<00:08:25.960> them<00:08:26.110> so<00:08:26.500> to<00:08:26.590> give 00:08:26.790 --> 00:08:26.800 align:start position:0% collaborate on finding them so to give 00:08:26.800 --> 00:08:29.089 align:start position:0% collaborate on finding them so to give you<00:08:26.830> an<00:08:27.130> overview<00:08:27.580> of<00:08:27.789> how<00:08:27.880> these<00:08:28.210> token<00:08:28.630> works 00:08:29.089 --> 00:08:29.099 align:start position:0% you an overview of how these token works 00:08:29.099 --> 00:08:33.480 align:start position:0% you an overview of how these token works on<00:08:30.099> the<00:08:30.460> surface<00:08:30.880> a<00:08:31.030> ETH<00:08:31.539> is<00:08:31.810> in<00:08:32.200> an<00:08:32.560> ear<00:08:32.890> C<00:08:33.159> 20 00:08:33.480 --> 00:08:33.490 align:start position:0% on the surface a ETH is in an ear C 20 00:08:33.490 --> 00:08:35.969 align:start position:0% on the surface a ETH is in an ear C 20 compatible<00:08:34.000> token<00:08:34.419> it<00:08:34.930> works<00:08:35.260> pretty<00:08:35.469> much<00:08:35.620> as 00:08:35.969 --> 00:08:35.979 align:start position:0% compatible token it works pretty much as 00:08:35.979 --> 00:08:37.469 align:start position:0% compatible token it works pretty much as you<00:08:36.099> would<00:08:36.219> expect<00:08:36.370> from<00:08:36.760> an<00:08:36.909> ear<00:08:37.029> seatback 00:08:37.469 --> 00:08:37.479 align:start position:0% you would expect from an ear seatback 00:08:37.479 --> 00:08:39.990 align:start position:0% you would expect from an ear seatback token<00:08:38.169> you<00:08:38.320> can<00:08:38.469> send<00:08:38.770> and<00:08:38.979> receive<00:08:39.010> but<00:08:39.849> there 00:08:39.990 --> 00:08:40.000 align:start position:0% token you can send and receive but there 00:08:40.000 --> 00:08:42.089 align:start position:0% token you can send and receive but there is<00:08:40.089> a<00:08:40.120> twist<00:08:40.479> you<00:08:41.260> can<00:08:41.440> lock<00:08:41.680> it<00:08:41.860> for<00:08:42.039> a 00:08:42.089 --> 00:08:42.099 align:start position:0% is a twist you can lock it for a 00:08:42.099 --> 00:08:44.490 align:start position:0% is a twist you can lock it for a predefined<00:08:42.640> amount<00:08:43.270> of<00:08:43.419> time<00:08:43.599> and<00:08:43.810> this<00:08:44.200> will 00:08:44.490 --> 00:08:44.500 align:start position:0% predefined amount of time and this will 00:08:44.500 --> 00:08:46.710 align:start position:0% predefined amount of time and this will give<00:08:44.770> you<00:08:44.890> some<00:08:45.220> something<00:08:46.060> we<00:08:46.240> call<00:08:46.420> mana 00:08:46.710 --> 00:08:46.720 align:start position:0% give you some something we call mana 00:08:46.720 --> 00:08:49.560 align:start position:0% give you some something we call mana which<00:08:47.290> acts<00:08:47.560> like<00:08:47.650> a<00:08:48.220> regional<00:08:49.150> creep 00:08:49.560 --> 00:08:49.570 align:start position:0% which acts like a regional creep 00:08:49.570 --> 00:08:51.240 align:start position:0% which acts like a regional creep that<00:08:50.110> can<00:08:50.350> be<00:08:50.500> burned<00:08:50.740> inside<00:08:51.100> the 00:08:51.240 --> 00:08:51.250 align:start position:0% that can be burned inside the 00:08:51.250 --> 00:08:53.250 align:start position:0% that can be burned inside the application<00:08:51.820> Maurice<00:08:52.510> will<00:08:52.690> cover<00:08:52.930> this<00:08:53.200> in 00:08:53.250 --> 00:08:53.260 align:start position:0% application Maurice will cover this in 00:08:53.260 --> 00:08:56.660 align:start position:0% application Maurice will cover this in more<00:08:53.470> detail<00:08:53.860> afterwards<00:08:54.430> and<00:08:54.790> essence<00:08:55.660> is 00:08:56.660 --> 00:08:56.670 align:start position:0% more detail afterwards and essence is 00:08:56.670 --> 00:09:01.500 align:start position:0% more detail afterwards and essence is basically<00:08:57.670> mana<00:08:58.390> that<00:08:58.660> is<00:08:58.810> burned<00:08:59.170> and<00:08:59.500> if<00:09:00.510> the 00:09:01.500 --> 00:09:01.510 align:start position:0% basically mana that is burned and if the 00:09:01.510 --> 00:09:03.420 align:start position:0% basically mana that is burned and if the quality<00:09:02.020> of<00:09:02.050> the<00:09:02.140> content<00:09:02.620> is<00:09:02.680> deemed<00:09:02.980> as<00:09:03.130> good 00:09:03.420 --> 00:09:03.430 align:start position:0% quality of the content is deemed as good 00:09:03.430 --> 00:09:06.060 align:start position:0% quality of the content is deemed as good the<00:09:04.030> authors<00:09:04.480> and<00:09:04.510> the<00:09:04.870> persons<00:09:05.440> interacting 00:09:06.060 --> 00:09:06.070 align:start position:0% the authors and the persons interacting 00:09:06.070 --> 00:09:09.270 align:start position:0% the authors and the persons interacting can<00:09:06.480> consume<00:09:07.480> this<00:09:07.690> essence<00:09:08.260> to<00:09:08.500> mint<00:09:08.800> new 00:09:09.270 --> 00:09:09.280 align:start position:0% can consume this essence to mint new 00:09:09.280 --> 00:09:12.510 align:start position:0% can consume this essence to mint new tokens<00:09:09.790> in<00:09:09.910> existence<00:09:10.510> and<00:09:10.840> not<00:09:11.410> Leslie<00:09:11.740> karma 00:09:12.510 --> 00:09:12.520 align:start position:0% tokens in existence and not Leslie karma 00:09:12.520 --> 00:09:14.190 align:start position:0% tokens in existence and not Leslie karma is<00:09:12.730> our<00:09:12.940> experiment<00:09:13.630> on<00:09:13.810> the<00:09:13.960> proto 00:09:14.190 --> 00:09:14.200 align:start position:0% is our experiment on the proto 00:09:14.200 --> 00:09:18.990 align:start position:0% is our experiment on the proto reputation<00:09:14.860> layer<00:09:15.040> and<00:09:17.550> Mario's<00:09:18.550> now<00:09:18.730> we'll 00:09:18.990 --> 00:09:19.000 align:start position:0% reputation layer and Mario's now we'll 00:09:19.000 --> 00:09:22.020 align:start position:0% reputation layer and Mario's now we'll give<00:09:19.420> you<00:09:19.570> a<00:09:20.260> presentation<00:09:21.100> of<00:09:21.370> the<00:09:21.430> token 00:09:22.020 --> 00:09:22.030 align:start position:0% give you a presentation of the token 00:09:22.030 --> 00:09:24.060 align:start position:0% give you a presentation of the token flow<00:09:22.300> of<00:09:22.630> the<00:09:22.900> states<00:09:23.230> and<00:09:23.560> how<00:09:23.770> everything 00:09:24.060 --> 00:09:24.070 align:start position:0% flow of the states and how everything 00:09:24.070 --> 00:09:31.350 align:start position:0% flow of the states and how everything ties<00:09:24.460> in<00:09:24.670> together<00:09:29.130> so<00:09:30.130> so<00:09:30.610> starting<00:09:31.030> from<00:09:31.180> the 00:09:31.350 --> 00:09:31.360 align:start position:0% ties in together so so starting from the 00:09:31.360 --> 00:09:34.170 align:start position:0% ties in together so so starting from the better<00:09:31.570> version<00:09:31.840> every<00:09:32.830> user<00:09:33.070> we<00:09:33.520> have<00:09:33.850> to 00:09:34.170 --> 00:09:34.180 align:start position:0% better version every user we have to 00:09:34.180 --> 00:09:38.070 align:start position:0% better version every user we have to burn<00:09:34.420> a<00:09:34.750> small<00:09:35.080> amount<00:09:35.410> of<00:09:35.550> mana<00:09:36.690> to<00:09:37.690> interact 00:09:38.070 --> 00:09:38.080 align:start position:0% burn a small amount of mana to interact 00:09:38.080 --> 00:09:41.070 align:start position:0% burn a small amount of mana to interact with<00:09:38.140> the<00:09:38.290> application<00:09:38.860> so<00:09:39.510> how<00:09:40.510> do<00:09:40.570> we<00:09:40.750> how<00:09:41.020> do 00:09:41.070 --> 00:09:41.080 align:start position:0% with the application so how do we how do 00:09:41.080 --> 00:09:45.600 align:start position:0% with the application so how do we how do we<00:09:41.260> get<00:09:41.470> mana<00:09:42.690> the<00:09:43.690> user<00:09:43.900> can<00:09:44.190> get<00:09:45.190> some<00:09:45.430> mana 00:09:45.600 --> 00:09:45.610 align:start position:0% we get mana the user can get some mana 00:09:45.610 --> 00:09:48.330 align:start position:0% we get mana the user can get some mana by<00:09:45.820> locking<00:09:46.450> his<00:09:47.020> Akasha<00:09:47.680> tokens<00:09:48.130> for<00:09:48.280> a 00:09:48.330 --> 00:09:48.340 align:start position:0% by locking his Akasha tokens for a 00:09:48.340 --> 00:09:51.200 align:start position:0% by locking his Akasha tokens for a period<00:09:48.670> of<00:09:48.850> time<00:09:49.150> during<00:09:49.780> which<00:09:50.260> he<00:09:50.800> gets 00:09:51.200 --> 00:09:51.210 align:start position:0% period of time during which he gets 00:09:51.210 --> 00:09:57.030 align:start position:0% period of time during which he gets periodically<00:09:52.210> the<00:09:52.960> mana<00:09:53.200> replenished<00:09:56.040> the 00:09:57.030 --> 00:09:57.040 align:start position:0% periodically the mana replenished the 00:09:57.040 --> 00:10:02.760 align:start position:0% periodically the mana replenished the man<00:09:57.220> I<00:09:57.250> used<00:09:57.370> for<00:09:59.130> the<00:10:00.130> mana<00:10:00.490> burned<00:10:00.910> for<00:10:01.810> doing 00:10:02.760 --> 00:10:02.770 align:start position:0% man I used for the mana burned for doing 00:10:02.770 --> 00:10:05.790 align:start position:0% man I used for the mana burned for doing actions<00:10:03.190> in<00:10:03.400> a<00:10:03.520> cursor<00:10:04.110> can<00:10:05.110> be<00:10:05.320> collected 00:10:05.790 --> 00:10:05.800 align:start position:0% actions in a cursor can be collected 00:10:05.800 --> 00:10:11.970 align:start position:0% actions in a cursor can be collected afterwards<00:10:09.480> into<00:10:10.480> two<00:10:10.870> specific<00:10:11.500> resources 00:10:11.970 --> 00:10:11.980 align:start position:0% afterwards into two specific resources 00:10:11.980 --> 00:10:14.850 align:start position:0% afterwards into two specific resources called<00:10:12.640> instance<00:10:13.300> and<00:10:13.510> karma<00:10:13.900> karma<00:10:14.350> will 00:10:14.850 --> 00:10:14.860 align:start position:0% called instance and karma karma will 00:10:14.860 --> 00:10:16.890 align:start position:0% called instance and karma karma will serve<00:10:15.100> in<00:10:15.370> Akasha<00:10:15.640> like<00:10:15.880> some<00:10:16.150> sort<00:10:16.420> of<00:10:16.570> proto 00:10:16.890 --> 00:10:16.900 align:start position:0% serve in Akasha like some sort of proto 00:10:16.900 --> 00:10:19.380 align:start position:0% serve in Akasha like some sort of proto reputation<00:10:17.560> which<00:10:18.070> will<00:10:18.280> unlock<00:10:18.430> specific 00:10:19.380 --> 00:10:19.390 align:start position:0% reputation which will unlock specific 00:10:19.390 --> 00:10:22.200 align:start position:0% reputation which will unlock specific features<00:10:19.900> like<00:10:20.160> creating<00:10:21.160> communities<00:10:21.790> and 00:10:22.200 --> 00:10:22.210 align:start position:0% features like creating communities and 00:10:22.210 --> 00:10:24.720 align:start position:0% features like creating communities and so<00:10:22.360> on<00:10:22.510> which<00:10:23.050> will<00:10:23.170> require<00:10:23.410> to<00:10:24.370> be<00:10:24.460> above 00:10:24.720 --> 00:10:24.730 align:start position:0% so on which will require to be above 00:10:24.730 --> 00:10:27.920 align:start position:0% so on which will require to be above level<00:10:25.720> of<00:10:25.840> karma<00:10:26.230> the<00:10:26.710> other<00:10:26.860> one<00:10:27.100> the<00:10:27.250> essence 00:10:27.920 --> 00:10:27.930 align:start position:0% level of karma the other one the essence 00:10:27.930 --> 00:10:31.470 align:start position:0% level of karma the other one the essence it's<00:10:28.930> interesting<00:10:29.260> because<00:10:29.730> this<00:10:30.730> is<00:10:31.180> the 00:10:31.470 --> 00:10:31.480 align:start position:0% it's interesting because this is the 00:10:31.480 --> 00:10:34.380 align:start position:0% it's interesting because this is the first<00:10:31.830> idea<00:10:32.830> which<00:10:33.730> came<00:10:33.940> to<00:10:34.060> us<00:10:34.210> to 00:10:34.380 --> 00:10:34.390 align:start position:0% first idea which came to us to 00:10:34.390 --> 00:10:37.710 align:start position:0% first idea which came to us to incentivize<00:10:35.280> the<00:10:36.280> users<00:10:36.610> to<00:10:36.850> create<00:10:37.300> content 00:10:37.710 --> 00:10:37.720 align:start position:0% incentivize the users to create content 00:10:37.720 --> 00:10:38.490 align:start position:0% incentivize the users to create content on<00:10:37.840> Akasha 00:10:38.490 --> 00:10:38.500 align:start position:0% on Akasha 00:10:38.500 --> 00:10:41.220 align:start position:0% on Akasha because<00:10:39.010> it<00:10:39.280> can<00:10:39.460> be<00:10:39.610> consumed<00:10:40.090> to<00:10:40.570> mint<00:10:40.810> new 00:10:41.220 --> 00:10:41.230 align:start position:0% because it can be consumed to mint new 00:10:41.230 --> 00:10:44.670 align:start position:0% because it can be consumed to mint new years<00:10:41.860> to<00:10:41.950> 20<00:10:42.520> Akasha<00:10:42.910> tokens<00:10:43.390> and<00:10:43.780> we<00:10:44.440> spent 00:10:44.670 --> 00:10:44.680 align:start position:0% years to 20 Akasha tokens and we spent 00:10:44.680 --> 00:10:48.990 align:start position:0% years to 20 Akasha tokens and we spent afterwards<00:10:45.540> also<00:10:46.540> at<00:10:46.930> any<00:10:47.080> given<00:10:47.410> time 00:10:48.990 --> 00:10:49.000 align:start position:0% afterwards also at any given time 00:10:49.000 --> 00:10:52.400 align:start position:0% afterwards also at any given time the<00:10:49.540> user<00:10:49.780> can<00:10:49.990> unlocked<00:10:50.530> the<00:10:50.850> magnified 00:10:52.400 --> 00:10:52.410 align:start position:0% the user can unlocked the magnified 00:10:52.410 --> 00:10:56.610 align:start position:0% the user can unlocked the magnified tokens<00:10:53.410> and<00:10:54.330> afterwards<00:10:55.330> it<00:10:55.450> will<00:10:55.570> go<00:10:55.810> to<00:10:55.870> the 00:10:56.610 --> 00:10:56.620 align:start position:0% tokens and afterwards it will go to the 00:10:56.620 --> 00:10:58.980 align:start position:0% tokens and afterwards it will go to the Year<00:10:56.890> c20<00:10:57.430> state<00:10:57.670> by<00:10:58.060> passing<00:10:58.540> to<00:10:58.690> a<00:10:58.720> delay 00:10:58.980 --> 00:10:58.990 align:start position:0% Year c20 state by passing to a delay 00:10:58.990 --> 00:11:02.220 align:start position:0% Year c20 state by passing to a delay time<00:10:59.230> which<00:10:59.770> we<00:10:59.950> call<00:11:00.160> it<00:11:00.310> a<00:11:00.340> cycle<00:11:00.670> yeah<00:11:01.600> so 00:11:02.220 --> 00:11:02.230 align:start position:0% time which we call it a cycle yeah so 00:11:02.230 --> 00:11:03.519 align:start position:0% time which we call it a cycle yeah so let's<00:11:02.560> see 00:11:03.519 --> 00:11:03.529 align:start position:0% let's see 00:11:03.529 --> 00:11:06.769 align:start position:0% let's see and<00:11:04.529> basic<00:11:05.189> flow<00:11:05.369> so<00:11:05.819> we<00:11:05.850> have<00:11:06.269> the<00:11:06.420> publisher 00:11:06.769 --> 00:11:06.779 align:start position:0% and basic flow so we have the publisher 00:11:06.779 --> 00:11:10.220 align:start position:0% and basic flow so we have the publisher which<00:11:07.439> post<00:11:07.739> an<00:11:08.009> entry<00:11:08.129> on<00:11:08.610> Akasha<00:11:09.230> the 00:11:10.220 --> 00:11:10.230 align:start position:0% which post an entry on Akasha the 00:11:10.230 --> 00:11:12.639 align:start position:0% which post an entry on Akasha the readers<00:11:10.559> afterwards<00:11:11.249> can<00:11:11.519> express<00:11:11.819> their 00:11:12.639 --> 00:11:12.649 align:start position:0% readers afterwards can express their 00:11:12.649 --> 00:11:15.889 align:start position:0% readers afterwards can express their general<00:11:13.649> feeling<00:11:13.980> about<00:11:14.249> the<00:11:14.639> quality<00:11:15.209> of<00:11:15.600> the 00:11:15.889 --> 00:11:15.899 align:start position:0% general feeling about the quality of the 00:11:15.899 --> 00:11:20.139 align:start position:0% general feeling about the quality of the content<00:11:16.139> by<00:11:16.589> voting<00:11:17.399> after<00:11:18.179> a<00:11:18.959> voting<00:11:19.379> period 00:11:20.139 --> 00:11:20.149 align:start position:0% content by voting after a voting period 00:11:20.149 --> 00:11:22.759 align:start position:0% content by voting after a voting period the<00:11:21.149> entry<00:11:21.449> will<00:11:21.720> generate<00:11:22.139> a<00:11:22.199> small<00:11:22.410> amount 00:11:22.759 --> 00:11:22.769 align:start position:0% the entry will generate a small amount 00:11:22.769 --> 00:11:25.220 align:start position:0% the entry will generate a small amount of<00:11:22.980> essence<00:11:23.489> which<00:11:24.239> afterwards<00:11:24.629> can<00:11:25.110> be 00:11:25.220 --> 00:11:25.230 align:start position:0% of essence which afterwards can be 00:11:25.230 --> 00:11:27.999 align:start position:0% of essence which afterwards can be claimed<00:11:25.499> by<00:11:25.649> both<00:11:25.769> publisher<00:11:26.519> and<00:11:26.759> the<00:11:26.910> reader 00:11:27.999 --> 00:11:28.009 align:start position:0% claimed by both publisher and the reader 00:11:28.009 --> 00:11:36.049 align:start position:0% claimed by both publisher and the reader by<00:11:29.420> specific<00:11:34.339> when<00:11:35.339> we<00:11:35.459> were<00:11:35.610> starting<00:11:35.850> to 00:11:36.049 --> 00:11:36.059 align:start position:0% by specific when we were starting to 00:11:36.059 --> 00:11:38.359 align:start position:0% by specific when we were starting to feel<00:11:36.299> good<00:11:36.600> about<00:11:36.720> ourselves<00:11:37.049> like<00:11:37.679> Yemen<00:11:38.160> I 00:11:38.359 --> 00:11:38.369 align:start position:0% feel good about ourselves like Yemen I 00:11:38.369 --> 00:11:40.239 align:start position:0% feel good about ourselves like Yemen I think<00:11:38.579> we're<00:11:38.699> onto<00:11:38.850> something<00:11:38.999> here 00:11:40.239 --> 00:11:40.249 align:start position:0% think we're onto something here 00:11:40.249 --> 00:11:44.269 align:start position:0% think we're onto something here Vitalik<00:11:41.249> did<00:11:41.459> it<00:11:41.579> again<00:11:42.079> so<00:11:43.079> then<00:11:43.290> just<00:11:43.920> a<00:11:44.100> few 00:11:44.269 --> 00:11:44.279 align:start position:0% Vitalik did it again so then just a few 00:11:44.279 --> 00:11:46.579 align:start position:0% Vitalik did it again so then just a few days<00:11:44.519> ago<00:11:44.790> Vitalik<00:11:45.239> published<00:11:45.660> this<00:11:45.809> this 00:11:46.579 --> 00:11:46.589 align:start position:0% days ago Vitalik published this this 00:11:46.589 --> 00:11:50.569 align:start position:0% days ago Vitalik published this this entry<00:11:47.040> so<00:11:47.629> he<00:11:48.629> basically<00:11:49.189> pointed<00:11:50.189> out<00:11:50.369> that 00:11:50.569 --> 00:11:50.579 align:start position:0% entry so he basically pointed out that 00:11:50.579 --> 00:11:55.069 align:start position:0% entry so he basically pointed out that there<00:11:50.730> are<00:11:51.079> more<00:11:52.079> than<00:11:52.319> just<00:11:53.449> so<00:11:54.449> a<00:11:54.480> good<00:11:54.779> talk 00:11:55.069 --> 00:11:55.079 align:start position:0% there are more than just so a good talk 00:11:55.079 --> 00:11:58.639 align:start position:0% there are more than just so a good talk and<00:11:55.110> economic<00:11:55.949> system<00:11:57.290> requires<00:11:58.290> more<00:11:58.589> than 00:11:58.639 --> 00:11:58.649 align:start position:0% and economic system requires more than 00:11:58.649 --> 00:12:02.479 align:start position:0% and economic system requires more than just<00:11:59.040> a<00:11:59.489> way<00:11:59.759> to<00:11:59.819> insert<00:12:00.540> units<00:12:01.230> of<00:12:01.489> that 00:12:02.479 --> 00:12:02.489 align:start position:0% just a way to insert units of that 00:12:02.489 --> 00:12:05.590 align:start position:0% just a way to insert units of that particular<00:12:03.209> currency<00:12:03.569> into<00:12:03.839> circulation<00:12:04.259> and 00:12:05.590 --> 00:12:05.600 align:start position:0% particular currency into circulation and 00:12:05.600 --> 00:12:09.499 align:start position:0% particular currency into circulation and you<00:12:06.600> know<00:12:06.889> this<00:12:07.889> is<00:12:08.100> quite<00:12:08.910> interesting 00:12:09.499 --> 00:12:09.509 align:start position:0% you know this is quite interesting 00:12:09.509 --> 00:12:12.470 align:start position:0% you know this is quite interesting because<00:12:09.769> following<00:12:10.769> a<00:12:11.069> couple<00:12:11.549> of<00:12:11.759> days<00:12:11.999> the 00:12:12.470 --> 00:12:12.480 align:start position:0% because following a couple of days the 00:12:12.480 --> 00:12:14.749 align:start position:0% because following a couple of days the media<00:12:12.839> started<00:12:13.259> to<00:12:13.379> digest<00:12:13.829> this<00:12:14.040> information 00:12:14.749 --> 00:12:14.759 align:start position:0% media started to digest this information 00:12:14.759 --> 00:12:18.559 align:start position:0% media started to digest this information and<00:12:15.019> started<00:12:16.019> calling<00:12:16.230> the<00:12:17.069> tokens<00:12:17.610> invented 00:12:18.559 --> 00:12:18.569 align:start position:0% and started calling the tokens invented 00:12:18.569 --> 00:12:22.579 align:start position:0% and started calling the tokens invented until<00:12:18.720> this<00:12:19.079> point<00:12:19.350> as<00:12:20.100> tokens<00:12:20.699> 1.0<00:12:21.329> and<00:12:21.660> you 00:12:22.579 --> 00:12:22.589 align:start position:0% until this point as tokens 1.0 and you 00:12:22.589 --> 00:12:23.929 align:start position:0% until this point as tokens 1.0 and you know<00:12:22.709> if<00:12:22.860> you<00:12:22.980> think<00:12:23.160> about<00:12:23.309> it<00:12:23.639> it's<00:12:23.790> pretty 00:12:23.929 --> 00:12:23.939 align:start position:0% know if you think about it it's pretty 00:12:23.939 --> 00:12:25.639 align:start position:0% know if you think about it it's pretty accurate<00:12:24.209> since<00:12:24.869> we<00:12:25.079> are<00:12:25.139> still<00:12:25.379> barely 00:12:25.639 --> 00:12:25.649 align:start position:0% accurate since we are still barely 00:12:25.649 --> 00:12:27.559 align:start position:0% accurate since we are still barely scratching<00:12:26.249> the<00:12:26.279> surface<00:12:26.549> of<00:12:26.970> what<00:12:27.209> can<00:12:27.419> be 00:12:27.559 --> 00:12:27.569 align:start position:0% scratching the surface of what can be 00:12:27.569 --> 00:12:29.509 align:start position:0% scratching the surface of what can be done<00:12:27.749> and<00:12:28.019> we're<00:12:28.829> still<00:12:29.129> trying<00:12:29.429> to 00:12:29.509 --> 00:12:29.519 align:start position:0% done and we're still trying to 00:12:29.519 --> 00:12:31.249 align:start position:0% done and we're still trying to understand<00:12:30.059> the<00:12:30.209> basic<00:12:30.360> pieces<00:12:30.989> of<00:12:31.139> the 00:12:31.249 --> 00:12:31.259 align:start position:0% understand the basic pieces of the 00:12:31.259 --> 00:12:34.460 align:start position:0% understand the basic pieces of the puzzle<00:12:31.709> that<00:12:31.949> make<00:12:32.910> a<00:12:32.939> good<00:12:33.269> token<00:12:33.989> work<00:12:34.199> and 00:12:34.460 --> 00:12:34.470 align:start position:0% puzzle that make a good token work and 00:12:34.470 --> 00:12:40.009 align:start position:0% puzzle that make a good token work and then<00:12:35.160> things<00:12:35.939> kept<00:12:36.329> snowballing<00:12:36.899> and<00:12:38.179> by<00:12:39.179> by 00:12:40.009 --> 00:12:40.019 align:start position:0% then things kept snowballing and by by 00:12:40.019 --> 00:12:42.199 align:start position:0% then things kept snowballing and by by the<00:12:40.079> end<00:12:40.319> of<00:12:40.439> the<00:12:40.619> day<00:12:40.769> we<00:12:40.949> had<00:12:41.129> like<00:12:41.369> this<00:12:41.910> sort 00:12:42.199 --> 00:12:42.209 align:start position:0% the end of the day we had like this sort 00:12:42.209 --> 00:12:42.619 align:start position:0% the end of the day we had like this sort of<00:12:42.329> stuff 00:12:42.619 --> 00:12:42.629 align:start position:0% of stuff 00:12:42.629 --> 00:12:44.210 align:start position:0% of stuff is<00:12:42.899> like<00:12:43.079> everything<00:12:43.470> you<00:12:43.739> need<00:12:43.919> to<00:12:44.069> know 00:12:44.210 --> 00:12:44.220 align:start position:0% is like everything you need to know 00:12:44.220 --> 00:12:51.259 align:start position:0% is like everything you need to know about<00:12:44.369> cryptocurrencies<00:12:47.869> so<00:12:49.790> you<00:12:50.790> know<00:12:50.910> 90% 00:12:51.259 --> 00:12:51.269 align:start position:0% about cryptocurrencies so you know 90% 00:12:51.269 --> 00:12:54.139 align:start position:0% about cryptocurrencies so you know 90% of<00:12:51.720> startups<00:12:52.290> in<00:12:52.439> general<00:12:52.860> fall<00:12:53.189> so<00:12:53.579> maybe<00:12:53.939> it 00:12:54.139 --> 00:12:54.149 align:start position:0% of startups in general fall so maybe it 00:12:54.149 --> 00:12:55.460 align:start position:0% of startups in general fall so maybe it would<00:12:54.329> have<00:12:54.419> been<00:12:54.600> more<00:12:54.749> accurate<00:12:54.809> to<00:12:55.290> say 00:12:55.460 --> 00:12:55.470 align:start position:0% would have been more accurate to say 00:12:55.470 --> 00:12:58.699 align:start position:0% would have been more accurate to say that<00:12:55.499> with<00:12:56.189> a<00:12:56.220> poorly<00:12:56.639> designed<00:12:56.910> token<00:12:57.589> 99%<00:12:58.589> of 00:12:58.699 --> 00:12:58.709 align:start position:0% that with a poorly designed token 99% of 00:12:58.709 --> 00:13:01.639 align:start position:0% that with a poorly designed token 99% of the<00:12:58.829> token<00:12:59.129> startups<00:12:59.579> will<00:12:59.730> fall<00:12:59.939> but<00:13:00.649> to 00:13:01.639 --> 00:13:01.649 align:start position:0% the token startups will fall but to 00:13:01.649 --> 00:13:04.579 align:start position:0% the token startups will fall but to focus<00:13:01.949> on<00:13:02.249> the<00:13:02.429> positive<00:13:02.999> the<00:13:03.720> question<00:13:04.470> of 00:13:04.579 --> 00:13:04.589 align:start position:0% focus on the positive the question of 00:13:04.589 --> 00:13:07.519 align:start position:0% focus on the positive the question of how<00:13:04.919> do<00:13:04.980> we<00:13:05.220> get<00:13:05.429> to<00:13:05.459> talk<00:13:05.730> in<00:13:05.910> 2.0<00:13:06.480> started<00:13:07.350> to 00:13:07.519 --> 00:13:07.529 align:start position:0% how do we get to talk in 2.0 started to 00:13:07.529 --> 00:13:08.659 align:start position:0% how do we get to talk in 2.0 started to take<00:13:08.369> shape 00:13:08.659 --> 00:13:08.669 align:start position:0% take shape 00:13:08.669 --> 00:13:12.949 align:start position:0% take shape and<00:13:09.290> since<00:13:10.290> Vitalik<00:13:10.799> thanks<00:13:11.490> started<00:13:12.240> this<00:13:12.389> I 00:13:12.949 --> 00:13:12.959 align:start position:0% and since Vitalik thanks started this I 00:13:12.959 --> 00:13:14.989 align:start position:0% and since Vitalik thanks started this I figure<00:13:13.529> that<00:13:13.679> it's<00:13:13.889> best<00:13:14.189> to<00:13:14.309> just<00:13:14.699> show<00:13:14.970> a 00:13:14.989 --> 00:13:14.999 align:start position:0% figure that it's best to just show a 00:13:14.999 --> 00:13:16.610 align:start position:0% figure that it's best to just show a short<00:13:15.419> video<00:13:15.660> of 00:13:16.610 --> 00:13:16.620 align:start position:0% short video of 00:13:16.620 --> 00:13:19.130 align:start position:0% short video of a<00:13:16.730> short<00:13:17.730> segment<00:13:17.880> of<00:13:18.240> a<00:13:18.330> recent<00:13:18.630> video<00:13:18.810> done 00:13:19.130 --> 00:13:19.140 align:start position:0% a short segment of a recent video done 00:13:19.140 --> 00:13:21.380 align:start position:0% a short segment of a recent video done by<00:13:20.180> VTEC 00:13:21.380 --> 00:13:21.390 align:start position:0% by VTEC 00:13:21.390 --> 00:13:23.390 align:start position:0% by VTEC so<00:13:21.600> without<00:13:21.870> further<00:13:22.050> ado<00:13:22.500> the<00:13:22.830> nice<00:13:23.190> thing 00:13:23.390 --> 00:13:23.400 align:start position:0% so without further ado the nice thing 00:13:23.400 --> 00:13:24.830 align:start position:0% so without further ado the nice thing about<00:13:23.460> cryptocurrency<00:13:24.030> I<00:13:24.270> think<00:13:24.540> is<00:13:24.630> that<00:13:24.660> it 00:13:24.830 --> 00:13:24.840 align:start position:0% about cryptocurrency I think is that it 00:13:24.840 --> 00:13:26.720 align:start position:0% about cryptocurrency I think is that it just<00:13:24.990> makes<00:13:25.170> it<00:13:25.290> so<00:13:25.590> bloody<00:13:25.890> easy<00:13:26.130> to<00:13:26.400> create 00:13:26.720 --> 00:13:26.730 align:start position:0% just makes it so bloody easy to create 00:13:26.730 --> 00:13:28.430 align:start position:0% just makes it so bloody easy to create one<00:13:26.910> of<00:13:26.940> these<00:13:27.090> economic<00:13:27.570> mechanisms<00:13:28.110> you 00:13:28.430 --> 00:13:28.440 align:start position:0% one of these economic mechanisms you 00:13:28.440 --> 00:13:30.320 align:start position:0% one of these economic mechanisms you just<00:13:28.680> write<00:13:28.890> it<00:13:29.010> up<00:13:29.100> in<00:13:29.220> code<00:13:29.490> then<00:13:30.030> it<00:13:30.060> just 00:13:30.320 --> 00:13:30.330 align:start position:0% just write it up in code then it just 00:13:30.330 --> 00:13:32.300 align:start position:0% just write it up in code then it just makes<00:13:30.510> it<00:13:30.600> really<00:13:30.750> easy<00:13:30.870> to<00:13:31.080> just<00:13:31.470> service<00:13:32.220> an 00:13:32.300 --> 00:13:32.310 align:start position:0% makes it really easy to just service an 00:13:32.310 --> 00:13:33.980 align:start position:0% makes it really easy to just service an economic<00:13:32.760> experimentation<00:13:33.510> ground<00:13:33.780> for 00:13:33.980 --> 00:13:33.990 align:start position:0% economic experimentation ground for 00:13:33.990 --> 00:13:37.340 align:start position:0% economic experimentation ground for doing<00:13:34.170> these<00:13:34.290> kinds<00:13:34.560> of<00:13:34.620> things<00:13:35.240> and<00:13:36.240> so<00:13:37.020> you 00:13:37.340 --> 00:13:37.350 align:start position:0% doing these kinds of things and so you 00:13:37.350 --> 00:13:39.860 align:start position:0% doing these kinds of things and so you know<00:13:38.100> that's<00:13:38.280> sort<00:13:38.520> of<00:13:38.580> the<00:13:39.060> whole<00:13:39.480> point<00:13:39.630> of 00:13:39.860 --> 00:13:39.870 align:start position:0% know that's sort of the whole point of 00:13:39.870 --> 00:13:41.450 align:start position:0% know that's sort of the whole point of economic<00:13:40.100> experimentation<00:13:41.100> is<00:13:41.190> sort<00:13:41.400> of 00:13:41.450 --> 00:13:41.460 align:start position:0% economic experimentation is sort of 00:13:41.460 --> 00:13:42.590 align:start position:0% economic experimentation is sort of coming<00:13:41.730> up<00:13:41.850> with<00:13:41.880> these<00:13:42.060> sort<00:13:42.240> of<00:13:42.300> clever 00:13:42.590 --> 00:13:42.600 align:start position:0% coming up with these sort of clever 00:13:42.600 --> 00:13:44.270 align:start position:0% coming up with these sort of clever clever<00:13:43.320> little<00:13:43.650> tricks<00:13:43.980> that<00:13:44.040> sort<00:13:44.220> of 00:13:44.270 --> 00:13:44.280 align:start position:0% clever little tricks that sort of 00:13:44.280 --> 00:13:46.720 align:start position:0% clever little tricks that sort of combine<00:13:44.640> together<00:13:45.000> incentives<00:13:45.600> and<00:13:45.780> sort<00:13:46.080> of 00:13:46.720 --> 00:13:46.730 align:start position:0% combine together incentives and sort of 00:13:46.730 --> 00:13:49.160 align:start position:0% combine together incentives and sort of put<00:13:47.730> some<00:13:48.150> little<00:13:48.390> put<00:13:48.570> things<00:13:48.720> together<00:13:48.870> in 00:13:49.160 --> 00:13:49.170 align:start position:0% put some little put things together in 00:13:49.170 --> 00:13:50.540 align:start position:0% put some little put things together in this<00:13:49.260> nice<00:13:49.470> way<00:13:49.740> that<00:13:49.770> gives<00:13:50.190> people<00:13:50.370> the 00:13:50.540 --> 00:13:50.550 align:start position:0% this nice way that gives people the 00:13:50.550 --> 00:13:54.290 align:start position:0% this nice way that gives people the incentive<00:13:51.510> to<00:13:51.540> do<00:13:51.690> the<00:13:51.810> right<00:13:51.960> thing<00:13:52.230> and<00:13:53.300> you 00:13:54.290 --> 00:13:54.300 align:start position:0% incentive to do the right thing and you 00:13:54.300 --> 00:13:55.760 align:start position:0% incentive to do the right thing and you know<00:13:54.390> the<00:13:54.540> skin<00:13:54.840> there's<00:13:55.380> probably<00:13:55.590> quite<00:13:55.680> a 00:13:55.760 --> 00:13:55.770 align:start position:0% know the skin there's probably quite a 00:13:55.770 --> 00:13:58.040 align:start position:0% know the skin there's probably quite a lot<00:13:55.950> to<00:13:56.070> be<00:13:56.160> done<00:13:56.340> it's<00:13:57.030> just<00:13:57.300> really<00:13:57.780> we're 00:13:58.040 --> 00:13:58.050 align:start position:0% lot to be done it's just really we're 00:13:58.050 --> 00:14:03.770 align:start position:0% lot to be done it's just really we're all<00:13:58.290> getting<00:13:58.500> started<00:14:01.730> I<00:14:02.730> like<00:14:03.090> to<00:14:03.240> focus<00:14:03.600> on 00:14:03.770 --> 00:14:03.780 align:start position:0% all getting started I like to focus on 00:14:03.780 --> 00:14:08.690 align:start position:0% all getting started I like to focus on that<00:14:05.390> right<00:14:06.390> it's<00:14:07.140> still<00:14:07.380> just<00:14:07.710> ear<00:14:08.040> -<00:14:08.340> after 00:14:08.690 --> 00:14:08.700 align:start position:0% that right it's still just ear - after 00:14:08.700 --> 00:14:13.180 align:start position:0% that right it's still just ear - after each<00:14:08.820> area<00:14:09.030> and<00:14:10.130> our<00:14:11.130> approach<00:14:11.970> this<00:14:12.420> thing<00:14:12.690> - 00:14:13.180 --> 00:14:13.190 align:start position:0% each area and our approach this thing - 00:14:13.190 --> 00:14:16.790 align:start position:0% each area and our approach this thing - maybe<00:14:14.330> answering<00:14:15.330> this<00:14:15.510> question<00:14:15.690> is<00:14:16.170> that 00:14:16.790 --> 00:14:16.800 align:start position:0% maybe answering this question is that 00:14:16.800 --> 00:14:19.910 align:start position:0% maybe answering this question is that just<00:14:17.580> as<00:14:17.760> a<00:14:18.120> theorem<00:14:18.570> had<00:14:19.170> during<00:14:19.770> its 00:14:19.910 --> 00:14:19.920 align:start position:0% just as a theorem had during its 00:14:19.920 --> 00:14:23.750 align:start position:0% just as a theorem had during its frontier<00:14:20.490> the<00:14:21.210> etherium<00:14:21.830> Olympics<00:14:22.830> where 00:14:23.750 --> 00:14:23.760 align:start position:0% frontier the etherium Olympics where 00:14:23.760 --> 00:14:25.970 align:start position:0% frontier the etherium Olympics where we're<00:14:24.510> developers<00:14:25.290> from<00:14:25.410> around<00:14:25.560> the<00:14:25.860> world 00:14:25.970 --> 00:14:25.980 align:start position:0% we're developers from around the world 00:14:25.980 --> 00:14:28.340 align:start position:0% we're developers from around the world were<00:14:26.220> invited<00:14:26.760> to<00:14:26.850> identify<00:14:27.480> bugs<00:14:27.780> attack 00:14:28.340 --> 00:14:28.350 align:start position:0% were invited to identify bugs attack 00:14:28.350 --> 00:14:30.740 align:start position:0% were invited to identify bugs attack vectors<00:14:28.860> and<00:14:29.070> basically<00:14:29.700> if<00:14:30.000> you<00:14:30.300> can<00:14:30.330> break 00:14:30.740 --> 00:14:30.750 align:start position:0% vectors and basically if you can break 00:14:30.750 --> 00:14:33.440 align:start position:0% vectors and basically if you can break it<00:14:30.990> go<00:14:31.380> ahead<00:14:31.650> and<00:14:31.890> we'll<00:14:32.460> learn<00:14:32.640> for<00:14:32.910> it<00:14:33.060> from 00:14:33.440 --> 00:14:33.450 align:start position:0% it go ahead and we'll learn for it from 00:14:33.450 --> 00:14:35.660 align:start position:0% it go ahead and we'll learn for it from it<00:14:33.600> will<00:14:33.870> become<00:14:34.200> stronger<00:14:34.560> we<00:14:35.340> invite 00:14:35.660 --> 00:14:35.670 align:start position:0% it will become stronger we invite 00:14:35.670 --> 00:14:38.660 align:start position:0% it will become stronger we invite everyone<00:14:36.200> here<00:14:37.200> and<00:14:37.440> that's<00:14:38.010> watching<00:14:38.550> the 00:14:38.660 --> 00:14:38.670 align:start position:0% everyone here and that's watching the 00:14:38.670 --> 00:14:41.990 align:start position:0% everyone here and that's watching the presentation<00:14:39.270> to<00:14:39.480> join<00:14:40.020> us<00:14:40.230> in<00:14:40.800> breaking<00:14:41.790> and 00:14:41.990 --> 00:14:42.000 align:start position:0% presentation to join us in breaking and 00:14:42.000 --> 00:14:44.300 align:start position:0% presentation to join us in breaking and reinventing<00:14:42.720> and<00:14:42.900> replaying<00:14:43.350> the<00:14:43.800> token 00:14:44.300 --> 00:14:44.310 align:start position:0% reinventing and replaying the token 00:14:44.310 --> 00:14:46.910 align:start position:0% reinventing and replaying the token proposal<00:14:44.850> and<00:14:45.140> basically<00:14:46.140> with<00:14:46.260> the<00:14:46.410> I<00:14:46.560> ETH 00:14:46.910 --> 00:14:46.920 align:start position:0% proposal and basically with the I ETH 00:14:46.920 --> 00:14:49.610 align:start position:0% proposal and basically with the I ETH proposal<00:14:47.460> and<00:14:47.580> what<00:14:47.700> we<00:14:47.900> showcase<00:14:48.900> today<00:14:49.140> we 00:14:49.610 --> 00:14:49.620 align:start position:0% proposal and what we showcase today we 00:14:49.620 --> 00:14:51.230 align:start position:0% proposal and what we showcase today we want<00:14:49.830> to<00:14:49.980> just<00:14:50.190> get<00:14:50.370> the<00:14:50.490> prototype<00:14:50.970> in<00:14:51.120> the 00:14:51.230 --> 00:14:51.240 align:start position:0% want to just get the prototype in the 00:14:51.240 --> 00:14:55.540 align:start position:0% want to just get the prototype in the world<00:14:51.450> and<00:14:51.870> then<00:14:52.760> in<00:14:53.760> a<00:14:53.790> sort<00:14:54.270> of<00:14:54.390> cyberpunk 00:14:55.540 --> 00:14:55.550 align:start position:0% world and then in a sort of cyberpunk 00:14:55.550 --> 00:14:59.180 align:start position:0% world and then in a sort of cyberpunk inception<00:14:56.550> like<00:14:57.680> fashion<00:14:58.680> to<00:14:58.830> iterate 00:14:59.180 --> 00:14:59.190 align:start position:0% inception like fashion to iterate 00:14:59.190 --> 00:15:02.090 align:start position:0% inception like fashion to iterate co-create<00:14:59.790> in<00:14:59.970> the<00:15:00.150> open<00:15:00.510> on<00:15:00.900> Akasha<00:15:01.560> itself 00:15:02.090 --> 00:15:02.100 align:start position:0% co-create in the open on Akasha itself 00:15:02.100 --> 00:15:06.170 align:start position:0% co-create in the open on Akasha itself so<00:15:02.880> we<00:15:03.810> will<00:15:03.960> use<00:15:04.140> tags<00:15:04.710> to<00:15:05.250> coordinate<00:15:06.000> and 00:15:06.170 --> 00:15:06.180 align:start position:0% so we will use tags to coordinate and 00:15:06.180 --> 00:15:08.090 align:start position:0% so we will use tags to coordinate and later<00:15:06.360> on<00:15:06.600> if<00:15:06.810> we<00:15:06.960> still<00:15:07.500> have<00:15:07.650> time<00:15:07.830> we<00:15:07.980> will 00:15:08.090 --> 00:15:08.100 align:start position:0% later on if we still have time we will 00:15:08.100 --> 00:15:10.520 align:start position:0% later on if we still have time we will show<00:15:08.190> you<00:15:08.370> an<00:15:08.760> actual<00:15:09.060> demo<00:15:09.330> of<00:15:09.540> how<00:15:09.570> this<00:15:09.900> this 00:15:10.520 --> 00:15:10.530 align:start position:0% show you an actual demo of how this this 00:15:10.530 --> 00:15:14.210 align:start position:0% show you an actual demo of how this this will<00:15:10.770> work<00:15:10.920> but<00:15:11.460> basically<00:15:11.940> what<00:15:12.660> we<00:15:12.840> want<00:15:13.220> or 00:15:14.210 --> 00:15:14.220 align:start position:0% will work but basically what we want or 00:15:14.220 --> 00:15:17.510 align:start position:0% will work but basically what we want or hope<00:15:14.550> is<00:15:15.030> that<00:15:15.510> if<00:15:16.500> we<00:15:16.710> approach<00:15:17.040> things<00:15:17.250> from 00:15:17.510 --> 00:15:17.520 align:start position:0% hope is that if we approach things from 00:15:17.520 --> 00:15:21.350 align:start position:0% hope is that if we approach things from this<00:15:17.670> perspective<00:15:18.080> maybe<00:15:19.790> people<00:15:20.790> and<00:15:21.030> and 00:15:21.350 --> 00:15:21.360 align:start position:0% this perspective maybe people and and 00:15:21.360 --> 00:15:24.290 align:start position:0% this perspective maybe people and and startups<00:15:22.230> can<00:15:22.440> think<00:15:22.740> of<00:15:22.920> of<00:15:23.460> tokens<00:15:23.940> as<00:15:24.120> this 00:15:24.290 --> 00:15:24.300 align:start position:0% startups can think of of tokens as this 00:15:24.300 --> 00:15:26.990 align:start position:0% startups can think of of tokens as this dynamic<00:15:24.900> adaptive<00:15:25.170> systems<00:15:25.920> which<00:15:26.220> involve 00:15:26.990 --> 00:15:27.000 align:start position:0% dynamic adaptive systems which involve 00:15:27.000 --> 00:15:29.190 align:start position:0% dynamic adaptive systems which involve multiple<00:15:27.660> pieces<00:15:28.200> that<00:15:28.530> you<00:15:28.680> have<00:15:28.710> to 00:15:29.190 --> 00:15:29.200 align:start position:0% multiple pieces that you have to 00:15:29.200 --> 00:15:32.820 align:start position:0% multiple pieces that you have to carefully<00:15:29.760> put<00:15:30.760> together<00:15:31.170> rather<00:15:32.170> than<00:15:32.320> a 00:15:32.820 --> 00:15:32.830 align:start position:0% carefully put together rather than a 00:15:32.830 --> 00:15:35.460 align:start position:0% carefully put together rather than a graph<00:15:33.130> going<00:15:33.430> from<00:15:33.790> zero<00:15:34.060> to<00:15:34.180> the<00:15:34.300> moon<00:15:34.600> right 00:15:35.460 --> 00:15:35.470 align:start position:0% graph going from zero to the moon right 00:15:35.470 --> 00:15:38.670 align:start position:0% graph going from zero to the moon right so<00:15:36.190> I<00:15:37.000> think<00:15:37.210> together<00:15:37.600> if<00:15:38.020> we<00:15:38.230> will<00:15:38.410> tackle 00:15:38.670 --> 00:15:38.680 align:start position:0% so I think together if we will tackle 00:15:38.680 --> 00:15:43.650 align:start position:0% so I think together if we will tackle this<00:15:38.980> this<00:15:39.940> question<00:15:40.740> we<00:15:41.740> might<00:15:42.240> reach<00:15:43.240> some 00:15:43.650 --> 00:15:43.660 align:start position:0% this this question we might reach some 00:15:43.660 --> 00:15:46.380 align:start position:0% this this question we might reach some emergent<00:15:44.170> shared<00:15:44.470> understanding<00:15:45.160> because<00:15:45.580> no 00:15:46.380 --> 00:15:46.390 align:start position:0% emergent shared understanding because no 00:15:46.390 --> 00:15:48.510 align:start position:0% emergent shared understanding because no one<00:15:46.540> has<00:15:46.750> like<00:15:46.960> the<00:15:47.140> full<00:15:47.410> idea<00:15:47.590> of<00:15:47.950> what<00:15:48.340> is 00:15:48.510 --> 00:15:48.520 align:start position:0% one has like the full idea of what is 00:15:48.520 --> 00:15:51.140 align:start position:0% one has like the full idea of what is talking<00:15:48.970> 2.0<00:15:49.420> but<00:15:50.020> a<00:15:50.080> thousand<00:15:50.770> little 00:15:51.140 --> 00:15:51.150 align:start position:0% talking 2.0 but a thousand little 00:15:51.150 --> 00:15:53.580 align:start position:0% talking 2.0 but a thousand little half-baked<00:15:52.150> ideas<00:15:52.690> can<00:15:52.960> come<00:15:53.170> together<00:15:53.320> in 00:15:53.580 --> 00:15:53.590 align:start position:0% half-baked ideas can come together in 00:15:53.590 --> 00:15:56.070 align:start position:0% half-baked ideas can come together in something<00:15:54.160> completely<00:15:54.700> new<00:15:55.270> and<00:15:55.480> the<00:15:55.870> cool 00:15:56.070 --> 00:15:56.080 align:start position:0% something completely new and the cool 00:15:56.080 --> 00:15:57.900 align:start position:0% something completely new and the cool thing<00:15:56.110> about<00:15:56.350> this<00:15:56.650> is<00:15:56.890> that<00:15:57.220> this<00:15:57.490> is<00:15:57.550> a<00:15:57.670> quote 00:15:57.900 --> 00:15:57.910 align:start position:0% thing about this is that this is a quote 00:15:57.910 --> 00:15:59.580 align:start position:0% thing about this is that this is a quote I<00:15:57.940> really<00:15:58.330> like<00:15:58.510> is<00:15:58.690> that<00:15:58.870> the<00:15:59.020> mind<00:15:59.290> once 00:15:59.580 --> 00:15:59.590 align:start position:0% I really like is that the mind once 00:15:59.590 --> 00:16:02.430 align:start position:0% I really like is that the mind once stretched<00:15:59.890> by<00:16:00.160> an<00:16:00.310> idea<00:16:00.760> never<00:16:01.510> return<00:16:02.080> to<00:16:02.290> its 00:16:02.430 --> 00:16:02.440 align:start position:0% stretched by an idea never return to its 00:16:02.440 --> 00:16:05.160 align:start position:0% stretched by an idea never return to its original<00:16:02.620> dimensions<00:16:03.250> and<00:16:03.910> if<00:16:04.150> you<00:16:04.270> want<00:16:04.480> an 00:16:05.160 --> 00:16:05.170 align:start position:0% original dimensions and if you want an 00:16:05.170 --> 00:16:08.790 align:start position:0% original dimensions and if you want an example<00:16:05.560> just<00:16:05.770> remember<00:16:06.490> that<00:16:07.090> in<00:16:07.470> 2014<00:16:08.470> a 00:16:08.790 --> 00:16:08.800 align:start position:0% example just remember that in 2014 a 00:16:08.800 --> 00:16:12.360 align:start position:0% example just remember that in 2014 a theorem<00:16:09.250> had<00:16:09.550> eater<00:16:10.510> presale<00:16:11.110> which<00:16:11.740> led<00:16:12.340> to 00:16:12.360 --> 00:16:12.370 align:start position:0% theorem had eater presale which led to 00:16:12.370 --> 00:16:14.100 align:start position:0% theorem had eater presale which led to around<00:16:13.000> eighteen<00:16:13.390> point<00:16:13.600> five<00:16:13.810> million 00:16:14.100 --> 00:16:14.110 align:start position:0% around eighteen point five million 00:16:14.110 --> 00:16:16.290 align:start position:0% around eighteen point five million dollars<00:16:14.530> being<00:16:14.770> raised<00:16:15.070> to<00:16:15.400> fund<00:16:15.730> the 00:16:16.290 --> 00:16:16.300 align:start position:0% dollars being raised to fund the 00:16:16.300 --> 00:16:18.360 align:start position:0% dollars being raised to fund the development<00:16:16.840> of<00:16:16.960> the<00:16:17.110> platform<00:16:17.650> and<00:16:17.950> it<00:16:18.160> was 00:16:18.360 --> 00:16:18.370 align:start position:0% development of the platform and it was 00:16:18.370 --> 00:16:20.880 align:start position:0% development of the platform and it was number<00:16:18.610> one<00:16:19.000> as<00:16:19.270> in<00:16:19.900> the<00:16:19.930> most<00:16:20.260> successful 00:16:20.880 --> 00:16:20.890 align:start position:0% number one as in the most successful 00:16:20.890 --> 00:16:22.500 align:start position:0% number one as in the most successful crowdfunding<00:16:21.160> campaign<00:16:21.850> in<00:16:22.000> the<00:16:22.120> history<00:16:22.270> of 00:16:22.500 --> 00:16:22.510 align:start position:0% crowdfunding campaign in the history of 00:16:22.510 --> 00:16:24.780 align:start position:0% crowdfunding campaign in the history of the<00:16:22.720> internet<00:16:23.110> and<00:16:23.350> now<00:16:24.010> a<00:16:24.280> couple<00:16:24.550> of<00:16:24.730> years 00:16:24.780 --> 00:16:24.790 align:start position:0% the internet and now a couple of years 00:16:24.790 --> 00:16:27.420 align:start position:0% the internet and now a couple of years later<00:16:25.240> over<00:16:25.630> three<00:16:26.410> billion<00:16:26.680> dollars<00:16:27.190> have 00:16:27.420 --> 00:16:27.430 align:start position:0% later over three billion dollars have 00:16:27.430 --> 00:16:29.670 align:start position:0% later over three billion dollars have been<00:16:27.460> raised<00:16:27.850> by<00:16:28.060> companies<00:16:28.570> using<00:16:28.840> icos<00:16:29.410> as<00:16:29.650> a 00:16:29.670 --> 00:16:29.680 align:start position:0% been raised by companies using icos as a 00:16:29.680 --> 00:16:32.040 align:start position:0% been raised by companies using icos as a form<00:16:30.010> of<00:16:30.130> raising<00:16:30.910> funds<00:16:31.120> for<00:16:31.240> their<00:16:31.540> projects 00:16:32.040 --> 00:16:32.050 align:start position:0% form of raising funds for their projects 00:16:32.050 --> 00:16:36.480 align:start position:0% form of raising funds for their projects so<00:16:32.530> just<00:16:33.070> one<00:16:33.220> idea<00:16:33.430> huge<00:16:34.210> impact<00:16:34.860> so<00:16:35.860> now<00:16:36.010> the 00:16:36.480 --> 00:16:36.490 align:start position:0% so just one idea huge impact so now the 00:16:36.490 --> 00:16:37.860 align:start position:0% so just one idea huge impact so now the big<00:16:36.640> picture<00:16:37.030> of<00:16:37.180> what<00:16:37.360> we're<00:16:37.510> trying<00:16:37.690> to 00:16:37.860 --> 00:16:37.870 align:start position:0% big picture of what we're trying to 00:16:37.870 --> 00:16:40.290 align:start position:0% big picture of what we're trying to accomplish<00:16:38.530> is<00:16:38.770> like<00:16:39.190> we're<00:16:39.730> not<00:16:39.880> trying<00:16:40.240> to 00:16:40.290 --> 00:16:40.300 align:start position:0% accomplish is like we're not trying to 00:16:40.300 --> 00:16:43.320 align:start position:0% accomplish is like we're not trying to compete<00:16:40.720> with<00:16:40.900> the<00:16:41.140> big<00:16:41.320> boys<00:16:41.350> I<00:16:41.770> mean<00:16:42.330> they 00:16:43.320 --> 00:16:43.330 align:start position:0% compete with the big boys I mean they 00:16:43.330 --> 00:16:45.600 align:start position:0% compete with the big boys I mean they have<00:16:43.540> billions<00:16:43.900> of<00:16:43.990> users<00:16:44.410> would<00:16:44.680> be<00:16:44.860> nice<00:16:45.040> but 00:16:45.600 --> 00:16:45.610 align:start position:0% have billions of users would be nice but 00:16:45.610 --> 00:16:48.300 align:start position:0% have billions of users would be nice but let's<00:16:45.970> get<00:16:46.150> real<00:16:46.440> we<00:16:47.440> want<00:16:47.680> to<00:16:47.830> have<00:16:47.980> a<00:16:48.010> real 00:16:48.300 --> 00:16:48.310 align:start position:0% let's get real we want to have a real 00:16:48.310 --> 00:16:50.550 align:start position:0% let's get real we want to have a real alternative<00:16:48.520> in<00:16:49.060> in<00:16:49.570> place<00:16:49.870> to<00:16:50.110> keep<00:16:50.260> them<00:16:50.410> in 00:16:50.550 --> 00:16:50.560 align:start position:0% alternative in in place to keep them in 00:16:50.560 --> 00:16:54.570 align:start position:0% alternative in in place to keep them in check<00:16:50.590> and<00:16:51.960> this<00:16:52.960> is<00:16:53.080> not<00:16:53.260> like<00:16:53.530> paper<00:16:54.340> or 00:16:54.570 --> 00:16:54.580 align:start position:0% check and this is not like paper or 00:16:54.580 --> 00:16:56.580 align:start position:0% check and this is not like paper or plastic<00:16:54.820> bag<00:16:55.330> choice<00:16:55.660> we<00:16:56.080> want<00:16:56.230> to<00:16:56.440> offer 00:16:56.580 --> 00:16:56.590 align:start position:0% plastic bag choice we want to offer 00:16:56.590 --> 00:16:58.320 align:start position:0% plastic bag choice we want to offer people<00:16:56.890> a<00:16:57.070> fundamentally<00:16:57.760> different<00:16:57.790> choice 00:16:58.320 --> 00:16:58.330 align:start position:0% people a fundamentally different choice 00:16:58.330 --> 00:17:01.380 align:start position:0% people a fundamentally different choice when<00:16:58.570> it<00:16:58.600> comes<00:16:58.720> to<00:16:59.170> each<00:16:59.700> person's<00:17:00.700> digital 00:17:01.380 --> 00:17:01.390 align:start position:0% when it comes to each person's digital 00:17:01.390 --> 00:17:03.390 align:start position:0% when it comes to each person's digital sovereignty<00:17:01.990> as<00:17:02.110> human<00:17:02.560> netizens 00:17:03.390 --> 00:17:03.400 align:start position:0% sovereignty as human netizens 00:17:03.400 --> 00:17:06.390 align:start position:0% sovereignty as human netizens and<00:17:03.600> I<00:17:04.600> think<00:17:04.990> we<00:17:05.050> can<00:17:05.199> all<00:17:05.320> agree<00:17:05.440> after<00:17:05.890> this 00:17:06.390 --> 00:17:06.400 align:start position:0% and I think we can all agree after this 00:17:06.400 --> 00:17:09.030 align:start position:0% and I think we can all agree after this beautiful<00:17:07.089> Def<00:17:07.600> Con<00:17:07.870> that<00:17:08.079> watching<00:17:08.860> history 00:17:09.030 --> 00:17:09.040 align:start position:0% beautiful Def Con that watching history 00:17:09.040 --> 00:17:12.000 align:start position:0% beautiful Def Con that watching history in<00:17:09.339> the<00:17:09.430> making<00:17:09.550> is<00:17:09.880> cool<00:17:10.150> but<00:17:11.079> we<00:17:11.560> think<00:17:11.770> that 00:17:12.000 --> 00:17:12.010 align:start position:0% in the making is cool but we think that 00:17:12.010 --> 00:17:13.620 align:start position:0% in the making is cool but we think that writing<00:17:12.280> the<00:17:12.430> future<00:17:12.640> ourself<00:17:13.209> is<00:17:13.390> even 00:17:13.620 --> 00:17:13.630 align:start position:0% writing the future ourself is even 00:17:13.630 --> 00:17:15.840 align:start position:0% writing the future ourself is even cooler<00:17:13.839> so<00:17:14.500> on<00:17:14.829> this<00:17:15.040> note<00:17:15.280> we<00:17:15.579> invite 00:17:15.840 --> 00:17:15.850 align:start position:0% cooler so on this note we invite 00:17:15.850 --> 00:17:18.420 align:start position:0% cooler so on this note we invite everyone<00:17:16.270> to<00:17:16.660> be<00:17:16.900> able<00:17:16.959> to<00:17:17.050> join<00:17:17.800> us<00:17:18.010> in 00:17:18.420 --> 00:17:18.430 align:start position:0% everyone to be able to join us in 00:17:18.430 --> 00:17:20.370 align:start position:0% everyone to be able to join us in building<00:17:19.000> together<00:17:19.120> in<00:17:19.480> this<00:17:19.660> decade<00:17:20.110> a 00:17:20.370 --> 00:17:20.380 align:start position:0% building together in this decade a 00:17:20.380 --> 00:17:23.130 align:start position:0% building together in this decade a pattern<00:17:21.010> ology<00:17:21.540> architecture<00:17:22.540> for<00:17:22.750> the<00:17:22.870> next 00:17:23.130 --> 00:17:23.140 align:start position:0% pattern ology architecture for the next 00:17:23.140 --> 00:17:26.819 align:start position:0% pattern ology architecture for the next century<00:17:23.350> and<00:17:24.839> we<00:17:25.839> actually<00:17:26.230> have<00:17:26.500> all<00:17:26.680> the 00:17:26.819 --> 00:17:26.829 align:start position:0% century and we actually have all the 00:17:26.829 --> 00:17:29.460 align:start position:0% century and we actually have all the tools<00:17:27.089> and<00:17:28.089> we<00:17:28.360> have<00:17:28.390> like<00:17:28.810> a<00:17:28.840> pretty<00:17:29.290> good 00:17:29.460 --> 00:17:29.470 align:start position:0% tools and we have like a pretty good 00:17:29.470 --> 00:17:32.250 align:start position:0% tools and we have like a pretty good idea<00:17:29.770> of<00:17:29.830> where<00:17:30.100> things<00:17:30.400> can<00:17:30.580> go<00:17:30.820> and<00:17:31.260> the 00:17:32.250 --> 00:17:32.260 align:start position:0% idea of where things can go and the 00:17:32.260 --> 00:17:33.690 align:start position:0% idea of where things can go and the future<00:17:32.500> is<00:17:32.650> not<00:17:32.770> the<00:17:32.950> place<00:17:33.130> we<00:17:33.310> get<00:17:33.460> to<00:17:33.550> visit 00:17:33.690 --> 00:17:33.700 align:start position:0% future is not the place we get to visit 00:17:33.700 --> 00:17:36.000 align:start position:0% future is not the place we get to visit the<00:17:34.450> future<00:17:34.780> is<00:17:34.960> a<00:17:34.990> place<00:17:35.260> we<00:17:35.410> get<00:17:35.560> to<00:17:35.710> create 00:17:36.000 --> 00:17:36.010 align:start position:0% the future is a place we get to create 00:17:36.010 --> 00:17:38.430 align:start position:0% the future is a place we get to create and<00:17:36.310> I<00:17:37.150> would<00:17:37.330> like<00:17:37.540> to<00:17:37.570> announce<00:17:38.050> that<00:17:38.260> the 00:17:38.430 --> 00:17:38.440 align:start position:0% and I would like to announce that the 00:17:38.440 --> 00:17:41.100 align:start position:0% and I would like to announce that the beta<00:17:38.770> signups<00:17:39.100> are<00:17:39.430> open<00:17:39.850> for<00:17:40.510> everyone<00:17:40.930> that 00:17:41.100 --> 00:17:41.110 align:start position:0% beta signups are open for everyone that 00:17:41.110 --> 00:17:42.070 align:start position:0% beta signups are open for everyone that wants<00:17:41.260> to<00:17:41.470> part 00:17:42.070 --> 00:17:42.080 align:start position:0% wants to part 00:17:42.080 --> 00:17:45.070 align:start position:0% wants to part paid<00:17:42.380> and<00:17:42.679> subscribe<00:17:43.549> just<00:17:44.149> go<00:17:44.390> to<00:17:44.450> Akasha<00:17:44.840> dot 00:17:45.070 --> 00:17:45.080 align:start position:0% paid and subscribe just go to Akasha dot 00:17:45.080 --> 00:17:45.490 align:start position:0% paid and subscribe just go to Akasha dot world 00:17:45.490 --> 00:17:45.500 align:start position:0% world 00:17:45.500 --> 00:17:48.009 align:start position:0% world insert<00:17:45.919> your<00:17:46.039> email<00:17:46.220> in<00:17:46.610> and<00:17:47.419> in<00:17:47.659> a<00:17:47.750> matter<00:17:47.929> of 00:17:48.009 --> 00:17:48.019 align:start position:0% insert your email in and in a matter of 00:17:48.019 --> 00:17:50.289 align:start position:0% insert your email in and in a matter of weeks<00:17:48.320> we<00:17:48.620> will<00:17:48.740> send<00:17:48.980> you<00:17:49.130> the<00:17:49.250> invite<00:17:49.580> and<00:17:49.850> we 00:17:50.289 --> 00:17:50.299 align:start position:0% weeks we will send you the invite and we 00:17:50.299 --> 00:17:52.630 align:start position:0% weeks we will send you the invite and we will<00:17:50.510> start<00:17:50.779> released<00:17:51.080> the<00:17:51.559> beta<00:17:51.740> and<00:17:52.309> since<00:17:52.549> I 00:17:52.630 --> 00:17:52.640 align:start position:0% will start released the beta and since I 00:17:52.640 --> 00:17:54.399 align:start position:0% will start released the beta and since I see<00:17:52.850> we<00:17:52.970> still<00:17:53.149> have<00:17:53.240> two<00:17:53.570> minutes<00:17:53.870> I<00:17:54.049> will<00:17:54.200> now 00:17:54.399 --> 00:17:54.409 align:start position:0% see we still have two minutes I will now 00:17:54.409 --> 00:17:56.320 align:start position:0% see we still have two minutes I will now show<00:17:54.710> you<00:17:54.740> a<00:17:54.890> demo<00:17:55.159> of<00:17:55.279> what<00:17:55.580> the<00:17:55.730> data<00:17:55.909> looks 00:17:56.320 --> 00:17:56.330 align:start position:0% show you a demo of what the data looks 00:17:56.330 --> 00:17:58.659 align:start position:0% show you a demo of what the data looks like<00:17:56.419> and<00:17:56.750> this<00:17:57.470> is<00:17:57.620> basically<00:17:57.799> the<00:17:58.070> dashboard 00:17:58.659 --> 00:17:58.669 align:start position:0% like and this is basically the dashboard 00:17:58.669 --> 00:18:00.789 align:start position:0% like and this is basically the dashboard view<00:17:58.850> in<00:17:59.779> which<00:17:59.960> we<00:18:00.140> have<00:18:00.350> like<00:18:00.559> different 00:18:00.789 --> 00:18:00.799 align:start position:0% view in which we have like different 00:18:00.799 --> 00:18:03.669 align:start position:0% view in which we have like different streams<00:18:01.490> and<00:18:01.809> different<00:18:02.809> columns<00:18:03.230> which<00:18:03.470> can 00:18:03.669 --> 00:18:03.679 align:start position:0% streams and different columns which can 00:18:03.679 --> 00:18:05.919 align:start position:0% streams and different columns which can be<00:18:03.799> customized<00:18:04.309> by<00:18:04.460> the<00:18:04.519> users<00:18:04.940> and<00:18:05.149> here<00:18:05.779> we 00:18:05.919 --> 00:18:05.929 align:start position:0% be customized by the users and here we 00:18:05.929 --> 00:18:08.950 align:start position:0% be customized by the users and here we had<00:18:06.080> a<00:18:06.110> column<00:18:07.010> which<00:18:07.159> is<00:18:07.309> a<00:18:07.340> tag<00:18:07.700> and<00:18:08.000> in<00:18:08.779> this 00:18:08.950 --> 00:18:08.960 align:start position:0% had a column which is a tag and in this 00:18:08.960 --> 00:18:10.899 align:start position:0% had a column which is a tag and in this case<00:18:09.140> is<00:18:09.320> crypto<00:18:09.679> Olympics<00:18:10.190> so<00:18:10.370> people<00:18:10.730> can 00:18:10.899 --> 00:18:10.909 align:start position:0% case is crypto Olympics so people can 00:18:10.909 --> 00:18:13.600 align:start position:0% case is crypto Olympics so people can coordinate<00:18:11.240> on<00:18:11.779> the<00:18:12.049> ideas<00:18:12.529> brainstorm<00:18:13.279> these 00:18:13.600 --> 00:18:13.610 align:start position:0% coordinate on the ideas brainstorm these 00:18:13.610 --> 00:18:16.330 align:start position:0% coordinate on the ideas brainstorm these are<00:18:13.760> proposals<00:18:14.210> they<00:18:15.110> can<00:18:15.350> use<00:18:15.559> the<00:18:15.830> entries 00:18:16.330 --> 00:18:16.340 align:start position:0% are proposals they can use the entries 00:18:16.340 --> 00:18:17.549 align:start position:0% are proposals they can use the entries and<00:18:16.519> the<00:18:16.610> comment<00:18:17.029> section<00:18:17.360> as 00:18:17.549 --> 00:18:17.559 align:start position:0% and the comment section as 00:18:17.559 --> 00:18:21.539 align:start position:0% and the comment section as counterproposals<00:18:18.559> or<00:18:18.769> to<00:18:18.950> discuss<00:18:19.340> various 00:18:21.539 --> 00:18:21.549 align:start position:0% counterproposals or to discuss various 00:18:21.549 --> 00:18:24.370 align:start position:0% counterproposals or to discuss various ideas<00:18:22.549> and<00:18:23.000> this<00:18:23.179> is<00:18:23.299> like<00:18:23.450> an<00:18:23.630> example<00:18:24.019> in 00:18:24.370 --> 00:18:24.380 align:start position:0% ideas and this is like an example in 00:18:24.380 --> 00:18:27.490 align:start position:0% ideas and this is like an example in which<00:18:24.590> is<00:18:24.830> all<00:18:25.070> a<00:18:25.100> con<00:18:25.639> or<00:18:25.789> a<00:18:25.820> Def<00:18:26.149> Con<00:18:26.500> how 00:18:27.490 --> 00:18:27.500 align:start position:0% which is all a con or a Def Con how 00:18:27.500 --> 00:18:30.279 align:start position:0% which is all a con or a Def Con how it<00:18:27.679> works<00:18:27.919> to<00:18:28.070> publish<00:18:28.460> a<00:18:29.000> comment<00:18:29.539> as<00:18:29.929> you<00:18:30.080> can 00:18:30.279 --> 00:18:30.289 align:start position:0% it works to publish a comment as you can 00:18:30.289 --> 00:18:34.210 align:start position:0% it works to publish a comment as you can see<00:18:30.529> the<00:18:31.130> UI<00:18:31.309> has<00:18:32.200> changed<00:18:33.200> quite<00:18:33.350> a<00:18:33.409> bit<00:18:33.559> also 00:18:34.210 --> 00:18:34.220 align:start position:0% see the UI has changed quite a bit also 00:18:34.220 --> 00:18:37.240 align:start position:0% see the UI has changed quite a bit also in<00:18:34.580> the<00:18:34.730> backend<00:18:34.940> we<00:18:35.620> basically<00:18:36.620> are<00:18:36.860> now 00:18:37.240 --> 00:18:37.250 align:start position:0% in the backend we basically are now 00:18:37.250 --> 00:18:40.049 align:start position:0% in the backend we basically are now looking<00:18:38.090> at<00:18:38.539> a<00:18:38.600> completely<00:18:39.289> rewritten 00:18:40.049 --> 00:18:40.059 align:start position:0% looking at a completely rewritten 00:18:40.059 --> 00:18:42.820 align:start position:0% looking at a completely rewritten decentralized<00:18:41.059> application<00:18:41.659> from<00:18:41.899> dub<00:18:42.139> so<00:18:42.409> it 00:18:42.820 --> 00:18:42.830 align:start position:0% decentralized application from dub so it 00:18:42.830 --> 00:18:45.519 align:start position:0% decentralized application from dub so it would<00:18:43.100> be<00:18:43.250> more<00:18:43.399> correct<00:18:43.730> to<00:18:43.940> call<00:18:44.120> it<00:18:44.529> like 00:18:45.519 --> 00:18:45.529 align:start position:0% would be more correct to call it like 00:18:45.529 --> 00:18:48.190 align:start position:0% would be more correct to call it like version<00:18:46.309> 2<00:18:46.519> but<00:18:47.179> since<00:18:47.480> we<00:18:47.600> started<00:18:47.960> with<00:18:48.080> the 00:18:48.190 --> 00:18:48.200 align:start position:0% version 2 but since we started with the 00:18:48.200 --> 00:18:52.000 align:start position:0% version 2 but since we started with the Alpha<00:18:48.559> we<00:18:48.740> will<00:18:49.610> name<00:18:50.120> it<00:18:50.149> better<00:18:50.840> and<00:18:51.139> here<00:18:51.860> on 00:18:52.000 --> 00:18:52.010 align:start position:0% Alpha we will name it better and here on 00:18:52.010 --> 00:18:53.470 align:start position:0% Alpha we will name it better and here on the<00:18:52.130> left<00:18:52.309> side<00:18:52.490> these<00:18:52.850> are<00:18:52.909> what<00:18:53.330> we<00:18:53.450> call 00:18:53.470 --> 00:18:53.480 align:start position:0% the left side these are what we call 00:18:53.480 --> 00:18:56.049 align:start position:0% the left side these are what we call boards<00:18:54.110> for<00:18:54.289> now<00:18:54.440> and<00:18:54.710> basically<00:18:55.100> offers<00:18:55.820> like 00:18:56.049 --> 00:18:56.059 align:start position:0% boards for now and basically offers like 00:18:56.059 --> 00:18:58.330 align:start position:0% boards for now and basically offers like different<00:18:56.570> windows<00:18:57.019> into<00:18:57.409> specific<00:18:57.889> topics 00:18:58.330 --> 00:18:58.340 align:start position:0% different windows into specific topics 00:18:58.340 --> 00:19:00.909 align:start position:0% different windows into specific topics so<00:18:58.549> if<00:18:58.760> we<00:18:59.090> take<00:18:59.269> the<00:18:59.419> example<00:18:59.809> of<00:18:59.840> Def<00:19:00.080> Con<00:19:00.380> one 00:19:00.909 --> 00:19:00.919 align:start position:0% so if we take the example of Def Con one 00:19:00.919 --> 00:19:02.830 align:start position:0% so if we take the example of Def Con one of<00:19:01.039> the<00:19:01.159> car<00:19:01.370> of<00:19:01.580> the<00:19:02.059> boards<00:19:02.389> could<00:19:02.510> have<00:19:02.630> been 00:19:02.830 --> 00:19:02.840 align:start position:0% of the car of the boards could have been 00:19:02.840 --> 00:19:06.310 align:start position:0% of the car of the boards could have been like<00:19:02.990> events<00:19:03.850> presentations<00:19:04.850> workshops<00:19:05.450> and 00:19:06.310 --> 00:19:06.320 align:start position:0% like events presentations workshops and 00:19:06.320 --> 00:19:07.810 align:start position:0% like events presentations workshops and people<00:19:06.649> could<00:19:06.830> have<00:19:06.950> coordinated<00:19:07.190> better 00:19:07.810 --> 00:19:07.820 align:start position:0% people could have coordinated better 00:19:07.820 --> 00:19:11.379 align:start position:0% people could have coordinated better rather<00:19:08.120> than<00:19:08.269> checking<00:19:09.110> on<00:19:09.260> ready<00:19:09.700> 10<00:19:10.700> discord 00:19:11.379 --> 00:19:11.389 align:start position:0% rather than checking on ready 10 discord 00:19:11.389 --> 00:19:15.190 align:start position:0% rather than checking on ready 10 discord rooms<00:19:11.690> one<00:19:12.409> slack<00:19:12.919> you<00:19:13.700> get<00:19:13.880> idea<00:19:14.240> to<00:19:14.539> jeeter's 00:19:15.190 --> 00:19:15.200 align:start position:0% rooms one slack you get idea to jeeter's 00:19:15.200 --> 00:19:18.430 align:start position:0% rooms one slack you get idea to jeeter's and<00:19:15.500> and<00:19:15.710> so<00:19:15.950> on<00:19:16.070> so<00:19:16.639> I<00:19:17.000> would<00:19:17.929> like<00:19:18.019> to<00:19:18.230> thank 00:19:18.430 --> 00:19:18.440 align:start position:0% and and so on so I would like to thank 00:19:18.440 --> 00:19:22.330 align:start position:0% and and so on so I would like to thank you<00:19:18.620> all<00:19:18.649> for<00:19:18.799> your<00:19:19.039> attention<00:19:19.490> and<00:19:21.340> it's 00:19:22.330 --> 00:19:22.340 align:start position:0% you all for your attention and it's 00:19:22.340 --> 00:19:24.940 align:start position:0% you all for your attention and it's great<00:19:23.059> being<00:19:23.269> here<00:19:23.659> hope<00:19:24.409> to<00:19:24.620> see<00:19:24.799> you<00:19:24.860> on 00:19:24.940 --> 00:19:24.950 align:start position:0% great being here hope to see you on 00:19:24.950 --> 00:19:26.870 align:start position:0% great being here hope to see you on arkasha<00:19:25.250> soon 00:19:26.870 --> 00:19:26.880 align:start position:0% arkasha soon 00:19:26.880 --> 00:19:32.500 align:start position:0% arkasha soon [Applause] 00:19:32.500 --> 00:19:32.510 align:start position:0% [Applause] 00:19:32.510 --> 00:19:39.890 align:start position:0% [Applause] [Music]