►
From YouTube: PSF TC Meeting 6.23.21
Description
Technical Steering Committee Meeting for June 23, 2021
B
A
Ahead,
guys
yeah
right
on
welcome
everybody
to
the
technical
steering
committee
meeting
for
the
permissionless
software
foundation.
Today
is
june
23rd
and
yeah
aaron.
I
can
confirm.
I
see
us
live
on
youtube,
so
that's
great
all
right!
My
name
is
chris
troutner.
I
helped
found
the
permissional
software
foundation
and
I
maintain
fullstack.cash
blockchain
as
a
service.
Let's
go
ahead
and
go
around.
Do
a
do.
A
quick
introduction!
A
B
A
A
Nice
thanks
aaron.
So
as
always,
the
agenda
can
be
found
on
github
under
the
permissionless
software
foundation,
github
group,
under
the
the
tsc
for
technical
steering
committee
repository,
and
then
we
file
the
agendas
as
as
issues,
and
so
this
is
issue
number
11
for
june
23rd,
and
these
are
links
to
the
the
well
here's,
the
youtube,
recording
and
we'll
also
try
and
get
an
odyssey
link,
but
for
those
who
are
watching
this
later
or
want
to
send
a
link
to
someone
later
we'll
update
these
with
with
the
links
yeah.
A
So
here's
the
agenda
today
we're
gonna
go
over
the
updates
to
the
psf
core
software
and
if
for
people
who
are
unfamiliar
with
what
I
mean
by
core
there's
a
link
here
to
a
blog
post
that
talks
about
that.
Then
we'll
cover
some
of
the
other
areas
of
research,
the
json
rpc
over
ipfs
and
pay-to-write
database
and
then
and
then
just
sort
of
miscellaneous
stuff.
A
So
I'll
go
through
a
lot
of
these
agenda
items
fairly
quickly.
Aaron
and
stoian
feel
free
to
interrupt
me
if
you
have
questions
or
want
more
details
on
something
all
right.
The
the
psf
core
software
is
mostly
concerned
with
the
bch
api
rest
api,
which
is
the
service
that
full
stack,
dot
cash
offers
and
then
the
bchjs
javascript
library,
which
complements
those
services
and
then
the
gatsby
ipfs
web
wallet,
which
is
the
front-end
gatsby
theme
that
powers
wallet.fullstack.cat.
A
These
are
all
open
source
projects
that
can
be
forked
and
used.
We
offer
a
paid
service,
but
by
no
means
do
you
have
to
pay
to
use
them.
We
have
free
tiers
and
paid
tiers
and
everyone's
free
to
run
their
own
software,
and
we've
been
experiencing
some.
Some
pretty
steady
growth
with
fullstack.cache
developers
really
appreciate
the
ability
to
just
read
one
page
of
documentation
and
maybe
some
example
code
and
hit
the
ground
running.
A
That's
what
we're
all
about
our
api
requests
last
week
exceeded
600
000
requests
per
day
and
so
being
able
to
scale
and
stay
ahead
of
the
growth
curve
is,
is
something
I'm
heavily
focused
on
right
now
and
daniel
who,
who
couldn't
be
here
today?
One
of
our
most
active
members
he's
been
working
on
some
of
the
scaling
tech.
So
I'm
actually
going
to
jump
to
this
last
item.
A
B
A
Okay,
can
you
hear
me
now?
I
gotta
mute
myself
most
people
who
interact
with
the
rest
api
directly,
which
is
mostly
just
people
who
don't
use
javascript.
They
will
need
to
explicitly
update
the
v5
route,
but
I
think
the
the
vast
majority
of
users
are
using
bchjs
and
so
there's
nothing
required
there.
You
just
simply
update
a
new
version
of
bchjs
in
your.
A
You
know
it
probably
not,
but
let's
go
ahead
and
show
that
for
people
who
want
to
be
a
little
proactive,
a
lot
of
these
web
wallets.
So
if
you're
talking
about
geodrop.cache,
if
you
don't,
if
you
don't
already
have
a
wallet,
you
won't
need
to
worry
about
this
when
you
create
a
new
wallet,
it'll
automatically
update
to
the
v5
route.
A
Just
like
you
see
here
so
I'm
in
wallet.fullstack.cache,
I'm
in
the
configuration
tab
and
then
right
here
is
where
it's
calling
the
v5
route,
and
that
will
happen
automatically
if
you're
creating
a
new
wallet.
This
will
all
happen
automatically.
If
you
have
an
existing
wallet,
you
may
need
to
go
in
there
and
manually
update
it,
but
we're
not
going
to
sunset
the
v4
route
for
a
while.
We
don't
even
have
a
date
set
yet
so
there's
nothing
immediate
that
anybody
needs
to
do
in
terms
of
updating
this.
A
B
Mostly
just
nice
for
them
to
see
it,
and
when
I
did
it
to
my
web
wallet,
I
had
to
click
on
the
plus
button,
which
looks
like
you
got
a
little
bit
new
styling
on
that
that
looks
nice.
The
I
had
to
click
on
the
plus
button
and
manually
enter
it
so
for
anybody
that
is
going
to
do
that.
It's
not
just
going
to
come
down
the
pop-up
menu.
If
it's
an
older
wallet,
so
you
just
are
going
to
have
to
click
plus
and
manually,
enter
it
yeah.
B
A
A
So
that's
the
v5
routes
worth
mentioning.
It's
it's
more
of
a
a
victory
for
us
because,
because
we
are
now
prepared
to
scale
you
know
bring
on
the
traffic
like.
If,
if
we
10xed
our
traffic
in
the
next
few
weeks,
we
could
easily
spin
up
the
infrastructure
to
handle
that
the
other
really
big
thing
is
the
double
spend
proofs.
This
is
a
new
feature
that
came
out
in
the
bch
n,
full
node,
and
it's
also
in
a
couple
other
full
nodes.
A
A
I
hesitate
to
call
it
secure,
zero
conf,
but
it's
getting
us
in
moving
us
in
the
right
direction.
So
the
idea
here
is
that
the
what
I
would
consider
the
canonical
use
case
is
a
merchant
would
receive
a
transaction.
You
know
they
sell
something
and
that
somebody
pays
them.
They
receive
notification
of
a
transaction
and
then
their
wallet
software
would
wait
three
to
five
seconds
after
receiving
the
notification
and
then
query
the
that
transaction
id
that
they
get.
They
would
query
to
see
if
that
generated
the
double
spend
proof.
A
By
calling
this
new,
this
new
endpoint
that's
available
in
bchjs
and
bch
api.
If
it
returns
nothing
like
no
data
comes
back,
then
the
transaction
is
safe
to
to.
Basically
you
can
you
can,
then
you
know
safely
give
the
customer
their
product
or
deliver
the
product
that
this
doesn't
have
to
be
a
physical
product.
This
is
more
than
likely
a
digital
product
or
service,
and
you
don't
have
to
wait
for
one
confirmation
you
can
be.
A
You
can
be
about
98.99,
confident
that
that
that's
not
a
double
spend
and
the
transaction
is
going
to
be
included
in
a
block.
However,
if
it
does
return
data,
that
means
that
the
the
transaction
triggered
a
double
spend
proof.
So
it's
it's.
Essentially,
it's
this
proof
that
it
is
a
double
spend
and
then,
as
a
merchant,
you
can
decide
what
to
do
at
that
point
and
like,
like
probably
not
give
them
the
product
or
service,
and
so
there
are
corner
cases
where
this
is
a
little
sketchy
to
use.
A
A
B
A
Just
awesome
yeah,
so
I'm
excited
for
people
to
play
with
it
at
this
point
like
consider
it
wrapped
with
caution.
Tape
like
it's
fully,
it's
fully
functional,
but
it's
it's
sort
of
unknown.
What
all
the
what
all
the
different
corner
cases
are
where
this
could
be
exploited.
So
so
this
is
officially
like
a
sandbox
for
developers
to
play
with
for
entrepreneurs
to
explore
explore
if
this.
If
this
adds
value
to
your
use
case,
you
should
definitely
you
know,
check
it
out.
A
You
buy
tok,
psf
tokens
or
or
sell
psf
tokens
simply
because
the
risk
is
too
high
because
that's
an
automated
app
and
if
someone
found
a
way
to
exploit
this
it
would
you
know
they
could
do
it
and
it
would
take
us
a
while
to
like
detect
that
and
and
so
the
risk
there
is
just
too
high
for
for
my
for
my
taste.
So
that's
an
example
of,
like
maybe
a
scenario
where
you
would
use
it
in
a
scenario
where
you
would
not
use
it.
A
A
Let's
clarify
a
lot
a
lot
of
ignorance
around
this.
Still,
I'm
still
trying
to
wrap
my
head
around
it
all,
and
then
the
last
thing
to
mention
in
terms
of
the
core
software
here
is
that
daniel
updated,
a
gatsby,
ipfs
web
wallet,
gatsby
released
a
major
version
three
and
it
just
a
lot
of
the
dependencies
needed
to
be
sort
of
massaged
to
get
it
to
work.
So
that's!
That's!
Pretty
cool,
it's
always
great
to
keep
our
core
software
up
to
date.
A
So
that
concludes
the
core
software.
We'll
move
on
to
you
know
just
sort
of
the
different
areas
of
research
that
members
are
doing.
I'm
I'm
personally
pretty
excited
about
this
jason
rpc
over
ipfs
and
the
the
pay
to
write
database
and
I've
been
focused
a
lot.
The
last
couple
weeks
on
the
pay
to
write
database
and
for
people
who
are
trying
to
like
understand
what
the
pay
to
write
database
is.
A
What
is
these
cases,
what
problems
it
solves,
just
the
high
level
understanding.
I
created
a
video,
that's
linked
here
and
I
it's
12
minutes.
I
really
encourage
people
to
watch
it
just
so
that
they
can
understand
what
is
this
pay
to
write
database?
What
makes
it
valuable?
Why?
Why
am
I
so
passionate
about
it
and
been
making
steady
progress
in
in
sort
of
the
research
I'm
starting
to
get
out
of
the
r
d
phase
and
more
into
the
the
product
development
phase?
So
it's
I've
basically
proven
out
the
technology.
A
I
know
it
works,
but
now
I
need
to
write
tests
and
I
need
to
refine
the
code
and
I
spent
the
last
few
days
learning
the
clean
architecture
pattern,
design
pattern
that
I'm
going
to
apply
to
this
and
which
helps
manage
complexity
over
time
and
so
anyways.
That's
going
on.
I
encourage
people
to
check
it
out.
I
don't
really
need
to
spend
much
more
time
on
on
that.
A
It's
there
for
anybody,
who's,
interested
and
and
if
anybody
else
gets
interested
in
it
and
has
questions
please
reach
out
to
me,
because
this
is
something
I'm
very
passionate
about.
I'm
working
hard
on
and
I'd
love
to
collaborate
with
other
people
on
right
on
so
moving
down
to
the
sort
of
just
miscellaneous
projects
got
a
couple
bunch
of
call
outs,
mostly
for
daniel
and
gary
here.
A
Gary
nadir
has
been
our
lead
developer
on
the
token
bridge
between
avalanche
and
the
bitcoin
cash
blockchains,
and
he
forked
the
slp
clie
wallet,
which
is
a
command
line,
hd
wallet
for
bitcoin
cash
we've.
He
forked
that
and
created
the
avex
by
wallet.
So
it's
same
exact
user
experience,
but
on
the
avalanche
blockchain
and
he
updated
the
burn
command
so
that
now
you
can
burn
avalanche
tokens
just
like
you
can
burn
slp
tokens
on
the
bitcoin
cash
side
and
he
also
added
this
right
here.
A
He
also
added
a
send
all
command,
which
is
really
nice,
being
able
to
send
all
the
avalanche
in
your
wallet
to
another
address
like
if
you
want
to
just
get
rid
of
that
wallet
and
but
but
what's
really
exciting,
is
he
added
this
slp
albux
bridge
command?
So
if
you
have
a
token
on
the
avalanche
blockchain,
you
can
send
it
across
the
well.
Actually
you
have
to
have
a
specific
test
token.
It
won't
work
for
any
generic
token,
but
we
have
a
faucet
where
you
can
get
these
test
tokens.
A
If
you
want
to
play
with
this,
but
then,
if
you
have
that
token
in
your
wallet,
you
can
issue
this
command
and
it'll
send
the
token
across
the
bridge
over
to
the
bitcoin
cash
blockchain
and
and
you'll
you'll,
see
the
the
token
appear
in
whatever
address
on
the
bitcoin
cash
side,
that
you
specify
and
he's
working
on
a
similar
command
for
slp
client
wallet
to
send
the
token
the
other
direction
so
yeah.
So
there's
just
so.
A
lot
of
people
are
interested
in
this
token
bridge.
C
A
Yeah
it
connects
to
the
main
net
and
it
it's
using
their
ava
labs
provides
a
public
node.
I
think
it's
probably
a
load
balanced.
You
know
several
nodes,
but
they
have
like
a
public
sort
of
like
how
bitcoin.com
used
to
have
rest.bitcoin.com
or
how
we
have.
You
know
a
free
tier
for
for
stack
dot
cash.
It's
a
similar
thing.
They
have
direct
access
to
a
node
that
you
can
interact
with.
So
that's
that's.
What
avex
clyde
wallet
uses
it'll
just
automatically
connect
that
free
public
node.
C
A
A
good
question:
it's
using
the
x
chain
so
for
people
who
aren't
familiar
with
avalanche,
there's
three
primary
chains:
the
p
chain,
which
is
for
platforms,
the
c
chain,
which
is
for
smart
contracts
and
the
x
chain,
which
is
more
like
bitcoin
with
transactions
and
there's
the
c
chain
which
is
an
evm
compatible,
has
erc20
tokens.
And
then
the
x
chain
has
tokens
that
are
similar
to
like
slp
tokens.
The
x
chain
operates
very
similar
to
bitcoin
cash,
so
yeah.
A
A
So
when
you
combine
all
these
bridges,
it
should
be
possible
to
take
an
erc20
token
on
ethereum,
move
it
across
to
the
bridge
to
avalanche
c
chain,
convert
that
to
a
token
on
the
x
chain
and
then
send
it
across
the
bridge
to
bitcoin
cash
as
an
slp
token
and
all
the
way
back
again,
I'm
really
looking
forward
to
the
day
when
I
can.
I
can
do
that
like
just
to
prove
it
out.
Conceptually
that'll
be
really
cool.
A
That's
the
bug
that
daniel's
just
fixed
is
now
now
the
server
will
detect.
You
know,
file
names
that
it
can't
parse
and
it'll.
Tell
you
that.
That's
the
problem
that
was
that
that
was
part
of
the
problem
is
it's
clearly
having
a
bug,
but
we
didn't
know
what
was
causing
it.
We
didn't
know
how
to
fix
it.
So
now
now
it
presents
a
clear
text
message
or
clear.
One
error
message
to
the
user,
saying
you
know
your
your
file
name.
I
can't
I
can't
read
your
file
name.
A
So
just
a
little
more
user
user
help
there
and
one
of
the
things
that
I
think
daniel's
going
to
be
working
on
in
this
upcoming
quarter
is
email
notifications.
So
we
have
this
ability
to
send
end
an
encrypted
email
to
a
bitcoin
cash
address.
But
then,
if
you
receive
an
email,
you
don't
know
you
don't
get
any
notification
until
you
like
log
in
to
message.fullstack.cache
and
check
your
inbox,
and
so
what
we
want
to
do
is
add
a
feature
where
you
can.
A
C
A
A
A
A
Finally,
just
to
wrap
up
a
few
things,
the
yeah
at
full
stack
dot
cash
about
halfway
down
the
page.
There's
a
section:
that's
titled!
What
type
of
developer
are
you
and
there
that
leads
to
three
other
pages
for,
like
front-end
developers,
back-end
developers
and
library
developers,
there's
been
a
ton
of
content
added
to
those
three
pages,
so
I
really
want
to
encourage
people
to
go
there
and
check
them
out.
Give
us
feedback.
Basically,
a
lot
of
people
come
into
the
space
as
a
front-end
developer.
A
A
You
know
that
back-end
pages
is
designed
to
help
you
get
oriented
oriented
as
quickly
as
possible
or,
if
you
want
to
you,
know,
build
build
a
library
that
sort
of
just
sort
of
supercharge
your
app
or
do
some
very
specific
thing
like
send
an
encrypted
message
or
you
know,
do
pass
some
sort
of
media
over
the
blockchain.
That's
what
the
library
sections
for
it's
like.
Here's,
how
you
you
know
build
craft.
A
Your
own
little
lego
blocks
that
that
interact
with
the
blockchains
and
is
is
compatible
with
our
front
end
and
back-end
software
and
then
finally,
geodrop.cache,
which
is
our
example
of
a
of
a
game
that
you
can
that
you
can
build
with
our
wallet
tools.
Is
that's
fully
functional.
Now
that's
been
fixed,
so
if
people
want
to
sort
of
check
it
out,
it's
a
it's,
a
map-based,
scavenger
hunt
game
and
it's
it's
it's
it's
really.
A
It's
an
example
of
what
you
can
build
with
with
some
of
our
front-end
software,
and
I've
had
multiple
entrepreneurs
approach
me
with
with
ideas
that
are
very
similar
to
the
game,
like
they're,
not
the
game
that
we
built,
but
it
uses
all
the
tech
that
goes
into
the
game.
So
that's,
that's
really.
The
point
is
it's
it's
a
demonstration
of
what
you
could
build
with
with
you
know,
just
some
very
common
lego
blocks
of
software.
A
F
B
B
A
C
C
C
C
Bcp,
like
payloads,
which
are
on
on
chain,
so
I
extended
this
library
so
now
the
usual
code
is
like
you
just
create
a
config
with
this
is
the
mostly
required
fields
of
the
name
of
your
group.
No,
this
is
the
children
token.
So
this
is
the
group
id
the
name
of
your
child
token
and
the
ticker
and
just
pass
this
to
the
create
nft
child
call.
C
So,
but
basically
you
just
add
this
section
payload
to
to
the
config,
which
will
contain
the
the
type
of
your
payload.
It
can
be
video
audio,
something
like
this
one
and
it
will
be
the
world
where
your
payload
is
stored,
in
this
case
it's
on
ipfs,
okay
and
you're
using
same
code,
so
nothing
changing
just
adding
these
payloads
section
and
you
will
have
the
new
type
of
nfts
with
bcp
attached.
A
C
Because
yeah,
it's
very
unexploited
territory.
I
made
a
lot
of
experiments
not
of
them
successful
so
so
yeah.
The
question
is
like
like
for
the
users,
it's
very
easy
just
add
this
to
the
json
over,
but
for
the
the
the
blockchain
like
saving,
it's
like
very
fuzzy
territory,
because
this
is
trying
to
use,
multiply
op
returns,
but
it's
mostly
in
the
moment
just
talk.
C
C
C
Transaction
builder
like,
for
example,
if
it's
usual
sop
token,
on
the
output
zero,
you
just
put
this
script,
which
you
create
with
generate
nft,
something
something,
and
you
just
put
like
some
dust
there
right
and
you're
ready
with
the
sop,
but
I
was
experimenting
so
okay,
this
second
one.
Where
should
I
put
it
this
guy?
Like?
Should
I
put
it
here
after
this
guy
and
have
the
two,
this
transaction,
or
have
one
this
transaction
with
amount
of
two
dusts?
C
A
B
A
B
A
Okay,
yeah,
I
mean
I
don't
know
if
we
need
to
do
the
recording,
but
I
I
definitely
want
to
keep
this
conversation
going
and
I
will
put
a
new
zoom
link
in
the
in
the
in
the
telegram
channel
but
yeah
stewie.
So
I
just
want
to
clarify
you're
you're,
creating
a
second
op
return
in
the
transaction.
So
your
second
op
return,
output
and
you're
putting
this
data
in
in
that
op
return.
Yes,
can
you
create
the
token
yes.
B
All
right
for
those
who
are
on
youtube,
we
are
just
waiting
having
some
complications
with
zoom.
We
are
going
to
get
back
on
in
just
a
second.
I
hope
you've
enjoyed
what
we're
talking
about
so
far,
a
lot
of
really
really
cool
stuff
that
we're
doing
some
of
the
cool
stuff
that
stoyan's
doing
getting
nfts
working.
Let's
see
here,
we
got
a
new
zoom
meeting,
I'm
opening
it
up
and
we're
gonna
get
it
piped
over
all
right.
B
So
I'm
just
waiting
for
chris
to
let
me
in
and
once
he
does.
Let
me
in
we're
gonna
get
back
all
right.
I
got
chris
you
like
my
new
setup.
Yeah,
the
tvs
are
pretty
cool
yeah.
I
thought
it'd
be
fun,
so
we
gotta
wait
for
the
other
guys
and
then
we'll
get
them
in
here.
So
let
me
go
ahead
and
adjust
you
all
right.
Chris.
B
B
So
I
know
that
a
lot
of
people
out
there
are
concerned
or
have
concerns
with
here.
There's
your
face
all
right.
I
know
that
a
lot
of
people
have
concerns
with
the
amount
of
information
being
written
to
a
blockchain,
and
that's
part
of
the
reason
that
we're
talking
about
the
pay
to
write
database
right
is
trying
to
solve.
This
problem
is
riding
to
a
second
op
return.
Gonna
be
a
conflict
there.
A
Well,
you
know
this.
This
gets
back
to
the
age-old
idea
of
spam
on
the
blockchain.
What
is
spam
and
if
you
pay
for
it,
is
it
really
spam?
That's
really
the
the
paradox
there,
and
so
the
rules,
let
you
put
in
another
op
return
and
you
gotta
pay
for
it.
When
you
make
the
transaction
so
you're
playing.
B
B
A
B
Well,
yeah
I
mean
we've
always
had
these
arguments
of
the
block.
Size
was
a
huge
argument
and
you
know
now:
I'm
buying
an
eight
terabyte
drive
for
like
120
bucks,
and
you
know
I've
got
a
a
two
terabyte
nvme
m2
drive.
That's
cost
me,
you
know
300
bucks
and
has
a
read,
write,
speed
of
like
4
000
megabits
per
second
like
crazy,
and
that's
only
getting
better
the
in
the
360
field.
I've
candel
just
released
a
12k
camera
and
they
got
a
specialized.
A
Wow
yeah
yeah,
you
know
the
the
the
issue
with
spam
on
the
blockchain.
This
is
this
is
where
the
the
argument
starts
to
get
confused.
Is
it's
not
so
much
about
how
much
space
it's
the
blockchain's?
Taking
up
it's
it's?
How
much
do
you
have
to
pay
to
run
a
node
in
the
cloud
because,
like
the
thing
is,
is
like
all
these
apps
that
that
deal
with
nfts,
all
the
all
the
things
real
users
want
to
use.
A
They
require
cloud
infrastructure.
They
they
can't.
You
know
if
you're
running
a
full
node
on
a
raspberry
pi
in
a
shed
on
your
property.
That's
great,
but
you
can't
run
a
production.
You
know
application
with
that
as
your
back
end,
and
so
you
you
don't
get
to
leverage
these
really
cheap
hard
drive
prices,
really
what
what
makes
this
either
prohibitive
or
not
to
operate.
A
You
know
an
app
that
has
a
good
user
experience
is
what
is
the
cost
of
running
a
full
node
in
the
cloud
and
and
so
basically,
what
you're
doing
is
you're
it
like
the
the
bitcoin
cash
blockchain's
around
200
gigabytes
right
now,
and
so
whether
you're
getting
value
out
of
the
data?
That's
in
that
200
gigabytes
or
not.
You
still
have
to
pay
to
host
that
in
the
cloud,
and
so
it's
this
cloud
hosting
cost,
because
you
you
need
it
to
be.
A
You
know
not
just
performant,
but
you
know
like
basically
available
to
the
cloud,
so
it
doesn't
matter
how
how
cheap
a
hard
drive
is
that
you
can
get.
You
know
it
for
your
home
use
that
doesn't
affect
that.
That's
that's!
Why
that's
one
thing
that
people
people
say
like
oh,
the
size
of
blockchain
doesn't
matter
because
hard
drive
space
is
so
cheap
and
that's
missing
the
point.
The
point
is
like
this
has
to
run
in
the
cloud
and
that's
the
cost
that
matters
not
not
how
cheap
you
can
buy
a
hard
drive
of
amazon.
B
C
B
A
A
C
A
C
Yes,
so
so,
with
this
experiment
like
some
of
them
created
tokens
that
looks
good,
but
not
so
good,
like
you
can
see
here
that
balance
is
zero,
so
not
very
successful
the
good
one,
the
the
current
one,
that
I
told
you
with
the
two
scripts
script,
following
immediately
of
the
dust
output,
it's
creating
pretty
nice,
not
this
one.
I
need
to
maybe
click
on
this
one.
C
C
So
information
is
there
on
the
blockchain,
but
it's
still
very,
let's
see
this
explorer.
For
example,
it's
choosing
to
show
the
second
top
return
here,
which
is
the
bcp,
not
the
sop
one,
and
that's
why
I
think
it's
mistaking
also
here
it
does
not
get
it
that
it's
sop,
so
maybe,
if
I,
but
no
I'm
not
sure
if
I
switch
the
output,
would
it
show
properly.
A
C
So
it's
just
displaying
problem.
Not
these
tokens
are
validated
so
they're
valid
bsop
sop,
but
one
more
problem,
for
example,
is
if
I
send
this
token
to
somebody
like.
Oh,
I
already
have
it
in
my
wallet
here,
but
if
I
send
this
guy
to
somebody,
the
second
op
return
will
be
lost,
because
the
sent
does
not
understand
the
day's
second
op
return,
but
it
will
still
so
every
time
when
you
send
such
kind
of
tokens
and
you
decide
to
display
it.
A
Right,
but
that
actually
fits
in
really
nicely
with
the
way
so
like
when
you
call
the
hydrate
utxo
call,
for
instance,
it
has
to
go
get
the
genesis
data,
because
that's
the
data
that
has
the
ticker
name
and
the
most
importantly,
the
decimals,
so
you
can
figure
out
like
what
the
decimal
precision
of
this
token
is.
That's
in
the
genesis
data
like
that,
you
can't
you,
don't
you
don't
you
don't
know
what
the
decimal
position
is
just
by
looking
at
the
transaction
of
a
token
of
ascend
of
a
send
transaction.
A
C
A
Yeah
yeah,
you
know
so
this
is.
I
think
this
would
be
a
really
good
complement
to
that
mutable
data
specification,
because
that
specification
was
created.
You
know
before
multiple
opera
terms
were
allowed,
and
so
the
idea
was
you
basically
do
a
bunch.
You
take
the
same
information
and
you
capture
it
by
creating
a
transaction
and
putting
that
transaction
in
the
document
hash.
A
But
but
you
sort
of
like
what
you're
doing
here,
I
think
is
much
simpler,
certainly
a
much
simpler
implementation
and
it
would
be
much
simpler
for
a
wallet
to
retrieve
the
data
this
way
and
it
would
reduce
the
number
of
api
calls.
So
that's
really
good
and
so
yeah
I
really
like,
but
but
it's
also
specific
to
being
able
to
have
multiple
op
returns.
A
So,
for
example,
any
protocol
built
around
this
would
not
work
on
on
the
ecash
blockchain,
whereas
if
we
stuck
to
the
spec
that
that
is
on
the
document,
hash
that
would
work
on
both
blockchains.
So
I
I
think
we
should
do
both.
I
think
you
know
if
we,
if
we
had
it
this
way
as
like
an
as
an
optional,
you
know
what
you
did
here.
Having
a
second
op
return
in
the
genesis
transaction,
we
can
make
that
like
an
optional
implementation
or
bitcoin
cash,
specific
implementation
and.
C
C
A
I
like
them
both
I
mean
yeah,
it's
just
a
trade-off
like
like.
I
honestly,
I
think
the
way
that
you
did
it
here
is
more
efficient.
You
know
it
would
reduce
the
number
of
api
calls.
It
would
be
much
easier
to
write
software
to
look
up
the
data
this
way
and
yeah.
So
this
is
this.
Is
this
is
really
interesting.
I
I
hadn't
this
is.
This
is
a
good
test
too,
because,
as
far
as
I
know,
no
one
has
tested
a
genesis
transaction
with
multiple
operators.
A
C
A
C
F
C
Functions
and-
and
the
problem
here
was
that,
like
we
know,
this
wallet
is
multi
addresses.
If
you
remember,
we
thought
about
this,
it's
pretty
much.
You
can
get
many
many
addresses
with
this
get
address,
so
I
decided
the
first
to
work
with
it
like
a
single
wallet,
adding
index
index
parameter
to
every
one
of
these
cause,
to
show
it
exactly
in
which
wallet
of
my
stuff.
F
C
C
C
So
you
can
see
the
list
of
the
tokens
they're
visible
here,
in
fact,
because
this
wallet
have
this
by
default.
So
you
can
see
there's
some
stuff,
but
you
can
use.
Also
this
list
token
and
again
there
is
the
several
parameters
oops
like
minus.
What
was
tokens
help
so
you
can
list
only
the
groups
if
you
want
because
like
if
you
show
this
inside,
for
example,
the
the
full
stack
quality
you
need.
C
First,
maybe
only
the
groups
and
when
you
click
on
some
group
you
will
see
them
all
and
the
second
important
was
this
index
because,
like
you
see
here,
are
two
wallets,
so
I
will
just
use
index
one
to
to
show
what
is
inside
this
thing,
because
only
these
tokens,
so
the
name
was
nft
and
the
index
is
one
and
we
can
see
there.
There's
this
bcp
child
guy
nice,
which
I
created
here
so
the
other
yeah,
pretty
obvious.
You
can
create
stuff
yeah.
C
A
C
A
So
I
don't
know
if
it's
in
the
main
line
or
if
it
was
one
of
the
sort
of
prototypes
I
built
to
explore
something,
but
I
think
that
there's
like
a
if
you
do
help,
I
think
I
saw
there's
like
a
sign.
There's
a
sign
message,
call
and
yeah.
There's
a
signed
message
call,
and
there
was
something
I
was
doing.
It
might
be
the
get
key.
A
You
know,
you're,
not
messing
you're,
not
signing
a
message
with
a
random
address
in
the
hd
wallet.
You
basically
tell
it
like
this.
This
is
the
address
that
I
want
to
sign
messages
with,
and
so
you
could
do
that
same
thing
with
these
nfts,
where
you
could
be
like
this.
This
is
my
nft
address
and
I'm
going
to
put
some
money,
I'm
going
to
put
some
bitcoin
cash
in
that
address
to
pay
for
transaction
fees,
and
you
know
that
all
my
nft
work
is
just
going
to
use
this
one
address.
C
A
C
Don't
know
how
to
do
this
to
have
like
some
way
to
enable
dangerous
commands
on
the
sop
wallet.
Like
usual
people
just
start
hitting
this.
Thus
these
commands,
but
if
you
add
something
something,
it
will
also
allow
other
commands
like
this
one
experimental
like
an
advanced
mode
or
yeah
or
experimental.
C
C
A
C
B
B
A
F
B
F
C
B
B
And
really
really
cool
to
see
the
multi-op
return
thing
and
yeah
chris
you're
right.
It's
probably
a
bitcoin
cash
thing,
since
bitcoin
cash
has
the
multi-op
return.
Who
knows
if
ecash
is
going
to
want
to
use
that
or
not,
but
the
mutable
protocol
could
probably
work
on
the
e-cash
thing
as
well.
So
those
of
you
that
are
watching,
oh,
we
got
a
colby
replied
will
do
and
michael
afe
aphidus
affidavis.
B
I'm
sorry,
I'm
butching
your
last
name.
Man
love
the
tools
you
guys
are
working
on,
can't
wait
to
play
with
the
cly
wallet
and
aaron.
That's
a
nice
name:
buddy
garen,
sir!
It's
like
old,
school
mtv,
look
with
the
tvs.
All
right.
People
are
liking.
It.
We
just
gained
two
new
viewers.
So
obviously
the
tvs
are
working
for
us.
A
B
Yeah
so
go
to
psfoundation.cache.
You
can
check
out
the
telegram
and
yeah
join
and
talk
to
us.
We,
we
really
want
to
hear
from
you
so
all
right,
cool,
yeah,
very,
very,
very
cool
stuff
fun
to
play
with
the
clyde
wall.
I
haven't
got
to
do
that.
Lately.
I've
been
diving
into
mocha
pro
and
some
editing
software
for
other
stuff,
but
I
want
to
get
back
on
that
and
once
you
have
that
code
up
story
and
I
I
definitely
want
to
check
it
out
because
that's
that's
really
cool
so.
A
Let
us
sort
of
collaborate.
You
know
on
some
of
these
ideas
around
nfts
and
and
different
media
formats
and
immutable
data
specification,
and
and
once
we
get
it
kind
of
hashed
out
on
the
command
line,
then
we
can
worry
about.
You
know
creating
a
plug-in
for
wallet.fullstack.cache
to
actually
display
this
stuff.
You
know
for
normal
people.
D
B
B
So
go
through
that
read
that
and
download
the
clywallet.
The
slp
client
wallet
create
a
token
from
the
command
line
and
send
it
to
us
and
I'll
go
ahead
and
I'll
drop
in
an
slp
address
unless
chris,
if
you
want
to
put
yours
I'll,
just
put
one
of
mine
I'll
go
ahead
and
put
yours,
and
I
don't
have
one
handy
and
I
will
drop
this
into
the
chat
for
anybody
as
well
and
telegram.
Oh
geez,
that's
long
and
it's
hidden
by
part
of
the
tv,
that's
yeah.
B
B
B
Tag
me
talk
to
me
if
you
can
create
a
a
token
and
send
it
to
me.
That's
a
good
place
to
start
we're
starting
this
certification
program
and
that's
one
of
the
first
parts,
and
then
we
want
to
move
people
into
an
apprenticeship
program
where
you're
getting
paid
and
you're
working,
but
first
things.
First,
you
gotta
show
us
you
can
do
some
of
this
stuff.
You
know
historian's
still
showing
us.
You
know.
C
F
F
B
You
know
your
non-custodial
online
web
wallet,
so
one
of
the
only
ones
that
supports
nft
tokens,
yup
I've
lost
an
nft
token,
sending
it
to
a
non-supporter
wallet
before
so
and
but
bear
in
mind,
don't
keep
a
lot
of
money
on
it.
It
is
a
web
wallet.
So
don't
put
your
life
savings
in
a
web
wallet.
You
know
and.
B
Yes,
write
down
your
12
words:
do
it
and
preferably
write
down
your
private
key
as
well
and
check
it
front
to
back
now
a
lot
of
people
don't
do
that
either.
You
know
it's
really
easy
to
to
mess
things
up,
always
check
it
backwards
and
forwards,
and
especially
with
your
mnemonic,
your
seed,
your
12
words,
so.
B
A
So
all
right!
Well
yeah,
it's
been
about
an
hour.
Let's
go
ahead
and
wrap
this
up.
It's
been
a
it's
been
a
great
meeting,
lots
of
lots
of
successes.
The
last
couple
weeks
we
got
more
stuff
coming
down
the
pike
and
yeah
I'm
making
pretty
steady
progress
on
that
pay
to
write
database,
and
I
just
really
can't
can't
emphasize
enough.
I
really
want
people
to
go
check
that
out
and
they
it's
it's
live
you
can.
You
can
interact
with
it.
A
You
have
to
burn
a
psf
token
in
order
to
write
data
to
the
database.
So
that's
that's
kind
of
the
coolest
thing
and
yeah
it's
0.01,
so
every
one
psf
token
gives
you
100
and
but
yeah
I'm
looking
forward
to
improving
that
and
making
it
a
little
more
robust
and
starting
to
develop
some
of
the
on-chain
interfaces
for
it,
so
that
so
that
on-chain
apps
can
write
and
read
directly
to
the
database.
B
Yeah
cool
and
so
right
now
what
are
we?
What
are
we
sitting
at
50
cents,
40
cents
for
a
token
yeah
we're
hovering
around
50
cents.
I
think
it's
closer
to
40,
but
and
so
for
that
amount
you
can
write
a
megabyte
to
the
blockchain
and
think
about
it.
As
a
semi-permanent
way
of
writing.
You
know
you're,
not
exactly
etching
things
in
stone,
but
you're.
Also,
not
writing
them
down
on
a
cocktail
napkin
either.
So.
A
F
A
An
interesting
idea
because
it's
similar
to
a
blockchain
yeah,
it's
the
the
10
kilobytes,
is
you
know
that
you
can
only
write
220
bytes
to
the
op
return
in
a
in
a
bitcoin
cash
transaction,
and
I
believe
that
that
requirement
is
enforced
across
all
the
turns.
That's
that's
actually
something
I
don't
know.
I
don't
know.
I
don't
think
you
can
do
two
opera
turns
with
220
bytes
in
each
one.
I
think
the
amount
of
data
is
sort
of
split
among
all
the
op
returns.
I
might
be
wrong
about
that,
but
but
anyways.
A
The
idea
here
is
that
you
will
be
able
to
essentially
send
a
dust
output
in
a
transaction
that
has
not
returned
to
the
database,
which
will
then
that
will
be
the
payment
to
to
record
the
data
in
the
op
return
to
the
database.
And
then
you
can
also
send
a
similar
transaction
to
it.
To
read
that
operating
back
out
of
the
database
into
an
on-chain
transaction
and
that
and
you'll
have
multiple
blockchains
with
the
ability
to
do
that.