WEBVTT
Kind: captions
Language: en

00:00:00.060 --> 00:00:02.840 align:start position:0%
 
so<00:00:00.689><c> yeah</c><00:00:00.869><c> it's</c><00:00:01.109><c> a</c><00:00:01.170><c> fun</c><00:00:01.349><c> I'm</c><00:00:02.040><c> here</c><00:00:02.370><c> representing</c>

00:00:02.840 --> 00:00:02.850 align:start position:0%
so yeah it's a fun I'm here representing
 

00:00:02.850 --> 00:00:04.730 align:start position:0%
so yeah it's a fun I'm here representing
Lib<00:00:03.389><c> submarine</c><00:00:03.780><c> I</c><00:00:04.020><c> spend</c><00:00:04.410><c> most</c><00:00:04.500><c> of</c><00:00:04.620><c> my</c><00:00:04.680><c> time</c>

00:00:04.730 --> 00:00:04.740 align:start position:0%
Lib submarine I spend most of my time
 

00:00:04.740 --> 00:00:07.250 align:start position:0%
Lib submarine I spend most of my time
thinking<00:00:04.950><c> about</c><00:00:05.340><c> security</c><00:00:06.120><c> tokens</c><00:00:06.690><c> so</c><00:00:07.140><c> he's</c>

00:00:07.250 --> 00:00:07.260 align:start position:0%
thinking about security tokens so he's
 

00:00:07.260 --> 00:00:08.600 align:start position:0%
thinking about security tokens so he's
financial<00:00:07.740><c> securities</c><00:00:08.189><c> had</c><00:00:08.400><c> we</c><00:00:08.519><c> actually</c>

00:00:08.600 --> 00:00:08.610 align:start position:0%
financial securities had we actually
 

00:00:08.610 --> 00:00:10.579 align:start position:0%
financial securities had we actually
represent<00:00:09.120><c> them</c><00:00:09.240><c> on</c><00:00:09.299><c> the</c><00:00:09.419><c> blockchain</c><00:00:09.629><c> but</c>

00:00:10.579 --> 00:00:10.589 align:start position:0%
represent them on the blockchain but
 

00:00:10.589 --> 00:00:11.930 align:start position:0%
represent them on the blockchain but
I've<00:00:10.799><c> been</c><00:00:10.919><c> fortunate</c><00:00:11.160><c> enough</c><00:00:11.370><c> over</c><00:00:11.759><c> the</c><00:00:11.849><c> last</c>

00:00:11.930 --> 00:00:11.940 align:start position:0%
I've been fortunate enough over the last
 

00:00:11.940 --> 00:00:13.730 align:start position:0%
I've been fortunate enough over the last
few<00:00:12.150><c> months</c><00:00:12.209><c> to</c><00:00:12.570><c> work</c><00:00:12.870><c> with</c><00:00:13.169><c> some</c><00:00:13.679><c> incredible</c>

00:00:13.730 --> 00:00:13.740 align:start position:0%
few months to work with some incredible
 

00:00:13.740 --> 00:00:16.010 align:start position:0%
few months to work with some incredible
people<00:00:14.129><c> and</c><00:00:14.490><c> implementing</c><00:00:15.119><c> Lib</c><00:00:15.539><c> submarine</c>

00:00:16.010 --> 00:00:16.020 align:start position:0%
people and implementing Lib submarine
 

00:00:16.020 --> 00:00:18.350 align:start position:0%
people and implementing Lib submarine
which<00:00:16.290><c> comes</c><00:00:16.620><c> off</c><00:00:16.770><c> of</c><00:00:16.800><c> the</c><00:00:17.100><c> work</c><00:00:17.280><c> that</c><00:00:17.640><c> has</c>

00:00:18.350 --> 00:00:18.360 align:start position:0%
which comes off of the work that has
 

00:00:18.360 --> 00:00:20.240 align:start position:0%
which comes off of the work that has
been<00:00:18.510><c> done</c><00:00:18.660><c> that</c><00:00:18.840><c> I</c><00:00:19.080><c> see</c><00:00:19.290><c> three</c><00:00:19.530><c> out</c><00:00:20.190><c> of</c>

00:00:20.240 --> 00:00:20.250 align:start position:0%
been done that I see three out of
 

00:00:20.250 --> 00:00:23.240 align:start position:0%
been done that I see three out of
Cornell<00:00:20.900><c> so</c><00:00:21.900><c> Lib</c><00:00:22.440><c> submarine</c><00:00:22.830><c> there</c><00:00:23.130><c> was</c><00:00:23.220><c> a</c>

00:00:23.240 --> 00:00:23.250 align:start position:0%
Cornell so Lib submarine there was a
 

00:00:23.250 --> 00:00:26.120 align:start position:0%
Cornell so Lib submarine there was a
previous<00:00:23.520><c> talk</c><00:00:23.840><c> earlier</c><00:00:24.840><c> today</c><00:00:25.130><c> describing</c>

00:00:26.120 --> 00:00:26.130 align:start position:0%
previous talk earlier today describing
 

00:00:26.130 --> 00:00:27.740 align:start position:0%
previous talk earlier today describing
how<00:00:26.250><c> the</c><00:00:26.310><c> mechanism</c><00:00:26.820><c> is</c><00:00:26.940><c> actually</c><00:00:27.120><c> used</c><00:00:27.570><c> to</c>

00:00:27.740 --> 00:00:27.750 align:start position:0%
how the mechanism is actually used to
 

00:00:27.750 --> 00:00:29.630 align:start position:0%
how the mechanism is actually used to
prevent<00:00:27.990><c> front</c><00:00:28.290><c> running</c><00:00:28.620><c> on</c><00:00:28.770><c> decentralized</c>

00:00:29.630 --> 00:00:29.640 align:start position:0%
prevent front running on decentralized
 

00:00:29.640 --> 00:00:31.910 align:start position:0%
prevent front running on decentralized
exchanges<00:00:30.180><c> my</c><00:00:31.050><c> talk</c><00:00:31.290><c> today</c><00:00:31.440><c> is</c><00:00:31.530><c> gonna</c><00:00:31.680><c> talk</c>

00:00:31.910 --> 00:00:31.920 align:start position:0%
exchanges my talk today is gonna talk
 

00:00:31.920 --> 00:00:34.340 align:start position:0%
exchanges my talk today is gonna talk
about<00:00:32.070><c> how</c><00:00:32.640><c> do</c><00:00:32.699><c> we</c><00:00:32.940><c> actually</c><00:00:33.149><c> implement</c><00:00:33.719><c> those</c>

00:00:34.340 --> 00:00:34.350 align:start position:0%
about how do we actually implement those
 

00:00:34.350 --> 00:00:36.470 align:start position:0%
about how do we actually implement those
what<00:00:35.309><c> does</c><00:00:35.399><c> it</c><00:00:35.519><c> look</c><00:00:35.670><c> like</c><00:00:35.730><c> from</c><00:00:36.149><c> the</c><00:00:36.210><c> smart</c>

00:00:36.470 --> 00:00:36.480 align:start position:0%
what does it look like from the smart
 

00:00:36.480 --> 00:00:37.849 align:start position:0%
what does it look like from the smart
contracts<00:00:36.839><c> perspective</c><00:00:37.289><c> and</c><00:00:37.530><c> how</c><00:00:37.620><c> does</c><00:00:37.679><c> it</c>

00:00:37.849 --> 00:00:37.859 align:start position:0%
contracts perspective and how does it
 

