WEBVTT
Kind: captions
Language: en

00:00:01.070 --> 00:00:10.539 align:start position:0%
 
[Applause]

00:00:10.539 --> 00:00:10.549 align:start position:0%
 
 

00:00:10.549 --> 00:00:13.430 align:start position:0%
 
hello<00:00:11.549><c> everyone</c><00:00:11.900><c> looming</c><00:00:12.900><c> today</c><00:00:13.139><c> I'm</c><00:00:13.259><c> here</c>

00:00:13.430 --> 00:00:13.440 align:start position:0%
hello everyone looming today I'm here
 

00:00:13.440 --> 00:00:14.869 align:start position:0%
hello everyone looming today I'm here
discussing<00:00:13.889><c> our</c><00:00:14.039><c> meta</c><00:00:14.250><c> transaction</c><00:00:14.759><c> tree</c>

00:00:14.869 --> 00:00:14.879 align:start position:0%
discussing our meta transaction tree
 

00:00:14.879 --> 00:00:17.269 align:start position:0%
discussing our meta transaction tree
layers<00:00:15.199><c> so</c><00:00:16.199><c> what</c><00:00:16.529><c> are</c><00:00:16.619><c> the</c><00:00:16.740><c> transactions</c>

00:00:17.269 --> 00:00:17.279 align:start position:0%
layers so what are the transactions
 

00:00:17.279 --> 00:00:19.609 align:start position:0%
layers so what are the transactions
first<00:00:17.630><c> benefactors</c><00:00:18.630><c> enable</c><00:00:18.960><c> fund</c><00:00:19.169><c> lists</c><00:00:19.439><c> keep</c>

00:00:19.609 --> 00:00:19.619 align:start position:0%
first benefactors enable fund lists keep
 

00:00:19.619 --> 00:00:22.580 align:start position:0%
first benefactors enable fund lists keep
bears<00:00:19.829><c> too</c><00:00:20.130><c> and</c><00:00:20.880><c> use</c><00:00:21.060><c> smart</c><00:00:21.329><c> contracts</c><00:00:21.840><c> rather</c>

00:00:22.580 --> 00:00:22.590 align:start position:0%
bears too and use smart contracts rather
 

00:00:22.590 --> 00:00:24.019 align:start position:0%
bears too and use smart contracts rather
than<00:00:22.829><c> spending</c><00:00:23.099><c> gasps</c><00:00:23.310><c> they</c><00:00:23.520><c> signed</c><00:00:23.849><c> their</c>

00:00:24.019 --> 00:00:24.029 align:start position:0%
than spending gasps they signed their
 

00:00:24.029 --> 00:00:25.909 align:start position:0%
than spending gasps they signed their
intended<00:00:24.480><c> action</c><00:00:24.900><c> and</c><00:00:25.320><c> using</c><00:00:25.650><c> their</c><00:00:25.770><c> private</c>

00:00:25.909 --> 00:00:25.919 align:start position:0%
intended action and using their private
 

00:00:25.919 --> 00:00:28.190 align:start position:0%
intended action and using their private
key<00:00:26.250><c> and</c><00:00:26.489><c> then</c><00:00:26.939><c> a</c><00:00:27.119><c> new</c><00:00:27.300><c> layer</c><00:00:27.450><c> broadcasts</c><00:00:28.110><c> on</c>

00:00:28.190 --> 00:00:28.200 align:start position:0%
key and then a new layer broadcasts on
 

00:00:28.200 --> 00:00:29.929 align:start position:0%
key and then a new layer broadcasts on
their<00:00:28.320><c> behalf</c><00:00:28.649><c> and</c><00:00:28.919><c> pays</c><00:00:29.369><c> the</c><00:00:29.550><c> associate</c>

00:00:29.929 --> 00:00:29.939 align:start position:0%
their behalf and pays the associate
 

00:00:29.939 --> 00:00:32.179 align:start position:0%
their behalf and pays the associate
entities<00:00:30.169><c> so</c><00:00:31.169><c> that</c><00:00:31.200><c> bloom</c><00:00:31.529><c> in</c><00:00:31.649><c> the</c><00:00:31.739><c> past</c><00:00:31.950><c> year</c>

00:00:32.179 --> 00:00:32.189 align:start position:0%
entities so that bloom in the past year
 

00:00:32.189 --> 00:00:34.639 align:start position:0%
entities so that bloom in the past year
we've<00:00:32.309><c> submitted</c><00:00:32.489><c> over</c><00:00:33.230><c> 250,000</c><00:00:34.230><c> of</c><00:00:34.440><c> meta</c>

00:00:34.639 --> 00:00:34.649 align:start position:0%
we've submitted over 250,000 of meta
 

00:00:34.649 --> 00:00:36.500 align:start position:0%
we've submitted over 250,000 of meta
transactions<00:00:35.190><c> on</c><00:00:35.280><c> bayonet</c><00:00:35.640><c> sometimes</c><00:00:36.239><c> it</c><00:00:36.360><c> has</c>

00:00:36.500 --> 00:00:36.510 align:start position:0%
transactions on bayonet sometimes it has
 

00:00:36.510 --> 00:00:38.779 align:start position:0%
transactions on bayonet sometimes it has
six<00:00:36.870><c> six</c><00:00:37.200><c> thousand</c><00:00:37.590><c> management</c><00:00:38.340><c> actions</c><00:00:38.640><c> in</c><00:00:38.730><c> a</c>

