►
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/why-account-abstraction-is-a-game-changer-for-dapps/
Native account abstraction on L2 is a breakthrough for the usability and security of crypto. It’s also the only way to scale self-custody. This talk explains what account abstraction is and why it matters for Dapps and their users. We’ll provide specific examples of features that it uniquely enables, such as session keys, fraud monitoring, multicall, social recovery and more. The end result is the unlocking of new experiences and use cases that can move the needle for crypto’s adoption.
Speaker(s): Julien Niset, Itamar Lesuisse
Skill level: Intermediate
Track: UX & Design
Keywords: UX,security,Dapps
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
Is
kind
of
a
challenge,
but
hopefully
we'll
make
it
fun,
so
my
name
is
julianize
I'm,
one
of
the
three
co-founder
at
Arjun
and
this
morning,
I'll
be
talking
about
account
abstraction.
Why
it's
it's
a
game
changer
for
the
ux
of
of
dapps,
but
I
think
an
alternative
title
of
my
talk.
Could
it
be
how
to
scale
self-care
study?
So
let
me
start
with
a
pretty
obvious
statement
and
I
hope.
We
all
agree
in
this
room
that
self-cue
study
matters
right.
A
Blockchain
is
an
amazing
technology
that,
for
the
first
time,
can
enable
true
digital
ownership.
But
of
course
you
don't
really
own
an
asset.
If
you
give
coustative
to
someone
else
to
a
third
party
and
I
think
the
the
recent
event
of
of
this
summer
with
the
problem
with
Celsius,
is
kind
of
a
good
wake-up
call
of
what
bad
things
can
happen
if
we
rely
on
custodial
Solutions.
A
But
of
course
we
all
know
that
self-key
study
is
hard
right.
If
we
look
at
crypto
Twitter
we'll
see
everyday
users,
you
know
explaining
how
they
lost
access
to
their
assets
or
the
assets
got
got
stolen
and
I
mean.
Sometimes
these
people
are
are
expert.
If
you
look
at
the
tweet
on
the
top
right,
it
comes
from
huge
yoga
of
the
founder
of
a
well-known
D5
project,
so
even
expert
are
making
mistake
and
are
basically
struggling
with
with
self-custody.
A
So
the
question
is
why
circus
studies
so
hard
right
and-
and
we
believe
that
Arjun-
that
the
problem
lies
in
how
ethereum
accounts
were
a
design
at
the
beginning
of
of
ethereum.
It
really
lies
at
the
heart
of
of
the
evm.
So
let
me
dig
a
little
bit
into
ethereum
account
to
try
to
understand
why
there
are
a
problem
and
and
then
Theo
we
can
fix
that.
A
A
So
there's
really
a
link
between
the
two
and
on
ethereum.
That
cling
is
not
is
not
random.
We
need
to
use
a
very
specific
signature
scheme
called
the
cdsa
on
a
very
specific
elliptic
curve.
Sec
p256
K1,
the
details
are
not
that
important,
but
what
matters
is
that
all
of
this
is
are
coded.
All
of
that
logic
is
out
coded
in
DVM,
and
so,
if
we
take
a
step
back,
we
see
that
in
the
user
space
we
have
designer
the
key
pair
and
then
on
ethereum.
A
We
have
the
eoa
with
all
the
evm
logic,
to
validate
and
execute
transactions,
and
we
see
that
there's
video
type
coupling
between
the
two
right.
These
are
basically
two
sides
of
the
same
coin
and
that's
kind
of
the
problem,
because
on
ethereum
we
have
merged
the
concept
of
designer
the
object.
That's
authorized
to
spend
your
token
with
the
concept
of
the
account
the
object,
all
the
your
tokens
on
ethereum.
A
They
are
basically
two
sides
of
the
same
coin
and
that's,
of
course,
a
problem,
because
if
the
signer
is
the
account
and
vice
versa,
that
means
that
if
you
lose
your
signer
you've
lost
everything.
If
I
have
your
assigner
I
have
your
tokens
right.
That
basically
means
that
on
ethereum,
the
entire
security
relies
on
users
managing
a
secret,
this
private
key
designer
at
all
cost
and
as
a
user.
You
cannot
make
a
mistake.
A
If
you
make
a
mistake,
you
lose
everything
and
I
mean
if
there's
one
thing:
we've
learned
from
40
Years
of
the
internet
is
that
we
humans
we
suck
at
managing
passwords
and
we
humans.
We
make
mistake.
So,
of
course,
I
mean
this
is
absurd,
and
and
this
this
concept
is
Paradigm
will
never
work
for
mainstream
users.
A
I
mean
do
we
really
expect
the
next
billions
of
users
to
basically
being
able
to
manage
that
single
Secret
at
all
cost
I
mean
we're
pretty
convinced
that
the
answer
is
no,
so
can
we
do
better,
and
fortunately,
yes,
we
can
do
better
and
there's
something
called
account
abstraction.
The
idea
of
account
attraction
is
is
really
to
decouple
that
relation
between
the
signer
in
the
account
with
account
abstraction.
Every
account
is
a
smart
contract
that
can
contain
its
own
Logic.
A
For
example,
you
you
may
want
to
use
a
different
signature
scheme
or
you
may
want
to
use
a
different
elliptic
curve,
or
maybe
you
want
to
use
multiple
signers
to
validate
transaction.
Think
of
a
native
multisig,
or
maybe
you
want
to
rotate
your
signer,
based
on
some
logic
that
you've
defined
with
account
abstraction.
All
of
this
is
possible.
Another
way
to
see
it
is
that,
on
a
with
account
abstraction,
every
account
is
a
smart
contract
with
custom
logic
that
can
initiate
transaction.
A
So
no
smart
contract
can
become
top
level
accounts
and
the
good
news
is
that
with
true
account,
abstraction
there's,
no
more
EOS
right,
because
every
single
account
is
a
smart
contract
and
you
may
have
heard
about
account
abstraction
lately,
but
actually
it's
not
a
New
Concept.
If
we
look
back,
we
see
that
vitalik
started
talking
about
account
abstraction
as
early
as
2016,
with
the
first
EIP
being
proposed
early
2017,
the
ip86
we
at
Arjun
and
people
like
it
knows
this
with
diagnose
is
safe.
A
We
started
building
smart
contract
wallet
in
2018,
which
basically
were
a
form
of
account
abstraction.
The
idea
was
really
to
solve
these,
these
ux
problem
for
self-custody
using
smart
contract,
but
we
did
so
at
the
application
layer
and
we
came
with
ID
like
social
recovery,
from
monitoring
and
so
on.
In
2020,
there
was
a
new
EIP
again
led
by
vitalik
EIP
2938,
where
the
idea
was
to
add
a
new
type
of
transaction
to
let
smart
contract
become
first
top
level
account
so
enabling
smart
contract
to
basically
make
transaction
and
pay
for
transaction
fees.
A
Soon
after
there
was
the
ip3074
which
took
actually
the
opposite
approach,
which
was
trying
to
enable
some
of
the
smart
contract
feature
on
existing
EOS
and
then
recently
there
was
a
new
EIP
again
led
by
his
italic
eip4337,
which
basically
is
a
generalization
of
smart
contract
quality.
The
idea
is
to
decentralize
some
of
the
infrastructure
that
is
needed
to
make
to
to
write
and
to
operate.
Orchest,
Smart,
contract
wallet
and
I.
Think
eip4337
is
very
interesting
for
different
reasons.
First
of
all,
it
does
not
require
a
fork,
so
it
lacks
smart
contract
quality.
A
So
let
me
dig
a
little
bit
into
4337
rapidly,
so
on
4337
users,
they
send,
they
don't
make
transaction,
they
send
user
operation
and
they
send
this
user
operation
to
a
highly
level
mempool
on
which
you
have
bundlers
like
miners.
That
can
basically
take
a
bunch
of
these
user
operation
and
building
them
into
a
normal
L1
transaction,
and
that
transaction
is
sent
to
a
specific
contract.
A
single
term
called
the
entry
point
when
that
transaction
reach
the
entry
point
contract.
A
The
entry
point
will
basically
orchestrate
the
validation
and
the
execution
of
this
user
operation,
and
it
does
so
by
calling
two
method
of
the
on
the
wallet,
a
first
method
to
validate
the
transaction.
Basically
asking
the
wallet:
are
you
okay
to
execute
that
operation?
And
will
you
pay
you
know?
Will
you
pay
the
fee
to
do
so
and
then
a
second
call
to
execute.
So
we
see
that
with
4337
there's
a
clear
separation
between
validation
and
execution.
Okay
I
mean
all
this
is
great,
but
is
this
really
the
end
of
account?
A
Abstraction
I
mean
every
Ridge,
the
Holy
Grail.
Of
course
the
answer
is
no.
Each
of
these
VIPs
that
have
been
proposed
over
the
years.
They
all
bring
some
of
the
features
of
account
abstraction,
but
they
also
all
have
limitation.
If
we
look
at
the
ip4337,
the
main
limitation
is
that
it
leaves
that
the
application
layer,
so
basically
e4337
wallet,
lag
smart
contract
wallet.
There
are
second
class
citizen
because
they
still
live
on
a
chain
which
relies
on
the
OAS
every
single
depth.
The
tooling
I
mean
the
way
developer,
thinks
about
account.
A
We
all
think
in
terms
of
uas
and
that
makes
Smart
contract
quality
of
437
wallet,
second
class
Citizen
and
that's
actually
a
blocker
for
their
adoption.
So
what
can
you
know?
What
can
we
do
next?
Well,
what
would
be
ideal,
of
course,
is
to
bring
four
three
three
seven
one
layer
down
to
bring
it
from
the
application
layer
to
the
protocol,
and
actually
the
people
who
propose
4337
are
working
on
that
right
now.
But
what
we
think
at
origin
is
that
we
shouldn't
wait
for
that
to
happen.
A
A
There
are
stuff
that
we
now
know
can
be
improved,
and
so
we
believe
that
layer,
2
is
actually
the
great
moment
to
do
so,
and
that's
why
I
mean
we've
been
really
excited
lately,
because
two
of
the
major
layer,
2
providers,
namely
stocknet
and
ZK
sync-
have
committed
to
ship
with
Native
account,
abstraction
and
so
at
origin.
We've
been
working
with
them
quite
closely
for
the
past
year
trying
to
bring
our
experience
as
a
smart
contract,
a
wallet
company
and
making
sure
we
can
really
design
a
kind
of
abstraction.
A
The
way
it's
needed
for
for
users
and
for
the
next
wave
of
of
users.
So,
in
the
remaining
of
the
talk,
I'll
basically
focus
on
stacknet
and
give
you
some
some
example
in
the
stagnet
ecosystem.
But
just
remember
remember
that
everything
I
will
say
applies
to
Z
casing
as
well,
so
with
account
abstraction,
every
account
is
a
smart
contract.
But
of
course
it
cannot
be
any
smart
contract
right.
The
protocol
or
the
VM
needs
to
know
how
to
interact
with
that
account
contract.
A
That
means
that
the
account
must
comply
to
a
certain
interface,
and
so
we've
been
working
with
starknet
and
open
Zeppelin
and
defining
that
interface
for
stacknet,
and
we
came
up
with
the
following
interface:
it's
written
in
Cairo,
so
don't
worry
is
that
you
know
the
style
might
be
a
bit
a
bit
surprising.
But
what's
important
to
note
is
that
just
like
in
the
ip4337,
we
have
a
method
to
validate
a
transaction,
so
every
account
must
expose
a
method
to
say
to
to
validate
and
decide
what
kind
of
signature
schemes
it
wants
to
use.
A
You
know
what
kind
of
nodes
mechanism,
and
so
on
and
there's
a
method
to
execute,
to
really
execute
the
call
and
interact
with
other
contract
and
because
we
are
starting
with
a
blank
page
on
stagnet.
We
did
something
very
cool
is
that
we
introduce
multicol
natively
so
on
stock
net,
every
transaction
is
actually
a
multi-call
by
definition.
Natively
and
I'll
come
back
on
why
that
is
exciting
in
a
few
minutes.
A
On
top
of
these
two
method,
we
also
have
a
method
to
validate
the
deployment
of
an
account.
That
means
that
no
account
contract
on
stagnet
can
pay
for
their
own
deployment.
That
again
it's
something
that
enables
a
great
user
experience
and
finally,
we
have
one
last
important
method
called
is
valid.
Signature
in
the
idea
of
his
body.
Signature
is
to
basically
verify
off-chain
transactions
all
right
again.
I'll
come
back
to
that,
but
smart
contract
they
cannot
sign,
but
they
can
delegate
signature
to
signers
to
keys,
but
they
must
expose
a
way
to
say.
A
Okay,
this
signature
is
actually
valid
for
myself
and
on
on
ethereum.
This
is
the
equivalent
of
VIP
1271..
Okay,
since
this
is
a
developer
conference,
there's
basically
five
things
that
you
need
to
remember
as
a
developer.
If
you
want
to
build
for
account
abstraction
the
first
one
is
that
accounts
are
smart
contract,
and
so
they
need
to
be
deployed.
A
Thankfully,
this
is
something
that
wallet
will
take
care
of,
but
you
still
need
to
think
that
there
is
a
an
account
behind
every
every
wallet.
The
address
of
this
account
is
computed
like
a
smart
contract,
so
there's
no
link
between
the
signer
like
on
ethereum.
It's
it's.
A
new
address
for
a
smart
contract
being
deployed
transactions
can
have
multiple
signature.
A
So
we
need
to
think
that
you
cannot
assume
that,
for
an
account
has
only
one
signer,
maybe
it's
a
native
multisig,
so
you
shouldn't
make
any
assumption
and
signatures
can
basically
be
an
array
and
then,
if
you
want
to
verify
option
signature,
you
cannot
use
a
local
EC
recovery
that
you've
been
used
to.
You
need
to
actually
ping
the
account
and
say:
is
this
signature
valid?
A
A
Okay,
so,
as
I
said,
we've
been,
you
know,
working
with
starknet
on
the
defining
account
abstraction
there
and
of
course
we
built
a
wallet
because
at
Urgent
that's
what
we
do,
and
so
we
actually
built
the
first
wallet
with
Native
account
abstraction
collagen,
X
I
promise
you.
This
is
the
only
slide
where
I
will
chill
Argent,
but
it's
still
needed
since
I'm
on
Main
stage,
so
our
Gen
X
first
wallet
on
stagnet
Native
account
abstraction,
which
is
quite
of
amazing
works
as
a
browser
extension.
So
it
works
on
on
Chrome
and
Firefox.
A
You
can
have
multiple
accounts.
It
works
on
stagnet,
testnet
and
stagnet
mainnet,
and
it
does
the
usual
over
one
of
a
wallet.
You
can
send
and
receive
token
you
can
interact
with
dapps
but
as
I
will
show
it
does
much
more
than
that
also
and
it's
100
open
source.
So
if
you
are
interested,
please
check
the
repo
feel
free
to
contribute
and
if
you
haven't
tried,
the
wallet
do
so
as
well
and
it's
been
actually
an
amazing
ride.
A
You
may
not
know
the
stagnant
ecosystem
is
going,
but
actually,
since
we
started
our
Gen
X
in
January,
we've
had
more
than
250k
downloads,
so
that's
I
think
that's
kind
of
impressive
and
we
are
securing
more
than
90
of
the
funds
on
starknet
mainnet
today.
So
all
this
RJ
next
work.
So
typically,
when
you
think
of
a
wallet,
for
example
like
metamask,
you
think
about
the
client
and
you
think
about
the
key
that
can
sign
transactions
well,
with
account
abstraction.
You
need
to
think
about
the
account
contract
as
well.
A
So
rgnx
is
really
these
three
things:
a
client,
front-end
keys
that
can
sign
transaction
and
then
account
contracts
that
live
on
chain
and
it
works
from
a
user
or
tab.
Developer's
point
of
view.
It
works
exactly
like,
like
you
would
expect
from
your
metamask.
For
example,
when
you
connect
your
wallet
and
you
do
an
action,
the
wallet
will
pop
up.
You
can
review
the
action
approve.
The
extension
will
use
a
key
to
sign
the
authorization.
A
All
this
is
sent
to
the
account
contract
on
chain
which
will
validate
and
then
execute
the
operation
and
call
the
Target
contract
okay.
So
now,
let's
get
to
the
interesting
part,
the
unique
features
that
I
enabled
by
account
abstraction.
So
I
mentioned
that
on
stacknet
we
have
native
multi-call.
The
idea
of
a
multicool
is
that
you
can
actually
make
a
sequence
of
operation
at
as
one
Atomic
transaction.
A
Think,
for
example,
of
the
infamous
erc20
approved
end
call
right
on
ethereum.
If
you
want
to
interact
with
adapt.
That
requires
a
token
you
need
to
First
make
a
first
transaction
to
approve
your
token
wait
for
that
transaction
to
be
mine,
then
you
can
actually
make
your
call
well
with
multicall,
because
your
account
is
a
smart
contract.
You
can
orchestrate
these
different
operations
in
sequence,
so
you
can
actually
in
one
transaction,
do
your
approve
annual
call
or
maybe
you
can
do
your
approve
and
then
five
calls
and
we're
seeing
on
stagnet.
A
The
developers
are
experimenting
with
that,
for
example,
if
you,
if
you
go
on
aspect
which
is
an
nft
Marketplace
on
Stark
net,
when
you
want
to
buy
nfts,
you
can
add
them
to
your
shopping
cart,
which
is
an
experience
that
we
all
know,
and
so
you
see
all
the
nfts
that
you
want
to
buy.
You
finish
your
session,
then
you
go
and
you
actually
buy
this
nft
in
one
transaction,
because
your
account
will
orchestrate
the
buying
all
of
these
these
nfts.
So
in
terms
of
ux,
it's
an
amazing
Improvement.
A
Another
thing
that
we
are
doing
on
stagnet
that
you
can
do
because
of
account
abstraction
is
social
recovery.
The
idea
of
social
recovery,
in
a
nutshell,
is
to
get
rid
of
seed
phrases.
Oh,
do
you
do
that?
Because
your
account
is
a
smart
contract.
You
can
program
it
to
support
a
second
key
and
you
can
Define
that
that
key
cannot
transfer
token.
It
cannot
interact
with
depth.
A
You
can
actually
only
do
one
thing,
which
is
to
replace
the
signer
key
in
case
of
a
problem,
and
you
can
imagine
that
no,
you
give
that
recovery
key
to
a
party
that
you
trust
that
we
call
a
guardian.
Think
of
it,
for
example,
as
a
service
and
the
day
you
lose
your
computer,
you
lose
access
to
your
wallet
well,
instead
of
having
to
think
about
a
seed
phrase,
private
key.
No,
you
just
contact
your
guardian.
A
This
service,
you
authenticate
with
whatever
mean
you've
agreed
with
him,
and
the
service
will
make
the
only
transaction
it
can
do
on
your
account
and
reprogram
your
account
with
a
new
key
and,
of
course
you
can
use
a
service,
but
you
can
decide
to
be
your
own
Guardian.
You
can
use
a
ledger
to
do
so,
for
example,
and
we
are
working
on
ledger
to
enable
exactly
that.
A
So
social
recovery
is
really
a
way
to
get
rid
of
seed
phrase
to
provide
a
ux
that
users,
normal
users,
can
understand,
and
it's
100
non-custodial,
because
you
as
the
owner
of
the
the
main
key,
you
can
decide
who's
your
guardian
and
you
can
change
that
Guardian
at
any
point.
If
you
want
to
so
that's
really
cool.
What?
What
else
can
we
do?
Well,
we
can
do
front
monitoring
with
2fa.
Imagine
that
again
on
your
account,
your
program
is
second
key
and
you
decide
that
that
second
key
must
cost
Okay.
A
So
I
was
talking
about
the
new
cool
feature.
The
idea
to
do
fraud,
monitoring
with
2fa
I
think
I
was
explaining
that
you
can
add
a
key
to
your
account
and
that
key
must
cosine
every
transaction.
So
you
turn
your
account
into
a
two
of
two
multisig
and
you
can
just
you
can
choose
to
give
that
key
to
a
service.
A
Now,
imagine
that
every
time
you
make
a
transaction
with
your
origin,
X
wallet
the
call
data,
so
the
raw
call
that
will
be
executed
on
chain
can
be
sent
to
that
service
for
analysis
and
that
service,
based
on
some
business
rules
that
you
may
have
decide.
You
know
maximum
daily
limit
or
you
know,
trusted
up
and
so
on,
so
it
can
use
whatever
logic
you've
decided
to
decide.
If
the
transaction
is
secure,
it's
something
that
we
know
is
legit
or
if
he
doesn't
know.
A
If
we,
if
it
knows
the
transaction,
it
can
co-sign
automatically
transparent
to
the
user
right
you've
just
made
one
approve
automatically
the
transaction
is
sent,
but
if,
for
some
reason
the
service
detects
that
it's
a
call
to
a
contract
like
that
he
doesn't
know.
For
example,
he
may
ask
you
to
confirm
who
you
are
using
a
second
Factor
just
to
make
sure
that
no
one
is
abusing
your
account.
So
suddenly
you
can
bring
fraud
monitoring
with
2fa
on
chain,
thanks
to
a
account
abstraction.
A
What
else
this
one
is
something
that
I'm
very
excited
about
the
idea
of
session
keys
and
I
think
it's
particularly
relevant
now
for
on-chain
games.
So
if
you
play
non-chained
games,
you've
I
guess
all
been
frustrated
by
the
need
to
sign
transaction.
Every
time
you
make
an
action
having
your
wallet
pop-up
you
approve,
and
then
you
come
back
to
the
game,
so
Unchained
games
today
is
basically
going
on
and
off
of
the
game
to
approve
transaction.
A
Well,
the
idea
of
session
Keys
is
to
say
no
imagine
that
your
game,
the
dab,
the
client,
generates
a
temporary
key
in
your
browser
and
ask
you
to
approve
that
key.
But
he
asks
you
to
approve
that
key
with
a
set
of
constrained
policies.
For
example,
the
DAP
will
say:
I
want
to
sign
transaction,
but
only
for
25
minutes.
The
duration
of
a
session
and
I
will
only
call
this
contract
and
that
contract
and
descend
that
method.
That's
the
only
thing
that
I
want
to
do
as
a
user.
You
can
approve.
A
So
yes,
that's
one
confirmation
with
your
wallet,
you
say:
yeah
I
want
to
start
a
session
on
that
game
under
this
condition,
and
next,
when
you
start
playing
the
game
every
time,
you
click
on
a
button.
You
make
a
game
action.
The
dab
can
send
the
transaction
directly
to
your
account
and
the
transaction
will
be
approved.
So
you
no
longer
need
to
sign.
A
You're
no
longer
need
to
confirm
you
can
actually
focus
on
playing
the
game,
but
you
know
that
your
account
and
your
tokens
are
secure,
because
the
key
you
approved
can
only
do
a
very
construct
set
of
actions
that
you
have
approved.
That's
something
that
several
games
are
actually
now
integrating
into
their
logic
on
stagnet,
so
I
do
believe
that
that's
a
pattern
that
will
come
and
that
really
will
enable
the
ux
of
of
unchain
games.
A
Another
thing
is
that
we
are
experimenting
and
it's
a
collaboration
with
cartridge
and
Ledger
is
the
idea
to
make
the
account
much
more
modular.
So
imagine
that
your
account
is
kind
of
a
base
contract
on
top
of
which
you
can
add
plugins
and
each
plugin
can
have
a
different
logic
to
validate
and
execute
transaction.
A
So
you
can
imagine
that
there's
a
plugin
which
contains
the
session
keys
that
I
just
showed
there's
another
plugin
that
may
work
as
a
new,
a
just
a
signer,
but
then
there's
another
plugin
which
much
stronger
security
that
we'll
use
that
will
be
a
multi-sig
or
that
will
do
social,
a
recovery
as
a
user.
You
can
actually
pick
and
choose
the
plugins
that
you
want
for
your
wallet
and
really
design
your
wallet
for
the
purpose.
A
The
use
case
that
you
want
to
use
it
if
a
wallet
for
gaming,
where
you
know
you
will
spend
maximum
50
dollars,
does
may
not
need
the
same
security
requirements
as
your
the
wallet
you
use
for
trading
on
D5,
for
example,
and
by
making
the
account
modular
user
can
really
choose
pick
and
choose
the
experience
that
that
they
want.
And
finally,
one
last
feature
that
we
are
exploring
is
the
ability
to
use
the
secure
Enclave
of
your
phone,
because
your
account
can
be
programmed.
A
You
can
actually
program
it
to
verify
signature
on
a
different
elliptic
curve
and,
for
example,
you
can
use
it
to
verify
signatures
a
curve,
that's
approved
by
the
nist,
and
that
is
implemented
in
the
secure
Enclave
of
your
phone.
And
suddenly
you
are
turning
every
single
smartphone
into
a
hardware
wallet
and
that's
actually
something
that
someone
has
done
on
stacknet.
So
he
built
an
account
that
uses
that
logic
to
verify
signature.
So
you
can
really
now
turn
smartphone
into
Hardware
wallet.
The
use
cases
that
I
showed
you
are
the
stuff
that
we
are.
A
You
know,
building
and
exploring
at
urgent,
but
I
believe
that
icon
abstraction
opens
a
completely
new
design
space
for
for
user
experience
and
so
we're
only
scratching
the
surface
of
what
can
be
done.
So
I
hope
that
I've
convinced
you
that
icon
abstraction
is
needed
for
the
ux
of
the
blockchain
but
I
think,
more
importantly,
to
really
scale
the
user
experience
of
self-q
study.
A
And
the
thing
is
that
if
we
don't
do
that
and
if
we
stick
to
the
eoa
model
that
we
have
today,
my
bet
is
that
the
next
wave
of
users
they
will
turn
to
centralized
Solutions
I
mean
most
of
us
in
this
room.
We
are
using
it
already
a
coinbase
or
an
FTX,
or
you
know,
binance
account,
because,
yes,
it's
simpler,
so
can
we
really
expect
the
next
wave
of
billion
users
to
not
do
that?
A
Of
course
they
will
so
we
need
to
find
a
way
to
build
a
user
experience
that
is
on
power
with
these
centralized
exchanges,
so
that
would
be
big
certificate
study
at
the
heart
of
every
interaction
on
the
blockchain
and
and
I'm
personally
convinced
that
only
account
abstraction
can
do
that.
So,
let's
make
it
happen
and
build
that
together.
Thank
you,
Julian.
A
You
want
to
know
more
there's
a
three-part
series
called
what
the
is
a
con
abstraction
you
can
find
it
on
Twitter
and
also,
if
you're
interested,
we
are
actually
having
a
panel
on
this
main
stage
at
5
pm
today
with
vitalik
Dan
Finley
from
metamask,
and
then
you
have
which
has
been
pushing
for
eip4337.
So
if
you
want
to
know
more,
please
stick
around
and
come
at
5
PM,
perfect.