►
From YouTube: ERC lightning talks | 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/erc-lightning-talks/
15mins lightning talks about ERCs, mainly focused on following topics:
NFTs/SBTs/ABTs/Token-gating/Curation
Music NFT metadata
Privacy and self-sovereign identity
Other Radical Exchange topics e.g. Plural Property
Speaker(s): timdaub, Anett Rolikova
Skill level: Beginner
Track: Developer Infrastructure
Keywords: engineering,soulbound,erc,lightning talks,nft,privacy
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
Annette
is
currently
still
in
a
podcast
interview,
but
I
think
she
will
come
also
later
I'm
quickly.
Gonna
give
an
overview
of
what's
going
to
happen
in
the
next
I
think
we
have
like
one
and
a
half
hours.
You
can
already
see
a
bit
on
my
like
drawn
slides,
I,
don't
like
PowerPoint
that
much
like
what
will
be
the
what
will
be
essentially
like
the
the
the
content
of
of
this
entire
session.
We
have
lined
up
as
like
six
seven
speakers,
including
me.
A
We
are
going
to
Center
all
of
these
talks,
Around
The,
ethereum,
Magicians
and
specifically
we're
going
to
talk
about
ERC
proposals,
so
ethereum
request
for
for
for
comments
right.
So
basically
everything
that
didn't
fit
into
Annette
and
Tim
bico's
earlier
session.
I
think
like
it
was
about
two
weeks
two
days
ago
about
the
ethereum
core
roadmap,
so
how
this
works.
A
Each
speaker
has
roughly
15
minutes
and
then
we
have
a
usually
like
a
five
minute
break
where
we
can
set
up
the
next
speaker
and
maybe
there's
even
like
time
for
questions
I
guess
we
will
have
some
talks
about
timestamps
in
ethereum,
get
locks
from
Ronin
that
just
entered
the
room
by
chance.
We
will
have
some
talks
about
Soul
Bond
tokens
about
music
nfts
about
yeah
d-soc.
A
I,
think
you
know
there
was
a
there
there's
starting
to
be
this
debate
basically
around
like
how
can
we
actually
do
Innovation
with
these
contracts,
if
you
cannot
change
them
anymore,
right
and
so
like?
What
can
we
do
about
it
and
I've
tried
to
kind
of
like
Express
that,
where
you
know
like
this
contract
this
this
document,
this
proposal
that
once
you
once
you
put
it
into
the
the
final
status?
A
And
apart
from
all
of
this,
like
pessimism,
I
think
there's
there's
another
good
reason
for
submitting
and
and
being
active
on
this
forum,
and
it's
because
you
get
a
ton
of
exposure
to
to
your
ideals.
So
this
is
a
thread
here
that
I
made
I
think
around
in
in
April,
and
it's
about
like
a
specification
for
soul,
bound
tokens
or
we
now
call
them
account
bound
tokens,
and
this
threat
has
gotten
9000
views
and
if
you
would
sort
by
the
replies,
it's
actually
the
top.
A
A
And
you
know
we
are
actively
talking
about
all
of
the
Privacy
challenges
of
Soul
Bond
tokens,
and
so
this
has
really
become
basically
like
a
space
where
this
entire
standard,
all
the
solar
token
things.
Everything
is
like
very
verbosely,
documented
and
and
I
I
think
it's
awesome,
because
I
I
wouldn't
have
had
these
ideal
ideas
by
myself.
So
I
think
this
is
like
a
community
effort
and
it's
cool
and
so
by
the
way
I'm
like.
A
So
that's
really
cool
and
that's
really
a
strength.
But
it's
also
a
weakness
and
I.
Think
this
I
guess
it's
like
a
bit
of
a
famous
cartoon
in
the
in
the
in
these
standards
community,
at
least
where
you
know
like
the
there's
like
the
this
XKCD
comic.
You
know
where
there's
like
14
competing
standards
for
a
use
case
and
then
there's
this
one
guy
saying:
hey,
that's
crazy,
like
why
do
we
need
14
standards?
A
A
So
to
say
where
you
know
on
one
side,
we
have
more
like
a
market
driven
adoption
where
the
individual
kind
of
makes
the
decision
by
themselves
they
they
do
all
of
the
due
diligence
and
and
they
come
to
the
conclusion
that
they
want
to
use
a
standard
and
then,
on
the
other
hand-
and
this
is
maybe
true
for
yeah,
like
more
I-
think
like
groups
that
have
to
make
decisions
rather
quickly
and
and
like
yeah
like
close
to
time.
I
think
you
have
this.
Basically,
this.
A
You
have
this
totally
chaotic
evolutionary
kind
of
thing
that
that
is
the
market
that
somehow
also
figures
out
like
what
is
the
best
decision,
but
completely
different
and
not
by
talking
to
each
other
and
so
I,
I.
Think
and
I
mean
by
no
means
is
this
Financial
advice,
but
I
I
would
always
bet
on
the
market
and
not
on,
like
an
individual
committee
actually
and
and
so
I
I
think,
that's,
that's,
actually
the
better
the
better
approach
and
and
also
I
mean
I.
Guess
it's
also.
A
Actually
there
is
now
we
are
starting
to
see
a
pattern
emerged
where
people
are
starting
to
really
upgrade
the
standard,
and
they
are
doing
it
in
a
way
where
they
are
basically
like
yeah,
basically,
bolting
kind
of
this
one
lock
to
the
other,
almost
like
a
like,
like
in
a
I,
don't
know
on
these
bridges
that
sometimes
you
can
see
as
a
tourist
kind
of
thing,
so
so
I
think
over
the
last
half
a
year.
That
has
really
happened.
A
So,
for
example,
we
now
have
a
standard
event
for
emitting
a
an
event
when
the
metadata
is
updated
in
in
an
NLT
standard,
and
that's
the
one
on
the
top
right.
It's
the
4906
that
essentially
just
emits
an
event.
We
now
have
a
very
interesting
standard
for
that,
basically
splits,
the
user
and
the
owner
into
two
different
groups
and
I
think,
especially
with
you
know,
with
d-soc
kind
of
making
us
aware
that
there
are
only
that
that
there
are
like
subsets
of
ownership.
A
Where
kind
of
ownership
represents
this
bucket
of
right
and
then
you
know
you
can
have
fructose
and
you're
kind
of
Usos
and
abusers,
and
so
on
this.
This
is
starting
to
become
really
really
interesting
right.
We
have
like
different
kind
of
roles
that
could
interact
with
the
nft
and
then
this
could
have
like
different
economies,
and
so
that's
I
want
to
give
a
shout
out.
A
That's
4907
and
then
I
guess
maybe
like
a
a
more
Infamous
one
is
the
is
the
royalties
one
and
it's
the
2980
81
and
that's
basically
an
optional,
an
an
optional
royalties
location
mechanism
for
nfts
that
is
implemented.
I.
Think
in
in
many
nft
marketplaces
and
and
again
I
I
just
want
to
highlight
that
I
think
it
is
definitely
possible
to
upgrade
these
things
and
like
we
are.
We
are
doing
that.
I.
A
And
then
we
also
have
this
view
function
that
allows
you
to
always
check
whether
a
token
is
locked
and
the
purpose
for
this
is
that
that,
if
you
were,
if
you
were
to
just
use
like
the
plane,
721
standard,
which
actually
it
has
a
kind
of
like
a
small
line
in
it,
where
it
says
like
that
these
nfts
can
also
be
they
can
be
used
as
a
reader
like
a
read-only
registry.
The
problem
is
that
indexes
and
wallets,
and
so
on,
wouldn't
really
recognize
it,
because
a
computer
cannot
reason
from.
A
Let's
say
you
know
the
transfer
is
reverting
to
you
know.
This
thing
is
like
locked,
because
it
could
also
be
that
you
have
done
like
something
else
like
something
something
else
wrong.
You
know,
and
so,
therefore,
the
error
might
be
referring
to
something
else.
So
I
I
personally
think
that's
useful
and
that's
final
now
also,
and
it's
building
on
721
yeah
I
mean
now
I'm
at
17
minutes.
The
next
we're
gonna
have
the
next
speaker.
A
B
B
But
for
some
other
case
it
actually
worked
very
well,
and
so
I
was
doing
so.
I
have
this
game,
so
the
whole
state
of
the
game
is
actually
here.
So
you
have
all
the
fleet
is
gaming
space.
You
have
planet
and
Fleet.
You
can
there's
two
main
things
and
it's
like
I
think
this
state
is
around
seven
megabyte,
but
it's
not
actually
I
didn't
implement
the
full,
so
I
have
an
index.
I
have
the
same
indexer
running
on
the
graph
and
I
didn't
finish
to
implement
it
fully.
B
B
Then
I
need
to
request
20
000
times
depending
I
mean
a
bit
less
because
you
can
have
same
even
an
event
in
the
same
block,
but
you
I
have
to
request
that
on
top
and
because
it's
a
in
browser
indexer,
it
uses
eip119393,
which
is
like
the
the
wallet
interface
and
I,
cannot
do
batch
request.
I
have
to
do
all
these
requests,
and
so
I
have
this
version.
We
actually
is
still
running
from
last
time
and
sometime
here
or
out,
because
the
RPC
is
not
happy
that
I'm,
so
the
RPC
of
metamask.
B
B
So
so
the
proposal
I
wanted
to
show
you
a
kind
of
a
really
example.
But
the
proposal
is
is
basically
to
add
this
to
the
Json
object.
So
it's
a
very
simple
change.
You
can
do
in
a
in
your
node,
so
in
goatorium
or
what
whatever
and
so
actually
finally
enough,
like
team
pushed
me
to
go
to
the
core
Dev
meeting
the
other
day
and
actually
I'm
going
to,
and
so
we
are
the
interesting
discussion
about
it,
but
so
I
kind
of
so
most
of
it
I
already
say.
B
B
So
if
you
don't
care
about
the
timestamp,
you
don't
need,
and
actually
this
one
could
really
by
actually
solving
the
first
one.
So
this
one
is
really
an
alternative,
but
I
don't
see
any
reason.
To
just
add
another
one,
especially
I,
think
graphql
is
not
supported
in
all
the
node
implementation
today,
and
so,
as
I
say,
I
went
to
the
core
Dev
and
we
had
the
feedback
and
the
main
feedback
was
that
hey?
B
If
we,
we
don't
have
access
to
pass
logs,
how
do
we
are
going
to
index
in
a
decentralized
manner
because,
of
course,
if
you
have
a
backhand,
you
know
you
solve
your
problem,
but
we
we
don't
want
to
have
a
back-end
right.
You
want
to
be
able
to
use
tornado
cache
from
your
browser
without
relying
with
only
relying
on
your
node
and
so
so
I
think
I.
B
Don't
know
for
me
that
I
would
like
to
to
have
discussion
as
a
community
how
we
can
so
solve
that,
like
I
know,
there
is
work
on
the
around
like
right
now
about
portal
things,
portal,
Network
and
so,
but
I
think
it's
important.
We
we
understand,
like
the
point
of
view
of
application
developer,
that
don't
want
to
be
involved
with
our
application
once
it's
launched
and
another
thing
yeah
so
I
mentioned,
like
most
systems,
already
rely
on
the
log
events.
B
B
So
I
think
that's
what
we
should
do
and
minimize
the
role
of
the
yeah
minimize
the
gas
cost
we
basically,
that
was
when
we
Nima,
is
the
things
that
happen
on
the
Chain.
If
we
can
do
it
of
chain,
but
it's
assume
we
have
a
system
to
retrieve
it.
That's
why
I
think
it's
important
to
discuss,
because
maybe
the
conclusion
is
like?
Oh
actually,
we
cannot
and
we
have
to
pay
gas
to
do
that,
but
I
hope
it's
not
the
case.
D
Hello:
everyone
I'm
gonna
start
my
timer,
so
I
have
a
reference
point
here
yeah.
This
is
my
first
time
actually
talking
at
Defcon.
This
is
my
second
Devcon
I'm
super
happy
to
be
contributing
back
and
sharing
knowledge
and
the
sparking
debate
and
ideas.
So
thanks
for
having
me
and
thanks
Tim
for
organizing
this
as
well
and
it
so
today,
I
wanted
to
talk
about
eip4973,
Badges
and
the
financializing
towers
and
Beyond
as
well.
So,
firstly,
a
little
bit
about
me.
D
My
name
is
Rahul
I'm,
co-founder
of
this
little
baby
company
that
we
started
called
autospace
and
I've
been
in
the
crypto
ecosystem.
Since
2016.
I
started
off
with
my
journey.
Also,
with
music
I
was
building
nfts
to
assetize
music
royalties
back
in
2017
did
not
work.
They
moved
on
to
SoundCloud
got
fomo
with
those
and
I
got
back
to
crypto
full
time
now,
so
I
think
I
want
to
start
with
how
this
year
had
started
actually
like.
D
We
think
that
there's
this
paper
called
decentralized
Society
and
it
centered
our
attention
on
this
notion
that
web3
centers
around
expressing
transferable
Financial
assets,
rather
than
encoding
social
relationships
of
trust.
When
everything
is
transferable,
things
can
be
sold
to
the
highest
bidder.
So
you
know
we
wanted
to
challenge
that
and
that's
that's
what
that
problem
is
what
gave
to
this
idea
and
working
with
Tim
on
this
EIP.
D
What
we
call
account
bound
tokens
not
to
be
confused
with
sold
down
tokens
or
you
may
be,
but
semantically
speaking,
we
kind
of
you
can
Define
this
as
non-transferable
tokens
bound
to
an
account
and
then
our
goal
here
was
to
really
it's
very
semantic,
based
again
like
to
create
special
ownership,
Deeds
or
creating
like
permission
Primitives,
but
really
to
create
a
new
ownership
experience
through
this
primitive.
You
can
read
more
about
this.
We
have
written
a
more
extensive
article
on
this.
D
D
What
we're
actually
seeing
is
this
non-transferable
tokens
is
a
spectrum
and
you
you
can
Define
what
is
being
bound
to
and
what
is
that
binding
strategy,
and
you
can
kind
of
this
is
this-
is
where
the
explosion
of
ideas
are
coming
and,
as
a
builder
I
feel
like
some
of
the
nfts
nft
spec
is
kind
of
over
optimized
for
what
we
actually
express
our
ideas
through.
So
we're
kind
of
like
craving
for
new
tools
and
new
new
instruments
to
kind
of
like
build
our
ideas
right
and
at
Auto
space.
D
We,
we
call
something
smaller,
something
simpler.
We
call
them
badges,
which
is
powered
by
eip4973,
accountable
tokens,
so
I
want
to
dive
right
into
it
like
because,
because
ever
since
Soul
bound
tokens
was
kind
of
like
really
a
Hot
Topic,
it
kind
of
sparked
like
a
lot
of
hot
debates
or-
and
it's
it's
debates
are
great
like
because
it
really
helped
us
intellectually
navigate
the
space
and
like
get
like
a
pluralistic
opinion
from
various
parties.
D
One
of
the
first
things
or
concerns
they
put
out
like
I
think
was
permanence.
You
know
what,
if
I
don't
want
a
sold
out
token
or
an
account
token.
You
know
anymore
and
the
second
one
is
a
lack
of
consent.
What
if
I
get
an
nft
like
that's
non-transferable,
airdrop
to
be
with
my
personal
details,
you
know
what
would
happen.
You
know
and
key
rotation.
You
know
like
I
I.
D
What,
if
I
lose
access
to
my
key
wallet,
yeah
I,
want
to
like
I,
mean
to
my
wallet
or
do
I
want
to
change
my
wallet
and
lastly,
this
more
popular
active
debate
about
like
verifiable
credentials
and
abts
on
Chain
versus
off-chain
identity.
So
lots
of
things
very
simply
put
there
we've
written
again
lots
of
detail
on
this,
but
I
can
kind
of
summarize
this.
These
were
the
design
decisions
that
helped
us
input
into
erp4973,
so
permanence.
D
D
D
So
let's
Dive
Right
In
like
so.
This
is
the
erc4973
at
a
glance
you
could
just
npm
install
that
very
easy.
So
that's
a
very,
very
light.
Interface
right,
like
it's
just
expresses,
so
we
can
kind
of
like
dive
into
what
this
actually
does.
So,
firstly,
this
top
section
right.
This
transfer
event
balance
off
on
or
off.
This
is.
This
was
mainly
to
ensure
backward
compatibility,
backward
compatibility
to
nft
in
general,
so
we
actually
implement
the
ierc
721
mm
metadata.
D
So
one
of
the
things
that
building
this
EIP-
actually
it
was
super
amazing
learning
experience.
We
actually
didn't
have
the
transport
event
first,
and
then
we
were
kind
of
missing
all
these
stuff,
like
etherscan,
was
not
showing
the
log.
Events,
for
example,
or
metamask,
was
not
showing
the
the
the
interesting
metadata.
So
we
we
actually
started
using
the
transfer
event,
which
is
such
a
simple
change.
Everything
started
working
automatically.
D
So
if
you
see
the
function,
there's
like
three
three
parameters:
right
like
the
from
the
URI
and
the
signature.
So
we
call
this
a
take
flow,
so
you
cannot
actually
mint
an
account
bound
token
unless
it's
two
parties
involved.
So
it's
like
a
peer-to-peer
fully
mutually
consented
protocol
right.
So
you
can
think
about
this
as
like:
okay,
Alice,
designs
and
ABT,
described
by
a
spec,
which
is
hosted
by
a
token
URI
Alice
then
wants
to
issue
the
ABC
to
Bob.
D
Alice
can
only
do
that
if
this,
if,
if
he
signs
using
aip712
signature
and
provide
that's
capturing
her
consent,
so
now
that
one
party
consent
is
established,
Bob
can
now
take
the
SBT.
He
would
then
basically
authenticate
by
providing
the
circuit
URI
the
signature
from
Alice
and
then
prove
that
I
can
take
this,
so
this
is
in
Auto
space.
We
actually
call
this.
The
allow
list
flow
so
I'm,
just
like
adding
people
to
an
allow
list.
D
I'm
like
signing
people
for
to
a
badge
and
the
give
flow,
is
actually
its
inverse.
It's
it's.
When
the
when
Alice
designs,
an
ABT
Bob
wants
the
ABT
so
signs
it
and
then
Alice
can
now
give
the
ABT
to
Bob.
So
this
in
order
space,
we
call
it
the
airdrop
flow.
So
if
you,
if
you
give
a
badge
you
can
just
like
basically
I
want
this
and
100
people
say
I
want
this.
You
can
actually
do
an
airdrop
through
through
an.
D
And
the
last
bit
is
this
one?
It's
the
unequiv.
This
basically
means
complete
dissociation
from
the
account
bound
token,
so
only
the
owner
of
the
token
can
dissociate.
So
these
are
like
basically,
the
fundamental
building
blocks.
That
kind
of
like
help.
This
create
this
very
bare
minimum,
very
simple,
very
it's
highly
functional,
highly
utilitarian,
EIP
4973
and
then
Auto
space.
D
D
I
mean
I
think
we
can
all
agree
that
the
ecosystem
is
like
hyper
financialized
and
we
want
to
challenge
that
status
quo.
Like
you
know
you,
if
you're
in
a
position
of
wealth
and
influence,
you
can
buy
tokens
and
if
your
community
is
basically
to
design
their
governance
on
a
one
token,
one
vote
system,
so
person
of
influence
can
basically
assert
their
entire
influence
through
that
power.
D
It's
basically
plutocracy
right.
So
we
want
to
challenge
that
and
we
want
to
move
towards
more
towards
the
one
human
one
vote.
But
for
us
we
see
the
one
account
one
vote
as
a
necessary
step
to
kind
of
get
to
one
human
one
vote,
and
then
this
is
really
Fresh.
Off
The
Grill
right.
This
happened
like
a
few
days
ago.
D
The
mango
markets,
the
hacker
exploited
mango
for
100
million
hacker,
turns
around
offense
to
return
the
funds
and
he
used
32
million
of
those
votes
to
say
yes
to
his
own
proposal,
because
he
hacked
those
and
then
executed.
That
proposal
and
I
think
we
can
do
better
than
this
right.
Like
it's
a
that's
a
no-brainer
I
feel,
but
it's
really.
The
takeaway
that
I
wanted
to
kind
of
here
have
here
is:
let's
move
away
from
the
one
token
one
vote
system
and
away
from
plutocracy
and
I.
D
Think,
let's,
let's
explore
new
forms
of
governance.
I
think
it
is
no
one-size-fits-all
I
think
we're
in
a
stage
where
the
ecosystem
is
growing
so
so
fast
and
we
as
Builders
we.
We
definitely
need
more
instruments
at
our
toolkit.
We
need
to
spark
debate.
Yeah
apply,
rigor,
get
feedback,
so
I'm
glad
that
I'm
kind
of
like
getting
a
lot
of
that
here
in
Devcon.
So
that's
that's
a
lot,
that's
it
and
that's
a
Dali
otter.
We
are,
we
don't
work.
We
just
create
these
Dolly
orders
most
of
the
time.
If.
F
D
D
Yeah,
absolutely
so
so
one
of
the
things
with
account
recovery,
it
actually
came
up
pretty
actively
in
the
debate
like
hey
if
I
have
badges.
In
my
account,
if
you
have
non-transport
like
tokens,
what
if
I
want
to
rotate
my
keys,
then
how
do
I
do
this
and
that's
one
of
the
criticisms
that
were
pointed
at
sold
down
tokensen
initially,
quite
frankly,
I
feel
this
is
a
this
is
not
a
soul,
bound
problem
or
a
soul
bound
token
problem.
This
is
a
entire
protocol.
Ethereum
problem
and
I
feel
like.
D
The
other
aspect
is
reactive
recovery,
which
is
where,
like
I
lost
everything,
then
you
know
that's
a
tricky
one.
You
have
to
establish
with
your
like
your
Dao,
for
example,
that
hey
I'm
the
same
person
behind
this
new
wallet
like
you
have
to
re-issue
it
and
one
of
the
models
we
are
looking
at.
There
is
reassurance,
but
the
community
perhaps
can
revoke
those
badges.
So
that's
that's
how
we're
kind
of
thinking
about
it.
Thanks.
C
G
C
D
D
This
is
one
of
the
forums
we're
hoping
to
get
feedback
on.
Like
you
know,
where
should
we
park
it?
Should
we
get
feedback
or
have
invest
in
extensions
and
like
because
there's
a
lot
of
utility?
This
can
deliver
in
its
current
form.
You
know,
and
then
it
would
be
strange
to
perhaps,
like
you
know,
stretch
this
timeline,
because
I
think
I've
seen
aips
go
for
years.
D
A
Yeah
I'm
just
gonna,
while
the
next
speaker
Sweetman,
is
going
to
set
up
the
the
laptop
and
so
on
I'm.
Just
gonna
walk
you
through
the
rest
of
our
timetable,
which
is
by
the
way
here.
So
next
up
is
sweetman.eath
and
he's
going
to
talk
about
music,
the
music
nft
engineer.
Then
we
have
Andres
who
is
going
to
talk
about
web3
the
web,
3
music,
nft
multiplayer
problems,
I'm
very
excited
about
that
I!
Think
it's
like
it
comes
out
of
water
and
music
research.
A
Then
we
have
Ian
who
is
going
to
talk
about
Rich
content
types
in
nfts
and
then
finally,
we
have
Francisco,
who
is
going
to
talk
about
a
like
a
very
recent
EIP
called
5267
I
think,
which
I
think
it
defines
the
domain
separator
of
EIP
712
so
yeah.
If
you're
familiar
with
that
I
guess
it's
you,
you
kind
of
understand
what
it
is.
If
not,
then
I
recommend
going
to
eips.etherium.org
and
reading
up
on
it.
H
H
H
First,
the
problem
you're
going
to
see
QR
codes
throughout
this,
the
ones
on
that
side
are
from
musicians
in
Latin
America.
If
you
want
to
support
creators
here
in
Latin,
America
scan
that
by
the
nft
support
local
creators
on
this
side,
you'll
see
cc0,
music,
nfts,
100
Freeman
on
different
chains
and
so
they'll
be
scattered
throughout.
If
you
want
some
nfts
momentum,
the
problem
don't
worry.
The
same.
Qr
codes
are
going
to
be
a
little
bit
hidden
in
here.
H
H
Up
top
you've
got
Zora
creator
in
the
middle
you've
got
catalog
and
down
at
the
bottom,
you've
got
sound
you'll
notice
that
they
each
have
different
metadata,
but
honestly,
there's
no
real
differentiation
between
the
metadata
of
a
music
nft
and
a
normal
nft.
In
most
cases
over
here
on
this
side,
you'll
see
the
music
metadata
standard.
This
includes
the
same
attributes
as
a
normal
nft,
in
addition
to
attributes
that
matter
for
music
attributes
like
lossless
audio
attributes
like
BPM
attributes
like
duration.
H
Next,
the
opportunity
another
set
of
nfts-
oh
yeah,
the
last
one
I'm
sorry
I,
didn't
I,
didn't
shout
out
the
Creator,
so
the
last
Creator
this
first
nft
is
caspiel.
We've
got
Colombo
in
the
audience
manager
of
cast
peel,
and
so
that
nft
is
from
a
musician
named
caspiel
who
dropped
on
Zora
Creator,
and
that
is
a
music
video
of
her
latest
music.
H
Video
reflejo
and
all
of
my
music
nfts
are
cc0
from
a
musician
named
Sagrado
based
out
of
Mexico,
my
favorite,
because
he
does
everything
cc0
this
next
one
over
here
we've
got
another
Zora,
nft
I
think
we've
got
tranky
in
the
audience
who
helped
a
Buenos.
Aires
Creator
named
well
created
a
platform
called
unun,
and
so,
if
you
scan
this
it'll
take
you
over
to
unun
to
Mint
some
music
nfts
from
local
Buenos
Aires
creators,
and
this
one
is
another
one
from
Sagrado,
and
this
one
I
believe
is
on
polygon.
H
Last
one
was
optimism
this
one's
on
polygon,
the
opportunity
we
have
an
opportunity
right
now
to
standardize
music
metadata
right
now
it's
been
in
discussions.
You
might
have
heard
about
telegram
groups.
You
might
have
heard
about
different
chats
that
are
scattered
amongst
the
music
nft
ecosystems.
Maybe
you've
talked
with
Hi-Fi
Labs
about
their
music
nft
standards.
Maybe
you've
talked
with
Zora
there's
a
lot
of
different
standards
out
there.
We
have
not
really
reached
consensus
and
I
find
that
awesome,
because
there's
no
gatekeeper,
there's
nobody,
that's
telling
us.
H
H
How
you
can
help
again,
the
music
metadata
standard
is
not
something
that
we're
gonna
have
Sony
or
Warner,
or
some
record
label
is
going
to
come
down
and
say.
This
is
how
it
is.
It's
going
to
be
bottom
up
from
the
engineers
that
are
building
from
the
creators
that
are
choosing
what
platforms
to
build
on
each
of
us
as
individuals
is
choosing
which
memes
we
want
to
propagate
in
order
to
make
the
mess
the
best
metadata
win.
The
final
set
of
nfts
we've
got.
H
This
is
a
catalog
nft
from
a
Creator
named,
hey
Bella,
who
is
also
based
here
in
Colombia
in
Medellin,
and
this
one
is
an
arbitrum
nft,
the
same
nft
by
Sagrado
spread
the
memes
all
the
ethereum
Wizards,
all
of
you
Builders.
We
are
building
it's
important
that
we
propagate
proper
music
metadata
when
we're
building.
If
we're
giving
these
musicians
poor
metadata,
we're
setting
them
up
for
failure
in
the
long
term
as
Spotify
as
iTunes
as
these
other
big
platforms,
the
future
tapes,
the
spin
amps
our
indexing
music
nfts.
H
That's
fully
on
chain
deployed
on
ethereum,
mainnet,
polygon,
mainnet,
optimism,
mainnet,
arbitrim
mainnet,
as
well
as
test
nets
for
all
those
Chains
It's
live
the
contracts
are
verified.
It's
fully
running
on
a
platform
that
I
built
called
decent,
and
so
what
I'd
like
to
ask
the
community
here,
I'm
not
very
familiar
with
the
IPS
I'm,
not
really
familiar
with
what
we
do
as
a
community.
The
formal
way
I'm
really
used
to
building
with
the
musicians
on
the
ground.
H
I,
don't
know
if
we
need
an
EIP
for
like
proper
music
metadata
for
us
to
get
aligned.
I,
don't
know
if
we
just
need
to
talk
with
the
Zoras
to
properly
plug
in
the
music
metadata
render
into
the
Zora
stack
so
that
musicians
can
use
it.
Maybe
it's
just
me
writing
an
EIP
with
Hi-Fi
labs
and
getting
it
plugged
in
there
there's
a
lot
of
different
ways.
We
can
propagate
this
meme
out
into
the
ecosystem.
H
I,
don't
really
know
what
to
do
and
I'm
not
going
to
claim
that
I'm
like
the
king
of
all
this
I
just
would
like
to
have
the
conversation
more
and
so
I'd
like
to
ask
for
help
in
propagating
these
music
metadata
memes.
So
we
can
help
musicians
adopt
this
technology,
so
that
musicians
can
start
leveraging
these
web3
rails
that
make
us
and
the
technology
that
we
love
so
powerful
and
groundbreaking,
and
like
fundamentally
changing
the
world
that
we
know
and
love,
that's
it
Viva
La
Musica.
H
These
are
all
the
music
nfts
that
I
showed
throughout,
and
then
these
are
a
lot
of
musicians
that
are
based
in
Argentina
and
Buenos
Aires
in
Argentina,
as
well
as
Colombia
that
I
work
with
on
a
regular
basis.
And
so,
if
you
want
to
talk
to
some
musicians
that
are
based
here
in
Latin
America
and
you
want
to
like
get
their
thoughts
or
help
them
out
or
talk
to
them
about
the
music
nfts
that
they're
making
I've
attached
all
their
Twitter
handles
above
so
please
reach
out
to
them.
H
D
I
was
wondering
like
how
what
was
your
process
in
navigating
to
the
EIP
like?
How
did
you
gather
information
about
like
music
metadata
is
a
very
complex
structure
right
like
and
there's
not
having
consensus
over
metadata
just
sounds
like
a
classic
music
industry.
To
be
honest,
so
I
was
wondering
like
how
was
your
process
to
getting
to
the
the
stage
and
the
EIP
generally
to.
H
Be
clear,
there
is
no
EIP
right
now.
This
is
this
is
a
bunch
of
blank
data
I
copied
EI
I
took
a
screenshot
of
eip721
and
I
blanked
out
the
data
to
just
kind
of
like
put
the
meme
in
your
head
as
something
that
we
can
do.
I,
don't
question
back
to
you.
Do
you
think
this
is
something
we
could
do
with
an
EIP?
Or
does
this
feel,
like
you
say,
like
the
music
industry?
Is
too
decentralized
for
us
to
come
up
with
an
eip4
music
metadata
standard,
I.
D
H
In
in
an
attribute,
I
didn't
talk
about
all
of
these.
All
of
these
decent
nfts
100
of
them
metadata,
is
on
chain.
So
one
of
the
awesome
Parts
about
l2s
is
it's
incredibly
cheap
to
store
all
metadata
on
chain,
and
so
we
can
store
that
entire
music
metadata
on
chain
for
less
than
a
penny,
and
so
musicians
that
are
based
in
Latin.
America
cannot
afford
to
do
transactions
on
each
mainnet,
but
by
offering
them
these
rails
to
be
able
to
create
music
metadata.
H
We
can
also
offer
them
the
opportunity
to
put
it
fully
on
chain
so
that
there's
no
trust
needed
in
apis
like
what
sound
uses
or
even
like
the
delay
you
get
by
uploading
to
ipfs,
if
you're
not
using
a
dedicated
Gateway
when
you
store
it
all
on
chain,
you
get
that
instant
availability
that
you
get
on.
Optimism
of
a
trim
polygon
and
the
other
l2s.
H
It
I'm
very
open
to
it
I'm
I'm
here
in
the
community
I,
my
entire
life
is
music
nfts,
and
so,
if
the
community
decides
that
we
want
an
EIP
I'm
about
it,
I'm
I'm
very
much
of
the
belief
that
I,
don't
I,
don't
want
to
say
like
this
is
the
way
I
like
hearing
like
the
music
metadata
standard.
I
didn't
come
up
with
that.
That
came
out
a
catalog
and
I'm
just
propagating
that
Meme,
because
it's
in
my
opinion,
the
best
meme
yeah.
C
No
I
I
think
a
great
first
step
would
be
to
public,
like
it
seems.
You've
done
a
lot
of
research
to
publish
that
in
some
written
form,
maybe
in
The
ethereum
Magicians
form
to
just
kind
of
keep
it
make
it
visible,
and
someone
else
can
then
maybe
pick
it
up
and
formalize
it
and
they're
in
the
IP.
That
would
be
very
valuable
and
I
I
want
to
offer
a
counter.
I.
Don't
think
that
you
specifying
something
and
standardizing
something
would
be
like
imposing
your
view
of
things
on
the
world.
C
I
Hey
it's
quite
funny,
because
obviously
I
wrote
they
bought
a
music
report.
Yesterday
they
came
out
on
this
subject.
Have
you
not
read
it
yet?
I
have
not
interested
in
because
there's
definitely
points
of
conflict
between
how
we're
seeing
this
and
for
me,
having
worked
like
the
whole
has
inside
the
Beast,
as
it
were.
I
H
I
This
is
the
challenge
right
and
then
you've
got
differentiological
buyers,
Publishers
producers.
All
these
people
who
are
part
of
this
Rich
soup
of
influencer
creates
a
piece
of
art
like
at
the
moment.
The
music
entities
were
in
a
pretty
nice
place
in
there
it's
usually
been
one
person
putting
something
out
but
gets
complicated
as
soon
as
like
that,
expands,
right
and
I.
Think
like
it's
really
important
that
as
we're
thinking
through
this,
we
need
to
be.
A
J
This
is
more
just
a
comment
about
whether
or
not
you
want
to
do
like
an
EIP
or
something
I
was
in
a
talk
yesterday.
That
was
like
see
something
called
like
c
a
I
p.
It
was
kind
of
over
my
head.
I'm,
not
gonna
lie
like
Captain,
but
it
was
a
different
type
of
like
Improvement
proposal
sort
of
like
Coalition
about
self-related
like
l2s,
and
things
I
mean
and
addresses,
so
it
could
be.
They
have
a
the
GitHub.
H
Yes,
so
here's
the
catalog
standard
and
you're
talking
about
cap
19
is
like
cross
chain
assets
in
here
we
have
references
to
other
types
of
assets
and
so
you'll
see
in
fields
like
artwork.
You
have
a
URI
and
a
mime
type,
which
is
very
normal,
but
then
you
also
have
this
nft
field
which
can
link
to
other
nfts
and
that
follows
the
cap
19
standard
of
cross
chain.
So
you
can
actually
link
different
nfts
if,
like,
for
example,
all
the
nfts
I
just
made
from
Sagrado
are
derivative.
H
Nfts
of
an
original
nft
I
did
not
link
the
original
nft,
and
that's
a
downside
on
me
and
I'm
going
to
publicly
say
that,
like
I
could
obviously
do
better,
but
the
standard
is
already
up
to
date
so
that
if
we
want
to
link
other
assets
within
our
nfts,
we
can,
and
so
when
we're
thinking
about
composing
nfts
is
music.
That's
built
on
top
of
stems
or
music
that's
built
on
top
of
other
music
or
a
remix.
That's
built
on
top
of
music.
That's
built
on
top
of
stems.
H
J
Is
mainly
just
mainly
referring
to
the
structure
they
have
like
on
GitHub
for
like
organizing
Community,
like
input
so
I
think
just
like
forking
the
GitHub
they
have
would
be
a
great
place
to
start.
If
you
were
trying
to
like
start
the
process
of
figuring
out
how
to
like,
you
know,
just
like
coordinate
between
a
lot
of
people
forking,
their
repo
seems
like
a
good
place
to
start
just
start
housing
that
information
in
some
place.
A
K
Started
off
a
few
months
ago,
a
in
the
whatever
music
Dao
researching
about
splits,
and
we
basically
got
two
three
main
conclusions.
Some
of
them
are
very
obvious.
Some,
probably
not
that
much
one
is
that
a
blockchains
can
serve
as
a
a
login
as
a
log
of
information
and
hopefully
look
into
the
future
even
like
a
global
jurisdiction
notary
system
with
a
legal
validation.
K
So
what
is
the
problem?
The
problem
is
copyright
right.
We
all
know
it's
the
problem
and
it
is
the
solution
and
copyright
law
has
been
used
and
has
been
abused,
but
it's
still
the
only
a
or
the
or
the
most
widely
used
form
of
monetization
of
intellectual
property
right
and
if
we're
looking
to
the
Future,
where
each
time
we
have
less
and
less
a
jobs
available,
we
have
a
growing
Creator
class.
K
It
is
mainly
a
human
problem
like
it
always
is,
and
it
is
that
people
do
not
register
their
intellectual
property
as
close
to
the
moment
of
Genesis
as
possible,
which
is
actually
the
the
best
way
to
protect
intellectual
property,
and
so-
and
this
is
maybe
because
creators
think
that
registering
or
then
speaking
about
legal
aspects
in
the
moment
of
creation
kills
the
Bible
so
that
actually
gives
birth
to
a
lot
of
problems.
I,
like
I've,
been
up.
K
K
So
personally,
I
have
been
in
those
situations
and
I
have
been
muscled
out
or
cut
out
of
hit
records
because
the
more
Savvy
people
will
head
out
and
register
the
the
copyright
of
the
song,
and
this
is
a
story
that
kind
of
like
repeats
itself
endlessly
in
in
music
making.
So
what
would
the
ideal
process
be?
K
The
ideal
process
would
be.
Would
be
to
register
to
have
a
mechanism
to
register
the
IP
as
soon
as
possible?
Right
in
a
nutshell,
a
in
a
nutshell,
it
would
protect
the
creators
and
hopefully,
in
consensus,
be
able
to
register
this
IP
in
consensus
right.
So
we
have
a
solution
right.
We
have
temp
temporarily,
called
it
a
copyright
wallet
and
a
copyright
wallet.
K
It
allows
it's
a
tool,
basically
it's
a
tool
that
is
inserted
in
the
job
to
be
done.
It's
a
you
know
like
a
small,
sharp
tool
that
is
inserted
in
a
job,
CB
Dom
process,
and
it
allows
for
in
multiplayer
mode,
deploying
registry
time,
stamping
a
registry
on
the
blockchain
of
that
intellectual
property.
K
K
K
The
same
way,
the
a
a
chat
with
you
know
like
have
access
to
to
listening
to
a
voicemail
or
or
a
shared
audio.
The
mobile
wallets
of
the
participants
would
receive
that
audio
and
they
will
receive
a
notification
too
accept
or
deny
their
participation
in
the
in
the
in
that
creative
process.
And
if
there
is
consensus,
then
a
smart
contract
is
deployed
and
the
non-transferable
nft
is
minted.
I
K
Answer
would
be
a
either
we
one
of
two
answers:
it
I'm
guessing
the
the
Dynamics.
The
current
Dynamics
are
more
of
like
you
songwrite
and
you
fixate
on
a
on
a
recording
immediately
right
just
because
the
tools
are
available.
So
people
are
not
writing
songs
with
their
guitar,
but
they
just
fixed,
like
they
just
record
them
immediately,
and
that
is
just
because
we
have
the
tools
to
do
it.
K
Unlike
before
we
used
to
like
Write,
Sheet,
Music
or
or
write
song
there,
a
lyrics
on
paper
so
but
the
but
I
guess
the
the
answer
to
that
would
be.
We
could
either
do
two
Registries
or
just
split
percentages,
because
at
the
same
time
you
know
like
writing
and
mastering
is
basically
a
master
like
or
like
recording
is
like
a
50
50
Endeavor
right,
so
we
could
split
from
just
one
big
chunk
of
100
of
ownership
or
mint.
You
know
specifics.
H
So
is
is
the
biggest
reason
we
want
it
to
be
a
wallet
so
that
we
can
have
that
kind
of
signature
based
approval
like
like
the
question
from
Dan
in
the
last
talk
of
deciding
when
the
metadata
would
get
to
be
updated
or
if
a
piece
of
work
can
be
included
into
a
movie
or
if
the
rights
could
be
included.
Like
you
have
that
signature
step
from
each
of
the
participants.
Is
that
the
reason
kind
of
thinking
of
it
as
a
wallet
or
what?
K
That
is
one
reason,
and
the
other
reason
is-
and
this
is
very
personal-
you
know
like
looking
into
the
future.
What
I
think
that
would
happen
or
would
would
happen
or
would
make
sense
if
it
would
happen,
is
that
this
contract
is
like
the
master
contract
of
all
the
IP
that
is
derivative
from
this
original
registry.
K
So
from
this
original
registry-
and
we
spoke
about
it
briefly
on
Twitter,
we
could
also
have
some
form
of
progress
nfts,
where
everybody
is,
for
example,
we
go
into
the
studio,
and
then
we
somebody's
gonna
come
and
feature
a
song
right
that
it
was
not.
He
was
not
or
she
was
not
in
the
studio
in
the
on
the
first
day
of
the
recording,
then
there's
a
way
of
tracking
the
progress
of
the
intellectual
property.
K
Obviously,
you
could
go
like
even
deeper,
with
a
Content
ID
mechanisms
and
whatnot,
but
but
I
think
that
this
smart
contract
would
probably
evolve
to
be
like
the
master
contract,
where
you
would
mint
the
one
of
one
of
the
song
or
the
10
editions
of
the
the
video
and
all
the
derivative
works
and
the
cruel.
The
value
in
one
contract.
Basically,.
I
But
when
I
was
when
I
did
that
design
I
was
I
proposed
that
you
have
like
a
time
period
that
can
be
defined
in
which
data
can
change,
and
at
that
point
it's
finalized
and
boom.
It
goes
and
that's
that
how
do
you
feel
about
that
in
terms
of
like
the
this
workflow?
Like
you
know,
do
you
see
that
you've
got
multiple
parties
kind
of
putting
their
information
in?
K
I
wish
you
right
yeah
we
wish,
but
if
the
tool
is
available,
that
might
be
an
incentive
right
and
if
we
fulfill
the
promise
of
value
through
these
a
specific
type
of
a
creative
product,
then
we
might
be
able
to
take
it
a
step
further
because,
right,
you
know,
like
20
years
ago,
split
like
splits
were
non-existent.
Basically,
Publishers
and
record
labels
were
the
ones
actually
doing
the
paperwork,
but
it
has
evolved
in
the
creative
mind
that
they
own
their
their
their
creation
said
that
they
want
to
be
a
part
of
split.
K
So
more
and
more,
you
see
like
producers
and
artists
and
songwriters,
be
like
okay,
like
let's
you
know
like.
Let's
show
me
the
splits
right
or
let's
negotiate
the
splits,
hopefully
as
soon
as
possible,
and
this
is
kind
of
just
like
inserting
it
in
that
moment
of
you
bounce
the
song
you
share
it.
Is
there
consensus?
How
do
we?
How
are
we?
You
know
like
splitting
the
ownership
of
this?
M
Yeah
I
have
a
question
so
I
understand
this
or
I
my
mind
tries
to
abstract
this,
like
the
concept
of
self-sovereignty
in
intellectual
property.
But
then
I
see
this
like
conflict
between
the
existing
structures
and
the
structures,
the
social
structures
basically
and
standards
that
would
have
to
evolve.
If,
This
Were
to
actually
come
and
have
any
chance
at
becoming,
like
the
dominant
form
of
of
you,
know,
managing
creative
IP
I'm
wondering
how
you
see,
like
the
end
game
of
this
playing
out.
K
A
global
copyright
database
right
if
that
makes
sense,
it
has
been
tried
several
times.
I
know
a
lot
of
people
are
accepted
into
that
or
I
don't
know
if
it
if
it
even
it's
a
good
idea,
but
but
there
has
been
efforts
in
you
know
like
like
just
sharing
the
information,
but
the
power
struggle
between
Corporation
makes
it
makes
it
impossible
right.
They
don't
want
to
just
have
that,
be
one
entity,
and,
and
that's
that
and
that's
where
the
efforts
have
died.
N
K
So
copyright
law
actually
states
that
you're
right
in
of
on
an
idea
is
immutable.
Nobody
can
take
that
away
from
you,
so
a
hypnosis
can
buy
the
the
Bruce
Springsteen
catalog,
but
you
know
like
Merk
could
never
say
he
sang
those
songs
right,
even
though
he
he
owns
the
financial
exploitation
of
of
the
IP.
A
A
O
O
If
you
have
questions
beyond
the
talk
or
you're
watching
it
recorded
make
a
GitHub
issue,
probably
the
easiest
way
to
respond
and
I'm
just
going
to
open
a
conversation
about
kind
of
what
we've
done
previously
as
an
organization
at
Zora,
What,
I've,
Done
personally
for
certain
nft
projects
and
rendering.
So
if
you
go
to
the
original
EIP
721,
the
metadata
scheme
is
pretty
lightweight.
You
have
a
name
description
and
image.
O
It
was
designed
an
era
of
crypto
punks
cryptokitties,
where
you
tracked
ownership
and
the
image
just
kind
of
showed
a
cute
item
or
like
the
thing,
and
then
that
became
more
and
more
important
with
time.
I
think
it
was
left
pretty
open-ended
for
people
to
build
out
from
here
and
I
do
like
that
idea
of
a
very
minimal
standard,
and
then
people
can
run
with
it,
but
I
think
at
some
point.
That
standard
can
also
be
improved.
So
an
example
is,
and
I've
had
co-workers.
Ask
me
this
all
the
time.
O
O
Openc
kind
of
added
animation
URL
to
show
an
animation
which
could
be
a
web
page,
gltf,
audio,
a
bunch
of
random
grab
bag
of
content
and
the
great
part
about
an
image
is,
if
you
want
to
render
it
as
a
consumer,
you
just
pop
it
into
an
HTML
image
tag
or
you
put
an
image.
Viewer
images
are
pretty
well
defined
on
how
to
render
animations
get
a
lot
more
complex.
O
What
we
could
do
is
we
could
convert
the
presentation
into
an
HTML
viewer
and
upload
the
HTML
viewer
that
becomes
pretty
cumbersome
and
a
little
bit
difficult,
because
the
original
content
is
the
PDF.
It's
not
the
HTML
viewer
and
the
way
Zora
approached
this
with
the
Zora
protocol
in
2020.
That
I
didn't
really
work
on
that
was
before
my
time
was
to
separate
this
concept
of
metadata
and
content.
O
So
if
we
were
to
Mint
a
presentation,
it
would
be
the
PDF
and
then
the
metadata
is
defined,
also,
incredibly
simply
as
name
description,
mime
type
inversion.
The
mime
type
is
useful
for
rendering,
as
I
said,
you
need
to
have
some
idea
of
what
you're
going
to
render
before
and
fetching
it
from
the
server
just
to
figure
out
what
the
mime
type
is
is
a
little
bit
frustrating.
O
So
this
here
calls
the
token
URI.
It
returns
a
ipfs
file
and
then
here
that
file
is
just
text
of
these
two
icons.
The
token
metadata
URI
is
name
description,
mine
type
textplane,
so
that
tells
the
Zora
platform
to
render
a
text
plane
image
of
that
per
text,
plane
of
that
nft
and
I.
Don't
think
there
have
been
a
lot
of
platforms
that
support
this.
O
So
when
you
try
to
look
at
an
open,
C,
good
luck-
and
that
brings
me
to
my
next
point
of
thinking
about
going
back
in
Computing
history
of
what
people
have
done
to
solve
this
problem.
This
is
a
multi-part
form
data.
It's
used
for
email,
kind
of
and
used
when
you
upload
files
in
a
classic
web
form,
it
has
content
type
and
it
has
a
certain
set
of
attachments.
O
Here
you
have
an
example:
sorry
got
out
of
weight,
so
an
example
of
what
we
could
do
is
add
a
new
field
to
the
metadata
standard,
either
through
a
secondary
proposal
mechanism
or
the
EIP
standard.
That
represents
what
we
just
talked
about
and
there's
a
lot
of
details
here
to
unpack.
So
one
of
them
is
maybe
you'll
want
to
include
the
content
directly.
Should
it
be
body
or
should
it
be
encoded
in
a
data
URI?
O
In
that
case
the
content
type
is
redundant,
but
when
you
have
an
external
pinned
file,
you
really
want
that
content
type
for
rendering
it
just
makes
life
so
much
easier
from
a
platform
and
indexing
standpoint.
If
you
have
a
really
obscure
file
type,
let's
say
somebody
loves
to
upload
Illustrator
files.
You
could
use
an
indexer
to
find
every
illustrator
file
with
a
very
simple
content,
standard
and
I.
O
Think
the
idea
here
is,
you
have
a
token
ID
represented
by
a
file,
and
the
metadata
describes
that
file
is,
but
that
file,
when
you
need
to
have
a
file
with
your
nft
is
the
highest
resolution,
the
most
the
highest
resolution.
The
most
well-known
version
of
that
an
example
is
Zora
was
brought
on
to
work
with
the
Warhol
Foundation
to
Mint
one
of
the
original
computer
nfts,
and
it
was
made
on
an
Amiga
with
a
beta
version
of
software.
O
An
art
collector
is
really
frustrated
that
the
nft
was
a
tiff
file,
but
it
was
built
with
the
Zora
protocol,
meaning
it
did
support
Tiff
files.
However,
nobody
else
did
so.
What
we
had
to
end
up
doing
is
use
the
external
URL,
which
is
an
openc
extension
to
link
to
something
to
link
to
the
Tiff
and
then
switch
the
image
URI
to
become
a
PNG
that
renders
everywhere-
and
this
is
after
back
and
forth
with
conservationist
and
with
different
protocols
as
to
what
they
expect
the
nft
to
be.
Now.
O
If
we
were
to
use
the
content
standard,
we
could
Define
the
image
that
renders
as
a
preview
with
ipfs,
and
then
we
could
use
the
Amica
mime
type
or
just
a
binary
blob
with
some
notes
around
it.
In
the
description
to
refer
to
the
original
media
and
I.
Think
that
would
help
conservationists
feel
better
that
the
nft
is
representing
what
it
really
represents
and
not
needed
to
be
converted
into
a
new
format
to
be
an
nft.
O
This
is
not
very
helpful.
We
could
try
to
expand
that
content
field,
but
that
could
be
any
file
type,
as
I
said
before
it
could
be
some
binary
blob
or
it
actually
could
be
useful
Json.
So
if
it's
defined
as
Json
or
maybe
an
extension
to
Json,
you
could
use
that.
But
the
ID
here
is
would
be
the
markdown
and
if
Mirror
Has
extra
information,
they
could
use
their
own
fields
to
refer
to
that
information
within
the
content
file
or
outside
there's
a
way
you
can
actually
add
Json
headers
to
markdown
files.
O
O
Don't
work
for
security
reasons
here,
it's
slightly
better,
but
also
links
don't
work
due
to
security
reasons.
The
sandboxing
on
an
iframe
is
actually
pretty
difficult
to
work
with
If
This
Were
A
markdown
file.
You
could
just
run
it
through
whatever
markdown
renderer
or
even
provide
a
link
and
just
show
the
preview
image
associated
with
the
nft.
O
It
is
a
part
of
the
Ringer's
art
blocks
collection
and
it
is
a
follow-up
limited
time
Edition
where
funds
went
to
charity,
and
it
was
a
very
large
SVG,
megabytes
and
megabytes.
Svg
and
I
believe
manifold
helped
with
the
mint
and
the
original
file
for
image
was
an
SVG,
but
that
SVG
broke
wallets
and
people
were
not
happy
because
an
SVG
is
text
and
for
you
to
encode
text,
you
actually
have
to
turn
the
SVG
into
some
sort
of
bitmap
format
and
then
convert
it
again
and
resize
it.
O
So
it's
really
difficult
to
resize
in
SVG
and
most
marketplaces
pass
through
the
SVG,
but
this
particular
SVG
was
so
large.
It
started
breaking
stuff,
so
what
they
had
to
do
is
they
actually
had
to
update
that
and
change
the
image
to
a
PNG
that
did
render
well,
but
it
was
a
12
21
000
by
43
000,
pixel
PNG,
which
also
caused
some
problems
because
marketplaces
taking
the
PNG
or
whatever
image
file
resize
it
to
reasonable
size
and
display
it.
O
So,
if
you
own
that
to
your
wish
to
display
it,
you
can
then
download
that
original
file
and
work
with
it
as
you
will,
and
if
you
were
to
take
the
content
type,
you
could
then
encode
the
image,
SVG,
XML
and
then
a
URI
and
then
optionally
include
a
sha256
if
you're
using
airweed,
that's
actually
a
really
nice
way
of
verifying
that
the
file
is
what
it
is,
because
airweave
doesn't
use
content
addressable
hash.
So
the
the
link
to
ipfs
for
every
file
is
unique
per
file,
but
for
our
weave
it's
different.
O
O
The
idea
of
this
proposal
is
to
add
in
a
Content
field,
and
the
idea
with
content
is
it's
quite
simple:
it
doesn't
have
any
underscores
and
it's
the
first
time
I
think
there's
going
to
be
some
proposal
or
thought
process
around
creating
nested
structures
in
the
metadata,
but
I
think
it's
quite
useful
because
content
underscore
type
content
it
just
doesn't
like.
We
already
have
Json.
O
We
can
Nest
this,
but
type
URI,
shot,
256
and
potentially
potentially
body
for
those
that
want
to
directly
put
plain
text
in
but
I
feel
like
a
URI
encoding
is
also
usually
a
fine
option.
I'd
love
to
hear
what
different
creators
of
Standards
or
media
have
another
thought
was.
You
could
have
some
sort
of
attachments.
Associated
say
you
have
an
image
that
a
product
you're
selling
as
an
nft,
and
you
have
a
slideshow
I,
recently
worked
with
the
team
to
show
a
product
and
the
slideshow
had
five
images.
O
O
Where
you
have
this
media,
how
do
you
render
it
well
on
a
Marketplace
or
in
another
context,
I
think
that's
out
of
scope
for
this
particular
Focus
and
the
meaning
of
canonicals
to
have
a
standard
or
primary
authoritative
body
on
a
subject.
So
the
URL
is
the
authoritative
idea
of
what
that
nft
is,
and
it's
left
up
to
interpretation
of
the
Creator
or
the
platform,
to
figure
out
how
to
best
Express
that
and
use
it.
O
My
open
questions
are:
should
this
be
an
EIP
within
The,
ethereum,
Magicians
group
chat?
That's
a
pretty
widely
debated.
Topic
of
metadata
is
included
in
the
original
proposal,
but
it's
not
really
defined
beyond
that
and
it's
defined
quite
Loosely.
So
one
thing
I
like
to
do
is
try
to
stick
to
proposals
and
I'll
typically
use
the
Key
Properties,
instead
of
whatever
has
been
defined.
O
I
have
a
GitHub
of
these
files,
and
this
is
my
Twitter
and
zoom
in
a
little
bit
and
then
the
one
last
thing
is:
there
was
an
on-chain
version
of
this
EIP
content
type
that
used
mime
content,
URI
and
hash,
and
this
is
kind
of
the
inspiration
for
the
off
chain
version
of
this
proposal.
Unchained
ideas.
If
you
have
dynamically
generated
SVG,
it's
more
composable,
it's
easier
just
to
return
a
struct
but
I
think
now
kind
of
working
on
more
projects
and
finding
more
examples.
O
The
off
chain
example
is
more
compelling
and
you
can
still
generate
a
Json
blob
on
chain,
including
the
content
field,
so
it
kind
of
works
both
ways.
I
just
think
this
is
a
better
start
to
the
approach,
a
way
to
approach
this
project
then
including
a
new
getter
function
as
an
EIP
within
the
solidity
world.
This
is
all
off-chain
metadata.
L
O
I
hope
the
very
first
thing
is
indexers
Pro
platforms
would
include
it
in
minting,
so
manifold
actually
does
really
try
hard
to
include
a
lot
of
metadata.
They
do
image
image
underscore
URL
image
includes
the
hash
and
the
URL
and
the
content
type
and
some
other
data,
so
I
think
kind
of
thinking
with
them
to
figure
out
what
their
needs
are.
O
Oh
here
is
a
solidity
contract
and
what
I
typically
have
advised
creators
to
do
is
actually
explain
it
and
link
in
the
description.
The
ipfs
URL
of
the
canonical
media,
it's
Packy,
but
it
seems
to
have
worked,
and
that
would
kind
of
remove
that
and
allow
for
use
users
to
see
like
a
link
and
I've
seen
artists
on
Twitter
talking
about
using
unlockable
media
and
open
C
to
include
the
source
files.
O
P
O
So
the
one
problem
when
you're
indexing
is
that
a
lot
of
times
ipfs
is
really
slow.
People's
servers
go
down
if
you're
able
to
get
the
metadata
on
the
client
a
lot
of
people
hot
link
directly
to
an
ipfs
Gateway
and
pulling
the
content
type
out
of
the
headers
really
allows
for
a
better
set
of
expectations
when
you're
indexing
and
rendering
the
nft.
But
your
question
is
to
kind
of
use
the
HTTP
response
conversation
to
define
the
Mind
type
rather
than
put
it
in
the
metadata.
P
O
I
think
a
lot
of
the
off
off-chain
nfts
go
through
a
decentralized
Gateway
provider
and
those
Gateway
providers
are
not
very
like
you're
out.
The
control
of
the
server
retrieving
decentralized.
Media
is
out
of
the
control
of
the
user
in
most
cases,
so
you
can't
rely
on
a
server
negotiation,
you're
thinking
of
a
world,
maybe
where
there's
a
server
that
is
connected
to
the
URI
of
the
nft
and
that's
becoming
a
lot
less
common,
because
that
means
you're
now
having
a
centralized
point
of
failure.
O
So
the
idea
here
is,
if
you
put
it
in
the
Json
there'll
at
least
be
some
intentionality.
If
you're
on
some
weird
version
of
ipfs
like
node,
that
doesn't
understand
the
media,
it's
serving
or
there's
a
bug
in
it.
You'll
still
have
something
that
kind
of
works
or
have
an
expectation
of
what
the
original
intention
was.
A
G
O
That's
actually
a
great
question
that
I
didn't
have
time
to
address,
but
mirror
and
Zora,
and
a
few
other
platforms
have
editions
and
I
think
utilizing
a
singular
nft
metadata
in
the
contract.
Uri,
which
is
an
openc
extension,
is
a
really
effective
way
to
handle
that
and
right
now,
I
know
most
platforms
that
do
additions,
support
the
contract
URI
so
for
dead
ringers
and
for
Zora
editions.
The
contract
URI
is
actually
generated
on
chain
and
sometimes
we'll
put
an
ipfs
depending
on
how
big
the
content
is,
and
that
includes
image.
O
It
includes
animation
if
every
single
thing
in
the
collection
is
the
same,
and
we
use
that
internally
in
our
infrastructure
to
give
a
preview,
if
there's
no
mints
yet
or
like
what
that
whole
collection's
supposed
to
be,
there's
no
standard
around
it,
but
this
would
also
slot
quite
well
within
the
contract
metadata.
If
you
wanted
to
have
a
canonical
contract
content
field,
it
should
just
work.
A
C
Gladly
yeah
so
sorry
we're
gonna
move
on
from
nfts.
Now
it's
going
to
be
about
erc20s,
which
are
boring
now,
but
okay,
I'm
correction,
I'm,
not
from
openc
I
work
at
open,
Zeppelin,
maintain
and
develop
open
sampling
contracts,
which
obviously
maintains
many
ERC
implementations.
And
so
this
is
a
really
important
topic
to
me.
C
So
this
eib
that
I'm
going
to
be
talking
about
is
really
quite
tiny,
but
I
want
to
use
it
more
as
an
excuse,
maybe
to
talk
about
the
process
of
building
an
EIP
and
what
the
kind
of
steps
that
I
think
one
should
follow.
So
because,
like
eip1,
which
it's
not
here,
but
maybe
you've
all
seen
it
kind
of
defines
the
series
of
stages
like
draft
review
last
call
and
final.
But
it
doesn't
really
say
what
should
happen
in
each
of
those
stages.
C
So
the
problem
at
hand
here
is
the
erc20
permits
anyone
that
has
used
a
amm,
a
decentralized
exchange.
Before
knows
that,
in
order
to
do
a
token
exchange,
you
need
to
approve
first
and
then
transfer,
and
this
EIP
permit
is
one
way
of
foregoing
the
initial
approved
transaction
and
replacing
it
with
a
signature
that
allows
you
to
allows
you
to
do
it
all
in
just
one
transaction
by
just
including
the
signature
in
the
first
transaction.
C
So
this
saves
gas,
it
is
one
less
transactions
and
it
uses
the
signature
instead,
but
it's
kind
of
weird.
If
you
use
an
exchange
or
an
aggregator,
you
don't
really
see
this
being
used
very
often,
I
think
main,
maybe
it's
just
for
like
usdc
exchanges
supported,
but
there
are
many
other
tokens
that
have
this
and
don't
so.
The
question
that
was
in
the
back
of
my
mind
is
like:
why
is
this?
Why
is
that
so
weird?
So
the
this
EIP
underneath
uses
this
other
EIP
712.
C
C
In
the
case
of
permit,
you
will
include
the
amount
that
you're
allowing
you
will
include
and
expires
timestamp
and
a
nouns
and
so
on,
and
this
is
an
important
standard,
because
wallets
can
Implement
support
for
it
and
show
this
structured
data
to
the
user
in
a
nice
way.
One
of
the
important
things
in
these
EAP
is
the
notion
of
a
domains.
So
when
you
make
an
approval
for
say
usdc,
you
don't
want
an
attacker
to
take
that
signature
and
kind
of
send
it
to
die
right.
C
You
don't
want
an
attacker
to
reuse
the
signature
in
a
different
domain,
so
every
signature
has
this
domain
separator
inside
of
it.
That
makes
sure
that
the
signature
is
only
valid
in
one
domain.
So
this
is
the
right,
so
the
decentralized
exchange
has
no
way
of
knowing
given
some
arbitrary
token.
What
domain
they
want
to
use
and
I.
Think
yeah.
I
think
that
is
the
reason
why
this
hasn't
been
really
adopted.
C
So
you
will
see
that
the
erc20
permit
ERC
defines
a
getter
that
gives
you
the
hash,
but
really
the
712
RPC
endpoint
requires
the
entire
domain
object
and
there
is
really
no
way
to
find
it
here.
So
this
is
where
eip5267
comes
in
now
we
will
see
now
it's
a
very
simple
function
that
literally
just
allows
you
to
obtain
the
domain.
C
C
Is
this
useful
to
you?
Would
it
does
this
solve
a
real
problem
from
for
you
and
generally,
the
answer
in
this
case
has
been
yes
in
the
ethereum
magician
threat.
There's
also
been
a
couple
of
interesting
comments
and
common
questions.
I
have
taken
some
of
the
questions
and
documented
them
as
part
of
the
EIP
as
well,
and
also
some
concerns
that
have
arised.
C
And
here
I'm,
putting
myself
in
the
shoes
of
I
am
the
UI
for
one
inch,
and
this
is
what
I'm
going
to
be
doing
and
just
kind
of
really
figuring
out
if
it
works,
if
I
can
actually
produce
the
signatures
that
they
will
need
to
produce
and
also
to
use
this
to
figure
out
the
backwards.
Compatibility
story
and
I
still
need
to
develop
this
a
little
bit
further,
but
I'm
hoping
that
I'm
going
to
come
up
with
a
good
and
kind
of
comprehensive
answer.
C
C
I
think
yeah,
that's
it
again.
It
was
very
quick,
but
these
are
some
of
the
things
that
I've
been
experimenting
with
in
order
to
get
this
to
a
final
stage,
I
think
there
are,
we
see
many
eaps
that
take
more
of
a
fast
track
and
get
to
a
final
stage,
which
is
you
know
it's
better
in
a
way,
because
we
know
that
these
processes
can
be
long
and
it's
really
annoying.
C
But
then
you
get
to
a
final
stage
and
it
doesn't
necessarily
mean
anything
if
it
hasn't
been
thoroughly
tested
and
then
you're
really
going
to
run
into
some
issues
when
say
open,
Zeppelin
implements
it
and
people
start
deploying
it,
and
you
realize
oh
this,
this
isn't
really
enough.
So
then
you
need
to
start
thinking
about
like
a
follow-up
EIP
and
it's
all
really
much
more
complicated
than
it
should
be.
If
we
do
things
better
before
we
get
to
a
final
stage
so
anyway,
those
are
some
of
my
ideas.
Thank
you.
E
Hey
really
cool
first
comment:
it
reminds
me
of
like
the
Amazon
six
page,
written
narrative
way
of
you
have
to
like
sharpen
your
point
or
your
case,
and
then
you
go
around
and
get
feedback
from
people
and
then
incorporate
that
in
a
fact,
at
the
end
of
the
document
to
like,
because
you
know
other
people
have
those
concerns
or
objections.
So
that's
really
awesome.
Do
you?
Can
you
just
speak
a
little
bit
more
about
that
process
and
how
you've
followed
up
with
people,
maybe
on
this
one
or
something
in
the
past?
E
So
it's
one
thing
for
somebody
to
say
it
looks
great,
maybe
give
some
feedback
on
The
ethereum,
Magician's
post,
but
really
an
eip's
success
or
failure
is
like
people
using
it
like
you
just
spoke
to
so.
Have
you
have
a
good
example
of
like
following
back
up
with
protocols
and
actually
getting
them
to
implement
the
EIP
as
part
of
your
kind
of
Biz
Dev
work?
If
you
call
it
yeah.
C
So
good
question
I
haven't
thought
about
that
too
much
yet,
but
one
of
the
things
that
I
I
personally
struggle
with
is
that
I
feel
like
I'm
in
a
bit
of
a
conflict
of
interest
position
because
of
being
on
opens
up
and
contracts
maintainer.
It's
like
it's
going
to
be
really
easy
for
me
to
put
this
in
the
contract
and
make
people
use
it,
but
I
don't
want
to
force
it
down
people
so,
for
example,
one
thing
that
I
could
do
and
now
that
I'm
thinking
about
I
think
it
will
be.
C
A
great
idea
is
to
talk
to
this
one-inch
developer.
That
I
talked
about
and
maybe
try
to
get
them
to
to
walk
me
through.
Do
they
really
see?
Do
they
like
really
see
themselves
implementing
this,
and
maybe
what
is
the
timeline
and
kind
of
yeah
just
trying
to
get
more
concrete
data
on
on
their
plans
and
try
to
try
to
get
them
to
commit?
A
Yeah
and
that's
essentially
it
that
was
the
ERC
lightning
talks
from
The,
Magicians
I
hope
you
all
liked
it.
You
can
find
each
and
everyone,
hopefully
on
the
East
magician's
forum
and
I'm,
looking
forward
to
all
of
the
posts
that
are
coming
out
of
these
discussions.
I'm
I
want
to
thank
you
all
for
participating
like
so
much
in
this
conversation
and
I
I
really
appreciate
that
we
were
having
like
a
back
and
forth
between
the
audience
and
and
the
presenters
and
so
on
and
yeah.