00:00:38.779 --> 00:00:38.789 align:start position:0%
six six thousand management actions in a
 

00:00:38.789 --> 00:00:40.970 align:start position:0%
six six thousand management actions in a
single<00:00:39.090><c> day</c><00:00:39.500><c> during</c><00:00:40.500><c> this</c><00:00:40.649><c> time</c><00:00:40.860><c> we</c><00:00:40.950><c> were</c>

00:00:40.970 --> 00:00:40.980 align:start position:0%
single day during this time we were
 

00:00:40.980 --> 00:00:44.209 align:start position:0%
single day during this time we were
spending<00:00:41.309><c> up</c><00:00:42.000><c> to</c><00:00:42.289><c> one</c><00:00:43.289><c> to</c><00:00:43.320><c> three</c><00:00:43.530><c> eat</c><00:00:43.949><c> per</c><00:00:44.190><c> day</c>

00:00:44.209 --> 00:00:44.219 align:start position:0%
spending up to one to three eat per day
 

00:00:44.219 --> 00:00:46.549 align:start position:0%
spending up to one to three eat per day
just<00:00:44.670><c> to</c><00:00:44.760><c> keep</c><00:00:44.789><c> our</c><00:00:45.210><c> benefits</c><00:00:45.989><c> actually</c><00:00:46.140><c> was</c>

00:00:46.549 --> 00:00:46.559 align:start position:0%
just to keep our benefits actually was
 

00:00:46.559 --> 00:00:48.860 align:start position:0%
just to keep our benefits actually was
going<00:00:46.739><c> this</c><00:00:47.519><c> has</c><00:00:47.670><c> to</c><00:00:47.789><c> do</c><00:00:47.940><c> with</c><00:00:47.969><c> like</c><00:00:48.269><c> identity</c>

00:00:48.860 --> 00:00:48.870 align:start position:0%
going this has to do with like identity
 

00:00:48.870 --> 00:00:51.829 align:start position:0%
going this has to do with like identity
credential<00:00:49.499><c> issuance</c><00:00:49.969><c> so</c><00:00:50.969><c> what</c><00:00:51.719><c> we've</c>

00:00:51.829 --> 00:00:51.839 align:start position:0%
credential issuance so what we've
 

00:00:51.839 --> 00:00:53.660 align:start position:0%
credential issuance so what we've
learned<00:00:52.079><c> pretty</c><00:00:52.440><c> early</c><00:00:52.559><c> on</c><00:00:52.920><c> is</c><00:00:53.190><c> that</c><00:00:53.219><c> simply</c>

00:00:53.660 --> 00:00:53.670 align:start position:0%
learned pretty early on is that simply
 

00:00:53.670 --> 00:00:55.459 align:start position:0%
learned pretty early on is that simply
broadcasting<00:00:54.480><c> the</c><00:00:54.539><c> transactions</c><00:00:55.140><c> does</c><00:00:55.319><c> not</c>

00:00:55.459 --> 00:00:55.469 align:start position:0%
broadcasting the transactions does not
 

00:00:55.469 --> 00:00:58.040 align:start position:0%
broadcasting the transactions does not
scale<00:00:55.769><c> you</c><00:00:56.129><c> can't</c><00:00:56.399><c> just</c><00:00:56.579><c> call</c><00:00:56.789><c> web</c><00:00:57.329><c> 310</c>

00:00:58.040 --> 00:00:58.050 align:start position:0%
scale you can't just call web 310
 

00:00:58.050 --> 00:00:59.930 align:start position:0%
scale you can't just call web 310
directly<00:00:58.559><c> to</c><00:00:58.649><c> SMEs</c><00:00:59.010><c> and</c><00:00:59.370><c> hope</c><00:00:59.550><c> that</c><00:00:59.789><c> it's</c>

00:00:59.930 --> 00:00:59.940 align:start position:0%
directly to SMEs and hope that it's
 

00:00:59.940 --> 00:01:02.149 align:start position:0%
directly to SMEs and hope that it's
going<00:01:00.089><c> to</c><00:01:00.179><c> work</c><00:01:00.449><c> confirmation</c><00:01:01.409><c> times</c><00:01:01.859><c> are</c>

00:01:02.149 --> 00:01:02.159 align:start position:0%
going to work confirmation times are
 

00:01:02.159 --> 00:01:04.759 align:start position:0%
going to work confirmation times are
long<00:01:03.030><c> and</c><00:01:03.059><c> they're</c><00:01:03.389><c> inconsistent</c><00:01:03.690><c> gas</c><00:01:04.350><c> prices</c>

00:01:04.759 --> 00:01:04.769 align:start position:0%
long and they're inconsistent gas prices
 

00:01:04.769 --> 00:01:06.710 align:start position:0%
long and they're inconsistent gas prices
can<00:01:04.890><c> be</c><00:01:04.920><c> volatile</c><00:01:05.430><c> and</c><00:01:05.760><c> there</c><00:01:06.270><c> are</c><00:01:06.360><c> frequently</c>

00:01:06.710 --> 00:01:06.720 align:start position:0%
can be volatile and there are frequently
 

00:01:06.720 --> 00:01:08.330 align:start position:0%
can be volatile and there are frequently
trade<00:01:07.020><c> chain</c><00:01:07.380><c> reorg</c><00:01:07.770><c> switch</c><00:01:08.100><c> drop</c>

00:01:08.330 --> 00:01:08.340 align:start position:0%
trade chain reorg switch drop
 

