►
From YouTube: PSF TSC Meeting
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
B
You
can
turn
them
off
too,
but
it's
okay,
we'll
leave
it
on.
C
C
A
A
Go
there
we
go
okay,
I
think
joey's
here
haven't
seen
anything
from
daniel
or
any
other
notices
on
the
psf
channel
sam,
I'm
glad
you
could
make
it
welcome.
A
So
yeah
try
and
while
I'm
sharing
my
screen,
I'm
not
gonna
be
able
to
see
the
zoom
chat
so
david.
Why
don't
you
let
me
know
and
I'll
rely
on
david
to
keep
an
eye
on
the
zoom
chat
and
the
youtube
chat?
If
there's
any
questions.
A
So
just
to
set
the
stage
this
is
going
to
be
really
informal.
I
know
like
the
agenda,
is
very
formal
and
there's
all
these
documents
and
stuff
that
make
it
very
formal,
that's
so
that
we
have
a
path
to
scale
and
become
formal
as
we
grow,
but
right
now
this
is
a
small
group
and
it's
gonna
be
pretty
informal.
Don't
worry
about
interrupting
me.
Ask.
A
If
you
have
them
yeah.
D
A
At
the
moment,
this
is
more
like
a
club
than
some
big
corporation
or
something
so
yeah.
We're
just
we're
just
all
friends
and
we're
here
to
we're
all
interested
in
privacy
and
free
speech
and
economic
activity
and
blockchains,
and
so
we're
just
here
to
further
the
technology
around
that.
A
A
Sure
yeah,
why
don't
we
do
a
quick
round
table
introduction,
since
we
don't
have
very
many
people?
I
am
chris
troutner.
I
founded
the
permissionless
software
foundation
and
as
well
as
fullstack.cache,
which
is
the
bitcoin
cash
blockchain
as
a
service.
We've
also
branched
out
into
the
bch
a
blockchain
and
we're
looking,
I'm
also
very
interested
in
the
avalanche
blockchain
and
we're
going
to
talk
about
all
those
blockchains
today,
david.
A
Why
don't
you
introduce
yourself
and
then
we'll
go
to
dawn
and
and
then
maybe
stoian
and
then
joey
and
damn.
B
Good,
my
name
is
david
arlen.
I
am
the
business
development
guy
for
the
psf
foundation
and
I've
been
in
the
blockchain
space
for
a
number
of
years,
just
here
to
help
out
where
I
can
I'm
not
a
programmer.
Let's
make
that
clear.
A
Who's
next
yeah
don!
Why
don't
you
give
an
intro.
E
Hey
I'm
don
don
wonton,
I'm
a
general
manager
at
ava
labs
with
the
avalanche
blockchain
and
been
in
crypto
losing
money
since
2016.
I
believe.
A
D
Okay,
so
my
name
is
stoyan
jake
jakov,
originally
I'm
from
bulgaria,
but
I'm
living
like
from
20
years
in
japan,
so
my
daily
job
is
programmer
and
system
engineer
something
like
this:
it
guy,
so
I'm
pretty
new
to
the
blockchain.
In
fact,
I
started.
Maybe
when
the
coroner
starts.
D
E
D
D
D
A
F
Sure
yeah,
so
I
I've
been
a
full
stack
web
developer
in
crypto
since
around
2016.
I
started
at
bitcoin.com.
I
was
there
for
a
few
years
and
I've
been
with
bitcoin
abc
for
the
last
few
months.
A
A
All
right
we'll
keep
working
on
your
on
your
audio
and
we'll
come
back.
If
you
get
it
figured
out,
okay,
well,
let's
sort
of
jump
into
the
agenda
here.
A
So
the
stuff
at
the
bottom
is
the
really
interesting
stuff
that,
like
I
want
us
to
discuss
today,
but
there's
some
sort
of
more
formal
things
that
we
should
discuss,
hopefully
quickly
at
the
beginning.
Since
this
is
the
first
meeting
of
the
technical
steering
committee
I
wanted
to,
I
better
bring
up
just
a
few.
So
I
want
to
talk
about
some
of
the
things
quickly
that
I,
that
is,
in
the
blog.
A
So
if
you
go
to
psfoundation.cache
blog,
you
can
read
about
these
things
that
I'm
going
to
very
quickly
touch
on
this
sort
of
so
the
permissionless
software
foundation's
been
around
for
over
a
year.
A
We
might
actually
be
pushing
two
years
and
we've
already
gone
through
some
at
least
two
significant
changes
in
governance
as
we
grow
and
as
we
sort
of
are
finding
for
lack
of
a
better
term
product
market
fit,
and
so
this
latest
iteration
on
governance
was
kicked
off
by
this
article
that
I
wrote
called
healthy
bitcoin,
which
is
a
play
on
the
article
by
mckeil
rogers,
on
healthy,
open
source
and
what
we're
trying
to
achieve
is
an
architecture
that
looks
like
this.
A
Where
we've
got
the
technical
steering
committee,
which
is
this
committee,
we've
got
the
the
community
committee,
the
com
com
and
so
those
sort
of
balance
each
other
out.
You
got
you
got
the
technical
people
and
you
got
the
the
non-technical
people
and
both
of
those
top
level
committees
are
ultimately
answerable
to
the
psf
token
holders,
since
any
okay,
so
I'll
leave
that
there
and
I
want
to
introduce
two
new
concepts.
A
Another
big
source
of
inspiration
with
this
is
the
working
in
public
by
nadia
ekball.
This
is
a
fairly
recent
book
that
was
published
a
few
months
ago,
but
nadia
has
been
a
researcher
studying
open
source
culture
for
more
than
a
decade.
I
think,
and
that
most
recent
book
really
it's
all
about.
How
do
you
manage
open
source
communities?
How
do
you?
How
do
you
get
a
group
of
people
to
work
together
and
coordinate
and
sustainably
move
forward?
A
And
one
of
the
really
important
takeaways
from
that
book
is
this
concept
of
intrinsic
versus
extrinsic
motivation.
So
when
people
write
software,
you
know
what
we
generally
would
think
of
as
open
source
that
comes
from
it's
a
creative
process,
so
it
has
intrinsic
motivation.
You
don't
really
need
to
pay
people
to
write
software
because
they
want
to
ride
it.
A
What
you
need
to
pay
people
for
is
when
you
need
extrinsic
motivation,
like
writing,
unit
tests
and
quality
assurance
and
all
the
tedious
stuff
that
people
don't
have
an
intrinsic
motivation
to
do,
and
so,
as
we
move
forward
and
as
we
build
infrastructure
on
top
of
blockchains,
we
need
to
ensure
that
there's
high
quality
and
tests
and
all
those
tedious
things
get
done.
A
And
so
that's
where
the
token
comes
in
that's
a
way
for
us
to
provide
extrinsic
motivation
to
developers
to
just
to
get
a
more
holistic
approach
so
that
we
can
sustainably
build
infrastructure.
A
And
so
that's
why
the
psf
token
holders
are
at
the
top,
because
any
tokens
that
we
bring
into
existence
to
provide
that
extrinsic
motivation
will
dilute
the
value
of
the
existing
token
holders
so
they're,
the
ones
that
are
most
impacted
by
that
so
they're,
the
ones
who
should
have
the
final
say
on
that
and
control.
How
that's
done
so.
That's,
ultimately
how
these
two,
these
two
committees:
they
they
answer
to
them
and
so
that
those
token
holders
are
really
represented
by
the
telegram
vip
room.
A
A
That's
really
the
voice
of
the
of
the
stakeholders,
and
so
these
two
communities,
two
committees,
they'll
spin
off
work
groups
to
actually
get
the
work
done,
and
so
I'm
hoping
that
a
result
of
this
this
meeting
today
will
be
the
creation
of
at
least
one
of
these
work
groups
and
maybe
setting
the
stage
for
additional
work
groups.
A
Okay,
cool
so
real
quickly.
Let
me
just
touch
on
a
few
of
these
other
blog
posts,
so
that
was
this
healthy
bitcoin
one.
I've
also
there's
also
this
road
map.
A
Which
is
a
work
in
progress,
this
isn't
set
in
stone,
but
this
is
largely
going
to
drive
the
efforts
of
this
committee
and
sort
of
where
we
go,
and
I
I
won't.
A
I
won't
go
over
this
because
the
article's
there,
but
I'd
I'd,
love
to
see
further
discussion
on
this
and
really
that
that
leftmost
column,
the
core
is,
is
really
where
the
permissionless
software
is
foundation
is
concerned,
and
the
idea
behind
the
permission
of
software
foundation
is
that
this
code,
that
code
on
the
left,
bch
api,
bchjs
and
gatsby
ipfs
web
wallet,
that's
part
of
that
cash
stack
and
I
go
into
more
detail
on
the
cash
stack
in
another
blog
post
there
and
what
it
to
summarize
it
it's
it's
a
it's
a
stack
of
software,
it's
infrastructure
that
any
business
can
use
to
build
on
top
of
any
blockchain.
A
It's
right.
Now
it's
focused
on
bch
and
bcha.
We
hope
to
bring
avalanche
into
that
and
and
even
bsv.
If
developers
from
that
chain,
you
know
want
to
participate,
but
it
certainly
could
apply
to
them.
And
what
we're
trying
to
do
is
create
a
common
core
of
infrastructure
to
go
from
a
blockchain
to
a
phone
app
or
a
web
app
and
provide
like
common
libraries
that
we
can
all
use
and
we
can
all
collaborate-
and
we
all
have
incentive
to
maintain.
A
So
you
know
so
fullstack.cache
would
be
one
entity
bcha
or
abc
a
bitcoin
abc
would
be
one
entity
contributing
to
this.
Hopefully,
avalanche
labs
would
be
one
entity
contributing
to
this.
A
This
core
thing
and
we
may
all
have
our
own
forks,
but
but
the
idea
is
to
provide
this
valuable
stack
that
all
these
different
corporate
entities
or
business
entities
really
have
incentive
to
contribute
to
and
maintain
and
that's
sort
of
the
the
bedrock
foundation
that
will
lead
to
everything
else
on
the
road
map
and-
and
it's
really,
the
the
people
who
are
participating
are
the
people
who
will
get
to
drive
the
roadmap,
let's
see
yeah
and
then,
and
then
this
latest
article
on
the
cross
chain,
slp
we'll
get
to
that.
A
Okay.
So
with
that,
let
me
go
into
this
liberal
contribution
policy.
This
is,
this
is
again
borrowed
from
the
note.js
foundation
and
the
this
is
this
is
very
different.
Then
then
most
software
companies
would
approach
well
I'll.
Just
summarize
it
it's
here
if
you
want
to
read
it,
but
the
idea
behind
the
liberal
contribution
policy
is
that
if
someone
submits
a
pull
request
to
change
code,
it
will
land
by
default
after
36
to
72
hours,
if
no
one
essentially
takes
steps
to
to
prevent
it
from
landing.
A
So
this
is
the
opposite
of
how
it's
typically
done,
where
nothing
gets
in
unless
it's
like
gone
through
the
rigorous
process
of
code
review,
so
that
process
of
code
review
still
needs
to
take
place,
but
the
idea
is
to
not
create
bottlenecks.
The
idea
is
to
you
know:
if
people
don't
participate,
that
shouldn't
that
shouldn't
block
other
people
from
participating-
and
that's
really,
I
think,
the
core
idea
behind
this
liberal
liberal
contribution
policy.
A
It's
also
possible
because
get
makes
it
really
easy
to
roll
back
changes
and
mistakes,
and
you
know
this
may
not
be
the
basically.
A
My
approach
to
this
is-
and
I
I
think,
a
lot
of
people
like
me
who
are
developer
and
develop,
and
engineering
managers
they're
really
uncomfortable
at
first
with
this
idea,
but
the
the
thesis
that
mikhail
rogers,
who
who
is
the
one
who
I'm
sort
of
inspired
by
he
used
this
to
grow
the
node.js
foundation
from
like
three
contributors
to
over
300
contributors,
and
it's
largely
like
what
we
know
today
is
the
node.js
javascript.
A
You
know
language
is
a
direct
result
of
this
policy
and
it's
it's
success,
so
we
could
definitely
do
worse
than
than
follow
it
and
be
inspired
by
it.
So
again,
it's
a
conversation
going
forward.
I
just
want
to
let
everybody
know
that
this
is
the
idea
going
forward.
So
what
the
liberal
contribution
policy
does
that
it
puts
more
of
an
onus
on
the
on
people
to
be
more
proactive
and
I'm
certainly
going
to
be
more
proactive
with
with
doing
code,
reviews
and
yeah.
A
C
Yes,
oh
sam,
I'm
saying
by
the
way
again
from
chicago,
I
was
wondering:
are
there
any
like
technical
prerequisites
for
for
contributing
like
as
far
as
like
a
skill
set.
A
No,
no!
Actually,
if
you
read,
if
you
read
the
the
contribution
policy,
there's
I'm
glad
you
had
that.
Ask
that
sam
there's,
there's
like
a
ladder
here,
so
some
so
there's
the
the
way.
The
vocabulary
here
is
that
there's
like
a
contributor,
a
committer
and
then
the
technical
committee.
So
a
contributor
is
anyone
who
creates
an
issue
or
a
pull
request
or
or
may
participate
in
the
telegram
channel.
A
committer
is
a
person.
A
Who's
actually
landed
a
pull
request
and
and
been
given
right
access
to
the
to
the
repository,
and
so
they
have.
They
then
have
the
ability
to
do
code
reviews
and
then,
if
they're,
in
the
event
of
a
dispute,
there's
a
technical
committee.
So
this
entire
liberal
contribution
policy
model
is
designed
to
grow
contributors
and
and
to
help
people
sort
of
learn
how
to
contribute.
So
we
very
much
welcome
any
level
of
contribution
whether
it's
you
know
opening
an
issue
to
ask
a
question.
A
Okay,
so
I
already
just
kind
of
touched
on
this
road
map.
Let
me
so
the
idea
behind
the
road
map
here
for
the
permission,
software
foundation
is
like
we're
focused
on
protecting
helping
individuals,
protect
their
privacy
and
their
right
to
free
speech
and
engage
in
economic
action.
So
it's
very
much
focused
on
individuals
and
individual
action,
and
then
the
software
and
the
technology
is
sort
of
secondary.
It's
it's
the
means
by
which
we
achieve
these
high
level
goals.
A
And
so,
if
you
look
at
the
roadmap
and
if
you
scroll
below
the
roadmap,
I
have
lists
of
all
the
github
repositories
that
are
reflected
in
the
roadmap.
But
I've
got
three
columns
in
the
roadmap
for
privacy,
free
speech
and
economic
action
and
which
should
be
clear
just
by
looking
at
the
general
shape
of
this.
A
Is
they
sort
of
build
on
top
of
one
another,
like
you
can't
really
have
a
very
effective
free
speech
unless
you
also
have
privacy
so
that
you
don't
get
persecuted
for
your
speech,
you
can't
really
have
very
good
economic
action
unless
you
have
both
free
speech
and
privacy
and
so
in
this
road
map.
A
I
this
the
top
sort
of
lists
a
lot
of
the
existing
software,
so
message.fullstack.cache
sort
of
spans
the
whole
spectrum,
and
in
a
previous
video
where
I
talked
about
our
communication
channels,
that
allows
you
to
stake
tokens
and
get
access
to
the
vip
room
so
that
you
can.
You
can
have
more
of
a
voice
in
the
community
and
and
drive
this
road
map
it
lets
you
send
end-to-end
encrypted.
A
You
know
essentially
emails
to
to
anybody
with
a
bitcoin
cash
address
and
it
gives
access
to
like
a
sort
of
a
condensed
community
feed
which
also
takes
place
on
the
blockchain,
but
we
can
actually
at
that
website
we
can
take
that
and
raw
information
and
sort
of
filter
it
and
and
then
from
there.
We
have.
You
know
these
these
different
branches.
A
I
don't
want
to
take
forever
talking
about
this
because
we
can
take
this
offline,
but
I
just
want
to
introduce
this
idea
of
the
roadmap,
in
particular
for
people
who
who
have
psf
tokens
that
they've
staked
and
get
access
to
the
vip
room
very
much.
I
want
to
hear
your
input
on
this
and
I
want
the
community
as
a
whole
to
drive
this,
even
even
if
I'm
getting
the
ball
rolling,
this
needs
to
be
a
community
driven
thing.
Can't
just
be
my
my
thing.
A
Okay,
so
that's
the
roadmap
interrupt
me
if
anybody
has
questions,
but
otherwise
I'm
gonna
move
on
to
the
next
item,
so
so
fullstack.cache.
A
I
think
most
people
here
are
familiar
with
it,
but
for
people
who
aren't
fullstack.cache
is
a
website
that
I
run
with
a
couple
other
people
and
it's
based
on
this
idea
of
the
cash
stack
for
going
from
blockchain
to
phone
out
and
it's
essentially
it's
a
blockchain
as
a
service.
It's
a
subscription
service.
So
it's
a
rest
api.
A
You
would
pay
a
monthly
subscription
to
so
that
the
apps
that
you
build
can
just
quickly
and
easily
access
the
blockchain
and
all
the
support
information
around
that.
However,
it
is
not
a
walled
garden
if
people
want
to
replicate
this
infrastructure
on
their
own.
That
is
encouraged.
There's
tools
to
to
rapidly
do
that.
This
is
sort
of
the
flagship
product
for
the
psf
right
now,
when
people
pay
a
subscription
to
fullstack.cash.
A
That
subscription
goes
to
burn
tokens
and,
and
so
as
so,
the
the
bitcoin
cash
goes
into
the
token
liquidity,
app
the
tokens
get
burnt
and
take
out
of
existence,
so
the
bch
balance.
In
the
token
liquidity
app
goes
up,
the
token
balance
goes
down
that
makes
the
actual
like
dollar
value
of
the
of
the
token
higher,
and
that's
what
lets
us
pay
developers
for
those
extrinsically
motivated
things.
We
need
like
unit
tests
and
quality.
A
So
that's
that's
sort
of
the
very
brief
introduction
to
the
econ.
The
the
token
economics.
A
And
there's
more
info
at
psfoundation.cash.
If
you
want
to
dig
into
that,
I
think
I
can
skip
this.
There
have
been
many
updates
to
message.fullstack.cache
daniel's
been
working
really
hard
on
it.
In
fact,
let
me
just
check
yep.
He
has
not
showed
up
and
but
needless
to
say,
we've
been
focused
mostly
on
the
end
and
encrypted
messaging
features
of
message.fullstack.cache.
A
So
you
can
send
an
end
in
encrypted
message
to
anybody
with
a
bitcoin
to
any
bitcoin
cash
address.
You
can
send
it
to
just
recently
pushed
updates
so
that
you
can
send
do
like
group
group
sends
so
you
can
do
like
multiple
addresses
and
hit
send
once
and
it
goes
to
everybody
you
can
reply
and
you
can
forward.
So
we've
got
the
basic
email
functionality
in
there.
A
The
next
big
thing
that
we're
going
to
work
on
is
an
address
book
so
that
we're
not
just
dealing
with
bitcoin
cash
addresses,
which
is
you
know,
really
hard,
it'll,
be
much
more
like
human,
readable
and
then
unsensible
publishing.
A
I
do
wanna,
hopefully
that
website's
back
up
no
it's
up.
I
would
push
an
update
and
I
broke
something
so
unfortunately
I'll
cover
that
at
a
different
point,
but
the
unsensual
publishing
will
have
a
series
of
videos
and
what
it
is,
in
fact
a
better
example.
Since
that's
not
up
is
wallet.fullstack.
A
So
this
is
an
example
of
a
web
app
that
you
can
build
with
with
fullstack.cache,
but
in
terms
of
unsensible
publishing.
I
want
to
draw
attention
to.
A
Okay,
but
these
apps,
not
only
do
they
work
on
a
domain
name
like
whatever.fullstack.cache
they're,
also
mirrored
on
the
tor
network.
This
is
the
tor
address
and
ipfs.
This
is
the
ipfs
address,
and
these
can
also
be
mirrored
because
they're
on
ipfs,
they
can
be
mirrored
by
multiple
peers
and
that's
what
makes
it
uncensorable
is
it
so
fullstack.cache
could
get
blocked.
A
I
could
have
the
domain
taken
from
me,
or
I
could
just
have
a
simple
404
error
like
we
saw
and
that
can
go
down
and
that's
pretty
normal
for
the
web,
but
because
it's
accessed
over
tor
people
can
access
it
privately
because
it's
also
accessible
over
ipfs.
A
If
there
was
an
active
attempt
to
censor
this
website,
anybody
can
set
up
a
mirror
with
a
few
commands
and
and
provide
access
to
that
web
app,
and
it
leverages
this
thing
called
the
streisand
effect,
which
is
a
self-defeating
phenomenon
where
the
more
someone
tries
to
censor
a
piece
of
content.
It
actually
draws
attention
to
it,
causes
it
to
be
shared
more
and
thus
makes
it
harder
to
censor.
So
the
act
of
trying
to
sensor
actually
makes
it
harder
to
censor.
A
That's
the
streisand
effect
and
that's
what
ipfs
and,
to
a
large
extent,
bitcoin
cash
leverages
by
by
sort
of
making
it
super
super
easy
to
share
and
mirror
content.
So
I
encourage
people
to
check
out
more
and
there
will
be
videos
in
a
couple
hours
on
insensiblepublishing.com
that
that
speak
more
directly
to
this.
But
this
this
is
a
core
piece
of
tech
that
I've
been
working
on
for
the
last
couple
years,
all
the
sort
of
web
app
demos
that
I've
been
building
for
fullstack.cache
and
permissionless
software
foundation.
Leverage
this.
A
D
A
question
yeah:
is
there
some
development
on
the
like
before
there
was
a
problem
with
the
woman
from
china
which
cannot
access,
use
the
wallet,
because
the
rest
interface
is
not
how
to
see
it's
sensorable.
D
A
Yeah,
I'm
so
glad
you
asked
that
stoian
yeah,
that's
actually
right
here
under
the
free
speech
column,
this
ipfs
based
api
and
I
I
have
a
youtube
video
and
there
will
be
a
link
on
unsensiblepublishing.com
once
I
fix
the
website
and
that
I
did
on
this
topic
and
so
yeah.
It's
it's
in
the
road
map
and
just
real
briefly.
A
So
you
have
a
web
page
and,
like
I
just
described,
wallet.fullstack.com
is
mirrored
over
ipfs.
So
you
can
access
that
that
front
page
that
front
end,
but
that
doesn't
necessarily
mean
that
you
can
access
the
backend.
The
rest
api
provided
by
fullstack.cache.
D
A
It
is
possible
to
I
have
a
prototype
to
use
ipfs
to
basically
replace
the
rest
api
so
that
that
the
back
end
communication
happens
over
the
ipfs
network,
which
would
make
both
the
front
end
and
the
back
end
nearly
unsensible
I
mean
I
I
for
la.
I
think
it
would
be
unsensible.
I
honestly
can't
I've
talked
to
many
ipfs
people,
and
I
can't
think
of
a
way
that
it
could
be
censored
at
that
point.
A
A
A
Okay,
so
that's
sort
of
the
the
stuff
I
really
needed
to
cover.
I
think
this
next
is
this.
Next
phase
of
the
meeting
is
going
to
be
more
of
a
more
of
a
roundtable
discussion,
so
one
of
the
first
I
talked
about
sorry,
I'm
looking
yeah
talked
about
this
government
structure,
governance
structure
and
spinning
off
work
groups
and
one
of
the
first
work
groups
that
I'd
like
to
see
us
spin
off
is
like
an
slp
work
group,
simple,
ledger
protocol.
A
I
think
everybody
in
this
meeting
is
familiar
with
that
protocol
and
it's
it's
because
it's
so
simple,
it's
really
easy
to
port
it
to
different
blockchains
and
from
my
research,
I'm
pretty
sure
there
will
be
no
issue
getting
the
slp
protocol
to
run
on
the
bcha
blockchain.
A
It
already
does
get
it
to
run
on
the
avalanche
blockchain
and
it
could
even
run
on
bsv,
although
I
haven't
seen
any
interest
from
that
that
camp
in
doing
it,
but
technically
it
should
be
possible
and
I'd
like
to
so
slp
is
a
really
good
like
candidate
for
something
for
the
psf
to
manage,
because
it
is
so
flexible
in
cross
block
chain,
and
the
motivation
here
for
me
is
that
as
a
business
building,
trying
to
build
on
a
blockchain
for
the
last
few
years
and
a
developer
advocate
who's
talked
to
developers
at
other
companies
trying
to
build
on
blockchains.
A
There's
this
notion
of
platform
risk
and
platform
risk
is
really
well
studied,
because
it
applies
to
platforms
like
facebook
and
youtube
and
twitter
and
we're
all
familiar
with
getting
d
platformed,
and
that
is
the
risk
prevent.
You
know
that
platforms
provide.
Is
that
if
you
use
a
platform
because
it
has
that
network
effect,
the
risk
you're
taking
on
is
that
you
could
get
d
platformed,
and
so
the
advantage
of
using
a
blockchain
is
that
you
know
you
can't
get
de-platform
from
a
blockchain.
A
However,
you
do
get
lock-in
like
if
you
traditionally,
if
you
you
choose
a
blockchain
and
you're
stuck
on
that
blockchain
and
you
can't
it's
a
very
painful
and
expensive
process
to
try
and
move
off
of
that.
Blockchain
and
so
slp
tokens
provide
this
sort
of
middleware
that
that
could
potentially,
if
this
was
developed,
allow
a
business
to
move.
You
know
not
painlessly,
but
much
more
than
today,
move
from
one
blockchain
to
another.
If
one
blockchain
say
has
better
develops,
better
features
or
another,
our
blockchain
gets
taken
down,
say:
there's
like
a
huge.
A
You
know
like
inflation
bug
or
or
something
like
that,
which
is
a
you
know,
real
possibility,
even
if
it's
not
common,
and
so
I'm
personally
attracted
to
this
idea
that
slp
tokens
could
move
around
blockchains
and
that
we
could
develop
a
protocol
or
that
we
we
have
a
protocol
that
that
is
equally
applicable
to
several
blockchains.
A
So
I
know,
joey
working
with
bcha
is
doing
a
lot
of
work
with
slp
tokens
and
I've
talked
with
don
on
the
avalanche
side.
You
got
we,
we
have
a
project
we'll
get
to
in
a
minute
that
involves
actually
building
this
bridge,
to
bring
slp
tokens
to
the
avalanche
chain
and
and
back
so,
let's
consider
the
conversation
open.
If
anybody
has
any
input
on
this
idea
of
slp
protocol,
how
we
approach
it
and
this
idea
of
cross
block
chain
transfer
of
slp
tokens.
C
C
I
I've
seen
a
talk
with
with
a
cardona
and
he
was
talking
about
virtual
machines
yeah.
It
seemed
really
really
crazy.
I
was.
A
E
Right,
I
can
give
it
a
go.
So
it's
kind
of
you
know
you
always
hear
everyone
like
shilling
their
like
preferred
platform,
always
talking
about
like
tps
and
like
finality,
and
all
that
so
I'll.
Try
to
avoid
that,
but,
like
the
main
innovation
in
avalanche,
like
in
in
my
opinion,
is
the
fact
that
it's
like
leaderless.
E
So
you
know
you
had
like
the
classical
consensus,
which
is
you
know,
like
a
consortium
group
and
you
had
nakamoto
which,
like
a
lottery
type
system,
and
then
you
know,
the
leaders
pick
based
off
the
resources
that
they
have,
and
so
this
one's
leaderless
and
based
off
of
just
subsampling
like
random
peers
and
then
it
you
know,
it'll
go
to
like
the
side
that
is
most
voted
on,
but
as
far
as
the
virtual
machines,
polka
dots
really
having
its
run
right
now,
with
like
its
pocket
chains,
which
all
have
like
a
a
shared
security
model
which
kind
of
limits
it
to
like.
E
Roughly,
hopefully,
you
know,
100
chains
in
the
future,
but
avalanche
doesn't
share
like
the
same
security
model
between
all
these
subnets.
It
actually
allows
like
the
flexibility
of
really
doing
whatever
you
want,
whatever
virtual
machine
you
want,
and
you
like,
incentivizing
your
validators.
However,
you
want
it
like
proof
of
work,
proof
of
stake,
or
if
you
want
to
do
something
like
nano
again,
you
know
just
maybe
not
incentivized
at
all,
but
it
keeps
you
from
having
to
put
in
a
lot
of
resources.
E
I
guess,
like
you,
would,
with
polka
dot
and
creating
a
a
new
network
or
side
chain,
or
you
know,
subnet
whatever
you
want
to
call
it,
and
it's
not
like
one
linear
chain
with
like
a
lot
of
like
little
sub
chains,
even
like
the
main
chain
is,
is
three
separate
chains.
So
it's
like
a
network
of
all
these
extremely
flexible,
interacting
block
chains
and
and
dags,
like
chris
said
it
it's
fairly
complex.
So
even
just
talking
about
it,
I'm
realizing
I'm
not
making
like
a
whole
lot
of
sense,
but.
A
A
So
in
bitcoin
we
have
the
blockchain,
but
in
avalanche
you
they
have
three
base
block
chains.
They
have
the
x
chain,
the
p
chain
and
the
c
chain,
and
so
the
x
chain
is
the
most
that's
like
bitcoin.
It's.
It
has
the
the
base
asset,
which
is
avex
and
it
has
tokens
and
you
move
them
back
and
forth
and
it
has
a
ledger
and
it
works
basically
just
like
bitcoin
or
bitcoin
cash.
A
Chain
the
platform
chain
and
then
the
the
the
c
chain,
which
is
the
contract
chain.
So
it's
the
sea
chain,
that's
more
like
ethereum
right
and
so,
and
so
they
have
so
I
mean
I've
talked
to
a
lot
of
the
devs
there
at
ava
labs
and
the
the
meme
they
like
is.
Is
the
borg
like
we
shall
assimilate
everything
because
they
have
that
they
they
can.
Basically,
you
can
take
a
smart
contract
from
the
ethereum
and
just
port
it
right
over
to
avalanche
and
because
the
x
chain
works
very
similar
to
bitcoin.
A
You
can
do
pretty
much
and
it's
utxo
based
like
bitcoin
is
you
can
do
all
basically
the
same
functionality
that
bitcoin
has,
and
so
it's
really
so
that's
that's,
like
the.
I
think,
the
biggest
thing
that
people
have
to
like
understand
to
wrap
their
head
around
avalanche
and
and
then
what
you
said,
dawn
sort
of
sort
of
builds
on
top
of
that
is
the
platform
chain.
A
Lets
people
build
their
own
custom
blockchain
on
top
of
the
avalanche
blockchain,
and
so
you
can
have
a
super
custom
blockchains
that,
like
we've
never
seen
before
and
don't
exist
so
like,
for
instance,
I
I
think
I've
heard
emin
give
examples
of
like
like
real
estate
and
banks
like
they
might
form
a
private
blockchain
between
a
consortium
of
banks
and
that's
heavily
permissioned
and
like
is,
is
nothing
like
that
anybody
from
the
bitcoin
space
would
want
to
engage
in,
but
they
need
to
because
they
have
specific
needs,
for
you
know
their
regulated
industry.
A
So
it's
it's
really
flexible,
but
as
a
result
of
its
flexibility,
it's
also
incredibly
complex,
and
so
that's
the
hardest
part
with
with
wrapping
your
head
around
that
I
don't
don.
Did
I
do
justice.
E
Oh,
no,
you
did.
You
did
really
good
you
hit
on
the
because,
like
like
you're
talking
about
the
maybe
like
a
more
private
chain
like
I
was
talking
first
about,
you
know
like
building
new
things,
but
you
hit
really
good
on
like
the
sea
chain.
Just
the
ability
so
like
the
c
chain
is
just
a
straight
rip
of
ethereums.
You
know
evm,
it
even
uses
it.
I
mean
it
uses
everything's
the
same
really
even
the
address
format
the
contract.
So
you
can
use
things
like
truffle
and
remix
on
it.
E
You
can
go
in
and
you
know
point
meta
mask
or
anything
that
lets
you
do
rpcs
and
so
it
not
only
is
it
just
a
straight
rip,
but
the
interesting
thing
to
me
at
least,
is
that
it's
still
denominated
in
a
box
and
it's
just
a
simple
swap
back
and
forth.
So
you
can
take
the
tech
from
really
any
chain
that
you
wanted
to
and
use.
Avox
is
like
the
the
main
you
know,
source
of
value.
E
So
if
you
wanted
to
go
and
look
at
bsv
tech,
for
example,
I
like
bsv,
you
know
it's
got
its
things,
but
it's
got
some
really
nice
wallets
and
some
just
general
texts.
You
could
go
in
there
and
you
know,
make
a
you
know:
bitcoin
virtual
machine
and
then
use
eibach's,
the
denomination
and
then
basically
just
kind
of
assimilate
them,
and
you
repeat
that
with
every
single
chain
and
since
there's
no
real
limits
and
there's
not
really
a
real
cost.
Anyone
can
do
this.
It's
all
optional.
A
So
yeah
to
bring
this
back
around
to
the
slp
tokens
and
the
protocol.
You
know
the
state
of
the
slp
world
right
now
is
there's
slpdb,
which
is
written
in
typescript,
it's
a
fork
of
bitdb.
So
it's
it's
a
set
essentially
a
mongodb
database
and
it
has
a
writer
and
a
reader,
and
so
the
writer
is
slpdb.
It
crawls
a
blockchain
by
talking
to
a
full,
node
and
populates
the
database
with
all
the
slp
token
information
by
reading
the
op
return,
and
so
this
is
focused
on
the
bitcoin
cash
blockchain.
A
But
of
course
it
also
works
on
bcha,
because
this
was
all
developed
prior
to
the
fork,
and
there
are
issues
with
slp
db.
I
mean
I,
I
hesitate
to
call
them
issues
because
they're
really
just
the
same
limitations
that
any
piece
of
software
would
have
to
deal
with.
A
A
If
anybody's
curious,
I
think
the
emphasis
in
the
bch
blockchain
has
been
put
more
now
on
the
bchd
node
full
node,
which
has
slp
indexing
built
into
it,
and
one
of
the
big
features
that
that,
with
that
new
and
sort
of
incarnation
of
the
slp
protocol
or
implementation,
is
that
the
bchd
full
node
prevents
people
from
burning
tokens,
which
is
this
constant,
because
slp
tokens
are
not
minor,
validated
it's
possible
to
sort
of
screw
up
the
the
protocol
and
the
default
action
when
that
happens
is
that
the
tokens
are
burned
and
taken
like
like
they
just
go
away.
A
They
evaporate
and
that's
a
really
undesirable
thing
about
slp
tokens
that
we
sort
of
it's
sort
of
the
trade-off,
because
they're
so
simple
and
because
they're
so
simple,
we
can
translate
them
to
other
blockchains.
But
this
is
the
trade-off
and
so
bchd
with
this
new
slp
indexer
is
pretty
sweet
because
it
will
actually
prevent
you
from
burning
toe
it'll,
like
sort
of
check
your
work
and
it
will
refuse
to
broadcast
the
transaction
if
it's
malformed
and
would
potentially
burn
tokens.
A
So
that's
pretty
interesting.
So,
in
order
to
completely
bring
slp
tokens
to
a
blockchain,
you
would
need
some
type
of
indexer,
so
bch
has
bchd
and
slpdb
bcha
has
slp
db
avalanche
does
not
have
an
indexer,
however,
they
have
their
own
native
token,
and
so
I
guess
that
might
be
a
good
segue
into
this.
This
project
that
that
that
dawn
and
all
the
labs
are
going
to
be
sponsoring
we're.
A
Looking
for
a
developer
and
one
of
the
first
work
groups,
I'm
hoping
to
spin
off
would
be
focused
on
this
idea
of
building
a
bridge
between
all
three
chains:
bch
bcha
and
avex,
and
on
the
obex
side,
we're
not
going
to
worry
about
doing
an
index,
or
at
least
at
this
point
we're
just
going
to
will
burn
the
tokens
on
one
of
the
other
block
chains
and
then
have
them
reappear
as
an
avalanche
native
token
and
then
and
then
reverse.
That
process.
A
But
joey,
I'm
wondering
if
you
want
to
hop
in
here,
do
you
have
any
insight
into
sort
of
what
what
challenges
are
you
facing
in
terms
of
the
slp
protocol
on
the
bcha
chain?
What
what
obstacles
do
you
see
you
know
in
the
near
and
distant
future,.
F
Really
just
resources
testing
resources
in
the
immediate
future.
It's
just
gonna
be
rolling
out
software
that
fully
utilizes
the
tools
that
are
already
there.
You
know,
for
example,
cache
tab.
The
wallet
doesn't
even
do
a
lot
of
basic
things
like
minting
tokens
and
things
that
psf
back-ends
would
support.
F
F
Things
like
you
know
as
new
features,
are
added
making
sure
it's
not
breaking
anything,
but
I,
like
everybody
in
crypto
rate
like
there's
just
so
much
to
do
it's
hard
to
say.
F
A
Yeah
that
reliability,
thank
you
for
using
that
word,
because
that
is
the
watch
word,
so
james
cramer
just
released
version
1.0.0
of
slpdb
and
really
the
only
ch.
I
don't
know
if
you
were
aware
of
that
joey.
The
only
the
big
change
that
he's
made
in
this
first
official
release
is
that
slpdb
has
been
struggling
with
nft
tokens.
It
wasn't
optimized
for
it.
A
They
didn't
really
get
much
traction
while
it
was
being
developed
and
now
a
lot
of
companies
have
been
interested
in
nfts
a
lot
more
nfts
have
been
getting
generated
and
slp
db.
All
the
sop,
like
every
slp
db
instance
in
the
world,
has
been
struggling
with
this
because
it
for
some
reason.
When
you
create
nfts
it,
it
requires
significantly
more
memory
than
normal
tokens,
and
so
in
terms
of
reliability,
I'm
excited.
I
haven't
tried
out
the
new
version
yet
and
just
and
to
see
how
it
performs
relative
to
the
older
version
with
with
nfts.
A
So
just
food
for
thought.
I
don't
think
there's
anything
actionable
today,
but
but
one
of
the
first
work
groups,
I'd
love
to
see
spun
off,
is
just
a
work
group
to
focus
on
the
slp
protocol
and
and
in
terms
of
as
far
as
the
permission
of
software
foundation
is
concerned,
you
know
as
a
consortium
representing
several
businesses
in
the
blockchain
space,
like
sort
of
just
driving
the
evolution
of
that
protocol
and
that
reliability
is
is
first
and
foremost
one
of
the
issues
or
I
need
to
stop
using
that
word.
A
One
of
the
trade-offs
with
with
slpdb
is
it
uses
mongodb,
which
is
really
slow
and
has
a
really
large
footprint,
so
something
like
roxdb
or
leveldb
would
probably
be
a
better
choice.
It
would
make
it
much
faster
and
much
more
performant,
and
so
one
of
the
things
I
would
love
to
see
down
the
road
if
we
had
the
resources
and
interest
would
be
a
rewriting
of
the
slpdb
indexer
just
to
make
it
faster
and
more
reliable.
I
mean
it's
great.
A
What
we
have
right
now,
I
mean
james,
is,
is
a
genius
and
an
amazing
person,
and
I'm
so
grateful
that
he's.
Given
us
such
a
wonderful
piece
of
technology
like
slp
db,
but
he's
he's
sort
of
his
focus
is
more
on
the
bchd
and
and
moving
forward
with
that,
which
does
not
translate
well
like
that
approach
to
integrating
it
into
a
full
node
that
doesn't
really
translate
very
well
across
blockchains
and
and
so
just
putting
the
food
for
thought
out
there
to
anybody.
A
Who's
interested
would
love
to
start
like
a
consortium
or
work
group
to
just
sort
of
focus
on
the
state
of
slp
and,
and
you
know
where
it
goes.
A
Okay,
so
the
next
item
for
roundtable
discussion
is
this
relationship
between
the
community
committee
and
the
technical
steering
committee.
I
kind
of
described
that
so
I
don't
know
if
we
need
to
have
a
lot
of
discussion
about
it.
But
if
anybody
has
any
thoughts
on
that
topic,
I'm
all
ears,
in
particular
one
of
the
things
that
we're
going
to
have
to
explore
as
a
group
is
this
tension
between
the
community
committee,
the
technical
committee
and
the
token
holders,
and
it
remains
to
be
seen,
sort
of
how
that
relationship
will
evolve.
A
The
idea
behind
the
community
committee
is
that
it's
it's
supposed
to
set
the
the
culture
and
direction
and
be
more
of
a
formal
voice.
You
know
so
the
right
now
there's
not
very
many
people
in
the
vip
room.
So
it's
very
easy
to
track
those
conversations.
A
But
if
we're
successful,
there
will
be
more
people
and
more
voices
and
it
will
get
noisier,
and
so,
if
we
scale
and
if
we're
successful,
the
community
committee
will
sort
of
take
on
that
role
of
the
voice
of
the
stakeholders
and
represent
the
community
as
a
whole
and
set
a
lot
of
the
the
cultural
standards
for
the
psf
and
hopefully
balance
the
the
technical
committee.
This
committee,
in
terms
of
like
the
you,
know,
the
things
we
want
to
work
on.
So
hopefully
we
can
represent
businesses,
both
their
technical
needs
and
their
cultural
needs.
A
D
A
Well,
I
don't
know
if
it's
yeah
I
might
have,
that
might
not
have
been
the
best
way
to
describe
it.
I
don't
know
if
there
is
a
like
any
conflict,
they're,
certainly
designed
to
work
together.
It's
not
conflict
right,
it's
just
right,
okay,
right,
yeah
and
and
again
like
I'm,
getting
all
of
my
inspiration
from
the
node.js
foundation
this.
This
is
how
they
do
it.
They
have
a
a
community
committee
and
a
technical
committee,
the
technical
committee
sort
of
drives.
A
You
know
the
new
versions
and
the
and
and
all
the
features
that
go
into
node.js
and
the
community
committee
is
more
involved
with
like
hackathons
and
just
interfacing
with
businesses,
and
you
know
just
all
the
other
non-technical
things
that
are
involved
with
a
successful
project.
E
I
don't
think
there
needs
to
be
like
any
existing
tension.
Yet,
just
like
looking
back
at
the
past,
you
know
five
six
years
of
bitcoin.
We
can
definitely
assume
that
there's
going
to
be
some
tension
between
what
you
know,
the
community
voices
and
like
the
development,
because
that
seems
to
be
like
the
main
tension
point,
every
single
time.
A
B
It
seems
to
be
a
logical
or
I
come
to
a
logical
conclusion
with
it,
because
developers
are
engineers
or
scientists,
and
so
they
have
a
way
of
talking
about
the
technology.
B
That
is
really
constructive,
but
it
is
not
the
same,
as
you
know,
the
the
bystanders
or
or
the
people
that
are
the
you,
the
users
per
se,
so
that
that's
really
the
tension,
it's
just
because
they
come
from
different
worlds.
It's
like
they're
speaking
different
languages,
and
that
needs
to
be
explored
so
that
there's
a
bridge
between
those
two
groups-
and
I
think
that's
what
chris
is
talking
about.
A
B
Yeah
don
has
has
has
been
involved
in
the
in
the
tension
and
and
exploring
how
to
express
the
the
views
and
the
needs
of
the
developers
and
and
and
putting
it
into
layman's
terms.
Because
you
know
I
really
appreciate
developers,
because
without
them
we
wouldn't
have
anything.
But
you
know
they
are
a
different
animal
than
the
rest
of
the
world
and
no
offense
intended
at.
B
A
Well,
the
only
other
thing
on
the
agenda
is
to
discuss
this.
This
cross-chain
application,
the
don's
funding
we're
in
the
process
of
there's
I've
done
a
blog
post
with
the
specification
and
a
road
map
for
this
project.
A
The
idea,
like
I
described
before,
is
really
just
to
be
able
to
burn
a
token
on
the
bch
and
bcha
chain
and
have
it
appear
on
the
avalanche
chain
and
then
do
the
reverse
burn
a
token
on
the
avalanche
chain
and
have
it
appear
on
one
of
the
other
chains,
and
we've
got
a
good
foundation
of
technology
with
the
token
liquidity
app
that
the
psf
uses
to
maintain
liquidity
between
its
token
and
in
the
bch
chain.
A
That'll
be
sort
of
the
prototype,
that's
used,
and
so
really
all
that
we
have
to
figure
out.
Is
this
create
minting
and
burning
of
tokens
on
both
sides
and
then
modifying
the
token
liquidity
app
to
do
those
things
one
drawback
of
this
process.
It
is
neither
trustless
what
was
it?
It's
not
trustless,
and
it's
not
it's
not
an
atomic
swap.
So
maybe
we
can
build
up
to
those
someday,
but
right
now,
there's
no
option
for
tran.
A
For
transferring
a
token
across
blockchains-
and
this
will
at
least
open
the
door
to
that,
and
then
improvements
can
be
made
from
there.
So
I'm
in
the
process
of
of
talking
to
developers
who
are
interested
in
this.
I
encourage
people
to
reach
out
to
me
on
telegram
if
they're
interested
and
it's
only
paying
200,
it's
a
200
a
week-
stipend
and
we're
hoping
to
get
20
hours
a
week
out
of
that
which
is
very,
very
low
by
american
standards.
A
But
I've
been
told
by
multiple
people
in
eastern
europe
and
south
america
that
that's
a
pretty
good
income
and
don's
agreed
to
fund
it
for
three
months
and
we'll
we'll
see
where
it
goes
from
there.
I'm
hoping
the
project
will
only
take
two.
I
think
we've
done
a
good
job
of
sort
of
making
a
limited
scope
for
this
for
this
project
and
I'm
really
excited
because
it'll
it'll,
just
it's
it's
something
that's
never
been
done
before,
and
I
think
it
provides
a
good
path
for
businesses
to
de-risk.
A
E
I
have
a
quick
question
and
it
might
just
be
you
know
my
my
lack
of
technical
knowledge,
I'm
undoubtedly
the
least
technical
person
here,
but
the
language
of
like
burn,
and
then
you
know
minting
you
know,
because
most
bridges
have
some
sort
of
complex
way
of
you
know,
locking
a
token.
So
this
sounds
like
it's
actually
a
burning
and
then
like
a
re-minting.
So
is
this?
What's
currently,
you
know
in
the
works
between
different
blockchains,
only
something
that
can
work
with
like
variable
capped
assets,.
A
Yeah
yeah,
it
would
be
a
variable
capped,
asset
type
of
type
of
scenario,
so
yeah,
so
just
I
mean
minting,
is
bringing
a
new
token
into
existence.
Burning
is
the
opposite
of
that,
bringing
it
taking
it
out
of
existence,
so
this
whole
process
could
work
with
a
fixed
cap
asset
that
which,
for
those
who
don't
aren't
familiar
with
that
nomenclature,
that's
a
token
that
you
create
and
then
essentially
burn
the
minting
baton
in
in
slp
terms,
so
that
once
you
create
your
initial
batch
like
it's
fixed,
you
can't
change
the
supply
anymore.
A
You
can
still
burn
tokens,
but
you
know
or
lose
them,
but
you
can't
bring
any
new
ones
into
existence,
so
you
this
would
work
with
those
types
of
tokens,
but
it
would
you
know
long
term
that
would
that
would
present
an
issue.
E
What
is
this
the
idea
of
like
this
kind
of
bridge?
Is
it
something
that
can
be
you
know
built
off?
Is
it
like
a
stepping
stone
in
that
direction,
or
is
it
would
that
have
to
be
something
like
totally
separate.
A
Yeah
yeah
I'm
looking
at
it
as
a
stepping
stone
in
the
direction
you
know
like
like
we're
doing
something
that's
never
been
done
before,
and
so,
if
we
can
do
that,
that's
a
huge
milestone
and
then
from
there
we'll
have
a
lot
better
clarity
to
achieve
like
a
more
refined
process
like,
like
you
said
like
being
able
to
work
with
fixed
capped
assets
or
or
trying
to
do
more
of
an
atomic
swap
or
a
or
a
trustless
transfer.
A
So
what
makes
this
not
trustless
is
that
there
would
have
to
be
an
app
that
talks
to
the
avalanche,
blockchain
and
the
bitcoin
cash
blockchain,
and
and
handles
everything,
as
opposed
to
like
a
smart
contract
that
it
just
sits
there
and
no
one
can
turn
it
off
and
no
one
controls
it,
and
once
you
launch
it,
if
it
has
a
bug,
you
can't
fix
it.
You
know,
that's
the
it's!
It's
a
it's
very
much
a
double-edged
sword
with
with
the
this,
so
this
is
my
bias.
A
I've
always
taken
the
approach
that
smart
contracts
are
very
much
a
double-edged
sword
and
they
cut
both
ways,
and
I
mean
we've
seen
that,
like,
like
all
the
innumerable
amount
of
hacks
that
have
that
have
resulted
in
money
lost
like
that's
one
advantage
of
not
building
a
smart
contract
of
instead
taking
that
business
logic
and
putting
it
into
a
javascript
application
like
I
do
with
the
token
liquidity
app
that
has
had
bugs
and
when
it
has
a
bug,
I
shut
it
down
and
I
tell
everybody:
don't
use
it
and
then
I
fix
the
bug
and
then
I
bring
it
back
up.
A
So
it's
very
much
like
a
traditional
piece
of
software
and
that's
why
we
don't
have
you
know
people
running
like
exploiting
a
bug
and
just
like
draining
the
entire
app,
because
I
have
the
ability
to
actually
just
turn
it
off,
and
so
these
these
smart
contracts
that
that
you
know
can't
be
turned
off
by
anyone,
especially
a
state
actor
like
they're
great.
But
I
as
a
as
a
software
developer,
who
brings
things
to
production.
A
A
Well,
I'll
open
it
up
to
any
further
discussion.
If
anybody
has
anything
else,
they'd
like
to
talk
about.
D
A
Yeah,
that
was
a
good
article
that
was
on
read.cash
and
he
wrote
about
sort
of
a
another
twist
on
d5
of
being
able
to.
I
read
that
article
because
it
because
it
definitely
has
impacts
to
the
psf
token.
I
would
like
the
the
the
minting
of
ideally,
I
would
love
to
have
the
minting
baton
for
creating
psf
tokens
held
by
a
multi-signature
wallet
so
that
no
one
person
can
can
mint
new
tokens
and
that's
not
the
situation.
A
However,
we
mitigate
that
issue
because
the
psf
token
is
not
particularly
important
if
there
was
a
hack
like
it.
Let's
say
you
know
the
private
key
got
lost
or
stolen
or
whatever
it
doesn't
matter
like.
We
would
just
create
a
new
token
air
drop
it
to
all
the
existing
token
holders
and
change
all
the
software
to
use
the
new
token-
and
you
know
problem
fixed.
A
So
that's
how
we
mitigate
that
issue,
but
it
would
be
great
if
we
had
a
smart
contract
on
the
chain
that
everybody
could
see
that
nobody
could
tamper
with
that.
You
you
put
bitcoin
cash
in
and
you
get
a
token
out,
and
I
think
this
is
one.
One
reason
why
I'm
really
excited
about
this
token
bridge
is:
if
we
could
have
our
token
transfer
across
blockchains,
then
we
could
essentially,
like
you
know,
we
could
pick
one
of
those
chains
to
be
our
main
chain
based
on
desirable
features
to
to
create.
A
A
D
Do
you
plan
some
pcf
nft
tokens
like
tokenizing
these
positions
like
ceo,
ct
or
something
something
we
just
distribute
everything
so
yeah.
If
somebody
want
to
contact
the
the
this
pcf
dao
manager,
you
don't
need
to
know
his
address
or
something
yeah.
A
A
Well,
yeah,
I
mean
I'm
glad
you
brought
that
up
stoin,
because
I'm
still
like
really
inspired
by
your
work
at
the
last
hackathon
with
nft
tokens
and
using
that
as
sort
of
a
decentralized
register.
D
A
Yeah
I
mean
in
this
organization
I'd
like
it
to
be
more
horizontal,
but
but
I
I
see
the
advantage
of
that
and
I'd
like
to
tie
your
work
with
the
nfts
and
the
decentralized
register
into
the
work
I'm
doing
with
the
unsensible
publishing,
because
that
would
be
another
like
great
way
to
because
that's
the
problem
with
ipfs
hashes
and
I
have
like
a
partial
solution
to
that
to
make
them
easily
accessible.
A
But
with
your
nft
and
decentralized
register
idea
that
would
be
like
that
could
be
much
more
human,
readable
and,
like
you,
could
just
type
something
into
the
browser
and
and
like
have
it
magically
appear.
So
yeah
there's.
Definitely
a
lot
of
room
for
nfts,
particularly
with
the
work
that
you've
been
doing.