WEBVTT
Kind: captions
Language: en

00:00:01.160 --> 00:00:06.690 align:start position:0%
 
[Music]

00:00:06.690 --> 00:00:06.700 align:start position:0%
 
 

00:00:06.700 --> 00:00:14.310 align:start position:0%
 
[Music]

00:00:14.310 --> 00:00:14.320 align:start position:0%
 
 

00:00:14.320 --> 00:00:17.950 align:start position:0%
 
good<00:00:14.519><c> morning</c><00:00:14.960><c> everyone</c><00:00:15.960><c> uh</c><00:00:16.320><c> glad</c><00:00:16.560><c> to</c><00:00:16.720><c> be</c><00:00:17.000><c> here</c>

00:00:17.950 --> 00:00:17.960 align:start position:0%
good morning everyone uh glad to be here
 

00:00:17.960 --> 00:00:20.630 align:start position:0%
good morning everyone uh glad to be here
uh<00:00:18.119><c> as</c><00:00:18.199><c> you</c><00:00:18.320><c> see</c><00:00:18.640><c> I</c><00:00:18.800><c> renamed</c><00:00:19.279><c> my</c><00:00:19.480><c> trans</c><00:00:19.960><c> uh</c><00:00:20.279><c> my</c>

00:00:20.630 --> 00:00:20.640 align:start position:0%
uh as you see I renamed my trans uh my
 

00:00:20.640 --> 00:00:22.470 align:start position:0%
uh as you see I renamed my trans uh my
presentation<00:00:21.359><c> but</c><00:00:21.480><c> it's</c><00:00:21.640><c> the</c><00:00:21.760><c> same</c><00:00:22.000><c> thing</c><00:00:22.240><c> I</c>

00:00:22.470 --> 00:00:22.480 align:start position:0%
presentation but it's the same thing I
 

00:00:22.480 --> 00:00:24.550 align:start position:0%
presentation but it's the same thing I
promise<00:00:23.480><c> uh</c><00:00:23.599><c> so</c><00:00:23.840><c> we</c><00:00:24.039><c> basically</c><00:00:24.400><c> just</c>

00:00:24.550 --> 00:00:24.560 align:start position:0%
promise uh so we basically just
 

00:00:24.560 --> 00:00:27.589 align:start position:0%
promise uh so we basically just
rebranded<00:00:25.199><c> some</c><00:00:25.439><c> things</c><00:00:26.119><c> uh</c><00:00:26.400><c> I</c><00:00:26.760><c> applied</c><00:00:27.240><c> here</c>

00:00:27.589 --> 00:00:27.599 align:start position:0%
rebranded some things uh I applied here
 

00:00:27.599 --> 00:00:30.790 align:start position:0%
rebranded some things uh I applied here
as<00:00:28.320><c> um</c><00:00:29.320><c> co-founder</c><00:00:29.800><c> at</c><00:00:30.000><c> cluster</c><00:00:30.400><c> but</c><00:00:30.519><c> now</c><00:00:30.679><c> I</c>

00:00:30.790 --> 00:00:30.800 align:start position:0%
as um co-founder at cluster but now I
 

00:00:30.800 --> 00:00:34.270 align:start position:0%
as um co-founder at cluster but now I
work<00:00:31.039><c> as</c><00:00:31.240><c> VP</c><00:00:31.679><c> product</c><00:00:32.040><c> at</c><00:00:32.279><c> bomy</c><00:00:33.160><c> so</c><00:00:33.840><c> uh</c><00:00:34.000><c> without</c>

00:00:34.270 --> 00:00:34.280 align:start position:0%
work as VP product at bomy so uh without
 

00:00:34.280 --> 00:00:35.790 align:start position:0%
work as VP product at bomy so uh without
further<00:00:34.600><c> Ado</c><00:00:34.800><c> we</c><00:00:34.920><c> only</c><00:00:35.079><c> have</c><00:00:35.239><c> 5</c><00:00:35.399><c> minutes</c><00:00:35.640><c> so</c>

00:00:35.790 --> 00:00:35.800 align:start position:0%
further Ado we only have 5 minutes so
 

00:00:35.800 --> 00:00:39.190 align:start position:0%
further Ado we only have 5 minutes so
let's<00:00:35.960><c> get</c><00:00:36.520><c> started</c><00:00:37.520><c> um</c><00:00:38.320><c> so</c><00:00:38.800><c> one</c><00:00:38.920><c> of</c><00:00:39.040><c> the</c>

00:00:39.190 --> 00:00:39.200 align:start position:0%
let's get started um so one of the
 

00:00:39.200 --> 00:00:41.790 align:start position:0%
let's get started um so one of the
things<00:00:39.600><c> that</c><00:00:39.879><c> we</c><00:00:40.200><c> basically</c><00:00:40.640><c> deal</c><00:00:40.960><c> with</c><00:00:41.200><c> today</c>

00:00:41.790 --> 00:00:41.800 align:start position:0%
things that we basically deal with today
 

00:00:41.800 --> 00:00:45.350 align:start position:0%
things that we basically deal with today
is<00:00:42.160><c> let's</c><00:00:42.360><c> call</c><00:00:42.559><c> it</c><00:00:42.719><c> monolithic</c><00:00:43.879><c> execution</c><00:00:44.879><c> um</c>

00:00:45.350 --> 00:00:45.360 align:start position:0%
is let's call it monolithic execution um
 

00:00:45.360 --> 00:00:47.590 align:start position:0%
is let's call it monolithic execution um
so<00:00:46.360><c> let's</c><00:00:46.559><c> call</c><00:00:46.719><c> it</c><00:00:46.840><c> like</c><00:00:47.000><c> this</c><00:00:47.120><c> you</c><00:00:47.239><c> have</c><00:00:47.360><c> your</c>

00:00:47.590 --> 00:00:47.600 align:start position:0%
so let's call it like this you have your
 

00:00:47.600 --> 00:00:49.709 align:start position:0%
so let's call it like this you have your
normal<00:00:48.000><c> blockchain</c><00:00:48.480><c> transaction</c><00:00:49.079><c> you</c><00:00:49.360><c> encode</c>

00:00:49.709 --> 00:00:49.719 align:start position:0%
normal blockchain transaction you encode
 

00:00:49.719 --> 00:00:51.990 align:start position:0%
normal blockchain transaction you encode
a<00:00:49.920><c> transaction</c><00:00:50.480><c> you</c><00:00:50.680><c> sign</c><00:00:51.000><c> it</c><00:00:51.520><c> and</c><00:00:51.640><c> you</c><00:00:51.760><c> send</c>

00:00:51.990 --> 00:00:52.000 align:start position:0%
a transaction you sign it and you send
 

00:00:52.000 --> 00:00:54.189 align:start position:0%
a transaction you sign it and you send
it<00:00:52.120><c> to</c><00:00:52.239><c> an</c><00:00:52.359><c> RPC</c><00:00:52.800><c> node</c><00:00:53.039><c> and</c><00:00:53.199><c> the</c><00:00:53.280><c> RPC</c><00:00:53.719><c> node</c><00:00:53.960><c> sends</c>

00:00:54.189 --> 00:00:54.199 align:start position:0%
it to an RPC node and the RPC node sends
 

00:00:54.199 --> 00:00:56.069 align:start position:0%
it to an RPC node and the RPC node sends
it<00:00:54.320><c> to</c><00:00:54.440><c> a</c><00:00:54.559><c> block</c><00:00:54.800><c> Builder</c><00:00:55.160><c> who</c><00:00:55.359><c> then</c><00:00:55.800><c> you</c><00:00:55.920><c> know</c>

00:00:56.069 --> 00:00:56.079 align:start position:0%
it to a block Builder who then you know
 

00:00:56.079 --> 00:00:58.430 align:start position:0%
it to a block Builder who then you know
it<00:00:56.199><c> goes</c><00:00:56.399><c> to</c><00:00:56.559><c> a</c><00:00:56.680><c> minor</c><00:00:57.160><c> or</c><00:00:57.359><c> a</c><00:00:57.760><c> validator</c><00:00:58.239><c> or</c><00:00:58.359><c> a</c>

00:00:58.430 --> 00:00:58.440 align:start position:0%
it goes to a minor or a validator or a
 

00:00:58.440 --> 00:00:59.950 align:start position:0%
it goes to a minor or a validator or a
sequencer<00:00:59.000><c> they</c><00:00:59.120><c> include</c><00:00:59.399><c> it</c><00:00:59.519><c> into</c><00:00:59.640><c> the</c><00:00:59.719><c> BL</c>

00:00:59.950 --> 00:00:59.960 align:start position:0%
sequencer they include it into the BL
 

00:00:59.960 --> 00:01:02.229 align:start position:0%
sequencer they include it into the BL
Blain<00:01:00.239><c> and</c><00:01:00.399><c> that's</c><00:01:00.559><c> it</c><00:01:01.399><c> that's</c><00:01:01.559><c> monolithic</c>

00:01:02.229 --> 00:01:02.239 align:start position:0%
Blain and that's it that's monolithic
 

00:01:02.239 --> 00:01:04.390 align:start position:0%
Blain and that's it that's monolithic
and<00:01:03.079><c> some</c><00:01:03.239><c> of</c><00:01:03.440><c> the</c><00:01:03.680><c> some</c><00:01:03.800><c> of</c><00:01:03.920><c> the</c><00:01:04.000><c> features</c><00:01:04.280><c> of</c>

00:01:04.390 --> 00:01:04.400 align:start position:0%
and some of the some of the features of
 

00:01:04.400 --> 00:01:06.270 align:start position:0%
and some of the some of the features of
the<00:01:04.479><c> monolithic</c><00:01:05.000><c> environments</c><00:01:05.479><c> are</c><00:01:06.080><c> they're</c>

00:01:06.270 --> 00:01:06.280 align:start position:0%
the monolithic environments are they're
 

00:01:06.280 --> 00:01:09.070 align:start position:0%
the monolithic environments are they're
unicast<00:01:06.920><c> like</c><00:01:07.119><c> one</c><00:01:07.600><c> RPC</c><00:01:08.200><c> node</c><00:01:08.520><c> communicates</c>

00:01:09.070 --> 00:01:09.080 align:start position:0%
unicast like one RPC node communicates
 

00:01:09.080 --> 00:01:11.510 align:start position:0%
unicast like one RPC node communicates
to<00:01:09.240><c> one</c><00:01:09.479><c> blockchain</c><00:01:10.360><c> they're</c><00:01:10.680><c> isomorphic</c><00:01:11.400><c> in</c>

00:01:11.510 --> 00:01:11.520 align:start position:0%
to one blockchain they're isomorphic in
 

00:01:11.520 --> 00:01:14.429 align:start position:0%
to one blockchain they're isomorphic in
a<00:01:11.680><c> sense</c><00:01:11.960><c> that</c><00:01:12.119><c> an</c><00:01:12.439><c> evm</c><00:01:13.280><c> node</c><00:01:13.759><c> doesn't</c>

00:01:14.429 --> 00:01:14.439 align:start position:0%
a sense that an evm node doesn't
 

00:01:14.439 --> 00:01:17.149 align:start position:0%
a sense that an evm node doesn't
understand<00:01:14.640><c> an</c><00:01:14.880><c> svm</c><00:01:15.439><c> transaction</c><00:01:16.159><c> or</c><00:01:16.479><c> like</c><00:01:16.600><c> a</c>

00:01:17.149 --> 00:01:17.159 align:start position:0%
understand an svm transaction or like a
 

00:01:17.159 --> 00:01:19.390 align:start position:0%
understand an svm transaction or like a
near<00:01:17.520><c> transaction</c><00:01:18.000><c> or</c><00:01:18.159><c> a</c><00:01:18.560><c> wasm</c><00:01:18.960><c> transaction</c>

00:01:19.390 --> 00:01:19.400 align:start position:0%
near transaction or a wasm transaction
 

00:01:19.400 --> 00:01:22.429 align:start position:0%
near transaction or a wasm transaction
or<00:01:19.560><c> whatever</c><00:01:20.360><c> uh</c><00:01:20.479><c> signature</c><00:01:20.920><c> scheme</c><00:01:21.439><c> coupled</c>