00:01:08.340 --> 00:01:13.149 align:start position:0%
trade chain reorg switch drop
transactions<00:01:10.790><c> so</c><00:01:11.790><c> the</c><00:01:11.909><c> first</c><00:01:12.090><c> thing</c><00:01:12.240><c> that</c><00:01:12.360><c> we</c>

00:01:13.149 --> 00:01:13.159 align:start position:0%
transactions so the first thing that we
 

00:01:13.159 --> 00:01:16.280 align:start position:0%
transactions so the first thing that we
encoded<00:01:14.159><c> into</c><00:01:14.370><c> this</c><00:01:14.580><c> service</c><00:01:14.940><c> which</c><00:01:15.300><c> handles</c>

00:01:16.280 --> 00:01:16.290 align:start position:0%
encoded into this service which handles
 

00:01:16.290 --> 00:01:19.490 align:start position:0%
encoded into this service which handles
very<00:01:17.070><c> high</c><00:01:17.280><c> volume</c><00:01:17.700><c> transactions</c><00:01:18.330><c> is</c><00:01:19.050><c> non</c>

00:01:19.490 --> 00:01:19.500 align:start position:0%
very high volume transactions is non
 

00:01:19.500 --> 00:01:23.150 align:start position:0%
very high volume transactions is non
store<00:01:19.860><c> casting</c><00:01:20.280><c> so</c><00:01:20.780><c> the</c><00:01:21.780><c> in</c><00:01:22.560><c> a</c><00:01:22.680><c> simple</c><00:01:23.010><c> piece</c>

00:01:23.150 --> 00:01:23.160 align:start position:0%
store casting so the in a simple piece
 

00:01:23.160 --> 00:01:25.670 align:start position:0%
store casting so the in a simple piece
on<00:01:23.340><c> the</c><00:01:23.430><c> left</c><00:01:23.460><c> you</c><00:01:24.060><c> can</c><00:01:24.090><c> see</c><00:01:24.240><c> that</c><00:01:24.720><c> we</c>

00:01:25.670 --> 00:01:25.680 align:start position:0%
on the left you can see that we
 

00:01:25.680 --> 00:01:27.770 align:start position:0%
on the left you can see that we
broadcast<00:01:25.950><c> one</c><00:01:26.460><c> transaction</c><00:01:26.820><c> witness</c><00:01:27.480><c> one</c>

00:01:27.770 --> 00:01:27.780 align:start position:0%
broadcast one transaction witness one
 

00:01:27.780 --> 00:01:29.750 align:start position:0%
broadcast one transaction witness one
zero<00:01:27.990><c> zero</c><00:01:28.020><c> one</c><00:01:28.230><c> and</c><00:01:28.620><c> everything</c><00:01:29.490><c> else</c><00:01:29.610><c> is</c>

00:01:29.750 --> 00:01:29.760 align:start position:0%
zero zero one and everything else is
 

00:01:29.760 --> 00:01:31.970 align:start position:0%
zero zero one and everything else is
blocked<00:01:30.060><c> so</c><00:01:30.780><c> they</c><00:01:30.900><c> can't</c><00:01:31.140><c> all</c><00:01:31.350><c> be</c><00:01:31.380><c> mined</c><00:01:31.860><c> in</c>

00:01:31.970 --> 00:01:31.980 align:start position:0%
blocked so they can't all be mined in
 

00:01:31.980 --> 00:01:33.650 align:start position:0%
blocked so they can't all be mined in
the<00:01:32.040><c> same</c><00:01:32.220><c> block</c><00:01:32.460><c> instead</c><00:01:33.120><c> what</c><00:01:33.270><c> you</c><00:01:33.360><c> can</c><00:01:33.510><c> do</c>

00:01:33.650 --> 00:01:33.660 align:start position:0%
the same block instead what you can do
 

00:01:33.660 --> 00:01:35.870 align:start position:0%
the same block instead what you can do
is<00:01:33.960><c> use</c><00:01:34.290><c> the</c><00:01:34.320><c> nos</c><00:01:34.590><c> field</c><00:01:34.920><c> of</c><00:01:35.100><c> send</c><00:01:35.280><c> transaction</c>

00:01:35.870 --> 00:01:35.880 align:start position:0%
is use the nos field of send transaction
 

00:01:35.880 --> 00:01:38.180 align:start position:0%
is use the nos field of send transaction
so<00:01:36.330><c> that</c><00:01:36.480><c> you</c><00:01:36.570><c> can</c><00:01:36.750><c> do</c><00:01:37.110><c> one</c><00:01:37.710><c> thousand</c><00:01:38.040><c> one</c>

00:01:38.180 --> 00:01:38.190 align:start position:0%
so that you can do one thousand one
 

00:01:38.190 --> 00:01:39.680 align:start position:0%
so that you can do one thousand one
three<00:01:38.430><c> one</c><00:01:38.640><c> thousand</c><00:01:38.970><c> five</c><00:01:39.090><c> and</c><00:01:39.420><c> you</c><00:01:39.480><c> can</c><00:01:39.600><c> have</c>

00:01:39.680 --> 00:01:39.690 align:start position:0%
three one thousand five and you can have
 

00:01:39.690 --> 00:01:41.120 align:start position:0%
three one thousand five and you can have
all<00:01:39.900><c> of</c><00:01:40.020><c> these</c><00:01:40.110><c> tapped</c><00:01:40.380><c> into</c><00:01:40.560><c> the</c><00:01:40.710><c> same</c><00:01:40.890><c> block</c>

