►
From YouTube: Usable Security in Web3 by Antonela | 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/usable-security-in-web3/
Self-custodial wallets are the most powerful expression of autonomy we can aspire to in web3, but can people actually keep their EOA accounts safe? Balancing security and usability is critical for onboarding the next billion to web3. During this talk, we will explore how both can converge to give users a usable, secure experience.
Speaker(s): Antonela
Skill level: Intermediate
Track: Security
Keywords: usable,security,human-centered design
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
redefining
the
level
of
control
people
have
in
ways
that
was
deeply
different
and
how
this
had
been
done
before?
Not
only
that
well,
3
has
started
with
literal
Financial
value,
even
though
this
is
an
empowering
proposition.
We
see
how
meaningful
has
their
money
compromised
every
day,
I'm
Antonella
I
do
block
security
at
metamask.
A
My
folks
are
there
before
that
I
will
let
the
user
experience
team
by
the
tour
project
for
half
of
the
decade,
deploying
privacy
and
Hyson
technology
is
not
a
crime.
Wallets
can
be
a
lot
of
things
we
can
Define
wallets
as
a
container
of
private
keys
and
their
system
affirmations
to
manage
them.
Every
time
a
dove
asks
the
wallet
to
execute
a
transaction.
The
wallet
is
asking
the
user
to
confirm
the
usage
of
this
case.
Dan
Finley
and
Eric
Marx
made
a
beautiful
definition.
A
Wallets
are
built
around
the
responsibility
of
myriad
in
the
the
interactions
between
untrusted
applications
and
users,
keys
on
the
computers
getting
appropriate
consent
from
the
user.
If
we
map
a
thread
model
of
a
non-cotiller
wallet
like
metamask,
we
will
discover
that
the
two
more
important
assets
that
we
have
at
stake
are
a
pair
of
keys
and
the
permissions
to
use
this
keys.
This
talk
is
not
going
to
be
about
very
Keys.
A
It's
not
going
to
be
about
artifacts
to
protect
this
privacy
like
Oh,
see
it's
phrases,
passwords
fast
prices
or
attacks,
or
that
today,
I'm
going
to
talk
about
permissions
and
I
want
to
talk
about
permissions,
because
permissions
is
the
elephant
in
the
room,
usability
topic,
Dev,
foreign
users.
In
this
ecosystem
there
is
a
lack
of
Interest
or
protocol
level
on
how
protocol
decisions
affects
everyday
people's
lives
and
the
responsibility
of
giving
users
the
chance
to
understand
what
they
are
giving
permissions
to
falls
on
wallets.
A
A
For
example,
the
rehab
is
requesting
access
to
users,
public
skills,
the
address
to
be
able
to
push
requests
in
this
way,
and
this
is
the
user-facing
interface
on
how
the
request
looks
on
user's
computer
I'm
sure
some
people
has
been
facing
these
screens
before
the
wallet
is
making
an
epic
effort
to
expose
and
Trust
information
in
a
secure
environment
in
a
legible
manner,
so
the
user
can
consent
to
execute
or
not
this
transaction.
We
do
things
like
treating
childish
and
treat
analysis
human
review.
We
have
a
lava
mode
for
preventing
supply
chain
attacks.
A
You
should
check
out
on
kumari's
talk
from
yesterday.
We
have
fishing
detect
block
lists
to
Medical
efficient
attacks,
our
vanity
program
and
more
people
who
work
on
security
knows
that
this
is
called
elastic,
security
or
Security
in
that.
But
this
is
not
enough
to
enable
users
to
consent
in
transaction
and
I
will
stop
and
I.
Imagine
that
some
people
is
questioning
why
we
are
talking
about
consent
in
a
usable
security,
talk
and
Friends,
because
they
are
not
secure
systems
without
consent.
A
Consent
is
the
radical
idea
that
one
person
must
voluntarily
agree
to
the
proposal
of
the
size
to
another
thinking
about
this,
why
Building
Technology?
He
still
gives
a
feminist
perspective
to
active
concern
to
apply
it
to
their
social
information
system
that
we
work
with
every
day.
These
are
not
my
ideas.
A
These
are
ideas
that
came
in
the
backbone
from
the
feminist
principles
of
the
internet,
for
open
human
centered
design
processes.
Basically,
when
we
talk
about
consensual
technology,
we
talk
about
having
control
over
our
digital
bodies,
which
of
course
include
our
data
and
for
sure
our
money,
so
how
a
transaction
based
on
concern
should
be
a
few
people
has
been
thinking
about
this
they're,
finding
a
framework
on
how
to
approach
a
consensual
way
to
having
interactions.
I,
really
like
the
five
principles
defined
by
false
Alien
media.
You
can
check
this
and
more
in
the
website.
A
It's
called
senseful
touch.io
good
consent
is
freely
given
is
revocable.
It's
informed,
it's
enthusiastic
and
it's
specific
and
what
we
mean
by
all
these
things.
The
fact
that
the
consent
is
freely
given
puts
the
person
in
a
position
of
doing
something
with
another.
That
should
be
made
without
pressure
with
force
or
manipulation.
A
Anyone
can
change
the
mind
on
what
they
do
at
any
time.
Trust
is
not
forever.
This
is
why
transactions
should
be
revocable.
People
should
be
able
to
understand
what
the
trade-offs
are
of
this
decision.
People
should
be
able
to
read
what
they
are
going
to.
Consent
to
people
should
be
able
to
comprehend
what
is
going
on.
Consent
should
be
enthusiastic
if
someone
is
not
excited
or
really
into
it.
That
is
not
consent.
Consent
should
be
specific.
A
Saying
yes
to
this
now
today,
here
in
Bogota,
in
October,
doesn't
mean
that
I
said
yes
to
other
things,
so
we
started
questioning
our
interfaces
and
how
they
can
become
interfaces
that
could
enable
people
to
give
real
consent.
The
use
of
a
security
design
question
that
we
put
over
a
table
with
our
teams,
with
designers,
with
developers
with
project
managers
with
people
working
on
metrics
with
people
working
on
communication.
If
we
build
a
transaction
flow
grounded
in
concerned,
how
could
it
look
like
you
spoke
and
we
are
listening?
A
We
read
social
media,
we
read
the
forums
we
read
and
we
are
working
hard
on
improving
our
confirmation
screens,
even
when
new
transactions
methods
are
being
defined
right
now
in
other
rooms
on
protocol
level,
without
considering
how
to
expose
users
to
a
consensual
interaction.
Let's
see
the
case
of
approvals.
A
To
allow
a
smart
contracts
to
interoperate
tokens
and
provide
a
better
user
experience,
what
interacts
with
that
in
order
to
perform
operations
that
require
interactions
with
a
man
contracts
like
minting
stacking
swapping
users
are
first
required
to
permit
the
invokers
more
contract
to
transfer
a
number
of
tokens
on
their
rehab.
Sometimes
the
dive
required
improving
this
infinite
amount
of
these
tokens,
even
if
the
user
trust
it
up,
it
could
be
problematic.
A
This
is
our
current
tokens
allowance
screen.
We
have
the
original
mind
requesting
this
transaction.
We
have
the
contract
explicit.
Who
is
asking
for
this
interaction?
But
the
point
here
is:
we
don't
have
allowances
in
the
first
screen
of
this
flow
and
we
have
been
working
on
that
and
we
iterated
this.
This
new
UI
aims
to
empower
users
to
the
final
allowance
that
they
want
to
give
to
the
lab.
We
split
the
flow
into.
A
A
A
Users
can
yeah
I
say
that
before
can
verify
contract
details
and
more
things
echo
in
on
what
Taylor
said
this
week,
we
should
be
responsible
of
what
technology
we
build.
We
should
be
there,
which
will
technology
that
we
expect
people
as
developers
as
wallet
developers.
We
have
the
responsibility
of
critical
thinking
about
how
to
expose
users
to
give
consent
to
a
decision
that
directly
affects
the
digital
values,
and
these
allowed
us
to
explore
opportunities
to
design
the
centralized
technology
that
respects
people,
but
practicing
open
design,
methodologies,
balancing
security
and
usability
it's
complex.
A
We
do
a
lot
of
complex
things
here.
These
requires
inadequate
thread,
modeling
the
possibility
of
including
people
in
your
development
process
and
trying
to
understand
people's
mental
models
too
much
with
the
flows
that
we
propose
as
a
facilitator
of
consensual
transactions.
We
are
trying
to
generate
more
Open
Spaces
to
discuss
ESL
Security
in
the
decentralized
circle.
A
A
If
you
are
a
developer
and
you
have
ideas
on
how
to
improve
metamask,
you
want
to
extend
it.
You
want
to
connect
your
API
to
metamaski
expose
in
a
metamask
UI.
You
should
check
out
meta,
multiply,
IO,
slash,
snaps
and
edit
stocks
from
yesterday.
I
personally
believe
that
there
is
a
long
way
to
go
to
rethink
how
the
information
systems
to
which
we
delegate
trust
interact
with
consent.
B
A
A
C
Hello
thanks
for
your
talk
and
you
presentation
is
told
that,
as
a
security
researcher,
you
have
to
do
balance
between
user
experience
and
security.
How
do
you
draw
the
line
of
saying
the
issue
is
supposed
to
know
the
thing
and
I
have
to
teach
the
the
user?
That
did
you
think
that
happened
now.
Good.
A
Question
I:
don't
think
we
are
here
to
teach
users
I
think
we
are
here
to
inform
people
to
make
informal
decisions
on
the
balance
between
how
much
information
we
show
in
our
screen
and
how
this
information
resonates
with
people
and
also
the
time
that
happens
between
the
people,
make
a
decision
and
read,
may
vary
and
change.
I
think
that
is
the
most
fun
part.
Finding
this
balance
I
think
it's
super
important
also
to
work
with
users.
A
If
you
have
a
product,
if
you
are
building
a
pro
a
product
whatever
you
should
have
users
in
your
development
process,
so
you
can
expose
users
to
your
product
early
and
you
can
get
feedback
and
that
it's
so
rich
because
you
have
people
using
your
pro
before
your
life
or
whatever.
So
that'll
answer
your
question
a
little
bit.
D
A
It's
a
protocol
issue,
it's
not
our
problem.
Now.
We
should
work
together
on
protocol
level
to
make
sure
that
I
mean
to
comprehend
that
we
are
human
and
we
can
make
mistakes
and
I
know
that
Rick
vocability
is
like
a
Hot
Topic
in
this
space.
There
are
a
lot
of
ideas
on
how
to
make
transactions
revocable.
You
can
do
things
like
I,
don't
know
having
a
space
of
nouns
in
the
middle,
and
you
have
a
certain
time
that
you
can
revoke
and
stuff.
They
are
smart
people.
Thinking
about
that.
E
Hi
great
and
great
work
using
is
consent.
How
do
you
think
two
is
possible
to
handle
a
psychnic
message?
Concern
specifically
when
we
sign
some
structured
information
on
metamask,
you
will
see
an
adjacent
that
is
really
hard
to
understand
and
there's
been
a
lot
of
hacks
lately,
based
on
on
our
erc20
tokens,
able
to
permit
user
to
sign
message
in
order
to
allow
for
transactions.
So
it's
very
hard
for
a
user
to
know
if
you're
approving,
genosis,
multiple
or
giving
permission
to
someone
to
spend
your
tokens
on
your
big
house.
A
There
are
a
lot
of
initiatives
they
want
to
make
transactions
readable.
They
are,
you
know,
I
mean
I,
remember
five
right
now,
but
there's
a
lot
of
people
working
on
that
I.
Think
it's
the
next
step
for
big
adoption.
Should
we
having
transactions
in
every
double
Manner
and
I,
seek
companies
making
their
own
versions
of
this?
We
should
aim
to
have
a
community
level
consensus
on
how
we
are
going
to
expose
these
two
users
I.
Think
it's
like
it's
more
powerful.
F
Hi,
thank
you
so
much
for
our
presentation
today.
I
feel
like
I
learned
a
lot,
so
one
question
I
just
really
want
to
ask-
is
about
metamask
product
design,
so
I
as
far
as
I
know,
initially
melamas
didn't
want
to
launch
the
swap
function
and
you
know
on
they
launched
a
swap
function.
I
just
wanna
I
just
feel
like
in
the
current
space.
A
Yeah
amazing
question:
I
can
open
my
computer
and
show
you
our
designs
after
the
talk
and
we
can
discuss
it.
We
are
working
on
network
abstraction.
It's
super
interesting
because
super
early
in
the
moment,
right
now
and
the
options
are
infinite.
Like
I,
don't
think
the
version
we
are
going
to
ship
first
is
going
to
be
the
best
one,
but
I
think
it's
something
good
that
we
are
going
to
iterate
and
we
are
going
to
learn
also
how
people
is
using
different
networks.
A
G
I
actually
have
two
questions
if
allowed,
but
one
is
a
follow-up
to
the
question
before
last
about
signing
and
permissions
and
how
those
interact
and
even
where
they
are
readable.
If
there's
one
particular
thing
that's
being
asked
for
over
and
over
and
over
and
over
and
over
again,
the
user
will
get
alert,
fatigue
and
just
be
clicking
and
to
avoid
that
I
was
seeking
to
have
a
permission
for
that
particular
thing.
G
That
gets
repeated
many
times
and
was
here
for
the
hackathon
last
weekend
and
wanted
to
use
made
a
mask
snaps
to
make
that
easier
and
was
told.
Oh
no
I,
actually
made
in
my
Snaps,
doesn't
support
working
with
the
permission
system
to
do
that.
I
was
wondering
if
there
are
plans
to
allow
snaps
to
work
with
the
permission
system
in
the
future
to
follow
up
on
that.
A
G
The
other
question
was
you
showed
earlier
some
designs
where
you
were
making
it
clear
that,
like
oh,
you
can
set
a
limit
for
how
much
of
a
token
a
particular
dab
can
be
authorized
for,
and
you
have
a
line
in
there
like.
Oh,
you
can
raise
this
limit
later,
but
you
aren't
telling
people
that
there's
a
cost
to
do
so.
It's
like
a
financial
cost
of
doing
so
later
and
I
think
that
that
seems
to
undermine
this
idea
of
consent
a
little
bit
because
you're
not
telling
people
that
there
are
going
to
be
costs.
A
H
Yeah
thanks
for
this
great
presentation,
it's
really
insightful
and
so
I
have
a
question
around
the
of
the
fact
of
give
it
consent.
You
mentioned
that
it's
quite
complex,
because
it's
either
you
give
too
much
permission
and
you
fall
into
like
an
area
where
it's
dangerous
as
a
user
or
you
you
give
too
much
restriction
and
then
you
hurt
the
usability
of
a
user,
because
the
user
then
cannot
do
that.
Much.
H
A
Equation:
it's.
It
has
different
parts.
First,
you
should
have
an
interdisciplinary
team
working
on
stuff,
because
it's
more
powerful.
You
have
more
views
when
people
when
building
something
for
people,
then
there
is
something
very
strong
having
enough
meta
mask
right
now
and
is
the
fact
that
we
are
building
approach
for
the
entire
world
put
us
in
a
position
to
hire
people
from
all
over
the
world.
So
basically
we
have
people
working
everywhere,
and
this
is
powerful
because
you
have
people
sitting
and
tables
making
decisions
that
have
different
biases
mental
models.
This
is
one
part.
A
The
other
part
is
talk
with
users.
I
think
talking
with
users.
Is
it's
so
insightful?
You
are
going
to
discover
things
that
you
even
imagine
in
the
first
second
three
rounds
of
user
testing,
so
the
worst
team
users
first
and
try
and
iterate
I-
think
the
finding
the
balance
is,
the
most
fun
part
of
being
working
on
this.