00:00:37.859 --> 00:00:39.500 align:start position:0%
contracts perspective and how does it
look<00:00:38.039><c> like</c><00:00:38.219><c> from</c><00:00:38.399><c> the</c><00:00:38.489><c> DOT</c><00:00:38.730><c> perspective</c><00:00:39.300><c> to</c>

00:00:39.500 --> 00:00:39.510 align:start position:0%
look like from the DOT perspective to
 

00:00:39.510 --> 00:00:42.349 align:start position:0%
look like from the DOT perspective to
work<00:00:39.929><c> with</c><00:00:40.170><c> Lib</c><00:00:40.620><c> submarine</c><00:00:41.070><c> so</c><00:00:42.030><c> let's</c><00:00:42.210><c> jump</c>

00:00:42.349 --> 00:00:42.359 align:start position:0%
work with Lib submarine so let's jump
 

00:00:42.359 --> 00:00:45.139 align:start position:0%
work with Lib submarine so let's jump
into<00:00:42.480><c> it</c><00:00:43.010><c> quick</c><00:00:44.010><c> overview</c><00:00:44.550><c> I'm</c><00:00:44.760><c> not</c><00:00:44.909><c> going</c><00:00:45.089><c> to</c>

00:00:45.139 --> 00:00:45.149 align:start position:0%
into it quick overview I'm not going to
 

00:00:45.149 --> 00:00:48.229 align:start position:0%
into it quick overview I'm not going to
go<00:00:45.239><c> into</c><00:00:45.420><c> detail</c><00:00:45.749><c> about</c><00:00:45.780><c> this</c><00:00:46.879><c> Lib</c><00:00:47.879><c> submarine</c>

00:00:48.229 --> 00:00:48.239 align:start position:0%
go into detail about this Lib submarine
 

00:00:48.239 --> 00:00:49.700 align:start position:0%
go into detail about this Lib submarine
is<00:00:48.390><c> the</c><00:00:48.510><c> right</c><00:00:48.659><c> solution</c><00:00:49.170><c> to</c><00:00:49.319><c> prevent</c>

00:00:49.700 --> 00:00:49.710 align:start position:0%
is the right solution to prevent
 

00:00:49.710 --> 00:00:52.040 align:start position:0%
is the right solution to prevent
reordering<00:00:50.339><c> attacks</c><00:00:50.670><c> and</c><00:00:50.969><c> also</c><00:00:51.420><c> to</c><00:00:51.479><c> increase</c>

00:00:52.040 --> 00:00:52.050 align:start position:0%
reordering attacks and also to increase
 

00:00:52.050 --> 00:00:54.349 align:start position:0%
reordering attacks and also to increase
the<00:00:52.499><c> level</c><00:00:52.739><c> of</c><00:00:52.859><c> privacy</c><00:00:53.129><c> in</c><00:00:53.640><c> a</c><00:00:53.789><c> commit</c><00:00:54.089><c> reveal</c>

00:00:54.349 --> 00:00:54.359 align:start position:0%
the level of privacy in a commit reveal
 

00:00:54.359 --> 00:00:56.840 align:start position:0%
the level of privacy in a commit reveal
scheme<00:00:54.719><c> and</c><00:00:54.929><c> really</c><00:00:55.710><c> eliminate</c><00:00:56.280><c> the</c><00:00:56.460><c> signal</c>

00:00:56.840 --> 00:00:56.850 align:start position:0%
scheme and really eliminate the signal
 

00:00:56.850 --> 00:00:58.849 align:start position:0%
scheme and really eliminate the signal
that<00:00:57.059><c> the</c><00:00:57.179><c> commit</c><00:00:57.479><c> is</c><00:00:57.510><c> gonna</c><00:00:57.780><c> provide</c><00:00:58.109><c> so</c><00:00:58.769><c> on</c>

00:00:58.849 --> 00:00:58.859 align:start position:0%
that the commit is gonna provide so on
 

00:00:58.859 --> 00:01:00.529 align:start position:0%
that the commit is gonna provide so on
the<00:00:58.979><c> on</c><00:00:59.309><c> the</c><00:00:59.519><c> left</c><00:00:59.729><c> side</c><00:00:59.909><c> of</c><00:01:00.030><c> the</c><00:01:00.089><c> screen</c><00:01:00.239><c> here</c>

00:01:00.529 --> 00:01:00.539 align:start position:0%
the on the left side of the screen here
 

00:01:00.539 --> 00:01:01.549 align:start position:0%
the on the left side of the screen here
you<00:01:00.629><c> can</c><00:01:00.749><c> see</c><00:01:00.899><c> kind</c><00:01:01.019><c> of</c><00:01:01.109><c> what</c><00:01:01.260><c> a</c><00:01:01.289><c> regular</c>

00:01:01.549 --> 00:01:01.559 align:start position:0%
you can see kind of what a regular
 

00:01:01.559 --> 00:01:03.229 align:start position:0%
you can see kind of what a regular
commit<00:01:02.010><c> reveal</c><00:01:02.249><c> scheme</c><00:01:02.550><c> will</c><00:01:02.670><c> be</c><00:01:02.819><c> which</c><00:01:03.030><c> is</c>

00:01:03.229 --> 00:01:03.239 align:start position:0%
commit reveal scheme will be which is
 

00:01:03.239 --> 00:01:05.539 align:start position:0%
commit reveal scheme will be which is
you<00:01:03.719><c> have</c><00:01:03.749><c> the</c><00:01:04.019><c> commits</c><00:01:04.379><c> that</c><00:01:04.589><c> hashes</c><00:01:05.430><c> the</c>

00:01:05.539 --> 00:01:05.549 align:start position:0%
you have the commits that hashes the
 

00:01:05.549 --> 00:01:06.770 align:start position:0%
you have the commits that hashes the
data<00:01:05.759><c> but</c><00:01:06.090><c> you</c><00:01:06.149><c> still</c><00:01:06.360><c> have</c><00:01:06.479><c> see</c><00:01:06.659><c> the</c>

00:01:06.770 --> 00:01:06.780 align:start position:0%
data but you still have see the
 

00:01:06.780 --> 00:01:08.899 align:start position:0%
data but you still have see the
participation<00:01:07.409><c> as</c><00:01:07.770><c> well</c><00:01:08.130><c> as</c><00:01:08.340><c> the</c><00:01:08.610><c> value</c>

00:01:08.899 --> 00:01:08.909 align:start position:0%
participation as well as the value
 

00:01:08.909 --> 00:01:12.499 align:start position:0%
participation as well as the value
that's<00:01:09.090><c> being</c><00:01:09.210><c> committed</c><00:01:10.640><c> then</c><00:01:11.640><c> during</c><00:01:12.420><c> the</c>

00:01:12.499 --> 00:01:12.509 align:start position:0%
that's being committed then during the
 

00:01:12.509 --> 00:01:13.910 align:start position:0%
that's being committed then during the
reveal<00:01:12.780><c> stage</c><00:01:12.930><c> you</c><00:01:13.200><c> reveal</c><00:01:13.530><c> what</c><00:01:13.649><c> the</c><00:01:13.740><c> data</c>

00:01:13.910 --> 00:01:13.920 align:start position:0%
reveal stage you reveal what the data
 

