WEBVTT Kind: captions Language: en 00:00:05.170 --> 00:00:08.290 align:start position:0% everyone<00:00:06.430> thank<00:00:07.430> you<00:00:07.550> for<00:00:07.609> coming 00:00:08.290 --> 00:00:08.300 align:start position:0% everyone thank you for coming 00:00:08.300 --> 00:00:13.449 align:start position:0% everyone thank you for coming my<00:00:08.870> name<00:00:09.020> is<00:00:09.139> Alex<00:00:09.950> I<00:00:09.980> work<00:00:10.430> in<00:00:10.639> smart<00:00:11.150> egg<00:00:12.459> hi 00:00:13.449 --> 00:00:13.459 align:start position:0% my name is Alex I work in smart egg hi 00:00:13.459 --> 00:00:17.350 align:start position:0% my name is Alex I work in smart egg hi and<00:00:13.699> today<00:00:14.480> I<00:00:14.750> will<00:00:14.930> tell<00:00:15.619> about<00:00:16.070> one<00:00:16.940> of<00:00:16.970> our 00:00:17.350 --> 00:00:17.360 align:start position:0% and today I will tell about one of our 00:00:17.360 --> 00:00:20.950 align:start position:0% and today I will tell about one of our creations<00:00:18.020> ear<00:00:18.380> seed<00:00:18.650> magnet<00:00:18.980> SEO<00:00:19.430> and<00:00:19.670> how<00:00:19.960> it 00:00:20.950 --> 00:00:20.960 align:start position:0% creations ear seed magnet SEO and how it 00:00:20.960 --> 00:00:23.380 align:start position:0% creations ear seed magnet SEO and how it helps<00:00:21.380> in<00:00:21.920> achieving<00:00:22.280> the<00:00:22.910> decentralized 00:00:23.380 --> 00:00:23.390 align:start position:0% helps in achieving the decentralized 00:00:23.390 --> 00:00:27.790 align:start position:0% helps in achieving the decentralized security<00:00:25.750> to<00:00:26.750> start<00:00:26.990> with<00:00:27.200> a<00:00:27.230> couple<00:00:27.560> of<00:00:27.590> words 00:00:27.790 --> 00:00:27.800 align:start position:0% security to start with a couple of words 00:00:27.800 --> 00:00:30.460 align:start position:0% security to start with a couple of words about<00:00:27.980> smart<00:00:28.430> egg<00:00:28.670> so<00:00:29.570> we've<00:00:29.780> been<00:00:29.900> working<00:00:30.080> in 00:00:30.460 --> 00:00:30.470 align:start position:0% about smart egg so we've been working in 00:00:30.470 --> 00:00:31.990 align:start position:0% about smart egg so we've been working in the<00:00:30.560> area<00:00:30.830> of<00:00:30.860> application<00:00:31.340> security<00:00:31.520> for 00:00:31.990 --> 00:00:32.000 align:start position:0% the area of application security for 00:00:32.000 --> 00:00:35.020 align:start position:0% the area of application security for maybe<00:00:32.689> 10<00:00:32.989> years<00:00:33.260> now<00:00:33.440> and<00:00:33.649> the<00:00:34.250> five<00:00:34.460> years<00:00:34.789> of 00:00:35.020 --> 00:00:35.030 align:start position:0% maybe 10 years now and the five years of 00:00:35.030 --> 00:00:37.780 align:start position:0% maybe 10 years now and the five years of those<00:00:35.539> we<00:00:35.840> are<00:00:36.170> creating<00:00:36.860> application 00:00:37.780 --> 00:00:37.790 align:start position:0% those we are creating application 00:00:37.790 --> 00:00:39.970 align:start position:0% those we are creating application security<00:00:38.060> tools<00:00:38.450> both<00:00:38.840> for<00:00:39.140> small<00:00:39.470> businesses 00:00:39.970 --> 00:00:39.980 align:start position:0% security tools both for small businesses 00:00:39.980 --> 00:00:43.000 align:start position:0% security tools both for small businesses and<00:00:40.310> big<00:00:40.579> enterprise<00:00:41.120> businesses<00:00:41.660> and<00:00:41.920> in<00:00:42.920> the 00:00:43.000 --> 00:00:43.010 align:start position:0% and big enterprise businesses and in the 00:00:43.010 --> 00:00:46.000 align:start position:0% and big enterprise businesses and in the area<00:00:43.310> of<00:00:43.340> blockchain<00:00:43.910> security<00:00:44.440> we<00:00:45.440> perform 00:00:46.000 --> 00:00:46.010 align:start position:0% area of blockchain security we perform 00:00:46.010 --> 00:00:49.630 align:start position:0% area of blockchain security we perform more<00:00:46.340> than<00:00:46.399> 200<00:00:47.329> blockchain<00:00:47.780> audits<00:00:48.320> and<00:00:48.640> of 00:00:49.630 --> 00:00:49.640 align:start position:0% more than 200 blockchain audits and of 00:00:49.640 --> 00:00:52.450 align:start position:0% more than 200 blockchain audits and of course<00:00:49.940> we<00:00:50.210> create<00:00:50.630> a<00:00:51.110> number<00:00:51.829> of<00:00:52.010> smart 00:00:52.450 --> 00:00:52.460 align:start position:0% course we create a number of smart 00:00:52.460 --> 00:00:55.959 align:start position:0% course we create a number of smart contract<00:00:53.000> security<00:00:53.450> tools<00:00:53.660> and<00:00:54.820> during<00:00:55.820> our 00:00:55.959 --> 00:00:55.969 align:start position:0% contract security tools and during our 00:00:55.969 --> 00:01:00.729 align:start position:0% contract security tools and during our work<00:00:56.300> in<00:00:57.460> blockchain<00:00:58.600> we<00:00:59.600> encountered<00:01:00.290> the 00:01:00.729 --> 00:01:00.739 align:start position:0% work in blockchain we encountered the 00:01:00.739 --> 00:01:04.209 align:start position:0% work in blockchain we encountered the following<00:01:01.010> problem<00:01:02.350> many<00:01:03.350> blockchain 00:01:04.209 --> 00:01:04.219 align:start position:0% following problem many blockchain 00:01:04.219 --> 00:01:06.819 align:start position:0% following problem many blockchain projects<00:01:04.699> like<00:01:05.030> some<00:01:05.360> gaps<00:01:05.659> or<00:01:06.049> exchanges 00:01:06.819 --> 00:01:06.829 align:start position:0% projects like some gaps or exchanges 00:01:06.829 --> 00:01:10.660 align:start position:0% projects like some gaps or exchanges deal<00:01:07.460> with<00:01:08.090> tokens<00:01:08.630> and<00:01:09.369> most<00:01:10.369> of<00:01:10.549> those 00:01:10.660 --> 00:01:10.670 align:start position:0% deal with tokens and most of those 00:01:10.670 --> 00:01:12.999 align:start position:0% deal with tokens and most of those tokens<00:01:10.939> are<00:01:11.270> meant<00:01:11.630> to<00:01:11.929> be<00:01:12.200> easy<00:01:12.439> to<00:01:12.799> any 00:01:12.999 --> 00:01:13.009 align:start position:0% tokens are meant to be easy to any 00:01:13.009 --> 00:01:16.029 align:start position:0% tokens are meant to be easy to any compliant<00:01:13.609> but<00:01:14.240> the<00:01:14.389> sad<00:01:14.659> truth<00:01:14.959> is<00:01:15.200> that<00:01:15.560> most 00:01:16.029 --> 00:01:16.039 align:start position:0% compliant but the sad truth is that most 00:01:16.039 --> 00:01:20.789 align:start position:0% compliant but the sad truth is that most of<00:01:16.280> them<00:01:16.429> are<00:01:16.579> not<00:01:18.549> currently<00:01:19.549> if<00:01:19.789> you<00:01:19.999> run 00:01:20.789 --> 00:01:20.799 align:start position:0% of them are not currently if you run 00:01:20.799 --> 00:01:25.269 align:start position:0% of them are not currently if you run some<00:01:21.799> some<00:01:22.729> of<00:01:22.819> such<00:01:23.060> projects<00:01:23.950> for<00:01:24.950> you<00:01:25.039> there 00:01:25.269 --> 00:01:25.279 align:start position:0% some some of such projects for you there 00:01:25.279 --> 00:01:27.489 align:start position:0% some some of such projects for you there are<00:01:25.369> only<00:01:25.399> two<00:01:25.850> approaches<00:01:26.420> to<00:01:26.450> ensure<00:01:26.840> the 00:01:27.489 --> 00:01:27.499 align:start position:0% are only two approaches to ensure the 00:01:27.499 --> 00:01:29.169 align:start position:0% are only two approaches to ensure the intercept<00:01:27.979> we<00:01:28.100> need<00:01:28.279> compatibility 00:01:29.169 --> 00:01:29.179 align:start position:0% intercept we need compatibility 00:01:29.179 --> 00:01:31.779 align:start position:0% intercept we need compatibility it's<00:01:29.689> either<00:01:30.049> or<00:01:30.409> during<00:01:30.649> third<00:01:31.310> party<00:01:31.639> code 00:01:31.779 --> 00:01:31.789 align:start position:0% it's either or during third party code 00:01:31.789 --> 00:01:35.459 align:start position:0% it's either or during third party code audit<00:01:32.270> or<00:01:32.450> writing<00:01:33.139> a<00:01:33.289> bunch<00:01:33.560> of<00:01:33.740> tests<00:01:34.159> so 00:01:35.459 --> 00:01:35.469 align:start position:0% audit or writing a bunch of tests so 00:01:35.469 --> 00:01:38.769 align:start position:0% audit or writing a bunch of tests so both<00:01:36.469> of<00:01:36.679> these<00:01:37.159> approaches<00:01:37.700> take<00:01:38.240> long<00:01:38.509> time 00:01:38.769 --> 00:01:38.779 align:start position:0% both of these approaches take long time 00:01:38.779 --> 00:01:41.260 align:start position:0% both of these approaches take long time they<00:01:39.200> are<00:01:39.380> expensive<00:01:40.159> they<00:01:40.639> need<00:01:40.880> certain 00:01:41.260 --> 00:01:41.270 align:start position:0% they are expensive they need certain 00:01:41.270 --> 00:01:43.510 align:start position:0% they are expensive they need certain degree<00:01:41.509> of<00:01:41.689> trust<00:01:42.049> and<00:01:42.380> of<00:01:42.950> course<00:01:43.279> they<00:01:43.490> are 00:01:43.510 --> 00:01:43.520 align:start position:0% degree of trust and of course they are 00:01:43.520 --> 00:01:49.469 align:start position:0% degree of trust and of course they are not<00:01:43.849> scalable<00:01:46.719> so<00:01:47.719> according<00:01:48.439> to<00:01:48.469> our<00:01:48.590> region 00:01:49.469 --> 00:01:49.479 align:start position:0% not scalable so according to our region 00:01:49.479 --> 00:01:54.099 align:start position:0% not scalable so according to our region if<00:01:50.479> you<00:01:51.049> work<00:01:51.649> in<00:01:51.979> a<00:01:52.340> project<00:01:52.639> that<00:01:53.270> deals<00:01:53.899> with 00:01:54.099 --> 00:01:54.109 align:start position:0% if you work in a project that deals with 00:01:54.109 --> 00:01:57.789 align:start position:0% if you work in a project that deals with any<00:01:55.179> counterparty<00:01:56.179> interfaces<00:01:56.929> that<00:01:57.439> need<00:01:57.619> to 00:01:57.789 --> 00:01:57.799 align:start position:0% any counterparty interfaces that need to 00:01:57.799 --> 00:02:01.239 align:start position:0% any counterparty interfaces that need to comply<00:01:58.189> to<00:01:58.219> some<00:01:58.729> requirements<00:01:59.539> you<00:02:00.529> need<00:02:01.189> to 00:02:01.239 --> 00:02:01.249 align:start position:0% comply to some requirements you need to 00:02:01.249 --> 00:02:04.029 align:start position:0% comply to some requirements you need to have<00:02:02.179> a<00:02:02.209> way<00:02:02.450> to<00:02:02.479> check<00:02:03.020> these<00:02:03.259> compliance<00:02:03.649> in 00:02:04.029 --> 00:02:04.039 align:start position:0% have a way to check these compliance in 00:02:04.039 --> 00:02:07.479 align:start position:0% have a way to check these compliance in a<00:02:04.189> decentralized<00:02:04.819> way<00:02:05.529> so<00:02:06.529> as<00:02:06.799> a<00:02:06.859> first<00:02:07.159> step 00:02:07.479 --> 00:02:07.489 align:start position:0% a decentralized way so as a first step 00:02:07.489 --> 00:02:11.979 align:start position:0% a decentralized way so as a first step in<00:02:08.090> achieving<00:02:08.500> this<00:02:09.500> vision<00:02:09.860> we<00:02:10.849> created<00:02:11.420> the 00:02:11.979 --> 00:02:11.989 align:start position:0% in achieving this vision we created the 00:02:11.989 --> 00:02:13.870 align:start position:0% in achieving this vision we created the tool<00:02:12.170> that<00:02:12.590> we<00:02:12.710> named<00:02:12.920> either<00:02:13.190> C<00:02:13.340> 20<00:02:13.670> test 00:02:13.870 --> 00:02:13.880 align:start position:0% tool that we named either C 20 test 00:02:13.880 --> 00:02:16.780 align:start position:0% tool that we named either C 20 test shield<00:02:14.270> basically<00:02:14.960> it's<00:02:15.170> adapt<00:02:15.500> it<00:02:16.250> runs 00:02:16.780 --> 00:02:16.790 align:start position:0% shield basically it's adapt it runs 00:02:16.790 --> 00:02:17.880 align:start position:0% shield basically it's adapt it runs tests<00:02:17.480> on 00:02:17.880 --> 00:02:17.890 align:start position:0% tests on 00:02:17.890 --> 00:02:22.080 align:start position:0% tests on it<00:02:18.760> saves<00:02:19.510> the<00:02:19.750> results<00:02:20.170> on<00:02:20.260> chain<00:02:20.500> and<00:02:20.940> it<00:02:21.940> is 00:02:22.080 --> 00:02:22.090 align:start position:0% it saves the results on chain and it is 00:02:22.090 --> 00:02:23.880 align:start position:0% it saves the results on chain and it is completely<00:02:22.420> trustless<00:02:22.930> since<00:02:23.200> it's<00:02:23.440> a<00:02:23.620> smart 00:02:23.880 --> 00:02:23.890 align:start position:0% completely trustless since it's a smart 00:02:23.890 --> 00:02:26.160 align:start position:0% completely trustless since it's a smart contract<00:02:24.010> it<00:02:24.490> has<00:02:24.670> simple<00:02:25.000> web<00:02:25.150> interface<00:02:25.720> but 00:02:26.160 --> 00:02:26.170 align:start position:0% contract it has simple web interface but 00:02:26.170 --> 00:02:32.280 align:start position:0% contract it has simple web interface but it<00:02:26.590> can<00:02:26.860> be<00:02:27.010> used<00:02:27.190> by<00:02:27.460> a<00:02:27.490> smart<00:02:27.880> contract<00:02:30.990> so<00:02:31.990> I 00:02:32.280 --> 00:02:32.290 align:start position:0% it can be used by a smart contract so I 00:02:32.290 --> 00:02:36.210 align:start position:0% it can be used by a smart contract so I will<00:02:32.500> show<00:02:32.710> you<00:02:32.770> how<00:02:32.920> it<00:02:33.010> looks<00:02:33.070> like<00:02:34.230> so<00:02:35.230> the 00:02:36.210 --> 00:02:36.220 align:start position:0% will show you how it looks like so the 00:02:36.220 --> 00:02:38.310 align:start position:0% will show you how it looks like so the process<00:02:36.520> is<00:02:36.670> really<00:02:37.000> easy<00:02:37.150> it<00:02:37.600> has<00:02:37.930> only<00:02:38.140> three 00:02:38.310 --> 00:02:38.320 align:start position:0% process is really easy it has only three 00:02:38.320 --> 00:02:42.210 align:start position:0% process is really easy it has only three steps<00:02:38.650> you<00:02:38.860> enter<00:02:39.340> the<00:02:39.580> address<00:02:40.120> of<00:02:40.390> token<00:02:41.220> you 00:02:42.210 --> 00:02:42.220 align:start position:0% steps you enter the address of token you 00:02:42.220 --> 00:02:45.210 align:start position:0% steps you enter the address of token you approve<00:02:43.150> 1000<00:02:44.020> token<00:02:44.260> units<00:02:44.560> in<00:02:44.830> order<00:02:44.980> to 00:02:45.210 --> 00:02:45.220 align:start position:0% approve 1000 token units in order to 00:02:45.220 --> 00:02:47.910 align:start position:0% approve 1000 token units in order to perform<00:02:45.550> some<00:02:45.790> checks<00:02:45.820> and<00:02:46.740> please<00:02:47.740> note<00:02:47.890> that 00:02:47.910 --> 00:02:47.920 align:start position:0% perform some checks and please note that 00:02:47.920 --> 00:02:49.830 align:start position:0% perform some checks and please note that all<00:02:48.400> of<00:02:48.550> those<00:02:48.670> tokens<00:02:49.060> will<00:02:49.180> be<00:02:49.330> found<00:02:49.600> it<00:02:49.720> to 00:02:49.830 --> 00:02:49.840 align:start position:0% all of those tokens will be found it to 00:02:49.840 --> 00:02:52.350 align:start position:0% all of those tokens will be found it to you<00:02:49.959> and<00:02:50.290> then<00:02:51.010> step<00:02:51.160> 3<00:02:51.340> on<00:02:51.520> step<00:02:51.820> 3<00:02:52.000> you<00:02:52.150> click 00:02:52.350 --> 00:02:52.360 align:start position:0% you and then step 3 on step 3 you click 00:02:52.360 --> 00:02:57.210 align:start position:0% you and then step 3 on step 3 you click yes<00:02:52.630> ok<00:02:53.020> please<00:02:53.350> check<00:02:53.890> this<00:02:54.010> token<00:02:54.690> and<00:02:56.220> after 00:02:57.210 --> 00:02:57.220 align:start position:0% yes ok please check this token and after 00:02:57.220 --> 00:02:58.650 align:start position:0% yes ok please check this token and after a<00:02:57.250> couple<00:02:57.400> of<00:02:57.489> minutes<00:02:57.820> after<00:02:58.420> the 00:02:58.650 --> 00:02:58.660 align:start position:0% a couple of minutes after the 00:02:58.660 --> 00:03:02.250 align:start position:0% a couple of minutes after the transaction<00:02:59.100> transaction<00:03:00.100> is<00:03:00.550> mined<00:03:00.940> you<00:03:01.930> see 00:03:02.250 --> 00:03:02.260 align:start position:0% transaction transaction is mined you see 00:03:02.260 --> 00:03:04.380 align:start position:0% transaction transaction is mined you see the<00:03:02.440> result<00:03:02.800> it's<00:03:03.130> basically<00:03:03.730> it's<00:03:03.970> a<00:03:04.030> list<00:03:04.209> of 00:03:04.380 --> 00:03:04.390 align:start position:0% the result it's basically it's a list of 00:03:04.390 --> 00:03:06.720 align:start position:0% the result it's basically it's a list of properties<00:03:04.959> group<00:03:05.320> by<00:03:05.530> type<00:03:05.830> and<00:03:06.100> they<00:03:06.550> are 00:03:06.720 --> 00:03:06.730 align:start position:0% properties group by type and they are 00:03:06.730 --> 00:03:10.770 align:start position:0% properties group by type and they are color<00:03:07.030> coded<00:03:08.370> to<00:03:09.370> show<00:03:09.610> whether<00:03:09.910> the<00:03:10.239> concrete 00:03:10.770 --> 00:03:10.780 align:start position:0% color coded to show whether the concrete 00:03:10.780 --> 00:03:15.030 align:start position:0% color coded to show whether the concrete property<00:03:11.530> is<00:03:12.330> violated<00:03:13.330> or<00:03:13.840> not<00:03:14.230> so<00:03:14.680> the<00:03:14.830> same 00:03:15.030 --> 00:03:15.040 align:start position:0% property is violated or not so the same 00:03:15.040 --> 00:03:18.870 align:start position:0% property is violated or not so the same results<00:03:15.550> are<00:03:15.730> written<00:03:16.560> on<00:03:17.560> chain<00:03:18.040> and<00:03:18.280> can<00:03:18.760> be 00:03:18.870 --> 00:03:18.880 align:start position:0% results are written on chain and can be 00:03:18.880 --> 00:03:21.449 align:start position:0% results are written on chain and can be accessed<00:03:19.330> by<00:03:19.959> any<00:03:20.230> smart<00:03:20.590> contract<00:03:20.980> at<00:03:21.280> any 00:03:21.449 --> 00:03:21.459 align:start position:0% accessed by any smart contract at any 00:03:21.459 --> 00:03:27.990 align:start position:0% accessed by any smart contract at any time<00:03:22.950> so<00:03:23.950> what<00:03:24.100> we<00:03:24.220> get<00:03:24.630> we<00:03:25.630> get<00:03:25.780> low<00:03:26.380> price<00:03:27.000> you 00:03:27.990 --> 00:03:28.000 align:start position:0% time so what we get we get low price you 00:03:28.000 --> 00:03:31.199 align:start position:0% time so what we get we get low price you pay<00:03:28.209> only<00:03:28.420> for<00:03:28.750> guests<00:03:29.400> the<00:03:30.400> process<00:03:30.730> is<00:03:30.910> fully 00:03:31.199 --> 00:03:31.209 align:start position:0% pay only for guests the process is fully 00:03:31.209 --> 00:03:34.650 align:start position:0% pay only for guests the process is fully automated<00:03:32.340> because<00:03:33.340> no<00:03:33.760> people<00:03:33.970> involved<00:03:34.540> at 00:03:34.650 --> 00:03:34.660 align:start position:0% automated because no people involved at 00:03:34.660 --> 00:03:38.400 align:start position:0% automated because no people involved at any<00:03:34.930> moment<00:03:35.440> and<00:03:36.510> those<00:03:37.510> tests<00:03:37.959> are<00:03:38.110> really 00:03:38.400 --> 00:03:38.410 align:start position:0% any moment and those tests are really 00:03:38.410 --> 00:03:41.640 align:start position:0% any moment and those tests are really easy<00:03:38.620> to<00:03:38.769> run<00:03:39.040> you<00:03:39.580> saw<00:03:39.790> it<00:03:40.000> and<00:03:40.290> the<00:03:41.290> results 00:03:41.640 --> 00:03:41.650 align:start position:0% easy to run you saw it and the results 00:03:41.650 --> 00:03:44.820 align:start position:0% easy to run you saw it and the results are<00:03:41.769> easy<00:03:42.010> to<00:03:42.190> understand<00:03:42.730> and<00:03:43.000> easy<00:03:43.720> to<00:03:44.140> show 00:03:44.820 --> 00:03:44.830 align:start position:0% are easy to understand and easy to show 00:03:44.830 --> 00:03:47.850 align:start position:0% are easy to understand and easy to show to<00:03:44.890> anyone<00:03:45.370> and<00:03:45.870> not<00:03:46.870> to<00:03:47.019> say<00:03:47.200> that<00:03:47.350> we<00:03:47.530> achieve 00:03:47.850 --> 00:03:47.860 align:start position:0% to anyone and not to say that we achieve 00:03:47.860 --> 00:03:52.440 align:start position:0% to anyone and not to say that we achieve Trust<00:03:48.340> lessness<00:03:48.519> so<00:03:50.940> please<00:03:51.940> go<00:03:52.120> and<00:03:52.209> try<00:03:52.390> it 00:03:52.440 --> 00:03:52.450 align:start position:0% Trust lessness so please go and try it 00:03:52.450 --> 00:03:57.240 align:start position:0% Trust lessness so please go and try it it's<00:03:52.959> online<00:03:53.950> it's<00:03:54.700> tested<00:03:55.209> net<00:03:55.630> and<00:03:56.100> also<00:03:57.100> we 00:03:57.240 --> 00:03:57.250 align:start position:0% it's online it's tested net and also we 00:03:57.250 --> 00:04:01.699 align:start position:0% it's online it's tested net and also we open<00:03:57.610> sourced<00:03:57.940> it<00:03:58.150> and<00:03:58.330> it<00:03:59.230> can<00:03:59.530> be<00:03:59.680> it<00:04:00.430> can<00:04:00.489> be 00:04:01.699 --> 00:04:01.709 align:start position:0% open sourced it and it can be it can be 00:04:01.709 --> 00:04:05.880 align:start position:0% open sourced it and it can be it can be found<00:04:02.709> on<00:04:03.269> github<00:04:04.269> so<00:04:04.510> you<00:04:04.780> can<00:04:05.380> play<00:04:05.590> with<00:04:05.769> it 00:04:05.880 --> 00:04:05.890 align:start position:0% found on github so you can play with it 00:04:05.890 --> 00:04:11.250 align:start position:0% found on github so you can play with it and<00:04:06.130> maybe<00:04:09.299> change<00:04:10.299> it<00:04:10.450> according<00:04:10.989> to<00:04:11.110> your 00:04:11.250 --> 00:04:11.260 align:start position:0% and maybe change it according to your 00:04:11.260 --> 00:04:13.850 align:start position:0% and maybe change it according to your needs 00:04:13.850 --> 00:04:13.860 align:start position:0% 00:04:13.860 --> 00:04:19.770 align:start position:0% thank<00:04:14.860> you<00:04:17.910> hey<00:04:18.910> everyone<00:04:19.209> my<00:04:19.450> name<00:04:19.570> is<00:04:19.630> Tim 00:04:19.770 --> 00:04:19.780 align:start position:0% thank you hey everyone my name is Tim 00:04:19.780 --> 00:04:21.659 align:start position:0% thank you hey everyone my name is Tim Baker<00:04:19.959> I'm<00:04:20.350> here<00:04:20.650> to<00:04:20.739> talk<00:04:20.890> about<00:04:21.130> how<00:04:21.340> we<00:04:21.400> can 00:04:21.659 --> 00:04:21.669 align:start position:0% Baker I'm here to talk about how we can 00:04:21.669 --> 00:04:23.940 align:start position:0% Baker I'm here to talk about how we can fund<00:04:21.940> each<00:04:22.240> one<00:04:22.540> point<00:04:22.780> X<00:04:22.930> by<00:04:23.260> auctioning<00:04:23.919> off 00:04:23.940 --> 00:04:23.950 align:start position:0% fund each one point X by auctioning off 00:04:23.950 --> 00:04:25.830 align:start position:0% fund each one point X by auctioning off the<00:04:24.160> names<00:04:24.340> to<00:04:24.729> a<00:04:24.910> theorem<00:04:25.210> network<00:04:25.510> upgrades 00:04:25.830 --> 00:04:25.840 align:start position:0% the names to a theorem network upgrades 00:04:25.840 --> 00:04:29.880 align:start position:0% the names to a theorem network upgrades so<00:04:26.650> bit<00:04:27.310> of<00:04:27.400> background<00:04:28.289> there's<00:04:29.289> some 00:04:29.880 --> 00:04:29.890 align:start position:0% so bit of background there's some 00:04:29.890 --> 00:04:31.290 align:start position:0% so bit of background there's some initiatives<00:04:30.370> on<00:04:30.669> a<00:04:30.700> theorem<00:04:31.000> one<00:04:31.120> thought<00:04:31.270> oh 00:04:31.290 --> 00:04:31.300 align:start position:0% initiatives on a theorem one thought oh 00:04:31.300 --> 00:04:31.800 align:start position:0% initiatives on a theorem one thought oh and 00:04:31.800 --> 00:04:31.810 align:start position:0% and 00:04:31.810 --> 00:04:34.409 align:start position:0% and that<00:04:32.620> donates<00:04:32.950> the<00:04:33.190> fund<00:04:33.520> they<00:04:33.910> don't<00:04:34.090> get<00:04:34.270> the 00:04:34.409 --> 00:04:34.419 align:start position:0% that donates the fund they don't get the 00:04:34.419 --> 00:04:35.850 align:start position:0% that donates the fund they don't get the funds<00:04:34.630> they<00:04:34.810> need<00:04:34.990> to<00:04:35.200> get<00:04:35.410> off<00:04:35.470> the<00:04:35.680> ground 00:04:35.850 --> 00:04:35.860 align:start position:0% funds they need to get off the ground 00:04:35.860 --> 00:04:38.070 align:start position:0% funds they need to get off the ground and<00:04:36.100> oftentimes<00:04:37.000> the<00:04:37.450> amount<00:04:37.690> needed<00:04:37.900> for 00:04:38.070 --> 00:04:38.080 align:start position:0% and oftentimes the amount needed for 00:04:38.080 --> 00:04:39.690 align:start position:0% and oftentimes the amount needed for these<00:04:38.320> initiatives<00:04:38.680> are<00:04:38.950> quite<00:04:39.160> small<00:04:39.370> too 00:04:39.690 --> 00:04:39.700 align:start position:0% these initiatives are quite small too 00:04:39.700 --> 00:04:41.670 align:start position:0% these initiatives are quite small too basically<00:04:40.000> to<00:04:40.270> build<00:04:40.389> a<00:04:40.540> proof<00:04:40.720> of<00:04:40.810> concept<00:04:40.960> to 00:04:41.670 --> 00:04:41.680 align:start position:0% basically to build a proof of concept to 00:04:41.680 --> 00:04:43.320 align:start position:0% basically to build a proof of concept to get<00:04:41.800> to<00:04:41.919> an<00:04:42.010> initial<00:04:42.430> EEP<00:04:42.639> and<00:04:42.970> something<00:04:43.240> like 00:04:43.320 --> 00:04:43.330 align:start position:0% get to an initial EEP and something like 00:04:43.330 --> 00:04:45.000 align:start position:0% get to an initial EEP and something like that<00:04:43.480> so<00:04:44.050> I<00:04:44.080> think<00:04:44.169> we<00:04:44.350> could<00:04:44.500> fund<00:04:44.650> some<00:04:44.980> of 00:04:45.000 --> 00:04:45.010 align:start position:0% that so I think we could fund some of 00:04:45.010 --> 00:04:46.590 align:start position:0% that so I think we could fund some of these<00:04:45.190> efforts<00:04:45.400> by<00:04:46.030> auctioning<00:04:46.510> off<00:04:46.540> the 00:04:46.590 --> 00:04:46.600 align:start position:0% these efforts by auctioning off the 00:04:46.600 --> 00:04:50.129 align:start position:0% these efforts by auctioning off the names<00:04:46.900> the<00:04:47.320> network<00:04:47.800> upgrades<00:04:49.020> so<00:04:50.020> what<00:04:50.110> I 00:04:50.129 --> 00:04:50.139 align:start position:0% names the network upgrades so what I 00:04:50.139 --> 00:04:53.159 align:start position:0% names the network upgrades so what I mean<00:04:50.350> specifically<00:04:50.770> is<00:04:51.070> I<00:04:51.669> think<00:04:52.360> we<00:04:52.810> could 00:04:53.159 --> 00:04:53.169 align:start position:0% mean specifically is I think we could 00:04:53.169 --> 00:04:55.290 align:start position:0% mean specifically is I think we could run<00:04:53.350> an<00:04:53.590> untrained<00:04:54.040> option<00:04:54.400> from<00:04:54.850> the<00:04:55.060> first 00:04:55.290 --> 00:04:55.300 align:start position:0% run an untrained option from the first 00:04:55.300 --> 00:04:56.760 align:start position:0% run an untrained option from the first block<00:04:55.480> of<00:04:55.630> an<00:04:55.690> upgrade<00:04:55.870> all<00:04:56.290> the<00:04:56.440> way<00:04:56.530> to<00:04:56.590> the 00:04:56.760 --> 00:04:56.770 align:start position:0% block of an upgrade all the way to the 00:04:56.770 --> 00:04:58.500 align:start position:0% block of an upgrade all the way to the last<00:04:56.919> block<00:04:57.190> of<00:04:57.220> it<00:04:57.460> before<00:04:57.820> the<00:04:57.910> next<00:04:58.090> one<00:04:58.240> and 00:04:58.500 --> 00:04:58.510 align:start position:0% last block of it before the next one and 00:04:58.510 --> 00:05:00.570 align:start position:0% last block of it before the next one and throughout<00:04:59.080> the<00:04:59.200> auction<00:04:59.530> people<00:04:59.980> bid<00:05:00.220> for 00:05:00.570 --> 00:05:00.580 align:start position:0% throughout the auction people bid for 00:05:00.580 --> 00:05:03.240 align:start position:0% throughout the auction people bid for what<00:05:00.730> the<00:05:00.910> name<00:05:01.090> of<00:05:01.120> the<00:05:01.360> upgrade<00:05:01.720> will<00:05:01.840> be<00:05:02.250> and 00:05:03.240 --> 00:05:03.250 align:start position:0% what the name of the upgrade will be and 00:05:03.250 --> 00:05:05.190 align:start position:0% what the name of the upgrade will be and this<00:05:03.850> kind<00:05:04.090> of<00:05:04.120> a<00:05:04.210> dynamic<00:05:04.360> auction<00:05:04.990> so 00:05:05.190 --> 00:05:05.200 align:start position:0% this kind of a dynamic auction so 00:05:05.200 --> 00:05:06.750 align:start position:0% this kind of a dynamic auction so throughout<00:05:05.530> the<00:05:05.710> oxygen<00:05:06.010> whatever<00:05:06.190> the 00:05:06.750 --> 00:05:06.760 align:start position:0% throughout the oxygen whatever the 00:05:06.760 --> 00:05:08.879 align:start position:0% throughout the oxygen whatever the highest<00:05:07.120> bid<00:05:07.300> says<00:05:07.510> the<00:05:07.630> name<00:05:07.810> is<00:05:07.840> is<00:05:08.200> what<00:05:08.650> we 00:05:08.879 --> 00:05:08.889 align:start position:0% highest bid says the name is is what we 00:05:08.889 --> 00:05:11.790 align:start position:0% highest bid says the name is is what we refer<00:05:09.040> to<00:05:09.360> the<00:05:10.360> upgrade<00:05:10.660> as<00:05:10.810> for<00:05:11.110> that<00:05:11.229> time 00:05:11.790 --> 00:05:11.800 align:start position:0% refer to the upgrade as for that time 00:05:11.800 --> 00:05:15.420 align:start position:0% refer to the upgrade as for that time for<00:05:12.790> that<00:05:12.910> point<00:05:13.120> in<00:05:13.210> time<00:05:13.330> um<00:05:13.990> and<00:05:14.740> obviously 00:05:15.420 --> 00:05:15.430 align:start position:0% for that point in time um and obviously 00:05:15.430 --> 00:05:17.520 align:start position:0% for that point in time um and obviously whenever<00:05:16.150> someone<00:05:16.479> out<00:05:16.570> bids<00:05:16.810> that<00:05:17.050> bid<00:05:17.200> then 00:05:17.520 --> 00:05:17.530 align:start position:0% whenever someone out bids that bid then 00:05:17.530 --> 00:05:19.400 align:start position:0% whenever someone out bids that bid then you<00:05:17.650> refund<00:05:17.950> the<00:05:18.070> previous<00:05:18.340> bird<00:05:18.520> person 00:05:19.400 --> 00:05:19.410 align:start position:0% you refund the previous bird person 00:05:19.410 --> 00:05:22.080 align:start position:0% you refund the previous bird person update<00:05:20.410> the<00:05:20.530> name<00:05:20.650> and<00:05:21.520> that's<00:05:21.729> it 00:05:22.080 --> 00:05:22.090 align:start position:0% update the name and that's it 00:05:22.090 --> 00:05:23.129 align:start position:0% update the name and that's it there's<00:05:22.540> a<00:05:22.570> couple<00:05:22.720> things<00:05:22.900> that<00:05:23.020> are 00:05:23.129 --> 00:05:23.139 align:start position:0% there's a couple things that are 00:05:23.139 --> 00:05:25.050 align:start position:0% there's a couple things that are important<00:05:23.530> here<00:05:23.590> the<00:05:24.100> first<00:05:24.370> is<00:05:24.610> that<00:05:24.850> you'd 00:05:25.050 --> 00:05:25.060 align:start position:0% important here the first is that you'd 00:05:25.060 --> 00:05:26.370 align:start position:0% important here the first is that you'd want<00:05:25.240> to<00:05:25.270> have<00:05:25.389> like<00:05:25.570> a<00:05:25.600> high<00:05:25.840> minimum<00:05:26.200> bid 00:05:26.370 --> 00:05:26.380 align:start position:0% want to have like a high minimum bid 00:05:26.380 --> 00:05:28.890 align:start position:0% want to have like a high minimum bid because<00:05:27.070> premium<00:05:28.000> namespace<00:05:28.450> you're<00:05:28.600> selling 00:05:28.890 --> 00:05:28.900 align:start position:0% because premium namespace you're selling 00:05:28.900 --> 00:05:30.780 align:start position:0% because premium namespace you're selling you<00:05:29.139> want<00:05:29.320> to<00:05:29.380> make<00:05:29.470> sure<00:05:29.500> that<00:05:29.860> people<00:05:30.669> value 00:05:30.780 --> 00:05:30.790 align:start position:0% you want to make sure that people value 00:05:30.790 --> 00:05:32.850 align:start position:0% you want to make sure that people value it<00:05:31.030> accordingly<00:05:31.419> so<00:05:31.930> I<00:05:31.990> proposed<00:05:32.290> a<00:05:32.320> thousand 00:05:32.850 --> 00:05:32.860 align:start position:0% it accordingly so I proposed a thousand 00:05:32.860 --> 00:05:34.890 align:start position:0% it accordingly so I proposed a thousand each<00:05:33.010> minimum<00:05:33.490> and<00:05:34.389> you<00:05:34.419> also<00:05:34.600> want<00:05:34.810> to<00:05:34.840> have 00:05:34.890 --> 00:05:34.900 align:start position:0% each minimum and you also want to have 00:05:34.900 --> 00:05:36.300 align:start position:0% each minimum and you also want to have large<00:05:35.229> increments<00:05:35.770> between<00:05:35.860> the<00:05:36.130> bids 00:05:36.300 --> 00:05:36.310 align:start position:0% large increments between the bids 00:05:36.310 --> 00:05:37.529 align:start position:0% large increments between the bids because<00:05:36.610> you<00:05:36.700> don't<00:05:36.820> want<00:05:36.940> people<00:05:37.030> to<00:05:37.300> spam 00:05:37.529 --> 00:05:37.539 align:start position:0% because you don't want people to spam 00:05:37.539 --> 00:05:39.420 align:start position:0% because you don't want people to spam the<00:05:37.570> network<00:05:38.020> while<00:05:38.830> they're<00:05:38.979> making<00:05:39.039> bids 00:05:39.420 --> 00:05:39.430 align:start position:0% the network while they're making bids 00:05:39.430 --> 00:05:41.340 align:start position:0% the network while they're making bids for<00:05:39.700> for<00:05:39.970> these<00:05:40.060> names<00:05:40.270> so<00:05:40.900> I<00:05:40.930> had<00:05:41.050> a<00:05:41.110> proposal 00:05:41.340 --> 00:05:41.350 align:start position:0% for for these names so I had a proposal 00:05:41.350 --> 00:05:43.920 align:start position:0% for for these names so I had a proposal for<00:05:41.650> a<00:05:41.710> hundred<00:05:42.010> eath<00:05:42.130> and<00:05:43.120> this<00:05:43.780> would 00:05:43.920 --> 00:05:43.930 align:start position:0% for a hundred eath and this would 00:05:43.930 --> 00:05:45.240 align:start position:0% for a hundred eath and this would obviously<00:05:43.960> be<00:05:44.320> a<00:05:44.440> bit<00:05:44.620> complicated<00:05:44.919> on<00:05:45.220> the 00:05:45.240 --> 00:05:45.250 align:start position:0% obviously be a bit complicated on the 00:05:45.250 --> 00:05:46.469 align:start position:0% obviously be a bit complicated on the client<00:05:45.640> side<00:05:45.669> because<00:05:46.120> if<00:05:46.210> they<00:05:46.300> need<00:05:46.450> to 00:05:46.469 --> 00:05:46.479 align:start position:0% client side because if they need to 00:05:46.479 --> 00:05:48.090 align:start position:0% client side because if they need to change<00:05:46.720> the<00:05:46.900> name<00:05:47.020> all<00:05:47.169> the<00:05:47.260> time<00:05:47.500> that's<00:05:47.950> not 00:05:48.090 --> 00:05:48.100 align:start position:0% change the name all the time that's not 00:05:48.100 --> 00:05:49.890 align:start position:0% change the name all the time that's not ideal<00:05:48.220> so<00:05:48.970> we<00:05:49.270> could<00:05:49.419> just<00:05:49.570> use<00:05:49.720> version 00:05:49.890 --> 00:05:49.900 align:start position:0% ideal so we could just use version 00:05:49.900 --> 00:05:52.710 align:start position:0% ideal so we could just use version numbers<00:05:50.350> in<00:05:50.560> the<00:05:50.770> clients<00:05:51.250> and<00:05:51.430> use<00:05:51.760> marketing 00:05:52.710 --> 00:05:52.720 align:start position:0% numbers in the clients and use marketing 00:05:52.720 --> 00:05:54.810 align:start position:0% numbers in the clients and use marketing name<00:05:52.870> that<00:05:53.680> we<00:05:53.770> use<00:05:53.800> sort<00:05:54.250> of<00:05:54.430> in<00:05:54.550> blog<00:05:54.789> posts 00:05:54.810 --> 00:05:54.820 align:start position:0% name that we use sort of in blog posts 00:05:54.820 --> 00:05:57.240 align:start position:0% name that we use sort of in blog posts and<00:05:55.390> whatnot<00:05:55.660> kind<00:05:56.440> of<00:05:56.500> like<00:05:56.590> Android<00:05:57.010> does 00:05:57.240 --> 00:05:57.250 align:start position:0% and whatnot kind of like Android does 00:05:57.250 --> 00:05:59.070 align:start position:0% and whatnot kind of like Android does where<00:05:57.490> all<00:05:57.640> the<00:05:57.789> major<00:05:57.910> releases<00:05:58.270> have<00:05:58.570> both<00:05:58.810> a 00:05:59.070 --> 00:05:59.080 align:start position:0% where all the major releases have both a 00:05:59.080 --> 00:06:04.200 align:start position:0% where all the major releases have both a marketing<00:05:59.620> name<00:05:59.800> and<00:06:00.070> a<00:06:00.340> version<00:06:00.490> number<00:06:03.210> and 00:06:04.200 --> 00:06:04.210 align:start position:0% marketing name and a version number and 00:06:04.210 --> 00:06:07.110 align:start position:0% marketing name and a version number and so<00:06:05.169> on<00:06:05.350> the<00:06:05.740> upgrade<00:06:06.190> block<00:06:06.400> whatever<00:06:06.850> their 00:06:07.110 --> 00:06:07.120 align:start position:0% so on the upgrade block whatever their 00:06:07.120 --> 00:06:08.400 align:start position:0% so on the upgrade block whatever their highest<00:06:07.360> bid<00:06:07.510> says<00:06:07.720> the<00:06:07.810> name<00:06:07.960> is<00:06:08.139> gets 00:06:08.400 --> 00:06:08.410 align:start position:0% highest bid says the name is gets 00:06:08.410 --> 00:06:09.840 align:start position:0% highest bid says the name is gets finalized<00:06:08.800> on<00:06:08.979> chain<00:06:09.250> and<00:06:09.490> that's<00:06:09.669> how<00:06:09.789> we 00:06:09.840 --> 00:06:09.850 align:start position:0% finalized on chain and that's how we 00:06:09.850 --> 00:06:12.330 align:start position:0% finalized on chain and that's how we referred<00:06:10.419> to<00:06:10.510> the<00:06:10.600> upgrade<00:06:10.990> going<00:06:11.919> forward<00:06:12.220> in 00:06:12.330 --> 00:06:12.340 align:start position:0% referred to the upgrade going forward in 00:06:12.340 --> 00:06:16.860 align:start position:0% referred to the upgrade going forward in time<00:06:12.570> and<00:06:14.820> what<00:06:15.820> are<00:06:15.880> you<00:06:15.970> actually<00:06:16.090> fund<00:06:16.539> here 00:06:16.860 --> 00:06:16.870 align:start position:0% time and what are you actually fund here 00:06:16.870 --> 00:06:19.350 align:start position:0% time and what are you actually fund here so<00:06:17.440> I<00:06:17.680> think<00:06:18.070> we<00:06:18.520> should<00:06:18.669> raise<00:06:18.820> these<00:06:19.120> funds 00:06:19.350 --> 00:06:19.360 align:start position:0% so I think we should raise these funds 00:06:19.360 --> 00:06:20.909 align:start position:0% so I think we should raise these funds and<00:06:19.630> try<00:06:19.750> to<00:06:19.810> spend<00:06:20.110> them<00:06:20.229> on<00:06:20.380> initiatives 00:06:20.909 --> 00:06:20.919 align:start position:0% and try to spend them on initiatives 00:06:20.919 --> 00:06:22.710 align:start position:0% and try to spend them on initiatives that<00:06:21.070> have<00:06:21.190> a<00:06:21.250> high<00:06:21.460> likelihood<00:06:21.700> of<00:06:22.180> improving 00:06:22.710 --> 00:06:22.720 align:start position:0% that have a high likelihood of improving 00:06:22.720 --> 00:06:25.560 align:start position:0% that have a high likelihood of improving the<00:06:22.930> etherium<00:06:23.260> network<00:06:23.590> today<00:06:24.360> this<00:06:25.360> means 00:06:25.560 --> 00:06:25.570 align:start position:0% the etherium network today this means 00:06:25.570 --> 00:06:28.110 align:start position:0% the etherium network today this means things<00:06:25.810> like<00:06:26.020> new<00:06:26.830> syncing<00:06:27.639> and<00:06:27.729> discovery 00:06:28.110 --> 00:06:28.120 align:start position:0% things like new syncing and discovery 00:06:28.120 --> 00:06:30.360 align:start position:0% things like new syncing and discovery protocols<00:06:28.630> some<00:06:28.930> better<00:06:29.110> testing<00:06:29.620> some<00:06:30.190> eath 00:06:30.360 --> 00:06:30.370 align:start position:0% protocols some better testing some eath 00:06:30.370 --> 00:06:32.129 align:start position:0% protocols some better testing some eath one<00:06:30.550> point<00:06:30.729> X<00:06:30.880> initiatives<00:06:31.419> like<00:06:31.660> state<00:06:31.870> rent 00:06:32.129 --> 00:06:32.139 align:start position:0% one point X initiatives like state rent 00:06:32.139 --> 00:06:34.290 align:start position:0% one point X initiatives like state rent some<00:06:32.650> coordination<00:06:33.100> across<00:06:33.490> the<00:06:33.700> clients<00:06:34.120> or 00:06:34.290 --> 00:06:34.300 align:start position:0% some coordination across the clients or 00:06:34.300 --> 00:06:36.150 align:start position:0% some coordination across the clients or even<00:06:34.570> some<00:06:34.720> research<00:06:35.020> ideas<00:06:35.380> like<00:06:35.680> off<00:06:35.889> chain 00:06:36.150 --> 00:06:36.160 align:start position:0% even some research ideas like off chain 00:06:36.160 --> 00:06:38.700 align:start position:0% even some research ideas like off chain storage<00:06:36.550> and<00:06:36.960> again<00:06:37.960> it's<00:06:38.169> important<00:06:38.620> to<00:06:38.650> note 00:06:38.700 --> 00:06:38.710 align:start position:0% storage and again it's important to note 00:06:38.710 --> 00:06:40.409 align:start position:0% storage and again it's important to note that<00:06:38.860> we<00:06:39.190> should<00:06:39.370> try<00:06:39.520> to<00:06:39.580> optimize<00:06:39.849> to<00:06:40.270> have<00:06:40.390> a 00:06:40.409 --> 00:06:40.419 align:start position:0% that we should try to optimize to have a 00:06:40.419 --> 00:06:42.210 align:start position:0% that we should try to optimize to have a large<00:06:40.659> set<00:06:41.020> of<00:06:41.110> initiatives<00:06:41.440> so<00:06:41.830> have<00:06:41.979> fairly 00:06:42.210 --> 00:06:42.220 align:start position:0% large set of initiatives so have fairly 00:06:42.220 --> 00:06:43.920 align:start position:0% large set of initiatives so have fairly small<00:06:42.520> amounts<00:06:43.060> that<00:06:43.270> are<00:06:43.390> kind<00:06:43.539> of<00:06:43.599> proof<00:06:43.810> of 00:06:43.920 --> 00:06:43.930 align:start position:0% small amounts that are kind of proof of 00:06:43.930 --> 00:06:45.300 align:start position:0% small amounts that are kind of proof of concept<00:06:44.289> size 00:06:45.300 --> 00:06:45.310 align:start position:0% concept size 00:06:45.310 --> 00:06:47.010 align:start position:0% concept size that<00:06:45.460> are<00:06:45.580> spent<00:06:45.820> fairly<00:06:46.090> quickly<00:06:46.300> so<00:06:46.630> in<00:06:46.960> an 00:06:47.010 --> 00:06:47.020 align:start position:0% that are spent fairly quickly so in an 00:06:47.020 --> 00:06:48.660 align:start position:0% that are spent fairly quickly so in an ideal<00:06:47.350> world<00:06:47.560> you've<00:06:47.830> spent<00:06:48.130> almost<00:06:48.370> all<00:06:48.639> of 00:06:48.660 --> 00:06:48.670 align:start position:0% ideal world you've spent almost all of 00:06:48.670 --> 00:06:50.180 align:start position:0% ideal world you've spent almost all of the<00:06:48.850> funds<00:06:49.060> from<00:06:49.150> one<00:06:49.420> auction<00:06:49.600> before 00:06:50.180 --> 00:06:50.190 align:start position:0% the funds from one auction before 00:06:50.190 --> 00:06:54.180 align:start position:0% the funds from one auction before starting<00:06:51.190> the<00:06:51.310> next<00:06:51.490> one<00:06:52.680> but<00:06:53.680> who<00:06:53.830> gets<00:06:54.040> to 00:06:54.180 --> 00:06:54.190 align:start position:0% starting the next one but who gets to 00:06:54.190 --> 00:06:56.220 align:start position:0% starting the next one but who gets to decide<00:06:54.310> how<00:06:54.639> we<00:06:54.700> spend<00:06:54.970> those<00:06:55.060> funds<00:06:55.330> um 00:06:56.220 --> 00:06:56.230 align:start position:0% decide how we spend those funds um 00:06:56.230 --> 00:06:58.290 align:start position:0% decide how we spend those funds um proposal<00:06:57.100> for<00:06:57.250> this<00:06:57.400> is<00:06:57.700> a<00:06:57.760> three<00:06:58.030> out<00:06:58.120> of<00:06:58.150> five 00:06:58.290 --> 00:06:58.300 align:start position:0% proposal for this is a three out of five 00:06:58.300 --> 00:07:00.270 align:start position:0% proposal for this is a three out of five multi-sig<00:06:58.840> with<00:06:59.020> the<00:06:59.080> following<00:06:59.410> parties<00:06:59.740> so 00:07:00.270 --> 00:07:00.280 align:start position:0% multi-sig with the following parties so 00:07:00.280 --> 00:07:01.860 align:start position:0% multi-sig with the following parties so you'd<00:07:00.400> have<00:07:00.460> someone<00:07:01.389> who's<00:07:01.570> there<00:07:01.690> to 00:07:01.860 --> 00:07:01.870 align:start position:0% you'd have someone who's there to 00:07:01.870 --> 00:07:03.629 align:start position:0% you'd have someone who's there to represent<00:07:01.990> the<00:07:02.350> theorem<00:07:02.710> foundation<00:07:03.160> who's 00:07:03.629 --> 00:07:03.639 align:start position:0% represent the theorem foundation who's 00:07:03.639 --> 00:07:04.980 align:start position:0% represent the theorem foundation who's not<00:07:03.790> a<00:07:03.820> client<00:07:04.030> developer<00:07:04.510> who's<00:07:04.780> really 00:07:04.980 --> 00:07:04.990 align:start position:0% not a client developer who's really 00:07:04.990 --> 00:07:06.360 align:start position:0% not a client developer who's really there<00:07:05.139> to<00:07:05.260> represent<00:07:05.380> sort<00:07:05.889> of<00:07:05.950> the<00:07:06.070> etherium 00:07:06.360 --> 00:07:06.370 align:start position:0% there to represent sort of the etherium 00:07:06.370 --> 00:07:08.460 align:start position:0% there to represent sort of the etherium brand<00:07:06.669> and<00:07:06.970> vision<00:07:07.330> I<00:07:07.540> didn't<00:07:08.200> want<00:07:08.320> to<00:07:08.380> have 00:07:08.460 --> 00:07:08.470 align:start position:0% brand and vision I didn't want to have 00:07:08.470 --> 00:07:10.800 align:start position:0% brand and vision I didn't want to have to<00:07:08.680> kind<00:07:08.919> developers<00:07:09.460> ideally<00:07:10.360> one<00:07:10.540> or<00:07:10.660> more 00:07:10.800 --> 00:07:10.810 align:start position:0% to kind developers ideally one or more 00:07:10.810 --> 00:07:12.750 align:start position:0% to kind developers ideally one or more not<00:07:11.080> from<00:07:11.260> the<00:07:11.350> EF<00:07:11.650> who<00:07:12.520> are<00:07:12.580> there<00:07:12.730> to 00:07:12.750 --> 00:07:12.760 align:start position:0% not from the EF who are there to 00:07:12.760 --> 00:07:15.750 align:start position:0% not from the EF who are there to represent<00:07:12.940> the<00:07:13.480> core<00:07:13.660> devs<00:07:13.919> and<00:07:14.919> then<00:07:15.250> you'd 00:07:15.750 --> 00:07:15.760 align:start position:0% represent the core devs and then you'd 00:07:15.760 --> 00:07:17.250 align:start position:0% represent the core devs and then you'd want<00:07:15.790> also<00:07:16.060> an<00:07:16.300> independent<00:07:16.570> protocol 00:07:17.250 --> 00:07:17.260 align:start position:0% want also an independent protocol 00:07:17.260 --> 00:07:18.630 align:start position:0% want also an independent protocol developer<00:07:17.710> to<00:07:18.070> someone<00:07:18.310> who's<00:07:18.490> not 00:07:18.630 --> 00:07:18.640 align:start position:0% developer to someone who's not 00:07:18.640 --> 00:07:19.890 align:start position:0% developer to someone who's not affiliated<00:07:19.090> with<00:07:19.240> one<00:07:19.510> of<00:07:19.630> the<00:07:19.750> bigger 00:07:19.890 --> 00:07:19.900 align:start position:0% affiliated with one of the bigger 00:07:19.900 --> 00:07:21.720 align:start position:0% affiliated with one of the bigger companies<00:07:20.380> in<00:07:20.500> the<00:07:20.590> space<00:07:20.680> and<00:07:21.070> finally 00:07:21.720 --> 00:07:21.730 align:start position:0% companies in the space and finally 00:07:21.730 --> 00:07:22.830 align:start position:0% companies in the space and finally someone<00:07:22.030> to<00:07:22.180> represent<00:07:22.570> the<00:07:22.630> broader 00:07:22.830 --> 00:07:22.840 align:start position:0% someone to represent the broader 00:07:22.840 --> 00:07:24.600 align:start position:0% someone to represent the broader community<00:07:23.050> so<00:07:23.770> someone<00:07:24.070> who's<00:07:24.220> not<00:07:24.340> part<00:07:24.580> of 00:07:24.600 --> 00:07:24.610 align:start position:0% community so someone who's not part of 00:07:24.610 --> 00:07:27.120 align:start position:0% community so someone who's not part of the<00:07:24.730> EF<00:07:25.030> who's<00:07:25.270> not<00:07:25.419> a<00:07:25.450> core<00:07:25.870> developer<00:07:26.130> but 00:07:27.120 --> 00:07:27.130 align:start position:0% the EF who's not a core developer but 00:07:27.130 --> 00:07:28.440 align:start position:0% the EF who's not a core developer but just<00:07:27.280> represents<00:07:27.669> the<00:07:27.760> etherium<00:07:28.060> community 00:07:28.440 --> 00:07:28.450 align:start position:0% just represents the etherium community 00:07:28.450 --> 00:07:30.240 align:start position:0% just represents the etherium community at<00:07:28.540> large<00:07:28.720> whether<00:07:29.320> they're<00:07:29.500> a<00:07:29.530> top<00:07:29.770> developer 00:07:30.240 --> 00:07:30.250 align:start position:0% at large whether they're a top developer 00:07:30.250 --> 00:07:32.280 align:start position:0% at large whether they're a top developer and<00:07:30.550> a<00:07:30.580> theorem<00:07:30.880> cat<00:07:31.060> harder<00:07:31.450> or<00:07:31.870> just<00:07:32.140> some 00:07:32.280 --> 00:07:32.290 align:start position:0% and a theorem cat harder or just some 00:07:32.290 --> 00:07:33.630 align:start position:0% and a theorem cat harder or just some reddit<00:07:32.560> or<00:07:32.680> Twitter<00:07:32.919> user<00:07:33.160> who's<00:07:33.520> very 00:07:33.630 --> 00:07:33.640 align:start position:0% reddit or Twitter user who's very 00:07:33.640 --> 00:07:36.750 align:start position:0% reddit or Twitter user who's very favorable<00:07:34.180> towards<00:07:34.450> a<00:07:34.480> theorem<00:07:35.070> um 00:07:36.750 --> 00:07:36.760 align:start position:0% favorable towards a theorem um 00:07:36.760 --> 00:07:39.000 align:start position:0% favorable towards a theorem um and<00:07:37.030> the<00:07:37.630> people<00:07:37.900> on<00:07:37.990> these<00:07:38.080> multi-sig<00:07:38.620> would 00:07:39.000 --> 00:07:39.010 align:start position:0% and the people on these multi-sig would 00:07:39.010 --> 00:07:40.680 align:start position:0% and the people on these multi-sig would basically<00:07:39.190> be<00:07:39.430> able<00:07:39.610> to<00:07:39.880> rotate<00:07:40.030> in<00:07:40.419> and<00:07:40.600> out 00:07:40.680 --> 00:07:40.690 align:start position:0% basically be able to rotate in and out 00:07:40.690 --> 00:07:42.420 align:start position:0% basically be able to rotate in and out on<00:07:40.960> a<00:07:40.990> per<00:07:41.200> upgrade<00:07:41.500> basis<00:07:41.860> so<00:07:42.220> you're<00:07:42.340> not 00:07:42.420 --> 00:07:42.430 align:start position:0% on a per upgrade basis so you're not 00:07:42.430 --> 00:07:44.400 align:start position:0% on a per upgrade basis so you're not signing<00:07:42.760> up<00:07:42.910> to<00:07:43.030> this<00:07:43.150> for<00:07:43.330> life<00:07:43.450> this 00:07:44.400 --> 00:07:44.410 align:start position:0% signing up to this for life this 00:07:44.410 --> 00:07:46.080 align:start position:0% signing up to this for life this obviously<00:07:44.770> implies<00:07:44.979> you<00:07:45.190> need<00:07:45.340> a<00:07:45.370> process<00:07:45.610> to 00:07:46.080 --> 00:07:46.090 align:start position:0% obviously implies you need a process to 00:07:46.090 --> 00:07:48.060 align:start position:0% obviously implies you need a process to decide<00:07:46.570> how<00:07:46.990> you<00:07:47.050> add<00:07:47.350> or<00:07:47.530> remove<00:07:47.650> people<00:07:48.040> from 00:07:48.060 --> 00:07:48.070 align:start position:0% decide how you add or remove people from 00:07:48.070 --> 00:07:50.190 align:start position:0% decide how you add or remove people from that<00:07:48.310> multi-sig<00:07:48.790> and<00:07:49.720> there's<00:07:49.990> a<00:07:50.050> couple 00:07:50.190 --> 00:07:50.200 align:start position:0% that multi-sig and there's a couple 00:07:50.200 --> 00:07:51.900 align:start position:0% that multi-sig and there's a couple constraints<00:07:50.770> on<00:07:50.890> the<00:07:51.460> people<00:07:51.700> in<00:07:51.880> that 00:07:51.900 --> 00:07:51.910 align:start position:0% constraints on the people in that 00:07:51.910 --> 00:07:54.990 align:start position:0% constraints on the people in that multisig<00:07:53.370> specifically<00:07:54.370> that<00:07:54.580> you<00:07:54.850> don't 00:07:54.990 --> 00:07:55.000 align:start position:0% multisig specifically that you don't 00:07:55.000 --> 00:07:56.460 align:start position:0% multisig specifically that you don't want<00:07:55.120> them<00:07:55.210> to<00:07:55.330> be<00:07:55.419> able<00:07:55.479> to<00:07:55.720> get<00:07:55.840> grants<00:07:56.290> from 00:07:56.460 --> 00:07:56.470 align:start position:0% want them to be able to get grants from 00:07:56.470 --> 00:07:58.350 align:start position:0% want them to be able to get grants from the<00:07:56.800> auction<00:07:57.490> if<00:07:57.700> they're<00:07:57.910> part<00:07:58.120> of<00:07:58.240> their 00:07:58.350 --> 00:07:58.360 align:start position:0% the auction if they're part of their 00:07:58.360 --> 00:08:00.210 align:start position:0% the auction if they're part of their multi-sig<00:07:58.810> and<00:07:59.020> even<00:07:59.530> farther<00:07:59.680> than<00:07:59.890> that<00:07:59.950> you 00:08:00.210 --> 00:08:00.220 align:start position:0% multi-sig and even farther than that you 00:08:00.220 --> 00:08:01.350 align:start position:0% multi-sig and even farther than that you probably<00:08:00.460> don't<00:08:00.640> want<00:08:00.760> anyone<00:08:01.120> from<00:08:01.210> the 00:08:01.350 --> 00:08:01.360 align:start position:0% probably don't want anyone from the 00:08:01.360 --> 00:08:03.150 align:start position:0% probably don't want anyone from the organization's<00:08:01.990> to<00:08:02.200> apply<00:08:02.470> for<00:08:02.650> a<00:08:02.680> grant<00:08:02.890> if 00:08:03.150 --> 00:08:03.160 align:start position:0% organization's to apply for a grant if 00:08:03.160 --> 00:08:05.460 align:start position:0% organization's to apply for a grant if they<00:08:03.340> control<00:08:03.640> the<00:08:03.760> keys<00:08:03.940> to<00:08:04.120> the<00:08:04.210> funds<00:08:04.470> so 00:08:05.460 --> 00:08:05.470 align:start position:0% they control the keys to the funds so 00:08:05.470 --> 00:08:07.320 align:start position:0% they control the keys to the funds so for<00:08:05.620> example<00:08:05.979> if<00:08:06.220> basu<00:08:06.700> which<00:08:06.940> is<00:08:07.060> the<00:08:07.150> team 00:08:07.320 --> 00:08:07.330 align:start position:0% for example if basu which is the team 00:08:07.330 --> 00:08:09.330 align:start position:0% for example if basu which is the team that<00:08:07.360> I'm<00:08:07.600> on<00:08:07.750> was<00:08:08.289> part<00:08:08.530> of<00:08:08.590> the<00:08:08.830> multi-sig 00:08:09.330 --> 00:08:09.340 align:start position:0% that I'm on was part of the multi-sig 00:08:09.340 --> 00:08:10.770 align:start position:0% that I'm on was part of the multi-sig for<00:08:09.520> Berlin<00:08:09.850> which<00:08:10.150> is<00:08:10.270> the<00:08:10.390> next<00:08:10.600> upgrade 00:08:10.770 --> 00:08:10.780 align:start position:0% for Berlin which is the next upgrade 00:08:10.780 --> 00:08:13.170 align:start position:0% for Berlin which is the next upgrade after<00:08:11.110> Istanbul<00:08:11.740> that<00:08:12.220> no<00:08:12.370> one<00:08:12.520> from<00:08:12.640> Pegasus 00:08:13.170 --> 00:08:13.180 align:start position:0% after Istanbul that no one from Pegasus 00:08:13.180 --> 00:08:15.060 align:start position:0% after Istanbul that no one from Pegasus which<00:08:13.510> is<00:08:13.660> the<00:08:13.750> company<00:08:14.080> I<00:08:14.110> work<00:08:14.350> for<00:08:14.380> should 00:08:15.060 --> 00:08:15.070 align:start position:0% which is the company I work for should 00:08:15.070 --> 00:08:16.890 align:start position:0% which is the company I work for should be<00:08:15.100> able<00:08:15.250> to<00:08:15.430> apply<00:08:15.610> for<00:08:15.700> a<00:08:15.880> grant<00:08:16.120> for<00:08:16.660> funds 00:08:16.890 --> 00:08:16.900 align:start position:0% be able to apply for a grant for funds 00:08:16.900 --> 00:08:22.200 align:start position:0% be able to apply for a grant for funds from<00:08:17.530> funds<00:08:17.830> raised<00:08:18.310> during<00:08:18.669> that<00:08:18.789> auction<00:08:20.789> um 00:08:22.200 --> 00:08:22.210 align:start position:0% from funds raised during that auction um 00:08:22.210 --> 00:08:25.170 align:start position:0% from funds raised during that auction um and<00:08:22.630> so<00:08:23.500> one<00:08:24.100> interesting<00:08:24.310> question<00:08:24.640> here<00:08:25.000> is 00:08:25.170 --> 00:08:25.180 align:start position:0% and so one interesting question here is 00:08:25.180 --> 00:08:26.820 align:start position:0% and so one interesting question here is like<00:08:25.360> whether<00:08:25.750> you<00:08:25.870> actually<00:08:26.020> named<00:08:26.380> the<00:08:26.650> hard 00:08:26.820 --> 00:08:26.830 align:start position:0% like whether you actually named the hard 00:08:26.830 --> 00:08:29.279 align:start position:0% like whether you actually named the hard fork<00:08:27.039> so<00:08:28.030> I<00:08:28.060> have<00:08:28.270> a<00:08:28.300> couple<00:08:28.510> proposals<00:08:28.810> for 00:08:29.279 --> 00:08:29.289 align:start position:0% fork so I have a couple proposals for 00:08:29.289 --> 00:08:31.310 align:start position:0% fork so I have a couple proposals for what<00:08:29.320> would<00:08:29.590> be<00:08:29.710> okay<00:08:30.160> or<00:08:30.370> not<00:08:30.550> okay<00:08:30.610> for<00:08:31.090> names 00:08:31.310 --> 00:08:31.320 align:start position:0% what would be okay or not okay for names 00:08:31.320 --> 00:08:33.329 align:start position:0% what would be okay or not okay for names obviously<00:08:32.320> this<00:08:32.440> is<00:08:32.620> something<00:08:32.650> you'd<00:08:33.130> want 00:08:33.329 --> 00:08:33.339 align:start position:0% obviously this is something you'd want 00:08:33.339 --> 00:08:35.130 align:start position:0% obviously this is something you'd want to<00:08:33.430> prove<00:08:33.580> by<00:08:33.880> the<00:08:33.940> community<00:08:34.450> and<00:08:34.690> you'd<00:08:34.990> want 00:08:35.130 --> 00:08:35.140 align:start position:0% to prove by the community and you'd want 00:08:35.140 --> 00:08:37.500 align:start position:0% to prove by the community and you'd want to<00:08:35.260> discuss<00:08:35.669> and<00:08:36.669> more<00:08:36.880> specifically<00:08:37.300> you 00:08:37.500 --> 00:08:37.510 align:start position:0% to discuss and more specifically you 00:08:37.510 --> 00:08:39.149 align:start position:0% to discuss and more specifically you probably<00:08:37.780> want<00:08:37.960> to<00:08:38.020> have<00:08:38.080> a<00:08:38.200> process<00:08:38.469> where<00:08:38.890> at 00:08:39.149 --> 00:08:39.159 align:start position:0% probably want to have a process where at 00:08:39.159 --> 00:08:41.159 align:start position:0% probably want to have a process where at least<00:08:39.520> one<00:08:39.669> person<00:08:40.150> on<00:08:40.180> a<00:08:40.270> bottie<00:08:40.450> sig<00:08:40.750> has<00:08:41.020> to 00:08:41.159 --> 00:08:41.169 align:start position:0% least one person on a bottie sig has to 00:08:41.169 --> 00:08:43.020 align:start position:0% least one person on a bottie sig has to approve<00:08:41.380> of<00:08:41.440> a<00:08:41.620> name<00:08:41.800> for<00:08:42.280> a<00:08:42.339> bid<00:08:42.490> to<00:08:42.610> be<00:08:42.729> valid 00:08:43.020 --> 00:08:43.030 align:start position:0% approve of a name for a bid to be valid 00:08:43.030 --> 00:08:45.720 align:start position:0% approve of a name for a bid to be valid so<00:08:43.470> some<00:08:44.470> couple<00:08:44.710> ideas<00:08:44.830> of<00:08:45.070> what's<00:08:45.190> okay<00:08:45.280> just 00:08:45.720 --> 00:08:45.730 align:start position:0% so some couple ideas of what's okay just 00:08:45.730 --> 00:08:47.550 align:start position:0% so some couple ideas of what's okay just like<00:08:45.820> some<00:08:45.970> generic<00:08:46.390> words<00:08:46.600> you<00:08:47.140> don't<00:08:47.260> want 00:08:47.550 --> 00:08:47.560 align:start position:0% like some generic words you don't want 00:08:47.560 --> 00:08:50.400 align:start position:0% like some generic words you don't want bad<00:08:47.890> stuff<00:08:48.339> no<00:08:48.820> offensive<00:08:49.270> stuff<00:08:49.480> and 00:08:50.400 --> 00:08:50.410 align:start position:0% bad stuff no offensive stuff and 00:08:50.410 --> 00:08:51.750 align:start position:0% bad stuff no offensive stuff and probably<00:08:50.920> just<00:08:50.980> like<00:08:51.220> not<00:08:51.490> anything 00:08:51.750 --> 00:08:51.760 align:start position:0% probably just like not anything 00:08:51.760 --> 00:08:54.650 align:start position:0% probably just like not anything confusing<00:08:52.390> so<00:08:52.720> no<00:08:52.870> previous<00:08:53.290> upgrade<00:08:53.709> names 00:08:54.650 --> 00:08:54.660 align:start position:0% confusing so no previous upgrade names 00:08:54.660 --> 00:08:57.540 align:start position:0% confusing so no previous upgrade names no<00:08:55.660> other<00:08:56.230> blockchain<00:08:56.830> name<00:08:57.040> so<00:08:57.280> it<00:08:57.339> would<00:08:57.459> be 00:08:57.540 --> 00:08:57.550 align:start position:0% no other blockchain name so it would be 00:08:57.550 --> 00:08:59.100 align:start position:0% no other blockchain name so it would be kind<00:08:57.730> of<00:08:57.760> awkward<00:08:57.880> if<00:08:58.240> you<00:08:58.330> had<00:08:58.480> like<00:08:58.630> the 00:08:59.100 --> 00:08:59.110 align:start position:0% kind of awkward if you had like the 00:08:59.110 --> 00:09:02.400 align:start position:0% kind of awkward if you had like the et<00:08:59.350> see<00:08:59.529> if<00:08:59.769> they're<00:08:59.950> up<00:09:00.070> grade<00:09:00.420> and<00:09:01.420> generally 00:09:02.400 --> 00:09:02.410 align:start position:0% et see if they're up grade and generally 00:09:02.410 --> 00:09:04.680 align:start position:0% et see if they're up grade and generally like<00:09:02.860> something<00:09:03.579> that<00:09:03.820> you<00:09:04.180> would<00:09:04.329> be<00:09:04.450> okay 00:09:04.680 --> 00:09:04.690 align:start position:0% like something that you would be okay 00:09:04.690 --> 00:09:06.660 align:start position:0% like something that you would be okay sponsoring<00:09:05.110> Def<00:09:05.290> Con<00:09:05.500> would<00:09:06.130> probably<00:09:06.519> be<00:09:06.640> a 00:09:06.660 --> 00:09:06.670 align:start position:0% sponsoring Def Con would probably be a 00:09:06.670 --> 00:09:09.750 align:start position:0% sponsoring Def Con would probably be a good<00:09:06.880> a<00:09:07.120> good<00:09:07.360> name<00:09:07.540> there<00:09:08.040> and<00:09:09.040> finally<00:09:09.519> if 00:09:09.750 --> 00:09:09.760 align:start position:0% good a good name there and finally if 00:09:09.760 --> 00:09:11.370 align:start position:0% good a good name there and finally if you<00:09:10.060> don't<00:09:10.240> raise<00:09:10.630> any<00:09:10.839> money<00:09:10.959> during<00:09:11.200> this 00:09:11.370 --> 00:09:11.380 align:start position:0% you don't raise any money during this 00:09:11.380 --> 00:09:12.990 align:start position:0% you don't raise any money during this auction<00:09:11.680> that<00:09:11.980> we<00:09:12.100> could<00:09:12.250> just<00:09:12.579> revert<00:09:12.850> back 00:09:12.990 --> 00:09:13.000 align:start position:0% auction that we could just revert back 00:09:13.000 --> 00:09:15.240 align:start position:0% auction that we could just revert back to<00:09:13.209> using<00:09:13.360> Def<00:09:13.930> Con<00:09:14.140> city<00:09:14.410> names<00:09:14.589> which<00:09:15.130> is 00:09:15.240 --> 00:09:15.250 align:start position:0% to using Def Con city names which is 00:09:15.250 --> 00:09:16.710 align:start position:0% to using Def Con city names which is what<00:09:15.370> we<00:09:15.490> started<00:09:15.790> doing<00:09:15.850> informally<00:09:16.510> past 00:09:16.710 --> 00:09:16.720 align:start position:0% what we started doing informally past 00:09:16.720 --> 00:09:21.360 align:start position:0% what we started doing informally past Istanbul<00:09:18.480> so<00:09:19.480> that's<00:09:19.630> what<00:09:19.720> I<00:09:19.779> had<00:09:19.930> I<00:09:20.829> have 00:09:21.360 --> 00:09:21.370 align:start position:0% Istanbul so that's what I had I have 00:09:21.370 --> 00:09:22.680 align:start position:0% Istanbul so that's what I had I have like<00:09:21.519> a<00:09:21.550> minute<00:09:21.760> left<00:09:22.000> if<00:09:22.269> anyone<00:09:22.540> has<00:09:22.660> a 00:09:22.680 --> 00:09:22.690 align:start position:0% like a minute left if anyone has a 00:09:22.690 --> 00:09:30.060 align:start position:0% like a minute left if anyone has a question<00:09:22.779> okay<00:09:25.680> thanks<00:09:26.680> everybody<00:09:29.070> hello 00:09:30.060 --> 00:09:30.070 align:start position:0% question okay thanks everybody hello 00:09:30.070 --> 00:09:33.240 align:start position:0% question okay thanks everybody hello everyone<00:09:30.990> this<00:09:31.990> is<00:09:32.050> whom<00:09:32.380> and<00:09:32.589> Franklin<00:09:33.070> time 00:09:33.240 --> 00:09:33.250 align:start position:0% everyone this is whom and Franklin time 00:09:33.250 --> 00:09:35.220 align:start position:0% everyone this is whom and Franklin time with<00:09:33.459> Gartner<00:09:33.910> so<00:09:34.209> in<00:09:34.480> this<00:09:34.660> session<00:09:34.839> I<00:09:35.050> want 00:09:35.220 --> 00:09:35.230 align:start position:0% with Gartner so in this session I want 00:09:35.230 --> 00:09:36.600 align:start position:0% with Gartner so in this session I want to<00:09:35.410> share<00:09:35.649> with<00:09:35.829> you<00:09:35.950> some<00:09:36.160> end-user 00:09:36.600 --> 00:09:36.610 align:start position:0% to share with you some end-user 00:09:36.610 --> 00:09:38.220 align:start position:0% to share with you some end-user perspective<00:09:36.910> you<00:09:37.510> know<00:09:37.600> that<00:09:37.810> hopefully 00:09:38.220 --> 00:09:38.230 align:start position:0% perspective you know that hopefully 00:09:38.230 --> 00:09:42.090 align:start position:0% perspective you know that hopefully helped<00:09:38.410> with<00:09:38.589> the<00:09:38.740> adoption<00:09:39.610> so<00:09:40.209> we<00:09:41.110> have<00:09:41.380> this 00:09:42.090 --> 00:09:42.100 align:start position:0% helped with the adoption so we have this 00:09:42.100 --> 00:09:44.250 align:start position:0% helped with the adoption so we have this basically<00:09:42.940> service<00:09:43.480> you<00:09:43.570> know<00:09:43.660> thousands<00:09:44.140> of 00:09:44.250 --> 00:09:44.260 align:start position:0% basically service you know thousands of 00:09:44.260 --> 00:09:46.920 align:start position:0% basically service you know thousands of inquiries<00:09:44.980> per<00:09:45.279> year<00:09:45.519> you<00:09:45.730> know<00:09:45.880> that<00:09:45.930> relates 00:09:46.920 --> 00:09:46.930 align:start position:0% inquiries per year you know that relates 00:09:46.930 --> 00:09:49.050 align:start position:0% inquiries per year you know that relates to<00:09:47.110> blockchain<00:09:47.620> and<00:09:47.829> pretty<00:09:48.490> much<00:09:48.640> half<00:09:48.880> of 00:09:49.050 --> 00:09:49.060 align:start position:0% to blockchain and pretty much half of 00:09:49.060 --> 00:09:51.750 align:start position:0% to blockchain and pretty much half of them<00:09:49.269> deals<00:09:50.170> with<00:09:50.500> you<00:09:50.800> know<00:09:50.920> selecting<00:09:51.670> a 00:09:51.750 --> 00:09:51.760 align:start position:0% them deals with you know selecting a 00:09:51.760 --> 00:09:54.780 align:start position:0% them deals with you know selecting a blockchain<00:09:52.029> platform<00:09:52.920> in<00:09:53.920> many<00:09:54.160> cases<00:09:54.579> we'll 00:09:54.780 --> 00:09:54.790 align:start position:0% blockchain platform in many cases we'll 00:09:54.790 --> 00:09:56.970 align:start position:0% blockchain platform in many cases we'll see<00:09:55.029> there<00:09:55.450> is<00:09:55.540> a<00:09:55.570> still<00:09:55.839> a<00:09:55.870> lot<00:09:56.110> of<00:09:56.260> confusion 00:09:56.970 --> 00:09:56.980 align:start position:0% see there is a still a lot of confusion 00:09:56.980 --> 00:10:00.540 align:start position:0% see there is a still a lot of confusion that<00:09:57.370> what<00:09:58.060> a<00:09:58.269> auction<00:09:59.230> platform<00:09:59.769> is<00:10:00.010> or<00:10:00.310> is 00:10:00.540 --> 00:10:00.550 align:start position:0% that what a auction platform is or is 00:10:00.550 --> 00:10:06.480 align:start position:0% that what a auction platform is or is not<00:10:00.880> so<00:10:01.680> and<00:10:02.680> that<00:10:03.130> really<00:10:03.430> play<00:10:04.209> into<00:10:05.490> the 00:10:06.480 --> 00:10:06.490 align:start position:0% not so and that really play into the 00:10:06.490 --> 00:10:08.840 align:start position:0% not so and that really play into the adoption<00:10:07.149> and<00:10:07.420> and<00:10:07.690> the<00:10:07.839> ease<00:10:08.050> of<00:10:08.079> you<00:10:08.440> know 00:10:08.840 --> 00:10:08.850 align:start position:0% adoption and and the ease of you know 00:10:08.850 --> 00:10:13.850 align:start position:0% adoption and and the ease of you know evaluating<00:10:09.850> a<00:10:09.970> platform<00:10:10.510> so<00:10:11.399> there<00:10:12.399> are<00:10:12.550> many 00:10:13.850 --> 00:10:13.860 align:start position:0% evaluating a platform so there are many 00:10:13.860 --> 00:10:16.980 align:start position:0% evaluating a platform so there are many there<00:10:14.860> are<00:10:14.920> many<00:10:15.130> different<00:10:16.089> definitions<00:10:16.120> you 00:10:16.980 --> 00:10:16.990 align:start position:0% there are many different definitions you 00:10:16.990 --> 00:10:18.470 align:start position:0% there are many different definitions you know<00:10:17.110> that<00:10:17.380> we<00:10:17.560> find<00:10:17.829> out<00:10:18.010> you<00:10:18.160> know 00:10:18.470 --> 00:10:18.480 align:start position:0% know that we find out you know 00:10:18.480 --> 00:10:20.130 align:start position:0% know that we find out you know unfortunately<00:10:19.480> some<00:10:19.660> of<00:10:19.810> them<00:10:19.959> really 00:10:20.130 --> 00:10:20.140 align:start position:0% unfortunately some of them really 00:10:20.140 --> 00:10:22.259 align:start position:0% unfortunately some of them really doesn't<00:10:20.589> make<00:10:20.709> sense<00:10:21.040> and<00:10:21.339> it<00:10:21.490> you<00:10:21.970> have<00:10:22.089> to 00:10:22.259 --> 00:10:22.269 align:start position:0% doesn't make sense and it you have to 00:10:22.269 --> 00:10:23.460 align:start position:0% doesn't make sense and it you have to spend<00:10:22.540> a<00:10:22.600> lot<00:10:22.750> of<00:10:22.810> time<00:10:23.140> you<00:10:23.170> know<00:10:23.440> for 00:10:23.460 --> 00:10:23.470 align:start position:0% spend a lot of time you know for 00:10:23.470 --> 00:10:25.590 align:start position:0% spend a lot of time you know for companies<00:10:24.310> to<00:10:24.459> first<00:10:24.730> of<00:10:24.850> all<00:10:24.940> define<00:10:25.120> a 00:10:25.590 --> 00:10:25.600 align:start position:0% companies to first of all define a 00:10:25.600 --> 00:10:27.689 align:start position:0% companies to first of all define a blogging<00:10:25.959> platform<00:10:26.199> what<00:10:26.860> it<00:10:27.040> constitutes 00:10:27.689 --> 00:10:27.699 align:start position:0% blogging platform what it constitutes 00:10:27.699 --> 00:10:31.110 align:start position:0% blogging platform what it constitutes and<00:10:28.110> take<00:10:29.110> the<00:10:29.230> next<00:10:29.620> step<00:10:29.949> to<00:10:30.250> start 00:10:31.110 --> 00:10:31.120 align:start position:0% and take the next step to start 00:10:31.120 --> 00:10:33.509 align:start position:0% and take the next step to start comparing<00:10:31.690> the<00:10:32.529> platform<00:10:33.040> which<00:10:33.190> is<00:10:33.339> out 00:10:33.509 --> 00:10:33.519 align:start position:0% comparing the platform which is out 00:10:33.519 --> 00:10:35.460 align:start position:0% comparing the platform which is out there<00:10:33.760> and<00:10:34.000> select<00:10:34.540> something<00:10:34.899> that<00:10:35.199> works 00:10:35.460 --> 00:10:35.470 align:start position:0% there and select something that works 00:10:35.470 --> 00:10:36.120 align:start position:0% there and select something that works for<00:10:35.680> them 00:10:36.120 --> 00:10:36.130 align:start position:0% for them 00:10:36.130 --> 00:10:38.960 align:start position:0% for them so<00:10:36.610> from<00:10:37.209> what<00:10:37.420> we<00:10:37.570> have<00:10:37.690> seen<00:10:37.930> obviously 00:10:38.960 --> 00:10:38.970 align:start position:0% so from what we have seen obviously 00:10:38.970 --> 00:10:42.150 align:start position:0% so from what we have seen obviously ethereum<00:10:39.970> in<00:10:40.089> hyper<00:10:40.300> ledger<00:10:40.660> fabric<00:10:41.620> are<00:10:41.800> the 00:10:42.150 --> 00:10:42.160 align:start position:0% ethereum in hyper ledger fabric are the 00:10:42.160 --> 00:10:44.189 align:start position:0% ethereum in hyper ledger fabric are the most<00:10:42.370> popular<00:10:42.880> one<00:10:43.089> but<00:10:43.300> I<00:10:43.449> have<00:10:43.600> to<00:10:43.779> say<00:10:43.959> that 00:10:44.189 --> 00:10:44.199 align:start position:0% most popular one but I have to say that 00:10:44.199 --> 00:10:46.769 align:start position:0% most popular one but I have to say that there<00:10:44.649> is<00:10:44.769> no<00:10:44.980> loyalty<00:10:45.370> to<00:10:46.209> any<00:10:46.449> of<00:10:46.600> these 00:10:46.769 --> 00:10:46.779 align:start position:0% there is no loyalty to any of these 00:10:46.779 --> 00:10:48.720 align:start position:0% there is no loyalty to any of these platforms<00:10:47.050> because<00:10:47.709> they<00:10:47.829> still<00:10:48.070> most<00:10:48.430> of<00:10:48.610> the 00:10:48.720 --> 00:10:48.730 align:start position:0% platforms because they still most of the 00:10:48.730 --> 00:10:51.300 align:start position:0% platforms because they still most of the organizations<00:10:49.449> are<00:10:49.630> testing<00:10:50.620> you<00:10:50.800> know<00:10:50.920> and 00:10:51.300 --> 00:10:51.310 align:start position:0% organizations are testing you know and 00:10:51.310 --> 00:10:53.730 align:start position:0% organizations are testing you know and and<00:10:51.579> going<00:10:51.910> through<00:10:52.149> proof<00:10:52.510> of<00:10:52.660> concept<00:10:53.140> or 00:10:53.730 --> 00:10:53.740 align:start position:0% and going through proof of concept or 00:10:53.740 --> 00:10:56.430 align:start position:0% and going through proof of concept or some<00:10:54.459> sort<00:10:54.699> of<00:10:54.820> limited<00:10:55.240> pilot<00:10:55.720> so<00:10:55.930> the<00:10:56.140> any 00:10:56.430 --> 00:10:56.440 align:start position:0% some sort of limited pilot so the any 00:10:56.440 --> 00:11:00.540 align:start position:0% some sort of limited pilot so the any decision<00:10:57.130> that<00:10:57.339> they<00:10:57.550> make<00:10:58.560> is<00:10:59.560> not<00:10:59.769> really<00:11:00.519> a 00:11:00.540 --> 00:11:00.550 align:start position:0% decision that they make is not really a 00:11:00.550 --> 00:11:02.670 align:start position:0% decision that they make is not really a strategic<00:11:00.820> one<00:11:01.329> so<00:11:01.570> in<00:11:01.720> a<00:11:01.810> couple<00:11:02.050> of<00:11:02.260> years<00:11:02.500> or 00:11:02.670 --> 00:11:02.680 align:start position:0% strategic one so in a couple of years or 00:11:02.680 --> 00:11:04.560 align:start position:0% strategic one so in a couple of years or one<00:11:02.860> year<00:11:02.890> you<00:11:03.250> know<00:11:03.370> they<00:11:03.970> may<00:11:04.120> switch<00:11:04.180> to 00:11:04.560 --> 00:11:04.570 align:start position:0% one year you know they may switch to 00:11:04.570 --> 00:11:07.019 align:start position:0% one year you know they may switch to another<00:11:04.690> platform<00:11:05.140> so<00:11:05.620> what<00:11:06.339> we<00:11:06.519> thought<00:11:06.760> you 00:11:07.019 --> 00:11:07.029 align:start position:0% another platform so what we thought you 00:11:07.029 --> 00:11:09.630 align:start position:0% another platform so what we thought you know<00:11:07.149> it<00:11:07.540> may<00:11:07.810> help<00:11:08.140> is<00:11:08.920> to<00:11:09.279> start 00:11:09.630 --> 00:11:09.640 align:start position:0% know it may help is to start 00:11:09.640 --> 00:11:12.430 align:start position:0% know it may help is to start establishing<00:11:10.000> a<00:11:10.829> functional<00:11:11.829> framework 00:11:12.430 --> 00:11:12.440 align:start position:0% establishing a functional framework 00:11:12.440 --> 00:11:14.550 align:start position:0% establishing a functional framework for<00:11:12.650> blocking<00:11:13.160> platforms<00:11:13.760> you<00:11:13.880> know<00:11:14.000> that 00:11:14.550 --> 00:11:14.560 align:start position:0% for blocking platforms you know that 00:11:14.560 --> 00:11:18.400 align:start position:0% for blocking platforms you know that helps<00:11:15.560> with<00:11:16.510> organizations<00:11:17.510> to<00:11:17.720> do<00:11:17.840> an<00:11:17.990> Apple 00:11:18.400 --> 00:11:18.410 align:start position:0% helps with organizations to do an Apple 00:11:18.410 --> 00:11:21.220 align:start position:0% helps with organizations to do an Apple to<00:11:18.650> Apple<00:11:18.800> comparison<00:11:19.520> of<00:11:20.230> different 00:11:21.220 --> 00:11:21.230 align:start position:0% to Apple comparison of different 00:11:21.230 --> 00:11:23.860 align:start position:0% to Apple comparison of different frameworks<00:11:21.800> or<00:11:22.310> platforms<00:11:22.850> out<00:11:22.970> there<00:11:23.210> which 00:11:23.860 --> 00:11:23.870 align:start position:0% frameworks or platforms out there which 00:11:23.870 --> 00:11:26.260 align:start position:0% frameworks or platforms out there which there<00:11:24.350> are<00:11:24.410> hundreds<00:11:24.830> of<00:11:24.980> them<00:11:25.270> they 00:11:26.260 --> 00:11:26.270 align:start position:0% there are hundreds of them they 00:11:26.270 --> 00:11:28.510 align:start position:0% there are hundreds of them they initially<00:11:26.990> come<00:11:27.200> to<00:11:27.440> us<00:11:27.590> and<00:11:27.890> say<00:11:28.100> okay<00:11:28.220> why 00:11:28.510 --> 00:11:28.520 align:start position:0% initially come to us and say okay why 00:11:28.520 --> 00:11:30.820 align:start position:0% initially come to us and say okay why don't<00:11:28.580> you<00:11:28.880> as<00:11:29.240> Gartner<00:11:29.720> go<00:11:30.080> create<00:11:30.350> a<00:11:30.440> Magic 00:11:30.820 --> 00:11:30.830 align:start position:0% don't you as Gartner go create a Magic 00:11:30.830 --> 00:11:33.340 align:start position:0% don't you as Gartner go create a Magic Quadrant<00:11:30.950> you<00:11:31.370> know<00:11:31.490> for<00:11:31.900> for<00:11:32.900> all<00:11:33.020> of<00:11:33.200> this 00:11:33.340 --> 00:11:33.350 align:start position:0% Quadrant you know for for all of this 00:11:33.350 --> 00:11:35.050 align:start position:0% Quadrant you know for for all of this platform<00:11:33.590> the<00:11:33.980> challenge<00:11:34.430> is<00:11:34.610> that<00:11:34.820> there's 00:11:35.050 --> 00:11:35.060 align:start position:0% platform the challenge is that there's 00:11:35.060 --> 00:11:37.510 align:start position:0% platform the challenge is that there's so<00:11:35.210> many<00:11:35.360> of<00:11:35.570> them<00:11:35.600> out<00:11:35.930> there<00:11:36.140> so<00:11:36.320> and<00:11:37.040> then 00:11:37.510 --> 00:11:37.520 align:start position:0% so many of them out there so and then 00:11:37.520 --> 00:11:39.790 align:start position:0% so many of them out there so and then they<00:11:37.640> are<00:11:37.760> changing<00:11:38.240> to<00:11:38.600> fans<00:11:38.900> in<00:11:39.170> terms<00:11:39.470> of 00:11:39.790 --> 00:11:39.800 align:start position:0% they are changing to fans in terms of 00:11:39.800 --> 00:11:42.400 align:start position:0% they are changing to fans in terms of you<00:11:39.980> know<00:11:40.300> all<00:11:41.300> the<00:11:41.570> improvements<00:11:41.840> that 00:11:42.400 --> 00:11:42.410 align:start position:0% you know all the improvements that 00:11:42.410 --> 00:11:44.050 align:start position:0% you know all the improvements that happening<00:11:42.860> so<00:11:42.890> it's<00:11:43.370> kind<00:11:43.610> of<00:11:43.670> working 00:11:44.050 --> 00:11:44.060 align:start position:0% happening so it's kind of working 00:11:44.060 --> 00:11:47.290 align:start position:0% happening so it's kind of working progress<00:11:44.300> so<00:11:45.110> that's<00:11:45.590> not<00:11:45.860> possible<00:11:46.220> so<00:11:47.000> what 00:11:47.290 --> 00:11:47.300 align:start position:0% progress so that's not possible so what 00:11:47.300 --> 00:11:50.380 align:start position:0% progress so that's not possible so what we<00:11:47.510> did<00:11:47.720> instead<00:11:47.930> we<00:11:48.470> created<00:11:49.460> this<00:11:49.640> framework 00:11:50.380 --> 00:11:50.390 align:start position:0% we did instead we created this framework 00:11:50.390 --> 00:11:54.130 align:start position:0% we did instead we created this framework that<00:11:51.320> pretty<00:11:51.770> much<00:11:52.010> covers<00:11:52.520> all<00:11:52.870> the<00:11:53.870> key 00:11:54.130 --> 00:11:54.140 align:start position:0% that pretty much covers all the key 00:11:54.140 --> 00:11:56.830 align:start position:0% that pretty much covers all the key functional<00:11:54.830> modules<00:11:55.100> from<00:11:55.700> smart<00:11:56.210> contracts 00:11:56.830 --> 00:11:56.840 align:start position:0% functional modules from smart contracts 00:11:56.840 --> 00:11:59.790 align:start position:0% functional modules from smart contracts node<00:11:57.110> management<00:11:57.830> the<00:11:58.460> core<00:11:58.700> blockchain 00:11:59.790 --> 00:11:59.800 align:start position:0% node management the core blockchain 00:11:59.800 --> 00:12:02.920 align:start position:0% node management the core blockchain transactions<00:12:00.910> infrastructure<00:12:01.910> and<00:12:02.210> more<00:12:02.780> and 00:12:02.920 --> 00:12:02.930 align:start position:0% transactions infrastructure and more and 00:12:02.930 --> 00:12:07.290 align:start position:0% transactions infrastructure and more and more<00:12:03.110> the<00:12:03.290> ecosystem<00:12:04.570> management<00:12:05.570> aspect<00:12:06.440> of 00:12:07.290 --> 00:12:07.300 align:start position:0% more the ecosystem management aspect of 00:12:07.300 --> 00:12:11.230 align:start position:0% more the ecosystem management aspect of blockchain<00:12:08.300> solution<00:12:08.840> so<00:12:09.550> so<00:12:10.550> basically<00:12:10.730> the 00:12:11.230 --> 00:12:11.240 align:start position:0% blockchain solution so so basically the 00:12:11.240 --> 00:12:12.850 align:start position:0% blockchain solution so so basically the idea<00:12:11.270> is<00:12:11.720> that<00:12:11.810> this<00:12:12.050> is<00:12:12.110> not<00:12:12.380> obviously 00:12:12.850 --> 00:12:12.860 align:start position:0% idea is that this is not obviously 00:12:12.860 --> 00:12:14.410 align:start position:0% idea is that this is not obviously perfect<00:12:13.430> you<00:12:13.550> know<00:12:13.670> we<00:12:13.850> are<00:12:13.910> going<00:12:14.090> to<00:12:14.180> improve 00:12:14.410 --> 00:12:14.420 align:start position:0% perfect you know we are going to improve 00:12:14.420 --> 00:12:16.810 align:start position:0% perfect you know we are going to improve it<00:12:14.630> over<00:12:14.720> time<00:12:14.870> but<00:12:15.320> the<00:12:15.440> idea<00:12:15.800> is<00:12:15.950> that<00:12:16.010> first 00:12:16.810 --> 00:12:16.820 align:start position:0% it over time but the idea is that first 00:12:16.820 --> 00:12:18.910 align:start position:0% it over time but the idea is that first of<00:12:17.030> all<00:12:17.180> they<00:12:17.360> get<00:12:17.600> an<00:12:17.750> understanding<00:12:18.080> what<00:12:18.890> a 00:12:18.910 --> 00:12:18.920 align:start position:0% of all they get an understanding what a 00:12:18.920 --> 00:12:23.080 align:start position:0% of all they get an understanding what a platform<00:12:20.110> is<00:12:21.110> and<00:12:21.620> then<00:12:22.220> they<00:12:22.460> start<00:12:22.730> asking 00:12:23.080 --> 00:12:23.090 align:start position:0% platform is and then they start asking 00:12:23.090 --> 00:12:26.230 align:start position:0% platform is and then they start asking the<00:12:23.180> right<00:12:23.210> question<00:12:23.840> so<00:12:24.110> for<00:12:24.920> every<00:12:25.400> of<00:12:25.700> these 00:12:26.230 --> 00:12:26.240 align:start position:0% the right question so for every of these 00:12:26.240 --> 00:12:28.960 align:start position:0% the right question so for every of these functional<00:12:27.050> modules<00:12:27.290> we<00:12:27.830> define<00:12:28.760> you<00:12:28.910> know 00:12:28.960 --> 00:12:28.970 align:start position:0% functional modules we define you know 00:12:28.970 --> 00:12:30.460 align:start position:0% functional modules we define you know what<00:12:29.240> it<00:12:29.420> is<00:12:29.630> you<00:12:29.930> know<00:12:30.020> and<00:12:30.170> then<00:12:30.290> we 00:12:30.460 --> 00:12:30.470 align:start position:0% what it is you know and then we 00:12:30.470 --> 00:12:32.620 align:start position:0% what it is you know and then we introduce<00:12:31.100> some<00:12:31.340> questions<00:12:31.880> that<00:12:32.090> they 00:12:32.620 --> 00:12:32.630 align:start position:0% introduce some questions that they 00:12:32.630 --> 00:12:36.520 align:start position:0% introduce some questions that they should<00:12:32.960> ask<00:12:33.520> so<00:12:34.520> if<00:12:34.880> you<00:12:35.630> add<00:12:35.900> them<00:12:36.110> up<00:12:36.260> it's 00:12:36.520 --> 00:12:36.530 align:start position:0% should ask so if you add them up it's 00:12:36.530 --> 00:12:39.070 align:start position:0% should ask so if you add them up it's about<00:12:36.770> hundred<00:12:37.220> forty<00:12:37.850> two<00:12:37.880> questions<00:12:38.840> you 00:12:39.070 --> 00:12:39.080 align:start position:0% about hundred forty two questions you 00:12:39.080 --> 00:12:41.710 align:start position:0% about hundred forty two questions you know<00:12:39.410> that<00:12:39.760> pretty<00:12:40.760> much<00:12:40.910> covers<00:12:41.180> you<00:12:41.540> know 00:12:41.710 --> 00:12:41.720 align:start position:0% know that pretty much covers you know 00:12:41.720 --> 00:12:44.140 align:start position:0% know that pretty much covers you know all<00:12:42.710> the<00:12:43.040> key<00:12:43.280> imports<00:12:43.760> and<00:12:43.880> you<00:12:44.030> know 00:12:44.140 --> 00:12:44.150 align:start position:0% all the key imports and you know 00:12:44.150 --> 00:12:46.630 align:start position:0% all the key imports and you know features<00:12:44.600> that<00:12:44.930> you<00:12:45.320> may<00:12:45.470> expect<00:12:45.890> from<00:12:46.580> a 00:12:46.630 --> 00:12:46.640 align:start position:0% features that you may expect from a 00:12:46.640 --> 00:12:49.960 align:start position:0% features that you may expect from a platform<00:12:46.970> some<00:12:47.570> of<00:12:47.720> them<00:12:48.430> may<00:12:49.430> be<00:12:49.490> applicable 00:12:49.960 --> 00:12:49.970 align:start position:0% platform some of them may be applicable 00:12:49.970 --> 00:12:52.780 align:start position:0% platform some of them may be applicable or<00:12:50.390> not<00:12:50.420> applicable<00:12:51.370> depending<00:12:52.370> to<00:12:52.490> the<00:12:52.610> use 00:12:52.780 --> 00:12:52.790 align:start position:0% or not applicable depending to the use 00:12:52.790 --> 00:12:57.880 align:start position:0% or not applicable depending to the use case<00:12:53.060> that<00:12:53.420> they<00:12:54.230> have<00:12:54.700> and<00:12:56.320> that<00:12:57.320> will<00:12:57.620> give 00:12:57.880 --> 00:12:57.890 align:start position:0% case that they have and that will give 00:12:57.890 --> 00:12:59.710 align:start position:0% case that they have and that will give them<00:12:58.100> hopefully<00:12:58.460> an<00:12:58.760> understanding<00:12:59.420> that<00:12:59.450> for 00:12:59.710 --> 00:12:59.720 align:start position:0% them hopefully an understanding that for 00:12:59.720 --> 00:13:01.900 align:start position:0% them hopefully an understanding that for example<00:12:59.990> what's<00:13:00.350> the<00:13:00.440> difference<00:13:00.860> if<00:13:01.400> they<00:13:01.670> go 00:13:01.900 --> 00:13:01.910 align:start position:0% example what's the difference if they go 00:13:01.910 --> 00:13:05.310 align:start position:0% example what's the difference if they go with<00:13:02.210> let's<00:13:03.200> say<00:13:03.440> if<00:13:04.010> they're<00:13:04.250> young<00:13:04.460> versus 00:13:05.310 --> 00:13:05.320 align:start position:0% with let's say if they're young versus 00:13:05.320 --> 00:13:11.110 align:start position:0% with let's say if they're young versus hadera<00:13:06.320> versus<00:13:07.310> fabric<00:13:07.850> or<00:13:08.270> dumb<00:13:09.040> and<00:13:10.040> some<00:13:10.940> of 00:13:11.110 --> 00:13:11.120 align:start position:0% hadera versus fabric or dumb and some of 00:13:11.120 --> 00:13:13.270 align:start position:0% hadera versus fabric or dumb and some of the<00:13:11.300> differences<00:13:12.050> you<00:13:12.290> know<00:13:12.440> will<00:13:12.770> come<00:13:12.980> up<00:13:13.160> in 00:13:13.270 --> 00:13:13.280 align:start position:0% the differences you know will come up in 00:13:13.280 --> 00:13:17.800 align:start position:0% the differences you know will come up in us<00:13:13.630> as<00:13:14.630> part<00:13:15.290> of<00:13:15.470> that<00:13:15.530> process<00:13:15.950> you<00:13:16.310> know<00:13:16.810> but 00:13:17.800 --> 00:13:17.810 align:start position:0% us as part of that process you know but 00:13:17.810 --> 00:13:19.840 align:start position:0% us as part of that process you know but this<00:13:18.110> story<00:13:18.350> doesn't<00:13:18.440> change<00:13:18.980> doesn't<00:13:19.520> end 00:13:19.840 --> 00:13:19.850 align:start position:0% this story doesn't change doesn't end 00:13:19.850 --> 00:13:23.800 align:start position:0% this story doesn't change doesn't end there<00:13:20.620> what<00:13:21.620> we<00:13:22.010> have<00:13:22.970> to<00:13:23.210> deal<00:13:23.390> with<00:13:23.420> you<00:13:23.750> know 00:13:23.800 --> 00:13:23.810 align:start position:0% there what we have to deal with you know 00:13:23.810 --> 00:13:25.689 align:start position:0% there what we have to deal with you know there's<00:13:24.110> a<00:13:24.200> lot<00:13:24.410> of<00:13:24.620> debates<00:13:24.980> around 00:13:25.689 --> 00:13:25.699 align:start position:0% there's a lot of debates around 00:13:25.699 --> 00:13:28.329 align:start position:0% there's a lot of debates around versus<00:13:26.389> you<00:13:26.629> know<00:13:26.660> enterprise<00:13:27.259> we<00:13:27.589> see<00:13:28.100> those 00:13:28.329 --> 00:13:28.339 align:start position:0% versus you know enterprise we see those 00:13:28.339 --> 00:13:32.079 align:start position:0% versus you know enterprise we see those are<00:13:28.579> the<00:13:28.609> two<00:13:28.999> key<00:13:30.189> patterns<00:13:31.189> in<00:13:31.369> terms<00:13:31.399> of<00:13:31.850> the 00:13:32.079 --> 00:13:32.089 align:start position:0% are the two key patterns in terms of the 00:13:32.089 --> 00:13:34.569 align:start position:0% are the two key patterns in terms of the design<00:13:32.569> of<00:13:32.600> these<00:13:32.989> platforms<00:13:33.230> we<00:13:34.220> see 00:13:34.569 --> 00:13:34.579 align:start position:0% design of these platforms we see 00:13:34.579 --> 00:13:36.699 align:start position:0% design of these platforms we see sometimes<00:13:35.059> people<00:13:35.809> try<00:13:35.989> to<00:13:36.109> differentiate 00:13:36.699 --> 00:13:36.709 align:start position:0% sometimes people try to differentiate 00:13:36.709 --> 00:13:38.470 align:start position:0% sometimes people try to differentiate these<00:13:37.069> platforms<00:13:37.639> in<00:13:37.730> a<00:13:37.819> much<00:13:38.029> more<00:13:38.209> granular 00:13:38.470 --> 00:13:38.480 align:start position:0% these platforms in a much more granular 00:13:38.480 --> 00:13:42.809 align:start position:0% these platforms in a much more granular way<00:13:38.989> but<00:13:39.970> the<00:13:40.970> lot<00:13:41.480> of<00:13:41.509> those<00:13:41.809> differences<00:13:42.470> we 00:13:42.809 --> 00:13:42.819 align:start position:0% way but the lot of those differences we 00:13:42.819 --> 00:13:45.549 align:start position:0% way but the lot of those differences we consider<00:13:43.819> them<00:13:44.059> as<00:13:44.179> configurable<00:13:45.019> features 00:13:45.549 --> 00:13:45.559 align:start position:0% consider them as configurable features 00:13:45.559 --> 00:13:48.879 align:start position:0% consider them as configurable features that<00:13:45.889> over<00:13:46.339> time<00:13:46.639> they<00:13:47.600> morph<00:13:47.959> into<00:13:48.290> the<00:13:48.589> same 00:13:48.879 --> 00:13:48.889 align:start position:0% that over time they morph into the same 00:13:48.889 --> 00:13:52.030 align:start position:0% that over time they morph into the same platform<00:13:50.019> that<00:13:51.019> that<00:13:51.049> we<00:13:51.470> have<00:13:51.649> and<00:13:51.889> even 00:13:52.030 --> 00:13:52.040 align:start position:0% platform that that we have and even 00:13:52.040 --> 00:13:55.059 align:start position:0% platform that that we have and even between<00:13:52.579> public<00:13:53.209> and<00:13:53.509> enterprise<00:13:54.079> we'll<00:13:54.829> see 00:13:55.059 --> 00:13:55.069 align:start position:0% between public and enterprise we'll see 00:13:55.069 --> 00:13:57.519 align:start position:0% between public and enterprise we'll see the<00:13:55.220> lines<00:13:55.459> will<00:13:55.759> start<00:13:55.939> lowering<00:13:56.749> over<00:13:57.290> time 00:13:57.519 --> 00:13:57.529 align:start position:0% the lines will start lowering over time 00:13:57.529 --> 00:13:59.439 align:start position:0% the lines will start lowering over time so<00:13:57.799> for<00:13:58.040> example<00:13:58.489> what's<00:13:58.699> happening<00:13:59.179> with<00:13:59.359> the 00:13:59.439 --> 00:13:59.449 align:start position:0% so for example what's happening with the 00:13:59.449 --> 00:14:03.159 align:start position:0% so for example what's happening with the tharam<00:13:59.839> 2.0<00:14:00.879> we<00:14:01.879> envision<00:14:02.809> you<00:14:02.959> know<00:14:02.989> an 00:14:03.159 --> 00:14:03.169 align:start position:0% tharam 2.0 we envision you know an 00:14:03.169 --> 00:14:04.989 align:start position:0% tharam 2.0 we envision you know an environment<00:14:03.769> that<00:14:03.829> you<00:14:03.949> can<00:14:04.069> define<00:14:04.549> a<00:14:04.609> shard 00:14:04.989 --> 00:14:04.999 align:start position:0% environment that you can define a shard 00:14:04.999 --> 00:14:08.169 align:start position:0% environment that you can define a shard you<00:14:05.359> fix<00:14:06.319> the<00:14:06.649> validators<00:14:07.399> for<00:14:07.639> that<00:14:07.819> those 00:14:08.169 --> 00:14:08.179 align:start position:0% you fix the validators for that those 00:14:08.179 --> 00:14:11.349 align:start position:0% you fix the validators for that those shards<00:14:08.540> and<00:14:08.869> eventually<00:14:09.439> use<00:14:10.009> the<00:14:10.339> some<00:14:11.119> sort 00:14:11.349 --> 00:14:11.359 align:start position:0% shards and eventually use the some sort 00:14:11.359 --> 00:14:12.970 align:start position:0% shards and eventually use the some sort of<00:14:11.480> gateway<00:14:11.779> you<00:14:12.230> know<00:14:12.379> to<00:14:12.439> interact<00:14:12.889> with 00:14:12.970 --> 00:14:12.980 align:start position:0% of gateway you know to interact with 00:14:12.980 --> 00:14:15.220 align:start position:0% of gateway you know to interact with beacon<00:14:13.459> chain<00:14:13.639> so<00:14:13.850> while<00:14:14.059> you<00:14:14.269> are<00:14:14.389> isolating 00:14:15.220 --> 00:14:15.230 align:start position:0% beacon chain so while you are isolating 00:14:15.230 --> 00:14:18.909 align:start position:0% beacon chain so while you are isolating your<00:14:15.529> shard<00:14:16.249> and<00:14:16.549> chain<00:14:16.850> you<00:14:17.739> have<00:14:18.739> the 00:14:18.909 --> 00:14:18.919 align:start position:0% your shard and chain you have the 00:14:18.919 --> 00:14:22.509 align:start position:0% your shard and chain you have the opportunity<00:14:19.579> to<00:14:19.879> connect<00:14:20.540> to<00:14:20.660> a<00:14:20.689> public<00:14:21.519> type 00:14:22.509 --> 00:14:22.519 align:start position:0% opportunity to connect to a public type 00:14:22.519 --> 00:14:26.139 align:start position:0% opportunity to connect to a public type of<00:14:22.730> you<00:14:22.819> know<00:14:22.850> platform<00:14:23.449> so<00:14:23.769> so<00:14:24.769> that's<00:14:25.149> so 00:14:26.139 --> 00:14:26.149 align:start position:0% of you know platform so so that's so 00:14:26.149 --> 00:14:28.329 align:start position:0% of you know platform so so that's so that's<00:14:26.419> that's<00:14:27.259> something<00:14:27.769> that<00:14:27.949> we<00:14:28.100> try<00:14:28.309> to 00:14:28.329 --> 00:14:28.339 align:start position:0% that's that's something that we try to 00:14:28.339 --> 00:14:31.840 align:start position:0% that's that's something that we try to convey<00:14:28.939> to<00:14:28.999> this<00:14:29.299> organization<00:14:30.289> not<00:14:31.279> to<00:14:31.489> too 00:14:31.840 --> 00:14:31.850 align:start position:0% convey to this organization not to too 00:14:31.850 --> 00:14:33.579 align:start position:0% convey to this organization not to too much<00:14:32.029> you<00:14:32.179> know<00:14:32.299> stock<00:14:32.600> with<00:14:32.839> having<00:14:33.199> a<00:14:33.319> shared 00:14:33.579 --> 00:14:33.589 align:start position:0% much you know stock with having a shared 00:14:33.589 --> 00:14:35.679 align:start position:0% much you know stock with having a shared ledger<00:14:33.859> looking<00:14:34.429> at<00:14:34.579> the<00:14:34.730> bigger<00:14:35.149> picture<00:14:35.269> of 00:14:35.679 --> 00:14:35.689 align:start position:0% ledger looking at the bigger picture of 00:14:35.689 --> 00:14:37.929 align:start position:0% ledger looking at the bigger picture of the<00:14:35.839> platform<00:14:36.529> like<00:14:36.739> the<00:14:36.949> crypto<00:14:37.309> economics 00:14:37.929 --> 00:14:37.939 align:start position:0% the platform like the crypto economics 00:14:37.939 --> 00:14:41.559 align:start position:0% the platform like the crypto economics you<00:14:38.119> know<00:14:38.859> embedded<00:14:39.859> native<00:14:40.279> you<00:14:40.459> know<00:14:40.579> token 00:14:41.559 --> 00:14:41.569 align:start position:0% you know embedded native you know token 00:14:41.569 --> 00:14:43.509 align:start position:0% you know embedded native you know token you<00:14:41.869> know<00:14:42.019> that<00:14:42.350> that's<00:14:42.589> established<00:14:42.919> in<00:14:43.399> the 00:14:43.509 --> 00:14:43.519 align:start position:0% you know that that's established in the 00:14:43.519 --> 00:14:45.699 align:start position:0% you know that that's established in the platform<00:14:44.029> that<00:14:44.269> the<00:14:44.559> coordination<00:14:45.559> and 00:14:45.699 --> 00:14:45.709 align:start position:0% platform that the coordination and 00:14:45.709 --> 00:14:47.409 align:start position:0% platform that the coordination and consensus<00:14:46.399> you<00:14:46.609> know<00:14:46.730> protocol<00:14:47.269> the 00:14:47.409 --> 00:14:47.419 align:start position:0% consensus you know protocol the 00:14:47.419 --> 00:14:50.559 align:start position:0% consensus you know protocol the importance<00:14:47.959> of<00:14:48.199> them<00:14:48.410> to<00:14:48.949> make<00:14:49.339> their<00:14:49.669> choice 00:14:50.559 --> 00:14:50.569 align:start position:0% importance of them to make their choice 00:14:50.569 --> 00:14:54.159 align:start position:0% importance of them to make their choice future-proof<00:14:51.559> over<00:14:51.889> time<00:14:52.129> but<00:14:53.089> in<00:14:53.600> addition 00:14:54.159 --> 00:14:54.169 align:start position:0% future-proof over time but in addition 00:14:54.169 --> 00:14:58.900 align:start position:0% future-proof over time but in addition to<00:14:54.709> that<00:14:54.859> we<00:14:55.759> think<00:14:56.889> the<00:14:57.889> organization's<00:14:58.699> need 00:14:58.900 --> 00:14:58.910 align:start position:0% to that we think the organization's need 00:14:58.910 --> 00:15:03.159 align:start position:0% to that we think the organization's need to<00:14:59.029> also<00:14:59.239> look<00:14:59.600> at<00:15:01.299> areas<00:15:02.299> beyond<00:15:02.749> just<00:15:02.959> having 00:15:03.159 --> 00:15:03.169 align:start position:0% to also look at areas beyond just having 00:15:03.169 --> 00:15:05.409 align:start position:0% to also look at areas beyond just having the<00:15:03.470> pure<00:15:04.069> blockchain<00:15:04.609> platform<00:15:05.119> and<00:15:05.299> that's 00:15:05.409 --> 00:15:05.419 align:start position:0% the pure blockchain platform and that's 00:15:05.419 --> 00:15:07.659 align:start position:0% the pure blockchain platform and that's you<00:15:05.720> know<00:15:05.749> things<00:15:06.109> like<00:15:06.429> decentralized<00:15:07.429> web 00:15:07.659 --> 00:15:07.669 align:start position:0% you know things like decentralized web 00:15:07.669 --> 00:15:10.299 align:start position:0% you know things like decentralized web at<00:15:08.629> Gartner<00:15:08.959> we<00:15:09.319> believe<00:15:09.619> that<00:15:09.829> interview 00:15:10.299 --> 00:15:10.309 align:start position:0% at Gartner we believe that interview 00:15:10.309 --> 00:15:12.460 align:start position:0% at Gartner we believe that interview ssin<00:15:10.459> of<00:15:10.609> decentralized<00:15:11.059> web<00:15:11.600> I<00:15:11.779> think<00:15:12.019> it's<00:15:12.350> a 00:15:12.460 --> 00:15:12.470 align:start position:0% ssin of decentralized web I think it's a 00:15:12.470 --> 00:15:15.090 align:start position:0% ssin of decentralized web I think it's a key<00:15:12.679> element<00:15:12.709> of<00:15:13.309> supporting<00:15:14.119> digital 00:15:15.090 --> 00:15:15.100 align:start position:0% key element of supporting digital 00:15:15.100 --> 00:15:18.309 align:start position:0% key element of supporting digital ecosystems<00:15:16.100> moving<00:15:16.879> forward<00:15:17.299> so<00:15:17.929> without 00:15:18.309 --> 00:15:18.319 align:start position:0% ecosystems moving forward so without 00:15:18.319 --> 00:15:20.979 align:start position:0% ecosystems moving forward so without having<00:15:18.919> that<00:15:19.489> fabric<00:15:20.149> you<00:15:20.179> know<00:15:20.449> to<00:15:20.509> do 00:15:20.979 --> 00:15:20.989 align:start position:0% having that fabric you know to do 00:15:20.989 --> 00:15:23.079 align:start position:0% having that fabric you know to do transfer<00:15:21.619> if<00:15:21.709> occation<00:15:22.220> between<00:15:22.609> all<00:15:22.759> sort<00:15:22.999> of 00:15:23.079 --> 00:15:23.089 align:start position:0% transfer if occation between all sort of 00:15:23.089 --> 00:15:26.349 align:start position:0% transfer if occation between all sort of entities<00:15:23.919> that<00:15:24.919> having<00:15:25.579> that<00:15:25.759> vision<00:15:26.119> of 00:15:26.349 --> 00:15:26.359 align:start position:0% entities that having that vision of 00:15:26.359 --> 00:15:28.539 align:start position:0% entities that having that vision of digitalization<00:15:26.959> in<00:15:27.559> the<00:15:27.649> ecosystem<00:15:28.309> was 00:15:28.539 --> 00:15:28.549 align:start position:0% digitalization in the ecosystem was 00:15:28.549 --> 00:15:31.239 align:start position:0% digitalization in the ecosystem was almost<00:15:28.970> impossible<00:15:29.179> so<00:15:29.839> so<00:15:30.499> decentralized 00:15:31.239 --> 00:15:31.249 align:start position:0% almost impossible so so decentralized 00:15:31.249 --> 00:15:32.919 align:start position:0% almost impossible so so decentralized web<00:15:31.429> is<00:15:31.579> coming<00:15:31.999> and<00:15:32.179> then<00:15:32.329> from<00:15:32.569> a<00:15:32.600> platform 00:15:32.919 --> 00:15:32.929 align:start position:0% web is coming and then from a platform 00:15:32.929 --> 00:15:34.899 align:start position:0% web is coming and then from a platform perspective<00:15:33.169> if<00:15:33.919> the<00:15:34.279> platform<00:15:34.489> has<00:15:34.879> a 00:15:34.899 --> 00:15:34.909 align:start position:0% perspective if the platform has a 00:15:34.909 --> 00:15:37.749 align:start position:0% perspective if the platform has a limited<00:15:35.449> vision<00:15:35.720> it<00:15:36.619> can<00:15:36.949> not<00:15:37.159> support<00:15:37.549> the 00:15:37.749 --> 00:15:37.759 align:start position:0% limited vision it can not support the 00:15:37.759 --> 00:15:39.550 align:start position:0% limited vision it can not support the centralized<00:15:38.299> web<00:15:38.569> so 00:15:39.550 --> 00:15:39.560 align:start position:0% centralized web so 00:15:39.560 --> 00:15:42.040 align:start position:0% centralized web so that's<00:15:40.100> another<00:15:40.519> lid<00:15:40.880> layer<00:15:41.390> that<00:15:41.690> needs<00:15:41.930> to 00:15:42.040 --> 00:15:42.050 align:start position:0% that's another lid layer that needs to 00:15:42.050 --> 00:15:45.430 align:start position:0% that's another lid layer that needs to be<00:15:42.110> factored<00:15:42.589> as<00:15:42.709> part<00:15:43.040> of<00:15:43.220> the<00:15:43.430> decision<00:15:44.440> so 00:15:45.430 --> 00:15:45.440 align:start position:0% be factored as part of the decision so 00:15:45.440 --> 00:15:48.069 align:start position:0% be factored as part of the decision so and<00:15:45.800> even<00:15:46.370> we<00:15:46.490> push<00:15:46.700> it<00:15:46.880> further<00:15:47.120> in<00:15:47.540> terms<00:15:47.810> of 00:15:48.069 --> 00:15:48.079 align:start position:0% and even we push it further in terms of 00:15:48.079 --> 00:15:50.380 align:start position:0% and even we push it further in terms of long<00:15:48.320> term<00:15:48.350> planning<00:15:49.040> like<00:15:49.250> 10<00:15:49.519> years<00:15:49.820> 15 00:15:50.380 --> 00:15:50.390 align:start position:0% long term planning like 10 years 15 00:15:50.390 --> 00:15:52.600 align:start position:0% long term planning like 10 years 15 years<00:15:50.420> down<00:15:50.899> the<00:15:51.079> road<00:15:51.110> this<00:15:51.950> concept<00:15:52.490> of 00:15:52.600 --> 00:15:52.610 align:start position:0% years down the road this concept of 00:15:52.610 --> 00:15:54.550 align:start position:0% years down the road this concept of worldwide<00:15:52.940> ledger<00:15:53.420> you<00:15:53.839> know<00:15:53.990> that<00:15:54.260> we<00:15:54.470> are 00:15:54.550 --> 00:15:54.560 align:start position:0% worldwide ledger you know that we are 00:15:54.560 --> 00:15:57.730 align:start position:0% worldwide ledger you know that we are going<00:15:54.769> to<00:15:54.890> have<00:15:55.420> any<00:15:56.420> kind<00:15:56.899> of<00:15:57.079> a<00:15:57.230> muted 00:15:57.730 --> 00:15:57.740 align:start position:0% going to have any kind of a muted 00:15:57.740 --> 00:16:01.780 align:start position:0% going to have any kind of a muted version<00:15:58.490> of<00:15:58.640> world<00:15:58.910> wide<00:15:59.120> web<00:15:59.450> that<00:16:00.790> basically 00:16:01.780 --> 00:16:01.790 align:start position:0% version of world wide web that basically 00:16:01.790 --> 00:16:04.000 align:start position:0% version of world wide web that basically connect<00:16:02.269> all<00:16:02.420> these<00:16:02.600> Ledger's<00:16:03.140> together<00:16:03.709> you 00:16:04.000 --> 00:16:04.010 align:start position:0% connect all these Ledger's together you 00:16:04.010 --> 00:16:06.190 align:start position:0% connect all these Ledger's together you know<00:16:04.130> with<00:16:04.370> new<00:16:04.640> type<00:16:04.880> of<00:16:05.209> identification 00:16:06.190 --> 00:16:06.200 align:start position:0% know with new type of identification 00:16:06.200 --> 00:16:10.120 align:start position:0% know with new type of identification metals<00:16:06.920> new<00:16:07.130> type<00:16:07.370> of<00:16:07.579> an<00:16:07.730> object<00:16:08.649> new<00:16:09.649> type<00:16:09.920> of 00:16:10.120 --> 00:16:10.130 align:start position:0% metals new type of an object new type of 00:16:10.130 --> 00:16:15.310 align:start position:0% metals new type of an object new type of protocols<00:16:10.790> that<00:16:11.140> we<00:16:12.140> try<00:16:12.440> to<00:16:12.470> convey<00:16:13.480> and<00:16:14.480> the 00:16:15.310 --> 00:16:15.320 align:start position:0% protocols that we try to convey and the 00:16:15.320 --> 00:16:19.389 align:start position:0% protocols that we try to convey and the whole<00:16:15.500> idea<00:16:15.950> is<00:16:15.980> to<00:16:17.380> help<00:16:18.380> the<00:16:18.620> organization's 00:16:19.389 --> 00:16:19.399 align:start position:0% whole idea is to help the organization's 00:16:19.399 --> 00:16:21.009 align:start position:0% whole idea is to help the organization's to<00:16:19.550> understand<00:16:20.149> you<00:16:20.300> know<00:16:20.420> where<00:16:20.660> are<00:16:20.839> we 00:16:21.009 --> 00:16:21.019 align:start position:0% to understand you know where are we 00:16:21.019 --> 00:16:22.540 align:start position:0% to understand you know where are we going<00:16:21.260> with<00:16:21.410> all<00:16:21.560> of<00:16:21.589> these<00:16:21.890> technologies 00:16:22.540 --> 00:16:22.550 align:start position:0% going with all of these technologies 00:16:22.550 --> 00:16:25.840 align:start position:0% going with all of these technologies sometimes<00:16:23.000> you<00:16:23.120> know<00:16:23.680> as<00:16:24.680> developers<00:16:25.550> we<00:16:25.730> may 00:16:25.840 --> 00:16:25.850 align:start position:0% sometimes you know as developers we may 00:16:25.850 --> 00:16:27.880 align:start position:0% sometimes you know as developers we may focus<00:16:26.120> too<00:16:26.510> much<00:16:26.540> on<00:16:26.839> the<00:16:26.899> bits<00:16:27.140> and<00:16:27.290> bytes<00:16:27.380> you 00:16:27.880 --> 00:16:27.890 align:start position:0% focus too much on the bits and bytes you 00:16:27.890 --> 00:16:30.250 align:start position:0% focus too much on the bits and bytes you know<00:16:28.010> and<00:16:28.190> miss<00:16:28.790> on<00:16:28.970> the<00:16:29.120> bigger<00:16:29.870> picture 00:16:30.250 --> 00:16:30.260 align:start position:0% know and miss on the bigger picture 00:16:30.260 --> 00:16:32.620 align:start position:0% know and miss on the bigger picture which<00:16:30.769> is<00:16:30.800> important<00:16:31.700> for<00:16:31.760> them<00:16:32.180> you<00:16:32.450> know<00:16:32.570> to 00:16:32.620 --> 00:16:32.630 align:start position:0% which is important for them you know to 00:16:32.630 --> 00:16:35.079 align:start position:0% which is important for them you know to build<00:16:32.930> the<00:16:33.140> case<00:16:33.410> to<00:16:34.220> adopt<00:16:34.610> this<00:16:34.820> type<00:16:35.060> of 00:16:35.079 --> 00:16:35.089 align:start position:0% build the case to adopt this type of 00:16:35.089 --> 00:16:37.720 align:start position:0% build the case to adopt this type of technology<00:16:35.600> so<00:16:36.140> so<00:16:36.890> that's<00:16:37.100> the<00:16:37.250> idea<00:16:37.370> you 00:16:37.720 --> 00:16:37.730 align:start position:0% technology so so that's the idea you 00:16:37.730 --> 00:16:40.240 align:start position:0% technology so so that's the idea you know<00:16:37.880> as<00:16:38.120> some<00:16:38.470> kind<00:16:39.470> of<00:16:39.680> you<00:16:39.860> know<00:16:39.980> hopefully 00:16:40.240 --> 00:16:40.250 align:start position:0% know as some kind of you know hopefully 00:16:40.250 --> 00:16:42.759 align:start position:0% know as some kind of you know hopefully pointers<00:16:41.180> you<00:16:41.209> know<00:16:41.420> as<00:16:41.630> you<00:16:41.810> want<00:16:42.019> building 00:16:42.759 --> 00:16:42.769 align:start position:0% pointers you know as you want building 00:16:42.769 --> 00:16:44.380 align:start position:0% pointers you know as you want building in<00:16:42.950> all<00:16:43.070> these<00:16:43.279> great<00:16:43.519> systems<00:16:43.760> you<00:16:44.180> know<00:16:44.329> to 00:16:44.380 --> 00:16:44.390 align:start position:0% in all these great systems you know to 00:16:44.390 --> 00:16:46.630 align:start position:0% in all these great systems you know to convey<00:16:45.050> it<00:16:45.110> in<00:16:45.260> a<00:16:45.380> way<00:16:45.529> that<00:16:45.560> they<00:16:46.040> can<00:16:46.310> relate 00:16:46.630 --> 00:16:46.640 align:start position:0% convey it in a way that they can relate 00:16:46.640 --> 00:16:49.269 align:start position:0% convey it in a way that they can relate to<00:16:46.699> and<00:16:46.990> adopt<00:16:47.990> it<00:16:48.170> over<00:16:48.410> time<00:16:48.589> that's<00:16:49.100> it 00:16:49.269 --> 00:16:49.279 align:start position:0% to and adopt it over time that's it 00:16:49.279 --> 00:16:54.730 align:start position:0% to and adopt it over time that's it thank<00:16:49.699> you<00:16:51.940> hi<00:16:52.940> everyone<00:16:53.360> and<00:16:53.959> welcome<00:16:54.019> to 00:16:54.730 --> 00:16:54.740 align:start position:0% thank you hi everyone and welcome to 00:16:54.740 --> 00:16:55.120 align:start position:0% thank you hi everyone and welcome to Japan 00:16:55.120 --> 00:16:55.130 align:start position:0% Japan 00:16:55.130 --> 00:16:57.579 align:start position:0% Japan my<00:16:56.029> name<00:16:56.209> is<00:16:56.360> you<00:16:56.570> know<00:16:56.690> scanner<00:16:56.959> Rama<00:16:57.260> I'm 00:16:57.579 --> 00:16:57.589 align:start position:0% my name is you know scanner Rama I'm 00:16:57.589 --> 00:17:00.550 align:start position:0% my name is you know scanner Rama I'm master<00:16:58.399> student<00:16:58.850> at<00:16:59.089> a<00:16:59.149> Tokyo<00:16:59.600> Institute<00:17:00.019> of 00:17:00.550 --> 00:17:00.560 align:start position:0% master student at a Tokyo Institute of 00:17:00.560 --> 00:17:03.280 align:start position:0% master student at a Tokyo Institute of Technology<00:17:01.240> today<00:17:02.240> I<00:17:02.269> would<00:17:02.570> like<00:17:02.779> to<00:17:03.019> talk 00:17:03.280 --> 00:17:03.290 align:start position:0% Technology today I would like to talk 00:17:03.290 --> 00:17:05.740 align:start position:0% Technology today I would like to talk about<00:17:03.649> network<00:17:04.579> simulator<00:17:05.000> called<00:17:05.329> shim 00:17:05.740 --> 00:17:05.750 align:start position:0% about network simulator called shim 00:17:05.750 --> 00:17:09.699 align:start position:0% about network simulator called shim brach<00:17:07.030> network<00:17:08.030> is<00:17:08.390> one<00:17:08.990> of<00:17:09.049> the<00:17:09.199> important 00:17:09.699 --> 00:17:09.709 align:start position:0% brach network is one of the important 00:17:09.709 --> 00:17:12.819 align:start position:0% brach network is one of the important theme<00:17:09.980> for<00:17:10.309> us<00:17:10.600> so<00:17:11.600> Brooke<00:17:12.020> Taney<00:17:12.199> is<00:17:12.380> based<00:17:12.650> on 00:17:12.819 --> 00:17:12.829 align:start position:0% theme for us so Brooke Taney is based on 00:17:12.829 --> 00:17:15.100 align:start position:0% theme for us so Brooke Taney is based on p2p<00:17:13.069> networks<00:17:13.790> so<00:17:14.150> it's<00:17:14.540> necessary<00:17:14.990> to 00:17:15.100 --> 00:17:15.110 align:start position:0% p2p networks so it's necessary to 00:17:15.110 --> 00:17:17.049 align:start position:0% p2p networks so it's necessary to consider<00:17:15.770> communication<00:17:16.579> within<00:17:16.819> the 00:17:17.049 --> 00:17:17.059 align:start position:0% consider communication within the 00:17:17.059 --> 00:17:21.789 align:start position:0% consider communication within the network<00:17:18.220> for<00:17:19.220> example<00:17:19.780> we<00:17:20.780> want<00:17:21.079> to<00:17:21.319> improve 00:17:21.789 --> 00:17:21.799 align:start position:0% network for example we want to improve 00:17:21.799 --> 00:17:24.069 align:start position:0% network for example we want to improve the<00:17:22.130> rope<00:17:22.669> chain<00:17:22.699> throughput<00:17:23.360> you<00:17:23.689> will 00:17:24.069 --> 00:17:24.079 align:start position:0% the rope chain throughput you will 00:17:24.079 --> 00:17:27.789 align:start position:0% the rope chain throughput you will increase<00:17:24.410> the<00:17:24.770> box<00:17:25.490> size<00:17:25.669> and<00:17:25.970> the<00:17:26.630> number<00:17:27.589> of 00:17:27.789 --> 00:17:27.799 align:start position:0% increase the box size and the number of 00:17:27.799 --> 00:17:32.400 align:start position:0% increase the box size and the number of rocks<00:17:28.040> generated<00:17:28.669> per<00:17:28.940> second<00:17:30.340> but<00:17:31.340> however 00:17:32.400 --> 00:17:32.410 align:start position:0% rocks generated per second but however 00:17:32.410 --> 00:17:35.950 align:start position:0% rocks generated per second but however this<00:17:33.429> increases<00:17:34.429> brach<00:17:34.940> propagation<00:17:35.600> delay 00:17:35.950 --> 00:17:35.960 align:start position:0% this increases brach propagation delay 00:17:35.960 --> 00:17:41.260 align:start position:0% this increases brach propagation delay and<00:17:36.640> shortens<00:17:37.640> approximation<00:17:38.480> time<00:17:39.250> so<00:17:40.270> then 00:17:41.260 --> 00:17:41.270 align:start position:0% and shortens approximation time so then 00:17:41.270 --> 00:17:44.799 align:start position:0% and shortens approximation time so then it's<00:17:41.679> it<00:17:42.679> becomes<00:17:43.010> difficult<00:17:43.640> to<00:17:43.940> synchronize 00:17:44.799 --> 00:17:44.809 align:start position:0% it's it becomes difficult to synchronize 00:17:44.809 --> 00:17:48.940 align:start position:0% it's it becomes difficult to synchronize prochain<00:17:45.530> in<00:17:46.280> network<00:17:46.760> and<00:17:47.470> toggle<00:17:48.470> the<00:17:48.710> chain 00:17:48.940 --> 00:17:48.950 align:start position:0% prochain in network and toggle the chain 00:17:48.950 --> 00:17:53.470 align:start position:0% prochain in network and toggle the chain folks<00:17:50.980> so<00:17:51.980> like<00:17:52.400> this 00:17:53.470 --> 00:17:53.480 align:start position:0% folks so like this 00:17:53.480 --> 00:17:56.080 align:start position:0% folks so like this network<00:17:54.289> communication<00:17:55.010> is<00:17:55.250> a<00:17:55.309> cause<00:17:55.789> of 00:17:56.080 --> 00:17:56.090 align:start position:0% network communication is a cause of 00:17:56.090 --> 00:17:59.140 align:start position:0% network communication is a cause of security<00:17:56.659> degradation<00:17:57.049> on<00:17:57.679> broad<00:17:58.010> chain<00:17:58.309> so 00:17:59.140 --> 00:17:59.150 align:start position:0% security degradation on broad chain so 00:17:59.150 --> 00:18:02.830 align:start position:0% security degradation on broad chain so we<00:17:59.179> research<00:17:59.870> the<00:18:00.880> improving<00:18:01.880> as<00:18:02.360> a<00:18:02.539> method 00:18:02.830 --> 00:18:02.840 align:start position:0% we research the improving as a method 00:18:02.840 --> 00:18:05.950 align:start position:0% we research the improving as a method for<00:18:03.080> improving<00:18:03.620> the<00:18:04.340> rock<00:18:05.270> chain<00:18:05.510> networks 00:18:05.950 --> 00:18:05.960 align:start position:0% for improving the rock chain networks 00:18:05.960 --> 00:18:09.430 align:start position:0% for improving the rock chain networks but<00:18:06.679> it's<00:18:07.190> difficult<00:18:07.760> to<00:18:08.179> experiment<00:18:08.990> with 00:18:09.430 --> 00:18:09.440 align:start position:0% but it's difficult to experiment with 00:18:09.440 --> 00:18:14.140 align:start position:0% but it's difficult to experiment with your<00:18:09.799> networks<00:18:11.020> so<00:18:12.020> we<00:18:12.260> we<00:18:12.799> derived<00:18:13.190> broken 00:18:14.140 --> 00:18:14.150 align:start position:0% your networks so we we derived broken 00:18:14.150 --> 00:18:17.919 align:start position:0% your networks so we we derived broken Network<00:18:14.570> Schmidt<00:18:14.929> so<00:18:15.919> and<00:18:16.669> we<00:18:17.000> we<00:18:17.510> call<00:18:17.750> it 00:18:17.919 --> 00:18:17.929 align:start position:0% Network Schmidt so and we we call it 00:18:17.929 --> 00:18:22.830 align:start position:0% Network Schmidt so and we we call it shim<00:18:18.260> broke<00:18:19.270> symbol<00:18:20.270> Schmidt<00:18:21.220> Rock<00:18:22.220> Gym 00:18:22.830 --> 00:18:22.840 align:start position:0% shim broke symbol Schmidt Rock Gym 00:18:22.840 --> 00:18:26.710 align:start position:0% shim broke symbol Schmidt Rock Gym protocols<00:18:23.840> and<00:18:24.080> Rock<00:18:24.620> propagation<00:18:25.720> by 00:18:26.710 --> 00:18:26.720 align:start position:0% protocols and Rock propagation by 00:18:26.720 --> 00:18:27.490 align:start position:0% protocols and Rock propagation by default 00:18:27.490 --> 00:18:27.500 align:start position:0% default 00:18:27.500 --> 00:18:30.520 align:start position:0% default Brockton<00:18:28.250> using<00:18:28.820> proof-of-work<00:18:29.390> and<00:18:29.960> longest 00:18:30.520 --> 00:18:30.530 align:start position:0% Brockton using proof-of-work and longest 00:18:30.530 --> 00:18:34.600 align:start position:0% Brockton using proof-of-work and longest through<00:18:30.820> on<00:18:31.820> random<00:18:32.780> networks<00:18:33.280> but<00:18:34.280> if<00:18:34.460> you 00:18:34.600 --> 00:18:34.610 align:start position:0% through on random networks but if you 00:18:34.610 --> 00:18:37.270 align:start position:0% through on random networks but if you want<00:18:34.820> to<00:18:35.000> test<00:18:35.750> you<00:18:35.990> a<00:18:36.020> new<00:18:36.230> idea<00:18:36.590> you<00:18:36.919> can 00:18:37.270 --> 00:18:37.280 align:start position:0% want to test you a new idea you can 00:18:37.280 --> 00:18:39.490 align:start position:0% want to test you a new idea you can design<00:18:37.610> an<00:18:37.909> order<00:18:38.179> behavior<00:18:38.690> network 00:18:39.490 --> 00:18:39.500 align:start position:0% design an order behavior network 00:18:39.500 --> 00:18:41.980 align:start position:0% design an order behavior network topology<00:18:40.070> and<00:18:40.280> network<00:18:40.940> configuration<00:18:41.720> to 00:18:41.980 --> 00:18:41.990 align:start position:0% topology and network configuration to 00:18:41.990 --> 00:18:46.600 align:start position:0% topology and network configuration to fit<00:18:42.169> your<00:18:42.320> ideas<00:18:43.059> and<00:18:44.710> you<00:18:45.710> can<00:18:45.890> get<00:18:46.100> the 00:18:46.600 --> 00:18:46.610 align:start position:0% fit your ideas and you can get the 00:18:46.610 --> 00:18:50.020 align:start position:0% fit your ideas and you can get the various<00:18:47.059> data<00:18:47.299> from<00:18:47.720> zimberg<00:18:48.520> this<00:18:49.520> data<00:18:49.760> can 00:18:50.020 --> 00:18:50.030 align:start position:0% various data from zimberg this data can 00:18:50.030 --> 00:18:52.930 align:start position:0% various data from zimberg this data can be<00:18:50.090> used<00:18:50.210> for<00:18:51.070> network<00:18:52.070> measurement<00:18:52.669> and 00:18:52.930 --> 00:18:52.940 align:start position:0% be used for network measurement and 00:18:52.940 --> 00:18:56.740 align:start position:0% be used for network measurement and attack<00:18:53.480> analysis<00:18:54.080> and<00:18:54.380> so<00:18:54.740> on<00:18:55.360> and<00:18:56.360> this 00:18:56.740 --> 00:18:56.750 align:start position:0% attack analysis and so on and this 00:18:56.750 --> 00:19:00.460 align:start position:0% attack analysis and so on and this distributor<00:18:57.620> was<00:18:57.830> used<00:18:58.130> for<00:18:58.690> some<00:18:59.690> experiment 00:19:00.460 --> 00:19:00.470 align:start position:0% distributor was used for some experiment 00:19:00.470 --> 00:19:03.820 align:start position:0% distributor was used for some experiment about<00:19:01.419> net<00:19:02.419> new<00:19:02.690> neighbor<00:19:03.289> selection 00:19:03.820 --> 00:19:03.830 align:start position:0% about net new neighbor selection 00:19:03.830 --> 00:19:06.850 align:start position:0% about net new neighbor selection algorithm<00:19:04.429> and<00:19:04.960> measuring<00:19:05.960> the<00:19:06.140> effect<00:19:06.530> of 00:19:06.850 --> 00:19:06.860 align:start position:0% algorithm and measuring the effect of 00:19:06.860 --> 00:19:13.289 align:start position:0% algorithm and measuring the effect of delay<00:19:07.429> networks<00:19:09.909> so<00:19:10.909> and<00:19:11.450> now<00:19:12.070> simple 00:19:13.289 --> 00:19:13.299 align:start position:0% delay networks so and now simple 00:19:13.299 --> 00:19:16.180 align:start position:0% delay networks so and now simple supports<00:19:14.299> Bitcoin<00:19:14.900> litecoin<00:19:15.230> and<00:19:15.890> those 00:19:16.180 --> 00:19:16.190 align:start position:0% supports Bitcoin litecoin and those 00:19:16.190 --> 00:19:19.480 align:start position:0% supports Bitcoin litecoin and those going<00:19:16.520> and<00:19:16.820> we<00:19:17.330> are<00:19:17.480> developing<00:19:17.690> for<00:19:18.490> Islam 00:19:19.480 --> 00:19:19.490 align:start position:0% going and we are developing for Islam 00:19:19.490 --> 00:19:23.200 align:start position:0% going and we are developing for Islam support<00:19:19.909> but<00:19:20.840> there<00:19:21.320> are<00:19:21.470> many<00:19:21.890> ISM<00:19:22.400> projects 00:19:23.200 --> 00:19:23.210 align:start position:0% support but there are many ISM projects 00:19:23.210 --> 00:19:28.390 align:start position:0% support but there are many ISM projects so<00:19:23.750> such<00:19:24.380> as<00:19:24.650> casbah<00:19:25.280> plasma<00:19:25.929> so<00:19:26.950> this<00:19:27.950> time<00:19:28.159> I 00:19:28.390 --> 00:19:28.400 align:start position:0% so such as casbah plasma so this time I 00:19:28.400 --> 00:19:31.120 align:start position:0% so such as casbah plasma so this time I should<00:19:28.520> meet<00:19:29.330> it<00:19:29.570> cost<00:19:29.929> on<00:19:30.230> Shem<00:19:30.620> broke<00:19:30.830> as<00:19:31.070> a 00:19:31.120 --> 00:19:31.130 align:start position:0% should meet it cost on Shem broke as a 00:19:31.130 --> 00:19:35.320 align:start position:0% should meet it cost on Shem broke as a sample<00:19:31.549> experiment<00:19:32.650> ghost<00:19:33.650> is<00:19:33.980> a<00:19:34.330> broad 00:19:35.320 --> 00:19:35.330 align:start position:0% sample experiment ghost is a broad 00:19:35.330 --> 00:19:38.380 align:start position:0% sample experiment ghost is a broad selection<00:19:35.650> protocol<00:19:36.650> the<00:19:37.429> current<00:19:37.850> a<00:19:38.059> certain 00:19:38.380 --> 00:19:38.390 align:start position:0% selection protocol the current a certain 00:19:38.390 --> 00:19:41.230 align:start position:0% selection protocol the current a certain protocol<00:19:38.809> sect<00:19:39.110> the<00:19:39.500> longest<00:19:40.070> chain<00:19:40.280> as<00:19:40.580> may 00:19:41.230 --> 00:19:41.240 align:start position:0% protocol sect the longest chain as may 00:19:41.240 --> 00:19:45.340 align:start position:0% protocol sect the longest chain as may chain<00:19:41.539> but<00:19:42.500> instead<00:19:43.120> ghost<00:19:44.120> X<00:19:44.539> the<00:19:45.049> heaviest 00:19:45.340 --> 00:19:45.350 align:start position:0% chain but instead ghost X the heaviest 00:19:45.350 --> 00:19:49.630 align:start position:0% chain but instead ghost X the heaviest chain<00:19:45.679> the<00:19:46.640> which<00:19:46.789> t<00:19:46.940> means<00:19:47.799> subtree<00:19:48.799> with<00:19:49.039> the 00:19:49.630 --> 00:19:49.640 align:start position:0% chain the which t means subtree with the 00:19:49.640 --> 00:19:53.560 align:start position:0% chain the which t means subtree with the most<00:19:49.880> blocks<00:19:50.530> so<00:19:51.530> I<00:19:51.559> try<00:19:51.950> to<00:19:52.419> measuring<00:19:53.419> the 00:19:53.560 --> 00:19:53.570 align:start position:0% most blocks so I try to measuring the 00:19:53.570 --> 00:19:56.020 align:start position:0% most blocks so I try to measuring the effect<00:19:53.960> of<00:19:54.200> ghost<00:19:54.590> protocol<00:19:55.190> against<00:19:55.730> surface 00:19:56.020 --> 00:19:56.030 align:start position:0% effect of ghost protocol against surface 00:19:56.030 --> 00:20:01.419 align:start position:0% effect of ghost protocol against surface mining<00:19:57.850> this<00:19:58.850> is<00:19:59.150> an<00:19:59.390> interim<00:19:59.840> result<00:20:00.429> the 00:20:01.419 --> 00:20:01.429 align:start position:0% mining this is an interim result the 00:20:01.429 --> 00:20:06.700 align:start position:0% mining this is an interim result the left<00:20:02.000> shorts<00:20:02.659> the<00:20:03.549> ratio<00:20:04.549> of<00:20:04.610> the<00:20:05.000> attackers 00:20:06.700 --> 00:20:06.710 align:start position:0% left shorts the ratio of the attackers 00:20:06.710 --> 00:20:09.310 align:start position:0% left shorts the ratio of the attackers in<00:20:07.100> main<00:20:07.310> chain<00:20:07.780> corresponding<00:20:08.780> to<00:20:08.990> the 00:20:09.310 --> 00:20:09.320 align:start position:0% in main chain corresponding to the 00:20:09.320 --> 00:20:12.820 align:start position:0% in main chain corresponding to the attackers<00:20:09.860> mining<00:20:10.520> power<00:20:10.990> this<00:20:11.990> shows<00:20:12.320> how 00:20:12.820 --> 00:20:12.830 align:start position:0% attackers mining power this shows how 00:20:12.830 --> 00:20:15.610 align:start position:0% attackers mining power this shows how much<00:20:12.890> mining<00:20:13.760> power<00:20:13.940> is<00:20:14.270> needed<00:20:14.540> for<00:20:14.990> surface 00:20:15.610 --> 00:20:15.620 align:start position:0% much mining power is needed for surface 00:20:15.620 --> 00:20:21.400 align:start position:0% much mining power is needed for surface mining<00:20:16.070> and<00:20:17.410> light<00:20:18.410> shows<00:20:18.800> the<00:20:20.410> average 00:20:21.400 --> 00:20:21.410 align:start position:0% mining and light shows the average 00:20:21.410 --> 00:20:25.420 align:start position:0% mining and light shows the average length<00:20:21.710> of<00:20:21.920> the<00:20:22.430> attack<00:20:23.230> chain<00:20:24.230> released<00:20:25.220> by 00:20:25.420 --> 00:20:25.430 align:start position:0% length of the attack chain released by 00:20:25.430 --> 00:20:30.370 align:start position:0% length of the attack chain released by the<00:20:25.490> article<00:20:27.190> this<00:20:28.190> is<00:20:28.250> related<00:20:29.180> to<00:20:29.210> the<00:20:30.140> safe 00:20:30.370 --> 00:20:30.380 align:start position:0% the article this is related to the safe 00:20:30.380 --> 00:20:35.020 align:start position:0% the article this is related to the safe number<00:20:30.620> of<00:20:30.920> Confirmation<00:20:32.350> this<00:20:34.030> emboss 00:20:35.020 --> 00:20:35.030 align:start position:0% number of Confirmation this emboss 00:20:35.030 --> 00:20:38.320 align:start position:0% number of Confirmation this emboss wizard<00:20:35.630> is<00:20:36.020> a<00:20:36.620> short<00:20:37.070> the<00:20:37.310> cost<00:20:37.580> is<00:20:37.970> better 00:20:38.320 --> 00:20:38.330 align:start position:0% wizard is a short the cost is better 00:20:38.330 --> 00:20:42.190 align:start position:0% wizard is a short the cost is better than<00:20:38.780> the<00:20:38.960> longer<00:20:39.320> sir<00:20:39.560> but<00:20:40.370> it's<00:20:40.820> not<00:20:41.180> as<00:20:41.600> much 00:20:42.190 --> 00:20:42.200 align:start position:0% than the longer sir but it's not as much 00:20:42.200 --> 00:20:46.800 align:start position:0% than the longer sir but it's not as much as<00:20:42.470> I<00:20:42.500> expected<00:20:43.600> this<00:20:44.600> is<00:20:44.870> probably<00:20:45.770> because 00:20:46.800 --> 00:20:46.810 align:start position:0% as I expected this is probably because 00:20:46.810 --> 00:20:52.990 align:start position:0% as I expected this is probably because assume<00:20:47.810> has<00:20:48.640> has<00:20:49.640> not<00:20:50.020> met<00:20:51.020> so<00:20:51.440> much<00:20:51.680> folks 00:20:52.990 --> 00:20:53.000 align:start position:0% assume has has not met so much folks 00:20:53.000 --> 00:21:01.480 align:start position:0% assume has has not met so much folks so<00:20:53.630> I<00:20:53.660> think<00:20:54.100> if<00:20:58.090> it<00:20:59.090> goes<00:20:59.450> is<00:20:59.750> better<00:21:00.530> a<00:21:00.890> more 00:21:01.480 --> 00:21:01.490 align:start position:0% so I think if it goes is better a more 00:21:01.490 --> 00:21:08.320 align:start position:0% so I think if it goes is better a more efficient<00:21:02.330> with<00:21:03.020> more<00:21:03.830> forked<00:21:04.820> rock<00:21:05.210> chain<00:21:07.330> so 00:21:08.320 --> 00:21:08.330 align:start position:0% efficient with more forked rock chain so 00:21:08.330 --> 00:21:11.770 align:start position:0% efficient with more forked rock chain so as<00:21:08.690> this<00:21:08.900> experiment<00:21:10.060> simple<00:21:11.060> will<00:21:11.270> help<00:21:11.600> you 00:21:11.770 --> 00:21:11.780 align:start position:0% as this experiment simple will help you 00:21:11.780 --> 00:21:15.000 align:start position:0% as this experiment simple will help you to<00:21:11.960> evaluate<00:21:12.560> some<00:21:13.370> certain<00:21:14.000> protocols 00:21:15.000 --> 00:21:15.010 align:start position:0% to evaluate some certain protocols 00:21:15.010 --> 00:21:21.220 align:start position:0% to evaluate some certain protocols please<00:21:16.010> try<00:21:16.840> simple<00:21:17.840> and<00:21:19.150> and<00:21:20.150> give<00:21:21.110> us 00:21:21.220 --> 00:21:21.230 align:start position:0% please try simple and and give us 00:21:21.230 --> 00:21:24.040 align:start position:0% please try simple and and give us feedback<00:21:21.670> you<00:21:22.670> if<00:21:22.910> you<00:21:23.030> if<00:21:23.780> you<00:21:23.990> are 00:21:24.040 --> 00:21:24.050 align:start position:0% feedback you if you if you are 00:21:24.050 --> 00:21:26.320 align:start position:0% feedback you if you if you are interested<00:21:24.320> in<00:21:24.890> the<00:21:25.190> shrimp<00:21:25.460> rock<00:21:25.640> you<00:21:26.090> can 00:21:26.320 --> 00:21:26.330 align:start position:0% interested in the shrimp rock you can 00:21:26.330 --> 00:21:28.810 align:start position:0% interested in the shrimp rock you can get<00:21:26.570> more<00:21:27.050> information<00:21:27.290> and<00:21:27.890> called<00:21:28.460> our 00:21:28.810 --> 00:21:28.820 align:start position:0% get more information and called our 00:21:28.820 --> 00:21:31.570 align:start position:0% get more information and called our website<00:21:29.450> or<00:21:29.750> github<00:21:30.340> thank<00:21:31.340> you<00:21:31.430> for 00:21:31.570 --> 00:21:31.580 align:start position:0% website or github thank you for 00:21:31.580 --> 00:21:33.940 align:start position:0% website or github thank you for listening<00:21:31.790> please<00:21:32.300> enjoy<00:21:32.960> the<00:21:33.320> pond<00:21:33.590> or<00:21:33.740> sack 00:21:33.940 --> 00:21:33.950 align:start position:0% listening please enjoy the pond or sack 00:21:33.950 --> 00:21:44.120 align:start position:0% listening please enjoy the pond or sack up 00:21:44.120 --> 00:21:44.130 align:start position:0% 00:21:44.130 --> 00:21:46.190 align:start position:0% you