WEBVTT Kind: captions Language: en 00:00:01.010 --> 00:00:06.190 align:start position:0% [Music] 00:00:06.190 --> 00:00:06.200 align:start position:0% [Music] 00:00:06.200 --> 00:00:09.500 align:start position:0% [Music] so<00:00:07.200> hello<00:00:07.379> and<00:00:07.589> welcome<00:00:08.160> to<00:00:08.370> building<00:00:08.849> auger 00:00:09.500 --> 00:00:09.510 align:start position:0% so hello and welcome to building auger 00:00:09.510 --> 00:00:12.740 align:start position:0% so hello and welcome to building auger lessons<00:00:10.260> learned<00:00:11.090> in<00:00:12.090> this<00:00:12.269> talk<00:00:12.420> I'd<00:00:12.570> like<00:00:12.599> to 00:00:12.740 --> 00:00:12.750 align:start position:0% lessons learned in this talk I'd like to 00:00:12.750 --> 00:00:14.509 align:start position:0% lessons learned in this talk I'd like to tell<00:00:12.929> you<00:00:12.960> a<00:00:13.290> little<00:00:13.590> bit<00:00:13.710> about<00:00:13.920> myself<00:00:14.099> and 00:00:14.509 --> 00:00:14.519 align:start position:0% tell you a little bit about myself and 00:00:14.519 --> 00:00:17.689 align:start position:0% tell you a little bit about myself and go<00:00:15.389> quickly<00:00:15.690> into<00:00:15.929> what<00:00:16.289> auger<00:00:16.500> is<00:00:16.800> and<00:00:17.130> how<00:00:17.490> it 00:00:17.689 --> 00:00:17.699 align:start position:0% go quickly into what auger is and how it 00:00:17.699 --> 00:00:19.490 align:start position:0% go quickly into what auger is and how it might<00:00:17.850> architectural<00:00:18.720> II<00:00:18.779> differ<00:00:19.020> from 00:00:19.490 --> 00:00:19.500 align:start position:0% might architectural II differ from 00:00:19.500 --> 00:00:22.429 align:start position:0% might architectural II differ from depths<00:00:19.980> you<00:00:20.070> might<00:00:20.220> be<00:00:20.340> more<00:00:20.520> used<00:00:20.699> to<00:00:21.439> I'd 00:00:22.429 --> 00:00:22.439 align:start position:0% depths you might be more used to I'd 00:00:22.439 --> 00:00:23.720 align:start position:0% depths you might be more used to I'd also<00:00:22.560> like<00:00:22.710> to<00:00:22.830> talk<00:00:22.949> about<00:00:23.189> what<00:00:23.340> went<00:00:23.490> loft 00:00:23.720 --> 00:00:23.730 align:start position:0% also like to talk about what went loft 00:00:23.730 --> 00:00:26.029 align:start position:0% also like to talk about what went loft wrong<00:00:23.970> along<00:00:24.269> the<00:00:24.420> way<00:00:24.539> during<00:00:25.350> the<00:00:25.410> build<00:00:25.769> and 00:00:26.029 --> 00:00:26.039 align:start position:0% wrong along the way during the build and 00:00:26.039 --> 00:00:27.859 align:start position:0% wrong along the way during the build and deployment<00:00:26.430> process<00:00:26.970> we<00:00:27.240> had<00:00:27.390> issues<00:00:27.510> with 00:00:27.859 --> 00:00:27.869 align:start position:0% deployment process we had issues with 00:00:27.869 --> 00:00:30.439 align:start position:0% deployment process we had issues with test<00:00:28.380> at<00:00:28.500> deployment<00:00:29.010> we<00:00:29.910> had<00:00:30.000> issues<00:00:30.330> with 00:00:30.439 --> 00:00:30.449 align:start position:0% test at deployment we had issues with 00:00:30.449 --> 00:00:32.630 align:start position:0% test at deployment we had issues with our<00:00:30.599> integration<00:00:31.050> with<00:00:31.080> 0x<00:00:31.529> and<00:00:32.369> we've<00:00:32.489> had 00:00:32.630 --> 00:00:32.640 align:start position:0% our integration with 0x and we've had 00:00:32.640 --> 00:00:34.459 align:start position:0% our integration with 0x and we've had issues<00:00:32.969> with<00:00:33.210> the<00:00:33.360> etherium<00:00:33.899> JSON<00:00:34.290> RPC 00:00:34.459 --> 00:00:34.469 align:start position:0% issues with the etherium JSON RPC 00:00:34.469 --> 00:00:37.970 align:start position:0% issues with the etherium JSON RPC interface<00:00:36.140> and<00:00:37.140> finally<00:00:37.500> I'd<00:00:37.620> like<00:00:37.739> to<00:00:37.829> talk 00:00:37.970 --> 00:00:37.980 align:start position:0% interface and finally I'd like to talk 00:00:37.980 --> 00:00:39.110 align:start position:0% interface and finally I'd like to talk about<00:00:38.129> some<00:00:38.430> of<00:00:38.460> the<00:00:38.610> new<00:00:38.700> exciting<00:00:38.969> things 00:00:39.110 --> 00:00:39.120 align:start position:0% about some of the new exciting things 00:00:39.120 --> 00:00:43.959 align:start position:0% about some of the new exciting things we're<00:00:39.390> going<00:00:39.510> to<00:00:39.570> be<00:00:39.629> releasing<00:00:39.840> in<00:00:40.230> Agra<00:00:40.649> v2 00:00:43.959 --> 00:00:43.969 align:start position:0% 00:00:43.969 --> 00:00:46.940 align:start position:0% my<00:00:44.969> name<00:00:45.120> is<00:00:45.300> Scott<00:00:45.480> Bigelow<00:00:45.840> and<00:00:45.989> I<00:00:46.770> got 00:00:46.940 --> 00:00:46.950 align:start position:0% my name is Scott Bigelow and I got 00:00:46.950 --> 00:00:49.209 align:start position:0% my name is Scott Bigelow and I got involved<00:00:47.160> with<00:00:47.309> aetherium<00:00:47.820> in<00:00:48.030> early<00:00:48.570> 2017 00:00:49.209 --> 00:00:49.219 align:start position:0% involved with aetherium in early 2017 00:00:49.219 --> 00:00:51.650 align:start position:0% involved with aetherium in early 2017 when<00:00:50.219> I<00:00:50.250> wanted<00:00:50.640> to<00:00:50.700> understand<00:00:51.120> what<00:00:51.329> a<00:00:51.360> smart 00:00:51.650 --> 00:00:51.660 align:start position:0% when I wanted to understand what a smart 00:00:51.660 --> 00:00:54.020 align:start position:0% when I wanted to understand what a smart contract<00:00:51.840> was<00:00:52.260> a<00:00:52.289> little<00:00:52.620> better<00:00:52.800> I<00:00:53.070> had<00:00:53.910> some 00:00:54.020 --> 00:00:54.030 align:start position:0% contract was a little better I had some 00:00:54.030 --> 00:00:55.939 align:start position:0% contract was a little better I had some previous<00:00:54.210> experience<00:00:54.809> with<00:00:54.899> Bitcoin<00:00:55.590> back<00:00:55.829> in 00:00:55.939 --> 00:00:55.949 align:start position:0% previous experience with Bitcoin back in 00:00:55.949 --> 00:00:59.000 align:start position:0% previous experience with Bitcoin back in 2013<00:00:56.370> but<00:00:57.030> I<00:00:57.090> just<00:00:57.239> didn't<00:00:57.510> get<00:00:57.600> it<00:00:57.660> and<00:00:57.930> I<00:00:58.890> feel 00:00:59.000 --> 00:00:59.010 align:start position:0% 2013 but I just didn't get it and I feel 00:00:59.010 --> 00:01:00.740 align:start position:0% 2013 but I just didn't get it and I feel like<00:00:59.070> the<00:00:59.219> best<00:00:59.399> way<00:00:59.489> to<00:00:59.609> understand<00:01:00.210> was<00:01:00.480> to 00:01:00.740 --> 00:01:00.750 align:start position:0% like the best way to understand was to 00:01:00.750 --> 00:01:03.139 align:start position:0% like the best way to understand was to pick<00:01:01.680> up<00:01:01.800> a<00:01:01.859> tutorial<00:01:02.129> and<00:01:02.550> you<00:01:02.850> know<00:01:02.969> write 00:01:03.139 --> 00:01:03.149 align:start position:0% pick up a tutorial and you know write 00:01:03.149 --> 00:01:06.140 align:start position:0% pick up a tutorial and you know write the<00:01:03.300> standard<00:01:03.660> er<00:01:03.899> C<00:01:04.049> 20<00:01:04.379> contract<00:01:05.010> but<00:01:05.880> to<00:01:06.000> do 00:01:06.140 --> 00:01:06.150 align:start position:0% the standard er C 20 contract but to do 00:01:06.150 --> 00:01:06.560 align:start position:0% the standard er C 20 contract but to do so 00:01:06.560 --> 00:01:06.570 align:start position:0% so 00:01:06.570 --> 00:01:09.740 align:start position:0% so you<00:01:06.990> needed<00:01:07.290> to<00:01:07.439> get<00:01:07.560> on<00:01:07.740> a<00:01:07.770> test<00:01:08.070> network<00:01:08.750> in 00:01:09.740 --> 00:01:09.750 align:start position:0% you needed to get on a test network in 00:01:09.750 --> 00:01:11.480 align:start position:0% you needed to get on a test network in the<00:01:09.840> network<00:01:10.110> that<00:01:10.200> I<00:01:10.260> chose<00:01:10.500> at<00:01:10.650> the<00:01:10.680> time<00:01:10.950> was 00:01:11.480 --> 00:01:11.490 align:start position:0% the network that I chose at the time was 00:01:11.490 --> 00:01:15.649 align:start position:0% the network that I chose at the time was kovin<00:01:12.200> this<00:01:13.200> is<00:01:13.470> a<00:01:13.500> parity<00:01:14.310> only<00:01:14.640> proof<00:01:15.450> of 00:01:15.649 --> 00:01:15.659 align:start position:0% kovin this is a parity only proof of 00:01:15.659 --> 00:01:18.920 align:start position:0% kovin this is a parity only proof of authority<00:01:16.110> Network<00:01:17.390> proof<00:01:18.390> of<00:01:18.479> authority 00:01:18.920 --> 00:01:18.930 align:start position:0% authority Network proof of authority 00:01:18.930 --> 00:01:20.719 align:start position:0% authority Network proof of authority means<00:01:19.500> that<00:01:19.740> there's<00:01:20.100> a<00:01:20.189> small<00:01:20.490> set<00:01:20.700> of 00:01:20.719 --> 00:01:20.729 align:start position:0% means that there's a small set of 00:01:20.729 --> 00:01:22.490 align:start position:0% means that there's a small set of validators<00:01:21.270> that<00:01:21.659> are<00:01:21.750> eligible<00:01:22.140> to<00:01:22.200> mine 00:01:22.490 --> 00:01:22.500 align:start position:0% validators that are eligible to mine 00:01:22.500 --> 00:01:24.469 align:start position:0% validators that are eligible to mine this<00:01:22.680> network<00:01:22.979> so<00:01:23.729> if<00:01:23.820> you<00:01:23.909> want<00:01:24.060> to<00:01:24.150> come<00:01:24.330> by 00:01:24.469 --> 00:01:24.479 align:start position:0% this network so if you want to come by 00:01:24.479 --> 00:01:26.690 align:start position:0% this network so if you want to come by any<00:01:24.689> Co<00:01:24.960> vineeth<00:01:25.290> you<00:01:26.280> need<00:01:26.400> to<00:01:26.490> go<00:01:26.549> to<00:01:26.610> a 00:01:26.690 --> 00:01:26.700 align:start position:0% any Co vineeth you need to go to a 00:01:26.700 --> 00:01:29.300 align:start position:0% any Co vineeth you need to go to a faucet<00:01:26.970> and<00:01:27.390> one<00:01:28.380> of<00:01:28.470> the<00:01:28.530> popular<00:01:28.860> faucets<00:01:29.220> at 00:01:29.300 --> 00:01:29.310 align:start position:0% faucet and one of the popular faucets at 00:01:29.310 --> 00:01:31.039 align:start position:0% faucet and one of the popular faucets at the<00:01:29.400> time<00:01:29.640> was<00:01:30.030> this<00:01:30.210> Gator<00:01:30.540> channel<00:01:30.930> where 00:01:31.039 --> 00:01:31.049 align:start position:0% the time was this Gator channel where 00:01:31.049 --> 00:01:32.870 align:start position:0% the time was this Gator channel where you<00:01:31.140> can<00:01:31.259> come<00:01:31.439> in<00:01:31.470> type<00:01:32.100> in<00:01:32.280> your<00:01:32.369> Kovan<00:01:32.729> eath 00:01:32.870 --> 00:01:32.880 align:start position:0% you can come in type in your Kovan eath 00:01:32.880 --> 00:01:35.960 align:start position:0% you can come in type in your Kovan eath interface<00:01:33.270> beneath<00:01:34.229> address<00:01:34.650> and<00:01:34.970> somebody 00:01:35.960 --> 00:01:35.970 align:start position:0% interface beneath address and somebody 00:01:35.970 --> 00:01:37.460 align:start position:0% interface beneath address and somebody will<00:01:36.090> come<00:01:36.119> by<00:01:36.360> maybe<00:01:36.600> in<00:01:36.780> four<00:01:36.960> hours<00:01:37.259> maybe 00:01:37.460 --> 00:01:37.470 align:start position:0% will come by maybe in four hours maybe 00:01:37.470 --> 00:01:41.140 align:start position:0% will come by maybe in four hours maybe in<00:01:37.650> 36<00:01:38.130> and<00:01:38.430> will<00:01:39.000> send<00:01:39.270> you<00:01:39.479> some<00:01:39.689> Co<00:01:39.930> vineeth 00:01:41.140 --> 00:01:41.150 align:start position:0% in 36 and will send you some Co vineeth 00:01:41.150 --> 00:01:43.280 align:start position:0% in 36 and will send you some Co vineeth now<00:01:42.150> I<00:01:42.180> come<00:01:42.420> from<00:01:42.509> a<00:01:42.630> background<00:01:42.780> of<00:01:42.990> software 00:01:43.280 --> 00:01:43.290 align:start position:0% now I come from a background of software 00:01:43.290 --> 00:01:44.870 align:start position:0% now I come from a background of software development<00:01:43.590> so<00:01:44.070> my<00:01:44.189> first<00:01:44.340> thought<00:01:44.549> was<00:01:44.700> well 00:01:44.870 --> 00:01:44.880 align:start position:0% development so my first thought was well 00:01:44.880 --> 00:01:46.609 align:start position:0% development so my first thought was well we<00:01:44.939> should<00:01:45.090> automate<00:01:45.360> this<00:01:45.509> and<00:01:45.840> so<00:01:46.259> I<00:01:46.290> wrote 00:01:46.609 --> 00:01:46.619 align:start position:0% we should automate this and so I wrote 00:01:46.619 --> 00:01:48.620 align:start position:0% we should automate this and so I wrote this<00:01:46.920> kovin<00:01:47.549> Gator<00:01:48.060> BOTS 00:01:48.620 --> 00:01:48.630 align:start position:0% this kovin Gator BOTS 00:01:48.630 --> 00:01:50.569 align:start position:0% this kovin Gator BOTS that's<00:01:49.079> monitored<00:01:49.920> for<00:01:50.100> these<00:01:50.220> things<00:01:50.399> and 00:01:50.569 --> 00:01:50.579 align:start position:0% that's monitored for these things and 00:01:50.579 --> 00:01:52.130 align:start position:0% that's monitored for these things and delivered<00:01:51.060> if<00:01:51.180> to<00:01:51.360> the<00:01:51.450> people<00:01:51.689> who<00:01:51.780> requested 00:01:52.130 --> 00:01:52.140 align:start position:0% delivered if to the people who requested 00:01:52.140 --> 00:01:54.560 align:start position:0% delivered if to the people who requested them<00:01:52.290> in<00:01:52.439> real<00:01:52.649> time<00:01:52.920> and<00:01:53.189> this<00:01:54.180> was<00:01:54.299> really<00:01:54.479> my 00:01:54.560 --> 00:01:54.570 align:start position:0% them in real time and this was really my 00:01:54.570 --> 00:01:56.359 align:start position:0% them in real time and this was really my first<00:01:54.750> interface<00:01:55.290> with<00:01:55.590> the<00:01:55.920> etherium 00:01:56.359 --> 00:01:56.369 align:start position:0% first interface with the etherium 00:01:56.369 --> 00:01:58.490 align:start position:0% first interface with the etherium ecosystem<00:01:56.880> and<00:01:57.180> I<00:01:57.689> thought<00:01:57.840> it<00:01:57.960> was<00:01:58.049> great<00:01:58.200> and 00:01:58.490 --> 00:01:58.500 align:start position:0% ecosystem and I thought it was great and 00:01:58.500 --> 00:02:01.209 align:start position:0% ecosystem and I thought it was great and I<00:01:58.770> had<00:01:58.920> even<00:01:59.040> gotten<00:01:59.310> to<00:01:59.340> smart<00:01:59.670> contracts<00:02:00.149> yet 00:02:01.209 --> 00:02:01.219 align:start position:0% I had even gotten to smart contracts yet 00:02:01.219 --> 00:02:03.469 align:start position:0% I had even gotten to smart contracts yet this<00:02:02.219> bot<00:02:02.430> has<00:02:02.579> been<00:02:02.700> running<00:02:02.939> for<00:02:02.969> just<00:02:03.360> over 00:02:03.469 --> 00:02:03.479 align:start position:0% this bot has been running for just over 00:02:03.479 --> 00:02:05.090 align:start position:0% this bot has been running for just over a<00:02:03.630> year<00:02:03.689> now<00:02:03.869> and<00:02:04.200> has<00:02:04.320> faucet<00:02:04.680> adore<00:02:04.920> most 00:02:05.090 --> 00:02:05.100 align:start position:0% a year now and has faucet adore most 00:02:05.100 --> 00:02:08.630 align:start position:0% a year now and has faucet adore most 30,000<00:02:05.969> times<00:02:06.950> so<00:02:07.950> if<00:02:08.069> you've<00:02:08.190> gotten<00:02:08.489> Co 00:02:08.630 --> 00:02:08.640 align:start position:0% 30,000 times so if you've gotten Co 00:02:08.640 --> 00:02:11.420 align:start position:0% 30,000 times so if you've gotten Co vineeth<00:02:08.910> in<00:02:09.869> this<00:02:10.110> Gator<00:02:10.289> channel<00:02:10.649> you<00:02:11.160> got<00:02:11.310> it 00:02:11.420 --> 00:02:11.430 align:start position:0% vineeth in this Gator channel you got it 00:02:11.430 --> 00:02:13.350 align:start position:0% vineeth in this Gator channel you got it from<00:02:11.520> me 00:02:13.350 --> 00:02:13.360 align:start position:0% from me 00:02:13.360 --> 00:02:15.520 align:start position:0% from me but<00:02:14.360> this<00:02:14.450> really<00:02:14.660> led<00:02:14.810> me<00:02:14.840> to<00:02:15.140> wanting<00:02:15.349> to<00:02:15.440> get 00:02:15.520 --> 00:02:15.530 align:start position:0% but this really led me to wanting to get 00:02:15.530 --> 00:02:17.559 align:start position:0% but this really led me to wanting to get more<00:02:15.830> involved<00:02:16.280> in<00:02:16.400> the<00:02:16.670> etherium<00:02:17.000> ecosystem 00:02:17.559 --> 00:02:17.569 align:start position:0% more involved in the etherium ecosystem 00:02:17.569 --> 00:02:20.470 align:start position:0% more involved in the etherium ecosystem and<00:02:18.349> I<00:02:18.410> started<00:02:18.709> work<00:02:18.860> on<00:02:19.040> auger<00:02:19.760> later<00:02:20.300> that 00:02:20.470 --> 00:02:20.480 align:start position:0% and I started work on auger later that 00:02:20.480 --> 00:02:24.990 align:start position:0% and I started work on auger later that year<00:02:20.599> in<00:02:20.750> 2017<00:02:22.360> auger<00:02:23.360> is<00:02:23.510> a<00:02:23.870> etherium<00:02:24.709> based 00:02:24.990 --> 00:02:25.000 align:start position:0% year in 2017 auger is a etherium based 00:02:25.000 --> 00:02:27.990 align:start position:0% year in 2017 auger is a etherium based decentralized<00:02:26.000> prediction<00:02:26.900> market<00:02:27.200> protocol 00:02:27.990 --> 00:02:28.000 align:start position:0% decentralized prediction market protocol 00:02:28.000 --> 00:02:30.400 align:start position:0% decentralized prediction market protocol this<00:02:29.000> is<00:02:29.090> a<00:02:29.150> system<00:02:29.450> where<00:02:29.569> any<00:02:29.720> user<00:02:29.959> can<00:02:30.080> come 00:02:30.400 --> 00:02:30.410 align:start position:0% this is a system where any user can come 00:02:30.410 --> 00:02:32.530 align:start position:0% this is a system where any user can come and<00:02:30.590> create<00:02:31.370> a<00:02:31.400> market<00:02:31.760> which<00:02:32.060> is<00:02:32.090> really<00:02:32.360> just 00:02:32.530 --> 00:02:32.540 align:start position:0% and create a market which is really just 00:02:32.540 --> 00:02:35.290 align:start position:0% and create a market which is really just a<00:02:32.720> question<00:02:33.140> that<00:02:34.010> has<00:02:34.160> some<00:02:34.849> set<00:02:35.060> of<00:02:35.150> outcomes 00:02:35.290 --> 00:02:35.300 align:start position:0% a question that has some set of outcomes 00:02:35.300 --> 00:02:38.259 align:start position:0% a question that has some set of outcomes and<00:02:35.830> an<00:02:36.830> expiration<00:02:37.250> date<00:02:37.459> some<00:02:37.760> future<00:02:38.090> date 00:02:38.259 --> 00:02:38.269 align:start position:0% and an expiration date some future date 00:02:38.269 --> 00:02:40.140 align:start position:0% and an expiration date some future date where<00:02:38.420> this<00:02:38.480> is<00:02:38.630> going<00:02:38.750> to<00:02:38.810> be<00:02:38.900> resolved 00:02:40.140 --> 00:02:40.150 align:start position:0% where this is going to be resolved 00:02:40.150 --> 00:02:43.000 align:start position:0% where this is going to be resolved before<00:02:41.150> that<00:02:41.480> resolution<00:02:41.750> users<00:02:42.470> can<00:02:42.650> stake 00:02:43.000 --> 00:02:43.010 align:start position:0% before that resolution users can stake 00:02:43.010 --> 00:02:44.920 align:start position:0% before that resolution users can stake eath<00:02:43.250> on<00:02:43.519> what<00:02:43.730> they<00:02:43.849> believe<00:02:43.879> that<00:02:44.660> correct 00:02:44.920 --> 00:02:44.930 align:start position:0% eath on what they believe that correct 00:02:44.930 --> 00:02:48.400 align:start position:0% eath on what they believe that correct outcome<00:02:45.290> to<00:02:45.440> be<00:02:45.470> and<00:02:46.299> after<00:02:47.299> resolution<00:02:47.540> the 00:02:48.400 --> 00:02:48.410 align:start position:0% outcome to be and after resolution the 00:02:48.410 --> 00:02:50.080 align:start position:0% outcome to be and after resolution the market<00:02:48.830> creator<00:02:49.099> is<00:02:49.310> responsible<00:02:49.849> to<00:02:49.910> come 00:02:50.080 --> 00:02:50.090 align:start position:0% market creator is responsible to come 00:02:50.090 --> 00:02:52.210 align:start position:0% market creator is responsible to come back<00:02:50.269> and<00:02:50.480> inform<00:02:51.410> the<00:02:51.560> blockchain<00:02:51.739> what<00:02:52.130> the 00:02:52.210 --> 00:02:52.220 align:start position:0% back and inform the blockchain what the 00:02:52.220 --> 00:02:55.750 align:start position:0% back and inform the blockchain what the real<00:02:52.459> world<00:02:52.760> outcome<00:02:53.239> was<00:02:54.459> but<00:02:55.459> of<00:02:55.549> course 00:02:55.750 --> 00:02:55.760 align:start position:0% real world outcome was but of course 00:02:55.760 --> 00:02:57.069 align:start position:0% real world outcome was but of course there's<00:02:55.910> no<00:02:55.970> reason<00:02:56.090> to<00:02:56.450> trust<00:02:56.599> this<00:02:56.780> market 00:02:57.069 --> 00:02:57.079 align:start position:0% there's no reason to trust this market 00:02:57.079 --> 00:02:58.509 align:start position:0% there's no reason to trust this market crater<00:02:57.349> to<00:02:57.890> give<00:02:58.040> you<00:02:58.130> the<00:02:58.250> correct<00:02:58.400> answer 00:02:58.509 --> 00:02:58.519 align:start position:0% crater to give you the correct answer 00:02:58.519 --> 00:03:01.259 align:start position:0% crater to give you the correct answer and<00:02:59.140> that's<00:03:00.140> where<00:03:00.290> augur<00:03:00.530> really<00:03:00.799> comes<00:03:00.980> in 00:03:01.259 --> 00:03:01.269 align:start position:0% and that's where augur really comes in 00:03:01.269 --> 00:03:04.059 align:start position:0% and that's where augur really comes in auger<00:03:02.269> has<00:03:02.450> created<00:03:02.750> a<00:03:02.780> system<00:03:02.959> of<00:03:03.260> economic 00:03:04.059 --> 00:03:04.069 align:start position:0% auger has created a system of economic 00:03:04.069 --> 00:03:06.670 align:start position:0% auger has created a system of economic incentives<00:03:04.420> such<00:03:05.420> that<00:03:05.630> rep<00:03:05.870> holders<00:03:06.319> the 00:03:06.670 --> 00:03:06.680 align:start position:0% incentives such that rep holders the 00:03:06.680 --> 00:03:08.620 align:start position:0% incentives such that rep holders the holders<00:03:07.130> of<00:03:07.160> the<00:03:07.310> auger<00:03:07.730> rep<00:03:08.000> token<00:03:08.480> are 00:03:08.620 --> 00:03:08.630 align:start position:0% holders of the auger rep token are 00:03:08.630 --> 00:03:11.050 align:start position:0% holders of the auger rep token are incentivized<00:03:09.560> to<00:03:09.709> come<00:03:09.920> and<00:03:10.160> dispute<00:03:10.730> answers 00:03:11.050 --> 00:03:11.060 align:start position:0% incentivized to come and dispute answers 00:03:11.060 --> 00:03:13.660 align:start position:0% incentivized to come and dispute answers that<00:03:11.239> are<00:03:11.329> incorrect<00:03:11.720> in<00:03:12.370> this<00:03:13.370> dispute 00:03:13.660 --> 00:03:13.670 align:start position:0% that are incorrect in this dispute 00:03:13.670 --> 00:03:15.220 align:start position:0% that are incorrect in this dispute process<00:03:14.090> can<00:03:14.329> last<00:03:14.450> a<00:03:14.630> long<00:03:14.780> time 00:03:15.220 --> 00:03:15.230 align:start position:0% process can last a long time 00:03:15.230 --> 00:03:17.650 align:start position:0% process can last a long time this<00:03:16.099> depute<00:03:16.430> dispute<00:03:16.880> process<00:03:17.180> can<00:03:17.329> go<00:03:17.359> back 00:03:17.650 --> 00:03:17.660 align:start position:0% this depute dispute process can go back 00:03:17.660 --> 00:03:20.800 align:start position:0% this depute dispute process can go back and<00:03:17.900> forth<00:03:18.109> and<00:03:18.350> back<00:03:18.410> and<00:03:18.530> forth<00:03:18.739> and<00:03:19.630> if<00:03:20.630> we 00:03:20.800 --> 00:03:20.810 align:start position:0% and forth and back and forth and if we 00:03:20.810 --> 00:03:22.569 align:start position:0% and forth and back and forth and if we ever<00:03:20.930> notice<00:03:21.260> this<00:03:21.470> if<00:03:21.950> if<00:03:22.069> the<00:03:22.190> system<00:03:22.459> ever 00:03:22.569 --> 00:03:22.579 align:start position:0% ever notice this if if the system ever 00:03:22.579 --> 00:03:23.650 align:start position:0% ever notice this if if the system ever notices<00:03:22.970> that<00:03:23.090> there<00:03:23.209> is<00:03:23.299> a<00:03:23.329> major<00:03:23.510> problem 00:03:23.650 --> 00:03:23.660 align:start position:0% notices that there is a major problem 00:03:23.660 --> 00:03:26.410 align:start position:0% notices that there is a major problem the<00:03:24.560> system<00:03:24.799> ends<00:03:25.040> up<00:03:25.100> forking<00:03:25.790> and<00:03:25.940> every 00:03:26.410 --> 00:03:26.420 align:start position:0% the system ends up forking and every 00:03:26.420 --> 00:03:27.900 align:start position:0% the system ends up forking and every holder<00:03:26.750> of<00:03:26.900> rep<00:03:27.079> needs<00:03:27.350> to<00:03:27.440> make<00:03:27.560> a<00:03:27.590> decision 00:03:27.900 --> 00:03:27.910 align:start position:0% holder of rep needs to make a decision 00:03:27.910 --> 00:03:30.280 align:start position:0% holder of rep needs to make a decision which<00:03:28.910> side<00:03:29.180> of<00:03:29.299> this<00:03:29.389> fork<00:03:29.720> do<00:03:29.870> I<00:03:29.930> want<00:03:30.139> to<00:03:30.200> be 00:03:30.280 --> 00:03:30.290 align:start position:0% which side of this fork do I want to be 00:03:30.290 --> 00:03:33.819 align:start position:0% which side of this fork do I want to be on<00:03:30.440> and<00:03:30.850> we<00:03:31.850> believe<00:03:32.150> that<00:03:32.450> you<00:03:33.170> that<00:03:33.530> holders 00:03:33.819 --> 00:03:33.829 align:start position:0% on and we believe that you that holders 00:03:33.829 --> 00:03:34.690 align:start position:0% on and we believe that you that holders of<00:03:33.950> rep<00:03:34.069> token<00:03:34.370> are<00:03:34.459> going<00:03:34.579> to<00:03:34.639> be 00:03:34.690 --> 00:03:34.700 align:start position:0% of rep token are going to be 00:03:34.700 --> 00:03:36.879 align:start position:0% of rep token are going to be incentivized<00:03:35.209> to<00:03:35.299> want<00:03:35.510> to<00:03:35.600> be<00:03:35.720> on<00:03:35.750> the<00:03:36.560> true 00:03:36.879 --> 00:03:36.889 align:start position:0% incentivized to want to be on the true 00:03:36.889 --> 00:03:39.280 align:start position:0% incentivized to want to be on the true fork<00:03:37.459> the<00:03:38.000> fork<00:03:38.030> that<00:03:38.389> represents<00:03:38.840> the<00:03:38.989> true 00:03:39.280 --> 00:03:39.290 align:start position:0% fork the fork that represents the true 00:03:39.290 --> 00:03:44.199 align:start position:0% fork the fork that represents the true outcome<00:03:42.069> to<00:03:43.069> accomplish<00:03:43.400> this<00:03:43.549> took<00:03:44.000> quite<00:03:44.150> a 00:03:44.199 --> 00:03:44.209 align:start position:0% outcome to accomplish this took quite a 00:03:44.209 --> 00:03:47.949 align:start position:0% outcome to accomplish this took quite a bit<00:03:44.359> of<00:03:44.450> code<00:03:45.130> augur<00:03:46.130> is<00:03:46.489> nearly<00:03:46.760> 5000<00:03:47.750> lines 00:03:47.949 --> 00:03:47.959 align:start position:0% bit of code augur is nearly 5000 lines 00:03:47.959 --> 00:03:50.319 align:start position:0% bit of code augur is nearly 5000 lines of<00:03:48.170> solidity<00:03:48.500> code<00:03:48.769> and<00:03:48.980> the<00:03:49.579> base<00:03:49.730> deploy<00:03:50.090> is 00:03:50.319 --> 00:03:50.329 align:start position:0% of solidity code and the base deploy is 00:03:50.329 --> 00:03:54.610 align:start position:0% of solidity code and the base deploy is 41<00:03:50.989> contracts<00:03:51.609> and<00:03:53.380> architectural<00:03:54.380> a<00:03:54.470> it's<00:03:54.560> a 00:03:54.610 --> 00:03:54.620 align:start position:0% 41 contracts and architectural a it's a 00:03:54.620 --> 00:03:57.640 align:start position:0% 41 contracts and architectural a it's a little<00:03:54.799> different<00:03:55.069> to<00:03:56.109> if<00:03:57.109> you've<00:03:57.319> used<00:03:57.500> the 00:03:57.640 --> 00:03:57.650 align:start position:0% little different to if you've used the 00:03:57.650 --> 00:04:00.039 align:start position:0% little different to if you've used the maker<00:03:57.950> interface<00:03:58.400> before<00:03:58.609> this<00:03:59.239> is<00:03:59.480> a<00:03:59.750> this<00:03:59.959> is 00:04:00.039 --> 00:04:00.049 align:start position:0% maker interface before this is a this is 00:04:00.049 --> 00:04:02.080 align:start position:0% maker interface before this is a this is another<00:04:00.230> DAP<00:04:00.470> which<00:04:01.040> is<00:04:01.190> a<00:04:01.220> series<00:04:01.760> of<00:04:01.790> smart 00:04:02.080 --> 00:04:02.090 align:start position:0% another DAP which is a series of smart 00:04:02.090 --> 00:04:05.949 align:start position:0% another DAP which is a series of smart contracts<00:04:02.630> and<00:04:02.810> a<00:04:03.650> UI<00:04:04.190> a<00:04:04.519> static<00:04:05.030> UI<00:04:05.180> that<00:04:05.810> can 00:04:05.949 --> 00:04:05.959 align:start position:0% contracts and a UI a static UI that can 00:04:05.959 --> 00:04:07.300 align:start position:0% contracts and a UI a static UI that can make<00:04:06.109> dynamic<00:04:06.290> calls<00:04:06.620> into<00:04:06.889> a<00:04:06.950> theorem<00:04:07.250> and 00:04:07.300 --> 00:04:07.310 align:start position:0% make dynamic calls into a theorem and 00:04:07.310 --> 00:04:09.729 align:start position:0% make dynamic calls into a theorem and run<00:04:07.459> an<00:04:07.549> eighth<00:04:07.670> call<00:04:08.000> this<00:04:08.989> is<00:04:09.139> a<00:04:09.169> simple 00:04:09.729 --> 00:04:09.739 align:start position:0% run an eighth call this is a simple 00:04:09.739 --> 00:04:11.979 align:start position:0% run an eighth call this is a simple function<00:04:09.859> call<00:04:10.220> is<00:04:10.370> just<00:04:10.400> a<00:04:10.549> read<00:04:10.790> call<00:04:11.030> to<00:04:11.780> ask 00:04:11.979 --> 00:04:11.989 align:start position:0% function call is just a read call to ask 00:04:11.989 --> 00:04:13.420 align:start position:0% function call is just a read call to ask questions<00:04:12.380> I<00:04:12.440> might<00:04:12.530> ask<00:04:12.590> things<00:04:12.950> like<00:04:13.130> hey 00:04:13.420 --> 00:04:13.430 align:start position:0% questions I might ask things like hey 00:04:13.430 --> 00:04:14.979 align:start position:0% questions I might ask things like hey how<00:04:13.579> much<00:04:13.730> MKR<00:04:14.120> does<00:04:14.419> this<00:04:14.480> account<00:04:14.810> to<00:04:14.870> have 00:04:14.979 --> 00:04:14.989 align:start position:0% how much MKR does this account to have 00:04:14.989 --> 00:04:17.050 align:start position:0% how much MKR does this account to have you<00:04:15.650> know<00:04:15.739> how<00:04:15.859> much<00:04:15.980> died<00:04:16.400> is<00:04:16.639> this<00:04:16.760> account 00:04:17.050 --> 00:04:17.060 align:start position:0% you know how much died is this account 00:04:17.060 --> 00:04:21.399 align:start position:0% you know how much died is this account half<00:04:19.090> now<00:04:20.090> these<00:04:20.209> questions<00:04:20.870> come<00:04:21.109> from<00:04:21.320> the 00:04:21.399 --> 00:04:21.409 align:start position:0% half now these questions come from the 00:04:21.409 --> 00:04:23.770 align:start position:0% half now these questions come from the current<00:04:21.829> states<00:04:22.159> of<00:04:22.340> the<00:04:23.120> etherium<00:04:23.479> network 00:04:23.770 --> 00:04:23.780 align:start position:0% current states of the etherium network 00:04:23.780 --> 00:04:25.410 align:start position:0% current states of the etherium network all<00:04:24.020> this<00:04:24.500> data<00:04:24.680> is<00:04:24.830> stored 00:04:25.410 --> 00:04:25.420 align:start position:0% all this data is stored 00:04:25.420 --> 00:04:26.940 align:start position:0% all this data is stored that<00:04:25.600> you<00:04:25.720> know<00:04:25.810> the<00:04:25.960> storage<00:04:26.230> of<00:04:26.560> the 00:04:26.940 --> 00:04:26.950 align:start position:0% that you know the storage of the 00:04:26.950 --> 00:04:29.910 align:start position:0% that you know the storage of the contract<00:04:27.520> space<00:04:27.990> and<00:04:28.990> there's<00:04:29.620> a<00:04:29.680> little<00:04:29.830> bit 00:04:29.910 --> 00:04:29.920 align:start position:0% contract space and there's a little bit 00:04:29.920 --> 00:04:31.530 align:start position:0% contract space and there's a little bit of<00:04:29.950> logs<00:04:30.160> here<00:04:30.430> they<00:04:30.730> can<00:04:30.910> tell<00:04:31.300> you<00:04:31.390> some 00:04:31.530 --> 00:04:31.540 align:start position:0% of logs here they can tell you some 00:04:31.540 --> 00:04:33.090 align:start position:0% of logs here they can tell you some things<00:04:31.750> that<00:04:31.870> happened<00:04:32.140> in<00:04:32.200> history<00:04:32.530> but 00:04:33.090 --> 00:04:33.100 align:start position:0% things that happened in history but 00:04:33.100 --> 00:04:34.830 align:start position:0% things that happened in history but mostly<00:04:33.610> it<00:04:33.790> is<00:04:33.880> powered<00:04:34.210> by<00:04:34.240> asking<00:04:34.780> questions 00:04:34.830 --> 00:04:34.840 align:start position:0% mostly it is powered by asking questions 00:04:34.840 --> 00:04:37.040 align:start position:0% mostly it is powered by asking questions about<00:04:35.350> right<00:04:35.710> now 00:04:37.040 --> 00:04:37.050 align:start position:0% about right now 00:04:37.050 --> 00:04:38.850 align:start position:0% about right now so<00:04:38.050> our<00:04:38.230> ger<00:04:38.320> does<00:04:38.470> this<00:04:38.560> a<00:04:38.620> little 00:04:38.850 --> 00:04:38.860 align:start position:0% so our ger does this a little 00:04:38.860 --> 00:04:40.830 align:start position:0% so our ger does this a little differently<00:04:39.190> the<00:04:39.850> UI<00:04:40.000> does<00:04:40.360> not<00:04:40.540> communicate 00:04:40.830 --> 00:04:40.840 align:start position:0% differently the UI does not communicate 00:04:40.840 --> 00:04:43.590 align:start position:0% differently the UI does not communicate directly<00:04:41.380> with<00:04:41.770> the<00:04:42.040> etherium<00:04:42.400> node<00:04:42.580> the<00:04:43.420> UI 00:04:43.590 --> 00:04:43.600 align:start position:0% directly with the etherium node the UI 00:04:43.600 --> 00:04:46.470 align:start position:0% directly with the etherium node the UI has<00:04:43.870> an<00:04:43.990> intermediary<00:04:44.530> which<00:04:45.370> processes<00:04:45.970> logs 00:04:46.470 --> 00:04:46.480 align:start position:0% has an intermediary which processes logs 00:04:46.480 --> 00:04:49.400 align:start position:0% has an intermediary which processes logs to<00:04:47.200> reconstitute<00:04:48.010> the<00:04:48.370> state<00:04:48.580> of<00:04:48.790> augur<00:04:48.970> and 00:04:49.400 --> 00:04:49.410 align:start position:0% to reconstitute the state of augur and 00:04:49.410 --> 00:04:51.960 align:start position:0% to reconstitute the state of augur and because<00:04:50.410> augur<00:04:50.740> is<00:04:50.860> a<00:04:50.890> decentralized<00:04:51.430> system 00:04:51.960 --> 00:04:51.970 align:start position:0% because augur is a decentralized system 00:04:51.970 --> 00:04:54.630 align:start position:0% because augur is a decentralized system this<00:04:52.630> isn't<00:04:52.930> a<00:04:52.960> server<00:04:53.200> sitting<00:04:53.380> in<00:04:53.560> iraq<00:04:53.800> this 00:04:54.630 --> 00:04:54.640 align:start position:0% this isn't a server sitting in iraq this 00:04:54.640 --> 00:04:58.050 align:start position:0% this isn't a server sitting in iraq this is<00:04:55.120> your<00:04:55.390> box<00:04:55.570> and<00:04:56.280> if<00:04:57.280> you've<00:04:57.400> ever<00:04:57.490> seen<00:04:57.850> this 00:04:58.050 --> 00:04:58.060 align:start position:0% is your box and if you've ever seen this 00:04:58.060 --> 00:04:59.940 align:start position:0% is your box and if you've ever seen this window<00:04:58.360> before<00:04:58.720> that's<00:04:59.290> why<00:04:59.530> augur<00:04:59.770> is 00:04:59.940 --> 00:04:59.950 align:start position:0% window before that's why augur is 00:04:59.950 --> 00:05:02.040 align:start position:0% window before that's why augur is presented<00:05:00.340> as<00:05:00.430> an<00:05:00.550> executable<00:05:00.970> because<00:05:01.780> this 00:05:02.040 --> 00:05:02.050 align:start position:0% presented as an executable because this 00:05:02.050 --> 00:05:04.290 align:start position:0% presented as an executable because this service<00:05:02.470> that<00:05:02.620> powers<00:05:02.890> the<00:05:02.980> UI<00:05:03.130> is<00:05:03.700> critical 00:05:04.290 --> 00:05:04.300 align:start position:0% service that powers the UI is critical 00:05:04.300 --> 00:05:07.500 align:start position:0% service that powers the UI is critical for<00:05:04.540> its<00:05:04.690> functionality<00:05:06.120> and<00:05:07.120> so<00:05:07.240> why<00:05:07.330> do<00:05:07.390> we 00:05:07.500 --> 00:05:07.510 align:start position:0% for its functionality and so why do we 00:05:07.510 --> 00:05:09.330 align:start position:0% for its functionality and so why do we do<00:05:07.630> this<00:05:07.720> why<00:05:08.290> do<00:05:08.350> we<00:05:08.470> take<00:05:08.590> the<00:05:08.740> etherium 00:05:09.330 --> 00:05:09.340 align:start position:0% do this why do we take the etherium 00:05:09.340 --> 00:05:11.370 align:start position:0% do this why do we take the etherium database<00:05:09.700> and<00:05:10.000> turn<00:05:10.990> it<00:05:11.080> into<00:05:11.200> another 00:05:11.370 --> 00:05:11.380 align:start position:0% database and turn it into another 00:05:11.380 --> 00:05:14.120 align:start position:0% database and turn it into another database<00:05:11.890> so<00:05:12.820> we<00:05:12.910> get<00:05:13.030> a<00:05:13.060> few<00:05:13.180> features<00:05:13.510> here 00:05:14.120 --> 00:05:14.130 align:start position:0% database so we get a few features here 00:05:14.130 --> 00:05:17.460 align:start position:0% database so we get a few features here we<00:05:15.130> get<00:05:15.250> relational<00:05:15.730> data<00:05:15.960> the<00:05:16.960> augur<00:05:17.260> data 00:05:17.460 --> 00:05:17.470 align:start position:0% we get relational data the augur data 00:05:17.470 --> 00:05:20.100 align:start position:0% we get relational data the augur data model<00:05:17.800> is<00:05:17.950> fairly<00:05:18.400> complex<00:05:18.820> we<00:05:19.570> have<00:05:19.720> lots<00:05:20.020> of 00:05:20.100 --> 00:05:20.110 align:start position:0% model is fairly complex we have lots of 00:05:20.110 --> 00:05:21.060 align:start position:0% model is fairly complex we have lots of different<00:05:20.380> things<00:05:20.470> that<00:05:20.680> relate<00:05:20.890> to<00:05:20.920> each 00:05:21.060 --> 00:05:21.070 align:start position:0% different things that relate to each 00:05:21.070 --> 00:05:22.380 align:start position:0% different things that relate to each other<00:05:21.250> and<00:05:21.400> if<00:05:21.490> each<00:05:21.670> one<00:05:21.820> of<00:05:21.940> these<00:05:22.000> needed<00:05:22.330> to 00:05:22.380 --> 00:05:22.390 align:start position:0% other and if each one of these needed to 00:05:22.390 --> 00:05:24.240 align:start position:0% other and if each one of these needed to be<00:05:22.510> some<00:05:22.690> Eve<00:05:22.840> call<00:05:23.140> that<00:05:23.470> like<00:05:23.710> bled<00:05:23.950> to<00:05:24.070> some 00:05:24.240 --> 00:05:24.250 align:start position:0% be some Eve call that like bled to some 00:05:24.250 --> 00:05:26.130 align:start position:0% be some Eve call that like bled to some other<00:05:24.430> earth<00:05:24.640> call<00:05:24.880> this<00:05:25.390> could<00:05:25.570> be<00:05:25.690> dozens 00:05:26.130 --> 00:05:26.140 align:start position:0% other earth call this could be dozens 00:05:26.140 --> 00:05:27.990 align:start position:0% other earth call this could be dozens and<00:05:26.290> dozens<00:05:26.380> of<00:05:26.830> queries<00:05:27.220> just<00:05:27.250> to<00:05:27.640> look<00:05:27.790> up<00:05:27.910> a 00:05:27.990 --> 00:05:28.000 align:start position:0% and dozens of queries just to look up a 00:05:28.000 --> 00:05:29.880 align:start position:0% and dozens of queries just to look up a single<00:05:28.270> page<00:05:28.420> by<00:05:29.170> putting<00:05:29.440> this<00:05:29.500> into<00:05:29.770> an 00:05:29.880 --> 00:05:29.890 align:start position:0% single page by putting this into an 00:05:29.890 --> 00:05:31.560 align:start position:0% single page by putting this into an indexed<00:05:30.370> relational<00:05:30.790> database<00:05:31.120> we<00:05:31.300> can<00:05:31.420> serve 00:05:31.560 --> 00:05:31.570 align:start position:0% indexed relational database we can serve 00:05:31.570 --> 00:05:36.300 align:start position:0% indexed relational database we can serve that<00:05:31.600> with<00:05:31.840> a<00:05:31.870> simple<00:05:32.230> single<00:05:32.770> joint<00:05:33.400> query<00:05:35.310> we 00:05:36.300 --> 00:05:36.310 align:start position:0% that with a simple single joint query we 00:05:36.310 --> 00:05:38.220 align:start position:0% that with a simple single joint query we also<00:05:36.460> get<00:05:36.610> data<00:05:36.790> locality<00:05:37.090> no<00:05:37.810> matter<00:05:37.990> what 00:05:38.220 --> 00:05:38.230 align:start position:0% also get data locality no matter what 00:05:38.230 --> 00:05:39.930 align:start position:0% also get data locality no matter what your<00:05:38.380> latency<00:05:38.770> is<00:05:38.920> to<00:05:39.190> that<00:05:39.310> aetherium<00:05:39.730> node 00:05:39.930 --> 00:05:39.940 align:start position:0% your latency is to that aetherium node 00:05:39.940 --> 00:05:41.970 align:start position:0% your latency is to that aetherium node you<00:05:40.480> are<00:05:40.600> serving<00:05:40.960> this<00:05:41.020> data<00:05:41.260> local<00:05:41.590> it's<00:05:41.740> all 00:05:41.970 --> 00:05:41.980 align:start position:0% you are serving this data local it's all 00:05:41.980 --> 00:05:45.720 align:start position:0% you are serving this data local it's all ready<00:05:42.310> for<00:05:42.580> you<00:05:42.750> and<00:05:44.130> users<00:05:45.130> are<00:05:45.340> the<00:05:45.430> ones<00:05:45.580> who 00:05:45.720 --> 00:05:45.730 align:start position:0% ready for you and users are the ones who 00:05:45.730 --> 00:05:47.850 align:start position:0% ready for you and users are the ones who are<00:05:45.760> contributing<00:05:46.390> the<00:05:46.690> titles<00:05:47.140> for<00:05:47.560> these 00:05:47.850 --> 00:05:47.860 align:start position:0% are contributing the titles for these 00:05:47.860 --> 00:05:50.490 align:start position:0% are contributing the titles for these markets<00:05:48.280> and<00:05:48.490> outcomes<00:05:48.880> and<00:05:49.180> whenever<00:05:50.140> users 00:05:50.490 --> 00:05:50.500 align:start position:0% markets and outcomes and whenever users 00:05:50.500 --> 00:05:51.720 align:start position:0% markets and outcomes and whenever users are<00:05:50.770> entering<00:05:51.040> text<00:05:51.340> you're<00:05:51.430> going<00:05:51.460> to<00:05:51.610> need<00:05:51.700> a 00:05:51.720 --> 00:05:51.730 align:start position:0% are entering text you're going to need a 00:05:51.730 --> 00:05:53.100 align:start position:0% are entering text you're going to need a good<00:05:51.940> way<00:05:52.090> to<00:05:52.150> find<00:05:52.510> that<00:05:52.660> text<00:05:52.960> something 00:05:53.100 --> 00:05:53.110 align:start position:0% good way to find that text something 00:05:53.110 --> 00:05:54.690 align:start position:0% good way to find that text something that's<00:05:53.320> not<00:05:53.410> exactly<00:05:53.920> accurate<00:05:54.130> so<00:05:54.460> we<00:05:54.490> have 00:05:54.690 --> 00:05:54.700 align:start position:0% that's not exactly accurate so we have 00:05:54.700 --> 00:05:56.880 align:start position:0% that's not exactly accurate so we have string<00:05:55.330> matching<00:05:55.750> and<00:05:55.900> search<00:05:56.200> patterns<00:05:56.650> that 00:05:56.880 --> 00:05:56.890 align:start position:0% string matching and search patterns that 00:05:56.890 --> 00:06:00.450 align:start position:0% string matching and search patterns that that<00:05:57.310> help<00:05:57.580> with<00:05:57.730> this<00:05:57.820> discovery<00:05:59.460> but 00:06:00.450 --> 00:06:00.460 align:start position:0% that help with this discovery but 00:06:00.460 --> 00:06:03.510 align:start position:0% that help with this discovery but there's<00:06:00.640> another<00:06:00.760> reason<00:06:00.970> I<00:06:02.490> mentioned<00:06:03.490> that 00:06:03.510 --> 00:06:03.520 align:start position:0% there's another reason I mentioned that 00:06:03.520 --> 00:06:06.240 align:start position:0% there's another reason I mentioned that there<00:06:03.670> were<00:06:03.730> 41<00:06:04.120> based<00:06:04.570> contracts<00:06:05.170> but<00:06:06.070> that's 00:06:06.240 --> 00:06:06.250 align:start position:0% there were 41 based contracts but that's 00:06:06.250 --> 00:06:09.150 align:start position:0% there were 41 based contracts but that's just<00:06:06.370> where<00:06:06.490> it<00:06:06.550> starts<00:06:07.770> when<00:06:08.770> you<00:06:08.860> create<00:06:09.130> a 00:06:09.150 --> 00:06:09.160 align:start position:0% just where it starts when you create a 00:06:09.160 --> 00:06:11.490 align:start position:0% just where it starts when you create a new<00:06:09.190> market<00:06:09.610> that<00:06:09.820> is<00:06:10.180> a<00:06:10.210> new<00:06:10.360> contract<00:06:10.810> plus 00:06:11.490 --> 00:06:11.500 align:start position:0% new market that is a new contract plus 00:06:11.500 --> 00:06:13.230 align:start position:0% new market that is a new contract plus you're<00:06:11.680> gonna<00:06:11.770> have<00:06:11.980> two<00:06:12.550> to<00:06:12.670> eight<00:06:12.790> outcome 00:06:13.230 --> 00:06:13.240 align:start position:0% you're gonna have two to eight outcome 00:06:13.240 --> 00:06:16.320 align:start position:0% you're gonna have two to eight outcome token<00:06:13.630> contracts<00:06:14.700> you<00:06:15.700> provided<00:06:16.120> in<00:06:16.210> an 00:06:16.320 --> 00:06:16.330 align:start position:0% token contracts you provided in an 00:06:16.330 --> 00:06:19.530 align:start position:0% token contracts you provided in an initial<00:06:16.750> report<00:06:17.020> that<00:06:17.290> is<00:06:17.830> a<00:06:17.860> contract<00:06:18.540> when 00:06:19.530 --> 00:06:19.540 align:start position:0% initial report that is a contract when 00:06:19.540 --> 00:06:21.750 align:start position:0% initial report that is a contract when you<00:06:19.630> provide<00:06:19.960> a<00:06:20.170> dispute<00:06:20.650> that<00:06:21.460> is<00:06:21.580> a<00:06:21.610> new 00:06:21.750 --> 00:06:21.760 align:start position:0% you provide a dispute that is a new 00:06:21.760 --> 00:06:25.200 align:start position:0% you provide a dispute that is a new contract<00:06:22.240> has<00:06:22.870> a<00:06:22.900> week<00:06:23.380> past<00:06:23.970> that<00:06:24.970> is<00:06:25.180> a 00:06:25.200 --> 00:06:25.210 align:start position:0% contract has a week past that is a 00:06:25.210 --> 00:06:28.800 align:start position:0% contract has a week past that is a contract<00:06:25.720> it's<00:06:26.050> called<00:06:26.230> a<00:06:26.320> fee<00:06:26.470> window<00:06:27.690> and<00:06:28.690> so 00:06:28.800 --> 00:06:28.810 align:start position:0% contract it's called a fee window and so 00:06:28.810 --> 00:06:30.120 align:start position:0% contract it's called a fee window and so this<00:06:28.960> chart<00:06:29.230> from<00:06:29.320> before<00:06:29.650> where<00:06:29.890> we<00:06:29.950> talked 00:06:30.120 --> 00:06:30.130 align:start position:0% this chart from before where we talked 00:06:30.130 --> 00:06:31.980 align:start position:0% this chart from before where we talked about<00:06:30.220> the<00:06:30.400> 41<00:06:30.850> contracts<00:06:31.540> that<00:06:31.720> make<00:06:31.870> up 00:06:31.980 --> 00:06:31.990 align:start position:0% about the 41 contracts that make up 00:06:31.990 --> 00:06:34.920 align:start position:0% about the 41 contracts that make up augur<00:06:32.200> is<00:06:32.950> dwarfed<00:06:33.580> by<00:06:34.420> the<00:06:34.480> number<00:06:34.810> of 00:06:34.920 --> 00:06:34.930 align:start position:0% augur is dwarfed by the number of 00:06:34.930 --> 00:06:36.630 align:start position:0% augur is dwarfed by the number of contracts<00:06:35.410> that<00:06:35.500> have<00:06:35.620> been<00:06:35.800> deployed<00:06:36.010> since 00:06:36.630 --> 00:06:36.640 align:start position:0% contracts that have been deployed since 00:06:36.640 --> 00:06:39.250 align:start position:0% contracts that have been deployed since its<00:06:36.790> launch<00:06:36.940> which<00:06:37.540> sits<00:06:37.780> at<00:06:37.840> over<00:06:38.050> 5,000 00:06:39.250 --> 00:06:39.260 align:start position:0% its launch which sits at over 5,000 00:06:39.260 --> 00:06:43.930 align:start position:0% its launch which sits at over 5,000 auger<00:06:40.250> is<00:06:40.940> also<00:06:41.390> a<00:06:41.600> fairly<00:06:41.960> old<00:06:42.200> project<00:06:43.070> we're 00:06:43.930 --> 00:06:43.940 align:start position:0% auger is also a fairly old project we're 00:06:43.940 --> 00:06:46.560 align:start position:0% auger is also a fairly old project we're currently<00:06:44.090> sitting<00:06:44.330> at<00:06:44.510> blocked<00:06:44.750> 6.6<00:06:45.500> million 00:06:46.560 --> 00:06:46.570 align:start position:0% currently sitting at blocked 6.6 million 00:06:46.570 --> 00:06:50.140 align:start position:0% currently sitting at blocked 6.6 million the<00:06:47.570> release<00:06:47.810> took<00:06:47.990> place<00:06:48.140> around<00:06:48.380> 5.9<00:06:49.150> by 00:06:50.140 --> 00:06:50.150 align:start position:0% the release took place around 5.9 by 00:06:50.150 --> 00:06:52.840 align:start position:0% the release took place around 5.9 by involvement<00:06:50.660> 4.4<00:06:51.400> but<00:06:52.400> if<00:06:52.490> you<00:06:52.580> want<00:06:52.730> to<00:06:52.790> go 00:06:52.840 --> 00:06:52.850 align:start position:0% involvement 4.4 but if you want to go 00:06:52.850 --> 00:06:55.900 align:start position:0% involvement 4.4 but if you want to go back<00:06:53.000> to<00:06:53.210> that<00:06:53.330> very<00:06:53.750> first<00:06:54.160> auger<00:06:55.160> contract 00:06:55.900 --> 00:06:55.910 align:start position:0% back to that very first auger contract 00:06:55.910 --> 00:06:58.000 align:start position:0% back to that very first auger contract deployment<00:06:56.420> the<00:06:57.290> first<00:06:57.530> time<00:06:57.740> that<00:06:57.860> somebody 00:06:58.000 --> 00:06:58.010 align:start position:0% deployment the first time that somebody 00:06:58.010 --> 00:06:59.230 align:start position:0% deployment the first time that somebody said<00:06:58.250> I<00:06:58.370> would<00:06:58.490> like<00:06:58.580> to<00:06:58.700> make<00:06:58.820> something<00:06:59.060> like 00:06:59.230 --> 00:06:59.240 align:start position:0% said I would like to make something like 00:06:59.240 --> 00:07:02.020 align:start position:0% said I would like to make something like auger<00:06:59.480> and<00:06:59.840> deploy<00:07:00.140> it<00:07:00.230> to<00:07:00.260> the<00:07:00.380> network<00:07:01.030> need 00:07:02.020 --> 00:07:02.030 align:start position:0% auger and deploy it to the network need 00:07:02.030 --> 00:07:04.810 align:start position:0% auger and deploy it to the network need to<00:07:02.120> go<00:07:02.210> before<00:07:02.360> block<00:07:02.690> zero<00:07:03.340> this<00:07:04.340> system<00:07:04.700> was 00:07:04.810 --> 00:07:04.820 align:start position:0% to go before block zero this system was 00:07:04.820 --> 00:07:07.390 align:start position:0% to go before block zero this system was developed<00:07:05.030> well<00:07:06.020> before<00:07:06.440> the<00:07:06.740> etherium<00:07:07.190> main 00:07:07.390 --> 00:07:07.400 align:start position:0% developed well before the etherium main 00:07:07.400 --> 00:07:09.670 align:start position:0% developed well before the etherium main net<00:07:07.610> block<00:07:07.850> zero<00:07:08.150> was<00:07:08.360> launched<00:07:08.750> on<00:07:08.900> a<00:07:08.990> test 00:07:09.670 --> 00:07:09.680 align:start position:0% net block zero was launched on a test 00:07:09.680 --> 00:07:13.090 align:start position:0% net block zero was launched on a test network<00:07:10.300> that<00:07:11.300> I<00:07:12.230> think<00:07:12.680> at<00:07:12.740> the<00:07:12.800> time<00:07:12.950> was 00:07:13.090 --> 00:07:13.100 align:start position:0% network that I think at the time was 00:07:13.100 --> 00:07:16.900 align:start position:0% network that I think at the time was called<00:07:13.220> POC<00:07:13.880> nine<00:07:15.340> but<00:07:16.340> this<00:07:16.460> is<00:07:16.580> actually 00:07:16.900 --> 00:07:16.910 align:start position:0% called POC nine but this is actually 00:07:16.910 --> 00:07:19.690 align:start position:0% called POC nine but this is actually before<00:07:17.390> solidity<00:07:17.950> solidity<00:07:18.950> zero<00:07:19.310> point<00:07:19.550> one 00:07:19.690 --> 00:07:19.700 align:start position:0% before solidity solidity zero point one 00:07:19.700 --> 00:07:21.550 align:start position:0% before solidity solidity zero point one point<00:07:19.850> zero<00:07:20.120> was<00:07:20.270> released<00:07:20.510> here<00:07:20.780> and<00:07:21.020> so 00:07:21.550 --> 00:07:21.560 align:start position:0% point zero was released here and so 00:07:21.560 --> 00:07:23.620 align:start position:0% point zero was released here and so these<00:07:21.710> contracts<00:07:22.280> were<00:07:22.580> written<00:07:22.760> in<00:07:23.060> serpent 00:07:23.620 --> 00:07:23.630 align:start position:0% these contracts were written in serpent 00:07:23.630 --> 00:07:26.320 align:start position:0% these contracts were written in serpent a<00:07:23.870> different<00:07:24.710> smart<00:07:25.040> contract<00:07:25.520> language<00:07:25.730> that 00:07:26.320 --> 00:07:26.330 align:start position:0% a different smart contract language that 00:07:26.330 --> 00:07:29.740 align:start position:0% a different smart contract language that compiles<00:07:26.690> down<00:07:26.810> to<00:07:26.960> the<00:07:27.020> EVM<00:07:27.350> code<00:07:28.660> so<00:07:29.660> when 00:07:29.740 --> 00:07:29.750 align:start position:0% compiles down to the EVM code so when 00:07:29.750 --> 00:07:31.780 align:start position:0% compiles down to the EVM code so when the<00:07:29.810> rep<00:07:29.960> token<00:07:30.320> launched<00:07:30.800> around<00:07:31.040> block<00:07:31.190> 2.4 00:07:31.780 --> 00:07:31.790 align:start position:0% the rep token launched around block 2.4 00:07:31.790 --> 00:07:33.910 align:start position:0% the rep token launched around block 2.4 million<00:07:32.000> this<00:07:32.720> token<00:07:33.020> was<00:07:33.110> also<00:07:33.410> written<00:07:33.740> in 00:07:33.910 --> 00:07:33.920 align:start position:0% million this token was also written in 00:07:33.920 --> 00:07:36.400 align:start position:0% million this token was also written in serpent<00:07:34.310> and<00:07:34.460> work<00:07:35.360> got<00:07:35.630> underway<00:07:35.990> to<00:07:36.260> develop 00:07:36.400 --> 00:07:36.410 align:start position:0% serpent and work got underway to develop 00:07:36.410 --> 00:07:38.650 align:start position:0% serpent and work got underway to develop the<00:07:36.890> augur<00:07:37.070> contracts<00:07:37.640> in<00:07:37.880> this<00:07:38.420> other 00:07:38.650 --> 00:07:38.660 align:start position:0% the augur contracts in this other 00:07:38.660 --> 00:07:43.540 align:start position:0% the augur contracts in this other language<00:07:39.170> serpent<00:07:41.920> unfortunately<00:07:42.920> around 00:07:43.540 --> 00:07:43.550 align:start position:0% language serpent unfortunately around 00:07:43.550 --> 00:07:46.390 align:start position:0% language serpent unfortunately around block<00:07:44.180> 4.1<00:07:44.750> million<00:07:44.960> we<00:07:45.590> asked<00:07:45.920> Zeb<00:07:46.130> Glenn<00:07:46.310> to 00:07:46.390 --> 00:07:46.400 align:start position:0% block 4.1 million we asked Zeb Glenn to 00:07:46.400 --> 00:07:47.830 align:start position:0% block 4.1 million we asked Zeb Glenn to take<00:07:46.550> a<00:07:46.580> look<00:07:46.790> and<00:07:46.910> that<00:07:47.000> how's<00:07:47.390> us<00:07:47.540> to<00:07:47.630> a<00:07:47.660> house 00:07:47.830 --> 00:07:47.840 align:start position:0% take a look and that how's us to a house 00:07:47.840 --> 00:07:49.960 align:start position:0% take a look and that how's us to a house serpent<00:07:48.260> going<00:07:48.530> we<00:07:49.160> had<00:07:49.280> them<00:07:49.430> both<00:07:49.670> look<00:07:49.880> at 00:07:49.960 --> 00:07:49.970 align:start position:0% serpent going we had them both look at 00:07:49.970 --> 00:07:51.640 align:start position:0% serpent going we had them both look at our<00:07:50.060> smart<00:07:50.330> contracts<00:07:50.750> and<00:07:50.990> the<00:07:51.290> serpent 00:07:51.640 --> 00:07:51.650 align:start position:0% our smart contracts and the serpent 00:07:51.650 --> 00:07:55.000 align:start position:0% our smart contracts and the serpent compiler<00:07:52.160> and<00:07:52.570> what<00:07:53.570> they<00:07:53.660> discovered<00:07:54.140> was 00:07:55.000 --> 00:07:55.010 align:start position:0% compiler and what they discovered was 00:07:55.010 --> 00:07:56.650 align:start position:0% compiler and what they discovered was that<00:07:55.040> the<00:07:55.220> circ<00:07:55.400> of<00:07:55.520> a<00:07:55.580> serpent<00:07:55.910> compiler<00:07:56.360> had 00:07:56.650 --> 00:07:56.660 align:start position:0% that the circ of a serpent compiler had 00:07:56.660 --> 00:07:59.620 align:start position:0% that the circ of a serpent compiler had a<00:07:56.690> critical<00:07:57.410> vulnerability<00:07:58.250> in<00:07:58.340> it<00:07:58.570> wasn't<00:07:59.570> an 00:07:59.620 --> 00:07:59.630 align:start position:0% a critical vulnerability in it wasn't an 00:07:59.630 --> 00:08:01.000 align:start position:0% a critical vulnerability in it wasn't an issue<00:07:59.750> with<00:07:59.930> the<00:08:00.020> smart<00:08:00.260> contract<00:08:00.650> code<00:08:00.800> but 00:08:01.000 --> 00:08:01.010 align:start position:0% issue with the smart contract code but 00:08:01.010 --> 00:08:02.680 align:start position:0% issue with the smart contract code but even<00:08:01.310> the<00:08:01.460> rep<00:08:01.670> token<00:08:02.060> itself<00:08:02.300> that<00:08:02.480> had<00:08:02.570> been 00:08:02.680 --> 00:08:02.690 align:start position:0% even the rep token itself that had been 00:08:02.690 --> 00:08:05.530 align:start position:0% even the rep token itself that had been deployed<00:08:02.990> was<00:08:03.620> vulnerable<00:08:04.400> to<00:08:04.610> a<00:08:04.790> VM<00:08:05.240> code 00:08:05.530 --> 00:08:05.540 align:start position:0% deployed was vulnerable to a VM code 00:08:05.540 --> 00:08:09.220 align:start position:0% deployed was vulnerable to a VM code that<00:08:06.050> came<00:08:06.200> out<00:08:06.440> of<00:08:06.530> the<00:08:06.620> compiler<00:08:07.070> and<00:08:07.510> so<00:08:08.510> the 00:08:09.220 --> 00:08:09.230 align:start position:0% that came out of the compiler and so the 00:08:09.230 --> 00:08:10.870 align:start position:0% that came out of the compiler and so the rep<00:08:09.380> token<00:08:09.710> had<00:08:09.980> to<00:08:10.100> get<00:08:10.250> redeployed<00:08:10.670> at<00:08:10.760> this 00:08:10.870 --> 00:08:10.880 align:start position:0% rep token had to get redeployed at this 00:08:10.880 --> 00:08:12.040 align:start position:0% rep token had to get redeployed at this point<00:08:11.120> it<00:08:11.270> was<00:08:11.360> really<00:08:11.420> written<00:08:11.900> as<00:08:12.020> a 00:08:12.040 --> 00:08:12.050 align:start position:0% point it was really written as a 00:08:12.050 --> 00:08:14.470 align:start position:0% point it was really written as a solidity<00:08:12.530> contract<00:08:13.040> and<00:08:13.280> all<00:08:13.880> of<00:08:14.150> the<00:08:14.210> augur 00:08:14.470 --> 00:08:14.480 align:start position:0% solidity contract and all of the augur 00:08:14.480 --> 00:08:16.030 align:start position:0% solidity contract and all of the augur contracts<00:08:14.930> that<00:08:15.110> were<00:08:15.230> already<00:08:15.620> ready<00:08:15.830> for 00:08:16.030 --> 00:08:16.040 align:start position:0% contracts that were already ready for 00:08:16.040 --> 00:08:17.620 align:start position:0% contracts that were already ready for audits<00:08:16.340> had<00:08:16.760> to<00:08:16.850> get<00:08:16.970> rewritten<00:08:17.330> into 00:08:17.620 --> 00:08:17.630 align:start position:0% audits had to get rewritten into 00:08:17.630 --> 00:08:19.570 align:start position:0% audits had to get rewritten into solidity<00:08:18.200> because<00:08:18.500> it<00:08:18.980> was<00:08:19.100> clear<00:08:19.370> that<00:08:19.400> the 00:08:19.570 --> 00:08:19.580 align:start position:0% solidity because it was clear that the 00:08:19.580 --> 00:08:21.520 align:start position:0% solidity because it was clear that the market<00:08:19.850> had<00:08:19.940> really<00:08:20.150> gone<00:08:20.270> this<00:08:20.330> way<00:08:20.630> and<00:08:20.840> this 00:08:21.520 --> 00:08:21.530 align:start position:0% market had really gone this way and this 00:08:21.530 --> 00:08:25.840 align:start position:0% market had really gone this way and this research<00:08:21.860> really<00:08:22.120> justified<00:08:23.120> that<00:08:23.270> effort<00:08:24.850> so 00:08:25.840 --> 00:08:25.850 align:start position:0% research really justified that effort so 00:08:25.850 --> 00:08:28.030 align:start position:0% research really justified that effort so your<00:08:26.090> smart<00:08:26.360> contract<00:08:26.780> is<00:08:26.930> no<00:08:27.290> more<00:08:27.560> secure 00:08:28.030 --> 00:08:28.040 align:start position:0% your smart contract is no more secure 00:08:28.040 --> 00:08:30.970 align:start position:0% your smart contract is no more secure than<00:08:28.430> your<00:08:28.460> compiler<00:08:29.440> which<00:08:30.440> is<00:08:30.560> why<00:08:30.650> we<00:08:30.860> were 00:08:30.970 --> 00:08:30.980 align:start position:0% than your compiler which is why we were 00:08:30.980 --> 00:08:32.830 align:start position:0% than your compiler which is why we were proud<00:08:31.160> to<00:08:31.190> release<00:08:31.430> yesterday<00:08:31.730> a<00:08:32.150> joint 00:08:32.830 --> 00:08:32.840 align:start position:0% proud to release yesterday a joint 00:08:32.840 --> 00:08:34.750 align:start position:0% proud to release yesterday a joint effort<00:08:33.200> between<00:08:33.440> auger<00:08:34.099> and<00:08:34.250> the<00:08:34.340> etherium 00:08:34.750 --> 00:08:34.760 align:start position:0% effort between auger and the etherium 00:08:34.760 --> 00:08:38.339 align:start position:0% effort between auger and the etherium foundation<00:08:35.300> for<00:08:35.900> a<00:08:35.930> solidity<00:08:36.890> compiler<00:08:37.460> audit 00:08:38.339 --> 00:08:38.349 align:start position:0% foundation for a solidity compiler audit 00:08:38.349 --> 00:08:40.390 align:start position:0% foundation for a solidity compiler audit and<00:08:39.349> they<00:08:39.440> found<00:08:39.560> some<00:08:39.740> great<00:08:39.890> stuff<00:08:39.919> they<00:08:40.250> had 00:08:40.390 --> 00:08:40.400 align:start position:0% and they found some great stuff they had 00:08:40.400 --> 00:08:43.330 align:start position:0% and they found some great stuff they had over<00:08:40.780> 12<00:08:41.780> with<00:08:41.960> they<00:08:42.050> had<00:08:42.140> 12<00:08:42.320> issues<00:08:42.620> that 00:08:43.330 --> 00:08:43.340 align:start position:0% over 12 with they had 12 issues that 00:08:43.340 --> 00:08:45.810 align:start position:0% over 12 with they had 12 issues that they<00:08:43.520> consider<00:08:43.849> to<00:08:43.910> be<00:08:44.150> high<00:08:44.570> or<00:08:44.900> critical<00:08:44.930> and 00:08:45.810 --> 00:08:45.820 align:start position:0% they consider to be high or critical and 00:08:45.820 --> 00:08:48.160 align:start position:0% they consider to be high or critical and these<00:08:46.820> issues<00:08:47.120> are<00:08:47.330> as<00:08:47.750> some<00:08:47.870> of<00:08:47.930> them<00:08:48.050> have 00:08:48.160 --> 00:08:48.170 align:start position:0% these issues are as some of them have 00:08:48.170 --> 00:08:49.210 align:start position:0% these issues are as some of them have been<00:08:48.260> addressed<00:08:48.620> some<00:08:48.770> of<00:08:48.830> them<00:08:48.950> will<00:08:49.100> be 00:08:49.210 --> 00:08:49.220 align:start position:0% been addressed some of them will be 00:08:49.220 --> 00:08:50.740 align:start position:0% been addressed some of them will be addressed<00:08:49.550> but<00:08:50.000> luckily<00:08:50.180> none<00:08:50.480> of<00:08:50.510> these 00:08:50.740 --> 00:08:50.750 align:start position:0% addressed but luckily none of these 00:08:50.750 --> 00:08:52.570 align:start position:0% addressed but luckily none of these created<00:08:51.470> EVM<00:08:51.890> code 00:08:52.570 --> 00:08:52.580 align:start position:0% created EVM code 00:08:52.580 --> 00:08:54.700 align:start position:0% created EVM code left<00:08:52.820> our<00:08:53.060> contracts<00:08:53.660> vulnerable<00:08:54.140> but<00:08:54.620> we 00:08:54.700 --> 00:08:54.710 align:start position:0% left our contracts vulnerable but we 00:08:54.710 --> 00:08:56.680 align:start position:0% left our contracts vulnerable but we feel<00:08:54.920> a<00:08:55.070> lot<00:08:55.310> better<00:08:55.490> about<00:08:55.820> the<00:08:56.270> platform 00:08:56.680 --> 00:08:56.690 align:start position:0% feel a lot better about the platform 00:08:56.690 --> 00:08:57.850 align:start position:0% feel a lot better about the platform that<00:08:56.780> we<00:08:56.840> are<00:08:56.960> leaving<00:08:57.110> behind<00:08:57.260> for<00:08:57.620> other 00:08:57.850 --> 00:08:57.860 align:start position:0% that we are leaving behind for other 00:08:57.860 --> 00:09:03.670 align:start position:0% that we are leaving behind for other developers<00:08:58.370> to<00:08:58.400> build<00:08:58.670> upon<00:09:02.560> one<00:09:03.560> of<00:09:03.590> the 00:09:03.670 --> 00:09:03.680 align:start position:0% developers to build upon one of the 00:09:03.680 --> 00:09:05.170 align:start position:0% developers to build upon one of the issues<00:09:03.860> we<00:09:03.980> ran<00:09:04.070> sue<00:09:04.310> was<00:09:04.430> a<00:09:04.460> test<00:09:04.760> net<00:09:04.970> gas 00:09:05.170 --> 00:09:05.180 align:start position:0% issues we ran sue was a test net gas 00:09:05.180 --> 00:09:07.840 align:start position:0% issues we ran sue was a test net gas limit<00:09:05.390> issue<00:09:05.800> so<00:09:06.800> I<00:09:06.830> mentioned<00:09:07.190> we<00:09:07.250> have<00:09:07.400> 41 00:09:07.840 --> 00:09:07.850 align:start position:0% limit issue so I mentioned we have 41 00:09:07.850 --> 00:09:09.700 align:start position:0% limit issue so I mentioned we have 41 contracts<00:09:08.420> and<00:09:08.630> those<00:09:08.720> take<00:09:08.900> 50<00:09:09.320> million<00:09:09.590> gas 00:09:09.700 --> 00:09:09.710 align:start position:0% contracts and those take 50 million gas 00:09:09.710 --> 00:09:13.270 align:start position:0% contracts and those take 50 million gas to<00:09:09.920> deploy<00:09:10.160> but<00:09:11.440> one<00:09:12.440> of<00:09:12.530> these<00:09:12.680> contracts<00:09:13.190> the 00:09:13.270 --> 00:09:13.280 align:start position:0% to deploy but one of these contracts the 00:09:13.280 --> 00:09:16.990 align:start position:0% to deploy but one of these contracts the largest<00:09:13.670> of<00:09:13.760> them<00:09:13.910> takes<00:09:14.630> 5.8<00:09:15.140> million<00:09:16.000> which 00:09:16.990 --> 00:09:17.000 align:start position:0% largest of them takes 5.8 million which 00:09:17.000 --> 00:09:18.340 align:start position:0% largest of them takes 5.8 million which isn't<00:09:17.210> a<00:09:17.270> problem<00:09:17.420> for<00:09:17.570> maintenance<00:09:17.990> may<00:09:18.140> net 00:09:18.340 --> 00:09:18.350 align:start position:0% isn't a problem for maintenance may net 00:09:18.350 --> 00:09:21.900 align:start position:0% isn't a problem for maintenance may net has<00:09:18.590> a<00:09:18.620> block<00:09:19.160> gas<00:09:19.520> limit<00:09:19.820> of<00:09:20.030> eight<00:09:20.240> million 00:09:21.900 --> 00:09:21.910 align:start position:0% has a block gas limit of eight million 00:09:21.910 --> 00:09:24.340 align:start position:0% has a block gas limit of eight million robson<00:09:22.910> however<00:09:23.360> which<00:09:23.660> is<00:09:23.690> one<00:09:23.900> of<00:09:23.930> our<00:09:24.050> main 00:09:24.340 --> 00:09:24.350 align:start position:0% robson however which is one of our main 00:09:24.350 --> 00:09:26.380 align:start position:0% robson however which is one of our main test<00:09:24.650> networks<00:09:25.010> for<00:09:25.760> developments<00:09:26.240> at<00:09:26.360> the 00:09:26.380 --> 00:09:26.390 align:start position:0% test networks for developments at the 00:09:26.390 --> 00:09:29.410 align:start position:0% test networks for developments at the time<00:09:26.660> had<00:09:27.560> a<00:09:27.590> block<00:09:27.950> gas<00:09:28.310> limit<00:09:28.520> of<00:09:28.730> 4.7 00:09:29.410 --> 00:09:29.420 align:start position:0% time had a block gas limit of 4.7 00:09:29.420 --> 00:09:31.570 align:start position:0% time had a block gas limit of 4.7 million<00:09:29.600> it<00:09:29.840> could<00:09:29.930> not<00:09:30.380> contain<00:09:30.770> that<00:09:31.250> one 00:09:31.570 --> 00:09:31.580 align:start position:0% million it could not contain that one 00:09:31.580 --> 00:09:33.910 align:start position:0% million it could not contain that one transaction<00:09:32.000> to<00:09:32.750> deploy<00:09:33.020> the<00:09:33.530> largest 00:09:33.910 --> 00:09:33.920 align:start position:0% transaction to deploy the largest 00:09:33.920 --> 00:09:35.350 align:start position:0% transaction to deploy the largest contract<00:09:34.310> which<00:09:34.610> was<00:09:34.760> critical<00:09:35.180> for<00:09:35.330> our 00:09:35.350 --> 00:09:35.360 align:start position:0% contract which was critical for our 00:09:35.360 --> 00:09:39.490 align:start position:0% contract which was critical for our system<00:09:36.730> here's<00:09:37.730> a<00:09:37.790> chart<00:09:38.000> of<00:09:38.120> the<00:09:38.840> block<00:09:39.290> gas 00:09:39.490 --> 00:09:39.500 align:start position:0% system here's a chart of the block gas 00:09:39.500 --> 00:09:42.670 align:start position:0% system here's a chart of the block gas limit<00:09:39.740> over<00:09:40.070> the<00:09:40.160> last<00:09:40.340> two<00:09:40.760> years<00:09:41.530> you<00:09:42.530> can 00:09:42.670 --> 00:09:42.680 align:start position:0% limit over the last two years you can 00:09:42.680 --> 00:09:45.550 align:start position:0% limit over the last two years you can see<00:09:42.830> for<00:09:43.040> large<00:09:43.340> periods<00:09:43.790> of<00:09:43.880> time<00:09:44.090> blue<00:09:44.990> main 00:09:45.550 --> 00:09:45.560 align:start position:0% see for large periods of time blue main 00:09:45.560 --> 00:09:48.490 align:start position:0% see for large periods of time blue main net<00:09:45.800> could<00:09:46.250> host<00:09:46.520> large<00:09:47.150> contracts<00:09:47.780> but<00:09:48.350> there 00:09:48.490 --> 00:09:48.500 align:start position:0% net could host large contracts but there 00:09:48.500 --> 00:09:49.810 align:start position:0% net could host large contracts but there was<00:09:48.620> no<00:09:48.860> test<00:09:49.190> network<00:09:49.460> where<00:09:49.610> you<00:09:49.670> could 00:09:49.810 --> 00:09:49.820 align:start position:0% was no test network where you could 00:09:49.820 --> 00:09:51.370 align:start position:0% was no test network where you could actually<00:09:50.030> deploy<00:09:50.540> these<00:09:50.750> and<00:09:50.960> try<00:09:51.110> them<00:09:51.290> out 00:09:51.370 --> 00:09:51.380 align:start position:0% actually deploy these and try them out 00:09:51.380 --> 00:09:52.740 align:start position:0% actually deploy these and try them out and<00:09:51.440> share<00:09:51.770> them<00:09:51.950> with<00:09:51.980> the<00:09:52.070> world 00:09:52.740 --> 00:09:52.750 align:start position:0% and share them with the world 00:09:52.750 --> 00:09:55.840 align:start position:0% and share them with the world so<00:09:53.750> while<00:09:53.930> Rob's<00:09:54.200> turn<00:09:54.410> in<00:09:54.560> main<00:09:54.740> net<00:09:54.950> run<00:09:55.670> the 00:09:55.840 --> 00:09:55.850 align:start position:0% so while Rob's turn in main net run the 00:09:55.850 --> 00:09:59.160 align:start position:0% so while Rob's turn in main net run the same<00:09:56.030> code<00:09:56.710> there's<00:09:57.710> a<00:09:57.770> critical<00:09:58.070> difference 00:09:59.160 --> 00:09:59.170 align:start position:0% same code there's a critical difference 00:09:59.170 --> 00:10:02.350 align:start position:0% same code there's a critical difference Robson<00:10:00.170> isn't<00:10:00.410> used<00:10:00.620> as<00:10:00.770> much<00:10:00.950> and<00:10:01.360> miners 00:10:02.350 --> 00:10:02.360 align:start position:0% Robson isn't used as much and miners 00:10:02.360 --> 00:10:05.140 align:start position:0% Robson isn't used as much and miners look<00:10:02.750> to<00:10:02.960> how<00:10:03.170> full<00:10:03.530> of<00:10:03.560> block<00:10:03.830> is<00:10:04.040> to<00:10:04.550> slightly 00:10:05.140 --> 00:10:05.150 align:start position:0% look to how full of block is to slightly 00:10:05.150 --> 00:10:07.480 align:start position:0% look to how full of block is to slightly increase<00:10:05.390> or<00:10:05.870> slightly<00:10:06.320> decrease<00:10:06.770> the<00:10:07.250> block 00:10:07.480 --> 00:10:07.490 align:start position:0% increase or slightly decrease the block 00:10:07.490 --> 00:10:09.760 align:start position:0% increase or slightly decrease the block gas<00:10:07.820> limit<00:10:08.180> for<00:10:08.360> the<00:10:08.450> next<00:10:08.660> block<00:10:08.840> it's<00:10:09.560> up<00:10:09.680> to 00:10:09.760 --> 00:10:09.770 align:start position:0% gas limit for the next block it's up to 00:10:09.770 --> 00:10:11.050 align:start position:0% gas limit for the next block it's up to them<00:10:09.890> they<00:10:10.040> don't<00:10:10.100> have<00:10:10.340> to<00:10:10.520> use<00:10:10.670> this<00:10:10.850> as 00:10:11.050 --> 00:10:11.060 align:start position:0% them they don't have to use this as 00:10:11.060 --> 00:10:13.120 align:start position:0% them they don't have to use this as their<00:10:11.450> their<00:10:11.840> criteria<00:10:12.320> but<00:10:12.800> it's<00:10:12.890> what<00:10:13.040> they 00:10:13.120 --> 00:10:13.130 align:start position:0% their their criteria but it's what they 00:10:13.130 --> 00:10:16.420 align:start position:0% their their criteria but it's what they generally<00:10:13.610> do<00:10:14.320> so<00:10:15.320> what's<00:10:15.860> a<00:10:15.920> project<00:10:16.250> to<00:10:16.310> do 00:10:16.420 --> 00:10:16.430 align:start position:0% generally do so what's a project to do 00:10:16.430 --> 00:10:19.060 align:start position:0% generally do so what's a project to do when<00:10:16.550> they<00:10:16.640> want<00:10:16.790> to<00:10:16.850> ship<00:10:17.000> to<00:10:17.090> Robson<00:10:18.070> well 00:10:19.060 --> 00:10:19.070 align:start position:0% when they want to ship to Robson well 00:10:19.070 --> 00:10:20.280 align:start position:0% when they want to ship to Robson well just<00:10:19.250> fill<00:10:19.370> up<00:10:19.460> the<00:10:19.490> blocks 00:10:20.280 --> 00:10:20.290 align:start position:0% just fill up the blocks 00:10:20.290 --> 00:10:23.320 align:start position:0% just fill up the blocks let's<00:10:21.290> get<00:10:21.500> these<00:10:22.100> miners<00:10:22.550> to<00:10:22.790> think<00:10:23.210> that 00:10:23.320 --> 00:10:23.330 align:start position:0% let's get these miners to think that 00:10:23.330 --> 00:10:24.670 align:start position:0% let's get these miners to think that these<00:10:23.480> blocks<00:10:23.750> are<00:10:23.900> really<00:10:24.110> full<00:10:24.320> so<00:10:24.560> they'll 00:10:24.670 --> 00:10:24.680 align:start position:0% these blocks are really full so they'll 00:10:24.680 --> 00:10:26.290 align:start position:0% these blocks are really full so they'll start<00:10:24.830> voting<00:10:25.280> this<00:10:25.370> limit<00:10:25.640> up<00:10:25.790> and<00:10:26.090> so<00:10:26.150> that's 00:10:26.290 --> 00:10:26.300 align:start position:0% start voting this limit up and so that's 00:10:26.300 --> 00:10:28.330 align:start position:0% start voting this limit up and so that's what<00:10:26.390> we<00:10:26.480> did<00:10:26.630> we<00:10:27.590> wrote<00:10:27.830> this<00:10:27.980> up<00:10:28.160> with<00:10:28.280> a 00:10:28.330 --> 00:10:28.340 align:start position:0% what we did we wrote this up with a 00:10:28.340 --> 00:10:30.580 align:start position:0% what we did we wrote this up with a smart<00:10:28.610> contract<00:10:28.760> whose<00:10:29.750> only<00:10:30.020> intention<00:10:30.410> was 00:10:30.580 --> 00:10:30.590 align:start position:0% smart contract whose only intention was 00:10:30.590 --> 00:10:32.200 align:start position:0% smart contract whose only intention was to<00:10:30.740> waste<00:10:31.130> all<00:10:31.400> gas<00:10:31.610> that<00:10:31.790> came<00:10:31.910> into<00:10:32.060> the 00:10:32.200 --> 00:10:32.210 align:start position:0% to waste all gas that came into the 00:10:32.210 --> 00:10:36.400 align:start position:0% to waste all gas that came into the transaction<00:10:33.190> now<00:10:34.990> knowing<00:10:35.990> what<00:10:36.110> we<00:10:36.170> know<00:10:36.260> now 00:10:36.400 --> 00:10:36.410 align:start position:0% transaction now knowing what we know now 00:10:36.410 --> 00:10:37.270 align:start position:0% transaction now knowing what we know now we<00:10:36.470> could<00:10:36.650> have<00:10:36.680> done<00:10:36.830> this<00:10:36.950> a<00:10:37.010> little<00:10:37.130> better 00:10:37.270 --> 00:10:37.280 align:start position:0% we could have done this a little better 00:10:37.280 --> 00:10:39.790 align:start position:0% we could have done this a little better if<00:10:37.550> you<00:10:37.730> assert<00:10:38.030> false<00:10:38.300> you<00:10:38.840> can<00:10:39.050> actually<00:10:39.650> hit 00:10:39.790 --> 00:10:39.800 align:start position:0% if you assert false you can actually hit 00:10:39.800 --> 00:10:41.380 align:start position:0% if you assert false you can actually hit an<00:10:39.890> EVM<00:10:40.220> up<00:10:40.370> code<00:10:40.580> that<00:10:40.700> doesn't<00:10:40.820> waste<00:10:41.120> all 00:10:41.380 --> 00:10:41.390 align:start position:0% an EVM up code that doesn't waste all 00:10:41.390 --> 00:10:43.300 align:start position:0% an EVM up code that doesn't waste all this<00:10:41.510> time<00:10:41.570> on<00:10:41.960> these<00:10:42.050> full<00:10:42.260> nodes<00:10:42.500> but<00:10:43.040> still 00:10:43.300 --> 00:10:43.310 align:start position:0% this time on these full nodes but still 00:10:43.310 --> 00:10:45.610 align:start position:0% this time on these full nodes but still effectively<00:10:44.090> wastes<00:10:44.480> gas<00:10:44.660> and<00:10:44.990> gives<00:10:45.500> you 00:10:45.610 --> 00:10:45.620 align:start position:0% effectively wastes gas and gives you 00:10:45.620 --> 00:10:48.790 align:start position:0% effectively wastes gas and gives you this<00:10:45.800> block<00:10:46.090> this<00:10:47.090> block<00:10:47.150> that<00:10:47.480> is<00:10:47.540> full<00:10:48.530> of 00:10:48.790 --> 00:10:48.800 align:start position:0% this block this block that is full of 00:10:48.800 --> 00:10:52.140 align:start position:0% this block this block that is full of failing<00:10:49.190> transactions<00:10:49.730> but<00:10:50.630> it's<00:10:50.750> full<00:10:50.960> and 00:10:52.140 --> 00:10:52.150 align:start position:0% failing transactions but it's full and 00:10:52.150 --> 00:10:54.550 align:start position:0% failing transactions but it's full and you<00:10:53.150> know<00:10:53.240> I<00:10:53.270> started<00:10:53.810> in<00:10:53.930> test<00:10:54.140> nets<00:10:54.350> and<00:10:54.500> I 00:10:54.550 --> 00:10:54.560 align:start position:0% you know I started in test nets and I 00:10:54.560 --> 00:10:55.960 align:start position:0% you know I started in test nets and I really<00:10:54.830> wanted<00:10:55.010> to<00:10:55.070> help<00:10:55.220> people<00:10:55.340> with<00:10:55.760> the 00:10:55.960 --> 00:10:55.970 align:start position:0% really wanted to help people with the 00:10:55.970 --> 00:10:58.150 align:start position:0% really wanted to help people with the faucet<00:10:56.360> that<00:10:56.510> I<00:10:56.600> built<00:10:56.870> and<00:10:57.320> so<00:10:57.830> this<00:10:57.950> kind<00:10:58.130> of 00:10:58.150 --> 00:10:58.160 align:start position:0% faucet that I built and so this kind of 00:10:58.160 --> 00:10:59.650 align:start position:0% faucet that I built and so this kind of weighed<00:10:58.280> pretty<00:10:58.490> heavily<00:10:58.640> on<00:10:58.820> me<00:10:59.030> I<00:10:59.210> was 00:10:59.650 --> 00:10:59.660 align:start position:0% weighed pretty heavily on me I was 00:10:59.660 --> 00:11:01.210 align:start position:0% weighed pretty heavily on me I was wondering<00:11:00.050> like<00:11:00.080> you<00:11:00.680> know<00:11:00.800> why<00:11:01.010> are<00:11:01.040> we 00:11:01.210 --> 00:11:01.220 align:start position:0% wondering like you know why are we 00:11:01.220 --> 00:11:03.970 align:start position:0% wondering like you know why are we destroying<00:11:01.750> you<00:11:02.750> know<00:11:02.840> the<00:11:03.140> the<00:11:03.410> usability<00:11:03.770> of 00:11:03.970 --> 00:11:03.980 align:start position:0% destroying you know the the usability of 00:11:03.980 --> 00:11:06.130 align:start position:0% destroying you know the the usability of this<00:11:04.160> for<00:11:04.340> days<00:11:04.520> at<00:11:04.820> a<00:11:04.850> time<00:11:04.910> for<00:11:05.810> people<00:11:05.930> who 00:11:06.130 --> 00:11:06.140 align:start position:0% this for days at a time for people who 00:11:06.140 --> 00:11:06.660 align:start position:0% this for days at a time for people who want<00:11:06.320> to<00:11:06.380> use 00:11:06.660 --> 00:11:06.670 align:start position:0% want to use 00:11:06.670 --> 00:11:10.140 align:start position:0% want to use Austin<00:11:07.950> no<00:11:08.950> I'm<00:11:09.130> just<00:11:09.340> kidding<00:11:09.700> somebody<00:11:10.000> kept 00:11:10.140 --> 00:11:10.150 align:start position:0% Austin no I'm just kidding somebody kept 00:11:10.150 --> 00:11:12.390 align:start position:0% Austin no I'm just kidding somebody kept mining<00:11:10.540> empty<00:11:10.810> blocks<00:11:11.050> and<00:11:11.380> so<00:11:12.130> they<00:11:12.220> kept 00:11:12.390 --> 00:11:12.400 align:start position:0% mining empty blocks and so they kept 00:11:12.400 --> 00:11:15.780 align:start position:0% mining empty blocks and so they kept voting<00:11:12.610> that<00:11:12.850> gas<00:11:13.030> limit<00:11:13.240> down<00:11:14.520> so<00:11:15.520> we<00:11:15.610> had<00:11:15.730> to 00:11:15.780 --> 00:11:15.790 align:start position:0% voting that gas limit down so we had to 00:11:15.790 --> 00:11:16.410 align:start position:0% voting that gas limit down so we had to do<00:11:15.880> it<00:11:15.940> ourselves 00:11:16.410 --> 00:11:16.420 align:start position:0% do it ourselves 00:11:16.420 --> 00:11:18.900 align:start position:0% do it ourselves we<00:11:16.630> spun<00:11:16.840> up<00:11:16.960> our<00:11:17.080> own<00:11:17.230> miners<00:11:17.650> with<00:11:18.370> a<00:11:18.400> target 00:11:18.900 --> 00:11:18.910 align:start position:0% we spun up our own miners with a target 00:11:18.910 --> 00:11:21.240 align:start position:0% we spun up our own miners with a target gas<00:11:19.060> limit<00:11:19.420> that<00:11:20.380> was<00:11:20.500> already<00:11:20.740> set<00:11:20.950> to<00:11:20.980> higher 00:11:21.240 --> 00:11:21.250 align:start position:0% gas limit that was already set to higher 00:11:21.250 --> 00:11:23.190 align:start position:0% gas limit that was already set to higher so<00:11:21.610> even<00:11:22.270> though<00:11:22.360> these<00:11:22.480> blocks<00:11:22.720> were<00:11:22.870> mining 00:11:23.190 --> 00:11:23.200 align:start position:0% so even though these blocks were mining 00:11:23.200 --> 00:11:24.810 align:start position:0% so even though these blocks were mining were<00:11:23.290> mostly<00:11:23.560> empty<00:11:23.890> we<00:11:24.040> kept<00:11:24.280> voting<00:11:24.550> that 00:11:24.810 --> 00:11:24.820 align:start position:0% were mostly empty we kept voting that 00:11:24.820 --> 00:11:26.850 align:start position:0% were mostly empty we kept voting that gas<00:11:25.000> lit<00:11:25.270> up<00:11:25.420> we<00:11:25.720> became<00:11:25.960> more<00:11:26.320> than<00:11:26.530> half<00:11:26.710> of 00:11:26.850 --> 00:11:26.860 align:start position:0% gas lit up we became more than half of 00:11:26.860 --> 00:11:28.350 align:start position:0% gas lit up we became more than half of the<00:11:26.980> network<00:11:27.250> and<00:11:27.610> were<00:11:27.730> able<00:11:27.970> to<00:11:28.000> get<00:11:28.210> that 00:11:28.350 --> 00:11:28.360 align:start position:0% the network and were able to get that 00:11:28.360 --> 00:11:31.020 align:start position:0% the network and were able to get that gas<00:11:28.510> limit<00:11:28.720> up<00:11:29.550> but<00:11:30.550> it<00:11:30.640> really<00:11:30.760> got<00:11:30.910> us 00:11:31.020 --> 00:11:31.030 align:start position:0% gas limit up but it really got us 00:11:31.030 --> 00:11:33.900 align:start position:0% gas limit up but it really got us involved<00:11:31.240> with<00:11:31.950> how<00:11:32.950> are<00:11:33.070> we<00:11:33.190> developing<00:11:33.550> our 00:11:33.900 --> 00:11:33.910 align:start position:0% involved with how are we developing our 00:11:33.910 --> 00:11:35.760 align:start position:0% involved with how are we developing our software<00:11:34.330> is<00:11:34.510> test<00:11:34.990> that<00:11:35.140> really<00:11:35.410> the<00:11:35.620> right 00:11:35.760 --> 00:11:35.770 align:start position:0% software is test that really the right 00:11:35.770 --> 00:11:39.450 align:start position:0% software is test that really the right place<00:11:36.010> to<00:11:36.280> be<00:11:36.370> doing<00:11:36.490> all<00:11:36.820> of<00:11:36.850> this<00:11:37.060> work<00:11:38.460> here 00:11:39.450 --> 00:11:39.460 align:start position:0% place to be doing all of this work here 00:11:39.460 --> 00:11:41.190 align:start position:0% place to be doing all of this work here is<00:11:39.640> a<00:11:39.670> repository<00:11:39.910> where<00:11:40.570> we<00:11:40.660> have<00:11:40.780> created 00:11:41.190 --> 00:11:41.200 align:start position:0% is a repository where we have created 00:11:41.200 --> 00:11:43.350 align:start position:0% is a repository where we have created guess<00:11:41.800> and<00:11:42.040> parity<00:11:42.460> in<00:11:42.610> various<00:11:43.120> incarnations 00:11:43.350 --> 00:11:43.360 align:start position:0% guess and parity in various incarnations 00:11:43.360 --> 00:11:45.510 align:start position:0% guess and parity in various incarnations so<00:11:43.840> this<00:11:43.960> is<00:11:44.140> you<00:11:44.470> know<00:11:44.590> connecting<00:11:45.130> to<00:11:45.310> Rob 00:11:45.510 --> 00:11:45.520 align:start position:0% so this is you know connecting to Rob 00:11:45.520 --> 00:11:47.400 align:start position:0% so this is you know connecting to Rob Stan<00:11:45.790> having<00:11:46.120> a<00:11:46.180> local<00:11:46.360> instant<00:11:46.870> seal<00:11:47.080> having 00:11:47.400 --> 00:11:47.410 align:start position:0% Stan having a local instant seal having 00:11:47.410 --> 00:11:48.900 align:start position:0% Stan having a local instant seal having a<00:11:47.500> local<00:11:47.830> mining<00:11:48.160> thing<00:11:48.280> that<00:11:48.460> mines<00:11:48.610> blocks 00:11:48.900 --> 00:11:48.910 align:start position:0% a local mining thing that mines blocks 00:11:48.910 --> 00:11:51.830 align:start position:0% a local mining thing that mines blocks about<00:11:49.180> every<00:11:49.390> second<00:11:49.780> and<00:11:50.250> this<00:11:51.250> is<00:11:51.310> a<00:11:51.400> public 00:11:51.830 --> 00:11:51.840 align:start position:0% about every second and this is a public 00:11:51.840 --> 00:11:54.000 align:start position:0% about every second and this is a public repository<00:11:52.840> where<00:11:53.020> anybody<00:11:53.650> can<00:11:53.800> come<00:11:53.890> and 00:11:54.000 --> 00:11:54.010 align:start position:0% repository where anybody can come and 00:11:54.010 --> 00:11:55.920 align:start position:0% repository where anybody can come and create<00:11:54.190> these<00:11:54.280> docker<00:11:54.490> files<00:11:54.820> and<00:11:55.120> images<00:11:55.390> to 00:11:55.920 --> 00:11:55.930 align:start position:0% create these docker files and images to 00:11:55.930 --> 00:11:58.230 align:start position:0% create these docker files and images to have<00:11:56.470> a<00:11:56.500> consistent<00:11:57.280> environment<00:11:57.520> to 00:11:58.230 --> 00:11:58.240 align:start position:0% have a consistent environment to 00:11:58.240 --> 00:12:01.980 align:start position:0% have a consistent environment to redeploy<00:11:58.630> to<00:12:00.120> so<00:12:01.120> you<00:12:01.180> have<00:12:01.300> this<00:12:01.390> local<00:12:01.660> guess 00:12:01.980 --> 00:12:01.990 align:start position:0% redeploy to so you have this local guess 00:12:01.990 --> 00:12:03.810 align:start position:0% redeploy to so you have this local guess that<00:12:02.350> you<00:12:02.440> can<00:12:02.590> spin<00:12:02.770> up<00:12:02.890> on<00:12:03.040> your<00:12:03.490> local 00:12:03.810 --> 00:12:03.820 align:start position:0% that you can spin up on your local 00:12:03.820 --> 00:12:06.120 align:start position:0% that you can spin up on your local system<00:12:04.060> that's<00:12:04.330> great<00:12:04.510> and<00:12:04.780> then<00:12:05.560> you<00:12:05.650> can<00:12:05.800> put 00:12:06.120 --> 00:12:06.130 align:start position:0% system that's great and then you can put 00:12:06.130 --> 00:12:08.850 align:start position:0% system that's great and then you can put contracts<00:12:06.610> into<00:12:06.880> it<00:12:07.000> and<00:12:07.810> if<00:12:08.500> anything<00:12:08.680> goes 00:12:08.850 --> 00:12:08.860 align:start position:0% contracts into it and if anything goes 00:12:08.860 --> 00:12:10.110 align:start position:0% contracts into it and if anything goes wrong<00:12:09.010> you<00:12:09.190> just<00:12:09.370> tear<00:12:09.490> it<00:12:09.550> down<00:12:09.610> bring<00:12:09.940> a<00:12:10.030> new 00:12:10.110 --> 00:12:10.120 align:start position:0% wrong you just tear it down bring a new 00:12:10.120 --> 00:12:11.730 align:start position:0% wrong you just tear it down bring a new one<00:12:10.240> up<00:12:10.330> and<00:12:10.450> redeploy<00:12:10.810> but<00:12:11.380> for<00:12:11.530> us<00:12:11.620> this 00:12:11.730 --> 00:12:11.740 align:start position:0% one up and redeploy but for us this 00:12:11.740 --> 00:12:12.950 align:start position:0% one up and redeploy but for us this redeployment<00:12:12.250> actual<00:12:12.430> takes<00:12:12.550> a<00:12:12.640> long<00:12:12.790> time 00:12:12.950 --> 00:12:12.960 align:start position:0% redeployment actual takes a long time 00:12:12.960 --> 00:12:15.630 align:start position:0% redeployment actual takes a long time takes<00:12:13.960> about<00:12:14.050> 20<00:12:14.500> to<00:12:14.650> 30<00:12:14.860> minutes<00:12:14.920> to<00:12:15.250> do<00:12:15.460> an 00:12:15.630 --> 00:12:15.640 align:start position:0% takes about 20 to 30 minutes to do an 00:12:15.640 --> 00:12:17.490 align:start position:0% takes about 20 to 30 minutes to do an augur<00:12:16.120> deploy<00:12:16.390> with<00:12:16.720> all<00:12:16.930> the<00:12:17.080> seed<00:12:17.290> data 00:12:17.490 --> 00:12:17.500 align:start position:0% augur deploy with all the seed data 00:12:17.500 --> 00:12:19.050 align:start position:0% augur deploy with all the seed data that's<00:12:17.980> important<00:12:18.400> for<00:12:18.550> our<00:12:18.580> development 00:12:19.050 --> 00:12:19.060 align:start position:0% that's important for our development 00:12:19.060 --> 00:12:21.000 align:start position:0% that's important for our development environments<00:12:19.540> and<00:12:19.840> so<00:12:20.590> we<00:12:20.650> took<00:12:20.770> it<00:12:20.860> one<00:12:20.950> step 00:12:21.000 --> 00:12:21.010 align:start position:0% environments and so we took it one step 00:12:21.010 --> 00:12:21.920 align:start position:0% environments and so we took it one step further 00:12:21.920 --> 00:12:21.930 align:start position:0% further 00:12:21.930 --> 00:12:24.930 align:start position:0% further we<00:12:22.930> wrapped<00:12:23.200> after<00:12:24.040> the<00:12:24.130> contract<00:12:24.550> deployment 00:12:24.930 --> 00:12:24.940 align:start position:0% we wrapped after the contract deployment 00:12:24.940 --> 00:12:27.480 align:start position:0% we wrapped after the contract deployment into<00:12:25.120> a<00:12:25.150> new<00:12:25.450> docker<00:12:25.690> image<00:12:26.080> and<00:12:26.320> this<00:12:27.160> became 00:12:27.480 --> 00:12:27.490 align:start position:0% into a new docker image and this became 00:12:27.490 --> 00:12:29.610 align:start position:0% into a new docker image and this became the<00:12:27.640> base<00:12:27.790> with<00:12:28.000> which<00:12:28.150> and<00:12:28.480> all<00:12:28.660> our<00:12:29.020> entire 00:12:29.610 --> 00:12:29.620 align:start position:0% the base with which and all our entire 00:12:29.620 --> 00:12:31.320 align:start position:0% the base with which and all our entire development<00:12:30.070> environments<00:12:30.670> were<00:12:30.970> call<00:12:31.210> her 00:12:31.320 --> 00:12:31.330 align:start position:0% development environments were call her 00:12:31.330 --> 00:12:33.570 align:start position:0% development environments were call her develop<00:12:31.660> errs<00:12:31.780> use<00:12:31.990> these<00:12:32.200> images<00:12:32.320> now<00:12:32.680> and<00:12:32.980> we 00:12:33.570 --> 00:12:33.580 align:start position:0% develop errs use these images now and we 00:12:33.580 --> 00:12:37.050 align:start position:0% develop errs use these images now and we version<00:12:33.910> them<00:12:34.830> so<00:12:35.830> whenever<00:12:36.160> we<00:12:36.370> have<00:12:36.490> a<00:12:36.520> new 00:12:37.050 --> 00:12:37.060 align:start position:0% version them so whenever we have a new 00:12:37.060 --> 00:12:39.510 align:start position:0% version them so whenever we have a new set<00:12:37.330> of<00:12:37.360> contracts<00:12:37.960> to<00:12:38.170> test<00:12:38.500> out<00:12:38.680> we<00:12:38.950> say<00:12:39.100> hey 00:12:39.510 --> 00:12:39.520 align:start position:0% set of contracts to test out we say hey 00:12:39.520 --> 00:12:41.790 align:start position:0% set of contracts to test out we say hey everybody<00:12:39.730> -<00:12:40.060> 12<00:12:40.360> is<00:12:40.480> up<00:12:40.600> and<00:12:40.720> all<00:12:41.200> developers 00:12:41.790 --> 00:12:41.800 align:start position:0% everybody - 12 is up and all developers 00:12:41.800 --> 00:12:44.520 align:start position:0% everybody - 12 is up and all developers pulled<00:12:42.190> down<00:12:42.370> -<00:12:42.610> 12<00:12:42.910> and<00:12:43.150> it's<00:12:43.960> exactly<00:12:44.380> the 00:12:44.520 --> 00:12:44.530 align:start position:0% pulled down - 12 and it's exactly the 00:12:44.530 --> 00:12:46.380 align:start position:0% pulled down - 12 and it's exactly the same<00:12:44.650> for<00:12:44.710> everybody<00:12:45.040> the<00:12:45.880> same<00:12:46.030> transaction 00:12:46.380 --> 00:12:46.390 align:start position:0% same for everybody the same transaction 00:12:46.390 --> 00:12:48.180 align:start position:0% same for everybody the same transaction hashes<00:12:46.870> the<00:12:46.990> same<00:12:47.110> addresses<00:12:47.500> the<00:12:47.740> same<00:12:47.890> block 00:12:48.180 --> 00:12:48.190 align:start position:0% hashes the same addresses the same block 00:12:48.190 --> 00:12:50.070 align:start position:0% hashes the same addresses the same block timestamps<00:12:48.940> so<00:12:49.330> we<00:12:49.420> know<00:12:49.660> that<00:12:49.840> we're<00:12:49.930> all 00:12:50.070 --> 00:12:50.080 align:start position:0% timestamps so we know that we're all 00:12:50.080 --> 00:12:51.450 align:start position:0% timestamps so we know that we're all building<00:12:50.350> on<00:12:50.530> something<00:12:50.800> that's<00:12:50.950> the<00:12:51.010> same<00:12:51.190> as 00:12:51.450 --> 00:12:51.460 align:start position:0% building on something that's the same as 00:12:51.460 --> 00:12:52.800 align:start position:0% building on something that's the same as if<00:12:51.580> it<00:12:51.640> was<00:12:51.790> up<00:12:51.910> on<00:12:52.000> Rob's<00:12:52.270> turn<00:12:52.420> on<00:12:52.540> something 00:12:52.800 --> 00:12:52.810 align:start position:0% if it was up on Rob's turn on something 00:12:52.810 --> 00:12:55.200 align:start position:0% if it was up on Rob's turn on something public<00:12:53.170> but<00:12:53.950> it's<00:12:54.070> local<00:12:54.460> and<00:12:54.640> it<00:12:54.910> has<00:12:55.000> one 00:12:55.200 --> 00:12:55.210 align:start position:0% public but it's local and it has one 00:12:55.210 --> 00:12:57.960 align:start position:0% public but it's local and it has one second<00:12:55.540> blocked<00:12:55.720> block<00:12:56.260> times<00:12:56.530> and<00:12:56.890> it<00:12:57.850> has<00:12:57.940> a 00:12:57.960 --> 00:12:57.970 align:start position:0% second blocked block times and it has a 00:12:57.970 --> 00:12:59.220 align:start position:0% second blocked block times and it has a block<00:12:58.150> cast<00:12:58.360> limit<00:12:58.570> of<00:12:58.630> 8<00:12:58.720> million<00:12:58.930> we<00:12:59.110> had 00:12:59.220 --> 00:12:59.230 align:start position:0% block cast limit of 8 million we had 00:12:59.230 --> 00:13:00.360 align:start position:0% block cast limit of 8 million we had complete<00:12:59.620> control<00:12:59.710> of<00:13:00.010> how<00:13:00.190> this<00:13:00.310> thing 00:13:00.360 --> 00:13:00.370 align:start position:0% complete control of how this thing 00:13:00.370 --> 00:13:04.020 align:start position:0% complete control of how this thing behaves<00:13:01.740> there<00:13:02.740> are<00:13:02.800> new<00:13:02.920> tools<00:13:03.100> to<00:13:03.490> do<00:13:03.790> some 00:13:04.020 --> 00:13:04.030 align:start position:0% behaves there are new tools to do some 00:13:04.030 --> 00:13:06.360 align:start position:0% behaves there are new tools to do some of<00:13:04.120> the<00:13:04.180> same<00:13:04.330> things<00:13:04.570> this<00:13:04.750> is<00:13:04.900> ganache<00:13:05.370> this 00:13:06.360 --> 00:13:06.370 align:start position:0% of the same things this is ganache this 00:13:06.370 --> 00:13:07.770 align:start position:0% of the same things this is ganache this wasn't<00:13:06.700> released<00:13:06.910> by<00:13:07.150> the<00:13:07.210> time<00:13:07.420> that<00:13:07.570> we<00:13:07.690> were 00:13:07.770 --> 00:13:07.780 align:start position:0% wasn't released by the time that we were 00:13:07.780 --> 00:13:08.880 align:start position:0% wasn't released by the time that we were working<00:13:07.840> on<00:13:08.170> this<00:13:08.320> but<00:13:08.470> I<00:13:08.500> think<00:13:08.680> we<00:13:08.770> would 00:13:08.880 --> 00:13:08.890 align:start position:0% working on this but I think we would 00:13:08.890 --> 00:13:09.960 align:start position:0% working on this but I think we would look<00:13:08.980> into<00:13:09.160> something<00:13:09.490> along<00:13:09.730> these<00:13:09.910> lines 00:13:09.960 --> 00:13:09.970 align:start position:0% look into something along these lines 00:13:09.970 --> 00:13:13.980 align:start position:0% look into something along these lines this<00:13:10.390> is<00:13:10.510> an<00:13:10.630> excellent<00:13:11.140> local<00:13:11.800> test<00:13:12.100> RPC<00:13:12.990> but 00:13:13.980 --> 00:13:13.990 align:start position:0% this is an excellent local test RPC but 00:13:13.990 --> 00:13:15.870 align:start position:0% this is an excellent local test RPC but no<00:13:14.500> matter<00:13:14.620> what<00:13:14.830> you're<00:13:14.950> using<00:13:14.980> invest<00:13:15.670> in 00:13:15.870 --> 00:13:15.880 align:start position:0% no matter what you're using invest in 00:13:15.880 --> 00:13:17.310 align:start position:0% no matter what you're using invest in your<00:13:15.970> aetherium<00:13:16.450> development<00:13:16.900> environment 00:13:17.310 --> 00:13:17.320 align:start position:0% your aetherium development environment 00:13:17.320 --> 00:13:19.800 align:start position:0% your aetherium development environment our<00:13:18.190> velocity<00:13:18.700> went<00:13:18.850> way<00:13:19.150> up<00:13:19.180> once<00:13:19.570> we<00:13:19.690> got 00:13:19.800 --> 00:13:19.810 align:start position:0% our velocity went way up once we got 00:13:19.810 --> 00:13:23.420 align:start position:0% our velocity went way up once we got this<00:13:19.960> right 00:13:23.420 --> 00:13:23.430 align:start position:0% 00:13:23.430 --> 00:13:26.340 align:start position:0% so<00:13:24.430> we<00:13:24.490> had<00:13:24.579> an<00:13:24.639> issue<00:13:24.730> with<00:13:24.910> 0x<00:13:25.350> after 00:13:26.340 --> 00:13:26.350 align:start position:0% so we had an issue with 0x after 00:13:26.350 --> 00:13:29.400 align:start position:0% so we had an issue with 0x after deployment<00:13:27.959> so<00:13:28.959> I<00:13:28.990> mentioned<00:13:29.259> there's<00:13:29.379> this 00:13:29.400 --> 00:13:29.410 align:start position:0% deployment so I mentioned there's this 00:13:29.410 --> 00:13:31.920 align:start position:0% deployment so I mentioned there's this five<00:13:29.709> point<00:13:29.889> eight<00:13:30.069> million<00:13:30.610> gasp<00:13:31.180> contract 00:13:31.920 --> 00:13:31.930 align:start position:0% five point eight million gasp contract 00:13:31.930 --> 00:13:34.170 align:start position:0% five point eight million gasp contract this<00:13:32.649> contains<00:13:33.069> the<00:13:33.160> market<00:13:33.550> functionality 00:13:34.170 --> 00:13:34.180 align:start position:0% this contains the market functionality 00:13:34.180 --> 00:13:36.420 align:start position:0% this contains the market functionality if<00:13:34.990> every<00:13:35.259> time<00:13:35.439> a<00:13:35.470> user<00:13:35.620> created<00:13:36.100> a<00:13:36.160> market 00:13:36.420 --> 00:13:36.430 align:start position:0% if every time a user created a market 00:13:36.430 --> 00:13:37.920 align:start position:0% if every time a user created a market they<00:13:36.519> had<00:13:36.610> to<00:13:36.670> deploy<00:13:36.819> a<00:13:36.879> 5.8<00:13:37.360> million<00:13:37.540> gasp<00:13:37.779> to 00:13:37.920 --> 00:13:37.930 align:start position:0% they had to deploy a 5.8 million gasp to 00:13:37.930 --> 00:13:40.710 align:start position:0% they had to deploy a 5.8 million gasp to be<00:13:38.019> really<00:13:38.290> expensive<00:13:39.300> and<00:13:40.300> so<00:13:40.420> we<00:13:40.480> deploy<00:13:40.689> a 00:13:40.710 --> 00:13:40.720 align:start position:0% be really expensive and so we deploy a 00:13:40.720 --> 00:13:43.139 align:start position:0% be really expensive and so we deploy a delegator<00:13:41.139> a<00:13:41.350> delegator<00:13:42.069> is<00:13:42.249> a<00:13:42.279> contract<00:13:42.819> that 00:13:43.139 --> 00:13:43.149 align:start position:0% delegator a delegator is a contract that 00:13:43.149 --> 00:13:45.809 align:start position:0% delegator a delegator is a contract that has<00:13:43.660> its<00:13:43.839> own<00:13:43.930> contract<00:13:44.379> states<00:13:44.589> has<00:13:45.579> its<00:13:45.759> own 00:13:45.809 --> 00:13:45.819 align:start position:0% has its own contract states has its own 00:13:45.819 --> 00:13:47.400 align:start position:0% has its own contract states has its own address<00:13:45.970> buffers<00:13:46.569> all<00:13:46.899> of<00:13:46.990> its<00:13:47.079> functionality 00:13:47.400 --> 00:13:47.410 align:start position:0% address buffers all of its functionality 00:13:47.410 --> 00:13:48.269 align:start position:0% address buffers all of its functionality somewhere<00:13:47.889> else 00:13:48.269 --> 00:13:48.279 align:start position:0% somewhere else 00:13:48.279 --> 00:13:51.090 align:start position:0% somewhere else the<00:13:49.209> only<00:13:49.300> problem<00:13:49.660> when<00:13:50.259> you<00:13:50.350> use<00:13:50.740> this 00:13:51.090 --> 00:13:51.100 align:start position:0% the only problem when you use this 00:13:51.100 --> 00:13:53.220 align:start position:0% the only problem when you use this contract<00:13:51.639> you<00:13:52.089> incur<00:13:52.389> about<00:13:52.600> a<00:13:52.629> two<00:13:52.839> thousand 00:13:53.220 --> 00:13:53.230 align:start position:0% contract you incur about a two thousand 00:13:53.230 --> 00:13:55.619 align:start position:0% contract you incur about a two thousand gas<00:13:53.399> cost<00:13:54.399> whenever<00:13:54.819> you<00:13:54.999> bridge<00:13:55.480> this 00:13:55.619 --> 00:13:55.629 align:start position:0% gas cost whenever you bridge this 00:13:55.629 --> 00:13:57.090 align:start position:0% gas cost whenever you bridge this delegation<00:13:56.050> that's<00:13:56.379> just<00:13:56.529> the<00:13:56.740> base<00:13:56.860> call 00:13:57.090 --> 00:13:57.100 align:start position:0% delegation that's just the base call 00:13:57.100 --> 00:14:00.389 align:start position:0% delegation that's just the base call cost<00:13:57.399> of<00:13:57.610> a<00:13:57.730> call<00:13:58.180> like<00:13:58.269> that<00:13:59.069> but<00:14:00.069> imagine 00:14:00.389 --> 00:14:00.399 align:start position:0% cost of a call like that but imagine 00:14:00.399 --> 00:14:02.489 align:start position:0% cost of a call like that but imagine that<00:14:00.519> this<00:14:00.610> isn't<00:14:00.819> the<00:14:01.180> market<00:14:01.540> this<00:14:02.079> is<00:14:02.139> the 00:14:02.489 --> 00:14:02.499 align:start position:0% that this isn't the market this is the 00:14:02.499 --> 00:14:05.340 align:start position:0% that this isn't the market this is the rep<00:14:02.889> token<00:14:03.249> contract<00:14:03.699> and<00:14:04.290> imagine<00:14:05.290> the 00:14:05.340 --> 00:14:05.350 align:start position:0% rep token contract and imagine the 00:14:05.350 --> 00:14:06.689 align:start position:0% rep token contract and imagine the caller<00:14:05.559> isn't<00:14:05.889> a<00:14:05.920> person<00:14:06.249> who's<00:14:06.399> willing<00:14:06.519> to 00:14:06.689 --> 00:14:06.699 align:start position:0% caller isn't a person who's willing to 00:14:06.699 --> 00:14:09.329 align:start position:0% caller isn't a person who's willing to spend<00:14:06.939> two<00:14:07.269> thousand<00:14:07.629> extra<00:14:07.930> gas<00:14:08.339> imagine 00:14:09.329 --> 00:14:09.339 align:start position:0% spend two thousand extra gas imagine 00:14:09.339 --> 00:14:12.470 align:start position:0% spend two thousand extra gas imagine this<00:14:09.459> is<00:14:09.639> zero<00:14:10.209> X<00:14:10.360> and<00:14:10.660> the<00:14:10.870> 0<00:14:11.050> X<00:14:11.199> contract<00:14:11.709> and 00:14:12.470 --> 00:14:12.480 align:start position:0% this is zero X and the 0 X contract and 00:14:12.480 --> 00:14:15.410 align:start position:0% this is zero X and the 0 X contract and also<00:14:13.480> imagine<00:14:13.870> that<00:14:14.470> the<00:14:14.589> 0<00:14:14.800> X<00:14:14.920> contract 00:14:15.410 --> 00:14:15.420 align:start position:0% also imagine that the 0 X contract 00:14:15.420 --> 00:14:17.939 align:start position:0% also imagine that the 0 X contract created<00:14:16.420> a<00:14:16.509> limit<00:14:16.990> a<00:14:17.110> hard-coded<00:14:17.589> limit 00:14:17.939 --> 00:14:17.949 align:start position:0% created a limit a hard-coded limit 00:14:17.949 --> 00:14:19.739 align:start position:0% created a limit a hard-coded limit inside<00:14:18.309> of<00:14:18.430> their<00:14:18.610> contract<00:14:19.269> that<00:14:19.360> said<00:14:19.569> a 00:14:19.739 --> 00:14:19.749 align:start position:0% inside of their contract that said a 00:14:19.749 --> 00:14:21.840 align:start position:0% inside of their contract that said a balance<00:14:20.439> of<00:14:20.559> lookup<00:14:20.949> should<00:14:21.160> never<00:14:21.399> take<00:14:21.610> more 00:14:21.840 --> 00:14:21.850 align:start position:0% balance of lookup should never take more 00:14:21.850 --> 00:14:24.059 align:start position:0% balance of lookup should never take more than<00:14:21.999> this<00:14:22.149> much<00:14:22.329> gas<00:14:22.569> and<00:14:22.990> at<00:14:23.769> the<00:14:23.889> right 00:14:24.059 --> 00:14:24.069 align:start position:0% than this much gas and at the right 00:14:24.069 --> 00:14:26.160 align:start position:0% than this much gas and at the right that's<00:14:25.059> a<00:14:25.149> lot<00:14:25.360> of<00:14:25.389> gas<00:14:25.569> to<00:14:25.779> do<00:14:25.870> a<00:14:25.899> simple 00:14:26.160 --> 00:14:26.170 align:start position:0% that's a lot of gas to do a simple 00:14:26.170 --> 00:14:28.559 align:start position:0% that's a lot of gas to do a simple storage<00:14:26.500> lookup<00:14:26.800> and<00:14:26.949> return<00:14:27.189> that<00:14:27.220> data<00:14:27.569> but 00:14:28.559 --> 00:14:28.569 align:start position:0% storage lookup and return that data but 00:14:28.569 --> 00:14:30.809 align:start position:0% storage lookup and return that data but not<00:14:28.809> when<00:14:28.959> you<00:14:29.050> add<00:14:29.170> in<00:14:29.350> delegation<00:14:29.920> and<00:14:30.129> we 00:14:30.809 --> 00:14:30.819 align:start position:0% not when you add in delegation and we 00:14:30.819 --> 00:14:32.699 align:start position:0% not when you add in delegation and we blew<00:14:31.089> that<00:14:31.300> gas<00:14:31.480> limit<00:14:31.870> for<00:14:32.050> that<00:14:32.079> one<00:14:32.350> lookup 00:14:32.699 --> 00:14:32.709 align:start position:0% blew that gas limit for that one lookup 00:14:32.709 --> 00:14:36.059 align:start position:0% blew that gas limit for that one lookup so<00:14:33.899> congratulations<00:14:34.899> you've<00:14:35.110> deployed<00:14:35.410> also 00:14:36.059 --> 00:14:36.069 align:start position:0% so congratulations you've deployed also 00:14:36.069 --> 00:14:40.740 align:start position:0% so congratulations you've deployed also your<00:14:36.459> delisted<00:14:39.000> so<00:14:40.000> we<00:14:40.089> had<00:14:40.180> some<00:14:40.300> ideas<00:14:40.660> about 00:14:40.740 --> 00:14:40.750 align:start position:0% your delisted so we had some ideas about 00:14:40.750 --> 00:14:44.819 align:start position:0% your delisted so we had some ideas about how<00:14:40.839> to<00:14:40.990> solve<00:14:41.230> this<00:14:43.379> we<00:14:44.379> could<00:14:44.529> have<00:14:44.559> wrapped 00:14:44.819 --> 00:14:44.829 align:start position:0% how to solve this we could have wrapped 00:14:44.829 --> 00:14:46.410 align:start position:0% how to solve this we could have wrapped the<00:14:45.040> rep<00:14:45.189> token<00:14:45.490> in<00:14:45.610> a<00:14:45.670> non<00:14:45.879> delegated 00:14:46.410 --> 00:14:46.420 align:start position:0% the rep token in a non delegated 00:14:46.420 --> 00:14:47.970 align:start position:0% the rep token in a non delegated contract<00:14:46.809> in<00:14:47.350> the<00:14:47.439> same<00:14:47.589> way<00:14:47.709> that<00:14:47.769> you<00:14:47.860> can 00:14:47.970 --> 00:14:47.980 align:start position:0% contract in the same way that you can 00:14:47.980 --> 00:14:49.920 align:start position:0% contract in the same way that you can wrap<00:14:48.189> ether<00:14:48.550> into<00:14:48.879> an<00:14:48.970> A<00:14:49.089> or<00:14:49.120> C<00:14:49.269> 20<00:14:49.540> contract 00:14:49.920 --> 00:14:49.930 align:start position:0% wrap ether into an A or C 20 contract 00:14:49.930 --> 00:14:51.329 align:start position:0% wrap ether into an A or C 20 contract there's<00:14:50.110> no<00:14:50.170> reason<00:14:50.379> you<00:14:50.410> can't<00:14:50.649> wrap<00:14:50.800> a<00:14:50.980> near 00:14:51.329 --> 00:14:51.339 align:start position:0% there's no reason you can't wrap a near 00:14:51.339 --> 00:14:53.189 align:start position:0% there's no reason you can't wrap a near Z<00:14:51.519> 20<00:14:51.790> into<00:14:52.029> another<00:14:52.240> a<00:14:52.389> or<00:14:52.449> C<00:14:52.569> 20<00:14:52.779> that<00:14:52.930> isn't 00:14:53.189 --> 00:14:53.199 align:start position:0% Z 20 into another a or C 20 that isn't 00:14:53.199 --> 00:14:55.259 align:start position:0% Z 20 into another a or C 20 that isn't delegated<00:14:53.559> and<00:14:53.649> is<00:14:53.800> compatible<00:14:54.339> but<00:14:55.059> that<00:14:55.180> has 00:14:55.259 --> 00:14:55.269 align:start position:0% delegated and is compatible but that has 00:14:55.269 --> 00:14:57.439 align:start position:0% delegated and is compatible but that has a<00:14:55.300> horrible<00:14:55.660> user<00:14:56.110> experience<00:14:56.620> for<00:14:56.769> the<00:14:56.829> user 00:14:57.439 --> 00:14:57.449 align:start position:0% a horrible user experience for the user 00:14:57.449 --> 00:15:00.840 align:start position:0% a horrible user experience for the user luckily<00:14:58.709> we<00:14:59.709> talked<00:14:59.920> to<00:15:00.040> 0x<00:15:00.250> about<00:15:00.550> this<00:15:00.670> issue 00:15:00.840 --> 00:15:00.850 align:start position:0% luckily we talked to 0x about this issue 00:15:00.850 --> 00:15:02.369 align:start position:0% luckily we talked to 0x about this issue they<00:15:01.269> were<00:15:01.329> able<00:15:01.449> to<00:15:01.569> execute<00:15:01.930> on<00:15:02.259> their 00:15:02.369 --> 00:15:02.379 align:start position:0% they were able to execute on their 00:15:02.379 --> 00:15:04.439 align:start position:0% they were able to execute on their governance<00:15:02.680> and<00:15:02.860> they<00:15:02.949> upgraded<00:15:03.429> their<00:15:03.790> 0x 00:15:04.439 --> 00:15:04.449 align:start position:0% governance and they upgraded their 0x 00:15:04.449 --> 00:15:06.900 align:start position:0% governance and they upgraded their 0x exchange<00:15:04.870> to<00:15:05.079> a<00:15:05.110> v2<00:15:05.559> that<00:15:06.040> has<00:15:06.429> a<00:15:06.459> lot<00:15:06.699> of<00:15:06.730> new 00:15:06.900 --> 00:15:06.910 align:start position:0% exchange to a v2 that has a lot of new 00:15:06.910 --> 00:15:09.689 align:start position:0% exchange to a v2 that has a lot of new features<00:15:07.259> but<00:15:08.259> lifts<00:15:08.679> this<00:15:08.800> gas<00:15:09.040> limit<00:15:09.279> so 00:15:09.689 --> 00:15:09.699 align:start position:0% features but lifts this gas limit so 00:15:09.699 --> 00:15:11.819 align:start position:0% features but lifts this gas limit so that<00:15:10.000> the<00:15:10.360> rep<00:15:10.509> token<00:15:10.870> is<00:15:10.990> again<00:15:11.259> compatible 00:15:11.819 --> 00:15:11.829 align:start position:0% that the rep token is again compatible 00:15:11.829 --> 00:15:15.749 align:start position:0% that the rep token is again compatible with<00:15:12.129> the<00:15:12.250> 0x<00:15:12.550> exchange<00:15:14.490> so<00:15:15.490> we<00:15:15.579> have<00:15:15.670> these 00:15:15.749 --> 00:15:15.759 align:start position:0% with the 0x exchange so we have these 00:15:15.759 --> 00:15:18.329 align:start position:0% with the 0x exchange so we have these interfaces<00:15:16.240> we<00:15:16.420> have<00:15:16.509> a<00:15:16.660> or<00:15:16.749> C<00:15:16.899> 20<00:15:17.199> and<00:15:18.160> these 00:15:18.329 --> 00:15:18.339 align:start position:0% interfaces we have a or C 20 and these 00:15:18.339 --> 00:15:19.139 align:start position:0% interfaces we have a or C 20 and these things<00:15:18.519> are<00:15:18.639> great<00:15:18.699> and<00:15:18.850> it's<00:15:18.939> great<00:15:19.120> to 00:15:19.139 --> 00:15:19.149 align:start position:0% things are great and it's great to 00:15:19.149 --> 00:15:20.519 align:start position:0% things are great and it's great to follow<00:15:19.360> these<00:15:19.540> interfaces<00:15:19.870> but<00:15:20.170> it's<00:15:20.290> no 00:15:20.519 --> 00:15:20.529 align:start position:0% follow these interfaces but it's no 00:15:20.529 --> 00:15:22.350 align:start position:0% follow these interfaces but it's no substitute<00:15:20.829> for<00:15:21.160> testing<00:15:21.670> your<00:15:21.790> integrations 00:15:22.350 --> 00:15:22.360 align:start position:0% substitute for testing your integrations 00:15:22.360 --> 00:15:24.210 align:start position:0% substitute for testing your integrations there's<00:15:22.959> all<00:15:23.170> sorts<00:15:23.470> of<00:15:23.529> crazy<00:15:23.649> things<00:15:23.860> that 00:15:24.210 --> 00:15:24.220 align:start position:0% there's all sorts of crazy things that 00:15:24.220 --> 00:15:26.549 align:start position:0% there's all sorts of crazy things that these<00:15:24.339> contracts<00:15:24.819> do<00:15:25.059> that<00:15:25.779> are<00:15:25.899> on<00:15:26.110> top<00:15:26.350> of 00:15:26.549 --> 00:15:26.559 align:start position:0% these contracts do that are on top of 00:15:26.559 --> 00:15:28.710 align:start position:0% these contracts do that are on top of the<00:15:26.649> IRC<00:15:26.860> 20<00:15:27.189> interface<00:15:27.519> and<00:15:28.149> if<00:15:28.360> you<00:15:28.449> really 00:15:28.710 --> 00:15:28.720 align:start position:0% the IRC 20 interface and if you really 00:15:28.720 --> 00:15:30.389 align:start position:0% the IRC 20 interface and if you really care<00:15:29.019> about<00:15:29.199> integrating<00:15:29.920> with<00:15:30.009> somebody 00:15:30.389 --> 00:15:30.399 align:start position:0% care about integrating with somebody 00:15:30.399 --> 00:15:32.129 align:start position:0% care about integrating with somebody especially<00:15:31.029> if<00:15:31.420> you're<00:15:31.540> a<00:15:31.569> little<00:15:31.629> different 00:15:32.129 --> 00:15:32.139 align:start position:0% especially if you're a little different 00:15:32.139 --> 00:15:33.820 align:start position:0% especially if you're a little different test<00:15:32.500> that<00:15:32.679> integration<00:15:33.040> out 00:15:33.820 --> 00:15:33.830 align:start position:0% test that integration out 00:15:33.830 --> 00:15:35.680 align:start position:0% test that integration out so<00:15:34.310> here's<00:15:34.550> how<00:15:34.700> different<00:15:35.060> the<00:15:35.120> rep<00:15:35.269> token<00:15:35.570> is 00:15:35.680 --> 00:15:35.690 align:start position:0% so here's how different the rep token is 00:15:35.690 --> 00:15:38.290 align:start position:0% so here's how different the rep token is if<00:15:35.899> you<00:15:36.380> look<00:15:36.649> on<00:15:36.860> a<00:15:37.160> Thirsk<00:15:37.399> an<00:15:37.519> the<00:15:37.850> rep<00:15:38.000> token 00:15:38.290 --> 00:15:38.300 align:start position:0% if you look on a Thirsk an the rep token 00:15:38.300 --> 00:15:41.350 align:start position:0% if you look on a Thirsk an the rep token is<00:15:38.420> not<00:15:38.750> verified<00:15:39.910> not<00:15:40.910> because<00:15:41.149> it<00:15:41.240> isn't 00:15:41.350 --> 00:15:41.360 align:start position:0% is not verified not because it isn't 00:15:41.360 --> 00:15:43.840 align:start position:0% is not verified not because it isn't verifiable<00:15:41.990> but<00:15:42.500> because<00:15:42.769> ether<00:15:43.490> scan<00:15:43.700> does 00:15:43.840 --> 00:15:43.850 align:start position:0% verifiable but because ether scan does 00:15:43.850 --> 00:15:46.329 align:start position:0% verifiable but because ether scan does not<00:15:44.000> support<00:15:44.529> verification<00:15:45.529> of<00:15:45.680> a<00:15:45.800> contract 00:15:46.329 --> 00:15:46.339 align:start position:0% not support verification of a contract 00:15:46.339 --> 00:15:48.190 align:start position:0% not support verification of a contract that<00:15:46.910> was<00:15:47.029> deployed<00:15:47.330> by<00:15:47.540> another<00:15:47.779> contract 00:15:48.190 --> 00:15:48.200 align:start position:0% that was deployed by another contract 00:15:48.200 --> 00:15:49.240 align:start position:0% that was deployed by another contract and<00:15:48.320> that's<00:15:48.440> what<00:15:48.589> the<00:15:48.680> that's<00:15:48.860> what<00:15:49.070> the<00:15:49.100> rep 00:15:49.240 --> 00:15:49.250 align:start position:0% and that's what the that's what the rep 00:15:49.250 --> 00:15:51.940 align:start position:0% and that's what the that's what the rep token<00:15:49.550> is<00:15:49.670> and<00:15:50.110> even<00:15:51.110> if<00:15:51.260> it<00:15:51.380> was<00:15:51.529> verified 00:15:51.940 --> 00:15:51.950 align:start position:0% token is and even if it was verified 00:15:51.950 --> 00:15:53.949 align:start position:0% token is and even if it was verified this<00:15:52.490> is<00:15:52.610> what<00:15:52.730> it<00:15:52.820> looks<00:15:52.940> like<00:15:53.060> is<00:15:53.600> it<00:15:53.750> a<00:15:53.810> bunch 00:15:53.949 --> 00:15:53.959 align:start position:0% this is what it looks like is it a bunch 00:15:53.959 --> 00:15:56.050 align:start position:0% this is what it looks like is it a bunch of<00:15:54.079> assembly<00:15:54.610> delegating<00:15:55.610> that<00:15:55.640> call<00:15:55.910> to 00:15:56.050 --> 00:15:56.060 align:start position:0% of assembly delegating that call to 00:15:56.060 --> 00:15:57.040 align:start position:0% of assembly delegating that call to another<00:15:56.269> contract<00:15:56.720> so<00:15:56.810> doesn't<00:15:56.959> really 00:15:57.040 --> 00:15:57.050 align:start position:0% another contract so doesn't really 00:15:57.050 --> 00:16:01.600 align:start position:0% another contract so doesn't really instill<00:15:57.500> much<00:15:57.709> confidence<00:15:58.130> anyway<00:16:00.459> so<00:16:01.459> let's 00:16:01.600 --> 00:16:01.610 align:start position:0% instill much confidence anyway so let's 00:16:01.610 --> 00:16:04.990 align:start position:0% instill much confidence anyway so let's talk<00:16:01.700> about<00:16:01.850> json-rpc<00:16:03.640> so<00:16:04.640> one<00:16:04.760> of<00:16:04.790> the<00:16:04.910> nice 00:16:04.990 --> 00:16:05.000 align:start position:0% talk about json-rpc so one of the nice 00:16:05.000 --> 00:16:06.850 align:start position:0% talk about json-rpc so one of the nice things<00:16:05.269> about<00:16:05.360> deploying<00:16:06.110> your<00:16:06.230> software<00:16:06.680> is 00:16:06.850 --> 00:16:06.860 align:start position:0% things about deploying your software is 00:16:06.860 --> 00:16:08.740 align:start position:0% things about deploying your software is that<00:16:07.310> you<00:16:07.910> get<00:16:08.000> a<00:16:08.089> chance<00:16:08.120> to<00:16:08.450> get<00:16:08.540> some<00:16:08.690> real 00:16:08.740 --> 00:16:08.750 align:start position:0% that you get a chance to get some real 00:16:08.750 --> 00:16:15.940 align:start position:0% that you get a chance to get some real user<00:16:09.709> feedback<00:16:14.050> now<00:16:15.050> luckily<00:16:15.260> we<00:16:15.649> received 00:16:15.940 --> 00:16:15.950 align:start position:0% user feedback now luckily we received 00:16:15.950 --> 00:16:19.360 align:start position:0% user feedback now luckily we received more<00:16:16.130> actionable<00:16:16.519> feedback<00:16:16.730> than<00:16:17.120> this<00:16:18.370> we 00:16:19.360 --> 00:16:19.370 align:start position:0% more actionable feedback than this we 00:16:19.370 --> 00:16:21.610 align:start position:0% more actionable feedback than this we got<00:16:19.519> some<00:16:19.670> github<00:16:20.089> issues<00:16:20.360> we<00:16:20.630> had<00:16:20.779> failed<00:16:21.410> to 00:16:21.610 --> 00:16:21.620 align:start position:0% got some github issues we had failed to 00:16:21.620 --> 00:16:23.819 align:start position:0% got some github issues we had failed to fetch<00:16:21.769> parent<00:16:22.130> block<00:16:22.310> stuff<00:16:22.940> is<00:16:23.120> missing 00:16:23.819 --> 00:16:23.829 align:start position:0% fetch parent block stuff is missing 00:16:23.829 --> 00:16:26.230 align:start position:0% fetch parent block stuff is missing balances<00:16:24.829> are<00:16:24.950> gone<00:16:25.190> I<00:16:25.459> can't<00:16:25.700> find<00:16:25.940> anything 00:16:26.230 --> 00:16:26.240 align:start position:0% balances are gone I can't find anything 00:16:26.240 --> 00:16:28.360 align:start position:0% balances are gone I can't find anything things<00:16:26.660> are<00:16:26.779> shutting<00:16:27.050> down<00:16:27.170> syncing<00:16:28.160> is<00:16:28.339> a 00:16:28.360 --> 00:16:28.370 align:start position:0% things are shutting down syncing is a 00:16:28.370 --> 00:16:31.750 align:start position:0% things are shutting down syncing is a major<00:16:28.880> issue<00:16:29.950> so<00:16:30.950> what<00:16:31.070> went<00:16:31.220> wrong<00:16:31.250> here<00:16:31.519> I 00:16:31.750 --> 00:16:31.760 align:start position:0% major issue so what went wrong here I 00:16:31.760 --> 00:16:40.930 align:start position:0% major issue so what went wrong here I mean<00:16:38.079> so<00:16:39.079> from<00:16:39.649> that<00:16:39.800> prior<00:16:40.130> list<00:16:40.610> of<00:16:40.760> docker 00:16:40.930 --> 00:16:40.940 align:start position:0% mean so from that prior list of docker 00:16:40.940 --> 00:16:43.120 align:start position:0% mean so from that prior list of docker images<00:16:41.270> we<00:16:41.390> built<00:16:41.600> for<00:16:41.779> for<00:16:42.440> gas<00:16:42.620> and<00:16:42.800> parity 00:16:43.120 --> 00:16:43.130 align:start position:0% images we built for for gas and parity 00:16:43.130 --> 00:16:44.800 align:start position:0% images we built for for gas and parity we<00:16:43.220> took<00:16:43.370> testing<00:16:43.700> very<00:16:43.910> seriously<00:16:44.270> we<00:16:44.450> tested 00:16:44.800 --> 00:16:44.810 align:start position:0% we took testing very seriously we tested 00:16:44.810 --> 00:16:48.010 align:start position:0% we took testing very seriously we tested all<00:16:44.959> of<00:16:45.050> these<00:16:45.320> things<00:16:45.589> we<00:16:46.459> tested<00:16:46.910> in<00:16:47.089> fira<00:16:47.779> we 00:16:48.010 --> 00:16:48.020 align:start position:0% all of these things we tested in fira we 00:16:48.020 --> 00:16:51.310 align:start position:0% all of these things we tested in fira we tested<00:16:48.440> local<00:16:48.980> and<00:16:49.160> remote<00:16:49.310> and<00:16:49.790> you<00:16:50.360> know<00:16:50.480> POA 00:16:51.310 --> 00:16:51.320 align:start position:0% tested local and remote and you know POA 00:16:51.320 --> 00:16:53.639 align:start position:0% tested local and remote and you know POA we<00:16:51.529> tested<00:16:51.829> the<00:16:51.890> whole<00:16:52.100> thing<00:16:52.370> but<00:16:52.970> in<00:16:53.089> the<00:16:53.180> end 00:16:53.639 --> 00:16:53.649 align:start position:0% we tested the whole thing but in the end 00:16:53.649 --> 00:16:56.440 align:start position:0% we tested the whole thing but in the end this<00:16:54.649> is<00:16:54.709> what<00:16:54.829> happened<00:16:55.220> we<00:16:56.120> had<00:16:56.209> an<00:16:56.300> issue 00:16:56.440 --> 00:16:56.450 align:start position:0% this is what happened we had an issue 00:16:56.450 --> 00:16:58.360 align:start position:0% this is what happened we had an issue that<00:16:57.050> was<00:16:57.170> specific<00:16:57.680> to<00:16:57.800> in<00:16:57.920> fira<00:16:58.160> and 00:16:58.360 --> 00:16:58.370 align:start position:0% that was specific to in fira and 00:16:58.370 --> 00:17:01.420 align:start position:0% that was specific to in fira and specific<00:16:58.850> to<00:16:58.970> maintenance<00:17:00.040> so<00:17:01.040> so<00:17:01.279> what 00:17:01.420 --> 00:17:01.430 align:start position:0% specific to maintenance so so what 00:17:01.430 --> 00:17:04.569 align:start position:0% specific to maintenance so so what happened<00:17:01.730> here<00:17:03.160> well<00:17:04.160> let's<00:17:04.189> talk<00:17:04.429> about 00:17:04.569 --> 00:17:04.579 align:start position:0% happened here well let's talk about 00:17:04.579 --> 00:17:05.409 align:start position:0% happened here well let's talk about Eastgate<00:17:05.030> logs 00:17:05.409 --> 00:17:05.419 align:start position:0% Eastgate logs 00:17:05.419 --> 00:17:08.860 align:start position:0% Eastgate logs our<00:17:06.319> system<00:17:06.740> works<00:17:06.919> by<00:17:07.419> when<00:17:08.419> we're<00:17:08.569> syncing 00:17:08.860 --> 00:17:08.870 align:start position:0% our system works by when we're syncing 00:17:08.870 --> 00:17:09.850 align:start position:0% our system works by when we're syncing synchronizing<00:17:09.470> the<00:17:09.530> logs<00:17:09.679> with<00:17:09.829> the 00:17:09.850 --> 00:17:09.860 align:start position:0% synchronizing the logs with the 00:17:09.860 --> 00:17:12.549 align:start position:0% synchronizing the logs with the blockchain<00:17:10.100> we<00:17:10.400> say<00:17:10.579> please<00:17:11.240> give<00:17:11.419> me<00:17:11.600> the<00:17:12.410> log 00:17:12.549 --> 00:17:12.559 align:start position:0% blockchain we say please give me the log 00:17:12.559 --> 00:17:14.230 align:start position:0% blockchain we say please give me the log please<00:17:12.890> give<00:17:13.040> me<00:17:13.100> new<00:17:13.189> blocks<00:17:13.429> inside<00:17:13.819> great<00:17:14.030> I 00:17:14.230 --> 00:17:14.240 align:start position:0% please give me new blocks inside great I 00:17:14.240 --> 00:17:16.090 align:start position:0% please give me new blocks inside great I just<00:17:14.630> found<00:17:14.720> a<00:17:14.839> new<00:17:14.959> block<00:17:15.140> block<00:17:15.380> 100<00:17:15.559> cool 00:17:16.090 --> 00:17:16.100 align:start position:0% just found a new block block 100 cool 00:17:16.100 --> 00:17:19.179 align:start position:0% just found a new block block 100 cool give<00:17:16.910> me<00:17:16.970> the<00:17:17.030> logs<00:17:17.209> for<00:17:17.360> this<00:17:17.480> block<00:17:18.189> here's 00:17:19.179 --> 00:17:19.189 align:start position:0% give me the logs for this block here's 00:17:19.189 --> 00:17:22.870 align:start position:0% give me the logs for this block here's an<00:17:19.309> array<00:17:19.550> of<00:17:19.699> logs<00:17:21.130> now<00:17:22.130> in<00:17:22.370> fear<00:17:22.640> it<00:17:22.730> does 00:17:22.870 --> 00:17:22.880 align:start position:0% an array of logs now in fear it does 00:17:22.880 --> 00:17:25.630 align:start position:0% an array of logs now in fear it does something<00:17:23.260> different<00:17:24.260> on<00:17:24.380> maintenance<00:17:24.640> in 00:17:25.630 --> 00:17:25.640 align:start position:0% something different on maintenance in 00:17:25.640 --> 00:17:27.250 align:start position:0% something different on maintenance in fact<00:17:26.059> they<00:17:26.150> do<00:17:26.209> something<00:17:26.630> that<00:17:26.929> I<00:17:27.079> would 00:17:27.250 --> 00:17:27.260 align:start position:0% fact they do something that I would 00:17:27.260 --> 00:17:30.610 align:start position:0% fact they do something that I would consider<00:17:27.350> to<00:17:27.770> be<00:17:28.000> just<00:17:29.000> a<00:17:29.150> little<00:17:29.330> bit<00:17:29.620> crazy 00:17:30.610 --> 00:17:30.620 align:start position:0% consider to be just a little bit crazy 00:17:30.620 --> 00:17:35.770 align:start position:0% consider to be just a little bit crazy in<00:17:32.230> fear<00:17:33.230> serves<00:17:33.559> over<00:17:33.890> a<00:17:34.790> hundred<00:17:35.330> thousand 00:17:35.770 --> 00:17:35.780 align:start position:0% in fear serves over a hundred thousand 00:17:35.780 --> 00:17:39.250 align:start position:0% in fear serves over a hundred thousand transactions<00:17:36.320> per<00:17:36.470> second<00:17:37.870> that's<00:17:38.870> the<00:17:39.110> thing 00:17:39.250 --> 00:17:39.260 align:start position:0% transactions per second that's the thing 00:17:39.260 --> 00:17:40.690 align:start position:0% transactions per second that's the thing that<00:17:39.380> it<00:17:39.530> is<00:17:39.590> different<00:17:39.919> that's<00:17:40.400> the<00:17:40.550> thing 00:17:40.690 --> 00:17:40.700 align:start position:0% that it is different that's the thing 00:17:40.700 --> 00:17:41.890 align:start position:0% that it is different that's the thing that<00:17:40.820> I<00:17:40.880> think<00:17:41.030> is<00:17:41.120> a<00:17:41.150> little<00:17:41.300> bit<00:17:41.510> wild<00:17:41.630> here 00:17:41.890 --> 00:17:41.900 align:start position:0% that I think is a little bit wild here 00:17:41.900 --> 00:17:43.750 align:start position:0% that I think is a little bit wild here and<00:17:42.470> to<00:17:42.590> accomplish<00:17:42.890> this<00:17:43.220> to<00:17:43.460> accomplish 00:17:43.750 --> 00:17:43.760 align:start position:0% and to accomplish this to accomplish 00:17:43.760 --> 00:17:46.870 align:start position:0% and to accomplish this to accomplish this<00:17:43.880> feat<00:17:44.500> they<00:17:45.500> need<00:17:45.650> more<00:17:46.010> than<00:17:46.400> one<00:17:46.610> server 00:17:46.870 --> 00:17:46.880 align:start position:0% this feat they need more than one server 00:17:46.880 --> 00:17:47.800 align:start position:0% this feat they need more than one server to<00:17:47.059> do<00:17:47.179> it 00:17:47.800 --> 00:17:47.810 align:start position:0% to do it 00:17:47.810 --> 00:17:49.630 align:start position:0% to do it if<00:17:48.050> I<00:17:48.140> need<00:17:48.320> a<00:17:48.350> huge<00:17:48.800> quantity<00:17:49.070> of<00:17:49.310> service<00:17:49.550> to 00:17:49.630 --> 00:17:49.640 align:start position:0% if I need a huge quantity of service to 00:17:49.640 --> 00:17:50.830 align:start position:0% if I need a huge quantity of service to do<00:17:49.730> it<00:17:49.820> in<00:17:49.970> fact<00:17:50.120> if<00:17:50.210> I<00:17:50.330> have<00:17:50.420> to<00:17:50.510> guess<00:17:50.660> how 00:17:50.830 --> 00:17:50.840 align:start position:0% do it in fact if I have to guess how 00:17:50.840 --> 00:17:51.970 align:start position:0% do it in fact if I have to guess how many<00:17:50.990> servers<00:17:51.200> there<00:17:51.380> have<00:17:51.530> it<00:17:51.620> this<00:17:51.740> isn't<00:17:51.920> a 00:17:51.970 --> 00:17:51.980 align:start position:0% many servers there have it this isn't a 00:17:51.980 --> 00:17:53.080 align:start position:0% many servers there have it this isn't a public<00:17:52.160> number<00:17:52.460> I<00:17:52.610> would<00:17:52.850> guess<00:17:53.000> they 00:17:53.080 --> 00:17:53.090 align:start position:0% public number I would guess they 00:17:53.090 --> 00:17:57.600 align:start position:0% public number I would guess they probably<00:17:53.150> have<00:17:53.450> like<00:17:53.630> well<00:17:53.870> let's<00:17:54.200> say<00:17:54.320> -<00:17:56.380> and 00:17:57.600 --> 00:17:57.610 align:start position:0% probably have like well let's say - and 00:17:57.610 --> 00:17:59.650 align:start position:0% probably have like well let's say - and in<00:17:58.610> order<00:17:58.790> to<00:17:58.910> have<00:17:59.000> more<00:17:59.210> than<00:17:59.270> one<00:17:59.450> server 00:17:59.650 --> 00:17:59.660 align:start position:0% in order to have more than one server 00:17:59.660 --> 00:18:01.360 align:start position:0% in order to have more than one server you're<00:17:59.750> gonna<00:17:59.870> need<00:17:59.990> a<00:18:00.050> proxy<00:18:00.470> and<00:18:00.830> so<00:18:01.160> let's 00:18:01.360 --> 00:18:01.370 align:start position:0% you're gonna need a proxy and so let's 00:18:01.370 --> 00:18:02.830 align:start position:0% you're gonna need a proxy and so let's walk<00:18:01.670> through<00:18:01.730> this<00:18:01.910> conversation<00:18:02.090> again<00:18:02.480> hey 00:18:02.830 --> 00:18:02.840 align:start position:0% walk through this conversation again hey 00:18:02.840 --> 00:18:03.850 align:start position:0% walk through this conversation again hey please<00:18:03.140> give<00:18:03.170> me<00:18:03.350> a<00:18:03.380> new<00:18:03.470> block 00:18:03.850 --> 00:18:03.860 align:start position:0% please give me a new block 00:18:03.860 --> 00:18:06.430 align:start position:0% please give me a new block here's<00:18:04.010> block<00:18:04.190> 101<00:18:04.820> great<00:18:05.780> can<00:18:05.960> I<00:18:06.020> get<00:18:06.080> logs 00:18:06.430 --> 00:18:06.440 align:start position:0% here's block 101 great can I get logs 00:18:06.440 --> 00:18:14.620 align:start position:0% here's block 101 great can I get logs for<00:18:06.650> block<00:18:06.800> 101<00:18:10.420> sorry<00:18:11.420> so<00:18:13.000> this<00:18:14.000> system 00:18:14.620 --> 00:18:14.630 align:start position:0% for block 101 sorry so this system 00:18:14.630 --> 00:18:16.480 align:start position:0% for block 101 sorry so this system doesn't<00:18:15.080> necessarily<00:18:15.770> have<00:18:16.310> the<00:18:16.460> same 00:18:16.480 --> 00:18:16.490 align:start position:0% doesn't necessarily have the same 00:18:16.490 --> 00:18:17.920 align:start position:0% doesn't necessarily have the same perspective<00:18:16.820> of<00:18:17.090> the<00:18:17.180> etherium<00:18:17.510> Network<00:18:17.780> as 00:18:17.920 --> 00:18:17.930 align:start position:0% perspective of the etherium Network as 00:18:17.930 --> 00:18:20.590 align:start position:0% perspective of the etherium Network as the<00:18:18.080> one<00:18:18.200> that<00:18:18.230> delivered<00:18:18.650> you<00:18:18.770> block<00:18:19.460> 101<00:18:19.880> and 00:18:20.590 --> 00:18:20.600 align:start position:0% the one that delivered you block 101 and 00:18:20.600 --> 00:18:22.570 align:start position:0% the one that delivered you block 101 and so<00:18:20.720> the<00:18:21.620> system<00:18:21.800> this<00:18:21.980> is<00:18:22.130> this<00:18:22.280> is<00:18:22.400> just<00:18:22.520> a 00:18:22.570 --> 00:18:22.580 align:start position:0% so the system this is this is just a 00:18:22.580 --> 00:18:24.550 align:start position:0% so the system this is this is just a standard<00:18:22.760> aetherium<00:18:23.240> node<00:18:23.420> thinks<00:18:24.230> to<00:18:24.290> itself 00:18:24.550 --> 00:18:24.560 align:start position:0% standard aetherium node thinks to itself 00:18:24.560 --> 00:18:26.170 align:start position:0% standard aetherium node thinks to itself well<00:18:24.920> what<00:18:25.040> the<00:18:25.100> hell<00:18:25.220> is<00:18:25.280> block<00:18:25.430> 101<00:18:25.820> but<00:18:26.120> the 00:18:26.170 --> 00:18:26.180 align:start position:0% well what the hell is block 101 but the 00:18:26.180 --> 00:18:28.360 align:start position:0% well what the hell is block 101 but the problem<00:18:26.450> is<00:18:26.570> is<00:18:26.660> it<00:18:26.750> doesn't<00:18:27.320> say<00:18:27.530> that<00:18:27.740> it 00:18:28.360 --> 00:18:28.370 align:start position:0% problem is is it doesn't say that it 00:18:28.370 --> 00:18:29.950 align:start position:0% problem is is it doesn't say that it doesn't<00:18:28.580> say<00:18:28.760> what<00:18:28.940> the<00:18:28.970> hell<00:18:29.150> is<00:18:29.270> block<00:18:29.450> 101 00:18:29.950 --> 00:18:29.960 align:start position:0% doesn't say what the hell is block 101 00:18:29.960 --> 00:18:33.880 align:start position:0% doesn't say what the hell is block 101 it<00:18:30.290> says<00:18:30.650> empty<00:18:31.190> array<00:18:32.440> so<00:18:33.440> I<00:18:33.470> don't<00:18:33.710> think 00:18:33.880 --> 00:18:33.890 align:start position:0% it says empty array so I don't think 00:18:33.890 --> 00:18:35.820 align:start position:0% it says empty array so I don't think this<00:18:34.010> is<00:18:34.090> inferiors<00:18:35.090> fault 00:18:35.820 --> 00:18:35.830 align:start position:0% this is inferiors fault 00:18:35.830 --> 00:18:39.700 align:start position:0% this is inferiors fault this<00:18:36.830> is<00:18:37.040> json-rpc<00:18:38.290> kind<00:18:39.290> of<00:18:39.380> not<00:18:39.650> necessarily 00:18:39.700 --> 00:18:39.710 align:start position:0% this is json-rpc kind of not necessarily 00:18:39.710 --> 00:18:41.950 align:start position:0% this is json-rpc kind of not necessarily lying<00:18:40.310> but<00:18:41.180> not<00:18:41.300> really<00:18:41.480> telling<00:18:41.660> the<00:18:41.750> truth 00:18:41.950 --> 00:18:41.960 align:start position:0% lying but not really telling the truth 00:18:41.960 --> 00:18:42.840 align:start position:0% lying but not really telling the truth either 00:18:42.840 --> 00:18:42.850 align:start position:0% either 00:18:42.850 --> 00:18:44.860 align:start position:0% either so<00:18:43.850> what<00:18:43.940> solutions<00:18:44.300> do<00:18:44.390> we<00:18:44.480> have<00:18:44.630> for<00:18:44.750> this 00:18:44.860 --> 00:18:44.870 align:start position:0% so what solutions do we have for this 00:18:44.870 --> 00:18:47.950 align:start position:0% so what solutions do we have for this well<00:18:45.460> we<00:18:46.460> could<00:18:46.580> ask<00:18:46.670> for<00:18:46.790> all<00:18:46.970> logs<00:18:47.240> and<00:18:47.540> just 00:18:47.950 --> 00:18:47.960 align:start position:0% well we could ask for all logs and just 00:18:47.960 --> 00:18:49.510 align:start position:0% well we could ask for all logs and just throw<00:18:48.170> everything<00:18:48.350> away<00:18:48.650> and<00:18:48.770> then<00:18:49.100> filter 00:18:49.510 --> 00:18:49.520 align:start position:0% throw everything away and then filter 00:18:49.520 --> 00:18:51.010 align:start position:0% throw everything away and then filter out<00:18:49.760> the<00:18:49.910> augur<00:18:50.180> logs<00:18:50.330> ourselves<00:18:50.720> but<00:18:50.840> know 00:18:51.010 --> 00:18:51.020 align:start position:0% out the augur logs ourselves but know 00:18:51.020 --> 00:18:52.900 align:start position:0% out the augur logs ourselves but know that<00:18:51.170> the<00:18:51.260> presence<00:18:51.620> of<00:18:51.710> logs<00:18:51.950> means<00:18:52.310> did<00:18:52.820> we 00:18:52.900 --> 00:18:52.910 align:start position:0% that the presence of logs means did we 00:18:52.910 --> 00:18:55.840 align:start position:0% that the presence of logs means did we talk<00:18:53.090> to<00:18:53.210> a<00:18:53.240> node<00:18:53.450> that<00:18:53.600> had<00:18:53.840> that<00:18:54.260> block<00:18:54.850> but 00:18:55.840 --> 00:18:55.850 align:start position:0% talk to a node that had that block but 00:18:55.850 --> 00:18:57.970 align:start position:0% talk to a node that had that block but we<00:18:55.940> get<00:18:56.090> empty<00:18:56.330> blocks<00:18:56.570> all<00:18:56.750> the<00:18:56.780> time<00:18:57.020> okay 00:18:57.970 --> 00:18:57.980 align:start position:0% we get empty blocks all the time okay 00:18:57.980 --> 00:18:59.710 align:start position:0% we get empty blocks all the time okay but<00:18:58.460> maybe<00:18:58.640> we<00:18:58.820> could<00:18:58.910> use<00:18:59.060> like<00:18:59.240> the<00:18:59.510> logs 00:18:59.710 --> 00:18:59.720 align:start position:0% but maybe we could use like the logs 00:18:59.720 --> 00:19:01.390 align:start position:0% but maybe we could use like the logs bloom<00:19:00.080> filter<00:19:00.410> and<00:19:00.560> if<00:19:00.620> it's<00:19:00.740> empty<00:19:00.980> we<00:19:01.190> know 00:19:01.390 --> 00:19:01.400 align:start position:0% bloom filter and if it's empty we know 00:19:01.400 --> 00:19:03.700 align:start position:0% bloom filter and if it's empty we know but<00:19:01.940> it's<00:19:02.060> still<00:19:02.300> a<00:19:02.510> lot<00:19:02.690> of<00:19:02.810> logs<00:19:02.990> so<00:19:03.560> how 00:19:03.700 --> 00:19:03.710 align:start position:0% but it's still a lot of logs so how 00:19:03.710 --> 00:19:05.410 align:start position:0% but it's still a lot of logs so how about<00:19:03.830> we<00:19:04.070> get<00:19:04.190> augur<00:19:04.460> logs<00:19:04.730> and<00:19:04.910> crypto 00:19:05.410 --> 00:19:05.420 align:start position:0% about we get augur logs and crypto 00:19:05.420 --> 00:19:06.880 align:start position:0% about we get augur logs and crypto kitties<00:19:05.690> because<00:19:06.260> we<00:19:06.350> know<00:19:06.530> the<00:19:06.650> crypto 00:19:06.880 --> 00:19:06.890 align:start position:0% kitties because we know the crypto 00:19:06.890 --> 00:19:08.880 align:start position:0% kitties because we know the crypto kiddies<00:19:07.100> has<00:19:07.250> lots<00:19:07.460> of<00:19:07.580> events<00:19:07.760> all<00:19:08.000> the<00:19:08.030> time 00:19:08.880 --> 00:19:08.890 align:start position:0% kiddies has lots of events all the time 00:19:08.890 --> 00:19:10.870 align:start position:0% kiddies has lots of events all the time so<00:19:09.890> we're<00:19:09.980> gonna<00:19:10.070> get<00:19:10.250> like<00:19:10.400> a<00:19:10.430> totally 00:19:10.870 --> 00:19:10.880 align:start position:0% so we're gonna get like a totally 00:19:10.880 --> 00:19:13.570 align:start position:0% so we're gonna get like a totally adorable<00:19:11.150> cat<00:19:11.480> in<00:19:11.720> our<00:19:12.140> JSON<00:19:12.470> response<00:19:12.860> but 00:19:13.570 --> 00:19:13.580 align:start position:0% adorable cat in our JSON response but 00:19:13.580 --> 00:19:15.190 align:start position:0% adorable cat in our JSON response but we're<00:19:13.670> gonna<00:19:13.760> discard<00:19:14.150> it<00:19:14.300> use<00:19:14.570> that<00:19:14.900> as<00:19:15.110> our 00:19:15.190 --> 00:19:15.200 align:start position:0% we're gonna discard it use that as our 00:19:15.200 --> 00:19:17.320 align:start position:0% we're gonna discard it use that as our indication<00:19:15.770> that<00:19:16.250> we<00:19:16.490> talked<00:19:16.760> to<00:19:16.970> a<00:19:17.000> proper 00:19:17.320 --> 00:19:17.330 align:start position:0% indication that we talked to a proper 00:19:17.330 --> 00:19:19.900 align:start position:0% indication that we talked to a proper note<00:19:17.510> and<00:19:18.130> we<00:19:19.130> seriously<00:19:19.460> consider<00:19:19.790> this 00:19:19.900 --> 00:19:19.910 align:start position:0% note and we seriously consider this 00:19:19.910 --> 00:19:22.140 align:start position:0% note and we seriously consider this probably<00:19:20.180> more<00:19:20.330> than<00:19:20.450> I'm<00:19:20.570> willing<00:19:20.780> to<00:19:20.810> admit 00:19:22.140 --> 00:19:22.150 align:start position:0% probably more than I'm willing to admit 00:19:22.150 --> 00:19:24.850 align:start position:0% probably more than I'm willing to admit but<00:19:23.150> the<00:19:23.480> problem<00:19:23.870> is<00:19:23.990> is<00:19:24.110> I<00:19:24.350> don't<00:19:24.560> want<00:19:24.710> to 00:19:24.850 --> 00:19:24.860 align:start position:0% but the problem is is I don't want to 00:19:24.860 --> 00:19:27.580 align:start position:0% but the problem is is I don't want to wake<00:19:25.160> up<00:19:25.310> one<00:19:25.460> day<00:19:25.490> and<00:19:25.900> write<00:19:26.900> this<00:19:27.110> comments 00:19:27.580 --> 00:19:27.590 align:start position:0% wake up one day and write this comments 00:19:27.590 --> 00:19:33.439 align:start position:0% wake up one day and write this comments as<00:19:27.740> a<00:19:27.920> response<00:19:28.280> to<00:19:28.370> a<00:19:28.460> data<00:19:28.670> quality<00:19:28.820> issue 00:19:33.439 --> 00:19:33.449 align:start position:0% 00:19:33.449 --> 00:19:35.879 align:start position:0% so<00:19:34.449> a<00:19:34.479> solution<00:19:34.659> would<00:19:34.959> actually<00:19:35.229> work<00:19:35.379> well 00:19:35.879 --> 00:19:35.889 align:start position:0% so a solution would actually work well 00:19:35.889 --> 00:19:37.619 align:start position:0% so a solution would actually work well what<00:19:36.039> if<00:19:36.129> every<00:19:36.369> time<00:19:36.399> you<00:19:36.579> got<00:19:36.759> a<00:19:37.179> blog<00:19:37.599> that 00:19:37.619 --> 00:19:37.629 align:start position:0% what if every time you got a blog that 00:19:37.629 --> 00:19:39.060 align:start position:0% what if every time you got a blog that was<00:19:37.929> empty<00:19:38.169> it<00:19:38.379> was<00:19:38.529> like<00:19:38.619> you<00:19:38.709> know<00:19:38.799> empty 00:19:39.060 --> 00:19:39.070 align:start position:0% was empty it was like you know empty 00:19:39.070 --> 00:19:40.919 align:start position:0% was empty it was like you know empty response<00:19:39.429> you<00:19:40.089> remembered<00:19:40.479> that<00:19:40.570> and<00:19:40.809> then 00:19:40.919 --> 00:19:40.929 align:start position:0% response you remembered that and then 00:19:40.929 --> 00:19:42.389 align:start position:0% response you remembered that and then the<00:19:41.169> next<00:19:41.199> time<00:19:41.559> you<00:19:41.649> heard<00:19:41.829> about<00:19:41.889> the<00:19:42.099> next 00:19:42.389 --> 00:19:42.399 align:start position:0% the next time you heard about the next 00:19:42.399 --> 00:19:44.969 align:start position:0% the next time you heard about the next block<00:19:42.609> you<00:19:43.299> made<00:19:43.539> a<00:19:43.570> range<00:19:43.839> request<00:19:44.259> for<00:19:44.559> 101 00:19:44.969 --> 00:19:44.979 align:start position:0% block you made a range request for 101 00:19:44.979 --> 00:19:47.279 align:start position:0% block you made a range request for 101 to<00:19:45.099> 102<00:19:45.249> and<00:19:45.669> then<00:19:45.999> if<00:19:46.059> you<00:19:46.149> saw<00:19:46.359> 102<00:19:46.690> you<00:19:46.989> knew 00:19:47.279 --> 00:19:47.289 align:start position:0% to 102 and then if you saw 102 you knew 00:19:47.289 --> 00:19:48.659 align:start position:0% to 102 and then if you saw 102 you knew that<00:19:47.440> you<00:19:47.529> actually<00:19:47.679> did<00:19:48.099> hit<00:19:48.279> one<00:19:48.309> of<00:19:48.549> what 00:19:48.659 --> 00:19:48.669 align:start position:0% that you actually did hit one of what 00:19:48.669 --> 00:19:50.659 align:start position:0% that you actually did hit one of what it's<00:19:48.969> just<00:19:49.029> it's<00:19:49.239> getting<00:19:49.329> crazy<00:19:49.659> right<00:19:49.809> so 00:19:50.659 --> 00:19:50.669 align:start position:0% it's just it's getting crazy right so 00:19:50.669 --> 00:19:53.759 align:start position:0% it's just it's getting crazy right so what<00:19:51.669> we<00:19:51.759> did<00:19:51.909> was<00:19:52.539> there<00:19:53.049> was<00:19:53.169> this<00:19:53.229> AIP<00:19:53.529> out 00:19:53.759 --> 00:19:53.769 align:start position:0% what we did was there was this AIP out 00:19:53.769 --> 00:19:54.959 align:start position:0% what we did was there was this AIP out there<00:19:53.949> that<00:19:54.070> had<00:19:54.159> been<00:19:54.249> out<00:19:54.369> there<00:19:54.489> for<00:19:54.669> over<00:19:54.699> a 00:19:54.959 --> 00:19:54.969 align:start position:0% there that had been out there for over a 00:19:54.969 --> 00:19:57.119 align:start position:0% there that had been out there for over a year<00:19:55.029> that<00:19:55.629> said<00:19:55.809> how<00:19:56.320> about<00:19:56.409> we<00:19:56.619> query<00:19:56.859> blocks 00:19:57.119 --> 00:19:57.129 align:start position:0% year that said how about we query blocks 00:19:57.129 --> 00:19:58.949 align:start position:0% year that said how about we query blocks by<00:19:57.489> block<00:19:57.699> hash<00:19:57.940> this<00:19:58.179> is<00:19:58.269> a<00:19:58.299> more<00:19:58.629> unique 00:19:58.949 --> 00:19:58.959 align:start position:0% by block hash this is a more unique 00:19:58.959 --> 00:20:01.259 align:start position:0% by block hash this is a more unique identifier<00:19:59.440> and<00:19:59.759> more<00:20:00.759> importantly<00:20:01.089> how 00:20:01.259 --> 00:20:01.269 align:start position:0% identifier and more importantly how 00:20:01.269 --> 00:20:03.269 align:start position:0% identifier and more importantly how about<00:20:01.419> when<00:20:01.570> it's<00:20:01.719> not<00:20:01.869> there<00:20:02.139> you<00:20:02.919> let<00:20:03.159> the 00:20:03.269 --> 00:20:03.279 align:start position:0% about when it's not there you let the 00:20:03.279 --> 00:20:04.889 align:start position:0% about when it's not there you let the person<00:20:03.399> know<00:20:03.609> you<00:20:03.849> you<00:20:04.029> don't<00:20:04.239> you<00:20:04.509> don't<00:20:04.659> kind 00:20:04.889 --> 00:20:04.899 align:start position:0% person know you you don't you don't kind 00:20:04.899 --> 00:20:06.389 align:start position:0% person know you you don't you don't kind of<00:20:04.989> fuzz<00:20:05.409> over<00:20:05.440> the<00:20:05.829> fact<00:20:06.039> that<00:20:06.099> you've<00:20:06.249> never 00:20:06.389 --> 00:20:06.399 align:start position:0% of fuzz over the fact that you've never 00:20:06.399 --> 00:20:07.949 align:start position:0% of fuzz over the fact that you've never heard<00:20:06.609> of<00:20:06.729> that<00:20:06.789> block<00:20:07.059> you<00:20:07.389> deliver<00:20:07.749> that<00:20:07.809> to 00:20:07.949 --> 00:20:07.959 align:start position:0% heard of that block you deliver that to 00:20:07.959 --> 00:20:09.209 align:start position:0% heard of that block you deliver that to the<00:20:07.989> client<00:20:08.319> so<00:20:08.440> they<00:20:08.619> can<00:20:08.799> make<00:20:08.949> the<00:20:09.069> right 00:20:09.209 --> 00:20:09.219 align:start position:0% the client so they can make the right 00:20:09.219 --> 00:20:11.999 align:start position:0% the client so they can make the right choice<00:20:09.459> on<00:20:09.609> their<00:20:09.729> side<00:20:10.589> if<00:20:11.589> anybody<00:20:11.889> heard 00:20:11.999 --> 00:20:12.009 align:start position:0% choice on their side if anybody heard 00:20:12.009 --> 00:20:13.769 align:start position:0% choice on their side if anybody heard Jack<00:20:12.219> Peterson's<00:20:12.729> talked<00:20:12.999> last<00:20:13.359> year<00:20:13.509> about 00:20:13.769 --> 00:20:13.779 align:start position:0% Jack Peterson's talked last year about 00:20:13.779 --> 00:20:15.239 align:start position:0% Jack Peterson's talked last year about bounties<00:20:14.259> I<00:20:14.469> think<00:20:14.799> this<00:20:14.889> is<00:20:14.979> one<00:20:15.099> of<00:20:15.159> the 00:20:15.239 --> 00:20:15.249 align:start position:0% bounties I think this is one of the 00:20:15.249 --> 00:20:16.709 align:start position:0% bounties I think this is one of the critical<00:20:15.369> success<00:20:15.729> stories<00:20:16.179> of<00:20:16.359> bounties 00:20:16.709 --> 00:20:16.719 align:start position:0% critical success stories of bounties 00:20:16.719 --> 00:20:18.269 align:start position:0% critical success stories of bounties here's<00:20:17.379> an<00:20:17.499> EIP<00:20:17.679> that<00:20:17.919> had<00:20:18.009> been<00:20:18.099> sitting 00:20:18.269 --> 00:20:18.279 align:start position:0% here's an EIP that had been sitting 00:20:18.279 --> 00:20:21.659 align:start position:0% here's an EIP that had been sitting there<00:20:18.399> for<00:20:18.969> 15<00:20:19.629> months<00:20:19.829> after<00:20:20.829> auger 00:20:21.659 --> 00:20:21.669 align:start position:0% there for 15 months after auger 00:20:21.669 --> 00:20:24.029 align:start position:0% there for 15 months after auger experienced<00:20:22.239> these<00:20:22.359> issues<00:20:22.690> that<00:20:23.409> a<00:20:23.589> IP<00:20:23.889> we 00:20:24.029 --> 00:20:24.039 align:start position:0% experienced these issues that a IP we 00:20:24.039 --> 00:20:25.349 align:start position:0% experienced these issues that a IP we got<00:20:24.159> you'll<00:20:24.369> be<00:20:24.459> able<00:20:24.549> to<00:20:24.669> use<00:20:24.789> bounties<00:20:25.149> and 00:20:25.349 --> 00:20:25.359 align:start position:0% got you'll be able to use bounties and 00:20:25.359 --> 00:20:28.409 align:start position:0% got you'll be able to use bounties and engaging<00:20:25.629> the<00:20:25.839> network<00:20:26.379> to<00:20:26.819> get<00:20:27.819> it<00:20:27.909> merged<00:20:28.209> in 00:20:28.409 --> 00:20:28.419 align:start position:0% engaging the network to get it merged in 00:20:28.419 --> 00:20:30.749 align:start position:0% engaging the network to get it merged in two<00:20:28.599> weeks<00:20:28.809> and<00:20:29.339> implemented<00:20:30.339> in<00:20:30.429> GAF<00:20:30.609> in 00:20:30.749 --> 00:20:30.759 align:start position:0% two weeks and implemented in GAF in 00:20:30.759 --> 00:20:33.869 align:start position:0% two weeks and implemented in GAF in parity<00:20:31.119> in<00:20:31.239> six<00:20:32.009> that<00:20:33.009> is<00:20:33.129> an<00:20:33.249> excellent 00:20:33.869 --> 00:20:33.879 align:start position:0% parity in six that is an excellent 00:20:33.879 --> 00:20:36.299 align:start position:0% parity in six that is an excellent response<00:20:34.059> right<00:20:34.690> and<00:20:35.619> that<00:20:35.739> that's<00:20:35.919> a<00:20:36.069> killer 00:20:36.299 --> 00:20:36.309 align:start position:0% response right and that that's a killer 00:20:36.309 --> 00:20:40.079 align:start position:0% response right and that that's a killer ecosystem<00:20:36.879> and<00:20:37.659> so<00:20:38.619> but<00:20:39.549> in<00:20:39.639> the<00:20:39.699> meantime<00:20:39.849> we 00:20:40.079 --> 00:20:40.089 align:start position:0% ecosystem and so but in the meantime we 00:20:40.089 --> 00:20:41.489 align:start position:0% ecosystem and so but in the meantime we had<00:20:40.179> to<00:20:40.269> say<00:20:40.359> oK<00:20:40.599> you've<00:20:40.629> got<00:20:40.869> one<00:20:41.079> node<00:20:41.289> you're 00:20:41.489 --> 00:20:41.499 align:start position:0% had to say oK you've got one node you're 00:20:41.499 --> 00:20:43.519 align:start position:0% had to say oK you've got one node you're good<00:20:41.679> to<00:20:41.769> go<00:20:41.799> if<00:20:42.099> you<00:20:42.279> have<00:20:42.429> two<00:20:42.699> or<00:20:42.729> more<00:20:42.879> nodes 00:20:43.519 --> 00:20:43.529 align:start position:0% good to go if you have two or more nodes 00:20:43.529 --> 00:20:45.209 align:start position:0% good to go if you have two or more nodes whether<00:20:44.529> you're<00:20:44.649> in<00:20:44.709> fear<00:20:44.859> where<00:20:45.099> you're 00:20:45.209 --> 00:20:45.219 align:start position:0% whether you're in fear where you're 00:20:45.219 --> 00:20:47.159 align:start position:0% whether you're in fear where you're there<00:20:45.309> anybody<00:20:45.819> we<00:20:46.359> can't<00:20:46.569> do<00:20:46.690> that<00:20:46.779> until<00:20:46.959> the 00:20:47.159 --> 00:20:47.169 align:start position:0% there anybody we can't do that until the 00:20:47.169 --> 00:20:50.579 align:start position:0% there anybody we can't do that until the CIP<00:20:47.440> gets<00:20:47.709> merged<00:20:49.289> then<00:20:50.289> we've<00:20:50.379> got<00:20:50.469> other 00:20:50.579 --> 00:20:50.589 align:start position:0% CIP gets merged then we've got other 00:20:50.589 --> 00:20:53.219 align:start position:0% CIP gets merged then we've got other issues<00:20:50.739> we<00:20:51.069> had<00:20:51.190> parity<00:20:52.029> there<00:20:52.629> was<00:20:52.719> a<00:20:52.779> parity 00:20:53.219 --> 00:20:53.229 align:start position:0% issues we had parity there was a parity 00:20:53.229 --> 00:20:54.989 align:start position:0% issues we had parity there was a parity specific<00:20:53.679> issue<00:20:53.859> when<00:20:54.519> people<00:20:54.759> started 00:20:54.989 --> 00:20:54.999 align:start position:0% specific issue when people started 00:20:54.999 --> 00:20:56.099 align:start position:0% specific issue when people started launching<00:20:55.269> their<00:20:55.419> new<00:20:55.449> nodes<00:20:55.749> and<00:20:55.869> I<00:20:55.929> didn't 00:20:56.099 --> 00:20:56.109 align:start position:0% launching their new nodes and I didn't 00:20:56.109 --> 00:20:57.389 align:start position:0% launching their new nodes and I didn't understand<00:20:56.409> this<00:20:56.469> because<00:20:56.679> remember<00:20:56.739> like<00:20:57.279> I 00:20:57.389 --> 00:20:57.399 align:start position:0% understand this because remember like I 00:20:57.399 --> 00:20:59.069 align:start position:0% understand this because remember like I come<00:20:57.579> from<00:20:57.669> kovin<00:20:57.999> like<00:20:58.119> parodies<00:20:58.479> my<00:20:58.629> jam<00:20:58.899> I 00:20:59.069 --> 00:20:59.079 align:start position:0% come from kovin like parodies my jam I 00:20:59.079 --> 00:21:00.629 align:start position:0% come from kovin like parodies my jam I know<00:20:59.169> this<00:20:59.709> works<00:20:59.919> with<00:21:00.069> parity<00:21:00.369> so<00:21:00.489> what 00:21:00.629 --> 00:21:00.639 align:start position:0% know this works with parity so what 00:21:00.639 --> 00:21:01.259 align:start position:0% know this works with parity so what happens<00:21:00.909> here 00:21:01.259 --> 00:21:01.269 align:start position:0% happens here 00:21:01.269 --> 00:21:02.939 align:start position:0% happens here how<00:21:01.719> does<00:21:01.869> parity<00:21:02.229> getting<00:21:02.469> these<00:21:02.589> exact<00:21:02.889> same 00:21:02.939 --> 00:21:02.949 align:start position:0% how does parity getting these exact same 00:21:02.949 --> 00:21:06.180 align:start position:0% how does parity getting these exact same issues<00:21:03.459> a<00:21:03.639> single<00:21:04.569> node<00:21:05.009> let's<00:21:06.009> talk<00:21:06.129> about 00:21:06.180 --> 00:21:06.190 align:start position:0% issues a single node let's talk about 00:21:06.190 --> 00:21:08.789 align:start position:0% issues a single node let's talk about leaf<00:21:06.369> get<00:21:06.579> logs<00:21:06.789> when<00:21:07.449> you<00:21:07.539> synchronize<00:21:08.019> with 00:21:08.789 --> 00:21:08.799 align:start position:0% leaf get logs when you synchronize with 00:21:08.799 --> 00:21:10.049 align:start position:0% leaf get logs when you synchronize with the<00:21:08.859> etherion<00:21:09.190> blockchain<00:21:09.609> it<00:21:09.909> goes 00:21:10.049 --> 00:21:10.059 align:start position:0% the etherion blockchain it goes 00:21:10.059 --> 00:21:11.459 align:start position:0% the etherion blockchain it goes something<00:21:10.329> like<00:21:10.359> this<00:21:10.539> you<00:21:10.719> start<00:21:10.779> at<00:21:11.019> 0<00:21:11.199> you 00:21:11.459 --> 00:21:11.469 align:start position:0% something like this you start at 0 you 00:21:11.469 --> 00:21:14.789 align:start position:0% something like this you start at 0 you go<00:21:11.949> to<00:21:11.979> 6.6<00:21:12.609> million<00:21:12.789> you're<00:21:13.209> good<00:21:13.469> the<00:21:14.469> parity 00:21:14.789 --> 00:21:14.799 align:start position:0% go to 6.6 million you're good the parity 00:21:14.799 --> 00:21:15.869 align:start position:0% go to 6.6 million you're good the parity developed<00:21:15.099> something<00:21:15.219> called<00:21:15.309> a<00:21:15.459> warp<00:21:15.639> sync 00:21:15.869 --> 00:21:15.879 align:start position:0% developed something called a warp sync 00:21:15.879 --> 00:21:19.289 align:start position:0% developed something called a warp sync where<00:21:16.569> you<00:21:17.349> first<00:21:17.739> sync<00:21:18.159> you<00:21:18.699> so<00:21:18.999> you<00:21:19.059> pick<00:21:19.269> a 00:21:19.289 --> 00:21:19.299 align:start position:0% where you first sync you so you pick a 00:21:19.299 --> 00:21:20.969 align:start position:0% where you first sync you so you pick a points<00:21:19.629> in<00:21:19.749> the<00:21:19.839> middle<00:21:20.019> pretty<00:21:20.679> close<00:21:20.859> to 00:21:20.969 --> 00:21:20.979 align:start position:0% points in the middle pretty close to 00:21:20.979 --> 00:21:23.969 align:start position:0% points in the middle pretty close to head<00:21:21.129> and<00:21:21.459> you<00:21:21.639> sink<00:21:21.909> that<00:21:21.940> part<00:21:22.269> first<00:21:22.979> then 00:21:23.969 --> 00:21:23.979 align:start position:0% head and you sink that part first then 00:21:23.979 --> 00:21:25.709 align:start position:0% head and you sink that part first then you<00:21:24.849> say<00:21:25.059> hey<00:21:25.209> I'm<00:21:25.329> good<00:21:25.479> to<00:21:25.569> go 00:21:25.709 --> 00:21:25.719 align:start position:0% you say hey I'm good to go 00:21:25.719 --> 00:21:28.889 align:start position:0% you say hey I'm good to go and<00:21:25.959> later<00:21:26.349> you<00:21:26.559> backfill<00:21:27.129> from<00:21:27.609> zero<00:21:28.569> to<00:21:28.659> that 00:21:28.889 --> 00:21:28.899 align:start position:0% and later you backfill from zero to that 00:21:28.899 --> 00:21:32.879 align:start position:0% and later you backfill from zero to that warp<00:21:29.079> sync<00:21:29.259> start<00:21:29.469> point<00:21:31.589> but<00:21:32.589> you<00:21:32.679> think 00:21:32.879 --> 00:21:32.889 align:start position:0% warp sync start point but you think 00:21:32.889 --> 00:21:33.869 align:start position:0% warp sync start point but you think you're<00:21:33.069> synchronized<00:21:33.459> when<00:21:33.639> you're<00:21:33.759> right 00:21:33.869 --> 00:21:33.879 align:start position:0% you're synchronized when you're right 00:21:33.879 --> 00:21:35.789 align:start position:0% you're synchronized when you're right here<00:21:34.119> and<00:21:34.299> if<00:21:34.599> you<00:21:34.659> issue<00:21:34.809> with<00:21:35.019> get<00:21:35.169> logs<00:21:35.379> for 00:21:35.789 --> 00:21:35.799 align:start position:0% here and if you issue with get logs for 00:21:35.799 --> 00:21:38.309 align:start position:0% here and if you issue with get logs for this<00:21:36.039> you've<00:21:36.699> got<00:21:36.849> your<00:21:36.940> logs<00:21:37.149> back<00:21:37.359> if<00:21:38.169> you 00:21:38.309 --> 00:21:38.319 align:start position:0% this you've got your logs back if you 00:21:38.319 --> 00:21:40.319 align:start position:0% this you've got your logs back if you issue<00:21:38.619> a<00:21:38.709> get<00:21:38.919> logs<00:21:39.099> back<00:21:39.309> here<00:21:39.639> you<00:21:39.940> get<00:21:40.059> empty 00:21:40.319 --> 00:21:40.329 align:start position:0% issue a get logs back here you get empty 00:21:40.329 --> 00:21:42.779 align:start position:0% issue a get logs back here you get empty array<00:21:40.539> again<00:21:40.779> and<00:21:41.679> if<00:21:41.950> you<00:21:42.039> issue<00:21:42.219> a<00:21:42.339> get<00:21:42.609> logs 00:21:42.779 --> 00:21:42.789 align:start position:0% array again and if you issue a get logs 00:21:42.789 --> 00:21:44.410 align:start position:0% array again and if you issue a get logs that<00:21:42.999> spans<00:21:43.359> this<00:21:43.569> point 00:21:44.410 --> 00:21:44.420 align:start position:0% that spans this point 00:21:44.420 --> 00:21:46.510 align:start position:0% that spans this point you<00:21:44.690> get<00:21:44.840> half<00:21:45.140> of<00:21:45.350> the<00:21:46.100> logs<00:21:46.309> you<00:21:46.400> were 00:21:46.510 --> 00:21:46.520 align:start position:0% you get half of the logs you were 00:21:46.520 --> 00:21:48.789 align:start position:0% you get half of the logs you were expecting<00:21:46.990> and<00:21:47.990> you<00:21:48.049> can<00:21:48.200> imagine<00:21:48.410> the<00:21:48.620> kind 00:21:48.789 --> 00:21:48.799 align:start position:0% expecting and you can imagine the kind 00:21:48.799 --> 00:21:50.410 align:start position:0% expecting and you can imagine the kind of<00:21:48.830> havoc<00:21:49.100> this<00:21:49.220> wrecks<00:21:49.429> on<00:21:49.549> a<00:21:49.580> system<00:21:49.970> that 00:21:50.410 --> 00:21:50.420 align:start position:0% of havoc this wrecks on a system that 00:21:50.420 --> 00:21:54.100 align:start position:0% of havoc this wrecks on a system that was<00:21:50.510> deployed<00:21:50.809> right<00:21:50.990> here<00:21:51.580> so<00:21:52.900> we<00:21:53.900> made<00:21:54.049> sure 00:21:54.100 --> 00:21:54.110 align:start position:0% was deployed right here so we made sure 00:21:54.110 --> 00:21:56.530 align:start position:0% was deployed right here so we made sure we<00:21:54.200> documented<00:21:54.710> this<00:21:54.799> and<00:21:54.920> I<00:21:54.980> read<00:21:55.160> me<00:21:55.540> we 00:21:56.530 --> 00:21:56.540 align:start position:0% we documented this and I read me we 00:21:56.540 --> 00:21:58.270 align:start position:0% we documented this and I read me we tried<00:21:56.720> to<00:21:56.929> detect<00:21:57.170> detect<00:21:57.799> the<00:21:57.890> behavior 00:21:58.270 --> 00:21:58.280 align:start position:0% tried to detect detect the behavior 00:21:58.280 --> 00:22:01.060 align:start position:0% tried to detect detect the behavior automatically<00:21:59.470> but<00:22:00.470> really<00:22:00.799> the<00:22:00.920> solution 00:22:01.060 --> 00:22:01.070 align:start position:0% automatically but really the solution 00:22:01.070 --> 00:22:03.070 align:start position:0% automatically but really the solution was<00:22:01.490> we've<00:22:01.850> been<00:22:01.970> working<00:22:02.330> with<00:22:02.360> parody<00:22:02.929> and 00:22:03.070 --> 00:22:03.080 align:start position:0% was we've been working with parody and 00:22:03.080 --> 00:22:04.419 align:start position:0% was we've been working with parody and this<00:22:03.320> is<00:22:03.410> actually<00:22:03.650> scheduled<00:22:04.040> for<00:22:04.190> a<00:22:04.220> future 00:22:04.419 --> 00:22:04.429 align:start position:0% this is actually scheduled for a future 00:22:04.429 --> 00:22:06.250 align:start position:0% this is actually scheduled for a future release<00:22:04.730> to<00:22:05.330> deliver<00:22:05.870> the<00:22:06.049> correct 00:22:06.250 --> 00:22:06.260 align:start position:0% release to deliver the correct 00:22:06.260 --> 00:22:07.600 align:start position:0% release to deliver the correct information<00:22:06.440> to<00:22:06.799> volunteer<00:22:07.429> more 00:22:07.600 --> 00:22:07.610 align:start position:0% information to volunteer more 00:22:07.610 --> 00:22:10.750 align:start position:0% information to volunteer more information<00:22:08.179> and<00:22:09.070> we've<00:22:10.070> seen<00:22:10.220> some<00:22:10.429> similar 00:22:10.750 --> 00:22:10.760 align:start position:0% information and we've seen some similar 00:22:10.760 --> 00:22:13.210 align:start position:0% information and we've seen some similar issues<00:22:11.120> on<00:22:11.360> the<00:22:11.570> gift<00:22:11.750> RPC<00:22:12.679> JSON<00:22:13.130> RPC 00:22:13.210 --> 00:22:13.220 align:start position:0% issues on the gift RPC JSON RPC 00:22:13.220 --> 00:22:16.659 align:start position:0% issues on the gift RPC JSON RPC interface<00:22:13.490> so<00:22:14.270> but<00:22:14.390> eath<00:22:14.540> call<00:22:15.429> when<00:22:16.429> you<00:22:16.520> call 00:22:16.659 --> 00:22:16.669 align:start position:0% interface so but eath call when you call 00:22:16.669 --> 00:22:18.370 align:start position:0% interface so but eath call when you call a<00:22:16.700> function<00:22:16.790> that<00:22:17.270> revert<00:22:17.840> Svea<00:22:18.110> that<00:22:18.230> eath 00:22:18.370 --> 00:22:18.380 align:start position:0% a function that revert Svea that eath 00:22:18.380 --> 00:22:24.460 align:start position:0% a function that revert Svea that eath call<00:22:19.030> you<00:22:20.030> get<00:22:20.179> 0x<00:22:21.370> eath<00:22:22.370> call<00:22:23.260> when<00:22:24.260> you<00:22:24.350> call 00:22:24.460 --> 00:22:24.470 align:start position:0% call you get 0x eath call when you call 00:22:24.470 --> 00:22:26.230 align:start position:0% call you get 0x eath call when you call a<00:22:24.530> function<00:22:24.620> on<00:22:25.100> a<00:22:25.160> missing<00:22:25.669> contract<00:22:26.120> either 00:22:26.230 --> 00:22:26.240 align:start position:0% a function on a missing contract either 00:22:26.240 --> 00:22:27.669 align:start position:0% a function on a missing contract either because<00:22:26.510> it<00:22:26.630> will<00:22:26.750> never<00:22:26.960> exist<00:22:27.140> or<00:22:27.500> because 00:22:27.669 --> 00:22:27.679 align:start position:0% because it will never exist or because 00:22:27.679 --> 00:22:29.140 align:start position:0% because it will never exist or because you're<00:22:27.799> talking<00:22:28.070> to<00:22:28.160> a<00:22:28.190> node<00:22:28.490> that<00:22:28.760> is<00:22:28.880> not<00:22:29.059> at 00:22:29.140 --> 00:22:29.150 align:start position:0% you're talking to a node that is not at 00:22:29.150 --> 00:22:30.549 align:start position:0% you're talking to a node that is not at the<00:22:29.210> block<00:22:29.390> height<00:22:29.600> that<00:22:29.750> has<00:22:29.929> that<00:22:30.110> contract 00:22:30.549 --> 00:22:30.559 align:start position:0% the block height that has that contract 00:22:30.559 --> 00:22:33.909 align:start position:0% the block height that has that contract deployment<00:22:31.010> you<00:22:31.549> get<00:22:31.700> 0x<00:22:32.710> let's<00:22:33.710> talk<00:22:33.799> what 00:22:33.909 --> 00:22:33.919 align:start position:0% deployment you get 0x let's talk what 00:22:33.919 --> 00:22:36.010 align:start position:0% deployment you get 0x let's talk what eve<00:22:34.040> call<00:22:34.250> when<00:22:34.580> you<00:22:34.790> talk<00:22:35.090> to<00:22:35.330> a<00:22:35.360> server<00:22:35.870> that 00:22:36.010 --> 00:22:36.020 align:start position:0% eve call when you talk to a server that 00:22:36.020 --> 00:22:37.780 align:start position:0% eve call when you talk to a server that is<00:22:36.200> overloaded<00:22:36.770> for<00:22:36.950> a<00:22:36.980> contract<00:22:37.490> function 00:22:37.780 --> 00:22:37.790 align:start position:0% is overloaded for a contract function 00:22:37.790 --> 00:22:41.190 align:start position:0% is overloaded for a contract function that<00:22:37.880> will<00:22:38.059> succeed<00:22:38.710> you<00:22:39.710> get<00:22:39.830> 0x 00:22:41.190 --> 00:22:41.200 align:start position:0% that will succeed you get 0x 00:22:41.200 --> 00:22:43.659 align:start position:0% that will succeed you get 0x and<00:22:42.200> so<00:22:42.320> we're<00:22:42.440> left<00:22:42.530> wondering<00:22:42.650> should<00:22:43.580> I 00:22:43.659 --> 00:22:43.669 align:start position:0% and so we're left wondering should I 00:22:43.669 --> 00:22:45.130 align:start position:0% and so we're left wondering should I retry<00:22:43.970> in<00:22:44.030> 100<00:22:44.360> milliseconds<00:22:44.840> or<00:22:44.929> should<00:22:45.080> I 00:22:45.130 --> 00:22:45.140 align:start position:0% retry in 100 milliseconds or should I 00:22:45.140 --> 00:22:46.659 align:start position:0% retry in 100 milliseconds or should I never<00:22:45.530> talk<00:22:45.830> to<00:22:45.950> you<00:22:46.010> again<00:22:46.100> because<00:22:46.340> this<00:22:46.610> is 00:22:46.659 --> 00:22:46.669 align:start position:0% never talk to you again because this is 00:22:46.669 --> 00:22:50.289 align:start position:0% never talk to you again because this is an<00:22:46.880> unrecoverable<00:22:47.299> error<00:22:48.669> so<00:22:49.669> so<00:22:50.059> what's<00:22:50.240> the 00:22:50.289 --> 00:22:50.299 align:start position:0% an unrecoverable error so so what's the 00:22:50.299 --> 00:22:50.860 align:start position:0% an unrecoverable error so so what's the lesson<00:22:50.419> here 00:22:50.860 --> 00:22:50.870 align:start position:0% lesson here 00:22:50.870 --> 00:22:53.620 align:start position:0% lesson here I<00:22:50.980> think<00:22:51.980> we<00:22:52.070> don't<00:22:52.220> quite<00:22:52.370> know<00:22:52.580> what<00:22:52.880> the 00:22:53.620 --> 00:22:53.630 align:start position:0% I think we don't quite know what the 00:22:53.630 --> 00:22:54.880 align:start position:0% I think we don't quite know what the theorems<00:22:54.080> json-rpc 00:22:54.880 --> 00:22:54.890 align:start position:0% theorems json-rpc 00:22:54.890 --> 00:22:58.450 align:start position:0% theorems json-rpc is<00:22:55.070> currently<00:22:55.610> for<00:22:55.850> is<00:22:56.390> this<00:22:56.570> a<00:22:56.630> web<00:22:56.840> api<00:22:57.140> or<00:22:57.470> is 00:22:58.450 --> 00:22:58.460 align:start position:0% is currently for is this a web api or is 00:22:58.460 --> 00:23:01.150 align:start position:0% is currently for is this a web api or is this<00:22:58.610> a<00:22:58.880> database<00:22:59.690> query<00:23:00.020> layer<00:23:00.230> because 00:23:01.150 --> 00:23:01.160 align:start position:0% this a database query layer because 00:23:01.160 --> 00:23:02.289 align:start position:0% this a database query layer because these<00:23:01.250> have<00:23:01.400> different<00:23:01.429> success<00:23:01.910> metrics 00:23:02.289 --> 00:23:02.299 align:start position:0% these have different success metrics 00:23:02.299 --> 00:23:05.350 align:start position:0% these have different success metrics this<00:23:03.140> needs<00:23:03.380> to<00:23:03.440> be<00:23:03.580> 99.99%<00:23:04.580> available<00:23:05.240> but 00:23:05.350 --> 00:23:05.360 align:start position:0% this needs to be 99.99% available but 00:23:05.360 --> 00:23:06.460 align:start position:0% this needs to be 99.99% available but it's<00:23:05.480> okay<00:23:05.720> to<00:23:05.750> have<00:23:05.929> a<00:23:05.990> little<00:23:06.049> bit<00:23:06.260> of<00:23:06.320> cash 00:23:06.460 --> 00:23:06.470 align:start position:0% it's okay to have a little bit of cash 00:23:06.470 --> 00:23:07.510 align:start position:0% it's okay to have a little bit of cash it<00:23:06.620> in<00:23:06.710> there<00:23:06.799> it's<00:23:06.919> okay<00:23:07.160> to<00:23:07.220> have<00:23:07.400> a<00:23:07.429> little 00:23:07.510 --> 00:23:07.520 align:start position:0% it in there it's okay to have a little 00:23:07.520 --> 00:23:09.460 align:start position:0% it in there it's okay to have a little bit<00:23:07.730> of<00:23:07.790> fuzzy<00:23:08.030> answers<00:23:08.360> this<00:23:08.540> is<00:23:08.600> serving<00:23:09.020> now 00:23:09.460 --> 00:23:09.470 align:start position:0% bit of fuzzy answers this is serving now 00:23:09.470 --> 00:23:12.640 align:start position:0% bit of fuzzy answers this is serving now a<00:23:09.590> web<00:23:09.740> UI<00:23:10.960> but<00:23:11.960> this<00:23:12.080> needs<00:23:12.260> to<00:23:12.320> be<00:23:12.410> a<00:23:12.440> hundred 00:23:12.640 --> 00:23:12.650 align:start position:0% a web UI but this needs to be a hundred 00:23:12.650 --> 00:23:14.799 align:start position:0% a web UI but this needs to be a hundred percent<00:23:12.770> accurate<00:23:13.280> and<00:23:13.520> you<00:23:14.299> need<00:23:14.480> to<00:23:14.630> if<00:23:14.780> you 00:23:14.799 --> 00:23:14.809 align:start position:0% percent accurate and you need to if you 00:23:14.809 --> 00:23:16.450 align:start position:0% percent accurate and you need to if you can't<00:23:15.230> be<00:23:15.410> confidence<00:23:15.980> in<00:23:16.070> the<00:23:16.160> answer 00:23:16.450 --> 00:23:16.460 align:start position:0% can't be confidence in the answer 00:23:16.460 --> 00:23:19.680 align:start position:0% can't be confidence in the answer deliver<00:23:17.210> reliable<00:23:17.570> errors<00:23:17.990> to<00:23:18.110> the<00:23:18.140> user<00:23:18.380> so 00:23:19.680 --> 00:23:19.690 align:start position:0% deliver reliable errors to the user so 00:23:19.690 --> 00:23:22.090 align:start position:0% deliver reliable errors to the user so I'm<00:23:20.690> proposing<00:23:21.169> I<00:23:21.260> believe<00:23:21.500> it<00:23:21.559> is<00:23:21.650> currently 00:23:22.090 --> 00:23:22.100 align:start position:0% I'm proposing I believe it is currently 00:23:22.100 --> 00:23:25.150 align:start position:0% I'm proposing I believe it is currently a<00:23:22.309> Web<00:23:22.549> API<00:23:22.820> and<00:23:23.120> to<00:23:23.210> support<00:23:23.540> that<00:23:24.070> here's<00:23:25.070> the 00:23:25.150 --> 00:23:25.160 align:start position:0% a Web API and to support that here's the 00:23:25.160 --> 00:23:26.710 align:start position:0% a Web API and to support that here's the documentation<00:23:25.730> for<00:23:25.880> the<00:23:25.940> JSON<00:23:26.240> RPC<00:23:26.390> interface 00:23:26.710 --> 00:23:26.720 align:start position:0% documentation for the JSON RPC interface 00:23:26.720 --> 00:23:28.480 align:start position:0% documentation for the JSON RPC interface this<00:23:27.350> is<00:23:27.410> over<00:23:27.650> a<00:23:27.679> hundred<00:23:28.040> pages<00:23:28.160> of 00:23:28.480 --> 00:23:28.490 align:start position:0% this is over a hundred pages of 00:23:28.490 --> 00:23:31.659 align:start position:0% this is over a hundred pages of documentation<00:23:29.590> the<00:23:30.590> word<00:23:30.799> error<00:23:31.100> appears 00:23:31.659 --> 00:23:31.669 align:start position:0% documentation the word error appears 00:23:31.669 --> 00:23:35.320 align:start position:0% documentation the word error appears zero<00:23:32.150> times<00:23:33.700> and<00:23:34.700> I<00:23:34.760> think<00:23:34.850> it<00:23:35.000> is<00:23:35.090> not<00:23:35.299> a 00:23:35.320 --> 00:23:35.330 align:start position:0% zero times and I think it is not a 00:23:35.330 --> 00:23:36.669 align:start position:0% zero times and I think it is not a database<00:23:35.660> query<00:23:35.929> layer<00:23:36.140> because<00:23:36.380> if<00:23:36.500> you<00:23:36.590> were 00:23:36.669 --> 00:23:36.679 align:start position:0% database query layer because if you were 00:23:36.679 --> 00:23:37.720 align:start position:0% database query layer because if you were to<00:23:36.770> pretend<00:23:37.130> that<00:23:37.220> the<00:23:37.340> issues<00:23:37.580> we've 00:23:37.720 --> 00:23:37.730 align:start position:0% to pretend that the issues we've 00:23:37.730 --> 00:23:39.400 align:start position:0% to pretend that the issues we've experienced<00:23:38.299> appeared<00:23:38.690> in<00:23:38.780> the<00:23:38.870> my<00:23:38.990> sequel 00:23:39.400 --> 00:23:39.410 align:start position:0% experienced appeared in the my sequel 00:23:39.410 --> 00:23:41.799 align:start position:0% experienced appeared in the my sequel bug<00:23:39.650> tracker<00:23:40.120> these<00:23:41.120> would<00:23:41.240> be<00:23:41.299> big<00:23:41.480> issues 00:23:41.799 --> 00:23:41.809 align:start position:0% bug tracker these would be big issues 00:23:41.809 --> 00:23:43.570 align:start position:0% bug tracker these would be big issues quite<00:23:42.260> if<00:23:42.380> querying<00:23:42.650> for<00:23:42.740> new<00:23:43.010> data<00:23:43.220> returns 00:23:43.570 --> 00:23:43.580 align:start position:0% quite if querying for new data returns 00:23:43.580 --> 00:23:45.220 align:start position:0% quite if querying for new data returns success<00:23:43.910> with<00:23:44.090> zero<00:23:44.270> rows<00:23:44.480> or<00:23:44.750> querying<00:23:45.140> for 00:23:45.220 --> 00:23:45.230 align:start position:0% success with zero rows or querying for 00:23:45.230 --> 00:23:46.930 align:start position:0% success with zero rows or querying for old<00:23:45.470> data<00:23:45.770> returns<00:23:46.130> success<00:23:46.429> with<00:23:46.580> zero<00:23:46.760> rows 00:23:46.930 --> 00:23:46.940 align:start position:0% old data returns success with zero rows 00:23:46.940 --> 00:23:50.260 align:start position:0% old data returns success with zero rows this<00:23:47.809> would<00:23:47.929> be<00:23:47.990> a<00:23:48.020> big<00:23:48.200> deal<00:23:48.970> you<00:23:49.970> know<00:23:50.000> but<00:23:50.179> I 00:23:50.260 --> 00:23:50.270 align:start position:0% this would be a big deal you know but I 00:23:50.270 --> 00:23:51.700 align:start position:0% this would be a big deal you know but I don't<00:23:50.330> I<00:23:50.570> don't<00:23:50.630> really<00:23:50.840> fault<00:23:51.140> the<00:23:51.260> JSON<00:23:51.590> RPC 00:23:51.700 --> 00:23:51.710 align:start position:0% don't I don't really fault the JSON RPC 00:23:51.710 --> 00:23:53.799 align:start position:0% don't I don't really fault the JSON RPC or<00:23:52.250> parity<00:23:53.179> or<00:23:53.330> get<00:23:53.510> for<00:23:53.690> these 00:23:53.799 --> 00:23:53.809 align:start position:0% or parity or get for these 00:23:53.809 --> 00:23:55.090 align:start position:0% or parity or get for these implementations<00:23:54.350> because<00:23:54.559> what<00:23:54.740> we<00:23:54.830> built 00:23:55.090 --> 00:23:55.100 align:start position:0% implementations because what we built 00:23:55.100 --> 00:23:57.260 align:start position:0% implementations because what we built really<00:23:55.400> works<00:23:55.730> we've<00:23:56.660> built 00:23:57.260 --> 00:23:57.270 align:start position:0% really works we've built 00:23:57.270 --> 00:24:00.560 align:start position:0% really works we've built things<00:23:57.570> and<00:23:57.780> they<00:23:57.930> work<00:23:58.140> great<00:23:59.270> you<00:24:00.270> know<00:24:00.360> I 00:24:00.560 --> 00:24:00.570 align:start position:0% things and they work great you know I 00:24:00.570 --> 00:24:01.850 align:start position:0% things and they work great you know I haven't<00:24:00.990> had<00:24:01.140> a<00:24:01.200> problem<00:24:01.470> using<00:24:01.560> the<00:24:01.710> maker 00:24:01.850 --> 00:24:01.860 align:start position:0% haven't had a problem using the maker 00:24:01.860 --> 00:24:03.800 align:start position:0% haven't had a problem using the maker interface<00:24:02.190> but<00:24:02.400> if<00:24:02.460> I<00:24:02.550> ever<00:24:02.670> did<00:24:02.940> I<00:24:03.150> don't<00:24:03.750> know 00:24:03.800 --> 00:24:03.810 align:start position:0% interface but if I ever did I don't know 00:24:03.810 --> 00:24:04.910 align:start position:0% interface but if I ever did I don't know I<00:24:03.840> would<00:24:03.990> just<00:24:04.140> refresh<00:24:04.440> and<00:24:04.590> everything's 00:24:04.910 --> 00:24:04.920 align:start position:0% I would just refresh and everything's 00:24:04.920 --> 00:24:06.410 align:start position:0% I would just refresh and everything's fine<00:24:04.980> if<00:24:05.280> I<00:24:05.370> was<00:24:05.520> in<00:24:05.640> that<00:24:05.670> you<00:24:05.820> know<00:24:06.030> one<00:24:06.270> in<00:24:06.360> a 00:24:06.410 --> 00:24:06.420 align:start position:0% fine if I was in that you know one in a 00:24:06.420 --> 00:24:08.260 align:start position:0% fine if I was in that you know one in a thousand<00:24:06.840> case<00:24:06.990> right<00:24:07.230> I<00:24:07.260> got<00:24:07.470> a<00:24:07.500> bad<00:24:07.710> get<00:24:07.920> log 00:24:08.260 --> 00:24:08.270 align:start position:0% thousand case right I got a bad get log 00:24:08.270 --> 00:24:10.610 align:start position:0% thousand case right I got a bad get log but<00:24:09.270> when<00:24:09.420> you're<00:24:09.570> synchronizing<00:24:10.290> the 00:24:10.610 --> 00:24:10.620 align:start position:0% but when you're synchronizing the 00:24:10.620 --> 00:24:13.010 align:start position:0% but when you're synchronizing the database<00:24:11.040> off<00:24:11.760> of<00:24:12.300> the<00:24:12.360> theorem<00:24:12.660> in<00:24:12.750> this<00:24:12.870> way 00:24:13.010 --> 00:24:13.020 align:start position:0% database off of the theorem in this way 00:24:13.020 --> 00:24:15.920 align:start position:0% database off of the theorem in this way when<00:24:13.980> you<00:24:14.070> lose<00:24:14.280> data<00:24:14.490> you<00:24:15.240> start<00:24:15.570> building 00:24:15.920 --> 00:24:15.930 align:start position:0% when you lose data you start building 00:24:15.930 --> 00:24:19.430 align:start position:0% when you lose data you start building the<00:24:16.260> missing<00:24:16.650> data<00:24:16.830> or<00:24:17.900> your<00:24:18.900> synchronization 00:24:19.430 --> 00:24:19.440 align:start position:0% the missing data or your synchronization 00:24:19.440 --> 00:24:21.350 align:start position:0% the missing data or your synchronization is<00:24:19.530> paused<00:24:19.710> because<00:24:19.890> you<00:24:20.130> don't<00:24:20.310> know<00:24:20.490> when<00:24:21.090> or 00:24:21.350 --> 00:24:21.360 align:start position:0% is paused because you don't know when or 00:24:21.360 --> 00:24:24.530 align:start position:0% is paused because you don't know when or if<00:24:21.390> you<00:24:21.780> should<00:24:21.990> be<00:24:22.110> retrying<00:24:23.330> you<00:24:24.330> know<00:24:24.390> an 00:24:24.530 --> 00:24:24.540 align:start position:0% if you should be retrying you know an 00:24:24.540 --> 00:24:26.510 align:start position:0% if you should be retrying you know an auger<00:24:24.780> is<00:24:24.960> not<00:24:25.080> the<00:24:25.170> only<00:24:25.320> system<00:24:25.740> that<00:24:25.920> is 00:24:26.510 --> 00:24:26.520 align:start position:0% auger is not the only system that is 00:24:26.520 --> 00:24:28.310 align:start position:0% auger is not the only system that is trying<00:24:26.910> to<00:24:27.060> treat<00:24:27.300> the<00:24:27.480> etherium<00:24:27.930> json-rpc 00:24:28.310 --> 00:24:28.320 align:start position:0% trying to treat the etherium json-rpc 00:24:28.320 --> 00:24:30.320 align:start position:0% trying to treat the etherium json-rpc like<00:24:28.710> a<00:24:28.740> database<00:24:29.100> here's<00:24:29.370> the<00:24:29.460> etherium<00:24:29.940> ETL 00:24:30.320 --> 00:24:30.330 align:start position:0% like a database here's the etherium ETL 00:24:30.330 --> 00:24:33.290 align:start position:0% like a database here's the etherium ETL project<00:24:30.810> where<00:24:31.230> Google<00:24:31.710> is<00:24:32.090> running<00:24:33.090> daily 00:24:33.290 --> 00:24:33.300 align:start position:0% project where Google is running daily 00:24:33.300 --> 00:24:34.940 align:start position:0% project where Google is running daily exports<00:24:33.810> of<00:24:33.930> the<00:24:34.050> entire<00:24:34.440> etherium 00:24:34.940 --> 00:24:34.950 align:start position:0% exports of the entire etherium 00:24:34.950 --> 00:24:38.500 align:start position:0% exports of the entire etherium blockchain<00:24:35.370> and<00:24:35.400> putting<00:24:35.820> inside<00:24:36.060> a<00:24:36.120> bigquery 00:24:38.500 --> 00:24:38.510 align:start position:0% blockchain and putting inside a bigquery 00:24:38.510 --> 00:24:40.880 align:start position:0% blockchain and putting inside a bigquery but<00:24:39.510> this<00:24:39.630> is<00:24:39.780> this<00:24:40.080> is<00:24:40.140> a<00:24:40.260> daily<00:24:40.440> export<00:24:40.800> and 00:24:40.880 --> 00:24:40.890 align:start position:0% but this is this is a daily export and 00:24:40.890 --> 00:24:42.320 align:start position:0% but this is this is a daily export and there's<00:24:41.010> lots<00:24:41.340> of<00:24:41.460> value<00:24:41.700> we<00:24:41.790> had<00:24:41.970> there<00:24:42.180> in 00:24:42.320 --> 00:24:42.330 align:start position:0% there's lots of value we had there in 00:24:42.330 --> 00:24:44.210 align:start position:0% there's lots of value we had there in research<00:24:42.810> and<00:24:43.050> reporting<00:24:43.500> and<00:24:43.650> charting<00:24:44.130> you 00:24:44.210 --> 00:24:44.220 align:start position:0% research and reporting and charting you 00:24:44.220 --> 00:24:47.090 align:start position:0% research and reporting and charting you can<00:24:44.340> do<00:24:44.430> some<00:24:44.550> really<00:24:44.790> cool<00:24:45.000> stuff<00:24:45.440> but<00:24:46.440> this 00:24:47.090 --> 00:24:47.100 align:start position:0% can do some really cool stuff but this 00:24:47.100 --> 00:24:48.950 align:start position:0% can do some really cool stuff but this is<00:24:47.160> a<00:24:47.340> different<00:24:47.670> product<00:24:47.850> than<00:24:48.420> an<00:24:48.600> ETL 00:24:48.950 --> 00:24:48.960 align:start position:0% is a different product than an ETL 00:24:48.960 --> 00:24:52.190 align:start position:0% is a different product than an ETL process<00:24:49.410> the<00:24:50.100> tracks<00:24:50.430> head<00:24:50.700> closely<00:24:51.420> and<00:24:51.660> can 00:24:52.190 --> 00:24:52.200 align:start position:0% process the tracks head closely and can 00:24:52.200 --> 00:24:54.860 align:start position:0% process the tracks head closely and can serve<00:24:52.470> as<00:24:52.680> the<00:24:52.830> API<00:24:53.220> for<00:24:54.060> a<00:24:54.090> complicated<00:24:54.660> for 00:24:54.860 --> 00:24:54.870 align:start position:0% serve as the API for a complicated for 00:24:54.870 --> 00:25:00.110 align:start position:0% serve as the API for a complicated for an<00:24:54.960> application<00:24:55.500> that<00:24:55.710> is<00:24:55.830> more<00:24:56.130> complex<00:24:59.090> so<00:25:00.090> I 00:25:00.110 --> 00:25:00.120 align:start position:0% an application that is more complex so I 00:25:00.120 --> 00:25:01.700 align:start position:0% an application that is more complex so I believe<00:25:00.510> that<00:25:00.720> ETL<00:25:01.200> is<00:25:01.320> going<00:25:01.470> to<00:25:01.530> be<00:25:01.620> the 00:25:01.700 --> 00:25:01.710 align:start position:0% believe that ETL is going to be the 00:25:01.710 --> 00:25:04.280 align:start position:0% believe that ETL is going to be the future<00:25:01.890> to<00:25:02.760> building<00:25:03.210> advanced<00:25:03.720> applications 00:25:04.280 --> 00:25:04.290 align:start position:0% future to building advanced applications 00:25:04.290 --> 00:25:07.250 align:start position:0% future to building advanced applications like<00:25:04.470> this<00:25:05.660> and<00:25:06.660> so<00:25:06.780> why<00:25:06.930> am<00:25:07.050> i<00:25:07.110> up<00:25:07.230> here 00:25:07.250 --> 00:25:07.260 align:start position:0% like this and so why am i up here 00:25:07.260 --> 00:25:09.020 align:start position:0% like this and so why am i up here talking<00:25:08.100> about<00:25:08.310> some<00:25:08.670> of<00:25:08.730> these<00:25:08.820> specific 00:25:09.020 --> 00:25:09.030 align:start position:0% talking about some of these specific 00:25:09.030 --> 00:25:10.790 align:start position:0% talking about some of these specific issues<00:25:09.330> want<00:25:09.720> to<00:25:09.780> just<00:25:09.930> go<00:25:09.990> file<00:25:10.260> some<00:25:10.530> issues 00:25:10.790 --> 00:25:10.800 align:start position:0% issues want to just go file some issues 00:25:10.800 --> 00:25:12.440 align:start position:0% issues want to just go file some issues because<00:25:11.580> I<00:25:11.820> think<00:25:11.880> that<00:25:12.150> what<00:25:12.240> we're<00:25:12.360> talking 00:25:12.440 --> 00:25:12.450 align:start position:0% because I think that what we're talking 00:25:12.450 --> 00:25:14.450 align:start position:0% because I think that what we're talking about<00:25:12.690> here<00:25:13.020> is<00:25:13.170> cultural<00:25:14.010> and<00:25:14.100> I<00:25:14.220> think<00:25:14.370> if 00:25:14.450 --> 00:25:14.460 align:start position:0% about here is cultural and I think if 00:25:14.460 --> 00:25:16.010 align:start position:0% about here is cultural and I think if this<00:25:14.580> we<00:25:14.730> need<00:25:14.850> to<00:25:14.940> decide<00:25:15.300> if<00:25:15.660> this<00:25:15.780> is<00:25:15.840> the 00:25:16.010 --> 00:25:16.020 align:start position:0% this we need to decide if this is the 00:25:16.020 --> 00:25:17.330 align:start position:0% this we need to decide if this is the kind<00:25:16.140> of<00:25:16.230> thing<00:25:16.440> that<00:25:16.620> we<00:25:16.800> want<00:25:16.920> to<00:25:17.040> care<00:25:17.250> about 00:25:17.330 --> 00:25:17.340 align:start position:0% kind of thing that we want to care about 00:25:17.340 --> 00:25:19.940 align:start position:0% kind of thing that we want to care about and<00:25:17.730> we<00:25:18.510> want<00:25:18.690> to<00:25:18.810> request<00:25:19.080> out<00:25:19.380> of<00:25:19.560> out<00:25:19.770> of 00:25:19.940 --> 00:25:19.950 align:start position:0% and we want to request out of out of 00:25:19.950 --> 00:25:21.620 align:start position:0% and we want to request out of out of these<00:25:20.100> api's<00:25:20.490> and<00:25:20.850> work<00:25:21.180> towards<00:25:21.510> achieving 00:25:21.620 --> 00:25:21.630 align:start position:0% these api's and work towards achieving 00:25:21.630 --> 00:25:23.960 align:start position:0% these api's and work towards achieving so<00:25:22.590> I<00:25:22.620> think<00:25:22.770> we<00:25:22.950> need<00:25:23.100> to<00:25:23.190> care<00:25:23.490> more<00:25:23.730> about 00:25:23.960 --> 00:25:23.970 align:start position:0% so I think we need to care more about 00:25:23.970 --> 00:25:27.410 align:start position:0% so I think we need to care more about reliable<00:25:24.660> data<00:25:25.020> access<00:25:25.710> and<00:25:26.120> there's<00:25:27.120> lots<00:25:27.300> of 00:25:27.410 --> 00:25:27.420 align:start position:0% reliable data access and there's lots of 00:25:27.420 --> 00:25:29.420 align:start position:0% reliable data access and there's lots of projects<00:25:27.780> underway<00:25:28.020> that<00:25:28.680> are<00:25:29.100> leading<00:25:29.340> this 00:25:29.420 --> 00:25:29.430 align:start position:0% projects underway that are leading this 00:25:29.430 --> 00:25:31.430 align:start position:0% projects underway that are leading this charge<00:25:29.580> in<00:25:29.820> fact<00:25:29.970> you<00:25:30.840> know<00:25:30.930> the<00:25:31.140> folks 00:25:31.430 --> 00:25:31.440 align:start position:0% charge in fact you know the folks 00:25:31.440 --> 00:25:32.480 align:start position:0% charge in fact you know the folks interfere<00:25:31.800> we've<00:25:31.980> been<00:25:32.070> talking<00:25:32.370> to<00:25:32.460> our 00:25:32.480 --> 00:25:32.490 align:start position:0% interfere we've been talking to our 00:25:32.490 --> 00:25:36.380 align:start position:0% interfere we've been talking to our pushing<00:25:33.350> fql<00:25:34.350> this<00:25:35.130> is<00:25:35.280> a<00:25:35.310> a<00:25:35.490> new<00:25:35.970> way<00:25:36.150> of 00:25:36.380 --> 00:25:36.390 align:start position:0% pushing fql this is a a new way of 00:25:36.390 --> 00:25:39.250 align:start position:0% pushing fql this is a a new way of talking<00:25:36.990> to<00:25:37.020> the<00:25:37.560> etherium<00:25:38.130> blockchain<00:25:38.760> and 00:25:39.250 --> 00:25:39.260 align:start position:0% talking to the etherium blockchain and 00:25:39.260 --> 00:25:42.080 align:start position:0% talking to the etherium blockchain and currently<00:25:40.260> it<00:25:40.440> is<00:25:40.470> it<00:25:40.740> is<00:25:40.890> resting<00:25:41.820> on<00:25:41.970> the 00:25:42.080 --> 00:25:42.090 align:start position:0% currently it is it is resting on the 00:25:42.090 --> 00:25:43.940 align:start position:0% currently it is it is resting on the JSON<00:25:42.360> RPC<00:25:42.450> interface<00:25:42.750> but<00:25:43.440> the<00:25:43.530> intention<00:25:43.800> is 00:25:43.940 --> 00:25:43.950 align:start position:0% JSON RPC interface but the intention is 00:25:43.950 --> 00:25:46.010 align:start position:0% JSON RPC interface but the intention is to<00:25:44.010> put<00:25:44.220> it<00:25:44.310> inside<00:25:44.430> of<00:25:44.670> aetherium<00:25:45.330> and<00:25:45.510> so 00:25:46.010 --> 00:25:46.020 align:start position:0% to put it inside of aetherium and so 00:25:46.020 --> 00:25:47.330 align:start position:0% to put it inside of aetherium and so this<00:25:46.170> is<00:25:46.290> our<00:25:46.410> chance<00:25:46.650> to<00:25:46.740> really<00:25:46.860> get<00:25:47.220> it 00:25:47.330 --> 00:25:47.340 align:start position:0% this is our chance to really get it 00:25:47.340 --> 00:25:49.310 align:start position:0% this is our chance to really get it right<00:25:47.370> and<00:25:47.730> enable<00:25:48.300> ourselves<00:25:48.540> to<00:25:49.050> build 00:25:49.310 --> 00:25:49.320 align:start position:0% right and enable ourselves to build 00:25:49.320 --> 00:25:54.350 align:start position:0% right and enable ourselves to build these<00:25:49.560> big<00:25:49.770> applications<00:25:52.790> so<00:25:53.790> what's<00:25:53.970> what's 00:25:54.350 --> 00:25:54.360 align:start position:0% these big applications so what's what's 00:25:54.360 --> 00:25:57.830 align:start position:0% these big applications so what's what's next<00:25:54.660> what's<00:25:55.380> coming<00:25:55.590> up<00:25:55.650> in<00:25:55.830> in<00:25:56.040> augur<00:25:56.280> v2<00:25:56.840> so 00:25:57.830 --> 00:25:57.840 align:start position:0% next what's coming up in in augur v2 so 00:25:57.840 --> 00:26:00.610 align:start position:0% next what's coming up in in augur v2 so currently<00:25:58.110> all<00:25:58.590> markets<00:25:59.580> in<00:25:59.760> augur<00:26:00.210> are 00:26:00.610 --> 00:26:00.620 align:start position:0% currently all markets in augur are 00:26:00.620 --> 00:26:04.100 align:start position:0% currently all markets in augur are denominated<00:26:01.620> in<00:26:01.740> ether<00:26:02.160> ether<00:26:02.540> is<00:26:03.540> the<00:26:03.750> only 00:26:04.100 --> 00:26:04.110 align:start position:0% denominated in ether ether is the only 00:26:04.110 --> 00:26:07.130 align:start position:0% denominated in ether ether is the only token<00:26:04.290> that<00:26:04.440> we<00:26:04.590> accept<00:26:04.920> for<00:26:05.780> for<00:26:06.780> trading<00:26:06.960> on 00:26:07.130 --> 00:26:07.140 align:start position:0% token that we accept for for trading on 00:26:07.140 --> 00:26:10.370 align:start position:0% token that we accept for for trading on these<00:26:07.290> order<00:26:07.470> books<00:26:07.880> but<00:26:08.930> we<00:26:09.930> have<00:26:10.020> decided 00:26:10.370 --> 00:26:10.380 align:start position:0% these order books but we have decided 00:26:10.380 --> 00:26:11.180 align:start position:0% these order books but we have decided not<00:26:10.530> to<00:26:10.590> add 00:26:11.180 --> 00:26:11.190 align:start position:0% not to add 00:26:11.190 --> 00:26:13.970 align:start position:0% not to add died<00:26:11.550> as<00:26:12.110> the<00:26:13.110> token<00:26:13.410> that<00:26:13.440> will<00:26:13.620> be<00:26:13.710> used<00:26:13.890> here 00:26:13.970 --> 00:26:13.980 align:start position:0% died as the token that will be used here 00:26:13.980 --> 00:26:16.640 align:start position:0% died as the token that will be used here we<00:26:14.550> have<00:26:14.670> decided<00:26:15.000> to<00:26:15.120> replace<00:26:15.420> die<00:26:16.260> as<00:26:16.530> the 00:26:16.640 --> 00:26:16.650 align:start position:0% we have decided to replace die as the 00:26:16.650 --> 00:26:18.590 align:start position:0% we have decided to replace die as the only<00:26:16.800> token<00:26:17.250> that<00:26:17.400> will<00:26:17.670> be<00:26:17.760> traded<00:26:18.090> on<00:26:18.240> the 00:26:18.590 --> 00:26:18.600 align:start position:0% only token that will be traded on the 00:26:18.600 --> 00:26:21.050 align:start position:0% only token that will be traded on the auger<00:26:18.990> platform<00:26:19.380> because<00:26:20.370> we've<00:26:20.640> realized 00:26:21.050 --> 00:26:21.060 align:start position:0% auger platform because we've realized 00:26:21.060 --> 00:26:23.780 align:start position:0% auger platform because we've realized that<00:26:21.240> not<00:26:21.990> everyone<00:26:22.050> who<00:26:22.920> finds<00:26:23.490> use<00:26:23.760> in 00:26:23.780 --> 00:26:23.790 align:start position:0% that not everyone who finds use in 00:26:23.790 --> 00:26:26.420 align:start position:0% that not everyone who finds use in aetherium<00:26:24.860> necessarily<00:26:25.860> wants<00:26:26.040> to<00:26:26.100> also<00:26:26.340> be 00:26:26.420 --> 00:26:26.430 align:start position:0% aetherium necessarily wants to also be 00:26:26.430 --> 00:26:28.850 align:start position:0% aetherium necessarily wants to also be long<00:26:26.610> ether<00:26:27.050> especially<00:26:28.050> not<00:26:28.140> for<00:26:28.290> six<00:26:28.530> months 00:26:28.850 --> 00:26:28.860 align:start position:0% long ether especially not for six months 00:26:28.860 --> 00:26:30.740 align:start position:0% long ether especially not for six months or<00:26:29.040> a<00:26:29.130> year<00:26:29.190> as<00:26:30.120> long<00:26:30.330> as<00:26:30.450> some<00:26:30.570> of<00:26:30.600> these 00:26:30.740 --> 00:26:30.750 align:start position:0% or a year as long as some of these 00:26:30.750 --> 00:26:34.850 align:start position:0% or a year as long as some of these markets<00:26:31.080> can<00:26:31.200> take<00:26:31.350> to<00:26:31.470> resolve<00:26:33.710> we're<00:26:34.710> also 00:26:34.850 --> 00:26:34.860 align:start position:0% markets can take to resolve we're also 00:26:34.860 --> 00:26:36.290 align:start position:0% markets can take to resolve we're also working<00:26:35.100> to<00:26:35.220> improve<00:26:35.550> the<00:26:35.730> user<00:26:35.910> experience 00:26:36.290 --> 00:26:36.300 align:start position:0% working to improve the user experience 00:26:36.300 --> 00:26:38.720 align:start position:0% working to improve the user experience here<00:26:36.770> downloading<00:26:37.770> an<00:26:37.860> application<00:26:38.490> and 00:26:38.720 --> 00:26:38.730 align:start position:0% here downloading an application and 00:26:38.730 --> 00:26:40.940 align:start position:0% here downloading an application and having<00:26:39.360> it<00:26:39.450> sync<00:26:39.720> locally<00:26:40.170> as<00:26:40.350> some<00:26:40.590> window 00:26:40.940 --> 00:26:40.950 align:start position:0% having it sync locally as some window 00:26:40.950 --> 00:26:42.110 align:start position:0% having it sync locally as some window running<00:26:41.190> on<00:26:41.280> your<00:26:41.370> system<00:26:41.490> like<00:26:41.640> that's<00:26:41.880> not 00:26:42.110 --> 00:26:42.120 align:start position:0% running on your system like that's not 00:26:42.120 --> 00:26:43.370 align:start position:0% running on your system like that's not really<00:26:42.450> an<00:26:42.540> optimal<00:26:42.810> experience<00:26:43.020> and<00:26:43.260> that's 00:26:43.370 --> 00:26:43.380 align:start position:0% really an optimal experience and that's 00:26:43.380 --> 00:26:45.500 align:start position:0% really an optimal experience and that's not<00:26:43.500> really<00:26:43.740> the<00:26:44.250> way<00:26:44.280> that's<00:26:44.640> you<00:26:45.120> know<00:26:45.210> the 00:26:45.500 --> 00:26:45.510 align:start position:0% not really the way that's you know the 00:26:45.510 --> 00:26:47.420 align:start position:0% not really the way that's you know the web<00:26:45.630> is<00:26:45.780> supposed<00:26:46.050> to<00:26:46.110> work<00:26:46.290> and<00:26:47.070> so<00:26:47.280> we're 00:26:47.420 --> 00:26:47.430 align:start position:0% web is supposed to work and so we're 00:26:47.430 --> 00:26:49.730 align:start position:0% web is supposed to work and so we're working<00:26:47.610> to<00:26:48.000> take<00:26:48.720> the<00:26:48.870> same<00:26:49.080> architecture 00:26:49.730 --> 00:26:49.740 align:start position:0% working to take the same architecture 00:26:49.740 --> 00:26:51.560 align:start position:0% working to take the same architecture and<00:26:49.950> to<00:26:50.310> run<00:26:50.460> it<00:26:50.550> inside<00:26:50.850> of<00:26:50.880> the<00:26:51.060> browser<00:26:51.210> and 00:26:51.560 --> 00:26:51.570 align:start position:0% and to run it inside of the browser and 00:26:51.570 --> 00:26:53.660 align:start position:0% and to run it inside of the browser and use<00:26:51.900> some<00:26:52.080> modern<00:26:52.440> browser<00:26:52.680> features<00:26:52.950> to 00:26:53.660 --> 00:26:53.670 align:start position:0% use some modern browser features to 00:26:53.670 --> 00:26:55.190 align:start position:0% use some modern browser features to accomplish<00:26:54.120> a<00:26:54.150> lot<00:26:54.420> of<00:26:54.510> the<00:26:54.570> same<00:26:54.750> things<00:26:55.020> that 00:26:55.190 --> 00:26:55.200 align:start position:0% accomplish a lot of the same things that 00:26:55.200 --> 00:26:57.560 align:start position:0% accomplish a lot of the same things that we<00:26:55.290> need<00:26:55.580> but<00:26:56.580> do<00:26:56.760> it<00:26:56.850> in<00:26:56.910> a<00:26:56.970> way<00:26:57.090> that<00:26:57.480> is 00:26:57.560 --> 00:26:57.570 align:start position:0% we need but do it in a way that is 00:26:57.570 --> 00:26:59.240 align:start position:0% we need but do it in a way that is transparent<00:26:58.230> to<00:26:58.380> the<00:26:58.530> user<00:26:58.710> and<00:26:58.920> doesn't 00:26:59.240 --> 00:26:59.250 align:start position:0% transparent to the user and doesn't 00:26:59.250 --> 00:27:02.480 align:start position:0% transparent to the user and doesn't require<00:26:59.460> this<00:27:00.060> extra<00:27:00.480> UX<00:27:00.750> burden<00:27:01.370> because<00:27:02.370> I 00:27:02.480 --> 00:27:02.490 align:start position:0% require this extra UX burden because I 00:27:02.490 --> 00:27:03.350 align:start position:0% require this extra UX burden because I think<00:27:02.550> this<00:27:02.730> is<00:27:02.820> gonna<00:27:02.970> be<00:27:03.060> a<00:27:03.090> powerful 00:27:03.350 --> 00:27:03.360 align:start position:0% think this is gonna be a powerful 00:27:03.360 --> 00:27:06.350 align:start position:0% think this is gonna be a powerful pattern<00:27:03.660> for<00:27:04.140> larger<00:27:04.920> and<00:27:05.130> larger<00:27:05.610> groups<00:27:06.240> to 00:27:06.350 --> 00:27:06.360 align:start position:0% pattern for larger and larger groups to 00:27:06.360 --> 00:27:07.940 align:start position:0% pattern for larger and larger groups to implement<00:27:06.750> because<00:27:07.260> if<00:27:07.470> we<00:27:07.560> want<00:27:07.710> to<00:27:07.770> take 00:27:07.940 --> 00:27:07.950 align:start position:0% implement because if we want to take 00:27:07.950 --> 00:27:11.420 align:start position:0% implement because if we want to take this<00:27:08.880> chart<00:27:09.240> and<00:27:09.740> change<00:27:10.740> the<00:27:10.950> scale<00:27:11.190> of<00:27:11.340> it 00:27:11.420 --> 00:27:11.430 align:start position:0% this chart and change the scale of it 00:27:11.430 --> 00:27:13.670 align:start position:0% this chart and change the scale of it again<00:27:11.670> I<00:27:12.110> want<00:27:13.110> to<00:27:13.230> make<00:27:13.320> sure<00:27:13.350> whatever 00:27:13.670 --> 00:27:13.680 align:start position:0% again I want to make sure whatever 00:27:13.680 --> 00:27:15.950 align:start position:0% again I want to make sure whatever project<00:27:14.130> does<00:27:14.280> that<00:27:14.520> has<00:27:15.270> has<00:27:15.570> a<00:27:15.600> great 00:27:15.950 --> 00:27:15.960 align:start position:0% project does that has has a great 00:27:15.960 --> 00:27:17.360 align:start position:0% project does that has has a great platform<00:27:16.380> to<00:27:16.440> build<00:27:16.560> on<00:27:16.740> an<00:27:16.890> audited 00:27:17.360 --> 00:27:17.370 align:start position:0% platform to build on an audited 00:27:17.370 --> 00:27:20.420 align:start position:0% platform to build on an audited ecosystem<00:27:18.860> development<00:27:19.860> environments<00:27:20.340> that 00:27:20.420 --> 00:27:20.430 align:start position:0% ecosystem development environments that 00:27:20.430 --> 00:27:22.580 align:start position:0% ecosystem development environments that can<00:27:20.520> support<00:27:20.850> large<00:27:21.270> arrays<00:27:21.750> of<00:27:22.140> of 00:27:22.580 --> 00:27:22.590 align:start position:0% can support large arrays of of 00:27:22.590 --> 00:27:26.720 align:start position:0% can support large arrays of of engineering<00:27:23.130> teams<00:27:25.400> integrations<00:27:26.400> with 00:27:26.720 --> 00:27:26.730 align:start position:0% engineering teams integrations with 00:27:26.730 --> 00:27:28.610 align:start position:0% engineering teams integrations with other<00:27:26.880> projects<00:27:27.450> that<00:27:27.510> are<00:27:27.810> well<00:27:27.990> tested<00:27:28.470> and 00:27:28.610 --> 00:27:28.620 align:start position:0% other projects that are well tested and 00:27:28.620 --> 00:27:30.380 align:start position:0% other projects that are well tested and not<00:27:28.860> just<00:27:29.100> relying<00:27:29.430> on<00:27:29.640> simple<00:27:30.030> interfaces 00:27:30.380 --> 00:27:30.390 align:start position:0% not just relying on simple interfaces 00:27:30.390 --> 00:27:35.230 align:start position:0% not just relying on simple interfaces and<00:27:31.160> to<00:27:32.160> build<00:27:32.370> on<00:27:32.550> a<00:27:32.610> reliable<00:27:33.300> data<00:27:33.570> platform 00:27:35.230 --> 00:27:35.240 align:start position:0% and to build on a reliable data platform 00:27:35.240 --> 00:27:38.990 align:start position:0% and to build on a reliable data platform thank<00:27:36.240> you 00:27:38.990 --> 00:27:39.000 align:start position:0% 00:27:39.000 --> 00:27:43.320 align:start position:0% [Music] 00:27:43.320 --> 00:27:43.330 align:start position:0% 00:27:43.330 --> 00:27:51.980 align:start position:0% you 00:27:51.980 --> 00:27:51.990 align:start position:0% 00:27:51.990 --> 00:27:54.050 align:start position:0% you