00:01:22.429 --> 00:01:22.439 align:start position:0%
or whatever uh signature scheme coupled
 

00:01:22.439 --> 00:01:24.469 align:start position:0%
or whatever uh signature scheme coupled
uh<00:01:22.840><c> you</c><00:01:22.960><c> know</c><00:01:23.119><c> your</c><00:01:23.320><c> ethereum</c><00:01:23.759><c> node</c><00:01:24.159><c> really</c>

00:01:24.469 --> 00:01:24.479 align:start position:0%
uh you know your ethereum node really
 

00:01:24.479 --> 00:01:26.670 align:start position:0%
uh you know your ethereum node really
does<00:01:24.799><c> only</c><00:01:25.040><c> use</c><00:01:25.320><c> one</c><00:01:25.520><c> signature</c><00:01:25.960><c> scheme</c><00:01:26.360><c> for</c>

00:01:26.670 --> 00:01:26.680 align:start position:0%
does only use one signature scheme for
 

00:01:26.680 --> 00:01:28.670 align:start position:0%
does only use one signature scheme for
everything<00:01:27.479><c> uh</c><00:01:27.560><c> they're</c><00:01:27.759><c> non-c</c><00:01:28.119><c> composable</c>

00:01:28.670 --> 00:01:28.680 align:start position:0%
everything uh they're non-c composable
 

00:01:28.680 --> 00:01:30.510 align:start position:0%
everything uh they're non-c composable
so<00:01:28.840><c> imagine</c><00:01:29.159><c> if</c><00:01:29.280><c> you</c><00:01:29.360><c> are</c><00:01:29.560><c> pre</c><00:01:29.960><c> signing</c><00:01:30.280><c> two</c>

00:01:30.510 --> 00:01:30.520 align:start position:0%
so imagine if you are pre signing two
 

00:01:30.520 --> 00:01:33.310 align:start position:0%
so imagine if you are pre signing two
transactions<00:01:31.200><c> so</c><00:01:31.520><c> one</c><00:01:31.920><c> and</c><00:01:32.079><c> two</c><00:01:32.640><c> you</c><00:01:32.880><c> can't</c>

00:01:33.310 --> 00:01:33.320 align:start position:0%
transactions so one and two you can't
 

00:01:33.320 --> 00:01:35.870 align:start position:0%
transactions so one and two you can't
pre-sign<00:01:34.280><c> that</c><00:01:34.560><c> the</c><00:01:34.880><c> second</c><00:01:35.280><c> transaction</c>

00:01:35.870 --> 00:01:35.880 align:start position:0%
pre-sign that the second transaction
 

00:01:35.880 --> 00:01:37.950 align:start position:0%
pre-sign that the second transaction
takes<00:01:36.240><c> as</c><00:01:36.399><c> its</c><00:01:36.680><c> input</c><00:01:37.159><c> the</c><00:01:37.280><c> output</c><00:01:37.640><c> from</c><00:01:37.880><c> the</c>

00:01:37.950 --> 00:01:37.960 align:start position:0%
takes as its input the output from the
 

00:01:37.960 --> 00:01:39.950 align:start position:0%
takes as its input the output from the
first<00:01:38.360><c> transaction</c><00:01:39.360><c> uh</c><00:01:39.520><c> and</c><00:01:39.720><c> they're</c>

00:01:39.950 --> 00:01:39.960 align:start position:0%
first transaction uh and they're
 

00:01:39.960 --> 00:01:41.749 align:start position:0%
first transaction uh and they're
non-collaborative<00:01:40.880><c> if</c><00:01:40.960><c> you</c><00:01:41.079><c> have</c><00:01:41.280><c> multiple</c>

00:01:41.749 --> 00:01:41.759 align:start position:0%
non-collaborative if you have multiple
 

00:01:41.759 --> 00:01:43.469 align:start position:0%
non-collaborative if you have multiple
transactions<00:01:42.280><c> that</c><00:01:42.399><c> you</c><00:01:42.479><c> want</c><00:01:42.640><c> to</c><00:01:42.840><c> execute</c>

00:01:43.469 --> 00:01:43.479 align:start position:0%
transactions that you want to execute
 

00:01:43.479 --> 00:01:44.990 align:start position:0%
transactions that you want to execute
first<00:01:43.680><c> of</c><00:01:43.799><c> all</c><00:01:43.920><c> you</c><00:01:44.040><c> can't</c><00:01:44.320><c> even</c><00:01:44.520><c> bundle</c><00:01:44.880><c> them</c>

00:01:44.990 --> 00:01:45.000 align:start position:0%
first of all you can't even bundle them
 

00:01:45.000 --> 00:01:47.350 align:start position:0%
first of all you can't even bundle them
in<00:01:45.119><c> a</c><00:01:45.240><c> single</c><00:01:45.520><c> object</c><00:01:45.960><c> but</c><00:01:46.119><c> even</c><00:01:46.399><c> if</c><00:01:46.560><c> you</c><00:01:46.759><c> could</c>

00:01:47.350 --> 00:01:47.360 align:start position:0%
in a single object but even if you could
 

00:01:47.360 --> 00:01:49.310 align:start position:0%
in a single object but even if you could
there<00:01:47.479><c> is</c><00:01:47.680><c> no</c><00:01:47.920><c> way</c><00:01:48.119><c> for</c><00:01:48.360><c> a</c><00:01:48.680><c> collaborative</c>

00:01:49.310 --> 00:01:49.320 align:start position:0%
there is no way for a collaborative
 

00:01:49.320 --> 00:01:51.469 align:start position:0%
there is no way for a collaborative
execution<00:01:49.880><c> where</c><00:01:50.399><c> let's</c><00:01:50.600><c> say</c><00:01:50.799><c> a</c><00:01:50.960><c> solver</c>

00:01:51.469 --> 00:01:51.479 align:start position:0%
execution where let's say a solver
 

00:01:51.479 --> 00:01:53.270 align:start position:0%
execution where let's say a solver
solves<00:01:51.840><c> for</c><00:01:52.000><c> a</c><00:01:52.159><c> fraction</c><00:01:52.479><c> of</c><00:01:52.640><c> your</c><00:01:53.119><c> uh</c>

00:01:53.270 --> 00:01:53.280 align:start position:0%
solves for a fraction of your uh
 

00:01:53.280 --> 00:01:55.149 align:start position:0%
solves for a fraction of your uh
transaction<00:01:53.920><c> then</c><00:01:54.040><c> a</c><00:01:54.159><c> bundler</c><00:01:54.600><c> solves</c><00:01:54.960><c> for</c>

00:01:55.149 --> 00:01:55.159 align:start position:0%
transaction then a bundler solves for
 

00:01:55.159 --> 00:01:57.230 align:start position:0%
transaction then a bundler solves for
the<00:01:55.320><c> next</c><00:01:56.079><c> fraction</c><00:01:56.399><c> of</c><00:01:56.520><c> your</c><00:01:56.680><c> transaction</c>

00:01:57.230 --> 00:01:57.240 align:start position:0%
the next fraction of your transaction
 

00:01:57.240 --> 00:02:00.590 align:start position:0%
the next fraction of your transaction
Etc<00:01:58.159><c> um</c><00:01:58.520><c> so</c><00:01:59.520><c> yeah</c><00:01:59.680><c> this</c><00:01:59.960><c> are</c><00:02:00.079><c> the</c><00:02:00.200><c> problems</c>

00:02:00.590 --> 00:02:00.600 align:start position:0%
Etc um so yeah this are the problems
 

00:02:00.600 --> 00:02:03.510 align:start position:0%
Etc um so yeah this are the problems
with<00:02:01.039><c> monolithic</c><00:02:01.799><c> execution</c><00:02:02.799><c> and</c><00:02:03.119><c> that's</c>

00:02:03.510 --> 00:02:03.520 align:start position:0%
with monolithic execution and that's
 

00:02:03.520 --> 00:02:06.190 align:start position:0%
with monolithic execution and that's
where<00:02:03.719><c> we</c><00:02:03.880><c> go</c><00:02:04.240><c> into</c><00:02:04.640><c> this</c><00:02:05.119><c> modular</c><00:02:05.640><c> execution</c>

00:02:06.190 --> 00:02:06.200 align:start position:0%
where we go into this modular execution
 

00:02:06.200 --> 00:02:07.710 align:start position:0%
where we go into this modular execution
what<00:02:06.320><c> we</c><00:02:06.399><c> use</c><00:02:06.600><c> to</c><00:02:06.719><c> call</c><00:02:06.960><c> transaction</c>

00:02:07.710 --> 00:02:07.720 align:start position:0%
what we use to call transaction
 

00:02:07.720 --> 00:02:09.830 align:start position:0%
what we use to call transaction
orchestration<00:02:08.720><c> uh</c><00:02:08.840><c> modular</c><00:02:09.319><c> execution</c>

00:02:09.830 --> 00:02:09.840 align:start position:0%
orchestration uh modular execution
 

00:02:09.840 --> 00:02:13.710 align:start position:0%
orchestration uh modular execution
environment<00:02:10.599><c> uh</c><00:02:10.720><c> in</c><00:02:10.920><c> essence</c><00:02:11.640><c> is</c><00:02:12.319><c> um</c><00:02:12.840><c> is</c><00:02:13.000><c> using</c>

00:02:13.710 --> 00:02:13.720 align:start position:0%
environment uh in essence is um is using
 

00:02:13.720 --> 00:02:15.869 align:start position:0%
environment uh in essence is um is using
super<00:02:14.200><c> transactions</c><00:02:15.200><c> and</c><00:02:15.400><c> a</c><00:02:15.519><c> super</c>

00:02:15.869 --> 00:02:15.879 align:start position:0%
super transactions and a super
 

00:02:15.879 --> 00:02:17.589 align:start position:0%
super transactions and a super
transaction<00:02:16.360><c> is</c><00:02:16.440><c> a</c><00:02:16.599><c> single</c><00:02:16.920><c> data</c><00:02:17.239><c> object</c>

00:02:17.589 --> 00:02:17.599 align:start position:0%
transaction is a single data object
 

00:02:17.599 --> 00:02:19.070 align:start position:0%
transaction is a single data object
which<00:02:17.760><c> can</c><00:02:17.959><c> contain</c><00:02:18.560><c> the</c><00:02:18.720><c> payment</c>

00:02:19.070 --> 00:02:19.080 align:start position:0%
which can contain the payment
 

00:02:19.080 --> 00:02:20.949 align:start position:0%
which can contain the payment
information<00:02:19.720><c> for</c><00:02:20.040><c> how</c><00:02:20.160><c> you</c><00:02:20.280><c> want</c><00:02:20.400><c> to</c><00:02:20.599><c> pay</c><00:02:20.760><c> for</c>

00:02:20.949 --> 00:02:20.959 align:start position:0%
information for how you want to pay for
 

00:02:20.959 --> 00:02:23.670 align:start position:0%
information for how you want to pay for
this<00:02:21.160><c> super</c><00:02:21.640><c> transaction</c><00:02:22.640><c> uh</c><00:02:22.800><c> user</c><00:02:23.200><c> Ops</c>

00:02:23.670 --> 00:02:23.680 align:start position:0%
this super transaction uh user Ops
 

00:02:23.680 --> 00:02:26.750 align:start position:0%
this super transaction uh user Ops
intents<00:02:24.440><c> offchain</c><00:02:25.000><c> actions</c><00:02:25.440><c> ZK</c><00:02:25.920><c> proofs</c><00:02:26.560><c> it's</c>

00:02:26.750 --> 00:02:26.760 align:start position:0%
intents offchain actions ZK proofs it's
 

00:02:26.760 --> 00:02:28.910 align:start position:0%
intents offchain actions ZK proofs it's
modular<00:02:27.319><c> it's</c><00:02:27.519><c> extensible</c><00:02:28.200><c> and</c><00:02:28.319><c> it's</c><00:02:28.519><c> also</c>