00:01:41.120 --> 00:01:41.130 align:start position:0%
all of these tapped into the same block
 

00:01:41.130 --> 00:01:44.720 align:start position:0%
all of these tapped into the same block
without<00:01:41.760><c> waiting</c><00:01:41.970><c> for</c><00:01:42.120><c> mining</c><00:01:43.310><c> when</c><00:01:44.310><c> there</c><00:01:44.520><c> is</c>

00:01:44.720 --> 00:01:44.730 align:start position:0%
without waiting for mining when there is
 

00:01:44.730 --> 00:01:47.210 align:start position:0%
without waiting for mining when there is
a<00:01:45.000><c> non</c><00:01:45.480><c> set</c><00:01:45.780><c> blocking</c><00:01:46.290><c> the</c><00:01:46.530><c> next</c><00:01:46.770><c> one</c><00:01:46.890><c> so</c><00:01:47.070><c> if</c>

00:01:47.210 --> 00:01:47.220 align:start position:0%
a non set blocking the next one so if
 

00:01:47.220 --> 00:01:48.710 align:start position:0%
a non set blocking the next one so if
we're<00:01:47.520><c> waiting</c><00:01:47.820><c> for</c><00:01:47.850><c> one</c><00:01:48.120><c> zero</c><00:01:48.330><c> zero</c><00:01:48.360><c> two</c><00:01:48.690><c> two</c>

00:01:48.710 --> 00:01:48.720 align:start position:0%
we're waiting for one zero zero two two
 

00:01:48.720 --> 00:01:50.990 align:start position:0%
we're waiting for one zero zero two two
mine<00:01:48.990><c> we</c><00:01:49.320><c> need</c><00:01:49.470><c> to</c><00:01:49.560><c> aggressively</c><00:01:50.000><c> rebroadcast</c>

00:01:50.990 --> 00:01:51.000 align:start position:0%
mine we need to aggressively rebroadcast
 

00:01:51.000 --> 00:01:53.030 align:start position:0%
mine we need to aggressively rebroadcast
that<00:01:51.270><c> transaction</c><00:01:51.870><c> with</c><00:01:52.200><c> a</c><00:01:52.230><c> high</c><00:01:52.410><c> of</c><00:01:52.530><c> gas</c>

00:01:53.030 --> 00:01:53.040 align:start position:0%
that transaction with a high of gas
 

00:01:53.040 --> 00:01:55.010 align:start position:0%
that transaction with a high of gas
until<00:01:53.250><c> it</c><00:01:53.370><c> goes</c><00:01:53.490><c> through</c><00:01:53.790><c> so</c><00:01:54.210><c> this</c><00:01:54.330><c> happens</c><00:01:54.720><c> in</c>

00:01:55.010 --> 00:01:55.020 align:start position:0%
until it goes through so this happens in
 

00:01:55.020 --> 00:01:56.720 align:start position:0%
until it goes through so this happens in
the<00:01:55.140><c> service</c><00:01:55.440><c> every</c><00:01:55.680><c> 30</c><00:01:55.920><c> seconds</c><00:01:56.370><c> it</c>

00:01:56.720 --> 00:01:56.730 align:start position:0%
the service every 30 seconds it
 

00:01:56.730 --> 00:01:58.790 align:start position:0%
the service every 30 seconds it
rebroadcast<00:01:57.150><c> with</c><00:01:57.630><c> a</c><00:01:57.720><c> point</c><00:01:57.960><c> one</c><00:01:58.140><c> Waymire</c><00:01:58.560><c> gas</c>

00:01:58.790 --> 00:01:58.800 align:start position:0%
rebroadcast with a point one Waymire gas
 

00:01:58.800 --> 00:02:02.300 align:start position:0%
rebroadcast with a point one Waymire gas
price<00:01:59.100><c> in</c><00:01:59.820><c> order</c><00:02:00.150><c> to</c><00:02:00.470><c> force</c><00:02:01.470><c> it</c><00:02:01.650><c> through</c><00:02:01.680><c> so</c>

00:02:02.300 --> 00:02:02.310 align:start position:0%
price in order to force it through so
 

00:02:02.310 --> 00:02:03.800 align:start position:0%
price in order to force it through so
that<00:02:02.340><c> every</c><00:02:02.700><c> other</c><00:02:02.820><c> transaction</c><00:02:03.390><c> will</c><00:02:03.480><c> endure</c>

00:02:03.800 --> 00:02:03.810 align:start position:0%
that every other transaction will endure
 

00:02:03.810 --> 00:02:06.770 align:start position:0%
that every other transaction will endure
blocked<00:02:04.080><c> we</c><00:02:05.070><c> found</c><00:02:05.400><c> that</c><00:02:05.790><c> on</c><00:02:06.000><c> an</c><00:02:06.120><c> average</c><00:02:06.240><c> each</c>

00:02:06.770 --> 00:02:06.780 align:start position:0%
blocked we found that on an average each
 

00:02:06.780 --> 00:02:08.900 align:start position:0%
blocked we found that on an average each
transaction<00:02:07.200><c> needed</c><00:02:07.680><c> to</c><00:02:07.770><c> be</c><00:02:07.860><c> broadcast</c><00:02:08.369><c> twice</c>