00:01:13.920 --> 00:01:15.920 align:start position:0%
reveal stage you reveal what the data
can<00:01:14.100><c> contains</c><00:01:14.850><c> and</c><00:01:15.119><c> maybe</c><00:01:15.570><c> this</c><00:01:15.719><c> is</c><00:01:15.810><c> like</c><00:01:15.869><c> a</c>

00:01:15.920 --> 00:01:15.930 align:start position:0%
can contains and maybe this is like a
 

00:01:15.930 --> 00:01:18.440 align:start position:0%
can contains and maybe this is like a
voting<00:01:16.289><c> mechanism</c><00:01:16.439><c> right</c><00:01:16.950><c> on</c><00:01:17.369><c> the</c><00:01:18.119><c> right</c><00:01:18.270><c> side</c>

00:01:18.440 --> 00:01:18.450 align:start position:0%
voting mechanism right on the right side
 

00:01:18.450 --> 00:01:20.149 align:start position:0%
voting mechanism right on the right side
of<00:01:18.539><c> the</c><00:01:18.630><c> screen</c><00:01:18.869><c> you</c><00:01:19.259><c> actually</c><00:01:19.590><c> see</c><00:01:19.799><c> what</c><00:01:20.100><c> it</c>

00:01:20.149 --> 00:01:20.159 align:start position:0%
of the screen you actually see what it
 

00:01:20.159 --> 00:01:21.370 align:start position:0%
of the screen you actually see what it
would<00:01:20.219><c> look</c><00:01:20.280><c> like</c><00:01:20.430><c> from</c><00:01:20.670><c> a</c><00:01:20.789><c> submarine</c>

00:01:21.370 --> 00:01:21.380 align:start position:0%
would look like from a submarine
 

00:01:21.380 --> 00:01:23.569 align:start position:0%
would look like from a submarine
perspective<00:01:22.380><c> which</c><00:01:22.530><c> is</c><00:01:22.710><c> the</c><00:01:22.920><c> entire</c><00:01:23.189><c> commit</c>

00:01:23.569 --> 00:01:23.579 align:start position:0%
perspective which is the entire commit
 

00:01:23.579 --> 00:01:25.819 align:start position:0%
perspective which is the entire commit
period<00:01:23.969><c> is</c><00:01:24.090><c> completely</c><00:01:24.479><c> hidden</c><00:01:24.630><c> its</c><00:01:25.200><c> mask</c><00:01:25.560><c> you</c>

00:01:25.819 --> 00:01:25.829 align:start position:0%
period is completely hidden its mask you
 

00:01:25.829 --> 00:01:27.440 align:start position:0%
period is completely hidden its mask you
don't<00:01:26.009><c> see</c><00:01:26.280><c> who's</c><00:01:26.520><c> participating</c><00:01:27.210><c> you</c><00:01:27.299><c> don't</c>

00:01:27.440 --> 00:01:27.450 align:start position:0%
don't see who's participating you don't
 

00:01:27.450 --> 00:01:28.819 align:start position:0%
don't see who's participating you don't
see<00:01:27.570><c> the</c><00:01:27.689><c> value</c><00:01:27.780><c> that's</c><00:01:28.079><c> being</c><00:01:28.229><c> committed</c><00:01:28.530><c> and</c>

00:01:28.819 --> 00:01:28.829 align:start position:0%
see the value that's being committed and
 

00:01:28.829 --> 00:01:30.620 align:start position:0%
see the value that's being committed and
of<00:01:29.369><c> course</c><00:01:29.670><c> you</c><00:01:29.789><c> don't</c><00:01:29.939><c> see</c><00:01:30.060><c> the</c><00:01:30.180><c> data</c><00:01:30.359><c> that's</c>

00:01:30.620 --> 00:01:30.630 align:start position:0%
of course you don't see the data that's
 

00:01:30.630 --> 00:01:32.840 align:start position:0%
of course you don't see the data that's
being<00:01:30.780><c> committed</c><00:01:31.079><c> but</c><00:01:32.039><c> again</c><00:01:32.369><c> everything</c><00:01:32.700><c> is</c>

00:01:32.840 --> 00:01:32.850 align:start position:0%
being committed but again everything is
 

00:01:32.850 --> 00:01:36.499 align:start position:0%
being committed but again everything is
revealed<00:01:33.090><c> at</c><00:01:34.020><c> the</c><00:01:34.140><c> end</c><00:01:34.259><c> of</c><00:01:34.320><c> the</c><00:01:34.380><c> day</c><00:01:34.520><c> so</c><00:01:35.520><c> how</c><00:01:36.450><c> do</c>

00:01:36.499 --> 00:01:36.509 align:start position:0%
revealed at the end of the day so how do
 

00:01:36.509 --> 00:01:38.779 align:start position:0%
revealed at the end of the day so how do
you<00:01:36.689><c> actually</c><00:01:36.840><c> implement</c><00:01:37.530><c> it</c><00:01:37.680><c> here</c><00:01:38.310><c> on</c><00:01:38.579><c> the</c>

00:01:38.779 --> 00:01:38.789 align:start position:0%
you actually implement it here on the
 

00:01:38.789 --> 00:01:41.539 align:start position:0%
you actually implement it here on the
left<00:01:39.000><c> side</c><00:01:39.180><c> of</c><00:01:39.570><c> the</c><00:01:39.780><c> screen</c><00:01:40.049><c> we</c><00:01:40.380><c> have</c><00:01:40.409><c> a</c><00:01:41.070><c> very</c>

00:01:41.539 --> 00:01:41.549 align:start position:0%
left side of the screen we have a very
 

00:01:41.549 --> 00:01:43.190 align:start position:0%
left side of the screen we have a very
simple<00:01:41.939><c> auction</c><00:01:42.390><c> contract</c><00:01:42.960><c> that's</c>

00:01:43.190 --> 00:01:43.200 align:start position:0%
simple auction contract that's
 

00:01:43.200 --> 00:01:46.039 align:start position:0%
simple auction contract that's
implemented<00:01:43.829><c> as</c><00:01:44.009><c> an</c><00:01:44.219><c> ER</c><00:01:44.490><c> C</c><00:01:44.729><c> 721</c><00:01:45.509><c> token</c>

00:01:46.039 --> 00:01:46.049 align:start position:0%
implemented as an ER C 721 token
 

00:01:46.049 --> 00:01:49.310 align:start position:0%
implemented as an ER C 721 token
receiver<00:01:46.439><c> hook</c><00:01:47.240><c> we</c><00:01:48.240><c> took</c><00:01:48.450><c> out</c><00:01:48.600><c> a</c><00:01:48.630><c> lot</c><00:01:48.960><c> of</c><00:01:49.109><c> kind</c>

00:01:49.310 --> 00:01:49.320 align:start position:0%
receiver hook we took out a lot of kind
 

00:01:49.320 --> 00:01:52.279 align:start position:0%
receiver hook we took out a lot of kind
of<00:01:49.350><c> the</c><00:01:49.469><c> basic</c><00:01:50.039><c> storage</c><00:01:51.000><c> and</c><00:01:51.329><c> like</c><00:01:51.479><c> function</c>

00:01:52.279 --> 00:01:52.289 align:start position:0%
of the basic storage and like function
 

00:01:52.289 --> 00:01:53.690 align:start position:0%
of the basic storage and like function
setup<00:01:52.619><c> functions</c><00:01:52.979><c> are</c><00:01:53.100><c> required</c><00:01:53.429><c> for</c><00:01:53.609><c> the</c>

00:01:53.690 --> 00:01:53.700 align:start position:0%
setup functions are required for the
 

