WEBVTT Kind: captions Language: en 00:00:04.020 --> 00:00:06.389 align:start position:0% thank<00:00:05.020> you<00:00:05.170> guys<00:00:05.350> couples<00:00:05.920> come<00:00:06.100> for<00:00:06.279> this 00:00:06.389 --> 00:00:06.399 align:start position:0% thank you guys couples come for this 00:00:06.399 --> 00:00:08.250 align:start position:0% thank you guys couples come for this talk<00:00:06.640> when<00:00:07.120> I<00:00:07.149> want<00:00:07.330> to<00:00:07.390> present<00:00:07.660> about<00:00:07.750> today 00:00:08.250 --> 00:00:08.260 align:start position:0% talk when I want to present about today 00:00:08.260 --> 00:00:10.259 align:start position:0% talk when I want to present about today is<00:00:08.530> what<00:00:09.190> we've<00:00:09.309> been<00:00:09.340> building<00:00:09.820> for<00:00:09.940> the<00:00:10.059> past 00:00:10.259 --> 00:00:10.269 align:start position:0% is what we've been building for the past 00:00:10.269 --> 00:00:10.980 align:start position:0% is what we've been building for the past six<00:00:10.540> months 00:00:10.980 --> 00:00:10.990 align:start position:0% six months 00:00:10.990 --> 00:00:13.049 align:start position:0% six months a<00:00:11.249> financially<00:00:12.249> accountable<00:00:12.459> watching 00:00:13.049 --> 00:00:13.059 align:start position:0% a financially accountable watching 00:00:13.059 --> 00:00:14.999 align:start position:0% a financially accountable watching Network<00:00:13.389> and<00:00:13.749> this<00:00:13.959> is<00:00:14.110> in<00:00:14.230> calabria<00:00:14.740> some<00:00:14.919> of 00:00:14.999 --> 00:00:15.009 align:start position:0% Network and this is in calabria some of 00:00:15.009 --> 00:00:16.800 align:start position:0% Network and this is in calabria some of Chris<00:00:15.219> who's<00:00:15.400> in<00:00:15.519> the<00:00:15.610> audience<00:00:15.730> Sergey<00:00:16.660> and 00:00:16.800 --> 00:00:16.810 align:start position:0% Chris who's in the audience Sergey and 00:00:16.810 --> 00:00:17.550 align:start position:0% Chris who's in the audience Sergey and Salvatore 00:00:17.550 --> 00:00:17.560 align:start position:0% Salvatore 00:00:17.560 --> 00:00:19.020 align:start position:0% Salvatore I<00:00:17.590> wanna<00:00:18.130> what<00:00:18.310> I<00:00:18.340> really<00:00:18.640> want<00:00:18.789> to<00:00:18.880> highlight 00:00:19.020 --> 00:00:19.030 align:start position:0% I wanna what I really want to highlight 00:00:19.030 --> 00:00:20.550 align:start position:0% I wanna what I really want to highlight is<00:00:19.390> that<00:00:19.420> normally<00:00:19.930> when<00:00:20.020> people<00:00:20.290> think<00:00:20.410> of 00:00:20.550 --> 00:00:20.560 align:start position:0% is that normally when people think of 00:00:20.560 --> 00:00:22.740 align:start position:0% is that normally when people think of Pisa<00:00:20.830> they<00:00:21.490> think<00:00:21.700> of<00:00:21.790> all<00:00:21.970> team<00:00:22.180> protocols 00:00:22.740 --> 00:00:22.750 align:start position:0% Pisa they think of all team protocols 00:00:22.750 --> 00:00:24.660 align:start position:0% Pisa they think of all team protocols and<00:00:22.930> scalability<00:00:23.290> so<00:00:24.190> I've<00:00:24.250> actually<00:00:24.370> taken 00:00:24.660 --> 00:00:24.670 align:start position:0% and scalability so I've actually taken 00:00:24.670 --> 00:00:26.880 align:start position:0% and scalability so I've actually taken this<00:00:24.940> moment<00:00:25.390> where<00:00:25.780> this<00:00:25.990> talk<00:00:26.350> is<00:00:26.530> not<00:00:26.560> gonna 00:00:26.880 --> 00:00:26.890 align:start position:0% this moment where this talk is not gonna 00:00:26.890 --> 00:00:28.800 align:start position:0% this moment where this talk is not gonna have<00:00:27.070> anything<00:00:27.550> to<00:00:27.730> do<00:00:27.880> of<00:00:27.970> off<00:00:28.150> gym<00:00:28.330> protocols 00:00:28.800 --> 00:00:28.810 align:start position:0% have anything to do of off gym protocols 00:00:28.810 --> 00:00:31.080 align:start position:0% have anything to do of off gym protocols whatsoever<00:00:29.410> I<00:00:29.680> want<00:00:30.250> to<00:00:30.340> highlight<00:00:30.520> how<00:00:30.760> P's 00:00:31.080 --> 00:00:31.090 align:start position:0% whatsoever I want to highlight how P's 00:00:31.090 --> 00:00:32.700 align:start position:0% whatsoever I want to highlight how P's is<00:00:31.300> generally<00:00:31.750> useful<00:00:31.960> for<00:00:32.349> mousse<00:00:32.500> top 00:00:32.700 --> 00:00:32.710 align:start position:0% is generally useful for mousse top 00:00:32.710 --> 00:00:36.840 align:start position:0% is generally useful for mousse top developers<00:00:34.440> cool<00:00:35.440> now<00:00:36.190> when<00:00:36.310> I'm<00:00:36.400> gonna<00:00:36.550> begin 00:00:36.840 --> 00:00:36.850 align:start position:0% developers cool now when I'm gonna begin 00:00:36.850 --> 00:00:38.910 align:start position:0% developers cool now when I'm gonna begin with<00:00:37.060> is<00:00:37.240> actually<00:00:37.690> a<00:00:37.900> watching<00:00:38.440> network<00:00:38.740> is<00:00:38.890> a 00:00:38.910 --> 00:00:38.920 align:start position:0% with is actually a watching network is a 00:00:38.920 --> 00:00:41.040 align:start position:0% with is actually a watching network is a misnomer<00:00:39.510> there's<00:00:40.510> actually<00:00:40.810> two<00:00:41.020> different 00:00:41.040 --> 00:00:41.050 align:start position:0% misnomer there's actually two different 00:00:41.050 --> 00:00:44.130 align:start position:0% misnomer there's actually two different rules<00:00:41.650> in<00:00:42.070> this<00:00:42.730> third-party<00:00:43.140> Broadcasting 00:00:44.130 --> 00:00:44.140 align:start position:0% rules in this third-party Broadcasting 00:00:44.140 --> 00:00:47.040 align:start position:0% rules in this third-party Broadcasting Network<00:00:44.170> we<00:00:45.130> have<00:00:45.160> relators<00:00:46.000> where<00:00:46.690> our<00:00:46.840> meta 00:00:47.040 --> 00:00:47.050 align:start position:0% Network we have relators where our meta 00:00:47.050 --> 00:00:48.930 align:start position:0% Network we have relators where our meta transactions<00:00:47.829> you<00:00:48.489> know<00:00:48.579> you<00:00:48.640> give<00:00:48.910> a 00:00:48.930 --> 00:00:48.940 align:start position:0% transactions you know you give a 00:00:48.940 --> 00:00:51.060 align:start position:0% transactions you know you give a transaction<00:00:49.540> to<00:00:49.570> this<00:00:49.810> third<00:00:50.020> party<00:00:50.440> and<00:00:50.680> they 00:00:51.060 --> 00:00:51.070 align:start position:0% transaction to this third party and they 00:00:51.070 --> 00:00:52.800 align:start position:0% transaction to this third party and they guarantee<00:00:51.340> that<00:00:51.850> it<00:00:51.970> gets<00:00:52.120> relayed<00:00:52.420> to<00:00:52.690> the 00:00:52.800 --> 00:00:52.810 align:start position:0% guarantee that it gets relayed to the 00:00:52.810 --> 00:00:55.799 align:start position:0% guarantee that it gets relayed to the network<00:00:53.170> or<00:00:53.680> you<00:00:54.579> have<00:00:54.760> Watchers<00:00:55.270> you<00:00:55.690> know 00:00:55.799 --> 00:00:55.809 align:start position:0% network or you have Watchers you know 00:00:55.809 --> 00:00:58.380 align:start position:0% network or you have Watchers you know these<00:00:55.960> watch<00:00:56.170> towers<00:00:56.680> and<00:00:57.010> a<00:00:57.489> watch<00:00:57.700> tower<00:00:58.000> you 00:00:58.380 --> 00:00:58.390 align:start position:0% these watch towers and a watch tower you 00:00:58.390 --> 00:01:00.870 align:start position:0% these watch towers and a watch tower you can<00:00:58.420> be<00:00:58.660> hired<00:00:58.960> simply<00:00:59.710> the<00:00:59.980> watts<00:01:00.190> for<00:01:00.460> events 00:01:00.870 --> 00:01:00.880 align:start position:0% can be hired simply the watts for events 00:01:00.880 --> 00:01:03.209 align:start position:0% can be hired simply the watts for events on<00:01:01.000> the<00:01:01.120> blockchain<00:01:01.329> if<00:01:01.870> there's<00:01:02.469> an<00:01:02.590> event<00:01:02.920> it 00:01:03.209 --> 00:01:03.219 align:start position:0% on the blockchain if there's an event it 00:01:03.219 --> 00:01:05.670 align:start position:0% on the blockchain if there's an event it will<00:01:03.579> then<00:01:03.760> respond<00:01:04.149> in<00:01:04.299> your<00:01:04.420> behalf<00:01:04.689> so 00:01:05.670 --> 00:01:05.680 align:start position:0% will then respond in your behalf so 00:01:05.680 --> 00:01:07.560 align:start position:0% will then respond in your behalf so that's<00:01:05.890> why<00:01:06.070> it's<00:01:06.250> actually<00:01:06.430> a<00:01:06.729> third<00:01:07.240> party 00:01:07.560 --> 00:01:07.570 align:start position:0% that's why it's actually a third party 00:01:07.570 --> 00:01:09.330 align:start position:0% that's why it's actually a third party broadcast<00:01:08.080> network<00:01:08.530> which<00:01:08.770> sounds<00:01:09.070> really 00:01:09.330 --> 00:01:09.340 align:start position:0% broadcast network which sounds really 00:01:09.340 --> 00:01:11.670 align:start position:0% broadcast network which sounds really boring<00:01:09.610> you<00:01:09.850> know<00:01:09.880> lol<00:01:10.479> but<00:01:11.200> that's<00:01:11.380> actually 00:01:11.670 --> 00:01:11.680 align:start position:0% boring you know lol but that's actually 00:01:11.680 --> 00:01:14.940 align:start position:0% boring you know lol but that's actually what<00:01:11.799> it<00:01:11.830> is<00:01:12.720> so<00:01:13.720> why<00:01:13.900> do<00:01:13.960> we<00:01:14.110> have<00:01:14.200> you<00:01:14.799> know 00:01:14.940 --> 00:01:14.950 align:start position:0% what it is so why do we have you know 00:01:14.950 --> 00:01:18.360 align:start position:0% what it is so why do we have you know real<00:01:15.190> Ayres<00:01:15.430> and<00:01:15.580> responders<00:01:16.590> real<00:01:17.590> Ayres<00:01:17.890> try 00:01:18.360 --> 00:01:18.370 align:start position:0% real Ayres and responders real Ayres try 00:01:18.370 --> 00:01:20.430 align:start position:0% real Ayres and responders real Ayres try to<00:01:18.430> solve<00:01:18.790> the<00:01:18.970> problem<00:01:19.540> when<00:01:20.110> the<00:01:20.140> user 00:01:20.430 --> 00:01:20.440 align:start position:0% to solve the problem when the user 00:01:20.440 --> 00:01:22.740 align:start position:0% to solve the problem when the user doesn't<00:01:20.830> have<00:01:21.070> access<00:01:21.310> to<00:01:21.700> the<00:01:22.030> native<00:01:22.330> token 00:01:22.740 --> 00:01:22.750 align:start position:0% doesn't have access to the native token 00:01:22.750 --> 00:01:24.980 align:start position:0% doesn't have access to the native token so<00:01:23.350> this<00:01:23.440> could<00:01:23.619> be<00:01:23.710> onboarding<00:01:24.280> new<00:01:24.340> users 00:01:24.980 --> 00:01:24.990 align:start position:0% so this could be onboarding new users 00:01:24.990 --> 00:01:27.330 align:start position:0% so this could be onboarding new users accessing<00:01:25.990> coins<00:01:26.409> in<00:01:26.619> a<00:01:26.710> contract<00:01:27.190> like<00:01:27.310> a 00:01:27.330 --> 00:01:27.340 align:start position:0% accessing coins in a contract like a 00:01:27.340 --> 00:01:30.060 align:start position:0% accessing coins in a contract like a multi<00:01:27.760> sake<00:01:28.060> or<00:01:28.380> mixing<00:01:29.380> and<00:01:29.530> doubling<00:01:29.920> as 00:01:30.060 --> 00:01:30.070 align:start position:0% multi sake or mixing and doubling as 00:01:30.070 --> 00:01:33.240 align:start position:0% multi sake or mixing and doubling as well<00:01:30.360> where<00:01:31.360> watchtowers<00:01:32.260> and<00:01:32.560> responders 00:01:33.240 --> 00:01:33.250 align:start position:0% well where watchtowers and responders 00:01:33.250 --> 00:01:35.760 align:start position:0% well where watchtowers and responders they<00:01:33.820> try<00:01:34.119> to<00:01:34.180> alleviate<00:01:34.510> the<00:01:35.170> user<00:01:35.439> liveness 00:01:35.760 --> 00:01:35.770 align:start position:0% they try to alleviate the user liveness 00:01:35.770 --> 00:01:38.219 align:start position:0% they try to alleviate the user liveness requirement<00:01:36.640> that's<00:01:37.540> to<00:01:37.720> say<00:01:37.869> you<00:01:37.930> do<00:01:38.140> an 00:01:38.219 --> 00:01:38.229 align:start position:0% requirement that's to say you do an 00:01:38.229 --> 00:01:38.880 align:start position:0% requirement that's to say you do an auction 00:01:38.880 --> 00:01:38.890 align:start position:0% auction 00:01:38.890 --> 00:01:41.070 align:start position:0% auction you<00:01:39.100> know<00:01:39.220> you<00:01:39.280> submit<00:01:39.700> your<00:01:39.850> bid<00:01:40.090> three<00:01:40.900> days 00:01:41.070 --> 00:01:41.080 align:start position:0% you know you submit your bid three days 00:01:41.080 --> 00:01:43.050 align:start position:0% you know you submit your bid three days later<00:01:41.409> you<00:01:41.500> have<00:01:41.590> the<00:01:41.680> reveal<00:01:42.010> your<00:01:42.220> bid<00:01:42.460> and 00:01:43.050 --> 00:01:43.060 align:start position:0% later you have the reveal your bid and 00:01:43.060 --> 00:01:44.280 align:start position:0% later you have the reveal your bid and you<00:01:43.119> don't<00:01:43.299> want<00:01:43.450> to<00:01:43.510> come<00:01:43.659> online<00:01:43.810> in<00:01:44.080> three 00:01:44.280 --> 00:01:44.290 align:start position:0% you don't want to come online in three 00:01:44.290 --> 00:01:46.380 align:start position:0% you don't want to come online in three days<00:01:44.439> time<00:01:44.830> so<00:01:45.340> the<00:01:45.430> wast<00:01:45.610> Harkins<00:01:46.030> is<00:01:46.090> do<00:01:46.270> that 00:01:46.380 --> 00:01:46.390 align:start position:0% days time so the wast Harkins is do that 00:01:46.390 --> 00:01:48.330 align:start position:0% days time so the wast Harkins is do that in<00:01:46.509> your<00:01:46.630> behalf<00:01:46.960> of<00:01:47.229> course<00:01:48.040> the<00:01:48.159> main 00:01:48.330 --> 00:01:48.340 align:start position:0% in your behalf of course the main 00:01:48.340 --> 00:01:49.920 align:start position:0% in your behalf of course the main motivations<00:01:49.060> always<00:01:49.390> been<00:01:49.540> off<00:01:49.720> team 00:01:49.920 --> 00:01:49.930 align:start position:0% motivations always been off team 00:01:49.930 --> 00:01:51.990 align:start position:0% motivations always been off team protocols<00:01:50.500> like<00:01:50.680> plasma<00:01:50.979> and<00:01:51.250> steer<00:01:51.490> channels 00:01:51.990 --> 00:01:52.000 align:start position:0% protocols like plasma and steer channels 00:01:52.000 --> 00:01:53.789 align:start position:0% protocols like plasma and steer channels onion<00:01:52.840> also<00:01:53.020> to<00:01:53.200> date<00:01:53.380> availability 00:01:53.789 --> 00:01:53.799 align:start position:0% onion also to date availability 00:01:53.799 --> 00:01:57.270 align:start position:0% onion also to date availability providers<00:01:54.490> as<00:01:54.640> well<00:01:55.890> so<00:01:56.890> what<00:01:57.009> is<00:01:57.130> the 00:01:57.270 --> 00:01:57.280 align:start position:0% providers as well so what is the 00:01:57.280 --> 00:02:00.630 align:start position:0% providers as well so what is the perception<00:01:57.939> of<00:01:58.150> a<00:01:59.080> third-party<00:01:59.640> broadcasting 00:02:00.630 --> 00:02:00.640 align:start position:0% perception of a third-party broadcasting 00:02:00.640 --> 00:02:02.340 align:start position:0% perception of a third-party broadcasting network<00:02:00.939> you<00:02:01.180> know<00:02:01.299> how<00:02:01.420> do<00:02:01.479> people<00:02:01.900> typically 00:02:02.340 --> 00:02:02.350 align:start position:0% network you know how do people typically 00:02:02.350 --> 00:02:05.219 align:start position:0% network you know how do people typically think<00:02:02.470> about<00:02:02.770> it<00:02:03.130> in<00:02:03.310> their<00:02:03.490> protocols<00:02:04.229> well 00:02:05.219 --> 00:02:05.229 align:start position:0% think about it in their protocols well 00:02:05.229 --> 00:02:06.840 align:start position:0% think about it in their protocols well first<00:02:05.500> you<00:02:05.650> have<00:02:05.680> a<00:02:05.770> user<00:02:06.070> and<00:02:06.430> this<00:02:06.700> is<00:02:06.790> the 00:02:06.840 --> 00:02:06.850 align:start position:0% first you have a user and this is the 00:02:06.850 --> 00:02:09.509 align:start position:0% first you have a user and this is the anime<00:02:07.329> edition<00:02:07.720> by<00:02:07.869> the<00:02:07.930> way<00:02:08.110> of<00:02:08.259> the<00:02:08.379> talk<00:02:08.590> so 00:02:09.509 --> 00:02:09.519 align:start position:0% anime edition by the way of the talk so 00:02:09.519 --> 00:02:12.780 align:start position:0% anime edition by the way of the talk so the<00:02:09.729> user<00:02:10.000> typically<00:02:10.629> has<00:02:10.869> a<00:02:10.899> job<00:02:11.459> and<00:02:12.459> what 00:02:12.780 --> 00:02:12.790 align:start position:0% the user typically has a job and what 00:02:12.790 --> 00:02:14.010 align:start position:0% the user typically has a job and what they're<00:02:12.940> going<00:02:13.209> to<00:02:13.330> do<00:02:13.450> is<00:02:13.569> hire<00:02:13.780> multiple 00:02:14.010 --> 00:02:14.020 align:start position:0% they're going to do is hire multiple 00:02:14.020 --> 00:02:16.980 align:start position:0% they're going to do is hire multiple watch<00:02:14.500> towers<00:02:14.980> at<00:02:15.190> exactly<00:02:15.760> the<00:02:15.970> same<00:02:16.180> time 00:02:16.980 --> 00:02:16.990 align:start position:0% watch towers at exactly the same time 00:02:16.990 --> 00:02:18.690 align:start position:0% watch towers at exactly the same time so<00:02:17.080> they're<00:02:17.200> gonna<00:02:17.350> send<00:02:17.650> the<00:02:17.770> job<00:02:18.010> out<00:02:18.190> you 00:02:18.690 --> 00:02:18.700 align:start position:0% so they're gonna send the job out you 00:02:18.700 --> 00:02:21.390 align:start position:0% so they're gonna send the job out you know<00:02:18.850> Bom<00:02:19.090> Bom<00:02:19.390> Bom<00:02:19.690> and<00:02:20.020> then<00:02:20.830> multiple<00:02:21.190> Watts 00:02:21.390 --> 00:02:21.400 align:start position:0% know Bom Bom Bom and then multiple Watts 00:02:21.400 --> 00:02:26.040 align:start position:0% know Bom Bom Bom and then multiple Watts Towers<00:02:21.670> now<00:02:22.030> have<00:02:22.300> the<00:02:22.480> job<00:02:23.160> but<00:02:24.600> the<00:02:25.600> user<00:02:25.900> has 00:02:26.040 --> 00:02:26.050 align:start position:0% Towers now have the job but the user has 00:02:26.050 --> 00:02:29.040 align:start position:0% Towers now have the job but the user has to<00:02:26.230> pay<00:02:26.440> for<00:02:26.710> multiple<00:02:27.220> Watts<00:02:27.400> Towers<00:02:27.870> so<00:02:28.870> this 00:02:29.040 --> 00:02:29.050 align:start position:0% to pay for multiple Watts Towers so this 00:02:29.050 --> 00:02:30.990 align:start position:0% to pay for multiple Watts Towers so this sounds<00:02:29.410> a<00:02:29.440> bit<00:02:29.560> crazy<00:02:29.740> expensive<00:02:30.520> doesn't<00:02:30.790> it 00:02:30.990 --> 00:02:31.000 align:start position:0% sounds a bit crazy expensive doesn't it 00:02:31.000 --> 00:02:33.930 align:start position:0% sounds a bit crazy expensive doesn't it so<00:02:31.930> typically<00:02:32.410> what<00:02:32.650> people<00:02:32.920> do<00:02:33.070> instead<00:02:33.250> is 00:02:33.930 --> 00:02:33.940 align:start position:0% so typically what people do instead is 00:02:33.940 --> 00:02:35.940 align:start position:0% so typically what people do instead is that<00:02:34.000> there's<00:02:34.420> his<00:02:34.540> own<00:02:34.750> chain<00:02:35.140> bounty 00:02:35.940 --> 00:02:35.950 align:start position:0% that there's his own chain bounty 00:02:35.950 --> 00:02:38.580 align:start position:0% that there's his own chain bounty so<00:02:36.790> the<00:02:36.910> first<00:02:37.240> Watts<00:02:37.570> tower<00:02:37.900> the<00:02:38.290> salt<00:02:38.530> you 00:02:38.580 --> 00:02:38.590 align:start position:0% so the first Watts tower the salt you 00:02:38.590 --> 00:02:40.830 align:start position:0% so the first Watts tower the salt you know<00:02:38.680> the<00:02:38.800> relay<00:02:39.190> the<00:02:39.340> transaction<00:02:40.090> and<00:02:40.270> get 00:02:40.830 --> 00:02:40.840 align:start position:0% know the relay the transaction and get 00:02:40.840 --> 00:02:42.990 align:start position:0% know the relay the transaction and get it<00:02:40.960> in<00:02:41.080> the<00:02:41.200> blockchain<00:02:41.440> will<00:02:42.280> get<00:02:42.520> the<00:02:42.670> claim 00:02:42.990 --> 00:02:43.000 align:start position:0% it in the blockchain will get the claim 00:02:43.000 --> 00:02:46.770 align:start position:0% it in the blockchain will get the claim this<00:02:43.510> bounty<00:02:44.550> so<00:02:45.550> can<00:02:46.210> you<00:02:46.300> see<00:02:46.450> the<00:02:46.570> obvious 00:02:46.770 --> 00:02:46.780 align:start position:0% this bounty so can you see the obvious 00:02:46.780 --> 00:02:49.260 align:start position:0% this bounty so can you see the obvious problem<00:02:47.410> with<00:02:47.530> this<00:02:47.740> if<00:02:48.580> you've<00:02:48.760> hired<00:02:48.910> 20 00:02:49.260 --> 00:02:49.270 align:start position:0% problem with this if you've hired 20 00:02:49.270 --> 00:02:50.910 align:start position:0% problem with this if you've hired 20 Watts<00:02:49.570> Towers<00:02:49.870> on<00:02:50.320> they're<00:02:50.470> all<00:02:50.500> competing 00:02:50.910 --> 00:02:50.920 align:start position:0% Watts Towers on they're all competing 00:02:50.920 --> 00:02:53.160 align:start position:0% Watts Towers on they're all competing for<00:02:51.100> the<00:02:51.250> same<00:02:51.460> bounty<00:02:52.030> you're<00:02:52.750> gonna<00:02:52.990> get 00:02:53.160 --> 00:02:53.170 align:start position:0% for the same bounty you're gonna get 00:02:53.170 --> 00:02:55.920 align:start position:0% for the same bounty you're gonna get spams<00:02:53.560> bombs<00:02:53.890> bombs<00:02:54.130> bombs<00:02:54.340> bomb<00:02:54.900> you<00:02:55.900> know 00:02:55.920 --> 00:02:55.930 align:start position:0% spams bombs bombs bombs bomb you know 00:02:55.930 --> 00:02:57.420 align:start position:0% spams bombs bombs bombs bomb you know only<00:02:56.200> one<00:02:56.500> watched<00:02:56.740> how<00:02:56.950> it's<00:02:57.100> gonna<00:02:57.250> get 00:02:57.420 --> 00:02:57.430 align:start position:0% only one watched how it's gonna get 00:02:57.430 --> 00:02:59.190 align:start position:0% only one watched how it's gonna get rewarded<00:02:58.000> and<00:02:58.210> the<00:02:58.270> rats<00:02:58.720> are<00:02:58.870> gonna<00:02:59.020> have<00:02:59.140> to 00:02:59.190 --> 00:02:59.200 align:start position:0% rewarded and the rats are gonna have to 00:02:59.200 --> 00:03:01.140 align:start position:0% rewarded and the rats are gonna have to pay<00:02:59.350> a<00:02:59.380> penalty<00:02:59.650> you<00:03:00.130> know<00:03:00.280> the<00:03:00.430> gas<00:03:00.610> price<00:03:01.000> of 00:03:01.140 --> 00:03:01.150 align:start position:0% pay a penalty you know the gas price of 00:03:01.150 --> 00:03:03.240 align:start position:0% pay a penalty you know the gas price of a<00:03:01.240> transaction<00:03:01.630> for<00:03:02.380> failing<00:03:02.710> to<00:03:02.740> get<00:03:02.950> it<00:03:03.100> in 00:03:03.240 --> 00:03:03.250 align:start position:0% a transaction for failing to get it in 00:03:03.250 --> 00:03:05.700 align:start position:0% a transaction for failing to get it in and<00:03:03.610> that's<00:03:04.120> not<00:03:04.240> very<00:03:04.300> good<00:03:04.720> you<00:03:05.290> know<00:03:05.410> as<00:03:05.530> an 00:03:05.700 --> 00:03:05.710 align:start position:0% and that's not very good you know as an 00:03:05.710 --> 00:03:09.030 align:start position:0% and that's not very good you know as an illustrated<00:03:06.250> example<00:03:06.570> bomb<00:03:07.570> you<00:03:08.380> know<00:03:08.440> the 00:03:09.030 --> 00:03:09.040 align:start position:0% illustrated example bomb you know the 00:03:09.040 --> 00:03:11.640 align:start position:0% illustrated example bomb you know the reward<00:03:09.430> has<00:03:09.520> given<00:03:09.850> in<00:03:09.910> this<00:03:10.060> watch<00:03:10.270> tower<00:03:10.650> now 00:03:11.640 --> 00:03:11.650 align:start position:0% reward has given in this watch tower now 00:03:11.650 --> 00:03:13.730 align:start position:0% reward has given in this watch tower now they're<00:03:11.920> competing<00:03:12.340> for<00:03:12.520> this<00:03:12.790> 5k<00:03:13.060> you<00:03:13.600> know 00:03:13.730 --> 00:03:13.740 align:start position:0% they're competing for this 5k you know 00:03:13.740 --> 00:03:16.530 align:start position:0% they're competing for this 5k you know $5,000<00:03:14.740> as<00:03:14.890> a<00:03:14.920> bounty<00:03:15.190> that's<00:03:16.000> fine 00:03:16.530 --> 00:03:16.540 align:start position:0% $5,000 as a bounty that's fine 00:03:16.540 --> 00:03:18.630 align:start position:0% $5,000 as a bounty that's fine over<00:03:16.990> the<00:03:17.170> long<00:03:17.320> period<00:03:17.350> you<00:03:18.250> make<00:03:18.430> some 00:03:18.630 --> 00:03:18.640 align:start position:0% over the long period you make some 00:03:18.640 --> 00:03:20.550 align:start position:0% over the long period you make some losses<00:03:18.880> you<00:03:19.180> win<00:03:19.360> but<00:03:20.080> if<00:03:20.170> they're<00:03:20.290> competing 00:03:20.550 --> 00:03:20.560 align:start position:0% losses you win but if they're competing 00:03:20.560 --> 00:03:21.690 align:start position:0% losses you win but if they're competing for<00:03:20.830> $5.00 00:03:21.690 --> 00:03:21.700 align:start position:0% for $5.00 00:03:21.700 --> 00:03:24.150 align:start position:0% for $5.00 that's<00:03:22.450> a<00:03:22.600> sucks<00:03:23.020> you<00:03:23.440> know<00:03:23.590> who<00:03:23.830> wants<00:03:24.070> to 00:03:24.150 --> 00:03:24.160 align:start position:0% that's a sucks you know who wants to 00:03:24.160 --> 00:03:25.860 align:start position:0% that's a sucks you know who wants to compete<00:03:24.310> for<00:03:24.580> $5.00<00:03:25.150> and<00:03:25.330> lose<00:03:25.450> money<00:03:25.630> in<00:03:25.780> the 00:03:25.860 --> 00:03:25.870 align:start position:0% compete for $5.00 and lose money in the 00:03:25.870 --> 00:03:27.750 align:start position:0% compete for $5.00 and lose money in the long<00:03:26.020> run<00:03:26.050> so<00:03:26.950> it's<00:03:27.070> not<00:03:27.160> a<00:03:27.220> great<00:03:27.520> way<00:03:27.730> to 00:03:27.750 --> 00:03:27.760 align:start position:0% long run so it's not a great way to 00:03:27.760 --> 00:03:29.130 align:start position:0% long run so it's not a great way to build<00:03:28.030> these<00:03:28.210> third-party<00:03:28.480> watching 00:03:29.130 --> 00:03:29.140 align:start position:0% build these third-party watching 00:03:29.140 --> 00:03:32.190 align:start position:0% build these third-party watching networks<00:03:29.500> an<00:03:30.450> alternative<00:03:31.450> approach<00:03:31.600> with 00:03:32.190 --> 00:03:32.200 align:start position:0% networks an alternative approach with 00:03:32.200 --> 00:03:34.770 align:start position:0% networks an alternative approach with people<00:03:32.470> 10<00:03:32.740> that<00:03:32.950> recommend<00:03:33.520> is<00:03:33.760> why<00:03:34.510> don't<00:03:34.570> we 00:03:34.770 --> 00:03:34.780 align:start position:0% people 10 that recommend is why don't we 00:03:34.780 --> 00:03:38.250 align:start position:0% people 10 that recommend is why don't we you<00:03:35.380> know<00:03:35.500> do<00:03:35.740> segments<00:03:36.370> so<00:03:37.360> watts<00:03:37.660> Tower<00:03:37.990> 1 00:03:38.250 --> 00:03:38.260 align:start position:0% you know do segments so watts Tower 1 00:03:38.260 --> 00:03:41.610 align:start position:0% you know do segments so watts Tower 1 can<00:03:38.590> respond<00:03:39.010> by<00:03:39.430> time<00:03:39.760> t1<00:03:40.260> Watchtower<00:03:41.260> two 00:03:41.610 --> 00:03:41.620 align:start position:0% can respond by time t1 Watchtower two 00:03:41.620 --> 00:03:45.930 align:start position:0% can respond by time t1 Watchtower two can<00:03:41.920> respond<00:03:42.340> by<00:03:42.670> t2<00:03:43.020> opto<00:03:44.020> TN<00:03:44.410> now<00:03:45.400> the<00:03:45.460> issue 00:03:45.930 --> 00:03:45.940 align:start position:0% can respond by t2 opto TN now the issue 00:03:45.940 --> 00:03:47.580 align:start position:0% can respond by t2 opto TN now the issue here<00:03:46.450> is<00:03:46.600> that<00:03:46.630> is<00:03:46.900> really<00:03:47.140> awkward<00:03:47.560> to 00:03:47.580 --> 00:03:47.590 align:start position:0% here is that is really awkward to 00:03:47.590 --> 00:03:50.100 align:start position:0% here is that is really awkward to enforce<00:03:48.130> either<00:03:48.970> your<00:03:49.270> smart<00:03:49.600> contract 00:03:50.100 --> 00:03:50.110 align:start position:0% enforce either your smart contract 00:03:50.110 --> 00:03:53.040 align:start position:0% enforce either your smart contract considers<00:03:50.470> is<00:03:50.650> up<00:03:50.830> front<00:03:51.190> or<00:03:51.970> you<00:03:52.390> somehow<00:03:52.780> try 00:03:53.040 --> 00:03:53.050 align:start position:0% considers is up front or you somehow try 00:03:53.050 --> 00:03:55.170 align:start position:0% considers is up front or you somehow try to<00:03:53.110> enforce<00:03:53.530> is<00:03:53.680> an<00:03:53.830> altar<00:03:54.250> monitor<00:03:54.700> which 00:03:55.170 --> 00:03:55.180 align:start position:0% to enforce is an altar monitor which 00:03:55.180 --> 00:03:57.090 align:start position:0% to enforce is an altar monitor which doesn't<00:03:55.510> really<00:03:55.600> work<00:03:55.840> either<00:03:56.020> so<00:03:56.380> I've<00:03:56.920> never 00:03:57.090 --> 00:03:57.100 align:start position:0% doesn't really work either so I've never 00:03:57.100 --> 00:03:58.740 align:start position:0% doesn't really work either so I've never really<00:03:57.370> considered<00:03:57.550> this<00:03:57.970> as<00:03:58.120> a<00:03:58.150> real<00:03:58.360> valid 00:03:58.740 --> 00:03:58.750 align:start position:0% really considered this as a real valid 00:03:58.750 --> 00:04:01.560 align:start position:0% really considered this as a real valid solution<00:03:59.170> to<00:03:59.290> the<00:03:59.380> problem<00:03:59.830> and<00:04:00.450> then<00:04:01.450> the 00:04:01.560 --> 00:04:01.570 align:start position:0% solution to the problem and then the 00:04:01.570 --> 00:04:04.440 align:start position:0% solution to the problem and then the worst<00:04:01.750> case<00:04:01.900> scenario<00:04:02.590> you<00:04:02.860> guys<00:04:03.640> hire<00:04:03.970> 20 00:04:04.440 --> 00:04:04.450 align:start position:0% worst case scenario you guys hire 20 00:04:04.450 --> 00:04:07.560 align:start position:0% worst case scenario you guys hire 20 Watchers<00:04:04.930> and<00:04:05.170> nobody<00:04:06.130> responded<00:04:06.820> and<00:04:07.060> your 00:04:07.560 --> 00:04:07.570 align:start position:0% Watchers and nobody responded and your 00:04:07.570 --> 00:04:09.750 align:start position:0% Watchers and nobody responded and your transaction<00:04:08.110> has<00:04:08.200> never<00:04:08.350> relayed<00:04:08.800> maybe<00:04:09.580> you 00:04:09.750 --> 00:04:09.760 align:start position:0% transaction has never relayed maybe you 00:04:09.760 --> 00:04:11.430 align:start position:0% transaction has never relayed maybe you lost<00:04:09.910> the<00:04:10.150> auction<00:04:10.300> you<00:04:10.750> lost<00:04:10.960> money<00:04:11.200> in<00:04:11.350> your 00:04:11.430 --> 00:04:11.440 align:start position:0% lost the auction you lost money in your 00:04:11.440 --> 00:04:14.040 align:start position:0% lost the auction you lost money in your steer<00:04:11.680> channel<00:04:12.330> well<00:04:13.330> there's<00:04:13.900> no<00:04:14.020> evidence 00:04:14.040 --> 00:04:14.050 align:start position:0% steer channel well there's no evidence 00:04:14.050 --> 00:04:16.949 align:start position:0% steer channel well there's no evidence there's<00:04:14.740> no<00:04:14.800> recourse<00:04:15.310> nothing<00:04:15.820> so<00:04:16.630> I<00:04:16.690> really 00:04:16.949 --> 00:04:16.959 align:start position:0% there's no recourse nothing so I really 00:04:16.959 --> 00:04:18.750 align:start position:0% there's no recourse nothing so I really sucks<00:04:17.290> this<00:04:17.440> from<00:04:17.620> a<00:04:17.680> user<00:04:17.920> perspective<00:04:18.100> you 00:04:18.750 --> 00:04:18.760 align:start position:0% sucks this from a user perspective you 00:04:18.760 --> 00:04:20.580 align:start position:0% sucks this from a user perspective you can't<00:04:18.970> blame<00:04:19.209> anyone<00:04:19.540> because<00:04:20.230> they<00:04:20.260> didn't 00:04:20.580 --> 00:04:20.590 align:start position:0% can't blame anyone because they didn't 00:04:20.590 --> 00:04:23.940 align:start position:0% can't blame anyone because they didn't do<00:04:20.680> their<00:04:20.799> job<00:04:21.750> so<00:04:22.750> why<00:04:23.020> do<00:04:23.080> we<00:04:23.200> always<00:04:23.560> think 00:04:23.940 --> 00:04:23.950 align:start position:0% do their job so why do we always think 00:04:23.950 --> 00:04:25.710 align:start position:0% do their job so why do we always think this<00:04:24.160> is<00:04:24.340> the<00:04:24.460> best<00:04:24.730> way<00:04:24.970> that<00:04:25.000> builders<00:04:25.450> third 00:04:25.710 --> 00:04:25.720 align:start position:0% this is the best way that builders third 00:04:25.720 --> 00:04:27.540 align:start position:0% this is the best way that builders third party<00:04:26.080> broadcasting<00:04:26.740> network<00:04:27.070> it<00:04:27.430> was 00:04:27.540 --> 00:04:27.550 align:start position:0% party broadcasting network it was 00:04:27.550 --> 00:04:29.100 align:start position:0% party broadcasting network it was actually<00:04:27.850> really<00:04:28.000> frustrating<00:04:28.210> because<00:04:28.810> it's 00:04:29.100 --> 00:04:29.110 align:start position:0% actually really frustrating because it's 00:04:29.110 --> 00:04:30.210 align:start position:0% actually really frustrating because it's clearly<00:04:29.350> awkward<00:04:29.919> and 00:04:30.210 --> 00:04:30.220 align:start position:0% clearly awkward and 00:04:30.220 --> 00:04:32.010 align:start position:0% clearly awkward and doesn't<00:04:30.490> work<00:04:30.580> that<00:04:30.640> well<00:04:31.000> you<00:04:31.720> know<00:04:31.780> come<00:04:31.990> a 00:04:32.010 --> 00:04:32.020 align:start position:0% doesn't work that well you know come a 00:04:32.020 --> 00:04:35.160 align:start position:0% doesn't work that well you know come a little<00:04:32.200> animate<00:04:32.710> gift<00:04:32.980> there<00:04:33.750> so<00:04:34.750> from<00:04:35.080> the 00:04:35.160 --> 00:04:35.170 align:start position:0% little animate gift there so from the 00:04:35.170 --> 00:04:37.590 align:start position:0% little animate gift there so from the end<00:04:35.290> user<00:04:35.650> perspective<00:04:36.030> why<00:04:37.030> are<00:04:37.090> we<00:04:37.330> trying 00:04:37.590 --> 00:04:37.600 align:start position:0% end user perspective why are we trying 00:04:37.600 --> 00:04:39.690 align:start position:0% end user perspective why are we trying to<00:04:37.660> design<00:04:38.020> these<00:04:38.200> third-party<00:04:38.700> relay 00:04:39.690 --> 00:04:39.700 align:start position:0% to design these third-party relay 00:04:39.700 --> 00:04:41.850 align:start position:0% to design these third-party relay networks<00:04:40.150> in<00:04:40.330> this<00:04:40.420> fashion<00:04:40.930> so<00:04:41.110> what<00:04:41.650> are<00:04:41.770> the 00:04:41.850 --> 00:04:41.860 align:start position:0% networks in this fashion so what are the 00:04:41.860 --> 00:04:45.020 align:start position:0% networks in this fashion so what are the goals<00:04:42.070> that<00:04:42.370> were<00:04:42.520> trying<00:04:42.910> to<00:04:43.150> achieve 00:04:45.020 --> 00:04:45.030 align:start position:0% goals that were trying to achieve 00:04:45.030 --> 00:04:47.540 align:start position:0% goals that were trying to achieve typically<00:04:46.030> we're<00:04:46.270> trying<00:04:46.570> to<00:04:46.660> minimize<00:04:46.780> trust 00:04:47.540 --> 00:04:47.550 align:start position:0% typically we're trying to minimize trust 00:04:47.550 --> 00:04:50.550 align:start position:0% typically we're trying to minimize trust we<00:04:48.550> don't<00:04:48.730> want<00:04:48.850> to<00:04:48.970> blindly<00:04:49.540> trust<00:04:49.660> a<00:04:50.320> single 00:04:50.550 --> 00:04:50.560 align:start position:0% we don't want to blindly trust a single 00:04:50.560 --> 00:04:54.480 align:start position:0% we don't want to blindly trust a single party<00:04:51.550> to<00:04:52.060> respond<00:04:52.510> on<00:04:52.630> our<00:04:52.750> behalf<00:04:53.080> and<00:04:53.500> also 00:04:54.480 --> 00:04:54.490 align:start position:0% party to respond on our behalf and also 00:04:54.490 --> 00:04:57.060 align:start position:0% party to respond on our behalf and also for<00:04:54.730> the<00:04:54.820> availability<00:04:55.330> of<00:04:55.570> Broadcasters<00:04:56.470> if 00:04:57.060 --> 00:04:57.070 align:start position:0% for the availability of Broadcasters if 00:04:57.070 --> 00:05:00.420 align:start position:0% for the availability of Broadcasters if I<00:04:57.250> hire<00:04:57.520> 22<00:04:58.240> Watchers<00:04:58.950> hopefully<00:04:59.950> ones<00:05:00.220> at 00:05:00.420 --> 00:05:00.430 align:start position:0% I hire 22 Watchers hopefully ones at 00:05:00.430 --> 00:05:03.170 align:start position:0% I hire 22 Watchers hopefully ones at least<00:05:00.460> online<00:05:01.150> to<00:05:01.330> complete<00:05:01.660> the<00:05:01.810> job<00:05:02.020> for<00:05:02.380> me 00:05:03.170 --> 00:05:03.180 align:start position:0% least online to complete the job for me 00:05:03.180 --> 00:05:05.340 align:start position:0% least online to complete the job for me but<00:05:04.180> well<00:05:04.330> most<00:05:04.540> people<00:05:04.840> seem<00:05:05.050> to<00:05:05.110> forget 00:05:05.340 --> 00:05:05.350 align:start position:0% but well most people seem to forget 00:05:05.350 --> 00:05:09.240 align:start position:0% but well most people seem to forget about<00:05:05.590> as<00:05:06.570> accountability<00:05:07.710> you<00:05:08.710> know<00:05:08.860> if<00:05:09.010> the 00:05:09.240 --> 00:05:09.250 align:start position:0% about as accountability you know if the 00:05:09.250 --> 00:05:11.010 align:start position:0% about as accountability you know if the watch<00:05:09.430> tower<00:05:09.760> doesn't<00:05:10.060> do<00:05:10.150> the<00:05:10.270> job<00:05:10.480> for<00:05:10.510> me 00:05:11.010 --> 00:05:11.020 align:start position:0% watch tower doesn't do the job for me 00:05:11.020 --> 00:05:13.560 align:start position:0% watch tower doesn't do the job for me can<00:05:11.680> I<00:05:11.710> prove<00:05:12.160> that<00:05:12.220> and<00:05:12.730> can<00:05:13.060> I<00:05:13.150> hold<00:05:13.420> them 00:05:13.560 --> 00:05:13.570 align:start position:0% can I prove that and can I hold them 00:05:13.570 --> 00:05:16.470 align:start position:0% can I prove that and can I hold them accountable<00:05:14.490> so<00:05:15.490> this<00:05:15.700> is<00:05:15.850> basically<00:05:16.270> what 00:05:16.470 --> 00:05:16.480 align:start position:0% accountable so this is basically what 00:05:16.480 --> 00:05:17.430 align:start position:0% accountable so this is basically what we're<00:05:16.630> building<00:05:16.930> a<00:05:17.020> Pisa 00:05:17.430 --> 00:05:17.440 align:start position:0% we're building a Pisa 00:05:17.440 --> 00:05:19.410 align:start position:0% we're building a Pisa safe<00:05:18.190> announce<00:05:18.580> the<00:05:18.760> accountable 00:05:19.410 --> 00:05:19.420 align:start position:0% safe announce the accountable 00:05:19.420 --> 00:05:22.500 align:start position:0% safe announce the accountable third-party<00:05:20.350> Broadcasting<00:05:21.100> Network<00:05:21.360> so<00:05:22.360> now 00:05:22.500 --> 00:05:22.510 align:start position:0% third-party Broadcasting Network so now 00:05:22.510 --> 00:05:25.560 align:start position:0% third-party Broadcasting Network so now I'm<00:05:22.600> going<00:05:22.720> to<00:05:22.810> start<00:05:23.020> my<00:05:23.110> talk<00:05:23.280> cool<00:05:24.419> so<00:05:25.419> what 00:05:25.560 --> 00:05:25.570 align:start position:0% I'm going to start my talk cool so what 00:05:25.570 --> 00:05:27.540 align:start position:0% I'm going to start my talk cool so what is<00:05:25.690> Pisa<00:05:26.220> basically<00:05:27.220> we<00:05:27.310> have<00:05:27.400> this 00:05:27.540 --> 00:05:27.550 align:start position:0% is Pisa basically we have this 00:05:27.550 --> 00:05:30.180 align:start position:0% is Pisa basically we have this broadcaster<00:05:28.450> he<00:05:28.960> has<00:05:29.080> skin<00:05:29.410> in<00:05:29.560> the<00:05:29.650> game<00:05:29.680> and 00:05:30.180 --> 00:05:30.190 align:start position:0% broadcaster he has skin in the game and 00:05:30.190 --> 00:05:32.130 align:start position:0% broadcaster he has skin in the game and coins<00:05:30.610> locked<00:05:30.970> up<00:05:31.180> on<00:05:31.360> the<00:05:31.450> blockchain<00:05:31.690> and 00:05:32.130 --> 00:05:32.140 align:start position:0% coins locked up on the blockchain and 00:05:32.140 --> 00:05:34.409 align:start position:0% coins locked up on the blockchain and there's<00:05:32.650> a<00:05:32.740> piece<00:05:32.950> of<00:05:33.130> contract<00:05:33.640> which<00:05:34.270> is 00:05:34.409 --> 00:05:34.419 align:start position:0% there's a piece of contract which is 00:05:34.419 --> 00:05:36.780 align:start position:0% there's a piece of contract which is effectively<00:05:35.020> the<00:05:35.500> service<00:05:35.919> level<00:05:36.250> agreement 00:05:36.780 --> 00:05:36.790 align:start position:0% effectively the service level agreement 00:05:36.790 --> 00:05:40.920 align:start position:0% effectively the service level agreement between<00:05:37.330> the<00:05:37.690> tower<00:05:37.960> and<00:05:38.169> the<00:05:38.500> customer<00:05:39.930> now 00:05:40.920 --> 00:05:40.930 align:start position:0% between the tower and the customer now 00:05:40.930 --> 00:05:43.530 align:start position:0% between the tower and the customer now when<00:05:41.200> the<00:05:41.350> customer<00:05:41.860> hires<00:05:42.130> Pisa<00:05:42.550> you<00:05:43.270> send 00:05:43.530 --> 00:05:43.540 align:start position:0% when the customer hires Pisa you send 00:05:43.540 --> 00:05:45.900 align:start position:0% when the customer hires Pisa you send the<00:05:43.660> job<00:05:43.870> the<00:05:44.050> Pisa<00:05:44.290> and<00:05:44.590> in<00:05:44.890> return<00:05:45.280> the 00:05:45.900 --> 00:05:45.910 align:start position:0% the job the Pisa and in return the 00:05:45.910 --> 00:05:48.060 align:start position:0% the job the Pisa and in return the customer<00:05:46.390> will<00:05:46.540> get<00:05:46.690> a<00:05:46.720> signed<00:05:46.990> receipt<00:05:47.229> so 00:05:48.060 --> 00:05:48.070 align:start position:0% customer will get a signed receipt so 00:05:48.070 --> 00:05:49.110 align:start position:0% customer will get a signed receipt so now<00:05:48.220> they<00:05:48.400> have<00:05:48.520> you<00:05:48.610> know<00:05:48.760> cryptographic 00:05:49.110 --> 00:05:49.120 align:start position:0% now they have you know cryptographic 00:05:49.120 --> 00:05:51.270 align:start position:0% now they have you know cryptographic evidence<00:05:49.900> that<00:05:50.350> they're<00:05:50.530> actually<00:05:50.979> hired 00:05:51.270 --> 00:05:51.280 align:start position:0% evidence that they're actually hired 00:05:51.280 --> 00:05:55.409 align:start position:0% evidence that they're actually hired Pisa<00:05:52.120> or<00:05:52.450> a<00:05:52.540> watch<00:05:52.810> tower<00:05:54.060> so<00:05:55.060> what<00:05:55.210> type<00:05:55.390> of 00:05:55.409 --> 00:05:55.419 align:start position:0% Pisa or a watch tower so what type of 00:05:55.419 --> 00:05:59.190 align:start position:0% Pisa or a watch tower so what type of job<00:05:55.810> can<00:05:56.050> Pisa<00:05:56.350> accept<00:05:57.060> both<00:05:58.060> it<00:05:58.750> can<00:05:59.020> be<00:05:59.169> a 00:05:59.190 --> 00:05:59.200 align:start position:0% job can Pisa accept both it can be a 00:05:59.200 --> 00:06:00.960 align:start position:0% job can Pisa accept both it can be a real<00:05:59.470> layer<00:05:59.680> you<00:06:00.400> know<00:06:00.550> these<00:06:00.669> meta 00:06:00.960 --> 00:06:00.970 align:start position:0% real layer you know these meta 00:06:00.970 --> 00:06:03.540 align:start position:0% real layer you know these meta transactions<00:06:01.750> and<00:06:01.990> it<00:06:02.530> can<00:06:02.680> be<00:06:02.800> a<00:06:02.830> responder 00:06:03.540 --> 00:06:03.550 align:start position:0% transactions and it can be a responder 00:06:03.550 --> 00:06:05.880 align:start position:0% transactions and it can be a responder it<00:06:04.030> can<00:06:04.210> watch<00:06:04.390> for<00:06:04.630> events<00:06:05.080> and<00:06:05.260> respond<00:06:05.800> on 00:06:05.880 --> 00:06:05.890 align:start position:0% it can watch for events and respond on 00:06:05.890 --> 00:06:09.719 align:start position:0% it can watch for events and respond on your<00:06:06.040> behalf<00:06:06.340> and<00:06:07.800> of<00:06:08.800> course<00:06:09.130> the<00:06:09.400> way<00:06:09.490> I<00:06:09.520> will 00:06:09.719 --> 00:06:09.729 align:start position:0% your behalf and of course the way I will 00:06:09.729 --> 00:06:12.060 align:start position:0% your behalf and of course the way I will look<00:06:09.910> like<00:06:10.180> is<00:06:10.510> you<00:06:11.080> know<00:06:11.169> Alice<00:06:11.530> and<00:06:11.680> Bob<00:06:11.800> do 00:06:12.060 --> 00:06:12.070 align:start position:0% look like is you know Alice and Bob do 00:06:12.070 --> 00:06:15.390 align:start position:0% look like is you know Alice and Bob do something<00:06:12.750> Alice<00:06:13.750> hires<00:06:13.990> Pisa<00:06:14.380> Alice<00:06:15.220> goes 00:06:15.390 --> 00:06:15.400 align:start position:0% something Alice hires Pisa Alice goes 00:06:15.400 --> 00:06:18.270 align:start position:0% something Alice hires Pisa Alice goes offline<00:06:16.020> if<00:06:17.020> there's<00:06:17.590> an<00:06:17.710> event<00:06:17.950> on<00:06:18.190> the 00:06:18.270 --> 00:06:18.280 align:start position:0% offline if there's an event on the 00:06:18.280 --> 00:06:20.940 align:start position:0% offline if there's an event on the blockchain<00:06:18.630> then<00:06:19.630> Pisa<00:06:19.960> will<00:06:20.169> simply<00:06:20.530> respond 00:06:20.940 --> 00:06:20.950 align:start position:0% blockchain then Pisa will simply respond 00:06:20.950 --> 00:06:23.820 align:start position:0% blockchain then Pisa will simply respond in<00:06:21.130> Alice's<00:06:21.520> behalf<00:06:22.200> then<00:06:23.200> Alice<00:06:23.440> can<00:06:23.620> come 00:06:23.820 --> 00:06:23.830 align:start position:0% in Alice's behalf then Alice can come 00:06:23.830 --> 00:06:25.560 align:start position:0% in Alice's behalf then Alice can come back<00:06:23.979> online<00:06:24.370> later<00:06:24.580> and<00:06:24.910> then<00:06:25.180> she<00:06:25.330> can<00:06:25.479> you 00:06:25.560 --> 00:06:25.570 align:start position:0% back online later and then she can you 00:06:25.570 --> 00:06:28.050 align:start position:0% back online later and then she can you verify<00:06:26.110> the<00:06:26.919> peas<00:06:27.250> and<00:06:27.490> the<00:06:27.580> watchtower 00:06:28.050 --> 00:06:28.060 align:start position:0% verify the peas and the watchtower 00:06:28.060 --> 00:06:31.760 align:start position:0% verify the peas and the watchtower actually<00:06:28.870> did<00:06:29.110> his<00:06:29.229> job<00:06:29.850> now<00:06:30.850> the<00:06:30.910> question<00:06:31.510> is 00:06:31.760 --> 00:06:31.770 align:start position:0% actually did his job now the question is 00:06:31.770 --> 00:06:35.190 align:start position:0% actually did his job now the question is what<00:06:32.770> a<00:06:32.800> Pisa<00:06:33.130> didn't<00:06:33.520> respond<00:06:33.970> what<00:06:34.900> a<00:06:34.930> Pisa 00:06:35.190 --> 00:06:35.200 align:start position:0% what a Pisa didn't respond what a Pisa 00:06:35.200 --> 00:06:37.860 align:start position:0% what a Pisa didn't respond what a Pisa didn't<00:06:35.650> do<00:06:35.770> the<00:06:35.890> job<00:06:36.190> and<00:06:36.550> didn't<00:06:37.360> protect<00:06:37.720> the 00:06:37.860 --> 00:06:37.870 align:start position:0% didn't do the job and didn't protect the 00:06:37.870 --> 00:06:39.779 align:start position:0% didn't do the job and didn't protect the customer<00:06:38.410> you<00:06:39.070> know<00:06:39.190> when<00:06:39.370> it<00:06:39.490> when<00:06:39.729> it 00:06:39.779 --> 00:06:39.789 align:start position:0% customer you know when it when it 00:06:39.789 --> 00:06:43.170 align:start position:0% customer you know when it when it promised<00:06:40.210> it<00:06:40.330> would<00:06:41.430> can<00:06:42.430> we<00:06:42.550> do<00:06:42.700> anything 00:06:43.170 --> 00:06:43.180 align:start position:0% promised it would can we do anything 00:06:43.180 --> 00:06:44.159 align:start position:0% promised it would can we do anything about<00:06:43.300> that 00:06:44.159 --> 00:06:44.169 align:start position:0% about that 00:06:44.169 --> 00:06:45.540 align:start position:0% about that and<00:06:44.229> that's<00:06:44.379> exactly<00:06:44.560> what<00:06:44.979> peas<00:06:45.159> is<00:06:45.310> trying 00:06:45.540 --> 00:06:45.550 align:start position:0% and that's exactly what peas is trying 00:06:45.550 --> 00:06:48.300 align:start position:0% and that's exactly what peas is trying to<00:06:45.639> solve<00:06:45.849> Pisa<00:06:46.749> is<00:06:47.020> a<00:06:47.139> trust<00:06:47.439> minimized 00:06:48.300 --> 00:06:48.310 align:start position:0% to solve Pisa is a trust minimized 00:06:48.310 --> 00:06:51.179 align:start position:0% to solve Pisa is a trust minimized you<00:06:48.400> know<00:06:48.550> third-party<00:06:49.539> broadcaster<00:06:50.319> because 00:06:51.179 --> 00:06:51.189 align:start position:0% you know third-party broadcaster because 00:06:51.189 --> 00:06:53.700 align:start position:0% you know third-party broadcaster because it<00:06:51.310> has<00:06:51.430> pronounced<00:06:51.789> reliability<00:06:52.479> the<00:06:53.409> user 00:06:53.700 --> 00:06:53.710 align:start position:0% it has pronounced reliability the user 00:06:53.710 --> 00:06:55.649 align:start position:0% it has pronounced reliability the user has<00:06:53.979> a<00:06:54.009> signed<00:06:54.400> receipt<00:06:54.610> that<00:06:55.210> they<00:06:55.389> hired 00:06:55.649 --> 00:06:55.659 align:start position:0% has a signed receipt that they hired 00:06:55.659 --> 00:06:58.050 align:start position:0% has a signed receipt that they hired this<00:06:55.870> watcher<00:06:56.349> on<00:06:57.009> they<00:06:57.370> have<00:06:57.460> on<00:06:57.669> she<00:06:57.939> and 00:06:58.050 --> 00:06:58.060 align:start position:0% this watcher on they have on she and 00:06:58.060 --> 00:07:01.409 align:start position:0% this watcher on they have on she and evidence<00:06:58.569> that<00:06:59.199> Pisa<00:06:59.499> didn't<00:06:59.949> do<00:07:00.039> its<00:07:00.189> job<00:07:00.490> you 00:07:01.409 --> 00:07:01.419 align:start position:0% evidence that Pisa didn't do its job you 00:07:01.419 --> 00:07:03.360 align:start position:0% evidence that Pisa didn't do its job you simply<00:07:01.870> submit<00:07:02.050> both<00:07:02.379> pieces<00:07:02.680> of<00:07:02.889> evidence<00:07:03.039> to 00:07:03.360 --> 00:07:03.370 align:start position:0% simply submit both pieces of evidence to 00:07:03.370 --> 00:07:04.760 align:start position:0% simply submit both pieces of evidence to the<00:07:03.460> Pisa<00:07:03.669> contract 00:07:04.760 --> 00:07:04.770 align:start position:0% the Pisa contract 00:07:04.770 --> 00:07:07.739 align:start position:0% the Pisa contract whoops<00:07:05.949> then<00:07:06.669> the<00:07:06.789> Pisa<00:07:06.999> contract<00:07:07.509> will<00:07:07.629> look 00:07:07.739 --> 00:07:07.749 align:start position:0% whoops then the Pisa contract will look 00:07:07.749 --> 00:07:10.739 align:start position:0% whoops then the Pisa contract will look at<00:07:07.900> the<00:07:07.990> evidence<00:07:08.490> evaluate<00:07:09.490> it<00:07:09.699> and<00:07:09.849> say<00:07:10.240> yep 00:07:10.739 --> 00:07:10.749 align:start position:0% at the evidence evaluate it and say yep 00:07:10.749 --> 00:07:14.249 align:start position:0% at the evidence evaluate it and say yep Pisa<00:07:11.590> didn't<00:07:11.949> do<00:07:12.009> his<00:07:12.129> job<00:07:12.449> so<00:07:13.449> now<00:07:13.479> it<00:07:13.840> forces 00:07:14.249 --> 00:07:14.259 align:start position:0% Pisa didn't do his job so now it forces 00:07:14.259 --> 00:07:16.619 align:start position:0% Pisa didn't do his job so now it forces his<00:07:14.409> refund<00:07:14.919> period<00:07:15.219> and<00:07:15.699> there's<00:07:16.479> two 00:07:16.619 --> 00:07:16.629 align:start position:0% his refund period and there's two 00:07:16.629 --> 00:07:19.769 align:start position:0% his refund period and there's two outcomes<00:07:16.839> either<00:07:17.830> alice<00:07:18.490> is<00:07:18.699> refunded<00:07:19.479> a<00:07:19.539> pre 00:07:19.769 --> 00:07:19.779 align:start position:0% outcomes either alice is refunded a pre 00:07:19.779 --> 00:07:21.480 align:start position:0% outcomes either alice is refunded a pre agreed<00:07:20.080> amount<00:07:20.319> that<00:07:21.129> was<00:07:21.279> you<00:07:21.400> know 00:07:21.480 --> 00:07:21.490 align:start position:0% agreed amount that was you know 00:07:21.490 --> 00:07:24.570 align:start position:0% agreed amount that was you know specified<00:07:22.150> in<00:07:22.330> the<00:07:22.419> signed<00:07:22.659> receipt<00:07:23.050> or<00:07:23.860> pisa 00:07:24.570 --> 00:07:24.580 align:start position:0% specified in the signed receipt or pisa 00:07:24.580 --> 00:07:26.390 align:start position:0% specified in the signed receipt or pisa is<00:07:24.819> eventually<00:07:25.150> sloshed 00:07:26.390 --> 00:07:26.400 align:start position:0% is eventually sloshed 00:07:26.400 --> 00:07:29.339 align:start position:0% is eventually sloshed so<00:07:27.400> Pisa<00:07:27.699> issues<00:07:28.060> the<00:07:28.180> refund<00:07:28.629> really 00:07:29.339 --> 00:07:29.349 align:start position:0% so Pisa issues the refund really 00:07:29.349 --> 00:07:31.890 align:start position:0% so Pisa issues the refund really straightforward<00:07:29.650> you<00:07:30.490> send<00:07:30.759> the<00:07:30.879> money<00:07:31.029> you 00:07:31.890 --> 00:07:31.900 align:start position:0% straightforward you send the money you 00:07:31.900 --> 00:07:33.480 align:start position:0% straightforward you send the money you know<00:07:32.050> that<00:07:32.289> challenge<00:07:32.680> is<00:07:32.770> cancelled<00:07:33.249> and 00:07:33.480 --> 00:07:33.490 align:start position:0% know that challenge is cancelled and 00:07:33.490 --> 00:07:35.999 align:start position:0% know that challenge is cancelled and everyone's<00:07:33.939> happy<00:07:34.169> so<00:07:35.169> I<00:07:35.229> got<00:07:35.409> one<00:07:35.560> question 00:07:35.999 --> 00:07:36.009 align:start position:0% everyone's happy so I got one question 00:07:36.009 --> 00:07:37.619 align:start position:0% everyone's happy so I got one question here<00:07:36.310> who's<00:07:36.520> ever<00:07:36.759> sent<00:07:36.969> a<00:07:37.060> transaction<00:07:37.599> to 00:07:37.619 --> 00:07:37.629 align:start position:0% here who's ever sent a transaction to 00:07:37.629 --> 00:07:39.950 align:start position:0% here who's ever sent a transaction to the<00:07:37.810> network<00:07:38.199> that<00:07:38.469> lingered<00:07:38.830> for<00:07:38.979> six<00:07:39.189> hours 00:07:39.950 --> 00:07:39.960 align:start position:0% the network that lingered for six hours 00:07:39.960 --> 00:07:42.390 align:start position:0% the network that lingered for six hours there<00:07:40.960> we<00:07:41.080> go<00:07:41.319> look<00:07:41.589> at<00:07:41.650> these<00:07:41.800> year<00:07:42.099> old<00:07:42.219> top 00:07:42.390 --> 00:07:42.400 align:start position:0% there we go look at these year old top 00:07:42.400 --> 00:07:44.339 align:start position:0% there we go look at these year old top developers<00:07:42.849> definitely<00:07:43.300> now<00:07:43.900> what<00:07:44.110> would<00:07:44.259> be 00:07:44.339 --> 00:07:44.349 align:start position:0% developers definitely now what would be 00:07:44.349 --> 00:07:46.260 align:start position:0% developers definitely now what would be nice<00:07:44.560> is<00:07:44.620> if<00:07:44.979> it<00:07:45.099> lingers<00:07:45.580> for<00:07:45.610> six<00:07:45.939> hours 00:07:46.260 --> 00:07:46.270 align:start position:0% nice is if it lingers for six hours 00:07:46.270 --> 00:07:48.300 align:start position:0% nice is if it lingers for six hours you're<00:07:46.689> gonna<00:07:46.900> get<00:07:47.050> a<00:07:47.110> $20<00:07:47.620> refund<00:07:48.009> from<00:07:48.129> Pisa 00:07:48.300 --> 00:07:48.310 align:start position:0% you're gonna get a $20 refund from Pisa 00:07:48.310 --> 00:07:49.649 align:start position:0% you're gonna get a $20 refund from Pisa you<00:07:49.000> know<00:07:49.120> you're<00:07:49.330> gonna<00:07:49.449> have<00:07:49.539> a<00:07:49.569> little 00:07:49.649 --> 00:07:49.659 align:start position:0% you know you're gonna have a little 00:07:49.659 --> 00:07:50.999 align:start position:0% you know you're gonna have a little smile<00:07:49.960> in<00:07:50.080> your<00:07:50.169> face<00:07:50.229> cuz<00:07:50.529> you<00:07:50.620> made<00:07:50.770> money 00:07:50.999 --> 00:07:51.009 align:start position:0% smile in your face cuz you made money 00:07:51.009 --> 00:07:52.709 align:start position:0% smile in your face cuz you made money for<00:07:51.219> that<00:07:51.339> for<00:07:51.669> the<00:07:51.729> body<00:07:51.909> wax<00:07:52.360> use<00:07:52.569> your 00:07:52.709 --> 00:07:52.719 align:start position:0% for that for the body wax use your 00:07:52.719 --> 00:07:55.439 align:start position:0% for that for the body wax use your experience<00:07:53.199> anyway<00:07:54.069> if<00:07:54.399> Peter<00:07:54.939> doesn't<00:07:55.060> give 00:07:55.439 --> 00:07:55.449 align:start position:0% experience anyway if Peter doesn't give 00:07:55.449 --> 00:07:58.529 align:start position:0% experience anyway if Peter doesn't give you<00:07:55.539> that<00:07:55.569> twenty<00:07:55.960> dollar<00:07:56.110> refund<00:07:57.029> well<00:07:58.029> you 00:07:58.529 --> 00:07:58.539 align:start position:0% you that twenty dollar refund well you 00:07:58.539 --> 00:08:00.600 align:start position:0% you that twenty dollar refund well you know<00:07:58.659> blocks<00:07:59.020> keep<00:07:59.259> ticking<00:07:59.740> pisac<00:08:00.490> is 00:08:00.600 --> 00:08:00.610 align:start position:0% know blocks keep ticking pisac is 00:08:00.610 --> 00:08:02.550 align:start position:0% know blocks keep ticking pisac is slashed<00:08:00.909> and<00:08:01.330> pieces<00:08:01.960> it<00:08:02.020> will<00:08:02.080> loses<00:08:02.379> money 00:08:02.550 --> 00:08:02.560 align:start position:0% slashed and pieces it will loses money 00:08:02.560 --> 00:08:05.550 align:start position:0% slashed and pieces it will loses money and<00:08:02.979> be<00:08:03.129> very<00:08:03.310> upset<00:08:03.899> and<00:08:04.899> that's<00:08:05.080> the<00:08:05.229> basic 00:08:05.550 --> 00:08:05.560 align:start position:0% and be very upset and that's the basic 00:08:05.560 --> 00:08:06.809 align:start position:0% and be very upset and that's the basic principle<00:08:06.039> about<00:08:06.250> but<00:08:06.430> I<00:08:06.460> you<00:08:06.610> know<00:08:06.699> behind 00:08:06.809 --> 00:08:06.819 align:start position:0% principle about but I you know behind 00:08:06.819 --> 00:08:09.149 align:start position:0% principle about but I you know behind this<00:08:07.240> now<00:08:08.139> what<00:08:08.289> does<00:08:08.409> this<00:08:08.500> on<00:08:08.770> chiyan 00:08:09.149 --> 00:08:09.159 align:start position:0% this now what does this on chiyan 00:08:09.159 --> 00:08:11.689 align:start position:0% this now what does this on chiyan evidence<00:08:09.759> actually<00:08:10.750> look<00:08:11.020> like 00:08:11.689 --> 00:08:11.699 align:start position:0% evidence actually look like 00:08:11.699 --> 00:08:14.939 align:start position:0% evidence actually look like well<00:08:12.699> first<00:08:13.149> Lazar<00:08:13.870> did<00:08:14.169> the<00:08:14.259> real<00:08:14.469> a<00:08:14.620> kiss 00:08:14.939 --> 00:08:14.949 align:start position:0% well first Lazar did the real a kiss 00:08:14.949 --> 00:08:18.029 align:start position:0% well first Lazar did the real a kiss these<00:08:15.460> meta<00:08:15.819> transactions<00:08:16.629> every<00:08:17.469> Tammy<00:08:17.740> hire 00:08:18.029 --> 00:08:18.039 align:start position:0% these meta transactions every Tammy hire 00:08:18.039 --> 00:08:20.519 align:start position:0% these meta transactions every Tammy hire Pisa<00:08:18.430> the<00:08:19.120> real<00:08:19.389> a<00:08:19.539> a<00:08:19.569> transaction<00:08:20.289> in<00:08:20.379> your 00:08:20.519 --> 00:08:20.529 align:start position:0% Pisa the real a a transaction in your 00:08:20.529 --> 00:08:23.879 align:start position:0% Pisa the real a a transaction in your behalf<00:08:21.089> Pisa<00:08:22.089> will<00:08:22.389> relay<00:08:22.779> that<00:08:22.990> via<00:08:23.409> the<00:08:23.529> Pisa 00:08:23.879 --> 00:08:23.889 align:start position:0% behalf Pisa will relay that via the Pisa 00:08:23.889 --> 00:08:26.489 align:start position:0% behalf Pisa will relay that via the Pisa contract<00:08:24.520> and<00:08:24.819> it<00:08:25.270> simply<00:08:25.599> keeps<00:08:25.779> a<00:08:25.899> record<00:08:26.110> of 00:08:26.489 --> 00:08:26.499 align:start position:0% contract and it simply keeps a record of 00:08:26.499 --> 00:08:33.569 align:start position:0% contract and it simply keeps a record of every<00:08:26.979> attempt<00:08:27.810> okay<00:08:28.860> now<00:08:31.019> yep<00:08:32.159> so<00:08:33.159> it<00:08:33.279> keeps<00:08:33.459> a 00:08:33.569 --> 00:08:33.579 align:start position:0% every attempt okay now yep so it keeps a 00:08:33.579 --> 00:08:35.730 align:start position:0% every attempt okay now yep so it keeps a record<00:08:33.729> of<00:08:34.089> that<00:08:34.180> attempt<00:08:34.659> so<00:08:34.959> later<00:08:35.229> on<00:08:35.500> if 00:08:35.730 --> 00:08:35.740 align:start position:0% record of that attempt so later on if 00:08:35.740 --> 00:08:36.809 align:start position:0% record of that attempt so later on if you<00:08:35.769> come<00:08:36.039> online 00:08:36.809 --> 00:08:36.819 align:start position:0% you come online 00:08:36.819 --> 00:08:38.939 align:start position:0% you come online you<00:08:37.149> know<00:08:37.300> Pisa<00:08:37.569> promised<00:08:38.169> you<00:08:38.380> this 00:08:38.939 --> 00:08:38.949 align:start position:0% you know Pisa promised you this 00:08:38.949 --> 00:08:41.219 align:start position:0% you know Pisa promised you this transaction<00:08:39.519> would<00:08:39.789> be<00:08:39.940> relayed<00:08:40.360> before<00:08:40.959> time 00:08:41.219 --> 00:08:41.229 align:start position:0% transaction would be relayed before time 00:08:41.229 --> 00:08:44.460 align:start position:0% transaction would be relayed before time T<00:08:41.260> you<00:08:42.250> come<00:08:42.459> online<00:08:42.699> after<00:08:43.209> time<00:08:43.479> T<00:08:43.750> you<00:08:43.959> look 00:08:44.460 --> 00:08:44.470 align:start position:0% T you come online after time T you look 00:08:44.470 --> 00:08:46.319 align:start position:0% T you come online after time T you look at<00:08:44.589> the<00:08:44.680> Pisa<00:08:44.920> contract<00:08:45.550> and<00:08:45.760> there's<00:08:46.180> no 00:08:46.319 --> 00:08:46.329 align:start position:0% at the Pisa contract and there's no 00:08:46.329 --> 00:08:48.780 align:start position:0% at the Pisa contract and there's no record<00:08:46.870> of<00:08:46.990> the<00:08:47.170> attempt<00:08:47.620> there's<00:08:48.279> no<00:08:48.399> record 00:08:48.780 --> 00:08:48.790 align:start position:0% record of the attempt there's no record 00:08:48.790 --> 00:08:50.759 align:start position:0% record of the attempt there's no record of<00:08:48.880> the<00:08:49.029> attempt<00:08:49.510> he's<00:08:49.959> it<00:08:50.110> didn't<00:08:50.290> do<00:08:50.410> its<00:08:50.529> job 00:08:50.759 --> 00:08:50.769 align:start position:0% of the attempt he's it didn't do its job 00:08:50.769 --> 00:08:52.829 align:start position:0% of the attempt he's it didn't do its job you<00:08:51.459> just<00:08:51.699> send<00:08:51.910> over<00:08:52.000> the<00:08:52.209> signed<00:08:52.420> receipt 00:08:52.829 --> 00:08:52.839 align:start position:0% you just send over the signed receipt 00:08:52.839 --> 00:08:55.530 align:start position:0% you just send over the signed receipt I'm<00:08:53.019> Pisa<00:08:53.620> gets<00:08:53.890> punished<00:08:54.220> so<00:08:55.120> that's<00:08:55.269> cool 00:08:55.530 --> 00:08:55.540 align:start position:0% I'm Pisa gets punished so that's cool 00:08:55.540 --> 00:08:57.740 align:start position:0% I'm Pisa gets punished so that's cool that<00:08:56.350> actually<00:08:56.470> works<00:08:56.829> out<00:08:56.980> of<00:08:57.220> the<00:08:57.310> box 00:08:57.740 --> 00:08:57.750 align:start position:0% that actually works out of the box 00:08:57.750 --> 00:09:01.130 align:start position:0% that actually works out of the box today<00:08:58.050> on<00:08:58.860> the<00:08:59.820> other<00:08:59.940> hand<00:09:00.270> what<00:09:00.750> about<00:09:00.990> the 00:09:01.130 --> 00:09:01.140 align:start position:0% today on the other hand what about the 00:09:01.140 --> 00:09:03.260 align:start position:0% today on the other hand what about the responder<00:09:01.800> well<00:09:02.580> in<00:09:02.700> the<00:09:02.790> kids<00:09:03.030> of<00:09:03.150> the 00:09:03.260 --> 00:09:03.270 align:start position:0% responder well in the kids of the 00:09:03.270 --> 00:09:06.110 align:start position:0% responder well in the kids of the responder<00:09:03.960> basically<00:09:04.950> we<00:09:05.460> have<00:09:05.610> to<00:09:05.790> look<00:09:05.910> for 00:09:06.110 --> 00:09:06.120 align:start position:0% responder basically we have to look for 00:09:06.120 --> 00:09:08.480 align:start position:0% responder basically we have to look for events<00:09:06.630> in<00:09:06.810> the<00:09:07.020> other<00:09:07.200> contract<00:09:07.800> so<00:09:08.340> let's 00:09:08.480 --> 00:09:08.490 align:start position:0% events in the other contract so let's 00:09:08.490 --> 00:09:10.670 align:start position:0% events in the other contract so let's consider<00:09:08.670> the<00:09:09.000> auction<00:09:09.450> we<00:09:10.230> have<00:09:10.350> to<00:09:10.500> watch 00:09:10.670 --> 00:09:10.680 align:start position:0% consider the auction we have to watch 00:09:10.680 --> 00:09:12.050 align:start position:0% consider the auction we have to watch out<00:09:10.950> for<00:09:10.980> you<00:09:11.340> know<00:09:11.400> the<00:09:11.520> auction<00:09:11.880> to<00:09:11.940> be 00:09:12.050 --> 00:09:12.060 align:start position:0% out for you know the auction to be 00:09:12.060 --> 00:09:15.890 align:start position:0% out for you know the auction to be triggered<00:09:13.670> sorry<00:09:14.670> yeah<00:09:15.360> we<00:09:15.540> have<00:09:15.630> the<00:09:15.750> Watts 00:09:15.890 --> 00:09:15.900 align:start position:0% triggered sorry yeah we have the Watts 00:09:15.900 --> 00:09:18.200 align:start position:0% triggered sorry yeah we have the Watts out<00:09:16.080> for<00:09:16.320> the<00:09:16.410> auction<00:09:16.710> to<00:09:16.800> be<00:09:16.890> triggered<00:09:17.210> once 00:09:18.200 --> 00:09:18.210 align:start position:0% out for the auction to be triggered once 00:09:18.210 --> 00:09:19.730 align:start position:0% out for the auction to be triggered once it's<00:09:18.360> been<00:09:18.450> triggered<00:09:18.960> then<00:09:19.530> there's 00:09:19.730 --> 00:09:19.740 align:start position:0% it's been triggered then there's 00:09:19.740 --> 00:09:21.290 align:start position:0% it's been triggered then there's evidence<00:09:20.130> the<00:09:20.280> auction<00:09:20.520> was<00:09:20.640> triggered<00:09:21.090> and 00:09:21.290 --> 00:09:21.300 align:start position:0% evidence the auction was triggered and 00:09:21.300 --> 00:09:24.260 align:start position:0% evidence the auction was triggered and that<00:09:21.540> we<00:09:21.630> didn't<00:09:21.930> respond<00:09:22.520> now<00:09:23.520> the<00:09:23.580> issue<00:09:23.910> is 00:09:24.260 --> 00:09:24.270 align:start position:0% that we didn't respond now the issue is 00:09:24.270 --> 00:09:28.460 align:start position:0% that we didn't respond now the issue is that<00:09:24.860> this<00:09:25.860> can't<00:09:26.370> work<00:09:26.610> today<00:09:27.350> but<00:09:28.350> it 00:09:28.460 --> 00:09:28.470 align:start position:0% that this can't work today but it 00:09:28.470 --> 00:09:30.830 align:start position:0% that this can't work today but it requires<00:09:28.860> its<00:09:29.100> external<00:09:29.400> contract<00:09:30.150> to<00:09:30.720> use 00:09:30.830 --> 00:09:30.840 align:start position:0% requires its external contract to use 00:09:30.840 --> 00:09:33.440 align:start position:0% requires its external contract to use our<00:09:31.020> data<00:09:31.290> registry<00:09:31.890> and<00:09:32.460> that's<00:09:33.000> not<00:09:33.120> great 00:09:33.440 --> 00:09:33.450 align:start position:0% our data registry and that's not great 00:09:33.450 --> 00:09:36.020 align:start position:0% our data registry and that's not great it's<00:09:33.990> a<00:09:34.110> bit<00:09:34.230> invasive<00:09:34.550> we<00:09:35.550> want<00:09:35.760> to<00:09:35.850> make<00:09:36.000> sure 00:09:36.020 --> 00:09:36.030 align:start position:0% it's a bit invasive we want to make sure 00:09:36.030 --> 00:09:38.050 align:start position:0% it's a bit invasive we want to make sure we<00:09:36.240> have<00:09:36.330> seamless<00:09:36.810> integrations<00:09:37.470> tupiza 00:09:38.050 --> 00:09:38.060 align:start position:0% we have seamless integrations tupiza 00:09:38.060 --> 00:09:41.150 align:start position:0% we have seamless integrations tupiza so<00:09:39.060> for<00:09:39.270> seamless<00:09:39.630> integrations<00:09:40.410> we<00:09:40.890> have<00:09:41.010> to 00:09:41.150 --> 00:09:41.160 align:start position:0% so for seamless integrations we have to 00:09:41.160 --> 00:09:43.310 align:start position:0% so for seamless integrations we have to push<00:09:41.340> for<00:09:41.550> this<00:09:41.640> hard<00:09:41.910> fork<00:09:42.210> for<00:09:42.840> block<00:09:43.080> top 00:09:43.310 --> 00:09:43.320 align:start position:0% push for this hard fork for block top 00:09:43.320 --> 00:09:45.950 align:start position:0% push for this hard fork for block top block<00:09:43.590> hash<00:09:43.830> if<00:09:44.370> there's<00:09:45.120> you<00:09:45.180> know<00:09:45.240> hard<00:09:45.600> fork 00:09:45.950 --> 00:09:45.960 align:start position:0% block hash if there's you know hard fork 00:09:45.960 --> 00:09:47.960 align:start position:0% block hash if there's you know hard fork then<00:09:46.440> we<00:09:46.530> can<00:09:46.710> use<00:09:46.860> the<00:09:46.980> transaction<00:09:47.550> receipts 00:09:47.960 --> 00:09:47.970 align:start position:0% then we can use the transaction receipts 00:09:47.970 --> 00:09:51.140 align:start position:0% then we can use the transaction receipts and<00:09:48.300> a<00:09:48.840> block<00:09:49.140> as<00:09:49.470> evidence<00:09:50.370> that<00:09:50.430> Pisa<00:09:50.760> didn't 00:09:51.140 --> 00:09:51.150 align:start position:0% and a block as evidence that Pisa didn't 00:09:51.150 --> 00:09:53.030 align:start position:0% and a block as evidence that Pisa didn't do<00:09:51.240> its<00:09:51.390> job<00:09:51.630> if<00:09:52.470> you<00:09:52.560> wanted<00:09:52.770> or<00:09:52.890> more 00:09:53.030 --> 00:09:53.040 align:start position:0% do its job if you wanted or more 00:09:53.040 --> 00:09:55.160 align:start position:0% do its job if you wanted or more information<00:09:53.550> about<00:09:53.640> that<00:09:53.790> just<00:09:54.780> check<00:09:54.990> out 00:09:55.160 --> 00:09:55.170 align:start position:0% information about that just check out 00:09:55.170 --> 00:09:57.110 align:start position:0% information about that just check out this<00:09:55.290> wonderful<00:09:55.800> blog<00:09:55.980> post<00:09:56.340> that<00:09:56.820> Chris 00:09:57.110 --> 00:09:57.120 align:start position:0% this wonderful blog post that Chris 00:09:57.120 --> 00:10:01.040 align:start position:0% this wonderful blog post that Chris wrote<00:09:57.360> oh<00:09:59.150> and<00:10:00.150> I<00:10:00.180> also<00:10:00.330> found<00:10:00.570> this<00:10:00.750> emoji 00:10:01.040 --> 00:10:01.050 align:start position:0% wrote oh and I also found this emoji 00:10:01.050 --> 00:10:03.230 align:start position:0% wrote oh and I also found this emoji I'll<00:10:01.740> try<00:10:01.920> to<00:10:01.980> find<00:10:02.190> a<00:10:02.250> fork<00:10:02.490> emoji<00:10:02.910> so<00:10:03.089> if<00:10:03.180> you 00:10:03.230 --> 00:10:03.240 align:start position:0% I'll try to find a fork emoji so if you 00:10:03.240 --> 00:10:06.079 align:start position:0% I'll try to find a fork emoji so if you want<00:10:03.390> to<00:10:03.450> get<00:10:04.140> this<00:10:04.260> in<00:10:04.410> the<00:10:04.500> iOS<00:10:04.850> and<00:10:05.850> it<00:10:06.000> was 00:10:06.079 --> 00:10:06.089 align:start position:0% want to get this in the iOS and it was 00:10:06.089 --> 00:10:09.470 align:start position:0% want to get this in the iOS and it was sign<00:10:06.270> up<00:10:06.450> to<00:10:06.630> the<00:10:06.780> Chien's<00:10:07.200> org<00:10:08.180> so<00:10:09.180> what's<00:10:09.360> the 00:10:09.470 --> 00:10:09.480 align:start position:0% sign up to the Chien's org so what's the 00:10:09.480 --> 00:10:11.329 align:start position:0% sign up to the Chien's org so what's the current<00:10:09.690> state<00:10:09.930> of<00:10:09.990> the<00:10:10.170> PISA<00:10:10.380> project<00:10:10.980> you 00:10:11.329 --> 00:10:11.339 align:start position:0% current state of the PISA project you 00:10:11.339 --> 00:10:12.200 align:start position:0% current state of the PISA project you know<00:10:11.460> this<00:10:11.640> is<00:10:11.760> something<00:10:12.089> we've<00:10:12.180> been 00:10:12.200 --> 00:10:12.210 align:start position:0% know this is something we've been 00:10:12.210 --> 00:10:14.329 align:start position:0% know this is something we've been working<00:10:12.450> on<00:10:12.750> for<00:10:12.780> two<00:10:13.050> years<00:10:13.080> in<00:10:13.680> terms<00:10:14.250> of 00:10:14.329 --> 00:10:14.339 align:start position:0% working on for two years in terms of 00:10:14.339 --> 00:10:16.160 align:start position:0% working on for two years in terms of designing<00:10:14.610> the<00:10:14.760> protocol<00:10:15.240> and<00:10:15.540> now<00:10:16.020> we've 00:10:16.160 --> 00:10:16.170 align:start position:0% designing the protocol and now we've 00:10:16.170 --> 00:10:17.960 align:start position:0% designing the protocol and now we've been<00:10:16.290> trying<00:10:16.500> to<00:10:16.560> implement<00:10:17.100> it<00:10:17.310> for<00:10:17.670> the<00:10:17.760> past 00:10:17.960 --> 00:10:17.970 align:start position:0% been trying to implement it for the past 00:10:17.970 --> 00:10:21.310 align:start position:0% been trying to implement it for the past six<00:10:18.300> months<00:10:19.339> what's<00:10:20.339> nice<00:10:20.550> is<00:10:20.790> that<00:10:20.820> we 00:10:21.310 --> 00:10:21.320 align:start position:0% six months what's nice is that we 00:10:21.320 --> 00:10:23.360 align:start position:0% six months what's nice is that we envisioned<00:10:22.320> it<00:10:22.410> to<00:10:22.440> be<00:10:22.620> like<00:10:22.770> an<00:10:22.890> inferior 00:10:23.360 --> 00:10:23.370 align:start position:0% envisioned it to be like an inferior 00:10:23.370 --> 00:10:26.510 align:start position:0% envisioned it to be like an inferior Lake<00:10:23.520> API<00:10:24.060> as<00:10:24.480> a<00:10:24.540> top<00:10:25.410> developer<00:10:26.040> you're 00:10:26.510 --> 00:10:26.520 align:start position:0% Lake API as a top developer you're 00:10:26.520 --> 00:10:28.460 align:start position:0% Lake API as a top developer you're simply<00:10:26.910> gonna<00:10:27.030> have<00:10:27.150> a<00:10:27.210> very<00:10:27.390> simple<00:10:27.810> API<00:10:28.020> like 00:10:28.460 --> 00:10:28.470 align:start position:0% simply gonna have a very simple API like 00:10:28.470 --> 00:10:31.430 align:start position:0% simply gonna have a very simple API like this<00:10:28.740> you<00:10:29.610> tell<00:10:29.940> Peter<00:10:30.210> when<00:10:31.080> do<00:10:31.230> you<00:10:31.320> need 00:10:31.430 --> 00:10:31.440 align:start position:0% this you tell Peter when do you need 00:10:31.440 --> 00:10:33.710 align:start position:0% this you tell Peter when do you need that<00:10:31.589> transaction<00:10:32.130> delivered<00:10:32.550> what<00:10:33.420> was<00:10:33.570> the 00:10:33.710 --> 00:10:33.720 align:start position:0% that transaction delivered what was the 00:10:33.720 --> 00:10:35.930 align:start position:0% that transaction delivered what was the code<00:10:33.990> theater<00:10:34.500> and<00:10:34.710> what<00:10:35.250> is<00:10:35.370> the<00:10:35.520> contract 00:10:35.930 --> 00:10:35.940 align:start position:0% code theater and what is the contract 00:10:35.940 --> 00:10:39.470 align:start position:0% code theater and what is the contract address<00:10:36.740> you<00:10:37.740> simply<00:10:38.130> call<00:10:38.370> the<00:10:38.520> API<00:10:38.880> and<00:10:39.240> in 00:10:39.470 --> 00:10:39.480 align:start position:0% address you simply call the API and in 00:10:39.480 --> 00:10:41.570 align:start position:0% address you simply call the API and in return<00:10:39.870> you'll<00:10:40.410> get<00:10:40.650> a<00:10:40.680> signed<00:10:40.980> receipt<00:10:41.339> and 00:10:41.570 --> 00:10:41.580 align:start position:0% return you'll get a signed receipt and 00:10:41.580 --> 00:10:44.810 align:start position:0% return you'll get a signed receipt and that's<00:10:42.390> awesome<00:10:42.930> and<00:10:43.310> right<00:10:44.310> now<00:10:44.460> our<00:10:44.490> current 00:10:44.810 --> 00:10:44.820 align:start position:0% that's awesome and right now our current 00:10:44.820 --> 00:10:48.110 align:start position:0% that's awesome and right now our current guinea<00:10:45.120> pigs<00:10:45.480> are<00:10:45.870> connects<00:10:46.530> and<00:10:46.860> l4<00:10:47.370> so<00:10:47.970> now 00:10:48.110 --> 00:10:48.120 align:start position:0% guinea pigs are connects and l4 so now 00:10:48.120 --> 00:10:49.010 align:start position:0% guinea pigs are connects and l4 so now we're<00:10:48.240> actually<00:10:48.330> trying<00:10:48.720> to<00:10:48.810> do<00:10:48.930> an 00:10:49.010 --> 00:10:49.020 align:start position:0% we're actually trying to do an 00:10:49.020 --> 00:10:50.810 align:start position:0% we're actually trying to do an integration<00:10:49.380> to<00:10:50.070> see<00:10:50.250> how<00:10:50.400> well<00:10:50.580> this<00:10:50.760> works 00:10:50.810 --> 00:10:50.820 align:start position:0% integration to see how well this works 00:10:50.820 --> 00:10:53.780 align:start position:0% integration to see how well this works and<00:10:51.450> once<00:10:52.080> it<00:10:52.230> works<00:10:52.410> everyone<00:10:53.130> here<00:10:53.370> can<00:10:53.520> try 00:10:53.780 --> 00:10:53.790 align:start position:0% and once it works everyone here can try 00:10:53.790 --> 00:10:56.480 align:start position:0% and once it works everyone here can try it<00:10:53.850> out<00:10:54.060> and<00:10:54.440> of<00:10:55.440> course<00:10:55.500> if<00:10:55.920> you<00:10:56.010> want<00:10:56.190> to<00:10:56.280> find 00:10:56.480 --> 00:10:56.490 align:start position:0% it out and of course if you want to find 00:10:56.490 --> 00:10:58.760 align:start position:0% it out and of course if you want to find more<00:10:56.610> information<00:10:56.670> about<00:10:57.300> it<00:10:57.690> our<00:10:58.020> client 00:10:58.760 --> 00:10:58.770 align:start position:0% more information about it our client 00:10:58.770 --> 00:11:03.110 align:start position:0% more information about it our client information<00:10:59.040> is<00:10:59.430> on<00:10:59.550> an<00:10:59.760> new<00:11:00.000> MP<00:11:00.540> MP<00:11:00.780> m<00:11:01.760> Jas<00:11:02.760> and 00:11:03.110 --> 00:11:03.120 align:start position:0% information is on an new MP MP m Jas and 00:11:03.120 --> 00:11:05.720 align:start position:0% information is on an new MP MP m Jas and everything's<00:11:03.960> open<00:11:04.320> source<00:11:04.589> so<00:11:05.430> you<00:11:05.460> can<00:11:05.520> just 00:11:05.720 --> 00:11:05.730 align:start position:0% everything's open source so you can just 00:11:05.730 --> 00:11:07.220 align:start position:0% everything's open source so you can just look<00:11:05.820> at<00:11:05.970> this<00:11:06.060> repo<00:11:06.540> and<00:11:06.720> you<00:11:06.900> can<00:11:07.020> see 00:11:07.220 --> 00:11:07.230 align:start position:0% look at this repo and you can see 00:11:07.230 --> 00:11:09.290 align:start position:0% look at this repo and you can see exactly<00:11:07.589> how<00:11:07.830> Pisa<00:11:08.100> works<00:11:08.339> today<00:11:08.580> you<00:11:09.150> know 00:11:09.290 --> 00:11:09.300 align:start position:0% exactly how Pisa works today you know 00:11:09.300 --> 00:11:11.370 align:start position:0% exactly how Pisa works today you know and<00:11:09.330> try<00:11:09.630> it<00:11:09.690> locally<00:11:10.020> amongst<00:11:10.320> yourselves 00:11:11.370 --> 00:11:11.380 align:start position:0% and try it locally amongst yourselves 00:11:11.380 --> 00:11:15.120 align:start position:0% and try it locally amongst yourselves now<00:11:12.370> where's<00:11:12.610> Pisa<00:11:13.060> a<00:11:13.450> boring<00:11:14.140> tedious<00:11:14.620> and 00:11:15.120 --> 00:11:15.130 align:start position:0% now where's Pisa a boring tedious and 00:11:15.130 --> 00:11:19.470 align:start position:0% now where's Pisa a boring tedious and hard<00:11:15.460> project<00:11:16.560> actually<00:11:17.560> Pisa<00:11:18.430> is<00:11:18.820> a<00:11:18.850> high 00:11:19.470 --> 00:11:19.480 align:start position:0% hard project actually Pisa is a high 00:11:19.480 --> 00:11:22.350 align:start position:0% hard project actually Pisa is a high availability<00:11:20.020> reliability<00:11:21.010> and<00:11:21.820> fault 00:11:22.350 --> 00:11:22.360 align:start position:0% availability reliability and fault 00:11:22.360 --> 00:11:25.430 align:start position:0% availability reliability and fault tolerant<00:11:22.960> project<00:11:23.700> what<00:11:24.700> do<00:11:24.760> I<00:11:24.820> mean<00:11:25.000> by<00:11:25.060> that 00:11:25.430 --> 00:11:25.440 align:start position:0% tolerant project what do I mean by that 00:11:25.440 --> 00:11:29.010 align:start position:0% tolerant project what do I mean by that so<00:11:26.440> if<00:11:26.560> you're<00:11:26.680> a<00:11:26.710> dub<00:11:26.980> developer<00:11:27.610> and<00:11:28.180> you've 00:11:29.010 --> 00:11:29.020 align:start position:0% so if you're a dub developer and you've 00:11:29.020 --> 00:11:30.870 align:start position:0% so if you're a dub developer and you've got<00:11:29.200> a<00:11:29.230> guarantee<00:11:29.680> transactions<00:11:30.520> for<00:11:30.730> your 00:11:30.870 --> 00:11:30.880 align:start position:0% got a guarantee transactions for your 00:11:30.880 --> 00:11:33.180 align:start position:0% got a guarantee transactions for your users<00:11:31.330> get<00:11:31.570> in<00:11:31.690> the<00:11:31.780> blockchain<00:11:32.070> once<00:11:33.070> you've 00:11:33.180 --> 00:11:33.190 align:start position:0% users get in the blockchain once you've 00:11:33.190 --> 00:11:35.160 align:start position:0% users get in the blockchain once you've got<00:11:33.340> to<00:11:33.460> worry<00:11:33.670> about<00:11:33.760> is<00:11:34.330> bumping<00:11:35.020> the 00:11:35.160 --> 00:11:35.170 align:start position:0% got to worry about is bumping the 00:11:35.170 --> 00:11:37.410 align:start position:0% got to worry about is bumping the feature<00:11:35.650> in<00:11:35.770> congestion<00:11:36.460> you've<00:11:37.120> got<00:11:37.300> to 00:11:37.410 --> 00:11:37.420 align:start position:0% feature in congestion you've got to 00:11:37.420 --> 00:11:39.000 align:start position:0% feature in congestion you've got to worry<00:11:37.510> about<00:11:37.600> managing<00:11:37.960> the<00:11:38.290> balance<00:11:38.770> of 00:11:39.000 --> 00:11:39.010 align:start position:0% worry about managing the balance of 00:11:39.010 --> 00:11:41.370 align:start position:0% worry about managing the balance of multiple<00:11:39.730> hot<00:11:39.910> wallis<00:11:40.270> to<00:11:40.420> pay<00:11:40.540> for<00:11:40.750> gas 00:11:41.370 --> 00:11:41.380 align:start position:0% multiple hot wallis to pay for gas 00:11:41.380 --> 00:11:43.200 align:start position:0% multiple hot wallis to pay for gas managing<00:11:42.160> dependent<00:11:42.820> and<00:11:42.940> chiyan 00:11:43.200 --> 00:11:43.210 align:start position:0% managing dependent and chiyan 00:11:43.210 --> 00:11:45.870 align:start position:0% managing dependent and chiyan transactions<00:11:44.170> handling<00:11:44.890> block<00:11:45.160> readers<00:11:45.580> and 00:11:45.870 --> 00:11:45.880 align:start position:0% transactions handling block readers and 00:11:45.880 --> 00:11:48.150 align:start position:0% transactions handling block readers and hard<00:11:46.060> Forks<00:11:46.680> detecting<00:11:47.680> these<00:11:47.770> emitted 00:11:48.150 --> 00:11:48.160 align:start position:0% hard Forks detecting these emitted 00:11:48.160 --> 00:11:50.640 align:start position:0% hard Forks detecting these emitted events<00:11:48.580> taking<00:11:49.300> data<00:11:49.540> from<00:11:49.720> it<00:11:50.110> and<00:11:50.290> using 00:11:50.640 --> 00:11:50.650 align:start position:0% events taking data from it and using 00:11:50.650 --> 00:11:52.770 align:start position:0% events taking data from it and using that<00:11:50.710> as<00:11:50.860> part<00:11:51.070> of<00:11:51.130> the<00:11:51.250> response<00:11:51.640> I'm<00:11:52.540> one 00:11:52.770 --> 00:11:52.780 align:start position:0% that as part of the response I'm one 00:11:52.780 --> 00:11:54.720 align:start position:0% that as part of the response I'm one really<00:11:52.990> good<00:11:53.140> example<00:11:53.200> of<00:11:53.680> this<00:11:53.860> was<00:11:54.220> defy<00:11:54.670> see 00:11:54.720 --> 00:11:54.730 align:start position:0% really good example of this was defy see 00:11:54.730 --> 00:11:56.820 align:start position:0% really good example of this was defy see ever<00:11:55.180> you<00:11:55.870> know<00:11:55.960> if<00:11:56.050> you<00:11:56.110> combine<00:11:56.410> if<00:11:56.680> you 00:11:56.820 --> 00:11:56.830 align:start position:0% ever you know if you combine if you 00:11:56.830 --> 00:11:59.010 align:start position:0% ever you know if you combine if you picked<00:11:57.100> here<00:11:57.460> more<00:11:57.670> of<00:11:57.700> the<00:11:57.910> above<00:11:58.210> it<00:11:58.810> could 00:11:59.010 --> 00:11:59.020 align:start position:0% picked here more of the above it could 00:11:59.020 --> 00:12:02.430 align:start position:0% picked here more of the above it could become<00:11:59.110> non-trivial<00:11:59.710> so<00:12:00.520> device<00:12:01.030> chin<00:12:01.540> C<00:12:02.200> ever 00:12:02.430 --> 00:12:02.440 align:start position:0% become non-trivial so device chin C ever 00:12:02.440 --> 00:12:05.250 align:start position:0% become non-trivial so device chin C ever had<00:12:02.830> a<00:12:02.860> chiyan<00:12:03.280> transaction<00:12:04.090> but<00:12:04.990> in<00:12:05.110> the 00:12:05.250 --> 00:12:05.260 align:start position:0% had a chiyan transaction but in the 00:12:05.260 --> 00:12:07.500 align:start position:0% had a chiyan transaction but in the chiyan<00:12:05.710> the<00:12:06.190> first<00:12:06.550> transaction<00:12:07.000> had<00:12:07.270> a<00:12:07.300> low 00:12:07.500 --> 00:12:07.510 align:start position:0% chiyan the first transaction had a low 00:12:07.510 --> 00:12:10.560 align:start position:0% chiyan the first transaction had a low fee<00:12:07.890> it<00:12:08.890> had<00:12:09.040> a<00:12:09.070> low<00:12:09.310> fee<00:12:09.610> and<00:12:10.090> it<00:12:10.180> didn't<00:12:10.450> get 00:12:10.560 --> 00:12:10.570 align:start position:0% fee it had a low fee and it didn't get 00:12:10.570 --> 00:12:12.780 align:start position:0% fee it had a low fee and it didn't get in<00:12:10.720> which<00:12:11.380> meant<00:12:11.680> the<00:12:11.800> other<00:12:12.010> transactions 00:12:12.780 --> 00:12:12.790 align:start position:0% in which meant the other transactions 00:12:12.790 --> 00:12:15.450 align:start position:0% in which meant the other transactions also<00:12:13.240> didn't<00:12:13.570> get<00:12:13.660> in<00:12:13.840> so<00:12:14.830> this<00:12:15.010> is<00:12:15.070> actually<00:12:15.430> a 00:12:15.450 --> 00:12:15.460 align:start position:0% also didn't get in so this is actually a 00:12:15.460 --> 00:12:17.220 align:start position:0% also didn't get in so this is actually a non-trivial<00:12:15.940> problem<00:12:16.180> the<00:12:16.600> builds<00:12:17.020> and 00:12:17.220 --> 00:12:17.230 align:start position:0% non-trivial problem the builds and 00:12:17.230 --> 00:12:19.800 align:start position:0% non-trivial problem the builds and actually<00:12:18.220> most<00:12:18.400> projects<00:12:19.120> have<00:12:19.300> to<00:12:19.420> do<00:12:19.600> this 00:12:19.800 --> 00:12:19.810 align:start position:0% actually most projects have to do this 00:12:19.810 --> 00:12:22.230 align:start position:0% actually most projects have to do this with<00:12:20.560> sort<00:12:20.800> of<00:12:20.860> sucks<00:12:21.130> has<00:12:21.520> taken<00:12:21.820> us<00:12:21.910> four<00:12:22.150> or 00:12:22.230 --> 00:12:22.240 align:start position:0% with sort of sucks has taken us four or 00:12:22.240 --> 00:12:24.480 align:start position:0% with sort of sucks has taken us four or five<00:12:22.420> months<00:12:22.870> to<00:12:23.350> get<00:12:23.440> an<00:12:23.560> alpha<00:12:23.770> version<00:12:24.130> that 00:12:24.480 --> 00:12:24.490 align:start position:0% five months to get an alpha version that 00:12:24.490 --> 00:12:26.610 align:start position:0% five months to get an alpha version that we're<00:12:24.640> sort<00:12:24.880> of<00:12:25.000> comfortable<00:12:25.540> with<00:12:25.660> and<00:12:26.440> we 00:12:26.610 --> 00:12:26.620 align:start position:0% we're sort of comfortable with and we 00:12:26.620 --> 00:12:28.740 align:start position:0% we're sort of comfortable with and we expected<00:12:27.130> to<00:12:27.280> every<00:12:27.610> team<00:12:27.850> to<00:12:28.000> replicate<00:12:28.540> this 00:12:28.740 --> 00:12:28.750 align:start position:0% expected to every team to replicate this 00:12:28.750 --> 00:12:30.570 align:start position:0% expected to every team to replicate this you've<00:12:29.410> already<00:12:29.500> lost<00:12:29.860> four<00:12:30.100> or<00:12:30.220> five<00:12:30.370> months 00:12:30.570 --> 00:12:30.580 align:start position:0% you've already lost four or five months 00:12:30.580 --> 00:12:32.880 align:start position:0% you've already lost four or five months of<00:12:30.670> engineering<00:12:31.210> time<00:12:31.440> so<00:12:32.440> that's<00:12:32.560> exactly 00:12:32.880 --> 00:12:32.890 align:start position:0% of engineering time so that's exactly 00:12:32.890 --> 00:12:34.590 align:start position:0% of engineering time so that's exactly why<00:12:33.130> I<00:12:33.160> think<00:12:33.430> P's<00:12:33.610> is<00:12:33.760> useful<00:12:34.090> for<00:12:34.210> move<00:12:34.390> stop 00:12:34.590 --> 00:12:34.600 align:start position:0% why I think P's is useful for move stop 00:12:34.600 --> 00:12:37.650 align:start position:0% why I think P's is useful for move stop developers<00:12:35.820> now<00:12:36.820> what<00:12:36.970> about<00:12:37.060> the<00:12:37.270> future<00:12:37.540> of 00:12:37.650 --> 00:12:37.660 align:start position:0% developers now what about the future of 00:12:37.660 --> 00:12:40.980 align:start position:0% developers now what about the future of Pisa<00:12:38.460> what<00:12:39.460> I<00:12:39.490> really<00:12:39.850> want<00:12:40.030> to<00:12:40.150> build<00:12:40.360> is<00:12:40.750> a 00:12:40.980 --> 00:12:40.990 align:start position:0% Pisa what I really want to build is a 00:12:40.990 --> 00:12:44.160 align:start position:0% Pisa what I really want to build is a watching<00:12:41.380> pool<00:12:42.090> okay<00:12:43.120> so<00:12:43.450> typically<00:12:43.960> when 00:12:44.160 --> 00:12:44.170 align:start position:0% watching pool okay so typically when 00:12:44.170 --> 00:12:45.480 align:start position:0% watching pool okay so typically when people<00:12:44.200> think<00:12:44.620> about<00:12:44.740> these<00:12:45.040> watching 00:12:45.480 --> 00:12:45.490 align:start position:0% people think about these watching 00:12:45.490 --> 00:12:47.820 align:start position:0% people think about these watching networks<00:12:45.960> every<00:12:46.960> all<00:12:47.140> the<00:12:47.290> watchers<00:12:47.620> are<00:12:47.740> in 00:12:47.820 --> 00:12:47.830 align:start position:0% networks every all the watchers are in 00:12:47.830 --> 00:12:50.040 align:start position:0% networks every all the watchers are in competition<00:12:48.330> we're<00:12:49.330> actually<00:12:49.540> you<00:12:49.960> gonna 00:12:50.040 --> 00:12:50.050 align:start position:0% competition we're actually you gonna 00:12:50.050 --> 00:12:52.320 align:start position:0% competition we're actually you gonna have<00:12:50.170> a<00:12:50.230> pool<00:12:50.470> real<00:12:51.430> there's<00:12:51.670> non<00:12:51.850> trusted 00:12:52.320 --> 00:12:52.330 align:start position:0% have a pool real there's non trusted 00:12:52.330 --> 00:12:54.720 align:start position:0% have a pool real there's non trusted coordinator<00:12:52.840> you<00:12:53.680> know<00:12:53.770> I<00:12:53.800> send<00:12:54.190> the<00:12:54.310> job<00:12:54.580> to 00:12:54.720 --> 00:12:54.730 align:start position:0% coordinator you know I send the job to 00:12:54.730 --> 00:12:56.910 align:start position:0% coordinator you know I send the job to the<00:12:54.820> Pisa<00:12:55.060> server<00:12:55.450> the<00:12:56.170> Pisa<00:12:56.440> server<00:12:56.800> will 00:12:56.910 --> 00:12:56.920 align:start position:0% the Pisa server the Pisa server will 00:12:56.920 --> 00:12:59.280 align:start position:0% the Pisa server the Pisa server will send<00:12:57.130> their<00:12:57.280> job<00:12:57.430> to<00:12:57.550> each<00:12:57.700> watcher<00:12:58.240> and<00:12:58.420> we 00:12:59.280 --> 00:12:59.290 align:start position:0% send their job to each watcher and we 00:12:59.290 --> 00:13:01.860 align:start position:0% send their job to each watcher and we get<00:12:59.500> Caravan<00:13:00.100> Watchers<00:13:00.520> or<00:13:00.670> green<00:13:00.880> we<00:13:01.660> get<00:13:01.840> a 00:13:01.860 --> 00:13:01.870 align:start position:0% get Caravan Watchers or green we get a 00:13:01.870 --> 00:13:03.630 align:start position:0% get Caravan Watchers or green we get a fully<00:13:02.230> signed<00:13:02.410> receipt<00:13:02.800> then<00:13:03.280> the<00:13:03.460> sign 00:13:03.630 --> 00:13:03.640 align:start position:0% fully signed receipt then the sign 00:13:03.640 --> 00:13:05.730 align:start position:0% fully signed receipt then the sign receipt<00:13:03.970> goes<00:13:04.090> out<00:13:04.210> to<00:13:04.390> the<00:13:04.480> customer<00:13:04.930> so 00:13:05.730 --> 00:13:05.740 align:start position:0% receipt goes out to the customer so 00:13:05.740 --> 00:13:07.710 align:start position:0% receipt goes out to the customer so actually<00:13:06.250> all<00:13:06.430> the<00:13:06.910> Watchers<00:13:07.270> are<00:13:07.420> watching 00:13:07.710 --> 00:13:07.720 align:start position:0% actually all the Watchers are watching 00:13:07.720 --> 00:13:08.520 align:start position:0% actually all the Watchers are watching each<00:13:07.810> other's<00:13:08.050> backs 00:13:08.520 --> 00:13:08.530 align:start position:0% each other's backs 00:13:08.530 --> 00:13:11.490 align:start position:0% each other's backs so<00:13:09.130> Alisa's<00:13:09.460> you<00:13:09.580> know<00:13:09.670> we<00:13:10.480> know<00:13:10.840> our<00:13:11.080> service 00:13:11.490 --> 00:13:11.500 align:start position:0% so Alisa's you know we know our service 00:13:11.500 --> 00:13:13.650 align:start position:0% so Alisa's you know we know our service gets<00:13:11.680> tossed<00:13:11.980> hopefully<00:13:12.730> one<00:13:12.910> remains<00:13:13.210> online 00:13:13.650 --> 00:13:13.660 align:start position:0% gets tossed hopefully one remains online 00:13:13.660 --> 00:13:16.050 align:start position:0% gets tossed hopefully one remains online there's<00:13:14.620> also<00:13:14.740> the<00:13:14.920> motivation<00:13:15.490> for<00:13:15.580> n<00:13:15.730> level 00:13:16.050 --> 00:13:16.060 align:start position:0% there's also the motivation for n level 00:13:16.060 --> 00:13:19.800 align:start position:0% there's also the motivation for n level programming<00:13:16.510> the<00:13:16.990> avoid<00:13:17.260> critical<00:13:17.710> bugs<00:13:18.810> now 00:13:19.800 --> 00:13:19.810 align:start position:0% programming the avoid critical bugs now 00:13:19.810 --> 00:13:21.240 align:start position:0% programming the avoid critical bugs now what<00:13:19.990> about<00:13:20.110> the<00:13:20.320> security<00:13:20.710> clutter<00:13:21.100> or 00:13:21.240 --> 00:13:21.250 align:start position:0% what about the security clutter or 00:13:21.250 --> 00:13:21.870 align:start position:0% what about the security clutter or lockup 00:13:21.870 --> 00:13:21.880 align:start position:0% lockup 00:13:21.880 --> 00:13:24.420 align:start position:0% lockup a<00:13:21.940> lot<00:13:22.810> of<00:13:22.840> people<00:13:23.140> ask<00:13:23.290> about<00:13:23.620> this<00:13:23.830> you<00:13:24.370> know 00:13:24.420 --> 00:13:24.430 align:start position:0% a lot of people ask about this you know 00:13:24.430 --> 00:13:25.230 align:start position:0% a lot of people ask about this you know one<00:13:24.580> of<00:13:24.610> the<00:13:24.730> me 00:13:25.230 --> 00:13:25.240 align:start position:0% one of the me 00:13:25.240 --> 00:13:27.870 align:start position:0% one of the me of<00:13:25.810> Pisa<00:13:26.050> is<00:13:26.440> that<00:13:26.890> we<00:13:27.010> may<00:13:27.250> have<00:13:27.339> to<00:13:27.520> lock<00:13:27.700> up 00:13:27.870 --> 00:13:27.880 align:start position:0% of Pisa is that we may have to lock up 00:13:27.880 --> 00:13:30.000 align:start position:0% of Pisa is that we may have to lock up 50k<00:13:28.420> dollars<00:13:28.930> there<00:13:29.290> really<00:13:29.560> sure<00:13:29.740> that<00:13:29.890> we 00:13:30.000 --> 00:13:30.010 align:start position:0% 50k dollars there really sure that we 00:13:30.010 --> 00:13:32.250 align:start position:0% 50k dollars there really sure that we have<00:13:30.130> skin<00:13:30.399> in<00:13:30.520> the<00:13:30.610> game<00:13:30.720> well<00:13:31.720> it's<00:13:31.810> nice<00:13:31.990> is 00:13:32.250 --> 00:13:32.260 align:start position:0% have skin in the game well it's nice is 00:13:32.260 --> 00:13:35.160 align:start position:0% have skin in the game well it's nice is that<00:13:32.290> we<00:13:32.770> can<00:13:33.160> outsource<00:13:33.640> that<00:13:33.880> other<00:13:34.540> people 00:13:35.160 --> 00:13:35.170 align:start position:0% that we can outsource that other people 00:13:35.170 --> 00:13:36.870 align:start position:0% that we can outsource that other people can<00:13:35.320> donate<00:13:35.470> the<00:13:35.740> money<00:13:35.920> in<00:13:36.040> our<00:13:36.160> behalf<00:13:36.459> and 00:13:36.870 --> 00:13:36.880 align:start position:0% can donate the money in our behalf and 00:13:36.880 --> 00:13:38.400 align:start position:0% can donate the money in our behalf and they're<00:13:37.420> sort<00:13:37.570> of<00:13:37.630> betting<00:13:38.110> on<00:13:38.260> our 00:13:38.400 --> 00:13:38.410 align:start position:0% they're sort of betting on our 00:13:38.410 --> 00:13:40.620 align:start position:0% they're sort of betting on our reputation<00:13:39.220> that<00:13:39.490> we<00:13:39.550> won't<00:13:39.820> get<00:13:39.970> slashed<00:13:40.270> I'm 00:13:40.620 --> 00:13:40.630 align:start position:0% reputation that we won't get slashed I'm 00:13:40.630 --> 00:13:43.110 align:start position:0% reputation that we won't get slashed I'm by<00:13:41.140> betting<00:13:41.380> on<00:13:41.529> our<00:13:41.680> reputation<00:13:41.950> you<00:13:42.910> get<00:13:43.089> a 00:13:43.110 --> 00:13:43.120 align:start position:0% by betting on our reputation you get a 00:13:43.120 --> 00:13:45.180 align:start position:0% by betting on our reputation you get a share<00:13:43.390> of<00:13:43.480> that<00:13:43.600> revenue<00:13:43.959> and<00:13:44.770> we<00:13:44.890> can<00:13:45.040> also 00:13:45.180 --> 00:13:45.190 align:start position:0% share of that revenue and we can also 00:13:45.190 --> 00:13:46.980 align:start position:0% share of that revenue and we can also just<00:13:45.399> lock<00:13:45.670> it<00:13:45.700> up<00:13:45.910> a<00:13:46.060> maker<00:13:46.300> and<00:13:46.540> compound 00:13:46.980 --> 00:13:46.990 align:start position:0% just lock it up a maker and compound 00:13:46.990 --> 00:13:48.990 align:start position:0% just lock it up a maker and compound then<00:13:47.560> use<00:13:47.770> that<00:13:47.800> money<00:13:47.950> to<00:13:48.250> earn<00:13:48.310> interest<00:13:48.580> as 00:13:48.990 --> 00:13:49.000 align:start position:0% then use that money to earn interest as 00:13:49.000 --> 00:13:50.490 align:start position:0% then use that money to earn interest as well<00:13:49.120> there's<00:13:49.839> actually<00:13:50.080> quite<00:13:50.200> nice<00:13:50.470> you 00:13:50.490 --> 00:13:50.500 align:start position:0% well there's actually quite nice you 00:13:50.500 --> 00:13:51.690 align:start position:0% well there's actually quite nice you know<00:13:50.709> the<00:13:50.800> money<00:13:50.980> doesn't<00:13:51.310> go<00:13:51.399> to<00:13:51.459> whist 00:13:51.690 --> 00:13:51.700 align:start position:0% know the money doesn't go to whist 00:13:51.700 --> 00:13:55.440 align:start position:0% know the money doesn't go to whist there's<00:13:52.570> a<00:13:52.630> real<00:13:52.810> store<00:13:53.110> of<00:13:53.200> all<00:13:53.350> you<00:13:54.420> now<00:13:55.420> I 00:13:55.440 --> 00:13:55.450 align:start position:0% there's a real store of all you now I 00:13:55.450 --> 00:13:57.030 align:start position:0% there's a real store of all you now I just<00:13:55.690> want<00:13:55.839> to<00:13:55.930> finish<00:13:56.200> to<00:13:56.410> my<00:13:56.529> takeaway 00:13:57.030 --> 00:13:57.040 align:start position:0% just want to finish to my takeaway 00:13:57.040 --> 00:14:00.230 align:start position:0% just want to finish to my takeaway message<00:13:57.459> of<00:13:57.790> all<00:13:58.240> of<00:13:58.390> this<00:13:58.510> you<00:13:58.690> know<00:13:58.770> talk 00:14:00.230 --> 00:14:00.240 align:start position:0% message of all of this you know talk 00:14:00.240 --> 00:14:03.630 align:start position:0% message of all of this you know talk what<00:14:01.240> makes<00:14:01.480> cryptocurrency<00:14:02.170> so<00:14:02.649> grit<00:14:02.950> you 00:14:03.630 --> 00:14:03.640 align:start position:0% what makes cryptocurrency so grit you 00:14:03.640 --> 00:14:05.340 align:start position:0% what makes cryptocurrency so grit you know<00:14:03.790> why<00:14:03.970> are<00:14:04.029> we<00:14:04.149> all<00:14:04.390> excited<00:14:04.540> about<00:14:04.990> it 00:14:05.340 --> 00:14:05.350 align:start position:0% know why are we all excited about it 00:14:05.350 --> 00:14:06.990 align:start position:0% know why are we all excited about it from<00:14:06.040> my<00:14:06.220> perspective 00:14:06.990 --> 00:14:07.000 align:start position:0% from my perspective 00:14:07.000 --> 00:14:08.970 align:start position:0% from my perspective what<00:14:07.390> makes<00:14:07.600> cryptocurrency<00:14:08.050> so<00:14:08.440> grit<00:14:08.709> is 00:14:08.970 --> 00:14:08.980 align:start position:0% what makes cryptocurrency so grit is 00:14:08.980 --> 00:14:11.310 align:start position:0% what makes cryptocurrency so grit is that<00:14:09.640> everything<00:14:10.270> is<00:14:10.450> publicly<00:14:11.050> verifiable 00:14:11.310 --> 00:14:11.320 align:start position:0% that everything is publicly verifiable 00:14:11.320 --> 00:14:13.530 align:start position:0% that everything is publicly verifiable and<00:14:12.190> we<00:14:12.640> have<00:14:12.730> a<00:14:12.760> set<00:14:13.000> of<00:14:13.089> you<00:14:13.240> know<00:14:13.300> we<00:14:13.390> have<00:14:13.510> a 00:14:13.530 --> 00:14:13.540 align:start position:0% and we have a set of you know we have a 00:14:13.540 --> 00:14:16.440 align:start position:0% and we have a set of you know we have a decentralized<00:14:14.500> set<00:14:14.740> of<00:14:14.890> validators<00:14:15.520> I<00:14:15.730> don't 00:14:16.440 --> 00:14:16.450 align:start position:0% decentralized set of validators I don't 00:14:16.450 --> 00:14:18.630 align:start position:0% decentralized set of validators I don't in<00:14:16.570> the<00:14:16.660> world<00:14:16.870> can<00:14:17.589> volunteer<00:14:18.100> blocks<00:14:18.459> in 00:14:18.630 --> 00:14:18.640 align:start position:0% in the world can volunteer blocks in 00:14:18.640 --> 00:14:20.790 align:start position:0% in the world can volunteer blocks in real<00:14:18.820> time<00:14:19.149> if<00:14:19.570> you're<00:14:20.080> volunteered<00:14:20.620> in<00:14:20.709> a 00:14:20.790 --> 00:14:20.800 align:start position:0% real time if you're volunteered in a 00:14:20.800 --> 00:14:23.639 align:start position:0% real time if you're volunteered in a block<00:14:21.070> you<00:14:21.510> can<00:14:22.510> you<00:14:22.690> know<00:14:22.779> hold<00:14:23.110> the<00:14:23.260> miners 00:14:23.639 --> 00:14:23.649 align:start position:0% block you can you know hold the miners 00:14:23.649 --> 00:14:25.710 align:start position:0% block you can you know hold the miners accountable<00:14:24.279> you<00:14:24.459> vallah<00:14:24.910> date<00:14:25.180> it<00:14:25.330> and<00:14:25.450> you 00:14:25.710 --> 00:14:25.720 align:start position:0% accountable you vallah date it and you 00:14:25.720 --> 00:14:28.860 align:start position:0% accountable you vallah date it and you accept<00:14:26.170> it<00:14:26.320> or<00:14:26.470> you<00:14:26.560> reject<00:14:27.459> it<00:14:27.610> if<00:14:27.880> the<00:14:28.510> miners 00:14:28.860 --> 00:14:28.870 align:start position:0% accept it or you reject it if the miners 00:14:28.870 --> 00:14:31.769 align:start position:0% accept it or you reject it if the miners cheat<00:14:29.200> you<00:14:29.890> just<00:14:30.070> reject<00:14:30.459> the<00:14:30.610> block<00:14:30.850> and<00:14:31.600> what 00:14:31.769 --> 00:14:31.779 align:start position:0% cheat you just reject the block and what 00:14:31.779 --> 00:14:33.900 align:start position:0% cheat you just reject the block and what you're<00:14:31.930> actually<00:14:32.110> doing<00:14:32.470> is<00:14:33.130> holding<00:14:33.579> the 00:14:33.900 --> 00:14:33.910 align:start position:0% you're actually doing is holding the 00:14:33.910 --> 00:14:35.550 align:start position:0% you're actually doing is holding the block<00:14:34.120> producers<00:14:34.690> pronounce<00:14:35.350> the 00:14:35.550 --> 00:14:35.560 align:start position:0% block producers pronounce the 00:14:35.560 --> 00:14:37.740 align:start position:0% block producers pronounce the accountable<00:14:36.190> if<00:14:36.399> they<00:14:36.880> produce<00:14:37.060> Bob<00:14:37.450> blocks 00:14:37.740 --> 00:14:37.750 align:start position:0% accountable if they produce Bob blocks 00:14:37.750 --> 00:14:42.000 align:start position:0% accountable if they produce Bob blocks and<00:14:38.529> that's<00:14:38.920> really<00:14:39.130> cool<00:14:39.430> so<00:14:40.290> I<00:14:41.290> guess<00:14:41.770> my 00:14:42.000 --> 00:14:42.010 align:start position:0% and that's really cool so I guess my 00:14:42.010 --> 00:14:44.040 align:start position:0% and that's really cool so I guess my motivation<00:14:42.700> for<00:14:42.730> the<00:14:42.940> past<00:14:43.149> few<00:14:43.360> years<00:14:43.450> and 00:14:44.040 --> 00:14:44.050 align:start position:0% motivation for the past few years and 00:14:44.050 --> 00:14:45.569 align:start position:0% motivation for the past few years and what<00:14:44.350> we're<00:14:44.500> trying<00:14:44.649> to<00:14:44.770> now<00:14:44.920> build<00:14:45.130> a<00:14:45.310> Pisa 00:14:45.569 --> 00:14:45.579 align:start position:0% what we're trying to now build a Pisa 00:14:45.579 --> 00:14:47.370 align:start position:0% what we're trying to now build a Pisa has<00:14:45.910> lost<00:14:46.690> bringing<00:14:46.899> financial 00:14:47.370 --> 00:14:47.380 align:start position:0% has lost bringing financial 00:14:47.380 --> 00:14:49.470 align:start position:0% has lost bringing financial accountability<00:14:47.770> to<00:14:48.550> every<00:14:48.880> single<00:14:49.270> online 00:14:49.470 --> 00:14:49.480 align:start position:0% accountability to every single online 00:14:49.480 --> 00:14:52.470 align:start position:0% accountability to every single online service<00:14:50.850> starting<00:14:51.850> with<00:14:51.970> you<00:14:52.060> know<00:14:52.180> third 00:14:52.470 --> 00:14:52.480 align:start position:0% service starting with you know third 00:14:52.480 --> 00:14:55.079 align:start position:0% service starting with you know third party<00:14:52.870> broadcast<00:14:53.410> networks<00:14:53.890> we're<00:14:54.790> building 00:14:55.079 --> 00:14:55.089 align:start position:0% party broadcast networks we're building 00:14:55.089 --> 00:14:56.850 align:start position:0% party broadcast networks we're building this<00:14:55.209> new<00:14:55.450> finance<00:14:55.750> the<00:14:55.899> accountable<00:14:56.500> therap 00:14:56.850 --> 00:14:56.860 align:start position:0% this new finance the accountable therap 00:14:56.860 --> 00:14:59.940 align:start position:0% this new finance the accountable therap RT<00:14:57.240> and<00:14:58.240> this<00:14:59.170> is<00:14:59.290> what<00:14:59.380> everyone<00:14:59.649> in<00:14:59.829> this 00:14:59.940 --> 00:14:59.950 align:start position:0% RT and this is what everyone in this 00:14:59.950 --> 00:15:02.400 align:start position:0% RT and this is what everyone in this room<00:15:00.220> should<00:15:00.279> be<00:15:00.490> aiming<00:15:00.760> towards<00:15:01.240> as<00:15:01.360> well<00:15:01.570> we 00:15:02.400 --> 00:15:02.410 align:start position:0% room should be aiming towards as well we 00:15:02.410 --> 00:15:04.910 align:start position:0% room should be aiming towards as well we should<00:15:02.620> be<00:15:02.649> building<00:15:02.920> services<00:15:03.790> such<00:15:04.600> that 00:15:04.910 --> 00:15:04.920 align:start position:0% should be building services such that 00:15:04.920 --> 00:15:07.530 align:start position:0% should be building services such that they've<00:15:05.920> you<00:15:06.220> know<00:15:06.279> the<00:15:06.459> terms<00:15:06.760> of<00:15:07.089> the<00:15:07.329> you 00:15:07.530 --> 00:15:07.540 align:start position:0% they've you know the terms of the you 00:15:07.540 --> 00:15:09.569 align:start position:0% they've you know the terms of the you know<00:15:07.600> service<00:15:08.110> level<00:15:08.350> agreement<00:15:08.860> are<00:15:09.010> easily 00:15:09.569 --> 00:15:09.579 align:start position:0% know service level agreement are easily 00:15:09.579 --> 00:15:12.900 align:start position:0% know service level agreement are easily enforceable<00:15:10.240> and<00:15:10.390> verifiable<00:15:11.459> we<00:15:12.459> should<00:15:12.670> not 00:15:12.900 --> 00:15:12.910 align:start position:0% enforceable and verifiable we should not 00:15:12.910 --> 00:15:15.750 align:start position:0% enforceable and verifiable we should not blindly<00:15:13.390> trust<00:15:13.990> third<00:15:14.320> parties<00:15:14.860> we<00:15:15.550> should 00:15:15.750 --> 00:15:15.760 align:start position:0% blindly trust third parties we should 00:15:15.760 --> 00:15:18.990 align:start position:0% blindly trust third parties we should verify<00:15:16.000> everything<00:15:16.750> they<00:15:17.079> do<00:15:17.140> and<00:15:17.880> if<00:15:18.880> the 00:15:18.990 --> 00:15:19.000 align:start position:0% verify everything they do and if the 00:15:19.000 --> 00:15:20.850 align:start position:0% verify everything they do and if the third<00:15:19.209> parties<00:15:19.600> deviate<00:15:20.079> from<00:15:20.110> the<00:15:20.320> protocol 00:15:20.850 --> 00:15:20.860 align:start position:0% third parties deviate from the protocol 00:15:20.860 --> 00:15:22.860 align:start position:0% third parties deviate from the protocol or<00:15:21.130> if<00:15:21.339> they<00:15:21.490> cheat<00:15:21.760> we<00:15:22.480> should<00:15:22.660> have<00:15:22.750> an 00:15:22.860 --> 00:15:22.870 align:start position:0% or if they cheat we should have an 00:15:22.870 --> 00:15:25.470 align:start position:0% or if they cheat we should have an ability<00:15:23.110> the<00:15:23.470> issue<00:15:23.649> punishments<00:15:24.490> you<00:15:24.730> know 00:15:25.470 --> 00:15:25.480 align:start position:0% ability the issue punishments you know 00:15:25.480 --> 00:15:27.030 align:start position:0% ability the issue punishments you know they<00:15:25.600> make<00:15:25.810> sure<00:15:25.990> we<00:15:26.110> hold<00:15:26.290> them<00:15:26.529> financially 00:15:27.030 --> 00:15:27.040 align:start position:0% they make sure we hold them financially 00:15:27.040 --> 00:15:28.920 align:start position:0% they make sure we hold them financially accountable<00:15:27.250> and<00:15:28.089> that's<00:15:28.420> actually<00:15:28.690> what 00:15:28.920 --> 00:15:28.930 align:start position:0% accountable and that's actually what 00:15:28.930 --> 00:15:30.630 align:start position:0% accountable and that's actually what makes<00:15:29.050> cryptocurrency<00:15:29.589> so<00:15:29.980> grid<00:15:30.279> you<00:15:30.579> know 00:15:30.630 --> 00:15:30.640 align:start position:0% makes cryptocurrency so grid you know 00:15:30.640 --> 00:15:32.310 align:start position:0% makes cryptocurrency so grid you know that's<00:15:30.910> the<00:15:31.060> toss<00:15:31.240> is<00:15:31.270> real<00:15:31.630> vision<00:15:31.959> of<00:15:32.079> why<00:15:32.170> he 00:15:32.310 --> 00:15:32.320 align:start position:0% that's the toss is real vision of why he 00:15:32.320 --> 00:15:35.130 align:start position:0% that's the toss is real vision of why he built<00:15:32.500> this<00:15:32.740> entire<00:15:32.920> system<00:15:33.959> so<00:15:34.959> that's 00:15:35.130 --> 00:15:35.140 align:start position:0% built this entire system so that's 00:15:35.140 --> 00:15:36.840 align:start position:0% built this entire system so that's basically<00:15:35.500> the<00:15:35.620> end<00:15:35.829> of<00:15:35.949> this<00:15:36.070> talk<00:15:36.370> you<00:15:36.699> know 00:15:36.840 --> 00:15:36.850 align:start position:0% basically the end of this talk you know 00:15:36.850 --> 00:15:38.550 align:start position:0% basically the end of this talk you know our<00:15:36.970> goal<00:15:37.270> is<00:15:37.420> to<00:15:37.449> build<00:15:37.750> as<00:15:37.870> financially 00:15:38.550 --> 00:15:38.560 align:start position:0% our goal is to build as financially 00:15:38.560 --> 00:15:39.090 align:start position:0% our goal is to build as financially accountable 00:15:39.090 --> 00:15:39.100 align:start position:0% accountable 00:15:39.100 --> 00:15:41.550 align:start position:0% accountable the<00:15:39.220> party<00:15:39.610> broadcast<00:15:40.150> network<00:15:40.660> hopefully 00:15:41.550 --> 00:15:41.560 align:start position:0% the party broadcast network hopefully 00:15:41.560 --> 00:15:43.380 align:start position:0% the party broadcast network hopefully people<00:15:41.650> here<00:15:41.920> realized<00:15:42.460> I<00:15:42.700> did<00:15:42.940> not<00:15:43.090> talk 00:15:43.380 --> 00:15:43.390 align:start position:0% people here realized I did not talk 00:15:43.390 --> 00:15:46.500 align:start position:0% people here realized I did not talk about<00:15:43.540> Austrian<00:15:44.110> protocols<00:15:44.700> whatsoever<00:15:45.700> it's 00:15:46.500 --> 00:15:46.510 align:start position:0% about Austrian protocols whatsoever it's 00:15:46.510 --> 00:15:48.060 align:start position:0% about Austrian protocols whatsoever it's generally<00:15:46.990> useful<00:15:47.410> for<00:15:47.620> most<00:15:47.800> smart 00:15:48.060 --> 00:15:48.070 align:start position:0% generally useful for most smart 00:15:48.070 --> 00:15:50.100 align:start position:0% generally useful for most smart contracts<00:15:48.550> and<00:15:49.120> now<00:15:49.420> hopefully<00:15:49.720> we're<00:15:49.990> going 00:15:50.100 --> 00:15:50.110 align:start position:0% contracts and now hopefully we're going 00:15:50.110 --> 00:15:51.540 align:start position:0% contracts and now hopefully we're going to<00:15:50.200> be<00:15:50.290> I<00:15:50.530> mean<00:15:50.770> there's<00:15:50.980> an<00:15:51.070> alpha<00:15:51.250> version 00:15:51.540 --> 00:15:51.550 align:start position:0% to be I mean there's an alpha version 00:15:51.550 --> 00:15:53.490 align:start position:0% to be I mean there's an alpha version running<00:15:51.970> already<00:15:52.090> and<00:15:52.570> hopefully<00:15:53.110> the<00:15:53.170> API 00:15:53.490 --> 00:15:53.500 align:start position:0% running already and hopefully the API 00:15:53.500 --> 00:16:04.860 align:start position:0% running already and hopefully the API will<00:15:53.620> be<00:15:53.710> publicly<00:15:54.040> available<00:15:54.340> very<00:15:54.760> soon 00:16:04.860 --> 00:16:04.870 align:start position:0% 00:16:04.870 --> 00:16:06.930 align:start position:0% you