►
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/adoption-day-ux-unconference/
View schedule at: https://adoption.web3.design 🚀👩🚀
Open-source design unconference and working groups helping to drive improved User Experience and usability standards forward for the decentralized eco-system.
Enable cross pollination of fresh perspectives and emerging UX methodologies. Bringing together developers and designers in the ecosystem working at the various layers of the Web3 Tech Stack to share their unique solutions and encourage interoperability amongst various systems.
Speaker(s): Aqeel Mohammad
Skill level: Beginner
Track: UX & Design
Keywords: adoption
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
So
we're
going
to
have
a
few
individuals
kind
of
doing
lightning
talks
throughout
the
day,
we'll
take
a
break
at
lunch
and
then
we'll
have
more
opportunities
for
like
Fishbowl
panels,
for
people
to
come.
Talk
about
designing
for
adoption,
designing
for
decentralization
and
so
forth.
So
personally,
I've
been
quite
interested
in
looking
at
how
we
can
start
designing
for
adoption,
but
not
compromising
when
it
comes
to
decentralization
in
the
ecosystem,
which
we
think
I
think
we
do
quite
often.
A
So
it
would
be
interesting
to
kind
of
get
the
feedback
from
individuals
that
are
working
on
projects
like
status.
I
know,
Rachel
has
been
doing
some
stuff
on
ZK
for
public
goods
rahul's
from
Reddit.
So
we
have
quite
a
few
different
interesting
projects.
Rob
will
be
talking
about
remix
and
if
there's
the
ease
of
use
for
like
web3,
Technologies
and
developer,
resources
is
actually
a
risk
factor.
A
We'll
have
some
people
from
a
lot
of
the
the
client
teams
also
coming
because
that's
the
area
where
I
kind
of
sit
and
work
in
and
I'm
quite
interested
to
see
what
challenges
they're
kind
of
facing.
As
far
as
adoption
for
people
staking
people
running
nodes
and
making
sure
that
there
is
decentralization
in
the
ecosystem
being
taken
in
account
when
we
do
create
these
resources
for
individuals.
Additionally,
we
have
from
optimism
Calvin
talking
about
risk
Frameworks
for
L2
Bridges.
A
So
that's
a
quite
a
huge
space
that
we've
kind
of
not
really
paid
attention
to
at
this
point,
as
these
Layer
Two
start
to
come
in
what
do
ux
around
those
things
really
look
like
and
then
we'll
have
a
few
more
client
teams,
kind
of
talk
about
the
integration
and
standardization
around
ux
and
front
ends
for
those
things.
Additionally,
we'll
have
a
few
opportunities
for
people
to
just
kind
of
like
Get
on
stage
and
Riff
on
anything
that
they
kind
of
feel
important
to
the
ecosystem.
A
So
hopefully,
as
more
people
struggle
in
throughout
the
day,
we
get
to
a
little
bit
more
of
an
energy
of
a
collaborative
nature.
So
if
there
are
certain
Empty,
Chairs,
Etc
kind
of
like
cholesterol
on
certain
tables
for
now,
so
you
guys
have
a
little
bit
more
of
a
integration
and
communication
with
the
individuals
that
are
sitting
next
to
you.
A
B
My
name
is
Rachel
I'm
at
the
ethereum
foundation
on
the
privacy
and
scaling
Explorations
team,
so
our
team
started
out
with
a
bunch
of
developers
who
were
creating
like
cryptographic,
Primitives
or
like
programmable
cryptography,
a
lot
of
zero
knowledge
protocols,
so
that
would
allow
people
to
prove
that
something's
true
without
revealing,
maybe
their
Identity
or
everything
about
themselves
and
I
came
into
the
team
after
they
had
existed
for
several
years.
I
was
the
first
designer
on
the
team.
B
There
are
four
of
us
now,
but
it's
like
the
past
two
years
have
been
really
exploratory
and
experimental,
trying
to
figure
out
like
how
does
design
fit
into
this
space
when
I
got
there.
My
team
lead
Barry,
White
Hat
had
a
bunch
of
project.
Ideas
in
mind
of
like
here
are
some
Concepts
for
how
we
could
apply
some
of
these
ZK
protocols
to
Applications.
B
B
And
those
were
like
the
first
experiments.
How
do
we
put
an
interface
to
this
complex
code?
So
what
I've
learned
through
talking
to
the
developers
that
I
work
with
is
that
the
type
of
code
that
they're
writing
I?
Don't
have
any
development
background,
so
I'm?
Sorry,
if
I
butcher
some
of
the
language
but
like
the
type
of
code
that
they're
writing
is
strange
for
a
traditional
development
background
and
like
there's
some
reframing
that
has
to
happen
and
like
a
logic
that
has
to
change
when
they're
writing
the
code.
B
So
that's,
why,
like
they
refer
to
it
as
programmable
cryptography?
How
can
you
take
this
like
abstract,
math
and
turn
it
into
code?
That
has
like
the
function
to
execute
certain
things
and
then
how
do
you
create
designs?
On
top
of
that,
so
someone
asked
me:
I've
been
asked
a
lot
this
week
like,
if
you
don't
have
any
development
experience
you
like
have
little
knowledge
about
cryptography.
B
How
are
you
designing
for
these
projects
and
what
it
comes
down
to
is
like
not
being
afraid
to
ask
questions
not
being
afraid
to
ask
for
clarity,
and
what
I've
learned
is
that,
when
I'm
in
these
sessions
with
the
developers
that
I
work
with
asking
questions,
they've
I've
gotten
feedback
that
for
them
it
is
also
super
clarifying
for
the
work
that
they
are
doing.
So
it's
like
design
becomes
more
of
this,
like
facilitation
of
conversation,
role,.
B
B
So
when
I
started,
I
had
this
misconception,
that
I
was
designing
for
end
users
of
of
products
that
would
give
people
privacy
and
anonymity,
but
the
more
I'm
on
the
team.
The
more
I
realize
it's
like
we're
doing:
research
for
other
builders
for
other
creatives,
because
all
of
our
work
is
open
source.
B
Everything
we're
making
is
a
public
good
and
should
be
for
the
community
to
use
to
work
from
and
build
off
of.
So
the
real
value
of
the
proof
of
concept
applications
is
not
like
this
product
that
allows
people
to
anonymously
chat.
It's,
for
example,
an
anonymous
chat,
application
that
shows
other
builders.
This
is
possible.
You
can
build
this
thing,
and
here
is
just
one
example
of
how
we've
built
it.
B
The
other
important
thing
like
going
back
to
the
protocol
conversation,
the
protocols
are
like
kind
of
like
rules
like
this
is
these
are
the
functions
that
you
can
execute
with
this
code,
so
at
first,
like
a
lot
of
our
protocols,
just
had
documentation
online.
That
was,
you
know
there
for
the
Curious
people
to
read
and
interpret
and
try
to
build
with,
and
what
we're
learning
is
that's
not
enough.
Like
protocols
can
also
have
websites.
A
A
quick
question
around
that:
why
do
you
think
it
is
in
this
ecosystem,
we're
building
technology
that
doesn't
have
a
clear
use
case
so
and
then
you're
pushing
the
use
cases
on
individuals
that
might
be
able
to
use
them
so
and
also
the
other
thing
that
you
kind
of
mentioned
was
that
you,
you
guys
currently
at
the
the
team?
Don't
have
any
end
users
but
you're
developing,
like
these
prototypes
for
these
teams
to
kind
of
get
an
idea
of
how
to
utilize
the
technology?
A
B
C
B
Team
are
starting
to
have
ideas
for
like
new
projects
that
we
could
work
on
and
new
ways
to
apply
the
protocols,
and
it's
not
coming
from
just
a
few
people.
So
I
kind
of
think
that,
like
we
have
to
be
able
to
communicate
the
value
in
order
to
get
to
a
point
where
we're
having
more
conversations
with
people
who
are
saying
this
is
what
I
want
to
prove
without
exposing
my
identity.
For
example,.
A
It
is
a
bit
restrictive,
even
then,
that
like
you're
not
still
getting
strong
enough
signal
from
these
projects,
that
would
benefit
from
it
is
like
their
exact
use
cases
and
how
the
protocol
might
need
to
be
adjusted
according
to
that,
because
it
is
kind
of
coming
from
like
the
backward
approach
of
the
protocol
is
being
developed
without
having
a
clear
use
case.
So,
let's
say
status
is
developing
a
messaging
protocol.
A
They
have
a
clear
use
case
as
far
as
like
how
to
implement
that,
because
they
know
what
they
want
to
build
on
the
product
side,
whereas
you
guys
are
building
this
like
bottom
layer
without
having
clear
context
to
that.
Are
there
any
learnings?
You
guys
have
learned
from
like
teams
or
feedback
that
you're
getting
from
people
that
do
want
to
implement
some
of
this
stuff.
B
Yeah
all
the
time,
like
I
think
that
the
community
really
challenges
us
I
mean
I've,
been
sitting
in
on
talks
and
going
to
our
Community
Hub
that
we
have
downstairs
the
temporary
Anonymous
Zone
and
we're
constantly
getting
questioned
like
wait.
So
you're
only
able
to
do
XYZ
with
this
protocol,
like
isn't
that
limiting,
and
that
makes
us
like
reflect
on
reflect
on
what
we're
doing
and
see
where
we
can
improve.
C
All
right
good
morning,
everyone,
it's
fun
that
we
all
are
hungover
together
from
Ravi
and
now
we're
here
trying
to
design
beautiful
systems
so
that
more
of
us
can
go
to
Rave
and
then
come
back
and
actually
that's
a
good
point.
How
many
of
us
are
feel
safe
enough
to
be
hungover
and
still
use
like
a
crypto
wallet
to
do
some
weird
transaction,
for
example?
I?
Probably
wouldn't
because
I
know
I'll
mess
up
a
lot
right.
C
Over
the
last
year,
I
have
had
the
pleasure
of
building
and
maintaining
a
crypto
wallet
that
has
been
used
by
over
3
million
users
for
now
at
Reddit,
where
I
work
and
I
prepared
some
notes
about
how
I
think
wallets
are
today
and
what
wallet
could
be
tomorrow,
not
should
but
good.
So
today,
all
the
wallets
kind
of
look
the
same
right.
C
We
all
get
it
right.
The
password
is
not
the
recovery
phrase.
This
is
because
you
save
your
password,
doesn't
mean
you're
kind
of
safe,
like
you
still
need
a
recovery
phrase,
and
if
you
forget
your
password,
it's
okay!
If
you
have
your
recovery
phrase,
unfortunately,
this
Paradigm
is
flipped
over
from
the
web
2
model
when
the
web
2
model.
The
only
thing
you
care
about
is
the
password
as
long
as
you
have
a
password
you're
safe.
If
you
forget
your
password,
that's
fine.
C
There
are
some
ways
to
recover
them
or
reset
them
in
some
way
or
the
other
right,
which
is
very
interesting
since,
like
1990s,
every
web
to
security
engineer
will
tell
you,
don't
write
your
password
anywhere,
don't
put
it
as
posted
notes
on
your
laptop,
and
here
we
are
like
20
since
2014
we've
been
working
in
ethereum,
and
what
do
we
tell
our
users?
Save
your
recovery
phrase,
don't
write
it
in
one
place,
write
it
with
pen
and
paper,
write
in
five
different
places.
C
If
you're,
like
paranoid
enough,
you
should
put
in
like
bank
account,
lockers
fly
halfway
across
the
world,
just
to
recover
your
keys,
if
you
have
like,
if
you're
like
some
kind
of
a
Degen
or
whatever,
which
is
completely
completely
completely
different
to
what
we
do
in
web
2
right.
So
it's
kind
of
weird
for
us
to
s
for
us
to
expect
web
2
users
to
do
the
same
thing
right
and,
if
you've
been
around
in
Defcon
over
the
last
three
days
or
if
you've
been
hanging
around
in
the
world
of
account
obstruction.
C
You
know
that
there
are
like
three
really
hyped
up.
Eips
like
one
is
this
4337,
which
requires
you
took,
which
enables
you
to
have
the
smart
contract
wallet
without
any
protocol
changes.
You
also
have
Argent
that's
building
this
smart
contract
wallet,
which
is
amazing,
because
you
don't
now
need
to
care
about
your
private
keys.
C
Well,
you
kind
of
do,
but
you
know
there
are
ways
to
go
about
it
right
and
then
there
are
like
these
other
older
eips
I'm,
forgetting
the
numbers
I
think
it's
2918,
or
something
and
some
of
them,
like
kind
of
asked
about
protocol
changes
right.
My
hot
take
here
is
4337,
no
matter
how
hyped
up
it
is
it's
actually
not
the
best
idea
for
multiple
reasons.
One
is,
it
adds
insane
amounts
of
complexity.
C
So
if
anyone
has
been
like
hanging
around
the
fourth
reasonable
world,
what
they
do
is
you
have
a
smart
contract
wallet,
and
then
you
have
this
other
private
mempool
other
than
the
ethereum
mempool
that
we
all
use,
know
and
love
and
get
drugged
on.
So
we
have
this
private
mempool.
You
do
your
transactions,
you
send
to
the
private
mempool.
C
It
will
probably
cause
like
a
ton
of
other
issues
if
not
done
properly,
and
it's
still
like
for
a
normal
user.
Now
they
have
like
two
weird
hexadecimal
strings
that
they
think
about.
One
is
their
actual
account
like
their
eeoa
in
in
the
technical
sense,
and
one
is
a
smart
contract
wallet
and
now
when
they
go
on
etherscan,
they
don't
want
to
check
their
actual
address.
They
have
to
check
their
smart
contract
address
kind
of
thing,
so
this
is
like
a
bit
messed
up.
C
Instead
of
trying
to
simplify
things,
we
are
adding
another
layer
of
complexity
and
stuff
right
and
I've
been
thinking
a
lot
about
these
things,
and
the
best
thing
is
that
there
is
no
good
answer
which
is,
which
is
why
I
love
this
space
right,
because
we
need
researchers
and
Academia
and
non-academia.
We
need
ux
people,
we
need
like
Engineers,
but
we
need
all
of
them
to
come
together
and
like
work
on
ux
together.
C
We
don't
just
want
like
designers
to
do
their
thing
and
then
Engineers
to
do
their
thing
and
then
academics
to
do
their
own
thing,
because
then
none
of
them
actually
think
about
things
together
right.
So
one
of
the
interesting
things
I've
been
thinking
about
is
which
sadly
I
don't
think
it's
possible
to
act.
Large
scale
today
is
things
called
multi-party
competition.
Anyone
here
is
familiar
with
the
idea
by
any
chance,
yeah,
okay,
so
for
those
who
don't
really
quickly,
the
idea
is
instead
of
So.
C
Currently
you
have
this
private
key
and
then
this
one
private
key.
Does
this
execution
on
its
own
today,
the
signing
of
the
transaction
and
then
sends
it
to
the
great
mempool
that
we
all
know
and
love,
but
in
multi-party
computation?
You
have
bunch
of
parties
or
people
or
clients
that
come
together
to
do
this
transaction
together.
C
So,
for
example,
you
can
think
about
your
private
key
being
divided
into
three
different
parts
and
then
every
time
you
do
a
transaction,
you
could
do
like
a
two
of
three
of
those
private
Keys
coming
together
to
do
a
transaction
right
and
then
the
most
interesting
thing.
So
I
was
talking
with
someone
who
works
at
web3
auth
today
earlier
I.
C
Think
yesterday
and
the
most
interesting
thing
about
this
is
like
so
one
of
the
keys
is
stored
in
the
laptop
or
like
a
recovery
device
that
you
kind
of
don't
use
it's
kind
of
like
a
cold
wallet.
Then
your
second
key
is
stored
on
your
phone.
So
it's
a
mobile
wallet
and
then
the
third
key
is
can
be
used
by
login
with
Google
or
log
in
with
Facebook
or
something,
but
they
don't
actually
store
that
key
in
Google
servers.
Obviously,
so
they
have
this
other.
C
They
have
this
really
interesting
idea
where
they
have
something
akin
to
a
data
availability,
Committee
of
sorts.
They
have
a
committee
that
talks
to
these
providers
like
Google
and
Facebook,
and
Reddit
and
Twitter,
who
then
stored
the
private
key
there.
But
you
need,
like
this
oauth
login
token
from
Google
to
actually
execute
the
transactions
and
stuff
right
still
quite
better.
We
have
like
now
you
have,
you
can
lose
one
of
the
keys
and
it's
fine.
C
You
could
forget,
like
your
Google,
password
or
Facebook
password,
and
you
could
use
normal
login
systems,
a
normal
reset,
password
techniques
and
stuff
right,
and
then
you
go
like
okay
Rahul.
This
is
this
is
very
cool.
Will
this
work
today?
It
does
kind
of
work.
Coinbase
wallet
has
something
similar,
but
instead
of
divided
into
three
parts,
they
have
two
parts
kind
of
thing,
but
if
you
ever
use
it,
you
realize
it's
a
bit
slower
than
normal
wallets.
Obviously,
because
I
mean
you
can
imagine,
there
are
like
three
keys:
they
come
together.
C
So
maybe
what
what
we
really
need
are
like
two
kinds
of
wallets
right:
one
is
the
kind
of
wallets
used
by
people
who
are
familiar
with
crypto,
and
these
are
also
the
people
funny
enough.
These
are
also
the
people
who
at
some
point,
may
have
gotten
hacked,
but
they
still
love
crypto
somewhere.
They
just
still
keep
using
it
right.
C
So
that's
probably
where
we
want
to
do
these
really
fun
techniques,
and
then
we
want
to
try
and
do
these
really
really
simple
things
in
for
like
the
normal
users
who
aren't
encrypted
yet,
but
we
all
want
them
to
be
in
crypto
right
and
the
idea
of
not
instead
of
like
having
one
app
that
does
both
of
these
things
with,
like
you
know
this
Advanced
option
where
people
can
do
these
crazy
things,
you
have
two
different
apps.
They
can
both
take
two
very
different
strategies
and
experiment
with
things
much
more
quicker.
A
Crypto
wallets
so
we're
curious
as
far
as
like
from
the
Reddit
perspective,
so
most
of
the
projects
in
the
ecosystem,
don't
really
have
a
user
base.
You
guys
are
fortunate
enough
to
have
like
millions
of
users
that
you
are
exposing
to
some
of
the
Technologies.
What
are
some
of
the
challenges
or
the
issues
that
you
guys
have
kind
of
identified?
As
far
as
like?
C
C
It's
also
weird,
because
you
can't
expect
them
to
understand
private
public
key,
but
I
think
by
far
my
biggest
takeaway
is
usually
when
we
onboard
people
into
new
technologies.
We
tell
them
what
are
the
pros?
How
beautiful
it
is
how
it's
going
to
change
your
life,
whereas
when
you
try
to
onboard
people
in
crypto,
we
kind
of
scared
them.
We
throw
these
really
scary.
Jargons
like
cryptography
encryption,
private
key,
don't
give
your
keys,
you
will
get
hacked.
C
You
will
lose
everything
right,
so
we
give
them
like
a
one
hour
essay
on
like
what
you
need
to
be
careful
about,
and
then
we
go
like
so
yeah
if
you're
kind
of,
if
you're
still
interested
come
into
this
crazy
world
that
we
all
know
and
love
called
crypto
kind
of
thing
so
maybe
like
have
it
a
bit
more
easier,
rolling
yeah.
Thank
you.
Everyone.
A
D
D
D
So
we
can
ease
this
user
pane
cool
before
I
dive
in
let's
think
about
what
users
really
need
in
their
kind
of
hierarchy
of
needs
when
it
comes
to
transferring
money,
the
most
important
thing
of
any
money
transfer
mechanism,
not
just
crypto
traditional
money,
transfer
mechanisms,
huala
anything
is
reliability.
You
know
reliability
is
important.
You
don't
want
your
money
to
get
lost
if
we
don't
get
reliability
right,
nothing
really
Else
Matters,
and
that
includes
security
and
then,
once
we've
got
reliability
nailed.
D
Then
there
are
three
more
points,
all
kind
of
more
or
less
on
the
same
level,
which
is
cost
speed
and
usability
and
users
can
be
happy
to
trade.
Some
of
these
against
each
other,
you
know
pay
a
bit
more
for
a
transaction
to
go
faster,
pay
a
bit
less
and
a
transaction
go
slower,
but
yeah
reliability
is
absolutely
the
number
one
important
thing.
D
There
about
when
making
a
transfer,
nobody
cares
about
the
detailed
mechanics
about
how
a
transfer
is
made.
This
has
not
been
a
user
need.
People
have
not
been
saying.
Oh
I
really
want
to
get
understand
how
swift
Works,
how
what's
my
banking
system
doing
under
the
hood
wow
crypto
can
really
expose
the
inner
workings
of
Swift
transactions.
I
haven't
heard
that
from
anyone
and
in
today's
multi-chain
blockchain
world
in
yeah
multi-chain
blockchain
world.
We
require
users
to
understand
what
L2
chains
are
now
in
building
status.
D
I
think
about
my
mom,
my
mom's
over
70
years
old
she's,
a
complete,
technophobe
and
I
want
to
make
something
that
she
can
use
and
she
can
tell
her
friends
about
and
her
friends
can
use
and
if
I
have
to
be
explaining
to
her
what
an
L2
chain
is
I've
probably
failed
at
that
point
yeah.
We
don't.
You
know
if
I
want
to
send
money
to
someone
on
PayPal
I
just
use
their
email
address.
We
don't
want
to
require
multiple
information,
artifacts
yeah
and
asking
people
to
perform
manual.
D
Routing
actions
is
absolutely
crazy,
but
I'll
dive
into
this.
So
back
in
the
good
old
days
when
we
were
just
ethereum
was
new
and
we'd
all
moved
from
Bitcoin
and
it
was
just
ethereum
and
single
chain
token
transfers.
Everything
was
easy.
This
was
a
token
transfer.
So
if
Bob
wanted
to
send
a
hundred,
if
Alice
wanted
to
send
a
hundred
die
to
Bob,
Bob
Bob
would
send
Alice
his
ethereum
address,
or
your
last
name
Alice
would
enter
Bob's
ethereum
address,
select
I
enter
100
sign,
the
transaction
done,
that's
really
easy.
D
D
It
didn't
scale
and
if
we
want
to
bring
crypto
and
especially
in
the
for
payments
and
token
transfers
the
world,
we
needed
something
that
could
do
more
than
50
transactions
per
second,
so
that's
been
the
last
five
years
of
work
with
l2s
and
you
know
now
dank
sharding
and
all
the
exciting
things
that
are
happening.
This
gives
us
the
scale,
but
unfortunately
it's
had
a
side
effect
that
it's
broken
the
token
transfer,
ux
I
think
pretty
comprehensively.
Unfortunately.
D
So
this
is
what
a
simple
token
transfer
looks
like
in
today's
multi-chain
world.
Contrast
it
to
that
it's
horrible,
but
let's
walk
through
it.
Okay,
so
let's
say:
Alice
wants
to
send
100
die
to
Bob.
Today
at
the
conference
and
Alice
has
125
die
in
total
she's
got
25
on
ethereum
mainnet,
25,
down
optimism,
25
down
arbitrum
25
to
100K
sync
and
25
Diane
scroll
all
on
the
same
ethereum
address.
However,
Bob's
wallet
only
supports
ethereum
main
net
and
optimism.
So
what
do
they
do
so
Alice
says
to
Bob.
D
I
would
like
to
send
you
a
hundred
die
and
Bob
says
to
Alice.
Here
is
my
address
and
I
use
ethereum
and
optimism.
So
this
is
our
first
fail.
Both
Alice
and
Bob
need
to
know
what
L2
chains
are.
As
I
said,
I
don't
want
to
have
to
explain
this
to
my
mom,
so
then
Alice
saves
Bob's
address
and
then
Alice
also
tries
to
remember
that
Bob
told
her
that
he
was
only
happy
to
receive
funds
on
mainnet
and
optimism.
D
D
Then
Alice
opens
one
of
the
many
cross-change
bridged
apps
and
uses
it
to
bridge
25
die
from
arbitrim
to
optimism.
So
now
Alice
not
only
needs
to
know
what
else
you
chains
are.
She
needs
to
know
what
cross-chain
bridged
apps
are
okay
and
there's
like
10
or
15
of
them
today
so
and
the
prices
a
lot
of
these
are
balanceable,
so
the
prices
are
changing.
D
D
Now,
unfortunately,
that
bridged
app
didn't
support,
ZK
sync
to
optimism.
So
now
she
needs
to
navigate
to
a
second
bridged.
App
and
Bridge
25
die
from
Z
Keys
Inc
to
optimism,
but
now
remember:
Alice
also
had
25
die
on
scroll
now,
if
Alice
had
no
way
of
knowing
this,
but
it
would
have
been
cheaper
for
her
to
actually
use
a
different
bridged
out
and
do
the
scroll
to
optimism
transfer.
D
Yay
Alice
now
has
25
ethereum,
mainnet
and
75
on
optimism,
and
so
Alice
can
go
back
to
what
she
originally
wanted
to
do,
which
was
send
100
to
Bob.
So
she
does
one
transaction
on
ethereum,
Main
net
to
Bob's,
address
of
25
die
and
another
transaction
on
optimism
to
Bob's,
address
of
75
die
and
finally,
after
about
10
minutes
of
work,
Alice
has
managed
to
send
a
hundred
die
to
Bob
now
I'm,
a
blockchain
geek
I
love
this,
but
even
me
and
understand
how
this
works.
D
I
don't
want
to
spend
10
or
15
minutes,
making
a
single
transfer
to
someone.
You
know
and
that's
this
is
yeah
we're
we're
so
far
beyond
where
we
need
to
be
for
mainstream
adoption
of
multi-chain.
Here,
it's
yeah
we've
got
something
we
need
to
fix
yeah.
So,
let's
reflect
on
it.
Yeah
all
Alice
wanted
to
do
was
said
to
send
100
die.
She
had
to
navigate
to
and
interact
with
two
different
Bridge
steps.
D
D
D
And
now
how
do
I
sell
this?
To
someone
I've
been
telling
them
all
the
wonderful
things
about
crypto
and
then
they
go
to
make
a
transfer
they
run
into
this
and
they
were
like
oh
I'm,
never
doing
that
again,
I'm
going
back
to
PayPal.
You
know
that's
this
this!
This
will
turn
people
off
and
yeah
it's
needless
needlessly
costly,
and
it
requires
far
too
higher
level
of.
D
Blockchain
knowledge
really,
so
we
can
fix
it,
that's
the
problem,
but
wallets.
We
need
to
work
together
to
fix
this,
so
I'll
jump
to
the
conclusion
and
then
I'll
talk
why
this
is
the
answer
so
to
unlock
fixing
all
of
those
problems.
I've
talked
about
us
wallets.
We
need
to
agree
on
standards
so
that
when
one
of
our
users
gives
another
of
users
then
address
it.
Also
that
address
also
signals
which
chains,
the
other
user,
is
happy
to
receive
funds
on.
D
Luckily,
there's
already
a
standard
called
eip3770,
which
pre-pends
change
short
name
to
the
beginning
of
an
address
based
on
lychee's
database
of
change
short
names.
What
we're
doing
at
status
is
we're
extending
that,
so
you
can
prepend
multiple
change,
short
names
and
yeah.
To
be
honest,
we're
happy
to
do
it
in
whatever
way
the
consensus
of
of
wallet
Builders
comes
up
with,
but
I
do
think.
The
most
important
thing
is.
D
We
need
to
agree
a
way
for
users
to
Signal,
which
chains
they're
happy
to
receive
funds
on
for
a
given
address
now,
and
there
are
other
ways
to
do
this
so
like
ens.
In
fact,
ens
already
basically
supports
doing
this,
but
not
all
users
have
ens
addresses
it
costs
money
to
create
an
EMS
address
their
privacy
implications.
So
this
is
a
fallback
for
people
who
don't
have
any
NS
address.
D
D
So,
let's,
let's
unpack
how
this
actually
works
under
the
covers,
so
Alice
says
to
Bob
I'd
like
to
send
you
a
hundred
to
die
and
Bob
sends
his
address
to
Alice.
Now,
with
with
this
address
format,
that
adds
the
change
that
the
owner
of
the
dress
is
happy
to
receive
funds
on
Bob's
wallet
automatic.
Yes,
so
that
Bob's
wallet
automatically
encodes
this
into
Bob's
address
and
Bob
doesn't
need
to
even
know
that
his
wallet
is
doing
this
potentially
and
then,
when
Alice
enters
Bob's
address
into
her
wallet.
D
Alice's
wallet
reads
which
chains
Bob's
wallet
can
receive
receive
funds
from
the
short
name
chain,
IDs
that
are
prepended
to
Bob's
ethereum
address
and
now
Alice's
wallet
can
do
all
the
clever
stuff.
So
add
the
Alice's
wallet,
we'll
look
at
the
type
of
token
Alice
wants
to
send
the
number
of
token
allies
wants
to
send
what
the
balance
of
that
token
is
across
all
the
chains
that
the
wallet
supports
and
has
for
that
address.
D
It
will
look
at
the
chains
which
Bob
is
happy
to
receive
funds
on
that
address.
It
will
look
at
15,
cross-chain
bridges
in
real
time
and
work
out
exactly
which
one
is
cheapest.
It
will
look
at
gas
prices
across
all
the
various
chains
and
basically
it
can
entirely
automate
the
routing.
This
is
an
impossible
problem
actually
for
a
human
to
solve.
This
is
the
type
of
thing
we
invented
computers,
for
so,
let's
use
computers
to
do
this.
A
D
A
D
This
is
just
optionally
abstracting
everything
away
from
the
user,
but
obviously
a
user
can
like
peel
back
the
onion
and
dig
in,
and
you
know,
manually
tweak
parameters
when
we've
done
some
ad
hoc
testing
of
the
designs,
we
have
for
status
that
basically
Implement
all
of
this.
It's
quite
interesting
existing
blockchain
users
kind
of
go.
Oh,
this
is
scary.
What
are
you
doing,
but
people
who've
never
used
blockchain
before
seem
to
be
completely
comfortable
with
it.
So
I
think,
once
we
release
our
product,
that
does
all
of
these
things.
D
Yeah
existing
blockchain
users
will
take
a
while
to
get
comfortable
with
this
level
of
automation,
but
I
think
for
new
user
adoption.
It'll
be
great
yeah,
and
now
we
have
a
token
transfer
experience
that
delivers
usability.
We've
got
back
that
you
know
it's
it's
simple
to
use.
We
have
delivered
to
users,
the
cost
benefits
of
L2
chains
with
and
without
all
the
complexity
of
the
current
multi-chain
token
send
and
yeah
we've
eliminated.
The
two
separate
information
artifacts
that
uses
need
to
needed
to
hold.
D
We've
made
it
possible
for
users
to
send
transactions
in
the
cheapest
way.
That's
available
at
that
point
of
time,
Etc,
so
yeah,
these
usability
costs
and
reliability
benefits
are
all
needed
yeah.
If
crypto
token
transfers
are
going
to
have
have
a
chance
of
breaking
into
the
mainstream
yeah
from
from
earlier
I.
Sorry.
D
Potentially
I've
tried
to
keep
this
proposal
as
simple
as
possible,
just
because
this
is
something
we
need
to
bring
come
to
consensus
on
as
wallet
Builders
and
the
simpler.
It
is
the
better
chance
of
it
happening,
but
yeah
there's
there's
many
ideas
of
ways
it
could
be
extended
in
the
future
and
also
with
different
address
formats
and
things.
Resolver
services
are
a
really
good
way
to
go,
but
I
think
we
need
a
base
layer
address
standard
as.
A
Well,
yeah
I
think
this
topic
requires
a
working
group
for
sure,
so
I'd
want
to
be
respectful
of
other
other
speakers
time.
So,
if
you
guys
do
have
more
questions
and
you're
gonna
kind
of
acquire
Less
in
the
corner
of
this
room,
we
have
the
room
for
the
whole
day
so
you're
more
than
welcome
to
kind
of
like
brainstorm
and
work
on
this
stuff
and
I.
Think.
Thank
you,
John
for
really
like
picking
up
the
Baton,
for
this
is
it's
an
area
that
no
one
has
really
done
any
work
in
in
some
organized
manner.
A
A
E
E
You
know
MS-DOS
or
whatever,
and
we
recently
got
this
email
telling
people
that
we
got
a
shutdown
remix,
because
it's
too
easy
to
scam
people
there
and
we
often
get
emails
from
people
saying
I
lost
my
money
from
this
I
copied
some
code
from
a
YouTube
video
and
lost
my
money.
Can
you
get
it
help
me
get
it
back?
E
So
then
it's
a
question
of
like?
Are
we
responsible
for
that?
Did
we
enable
these
scammers?
What
else
does
he
say?
That's
funny?
Well,
it's
not
really
funny,
but
but
I
beg
you
to
close
your
site,
so
who's
responsible
and
the
choices
are
users
because
they're
the
idiots
that
got
scammed.
Well,
that's
not
really
a
great
thing
to
say:
remix
I,
don't
really
want
to
be
responsible
or
the
scammers.
Well,
they
did
it.
E
But
anyway,
it's
a
discussion
that
we
need
to
kind
of
have
and
in
trying
to
slow
down
the
process.
Do
we
need
to
add
some
friction
now
friction
can
come
in
a
couple.
Different
forms
could
be
warnings,
we've
added
some
warnings
and
remix
and,
as
the
videos
came
out
of
telling
people
to
use
the
this
flashbot
stuff
and
the
scam
videos,
we
added
some
warnings
in
the
home
page.
We
added
some
warnings
there.
E
You
know
people
are
still
getting
scammed,
so
maybe
they're
not
reading
the
warnings
and
also
when
you
deploy
to
mainnet.
You
see
this
modal,
it's
not
about
saying.
You
know,
don't
do
this.
If
you
don't
know
the
solidity
code
that
you're
deploying
it's
actually
about
more
like
gas
fees,
but
anyway
it
slows
people
down.
E
So
it's
a
little
bit
harder
to
deploy
to
mainnet
than
to
any
test
net
and
from
the
remix
docs.
You
know
it's
like
warning
people
not
to
deploy
things.
They
don't
know,
I
mean
they
have
to
dig
through
the
docs
to
get
this.
So
maybe
that's
not
such
a
useful
warning,
but
also
like
it's
a
warning
with
a
little
bit
of
humor,
where,
like
don't
yeah,
don't
use
a
get
rich,
quick
screen
scheme
and
if
you
really
really
want
to
get
rich,
you
know
it's.
E
Maybe
humor
is
a
way
of
getting
the
warnings
to
work
a
little
bit
and
how
many
warnings
are
too
many,
and
when
does
it
get
depressing?
You
know
like
like
this.
You
know
that's
a
warning
to
depress
people
and
if
you
come
into
remix
every
day
and
you
see
like
scam
stuff,
you
know
it's
kind
of
disgusting
or
there's
other
kinds
of
warnings
like
harken.
Stranger
shun
the
danger.
If
you
plan
to
stay
the
same
best
come
back
from
whence
you
came.
E
E
But
you
know
who
defines
what
a
gullible
user
is,
especially
if
you're
trying
to
make
your
tool
accessible
to
everybody
and
look
like
here's.
A
another
sort
of
example,
like
a
table
saw,
is
a
kind
of
a
beautiful
object,
but
it's
got
some
ugly
parts
that
like
finger
protector,
also
like
the
tube
that
takes
out
the
sawdust,
is
a
it's
kind
of
ugly
and
the
stop
button
is
ugly.
But
the
rest
is
like
very
nice
tool.
E
But
you
add
some
of
these
like
protection
features
and
it
makes
the
tool
a
little
more
cumbersome,
maybe
a
more
useful,
maybe
more,
you
feel
more
safer
to
use
it.
But
has
some
problems
like
if
you
extend
this
like
the
in
a
shop
class
in
high
school,
the
teacher
doesn't
want
to
take
responsibility
for
anyone
getting
hurt,
so
they
make
it
impossible
for
any
of
the
students
to
use
the
tool,
because
you
have
to
go
through
all
these
steps
to
use
the
tool.
E
E
Maybe
that
would
temper
people,
but
maybe
it
would
be
obnoxious
itself
and
how
do
we
make
it?
So
it's
not
miserable
and
or
it
could
be
like
more,
like
just
news
like
have
you
seen
that
newspaper
wrecked
it's
really
I
liked
reading
it
I
also
like
reading
the
club,
the
crime,
blotter
and
then,
and
then
all
the
news,
local
newspaper
like
what
the
local
crimes
are
around
me.
E
E
You
know
I,
guess
that's
a
kind
of
delay,
which
is
a
little
bit
like
that
modal
before
we
deploy
to
mainnet,
so
I,
don't
really
want
to
use
too
much
friction,
because
the
whole
idea
is
that
you
don't.
The
guy's
point
was
that
in
other
tools,
like
hard
hat
or
truffle
or
anything,
there's
a
kind
of
setup
and
it
gets
it
kind
of
that
bar
like
stops
a
lot
of
people
or
fresh
beginners
from
using
the
tools
so
with
a
tool
that
we
want
everyone
to
use.
E
You
know
like
in
the
US,
you
have
to
be
over
18
to
sign
a
credit
card,
but
I,
don't
know
how
you
put
that
into
remix,
but
still
there's
certain
kinds
of
thresholds
that
are
used
in
other
Financial
systems.
But
then
you
know
the
credit
card
companies
are
sending
their
credit
cards
to
everybody,
and
people
are
going
to
debt
as
a
result
who
don't
understand
how
to
use
it
and
even
those
who
do
understand
how
to
use
it.
E
The
question
that
you
know
is
another
way
to
ask,
so
maybe
we
can
get
better
warnings
or
better
ways
of
understanding.
What's
going
on,
so
you
know
maybe
they're
more
gullible
because
they're
afraid
of
missing
out
or
maybe
they're
more
gullible,
just
because
it's
it's
a
get
rich
quick
scheme
and
they're
trying
to
enter
the
space.
Someone
shows
them
how
to
do
it.
E
Sort
of
but
I
mean
I'm,
always
afraid
to
deploy
things
to
mainnet.
That
I,
don't
understand,
and
even
things
I
do
understand.
So
I'm
surprised
that
people
have
the
courage
to
follow
these
schemes,
but
they
do-
and
this
just
was
a
thought
that
came
up
after
the
last
talk-
that
maybe
users
see
everything
as
just
so
complicated
they
have
to.
They
want
to
understand
it.
They
want
to
play
with
it.
E
Here's
a
little
bit
of
code,
okay
I'll,
try,
but
they
don't
understand
the
complexities
of
the
whole
system
and
so
they're
just
trying
stuff
out
and
and
they
get
screwed.
So
it's
somehow
to
temper
their
play
is
I.
Guess
is
the
warning
here
and
then
the
other
idea
is
maybe
the
scammers
are
just
very
charismatic
and
seductive,
and
so
I
don't
know.
Can
we
make
warnings
that
are
out
out
seduce
the
seducers?
E
A
You
just
had
a
quick
question:
do
you
think
it
is
like
as
a
remix
is
an
educational
tool?
It
is
your
responsibility
to
worry
about
some
of
this
stuff
or
you're
already
doing
the
service
that
you
are
providing,
which
is
provide
this
playground
for
individuals
to
learn
and
so
forth.
Do
you
think
that's
enough,
or
do
you
take
that
burden
on
yourself
at
this
point.
F
A
H
Yes,
thank
you
Akil,
so
hey,
hey
guys
good
day.
You
know
happy
to
be
here
and
today
I'm
going
to
talk
about
attestations
and
the
ux
challenges
that
we
faced
with
attestations
and
really.
This
is
an
appeal
to
all
of
you
guys
here
the
ux
designers
right
to
really
bring
this
concept
live
into
web3
and
also
help
us
with
the
adoption,
because
we
are
doing
it
as
a
public
good
for
everyone
so
before
beginning
jumping
into
it
right,
jumping
into
the
ux
issues.
H
Let
me
give
you
a
brief
on
what
addressations
are
so
at
the
heart
of
it.
Attestation
is
a
cryptographic
proof
that
is
issued
by
Devcon,
saying
that
this
ticket
is
assigned
against
your
email,
so
go
to
your
inbox
check
out
the
Third
email
from
Deva,
the
Unicorn.
You
have
your
Association
email
there.
So
once
you
click
that
you
go
to
this
page
that
decodes
this
attestation
so
attestation,
even
though
it's
actually
photographic
proof,
it's
encoded
as
a
URL,
and
this
is
decoded
and
stored
in
your
browser's
local
storage.
H
Now,
local
storage
is
considered
as
a
secure
Enclave,
where
the
proof
cryptographic
proof
resides
in
a
relatively
Safe
Way
other
browsers,
other
browsers
or
other
websites
cannot
access
this
in
a
direct
fashion.
Now,
once
you
have
this
proof,
you
can
do
several
interesting
things
now.
The
first
thing
is
that
this
is
readily
usable
by
smart
contracts.
So
you
can
initiate
transactions
on
chain.
You
can
do
things
on
chain,
so
minting
nfts
right.
That
is
something
that
you
can
do
on
chain,
because
you
have
this
cryptographic
proof
now.
H
The
beauty
of
application
is
that
it
does
not
have
to
be
limited
to
Onsen
transactions.
You
can
use
it
off
scene
and
also
you
can
use
it
for
in
person
in
real
life
examples,
because
you
also
can
expose
the
signed
ticket
as
a
QR
code.
Now
this
is
using
the
standard,
cryptographic
methods
and
as
long
as
you
know,
devcon's
public
key
anyone
can
literally
decode
it
and
verify
this
is
signed
by
Defcon
and
it
is
a
ticket
attestation.
H
Now
this
is
the
concept
and
we
are
doing
ticket
as
a
session
because
we
believe
that
before
we
go
into
ticketing
and
before
we
jump
into
nfts
as
tickets,
you
need
to
have
a
step
before
that,
where
it
is
a
ubiquitous
technology,
because
web3
is
not
just
limited
to
on-san
transactions
and
if
you're,
using
something
like
tickets.
Where
for
events,
you
know
you
should
not
restrict
it
to
people
who
only
have
wallet
or
if
you
don't
have
all
of
the
other
solution
is
to
have
a
custodial
wallet,
but
that
sort
of
Beats
the
purpose
right.
H
So
we
are
building
this
piece
of
technology
by
lensing
it
on
one
of
the
most
ubiquitous
things.
That's
there
in
Internet,
which
is
an
email
address,
and
that's
where
you
know
we
are
linking
this
proof
against
and
from
there
it
is
up
to
you.
You
know
it
is
up
to
everyone
to
use
this
attestation
in
a
permissionless
fashion
to
do
whatever
you
want
and
that's
the
vision.
That's
the
idea
that
we
are
trying
to
do.
Okay,
so
that's
a
vision.
That's
we
are
trying
to
do
now.
H
The
ux
challenges
the
first
one
starts
with
the
naming
itself
attestations
before
I
explained
attestations
to
you.
What
did
it
mean
to
you?
You
know:
hey,
you
have
a
ticket
at
the
station.
What
does
it
mean
to
you?
So
we
had
been
having
these
conversations.
Luckily
you
know
for
us,
you
know-
maybe
maybe
not
luckily
for
everyone,
but
we
had,
like
you
know
three
years
to
plan
for
this
because
of
covet,
and
we
had
been.
You
know,
bouncing
these
ideas
with
people,
so
the
first
feedback
that
I
would
always
get.
H
Is
that
now
you
know
at
a
station
it
doesn't
mean
anything.
You
know
you
should
call
it
something
else
now.
What
is
that
something
else?
Certificates
proves,
and
you
know
what
what
happened
all
these
three
years,
nfts
happened
and
until
that
point
of
time
nobody
knew
what
nfts
are
and
now
everybody
you
know
the
kid
night
so
knows
what
an
nft
is.
So
we
thought
that
okay,
maybe
we'll
stick
with
that,
Association,
because
nothing
there
is
nothing
really
that
captures
that
idea
around
having
a
cryptographic
proof
that
can
do
all
these
things.
H
That
can
be
a
core
component
of
how
web3
really
connects
to
the
real
world,
so
we
then
did
that,
but
still
it's
not
understood
just
yet.
So
the
first
challenge
is
naming
it
and
you
know
how
how
to
how?
How
do
we
design
it
now?
The
second
one
you
know
really
comes
into
you
know
again.
You
know,
I
would
say
that
it's
part
of
this
first
challenge
is
how
we
visualize
it,
because
nfts
have
a
picture
associated
with
it.
H
It
has
a
standard
metadata,
but
at
the
same
time
attestation
does
not
have
a
visualization
to
it.
Now
we
went
around
this
Challenge
and
we
visualized
it
as
a
ticket
in
in
the
web
page
and
now
there
are
two
different
states
that
you
can
have
you
go
to
this
web
space
using
a
magic
link
and
you
would
have
a
ticket
there
and
if
not,
you
would
have
a
blank
space
saying
that
you
don't
have
a
ticket
at
a
station
now
even
testing
it
with
users
in
Dev
con.
H
You
know,
if
you
click,
if
you
click
your
magic
link,
you
can
see
that
you
know.
That's.
That's
visualization
is
the
first
one
that
comes
up.
However,
it
is
not
intuitive
to
say
that
you
know
this
is
the
ticket,
and
that
is
the
ticket
attestation
that
you
have
so
we
are
still
working
on
it.
So
I
think
that
you
know
there's
a
long
way
to
go
in
order
to
identify.
H
You
know
how
we
can
visualize
this
thing,
and
the
third
thing
is
that
you
know
even
for
attestations,
even
when
you
have
it,
you
know
loaded
into
your
local
storage
there.
It's
not
complete
yet
because
the
proof
essentially
says
that
Defcon
has
issued
this
ticket
against
your
email,
and
you
know
that's
in
your
local
storage
now
in
order
to
do
any
sort
of
on-sane
interactions.
You
have
to
have
a
second
piece
there,
which
is
what
we
call
as
email
address
session
now.
H
H
Now
the
state
of
how
the
ticket
is
verified
and
where
you
can
use
it,
that
is
still
something
that
we
are
trying
to
figure
out.
What
is
the
best
way
to
communicate
it
to
a
user,
especially
a
user,
who
is
completely
new
to
crypto
and
completely
new
to
web3?
So
you
know
that's
the
first
challenge
that
we
are.
You
know
working
around
and
that's
around.
You
know,
naming
you
know,
definition
and
visualization.
H
The
second
Us
ux
Talent
is
that
browser
support.
Okay,
now
people
use
all
different
kind
of
browsers
now,
but
looking
at
the
devices
that
the
group
that
are
using
associations
today,
it
seems
that
Chrome
and
Safari
kind
of
you
know
encapsulates-
or
you
know,
has
around
85
percentage
of
the
users
are
using
it.
However,
they
are
using
it
on
mobile
they're,
using
it
on
desktop
and
in
order
to
get
some
of
the
complex
logic
working
around
attestations,
it
is
best
to
be
used
on
a
desktop
browser.
H
However,
when
it
comes
to
mobile
browsers,
there
are
so
many
different
channels,
there's
so
many
different
Hoops
that
the
users
have
to
go
through
in
some
browsers.
They
would
have
to
give
the
permissions
in
the
some
browsers.
They
would
have
to
open
up
a
new
tab
and
come
back
so
it's
really
really
hard,
and
especially
when
you
take
it
to
the
wallet
browsers,
the
dab
browsers,
it
doesn't
work
there
at
all.
So
you
know
we
have
so
many
people
coming
in
saying
that
you
know
they're
using
a
smart
contract
wallet.
H
So
smart,
you
know
smart
contract
browser
and
it
doesn't
work
because
the
modern
browsers
have
the
capacity
to
you,
know,
process
and
use
attestations,
but
most
of
these
wallet
browsers
does
not
so
how
a
user
is
navigated
to
the
browser
is
also
a
challenge
now.
The
way
we
go
around
it
is
that
you
know
we
identify
the
device
and
we
show
a
message
that
this
is
not
a
supported
browser.
H
You
sit
in
another
browser,
but
in
not
you
know,
invariably
people
would
still
try
to
use
it
on
a
Dap
browser
and
you
would
get
it
we're
gonna
battle,
so
Nazi.
You
know
second
floor
and
the
last
one
is
that,
in
order
to
procure
a
email
address
session,
which
I
said
that
that's
needed
to
prove
the
complete,
unbroken
proof
from
Defcon
to
issuing
the
ticket
to
you
and
you
having
this
wallet,
there
is
a
OTP
flow
that
you
need
to
go
through.
Okay,
and
we
did
that
for
devconnect.
H
You
know,
devkinand
was
the
first
instance
where
we
shared
it,
share
this
ticket
attestation
with
to
everyone
and
ask
them
to
meet
tickets.
Okay,
and
for
this
user
experience,
people
had
to
clip
through
go
to
the
page
and
then
procure
this
email
address
station
and
from
there
the
biggest
friction
Point
happened,
because
you
know
you
would
have
to
go
to
a
new
tab
because
of
the
restrictions
are
on
iframes
because
of
the
restrictions
about
your
cookies,
and
you
know
all
the
cross
origin
issues.
H
You
had
to
open
up
a
new
tab
and
then
go
to
your
email
address,
get
the
OTP
put
that
into
the
tab.
That
was,
you
know,
opened
up.
You
had
to
close
it
and
then
come
back,
and
then
you
would
have
a
full
attestation.
That's
ready
to
be
used
for
minting,
it
was
really
really
bad
and
you
know
getting
all
the
redirect
flows.
Implemented
was
also
hard.
You
know
we
are
still
working
on
it,
but
hey
for
Devcon.
We
thought
that
this
is
a
New
Concept.
H
Let's
just
take
it
away,
you
know,
let's
just
make
it
so
simple
that
you
know
people
can
still
use
it
so
in
in
the
current
US
that
you
see
right
now,
you
don't
see
this
second
portion
of
you
know
procuring
email
address
sessions
because
we
wanted
to
make
it
as
easy
as
possible
for
anyone
to
adopt
it
now.
Even
then,
what
we
are
seeing
is
that
people
are
getting
really
confused,
okay
and
especially
for
the
nft
minting
process.
H
We
have
made
it
so
simple
that
all
you
have
to
do
is
to
go
to
the
ticket
minting
page
connect
to
your
wallet
and
click
mint
and
after
a
while
the
nft
would
come
through.
Now
we
went
in
a
little
bit
high
on
really
good
videos
and
Graphics
around.
You
know
how
to
visualize
it.
However,
on
iPhones
it
doesn't
work,
you
know
no
surprises
and
people
are.
H
You
know
confused
around,
you
know
how
this
meeting
process
is
happening,
and
the
interesting
question
is
that
have
we
made
it
too
simple,
you
don't
have
to
sign
a
transaction
in
order
to
claim
your
nft
and
I'm.
Seeing
that
you
know
people
are
getting
confused.
Okay,
I
did
not
sign
in
some
transaction
I
connected
my
wallet.
How
is
the
nft
getting
minted
for
me?
So
then
I'm?
Then
we
are
thinking
right.
You
know,
have
we
made
it
too
simple?
Is
there
any
other?
H
You
know
feedback
that
we
should
give
to
the
user
to
make
it
a
bit
more
clear
that
you
know
this
is
how
it
works.
So
anyway,
you
know
this
is
where
we
are
today.
You
know
really
looking
at
you
know
getting
the
meaning
processes
out
getting
to
get
the
feedback
from
the
community.
Now
again,
you
know,
as
I
said
earlier,
this
is
an
open
appeal
to
all
the
designers
over
here
around.
H
You
know,
thinking
about
how
we
could
make
this
open,
Community,
sorry,
open
source
technology,
better,
how
we
can
use
it
to
connect
it
to
the
real
world.
So
you
know
that's
what
we
are
really
looking
for
and
I
have
you
know
I
ask
you
to
go
check
out
your
Digger
data
station
web
page
try
to
use
it
to
claim
some
of
the
permissionless
perks
that
people
are
providing,
try
to
maintain
nft
and
let
us
know
if
you
have
any
feedback.
You
know
right
on
the
bottom
of
the
page.
H
A
Kind
of
sounds
like
you're
damned,
if
you
do,
if
you
and
damned,
if
you
don't
so
it's
interesting
to
see
that
even
making
it
easier
confuses
users
at
the
end
of
the
day,
but
I'm
really
excited
to
have
Kelvin
come
up
and
talk
about
the
the
risk
factors
around
L2
Bridges
and
what
kind
of
systems
we
can
create
around
that.
So
thank
you
very
much.
F
A
F
Yeah
highly
interested
base
layer,
attestation
thing:
okay,
so
I'm
going
to
need
some
like
basic
audience,
participation
to
prove
a
point.
So
you
know
like
how
you
know
raise
your
hand
if
you
know
what
Roll-Ups
are
generally,
you
know
what
layer
twos
are:
okay
kind
of
every
most
people,
all
right,
optimistic
roll
ups.
Right,
raise
your
hand
if
you
know
what
an
optimistic
roll-up
is.
F
If
you
you
know,
if
this
is
what
you
believe,
a
fraud
proof
is
all
right.
Okay
and
then
you
know,
if
I,
if
I
ask
people,
let's
say
you
had
if
I
asked
people
which,
which
blockchain,
which
Roll-Ups
today
have
fraud
proofs,
have
working
fraud
proofs.
Can
someone
can
I
point
at
people
which
yeah
yeah
tell
tell
me
tell
me
which,
which
optimistic
Roll-Ups
have
working
fraud?
Proofs.
I
F
F
F
There's
no
language
that
we
can
use
to
say
what
are
the
real
security
properties
of
these
different
systems
right
and
so
people
say.
Oh,
you
know
we
have.
You
know,
maybe
the
only
roll-up
that
has
working
fraud.
Proofs
is
fuel
V1
and
no
one
uses
it,
and
it
only
really
has
half
working
fraud
proofs
because
it
has
one
implementation
if
that
implementation
has
bugs.
Who
cares
right?
So
we're
faced
right
now
with
two
very,
very
important
problems
in
the
in
the
roll
up
space?
F
F
If
we
don't
do
that,
then
security
is
going
to
come
down
to
marketing
right.
You
can
just
convince
users
that
you're
more
secure
by
saying
these
vague
things
that
are
not
technically
incorrect,
but
no
one
can
really
prove
you
otherwise
and
like,
and
if
you
try
to
argue
about
it,
you're
going
to
start
a
big
fight
on
Twitter
like
I
do
every
other
day,
and
then
this
is
what
happens
right.
Security
becomes
about
marketing
instead
of
real
security
for
users.
So
this
is
problem
number
one
right.
F
How
do
we
come
up
with
a
framework
of
like
this
is
a
more
technical
problem
of
specific
features
that
a
roll-up
or
a
layer?
2
system
needs
to
have
to
be
considered
secure
and
then
the
other
side
of
this
coin
is
that
that
system
of
keeping
things
accountable
doesn't
matter
unless
we
can
communicate
that
to
users
in
an
effective
way.
If
you
go
to,
you
know,
I
love
l2b,
but
if
you
go
to
l2beat
right
now
and
you
look
at
the
risks,
it's
illegible,
it
doesn't
make
any
sense
this.
F
You
know
this
can
do
this,
if
that
it's
just
it's
impossible
for
the
average
user
to
actually
look
at
that
information
and
get
anything
meaningful
out
of
it
and
I
think
the
average
user
really
needs
something
much
simpler
right.
Maybe
that
looks
like
a
score
like
a
you
know
like
like
one
of
those
JavaScript
performance
scores.
Maybe
it
literally
just
comes
down
to
a
single
number
that
says,
or
you
know,
a
rating
out
of
100
whatever
it
is
right,
something
that
just
in
in
the
simplest
possible
terms,
communicates
it
to
a
user.
F
What
are
the
actual
security
properties
of
the
thing
you're
about
to
interact
with?
Because
if
we
don't
people
are
going
to
get
burnt
and
then
they're
going
to
go
and
they're
going
to
complain
about
layer,
twos
and
they're,
going
to
never
use
another
layer
two
again
because
they
thought
it
was
Secure,
because
the
marketing
said
it
was
Secure
and
and
really
and
then
and
then
the
people
who
were
marketing
it
were
saying.
Well,
you
know
we
never
actually
said
it
was
Secure.
We
said
it.
F
F
F
You
know
we
want
concrete
things
that,
if
you're
not
doing
these
things,
the
reality
is
you're
not
secure,
no
matter
how
much
you
say,
you're
secure,
so
we
want
a
list
of
concrete
things
and
then,
on
the
other
side,
we
want
a
way
to
easily
communicate
that
to
users.
I,
don't
know
what
that
looks
like
I,
don't
know
where
the
right
place
is
to
put
that
information.
I.
F
They're
on
the
bridged,
app
they've
already
basically
committed
to
bridging,
so
it's
unclear
where
to
put
this
information
so
that
users
know
ahead
of
time
before
they
even
get
into
the
ecosystem,
because
once
they're
in
you
know,
oh
now,
I
found
out
that
it's
not
as
secure
as
I
want,
but
what
I
have
to
I
have
to
withdraw
now
and
spend
more
money
to
get
out
of
the
system.
It's
just
a
headache.
F
So
the
goal
is:
how
do
we
make
sure
that
users
really
know
the
security
properties
of
the
systems
that
we're
using
and
where
should
that
information
live?
And
what
should
that
information
look
like?
So
that's
what
we're
interested
at
optimism.
Basically,
you
know
how
do
we
we
just
want
to
make
sure
that
our
users
know
what
they're
getting
into
before
they're
getting
into
it.
A
One
of
the
issues
is
similar
when
you
have
staking
providers
is
like
who
does
that
ranking
and
then
is
that
ranking
then
also
somewhat
compromised
by
the
organization?
That's
doing
it
or
who's
financing
them
Etc
like
how
do
you
create
some
sort
of
mechanism
around
what
is
secure?
What
is
insecure,
like
right.
F
I
F
The
low
level
things
and
I
think
fundamentally,
this
is
just
going
to
have
to
be
an
open
thing.
I
mean
optimism
is
very
interested
in
this
for
ourselves,
we
want
to
keep
ourselves
accountable,
and
so,
where
we've
been
working
on
this
internally,
just
as
like
a
checklist
of
things
that
we
need
to
do
to
get
to
real
security
and
so
I
think
an
easy
answer,
is
we
just
put
it
out?
F
There
start
some
type
sort
of
organization
which
is
like
a
you
know,
some
sort
of
Collective
group
of
the
bigger
l2s
and
say
these
are
the
security
properties
that
we're
pitching.
If
you
have
any
ideas
about
security
properties
that
don't
you
know
that
we're
missing
or
a
few
things
that
you
think
these
don't
matter
like
explain
to
us
why?
Why
does
this
matter?
F
A
Another
question
came
in
from
Grammy
from
Argent:
he
wasn't
able
to
attend,
but
he
was
wondering
how
could
he
understand
the
trust
differences
between
the
role
of
flavor?
So
his
understanding
was
that
ZK
Roll-Ups
can
trust
each
other,
but
optimistic
rollups
can't
trust
them,
or
is
that
true,
or
is
the
understanding
flawed.
F
Well,
okay,
you
know
here's
another
thing
right,
it's
like
you,
you
have
so
many
different
axes
along
which
you
want
to
measure
these
things
and
like
a
critical
one
is,
is
bug
risk
right,
like
you
can
have
a
zika
roll
up.
The
whole
point
of
the
proof
system
is
to
prove
the
correct
execution
of
the
client.
F
If
the,
if
the
client
has
a
bug
in
it,
the
proof
system
might
be
perfect,
but
all
of
a
sudden,
the
proof
just
proves
that
the
bug
ran
correctly
and
now
you
can
lose
all
your
money
and
so,
like
I,
think,
there's
there's
so
many
different
angles
that
people
have
been.
You
know
it's
so
easy
to
get
confused
about.
Okay
is
a
ZK
roll-up,
more
secure
than
an
optimistic
roll-up?
F
How
do
you
communicate
that
to
users
saying
you
know
a
system
with
one
proof
is
less
secure
than
a
system
with
two
proofs,
but
if
the
set,
if
the
system
with
two
proofs
was
built
was
has
never
been
tested
on
chain
before,
maybe
it's
less
secure,
and
so
it's
you
know
at
the
end
of
the
day,
there's
too
much
information
to
communicate
to
users.
How
do
you
boil
that
down
into
this
chain
is
like
okay,
secure?
This
chain
is
more
secure
than
this
other
chain
right.
A
Makes
sense
and
then
beyond
that
I
think
what
John
was
talking
about.
Just
the
user
experience
between
bouncing
and
utilizing
these
chains
in
some
time
with
cohesive
manner
is
a
big
challenge
too.
So
I
think
maybe
that
group
could
get
together
and
discuss
some
of
these
things
together
in
some
capacity
and
I
think
the
smart
token
Labs
have
quite
a
bit
of
experience
from
alpha
wallet,
et
cetera
as
well,
so
that
that
could
be
a
good
conglomerate
of
teams
to
get
together.
A
So
the
next
topics,
we're
kind
of
jump
into,
is
I
invited
most
of
the
client
teams
to
come,
participate.
I.
Think
that's
one
of
the
biggest
issues
in
the
ecosystem.
Right
now
is
how
do
we
get
more
people
participating
in
the
network
itself
and
what
are
the
ux
issues
and
areas
that
we
need
to
kind
of
focus
on
so
we'll
kind
of
skip
over
the
attendee
Fishbowl
and
just
go
straight
to
Cindy
who's
from
chainsafe
labs
and
working
on
lodestar
and
other
projects
there.
So
thank
you
very
much
Cindy
good!
J
I
think
it's
refreshing
cool,
so
my
name
is
Cindy
I
work
at
chain,
Safe
Systems.
We
are
a
blockchain
research
and
development
firm.
We
also
make
products
that
help
end
users
out
using
web3
in
their
everyday
cool.
So
in
2020
and
2021
I
worked
on
a
project
called
chainsave
files.
It's
an
encrypted
file
management
platform,
kind
of
like
pad
or
skiff.
The
only
difference
is
that
we
used.
We
put
the
content
directly
on
the
ipfs
and
filecoin
Network.
J
So
I
want
to
share
some
stories
about
what
it
was
like
to
build
on
privacy
for
end
users.
There's
three
challenges:
I
mean
three
challenges:
three
trade-offs
and
some
solutions
and
tips
that
I
can
give
you
guys.
The
first
one
is
designing
for
different
appetites
for
privacy
in
a
single
app
is
really
hard.
We
came
up
with
features
like
exporting
all
your
data
off
via
CLI,
pinning
on
ipfs,
Via,
CLI,
and
also
a
social
recovery
flow
using
web3
auth.
J
J
So
we
use
the
framework
of
asking
ourselves
questions
about
transparency
to
deal
with
this
like.
If
we
add
this
feature,
would
it
diminish
our
users
Trust?
If
we,
if
we
didn't,
show
this
modal
or
if
we
didn't
show
this
hash,
would
it
increase
users,
trust,
and
so
we
argued
endlessly
about?
Where
do
we
put
the
CID
for
the
files
that
are
stored
on
the
filecoin
ipfs
network?
Do
we
show
that,
like
right
in
the
file
browser,
do
we
abstract
it
away?
J
So
those
are
some
trade-offs
that
we
faced
when
we
were
designing
for
different
appetites
for
privacy.
Some
solutions
that
I
I
mean
some
recommendations
and
tips.
I
would
give
you
guys
if
you're
dealing
with
a
similar
issue
is
craft
for
giving
user
flows,
meaning
that
you
should
expect
error.
That's
a
clear
choice.
You
should
also
air,
or,
in
my
opinion
you
should
err
on
the
side
of
showing
too
much
information
but
show
skip
buttons
and
make
them
dismissable
for
the
folks
that
are
used
to
it.
J
We
ended
up
limiting
geographic
information,
so
you
couldn't
zoom
in
on
the
heat
map,
all
the
way
stuff
like
that,
and
then
emphasizing
client
stats
and
upgrade
information.
That
was
a
little
easier
than
dealing
with
end
users,
but
it
was
because
the
community
is
a
lot
more
responsive
and
easy
to
reach.
J
To
summarize
this
point:
it's
sometimes
you
do
things
that
are
ux
sacrilege,
so
you're
working
off
of
like
a
huge
assumption,
you're
filling
in
a
lot
of
the
blanks
yourself
or
your
sample
sizes,
are
just
really
small.
So
the
ways
that
we
tried
to
deal
with
this
is
if
our
sample
size
is
very
small,
try
to
stay
credible
by
keeping
it
one-on-one.
We
would
talk
to
a
nons
async
on
Discord
and
telegram
not
try
too
hard
to
focus
on.
Like
you
know,
sometimes
people
try
really
hard
to
get
you
in
a
calendly
meeting.
J
J
Hence
there's
also
a
proliferation
of
insight
generating
apps
for
users.
Today,
there's
this
really
great
essay
by
Lauren,
McCarthy
she's.
The
creator
of
p5.js,
which
I
love
and
she
says
that
software
is
used
by
many
but
intelligible
by
the
very
few,
and
one
great
thing
from
building
in
a
community
like
this,
is
that
there
are
network
effects
for
blockchain
for
blockchain
technological
literacy,
so
as
Builders
and
designers
I.
Don't
think
this
means
that
we
should
expect
that
people
using
these
platforms
should
be
as
technical
as
us
who
are
building
them.
J
But
we
also
don't
want
to
oversimplify
to
the
point
of
disempowerment
and
learned
helplessness.
What
does
it
look
like
in
practice?
Make?
Don't
trust,
verify
a
user
pattern
and
not
just
a
name
for
a
cultural
movement,
so
that
means
like
showing
people
valuable
information
at
helpful
moments
having
humans
answer,
questions
having
great
docs,
let
your
uis
have
dense
information,
but
make
them
collapsible
and
within
reach
and
yeah
keep
those
routes
open
for
people
to
verify
information
so
yeah.
Those
are
some
stories
that
I
learned
from
building
on
decentralized
apps
for
the
past
two
years.
J
A
J
So
we
showed
things
like
the
content
identifiers,
so
people
can
view
the
content
on
an
ipfs
Gateway
which
looked
a
bit
scary
for
end
users.
They
didn't
like
it,
so
what
we
ended
up
doing
was
putting
it
in
an
info
menu
item
when
you're.
Looking
at
your
files,
like
imagine
a
Google
drive,
there
is
an
info
section
and
then
there's
a
technical
info
section
where
we
tease
the
CID,
but
we
also
show
the
miners,
so
you
can
see
it
on
an
Explorer.
A
J
A
K
Hello,
everyone
from
status
has
introduced
light
clients
I'd
like
to
start
with
two
little
stories.
It's
actually
going
to
tie
into
to
what
Cindy
was
just
talking
about,
which
is
about
how
users
like
to
use
systems,
but
they
don't
necessarily
understand
the
fine
nuances
of
what
they're
doing
when
they're
using
them.
So
I
was
learning
about.
K
You
know
networking
a
few
years
back,
maybe
20
years
back
and
it
was
these
were
really
fun
times,
because
we
used
to
really
trust
the
internet
like
we
were
very
optimistic
about
things,
so
we
didn't
really
think
about
encryption
or
any
of
those
things.
However,
tour
was
coming
up
as
an
anonymity
solution
right
and
if
you
were
running
a
tour
node,
you
could
actually
look
at
all
the
traffic
going
through
and
most
funny.
K
K
K
But
the
cool
part
is
that,
with
these
signatures,
we
actually
have
the
possibility
to
verify
that
the
data
that
we're
getting
from
providers
is
the
data
that
everybody
agreed
on.
What
does
that
mean?
Well,
it
means
that
suddenly,
the
way
we
used
to
operate
in
web
2
was
that
we
would
trust
our
provider
of
data,
we'll
trust
Google.
We
would
trust
our
bank,
we
would
trust
whoever
was
there,
and
why
did
we
do
that?
Because
we
had
a
legal
recourse
to
sue
them
if
they
did
something
wrong?
K
The
systems
that
we're
building
today
we're
kind
of
like
interacting
with
randos
on
the
internet
and
Randall's
out
on
the
internet.
They
might
be
like
me,
like
20
years
ago,
that
was
like
just
looking
at
the
passwords
and
being
very
amused
by
the
naivety
of
people
using
those
systems
and
thinking
that
they
were
Anonymous
and
safe
right
as
Torres
was
presented
at
the
time.
K
K
What
that
does
is
that
it
create
a
model
in
which
data
providers
are
no
longer
have
to
be
trusted.
What
does
that
protect
against?
Well
many
things
inferior,
for
example.
Most
of
us
know
it
alchemy.
Most
of
us
know
it
pocket
Network.
Most
of
us
know
it.
What
we
do
is
that
we
ask
them
for
our
balance.
K
We
ask
them
for
the
state
of
our
nft,
whatever
we
asked
them
to
create
a
transaction
on
our
behalf
and
submit
it
to
the
network,
and
we
hope
that
it's
all
kind
of
fine
submitting
a
transaction,
we
sign
it,
so
they
cannot
manipulate
the
transaction,
but
they
can
manipulate
the
inputs
to
the
transaction.
They
can
give
us
a
false
balance.
K
They
can
say
that
the
nft
belongs
to
you
when,
in
fact
somebody
stole
it
on
the
way
to
you,
the
one
that
sold
it
to
you,
maybe
right
so,
with
the
lifetime
protocol,
we
can
suddenly
create
user
interfaces
that
can
verify
all
the
data
that
we
get
from
all
our
providers
and
then
we
no
longer
have
to
trust
them
to
provide
correct
data.
And
what
does
this
enable
well
on
mobile
phones?
Wallets
that
verify
data
suddenly
become
feasible.
K
We
can
create
smart
contracts
which
understand
that
the
consensus
of
another
chain
has
landed
at
a
particular
block
and
therefore
Bridges
become
more
secure.
We
can
create.
Is
there
a
knowledge
proof
of
all
the
past
history
of
this
consensus
and
with
a
single
small
verification
similar
to
Mina?
We
can
again
verify
that
everybody's
agreed
on
a
particular
state.
K
So
if
I
was
doing
my
experiment
today
on
Tor
I
would
notice
that
everybody
uses
https
right.
Everybody
uses
SSL,
everybody
encrypts
the
traffic.
There
are
no
more
email
providers
that
allow
you
to
log
in
without
a
secure
connection,
and
I
would
argue
that
six
months
from
now
there
will
not
be
a
single
wallet
out
there.
That
does
not
verify
the
stuff
that
you're
getting
from
your
data
provider
using
the
light
client
protocol
and
that's
the
world
that
I
want
to
see.
K
So
if
anybody
is
working
on
wallets,
if
anybody's
working
on
any
kind
of
tooling
join
me,
I'll
be
happy
to
explain
the
protocol,
we
have
libraries
available
that
you
can
just
include
in
your
application
that
allow
you
to
add
this
functionality
like
at
minimum
cost.
If
you're
a
user,
we
have
a
proxy
so
that
you
can
run
this
little
mini
node
in
your
like
home
setup.
K
It
uses
almost
no
bandwidth
and
what
it
does.
It
sits
between,
say,
metamask
and
and
and
you're
inferior,
and
when
your
metamask
makes
requests,
it
verifies
all
those
all
that
information
that
is
getting
from
infuria
using
the
like
line
protocol
and
it
will
block
any
data
that
is
not
valid.
According
to
the
consensus
that
everybody's
agreed
upon.
A
K
What
we're
relying
on
inferior
for
is
that
they
become
like
a
static
data
provider,
so
they
still
analyze
the
chain
they
run.
They
run
the
node
for
you
and
so
on,
and
when
we
ask
for
data,
they
give
you
the
balance,
for
example,
and
they
give
you
a
cryptographic
proof
of
how
they
came
to
that
conclusion,
that
your
balance
is
5,
8
or
whatever.
K
C
K
They're
still
very
valuable,
because
this
is
basically
the
lowest
bandwidth
way
to
get
data
available
today,
I'm
saying
today,
because
we're
also
working
on
another
project,
where
the
data
itself,
where
you
can
swap
out
infuro
for
a
decentralized
range
of
servers
that
will
be
providing
those
data
points.
But
even
in
that
solution
you
don't
know
if
the
data
you
would
be
getting
from
from
the
network
would
be
true.
So.
C
A
Work
so
quick
question
from
a
user
perspective.
How
do
you
convince
people
that
they
now
would
benefit
from
running
some
of
these
services
and,
as
we
know
from
past
experiences
that
once
people
get
into
a
habit
of
relying
on
third-party
intermediaries,
it's
really
hard
to
convince
them
to
now
take
on
more
responsibility.
So
what
do
you
think
as
a
community
like
what
kind
of
education
or
work
we
need
to
do
for
people
to
realize
like
this
would
be
a
good
value?
Add
for
everyone
to
be
running
on
their
own
devices.
K
K
We
can
provide
something
that
is
lightweight
enough,
that
the
third
party
providers
become
just
data
stores
like
a
hard
drive
basically,
and
the
journey
is
the
same
Journey
that
we
did
from
unencrypted
internet
to
encrypted
internet
right
now,
everybody
expects
a
little
icon
that
you
know
their
connection
is
safe
and
and
the
certificate
is
valid
and
blah
blah
blah
I.
Imagine
that
a
wallet
would
want
to
show
that
it's
validated
the
data
coming
from
the
provider
using
a
Lifeline
solution
like
this
in
a
similar
fashion.
K
L
So,
during
the
process
of
these
hard,
forks
I
was
able
to
interact
with
a
lot
of
our
users
and
notice.
There's
some
areas
that
could
increase
adoption
in
ethereum
staking
so
today,
I'm
just
going
to
go
over
a
couple
of
these
areas.
That
I
have
some
opinion
on
and
then
shed
some
light
in
the
staking
infrastructure
in
general.
L
So
the
first
opportunity
I
see
is
around
service
management
and
it's
as
as
we're
growing
in
this
staking
Community.
There's
all
these
other
tools
that
you
can
add
in,
but
connecting
these
and
enabling
these
for
our
users
might
not
necessarily
be
in
the
protocol
specs,
so
designing
the
consensus
clients.
We
follow
these
protocol
specs
defined
by
the
ethereum
foundation.
L
However,
there's
plenty
of
other
things
that
aren't
defined
in
those
specs
and
client
teams
have
a
lot
of
Lee
leeway.
So
one
example
is
when
I
first
started.
Prism
was
the
only
client
with
a
UI.
All
other
clients
did
not
have
UI
capabilities
and
they
did
not
have
apis
to
allow
management
of
their
keys.
L
So
that's
just
one
example,
but
as
we
continue
to
grow
now,
there's
plug-ins
like
web3
signer
for
remote
signing.
If
you
don't
want
to
include
your
validator
keys
in
the
validator
itself
and
in
the
validator
client
itself,
then
you
can
use
this
third-party
tool
called
web3,
signer
and
prism
supports
that
I
believe
most
of
the
client
teams
support
that.
L
We
do
need
Community
Support,
like
what
do
we
need
to
add,
as
integration
into
the
system
and
also
with
withdrawals
coming
so
there's
a
lot
of
different
areas
where
plug-ins
can
be
attached
to
these
clients
and
it's
sort
of
not
part
of
the
protocol
spec.
So
we
need
some
feedback
from
the
community
so
with
more
and
more
services
being
built
and
pieced
together.
There
are
a
lot
of
opportunities
to
align
the
user
experience,
even
if
it's
not
part
of
the
protocol
spec.
L
The
next
topic
that
I
wanted
to
talk
about
was
improving
the
user
Journey
for
entering
test.
Nets
I
think
that's
an
area
that
we
could
really
improve
as
right.
Now
you
need
to
get
your
Gorly
eth
through
Discord
or
social
media
or
like
really
sketchy
sites
or
just
connections
with
with
certain
people.
L
And
so,
typically
at
your
traditional
tech
company,
you
would
go
through
your
local,
develop
the
software
on
your
local
move
to
a
Dev
space,
move
to
a
test
space
and
then
into
production.
If
you're
working
on
staking
or
developing
in
the
defy
space-
and
you
want
to
run
your
own
node,
it
should
work
in
a
similar
fashion.
I've
heard
people
try
to
do
a
deposit
contract
and
then
just
directly
go
into
mainnet
without
any
experience
in
staking
at
all.
So
it's
really
important
to
try
to
increase
this
adoption.
L
So
all
in
all,
this
is
a
call
to
action
to
developers.
There
are
a
lot
of
opportunities
in
this
ecosystem
without
knowing
Premier
knowledge
on
cryptography
for
Choice
consensus
knowledge
of
how
the
evm
works.
So
there's
a
lot
of
opportunities
just
in
how
these
microservices
or
Services
interact
with
each
other
and
helping
the
community
create
better
standards
and
result
in
a
better
user
experience.
Thank
you
very
much.
Thank
you.
So.
A
I
had
a
few
questions
touching
on
some
of
the
points
that
you
kind
of
raised.
The
first
one
was
around
like
the
the
the
standardization
work
that
you
guys
did
for
the
key
manager
stuff.
What
were
the
challenges
there?
How
did
you
guys
actually
get
the
community
because
I
know
on
the
back
end,
we
try
to
create
a
lot
of
Discord
channels.
Have
those
conversations,
then,
eventually,
you
and
Michael
were
able
to
kind
of
push
it
through.
L
We
were
actually
trying
to
push
that
through
through
the
East
Staker
community,
so
consensus
teams-
all
core
devs,
are
very-
are
on
a
very
tight
schedule.
They
want
to
get
the
protocols
done,
so
these
things
usually
fall
on
the
Wayside
and
actually
dap
lion,
so
I'm
calling
out
load
start
Team
was
the
first
one
to
take
initiative,
create
that
PR
and
ask
the
community
whether
or
not
we
could
include
this.
L
So
he
actually
went
to
the
beacon,
API,
specs
and
created
a
PR,
took
that
initiative
and
got
the
ball
rolling.
Now.
The
next
step
is
people
reviewed
it.
They
had
comments
on
it,
but
it
that
wasn't
enough
to
get
all
the
client
teams
aligned
together
so
that
took
some
more
social
engineering,
a
lot
of
trying
to
reach
out
to
one
person
connect
to
the
next
person
and
get
everyone
together.
So
a
lot
of
help
from
the
East
Staker
Community
to
try
to
push
this
through.
L
A
So
I
think
the
other
question
is
now
that
the
merges
happened
and
maybe
there's
some
more
capacity
available
in
these
teams.
Is
this
something
that
the
client
teams,
maybe
other
client
teams,
can
weigh
in
this,
as
well
as
like?
Is
some
of
this
becoming
more
of
a
priority
for,
or
resource
allocation
being
put
towards
this
or
not,
really
I'll?
Take
that
as
a
no
so
like?
How
do
we?
How
do
we
move
those
conversations
forward?
L
That's
that's
why
I
wanted
to
do
the
stock
in
the
first
place,
to
try
to
get
a
call
to
action
to
developers
as
we
move
from
the
merge
to
The
Surge
now,
client
teams
will
be
even
more
focused
on
protocol
level
decisions.
So
the
next
three
things:
censorship,
resistance
with
Mev
scalability
with
eip4844
and
withdrawals,
so
client
teams
are
pretty
much
very
focused
on
that
and
the
continuing
development
around
Fork
choice
and
protocol
level
design.
L
A
That
kind
of,
like
perfectly
segues,
into
Landscapes,
talk
from
that
node,
where
their
challenges
they're
facing
as
far
as
like
integrating
some
of
these
clients
in
the
first
place
into
their
services
and
the
front
end
that
they've
built
out,
which
is
amazing
as
far
as
like
just
running
these
services
in
a
preview,
terrific
configure
device
or
application.
As
a
stance,
you
can
just
connect
here.
If
you
wish-
and
this
is.
A
Have
to
join
because
he
has
a
session
right
now
actually
happening.
So
perhaps
we'll
do
a
quick
lighting
plot
from
him
after
lunch
if
he
is
able
to
join.
But
aside
from
that,
I'd
be
curious
to
get
some
of
the
the
individuals
working
on
the
front
end
to
have
a
discussion
on
like
what
we
can
do
to
move
some
of
this
stuff
forward
as
well.
M
All
right
all
right,
thank
you.
James
I
think
this
was
a.
This
is
a
great
great
summary
of
of
what
we're
doing
as
Community
from
the
community
side
as
integrators
that
we
need
to
make
the
ux
easier
for
for
them
for
the
users
right,
so
that
node
very
briefly,
we
we
help
people
run
nodes.
We
help
people
run
validators
or
nodes
or
anything
you
want
by
providing
these
free,
open
source
software
that
you
can
install
in
any
machine
and
it'll
turn
it
into
well.
M
It's
actually
Linux
and
it's
Docker
based
and
any
machine
that
you
install
is
in
it'll,
give
you
this
set
of
tools
to
manage
nodes
in
a
like
in
a
super
easy
way
right.
So
you
would
go
here
and
you
decide
that
you
want
to
install
like
a
pocket
network
node
or
a
nimbus
or
whatever
it
is,
and
dab.
Node
has
been
a
really
good
solution
lately
for
for
those
who
want
to
validate
and
and
they
maybe
they
don't
have
the
technical
knowledge
right.
M
M
That's
that's!
That's
something
that
if
you're
a
validator,
if
you're
a
solo
Staker-
and
you
want
to
test
those
as
James
was
saying-
we
need
please
do
test
those
in
testnet
before
you
would
need
a
couple
of
hours
for
for
each
of
these
to
test
each
of
these
new
releases
right.
That's
72
hours
a
year
on
testing
on
on
testing
and
deploying
the
the
new
versions
of
the
nodes.
So
there's
there's
a
lot
that
that
note
does
in
the
integration
side
that
it
just
works.
M
M
The
docker
images
are
distributed
through
ipfs,
so
ipf
has
that
note
has
an
ipfs
node
inside
and
it
also
has
an
ethereum
node
inside
so
you're,
actually
never
calling
home
you're
using
nodes
in
your
machine
to
to
take
the
and
to
get
the
the
content
to
download
to
know
what
the
content
is
available
and
to
get
this
content
into
your
computer.
Okay.
M
So
back
to
the
story
that
James
was
saying
we're
trying
to
make
it
super
easy
for
for
people
to
stake
with
no
technical
knowledge
right
and
one
of
the
problems
that
we
had
was
that
there
was
only
one
client
with
a
UI
which
was
prism
and
we
that
Lion
at
that
moment
was
already
working
on
load,
sir,
but
he
was
a
he
was
already.
He
was
also
working.
M
A
dab,
node,
so
actually
I
was
I
was
very
involved
on
on
kicking
kicking
off
this
initiative
of
the
key
manager
API,
because
it's
something
that
we
needed.
For
that
note,
we
needed
the
key
manager
API,
so
people,
so
we
could
have
client
diversity
in
dub.
Note
right
now.
Do
we
have
World?
Well
I'm,
not
gonna,
go
on
this
story.
M
Any
longer
we'll
see
the
the
UI
later
there's
still
a
lot
of
problems
like
dapno
itself
has
is
not
free
of
its
own
problems
and
when
you,
when
you
try
to
validate
with
that
node
you'll,
find
that
you
need
to.
You
need
a
lot
of
previous
knowledge.
You
know
a
lot
of
reading
up,
but
you
need
to
know
you
need
to
know
that
you
you
don't.
What
is
a
note.
A
note
has
changed.
M
The
definition
of
a
node
has
changed
now
you
need
an
execution
layer
and
you
need
a
consensus
layer
and
you
need
both
and
then
you
need
a
validator
client
and
then,
if
you
want
to
manage
the
keys
you
need,
which
is
what
we
do
in
in
that
note,
and
you
need
this
UI
to
to
input
and
output
the
keys.
You
will
need
a
UI
for
this,
and
how
do
you
find
those
packages
in
here?
There's
taku,
there's
Lighthouse
nurses,
but
there's
also
Lighthouse,
there's
numbers.
There's
numbers
there's
take
a
pratter,
there's
SSV
product.
M
It's
like
it's!
It's
chaotic!
It's
like
okay!
We
need
to
guide
the
users
better.
So
that's
what
we
are
working
on
right
now.
That's
what
we
did,
which
is
so
it
looks
like
okay,
because
it's
it's
not
beautiful,
but
it's
very
functional
and
it
guides
the
user
to
do
whatever
it
needs
to
do.
It
says:
Hey
choose
an
execution
client
and
you
can
choose
on
this.
Three:
hey
choose
a
consensus:
client,
hey
and
it'll.
M
Choose
this
one
or
these
four
it's
funny,
because
top
lion
has
been
working
on
dabnode
for
most
of
his
career
and
guess
which
consensus
client
is
not
in
tab.
Node,
lodestar
lion
get
your
together
come
on,
then
the
web
designer,
which
maintains
the
keys-
and
this
is
a
really
key-
ux-
Improvement-
that
the
fact
that
the
keys
are
in
the
web
designer,
because
now
you
can
thanks
to
the
checkpoint,
seeing
by
the
way
really
good
work,
client
implementers
things
in
the
checkpoint
thing.
M
You'll
be
validating
in
like
two
minutes:
you'll
be
online
and
validating
in
two
minutes:
there's
literally
no
switch.
Another
thing
is
that
you
cannot
it's
another
thing
that
we
need
to
manage
in
the
background,
for
the
user
is
the
fact
that
you
cannot
have
two
consensus
clients
pointing
at
the
same
execution
client,
so
we
take
care
of
turning
it
off.
We
took
it.
We
take
care
of
all
the
these
little
edge
cases
and
little
things
to
make
it
super
simple
for
the
user.
M
So
now,
let's
look
at
the
keys.
Why
are
the
keys
in
the
in
the
web
designer
the
keys
are
in
the
web
designer?
So
when
I
change,
this
I
don't
need
to
take
the
keys
out
of
one
package,
remove
them
change,
download
the
other,
put
the
keys
in
there
and
then
start
validating.
This
is
a
recipe
for
disaster.
You,
if
you
forget
that
your
keys
were
in
the
other
client
double
signing,
slash.
A
M
M
So
in
that
note,
because
of
the
way
it
works,
and
because
we
try
to
not
to
make
it
super
complicated
it
it
when
you
configure,
it
uses,
pass
the
value
of
the
few
recipient
address
and
that's
all
of
the
keys
go
there.
So
this
UI,
where
you
have
the
list
of
keys
sorry
I,
could
have
put
some
some
fake
Keys
here
wow,
but
it
doesn't
have
this.
M
It
doesn't
have
this,
and
why
doesn't
it
have
this
because
there's
no
standard
there's
no
standard
for
changing
this
so
right
now,
if
we
want
to
do
it,
we
need
to
create
any
a
specific
implementation
per
each
client,
using
whatever
system
that
each
client
has
on
how
to
change
the
validator,
so
the
prcbn
for
each
validator
key.
So
this
is
one
of
the
things
that
we
are
going
to
be
pushing
just
like
we
push
for
the
key
manager
API.
This
is
one
of
the
things
that
we're
going
to
push
in
standardization
guys.
Standardization
is
key.
M
I
understand
that
the
the
consensus
teams
are
super
busy
and
the
work
that
you're
doing
is
incredible
and
wasting
time
on
coordination
might
seem
like
yeah
like
a
waste
of
time,
but
then
it
will
have
to
to
be
done
later.
Somebody
you're
just
kicking
the
bucket
right,
like
it
will
have
to
be
done
by
somebody
later
on
and
there's
literally
nobody
better
than
you
to
decide
on
a
simple
way
of
doing
it.
So
we're
going
to
be
pushing
for
this
in
the
next
or
in
the
next
round.
M
We're
gonna
do
something
similar
than
what
we
did
with
the
key
manager.
Ui
intake
manager,
API,
but
then
there's
going
to
be
something
else.
There's
going
to
be
another
thing
that
needs
to
be
integrated,
there's
going
to
be
another
thing
that
makes
it
that
makes
life
easier
for
the
users,
so
I
would
I
would
hope
that
initiatives
like
this
get
us
all
together
in
a
room
and
see
like
hey
what
what
problems
are
we
having?
What
problems?
Are
we
having
and
one
side
one
pro
one?
M
A
Yeah
so
I
think
we've
seen
there's
two
opportunities
for
Clear
working
groups
to
happen.
One
is
the
wallet
one.
One
is
probably
client
team
integration
and
standardization
Adrian
did
have
some
ideas
around
standardization
that
he
wanted
to
push
as
well,
so
I
think,
maybe
even
if
he
can't
get
it
in
person,
maybe
I'll
create
a
back
Channel
communication
to
just
kick
start
some
of
this
stuff.
But
beyond
that,
I
think
some
people
might
want
to
have
other
conversations
that
are
in
the
room
that
we
might
have
not
given
too
much
priority
towards
so
before.
A
We
just
go
to
off
to
lunch.
If
anyone
just
wants
to
come
up,
ask
any
questions
or
wants
to
just
do
like
an
open
mic
session
about
some
other
issues
that
they
are
very
passionate
about.
Would
love
to
kind
of
give
you
guys
the
opportunity,
because
we
were
a
bit
behind
schedule,
so
I
didn't
give
opportunities
for
people
to
ask
questions
from
all
the
different
speakers.
A
A
G
Thank
you
for
hosting,
and
thank
you
for
speaking,
everybody
I
had
a
question
about
improving
the
accessibility
of
staking
very
much
along
the
lines
of
what
James
has
been
talking
about.
You
know,
I.
Think
I
could
convince
my
mom
to
try
and
create
a
wallet
like
a
metamask
wallet
on
Chrome
I.
Don't
think
I
could
convince
her
to
wrap
her
head
around
the
complexities
of
you
know
what
is
a
node?
What
how
do
you
define
a
node?
How
do
you
think
about
it?
G
What
I've
been
thinking
about
a
lot
is:
how
close
are
we
to
getting
to
a
point
where
somebody
completely
non-technical
could
in
two
steps
you
know,
download
an
app
deposit,
Eve
and
run
a
node
and
then
maybe
under
the
hood.
Whatever
solution
that
is,
could
just
roll
a
dice
choose
a
client
choose
elcl
automatically,
maybe
create
or
yeah
I,
don't
know,
I
guess.
The
main
question
is:
how
do
we
get
to
a
point
where,
where
it's
as
simple
as
one
two,
how
far
away
are
we
from
that
I
know?
G
Standardization
is
a
big
part
of
that,
but
maybe
even
without
standardization
it
would
be
possible
and
some
assumptions
could
be
made
that
could
be
tested
and
then
that
testing
could
influence
standardization
sort
of
in
a
backwards
backwards
way.
So
what
are
your
thoughts
on
that
I'm?
Addressing
it
to
you,
because
you
were
talking
about
a
lot
of
this
stuff,
but
anyone
feel
free
to
love.
A
C
G
Yeah
I'm
kind
of
bundling
the
run
and
node
stake
Ethans
into
a
single
bucket
and
thinking
about
how
do
we
pull
that
activity
along
the
technology
adoption
curve
by
making
it
so
simple
that
you
don't
need
to
understand
technical
terminology,
but
you
do
want
to
participate
in
decentralizing
digital
economy
like
you
philosophically
or
maybe
your
values
are
aligned,
but
your
knowledge
and
your
technical
familiarity
is
the
the
limiting
factor.
So
assuming
that
you
have
values
that
align
but
not
technical,
familiarity,
I
feel
like
there's.
A
G
G
M
M
Well,
let
me
start
from
the
beginning,
like
the
we
can
take
an
approach
of
like
free,
open
source
software,
but
that's
not
the
approach.
That's
gonna
get
us
this
Mass
adoption
right,
because
then
you
need
a
Linux
installation.
You
need
like
this
all
this
sort
of
stuff
that
it
doesn't.
That
will
not
make
it
happen.
That
will
just
people
will
not
do
that.
So
what
we're
doing
as
well
we're
selling
Hardware
we're
selling
Hardware
that
comes
pre-installed
and
you
just
plug
and
play
you
plug
it
to
your
router.
M
You
turn
it
on
either
it's
a
hotspot
and
then
you
can
connect
and
configure
your
VP,
your
VPN,
and
then
you
can
go.
You
can
enter
and
access
this
machine,
which
is
effectively
a
server
that
lives
in
your
kitchen.
But
we
didn't,
we
didn't
call
it
a
server,
because
that's
scary,
we
call
it
your
dap,
node,
home
and
and
yeah
you
can
access
from
wherever
you
want.
So
these
machine
first
of
all,
the
first
hurdle
is
that
that's
a
different
mentality.
That's
that's!
M
Not
a
free,
open
source
mentality
of
like
I'm
gonna
hack,
a
node
I'm
like
that
changes.
It's
like
I
buy
this
machine
and
I
expect
to
have
a
return
from
it
and
here's
the
this
links
very
well
with
what
you
were
saying
about.
You
can
run
a
node
without
validation,
but
that's
not
going
to
happen.
That's
not
going
to
happen.
M
We've
been
written
up
note
since
2017
we've
been
trying
to
get
people
to
run
nodes,
and
we
only
got
big
download
only
got
users
non-technical
users
when
there
was
incentives
to
run
this
note
when
there
was
money
on
the
line
when
there
was
a
way
of
doing
this.
So
now
we
have
this
first
step
where
people
are
have
to
buy
something
because
they
don't
have
the
the
the
the
experience
of
like
of
like
how
to
install
Linux.
M
Whatever
people
have
to
buy
something
and
then
there's
the
incentives
and
they
if
they
buy
something,
what's
their
expectation,
there's
an
expectation
of
return
and
then
then
it
just
becomes
easy
on
the
implementation,
because
what
you
have
seen
what
I
was
showing
on
dab
node
is
three
call
this
this
column
like
thing
or
you
got
to
choose
your
execution
client.
You
got
to
choose
your
consensus
line
this.
We
could
have
like
an
API
that
says
that
automatically
chooses
whatever
combination
is
the
least
used.
M
So
in
DAV,
node
we're
thinking
about
doing
that
and
then
having
the
advanced
mode
is
like
you
choose
yourself,
but
then
there's
like
a
set
of
constraints
of
like
what
we
want
to
do
in
Davenport
as
well.
Maybe
somebody
else
like
a
competitor,
that's
less
focused
on
under
centralization,
because
we
don't
want
to
be
calling
any
apis
like
we.
What
do
you
have
on
your
machine?
Is
yours
and
you
never
go
home,
there's
no
Telemetry.
M
A
C
A
Network
and
the
services
people
are
using
so
the
way
that
like
status
is
looking
at.
It
is
like,
if
you're
running
your
nodes
for
messaging
or
all
these
other
services.
Now
you
have
a
utility
or
a
factor
for
not
bunching
in
your
ethereum
clients
there
as
well.
So
now
you
have
this
like
whole
Vision
or
like
this
window
into
web3,
that
we
were
kind
of
like
promised,
with
the
the
miss
browser
where
you
have
the
ability
to
control
all
your
web3
services,
and
then
it
just
makes
a
little
bit
more
sense
for
users
to
say.
A
It
just
becomes
a
little
bit
easier
to
not
just
plug
in
an
ethereum
client
there
as
well,
so
I
think
there's
two
layers.
It's
like
do
people
comprehend
their
whole
vision
of
web3
and
how
that
comes
together
and
then
the
other
one
is
like.
How
do
you
incentivize
individuals
to
run
that
infrastructure
structure
without
it
being
staking
so
like
if
you're
looking
at
individuals
in
Bogota
or
looking
at
individuals
in
India
or
looking
at
individuals
in
Africa
for
them
to
actually
run
those
nodes
and
then
decentralize
the
ecosystem?
A
Further,
and
maybe
there
is
some
sort
of
like
incentive
mechanism
that
we
can
come
up
with,
where
they're
benefiting
without
having
to
put
out
their
cash,
which
is
33.
There
is
too
much
for
them,
even
if
they
do
like
distributed
validated
technology
if
they're
providing
a
service
to
the
network.
Perhaps
there
is
some
sort
of
incentivization
that
kind
of
is
given
to
them
at
that
point
in
the
in
the
long
term
of
like
okay,
we
decentralized
the
ecosystem
not
to
just
Europe
and
America
at
that
point,
so
I
think
there's
a
lot
of
thinking.
A
That
needs
to
be
done
from
like
the
protocol
level
or
just
from
the
community
like
funding
mechanism
perspective
there
as
well.
So
it
was
interesting
to
see
like
how
we
start
thinking
about
these
problems
over
the
next
few
coming
years.
Now
that
the
proof
of
stake
ecosystem
is
kind
of
developing
and
it'd
be
exciting
to
kind
of
have
thinkers
like
you
guys,
come
up
with
ideas
and
experiment
and
evangelize
as
well.
So
thank
you
very
much.