00:01:53.700 --> 00:01:55.910 align:start position:0%
setup functions are required for the
auction<00:01:53.820><c> and</c><00:01:54.210><c> only</c><00:01:54.539><c> left</c><00:01:54.810><c> this</c><00:01:55.109><c> bid</c><00:01:55.439><c> function</c>

00:01:55.910 --> 00:01:55.920 align:start position:0%
auction and only left this bid function
 

00:01:55.920 --> 00:01:57.499 align:start position:0%
auction and only left this bid function
which<00:01:56.520><c> is</c><00:01:56.670><c> the</c><00:01:56.789><c> one</c><00:01:56.969><c> that</c><00:01:57.119><c> people</c><00:01:57.270><c> would</c>

00:01:57.499 --> 00:01:57.509 align:start position:0%
which is the one that people would
 

00:01:57.509 --> 00:01:59.419 align:start position:0%
which is the one that people would
monitor<00:01:57.960><c> to</c><00:01:58.170><c> get</c><00:01:58.259><c> an</c><00:01:58.409><c> idea</c><00:01:58.740><c> of</c><00:01:58.799><c> what</c><00:01:59.280><c> the</c>

00:01:59.419 --> 00:01:59.429 align:start position:0%
monitor to get an idea of what the
 

00:01:59.429 --> 00:02:03.380 align:start position:0%
monitor to get an idea of what the
active<00:01:59.880><c> bids</c><00:02:00.179><c> are</c><00:02:00.450><c> on</c><00:02:00.689><c> this</c><00:02:00.810><c> auction</c><00:02:01.490><c> so</c><00:02:02.490><c> what</c>

00:02:03.380 --> 00:02:03.390 align:start position:0%
active bids are on this auction so what
 

00:02:03.390 --> 00:02:04.789 align:start position:0%
active bids are on this auction so what
someone<00:02:04.079><c> that's</c><00:02:04.200><c> monitoring</c><00:02:04.530><c> the</c><00:02:04.619><c> chain</c>

00:02:04.789 --> 00:02:04.799 align:start position:0%
someone that's monitoring the chain
 

00:02:04.799 --> 00:02:07.249 align:start position:0%
someone that's monitoring the chain
would<00:02:04.920><c> see</c><00:02:05.070><c> is</c><00:02:05.310><c> that</c><00:02:05.549><c> when</c><00:02:06.119><c> someone</c><00:02:06.689><c> commits</c><00:02:07.109><c> a</c>

00:02:07.249 --> 00:02:07.259 align:start position:0%
would see is that when someone commits a
 

00:02:07.259 --> 00:02:09.330 align:start position:0%
would see is that when someone commits a
new<00:02:07.499><c> bid</c><00:02:07.740><c> to</c><00:02:07.950><c> the</c><00:02:07.979><c> to</c><00:02:08.519><c> the</c>

00:02:09.330 --> 00:02:09.340 align:start position:0%
new bid to the to the
 

00:02:09.340 --> 00:02:10.830 align:start position:0%
new bid to the to the
so<00:02:09.550><c> the</c><00:02:09.640><c> mempool</c><00:02:09.940><c> they</c><00:02:10.209><c> could</c><00:02:10.360><c> see</c><00:02:10.569><c> it</c><00:02:10.660><c> and</c>

00:02:10.830 --> 00:02:10.840 align:start position:0%
so the mempool they could see it and
 

00:02:10.840 --> 00:02:12.990 align:start position:0%
so the mempool they could see it and
then<00:02:10.959><c> make</c><00:02:11.170><c> sure</c><00:02:11.200><c> they</c><00:02:11.500><c> place</c><00:02:11.920><c> a</c><00:02:12.190><c> transaction</c>

00:02:12.990 --> 00:02:13.000 align:start position:0%
then make sure they place a transaction
 

00:02:13.000 --> 00:02:14.820 align:start position:0%
then make sure they place a transaction
right<00:02:13.180><c> after</c><00:02:13.510><c> that</c><00:02:13.720><c> kind</c><00:02:13.870><c> of</c><00:02:13.990><c> beats</c><00:02:14.440><c> the</c><00:02:14.680><c> bit</c>

00:02:14.820 --> 00:02:14.830 align:start position:0%
right after that kind of beats the bit
 

00:02:14.830 --> 00:02:17.070 align:start position:0%
right after that kind of beats the bit
and<00:02:15.040><c> make</c><00:02:15.400><c> sure</c><00:02:15.430><c> that</c><00:02:15.640><c> they're</c><00:02:15.819><c> on</c><00:02:15.850><c> top</c><00:02:16.090><c> of</c><00:02:16.120><c> the</c>

00:02:17.070 --> 00:02:17.080 align:start position:0%
and make sure that they're on top of the
 

00:02:17.080 --> 00:02:19.140 align:start position:0%
and make sure that they're on top of the
auction<00:02:17.470><c> so</c><00:02:18.400><c> what</c><00:02:18.550><c> you</c><00:02:18.610><c> want</c><00:02:18.760><c> to</c><00:02:18.819><c> do</c><00:02:18.910><c> is</c><00:02:19.000><c> be</c>

00:02:19.140 --> 00:02:19.150 align:start position:0%
auction so what you want to do is be
 

00:02:19.150 --> 00:02:21.750 align:start position:0%
auction so what you want to do is be
able<00:02:19.420><c> to</c><00:02:19.600><c> mask</c><00:02:19.870><c> the</c><00:02:20.200><c> value</c><00:02:20.680><c> and</c><00:02:20.920><c> and</c><00:02:21.250><c> really</c>

00:02:21.750 --> 00:02:21.760 align:start position:0%
able to mask the value and and really
 

00:02:21.760 --> 00:02:23.280 align:start position:0%
able to mask the value and and really
the<00:02:21.819><c> participation</c><00:02:22.360><c> inside</c><00:02:22.900><c> of</c><00:02:22.990><c> this</c><00:02:23.050><c> bidding</c>

00:02:23.280 --> 00:02:23.290 align:start position:0%
the participation inside of this bidding
 

00:02:23.290 --> 00:02:25.470 align:start position:0%
the participation inside of this bidding
and<00:02:23.590><c> create</c><00:02:24.280><c> what</c><00:02:24.520><c> is</c><00:02:24.550><c> called</c><00:02:24.819><c> a</c><00:02:25.000><c> sealed</c><00:02:25.270><c> bid</c>

00:02:25.470 --> 00:02:25.480 align:start position:0%
and create what is called a sealed bid
 

00:02:25.480 --> 00:02:28.800 align:start position:0%
and create what is called a sealed bid
auction<00:02:25.930><c> so</c><00:02:26.560><c> this</c><00:02:27.040><c> can</c><00:02:27.220><c> be</c><00:02:27.340><c> done</c><00:02:27.520><c> the</c><00:02:28.510><c> only</c>

00:02:28.800 --> 00:02:28.810 align:start position:0%
auction so this can be done the only
 

00:02:28.810 --> 00:02:29.970 align:start position:0%
auction so this can be done the only
function<00:02:29.170><c> that</c><00:02:29.200><c> you</c><00:02:29.350><c> end</c><00:02:29.470><c> up</c><00:02:29.590><c> needing</c><00:02:29.739><c> to</c>

00:02:29.970 --> 00:02:29.980 align:start position:0%
function that you end up needing to
 