00:02:28.910 --> 00:02:28.920 align:start position:0%
modular it's extensible and it's also
 

00:02:28.920 --> 00:02:31.509 align:start position:0%
modular it's extensible and it's also
recursive<00:02:30.000><c> so</c><00:02:30.319><c> what</c><00:02:30.440><c> does</c><00:02:30.640><c> this</c><00:02:30.800><c> enable</c><00:02:31.239><c> so</c>

00:02:31.509 --> 00:02:31.519 align:start position:0%
recursive so what does this enable so
 

00:02:31.519 --> 00:02:34.710 align:start position:0%
recursive so what does this enable so
this<00:02:31.680><c> enables</c><00:02:32.400><c> essentially</c><00:02:33.400><c> um</c><00:02:33.959><c> a</c><00:02:34.120><c> node</c><00:02:34.519><c> to</c>

00:02:34.710 --> 00:02:34.720 align:start position:0%
this enables essentially um a node to
 

00:02:34.720 --> 00:02:36.830 align:start position:0%
this enables essentially um a node to
commit<00:02:35.080><c> to</c><00:02:35.280><c> multiple</c><00:02:35.800><c> actions</c><00:02:36.160><c> to</c><00:02:36.319><c> the</c><00:02:36.440><c> user</c>

00:02:36.830 --> 00:02:36.840 align:start position:0%
commit to multiple actions to the user
 

00:02:36.840 --> 00:02:39.110 align:start position:0%
commit to multiple actions to the user
and<00:02:36.959><c> the</c><00:02:37.080><c> user</c><00:02:37.440><c> permissions</c><00:02:38.440><c> these</c><00:02:38.680><c> multiple</c>

00:02:39.110 --> 00:02:39.120 align:start position:0%
and the user permissions these multiple
 

00:02:39.120 --> 00:02:41.550 align:start position:0%
and the user permissions these multiple
actions<00:02:39.480><c> with</c><00:02:39.599><c> a</c><00:02:39.720><c> single</c><00:02:40.400><c> signature</c><00:02:41.239><c> uh</c><00:02:41.360><c> it</c>

00:02:41.550 --> 00:02:41.560 align:start position:0%
actions with a single signature uh it
 

00:02:41.560 --> 00:02:43.990 align:start position:0%
actions with a single signature uh it
requires<00:02:42.319><c> uh</c><00:02:42.480><c> smart</c><00:02:42.840><c> contract</c><00:02:43.280><c> accounts</c><00:02:43.760><c> it</c>

00:02:43.990 --> 00:02:44.000 align:start position:0%
requires uh smart contract accounts it
 

00:02:44.000 --> 00:02:48.070 align:start position:0%
requires uh smart contract accounts it
relies<00:02:44.440><c> on</c><00:02:44.840><c> ERC</c><00:02:45.640><c> 7579</c><00:02:46.640><c> validator</c><00:02:47.159><c> module</c><00:02:47.920><c> it</c>

00:02:48.070 --> 00:02:48.080 align:start position:0%
relies on ERC 7579 validator module it
 

00:02:48.080 --> 00:02:49.949 align:start position:0%
relies on ERC 7579 validator module it
encodes<00:02:48.519><c> all</c><00:02:48.599><c> of</c><00:02:48.760><c> this</c><00:02:48.879><c> into</c><00:02:49.120><c> a</c><00:02:49.200><c> Merkel</c><00:02:49.599><c> tree</c>

00:02:49.949 --> 00:02:49.959 align:start position:0%
encodes all of this into a Merkel tree
 

00:02:49.959 --> 00:02:51.790 align:start position:0%
encodes all of this into a Merkel tree
then<00:02:50.080><c> you</c><00:02:50.280><c> sign</c><00:02:50.560><c> the</c><00:02:50.640><c> Merkel</c><00:02:50.959><c> tree</c><00:02:51.159><c> root</c><00:02:51.480><c> hash</c>

00:02:51.790 --> 00:02:51.800 align:start position:0%
then you sign the Merkel tree root hash
 

00:02:51.800 --> 00:02:53.710 align:start position:0%
then you sign the Merkel tree root hash
and<00:02:51.959><c> after</c><00:02:52.159><c> you've</c><00:02:52.360><c> signed</c><00:02:53.040><c> the</c><00:02:53.200><c> Merkel</c><00:02:53.560><c> tree</c>

00:02:53.710 --> 00:02:53.720 align:start position:0%
and after you've signed the Merkel tree
 

00:02:53.720 --> 00:02:55.589 align:start position:0%
and after you've signed the Merkel tree
root<00:02:54.120><c> hash</c><00:02:54.519><c> this</c><00:02:54.800><c> essentially</c><00:02:55.319><c> gives</c>

00:02:55.589 --> 00:02:55.599 align:start position:0%
root hash this essentially gives
 

00:02:55.599 --> 00:02:57.790 align:start position:0%
root hash this essentially gives
permission<00:02:56.319><c> to</c><00:02:56.560><c> all</c><00:02:56.800><c> to</c><00:02:56.920><c> all</c><00:02:57.040><c> of</c><00:02:57.120><c> the</c><00:02:57.239><c> leaves</c>

00:02:57.790 --> 00:02:57.800 align:start position:0%
permission to all to all of the leaves
 

00:02:57.800 --> 00:03:00.470 align:start position:0%
permission to all to all of the leaves
to<00:02:58.000><c> get</c><00:02:58.319><c> uh</c><00:02:58.519><c> executed</c><00:02:59.519><c> um</c><00:02:59.920><c> what's</c><00:03:00.120><c> the</c><00:03:00.280><c> cool</c>

00:03:00.470 --> 00:03:00.480 align:start position:0%
to get uh executed um what's the cool
 

00:03:00.480 --> 00:03:01.750 align:start position:0%
to get uh executed um what's the cool
thing<00:03:00.640><c> about</c><00:03:00.840><c> modular</c><00:03:01.319><c> execution</c>

00:03:01.750 --> 00:03:01.760 align:start position:0%
thing about modular execution
 

00:03:01.760 --> 00:03:03.710 align:start position:0%
thing about modular execution
environments<00:03:02.680><c> well</c><00:03:03.120><c> like</c><00:03:03.360><c> one</c><00:03:03.480><c> of</c><00:03:03.599><c> the</c>

00:03:03.710 --> 00:03:03.720 align:start position:0%
environments well like one of the
 

00:03:03.720 --> 00:03:05.630 align:start position:0%
environments well like one of the
coolest<00:03:04.080><c> things</c><00:03:04.280><c> is</c><00:03:04.440><c> that</c><00:03:04.640><c> they</c><00:03:04.840><c> are</c><00:03:05.519><c> uh</c>

00:03:05.630 --> 00:03:05.640 align:start position:0%
coolest things is that they are uh
 

00:03:05.640 --> 00:03:07.350 align:start position:0%
coolest things is that they are uh
modular<00:03:06.239><c> obviously</c><00:03:06.720><c> but</c><00:03:06.840><c> they</c><00:03:06.920><c> are</c><00:03:07.080><c> also</c>

00:03:07.350 --> 00:03:07.360 align:start position:0%
modular obviously but they are also
 

00:03:07.360 --> 00:03:09.509 align:start position:0%
modular obviously but they are also
recursive<00:03:08.360><c> uh</c><00:03:08.480><c> what</c><00:03:08.599><c> does</c><00:03:08.840><c> this</c><00:03:09.000><c> mean</c><00:03:09.280><c> so</c>

00:03:09.509 --> 00:03:09.519 align:start position:0%
recursive uh what does this mean so
 

00:03:09.519 --> 00:03:12.149 align:start position:0%
recursive uh what does this mean so
let's<00:03:09.720><c> say</c><00:03:09.959><c> I'm</c><00:03:10.080><c> a</c><00:03:10.280><c> node</c><00:03:11.280><c> um</c><00:03:11.760><c> which</c><00:03:11.959><c> has</c>

00:03:12.149 --> 00:03:12.159 align:start position:0%
let's say I'm a node um which has
 

00:03:12.159 --> 00:03:14.750 align:start position:0%
let's say I'm a node um which has
committed<00:03:12.519><c> to</c><00:03:12.720><c> execute</c><00:03:13.120><c> something</c><00:03:13.560><c> for</c><00:03:13.760><c> you</c>

00:03:14.750 --> 00:03:14.760 align:start position:0%
committed to execute something for you
 

00:03:14.760 --> 00:03:17.910 align:start position:0%
committed to execute something for you
um<00:03:15.120><c> and</c><00:03:15.480><c> I</c><00:03:16.440><c> don't</c><00:03:16.760><c> know</c><00:03:16.959><c> how</c><00:03:17.120><c> to</c><00:03:17.319><c> execute</c><00:03:17.760><c> the</c>

00:03:17.910 --> 00:03:17.920 align:start position:0%
um and I don't know how to execute the
 

00:03:17.920 --> 00:03:19.670 align:start position:0%
um and I don't know how to execute the
entire<00:03:18.640><c> thing</c><00:03:18.879><c> that</c><00:03:19.000><c> you</c><00:03:19.120><c> have</c><00:03:19.280><c> given</c><00:03:19.480><c> me</c>

00:03:19.670 --> 00:03:19.680 align:start position:0%
entire thing that you have given me
 

00:03:19.680 --> 00:03:22.670 align:start position:0%
entire thing that you have given me
maybe<00:03:19.879><c> it</c><00:03:20.040><c> has</c><00:03:20.280><c> like</c><00:03:20.440><c> a</c><00:03:21.159><c> intent</c><00:03:21.720><c> to</c><00:03:21.879><c> move</c><00:03:22.280><c> funds</c>

00:03:22.670 --> 00:03:22.680 align:start position:0%
maybe it has like a intent to move funds
 

00:03:22.680 --> 00:03:24.670 align:start position:0%
maybe it has like a intent to move funds
from<00:03:22.879><c> optimism</c><00:03:23.360><c> to</c><00:03:23.560><c> base</c><00:03:23.920><c> and</c><00:03:24.080><c> then</c><00:03:24.200><c> it</c><00:03:24.360><c> has</c><00:03:24.480><c> a</c>

00:03:24.670 --> 00:03:24.680 align:start position:0%
from optimism to base and then it has a
 

00:03:24.680 --> 00:03:27.110 align:start position:0%
from optimism to base and then it has a
requirement<00:03:25.159><c> for</c><00:03:25.640><c> two</c><00:03:25.879><c> two</c><00:03:26.040><c> or</c><00:03:26.200><c> three</c><00:03:26.720><c> user</c>

00:03:27.110 --> 00:03:27.120 align:start position:0%
requirement for two two or three user
 

00:03:27.120 --> 00:03:29.990 align:start position:0%
requirement for two two or three user
Ops<00:03:28.040><c> uh</c><00:03:28.120><c> to</c><00:03:28.360><c> execute</c><00:03:29.040><c> certain</c><00:03:29.360><c> you</c><00:03:29.480><c> know</c><00:03:29.840><c> let's</c>

00:03:29.990 --> 00:03:30.000 align:start position:0%
Ops uh to execute certain you know let's
 

00:03:30.000 --> 00:03:33.550 align:start position:0%
Ops uh to execute certain you know let's
call<00:03:30.120><c> it</c><00:03:30.280><c> like</c><00:03:30.439><c> this</c><00:03:31.120><c> uh</c><00:03:31.319><c> intent</c><00:03:32.319><c> uh</c><00:03:32.879><c> user</c><00:03:33.239><c> op</c>

00:03:33.550 --> 00:03:33.560 align:start position:0%
call it like this uh intent uh user op
 

00:03:33.560 --> 00:03:36.750 align:start position:0%
call it like this uh intent uh user op
first<00:03:33.920><c> remove</c><00:03:34.400><c> my</c><00:03:34.799><c> Supply</c><00:03:35.519><c> from</c><00:03:36.080><c> a</c><00:03:36.480><c> on</c>

00:03:36.750 --> 00:03:36.760 align:start position:0%
first remove my Supply from a on
 

