►
From YouTube: Account Abstraction Panel | Devcon Bogotá
Description
Visit the https://archive.devcon.org/ to gain access to the entire library of Devcon talks with the ease of filtering, playlists, personalized suggestions, decentralized access on Swarm, IPFS and more.
https://archive.devcon.org/archive/watch/6/account-abstraction-panel/
Account Abstraction: Experts agree, if we don't have Account Abstraction, then Ethereum is at stake!
Your private key wallet will soon be a thing of the past. Account Abstraction promises to put programmability into every Ethereum wallet, and unlock new frontiers for both developers and users.
How will Ethereum be different, when every wallet upgrades to a smart wallet?
What will it take to get there?
What commercial use-cases emerge?
What other parts of Ethereum does AA touch?
Speaker(s): lightclient, Julien Niset, Yoav Weiss, Vitalik Buterin, David Hoffman
Skill level: Beginner
Track: Opportunity & Global Impact
Keywords: banks,private sector
Follow us: https://twitter.com/efdevcon, https://twitter.com/ethereum
Learn more about devcon: https://www.devcon.org/
Learn more about ethereum: https://ethereum.org/
Devcon is the Ethereum conference for developers, researchers, thinkers, and makers.
Devcon 6 was held in Bogotá, Colombia on Oct 11 - 14, 2022.
Devcon is organized and presented by the Ethereum Foundation, with the support of our sponsors. To find out more, please visit https://ethereum.foundation/
A
A
Today,
I
have
the
pleasure
of
moderating
a
panel
that
is
going
to
technically
challenge
me,
so
I'm
just
going
to
be
really
good
at
asking
questions.
Hopefully
this
is
about
account
abstraction,
which
has
been
a
part
of
ethereum
as
a
topic
for
a
very
long
time,
and
now
that
we
are
post
merge,
maybe
we
can
actually
redistribute
some
developer
resources
to
building
something
that
has
always
been
talked
about
as
something
that
is
fundamentally
crucial
to
the
future
of
ethereum
and
every
time
I
talk
to
somebody
who's
technically
minded.
A
They
all
say
that
we
need
account
abstraction,
it's
not
an
option.
We
have
to
have
it
so
we're
going
to
explore
why
everyone
who's
more
technical
to
me
are
always
like,
yes,
accountants,
attraction,
good.
So
on
we
have
Julian
Julian
Nissa,
the
co-founder
of
Argent.
He
is
here
in
the
middle.
There
we
go
and
then
on
the
far
end
we
have
yoab
Weiss
the
security
researcher
at
the
EF
and
then
in
the.
A
A
E
D
If
you
are
a
large
corporation
or
an
individual
customer,
maybe
you
want
to
have
some
different
spending
policies,
so
all
of
these
things
become
possible
anything
that
the
bank
bank
account
can
do
for
you
and
more
can
be
done,
can
be
done
using
account
obstruction.
I
think
this
is
a
must
for
ux
purposes.
Certainly.
A
C
So
Arjun
it's
a
smart
contract.
You
know
we're
a
company
we've
been
building
smart
contract
based
wallet
since
2010,
and
basically
we
started
on
a
mission
to
actually
solve
exactly
what
account
abstraction
is
trying
to
solve,
recognizing
that
the
user
experience
of
EOS
will
basically
never
scale,
and
so,
if
we
keep
that
Paradigm
I
think
we
will
remain
in
the
bubble
that
we
are
in
but
will
be
unable
to
reach
the
next.
C
You
know
100
million
users
or
billion
of
users,
because
the
user
experience
of
self-q
study
is
too
complicated,
and
so
we
started
building
Argent
based
on.
You
know
to
try
to
fix
that,
and
we
did
that
at
the
application
layer
on
ethereum
so
trying
to
to
build
a
smart
contract
based
wallet
enabling
different
security
flows
to
actually
fix
the
issues
that
you
have
mentioned.
So,
for
example,
we
introduced
social
recovery,
which
is
a
way
to
get
rid
of
seed
phrase.
We
introduced
some
kind
of
fraud,
monitoring
and
so
on.
A
Matt
I've
got
a
special
question
for
you,
but
also
feel
free
to
introduce
yourself
and
and
tell
us
what
you
do
at
Geth,
but
also
could
you
after
you
do
that
explain?
Why
do
we
call
it
account
abstraction?
What
are
we
abstracting?
Why
is
the
abstracting
word
here
just
to
really
get
things
at
the
very
basement
level?
A
F
So
I
recently
joined
the
guest
team.
Actually
so
I'm
kind
of,
like
looking
for
my
home
amongst
the
guest
team,
I,
think
that
there's
many
different
things
that
the
get
team
has
focuses
on
and
so
I'm
trying
to
find
like.
Where
am
I.
A
very
specific
Focus
will
end
up
being
so
before
that
I
was
part
of
this
team
called
quilt,
and
we
did
a
lot
of
research
and
development
on
future
ideas
in
ethereum
and
the
first
place
that
I
became
involved
with
account.
F
All
of
the
execution
semantics
about
the
virtual
machine
that
was
executing
on
ethereum
and,
of
course,
like
one
of
those
things
that
you
needed
to
Define
abstractly
was
like
the
account
of
logic,
and
so
this
is
where
we
first
started
running
into
this
problem,
like
vitalik
had
already
talked
about
in
the
relation
to
the
evm
like
earlier
on
in
2016
and
so
and
so
I
guess.
For
me,
the
the
meaning
of
account
abstraction
is
actually
you
know,
maybe
not
the
perfect
way
of
of
defining
like
what
accounts
abstraction.
F
Actually
is
it's
a
term
that
has
like
many
meanings
for
many
different
people
and
for
me,
whenever
I
understand,
accounts,
abstraction,
I,
think
of
it
more
as
like
validation,
abstraction
I.
Think
of
it
like
we're
trying
to
abstract
what
it
means
to
validate
an
account
in
ethereum,
and
so
today,
if
you
want
to
validate
a
transaction
in
ethereum
you're,
going
to
recover
some
address
from
a
signature.
F
Look
at
that
address
in
the
state
to
determine
if
the
nonce
is
okay
for
the
transaction
that's
been
sent
and
that
the
account
has
enough
balance,
and
so
that's
one
way
of
validating
a
transaction.
But
there's
many
different
ways:
you
could
have
a
multi-signature,
you
could
use
different
cryptographic
Primitives
to
to
validate
a
transaction,
and
so,
when
I
think
of
accounts
abstraction,
that's
what
I
first
and
foremost
think
about,
but
I
also
understand
accounts.
Abstraction
is,
you
know,
used
more
generally
now
to
think
about
smart
contract
wallets
and
how
can
we
add
more
functionality?
A
Vitalik,
every
time
you
introduce
yourself,
you
always
come
up
with
a
new
funny
different
way
of
doing
it.
Depending
on
what
era
of
ethereum
you
are
so
I'd
love
for
you
to
introduce
yourself
and
how
you
relate
to
ethereum
these
days
and
also
answer
the
question
for
you.
Why
does
everyone
say
that
account
abstraction
is
inevitable.
G
Yeah
yeah
so
hi
guys,
I'm,
vitalik,
I'm,
a
fashion
influencer
and
travel
blogger
at
the
ethereum
foundation
yeah.
So
a
chaotic
reaction
has
been
a
topic.
I've
been
like
really
trying
to
push
for
almost
since
the
beginning.
Right,
like
you
think,
even
actually,
when
ethereum
launched
the
original
Vision
I
had
been
hoping
for,
was
to
try
to
get
people
to
use
Smart
contract.
G
While
it's
by
default
right,
because
I
mean
we
wanted
people's
money
to
be
secure
and
we
thought
it
would
be
really
nice
if
people
could
just
have
the
default
type
of
accounts
be
a
two
of
three
multi-sig
wallet
right
and
that
that
ended
up
not
happening
I.
Think
in
part,
because
the
community
was
just
I'm,
you
know
so
fed
up
by
yeah
incest
and
kind
of
delays
on
top
of
delays
for
the
ethereum
1.0
launch.
Then
at
some
point
we
just
put
our
foot
down
and
said:
okay,
you
know
no
more
features.
G
Unfortunately,
we
have
to
just
like
cut
everything
and
launch
something,
but
then
you
know,
since
then,
we've
been
trying
very
hard
to
come
up
with
the
right
way
to
actually
get
to
the
point
where
smart
contract
wallets
can
be
the
default
type
of
wallet
that
people
can
use
and
try
to
get
all
these
benefits.
Like
you
know,
security
for
multi-cigs,
you
know
a
social
recovery,
other
types
of
cryptography
and
if
we
want
Quantum
resistance
more
recently
yeah
mineral
thanks
to
minnow.
G
You
know
your
evangelo
and
the
others
are
the
the
topic
of
kind
of
trying
to
get
where
like
aggregation
to
be
in
here
in
there
as
well,
to
try
to
kind
of
save
gas
and
save
data.
So
I'm
like
basically
trying
to
find
the
way
to
bring
a
smart
contract
while
it's
in
and
make
them
actually
be
as
convenient
and
have
all
of
the
properties
and
censorship.
Resistance
is
another
important
property
that
externally
owned
accounts.
G
That's
been
basically
there's
been
this.
You
know
really
long
strand
of
research
of
trying
to
like
really
yeah
optimize
and
figure
out
like
what
is
the
cleanest
and
like
what
is
the
most
sensible
and
secure
design
to
get
to.
You
know
what
actually
satisfying
these
goals,
and
you
know
that's
what
we're
trying
to
implements
and
roll
out
today.
I.
A
Want
you
to
check
my
understanding
on
this,
because
I
actually
had
to
do
some
homework
to
prepare
for
this
mod
this
panel,
because
this
is
technically
challenging
for
me,
after
kind
of
figuring
out
when
people
explain
account
abstraction,
they
were
like.
Oh,
it
enables
you
to
do
this
and
then
it
unlocks
this
feature,
and
it
lets
us
do
that,
but
it
kind
of
feels
like
we're
feeling
that
elephant
metaphor
where
somebody's
feeling
the
tail
and
it's
like
a
snake
and
somebody's
feeling
the
leg.
It's
like.
A
A
Bitcoin
is
a
calculator
ethereum
is
a
smartphone
and
I
kind
of
apply
that
to
externally
owned
accounts
and
a
smart
contract
wallets
or
account
extraction
wallets,
where
it's
externally
owned
accounts
are
like
Bitcoin,
they
don't
really
do
too
much
and
then
externally
and
then
account
extraction
wallets
are
like
ethereum,
where
there's
a
chip
in
it.
Is
that
metaphor
land
yeah?
No,
no,
that's
a
that's
a
really
fun.
A
F
Right
so
I
think
you
know
if
you're
thinking
of
the
con,
the
concept
of
like
putting
a
chip
into
a
wallet,
there's
like
two
important
pieces
that
the
wall
is
doing
and
the
way
that
I
think
about
it
is
that
the
chip
is
dealing
with
the
validation
logic
like
I
mentioned
when
I
spoke
a
minute
ago.
It's
determining
like
is
this
message
and
signature.
That's
coming
from
account
valid
in
the
context
of
this
account.
F
We
also
think
it's
doing
a
lot
of
other
stuff
now
and
so
that
chip
is
now
determined
like
I
want
to
send
a
bunch
of
transactions
from
this
account
all
or
I
want
to
send
a
bunch
of
calls
from
this
transaction
or
from
this
account's,
all-in-one
transaction
or
I
want
to
recover,
using
like
some
social
Recovery
Group
that
I've
come
up
with.
So
that's
like
another
part
of
the
chip.
A
Beautiful
beautiful
and
I
want
to
throw
this
one
to
Julian
as
somebody
who's
responsible
for
actually
putting
some
smart
contract
while
it's
in
people's
hands.
Thank
you
for
your
service.
How
do
you
think
this
is
going
to
get
rolled
out
people
in
general
and
we'll
get
into
the
topic
as
to
why
people
think
that
everyone
will
have
a
a
smart
contract
wallet
rather
than
externally
owned
account
in
the
future?
But
what's
like,
what's
your
idea
for
how
this
gets
rolled
out
into
how
do
we
replace
private
keys
with
externally,
with
account
extracted,
wallets.
C
So
that's
that's
a
very
good
question.
I
think
the
the
way
I
see
it
is
that
I
think
I
mean
vitalik
has
been
pushing
for
a
kind
of
abstraction
for
a
long
time,
and
every
single
proposal
has
some.
You
know
enabled
some
of
the
features
of
account
abstraction,
but
none
of
them
I
think
is
the
end
game
and
and
personally,
for
example,
I
like
the
last
proposal
4337.
But
the
problem
is
that
it's
still
it's
at
the
application
layer,
so
we
are
not
fixing.
C
What
I
think
is
the
real
problem
is
getting
rid
of
of
voas
and
I.
Understand
that
on
ethereum
there's
so
much
at
stake
that
such
a
drastic
change
will
take
time.
I
think
people
are
recognizing
that
account
abstraction
is
the
future
I
think
it
will
happen,
but
on
ethereum
I
think
it
will
take
time.
What
we've
been
pushing
at
Urgent
is
that
I
think
now
we
are
seeing
the
emergence
of
layer,
twos
and
I.
Think
layer
2's
are
an
amazing
opportunity
to
actually
try
to
test
some
of
these.
C
You
know
and
try
to
fix
some
of
these
limitations
of
the
evm
that
we
have
only
one
because
there's
much
less
at
stake
and
then
each
layer
two,
they
may
favor
a
different
type
of
trade-offs,
so
we
can
explore
on
different
patterns
and
actually
bring
alcohol
abstraction
at
the
at
the
layer
twos
right
now.
So
this
is
what
we
are
pushing
and
that
will
enable
us
to
better
understand.
C
You
know
the
limitations,
what
we
can
do
and
and
following
that
I
think
then
we'll
have
everything
enhanced
to
actually
bring
that
to
layer
one
and
push
for
a
kind
of
fraction
at
really
the
protocol
level.
Only
one,
that's
the
way,
I
see
the
roadmap
of
account,
abstraction,
not
folding,
beautiful
and.
A
And
you'll
have
you're
a
security
Reacher
at
EF,
so
I
want
to
tap
into
your
security
mind.
Why
are
smart
contract
wallets
more
secure
like
what
security
benefits
from
a
user
perspective
or
whoever
might
else
whatever
entity
might
also
use
a
Smart
contract
wallet?
Why?
Why
is
it
more
secure
than
our
current
wallets.
D
Well
then,
this
is
a.
There
are
many
different
ways
in
which
it
makes
you
more
secure.
First
of
all
is
a
key
management
users:
users,
don't
know
how
to
manage
Keys,
even
expert
users,
and
they
just
I
think
that
five
years
from
now,
if
we
we
recall
that
we
used
to
secure
our
assets
by
writing,
12
words
on
a
piece
of
paper,
it
will
seem
unreal
to
us
so
I
think,
for
example,
being
able
to
add
devices
to
add
devices
to
your
wallet.
So
the
wallet
is
no
longer
associated
with
some
seed
phrase.
D
You
never
actually
see,
but
instead
you
add
your
phone,
you
add
your
computer,
then
if
you
lose
your
phone,
you
remove
it
and
add
a
new
one
using
your
computer.
So,
and
so
this
allows
this
obviously
improves
the
security,
because
you
don't
need
to
manage
keys
and
then
there's
the
there
are
things
like,
for
example,
you
could
say
that
your
wallet
is
that
you
can.
D
In
that
case,
in
that
case,
you
have
to
go,
get
your
Ledger
or
something
you
had.
You
have
to
add
another
signature,
so
it
allows
you
to
have
a
security
policies
to
protect
yourself
and
there's
the
the
other
Security
benefits
of
switching
of
switching
to
a
better
signature
scheme
which
we're
going
to
have
to
do
in
the
future
anyway.
D
And
since,
since
it's
programmable,
you
can
add
any
any
security
mechanism
you
come
up
with
and
different
users
will
have
different,
we'll
have
a
different
requirements
so
having
just
a
single
security
policy
for
accounts,
which
is
what
we
have
with
EOS
I
mean
the
security
policy
for
a
foreign
AOA
is,
if
you
have
the
key,
do
anything.
If
you
don't
have
the
key
do
nothing.
This
is
not
granular
enough,
so
I
think
being
able
to
have
a
to
have
personalized
security
policies
will
make
ethereum
overall,
more
secure.
A
I
think
the
way
that
I
see
account
objective
wallet,
smart
contract,
wallets,
there's
this
unique
relationship
with
devices
and
we
all
have
a
bajillion
devices
in
our
homes
like
when
I
said
on,
my
computer
I
have
my
computer
in
front
of
me:
I
got
my
phone
and
then
maybe
there's
an
iPad,
and
those
are
three
devices
each
with
different
levels
of
security
assumptions
around
them.
Like
my
computer
is
at
home,
it
doesn't
go
anywhere.
A
My
mobile
phone
can
go
anywhere
in
the
world,
but
all
of
these
things
can
you
talk
about
the
relationship
between
a
device
and
the
wallet
and
how
that
can
relate
to
a
different
level
of
security
of
control
of
access
right.
So
maybe
I
only
want
to
send
a
hundred
dollars
with
my
phone,
but
I
can
send
all
of
my
money
with
my
computer.
Can
you
talk
about
the
relationship
with
a
device
and
a
smart
contract
wallet.
D
So
yes,
you
could
say
that
you
can
use
your
phone
to
do
small
things,
but
your
computer
for
a
for
bigger
things,
I'm
actually
not
sure
I'm.
Sometimes
your
phone
could
actually
be
more
secure
because
on
your
computer
may
or
may
not
have
the
capability
of
security
of
a
on
of
a
secure
enclaves,
but
phones,
modern
phones.
They
usually
do
now.
The
problem
is
that
at
the
moment
you
couldn't
use
it
within
AOA
because
it
doesn't
support
the
signatures,
the
ethereum
use.
D
It
doesn't
support
the
same
curve,
but
with
account
obstruction,
it
becomes
it
becomes
possible
and
someone
actually
just
built
built
a
nice
demo
of
such
wallet
at
the
hackathon
here
in
Bogota.
So
you
can
have
so
if
you
can
associate
the
fingerprint
of
a
specific
device-
and
you
can,
you
can
have
a
fingerprint
on
your
device,
which
is
actually
verified
by
a
secure
Enclave
on
your
phone
and
then
the
signature
happens
inside
it.
So
your
phone
actually
gives
you
a
pretty
good,
pretty
good
security.
But
in
any
case
you
have
to
evaluate
that.
D
For
example,
your
phone
is
coming
with
you,
your
computer
stays
at
home,
so
you
have
to
evaluate
your
unique
situation
and
set
up
a
policy
where
you
decide
which
device
can
do
what
and
maybe
sometimes
you
need
the
to
use
two
of
the
devices.
Maybe
sometimes
you
need
to
go,
also
get
your
Ledger
from
the
safe.
So
it's
up
to
you
to
say
to
decide
how
each
device
is
going
to
be
used
in
your
wallet.
A
I
think
the
important
important
thing
to
take
a
note
from
here
is
that
we're
using
devices
to
relate
to
a
wallet
differently
rather
than
having
a
different
wallet
on
every
single
device,
and
so
Julian
I
want
to
throw
this
one
to
you.
And
now
you
guys
are
thinking
this
at
Argent
and
check.
My
understanding
here
is
like
I've
got
I've
got
a
wallet
here
on
my
phone
I've
got
a
wallet
on
my
my
metamask
on
my
computer.
A
I've
got
a
wallet
on
my
ledger:
there's
three
different
wallets,
but
now
we're
talking
about
three
different
ways
of
interfacing
with
the
same
wallet,
which
is
a
different,
different
kind
of
just
organizational
structure.
So
do
you
think
that,
like
we're
just
going
to
be
able
to
kill
most
of
the
wallets
all
these
like
throwaway,
wallets
that
we
use,
and
instead
of
like
having
a
little
bit
of
cash
in
some
wallet
and
a
medium
amount
of
cash
in
another
wallet
and
then
like
cold
storage?
A
C
I
think
the
first
thing
for
me
and
the
beauty
of
account
obstruction
is
that
you
can
choose
as
a
user,
so
I
don't
think,
there's
one
model
that
fits
for
anyone.
There
are
users
that
may
want
ones
who
have
different
accounts
for
privacy
reasons,
for
example,
so
I
think
there's
not
one
model
that
that
fits
all.
C
But,
of
course,
in
terms
of
origin,
we
like
to
see
the
origin
wallet,
the
main
account
if
you
want
as
your
identity
on
chain
and
so
yes
having
the
ability
to
choose
the
security
Associated
to
the
key
that
that's
in
a
different
device
is,
of
course,
very,
very
important,
and
so
at
Arjun
we
are
researching
a
lot
of
different
IDs,
for
example,
now
we're
exploring
something
called
session.
Keys
is
the
idea
to
have
an
ephemeral
keys,
to
which
you
can
attach
very
strict
policies.
C
But
to
answer
your
question
for
me:
it's
really
about
giving
the
choice
to
users
and
I
think
that's
again.
The
beauty
of
Icon
obstruction
is
that
it
opens
a
completely
new
design
space
for
what
an
account
can
be
and
I
think
we
are
only
scratching
the
surface
of
of
what
can
be
done
at
origin.
We
see
it
as
as
your
identity,
it's
your
our
account.
You
may
have
multiple
accounts
with
different
rules,
for
example.
It's
a
good
example.
C
If
I'm
playing
an
Unchained
game,
I
may
not
want
to
play
a
non-chained
game
on
which
I
have
say
50.
In
a
certain
token,
I
don't
want
to
play
that
game
with
the
same
account
on
which
I
have
all
my
savings,
for
example,
so
I
think
having
the
ability
to
have
different
account
with
different
rules
and
different
logic
is
actually
what
account
abstraction
brings.
D
And
I
I
think
I
just
wanted
to
add
that,
for
even
for
privacy
reasons,
you
want
to
have
multiple
wallets,
because
you
don't
want
to
docs
yourself
everywhere.
It's
still
the
fact
that
we
decouple
the
we
decouple
the
device
and
the
keys
from
the
wallets
means
that
you
can
have
all
of
them
associated
with
a
fingerprint
on
your
same
phone,
so
you
choose
which
one
you're
using
based
on
whatever
privacy
you
want
to
have,
but
you
still
use
the
same
device.
A
I'm
going
to
turn
this
conversation
to
how
we
actually
get
account
abstraction
implemented
at
the
layer,
one
because
this
is
going
to
take
a
an
EIP.
This
is
going
to
take
a
hard
Fork
to
get
this
into
ethereum
and
I
want
to
throw
this
one
to
vitalik
our
resident
crypto
philosopher
here,
crypto
loves
tribes.
We
got
like
the
layer,
one
tribes,
we've
got
the
layer,
two
tribes
are
there
like
account
abstraction
tribes,
and
if
there
are
what
do
they
fight
over.
G
I
mean
I
kind
of
feel,
like
the
tribeness
of
account.
Abstraction
is
like
a
bit
overstated
in
that
I.
Don't
like
I,
don't
really
see
many
competing
camps
of
approaches
for,
like
let's
say
how
to
solve.
The
problem
of
I
have
a
smart
contract
as
well,
and
I
want
to
be
able
to
send
things
from
that
smart
contract
wallet
without
needing
you
know
some
third
party
to
wrap
my
transaction
and
pay
21,
000
gas,
overhead
or
whatever
right,
but
there's
the
different
camps.
G
I
think
are
more
kind
of
just
groups
of
people
that
came
into
the
space
of
improving
accounts,
with
different
emphasis
right
so
like
the
like.
The
emphasis
that
I
came
with
is
solving
the
yep,
the
the
problem
of
like
how
to
make
it
easier
for
people
to
have
Smart
contract,
while
it's
with
arbitrary
validation.
G
Think
you
know,
there's
I
mean
different
ideas
that
are
slowly
kind
of
convert
converging
toward
some
architecture.
That
can
that
actually
does
kind
of
do
is
getting
better
and
better
at
actually
fitting
together
and
in
service
of
like
how
to
get
from
here.
To
there
like
one
of
the
differences
between
eip2938
and
erc4337
right
is
that
4337
is
an
ERC
is
2938
is
an
EIP
and
2938
is
a
kind
of
boil
the
ocean.
Let's
change
the
protocol
now
and
like,
let's,
you
know,
set
things
right
in
the
protocol
sort
of
solution.
G
4337
is
an
extra
protocol
solution
right
and
it's
a
kind
of
analogous
to
sort
of
the
roll-up
Centric
roadmap
in
some
way.
Right,
which
is
you
know,
part
of
part
of
the
motivation
there
is
like
the
core
developers
are
busy
and
you
know,
there's
the
merge
and
there's
the
Surge
and
there's
a
splurge
on
The
Purge,
and
you
know
some
people
wants
to
call
singles
to
what
finality
of
the
George.
G
But
you
know
the
yeah,
and
then
you
know,
because
4337
is
an
ERC,
we
can
kind
of
work
on
it
separately.
Get
it,
and
you
know,
have
a
small
amount
of
usage
just
start
fairly
quickly,
get
it
until
twos
and
improve
it
from
there
from
there
over
time.
But
I
guess.
The
the
one
kind
of
big
difference
here
is
that
I
think
over
time,
like
especially
over
the
last
year.
G
Where,
like
it's,
you
know,
it
starts
off
in
kind
of
making
it
friendly
for
the
API
people
that
kind
of
wants
to
Pioneer
and
what
and
I
really
care
about
getting
these
properties
early
and
then
you
know
expanding
more
and
more
until
finally,
you
know
eoas
may
may
actually
you
know
finally
kind
of
go
away
and
we
really
do
just
have
Smart
contract
wallets
and
all
the
benefits
are
available
for
everyone.
So.
G
There
there
is
an
ERC
and
to
be
clear
right,
it's
important
to
remember
that,
like
with
just
the
ERC,
we
can
already
get
to
the
point
where
you
know
if
people
wants
to
like
replace
their
entire
activity
and
like
run
it
off
of
account
abstracted
wallets
instead
of
regular
ones
like
they
can
do
it
and
it
works
reasonably
well
right,
but
but
the
EIP
is
for
the
second
stage
of
the
roadmap.
Indeed,
like
there
are
like
we
didn't
there's,
we
do
not
have
those
cips
yet
they're
under
development.
G
C
If
you
look
at
stagnet,
it's
still
in
Alpha,
but
actually
it
loans
with
Native
like
an
abstraction.
So
there's
no
more
eras.
It's
actually
trying
to
be
the
end
goal
and
I
think
that
we
learn
a
lot
on
the
Star
Credit
Simpson
that
we
can
then
bring
back
to
the
next
CIP
that
will
put
hopefully
4337
to
the
one
layer
down
to
the
protocol
level.
F
If
it's
okay,
if
I
mean
just
make
a
comment
on
this,
I,
think
that
this
idea
of
layer
twos
experimenting
with
future
potential.
Core
changes
to
the
ethereum
protocol
is
really
interesting
and
I.
Think
things
like
Stark
net
is
a
very
interesting
place
for
it
to
happen,
because
it's
very
different
than
what
the
evm
actually
looks
like
and
I
think
it's
probably
the
right
place
for
those
things
to
happen,
but
I'm
still
hesitant
about
understanding
how
this
is
going
to
play
out
across
all
of
the
different
layer.
F
C
G
I
mean
one
way
to
look
at
like
how
much
equivalence
you
need
is
kind
of
from
the
point
of
view
of
the
user
right
so
like
I,
have
you
know
my
ethereum
wallet
like
zero
xd8da,
blah
blah
blah
and
one
of
the
nice
things
that
the
eoas
offer
is
that
neck,
one
with
just
the
same
wallet
the
same
code,
the
same
key
scheme,
the
same
everything
I
can
just
you
know,
switch
to
all
optimism
and
with
the
send
the
transaction
on
optimism,
switch
to
Arbitrage
and
transaction
on
arbitrum
and
so
forth.
Right.
G
G
So
like
one
one
thing
that
you
know
like
people,
you
know,
ZK,
Stark
and
similar
systems
could
do
is
like
try
to
achieve
kind
of
like
that
code
in
Azure
s,
equivalence,
for
example.
You
know
even
while
experimenting
what's
trying
to
like
make
the
way
they
handle
operations,
much
cleaner
and
different,
and.
A
Just
a
I
want
to
go
back
to
what
Matt
was
saying
just
to
really
drive
this
point
home
about
how
layer
twos
are
going
to
be
like
the
testing
bed
for
account
abstract
action.
Matt.
Can
you
just
kind
of
walk
us
through
into
the
future
about
how
you
think
this
may
play
out
like
ZK
sync?
Does
some
sort
of
flavor
of
account
abstractions
Dark
Knight
does
a
different
one?
The
market
decides
what
they
like.
We
sort
of
come
to
consensus
as
to
what
features
should
be
pushed
down
to
the
layer
one.
F
F
That's
great
and
everybody
will
do
it
just
because
all
the
other,
you
know
all
the
other
companies
will
have
have
run
out
of
money
and
you
know
left
the
ecosystem,
but
I
think
I'm
very
worried
about
the
like
shorter
term,
like
three
to
five
years
like
how.
How
are
we
going
to
be
able
to
bring
millions
of
people
into
this
ecosystem
and
have
like
really
good
experiences
using
applications?
F
If
every
single
protocol
has
a
different
way
of
doing
account,
abstraction
I
can't
imagine
trying
to
support
like
10
different
ways
of
doing
account,
abstraction
in
ether's,
JS
or
web3
JS,
and
so
that's
kind
of
like
my
perspective
is
like.
How
can
we
do
this
in
a
way
that
we
avoid
the
fragmentation
and
that's
why
my
perspective
is
that
we
should
really
consider
using
the
evm
on
the
ethereum
mainnet
as
the
shelling
point
for
coordination
amongst
all
these
different
protocols.
A
Is
there
going
to
become
a
moment
where,
at
some
point
this
turns
from
like
oh
we'll
talk
about
account
of
traction
and
we'll
ideate
on
it
to
like?
Oh,
we
need
to
pull
the
fire
alarm
and
ship.
This
thing
is
that
is
there
like
a
fire
alarm
event
potential
in
the
future?
Where,
like
we
need
to
get
this
done,
starting
a
ship
already.
G
F
I
think
I
mean
we've
had
no
safes
for
a
long
time
as
well,
so
the
smart
contract
wallets
have
existed.
We
want
to
like
improve
the
experience
of
using
them
and
I
wanted
to
say,
like
earlier,
like
I,
think
it's
really
cool
understanding,
all
the
different
security
perspectives
of
account
obstruction
and
the
different
policies
of
different
devices,
but
the
way
that
I
think
about
it.
C
My
point
of
view
I
do
see
some
kind
of
of
urgency,
because
I
and
for
me
it's
related
to
self-q
study
I,
think
self-q
study
today
because
of
vlas
is
really
hard.
We
all
know
that
and
we
because
of
that,
a
lot
of
people
are
actually
turning
to
centralized
solution.
I
mean
if
we
ask
the
audience
most
of
us
here
we
have
a
binance
or
an
FDX
or
a
coinbase
account,
even
though
we
are
the
builders
and
the
early
adopters.
C
So
my
fear
is
that
if
we
don't
find
a
way
to
to
to
have
a
good
user
experience
for
self-care
study,
then
my
fear
is
that
the
next
wave
of
users
may
turn
more
and
more
to
centralized
solution
and
then
will
it
fail
as
an
ecosystem
and,
in
my
opinion,
account
abstraction
is
actually
the
only
way
to
to
enable
this
user
experience
that
can
big
self-q
study,
but
still
make
it
simple
for
user.
So
I
do
feel
a
certain
sense
of
urgency.
Yeah.
F
That's
a
good
point
and
I
feel
like
for
me.
The
urgency
is
like
how
do
we
make
smart
contract
walls
the
default
everywhere,
because
defaults
are
sticky,
and
so,
if
I
go
to
minta
nft
on
openc
and
I
create
a
metamask
following
some
tutorial.
That's
the
default
that
I'm
stuck
with
for
a
long
time,
it's
very
hard
for
me
to
migrate
to
the
smart
contract
world
and
so
figuring
out
how
to
make
that
the
first
thing
that
people
see
whenever
they
come
onto
all
of
the
different
protocols
is
very,
very
important.
Yeah.
A
D
D
A
I
want
to
run
through
some
potential
use
cases
just
to
make
things
really
Concrete
in
the
imagination
of
of
the
people
in
the
audience
here
and
the
listeners.
So
I
want
you
to
each
of
you
to
think
of
the
most
powerful
use
case
that
account
abstraction
unlocks
and
how
that,
on
boards,
new
people,
new
utility
into
ethereum
you
each
get
one
and
whoever
is
going
to
go
first,
is
going
to
have
the
the
opportunity
to
have
the
best
one.
You're
gonna
give
it
to
you.
D
You
know
there
are:
there
are
millions
of
use
cases,
some
of
them
quite
exotic,
I'm
tempted
to
talk
about
them,
but
instead
I
just
repeat
that
being
able
that
being
able
to
obstruct
the
signature
and
to
have
as
to
have
authentication
and
authorization
obstructed
and
let
the
user
control
it.
That's
the
single
most
important
thing,
in
my
opinion,.
G
G
For
example,
you
have
you
know
six
keys
and
you
need
four
of
them
in
order
to
assign
a
transaction
right
like
that's
like
most
of
my
money
is
in
a
four
of
six
ignosis
safe
right
and
like
that,
you
know
it's.
It's
public
info,
it's
on
etherscan,
but
then
the
social
recovery
wallet
is
like
a
wallet
where
you
can
sign
things
with
instant
transactions
with
one
key.
But
if
you
lose
your
key,
then
there
is,
you
know
some
other
mechanism,
which
itself
probably
could
be
a
multi-cig
right.
G
Up
and
that
mechanism
can
change
the
key
of
your
account
if
you
lose
it
right,
so
the
philosophy
there
is
like
in
practice
people's
accounts
getting
lost,
there's
a
big.
It
happens
much
more
often
it's
a
bigger
problem
than
accounts
getting
stolen,
and
so
you
know
you
can
solve
that
problem
without
sacrificing
any
convenience,
and
that
makes
sense,
for
you
know
a
lot
of
smaller
and
medium
value.
Use
cases
right.
G
So
the
challenge,
though,
is
that
you
know
if
you
want
the
benefits
of
either
the
security
like
the
security,
the
protection
against
theft
and,
like
the
kind
of
you
know,
the
really
hardcore
and
security
of
a
multi-sig
wallets
or
the
easier
recovery
of
a
social
recovery
wallets.
You
have
to
put
your
funds
into
a
smart
contract.
G
If
that
intermediary
starts
censoring
and
that
or
or
even
just
you
know,
disappears
or
whatever
and
it
you
know
that
you
end
up
wasting
gas
and
there's
just
like
a
lot
of
extra
money.
Black
City
involved,
which
is
I,
mean
what
basically,
you
know
what
we're
trying
to
get
rid
of
here
right.
So
I
think,
like
you
know,
multi-sigs
and
social
recoveries
are
one
easy
use
case
of
abstraction,
but
then
another
one
is
being
Quantum
proof
right
like
when
the
quantum
computers
come,
we
yeah.
G
D
It's
unknown,
but
but
what's
but
what's
great
about
our
current
process
even
with
the
ELC
is
that
we
can
start
moving
away
from
it.
We
don't
have
to
do
it
one
day
we
can.
We
can
start
moving
gradually
and
over
time,
you'll
see
less
and
less
wallets
relying
on
relying
on
ecdsa,
so
we
can
start
moving
there.
It's
not
a
one
day.
A
F
A
good
core
developer
I,
don't
use
the
blockchain
very
often,
but
when
I
do
use,
the
blockchain
I
have
to
sign
so
many
messages
to
send
anything.
I
have
to
approve
my
tokens
to
go
to
a
contract.
I
have
to
send
them.
Then
I
have
to
approve
more
tokens
to
go
to
a
different
contract
all
for
the
same
application
and
to
me
it's
like
we
could
be
making
this
all
a
single
message
to
go
on
chain.
So.
F
F
If
you
have
a
noses,
safe
or
an
Arjun
wallet,
it
would
get
that
message
and
it
would
say
I
want
you
to
do
two
operations,
but
you
have
the
ability
to
send
them
all
in
one
transaction.
So
now
you
just
sign
one
transaction
and
send
that
off.
That's
something
that
we
could
just
have
today
that
I
think
we're
totally
missing.
C
And
actually,
a
good
example
of
that
in
practice
is
on
the
stagnet
ecosystem.
There's
a
like
nft,
Marketplace
and,
and
there
they've
introduced
the
concept
of
a
shopping
cart.
So
when
you
go,
you
can
actually
do
your
shopping
in
a
sand.
You
want
to
buy
that
Nifty
in
that
one,
that
one
and
you
will
pay
different
token
and
at
the
end
of
your
session,
you
go
to
your
shopping
cart.
C
C
You
can
imagine,
for
example,
that
you,
you
program
a
second
key
on
your
account
that
must
co-sign
every
transaction.
So
you
turn
your
account
in
the
two
of
two
multisig,
but
then
you
can
choose
to
give
that
key
to
a
service
that
may
monitor
the
operation
that
you
are
about
to
do
and
so
that
service,
if
it
takes
that
the
call
data
is
legit,
it's
something
that
you
know
is
secure.
You
can
co-sign
automatically
it's
transparent
to
the
user,
but
now
you're
making
a
last
transfer
to
an
address
that
you've
never
interacted
with.
C
Maybe
you
can
just
ask
you
to
confirm
who
you
are
with
a
second
sector
like
email
and
SMS
or
Google
load,
or
something
so
using
a
construction.
We
can
actually
bring
the
flows
that
user
normal
user
are
expecting.
You
know
bring
the
best
of
web
2
or
of
the
banking
world,
but
actually
reproduce
that
purely
on
chain,
so
I
think
yeah.
For
me,
it's
really
multi-core
social
recovery
and
and
fraud
monitoring
are
three
ways
that
we
can
greatly
improve.
The
the
user
experience
for
users.
A
One
thing
I'm
still
uncertain
of
is
is
how
we
we
want
everyone
to
have
a
smart
contract,
while
we
assume
that
everyone
will
eventually
have
a
smart
contract,
while,
as
everyone
is
in
this
room
and
also
all
future
users
of
ethereum,
how
does
that
actually
happen?
As
in
who
are
the
service
providers,
we
have
somebody
like
Arjun
who's,
producing
a
smart
contract
wallet,
but
what
are
the
other
categories
of
how
smart
contract
wallets
get
into
the
hands
of
users
like
I?
A
Could
imagine,
for
example,
like
I'm
logging
into
some
web3
game
and
I
need
to
use
a
wallet
for
that?
Where
does
that
wallet
come
from?
Who
provides
that
wallet?
And
maybe
maybe
that's
what
Nosa
safe
is,
but
maybe
not
like
what
are
the
categories
of
who's?
Providing
all
of
these
wallet
wallets
to
us
all?
The
users
like?
Are
there
different
categories
out
there.
G
You
know
acts
once
in
that
intermediary
is
what
that
could
you
know,
do
their
thing
and
then
disappear,
which
are
you
know:
smart
contract
wallet,
authors,
wallet
developers
and
people
like
that.
But
look
we
don't
want
to
how
to
depend
on.
You
know
like
active,
a
kind
of
relaying
actors
of
some
kind,
for
example.
Right,
which
is
you
know
that,
like
the
status
quo
is
that
you
do
need
Asia
like
you,
do
need
to
talk
to
a
specific
relaying
actor.
G
If
you
want
a
you
know,
if
you
don't
have
your
own
Ela
and
you
want
to
use
a
transaction
through
a
smart
contract.
Well
right
and
I
think
you
know
censorship.
Resistance
is
a
good
reason
to
minimize
activities
or
Media,
or
it's
just
kind
of
Simplicity,
but
it's
like
it
takes
a
while
to
get
there
right
so
erc4337
it
works
through
in
Mev
ecosystem,
so
it
kind
of
Acts
makes
it.
It
relies
on
Builders
to
access
intermediate
areas,
and
then
you
know
the
goal
of
the
the
various
kind
of
longer
term.
A
So
we
are
okay,
five
minutes
we're
gonna,
try
and
find
some
time
for
questions.
So
if
you
have
questions
start
thinking
of
them
now,
but
as
we
wrap
this
up,
I
wanted
to
do
some
call
to
actions
and
there's
a
very
various
different
like
stakeholders.
In
this.
In
the
world
of
account
extraction,
we
got
core
devs
application,
devs
layer,
two
teams
and
users.
Each
of
these
people
have
their
own
sort
of
responsibility
for
getting
account
extraction
out
into
the
world.
So,
let's
start
with
the
core
devs.
A
G
You
know
they
run
sequencers
and
they're
in
the
process
of
figuring
out
how
to
decentralize
those
sequencers
and
as
part
of
those
processes
making
their
leaders
support,
account
abstraction
and
are
accounts,
abstracted
transactions
and
accounts.
Natively
is
something
that's
really
important
right
so
and
then,
in
the
one
longer
term,
once
the
Asia
layer,
1
EIP,
has
started
coming
in
then
mineral
core
developers
need
to
start
paying
more
and
more
attention
to
it.
A
F
There's
two
things:
I
would
really
like
to
see.
My
colleague,
Sam
Wilson
has
started
a
bi-monthly
call
called
all
wallet.
Devs
I
think
that
if
wall
developers
are
not
aware
of
it,
it's
an
awesome
thing
to
to
see
what
the
current
discussions
around
improving
wallets
are
and
account.
Abstraction
is
obviously
one
of
them
and
I
think.
The
second
thing
is
something
that
we
can
be
doing
today
to
improve
the
user
experience
of
dapps
is.
F
This
is
like
creating
a
new
interface
for
adapt
developers
to
Define
that
they're
trying
to
do
a
batch
of
operations
together
and
then
allowing
the
wallet
on
the
back
end
to
decide
whether
to
send
that
as
an
individual
transaction
or
as
multiple
transactions
I.
Think.
If
we
do
that,
then
we
start
to
show
the
core
developers
that
we're
really
serious
about
batch
transactions
in
smart
contract,
wallets
and
I
think
that
that
will
really
improve.
You
know
their
feelings
about
changing
the
protocol
to
support
that
type
of
Technology
Julian.
C
Signature
I
think
just
making
sure
that
you
adapt
today
is
compatible
with
smart
contract
wallet
and,
as
you
mentioned,
we
can
extend
that
to
multiple,
but
I
think
that
would
that
would
give
already
a
good
sign,
and
that
also
means
that
if
you
know
erc4337
picks
up
and
people
build
more
and
more
wallet
on
top
of
that,
they
will
become
more
and
more
first
class
citizen,
even
on
L1
I.
Think
they've
never
reached
the
point
of
having
full
first
one
first
class
citizen,
but
making
sure
every
single
dab
is
compatible
with
smart
contract
wallet.
A
You'll
have
tickets
home,
and
also
you
have
is
the
the
person
that
actually
helped
educate
me
a
lot
on
for
this
panel,
because
I
was
definitely
not
prepared
more
than
a
week
ago,
so
yoab.
Thank
you
for
your
help.
What's
the
big
call
to
action
that
you
have
to
how
we
get
account
abstraction
into
the
hands
of
everyone,
yeah.
D
Maybe
you
know
allow
users
to
allow
users
who
do
non-financial
stuff
to
pay
with
a
credit
card
and
not
buy
crypto
at
all,
and
there
are
many
things
that
the
wallet
could
be
doing
using
account
obstruction
to
make
the
user's
life
easier.
So
start.
Thinking
about
that
and
there's
a
so
I
I
posted
a
presentation
with
many
with
many
cool
use
cases
that
you
could
build
using
it.
So
so
I
could
so
I
think
going
through
this
list
and
seeing
what
could
help
your
wallet
become
better,
maybe
interesting
and.
A
I
think
just
again
to
really
just
drive
this
point.
Home
ethereum
is
a
technology
that
is
working
on
expressing
itself
starting
in
2015.
It
was
limited,
and
now
we
have
proof
of
stake.
Now
we
have
layer.
Twos
we
have
ethereum
can
express
itself
a
little
bit
better,
but
it's
not
going
to
be
done
expressing
itself
until
wallets
themselves
are
expressive
as
the
Turing
complete
nature
of
ethereum
itself,
and
so
we
will
actually
not
see
a
complete
ethereum
until
we
all
have
Smart
contract
wallets,
and
that
is
how
I
will
finish
this
panel
panelists.
A
A
C
So
for
the
moment
we
are
exploring
with
Falls
337,
but
again
just
to
highlight
that
on
Stockton
and
DK
Singh,
it's
actually
heavily
inspired
by
4337.
So
it's
actually
what
we
are
already
supporting
but
on
on
this
chain.
So
at
the
moment,
no
plans,
but
that's
for
sure
something
that
we
are
discussing
internally
and
researching.
D
Well,
first
of
all,
because
we
are
not
very
good
writers,
I
guess,
but
I
mean
we
could.
We
could
have
written
it
in
a
clearer
way
and
maybe
even
split
it
to
more
than
one
more
than
one
ELC,
but
the
other.
The
other
reason
is
that
it
really
is
complicated,
so
it
really
is
complicated
because
we
paid
a
lot
of
attention
to
to
keep
things
decentralized
by
having
a
mempool
and
keeping
the
mempool
keeping
the
main
pool
protected,
so
so
to
prevent
a
Dos
attacks
that
would
bring
the
system
May
on
his
knees.
I
G
So
the
issue
with
the
meta
transactions
right
is
like
one.
You
need
some
kind
of
mechanism
to
like
figure
out.
You
know
who's
going
to
pay
on
your
behalf
and
connect
you
to
the
person
paying
on
your
behalf
and
these
like.
If
this
depends
on
specific
actors,
then
like
that
becomes
a
censorship
vector
and
they
might
disappear.
And
all
of
these
things
and
also
emitted
transaction
requires,
like
this
extra
gas
cost
of
21
000
per
transaction
right
on
top
of
a
smart
contract
overhead.
G
So,
like
I,
think
it's
important
to
remember
that
erc4337
like
it,
is
similar
to
meta
transactions
in
a
lot
of
ways
and
like
it
uses
very
similar
ideas,
but,
like
it
does
add
this,
like
oh
open
mempool,
to
solve
to
kind
of
remove
dependence
on
specific
actors,
and
it
adds
this
kind
of
like
batching
problem
to
like
basically
cut
the
yeah
21
000
overhead
to
one
to
one
per
block.
So
I,
like
I
view
it
as
a
kind
of
iteration
on
the
same
idea.
C
If
I
can
just
add
on
that,
I
think
with
Native
account
abstraction,
there's
no
more
meta
transaction,
because
the
account
can
pay
transaction
fee
by
itself.
So
the
day,
if
we
bring
4337
to
the
protocol
level,
there
is
no
more
meta
transaction
because
you
just
sign
with
the
keys,
you
send
your
transaction
and
then
the
account
will
automatically
validate
and
if
you
validate
the
transaction,
we'll
pay
the
fee
directly
to
the
miner.
B
B
B
D
Yeah
so
so
I
think,
once
you
have
a
recovery
built
into
the
wallet
you
could,
you
could
use
different
mechanism?
First
of
all,
if
you
don't
have
crypto
friends,
and
you
don't
mind
some
centralization,
you
could
have.
For
example,
you
could
have
a
service
like
a
professional
Guardian,
someone
with
someone
who
can
verify
your
identity
and
then
recover
your
wallet,
and
you
could
use
a
centralized,
centralized
Solutions
like
a
Google
drive
or
apple.
D
But
but
since
you
can
have
as
many
keys
as
you
want
for
the
recovery
you
can
actually
have,
you
can
use
a
centralized
way
for
login,
like
log
in
with
Google
or
anything
anything
of
this
sort
and
then
and
still
keep
a
more
complex
recovery
mechanism
for
the
case
where
they
decide
AI
to
sensor
you,
for
example,
so
you
can
benefit
from
both
from
both
worlds.
Here
my.
C
So
the
way
we
see
social
recovery
is
kind
of
in
a
sense,
it's
a
protocol,
so
every
users
will
want
to
use
different
mechanism
to
you
know
to
get
back
access
to
to
the
wallet
so
yeah.
We
don't
expect
people
to
have
crypto
friends
and
to
rely
on
your
friends,
but
maybe,
if
you're,
a
more
crypto
expert,
you
may
just
want
to
use
a
hardware
wallet
that
you
control
and
you
can
put
that
you
know
in
a
safe
in
a
bank
and
if
something
bad
happens,
you
can
use
that.
That's
how
we
want
it.
C
So
that's
one
option:
you
can
actually
give
that
key
to
a
centralized
service
that
you
trust,
but
the
day
you
don't
trust
it.
You
can
just
remove
it
or
or
you
can
actually
combine.
So
you
can.
You
can
use
a
centralized
service
and
a
hardware
wallet
I
think
it
really
depends
on
on
the
user.
If
you
have
fifty
dollars,
it's
probably
okay,
to
give
that
recovery
key.
C
You
know
that
that
to
to
ask
is,
is
centralized
service
that
you
trust
to
act
as
your
guardian,
but
of
course,
if
you
have
millions
that
may
not
be
acceptable,
so
you
may
want
to
use
two
three
Hardware
wallets
that
you
put
in
different
states.
So
the
way
we
see
is
that
recovery
is
really
a
protocol
and
and
depending
on
users,
we
can
build
on
top
of
that.
The
user
experience
that
they
need,
depending
on
the
use
case
and
where
they
are
in
the
in
the
crypto
Journey.
C
That's
honestly,
a
very
good
question
and
something
we
haven't
really
thought
about.
So
just
to
make
sure
understand
your
question
you're
saying
if
we
enable
this
cosigner,
for
example,
can
this
cosigner
anticipate
some
kind
of
Mev
extraction?
I
guess
the
answer
is
probably
yes,
but,
to
be
honest,
we
haven't
researched
that
yeah.
So
that's
a
that's
a
good
question.
I
I!
Don't
see
why
not,
because,
based
on
the
type
of
transaction,
you
can
probably
assume
that
some
Mev
will
happen
but
yeah.
That's
that's
an
interesting
point
of
view
and
something
interesting
to
research.
H
Shoot
really
quick
one
about
MPC
wallets,
so
the
use
cases
that
you
describe
the
main
ones
with
multisigs
social
recovery
can
be
solved
a
bit
in
a
bit
of
a
hacky
way
with
MPC
EOS,
like
the
one
that
I
think
coinbase
wallet
is
working
on.
Is
that
good
or
bad?
And
if
it's
bad,
what
do
we
do
about
it?
I.
G
Mean
so
yeah,
like
one
specific
thing
that
eeo
the
MPC
approach
can't
solve
right
is
the
key
is
key
changes
so
like
they?
Actually,
they
can't
really
solve
social
recovery
well
right,
and
the
reason
is
that,
even
if
you
take
your
key
and
you
split
it
into
five
secret
shares-
and
you
give
each
year
to
one
of
your
friends
the
yeah,
the
problem
is
that,
like,
if
your
friends
get
hacked,
you
know
even
five
years
later,
like
there's
basically
no
time
limit,
you
have
no
way
to
revoke
once
enough
of
them.
G
Get
hacked
they'll,
be
able
to
take
control
of
your
key
in
your
account
right.
So
that's
one
very,
very
big
problem,
and
then
another
problem
is
that,
just
for
my
ux
perspective,
that
kind
of
approach
would
require
the
users
who
participate
in
like
basically,
it
will
require
your
recovery
Partners
to
have
custom
software
and
account
abstraction
done
with
smart
contracts
is
like
cleaner
because
it
doesn't
require
custom
software
right
like
to
add
a
bunch
of
recovery
Partners.
G
D
And
in
order
to
add
that,
when
you're,
that
an
MPC
aims
to
solve
the
aims
to
solve,
maybe
a
recovery
or
managing
the
keys,
but
it
doesn't
give
you
things
like
adding
a
policies.
I
mean
you.
Can
it
helps
you
with
the
authentication
of
the
account,
but
nothing
else,
and
there
are
actually
NPC.
There
are
some
NPC
wallets
that
use
it
that
run
a
policy
on
a
centralized
server.
So
you
have
a
server
participating
in
the
MPC
and
the
server
will
make
sure
that
you
don't
do
certain
things.
D
K
More
all
right,
cool
we're
good.
We
can
appreciate
that.
That's
love,
I'm
Russ
from
40
acres,
now
we're
trying
to
create
self-sustaining
communities
of
color,
utilizing,
blockchain
and
obviously
there's
a
lot
of
big
brains
in
the
building
right
now,
but
for
the
people
that
have
no
idea
what
you're
talking
about
I'm
super
curious.
There
was
a
wallet
out
and
you
could
aggregate
you
could
use
D5
nft
marketplaces,
I'm
curious!
Is
there
space
for
things
and
products
like
this
in
the
ethereum
space?
K
And
how
do
we
kind
of
aggregate
that
information
for
people
who
don't
even
know
what
a
smart
contract
is
course?
So,
basically,
there
was
a
wallet
out
right
and
you
could
put.
There
was
D5
protocols
in
it.
There
was
nft
marketplaces,
All
in
One,
Stop,
Shop
and
so
I'm
curious
is:
are
there
other
products
or
anything
like
this
being
built
again
to
help
those
who
have
no
idea?
What
smart
contracts
are?
Those
who
just
need
this
information?
The
most.
A
Smart
contracts
wallets
are
how
we
get
there,
and
so
I'd
say
that
smart
contracts
wallets
are
kind
of
how
ethereum
kind
of
fits
into
every
single
corner
of
the
internet,
and
it's
because
we
find
ways
to
hook
ethereum
into
some
sort
of
web3
app
game,
nft
Marketplace
and
it
doesn't
feel
like
ethereum.
It
just
feels
like
the
internet
and
that's
and
smart
contract
wallets
are
definitely
how
we
get.
There.
I
hope
that
answered
your
question
cool
thanks,
guys.