00:02:08.900 --> 00:02:08.910 align:start position:0%
transaction needed to be broadcast twice
 

00:02:08.910 --> 00:02:12.110 align:start position:0%
transaction needed to be broadcast twice
to<00:02:09.360><c> go</c><00:02:09.509><c> through</c><00:02:09.780><c> so</c><00:02:10.320><c> this</c><00:02:10.740><c> when</c><00:02:11.280><c> I</c><00:02:11.580><c> set</c><00:02:11.880><c> up</c><00:02:11.910><c> this</c>

00:02:12.110 --> 00:02:12.120 align:start position:0%
to go through so this when I set up this
 

00:02:12.120 --> 00:02:14.390 align:start position:0%
to go through so this when I set up this
inelastic<00:02:12.900><c> sac</c><00:02:13.110><c> when</c><00:02:13.890><c> I</c><00:02:13.920><c> looked</c><00:02:14.190><c> in</c><00:02:14.310><c> the</c>

00:02:14.390 --> 00:02:14.400 align:start position:0%
inelastic sac when I looked in the
 

00:02:14.400 --> 00:02:15.950 align:start position:0%
inelastic sac when I looked in the
morning<00:02:14.700><c> this</c><00:02:14.790><c> look</c><00:02:15.000><c> healthy</c><00:02:15.300><c> to</c><00:02:15.330><c> me</c>

00:02:15.950 --> 00:02:15.960 align:start position:0%
morning this look healthy to me
 

00:02:15.960 --> 00:02:17.750 align:start position:0%
morning this look healthy to me
there<00:02:16.320><c> were</c><00:02:16.500><c> transactions</c><00:02:17.160><c> being</c><00:02:17.340><c> created</c><00:02:17.670><c> on</c>

00:02:17.750 --> 00:02:17.760 align:start position:0%
there were transactions being created on
 

00:02:17.760 --> 00:02:19.190 align:start position:0%
there were transactions being created on
the<00:02:17.850><c> bottom</c><00:02:18.150><c> and</c><00:02:18.360><c> then</c><00:02:18.750><c> they</c><00:02:18.870><c> were</c><00:02:18.930><c> being</c>

00:02:19.190 --> 00:02:19.200 align:start position:0%
the bottom and then they were being
 

00:02:19.200 --> 00:02:24.230 align:start position:0%
the bottom and then they were being
committed<00:02:19.590><c> or</c><00:02:19.920><c> rebroadcast</c><00:02:20.220><c> on</c><00:02:20.910><c> the</c><00:02:21.030><c> top</c><00:02:23.240><c> gas</c>

00:02:24.230 --> 00:02:24.240 align:start position:0%
committed or rebroadcast on the top gas
 

00:02:24.240 --> 00:02:26.630 align:start position:0%
committed or rebroadcast on the top gas
prices<00:02:24.720><c> sometimes</c><00:02:25.110><c> spiked</c><00:02:25.709><c> very</c><00:02:25.980><c> high</c><00:02:26.190><c> that's</c>

00:02:26.630 --> 00:02:26.640 align:start position:0%
prices sometimes spiked very high that's
 

00:02:26.640 --> 00:02:28.210 align:start position:0%
prices sometimes spiked very high that's
important<00:02:27.120><c> to</c><00:02:27.209><c> set</c><00:02:27.360><c> a</c><00:02:27.390><c> cap</c><00:02:27.600><c> and</c><00:02:27.810><c> wait</c><00:02:27.990><c> it</c><00:02:28.110><c> out</c>

00:02:28.210 --> 00:02:28.220 align:start position:0%
important to set a cap and wait it out
 

00:02:28.220 --> 00:02:32.210 align:start position:0%
important to set a cap and wait it out
because<00:02:29.220><c> gas</c><00:02:29.850><c> prices</c><00:02:30.270><c> are</c><00:02:30.510><c> volatile</c><00:02:31.200><c> but</c><00:02:32.100><c> if</c>

00:02:32.210 --> 00:02:32.220 align:start position:0%
because gas prices are volatile but if
 

00:02:32.220 --> 00:02:33.680 align:start position:0%
because gas prices are volatile but if
we<00:02:32.340><c> filter</c><00:02:32.700><c> out</c><00:02:32.730><c> everything</c><00:02:33.000><c> above</c><00:02:33.480><c> a</c><00:02:33.510><c> hundred</c>

00:02:33.680 --> 00:02:33.690 align:start position:0%
we filter out everything above a hundred
 

00:02:33.690 --> 00:02:36.650 align:start position:0%
we filter out everything above a hundred
way<00:02:34.080><c> it's</c><00:02:34.800><c> actually</c><00:02:34.980><c> pretty</c><00:02:35.280><c> consistent</c><00:02:35.880><c> so</c>

00:02:36.650 --> 00:02:36.660 align:start position:0%
way it's actually pretty consistent so
 

00:02:36.660 --> 00:02:38.630 align:start position:0%
way it's actually pretty consistent so
if<00:02:36.690><c> you</c><00:02:37.080><c> were</c><00:02:37.410><c> spending</c><00:02:37.770><c> you</c><00:02:38.310><c> know</c><00:02:38.370><c> maybe</c>

00:02:38.630 --> 00:02:38.640 align:start position:0%
if you were spending you know maybe
 

00:02:38.640 --> 00:02:40.280 align:start position:0%
if you were spending you know maybe
somebody<00:02:38.910><c> has</c><00:02:39.209><c> some</c><00:02:39.360><c> arbitrage</c><00:02:39.720><c> opportunity</c>