00:03:36.760 --> 00:03:39.830 align:start position:0%
first remove my Supply from a on
optimism<00:03:37.439><c> then</c><00:03:37.560><c> an</c><00:03:37.959><c> intent</c><00:03:38.959><c> uh</c><00:03:39.120><c> move</c><00:03:39.640><c> this</c>

00:03:39.830 --> 00:03:39.840 align:start position:0%
optimism then an intent uh move this
 

00:03:39.840 --> 00:03:41.990 align:start position:0%
optimism then an intent uh move this
usdc<00:03:40.519><c> from</c><00:03:40.720><c> optimism</c><00:03:41.200><c> to</c><00:03:41.360><c> base</c><00:03:41.640><c> and</c><00:03:41.760><c> then</c><00:03:41.879><c> a</c>

00:03:41.990 --> 00:03:42.000 align:start position:0%
usdc from optimism to base and then a
 

00:03:42.000 --> 00:03:45.070 align:start position:0%
usdc from optimism to base and then a
user<00:03:42.319><c> op</c><00:03:42.640><c> Supply</c><00:03:43.040><c> to</c><00:03:43.599><c> a</c><00:03:43.959><c> on</c><00:03:44.159><c> base</c><00:03:44.760><c> which</c><00:03:44.920><c> is</c>

00:03:45.070 --> 00:03:45.080 align:start position:0%
user op Supply to a on base which is
 

00:03:45.080 --> 00:03:46.750 align:start position:0%
user op Supply to a on base which is
basically<00:03:45.480><c> let's</c><00:03:45.640><c> call</c><00:03:45.840><c> it</c><00:03:45.920><c> a</c><00:03:46.040><c> rebalancing</c><00:03:46.599><c> an</c>

00:03:46.750 --> 00:03:46.760 align:start position:0%
basically let's call it a rebalancing an
 

00:03:46.760 --> 00:03:48.630 align:start position:0%
basically let's call it a rebalancing an
AA<00:03:47.120><c> position</c><00:03:47.480><c> in</c><00:03:47.560><c> a</c><00:03:47.720><c> single</c><00:03:48.159><c> single</c>

00:03:48.630 --> 00:03:48.640 align:start position:0%
AA position in a single single
 

00:03:48.640 --> 00:03:51.789 align:start position:0%
AA position in a single single
transaction<00:03:49.640><c> super</c><00:03:50.239><c> transaction</c><00:03:51.239><c> um</c><00:03:51.640><c> and</c>

00:03:51.789 --> 00:03:51.799 align:start position:0%
transaction super transaction um and
 

00:03:51.799 --> 00:03:53.309 align:start position:0%
transaction super transaction um and
this<00:03:51.879><c> is</c><00:03:52.200><c> kind</c><00:03:52.319><c> of</c><00:03:52.480><c> let's</c><00:03:52.680><c> say</c><00:03:52.879><c> this</c><00:03:53.000><c> can</c><00:03:53.159><c> be</c>

00:03:53.309 --> 00:03:53.319 align:start position:0%
this is kind of let's say this can be
 

00:03:53.319 --> 00:03:55.630 align:start position:0%
this is kind of let's say this can be
done<00:03:53.519><c> by</c><00:03:53.680><c> a</c><00:03:53.799><c> single</c><00:03:54.079><c> node</c><00:03:54.439><c> but</c><00:03:54.760><c> for</c><00:03:55.120><c> for</c><00:03:55.439><c> just</c>

00:03:55.630 --> 00:03:55.640 align:start position:0%
done by a single node but for for just
 

00:03:55.640 --> 00:03:58.750 align:start position:0%
done by a single node but for for just
for<00:03:56.280><c> um</c><00:03:57.200><c> for</c><00:03:57.439><c> an</c><00:03:57.640><c> example</c><00:03:58.079><c> let's</c><00:03:58.239><c> say</c><00:03:58.680><c> a</c>

00:03:58.750 --> 00:03:58.760 align:start position:0%
for um for an example let's say a
 

00:03:58.760 --> 00:04:00.309 align:start position:0%
for um for an example let's say a
thought<00:03:59.040><c> experiment</c><00:03:59.519><c> let's</c><00:03:59.840><c> say</c><00:04:00.000><c> that</c><00:04:00.159><c> the</c>

00:04:00.309 --> 00:04:00.319 align:start position:0%
thought experiment let's say that the
 

00:04:00.319 --> 00:04:02.429 align:start position:0%
thought experiment let's say that the
node<00:04:00.640><c> doesn't</c><00:04:00.959><c> know</c><00:04:01.159><c> how</c><00:04:01.319><c> to</c><00:04:01.959><c> trigger</c><00:04:02.280><c> an</c>

00:04:02.429 --> 00:04:02.439 align:start position:0%
node doesn't know how to trigger an
 

00:04:02.439 --> 00:04:03.869 align:start position:0%
node doesn't know how to trigger an
intent<00:04:02.840><c> it</c><00:04:02.959><c> doesn't</c><00:04:03.200><c> know</c><00:04:03.360><c> how</c><00:04:03.439><c> to</c><00:04:03.560><c> front</c>

00:04:03.869 --> 00:04:03.879 align:start position:0%
intent it doesn't know how to front
 

00:04:03.879 --> 00:04:06.309 align:start position:0%
intent it doesn't know how to front
liquidity<00:04:04.799><c> what</c><00:04:04.959><c> can</c><00:04:05.200><c> happen</c><00:04:05.560><c> essentially</c><00:04:06.159><c> is</c>

00:04:06.309 --> 00:04:06.319 align:start position:0%
liquidity what can happen essentially is
 

00:04:06.319 --> 00:04:08.830 align:start position:0%
liquidity what can happen essentially is
that<00:04:06.799><c> one</c><00:04:06.959><c> of</c><00:04:07.079><c> the</c><00:04:07.200><c> leaves</c><00:04:07.760><c> of</c><00:04:08.000><c> this</c><00:04:08.400><c> Merkel</c>

00:04:08.830 --> 00:04:08.840 align:start position:0%
that one of the leaves of this Merkel
 

00:04:08.840 --> 00:04:10.869 align:start position:0%
that one of the leaves of this Merkel
tree<00:04:09.159><c> can</c><00:04:09.319><c> be</c><00:04:09.560><c> the</c><00:04:09.720><c> root</c><00:04:10.040><c> of</c><00:04:10.239><c> another</c><00:04:10.480><c> Merkel</c>

00:04:10.869 --> 00:04:10.879 align:start position:0%
tree can be the root of another Merkel
 

00:04:10.879 --> 00:04:13.390 align:start position:0%
tree can be the root of another Merkel
tree<00:04:11.599><c> and</c><00:04:11.760><c> then</c><00:04:12.040><c> one</c><00:04:12.280><c> node</c><00:04:12.680><c> can</c><00:04:12.879><c> commit</c><00:04:13.200><c> to</c>

00:04:13.390 --> 00:04:13.400 align:start position:0%
tree and then one node can commit to
 

00:04:13.400 --> 00:04:16.590 align:start position:0%
tree and then one node can commit to
another<00:04:13.760><c> so</c><00:04:13.959><c> essentially</c><00:04:14.439><c> this</c><00:04:14.519><c> is</c><00:04:15.000><c> a</c><00:04:16.000><c> data</c>

00:04:16.590 --> 00:04:16.600 align:start position:0%
another so essentially this is a data
 

00:04:16.600 --> 00:04:18.990 align:start position:0%
another so essentially this is a data
structure<00:04:17.160><c> for</c><00:04:17.359><c> a</c><00:04:17.560><c> new</c><00:04:17.840><c> type</c><00:04:18.000><c> of</c><00:04:18.199><c> transaction</c>

00:04:18.990 --> 00:04:19.000 align:start position:0%
structure for a new type of transaction
 

00:04:19.000 --> 00:04:21.870 align:start position:0%
structure for a new type of transaction
which<00:04:19.320><c> is</c><00:04:19.840><c> recursive</c><00:04:20.840><c> by</c><00:04:21.079><c> default</c><00:04:21.519><c> and</c><00:04:21.720><c> which</c>

00:04:21.870 --> 00:04:21.880 align:start position:0%
which is recursive by default and which
 

00:04:21.880 --> 00:04:24.150 align:start position:0%
which is recursive by default and which
has<00:04:22.199><c> multiple</c><00:04:22.720><c> elements</c><00:04:23.120><c> of</c><00:04:23.320><c> execution</c><00:04:23.880><c> by</c>

00:04:24.150 --> 00:04:24.160 align:start position:0%
has multiple elements of execution by
 

00:04:24.160 --> 00:04:27.230 align:start position:0%
has multiple elements of execution by
default<00:04:25.160><c> uh</c><00:04:25.320><c> we</c><00:04:25.440><c> are</c><00:04:25.680><c> trying</c><00:04:26.040><c> to</c><00:04:26.440><c> essentially</c>

00:04:27.230 --> 00:04:27.240 align:start position:0%
default uh we are trying to essentially
 

00:04:27.240 --> 00:04:30.830 align:start position:0%
default uh we are trying to essentially
push<00:04:27.600><c> this</c><00:04:27.759><c> to</c><00:04:28.000><c> become</c><00:04:29.000><c> the</c><00:04:29.800><c> one</c><00:04:29.960><c> of</c><00:04:30.120><c> the</c><00:04:30.320><c> main</c>

00:04:30.830 --> 00:04:30.840 align:start position:0%
push this to become the one of the main
 

00:04:30.840 --> 00:04:33.870 align:start position:0%
push this to become the one of the main
if<00:04:31.039><c> not</c><00:04:31.280><c> the</c><00:04:31.520><c> main</c><00:04:32.400><c> um</c><00:04:32.880><c> data</c><00:04:33.160><c> model</c><00:04:33.479><c> for</c>

00:04:33.870 --> 00:04:33.880 align:start position:0%
if not the main um data model for
 

00:04:33.880 --> 00:04:35.550 align:start position:0%
if not the main um data model for
transactions<00:04:34.479><c> within</c><00:04:34.680><c> a</c><00:04:34.800><c> chain</c><00:04:35.039><c> abstracted</c>

00:04:35.550 --> 00:04:35.560 align:start position:0%
transactions within a chain abstracted
 

00:04:35.560 --> 00:04:38.670 align:start position:0%
transactions within a chain abstracted
world<00:04:36.280><c> because</c><00:04:36.800><c> it</c><00:04:37.000><c> Bridges</c><00:04:37.479><c> gaps</c><00:04:37.880><c> between</c><00:04:38.560><c> uh</c>

00:04:38.670 --> 00:04:38.680 align:start position:0%
world because it Bridges gaps between uh
 

00:04:38.680 --> 00:04:40.390 align:start position:0%
world because it Bridges gaps between uh
so<00:04:38.960><c> like</c><00:04:39.120><c> the</c><00:04:39.240><c> leaf</c><00:04:39.560><c> can</c><00:04:39.680><c> be</c><00:04:39.840><c> a</c><00:04:39.960><c> Solana</c>

00:04:40.390 --> 00:04:40.400 align:start position:0%
so like the leaf can be a Solana
 

00:04:40.400 --> 00:04:41.670 align:start position:0%
so like the leaf can be a Solana
transaction<00:04:40.840><c> it</c><00:04:40.919><c> can</c><00:04:41.039><c> be</c><00:04:41.120><c> an</c><00:04:41.240><c> ethereum</c>

00:04:41.670 --> 00:04:41.680 align:start position:0%
transaction it can be an ethereum
 

00:04:41.680 --> 00:04:44.230 align:start position:0%
transaction it can be an ethereum
transaction<00:04:42.120><c> it</c><00:04:42.240><c> can</c><00:04:42.360><c> be</c><00:04:42.520><c> a</c><00:04:42.759><c> vasm</c><00:04:43.240><c> transaction</c>

00:04:44.230 --> 00:04:44.240 align:start position:0%
transaction it can be a vasm transaction
 

