►
From YouTube: DXdev Weekly Sync [2023-03-14]
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hola
hola
welcome
to
the
weekly
DXL
developer,
call
14th
of
March
2023
and,
like
wish
us
here
on
a
very
fun
joke.
I,
don't
want
to
be
blinded
by
the
bright
future
of
the
exile.
This
is
why
I'm
wearing
sunglasses,
because
yeah
I
need
to
protect
myself.
A
Yeah
depends
on
how
you
write.
You
know
in
Argentina
we
usually
use
in
Latin
America
the
day
and
then
the
month.
So.
B
A
Pi
Day,
it
sounds
like
I'm
saying
bye
like
a
pie,
but
I
don't
know
how
to
use
it.
The
pie
number
anyway.
Let's,
let's
continue
you
guys,
are
distracting
me.
Let's
start
with
the:
let's
do
the
usual
Roundup
over
the
Excel
projects,
then
we
are
going
to
have
nurse
on
explaining.
Dca
is
tackly
contracts
that
he
have
is
working
on:
B,
it's
Pi,
okay
and
and
I'm
going
to
share
a
few
resources
that
you
found
about
accounts
abstraction.
A
C
Update
yeah
I
think
I
can
give
a
date
today.
That's
actually
not
much
in
the
day
of
updates
today,
because
yeah
headstone
building,
basically
working
on
the
1.5
contract
integration
in
the
The
Guild
UI,
so
yeah,
and
we
are
also
working
on
basically
a
tower
deploy.
A
C
A
Good
good
yeah,
there
is
a
difference,
I
mean
actually
like
a
minidao.
We
are
calling
the
Dao
deployer,
the
one
that
is
the
the
current
down
that
we
use
on
on
mainnet,
which
is.
A
A
The
main
difference
is
that
the
guild
is
a
simple
dial.
We
use
only
one
token
the
Dao.
The
complex
now
will
be
one
that
uses
two
tokens
one
as
reputation
and
one
four
is
taking
or
or
liquid
governance.
So
this
is
what
is
going
to
happen
later
on
Governor
2.0,
right
that
we
are
going
to
have
a
non-transfer
reputation,
token
and
a
liquid
erc20
token
that
is
going
to
be
used,
Forex,
taking
and
also
governance
rights,
so
yeah,
that's
that
would
be
the
main
difference.
A
Maybe
the
xcomp
team,
or
you
know
dark,
can
work
on
a
feature
to
see
if
we
can
differentiate
it
and
communicate
on
on
fmy,
because
it's
like
a
bit
confusion.
The
names
on
that,
but
yeah
mainly
work
on
the
on
the
on
the
deployment
I
talk
with.
We
talk
about
with
Milton
and
and
ferrico
about
two
different
possibilities
on
doing
on
doing
the
deployment.
One
will
be
build
everything
from
the
UI
side
and
one
is
to
have
a
smart
contract
deployed
that
will
be
a
factory.
C
Yeah,
so
the
plan
is
to
avoid
using
a
deployer
or
like
a
like
a
back
end
of
sorts.
If
we
can
so
I
think
we
are
probably
going
to
do
it
in
from
the
front
end.
But
basically
the
plan
so
far
is
to
have
a
deploy,
a
guild
which
will
deploy
goods
for
you.
C
So
if
you
have,
if
you,
if
you
need
your
own
dial
created,
you
can
actually
create
a
proposal
from
Debbie
and
then
that
proposal
will
be
created
in
the
deployed
now
and
the
deployed
Tower
will
do
the
handle
deployments
for
you.
This
is
for
like
production
like
caught
on
code
production
deployments
of
now,
but
if
you
wanted
to
do
you
know,
do
your
own
deployment,
you
can
just
do
it
so
why
we
need.
C
The
deployer
is
basically
to
like
verify
that
Guild
is
basically
like
a
proper,
a
deployment
of
a
certain
protocol,
for
example.
So
this
they
would
like
carrier
verified
badge,
for
example,
not
to
sure,
if
I'm
being
clear
here
so
yeah
questions.
Please.
A
Yeah,
so
everything
will
be
done
from
the
UIC
we
talk
about
it.
Is
there
any
change
on?
How
do
you
plan
to.
C
Yeah
so
I'm
I'm
actually
going
to
talk
about
sorry,
I
mean
we
really.
We
just
like
figured
out
the
specific
plan.
So
what
we
could
do
is
like
okay,
we're
going
to
talk
with
Frederica
and
figure
out.
What
are
the
possibilities?
Are
there,
but
so
yeah
I
I
think
the
best
way
for
now
is
to
like
avoid
using
the
factory.
If
we
can
we'll
start
with
just
like
speed
up
our
development
process
as
well,
but
yeah,
so
maybe
in
a
future
iteration
we
can
actually
add
the
factory
as
well
I.
C
No,
we
would
like
continue
using
the
registry
The
Guild
register
we
have
and
the
deploy
again
will
basically
handle
adding
new
guilds
to
the
that
I
used
to
contract.
A
C
It
will
handlebot,
basically
so
I
think
the
plan
is
to
basically
on
the
create
to
deploy
and
the
registry
as
well,
so
the
Creator
deploy
will
be
on
by
The,
deployer
Guild
and
then
so.
They
can
basically
like
make
sure
that
someone
else
like
hunt
steel,
The
Guild,
address
on
a
different
chain.
So
basically
we
will
have
the
same
Guild
address
for
educated
on
all
the
chains
if
they
want
to
have
multiple
deployments
on
different
chains.
C
Yeah
yeah:
that's
that's
not
going
to
be
permissionless
because
it.
A
A
B
A
A
Exactly
no
no
yeah,
this
is
what
yeah.
This
is
what
we,
what
I
think
the
vs
go
up
team
should
think
about,
or
to
create
a
good
and
easy
process
where
you
can
deploy
permissionless,
you
have
permission
as
deployment
permission
is
deterministic
deployments,
which
means
that
you
know
that
this
address
is
gonna,
be
deployed
on
any
network
this,
this
smart
contract,
while
it
can
be
applied
on
any
network.
This
give,
can
be
deployed
on
any
network.
C
So
I
think
the
plan
is
to
basically
make
make
things
smooth
in
the
UI,
so
the
UI
would
support
doing
your
own
deployment
without
using
the
deploy
now
or
like.
If
you
want
to
do
it
through
deployed
how
it
would
basically
support
that
as
well.
C
A
A
Think
I
think
it
shouldn't
be
done
that
way.
I
think
it
should
just
create
the
gear.
It
does
an
unnecessary
overhead
to
a
dial,
deploying
bureaucracy
in
the
process
of
deploying
the
yield
where,
if
I
want
to
deploy,
I
just
go
and
execute
the
transaction.
I
shouldn't
have
to
wait
for
someone
to
vote
for
me
to
deploy
a
guild,
yes
for
registering
of
having
a
curated
list
of
gifts
right
because,
if
not,
let's
say
if
I
want
to
deploy
a
gear
that
is
going
to
do
deal,
arms
and
organs.
I
can
do
it.
B
A
Anyway,
Let's
yeah,
let's.
C
Yeah
I
think
we
can
like
continue
this
this
discussion
later
as
well.
So
let's
do
that
and
figure
out
figure
out
the
best
path
forward.
I
enjoy
like
this
like
things
that
we
have
not
finalized
it.
Anyway,
we
have
not
written
any
card
or
anything
around
this,
so
yeah.
A
Okay:
okay,
an
update
also
on
the
DS
go
up
side.
We
have
received
the
final
audio
document
from
Omega,
so
the
version
2.0
release
is
already
ready
to
emerge.
I'm
still
waiting
for
approvals
of
the
DXL
members,
malusia
Milton,
Fede,
Ross
and
I.
Think
all
of
us
needs
to
go
there
and
approve,
even
though
I
need
two
review
approvals
to
to
merge
a
final
release,
and
this
is
going
to
later
once
that
is
merged.
We
are
going
to
do
the
reason
GitHub,
but
the
audit
document
is
already
there
on.
A
Then
we
are
going
to
have
I
think
minor
releases
coming
in
the
future
before
integrating
the
governor
2.0
contracts.
But
it's
a
very
important,
my
son,
because
these
are
the
contacts
that
are
going
to
be
using
the
next
iteration
of
our
Dao,
which
means
a
redeployment
of
the
dial
that
is
going
to,
and
that
is
going
to
happen
and
we
are
going
to
start
moving
funds
later
and
over.
This
doubt
that
we
are
going
to
redeploy-
and
we
are
going
to
have
the
same
address
on
every
network
is
where
we
are
going
to.
A
D
Yeah
not
known
big
updates
on
swapper,
actually,
so
just
the
thing
that
we
are
integrating
Levi
for
root
swap
and
then
and
then
yeah,
the
contracts
are
I,
think
ready
to
review
for
zapper
and
then
and
then
we're
just
working
on
struckley
right
now,
so
Leo
took
started
working
on
it
from
this
week
and
Nelson
was
working
on
the
contracts
by
adding
some
fees
to
it.
I
think
yeah
I
will
pass
it
on
to
Nelson
and
he
will
he
will
continue.
B
E
This
is
the
current
front
end
for
stockley.
The
idea
is,
you
can
create,
wait.
E
A
F
A
F
E
So
I'm
only
sharing
my
browser,
but
that
should
work
well
yeah,
then
I
will
see
how
they
share
the
PS
code.
Well,
so
this
is
the
exactly
front
end
for
anyone
that
hasn't
seen
it.
The
idea
of
stock
list
that
you
can
do
DCA,
which
is
dollar
cost
average.
You
set
an
amount
of
usdc,
you
choose
whatever
token
you
want
to
buy
and
the
frequency
and
let's
say
you
want
to
buy
a
hundred
hundred
dollars
of
width,
and
you
want
to
split
it
every
hour
from
now.
E
It
will
every
hour
will
do
the
a
proper
between
now
and
tomorrow
2PM.
It
will
split
the
money
hourly
evenly
and
it
will
do
execute
the
orders
so
how
this
well
I.
F
F
B
E
E
So
first
after
we
set
up
all
over
here,
it
will
ask
us
to
sign
a
transaction
and
that
transaction
will
execute.
These
create
order.
Function
which
comes
with
this
Singleton
address
is
this:
this
actual
all
the
is
using
minimal
proxy
implementation,
the
one
implemented
by
open
sibling.
So
we
deploy
these
as
a
standalone
contract,
and
then
we
every
time
we
create
another
here.
It
creates
a
minimal
proxy
to
the
address,
and
so
it's
quite
cheap
for
the
users.
E
For
every
for
every
dcao
that
we
want
to
place,
we
will
have
to
deploy
a
new
contract
that
will
be
the
address,
so
that
would
just
be
the
this
proxy.
So
once
this
function
is
called,
it
sends
the
address
of
the
of
the
TCA
order
that
we
use
as
a
base
like
the
code
base.
It
sends
the
initializure
signature
and
the
data
for
the
parameters
and
yeah
announced
for
results.
So
this
will
create
a
proxy.
E
The
proxy
is
using
these
clones,
which
are
the
implementation
of
open
sampling
for
minimal
proxies.
It
generates
assaults
and
it
does
deterministic
clone
using
the
previously
deployed
order,
which
is
this
code,
and
then
it
executes
the
initializer
function,
using
the
parameters
also
solving
the
same
bytes
parameter
that
actually
deploys
these
contracts.
E
Here,
the
the
parameters
and
the
initial
parameters,
then
what
we
do
is
we
need
to
take
the
cell,
the
cell
token,
from
the
we
pass,
the
initializer,
which
is
the
parameters
we
send
to
deploy
the
the
proxy
and
we
take
the
cell
token
address
and
the
principal
which
is
actually
the
amount
of
money
we
are
sending
here
as
USC.
It
could
be
any
token,
but
here
it's
us
you
see
and
what
we
do
is
we
take.
E
We
take
that
token
yeah.
We
take
that
token
and
send
it
to
the
order
so
that
this
will
be
the
already
deployed
proxy,
using
the
the
order
on.
E
E
Happens
this
is
this
is
deployed
when
so
wait.
Let
me
go
back
here,
so
the
user
calls
this
function
right
so
on
this
function
creates
a
proxy
which
is
the
actual
order.
This
is
what
the
code
swap.
E
Relayers
will
will
use
we'll
call
to
execute
the
orders
later
on,
so
we
deploy
this
proxy
and
we
call
the
initializer
using
the
parameters
like
owner
receiver.
Token
by
token
amounts
the
fees
and
everything
else,
and
here,
as
I
was
saying,
we
take
the
cell
token
and
the
principle
from
the
parameters
we
already
sent
to
them
all
the
contracts
and
we
take.
E
We
send
the
the
money
from
the
user
that's
executed
in
this
function
that
previously
obviously
approved
the
tokens
we
to
be
taken.
E
We
send
the
the
total
amount,
minions
minus
the
the
protocol
fee
to
the
older
contract,
and
then
we
take
the
fee
and
it
will
stay
in
this
Factory
contract,
and
then
we
have
functions
to
change
the
protocol
fee
or
take
the
fee,
and
once
that's
done,
we
move
to
here,
which
is
a
contract
we
just
deployed
as
minimal
proxy.
E
So
here
are
the
the
initialized
parameters
which
is
owner
receiver,
which
currently
the
front
sets
this
as
the
same.
But
like
the
idea
is
that
if
we
want,
we
can
set
this
to
be
different,
the
cell
token
device
token
the
amount,
the
start
time
and
the
end
time
and
the
interval.
This
will
allow
us
to
calculate
the
slots
for
for
the
others
and
then
the
settlement
contract.
This
is
a
call
swap
set
my
contract,
so
we
do
some
checks
to
make
sure
like
the
start.
E
E
Then
what
happens
is
there
are
a
lot
of
like
infrared
functions
that
the
code
swap
backend
will
use
to
calculate
when
it
should
execute
the
transaction,
which
are
these
all
those
slots
and
Slots
it
takes.
It
doesn't
open
and
calculates
like
it
gives
the
the
execution
time
of
each
other
like
if
we
have
every
hour,
it
will
have
the
time
of
the
exact
time
of
each
of
when
hxa
new
order
should
be
executed,
and
this
Returns
the
like
the
current
one
like.
E
Then
here
we
have
another
function
that
will
also
be
used
by
by
call
swap,
which
is
the
the
way
to
validate
that
the
signal,
the
signatures
that
were
made
by
the
user
to
make
sure
the
owner
of
the
of
the
vault
is
going
to
to
get
the
the
transaction
and
not
asked,
and
then
this
is
where
we
like
have
all
the
the
data
like
this
is
a
function,
call
swap
we'll
execute
when
it
has
to
execute
the
order.
E
So
when
the
time
matches
the
one
of
the
current
slots,
they
will
call
this
function
and
have
all
the
the
data
from
the
from
the
other,
and
they
will
also
call
this
validation
method,
which
also
uses
all
the
data
from
the
from
the
order
which
is
stored
in
the
contract
using
the
owner
receiver
and
things
like
that,
and
if
all
checks
out
it
will
take
the
money
from
this
contract,
it's
already
approved.
E
So
it
can,
you
can
take
the
money,
execute
the
the
all
the
ad
market
price,
so
we
don't
set
how
minimal
amount,
because
we
are
trading
at
market
price
and
after
the
the
contract
is
after
the
trade
is
executed,
it
will
send
the
money
back
to
the
receiver
set,
which
for
now
is
equal
to
the
owner
of
the
contract,
which
is
the
user
and
we'll
do
that
like
if
we
set
it
to
every
hour,
we'll
do
it
every
hour
until
there
is
no
more
left.
E
If
the
user
wants
to
cancel
at
any
given
time
it's
possible,
it
can
have
like,
on
the
address
of
the
proxy
that
he
deployed,
he
can
call
cancel
at
any
time
and
it
will
transfer
back
any
remaining
balance
on
on
this
contract
to
him
and
that's
pretty
much
it,
and
once
this
once
the
funds
are
used.
So
the
the
control
has
some
ceremony
left.
E
It's
pretty
much
at
that
contract
cannot
be
used
again.
So
it's
like
they
use
this.
So
you
deploy
the
order
and
then
once
it's
fulfilled,
you
are
done
and
that's
pretty
much
it
on
the
contracts
I'm
going
to
show
you
sorry
I
made
a
couple
of
graphs,
but
I
can
share
them
later
on
the
channels
with
this
flow.
E
E
A
For
example,
if
I
to
check
the
market
price
so
I
want
this
order
to
be
executed,
and
now
the
price
I
know
that
is,
for
example,
let's
say
two
thousand
dollars,
but
I
don't
want
my
orders,
my
DC
orders,
we
trade
under
1800.
E
That's
a
future.
We
can
definitely
Implement.
It
will
require,
like
some
sort
of
Oracle
queries
to
to
the
tokens,
but
that's
definitely
something
we
we
can
do
this
remember
this
is
an
MBP,
so
it's
a
minimal,
but
you
know
for
DCA,
but
obviously
suggestions
are
welcome.
Having
said,
but
this
has
been
built
by
Adam,
so
I
wasn't
the
one
to
to
build
it
so
congrats
to
him.
I
know
he's
not
here.
Well,
don't
want
to
Secretary
of
his
work,
but
yeah
I
mean
I.
E
So
yeah
and
things
can
happen,
and
maybe
you
don't
want
to
trade
at
that
lower
price,
so
you
can
just
want
them
to
revert
yeah.
That's
it
that's
a
fair
point.
There
are
also
other
ideas.
I
think
Sky
show
you
one
of
the
calls
about
like
being
able
not
only
to
to
execute
DCA
in
this
way,
but
like
also
being
able
to
set
different
prices
so
when
it
reaches
a
specific
price,
it
executes
the
other
and
things
like
that.
A
E
E
A
A
E
To
be
fair,
like
setting
a
minimum
price
where
you
say
yeah,
okay,
stop
that
that's
not
hard
to
do
it's
just
one
more
parameter
in
the
initializure
contract
like
here.
E
E
E
E
But
the
thing
is
that
the
orders
are
executed
by
The
Vault
relays,
so
we
don't
have
control
of
the
all
the
execution,
so
so
it's
executed
by
them.
So
we
can
only
say:
okay,
don't
do
it,
but
we
cannot
do
like
okay.
If
we,
if
we've
done
it
and
before
you
send
me
tokens
report
or
whatever,
that's
not
possible.
A
E
But
the
thing
is
the
I
mean
the
the
function
that
it's
called
on
chain.
Is
this
one
I
believe-
and
this
is
before
executing
the
order,
so
I
don't
know
like
at
the
time
code
swap
sends
the
token
to
a
user
to
a
receiver.
E
That's
that
could
be
an
an
account,
so
I
I
cannot
access
a
revert
after
that
point
right
right,
I
mean
we
could
do,
is
set
the
receivers
as
a
contract
and
then
get
the
money
sent
there
and
then,
if
it's
less
than
whatever
revert,
that
could
be
a
way.
But
that
means
a
lot
more
gut
fees,
because
we
transfer
the
money
to
one
contract
and
then
the
contract
has
to
transfer
it
back
to
the
receiver
and
it
gets
more
complex.
This.
E
F
A
Awesome
and
yeah
we
should
yeah.
We
should
start
working
on
having
it
on.
A
Okay,
thanks
Nelson.
Yes,
we
have
to
cover
reviews
so
yeah
later
many.
We
will
share
it
across
with
feather
Nani
and
Milton
also,
so
we
can
have
their
reviews
too.
Good,
thank
you
and
on
the
contract
yeah
yeah.
Then
we
have
it
upside.
Who
is
working
on
that
dub.
D
Leo's
Leo's
just
started
like
for
a
few
days.
Maybe.
A
Okay,
good
looks
very
good.
The
design
looks
awesome,
so
that
is
interesting.
Okay,
great
a
great
update,
they
are
very
excited.
Yeah
very
good
looks
yeah,
looks
like
very
ready
again
Mary.
Maybe
we
just
work
online
that
feature
and
doing
a
review,
and
then
we
can
just
start
working
on
having
that
deployed.
A
Okay
and
At
Last
I
wanted
to
share
a
few
resources
about
account
of
traction.
A
Okay,
okay,
awesome
when
I'm
going
to
share
the
link.
This
week's
later,
this
was
updated
and
I
think
it
was
even
like
deployed
on
the
ethereum
org
Foundation
a
few
days
ago.
This
is
very
interesting,
very
good
read
that
is
a
low
level,
explaining
the
difference
between
account
attraction
and
externally
own
account,
eoas.
A
The
main
difference
that
we
are
going
to
have
between
this
account
of
traction
and
than
ethereum
account.
So
this
is
going
to
work
the
account
attraction.
Basically,
it's
an
it's
a
change
on
the
on
the
client.
It's
a
deployed
of
a
new
smart
contracts
that
are
going
to
allow
to
manage
smart
wallets,
and
this
is
going
to
have
a
new
type
of
transaction
that
is
going
to
call
user.
A
Op
is
going
to
be
called
user
operations
and
it's
going
to
allow
it's
going
to
allow
ethereum
accounts
to
own
a
smart
wallets
and
Define
security
roles
recover
the
or
not
the
account
the
smart
wallet
if
you
lost.
If
you
love
your
keys
share
your
account
security
pay,
someone
else,
gas
or,
as
per
yours,
you
will.
A
You
will
be
able
to
pay
us
using
erc20
tokens,
but
a
lot
of
transactions
together,
and
it's
going
to
again
allow
you
to
bundle
a
lot
of
user
operations
that
are
going
to
be
executed
by
these
ASMR
wallet
right.
So
the
main
thing
is
that
also
you
are
still
going
to
need.
Ethereum
accounts
to
own
this
smart
wallet,
but
it's
going
to
allow
you
to
do
a
lot
of
things
and
bundle.
A
lot
of
transactions
together
again
pay
gas
on
erc20
token.
A
This
is
very
good
read
that
is
going
to
show
you
what
what
is
going
to
be
the
security
change
in
the
future
regarding
seed
prices,
management
and,
for
example,
samples
of
security
logic
that
can
be
built
into
smart
contract
wallet.
You
can
have
multi6
a
smart
contract,
I'm
going
to
read
multi-6.
A
You
can
have
account
phrasing
saying
that
if,
if,
for
example,
I
know
like
the
accounts
were
lost,
or
you
want
to
freeze
a
certain
small
wallet,
you
can
have
an
account
just
to
freeze
or
unfreeze
in
a
smart
Wallet
account
recovery
set
transaction
naming.
How
much
do
you
want
to
do?
You
want
to
allow
the
smart
wallet
to
to
send
every
day,
week
or
month,
create
white
list
like,
for
example,
you're
going
to
have
a
transaction
limit,
but
you
can
allow
to
override
this
limit
and
to
send
these
transactions
any
amount.
A
How
will
account
attraction
be
implemented?
The
main
thing,
the
main
yeah,
the
main
pursuit
of
this
is
going,
was
EIP
4337,
the
easy
one
supported
by
by
italic,
which
I'm
going
to
share
also
a
blog
post
about
italic.
That
explains
how
it
works.
A
This
smart
contract,
the
main
the
core
of
this
eib
is
a
smart
contract
called
entry
point
which
was
already
deployed,
and
it
is
already
working
on
mainnet
with
the
use
of
this
smart
Contra
that
is
going
to
allow
the
execution
of
user
operations
you
we
will
be
able
to
use
account
of
fraction.
Yeah
I
was
here
here
is
another
and
another
document
that
I'm
going
to
share.
A
This
is
a
document
of
the
EAP
4337
that
it
goes
way
depending
on
how
it's
going
to
work
user
sends
use
and
user
operation
objects
into
a
separate
mempool.
This
is
very
important.
This
is
this
is
going
to
allow
a
change
on
the
client
on
the
ethereum
client
that
we
are
going
to
have
a
mempool
where
the.
A
Go
and
a
pool
where
the
user
operations
go
right.
So
basically,
you
think
that
you
are
going
to
have
two
pools
and
one
you're
going
to
one
is
the
without
we
have
been
using
so
far.
We
are
using
transactions
and
they
are
picked
by
the
Marines
and
they
are
executed,
and
then
is
the
user
operation
where
the
operations
are
going
to
be
picked
and
they're
going
to
be
bundled
together
into
a
transaction
that
is
going
to
be
executed.
A
So
these
user
operations
are
going
to
be
executed
over
the
smart
wallets
that
are
machine
that
are
executed
using
the
entry
point.
This
is
basically
how
how
it's
going
to
work
I'm
going
to
share
this
later.
This
is
a
new
type
of
of
transaction
that
that
we
are
going
to
have
how
it's
going
to
work.
There
are
some.
A
Graphics
here,
but
I
think
it's
not
I
think
is
on
the
here
on
the
post
of
italic.
This
is
also
a
very
good
read:
a
contraction
without
a
training
protocol
changes.
This
is
why
he
was
supporting
this
and
this
EIP,
and
this
is
basically
how
it's
going
to
work
here.
You
have
users,
user,
user
user
or
happy
users.
A
So,
of
course,
this
is
going
to
come
alongside
changing
on
the
on
the
on
ethereum
client
and
not
very
well
words
on
on
how
the
progress
is
been
on
how
the
product
has
been
done
so
far
here.
The
most
important
thing
was
that
we
need
the
entry
point
to
be
deployed
to
the
community
to
come
together
until
into
a
standardized
way
to
use
exclusive
operations.
That
already
happened.
So
this
is
going
this
part,
the
bundle
and
the
bundle
transactions
is
going
to
come
alive
very
soon.
A
So
this
is
a
a
word
that
we
are
going
to
be
seeing
a
lot
in
the
in
the
following
months,
where
different
services
are
going
to
have
their
bundle
of
services,
where
you're
going
to
send
the
user
operations
and
they're
going
to
be
picked
up,
and
then
we're
having
a
a
talk
that
iPhone
that
was
given
on
the
debit
countries.
Account
attraction
on
85,
explain
like
I'm
five,
so
I'm
going
to
be
showing
all
these
later
on.
A
The
development,
Channel
and
I
just
wanted
to
give
a
quick
overview
on
on
how
this
is
going
to
affect
our
not
just
us
the
entire
ethereum
community.
So
the
main
thing
that
we
should
start
looking
later
is
the
bundle
Services
how
we
can
and
which
wallets.
Are
we
going
to
start
supporting
or
from
or
promoting
the
use
on,
our
community
I?
Think
a
lot
of
us
are
using
maybe
frame
or
metamask.
A
We
are
between
those
and
those
wallets
and
we
should
follow
up
on
what
are
their
plans
to
start
integrating
this
user
operation
bundle
services
and
how
this
can
be
used
later,
maybe
by
by
DXL
but
again,
I.
Think
it's
something
very
interesting.
We
are
going
to
start
seeing
different
wallet.
Services
coming
up
in
the
following
month,
for
the
guide
are
going
to
be
going
to
eth
Porto,
and
this
is
something
to
look
up.
A
So
look
if
you
find
someone
who
is
working
already
on
that,
don't
plan
to
work
on
on
the
vendor
service,
on
user
operations
or
account
attraction,
I
think
it's
something
to
that.
We
should
keep
our
eye
on
and
yes,
I'm
going
to
be
showing
you
know
all
this
stuff
on
the
development
Channel
it's
we
have
different
things
so
really
from
the
basic
intermediate
beginner
level
to
an
intermediate
level
where
you
can
go
even
deeper
yeah.