[Music]
hello everyone H thanks for coming and
first thanks to the organization for
this EV is has been great so far so for
today my to is locks for you ano and I
will be talking about lcks so first
let's see what logs are H they are piece
of information emitted by
contracts uh they don't have a limit on
size more than the uh block site and
they have three important parts one is
the address of the contract emitting the
LW H the other is uh topics that are
indexed information so it can be
retrieved fast and then we have a data
that is ex decimal data field and it can
be whatever you want so uh this is a
block Scout screenshot and this is a
transfer from usdt and you can see that
uh they present like a very human
friendly UI like they could input data
uh but here below you can see the topics
and the data and the first one is the
signature always the signature of the
event and in this case the transfer has
a from and a two and these are the two
other topics in the
logs uh so the important of topics is uh
for example uh this is a screenshot from
Ry and we can use logs to provide
insightful information to the user from
transfer for example we can obtain what
tokens were swapped in a transaction and
it works in any evbm chain so for
example these are information obtained
from arbit ruman Optimus and we can see
that uh the user swapped some tokens in
L and all this is thank you to
Locks uh so what is the problem with
them uh there are two big complaints
that the community has about them one is
that the user has to pay for emitting
log so every time the contract emits
information the user pays for it and uh
the network as a whole needs to store
this information in the
database uh to see about uh the first
problem I took this Dune dashboard and
as you can see it's a bit old
information but in the 30 days period it
was over
1,000 ethereum spend only on gas and
this is around 15 to 20% of the total
spent in
transactions uh so what can we do about
this uh one of the proposal that I saw
the first company that I saw was Shadow
H is to completely remove the lock so if
they are a problem we get rid of them
and the proposal is uh that you can uh
have the chain without locks and then
afterwards you offchain ER emit them
like reprocess the transaction and emit
them modifying the bite code of the
contract
uh this was from a company and then it
came the proposal the standard proposal
uh is this one and uh it's useful to
have a standard because everyone can
implement it but it has it has a
conversation and it didn't have much
feedback like it stopped at some point
last
year uh so is this good is this bad we
need to consider a few things first ER
the user pays for the meeting logs but
they also benefit from them so as you
can see in Rod key we display
information and it's thanks to the locks
also if you use H cidon or any other
application a frontend whatever they all
use locks so you are paying for them but
they are useful for you
always uh Also regarding the ethereum
scalability ER go ethereum the note is
14 tabes in archive mode uh I was told
that it's around 600 GB the locks in the
system so it's a small prop portion of
the 14 Tab and uh if at any point they
are a problem they can be completely
removed from the node also uh they can
be shed in a different note or whatever
and um it's not such a big big deal and
if it ever becomes a problem we can
manage
it and also data ownership the problem
is that if you put a company like Shadow
or ghost or any other company doing
Shadow locks you are not sovereign of
your data you can't use your note
anymore more to get this information
that you are is it is useful for you so
you are using it so this is a big
problem and of course we are cyber punan
so
um we we want to have this data and use
it uh there are also good things about
Shadow logs for example H liquidity
Liquidations in the contracts were not
indexed properly so you can use Shadow
locks to properly detect when you were
liquidated and also there is a similar
issue in the nosis bridge uh because the
address is is not indexed
properly also for example Unis swap
created a beautiful dashboard and pendel
improveed the routing using Shadow loog
so there there are good use cases for
them uh so my feedback here is that we
need balance and there are two main
takeaways one is that uh we need the
logs uh for everyone to use them we
don't need everything in there you can
later but we need a minimum and it's to
good to have extra information in Shadow
logs so that is all thank you for coming
and let's see if you have any
question okay now if somebody has any
question please raise your hand and I
will throw you this don't worry it
doesn't hurt
soft also is a 5 minute talk
count yeah and afterward if there's some
more deep in questions you can discuss
it outside it's okay
okay M has a
question a don't worry it doesn't
break is this a microphone it is just
put it close to you and talk to it all
right is not the yeah so uh for the
locks why why do not them make them uh
basically uh almost free so that the
protocols would use them more and that
way we don't need Shadow blocks because
the I don't think the impact on the nde
performance is not that bad uh as far as
I know there is not there is not such a
big impact on using the locks H the main
problem will be I guess I'm not an
expert on that part but I guess it will
be DDS to the note so if you can SP as
much locks as you want someone could
Theos and it's not zero cost but it's
almost free the locks in the this but if
you can reduce the amount that you spend
of them you can D note and also
um uh you have to careful measure
because everything is like an
equilibrium in the E theum ecosystem so
if you modify one constant here in the
price it can affect to everything
because as far as I know nodes were
locks were supposed to be like for real
time notification so user could get real
time feedback and then developers use
them to store information so they Chang
it the use case of the lock so I guess
it needs an equilibrium and careful
review for that
hey uh do you think that it's fair to
say that the reason um that sad wants to
just eliminate the logs is uh in order
to make the users pay less but in the
end the users end up using the logs from
like R key from a from front and so
shouldn't the users actually end up
paying for the logs I mean doesn't it
make sense in the end uh for user to pay
yeah yeah for me it makes use that what
I said a little bit like the user is
paying for this information but they
directly have a positive impact from it
so Shadow logs are good in cases that H
you need extra information like adding
more things as a developer if you need
analytics or or anything but the user
has a real positive impact for having
logs and they pay for something that
really benefits it and it's not that
expensive it's for a single user the
whole network can have a high cost but
the single user is not paying all
everything just paying a fraction of
that so this is positive for them okay
thank you very much jair time's up thank
you bye bye
bye so now please