00:04:44.240 --> 00:04:46.070 align:start position:0%
transaction it can be a vasm transaction
uh<00:04:44.400><c> payment</c><00:04:44.800><c> can</c><00:04:44.960><c> be</c><00:04:45.240><c> like</c><00:04:45.360><c> an</c><00:04:45.520><c> onchain</c>

00:04:46.070 --> 00:04:46.080 align:start position:0%
uh payment can be like an onchain
 

00:04:46.080 --> 00:04:49.430 align:start position:0%
uh payment can be like an onchain
payment<00:04:46.440><c> it</c><00:04:46.560><c> can</c><00:04:46.720><c> be</c><00:04:46.840><c> an</c><00:04:47.039><c> offchain</c><00:04:47.919><c> payment</c><00:04:48.919><c> um</c>

00:04:49.430 --> 00:04:49.440 align:start position:0%
payment it can be an offchain payment um
 

00:04:49.440 --> 00:04:51.029 align:start position:0%
payment it can be an offchain payment um
offchain<00:04:49.919><c> actions</c><00:04:50.320><c> for</c><00:04:50.520><c> example</c><00:04:50.800><c> you</c><00:04:50.919><c> can</c>

00:04:51.029 --> 00:04:51.039 align:start position:0%
offchain actions for example you can
 

00:04:51.039 --> 00:04:53.909 align:start position:0%
offchain actions for example you can
trigger<00:04:51.600><c> a</c><00:04:51.800><c> call</c><00:04:52.080><c> to</c><00:04:52.199><c> some</c><00:04:52.440><c> API</c><00:04:53.080><c> then</c><00:04:53.440><c> require</c>

00:04:53.909 --> 00:04:53.919 align:start position:0%
trigger a call to some API then require
 

00:04:53.919 --> 00:04:56.430 align:start position:0%
trigger a call to some API then require
this<00:04:54.080><c> to</c><00:04:54.280><c> generate</c><00:04:54.639><c> a</c><00:04:54.800><c> ZK</c><00:04:55.120><c> TLS</c><00:04:55.639><c> proof</c><00:04:56.280><c> that</c>

00:04:56.430 --> 00:04:56.440 align:start position:0%
this to generate a ZK TLS proof that
 

00:04:56.440 --> 00:04:58.310 align:start position:0%
this to generate a ZK TLS proof that
something<00:04:56.720><c> has</c><00:04:56.840><c> been</c><00:04:57.039><c> executed</c><00:04:57.520><c> so</c><00:04:57.680><c> it's</c><00:04:58.080><c> very</c>

00:04:58.310 --> 00:04:58.320 align:start position:0%
something has been executed so it's very
 

00:04:58.320 --> 00:05:01.230 align:start position:0%
something has been executed so it's very
extensible<00:04:58.919><c> very</c><00:04:59.120><c> modular</c><00:04:59.960><c> it</c><00:05:00.440><c> uh</c><00:05:00.759><c> really</c>

00:05:01.230 --> 00:05:01.240 align:start position:0%
extensible very modular it uh really
 

00:05:01.240 --> 00:05:03.469 align:start position:0%
extensible very modular it uh really
effortlessly<00:05:01.880><c> achieves</c><00:05:02.720><c> all</c><00:05:03.000><c> the</c><00:05:03.120><c> elements</c>

00:05:03.469 --> 00:05:03.479 align:start position:0%
effortlessly achieves all the elements
 

00:05:03.479 --> 00:05:05.749 align:start position:0%
effortlessly achieves all the elements
of<00:05:03.600><c> chain</c><00:05:03.880><c> abstraction</c><00:05:04.479><c> like</c><00:05:04.880><c> uh</c><00:05:05.440><c> gas</c>

00:05:05.749 --> 00:05:05.759 align:start position:0%
of chain abstraction like uh gas
 

00:05:05.759 --> 00:05:07.830 align:start position:0%
of chain abstraction like uh gas
abstraction<00:05:06.400><c> single</c><00:05:06.759><c> signature</c><00:05:07.199><c> multi-chain</c>

00:05:07.830 --> 00:05:07.840 align:start position:0%
abstraction single signature multi-chain
 

00:05:07.840 --> 00:05:10.070 align:start position:0%
abstraction single signature multi-chain
stuff<00:05:08.720><c> um</c><00:05:08.919><c> and</c><00:05:09.120><c> yeah</c><00:05:09.360><c> also</c><00:05:09.720><c> what</c><00:05:09.840><c> we</c><00:05:09.960><c> are</c>

00:05:10.070 --> 00:05:10.080 align:start position:0%
stuff um and yeah also what we are
 

00:05:10.080 --> 00:05:12.270 align:start position:0%
stuff um and yeah also what we are
building<00:05:10.560><c> is</c><00:05:10.919><c> a</c><00:05:11.280><c> modular</c><00:05:11.759><c> execution</c>

00:05:12.270 --> 00:05:12.280 align:start position:0%
building is a modular execution
 

00:05:12.280 --> 00:05:14.590 align:start position:0%
building is a modular execution
environment<00:05:13.240><c> U</c><00:05:13.639><c> which</c><00:05:13.759><c> is</c><00:05:13.840><c> a</c><00:05:14.000><c> permissionless</c>

00:05:14.590 --> 00:05:14.600 align:start position:0%
environment U which is a permissionless
 

00:05:14.600 --> 00:05:16.270 align:start position:0%
environment U which is a permissionless
execution<00:05:15.039><c> layer</c><00:05:15.280><c> for</c><00:05:15.440><c> all</c><00:05:15.560><c> of</c><00:05:15.759><c> this</c><00:05:16.039><c> but</c><00:05:16.160><c> you</c>

00:05:16.270 --> 00:05:16.280 align:start position:0%
execution layer for all of this but you
 

00:05:16.280 --> 00:05:17.670 align:start position:0%
execution layer for all of this but you
know<00:05:16.479><c> I</c><00:05:16.560><c> wanted</c><00:05:16.759><c> to</c><00:05:16.880><c> keep</c><00:05:17.080><c> this</c><00:05:17.240><c> Technical</c><00:05:17.560><c> and</c>

00:05:17.670 --> 00:05:17.680 align:start position:0%
know I wanted to keep this Technical and
 

00:05:17.680 --> 00:05:20.749 align:start position:0%
know I wanted to keep this Technical and
not<00:05:17.800><c> Shilling</c><00:05:18.160><c> our</c><00:05:18.280><c> own</c><00:05:18.479><c> things</c><00:05:18.840><c> so</c><00:05:19.759><c> um</c><00:05:20.160><c> yeah</c>

00:05:20.749 --> 00:05:20.759 align:start position:0%
not Shilling our own things so um yeah
 

00:05:20.759 --> 00:05:22.749 align:start position:0%
not Shilling our own things so um yeah
um<00:05:21.120><c> this</c><00:05:21.240><c> is</c><00:05:21.360><c> it</c><00:05:21.520><c> for</c><00:05:21.759><c> super</c><00:05:22.080><c> transactions</c><00:05:22.600><c> and</c>

00:05:22.749 --> 00:05:22.759 align:start position:0%
um this is it for super transactions and
 

00:05:22.759 --> 00:05:27.469 align:start position:0%
um this is it for super transactions and
modular<00:05:23.160><c> execution</c>

00:05:27.469 --> 00:05:27.479 align:start position:0%
 
 

00:05:27.479 --> 00:05:30.350 align:start position:0%
 
environments<00:05:28.479><c> thank</c><00:05:28.639><c> you</c><00:05:28.800><c> m</c>

00:05:30.350 --> 00:05:30.360 align:start position:0%
environments thank you m
 

00:05:30.360 --> 00:05:32.629 align:start position:0%
environments thank you m
and<00:05:30.680><c> now</c><00:05:30.840><c> we</c><00:05:30.960><c> have</c><00:05:31.120><c> time</c><00:05:31.319><c> for</c><00:05:31.759><c> questions</c><00:05:32.400><c> raise</c>

00:05:32.629 --> 00:05:32.639 align:start position:0%
and now we have time for questions raise
 

00:05:32.639 --> 00:05:35.189 align:start position:0%
and now we have time for questions raise
your<00:05:32.800><c> hand</c><00:05:33.319><c> if</c><00:05:33.520><c> you</c><00:05:33.800><c> have</c><00:05:34.120><c> a</c><00:05:34.440><c> question</c><00:05:34.880><c> I</c><00:05:35.039><c> know</c>

00:05:35.189 --> 00:05:35.199 align:start position:0%
your hand if you have a question I know
 

00:05:35.199 --> 00:05:38.950 align:start position:0%
your hand if you have a question I know
you<00:05:35.360><c> do</c><00:05:36.199><c> don't</c><00:05:36.440><c> be</c>

00:05:38.950 --> 00:05:38.960 align:start position:0%
 
 

00:05:38.960 --> 00:05:42.070 align:start position:0%
 
shy<00:05:39.960><c> yes</c><00:05:40.520><c> all</c><00:05:40.720><c> right</c><00:05:41.039><c> so</c><00:05:41.199><c> I'm</c><00:05:41.319><c> GNA</c><00:05:41.639><c> throw</c><00:05:41.919><c> you</c>

00:05:42.070 --> 00:05:42.080 align:start position:0%
shy yes all right so I'm GNA throw you
 

00:05:42.080 --> 00:05:45.670 align:start position:0%
shy yes all right so I'm GNA throw you
the<00:05:42.199><c> box</c><00:05:42.520><c> get</c><00:05:42.720><c> ready</c><00:05:42.919><c> to</c><00:05:43.160><c> catch</c><00:05:43.400><c> it</c><00:05:43.720><c> yeah</c><00:05:44.600><c> and</c>

00:05:45.670 --> 00:05:45.680 align:start position:0%
the box get ready to catch it yeah and
 

00:05:45.680 --> 00:05:49.629 align:start position:0%
the box get ready to catch it yeah and
go<00:05:46.680><c> okay</c><00:05:47.680><c> uh</c><00:05:48.120><c> how</c><00:05:48.280><c> do</c><00:05:48.400><c> you</c><00:05:48.600><c> ensure</c><00:05:49.199><c> like</c>

00:05:49.629 --> 00:05:49.639 align:start position:0%
go okay uh how do you ensure like
 

00:05:49.639 --> 00:05:51.749 align:start position:0%
go okay uh how do you ensure like
transaction<00:05:50.199><c> atomicity</c><00:05:50.919><c> in</c><00:05:51.000><c> a</c><00:05:51.160><c> multichain</c>

00:05:51.749 --> 00:05:51.759 align:start position:0%
transaction atomicity in a multichain
 

00:05:51.759 --> 00:05:54.590 align:start position:0%
transaction atomicity in a multichain
environment<00:05:52.479><c> let's</c><00:05:52.720><c> say</c><00:05:53.639><c> uh</c><00:05:54.000><c> you</c><00:05:54.160><c> did</c><00:05:54.440><c> a</c>

00:05:54.590 --> 00:05:54.600 align:start position:0%
environment let's say uh you did a
 

00:05:54.600 --> 00:05:57.909 align:start position:0%
environment let's say uh you did a
transaction<00:05:55.000><c> on</c><00:05:55.199><c> optimism</c><00:05:56.120><c> and</c><00:05:56.600><c> Main</c><00:05:57.600><c> and</c>

00:05:57.909 --> 00:05:57.919 align:start position:0%
transaction on optimism and Main and
 

00:05:57.919 --> 00:06:00.830 align:start position:0%
transaction on optimism and Main and
then<00:05:58.319><c> something</c><00:05:58.639><c> happened</c><00:05:58.880><c> to</c><00:05:59.039><c> op</c><00:05:59.840><c> optimism</c>

00:06:00.830 --> 00:06:00.840 align:start position:0%
then something happened to op optimism
 

00:06:00.840 --> 00:06:03.309 align:start position:0%
then something happened to op optimism
and<00:06:01.560><c> someone</c><00:06:01.919><c> claimed</c><00:06:02.319><c> that</c><00:06:02.440><c> the</c><00:06:02.600><c> rollup</c><00:06:03.080><c> was</c>

00:06:03.309 --> 00:06:03.319 align:start position:0%
and someone claimed that the rollup was
 