00:02:29.980 --> 00:02:31.470 align:start position:0%
function that you end up needing to
change<00:02:30.250><c> is</c><00:02:30.459><c> this</c><00:02:30.580><c> bid</c><00:02:30.790><c> function</c><00:02:31.180><c> so</c><00:02:31.420><c> you</c>

00:02:31.470 --> 00:02:31.480 align:start position:0%
change is this bid function so you
 

00:02:31.480 --> 00:02:33.059 align:start position:0%
change is this bid function so you
actually<00:02:31.660><c> implement</c><00:02:32.200><c> it</c><00:02:32.319><c> as</c><00:02:32.440><c> an</c><00:02:32.620><c> event</c>

00:02:33.059 --> 00:02:33.069 align:start position:0%
actually implement it as an event
 

00:02:33.069 --> 00:02:35.699 align:start position:0%
actually implement it as an event
receiver<00:02:33.880><c> hook</c><00:02:34.150><c> based</c><00:02:34.750><c> off</c><00:02:34.989><c> of</c><00:02:35.020><c> this</c><00:02:35.380><c> lib</c>

00:02:35.699 --> 00:02:35.709 align:start position:0%
receiver hook based off of this lib
 

00:02:35.709 --> 00:02:37.440 align:start position:0%
receiver hook based off of this lib
Submarine<00:02:36.250><c> contract</c><00:02:36.819><c> that</c><00:02:36.940><c> you</c><00:02:37.030><c> inherit</c><00:02:37.420><c> from</c>

00:02:37.440 --> 00:02:37.450 align:start position:0%
Submarine contract that you inherit from
 

00:02:37.450 --> 00:02:39.180 align:start position:0%
Submarine contract that you inherit from
so<00:02:38.050><c> you</c><00:02:38.110><c> can</c><00:02:38.230><c> see</c><00:02:38.350><c> at</c><00:02:38.440><c> the</c><00:02:38.530><c> top</c><00:02:38.709><c> you</c><00:02:38.830><c> inherit</c>

00:02:39.180 --> 00:02:39.190 align:start position:0%
so you can see at the top you inherit
 

00:02:39.190 --> 00:02:42.240 align:start position:0%
so you can see at the top you inherit
the<00:02:39.340><c> the</c><00:02:39.760><c> the</c><00:02:40.090><c> new</c><00:02:40.270><c> contract</c><00:02:40.810><c> and</c><00:02:41.590><c> then</c><00:02:41.860><c> you</c>

00:02:42.240 --> 00:02:42.250 align:start position:0%
the the the new contract and then you
 

00:02:42.250 --> 00:02:44.220 align:start position:0%
the the the new contract and then you
implement<00:02:42.730><c> this</c><00:02:42.880><c> function</c><00:02:43.269><c> called</c><00:02:43.540><c> on</c><00:02:43.720><c> lips</c>

00:02:44.220 --> 00:02:44.230 align:start position:0%
implement this function called on lips
 

00:02:44.230 --> 00:02:46.380 align:start position:0%
implement this function called on lips
on<00:02:44.500><c> submarine</c><00:02:45.040><c> reveal</c><00:02:45.400><c> with</c><00:02:45.970><c> these</c><00:02:46.150><c> data</c>

00:02:46.380 --> 00:02:46.390 align:start position:0%
on submarine reveal with these data
 

00:02:46.390 --> 00:02:48.449 align:start position:0%
on submarine reveal with these data
parameters<00:02:46.989><c> so</c><00:02:47.230><c> the</c><00:02:47.320><c> submarine</c><00:02:47.739><c> ID</c><00:02:47.920><c> is</c><00:02:48.250><c> what</c>

00:02:48.449 --> 00:02:48.459 align:start position:0%
parameters so the submarine ID is what
 

00:02:48.459 --> 00:02:50.670 align:start position:0%
parameters so the submarine ID is what
kind<00:02:48.640><c> of</c><00:02:48.670><c> identifies</c><00:02:49.269><c> the</c><00:02:49.540><c> bed</c><00:02:49.720><c> and</c><00:02:50.440><c> then</c><00:02:50.590><c> you</c>

00:02:50.670 --> 00:02:50.680 align:start position:0%
kind of identifies the bed and then you
 

00:02:50.680 --> 00:02:52.440 align:start position:0%
kind of identifies the bed and then you
have<00:02:50.769><c> the</c><00:02:50.890><c> embedded</c><00:02:51.340><c> data</c><00:02:51.489><c> which</c><00:02:51.850><c> is</c><00:02:52.030><c> that</c>

00:02:52.440 --> 00:02:52.450 align:start position:0%
have the embedded data which is that
 

00:02:52.450 --> 00:02:54.059 align:start position:0%
have the embedded data which is that
data<00:02:52.690><c> that</c><00:02:52.930><c> was</c><00:02:53.140><c> previously</c><00:02:53.620><c> hashed</c><00:02:53.860><c> in</c><00:02:54.010><c> a</c>

00:02:54.059 --> 00:02:54.069 align:start position:0%
data that was previously hashed in a
 

00:02:54.069 --> 00:02:55.740 align:start position:0%
data that was previously hashed in a
commit<00:02:54.280><c> reveal</c><00:02:54.489><c> scheme</c><00:02:54.760><c> in</c><00:02:54.970><c> this</c><00:02:55.209><c> scheme</c><00:02:55.450><c> you</c>

00:02:55.740 --> 00:02:55.750 align:start position:0%
commit reveal scheme in this scheme you
 

00:02:55.750 --> 00:02:57.750 align:start position:0%
commit reveal scheme in this scheme you
have<00:02:56.410><c> it</c><00:02:56.590><c> through</c><00:02:56.860><c> this</c><00:02:56.980><c> function</c><00:02:57.370><c> and</c><00:02:57.580><c> as</c>

00:02:57.750 --> 00:02:57.760 align:start position:0%
have it through this function and as
 

00:02:57.760 --> 00:02:59.790 align:start position:0%
have it through this function and as
well<00:02:57.910><c> as</c><00:02:58.000><c> the</c><00:02:58.090><c> value</c><00:02:58.480><c> then</c><00:02:58.930><c> the</c><00:02:59.110><c> logic</c><00:02:59.530><c> of</c><00:02:59.680><c> your</c>

00:02:59.790 --> 00:02:59.800 align:start position:0%
well as the value then the logic of your
 

00:02:59.800 --> 00:03:01.140 align:start position:0%
well as the value then the logic of your
function<00:03:00.130><c> actually</c><00:03:00.459><c> kind</c><00:03:00.640><c> of</c><00:03:00.670><c> remains</c><00:03:00.970><c> the</c>

00:03:01.140 --> 00:03:01.150 align:start position:0%
function actually kind of remains the
 

00:03:01.150 --> 00:03:02.699 align:start position:0%
function actually kind of remains the
same<00:03:01.360><c> you</c><00:03:01.630><c> still</c><00:03:01.690><c> have</c><00:03:02.080><c> the</c><00:03:02.200><c> same</c><00:03:02.350><c> logical</c>

00:03:02.699 --> 00:03:02.709 align:start position:0%
same you still have the same logical
 

00:03:02.709 --> 00:03:05.880 align:start position:0%
same you still have the same logical
checks<00:03:03.010><c> the</c><00:03:03.430><c> same</c><00:03:03.700><c> storage</c><00:03:04.090><c> changes</c><00:03:04.660><c> and</c><00:03:04.930><c> the</c>

