►
From YouTube: PSF TSC Meeting - 03/03/2021
Description
The agenda for this meeting:
https://github.com/Permissionless-Software-Foundation/TSC/issues/5
A
A
A
C
D
A
All
right,
so
the
big
things
on
the
agenda
today
is
changes
to
bch
api.
There's
been
a
lot
of
changes.
First
of
all
we
had
announced
about
a
month
ago
that
we
were
going
to
be
deprecating,
the
v3
branch.
So
when
you,
when
you
instantiate
bchjs
the
javascript
library
by
default,
it
will
use
the
v4
branch,
so
people
who
don't
like
understand
what
I'm
saying
can
safely
ignore,
what
I'm
saying,
but
for
businesses
who
need
more
fine-grained
control
over
bch,
api
or
bchjs
and
how
it's
instantiated.
A
This
is
important,
so
the
v3
route
was
an
older
route.
Probably
about
four
months
ago,
we
created
the
the
v4
route,
because
there
was
some
breaking
changes
so
with
the
api.
What
we
try
to
do
is
not
it's
okay
to
add
new
features,
but
we
try
not
to
affect
backwards
compatibility,
and
so
whenever
we
need
to
make
a
change
that
would
negatively
affect
backwards
compatibility.
A
So
that's
the
first
item
and
the
second
item,
the
more
salient
things
is:
there's
this
new
user
object
that
so
joey
you
and
I
had
had
a
conversation
a
couple
meetings
ago
about
this
trade-off
between
abstraction
and
rate
limits,
where
it's
like
in
order
to
provide
a
good
user
experience.
We
want
to
provide
these
high
levels
of
extraction
like
utxo.getcall
in
bchjs
is
a
good
example.
A
You
just
you,
give
it
an
address
and
it
gives
you
back
another
object
that
has
all
the
utxos
sorted
by
like
normal
bitcoin
cash
and
then
like
slp
tokens
and
with
including
minting
batons
or
sorted
from
regular
tokens
and
then
nfts,
and
so
the
group
and
the
chil
in
the
nft
and
the
minting
batons.
Those
are
all
separated
into
different
arrays
and
so
that's
highly
convenient
for
a
wallet
developer,
to
make
one
call
and
to
get
all
these
really
nice,
hydrated
and
and
sorted
utxos.
A
But
what
actually
happens
behind
the
scenes
is
this
incredibly
elaborate
chain
of
api
calls,
and
so
it's
a
very
api
heavy
call
and
I've
seen
over
and
over
and
over
again
this.
This
repeating
thing
where,
if
you
don't
con,
if
you
give
people
the
ability
to
abuse
an
api
call,
they
will
and
so
rate
limits,
is
how
you
reel
this
in
and
keep
everything
fair
and
the
problem
that
I've
been
having
up
to
this
time.
A
A
A
So
the
call
I
was
just
talking
about
is
this
hydrate
utxos
call,
and
that
is
really
just
a
wrapper.
You
call
that
and
then
bch
api
calls
token
utxo
details
and
what
it's
doing
is
it's
passing
this
user
object,
which
contains
like
your
ip
address
and
if
you
passed
in
a
jot
token,
that
would
come
along
for
the
ride
too.
A
So
what
I
can
do
now
is
even
though
bch
api
is
making
all
these
internal
calls
it's
still
tracking
the
rate
limits
per
user
really
per
ip
address,
and
and
so
I
can
apply
the
normal
rate
limits,
even
though
the
calls
are
whether
they're,
internal
or
external,
the
same
rate
limits
get
applied
to
the
same
user.
So
what
this
did
is
the
normal
users
just
casually
use
the
web
wallet,
they
it
restored
their.
A
A
This
trade-off
that
I've
made
in
that
everyone's
getting
the
rate
limits
applied
to
them
fairly,
whether
you're,
making
internal
calls
or
external
calls,
and
it's
just
something
to
be
to
be
mindful
of
because
anybody
who's
using
who
who's
using
the
public
full
stack.cash
bch
api
that
who's,
making
heavy
calls
to
hydrate
utxo
they're,
going
to
start
to
see
rate
limits.
A
lot
more
and
and
the
way
that's
going
to
manifest
itself
is
you'll.
Get
utxos
within
with
a
null
value.
A
A
Okay,
so
joey
you're
gonna
see
this
same
problem
if
slp
tokens
on
the
abc
chain
take
off
like
you're.
This
is
these
are
the
same
problems
that
you're
gonna
wrestle
with,
and
it's
probably
a
ways
out
for
for
you,
but
this
is
sort
of
how
I'm
dealing
with
it
we'll
see
how
it
works,
and
you
know
I'll
adapt
if
it
turns
out
to
not
be
a
good
solution.
A
But
yeah
like
like
what
what's
so
nice
about
the
abc
chains.
You
guys
don't
have
to
worry
about
these
scaling
issues
and
because
it's
not
only
this,
it's
also,
you
know.
Slp
dbs
are
getting
more
expensive
to
run,
and
so
there's
there's
just
a
lot
of
sort
of
leaky
holes
in
terms
of
scaling
with
slpdb,
and
so
the
best
solution
I
can
come
up
with
is
just
to
sort
of
plan
for
a
for
a
messy
reality.
A
A
A
In
fact,
I'm
probably
gonna
drop
the
price
of
100
rpm
tier
down
to,
like
I
don't
know,
maybe
five
dollars
and
five
to
ten
dollars
and
then
I'll
offer
another
like
300
and
then
500
and
then
thousand
rpm
tiers
at
higher
prices
and
but
so
for
people
who
are
using
the
free
tier
at
20
rpm
or
want
to
buy,
like
that
first
step
up
to
100,
rpm
and
they're
bumping
up
against
rate
limits.
This
is
a
really
good
way
to
continue
to
operate
within
the
scope
of
a
lower
rate
limit
here.
A
A
The
first
is
users
that
are
just
running
bch
ap
api
locally,
and
they
don't
want
to
deal
with
rate
limits,
and
you
know
they
can
safely
essentially
run
a
public
interface
because
no
one's
going
to
connect
to
it
with
them,
and
they
just
don't
want
to
deal
with
all
this
rate
limit
stuff.
Someone
just
submitted
an
issue
on
the
repo
requesting
this,
and
I
thought
that
was.
That
was
a
pretty
good
idea.
A
So
that's
the
first
use
case.
The
second
use
case
is
people
who
run
their
own
private
instance
of
bch
api.
I
believe
this
is
what
abc
is
doing
and
what
some
of
the
full
stack
dot
cash
clients
are
doing,
where
they're
running
their
own
local
instance.
They
want
to
run
as
fast
as
possible.
They
don't
want
rate
limits
applied
to
them,
but
it's
publicly
exposed.
A
So
they
need
to
be
able
to
have
basic
authentication
so
that
so
that
they're,
the
only
ones
allowed
to
to
talk
to
the
system
or
the
system,
will
only
respond
to
them.
And
so
that's
the
case.
So
I
already
have
that
case
built
in,
but
but
that's
going
to
get
revisited
well,
where
it's
just
basic
authentication,
you're,
essentially
passing
in
a
password
in
the
header
and
and
if
you
don't
do
that,
the
system
just
won't
respond
to
you
and
then
the
third
use
case
is
people
who
are
buying
these.
A
These
rate
limit
tiers
on
full
stack,
dot
cash.
You
know
so
we'll
have
20,
which
will
be
the
300
rpm,
which
is
the
first
paid
tier,
and
then
there
will
be
a
300
and
a
500
and
a
thousand
rpm
tiers
and
then
all
the
way
and
then
from
there
there's.
The
fourth
use
case
is
the
or
that
that
is
the
fourth
use
case
then,
and
then
there's
people
who
are
running
private
instances,
in
which
case
they're
using
basic
authentication.
A
A
And
yeah,
so
that's
pretty
much
the
agenda,
that's
pretty
much
what
I
have
to
cover
today.
Let's
talk
real
briefly
about
nfts
they're,
they're,
all
the
rage,
seeing
a
lot
of
people.
A
lot
of
people
are
reaching
out
to
me
asking
about
nfts
and
then,
of
course,
there's
pushback,
because
all
I
have
is
developer
tools
and
most
those
people
are
not
developers,
in
which
case
I
really
just
don't,
have
anything
for
them
and
yeah.
It's
just
all
the
rage.
A
I
mean,
I
think
it's
it's
we're
in
an
interesting
position,
both
bch
and
abc,
because
we
have
technology
for
scaling
and
low
transaction
fees
are
really
attractive
for
this
nft
world
and
they
effectively
like
mechanically
under
the
hood.
They
they're
very
different
than
ethereum,
like
in
terms
of
how
you
create
them
and
move
them,
but
their
usage
is
is
pretty
much
exactly
the
same.
A
It's
not
a
it's
a
non-fungible
token
that
you
can
apply
a
a
piece
of
content
to
like
a
song
or
a
picture
usually
hosted
on
ipfs
and
and
so
that's
pretty
attractive.
One
of
the
big
bottlenecks
I
see
for
for
both
of
these
chains
is
that
you
can't
use
the
slpdb
whitelist
feature
for
nfts,
because
they're
they're
unique
so
for
fungible
tokens.
A
One
of
the
ways
you
can
get
away
from
the
scaling
bottleneck
that
slpdb
is
currently
experiencing
is
by
using
the
white
list,
so
you're
essentially
telling
slpdb
ignore
everything
all
the
tokens
in
the
world,
except
for
what's
on
this
list
and
that
that
makes
scaling
super
easy
in
terms
of
tokens.
But
that
approach
doesn't
work
for
nfts,
because
nfts
are
each
unique,
and
so
you
can't
ahead
of
time
know
what
the
token
id
of
an
nft
is
going
to
be
in
order
to
to
add
it
to
the
white
list
of
slp
db.
A
The
white
list
is
something
you
have
to
create
prior
to
syncing
slp
db.
So
it's
you
sort
of
hit
go
and
then
you
you
can't
you
can't
dynamically
adjust
that
list
later
on.
At
least
I'm
not
aware
of
a
way
to
do
that.
I
have
caught
wind
of
someone
who
is
working
on
like
a
whitelist
feature
for
nfts,
but
I
don't
have
any
technical
details
on
that.
A
E
You
still
need
a
lot
of
kind
of
technical
ability,
but
because
they've
really
proved
it
out,
everybody
builds
them
there.
So,
even
though
you
have
the
same
technical
capacity
on
the
bitcoin
cash
stuff,
the
market's
not
there
so
like.
Yes,
there's
a
lot
of
technical
stuff
like
that's
important
and
we
can
worry
about
it,
but
I
think
all
we
really
need
to
focus
dev
efforts
on.
If
we
want
this
like
we
want
people
to
care
about
it,
we
need
some
way
to
make
markets
and
sell
it.
E
E
A
So
he
said
something
there
that
I
want
to
explore,
because
I
have
my
own
opinion,
but
I
want
to
hear
your
guys's
opinion,
so
one
of
the
the
unfortunately
consistent
patterns,
I'm
seeing
around
slp
tokens,
is
that
everybody's
focused
on
like
the
marketing
and
the
usage
of
it,
and
they
want
to
just
ignore
the
engineering
details.
And
so
you
know
like
spice
and
honk
were
the
first
two
really
like
popular
slp
tokens
and
they
continually
broke
all
the
slpdbs
in
the
world
like
like
they'd
cause
a
problem.
A
We'd
all
come
together
and
fix
it
and
get
it
running
again
and
then
they'd
kill
it
again
like
a
week
later,
just
from
the
sheer
volume
and-
and
this
this
is,
the
same
problem
is
happening
right
now
with
nfts
sweet.
I
o
is
probably,
I
think,
the
push
in
the
the
state
of
the
art
with
nfts
on
the
bitcoin
cash
chain,
with
their
phone
out
and
they're,
creating
a
ton
of
nfts
and
people
are
trading.
A
Nfts
and
and
they've
crashed
all
the
slp
dbs
in
the
world
a
couple
times,
and
it's
a
good
thing,
because
we
get
stronger
every
time.
This
happens.
Even
though
it
literally
affects
everyone
in
the
world
trying
to
use
this
technology
and
we're
gonna
continue
to
see
this
pattern,
and
so
it's
like
there's
like
there's,
I
can
see
both
arguments
right
here
like
like
one.
One
option
is:
let's
just
ignore
the
technical
issues
and
push
forward
and
with
what
we
have
and
get
people
excited
and
hopefully
like
through
that
excitement.
A
E
Yeah
I
mean
it'd
be
great
to
just
solve
them
all,
but
I
don't
think
there's
enough
interest
for
people
to
do
it
unless
there's
some
serious
money
on
the
table
so
yeah
like
best
case
scenario,
it
works
it's
flawless
but,
like
even
you
know,
imagine
the
hypothetical
scenario
like
every
engineer.
Who's
ever
worked
on.
Bch
stops.
E
I
feel
like
to
bch's
credit
and
an
abc
as
well
like
they've,
always
eventually
focused
on
these
technical
problems,
which
are
important
but
I'd
say
now,
like
you
know,
it's
been
going
on
for
years
and
the
results
aren't
good.
So
I
think
there
needs
to
be
a
new,
a
new
approach.
I'd
say,
market
focused
just
something
that
works,
allowing
people
to
sell
something
and
if
it
sucks
and
stuff
breaks
well,
then
those
problems
are
identified
and
can
be
fixed
right
because,
like
right
now
it's
oh.
E
We
made
this
hypothetical
thing
and
like
in
this
scenario,
if
people
liked
it
it
would
break
so
we
have
to
fix
it,
but
you
know
we
can
do
that
forever.
The
stuff
is
never
finished
so
getting
people
on
it,
especially
where
the
market
is
now
and
where
all
this
growth
is
coming,
like
there's
a
real
existential
risk
to
these
bitcoin
forks,
just
missing
the
boat,
because
people
don't
know
about
it,
people
aren't
trading
on
it.
People
think
ethereum's
trade-off
is
the
only
trade-off.
E
A
A
My
understanding
is,
there's
not
going
to
be
any
consensus
changes
in
may.
I
think
I
think
every
full
node
has
come
out
and
stated
that,
like
there's
things
they're
working
on
like
for
down
the
road,
but
for
this
may
upgrade,
I
my
understanding
from
talking
to
several
of
the
the
full
node
developers.
Is
that
there's
not
going
to
be
any
consensus
changes
in
may.
A
Yeah
general
protocols
needs
bigger
integers
for
their
any
hedge
product,
and
so
that's
probably
they've
said
that
my
understanding,
the
last
time
I
talked
to
those
guys
was
that
they
they
do
not
want
to
push
it
forward
in
may.
But
it's
it's
like
the
main
thing
they're
working
on
and
they
do
need.
They
do
need
to
make
this
change
at
some
point
for
their
for
their
business
model.
D
A
Slow
yeah.
Well,
there
there
are,
I
yeah
I've
heard
I
don't
know
how
seriously
to
take
some
of
these
other
projects,
like
I
know,
there's
mainnet,
dot
cash
and
I
think
the
dev
behind
that
is
named
pat
and
I
might
be
getting
this
wrong,
but
I
think
he's
the
one
who
told
me
that
he
was
working
on
a
whitelist
feature
for
nfts,
a
change
to
slp
db,
and
so
I
might
be
wrong
about
who
said
that.
A
That
you
know
from
so
from
all
the
devs
that
I've
talked
to
in
the
space
we
all
kind
of
feel
the
same,
whereas
like
yeah,
we
we
recognize
like
a
serious
issue
with
slpdb
tokens
and
we
all
want
minor,
validated
tokens
and
the
two
proposals
on
the
table.
Right
now
is
the
group
token
proposal
from
andrew
stone
or
the
the
cash
token
proposal
from
jason
drezner.
A
Both
of
those
proposals
are
incredibly
complex
and
that's
that's
the
rub.
That's
the
that's!
The
thing
that
I
think
is
preventing
them
from
moving
forward.
Is
that
they're
so
complex
that
there
just
isn't
really
a
lot
of
healthy
discussion
around
them,
because
it's
so
difficult
for
other
people
to
wrap
their
minds
around
the
idea,
and
so
there's
this.
You
know
abundance
of
caution
of
like
let's
not
introduce
bugs.
If
we
don't
fully
understand
and
can
debate
like
a
new
idea,
so
yeah
I
don't-
I
don't
know
it's
it.
A
It
seems
like
it's
at
a
stalemate
to
me.
I
I
wouldn't
be
surprised
if
those
two
token
solutions
are
shelved.
You
know
permanently
at
least
or
at
least
don't
come
out
for
another
year.
I
seriously
don't
see
them
being
implemented
in
the
next
year.
I
could
be
wrong,
but
it
would
be
nice
to
have
minor
tokens
minor,
validated
tokens.
D
Can
it
be
solved
on
the
lower
level
like
not
to
limit
so
much
on
the
api
level
but,
for
example,
to
have
a
better
hardware,
not
harder
like
bs
hd?
I
think
it
have
also
indexer
on
this.
The
new
file
fulcrum
version,
I
think
from
the
previous
week.
If
this
thing's
going
better,
will
be
still
the
the
rate
limiting
needed.
A
Yeah,
so
that's
actually
that's.
I
would
love
some
help
with
that.
I
think
bchd
is
possibly
the
the
solution
here.
The
pragmatic
solution,
if
not
the
ideal
one
in
that,
I
think
with
the
indexing
turned
on.
I
think
it
takes
between
400
and
500
gigabytes,
but
then
you've
got
the
full
node
you've
got
the
slp,
the
slp
indexing
built
into
it.
I
don't
think
it
suffers
from
the
same
issues
with
nft
tokens
as
slpdb
does
the
the
the
unknown
in
my
mind
there
is
scaling.
A
What
I've
seen
in
practice
is
that
bchd,
when
it
when
it
falls
over
which
it
does
fairly
often
it
corrupts
its
database
and
then
you
have
to
sync
from
scratch,
which
means
you
need
to
maintain
about
so
the
way
I-
and
this
is
not
uncommon
in
in
blockchain.
So
the
way
I
approach
this
is,
I
build
everything
around
a
docker
container
and
then
I
have
the
database
that
the
docker
container
mounts
and
that
way
when,
if,
when
the
database
gets
corrupted,
I
can
have
a
backup.
A
So
you
know
you're
still
talking
about
a
couple
hours
of
downtime
there,
because
you've
got
to
like
detect
the
issue
delete
the
old
database,
restore
the
database
from
like
a
300
gigabyte.
Zip
file,
then
mount
it,
and
then
you
can
get
back
into
operation.
Then
you
got
to
resync
from
whenever
you
took
the
the
snapshot,
so
it's
a
far
from
perfect
solution,
but
but
it
is
possible-
and
I
just
I
haven't
been
able
to
to
to
sort
of
give
vchd
with
the
slp
indexing
like
the
proper
focus.
A
I
would
like
to
the
one
feature,
even
if
bchd
doesn't
scale
the
one
feature
that
I
really
like
that
that
james
cramer
built
is
that
it
will
prevent
you
from
burning
tokens
like
it
will,
if
you
give
it
a
transaction
that
would
burn
a
token,
it
will
reject
your
transaction
and
not
broadcast
it.
You
have
to.
You,
have
to
deliberately
tell
it
like.
Yes,
I
understand
that
this
is
a
burning
transaction
and
I
want
you
to
deliberately
burn
these
it
won't.
A
It
essentially
will
check
your
work
and
won't
let
you
burn
a
token,
which
is
like
the
main
pain
point
in
slp
tokens
and
and
one
of
the
main
things
that
would
be
solved
by
minor,
validated
tokens.
So
so
there's
potential
there
it
just
it's
it's
it's
not
a
silver
bullet
by
any
means-
and
I
don't
know
yeah,
I
don't
there's,
there's
two
scaling
issues.
A
There's
there's
one
is
just
volume
of
requests,
and
I
know
bchd
has
issues
with
just
sheer
volume
of
requests
that
can
somewhat
be
solved
with
horizontal
scaling,
but
then
you've
every
time
you
have
a
replica
of
a
bchd.
You
have
you've
just
multiplied
the
amount
of
effort
you
have
to
do
to
like,
maintain
it
and
restore
these
databases
when
they
get
corrupted.
A
So
that's
the
first
scaling
issue.
The
second
scaling
issue
is,
as
slp
token,
transactions
increase
on
the
blockchain
and
the
number
of
tokens
overall
increase.
Slpdb
is
becoming
exponentially
more
expensive
to
run
as
a
result
of
that,
and
I
would
expect
that
same
pattern
to
apply
to
bchd
with
its
slp
indexer.
But
I
I
haven't
looked
into
it
enough
to
like
verify
that
if
it
doesn't
suffer
from
that
solution,
I
don't
I
don't
know
why.
I
don't
know
why
it
wouldn't
so
yeah.
It's
it's
a
it's
a
delicate
dance
man
yeah.
B
D
A
I
honestly,
like,
I
think
that
the
I'm
speculating
here-
don't
don't
hold
me
to
any
of
this,
but
I
think
that
the
there's
there's
a
number
of
problems
with
slp
tokens
beyond
just
whether
or
not
they're
validated
or
not.
I
think
that
tokens
will
slowly
atrophy
from
the
the
bitcoin
chains
in
favor
of
having
tokens
on
other
chains
like
avalanche
that
have
native
tokens
and
have
this
sort
of
solution
figured
out
and
they
have
like
a
cash-like
experience.
A
However,
avalanche
is
not
going
to
lower
their
transaction
fees,
which
I
think
are
about
a
penny
right
now
and
will
increase
as
the
price
of
avalanche
goes
up
and
they're,
not
interested
in
being
cash
they're
not
trying
to
be
cash.
They
want
those
transactions
to
be
high
so
that
because
the
avax
gets
burned,
it's
not
paid
as
a
transaction
fee
like
it
is
in
bitcoin
to
a
minor
and
they
want
that
they
want
to
burn
their
tokens.
A
So
that's
just
one
blockchain
there's,
you
know,
there's
ethereum,
there's
other
blockchains
that
have
tokens
and
also
this
token
idea
of
putting
information
in
the
op
return.
That
is
at
some
point
of
scale
like
you
know,
right
now,
we're
at
300
transactions
per
day
by
the
time
sometime
between
now
and
300
million
transactions
per
day.
We're
gonna
have
a
serious
problem
with
using
off
return
data
on
chain.
It's
gonna,
it's
gonna
adversely
affect
the
cash
use
case,
and
so
I
think
tokens
will
get
elevated
to
the
next
layer
up.
A
A
Could
you
could
pay
ecash
to
buy
a
token
on
avex,
and
then
you
could
sell
that
token
on
avex,
for
for
bitcoin
cash
and
and
so
the
the
negotiation
is
off
chain
and
the
settlement
is
on
chain
and
and
you
can
jump
between
chains,
and
so
I
think
that
this
is
from
an
engineering
standpoint.
This
is
where
it's
going
to
go
now.
D
D
A
A
B
D
D
I
I
wrote
in
fact
the
the
code
that's
generated,
the
nft,
which
is
behind
it
was
a
slp
faucet
which
was
generating
the
usual
sop
tokens,
and
I
just
make
a
small
modification,
so
it
can
generate
also
nfts,
but
it
was
not
interesting.
It
was
just
like
in
the
beginning
very
hard
to
see
something,
some
small
modifications
but
joya.
This
thing
he
found
some
generator,
which
is
like
ai,
which
is
like
parsing,
a
huge
amount
of
videos,
animes
getting
the
faces
from
there
and
like
teaching
it's
itself
so.
E
D
A
Yeah
yeah,
it's
interesting,
you
know
that's
and
that's
the
nice
thing
about
this.
Is
you
know
so
I
love
that
we've
got
that
level
of
organic
growth
and
it's
not
like
ethereum
nfp
tokens
don't
have
issues.
It's
not
such
a
big
deal
that
we
have
issues
on
the
bitcoin
cash
chain
and
the
abc
chain.
I
mean
right
now.
If
I
was
to
create
an
nft,
I
would
do
it
on
the
abc
chain,
just
because
the
volume's
there
I
wouldn't
have
these
scaling
issues
and
but
yeah.
A
A
But
yeah,
I'm
really.
I
mean
it
was
the
same
thing
with
the
spice
token,
when
slp
tokens
were
first
created
like
it
was
just
fun
and
people
just
used
the
crap
out
of
them
because
they
were
fun
and
these
waifu
nfts
are
similarly
fun
and
I
love
I
love
that
they
are
generating
these
deep
fakes
so
that
they
and
every
nft
is
actually
unique
and
and
but
they
also
can't
run
out
of
them.
They
can
produce
an
infinite
amount
amount
of
unique
cartoon
characters.
Yeah.
It's.
D
It's
cozy:
it's
interesting,
that's
starting
to
have
already
like
several
like
classes
of
nfts
and
most
of
the
wallets
started
to
to
try
to
support
this
like
different
classes
like
this,
for
example,
rifles
they're,
not
very
good
solution,
because
in
fact,
the
the
the
the
picture
there
is
not
on
the
ipfs
or
somewhere.
There
is
icons
on
the
this
c,
simple
ledger:
dot
e
for
server.
D
The
the
document
to
oreo
is
just
like
a
pointer
to
this
one,
so
it's
not
perfectly
blockchain
solution,
but
it's
very
popular,
so
the
people
start
the
wallets
like
zap
it
another
one.
They
start
supporting
this
type
of
class
of
nfts
and
I
think
the
the
recently
the
poker
added
to
the
this
signup.cash
added
also
support
for
the
media
on
ipfs.
A
A
A
So
we'll
probably
do
a
plug-in
and
probably
create
a
a
funding
proposal
for
for
you
to
do
this.
If
you're
interested,
which
I
think
you
are,
is
create
a
plug-in
for
wallet.fullstack.cache
that
would
they
would
utilize
these
new
api
calls
and
and
display
nfts
in
their
own
area,
and
so
since
we're
thinking
along
those
lines,
I
wanted
to
just
remind
you-
and
anybody
who
watches
this
video
and
joey
as
well,
that
the
permissionless
software
foundation
has
this
specifications
repo
and
the
only
spec
in
here
there's
four
specs
specifications.
A
The
only
one
that's
really
mature
in
here
is
the
first
one
for
media
sharing.
This
is
what
we
use
for
message.fullstack.cache
to
send
encrypted
email,
and
but
it
can
be
used
very
generically.
It's
also
how
uncensorablepublishing.com
syndicates
the
ipfs
websites
using
the
same
specification,
but
on
the
topic
of
the
the
waifus
and
attaching
the
artwork
to
an
nft.
A
So
there's
there's
obviously
the
ipfs
hash
and
that's
a
that's
a
much
better
way
to
do
it
than
than
a
centralized
server,
because
anybody
can
serve
that
content.
That
content
can
be
backed
up
in
filecoin.
That's
a
better
way
to
do
it,
but
it's
still
immutable.
You
still
can't
you
know,
change
the
data
once
you
create
the
coin
or
the
token,
and
so
this
mutable
data
specification.
A
Let
me
just
open
that
up,
because
I
need
a
refresher
as
well.
This
starts
to
scratch
the
surface
on
how?
Basically,
if
you
create
a
file
using
the
bitcoin
file,
protocol
you'll
get
this
transaction
hash
and
you
can
put
that
into
that.
That
document
hash
of
an
nft
token,
and
if
that
bitcoin
file
protocol
points
to
a
file
on
the
blockchain,
that
then
points
to
something
that
can
be
changed
now.
You've
created
a
way
for
a
wallet
to
download
and
read
mutable
data
for
an
immutable
token
and
and
so
anyways.
A
A
In
the
token
we
could
set
up
a
similar
thing
to
the
locat
id
where
a
wallet
could
on
the
fly.
Look
up
this
data
and
understand,
like
oh,
this
token
is
associated
with
this.
Other
protocol
like
waifus
or
concert
tickets,
or
you
know
whatever
arbitrary
app
this
token's
intended
to
work
with
the
wallet,
can
kind
of
like
figure
that
out
on
the
fly
by
by
following
this
breadcrumb
trail
of
data
and
so
anyways
I'd
I'd,
love,
I'd
love
help
with
these.
A
D
D
D
Yeah,
I
just
put
everything
inside
this
200
bytes
or
something
that
was-
and
it
was
just
like
a
simple
letter
to
start
to
show
is
this
the
internal
on
external
link?
If
you
start
with
t,
it
will
be
transaction
id
after
this.
If
you
start
with
q,
it
will
be
ipfs
hash
and
you
just
can
put
inside
this
memo
several
pointers
to
outside
hot
c,
not
blockchain
or
blockchain
data
like
this
mutable
data.
D
A
A
Yeah
yeah.
That
way
it
would
I
mean
I
think
this
is
how
we
scale
a
lot
of
these
ideas.
I
think
this
is
something
that
we
can
do
on
the
bitcoin
cash
blockchain
and
abc
blockchain,
that
it's
not
that
you
can't
do
it
on
ethereum.
It's
just
that.
This
is
how
we
get
like
ethereum
like
qualities
in
terms
of
the
user
experience
and
being
able,
like
I
mean
the
perennial
issue
is
that
the
stems
from
is
being
able
to
change
the
token
icon
after
the
fact.
A
So
you
know
you
get
a
company
like
usdh
and
they
go
through
a
rebranding
or
tether.
You
know
they
already
have
all
these
tokens.
You
know
circulating
in
the
economy
and
it's
on
an
immutable
blockchain,
so
you
think
it
would
be
impossible,
but
if
they
follow
these
specifications
you
can
actually
update
the
token
icon
that
displays
in
the
wallet
anytime.
You
feel
like
it
without
actually
impacting.
You
know
the
tokens
themselves.
A
And-
and
I
loved
your
idea
in
the
hackathon
using
nfts
as
a
decentralized
dns
system,
and
so
like
that's
a
perfect
example
of
that
that
slp
json
id
specification
where,
if
someone,
if
a
wallet
you
know
got
one
of
these,
it
could
tell
that
it's
an
nft,
obviously,
but
but
with
this
system
it
could
actually
be
like.
Oh,
this
is
a
this
is
a
dns.
A
A
D
A
D
A
D
A
D
A
Okay,
guys:
well,
that's
a
good
place
to
wrap
this
up
thanks
for
joining
the
meeting.
We'll
do
the
technical
steering
committee
again
in
two
weeks
and
same
time
next
week
will
be
the
com-com
meeting
where
we'll
be
talking
about
the
second
voting
token,
for
the
second
proposal
and
yeah
right
on
thanks
chris
I'm
good.