00:06:03.319 --> 00:06:06.790 align:start position:0%
and someone claimed that the rollup was
faulty<00:06:03.840><c> and</c><00:06:04.520><c> the</c><00:06:05.199><c> block</c><00:06:05.639><c> reverted</c><00:06:06.639><c> what</c>

00:06:06.790 --> 00:06:06.800 align:start position:0%
faulty and the block reverted what
 

00:06:06.800 --> 00:06:08.710 align:start position:0%
faulty and the block reverted what
happens<00:06:07.120><c> to</c><00:06:07.319><c> the</c><00:06:07.880><c> transaction</c><00:06:08.440><c> which</c><00:06:08.560><c> was</c>

00:06:08.710 --> 00:06:08.720 align:start position:0%
happens to the transaction which was
 

00:06:08.720 --> 00:06:11.909 align:start position:0%
happens to the transaction which was
settled<00:06:09.479><c> before</c><00:06:10.479><c> so</c><00:06:10.840><c> the</c><00:06:11.400><c> um</c><00:06:11.599><c> super</c>

00:06:11.909 --> 00:06:11.919 align:start position:0%
settled before so the um super
 

00:06:11.919 --> 00:06:13.270 align:start position:0%
settled before so the um super
transactions<00:06:12.360><c> and</c><00:06:12.520><c> modular</c><00:06:12.880><c> execution</c>

00:06:13.270 --> 00:06:13.280 align:start position:0%
transactions and modular execution
 

00:06:13.280 --> 00:06:15.589 align:start position:0%
transactions and modular execution
environments<00:06:13.720><c> are</c><00:06:13.919><c> just</c><00:06:14.199><c> technical</c><00:06:14.639><c> Concepts</c>

00:06:15.589 --> 00:06:15.599 align:start position:0%
environments are just technical Concepts
 

00:06:15.599 --> 00:06:17.670 align:start position:0%
environments are just technical Concepts
They<00:06:15.759><c> Don't</c><00:06:16.080><c> Really</c><00:06:16.880><c> guarantee</c><00:06:17.319><c> or</c><00:06:17.479><c> not</c>

00:06:17.670 --> 00:06:17.680 align:start position:0%
They Don't Really guarantee or not
 

00:06:17.680 --> 00:06:21.070 align:start position:0%
They Don't Really guarantee or not
guarantee<00:06:18.080><c> atomicity</c><00:06:18.919><c> so</c><00:06:19.919><c> a</c><00:06:20.440><c> example</c><00:06:20.840><c> of</c><00:06:20.960><c> a</c>

00:06:21.070 --> 00:06:21.080 align:start position:0%
guarantee atomicity so a example of a
 

00:06:21.080 --> 00:06:22.950 align:start position:0%
guarantee atomicity so a example of a
modular<00:06:21.479><c> execution</c><00:06:21.919><c> environment</c><00:06:22.440><c> can</c><00:06:22.599><c> be</c><00:06:22.759><c> one</c>

00:06:22.950 --> 00:06:22.960 align:start position:0%
modular execution environment can be one
 

00:06:22.960 --> 00:06:25.510 align:start position:0%
modular execution environment can be one
which<00:06:23.120><c> guarantees</c><00:06:23.599><c> atomicity</c><00:06:24.560><c> so</c><00:06:24.919><c> we</c><00:06:25.160><c> are</c>

00:06:25.510 --> 00:06:25.520 align:start position:0%
which guarantees atomicity so we are
 

00:06:25.520 --> 00:06:28.150 align:start position:0%
which guarantees atomicity so we are
currently<00:06:26.039><c> working</c><00:06:26.599><c> with</c><00:06:27.280><c> uh</c><00:06:27.440><c> certain</c><00:06:27.840><c> block</c>

00:06:28.150 --> 00:06:28.160 align:start position:0%
currently working with uh certain block
 

00:06:28.160 --> 00:06:30.469 align:start position:0%
currently working with uh certain block
Builders<00:06:28.639><c> who</c><00:06:28.800><c> can</c><00:06:28.960><c> like</c><00:06:29.120><c> build</c><00:06:29.599><c> blocks</c><00:06:30.280><c> on</c>

00:06:30.469 --> 00:06:30.479 align:start position:0%
Builders who can like build blocks on
 

00:06:30.479 --> 00:06:32.110 align:start position:0%
Builders who can like build blocks on
top<00:06:30.639><c> of</c><00:06:30.800><c> multiple</c><00:06:31.160><c> blockchains</c><00:06:31.639><c> at</c><00:06:31.759><c> the</c><00:06:31.880><c> same</c>

00:06:32.110 --> 00:06:32.120 align:start position:0%
top of multiple blockchains at the same
 

00:06:32.120 --> 00:06:33.510 align:start position:0%
top of multiple blockchains at the same
time<00:06:32.639><c> so</c><00:06:32.800><c> you</c><00:06:32.880><c> can</c><00:06:33.080><c> get</c><00:06:33.280><c> like</c><00:06:33.400><c> a</c>

00:06:33.510 --> 00:06:33.520 align:start position:0%
time so you can get like a
 

00:06:33.520 --> 00:06:35.150 align:start position:0%
time so you can get like a
pre-confirmation<00:06:34.039><c> whether</c><00:06:34.639><c> or</c><00:06:34.800><c> not</c><00:06:35.000><c> it's</c>

00:06:35.150 --> 00:06:35.160 align:start position:0%
pre-confirmation whether or not it's
 

00:06:35.160 --> 00:06:36.870 align:start position:0%
pre-confirmation whether or not it's
going<00:06:35.240><c> to</c><00:06:35.400><c> get</c><00:06:35.560><c> executed</c><00:06:36.120><c> everywhere</c><00:06:36.560><c> or</c>

00:06:36.870 --> 00:06:36.880 align:start position:0%
going to get executed everywhere or
 

00:06:36.880 --> 00:06:39.150 align:start position:0%
going to get executed everywhere or
nowhere<00:06:37.880><c> um</c><00:06:38.120><c> a</c><00:06:38.199><c> lot</c><00:06:38.319><c> of</c><00:06:38.479><c> things</c><00:06:38.680><c> don't</c><00:06:38.919><c> really</c>

00:06:39.150 --> 00:06:39.160 align:start position:0%
nowhere um a lot of things don't really
 

00:06:39.160 --> 00:06:41.350 align:start position:0%
nowhere um a lot of things don't really
require<00:06:39.599><c> this</c><00:06:39.720><c> type</c><00:06:39.880><c> of</c><00:06:40.000><c> hard</c><00:06:40.240><c> atomicity</c><00:06:41.199><c> like</c>

00:06:41.350 --> 00:06:41.360 align:start position:0%
require this type of hard atomicity like
 

00:06:41.360 --> 00:06:43.189 align:start position:0%
require this type of hard atomicity like
for<00:06:41.560><c> example</c><00:06:42.000><c> this</c><00:06:42.280><c> case</c><00:06:42.520><c> that</c><00:06:42.639><c> I</c><00:06:42.759><c> said</c><00:06:42.960><c> with</c>

00:06:43.189 --> 00:06:43.199 align:start position:0%
for example this case that I said with
 

00:06:43.199 --> 00:06:45.550 align:start position:0%
for example this case that I said with
AA<00:06:43.520><c> like</c><00:06:43.680><c> the</c><00:06:43.800><c> worst</c><00:06:44.080><c> case</c><00:06:44.360><c> if</c><00:06:44.759><c> a</c><00:06:45.000><c> piece</c><00:06:45.199><c> of</c><00:06:45.319><c> the</c>

00:06:45.550 --> 00:06:45.560 align:start position:0%
AA like the worst case if a piece of the
 

00:06:45.560 --> 00:06:47.510 align:start position:0%
AA like the worst case if a piece of the
transaction<00:06:45.919><c> fails</c><00:06:46.240><c> you'll</c><00:06:46.479><c> just</c><00:06:46.919><c> retry</c><00:06:47.400><c> the</c>

00:06:47.510 --> 00:06:47.520 align:start position:0%
transaction fails you'll just retry the
 

00:06:47.520 --> 00:06:49.150 align:start position:0%
transaction fails you'll just retry the
transaction<00:06:47.960><c> on</c><00:06:48.120><c> the</c><00:06:48.240><c> destination</c><00:06:48.680><c> chain</c><00:06:49.000><c> and</c>

00:06:49.150 --> 00:06:49.160 align:start position:0%
transaction on the destination chain and
 

00:06:49.160 --> 00:06:50.790 align:start position:0%
transaction on the destination chain and
then<00:06:49.400><c> so</c><00:06:49.599><c> even</c><00:06:49.840><c> like</c><00:06:49.960><c> a</c><00:06:50.039><c> super</c><00:06:50.319><c> transaction</c>

00:06:50.790 --> 00:06:50.800 align:start position:0%
then so even like a super transaction
 

00:06:50.800 --> 00:06:52.950 align:start position:0%
then so even like a super transaction
can<00:06:51.000><c> contain</c><00:06:51.360><c> also</c><00:06:51.599><c> retry</c><00:06:52.039><c> instructions</c><00:06:52.800><c> so</c>

00:06:52.950 --> 00:06:52.960 align:start position:0%
can contain also retry instructions so
 

00:06:52.960 --> 00:06:55.189 align:start position:0%
can contain also retry instructions so
you<00:06:53.039><c> can</c><00:06:53.280><c> pre</c><00:06:53.759><c> sign</c><00:06:54.240><c> all</c><00:06:54.400><c> of</c><00:06:54.520><c> the</c><00:06:54.639><c> retry</c>

00:06:55.189 --> 00:06:55.199 align:start position:0%
you can pre sign all of the retry
 

00:06:55.199 --> 00:06:57.830 align:start position:0%
you can pre sign all of the retry
instructions<00:06:56.080><c> that</c><00:06:56.280><c> that</c><00:06:56.440><c> are</c><00:06:56.639><c> needed</c><00:06:57.520><c> uh</c><00:06:57.639><c> in</c>

00:06:57.830 --> 00:06:57.840 align:start position:0%
instructions that that are needed uh in
 

00:06:57.840 --> 00:07:00.670 align:start position:0%
instructions that that are needed uh in
our<00:06:58.240><c> experience</c><00:06:58.879><c> like</c><00:06:59.120><c> n</c>

00:07:00.670 --> 00:07:00.680 align:start position:0%
our experience like n
 

00:07:00.680 --> 00:07:04.070 align:start position:0%
our experience like n
99%<00:07:01.680><c> of</c><00:07:01.960><c> everything</c><00:07:02.400><c> goes</c><00:07:02.680><c> through</c><00:07:03.680><c> uh</c><00:07:03.879><c> but</c>

00:07:04.070 --> 00:07:04.080 align:start position:0%
99% of everything goes through uh but
 

00:07:04.080 --> 00:07:05.869 align:start position:0%
99% of everything goes through uh but
yeah<00:07:04.280><c> for</c><00:07:04.639><c> certain</c><00:07:05.039><c> cases</c><00:07:05.400><c> let's</c><00:07:05.599><c> call</c><00:07:05.759><c> it</c>

00:07:05.869 --> 00:07:05.879 align:start position:0%
yeah for certain cases let's call it
 

00:07:05.879 --> 00:07:08.230 align:start position:0%
yeah for certain cases let's call it
maybe<00:07:06.199><c> trading</c><00:07:06.680><c> or</c><00:07:06.919><c> or</c><00:07:07.039><c> defi</c><00:07:07.560><c> positions</c><00:07:08.000><c> where</c>

00:07:08.230 --> 00:07:08.240 align:start position:0%
maybe trading or or defi positions where
 

00:07:08.240 --> 00:07:10.869 align:start position:0%
maybe trading or or defi positions where
like<00:07:09.240><c> maybe</c><00:07:09.440><c> you</c><00:07:09.520><c> want</c><00:07:09.639><c> to</c><00:07:09.800><c> do</c><00:07:10.039><c> a</c><00:07:10.319><c> cross</c><00:07:10.639><c> chain</c>