00:03:05.880 --> 00:03:05.890 align:start position:0%
checks the same storage changes and the
 

00:03:05.890 --> 00:03:07.559 align:start position:0%
checks the same storage changes and the
new<00:03:06.040><c> logic</c><00:03:06.430><c> for</c><00:03:06.610><c> calculating</c><00:03:07.030><c> who</c><00:03:07.360><c> is</c><00:03:07.420><c> the</c>

00:03:07.559 --> 00:03:07.569 align:start position:0%
new logic for calculating who is the
 

00:03:07.569 --> 00:03:10.680 align:start position:0%
new logic for calculating who is the
winner<00:03:07.769><c> so</c><00:03:08.769><c> this</c><00:03:09.100><c> and</c><00:03:09.430><c> would</c><00:03:10.180><c> actually</c><00:03:10.330><c> happen</c>

00:03:10.680 --> 00:03:10.690 align:start position:0%
winner so this and would actually happen
 

00:03:10.690 --> 00:03:12.360 align:start position:0%
winner so this and would actually happen
on<00:03:11.050><c> the</c><00:03:11.170><c> reveal</c><00:03:11.530><c> stage</c><00:03:11.709><c> of</c><00:03:12.010><c> your</c><00:03:12.100><c> commit</c>

00:03:12.360 --> 00:03:12.370 align:start position:0%
on the reveal stage of your commit
 

00:03:12.370 --> 00:03:14.009 align:start position:0%
on the reveal stage of your commit
reveal<00:03:12.640><c> so</c><00:03:13.150><c> you</c><00:03:13.209><c> make</c><00:03:13.420><c> sure</c><00:03:13.600><c> that</c><00:03:13.750><c> you're</c><00:03:13.930><c> not</c>

00:03:14.009 --> 00:03:14.019 align:start position:0%
reveal so you make sure that you're not
 

00:03:14.019 --> 00:03:16.259 align:start position:0%
reveal so you make sure that you're not
liable<00:03:14.350><c> to</c><00:03:14.640><c> someone</c><00:03:15.640><c> that's</c><00:03:15.790><c> watching</c><00:03:15.940><c> all</c>

00:03:16.259 --> 00:03:16.269 align:start position:0%
liable to someone that's watching all
 

00:03:16.269 --> 00:03:19.890 align:start position:0%
liable to someone that's watching all
the<00:03:16.360><c> commits</c><00:03:16.660><c> unable</c><00:03:16.930><c> to</c><00:03:17.110><c> to</c><00:03:18.660><c> make</c><00:03:19.660><c> beds</c>

00:03:19.890 --> 00:03:19.900 align:start position:0%
the commits unable to to make beds
 

00:03:19.900 --> 00:03:22.850 align:start position:0%
the commits unable to to make beds
accordingly<00:03:20.700><c> so</c><00:03:21.700><c> from</c><00:03:22.120><c> the</c><00:03:22.239><c> user</c><00:03:22.450><c> perspective</c>

00:03:22.850 --> 00:03:22.860 align:start position:0%
accordingly so from the user perspective
 

00:03:22.860 --> 00:03:25.800 align:start position:0%
accordingly so from the user perspective
if<00:03:23.860><c> you're</c><00:03:24.220><c> just</c><00:03:24.400><c> modifying</c><00:03:24.910><c> a</c><00:03:25.269><c> traditional</c>

00:03:25.800 --> 00:03:25.810 align:start position:0%
if you're just modifying a traditional
 

00:03:25.810 --> 00:03:27.360 align:start position:0%
if you're just modifying a traditional
commit<00:03:26.110><c> reveal</c><00:03:26.380><c> scheme</c><00:03:26.709><c> it</c><00:03:26.920><c> actually</c><00:03:27.220><c> doesn't</c>

00:03:27.360 --> 00:03:27.370 align:start position:0%
commit reveal scheme it actually doesn't
 

00:03:27.370 --> 00:03:28.860 align:start position:0%
commit reveal scheme it actually doesn't
look<00:03:27.579><c> very</c><00:03:27.610><c> much</c><00:03:27.880><c> different</c><00:03:28.450><c> from</c><00:03:28.540><c> a</c><00:03:28.660><c> user</c>

00:03:28.860 --> 00:03:28.870 align:start position:0%
look very much different from a user
 

00:03:28.870 --> 00:03:31.530 align:start position:0%
look very much different from a user
perspective<00:03:29.110><c> it</c><00:03:29.590><c> still</c><00:03:30.130><c> needs</c><00:03:30.370><c> to</c><00:03:30.610><c> do</c><00:03:30.850><c> to</c><00:03:31.239><c> sign</c>

00:03:31.530 --> 00:03:31.540 align:start position:0%
perspective it still needs to do to sign
 

00:03:31.540 --> 00:03:33.600 align:start position:0%
perspective it still needs to do to sign
transaction<00:03:32.320><c> from</c><00:03:32.470><c> the</c><00:03:32.560><c> user</c><00:03:32.860><c> and</c><00:03:33.130><c> then</c><00:03:33.190><c> you</c>

00:03:33.600 --> 00:03:33.610 align:start position:0%
transaction from the user and then you
 

00:03:33.610 --> 00:03:35.190 align:start position:0%
transaction from the user and then you
have<00:03:33.730><c> this</c><00:03:33.850><c> third</c><00:03:34.150><c> transaction</c><00:03:34.630><c> which</c><00:03:34.959><c> is</c><00:03:35.079><c> the</c>

00:03:35.190 --> 00:03:35.200 align:start position:0%
have this third transaction which is the
 

00:03:35.200 --> 00:03:39.030 align:start position:0%
have this third transaction which is the
unlock<00:03:35.500><c> transaction</c><00:03:36.160><c> which</c><00:03:36.670><c> is</c><00:03:37.859><c> generated</c><00:03:38.859><c> as</c>

00:03:39.030 --> 00:03:39.040 align:start position:0%
unlock transaction which is generated as
 

00:03:39.040 --> 00:03:41.610 align:start position:0%
unlock transaction which is generated as
kind<00:03:39.549><c> of</c><00:03:39.609><c> a</c><00:03:39.730><c> raw</c><00:03:40.060><c> sign</c><00:03:40.600><c> transaction</c><00:03:41.380><c> and</c><00:03:41.590><c> can</c>

00:03:41.610 --> 00:03:41.620 align:start position:0%
kind of a raw sign transaction and can
 

00:03:41.620 --> 00:03:43.380 align:start position:0%
kind of a raw sign transaction and can
be<00:03:41.890><c> relayed</c><00:03:42.220><c> by</c><00:03:42.430><c> anyone</c><00:03:43.180><c> that's</c>

00:03:43.380 --> 00:03:43.390 align:start position:0%
be relayed by anyone that's
 

00:03:43.390 --> 00:03:47.670 align:start position:0%
be relayed by anyone that's
communicating<00:03:43.989><c> with</c><00:03:44.109><c> the</c><00:03:44.200><c> chain</c><00:03:46.109><c> so</c><00:03:47.109><c> from</c><00:03:47.590><c> a</c>

00:03:47.670 --> 00:03:47.680 align:start position:0%
communicating with the chain so from a
 

00:03:47.680 --> 00:03:49.050 align:start position:0%
communicating with the chain so from a
client<00:03:48.010><c> perspective</c><00:03:48.100><c> then</c><00:03:48.700><c> what</c><00:03:48.850><c> you</c><00:03:48.910><c> have</c><00:03:48.940><c> to</c>