00:02:40.280 --> 00:02:40.290 align:start position:0%
somebody has some arbitrage opportunity
 

00:02:40.290 --> 00:02:43.460 align:start position:0%
somebody has some arbitrage opportunity
way<00:02:40.440><c> back</c><00:02:40.650><c> in</c><00:02:41.070><c> a</c><00:02:41.310><c> sip</c><00:02:41.790><c> end</c><00:02:42.000><c> in</c><00:02:42.200><c> February</c><00:02:43.200><c> you</c>

00:02:43.460 --> 00:02:43.470 align:start position:0%
way back in a sip end in February you
 

00:02:43.470 --> 00:02:44.870 align:start position:0%
way back in a sip end in February you
didn't<00:02:43.950><c> want</c><00:02:44.130><c> to</c><00:02:44.190><c> be</c><00:02:44.250><c> competing</c><00:02:44.489><c> with</c><00:02:44.610><c> every</c>

00:02:44.870 --> 00:02:44.880 align:start position:0%
didn't want to be competing with every
 

00:02:44.880 --> 00:02:45.380 align:start position:0%
didn't want to be competing with every
gas

00:02:45.380 --> 00:02:45.390 align:start position:0%
gas
 

00:02:45.390 --> 00:02:47.720 align:start position:0%
gas
just<00:02:45.720><c> wait</c><00:02:45.870><c> a</c><00:02:45.900><c> little</c><00:02:46.110><c> bit</c><00:02:46.320><c> and</c><00:02:47.100><c> then</c><00:02:47.310><c> you</c><00:02:47.700><c> can</c>

00:02:47.720 --> 00:02:47.730 align:start position:0%
just wait a little bit and then you can
 

00:02:47.730 --> 00:02:50.960 align:start position:0%
just wait a little bit and then you can
get<00:02:48.330><c> your</c><00:02:48.600><c> transaction</c><00:02:49.500><c> through</c><00:02:49.680><c> our</c><00:02:50.489><c> actual</c>

00:02:50.960 --> 00:02:50.970 align:start position:0%
get your transaction through our actual
 

00:02:50.970 --> 00:02:52.820 align:start position:0%
get your transaction through our actual
spending<00:02:51.209><c> ended</c><00:02:51.660><c> up</c><00:02:51.750><c> being</c><00:02:51.989><c> far</c><00:02:52.500><c> less</c><00:02:52.800><c> than</c>

00:02:52.820 --> 00:02:52.830 align:start position:0%
spending ended up being far less than
 

00:02:52.830 --> 00:02:54.410 align:start position:0%
spending ended up being far less than
the<00:02:53.070><c> average</c><00:02:53.250><c> but</c><00:02:53.700><c> we</c><00:02:53.790><c> still</c><00:02:53.910><c> have</c><00:02:54.090><c> very</c><00:02:54.239><c> high</c>

00:02:54.410 --> 00:02:54.420 align:start position:0%
the average but we still have very high
 

00:02:54.420 --> 00:02:58.220 align:start position:0%
the average but we still have very high
throughput<00:02:55.220><c> also</c><00:02:56.220><c> during</c><00:02:56.870><c> when</c><00:02:57.870><c> the</c><00:02:58.019><c> network</c>

00:02:58.220 --> 00:02:58.230 align:start position:0%
throughput also during when the network
 

00:02:58.230 --> 00:03:00.259 align:start position:0%
throughput also during when the network
is<00:02:58.320><c> very</c><00:02:58.350><c> congested</c><00:02:58.860><c> mining</c><00:02:59.790><c> will</c><00:02:59.910><c> sometimes</c>

00:03:00.259 --> 00:03:00.269 align:start position:0%
is very congested mining will sometimes
 

00:03:00.269 --> 00:03:03.320 align:start position:0%
is very congested mining will sometimes
lag<00:03:00.540><c> by</c><00:03:00.810><c> many</c><00:03:01.019><c> hours</c><00:03:01.470><c> and</c><00:03:02.430><c> you</c><00:03:03.060><c> might</c><00:03:03.209><c> be</c>

00:03:03.320 --> 00:03:03.330 align:start position:0%
lag by many hours and you might be
 

00:03:03.330 --> 00:03:05.060 align:start position:0%
lag by many hours and you might be
concerned<00:03:03.660><c> that</c><00:03:03.930><c> it'll</c><00:03:04.080><c> never</c><00:03:04.110><c> catch</c><00:03:04.410><c> up</c><00:03:04.650><c> but</c>

00:03:05.060 --> 00:03:05.070 align:start position:0%
concerned that it'll never catch up but
 

00:03:05.070 --> 00:03:07.250 align:start position:0%
concerned that it'll never catch up but
as<00:03:05.190><c> soon</c><00:03:05.400><c> as</c><00:03:05.519><c> the</c><00:03:06.420><c> number</c><00:03:06.690><c> congestion</c><00:03:07.110><c> goes</c>

00:03:07.250 --> 00:03:07.260 align:start position:0%
as soon as the number congestion goes
 

00:03:07.260 --> 00:03:10.210 align:start position:0%
as soon as the number congestion goes
away<00:03:07.470><c> the</c><00:03:08.040><c> backlog</c><00:03:08.459><c> clears</c><00:03:08.820><c> and</c><00:03:09.090><c> then</c><00:03:09.660><c> you're</c>

