WEBVTT Kind: captions Language: en 00:00:00.000 --> 00:00:03.800 align:start position:0% then<00:00:00.719> I'm<00:00:00.930> the<00:00:01.079> CTO<00:00:01.290> at<00:00:01.589> bit<00:00:01.770> go<00:00:01.920> and<00:00:02.510> so<00:00:03.510> Big<00:00:03.689> O 00:00:03.800 --> 00:00:03.810 align:start position:0% then I'm the CTO at bit go and so Big O 00:00:03.810 --> 00:00:06.470 align:start position:0% then I'm the CTO at bit go and so Big O is<00:00:03.840> like<00:00:04.049> an<00:00:04.170> exchange<00:00:04.500> API<00:00:05.490> that<00:00:06.089> many 00:00:06.470 --> 00:00:06.480 align:start position:0% is like an exchange API that many 00:00:06.480 --> 00:00:09.290 align:start position:0% is like an exchange API that many exchanges<00:00:07.379> like<00:00:07.710> this<00:00:07.890> then<00:00:08.130> call<00:00:08.970> bit<00:00:09.120> and<00:00:09.240> a 00:00:09.290 --> 00:00:09.300 align:start position:0% exchanges like this then call bit and a 00:00:09.300 --> 00:00:12.230 align:start position:0% exchanges like this then call bit and a bit<00:00:09.540> used<00:00:09.809> for<00:00:10.230> their<00:00:10.530> wallets<00:00:10.860> so<00:00:11.670> we<00:00:11.820> you 00:00:12.230 --> 00:00:12.240 align:start position:0% bit used for their wallets so we you 00:00:12.240 --> 00:00:15.250 align:start position:0% bit used for their wallets so we you know<00:00:12.330> you<00:00:12.929> do<00:00:13.049> scalability<00:00:13.679> and<00:00:13.920> security<00:00:14.370> oh 00:00:15.250 --> 00:00:15.260 align:start position:0% know you do scalability and security oh 00:00:15.260 --> 00:00:18.439 align:start position:0% know you do scalability and security oh yeah<00:00:16.289> my<00:00:16.500> name<00:00:16.619> is<00:00:16.710> Jake<00:00:16.890> Craig<00:00:17.130> also<00:00:17.880> work<00:00:18.300> at 00:00:18.439 --> 00:00:18.449 align:start position:0% yeah my name is Jake Craig also work at 00:00:18.449 --> 00:00:20.000 align:start position:0% yeah my name is Jake Craig also work at coinbase<00:00:18.660> senior<00:00:19.320> software<00:00:19.560> engineer<00:00:19.650> on<00:00:19.949> the 00:00:20.000 --> 00:00:20.010 align:start position:0% coinbase senior software engineer on the 00:00:20.010 --> 00:00:22.400 align:start position:0% coinbase senior software engineer on the the<00:00:20.400> crypto<00:00:20.640> payments<00:00:21.029> engineering<00:00:21.600> team<00:00:21.750> so 00:00:22.400 --> 00:00:22.410 align:start position:0% the crypto payments engineering team so 00:00:22.410 --> 00:00:23.750 align:start position:0% the crypto payments engineering team so we're<00:00:22.529> the<00:00:22.619> team<00:00:22.740> that<00:00:22.980> sort<00:00:23.250> of<00:00:23.310> runs<00:00:23.490> all<00:00:23.670> the 00:00:23.750 --> 00:00:23.760 align:start position:0% we're the team that sort of runs all the 00:00:23.760 --> 00:00:24.920 align:start position:0% we're the team that sort of runs all the blockchain<00:00:23.970> integrations<00:00:24.480> at<00:00:24.600> coinbase 00:00:24.920 --> 00:00:24.930 align:start position:0% blockchain integrations at coinbase 00:00:24.930 --> 00:00:27.140 align:start position:0% blockchain integrations at coinbase if<00:00:25.230> you<00:00:25.350> do<00:00:25.439> sends<00:00:25.800> or<00:00:25.949> receives<00:00:25.980> hot<00:00:26.849> wallet 00:00:27.140 --> 00:00:27.150 align:start position:0% if you do sends or receives hot wallet 00:00:27.150 --> 00:00:28.519 align:start position:0% if you do sends or receives hot wallet cold<00:00:27.330> storage<00:00:27.660> all<00:00:27.779> that<00:00:27.930> kind<00:00:28.140> of<00:00:28.170> stuff<00:00:28.260> goes 00:00:28.519 --> 00:00:28.529 align:start position:0% cold storage all that kind of stuff goes 00:00:28.529 --> 00:00:30.620 align:start position:0% cold storage all that kind of stuff goes through<00:00:28.680> our<00:00:28.740> systems<00:00:29.449> yep<00:00:30.480> I've<00:00:30.539> been 00:00:30.620 --> 00:00:30.630 align:start position:0% through our systems yep I've been 00:00:30.630 --> 00:00:31.490 align:start position:0% through our systems yep I've been working<00:00:30.869> in<00:00:30.960> for<00:00:30.990> business 00:00:31.490 --> 00:00:31.500 align:start position:0% working in for business 00:00:31.500 --> 00:00:33.470 align:start position:0% working in for business all<00:00:31.710> right<00:00:31.920> on<00:00:32.040> the<00:00:32.160> Kuna<00:00:32.489> cool<00:00:33.239> and<00:00:33.420> I've 00:00:33.470 --> 00:00:33.480 align:start position:0% all right on the Kuna cool and I've 00:00:33.480 --> 00:00:34.670 align:start position:0% all right on the Kuna cool and I've probably<00:00:33.630> introduced<00:00:34.079> myself<00:00:34.200> as<00:00:34.469> well<00:00:34.590> so 00:00:34.670 --> 00:00:34.680 align:start position:0% probably introduced myself as well so 00:00:34.680 --> 00:00:36.229 align:start position:0% probably introduced myself as well so I'm<00:00:34.770> Eric<00:00:35.010> Scribner<00:00:35.370> and<00:00:35.610> I'm<00:00:35.790> also<00:00:36.000> on<00:00:36.180> the 00:00:36.229 --> 00:00:36.239 align:start position:0% I'm Eric Scribner and I'm also on the 00:00:36.239 --> 00:00:37.580 align:start position:0% I'm Eric Scribner and I'm also on the crypto<00:00:36.510> payments<00:00:36.870> team<00:00:37.020> with<00:00:37.200> Jake<00:00:37.410> and 00:00:37.580 --> 00:00:37.590 align:start position:0% crypto payments team with Jake and 00:00:37.590 --> 00:00:39.799 align:start position:0% crypto payments team with Jake and coinbase<00:00:38.010> and<00:00:38.700> did<00:00:39.450> a<00:00:39.480> pretty<00:00:39.600> good<00:00:39.750> job 00:00:39.799 --> 00:00:39.809 align:start position:0% coinbase and did a pretty good job 00:00:39.809 --> 00:00:41.840 align:start position:0% coinbase and did a pretty good job summarizing<00:00:40.260> what<00:00:40.469> we<00:00:40.590> do<00:00:40.680> their<00:00:40.829> stuff<00:00:41.250> I'll 00:00:41.840 --> 00:00:41.850 align:start position:0% summarizing what we do their stuff I'll 00:00:41.850 --> 00:00:43.940 align:start position:0% summarizing what we do their stuff I'll leave<00:00:42.329> it<00:00:42.420> at<00:00:42.480> that<00:00:42.510> and<00:00:42.930> all<00:00:43.410> right<00:00:43.620> so<00:00:43.829> we'll 00:00:43.940 --> 00:00:43.950 align:start position:0% leave it at that and all right so we'll 00:00:43.950 --> 00:00:45.560 align:start position:0% leave it at that and all right so we'll start<00:00:44.100> with<00:00:44.309> the<00:00:44.579> we'll<00:00:45.210> start<00:00:45.360> with<00:00:45.480> some 00:00:45.560 --> 00:00:45.570 align:start position:0% start with the we'll start with some 00:00:45.570 --> 00:00:48.410 align:start position:0% start with the we'll start with some softball<00:00:45.989> questions<00:00:46.469> here<00:00:46.640> all<00:00:47.640> right<00:00:47.910> so 00:00:48.410 --> 00:00:48.420 align:start position:0% softball questions here all right so 00:00:48.420 --> 00:00:51.319 align:start position:0% softball questions here all right so this<00:00:48.930> one<00:00:49.170> is<00:00:49.980> one<00:00:50.190> of<00:00:50.219> my<00:00:50.309> favorite<00:00:50.670> ones<00:00:50.820> I 00:00:51.319 --> 00:00:51.329 align:start position:0% this one is one of my favorite ones I 00:00:51.329 --> 00:00:52.790 align:start position:0% this one is one of my favorite ones I think<00:00:51.870> this<00:00:52.050> should<00:00:52.140> be<00:00:52.199> asked<00:00:52.500> more<00:00:52.649> to 00:00:52.790 --> 00:00:52.800 align:start position:0% think this should be asked more to 00:00:52.800 --> 00:00:55.729 align:start position:0% think this should be asked more to theorem<00:00:53.129> and<00:00:53.309> DEF<00:00:54.030> CON<00:00:54.210> events<00:00:54.629> in<00:00:54.840> general<00:00:54.960> so 00:00:55.729 --> 00:00:55.739 align:start position:0% theorem and DEF CON events in general so 00:00:55.739 --> 00:00:58.400 align:start position:0% theorem and DEF CON events in general so if<00:00:55.860> you<00:00:55.949> were<00:00:56.070> an<00:00:56.190> EVM<00:00:56.550> op<00:00:56.760> code<00:00:57.090> which<00:00:57.780> Evo<00:00:58.199> mob 00:00:58.400 --> 00:00:58.410 align:start position:0% if you were an EVM op code which Evo mob 00:00:58.410 --> 00:01:02.319 align:start position:0% if you were an EVM op code which Evo mob code<00:00:58.680> would<00:00:58.890> you<00:00:59.039> be<00:00:59.250> and<00:00:59.550> why 00:01:02.319 --> 00:01:02.329 align:start position:0% 00:01:02.329 --> 00:01:06.440 align:start position:0% well<00:01:03.470> I'm<00:01:04.470> on<00:01:04.650> stage<00:01:04.890> in<00:01:05.189> 2018<00:01:05.909> so<00:01:06.090> I<00:01:06.119> think<00:01:06.240> I 00:01:06.440 --> 00:01:06.450 align:start position:0% well I'm on stage in 2018 so I think I 00:01:06.450 --> 00:01:26.899 align:start position:0% well I'm on stage in 2018 so I think I have<00:01:06.659> to<00:01:06.869> be<00:01:06.990> the<00:01:07.140> PC<00:01:07.650> opcode<00:01:25.369> all<00:01:26.369> right<00:01:26.610> all 00:01:26.899 --> 00:01:26.909 align:start position:0% have to be the PC opcode all right all 00:01:26.909 --> 00:01:29.649 align:start position:0% have to be the PC opcode all right all right<00:01:27.030> I<00:01:27.090> can<00:01:27.240> see<00:01:27.330> that<00:01:27.479> oh<00:01:27.710> yeah<00:01:28.710> and<00:01:29.130> the<00:01:29.220> why 00:01:29.649 --> 00:01:29.659 align:start position:0% right I can see that oh yeah and the why 00:01:29.659 --> 00:01:31.789 align:start position:0% right I can see that oh yeah and the why why<00:01:30.659> yeah<00:01:31.020> what<00:01:31.140> do<00:01:31.200> you<00:01:31.229> enjoy<00:01:31.409> that<00:01:31.590> call 00:01:31.789 --> 00:01:31.799 align:start position:0% why yeah what do you enjoy that call 00:01:31.799 --> 00:01:38.870 align:start position:0% why yeah what do you enjoy that call because<00:01:32.579> I<00:01:32.759> think<00:01:33.060> it's<00:01:33.240> what<00:01:36.920> okay<00:01:37.920> all<00:01:38.610> right 00:01:38.870 --> 00:01:38.880 align:start position:0% because I think it's what okay all right 00:01:38.880 --> 00:01:40.010 align:start position:0% because I think it's what okay all right fair<00:01:39.060> enough<00:01:39.119> and<00:01:39.420> Jake<00:01:39.630> which<00:01:39.810> one<00:01:39.930> are<00:01:39.960> you 00:01:40.010 --> 00:01:40.020 align:start position:0% fair enough and Jake which one are you 00:01:40.020 --> 00:01:42.109 align:start position:0% fair enough and Jake which one are you gonna<00:01:40.170> be<00:01:40.320> so<00:01:40.650> good<00:01:40.799> I've<00:01:41.009> got<00:01:41.159> two<00:01:41.369> I<00:01:41.820> think 00:01:42.109 --> 00:01:42.119 align:start position:0% gonna be so good I've got two I think 00:01:42.119 --> 00:01:43.850 align:start position:0% gonna be so good I've got two I think the<00:01:42.270> first<00:01:42.600> one<00:01:42.689> you<00:01:43.079> might<00:01:43.439> be<00:01:43.590> what<00:01:43.740> you're 00:01:43.850 --> 00:01:43.860 align:start position:0% the first one you might be what you're 00:01:43.860 --> 00:01:45.889 align:start position:0% the first one you might be what you're guessing<00:01:44.130> there<00:01:44.970> is<00:01:45.119> a<00:01:45.149> NOC<00:01:45.390> code<00:01:45.600> called 00:01:45.889 --> 00:01:45.899 align:start position:0% guessing there is a NOC code called 00:01:45.899 --> 00:01:48.789 align:start position:0% guessing there is a NOC code called coinbase<00:01:46.250> which<00:01:47.250> is<00:01:47.369> a<00:01:47.399> very<00:01:47.670> convenient<00:01:48.090> one 00:01:48.789 --> 00:01:48.799 align:start position:0% coinbase which is a very convenient one 00:01:48.799 --> 00:01:51.319 align:start position:0% coinbase which is a very convenient one but<00:01:49.799> that's<00:01:50.100> not<00:01:50.250> gonna<00:01:50.340> be<00:01:50.430> my<00:01:50.549> choice<00:01:50.759> my 00:01:51.319 --> 00:01:51.329 align:start position:0% but that's not gonna be my choice my 00:01:51.329 --> 00:01:53.660 align:start position:0% but that's not gonna be my choice my choice<00:01:51.360> is<00:01:51.570> gonna<00:01:51.659> be<00:01:51.810> X<00:01:51.960> or<00:01:52.170> which<00:01:52.860> it's<00:01:53.610> just 00:01:53.660 --> 00:01:53.670 align:start position:0% choice is gonna be X or which it's just 00:01:53.670 --> 00:01:55.399 align:start position:0% choice is gonna be X or which it's just cuz<00:01:53.939> you<00:01:54.299> know<00:01:54.420> all<00:01:54.630> the<00:01:54.810> new<00:01:54.899> cryptography 00:01:55.399 --> 00:01:55.409 align:start position:0% cuz you know all the new cryptography 00:01:55.409 --> 00:01:57.590 align:start position:0% cuz you know all the new cryptography stuff<00:01:55.619> in<00:01:55.740> coin<00:01:55.890> bit<00:01:56.070> coin<00:01:56.100> base<00:01:56.790> in<00:01:57.270> the 00:01:57.590 --> 00:01:57.600 align:start position:0% stuff in coin bit coin base in the 00:01:57.600 --> 00:01:58.880 align:start position:0% stuff in coin bit coin base in the community<00:01:57.960> coming<00:01:58.170> out<00:01:58.320> and<00:01:58.439> stuff<00:01:58.619> it's<00:01:58.829> just 00:01:58.880 --> 00:01:58.890 align:start position:0% community coming out and stuff it's just 00:01:58.890 --> 00:02:01.249 align:start position:0% community coming out and stuff it's just XOR<00:01:59.520> with<00:01:59.549> some<00:01:59.790> powers<00:02:00.119> basically<00:02:00.930> all<00:02:01.079> that 00:02:01.249 --> 00:02:01.259 align:start position:0% XOR with some powers basically all that 00:02:01.259 --> 00:02:03.170 align:start position:0% XOR with some powers basically all that at<00:02:01.469> some<00:02:01.710> level<00:02:01.950> and<00:02:02.250> it's<00:02:02.820> just<00:02:02.939> a<00:02:03.030> really 00:02:03.170 --> 00:02:03.180 align:start position:0% at some level and it's just a really 00:02:03.180 --> 00:02:05.359 align:start position:0% at some level and it's just a really exciting<00:02:03.360> thing<00:02:03.869> to<00:02:04.229> play<00:02:04.890> with<00:02:05.070> and<00:02:05.250> it's 00:02:05.359 --> 00:02:05.369 align:start position:0% exciting thing to play with and it's 00:02:05.369 --> 00:02:08.029 align:start position:0% exciting thing to play with and it's this<00:02:05.490> very<00:02:06.060> simple<00:02:06.390> thing<00:02:06.600> but<00:02:06.780> it's<00:02:07.229> just<00:02:07.590> so 00:02:08.029 --> 00:02:08.039 align:start position:0% this very simple thing but it's just so 00:02:08.039 --> 00:02:10.070 align:start position:0% this very simple thing but it's just so powerful<00:02:08.640> all<00:02:09.390> right<00:02:09.629> know<00:02:09.780> what<00:02:09.899> no<00:02:10.050> one 00:02:10.070 --> 00:02:10.080 align:start position:0% powerful all right know what no one 00:02:10.080 --> 00:02:12.050 align:start position:0% powerful all right know what no one picks<00:02:10.349> self-destructs<00:02:11.099> okay<00:02:11.489> that's<00:02:11.700> good 00:02:12.050 --> 00:02:12.060 align:start position:0% picks self-destructs okay that's good 00:02:12.060 --> 00:02:13.160 align:start position:0% picks self-destructs okay that's good that's<00:02:12.180> yours 00:02:13.160 --> 00:02:13.170 align:start position:0% that's yours 00:02:13.170 --> 00:02:17.270 align:start position:0% that's yours mine<00:02:14.150> okay<00:02:15.150> so<00:02:15.680> let's<00:02:16.680> kick<00:02:16.830> things<00:02:16.980> off<00:02:17.160> let's 00:02:17.270 --> 00:02:17.280 align:start position:0% mine okay so let's kick things off let's 00:02:17.280 --> 00:02:18.500 align:start position:0% mine okay so let's kick things off let's move<00:02:17.520> let's<00:02:17.700> move<00:02:17.730> under<00:02:17.970> the<00:02:18.000> medium<00:02:18.360> ones 00:02:18.500 --> 00:02:18.510 align:start position:0% move let's move under the medium ones 00:02:18.510 --> 00:02:21.620 align:start position:0% move let's move under the medium ones here<00:02:18.780> okay<00:02:19.230> so<00:02:19.670> I<00:02:20.670> really<00:02:20.970> like<00:02:21.300> this<00:02:21.450> first 00:02:21.620 --> 00:02:21.630 align:start position:0% here okay so I really like this first 00:02:21.630 --> 00:02:23.390 align:start position:0% here okay so I really like this first one<00:02:21.840> so<00:02:22.020> what<00:02:22.170> is<00:02:22.260> the<00:02:22.470> what<00:02:22.800> is<00:02:22.890> your<00:02:23.160> biggest 00:02:23.390 --> 00:02:23.400 align:start position:0% one so what is the what is your biggest 00:02:23.400 --> 00:02:24.680 align:start position:0% one so what is the what is your biggest challenge<00:02:23.580> integrating<00:02:24.300> with<00:02:24.420> the<00:02:24.450> theory 00:02:24.680 --> 00:02:24.690 align:start position:0% challenge integrating with the theory 00:02:24.690 --> 00:02:27.650 align:start position:0% challenge integrating with the theory I'm<00:02:24.780> at<00:02:24.900> this<00:02:24.989> moment<00:02:25.610> I'll<00:02:26.610> start<00:02:26.970> with<00:02:27.150> with 00:02:27.650 --> 00:02:27.660 align:start position:0% I'm at this moment I'll start with with 00:02:27.660 --> 00:02:32.840 align:start position:0% I'm at this moment I'll start with with you<00:02:27.900> okay<00:02:29.630> when<00:02:30.630> huge<00:02:30.870> challenge<00:02:31.350> is<00:02:31.500> a<00:02:31.850> Nantes 00:02:32.840 --> 00:02:32.850 align:start position:0% you okay when huge challenge is a Nantes 00:02:32.850 --> 00:02:37.210 align:start position:0% you okay when huge challenge is a Nantes management<00:02:33.390> in<00:02:33.569> terms<00:02:33.630> of<00:02:35.810> you<00:02:36.810> can<00:02:36.959> have 00:02:37.210 --> 00:02:37.220 align:start position:0% management in terms of you can have 00:02:37.220 --> 00:02:40.520 align:start position:0% management in terms of you can have rapidly<00:02:38.220> fluctuating<00:02:38.640> gas<00:02:39.569> prices<00:02:40.110> across 00:02:40.520 --> 00:02:40.530 align:start position:0% rapidly fluctuating gas prices across 00:02:40.530 --> 00:02:42.800 align:start position:0% rapidly fluctuating gas prices across the<00:02:40.769> network<00:02:41.160> and<00:02:41.370> if<00:02:41.790> one<00:02:42.180> transaction<00:02:42.510> gets 00:02:42.800 --> 00:02:42.810 align:start position:0% the network and if one transaction gets 00:02:42.810 --> 00:02:46.190 align:start position:0% the network and if one transaction gets stuck<00:02:43.110> then<00:02:43.580> it<00:02:44.630> slows<00:02:45.630> up<00:02:45.750> all<00:02:45.900> the<00:02:45.989> others 00:02:46.190 --> 00:02:46.200 align:start position:0% stuck then it slows up all the others 00:02:46.200 --> 00:02:48.710 align:start position:0% stuck then it slows up all the others and<00:02:46.410> you<00:02:46.530> either<00:02:47.190> have<00:02:47.489> to<00:02:47.519> resend<00:02:48.420> the<00:02:48.510> first 00:02:48.710 --> 00:02:48.720 align:start position:0% and you either have to resend the first 00:02:48.720 --> 00:02:52.640 align:start position:0% and you either have to resend the first one<00:02:48.930> or<00:02:49.170> just<00:02:49.620> wait<00:02:50.400> it<00:02:50.550> out<00:02:50.810> that's<00:02:51.810> a<00:02:51.930> huge 00:02:52.640 --> 00:02:52.650 align:start position:0% one or just wait it out that's a huge 00:02:52.650 --> 00:02:56.900 align:start position:0% one or just wait it out that's a huge challenge<00:02:53.930> yeah<00:02:54.930> I<00:02:54.959> think<00:02:55.430> we<00:02:56.430> see<00:02:56.610> that<00:02:56.730> as 00:02:56.900 --> 00:02:56.910 align:start position:0% challenge yeah I think we see that as 00:02:56.910 --> 00:02:59.720 align:start position:0% challenge yeah I think we see that as well<00:02:57.180> it's<00:02:57.540> a<00:02:57.660> pretty<00:02:58.220> common<00:02:59.220> issue<00:02:59.430> when<00:02:59.670> you 00:02:59.720 --> 00:02:59.730 align:start position:0% well it's a pretty common issue when you 00:02:59.730 --> 00:03:04.190 align:start position:0% well it's a pretty common issue when you have<00:02:59.880> very<00:03:00.120> large<00:03:00.269> wallets<00:03:01.640> so<00:03:02.640> with<00:03:03.480> you<00:03:04.080> know 00:03:04.190 --> 00:03:04.200 align:start position:0% have very large wallets so with you know 00:03:04.200 --> 00:03:06.500 align:start position:0% have very large wallets so with you know with<00:03:04.350> large<00:03:04.560> wallets<00:03:04.950> and<00:03:05.069> when<00:03:05.430> in<00:03:06.180> aetherium 00:03:06.500 --> 00:03:06.510 align:start position:0% with large wallets and when in aetherium 00:03:06.510 --> 00:03:09.380 align:start position:0% with large wallets and when in aetherium as<00:03:07.319> many<00:03:07.560> of<00:03:07.680> you<00:03:07.739> know<00:03:07.769> the<00:03:08.190> accounts<00:03:08.610> have<00:03:08.910> a 00:03:09.380 --> 00:03:09.390 align:start position:0% as many of you know the accounts have a 00:03:09.390 --> 00:03:11.360 align:start position:0% as many of you know the accounts have a nonce<00:03:09.600> and<00:03:09.950> whenever<00:03:10.950> you<00:03:11.069> create<00:03:11.250> a<00:03:11.340> new 00:03:11.360 --> 00:03:11.370 align:start position:0% nonce and whenever you create a new 00:03:11.370 --> 00:03:12.860 align:start position:0% nonce and whenever you create a new transaction<00:03:11.880> it<00:03:11.970> has<00:03:12.120> to<00:03:12.239> have<00:03:12.390> a<00:03:12.420> nonce<00:03:12.660> which 00:03:12.860 --> 00:03:12.870 align:start position:0% transaction it has to have a nonce which 00:03:12.870 --> 00:03:15.350 align:start position:0% transaction it has to have a nonce which is<00:03:13.080> monotonically<00:03:13.739> increasing<00:03:14.370> and<00:03:14.640> the<00:03:15.239> way 00:03:15.350 --> 00:03:15.360 align:start position:0% is monotonically increasing and the way 00:03:15.360 --> 00:03:16.789 align:start position:0% is monotonically increasing and the way that<00:03:15.540> it<00:03:15.630> was<00:03:15.720> designed<00:03:15.870> that<00:03:16.170> way<00:03:16.350> is<00:03:16.410> because 00:03:16.789 --> 00:03:16.799 align:start position:0% that it was designed that way is because 00:03:16.799 --> 00:03:20.210 align:start position:0% that it was designed that way is because it's<00:03:16.980> a<00:03:17.280> lot<00:03:17.400> easier<00:03:17.459> to<00:03:17.820> track<00:03:19.220> doubles 00:03:20.210 --> 00:03:20.220 align:start position:0% it's a lot easier to track doubles 00:03:20.220 --> 00:03:23.120 align:start position:0% it's a lot easier to track doubles protection<00:03:20.670> in<00:03:20.760> all<00:03:20.850> that<00:03:21.030> and<00:03:21.510> so<00:03:21.900> say<00:03:22.530> you 00:03:23.120 --> 00:03:23.130 align:start position:0% protection in all that and so say you 00:03:23.130 --> 00:03:25.400 align:start position:0% protection in all that and so say you know<00:03:23.250> you<00:03:23.310> you're<00:03:24.209> running<00:03:24.329> in<00:03:24.570> exchange<00:03:24.959> or 00:03:25.400 --> 00:03:25.410 align:start position:0% know you you're running in exchange or 00:03:25.410 --> 00:03:27.289 align:start position:0% know you you're running in exchange or something<00:03:25.680> like<00:03:25.739> that<00:03:25.799> and<00:03:26.549> you're<00:03:26.910> gonna<00:03:27.120> be 00:03:27.289 --> 00:03:27.299 align:start position:0% something like that and you're gonna be 00:03:27.299 --> 00:03:30.110 align:start position:0% something like that and you're gonna be sending<00:03:27.720> you<00:03:27.959> know<00:03:28.079> ten<00:03:28.560> transactions<00:03:29.190> for 00:03:30.110 --> 00:03:30.120 align:start position:0% sending you know ten transactions for 00:03:30.120 --> 00:03:33.590 align:start position:0% sending you know ten transactions for five<00:03:30.329> minutes<00:03:30.510> and<00:03:31.880> this<00:03:32.880> this<00:03:33.120> can<00:03:33.329> be<00:03:33.480> you 00:03:33.590 --> 00:03:33.600 align:start position:0% five minutes and this this can be you 00:03:33.600 --> 00:03:36.020 align:start position:0% five minutes and this this can be you know<00:03:33.720> 100<00:03:34.109> transactions<00:03:34.799> you<00:03:35.489> know<00:03:35.609> over<00:03:35.940> 50 00:03:36.020 --> 00:03:36.030 align:start position:0% know 100 transactions you know over 50 00:03:36.030 --> 00:03:38.449 align:start position:0% know 100 transactions you know over 50 minutes<00:03:36.480> and<00:03:36.780> if<00:03:37.530> a<00:03:37.769> transaction<00:03:38.130> number 00:03:38.449 --> 00:03:38.459 align:start position:0% minutes and if a transaction number 00:03:38.459 --> 00:03:41.150 align:start position:0% minutes and if a transaction number number<00:03:39.000> 4<00:03:39.239> you<00:03:40.079> put<00:03:40.290> in<00:03:40.380> a<00:03:40.440> wrong<00:03:40.620> gas<00:03:40.859> price 00:03:41.150 --> 00:03:41.160 align:start position:0% number 4 you put in a wrong gas price 00:03:41.160 --> 00:03:43.699 align:start position:0% number 4 you put in a wrong gas price then<00:03:41.850> by<00:03:42.030> transaction<00:03:42.510> 50<00:03:42.870> all<00:03:43.530> your 00:03:43.699 --> 00:03:43.709 align:start position:0% then by transaction 50 all your 00:03:43.709 --> 00:03:45.319 align:start position:0% then by transaction 50 all your transactions<00:03:44.100> can<00:03:44.250> clear<00:03:44.549> because<00:03:44.730> 4<00:03:45.060> isn't 00:03:45.319 --> 00:03:45.329 align:start position:0% transactions can clear because 4 isn't 00:03:45.329 --> 00:03:48.349 align:start position:0% transactions can clear because 4 isn't clear<00:03:45.500> so<00:03:46.500> I<00:03:46.530> think<00:03:46.820> that<00:03:47.820> that's<00:03:48.030> a<00:03:48.180> big 00:03:48.349 --> 00:03:48.359 align:start position:0% clear so I think that that's a big 00:03:48.359 --> 00:03:51.140 align:start position:0% clear so I think that that's a big that's<00:03:48.510> a<00:03:48.720> big<00:03:48.750> challenge<00:03:49.200> there<00:03:50.060> you<00:03:51.060> know 00:03:51.140 --> 00:03:51.150 align:start position:0% that's a big challenge there you know 00:03:51.150 --> 00:03:53.770 align:start position:0% that's a big challenge there you know you<00:03:51.690> want<00:03:51.840> to<00:03:51.930> talk<00:03:52.079> about<00:03:52.200> some<00:03:52.440> solutions 00:03:53.770 --> 00:03:53.780 align:start position:0% you want to talk about some solutions 00:03:53.780 --> 00:03:57.289 align:start position:0% you want to talk about some solutions yeah<00:03:54.780> yeah<00:03:55.709> like<00:03:55.890> you<00:03:55.980> said<00:03:56.220> we've<00:03:56.790> all<00:03:57.150> sort 00:03:57.289 --> 00:03:57.299 align:start position:0% yeah yeah like you said we've all sort 00:03:57.299 --> 00:03:58.759 align:start position:0% yeah yeah like you said we've all sort of<00:03:57.450> had<00:03:57.540> this<00:03:57.690> issue<00:03:57.840> and<00:03:58.200> it<00:03:58.350> is<00:03:58.380> one<00:03:58.590> that 00:03:58.759 --> 00:03:58.769 align:start position:0% of had this issue and it is one that 00:03:58.769 --> 00:04:00.170 align:start position:0% of had this issue and it is one that tends<00:03:58.950> to<00:03:59.100> come<00:03:59.220> up<00:03:59.340> at<00:03:59.489> scale<00:03:59.730> as<00:04:00.030> you're 00:04:00.170 --> 00:04:00.180 align:start position:0% tends to come up at scale as you're 00:04:00.180 --> 00:04:01.460 align:start position:0% tends to come up at scale as you're doing<00:04:00.359> just<00:04:00.450> a<00:04:00.600> lot<00:04:00.810> of<00:04:00.840> them<00:04:01.109> back-to-back 00:04:01.460 --> 00:04:01.470 align:start position:0% doing just a lot of them back-to-back 00:04:01.470 --> 00:04:03.380 align:start position:0% doing just a lot of them back-to-back right<00:04:02.040> if<00:04:02.130> you're<00:04:02.250> an<00:04:02.340> individual<00:04:02.700> wallet<00:04:03.120> you 00:04:03.380 --> 00:04:03.390 align:start position:0% right if you're an individual wallet you 00:04:03.390 --> 00:04:04.610 align:start position:0% right if you're an individual wallet you know<00:04:03.510> you<00:04:03.569> send<00:04:03.690> one<00:04:03.810> transaction<00:04:04.410> if<00:04:04.500> it 00:04:04.610 --> 00:04:04.620 align:start position:0% know you send one transaction if it 00:04:04.620 --> 00:04:06.349 align:start position:0% know you send one transaction if it takes<00:04:04.799> a<00:04:04.890> while<00:04:04.980> maybe<00:04:05.220> that's<00:04:05.430> okay<00:04:05.730> or<00:04:06.299> you 00:04:06.349 --> 00:04:06.359 align:start position:0% takes a while maybe that's okay or you 00:04:06.359 --> 00:04:07.940 align:start position:0% takes a while maybe that's okay or you can<00:04:06.480> really<00:04:06.660> easily<00:04:06.870> sort<00:04:07.319> of<00:04:07.380> replace<00:04:07.739> that 00:04:07.940 --> 00:04:07.950 align:start position:0% can really easily sort of replace that 00:04:07.950 --> 00:04:09.890 align:start position:0% can really easily sort of replace that it's<00:04:08.250> just<00:04:08.489> sort<00:04:08.609> of<00:04:08.700> replaced<00:04:09.060> by<00:04:09.239> fee 00:04:09.890 --> 00:04:09.900 align:start position:0% it's just sort of replaced by fee 00:04:09.900 --> 00:04:13.280 align:start position:0% it's just sort of replaced by fee mechanism<00:04:10.579> and<00:04:11.750> it's<00:04:12.750> an<00:04:12.900> interesting<00:04:13.200> one 00:04:13.280 --> 00:04:13.290 align:start position:0% mechanism and it's an interesting one 00:04:13.290 --> 00:04:14.780 align:start position:0% mechanism and it's an interesting one because<00:04:13.470> like<00:04:13.650> it<00:04:14.100> sort<00:04:14.310> of<00:04:14.370> depends<00:04:14.670> how<00:04:14.730> you 00:04:14.780 --> 00:04:14.790 align:start position:0% because like it sort of depends how you 00:04:14.790 --> 00:04:16.279 align:start position:0% because like it sort of depends how you structure<00:04:15.269> your<00:04:15.299> hot<00:04:15.720> wallet<00:04:16.019> as<00:04:16.139> well 00:04:16.279 --> 00:04:16.289 align:start position:0% structure your hot wallet as well 00:04:16.289 --> 00:04:17.870 align:start position:0% structure your hot wallet as well they're<00:04:16.979> different<00:04:17.039> ways<00:04:17.280> to<00:04:17.430> do<00:04:17.549> it<00:04:17.579> some 00:04:17.870 --> 00:04:17.880 align:start position:0% they're different ways to do it some 00:04:17.880 --> 00:04:19.250 align:start position:0% they're different ways to do it some exchanges<00:04:18.359> you<00:04:18.450> know<00:04:18.539> tend<00:04:18.780> to<00:04:18.870> use<00:04:18.989> like<00:04:19.229> a 00:04:19.250 --> 00:04:19.260 align:start position:0% exchanges you know tend to use like a 00:04:19.260 --> 00:04:21.110 align:start position:0% exchanges you know tend to use like a sort<00:04:19.620> of<00:04:19.680> single<00:04:19.889> or<00:04:20.130> a<00:04:20.190> few<00:04:20.400> addresses<00:04:21.030> for 00:04:21.110 --> 00:04:21.120 align:start position:0% sort of single or a few addresses for 00:04:21.120 --> 00:04:22.190 align:start position:0% sort of single or a few addresses for everything<00:04:21.450> so<00:04:21.599> they<00:04:21.690> have<00:04:21.810> a<00:04:21.840> lot<00:04:22.169> of 00:04:22.190 --> 00:04:22.200 align:start position:0% everything so they have a lot of 00:04:22.200 --> 00:04:24.440 align:start position:0% everything so they have a lot of transactions<00:04:22.950> going<00:04:23.099> through<00:04:23.250> that<00:04:23.340> address 00:04:24.440 --> 00:04:24.450 align:start position:0% transactions going through that address 00:04:24.450 --> 00:04:26.450 align:start position:0% transactions going through that address other<00:04:24.660> ones<00:04:24.900> use<00:04:25.080> you<00:04:25.260> know<00:04:25.380> contracts<00:04:26.250> and 00:04:26.450 --> 00:04:26.460 align:start position:0% other ones use you know contracts and 00:04:26.460 --> 00:04:29.360 align:start position:0% other ones use you know contracts and stuff<00:04:26.520> or<00:04:27.270> you<00:04:28.080> know<00:04:28.110> lots<00:04:28.500> of<00:04:28.620> them<00:04:28.800> like<00:04:29.100> we 00:04:29.360 --> 00:04:29.370 align:start position:0% stuff or you know lots of them like we 00:04:29.370 --> 00:04:30.950 align:start position:0% stuff or you know lots of them like we like<00:04:29.700> coinbase<00:04:29.910> in<00:04:30.150> our<00:04:30.240> wallet<00:04:30.600> we<00:04:30.630> just 00:04:30.950 --> 00:04:30.960 align:start position:0% like coinbase in our wallet we just 00:04:30.960 --> 00:04:33.440 align:start position:0% like coinbase in our wallet we just basically<00:04:31.800> have<00:04:32.190> just<00:04:32.220> you<00:04:32.640> know<00:04:32.730> hundreds<00:04:33.390> of 00:04:33.440 --> 00:04:33.450 align:start position:0% basically have just you know hundreds of 00:04:33.450 --> 00:04:35.570 align:start position:0% basically have just you know hundreds of millions<00:04:33.510> of<00:04:33.780> addresses<00:04:34.260> and<00:04:34.500> so<00:04:34.680> we're 00:04:35.570 --> 00:04:35.580 align:start position:0% millions of addresses and so we're 00:04:35.580 --> 00:04:37.790 align:start position:0% millions of addresses and so we're always<00:04:35.760> have<00:04:36.090> it<00:04:36.240> all<00:04:36.360> over<00:04:36.660> the<00:04:36.810> place<00:04:37.020> and<00:04:37.230> so 00:04:37.790 --> 00:04:37.800 align:start position:0% always have it all over the place and so 00:04:37.800 --> 00:04:39.980 align:start position:0% always have it all over the place and so when<00:04:38.250> we<00:04:38.400> hit<00:04:38.940> the<00:04:39.090> situation<00:04:39.630> it<00:04:39.780> can<00:04:39.870> be 00:04:39.980 --> 00:04:39.990 align:start position:0% when we hit the situation it can be 00:04:39.990 --> 00:04:41.630 align:start position:0% when we hit the situation it can be fairly<00:04:40.200> limited<00:04:40.560> in<00:04:40.920> scope<00:04:41.130> but<00:04:41.190> it<00:04:41.460> can 00:04:41.630 --> 00:04:41.640 align:start position:0% fairly limited in scope but it can 00:04:41.640 --> 00:04:43.370 align:start position:0% fairly limited in scope but it can affect<00:04:41.940> like<00:04:42.180> a<00:04:42.210> subset<00:04:42.630> of<00:04:42.660> customers<00:04:43.140> and 00:04:43.370 --> 00:04:43.380 align:start position:0% affect like a subset of customers and 00:04:43.380 --> 00:04:45.860 align:start position:0% affect like a subset of customers and there's<00:04:44.130> not<00:04:44.220> great<00:04:44.400> solutions<00:04:45.330> for<00:04:45.570> it<00:04:45.660> yet 00:04:45.860 --> 00:04:45.870 align:start position:0% there's not great solutions for it yet 00:04:45.870 --> 00:04:47.990 align:start position:0% there's not great solutions for it yet other<00:04:46.860> than<00:04:46.980> replacing<00:04:47.520> it<00:04:47.580> which<00:04:47.700> is<00:04:47.820> a 00:04:47.990 --> 00:04:48.000 align:start position:0% other than replacing it which is a 00:04:48.000 --> 00:04:49.370 align:start position:0% other than replacing it which is a solution<00:04:48.540> but<00:04:48.720> it's<00:04:48.900> a<00:04:48.960> more<00:04:49.110> sort<00:04:49.320> of 00:04:49.370 --> 00:04:49.380 align:start position:0% solution but it's a more sort of 00:04:49.380 --> 00:04:50.750 align:start position:0% solution but it's a more sort of complicated<00:04:49.920> one<00:04:50.010> to<00:04:50.100> manage<00:04:50.280> and<00:04:50.550> especially 00:04:50.750 --> 00:04:50.760 align:start position:0% complicated one to manage and especially 00:04:50.760 --> 00:04:51.950 align:start position:0% complicated one to manage and especially when<00:04:50.940> you've<00:04:51.030> got<00:04:51.150> a<00:04:51.180> lot<00:04:51.390> of<00:04:51.480> these<00:04:51.570> going<00:04:51.840> on 00:04:51.950 --> 00:04:51.960 align:start position:0% when you've got a lot of these going on 00:04:51.960 --> 00:04:53.840 align:start position:0% when you've got a lot of these going on and<00:04:52.170> so<00:04:52.710> this<00:04:52.890> this<00:04:53.040> thing<00:04:53.250> where<00:04:53.400> so<00:04:53.520> the<00:04:53.700> gas 00:04:53.840 --> 00:04:53.850 align:start position:0% and so this this thing where so the gas 00:04:53.850 --> 00:04:56.420 align:start position:0% and so this this thing where so the gas prices<00:04:54.270> can<00:04:54.450> spike<00:04:54.750> and<00:04:55.680> sort<00:04:56.130> of<00:04:56.190> delay 00:04:56.420 --> 00:04:56.430 align:start position:0% prices can spike and sort of delay 00:04:56.430 --> 00:04:58.340 align:start position:0% prices can spike and sort of delay everything<00:04:56.760> is<00:04:57.000> really<00:04:57.360> challenging<00:04:57.600> this 00:04:58.340 --> 00:04:58.350 align:start position:0% everything is really challenging this 00:04:58.350 --> 00:05:00.410 align:start position:0% everything is really challenging this example<00:04:58.800> that<00:04:59.040> I've<00:04:59.160> seen<00:04:59.580> in<00:05:00.000> our<00:05:00.120> systems 00:05:00.410 --> 00:05:00.420 align:start position:0% example that I've seen in our systems 00:05:00.420 --> 00:05:02.300 align:start position:0% example that I've seen in our systems before<00:05:00.510> is<00:05:00.900> a<00:05:01.140> transaction<00:05:01.620> two<00:05:02.070> minutes 00:05:02.300 --> 00:05:02.310 align:start position:0% before is a transaction two minutes 00:05:02.310 --> 00:05:04.790 align:start position:0% before is a transaction two minutes apart<00:05:02.370> same<00:05:02.880> gas<00:05:03.090> price<00:05:03.470> one<00:05:04.470> took<00:05:04.620> two 00:05:04.790 --> 00:05:04.800 align:start position:0% apart same gas price one took two 00:05:04.800 --> 00:05:06.230 align:start position:0% apart same gas price one took two minutes<00:05:04.920> to<00:05:05.130> confirm<00:05:05.430> in<00:05:05.580> the<00:05:05.640> electric<00:05:05.880> 13 00:05:06.230 --> 00:05:06.240 align:start position:0% minutes to confirm in the electric 13 00:05:06.240 --> 00:05:08.330 align:start position:0% minutes to confirm in the electric 13 hours<00:05:06.570> and<00:05:07.200> that's<00:05:07.590> not<00:05:07.740> a<00:05:07.800> really<00:05:08.040> great<00:05:08.130> way 00:05:08.330 --> 00:05:08.340 align:start position:0% hours and that's not a really great way 00:05:08.340 --> 00:05:10.970 align:start position:0% hours and that's not a really great way to<00:05:08.370> build<00:05:08.820> you<00:05:09.330> know<00:05:09.360> systems<00:05:09.900> interior<00:05:10.800> to 00:05:10.970 --> 00:05:10.980 align:start position:0% to build you know systems interior to 00:05:10.980 --> 00:05:12.230 align:start position:0% to build you know systems interior to build<00:05:11.130> a<00:05:11.190> business<00:05:11.340> on<00:05:11.670> the<00:05:11.760> theorem<00:05:12.060> and<00:05:12.180> so 00:05:12.230 --> 00:05:12.240 align:start position:0% build a business on the theorem and so 00:05:12.240 --> 00:05:14.270 align:start position:0% build a business on the theorem and so it's<00:05:12.390> a<00:05:12.480> it<00:05:12.840> doesn't<00:05:13.110> just<00:05:13.470> affect<00:05:13.650> us<00:05:13.980> I<00:05:14.130> could 00:05:14.270 --> 00:05:14.280 align:start position:0% it's a it doesn't just affect us I could 00:05:14.280 --> 00:05:15.620 align:start position:0% it's a it doesn't just affect us I could just<00:05:14.400> affect<00:05:14.670> a<00:05:14.760> business<00:05:15.090> doing<00:05:15.270> this<00:05:15.390> who 00:05:15.620 --> 00:05:15.630 align:start position:0% just affect a business doing this who 00:05:15.630 --> 00:05:16.700 align:start position:0% just affect a business doing this who doesn't<00:05:15.780> have<00:05:15.960> you<00:05:16.170> know<00:05:16.260> as<00:05:16.380> sophisticated 00:05:16.700 --> 00:05:16.710 align:start position:0% doesn't have you know as sophisticated 00:05:16.710 --> 00:05:19.970 align:start position:0% doesn't have you know as sophisticated infrastructure<00:05:17.550> to<00:05:17.700> handle<00:05:17.850> and<00:05:18.680> and<00:05:19.680> one<00:05:19.890> of 00:05:19.970 --> 00:05:19.980 align:start position:0% infrastructure to handle and and one of 00:05:19.980 --> 00:05:21.950 align:start position:0% infrastructure to handle and and one of the<00:05:20.040> things<00:05:20.280> that<00:05:20.520> we've<00:05:21.390> sort<00:05:21.660> of<00:05:21.720> talked 00:05:21.950 --> 00:05:21.960 align:start position:0% the things that we've sort of talked 00:05:21.960 --> 00:05:23.420 align:start position:0% the things that we've sort of talked about<00:05:22.200> and<00:05:22.350> seen<00:05:22.500> come<00:05:22.650> up<00:05:22.800> with<00:05:22.950> a<00:05:22.980> few<00:05:23.160> times 00:05:23.420 --> 00:05:23.430 align:start position:0% about and seen come up with a few times 00:05:23.430 --> 00:05:26.180 align:start position:0% about and seen come up with a few times is<00:05:23.790> you<00:05:24.780> know<00:05:24.870> this<00:05:24.960> idea<00:05:25.290> that<00:05:25.860> comes<00:05:26.010> from 00:05:26.180 --> 00:05:26.190 align:start position:0% is you know this idea that comes from 00:05:26.190 --> 00:05:28.670 align:start position:0% is you know this idea that comes from sort<00:05:26.430> of<00:05:26.460> Bitcoin<00:05:26.820> of<00:05:27.150> this<00:05:27.630> child<00:05:28.200> pays<00:05:28.440> for 00:05:28.670 --> 00:05:28.680 align:start position:0% sort of Bitcoin of this child pays for 00:05:28.680 --> 00:05:31.340 align:start position:0% sort of Bitcoin of this child pays for parent<00:05:28.950> style<00:05:29.370> of<00:05:29.550> transaction<00:05:30.090> where<00:05:30.870> it's<00:05:31.230> a 00:05:31.340 --> 00:05:31.350 align:start position:0% parent style of transaction where it's a 00:05:31.350 --> 00:05:34.040 align:start position:0% parent style of transaction where it's a similar<00:05:31.680> mechanism<00:05:31.890> of<00:05:32.370> sort<00:05:32.670> of<00:05:33.050> recovering 00:05:34.040 --> 00:05:34.050 align:start position:0% similar mechanism of sort of recovering 00:05:34.050 --> 00:05:35.720 align:start position:0% similar mechanism of sort of recovering sort<00:05:34.740> of<00:05:34.800> pending<00:05:35.130> ones<00:05:35.280> that<00:05:35.490> are<00:05:35.610> like 00:05:35.720 --> 00:05:35.730 align:start position:0% sort of pending ones that are like 00:05:35.730 --> 00:05:37.070 align:start position:0% sort of pending ones that are like chained<00:05:35.970> together<00:05:36.150> in<00:05:36.540> some<00:05:36.690> ways<00:05:36.840> like<00:05:36.960> in 00:05:37.070 --> 00:05:37.080 align:start position:0% chained together in some ways like in 00:05:37.080 --> 00:05:38.030 align:start position:0% chained together in some ways like in this<00:05:37.140> case<00:05:37.320> it's<00:05:37.470> chained<00:05:37.710> by<00:05:37.800> like<00:05:37.950> that 00:05:38.030 --> 00:05:38.040 align:start position:0% this case it's chained by like that 00:05:38.040 --> 00:05:40.190 align:start position:0% this case it's chained by like that nonce<00:05:38.250> it's<00:05:38.490> different<00:05:38.700> in<00:05:38.820> Bitcoin<00:05:39.120> but<00:05:39.360> the 00:05:40.190 --> 00:05:40.200 align:start position:0% nonce it's different in Bitcoin but the 00:05:40.200 --> 00:05:41.750 align:start position:0% nonce it's different in Bitcoin but the theory<00:05:40.470> is<00:05:40.500> sort<00:05:40.740> of<00:05:40.770> you<00:05:40.920> you<00:05:41.190> put<00:05:41.490> a<00:05:41.520> new 00:05:41.750 --> 00:05:41.760 align:start position:0% theory is sort of you you put a new 00:05:41.760 --> 00:05:43.460 align:start position:0% theory is sort of you you put a new transaction<00:05:42.360> out<00:05:42.450> like<00:05:42.690> on<00:05:42.810> top<00:05:43.050> of<00:05:43.200> all<00:05:43.320> these 00:05:43.460 --> 00:05:43.470 align:start position:0% transaction out like on top of all these 00:05:43.470 --> 00:05:45.500 align:start position:0% transaction out like on top of all these with<00:05:43.620> a<00:05:43.680> high<00:05:43.860> fee<00:05:44.220> and<00:05:44.460> then<00:05:44.910> that<00:05:45.180> sort<00:05:45.360> of 00:05:45.500 --> 00:05:45.510 align:start position:0% with a high fee and then that sort of 00:05:45.510 --> 00:05:47.360 align:start position:0% with a high fee and then that sort of can<00:05:45.810> subsidize<00:05:46.350> the<00:05:46.560> rest<00:05:46.740> of<00:05:46.890> the<00:05:46.980> lower<00:05:47.130> fees 00:05:47.360 --> 00:05:47.370 align:start position:0% can subsidize the rest of the lower fees 00:05:47.370 --> 00:05:48.980 align:start position:0% can subsidize the rest of the lower fees and<00:05:47.730> get<00:05:47.880> it<00:05:47.970> back<00:05:48.120> to<00:05:48.180> closer<00:05:48.660> to<00:05:48.840> what<00:05:48.960> the 00:05:48.980 --> 00:05:48.990 align:start position:0% and get it back to closer to what the 00:05:48.990 --> 00:05:50.570 align:start position:0% and get it back to closer to what the real<00:05:49.230> network<00:05:49.530> fee<00:05:49.770> is<00:05:49.830> so<00:05:50.040> miners<00:05:50.310> will<00:05:50.430> pick 00:05:50.570 --> 00:05:50.580 align:start position:0% real network fee is so miners will pick 00:05:50.580 --> 00:05:52.910 align:start position:0% real network fee is so miners will pick it<00:05:50.610> up<00:05:50.790> and<00:05:51.060> look<00:05:51.330> up<00:05:51.510> all<00:05:51.660> of<00:05:51.780> them<00:05:51.960> at<00:05:52.050> once<00:05:52.380> so 00:05:52.910 --> 00:05:52.920 align:start position:0% it up and look up all of them at once so 00:05:52.920 --> 00:05:54.830 align:start position:0% it up and look up all of them at once so you<00:05:53.340> just<00:05:53.490> send<00:05:53.700> this<00:05:53.760> like<00:05:53.940> transaction<00:05:54.600> with 00:05:54.830 --> 00:05:54.840 align:start position:0% you just send this like transaction with 00:05:54.840 --> 00:05:55.880 align:start position:0% you just send this like transaction with this<00:05:54.930> really<00:05:55.170> high<00:05:55.290> fee<00:05:55.500> and<00:05:55.680> then<00:05:55.770> all<00:05:55.860> a 00:05:55.880 --> 00:05:55.890 align:start position:0% this really high fee and then all a 00:05:55.890 --> 00:05:57.410 align:start position:0% this really high fee and then all a sudden<00:05:55.950> you<00:05:56.220> know<00:05:56.310> you're<00:05:56.490> maybe<00:05:56.640> you<00:05:56.850> know<00:05:56.940> 50 00:05:57.410 --> 00:05:57.420 align:start position:0% sudden you know you're maybe you know 50 00:05:57.420 --> 00:05:59.270 align:start position:0% sudden you know you're maybe you know 50 whatever<00:05:57.630> transactions<00:05:58.290> are<00:05:58.410> all<00:05:58.530> all<00:05:59.130> can 00:05:59.270 --> 00:05:59.280 align:start position:0% whatever transactions are all all can 00:05:59.280 --> 00:06:00.680 align:start position:0% whatever transactions are all all can get<00:05:59.370> confirmed<00:05:59.820> and<00:06:00.120> you<00:06:00.390> can<00:06:00.510> sort<00:06:00.660> of 00:06:00.680 --> 00:06:00.690 align:start position:0% get confirmed and you can sort of 00:06:00.690 --> 00:06:02.090 align:start position:0% get confirmed and you can sort of recover<00:06:00.990> that<00:06:01.170> and<00:06:01.380> have<00:06:01.560> a<00:06:01.590> sort<00:06:01.830> of<00:06:01.860> a<00:06:01.950> better 00:06:02.090 --> 00:06:02.100 align:start position:0% recover that and have a sort of a better 00:06:02.100 --> 00:06:05.330 align:start position:0% recover that and have a sort of a better experience<00:06:02.400> for<00:06:02.670> your<00:06:03.210> customers<00:06:03.390> and<00:06:04.340> so 00:06:05.330 --> 00:06:05.340 align:start position:0% experience for your customers and so 00:06:05.340 --> 00:06:07.100 align:start position:0% experience for your customers and so that's<00:06:05.520> yeah<00:06:06.120> that's<00:06:06.360> that's<00:06:06.570> an<00:06:06.750> interesting 00:06:07.100 --> 00:06:07.110 align:start position:0% that's yeah that's that's an interesting 00:06:07.110 --> 00:06:09.110 align:start position:0% that's yeah that's that's an interesting one<00:06:07.230> yeah<00:06:07.470> so<00:06:07.800> let's<00:06:08.370> talk<00:06:08.520> a<00:06:08.580> bit<00:06:08.670> about<00:06:08.910> that 00:06:09.110 --> 00:06:09.120 align:start position:0% one yeah so let's talk a bit about that 00:06:09.120 --> 00:06:11.960 align:start position:0% one yeah so let's talk a bit about that so<00:06:09.690> so<00:06:10.200> firstly<00:06:10.470> you<00:06:10.590> know<00:06:10.830> RBF<00:06:11.460> like<00:06:11.910> to 00:06:11.960 --> 00:06:11.970 align:start position:0% so so firstly you know RBF like to 00:06:11.970 --> 00:06:14.930 align:start position:0% so so firstly you know RBF like to replace<00:06:12.210> by<00:06:12.390> fee<00:06:12.630> it<00:06:13.530> works<00:06:13.830> today<00:06:14.340> because 00:06:14.930 --> 00:06:14.940 align:start position:0% replace by fee it works today because 00:06:14.940 --> 00:06:17.390 align:start position:0% replace by fee it works today because it's<00:06:15.210> you<00:06:15.690> know<00:06:15.780> you<00:06:15.840> can<00:06:15.930> do<00:06:16.140> it<00:06:16.230> yourself<00:06:16.400> but 00:06:17.390 --> 00:06:17.400 align:start position:0% it's you know you can do it yourself but 00:06:17.400 --> 00:06:21.140 align:start position:0% it's you know you can do it yourself but one<00:06:17.550> of<00:06:17.580> the<00:06:17.730> larger<00:06:18.170> I<00:06:19.370> think<00:06:20.370> confusions 00:06:21.140 --> 00:06:21.150 align:start position:0% one of the larger I think confusions 00:06:21.150 --> 00:06:22.880 align:start position:0% one of the larger I think confusions with<00:06:21.240> that<00:06:21.390> you<00:06:22.110> know<00:06:22.230> when<00:06:22.410> you<00:06:22.500> change<00:06:22.530> the 00:06:22.880 --> 00:06:22.890 align:start position:0% with that you know when you change the 00:06:22.890 --> 00:06:24.560 align:start position:0% with that you know when you change the Pheo<00:06:23.100> so<00:06:23.460> change<00:06:23.700> what<00:06:23.880> you're<00:06:24.000> signing<00:06:24.210> and 00:06:24.560 --> 00:06:24.570 align:start position:0% Pheo so change what you're signing and 00:06:24.570 --> 00:06:28.040 align:start position:0% Pheo so change what you're signing and therefore<00:06:25.470> the<00:06:25.980> th<00:06:26.250> ash<00:06:26.570> gets<00:06:27.570> changed<00:06:27.840> so 00:06:28.040 --> 00:06:28.050 align:start position:0% therefore the th ash gets changed so 00:06:28.050 --> 00:06:31.850 align:start position:0% therefore the th ash gets changed so you're<00:06:28.290> displaying<00:06:28.740> a<00:06:28.830> TX<00:06:29.100> hash<00:06:29.280> TX<00:06:30.240> ID<00:06:30.450> to<00:06:30.900> the 00:06:31.850 --> 00:06:31.860 align:start position:0% you're displaying a TX hash TX ID to the 00:06:31.860 --> 00:06:34.280 align:start position:0% you're displaying a TX hash TX ID to the customer<00:06:32.700> of<00:06:32.850> the<00:06:33.120> person<00:06:33.600> receiving<00:06:34.170> the 00:06:34.280 --> 00:06:34.290 align:start position:0% customer of the person receiving the 00:06:34.290 --> 00:06:36.790 align:start position:0% customer of the person receiving the funds<00:06:34.560> then<00:06:34.770> it<00:06:35.130> would<00:06:35.670> be<00:06:35.760> different 00:06:36.790 --> 00:06:36.800 align:start position:0% funds then it would be different 00:06:36.800 --> 00:06:41.930 align:start position:0% funds then it would be different with<00:06:38.300> CP<00:06:39.300> FP<00:06:39.740> it's<00:06:40.740> you<00:06:41.250> know<00:06:41.340> well-known<00:06:41.760> in 00:06:41.930 --> 00:06:41.940 align:start position:0% with CP FP it's you know well-known in 00:06:41.940 --> 00:06:46.430 align:start position:0% with CP FP it's you know well-known in Bitcoin<00:06:42.630> land<00:06:43.970> the<00:06:44.990> the<00:06:45.990> common<00:06:46.290> challenges 00:06:46.430 --> 00:06:46.440 align:start position:0% Bitcoin land the the common challenges 00:06:46.440 --> 00:06:49.820 align:start position:0% Bitcoin land the the common challenges you<00:06:46.920> know<00:06:47.010> the<00:06:47.550> idea<00:06:47.820> is<00:06:48.110> you<00:06:49.110> have<00:06:49.140> ten 00:06:49.820 --> 00:06:49.830 align:start position:0% you know the idea is you have ten 00:06:49.830 --> 00:06:51.650 align:start position:0% you know the idea is you have ten transactions<00:06:50.310> not<00:06:50.430> confirmed<00:06:50.850> so<00:06:51.360> you<00:06:51.420> put 00:06:51.650 --> 00:06:51.660 align:start position:0% transactions not confirmed so you put 00:06:51.660 --> 00:06:53.660 align:start position:0% transactions not confirmed so you put another<00:06:51.840> one<00:06:52.020> transaction<00:06:52.290> 11<00:06:52.800> and<00:06:53.100> it's<00:06:53.520> got 00:06:53.660 --> 00:06:53.670 align:start position:0% another one transaction 11 and it's got 00:06:53.670 --> 00:06:55.910 align:start position:0% another one transaction 11 and it's got an<00:06:53.760> outsized<00:06:54.150> fee<00:06:54.420> and<00:06:54.960> the<00:06:55.170> outsized<00:06:55.530> fee 00:06:55.910 --> 00:06:55.920 align:start position:0% an outsized fee and the outsized fee 00:06:55.920 --> 00:06:58.640 align:start position:0% an outsized fee and the outsized fee helps<00:06:56.670> to<00:06:56.970> tell<00:06:57.720> the<00:06:57.840> maya<00:06:57.990> that<00:06:58.200> hey<00:06:58.350> you<00:06:58.620> know 00:06:58.640 --> 00:06:58.650 align:start position:0% helps to tell the maya that hey you know 00:06:58.650 --> 00:07:01.040 align:start position:0% helps to tell the maya that hey you know if<00:06:58.920> you<00:06:59.010> want<00:06:59.220> to<00:06:59.310> get<00:06:59.610> this<00:06:59.730> outsized<00:07:00.150> fee<00:07:00.390> you 00:07:01.040 --> 00:07:01.050 align:start position:0% if you want to get this outsized fee you 00:07:01.050 --> 00:07:03.140 align:start position:0% if you want to get this outsized fee you you<00:07:01.710> you<00:07:02.070> go<00:07:02.190> to<00:07:02.250> mine<00:07:02.460> all<00:07:02.610> these<00:07:02.790> other<00:07:02.940> ten 00:07:03.140 --> 00:07:03.150 align:start position:0% you you go to mine all these other ten 00:07:03.150 --> 00:07:07.370 align:start position:0% you you go to mine all these other ten first<00:07:03.840> um<00:07:04.800> the<00:07:05.430> the<00:07:05.930> challenge<00:07:06.930> for<00:07:07.050> the<00:07:07.140> miner 00:07:07.370 --> 00:07:07.380 align:start position:0% first um the the challenge for the miner 00:07:07.380 --> 00:07:09.260 align:start position:0% first um the the challenge for the miner then<00:07:07.650> is<00:07:07.890> how<00:07:08.130> are<00:07:08.370> they<00:07:08.460> going<00:07:08.490> to<00:07:08.760> figure<00:07:09.120> out 00:07:09.260 --> 00:07:09.270 align:start position:0% then is how are they going to figure out 00:07:09.270 --> 00:07:12.280 align:start position:0% then is how are they going to figure out that<00:07:09.900> this<00:07:10.710> string<00:07:11.070> of<00:07:11.160> ten<00:07:11.340> transactions 00:07:12.280 --> 00:07:12.290 align:start position:0% that this string of ten transactions 00:07:12.290 --> 00:07:14.990 align:start position:0% that this string of ten transactions combined<00:07:13.290> with<00:07:13.410> xi<00:07:13.890> is<00:07:14.550> really<00:07:14.850> worthwhile 00:07:14.990 --> 00:07:15.000 align:start position:0% combined with xi is really worthwhile 00:07:15.000 --> 00:07:17.180 align:start position:0% combined with xi is really worthwhile for<00:07:15.360> them<00:07:15.450> to<00:07:15.600> mine<00:07:15.780> because<00:07:16.350> if<00:07:16.920> they<00:07:17.070> were<00:07:17.160> to 00:07:17.180 --> 00:07:17.190 align:start position:0% for them to mine because if they were to 00:07:17.190 --> 00:07:19.760 align:start position:0% for them to mine because if they were to do<00:07:17.370> this<00:07:17.520> infinitely<00:07:17.970> like<00:07:18.930> after<00:07:19.320> a<00:07:19.350> thousand 00:07:19.760 --> 00:07:19.770 align:start position:0% do this infinitely like after a thousand 00:07:19.770 --> 00:07:21.110 align:start position:0% do this infinitely like after a thousand and<00:07:19.890> thousand<00:07:20.130> and<00:07:20.250> one<00:07:20.370> transactions<00:07:20.880> then 00:07:21.110 --> 00:07:21.120 align:start position:0% and thousand and one transactions then 00:07:21.120 --> 00:07:23.120 align:start position:0% and thousand and one transactions then they<00:07:21.960> can<00:07:22.110> run<00:07:22.230> out<00:07:22.320> of<00:07:22.350> memory<00:07:22.560> just<00:07:22.860> waiting 00:07:23.120 --> 00:07:23.130 align:start position:0% they can run out of memory just waiting 00:07:23.130 --> 00:07:27.580 align:start position:0% they can run out of memory just waiting for<00:07:23.370> you<00:07:23.580> to<00:07:23.730> come<00:07:23.940> up<00:07:24.090> with<00:07:24.270> another<00:07:24.930> big<00:07:26.480> no 00:07:27.580 --> 00:07:27.590 align:start position:0% for you to come up with another big no 00:07:27.590 --> 00:07:29.690 align:start position:0% for you to come up with another big no that<00:07:28.590> was<00:07:28.680> the<00:07:28.770> thing<00:07:28.920> that's<00:07:29.040> brought<00:07:29.190> up<00:07:29.340> it 00:07:29.690 --> 00:07:29.700 align:start position:0% that was the thing that's brought up it 00:07:29.700 --> 00:07:31.520 align:start position:0% that was the thing that's brought up it came<00:07:29.940> up<00:07:30.090> in<00:07:30.180> if<00:07:30.300> you're<00:07:30.450> in<00:07:30.570> maybe<00:07:31.230> a<00:07:31.320> few 00:07:31.520 --> 00:07:31.530 align:start position:0% came up in if you're in maybe a few 00:07:31.530 --> 00:07:33.170 align:start position:0% came up in if you're in maybe a few months<00:07:31.710> ago<00:07:31.800> now<00:07:31.920> when<00:07:32.790> there<00:07:32.940> was<00:07:33.060> this 00:07:33.170 --> 00:07:33.180 align:start position:0% months ago now when there was this 00:07:33.180 --> 00:07:35.810 align:start position:0% months ago now when there was this exchange<00:07:34.170> that<00:07:34.500> was<00:07:34.800> sort<00:07:35.220> of<00:07:35.250> incentivizing 00:07:35.810 --> 00:07:35.820 align:start position:0% exchange that was sort of incentivizing 00:07:35.820 --> 00:07:39.140 align:start position:0% exchange that was sort of incentivizing lots<00:07:36.390> of<00:07:36.510> volume<00:07:36.900> on<00:07:37.140> the<00:07:37.560> network<00:07:37.880> so<00:07:38.880> it<00:07:39.060> was 00:07:39.140 --> 00:07:39.150 align:start position:0% lots of volume on the network so it was 00:07:39.150 --> 00:07:40.610 align:start position:0% lots of volume on the network so it was just<00:07:39.300> kind<00:07:39.510> of<00:07:39.540> backing<00:07:39.870> up<00:07:39.930> the<00:07:40.050> network<00:07:40.230> I 00:07:40.610 --> 00:07:40.620 align:start position:0% just kind of backing up the network I 00:07:40.620 --> 00:07:41.720 align:start position:0% just kind of backing up the network I think<00:07:40.860> this<00:07:40.950> is<00:07:41.070> another<00:07:41.310> sort<00:07:41.550> of<00:07:41.580> big 00:07:41.720 --> 00:07:41.730 align:start position:0% think this is another sort of big 00:07:41.730 --> 00:07:43.220 align:start position:0% think this is another sort of big challenge<00:07:42.060> with<00:07:42.120> the<00:07:42.240> theorem<00:07:42.570> is<00:07:42.750> that 00:07:43.220 --> 00:07:43.230 align:start position:0% challenge with the theorem is that 00:07:43.230 --> 00:07:45.650 align:start position:0% challenge with the theorem is that individual<00:07:43.800> token<00:07:44.430> sales<00:07:44.640> individual<00:07:45.300> just 00:07:45.650 --> 00:07:45.660 align:start position:0% individual token sales individual just 00:07:45.660 --> 00:07:47.990 align:start position:0% individual token sales individual just knew<00:07:45.930> you<00:07:46.470> know<00:07:46.560> games<00:07:47.070> or<00:07:47.340> whatever<00:07:47.550> can<00:07:47.880> like 00:07:47.990 --> 00:07:48.000 align:start position:0% knew you know games or whatever can like 00:07:48.000 --> 00:07:49.970 align:start position:0% knew you know games or whatever can like significantly<00:07:48.780> impact<00:07:49.260> the<00:07:49.350> network<00:07:49.680> very 00:07:49.970 --> 00:07:49.980 align:start position:0% significantly impact the network very 00:07:49.980 --> 00:07:52.010 align:start position:0% significantly impact the network very very<00:07:50.310> quickly<00:07:50.580> and<00:07:50.880> very<00:07:51.330> fast<00:07:51.630> they<00:07:51.810> start 00:07:52.010 --> 00:07:52.020 align:start position:0% very quickly and very fast they start 00:07:52.020 --> 00:07:54.140 align:start position:0% very quickly and very fast they start the<00:07:52.110> token<00:07:52.380> sale<00:07:52.530> the<00:07:52.740> fees<00:07:52.920> skyrocket<00:07:53.760> now 00:07:54.140 --> 00:07:54.150 align:start position:0% the token sale the fees skyrocket now 00:07:54.150 --> 00:07:55.310 align:start position:0% the token sale the fees skyrocket now everybody<00:07:54.570> in<00:07:54.660> the<00:07:54.720> networks<00:07:54.930> paying<00:07:55.140> more 00:07:55.310 --> 00:07:55.320 align:start position:0% everybody in the networks paying more 00:07:55.320 --> 00:07:56.960 align:start position:0% everybody in the networks paying more any<00:07:55.500> app<00:07:55.680> you've<00:07:55.920> built<00:07:56.130> is<00:07:56.340> just<00:07:56.490> now<00:07:56.700> all<00:07:56.880> of 00:07:56.960 --> 00:07:56.970 align:start position:0% any app you've built is just now all of 00:07:56.970 --> 00:07:58.850 align:start position:0% any app you've built is just now all of a<00:07:57.000> sudden<00:07:57.030> paying<00:07:57.390> more<00:07:57.600> and<00:07:58.500> then<00:07:58.680> now<00:07:58.800> you 00:07:58.850 --> 00:07:58.860 align:start position:0% a sudden paying more and then now you 00:07:58.860 --> 00:08:00.890 align:start position:0% a sudden paying more and then now you also<00:07:59.160> as<00:07:59.700> you<00:07:59.940> know<00:07:59.970> anybody<00:08:00.450> sending 00:08:00.890 --> 00:08:00.900 align:start position:0% also as you know anybody sending 00:08:00.900 --> 00:08:02.630 align:start position:0% also as you know anybody sending transactions<00:08:01.410> get<00:08:01.590> them<00:08:01.740> stuck<00:08:01.950> because<00:08:02.190> the 00:08:02.630 --> 00:08:02.640 align:start position:0% transactions get them stuck because the 00:08:02.640 --> 00:08:04.340 align:start position:0% transactions get them stuck because the the<00:08:02.910> estimate<00:08:03.270> can<00:08:03.390> only<00:08:03.510> update<00:08:03.720> once<00:08:04.110> it<00:08:04.230> has 00:08:04.340 --> 00:08:04.350 align:start position:0% the estimate can only update once it has 00:08:04.350 --> 00:08:06.560 align:start position:0% the estimate can only update once it has all<00:08:04.530> the<00:08:04.650> new<00:08:04.770> data<00:08:04.950> so<00:08:05.340> you're<00:08:06.210> kind<00:08:06.390> of<00:08:06.450> at 00:08:06.560 --> 00:08:06.570 align:start position:0% all the new data so you're kind of at 00:08:06.570 --> 00:08:07.910 align:start position:0% all the new data so you're kind of at this<00:08:06.750> you<00:08:06.960> can't<00:08:07.140> ever<00:08:07.260> predict<00:08:07.800> it 00:08:07.910 --> 00:08:07.920 align:start position:0% this you can't ever predict it 00:08:07.920 --> 00:08:09.800 align:start position:0% this you can't ever predict it necessarily<00:08:08.580> you<00:08:09.150> can<00:08:09.270> have<00:08:09.360> some<00:08:09.540> sort<00:08:09.720> of 00:08:09.800 --> 00:08:09.810 align:start position:0% necessarily you can have some sort of 00:08:09.810 --> 00:08:11.150 align:start position:0% necessarily you can have some sort of models<00:08:10.110> and<00:08:10.170> like<00:08:10.320> generally<00:08:10.710> it<00:08:10.770> works<00:08:10.890> and 00:08:11.150 --> 00:08:11.160 align:start position:0% models and like generally it works and 00:08:11.160 --> 00:08:12.920 align:start position:0% models and like generally it works and it<00:08:11.220> updates<00:08:11.400> fairly<00:08:11.910> quickly<00:08:12.120> but<00:08:12.480> there<00:08:12.810> is 00:08:12.920 --> 00:08:12.930 align:start position:0% it updates fairly quickly but there is 00:08:12.930 --> 00:08:14.780 align:start position:0% it updates fairly quickly but there is this<00:08:13.050> sort<00:08:13.200> of<00:08:13.290> delay<00:08:13.590> and<00:08:13.830> that<00:08:14.460> was<00:08:14.580> a<00:08:14.610> thing 00:08:14.780 --> 00:08:14.790 align:start position:0% this sort of delay and that was a thing 00:08:14.790 --> 00:08:16.730 align:start position:0% this sort of delay and that was a thing brought<00:08:15.030> up<00:08:15.180> when<00:08:15.930> I<00:08:15.960> was<00:08:16.080> started<00:08:16.440> we<00:08:16.560> talked 00:08:16.730 --> 00:08:16.740 align:start position:0% brought up when I was started we talked 00:08:16.740 --> 00:08:17.780 align:start position:0% brought up when I was started we talked about<00:08:16.950> in<00:08:17.040> theory<00:08:17.280> I'm<00:08:17.370> a<00:08:17.460> little<00:08:17.640> bit<00:08:17.760> I 00:08:17.780 --> 00:08:17.790 align:start position:0% about in theory I'm a little bit I 00:08:17.790 --> 00:08:19.670 align:start position:0% about in theory I'm a little bit I believe<00:08:18.330> on<00:08:18.540> the<00:08:18.690> parity<00:08:19.020> repo<00:08:19.290> is<00:08:19.470> an<00:08:19.560> issue 00:08:19.670 --> 00:08:19.680 align:start position:0% believe on the parity repo is an issue 00:08:19.680 --> 00:08:21.650 align:start position:0% believe on the parity repo is an issue that<00:08:19.950> has<00:08:20.070> some<00:08:20.280> sort<00:08:20.400> of<00:08:20.490> proposed<00:08:20.850> model<00:08:21.180> but 00:08:21.650 --> 00:08:21.660 align:start position:0% that has some sort of proposed model but 00:08:21.660 --> 00:08:22.760 align:start position:0% that has some sort of proposed model but they're<00:08:21.780> specifically<00:08:22.230> talking<00:08:22.440> about<00:08:22.500> sort 00:08:22.760 --> 00:08:22.770 align:start position:0% they're specifically talking about sort 00:08:22.770 --> 00:08:24.230 align:start position:0% they're specifically talking about sort of<00:08:22.800> like<00:08:22.890> toss<00:08:23.250> vectors<00:08:23.640> and<00:08:23.790> stuff<00:08:23.970> with<00:08:24.150> this 00:08:24.230 --> 00:08:24.240 align:start position:0% of like toss vectors and stuff with this 00:08:24.240 --> 00:08:26.090 align:start position:0% of like toss vectors and stuff with this how<00:08:24.570> long<00:08:24.810> you<00:08:24.990> track<00:08:25.260> it<00:08:25.290> what's<00:08:25.590> this<00:08:25.710> buffer 00:08:26.090 --> 00:08:26.100 align:start position:0% how long you track it what's this buffer 00:08:26.100 --> 00:08:27.800 align:start position:0% how long you track it what's this buffer and<00:08:26.430> is<00:08:26.850> that<00:08:27.030> configurable<00:08:27.450> and<00:08:27.600> how<00:08:27.660> does 00:08:27.800 --> 00:08:27.810 align:start position:0% and is that configurable and how does 00:08:27.810 --> 00:08:29.840 align:start position:0% and is that configurable and how does that<00:08:27.900> actually<00:08:28.020> work<00:08:28.230> so<00:08:28.740> so<00:08:29.370> to<00:08:29.430> summarize 00:08:29.840 --> 00:08:29.850 align:start position:0% that actually work so so to summarize 00:08:29.850 --> 00:08:32.300 align:start position:0% that actually work so so to summarize here<00:08:29.880> it<00:08:30.180> sounds<00:08:30.330> like<00:08:30.600> it's<00:08:31.050> like<00:08:31.590> volatility 00:08:32.300 --> 00:08:32.310 align:start position:0% here it sounds like it's like volatility 00:08:32.310 --> 00:08:34.909 align:start position:0% here it sounds like it's like volatility of<00:08:32.430> fees<00:08:32.669> is<00:08:33.060> the<00:08:33.380> biggest<00:08:34.380> challenge<00:08:34.590> here 00:08:34.909 --> 00:08:34.919 align:start position:0% of fees is the biggest challenge here 00:08:34.919 --> 00:08:36.529 align:start position:0% of fees is the biggest challenge here and<00:08:34.979> there's<00:08:35.130> no<00:08:35.310> good<00:08:35.789> solution<00:08:36.030> at<00:08:36.419> this 00:08:36.529 --> 00:08:36.539 align:start position:0% and there's no good solution at this 00:08:36.539 --> 00:08:37.630 align:start position:0% and there's no good solution at this point<00:08:36.719> is<00:08:36.810> that<00:08:36.960> the<00:08:37.110> is<00:08:37.289> that<00:08:37.320> the<00:08:37.440> deal 00:08:37.630 --> 00:08:37.640 align:start position:0% point is that the is that the deal 00:08:37.640 --> 00:08:40.190 align:start position:0% point is that the is that the deal there's<00:08:38.640> a<00:08:38.760> solution<00:08:39.330> it<00:08:39.479> is<00:08:39.510> a<00:08:39.660> challenging 00:08:40.190 --> 00:08:40.200 align:start position:0% there's a solution it is a challenging 00:08:40.200 --> 00:08:42.469 align:start position:0% there's a solution it is a challenging one<00:08:40.229> I<00:08:40.560> think<00:08:40.770> because<00:08:41.219> like<00:08:41.400> I've<00:08:42.090> been<00:08:42.270> said 00:08:42.469 --> 00:08:42.479 align:start position:0% one I think because like I've been said 00:08:42.479 --> 00:08:44.390 align:start position:0% one I think because like I've been said here<00:08:42.630> the<00:08:42.930> you<00:08:43.740> know<00:08:43.830> transaction<00:08:44.280> that's 00:08:44.390 --> 00:08:44.400 align:start position:0% here the you know transaction that's 00:08:44.400 --> 00:08:45.290 align:start position:0% here the you know transaction that's changing<00:08:44.730> and<00:08:44.850> stuff<00:08:45.000> it's<00:08:45.120> a<00:08:45.150> more 00:08:45.290 --> 00:08:45.300 align:start position:0% changing and stuff it's a more 00:08:45.300 --> 00:08:47.300 align:start position:0% changing and stuff it's a more complicated<00:08:45.600> thing<00:08:45.870> to<00:08:46.080> like<00:08:46.230> re<00:08:46.830> like<00:08:47.040> match 00:08:47.300 --> 00:08:47.310 align:start position:0% complicated thing to like re like match 00:08:47.310 --> 00:08:48.710 align:start position:0% complicated thing to like re like match things<00:08:47.610> up<00:08:47.790> if<00:08:47.940> you<00:08:48.060> you<00:08:48.240> know<00:08:48.330> have<00:08:48.360> sort<00:08:48.690> of 00:08:48.710 --> 00:08:48.720 align:start position:0% things up if you you know have sort of 00:08:48.720 --> 00:08:49.580 align:start position:0% things up if you you know have sort of two<00:08:48.930> pending<00:08:49.290> trends 00:08:49.580 --> 00:08:49.590 align:start position:0% two pending trends 00:08:49.590 --> 00:08:50.750 align:start position:0% two pending trends action<00:08:49.770> for<00:08:49.860> the<00:08:49.950> network<00:08:50.190> and<00:08:50.340> one<00:08:50.520> of<00:08:50.610> them 00:08:50.750 --> 00:08:50.760 align:start position:0% action for the network and one of them 00:08:50.760 --> 00:08:52.340 align:start position:0% action for the network and one of them will<00:08:50.910> confirm<00:08:51.270> and<00:08:51.630> generally<00:08:52.050> it<00:08:52.110> would<00:08:52.200> be 00:08:52.340 --> 00:08:52.350 align:start position:0% will confirm and generally it would be 00:08:52.350 --> 00:08:53.750 align:start position:0% will confirm and generally it would be the<00:08:52.440> higher<00:08:52.590> fee<00:08:52.830> one<00:08:52.980> but<00:08:53.250> like<00:08:53.370> I<00:08:53.490> think<00:08:53.670> in 00:08:53.750 --> 00:08:53.760 align:start position:0% the higher fee one but like I think in 00:08:53.760 --> 00:08:55.130 align:start position:0% the higher fee one but like I think in theory<00:08:53.970> like<00:08:54.210> the<00:08:54.330> lower<00:08:54.480> one<00:08:54.660> can<00:08:54.870> also 00:08:55.130 --> 00:08:55.140 align:start position:0% theory like the lower one can also 00:08:55.140 --> 00:08:56.930 align:start position:0% theory like the lower one can also confirm<00:08:55.590> so<00:08:56.160> now<00:08:56.430> you<00:08:56.490> have<00:08:56.610> to<00:08:56.700> have<00:08:56.790> these 00:08:56.930 --> 00:08:56.940 align:start position:0% confirm so now you have to have these 00:08:56.940 --> 00:08:58.430 align:start position:0% confirm so now you have to have these two<00:08:57.180> sort<00:08:57.450> of<00:08:57.480> states<00:08:57.750> and<00:08:57.990> like<00:08:58.080> which 00:08:58.430 --> 00:08:58.440 align:start position:0% two sort of states and like which 00:08:58.440 --> 00:09:00.410 align:start position:0% two sort of states and like which transaction<00:08:59.010> is<00:08:59.100> real<00:08:59.310> and<00:08:59.580> then<00:09:00.210> you<00:09:00.330> know 00:09:00.410 --> 00:09:00.420 align:start position:0% transaction is real and then you know 00:09:00.420 --> 00:09:01.880 align:start position:0% transaction is real and then you know one<00:09:00.600> of<00:09:00.630> them<00:09:00.840> will<00:09:01.020> confirm<00:09:01.350> and<00:09:01.680> so<00:09:01.740> it's 00:09:01.880 --> 00:09:01.890 align:start position:0% one of them will confirm and so it's 00:09:01.890 --> 00:09:03.380 align:start position:0% one of them will confirm and so it's just<00:09:01.950> more<00:09:02.340> complicated<00:09:02.550> problems 00:09:03.380 --> 00:09:03.390 align:start position:0% just more complicated problems 00:09:03.390 --> 00:09:05.690 align:start position:0% just more complicated problems employment<00:09:03.840> has<00:09:04.830> become<00:09:05.160> a<00:09:05.190> potential 00:09:05.690 --> 00:09:05.700 align:start position:0% employment has become a potential 00:09:05.700 --> 00:09:12.620 align:start position:0% employment has become a potential challenge<00:09:06.120> to<00:09:06.330> because<00:09:06.780> it's<00:09:07.080> even<00:09:09.410> it's<00:09:11.630> good 00:09:12.620 --> 00:09:12.630 align:start position:0% challenge to because it's even it's good 00:09:12.630 --> 00:09:15.020 align:start position:0% challenge to because it's even it's good potentially<00:09:13.140> ok<00:09:13.500> so<00:09:13.560> now<00:09:13.770> we<00:09:13.830> have<00:09:13.950> a<00:09:14.400> new<00:09:14.700> kind 00:09:15.020 --> 00:09:15.030 align:start position:0% potentially ok so now we have a new kind 00:09:15.030 --> 00:09:17.600 align:start position:0% potentially ok so now we have a new kind of<00:09:15.150> talks<00:09:15.330> on<00:09:15.420> this<00:09:15.540> bend<00:09:15.780> where<00:09:16.050> maybe<00:09:17.010> miners 00:09:17.600 --> 00:09:17.610 align:start position:0% of talks on this bend where maybe miners 00:09:17.610 --> 00:09:20.060 align:start position:0% of talks on this bend where maybe miners run<00:09:17.790> out<00:09:17.910> of<00:09:18.140> run<00:09:19.140> out<00:09:19.260> of<00:09:19.290> memory<00:09:19.530> space<00:09:19.740> when 00:09:20.060 --> 00:09:20.070 align:start position:0% run out of run out of memory space when 00:09:20.070 --> 00:09:21.230 align:start position:0% run out of run out of memory space when they're<00:09:20.190> waiting<00:09:20.400> for<00:09:20.700> all<00:09:20.790> these<00:09:20.940> pending 00:09:21.230 --> 00:09:21.240 align:start position:0% they're waiting for all these pending 00:09:21.240 --> 00:09:22.880 align:start position:0% they're waiting for all these pending transactions<00:09:21.810> maybe<00:09:22.110> but<00:09:22.500> if<00:09:22.620> if 00:09:22.880 --> 00:09:22.890 align:start position:0% transactions maybe but if if 00:09:22.890 --> 00:09:24.980 align:start position:0% transactions maybe but if if hypothetically<00:09:23.280> that<00:09:23.700> did<00:09:23.940> exist<00:09:24.240> if<00:09:24.600> it<00:09:24.840> was 00:09:24.980 --> 00:09:24.990 align:start position:0% hypothetically that did exist if it was 00:09:24.990 --> 00:09:27.800 align:start position:0% hypothetically that did exist if it was implemented<00:09:25.380> poorly<00:09:25.980> it<00:09:26.790> could<00:09:26.850> lead<00:09:27.480> to<00:09:27.510> this 00:09:27.800 --> 00:09:27.810 align:start position:0% implemented poorly it could lead to this 00:09:27.810 --> 00:09:30.560 align:start position:0% implemented poorly it could lead to this new<00:09:28.140> design<00:09:28.740> pattern<00:09:29.160> where<00:09:29.570> everyone's 00:09:30.560 --> 00:09:30.570 align:start position:0% new design pattern where everyone's 00:09:30.570 --> 00:09:34.250 align:start position:0% new design pattern where everyone's putting<00:09:30.840> no<00:09:32.000> 1g<00:09:33.000> way<00:09:33.150> or<00:09:33.390> whatever<00:09:33.690> it<00:09:33.840> be<00:09:33.990> as 00:09:34.250 --> 00:09:34.260 align:start position:0% putting no 1g way or whatever it be as 00:09:34.260 --> 00:09:36.950 align:start position:0% putting no 1g way or whatever it be as all<00:09:35.070> of<00:09:35.430> their<00:09:35.520> transaction<00:09:36.120> prices<00:09:36.330> and<00:09:36.720> then 00:09:36.950 --> 00:09:36.960 align:start position:0% all of their transaction prices and then 00:09:36.960 --> 00:09:39.860 align:start position:0% all of their transaction prices and then if<00:09:37.350> it<00:09:37.590> doesn't<00:09:38.040> clear<00:09:38.280> within<00:09:38.550> some<00:09:38.940> X<00:09:39.270> time 00:09:39.860 --> 00:09:39.870 align:start position:0% if it doesn't clear within some X time 00:09:39.870 --> 00:09:42.170 align:start position:0% if it doesn't clear within some X time period<00:09:40.290> then<00:09:40.770> they<00:09:41.040> put<00:09:41.370> out<00:09:41.490> a<00:09:41.520> transaction 00:09:42.170 --> 00:09:42.180 align:start position:0% period then they put out a transaction 00:09:42.180 --> 00:09:43.610 align:start position:0% period then they put out a transaction to<00:09:42.270> kind<00:09:42.450> of<00:09:42.510> clear<00:09:42.780> those<00:09:42.960> out<00:09:43.110> so<00:09:43.170> we<00:09:43.470> have 00:09:43.610 --> 00:09:43.620 align:start position:0% to kind of clear those out so we have 00:09:43.620 --> 00:09:46.400 align:start position:0% to kind of clear those out so we have this<00:09:43.770> now<00:09:44.030> almost<00:09:45.030> waves<00:09:45.420> of<00:09:45.750> transactions 00:09:46.400 --> 00:09:46.410 align:start position:0% this now almost waves of transactions 00:09:46.410 --> 00:09:47.900 align:start position:0% this now almost waves of transactions going<00:09:46.530> through<00:09:46.950> just<00:09:47.130> because<00:09:47.430> people<00:09:47.460> want 00:09:47.900 --> 00:09:47.910 align:start position:0% going through just because people want 00:09:47.910 --> 00:09:51.170 align:start position:0% going through just because people want to<00:09:48.000> pay<00:09:48.120> lower<00:09:48.540> their<00:09:48.750> costs<00:09:49.080> right<00:09:50.120> it's<00:09:51.120> a 00:09:51.170 --> 00:09:51.180 align:start position:0% to pay lower their costs right it's a 00:09:51.180 --> 00:09:52.600 align:start position:0% to pay lower their costs right it's a tricky<00:09:51.960> situation 00:09:52.600 --> 00:09:52.610 align:start position:0% tricky situation 00:09:52.610 --> 00:09:56.120 align:start position:0% tricky situation all<00:09:53.610> right<00:09:53.820> ok<00:09:54.150> well<00:09:54.390> it's<00:09:54.870> it's<00:09:55.140> so<00:09:55.770> all<00:09:55.980> three 00:09:56.120 --> 00:09:56.130 align:start position:0% all right ok well it's it's so all three 00:09:56.130 --> 00:09:59.480 align:start position:0% all right ok well it's it's so all three of<00:09:56.220> you<00:09:56.310> seem<00:09:56.460> to<00:09:56.550> have<00:09:56.640> consensus<00:09:57.150> yeah<00:09:58.490> one 00:09:59.480 --> 00:09:59.490 align:start position:0% of you seem to have consensus yeah one 00:09:59.490 --> 00:10:00.680 align:start position:0% of you seem to have consensus yeah one of<00:09:59.520> the<00:09:59.730> things<00:09:59.940> right<00:10:00.090> I<00:10:00.150> think<00:10:00.240> another<00:10:00.510> one 00:10:00.680 --> 00:10:00.690 align:start position:0% of the things right I think another one 00:10:00.690 --> 00:10:02.120 align:start position:0% of the things right I think another one that<00:10:00.900> it's<00:10:01.110> not<00:10:01.290> just<00:10:01.500> us<00:10:01.680> but<00:10:01.860> and<00:10:02.040> we 00:10:02.120 --> 00:10:02.130 align:start position:0% that it's not just us but and we 00:10:02.130 --> 00:10:03.650 align:start position:0% that it's not just us but and we definitely<00:10:02.280> experience<00:10:02.880> this<00:10:03.000> is<00:10:03.450> just 00:10:03.650 --> 00:10:03.660 align:start position:0% definitely experience this is just 00:10:03.660 --> 00:10:05.420 align:start position:0% definitely experience this is just running<00:10:03.870> notes<00:10:04.110> very<00:10:04.380> running<00:10:04.770> nose<00:10:05.070> keeping 00:10:05.420 --> 00:10:05.430 align:start position:0% running notes very running nose keeping 00:10:05.430 --> 00:10:07.310 align:start position:0% running notes very running nose keeping them<00:10:05.520> up-to-date<00:10:05.640> on<00:10:06.180> the<00:10:06.390> size<00:10:06.600> of<00:10:06.990> the 00:10:07.310 --> 00:10:07.320 align:start position:0% them up-to-date on the size of the 00:10:07.320 --> 00:10:09.110 align:start position:0% them up-to-date on the size of the backups<00:10:07.680> and<00:10:07.800> stuff<00:10:07.980> in<00:10:08.370> particular<00:10:08.880> these 00:10:09.110 --> 00:10:09.120 align:start position:0% backups and stuff in particular these 00:10:09.120 --> 00:10:10.790 align:start position:0% backups and stuff in particular these sort<00:10:09.360> of<00:10:09.390> like<00:10:09.540> archive<00:10:10.020> state<00:10:10.290> notes<00:10:10.500> that<00:10:10.710> in 00:10:10.790 --> 00:10:10.800 align:start position:0% sort of like archive state notes that in 00:10:10.800 --> 00:10:13.280 align:start position:0% sort of like archive state notes that in a<00:10:10.890> store<00:10:11.190> like<00:10:11.370> the<00:10:11.520> full<00:10:11.730> history<00:10:12.180> I<00:10:12.330> think 00:10:13.280 --> 00:10:13.290 align:start position:0% a store like the full history I think 00:10:13.290 --> 00:10:15.620 align:start position:0% a store like the full history I think offeree<00:10:14.040> of<00:10:14.640> you<00:10:14.820> know<00:10:14.910> parity<00:10:15.210> just<00:10:15.390> released 00:10:15.620 --> 00:10:15.630 align:start position:0% offeree of you know parity just released 00:10:15.630 --> 00:10:17.180 align:start position:0% offeree of you know parity just released a<00:10:15.690> website<00:10:16.080> about<00:10:16.470> like<00:10:16.650> that<00:10:16.800> constantly 00:10:17.180 --> 00:10:17.190 align:start position:0% a website about like that constantly 00:10:17.190 --> 00:10:18.980 align:start position:0% a website about like that constantly tracks<00:10:17.430> the<00:10:17.550> size<00:10:17.730> and<00:10:18.330> so<00:10:18.510> if<00:10:18.570> you<00:10:18.660> run<00:10:18.780> like 00:10:18.980 --> 00:10:18.990 align:start position:0% tracks the size and so if you run like 00:10:18.990 --> 00:10:20.540 align:start position:0% tracks the size and so if you run like parity<00:10:19.500> you<00:10:19.530> can<00:10:19.740> get<00:10:19.890> it<00:10:19.980> to<00:10:20.070> like<00:10:20.190> 200 00:10:20.540 --> 00:10:20.550 align:start position:0% parity you can get it to like 200 00:10:20.550 --> 00:10:22.520 align:start position:0% parity you can get it to like 200 something<00:10:20.670> gigabytes<00:10:21.270> but<00:10:22.200> you<00:10:22.290> don't<00:10:22.440> have 00:10:22.520 --> 00:10:22.530 align:start position:0% something gigabytes but you don't have 00:10:22.530 --> 00:10:23.630 align:start position:0% something gigabytes but you don't have this<00:10:22.620> sort<00:10:22.740> of<00:10:22.830> full<00:10:23.010> history<00:10:23.250> one<00:10:23.430> and<00:10:23.550> that 00:10:23.630 --> 00:10:23.640 align:start position:0% this sort of full history one and that 00:10:23.640 --> 00:10:24.830 align:start position:0% this sort of full history one and that one<00:10:23.760> tends<00:10:24.000> to<00:10:24.120> be<00:10:24.180> I<00:10:24.240> think<00:10:24.300> around<00:10:24.630> these 00:10:24.830 --> 00:10:24.840 align:start position:0% one tends to be I think around these 00:10:24.840 --> 00:10:27.950 align:start position:0% one tends to be I think around these days<00:10:24.960> 1.8<00:10:25.500> terabytes<00:10:25.950> or<00:10:26.070> something<00:10:26.510> and<00:10:27.510> so 00:10:27.950 --> 00:10:27.960 align:start position:0% days 1.8 terabytes or something and so 00:10:27.960 --> 00:10:29.030 align:start position:0% days 1.8 terabytes or something and so just<00:10:28.110> the<00:10:28.200> size<00:10:28.440> is<00:10:28.680> the<00:10:28.770> thing<00:10:28.920> I'm<00:10:29.010> just 00:10:29.030 --> 00:10:29.040 align:start position:0% just the size is the thing I'm just 00:10:29.040 --> 00:10:30.440 align:start position:0% just the size is the thing I'm just transferring<00:10:29.550> that<00:10:29.670> over<00:10:29.730> the<00:10:30.000> internet<00:10:30.300> when 00:10:30.440 --> 00:10:30.450 align:start position:0% transferring that over the internet when 00:10:30.450 --> 00:10:31.550 align:start position:0% transferring that over the internet when you<00:10:30.540> need<00:10:30.690> to<00:10:30.720> like<00:10:30.900> to<00:10:30.990> spin<00:10:31.140> up<00:10:31.230> a<00:10:31.320> new<00:10:31.440> one 00:10:31.550 --> 00:10:31.560 align:start position:0% you need to like to spin up a new one 00:10:31.560 --> 00:10:32.990 align:start position:0% you need to like to spin up a new one just<00:10:31.620> takes<00:10:31.980> a<00:10:32.070> lot<00:10:32.160> of<00:10:32.310> time<00:10:32.460> I<00:10:32.670> think<00:10:32.700> ours 00:10:32.990 --> 00:10:33.000 align:start position:0% just takes a lot of time I think ours 00:10:33.000 --> 00:10:34.460 align:start position:0% just takes a lot of time I think ours are<00:10:33.510> ones<00:10:33.810> when<00:10:33.990> you<00:10:34.020> spend<00:10:34.200> them<00:10:34.290> off<00:10:34.350> for 00:10:34.460 --> 00:10:34.470 align:start position:0% are ones when you spend them off for 00:10:34.470 --> 00:10:36.110 align:start position:0% are ones when you spend them off for like<00:10:34.560> three<00:10:34.830> four<00:10:35.100> hours<00:10:35.130> right<00:10:35.550> now<00:10:35.580> to<00:10:35.760> sort 00:10:36.110 --> 00:10:36.120 align:start position:0% like three four hours right now to sort 00:10:36.120 --> 00:10:37.550 align:start position:0% like three four hours right now to sort of<00:10:36.180> do<00:10:36.630> that<00:10:36.780> we've<00:10:36.900> got<00:10:37.020> things<00:10:37.170> to<00:10:37.350> get<00:10:37.440> them 00:10:37.550 --> 00:10:37.560 align:start position:0% of do that we've got things to get them 00:10:37.560 --> 00:10:40.220 align:start position:0% of do that we've got things to get them faster<00:10:37.950> but<00:10:38.190> a<00:10:38.340> fresh<00:10:38.910> thing<00:10:39.180> is<00:10:39.330> like<00:10:39.570> I<00:10:39.870> think 00:10:40.220 --> 00:10:40.230 align:start position:0% faster but a fresh thing is like I think 00:10:40.230 --> 00:10:43.960 align:start position:0% faster but a fresh thing is like I think the<00:10:40.380> last<00:10:40.530> one<00:10:40.650> I<00:10:40.800> did<00:10:42.470> something<00:10:43.470> like<00:10:43.500> that 00:10:43.960 --> 00:10:43.970 align:start position:0% the last one I did something like that 00:10:43.970 --> 00:10:46.460 align:start position:0% the last one I did something like that at<00:10:44.970> which<00:10:45.150> which<00:10:45.390> kind<00:10:45.630> of<00:10:45.660> flows<00:10:45.960> nicely<00:10:46.290> into 00:10:46.460 --> 00:10:46.470 align:start position:0% at which which kind of flows nicely into 00:10:46.470 --> 00:10:49.880 align:start position:0% at which which kind of flows nicely into the<00:10:46.650> next<00:10:46.680> question<00:10:47.310> which<00:10:48.120> is<00:10:48.320> do<00:10:49.320> you<00:10:49.440> do<00:10:49.800> you 00:10:49.880 --> 00:10:49.890 align:start position:0% the next question which is do you do you 00:10:49.890 --> 00:10:51.140 align:start position:0% the next question which is do you do you think<00:10:50.100> that<00:10:50.220> integrating<00:10:50.700> with<00:10:50.790> the<00:10:50.820> theorem 00:10:51.140 --> 00:10:51.150 align:start position:0% think that integrating with the theorem 00:10:51.150 --> 00:10:53.570 align:start position:0% think that integrating with the theorem is<00:10:51.240> getting<00:10:51.480> harder<00:10:52.140> at<00:10:52.320> that<00:10:52.500> low<00:10:52.950> level<00:10:53.280> that 00:10:53.570 --> 00:10:53.580 align:start position:0% is getting harder at that low level that 00:10:53.580 --> 00:10:56.330 align:start position:0% is getting harder at that low level that we're<00:10:53.670> talking<00:10:53.760> about<00:10:53.940> here<00:10:54.090> and<00:10:54.800> if<00:10:55.800> so<00:10:56.160> do 00:10:56.330 --> 00:10:56.340 align:start position:0% we're talking about here and if so do 00:10:56.340 --> 00:10:57.380 align:start position:0% we're talking about here and if so do you<00:10:56.430> think<00:10:56.640> that<00:10:56.760> we're<00:10:56.880> at<00:10:56.970> some<00:10:57.150> sort<00:10:57.330> of 00:10:57.380 --> 00:10:57.390 align:start position:0% you think that we're at some sort of 00:10:57.390 --> 00:11:00.290 align:start position:0% you think that we're at some sort of critical<00:10:57.630> juncture<00:10:58.080> with<00:10:58.230> respect<00:10:58.620> to<00:10:58.710> that 00:11:00.290 --> 00:11:00.300 align:start position:0% critical juncture with respect to that 00:11:00.300 --> 00:11:04.069 align:start position:0% critical juncture with respect to that I<00:11:00.329> think<00:11:01.230> for<00:11:01.879> for<00:11:02.879> instance<00:11:03.629> I<00:11:03.749> mean<00:11:03.929> the 00:11:04.069 --> 00:11:04.079 align:start position:0% I think for for instance I mean the 00:11:04.079 --> 00:11:05.840 align:start position:0% I think for for instance I mean the blockchain<00:11:04.860> size<00:11:05.309> keeps<00:11:05.670> increasing 00:11:05.840 --> 00:11:05.850 align:start position:0% blockchain size keeps increasing 00:11:05.850 --> 00:11:07.819 align:start position:0% blockchain size keeps increasing everyday<00:11:06.420> so<00:11:06.480> for<00:11:07.050> that<00:11:07.170> purpose<00:11:07.410> it<00:11:07.769> is 00:11:07.819 --> 00:11:07.829 align:start position:0% everyday so for that purpose it is 00:11:07.829 --> 00:11:10.850 align:start position:0% everyday so for that purpose it is getting<00:11:08.160> harder<00:11:08.550> in<00:11:08.910> terms<00:11:09.420> of<00:11:09.860> resyncing 00:11:10.850 --> 00:11:10.860 align:start position:0% getting harder in terms of resyncing 00:11:10.860 --> 00:11:12.769 align:start position:0% getting harder in terms of resyncing nodes<00:11:11.339> or<00:11:11.639> syncing<00:11:12.029> a<00:11:12.059> new<00:11:12.209> node<00:11:12.420> if<00:11:12.600> one 00:11:12.769 --> 00:11:12.779 align:start position:0% nodes or syncing a new node if one 00:11:12.779 --> 00:11:14.359 align:start position:0% nodes or syncing a new node if one crashes<00:11:12.990> or<00:11:13.470> something<00:11:13.709> like<00:11:13.829> that<00:11:14.009> you<00:11:14.220> lose 00:11:14.359 --> 00:11:14.369 align:start position:0% crashes or something like that you lose 00:11:14.369 --> 00:11:17.239 align:start position:0% crashes or something like that you lose a<00:11:14.399> database<00:11:15.259> in<00:11:16.259> a<00:11:16.619> lot<00:11:16.769> of<00:11:16.889> ways<00:11:17.040> though 00:11:17.239 --> 00:11:17.249 align:start position:0% a database in a lot of ways though 00:11:17.249 --> 00:11:19.549 align:start position:0% a database in a lot of ways though there's<00:11:17.490> a<00:11:17.579> lot<00:11:17.699> of<00:11:17.850> tooling<00:11:18.660> that<00:11:18.869> makes<00:11:19.319> it<00:11:19.529> a 00:11:19.549 --> 00:11:19.559 align:start position:0% there's a lot of tooling that makes it a 00:11:19.559 --> 00:11:21.290 align:start position:0% there's a lot of tooling that makes it a lot<00:11:19.800> easier<00:11:20.160> to<00:11:20.220> integrate<00:11:20.759> things<00:11:20.910> so<00:11:21.119> things 00:11:21.290 --> 00:11:21.300 align:start position:0% lot easier to integrate things so things 00:11:21.300 --> 00:11:22.910 align:start position:0% lot easier to integrate things so things like<00:11:21.480> truffle<00:11:21.959> or<00:11:21.990> ganache<00:11:22.350> are<00:11:22.589> becoming 00:11:22.910 --> 00:11:22.920 align:start position:0% like truffle or ganache are becoming 00:11:22.920 --> 00:11:24.499 align:start position:0% like truffle or ganache are becoming really<00:11:23.309> really<00:11:23.610> easy<00:11:23.759> to<00:11:23.819> use<00:11:24.059> and<00:11:24.300> there's<00:11:24.420> a 00:11:24.499 --> 00:11:24.509 align:start position:0% really really easy to use and there's a 00:11:24.509 --> 00:11:26.569 align:start position:0% really really easy to use and there's a great<00:11:24.899> user<00:11:25.589> experience<00:11:26.100> around<00:11:26.189> dev 00:11:26.569 --> 00:11:26.579 align:start position:0% great user experience around dev 00:11:26.579 --> 00:11:28.730 align:start position:0% great user experience around dev workflow<00:11:26.970> now<00:11:27.179> for<00:11:27.420> even<00:11:28.199> just<00:11:28.230> for<00:11:28.439> local 00:11:28.730 --> 00:11:28.740 align:start position:0% workflow now for even just for local 00:11:28.740 --> 00:11:31.299 align:start position:0% workflow now for even just for local development<00:11:28.829> but<00:11:29.249> also<00:11:29.309> for<00:11:29.730> production<00:11:30.720> and 00:11:31.299 --> 00:11:31.309 align:start position:0% development but also for production and 00:11:31.309 --> 00:11:34.309 align:start position:0% development but also for production and it's<00:11:32.309> it's<00:11:32.910> this<00:11:33.149> interesting<00:11:34.019> kind<00:11:34.230> of 00:11:34.309 --> 00:11:34.319 align:start position:0% it's it's this interesting kind of 00:11:34.319 --> 00:11:36.439 align:start position:0% it's it's this interesting kind of duality<00:11:34.860> so<00:11:35.429> some<00:11:35.610> parts<00:11:35.850> are<00:11:35.970> getting<00:11:36.149> harder 00:11:36.439 --> 00:11:36.449 align:start position:0% duality so some parts are getting harder 00:11:36.449 --> 00:11:38.049 align:start position:0% duality so some parts are getting harder in<00:11:36.629> my<00:11:36.779> opinion<00:11:37.199> in<00:11:37.259> some<00:11:37.410> parts<00:11:37.649> of<00:11:37.709> getting 00:11:38.049 --> 00:11:38.059 align:start position:0% in my opinion in some parts of getting 00:11:38.059 --> 00:11:42.109 align:start position:0% in my opinion in some parts of getting easier<00:11:39.059> potentially<00:11:39.720> I<00:11:39.959> think<00:11:40.679> to<00:11:41.059> go<00:11:42.059> to 00:11:42.109 --> 00:11:42.119 align:start position:0% easier potentially I think to go to 00:11:42.119 --> 00:11:45.019 align:start position:0% easier potentially I think to go to production<00:11:42.809> with<00:11:43.019> a<00:11:43.050> theorem<00:11:43.410> is<00:11:44.369> getting<00:11:44.999> a 00:11:45.019 --> 00:11:45.029 align:start position:0% production with a theorem is getting a 00:11:45.029 --> 00:11:47.389 align:start position:0% production with a theorem is getting a little<00:11:45.179> bit<00:11:45.360> harder<00:11:45.660> I<00:11:46.259> really<00:11:47.009> like<00:11:47.189> the 00:11:47.389 --> 00:11:47.399 align:start position:0% little bit harder I really like the 00:11:47.399 --> 00:11:50.419 align:start position:0% little bit harder I really like the developer<00:11:47.999> on-ramp<00:11:48.329> so<00:11:49.230> you<00:11:50.189> know<00:11:50.279> the 00:11:50.419 --> 00:11:50.429 align:start position:0% developer on-ramp so you know the 00:11:50.429 --> 00:11:53.239 align:start position:0% developer on-ramp so you know the developer<00:11:51.420> tooling<00:11:51.809> and<00:11:52.139> all<00:11:52.230> the<00:11:52.379> you<00:11:53.129> know 00:11:53.239 --> 00:11:53.249 align:start position:0% developer tooling and all the you know 00:11:53.249 --> 00:11:55.939 align:start position:0% developer tooling and all the you know building<00:11:53.639> on<00:11:53.759> tools<00:11:54.689> are<00:11:55.379> getting<00:11:55.529> better<00:11:55.679> and 00:11:55.939 --> 00:11:55.949 align:start position:0% building on tools are getting better and 00:11:55.949 --> 00:11:58.970 align:start position:0% building on tools are getting better and better<00:11:56.009> welcoming<00:11:56.699> new<00:11:57.240> new<00:11:57.660> new<00:11:58.019> developers 00:11:58.970 --> 00:11:58.980 align:start position:0% better welcoming new new new developers 00:11:58.980 --> 00:11:59.840 align:start position:0% better welcoming new new new developers and<00:11:59.100> that's<00:11:59.160> why<00:11:59.339> we<00:11:59.459> have<00:11:59.550> so<00:11:59.790> many 00:11:59.840 --> 00:11:59.850 align:start position:0% and that's why we have so many 00:11:59.850 --> 00:12:02.660 align:start position:0% and that's why we have so many developers<00:12:00.240> at<00:12:00.329> this<00:12:00.420> conference<00:12:00.600> I<00:12:01.670> think 00:12:02.660 --> 00:12:02.670 align:start position:0% developers at this conference I think 00:12:02.670 --> 00:12:06.009 align:start position:0% developers at this conference I think that<00:12:02.910> so<00:12:03.240> far<00:12:03.420> is<00:12:03.540> running<00:12:03.809> a<00:12:03.869> node<00:12:04.610> when<00:12:05.610> I 00:12:06.009 --> 00:12:06.019 align:start position:0% that so far is running a node when I 00:12:06.019 --> 00:12:10.489 align:start position:0% that so far is running a node when I last<00:12:07.019> fired<00:12:07.379> up<00:12:08.389> for<00:12:09.389> myself<00:12:09.779> you<00:12:10.019> know<00:12:10.139> we<00:12:10.350> had 00:12:10.489 --> 00:12:10.499 align:start position:0% last fired up for myself you know we had 00:12:10.499 --> 00:12:11.889 align:start position:0% last fired up for myself you know we had lots<00:12:10.679> of<00:12:10.769> nodes<00:12:11.009> in<00:12:11.129> production<00:12:11.519> but 00:12:11.889 --> 00:12:11.899 align:start position:0% lots of nodes in production but 00:12:11.899 --> 00:12:14.559 align:start position:0% lots of nodes in production but sometimes<00:12:12.899> you<00:12:13.019> want<00:12:13.170> to<00:12:13.230> hack<00:12:13.350> yourself<00:12:13.740> I 00:12:14.559 --> 00:12:14.569 align:start position:0% sometimes you want to hack yourself I 00:12:14.569 --> 00:12:18.169 align:start position:0% sometimes you want to hack yourself I think<00:12:15.569> death<00:12:16.100> if<00:12:17.100> you<00:12:17.160> you<00:12:17.639> know<00:12:17.759> running<00:12:17.999> in 00:12:18.169 --> 00:12:18.179 align:start position:0% think death if you you know running in 00:12:18.179 --> 00:12:20.329 align:start position:0% think death if you you know running in the<00:12:18.299> fast<00:12:18.869> fast<00:12:19.410> mode<00:12:19.679> it's<00:12:19.829> actually<00:12:20.069> not<00:12:20.189> too 00:12:20.329 --> 00:12:20.339 align:start position:0% the fast fast mode it's actually not too 00:12:20.339 --> 00:12:25.129 align:start position:0% the fast fast mode it's actually not too bad<00:12:20.660> and<00:12:21.660> I<00:12:22.910> think<00:12:23.910> it's<00:12:24.269> right<00:12:24.689> now<00:12:24.869> it's<00:12:24.899> not 00:12:25.129 --> 00:12:25.139 align:start position:0% bad and I think it's right now it's not 00:12:25.139 --> 00:12:26.960 align:start position:0% bad and I think it's right now it's not a<00:12:25.199> critical<00:12:25.529> juncture<00:12:25.649> juncture<00:12:26.249> because<00:12:26.670> at 00:12:26.960 --> 00:12:26.970 align:start position:0% a critical juncture juncture because at 00:12:26.970 --> 00:12:28.939 align:start position:0% a critical juncture juncture because at this<00:12:27.059> point<00:12:27.360> the<00:12:27.660> the<00:12:28.049> block<00:12:28.259> processing<00:12:28.740> time 00:12:28.939 --> 00:12:28.949 align:start position:0% this point the the block processing time 00:12:28.949 --> 00:12:31.869 align:start position:0% this point the the block processing time is<00:12:29.189> still<00:12:29.790> less<00:12:30.029> than<00:12:30.059> the<00:12:30.299> time<00:12:31.079> it<00:12:31.230> takes<00:12:31.350> to 00:12:31.869 --> 00:12:31.879 align:start position:0% is still less than the time it takes to 00:12:31.879 --> 00:12:35.299 align:start position:0% is still less than the time it takes to propagate<00:12:33.230> and<00:12:34.230> it's<00:12:34.499> time<00:12:34.619> that<00:12:34.649> one<00:12:34.980> you 00:12:35.299 --> 00:12:35.309 align:start position:0% propagate and it's time that one you 00:12:35.309 --> 00:12:38.749 align:start position:0% propagate and it's time that one you know<00:12:35.339> get<00:12:35.579> stopped<00:12:35.790> and<00:12:37.100> that<00:12:38.100> you<00:12:38.549> know<00:12:38.670> we 00:12:38.749 --> 00:12:38.759 align:start position:0% know get stopped and that you know we 00:12:38.759 --> 00:12:40.220 align:start position:0% know get stopped and that you know we can<00:12:38.879> talk<00:12:38.970> a<00:12:39.029> bit<00:12:39.179> about<00:12:39.209> more<00:12:39.509> about<00:12:39.869> that 00:12:40.220 --> 00:12:40.230 align:start position:0% can talk a bit about more about that 00:12:40.230 --> 00:12:41.629 align:start position:0% can talk a bit about more about that like<00:12:40.529> that<00:12:40.709> was<00:12:40.860> different<00:12:41.040> earlier<00:12:41.519> this 00:12:41.629 --> 00:12:41.639 align:start position:0% like that was different earlier this 00:12:41.639 --> 00:12:44.150 align:start position:0% like that was different earlier this year<00:12:41.869> but<00:12:42.869> I<00:12:42.929> think<00:12:42.990> that<00:12:43.350> right<00:12:43.799> now<00:12:43.980> it's 00:12:44.150 --> 00:12:44.160 align:start position:0% year but I think that right now it's 00:12:44.160 --> 00:12:46.369 align:start position:0% year but I think that right now it's quick<00:12:44.579> where<00:12:45.269> you<00:12:45.420> can<00:12:45.569> fast<00:12:45.899> think<00:12:46.139> all<00:12:46.290> the 00:12:46.369 --> 00:12:46.379 align:start position:0% quick where you can fast think all the 00:12:46.379 --> 00:12:48.679 align:start position:0% quick where you can fast think all the way<00:12:46.499> to<00:12:46.559> the<00:12:46.709> hit<00:12:46.889> of<00:12:47.309> the<00:12:47.459> chain<00:12:47.670> and<00:12:47.850> then<00:12:48.449> you 00:12:48.679 --> 00:12:48.689 align:start position:0% way to the hit of the chain and then you 00:12:48.689 --> 00:12:50.299 align:start position:0% way to the hit of the chain and then you can<00:12:48.869> just<00:12:49.079> you<00:12:49.499> know<00:12:49.529> your<00:12:50.009> blocks<00:12:50.220> are 00:12:50.299 --> 00:12:50.309 align:start position:0% can just you know your blocks are 00:12:50.309 --> 00:12:51.710 align:start position:0% can just you know your blocks are getting<00:12:50.519> pushed<00:12:50.939> that's<00:12:51.119> quick<00:12:51.269> enough<00:12:51.480> with 00:12:51.710 --> 00:12:51.720 align:start position:0% getting pushed that's quick enough with 00:12:51.720 --> 00:12:53.049 align:start position:0% getting pushed that's quick enough with you<00:12:52.049> know<00:12:52.139> modern<00:12:52.350> hardware<00:12:52.649> it's<00:12:52.860> not 00:12:53.049 --> 00:12:53.059 align:start position:0% you know modern hardware it's not 00:12:53.059 --> 00:12:55.579 align:start position:0% you know modern hardware it's not totally<00:12:54.059> a<00:12:54.089> problem<00:12:54.509> and<00:12:54.629> of<00:12:54.689> course<00:12:54.929> you<00:12:55.470> know 00:12:55.579 --> 00:12:55.589 align:start position:0% totally a problem and of course you know 00:12:55.589 --> 00:12:58.939 align:start position:0% totally a problem and of course you know you<00:12:55.649> really<00:12:55.860> want<00:12:56.100> to<00:12:56.189> be<00:12:56.279> running<00:12:56.519> a<00:12:57.470> node<00:12:58.470> in 00:12:58.939 --> 00:12:58.949 align:start position:0% you really want to be running a node in 00:12:58.949 --> 00:13:01.069 align:start position:0% you really want to be running a node in in<00:12:59.549> production<00:13:00.029> and<00:13:00.209> running<00:13:00.689> several<00:13:00.990> of 00:13:01.069 --> 00:13:01.079 align:start position:0% in production and running several of 00:13:01.079 --> 00:13:02.840 align:start position:0% in production and running several of them<00:13:01.230> so<00:13:01.350> that's<00:13:01.439> a<00:13:01.589> different<00:13:01.829> challenge<00:13:01.980> but 00:13:02.840 --> 00:13:02.850 align:start position:0% them so that's a different challenge but 00:13:02.850 --> 00:13:04.910 align:start position:0% them so that's a different challenge but to<00:13:03.480> get<00:13:03.629> on<00:13:03.839> board<00:13:04.019> I<00:13:04.350> think<00:13:04.470> it's<00:13:04.799> actually 00:13:04.910 --> 00:13:04.920 align:start position:0% to get on board I think it's actually 00:13:04.920 --> 00:13:08.090 align:start position:0% to get on board I think it's actually still<00:13:05.759> pretty<00:13:05.819> easy<00:13:06.319> either<00:13:07.319> like<00:13:07.529> onboarding 00:13:08.090 --> 00:13:08.100 align:start position:0% still pretty easy either like onboarding 00:13:08.100 --> 00:13:10.340 align:start position:0% still pretty easy either like onboarding definitely<00:13:08.579> doesn't<00:13:08.959> having<00:13:09.959> a<00:13:10.019> lot<00:13:10.169> there's 00:13:10.340 --> 00:13:10.350 align:start position:0% definitely doesn't having a lot there's 00:13:10.350 --> 00:13:11.659 align:start position:0% definitely doesn't having a lot there's a<00:13:10.379> lot<00:13:10.499> of<00:13:10.589> really<00:13:10.769> cool<00:13:10.889> stuff<00:13:11.040> there<00:13:11.339> to<00:13:11.549> like 00:13:11.659 --> 00:13:11.669 align:start position:0% a lot of really cool stuff there to like 00:13:11.669 --> 00:13:13.319 align:start position:0% a lot of really cool stuff there to like get<00:13:11.910> up<00:13:12.029> to<00:13:12.149> speed<00:13:12.389> and<00:13:12.720> like<00:13:12.990> start 00:13:13.319 --> 00:13:13.329 align:start position:0% get up to speed and like start 00:13:13.329 --> 00:13:15.059 align:start position:0% get up to speed and like start able<00:13:13.540> to<00:13:13.600> do<00:13:13.720> things<00:13:13.959> but<00:13:14.499> like<00:13:14.649> you<00:13:14.739> said<00:13:14.889> sort 00:13:15.059 --> 00:13:15.069 align:start position:0% able to do things but like you said sort 00:13:15.069 --> 00:13:16.590 align:start position:0% able to do things but like you said sort of<00:13:15.189> at<00:13:15.279> this<00:13:15.429> sort<00:13:15.670> of<00:13:15.759> like<00:13:15.879> scale<00:13:16.269> thing<00:13:16.509> or 00:13:16.590 --> 00:13:16.600 align:start position:0% of at this sort of like scale thing or 00:13:16.600 --> 00:13:18.030 align:start position:0% of at this sort of like scale thing or when<00:13:16.689> you're<00:13:16.809> running<00:13:16.899> like<00:13:17.110> businesses<00:13:17.769> that 00:13:18.030 --> 00:13:18.040 align:start position:0% when you're running like businesses that 00:13:18.040 --> 00:13:19.259 align:start position:0% when you're running like businesses that are<00:13:18.309> worth<00:13:18.429> a<00:13:18.489> lot<00:13:18.549> of<00:13:18.610> money<00:13:18.699> and<00:13:19.029> a<00:13:19.119> lot<00:13:19.209> of 00:13:19.259 --> 00:13:19.269 align:start position:0% are worth a lot of money and a lot of 00:13:19.269 --> 00:13:21.090 align:start position:0% are worth a lot of money and a lot of money's<00:13:19.540> moving<00:13:19.809> through<00:13:20.049> you<00:13:20.589> also<00:13:20.739> want<00:13:21.009> to 00:13:21.090 --> 00:13:21.100 align:start position:0% money's moving through you also want to 00:13:21.100 --> 00:13:22.199 align:start position:0% money's moving through you also want to like<00:13:21.220> have<00:13:21.429> sort<00:13:21.790> of<00:13:21.850> the<00:13:21.970> full<00:13:22.119> history 00:13:22.199 --> 00:13:22.209 align:start position:0% like have sort of the full history 00:13:22.209 --> 00:13:24.179 align:start position:0% like have sort of the full history yourself<00:13:22.749> and<00:13:22.989> always<00:13:23.230> have<00:13:23.410> a<00:13:23.439> copy<00:13:23.739> of<00:13:23.980> that 00:13:24.179 --> 00:13:24.189 align:start position:0% yourself and always have a copy of that 00:13:24.189 --> 00:13:26.939 align:start position:0% yourself and always have a copy of that and<00:13:24.509> so<00:13:25.509> you<00:13:25.569> this<00:13:26.199> kind<00:13:26.410> of<00:13:26.439> initial<00:13:26.739> sync 00:13:26.939 --> 00:13:26.949 align:start position:0% and so you this kind of initial sync 00:13:26.949 --> 00:13:28.739 align:start position:0% and so you this kind of initial sync time<00:13:27.160> Wow<00:13:27.819> like<00:13:27.999> I<00:13:28.089> think<00:13:28.149> for<00:13:28.360> a<00:13:28.389> lot<00:13:28.540> of<00:13:28.600> these 00:13:28.739 --> 00:13:28.749 align:start position:0% time Wow like I think for a lot of these 00:13:28.749 --> 00:13:30.329 align:start position:0% time Wow like I think for a lot of these cases<00:13:28.959> this<00:13:29.199> is<00:13:29.259> not<00:13:29.350> particularly<00:13:29.829> important 00:13:30.329 --> 00:13:30.339 align:start position:0% cases this is not particularly important 00:13:30.339 --> 00:13:32.460 align:start position:0% cases this is not particularly important or<00:13:30.429> like<00:13:30.850> syncing<00:13:31.480> sort<00:13:31.660> of<00:13:31.720> every<00:13:31.959> block<00:13:32.170> into 00:13:32.460 --> 00:13:32.470 align:start position:0% or like syncing sort of every block into 00:13:32.470 --> 00:13:33.929 align:start position:0% or like syncing sort of every block into sort<00:13:32.829> of<00:13:32.889> your<00:13:32.980> own<00:13:33.069> database<00:13:33.399> that<00:13:33.699> you<00:13:33.790> have 00:13:33.929 --> 00:13:33.939 align:start position:0% sort of your own database that you have 00:13:33.939 --> 00:13:35.249 align:start position:0% sort of your own database that you have sort<00:13:34.239> of<00:13:34.269> your<00:13:34.389> own<00:13:34.449> full<00:13:34.689> history<00:13:35.049> that<00:13:35.199> you 00:13:35.249 --> 00:13:35.259 align:start position:0% sort of your own full history that you 00:13:35.259 --> 00:13:38.669 align:start position:0% sort of your own full history that you can<00:13:35.410> analyze<00:13:36.149> outside<00:13:37.149> of<00:13:37.449> you<00:13:38.230> know<00:13:38.259> just<00:13:38.559> the 00:13:38.669 --> 00:13:38.679 align:start position:0% can analyze outside of you know just the 00:13:38.679 --> 00:13:40.679 align:start position:0% can analyze outside of you know just the sort<00:13:38.860> of<00:13:38.920> latest<00:13:39.429> state<00:13:39.730> like<00:13:40.449> one<00:13:40.569> of<00:13:40.629> the 00:13:40.679 --> 00:13:40.689 align:start position:0% sort of latest state like one of the 00:13:40.689 --> 00:13:42.119 align:start position:0% sort of latest state like one of the things<00:13:40.749> we<00:13:40.929> have<00:13:41.079> is<00:13:41.259> our<00:13:41.379> data<00:13:41.559> team<00:13:41.739> once<00:13:42.009> you 00:13:42.119 --> 00:13:42.129 align:start position:0% things we have is our data team once you 00:13:42.129 --> 00:13:44.729 align:start position:0% things we have is our data team once you know<00:13:42.220> full<00:13:42.489> copy<00:13:42.819> of<00:13:42.970> the<00:13:43.119> blockchain<00:13:43.899> in<00:13:44.470> you 00:13:44.729 --> 00:13:44.739 align:start position:0% know full copy of the blockchain in you 00:13:44.739 --> 00:13:45.780 align:start position:0% know full copy of the blockchain in you know<00:13:44.829> sequel<00:13:45.160> that<00:13:45.189> they<00:13:45.399> can<00:13:45.549> sort<00:13:45.699> of 00:13:45.780 --> 00:13:45.790 align:start position:0% know sequel that they can sort of 00:13:45.790 --> 00:13:49.079 align:start position:0% know sequel that they can sort of analyze<00:13:46.149> and<00:13:46.420> do<00:13:46.689> things<00:13:46.839> with<00:13:47.049> and<00:13:47.939> right<00:13:48.939> now 00:13:49.079 --> 00:13:49.089 align:start position:0% analyze and do things with and right now 00:13:49.089 --> 00:13:50.999 align:start position:0% analyze and do things with and right now so<00:13:49.660> we<00:13:49.839> sort<00:13:50.049> of<00:13:50.110> manually<00:13:50.499> build<00:13:50.649> tools<00:13:50.829> that 00:13:50.999 --> 00:13:51.009 align:start position:0% so we sort of manually build tools that 00:13:51.009 --> 00:13:53.100 align:start position:0% so we sort of manually build tools that do<00:13:51.100> that<00:13:51.129> kind<00:13:51.429> of<00:13:51.489> stuff<00:13:51.699> and<00:13:52.299> just<00:13:52.540> takes<00:13:52.989> a 00:13:53.100 --> 00:13:53.110 align:start position:0% do that kind of stuff and just takes a 00:13:53.110 --> 00:13:55.139 align:start position:0% do that kind of stuff and just takes a while<00:13:53.259> right<00:13:53.529> just<00:13:54.339> because<00:13:54.459> of<00:13:54.699> the<00:13:54.790> pure 00:13:55.139 --> 00:13:55.149 align:start position:0% while right just because of the pure 00:13:55.149 --> 00:13:57.210 align:start position:0% while right just because of the pure size<00:13:55.389> do<00:13:56.290> you<00:13:56.379> know<00:13:56.470> how<00:13:56.589> big<00:13:56.769> that<00:13:56.799> is<00:13:56.980> how 00:13:57.210 --> 00:13:57.220 align:start position:0% size do you know how big that is how 00:13:57.220 --> 00:14:01.859 align:start position:0% size do you know how big that is how much<00:13:57.369> data<00:13:58.059> that<00:14:00.239> depends<00:14:01.239> on<00:14:01.299> how<00:14:01.449> you<00:14:01.480> want 00:14:01.859 --> 00:14:01.869 align:start position:0% much data that depends on how you want 00:14:01.869 --> 00:14:03.960 align:start position:0% much data that depends on how you want to<00:14:01.929> index<00:14:02.230> it<00:14:02.439> right<00:14:02.980> so<00:14:03.249> I<00:14:03.549> think<00:14:03.579> that's<00:14:03.879> this 00:14:03.960 --> 00:14:03.970 align:start position:0% to index it right so I think that's this 00:14:03.970 --> 00:14:06.389 align:start position:0% to index it right so I think that's this project<00:14:04.389> I<00:14:04.480> saw<00:14:04.720> it<00:14:04.869> part<00:14:05.589> of<00:14:05.649> the<00:14:05.739> grant<00:14:06.189> team 00:14:06.389 --> 00:14:06.399 align:start position:0% project I saw it part of the grant team 00:14:06.399 --> 00:14:08.460 align:start position:0% project I saw it part of the grant team showcase<00:14:06.879> it<00:14:07.059> was<00:14:07.149> called<00:14:07.449> vulcanized<00:14:08.079> Evie 00:14:08.460 --> 00:14:08.470 align:start position:0% showcase it was called vulcanized Evie 00:14:08.470 --> 00:14:09.299 align:start position:0% showcase it was called vulcanized Evie or<00:14:08.589> something<00:14:08.860> like<00:14:08.949> that 00:14:09.299 --> 00:14:09.309 align:start position:0% or something like that 00:14:09.309 --> 00:14:11.519 align:start position:0% or something like that it<00:14:09.699> was<00:14:09.850> pretty<00:14:10.029> cool<00:14:10.540> you<00:14:11.049> told<00:14:11.230> them<00:14:11.319> what 00:14:11.519 --> 00:14:11.529 align:start position:0% it was pretty cool you told them what 00:14:11.529 --> 00:14:13.530 align:start position:0% it was pretty cool you told them what you<00:14:11.559> want<00:14:11.709> to<00:14:11.860> index<00:14:12.100> and<00:14:12.309> they<00:14:12.399> they<00:14:13.119> will<00:14:13.269> run 00:14:13.530 --> 00:14:13.540 align:start position:0% you want to index and they they will run 00:14:13.540 --> 00:14:15.090 align:start position:0% you want to index and they they will run it<00:14:13.660> through<00:14:13.899> and<00:14:14.170> put<00:14:14.290> it<00:14:14.350> into<00:14:14.529> a<00:14:14.559> post<00:14:14.860> Chris 00:14:15.090 --> 00:14:15.100 align:start position:0% it through and put it into a post Chris 00:14:15.100 --> 00:14:17.609 align:start position:0% it through and put it into a post Chris I<00:14:15.610> think<00:14:16.029> it's<00:14:16.239> a<00:14:16.299> great<00:14:16.449> idea<00:14:16.600> and<00:14:16.929> it's<00:14:17.319> nice 00:14:17.609 --> 00:14:17.619 align:start position:0% I think it's a great idea and it's nice 00:14:17.619 --> 00:14:19.650 align:start position:0% I think it's a great idea and it's nice it's<00:14:18.399> lowering<00:14:18.699> the<00:14:18.850> bar<00:14:19.059> so<00:14:19.329> that<00:14:19.480> not 00:14:19.650 --> 00:14:19.660 align:start position:0% it's lowering the bar so that not 00:14:19.660 --> 00:14:20.970 align:start position:0% it's lowering the bar so that not everyone<00:14:19.959> has<00:14:20.019> to<00:14:20.139> go<00:14:20.230> in<00:14:20.379> the<00:14:20.529> back<00:14:20.769> so<00:14:20.949> you 00:14:20.970 --> 00:14:20.980 align:start position:0% everyone has to go in the back so you 00:14:20.980 --> 00:14:22.379 align:start position:0% everyone has to go in the back so you know<00:14:21.069> you<00:14:21.189> guys<00:14:21.369> probably<00:14:21.399> blew<00:14:21.850> in<00:14:21.939> an<00:14:22.029> exit 00:14:22.379 --> 00:14:22.389 align:start position:0% know you guys probably blew in an exit 00:14:22.389 --> 00:14:25.169 align:start position:0% know you guys probably blew in an exit we<00:14:22.839> have<00:14:22.989> an<00:14:23.079> intensive<00:14:23.850> so<00:14:24.850> everyone's 00:14:25.169 --> 00:14:25.179 align:start position:0% we have an intensive so everyone's 00:14:25.179 --> 00:14:27.119 align:start position:0% we have an intensive so everyone's building<00:14:25.449> one<00:14:25.569> but<00:14:25.779> the<00:14:26.319> more<00:14:26.499> it<00:14:26.679> can<00:14:26.829> be<00:14:26.919> open 00:14:27.119 --> 00:14:27.129 align:start position:0% building one but the more it can be open 00:14:27.129 --> 00:14:29.519 align:start position:0% building one but the more it can be open stuff<00:14:27.869> all<00:14:28.869> right<00:14:29.019> I've<00:14:29.169> got<00:14:29.319> it<00:14:29.350> I've<00:14:29.499> got 00:14:29.519 --> 00:14:29.529 align:start position:0% stuff all right I've got it I've got 00:14:29.529 --> 00:14:31.559 align:start position:0% stuff all right I've got it I've got another<00:14:29.819> easier<00:14:30.819> one<00:14:30.970> for<00:14:31.149> you<00:14:31.239> well<00:14:31.389> maybe 00:14:31.559 --> 00:14:31.569 align:start position:0% another easier one for you well maybe 00:14:31.569 --> 00:14:33.659 align:start position:0% another easier one for you well maybe it's<00:14:31.689> not<00:14:31.749> easy<00:14:31.959> actually<00:14:32.230> it<00:14:32.980> could<00:14:33.160> be<00:14:33.309> easy 00:14:33.659 --> 00:14:33.669 align:start position:0% it's not easy actually it could be easy 00:14:33.669 --> 00:14:37.249 align:start position:0% it's not easy actually it could be easy all<00:14:33.879> the<00:14:33.970> way<00:14:34.029> to<00:14:34.089> hard<00:14:34.350> so<00:14:35.350> so<00:14:35.739> parity<00:14:36.069> again 00:14:37.249 --> 00:14:37.259 align:start position:0% all the way to hard so so parity again 00:14:37.259 --> 00:14:40.249 align:start position:0% all the way to hard so so parity again or<00:14:38.259> a<00:14:38.319> lot<00:14:38.619> if<00:14:38.980> you<00:14:39.009> like<00:14:39.249> that<00:14:39.399> one 00:14:40.249 --> 00:14:40.259 align:start position:0% or a lot if you like that one 00:14:40.259 --> 00:14:45.179 align:start position:0% or a lot if you like that one I'm<00:14:41.259> partial<00:14:42.249> to<00:14:42.279> parity<00:14:42.669> I<00:14:43.230> found<00:14:44.230> it's<00:14:44.470> been 00:14:45.179 --> 00:14:45.189 align:start position:0% I'm partial to parity I found it's been 00:14:45.189 --> 00:14:47.249 align:start position:0% I'm partial to parity I found it's been more<00:14:45.369> reliable<00:14:45.850> and<00:14:46.059> faster<00:14:46.749> sync<00:14:46.959> has<00:14:47.079> been 00:14:47.249 --> 00:14:47.259 align:start position:0% more reliable and faster sync has been 00:14:47.259 --> 00:14:49.559 align:start position:0% more reliable and faster sync has been nicer<00:14:47.589> and<00:14:47.769> we<00:14:48.759> can<00:14:48.910> get<00:14:49.059> into<00:14:49.269> the<00:14:49.389> whole 00:14:49.559 --> 00:14:49.569 align:start position:0% nicer and we can get into the whole 00:14:49.569 --> 00:14:55.499 align:start position:0% nicer and we can get into the whole parity<00:14:50.529> trace<00:14:50.769> parsing<00:14:51.399> issue<00:14:53.100> we<00:14:54.100> will<00:14:54.509> yeah 00:14:55.499 --> 00:14:55.509 align:start position:0% parity trace parsing issue we will yeah 00:14:55.509 --> 00:14:57.239 align:start position:0% parity trace parsing issue we will yeah but<00:14:55.809> we<00:14:56.350> can<00:14:56.649> definitely<00:14:56.739> we<00:14:57.040> can<00:14:57.160> definitely 00:14:57.239 --> 00:14:57.249 align:start position:0% but we can definitely we can definitely 00:14:57.249 --> 00:14:59.789 align:start position:0% but we can definitely we can definitely hop<00:14:57.549> into<00:14:57.759> that<00:14:58.019> yeah<00:14:59.019> that's<00:14:59.439> definitely<00:14:59.499> one 00:14:59.789 --> 00:14:59.799 align:start position:0% hop into that yeah that's definitely one 00:14:59.799 --> 00:15:02.009 align:start position:0% hop into that yeah that's definitely one a<00:14:59.829> bandage<00:15:00.160> parity<00:15:00.429> had<00:15:00.549> early<00:15:00.790> on<00:15:00.910> yeah<00:15:01.689> well 00:15:02.009 --> 00:15:02.019 align:start position:0% a bandage parity had early on yeah well 00:15:02.019 --> 00:15:03.769 align:start position:0% a bandage parity had early on yeah well that's<00:15:02.350> what<00:15:02.470> I've<00:15:02.589> heard<00:15:02.619> it<00:15:02.980> is<00:15:03.189> with<00:15:03.399> parity 00:15:03.769 --> 00:15:03.779 align:start position:0% that's what I've heard it is with parity 00:15:03.779 --> 00:15:05.970 align:start position:0% that's what I've heard it is with parity what<00:15:04.779> we're<00:15:04.899> sort<00:15:05.079> of<00:15:05.199> ending<00:15:05.559> out<00:15:05.649> here<00:15:05.860> is 00:15:05.970 --> 00:15:05.980 align:start position:0% what we're sort of ending out here is 00:15:05.980 --> 00:15:07.470 align:start position:0% what we're sort of ending out here is this<00:15:06.069> idea<00:15:06.249> if<00:15:06.489> you're<00:15:06.790> only<00:15:06.879> terse<00:15:07.119> can<00:15:07.299> you 00:15:07.470 --> 00:15:07.480 align:start position:0% this idea if you're only terse can you 00:15:07.480 --> 00:15:09.179 align:start position:0% this idea if you're only terse can you see<00:15:07.629> contracts<00:15:08.169> and<00:15:08.350> heathyr<00:15:08.619> around<00:15:08.889> they 00:15:09.179 --> 00:15:09.189 align:start position:0% see contracts and heathyr around they 00:15:09.189 --> 00:15:12.059 align:start position:0% see contracts and heathyr around they call<00:15:09.610> them<00:15:09.759> internal<00:15:10.389> transactions<00:15:11.019> and<00:15:11.259> sort 00:15:12.059 --> 00:15:12.069 align:start position:0% call them internal transactions and sort 00:15:12.069 --> 00:15:14.249 align:start position:0% call them internal transactions and sort of<00:15:12.160> detecting<00:15:12.579> those<00:15:12.730> and<00:15:13.540> seeing<00:15:13.839> like<00:15:14.049> where 00:15:14.249 --> 00:15:14.259 align:start position:0% of detecting those and seeing like where 00:15:14.259 --> 00:15:16.139 align:start position:0% of detecting those and seeing like where money<00:15:14.499> moves<00:15:14.739> is<00:15:14.919> a<00:15:15.100> complicated<00:15:15.699> thing<00:15:15.730> I 00:15:16.139 --> 00:15:16.149 align:start position:0% money moves is a complicated thing I 00:15:16.149 --> 00:15:17.609 align:start position:0% money moves is a complicated thing I actually<00:15:16.509> give<00:15:16.749> a<00:15:16.809> talk<00:15:16.959> on<00:15:16.989> this<00:15:17.169> yesterday 00:15:17.609 --> 00:15:17.619 align:start position:0% actually give a talk on this yesterday 00:15:17.619 --> 00:15:19.979 align:start position:0% actually give a talk on this yesterday that<00:15:18.179> it'll<00:15:19.179> be<00:15:19.239> a<00:15:19.269> recording<00:15:19.600> of<00:15:19.689> and<00:15:19.839> stuff 00:15:19.979 --> 00:15:19.989 align:start position:0% that it'll be a recording of and stuff 00:15:19.989 --> 00:15:21.269 align:start position:0% that it'll be a recording of and stuff about<00:15:20.199> sort<00:15:20.410> of<00:15:20.439> the<00:15:20.559> ins<00:15:20.709> and<00:15:20.829> outs<00:15:21.009> of<00:15:21.160> how 00:15:21.269 --> 00:15:21.279 align:start position:0% about sort of the ins and outs of how 00:15:21.279 --> 00:15:23.429 align:start position:0% about sort of the ins and outs of how that<00:15:21.339> works<00:15:21.819> and<00:15:21.970> stuff<00:15:22.149> but<00:15:22.839> from<00:15:23.350> my 00:15:23.429 --> 00:15:23.439 align:start position:0% that works and stuff but from my 00:15:23.439 --> 00:15:24.670 align:start position:0% that works and stuff but from my understanding<00:15:23.769> I<00:15:24.189> wasn't 00:15:24.670 --> 00:15:24.680 align:start position:0% understanding I wasn't 00:15:24.680 --> 00:15:27.370 align:start position:0% understanding I wasn't just<00:15:25.190> happened<00:15:25.490> but<00:15:25.810> parody<00:15:26.810> was<00:15:26.960> one<00:15:27.230> of<00:15:27.320> the 00:15:27.370 --> 00:15:27.380 align:start position:0% just happened but parody was one of the 00:15:27.380 --> 00:15:29.260 align:start position:0% just happened but parody was one of the first<00:15:27.589> ones<00:15:27.830> to<00:15:28.010> give<00:15:28.250> an<00:15:28.339> API<00:15:28.610> that<00:15:28.880> made<00:15:29.089> that 00:15:29.260 --> 00:15:29.270 align:start position:0% first ones to give an API that made that 00:15:29.270 --> 00:15:31.450 align:start position:0% first ones to give an API that made that more<00:15:29.600> like<00:15:29.870> accessible<00:15:30.380> and<00:15:30.680> easy<00:15:30.920> to<00:15:31.190> sort<00:15:31.370> of 00:15:31.450 --> 00:15:31.460 align:start position:0% more like accessible and easy to sort of 00:15:31.460 --> 00:15:33.400 align:start position:0% more like accessible and easy to sort of figure<00:15:31.610> out<00:15:31.730> what<00:15:31.850> happened<00:15:32.180> and<00:15:32.600> guess<00:15:33.170> now<00:15:33.380> I 00:15:33.400 --> 00:15:33.410 align:start position:0% figure out what happened and guess now I 00:15:33.410 --> 00:15:35.769 align:start position:0% figure out what happened and guess now I believe<00:15:34.040> since<00:15:34.310> 1.8<00:15:34.880> it<00:15:35.000> was<00:15:35.120> does<00:15:35.480> have<00:15:35.660> an 00:15:35.769 --> 00:15:35.779 align:start position:0% believe since 1.8 it was does have an 00:15:35.779 --> 00:15:37.600 align:start position:0% believe since 1.8 it was does have an API<00:15:36.050> for<00:15:36.110> this<00:15:36.350> -<00:15:36.589> but<00:15:37.310> it's<00:15:37.460> not<00:15:37.550> a 00:15:37.600 --> 00:15:37.610 align:start position:0% API for this - but it's not a 00:15:37.610 --> 00:15:39.310 align:start position:0% API for this - but it's not a standardized<00:15:38.149> API<00:15:38.300> it'sit's<00:15:39.020> actually<00:15:39.110> a 00:15:39.310 --> 00:15:39.320 align:start position:0% standardized API it'sit's actually a 00:15:39.320 --> 00:15:40.960 align:start position:0% standardized API it'sit's actually a custom<00:15:39.680> one<00:15:39.800> for<00:15:40.040> each<00:15:40.160> one<00:15:40.370> and<00:15:40.430> so<00:15:40.790> there's 00:15:40.960 --> 00:15:40.970 align:start position:0% custom one for each one and so there's 00:15:40.970 --> 00:15:42.730 align:start position:0% custom one for each one and so there's no<00:15:41.089> standard<00:15:41.510> way<00:15:41.540> to<00:15:41.690> process<00:15:42.560> these<00:15:42.680> and 00:15:42.730 --> 00:15:42.740 align:start position:0% no standard way to process these and 00:15:42.740 --> 00:15:44.380 align:start position:0% no standard way to process these and that's<00:15:43.010> setting<00:15:43.339> something<00:15:43.610> that<00:15:43.790> would<00:15:44.300> be 00:15:44.380 --> 00:15:44.390 align:start position:0% that's setting something that would be 00:15:44.390 --> 00:15:45.370 align:start position:0% that's setting something that would be really<00:15:44.570> interesting<00:15:44.899> to<00:15:44.930> see<00:15:45.110> in<00:15:45.200> the<00:15:45.260> future 00:15:45.370 --> 00:15:45.380 align:start position:0% really interesting to see in the future 00:15:45.380 --> 00:15:47.230 align:start position:0% really interesting to see in the future yeah<00:15:46.040> it's<00:15:46.279> it's<00:15:46.580> interesting<00:15:46.820> because<00:15:47.089> like 00:15:47.230 --> 00:15:47.240 align:start position:0% yeah it's it's interesting because like 00:15:47.240 --> 00:15:49.360 align:start position:0% yeah it's it's interesting because like there<00:15:47.779> there<00:15:48.230> are<00:15:48.350> lots<00:15:48.380> of<00:15:48.680> transactions 00:15:49.360 --> 00:15:49.370 align:start position:0% there there are lots of transactions 00:15:49.370 --> 00:15:50.889 align:start position:0% there there are lots of transactions that<00:15:49.490> happen<00:15:49.820> that<00:15:49.940> appear<00:15:50.420> nowhere<00:15:50.600> in<00:15:50.810> the 00:15:50.889 --> 00:15:50.899 align:start position:0% that happen that appear nowhere in the 00:15:50.899 --> 00:15:53.170 align:start position:0% that happen that appear nowhere in the blockchain<00:15:51.110> right<00:15:51.800> and<00:15:52.339> so<00:15:52.760> I<00:15:52.790> think<00:15:52.940> that's 00:15:53.170 --> 00:15:53.180 align:start position:0% blockchain right and so I think that's 00:15:53.180 --> 00:15:54.310 align:start position:0% blockchain right and so I think that's one<00:15:53.450> of<00:15:53.480> the<00:15:53.600> interesting<00:15:53.720> differences 00:15:54.310 --> 00:15:54.320 align:start position:0% one of the interesting differences 00:15:54.320 --> 00:15:55.930 align:start position:0% one of the interesting differences between<00:15:54.529> aetherium<00:15:54.890> and<00:15:55.130> a<00:15:55.310> lot<00:15:55.730> of<00:15:55.820> other 00:15:55.930 --> 00:15:55.940 align:start position:0% between aetherium and a lot of other 00:15:55.940 --> 00:15:59.380 align:start position:0% between aetherium and a lot of other ones<00:15:56.089> but<00:15:56.360> Ben<00:15:56.959> what<00:15:57.080> about<00:15:57.230> you<00:15:57.380> yeah<00:15:58.300> so<00:15:59.300> the 00:15:59.380 --> 00:15:59.390 align:start position:0% ones but Ben what about you yeah so the 00:15:59.390 --> 00:16:01.690 align:start position:0% ones but Ben what about you yeah so the first<00:15:59.600> question<00:15:59.720> I<00:16:00.350> think<00:16:00.680> both<00:16:01.070> parody<00:16:01.610> and 00:16:01.690 --> 00:16:01.700 align:start position:0% first question I think both parody and 00:16:01.700 --> 00:16:05.949 align:start position:0% first question I think both parody and get<00:16:01.880> ok<00:16:02.270> random<00:16:02.990> both<00:16:03.940> depending<00:16:04.940> on<00:16:05.060> what<00:16:05.750> the 00:16:05.949 --> 00:16:05.959 align:start position:0% get ok random both depending on what the 00:16:05.959 --> 00:16:07.990 align:start position:0% get ok random both depending on what the network<00:16:06.320> situation<00:16:06.830> is<00:16:06.950> sometimes<00:16:07.370> some<00:16:07.970> of 00:16:07.990 --> 00:16:08.000 align:start position:0% network situation is sometimes some of 00:16:08.000 --> 00:16:09.370 align:start position:0% network situation is sometimes some of them<00:16:08.180> a<00:16:08.240> challenge<00:16:08.570> is<00:16:08.690> processing<00:16:09.170> certain 00:16:09.370 --> 00:16:09.380 align:start position:0% them a challenge is processing certain 00:16:09.380 --> 00:16:11.110 align:start position:0% them a challenge is processing certain types<00:16:09.589> of<00:16:09.770> transactions<00:16:10.279> and<00:16:10.399> blocks<00:16:10.580> and 00:16:11.110 --> 00:16:11.120 align:start position:0% types of transactions and blocks and 00:16:11.120 --> 00:16:12.940 align:start position:0% types of transactions and blocks and some<00:16:11.360> of<00:16:11.480> them<00:16:11.600> you<00:16:12.080> know<00:16:12.110> then<00:16:12.589> the<00:16:12.709> other<00:16:12.830> one 00:16:12.940 --> 00:16:12.950 align:start position:0% some of them you know then the other one 00:16:12.950 --> 00:16:15.220 align:start position:0% some of them you know then the other one goes<00:16:13.130> faster<00:16:13.520> than<00:16:13.550> so<00:16:14.390> I<00:16:14.420> think<00:16:14.570> running<00:16:15.050> both 00:16:15.220 --> 00:16:15.230 align:start position:0% goes faster than so I think running both 00:16:15.230 --> 00:16:19.210 align:start position:0% goes faster than so I think running both this<00:16:15.740> is<00:16:15.800> the<00:16:15.920> way<00:16:16.040> to<00:16:16.100> go<00:16:17.200> with<00:16:18.200> I<00:16:18.529> think<00:16:19.130> that 00:16:19.210 --> 00:16:19.220 align:start position:0% this is the way to go with I think that 00:16:19.220 --> 00:16:21.639 align:start position:0% this is the way to go with I think that this<00:16:19.339> is<00:16:19.459> a<00:16:19.490> huge<00:16:19.820> topic<00:16:20.649> internal 00:16:21.639 --> 00:16:21.649 align:start position:0% this is a huge topic internal 00:16:21.649 --> 00:16:24.190 align:start position:0% this is a huge topic internal transactions<00:16:22.450> for<00:16:23.450> us<00:16:23.570> it's<00:16:23.810> one<00:16:23.870> of<00:16:24.080> the 00:16:24.190 --> 00:16:24.200 align:start position:0% transactions for us it's one of the 00:16:24.200 --> 00:16:27.639 align:start position:0% transactions for us it's one of the largest<00:16:24.529> pain<00:16:25.310> points<00:16:25.720> so<00:16:26.720> a<00:16:26.750> bit<00:16:27.080> go<00:16:27.230> we<00:16:27.410> use 00:16:27.639 --> 00:16:27.649 align:start position:0% largest pain points so a bit go we use 00:16:27.649 --> 00:16:29.410 align:start position:0% largest pain points so a bit go we use multi-sig<00:16:28.220> wallets<00:16:28.520> these<00:16:28.760> are<00:16:29.000> all<00:16:29.330> the 00:16:29.410 --> 00:16:29.420 align:start position:0% multi-sig wallets these are all the 00:16:29.420 --> 00:16:33.329 align:start position:0% multi-sig wallets these are all the contracts<00:16:29.839> in<00:16:30.110> smart<00:16:30.470> contracts<00:16:30.830> and<00:16:31.870> for<00:16:32.870> us 00:16:33.329 --> 00:16:33.339 align:start position:0% contracts in smart contracts and for us 00:16:33.339 --> 00:16:35.710 align:start position:0% contracts in smart contracts and for us when<00:16:34.339> when<00:16:34.670> we<00:16:34.880> send<00:16:35.120> out<00:16:35.240> from<00:16:35.390> the<00:16:35.510> smart 00:16:35.710 --> 00:16:35.720 align:start position:0% when when we send out from the smart 00:16:35.720 --> 00:16:37.390 align:start position:0% when when we send out from the smart contracts<00:16:36.020> we<00:16:36.110> want<00:16:36.320> the<00:16:36.770> receiver<00:16:37.100> to<00:16:37.310> be 00:16:37.390 --> 00:16:37.400 align:start position:0% contracts we want the receiver to be 00:16:37.400 --> 00:16:41.160 align:start position:0% contracts we want the receiver to be able<00:16:37.490> to<00:16:37.640> see<00:16:37.910> the<00:16:38.450> funds<00:16:39.070> on<00:16:40.070> more<00:16:40.370> modern 00:16:41.160 --> 00:16:41.170 align:start position:0% able to see the funds on more modern 00:16:41.170 --> 00:16:44.710 align:start position:0% able to see the funds on more modern exchanges<00:16:42.279> they<00:16:43.279> do<00:16:43.339> you<00:16:44.270> know<00:16:44.360> record<00:16:44.660> the 00:16:44.710 --> 00:16:44.720 align:start position:0% exchanges they do you know record the 00:16:44.720 --> 00:16:47.350 align:start position:0% exchanges they do you know record the deposit<00:16:45.140> because<00:16:45.890> they<00:16:46.010> can<00:16:46.130> look<00:16:46.339> at<00:16:46.550> these 00:16:47.350 --> 00:16:47.360 align:start position:0% deposit because they can look at these 00:16:47.360 --> 00:16:49.030 align:start position:0% deposit because they can look at these internal<00:16:47.720> transactions<00:16:48.170> and<00:16:48.320> so<00:16:48.410> a<00:16:48.770> little 00:16:49.030 --> 00:16:49.040 align:start position:0% internal transactions and so a little 00:16:49.040 --> 00:16:51.310 align:start position:0% internal transactions and so a little bit<00:16:49.130> about<00:16:49.279> international<00:16:49.490> sections<00:16:50.060> so<00:16:50.320> in 00:16:51.310 --> 00:16:51.320 align:start position:0% bit about international sections so in 00:16:51.320 --> 00:16:53.230 align:start position:0% bit about international sections so in aetherium<00:16:51.800> you<00:16:52.310> have<00:16:52.459> transactions<00:16:53.000> and 00:16:53.230 --> 00:16:53.240 align:start position:0% aetherium you have transactions and 00:16:53.240 --> 00:16:55.720 align:start position:0% aetherium you have transactions and transactions<00:16:53.990> are<00:16:54.110> what<00:16:54.290> I<00:16:54.709> think<00:16:55.400> are<00:16:55.670> the 00:16:55.720 --> 00:16:55.730 align:start position:0% transactions are what I think are the 00:16:55.730 --> 00:16:57.579 align:start position:0% transactions are what I think are the first<00:16:56.029> we<00:16:56.660> can<00:16:56.810> call<00:16:56.959> it<00:16:57.050> like<00:16:57.140> the<00:16:57.230> first<00:16:57.440> hop 00:16:57.579 --> 00:16:57.589 align:start position:0% first we can call it like the first hop 00:16:57.589 --> 00:17:00.730 align:start position:0% first we can call it like the first hop in<00:16:58.190> which<00:16:58.310> an<00:16:58.430> account<00:16:58.810> send<00:16:59.810> something<00:17:00.080> to<00:17:00.260> an 00:17:00.730 --> 00:17:00.740 align:start position:0% in which an account send something to an 00:17:00.740 --> 00:17:02.350 align:start position:0% in which an account send something to an address<00:17:01.370> where<00:17:01.550> the<00:17:01.670> address<00:17:01.880> is<00:17:02.000> either 00:17:02.350 --> 00:17:02.360 align:start position:0% address where the address is either 00:17:02.360 --> 00:17:06.689 align:start position:0% address where the address is either contract<00:17:03.290> or<00:17:03.800> another<00:17:04.579> account<00:17:05.209> and<00:17:05.530> a 00:17:06.689 --> 00:17:06.699 align:start position:0% contract or another account and a 00:17:06.699 --> 00:17:09.160 align:start position:0% contract or another account and a challenge<00:17:07.699> is<00:17:07.819> after<00:17:08.120> that<00:17:08.240> if<00:17:08.780> you<00:17:08.900> send<00:17:09.050> it 00:17:09.160 --> 00:17:09.170 align:start position:0% challenge is after that if you send it 00:17:09.170 --> 00:17:10.540 align:start position:0% challenge is after that if you send it to<00:17:09.290> a<00:17:09.319> contract<00:17:09.829> and<00:17:09.980> tell<00:17:10.100> the<00:17:10.220> contract<00:17:10.490> to 00:17:10.540 --> 00:17:10.550 align:start position:0% to a contract and tell the contract to 00:17:10.550 --> 00:17:12.460 align:start position:0% to a contract and tell the contract to do<00:17:10.640> something<00:17:11.000> then<00:17:11.630> internally<00:17:12.199> the 00:17:12.460 --> 00:17:12.470 align:start position:0% do something then internally the 00:17:12.470 --> 00:17:16.210 align:start position:0% do something then internally the contract<00:17:12.890> is<00:17:13.040> is<00:17:13.339> making<00:17:14.329> changes<00:17:14.809> to<00:17:15.470> state 00:17:16.210 --> 00:17:16.220 align:start position:0% contract is is making changes to state 00:17:16.220 --> 00:17:18.910 align:start position:0% contract is is making changes to state and<00:17:16.490> doing<00:17:17.300> internal<00:17:17.689> messages<00:17:18.110> some<00:17:18.800> of 00:17:18.910 --> 00:17:18.920 align:start position:0% and doing internal messages some of 00:17:18.920 --> 00:17:21.790 align:start position:0% and doing internal messages some of which<00:17:19.100> may<00:17:19.370> be<00:17:20.059> sending<00:17:20.750> funds<00:17:21.170> like<00:17:21.620> a 00:17:21.790 --> 00:17:21.800 align:start position:0% which may be sending funds like a 00:17:21.800 --> 00:17:26.890 align:start position:0% which may be sending funds like a theorem<00:17:22.100> to<00:17:22.730> other<00:17:23.150> dresses<00:17:24.250> now<00:17:25.900> the 00:17:26.890 --> 00:17:26.900 align:start position:0% theorem to other dresses now the 00:17:26.900 --> 00:17:28.540 align:start position:0% theorem to other dresses now the challenge<00:17:27.230> with<00:17:27.319> that<00:17:27.350> is<00:17:27.530> that<00:17:27.709> currently<00:17:28.400> in 00:17:28.540 --> 00:17:28.550 align:start position:0% challenge with that is that currently in 00:17:28.550 --> 00:17:31.030 align:start position:0% challenge with that is that currently in the<00:17:28.640> web<00:17:28.790> 3<00:17:28.970> API<00:17:29.300> there<00:17:30.080> is<00:17:30.200> a<00:17:30.230> get<00:17:30.470> transaction 00:17:31.030 --> 00:17:31.040 align:start position:0% the web 3 API there is a get transaction 00:17:31.040 --> 00:17:33.280 align:start position:0% the web 3 API there is a get transaction which<00:17:31.370> does<00:17:31.610> the<00:17:31.820> first<00:17:32.030> one<00:17:32.240> it<00:17:32.450> shows<00:17:32.960> you 00:17:33.280 --> 00:17:33.290 align:start position:0% which does the first one it shows you 00:17:33.290 --> 00:17:35.950 align:start position:0% which does the first one it shows you all<00:17:33.620> transactions<00:17:34.429> that<00:17:34.580> come<00:17:34.820> you<00:17:35.510> know<00:17:35.630> from 00:17:35.950 --> 00:17:35.960 align:start position:0% all transactions that come you know from 00:17:35.960 --> 00:17:36.870 align:start position:0% all transactions that come you know from accounts 00:17:36.870 --> 00:17:36.880 align:start position:0% accounts 00:17:36.880 --> 00:17:40.050 align:start position:0% accounts to<00:17:37.750> smart<00:17:38.080> contracts<00:17:38.500> but<00:17:39.220> usually<00:17:39.670> what<00:17:39.880> a 00:17:40.050 --> 00:17:40.060 align:start position:0% to smart contracts but usually what a 00:17:40.060 --> 00:17:42.270 align:start position:0% to smart contracts but usually what a multi-sig<00:17:40.540> wallet<00:17:40.810> is<00:17:41.020> is<00:17:41.440> that<00:17:41.650> you<00:17:42.160> would 00:17:42.270 --> 00:17:42.280 align:start position:0% multi-sig wallet is is that you would 00:17:42.280 --> 00:17:44.400 align:start position:0% multi-sig wallet is is that you would send<00:17:42.490> a<00:17:42.580> transaction<00:17:42.910> from<00:17:43.510> one<00:17:43.780> of<00:17:43.870> the<00:17:43.960> sinus 00:17:44.400 --> 00:17:44.410 align:start position:0% send a transaction from one of the sinus 00:17:44.410 --> 00:17:46.350 align:start position:0% send a transaction from one of the sinus to<00:17:45.070> the<00:17:45.340> multi-sig<00:17:45.760> wallet<00:17:46.030> and<00:17:46.120> then<00:17:46.300> a 00:17:46.350 --> 00:17:46.360 align:start position:0% to the multi-sig wallet and then a 00:17:46.360 --> 00:17:48.300 align:start position:0% to the multi-sig wallet and then a multi-state<00:17:46.780> wallet<00:17:47.050> would<00:17:47.140> then<00:17:47.350> send<00:17:48.160> out 00:17:48.300 --> 00:17:48.310 align:start position:0% multi-state wallet would then send out 00:17:48.310 --> 00:17:50.160 align:start position:0% multi-state wallet would then send out the<00:17:48.490> funds<00:17:48.730> from<00:17:49.030> the<00:17:49.390> smart<00:17:49.630> contract<00:17:49.780> and 00:17:50.160 --> 00:17:50.170 align:start position:0% the funds from the smart contract and 00:17:50.170 --> 00:17:52.440 align:start position:0% the funds from the smart contract and that<00:17:50.500> is<00:17:50.770> a<00:17:50.800> smart<00:17:51.610> contract<00:17:51.790> transaction<00:17:52.360> or 00:17:52.440 --> 00:17:52.450 align:start position:0% that is a smart contract transaction or 00:17:52.450 --> 00:17:55.620 align:start position:0% that is a smart contract transaction or internal<00:17:52.750> transaction<00:17:53.200> so<00:17:53.800> there's<00:17:54.340> no<00:17:54.630> you 00:17:55.620 --> 00:17:55.630 align:start position:0% internal transaction so there's no you 00:17:55.630 --> 00:17:58.710 align:start position:0% internal transaction so there's no you know<00:17:55.690> RPC<00:17:56.410> or<00:17:56.530> API<00:17:56.860> to<00:17:57.790> easily<00:17:58.150> get<00:17:58.360> ahold<00:17:58.600> of 00:17:58.710 --> 00:17:58.720 align:start position:0% know RPC or API to easily get ahold of 00:17:58.720 --> 00:18:00.450 align:start position:0% know RPC or API to easily get ahold of those<00:17:58.840> transactions<00:17:59.440> as<00:17:59.650> a<00:17:59.710> result<00:18:00.130> some<00:18:00.430> of 00:18:00.450 --> 00:18:00.460 align:start position:0% those transactions as a result some of 00:18:00.460 --> 00:18:03.840 align:start position:0% those transactions as a result some of some<00:18:01.360> of<00:18:01.450> the<00:18:01.570> exchanges<00:18:02.580> they<00:18:03.580> don't 00:18:03.840 --> 00:18:03.850 align:start position:0% some of the exchanges they don't 00:18:03.850 --> 00:18:06.390 align:start position:0% some of the exchanges they don't recognize<00:18:04.540> deposits<00:18:05.290> automatically<00:18:05.830> for 00:18:06.390 --> 00:18:06.400 align:start position:0% recognize deposits automatically for 00:18:06.400 --> 00:18:10.290 align:start position:0% recognize deposits automatically for such<00:18:06.550> or<00:18:07.090> such<00:18:07.150> not<00:18:07.510> contracts<00:18:07.870> in<00:18:08.020> and<00:18:09.030> this<00:18:10.030> I 00:18:10.290 --> 00:18:10.300 align:start position:0% such or such not contracts in and this I 00:18:10.300 --> 00:18:12.480 align:start position:0% such or such not contracts in and this I think<00:18:10.390> will<00:18:10.840> be<00:18:11.080> further<00:18:11.740> accelerated 00:18:12.480 --> 00:18:12.490 align:start position:0% think will be further accelerated 00:18:12.490 --> 00:18:14.610 align:start position:0% think will be further accelerated because<00:18:12.700> now<00:18:13.030> we're<00:18:13.210> moving<00:18:13.360> towards<00:18:13.960> oh<00:18:14.110> is 00:18:14.610 --> 00:18:14.620 align:start position:0% because now we're moving towards oh is 00:18:14.620 --> 00:18:17.150 align:start position:0% because now we're moving towards oh is that<00:18:14.650> unified<00:18:15.580> the<00:18:15.610> unify<00:18:16.150> idea<00:18:16.450> Wallis 00:18:17.150 --> 00:18:17.160 align:start position:0% that unified the unify idea Wallis 00:18:17.160 --> 00:18:19.950 align:start position:0% that unified the unify idea Wallis versal<00:18:18.190> yeah<00:18:18.430> universal<00:18:19.360> login<00:18:19.480> wallets 00:18:19.950 --> 00:18:19.960 align:start position:0% versal yeah universal login wallets 00:18:19.960 --> 00:18:22.110 align:start position:0% versal yeah universal login wallets which<00:18:20.410> I<00:18:20.560> think<00:18:20.770> I'm<00:18:20.860> a<00:18:20.980> big<00:18:21.190> believer<00:18:21.340> of<00:18:21.580> from 00:18:22.110 --> 00:18:22.120 align:start position:0% which I think I'm a big believer of from 00:18:22.120 --> 00:18:25.470 align:start position:0% which I think I'm a big believer of from a<00:18:22.150> UX<00:18:22.810> standpoint<00:18:23.200> I<00:18:24.210> remember<00:18:25.210> yeah<00:18:25.300> also 00:18:25.470 --> 00:18:25.480 align:start position:0% a UX standpoint I remember yeah also 00:18:25.480 --> 00:18:27.000 align:start position:0% a UX standpoint I remember yeah also smart<00:18:25.780> contracts<00:18:26.080> so<00:18:26.230> we<00:18:26.440> need<00:18:26.590> to<00:18:26.680> solve<00:18:26.860> this 00:18:27.000 --> 00:18:27.010 align:start position:0% smart contracts so we need to solve this 00:18:27.010 --> 00:18:30.270 align:start position:0% smart contracts so we need to solve this problem<00:18:27.690> you<00:18:28.690> know<00:18:28.780> as<00:18:28.960> an<00:18:29.080> industry<00:18:29.380> and<00:18:29.590> make 00:18:30.270 --> 00:18:30.280 align:start position:0% problem you know as an industry and make 00:18:30.280 --> 00:18:33.000 align:start position:0% problem you know as an industry and make more<00:18:30.490> people<00:18:30.670> actually<00:18:31.770> taking<00:18:32.770> deposits 00:18:33.000 --> 00:18:33.010 align:start position:0% more people actually taking deposits 00:18:33.010 --> 00:18:34.500 align:start position:0% more people actually taking deposits from<00:18:33.400> small<00:18:33.640> contracts<00:18:34.000> because<00:18:34.210> that's<00:18:34.360> what 00:18:34.500 --> 00:18:34.510 align:start position:0% from small contracts because that's what 00:18:34.510 --> 00:18:36.810 align:start position:0% from small contracts because that's what even<00:18:34.840> this<00:18:34.900> is<00:18:35.470> about<00:18:35.740> right<00:18:35.980> it's<00:18:36.550> a<00:18:36.640> small 00:18:36.810 --> 00:18:36.820 align:start position:0% even this is about right it's a small 00:18:36.820 --> 00:18:37.350 align:start position:0% even this is about right it's a small contracts 00:18:37.350 --> 00:18:37.360 align:start position:0% contracts 00:18:37.360 --> 00:18:38.640 align:start position:0% contracts yeah<00:18:37.570> and<00:18:37.720> it's<00:18:37.810> it's<00:18:38.050> a<00:18:38.140> scary<00:18:38.410> thing<00:18:38.590> to 00:18:38.640 --> 00:18:38.650 align:start position:0% yeah and it's it's a scary thing to 00:18:38.650 --> 00:18:42.060 align:start position:0% yeah and it's it's a scary thing to Parsa<00:18:39.220> process<00:18:39.670> these<00:18:39.790> two<00:18:40.710> you<00:18:41.710> can<00:18:41.740> have 00:18:42.060 --> 00:18:42.070 align:start position:0% Parsa process these two you can have 00:18:42.070 --> 00:18:43.650 align:start position:0% Parsa process these two you can have some<00:18:42.250> pretty<00:18:42.400> like<00:18:42.700> dangerous<00:18:43.240> sort<00:18:43.420> of<00:18:43.510> bugs 00:18:43.650 --> 00:18:43.660 align:start position:0% some pretty like dangerous sort of bugs 00:18:43.660 --> 00:18:44.790 align:start position:0% some pretty like dangerous sort of bugs that<00:18:43.780> come<00:18:43.930> up<00:18:44.110> from<00:18:44.290> doing<00:18:44.470> this<00:18:44.560> the<00:18:44.710> wrong 00:18:44.790 --> 00:18:44.800 align:start position:0% that come up from doing this the wrong 00:18:44.800 --> 00:18:47.550 align:start position:0% that come up from doing this the wrong way<00:18:44.860> and<00:18:45.160> so<00:18:45.630> there's<00:18:46.630> plenty<00:18:46.900> of<00:18:47.080> exchanges 00:18:47.550 --> 00:18:47.560 align:start position:0% way and so there's plenty of exchanges 00:18:47.560 --> 00:18:49.200 align:start position:0% way and so there's plenty of exchanges and<00:18:47.680> stuff<00:18:47.830> who<00:18:48.010> don't<00:18:48.430> want<00:18:48.640> to<00:18:48.730> do<00:18:48.850> this<00:18:48.970> yet 00:18:49.200 --> 00:18:49.210 align:start position:0% and stuff who don't want to do this yet 00:18:49.210 --> 00:18:50.880 align:start position:0% and stuff who don't want to do this yet because<00:18:49.480> it<00:18:49.780> is<00:18:49.930> this<00:18:50.080> sort<00:18:50.260> of<00:18:50.350> scary<00:18:50.650> thing 00:18:50.880 --> 00:18:50.890 align:start position:0% because it is this sort of scary thing 00:18:50.890 --> 00:18:53.010 align:start position:0% because it is this sort of scary thing to<00:18:51.070> get<00:18:51.190> wrong<00:18:51.430> whereas<00:18:52.270> like<00:18:52.420> transactions 00:18:53.010 --> 00:18:53.020 align:start position:0% to get wrong whereas like transactions 00:18:53.020 --> 00:18:54.420 align:start position:0% to get wrong whereas like transactions and<00:18:53.200> stuff<00:18:53.350> are<00:18:53.470> fairly<00:18:53.680> straightforward<00:18:54.010> to 00:18:54.420 --> 00:18:54.430 align:start position:0% and stuff are fairly straightforward to 00:18:54.430 --> 00:18:55.920 align:start position:0% and stuff are fairly straightforward to kind<00:18:54.580> of<00:18:54.640> tell<00:18:54.790> what's<00:18:54.940> going<00:18:55.150> on<00:18:55.240> these 00:18:55.920 --> 00:18:55.930 align:start position:0% kind of tell what's going on these 00:18:55.930 --> 00:18:57.690 align:start position:0% kind of tell what's going on these aren't<00:18:56.140> so<00:18:56.350> it's<00:18:56.470> a<00:18:56.530> big<00:18:56.710> risk<00:18:56.950> and<00:18:57.130> especially 00:18:57.690 --> 00:18:57.700 align:start position:0% aren't so it's a big risk and especially 00:18:57.700 --> 00:18:59.310 align:start position:0% aren't so it's a big risk and especially as<00:18:57.940> we<00:18:58.090> move<00:18:58.120> to<00:18:58.390> more<00:18:58.420> and<00:18:58.630> more<00:18:58.810> sort<00:18:59.260> of 00:18:59.310 --> 00:18:59.320 align:start position:0% as we move to more and more sort of 00:18:59.320 --> 00:19:02.220 align:start position:0% as we move to more and more sort of wallets<00:18:59.830> doing<00:19:00.790> things<00:19:01.030> these<00:19:02.020> are<00:19:02.140> gonna 00:19:02.220 --> 00:19:02.230 align:start position:0% wallets doing things these are gonna 00:19:02.230 --> 00:19:05.130 align:start position:0% wallets doing things these are gonna have<00:19:02.410> to<00:19:02.500> be<00:19:02.590> supported<00:19:03.040> and<00:19:03.750> me<00:19:04.750> to<00:19:04.870> make<00:19:04.990> that 00:19:05.130 --> 00:19:05.140 align:start position:0% have to be supported and me to make that 00:19:05.140 --> 00:19:07.470 align:start position:0% have to be supported and me to make that easier<00:19:05.460> and<00:19:06.460> that<00:19:06.490> kind<00:19:06.940> of<00:19:06.970> flows<00:19:07.210> nicely 00:19:07.470 --> 00:19:07.480 align:start position:0% easier and that kind of flows nicely 00:19:07.480 --> 00:19:09.720 align:start position:0% easier and that kind of flows nicely actually<00:19:08.230> into<00:19:08.470> the<00:19:08.560> next<00:19:09.250> one<00:19:09.400> that<00:19:09.460> I<00:19:09.610> kind 00:19:09.720 --> 00:19:09.730 align:start position:0% actually into the next one that I kind 00:19:09.730 --> 00:19:10.950 align:start position:0% actually into the next one that I kind of<00:19:09.820> wanted<00:19:10.000> to<00:19:10.060> throw<00:19:10.300> out<00:19:10.570> there<00:19:10.720> in<00:19:10.840> less 00:19:10.950 --> 00:19:10.960 align:start position:0% of wanted to throw out there in less 00:19:10.960 --> 00:19:15.560 align:start position:0% of wanted to throw out there in less sorry<00:19:11.440> we're<00:19:11.590> gonna<00:19:11.680> go<00:19:12.070> okay<00:19:13.350> yeah<00:19:14.350> so<00:19:14.950> so 00:19:15.560 --> 00:19:15.570 align:start position:0% sorry we're gonna go okay yeah so so 00:19:15.570 --> 00:19:18.600 align:start position:0% sorry we're gonna go okay yeah so so alright<00:19:16.570> so<00:19:16.630> I<00:19:17.260> guess<00:19:18.190> the<00:19:18.400> next<00:19:18.520> question 00:19:18.600 --> 00:19:18.610 align:start position:0% alright so I guess the next question 00:19:18.610 --> 00:19:22.200 align:start position:0% alright so I guess the next question would<00:19:18.850> be<00:19:18.910> wallet<00:19:19.750> contract<00:19:20.320> or<00:19:20.790> like<00:19:21.790> scan 00:19:22.200 --> 00:19:22.210 align:start position:0% would be wallet contract or like scan 00:19:22.210 --> 00:19:23.970 align:start position:0% would be wallet contract or like scan individual<00:19:22.750> blocks<00:19:22.990> and<00:19:23.230> transactions<00:19:23.800> and 00:19:23.970 --> 00:19:23.980 align:start position:0% individual blocks and transactions and 00:19:23.980 --> 00:19:26.310 align:start position:0% individual blocks and transactions and invoke<00:19:24.190> transactions<00:19:24.820> which<00:19:25.000> one<00:19:25.290> which<00:19:26.290> one 00:19:26.310 --> 00:19:26.320 align:start position:0% invoke transactions which one which one 00:19:26.320 --> 00:19:26.910 align:start position:0% invoke transactions which one which one do<00:19:26.500> you<00:19:26.590> prefer 00:19:26.910 --> 00:19:26.920 align:start position:0% do you prefer 00:19:26.920 --> 00:19:31.440 align:start position:0% do you prefer yeah<00:19:29.100> it<00:19:30.100> is<00:19:30.310> there's<00:19:30.730> pros<00:19:30.970> and<00:19:31.000> cons<00:19:31.150> right 00:19:31.440 --> 00:19:31.450 align:start position:0% yeah it is there's pros and cons right 00:19:31.450 --> 00:19:33.570 align:start position:0% yeah it is there's pros and cons right so<00:19:31.750> either<00:19:32.080> you're<00:19:32.680> generating<00:19:33.370> a<00:19:33.550> new 00:19:33.570 --> 00:19:33.580 align:start position:0% so either you're generating a new 00:19:33.580 --> 00:19:35.490 align:start position:0% so either you're generating a new address<00:19:33.790> for<00:19:33.910> every<00:19:34.870> deposit<00:19:35.140> you<00:19:35.290> want<00:19:35.440> to 00:19:35.490 --> 00:19:35.500 align:start position:0% address for every deposit you want to 00:19:35.500 --> 00:19:37.620 align:start position:0% address for every deposit you want to take<00:19:35.680> as<00:19:35.830> an<00:19:35.950> exchange<00:19:36.160> and<00:19:36.700> you<00:19:37.240> have<00:19:37.420> to 00:19:37.620 --> 00:19:37.630 align:start position:0% take as an exchange and you have to 00:19:37.630 --> 00:19:39.420 align:start position:0% take as an exchange and you have to monitor<00:19:37.900> these<00:19:38.140> interventions<00:19:38.770> actions<00:19:39.100> very 00:19:39.420 --> 00:19:39.430 align:start position:0% monitor these interventions actions very 00:19:39.430 --> 00:19:44.190 align:start position:0% monitor these interventions actions very very<00:19:40.240> carefully<00:19:40.780> and<00:19:41.610> it's<00:19:42.630> theirs<00:19:43.630> then<00:19:43.900> you 00:19:44.190 --> 00:19:44.200 align:start position:0% very carefully and it's theirs then you 00:19:44.200 --> 00:19:46.110 align:start position:0% very carefully and it's theirs then you have<00:19:44.320> to<00:19:44.470> sweep<00:19:44.740> them<00:19:44.920> into<00:19:45.160> your<00:19:45.340> your<00:19:45.700> hot<00:19:45.970> or 00:19:46.110 --> 00:19:46.120 align:start position:0% have to sweep them into your your hot or 00:19:46.120 --> 00:19:48.930 align:start position:0% have to sweep them into your your hot or cold<00:19:46.270> wallets<00:19:46.750> and<00:19:47.080> it's<00:19:47.430> this<00:19:48.430> big<00:19:48.670> process 00:19:48.930 --> 00:19:48.940 align:start position:0% cold wallets and it's this big process 00:19:48.940 --> 00:19:50.740 align:start position:0% cold wallets and it's this big process or<00:19:49.360> even 00:19:50.740 --> 00:19:50.750 align:start position:0% or even 00:19:50.750 --> 00:19:53.080 align:start position:0% or even as<00:19:50.810> a<00:19:51.770> contract<00:19:52.310> side<00:19:52.520> of<00:19:52.670> things<00:19:52.850> if<00:19:53.000> you 00:19:53.080 --> 00:19:53.090 align:start position:0% as a contract side of things if you 00:19:53.090 --> 00:19:54.730 align:start position:0% as a contract side of things if you build<00:19:53.300> things<00:19:53.480> as<00:19:53.660> a<00:19:53.690> contract<00:19:54.110> I<00:19:54.260> think<00:19:54.290> bit 00:19:54.730 --> 00:19:54.740 align:start position:0% build things as a contract I think bit 00:19:54.740 --> 00:19:55.930 align:start position:0% build things as a contract I think bit tricks<00:19:54.950> does<00:19:55.130> this<00:19:55.280> and<00:19:55.520> maybe<00:19:55.640> some<00:19:55.820> other 00:19:55.930 --> 00:19:55.940 align:start position:0% tricks does this and maybe some other 00:19:55.940 --> 00:19:56.940 align:start position:0% tricks does this and maybe some other ones<00:19:56.150> too 00:19:56.940 --> 00:19:56.950 align:start position:0% ones too 00:19:56.950 --> 00:19:59.830 align:start position:0% ones too things<00:19:57.950> like<00:19:58.070> sweeping<00:19:58.640> gets<00:19:59.030> easier<00:19:59.390> you<00:19:59.420> can 00:19:59.830 --> 00:19:59.840 align:start position:0% things like sweeping gets easier you can 00:19:59.840 --> 00:20:02.680 align:start position:0% things like sweeping gets easier you can monitor<00:20:00.470> events<00:20:01.430> in<00:20:01.670> your<00:20:01.730> smart<00:20:01.970> contract<00:20:02.420> so 00:20:02.680 --> 00:20:02.690 align:start position:0% monitor events in your smart contract so 00:20:02.690 --> 00:20:04.480 align:start position:0% monitor events in your smart contract so internal<00:20:03.470> transactions<00:20:04.040> aren't<00:20:04.250> a<00:20:04.310> problem 00:20:04.480 --> 00:20:04.490 align:start position:0% internal transactions aren't a problem 00:20:04.490 --> 00:20:05.380 align:start position:0% internal transactions aren't a problem anymore 00:20:05.380 --> 00:20:05.390 align:start position:0% anymore 00:20:05.390 --> 00:20:08.980 align:start position:0% anymore but<00:20:05.870> now<00:20:06.290> you<00:20:06.350> have<00:20:06.500> increased<00:20:07.460> cost<00:20:07.730> for<00:20:07.990> each 00:20:08.980 --> 00:20:08.990 align:start position:0% but now you have increased cost for each 00:20:08.990 --> 00:20:10.960 align:start position:0% but now you have increased cost for each individual<00:20:09.500> customer<00:20:09.680> who<00:20:10.220> needs<00:20:10.670> to<00:20:10.940> a 00:20:10.960 --> 00:20:10.970 align:start position:0% individual customer who needs to a 00:20:10.970 --> 00:20:12.940 align:start position:0% individual customer who needs to a deposit<00:20:11.540> address<00:20:11.750> but<00:20:11.930> may<00:20:12.230> never<00:20:12.470> deposit 00:20:12.940 --> 00:20:12.950 align:start position:0% deposit address but may never deposit 00:20:12.950 --> 00:20:16.030 align:start position:0% deposit address but may never deposit any<00:20:13.310> ether<00:20:13.640> in<00:20:13.760> there<00:20:13.910> you<00:20:14.660> have<00:20:14.810> to<00:20:15.040> handle 00:20:16.030 --> 00:20:16.040 align:start position:0% any ether in there you have to handle 00:20:16.040 --> 00:20:19.120 align:start position:0% any ether in there you have to handle tokens<00:20:16.430> as<00:20:16.610> a<00:20:16.640> completely<00:20:17.210> separate<00:20:17.510> case<00:20:18.130> it 00:20:19.120 --> 00:20:19.130 align:start position:0% tokens as a completely separate case it 00:20:19.130 --> 00:20:21.850 align:start position:0% tokens as a completely separate case it definitely<00:20:20.140> complicates<00:20:21.140> things<00:20:21.230> and<00:20:21.680> there 00:20:21.850 --> 00:20:21.860 align:start position:0% definitely complicates things and there 00:20:21.860 --> 00:20:23.700 align:start position:0% definitely complicates things and there is<00:20:21.950> that<00:20:22.100> trade-off<00:20:22.310> one<00:20:23.270> of<00:20:23.360> the<00:20:23.420> things<00:20:23.540> I 00:20:23.700 --> 00:20:23.710 align:start position:0% is that trade-off one of the things I 00:20:23.710 --> 00:20:26.080 align:start position:0% is that trade-off one of the things I don't<00:20:24.710> particularly<00:20:25.040> like<00:20:25.250> about<00:20:25.310> wallet 00:20:26.080 --> 00:20:26.090 align:start position:0% don't particularly like about wallet 00:20:26.090 --> 00:20:27.880 align:start position:0% don't particularly like about wallet contracts<00:20:26.510> especially<00:20:27.200> if<00:20:27.620> it's<00:20:27.740> like<00:20:27.860> a 00:20:27.880 --> 00:20:27.890 align:start position:0% contracts especially if it's like a 00:20:27.890 --> 00:20:30.850 align:start position:0% contracts especially if it's like a single<00:20:28.160> one<00:20:28.400> is<00:20:29.330> that<00:20:29.720> it<00:20:29.990> sort<00:20:30.140> of<00:20:30.260> it<00:20:30.470> puts 00:20:30.850 --> 00:20:30.860 align:start position:0% single one is that it sort of it puts 00:20:30.860 --> 00:20:32.110 align:start position:0% single one is that it sort of it puts all<00:20:31.070> your<00:20:31.280> transaction<00:20:31.700> history<00:20:31.730> in<00:20:31.970> one 00:20:32.110 --> 00:20:32.120 align:start position:0% all your transaction history in one 00:20:32.120 --> 00:20:33.970 align:start position:0% all your transaction history in one place<00:20:32.360> privacy<00:20:33.200> is<00:20:33.260> a<00:20:33.320> really<00:20:33.530> important 00:20:33.970 --> 00:20:33.980 align:start position:0% place privacy is a really important 00:20:33.980 --> 00:20:35.580 align:start position:0% place privacy is a really important thing<00:20:34.010> and<00:20:34.190> we<00:20:34.340> want<00:20:34.430> to<00:20:34.580> have<00:20:34.700> and<00:20:35.000> so 00:20:35.580 --> 00:20:35.590 align:start position:0% thing and we want to have and so 00:20:35.590 --> 00:20:37.510 align:start position:0% thing and we want to have and so contracts<00:20:36.590> especially<00:20:36.740> the<00:20:37.100> sitting<00:20:37.310> because 00:20:37.510 --> 00:20:37.520 align:start position:0% contracts especially the sitting because 00:20:37.520 --> 00:20:38.680 align:start position:0% contracts especially the sitting because of<00:20:37.670> the<00:20:37.760> cost<00:20:37.970> like<00:20:38.300> you're<00:20:38.450> going<00:20:38.570> to<00:20:38.630> be 00:20:38.680 --> 00:20:38.690 align:start position:0% of the cost like you're going to be 00:20:38.690 --> 00:20:40.510 align:start position:0% of the cost like you're going to be incentivized<00:20:39.230> as<00:20:39.470> any<00:20:39.710> sort<00:20:39.920> of<00:20:40.010> business<00:20:40.160> to 00:20:40.510 --> 00:20:40.520 align:start position:0% incentivized as any sort of business to 00:20:40.520 --> 00:20:42.760 align:start position:0% incentivized as any sort of business to do<00:20:41.030> sort<00:20:41.270> of<00:20:41.360> one<00:20:41.600> right<00:20:42.260> unless<00:20:42.470> there's<00:20:42.680> some 00:20:42.760 --> 00:20:42.770 align:start position:0% do sort of one right unless there's some 00:20:42.770 --> 00:20:43.990 align:start position:0% do sort of one right unless there's some extra<00:20:43.010> cost<00:20:43.220> or<00:20:43.400> something<00:20:43.640> for<00:20:43.790> you<00:20:43.880> know<00:20:43.970> a 00:20:43.990 --> 00:20:44.000 align:start position:0% extra cost or something for you know a 00:20:44.000 --> 00:20:45.760 align:start position:0% extra cost or something for you know a new<00:20:44.210> address<00:20:44.360> and<00:20:44.720> if<00:20:44.810> you<00:20:44.870> have<00:20:44.960> one<00:20:45.140> now<00:20:45.500> all 00:20:45.760 --> 00:20:45.770 align:start position:0% new address and if you have one now all 00:20:45.770 --> 00:20:47.920 align:start position:0% new address and if you have one now all of<00:20:45.950> your<00:20:46.040> history<00:20:46.130> to<00:20:46.550> that<00:20:46.690> exchange<00:20:47.690> is<00:20:47.810> in 00:20:47.920 --> 00:20:47.930 align:start position:0% of your history to that exchange is in 00:20:47.930 --> 00:20:49.540 align:start position:0% of your history to that exchange is in one<00:20:48.080> place<00:20:48.320> and<00:20:48.830> so<00:20:48.950> anybody<00:20:49.250> wants<00:20:49.400> to<00:20:49.460> see 00:20:49.540 --> 00:20:49.550 align:start position:0% one place and so anybody wants to see 00:20:49.550 --> 00:20:50.740 align:start position:0% one place and so anybody wants to see how<00:20:49.640> much<00:20:49.790> ether<00:20:50.030> you<00:20:50.240> had<00:20:50.390> added<00:20:50.450> how<00:20:50.630> much 00:20:50.740 --> 00:20:50.750 align:start position:0% how much ether you had added how much 00:20:50.750 --> 00:20:52.180 align:start position:0% how much ether you had added how much you<00:20:50.870> sent<00:20:51.050> there<00:20:51.200> they<00:20:51.320> cannot<00:20:51.560> tell<00:20:51.860> that<00:20:52.040> it 00:20:52.180 --> 00:20:52.190 align:start position:0% you sent there they cannot tell that it 00:20:52.190 --> 00:20:52.990 align:start position:0% you sent there they cannot tell that it may<00:20:52.280> be<00:20:52.340> how<00:20:52.460> much<00:20:52.550> you<00:20:52.670> have<00:20:52.790> in<00:20:52.820> that 00:20:52.990 --> 00:20:53.000 align:start position:0% may be how much you have in that 00:20:53.000 --> 00:20:54.310 align:start position:0% may be how much you have in that exchange<00:20:53.210> maybe<00:20:53.570> that<00:20:53.750> makes<00:20:53.900> them<00:20:54.050> more<00:20:54.080> of<00:20:54.260> a 00:20:54.310 --> 00:20:54.320 align:start position:0% exchange maybe that makes them more of a 00:20:54.320 --> 00:20:56.320 align:start position:0% exchange maybe that makes them more of a target<00:20:54.710> if<00:20:55.310> they<00:20:55.460> follow<00:20:55.670> a<00:20:55.760> pattern<00:20:56.000> like 00:20:56.320 --> 00:20:56.330 align:start position:0% target if they follow a pattern like 00:20:56.330 --> 00:20:57.850 align:start position:0% target if they follow a pattern like things<00:20:56.540> like<00:20:56.660> the<00:20:56.810> trucks<00:20:57.050> as<00:20:57.200> contracts<00:20:57.650> like 00:20:57.850 --> 00:20:57.860 align:start position:0% things like the trucks as contracts like 00:20:57.860 --> 00:20:59.800 align:start position:0% things like the trucks as contracts like you<00:20:58.310> can<00:20:58.460> detect<00:20:58.880> them<00:20:59.060> easily<00:20:59.450> and<00:20:59.630> so<00:20:59.750> you 00:20:59.800 --> 00:20:59.810 align:start position:0% you can detect them easily and so you 00:20:59.810 --> 00:21:01.480 align:start position:0% you can detect them easily and so you can<00:20:59.990> easily<00:21:00.320> see<00:21:00.500> how<00:21:00.530> much<00:21:00.950> of<00:21:01.100> it<00:21:01.190> checks<00:21:01.340> is 00:21:01.480 --> 00:21:01.490 align:start position:0% can easily see how much of it checks is 00:21:01.490 --> 00:21:03.820 align:start position:0% can easily see how much of it checks is receiving<00:21:01.970> through<00:21:02.570> that<00:21:02.870> pattern<00:21:03.260> or<00:21:03.710> is 00:21:03.820 --> 00:21:03.830 align:start position:0% receiving through that pattern or is 00:21:03.830 --> 00:21:05.770 align:start position:0% receiving through that pattern or is like<00:21:03.950> the<00:21:04.040> way<00:21:04.160> that<00:21:04.460> we<00:21:04.520> do<00:21:04.820> it<00:21:05.000> which<00:21:05.480> has 00:21:05.770 --> 00:21:05.780 align:start position:0% like the way that we do it which has 00:21:05.780 --> 00:21:07.540 align:start position:0% like the way that we do it which has some<00:21:05.990> other<00:21:06.170> downsides<00:21:06.710> and<00:21:06.920> cost<00:21:07.100> is<00:21:07.340> that<00:21:07.430> we 00:21:07.540 --> 00:21:07.550 align:start position:0% some other downsides and cost is that we 00:21:07.550 --> 00:21:09.720 align:start position:0% some other downsides and cost is that we generate<00:21:07.880> new<00:21:08.120> addresses<00:21:08.480> just<00:21:08.870> all<00:21:08.990> the<00:21:09.470> time 00:21:09.720 --> 00:21:09.730 align:start position:0% generate new addresses just all the time 00:21:09.730 --> 00:21:11.830 align:start position:0% generate new addresses just all the time almost<00:21:10.730> anytime<00:21:11.210> you<00:21:11.360> get<00:21:11.450> an<00:21:11.540> address<00:21:11.750> from 00:21:11.830 --> 00:21:11.840 align:start position:0% almost anytime you get an address from 00:21:11.840 --> 00:21:13.060 align:start position:0% almost anytime you get an address from us<00:21:12.020> it's<00:21:12.170> a<00:21:12.230> brand<00:21:12.470> new<00:21:12.530> one<00:21:12.680> that's<00:21:12.830> never 00:21:13.060 --> 00:21:13.070 align:start position:0% us it's a brand new one that's never 00:21:13.070 --> 00:21:14.890 align:start position:0% us it's a brand new one that's never been<00:21:13.250> seen<00:21:13.400> before<00:21:13.580> if<00:21:14.000> we<00:21:14.090> send<00:21:14.300> transactions 00:21:14.890 --> 00:21:14.900 align:start position:0% been seen before if we send transactions 00:21:14.900 --> 00:21:16.090 align:start position:0% been seen before if we send transactions it's<00:21:15.020> coming<00:21:15.290> from<00:21:15.380> a<00:21:15.530> new<00:21:15.620> mattress<00:21:15.800> it's 00:21:16.090 --> 00:21:16.100 align:start position:0% it's coming from a new mattress it's 00:21:16.100 --> 00:21:17.080 align:start position:0% it's coming from a new mattress it's never<00:21:16.280> been<00:21:16.400> seen<00:21:16.580> before 00:21:17.080 --> 00:21:17.090 align:start position:0% never been seen before 00:21:17.090 --> 00:21:19.390 align:start position:0% never been seen before ok<00:21:17.960> that<00:21:18.140> has<00:21:18.230> some<00:21:18.440> things<00:21:18.830> of<00:21:19.010> just<00:21:19.100> having<00:21:19.370> a 00:21:19.390 --> 00:21:19.400 align:start position:0% ok that has some things of just having a 00:21:19.400 --> 00:21:21.130 align:start position:0% ok that has some things of just having a lot<00:21:19.460> of<00:21:19.520> addresses<00:21:19.970> its<00:21:20.090> own<00:21:20.330> problem<00:21:20.780> and<00:21:20.960> I 00:21:21.130 --> 00:21:21.140 align:start position:0% lot of addresses its own problem and I 00:21:21.140 --> 00:21:23.110 align:start position:0% lot of addresses its own problem and I think<00:21:21.830> we<00:21:21.920> might<00:21:22.100> get<00:21:22.220> it<00:21:22.310> up<00:21:22.430> later<00:21:22.700> to<00:21:22.910> about 00:21:23.110 --> 00:21:23.120 align:start position:0% think we might get it up later to about 00:21:23.120 --> 00:21:24.460 align:start position:0% think we might get it up later to about you<00:21:23.240> know<00:21:23.330> sort<00:21:23.480> of<00:21:23.570> batching<00:21:23.900> transactions 00:21:24.460 --> 00:21:24.470 align:start position:0% you know sort of batching transactions 00:21:24.470 --> 00:21:25.780 align:start position:0% you know sort of batching transactions and<00:21:24.680> stuff<00:21:24.800> and<00:21:24.920> doing<00:21:25.010> a<00:21:25.100> lot<00:21:25.250> of<00:21:25.370> sins<00:21:25.550> you 00:21:25.780 --> 00:21:25.790 align:start position:0% and stuff and doing a lot of sins you 00:21:25.790 --> 00:21:27.760 align:start position:0% and stuff and doing a lot of sins you have<00:21:26.000> some<00:21:26.360> interesting<00:21:27.200> challenges<00:21:27.380> there 00:21:27.760 --> 00:21:27.770 align:start position:0% have some interesting challenges there 00:21:27.770 --> 00:21:30.100 align:start position:0% have some interesting challenges there in<00:21:28.070> certain<00:21:28.340> transactions<00:21:28.880> but<00:21:29.090> I<00:21:29.360> think<00:21:29.960> like 00:21:30.100 --> 00:21:30.110 align:start position:0% in certain transactions but I think like 00:21:30.110 --> 00:21:31.990 align:start position:0% in certain transactions but I think like I<00:21:30.410> don't<00:21:30.590> like<00:21:30.920> this<00:21:31.100> idea<00:21:31.310> of<00:21:31.580> just<00:21:31.880> like 00:21:31.990 --> 00:21:32.000 align:start position:0% I don't like this idea of just like 00:21:32.000 --> 00:21:33.970 align:start position:0% I don't like this idea of just like linking<00:21:32.600> everything<00:21:32.930> together<00:21:33.260> all<00:21:33.710> of<00:21:33.890> your 00:21:33.970 --> 00:21:33.980 align:start position:0% linking everything together all of your 00:21:33.980 --> 00:21:35.530 align:start position:0% linking everything together all of your activity<00:21:34.400> in<00:21:34.460> one<00:21:34.550> place<00:21:34.820> especially<00:21:35.270> if 00:21:35.530 --> 00:21:35.540 align:start position:0% activity in one place especially if 00:21:35.540 --> 00:21:37.720 align:start position:0% activity in one place especially if you're<00:21:35.660> gonna<00:21:35.750> like<00:21:35.990> send<00:21:36.230> from<00:21:36.530> there<00:21:36.680> too<00:21:36.950> so 00:21:37.720 --> 00:21:37.730 align:start position:0% you're gonna like send from there too so 00:21:37.730 --> 00:21:41.160 align:start position:0% you're gonna like send from there too so I<00:21:38.540> think<00:21:38.870> in<00:21:39.170> terms<00:21:39.350> of<00:21:39.620> having<00:21:40.100> one<00:21:40.340> address 00:21:41.160 --> 00:21:41.170 align:start position:0% I think in terms of having one address 00:21:41.170 --> 00:21:42.310 align:start position:0% I think in terms of having one address client 00:21:42.310 --> 00:21:42.320 align:start position:0% client 00:21:42.320 --> 00:21:45.700 align:start position:0% client I<00:21:42.350> mean<00:21:42.560> per<00:21:42.950> customer<00:21:43.160> exchange<00:21:44.530> pretty<00:21:45.530> much 00:21:45.700 --> 00:21:45.710 align:start position:0% I mean per customer exchange pretty much 00:21:45.710 --> 00:21:48.240 align:start position:0% I mean per customer exchange pretty much many<00:21:46.250> exchanges<00:21:46.490> are<00:21:46.760> used<00:21:46.910> to<00:21:47.000> this<00:21:47.090> concept 00:21:48.240 --> 00:21:48.250 align:start position:0% many exchanges are used to this concept 00:21:48.250 --> 00:21:50.560 align:start position:0% many exchanges are used to this concept from<00:21:49.250> you<00:21:49.460> know<00:21:49.550> a<00:21:49.580> variety<00:21:49.850> of<00:21:50.060> other<00:21:50.270> digital 00:21:50.560 --> 00:21:50.570 align:start position:0% from you know a variety of other digital 00:21:50.570 --> 00:21:53.850 align:start position:0% from you know a variety of other digital currencies<00:21:50.990> and<00:21:51.500> so<00:21:52.100> I<00:21:52.580> think<00:21:52.820> on<00:21:53.030> that<00:21:53.090> matter 00:21:53.850 --> 00:21:53.860 align:start position:0% currencies and so I think on that matter 00:21:53.860 --> 00:21:56.620 align:start position:0% currencies and so I think on that matter what<00:21:54.860> we're<00:21:55.250> doing<00:21:55.460> is<00:21:55.610> whether<00:21:56.390> or<00:21:56.600> not 00:21:56.620 --> 00:21:56.630 align:start position:0% what we're doing is whether or not 00:21:56.630 --> 00:21:59.290 align:start position:0% what we're doing is whether or not you're<00:21:57.140> a<00:21:57.170> contract<00:21:57.650> or<00:21:57.800> address<00:21:58.250> you<00:21:59.120> gotta 00:21:59.290 --> 00:21:59.300 align:start position:0% you're a contract or address you gotta 00:21:59.300 --> 00:22:01.900 align:start position:0% you're a contract or address you gotta have<00:21:59.510> one<00:21:59.590> one<00:22:00.590> address<00:22:00.890> you<00:22:01.370> know<00:22:01.490> one<00:22:01.670> one 00:22:01.900 --> 00:22:01.910 align:start position:0% have one one address you know one one 00:22:01.910 --> 00:22:04.060 align:start position:0% have one one address you know one one address<00:22:02.179> per<00:22:02.500> downline 00:22:04.060 --> 00:22:04.070 align:start position:0% address per downline 00:22:04.070 --> 00:22:06.219 align:start position:0% address per downline you<00:22:04.190> know<00:22:04.279> customer<00:22:04.639> deposit<00:22:04.999> a<00:22:05.029> dress<00:22:05.179> and<00:22:05.629> so 00:22:06.219 --> 00:22:06.229 align:start position:0% you know customer deposit a dress and so 00:22:06.229 --> 00:22:07.930 align:start position:0% you know customer deposit a dress and so what<00:22:06.679> happens<00:22:06.979> in<00:22:07.129> the<00:22:07.220> end<00:22:07.249> is<00:22:07.460> that<00:22:07.519> when<00:22:07.850> you 00:22:07.930 --> 00:22:07.940 align:start position:0% what happens in the end is that when you 00:22:07.940 --> 00:22:10.149 align:start position:0% what happens in the end is that when you try<00:22:08.090> and<00:22:08.210> do<00:22:08.389> that<00:22:08.509> with<00:22:08.570> contracts<00:22:09.289> you<00:22:09.979> are 00:22:10.149 --> 00:22:10.159 align:start position:0% try and do that with contracts you are 00:22:10.159 --> 00:22:12.489 align:start position:0% try and do that with contracts you are you're<00:22:10.489> probably<00:22:10.700> going<00:22:10.909> to<00:22:10.999> be<00:22:11.090> using<00:22:11.499> some 00:22:12.489 --> 00:22:12.499 align:start position:0% you're probably going to be using some 00:22:12.499 --> 00:22:14.609 align:start position:0% you're probably going to be using some kind<00:22:12.619> of<00:22:12.739> forward<00:22:12.979> or<00:22:13.159> contract<00:22:13.549> in<00:22:14.179> which 00:22:14.609 --> 00:22:14.619 align:start position:0% kind of forward or contract in which 00:22:14.619 --> 00:22:18.039 align:start position:0% kind of forward or contract in which what<00:22:15.619> it<00:22:15.950> is<00:22:16.039> is<00:22:16.190> a<00:22:16.220> really<00:22:16.429> small<00:22:16.789> shim<00:22:17.090> that 00:22:18.039 --> 00:22:18.049 align:start position:0% what it is is a really small shim that 00:22:18.049 --> 00:22:21.759 align:start position:0% what it is is a really small shim that forwards<00:22:18.830> the<00:22:18.979> money<00:22:19.159> from<00:22:20.229> this<00:22:21.229> unique 00:22:21.759 --> 00:22:21.769 align:start position:0% forwards the money from this unique 00:22:21.769 --> 00:22:23.830 align:start position:0% forwards the money from this unique deposit<00:22:22.279> address<00:22:22.489> for<00:22:22.700> each<00:22:22.789> customer<00:22:23.029> into 00:22:23.830 --> 00:22:23.840 align:start position:0% deposit address for each customer into 00:22:23.840 --> 00:22:29.950 align:start position:0% deposit address for each customer into some<00:22:24.460> some<00:22:25.460> main<00:22:26.169> and<00:22:28.450> you<00:22:29.450> know<00:22:29.539> sometimes<00:22:29.749> a 00:22:29.950 --> 00:22:29.960 align:start position:0% some some main and you know sometimes a 00:22:29.960 --> 00:22:33.009 align:start position:0% some some main and you know sometimes a challenge<00:22:30.259> with<00:22:30.350> that<00:22:30.379> is<00:22:30.529> is<00:22:31.720> with<00:22:32.720> with<00:22:32.899> us 00:22:33.009 --> 00:22:33.019 align:start position:0% challenge with that is is with with us 00:22:33.019 --> 00:22:34.499 align:start position:0% challenge with that is is with with us at<00:22:33.169> least<00:22:33.289> we<00:22:33.470> wanted<00:22:33.679> to<00:22:33.769> be<00:22:33.889> a<00:22:33.919> multi<00:22:34.249> sig 00:22:34.499 --> 00:22:34.509 align:start position:0% at least we wanted to be a multi sig 00:22:34.509 --> 00:22:37.810 align:start position:0% at least we wanted to be a multi sig platform<00:22:35.509> and<00:22:35.690> so<00:22:36.409> we<00:22:36.559> wanted<00:22:36.830> you<00:22:37.489> know<00:22:37.580> all 00:22:37.810 --> 00:22:37.820 align:start position:0% platform and so we wanted you know all 00:22:37.820 --> 00:22:40.269 align:start position:0% platform and so we wanted you know all all<00:22:38.450> our<00:22:38.570> wallets<00:22:38.869> and<00:22:38.989> contracts<00:22:39.379> to<00:22:39.470> be<00:22:39.619> you 00:22:40.269 --> 00:22:40.279 align:start position:0% all our wallets and contracts to be you 00:22:40.279 --> 00:22:42.099 align:start position:0% all our wallets and contracts to be you know<00:22:40.399> not<00:22:40.609> controlled<00:22:41.059> by<00:22:41.090> a<00:22:41.179> single<00:22:41.419> key<00:22:41.690> and 00:22:42.099 --> 00:22:42.109 align:start position:0% know not controlled by a single key and 00:22:42.109 --> 00:22:43.839 align:start position:0% know not controlled by a single key and that<00:22:42.710> was<00:22:42.859> one<00:22:43.009> of<00:22:43.039> the<00:22:43.159> requirements<00:22:43.669> that<00:22:43.700> we 00:22:43.839 --> 00:22:43.849 align:start position:0% that was one of the requirements that we 00:22:43.849 --> 00:22:46.029 align:start position:0% that was one of the requirements that we set<00:22:43.999> out<00:22:44.090> to<00:22:44.419> fulfill<00:22:44.720> and<00:22:45.109> that's<00:22:45.259> why<00:22:45.409> we<00:22:45.559> did 00:22:46.029 --> 00:22:46.039 align:start position:0% set out to fulfill and that's why we did 00:22:46.039 --> 00:22:50.830 align:start position:0% set out to fulfill and that's why we did it<00:22:46.159> that<00:22:46.309> way<00:22:46.489> I<00:22:47.590> think<00:22:48.590> that<00:22:48.940> I<00:22:49.940> mean<00:22:50.359> one<00:22:50.599> one 00:22:50.830 --> 00:22:50.840 align:start position:0% it that way I think that I mean one one 00:22:50.840 --> 00:22:53.680 align:start position:0% it that way I think that I mean one one one<00:22:51.080> advantage<00:22:51.470> of<00:22:51.619> that<00:22:51.769> for<00:22:52.159> for<00:22:52.669> us<00:22:52.789> that<00:22:53.090> I 00:22:53.680 --> 00:22:53.690 align:start position:0% one advantage of that for for us that I 00:22:53.690 --> 00:22:55.119 align:start position:0% one advantage of that for for us that I guess<00:22:54.349> I<00:22:54.379> haven't<00:22:54.529> talked<00:22:54.739> about<00:22:54.830> is<00:22:55.099> that 00:22:55.119 --> 00:22:55.129 align:start position:0% guess I haven't talked about is that 00:22:55.129 --> 00:22:58.570 align:start position:0% guess I haven't talked about is that with<00:22:55.519> with<00:22:55.879> contracts<00:22:56.349> you're<00:22:57.489> you<00:22:58.489> know 00:22:58.570 --> 00:22:58.580 align:start position:0% with with contracts you're you know 00:22:58.580 --> 00:23:00.549 align:start position:0% with with contracts you're you know instead<00:22:59.450> of<00:22:59.570> looking<00:23:00.109> at<00:23:00.200> the<00:23:00.289> internal 00:23:00.549 --> 00:23:00.559 align:start position:0% instead of looking at the internal 00:23:00.559 --> 00:23:02.349 align:start position:0% instead of looking at the internal transactions<00:23:01.099> by<00:23:01.609> yourself<00:23:01.970> by<00:23:02.059> looking<00:23:02.149> at 00:23:02.349 --> 00:23:02.359 align:start position:0% transactions by yourself by looking at 00:23:02.359 --> 00:23:04.299 align:start position:0% transactions by yourself by looking at transaction<00:23:02.749> receipts<00:23:03.080> you<00:23:03.739> can<00:23:03.919> look<00:23:04.129> at<00:23:04.220> the 00:23:04.299 --> 00:23:04.309 align:start position:0% transaction receipts you can look at the 00:23:04.309 --> 00:23:05.919 align:start position:0% transaction receipts you can look at the events<00:23:04.639> because<00:23:04.970> you<00:23:05.149> can<00:23:05.269> get<00:23:05.389> contracts<00:23:05.809> to 00:23:05.919 --> 00:23:05.929 align:start position:0% events because you can get contracts to 00:23:05.929 --> 00:23:09.009 align:start position:0% events because you can get contracts to file<00:23:06.139> events<00:23:06.499> and<00:23:07.210> and<00:23:08.210> actually<00:23:08.720> you<00:23:08.779> can<00:23:08.869> do 00:23:09.009 --> 00:23:09.019 align:start position:0% file events and and actually you can do 00:23:09.019 --> 00:23:10.869 align:start position:0% file events and and actually you can do it<00:23:09.139> within<00:23:09.409> the<00:23:09.619> 21,000<00:23:10.220> guests<00:23:10.369> with<00:23:10.519> it 00:23:10.869 --> 00:23:10.879 align:start position:0% it within the 21,000 guests with it 00:23:10.879 --> 00:23:12.279 align:start position:0% it within the 21,000 guests with it you<00:23:11.210> can<00:23:11.359> get<00:23:11.479> one<00:23:11.659> event<00:23:11.899> or<00:23:11.960> something<00:23:12.229> like 00:23:12.279 --> 00:23:12.289 align:start position:0% you can get one event or something like 00:23:12.289 --> 00:23:15.249 align:start position:0% you can get one event or something like that<00:23:12.349> badly<00:23:13.009> enough<00:23:13.450> and<00:23:14.450> then<00:23:14.779> you<00:23:14.809> can<00:23:15.019> you 00:23:15.249 --> 00:23:15.259 align:start position:0% that badly enough and then you can you 00:23:15.259 --> 00:23:17.139 align:start position:0% that badly enough and then you can you can<00:23:15.409> code<00:23:15.769> your<00:23:15.799> indexes<00:23:16.489> to<00:23:16.669> pick<00:23:16.849> up<00:23:16.999> those 00:23:17.139 --> 00:23:17.149 align:start position:0% can code your indexes to pick up those 00:23:17.149 --> 00:23:19.989 align:start position:0% can code your indexes to pick up those those<00:23:17.749> events<00:23:18.139> and<00:23:18.470> use<00:23:19.129> them<00:23:19.340> for<00:23:19.369> you<00:23:19.909> know 00:23:19.989 --> 00:23:19.999 align:start position:0% those events and use them for you know 00:23:19.999 --> 00:23:23.349 align:start position:0% those events and use them for you know deposits<00:23:21.070> so<00:23:22.070> so<00:23:22.729> there<00:23:22.940> is<00:23:23.059> one<00:23:23.210> advantage 00:23:23.349 --> 00:23:23.359 align:start position:0% deposits so so there is one advantage 00:23:23.359 --> 00:23:25.419 align:start position:0% deposits so so there is one advantage there<00:23:23.809> the<00:23:23.929> disadvantage<00:23:24.409> is<00:23:24.529> you<00:23:24.830> know<00:23:25.009> pay 00:23:25.419 --> 00:23:25.429 align:start position:0% there the disadvantage is you know pay 00:23:25.429 --> 00:23:27.940 align:start position:0% there the disadvantage is you know pay you<00:23:25.489> have<00:23:25.789> to<00:23:25.879> pay<00:23:25.999> the<00:23:26.149> gas<00:23:26.269> to<00:23:26.960> to<00:23:27.470> deploy<00:23:27.799> the 00:23:27.940 --> 00:23:27.950 align:start position:0% you have to pay the gas to to deploy the 00:23:27.950 --> 00:23:31.229 align:start position:0% you have to pay the gas to to deploy the contract<00:23:28.840> which<00:23:29.840> which<00:23:30.229> can<00:23:30.440> be<00:23:30.559> very<00:23:30.739> costly 00:23:31.229 --> 00:23:31.239 align:start position:0% contract which which can be very costly 00:23:31.239 --> 00:23:34.029 align:start position:0% contract which which can be very costly well<00:23:32.239> I<00:23:32.419> mean<00:23:32.659> I<00:23:32.749> think<00:23:32.809> there<00:23:33.019> are<00:23:33.139> some<00:23:33.409> IPS 00:23:34.029 --> 00:23:34.039 align:start position:0% well I mean I think there are some IPS 00:23:34.039 --> 00:23:36.969 align:start position:0% well I mean I think there are some IPS that<00:23:34.129> are<00:23:34.309> out<00:23:35.149> there<00:23:35.379> not<00:23:36.379> too<00:23:36.529> far<00:23:36.739> away<00:23:36.859> from 00:23:36.969 --> 00:23:36.979 align:start position:0% that are out there not too far away from 00:23:36.979 --> 00:23:40.210 align:start position:0% that are out there not too far away from being<00:23:37.369> minded<00:23:37.779> that<00:23:38.779> will<00:23:39.200> allow<00:23:39.769> us<00:23:39.950> to<00:23:39.979> do 00:23:40.210 --> 00:23:40.220 align:start position:0% being minded that will allow us to do 00:23:40.220 --> 00:23:42.460 align:start position:0% being minded that will allow us to do you<00:23:40.729> know<00:23:40.820> basically<00:23:41.299> paid<00:23:41.779> to<00:23:41.899> script<00:23:42.139> -<00:23:42.289> in 00:23:42.460 --> 00:23:42.470 align:start position:0% you know basically paid to script - in 00:23:42.470 --> 00:23:44.409 align:start position:0% you know basically paid to script - in other<00:23:42.590> words<00:23:42.679> you<00:23:43.429> can<00:23:43.580> pay<00:23:43.789> to<00:23:43.849> an<00:23:44.119> address 00:23:44.409 --> 00:23:44.419 align:start position:0% other words you can pay to an address 00:23:44.419 --> 00:23:46.529 align:start position:0% other words you can pay to an address which<00:23:45.229> is<00:23:45.259> a<00:23:45.379> contract<00:23:45.769> address<00:23:46.039> without 00:23:46.529 --> 00:23:46.539 align:start position:0% which is a contract address without 00:23:46.539 --> 00:23:49.359 align:start position:0% which is a contract address without actually<00:23:47.539> it<00:23:47.690> having<00:23:47.960> been<00:23:48.139> deployed<00:23:48.739> yet<00:23:49.070> and 00:23:49.359 --> 00:23:49.369 align:start position:0% actually it having been deployed yet and 00:23:49.369 --> 00:23:52.389 align:start position:0% actually it having been deployed yet and then<00:23:49.970> someone<00:23:50.450> else<00:23:50.539> can<00:23:50.840> then<00:23:51.019> deploy<00:23:51.830> after 00:23:52.389 --> 00:23:52.399 align:start position:0% then someone else can then deploy after 00:23:52.399 --> 00:23:53.649 align:start position:0% then someone else can then deploy after they<00:23:52.519> see<00:23:52.729> that<00:23:52.849> okay<00:23:53.210> someone<00:23:53.450> actually 00:23:53.649 --> 00:23:53.659 align:start position:0% they see that okay someone actually 00:23:53.659 --> 00:23:55.269 align:start position:0% they see that okay someone actually deposited<00:23:54.080> there<00:23:54.229> and<00:23:54.499> this<00:23:54.950> is<00:23:55.039> really 00:23:55.269 --> 00:23:55.279 align:start position:0% deposited there and this is really 00:23:55.279 --> 00:23:56.830 align:start position:0% deposited there and this is really useful<00:23:55.399> in<00:23:55.729> the<00:23:55.820> case<00:23:55.999> of<00:23:56.149> when<00:23:56.269> exchange<00:23:56.629> that 00:23:56.830 --> 00:23:56.840 align:start position:0% useful in the case of when exchange that 00:23:56.840 --> 00:23:59.440 align:start position:0% useful in the case of when exchange that has<00:23:57.019> a<00:23:57.289> hundred<00:23:57.950> thousand<00:23:58.309> users<00:23:58.879> and<00:23:59.239> only 00:23:59.440 --> 00:23:59.450 align:start position:0% has a hundred thousand users and only 00:23:59.450 --> 00:24:02.919 align:start position:0% has a hundred thousand users and only fifty<00:24:00.289> thousand<00:24:00.619> may<00:24:00.710> use<00:24:00.919> s<00:24:01.629> so<00:24:02.629> you<00:24:02.690> only 00:24:02.919 --> 00:24:02.929 align:start position:0% fifty thousand may use s so you only 00:24:02.929 --> 00:24:05.999 align:start position:0% fifty thousand may use s so you only need<00:24:03.019> to<00:24:03.320> set<00:24:03.499> up<00:24:03.529> the<00:24:03.739> address<00:24:03.979> after<00:24:04.340> they 00:24:05.999 --> 00:24:06.009 align:start position:0% need to set up the address after they 00:24:06.009 --> 00:24:08.950 align:start position:0% need to set up the address after they doing<00:24:07.009> there<00:24:07.220> I<00:24:07.369> think<00:24:07.639> about<00:24:07.820> like<00:24:08.059> the<00:24:08.779> gas 00:24:08.950 --> 00:24:08.960 align:start position:0% doing there I think about like the gas 00:24:08.960 --> 00:24:10.899 align:start position:0% doing there I think about like the gas limit<00:24:09.200> stuff<00:24:09.529> right<00:24:10.220> so<00:24:10.279> this<00:24:10.460> is<00:24:10.580> the<00:24:10.700> thing 00:24:10.899 --> 00:24:10.909 align:start position:0% limit stuff right so this is the thing 00:24:10.909 --> 00:24:12.099 align:start position:0% limit stuff right so this is the thing that<00:24:10.940> different<00:24:11.389> exchanges<00:24:11.749> have<00:24:11.869> to<00:24:11.960> make 00:24:12.099 --> 00:24:12.109 align:start position:0% that different exchanges have to make 00:24:12.109 --> 00:24:14.169 align:start position:0% that different exchanges have to make different<00:24:12.440> decisions<00:24:12.649> on<00:24:13.039> of<00:24:13.460> customers<00:24:14.029> sort 00:24:14.169 --> 00:24:14.179 align:start position:0% different decisions on of customers sort 00:24:14.179 --> 00:24:16.419 align:start position:0% different decisions on of customers sort of<00:24:14.269> sending<00:24:14.629> aetherium<00:24:15.289> somewhere<00:24:15.619> and<00:24:15.799> if<00:24:16.309> it 00:24:16.419 --> 00:24:16.429 align:start position:0% of sending aetherium somewhere and if it 00:24:16.429 --> 00:24:17.800 align:start position:0% of sending aetherium somewhere and if it might<00:24:16.609> go<00:24:16.730> to<00:24:16.789> a<00:24:16.879> smart<00:24:17.179> contract 00:24:17.800 --> 00:24:17.810 align:start position:0% might go to a smart contract 00:24:17.810 --> 00:24:19.450 align:start position:0% might go to a smart contract not<00:24:18.080> in<00:24:18.350> the<00:24:18.440> trade-off<00:24:18.770> of<00:24:18.800> like<00:24:19.130> what<00:24:19.280> sort 00:24:19.450 --> 00:24:19.460 align:start position:0% not in the trade-off of like what sort 00:24:19.460 --> 00:24:20.770 align:start position:0% not in the trade-off of like what sort of<00:24:19.520> UI<00:24:19.640> do<00:24:19.790> you<00:24:19.940> present<00:24:20.240> there<00:24:20.390> what<00:24:20.540> sort<00:24:20.690> of 00:24:20.770 --> 00:24:20.780 align:start position:0% of UI do you present there what sort of 00:24:20.780 --> 00:24:22.000 align:start position:0% of UI do you present there what sort of gas<00:24:21.020> do<00:24:21.200> you<00:24:21.260> charge<00:24:21.410> your<00:24:21.590> users<00:24:21.830> because 00:24:22.000 --> 00:24:22.010 align:start position:0% gas do you charge your users because 00:24:22.010 --> 00:24:23.890 align:start position:0% gas do you charge your users because your<00:24:22.640> standard<00:24:22.970> aetherium<00:24:23.210> transactions<00:24:23.810> a 00:24:23.890 --> 00:24:23.900 align:start position:0% your standard aetherium transactions a 00:24:23.900 --> 00:24:25.780 align:start position:0% your standard aetherium transactions a flat<00:24:24.110> 21,000<00:24:24.950> you<00:24:25.100> can<00:24:25.220> sort<00:24:25.400> of<00:24:25.460> guarantee 00:24:25.780 --> 00:24:25.790 align:start position:0% flat 21,000 you can sort of guarantee 00:24:25.790 --> 00:24:27.810 align:start position:0% flat 21,000 you can sort of guarantee that<00:24:26.000> or<00:24:26.480> decent<00:24:26.870> a<00:24:26.900> contracts<00:24:27.410> there's<00:24:27.560> no 00:24:27.810 --> 00:24:27.820 align:start position:0% that or decent a contracts there's no 00:24:27.820 --> 00:24:30.370 align:start position:0% that or decent a contracts there's no guarantees<00:24:28.820> necessarily<00:24:29.660> there's<00:24:30.170> things 00:24:30.370 --> 00:24:30.380 align:start position:0% guarantees necessarily there's things 00:24:30.380 --> 00:24:31.660 align:start position:0% guarantees necessarily there's things that<00:24:30.440> you<00:24:30.710> can<00:24:30.950> estimate<00:24:31.220> it<00:24:31.400> and<00:24:31.580> it's 00:24:31.660 --> 00:24:31.670 align:start position:0% that you can estimate it and it's 00:24:31.670 --> 00:24:33.130 align:start position:0% that you can estimate it and it's probably<00:24:31.880> right<00:24:32.120> but<00:24:32.300> it<00:24:32.420> might<00:24:32.450> change<00:24:32.870> to 00:24:33.130 --> 00:24:33.140 align:start position:0% probably right but it might change to 00:24:33.140 --> 00:24:35.200 align:start position:0% probably right but it might change to there's<00:24:33.410> some<00:24:33.560> ways<00:24:33.830> it<00:24:33.980> could<00:24:34.100> and<00:24:34.970> like 00:24:35.200 --> 00:24:35.210 align:start position:0% there's some ways it could and like 00:24:35.210 --> 00:24:36.580 align:start position:0% there's some ways it could and like that's<00:24:35.540> an<00:24:35.600> interesting<00:24:35.870> thing<00:24:35.960> in<00:24:36.080> exchange 00:24:36.580 --> 00:24:36.590 align:start position:0% that's an interesting thing in exchange 00:24:36.590 --> 00:24:38.650 align:start position:0% that's an interesting thing in exchange you<00:24:36.680> have<00:24:36.770> to<00:24:36.860> do<00:24:36.980> like<00:24:37.190> us<00:24:37.340> on<00:24:37.670> our<00:24:38.180> sort<00:24:38.600> of 00:24:38.650 --> 00:24:38.660 align:start position:0% you have to do like us on our sort of 00:24:38.660 --> 00:24:40.600 align:start position:0% you have to do like us on our sort of brokerage<00:24:38.840> of<00:24:39.290> just<00:24:39.530> corn-based<00:24:39.830> comms 00:24:40.600 --> 00:24:40.610 align:start position:0% brokerage of just corn-based comms 00:24:40.610 --> 00:24:42.100 align:start position:0% brokerage of just corn-based comms you<00:24:40.880> don't<00:24:41.030> see<00:24:41.150> any<00:24:41.330> gas<00:24:41.540> stuff<00:24:41.870> when<00:24:42.050> you 00:24:42.100 --> 00:24:42.110 align:start position:0% you don't see any gas stuff when you 00:24:42.110 --> 00:24:44.380 align:start position:0% you don't see any gas stuff when you send<00:24:42.350> and<00:24:42.530> it's<00:24:42.710> a<00:24:42.830> very<00:24:43.460> intentional 00:24:44.380 --> 00:24:44.390 align:start position:0% send and it's a very intentional 00:24:44.390 --> 00:24:46.150 align:start position:0% send and it's a very intentional decision<00:24:44.930> to<00:24:45.110> keep<00:24:45.230> it<00:24:45.410> simple<00:24:45.770> because<00:24:45.890> it's 00:24:46.150 --> 00:24:46.160 align:start position:0% decision to keep it simple because it's 00:24:46.160 --> 00:24:48.220 align:start position:0% decision to keep it simple because it's a<00:24:46.250> very<00:24:46.430> confusing<00:24:46.640> UX<00:24:47.330> sort<00:24:47.900> of<00:24:47.960> design 00:24:48.220 --> 00:24:48.230 align:start position:0% a very confusing UX sort of design 00:24:48.230 --> 00:24:50.050 align:start position:0% a very confusing UX sort of design pattern<00:24:48.590> it<00:24:48.680> as<00:24:48.800> a<00:24:48.830> sir<00:24:49.340> people<00:24:49.790> have<00:24:49.880> talked 00:24:50.050 --> 00:24:50.060 align:start position:0% pattern it as a sir people have talked 00:24:50.060 --> 00:24:52.180 align:start position:0% pattern it as a sir people have talked about<00:24:50.150> in<00:24:50.330> the<00:24:50.390> design<00:24:50.630> tracks<00:24:50.900> here<00:24:51.110> and<00:24:51.290> it's 00:24:52.180 --> 00:24:52.190 align:start position:0% about in the design tracks here and it's 00:24:52.190 --> 00:24:53.440 align:start position:0% about in the design tracks here and it's this<00:24:52.340> interesting<00:24:52.550> trade-off<00:24:53.030> of<00:24:53.060> like<00:24:53.300> how 00:24:53.440 --> 00:24:53.450 align:start position:0% this interesting trade-off of like how 00:24:53.450 --> 00:24:55.390 align:start position:0% this interesting trade-off of like how to<00:24:53.510> handle<00:24:53.780> that<00:24:53.900> and<00:24:54.080> I<00:24:54.170> was<00:24:54.290> like<00:24:54.440> a<00:24:54.680> business 00:24:55.390 --> 00:24:55.400 align:start position:0% to handle that and I was like a business 00:24:55.400 --> 00:24:56.560 align:start position:0% to handle that and I was like a business how<00:24:55.550> do<00:24:55.610> you<00:24:55.700> set<00:24:55.910> that<00:24:56.000> and<00:24:56.150> how<00:24:56.210> do<00:24:56.270> you<00:24:56.330> sort 00:24:56.560 --> 00:24:56.570 align:start position:0% how do you set that and how do you sort 00:24:56.570 --> 00:24:59.140 align:start position:0% how do you set that and how do you sort of<00:24:56.600> expose<00:24:56.930> that<00:24:57.140> to<00:24:57.380> users<00:24:57.880> yeah<00:24:58.880> it's<00:24:59.060> an 00:24:59.140 --> 00:24:59.150 align:start position:0% of expose that to users yeah it's an 00:24:59.150 --> 00:25:00.940 align:start position:0% of expose that to users yeah it's an interesting<00:24:59.300> question<00:24:59.840> for<00:24:59.990> exchanges<00:25:00.650> and<00:25:00.770> I 00:25:00.940 --> 00:25:00.950 align:start position:0% interesting question for exchanges and I 00:25:00.950 --> 00:25:03.310 align:start position:0% interesting question for exchanges and I mean<00:25:01.190> coinbase<00:25:01.520> you<00:25:01.790> kind<00:25:02.150> of<00:25:02.240> both<00:25:02.420> but<00:25:02.660> but 00:25:03.310 --> 00:25:03.320 align:start position:0% mean coinbase you kind of both but but 00:25:03.320 --> 00:25:06.610 align:start position:0% mean coinbase you kind of both but but exchanges<00:25:03.860> and<00:25:03.950> wallets<00:25:04.370> really<00:25:05.320> same<00:25:06.320> UX 00:25:06.610 --> 00:25:06.620 align:start position:0% exchanges and wallets really same UX 00:25:06.620 --> 00:25:08.290 align:start position:0% exchanges and wallets really same UX problem<00:25:06.980> really<00:25:07.130> it's<00:25:07.430> the<00:25:07.580> same<00:25:07.790> UX<00:25:08.030> problem 00:25:08.290 --> 00:25:08.300 align:start position:0% problem really it's the same UX problem 00:25:08.300 --> 00:25:10.210 align:start position:0% problem really it's the same UX problem that<00:25:08.530> aetherium<00:25:09.530> and<00:25:09.650> really<00:25:09.830> all<00:25:10.010> the 00:25:10.210 --> 00:25:10.220 align:start position:0% that aetherium and really all the 00:25:10.220 --> 00:25:11.890 align:start position:0% that aetherium and really all the cryptocurrency<00:25:10.730> industries<00:25:11.330> any<00:25:11.600> other<00:25:11.780> we 00:25:11.890 --> 00:25:11.900 align:start position:0% cryptocurrency industries any other we 00:25:11.900 --> 00:25:14.800 align:start position:0% cryptocurrency industries any other we do<00:25:12.020> right<00:25:12.170> now<00:25:12.820> it's<00:25:13.820> just<00:25:14.000> it's<00:25:14.360> probably<00:25:14.720> not 00:25:14.800 --> 00:25:14.810 align:start position:0% do right now it's just it's probably not 00:25:14.810 --> 00:25:16.180 align:start position:0% do right now it's just it's probably not just<00:25:15.020> a<00:25:15.080> theorem<00:25:15.380> and<00:25:15.530> but<00:25:15.710> we<00:25:15.800> can't<00:25:15.980> really 00:25:16.180 --> 00:25:16.190 align:start position:0% just a theorem and but we can't really 00:25:16.190 --> 00:25:18.130 align:start position:0% just a theorem and but we can't really just<00:25:16.460> sweep<00:25:16.640> it<00:25:16.760> under<00:25:16.910> the<00:25:16.940> rug<00:25:17.030> I<00:25:17.390> mean<00:25:17.870> the 00:25:18.130 --> 00:25:18.140 align:start position:0% just sweep it under the rug I mean the 00:25:18.140 --> 00:25:20.410 align:start position:0% just sweep it under the rug I mean the the<00:25:18.170> the<00:25:18.440> main<00:25:19.220> issue<00:25:19.460> I<00:25:19.610> think<00:25:19.730> really<00:25:20.240> is 00:25:20.410 --> 00:25:20.420 align:start position:0% the the main issue I think really is 00:25:20.420 --> 00:25:23.290 align:start position:0% the the main issue I think really is that<00:25:21.010> customers<00:25:22.010> expect<00:25:22.130> them<00:25:22.520> to<00:25:22.550> pay<00:25:22.820> you 00:25:23.290 --> 00:25:23.300 align:start position:0% that customers expect them to pay you 00:25:23.300 --> 00:25:25.360 align:start position:0% that customers expect them to pay you know<00:25:23.390> they're<00:25:23.600> used<00:25:23.750> to<00:25:23.840> paying<00:25:24.140> fees<00:25:25.130> which 00:25:25.360 --> 00:25:25.370 align:start position:0% know they're used to paying fees which 00:25:25.370 --> 00:25:29.770 align:start position:0% know they're used to paying fees which are<00:25:25.520> percentage<00:25:26.090> or<00:25:27.050> a<00:25:27.110> flat<00:25:27.500> fee<00:25:27.710> and<00:25:27.920> in<00:25:28.850> in<00:25:29.630> a 00:25:29.770 --> 00:25:29.780 align:start position:0% are percentage or a flat fee and in in a 00:25:29.780 --> 00:25:31.630 align:start position:0% are percentage or a flat fee and in in a theorem<00:25:30.080> and<00:25:30.170> other<00:25:30.290> chains<00:25:30.620> you're<00:25:31.430> really 00:25:31.630 --> 00:25:31.640 align:start position:0% theorem and other chains you're really 00:25:31.640 --> 00:25:39.720 align:start position:0% theorem and other chains you're really paying<00:25:31.850> for<00:25:32.330> compute<00:25:32.930> or<00:25:33.380> space<00:25:33.830> and 00:25:39.720 --> 00:25:39.730 align:start position:0% 00:25:39.730 --> 00:25:43.030 align:start position:0% interesting<00:25:40.960> all<00:25:41.960> right<00:25:42.110> so<00:25:42.290> I<00:25:42.530> think<00:25:42.590> Jake's 00:25:43.030 --> 00:25:43.040 align:start position:0% interesting all right so I think Jake's 00:25:43.040 --> 00:25:45.280 align:start position:0% interesting all right so I think Jake's you'd<00:25:43.250> mentioned<00:25:43.610> batching<00:25:44.180> briefly<00:25:44.840> down 00:25:45.280 --> 00:25:45.290 align:start position:0% you'd mentioned batching briefly down 00:25:45.290 --> 00:25:47.710 align:start position:0% you'd mentioned batching briefly down there<00:25:45.560> you<00:25:46.190> guys<00:25:46.340> want<00:25:46.490> me<00:25:46.580> chat<00:25:47.390> about<00:25:47.570> that 00:25:47.710 --> 00:25:47.720 align:start position:0% there you guys want me chat about that 00:25:47.720 --> 00:25:49.540 align:start position:0% there you guys want me chat about that of<00:25:47.870> it<00:25:47.960> what<00:25:48.050> do<00:25:48.110> you<00:25:48.200> think<00:25:48.380> about<00:25:48.590> it<00:25:48.740> is<00:25:49.310> it 00:25:49.540 --> 00:25:49.550 align:start position:0% of it what do you think about it is it 00:25:49.550 --> 00:25:51.580 align:start position:0% of it what do you think about it is it something<00:25:49.730> that<00:25:49.970> the<00:25:50.750> theory<00:25:50.960> needs<00:25:51.170> is<00:25:51.440> there 00:25:51.580 --> 00:25:51.590 align:start position:0% something that the theory needs is there 00:25:51.590 --> 00:25:53.620 align:start position:0% something that the theory needs is there some<00:25:51.800> sort<00:25:52.010> of<00:25:52.180> alternative<00:25:53.180> thing<00:25:53.420> that 00:25:53.620 --> 00:25:53.630 align:start position:0% some sort of alternative thing that 00:25:53.630 --> 00:25:55.030 align:start position:0% some sort of alternative thing that maybe<00:25:53.780> would<00:25:54.050> also<00:25:54.200> be<00:25:54.410> interesting<00:25:54.830> to<00:25:54.890> have 00:25:55.030 --> 00:25:55.040 align:start position:0% maybe would also be interesting to have 00:25:55.040 --> 00:25:57.670 align:start position:0% maybe would also be interesting to have yeah<00:25:55.700> I<00:25:56.120> think<00:25:56.240> I<00:25:56.510> only<00:25:56.780> first<00:25:57.170> brought<00:25:57.410> up<00:25:57.440> we 00:25:57.670 --> 00:25:57.680 align:start position:0% yeah I think I only first brought up we 00:25:57.680 --> 00:25:59.650 align:start position:0% yeah I think I only first brought up we were<00:25:57.800> sort<00:25:58.010> of<00:25:58.040> talking<00:25:58.160> yesterday<00:25:58.700> and<00:25:59.600> I 00:25:59.650 --> 00:25:59.660 align:start position:0% were sort of talking yesterday and I 00:25:59.660 --> 00:26:00.940 align:start position:0% were sort of talking yesterday and I sort<00:25:59.870> of<00:25:59.930> brought<00:26:00.200> this<00:26:00.380> up<00:26:00.560> and<00:26:00.680> I<00:26:00.740> hadn't 00:26:00.940 --> 00:26:00.950 align:start position:0% sort of brought this up and I hadn't 00:26:00.950 --> 00:26:02.250 align:start position:0% sort of brought this up and I hadn't thought<00:26:01.010> too<00:26:01.190> much<00:26:01.220> about<00:26:01.580> it<00:26:01.760> deeply<00:26:02.030> but 00:26:02.250 --> 00:26:02.260 align:start position:0% thought too much about it deeply but 00:26:02.260 --> 00:26:04.060 align:start position:0% thought too much about it deeply but like<00:26:03.260> I<00:26:03.290> mentioned<00:26:03.650> we<00:26:03.710> have<00:26:03.830> a<00:26:03.860> lot<00:26:03.920> of 00:26:04.060 --> 00:26:04.070 align:start position:0% like I mentioned we have a lot of 00:26:04.070 --> 00:26:05.620 align:start position:0% like I mentioned we have a lot of addresses<00:26:04.280> and<00:26:04.880> so<00:26:05.000> we<00:26:05.180> have<00:26:05.270> all<00:26:05.360> sorts<00:26:05.480> of 00:26:05.620 --> 00:26:05.630 align:start position:0% addresses and so we have all sorts of 00:26:05.630 --> 00:26:06.730 align:start position:0% addresses and so we have all sorts of customers<00:26:05.990> setting<00:26:06.230> and<00:26:06.350> all<00:26:06.410> sorts<00:26:06.680> of 00:26:06.730 --> 00:26:06.740 align:start position:0% customers setting and all sorts of 00:26:06.740 --> 00:26:08.230 align:start position:0% customers setting and all sorts of amounts<00:26:07.130> so<00:26:07.340> you<00:26:07.670> know<00:26:07.760> we'll<00:26:07.880> end<00:26:07.910> up<00:26:08.060> with<00:26:08.120> a 00:26:08.230 --> 00:26:08.240 align:start position:0% amounts so you know we'll end up with a 00:26:08.240 --> 00:26:09.520 align:start position:0% amounts so you know we'll end up with a lot<00:26:08.390> of<00:26:08.420> addresses<00:26:08.870> with<00:26:09.020> very<00:26:09.170> small<00:26:09.470> amounts 00:26:09.520 --> 00:26:09.530 align:start position:0% lot of addresses with very small amounts 00:26:09.530 --> 00:26:12.520 align:start position:0% lot of addresses with very small amounts of<00:26:09.920> ether<00:26:10.190> I<00:26:10.430> will<00:26:10.820> need<00:26:10.940> to<00:26:11.060> so<00:26:11.390> let's<00:26:11.750> say<00:26:11.900> we 00:26:12.520 --> 00:26:12.530 align:start position:0% of ether I will need to so let's say we 00:26:12.530 --> 00:26:13.750 align:start position:0% of ether I will need to so let's say we have<00:26:12.620> a<00:26:12.650> set<00:26:12.770> of<00:26:12.890> addresses<00:26:13.010> that<00:26:13.430> up<00:26:13.550> you<00:26:13.670> know 00:26:13.750 --> 00:26:13.760 align:start position:0% have a set of addresses that up you know 00:26:13.760 --> 00:26:16.150 align:start position:0% have a set of addresses that up you know one<00:26:14.420> eath<00:26:14.660> in<00:26:14.900> each<00:26:15.050> and<00:26:15.350> we<00:26:15.530> need<00:26:15.680> to<00:26:15.800> do<00:26:15.890> you 00:26:16.150 --> 00:26:16.160 align:start position:0% one eath in each and we need to do you 00:26:16.160 --> 00:26:18.520 align:start position:0% one eath in each and we need to do you know<00:26:16.250> attend<00:26:16.580> etherium<00:26:17.360> sent<00:26:17.600> well<00:26:18.200> we<00:26:18.380> need 00:26:18.520 --> 00:26:18.530 align:start position:0% know attend etherium sent well we need 00:26:18.530 --> 00:26:20.320 align:start position:0% know attend etherium sent well we need to<00:26:18.620> sort<00:26:18.800> of<00:26:18.860> combine<00:26:19.250> those<00:26:19.490> into<00:26:20.000> some<00:26:20.240> other 00:26:20.320 --> 00:26:20.330 align:start position:0% to sort of combine those into some other 00:26:20.330 --> 00:26:23.020 align:start position:0% to sort of combine those into some other address<00:26:20.780> and<00:26:21.050> then<00:26:21.650> after<00:26:22.340> that<00:26:22.490> confirms<00:26:22.850> on 00:26:23.020 --> 00:26:23.030 align:start position:0% address and then after that confirms on 00:26:23.030 --> 00:26:24.970 align:start position:0% address and then after that confirms on chain<00:26:23.270> all<00:26:23.540> you<00:26:23.780> know<00:26:23.870> ten<00:26:24.230> transactions<00:26:24.860> that 00:26:24.970 --> 00:26:24.980 align:start position:0% chain all you know ten transactions that 00:26:24.980 --> 00:26:26.650 align:start position:0% chain all you know ten transactions that might<00:26:25.100> take<00:26:25.280> what<00:26:25.940> we<00:26:26.000> need<00:26:26.150> so<00:26:26.360> we<00:26:26.390> need<00:26:26.570> to 00:26:26.650 --> 00:26:26.660 align:start position:0% might take what we need so we need to 00:26:26.660 --> 00:26:28.150 align:start position:0% might take what we need so we need to first<00:26:26.840> send<00:26:27.020> ten<00:26:27.260> wait<00:26:27.560> for<00:26:27.740> them<00:26:27.830> all<00:26:28.010> to 00:26:28.150 --> 00:26:28.160 align:start position:0% first send ten wait for them all to 00:26:28.160 --> 00:26:30.100 align:start position:0% first send ten wait for them all to confirm<00:26:28.550> then<00:26:29.060> once<00:26:29.300> they<00:26:29.450> confirm<00:26:29.600> we<00:26:29.960> can 00:26:30.100 --> 00:26:30.110 align:start position:0% confirm then once they confirm we can 00:26:30.110 --> 00:26:31.690 align:start position:0% confirm then once they confirm we can then<00:26:30.230> send<00:26:30.410> out<00:26:30.560> this<00:26:30.740> tiny<00:26:30.890> three<00:26:31.160> so<00:26:31.340> this 00:26:31.690 --> 00:26:31.700 align:start position:0% then send out this tiny three so this 00:26:31.700 --> 00:26:33.330 align:start position:0% then send out this tiny three so this we<00:26:31.909> call<00:26:32.059> this<00:26:32.149> like<00:26:32.299> consolidation 00:26:33.330 --> 00:26:33.340 align:start position:0% we call this like consolidation 00:26:33.340 --> 00:26:35.919 align:start position:0% we call this like consolidation internally<00:26:34.340> and<00:26:34.610> this<00:26:35.330> is<00:26:35.539> sort<00:26:35.840> of<00:26:35.870> a 00:26:35.919 --> 00:26:35.929 align:start position:0% internally and this is sort of a 00:26:35.929 --> 00:26:38.139 align:start position:0% internally and this is sort of a complicated<00:26:36.440> thing<00:26:36.470> to<00:26:36.620> manage<00:26:37.100> and<00:26:37.340> it's<00:26:38.029> an 00:26:38.139 --> 00:26:38.149 align:start position:0% complicated thing to manage and it's an 00:26:38.149 --> 00:26:40.120 align:start position:0% complicated thing to manage and it's an interesting<00:26:38.450> thing<00:26:38.600> because<00:26:38.799> like<00:26:39.799> Bitcoin 00:26:40.120 --> 00:26:40.130 align:start position:0% interesting thing because like Bitcoin 00:26:40.130 --> 00:26:43.090 align:start position:0% interesting thing because like Bitcoin and<00:26:40.399> sort<00:26:41.090> of<00:26:41.149> these<00:26:41.240> you<00:26:41.389> TXO<00:26:41.779> chains<00:26:42.169> they 00:26:43.090 --> 00:26:43.100 align:start position:0% and sort of these you TXO chains they 00:26:43.100 --> 00:26:44.860 align:start position:0% and sort of these you TXO chains they have<00:26:43.850> a<00:26:43.880> different<00:26:44.179> way<00:26:44.240> of<00:26:44.269> approaching<00:26:44.600> this 00:26:44.860 --> 00:26:44.870 align:start position:0% have a different way of approaching this 00:26:44.870 --> 00:26:47.230 align:start position:0% have a different way of approaching this that<00:26:45.289> doesn't<00:26:45.440> have<00:26:45.620> this<00:26:45.740> problem<00:26:46.039> and<00:26:46.490> so 00:26:47.230 --> 00:26:47.240 align:start position:0% that doesn't have this problem and so 00:26:47.240 --> 00:26:49.210 align:start position:0% that doesn't have this problem and so once<00:26:47.690> you<00:26:47.779> in<00:26:48.019> it<00:26:48.320> one<00:26:48.710> of<00:26:48.799> the<00:26:48.860> reasons<00:26:49.100> they 00:26:49.210 --> 00:26:49.220 align:start position:0% once you in it one of the reasons they 00:26:49.220 --> 00:26:50.620 align:start position:0% once you in it one of the reasons they do<00:26:49.279> that<00:26:49.519> is<00:26:49.730> so<00:26:49.760> you<00:26:49.940> can<00:26:50.059> have<00:26:50.179> sort<00:26:50.330> of<00:26:50.419> a<00:26:50.510> new 00:26:50.620 --> 00:26:50.630 align:start position:0% do that is so you can have sort of a new 00:26:50.630 --> 00:26:53.470 align:start position:0% do that is so you can have sort of a new address<00:26:50.809> for<00:26:51.230> every<00:26:51.380> sort<00:26:52.070> of<00:26:52.130> change<00:26:52.639> amount 00:26:53.470 --> 00:26:53.480 align:start position:0% address for every sort of change amount 00:26:53.480 --> 00:26:54.850 align:start position:0% address for every sort of change amount and<00:26:53.600> so<00:26:53.690> you<00:26:53.750> can<00:26:53.899> basically<00:26:54.080> always<00:26:54.409> be<00:26:54.590> using 00:26:54.850 --> 00:26:54.860 align:start position:0% and so you can basically always be using 00:26:54.860 --> 00:26:55.930 align:start position:0% and so you can basically always be using new<00:26:54.980> things<00:26:55.220> whereas<00:26:55.460> like<00:26:55.549> on<00:26:55.639> a<00:26:55.700> theorem 00:26:55.930 --> 00:26:55.940 align:start position:0% new things whereas like on a theorem 00:26:55.940 --> 00:26:57.549 align:start position:0% new things whereas like on a theorem it's<00:26:56.059> really<00:26:56.269> hard<00:26:56.539> and<00:26:56.809> it's<00:26:57.019> all<00:26:57.230> about<00:26:57.380> this 00:26:57.549 --> 00:26:57.559 align:start position:0% it's really hard and it's all about this 00:26:57.559 --> 00:27:00.070 align:start position:0% it's really hard and it's all about this privacy<00:26:58.010> stuff<00:26:58.190> again<00:26:58.460> where<00:26:59.240> you<00:26:59.840> wouldn't 00:27:00.070 --> 00:27:00.080 align:start position:0% privacy stuff again where you wouldn't 00:27:00.080 --> 00:27:01.450 align:start position:0% privacy stuff again where you wouldn't want<00:27:00.289> to<00:27:00.350> do<00:27:00.470> that<00:27:00.649> because<00:27:00.830> if<00:27:01.070> you<00:27:01.100> wanted<00:27:01.340> to 00:27:01.450 --> 00:27:01.460 align:start position:0% want to do that because if you wanted to 00:27:01.460 --> 00:27:03.070 align:start position:0% want to do that because if you wanted to do<00:27:01.639> a<00:27:01.669> cent<00:27:02.000> you'd<00:27:02.210> have<00:27:02.330> to<00:27:02.480> do<00:27:02.600> all<00:27:02.840> these 00:27:03.070 --> 00:27:03.080 align:start position:0% do a cent you'd have to do all these 00:27:03.080 --> 00:27:04.960 align:start position:0% do a cent you'd have to do all these like<00:27:03.260> intermediate<00:27:03.889> sentence<00:27:04.309> to<00:27:04.460> finally<00:27:04.850> be 00:27:04.960 --> 00:27:04.970 align:start position:0% like intermediate sentence to finally be 00:27:04.970 --> 00:27:06.460 align:start position:0% like intermediate sentence to finally be able<00:27:05.029> to<00:27:05.149> do<00:27:05.299> it<00:27:05.450> and<00:27:05.600> so<00:27:06.139> I<00:27:06.169> think<00:27:06.289> it'd<00:27:06.440> be 00:27:06.460 --> 00:27:06.470 align:start position:0% able to do it and so I think it'd be 00:27:06.470 --> 00:27:08.049 align:start position:0% able to do it and so I think it'd be interesting<00:27:06.710> to<00:27:07.159> consider<00:27:07.309> some<00:27:07.789> sort<00:27:08.000> of 00:27:08.049 --> 00:27:08.059 align:start position:0% interesting to consider some sort of 00:27:08.059 --> 00:27:10.870 align:start position:0% interesting to consider some sort of like<00:27:08.260> batching<00:27:09.260> strategy<00:27:10.220> or<00:27:10.309> like<00:27:10.429> multi 00:27:10.870 --> 00:27:10.880 align:start position:0% like batching strategy or like multi 00:27:10.880 --> 00:27:12.430 align:start position:0% like batching strategy or like multi transaction<00:27:11.659> thing<00:27:11.899> where<00:27:12.080> you<00:27:12.169> could<00:27:12.289> say 00:27:12.430 --> 00:27:12.440 align:start position:0% transaction thing where you could say 00:27:12.440 --> 00:27:13.810 align:start position:0% transaction thing where you could say you<00:27:12.500> know<00:27:12.679> from<00:27:12.860> all<00:27:12.950> these<00:27:13.100> addresses<00:27:13.610> I'll 00:27:13.810 --> 00:27:13.820 align:start position:0% you know from all these addresses I'll 00:27:13.820 --> 00:27:15.519 align:start position:0% you know from all these addresses I'll include<00:27:14.149> all<00:27:14.269> the<00:27:14.389> signatures<00:27:14.659> for<00:27:14.960> them<00:27:15.049> do 00:27:15.519 --> 00:27:15.529 align:start position:0% include all the signatures for them do 00:27:15.529 --> 00:27:17.440 align:start position:0% include all the signatures for them do all<00:27:15.710> these<00:27:15.830> transactions<00:27:16.460> at<00:27:16.580> once<00:27:16.760> into<00:27:17.120> some 00:27:17.440 --> 00:27:17.450 align:start position:0% all these transactions at once into some 00:27:17.450 --> 00:27:19.269 align:start position:0% all these transactions at once into some like<00:27:17.840> destination<00:27:18.500> and<00:27:18.710> as<00:27:18.980> sort<00:27:19.159> of<00:27:19.220> one 00:27:19.269 --> 00:27:19.279 align:start position:0% like destination and as sort of one 00:27:19.279 --> 00:27:22.299 align:start position:0% like destination and as sort of one atomic<00:27:20.110> send<00:27:21.110> there<00:27:21.289> because<00:27:21.620> also<00:27:21.889> you 00:27:22.299 --> 00:27:22.309 align:start position:0% atomic send there because also you 00:27:22.309 --> 00:27:24.250 align:start position:0% atomic send there because also you probably<00:27:22.549> don't<00:27:22.909> want<00:27:23.059> to<00:27:23.090> do<00:27:23.269> because<00:27:24.169> you 00:27:24.250 --> 00:27:24.260 align:start position:0% probably don't want to do because you 00:27:24.260 --> 00:27:25.269 align:start position:0% probably don't want to do because you could<00:27:24.380> also<00:27:24.620> I<00:27:24.649> guess<00:27:24.830> another<00:27:24.950> way<00:27:25.100> it's<00:27:25.220> sort 00:27:25.269 --> 00:27:25.279 align:start position:0% could also I guess another way it's sort 00:27:25.279 --> 00:27:26.379 align:start position:0% could also I guess another way it's sort of<00:27:25.370> consolidating<00:27:25.940> and<00:27:26.029> then<00:27:26.149> do<00:27:26.240> a<00:27:26.269> good 00:27:26.379 --> 00:27:26.389 align:start position:0% of consolidating and then do a good 00:27:26.389 --> 00:27:28.570 align:start position:0% of consolidating and then do a good thing<00:27:26.510> at<00:27:26.600> any<00:27:26.779> send<00:27:27.230> you<00:27:27.470> could<00:27:27.649> do<00:27:27.799> like<00:27:28.130> ten 00:27:28.570 --> 00:27:28.580 align:start position:0% thing at any send you could do like ten 00:27:28.580 --> 00:27:30.220 align:start position:0% thing at any send you could do like ten individual<00:27:29.029> any<00:27:29.210> sense<00:27:29.510> that<00:27:29.690> destination 00:27:30.220 --> 00:27:30.230 align:start position:0% individual any sense that destination 00:27:30.230 --> 00:27:32.379 align:start position:0% individual any sense that destination but<00:27:30.500> if<00:27:30.679> it's<00:27:30.919> like<00:27:31.070> a<00:27:31.100> payment<00:27:31.370> service<00:27:31.669> they 00:27:32.379 --> 00:27:32.389 align:start position:0% but if it's like a payment service they 00:27:32.389 --> 00:27:34.120 align:start position:0% but if it's like a payment service they probably<00:27:32.659> aren't<00:27:32.870> gonna<00:27:32.990> handle<00:27:33.350> that<00:27:33.529> well 00:27:34.120 --> 00:27:34.130 align:start position:0% probably aren't gonna handle that well 00:27:34.130 --> 00:27:35.560 align:start position:0% probably aren't gonna handle that well if<00:27:34.399> they're<00:27:34.580> expecting<00:27:34.789> ten<00:27:35.120> even<00:27:35.389> they<00:27:35.480> get 00:27:35.560 --> 00:27:35.570 align:start position:0% if they're expecting ten even they get 00:27:35.570 --> 00:27:36.909 align:start position:0% if they're expecting ten even they get like<00:27:35.720> ten<00:27:35.899> twenty<00:27:36.230> sends<00:27:36.559> they're<00:27:36.679> not<00:27:36.799> gonna 00:27:36.909 --> 00:27:36.919 align:start position:0% like ten twenty sends they're not gonna 00:27:36.919 --> 00:27:38.680 align:start position:0% like ten twenty sends they're not gonna know<00:27:37.130> where<00:27:37.669> it's<00:27:37.820> supposed<00:27:37.880> to<00:27:38.090> go<00:27:38.149> to<00:27:38.269> right 00:27:38.680 --> 00:27:38.690 align:start position:0% know where it's supposed to go to right 00:27:38.690 --> 00:27:41.259 align:start position:0% know where it's supposed to go to right pretty<00:27:38.960> bad<00:27:39.139> UX<00:27:39.500> if<00:27:39.769> a<00:27:40.010> user<00:27:40.549> goes<00:27:40.669> to<00:27:40.940> send<00:27:41.149> one 00:27:41.259 --> 00:27:41.269 align:start position:0% pretty bad UX if a user goes to send one 00:27:41.269 --> 00:27:43.090 align:start position:0% pretty bad UX if a user goes to send one transaction<00:27:41.690> and<00:27:42.080> they<00:27:42.169> received<00:27:42.559> ten<00:27:42.860> on<00:27:43.010> the 00:27:43.090 --> 00:27:43.100 align:start position:0% transaction and they received ten on the 00:27:43.100 --> 00:27:45.879 align:start position:0% transaction and they received ten on the other<00:27:43.250> end<00:27:43.399> yeah<00:27:44.299> that's<00:27:44.539> probably<00:27:44.889> confused 00:27:45.879 --> 00:27:45.889 align:start position:0% other end yeah that's probably confused 00:27:45.889 --> 00:27:49.180 align:start position:0% other end yeah that's probably confused I<00:27:46.190> think<00:27:47.260> with<00:27:48.260> the<00:27:48.380> theorem<00:27:48.559> actually<00:27:48.950> it's<00:27:49.100> a 00:27:49.180 --> 00:27:49.190 align:start position:0% I think with the theorem actually it's a 00:27:49.190 --> 00:27:51.789 align:start position:0% I think with the theorem actually it's a bit<00:27:49.370> it's<00:27:50.360> pretty<00:27:50.570> cool<00:27:51.139> in<00:27:51.320> different<00:27:51.620> sense 00:27:51.789 --> 00:27:51.799 align:start position:0% bit it's pretty cool in different sense 00:27:51.799 --> 00:27:54.370 align:start position:0% bit it's pretty cool in different sense that<00:27:52.010> in<00:27:52.279> Bitcoin<00:27:52.940> you<00:27:53.480> know<00:27:53.720> that<00:27:54.019> you<00:27:54.230> have 00:27:54.370 --> 00:27:54.380 align:start position:0% that in Bitcoin you know that you have 00:27:54.380 --> 00:27:56.409 align:start position:0% that in Bitcoin you know that you have these<00:27:54.500> inspects<00:27:55.039> and<00:27:55.399> you<00:27:55.940> can<00:27:56.090> tell<00:27:56.269> whether 00:27:56.409 --> 00:27:56.419 align:start position:0% these inspects and you can tell whether 00:27:56.419 --> 00:27:58.269 align:start position:0% these inspects and you can tell whether each<00:27:56.600> of<00:27:56.630> the<00:27:56.840> spent<00:27:57.080> is<00:27:57.200> economical<00:27:57.740> to<00:27:57.919> spend 00:27:58.269 --> 00:27:58.279 align:start position:0% each of the spent is economical to spend 00:27:58.279 --> 00:28:00.340 align:start position:0% each of the spent is economical to spend or<00:27:58.399> not<00:27:58.429> in<00:27:59.210> a<00:27:59.330> theorem<00:27:59.630> you<00:27:59.779> can<00:27:59.809> almost<00:28:00.080> say 00:28:00.340 --> 00:28:00.350 align:start position:0% or not in a theorem you can almost say 00:28:00.350 --> 00:28:01.960 align:start position:0% or not in a theorem you can almost say like<00:28:00.529> okay<00:28:00.860> if<00:28:00.980> you've<00:28:01.130> got<00:28:01.250> like<00:28:01.429> some<00:28:01.639> dust 00:28:01.960 --> 00:28:01.970 align:start position:0% like okay if you've got like some dust 00:28:01.970 --> 00:28:04.539 align:start position:0% like okay if you've got like some dust you<00:28:02.570> can<00:28:02.720> just<00:28:02.899> wait<00:28:03.080> because<00:28:03.769> you're<00:28:04.429> not 00:28:04.539 --> 00:28:04.549 align:start position:0% you can just wait because you're not 00:28:04.549 --> 00:28:06.009 align:start position:0% you can just wait because you're not spending<00:28:04.970> part<00:28:05.299> spend<00:28:05.570> you're<00:28:05.659> spending<00:28:05.929> from 00:28:06.009 --> 00:28:06.019 align:start position:0% spending part spend you're spending from 00:28:06.019 --> 00:28:08.350 align:start position:0% spending part spend you're spending from the<00:28:06.080> account<00:28:06.440> so<00:28:07.100> you<00:28:07.669> know<00:28:07.760> if<00:28:07.880> someone<00:28:08.149> sent 00:28:08.350 --> 00:28:08.360 align:start position:0% the account so you know if someone sent 00:28:08.360 --> 00:28:11.259 align:start position:0% the account so you know if someone sent you<00:28:08.480> a<00:28:08.510> lot<00:28:08.750> of<00:28:08.899> you<00:28:09.320> know<00:28:09.350> one<00:28:09.919> one<00:28:10.399> ways<00:28:10.610> you 00:28:11.259 --> 00:28:11.269 align:start position:0% you a lot of you know one one ways you 00:28:11.269 --> 00:28:13.629 align:start position:0% you a lot of you know one one ways you could<00:28:11.480> wait<00:28:11.630> for<00:28:11.870> I<00:28:12.260> don't<00:28:12.860> know<00:28:12.950> resilient<00:28:13.580> of 00:28:13.629 --> 00:28:13.639 align:start position:0% could wait for I don't know resilient of 00:28:13.639 --> 00:28:16.500 align:start position:0% could wait for I don't know resilient of them<00:28:13.760> before<00:28:14.450> you<00:28:14.570> actually<00:28:14.720> took<00:28:15.110> it<00:28:15.230> out 00:28:16.500 --> 00:28:16.510 align:start position:0% them before you actually took it out 00:28:16.510 --> 00:28:18.789 align:start position:0% them before you actually took it out usually<00:28:17.510> I<00:28:17.539> think<00:28:17.840> you<00:28:17.960> know<00:28:18.080> consolidation 00:28:18.789 --> 00:28:18.799 align:start position:0% usually I think you know consolidation 00:28:18.799 --> 00:28:20.560 align:start position:0% usually I think you know consolidation is<00:28:18.919> it's<00:28:19.250> a<00:28:19.309> good<00:28:19.460> idea<00:28:19.639> to<00:28:19.700> just<00:28:19.760> do<00:28:19.970> it<00:28:20.090> like 00:28:20.560 --> 00:28:20.570 align:start position:0% is it's a good idea to just do it like 00:28:20.570 --> 00:28:22.629 align:start position:0% is it's a good idea to just do it like when<00:28:20.990> the<00:28:21.440> account<00:28:21.769> went<00:28:22.039> when<00:28:22.190> the<00:28:22.340> network 00:28:22.629 --> 00:28:22.639 align:start position:0% when the account went when the network 00:28:22.639 --> 00:28:25.299 align:start position:0% when the account went when the network is<00:28:22.669> less<00:28:23.000> loaded<00:28:23.779> so<00:28:24.019> you<00:28:24.320> know<00:28:24.740> when<00:28:24.950> nobody's 00:28:25.299 --> 00:28:25.309 align:start position:0% is less loaded so you know when nobody's 00:28:25.309 --> 00:28:30.789 align:start position:0% is less loaded so you know when nobody's holding<00:28:25.490> any<00:28:25.639> I<00:28:25.760> SEOs<00:28:28.179> on<00:28:29.679> weekends<00:28:30.679> or 00:28:30.789 --> 00:28:30.799 align:start position:0% holding any I SEOs on weekends or 00:28:30.799 --> 00:28:32.980 align:start position:0% holding any I SEOs on weekends or something<00:28:30.860> like<00:28:31.130> that<00:28:31.510> when<00:28:32.510> the<00:28:32.600> gas<00:28:32.720> price 00:28:32.980 --> 00:28:32.990 align:start position:0% something like that when the gas price 00:28:32.990 --> 00:28:34.899 align:start position:0% something like that when the gas price is<00:28:33.350> pretty<00:28:33.649> low<00:28:33.889> and<00:28:34.100> keep<00:28:34.460> it<00:28:34.610> low<00:28:34.760> so<00:28:34.880> that 00:28:34.899 --> 00:28:34.909 align:start position:0% is pretty low and keep it low so that 00:28:34.909 --> 00:28:36.129 align:start position:0% is pretty low and keep it low so that you<00:28:35.059> don't<00:28:35.210> actually<00:28:35.360> impact<00:28:35.750> the<00:28:35.840> network 00:28:36.129 --> 00:28:36.139 align:start position:0% you don't actually impact the network 00:28:36.139 --> 00:28:39.310 align:start position:0% you don't actually impact the network because<00:28:36.940> you<00:28:37.940> very<00:28:38.149> well<00:28:38.299> could<00:28:38.539> one<00:28:39.139> of<00:28:39.169> the 00:28:39.310 --> 00:28:39.320 align:start position:0% because you very well could one of the 00:28:39.320 --> 00:28:42.490 align:start position:0% because you very well could one of the interesting<00:28:39.710> things<00:28:39.919> I<00:28:40.039> want<00:28:40.220> to<00:28:41.000> ask<00:28:41.440> both<00:28:42.440> of 00:28:42.490 --> 00:28:42.500 align:start position:0% interesting things I want to ask both of 00:28:42.500 --> 00:28:43.720 align:start position:0% interesting things I want to ask both of you<00:28:42.679> here 00:28:43.720 --> 00:28:43.730 align:start position:0% you here 00:28:43.730 --> 00:28:45.820 align:start position:0% you here you<00:28:43.820> know<00:28:43.940> what<00:28:44.360> have<00:28:44.750> you<00:28:44.870> seen<00:28:45.140> in<00:28:45.200> regards 00:28:45.820 --> 00:28:45.830 align:start position:0% you know what have you seen in regards 00:28:45.830 --> 00:28:48.600 align:start position:0% you know what have you seen in regards to<00:28:45.920> batching<00:28:46.520> out<00:28:46.640> outgoing<00:28:47.270> transactions<00:28:47.780> so 00:28:48.600 --> 00:28:48.610 align:start position:0% to batching out outgoing transactions so 00:28:48.610 --> 00:28:53.050 align:start position:0% to batching out outgoing transactions so you<00:28:49.610> know<00:28:49.700> with<00:28:50.950> with<00:28:51.950> with<00:28:52.430> other<00:28:52.640> with<00:28:52.970> other 00:28:53.050 --> 00:28:53.060 align:start position:0% you know with with with other with other 00:28:53.060 --> 00:28:55.120 align:start position:0% you know with with with other with other coins<00:28:53.420> without<00:28:54.200> getting<00:28:54.530> too<00:28:54.620> much<00:28:54.650> into<00:28:54.800> that 00:28:55.120 --> 00:28:55.130 align:start position:0% coins without getting too much into that 00:28:55.130 --> 00:28:57.880 align:start position:0% coins without getting too much into that a<00:28:55.700> common<00:28:56.270> pattern<00:28:56.600> is<00:28:56.840> you<00:28:57.140> wait<00:28:57.320> every<00:28:57.650> five 00:28:57.880 --> 00:28:57.890 align:start position:0% a common pattern is you wait every five 00:28:57.890 --> 00:29:00.220 align:start position:0% a common pattern is you wait every five minutes<00:28:58.190> or<00:28:58.490> ten<00:28:58.520> minutes<00:28:58.880> and<00:28:59.090> you<00:28:59.840> batch<00:29:00.050> out 00:29:00.220 --> 00:29:00.230 align:start position:0% minutes or ten minutes and you batch out 00:29:00.230 --> 00:29:02.860 align:start position:0% minutes or ten minutes and you batch out a<00:29:00.440> send<00:29:00.770> you<00:29:01.550> know<00:29:01.670> of<00:29:02.090> whoever<00:29:02.480> else<00:29:02.720> is 00:29:02.860 --> 00:29:02.870 align:start position:0% a send you know of whoever else is 00:29:02.870 --> 00:29:05.920 align:start position:0% a send you know of whoever else is trying<00:29:03.050> to<00:29:03.140> withdraw<00:29:03.320> during<00:29:04.310> that<00:29:04.580> time<00:29:04.930> with 00:29:05.920 --> 00:29:05.930 align:start position:0% trying to withdraw during that time with 00:29:05.930 --> 00:29:08.020 align:start position:0% trying to withdraw during that time with the<00:29:05.990> theorem<00:29:06.380> this<00:29:06.770> is<00:29:06.920> largely<00:29:07.250> not<00:29:07.700> been 00:29:08.020 --> 00:29:08.030 align:start position:0% the theorem this is largely not been 00:29:08.030 --> 00:29:10.090 align:start position:0% the theorem this is largely not been done<00:29:08.330> yet<00:29:08.360> even<00:29:09.200> though<00:29:09.350> it<00:29:09.530> is<00:29:09.650> very<00:29:09.860> possible 00:29:10.090 --> 00:29:10.100 align:start position:0% done yet even though it is very possible 00:29:10.100 --> 00:29:13.510 align:start position:0% done yet even though it is very possible even<00:29:10.640> today<00:29:11.450> without<00:29:11.900> making<00:29:12.890> any<00:29:13.070> changes 00:29:13.510 --> 00:29:13.520 align:start position:0% even today without making any changes 00:29:13.520 --> 00:29:15.550 align:start position:0% even today without making any changes whatsoever<00:29:13.790> to<00:29:14.450> consensus<00:29:15.020> at<00:29:15.200> all 00:29:15.550 --> 00:29:15.560 align:start position:0% whatsoever to consensus at all 00:29:15.560 --> 00:29:17.380 align:start position:0% whatsoever to consensus at all you<00:29:16.250> know<00:29:16.340> just<00:29:16.580> use<00:29:16.670> a<00:29:16.700> smart<00:29:16.970> contract<00:29:17.270> and 00:29:17.380 --> 00:29:17.390 align:start position:0% you know just use a smart contract and 00:29:17.390 --> 00:29:20.830 align:start position:0% you know just use a smart contract and do<00:29:17.450> a<00:29:17.480> multiset<00:29:18.050> yeah<00:29:18.770> for<00:29:19.730> me<00:29:19.910> and<00:29:20.300> like<00:29:20.660> some 00:29:20.830 --> 00:29:20.840 align:start position:0% do a multiset yeah for me and like some 00:29:20.840 --> 00:29:21.760 align:start position:0% do a multiset yeah for me and like some of<00:29:20.900> the<00:29:20.960> conversations<00:29:21.440> we've<00:29:21.590> had<00:29:21.620> about 00:29:21.760 --> 00:29:21.770 align:start position:0% of the conversations we've had about 00:29:21.770 --> 00:29:23.650 align:start position:0% of the conversations we've had about this<00:29:22.070> sort<00:29:22.250> of<00:29:22.310> thing<00:29:22.520> on<00:29:22.790> aetherium<00:29:23.390> and 00:29:23.650 --> 00:29:23.660 align:start position:0% this sort of thing on aetherium and 00:29:23.660 --> 00:29:25.600 align:start position:0% this sort of thing on aetherium and Bitcoin<00:29:23.930> really<00:29:24.260> any<00:29:24.410> chain<00:29:24.920> is<00:29:25.190> this<00:29:25.400> is 00:29:25.600 --> 00:29:25.610 align:start position:0% Bitcoin really any chain is this is 00:29:25.610 --> 00:29:29.140 align:start position:0% Bitcoin really any chain is this is privacy<00:29:26.390> again<00:29:27.010> because<00:29:28.010> like<00:29:28.250> you<00:29:28.370> now<00:29:28.820> link 00:29:29.140 --> 00:29:29.150 align:start position:0% privacy again because like you now link 00:29:29.150 --> 00:29:30.730 align:start position:0% privacy again because like you now link all<00:29:29.300> your<00:29:29.480> sort<00:29:29.660> of<00:29:29.690> customers<00:29:30.170> together<00:29:30.320> in 00:29:30.730 --> 00:29:30.740 align:start position:0% all your sort of customers together in 00:29:30.740 --> 00:29:32.770 align:start position:0% all your sort of customers together in some<00:29:30.950> ways<00:29:31.130> and<00:29:31.550> we<00:29:32.090> want<00:29:32.330> to<00:29:32.420> generally 00:29:32.770 --> 00:29:32.780 align:start position:0% some ways and we want to generally 00:29:32.780 --> 00:29:34.090 align:start position:0% some ways and we want to generally prefer<00:29:33.080> that<00:29:33.230> like<00:29:33.440> we<00:29:33.590> like<00:29:33.740> to<00:29:33.860> sort<00:29:34.010> of 00:29:34.090 --> 00:29:34.100 align:start position:0% prefer that like we like to sort of 00:29:34.100 --> 00:29:35.920 align:start position:0% prefer that like we like to sort of default<00:29:34.430> to<00:29:34.580> privacy<00:29:34.880> and<00:29:35.000> try<00:29:35.450> and<00:29:35.570> maintain 00:29:35.920 --> 00:29:35.930 align:start position:0% default to privacy and try and maintain 00:29:35.930 --> 00:29:37.960 align:start position:0% default to privacy and try and maintain that<00:29:36.170> as<00:29:36.410> long<00:29:36.530> as<00:29:36.560> we<00:29:36.740> can<00:29:36.920> and<00:29:37.070> so<00:29:37.220> when<00:29:37.760> sort 00:29:37.960 --> 00:29:37.970 align:start position:0% that as long as we can and so when sort 00:29:37.970 --> 00:29:38.980 align:start position:0% that as long as we can and so when sort of<00:29:38.030> batching<00:29:38.330> comes<00:29:38.510> up<00:29:38.660> and<00:29:38.810> that<00:29:38.900> that's 00:29:38.980 --> 00:29:38.990 align:start position:0% of batching comes up and that that's 00:29:38.990 --> 00:29:40.240 align:start position:0% of batching comes up and that that's always<00:29:39.170> the<00:29:39.380> thing<00:29:39.410> that<00:29:39.770> it<00:29:39.920> like<00:29:40.010> immature 00:29:40.240 --> 00:29:40.250 align:start position:0% always the thing that it like immature 00:29:40.250 --> 00:29:41.830 align:start position:0% always the thing that it like immature like<00:29:40.610> wallet<00:29:40.940> contracts<00:29:41.390> like<00:29:41.570> putting 00:29:41.830 --> 00:29:41.840 align:start position:0% like wallet contracts like putting 00:29:41.840 --> 00:29:43.600 align:start position:0% like wallet contracts like putting everything<00:29:42.140> in<00:29:42.320> one<00:29:42.440> place<00:29:42.680> and<00:29:42.950> maybe<00:29:43.430> just 00:29:43.600 --> 00:29:43.610 align:start position:0% everything in one place and maybe just 00:29:43.610 --> 00:29:44.920 align:start position:0% everything in one place and maybe just the<00:29:43.730> theorems<00:29:44.030> the<00:29:44.090> wrong<00:29:44.300> chain<00:29:44.570> for<00:29:44.840> the 00:29:44.920 --> 00:29:44.930 align:start position:0% the theorems the wrong chain for the 00:29:44.930 --> 00:29:47.140 align:start position:0% the theorems the wrong chain for the types<00:29:45.110> of<00:29:45.290> things<00:29:45.470> that<00:29:45.820> that<00:29:46.820> I'm<00:29:46.940> talking 00:29:47.140 --> 00:29:47.150 align:start position:0% types of things that that I'm talking 00:29:47.150 --> 00:29:48.700 align:start position:0% types of things that that I'm talking about<00:29:47.360> it<00:29:47.690> I<00:29:47.780> think<00:29:48.020> there's<00:29:48.140> ways<00:29:48.260> we<00:29:48.290> can<00:29:48.560> get 00:29:48.700 --> 00:29:48.710 align:start position:0% about it I think there's ways we can get 00:29:48.710 --> 00:29:53.110 align:start position:0% about it I think there's ways we can get there<00:29:48.920> but<00:29:49.640> for<00:29:50.600> me<00:29:50.720> I<00:29:51.140> haven't<00:29:51.530> seen<00:29:52.190> it<00:29:52.370> and 00:29:53.110 --> 00:29:53.120 align:start position:0% there but for me I haven't seen it and 00:29:53.120 --> 00:29:54.790 align:start position:0% there but for me I haven't seen it and you<00:29:53.690> can<00:29:53.840> definitely<00:29:54.140> pull<00:29:54.320> it<00:29:54.410> off<00:29:54.530> like<00:29:54.680> you 00:29:54.790 --> 00:29:54.800 align:start position:0% you can definitely pull it off like you 00:29:54.800 --> 00:29:56.440 align:start position:0% you can definitely pull it off like you saw<00:29:55.040> the<00:29:55.100> smart<00:29:55.370> contracts<00:29:55.820> and<00:29:56.060> stuff<00:29:56.120> I 00:29:56.440 --> 00:29:56.450 align:start position:0% saw the smart contracts and stuff I 00:29:56.450 --> 00:29:58.720 align:start position:0% saw the smart contracts and stuff I think<00:29:56.810> that's<00:29:57.170> kind<00:29:57.320> of<00:29:57.380> the<00:29:57.530> cerium<00:29:58.010> for<00:29:58.640> lack 00:29:58.720 --> 00:29:58.730 align:start position:0% think that's kind of the cerium for lack 00:29:58.730 --> 00:30:00.640 align:start position:0% think that's kind of the cerium for lack of<00:29:58.760> a<00:29:58.880> better<00:29:58.910> word<00:29:59.150> purest<00:29:59.660> answer<00:30:00.110> to<00:30:00.380> like 00:30:00.640 --> 00:30:00.650 align:start position:0% of a better word purest answer to like 00:30:00.650 --> 00:30:03.220 align:start position:0% of a better word purest answer to like the<00:30:00.800> bathroom<00:30:01.190> question<00:30:01.640> is<00:30:01.960> when<00:30:02.960> you<00:30:03.080> just 00:30:03.220 --> 00:30:03.230 align:start position:0% the bathroom question is when you just 00:30:03.230 --> 00:30:04.960 align:start position:0% the bathroom question is when you just use<00:30:03.380> a<00:30:03.410> smart<00:30:03.710> contract<00:30:04.130> for<00:30:04.280> that<00:30:04.400> and<00:30:04.730> that's 00:30:04.960 --> 00:30:04.970 align:start position:0% use a smart contract for that and that's 00:30:04.970 --> 00:30:06.850 align:start position:0% use a smart contract for that and that's kind<00:30:05.390> of<00:30:05.480> aetherium<00:30:05.900> and<00:30:06.200> for<00:30:06.500> everything 00:30:06.850 --> 00:30:06.860 align:start position:0% kind of aetherium and for everything 00:30:06.860 --> 00:30:08.680 align:start position:0% kind of aetherium and for everything which<00:30:07.010> isn't<00:30:07.850> a<00:30:07.970> bad<00:30:08.090> thing<00:30:08.150> but<00:30:08.540> maybe 00:30:08.680 --> 00:30:08.690 align:start position:0% which isn't a bad thing but maybe 00:30:08.690 --> 00:30:09.910 align:start position:0% which isn't a bad thing but maybe there's<00:30:09.020> trade-offs<00:30:09.260> that<00:30:09.560> you<00:30:09.620> don't<00:30:09.800> want 00:30:09.910 --> 00:30:09.920 align:start position:0% there's trade-offs that you don't want 00:30:09.920 --> 00:30:11.170 align:start position:0% there's trade-offs that you don't want to<00:30:09.980> make<00:30:10.130> there<00:30:10.370> in<00:30:10.610> your<00:30:10.820> in<00:30:11.120> your 00:30:11.170 --> 00:30:11.180 align:start position:0% to make there in your in your 00:30:11.180 --> 00:30:13.660 align:start position:0% to make there in your in your server-side<00:30:11.660> architecture<00:30:12.290> that<00:30:12.620> we<00:30:12.740> so 00:30:13.660 --> 00:30:13.670 align:start position:0% server-side architecture that we so 00:30:13.670 --> 00:30:14.860 align:start position:0% server-side architecture that we so you're<00:30:13.790> saying<00:30:13.970> earlier<00:30:14.300> if<00:30:14.480> you<00:30:14.660> have<00:30:14.690> a 00:30:14.860 --> 00:30:14.870 align:start position:0% you're saying earlier if you have a 00:30:14.870 --> 00:30:17.320 align:start position:0% you're saying earlier if you have a wallet<00:30:15.170> contract<00:30:15.860> I<00:30:16.190> guess<00:30:16.730> it<00:30:16.850> becomes<00:30:17.090> very 00:30:17.320 --> 00:30:17.330 align:start position:0% wallet contract I guess it becomes very 00:30:17.330 --> 00:30:18.910 align:start position:0% wallet contract I guess it becomes very convenient<00:30:17.840> to<00:30:17.990> do<00:30:18.110> these<00:30:18.260> kinds<00:30:18.530> of<00:30:18.620> multi 00:30:18.910 --> 00:30:18.920 align:start position:0% convenient to do these kinds of multi 00:30:18.920 --> 00:30:20.680 align:start position:0% convenient to do these kinds of multi since<00:30:19.070> but<00:30:19.190> if<00:30:19.280> you<00:30:19.340> don't<00:30:19.610> then<00:30:19.940> there's<00:30:20.450> no 00:30:20.680 --> 00:30:20.690 align:start position:0% since but if you don't then there's no 00:30:20.690 --> 00:30:23.020 align:start position:0% since but if you don't then there's no like<00:30:21.110> alternative<00:30:21.740> mechanism<00:30:22.250> right<00:30:22.400> yeah 00:30:23.020 --> 00:30:23.030 align:start position:0% like alternative mechanism right yeah 00:30:23.030 --> 00:30:24.400 align:start position:0% like alternative mechanism right yeah you<00:30:23.090> could<00:30:23.360> theoretically<00:30:23.810> design<00:30:24.380> a 00:30:24.400 --> 00:30:24.410 align:start position:0% you could theoretically design a 00:30:24.410 --> 00:30:26.290 align:start position:0% you could theoretically design a function<00:30:25.070> calling<00:30:25.280> your<00:30:25.520> contract<00:30:26.060> that 00:30:26.290 --> 00:30:26.300 align:start position:0% function calling your contract that 00:30:26.300 --> 00:30:29.590 align:start position:0% function calling your contract that would<00:30:26.930> multi<00:30:27.500> send<00:30:27.800> to<00:30:28.640> a<00:30:28.970> list<00:30:29.300> of<00:30:29.420> addresses 00:30:29.590 --> 00:30:29.600 align:start position:0% would multi send to a list of addresses 00:30:29.600 --> 00:30:31.660 align:start position:0% would multi send to a list of addresses that<00:30:29.870> you<00:30:29.990> pass<00:30:30.200> it<00:30:30.410> okay<00:30:30.620> yeah<00:30:31.130> and<00:30:31.310> it's<00:30:31.550> all 00:30:31.660 --> 00:30:31.670 align:start position:0% that you pass it okay yeah and it's all 00:30:31.670 --> 00:30:32.980 align:start position:0% that you pass it okay yeah and it's all technically<00:30:32.120> the<00:30:32.210> same<00:30:32.330> aetherium<00:30:32.720> address 00:30:32.980 --> 00:30:32.990 align:start position:0% technically the same aetherium address 00:30:32.990 --> 00:30:34.780 align:start position:0% technically the same aetherium address but<00:30:33.230> then<00:30:33.380> it<00:30:33.530> just<00:30:33.560> happen<00:30:33.980> all<00:30:34.130> internal 00:30:34.780 --> 00:30:34.790 align:start position:0% but then it just happen all internal 00:30:34.790 --> 00:30:36.130 align:start position:0% but then it just happen all internal transactions<00:30:35.420> but<00:30:35.570> then<00:30:35.750> like<00:30:35.870> you<00:30:35.900> said 00:30:36.130 --> 00:30:36.140 align:start position:0% transactions but then like you said 00:30:36.140 --> 00:30:37.570 align:start position:0% transactions but then like you said they're<00:30:36.290> all<00:30:36.380> linked<00:30:36.590> together<00:30:36.740> and<00:30:37.130> well<00:30:37.490> you 00:30:37.570 --> 00:30:37.580 align:start position:0% they're all linked together and well you 00:30:37.580 --> 00:30:39.400 align:start position:0% they're all linked together and well you also<00:30:37.700> need<00:30:37.880> a<00:30:37.940> gallant<00:30:38.360> need<00:30:38.870> a<00:30:38.900> balance<00:30:39.320> on 00:30:39.400 --> 00:30:39.410 align:start position:0% also need a gallant need a balance on 00:30:39.410 --> 00:30:40.750 align:start position:0% also need a gallant need a balance on that<00:30:39.440> account<00:30:39.740> too<00:30:40.010> that's<00:30:40.370> like<00:30:40.490> sort<00:30:40.640> of 00:30:40.750 --> 00:30:40.760 align:start position:0% that account too that's like sort of 00:30:40.760 --> 00:30:42.130 align:start position:0% that account too that's like sort of public<00:30:41.090> and<00:30:41.240> probably<00:30:41.480> associated<00:30:41.720> with<00:30:42.020> you 00:30:42.130 --> 00:30:42.140 align:start position:0% public and probably associated with you 00:30:42.140 --> 00:30:44.740 align:start position:0% public and probably associated with you in<00:30:42.260> some<00:30:42.410> way<00:30:42.560> so<00:30:42.620> like<00:30:43.430> you<00:30:43.670> like<00:30:44.360> its<00:30:44.510> offense 00:30:44.740 --> 00:30:44.750 align:start position:0% in some way so like you like its offense 00:30:44.750 --> 00:30:46.420 align:start position:0% in some way so like you like its offense valued<00:30:45.080> structure<00:30:45.440> well<00:30:45.800> it<00:30:45.920> but<00:30:46.070> like<00:30:46.190> you 00:30:46.420 --> 00:30:46.430 align:start position:0% valued structure well it but like you 00:30:46.430 --> 00:30:47.830 align:start position:0% valued structure well it but like you don't<00:30:46.610> want<00:30:46.730> to<00:30:46.820> probably<00:30:47.330> have<00:30:47.540> all<00:30:47.690> your 00:30:47.830 --> 00:30:47.840 align:start position:0% don't want to probably have all your 00:30:47.840 --> 00:30:51.100 align:start position:0% don't want to probably have all your money<00:30:47.990> in<00:30:48.200> one<00:30:48.320> place<00:30:48.560> maybe<00:30:49.220> but<00:30:49.930> the<00:30:50.930> thing<00:30:51.080> I 00:30:51.100 --> 00:30:51.110 align:start position:0% money in one place maybe but the thing I 00:30:51.110 --> 00:30:53.440 align:start position:0% money in one place maybe but the thing I think<00:30:51.320> essentially<00:30:51.830> lots<00:30:52.250> of<00:30:52.400> I<00:30:52.730> mean<00:30:53.180> lots<00:30:53.360> of 00:30:53.440 --> 00:30:53.450 align:start position:0% think essentially lots of I mean lots of 00:30:53.450 --> 00:30:56.270 align:start position:0% think essentially lots of I mean lots of exchanges<00:30:53.990> end<00:30:54.320> up<00:30:54.740> with<00:30:54.920> a<00:30:54.950> hot<00:30:55.130> wallet<00:30:55.430> so 00:30:56.270 --> 00:30:56.280 align:start position:0% exchanges end up with a hot wallet so 00:30:56.280 --> 00:30:58.410 align:start position:0% exchanges end up with a hot wallet so and<00:30:57.280> and<00:30:57.520> I<00:30:57.700> think<00:30:57.880> what<00:30:57.970> shape-shift<00:30:58.330> it 00:30:58.410 --> 00:30:58.420 align:start position:0% and and I think what shape-shift it 00:30:58.420 --> 00:30:59.700 align:start position:0% and and I think what shape-shift it doesn't<00:30:58.660> matter<00:30:58.780> as<00:30:58.930> much<00:30:58.960> because<00:30:59.290> you<00:30:59.560> do 00:30:59.700 --> 00:30:59.710 align:start position:0% doesn't matter as much because you do 00:30:59.710 --> 00:31:01.680 align:start position:0% doesn't matter as much because you do like<00:30:59.890> one<00:31:00.040> transaction<00:31:00.340> at<00:31:00.580> a<00:31:00.640> time<00:31:00.850> right<00:31:01.630> so 00:31:01.680 --> 00:31:01.690 align:start position:0% like one transaction at a time right so 00:31:01.690 --> 00:31:03.210 align:start position:0% like one transaction at a time right so you'd<00:31:02.080> like<00:31:02.230> to<00:31:02.350> send<00:31:02.500> that<00:31:02.680> but<00:31:02.830> maybe<00:31:02.950> one<00:31:03.190> of 00:31:03.210 --> 00:31:03.220 align:start position:0% you'd like to send that but maybe one of 00:31:03.220 --> 00:31:04.970 align:start position:0% you'd like to send that but maybe one of the<00:31:03.340> reasons<00:31:03.370> why<00:31:03.700> people<00:31:03.730> don't<00:31:04.060> use<00:31:04.450> this<00:31:04.600> as 00:31:04.970 --> 00:31:04.980 align:start position:0% the reasons why people don't use this as 00:31:04.980 --> 00:31:07.500 align:start position:0% the reasons why people don't use this as much<00:31:05.980> in<00:31:06.130> aetherium<00:31:06.490> is<00:31:06.610> like<00:31:06.820> I<00:31:07.150> think<00:31:07.270> it 00:31:07.500 --> 00:31:07.510 align:start position:0% much in aetherium is like I think it 00:31:07.510 --> 00:31:09.960 align:start position:0% much in aetherium is like I think it theorem<00:31:07.780> people<00:31:08.080> are<00:31:08.410> really<00:31:08.650> used<00:31:08.860> to<00:31:09.160> seeing 00:31:09.960 --> 00:31:09.970 align:start position:0% theorem people are really used to seeing 00:31:09.970 --> 00:31:12.270 align:start position:0% theorem people are really used to seeing a<00:31:10.180> transaction<00:31:10.690> where<00:31:10.900> they<00:31:11.020> have<00:31:11.230> a<00:31:11.560> source 00:31:12.270 --> 00:31:12.280 align:start position:0% a transaction where they have a source 00:31:12.280 --> 00:31:14.790 align:start position:0% a transaction where they have a source and<00:31:12.580> a<00:31:12.640> destination<00:31:13.320> and<00:31:14.320> if<00:31:14.470> you<00:31:14.560> look<00:31:14.680> at 00:31:14.790 --> 00:31:14.800 align:start position:0% and a destination and if you look at 00:31:14.800 --> 00:31:16.710 align:start position:0% and a destination and if you look at that<00:31:14.950> like<00:31:15.460> either<00:31:15.820> scan<00:31:16.210> you<00:31:16.480> know<00:31:16.570> it's 00:31:16.710 --> 00:31:16.720 align:start position:0% that like either scan you know it's 00:31:16.720 --> 00:31:18.300 align:start position:0% that like either scan you know it's quite<00:31:17.110> clear<00:31:17.320> it's<00:31:17.530> always<00:31:17.770> got<00:31:17.920> a<00:31:17.950> source<00:31:18.190> at 00:31:18.300 --> 00:31:18.310 align:start position:0% quite clear it's always got a source at 00:31:18.310 --> 00:31:20.790 align:start position:0% quite clear it's always got a source at a<00:31:18.340> destination<00:31:18.810> so<00:31:19.810> it's<00:31:19.960> very<00:31:20.080> one-to-one 00:31:20.790 --> 00:31:20.800 align:start position:0% a destination so it's very one-to-one 00:31:20.800 --> 00:31:22.950 align:start position:0% a destination so it's very one-to-one how<00:31:21.490> people<00:31:21.820> like<00:31:22.240> the<00:31:22.360> mental<00:31:22.660> model<00:31:22.870> of<00:31:22.900> how 00:31:22.950 --> 00:31:22.960 align:start position:0% how people like the mental model of how 00:31:22.960 --> 00:31:25.620 align:start position:0% how people like the mental model of how they<00:31:23.110> think<00:31:23.290> about<00:31:23.350> the<00:31:23.650> transaction<00:31:24.630> you 00:31:25.620 --> 00:31:25.630 align:start position:0% they think about the transaction you 00:31:25.630 --> 00:31:27.480 align:start position:0% they think about the transaction you know<00:31:25.840> in<00:31:26.050> another<00:31:26.200> change<00:31:26.650> you<00:31:26.920> always<00:31:27.370> have 00:31:27.480 --> 00:31:27.490 align:start position:0% know in another change you always have 00:31:27.490 --> 00:31:29.910 align:start position:0% know in another change you always have both<00:31:27.610> developers<00:31:28.060> yeah<00:31:29.050> it's<00:31:29.230> also<00:31:29.380> I<00:31:29.650> think<00:31:29.710> a 00:31:29.910 --> 00:31:29.920 align:start position:0% both developers yeah it's also I think a 00:31:29.920 --> 00:31:32.010 align:start position:0% both developers yeah it's also I think a little<00:31:30.070> less<00:31:30.580> necessary<00:31:31.420> in<00:31:31.570> etherium 00:31:32.010 --> 00:31:32.020 align:start position:0% little less necessary in etherium 00:31:32.020 --> 00:31:33.600 align:start position:0% little less necessary in etherium because<00:31:32.590> like<00:31:32.770> we<00:31:32.890> talked<00:31:33.250> about<00:31:33.280> that<00:31:33.460> not 00:31:33.600 --> 00:31:33.610 align:start position:0% because like we talked about that not 00:31:33.610 --> 00:31:35.160 align:start position:0% because like we talked about that not stuff<00:31:33.850> earlier<00:31:34.150> in<00:31:34.330> a<00:31:34.420> theorem<00:31:34.690> you<00:31:34.780> can<00:31:34.840> do 00:31:35.160 --> 00:31:35.170 align:start position:0% stuff earlier in a theorem you can do 00:31:35.170 --> 00:31:38.670 align:start position:0% stuff earlier in a theorem you can do these<00:31:35.290> sort<00:31:35.500> of<00:31:36.510> serial<00:31:37.510> but<00:31:37.930> like<00:31:38.140> back<00:31:38.650> to 00:31:38.670 --> 00:31:38.680 align:start position:0% these sort of serial but like back to 00:31:38.680 --> 00:31:41.820 align:start position:0% these sort of serial but like back to back<00:31:38.980> sends<00:31:39.780> like<00:31:40.780> on<00:31:40.960> from<00:31:41.230> a<00:31:41.320> single<00:31:41.590> account 00:31:41.820 --> 00:31:41.830 align:start position:0% back sends like on from a single account 00:31:41.830 --> 00:31:43.170 align:start position:0% back sends like on from a single account right<00:31:42.130> if<00:31:42.250> you<00:31:42.310> just<00:31:42.460> increment<00:31:42.730> the<00:31:42.850> knot<00:31:43.000> so 00:31:43.170 --> 00:31:43.180 align:start position:0% right if you just increment the knot so 00:31:43.180 --> 00:31:44.640 align:start position:0% right if you just increment the knot so you<00:31:43.240> can<00:31:43.390> continue<00:31:43.720> to<00:31:43.990> like<00:31:44.140> to<00:31:44.290> send<00:31:44.470> from 00:31:44.640 --> 00:31:44.650 align:start position:0% you can continue to like to send from 00:31:44.650 --> 00:31:46.140 align:start position:0% you can continue to like to send from the<00:31:44.830> same<00:31:44.950> account<00:31:45.160> so<00:31:45.370> you<00:31:45.400> can<00:31:45.520> you<00:31:46.120> can 00:31:46.140 --> 00:31:46.150 align:start position:0% the same account so you can you can 00:31:46.150 --> 00:31:48.060 align:start position:0% the same account so you can you can queue<00:31:46.570> up<00:31:46.690> all<00:31:46.870> of<00:31:47.110> them<00:31:47.260> at<00:31:47.410> once<00:31:47.590> without<00:31:47.800> any 00:31:48.060 --> 00:31:48.070 align:start position:0% queue up all of them at once without any 00:31:48.070 --> 00:31:50.610 align:start position:0% queue up all of them at once without any sort<00:31:48.340> of<00:31:48.400> delay<00:31:48.730> or<00:31:49.090> is<00:31:49.420> like<00:31:49.570> on<00:31:49.870> Bitcoin<00:31:50.290> and 00:31:50.610 --> 00:31:50.620 align:start position:0% sort of delay or is like on Bitcoin and 00:31:50.620 --> 00:31:52.800 align:start position:0% sort of delay or is like on Bitcoin and that<00:31:50.920> style<00:31:51.130> of<00:31:51.310> chain<00:31:51.550> you<00:31:52.300> have<00:31:52.450> to<00:31:52.570> sort<00:31:52.780> of 00:31:52.800 --> 00:31:52.810 align:start position:0% that style of chain you have to sort of 00:31:52.810 --> 00:31:55.590 align:start position:0% that style of chain you have to sort of if<00:31:53.080> you<00:31:53.230> have<00:31:53.380> a<00:31:53.410> big<00:31:53.980> sort<00:31:54.340> of<00:31:54.400> input<00:31:54.700> you<00:31:55.450> have 00:31:55.590 --> 00:31:55.600 align:start position:0% if you have a big sort of input you have 00:31:55.600 --> 00:31:57.870 align:start position:0% if you have a big sort of input you have to<00:31:55.750> sort<00:31:55.930> of<00:31:56.070> wait<00:31:57.070> for<00:31:57.100> that<00:31:57.400> to<00:31:57.580> do<00:31:57.670> its<00:31:57.820> thing 00:31:57.870 --> 00:31:57.880 align:start position:0% to sort of wait for that to do its thing 00:31:57.880 --> 00:31:59.670 align:start position:0% to sort of wait for that to do its thing and<00:31:58.240> then<00:31:58.330> do<00:31:58.450> another<00:31:58.480> one<00:31:58.900> or<00:31:59.080> there's<00:31:59.620> other 00:31:59.670 --> 00:31:59.680 align:start position:0% and then do another one or there's other 00:31:59.680 --> 00:32:01.440 align:start position:0% and then do another one or there's other ways<00:31:59.800> you<00:31:59.890> can<00:32:00.040> do<00:32:00.130> it<00:32:00.250> but<00:32:00.370> it's<00:32:00.670> a<00:32:00.970> lot 00:32:01.440 --> 00:32:01.450 align:start position:0% ways you can do it but it's a lot 00:32:01.450 --> 00:32:02.520 align:start position:0% ways you can do it but it's a lot trickier<00:32:01.690> words<00:32:02.110> I<00:32:02.170> get<00:32:02.230> through<00:32:02.380> I'm<00:32:02.470> just 00:32:02.520 --> 00:32:02.530 align:start position:0% trickier words I get through I'm just 00:32:02.530 --> 00:32:03.930 align:start position:0% trickier words I get through I'm just like<00:32:02.770> just<00:32:02.920> keep<00:32:03.100> sending<00:32:03.520> from<00:32:03.700> the<00:32:03.790> same 00:32:03.930 --> 00:32:03.940 align:start position:0% like just keep sending from the same 00:32:03.940 --> 00:32:05.820 align:start position:0% like just keep sending from the same account<00:32:04.270> and<00:32:04.510> it'll<00:32:04.660> let<00:32:04.780> you<00:32:04.810> do<00:32:05.080> it<00:32:05.230> and<00:32:05.380> like 00:32:05.820 --> 00:32:05.830 align:start position:0% account and it'll let you do it and like 00:32:05.830 --> 00:32:07.410 align:start position:0% account and it'll let you do it and like it<00:32:05.980> should<00:32:06.160> generally<00:32:06.520> work<00:32:06.670> and<00:32:06.910> it<00:32:07.270> doesn't 00:32:07.410 --> 00:32:07.420 align:start position:0% it should generally work and it doesn't 00:32:07.420 --> 00:32:09.540 align:start position:0% it should generally work and it doesn't mean<00:32:07.630> too<00:32:08.260> much<00:32:08.440> of<00:32:08.560> a<00:32:08.620> problem<00:32:08.890> we've<00:32:09.040> seen<00:32:09.070> or 00:32:09.540 --> 00:32:09.550 align:start position:0% mean too much of a problem we've seen or 00:32:09.550 --> 00:32:11.670 align:start position:0% mean too much of a problem we've seen or like<00:32:09.850> any<00:32:10.060> sort<00:32:10.240> of<00:32:10.330> need<00:32:11.020> for<00:32:11.200> batching<00:32:11.560> it 00:32:11.670 --> 00:32:11.680 align:start position:0% like any sort of need for batching it 00:32:11.680 --> 00:32:13.590 align:start position:0% like any sort of need for batching it either<00:32:12.150> there's<00:32:13.150> something<00:32:13.330> like<00:32:13.390> gas 00:32:13.590 --> 00:32:13.600 align:start position:0% either there's something like gas 00:32:13.600 --> 00:32:15.750 align:start position:0% either there's something like gas savings<00:32:13.990> potentially<00:32:14.410> yeah<00:32:14.770> I<00:32:14.800> think<00:32:15.280> I<00:32:15.490> think 00:32:15.750 --> 00:32:15.760 align:start position:0% savings potentially yeah I think I think 00:32:15.760 --> 00:32:18.300 align:start position:0% savings potentially yeah I think I think that<00:32:16.060> that<00:32:16.420> like<00:32:16.720> the<00:32:16.870> gas<00:32:17.050> savings<00:32:17.560> um<00:32:17.830> I 00:32:18.300 --> 00:32:18.310 align:start position:0% that that like the gas savings um I 00:32:18.310 --> 00:32:20.310 align:start position:0% that that like the gas savings um I think<00:32:18.910> that<00:32:19.240> with<00:32:19.630> the<00:32:19.720> theorem<00:32:19.990> maybe<00:32:20.140> we 00:32:20.310 --> 00:32:20.320 align:start position:0% think that with the theorem maybe we 00:32:20.320 --> 00:32:21.980 align:start position:0% think that with the theorem maybe we aren't<00:32:20.530> as<00:32:20.680> mature<00:32:20.950> with<00:32:21.520> doing<00:32:21.790> gas 00:32:21.980 --> 00:32:21.990 align:start position:0% aren't as mature with doing gas 00:32:21.990 --> 00:32:25.560 align:start position:0% aren't as mature with doing gas optimization<00:32:23.280> you<00:32:24.280> know<00:32:24.400> with<00:32:25.120> Bitcoin<00:32:25.450> for 00:32:25.560 --> 00:32:25.570 align:start position:0% optimization you know with Bitcoin for 00:32:25.570 --> 00:32:26.970 align:start position:0% optimization you know with Bitcoin for example<00:32:25.960> because<00:32:26.170> things<00:32:26.380> are<00:32:26.500> so<00:32:26.530> expensive 00:32:26.970 --> 00:32:26.980 align:start position:0% example because things are so expensive 00:32:26.980 --> 00:32:29.130 align:start position:0% example because things are so expensive you<00:32:27.400> wanted<00:32:27.940> to<00:32:28.030> save<00:32:28.240> every<00:32:28.720> little<00:32:28.930> bit<00:32:29.020> you 00:32:29.130 --> 00:32:29.140 align:start position:0% you wanted to save every little bit you 00:32:29.140 --> 00:32:31.710 align:start position:0% you wanted to save every little bit you could<00:32:29.350> so<00:32:30.030> you're<00:32:31.030> paying<00:32:31.330> the<00:32:31.480> same<00:32:31.510> amount 00:32:31.710 --> 00:32:31.720 align:start position:0% could so you're paying the same amount 00:32:31.720 --> 00:32:35.430 align:start position:0% could so you're paying the same amount for<00:32:32.350> signatures<00:32:32.980> on<00:32:33.670> the<00:32:33.760> inputs<00:32:34.120> and<00:32:35.020> if<00:32:35.350> you 00:32:35.430 --> 00:32:35.440 align:start position:0% for signatures on the inputs and if you 00:32:35.440 --> 00:32:36.840 align:start position:0% for signatures on the inputs and if you can<00:32:35.560> send<00:32:35.770> to<00:32:35.860> ten<00:32:36.010> at<00:32:36.160> once<00:32:36.340> instead<00:32:36.520> of<00:32:36.700> one 00:32:36.840 --> 00:32:36.850 align:start position:0% can send to ten at once instead of one 00:32:36.850 --> 00:32:40.620 align:start position:0% can send to ten at once instead of one at<00:32:36.970> a<00:32:37.030> time<00:32:37.210> you<00:32:37.840> do<00:32:38.470> that<00:32:38.650> right<00:32:39.220> but<00:32:39.940> with<00:32:40.540> the 00:32:40.620 --> 00:32:40.630 align:start position:0% at a time you do that right but with the 00:32:40.630 --> 00:32:42.000 align:start position:0% at a time you do that right but with the theorem<00:32:40.930> I<00:32:40.990> think<00:32:41.200> it's<00:32:41.500> still<00:32:41.710> a<00:32:41.770> little<00:32:41.800> bit 00:32:42.000 --> 00:32:42.010 align:start position:0% theorem I think it's still a little bit 00:32:42.010 --> 00:32:43.680 align:start position:0% theorem I think it's still a little bit earlier<00:32:42.310> with<00:32:42.430> the<00:32:42.550> gas<00:32:42.970> savings<00:32:43.360> now<00:32:43.510> it's 00:32:43.680 --> 00:32:43.690 align:start position:0% earlier with the gas savings now it's 00:32:43.690 --> 00:32:46.650 align:start position:0% earlier with the gas savings now it's mostly<00:32:43.960> like<00:32:44.170> how<00:32:44.710> do<00:32:44.770> we<00:32:44.950> price<00:32:45.250> that<00:32:45.610> way<00:32:45.880> you 00:32:46.650 --> 00:32:46.660 align:start position:0% mostly like how do we price that way you 00:32:46.660 --> 00:32:49.650 align:start position:0% mostly like how do we price that way you know<00:32:47.010> get<00:32:48.010> gas<00:32:48.280> price<00:32:48.550> rather<00:32:49.090> than<00:32:49.300> actual 00:32:49.650 --> 00:32:49.660 align:start position:0% know get gas price rather than actual 00:32:49.660 --> 00:32:51.840 align:start position:0% know get gas price rather than actual guest<00:32:49.900> spent<00:32:50.200> and<00:32:50.920> really<00:32:51.250> for<00:32:51.430> all<00:32:51.550> of<00:32:51.730> these 00:32:51.840 --> 00:32:51.850 align:start position:0% guest spent and really for all of these 00:32:51.850 --> 00:32:54.150 align:start position:0% guest spent and really for all of these conversations<00:32:52.120> change<00:32:52.870> once<00:32:53.260> like<00:32:53.650> an<00:32:53.800> actual 00:32:54.150 --> 00:32:54.160 align:start position:0% conversations change once like an actual 00:32:54.160 --> 00:32:56.940 align:start position:0% conversations change once like an actual Caspar<00:32:55.150> sharding<00:32:55.660> some<00:32:56.140> scaling<00:32:56.530> solution 00:32:56.940 --> 00:32:56.950 align:start position:0% Caspar sharding some scaling solution 00:32:56.950 --> 00:32:58.980 align:start position:0% Caspar sharding some scaling solution gets<00:32:57.580> implemented<00:32:57.970> they're<00:32:58.690> all<00:32:58.810> just 00:32:58.980 --> 00:32:58.990 align:start position:0% gets implemented they're all just 00:32:58.990 --> 00:33:01.020 align:start position:0% gets implemented they're all just completely<00:32:59.710> different<00:32:59.950> because<00:33:00.370> we<00:33:00.880> have<00:33:00.910> a 00:33:01.020 --> 00:33:01.030 align:start position:0% completely different because we have a 00:33:01.030 --> 00:33:03.870 align:start position:0% completely different because we have a whole<00:33:01.360> new<00:33:01.540> set<00:33:01.690> of<00:33:01.720> problems<00:33:01.900> and<00:33:02.610> yes<00:33:03.610> yeah<00:33:03.850> I 00:33:03.870 --> 00:33:03.880 align:start position:0% whole new set of problems and yes yeah I 00:33:03.880 --> 00:33:05.310 align:start position:0% whole new set of problems and yes yeah I mean<00:33:04.060> our<00:33:04.180> next<00:33:04.570> aim<00:33:04.600> to<00:33:04.810> measure<00:33:04.990> that<00:33:05.230> would 00:33:05.310 --> 00:33:05.320 align:start position:0% mean our next aim to measure that would 00:33:05.320 --> 00:33:06.780 align:start position:0% mean our next aim to measure that would be<00:33:05.380> like<00:33:05.590> with<00:33:05.800> the<00:33:05.980> with<00:33:06.400> the<00:33:06.490> sharded 00:33:06.780 --> 00:33:06.790 align:start position:0% be like with the with the sharded 00:33:06.790 --> 00:33:09.690 align:start position:0% be like with the with the sharded network<00:33:07.030> could<00:33:07.120> be<00:33:07.180> much<00:33:07.360> more<00:33:07.480> complicated 00:33:09.690 --> 00:33:09.700 align:start position:0% network could be much more complicated 00:33:09.700 --> 00:33:11.039 align:start position:0% network could be much more complicated I<00:33:09.730> think<00:33:09.909> I<00:33:09.940> think<00:33:10.240> we<00:33:10.330> might<00:33:10.539> switch<00:33:10.809> gears 00:33:11.039 --> 00:33:11.049 align:start position:0% I think I think we might switch gears 00:33:11.049 --> 00:33:15.779 align:start position:0% I think I think we might switch gears here<00:33:11.289> a<00:33:11.350> little<00:33:11.889> bit<00:33:12.419> so<00:33:13.419> uh<00:33:14.159> we<00:33:15.159> got<00:33:15.309> here<00:33:15.580> I 00:33:15.779 --> 00:33:15.789 align:start position:0% here a little bit so uh we got here I 00:33:15.789 --> 00:33:17.399 align:start position:0% here a little bit so uh we got here I guess<00:33:16.269> I<00:33:16.389> would<00:33:16.510> love<00:33:16.630> to<00:33:16.690> talk<00:33:16.779> about<00:33:16.929> privacy 00:33:17.399 --> 00:33:17.409 align:start position:0% guess I would love to talk about privacy 00:33:17.409 --> 00:33:19.649 align:start position:0% guess I would love to talk about privacy with<00:33:17.559> you<00:33:17.649> guys<00:33:17.799> so<00:33:18.269> how<00:33:19.269> are<00:33:19.389> you<00:33:19.510> thinking 00:33:19.649 --> 00:33:19.659 align:start position:0% with you guys so how are you thinking 00:33:19.659 --> 00:33:21.539 align:start position:0% with you guys so how are you thinking about<00:33:19.870> it<00:33:20.139> what<00:33:20.260> do<00:33:20.320> you<00:33:20.380> think<00:33:20.799> the<00:33:21.010> status<00:33:21.279> of 00:33:21.539 --> 00:33:21.549 align:start position:0% about it what do you think the status of 00:33:21.549 --> 00:33:23.730 align:start position:0% about it what do you think the status of privacy<00:33:21.940> and<00:33:22.029> fungibility<00:33:22.450> is<00:33:22.750> in<00:33:23.409> general 00:33:23.730 --> 00:33:23.740 align:start position:0% privacy and fungibility is in general 00:33:23.740 --> 00:33:26.250 align:start position:0% privacy and fungibility is in general are<00:33:24.130> we<00:33:24.340> there<00:33:24.549> yet<00:33:24.929> what<00:33:25.929> are<00:33:25.960> some<00:33:26.139> of<00:33:26.200> the 00:33:26.250 --> 00:33:26.260 align:start position:0% are we there yet what are some of the 00:33:26.260 --> 00:33:29.220 align:start position:0% are we there yet what are some of the interesting<00:33:26.710> prospects<00:33:27.250> and<00:33:27.840> how<00:33:28.840> do<00:33:29.169> you 00:33:29.220 --> 00:33:29.230 align:start position:0% interesting prospects and how do you 00:33:29.230 --> 00:33:33.720 align:start position:0% interesting prospects and how do you trade<00:33:29.529> that<00:33:29.559> off<00:33:29.830> with<00:33:30.070> scaling<00:33:32.370> in<00:33:33.370> terms<00:33:33.610> of 00:33:33.720 --> 00:33:33.730 align:start position:0% trade that off with scaling in terms of 00:33:33.730 --> 00:33:35.340 align:start position:0% trade that off with scaling in terms of aetherium<00:33:34.120> we're<00:33:34.269> definitely<00:33:34.750> not<00:33:35.019> there<00:33:35.200> yet 00:33:35.340 --> 00:33:35.350 align:start position:0% aetherium we're definitely not there yet 00:33:35.350 --> 00:33:37.680 align:start position:0% aetherium we're definitely not there yet for<00:33:35.590> privacy<00:33:35.919> okay<00:33:36.190> definitely<00:33:37.120> not<00:33:37.480> there 00:33:37.680 --> 00:33:37.690 align:start position:0% for privacy okay definitely not there 00:33:37.690 --> 00:33:40.710 align:start position:0% for privacy okay definitely not there yet<00:33:37.840> but<00:33:38.169> it's<00:33:38.470> like<00:33:39.429> snarks<00:33:39.820> exist<00:33:40.210> now<00:33:40.419> but 00:33:40.710 --> 00:33:40.720 align:start position:0% yet but it's like snarks exist now but 00:33:40.720 --> 00:33:43.169 align:start position:0% yet but it's like snarks exist now but it's<00:33:41.080> it's<00:33:41.500> really<00:33:41.740> not<00:33:42.340> easy<00:33:42.580> to<00:33:42.760> use<00:33:42.789> unless 00:33:43.169 --> 00:33:43.179 align:start position:0% it's it's really not easy to use unless 00:33:43.179 --> 00:33:45.360 align:start position:0% it's it's really not easy to use unless you<00:33:43.419> have<00:33:43.539> PhD<00:33:44.350> and<00:33:44.529> even<00:33:44.769> then<00:33:44.919> it's<00:33:45.100> it's 00:33:45.360 --> 00:33:45.370 align:start position:0% you have PhD and even then it's it's 00:33:45.370 --> 00:33:49.259 align:start position:0% you have PhD and even then it's it's difficult<00:33:46.440> it's<00:33:47.440> it's<00:33:48.399> definitely<00:33:48.639> tricky 00:33:49.259 --> 00:33:49.269 align:start position:0% difficult it's it's definitely tricky 00:33:49.269 --> 00:33:51.210 align:start position:0% difficult it's it's definitely tricky and<00:33:49.450> really<00:33:50.080> they<00:33:50.200> are<00:33:50.230> there<00:33:51.010> best 00:33:51.210 --> 00:33:51.220 align:start position:0% and really they are there best 00:33:51.220 --> 00:33:53.820 align:start position:0% and really they are there best implementation<00:33:51.789> should<00:33:52.750> be<00:33:52.990> in<00:33:53.139> some<00:33:53.409> sort<00:33:53.679> of 00:33:53.820 --> 00:33:53.830 align:start position:0% implementation should be in some sort of 00:33:53.830 --> 00:33:57.000 align:start position:0% implementation should be in some sort of plasma<00:33:54.669> like<00:33:55.149> implementation<00:33:56.019> or<00:33:56.289> in<00:33:56.679> a<00:33:56.769> shard 00:33:57.000 --> 00:33:57.010 align:start position:0% plasma like implementation or in a shard 00:33:57.010 --> 00:34:00.240 align:start position:0% plasma like implementation or in a shard of<00:33:57.159> some<00:33:57.340> kind<00:33:57.610> so<00:33:57.820> it's<00:33:58.570> almost<00:33:59.260> a<00:33:59.710> catch-22 00:34:00.240 --> 00:34:00.250 align:start position:0% of some kind so it's almost a catch-22 00:34:00.250 --> 00:34:03.480 align:start position:0% of some kind so it's almost a catch-22 and<00:34:00.549> that<00:34:00.669> which<00:34:01.000> which<00:34:01.630> comes<00:34:01.899> first<00:34:02.490> scaling 00:34:03.480 --> 00:34:03.490 align:start position:0% and that which which comes first scaling 00:34:03.490 --> 00:34:07.259 align:start position:0% and that which which comes first scaling of<00:34:03.549> the<00:34:03.580> privacy<00:34:04.620> yeah<00:34:05.620> so<00:34:06.610> I<00:34:06.639> think<00:34:06.789> it's<00:34:07.059> not 00:34:07.259 --> 00:34:07.269 align:start position:0% of the privacy yeah so I think it's not 00:34:07.269 --> 00:34:10.409 align:start position:0% of the privacy yeah so I think it's not that<00:34:07.600> not<00:34:08.050> by<00:34:08.320> any<00:34:08.500> I<00:34:09.369> mean<00:34:09.609> you<00:34:09.730> can<00:34:09.909> see<00:34:10.149> how 00:34:10.409 --> 00:34:10.419 align:start position:0% that not by any I mean you can see how 00:34:10.419 --> 00:34:13.700 align:start position:0% that not by any I mean you can see how easy<00:34:11.379> it<00:34:11.560> is<00:34:11.649> to<00:34:11.800> track<00:34:12.040> you<00:34:12.520> know<00:34:12.609> I<00:34:12.879> think 00:34:13.700 --> 00:34:13.710 align:start position:0% easy it is to track you know I think 00:34:13.710 --> 00:34:15.659 align:start position:0% easy it is to track you know I think this<00:34:14.710> can<00:34:14.889> they<00:34:15.010> have<00:34:15.129> label<00:34:15.520> like 00:34:15.659 --> 00:34:15.669 align:start position:0% this can they have label like 00:34:15.669 --> 00:34:21.359 align:start position:0% this can they have label like shape-shift<00:34:16.119> one<00:34:17.819> shows<00:34:18.819> you<00:34:19.329> know<00:34:20.369> that's 00:34:21.359 --> 00:34:21.369 align:start position:0% shape-shift one shows you know that's 00:34:21.369 --> 00:34:23.700 align:start position:0% shape-shift one shows you know that's that's<00:34:22.359> the<00:34:22.510> most<00:34:22.659> public<00:34:22.960> think<00:34:23.109> of<00:34:23.169> a<00:34:23.260> thing 00:34:23.700 --> 00:34:23.710 align:start position:0% that's the most public think of a thing 00:34:23.710 --> 00:34:24.930 align:start position:0% that's the most public think of a thing I've<00:34:23.829> ever<00:34:23.919> seen 00:34:24.930 --> 00:34:24.940 align:start position:0% I've ever seen 00:34:24.940 --> 00:34:27.059 align:start position:0% I've ever seen having<00:34:25.750> said<00:34:25.960> that<00:34:25.990> I<00:34:26.409> mean<00:34:26.649> I<00:34:26.710> don't<00:34:26.859> feel 00:34:27.059 --> 00:34:27.069 align:start position:0% having said that I mean I don't feel 00:34:27.069 --> 00:34:30.119 align:start position:0% having said that I mean I don't feel like<00:34:27.369> you<00:34:27.490> can<00:34:27.639> really<00:34:27.790> trust<00:34:28.119> so<00:34:29.109> call<00:34:29.349> us<00:34:29.649> you 00:34:30.119 --> 00:34:30.129 align:start position:0% like you can really trust so call us you 00:34:30.129 --> 00:34:32.609 align:start position:0% like you can really trust so call us you know<00:34:30.250> pseudonymous<00:34:30.819> nosov<00:34:31.300> bitcoin<00:34:31.899> you<00:34:32.139> can 00:34:32.609 --> 00:34:32.619 align:start position:0% know pseudonymous nosov bitcoin you can 00:34:32.619 --> 00:34:35.250 align:start position:0% know pseudonymous nosov bitcoin you can always<00:34:32.770> almost<00:34:33.389> think<00:34:34.389> about<00:34:34.450> it<00:34:34.720> as<00:34:34.810> those 00:34:35.250 --> 00:34:35.260 align:start position:0% always almost think about it as those 00:34:35.260 --> 00:34:36.809 align:start position:0% always almost think about it as those that<00:34:35.470> those<00:34:35.770> transactions<00:34:36.280> will<00:34:36.399> be<00:34:36.520> review 00:34:36.809 --> 00:34:36.819 align:start position:0% that those transactions will be review 00:34:36.819 --> 00:34:39.389 align:start position:0% that those transactions will be review when<00:34:37.599> you<00:34:37.659> think<00:34:37.869> about<00:34:38.069> privacy<00:34:39.069> it's<00:34:39.220> not 00:34:39.389 --> 00:34:39.399 align:start position:0% when you think about privacy it's not 00:34:39.399 --> 00:34:42.149 align:start position:0% when you think about privacy it's not just<00:34:39.639> about<00:34:39.760> like<00:34:40.480> privacy<00:34:40.899> today<00:34:41.260> and<00:34:41.649> okay 00:34:42.149 --> 00:34:42.159 align:start position:0% just about like privacy today and okay 00:34:42.159 --> 00:34:43.349 align:start position:0% just about like privacy today and okay maybe<00:34:42.399> it's<00:34:42.520> a<00:34:42.550> little<00:34:42.730> bit<00:34:42.849> hard<00:34:43.030> to<00:34:43.149> track 00:34:43.349 --> 00:34:43.359 align:start position:0% maybe it's a little bit hard to track 00:34:43.359 --> 00:34:45.720 align:start position:0% maybe it's a little bit hard to track today<00:34:43.569> but<00:34:44.409> the<00:34:44.679> blockchain<00:34:44.889> is<00:34:45.159> forever 00:34:45.720 --> 00:34:45.730 align:start position:0% today but the blockchain is forever 00:34:45.730 --> 00:34:48.899 align:start position:0% today but the blockchain is forever right<00:34:45.970> so<00:34:46.210> so<00:34:46.810> you<00:34:46.869> going<00:34:47.710> back<00:34:47.859> going<00:34:48.490> forward 00:34:48.899 --> 00:34:48.909 align:start position:0% right so so you going back going forward 00:34:48.909 --> 00:34:50.819 align:start position:0% right so so you going back going forward like<00:34:49.060> five<00:34:49.300> years<00:34:49.329> later<00:34:49.750> all<00:34:50.169> of<00:34:50.470> that<00:34:50.619> data 00:34:50.819 --> 00:34:50.829 align:start position:0% like five years later all of that data 00:34:50.829 --> 00:34:51.659 align:start position:0% like five years later all of that data is<00:34:50.980> gonna<00:34:51.129> be<00:34:51.280> there 00:34:51.659 --> 00:34:51.669 align:start position:0% is gonna be there 00:34:51.669 --> 00:34:53.550 align:start position:0% is gonna be there so<00:34:51.819> you're<00:34:52.480> gonna<00:34:52.599> have<00:34:52.780> to<00:34:52.990> live<00:34:53.530> with 00:34:53.550 --> 00:34:53.560 align:start position:0% so you're gonna have to live with 00:34:53.560 --> 00:34:55.409 align:start position:0% so you're gonna have to live with whatever<00:34:53.829> you're<00:34:54.040> putting<00:34:54.280> on<00:34:54.399> on<00:34:54.639> that<00:34:55.119> today 00:34:55.409 --> 00:34:55.419 align:start position:0% whatever you're putting on on that today 00:34:55.419 --> 00:34:57.420 align:start position:0% whatever you're putting on on that today so<00:34:55.960> I<00:34:56.290> think<00:34:56.530> that's<00:34:56.770> a<00:34:56.859> key<00:34:57.010> you<00:34:57.310> know 00:34:57.420 --> 00:34:57.430 align:start position:0% so I think that's a key you know 00:34:57.430 --> 00:34:59.579 align:start position:0% so I think that's a key you know security<00:34:58.150> is<00:34:58.359> really<00:34:58.750> important<00:34:59.109> and<00:34:59.170> privacy 00:34:59.579 --> 00:34:59.589 align:start position:0% security is really important and privacy 00:34:59.589 --> 00:35:02.160 align:start position:0% security is really important and privacy is<00:34:59.680> one<00:34:59.710> of<00:35:00.130> you<00:35:00.640> know<00:35:00.760> one<00:35:01.300> of<00:35:01.329> those<00:35:01.540> those 00:35:02.160 --> 00:35:02.170 align:start position:0% is one of you know one of those those 00:35:02.170 --> 00:35:04.319 align:start position:0% is one of you know one of those those important<00:35:02.740> things<00:35:02.890> for<00:35:03.069> security<00:35:03.550> because<00:35:04.119> it 00:35:04.319 --> 00:35:04.329 align:start position:0% important things for security because it 00:35:04.329 --> 00:35:07.200 align:start position:0% important things for security because it makes<00:35:04.599> it<00:35:04.859> just<00:35:05.859> that<00:35:06.010> much<00:35:06.069> harder<00:35:06.579> to<00:35:06.790> secure 00:35:07.200 --> 00:35:07.210 align:start position:0% makes it just that much harder to secure 00:35:07.210 --> 00:35:08.900 align:start position:0% makes it just that much harder to secure something<00:35:07.420> if<00:35:07.630> you<00:35:07.720> have<00:35:07.900> a<00:35:08.140> very<00:35:08.380> big<00:35:08.560> target 00:35:08.900 --> 00:35:08.910 align:start position:0% something if you have a very big target 00:35:08.910 --> 00:35:13.950 align:start position:0% something if you have a very big target amongst<00:35:09.910> other<00:35:10.000> reasons<00:35:10.440> so<00:35:11.440> I<00:35:12.240> I<00:35:13.240> just<00:35:13.720> don't 00:35:13.950 --> 00:35:13.960 align:start position:0% amongst other reasons so I I just don't 00:35:13.960 --> 00:35:16.260 align:start position:0% amongst other reasons so I I just don't see<00:35:14.230> this<00:35:14.440> as<00:35:14.650> something<00:35:15.460> that<00:35:15.640> is<00:35:15.910> being 00:35:16.260 --> 00:35:16.270 align:start position:0% see this as something that is being 00:35:16.270 --> 00:35:18.480 align:start position:0% see this as something that is being worked<00:35:16.510> on<00:35:16.720> in<00:35:16.900> us<00:35:17.050> yet<00:35:17.440> from<00:35:17.770> a<00:35:17.920> theorem<00:35:18.280> I 00:35:18.480 --> 00:35:18.490 align:start position:0% worked on in us yet from a theorem I 00:35:18.490 --> 00:35:21.180 align:start position:0% worked on in us yet from a theorem I think<00:35:19.030> that<00:35:19.500> we<00:35:20.500> have<00:35:20.650> scalability 00:35:21.180 --> 00:35:21.190 align:start position:0% think that we have scalability 00:35:21.190 --> 00:35:22.010 align:start position:0% think that we have scalability challenges 00:35:22.010 --> 00:35:22.020 align:start position:0% challenges 00:35:22.020 --> 00:35:23.240 align:start position:0% challenges and<00:35:22.109> I<00:35:22.440> think<00:35:22.500> they're<00:35:22.680> gonna<00:35:22.770> go<00:35:22.920> after<00:35:23.040> those 00:35:23.240 --> 00:35:23.250 align:start position:0% and I think they're gonna go after those 00:35:23.250 --> 00:35:26.000 align:start position:0% and I think they're gonna go after those first<00:35:23.550> because<00:35:24.530> that<00:35:25.530> is<00:35:25.710> what<00:35:25.859> drives 00:35:26.000 --> 00:35:26.010 align:start position:0% first because that is what drives 00:35:26.010 --> 00:35:27.589 align:start position:0% first because that is what drives adoption<00:35:26.490> I<00:35:26.670> mean<00:35:27.000> whether<00:35:27.150> you<00:35:27.240> like<00:35:27.420> it<00:35:27.450> or 00:35:27.589 --> 00:35:27.599 align:start position:0% adoption I mean whether you like it or 00:35:27.599 --> 00:35:32.210 align:start position:0% adoption I mean whether you like it or not<00:35:28.010> they<00:35:29.010> want<00:35:29.190> to<00:35:29.280> drive<00:35:29.369> adoption<00:35:30.170> yeah<00:35:31.220> I'm 00:35:32.210 --> 00:35:32.220 align:start position:0% not they want to drive adoption yeah I'm 00:35:32.220 --> 00:35:33.829 align:start position:0% not they want to drive adoption yeah I'm really<00:35:32.460> excited<00:35:32.609> for<00:35:33.150> sort<00:35:33.300> of<00:35:33.330> the<00:35:33.390> prospects 00:35:33.829 --> 00:35:33.839 align:start position:0% really excited for sort of the prospects 00:35:33.839 --> 00:35:35.900 align:start position:0% really excited for sort of the prospects of<00:35:33.930> like<00:35:34.109> the<00:35:34.230> future<00:35:34.530> of<00:35:34.619> privacy<00:35:34.770> but<00:35:35.310> yeah<00:35:35.880> I 00:35:35.900 --> 00:35:35.910 align:start position:0% of like the future of privacy but yeah I 00:35:35.910 --> 00:35:37.970 align:start position:0% of like the future of privacy but yeah I don't<00:35:36.089> think<00:35:36.240> aetherium<00:35:36.660> is<00:35:36.750> doing<00:35:36.980> maybe 00:35:37.970 --> 00:35:37.980 align:start position:0% don't think aetherium is doing maybe 00:35:37.980 --> 00:35:40.430 align:start position:0% don't think aetherium is doing maybe enough<00:35:38.280> to<00:35:38.520> to<00:35:38.790> be<00:35:38.910> concerned<00:35:39.240> about<00:35:39.420> it<00:35:39.750> or<00:35:40.200> to 00:35:40.430 --> 00:35:40.440 align:start position:0% enough to to be concerned about it or to 00:35:40.440 --> 00:35:42.020 align:start position:0% enough to to be concerned about it or to like<00:35:40.650> there's<00:35:41.280> definitely<00:35:41.369> teams<00:35:41.790> in<00:35:41.970> the 00:35:42.020 --> 00:35:42.030 align:start position:0% like there's definitely teams in the 00:35:42.030 --> 00:35:44.450 align:start position:0% like there's definitely teams in the space<00:35:42.210> working<00:35:42.480> on<00:35:42.720> sort<00:35:42.930> of<00:35:43.020> off<00:35:43.680> chain<00:35:44.190> sort 00:35:44.450 --> 00:35:44.460 align:start position:0% space working on sort of off chain sort 00:35:44.460 --> 00:35:45.740 align:start position:0% space working on sort of off chain sort of<00:35:44.550> style<00:35:44.760> solutions<00:35:45.210> which<00:35:45.390> I<00:35:45.480> think<00:35:45.630> could 00:35:45.740 --> 00:35:45.750 align:start position:0% of style solutions which I think could 00:35:45.750 --> 00:35:47.540 align:start position:0% of style solutions which I think could be<00:35:45.780> really<00:35:45.869> interesting<00:35:46.310> but<00:35:47.310> just<00:35:47.460> the 00:35:47.540 --> 00:35:47.550 align:start position:0% be really interesting but just the 00:35:47.550 --> 00:35:49.010 align:start position:0% be really interesting but just the general<00:35:47.820> sort<00:35:48.089> of<00:35:48.150> blockchain<00:35:48.599> community<00:35:48.960> as 00:35:49.010 --> 00:35:49.020 align:start position:0% general sort of blockchain community as 00:35:49.020 --> 00:35:50.150 align:start position:0% general sort of blockchain community as a<00:35:49.080> whole<00:35:49.260> there's<00:35:49.589> a<00:35:49.680> lot<00:35:49.859> of<00:35:50.010> really 00:35:50.150 --> 00:35:50.160 align:start position:0% a whole there's a lot of really 00:35:50.160 --> 00:35:51.410 align:start position:0% a whole there's a lot of really interesting<00:35:50.310> stuff<00:35:50.580> going<00:35:50.910> on<00:35:51.000> right<00:35:51.240> you 00:35:51.410 --> 00:35:51.420 align:start position:0% interesting stuff going on right you 00:35:51.420 --> 00:35:53.329 align:start position:0% interesting stuff going on right you know<00:35:51.540> there's<00:35:52.050> all<00:35:52.260> the<00:35:52.440> dizzy<00:35:52.830> cash<00:35:53.010> and<00:35:53.220> such 00:35:53.329 --> 00:35:53.339 align:start position:0% know there's all the dizzy cash and such 00:35:53.339 --> 00:35:54.740 align:start position:0% know there's all the dizzy cash and such doing<00:35:53.609> all<00:35:53.760> the<00:35:53.880> snarks<00:35:54.210> and<00:35:54.359> then<00:35:54.510> there's 00:35:54.740 --> 00:35:54.750 align:start position:0% doing all the snarks and then there's 00:35:54.750 --> 00:35:56.930 align:start position:0% doing all the snarks and then there's you<00:35:54.900> know<00:35:54.990> starts<00:35:55.410> now<00:35:55.650> and<00:35:55.980> you<00:35:56.550> know<00:35:56.670> bullet 00:35:56.930 --> 00:35:56.940 align:start position:0% you know starts now and you know bullet 00:35:56.940 --> 00:35:58.490 align:start position:0% you know starts now and you know bullet proofs<00:35:57.119> and<00:35:57.359> all<00:35:57.690> sorts<00:35:57.900> of<00:35:57.930> things<00:35:58.109> happening 00:35:58.490 --> 00:35:58.500 align:start position:0% proofs and all sorts of things happening 00:35:58.500 --> 00:35:59.690 align:start position:0% proofs and all sorts of things happening but<00:35:58.710> I<00:35:58.920> think<00:35:59.130> you<00:35:59.190> brought<00:35:59.339> up<00:35:59.430> really<00:35:59.609> good 00:35:59.690 --> 00:35:59.700 align:start position:0% but I think you brought up really good 00:35:59.700 --> 00:36:01.790 align:start position:0% but I think you brought up really good point<00:35:59.940> that<00:35:59.970> about<00:36:00.270> like<00:36:00.450> this<00:36:01.440> sort<00:36:01.589> of<00:36:01.650> like 00:36:01.790 --> 00:36:01.800 align:start position:0% point that about like this sort of like 00:36:01.800 --> 00:36:03.920 align:start position:0% point that about like this sort of like foreverness<00:36:02.280> this<00:36:02.640> sort<00:36:02.820> of<00:36:02.880> infinite<00:36:03.630> sort 00:36:03.920 --> 00:36:03.930 align:start position:0% foreverness this sort of infinite sort 00:36:03.930 --> 00:36:05.240 align:start position:0% foreverness this sort of infinite sort of<00:36:04.020> data<00:36:04.560> thing<00:36:04.830> and<00:36:04.920> this<00:36:04.980> has<00:36:05.130> already 00:36:05.240 --> 00:36:05.250 align:start position:0% of data thing and this has already 00:36:05.250 --> 00:36:06.890 align:start position:0% of data thing and this has already happened<00:36:05.460> with<00:36:05.790> Manero<00:36:06.119> where<00:36:06.450> you<00:36:06.630> know<00:36:06.720> they 00:36:06.890 --> 00:36:06.900 align:start position:0% happened with Manero where you know they 00:36:06.900 --> 00:36:08.540 align:start position:0% happened with Manero where you know they had<00:36:07.020> some<00:36:07.320> sort<00:36:07.470> of<00:36:07.560> bug<00:36:07.740> where<00:36:08.010> you<00:36:08.130> could<00:36:08.280> in 00:36:08.540 --> 00:36:08.550 align:start position:0% had some sort of bug where you could in 00:36:08.550 --> 00:36:10.700 align:start position:0% had some sort of bug where you could in theory<00:36:08.760> sort<00:36:09.000> of<00:36:09.089> I<00:36:09.450> think<00:36:10.050> in<00:36:10.200> some<00:36:10.410> ways<00:36:10.560> you 00:36:10.700 --> 00:36:10.710 align:start position:0% theory sort of I think in some ways you 00:36:10.710 --> 00:36:12.500 align:start position:0% theory sort of I think in some ways you could<00:36:10.859> I<00:36:10.890> don't<00:36:11.010> know<00:36:11.280> the<00:36:11.369> details<00:36:11.490> but<00:36:11.970> you 00:36:12.500 --> 00:36:12.510 align:start position:0% could I don't know the details but you 00:36:12.510 --> 00:36:13.700 align:start position:0% could I don't know the details but you could<00:36:12.660> effectively<00:36:13.020> like<00:36:13.320> sort<00:36:13.530> of<00:36:13.560> D 00:36:13.700 --> 00:36:13.710 align:start position:0% could effectively like sort of D 00:36:13.710 --> 00:36:15.440 align:start position:0% could effectively like sort of D anonymize<00:36:14.190> some<00:36:14.460> of<00:36:14.550> their<00:36:14.730> transaction 00:36:15.440 --> 00:36:15.450 align:start position:0% anonymize some of their transaction 00:36:15.450 --> 00:36:17.450 align:start position:0% anonymize some of their transaction history<00:36:15.540> because<00:36:16.440> of<00:36:16.619> some<00:36:17.040> sort<00:36:17.250> of<00:36:17.310> you<00:36:17.430> know 00:36:17.450 --> 00:36:17.460 align:start position:0% history because of some sort of you know 00:36:17.460 --> 00:36:20.390 align:start position:0% history because of some sort of you know vulnerability<00:36:18.300> there<00:36:18.510> and<00:36:19.070> that's<00:36:20.070> sort<00:36:20.310> of 00:36:20.390 --> 00:36:20.400 align:start position:0% vulnerability there and that's sort of 00:36:20.400 --> 00:36:21.980 align:start position:0% vulnerability there and that's sort of already<00:36:20.640> happened<00:36:21.270> and<00:36:21.450> so<00:36:21.540> in<00:36:21.690> a<00:36:21.780> lot<00:36:21.810> of 00:36:21.980 --> 00:36:21.990 align:start position:0% already happened and so in a lot of 00:36:21.990 --> 00:36:24.320 align:start position:0% already happened and so in a lot of those<00:36:22.230> new<00:36:22.680> cryptography<00:36:23.220> it's<00:36:23.460> also<00:36:23.640> new<00:36:24.060> and 00:36:24.320 --> 00:36:24.330 align:start position:0% those new cryptography it's also new and 00:36:24.330 --> 00:36:25.910 align:start position:0% those new cryptography it's also new and you<00:36:24.960> know<00:36:25.050> most<00:36:25.260> of<00:36:25.349> your<00:36:25.440> target<00:36:25.710> for<00:36:25.800> these 00:36:25.910 --> 00:36:25.920 align:start position:0% you know most of your target for these 00:36:25.920 --> 00:36:27.530 align:start position:0% you know most of your target for these things<00:36:26.130> like<00:36:26.280> fairly<00:36:26.730> like<00:36:27.000> well-established 00:36:27.530 --> 00:36:27.540 align:start position:0% things like fairly like well-established 00:36:27.540 --> 00:36:29.510 align:start position:0% things like fairly like well-established tested<00:36:28.320> and<00:36:28.440> stuff<00:36:28.619> and<00:36:28.890> so<00:36:28.950> we<00:36:28.980> do<00:36:29.190> these<00:36:29.310> you 00:36:29.510 --> 00:36:29.520 align:start position:0% tested and stuff and so we do these you 00:36:29.520 --> 00:36:31.370 align:start position:0% tested and stuff and so we do these you know<00:36:29.580> security<00:36:30.119> audits<00:36:30.510> but<00:36:30.630> a<00:36:30.869> lot<00:36:31.200> of<00:36:31.290> it's 00:36:31.370 --> 00:36:31.380 align:start position:0% know security audits but a lot of it's 00:36:31.380 --> 00:36:33.470 align:start position:0% know security audits but a lot of it's also<00:36:31.500> still<00:36:31.800> backed<00:36:32.010> by<00:36:32.250> this<00:36:32.310> this<00:36:32.790> there's<00:36:33.420> a 00:36:33.470 --> 00:36:33.480 align:start position:0% also still backed by this this there's a 00:36:33.480 --> 00:36:35.599 align:start position:0% also still backed by this this there's a word<00:36:33.720> for<00:36:33.990> it<00:36:34.109> but<00:36:34.260> this<00:36:34.470> idea<00:36:34.619> of<00:36:34.859> like<00:36:35.310> it 00:36:35.599 --> 00:36:35.609 align:start position:0% word for it but this idea of like it 00:36:35.609 --> 00:36:37.130 align:start position:0% word for it but this idea of like it hasn't<00:36:35.820> been<00:36:35.940> broken<00:36:36.150> yet<00:36:36.330> and<00:36:36.690> a<00:36:36.750> lot<00:36:36.990> of 00:36:37.130 --> 00:36:37.140 align:start position:0% hasn't been broken yet and a lot of 00:36:37.140 --> 00:36:38.870 align:start position:0% hasn't been broken yet and a lot of people<00:36:37.440> have<00:36:37.530> tried<00:36:37.800> we<00:36:38.160> can't<00:36:38.369> prove<00:36:38.670> it's 00:36:38.870 --> 00:36:38.880 align:start position:0% people have tried we can't prove it's 00:36:38.880 --> 00:36:40.130 align:start position:0% people have tried we can't prove it's totally<00:36:39.210> secure<00:36:39.510> but<00:36:39.630> we<00:36:39.690> think<00:36:39.839> it's<00:36:39.990> pretty 00:36:40.130 --> 00:36:40.140 align:start position:0% totally secure but we think it's pretty 00:36:40.140 --> 00:36:41.690 align:start position:0% totally secure but we think it's pretty good<00:36:40.380> and<00:36:40.560> so<00:36:40.950> we'll<00:36:41.070> keep<00:36:41.190> using<00:36:41.430> it<00:36:41.609> until 00:36:41.690 --> 00:36:41.700 align:start position:0% good and so we'll keep using it until 00:36:41.700 --> 00:36:44.329 align:start position:0% good and so we'll keep using it until then<00:36:42.060> and<00:36:42.900> a<00:36:43.290> lot<00:36:43.500> of<00:36:43.589> the<00:36:43.650> newer<00:36:43.800> stuff<00:36:43.859> Reyes 00:36:44.329 --> 00:36:44.339 align:start position:0% then and a lot of the newer stuff Reyes 00:36:44.339 --> 00:36:45.680 align:start position:0% then and a lot of the newer stuff Reyes imagine<00:36:45.030> would<00:36:45.089> have<00:36:45.240> like<00:36:45.359> similar 00:36:45.680 --> 00:36:45.690 align:start position:0% imagine would have like similar 00:36:45.690 --> 00:36:47.810 align:start position:0% imagine would have like similar properties<00:36:46.170> except<00:36:46.980> it<00:36:47.130> doesn't<00:36:47.310> have<00:36:47.460> like 00:36:47.810 --> 00:36:47.820 align:start position:0% properties except it doesn't have like 00:36:47.820 --> 00:36:49.730 align:start position:0% properties except it doesn't have like it's<00:36:48.060> not<00:36:48.210> battle<00:36:48.540> tested<00:36:48.900> in<00:36:48.990> that<00:36:49.080> way<00:36:49.290> and 00:36:49.730 --> 00:36:49.740 align:start position:0% it's not battle tested in that way and 00:36:49.740 --> 00:36:50.930 align:start position:0% it's not battle tested in that way and so<00:36:50.070> while<00:36:50.250> there's<00:36:50.430> like<00:36:50.520> really<00:36:50.790> smart 00:36:50.930 --> 00:36:50.940 align:start position:0% so while there's like really smart 00:36:50.940 --> 00:36:52.640 align:start position:0% so while there's like really smart people<00:36:51.240> doing<00:36:51.420> it<00:36:51.660> in<00:36:51.750> developing<00:36:52.230> this<00:36:52.410> stuff 00:36:52.640 --> 00:36:52.650 align:start position:0% people doing it in developing this stuff 00:36:52.650 --> 00:36:55.430 align:start position:0% people doing it in developing this stuff I<00:36:52.890> think<00:36:53.520> that's<00:36:53.670> a<00:36:53.760> really<00:36:54.270> like<00:36:54.599> big<00:36:55.020> sort<00:36:55.380> of 00:36:55.430 --> 00:36:55.440 align:start position:0% I think that's a really like big sort of 00:36:55.440 --> 00:36:58.430 align:start position:0% I think that's a really like big sort of risk<00:36:55.950> in<00:36:56.250> general<00:36:56.760> to<00:36:56.970> it<00:36:57.150> but<00:36:58.140> I<00:36:58.170> think<00:36:58.260> it's 00:36:58.430 --> 00:36:58.440 align:start position:0% risk in general to it but I think it's 00:36:58.440 --> 00:36:59.690 align:start position:0% risk in general to it but I think it's definitely<00:36:58.560> a<00:36:58.800> worthy<00:36:59.010> goal<00:36:59.160> that<00:36:59.520> we<00:36:59.640> should 00:36:59.690 --> 00:36:59.700 align:start position:0% definitely a worthy goal that we should 00:36:59.700 --> 00:37:01.730 align:start position:0% definitely a worthy goal that we should we<00:37:00.270> should<00:37:00.420> go<00:37:00.540> for<00:37:00.780> as<00:37:00.990> you<00:37:01.170> know<00:37:01.260> businesses 00:37:01.730 --> 00:37:01.740 align:start position:0% we should go for as you know businesses 00:37:01.740 --> 00:37:04.070 align:start position:0% we should go for as you know businesses and<00:37:01.920> anybody<00:37:02.220> wanting<00:37:02.460> to<00:37:02.580> build<00:37:02.700> on<00:37:02.880> this<00:37:03.080> you 00:37:04.070 --> 00:37:04.080 align:start position:0% and anybody wanting to build on this you 00:37:04.080 --> 00:37:05.420 align:start position:0% and anybody wanting to build on this you know<00:37:04.170> I<00:37:04.230> don't<00:37:04.260> want<00:37:04.500> my<00:37:04.589> whole<00:37:04.770> history<00:37:05.160> to<00:37:05.339> be 00:37:05.420 --> 00:37:05.430 align:start position:0% know I don't want my whole history to be 00:37:05.430 --> 00:37:07.040 align:start position:0% know I don't want my whole history to be for<00:37:05.609> everybody<00:37:05.820> to<00:37:06.150> read<00:37:06.300> anytime<00:37:06.660> I<00:37:06.690> send 00:37:07.040 --> 00:37:07.050 align:start position:0% for everybody to read anytime I send 00:37:07.050 --> 00:37:08.240 align:start position:0% for everybody to read anytime I send somebody<00:37:07.380> something<00:37:07.619> from<00:37:07.859> any<00:37:07.980> of<00:37:08.070> my<00:37:08.190> you 00:37:08.240 --> 00:37:08.250 align:start position:0% somebody something from any of my you 00:37:08.250 --> 00:37:09.410 align:start position:0% somebody something from any of my you know<00:37:08.369> aetherium<00:37:08.700> wallets<00:37:09.119> they<00:37:09.240> can 00:37:09.410 --> 00:37:09.420 align:start position:0% know aetherium wallets they can 00:37:09.420 --> 00:37:11.030 align:start position:0% know aetherium wallets they can potentially<00:37:10.260> see<00:37:10.470> my<00:37:10.560> whole<00:37:10.710> transaction 00:37:11.030 --> 00:37:11.040 align:start position:0% potentially see my whole transaction 00:37:11.040 --> 00:37:12.650 align:start position:0% potentially see my whole transaction history<00:37:11.250> and<00:37:11.670> I<00:37:11.880> could<00:37:12.060> split<00:37:12.210> it<00:37:12.300> up<00:37:12.420> in<00:37:12.540> all 00:37:12.650 --> 00:37:12.660 align:start position:0% history and I could split it up in all 00:37:12.660 --> 00:37:14.060 align:start position:0% history and I could split it up in all sorts<00:37:12.900> of<00:37:12.960> addresses<00:37:13.410> and<00:37:13.440> try<00:37:13.710> and<00:37:13.830> do<00:37:13.950> that 00:37:14.060 --> 00:37:14.070 align:start position:0% sorts of addresses and try and do that 00:37:14.070 --> 00:37:15.920 align:start position:0% sorts of addresses and try and do that but<00:37:14.369> then<00:37:14.760> it's<00:37:14.940> it's<00:37:15.089> like<00:37:15.450> that<00:37:15.630> problems 00:37:15.920 --> 00:37:15.930 align:start position:0% but then it's it's like that problems 00:37:15.930 --> 00:37:17.089 align:start position:0% but then it's it's like that problems describe<00:37:16.170> barely<00:37:16.440> even<00:37:16.500> like<00:37:16.770> a<00:37:16.830> just 00:37:17.089 --> 00:37:17.099 align:start position:0% describe barely even like a just 00:37:17.099 --> 00:37:18.740 align:start position:0% describe barely even like a just individual<00:37:17.580> level<00:37:17.880> not<00:37:18.089> even<00:37:18.300> the<00:37:18.420> exchange 00:37:18.740 --> 00:37:18.750 align:start position:0% individual level not even the exchange 00:37:18.750 --> 00:37:20.870 align:start position:0% individual level not even the exchange level<00:37:19.050> of<00:37:19.260> well<00:37:20.040> that's<00:37:20.339> really<00:37:20.670> complicated 00:37:20.870 --> 00:37:20.880 align:start position:0% level of well that's really complicated 00:37:20.880 --> 00:37:24.980 align:start position:0% level of well that's really complicated to<00:37:21.240> manage<00:37:21.450> it<00:37:22.200> was<00:37:22.320> expensive<00:37:22.650> just<00:37:23.040> few<00:37:23.280> eyes 00:37:24.980 --> 00:37:24.990 align:start position:0% to manage it was expensive just few eyes 00:37:24.990 --> 00:37:29.120 align:start position:0% to manage it was expensive just few eyes cool<00:37:26.150> alright<00:37:27.150> so<00:37:27.510> so<00:37:28.110> another<00:37:28.800> easier 00:37:29.120 --> 00:37:29.130 align:start position:0% cool alright so so another easier 00:37:29.130 --> 00:37:30.890 align:start position:0% cool alright so so another easier question<00:37:29.520> here<00:37:29.670> but<00:37:29.820> what<00:37:30.330> are<00:37:30.390> you<00:37:30.450> guys<00:37:30.540> most 00:37:30.890 --> 00:37:30.900 align:start position:0% question here but what are you guys most 00:37:30.900 --> 00:37:32.240 align:start position:0% question here but what are you guys most excited<00:37:31.110> about<00:37:31.530> with<00:37:31.770> respect<00:37:31.920> to<00:37:32.160> your 00:37:32.240 --> 00:37:32.250 align:start position:0% excited about with respect to your 00:37:32.250 --> 00:37:38.210 align:start position:0% excited about with respect to your theorem<00:37:34.670> it's<00:37:35.670> a<00:37:35.760> good<00:37:35.910> question<00:37:36.090> I<00:37:37.220> would 00:37:38.210 --> 00:37:38.220 align:start position:0% theorem it's a good question I would 00:37:38.220 --> 00:37:40.730 align:start position:0% theorem it's a good question I would like<00:37:39.180> as<00:37:39.390> a<00:37:39.420> something<00:37:40.020> we<00:37:40.230> would<00:37:40.320> like<00:37:40.470> to<00:37:40.500> see 00:37:40.730 --> 00:37:40.740 align:start position:0% like as a something we would like to see 00:37:40.740 --> 00:37:42.050 align:start position:0% like as a something we would like to see in<00:37:40.890> there<00:37:41.070> or<00:37:41.250> is<00:37:41.430> it<00:37:41.460> something<00:37:41.850> you<00:37:41.970> would 00:37:42.050 --> 00:37:42.060 align:start position:0% in there or is it something you would 00:37:42.060 --> 00:37:43.580 align:start position:0% in there or is it something you would like<00:37:42.180> to<00:37:42.330> see<00:37:42.510> some<00:37:42.750> project<00:37:43.200> that<00:37:43.350> you<00:37:43.410> think 00:37:43.580 --> 00:37:43.590 align:start position:0% like to see some project that you think 00:37:43.590 --> 00:37:45.500 align:start position:0% like to see some project that you think is<00:37:43.680> interesting<00:37:43.860> or<00:37:44.250> some<00:37:44.460> you<00:37:44.910> know<00:37:45.030> future 00:37:45.500 --> 00:37:45.510 align:start position:0% is interesting or some you know future 00:37:45.510 --> 00:37:47.600 align:start position:0% is interesting or some you know future prospect<00:37:46.200> are<00:37:46.800> you<00:37:46.890> really<00:37:47.100> looking<00:37:47.310> forward 00:37:47.600 --> 00:37:47.610 align:start position:0% prospect are you really looking forward 00:37:47.610 --> 00:37:53.000 align:start position:0% prospect are you really looking forward to<00:37:47.730> I<00:37:48.470> definitely<00:37:49.470> think<00:37:50.130> that<00:37:51.110> for<00:37:52.110> me<00:37:52.230> it<00:37:52.350> it 00:37:53.000 --> 00:37:53.010 align:start position:0% to I definitely think that for me it it 00:37:53.010 --> 00:37:54.170 align:start position:0% to I definitely think that for me it it probably<00:37:53.340> goes<00:37:53.460> back<00:37:53.490> to<00:37:53.730> the<00:37:53.820> whole<00:37:53.970> nonce 00:37:54.170 --> 00:37:54.180 align:start position:0% probably goes back to the whole nonce 00:37:54.180 --> 00:37:55.880 align:start position:0% probably goes back to the whole nonce thing<00:37:54.420> that<00:37:54.540> we<00:37:54.630> kind<00:37:55.020> of<00:37:55.170> started<00:37:55.440> with<00:37:55.590> it's 00:37:55.880 --> 00:37:55.890 align:start position:0% thing that we kind of started with it's 00:37:55.890 --> 00:37:59.210 align:start position:0% thing that we kind of started with it's that's<00:37:56.610> a<00:37:57.030> one<00:37:58.020> huge<00:37:58.380> pain<00:37:58.710> point<00:37:58.740> and 00:37:59.210 --> 00:37:59.220 align:start position:0% that's a one huge pain point and 00:37:59.220 --> 00:38:02.000 align:start position:0% that's a one huge pain point and something<00:37:59.850> some<00:38:00.510> solution<00:38:00.960> to<00:38:01.140> that<00:38:01.170> even<00:38:01.950> at 00:38:02.000 --> 00:38:02.010 align:start position:0% something some solution to that even at 00:38:02.010 --> 00:38:03.350 align:start position:0% something some solution to that even at the<00:38:02.100> protocol<00:38:02.460> level<00:38:02.520> would<00:38:02.760> be<00:38:02.820> very<00:38:03.210> nice 00:38:03.350 --> 00:38:03.360 align:start position:0% the protocol level would be very nice 00:38:03.360 --> 00:38:05.570 align:start position:0% the protocol level would be very nice it's<00:38:03.630> also<00:38:03.810> something<00:38:04.200> that<00:38:04.380> Jake<00:38:05.250> mentioned 00:38:05.570 --> 00:38:05.580 align:start position:0% it's also something that Jake mentioned 00:38:05.580 --> 00:38:07.040 align:start position:0% it's also something that Jake mentioned yesterday<00:38:05.730> when<00:38:06.060> we<00:38:06.150> were<00:38:06.240> chatting<00:38:06.450> was<00:38:06.810> it 00:38:07.040 --> 00:38:07.050 align:start position:0% yesterday when we were chatting was it 00:38:07.050 --> 00:38:09.830 align:start position:0% yesterday when we were chatting was it was<00:38:07.290> there's<00:38:08.300> it's<00:38:09.300> very<00:38:09.570> interesting 00:38:09.830 --> 00:38:09.840 align:start position:0% was there's it's very interesting 00:38:09.840 --> 00:38:12.710 align:start position:0% was there's it's very interesting concept<00:38:10.170> of<00:38:10.619> because<00:38:10.890> we<00:38:11.040> have<00:38:11.300> it's<00:38:12.300> more<00:38:12.630> of 00:38:12.710 --> 00:38:12.720 align:start position:0% concept of because we have it's more of 00:38:12.720 --> 00:38:14.330 align:start position:0% concept of because we have it's more of a<00:38:12.780> solution<00:38:12.990> to<00:38:13.200> the<00:38:13.320> internal<00:38:13.740> transactions 00:38:14.330 --> 00:38:14.340 align:start position:0% a solution to the internal transactions 00:38:14.340 --> 00:38:16.910 align:start position:0% a solution to the internal transactions parsing<00:38:14.880> problems<00:38:15.720> that<00:38:15.900> we've<00:38:16.020> had<00:38:16.170> where 00:38:16.910 --> 00:38:16.920 align:start position:0% parsing problems that we've had where 00:38:16.920 --> 00:38:19.400 align:start position:0% parsing problems that we've had where maybe<00:38:17.640> we<00:38:17.910> could<00:38:18.119> implement<00:38:18.390> events<00:38:19.230> at<00:38:19.320> the 00:38:19.400 --> 00:38:19.410 align:start position:0% maybe we could implement events at the 00:38:19.410 --> 00:38:21.500 align:start position:0% maybe we could implement events at the protocol<00:38:19.800> level<00:38:19.860> like<00:38:20.430> contract<00:38:20.940> type<00:38:21.150> events 00:38:21.500 --> 00:38:21.510 align:start position:0% protocol level like contract type events 00:38:21.510 --> 00:38:24.500 align:start position:0% protocol level like contract type events at<00:38:21.630> the<00:38:21.720> protocol<00:38:22.110> level<00:38:22.580> and<00:38:23.580> I<00:38:23.700> hope<00:38:24.450> I 00:38:24.500 --> 00:38:24.510 align:start position:0% at the protocol level and I hope I 00:38:24.510 --> 00:38:25.580 align:start position:0% at the protocol level and I hope I didn't<00:38:24.750> take<00:38:24.840> the<00:38:24.990> one<00:38:25.110> you<00:38:25.200> were<00:38:25.260> gonna<00:38:25.350> say 00:38:25.580 --> 00:38:25.590 align:start position:0% didn't take the one you were gonna say 00:38:25.590 --> 00:38:28.670 align:start position:0% didn't take the one you were gonna say just<00:38:25.619> now<00:38:25.890> but<00:38:26.220> no<00:38:27.000> no<00:38:27.330> I<00:38:27.360> think<00:38:27.720> yeah<00:38:27.900> yeah 00:38:28.670 --> 00:38:28.680 align:start position:0% just now but no no I think yeah yeah 00:38:28.680 --> 00:38:30.560 align:start position:0% just now but no no I think yeah yeah yeah<00:38:29.010> it's<00:38:29.310> a<00:38:29.430> really<00:38:29.580> interesting<00:38:29.760> idea<00:38:30.000> like 00:38:30.560 --> 00:38:30.570 align:start position:0% yeah it's a really interesting idea like 00:38:30.570 --> 00:38:32.150 align:start position:0% yeah it's a really interesting idea like this<00:38:30.750> I<00:38:30.930> like<00:38:31.260> because<00:38:31.380> I<00:38:31.530> think<00:38:31.710> it's<00:38:31.859> it's<00:38:32.070> a 00:38:32.150 --> 00:38:32.160 align:start position:0% this I like because I think it's it's a 00:38:32.160 --> 00:38:33.560 align:start position:0% this I like because I think it's it's a good<00:38:32.280> way<00:38:32.430> because<00:38:32.550> like<00:38:32.850> events<00:38:33.330> are<00:38:33.420> this 00:38:33.560 --> 00:38:33.570 align:start position:0% good way because like events are this 00:38:33.570 --> 00:38:34.910 align:start position:0% good way because like events are this later<00:38:33.780> known<00:38:34.050> density<00:38:34.260> and<00:38:34.590> people<00:38:34.800> know<00:38:34.890> I 00:38:34.910 --> 00:38:34.920 align:start position:0% later known density and people know I 00:38:34.920 --> 00:38:37.099 align:start position:0% later known density and people know I deal<00:38:35.220> with<00:38:35.280> them<00:38:35.490> give<00:38:35.730> the<00:38:35.820> vic-20<00:38:36.210> and<00:38:36.420> 7:21 00:38:37.099 --> 00:38:37.109 align:start position:0% deal with them give the vic-20 and 7:21 00:38:37.109 --> 00:38:38.300 align:start position:0% deal with them give the vic-20 and 7:21 and<00:38:37.290> they're<00:38:37.380> gonna<00:38:37.470> even<00:38:37.740> continue<00:38:38.130> to<00:38:38.220> be 00:38:38.300 --> 00:38:38.310 align:start position:0% and they're gonna even continue to be 00:38:38.310 --> 00:38:40.010 align:start position:0% and they're gonna even continue to be used<00:38:38.490> and<00:38:38.940> people<00:38:39.060> have<00:38:39.330> tools<00:38:39.600> and<00:38:39.900> stuff 00:38:40.010 --> 00:38:40.020 align:start position:0% used and people have tools and stuff 00:38:40.020 --> 00:38:41.120 align:start position:0% used and people have tools and stuff around<00:38:40.170> processing<00:38:40.740> them<00:38:40.859> in<00:38:40.980> really 00:38:41.120 --> 00:38:41.130 align:start position:0% around processing them in really 00:38:41.130 --> 00:38:42.620 align:start position:0% around processing them in really interesting<00:38:41.280> ways<00:38:41.520> and<00:38:41.940> so<00:38:42.359> I<00:38:42.390> think<00:38:42.480> that 00:38:42.620 --> 00:38:42.630 align:start position:0% interesting ways and so I think that 00:38:42.630 --> 00:38:44.480 align:start position:0% interesting ways and so I think that would<00:38:42.690> be<00:38:42.810> a<00:38:42.840> really<00:38:43.140> nice<00:38:43.290> way<00:38:43.560> that<00:38:43.590> you 00:38:44.480 --> 00:38:44.490 align:start position:0% would be a really nice way that you 00:38:44.490 --> 00:38:46.670 align:start position:0% would be a really nice way that you could<00:38:44.700> you<00:38:44.970> know<00:38:45.090> extend<00:38:45.570> you<00:38:46.320> could<00:38:46.470> bring 00:38:46.670 --> 00:38:46.680 align:start position:0% could you know extend you could bring 00:38:46.680 --> 00:38:48.440 align:start position:0% could you know extend you could bring these<00:38:46.980> sort<00:38:47.250> of<00:38:47.280> internal<00:38:47.850> transactions<00:38:48.330> out 00:38:48.440 --> 00:38:48.450 align:start position:0% these sort of internal transactions out 00:38:48.450 --> 00:38:50.540 align:start position:0% these sort of internal transactions out of<00:38:48.570> this<00:38:48.690> sort<00:38:48.900> of<00:38:48.960> mysterious<00:38:49.380> world<00:38:49.740> that 00:38:50.540 --> 00:38:50.550 align:start position:0% of this sort of mysterious world that 00:38:50.550 --> 00:38:52.940 align:start position:0% of this sort of mysterious world that you<00:38:50.609> need<00:38:50.730> to<00:38:50.850> parse<00:38:51.030> to<00:38:51.180> get<00:38:51.330> them<00:38:51.510> and<00:38:52.500> gets 00:38:52.940 --> 00:38:52.950 align:start position:0% you need to parse to get them and gets 00:38:52.950 --> 00:38:55.609 align:start position:0% you need to parse to get them and gets that's<00:38:53.460> one<00:38:53.670> way<00:38:53.820> yeah<00:38:54.510> I<00:38:54.810> think<00:38:55.109> it's<00:38:55.350> a<00:38:55.410> great 00:38:55.609 --> 00:38:55.619 align:start position:0% that's one way yeah I think it's a great 00:38:55.619 --> 00:38:58.310 align:start position:0% that's one way yeah I think it's a great it's<00:38:56.100> a<00:38:56.190> great<00:38:56.220> idea<00:38:56.760> I<00:38:57.119> mean<00:38:57.420> when<00:38:58.080> you<00:38:58.170> look 00:38:58.310 --> 00:38:58.320 align:start position:0% it's a great idea I mean when you look 00:38:58.320 --> 00:39:01.730 align:start position:0% it's a great idea I mean when you look at<00:38:58.440> it<00:38:59.060> what<00:39:00.060> what<00:39:00.630> people<00:39:00.810> what<00:39:01.440> a<00:39:01.470> lot<00:39:01.650> of 00:39:01.730 --> 00:39:01.740 align:start position:0% at it what what people what a lot of 00:39:01.740 --> 00:39:03.410 align:start position:0% at it what what people what a lot of people<00:39:01.950> actually<00:39:02.070> want<00:39:02.460> is<00:39:02.700> they<00:39:02.970> want<00:39:03.000> to<00:39:03.210> see 00:39:03.410 --> 00:39:03.420 align:start position:0% people actually want is they want to see 00:39:03.420 --> 00:39:06.590 align:start position:0% people actually want is they want to see when<00:39:03.600> a<00:39:03.630> theorem<00:39:03.960> moves<00:39:04.280> and<00:39:05.300> there<00:39:06.300> are<00:39:06.420> a<00:39:06.450> lot 00:39:06.590 --> 00:39:06.600 align:start position:0% when a theorem moves and there are a lot 00:39:06.600 --> 00:39:08.240 align:start position:0% when a theorem moves and there are a lot of<00:39:06.630> ways<00:39:06.960> that<00:39:07.350> smart<00:39:07.590> contracts<00:39:07.890> can<00:39:08.040> send 00:39:08.240 --> 00:39:08.250 align:start position:0% of ways that smart contracts can send 00:39:08.250 --> 00:39:10.970 align:start position:0% of ways that smart contracts can send that<00:39:08.400> today<00:39:08.820> which<00:39:09.480> don't<00:39:09.900> get<00:39:10.080> shown<00:39:10.320> up<00:39:10.530> with 00:39:10.970 --> 00:39:10.980 align:start position:0% that today which don't get shown up with 00:39:10.980 --> 00:39:15.080 align:start position:0% that today which don't get shown up with get<00:39:11.700> transaction<00:39:12.119> API<00:39:12.420> so<00:39:13.230> I<00:39:13.890> think<00:39:14.310> events 00:39:15.080 --> 00:39:15.090 align:start position:0% get transaction API so I think events 00:39:15.090 --> 00:39:16.970 align:start position:0% get transaction API so I think events are<00:39:15.180> one<00:39:15.270> of<00:39:15.390> those<00:39:15.480> ways<00:39:15.720> if<00:39:15.930> you<00:39:15.990> can<00:39:16.170> fire 00:39:16.970 --> 00:39:16.980 align:start position:0% are one of those ways if you can fire 00:39:16.980 --> 00:39:18.620 align:start position:0% are one of those ways if you can fire those<00:39:17.160> events<00:39:17.460> whatever<00:39:17.820> whenever<00:39:18.119> any<00:39:18.450> eff 00:39:18.620 --> 00:39:18.630 align:start position:0% those events whatever whenever any eff 00:39:18.630 --> 00:39:22.070 align:start position:0% those events whatever whenever any eff moves<00:39:18.950> that's<00:39:19.950> that's<00:39:20.310> a<00:39:20.400> big<00:39:20.580> way<00:39:20.730> that<00:39:21.080> that 00:39:22.070 --> 00:39:22.080 align:start position:0% moves that's that's a big way that that 00:39:22.080 --> 00:39:23.570 align:start position:0% moves that's that's a big way that that will<00:39:22.170> make<00:39:22.290> it<00:39:22.410> easier<00:39:22.680> for<00:39:22.710> integrators<00:39:23.280> to 00:39:23.570 --> 00:39:23.580 align:start position:0% will make it easier for integrators to 00:39:23.580 --> 00:39:25.970 align:start position:0% will make it easier for integrators to seize<00:39:24.359> these<00:39:24.900> transfers<00:39:25.440> and<00:39:25.650> credit 00:39:25.970 --> 00:39:25.980 align:start position:0% seize these transfers and credit 00:39:25.980 --> 00:39:28.700 align:start position:0% seize these transfers and credit deposits<00:39:26.810> another<00:39:27.810> way<00:39:27.990> you<00:39:28.050> know<00:39:28.290> could<00:39:28.560> be 00:39:28.700 --> 00:39:28.710 align:start position:0% deposits another way you know could be 00:39:28.710 --> 00:39:30.290 align:start position:0% deposits another way you know could be give<00:39:29.160> them<00:39:29.340> what<00:39:29.520> they<00:39:29.609> really<00:39:29.640> want<00:39:30.000> which<00:39:30.180> is 00:39:30.290 --> 00:39:30.300 align:start position:0% give them what they really want which is 00:39:30.300 --> 00:39:32.690 align:start position:0% give them what they really want which is again<00:39:30.810> transactions<00:39:31.320> API<00:39:32.130> which<00:39:32.400> actually 00:39:32.690 --> 00:39:32.700 align:start position:0% again transactions API which actually 00:39:32.700 --> 00:39:37.549 align:start position:0% again transactions API which actually gives<00:39:32.910> them<00:39:33.119> the<00:39:33.780> transactions<00:39:34.350> of<00:39:34.590> all<00:39:35.040> F 00:39:37.549 --> 00:39:37.559 align:start position:0% 00:39:37.559 --> 00:39:39.829 align:start position:0% and<00:39:38.549> you<00:39:38.670> know<00:39:38.789> that's<00:39:39.059> easier<00:39:39.539> said<00:39:39.569> than 00:39:39.829 --> 00:39:39.839 align:start position:0% and you know that's easier said than 00:39:39.839 --> 00:39:43.489 align:start position:0% and you know that's easier said than done<00:39:39.979> but<00:39:40.979> you<00:39:41.460> know<00:39:41.549> I<00:39:41.849> I<00:39:42.779> don't<00:39:43.019> even<00:39:43.229> know<00:39:43.410> if 00:39:43.489 --> 00:39:43.499 align:start position:0% done but you know I I don't even know if 00:39:43.499 --> 00:39:45.559 align:start position:0% done but you know I I don't even know if it's<00:39:43.619> that<00:39:43.799> hard<00:39:44.009> right<00:39:44.519> like<00:39:44.849> we<00:39:45.089> we've<00:39:45.420> all 00:39:45.559 --> 00:39:45.569 align:start position:0% it's that hard right like we we've all 00:39:45.569 --> 00:39:47.120 align:start position:0% it's that hard right like we we've all sort<00:39:45.779> of<00:39:45.900> experienced<00:39:46.410> this<00:39:46.469> parsing<00:39:46.920> of 00:39:47.120 --> 00:39:47.130 align:start position:0% sort of experienced this parsing of 00:39:47.130 --> 00:39:48.680 align:start position:0% sort of experienced this parsing of these<00:39:47.309> traces<00:39:47.640> like<00:39:47.789> it's<00:39:47.910> a<00:39:47.999> doable<00:39:48.329> thing<00:39:48.420> I 00:39:48.680 --> 00:39:48.690 align:start position:0% these traces like it's a doable thing I 00:39:48.690 --> 00:39:50.209 align:start position:0% these traces like it's a doable thing I mean<00:39:48.869> it'd<00:39:49.019> be<00:39:49.049> really<00:39:49.289> easy<00:39:49.410> to<00:39:49.710> like<00:39:49.979> write<00:39:50.190> a 00:39:50.209 --> 00:39:50.219 align:start position:0% mean it'd be really easy to like write a 00:39:50.219 --> 00:39:52.160 align:start position:0% mean it'd be really easy to like write a tool<00:39:50.489> that<00:39:50.759> does<00:39:50.819> this<00:39:51.150> like<00:39:51.329> it's<00:39:51.479> it's<00:39:51.839> yeah 00:39:52.160 --> 00:39:52.170 align:start position:0% tool that does this like it's it's yeah 00:39:52.170 --> 00:39:54.440 align:start position:0% tool that does this like it's it's yeah so<00:39:52.410> much<00:39:52.559> that<00:39:52.799> it's<00:39:52.920> like<00:39:53.180> difficult<00:39:54.180> it's 00:39:54.440 --> 00:39:54.450 align:start position:0% so much that it's like difficult it's 00:39:54.450 --> 00:39:56.509 align:start position:0% so much that it's like difficult it's just<00:39:54.539> that<00:39:54.930> it's<00:39:55.469> just<00:39:55.890> kind<00:39:56.099> of<00:39:56.130> there's<00:39:56.400> all 00:39:56.509 --> 00:39:56.519 align:start position:0% just that it's just kind of there's all 00:39:56.519 --> 00:39:58.039 align:start position:0% just that it's just kind of there's all these<00:39:56.609> nuances<00:39:56.819> that<00:39:57.390> don't<00:39:57.599> seem<00:39:57.749> right<00:39:57.869> be 00:39:58.039 --> 00:39:58.049 align:start position:0% these nuances that don't seem right be 00:39:58.049 --> 00:39:59.739 align:start position:0% these nuances that don't seem right be really<00:39:58.289> dire<00:39:58.499> augmented<00:39:58.979> and<00:39:59.099> so<00:39:59.549> like 00:39:59.739 --> 00:39:59.749 align:start position:0% really dire augmented and so like 00:39:59.749 --> 00:40:02.809 align:start position:0% really dire augmented and so like various<00:40:01.190> note<00:40:02.190> implications<00:40:02.700> could 00:40:02.809 --> 00:40:02.819 align:start position:0% various note implications could 00:40:02.819 --> 00:40:04.039 align:start position:0% various note implications could absolutely<00:40:03.029> implement<00:40:03.630> these<00:40:03.690> api<00:40:03.960> is 00:40:04.039 --> 00:40:04.049 align:start position:0% absolutely implement these api is 00:40:04.049 --> 00:40:05.479 align:start position:0% absolutely implement these api is especially<00:40:04.440> hands<00:40:04.710> I<00:40:04.799> have<00:40:04.920> sort<00:40:05.069> of<00:40:05.099> custom 00:40:05.479 --> 00:40:05.489 align:start position:0% especially hands I have sort of custom 00:40:05.489 --> 00:40:07.099 align:start position:0% especially hands I have sort of custom ones<00:40:05.640> but<00:40:05.849> I<00:40:05.999> think<00:40:06.239> would<00:40:06.359> be<00:40:06.420> ideal<00:40:06.749> is<00:40:06.960> like 00:40:07.099 --> 00:40:07.109 align:start position:0% ones but I think would be ideal is like 00:40:07.109 --> 00:40:09.380 align:start position:0% ones but I think would be ideal is like a<00:40:07.140> standard<00:40:07.499> sort<00:40:07.859> of<00:40:07.950> like<00:40:08.069> our<00:40:08.519> PC<00:40:08.819> API<00:40:09.059> that 00:40:09.380 --> 00:40:09.390 align:start position:0% a standard sort of like our PC API that 00:40:09.390 --> 00:40:10.849 align:start position:0% a standard sort of like our PC API that they<00:40:09.719> wouldn't<00:40:09.930> require<00:40:10.109> like<00:40:10.469> protocol 00:40:10.849 --> 00:40:10.859 align:start position:0% they wouldn't require like protocol 00:40:10.859 --> 00:40:12.019 align:start position:0% they wouldn't require like protocol levels<00:40:11.130> because<00:40:11.339> I<00:40:11.369> think<00:40:11.549> it's<00:40:11.759> gonna<00:40:11.849> be<00:40:11.999> a 00:40:12.019 --> 00:40:12.029 align:start position:0% levels because I think it's gonna be a 00:40:12.029 --> 00:40:14.150 align:start position:0% levels because I think it's gonna be a lot<00:40:12.150> harder<00:40:12.299> to<00:40:12.509> sort<00:40:12.719> of<00:40:12.809> sell<00:40:13.049> but<00:40:13.799> you<00:40:14.009> could 00:40:14.150 --> 00:40:14.160 align:start position:0% lot harder to sort of sell but you could 00:40:14.160 --> 00:40:20.359 align:start position:0% lot harder to sort of sell but you could absolutely<00:40:14.279> just<00:40:15.029> have<00:40:18.319> it<00:40:19.319> would<00:40:19.440> be<00:40:19.499> a<00:40:19.950> new 00:40:20.359 --> 00:40:20.369 align:start position:0% absolutely just have it would be a new 00:40:20.369 --> 00:40:23.930 align:start position:0% absolutely just have it would be a new kind<00:40:20.819> of<00:40:20.969> RPC<00:40:21.630> API<00:40:22.519> extension<00:40:23.519> to<00:40:23.579> web<00:40:23.700> three 00:40:23.930 --> 00:40:23.940 align:start position:0% kind of RPC API extension to web three 00:40:23.940 --> 00:40:25.969 align:start position:0% kind of RPC API extension to web three or<00:40:24.089> something<00:40:24.299> like<00:40:24.479> that<00:40:24.539> and<00:40:24.960> I<00:40:25.710> think 00:40:25.969 --> 00:40:25.979 align:start position:0% or something like that and I think 00:40:25.979 --> 00:40:31.130 align:start position:0% or something like that and I think people<00:40:26.099> you<00:40:26.609> know<00:40:28.190> someone<00:40:29.190> that<00:40:29.219> that<00:40:30.019> for<00:40:31.019> us 00:40:31.130 --> 00:40:31.140 align:start position:0% people you know someone that that for us 00:40:31.140 --> 00:40:33.019 align:start position:0% people you know someone that that for us because<00:40:31.680> we<00:40:31.920> care<00:40:32.160> so<00:40:32.190> much<00:40:32.369> about<00:40:32.460> platforms 00:40:33.019 --> 00:40:33.029 align:start position:0% because we care so much about platforms 00:40:33.029 --> 00:40:36.739 align:start position:0% because we care so much about platforms and<00:40:33.150> having<00:40:33.329> developers<00:40:33.779> use<00:40:34.109> platforms<00:40:35.749> you 00:40:36.739 --> 00:40:36.749 align:start position:0% and having developers use platforms you 00:40:36.749 --> 00:40:38.089 align:start position:0% and having developers use platforms you know<00:40:36.839> if<00:40:36.989> they<00:40:37.079> have<00:40:37.200> to<00:40:37.259> go<00:40:37.410> for<00:40:37.650> a<00:40:37.680> talk<00:40:37.920> like 00:40:38.089 --> 00:40:38.099 align:start position:0% know if they have to go for a talk like 00:40:38.099 --> 00:40:40.400 align:start position:0% know if they have to go for a talk like yours<00:40:38.719> great<00:40:39.719> talk 00:40:40.400 --> 00:40:40.410 align:start position:0% yours great talk 00:40:40.410 --> 00:40:42.109 align:start position:0% yours great talk but<00:40:40.859> if<00:40:41.130> they<00:40:41.309> have<00:40:41.400> to<00:40:41.460> go<00:40:41.579> for<00:40:41.729> a<00:40:41.789> talk<00:40:41.969> in 00:40:42.109 --> 00:40:42.119 align:start position:0% but if they have to go for a talk in 00:40:42.119 --> 00:40:43.549 align:start position:0% but if they have to go for a talk in order<00:40:42.269> to<00:40:42.390> learn<00:40:42.509> how<00:40:42.660> to<00:40:42.690> do<00:40:42.900> it<00:40:43.019> that's 00:40:43.549 --> 00:40:43.559 align:start position:0% order to learn how to do it that's 00:40:43.559 --> 00:40:45.289 align:start position:0% order to learn how to do it that's probably<00:40:43.859> too<00:40:44.160> hot<00:40:44.400> you<00:40:44.789> you<00:40:44.940> want<00:40:45.119> to<00:40:45.150> just 00:40:45.289 --> 00:40:45.299 align:start position:0% probably too hot you you want to just 00:40:45.299 --> 00:40:46.039 align:start position:0% probably too hot you you want to just give<00:40:45.630> it<00:40:45.660> to<00:40:45.779> them 00:40:46.039 --> 00:40:46.049 align:start position:0% give it to them 00:40:46.049 --> 00:40:48.140 align:start position:0% give it to them right<00:40:46.170> away<00:40:46.349> just<00:40:46.650> give<00:40:46.769> them<00:40:46.920> the<00:40:47.099> API<00:40:47.849> and<00:40:48.059> it 00:40:48.140 --> 00:40:48.150 align:start position:0% right away just give them the API and it 00:40:48.150 --> 00:40:49.940 align:start position:0% right away just give them the API and it should<00:40:48.299> do<00:40:48.390> anyone<00:40:48.719> more<00:40:49.229> on<00:40:49.410> the<00:40:49.499> topic<00:40:49.829> of 00:40:49.940 --> 00:40:49.950 align:start position:0% should do anyone more on the topic of 00:40:49.950 --> 00:40:52.519 align:start position:0% should do anyone more on the topic of things<00:40:50.489> that<00:40:50.849> I'd<00:40:51.779> love<00:40:52.049> to<00:40:52.079> see<00:40:52.319> nodes 00:40:52.519 --> 00:40:52.529 align:start position:0% things that I'd love to see nodes 00:40:52.529 --> 00:40:55.339 align:start position:0% things that I'd love to see nodes implement<00:40:53.069> is<00:40:53.269> the<00:40:54.269> I<00:40:54.690> believe<00:40:54.900> it<00:40:55.170> already 00:40:55.339 --> 00:40:55.349 align:start position:0% implement is the I believe it already 00:40:55.349 --> 00:40:57.950 align:start position:0% implement is the I believe it already exists<00:40:55.799> in<00:40:55.859> the<00:40:55.890> EVM<00:40:56.279> as<00:40:56.489> far<00:40:56.670> as<00:40:56.759> I<00:40:56.849> know<00:40:56.960> I 00:40:57.950 --> 00:40:57.960 align:start position:0% exists in the EVM as far as I know I 00:40:57.960 --> 00:41:01.059 align:start position:0% exists in the EVM as far as I know I think<00:40:58.650> it<00:40:58.859> came<00:40:59.009> with<00:40:59.190> metropolis<00:40:59.729> is<00:40:59.969> the 00:41:01.059 --> 00:41:01.069 align:start position:0% think it came with metropolis is the 00:41:01.069 --> 00:41:03.380 align:start position:0% think it came with metropolis is the returning<00:41:02.069> data<00:41:02.309> with<00:41:02.579> a<00:41:02.609> revert<00:41:02.969> opcode 00:41:03.380 --> 00:41:03.390 align:start position:0% returning data with a revert opcode 00:41:03.390 --> 00:41:06.229 align:start position:0% returning data with a revert opcode being<00:41:04.049> able<00:41:04.140> to<00:41:04.259> have<00:41:04.469> actual<00:41:05.069> error<00:41:05.700> codes<00:41:06.089> I 00:41:06.229 --> 00:41:06.239 align:start position:0% being able to have actual error codes I 00:41:06.239 --> 00:41:07.880 align:start position:0% being able to have actual error codes I can<00:41:06.390> send<00:41:06.599> back<00:41:06.749> in<00:41:06.989> my<00:41:07.109> errors<00:41:07.380> and<00:41:07.589> not<00:41:07.680> have 00:41:07.880 --> 00:41:07.890 align:start position:0% can send back in my errors and not have 00:41:07.890 --> 00:41:10.219 align:start position:0% can send back in my errors and not have to<00:41:08.099> do<00:41:08.940> extremely<00:41:09.450> tedious<00:41:09.660> solidity 00:41:10.219 --> 00:41:10.229 align:start position:0% to do extremely tedious solidity 00:41:10.229 --> 00:41:16.989 align:start position:0% to do extremely tedious solidity debugging<00:41:10.829> for<00:41:11.009> hours<00:41:11.430> to<00:41:11.700> find<00:41:12.089> out<00:41:12.269> my<00:41:12.779> typos 00:41:16.989 --> 00:41:16.999 align:start position:0% 00:41:16.999 --> 00:41:21.140 align:start position:0% I<00:41:19.009> didn't<00:41:20.009> see<00:41:20.099> at<00:41:20.190> this<00:41:20.279> time<00:41:20.489> I'm<00:41:20.700> sure<00:41:20.999> there 00:41:21.140 --> 00:41:21.150 align:start position:0% I didn't see at this time I'm sure there 00:41:21.150 --> 00:41:25.609 align:start position:0% I didn't see at this time I'm sure there was<00:41:22.460> standardized<00:41:23.460> the<00:41:23.809> return<00:41:24.809> codes<00:41:25.079> yeah 00:41:25.609 --> 00:41:25.619 align:start position:0% was standardized the return codes yeah 00:41:25.619 --> 00:41:28.549 align:start position:0% was standardized the return codes yeah okay<00:41:26.489> yeah<00:41:26.759> I<00:41:26.940> know<00:41:27.420> they<00:41:27.630> implemented<00:41:28.440> in 00:41:28.549 --> 00:41:28.559 align:start position:0% okay yeah I know they implemented in 00:41:28.559 --> 00:41:30.499 align:start position:0% okay yeah I know they implemented in Metropolis<00:41:29.339> the<00:41:29.369> OP<00:41:29.759> code<00:41:29.789> to<00:41:30.210> actually 00:41:30.499 --> 00:41:30.509 align:start position:0% Metropolis the OP code to actually 00:41:30.509 --> 00:41:32.539 align:start position:0% Metropolis the OP code to actually return<00:41:31.049> just<00:41:31.410> arbitrary<00:41:31.890> data<00:41:32.039> that<00:41:32.339> I<00:41:32.369> can 00:41:32.539 --> 00:41:32.549 align:start position:0% return just arbitrary data that I can 00:41:32.549 --> 00:41:36.019 align:start position:0% return just arbitrary data that I can pass<00:41:32.729> a<00:41:32.759> string<00:41:33.150> to<00:41:33.329> revert<00:41:34.279> but<00:41:35.279> I<00:41:35.579> haven't 00:41:36.019 --> 00:41:36.029 align:start position:0% pass a string to revert but I haven't 00:41:36.029 --> 00:41:37.099 align:start position:0% pass a string to revert but I haven't heard<00:41:36.210> anything<00:41:36.299> for<00:41:36.660> a<00:41:36.690> standardization 00:41:37.099 --> 00:41:37.109 align:start position:0% heard anything for a standardization 00:41:37.109 --> 00:41:38.719 align:start position:0% heard anything for a standardization yeah<00:41:37.799> I<00:41:37.829> think<00:41:37.979> there's<00:41:38.160> someone<00:41:38.309> working<00:41:38.640> on 00:41:38.719 --> 00:41:38.729 align:start position:0% yeah I think there's someone working on 00:41:38.729 --> 00:41:40.249 align:start position:0% yeah I think there's someone working on it<00:41:38.849> I<00:41:38.969> think<00:41:39.029> it's<00:41:39.299> really<00:41:39.599> important<00:41:39.989> it's 00:41:40.249 --> 00:41:40.259 align:start position:0% it I think it's really important it's 00:41:40.259 --> 00:41:41.930 align:start position:0% it I think it's really important it's like<00:41:40.410> kind<00:41:40.589> of<00:41:40.619> like<00:41:40.739> you<00:41:40.890> have<00:41:40.920> HTTP<00:41:41.460> status 00:41:41.930 --> 00:41:41.940 align:start position:0% like kind of like you have HTTP status 00:41:41.940 --> 00:41:43.190 align:start position:0% like kind of like you have HTTP status codes<00:41:42.390> you<00:41:42.509> should<00:41:42.660> have<00:41:42.749> returned<00:41:43.079> off 00:41:43.190 --> 00:41:43.200 align:start position:0% codes you should have returned off 00:41:43.200 --> 00:41:44.700 align:start position:0% codes you should have returned off course<00:41:43.469> yeah 00:41:44.700 --> 00:41:44.710 align:start position:0% course yeah 00:41:44.710 --> 00:41:46.170 align:start position:0% course yeah yeah<00:41:45.309> one<00:41:45.490> other<00:41:45.579> thing<00:41:45.730> I<00:41:45.819> think<00:41:45.970> is 00:41:46.170 --> 00:41:46.180 align:start position:0% yeah one other thing I think is 00:41:46.180 --> 00:41:47.910 align:start position:0% yeah one other thing I think is interesting<00:41:46.210> that<00:41:46.809> would<00:41:46.930> be<00:41:47.050> be<00:41:47.500> cool<00:41:47.740> to<00:41:47.890> see 00:41:47.910 --> 00:41:47.920 align:start position:0% interesting that would be be cool to see 00:41:47.920 --> 00:41:51.870 align:start position:0% interesting that would be be cool to see it<00:41:48.579> doesn't<00:41:49.390> exist<00:41:49.869> but<00:41:50.140> it's<00:41:50.349> is<00:41:50.589> like<00:41:51.099> some 00:41:51.870 --> 00:41:51.880 align:start position:0% it doesn't exist but it's is like some 00:41:51.880 --> 00:41:53.579 align:start position:0% it doesn't exist but it's is like some more<00:41:52.059> sort<00:41:52.270> of<00:41:52.390> infrastructure<00:41:52.869> or<00:41:53.020> sort<00:41:53.530> of 00:41:53.579 --> 00:41:53.589 align:start position:0% more sort of infrastructure or sort of 00:41:53.589 --> 00:41:55.170 align:start position:0% more sort of infrastructure or sort of tooling<00:41:53.920> around<00:41:54.010> like<00:41:54.490> running<00:41:54.819> notes<00:41:55.000> and 00:41:55.170 --> 00:41:55.180 align:start position:0% tooling around like running notes and 00:41:55.180 --> 00:41:56.700 align:start position:0% tooling around like running notes and running<00:41:55.420> notes<00:41:55.599> and<00:41:55.750> sort<00:41:55.900> of<00:41:55.930> like<00:41:56.109> a<00:41:56.140> high 00:41:56.700 --> 00:41:56.710 align:start position:0% running notes and sort of like a high 00:41:56.710 --> 00:41:59.280 align:start position:0% running notes and sort of like a high availability<00:41:56.920> set<00:41:57.670> up<00:41:57.790> right<00:41:58.480> and<00:41:58.720> a<00:41:58.750> lot<00:41:59.260> of 00:41:59.280 --> 00:41:59.290 align:start position:0% availability set up right and a lot of 00:41:59.290 --> 00:42:01.620 align:start position:0% availability set up right and a lot of the<00:42:00.010> nodes<00:42:00.190> of<00:42:00.339> today's<00:42:00.940> sort<00:42:01.150> of<00:42:01.210> expect<00:42:01.569> you 00:42:01.620 --> 00:42:01.630 align:start position:0% the nodes of today's sort of expect you 00:42:01.630 --> 00:42:03.720 align:start position:0% the nodes of today's sort of expect you to<00:42:01.750> run<00:42:01.990> them<00:42:02.200> and<00:42:02.440> this<00:42:02.980> single 00:42:03.720 --> 00:42:03.730 align:start position:0% to run them and this single 00:42:03.730 --> 00:42:05.940 align:start position:0% to run them and this single configuration<00:42:04.000> of<00:42:04.960> just<00:42:05.200> you<00:42:05.380> have<00:42:05.530> one<00:42:05.770> thing 00:42:05.940 --> 00:42:05.950 align:start position:0% configuration of just you have one thing 00:42:05.950 --> 00:42:07.440 align:start position:0% configuration of just you have one thing running<00:42:06.250> on<00:42:06.369> one<00:42:06.490> box<00:42:06.730> and<00:42:06.910> you<00:42:07.000> expect<00:42:07.300> it<00:42:07.420> to 00:42:07.440 --> 00:42:07.450 align:start position:0% running on one box and you expect it to 00:42:07.450 --> 00:42:09.930 align:start position:0% running on one box and you expect it to never<00:42:07.690> go<00:42:07.930> down<00:42:08.109> and<00:42:08.380> never<00:42:08.500> break<00:42:08.740> and<00:42:09.700> that's 00:42:09.930 --> 00:42:09.940 align:start position:0% never go down and never break and that's 00:42:09.940 --> 00:42:12.420 align:start position:0% never go down and never break and that's just<00:42:10.089> not<00:42:10.240> reality<00:42:10.720> right<00:42:11.200> these<00:42:11.410> every<00:42:11.980> piece 00:42:12.420 --> 00:42:12.430 align:start position:0% just not reality right these every piece 00:42:12.430 --> 00:42:13.890 align:start position:0% just not reality right these every piece of<00:42:12.579> software<00:42:12.849> will<00:42:13.089> break<00:42:13.270> at<00:42:13.420> some<00:42:13.540> point<00:42:13.780> it 00:42:13.890 --> 00:42:13.900 align:start position:0% of software will break at some point it 00:42:13.900 --> 00:42:16.319 align:start position:0% of software will break at some point it will<00:42:13.960> go<00:42:14.050> down<00:42:14.260> and<00:42:14.500> so<00:42:14.650> if<00:42:14.950> you're<00:42:15.460> having<00:42:16.240> a 00:42:16.319 --> 00:42:16.329 align:start position:0% will go down and so if you're having a 00:42:16.329 --> 00:42:17.609 align:start position:0% will go down and so if you're having a lot<00:42:16.480> of<00:42:16.660> sort<00:42:16.780> of<00:42:16.809> transaction<00:42:17.260> stuff<00:42:17.440> going 00:42:17.609 --> 00:42:17.619 align:start position:0% lot of sort of transaction stuff going 00:42:17.619 --> 00:42:19.200 align:start position:0% lot of sort of transaction stuff going through<00:42:17.770> also<00:42:17.920> you<00:42:18.069> can't<00:42:18.369> just<00:42:18.609> use<00:42:18.760> one<00:42:19.000> like 00:42:19.200 --> 00:42:19.210 align:start position:0% through also you can't just use one like 00:42:19.210 --> 00:42:21.089 align:start position:0% through also you can't just use one like it<00:42:19.329> just<00:42:19.540> wouldn't<00:42:19.809> work<00:42:19.990> at<00:42:20.740> this<00:42:20.859> sort<00:42:21.040> of 00:42:21.089 --> 00:42:21.099 align:start position:0% it just wouldn't work at this sort of 00:42:21.099 --> 00:42:23.309 align:start position:0% it just wouldn't work at this sort of scale<00:42:21.339> you<00:42:21.369> may<00:42:21.670> see<00:42:21.730> and<00:42:22.210> so<00:42:22.630> you<00:42:22.990> need<00:42:23.140> more 00:42:23.309 --> 00:42:23.319 align:start position:0% scale you may see and so you need more 00:42:23.319 --> 00:42:24.690 align:start position:0% scale you may see and so you need more than<00:42:23.470> one<00:42:23.530> and<00:42:24.010> then<00:42:24.160> you<00:42:24.250> get<00:42:24.400> into<00:42:24.609> all<00:42:24.670> sorts 00:42:24.690 --> 00:42:24.700 align:start position:0% than one and then you get into all sorts 00:42:24.700 --> 00:42:26.460 align:start position:0% than one and then you get into all sorts of<00:42:24.970> issues<00:42:25.089> where<00:42:25.480> you<00:42:25.510> make<00:42:25.960> a<00:42:25.990> request<00:42:26.260> to 00:42:26.460 --> 00:42:26.470 align:start position:0% of issues where you make a request to 00:42:26.470 --> 00:42:27.990 align:start position:0% of issues where you make a request to one<00:42:26.619> node<00:42:26.829> through<00:42:27.160> a<00:42:27.190> load<00:42:27.520> balancer<00:42:27.970> and 00:42:27.990 --> 00:42:28.000 align:start position:0% one node through a load balancer and 00:42:28.000 --> 00:42:29.460 align:start position:0% one node through a load balancer and then<00:42:28.420> you<00:42:28.540> make<00:42:28.660> another<00:42:28.690> one<00:42:28.990> and<00:42:29.260> you<00:42:29.319> get<00:42:29.440> a 00:42:29.460 --> 00:42:29.470 align:start position:0% then you make another one and you get a 00:42:29.470 --> 00:42:30.870 align:start position:0% then you make another one and you get a different<00:42:29.800> result<00:42:29.920> back<00:42:30.250> because<00:42:30.640> it<00:42:30.760> hit<00:42:30.849> a 00:42:30.870 --> 00:42:30.880 align:start position:0% different result back because it hit a 00:42:30.880 --> 00:42:31.950 align:start position:0% different result back because it hit a different<00:42:31.030> node<00:42:31.270> that's<00:42:31.480> a<00:42:31.569> different<00:42:31.809> part 00:42:31.950 --> 00:42:31.960 align:start position:0% different node that's a different part 00:42:31.960 --> 00:42:33.690 align:start position:0% different node that's a different part of<00:42:31.990> the<00:42:32.079> blockchain<00:42:32.260> so<00:42:33.040> you<00:42:33.099> have<00:42:33.369> to<00:42:33.490> sort<00:42:33.640> of 00:42:33.690 --> 00:42:33.700 align:start position:0% of the blockchain so you have to sort of 00:42:33.700 --> 00:42:35.400 align:start position:0% of the blockchain so you have to sort of deal<00:42:34.210> with<00:42:34.240> this<00:42:34.450> in<00:42:34.569> in<00:42:34.839> like<00:42:34.990> interesting 00:42:35.400 --> 00:42:35.410 align:start position:0% deal with this in in like interesting 00:42:35.410 --> 00:42:37.049 align:start position:0% deal with this in in like interesting ways<00:42:35.559> whether<00:42:35.950> or<00:42:36.040> not<00:42:36.099> you<00:42:36.220> sort<00:42:36.430> of<00:42:36.460> take 00:42:37.049 --> 00:42:37.059 align:start position:0% ways whether or not you sort of take 00:42:37.059 --> 00:42:38.640 align:start position:0% ways whether or not you sort of take data<00:42:37.300> from<00:42:37.510> multiple<00:42:37.599> nodes<00:42:37.990> put<00:42:38.200> it<00:42:38.290> on<00:42:38.380> your 00:42:38.640 --> 00:42:38.650 align:start position:0% data from multiple nodes put it on your 00:42:38.650 --> 00:42:40.020 align:start position:0% data from multiple nodes put it on your own<00:42:38.740> database<00:42:39.069> and<00:42:39.400> sort<00:42:39.550> of<00:42:39.579> handle<00:42:39.940> that 00:42:40.020 --> 00:42:40.030 align:start position:0% own database and sort of handle that 00:42:40.030 --> 00:42:42.870 align:start position:0% own database and sort of handle that inconsistency<00:42:40.690> there<00:42:40.900> or<00:42:41.170> just<00:42:41.980> run<00:42:42.490> one<00:42:42.670> node 00:42:42.870 --> 00:42:42.880 align:start position:0% inconsistency there or just run one node 00:42:42.880 --> 00:42:44.790 align:start position:0% inconsistency there or just run one node I<00:42:42.910> suppose<00:42:43.240> as<00:42:43.390> an<00:42:43.510> option<00:42:43.869> there's<00:42:44.589> a<00:42:44.650> lot<00:42:44.770> of 00:42:44.790 --> 00:42:44.800 align:start position:0% I suppose as an option there's a lot of 00:42:44.800 --> 00:42:46.170 align:start position:0% I suppose as an option there's a lot of choices<00:42:45.069> here<00:42:45.220> but<00:42:45.550> there's<00:42:45.880> not<00:42:45.970> much 00:42:46.170 --> 00:42:46.180 align:start position:0% choices here but there's not much 00:42:46.180 --> 00:42:47.700 align:start position:0% choices here but there's not much information<00:42:46.809> on<00:42:46.930> that<00:42:47.109> and<00:42:47.319> I<00:42:47.380> think<00:42:47.470> other 00:42:47.700 --> 00:42:47.710 align:start position:0% information on that and I think other 00:42:47.710 --> 00:42:48.990 align:start position:0% information on that and I think other block<00:42:48.160> chains<00:42:48.430> have<00:42:48.579> all<00:42:48.700> their<00:42:48.819> like 00:42:48.990 --> 00:42:49.000 align:start position:0% block chains have all their like 00:42:49.000 --> 00:42:51.089 align:start position:0% block chains have all their like proposed<00:42:49.390> ways<00:42:49.660> of<00:42:49.990> running<00:42:50.470> them<00:42:50.799> and<00:42:50.829> more 00:42:51.089 --> 00:42:51.099 align:start position:0% proposed ways of running them and more 00:42:51.099 --> 00:42:53.069 align:start position:0% proposed ways of running them and more of<00:42:51.220> this<00:42:51.369> like<00:42:51.579> high<00:42:52.030> availability<00:42:52.270> set<00:42:52.990> up 00:42:53.069 --> 00:42:53.079 align:start position:0% of this like high availability set up 00:42:53.079 --> 00:42:55.349 align:start position:0% of this like high availability set up for<00:42:53.319> like<00:42:53.440> if<00:42:53.530> you<00:42:53.650> want<00:42:53.799> to<00:42:53.859> build<00:42:54.010> like<00:42:54.359> you 00:42:55.349 --> 00:42:55.359 align:start position:0% for like if you want to build like you 00:42:55.359 --> 00:42:57.240 align:start position:0% for like if you want to build like you know<00:42:55.470> reliable<00:42:56.470> sort<00:42:56.680> of<00:42:56.740> infrastructure 00:42:57.240 --> 00:42:57.250 align:start position:0% know reliable sort of infrastructure 00:42:57.250 --> 00:42:58.589 align:start position:0% know reliable sort of infrastructure around<00:42:57.339> these<00:42:57.700> to<00:42:57.880> make<00:42:58.000> sure<00:42:58.180> that<00:42:58.359> you<00:42:58.510> know 00:42:58.589 --> 00:42:58.599 align:start position:0% around these to make sure that you know 00:42:58.599 --> 00:43:00.390 align:start position:0% around these to make sure that you know nodes<00:42:58.839> aren't<00:42:59.109> your<00:42:59.230> problem<00:42:59.680> and<00:42:59.920> you<00:43:00.250> can 00:43:00.390 --> 00:43:00.400 align:start position:0% nodes aren't your problem and you can 00:43:00.400 --> 00:43:02.160 align:start position:0% nodes aren't your problem and you can just<00:43:00.549> kind<00:43:00.700> of<00:43:00.760> focus<00:43:01.089> on<00:43:01.270> on<00:43:01.510> the<00:43:01.540> chain<00:43:01.869> I 00:43:02.160 --> 00:43:02.170 align:start position:0% just kind of focus on on the chain I 00:43:02.170 --> 00:43:03.599 align:start position:0% just kind of focus on on the chain I think<00:43:02.380> we<00:43:02.470> need<00:43:02.589> some<00:43:02.770> better<00:43:03.010> tooling<00:43:03.339> there 00:43:03.599 --> 00:43:03.609 align:start position:0% think we need some better tooling there 00:43:03.609 --> 00:43:05.640 align:start position:0% think we need some better tooling there yeah<00:43:04.119> I<00:43:04.630> think<00:43:04.809> that<00:43:05.049> sounds<00:43:05.079> like<00:43:05.380> a<00:43:05.440> great 00:43:05.640 --> 00:43:05.650 align:start position:0% yeah I think that sounds like a great 00:43:05.650 --> 00:43:07.799 align:start position:0% yeah I think that sounds like a great grant<00:43:06.040> project<00:43:06.490> actually<00:43:06.880> I<00:43:07.059> mean<00:43:07.569> think 00:43:07.799 --> 00:43:07.809 align:start position:0% grant project actually I mean think 00:43:07.809 --> 00:43:09.569 align:start position:0% grant project actually I mean think about<00:43:07.869> it<00:43:08.170> right<00:43:08.319> like<00:43:08.530> cuz<00:43:08.710> we<00:43:08.829> have<00:43:08.980> like<00:43:09.490> I 00:43:09.569 --> 00:43:09.579 align:start position:0% about it right like cuz we have like I 00:43:09.579 --> 00:43:10.859 align:start position:0% about it right like cuz we have like I think<00:43:09.670> a<00:43:09.790> theorem<00:43:10.030> is<00:43:10.119> really<00:43:10.510> cool<00:43:10.690> we<00:43:10.780> have 00:43:10.859 --> 00:43:10.869 align:start position:0% think a theorem is really cool we have 00:43:10.869 --> 00:43:12.870 align:start position:0% think a theorem is really cool we have like<00:43:11.020> the<00:43:11.109> most<00:43:11.290> clients<00:43:11.680> I<00:43:11.920> think<00:43:11.950> of<00:43:12.190> any 00:43:12.870 --> 00:43:12.880 align:start position:0% like the most clients I think of any 00:43:12.880 --> 00:43:14.160 align:start position:0% like the most clients I think of any blockchain<00:43:13.299> probably<00:43:13.660> most<00:43:13.900> different 00:43:14.160 --> 00:43:14.170 align:start position:0% blockchain probably most different 00:43:14.170 --> 00:43:16.319 align:start position:0% blockchain probably most different implementations<00:43:14.859> you<00:43:15.700> could<00:43:15.849> almost<00:43:15.970> be<00:43:16.299> like 00:43:16.319 --> 00:43:16.329 align:start position:0% implementations you could almost be like 00:43:16.329 --> 00:43:18.420 align:start position:0% implementations you could almost be like connect<00:43:17.109> to<00:43:17.230> the<00:43:17.319> web<00:43:17.440> three<00:43:17.710> or<00:43:17.890> gasps<00:43:18.190> and 00:43:18.420 --> 00:43:18.430 align:start position:0% connect to the web three or gasps and 00:43:18.430 --> 00:43:20.160 align:start position:0% connect to the web three or gasps and parity<00:43:18.910> and<00:43:19.119> be<00:43:19.660> like<00:43:19.780> a<00:43:19.809> load<00:43:20.020> balancer 00:43:20.160 --> 00:43:20.170 align:start position:0% parity and be like a load balancer 00:43:20.170 --> 00:43:22.920 align:start position:0% parity and be like a load balancer crossbows<00:43:20.920> and<00:43:20.950> and<00:43:21.579> only<00:43:22.210> accept<00:43:22.750> things 00:43:22.920 --> 00:43:22.930 align:start position:0% crossbows and and only accept things 00:43:22.930 --> 00:43:26.400 align:start position:0% crossbows and and only accept things that<00:43:23.819> go<00:43:24.819> with<00:43:24.849> them<00:43:25.089> agree<00:43:25.359> on<00:43:25.510> or<00:43:25.780> come<00:43:26.319> out 00:43:26.400 --> 00:43:26.410 align:start position:0% that go with them agree on or come out 00:43:26.410 --> 00:43:28.950 align:start position:0% that go with them agree on or come out yeah<00:43:26.799> we<00:43:27.190> have<00:43:27.490> an<00:43:27.609> injury<00:43:27.849> yeah<00:43:28.270> yeah<00:43:28.630> we<00:43:28.809> have 00:43:28.950 --> 00:43:28.960 align:start position:0% yeah we have an injury yeah yeah we have 00:43:28.960 --> 00:43:30.420 align:start position:0% yeah we have an injury yeah yeah we have like<00:43:29.109> an<00:43:29.230> interesting<00:43:29.500> set<00:43:29.680> of<00:43:29.710> that<00:43:29.859> kind<00:43:30.369> of 00:43:30.420 --> 00:43:30.430 align:start position:0% like an interesting set of that kind of 00:43:30.430 --> 00:43:32.250 align:start position:0% like an interesting set of that kind of does<00:43:30.549> that<00:43:30.579> but<00:43:30.880> not<00:43:31.000> about<00:43:31.660> the<00:43:31.839> agreement 00:43:32.250 --> 00:43:32.260 align:start position:0% does that but not about the agreement 00:43:32.260 --> 00:43:33.359 align:start position:0% does that but not about the agreement thing<00:43:32.380> where<00:43:32.500> we<00:43:32.589> actually<00:43:32.680> sort<00:43:33.040> of<00:43:33.069> chained 00:43:33.359 --> 00:43:33.369 align:start position:0% thing where we actually sort of chained 00:43:33.369 --> 00:43:34.890 align:start position:0% thing where we actually sort of chained them<00:43:33.609> together<00:43:33.819> we<00:43:34.390> chained<00:43:34.690> together 00:43:34.890 --> 00:43:34.900 align:start position:0% them together we chained together 00:43:34.900 --> 00:43:36.299 align:start position:0% them together we chained together different<00:43:35.290> node<00:43:35.410> implementations<00:43:35.980> so<00:43:36.130> that 00:43:36.299 --> 00:43:36.309 align:start position:0% different node implementations so that 00:43:36.309 --> 00:43:37.740 align:start position:0% different node implementations so that if<00:43:36.369> there<00:43:36.490> is<00:43:36.579> some<00:43:36.700> sort<00:43:36.910> of<00:43:36.970> consensus 00:43:37.740 --> 00:43:37.750 align:start position:0% if there is some sort of consensus 00:43:37.750 --> 00:43:40.559 align:start position:0% if there is some sort of consensus breaking<00:43:38.260> rules<00:43:38.730> it'll<00:43:39.730> sort<00:43:39.849> of<00:43:39.970> stop<00:43:40.210> there 00:43:40.559 --> 00:43:40.569 align:start position:0% breaking rules it'll sort of stop there 00:43:40.569 --> 00:43:42.930 align:start position:0% breaking rules it'll sort of stop there and<00:43:41.530> not<00:43:41.680> sort<00:43:41.890> of<00:43:41.980> get<00:43:42.130> to<00:43:42.309> our<00:43:42.460> the<00:43:42.670> rest<00:43:42.819> of 00:43:42.930 --> 00:43:42.940 align:start position:0% and not sort of get to our the rest of 00:43:42.940 --> 00:43:44.789 align:start position:0% and not sort of get to our the rest of our<00:43:43.030> systems<00:43:43.420> because<00:43:44.140> like<00:43:44.349> these<00:43:44.589> things 00:43:44.789 --> 00:43:44.799 align:start position:0% our systems because like these things 00:43:44.799 --> 00:43:46.260 align:start position:0% our systems because like these things happen<00:43:45.130> and<00:43:45.339> this<00:43:45.640> is<00:43:45.760> a<00:43:45.790> way<00:43:45.910> to<00:43:45.940> sort<00:43:46.180> of 00:43:46.260 --> 00:43:46.270 align:start position:0% happen and this is a way to sort of 00:43:46.270 --> 00:43:48.150 align:start position:0% happen and this is a way to sort of mitigate<00:43:46.420> them<00:43:46.750> and<00:43:46.960> so<00:43:47.170> yeah<00:43:47.380> trying<00:43:47.920> to<00:43:47.980> sort 00:43:48.150 --> 00:43:48.160 align:start position:0% mitigate them and so yeah trying to sort 00:43:48.160 --> 00:43:51.150 align:start position:0% mitigate them and so yeah trying to sort of<00:43:48.190> detect<00:43:48.579> consensus<00:43:49.270> and<00:43:49.510> detects<00:43:49.780> like<00:43:50.160> 51% 00:43:51.150 --> 00:43:51.160 align:start position:0% of detect consensus and detects like 51% 00:43:51.160 --> 00:43:52.289 align:start position:0% of detect consensus and detects like 51% attacks<00:43:51.400> and<00:43:51.579> things<00:43:51.730> like<00:43:51.819> that<00:43:51.880> there's 00:43:52.289 --> 00:43:52.299 align:start position:0% attacks and things like that there's 00:43:52.299 --> 00:43:54.030 align:start position:0% attacks and things like that there's probably<00:43:52.510> a<00:43:52.569> lot<00:43:52.690> of<00:43:52.750> interesting<00:43:53.079> tools<00:43:53.319> that 00:43:54.030 --> 00:43:54.040 align:start position:0% probably a lot of interesting tools that 00:43:54.040 --> 00:43:55.140 align:start position:0% probably a lot of interesting tools that can<00:43:54.220> be<00:43:54.309> produced<00:43:54.579> out<00:43:54.670> of<00:43:54.700> there<00:43:54.880> that<00:43:55.119> I 00:43:55.140 --> 00:43:55.150 align:start position:0% can be produced out of there that I 00:43:55.150 --> 00:43:57.089 align:start position:0% can be produced out of there that I think<00:43:55.420> a<00:43:55.510> lot<00:43:55.660> of<00:43:55.690> exchanges<00:43:56.230> in<00:43:56.500> companies 00:43:57.089 --> 00:43:57.099 align:start position:0% think a lot of exchanges in companies 00:43:57.099 --> 00:43:58.070 align:start position:0% think a lot of exchanges in companies building<00:43:57.460> are 00:43:58.070 --> 00:43:58.080 align:start position:0% building are 00:43:58.080 --> 00:43:59.540 align:start position:0% building are aren't<00:43:58.290> doing<00:43:58.590> on<00:43:58.710> their<00:43:58.890> own<00:43:58.980> but<00:43:59.220> there's<00:43:59.400> no 00:43:59.540 --> 00:43:59.550 align:start position:0% aren't doing on their own but there's no 00:43:59.550 --> 00:44:01.730 align:start position:0% aren't doing on their own but there's no sort<00:43:59.820> of<00:43:59.910> shared<00:44:00.440> stuff<00:44:01.440> out<00:44:01.560> there<00:44:01.650> that's 00:44:01.730 --> 00:44:01.740 align:start position:0% sort of shared stuff out there that's 00:44:01.740 --> 00:44:03.890 align:start position:0% sort of shared stuff out there that's actually<00:44:02.210> quite<00:44:03.210> interesting<00:44:03.720> but<00:44:03.840> also 00:44:03.890 --> 00:44:03.900 align:start position:0% actually quite interesting but also 00:44:03.900 --> 00:44:07.340 align:start position:0% actually quite interesting but also risky<00:44:04.850> so<00:44:05.850> when<00:44:06.060> you<00:44:06.150> look<00:44:06.330> at<00:44:06.480> like<00:44:06.690> consensus 00:44:07.340 --> 00:44:07.350 align:start position:0% risky so when you look at like consensus 00:44:07.350 --> 00:44:09.890 align:start position:0% risky so when you look at like consensus breaks<00:44:07.590> sometimes<00:44:08.030> what<00:44:09.030> people<00:44:09.540> do<00:44:09.720> is<00:44:09.870> they 00:44:09.890 --> 00:44:09.900 align:start position:0% breaks sometimes what people do is they 00:44:09.900 --> 00:44:12.440 align:start position:0% breaks sometimes what people do is they attack<00:44:10.320> one<00:44:11.310> of<00:44:11.400> the<00:44:11.460> implementations<00:44:12.060> and 00:44:12.440 --> 00:44:12.450 align:start position:0% attack one of the implementations and 00:44:12.450 --> 00:44:15.290 align:start position:0% attack one of the implementations and cause<00:44:12.990> it<00:44:13.170> to<00:44:13.310> you<00:44:14.310> know<00:44:14.430> maybe<00:44:14.610> see<00:44:15.000> a<00:44:15.030> block 00:44:15.290 --> 00:44:15.300 align:start position:0% cause it to you know maybe see a block 00:44:15.300 --> 00:44:17.800 align:start position:0% cause it to you know maybe see a block as<00:44:15.450> invalid<00:44:15.870> when<00:44:15.960> it<00:44:16.080> should<00:44:16.260> be<00:44:16.350> valid<00:44:16.710> and 00:44:17.800 --> 00:44:17.810 align:start position:0% as invalid when it should be valid and 00:44:17.810 --> 00:44:20.120 align:start position:0% as invalid when it should be valid and you<00:44:18.810> know<00:44:18.900> the<00:44:19.020> safest<00:44:19.440> way<00:44:19.590> in<00:44:19.650> my<00:44:19.770> opinion<00:44:19.950> is 00:44:20.120 --> 00:44:20.130 align:start position:0% you know the safest way in my opinion is 00:44:20.130 --> 00:44:21.380 align:start position:0% you know the safest way in my opinion is to<00:44:20.220> connect<00:44:20.460> to<00:44:20.520> both<00:44:20.670> of<00:44:20.820> them<00:44:20.940> and<00:44:21.090> then<00:44:21.180> see 00:44:21.380 --> 00:44:21.390 align:start position:0% to connect to both of them and then see 00:44:21.390 --> 00:44:23.450 align:start position:0% to connect to both of them and then see if<00:44:21.480> there's<00:44:21.690> a<00:44:21.780> substantial<00:44:22.530> difference<00:44:23.160> in 00:44:23.450 --> 00:44:23.460 align:start position:0% if there's a substantial difference in 00:44:23.460 --> 00:44:26.420 align:start position:0% if there's a substantial difference in the<00:44:23.580> two<00:44:23.730> chain<00:44:24.300> heads<00:44:24.540> by<00:44:25.320> you<00:44:26.100> know<00:44:26.220> a 00:44:26.420 --> 00:44:26.430 align:start position:0% the two chain heads by you know a 00:44:26.430 --> 00:44:29.030 align:start position:0% the two chain heads by you know a significant<00:44:27.060> amount<00:44:27.210> of<00:44:27.300> work<00:44:27.510> right<00:44:27.860> if<00:44:28.860> you 00:44:29.030 --> 00:44:29.040 align:start position:0% significant amount of work right if you 00:44:29.040 --> 00:44:31.280 align:start position:0% significant amount of work right if you change<00:44:29.370> both<00:44:29.550> of<00:44:29.700> them<00:44:29.880> it's<00:44:30.840> actually<00:44:31.140> good 00:44:31.280 --> 00:44:31.290 align:start position:0% change both of them it's actually good 00:44:31.290 --> 00:44:33.770 align:start position:0% change both of them it's actually good in<00:44:31.410> that<00:44:31.530> you<00:44:31.740> were<00:44:31.890> well<00:44:32.640> kind<00:44:33.060> of<00:44:33.180> good<00:44:33.420> in 00:44:33.770 --> 00:44:33.780 align:start position:0% in that you were well kind of good in 00:44:33.780 --> 00:44:36.620 align:start position:0% in that you were well kind of good in that<00:44:34.080> you<00:44:34.230> get<00:44:34.470> the<00:44:35.430> most<00:44:35.730> valid<00:44:36.030> one<00:44:36.360> in<00:44:36.510> that 00:44:36.620 --> 00:44:36.630 align:start position:0% that you get the most valid one in that 00:44:36.630 --> 00:44:38.720 align:start position:0% that you get the most valid one in that both<00:44:36.840> of<00:44:36.960> them<00:44:37.080> will<00:44:37.260> see<00:44:37.440> it<00:44:37.500> as<00:44:37.590> that<00:44:37.740> it<00:44:37.800> but 00:44:38.720 --> 00:44:38.730 align:start position:0% both of them will see it as that it but 00:44:38.730 --> 00:44:40.120 align:start position:0% both of them will see it as that it but that<00:44:38.880> could<00:44:39.060> be<00:44:39.090> something<00:44:39.450> out<00:44:39.540> there<00:44:39.570> that 00:44:40.120 --> 00:44:40.130 align:start position:0% that could be something out there that 00:44:40.130 --> 00:44:43.040 align:start position:0% that could be something out there that has<00:44:41.130> more<00:44:41.370> hash<00:44:41.580> power<00:44:41.820> that<00:44:42.480> you<00:44:42.660> don't<00:44:42.840> see 00:44:43.040 --> 00:44:43.050 align:start position:0% has more hash power that you don't see 00:44:43.050 --> 00:44:45.950 align:start position:0% has more hash power that you don't see as<00:44:43.140> that<00:44:43.320> it<00:44:43.500> so<00:44:44.370> right<00:44:44.940> yeah<00:44:45.510> it's<00:44:45.750> sort<00:44:45.840> of 00:44:45.950 --> 00:44:45.960 align:start position:0% as that it so right yeah it's sort of 00:44:45.960 --> 00:44:49.310 align:start position:0% as that it so right yeah it's sort of it's<00:44:46.290> sort<00:44:46.350> of<00:44:46.500> like<00:44:46.650> it<00:44:46.860> gives<00:44:47.070> up<00:44:48.320> lightness 00:44:49.310 --> 00:44:49.320 align:start position:0% it's sort of like it gives up lightness 00:44:49.320 --> 00:44:51.680 align:start position:0% it's sort of like it gives up lightness right<00:44:50.070> in<00:44:50.280> the<00:44:50.490> event<00:44:50.550> of<00:44:50.790> a<00:44:50.880> chain<00:44:51.120> split<00:44:51.570> it 00:44:51.680 --> 00:44:51.690 align:start position:0% right in the event of a chain split it 00:44:51.690 --> 00:44:53.360 align:start position:0% right in the event of a chain split it so<00:44:51.780> it<00:44:51.840> gives<00:44:52.050> up<00:44:52.200> liveness<00:44:52.410> since<00:44:52.830> instead<00:44:53.280> of 00:44:53.360 --> 00:44:53.370 align:start position:0% so it gives up liveness since instead of 00:44:53.370 --> 00:44:54.770 align:start position:0% so it gives up liveness since instead of like<00:44:53.520> just<00:44:53.790> keep<00:44:54.030> running<00:44:54.210> on<00:44:54.420> and<00:44:54.660> like 00:44:54.770 --> 00:44:54.780 align:start position:0% like just keep running on and like 00:44:54.780 --> 00:44:55.910 align:start position:0% like just keep running on and like hoping<00:44:55.110> you're<00:44:55.200> on<00:44:55.290> the<00:44:55.380> right<00:44:55.500> side<00:44:55.740> of<00:44:55.830> the 00:44:55.910 --> 00:44:55.920 align:start position:0% hoping you're on the right side of the 00:44:55.920 --> 00:44:58.400 align:start position:0% hoping you're on the right side of the chain<00:44:56.130> it<00:44:56.880> says<00:44:57.150> we're<00:44:57.630> just<00:44:57.810> gonna<00:44:57.930> stop<00:44:58.200> and 00:44:58.400 --> 00:44:58.410 align:start position:0% chain it says we're just gonna stop and 00:44:58.410 --> 00:44:59.300 align:start position:0% chain it says we're just gonna stop and we're<00:44:58.560> gonna<00:44:58.680> figure<00:44:58.800> out<00:44:58.890> what's<00:44:58.950> going<00:44:59.190> on 00:44:59.300 --> 00:44:59.310 align:start position:0% we're gonna figure out what's going on 00:44:59.310 --> 00:45:01.490 align:start position:0% we're gonna figure out what's going on here<00:44:59.520> and<00:44:59.910> we're<00:45:00.150> gonna<00:45:00.240> investigate<00:45:00.600> it<00:45:00.870> and 00:45:01.490 --> 00:45:01.500 align:start position:0% here and we're gonna investigate it and 00:45:01.500 --> 00:45:03.290 align:start position:0% here and we're gonna investigate it and then<00:45:02.130> attempt<00:45:02.490> to<00:45:02.550> make<00:45:02.730> the<00:45:02.850> right<00:45:02.970> decision 00:45:03.290 --> 00:45:03.300 align:start position:0% then attempt to make the right decision 00:45:03.300 --> 00:45:04.580 align:start position:0% then attempt to make the right decision there<00:45:03.450> and<00:45:03.600> catch<00:45:03.930> up<00:45:04.110> or<00:45:04.230> whatever<00:45:04.410> it<00:45:04.530> needs 00:45:04.580 --> 00:45:04.590 align:start position:0% there and catch up or whatever it needs 00:45:04.590 --> 00:45:06.650 align:start position:0% there and catch up or whatever it needs to<00:45:04.680> do<00:45:04.860> that's<00:45:05.820> sort<00:45:06.030> of<00:45:06.060> that's<00:45:06.270> adding<00:45:06.600> a 00:45:06.650 --> 00:45:06.660 align:start position:0% to do that's sort of that's adding a 00:45:06.660 --> 00:45:07.670 align:start position:0% to do that's sort of that's adding a great<00:45:06.810> point<00:45:06.930> though<00:45:07.110> that<00:45:07.230> is<00:45:07.350> the<00:45:07.380> sort<00:45:07.650> of 00:45:07.670 --> 00:45:07.680 align:start position:0% great point though that is the sort of 00:45:07.680 --> 00:45:08.960 align:start position:0% great point though that is the sort of trade-off<00:45:07.950> it<00:45:08.190> makes<00:45:08.370> to<00:45:08.520> do<00:45:08.610> something<00:45:08.880> like 00:45:08.960 --> 00:45:08.970 align:start position:0% trade-off it makes to do something like 00:45:08.970 --> 00:45:10.420 align:start position:0% trade-off it makes to do something like that<00:45:09.150> we're<00:45:09.480> gonna<00:45:09.570> stop<00:45:09.870> the<00:45:10.050> world<00:45:10.200> and 00:45:10.420 --> 00:45:10.430 align:start position:0% that we're gonna stop the world and 00:45:10.430 --> 00:45:13.030 align:start position:0% that we're gonna stop the world and until<00:45:11.430> we<00:45:11.490> figure<00:45:11.610> out<00:45:11.730> what's<00:45:11.940> going<00:45:12.150> on<00:45:12.240> yeah 00:45:13.030 --> 00:45:13.040 align:start position:0% until we figure out what's going on yeah 00:45:13.040 --> 00:45:18.770 align:start position:0% until we figure out what's going on yeah the<00:45:14.040> world<00:45:14.220> weird<00:45:16.580> all<00:45:17.580> right<00:45:17.820> I<00:45:17.850> think<00:45:18.030> I'll 00:45:18.770 --> 00:45:18.780 align:start position:0% the world weird all right I think I'll 00:45:18.780 --> 00:45:20.360 align:start position:0% the world weird all right I think I'll do<00:45:18.930> that<00:45:19.080> I'll<00:45:19.170> do<00:45:19.260> this<00:45:19.380> last<00:45:19.560> question<00:45:20.100> and<00:45:20.280> I 00:45:20.360 --> 00:45:20.370 align:start position:0% do that I'll do this last question and I 00:45:20.370 --> 00:45:21.560 align:start position:0% do that I'll do this last question and I would<00:45:20.430> love<00:45:20.610> to<00:45:20.700> do<00:45:20.820> some<00:45:21.000> some<00:45:21.270> audience 00:45:21.560 --> 00:45:21.570 align:start position:0% would love to do some some audience 00:45:21.570 --> 00:45:23.180 align:start position:0% would love to do some some audience questions<00:45:21.630> if<00:45:21.990> you<00:45:22.080> have<00:45:22.110> them<00:45:22.260> in<00:45:22.860> the<00:45:23.070> last 00:45:23.180 --> 00:45:23.190 align:start position:0% questions if you have them in the last 00:45:23.190 --> 00:45:25.910 align:start position:0% questions if you have them in the last ten<00:45:23.370> minutes<00:45:23.460> there<00:45:23.820> so<00:45:24.620> we'll<00:45:25.620> do<00:45:25.680> an<00:45:25.770> easy 00:45:25.910 --> 00:45:25.920 align:start position:0% ten minutes there so we'll do an easy 00:45:25.920 --> 00:45:28.280 align:start position:0% ten minutes there so we'll do an easy one<00:45:26.160> which<00:45:26.520> is<00:45:26.730> so<00:45:27.660> what's<00:45:27.810> you<00:45:27.870> so<00:45:28.140> what's 00:45:28.280 --> 00:45:28.290 align:start position:0% one which is so what's you so what's 00:45:28.290 --> 00:45:29.480 align:start position:0% one which is so what's you so what's your<00:45:28.380> favorite<00:45:28.680> thing<00:45:28.710> about<00:45:28.890> working<00:45:29.070> with 00:45:29.480 --> 00:45:29.490 align:start position:0% your favorite thing about working with 00:45:29.490 --> 00:45:31.220 align:start position:0% your favorite thing about working with the<00:45:29.580> theorem<00:45:29.990> versus<00:45:30.990> the<00:45:31.110> other 00:45:31.220 --> 00:45:31.230 align:start position:0% the theorem versus the other 00:45:31.230 --> 00:45:35.660 align:start position:0% the theorem versus the other cryptocurrency<00:45:31.650> is<00:45:31.920> equally<00:45:34.370> obvious<00:45:35.370> answer 00:45:35.660 --> 00:45:35.670 align:start position:0% cryptocurrency is equally obvious answer 00:45:35.670 --> 00:45:38.060 align:start position:0% cryptocurrency is equally obvious answer smart<00:45:35.940> contracts<00:45:36.330> right<00:45:36.570> there's<00:45:37.080> Stoppers 00:45:38.060 --> 00:45:38.070 align:start position:0% smart contracts right there's Stoppers 00:45:38.070 --> 00:45:39.890 align:start position:0% smart contracts right there's Stoppers so<00:45:38.610> much<00:45:38.760> more<00:45:39.000> that<00:45:39.120> you<00:45:39.180> can<00:45:39.390> do<00:45:39.600> so<00:45:39.810> many 00:45:39.890 --> 00:45:39.900 align:start position:0% so much more that you can do so many 00:45:39.900 --> 00:45:41.810 align:start position:0% so much more that you can do so many more<00:45:40.110> interesting<00:45:40.320> creative<00:45:41.040> solutions<00:45:41.610> to<00:45:41.700> a 00:45:41.810 --> 00:45:41.820 align:start position:0% more interesting creative solutions to a 00:45:41.820 --> 00:45:44.750 align:start position:0% more interesting creative solutions to a lot<00:45:42.000> of<00:45:42.030> the<00:45:42.150> problems<00:45:42.480> that<00:45:43.130> aren't<00:45:44.130> specific 00:45:44.750 --> 00:45:44.760 align:start position:0% lot of the problems that aren't specific 00:45:44.760 --> 00:45:47.440 align:start position:0% lot of the problems that aren't specific to<00:45:44.790> aetherium<00:45:45.240> necessarily<00:45:46.010> things<00:45:47.010> like 00:45:47.440 --> 00:45:47.450 align:start position:0% to aetherium necessarily things like 00:45:47.450 --> 00:45:49.460 align:start position:0% to aetherium necessarily things like it's<00:45:48.450> has<00:45:48.690> offered<00:45:49.020> its<00:45:49.050> own<00:45:49.230> share<00:45:49.440> of 00:45:49.460 --> 00:45:49.470 align:start position:0% it's has offered its own share of 00:45:49.470 --> 00:45:51.290 align:start position:0% it's has offered its own share of problems<00:45:49.860> but<00:45:50.100> and<00:45:50.370> and<00:45:50.700> really<00:45:50.940> just<00:45:51.060> a 00:45:51.290 --> 00:45:51.300 align:start position:0% problems but and and really just a 00:45:51.300 --> 00:45:53.540 align:start position:0% problems but and and really just a community<00:45:51.660> like<00:45:51.930> there's<00:45:52.140> a<00:45:52.310> huge<00:45:53.310> community 00:45:53.540 --> 00:45:53.550 align:start position:0% community like there's a huge community 00:45:53.550 --> 00:45:56.390 align:start position:0% community like there's a huge community around<00:45:54.060> the<00:45:54.690> area<00:45:55.080> and<00:45:55.350> building<00:45:56.070> this<00:45:56.220> out 00:45:56.390 --> 00:45:56.400 align:start position:0% around the area and building this out 00:45:56.400 --> 00:46:00.410 align:start position:0% around the area and building this out that<00:45:56.730> does<00:45:56.910> make<00:45:57.120> it<00:45:59.030> never<00:46:00.030> a<00:46:00.120> boring<00:46:00.330> day 00:46:00.410 --> 00:46:00.420 align:start position:0% that does make it never a boring day 00:46:00.420 --> 00:46:02.570 align:start position:0% that does make it never a boring day right<00:46:00.750> never<00:46:01.560> a<00:46:01.680> boring<00:46:01.890> day<00:46:01.980> it's<00:46:02.250> it's 00:46:02.570 --> 00:46:02.580 align:start position:0% right never a boring day it's it's 00:46:02.580 --> 00:46:03.500 align:start position:0% right never a boring day it's it's always<00:46:02.700> interesting<00:46:03.030> there's<00:46:03.420> always 00:46:03.500 --> 00:46:03.510 align:start position:0% always interesting there's always 00:46:03.510 --> 00:46:05.750 align:start position:0% always interesting there's always something<00:46:03.870> new<00:46:03.900> happening<00:46:04.380> it<00:46:04.650> moves<00:46:04.980> so<00:46:05.520> fast 00:46:05.750 --> 00:46:05.760 align:start position:0% something new happening it moves so fast 00:46:05.760 --> 00:46:09.590 align:start position:0% something new happening it moves so fast that<00:46:06.120> you<00:46:07.160> have<00:46:08.160> to<00:46:08.310> almost<00:46:08.970> struggle<00:46:09.390> to<00:46:09.480> keep 00:46:09.590 --> 00:46:09.600 align:start position:0% that you have to almost struggle to keep 00:46:09.600 --> 00:46:10.580 align:start position:0% that you have to almost struggle to keep up<00:46:09.750> with<00:46:09.870> it<00:46:09.990> sometimes 00:46:10.580 --> 00:46:10.590 align:start position:0% up with it sometimes 00:46:10.590 --> 00:46:13.010 align:start position:0% up with it sometimes that's<00:46:11.310> a<00:46:11.370> good<00:46:11.520> problem<00:46:11.670> to<00:46:11.760> have<00:46:12.240> yeah<00:46:12.990> I 00:46:13.010 --> 00:46:13.020 align:start position:0% that's a good problem to have yeah I 00:46:13.020 --> 00:46:14.450 align:start position:0% that's a good problem to have yeah I think<00:46:13.200> that<00:46:13.440> the<00:46:13.500> community<00:46:13.860> in<00:46:13.920> aetherium<00:46:14.310> is 00:46:14.450 --> 00:46:14.460 align:start position:0% think that the community in aetherium is 00:46:14.460 --> 00:46:16.700 align:start position:0% think that the community in aetherium is this<00:46:14.700> for<00:46:15.240> me<00:46:15.390> one<00:46:15.690> of<00:46:15.780> the<00:46:15.840> strong<00:46:16.140> probably 00:46:16.700 --> 00:46:16.710 align:start position:0% this for me one of the strong probably 00:46:16.710 --> 00:46:21.050 align:start position:0% this for me one of the strong probably the<00:46:16.770> strongest<00:46:17.130> one<00:46:17.400> it<00:46:18.390> has<00:46:19.370> what<00:46:20.370> the<00:46:20.850> most 00:46:21.050 --> 00:46:21.060 align:start position:0% the strongest one it has what the most 00:46:21.060 --> 00:46:23.450 align:start position:0% the strongest one it has what the most developers<00:46:21.650> which<00:46:22.650> is<00:46:22.830> a<00:46:22.860> great<00:46:23.130> indication 00:46:23.450 --> 00:46:23.460 align:start position:0% developers which is a great indication 00:46:23.460 --> 00:46:25.040 align:start position:0% developers which is a great indication for<00:46:23.700> me<00:46:23.790> as<00:46:23.910> an<00:46:24.030> engineer<00:46:24.120> where<00:46:24.690> it's<00:46:24.840> going 00:46:25.040 --> 00:46:25.050 align:start position:0% for me as an engineer where it's going 00:46:25.050 --> 00:46:28.820 align:start position:0% for me as an engineer where it's going to<00:46:25.110> go<00:46:25.230> I<00:46:25.770> think<00:46:26.670> that<00:46:27.050> in<00:46:28.050> general<00:46:28.140> you<00:46:28.560> want 00:46:28.820 --> 00:46:28.830 align:start position:0% to go I think that in general you want 00:46:28.830 --> 00:46:30.470 align:start position:0% to go I think that in general you want to<00:46:29.190> build<00:46:29.370> when<00:46:29.730> you<00:46:29.820> build<00:46:30.030> something<00:46:30.270> you 00:46:30.470 --> 00:46:30.480 align:start position:0% to build when you build something you 00:46:30.480 --> 00:46:31.790 align:start position:0% to build when you build something you want<00:46:30.630> to<00:46:30.720> see<00:46:30.870> like<00:46:30.990> other<00:46:31.140> people<00:46:31.410> are<00:46:31.500> using 00:46:31.790 --> 00:46:31.800 align:start position:0% want to see like other people are using 00:46:31.800 --> 00:46:34.090 align:start position:0% want to see like other people are using it<00:46:31.920> so<00:46:32.100> there<00:46:32.550> is<00:46:32.580> ad<00:46:32.760> option<00:46:33.030> as<00:46:33.150> well<00:46:33.300> and<00:46:33.540> you 00:46:34.090 --> 00:46:34.100 align:start position:0% it so there is ad option as well and you 00:46:34.100 --> 00:46:36.800 align:start position:0% it so there is ad option as well and you you<00:46:35.100> feel<00:46:35.310> the<00:46:35.400> most<00:46:35.610> you<00:46:36.030> feel<00:46:36.210> more<00:46:36.390> welcomed 00:46:36.800 --> 00:46:36.810 align:start position:0% you feel the most you feel more welcomed 00:46:36.810 --> 00:46:39.110 align:start position:0% you feel the most you feel more welcomed building<00:46:37.410> something<00:46:37.740> on<00:46:37.830> aetherium<00:46:38.220> it's 00:46:39.110 --> 00:46:39.120 align:start position:0% building something on aetherium it's 00:46:39.120 --> 00:46:40.970 align:start position:0% building something on aetherium it's like<00:46:39.300> you<00:46:39.480> know<00:46:39.570> here<00:46:40.050> I<00:46:40.080> built<00:46:40.320> this<00:46:40.470> and<00:46:40.740> and 00:46:40.970 --> 00:46:40.980 align:start position:0% like you know here I built this and and 00:46:40.980 --> 00:46:42.740 align:start position:0% like you know here I built this and and and<00:46:41.130> everyone<00:46:41.460> likes<00:46:41.850> to<00:46:41.970> try<00:46:42.180> and<00:46:42.390> see<00:46:42.600> what 00:46:42.740 --> 00:46:42.750 align:start position:0% and everyone likes to try and see what 00:46:42.750 --> 00:46:45.350 align:start position:0% and everyone likes to try and see what kind<00:46:42.900> of<00:46:42.930> depth<00:46:43.140> you<00:46:43.260> build<00:46:43.530> and<00:46:43.980> I<00:46:44.310> really<00:46:44.580> you 00:46:45.350 --> 00:46:45.360 align:start position:0% kind of depth you build and I really you 00:46:45.360 --> 00:46:47.960 align:start position:0% kind of depth you build and I really you know<00:46:45.420> I<00:46:45.510> really<00:46:45.870> enjoy<00:46:46.110> that<00:46:46.280> yeah<00:46:47.280> I<00:46:47.580> think 00:46:47.960 --> 00:46:47.970 align:start position:0% know I really enjoy that yeah I think 00:46:47.970 --> 00:46:49.460 align:start position:0% know I really enjoy that yeah I think that's<00:46:48.090> a<00:46:48.150> big<00:46:48.300> part<00:46:48.480> I<00:46:48.690> think<00:46:49.080> yeah<00:46:49.350> it's 00:46:49.460 --> 00:46:49.470 align:start position:0% that's a big part I think yeah it's 00:46:49.470 --> 00:46:51.470 align:start position:0% that's a big part I think yeah it's similar<00:46:49.620> answers<00:46:49.950> for<00:46:50.220> me<00:46:50.340> is<00:46:50.580> yeah<00:46:51.180> I<00:46:51.210> mean 00:46:51.470 --> 00:46:51.480 align:start position:0% similar answers for me is yeah I mean 00:46:51.480 --> 00:46:52.970 align:start position:0% similar answers for me is yeah I mean that<00:46:51.810> what<00:46:52.080> people<00:46:52.260> can<00:46:52.530> do<00:46:52.620> is<00:46:52.770> smart 00:46:52.970 --> 00:46:52.980 align:start position:0% that what people can do is smart 00:46:52.980 --> 00:46:54.230 align:start position:0% that what people can do is smart contracts<00:46:53.370> like<00:46:53.520> I<00:46:53.640> don't<00:46:53.700> really<00:46:53.910> do<00:46:54.120> much 00:46:54.230 --> 00:46:54.240 align:start position:0% contracts like I don't really do much 00:46:54.240 --> 00:46:56.210 align:start position:0% contracts like I don't really do much work<00:46:54.480> with<00:46:54.600> them<00:46:54.750> myself<00:46:54.930> but<00:46:55.680> to<00:46:55.890> see<00:46:56.070> what 00:46:56.210 --> 00:46:56.220 align:start position:0% work with them myself but to see what 00:46:56.220 --> 00:46:57.140 align:start position:0% work with them myself but to see what people<00:46:56.340> are<00:46:56.460> able<00:46:56.640> to<00:46:56.670> produce<00:46:56.820> especially 00:46:57.140 --> 00:46:57.150 align:start position:0% people are able to produce especially 00:46:57.150 --> 00:46:58.790 align:start position:0% people are able to produce especially like<00:46:57.540> all<00:46:57.690> the<00:46:57.810> recent<00:46:58.050> sort<00:46:58.230> of<00:46:58.320> financial 00:46:58.790 --> 00:46:58.800 align:start position:0% like all the recent sort of financial 00:46:58.800 --> 00:47:00.170 align:start position:0% like all the recent sort of financial instruments<00:46:59.010> and<00:46:59.280> stuff<00:46:59.520> things<00:46:59.820> like<00:46:59.970> like 00:47:00.170 --> 00:47:00.180 align:start position:0% instruments and stuff things like like 00:47:00.180 --> 00:47:02.150 align:start position:0% instruments and stuff things like like die<00:47:00.630> existing<00:47:01.170> and<00:47:01.320> you<00:47:01.350> know<00:47:01.470> the<00:47:01.680> ability<00:47:01.860> to 00:47:02.150 --> 00:47:02.160 align:start position:0% die existing and you know the ability to 00:47:02.160 --> 00:47:03.500 align:start position:0% die existing and you know the ability to be<00:47:02.250> able<00:47:02.370> to<00:47:02.490> create<00:47:02.850> some<00:47:03.030> sort<00:47:03.240> of<00:47:03.270> thing 00:47:03.500 --> 00:47:03.510 align:start position:0% be able to create some sort of thing 00:47:03.510 --> 00:47:04.930 align:start position:0% be able to create some sort of thing that<00:47:03.570> has<00:47:03.810> this<00:47:03.960> stable<00:47:04.290> value<00:47:04.440> without 00:47:04.930 --> 00:47:04.940 align:start position:0% that has this stable value without 00:47:04.940 --> 00:47:07.520 align:start position:0% that has this stable value without anything<00:47:05.940> actually<00:47:06.270> behind<00:47:07.020> it<00:47:07.230> is<00:47:07.350> this 00:47:07.520 --> 00:47:07.530 align:start position:0% anything actually behind it is this 00:47:07.530 --> 00:47:09.590 align:start position:0% anything actually behind it is this really<00:47:07.830> interesting<00:47:08.130> concept<00:47:08.580> or<00:47:09.000> all<00:47:09.480> the 00:47:09.590 --> 00:47:09.600 align:start position:0% really interesting concept or all the 00:47:09.600 --> 00:47:11.450 align:start position:0% really interesting concept or all the people<00:47:09.750> are<00:47:10.020> doing<00:47:10.080> with<00:47:10.260> you<00:47:10.410> know<00:47:10.530> the<00:47:11.430> the 00:47:11.450 --> 00:47:11.460 align:start position:0% people are doing with you know the the 00:47:11.460 --> 00:47:14.510 align:start position:0% people are doing with you know the the relays<00:47:12.000> and<00:47:12.450> all<00:47:12.600> the<00:47:13.070> variants<00:47:14.070> of<00:47:14.220> you<00:47:14.430> know 00:47:14.510 --> 00:47:14.520 align:start position:0% relays and all the variants of you know 00:47:14.520 --> 00:47:17.180 align:start position:0% relays and all the variants of you know loans<00:47:14.850> and<00:47:15.240> all<00:47:15.690> that<00:47:15.870> is<00:47:16.050> somehow<00:47:16.500> happening 00:47:17.180 --> 00:47:17.190 align:start position:0% loans and all that is somehow happening 00:47:17.190 --> 00:47:18.620 align:start position:0% loans and all that is somehow happening in<00:47:17.340> this<00:47:17.430> world<00:47:17.820> and<00:47:18.090> it's<00:47:18.210> kind<00:47:18.390> of<00:47:18.450> crazy 00:47:18.620 --> 00:47:18.630 align:start position:0% in this world and it's kind of crazy 00:47:18.630 --> 00:47:20.030 align:start position:0% in this world and it's kind of crazy that<00:47:18.840> that<00:47:18.990> happens<00:47:19.290> and<00:47:19.530> you<00:47:19.590> can<00:47:19.710> just<00:47:19.860> very 00:47:20.030 --> 00:47:20.040 align:start position:0% that that happens and you can just very 00:47:20.040 --> 00:47:21.770 align:start position:0% that that happens and you can just very easily<00:47:20.130> go<00:47:20.550> on<00:47:20.580> to<00:47:20.850> some<00:47:21.030> you<00:47:21.180> know<00:47:21.300> some 00:47:21.770 --> 00:47:21.780 align:start position:0% easily go on to some you know some 00:47:21.780 --> 00:47:23.600 align:start position:0% easily go on to some you know some wallet<00:47:22.170> app<00:47:22.290> and<00:47:22.590> instantly<00:47:22.980> you<00:47:23.250> know<00:47:23.280> take 00:47:23.600 --> 00:47:23.610 align:start position:0% wallet app and instantly you know take 00:47:23.610 --> 00:47:25.640 align:start position:0% wallet app and instantly you know take out<00:47:23.730> a<00:47:23.760> loan<00:47:23.970> or<00:47:24.240> something<00:47:24.540> and<00:47:24.720> and<00:47:25.530> that 00:47:25.640 --> 00:47:25.650 align:start position:0% out a loan or something and and that 00:47:25.650 --> 00:47:27.140 align:start position:0% out a loan or something and and that kind<00:47:25.830> of<00:47:25.860> works<00:47:26.040> and<00:47:26.520> then<00:47:26.700> the<00:47:26.760> community<00:47:27.030> is 00:47:27.140 --> 00:47:27.150 align:start position:0% kind of works and then the community is 00:47:27.150 --> 00:47:29.540 align:start position:0% kind of works and then the community is yeah<00:47:27.270> also<00:47:27.600> really<00:47:27.930> I<00:47:28.140> think<00:47:28.550> generally 00:47:29.540 --> 00:47:29.550 align:start position:0% yeah also really I think generally 00:47:29.550 --> 00:47:31.760 align:start position:0% yeah also really I think generally healthy<00:47:29.880> community<00:47:30.420> and<00:47:30.690> doesn't<00:47:31.410> have<00:47:31.620> as 00:47:31.760 --> 00:47:31.770 align:start position:0% healthy community and doesn't have as 00:47:31.770 --> 00:47:33.590 align:start position:0% healthy community and doesn't have as much<00:47:31.980> of<00:47:32.040> the<00:47:32.430> sort<00:47:32.820> of<00:47:32.850> tribalism<00:47:33.240> you<00:47:33.480> might 00:47:33.590 --> 00:47:33.600 align:start position:0% much of the sort of tribalism you might 00:47:33.600 --> 00:47:34.930 align:start position:0% much of the sort of tribalism you might see<00:47:33.690> across<00:47:33.870> all<00:47:34.050> different<00:47:34.200> block<00:47:34.650> chains 00:47:34.930 --> 00:47:34.940 align:start position:0% see across all different block chains 00:47:34.940 --> 00:47:37.430 align:start position:0% see across all different block chains there's<00:47:35.940> you<00:47:36.240> know<00:47:36.270> some<00:47:36.540> of<00:47:36.630> it<00:47:36.750> of<00:47:36.900> course<00:47:36.930> as 00:47:37.430 --> 00:47:37.440 align:start position:0% there's you know some of it of course as 00:47:37.440 --> 00:47:39.260 align:start position:0% there's you know some of it of course as there<00:47:37.620> is<00:47:37.710> anywhere<00:47:38.010> but<00:47:38.640> generally<00:47:39.060> I<00:47:39.090> find 00:47:39.260 --> 00:47:39.270 align:start position:0% there is anywhere but generally I find 00:47:39.270 --> 00:47:41.510 align:start position:0% there is anywhere but generally I find that<00:47:39.720> the<00:47:40.080> community<00:47:40.410> is<00:47:40.470> very<00:47:40.620> sort<00:47:41.130> of<00:47:41.190> open 00:47:41.510 --> 00:47:41.520 align:start position:0% that the community is very sort of open 00:47:41.520 --> 00:47:43.460 align:start position:0% that the community is very sort of open and<00:47:41.790> willing<00:47:42.450> to<00:47:42.600> work<00:47:42.870> with<00:47:43.110> other<00:47:43.290> block 00:47:43.460 --> 00:47:43.470 align:start position:0% and willing to work with other block 00:47:43.470 --> 00:47:44.750 align:start position:0% and willing to work with other block chains<00:47:43.710> up<00:47:43.980> and<00:47:44.100> try<00:47:44.190> and<00:47:44.340> push<00:47:44.460> sort<00:47:44.700> of 00:47:44.750 --> 00:47:44.760 align:start position:0% chains up and try and push sort of 00:47:44.760 --> 00:47:46.280 align:start position:0% chains up and try and push sort of everything<00:47:45.150> forward<00:47:45.420> I<00:47:45.720> think<00:47:45.930> like<00:47:46.140> one 00:47:46.280 --> 00:47:46.290 align:start position:0% everything forward I think like one 00:47:46.290 --> 00:47:48.950 align:start position:0% everything forward I think like one great<00:47:46.470> example<00:47:46.620> this<00:47:47.070> was<00:47:47.280> the<00:47:47.960> talk 00:47:48.950 --> 00:47:48.960 align:start position:0% great example this was the talk 00:47:48.960 --> 00:47:51.280 align:start position:0% great example this was the talk yesterday<00:47:49.170> on<00:47:49.590> verifiable<00:47:50.400> delay<00:47:50.610> functions 00:47:51.280 --> 00:47:51.290 align:start position:0% yesterday on verifiable delay functions 00:47:51.290 --> 00:47:53.540 align:start position:0% yesterday on verifiable delay functions that<00:47:52.290> they're<00:47:52.500> talking<00:47:52.920> about<00:47:53.010> doing<00:47:53.220> in 00:47:53.540 --> 00:47:53.550 align:start position:0% that they're talking about doing in 00:47:53.550 --> 00:47:56.960 align:start position:0% that they're talking about doing in serenity<00:47:54.180> is<00:47:54.570> this<00:47:54.870> the<00:47:55.830> it's<00:47:56.220> this<00:47:56.430> thing 00:47:56.960 --> 00:47:56.970 align:start position:0% serenity is this the it's this thing 00:47:56.970 --> 00:47:58.640 align:start position:0% serenity is this the it's this thing that's<00:47:57.120> not<00:47:57.270> specific<00:47:57.840> to<00:47:57.870> aetherium<00:47:58.320> like 00:47:58.640 --> 00:47:58.650 align:start position:0% that's not specific to aetherium like 00:47:58.650 --> 00:47:59.660 align:start position:0% that's not specific to aetherium like they're<00:47:58.800> actually<00:47:58.920> bringing<00:47:59.250> in<00:47:59.460> other 00:47:59.660 --> 00:47:59.670 align:start position:0% they're actually bringing in other 00:47:59.670 --> 00:48:01.790 align:start position:0% they're actually bringing in other chains<00:48:00.090> and<00:48:00.360> want<00:48:00.570> to<00:48:00.690> work<00:48:01.410> on<00:48:01.560> this<00:48:01.650> together 00:48:01.790 --> 00:48:01.800 align:start position:0% chains and want to work on this together 00:48:01.800 --> 00:48:03.620 align:start position:0% chains and want to work on this together in<00:48:02.070> collaboration<00:48:02.730> and<00:48:02.970> come<00:48:03.330> up<00:48:03.420> with<00:48:03.540> this 00:48:03.620 --> 00:48:03.630 align:start position:0% in collaboration and come up with this 00:48:03.630 --> 00:48:05.060 align:start position:0% in collaboration and come up with this just<00:48:03.900> better<00:48:04.200> cryptography<00:48:04.860> and<00:48:04.920> better 00:48:05.060 --> 00:48:05.070 align:start position:0% just better cryptography and better 00:48:05.070 --> 00:48:08.330 align:start position:0% just better cryptography and better system<00:48:05.460> to<00:48:05.640> you<00:48:06.360> know<00:48:06.710> have<00:48:07.710> this<00:48:07.980> you<00:48:08.310> know 00:48:08.330 --> 00:48:08.340 align:start position:0% system to you know have this you know 00:48:08.340 --> 00:48:10.760 align:start position:0% system to you know have this you know new<00:48:08.580> concept<00:48:09.090> to<00:48:09.120> work<00:48:09.330> for<00:48:09.930> for<00:48:10.170> everyone<00:48:10.560> and 00:48:10.760 --> 00:48:10.770 align:start position:0% new concept to work for for everyone and 00:48:10.770 --> 00:48:12.590 align:start position:0% new concept to work for for everyone and not<00:48:10.830> just<00:48:10.950> be<00:48:11.310> this<00:48:11.430> like<00:48:11.670> singular<00:48:12.150> thing<00:48:12.390> for 00:48:12.590 --> 00:48:12.600 align:start position:0% not just be this like singular thing for 00:48:12.600 --> 00:48:14.180 align:start position:0% not just be this like singular thing for a<00:48:12.630> theory<00:48:12.930> and<00:48:13.050> like<00:48:13.200> it's<00:48:13.350> you<00:48:13.500> know<00:48:13.530> our<00:48:13.920> baby 00:48:14.180 --> 00:48:14.190 align:start position:0% a theory and like it's you know our baby 00:48:14.190 --> 00:48:16.040 align:start position:0% a theory and like it's you know our baby and<00:48:14.370> we'll<00:48:14.460> just<00:48:14.610> you<00:48:14.760> know<00:48:14.790> keep<00:48:15.480> it<00:48:15.630> here<00:48:15.810> and 00:48:16.040 --> 00:48:16.050 align:start position:0% and we'll just you know keep it here and 00:48:16.050 --> 00:48:17.600 align:start position:0% and we'll just you know keep it here and nobody<00:48:16.620> else<00:48:16.770> can<00:48:16.860> have<00:48:17.040> it<00:48:17.100> they're<00:48:17.430> just 00:48:17.600 --> 00:48:17.610 align:start position:0% nobody else can have it they're just 00:48:17.610 --> 00:48:18.860 align:start position:0% nobody else can have it they're just like<00:48:17.760> let's<00:48:17.970> let's<00:48:18.180> share<00:48:18.450> that<00:48:18.630> with<00:48:18.780> the 00:48:18.860 --> 00:48:18.870 align:start position:0% like let's let's share that with the 00:48:18.870 --> 00:48:20.720 align:start position:0% like let's let's share that with the world<00:48:19.020> and<00:48:19.260> let's<00:48:19.380> you<00:48:19.650> know<00:48:19.680> make<00:48:20.430> it<00:48:20.550> all 00:48:20.720 --> 00:48:20.730 align:start position:0% world and let's you know make it all 00:48:20.730 --> 00:48:22.550 align:start position:0% world and let's you know make it all better<00:48:20.910> because<00:48:21.270> it's<00:48:21.690> we're<00:48:22.020> all<00:48:22.110> it's<00:48:22.380> so 00:48:22.550 --> 00:48:22.560 align:start position:0% better because it's we're all it's so 00:48:22.560 --> 00:48:23.990 align:start position:0% better because it's we're all it's so early<00:48:22.710> days<00:48:23.100> and<00:48:23.340> all<00:48:23.430> this<00:48:23.550> stuff 00:48:23.990 --> 00:48:24.000 align:start position:0% early days and all this stuff 00:48:24.000 --> 00:48:27.080 align:start position:0% early days and all this stuff is<00:48:24.030> a<00:48:24.090> lot<00:48:24.300> to<00:48:24.450> figure<00:48:24.600> out<00:48:24.720> and<00:48:25.250> I<00:48:26.250> don't<00:48:27.000> know 00:48:27.080 --> 00:48:27.090 align:start position:0% is a lot to figure out and I don't know 00:48:27.090 --> 00:48:28.520 align:start position:0% is a lot to figure out and I don't know who<00:48:27.240> the<00:48:27.360> winner<00:48:27.480> is<00:48:27.660> going<00:48:27.780> to<00:48:27.870> be<00:48:28.110> it<00:48:28.380> maybe 00:48:28.520 --> 00:48:28.530 align:start position:0% who the winner is going to be it maybe 00:48:28.530 --> 00:48:30.170 align:start position:0% who the winner is going to be it maybe we'll<00:48:28.740> all<00:48:28.860> be<00:48:29.040> winners<00:48:29.190> maybe<00:48:29.550> none<00:48:29.790> will<00:48:30.000> be 00:48:30.170 --> 00:48:30.180 align:start position:0% we'll all be winners maybe none will be 00:48:30.180 --> 00:48:32.870 align:start position:0% we'll all be winners maybe none will be but<00:48:30.690> we<00:48:30.780> want<00:48:30.960> a<00:48:31.050> you<00:48:31.170> know<00:48:31.400> I'll<00:48:32.400> just<00:48:32.760> work 00:48:32.870 --> 00:48:32.880 align:start position:0% but we want a you know I'll just work 00:48:32.880 --> 00:48:35.090 align:start position:0% but we want a you know I'll just work together<00:48:33.060> and<00:48:33.420> try<00:48:33.810> and<00:48:33.900> be<00:48:34.020> healthy<00:48:34.350> and<00:48:34.560> get 00:48:35.090 --> 00:48:35.100 align:start position:0% together and try and be healthy and get 00:48:35.100 --> 00:48:37.250 align:start position:0% together and try and be healthy and get there<00:48:35.420> all<00:48:36.420> right 00:48:37.250 --> 00:48:37.260 align:start position:0% there all right 00:48:37.260 --> 00:48:39.080 align:start position:0% there all right okay<00:48:37.740> so<00:48:37.800> we'll<00:48:38.010> open<00:48:38.070> up<00:48:38.220> to<00:48:38.280> questions<00:48:38.430> if 00:48:39.080 --> 00:48:39.090 align:start position:0% okay so we'll open up to questions if 00:48:39.090 --> 00:48:41.780 align:start position:0% okay so we'll open up to questions if anyone<00:48:39.300> has<00:48:39.420> any<00:48:39.570> all<00:48:40.380> right<00:48:40.650> I'll<00:48:41.550> just<00:48:41.610> hop 00:48:41.780 --> 00:48:41.790 align:start position:0% anyone has any all right I'll just hop 00:48:41.790 --> 00:48:43.370 align:start position:0% anyone has any all right I'll just hop down<00:48:41.940> here<00:48:42.090> with<00:48:42.180> this<00:48:42.270> microphone<00:48:42.540> hint<00:48:43.230> to 00:48:43.370 --> 00:48:43.380 align:start position:0% down here with this microphone hint to 00:48:43.380 --> 00:48:46.280 align:start position:0% down here with this microphone hint to you<00:48:44.420> so<00:48:45.420> you<00:48:45.480> guys<00:48:45.630> are<00:48:45.720> on<00:48:45.780> the<00:48:45.870> front<00:48:45.990> lines 00:48:46.280 --> 00:48:46.290 align:start position:0% you so you guys are on the front lines 00:48:46.290 --> 00:48:47.660 align:start position:0% you so you guys are on the front lines and<00:48:46.770> you'll<00:48:47.220> have<00:48:47.340> a<00:48:47.370> really<00:48:47.520> good 00:48:47.660 --> 00:48:47.670 align:start position:0% and you'll have a really good 00:48:47.670 --> 00:48:50.480 align:start position:0% and you'll have a really good perspective<00:48:47.880> on<00:48:48.210> this<00:48:48.420> I'm<00:48:49.380> curious<00:48:49.560> what<00:48:50.370> you 00:48:50.480 --> 00:48:50.490 align:start position:0% perspective on this I'm curious what you 00:48:50.490 --> 00:48:52.760 align:start position:0% perspective on this I'm curious what you which<00:48:50.700> projects<00:48:51.240> you<00:48:51.330> guys<00:48:51.480> think<00:48:51.840> belong<00:48:52.380> on 00:48:52.760 --> 00:48:52.770 align:start position:0% which projects you guys think belong on 00:48:52.770 --> 00:48:54.830 align:start position:0% which projects you guys think belong on chain<00:48:53.240> kind<00:48:54.240> of<00:48:54.360> where<00:48:54.450> you<00:48:54.540> draw<00:48:54.660> the<00:48:54.690> line 00:48:54.830 --> 00:48:54.840 align:start position:0% chain kind of where you draw the line 00:48:54.840 --> 00:48:58.220 align:start position:0% chain kind of where you draw the line for<00:48:55.140> that<00:48:55.230> and<00:48:56.060> you<00:48:57.060> know<00:48:57.120> as<00:48:57.300> assuming<00:48:58.110> that 00:48:58.220 --> 00:48:58.230 align:start position:0% for that and you know as assuming that 00:48:58.230 --> 00:48:59.510 align:start position:0% for that and you know as assuming that we<00:48:58.290> improve<00:48:58.620> efficiency<00:48:59.250> and<00:48:59.340> scalability 00:48:59.510 --> 00:48:59.520 align:start position:0% we improve efficiency and scalability 00:48:59.520 --> 00:49:01.340 align:start position:0% we improve efficiency and scalability and<00:48:59.970> stuff<00:49:00.150> do<00:49:00.570> you<00:49:00.630> guys<00:49:00.720> think<00:49:01.050> that<00:49:01.110> will 00:49:01.340 --> 00:49:01.350 align:start position:0% and stuff do you guys think that will 00:49:01.350 --> 00:49:09.710 align:start position:0% and stuff do you guys think that will change<00:49:01.380> so<00:49:02.100> how<00:49:03.860> ya<00:49:05.300> talk<00:49:06.300> first<00:49:06.510> yes<00:49:06.780> I<00:49:08.540> have<00:49:09.570> I 00:49:09.710 --> 00:49:09.720 align:start position:0% change so how ya talk first yes I have I 00:49:09.720 --> 00:49:12.170 align:start position:0% change so how ya talk first yes I have I could<00:49:09.960> flick<00:49:10.140> to<00:49:10.230> there<00:49:10.380> sorry<00:49:10.590> I<00:49:10.650> I<00:49:11.370> like<00:49:11.880> on 00:49:12.170 --> 00:49:12.180 align:start position:0% could flick to there sorry I I like on 00:49:12.180 --> 00:49:14.060 align:start position:0% could flick to there sorry I I like on changes<00:49:12.780> because<00:49:13.110> it's<00:49:13.440> sort<00:49:13.620> of<00:49:13.710> this 00:49:14.060 --> 00:49:14.070 align:start position:0% changes because it's sort of this 00:49:14.070 --> 00:49:15.590 align:start position:0% changes because it's sort of this singular<00:49:14.340> place<00:49:14.730> to<00:49:14.880> integrate<00:49:15.210> with<00:49:15.360> you 00:49:15.590 --> 00:49:15.600 align:start position:0% singular place to integrate with you 00:49:15.600 --> 00:49:16.880 align:start position:0% singular place to integrate with you know<00:49:15.690> the<00:49:15.780> title<00:49:16.050> is<00:49:16.140> integrating<00:49:16.770> with 00:49:16.880 --> 00:49:16.890 align:start position:0% know the title is integrating with 00:49:16.890 --> 00:49:19.310 align:start position:0% know the title is integrating with etherium<00:49:17.340> and<00:49:18.150> as<00:49:18.570> we've<00:49:18.750> talked<00:49:18.990> about<00:49:19.050> it's 00:49:19.310 --> 00:49:19.320 align:start position:0% etherium and as we've talked about it's 00:49:19.320 --> 00:49:21.110 align:start position:0% etherium and as we've talked about it's already<00:49:19.500> sufficiently<00:49:19.920> complicated<00:49:20.310> and<00:49:21.030> the 00:49:21.110 --> 00:49:21.120 align:start position:0% already sufficiently complicated and the 00:49:21.120 --> 00:49:22.190 align:start position:0% already sufficiently complicated and the more<00:49:21.300> things<00:49:21.480> we<00:49:21.630> add<00:49:21.720> on<00:49:21.840> top<00:49:21.990> of<00:49:22.140> that 00:49:22.190 --> 00:49:22.200 align:start position:0% more things we add on top of that 00:49:22.200 --> 00:49:25.130 align:start position:0% more things we add on top of that especially<00:49:22.440> layer<00:49:22.770> to<00:49:23.040> things<00:49:23.610> and<00:49:24.140> various 00:49:25.130 --> 00:49:25.140 align:start position:0% especially layer to things and various 00:49:25.140 --> 00:49:26.210 align:start position:0% especially layer to things and various protocols<00:49:25.470> it<00:49:25.770> becomes<00:49:25.980> even<00:49:26.190> more 00:49:26.210 --> 00:49:26.220 align:start position:0% protocols it becomes even more 00:49:26.220 --> 00:49:28.130 align:start position:0% protocols it becomes even more complicated<00:49:26.730> so<00:49:27.090> the<00:49:27.120> sort<00:49:27.570> of<00:49:27.600> onboarding 00:49:28.130 --> 00:49:28.140 align:start position:0% complicated so the sort of onboarding 00:49:28.140 --> 00:49:30.740 align:start position:0% complicated so the sort of onboarding cost<00:49:28.380> gets<00:49:29.190> a<00:49:29.520> lot<00:49:29.760> more<00:49:29.790> expensive<00:49:30.330> and<00:49:30.540> it's 00:49:30.740 --> 00:49:30.750 align:start position:0% cost gets a lot more expensive and it's 00:49:30.750 --> 00:49:32.240 align:start position:0% cost gets a lot more expensive and it's not<00:49:30.840> as<00:49:31.050> easy<00:49:31.200> unless<00:49:31.500> we<00:49:31.680> build<00:49:31.860> tools<00:49:32.040> that 00:49:32.240 --> 00:49:32.250 align:start position:0% not as easy unless we build tools that 00:49:32.250 --> 00:49:34.670 align:start position:0% not as easy unless we build tools that can<00:49:32.340> somehow<00:49:32.550> do<00:49:32.790> this<00:49:33.020> but<00:49:34.020> if<00:49:34.140> you<00:49:34.230> know<00:49:34.260> now 00:49:34.670 --> 00:49:34.680 align:start position:0% can somehow do this but if you know now 00:49:34.680 --> 00:49:36.710 align:start position:0% can somehow do this but if you know now some<00:49:35.220> new<00:49:35.370> protocol<00:49:35.910> comes<00:49:36.120> out<00:49:36.300> that<00:49:36.600> you 00:49:36.710 --> 00:49:36.720 align:start position:0% some new protocol comes out that you 00:49:36.720 --> 00:49:38.060 align:start position:0% some new protocol comes out that you know<00:49:36.840> all<00:49:37.020> of<00:49:37.050> the<00:49:37.290> exchanges<00:49:37.530> all<00:49:37.890> the 00:49:38.060 --> 00:49:38.070 align:start position:0% know all of the exchanges all the 00:49:38.070 --> 00:49:39.620 align:start position:0% know all of the exchanges all the wallets<00:49:38.430> need<00:49:38.610> to<00:49:38.700> integrate<00:49:39.120> and<00:49:39.360> you<00:49:39.510> know 00:49:39.620 --> 00:49:39.630 align:start position:0% wallets need to integrate and you know 00:49:39.630 --> 00:49:40.820 align:start position:0% wallets need to integrate and you know you<00:49:39.690> scale<00:49:40.080> that<00:49:40.230> up<00:49:40.290> you<00:49:40.560> know<00:49:40.650> it's<00:49:40.770> a 00:49:40.820 --> 00:49:40.830 align:start position:0% you scale that up you know it's a 00:49:40.830 --> 00:49:42.950 align:start position:0% you scale that up you know it's a multiple<00:49:41.160> different<00:49:41.310> ones<00:49:41.630> that's<00:49:42.630> going<00:49:42.870> to 00:49:42.950 --> 00:49:42.960 align:start position:0% multiple different ones that's going to 00:49:42.960 --> 00:49:44.930 align:start position:0% multiple different ones that's going to be<00:49:43.050> fairly<00:49:43.290> difficult<00:49:43.560> and<00:49:44.040> so<00:49:44.370> keeping<00:49:44.760> it<00:49:44.880> on 00:49:44.930 --> 00:49:44.940 align:start position:0% be fairly difficult and so keeping it on 00:49:44.940 --> 00:49:46.700 align:start position:0% be fairly difficult and so keeping it on chain<00:49:45.240> you<00:49:45.420> know<00:49:45.540> has<00:49:45.810> some<00:49:46.020> nice<00:49:46.170> guarantees 00:49:46.700 --> 00:49:46.710 align:start position:0% chain you know has some nice guarantees 00:49:46.710 --> 00:49:49.220 align:start position:0% chain you know has some nice guarantees there<00:49:46.950> just<00:49:47.190> simplifies<00:49:47.640> it<00:49:47.910> overall<00:49:48.330> but 00:49:49.220 --> 00:49:49.230 align:start position:0% there just simplifies it overall but 00:49:49.230 --> 00:49:50.420 align:start position:0% there just simplifies it overall but clearly<00:49:49.440> that<00:49:49.620> has<00:49:49.830> sort<00:49:50.100> of<00:49:50.160> you<00:49:50.400> know 00:49:50.420 --> 00:49:50.430 align:start position:0% clearly that has sort of you know 00:49:50.430 --> 00:49:52.100 align:start position:0% clearly that has sort of you know scaling<00:49:50.850> in<00:49:51.000> limits<00:49:51.540> and<00:49:51.690> stuff<00:49:51.840> and<00:49:51.990> there's 00:49:52.100 --> 00:49:52.110 align:start position:0% scaling in limits and stuff and there's 00:49:52.110 --> 00:49:53.540 align:start position:0% scaling in limits and stuff and there's a<00:49:52.170> lot<00:49:52.320> that<00:49:52.350> can<00:49:52.590> be<00:49:52.650> done<00:49:52.710> off<00:49:52.950> chaining<00:49:53.370> and 00:49:53.540 --> 00:49:53.550 align:start position:0% a lot that can be done off chaining and 00:49:53.550 --> 00:49:55.640 align:start position:0% a lot that can be done off chaining and maybe<00:49:54.030> you<00:49:54.240> know<00:49:54.330> published<00:49:55.140> there<00:49:55.320> as<00:49:55.470> just 00:49:55.640 --> 00:49:55.650 align:start position:0% maybe you know published there as just 00:49:55.650 --> 00:49:57.320 align:start position:0% maybe you know published there as just some<00:49:55.830> proof<00:49:56.100> and<00:49:56.370> I<00:49:56.760> think<00:49:56.940> there's<00:49:57.090> also<00:49:57.240> a 00:49:57.320 --> 00:49:57.330 align:start position:0% some proof and I think there's also a 00:49:57.330 --> 00:49:58.820 align:start position:0% some proof and I think there's also a lot<00:49:57.510> of<00:49:57.600> value<00:49:57.780> in<00:49:57.840> that<00:49:58.020> if<00:49:58.200> we<00:49:58.470> can<00:49:58.590> have<00:49:58.740> you 00:49:58.820 --> 00:49:58.830 align:start position:0% lot of value in that if we can have you 00:49:58.830 --> 00:50:00.680 align:start position:0% lot of value in that if we can have you know<00:49:58.920> really<00:49:59.190> good<00:49:59.340> sort<00:49:59.550> of<00:49:59.640> second<00:50:00.600> layer 00:50:00.680 --> 00:50:00.690 align:start position:0% know really good sort of second layer 00:50:00.690 --> 00:50:03.020 align:start position:0% know really good sort of second layer solutions<00:50:01.140> to<00:50:01.290> to<00:50:01.410> to<00:50:01.530> pull<00:50:01.680> it<00:50:01.770> off<00:50:01.860> yeah<00:50:02.100> so<00:50:03.000> I 00:50:03.020 --> 00:50:03.030 align:start position:0% solutions to to to pull it off yeah so I 00:50:03.030 --> 00:50:05.240 align:start position:0% solutions to to to pull it off yeah so I would<00:50:03.420> give<00:50:03.780> it<00:50:03.930> like<00:50:04.260> I<00:50:04.440> think<00:50:04.770> there's<00:50:05.160> a 00:50:05.240 --> 00:50:05.250 align:start position:0% would give it like I think there's a 00:50:05.250 --> 00:50:07.160 align:start position:0% would give it like I think there's a trick<00:50:05.460> answer<00:50:05.640> to<00:50:05.850> that<00:50:05.970> because<00:50:06.570> you<00:50:06.810> sit<00:50:07.020> on 00:50:07.160 --> 00:50:07.170 align:start position:0% trick answer to that because you sit on 00:50:07.170 --> 00:50:09.860 align:start position:0% trick answer to that because you sit on chain<00:50:07.440> I<00:50:07.800> think<00:50:08.340> like<00:50:08.490> side<00:50:08.730> chain<00:50:09.000> right<00:50:09.660> now 00:50:09.860 --> 00:50:09.870 align:start position:0% chain I think like side chain right now 00:50:09.870 --> 00:50:13.100 align:start position:0% chain I think like side chain right now it's<00:50:10.110> the<00:50:10.200> best<00:50:10.790> because<00:50:11.790> you<00:50:12.630> know<00:50:12.750> with<00:50:12.930> side 00:50:13.100 --> 00:50:13.110 align:start position:0% it's the best because you know with side 00:50:13.110 --> 00:50:14.540 align:start position:0% it's the best because you know with side chains<00:50:13.440> that<00:50:13.560> checkpoint<00:50:14.010> it<00:50:14.100> into<00:50:14.250> the<00:50:14.340> main 00:50:14.540 --> 00:50:14.550 align:start position:0% chains that checkpoint it into the main 00:50:14.550 --> 00:50:17.390 align:start position:0% chains that checkpoint it into the main main<00:50:15.030> that<00:50:15.320> you<00:50:16.320> kind<00:50:16.530> of<00:50:16.590> get<00:50:16.830> a<00:50:17.070> lot<00:50:17.310> of 00:50:17.390 --> 00:50:17.400 align:start position:0% main that you kind of get a lot of 00:50:17.400 --> 00:50:19.970 align:start position:0% main that you kind of get a lot of advantages<00:50:17.910> that<00:50:18.120> of<00:50:19.080> being<00:50:19.470> on<00:50:19.620> chaining 00:50:19.970 --> 00:50:19.980 align:start position:0% advantages that of being on chaining 00:50:19.980 --> 00:50:20.870 align:start position:0% advantages that of being on chaining that<00:50:20.100> it's<00:50:20.220> really<00:50:20.400> easy<00:50:20.430> to<00:50:20.700> integrate 00:50:20.870 --> 00:50:20.880 align:start position:0% that it's really easy to integrate 00:50:20.880 --> 00:50:22.490 align:start position:0% that it's really easy to integrate because<00:50:21.210> people<00:50:21.630> can<00:50:22.050> see<00:50:22.230> you<00:50:22.320> through 00:50:22.490 --> 00:50:22.500 align:start position:0% because people can see you through 00:50:22.500 --> 00:50:24.350 align:start position:0% because people can see you through transactions<00:50:23.160> and<00:50:23.370> you've<00:50:23.460> got<00:50:23.670> an<00:50:23.760> EVM<00:50:24.120> on 00:50:24.350 --> 00:50:24.360 align:start position:0% transactions and you've got an EVM on 00:50:24.360 --> 00:50:26.780 align:start position:0% transactions and you've got an EVM on the<00:50:24.840> side<00:50:25.020> chain<00:50:25.290> so<00:50:25.950> you<00:50:25.980> can<00:50:26.130> run<00:50:26.460> quite<00:50:26.760> a 00:50:26.780 --> 00:50:26.790 align:start position:0% the side chain so you can run quite a 00:50:26.790 --> 00:50:28.520 align:start position:0% the side chain so you can run quite a bit<00:50:26.970> there<00:50:27.150> but<00:50:27.180> it's<00:50:27.600> not<00:50:27.690> going<00:50:27.810> to<00:50:28.080> scale 00:50:28.520 --> 00:50:28.530 align:start position:0% bit there but it's not going to scale 00:50:28.530 --> 00:50:32.090 align:start position:0% bit there but it's not going to scale eventually<00:50:29.490> still<00:50:29.760> I<00:50:30.000> mean<00:50:30.930> a<00:50:30.990> single<00:50:31.260> that 00:50:32.090 --> 00:50:32.100 align:start position:0% eventually still I mean a single that 00:50:32.100 --> 00:50:34.760 align:start position:0% eventually still I mean a single that could<00:50:32.400> still<00:50:32.580> take<00:50:32.970> up<00:50:33.150> you<00:50:34.110> know<00:50:34.200> all<00:50:34.440> the<00:50:34.620> gas 00:50:34.760 --> 00:50:34.770 align:start position:0% could still take up you know all the gas 00:50:34.770 --> 00:50:37.009 align:start position:0% could still take up you know all the gas on<00:50:34.980> its<00:50:35.100> own<00:50:35.160> side<00:50:35.430> chain<00:50:35.640> again<00:50:35.760> so 00:50:37.009 --> 00:50:37.019 align:start position:0% on its own side chain again so 00:50:37.019 --> 00:50:40.339 align:start position:0% on its own side chain again so but<00:50:37.919> for<00:50:38.249> now<00:50:38.399> I<00:50:38.880> think<00:50:39.419> where<00:50:39.869> we<00:50:39.989> are<00:50:40.140> at 00:50:40.339 --> 00:50:40.349 align:start position:0% but for now I think where we are at 00:50:40.349 --> 00:50:43.099 align:start position:0% but for now I think where we are at that's<00:50:41.039> that's<00:50:41.399> that's<00:50:41.819> the<00:50:41.909> best<00:50:42.089> you<00:50:42.899> have 00:50:43.099 --> 00:50:43.109 align:start position:0% that's that's that's the best you have 00:50:43.109 --> 00:50:47.659 align:start position:0% that's that's that's the best you have and<00:50:43.409> it's<00:50:43.979> gonna<00:50:44.099> get<00:50:44.279> us<00:50:44.429> there<00:50:45.199> 22.0<00:50:46.309> yeah<00:50:47.309> I 00:50:47.659 --> 00:50:47.669 align:start position:0% and it's gonna get us there 22.0 yeah I 00:50:47.669 --> 00:50:49.609 align:start position:0% and it's gonna get us there 22.0 yeah I kind<00:50:48.119> of<00:50:48.149> see<00:50:48.299> both<00:50:48.479> sides<00:50:48.630> of<00:50:48.869> it<00:50:48.929> like<00:50:49.140> for 00:50:49.609 --> 00:50:49.619 align:start position:0% kind of see both sides of it like for 00:50:49.619 --> 00:50:52.009 align:start position:0% kind of see both sides of it like for simplicity<00:50:50.159> doing<00:50:50.969> it<00:50:51.059> all<00:50:51.209> on<00:50:51.390> just<00:50:51.419> the<00:50:51.839> main 00:50:52.009 --> 00:50:52.019 align:start position:0% simplicity doing it all on just the main 00:50:52.019 --> 00:50:53.239 align:start position:0% simplicity doing it all on just the main aetherium<00:50:52.439> chain<00:50:52.649> it's<00:50:52.829> definitely<00:50:53.159> the 00:50:53.239 --> 00:50:53.249 align:start position:0% aetherium chain it's definitely the 00:50:53.249 --> 00:50:56.019 align:start position:0% aetherium chain it's definitely the easiest<00:50:53.579> way<00:50:53.819> to<00:50:54.049> keep<00:50:55.049> it<00:50:55.229> simple<00:50:55.380> and 00:50:56.019 --> 00:50:56.029 align:start position:0% easiest way to keep it simple and 00:50:56.029 --> 00:50:58.339 align:start position:0% easiest way to keep it simple and scalability<00:50:57.029> purposes<00:50:57.630> it's<00:50:57.839> definitely 00:50:58.339 --> 00:50:58.349 align:start position:0% scalability purposes it's definitely 00:50:58.349 --> 00:51:00.349 align:start position:0% scalability purposes it's definitely nicer<00:50:58.679> to<00:50:58.799> do<00:50:58.890> it<00:50:59.039> on<00:50:59.159> a<00:50:59.189> society<00:50:59.849> of<00:50:59.909> some<00:51:00.119> kind 00:51:00.349 --> 00:51:00.359 align:start position:0% nicer to do it on a society of some kind 00:51:00.359 --> 00:51:02.239 align:start position:0% nicer to do it on a society of some kind there's<00:51:00.689> I<00:51:00.959> think<00:51:01.649> some<00:51:01.829> kind<00:51:01.949> of<00:51:02.069> balance 00:51:02.239 --> 00:51:02.249 align:start position:0% there's I think some kind of balance 00:51:02.249 --> 00:51:06.019 align:start position:0% there's I think some kind of balance there<00:51:02.669> I<00:51:03.559> would<00:51:04.559> at<00:51:05.189> the<00:51:05.309> very<00:51:05.339> least<00:51:05.759> I<00:51:05.999> think 00:51:06.019 --> 00:51:06.029 align:start position:0% there I would at the very least I think 00:51:06.029 --> 00:51:09.679 align:start position:0% there I would at the very least I think anything<00:51:06.779> that<00:51:06.929> should<00:51:07.199> be<00:51:08.449> anything<00:51:09.449> that's 00:51:09.679 --> 00:51:09.689 align:start position:0% anything that should be anything that's 00:51:09.689 --> 00:51:12.649 align:start position:0% anything that should be anything that's considerably<00:51:10.229> expensive<00:51:11.189> I<00:51:11.579> mean<00:51:12.239> you<00:51:12.509> can 00:51:12.649 --> 00:51:12.659 align:start position:0% considerably expensive I mean you can 00:51:12.659 --> 00:51:14.929 align:start position:0% considerably expensive I mean you can like<00:51:13.169> crypto<00:51:13.589> katie's<00:51:13.890> anything<00:51:14.309> that<00:51:14.459> clogs 00:51:14.929 --> 00:51:14.939 align:start position:0% like crypto katie's anything that clogs 00:51:14.939 --> 00:51:16.699 align:start position:0% like crypto katie's anything that clogs the<00:51:15.119> network<00:51:15.419> or<00:51:15.659> is<00:51:15.749> sufficiently<00:51:16.140> expensive 00:51:16.699 --> 00:51:16.709 align:start position:0% the network or is sufficiently expensive 00:51:16.709 --> 00:51:18.499 align:start position:0% the network or is sufficiently expensive or<00:51:16.919> has<00:51:17.039> sufficient<00:51:17.459> network<00:51:17.759> should<00:51:18.059> be<00:51:18.239> in 00:51:18.499 --> 00:51:18.509 align:start position:0% or has sufficient network should be in 00:51:18.509 --> 00:51:21.469 align:start position:0% or has sufficient network should be in some<00:51:19.439> side<00:51:19.859> chain<00:51:20.159> or<00:51:20.369> shard<00:51:20.729> or<00:51:21.029> something 00:51:21.469 --> 00:51:21.479 align:start position:0% some side chain or shard or something 00:51:21.479 --> 00:51:25.120 align:start position:0% some side chain or shard or something off<00:51:21.630> the<00:51:21.809> main<00:51:21.959> chain<00:51:22.229> of<00:51:22.469> course<00:51:23.809> anything 00:51:25.120 --> 00:51:25.130 align:start position:0% off the main chain of course anything 00:51:25.130 --> 00:51:28.039 align:start position:0% off the main chain of course anything more<00:51:26.130> simplistic<00:51:26.669> that<00:51:27.179> maybe<00:51:27.630> either 00:51:28.039 --> 00:51:28.049 align:start position:0% more simplistic that maybe either 00:51:28.049 --> 00:51:30.769 align:start position:0% more simplistic that maybe either doesn't<00:51:28.289> have<00:51:28.439> traffic<00:51:28.679> or<00:51:29.189> like<00:51:29.579> I'm<00:51:30.119> not 00:51:30.769 --> 00:51:30.779 align:start position:0% doesn't have traffic or like I'm not 00:51:30.779 --> 00:51:32.089 align:start position:0% doesn't have traffic or like I'm not sure<00:51:30.809> if<00:51:31.049> it<00:51:31.140> makes<00:51:31.319> sense<00:51:31.409> for<00:51:31.649> like<00:51:31.919> new 00:51:32.089 --> 00:51:32.099 align:start position:0% sure if it makes sense for like new 00:51:32.099 --> 00:51:34.579 align:start position:0% sure if it makes sense for like new developers<00:51:32.640> coming<00:51:32.880> in<00:51:33.119> after<00:51:33.329> like<00:51:33.869> 2.0<00:51:34.319> jobs 00:51:34.579 --> 00:51:34.589 align:start position:0% developers coming in after like 2.0 jobs 00:51:34.589 --> 00:51:36.979 align:start position:0% developers coming in after like 2.0 jobs and<00:51:34.859> stuff<00:51:35.189> like<00:51:35.309> that<00:51:35.519> should<00:51:36.419> jump<00:51:36.779> right 00:51:36.979 --> 00:51:36.989 align:start position:0% and stuff like that should jump right 00:51:36.989 --> 00:51:38.389 align:start position:0% and stuff like that should jump right into<00:51:37.199> oh<00:51:37.409> yeah<00:51:37.559> we're<00:51:37.709> gonna<00:51:37.799> develop<00:51:38.249> our 00:51:38.389 --> 00:51:38.399 align:start position:0% into oh yeah we're gonna develop our 00:51:38.399 --> 00:51:40.549 align:start position:0% into oh yeah we're gonna develop our thing<00:51:38.909> right<00:51:39.359> into<00:51:39.539> a<00:51:39.659> sidechain<00:51:40.169> this<00:51:40.380> is<00:51:40.469> my 00:51:40.549 --> 00:51:40.559 align:start position:0% thing right into a sidechain this is my 00:51:40.559 --> 00:51:44.419 align:start position:0% thing right into a sidechain this is my first<00:51:40.769> my<00:51:41.249> first<00:51:41.279> app<00:51:41.729> is<00:51:41.969> on<00:51:42.259> plasma<00:51:43.259> and<00:51:43.469> it 00:51:44.419 --> 00:51:44.429 align:start position:0% first my first app is on plasma and it 00:51:44.429 --> 00:51:46.849 align:start position:0% first my first app is on plasma and it it<00:51:45.119> increases<00:51:45.839> the<00:51:46.139> barrier<00:51:46.409> to<00:51:46.529> entry<00:51:46.679> for 00:51:46.849 --> 00:51:46.859 align:start position:0% it increases the barrier to entry for 00:51:46.859 --> 00:51:48.229 align:start position:0% it increases the barrier to entry for aetherium<00:51:47.459> which<00:51:47.609> is<00:51:47.729> one<00:51:47.909> of<00:51:47.999> the<00:51:48.089> things 00:51:48.229 --> 00:51:48.239 align:start position:0% aetherium which is one of the things 00:51:48.239 --> 00:51:49.399 align:start position:0% aetherium which is one of the things that<00:51:48.359> makes<00:51:48.509> aetherium<00:51:48.869> so<00:51:49.019> great<00:51:49.229> in<00:51:49.319> my 00:51:49.399 --> 00:51:49.409 align:start position:0% that makes aetherium so great in my 00:51:49.409 --> 00:51:51.709 align:start position:0% that makes aetherium so great in my opinion<00:51:49.789> so<00:51:50.789> there's<00:51:51.209> a<00:51:51.269> balance<00:51:51.389> there 00:51:51.709 --> 00:51:51.719 align:start position:0% opinion so there's a balance there 00:51:51.719 --> 00:51:54.579 align:start position:0% opinion so there's a balance there depending<00:51:52.169> on<00:51:52.289> in<00:51:52.529> each<00:51:53.189> individual<00:51:53.669> app 00:51:54.579 --> 00:51:54.589 align:start position:0% depending on in each individual app 00:51:54.589 --> 00:51:58.399 align:start position:0% depending on in each individual app alright<00:51:56.329> so<00:51:57.329> I<00:51:57.359> think<00:51:57.449> you<00:51:57.689> your<00:51:58.049> moderator 00:51:58.399 --> 00:51:58.409 align:start position:0% alright so I think you your moderator 00:51:58.409 --> 00:51:59.509 align:start position:0% alright so I think you your moderator asked<00:51:58.589> a<00:51:58.619> great<00:51:58.799> question<00:51:58.859> earlier<00:51:59.399> about 00:51:59.509 --> 00:51:59.519 align:start position:0% asked a great question earlier about 00:51:59.519 --> 00:52:01.219 align:start position:0% asked a great question earlier about what<00:51:59.819> was<00:51:59.939> your<00:52:00.059> favorite<00:52:00.449> feature<00:52:00.659> of<00:52:00.959> a 00:52:01.219 --> 00:52:01.229 align:start position:0% what was your favorite feature of a 00:52:01.229 --> 00:52:03.199 align:start position:0% what was your favorite feature of a theorem<00:52:01.619> but<00:52:01.829> I'd<00:52:01.979> like<00:52:02.069> to<00:52:02.130> ask<00:52:02.489> the<00:52:02.759> opposite 00:52:03.199 --> 00:52:03.209 align:start position:0% theorem but I'd like to ask the opposite 00:52:03.209 --> 00:52:05.899 align:start position:0% theorem but I'd like to ask the opposite what<00:52:03.569> is<00:52:03.779> the<00:52:04.469> the<00:52:04.859> biggest<00:52:05.069> pain<00:52:05.399> point<00:52:05.729> that 00:52:05.899 --> 00:52:05.909 align:start position:0% what is the the biggest pain point that 00:52:05.909 --> 00:52:10.309 align:start position:0% what is the the biggest pain point that you<00:52:06.059> as<00:52:07.669> scaling<00:52:08.669> if<00:52:09.509> your<00:52:09.689> room<00:52:09.809> developers 00:52:10.309 --> 00:52:10.319 align:start position:0% you as scaling if your room developers 00:52:10.319 --> 00:52:11.809 align:start position:0% you as scaling if your room developers deal<00:52:10.529> with<00:52:10.679> I<00:52:10.829> know<00:52:10.889> that<00:52:11.159> Morgan<00:52:11.729> from 00:52:11.809 --> 00:52:11.819 align:start position:0% deal with I know that Morgan from 00:52:11.819 --> 00:52:13.729 align:start position:0% deal with I know that Morgan from shapeshift<00:52:12.269> you<00:52:12.359> mentioned<00:52:12.779> earlier<00:52:13.529> that 00:52:13.729 --> 00:52:13.739 align:start position:0% shapeshift you mentioned earlier that 00:52:13.739 --> 00:52:16.099 align:start position:0% shapeshift you mentioned earlier that dealing<00:52:14.699> with<00:52:14.729> the<00:52:15.119> lack<00:52:15.269> of<00:52:15.299> return<00:52:15.779> codes 00:52:16.099 --> 00:52:16.109 align:start position:0% dealing with the lack of return codes 00:52:16.109 --> 00:52:18.229 align:start position:0% dealing with the lack of return codes was<00:52:16.349> a<00:52:16.529> pain<00:52:16.919> point<00:52:17.130> is<00:52:17.399> that<00:52:17.699> the<00:52:17.999> biggest 00:52:18.229 --> 00:52:18.239 align:start position:0% was a pain point is that the biggest 00:52:18.239 --> 00:52:19.939 align:start position:0% was a pain point is that the biggest pain<00:52:18.509> point<00:52:18.809> what's<00:52:19.259> the<00:52:19.409> worst<00:52:19.589> part<00:52:19.859> about 00:52:19.939 --> 00:52:19.949 align:start position:0% pain point what's the worst part about 00:52:19.949 --> 00:52:23.870 align:start position:0% pain point what's the worst part about dealing<00:52:20.549> with<00:52:20.729> a<00:52:20.849> theorem<00:52:21.179> at<00:52:21.299> scale<00:52:21.569> oh<00:52:22.849> so<00:52:23.849> I 00:52:23.870 --> 00:52:23.880 align:start position:0% dealing with a theorem at scale oh so I 00:52:23.880 --> 00:52:25.459 align:start position:0% dealing with a theorem at scale oh so I think<00:52:23.999> there's<00:52:24.299> really<00:52:24.689> two<00:52:24.959> sides<00:52:25.199> of<00:52:25.319> that 00:52:25.459 --> 00:52:25.469 align:start position:0% think there's really two sides of that 00:52:25.469 --> 00:52:27.799 align:start position:0% think there's really two sides of that is<00:52:25.679> there's<00:52:26.189> the<00:52:26.639> solidity<00:52:27.329> side<00:52:27.630> in<00:52:27.749> the 00:52:27.799 --> 00:52:27.809 align:start position:0% is there's the solidity side in the 00:52:27.809 --> 00:52:30.139 align:start position:0% is there's the solidity side in the smart<00:52:28.049> contract<00:52:28.469> and<00:52:28.649> what's<00:52:28.799> a<00:52:29.039> pain<00:52:29.909> point 00:52:30.139 --> 00:52:30.149 align:start position:0% smart contract and what's a pain point 00:52:30.149 --> 00:52:31.999 align:start position:0% smart contract and what's a pain point of<00:52:30.329> dealing<00:52:30.599> with<00:52:30.719> those<00:52:30.989> and<00:52:31.469> that<00:52:31.709> that 00:52:31.999 --> 00:52:32.009 align:start position:0% of dealing with those and that that 00:52:32.009 --> 00:52:34.339 align:start position:0% of dealing with those and that that whole<00:52:32.249> ecosystem<00:52:33.059> and<00:52:33.599> then<00:52:33.719> the<00:52:34.019> server-side 00:52:34.339 --> 00:52:34.349 align:start position:0% whole ecosystem and then the server-side 00:52:34.349 --> 00:52:36.639 align:start position:0% whole ecosystem and then the server-side architectures<00:52:35.159> and<00:52:35.399> integrating<00:52:36.359> at 00:52:36.639 --> 00:52:36.649 align:start position:0% architectures and integrating at 00:52:36.649 --> 00:52:39.019 align:start position:0% architectures and integrating at addresses<00:52:37.649> or<00:52:37.949> do<00:52:38.369> we<00:52:38.489> choose<00:52:38.639> a<00:52:38.699> wall<00:52:38.909> in 00:52:39.019 --> 00:52:39.029 align:start position:0% addresses or do we choose a wall in 00:52:39.029 --> 00:52:42.499 align:start position:0% addresses or do we choose a wall in contract<00:52:40.159> personally<00:52:41.159> having<00:52:41.549> doing<00:52:41.880> both 00:52:42.499 --> 00:52:42.509 align:start position:0% contract personally having doing both 00:52:42.509 --> 00:52:45.259 align:start position:0% contract personally having doing both sides<00:52:42.799> yeah<00:52:43.829> era<00:52:44.130> codes<00:52:44.459> is<00:52:44.609> a<00:52:44.639> huge<00:52:45.029> pain 00:52:45.259 --> 00:52:45.269 align:start position:0% sides yeah era codes is a huge pain 00:52:45.269 --> 00:52:48.829 align:start position:0% sides yeah era codes is a huge pain point<00:52:45.329> for<00:52:45.779> me<00:52:45.899> it's<00:52:46.589> it's<00:52:46.859> a<00:52:47.299> huge<00:52:48.299> time<00:52:48.599> sink 00:52:48.829 --> 00:52:48.839 align:start position:0% point for me it's it's a huge time sink 00:52:48.839 --> 00:52:50.730 align:start position:0% point for me it's it's a huge time sink trying<00:52:49.229> to<00:52:49.409> debug<00:52:49.949> issues<00:52:50.429> there 00:52:50.730 --> 00:52:50.740 align:start position:0% trying to debug issues there 00:52:50.740 --> 00:52:53.550 align:start position:0% trying to debug issues there when<00:52:50.920> you<00:52:51.550> have<00:52:51.760> essentially<00:52:52.420> two<00:52:53.260> maybe 00:52:53.550 --> 00:52:53.560 align:start position:0% when you have essentially two maybe 00:52:53.560 --> 00:52:55.650 align:start position:0% when you have essentially two maybe three<00:52:53.950> error<00:52:54.310> codes<00:52:54.670> that<00:52:54.880> all<00:52:55.030> basically<00:52:55.510> say 00:52:55.650 --> 00:52:55.660 align:start position:0% three error codes that all basically say 00:52:55.660 --> 00:52:58.020 align:start position:0% three error codes that all basically say the<00:52:55.780> same<00:52:55.810> thing<00:52:56.200> it's<00:52:57.130> definitely<00:52:57.820> a<00:52:57.850> pain 00:52:58.020 --> 00:52:58.030 align:start position:0% the same thing it's definitely a pain 00:52:58.030 --> 00:53:00.359 align:start position:0% the same thing it's definitely a pain point<00:52:58.240> I<00:52:58.770> think<00:52:59.770> it's<00:53:00.040> the<00:53:00.130> internal 00:53:00.359 --> 00:53:00.369 align:start position:0% point I think it's the internal 00:53:00.369 --> 00:53:01.830 align:start position:0% point I think it's the internal transactions<00:53:00.880> challenge<00:53:01.300> where<00:53:01.630> other 00:53:01.830 --> 00:53:01.840 align:start position:0% transactions challenge where other 00:53:01.840 --> 00:53:04.380 align:start position:0% transactions challenge where other people<00:53:02.110> are<00:53:02.200> not<00:53:02.400> viewing<00:53:03.400> them<00:53:03.550> easily<00:53:03.880> for 00:53:04.380 --> 00:53:04.390 align:start position:0% people are not viewing them easily for 00:53:04.390 --> 00:53:06.750 align:start position:0% people are not viewing them easily for me<00:53:04.420> because<00:53:05.350> that<00:53:05.380> you<00:53:06.310> don't<00:53:06.490> have<00:53:06.610> much 00:53:06.750 --> 00:53:06.760 align:start position:0% me because that you don't have much 00:53:06.760 --> 00:53:09.960 align:start position:0% me because that you don't have much control<00:53:06.910> of<00:53:07.240> yourself<00:53:07.570> you<00:53:08.560> can<00:53:08.710> yeah<00:53:09.490> no 00:53:09.960 --> 00:53:09.970 align:start position:0% control of yourself you can yeah no 00:53:09.970 --> 00:53:11.130 align:start position:0% control of yourself you can yeah no matter<00:53:10.119> how<00:53:10.240> much<00:53:10.330> time<00:53:10.540> you<00:53:10.660> spend<00:53:10.900> yourself 00:53:11.130 --> 00:53:11.140 align:start position:0% matter how much time you spend yourself 00:53:11.140 --> 00:53:12.780 align:start position:0% matter how much time you spend yourself you<00:53:11.470> know<00:53:11.560> gonna<00:53:11.680> get<00:53:12.340> someone<00:53:12.610> else<00:53:12.730> to 00:53:12.780 --> 00:53:12.790 align:start position:0% you know gonna get someone else to 00:53:12.790 --> 00:53:15.480 align:start position:0% you know gonna get someone else to accept<00:53:13.150> a<00:53:13.240> transaction<00:53:13.660> or<00:53:13.690> is<00:53:13.810> diecuts<00:53:14.490> yeah 00:53:15.480 --> 00:53:15.490 align:start position:0% accept a transaction or is diecuts yeah 00:53:15.490 --> 00:53:17.820 align:start position:0% accept a transaction or is diecuts yeah I<00:53:15.520> think<00:53:15.790> there's<00:53:16.270> a<00:53:16.360> few<00:53:16.660> I<00:53:17.260> think<00:53:17.740> like 00:53:17.820 --> 00:53:17.830 align:start position:0% I think there's a few I think like 00:53:17.830 --> 00:53:19.560 align:start position:0% I think there's a few I think like that's<00:53:17.980> a<00:53:18.130> huge<00:53:18.369> one<00:53:18.610> that's<00:53:18.880> like<00:53:19.240> prevents 00:53:19.560 --> 00:53:19.570 align:start position:0% that's a huge one that's like prevents 00:53:19.570 --> 00:53:21.030 align:start position:0% that's a huge one that's like prevents people<00:53:19.690> from<00:53:19.840> sort<00:53:20.140> of<00:53:20.170> getting<00:53:20.530> on<00:53:20.619> board<00:53:20.800> and 00:53:21.030 --> 00:53:21.040 align:start position:0% people from sort of getting on board and 00:53:21.040 --> 00:53:21.960 align:start position:0% people from sort of getting on board and getting<00:53:21.280> there<00:53:21.460> I<00:53:21.490> think<00:53:21.730> there's<00:53:21.880> like 00:53:21.960 --> 00:53:21.970 align:start position:0% getting there I think there's like 00:53:21.970 --> 00:53:23.460 align:start position:0% getting there I think there's like there's<00:53:22.150> things<00:53:22.300> we<00:53:22.390> can<00:53:22.540> do<00:53:22.660> that<00:53:23.350> will<00:53:23.440> make 00:53:23.460 --> 00:53:23.470 align:start position:0% there's things we can do that will make 00:53:23.470 --> 00:53:24.720 align:start position:0% there's things we can do that will make that<00:53:23.770> make<00:53:24.010> that<00:53:24.130> easier<00:53:24.430> and<00:53:24.520> these<00:53:24.610> are 00:53:24.720 --> 00:53:24.730 align:start position:0% that make that easier and these are 00:53:24.730 --> 00:53:25.740 align:start position:0% that make that easier and these are things<00:53:24.880> that<00:53:24.940> like<00:53:25.119> eventually<00:53:25.300> once<00:53:25.570> you<00:53:25.630> get 00:53:25.740 --> 00:53:25.750 align:start position:0% things that like eventually once you get 00:53:25.750 --> 00:53:27.540 align:start position:0% things that like eventually once you get them<00:53:25.869> kind<00:53:25.960> of<00:53:26.050> working<00:53:26.350> correctly<00:53:26.530> well<00:53:27.010> they 00:53:27.540 --> 00:53:27.550 align:start position:0% them kind of working correctly well they 00:53:27.550 --> 00:53:29.160 align:start position:0% them kind of working correctly well they do<00:53:27.610> become<00:53:27.880> not<00:53:28.180> so<00:53:28.210> much<00:53:28.630> of<00:53:28.750> a<00:53:28.840> pain<00:53:28.990> point 00:53:29.160 --> 00:53:29.170 align:start position:0% do become not so much of a pain point 00:53:29.170 --> 00:53:30.930 align:start position:0% do become not so much of a pain point but<00:53:29.920> they're<00:53:30.040> hard<00:53:30.220> to<00:53:30.340> get<00:53:30.460> right<00:53:30.610> the<00:53:30.760> first 00:53:30.930 --> 00:53:30.940 align:start position:0% but they're hard to get right the first 00:53:30.940 --> 00:53:31.200 align:start position:0% but they're hard to get right the first time 00:53:31.200 --> 00:53:31.210 align:start position:0% time 00:53:31.210 --> 00:53:33.090 align:start position:0% time things<00:53:31.750> that<00:53:31.869> we<00:53:31.960> see<00:53:32.140> like<00:53:32.470> you<00:53:33.070> know 00:53:33.090 --> 00:53:33.100 align:start position:0% things that we see like you know 00:53:33.100 --> 00:53:35.370 align:start position:0% things that we see like you know regularly<00:53:33.730> well<00:53:34.240> I'm<00:53:34.720> gonna<00:53:34.840> say<00:53:35.050> two<00:53:35.110> things 00:53:35.370 --> 00:53:35.380 align:start position:0% regularly well I'm gonna say two things 00:53:35.380 --> 00:53:37.530 align:start position:0% regularly well I'm gonna say two things one<00:53:35.530> thing<00:53:35.680> we<00:53:35.800> see<00:53:35.950> regularly<00:53:36.300> not<00:53:37.300> much 00:53:37.530 --> 00:53:37.540 align:start position:0% one thing we see regularly not much 00:53:37.540 --> 00:53:38.700 align:start position:0% one thing we see regularly not much recently<00:53:37.750> it's<00:53:38.080> everything's<00:53:38.350> kind<00:53:38.500> of<00:53:38.530> died 00:53:38.700 --> 00:53:38.710 align:start position:0% recently it's everything's kind of died 00:53:38.710 --> 00:53:40.170 align:start position:0% recently it's everything's kind of died down<00:53:38.740> but<00:53:39.070> all<00:53:39.190> the<00:53:39.280> gas<00:53:39.460> price<00:53:39.730> stuff<00:53:39.970> like 00:53:40.170 --> 00:53:40.180 align:start position:0% down but all the gas price stuff like 00:53:40.180 --> 00:53:41.760 align:start position:0% down but all the gas price stuff like really<00:53:40.420> this<00:53:40.540> year<00:53:40.600> all<00:53:40.930> the<00:53:41.080> time<00:53:41.290> gas<00:53:41.590> prices 00:53:41.760 --> 00:53:41.770 align:start position:0% really this year all the time gas prices 00:53:41.770 --> 00:53:44.490 align:start position:0% really this year all the time gas prices spiking<00:53:42.369> things<00:53:42.610> get<00:53:42.850> stuck<00:53:43.119> and<00:53:43.330> and<00:53:44.320> that's 00:53:44.490 --> 00:53:44.500 align:start position:0% spiking things get stuck and and that's 00:53:44.500 --> 00:53:46.560 align:start position:0% spiking things get stuck and and that's a<00:53:44.619> pretty<00:53:44.830> big<00:53:44.980> pain<00:53:45.190> point<00:53:45.220> and<00:53:45.670> we<00:53:46.300> don't 00:53:46.560 --> 00:53:46.570 align:start position:0% a pretty big pain point and we don't 00:53:46.570 --> 00:53:48.690 align:start position:0% a pretty big pain point and we don't currently<00:53:46.780> have<00:53:46.930> systems<00:53:47.290> on<00:53:48.040> aetherium<00:53:48.400> that 00:53:48.690 --> 00:53:48.700 align:start position:0% currently have systems on aetherium that 00:53:48.700 --> 00:53:50.130 align:start position:0% currently have systems on aetherium that sort<00:53:48.970> of<00:53:49.030> automatically<00:53:49.390> recovers<00:53:49.810> that<00:53:49.990> and 00:53:50.130 --> 00:53:50.140 align:start position:0% sort of automatically recovers that and 00:53:50.140 --> 00:53:51.870 align:start position:0% sort of automatically recovers that and we<00:53:50.410> talked<00:53:50.650> a<00:53:50.860> lot<00:53:50.980> of<00:53:51.130> some<00:53:51.220> ideas<00:53:51.580> earlier 00:53:51.870 --> 00:53:51.880 align:start position:0% we talked a lot of some ideas earlier 00:53:51.880 --> 00:53:53.370 align:start position:0% we talked a lot of some ideas earlier that<00:53:52.030> could<00:53:52.150> help<00:53:52.240> with<00:53:52.330> that<00:53:52.450> um<00:53:52.960> the<00:53:53.290> other 00:53:53.370 --> 00:53:53.380 align:start position:0% that could help with that um the other 00:53:53.380 --> 00:53:55.859 align:start position:0% that could help with that um the other one<00:53:53.790> that's<00:53:54.790> more<00:53:54.910> of<00:53:55.030> a<00:53:55.090> rarity<00:53:55.390> but<00:53:55.480> also 00:53:55.859 --> 00:53:55.869 align:start position:0% one that's more of a rarity but also 00:53:55.869 --> 00:53:57.780 align:start position:0% one that's more of a rarity but also similarly<00:53:56.260> for<00:53:56.560> like<00:53:56.680> building<00:53:57.430> these<00:53:57.550> sort 00:53:57.780 --> 00:53:57.790 align:start position:0% similarly for like building these sort 00:53:57.790 --> 00:53:59.280 align:start position:0% similarly for like building these sort of<00:53:57.820> high-volume<00:53:58.210> systems<00:53:58.750> if<00:53:58.930> you<00:53:58.960> have<00:53:59.200> to 00:53:59.280 --> 00:53:59.290 align:start position:0% of high-volume systems if you have to 00:53:59.290 --> 00:54:00.780 align:start position:0% of high-volume systems if you have to start<00:53:59.470> tracking<00:53:59.680> these<00:54:00.010> nonces<00:54:00.490> and<00:54:00.640> stuff 00:54:00.780 --> 00:54:00.790 align:start position:0% start tracking these nonces and stuff 00:54:00.790 --> 00:54:02.400 align:start position:0% start tracking these nonces and stuff yourself<00:54:01.150> if<00:54:01.570> you<00:54:01.690> get<00:54:01.810> one<00:54:01.930> out<00:54:02.050> of<00:54:02.170> order 00:54:02.400 --> 00:54:02.410 align:start position:0% yourself if you get one out of order 00:54:02.410 --> 00:54:04.890 align:start position:0% yourself if you get one out of order you're<00:54:03.100> in<00:54:03.190> a<00:54:03.250> really<00:54:03.460> weird<00:54:03.730> spot<00:54:04.240> because<00:54:04.810> if 00:54:04.890 --> 00:54:04.900 align:start position:0% you're in a really weird spot because if 00:54:04.900 --> 00:54:06.030 align:start position:0% you're in a really weird spot because if you're<00:54:04.990> doing<00:54:05.080> like<00:54:05.230> multiple<00:54:05.619> sends<00:54:05.920> for 00:54:06.030 --> 00:54:06.040 align:start position:0% you're doing like multiple sends for 00:54:06.040 --> 00:54:07.950 align:start position:0% you're doing like multiple sends for customers<00:54:06.400> there<00:54:06.640> and<00:54:06.940> you<00:54:07.270> like<00:54:07.450> skip<00:54:07.750> one 00:54:07.950 --> 00:54:07.960 align:start position:0% customers there and you like skip one 00:54:07.960 --> 00:54:10.260 align:start position:0% customers there and you like skip one now<00:54:08.680> you<00:54:09.160> have<00:54:09.310> so<00:54:09.640> if<00:54:09.700> you<00:54:09.730> have<00:54:09.850> like<00:54:09.940> four 00:54:10.260 --> 00:54:10.270 align:start position:0% now you have so if you have like four 00:54:10.270 --> 00:54:12.630 align:start position:0% now you have so if you have like four five<00:54:10.600> six<00:54:10.900> and<00:54:11.050> you<00:54:11.680> don't<00:54:11.859> do<00:54:12.040> five<00:54:12.250> for<00:54:12.520> some 00:54:12.630 --> 00:54:12.640 align:start position:0% five six and you don't do five for some 00:54:12.640 --> 00:54:14.160 align:start position:0% five six and you don't do five for some reason<00:54:12.910> it'll<00:54:13.119> hold<00:54:13.300> you've<00:54:13.660> got<00:54:13.840> this<00:54:13.960> whole 00:54:14.160 --> 00:54:14.170 align:start position:0% reason it'll hold you've got this whole 00:54:14.170 --> 00:54:15.270 align:start position:0% reason it'll hold you've got this whole and<00:54:14.500> so<00:54:14.590> the<00:54:14.710> other<00:54:14.830> ones<00:54:14.950> just<00:54:14.980> gonna<00:54:15.190> be 00:54:15.270 --> 00:54:15.280 align:start position:0% and so the other ones just gonna be 00:54:15.280 --> 00:54:16.920 align:start position:0% and so the other ones just gonna be pending<00:54:15.640> forever<00:54:15.940> until<00:54:16.330> you<00:54:16.450> fill<00:54:16.660> that<00:54:16.750> in 00:54:16.920 --> 00:54:16.930 align:start position:0% pending forever until you fill that in 00:54:16.930 --> 00:54:19.200 align:start position:0% pending forever until you fill that in and<00:54:17.170> like<00:54:17.980> what<00:54:18.460> if<00:54:18.550> you<00:54:18.580> like<00:54:18.700> I<00:54:19.030> don't<00:54:19.090> know 00:54:19.200 --> 00:54:19.210 align:start position:0% and like what if you like I don't know 00:54:19.210 --> 00:54:20.490 align:start position:0% and like what if you like I don't know we<00:54:19.359> tried<00:54:19.600> something<00:54:19.780> else<00:54:19.960> and<00:54:20.200> then<00:54:20.320> you 00:54:20.490 --> 00:54:20.500 align:start position:0% we tried something else and then you 00:54:20.500 --> 00:54:21.960 align:start position:0% we tried something else and then you send<00:54:20.770> another<00:54:20.859> transaction<00:54:21.280> out<00:54:21.670> you<00:54:21.790> can't 00:54:21.960 --> 00:54:21.970 align:start position:0% send another transaction out you can't 00:54:21.970 --> 00:54:23.790 align:start position:0% send another transaction out you can't cancel<00:54:22.210> this<00:54:22.480> six<00:54:22.720> now<00:54:22.930> like<00:54:23.350> it's<00:54:23.470> out<00:54:23.590> there 00:54:23.790 --> 00:54:23.800 align:start position:0% cancel this six now like it's out there 00:54:23.800 --> 00:54:25.560 align:start position:0% cancel this six now like it's out there and<00:54:24.040> so<00:54:24.160> you<00:54:24.250> have<00:54:24.430> this<00:54:24.520> weird<00:54:24.790> like<00:54:24.910> like<00:54:25.450> we 00:54:25.560 --> 00:54:25.570 align:start position:0% and so you have this weird like like we 00:54:25.570 --> 00:54:26.580 align:start position:0% and so you have this weird like like we can't<00:54:25.750> introduce<00:54:26.080> like<00:54:26.200> canceling 00:54:26.580 --> 00:54:26.590 align:start position:0% can't introduce like canceling 00:54:26.590 --> 00:54:28.410 align:start position:0% can't introduce like canceling transactions<00:54:27.280> that<00:54:27.369> would<00:54:27.460> we<00:54:27.580> eat<00:54:27.700> like<00:54:27.850> not 00:54:28.410 --> 00:54:28.420 align:start position:0% transactions that would we eat like not 00:54:28.420 --> 00:54:31.109 align:start position:0% transactions that would we eat like not really<00:54:28.750> possible<00:54:28.930> but<00:54:29.380> that<00:54:30.160> sort<00:54:30.880> of<00:54:30.970> thing 00:54:31.109 --> 00:54:31.119 align:start position:0% really possible but that sort of thing 00:54:31.119 --> 00:54:32.490 align:start position:0% really possible but that sort of thing in<00:54:31.210> like<00:54:31.330> calculating<00:54:31.810> these<00:54:31.869> nonces<00:54:32.290> like 00:54:32.490 --> 00:54:32.500 align:start position:0% in like calculating these nonces like 00:54:32.500 --> 00:54:34.470 align:start position:0% in like calculating these nonces like you<00:54:33.250> can't<00:54:33.520> because<00:54:33.850> you're<00:54:33.940> not<00:54:34.030> just<00:54:34.180> using 00:54:34.470 --> 00:54:34.480 align:start position:0% you can't because you're not just using 00:54:34.480 --> 00:54:36.570 align:start position:0% you can't because you're not just using a<00:54:34.540> single<00:54:34.750> node<00:54:35.080> you<00:54:35.770> have<00:54:35.980> to<00:54:36.130> sort<00:54:36.280> of<00:54:36.369> track 00:54:36.570 --> 00:54:36.580 align:start position:0% a single node you have to sort of track 00:54:36.580 --> 00:54:37.740 align:start position:0% a single node you have to sort of track that<00:54:36.790> yourself<00:54:37.119> and<00:54:37.300> make<00:54:37.450> the<00:54:37.480> right 00:54:37.740 --> 00:54:37.750 align:start position:0% that yourself and make the right 00:54:37.750 --> 00:54:40.920 align:start position:0% that yourself and make the right decision<00:54:38.170> there<00:54:38.350> and<00:54:38.590> so<00:54:39.750> that's<00:54:40.750> a<00:54:40.900> challenge 00:54:40.920 --> 00:54:40.930 align:start position:0% decision there and so that's a challenge 00:54:40.930 --> 00:54:43.080 align:start position:0% decision there and so that's a challenge to<00:54:41.530> like<00:54:41.680> do<00:54:41.859> right<00:54:42.130> and<00:54:42.369> then<00:54:42.550> when<00:54:42.790> you<00:54:42.910> get 00:54:43.080 --> 00:54:43.090 align:start position:0% to like do right and then when you get 00:54:43.090 --> 00:54:45.690 align:start position:0% to like do right and then when you get it<00:54:43.240> wrong<00:54:44.100> specifically<00:54:45.100> going<00:54:45.280> too<00:54:45.460> high 00:54:45.690 --> 00:54:45.700 align:start position:0% it wrong specifically going too high 00:54:45.700 --> 00:54:47.430 align:start position:0% it wrong specifically going too high going<00:54:46.000> too<00:54:46.180> low<00:54:46.390> the<00:54:46.600> node<00:54:46.750> will<00:54:46.900> reject 00:54:47.430 --> 00:54:47.440 align:start position:0% going too low the node will reject 00:54:47.440 --> 00:54:49.680 align:start position:0% going too low the node will reject usually<00:54:47.890> it's<00:54:48.670> just<00:54:48.730> like<00:54:49.359> you<00:54:49.450> know<00:54:49.570> it's 00:54:49.680 --> 00:54:49.690 align:start position:0% usually it's just like you know it's 00:54:49.690 --> 00:54:52.800 align:start position:0% usually it's just like you know it's sink<00:54:49.840> that<00:54:50.020> but<00:54:51.000> going<00:54:52.000> too<00:54:52.119> high<00:54:52.330> creates 00:54:52.800 --> 00:54:52.810 align:start position:0% sink that but going too high creates 00:54:52.810 --> 00:54:53.880 align:start position:0% sink that but going too high creates this<00:54:52.900> thing<00:54:53.109> where<00:54:53.230> it's<00:54:53.320> like<00:54:53.440> oh<00:54:53.530> yeah<00:54:53.710> now 00:54:53.880 --> 00:54:53.890 align:start position:0% this thing where it's like oh yeah now 00:54:53.890 --> 00:54:55.230 align:start position:0% this thing where it's like oh yeah now what<00:54:54.160> and<00:54:54.430> you<00:54:54.640> don't<00:54:54.730> know<00:54:54.850> how<00:54:54.940> long<00:54:55.090> it's 00:54:55.230 --> 00:54:55.240 align:start position:0% what and you don't know how long it's 00:54:55.240 --> 00:54:57.359 align:start position:0% what and you don't know how long it's gonna<00:54:55.359> last<00:54:55.450> it's<00:54:55.930> in<00:54:56.050> the<00:54:56.109> nymphal<00:54:56.530> the<00:54:57.250> other 00:54:57.359 --> 00:54:57.369 align:start position:0% gonna last it's in the nymphal the other 00:54:57.369 --> 00:54:59.220 align:start position:0% gonna last it's in the nymphal the other thing<00:54:57.580> once<00:54:57.760> where<00:54:57.970> you<00:54:58.180> know<00:54:58.270> we<00:54:58.869> filled<00:54:59.109> in 00:54:59.220 --> 00:54:59.230 align:start position:0% thing once where you know we filled in 00:54:59.230 --> 00:55:00.510 align:start position:0% thing once where you know we filled in the<00:54:59.290> gap<00:54:59.470> in<00:54:59.650> it<00:54:59.740> went<00:54:59.920> out<00:54:59.980> we<00:55:00.100> didn't<00:55:00.280> expect 00:55:00.510 --> 00:55:00.520 align:start position:0% the gap in it went out we didn't expect 00:55:00.520 --> 00:55:03.120 align:start position:0% the gap in it went out we didn't expect it<00:55:00.670> to<00:55:00.820> and<00:55:01.060> it's<00:55:01.600> like<00:55:01.660> oh<00:55:01.840> well 00:55:03.120 --> 00:55:03.130 align:start position:0% it to and it's like oh well 00:55:03.130 --> 00:55:07.290 align:start position:0% it to and it's like oh well it<00:55:03.790> was<00:55:03.970> okay<00:55:04.210> but<00:55:04.710> not<00:55:05.710> that<00:55:05.980> a<00:55:06.010> fun<00:55:06.250> thing<00:55:06.400> all 00:55:07.290 --> 00:55:07.300 align:start position:0% it was okay but not that a fun thing all 00:55:07.300 --> 00:55:10.260 align:start position:0% it was okay but not that a fun thing all right<00:55:07.480> any<00:55:07.720> other<00:55:07.810> questions<00:55:07.990> out<00:55:08.890> here<00:55:09.270> all 00:55:10.260 --> 00:55:10.270 align:start position:0% right any other questions out here all 00:55:10.270 --> 00:55:11.400 align:start position:0% right any other questions out here all right<00:55:10.390> we<00:55:10.480> got<00:55:10.600> one<00:55:10.630> way<00:55:10.900> at<00:55:11.020> the<00:55:11.080> back<00:55:11.170> gonna 00:55:11.400 --> 00:55:11.410 align:start position:0% right we got one way at the back gonna 00:55:11.410 --> 00:55:20.870 align:start position:0% right we got one way at the back gonna run<00:55:11.620> I<00:55:14.250> know 00:55:20.870 --> 00:55:20.880 align:start position:0% 00:55:20.880 --> 00:55:24.390 align:start position:0% so<00:55:21.880> a<00:55:21.910> better<00:55:22.210> standardization<00:55:23.110> for<00:55:23.400> like 00:55:24.390 --> 00:55:24.400 align:start position:0% so a better standardization for like 00:55:24.400 --> 00:55:27.330 align:start position:0% so a better standardization for like your<00:55:24.550> server<00:55:24.820> architecture<00:55:24.970> or<00:55:25.720> or<00:55:26.470> smart 00:55:27.330 --> 00:55:27.340 align:start position:0% your server architecture or or smart 00:55:27.340 --> 00:55:30.210 align:start position:0% your server architecture or or smart contracts<00:55:27.730> themselves<00:55:27.910> air<00:55:28.420> close<00:55:29.160> where<00:55:30.160> do 00:55:30.210 --> 00:55:30.220 align:start position:0% contracts themselves air close where do 00:55:30.220 --> 00:55:32.100 align:start position:0% contracts themselves air close where do you<00:55:30.310> guys<00:55:30.430> feel<00:55:30.670> the<00:55:30.940> governance<00:55:31.450> process<00:55:31.900> is 00:55:32.100 --> 00:55:32.110 align:start position:0% you guys feel the governance process is 00:55:32.110 --> 00:55:34.470 align:start position:0% you guys feel the governance process is for<00:55:32.770> that<00:55:32.980> are<00:55:33.220> you<00:55:33.310> guys<00:55:33.400> talking<00:55:33.940> one-to-one 00:55:34.470 --> 00:55:34.480 align:start position:0% for that are you guys talking one-to-one 00:55:34.480 --> 00:55:38.060 align:start position:0% for that are you guys talking one-to-one to<00:55:34.600> each<00:55:34.720> other<00:55:34.990> or<00:55:35.440> is<00:55:35.650> that<00:55:35.830> on<00:55:36.070> the<00:55:36.610> IPS<00:55:37.210> or 00:55:38.060 --> 00:55:38.070 align:start position:0% to each other or is that on the IPS or 00:55:38.070 --> 00:55:40.410 align:start position:0% to each other or is that on the IPS or it's<00:55:39.070> kind<00:55:39.250> of<00:55:39.340> like<00:55:39.460> how<00:55:39.610> do<00:55:39.670> you<00:55:39.850> have<00:55:40.180> those 00:55:40.410 --> 00:55:40.420 align:start position:0% it's kind of like how do you have those 00:55:40.420 --> 00:55:42.960 align:start position:0% it's kind of like how do you have those conversations<00:55:41.190> together<00:55:42.190> in<00:55:42.400> the<00:55:42.520> industry 00:55:42.960 --> 00:55:42.970 align:start position:0% conversations together in the industry 00:55:42.970 --> 00:55:44.990 align:start position:0% conversations together in the industry to<00:55:43.180> get<00:55:43.690> stuff<00:55:44.020> done 00:55:44.990 --> 00:55:45.000 align:start position:0% to get stuff done 00:55:45.000 --> 00:55:47.820 align:start position:0% to get stuff done yeah<00:55:46.000> I'll<00:55:46.630> see<00:55:46.840> your<00:55:46.930> question<00:55:47.230> one<00:55:47.680> thing 00:55:47.820 --> 00:55:47.830 align:start position:0% yeah I'll see your question one thing 00:55:47.830 --> 00:55:49.260 align:start position:0% yeah I'll see your question one thing real<00:55:48.010> quick<00:55:48.190> on<00:55:48.280> that<00:55:48.340> like<00:55:48.610> this<00:55:48.790> that's<00:55:49.180> one 00:55:49.260 --> 00:55:49.270 align:start position:0% real quick on that like this that's one 00:55:49.270 --> 00:55:50.370 align:start position:0% real quick on that like this that's one of<00:55:49.360> the<00:55:49.420> reasons<00:55:49.660> why<00:55:49.840> we<00:55:49.990> wanted<00:55:50.170> to<00:55:50.260> put 00:55:50.370 --> 00:55:50.380 align:start position:0% of the reasons why we wanted to put 00:55:50.380 --> 00:55:52.650 align:start position:0% of the reasons why we wanted to put together<00:55:50.470> this<00:55:50.710> panel<00:55:50.920> is<00:55:51.910> to<00:55:52.180> get<00:55:52.360> people 00:55:52.650 --> 00:55:52.660 align:start position:0% together this panel is to get people 00:55:52.660 --> 00:55:54.060 align:start position:0% together this panel is to get people talking<00:55:52.810> and<00:55:53.050> people<00:55:53.290> talking<00:55:53.530> in<00:55:53.590> public<00:55:53.710> I 00:55:54.060 --> 00:55:54.070 align:start position:0% talking and people talking in public I 00:55:54.070 --> 00:55:55.890 align:start position:0% talking and people talking in public I think<00:55:54.130> there's<00:55:54.460> a<00:55:54.520> lot<00:55:54.820> of<00:55:54.910> sort<00:55:55.150> of<00:55:55.210> secrecy<00:55:55.750> a 00:55:55.890 --> 00:55:55.900 align:start position:0% think there's a lot of sort of secrecy a 00:55:55.900 --> 00:55:57.540 align:start position:0% think there's a lot of sort of secrecy a lot<00:55:56.260> of<00:55:56.350> things<00:55:56.470> are<00:55:56.590> shrouded<00:55:57.040> and<00:55:57.280> they 00:55:57.540 --> 00:55:57.550 align:start position:0% lot of things are shrouded and they 00:55:57.550 --> 00:55:58.920 align:start position:0% lot of things are shrouded and they shouldn't<00:55:57.910> be<00:55:58.000> and<00:55:58.150> there's<00:55:58.270> no<00:55:58.390> real<00:55:58.540> reason 00:55:58.920 --> 00:55:58.930 align:start position:0% shouldn't be and there's no real reason 00:55:58.930 --> 00:56:00.990 align:start position:0% shouldn't be and there's no real reason for<00:55:58.960> them<00:55:59.260> to<00:55:59.290> be<00:55:59.580> but<00:56:00.580> I<00:56:00.610> think<00:56:00.790> we<00:56:00.880> all 00:56:00.990 --> 00:56:01.000 align:start position:0% for them to be but I think we all 00:56:01.000 --> 00:56:02.610 align:start position:0% for them to be but I think we all approach<00:56:01.600> things<00:56:01.840> different<00:56:02.110> ways<00:56:02.140> like<00:56:02.500> if 00:56:02.610 --> 00:56:02.620 align:start position:0% approach things different ways like if 00:56:02.620 --> 00:56:03.960 align:start position:0% approach things different ways like if we<00:56:02.740> were<00:56:02.830> to<00:56:02.890> talk<00:56:03.070> about<00:56:03.220> how<00:56:03.430> we<00:56:03.490> all<00:56:03.700> run<00:56:03.850> our 00:56:03.960 --> 00:56:03.970 align:start position:0% we were to talk about how we all run our 00:56:03.970 --> 00:56:05.400 align:start position:0% we were to talk about how we all run our nose<00:56:04.120> or<00:56:04.330> how<00:56:04.420> we<00:56:04.480> all<00:56:04.660> did<00:56:04.840> not<00:56:04.990> stuff<00:56:05.290> I 00:56:05.400 --> 00:56:05.410 align:start position:0% nose or how we all did not stuff I 00:56:05.410 --> 00:56:06.810 align:start position:0% nose or how we all did not stuff I imagine<00:56:06.040> we'd<00:56:06.190> all<00:56:06.310> sort<00:56:06.610> of<00:56:06.640> do<00:56:06.790> it 00:56:06.810 --> 00:56:06.820 align:start position:0% imagine we'd all sort of do it 00:56:06.820 --> 00:56:08.310 align:start position:0% imagine we'd all sort of do it differently<00:56:07.270> and<00:56:07.600> there's<00:56:07.960> things<00:56:08.080> to<00:56:08.170> learn 00:56:08.310 --> 00:56:08.320 align:start position:0% differently and there's things to learn 00:56:08.320 --> 00:56:09.510 align:start position:0% differently and there's things to learn from<00:56:08.410> each<00:56:08.590> other<00:56:08.740> there<00:56:08.950> like<00:56:09.160> we've<00:56:09.370> already 00:56:09.510 --> 00:56:09.520 align:start position:0% from each other there like we've already 00:56:09.520 --> 00:56:10.620 align:start position:0% from each other there like we've already learned<00:56:09.760> things<00:56:10.000> talking<00:56:10.210> about<00:56:10.480> you<00:56:10.540> know 00:56:10.620 --> 00:56:10.630 align:start position:0% learned things talking about you know 00:56:10.630 --> 00:56:11.850 align:start position:0% learned things talking about you know the<00:56:10.720> contracts<00:56:11.140> like<00:56:11.290> sprint<00:56:11.530> trade-offs 00:56:11.850 --> 00:56:11.860 align:start position:0% the contracts like sprint trade-offs 00:56:11.860 --> 00:56:12.930 align:start position:0% the contracts like sprint trade-offs there<00:56:11.920> and<00:56:12.130> the<00:56:12.190> way<00:56:12.280> they<00:56:12.430> do<00:56:12.490> things<00:56:12.760> in<00:56:12.820> the 00:56:12.930 --> 00:56:12.940 align:start position:0% there and the way they do things in the 00:56:12.940 --> 00:56:15.540 align:start position:0% there and the way they do things in the way<00:56:13.060> we<00:56:13.240> do<00:56:13.360> things<00:56:13.540> and<00:56:13.810> I<00:56:14.560> think<00:56:14.770> the<00:56:15.070> big 00:56:15.540 --> 00:56:15.550 align:start position:0% way we do things and I think the big 00:56:15.550 --> 00:56:16.590 align:start position:0% way we do things and I think the big thing<00:56:15.700> is<00:56:15.880> yeah<00:56:16.030> at<00:56:16.210> least<00:56:16.330> get<00:56:16.570> people 00:56:16.590 --> 00:56:16.600 align:start position:0% thing is yeah at least get people 00:56:16.600 --> 00:56:18.870 align:start position:0% thing is yeah at least get people talking<00:56:17.020> I<00:56:17.470> don't<00:56:18.250> necessarily<00:56:18.430> have<00:56:18.760> in<00:56:18.820> a 00:56:18.870 --> 00:56:18.880 align:start position:0% talking I don't necessarily have in a 00:56:18.880 --> 00:56:20.940 align:start position:0% talking I don't necessarily have in a year<00:56:19.060> I<00:56:19.090> think<00:56:19.150> the<00:56:19.390> best<00:56:19.620> place<00:56:20.620> to<00:56:20.650> do<00:56:20.920> that 00:56:20.940 --> 00:56:20.950 align:start position:0% year I think the best place to do that 00:56:20.950 --> 00:56:22.020 align:start position:0% year I think the best place to do that there's<00:56:21.280> definitely<00:56:21.400> you<00:56:21.670> know<00:56:21.730> something 00:56:22.020 --> 00:56:22.030 align:start position:0% there's definitely you know something 00:56:22.030 --> 00:56:23.310 align:start position:0% there's definitely you know something you<00:56:22.090> know<00:56:22.210> just<00:56:22.240> every<00:56:22.960> now<00:56:23.050> and<00:56:23.170> then<00:56:23.230> you 00:56:23.310 --> 00:56:23.320 align:start position:0% you know just every now and then you 00:56:23.320 --> 00:56:24.870 align:start position:0% you know just every now and then you talk<00:56:23.500> with<00:56:23.650> somebody<00:56:23.950> or<00:56:24.040> every<00:56:24.250> child<00:56:24.520> but<00:56:24.730> I 00:56:24.870 --> 00:56:24.880 align:start position:0% talk with somebody or every child but I 00:56:24.880 --> 00:56:26.070 align:start position:0% talk with somebody or every child but I did<00:56:25.030> think<00:56:25.090> it'd<00:56:25.210> be<00:56:25.300> really<00:56:25.450> cool<00:56:25.780> to<00:56:25.840> see 00:56:26.070 --> 00:56:26.080 align:start position:0% did think it'd be really cool to see 00:56:26.080 --> 00:56:29.100 align:start position:0% did think it'd be really cool to see more<00:56:26.670> sort<00:56:27.670> of<00:56:27.730> open<00:56:28.000> spaces<00:56:28.270> to<00:56:28.630> discuss<00:56:28.960> this 00:56:29.100 --> 00:56:29.110 align:start position:0% more sort of open spaces to discuss this 00:56:29.110 --> 00:56:31.460 align:start position:0% more sort of open spaces to discuss this things<00:56:29.290> especially<00:56:29.590> with<00:56:29.920> sort<00:56:30.130> of<00:56:30.190> you<00:56:30.340> know 00:56:31.460 --> 00:56:31.470 align:start position:0% things especially with sort of you know 00:56:31.470 --> 00:56:33.750 align:start position:0% things especially with sort of you know like<00:56:32.470> big<00:56:32.770> participants<00:56:33.310> of<00:56:33.430> the<00:56:33.490> network 00:56:33.750 --> 00:56:33.760 align:start position:0% like big participants of the network 00:56:33.760 --> 00:56:35.280 align:start position:0% like big participants of the network being<00:56:34.270> able<00:56:34.450> to<00:56:34.570> contribute<00:56:35.110> to<00:56:35.200> those 00:56:35.280 --> 00:56:35.290 align:start position:0% being able to contribute to those 00:56:35.290 --> 00:56:43.170 align:start position:0% being able to contribute to those conversations<00:56:41.190> maybe<00:56:42.190> I<00:56:42.340> think<00:56:42.730> it<00:56:42.910> would 00:56:43.170 --> 00:56:43.180 align:start position:0% conversations maybe I think it would 00:56:43.180 --> 00:56:44.250 align:start position:0% conversations maybe I think it would depend<00:56:43.330> on<00:56:43.450> the<00:56:43.540> company<00:56:43.870> because<00:56:44.140> I<00:56:44.170> think 00:56:44.250 --> 00:56:44.260 align:start position:0% depend on the company because I think 00:56:44.260 --> 00:56:45.870 align:start position:0% depend on the company because I think also<00:56:44.530> companies<00:56:44.920> like<00:56:45.160> to<00:56:45.340> do<00:56:45.430> a<00:56:45.460> lot<00:56:45.670> of<00:56:45.700> sort 00:56:45.870 --> 00:56:45.880 align:start position:0% also companies like to do a lot of sort 00:56:45.880 --> 00:56:47.400 align:start position:0% also companies like to do a lot of sort of<00:56:45.970> protecting<00:56:46.420> of<00:56:46.540> their<00:56:46.870> information<00:56:47.110> too 00:56:47.400 --> 00:56:47.410 align:start position:0% of protecting of their information too 00:56:47.410 --> 00:56:49.940 align:start position:0% of protecting of their information too and<00:56:47.560> that<00:56:47.680> becomes<00:56:48.040> sort<00:56:48.190> of<00:56:48.310> challenging<00:56:48.870> but 00:56:49.940 --> 00:56:49.950 align:start position:0% and that becomes sort of challenging but 00:56:49.950 --> 00:56:52.680 align:start position:0% and that becomes sort of challenging but it's<00:56:50.950> really<00:56:51.250> it's<00:56:51.550> like<00:56:51.610> all<00:56:51.880> open 00:56:52.680 --> 00:56:52.690 align:start position:0% it's really it's like all open 00:56:52.690 --> 00:56:56.250 align:start position:0% it's really it's like all open conversation<00:56:53.320> and<00:56:53.530> it<00:56:54.070> is<00:56:54.280> kind<00:56:54.550> of<00:56:55.260> segmented 00:56:56.250 --> 00:56:56.260 align:start position:0% conversation and it is kind of segmented 00:56:56.260 --> 00:56:57.930 align:start position:0% conversation and it is kind of segmented that<00:56:56.440> conversation<00:56:57.340> right<00:56:57.430> now<00:56:57.610> whether<00:56:57.820> it's 00:56:57.930 --> 00:56:57.940 align:start position:0% that conversation right now whether it's 00:56:57.940 --> 00:57:00.780 align:start position:0% that conversation right now whether it's get<00:56:58.690> or<00:56:58.810> stack<00:56:59.170> exchange<00:56:59.380> or<00:56:59.860> conferences<00:57:00.430> or 00:57:00.780 --> 00:57:00.790 align:start position:0% get or stack exchange or conferences or 00:57:00.790 --> 00:57:03.060 align:start position:0% get or stack exchange or conferences or github<00:57:01.330> issues<00:57:01.690> there's<00:57:01.930> tons<00:57:02.620> of<00:57:02.710> places 00:57:03.060 --> 00:57:03.070 align:start position:0% github issues there's tons of places 00:57:03.070 --> 00:57:04.650 align:start position:0% github issues there's tons of places where<00:57:03.280> a<00:57:03.310> lot<00:57:03.490> of<00:57:03.670> the<00:57:03.790> same<00:57:04.000> conversations 00:57:04.650 --> 00:57:04.660 align:start position:0% where a lot of the same conversations 00:57:04.660 --> 00:57:06.000 align:start position:0% where a lot of the same conversations are<00:57:04.750> happening<00:57:04.900> so<00:57:05.350> I<00:57:05.380> don't<00:57:05.620> really<00:57:05.860> know<00:57:05.980> of 00:57:06.000 --> 00:57:06.010 align:start position:0% are happening so I don't really know of 00:57:06.010 --> 00:57:08.370 align:start position:0% are happening so I don't really know of any<00:57:06.220> centralized<00:57:06.730> place<00:57:06.970> where<00:57:07.300> this<00:57:07.960> is<00:57:08.200> all 00:57:08.370 --> 00:57:08.380 align:start position:0% any centralized place where this is all 00:57:08.380 --> 00:57:11.370 align:start position:0% any centralized place where this is all happening<00:57:08.680> as<00:57:09.100> of<00:57:09.460> right<00:57:09.610> now<00:57:09.870> but<00:57:10.870> it<00:57:10.960> is<00:57:11.110> all 00:57:11.370 --> 00:57:11.380 align:start position:0% happening as of right now but it is all 00:57:11.380 --> 00:57:13.860 align:start position:0% happening as of right now but it is all about<00:57:11.590> really<00:57:11.860> conversation<00:57:12.550> and<00:57:12.870> seeing 00:57:13.860 --> 00:57:13.870 align:start position:0% about really conversation and seeing 00:57:13.870 --> 00:57:15.000 align:start position:0% about really conversation and seeing what<00:57:14.020> other<00:57:14.140> people<00:57:14.410> are<00:57:14.470> doing<00:57:14.710> this<00:57:14.830> is<00:57:14.980> a 00:57:15.000 --> 00:57:15.010 align:start position:0% what other people are doing this is a 00:57:15.010 --> 00:57:16.380 align:start position:0% what other people are doing this is a very<00:57:15.280> new<00:57:15.760> space 00:57:16.380 --> 00:57:16.390 align:start position:0% very new space 00:57:16.390 --> 00:57:17.730 align:start position:0% very new space we're<00:57:16.539> all<00:57:16.630> kind<00:57:16.809> of<00:57:16.930> just<00:57:17.140> figuring<00:57:17.349> it<00:57:17.650> out 00:57:17.730 --> 00:57:17.740 align:start position:0% we're all kind of just figuring it out 00:57:17.740 --> 00:57:19.650 align:start position:0% we're all kind of just figuring it out and<00:57:17.920> a<00:57:17.950> lot<00:57:18.069> of<00:57:18.099> things<00:57:18.309> you<00:57:18.460> almost<00:57:19.210> have<00:57:19.450> to 00:57:19.650 --> 00:57:19.660 align:start position:0% and a lot of things you almost have to 00:57:19.660 --> 00:57:21.120 align:start position:0% and a lot of things you almost have to learn<00:57:19.809> from<00:57:20.079> either<00:57:20.289> experience<00:57:20.980> or 00:57:21.120 --> 00:57:21.130 align:start position:0% learn from either experience or 00:57:21.130 --> 00:57:22.859 align:start position:0% learn from either experience or listening<00:57:21.460> to<00:57:21.579> somebody<00:57:21.730> that<00:57:21.970> did<00:57:22.299> get<00:57:22.750> the 00:57:22.859 --> 00:57:22.869 align:start position:0% listening to somebody that did get the 00:57:22.869 --> 00:57:23.849 align:start position:0% listening to somebody that did get the experience<00:57:23.319> and<00:57:23.440> make<00:57:23.559> those<00:57:23.650> mistakes 00:57:23.849 --> 00:57:23.859 align:start position:0% experience and make those mistakes 00:57:23.859 --> 00:57:26.849 align:start position:0% experience and make those mistakes already<00:57:24.450> do<00:57:25.450> you<00:57:25.510> think<00:57:25.690> think<00:57:25.869> interesting 00:57:26.849 --> 00:57:26.859 align:start position:0% already do you think think interesting 00:57:26.859 --> 00:57:27.809 align:start position:0% already do you think think interesting because<00:57:27.010> it<00:57:27.130> is<00:57:27.250> the<00:57:27.400> thing<00:57:27.549> like<00:57:27.700> I<00:57:27.760> don't 00:57:27.809 --> 00:57:27.819 align:start position:0% because it is the thing like I don't 00:57:27.819 --> 00:57:31.319 align:start position:0% because it is the thing like I don't think<00:57:28.119> how<00:57:29.309> people<00:57:30.309> talk<00:57:30.609> about<00:57:30.760> enough<00:57:31.059> is 00:57:31.319 --> 00:57:31.329 align:start position:0% think how people talk about enough is 00:57:31.329 --> 00:57:32.849 align:start position:0% think how people talk about enough is sort<00:57:31.569> of<00:57:31.599> the<00:57:31.779> the<00:57:31.990> types<00:57:32.200> of<00:57:32.380> problems<00:57:32.740> we 00:57:32.849 --> 00:57:32.859 align:start position:0% sort of the the types of problems we 00:57:32.859 --> 00:57:34.349 align:start position:0% sort of the the types of problems we were<00:57:33.069> talking<00:57:33.309> about<00:57:33.339> today<00:57:33.549> I<00:57:33.700> think<00:57:33.970> a<00:57:34.210> lot 00:57:34.349 --> 00:57:34.359 align:start position:0% were talking about today I think a lot 00:57:34.359 --> 00:57:35.940 align:start position:0% were talking about today I think a lot of<00:57:34.480> the<00:57:34.630> people<00:57:35.049> working<00:57:35.289> on<00:57:35.410> their<00:57:35.529> protocols 00:57:35.940 --> 00:57:35.950 align:start position:0% of the people working on their protocols 00:57:35.950 --> 00:57:38.279 align:start position:0% of the people working on their protocols and<00:57:36.130> stuff<00:57:36.279> tend<00:57:36.609> to<00:57:36.670> be<00:57:36.789> very<00:57:37.049> low-level<00:57:38.049> and 00:57:38.279 --> 00:57:38.289 align:start position:0% and stuff tend to be very low-level and 00:57:38.289 --> 00:57:39.390 align:start position:0% and stuff tend to be very low-level and close<00:57:38.440> to<00:57:38.559> there<00:57:38.710> and<00:57:38.859> have<00:57:38.980> you<00:57:39.279> know 00:57:39.390 --> 00:57:39.400 align:start position:0% close to there and have you know 00:57:39.400 --> 00:57:40.829 align:start position:0% close to there and have you know specific<00:57:40.029> ideas<00:57:40.299> around<00:57:40.420> how<00:57:40.510> people<00:57:40.750> are 00:57:40.829 --> 00:57:40.839 align:start position:0% specific ideas around how people are 00:57:40.839 --> 00:57:43.319 align:start position:0% specific ideas around how people are gonna<00:57:40.930> run<00:57:41.109> notes<00:57:41.380> and<00:57:41.680> stuff<00:57:41.859> together<00:57:42.269> but<00:57:43.269> I 00:57:43.319 --> 00:57:43.329 align:start position:0% gonna run notes and stuff together but I 00:57:43.329 --> 00:57:44.849 align:start position:0% gonna run notes and stuff together but I think<00:57:43.390> that<00:57:43.809> you<00:57:44.079> know<00:57:44.170> at<00:57:44.319> sufficiently 00:57:44.849 --> 00:57:44.859 align:start position:0% think that you know at sufficiently 00:57:44.859 --> 00:57:46.589 align:start position:0% think that you know at sufficiently large<00:57:45.400> volumes<00:57:45.819> you<00:57:45.970> have<00:57:46.299> to<00:57:46.420> do<00:57:46.510> it 00:57:46.589 --> 00:57:46.599 align:start position:0% large volumes you have to do it 00:57:46.599 --> 00:57:49.140 align:start position:0% large volumes you have to do it differently<00:57:46.869> and<00:57:47.109> I<00:57:48.039> don't<00:57:48.309> know<00:57:48.609> of<00:57:48.819> a<00:57:48.910> space 00:57:49.140 --> 00:57:49.150 align:start position:0% differently and I don't know of a space 00:57:49.150 --> 00:57:50.519 align:start position:0% differently and I don't know of a space where<00:57:49.390> people<00:57:49.660> really<00:57:49.779> talk<00:57:49.990> about<00:57:50.049> that<00:57:50.380> yet 00:57:50.519 --> 00:57:50.529 align:start position:0% where people really talk about that yet 00:57:50.529 --> 00:57:51.569 align:start position:0% where people really talk about that yet so<00:57:50.559> I<00:57:50.710> think<00:57:50.799> definitely<00:57:51.039> each<00:57:51.279> research 00:57:51.569 --> 00:57:51.579 align:start position:0% so I think definitely each research 00:57:51.579 --> 00:57:53.730 align:start position:0% so I think definitely each research would<00:57:51.730> be<00:57:51.849> an<00:57:51.940> interesting<00:57:52.119> place<00:57:52.450> to<00:57:52.740> just 00:57:53.730 --> 00:57:53.740 align:start position:0% would be an interesting place to just 00:57:53.740 --> 00:57:55.710 align:start position:0% would be an interesting place to just sort<00:57:53.859> of<00:57:53.950> discuss<00:57:54.190> that<00:57:54.369> or<00:57:54.609> either<00:57:55.089> magicians 00:57:55.710 --> 00:57:55.720 align:start position:0% sort of discuss that or either magicians 00:57:55.720 --> 00:57:59.299 align:start position:0% sort of discuss that or either magicians or<00:57:55.930> any<00:57:56.230> of<00:57:56.380> the<00:57:56.500> sort<00:57:56.680> of<00:57:56.769> forms<00:57:57.160> like<00:57:57.279> that 00:57:59.299 --> 00:57:59.309 align:start position:0% or any of the sort of forms like that 00:57:59.309 --> 00:58:01.710 align:start position:0% or any of the sort of forms like that all<00:58:00.309> right<00:58:00.369> we<00:58:00.970> got<00:58:01.089> we<00:58:01.180> got<00:58:01.299> one<00:58:01.450> quick 00:58:01.710 --> 00:58:01.720 align:start position:0% all right we got we got one quick 00:58:01.720 --> 00:58:04.470 align:start position:0% all right we got we got one quick comment<00:58:01.930> here<00:58:02.789> just<00:58:03.789> another<00:58:04.000> vote<00:58:04.180> in<00:58:04.299> favor 00:58:04.470 --> 00:58:04.480 align:start position:0% comment here just another vote in favor 00:58:04.480 --> 00:58:06.450 align:start position:0% comment here just another vote in favor of<00:58:04.660> just<00:58:04.809> some<00:58:04.990> sort<00:58:05.230> of<00:58:05.289> central<00:58:05.859> group<00:58:06.130> group 00:58:06.450 --> 00:58:06.460 align:start position:0% of just some sort of central group group 00:58:06.460 --> 00:58:08.160 align:start position:0% of just some sort of central group group chat<00:58:06.670> I<00:58:06.760> don't<00:58:06.910> care<00:58:07.029> at<00:58:07.119> the<00:58:07.180> venue<00:58:07.480> but<00:58:07.720> when 00:58:08.160 --> 00:58:08.170 align:start position:0% chat I don't care at the venue but when 00:58:08.170 --> 00:58:09.299 align:start position:0% chat I don't care at the venue but when I'm<00:58:08.260> having<00:58:08.410> issues<00:58:08.799> with<00:58:08.950> like<00:58:09.039> all<00:58:09.220> these 00:58:09.299 --> 00:58:09.309 align:start position:0% I'm having issues with like all these 00:58:09.309 --> 00:58:11.430 align:start position:0% I'm having issues with like all these like<00:58:09.490> holes<00:58:09.670> and<00:58:09.940> nonces<00:58:10.329> and<00:58:10.599> sending 00:58:11.430 --> 00:58:11.440 align:start position:0% like holes and nonces and sending 00:58:11.440 --> 00:58:13.529 align:start position:0% like holes and nonces and sending transactions<00:58:12.400> and<00:58:12.549> like<00:58:13.089> all<00:58:13.210> that<00:58:13.329> stuff 00:58:13.529 --> 00:58:13.539 align:start position:0% transactions and like all that stuff 00:58:13.539 --> 00:58:17.430 align:start position:0% transactions and like all that stuff just<00:58:13.650> if<00:58:14.650> we<00:58:14.799> can<00:58:14.950> find<00:58:15.160> some<00:58:15.549> central<00:58:16.539> group 00:58:17.430 --> 00:58:17.440 align:start position:0% just if we can find some central group 00:58:17.440 --> 00:58:23.039 align:start position:0% just if we can find some central group chat<00:58:17.650> ever<00:58:18.369> I<00:58:18.430> can<00:58:18.700> ask<00:58:18.970> you<00:58:19.210> guys<00:58:22.049> actually 00:58:23.039 --> 00:58:23.049 align:start position:0% chat ever I can ask you guys actually 00:58:23.049 --> 00:58:27.299 align:start position:0% chat ever I can ask you guys actually are<00:58:23.200> a<00:58:23.230> few<00:58:24.390> at<00:58:25.390> the<00:58:25.450> same<00:58:25.690> time<00:58:25.980> when<00:58:26.980> they<00:58:27.130> get 00:58:27.299 --> 00:58:27.309 align:start position:0% are a few at the same time when they get 00:58:27.309 --> 00:58:29.130 align:start position:0% are a few at the same time when they get too<00:58:27.430> large<00:58:27.640> and<00:58:28.000> people<00:58:28.480> start<00:58:28.690> leaving<00:58:29.019> and 00:58:29.130 --> 00:58:29.140 align:start position:0% too large and people start leaving and 00:58:29.140 --> 00:58:31.170 align:start position:0% too large and people start leaving and start<00:58:29.380> tuning<00:58:29.559> out<00:58:29.829> so<00:58:30.609> it's<00:58:30.759> it's<00:58:31.089> a 00:58:31.170 --> 00:58:31.180 align:start position:0% start tuning out so it's it's a 00:58:31.180 --> 00:58:38.339 align:start position:0% start tuning out so it's it's a challenge<00:58:36.539> yeah<00:58:37.539> I<00:58:37.569> think<00:58:37.990> it<00:58:38.109> would<00:58:38.200> be<00:58:38.259> good 00:58:38.339 --> 00:58:38.349 align:start position:0% challenge yeah I think it would be good 00:58:38.349 --> 00:58:39.749 align:start position:0% challenge yeah I think it would be good for<00:58:38.500> us<00:58:38.559> to<00:58:38.619> blog<00:58:39.039> post<00:58:39.309> or<00:58:39.430> something<00:58:39.670> about 00:58:39.749 --> 00:58:39.759 align:start position:0% for us to blog post or something about 00:58:39.759 --> 00:58:41.609 align:start position:0% for us to blog post or something about this<00:58:40.029> so<00:58:40.539> we've<00:58:40.630> only<00:58:40.720> got<00:58:40.900> 30<00:58:41.049> seconds<00:58:41.500> I<00:58:41.559> know 00:58:41.609 --> 00:58:41.619 align:start position:0% this so we've only got 30 seconds I know 00:58:41.619 --> 00:58:43.230 align:start position:0% this so we've only got 30 seconds I know the<00:58:41.769> panel's<00:58:42.069> out<00:58:42.190> here<00:58:42.400> but<00:58:42.549> to<00:58:42.670> end<00:58:42.819> on<00:58:43.029> an 00:58:43.230 --> 00:58:43.240 align:start position:0% the panel's out here but to end on an 00:58:43.240 --> 00:58:45.089 align:start position:0% the panel's out here but to end on an interesting<00:58:44.019> note<00:58:44.380> it<00:58:44.589> sounds<00:58:44.859> like<00:58:44.950> there's 00:58:45.089 --> 00:58:45.099 align:start position:0% interesting note it sounds like there's 00:58:45.099 --> 00:58:46.589 align:start position:0% interesting note it sounds like there's a<00:58:45.160> lot<00:58:45.309> of<00:58:45.400> challenges<00:58:45.609> from<00:58:46.150> a<00:58:46.180> developer 00:58:46.589 --> 00:58:46.599 align:start position:0% a lot of challenges from a developer 00:58:46.599 --> 00:58:47.849 align:start position:0% a lot of challenges from a developer point<00:58:46.779> of<00:58:46.930> view<00:58:47.019> I<00:58:47.259> know<00:58:47.380> that's<00:58:47.650> what<00:58:47.769> you 00:58:47.849 --> 00:58:47.859 align:start position:0% point of view I know that's what you 00:58:47.859 --> 00:58:51.630 align:start position:0% point of view I know that's what you engineers<00:58:48.250> love<00:58:49.559> but<00:58:50.559> what<00:58:51.069> like<00:58:51.309> why<00:58:51.490> are<00:58:51.549> you 00:58:51.630 --> 00:58:51.640 align:start position:0% engineers love but what like why are you 00:58:51.640 --> 00:58:53.279 align:start position:0% engineers love but what like why are you here<00:58:51.700> what's<00:58:52.089> so<00:58:52.210> exciting<00:58:52.480> about<00:58:52.720> you<00:58:53.049> to<00:58:53.259> be 00:58:53.279 --> 00:58:53.289 align:start position:0% here what's so exciting about you to be 00:58:53.289 --> 00:58:55.499 align:start position:0% here what's so exciting about you to be in<00:58:53.559> the<00:58:53.710> space<00:58:53.980> in<00:58:54.309> five<00:58:54.759> seconds 00:58:55.499 --> 00:58:55.509 align:start position:0% in the space in five seconds 00:58:55.509 --> 00:58:56.789 align:start position:0% in the space in five seconds none<00:58:56.079> of<00:58:56.109> the<00:58:56.259> challenges<00:58:56.680> are 00:58:56.789 --> 00:58:56.799 align:start position:0% none of the challenges are 00:58:56.799 --> 00:58:59.700 align:start position:0% none of the challenges are insurmountable<00:58:57.039> and<00:58:57.609> we're<00:58:58.390> seeing<00:58:58.690> the<00:58:59.319> 1/2 00:58:59.700 --> 00:58:59.710 align:start position:0% insurmountable and we're seeing the 1/2 00:58:59.710 --> 00:59:01.200 align:start position:0% insurmountable and we're seeing the 1/2 scale<00:58:59.950> and<00:59:00.160> the<00:59:00.220> one<00:59:00.339> to<00:59:00.460> get<00:59:00.579> better<00:59:00.789> here<00:59:01.029> and 00:59:01.200 --> 00:59:01.210 align:start position:0% scale and the one to get better here and 00:59:01.210 --> 00:59:05.849 align:start position:0% scale and the one to get better here and I<00:59:01.329> I<00:59:01.660> think<00:59:02.319> the<00:59:02.529> community<00:59:02.920> is<00:59:02.980> great<00:59:04.859> yeah 00:59:05.849 --> 00:59:05.859 align:start position:0% I I think the community is great yeah 00:59:05.859 --> 00:59:08.160 align:start position:0% I I think the community is great yeah I'm<00:59:06.460> sort<00:59:07.029> of<00:59:07.059> the<00:59:07.119> privacy<00:59:07.839> and<00:59:07.930> sort<00:59:08.109> of 00:59:08.160 --> 00:59:08.170 align:start position:0% I'm sort of the privacy and sort of 00:59:08.170 --> 00:59:10.410 align:start position:0% I'm sort of the privacy and sort of ownership<00:59:08.740> of<00:59:09.130> sort<00:59:09.490> of<00:59:09.519> your<00:59:09.700> own<00:59:09.759> funds<00:59:10.059> and 00:59:10.410 --> 00:59:10.420 align:start position:0% ownership of sort of your own funds and 00:59:10.420 --> 00:59:11.940 align:start position:0% ownership of sort of your own funds and you<00:59:10.720> know<00:59:10.839> all<00:59:11.049> the<00:59:11.230> sort<00:59:11.410> of<00:59:11.470> developments 00:59:11.940 --> 00:59:11.950 align:start position:0% you know all the sort of developments 00:59:11.950 --> 00:59:13.440 align:start position:0% you know all the sort of developments there<00:59:12.069> like<00:59:12.309> fascinating<00:59:12.910> to<00:59:13.029> me<00:59:13.059> all<00:59:13.299> this 00:59:13.440 --> 00:59:13.450 align:start position:0% there like fascinating to me all this 00:59:13.450 --> 00:59:14.700 align:start position:0% there like fascinating to me all this sort<00:59:13.720> of<00:59:13.779> talks<00:59:13.990> today<00:59:14.170> about<00:59:14.349> all<00:59:14.559> the 00:59:14.700 --> 00:59:14.710 align:start position:0% sort of talks today about all the 00:59:14.710 --> 00:59:17.309 align:start position:0% sort of talks today about all the privacy<00:59:15.099> all<00:59:15.519> the<00:59:16.019> cryptography<00:59:17.019> and<00:59:17.109> stuff 00:59:17.309 --> 00:59:17.319 align:start position:0% privacy all the cryptography and stuff 00:59:17.319 --> 00:59:18.900 align:start position:0% privacy all the cryptography and stuff is<00:59:17.440> it's<00:59:18.069> interesting<00:59:18.250> I<00:59:18.460> think<00:59:18.549> can<00:59:18.759> just 00:59:18.900 --> 00:59:18.910 align:start position:0% is it's interesting I think can just 00:59:18.910 --> 00:59:20.160 align:start position:0% is it's interesting I think can just lead<00:59:19.029> to<00:59:19.059> a<00:59:19.150> lot<00:59:19.299> of<00:59:19.329> you<00:59:19.450> know<00:59:19.509> good<00:59:19.750> in<00:59:19.960> the 00:59:20.160 --> 00:59:20.170 align:start position:0% lead to a lot of you know good in the 00:59:20.170 --> 00:59:22.499 align:start position:0% lead to a lot of you know good in the world<00:59:20.319> in<00:59:20.440> people<00:59:20.680> sort<00:59:20.859> of<00:59:20.890> you<00:59:21.009> know<00:59:21.509> all 00:59:22.499 --> 00:59:22.509 align:start position:0% world in people sort of you know all 00:59:22.509 --> 00:59:23.759 align:start position:0% world in people sort of you know all right<00:59:22.539> we<00:59:22.779> gonna<00:59:22.930> we<00:59:23.230> gotta<00:59:23.380> kind<00:59:23.559> of<00:59:23.589> wrap<00:59:23.740> it 00:59:23.759 --> 00:59:23.769 align:start position:0% right we gonna we gotta kind of wrap it 00:59:23.769 --> 00:59:25.769 align:start position:0% right we gonna we gotta kind of wrap it up<00:59:23.950> here<00:59:24.069> Morgan<00:59:24.549> if<00:59:24.640> you<00:59:24.700> want<00:59:24.849> a<00:59:24.910> five-second 00:59:25.769 --> 00:59:25.779 align:start position:0% up here Morgan if you want a five-second 00:59:25.779 --> 00:59:28.140 align:start position:0% up here Morgan if you want a five-second quick<00:59:26.140> brand<00:59:26.769> new<00:59:26.920> credit<00:59:27.160> set<00:59:27.609> of<00:59:27.730> problems 00:59:28.140 --> 00:59:28.150 align:start position:0% quick brand new credit set of problems 00:59:28.150 --> 00:59:29.460 align:start position:0% quick brand new credit set of problems to<00:59:28.269> solve<00:59:28.420> that<00:59:28.690> haven't<00:59:29.049> been<00:59:29.170> solved 00:59:29.460 --> 00:59:29.470 align:start position:0% to solve that haven't been solved 00:59:29.470 --> 00:59:39.290 align:start position:0% to solve that haven't been solved before<00:59:29.740> and<00:59:30.040> we<00:59:30.849> can<00:59:31.000> solve<00:59:31.150> them<00:59:31.240> together 00:59:39.290 --> 00:59:39.300 align:start position:0% 00:59:39.300 --> 00:59:41.360 align:start position:0% you