►
From YouTube: PSF TSC Meeting - 07-06-2022
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
A
And,
as
always,
guys
help
me
keep
an
eye
on
the
the
youtube
comments,
I
usually
don't
don't
look
at
those.
A
Right
on
okay,
welcome
everybody
to
the
permissionless
software
foundation.
Technical
steering
committee
today
is
july.
6Th
2022.
I
am
chris
troutner,
let's
go
around
and
do
some
quick
introductions.
Let's
start
with
you,
aaron
sunmen.
B
Greetings:
aaron
sunderman
here
big
fan
of
the
permissionless
software
foundation.
I
feel
like
this
is
one
of
those
and
I've
probably
said
this
in
every
introduction.
An
amazing
important
part
of
humanity
to
have
the
self-sovereign
individual
start
to
come
alive,
protection
from
the
state
and
I
feel
like
if
it's
not
permissionless,
it's
not
going
to
work
so
building
software.
B
For
this
permission
allows
this
to
happen,
is
fantastic
and
I'm
I'm
proud
to
be
a
part
of
it
and
also
shout
out
to
david
who's
watching
on
youtube.
C
Hi
my
name's
sam
and
I
am
a
psf
supporter
and
I'm
here
for
a
peer-to-peer
cash
for
the
world,
I'm
a
peer-to-peer
cash
maximalist
and
yeah.
I
think
that's
it
for
now.
A
And
you
run
some
web3
infrastructure.
I
was
just
testing
that
yesterday,
like
mine
fall
over
and
I
always
well
sam's
is
up
and
running.
Oh
yeah,.
C
I
I
haven't,
I
haven't
monitored
it
or
I
haven't
been,
keep
like
checking
it,
but
I'm
assuming
it's
still
like.
A
A
So,
as
always,
our
agendas
are
posted
on
github
under
the
permissionless
software
foundation,
github
group,
under
a
repository
called
tsc
for
technical
steering
committee
they're
filed
as
issues,
so
you
got
to
go
to
that
issues,
tab
and
then
they're
dated
so
the
scope
of
the
meeting
there's
some
helpful
links
at
the
top
here,
like
the
zoom
meeting
link
the
youtube
channel,
the
sort
of
rules
for
joining
is
in
this
pre-meeting
checklist.
The
scope
of
what
we
talk
about
is
some
of
the
software
listed
here.
There's
a
more
exhaustive
list
at
cashstack.info.
A
And
so
yeah,
let's,
let's
jump
on
into
it,
give
a
quick
update
on
the
token
decks.
So
just
as
a
refresher,
the
permissionless
software
foundation
was
given
a
grant
last
year
by
ava
labs
to
take
our
decks
prototype
at
that
time
time
and
bring
it
over
to
the
avalanche
x
chain
and
the
ecash
gnc
also
matched
that
grant
so
that
they
could
have
a
similar
decks
on
the
ecash
chain.
A
And
so
since
avalanche
was
first,
they
are
getting
the
software
first.
So
we're
I'm
in
the
process
of
wrapping
that
up
got
a
couple
links
to
a
couple
of
repositories
here:
avex
dex
ui,
I'm
rethinking
the
ui,
because
on
the
avalanche
side,
this
is
going
to
have
to
be
a
multi-chain
wallet.
So
it's
going
to
have
to
have
a
little
bit
of
bitcoin
cash
and
psf
tokens,
because
the
pay
to
write
database,
which
is
at
the
core
of
the
dex
right
now
only
exists
on
bitcoin
cash
and
someday.
A
A
So
if
anybody
wants
to
get
a
sneak
peek
at
what
the
user
interface
is
going
to
look
like
there,
I'm
basically
rewriting
it,
I'm
I'm
reusing
huge
chunks
of
code
from
from
the
other
wallets,
but
since
I'm
I'm
using
this
as
an
opportunity
to
basically
brush
up
on
my
react
skills
and
build
some
react.
Apps
and
I'll
talk
about
that
more
in
a
minute.
A
But
after
we
get
the
decks
up
and
running
on
avalanche
and
wrap
up
that
grant,
then
the
bch
decks,
which
is
fully
functional
at
this
point,
still
needs
some
improvement
found
that
you
know
it's
functional,
but
it
still
needs
a
lot
of
ux
improvement.
That's
going
to
be
a
pretty
simple
fork
to
get
it
over
to
the
ecash
chain,
so
I'll
focus
on
that
afterwards,
after
after
the
avalanche,
deck
is
up
and
running,
and
then,
after
after
that,
after
we've
met
our
sort
of
grant
obligations.
A
The
very
next
thing
I'm
very
excited
to
do
is
build
this
buy
now
button
which
we've
discussed
in
previous
meetings.
That'll.
Let
anybody
sell
any
token
on
the
deck,
so
I
want
to
build
it
so
that
I
can
sell
my
own
nfts
and
just
have
a
nice
buy
now
button,
but
one
of
the
sort
of
prototype
or
what
would
that,
like
a
boiler
plate
that
I'm
going
to
create?
A
Would
let
people
sell
usdt
the
the
the
one
stable
slp
stablecoin,
so
you
can
sell,
buy
essentially
make
it
really
as
easy
as
possible
to
buy
stable
coins
using
using
the
dex
protocol
and
as
always
guys,
if
you
have
any
questions
or
comments,
jump
in
and
interrupt
me.
Otherwise,
we'll
just
get
through
this
and
and
we'll
get
to
the
round
table.
A
So
I
talked
about
sort
of
rewriting
the
user
interface
using
react.
So
I
created
this
repository
called
react:
bootstrap
web
3,
spa,
so
spa
stands
for
single
page
app
and
it
leverages
our
web3
infrastructure.
A
A
And
I'll
give
that
a
minute
to
come
up,
but
it's
based
on
bootstrap,
so
bootstrap
is
a
is
an
html
and
css
template
it
it's
mobile
first.
So
basically,
what
this
lets
me
do
is.
I
can
just
focus
on
the
utility,
the
javascript
and
making
things
do.
What
I
want
to
do,
and
I
don't
have
to
spend
much
time
thinking
about
how
it
looks
or
how
it's
going
to
look
on
a
desktop
versus
a
a
phone.
That's
what
bootstrap
does
for
me.
A
They've
got
that
all
figured
out.
I
don't
have
to
think
about
it.
All
I
have
to
focus
on
is
just
like
putting
boxes
together
and,
and
then
the
bootstrap
framework
will
make
sure
that
it
all
looks
pretty
on
a
phone.
Oh
looks
like
this
thing's
still
coming
up.
D
A
A
A
C
I've
been
hearing
a
lot
of
people,
talk
about
a
tailwind
for
css
and,
like
you
might
want.
You
could
probably
look
at
that
too.
Like
some
it,
it
makes
the
you're
using
the
ui
components
a
lot
easier,
too
kind
of
like
bootstrap,
but
it's
like
a
modern
tool.
A
Okay,
that's
good
to
know.
I
need
to
check
into
both
of
these.
Bootstrap
was
just
something
I
learned
about
years
ago.
I
haven't
really
touched
this
front
end
stuff
in
a
long
time,
and
I
noticed
that
they
had
a
react
bootstrap,
so
they
took
all
the
bootstrap
and
they
basically
wrapped
it
with
react.
So
everything
that
bootstrap
offers
is
now
available
as
a
react
component.
So
that's
that's
largely
what
we're
we're
seeing
here,
but
what
you
can
see
is
when
it
comes
up
it
loads,
the
wallet
library
and
then
it
it
initializes
the
wallet.
A
So
that
means
this.
It's
going
out
to
the
it's
initializing
minimal,
slp
wallets
and
it's
leveraging
our
web3
infrastructure
by
default.
It
uses
freebch.fullstack.cache,
but
then
there's
this
drop-down
box,
and
so
you
can
if,
for
some
reason,
that's
down,
you
can
select
one
of
these
redundant
back
ends.
So
this
is
all
a
boilerplate.
This
is
intended
for
people
to
fork
and
then
start
from
here,
and
so
I
just
instituted
this
drop
down
menu
and
the
sort
of
the
ability
to
switch
between
different
views
by
selecting
things
in
the
menu.
A
So
it's
just
a
boiler
plate
and
then
I
also
forked
it
and
created
this
dash
android
fork,
which
has
the
capacitor
framework
which
lets
you
compile
that
into
a
native
android
app.
So
it
has
all
the
hooks
for
that,
and
so
this
is
a
great
way
to
we.
We
managed
to
do
all
this
with
the
with
the
with
wallet.fullstack.cache,
but
it
was
sort
of
after
the
fact
and
as
I
started,
to
dig
into
that
code
base
and
customize
it
for
for
avalanche.
A
I
realized,
like
you
know
if
we
had
been
able
to
start
from
scratch
with
a
clean,
a
clean
start
and
get
it
into
capacitor,
so
that
we
could
generate
the
android
app
and
like
did
that
from
day
one
and
then
and
then
added
all
the
functionality
we
needed
on
top.
A
That
would
actually
have
been
a
better
way
to
do
it,
so
this
is
kind
of
I'm
sort
of
taking
that
as
far
as
I
I'll
take,
I
can
take
it
as
long
as
it's
sort
of
efficient
and
cost
effective,
but
anyway,
so
if
anybody's
interested
there's
this
boilerplate
here,
you
can
do
very
simple.
You
know,
like
the
example,
there's
check
a
balance,
but
this
is
the
same
template
I'm
using
for
like
my
nft
display,
and
then
the
capacitor
framework
is
a
pretty
simple.
A
You
just
pull
your
code
into
this,
this
android
fork
and
if
anybody
actually
wants
to
install
android
studio
and
go
through
the
faster
documentation
is
pretty
simple.
But
if,
if,
if
you
need
any
hand
holding
I'm
happy
to
help
but
yeah,
the
idea
here
is
just
to
start
from
from
a
simple
boilerplate
and
then,
as
I
add,
features,
ensure
that
it
can
be.
Everything
can
be
compiled
into
android
and
keep
everything
in
sync
like
that.
A
A
You'll
wanna,
you
wanna,
pull
in
the
changes
and
rebuild
what
it
does
now
is
when
it
starts
up
it.
Look
it
pulls
down
the
mutable
data
for
this
token,
and
I've
actually
got
that
here
and
so
in
the
mutable
data.
Of
the
token
is
this
price
history,
and
so
this
sets
the
cost
of
one
penny's
worth
of
psf
tokens.
So
you
know
on
624
it
was
0.133.
A
This
price
look
up,
and
so
this
allows
us
to
peg
the
right
cost
or
the
cost
of
writing
to
the
database
to
us
dollars,
rather
than
natively
pegging
to
0.01
psf
tokens,
whatever
that
happens
to
be
in
fiat,
that's
what
it
was
before,
so
I
I
like
this
because
it
because
we're
going
to
get
a
the
psf
as
an
organization.
A
It's
just
it's
much
more
easy
to
reason
about
cash
flows.
So
as
we
get
more
rights,
every
right
is
a
penny
and
that's
that's
our
cash
flow.
That's
our
operating!
A
You
know
cash
flow
and
it
also-
and
it's
so
it's
a
way
of
sort
of
pegging
the
token
to
the
dollar,
at
least
as
far
as
the
paid
right
database
is
concerned,
in
a
decentralized
way.
That's
tamper
resistant,
especially
once
this.
This
sort
of
update
baton
gets
passed
to
the
minting
council.
It'll,
be
part
of
a
multi-sig
operation.
B
I'd
love
to
see
how
you're
actually
using
something
like
the
idea
of
mutable
data,
which
has
not
been
something
that's
really
been
presented
to
most
people
even
anywhere
in
the
web
3
space
I
feel
like
this
is
an
interesting
concept,
but
using
it
in
a
way
that
allows
for
something
to
be
used,
you
know
to
to
add
value
to
a
whole
ecosystem,
so
well
done.
I
think
this
is
great.
A
Cheers
thanks
and
then,
as
part
of
while
I
was
doing
this
so
I
I
felt
like
I
needed
to
do
this
now,
because
I'm
gonna
be
leveraging
this
work
as
I
wrap
up
the
avalanche
decks
because
it's
gonna
talk
to
the
pay-to-write
database,
and
so,
as
part
of
this,
I
I
took
the
time
to
increase
the
test
coverage.
So
it's
the
payroll
database
is
almost
at
100
test
coverage.
It's
like
99.8,
or
something
like
that.
There's
like
three
lines.
A
I
was
having
a
hard
time
getting
included
in
the
test,
so
I
always
like
it.
When
I
get
a
project
100
test
coverage,
I
really
feel
like
okay.
This
can
sit
now
and
I
can
go
work
on
something
else,
and
I
know
that
like.
If
I
get
a
drive
by
pull
request,
you
know-
and
I
I
I
have
a
high
degree
of
confidence
when
I,
when
I
merge
it
in.
A
That's
pretty
much
the
agenda,
the
yeah.
It's
pretty
much
just
full
speed
ahead
on
the
decks.
It's
trying
to
wrap
up
those
grants.
That's
that's
the
main
main
focus
for
me
right
now,
so
I
want
to
open
it
up
to
the
roundtable
discussion.
Aaron
you
were
talking.
A
B
Yeah,
hey
so
hello,
everybody
is
it
possible
for
you
to
share
a
screen
as
well
yeah.
B
Okay,
so
I
was
just
going
to
show
it's:
it's
not
done
yet.
There's
lots
to
do
on
it,
but
the
idea
is:
I'm
building
out
a
I'm,
an
nft
exchange
for
slp
nfts
right
so
on
bitcoin
cash.
Now
and
it's
I'm,
you
know
it's
going
to
take
a
long
time
really
to
get
some
of
it,
but
I
wanted
to
kind
of
come
back
with
some
of
this
idea
of
how
do
we
help
the
psf
grow
and
how
does
it?
B
How
do
we
monetize
some
of
this
and
and
and
I
I
I'm
not
taking
it
as
a
as
is
granted
that
you
actually
want
me
to
do
this,
so
I'm
sort
of
asking
you
today,
too,
is
to
say:
hey,
is
this
okay?
Is
this
something
that
that
we
would
consider
to
be
a
useful
thing
for
the
psf
as
a
token
ecosystem?
So
the
idea
is
when
someone
logs
into
this
right
so
right
now,
it's
not
done
clearly.
B
I
don't
have
a
lot
of
things
done,
but
I
do
have
a
login
process
and
I
have
this
where
it
goes
out
and
looks
at
how
many
looks
at
my
each
I'm
using
the
psf
bch
wallet,
so
each
person
gets
their
own
wallet
and
it
respects
slp
tokens
and
ft's
bch,
and
so
what
it
did
is
it
just
queried
for
two
things,
my
the
amount
of
bch,
which
I
have
seven
cents
talking
big
money
here
and
then
we
have
like
a
dollar
52
worth
of
psf,
and
so
I'm
I'm
doing
a
query.
B
Every
20
minutes
right
now
against
the
cost
of
that,
and
just
so
I
have
a
quote
system
going
on
and
then
the
ability
to
just
be
able
to
create
an
nft
and
put
it
up
for
sale.
So
this
is
clearly
not
done
yet,
but
the
idea
also
is
is
to
make
sure
that
the
individual,
when
something
is
sold,
I'm
going
to
stop
sharing
now,
because
it's
not
that
exciting,
it
looks
good.
B
The
idea
is
to
have
something
where
when
something
is
sold
the
individual
receives.
You
know
85
of
the
the
fund
for
selling
that
some
percentage
of
it
gets
paid
back
to
them
to
the
to
the
creator
in
psf
tokens.
B
That
is
that,
like
I
would
like
to
be
able
to
say
all
of
the
stuff,
the
the
the
ponies
that
were
created
for
ps.
You
know
slp
nfts,
the
reapers.
All
those
can
can
be
brought
in
here
and
sold
on
here
there's,
so
it
wouldn't
be
just
stuff-
that's
created
here,
but
it'd
be
trying
to
use
every
bit
of
those
that
have
been
created
and
used
in
the
past
and
being
able
to
have
like
the
sphere.
I
don't
know
into
the
sphere.
B
I
don't
know
if
you've
seen
that
game
or
played
that
game,
but
he
uses
slp
and
ft's
to
be
able
to
run
all
that,
and
so
I'd,
like
all
of
these
things,
to
to
work
out
here
and
to
integrate
the
psf
token
as
a
part
of
that
ecosystem,
so
general
discussion
here
is
there
negatives
to
that.
Is
it
positive
to
that?
What's
your
take?
Is
anyone
completely
against
it?
First
of
all,.
A
What
what
I
also
think
is
great
is
that
it's
not
me
doing
this,
I'm
glad
that
somebody
else
is
doing
doing
this
and
you
know
so
there's
we're
in
this
lull
with
the
nfts
right
now,
with
with
you
know
the
carnage
that's
going
on
in
smart
bch,
it's
unclear
if
all
of
this
migration
to
smart
bch
is
going
to
continue
or
if
there's
going
to
be,
people
are
going
to
come
back
to
slp
like
enter
the
sphere
is
a
perfect
example.
I
think
they
were
are.
A
I
think
they
have
the
wheels
in
motion
to
actually
move
to
a
different
blockchain,
but
you
know
I'm
ramping
up
my
nfts.
I've
got
a
couple
artists,
sort
of
waiting
in
the
wings
who
want
to
leverage
our
nfts
with
mutable
data
to
start
launching
art
and
then
I'm
working
with
launchpadip.com
to
to
create
a
system
for
for
basically
capturing
intellectual
property
as
as
an
nft
and
then
being
able
to
sell
that
and
so
yeah.
I
love
what
you're
building
and-
and
I
think
it
definitely
is
going
to
add
a
lot
of
utility.
B
That
you've
got
all
of
that
going
on
as
well,
because
I
feel
like
I
I
realize
you
know,
there's
a
lot
of
people
that
have
left
slp.
Even
the
guy
who
wrote
jungle.net,
I
don't
know
freeman,
I
think
I
mean
it
looks
as
though
a
lot
of
that
is
been
abandoned,
not
necessarily
that
project
but
others,
but
there's
we're
still
in
a
spot
where
people
even
like
and
reason
how
we're
at
horowitz
partners
have
a
hard
time
explaining
web
3
to
people
in
in
the
media.
B
And
the
funny
part
is
I'm
like
chris
dixon.
All
he
had
to
say
back
to
the
person
was
yeah,
but
if
you
sell
the
pdf,
they
can
just
keep
copying
and
copying
over
and
over
again
the
nft
cannot
be
copied,
it
is
sold
to
the
individual
and
he
didn't
actually
say
that.
So
even
even
the
best
people
have
a
hard
time
explaining
this,
which
means
this
is
still
nascent,
it's
still
new
and
it
doesn't
matter
if
it's
on
a
smartphone
or
whatever
else.
This
is
still
coming
and
it
will
be
big.
E
I'm
I'm
very
glad
that
you
are
developing
this.
This
is
totally
needed.
The
I
think
that
the
slp
token
itself
is
a
gateway
towards
the
decentralized
metaverse
and
because
the
is
so
much
cheaper.
Therefore,
it
is
easier
for
game
creators
to
create
using
the
slp
token,
but
I've
been
saying
for
a
while.
What
we
need
is
a
marketplace
someplace,
where
you
can
display
it
and
now
you're
doing
that.
That's
awesome!
E
You
may
want
to
look
at
3js
and
babylon.js
as
integrations
so
that
you
can
properly
display
3d
assets
there.
There
are
different
one
like
I
think,
three
jazz
and
babylon
js
both
have
they.
They
have
some
different
players,
so
you
have
to
look
at
them,
but
they'll
load
in
glbs.
E
They
can
load
up
gl
tiffs,
I
don't
know
if
anybody's
using
usds
yet
but
having
that
would
be
great
for
for
display
and
really
would
take
it
to
the
next
level,
because
that,
as
a
creator,
that's
one
of
the
things
I
find
that's
an
issue
is
that
you
know
there'll
be
a
lot
of
nft
stuff
but
nobody's
looking
at
supporting
the
3d
nfts,
which
are
the
future.
You
know
of
integration
and
interoperable
gaming
and
stuff
like
that.
So.
B
Yeah,
I
I
agree,
there's
an
interesting
side
to
that
too,
is
is
I've
mentioned
this
before,
but
usually
my
brothers
live.
I
have
four
older
brothers
and
they
all
live
across
the
united
states.
We
get
together
on
saturday
mornings
and
play
golf
together
on
the
oculus
rift
on
the
oculus
quest
2.
We
actually
play
walkabout
golf.
We
actually
have
an
hour
just
hanging
out
playing
golf
together
and
they're
all
over
the
country
and
they
could
be
anywhere
in
the
world.
B
But
this
idea
that
that
this
3d
space
is
is
still
new,
but
it
is
coming,
and
you
know
it
doesn't
matter
like
what
it
looks
like
right
now.
I
don't
know
how
old
all
of
you
are,
but
I
remember
when
the
first
sound
blaster
card
could
play
two
sounds
simultaneously
and
I
thought
that
was
amazing.
Now
I
got
a
phone
right
here
that
can
play.
You
know
eight
tracks
simultaneously,
and
so
so
you
know
just
just
because
it's
it's
not
big
yet
doesn't
mean
it
won't
be
so
shoemaker.
B
E
Well,
yeah
and
go
ahead.
Well,
I
was
going
to
say
this
really
ties
into
something
you
and
I
were
talking
about
chris.
I
think
last
week
with
the
ipfs
cluster
network,
I
mean
now
here's
a
place
for
them
to
write
and
some
you
know.
Maybe
we
can
take
this
to
an
another
point
up
after
chris
says
what
he
wants
to
say,
but
we
were
talking
about
utilizing
the
pay
to
write
database
as
a
pseudo
type
of
private
right
and
then
the
the
cluster
as
a
private
or
a
public
network.
E
You
know
writable
network
and
utilizing
slp
tokens
as
a
way
to
write
to
the
private
network
and
tell
the
public
network
what
to
pin.
So
that
was
another
thing.
You
know,
which
kind
of
goes
hand
in
hand
with
what
you're
talking
about
with
an
nft
whole
creation.
So
now
we're
using
the
psf
token
in
multiple
ways.
You
know
not
only
are
you
using
it
for
the
for
the
nfts,
but
you
could
be
using
it
to
pin
the
data
that
you're
that's
associated
with
your
nfcs.
A
Yeah,
I
love
seeing
the
psf
token
as
a
payment
method.
That's
something
we
need
to.
I
mean
that's
something
I
plan
to
grow
like
one
of
the
things
I
hope
we
can
get
to.
Probably
next
year
is
building
a
bridge
between
usdc
on
the
avalanche
chain
and
the
psf
token,
we'll,
probably
end
up
building
once
we
launch
the
avalanche
decks,
we'll
also
simultaneously
launch
a
psf
token
on
x-chain
and
a
bridge
between
psf
on
pch
and
x-chain,
so
being
able
to
exchange
the
psf
token
for
different
things.
A
I
mean
using
it
paid
right,
but
I
love
that
you
got
this
nft
sale.
You
know
a
way
to
sell
nfts,
because
one
of
the
things
I'm
working
on
with
launchpad
is
enabling
download.
So
the
idea
the
workflow
here
is
that,
like
an
artist,
doesn't
want
to
put
out
the
hi-res
image
they
want
to
put
out
just
like
the
token
icon,
and
so
they
would
create
an
nft
that
represents
the
high
res
stuff.
A
That's
what
you're
actually
buying,
and
so
you
would
buy
this
nft,
which
is
just
the
low
res
image
on
on
an
exchange
like
what
you
you're
building
and
then
bring
it
back
to
launchpad
to
exchange
it.
You
would
burn
it
to
get
the
actual
high
resolution
artwork
that
you're
trying
to
buy-
or
this
applies
to
any
kind
of
intellectual
property,
but
basically
using
tokens
as
a
key
that
unlocks
the
download
for
the
actual
intellectual
property.
A
So
it's
a
service,
it's
a
very
hard
thing
to
do
in
a
decentralized
way,
which
is
why
launchpad
is
building
it
and
so
and
what
we
don't
have
is
the
secondary
market
like
we're,
building
the
infrastructure
to
take
for
a
creator
to
create
a
token,
send
it
out
to
a
secondary
market,
a
user
to
acquire
that
token
somewhere
in
the
secondary
market,
bring
it
back
and
burn
it
to
to
unlock
the
download
yeah.
That's
awesome.
B
A
B
That's
happening
that
built
into
the
the
psf
bch
wallet
is
the
stability
that,
when
money
moves,
the
psf
automatically
gets
2000
satoshi's,
which
I
think
is
great,
so
that
we're
trying
to
support
her,
I'm
with
the
own
rare.art
site,
I'm
trying
to
support
it
in
two
different
ways.
One
is
to
support
the
usage
of
the
psf,
but
also
make
sure
that,
as
any
money
moves
around
it
automatically
there'll
be
little
chips
of
it.
Get
sent
to
the
psf
to
support
continued
development.
A
B
C
Let's
see
like
primary,
like
like
the
the
nfcs
themselves,
are
they
like
mostly
geared
towards
like
artwork,
or
I
think.
B
At
the
beginning,
it
would
be
probably
artwork
I'm
just
trying
to
keep
it
really
simple
in
the
beginning
and
then
add
functionality.
But
I
part
of
this
is
this
idea
of
well,
once
you
get
to
the
idea
of
immutable
and
mutable
data
associated,
I
think,
there's
a
whole
bunch
more
functionality
that
can
come
out
of
it
and
it's
difficult
to
see
it
right
now,
but
I
the
stuff
that
chris
is
doing
with
the
paperwhite
database,
where
you
actually
have
something
go
up.
Query
ipf
grab
that
file.
B
C
Right
I
was
watching
the
the
cash
tokens
proposal
yesterday
and
there
were
a
lot
of
I
I
guess
yeah
I
was
looking
at
all
use
cases
for
tokens
and,
and
one
of
the
things
was
that
it
should,
according
to
the
proposal
the
creator,
he
said
it
should
be
easy
to
migrate
slp
over
to.
But
I
guess
we'll
see
when
it
comes
out
so.
C
This
is
a
cash
token.
This
is
a
different
proposal.
Oh
then,
this
is
supposed
to
be
in
the
utxo
itself.
I
I
believe
it's
you
yeah
it's,
so
I
guess
it.
The
the
token
itself
is
supposed
to
be
a
native
native,
so
it's
like
minor
validated
yeah.
B
A
Been
trying
to
follow
this,
I
mean
the
proposal's
been
out
there
for
a
while
and
in
fact
there
was
two
separate
proposals
and
then
they
merged
together
and
then
they
separated
again
and
then
they
merged
together
again
and
then
supposedly
it's
going
to
go
into
the
upgrade
in
may
next
year.
A
Take
all
of
this
with
a
grain
of
salt.
It's
all
vaporware
at
this
point,
and
so
that's
that's
that's
the
attitude
I'm
taking
is
like
I'll
believe
it
when
I
see
it
because
there's
a
big
gap
between
ideas
and
reality
and
that
gap
is
called
execution
and
so
we'll
just
see
if
they're
able
to
execute
there's
a
lot
of
good
ideas,
and
I
see
very
little
in
the
way
of
execution.
A
But
you
know
the
the
bchn
team
is
pretty
good
about
that
execution
and,
in
particular,
jonathan
silverblood's,
great
at
sort
of
taking
these
ideas
and
and
bringing
him
into
reality
and-
and
he
seems
to
be
putting
his
focus
on
this
one.
So
I
think
it
actually
has
a
pretty
high
probability
of
of
at
least
achieving
some
level
of
reality.
A
My
attitude
on
this
is
like
slp
tokens
are
here:
they
exist.
We
have
infrastructure,
we
can
use
them
today.
Whatever
happens
tomorrow
is
tomorrow
and
and
if
it's
great
and
there's
a
migration
path,
you
know
all
the
better
and
and
so,
and
so
I
mean
obviously
slp
tokens,
it's
a
trade-off.
A
They
they're
simple
and
there's
a
lot
of
downfalls
with
that
simplicity,
so
if
they
can
create
a
more
expressive
more
native,
you
know
token
protocol,
that's
that's
minor,
validated
non-chain
and
can
interact
with
the
any
hedge
you
know
protocol
and
all
these
wonderful
ideas.
A
I
hope
it
exists,
but
I'm
too
busy
like
dealing
with
reality,
so
I'm
I'm
just
like
cautiously
optimistic
trying
to
follow
it,
but
but
it
is
good
stuff
and
I
don't
want
to
poo
poo
on
it,
but
I
mean
we
didn't
bitcoin
cash
has
been
talking
about
tokens
literally
since
the
very
beginning
of
bitcoin
cash
since
2017,
so
I
I
hope
they
pull
it
off.
I
mean
slp
was
really
sort
of
born
out
of
the
frustration
of
lack
of
progress
on
that
front.
So
we'll
see.
D
Yeah
exactly
I
had
some
thoughts
on
the
decks
like
it
was
too
short
demonstration.
But
for
me
it
looks
too
much
web
too,
like
I
think.
Maybe
you
need
to
change,
for
example
around
the
user
names
and
passwords,
because
you
need
like
database
for
this,
but
maybe
it
will
be
better
just
to
connect
wallet
and
in
this
case
yeah
it's
same
like
authentication.
D
Other
thing,
maybe
like
web
interface
is
one
of
the
last
thing
you
need
a
lot
of
infrastructure
below
like
aaron
was
mentioned
when
you
try
to
have
like,
for
example,
any
of
this
in
some
wallet
you
need
to
show
all
of
the
media
and
if
you
don't
have
a
pinning
service
which
belongs
to
you,
which
will
get
all
of
these
images.
Now
most
of
this
ethereum
compatible
blockchains.
D
They
have
this
the
graph
stuff,
which
is
like
a
huge
indexer
which
is
getting
all
of
the
data
and
making
the
database
from
this.
So
they're
quick.
But
you
need
to
have
something
like
this
one
like
way
too
some
out
of
cash
graphical
or
other
data
close,
so
they
will
be
displayed
more
quickly.
Also,
maybe
we're
good
to
have
like
an
api
before
the
ui
because
front
end.
They
can
stop
it
very
easy,
and
so
it's
urls
and
stuff
like
this
one.
D
But
if
you
have
something
like
api
k,
everybody
can
create
ui
somewhere
on
files
everywhere
and
just
access
this
service.
So
I
think
maybe
first
priority
should
be
not
like
web
interface,
but
like
api,
which
you
can
sell
your
tokens
there,
and
it
can
be
this
service
that
now
we
are
creating
these
decks
so
yeah.
It's
I
think
more
important
is
like
back
story.
Oh
absolutely
yeah,
you're,
absolutely
right.
B
Yeah-
and
I
don't
disagree
with
any
of
that,
because
I
feel
like
especially
like
the
ability
to
I
mean
because
clearly
this
has
to
be
custodial
if
I'm
holding
the
wallet
right.
If
I'm
not,
you
know,
so
there
is
issues
with
what
I'm
doing
and
I
think
you're
absolutely
right
that
you
know
caching
this
and
having
all
of
this
data
is
not
going
to
be
a
simple
thing,
so
so
you're
right
and
I
I'm
I'm-
definitely
looking
at
all
what
you're
talking
about
and.
A
Well,
let
me
counterbalance
that
opinion
because
I
really
like
the
way
you've
approached
this
aaron
in
that
you
know
you're
much
more
comfortable
php
than
you
are
with
javascript,
so
you
you
can
make
those
sort
of
api
calls
between
the
front
end
and
the
back
end
and
so
you're
leveraging
the
command
line
wallet
so
that
you
don't
have
to
reinvent
the
wheel.
You
can
just
issue
command
line
instructions
with
your
php
and
then
and
then
let
the
let
the
psf
cli
wallet
or
sop
wallet.
You
know
handle
it.
A
So
I
really
like
that
approach
and
then
same
with
the
front
end.
You
use
the
template
and
you're
just
sort
of
taking
the
very
conventional
web
2
approach.
So
at
the
end
of
the
day,
the
end
user
doesn't
care.
What's
going
on
under
the
hood,
it
either
works
or
it
doesn't
it's
a
fairly
binary
thing:
it
either
looks
good
or
it
doesn't
it
either
works
or
it
doesn't
so
and
that's
that's
where
I
get
hung
up
so
I'm.
A
B
My
first
push
to
say:
I
don't
want
person
to
have
to
know
anything
just
be
able
to
come
here
and
do
it
you
know
and
get
if
they
want
it.
But
I
know
that
there's
a
lot
of
parts
that
I
already
feel
like:
it's,
not
the
web,
3
ethos,
and
so
there's
parts
that
I'm
I'm
I'm
conflicted
about
as
well.
So
I
first
I
just
want
to
get
something
running,
because
otherwise
I'll
never
get
done
I'll
get
nothing
happening
so
that
first
bit
yeah.
A
As
a
group
we're
tackling
this,
you
know
like
I'll
worry
about
making
sure
that
we're
we're
honest
and
we
have
a.
We
have
a
path
forward
with
the
decentralized
web
3
stuff.
So
I
I
love
that
you
can
counterbalance
that
force
with,
like
I'm
just
going
to
build
something
that
looks
good
and
works,
and.
E
You
know,
as
I
get
the
cluster
network
set
up,
you
know
we
can.
You
could
even
integrate
that
into
your
website,
or
you
want
to
upload
an
nfv,
some
art
or
something
like
that.
Then
you
can
say
how
many
times
you
want
to
pin.
Where
do
you
want
it
pin,
and
these
are
things
that
we're
trying
to
solve
for
the
cluster
network
that
don't
exist
right
now,
for
somebody
to
be
able
to
use
in
a
pending
service
today
you
know.
B
I
would
love
that
because
I
feel
like
one
of
the
big
things
is
anything
that
gets
created
shouldn't
rely
on
my
site
to
work.
It
should
be,
you
know
it
should
exist
as
a
token
and
then
any
all
the
content
should
be
on
ipfs.
I
mean
not
immediately,
because
I
don't
I
I
don't
figure
all
that
out
yet,
but
but
I
I
agree,
it
needs
to
work
the
way
you're
talking
about
and
be
decentralized
from,
the
ownership
perspective
and
the
usage
perspective.
E
Well
and
chris-
I
don't
know
if
you
want
to
talk
a
little
bit
about
the
idea
where
we
were
having
with
the
peterrite
database
and
the
cluster
and
using
both
of
those
as
a
for
people
to
be
able
to
pin
data
that
way.
A
Yeah
well
yeah.
Let's
just
recap
on
that.
Just
so
you
and
I
are
on
the
same
page
and
everybody
else
can
so
so
aaron
and
I
had
a
conversation
about
so
aaron's
doing
work
with
ipfs
cluster,
and
so
that's
the
ability
of
several
ipfs
nodes
to
coordinate,
to,
pin
the
same
content
and
he's
trying
to
to
essentially
do
like
a
cdn
type
stuff,
where
your
geographic
location
might
determine
what
ipfs
nodes
your
node
connects
to
in
order
to
to
have
better
performance,
and
then
we
were
talking
about
well.
A
How
can
we
and
in
there's
so
the
ipfs
cluster?
Is
its
own
software
project
separate
from
ipfs?
It's
just.
Basically,
it's
like
it's
similar
in
many
ways
to
the
ipfs
cord
library
that
I
wrote
where
it's
it's
essentially
a
a
blob
of
software
that
you
bolt
onto
an
ipfs
node,
and
now
you
can
now
you
can
coordinate
this
cluster,
whereas
ipfs
cord
is
the
same
thing,
but
it's
more
about
communication
rather
than
pinning
files.
That's
really
the
main
difference
between
the
two.
A
Well,
so
we've
got
the
pay
to
write
database,
which
is
in
many
ways
an
ipfs
cluster,
because
what
you're
doing
is
you're
you're,
coordinating
the
pinning
of
of
content
and
that's
what
the
that's.
Essentially,
what
the
right
database
is
every
instance
maintains
its
own
copy
of
the
database
and
that
that
data
is
available
over
ipfs
now.
One
one
obstacle
right
now
is
that
the
paid
right
database
uses
is
on
a
private
ipfs
network.
It's
not
on
the
public
ipfs
network,
so
aaron
and
I
were
discussing
different
ways
to.
A
Sort
of
bridge
that
gap
and-
and
so
one
one
way
would
be-
keep
the
payrate
database
private
and
use
like
an
slp
use.
The
mutable
data
of
an
slp
token
to
somehow
sort
of
jump,
ju
hop
the
fence
there
or
you
know,
but
honestly,
so
so
what
I
really
actually
want
to
try
aaron
is
I'd
like
to
get
the
pay
to
write
database
out
of
the
ipfs
private
network.
I'd
like
what
I,
what
I
plan
to
do
is
set
up.
That
would
be
great.
A
Yeah,
I
mean,
I
think,
that's
ultimately
like
as
far
as
a
goal
like
that
should
be
our
goal
like
like
and,
like
I
said
during
our
discussion.
Moving
everything
over
to
a
private
ipfs
network
was
sort
of
a
an
act
of
of
desperation
just
to
sort
of
limit
limit.
The
influences
that
were
that
were
sort
of
there
were
so
many
problems
going
on.
I
couldn't
figure
out
like
what
was
how
to
attribute
the
different
things
and
how
to
separate
them.
A
A
I
think
I'm,
I
think,
it's
time
to
start
trying
to
build
that
back
out
on
the
public
network
and,
and
so
that
would
solve
a
lot
of
because
because
yeah
I
mean
that
we're
going
to
constantly
fight
this
problem
of
of
trying
to
get
data
back
and
forth,
and
I
would
love
it
if,
if
we
had
our
ipf,
if
we
had
the
paid
right
database
on
the
public
network,
then
people
can
access
individual
rights
in
the
database
just
over
ipfs.
They
don't
need
to
know
or.
E
A
E
Those
who
don't
understand
what
chris
is
saying
you
need
a
gateway
to
access
anything.
That's
on
a
private
network.
Therefore,
you're
always
going
to
induce
some
amount
of
latency
if
you're
having
to
jump
through
gateways
and
whereas,
if
it's
public,
you
can
just
connect
automatically
from
node
to
node
and
therefore
you
can
increase
your
speed.
In
fact,
you
could
crack
connect
directly
so
like
when
people
are
downloading
the
cache
deck
software
and
chris
says
you
know,
ipfs
swarm,
connect
to
the
three
ipfs
ids
he's
got
you're
directly
connecting
to
those
three
machines.
E
You
know
so,
but
right
now,
because
it
is
a
private
network,
you
will
you
got
to
go
through
gateways
and
we
were
talking
about
ways
to
leverage
the
private
network
in
the
public
network
and
utilizing
both
of
them
and
perhaps
utilizing
the
psf
token
as
a
way
for
people
to
pay
say
I
want
you
to
pin
this
content
id
and
then
be
able
to
say
I
want
it
pinned
10
times
in
in
these
10
regions.
E
You
know,
and
since
we
would
it's
pretty
much,
that
infrastructure
is
very
close
to
being
there
within
the
psf
community.
A
lot
more
so
than
say
me
having
to
write
it
or
hire
somebody
to
write
from
the
ground
up.
A
Yeah,
so
there's
there's
this
payments
option,
so
it's
like.
If
we,
if
we're
just
a
club
and
we're
all
friends-
and
we
all
know
one
another-
we
don't
need
to
think
about
payments
or
scaling.
But
if
we're
any
sort
of
because
correct
there,
there
is
no
payment
mechanism
sort
of
in
the
ipfs
cluster
right,
aaron.
E
No,
no,
we
were
talking
about
like
if
you're
you
know,
I
think
we
left
off
saying
bounties
to
run
on
pay,
to
write
databases
and
at
first
you
know
our
cold
start
for
the
hard
side
is
free,
pinning
for
those
who
run
nodes
at
first,
but
eventually
having
bounties
for
people
that
run
the
nodes
so
like
right
and
eventually
you
get
to
a
spot
where,
yes,
you
have
you
earn
and
what's
good
is
okay,
maybe
you
earn
some
psf
tokens.
E
You
can
go
use
those
for
pinning
you
can
sell
them
on
the
decks
now
you
can
buy
nfts
with
them
on
aaron
cool,
cleaner
site.
You
know,
so
I
I
it's
really
a
win-win.
If
we
end
up,
if
we
do
end
up
doing
it
this
way,
because
the
utility
of
the
psf
token
is
just
going
to
increase
with
all
these
projects
right.
E
A
So
there's
two
ways
to
skin
this
cat:
there's
there's
the
we
could
do
bounties
like
we
have
set
up
for
the
the
the
other
psf
infrastructure,
where
we
just
pay
people
to
run
these
instances
and
pin
data
as
it
comes
in
there's
also
like.
So
this
is
where
the
the
pay
to
write
database
comes
in
is
in
addition.
A
So
if,
if,
if
you
wanted
to
pin
a
piece
of
content
in
the
cluster,
one
way
that
we
could
do,
that
is
you
would
you
would
put
the
cid
that
you
want
pinned
into
a
pay
to
write
database
entry
and
then
all
these
nodes
that
are
listening
for
that
would
see
that
and
pin
the
content,
and,
along
with
that
data,
you
could
include
other
data
like
proof
of
proof
of
burn,
so
we
could
say
like
okay,
we're
gonna
charge,
you
know
one
penny
per
megabyte,
and
so
what
what
the
you
know,
the
consensus
rules
would
be,
would
be.
A
Okay,
this
new
paid
right
database
entry
came
in
it's
for
our
cluster.
Here's,
the
cid.
I
want
to
pin
I'm
going
to
go,
get
it
and
I'm
going
to
check
how
big
it
is
and
check
that
against
the
proof
of
burn
to
make
sure
they
they
paid
enough.
And
then,
if
that
all
checks,
then
I
will
pin
the
content.
So
so
one
is
sort
of
the
psf
as
an
organization
can
incentivize
this
through
through
bounties
or
the
individual
users
can
pick
like.
You
know,
pay
to
play
sort
of
things,
and
we
can
do
both.
E
Yeah,
I
think
a
lot
of
it
is
like
we're
getting
nose
distributed
one
by
one
to
people
and
a
lot.
It's
literally
adam,
going
to
their
house
setting
up
ports
forwarding
on
their
routers,
setting
up
the
machines
and
okay.
Now
we
got
ipfs6
up
and
we're
slowly
getting
to
where
we
have
all
15
machines
set
up
and
we
can
coordinate
them
correctly
and
start
running
tests.
But
after
that
point,
like
you
said
you
know,
I
think
it's
about
finding
the
proper
incentivization
mechanism.
E
I
do
think
I
do
like
the
idea
of
using
the
psf
token
for
painting
of
content
or
on
in
bounties
both
because
I
think
they're
going
to
give
utility
to
the
psf
token
added
utility,
because
it's
already
being
used
for
the
decks,
so
people
are
going
to
want
to
acquire
it.
Well,
here's
another
way
to
acquire
it.
You
know
I
could
go
on
the
decks
and
I
could
trade
for
it
or
I
could
run
a
cluster
node
and
I
could
earn
it.
You
know,
through
a
bounty
or
or
something
like
that.
F
E
So
this
is
another
way
to
earn
psf
tokens
and
then
be
able
to
utilize
them
for
the
projects
that
seem
to
be
cohesively
standing
up
all.
At
the
same
time,
I
had
no
idea
that
aaron
was
working
on
the
nft
thing,
which
just
really
goes
hand
in
hand
with
the
ipfs
cluster
thing,
because
you
need
some
place
to
store
this
data
and
ipfs
cluster
makes
a
lot
of
sense.
For
that
you
know,
and
then,
when,
when
you
take
the
pay
to
write
database,
I
do
like
the
idea
of
like
okay
pay.
E
The
right
database
is
about
being
lean
and
mean
you
know
it's
about
kilobytes
of
storage
and
it's
probably
best
used
to
reference
other
data
locations
right.
So
it's
getting
getting
it
fast,
being
lean
being
mean,
doesn't
take
a
lot
to
use
it
so
and
then
the
cluster
can
be
about
storing
larger
forms
of
data
right,
and
so
you
can
keep
those
separate
they're,
not
necessarily
the
cluster
is
not
going
to
get
so
big
that
it
bogs
down
the
original
functionality
of
the
paid
right
database
and
vice
versa.
E
Yeah
all
things
to
talk
about
once
we
get
the
cluster
stood
up
and
testing.
You
know.
I
think
that
having
them
separate
is
going
to
to
we're
going
to
find
benefits
to
having
whether
it's
taken
off
the
private
network
would
be
fine
but
having
it
so
that
pay
to
write
database.
This
is
what
the
pay-to-write
database
does.
E
That's
what
it
does
extremely
well,
and
you
know,
then
you
have
the
cluster,
which
is
like
all
right,
I'm
not
going
to
sit
there
and
upload
a
50
gigabyte
movie
to
the
pay
to
write
database,
but
I
might
pin
that
to
the
cluster
for
use
in
video
collaboration
right
so,
like
those
those
are
different
use
cases.
A
Yeah
I
just
want
to
jerry
thanks
for
sharing
this.
He
raised
an
interesting
idea
of
an
attack,
so
I
think
most
of
us
in
this
group
are
old
enough
to
remember
back
in
the
day
when
you
would
get
an
email
and
there'd
be
images
in
the
email.
A
really
common
tactic
was
that,
even
if
there
were
no
images
they
would,
they
would
include
at
least
a
one
pixel
image
that,
like
the
humans
wouldn't
even
notice.
A
But
when
you
open
the
email,
it
would
make
a
call
to
a
server
to
get
that
image
and
they
would
be
able
to
to
track
the
the
open
rate.
So
it's
like,
let's
say
they
sent
out
a
thousand
emails
they'd,
be
able
to
see
that
like
10
of
them
were
opened
because
10
of
them
made
a
call
to
get
this
one
pixel
image,
and
it's
so
small
that
it
you
know
it
didn't,
have
any
drag
on
performance.
A
So
jerry
was
just
pointing
out
an
article
about
how
this
is
being
done
now
with
nfts,
and
this
is
again
like
one
more
danger
of
having
the
image
that
represents
an
nft,
be
a
location-based
address
rather
than
a
content-based
address
on
ipfs
is
they
can
actually
see
the
ip
address
of
the
person
who
is
at
least
accessing
nft,
if
not
owning
it,
they
could
prob,
there's
probably
enough
information
there
that
you
could
you
know
if
you
just
pick
the
one
that
accesses
it,
the
most
that's
probably
the
owner
of
the
nft,
so
that
now
you
can
link
an
ip
address
with
the
ownership
of
an
nft
kind
of
a
sneaky
little
attack
yeah
and
again,
this
just
emphasizes
the
the
one
more
reason
why
he
should
be
using
ipfs
to
store
nft
content
and
not
centralized
urls
all
right.
C
I
was
wondering
I
wanted
to
ask
about
the
your
idea
of
the
buy
now
button
for
the
is
that
for
the
decks
I've
been.
C
I've
been
thinking
about
the
user
experience
and
basically,
like
are
you
looking
to
make
something
like
a
desktop
application
sort
of
like
how
you
know
like
like
limewire
used
to
be
where
user
just
clicks
a
button
and
the
the
app
just
spins
up
and
the
you
know
the
marketplace?
Is
there.
A
Yeah,
well,
I
covered
this
a
little
bit
in
our
last
meeting,
the
so
right
now
the
dex
is
based
on
the
idea
that
both
buyers
and
sellers
run
all
of
this.
These
docker
containers
and
it's
just
way
too
high
of
an
ask
for
like
the
casual
consumer.
A
So
the
idea
there
is
at
a
level
of
abstraction
by
creating
a
rest
api,
so
the
typical
web
2
back
end
that
most
websites
would
have
that
can
negotiate
the
the
dex
protocol
and
negotiate
the
purchase
of
a
token.
So
the
idea
was
so,
let's
say,
let's
say
I
want
to
sell
stable
coins,
but
I'm
gonna,
I'm
in
the
u.s
and
there's
laws
against
that.
So
I
I
can't
I
can't
just
trade
them.
A
However,
what
I
could
do
is
set
up
this
website
that
can
list
all
the
usdh
on
the
decks
with
a
buy
now
button
and
allow
you,
as
the
user
to
you,
know,
buy
that
thing
I
don't
know
legally.
A
I
don't
know
if
this
is
kosher
or
not,
but
the
idea
is
that
it
is
really
solving
the
problem
of
how
do
you
just
have
a
buy
now
button
where
the
user
can
just
click
the
button
get
a
qr
code,
pay
some
bch,
and
then
they
either
get
their
token
or
they
don't
the
nft
or
they
don't
and
so
what's
happening
behind
the
scenes.
There
is
the
rest.
A
Api
would
be
taking
that
money
negotiating
the
sale
through
the
dex
protocol
and
then,
after,
like
10
minutes
either
the
the
there
there's
that
there's
that
acceptance
phase
so
there's
three
there's
the
the
offer
the
counter
offer
and
the
acceptance
in
a
deck
sale.
So
the
the
seller
has
to
be
on
or
their
computer
has
to
be
online
in
order
to
see
the
counter
offer
come
through
and
finalize
the
transaction
by
generating
the
acceptance
and
broadcasting
acceptance
transaction
and
so
that
either
happens
or
it
doesn't.
A
And
so
the
idea
is
like
that
rest
api
would
take
the
money
and
hold
it
and
after
10
minutes,
if
the,
if
the
acceptance
transaction
has
been
broadcasted,
it
doesn't
need
to
do
anything
and
and
if
it
hasn't
it'll,
just
send
the
money
back.
So
there's
a
there's,
an
you're,
introducing
an
element
of
trust
in
that
you're.
A
Trusting
the
rest
api
in
order
to
get
a
better
user
experience
where
the
user
doesn't
really
need
to
know
anything
about
the
technology
just
hit
a
button,
pay
some
money
and
then
in
10
minutes
they
either
within
10
minutes.
They
either
get
their
money
back
or
they
get
the
token
that
they
wanted
to
buy.
A
Well,
I
was
gonna
do
a
couple.
I
was
gonna
talk
a
little
bit
more
about
this
idea
of
of
a
debt
of
the
craigslist
clone
idea.
I
had
a
few
more
thoughts
on
that,
but
I
also
just
wanted
before
we
dive
into
that.
I
wanted
to
point
out
that
bellagio
srinivasan
released
this
book
called
the
network
state.
A
B
A
Yeah
anyways,
I
think
it's
it's
you
know,
so
we
a
lot
of
people
in
the
crypto
space.
They
talk
about
the
sovereign
individual,
this
book
that
was
written
in
the
90s,
how
it
was
very
forward
thinking
and
then
you
know,
we've
we've
talked
about
other
books
like
the
cold
start
problem
recently,
which
is
all
about.
How
do
you
generate
network
effects
and
there's
there's
working
in
public
by
nadia
ekbal,
which
is
how
do
you
manage
open
source
communities?
A
And
I
think
this
is
another
sort
of
book
in
the
caliber
of
books
that
apply
directly
to
what
we're
trying
to
do
here
at
the
psf
in
his
book.
The
nation
state-
it's
it's.
A
It's
he's
been
he's
been
writing
on
this
topic
for
a
couple
years
now,
but
it's
this
idea
of
the
intersection
between
social
media
and
and
nation
states,
of
how,
like
there
aren't
very
many
nation
states
that
are
more
than
say,
10
million
people
where
there's
there's
a
significant
number
of
nation
states
that
are
that
have
populations
less
than
10
million
and
and
there
are
many
social
media,
there's
yeah
social
media
networks
that
are
bigger
than
10
million.
A
There
clearly
exists
an
overlap,
and
so
the
the
book
sort
of
theorizes
like
what
we're
going
to
see
in
the
future
in
terms
of
how
these
sort
of
social
networks
could
grow
to
contend
with
nation
states
and
why
an
individual
might
choose
to
join
one
or
not.
And
so
it's
just
a
very,
very
interesting
idea
in
his
outline.
He
talks
about
sort
of
the
stepping
stones
of
going
from
you
know.
A
First,
is
the
social
media,
which
is
just
a
group
like
us,
just
a
group
of
people
who
meet
once
in
a
while
with
a
common
interest,
and
then
the
next
step
is
unionization,
and
I
think
that's
where
we're
at
right
now
is
is
like,
is
creating
a
a
token-based
economy,
having
like
a
an
economic
and
like
utilitarian
purpose,
building
software
generating
a
cash
flow
as
a
as
a
group
and
an
economy
as
a
group
and
then
and
then
and
then
sort
of
going
from
there
and
and
formalizing
it
with
with
law
and
enforcement.
A
And
it
is
a
very
interesting
intellectual
exercise.
Even
if,
even
if
not
not
all
that
resonates
with
you,
it's
he
he's
probably
I
definitely
count
bellagio's
one
of
the
top
10
smartest
people
alive
today.
I.
B
B
Yeah,
I
I'll
definitely
read
that
book
too.
I
think
that's
one
of
those
I
think
you've
mentioned
the
cold
start
problem
as
well
as
this
one,
and
I
think
that'd
be
good
for
for
all
of
us
to
understand
the
at
least
those
that
are
minded
that
way.
A
A
So
we
talked
about
this
a
little
bit
in
the
the
last
meeting
and
I
was
introducing
the
idea
of
conceptualizing
a
store
as
an
nft
and
we
sort
of
got
into
the
the
pros
and
cons
of
you
know.
Why
should
it
be
an
nft
or
should
not
be
an
nft
like
why?
Why
this
or
why
that
we
kind
of
walked
through
some
of
the
logic
there
and
another?
A
One
of
the
things
that
we
discussed
was
this:
this
article,
that
we
had
shared
in
our
telegram:
channel
about
soul,
bound
tokens
and,
and
there's
this
really
thought-provoking
article
about
when
is
it
appropriate
to
make
something
represented
as
a
token
and
not
as
a
token
and
I'll
share
the
gist
of
that
article
was
that
claims
are,
should
not
be
tokens
and
a
claim
is
like
a
like
a
certificate
like
like
you,
you
pass
some
educational
thing
and,
and
so
like
you're,
getting
a
sort
of
a
badge
and-
and
that
really
should
probably
not
be
the
article
argued
that
that
should
not
be
a
token.
A
It
should
be
a
a
like,
a
transaction
on
the
blockchain,
that's
immutable
and
permanent
and
signed
by
a
a1
signature,
but
but
not
necessarily
a
token,
so
a
lot
of
nuance
and
subtlety
there
and
that
really
got
my
gears.
Turning
of
like
okay,
if
a
store
is
an
nft
and
its
products
are
probably
entries
in
the
paid
right
database
that
the
mutable
data
of
the
store
token
points
to
how
do
you?
A
How
do
you
like
leave?
How
does
a
customer
leave
feedback
or
if
you
know,
if
they're
not
safe,
for
work?
How
does
someone
sort
of
market
and
say
hey?
This
is
not
safe
for
work,
and
so
those
are
id.
Those
are
examples
of
claims,
like
reviews
and
compliments
and
complaints.
A
A
I
might
fork
the
psf,
slp,
indexer
and,
and
so
like
say,
the
ticker
of
the
nft
needs
to
follow
a
certain
pattern
to
identify
it
as
a
store.
A
So
that
way,
this
new
indexer
can
sort
of
ignore
all
slp
tokens,
except
for
the
ones
that
represent
stores,
and
then
these
claims
these
would
be
more
like
you
know
you
could
you
could
burn
psf
tokens,
so
you
could
take
a
utxo
that
represents
a
quantity
of
psf
tokens
and
then
burn
them
by
not
attaching
the
proper
op
return
to
it,
but
in
place
of
it
you
could
put
other
operating
data
that
the
indexer
could
pick
up
on,
and
so
that
would
be
one
way
of
implementing
a
claim,
so
it
would
be
on
the
blockchain
and
so
a
claim
would
be
about
either
a
store
or
another
claim.
A
So
this
is
how
you
could
leave
reviews
of
a
store
or
if,
if
say
it
was
a
negative
review
and
the
store
owner
wanted
to
respond
to
it,
they
could
make
a
claim
about
the
claim.
A
So
that's
so
that's
that's
kind
of
my
thinking
there
and
so
you're
the
you're
getting
the
data
on
the
blockchain
you're,
allowing
the
things
that
change
frequency
frequently
like
products
to
to
change.
That's
part
of
the
mutable
data,
however,
there's
an
append
only
you
know
history
there
on
the
blockchain
that
that
links
to
ipfs
content
and
and
now
you
can
make
sort
of
cl
you
can
claims
on
claims
and
and
ultimately,
in
terms
of
a
ui.
A
What
I
really
the
thing
that's
really
driving
my
imagination
here
is:
is
I
keep
going
back
to
craigslist
and
it's
a
little
more
cumbersome
today
because
they
have
more
captchas
and
stuff
to
prove,
but
it
used
to
be
just
take
a
picture,
add
a
title
and
a
price
and
you're
done,
and
so
I'm
trying
to
like
get
to
like
how
can
we
build
an
app?
That's
that
simple,
like
you,
just
take
a
picture,
a
title,
a
price
and
you're
done.
Everything
else
is
beyond
that
is
optional,
but
then
you
know
we.
A
We
really
got
to
worry
about
not
safe
for
work
stuff.
We
got
to
have
some
ability,
as
a
community,
to
police
the
content
or
not
police,
but
moderate
the
content.
So
it's
like
hey.
If
you
know,
if
five
people
have
marked
this
thing
as
not
safe
for
work,
it's
probably
not
safe
for
work
and
they
had
to
pay
something.
Even
it
was
a
penny
to
make
that
claim.
Then
then
yeah,
it's
probably
not
safe
for
work,
but
it
allows
sort
of
the
the
the
the
website
that's
serving.
A
The
content
can
make
those
decisions
and
people
can
choose
which
site
they're
going
to
go
to
to
consume
the
content,
so
it
makes
this
sort
of
moderation
as
a
service.
This
is
this
is
a
concept
that
I
I
find
right.
I've
been
following
I
find
rather
fascinating,
is
sort
of
this
very
gray
line
between
censorship
and
moderation
and-
and
you
know,
mo
censorship
as
something
that
somebody
does
to
you.
That's
out
of
your
control
versus
moderation.
A
That's
more
like
a
service
that
you
pay
for,
and
you,
if
you
don't
like
how
someone's
moderating
you
can
you
can
choose.
You
know
another
moderator,
so
so
a
lot
of
these
sort
of
squishy
ideas
trying
to
like
get
them
into
like
an
actual
quantitative
protocol
on
the
blockchain.
So
these
are
just
sort
of
some
of
my
ideas
and
then
I
threw
in
here
for
people
who
aren't
familiar
with
it.
There's
this
json
ld
or
linked
data,
and
it
it
and
probably
the
the
most
popular
implementation
of
it
is
schema.org
and
it's.
A
This
is
particularly
focused
on
stores
and
products
and
being
able
to
categorize
having
standardized
ways
to
describe
stores
and
products
in
their
interaction,
so
that
computers
can
sort
of
on
the
fly
figure
out,
get
get
get
context
and
be
like.
Oh,
this
data
is
a
product.
This
data
is
a
store.
The
state
is
a
user.
The
user
left
a
review
about
this
product
for
this
store,
and
so
like
the
computer
can
just
reason
about
those
things.
You
don't
have
to
explicitly
tell
it
these
things.
A
A
When
tim
berners-lee
about
two
decades
ago,
he
came
up
with
the
semantic
web
that
was
supposed
to
be
web3
and
then
that
and
then
the
ethereum
created
a
library
called
web3
and
that
so
that's
what
everybody
started,
calling
web3
and
so
now.
This
is
why
the
vcs
are
having
such
a
hard
time
explaining
web3,
because
their
the
original
conception
was
a
semantic
web.
A
A
But
anyways
those
are
just
some
ideas.
This
is
something
I'm
kind
of
cranking
on
in
the
background
as
I
try
and
work
through
the
the
deck
stuff
and
and
and
meet
our
obligations
with
that.
This
is
like
the
next
big
thing
I
really
wanna,
I
wanna
focus
on
and
the
more
I
think
about
it,
like
the
clearer.
These
ideas
are,
like
the
indexer,
that's
a
little
bit
of
work,
but
we
I
already
built
one.
So
it's
not
that
big
of
a
deal
to
fork
it
and
build
a
new
indexer.
A
You
know
the
the
schema.org
stuff's
all
there.
All
we
really
need
to
do
is
just
adopt
it
and,
and
then
it
really
just
leaves
stores
and
claims.
Those
are
really
like
the
only
two
things
that
really
need
to
be
figured
out
here.
C
A
I
can't
see
any
utility
there
for
it.
What
you
really
need
is
to
be
able
to
put
the
data
somewhere,
so
it's
immutable
and
censorship,
resistant
and-
and
so
the
indexer
can
pick
up
on
it.
A
Yeah,
just
like
a
memo,
dot
cash
entry
yeah-
it
really
could
be
that
simple
and
it
doesn't
need
to
involve
the
psf
token
at
all.
I
was
just
thinking
like
we
could
add
an
additional
constraint
where,
like
the
claim,
has
to
come
from
the
burning
of
some
quantity
of
psf
tokens,
you
know,
and
that
would
just
that
would
be
a
way
for
us
to
increase
our
cash
flow.
If
this
system
took
off
to
pay
for
infrastructure,
so
yeah
just
just
ideas
at
this
point
just
throwing
them
out
there.
E
I
I
like
the
idea
of
the
decentralized
craigslist
I
always
have.
I
think
all
these
things
we've
been
talking
about
are
working
working
on
are
kind
of
seeming
to
come
together
in
a
way
that's
gonna
be
cohesive
for
all
of
them.
A
Yeah
thanks
the
other.
The
other
inspiration
here
is
that
I
I
did
a
before
I
got
into
the
bitcoin
cash
basic
before
bitcoin
cash
existed,
I
spent
about
a
year
there
during
during
2017
doing
a
lot
of
work
with
the
open
bazaar
guys,
and
so
I
I
got
a
very
upfront
close
intimate
view
of
what
they
did
that
worked
really
well
and
what
they
did.
A
That
was
not
working
well,
and
I
think
one
of
the
things
that
at
that
time,
bitcoin
was
becoming
way
too
expensive
to
write
a
bunch
of
data
on
the
chain.
That's
why
they
didn't
do
it
that
way
they
took
a
fork
of
ipfs
and
they
created
like
a
private
ipfs
network
essentially,
and
that
didn't
work
very
well,
because
there's
all
these
issues
with
latency
and
availability,
and
you
know
so
there
there.
A
You
know
a
lot
of
these
issues
that
we're
going
to
deal
with,
and
so
this
is
why,
but
with
bitcoin
cash
and
the
ability
to
write
cheaply
to
the
chain
that
changes,
the
economics
and-
and
it
also
because
it's
on
the
blockchain.
Now
you
don't
have
the
availability
issues
that
you
would
have
with.
Ipfs,
because
it's
just
on
the
blockchain,
just
look
it
up
and-
and
I
think
originally
that's-
that's
sort
of
that
might
have
been.
A
B
Probably
to
mike
hearns
rage
quit
and
everything
else,
because
they
couldn't
scale
up.
I
mean
there's
a
lot
of
things
that
happened
after
that
that
put
us
on
this
spot.
So.
A
Yeah
yeah,
but
yeah,
you
know,
I
think
this
is
this.
This
is
a
use
case
where
our
hybrid
approach,
the
bulk
of
the
content,
goes
on
ipfs,
but
you
use
like
pointers
on
the
blockchain,
to
sort
of
organize
everything.
A
So
it's
small
and
efficient
you're
using
the
blockchain
efficiently,
but
also
a
big
key
part
of
that
is
having
no
transaction
fees,
so
I
think
I
think
that's
kind
of
the
sweet
spot
I'll,
just
open
it
up.
If
anybody
wants
to
talk
about
anything
else
before
we
wrap
this
up,
go
for
it.
D
A
Yeah,
it's
almost
like
in
these
bear
markets.
A
It's
you
know,
there's
so
much
building
going
on
that,
it's
almost
harder
to
follow,
because
you
know
during
the
bull
markets,
you're
you're
trying
at
least
I'm
I'm
trying
to
like
not
be
distracted
by
all
the
all
the
hoopla
and
and
just
keep
building,
but
now
now
everybody's
building,
because
there's
nothing
else
to
do.
Yeah.
D
A
D
I
hear
interesting
like
clarification
that
there's
the
two
like
now
when
we
are
not
in
the
bull
market.
We
build
market
yeah.
B
C
Yeah
I've
been
playing
with
web
assembly,
so
I
this
was,
I
think,
maybe
a
month
ago
I
was
having
a
hard
time
trying
to
figure
out
how
to
use.
I
guess
node
modules
on
the
front
end,
so
you
have
to
do
this
like
browserify
thing,
and
basically
I
was
trying
to
figure
out
how
to
how.
How
do
you
make?
C
How
do
you,
how
to
use
a
mnemonic
library-
and
I
kept
running
it's
basically,
I
I
found
this-
I
found
it
easier
to
use
web
assembly
than
doing
the
whole
common
js
to,
and
I
guess
the
whole
javascript
like
the
module
system
was
like
there's
like
this
whole
thing.
Where
you
have
to
there's
esm.
I
guess
the
module
system
is
kind.
A
Of
weird
common
js
and
esm
well,
yeah
how's
that
I've
never
really
dipped
my
toe
into
the
wasm
waters
like
what
how's
that
workflow
work.
So
you
can
write
you're,
saying
you're,
writing
something
in
node.js,
compiling
it
to
wasm,
and
then
you
can
access
it
in
the
browser.
C
Well,
basically,
there
is
you,
can
use
assembly,
script
and
rust
and
go
to
and
then,
if
you
can
compile
those
modules
using
web
to
webassembly,
which
is
then
webassembly
of
modules.
You
just
converted,
I
think,
to
just
javascript.
So
I
got
it.
I
got
a
mnemonic,
so
I
wanted
to
see
if
I
could
just
use
a
light
library
just
to
make
an
I'm
learning
the
whole
process
of
how
a
mnemonic,
how
you
get
a
mnemonic
to
a
seed
and
then
all.
C
And
yeah
yeah,
just
I
found
the
webassembly
workflow
just
to
be
a
little
simpler
than
than
going
from
common
js
to
esm
and.
D
This
web
assembly
is
like
very,
very
hot
topic.
I
think
most
of
the
recent
worlds.
Nice
projects
are
based
on
something
named
kozum
asam,
which
is
like
hot
c,
the
the
initial
cosmos,
this
atom
based
blockchains.
They
have
a
very
nice
like
underlying
structure,
but
they
separated
the
consensus
in
the
state.
So
you
have
like
a
pretty
hot
c
basic
layer
which
will
how
to
see
propagate
all
the
transactions,
but
you
can
put
every
state
on
top
of
this,
so
it
can
be.
D
You
can
propagate,
for
example,
the
the
state
of
the
traffic
lights.
Is
it
red
light
or
something?
So
you
can
have
this
kind
of
custom
application
on
top
and
you
can
use
the
underlying
structure,
but
it
was
like
nothing.
It
was
too
basic,
so
they
pretty
much
created
this
kozum
asm
project
which
allow
you
like
some
mentioned
in
some
programming
language,
which
is
pretty
much
rust
or
go
or
a
script.
D
D
So
you
can
create
them
for
many
blockchains,
so
all
of
the
cause,
all
of
the
cosmos
blockchain
like
including
the
our
friend
terra
luna
and
like
near
protocol
also
they
does
not
use
cosmos,
but
their
whole
system
is
based
on
this
cosmosome
like
a
web
assembler.
So
it's
very
exciting
topic
because
in
the
usual
evms,
when
you
create
some
blob
like
some,
you
compile
something
it's
in
some
format.
You
don't
know
what
is
inside,
like
it
there's
some
format,
but
it's
not
very
standard,
but
this
like
cosm.
Wasn't
it
standardized
everything?
D
D
If
you
know
them
evm
os,
you
can
see
they're
the
only
token
which
is
pumping
the
last
two
weeks.
It's
like
green
all
every
day
it
was
on
the
I
think,
half
of
the
door,
and
now
it's
like
three
dollars
already
during
this
bear
market
so
yeah
they.
They
have
an
interesting
concept.
When
you
create
account,
you
have
two
addresses:
one
is
in
the
cosmos
ecosystem.
E
C
One
of
one
of
the
things
I've
seen
was
about
web
assemblies.
It's
supposed
to
be
really
performant,
so
somebody
was
able
to
like
run
an
entire
operating
system
on
in
the
browser,
and
then
they
ran
they
had.
I
forgot,
which
one
I
think
was
windows
95
running
inside
the
browser,
and
then
they
had
like
netscape
and
then
netscape
was
running
chrome,
and
that
was
weird.
It
was
like.
It
was
crazy.
B
C
To
you
know,
you're
not
supposed
to
be
able
to
run
something
like
that.
You
can.
You
can
play
now.
You
can
play
like
3d
like
doom,
like
high
performance
games
in
in
the
browser.
A
So
yeah
they're,
I
I'm
a
little
conflicted
on
web
assembly
and
web
components.
So
if
you
in
it,
I
can't
really
tell
this
without
going
back
to
the
history.
So
there
was
tim.
Berners-Lee
started
the
the
the
w3c,
which
is
like
the
standards
body
for
for
creating
web
standards,
and
you
know
that's
how
we
got
html
and
xml
and
just
a
lot
of
the
the
base
technologies.
But
then,
once
microsoft
got
into
the
game
and
then
google
these
like
behemoths,
they
were
they.
A
They
were
so
big
that
they
were
able
to
be.
Like
you
know,
if
the
stamp,
if
they
liked
the
standard,
then
it
was
fine,
but
if
they
didn't
like
the
standard,
they
just
wouldn't
implement
it.
And
then
you
know
they
they
just
had
way
too
much
influence
and
that
they
could
just
be
they
could
just
veto,
they
could
just
veto
a
standard,
and
so
it
really
changed.
A
D
A
So
then
there
was
facebook
and
they
created
react
and
react.
Just
like
you
know
has
dominated.
I
mean
you
compared
to
like
vue
or
angular
like
yeah.
They
exist,
but
but
react
is
just
has
way
more
market
share
and
and
so
then
the
w3c
created
web
components,
which
is
like
that.
That's
what
react
introduced.
It
was
this
idea
of
like
let's,
let's
make
everything
a
component.
All
these
lego
blocks.
A
That's
what
a
web
app
is
you're,
just
putting
all
these
components
together,
and
so
the
web
w3c
came
up
with
web
components
and
a
lot
of
people
were
like.
Oh,
this
is
going
to
change
everything.
We
don't
need
react
anymore
because
it's
like
conception,
conceptual
things
like
natively
baked
into
a
browser,
but
it
never
went
anywhere
like
I
every
once
in
a
while.
I
hear
somebody's
talk
about
web
components
and
it's
like
nobody
uses
it.
Everybody
still
uses
react
and
then
webassembly
is
like
similar.
It's
like
it's
like.
A
They
came
up
with
this
really
nice
standard
and
everybody
liked
it.
It
was
great,
except,
like
I
just
haven't,
seen
the
adoption
you
get
these
pockets
and
where
I've
seen
webassembly
really
get
popular
is
non-javascript
programming
languages
because
they
they
need
some
way
to
write
code
and
go
or
rust
and
then
have
it
run
in
the
web.
A
Browser
and
webassembly
is
apparently
the
way
to
do
it,
but
I'm
still
I
like
so
I
don't
know
if
web
assembly
is
gonna,
be
like
web
components
or
if
it's
actually
going
to
take
off
and
right
now
I
just
I
don't
know
I
don't
I
I
I
see
a
lot
of
growth
in
these
little
niches,
but
I
don't
see
like
really
wide
adoption
yet
of
web
assembly.
A
D
Pretty
wild,
but
you
can
think
about
it
like
how
to
see
it's
the
same.
Like
java,
you,
you
don't
compile
directly
to
binary
code.
You
first
create
some
like
something
in
the
middle
all
programming
languages,
have
it
its
name
like
p
code
or
something
something.
So
you
create
some
kind
of
pseudo,
very
simple
assembler
and
it's
then
compiled
to
binary
code.
So
one
thing
is
just
this:
one:
there's
nothing
to
do
with
the
browsers
or
with
whatever
this
browser
is
just
one
environment
where
this
can
be
run,
but
it's
pretty.
D
F
A
Okay,
guys
well,
it's
been
we're,
get
getting
close
to
an
hour
and
a
half.
Let's
go
ahead
and
wrap
this
up.
It's
been
a
good
meeting,
really
liked,
seeing
what
you
guys
were
all
doing.
I
I
want
to
do
more
of
that,
like
you
know,
if
you
guys
are
doing
stuff
you're
excited
about,
I
want
to
open
this
up
as
a
platform
for
you
guys
to
to
show
and
tell
so
thank
you
aaron
for
for
your
for
demo
and
your
your
exchange.
B
E
B
I'm
excited
about.
I
love
the
fact
that
the
technology
to
integrate
to
interact
with
the
blockchain
is
built
in
the
psf's
handling
that
stuff,
because
that's
stuff,
I
would
not
be
able
to
do,
and
I
would
have
spent
ever
forever
just
getting
to
that
spot.
So,
thanks
to
the
psf
and
all
of
you
from
for
making
that
possible
and
everyone's
responded
throughout.
D
Just
can
I
just
mention
something
I
think
with
aaron
we
were
trying
friday
to
do
multisick
stuff
with
psf
wallet.
So
do
you
have
some
advice
chris,
where
we
can
go
to
to
do
this
stuff.
A
Yeah,
it's
pretty
rough,
that's
pretty
ambitious,
but
but
really
there's
those
those
two
there's
that
fork
of
psf
cly
wallet
and
it
has
two
commands.
You
know
one
one
was
intended
to
be
run
by
all
participants
and
one
is
run
by
the
aggregator,
and
so
I
would
say
just
study
those
commands.
The
multi-sig
is
super
rough
because,
like
ideally,
what
you
would
do
is
each
person
would
just
sign
a
message,
but
I
couldn't
figure
out
how
to
do
it.
That
way.
A
A
So
it's
it's
not
ideal
and
it's
a
struggle
because
I'm
trying
to
combine
bit
core
with
bchjs
they're,
both
forked
from
the
original
from
an
original
product
project,
but
they
both
like
signed
like
evolved
significantly
differently
and
so,
and
so
because
I'm
trying
to
do
an
slp
transaction,
a
multi-sig,
slp
transaction,
I'm
using
bch
jas
to
create
a
transaction
with
only
an
op
return,
because
bit
core
will
will
not
work
with
slp
tokens.
A
And
so
I
have
this
like
it's
a
partial
transaction.
It
just
has
one
output
which
is
not
returned.
I
pass
that
into
bit
core
and
then
bit
core
adds
the
pay-to-script
hash,
multi-sig
inputs
and
outputs
and
and
then
and
then
I
think
I
finally
I
broadcast
it
with
bchjs.
A
So
it's
it's
it's
not
there.
I
mean,
like
there's
a
lot
of
there's
a
lot
of
there's
a
lot
of
problems
with
it.
It's
just
it's
like
a
proof
of
concept.
It
barely
works,
but
yeah
I'd
love
to
have
more
eyeballs
on
it,
but
don't
expect
to
be
impressed.
E
D
E
A
But
yeah
I
mean
this
this.
That
code,
though,
is
like
our
whole
minting
council
is
gonna,
be
it's
either
going
to
exist
or
not
exist
based
on
that
code,
so
I
would
love
to
have
you
take
a
look
at
it?
Stoian
and
you
know
I
the
we
can
push
forward
with
the
code
as
it
is,
but
it
would
just
be
way
better
if
people
didn't
actually
have
to
send
their
private
keys
to
the
aggregator
if
they
could
actually
just
sign
a
message
and
that
should
be
possible
with
the
bit
core
code.
A
C
You
can
mint
with
cash
script,
but
that's
a
whole
other
thing
itself.
I've
been
playing
with
cash
script
a
little
bit.
I
made
this
little.
I
was
playing
with
this
app
where
it
creates
three
hashes
and
and
then
you
set
some
conditions
and
it's
been
pretty
it's
interesting
to
to
play
with
it's
really
really
like.
C
C
If
you,
if
you
go
to
the
the
docs,
there
is
a
minting,
you
could
set
a
condition
whatever
you
want.
Whatever
that
condition
you
know
you
can
set,
you
know
time
locks
or
these
many
addresses
or
but
there
is
a
mint
of,
I
know,
there's
a
slp
output
option
as
a
as
a
when
you
when
you
want
to
spend
from
the
contract
or
you
want
to
you,
know
broadcast.
A
C
D
A
Yeah,
that
would
be
a
much
cleaner
way
to
do
it,
because
all
I'm
using
bitcore4
is
to
create
the
the
paida
script,
hash
multi-sig
stuff,
so
cache
script
has
all
that,
and
so,
if
yeah
I
just
the
big
core.
Had
these
really
nice
examples,
I
was
able
to
hack
on
so
that's
why
I
went
with
that
route,
but
cash
script
would
be
a
much
more
native,
better
native
and
yeah.
I
need
I
need
to
look
into
that.
I'd
love
for
us
to
collectively
look
into
that.
D
Sure,
if
it's
needed,
because
it's
just
a
hot
sea
high
level
language,
but
it's
finally
compiled
to
these
op
codes,
which
are
put
inside
the
the
utxo
and
for
our
case
it's
pretty
simple-
you
just
put.
If
you
remember,
we
was
talking
before
it's
a
very
simple
format:
web
zero,
something
something
something
so
you
don't
need.
Maybe
cash
script
for
all
of
this.
A
Yeah
yeah
yeah,
I
mean
at
the
end
of
the
day,
you're
you're
you've
got
to
have
a
transaction
that
has
the
pay
to
script
hash
code
for
multisig
and
then
has
the
first
output
is
an
op
return
that
follows
the
slp
spec
and
that's
like
you
that
there's
those
those
two
components,
the
the
pay
script
hash
and
the
op
return
like
you
got
to
put
those
together
in
the
same
transaction.
That's
the
hard
part!
That's
that's
why
I
ended
up
having
to
like
cluj
together
different
parts
of
bitcoin
bchjs.
A
So
if
we
could
replace
the
bit
core
portion
with
cash
script
or
just
just
a
template,
that's
really
all
we
need
is
just
this
operator
or
the
the
script
template
is,
is
what
we
need,
and
so
that
could
either
come
from
bit
core
or
cash
script,
or
we
could
write
our
own
yeah.
So
there's
a
lot
of
room
for
refinement
there,
and
this
is
what
I'm
like.
A
And
then
the
minting
council
is
meeting
every
three
months
to
set
the
price
of
the
psf
token
and
and
manage
some
of
our
other
infrastructure.
Then
then
you
know
we
got
the
ball
rolling
and
and
we
can
always
improve
and
iterate
from
there.
A
Yeah,
probably
good
spot
to
wrap
it
up,
guys,
really
appreciate
you
making
time
and
yeah,
I
loved
loved
hearing
your
ideas
and
getting
your
input
today
thanks
everybody.