00:03:49.050 --> 00:03:49.060 align:start position:0%
client perspective then what you have to
 

00:03:49.060 --> 00:03:52.140 align:start position:0%
client perspective then what you have to
do<00:03:49.269><c> is</c><00:03:49.540><c> you</c><00:03:49.870><c> have</c><00:03:50.019><c> to</c><00:03:50.049><c> also</c><00:03:50.620><c> have</c><00:03:51.040><c> your</c><00:03:51.519><c> commit</c>

00:03:52.140 --> 00:03:52.150 align:start position:0%
do is you have to also have your commit
 

00:03:52.150 --> 00:03:55.890 align:start position:0%
do is you have to also have your commit
that<00:03:52.390><c> gets</c><00:03:52.660><c> generated</c><00:03:53.019><c> on</c><00:03:53.620><c> the</c><00:03:54.130><c> off</c><00:03:54.640><c> chain</c><00:03:55.030><c> and</c>

00:03:55.890 --> 00:03:55.900 align:start position:0%
that gets generated on the off chain and
 

00:03:55.900 --> 00:03:57.720 align:start position:0%
that gets generated on the off chain and
then<00:03:56.140><c> also</c><00:03:56.320><c> you</c><00:03:56.500><c> have</c><00:03:56.590><c> to</c><00:03:56.799><c> generate</c><00:03:57.220><c> a</c><00:03:57.250><c> miracle</c>

00:03:57.720 --> 00:03:57.730 align:start position:0%
then also you have to generate a miracle
 

00:03:57.730 --> 00:03:59.819 align:start position:0%
then also you have to generate a miracle
patrícia<00:03:58.060><c> proof</c><00:03:58.359><c> of</c><00:03:58.600><c> that</c><00:03:58.870><c> commit</c><00:03:59.230><c> off</c><00:03:59.410><c> chain</c>

00:03:59.819 --> 00:03:59.829 align:start position:0%
patrícia proof of that commit off chain
 

00:03:59.829 --> 00:04:02.160 align:start position:0%
patrícia proof of that commit off chain
and<00:04:00.489><c> we've</c><00:04:00.730><c> added</c><00:04:00.970><c> some</c><00:04:01.420><c> Python</c><00:04:01.810><c> scripts</c>

00:04:02.160 --> 00:04:02.170 align:start position:0%
and we've added some Python scripts
 

00:04:02.170 --> 00:04:03.720 align:start position:0%
and we've added some Python scripts
inside<00:04:02.350><c> of</c><00:04:02.590><c> our</c><00:04:02.709><c> repository</c><00:04:03.280><c> that</c><00:04:03.370><c> actually</c>

00:04:03.720 --> 00:04:03.730 align:start position:0%
inside of our repository that actually
 

00:04:03.730 --> 00:04:07.259 align:start position:0%
inside of our repository that actually
does<00:04:03.910><c> this</c><00:04:04.060><c> for</c><00:04:04.390><c> you</c><00:04:04.510><c> and</c><00:04:05.380><c> then</c><00:04:06.220><c> on</c><00:04:06.519><c> chain</c><00:04:07.000><c> we</c>

00:04:07.259 --> 00:04:07.269 align:start position:0%
does this for you and then on chain we
 

00:04:07.269 --> 00:04:08.970 align:start position:0%
does this for you and then on chain we
have<00:04:07.390><c> implemented</c><00:04:07.870><c> all</c><00:04:08.200><c> the</c><00:04:08.290><c> smart</c><00:04:08.530><c> contracts</c>

00:04:08.970 --> 00:04:08.980 align:start position:0%
have implemented all the smart contracts
 

00:04:08.980 --> 00:04:11.699 align:start position:0%
have implemented all the smart contracts
that<00:04:09.250><c> actually</c><00:04:09.730><c> executes</c><00:04:10.030><c> this</c><00:04:10.709><c> Submarine</c>

00:04:11.699 --> 00:04:11.709 align:start position:0%
that actually executes this Submarine
 

00:04:11.709 --> 00:04:14.190 align:start position:0%
that actually executes this Submarine
commit<00:04:12.070><c> and</c><00:04:12.220><c> then</c><00:04:12.370><c> also</c><00:04:12.840><c> verify</c><00:04:13.840><c> that</c><00:04:14.049><c> the</c>

00:04:14.190 --> 00:04:14.200 align:start position:0%
commit and then also verify that the
 

00:04:14.200 --> 00:04:16.080 align:start position:0%
commit and then also verify that the
commit<00:04:14.500><c> is</c><00:04:14.680><c> done</c><00:04:14.980><c> through</c><00:04:15.280><c> doing</c><00:04:15.519><c> on</c><00:04:15.760><c> chain</c>

00:04:16.080 --> 00:04:16.090 align:start position:0%
commit is done through doing on chain
 

00:04:16.090 --> 00:04:19.170 align:start position:0%
commit is done through doing on chain
miracle<00:04:16.600><c> material</c><00:04:17.049><c> proof</c><00:04:17.739><c> verification</c><00:04:18.400><c> so</c>

00:04:19.170 --> 00:04:19.180 align:start position:0%
miracle material proof verification so
 

00:04:19.180 --> 00:04:20.909 align:start position:0%
miracle material proof verification so
all<00:04:19.479><c> in</c><00:04:19.630><c> all</c><00:04:19.750><c> if</c><00:04:20.019><c> you</c><00:04:20.169><c> compare</c><00:04:20.590><c> kind</c><00:04:20.799><c> of</c><00:04:20.859><c> the</c>

00:04:20.909 --> 00:04:20.919 align:start position:0%
all in all if you compare kind of the
 

00:04:20.919 --> 00:04:22.890 align:start position:0%
all in all if you compare kind of the
gas<00:04:21.400><c> consumption</c><00:04:21.880><c> of</c><00:04:22.150><c> just</c><00:04:22.330><c> a</c><00:04:22.419><c> regular</c>

00:04:22.890 --> 00:04:22.900 align:start position:0%
gas consumption of just a regular
 

00:04:22.900 --> 00:04:25.140 align:start position:0%
gas consumption of just a regular
transaction<00:04:23.500><c> with</c><00:04:24.009><c> the</c><00:04:24.040><c> gas</c><00:04:24.340><c> consumption</c><00:04:24.790><c> of</c>

00:04:25.140 --> 00:04:25.150 align:start position:0%
transaction with the gas consumption of
 

00:04:25.150 --> 00:04:27.360 align:start position:0%
transaction with the gas consumption of
a<00:04:25.290><c> submarine</c><00:04:26.290><c> sentence</c><00:04:26.680><c> or</c><00:04:26.800><c> live</c><00:04:26.949><c> submarine</c>

00:04:27.360 --> 00:04:27.370 align:start position:0%
a submarine sentence or live submarine
 

00:04:27.370 --> 00:04:29.730 align:start position:0%
a submarine sentence or live submarine
you<00:04:27.820><c> have</c><00:04:27.910><c> approximately</c><00:04:28.780><c> 200</c><00:04:29.320><c> K</c><00:04:29.500><c> gas</c>

00:04:29.730 --> 00:04:29.740 align:start position:0%
you have approximately 200 K gas
 

00:04:29.740 --> 00:04:33.439 align:start position:0%
you have approximately 200 K gas
additional<00:04:30.490><c> per</c><00:04:31.120><c> per</c><00:04:32.050><c> commit</c><00:04:32.380><c> reveal</c><00:04:32.710><c> kind</c><00:04:33.100><c> of</c>