00:03:10.210 --> 00:03:10.220 align:start position:0%
away the backlog clears and then you're
 

00:03:10.220 --> 00:03:12.890 align:start position:0%
away the backlog clears and then you're
broadcasting<00:03:11.220><c> at</c><00:03:11.610><c> mining</c><00:03:11.910><c> times</c><00:03:12.180><c> get</c><00:03:12.750><c> much</c>

00:03:12.890 --> 00:03:12.900 align:start position:0%
broadcasting at mining times get much
 

00:03:12.900 --> 00:03:16.310 align:start position:0%
broadcasting at mining times get much
closer<00:03:13.110><c> together</c><00:03:14.720><c> one</c><00:03:15.720><c> last</c><00:03:15.870><c> thing</c><00:03:16.110><c> that</c><00:03:16.140><c> you</c>

00:03:16.310 --> 00:03:16.320 align:start position:0%
closer together one last thing that you
 

00:03:16.320 --> 00:03:18.710 align:start position:0%
closer together one last thing that you
also<00:03:16.470><c> shouldn't</c><00:03:16.799><c> look</c><00:03:16.920><c> for</c><00:03:17.160><c> is</c><00:03:17.880><c> chain</c><00:03:18.299><c> reports</c>

00:03:18.710 --> 00:03:18.720 align:start position:0%
also shouldn't look for is chain reports
 

00:03:18.720 --> 00:03:20.330 align:start position:0%
also shouldn't look for is chain reports
so<00:03:19.110><c> we</c><00:03:19.230><c> have</c><00:03:19.320><c> first</c><00:03:19.680><c> you</c><00:03:19.890><c> think</c><00:03:20.100><c> that</c>

00:03:20.330 --> 00:03:20.340 align:start position:0%
so we have first you think that
 

00:03:20.340 --> 00:03:21.830 align:start position:0%
so we have first you think that
something<00:03:20.610><c> was</c><00:03:20.700><c> mined</c><00:03:20.970><c> but</c><00:03:21.450><c> later</c><00:03:21.660><c> your</c>

00:03:21.830 --> 00:03:21.840 align:start position:0%
something was mined but later your
 

00:03:21.840 --> 00:03:23.660 align:start position:0%
something was mined but later your
transactions<00:03:22.320><c> are</c><00:03:22.380><c> not</c><00:03:22.410><c> being</c><00:03:22.680><c> broadcast</c><00:03:23.220><c> you</c>

00:03:23.660 --> 00:03:23.670 align:start position:0%
transactions are not being broadcast you
 

00:03:23.670 --> 00:03:24.949 align:start position:0%
transactions are not being broadcast you
should<00:03:23.820><c> go</c><00:03:24.120><c> back</c><00:03:24.299><c> and</c><00:03:24.360><c> look</c><00:03:24.660><c> at</c><00:03:24.780><c> the</c><00:03:24.840><c> most</c>

00:03:24.949 --> 00:03:24.959 align:start position:0%
should go back and look at the most
 

00:03:24.959 --> 00:03:26.930 align:start position:0%
should go back and look at the most
recent<00:03:25.110><c> transactions</c><00:03:25.860><c> see</c><00:03:26.340><c> if</c><00:03:26.459><c> it's</c><00:03:26.700><c> dropped</c>

00:03:26.930 --> 00:03:26.940 align:start position:0%
recent transactions see if it's dropped
 

00:03:26.940 --> 00:03:29.540 align:start position:0%
recent transactions see if it's dropped
and<00:03:27.239><c> then</c><00:03:27.540><c> you</c><00:03:27.989><c> can</c><00:03:28.140><c> either</c><00:03:28.230><c> fulfill</c><00:03:28.860><c> it</c>

00:03:29.540 --> 00:03:29.550 align:start position:0%
and then you can either fulfill it
 

00:03:29.550 --> 00:03:32.120 align:start position:0%
and then you can either fulfill it
value<00:03:30.510><c> exacted</c><00:03:30.840><c> or</c><00:03:31.410><c> you</c><00:03:31.620><c> can</c><00:03:31.770><c> actually</c><00:03:31.890><c> go</c>

00:03:32.120 --> 00:03:32.130 align:start position:0%
value exacted or you can actually go
 

00:03:32.130 --> 00:03:36.100 align:start position:0%
value exacted or you can actually go
back<00:03:32.160><c> and</c><00:03:32.430><c> read</c><00:03:32.550><c> broadcast</c><00:03:32.970><c> at</c><00:03:33.150><c> one</c><00:03:34.880><c> so</c>

00:03:36.100 --> 00:03:36.110 align:start position:0%
back and read broadcast at one so
 

00:03:36.110 --> 00:03:38.420 align:start position:0%
back and read broadcast at one so
finally<00:03:37.110><c> I</c><00:03:37.260><c> just</c><00:03:37.350><c> open</c><00:03:37.860><c> source</c><00:03:38.040><c> this</c><00:03:38.190><c> about</c>

00:03:38.420 --> 00:03:38.430 align:start position:0%
finally I just open source this about
 

00:03:38.430 --> 00:03:40.370 align:start position:0%
finally I just open source this about
ten<00:03:38.670><c> minutes</c><00:03:38.790><c> ago</c><00:03:39.030><c> this</c><00:03:39.510><c> service</c><00:03:40.350><c> that</c>

00:03:40.370 --> 00:03:40.380 align:start position:0%
ten minutes ago this service that
 

