►
From YouTube: State of the ENS by Nick Johnson | Devcon Bogotá
Description
Visit the https://archive.devcon.org/ to gain access to the entire library of Devcon talks with the ease of filtering, playlists, personalized suggestions, decentralized access on Swarm, IPFS and more.
https://archive.devcon.org/archive/watch/6/state-of-the-ens/
An overview of ENS's innovations and progress in the last couple of years. Learn about how the ENS DAO is developing new approaches to decentralised governance, and how the development of ENS's offchain infrastructure makes trustless access to data held outside L1 easier for everyone - enabling both ENS's expansion to L2s and much broader applications.
Speaker(s): Nick Johnson
Skill level: Intermediate
Track: Governance & Coordination
Keywords: ENS,Governance,L2
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
Wonderful,
probably
about
half
of
you
I'm,
so
delighted
with
how
everyone's
been
doing
with
this.
If
the
person
next
to
you
held
a
card
up,
have
a
word
with
them,
say:
hi
tap
your
phone
to
their
card
and
you'll
get
a
poab
that
proves
that
you
visit
that
you
met
them
at
Defcon.
We
still
have
a
few
of
these
cards
left
at
our
booth
on
level.
Three.
So,
after
the
event
come
down
we'll
print
one
for
you
with
your
ens
name
and
your
ens
avatar
on
it.
A
A
So,
first
off
the
agenda,
I'm
going
to
recap
everything
we've
done
in
the
last
three
years
and
then
go
on
to
talk
about
what
we're
working
on
now
and
what
we're
working
on
next.
First
of
all
in
the
next
category,
Thorin,
which
is
ens's
New,
Look
and
design
system
and
new
app.
Second
of
all,
talking
about
scaling,
ens
with
off-chain,
reads
and
writes
next.
The
name
wrapper
which
you
may
have
heard
about
is
a
way
to
improve
the
functionality
of
igneous
names
and
the
ability
to
issue
trustless
subdomains.
A
A
And
while
it
was
doing
well
at
the
time
we
had
very
little
idea
of
the
phenomenon,
ens
was
going
to
be
coming
in
the
next
few
years
we
had
about
50
Integrations
with
various
wallets,
including
metamask
applications
such
as
etherscan
and
so
forth.
That's
changed
a
bit
in
the
last
three
years.
Our
set
of
Integrations
now
looks
more
like
this
laughs.
A
So,
as
you
can
see,
we've
come
a
long
way
from
under
50
Integrations
to
over
500.
We
had
about
300
000
registrations.
Back
in
the
day.
That's
now
over
two
and
a
half
million
we
had
about
96
000
ethereum
addresses
that
had
interacted
with
ens
in
some
way.
That's
now
over
a
million
addresses,
66
700
years
of
registration
had
been
purchased.
That's
now
over
six
and
a
half
million,
if
you
strung
them
all
into
in
figuratively,
and
the
nascent
EMS
treasury
had
a
stunning
382
ethernet
at
the
time.
A
Of
course,
it's
not
all
about
the
numbers.
Ens
has
accomplished
a
lot
on
both
Technical
and
governance
fronts.
In
the
past
three
years.
Some
of
it
will
seem
like
old
news,
but
it's
been
a
long
time.
At
divcon
5
we
had
limited
DNS
integration
with
only
the
dot
XYZ
TLD
supported
you
could
take
a
neonessner
sorry.e,
XYZ
name.
You
could
import
it
into
ens
and
use
it
just
like
you
would
any
dot
ethname.
Since
then,
this
has
been
expanded
to
nearly
every
top
level
domain
that
supports
DNS
Tech.
A
So
that's
nearly
90
of
all
top
level
domains.
Nearly
any
name
can
now
be
imported
into
enes
and
used
as
a
native
name,
just
ask
our
developer:
Advocate
Loop
dot
computer.
It's
printed
on
his
badge,
I
believe
there
are
transaction
fees
associated
with
importing
any
of
these
names
and
at
times
when
gas
prices
have
been
very
high
and
The
Ether
price
has
been
very
high.
It's
been
quite
pricey,
but
we've
got
a
plan
to
improve
that
massively,
which
I'll
talk
about
shortly.
A
Another
major
Improvement
has
been
ens's
transition
away
from
being
just
a
way
to
name,
wallets
and
decentralized
content
to
being
a
web
3
native
identity
platform,
with
the
introduction
of
Avatar
records
and
text
fields
that
provide
information
about
your
profiles,
such
as
your
Twitter
handle
your
email
address.
Your
ens
name
now
represents
you
as
your
web3
identity.
It's
a
universal
portable
identity
and
one
project
that's
been.
Bringing
that
to
more
users
is
sign
in
with
ethereum.
A
It
started
out
as
an
RFP
issued
by
ens
and
it
was
funded
by
a
joint
Grant
from
ens
and
the
ethereum
foundation.
Spruce
won
the
bid
for
that
and
has
done
an
outstanding
job
of
growing
it
into
the
primary
way
that
people
authenticate
with
ethereum,
replacing
a
plethora
of
incompatible
and
and
different
standards
for
citing
messages
to
assert
your
identity
with
a
symbol
system
that
can
be
thank
you
that
can
be
easily
plugged
into
existing
systems,
including
web
2
Legacy
systems.
A
But,
of
course,
when
I
talk
about
the
last
three
years,
and
particularly
the
last
year,
top
of
most
people's
minds
will
be
the
launch
of
the
ens
Dow,
which
is
now
one
of
the
largest
and
most
active
dowels
in
web3,
which
I
am
absolutely
both.
Blown
Away
about
ens
has
always
aimed
for
gradual
decentralization,
starting
with
the
minimum
set
of
emissions
held
by
the
widest
number
of
people
we
could,
which
was
the
original
four
of
seven
multi-sig.
A
Unlike
most
multi-seekers,
it
included
participants
from
around
the
ecosystem,
not
team
members,
and
they
had
limited
powers
to
upgrade
enes
to
replace
components.
Our
goal
was
always
to
move
from
that
to
a
system
where
ens
was
governed
by
a
decentralized
organization,
since
we
launched
all
the
way
back
in
2017.
A
The
Dow
was
now
responsible
for
almost
all
governance
leaders
and
controls
available
to
ens,
including
approving
contract
upgrades
changes
to
core
parameters
such
as
pricing
and
how
expired
names
are
used.
It's
also
responsible
for
treasury
grants
and
projects
using
the
funding
gathered
from
the
protocol
in
the
years
since
the
Dow's
launch.
The
yiniest
hour
has
shown
that
it
can
maintain
a
high
level
of
civilized
discussion,
made
useful
progress
forward
and
improving
the
protocol.
Besides
budgeting
and
day-to-day
bookkeeping,
it's
made
meaningful
changes
to
the
protocol,
including
changing
how
expired
names
are
handled.
A
In
order
to
safeguard
the
stability
and
fairness
of
the
system.
The
Dow
has
also
started
to
build
out
public
goods
and
grants
programs
of
its
own.
One
example
of
this
is
the
small
grants
rounds
that
we
now
run
inspired
by
nouns
props
room.
This
is
a
regular
system
where
anyone
can
submit
a
proposal
for
work.
They
want
to
do
or
work
they
have
done.
Anyone
with
ens
tokens
from
the
Dow
can
vote
on
them
and
the
top
five
in
each
category.
A
We
have
a
public
goods
category
and
an
ecosystem
category
then
receive
one
e
feature
and
funding
to
pursue
it.
The
public
goods
is
focused
on
anything
in
the
wider
ens
ecosystem
and
the
Eco
ecosystem.
Category
is
focused
more
on
things
that
relate
directly
to
ens,
and
we
hope
this
can
work
to
better
incubate
and
start
up
new
projects
both
for
enes
and
for
the
wider
public
goods
on
ethereum
and
web3
ecosystem
working
groups
have
also
funded
initiatives
on
scales,
small
to
large,
ranging
from
a
200
000
k,
Sorry
200k.
A
This
was
built
by
Karma
and
integrates
with
all
their
stuff.
You
can
also
just
use
it
to
provide
insight
into
how
your
delegates
are
voted,
how
active
they
are,
how
many
tokens
they
have
and
so
forth.
The
Dow
has
also
resulted
in
more
Community
participation
in
the
core
protocol.
One
major
success
story
is
rafi's.
Work
on
improving
ans's
normalization
functions.
A
Normalization
is
how
we
handle
names
like
uppercase,
neck
being
different
from
lowercase
neck
and
ambiguous
emojis,
hidden
characters
and
so
forth.
To
start,
we
used
a
well-tested
system
called
uts-46,
which
is
what
the
domain
World
uses,
but
it's
become
clear
over
time
that
ens
has
some
unique
requirements
and
we
wanted
to
enable
things
such
as
emoji
and
other
characters
that
are
popular
in
the
community,
but
not
supported
directly
by
DNS.
A
The
last
three
years
has
also
seen
an
explosion
in
community-led
ens
initiatives,
independent
projects
that
build
on
top
of
the
ens
ecosystem.
One
popular
example
you
may
have
seen
is
the
ens
leaderboard,
which
shows
people
with
Twitter
handles
that
contain
Dot
eth
and
their
ranking
relative
to
followers.
We've
had
some
pretty
popular
ones,
including
Paris
Hilton,
for
instance,
right
up
the
top
of
the
leaderboard
I
myself
am
now
ranked
I,
don't
know
number
400
or
something
we've
had
the
launch
of
ens
Vision,
which
is
a
third-party
ens
trading.
A
Market
allows
people
to
now
register
names
from
scratch
and
also
trade
existing
names
and
projects
such
as
nimi,
which
is
a
web
3
profile
site.
It
lets
you
generate
a
customized
profile
and
in
fact
the
eth.limo
Gateway
folks
have
integrated
with
nimi.
So
if
you
have
an
ens
name
that
doesn't
have
content
set
up,
it
will
automatically
show
your
profile
with
your
pipes
and
so
forth.
Then
you
can
customize
it
as
you
wish.
A
Before
we
start
talking
about.
What's
new
one
small
announcement.
True
names
limited
is
the
name
of
the
development
company
that
builds
enes,
the
company
I
founded
that
gets
paid
by
the
Dow
employees
about
dozen
of
us
to
build
our
ens.
When
we
formed
it,
we
didn't
really
think
of
it
as
a
name
that
would
be
visible
to
people.
A
A
So,
what's
next,
first
we're
going
to
talk
about
Thorin
Thorin
is
ens's
new
design
system,
and
it's
built
from
the
ground
up
with
usability
and
web3
in
mind,
we've
used
it
to
completely
rewrite
the
ens
app
from
the
ground
up,
coupled
with
improvements
to
the
smart
contracts
behind
DNS.
This
enables
a
huge
Improvement
in
usability
for
ens
users.
A
The
ensui
faces
kind
of
a
unique
Challenge
from
amongst
web3
apps
and
in
fact,
kind
of
apps
in
general,
in
that
it
needs
to
provide
an
interface
that
is
both
easy
and
user-friendly
for
new
users,
but
has
the
advanced
levers
and
and
sophisticated
interaction
required
by
Advanced
users.
We
don't
want
to
create
a
situation
where
the
app
is
sufficiently
flexible
to
do
anything
with
ens,
but
deters
existing
users,
which
is
a
little
bit
the
case
in
the
current
APP,
or
is
so
straightforward
and
wizard-based
that
you
need
to
go
somewhere
else.
A
Aside
from
the
functional
improvements,
we've
hugely
improved
the
loading
times
and
made
the
new
app
100
mobile
friendly,
the
new
app
is
at
feature
parity
and
live
now
on.
The
girly
test
net
would
be
live
on
robston,
but
that's
already
been
deprecated
and
you
can
try
it
out
now
at
alpha.eds
domains,
just
to
emphasize
it's
only
on
girly.
It
is
a
little
bit.
You
know
sharp
edges.
Still
the
team
really
raced
to
get
it
out
in
time
and
did
an
amazing
job.
A
A
Thorin
isn't
just
for
ens.
Either.
We've
made
it
available
as
a
standard
react
library
that
anyone
can
use
for
their
web
3
apps.
You
can
check
it
out
on
sauron.ens
domains
and
you
may
have
noticed
it
powering
a
number
of
our
other
sites,
such
as
the
swag,
microsite
and
so
forth.
One
of
our
major
ongoing
projects
is
scaling
ens
for
many
projects.
This
is
accomplished
by
going
multi-chain
deploying
to
just
multiple
chains
if
you're
uniswap,
for
instance,
you
fragment
your
liquidity
a
bit,
but
you
can
work
in
parallel
across
multiple
chains.
A
Ens
is
in
kind
of
a
unique
position
here.
We
need
to
maintain
a
single
cohesive
registry
of
names
and
it's
far
too
early
in
the
L2
and
the
roll-up
ecosystem,
to
pick
a
single
Service
as
the
winner
that
we're
going
to
migrate
to.
Instead
we've
been
pursuing
options
that
make
it
possible
for
people
to
host
their
ens
names
anywhere
without
the
resolving
having
to
know
or
care
where
that
is
earlier.
A
This
year
we
launched
ccip,
read
as
a
collaboration
between
ens
and
chain
link,
while
previous
systems
such
as
bridging,
often
introduced
new
trust
assumptions
and
require
L1
transactions
to
execute
ccip
read,
uses
a
lower
level
primitive
proofs,
which
means
that
in
many
cases,
such
as
with
l2s,
this
can
be
done
with
no
additional
trust
assumptions
over
those.
The
L2
itself
requires
meaning
you
could
host
your
ens
name
on
optimism.
A
This
ends
up
being
a
little
bit
like
having
one
of
those
conversations
with
a
couple
who
have
had
a
fight
and
refusing
to
talk
to
each
other.
Well,
you
tell
the
Gateway
that
I
think
that
they
should
give
you
this
data
I
need.
So
the
conversation
tends
to
go
like
that.
Unfortunately,
just
ask
them
yourself:
isn't
an
option,
so
the
client
has
no
choice
but
to
play
middleman.
A
The
necessary
proofs
to
make
with
trustless
are
encapsulated
in
the
response
sent
by
the
Gateway
and
verified
by
the
resolver
before
returning
the
result
from
the
name
resolution.
This
means
that
implementing
the
base
protocol
is
enough
to
enable
all
current
and
future
l2s
and
off-chain
storage
systems
to
be
used
in
the
ens
name.
A
Some
of
the
largest
apps
and
wallets
have
already
upgraded
to
support
it
too,
including
metabase,
metamask,
coinbase
wallet
as
well
as
ethereum
etherscan,
there's
a
long
way
to
go
in
terms
of
making
this
latest
change
Universal.
So
please
reach
out
to
your
favorite,
wallets
and
apps.
If
you
see
that
they
don't
support
these
new
names
and
ask
them
to
let
them
know
how
important
it
is
like
our
Thorin
ccip
reader
also
isn't
just
for
ens,
it
can
be
used
to
add
off-chain
resolution
support
to
any
project.
A
Coinbase
has
gone
a
step
further
than
just
integrating
ctip
read
for
name
resolution
they're
using
ccip,
read,
ens
wildcard
support
and
ens's
DNS
integration
together
to
allow
their
wallet
their
wallet
users
to
create
ens
names
under
the
dot,
CB
dot
ID
domain
for
free.
These
names
will
instantly
work
in
any
wallet
or
dap.
That
supports
ens's
new
resolution
improvements
and
they
have
no
transaction
fees
to
set
up
for
either
users
or
coinbase.
A
It's
currently
supports
writing
to
evm-based,
l2s
or
side
chains
or
sending
signed
messages
to
an
HTTP
API,
but
this
is
extensible
with
new
methods,
as
they
crop
up.
Adding
support
for
this
to
the
NS
manager
and
further
standardizing
the
best
practices
and
making
it
as
as
flexible
and
accessible
as
possible
is
an
active,
active
area
of
research
and
development
for
the
team.
A
So
next
up
the
name
wrapper
which
you've
probably
heard
about
of
griping
about
on
Twitter,
because
it's
been
underway
for
a
while
ens
predates
all
of
the
nft
standards
and
while
the
dot
eth
registrar
was
written
after
Eep,
721
came
out
that
functionality
only
applies
to
dot
e
second
level
domains
so
nick.heath,
but
not
wallet.beck.eth
or
nick.xyz
or
whatnot.
As
a
result,
not
Alliance
names
can
be
transferred,
exchanged,
Etc
using
standard
nft
interfaces.
A
Further.
One
of
the
main
advantages
of
tradability
is
trustless
ownership.
If
somebody
sells
you
a
name
or
a
subdomain
or
gives
it
to
you,
you
want
to
make
sure
that
they
can't
take
it
back
next
week
and
set
it
to
a
different
address,
you're
kind
of
reliant
on
their
Goodwill.
There
are
solutions
to
work
around
this.
A
You
can
give
net
ownership
of
the
name
to
a
contract
and
we've
had
a
system
for
that
called
now.ens.domains
for
some
time,
but
it
has
significant
shortcomings
in
that
you're
committing
your
name
to
a
specific
contract
where
it
has
to
live
for
the
rest
of
time,
which
limits
what
you
can
do
with
it.
The
name
ramper
solves
both
these
problems.
It
allows
any
EMS
name
at
any
level,
whether
it's
a
dodeath
or
a
subdomain
or
a
DNS
name,
to
be
wrapped
as
an
ERC
1155
nft.
A
It
also
allows
owners
of
wrapped
names
to
revoke
permissions,
such
as
the
ability
to
replace
or
delete
subdomains
by
mechanism.
We
call
fuses
fuses,
allow
the
owner
of
a
name
to
revoke
their
own
control
and
that
of
any
subsequent
owners
over
certain
functionality
on
a
name
such
as
the
ability
to
unwrap
it
again
to
create
or
to
replace
subdomains
to
transfer
it
to
another
user
and
so
forth.
A
Once
a
fuse
is
burned
that
fuse
can't
be
reset
until
the
name
expires,
giving
a
user's
a
guarantee
as
to
what
can
be
done
to
or
with
their
names
until
the
name
expiration
is
reached.
The
name
ramp
attracts
these
permissions
and
provides
a
very
easy
API
for
fetching
the
set
of
restrictions
currently
applied
to
a
name
and
when
they'll
expire
alongside
the
name
wrapper.
We've
also
implemented
a
suite
of
other
contract
improvements,
including
to
the
dot
Heath,
registrar,
controller,
the
reverse
registrar
and
the
public
resolver
all
together.
A
These
will
prevent
a
much
smoother
registration
process
for
end
users
and
cut
down
on
the
number
of
transactions
and
gas
required,
as
well
as
other
quality
of
life.
Improvements
like
allowing
contract
donors
to
set
primary
names
for
their
contracts.
The
long
and
short
of
us
is
that,
with
the
new
DOT
ease
registrar,
you
will
be
able
to
register
a
name
wrap
it
in
order
to
set
permissions,
burn
fuses
and
set
your
primary
name
all
in
a
single
transaction
and
using
less
gas
than
doing
those
operations
would
cost.
Today.
A
A
Finally,
I'm
going
to
talk
about
something
else:
I'm
excited
we'll
be
able
to
release
soon.
Gasless
DNS
integration
presently
claiming
a
DNS
name
in
ens
cost
a
substantial
amount
of
gas,
it's
about
100K
to
a
million
gas
per
signature.
It
has
to
verify,
depending
on
the
ether
and
gas
price
that
can
range
anywhere
from
20
bucks
to
at
the
extremes
of
the
bull
market,
a
thousand
dollars.
A
Obviously
this
isn't
a
particularly
scalable
solution,
and
so
this
can
be
a
substantial
barrier
to
DNS
integration.
Fortunately,
we
have
a
plan
for
reducing
this
all
the
way
to
zero.
So,
first,
a
quick
overview
of
how
DNS
works.
It
uses
a
chain
of
trust
just
like
SSL.
The
root
zone
is
signed
by
a
well-known
certificate
Authority
and
they
sign
keys
for
each
of
the
subdomains
such
as.com
dot
link
Etc.
Each
of
those
zones
uses
its
keys
to
sign
this
subdomains
and
so
on
and
so
forth.
A
Our
current
DNS
integration
uses
this
to
allow
users
to
claim
DNS
names
inside
DNS.
Our
front
end
collects
up
all
the
complete
set
of
proofs
necessary
and
submits
them
to
a
Smart
contract
which
verifies
the
signatures
and
if
they
match
it,
lets
them
claim
the
name
if
you've
been
paying
attention
to
the
talk
so
far,
this
may
sound
quite
familiar
to
you
similar
to
something
else.
A
We've
discussed
ccip
read
if
we
treat
the
whole
of
ens
as
a
massive
off-chain
distributed
database,
we
can
have
a
Gateway
that
fetches
DNS
data
collects
all
the
proofs
necessary
and
submits
it
to
the
chain,
just
like
when
you're
resolving
a
name.
So
then
we
can
write
a
resolver
for
DNS
names
that
uses
that
gateway
to
resolve
names
in
ens
entirely
using
data
stored
in
DNS
users
can
set
DNS
records
to
configure
their
name
and
they
will
resolve
any
from
their
ens
is
supported
with
xero
on-chain
transactions.
A
Necessary
claiming
on
chain
may
still
be
useful
in
some
cases.
For
example,
if
you
need
granular
control
over
the
subdomains,
but
for
most
users
it'll
be
possible
to
claim
your
DNS
name
just
by
setting
some
text
records
we're
working
on
this
right
now,
the
DNA
SEC
Oracle
changes
are
done
and
we're
working
on
implementing
fixes
from
an
audit
before
we
roll
it
out.
We
hope
you
have
it
ready
to
go
before
the
end
of
the
year.
There's
been
a
lot
more
going
on
and
with
ens,
but
compressing
four
years
down
into
25.
A
Minutes
naturally
means
I
have
to
leave
some
things
out.
Just
one
more
thing:
the
Dow
was
nearly
a
year
old,
but
still
in
its
infancy.
We
have
a
lot
of
a
lot
to
learn
and
a
lot
to
do,
and
we
need
your
expertise.
Please
take
a
look
at
our
governance.
Page
reach
out
to
ens
domains
on
Twitter,
see
how
you
can
get
involved
and
help
us
build
a
truly
decentralized
public,
good
naming
for
web
3.,
and
that's
all
I
have
for
you.
Thank
you
very
much.
B
C
B
C
A
lot
for
the
talk
one
thing
I
was
thinking
about
you
should
probably
be
able
to
use
ens
to
the
problem
is
when
you
use
UI
to
to
communicate
with
a
page.
The
metamask
will
generate
you,
it
will
provide
a
transaction
for
you
and
basically
you
have
no
idea
like
if
actually
the
UI
is
the
right
UI
and
you,
if
you
are
calling
it
a
contract,
you
want
to
be
calling
and
I
guess
you
could
UNS
you.
Could
you
you?
C
A
Definitely
better
user
insights
into
transactions
is
I,
think
probably
the
major
adoption
barrier
and
and
fishing
and
so
forth.
Fourth
issue
in
web
3
today,
naming
contracts
of
the
units
names
is
one
big
step
towards
making
that
a
bit
better
and
in
fact
the
latest
contract
out
dates.
We're
pushing
out,
make
it
easier
for
contracts
to
get
ens
primary
names.
A
C
A
Sure
so
at
the
OS
level
is
depending
on
you,
look
at
it
tricky
or
easy.
You
can
run
your
own
DNS
resolver,
in
which
case
you
personally
get
to
resolve
all
units
names.
Getting
it
rolled
out
to
everybody
is
a
very
Steep
Hill
to
climb
I
think
we're
going
to
have
more
success,
getting
this
integration
to
browsers
such
as
Brave
and
Opera,
which
already
support
it
rather
than
integrated
directly
with
os's.