00:07:10.869 --> 00:07:10.879 align:start position:0%
like maybe you want to do a cross chain
 

00:07:10.879 --> 00:07:12.629 align:start position:0%
like maybe you want to do a cross chain
flash<00:07:11.240><c> loan</c><00:07:11.520><c> or</c><00:07:11.680><c> something</c><00:07:12.000><c> like</c><00:07:12.199><c> that</c><00:07:12.440><c> where</c>

00:07:12.629 --> 00:07:12.639 align:start position:0%
flash loan or something like that where
 

00:07:12.639 --> 00:07:15.550 align:start position:0%
flash loan or something like that where
atomicity<00:07:13.240><c> is</c><00:07:13.400><c> very</c><00:07:13.599><c> important</c><00:07:14.599><c> there</c><00:07:14.879><c> we</c><00:07:15.039><c> are</c>

00:07:15.550 --> 00:07:15.560 align:start position:0%
atomicity is very important there we are
 

00:07:15.560 --> 00:07:17.589 align:start position:0%
atomicity is very important there we are
already<00:07:15.800><c> in</c><00:07:16.000><c> active</c><00:07:16.560><c> conversations</c><00:07:17.199><c> with</c>

00:07:17.589 --> 00:07:17.599 align:start position:0%
already in active conversations with
 

00:07:17.599 --> 00:07:19.629 align:start position:0%
already in active conversations with
certain<00:07:17.960><c> projects</c><00:07:18.360><c> which</c><00:07:18.520><c> do</c><00:07:18.759><c> like</c><00:07:19.360><c> block</c>

00:07:19.629 --> 00:07:19.639 align:start position:0%
certain projects which do like block
 

00:07:19.639 --> 00:07:21.710 align:start position:0%
certain projects which do like block
building<00:07:20.240><c> on</c><00:07:20.440><c> top</c><00:07:20.599><c> of</c><00:07:20.720><c> multiple</c><00:07:21.080><c> rollups</c><00:07:21.599><c> at</c>

00:07:21.710 --> 00:07:21.720 align:start position:0%
building on top of multiple rollups at
 

00:07:21.720 --> 00:07:23.029 align:start position:0%
building on top of multiple rollups at
the<00:07:21.840><c> same</c><00:07:22.039><c> time</c><00:07:22.240><c> and</c><00:07:22.400><c> then</c><00:07:22.800><c> yeah</c><00:07:22.879><c> you</c>

00:07:23.029 --> 00:07:23.039 align:start position:0%
the same time and then yeah you
 

00:07:23.039 --> 00:07:26.189 align:start position:0%
the same time and then yeah you
basically<00:07:23.400><c> get</c><00:07:23.639><c> a</c><00:07:24.319><c> pre-commitment</c><00:07:25.160><c> to</c><00:07:25.319><c> to</c>

00:07:26.189 --> 00:07:26.199 align:start position:0%
basically get a pre-commitment to to
 

00:07:26.199 --> 00:07:28.029 align:start position:0%
basically get a pre-commitment to to
inclusion<00:07:26.759><c> of</c><00:07:26.960><c> all</c><00:07:27.120><c> of</c><00:07:27.280><c> the</c><00:07:27.479><c> transactions</c>

00:07:28.029 --> 00:07:28.039 align:start position:0%
inclusion of all of the transactions
 

00:07:28.039 --> 00:07:31.110 align:start position:0%
inclusion of all of the transactions
within<00:07:28.360><c> the</c><00:07:28.599><c> super</c><00:07:28.919><c> transaction</c><00:07:29.319><c> hash</c>

00:07:31.110 --> 00:07:31.120 align:start position:0%
within the super transaction hash
 

00:07:31.120 --> 00:07:33.270 align:start position:0%
within the super transaction hash
right<00:07:31.400><c> thanks</c><00:07:32.400><c> we</c><00:07:32.520><c> already</c><00:07:32.800><c> have</c><00:07:33.039><c> another</c>

00:07:33.270 --> 00:07:33.280 align:start position:0%
right thanks we already have another
 

00:07:33.280 --> 00:07:36.390 align:start position:0%
right thanks we already have another
question<00:07:33.520><c> lined</c><00:07:34.240><c> up</c><00:07:35.240><c> uh</c><00:07:35.599><c> yeah</c><00:07:35.800><c> my</c><00:07:36.039><c> question</c>

00:07:36.390 --> 00:07:36.400 align:start position:0%
question lined up uh yeah my question
 

00:07:36.400 --> 00:07:39.390 align:start position:0%
question lined up uh yeah my question
actually<00:07:36.759><c> was</c><00:07:37.280><c> the</c><00:07:37.479><c> same</c><00:07:38.120><c> uh</c><00:07:38.319><c> as</c><00:07:38.800><c> about</c>

00:07:39.390 --> 00:07:39.400 align:start position:0%
actually was the same uh as about
 

00:07:39.400 --> 00:07:43.230 align:start position:0%
actually was the same uh as about
atomicity<00:07:40.400><c> so</c><00:07:41.039><c> in</c><00:07:41.240><c> general</c><00:07:41.759><c> it's</c><00:07:42.440><c> U</c><00:07:42.960><c> like</c>

00:07:43.230 --> 00:07:43.240 align:start position:0%
atomicity so in general it's U like
 

00:07:43.240 --> 00:07:46.070 align:start position:0%
atomicity so in general it's U like
convenient<00:07:43.919><c> way</c><00:07:44.240><c> to</c><00:07:45.240><c> uh</c><00:07:45.520><c> put</c><00:07:45.840><c> all</c>

00:07:46.070 --> 00:07:46.080 align:start position:0%
convenient way to uh put all
 

00:07:46.080 --> 00:07:49.670 align:start position:0%
convenient way to uh put all
transactions<00:07:46.960><c> together</c><00:07:47.759><c> and</c><00:07:48.479><c> uh</c><00:07:48.639><c> do</c><00:07:48.800><c> you</c><00:07:49.080><c> have</c>

00:07:49.670 --> 00:07:49.680 align:start position:0%
transactions together and uh do you have
 

00:07:49.680 --> 00:07:54.350 align:start position:0%
transactions together and uh do you have
some<00:07:50.039><c> ways</c><00:07:50.840><c> to</c><00:07:51.840><c> uh</c><00:07:52.360><c> prescribe</c><00:07:53.360><c> uh</c><00:07:53.560><c> sequence</c><00:07:54.120><c> of</c>

00:07:54.350 --> 00:07:54.360 align:start position:0%
some ways to uh prescribe uh sequence of
 

00:07:54.360 --> 00:07:57.230 align:start position:0%
some ways to uh prescribe uh sequence of
transactions<00:07:54.960><c> so</c><00:07:55.199><c> let's</c><00:07:55.520><c> say</c><00:07:56.520><c> uh</c><00:07:57.000><c> this</c>

00:07:57.230 --> 00:07:57.240 align:start position:0%
transactions so let's say uh this
 

00:07:57.240 --> 00:08:00.029 align:start position:0%
transactions so let's say uh this
transaction<00:07:57.919><c> should</c><00:07:58.280><c> happen</c><00:07:58.960><c> before</c><00:07:59.840><c> this</c>

00:08:00.029 --> 00:08:00.039 align:start position:0%
transaction should happen before this
 

00:08:00.039 --> 00:08:04.670 align:start position:0%
transaction should happen before this
one<00:08:00.520><c> or</c><00:08:01.639><c> some</c><00:08:02.639><c> mechanisms</c><00:08:03.240><c> like</c><00:08:03.479><c> this</c><00:08:04.240><c> so</c><00:08:04.479><c> in</c>

00:08:04.670 --> 00:08:04.680 align:start position:0%
one or some mechanisms like this so in
 

00:08:04.680 --> 00:08:07.909 align:start position:0%
one or some mechanisms like this so in
general<00:08:05.400><c> they</c><00:08:05.560><c> are</c><00:08:05.879><c> sequenced</c><00:08:06.560><c> by</c><00:08:06.720><c> default</c><00:08:07.440><c> um</c>

00:08:07.909 --> 00:08:07.919 align:start position:0%
general they are sequenced by default um
 

00:08:07.919 --> 00:08:11.670 align:start position:0%
general they are sequenced by default um
so<00:08:08.800><c> a</c><00:08:09.400><c> node</c><00:08:09.840><c> will</c><00:08:10.039><c> not</c><00:08:10.360><c> execute</c><00:08:10.759><c> a</c><00:08:10.919><c> transaction</c>

00:08:11.670 --> 00:08:11.680 align:start position:0%
so a node will not execute a transaction
 

00:08:11.680 --> 00:08:14.029 align:start position:0%
so a node will not execute a transaction
if<00:08:12.000><c> it</c><00:08:12.199><c> simulates</c><00:08:12.680><c> a</c><00:08:12.840><c> revert</c><00:08:13.599><c> and</c><00:08:13.720><c> also</c><00:08:13.960><c> there</c>

00:08:14.029 --> 00:08:14.039 align:start position:0%
if it simulates a revert and also there
 

00:08:14.039 --> 00:08:15.790 align:start position:0%
if it simulates a revert and also there
is<00:08:14.199><c> like</c><00:08:14.360><c> this</c><00:08:14.520><c> entire</c><00:08:14.840><c> trustless</c><00:08:15.319><c> protocol</c>

00:08:15.790 --> 00:08:15.800 align:start position:0%
is like this entire trustless protocol
 

00:08:15.800 --> 00:08:17.390 align:start position:0%
is like this entire trustless protocol
with<00:08:15.960><c> staking</c><00:08:16.280><c> and</c><00:08:16.400><c> slashing</c><00:08:16.879><c> that</c><00:08:17.120><c> actually</c>

00:08:17.390 --> 00:08:17.400 align:start position:0%
with staking and slashing that actually
 

00:08:17.400 --> 00:08:19.390 align:start position:0%
with staking and slashing that actually
ensures<00:08:17.800><c> the</c><00:08:17.919><c> liveness</c><00:08:18.319><c> of</c><00:08:18.440><c> all</c><00:08:18.560><c> of</c><00:08:18.720><c> this</c><00:08:19.240><c> but</c>

00:08:19.390 --> 00:08:19.400 align:start position:0%
ensures the liveness of all of this but
 

00:08:19.400 --> 00:08:21.230 align:start position:0%
ensures the liveness of all of this but
let's<00:08:19.599><c> call</c><00:08:19.759><c> it</c><00:08:20.000><c> like</c><00:08:20.199><c> if</c><00:08:20.319><c> you</c><00:08:20.440><c> are</c><00:08:20.720><c> bridging</c>

00:08:21.230 --> 00:08:21.240 align:start position:0%
let's call it like if you are bridging
 

00:08:21.240 --> 00:08:24.029 align:start position:0%
let's call it like if you are bridging
to<00:08:21.960><c> base</c><00:08:22.440><c> and</c><00:08:22.720><c> like</c><00:08:22.960><c> the</c><00:08:23.080><c> transaction</c><00:08:23.599><c> on</c><00:08:23.759><c> base</c>

00:08:24.029 --> 00:08:24.039 align:start position:0%
to base and like the transaction on base
 

00:08:24.039 --> 00:08:27.149 align:start position:0%
to base and like the transaction on base
requires<00:08:24.520><c> 10</c><00:08:24.960><c> 100</c><00:08:25.400><c> usdc</c><00:08:26.400><c> until</c><00:08:26.680><c> you</c><00:08:26.840><c> have</c><00:08:27.000><c> a</c>

00:08:27.149 --> 00:08:27.159 align:start position:0%
requires 10 100 usdc until you have a
 

00:08:27.159 --> 00:08:29.670 align:start position:0%
requires 10 100 usdc until you have a
100<00:08:27.440><c> usdc</c><00:08:27.960><c> on</c><00:08:28.159><c> base</c><00:08:28.599><c> like</c><00:08:28.720><c> it</c><00:08:28.840><c> will</c><00:08:29.039><c> not</c><00:08:29.599><c> the</c>

00:08:29.670 --> 00:08:29.680 align:start position:0%
100 usdc on base like it will not the
 