00:03:40.380 --> 00:03:42.110 align:start position:0%
ten minutes ago this service that
actually<00:03:40.890><c> handled</c><00:03:41.250><c> all</c><00:03:41.340><c> this</c><00:03:41.460><c> logic</c><00:03:41.700><c> for</c><00:03:42.030><c> you</c>

00:03:42.110 --> 00:03:42.120 align:start position:0%
actually handled all this logic for you
 

00:03:42.120 --> 00:03:44.780 align:start position:0%
actually handled all this logic for you
and<00:03:42.600><c> it's</c><00:03:43.500><c> very</c><00:03:43.770><c> balloon</c><00:03:44.130><c> specific</c><00:03:44.580><c> now</c><00:03:44.730><c> you</c>

00:03:44.780 --> 00:03:44.790 align:start position:0%
and it's very balloon specific now you
 

00:03:44.790 --> 00:03:46.850 align:start position:0%
and it's very balloon specific now you
actually<00:03:45.120><c> have</c><00:03:45.300><c> to</c><00:03:45.510><c> encode</c><00:03:45.870><c> a</c><00:03:46.170><c> lot</c><00:03:46.590><c> of</c><00:03:46.680><c> the</c>

00:03:46.850 --> 00:03:46.860 align:start position:0%
actually have to encode a lot of the
 

00:03:46.860 --> 00:03:49.070 align:start position:0%
actually have to encode a lot of the
contract<00:03:47.700><c> logic</c><00:03:48.000><c> that</c><00:03:48.150><c> I</c><00:03:48.240><c> would</c><00:03:48.330><c> love</c><00:03:48.510><c> that</c><00:03:48.780><c> I</c>

00:03:49.070 --> 00:03:49.080 align:start position:0%
contract logic that I would love that I
 

00:03:49.080 --> 00:03:50.420 align:start position:0%
contract logic that I would love that I
try<00:03:49.230><c> to</c><00:03:49.290><c> get</c><00:03:49.440><c> some</c><00:03:49.650><c> other</c><00:03:49.800><c> companies</c><00:03:50.190><c> set</c><00:03:50.400><c> up</c>

00:03:50.420 --> 00:03:50.430 align:start position:0%
try to get some other companies set up
 

00:03:50.430 --> 00:03:52.880 align:start position:0%
try to get some other companies set up
with<00:03:50.610><c> this</c><00:03:50.700><c> service</c><00:03:51.030><c> it</c><00:03:51.750><c> does</c><00:03:51.930><c> a</c><00:03:51.960><c> lot</c><00:03:52.230><c> of</c><00:03:52.320><c> a</c>

00:03:52.880 --> 00:03:52.890 align:start position:0%
with this service it does a lot of a
 

00:03:52.890 --> 00:03:55.940 align:start position:0%
with this service it does a lot of a
camel<00:03:53.490><c> a</c><00:03:53.550><c> lot</c><00:03:53.700><c> with</c><00:03:54.660><c> us</c><00:03:54.750><c> awhile</c><00:03:54.900><c> to</c><00:03:55.020><c> the</c><00:03:55.350><c> to</c>

00:03:55.940 --> 00:03:55.950 align:start position:0%
camel a lot with us awhile to the to
 

00:03:55.950 --> 00:03:58.010 align:start position:0%
camel a lot with us awhile to the to
figure<00:03:55.980><c> out</c><00:03:56.340><c> so</c><00:03:56.820><c> please</c><00:03:57.420><c> take</c><00:03:57.570><c> a</c><00:03:57.630><c> look</c>

00:03:58.010 --> 00:03:58.020 align:start position:0%
figure out so please take a look
 

00:03:58.020 --> 00:04:00.050 align:start position:0%
figure out so please take a look
let<00:03:58.200><c> me</c><00:03:58.320><c> uses</c><00:03:58.560><c> PG</c><00:03:58.830><c> boss</c><00:03:59.010><c> for</c><00:03:59.250><c> the</c><00:03:59.310><c> queuing</c><00:03:59.640><c> is</c>

00:04:00.050 --> 00:04:00.060 align:start position:0%
let me uses PG boss for the queuing is
 

00:04:00.060 --> 00:04:02.060 align:start position:0%
let me uses PG boss for the queuing is
all<00:04:00.270><c> paid</c><00:04:00.510><c> script</c><00:04:00.840><c> so</c><00:04:01.080><c> use</c><00:04:01.260><c> type</c><00:04:01.470><c> chain</c><00:04:01.710><c> for</c>

00:04:02.060 --> 00:04:02.070 align:start position:0%
all paid script so use type chain for
 

00:04:02.070 --> 00:04:05.480 align:start position:0%
all paid script so use type chain for
contract<00:04:03.000><c> leggings</c><00:04:03.380><c> check</c><00:04:04.380><c> it</c><00:04:04.500><c> out</c><00:04:04.590><c> and</c><00:04:04.800><c> every</c>

00:04:05.480 --> 00:04:05.490 align:start position:0%
contract leggings check it out and every
 

00:04:05.490 --> 00:04:10.030 align:start position:0%
contract leggings check it out and every
little<00:04:05.670><c> T</c><00:04:05.940><c> with</c><00:04:06.030><c> it</c><00:04:06.150><c> thanks</c>

00:04:10.030 --> 00:04:10.040 align:start position:0%
 
 

00:04:10.040 --> 00:04:16.409 align:start position:0%
 
[Applause]