►
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/ups-and-downs-onboarding-a-million-users-to-layer-2/
In the last year we’ve seen thousands of projects and billions of dollars migrate over to rollups. Liquidity and users have started aggressively migrating, but there’s still a long way to go. In this talk we’ll cover successful use cases, pain points that make it challenging for both users and developers to onboard, and emerging projects and protocols in the layer 2 space that are showing a lot of promise.
Speaker(s): Matt Pearring
Skill level: Beginner
Track: Layer 2s
Keywords: Onboarding,Rollups,Layer-2
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
A
So
three
things
I'm
going
to
try
to
cover
here,
there's
a
lot
of
stuff
going
on
in
Layer
Two.
There's
a
lot
of
stuff
going
on
in
crypto,
I'm
gonna
try
to
focus
on
three
things
last
one
and
it
was
broad
talk
about
bridging
talk
about
compatibility
and
interop
and
I'm
going
to
talk
about
some
scalability
issues
that
I
think
we're
starting
at
coalesce
around
that
we
have
been
talking
about
for
a
while,
all
right,
so
bridging
right,
you
got
to
move
funds
from
layer,
one
to
Layer
Two.
At
some
point.
A
This
shouldn't
be
something
you
have
to
think
about
right.
So
we
want
it
to
be
there.
We
want
there
to
be
zero
degrees
of
separation
between
the
layers
at
some
point.
In
the
end
game
right
you
Bridge
right
onto
Layer
Two.
So
here's
where
we
are
today
it's
a
state
of
bridging
it
continues
to
be
really
challenging
and
continues
to
be
risky.
We
see
hacks
all
the
time.
It's
not
great,
but
it's
something
that
we
have
to
deal
with.
Ux
for
users
is
tricky
or
even
impossible,
depending
on
the
asset
right.
A
Not
all
tokens
are
your
320s.
Sometimes
you
can't
Bridge.
Sometimes
you
have
to
bridge
in
a
different
way,
so
it
becomes
really
challenging
for
someone
trying
to
use
any
kind
of
crypto
product
in
the
beginning
when
you
have
to
educate
them
on
what
bridging
is
and
what
that
means
is
for
developers.
Not
all
token
implementations
are
created
equal
on
Arboretum.
We
have
standard
versus
custom
bridging
so
when
you're
bridging
an
asset
over
for
the
first
time,
we
can
deploy
that
contract
for
you
on
Layer
Two
and
it'll
Auto
it'll
Auto
deploy
but
yeah.
A
If
you
have
things
like
interest
or
or
other
things
that
are,
you
know,
maybe
more
custom
for
implementation.
You
have
to
work
with
us
or
you
have
to
you
know,
build
your
own
custom
solution.
So
it's
pretty
complicated
and
I
think
you
know
we're
not
in
a
space
where
things
are
perfect,
but
we're
making
a
lot
of
progress
and
kind
of
at
a
higher
level
view.
This
is
our
Bridge.
You
know
fantastic
we're
from
the
team,
but
if
you
think
about
it,
bridging
is
really
designed
for
power
users
right.
A
So
it's
not
something
that
in
the
long
term,
we
want
to
have
be
kind
of
like
the
canonical
thing
you
have
to
do
on
on
the
blockchain.
So
what's
next
right
and
again,
this
is
a
lightning
talk.
I'm
trying
to
go
as
fast
as
I
can
one
thing
that
we're
exploring
is
fast
withdrawal
confirmation.
So
on
arbitrum
Nova
we
have
a
data
availability
committee.
A
A
Let's
see,
yeah
something
that
we're
you
know,
we'd
like
to
see
happen
and
the
ecosystem
is,
is
more
wallet
integration.
You
know
deep
well
in
integration,
I
would
say
with
fast
bridging.
So
when
you're,
you
know
in
a
wallet,
you
have
an
asset,
you
can
just
use
a
fast
Bridge
from
within
there.
You
don't
have
to
go
on
the
browser
and
actually
sort
through
all
these
options
and
make
trade-offs
with
your
own
independent
research.
You
can
actually
have
that
be
like
automated
for
you,
obviously
that's
going
to
require
kind
of
community
discussion.
A
This
is
just
something
that
goes
without
saying.
It
was
something
that
we've
done.
A
lot
of
work
on
is
within
the
bridge
itself,
increasing
discoverability
of
fast
Bridges
and
making
sure
it's
more
performant
right.
Not
all
bridges
are
created,
equal,
there's
lots
of
different
options
and
so
doing
what
we
can
from
an
agnostic
perspective
to
make
sure
that
we
provide
the
best.
Ux
is
something
that
we
try
to
do
all
the
time
and
something
I'd
like
to
see
long
term
is
Bridge
aggregation,
standard
functionality
right,
there's
lots
of
trade-offs.
A
So
sorry,
I'm
going
really
fast,
but
the
next
thing
I
want
to
talk
about,
is
kind
of
compatibility
right,
so
we're
in
a
good
state.
Right
now
in
Arboretum
on
a
lot
of
layer.
Twos,
you
know,
drop
in
compatibility
is
standard.
So
the
good
news
is,
you
know:
evm
programs
work
out
of
the
box,
it's
something
that
you
can
rely
on.
A
Moving
on
to
layer,
two
as
a
developer
is
basically
kind
of
like
not
a
huge
issue,
and
the
other
thing
is
core
infra
that
you
kind
of
come
to
know
and
love
on
ethereum
on
L1
on
other
blockchains,
RPC
providers,
price
oracles,
you
know
graphs,
monitoring
analytics
it's
all
it's
all
there.
It's
already
ready
for
you
on
L2,
so
we've
got
a
robust
set
of
tooling
and
infrastructure.
A
If
you
want
to
deploy
so
we're
in
a
pretty
good
State
there,
and
you
know
sdks
and
Frameworks,
we
have
new
things
like
Foundry
coming
up
every
day,
they're
beginning
to
multiply.
You
have
lots
of
options.
You
have
lots
of
things
that
you
can.
You
know
potentially
use
to
make
your
development
experience
easier.
This
is
just
a
quick
graphic
with
Nitro
we're
running
gef
at
the
core.
So
in
terms
of
compatibility,
we're
you
know
reaching
parity
as
much
as
we
can.
A
So
what's
next
right,
you
know
you
can
keep
pushing
the
envelope
here,
but
one
thing
that
we
want
to
think
about
right
now:
contracts,
solidity,
as
you
think,
about
Roll-Ups
in
the
future.
We
want
to
see
broader
language
support
for
smart
contract
execution.
So
this
is
something
that
you
can
imagine
having.
You
know
different
options
to
write
your
contract
code
in
and
compile
down
to
something
that
will
still
work
with
the
evm.
It's
a
really
exciting
time
again,
right
now
on
on
arbitrum,
we
have
two
dimensional
gas.
A
We
price
L1
call
data
posting
costs
separately
separately
from
L2
execution
costs.
This
is
something
that
you
know
if
you're,
if
you're
a
developer,
if
you're
a
project
you're
doing
a
lot
of
things,
estimating
it
and
getting
accurate
pricing
for
the
gas
as
time
goes
on,
especially
with
high
volume
is
really
difficult.
So
making
that
better
and
working
with
wallets
to
have
different
standards
with
transaction
types
is
something
that
we
want
to
push
for
again.
A
The
last
one
I
want
to
make
here
is
there's
a
huge
perception
issue
in
kind
of
like
major
Tech
I
came
from
that
industry
before
working
here.
People
are
not
super
enthused
about
crypto
development
and
we
need
to
do
something
about
that.
I,
don't
know
exactly
what
that
is,
but
it's
something
we
all
need
to
think
about
so
kind
of
a
philosophical
point.
There
I
think
this
next
point
is
kind
of
on
performance
right
like
as
as
much
as
we
can
increase
throughput
and
bandwidth
and
execution
speed
on
the
Chain.
A
More
people
will
use
it
more
developers
will
build.
So
the
good
news
is
this
is
happening
all
the
time.
You
know
we're
doing
this
today,
we're
at
a
conference
talking
about
how
we
can
all
work
together
to
make
this
possible.
So
there's
lots
of
stuff
happening.
We
ship
Nitro
a
couple
months
ago.
We
seven
extra
capacity,
we
lowered
speeds,
things
are
looking
pretty
good
for
Roll-Ups
and
the
one
thing
here
to
think
about,
though,
is
we
focus
on
gas?
All
the
time
remember,
Roll-Ups
and
and
blockchains
in
general
are
not
just
about
gas.
A
You
have
to
have
Security
on
the
Chain,
so
making
performance
for
validators
or
for
for
nodes
that
are
serving
as
validators.
You
know,
making
that
more
efficient,
making
that
more
accessible
is
something.
That's
going
to
continue
to
be
more
important
as
time
goes
on,
especially
with
you
know,
State
growing,
in
the
way
that
it
is-
and
this
is
just
you
know,
a
quick
reminder.
Fees
are
low,
it
you
know
they're,
not
they're,
not
arbitrarily
low
they're,
not
tiny,
but
we're
getting
better
things.
A
Are
things
are
kind
of
improving
and
so
I'm
not
sure
how
much
time
I
have
left
yeah,
yeah
so
staple
it's
a
problem.
You
know
we're
going
to
try
to
continually.
You
know
optimize
for
for
client
performance,
and
you
know
there
are
a
couple
things
that
we're
experimenting
with
rentable
storage.
We've
talked
a
lot
about
statelessness.
There's
still
a
lot
of
work
to
be
done
here.
I
think
we
have
a
lot
of
progress
to
be
made.
A
The
one
last
point
I
want
to
end
with
is
at
a
high
level
in
order
for
staple
to
be
a
problem,
we
need
to
get
people
to
actually
use
blockchains
outside
of,
like
the
canonical
use
cases
we're
comfortable
with
today.
I
personally
would
like
to
see
a
lot
more
use.
Cases
come
to
Market
with
lower
barriers
to
entry
right
now
most
games
in
crypto.
A
In
order
to
play,
you
got
to
spend
500
on
an
asset,
that's
not
something
that
most
people
can
actually
do
right
and
you're
going
to
make
a
leverage
long
on
some
ass
that
you've
never
heard
of
most
people
as
they
go
into
the
world
and
want
to
try
to
experiment
with
these
things.
You
need
to
make
sure
it's
easy
for
them
to
get
to
get
involved
with.
A
We
want
to
make
sure
things
like
you
know,
onboarding
into
D5,
having
account
abstraction,
being
able
to
pay
with
different
fees
for
for
your
transaction
pay
with
different
tokens
for
your
transactions,
something
that
we
want
to
see
something
that
we
want
to
encourage
and
something
I
want
to
talk
about.
Just
as
the
kind
of
a
last
point
is
we,
we
have
novel
experimentation
going
on
with
insurance
on
chain.
We
see
a
lot
of
hacks.
A
We
see
a
lot
of
teams
focusing
on
security,
focusing
on
audits,
focusing
having
the
best
talent
in-house
to
make
sure
that
things
are
secure.
That's
not
the
only
way
to
solve
the
problem.
You
can
kind
of
think
about
hedging
in
a
different
way,
so
baking
in
Insurance
into
the
core
flows
for
Defy
is
something
that
I
think
there's
a
lot
of
potential
and
that
we
have
lots
more
of
experimentation
to
do
with
so
sorry
for
going
really
fast,
but
yeah.
That's
arbitrary
and
that's
us.