00:04:33.439 --> 00:04:33.449 align:start position:0%
additional per per commit reveal kind of
 

00:04:33.449 --> 00:04:37.110 align:start position:0%
additional per per commit reveal kind of
process<00:04:34.449><c> but</c><00:04:35.050><c> on</c><00:04:36.039><c> the</c><00:04:36.400><c> flip</c><00:04:36.580><c> side</c><00:04:36.610><c> you</c><00:04:36.789><c> get</c>

00:04:37.110 --> 00:04:37.120 align:start position:0%
process but on the flip side you get
 

00:04:37.120 --> 00:04:38.550 align:start position:0%
process but on the flip side you get
front<00:04:37.449><c> running</c><00:04:37.600><c> protection</c><00:04:38.110><c> and</c><00:04:38.320><c> you</c><00:04:38.440><c> also</c>

00:04:38.550 --> 00:04:38.560 align:start position:0%
front running protection and you also
 

00:04:38.560 --> 00:04:40.650 align:start position:0%
front running protection and you also
get<00:04:38.830><c> protection</c><00:04:39.310><c> against</c><00:04:39.550><c> signaling</c><00:04:40.360><c> schemes</c>

00:04:40.650 --> 00:04:40.660 align:start position:0%
get protection against signaling schemes
 

00:04:40.660 --> 00:04:43.469 align:start position:0%
get protection against signaling schemes
so<00:04:41.530><c> we</c><00:04:41.860><c> have</c><00:04:42.009><c> one</c><00:04:42.490><c> decks</c><00:04:42.789><c> that's</c><00:04:43.060><c> looking</c><00:04:43.360><c> to</c>

00:04:43.469 --> 00:04:43.479 align:start position:0%
so we have one decks that's looking to
 

00:04:43.479 --> 00:04:45.150 align:start position:0%
so we have one decks that's looking to
integrate<00:04:43.690><c> with</c><00:04:44.020><c> us</c><00:04:44.199><c> already</c><00:04:44.440><c> to</c><00:04:44.770><c> help</c><00:04:45.009><c> them</c>

00:04:45.150 --> 00:04:45.160 align:start position:0%
integrate with us already to help them
 

00:04:45.160 --> 00:04:47.189 align:start position:0%
integrate with us already to help them
prevent<00:04:45.520><c> their</c><00:04:46.509><c> their</c><00:04:46.780><c> front</c><00:04:47.020><c> running</c>

00:04:47.189 --> 00:04:47.199 align:start position:0%
prevent their their front running
 

00:04:47.199 --> 00:04:49.050 align:start position:0%
prevent their their front running
problems<00:04:47.710><c> and</c><00:04:47.949><c> we</c><00:04:48.130><c> encourage</c><00:04:48.460><c> anyone</c><00:04:48.820><c> that's</c>

00:04:49.050 --> 00:04:49.060 align:start position:0%
problems and we encourage anyone that's
 

00:04:49.060 --> 00:04:50.879 align:start position:0%
problems and we encourage anyone that's
looking<00:04:49.210><c> on</c><00:04:49.630><c> implementing</c><00:04:50.289><c> these</c><00:04:50.500><c> kinds</c><00:04:50.560><c> of</c>

00:04:50.879 --> 00:04:50.889 align:start position:0%
looking on implementing these kinds of
 

00:04:50.889 --> 00:04:53.310 align:start position:0%
looking on implementing these kinds of
techniques<00:04:51.220><c> to</c><00:04:51.880><c> reach</c><00:04:52.060><c> out</c><00:04:52.240><c> to</c><00:04:52.389><c> us</c><00:04:52.509><c> these</c><00:04:53.139><c> are</c>

00:04:53.310 --> 00:04:53.320 align:start position:0%
techniques to reach out to us these are
 

00:04:53.320 --> 00:04:56.490 align:start position:0%
techniques to reach out to us these are
our<00:04:53.560><c> Twitter</c><00:04:54.270><c> hashtags</c><00:04:55.270><c> our</c><00:04:55.570><c> twitter</c><00:04:55.900><c> handles</c>

00:04:56.490 --> 00:04:56.500 align:start position:0%
our Twitter hashtags our twitter handles
 

00:04:56.500 --> 00:04:58.950 align:start position:0%
our Twitter hashtags our twitter handles
so<00:04:57.039><c> reach</c><00:04:57.280><c> out</c><00:04:57.430><c> to</c><00:04:57.550><c> us</c><00:04:57.639><c> we'll</c><00:04:58.300><c> be</c><00:04:58.570><c> happy</c><00:04:58.840><c> to</c>

00:04:58.950 --> 00:04:58.960 align:start position:0%
so reach out to us we'll be happy to
 

00:04:58.960 --> 00:05:01.170 align:start position:0%
so reach out to us we'll be happy to
answer<00:04:58.990><c> question</c><00:04:59.650><c> how</c><00:04:59.860><c> to</c><00:04:59.919><c> integrate</c><00:05:00.100><c> and</c><00:05:01.030><c> you</c>

00:05:01.170 --> 00:05:01.180 align:start position:0%
answer question how to integrate and you
 

00:05:01.180 --> 00:05:02.879 align:start position:0%
answer question how to integrate and you
can<00:05:01.300><c> also</c><00:05:01.419><c> check</c><00:05:01.780><c> out</c><00:05:01.930><c> live</c><00:05:02.169><c> submarine</c><00:05:02.500><c> org</c>

00:05:02.879 --> 00:05:02.889 align:start position:0%
can also check out live submarine org
 

00:05:02.889 --> 00:05:04.890 align:start position:0%
can also check out live submarine org
this<00:05:03.340><c> is</c><00:05:03.580><c> just</c><00:05:03.910><c> open</c><00:05:04.210><c> source</c><00:05:04.389><c> code</c><00:05:04.600><c> that</c><00:05:04.810><c> we're</c>

00:05:04.890 --> 00:05:04.900 align:start position:0%
this is just open source code that we're
 

00:05:04.900 --> 00:05:07.379 align:start position:0%
this is just open source code that we're
working<00:05:05.050><c> on</c><00:05:05.260><c> for</c><00:05:05.440><c> fun</c><00:05:05.620><c> no</c><00:05:06.250><c> fees</c><00:05:06.490><c> no</c><00:05:06.760><c> token</c><00:05:07.150><c> no</c>

00:05:07.379 --> 00:05:07.389 align:start position:0%
working on for fun no fees no token no
 

00:05:07.389 --> 00:05:07.980 align:start position:0%
working on for fun no fees no token no
nothing

00:05:07.980 --> 00:05:07.990 align:start position:0%
nothing
 

00:05:07.990 --> 00:05:10.560 align:start position:0%
nothing
take<00:05:08.320><c> a</c><00:05:08.350><c> look</c><00:05:08.560><c> implement</c><00:05:09.039><c> it</c><00:05:09.220><c> and</c><00:05:09.479><c> see</c><00:05:10.479><c> you</c>

00:05:10.560 --> 00:05:10.570 align:start position:0%
take a look implement it and see you
 

00:05:10.570 --> 00:05:20.770 align:start position:0%
take a look implement it and see you
online

00:05:20.770 --> 00:05:20.780 align:start position:0%
 
 

00:05:20.780 --> 00:05:22.840 align:start position:0%
 
you