00:08:29.680 --> 00:08:31.270 align:start position:0%
100 usdc on base like it will not the
node<00:08:29.919><c> itself</c><00:08:30.159><c> will</c><00:08:30.319><c> not</c><00:08:30.560><c> execute</c><00:08:30.960><c> that</c><00:08:31.120><c> piece</c>

00:08:31.270 --> 00:08:31.280 align:start position:0%
node itself will not execute that piece
 

00:08:31.280 --> 00:08:33.389 align:start position:0%
node itself will not execute that piece
of<00:08:31.360><c> the</c><00:08:31.520><c> transaction</c><00:08:32.519><c> the</c><00:08:32.680><c> secondary</c><00:08:33.200><c> part</c>

00:08:33.389 --> 00:08:33.399 align:start position:0%
of the transaction the secondary part
 

00:08:33.399 --> 00:08:35.190 align:start position:0%
of the transaction the secondary part
which<00:08:33.560><c> you</c><00:08:33.640><c> can</c><00:08:33.839><c> do</c><00:08:34.200><c> is</c><00:08:34.440><c> you</c><00:08:34.560><c> can</c><00:08:34.760><c> set</c>

00:08:35.190 --> 00:08:35.200 align:start position:0%
which you can do is you can set
 

00:08:35.200 --> 00:08:37.389 align:start position:0%
which you can do is you can set
conditions<00:08:35.479><c> with</c><00:08:35.640><c> onchain</c><00:08:36.120><c> variables</c><00:08:36.959><c> so</c><00:08:37.159><c> for</c>

00:08:37.389 --> 00:08:37.399 align:start position:0%
conditions with onchain variables so for
 

00:08:37.399 --> 00:08:40.750 align:start position:0%
conditions with onchain variables so for
example<00:08:38.159><c> let's</c><00:08:38.399><c> call</c><00:08:38.599><c> it</c><00:08:39.080><c> um</c><00:08:39.680><c> transaction</c><00:08:40.399><c> on</c>

00:08:40.750 --> 00:08:40.760 align:start position:0%
example let's call it um transaction on
 

00:08:40.760 --> 00:08:43.509 align:start position:0%
example let's call it um transaction on
optimism<00:08:41.399><c> triggers</c><00:08:42.080><c> a</c><00:08:42.440><c> cross</c><00:08:42.719><c> chain</c><00:08:43.039><c> message</c>

00:08:43.509 --> 00:08:43.519 align:start position:0%
optimism triggers a cross chain message
 

00:08:43.519 --> 00:08:45.990 align:start position:0%
optimism triggers a cross chain message
onto<00:08:43.959><c> base</c><00:08:44.680><c> which</c><00:08:44.920><c> updates</c><00:08:45.320><c> an</c><00:08:45.519><c> onchain</c>

00:08:45.990 --> 00:08:46.000 align:start position:0%
onto base which updates an onchain
 

00:08:46.000 --> 00:08:47.870 align:start position:0%
onto base which updates an onchain
variable<00:08:46.640><c> which</c><00:08:46.880><c> gives</c><00:08:47.200><c> permission</c><00:08:47.560><c> to</c><00:08:47.720><c> the</c>

00:08:47.870 --> 00:08:47.880 align:start position:0%
variable which gives permission to the
 

00:08:47.880 --> 00:08:51.230 align:start position:0%
variable which gives permission to the
second<00:08:48.200><c> transaction</c><00:08:48.680><c> in</c><00:08:48.839><c> a</c><00:08:49.000><c> row</c><00:08:49.720><c> so</c><00:08:50.640><c> um</c><00:08:50.920><c> we</c><00:08:51.040><c> are</c>

00:08:51.230 --> 00:08:51.240 align:start position:0%
second transaction in a row so um we are
 

00:08:51.240 --> 00:08:53.070 align:start position:0%
second transaction in a row so um we are
actively<00:08:51.600><c> working</c><00:08:51.920><c> with</c><00:08:52.040><c> a</c><00:08:52.160><c> few</c><00:08:52.640><c> cross-chain</c>

00:08:53.070 --> 00:08:53.080 align:start position:0%
actively working with a few cross-chain
 

00:08:53.080 --> 00:08:54.790 align:start position:0%
actively working with a few cross-chain
messaging<00:08:53.519><c> protocols</c><00:08:53.959><c> to</c><00:08:54.120><c> enable</c><00:08:54.480><c> this</c>

00:08:54.790 --> 00:08:54.800 align:start position:0%
messaging protocols to enable this
 

00:08:54.800 --> 00:08:56.870 align:start position:0%
messaging protocols to enable this
functionality<00:08:55.800><c> uh</c><00:08:55.920><c> the</c><00:08:56.040><c> entire</c><00:08:56.360><c> idea</c><00:08:56.640><c> is</c><00:08:56.760><c> that</c>

00:08:56.870 --> 00:08:56.880 align:start position:0%
functionality uh the entire idea is that
 

00:08:56.880 --> 00:08:58.350 align:start position:0%
functionality uh the entire idea is that
you<00:08:57.000><c> should</c><00:08:57.240><c> be</c><00:08:57.360><c> able</c><00:08:57.560><c> to</c><00:08:57.720><c> write</c><00:08:58.000><c> let's</c><00:08:58.160><c> call</c>

00:08:58.350 --> 00:08:58.360 align:start position:0%
you should be able to write let's call
 

00:08:58.360 --> 00:09:00.269 align:start position:0%
you should be able to write let's call
them<00:08:58.519><c> smart</c><00:08:58.839><c> contracts</c><00:08:59.440><c> in</c><00:08:59.519><c> only</c><00:08:59.760><c> front</c><00:09:00.000><c> end</c>

00:09:00.269 --> 00:09:00.279 align:start position:0%
them smart contracts in only front end
 

00:09:00.279 --> 00:09:03.310 align:start position:0%
them smart contracts in only front end
code<00:09:00.880><c> where</c><00:09:01.079><c> it's</c><00:09:01.240><c> like</c><00:09:01.440><c> you</c><00:09:01.720><c> put</c><00:09:02.399><c> um</c><00:09:02.959><c> you</c><00:09:03.079><c> know</c>

00:09:03.310 --> 00:09:03.320 align:start position:0%
code where it's like you put um you know
 

00:09:03.320 --> 00:09:05.310 align:start position:0%
code where it's like you put um you know
if<00:09:03.560><c> else</c><00:09:04.160><c> conditionals</c><00:09:04.680><c> just</c><00:09:04.839><c> call</c><00:09:05.120><c> this</c>

00:09:05.310 --> 00:09:05.320 align:start position:0%
if else conditionals just call this
 

00:09:05.320 --> 00:09:06.949 align:start position:0%
if else conditionals just call this
transaction<00:09:05.839><c> if</c><00:09:06.000><c> output</c><00:09:06.360><c> is</c><00:09:06.480><c> bigger</c><00:09:06.760><c> than</c>

00:09:06.949 --> 00:09:06.959 align:start position:0%
transaction if output is bigger than
 

00:09:06.959 --> 00:09:08.949 align:start position:0%
transaction if output is bigger than
this<00:09:07.160><c> then</c><00:09:07.399><c> write</c><00:09:07.600><c> to</c><00:09:07.800><c> this</c><00:09:07.959><c> chain</c><00:09:08.360><c> set</c><00:09:08.640><c> set</c>

00:09:08.949 --> 00:09:08.959 align:start position:0%
this then write to this chain set set
 

00:09:08.959 --> 00:09:10.910 align:start position:0%
this then write to this chain set set
this<00:09:09.399><c> transaction</c><00:09:10.200><c> we're</c><00:09:10.399><c> also</c><00:09:10.519><c> building</c><00:09:10.800><c> an</c>

00:09:10.910 --> 00:09:10.920 align:start position:0%
this transaction we're also building an
 

00:09:10.920 --> 00:09:13.269 align:start position:0%
this transaction we're also building an
SDK<00:09:11.399><c> called</c><00:09:11.600><c> abstract</c><00:09:11.959><c> JS</c><00:09:12.360><c> that's</c><00:09:12.519><c> going</c><00:09:12.640><c> to</c>

00:09:13.269 --> 00:09:13.279 align:start position:0%
SDK called abstract JS that's going to
 

00:09:13.279 --> 00:09:15.990 align:start position:0%
SDK called abstract JS that's going to
enable<00:09:13.640><c> all</c><00:09:13.760><c> of</c><00:09:13.959><c> this</c><00:09:14.600><c> uh</c><00:09:14.800><c> but</c><00:09:15.079><c> so</c><00:09:15.560><c> essentially</c>

00:09:15.990 --> 00:09:16.000 align:start position:0%
enable all of this uh but so essentially
 

00:09:16.000 --> 00:09:19.069 align:start position:0%
enable all of this uh but so essentially
the<00:09:16.120><c> nodes</c><00:09:16.440><c> use</c><00:09:16.880><c> reverts</c><00:09:17.880><c> for</c><00:09:18.160><c> sequencing</c><00:09:18.760><c> so</c>

00:09:19.069 --> 00:09:19.079 align:start position:0%
the nodes use reverts for sequencing so
 

00:09:19.079 --> 00:09:21.590 align:start position:0%
the nodes use reverts for sequencing so
until<00:09:19.399><c> the</c><00:09:19.560><c> transaction</c><00:09:20.360><c> reverts</c><00:09:21.360><c> nothing</c>

00:09:21.590 --> 00:09:21.600 align:start position:0%
until the transaction reverts nothing
 

00:09:21.600 --> 00:09:23.470 align:start position:0%
until the transaction reverts nothing
gets<00:09:21.839><c> executed</c><00:09:22.680><c> and</c><00:09:22.800><c> then</c><00:09:22.920><c> you</c><00:09:23.000><c> can</c><00:09:23.160><c> use</c>

00:09:23.470 --> 00:09:23.480 align:start position:0%
gets executed and then you can use
 

00:09:23.480 --> 00:09:26.069 align:start position:0%
gets executed and then you can use
onchain<00:09:23.959><c> variables</c><00:09:24.560><c> to</c><00:09:25.560><c> control</c><00:09:25.920><c> the</c>

00:09:26.069 --> 00:09:26.079 align:start position:0%
onchain variables to control the
 

00:09:26.079 --> 00:09:28.310 align:start position:0%
onchain variables to control the
sequence<00:09:26.480><c> flow</c><00:09:27.079><c> but</c><00:09:27.320><c> let's</c><00:09:27.560><c> call</c><00:09:27.720><c> it</c><00:09:27.839><c> for</c><00:09:28.040><c> this</c>

00:09:28.310 --> 00:09:28.320 align:start position:0%
sequence flow but let's call it for this
 

00:09:28.320 --> 00:09:30.310 align:start position:0%
sequence flow but let's call it for this
a<00:09:28.680><c> example</c><00:09:29.000><c> and</c><00:09:29.079><c> for</c><00:09:29.399><c> lot</c><00:09:29.519><c> of</c><00:09:29.680><c> other</c><00:09:29.920><c> examples</c>

00:09:30.310 --> 00:09:30.320 align:start position:0%
a example and for lot of other examples
 

00:09:30.320 --> 00:09:32.030 align:start position:0%
a example and for lot of other examples
that<00:09:30.440><c> we</c><00:09:30.640><c> have</c><00:09:31.120><c> sequencing</c><00:09:31.680><c> happens</c>

00:09:32.030 --> 00:09:32.040 align:start position:0%
that we have sequencing happens
 

00:09:32.040 --> 00:09:34.230 align:start position:0%
that we have sequencing happens
automatically<00:09:32.839><c> because</c><00:09:33.640><c> like</c><00:09:33.839><c> until</c>

00:09:34.230 --> 00:09:34.240 align:start position:0%
automatically because like until
 

00:09:34.240 --> 00:09:37.880 align:start position:0%
automatically because like until
conditions<00:09:34.519><c> are</c><00:09:34.720><c> met</c><00:09:35.320><c> nothing</c><00:09:35.560><c> gets</c>