►
From YouTube: PSF TC Meeting 6.9.21
Description
Technical Steering Committee Meeting for June 9, 2021
A
A
C
D
C
All
right,
thank
you,
aaron
for
all
these
neat
graphics.
This
is
the
permissionless
software
foundation's
technical
steering
committee.
It
is
june
9th
2021,
and
the
purpose
of
this
meeting
is
just
to
cover
the
the
technical
aspects
and
accomplishments
that
we've
achieved
over
the
last
couple
weeks.
Let's
get
started
with
a
round
of
introductions.
I'll
start,
my
name
is
chris
troutner
I've.
I
helped
found
the
ps
foundation
of
the
permission,
software
foundation
with
with
a
few
people,
and
I
also
manage
fullstack.cash.
E
C
D
D
C
C
That's
telegram
there
we
go.
This
is
the
agenda
for
today.
As
always,
you
can
find
the
agenda
in
the
permissionless
software
foundation,
github
group
in
tsc
that
stands
for
technical
steering
committee
repository
and
then
we
file
the
agendas
as
issues.
So
all
the
old
agendas
are
there
they're.
Just
the
issue
has
been
closed,
so
they're
archived
but
everything's
there,
and
so
in
our
current
stage
of
growth.
These
meetings
are
really
all
about
celebrating
the
accomplishments
that
we've
achieved
in
between
the
meetings.
C
C
C
So
the
content
in
these
sections
are
relatively
there's
not
a
lot
there.
Yet
I'm
going
to
be
adding
more
content
over
the
next
couple
weeks,
but
the
intent
of
these
new
sections
is
for
developers
to
quickly
find
the
tools
that
are
of
most
interest
to
them
and
and
and
come
up
to
speed
on
them.
So
if
you're
a
front-end
developer,
you
can
go
to
the
front-end
section.
C
You
know
the
cache
stack,
how
to
set
up
full
nodes
and
indexers
how
to
run
some
of
the
command
line
apps
for
for
for
sending
transactions
using
the
different
blockchains
and
then,
if
you're,
a
library
developer
that
that
section
is
gonna
cover
a
lot
of
the
middleware
libraries
that
we've
developed,
as
well
as
testing
practices
and
and
just
just
best
practices
for
for
for
library
developers
and
and
sort
of
our
our
approach
to
it.
In
fullstack.cache.
C
B
B
D
I
like
the
idea
of
the
front
and
the
back
in
the
library.
This
is
something
we're
talking
about
with
this
development
program
and
we're.
We
are
interested
in
people
that
want
to
learn,
crypto
and
learn
and
program
it.
So
if
you
have
some
html
knowledge,
some
css
knowledge
and
some
javascript
knowledge,
please
get
in
touch
with
us,
because
we'd
like
to
talk
with
you
and
we're
going
to
be
developing
this
program
over
the
coming
months
and
hope
to
launch
it
sometime
in
the
fall
is,
is
my
hope.
I
don't
know
about
you.
D
C
D
C
C
C
Okay,
can
you
guys
hear
me
yeah?
Yes,
okay,
great,
I
keep
accidentally
meeting
myself.
The
front
end
page
has
a
youtube
video
that
shows
how
to
very
quickly
fork,
wallet.fullstack.cache
and
start
building
your
own
apps
and
I'm
planning
to
create
another
video
to
complement
this
one
specifically
on
our
plug-in
architecture.
The
approach
that
we
take
with
the
front-end
wallet
is
anything
that
can
be
a
plug-in
should
be
a
plug-in.
It's
very
modular
like
lego
blocks
and
so
right
now.
C
This
tech,
the
the
backend
area,
focuses
on
that
lower
half
of
the
cash
stack
as
well
as
some
of
the
more
command
line
based
applications,
and
so
it
goes
into
a
lot
of
that.
That
sort
of
what
would
be
considered
core
infrastructure
for
building
a
building,
a
a
cryptocurrency
app
and
then
finally,
the
the
javascript
library
focuses,
or
the
library
section
focuses
on
that
that
middleware,
which
is
typically
javascript
in
this
paradigm
and
and
just
cover
some
of
the
the
most
important
libraries
right
now.
C
It
calls
out
slp
cly
wallet
the
next
library
I'm
going
to
get
up.
There
is
avex
clie
wallet,
so
it's
the
same
exact
interface,
but
one
is
on
the
avalanche,
blockchain
one's
on
the
bitcoin
cash
blockchain
and
we
have
a
series
of
other
libraries,
one
of
which
I'm
going
to
talk
about
in
a
minute
like
for
calculating
merit,
scores
and
doing
end-to-end
encryption
so
anyways,
that's
that
is
what's
new
on
fullstack.cache,
so
I
really
would
love
to
get
some
feedback
from
people
in
the
permissionless
software
telegram
channel.
D
Go
ahead
and
that's
at
a
chat.fullstack
chat.fullstack.cash,
you
can
see
that
down
below
or
sorry
fullstack
dot
cash
I'm
off
today,
so
we're
going
to
get
to
chat.fullstack.cash
in
a
little
bit.
So.
But
if
you
guys
look
at
the
bottom
of
the
screen,
you
can
see
the
web
address
check
it
out.
Please
do
get
in
touch
with
us.
We
really
are
interested
in
working
with
people
in
the
community
and
developing
these
products.
C
We
use
the
token
liquidity
app
to
maintain
liquidity
between
the
psf
token
and
bitcoin
cash,
and
what
we're
preparing
to
do
is
launch
the
token
liquidity
app
on
the
ecash
blockchain,
as
well
as
the
avalanche
blockchain,
and
we're
going
to
do
this
shortly
after
we
launch
our
token
bridge.
So
the
idea
is
that
you
have
one
psf
token
that
you
can
transfer
across
blockchains
and
then
exchange
for
the
reserve
currency
on
that
blockchain.
C
So
the
we're
not
there
yet,
but
the
the
accomplishments
we've
achieved
in
the
last
couple
weeks
is
just
better
debugging
and
email
alerts.
We
now
have
it
set
up
where
anyone
who
wants
to
set
up
a
token
liquidity
app
for
their
own
token,
everything
you
need
to
customize
the
the
app
is
in
one
file,
it's
a
a
dot
env
file
and
a
file
which
lets
you
set
all
the
environment
variables
to
customize
the
app
for
your
token.
C
D
C
The
next
thing
on
the
agenda
is
the
fulcrum
api,
so
this
is.
This
speaks
again
directly
to
the
core
psf
software
and
if
I
bring
up
fullstack.cache
you'll
see
that
there
is
this,
the
cash
stack
and
one
of
this
electrum
x
block
is
the
the
fulcrum
indexer.
That's
what
provides
address,
balances
and
utxo
information
for
an
address.
C
Those
are
like
the
two
critical
pieces
of
information
that
the
indexer
provides
that
the
full
node
does
not
provide
and
is
required
to
do
any
sort
of
wallet
functionality
and
when
this
was
originally
developed
for
fulcrum,
it
has
this
sort
of
really
weird
way
that
it's
networked
and
as
fullstack.cache
increases
the
volume
that
the
quantity
of
api
calls
per
day
as
it
increases.
We
need
to
scale
horizontally
and
we
ran
into
an
issue
with
scaling
horizontally
with
the
existing
fulcrum
docker
container,
the
way
it
was
built.
C
So
this
is
just
some
tweaks
and
this
is
actually
a
really
good
segue
into
the
next.
The
next
agenda
item
here
and
we
have
created
a
new
v5
route.
V4
is
the
standard
route
that
bchjs
uses
and
that
everybody
should
be
using
right
now,
because
it's
the
only
functional
route,
we
created
a
new
v5
route
and
in
the
next
week
or
two
we
will
start
to
transition
bchjs
to
this
new
v5
route
and
there's
two
big
changes
to
the
v5
route.
C
The
first
one
is
replacing
the
old
fulcrum
calls
with
the
new
fulcrum
calls
to
fulcrum
api.
So
before
again
going
it
helps
to
look
at
this
cache
deck.
The
rest
api
would
call
and
talk
to
the
fulcrum
indexer
directly.
Now
what
happens
is
the
fulcrum.
Indexer
is
in
its
own
docker
container,
and
it's
orchestrated
with
a
second
docker
constant
container.
That
is
a
dedicated
api,
and
so
by
that
that
was
the
missing
piece
is
by
combining
a
rest
api
with
the
fulcrum
indexer
together
in
one
package.
C
We
can
now
scale
that
horizontally
and-
and
it
also
fixes
a
few
networking
issues
that
we
were
having
with
the
there.
We
go
with
bch
api.
So
so
it's
it's.
It's
kind
of
a
minor
tweak.
If
you're
using
bch
jas,
you
won't
even
know
notice
that
anything
changed
it's
only
if
you're
running
bch
api
is
sort
of
a
little
tweak
and
it
it
did
require
a
a
version
change
to
the
route
and
the
other
big
feature
that
we're
adding
is
the
double
spend
proof.
C
So
this
is
a
new
feature
on
the
bch
and
full
nodes
and
there's
a
couple
other
full
notes
that
support
it
as
well,
but
we
mostly
focus
on
whatever
full
node
the
miners
run,
which
is
bchn,
and
this
allows
you
to
essentially
if
someone
tries
to
double
spend,
which
is
a
let's
take
a
minute
to
talk
about
double
spending
here.
Double
spending
is
a
very
difficult
thing
to
do.
C
C
C
This
is
a
step
in
the
direction
of
making
secure,
zero
comp
transactions,
and
so
when
a
full
node
detects
a
double
spend,
it
will
generate
a
a
double
spend
proof,
and
this
is
the
new
feature
that
just
went
into
the
the
full,
the
bchn
full
node
a
few
months
ago,
and
there
there
are
no
libraries
that
I'm
aware
of
that.
That
leverage
this
new
rpc
call.
C
Let
people
deliberately
generate
double
spends
and
what
you'll
see
is
one
of
them
will
return
a
value
at
from
this
rpc
call,
which
is
the
proof
saying
like
this,
is
not
a
valid
transaction.
This
this
is
the
double
spend
it
like.
The
full
node
will
decide
which
one
is
legitimate
and
which
one
is
not
legitimate,
and
so
the
use
case
here
so
that
I
probably
should
have
started
with
the
use
case
rather
than
going
right
into
the
technical
things.
C
C
I
I
don't
know
if
this
is
like
the
silver
bullet
to
make
secure
zero
comp,
there's
a
lot
of
doubt
about
that.
But
this
is
a
new
feature.
It
will
probably
work
90
of
the
time
or
more
probably
more
than
90,
but
it'll
probably
cover
90
of
the
use
cases.
So
it's
definitely
something
that
I'm
excited
to
support
and
I'm
excited
to
see
you.
You
know
we
just
need
to
start
playing
with
it
and
and
sort
of.
C
If
there
is
a
security
issue
with
these,
we
need
to
start
exploring
that
and
we
need
to
see.
We
need
to
sort
of
open
the
door
in
little
ways
to
malicious
actors
to
try
and
really
put
this
to
the
test.
That's
just
sort
of
where
the
network
is
at
right
now,
so
we're
gonna
see.
So
it's
it's.
A
big
warning
like
this
is
cool
tech.
It's
also
brand
new.
No,
everyone
should
not
start
doing
zero
comp,
assuming
that
this
is
secure,
but
if
you're
a
developer.
D
You
heard
them
people
all
you,
hackers
and
malicious
out
actors
out
there
come
on
down
and
play
with
our
tech
and
see
if
you
can
break
it,
and
so
what
you're
talking
about
here
is
getting
us
closer
to
that
that
that
goal
of
zero
confirmation,
essentially
and
which
would
help
because
I
mean
you're
a
retailer,
say
you
run
things
wrong.
You
know
you
could
double
spend
some
of
these
coins
that
wouldn't
necessarily
be
a
malicious
thing,
but
you
I
could
see
retailers
firing
that
off
really
quickly
I've.
D
C
Thanks
man
yeah,
I'm
excited
to
see
how
it
plays
out.
I'm
cautiously
optimistic
it.
You
know,
in
the
case
of
like
a
buying
a
coffee
you're
not
like
you're
you're,
really
just
doing
one
transaction,
and
you
know
someone's
not
going
to
exploit
that.
I
think
that's
like
a
perfect
application
for
this
technology
in.
C
Liquidity
app,
you
know,
that's
more
of
an
automated
app,
so
if
someone
found
an
exploit,
they
could
just
be
sitting
there
running
the
exploit
and-
and
we
wouldn't
really
know
unless
we,
you
know-
got
an
email
from
the
app
or
checked
on
it.
And
so
that's
why
I'm
a
little,
I'm
probably
not
going
to
implement
this
right
away
in
into
something
like
the
token
liquidity
app.
So
people
have
to
be
really
careful
about
the
use
case.
D
C
D
C
C
This
is
actually
up
on
chat.fullstack.cache.
If
anybody
wants
to
play
with
it
and
what
it
is,
is
it's
the
peer-to-peer
database
and
right
now
there's
only
one
of
them.
I
just
discovered
a
bug.
Today
I
was
trying
to
replicate
the
data,
but
the
whole
idea
behind
it
is
it's
supposed
to
be
peer-to-peer
so
like
a
blockchain,
everyone
can
can
run
their
own
instance
of
the
database
and
and
in
order
to
write
to
the
database,
you
have
to
submit
a
proof
of
burn.
C
C
C
C
It's
only
like
two
or
three
entries
right
now,
so
it's
it's
at
a
place
where
people
can
very
tentatively
start
dipping
their
toe
in
the
water
and
playing
with
it
and
and
like
I
said
there
is
a
bug
right
now.
If
you
try
to
replicate,
it
won't
replicate
properly,
or
at
least
there's
there's
something
weird
going
on
there.
D
Yeah
so
tell
me
this:
I'm
interested
in
hearing
a
little
bit
more
about
this,
this
data
problem
with
the
blockchain,
because
I'm
I'm
seeing
the
same
things
as
you.
You
know
there's
this
concern
about
writing
data
to
the
blockchain,
and
I
do
like
this
idea
of
pay
to
write.
You
can
run
your
own
database
that
sort
of
thing,
so
one
of
my
questions
is
definitely
well
if
you
could
expand
upon
a
little
bit
the
problem
with
writing
data
to
the
blockchain
and
two,
this
idea
of
pay
to
write
databases.
C
D
C
That
technology,
that
can
enable
decentralized
vpns
that
could
that
could
allow
your
computer
to
talk
to
a
vpn
service
and
on
the
fly,
negotiate
the
vpn
service
and
pay
for
it
and
and
you'd
be
able
to
do
that
with
any
computer
in
the
world
and
and
it
would
eliminate
all
the
sort
of
networking
headache
that
is
typically
associated
with
that
yeah
and
so
yeah.
So
that's
so
so.
There's
there's
two
technologies
here:
there's
the
json
rpc
over
ipfs,
which
is
a
replacement
for
the
rest
api
and.
C
D
Well,
I
see
other
things
for
the
paid
right,
say:
okay,
say
I'm
a
manufacturing
company
right,
there's
a
big
push
for
manufacturing
companies
to
move
to
vpns
the
problem
being
a
lot
of
the
networking
they
would
use
or
the
cloud
services
are
run
by
big
companies
like
amazon
and
google.
Now,
if
I
am
a
big,
I
have
intellectual
property
and
I'm
this
manufacturing
company-
and
you
know
I
make
widgets.
C
That's
a
good
tee
up
for
some
of
it
for
some
of
the
problems
that
it
solves,
because
it
what
this
solves
is
a
bunch
of
small
problems.
But
when
you
add
them
all
up,
they
become
a
big
problem.
So
there's
a
lot
of
interest
right
now
around
using
the
blockchain
to
record
data
and
and
people
are
starting
to
wise
up
that
like
okay,
well,
clearly,
it's
it's
starting
to
become
just
well
accepted
that
putting
the
the
actual
content
on
the
blockchain
is
a
bad
idea.
C
D
C
And-
and
so
people
are
starting
to
to
get
up
on
that,
but
even
if
that
was
to
achieve
mass
adoption,
even
that
efficient
way
of
doing
it,
would
would
still
like
incredibly
bloat
the
the
size
of
the
blockchain
and
that's
not
necessarily
a
problem
to
some
people,
because
because
it's
just
the
size
of
the
blockchain,
it
doesn't
affect
the
actual
like
a
transaction
capability
once
once
you
get
a
full
node,
synced
and
and
people
think
like.
Oh,
I
can
buy
a
hundred
dollar.
C
You
know
hard
drive,
four
terabyte
hard
drive
from
amazon
and
like
what's
the
problem
right.
Well,
the
problem
there's
a
couple
problems.
The
first
problem
is
the
ibd
or
initial
block
download
when
you
sync
a
full
node
and
bring
it
to
the
network
for
the
first
time
you
have
to
download
and
process
all
the
data.
That's
ever
been
put
on
the
blockchain
ever
and-
and
this
is
that's
the
big
it's
it's
not
the
amount
of
storage
space
it
takes
on
the
hard
drive.
That's
the
problem.
It's
the
amount
of
time.
C
C
You
know
I
have,
I
have
my
own
solution,
so
I
haven't
had
to
do
it
in
a
long
time
and
it
also
is
greatly
dependent
on
your
hardware
and
your
and
your
network
speed.
So
if
you'd
like
a
fiber
optic
connection
with
the
top
of
the
line
and
hardware,
it
might
only
take
two
or
three
days,
but
if
you're
a
normal
person
on
a
normal
home
internet
connection
with
a
normal
laptop,
it's
probably
gonna.
Take
you
two
or
three
weeks.
D
C
So
you
have
to
download
it.
You
have
to
unzip
it
and
then
mount
it
with
the
docker
container
and
then
sync
from
where
that
snapshot
was
so
it
reduces
that
time
down
to
two
or
three
hours
depending
on
your
hardware.
But
you
know
that
that's
and
that's
might
be.
Okay.
You
know
in
in
the
case
of
fullstack.cash,
we're
we're
spinning
up
and
spinning
down
infrastructure
for
people.
So
that's
actually
an
onerous
amount
of
time
to
be
able
to
do
that.
D
E
I
think
the
problems
that
iran
was
talking
about
and
this
tools
a
little
hard
to
see
not
exactly
about
the
the
privacy
and
encryption
because
how
to
see
the
the
problem
that
you
have
with
amazon.
You
can
make
end-to-end
decrypt
encryption,
but
this
is
not
the
point
of
this
json
rpcs,
it's
more
about
the
to
not
have
a
central
point.
So
yeah.
E
So
the
people
trying
how
to
see
to
to
put
the
small
pieces
of
data
inside
like
many
many
many
many
transactions
just
to
save
them
own
chain,
which
is
well
okay,
but
not
so
good
solution
and
there
can
be
something
off
chain
like
this
example.
This,
for
example,
pay
to
write
database
ipfs,
anything
anything
where
you
can
keep
all
of
your
data
in
secure
way
like
secure
mean.
E
D
D
B
E
But
I
mean
it
will
be
fast
right,
but
it
will
be
like
really.
You
will
do
this
one,
but
the
people
really
trying
to
do
this.
With
the
data
on
the
blockchain,
we
were
talking
about
putting
the
how
to
see
the
huge
images
on
the
blockchain
so
well.
They
would
destroy
the
image
on
the
small
op
return
200
by
transactions
put
them
on
chain,
and
after
this
they
will
need
to
again
make
the
whole
picture
from
this
stuff.
E
E
Yeah-
and
I
know
that
the
people
who
are
like
want
to
to
make
a
fast
payments,
they're
pissed
off
from
this
one-
really
I
will
just
need
to
pass
two
gigabytes
of
transactions
with
like
images
just
so.
My
like
payment
transaction
can
go
very
long
going
discussion.
I
think
yeah.
It
will
continue.
Maybe
until
we
find
some
good
solutions.
C
So
there's
there's
a
half
a
dozen
little
little
infrastructural
issues
that
I
think
that
this
this
architecture
solves,
but
I'm,
I
think,
the
the
the
new
applications
that
it
opens
are
much
sexier.
So
just
just
to
talk
about
those
for
a
minute.
Oh
yeah
well
get
ready
one
of
the
ways
I
I
hope
to
see
this
database
used
in
the
future,
as
is
as
a
cross
block
chain,
communication
medium
and
a
cross
block
chain.
Token
medium.
C
You
can
burn
a
token
on
one
chain
to
upload?
Some
content
and
then
read
that
content
from
any
other
chain
on
chain
and
and
upload
data
from
the
other
chain,
so
it
will
allow
blockchains
to
communicate
across
chain
and
I've
actually
had
a
short
conversation
with
andrew
stone
from
bu
about
how
this
could
be
used
to
set
up
oracles
the
cross
chain.
Oracles
and
so
that's
a
mind
blow
right
there.
But
before
we
go
too
deep
into
those
weeds.
C
The
other
application
that
I'm
hoping
to
see
on
this
is
I'd
like
to
port
the
slp
token
specification
to
the
database
so
that
the
the
tokens
rather
than
being
on
a
blockchain,
actually
live
in
the
database.
So
then
you'll
have
a
cross
block
chain
token
standard,
so
it
doesn't
matter
which
blockchain
you're
on
you're
gonna
be
interacting
with
the
same
token,
and
that
would
that
would
essentially
let
businesses
create
their
own
token
and
then
and
then
they
just
don't
even
have
to
think
about
the
blockchain.
D
D
Dude,
that
is
pretty
cool
and
so
being
able
to
move
between
block
chains
for
people
that
don't
know
about
this,
which,
if
you're
watching
this,
I
don't
know
why
you
don't
know.
But
if
you
don't
know,
this
is
a
great
great
thing
that
we've
been
trying
to
work
on
in
the
space
for
a
long
time,
and
I
like
the
idea
that
it
can
be
used
as
an
oracle.
That's
that's
awesome
and
people
can
write
to
it
from
many
different
chains.
I
mean
the
applications
are
going
to
be
huge
in
this
sort
of
thing.
So.
C
E
Oh
yeah,
it's
it's
very
cool.
We
thought
I
think
about
this.
The
previous
technical
meeting,
also
about
the
everybody's.
It's
pretty
hot
topic.
Now,
like
storage
for
nfts,
for
example,
everybody
wants
to
have
media
stored
somewhere,
so
everybody
is
like
racing
now
to
to
to
make
something
good,
so
I
think
it
will
be
very
used
service.
C
Yeah
yeah
and
actually
yeah.
So
it's
worth
talking
about
that
storage
thing.
So
this
is
still
an
evolving
idea,
but
but
one
advantage
that
this
peer-to-peer
database
has
over
a
standard
blockchain
is
that
it
can
be
backed
up
to
filecoin
because
it's
on
the
ipfs
network
so
rather
than
having
one
database
that
continually
grows
year
after
year,
I
haven't
had
a
chance
to
really
fully
explore
this
idea,
but
but
I'm
leaning
towards
we
would
sunset
the
the
database
every
year
so
probably
like
in.
When
does
q3
start
like
it's
december
november
october.
E
Interesting
to
do
like,
I
think,
the
hard
drive
guys.
What
is
they
doing
is
depends
from
how
much
tokens
you
burn.
It
will
depends
how
long
it
will
keep
your
information.
So
now
we
are
talking
like
synthetic
every
year,
but
it
will
be
interesting.
For
example,
there
is
the
people
who
are
interested
their
data
to
be
there
for
a
month,
for
example,
for
some
hackathon
or
something
they
don't
want
to
pay
much,
but
other
guys.
E
C
Yeah,
that's
a
good
idea.
That's
a
good
idea!
I'm
excited
to
get
to
the
point
where
we
can
explore
that
more
fully
and
get
get
a
better
idea
of
like
what
the
costs
are,
because
I
have
a
feeling
that
yeah
I
mean
just
the
costs
around.
This
are
totally
different
than
it
would
be
for
a
blockchain
and
right
now,
just
because
I
had
to
pick
a
number
I
picked
10
000,
bytes
or
10
kilobytes
and
0.01
psf
tokens.
C
D
E
C
C
Yeah
there's
a
couple
more
things
on
the
agenda
here.
Yes,
the
merit
calculation
is
worth
mentioning.
I
have
a
link
to
the
poll
request
for
anybody
who
wants
to
check
into
it,
but
one
of
our
members
discovered-
I
don't
know
if
it's
a
bug
is
the
right
word,
but
but
an
undesirable
way
that
merit
was
being
calculated
when
and
it
happened
when
he
moved
from
electron
cash
wallet
into
message.fullstack.cash.
So
the
merit
calculation.
D
C
The
the
merit
calculation
is
what
essentially
determines
how
much
influence
you
have
on
the
governance
of
of
the
psf,
and
so
that's
why
people
who
take
the
governance
a
little
more
seriously,
are
concerned
about
how
the
merit
is
calculated.
I'd
love
to
get
more
feedback
on
this
because
it
it
as
I
dug
into
it.
It
seemed
like
there
was
a
lot
of
different
ways
to
do
it.
Essentially.
C
However,
if
you
say
pay
someone
in
psf
tokens,
that's
going
to
reset
the
clock
to
zero
and
that's
undesirable.
We
want
to
be
able
to
have
people
sort
of
simultaneously
staked
stake
tokens
and
be
able
to
spend
tokens
as
long
as
they're
sort
of
spending
and
replacing,
and
so
what
it
does
instead
is
it.
It
follows
the
parent
utxos
to
the
oldest
one
it
can
find
that
originated
from
the
same
address.
So
as
long
as
the
the
tokens
stayed
in
that
address
or
are
from
that
address,
they
got
spent.
C
D
C
Just
because
it
seems
like
a
lot
of
support
is
is
going
away
for
slp
tokens
or
the
you
know,
the
ones
that
everybody's
used
bitcoin.com
and
simple
ledger
are
starting
to
cut
back.
So
it
might
be
a
good
idea
for
us
to
build
our
own
block,
explorer
yeah
but
anyways.
This
is
an
example
of
the
transaction
I'm
talking
about
where,
on
the
left,
you
have
three
token
inputs
being
merged
into
a
single
transaction.
C
So
in
this
transaction
you
had
three
token
utx
that
was
being
merged,
and
so
the
question
is
which,
which
utxo
parent
chain
do
you
follow,
and
so
the
the
code
tweak
I
made
is
it
well?
It
follows
the
oldest
one,
it'll
it'll
look
at
each
one
and
figure
out
which
one
is
the
oldest
and
then
follow
that
chain
of
parents,
and
I
think
that's
pretty
accurate.
I've
tried
to
think
through.
So
like
the
the
sort
of
attack
vectors
here
and
I'm
a
little
worried.
C
I
might
not
have
thought
of
everything,
but
if,
if
anyone
is
inclined
to
follow
this
link
to
the
pull
request
and
look
at
the
code
and
how
I
calculated
it-
and
I
left
some
notes
in
there-
I'd
love,
I'd
love
feedback
and
I'd
love
to
hash.
This
out-
and
I
have
a
feeling
like
this-
is
something
that's
to
come
back
to
haunt
us
in
the
future.
C
D
C
D
B
B
E
C
D
C
Yeah,
you
know,
I
think,
that
this
community,
the
psf
we
have
a-
we-
have
an
opportunity
to
really
step
up
in
a
big
way.
Those
who
know
my
background.
They
know
that
I
I
used
to
work
at
bitcoin.com
on
the
rest.bitcoin.com
and
developer.bitcoin.com
platforms
and
and
that's
what
originally
started
the
fullstack.cache
and
that's
I
had
a
hand
in
the
creation
of
the
slp
token
protocol.
While
I
was
there
and
they
are
starting
to
shut
that
platform
down
rest.bitcoin.com
and
they're
forwarding
people
on
to
fullstack.cash.
C
C
It's
all
good,
the
the
the
company
who
actually
started
the
simple
ledger
protocol,
like
you
know
james
cramer,
they're,
also
starting
to
wind
down
some
of
their
infrastructure,
and
they
still
have
a
really
great
block
explorer.
It's
simple
ledger.info
and
it
appears
to
be
fully
functional
and
you
know
it
falls
over
occasionally,
but
so
does
the
bitcoin.com
block
explorer
and
I'm
really
proud
of
how
reliable
wallet.fullstack.cache
has
been
operating.
I
think
we've
really
nailed
the
our
ability
to
scale
our
infrastructure.
C
I'd
love
to
see
us
10x
our
api
volume,
so
that
we
could
really
put
that
to
the
test.
I
think
we're
ready
to
do
that,
but
if
we
built
a
block
explorer,
we
could
have.
You
know
that
reliability
that
I
think
people
would
appreciate
and
then
we'd
have
to
kind
of
think
about.
Well,
how
do
we?
How
do
we
monetize
that
so
that
it's
not
just
a
total
loss
leader?
You
know
one
thought
I
had
is
we
could
we
could
sell
advertising
and
then
that
advertising
money
could
go
to
burn
tokens?
C
D
C
C
D
C
E
Cozy
explorer
is
very
cool
too.
You
can
see
like,
for
example,
you
can
see
your
paper
where
it's
there,
how
much
token
you
have
there
you
can
see.
Also,
for
example,
if
you
have
many
devices
with
different
wallets,
you
can
check
them
daily
from
one
place
without
any
time
putting
your
mobile
you
putting
there
your
pin
and
everything
you
just
go
to
the
link
palm.
You
can
see.
You
balance
everything
and
yeah
like
chris
mentioned
it's
very
useful
to
see
if
some
transaction
is
already
like,
go
from
your
wallet
to
the
blockchain.
C
C
C
That's
a
really
unique
use
case
that
the
block
explorers
that
exist
now
will
not
be
able
to
handle,
and
so,
if
we
had
our
own
block
explorer,
we
could
add
those
types
of
features
to
to
help.
You
know
the
same
sort
of
use
cases
of
block
explorers
use
today
for
debugging
and
just
checking
on
things.
We
could
actually
track
these
cross
block
chain
transfers
and
and
help
people
sort
of
debug
that
whole
use
case.
D
C
I
think
the
majority
of
the
cost
would
be
in
the
development
and
maintenance.
I
think
the
the
the
the
hardware
infrastructure
would
be
essentially
a
fixed
cost.
It
wouldn't
be
zero.
You
know,
but
it'd
probably
be
like
less
than
a
thousand
dollars
a
month,
I'm
assuming
like.
If
we
had
you
know
a
million
users,
let's
say
we
had
a
million
users
a
day.
Our
infrastructure
cost
would
probably
be
less
than
a
thousand
dollars
a
month,
and
but
it
would
probably
require
a
full-time
developer
just
to
just
to
get
feedback.
D
C
D
E
Yeah,
it's
good
explorer
is
one
of
the
thousands
very
needed
tools
so
and
yeah
about
the
monetizations.
It
can
be
done
more
like
more
like
the
wallet
fullstack.cache
with
more
plugins.
For
example,
you
can
have
plugins
for
parsing
the
op
return
data
for
different
protocols,
for
example,
if
you
pay
more
we'll
parse
the
memo
dot
cash
op
returns,
so
you
can
see
the
message
is
there
or
we
can
parse
this
kind
of
op
returns,
so
it
can
be
more
like
with
pluggable
architecture,
so
we
can
charge
more
for
the
more
feature.
C
C
E
D
D
This
way
where
I
I
go
in
and
I
photograph
your
store
and
then
all
the
objects
in
the
store
can
be
clicked
on
looked
at
in
360,
and
then
you
can
put
them
in
your
your
basket.
But
how
could
it
be
to
in
that
360
environment,
whether
you're
in
a
vr,
headset
or
you're,
on
a
desktop
or
mobile?
You
click
in
a
random
spot
and
up
pops
discount
tokens
for
the
day
you
know,
and
then
they
can
set,
how
many
come
from
that
particular
token
fountain.
D
And
then,
when
you
go
to
cash
out
or
pay,
those
tokens
would
be
factored
into
how
much
you're
paying
and
whether
you're
paying
fiat
or
I
think
it
would
be
nice
eventually
to
where
okay
I've
got
wine
tokens
and
it
gives
me
a
10
discount
and
that's
factored
in
with
the
bch
or
the
or
the
e
cash
for
the
total
transaction,
and
then
they
they
create
a
qr,
and
I
send
the
money
to
them.
It'd
be
really
cool.
But
what
what
I'm
saying
about
these
guys
is?
That's
that's
more
low-level
stuff.
D
C
C
E
So
I
already
started
working
on
this
stuff,
so
I
make
a
very
small
wrapper
around
the
bch
gs
because,
like
we
told
the
previous
time,
it's
good
if
we
can
do
something
with
our
current
wallets,
like
this
minimal
wallet
and
the
sop
client
one
but
they're
very
difficult
to
to
extend
because
they're
like
they're
made
to
be
like
get
from
the
web,
you
cannot
import
them
and
extend
them.
So
I
decided
to
do
something
with
bch
gs
and
I
created
a
very
simple
wrapper.
E
E
It's
adding
one
new
namespace
nft,
so
you
can
have
some
like
bch
gs.nft
and
some
functions,
some
methods,
and
I
already
created
a
methods
and
I'm
using
this
new
course
utxo.get
to
do
the
stuff.
So
I
wanted
to
explore
this
one.
So
I
already
have
a
create
nft
group
and
I
have
a
mint
nifty
group.
I
have.
C
E
E
E
E
C
E
Yeah
and
about
the
graphical
interface,
I
was
researching
different
stuff
and
what
was
interesting,
how
I
found
several
projects
which
have
interesting
approach.
They
creating
something
like
ready
components,
react
components
to
show
the
the
standard
nfts
like
for
it's
foreign
for
ethereum.
So
it's
this
their
idea
about
the
fan
of
this.
This
seven
two
one,
but
it's
interesting
to
have
a
a
ready
react
component,
like
I
already
done
this
for
my
nft
checker.
E
So
it's
very
easy
to
put
it
inside
like
like
this
one
like
like
just
a
second
see
it's
not
the
map,
but
I
mean,
if
it's
ready
component,
you
can
just
include
it
after
this
in
the
in
the
plug-in
for
the
wallet,
dot,
foo,
dot,
stack,
cache
or
somewhere
else,
and
it
will
show
the
nft.
So
if
it
have
bcp,
it
will
show
the
media
based
on
this
bcp
or
it
can
directly
get
the
com,
the
url
from
the
document
url.
E
C
E
E
Component,
it
will
change
time
because
we
will
have
another
standards
and
everything,
but
the
styling
will
be
still
here.
We
will
have
this
gatsby
component
and
below
this.
It
can
be
something
some
wrapper
like
this
one
to
make
the
the
nft
functions,
so
this
one
can
be
pretty
much
given
to
different
people
to
develop
them
like,
for
example,
good
designers
can
do
great
job
better
than
me
in
the
like
styling
and
everything.
C
Yeah
yeah
yeah,
that's
always
been
that's.
That
was
a
big
reason
for
doing
the
plug-in.
Centric
architecture
is
just
because
I
I'm
just.
I
just
want
to
focus
on
base
functionality
and
then
I'll.
Let
somebody
else
worry
about
making
it
pretty
yeah,
that's
a
that's
a
great
approach,
and
so
it
seems
to
me
like
there's,
there's
really
two
plugins
here:
one
is
displaying
the
nfts
and
then
one
is
creating
the
nfts.
Yes,
yes,
and
so
two
very
different
things,
but
it
looks
like
you
got
them
both
covered
here
yeah.
This
one
is.
E
C
Some
new
commands
to
that
for
this
and
on
the
topic
of
the
way
you're
injecting
bchjs
in
this
you're,
like
so
close
to
the
way
I'm
doing
it
with.
If
you
look
at
bch
message
lib-
and
I
can
send
you
links
to
this
and
the
bch
encrypt
lib-
it
does
almost
the
same
thing
you're
doing
here,
except
it
injects
bch
a
dependency
at
runtime,
and
so
that
makes
the
libraries
like
really
small,
because
they
don't
they
don't
have
a
redundant
copy
of
bchjs.
D
C
C
Use
it
well,
I
need
to
put
you
in
touch
with
andre
cabrera,
who
is
he?
He
helped
me
with
the
initial
art
architecture
of
our
plug-in
for
the
wallet,
and
he
is.
I
was
just
mentioned
the
other
day
that
he
might
be
building
a
plug-in
for
creating
regular
slp
tokens,
and
so
there's
definitely
going
to
be
some
overlap
there
with
with,
if
we
create
a
plug-in
for
creating
nft
tokens,
so
we
should
definitely
collaborate
on
that.
Just
so,
you
know
figure
out
how
to
leverage
one
another's
code.
E
C
C
D
C
D
C
E
They
have
another,
also
interactive
nfts,
where,
like
sound
the
there
was
on
twitter,
I
will
send
you
maybe
link,
but
in
fact
you
can
send
the
nft
parameters
in
real
time.
So
it's
again
some
program,
but
it
has
like
an
open
a
way
to
send
them
different
parameters.
So,
for
example,
it
can
modulate
from
your
voice.
C
E
E
C
C
E
D
Oh
yeah,
I
I
like
the
360
stuff.
It's
it's
challenging.
It's
not
easy
to.
Edit
takes
a
lot
of
computing
power,
but
it's
fun
when
it's
done.
It's
really
cool.
I
in
fact
I
just
did
was
at
the
swimming
pool
on
sunday.
I've
got
a
waterproof
case
right
here,
and
so
I
was.
I
took
one
of
my
360
cameras
underwater
for
a
water
test,
because
we
got
a
big,
huge
zoo
here
with
a
cool
aquarium
and
I'm
trying
to
talk
to
them
about.
D
C
D
It's
always
reverse:
it's
always
reversed
and
yeah
we'll
be
putting
a
bunch
of
stuff
in
the
show
notes
today.
So
you
can
check
it
out.
If
you
have
any
questions,
please
hit
us
up
on
the
telegram
and
or
we
do
take
care
of
your
pigeon,
so
you
can
hit
us
up
that
way
as
well
all
right
everybody.
We
will
see
you
next
time
with
that
I'll
see
you
guys
later
and
I'm
gonna
hit
the
transition
for
the
outro.