►
From YouTube: PSF TC Meeting 1/19/22
Description
Technical Steering Committee Meeting for Jan. 19, 2022
B
All
right
welcome
everybody.
Thank
you
for
watching.
Thank
you
for
joining
the
people
who
are
here.
My
name
is
chris
troutner,
and
this
is
the
permissionless
software
foundation,
technical
steering
committee.
It
is
wednesday
january
19th
2022
at
8
a.m.
Pacific's
time,
let's
go
ahead
and
do
a
quick
round
of
introductions
before
we
jump
into
the
agenda.
As
I
said,
I'm
I'm
chris
shatner,
I'm
the
head
janitor.
B
Why
don't
you
kick
us
off?
My
name
is.
D
D
Alright,
my
name
is
aaron
shoemaker
and
I
work
with
nfts
and
vr
and
working
on
how
I
can
integrate
psf
software
into
that
world.
E
B
So
as
always,
our
agendas
are
filed
as
github
issues,
so
you
can
find
them
after
this
recording
at
on
github.com
under
the
permissionless
software
foundation
group
in
a
repository
called
tsc
for
technical
steering
committee
and
then
click
on
this
issues.
Tab
and-
and
we
have
a
date
for
the
meeting.
So
this
is
the
agenda,
so
this
is.
These
meetings
are
basically
an
opportunity
for
us
to
celebrate
our
technical
achievements.
Every
couple
weeks
we'll
go
through
the
agenda,
real,
quick
and
then
we'll
open
it
up
to
a
round
table.
B
I
know
stoian's
got
an
update
on
the
multi-sig
minting
looking
forward
to
hearing,
so
let's
go
ahead
and
go
through
this
agenda.
Real,
quick.
First
of
all
public
service
announcements,
the
slp
db,
the
the
the
older
indexer
that
tracks
slp
tokens
is
is
in
its
death
throes.
I
can't
seem
to
keep
it
up.
It
falls
over
about
twice
a
day
now,
sometimes
more,
and
it
takes
it
time
like
an
hour
or
so
to
to
catch
back
up
and
pick
itself
up
mostly
or
exclusively.
B
This
is
due
to
flex
usd
transactions
on
the
on
the
on
the
blockchain,
they're
they're,
so
complex.
That
that
an
slpdb
even
running
with
32
gigabytes
of
memory
runs
out
of
memory
and
has
a
hard
time
processing
these
transactions.
So
it's
very
much
instead
throws.
That
means
that
the
token
liquidity
app
at
psfoundation.cache
is
very
sketchy.
So
if
people
are
trying
to
cash
in
psf
tokens
or
purchase,
psf
tokens
just
know
that
that
it
might
not
go
through.
B
If
you
happen
to
do
it
at
a
moment
in
time
when
slpdb
is
is
struggling.
So
if
this
does
happen
to
you
reach
out
to
me
via
dm
with
telegram,
you
need
to
do
it
within
24
hours
if
your
exchange
doesn't
go
through
because
I'll
need
to
verify
it
with
the
logs.
So
if
you
don't
contact
me
within
24
hours,
you're
not
going
to
get
a
refund
so,
and
you
need
to
have
a
transaction
id
that
I
can
verify
with
the
logs.
So
just
generally
avoid
avoid
exchanging
psf
tokens.
B
If
you
can,
that's
that's
the
main
takeaway,
but
if
you
can't-
and
something
goes
wrong
reach
out
to
me-
also,
the
reimbursement
search
is
going
to
be
slow
because
they're
coming
from
a
multi-signature
wallet.
So
I
have
to
get
multiple
people,
I
don't
have
control
over
it.
I
have
to
get
multiple
people
organized
in
order
to
issue
a
reimbursement.
D
I
I
saw
some
of
this
stuff
in
the
psf
slp
telegram
chat
where
you're
talking
like
the
community's
talking
about
flex
usd,
and
you
were
talking
about
the
it's,
the
airdrops
that
are
causing
it
to
be
such
a
large
coin.
B
Yeah
indirectly,
the
air
drops
are
an
issue
like
it's
more
of
a
user
experience
issue
a
ux
issue
where
they're
dropping
like,
I
think
it's
every
hour.
They
drop
an
interest
payment
to
holders
of
the
coin,
and
so
that
makes
wallet
software
really
struggle
because
it
introduces
this
huge
computational
load
to
process
all
those
utxos
yeah.
F
B
F
B
Simply
won't
process
your
coins
and
they'll,
look
like
they
disappeared,
so
definitely
do
not
use
flex
usd
with
wallet.fullstack.cache.
I
don't
even
know
what
wallet
software
can
competently
handle.
That
that
token,
I
just
I'm
not
aware
of
what,
if,
if
there's
some
go-to
wallet
software
that
people
use
for
that
coin,
I
don't
know
what
it
is.
D
Yeah,
okay
and
you've
found
a
solution
for
that
right.
Are
you
going
to
talk
about
that
later.
F
B
B
It'll
create
a
transaction
with
like
hundreds
of
inputs,
and
so
slpdb
has
got
to
hold
every
input
in
memory
and
check
the
dag
and
do
all
this
computation
and
it
ultimately
freezes
and
falls
over,
and
so
that
that's
indirectly
that
doesn't
have
anything
to
do
directly
with
the
with
the
token
air
drops
it
it's
sort
of
indirectly
it's
when
someone
goes
to
actually
spend
those.
B
Right
right-
and
this
is
happening
to
every
slp
db
in
the
world,
so
I
think
I'm
only
aware
of
one
that's
actually
running
on
a
system
with
more
than
32
gigabytes,
and
I
know
that
that's
struggling
as
well,
but
I
I've
operated
about.
I
operate
about
five
of
them
and
I'm
watching
them
all
struggle
and
they
all
have
32
gigabytes
of
ram
on
a
dedicated
machine.
And
that's
that's
still
not
enough.
D
B
Yeah
yeah,
so
yeah,
so
slpdb
is
dying,
which
I'm
going
to
talk
about
move
into
this
psf
core
software.
Before
I
get
into
the
indexer,
the
cash
stack
how-to
setup
videos
have
been
updated.
So
if
you
go
to
the
ps
foundation,
dot
cash
click
on
the
menu
there's
a
video
section
and
that
section
has
been
updated
or
it's
it's
in
the
process
of
being
updated.
I've
been
spending
this
last
week
on
this
devops
and
infrastructure.
B
Section:
there's
walk
through
videos
on
how
to
set
up
the
the
back
end
of
the
cash
stack.
So
if
this
is
on
the
blog
that
this
devops
and
infrastructure
section
is
focusing
on
this
global
backend
showing
how
to
set
up
the
full
node,
the
fulcrum
indexer,
the
slp
indexer
I'll,
be
adding
videos
on
how
to
set
up
bch
api,
an
ipfs
bch
service
provider,
so
that'll
be
the
full
global
back
end,
I'm
hoping
by
the
end
of
next
week,
we'll
I'll
have
like
walk
through
videos.
B
And
for
those
people
who
want
to
set
up
the
new
slp
indexer,
I
just
added
that
video
here
at
the
end
on
how
to
set
up
the
you'll
you'll
need
to
have
a
full
node
running
before
you
can
run
that
because
it
depends
on
it,
but
but
yeah.
That's
a
new
video
on
how
to
set
up
and
install
the
the
psf
slp
indexer
and
in
those
videos
I
introduce
this.
B
So
all
that
information
is
there
chris.
So
can
all
of
this
run
on
that
raspberry
pi?
Maybe
I
wouldn't
recommend
it
in
in
the
videos.
One
of
the
first
videos
that
I
introduce
here
is
this
reference
implementation,
a
400
desktop,
run
it
with
32
gigabytes
of
ram
and
a
one
terabyte
hard
drive.
So
that's
that's
the
intended
hardware
for
for
the
back
end
here.
So.
B
Right,
yeah
yeah,
a
400
desktop,
can
run
all
the
software
that
we
produce
and
there's
no
software
purchases
needed
to
be
made
right.
Just
that's
the
one
purchase
everything
else
is
free
and
open
source.
Excellent.
Thank
you.
Chris
yeah
yeah,
thanks
for
asking
the
question
yeah,
and
so
the
future
videos
are
going
to
be
added
to
this
beginner
javascript
and
I'm
going
to
introduce
the
the
pi
400
so
for
people
who
don't
want
to
which
is
a
100
raspberry
pi
computer
in
a
keyboard
format
that'll
be
able
to
run
everything
above
this.
B
This
line,
this
ipfs
network
line,
but
which
is
referred
to
as
the
local
backend
and
the
front-end
software
and
so
that'll,
be
the
next
series
of
videos
and
then
ipfs
is
used
to
connect
those
two.
So
I'll
get
it
more
later.
We.
D
D
Okay,
we
got
a
dream
probe
says:
is
it
possible
to
filter
out
or
move
to
move
slp
to
a
new
chain?
Maybe
x,
ecash
or
xpi?
Does
another
service
cover
this
and
then
they
say
frogs
still.
B
Yeah,
so
for
the
first
question,
slp
can
run
on
any
blockchain.
Someone
just
has
to
do
the
work.
So
that's
what
it
comes
down
to.
I
am
syncing
the
the
new
psf
slp
indexer
on
the
ecash
chain
right
now,
so
because
those
two
chains
are
so
similar,
you
know
pretty
much
all
the
software
works
across
them,
so
I
so
yeah
I'm.
I
am
sinking
one
on
the
e
cash
chain
right
now,.
B
Okay,
so
that's
that
so
the
alpha
release
of
the
psf
slp
indexer
is
live.
Api
and
docs
are
available
at
psf,
slp
indexer.fullstack.cache.
So
that's
this
this
url
here.
So
this
is
like,
if
you,
if
you
follow
that
video
and
set
it
up.
This
is
the
rest
api
that
you
would
use
to
interact
with
it
and
in
particular
it's
these
five
or
four
end
points
where
you
can
get
an
address
balance.
B
You
can
get
a
transaction,
so
an
address
balance,
and
this
shows
an
example
of
what
comes
back
utxos
transactions
and
balances
associated
with
a
with
an
address.
There's
a
get
transaction
data
which
returns
like
a
hydrated
json
object
with
token
info,
so
the
inputs
and
the
outputs
have
addresses
and
token
quantities
in
there
and
then
there's
a
there's,
an
endpoint
just
to
check
on
the
status
of
the
of
the
indexer
to
see
if
it's
fully
synced
and
then
there's
an
endpoint
for
token
stats.
B
So
you
can
look
up
like
how
many
tokens
are
in
circulation.
How
many
tokens
have
been
burned?
When
was
the
token
created?
You
know
just
details
about
the
token.
B
So
that
is
up
in
live
people,
it's
it's
free
and
it's
set
with
a
rate
limit
of
two
requests
per
second,
but
it's
not
going
to
stay
up
forever.
This
is
just
basically
a
demo
and
it's
it's.
It's
still
alpha
software.
So
it's
going
to
change
rapidly
so
for
people
who
want
to
really
just
dive
in
and
learn
to
work
with
this
new
indexer,
you
know
everything's,
there
everything's
ready
to
kick
the
tires
and
take
it
for
a
test.
Drive
awesome.
B
I'm
also
like
officially
making
the
this
new
index
for
part
of
the
core
software.
So
so
it's
not
going
to
have
a
separate
section
anymore
in
the
agenda.
It's
just
going
to
be
part
of
the
core
software
section,
so
I've
already
started
moving
forward
because
slp
db
is
basically
dead.
It's
not
so
much
that
the
new
indexer
is
ready.
B
It's
that
slpdb
is,
is
in
its
death,
throw
so
so
we
just
can't
afford
to
wait
any
longer,
so
I'm
rapidly
replacing
the
code
in
bch,
api
and
bchjs
with
calls
to
the
to
the
new
indexer.
So
I've
got
links
to
the
the
api
documentation
here.
So
in
bch
api
there
is
a
psf
slp
section
that
shows
how
to
interact
with
the
new
rest,
api
endpoints
on
dch
api
and
then
at
vchjs.fullstack.cache.
B
There
is
this
new:
what
is
it
psf,
slp
class
that
incorporates
those
end
points
and
right
now
it's
pulling
from
that
that
demo
site,
so
so
people
don't
need
to
run
their
own
index
or
they
can
just
use
bchjs
to
interact
with
it
and
get
that
new
data
and
everything
so
actually
bchjs.
B
B
And
then,
finally,
I
don't
know
if
I
announced
this
last
meeting,
but
but
psf
bch
wallet
our
command
line
wallet.
Has
these
new
message
check
message
read
and
message
send
commands,
so
you
use
message:
send
to
send
an
end-to-end
encrypted
message
to
another
bitcoin
cash
address
message
check
to
check
if
you
have
any
messages
that
have
come
in
and
then
message
read
to
read
a
message
to
decrypt
it
and
read
it
on
screen.
B
So
this
is
using
our
pay
to
write
database
to
hold
the
encrypted
messages
when
they're
in
transit,
and
so
this
is
the
new
way
we're
doing
it.
I'm
pretty
excited
about
having
this
just
basic
end-to-end
encrypted
messaging
in
the
same
app
as
the
ability
to
send
tokens
and
and
money.
So
that's
pretty
exciting.
B
So
really
like
a
lot
of
my
focus
or
all
of
our
focus
me
and
gary
and
daniel
over
the
next
few
weeks
is
just
going
to
be
refining
this
bringing
in
the
new
indexer
the
new
slp
indexer
and
then
just
refining
all
this
code
to
work
with
the
new
indexer
and
and
work
with
this
with
this
new
web
3
architecture,
where
the
the
that
wallet
that
web
wallet
is
going
through,
the
ipfs
network
to
reach
the
backend
software
and
so
ipfs,
is
acting
like
a
bus
for
that
information.
D
See
this
is
exciting
because
I
I
think
this
is
the
direction
where
wallets
are
headed,
where
you
have
your
money,
you're
you're
doing
your
messaging.
I
think
eventually,
we're
gonna
see
media
players
as
songs
get
put
beyond
nfts,
and
then
your
wallet
can
call
the
asset
from
the
nft
to
stream
the
music.
You
know
like
yeah,
I
you
know
it's
all
coalescing
into
one
thing
and
just
starting
with
the
messaging
is
great.
It's
excellent.
B
B
You
know
like
the
whatever
that
nft
unlocks-
and
you
know
like
we'll,
be
able
to
just
with
these
two
things.
Tokens
and
and
encrypted
communication
like
we
can
build
off
of
that,
like
the
whole
range
of
use
cases.
B
Okay,
so
the
pay
to
write
database
has
been
we
we
just-
I
just
incremented
the
database
name
so
to
from
three
to
four,
and
so
it's
a
new
year.
We
have
a
new
database.
There's
not
really
there
wasn't
any.
I
looked
through
all
the
data
and
there
wasn't
really
anything.
B
You
know
application
critical
at
that
point,
so
it
seemed
like
a
good
time
to
to
just
throw
the
old
stuff
away
and
start
a
new
database.
Normally
we'd
be
a
little
more
careful
about
that.
You
know
going
forward,
but
so
we've
got
a
new
database
for
the
new
year.
B
It's
a
clean
break
and
it's
also
using
our
ipfs
private
network
everything's
operating
on
a
private
version
of
ipfs,
and
so
it
was
easier
to
just
bring
the
data
to
do
new
database
rather
than
try
and
bring
the
data
across
from
the
old
way
of
doing
it
on
the
public
ipfs
network
and
the
new
way
of
doing
it
on
the
private
network.
B
So
this
just
something
to
be
aware
of
people
are
running
the
pay
to
write
database
locally.
You
should
you
should
update
it.
Do
get
pull
update
the
new
code
and
it'll
automatically
start
using
the
new
database.
D
So
one
of
the
errands
I
know
is
running
running
that
so
go
ahead
and
update
aaron.
We
got
like
18
errands
in
the
psf
now.
F
B
Okay
and
then
quick
updates
on
the
token
decks,
there
are
new
examples
for
ecash
in
the
bchjs
examples
repository.
So
it's
again
in
github,
under
the
permission
of
the
software
foundation
group,
the
repo
is
called
bchjs
examples,
there's
an
ecast
directory,
and
so
we've
just
got
some
examples
to
create
an
ecash
wallet,
check
the
balance
of
the
wallet
and
send
some
e
cash.
B
I
just
added
these
because
the
two
main
changes
that
they've
made
are
the
redenomination
and
the
address
format,
and
so
I
just
wanted
to
make
sure
all
the
bch
js
software
still
worked
with
directly
with
the
full
node
and
it
does
so
the
the
changes
that
haven't
really
impacted
the
low
level
of
the
code.
So
this
is
now
that
I've
done
this.
I
have
a
great
deal
of
confidence
moving
forward
with
the
ecash
decks.
D
I
was
worried
about
that.
Redenomination.
B
Yeah,
I
was
too,
I
wasn't
sure
if
it
like
actually
was
done
at
a
very
low
level,
with
the
full
note
or
if
it
was
really
just
like
syntactical
sugar.
It
turns
out
it's
really
just
syntactical
sugar,
yeah
and
so
gary's
working
on
the
second
part
of
the
three-part
trade
process
and
and
daniel
will
be
shortly
starting
a
user
interface
for
for
browsing
orders
on
the
decks,
so
that'll
be
exciting.
I'm
looking
forward
to
that.
B
And
that's
the
agenda,
I'm
going
to
go
ahead
and
stop
sharing.
So
those
are.
Those
are
the
updates.
A
lot
lots
of
major
changes.
Lots
of
code
is
in
flux,
mostly
because
of
this
new
slp
indexer.
It's
definitely
got
some
limitations
and
some
bugs
it's
going
to
be
it's
going
to
be
rocky
but
yeah.
I
encourage
people
to
ask
questions
on
the
telegram
channels
and
participate
in
and
just
playing
with
it,
giving
giving
feedback.
D
Awesome
yeah
please
play
play
away
people
I
need
to
get
through
the
videos
and
start
playing
myself
when
I
get
some
time
here.
B
C
Okay,
so
can
you
see
this
yeah
okay,
so
I
made
pretty
good
progress,
I'm
very,
very
close,
but
not
done
so
as
an
example,
when
you
run
the
code.
C
So,
just
to
to,
can
you
see
this
or
it's
too
small?
I
can
see
it
fine,
yeah,
okay,
so
I
think
I
created
like
incomplete
transaction
and
for
the
for
the
outputs.
C
If
you
can
see
it's
already
pretty
properly
multisig
redeem
script
and
what
we
want
to
achieve
is
this
redeem
script.
Like
everybody,
maybe
know
the
utxo
like
this
script,
it's
just
a
fourth
programming
language
which-
and
this
is
the
help
c-
reverse
police
notation.
So
there's
no
brackets
there,
you
just
put
something
in
the
stack
and
get
it
from
there.
So
the
redeem
script
is
just
getting
the
three
something
from
the
stack
after
this
putting
in
the
stack
these
five
public
keys
and
after
this
executing
multi-check
signature.
C
So
what
we
want
to
put
this?
What
so
this
three
stuff
that
we
want
to
put
are
the
three
signatures
so
already
creating
pretty
nice
like
valid
signatures.
C
A
A
C
C
C
Just
a
second,
it's
too
big
sure
so
next
up,
we
need
this
to
sign
the
transactions
in
in
you,
your
usual
code.
You
use
this
transaction
builder
sign
and
you
give
it
a
key
pair
and
usually
the
redeem
script
is
empty,
but
this
thing
does
not
work
with
the
multisig.
C
We
need
to
put
instead
of
this,
this
three
signature
that
we
have
plus
we
need
to
put
this
thing
there,
so
I
I
researched
the
code
for
the
transaction
builder
and
what
is
pretty
much
doing
this
guy
he's
it's
using
this
psf
library,
so
I
have
to
see
recreated
the
sign.
C
So
everything
you
need
to
do
is
just
use
this
hash
for
cache
signature,
very,
very
hidden
function
and
what
you
give
it
is
just
the
input
index,
so
the
number
zero,
or
something
something
you're,
giving
this
redeem
script.
What
which
was
the
array
of
the
five
public
keys
and
the
amount
and
what
kind
of
signature
algorithm
you
want.
C
It's
this
ecliptic
code,
okay
and
after
this
this
this
sign,
which
is
a
function
on
the
easy
pair,
okay
and
after
this
yeah,
some
buffer
like
magic
to
make
it
look
more
like,
for
example,
it's
putting
there's
some
from
the
beginning
of
the
bitcoin.
There
was
some
error
with
the
signature,
so
you
need
this
op
0
in
the
beginning,
always
it's
not
needed
because
it
means
put
zero
numbers
in
the
stack,
which
is
pretty
much
nope
no
operation
but
yeah
right.
C
So
the
signature
is
created
very
correctly,
so
the
now,
the
only
missing
part,
is
how
to
put
this
ready
signature
data
in
the
transaction
scripts.
C
Even
if
I
have
this
in
the
code
like
I
so
after
you,
you
create
these
three
signatures.
C
B
That
encode
function
there
is
there's
a
couple
different
ways
to
call
it.
I
know
I
remember
messing
with
the
script,
because
this
what
I
I
don't
know
if
this
is
the
issue
that
you're
running
against,
but
it's
just
a
tip
like
in
the
script
class
like
bchjs,
has
a
all
those
class
libraries
there's
a
script,
there's
a
script
class
yeah
and
there's
it's
not
in
that
multi-sig.
B
But
there's
like
an
encode
and
in
code
two
and
the
the
original
encode
uses
the
minim
like
minimum
push
data,
which
is
some
sort
of
bip
standard,
but
it
screws
up
the
it's.
No
because
it's
not,
I
don't
think
it's
part
of
the
multi-sig
it's
in
the
the
actual
script
class.
B
B
So
in
code,
two
is
used
when
you're
working
with
the
op
return
for
for
for
slp
tokens,
because
that
first
encode
will
screw
up
the
op
return
and
make
an
invalid
slp
transaction,
and
the
difference
is
that
encode
follows
the
minimum
push
data
standard
and
code.
B
Two
does
not,
and
I
had
to
create
that
in
code
two
so
that
I
could
do
some
low
level
slp
stuff,
and
so
I'm
just
throwing
that
out
there,
because
I'm
wondering
if
maybe
something
like
that
is
happening
here,
which
is
why
your
your
stuff's
not
appearing
in
in
the
actual
transaction.
F
B
C
B
Pretty
this
is
awesome.
Research
stan.
Thank
you
for
doing
the
steep
dive
because
yeah
this
is.
This
is
definitely
very
specialized.
Knowledge.
D
So,
are
you
putting
the
the
multisig
into
the
redeem
strip
before
you
put
the
transaction
on?
Is
that
what
you
were
saying.
C
Just
maybe
okay,
it
was
a
little
high
level
stuff,
so
maybe
for
the
other
viewers
too,
we
need
to
explain
a
little
more.
Do
we
have
time
yeah
yeah,
so
I
will
just
go
to
the.
B
So
this
is
this:
is
andreas
antonopoulos's
mastering
bitcoin
book
and
yeah
yeah
modified
for
bitcoin
cash?
Definitely.
D
Because
I
know
the
transaction
gets
hashed
before
the
signature
is
added,
and
that
is
added
to
the
to
create
the
signature.
C
This
is
too
complicated,
so
I
will
show
maybe
just
a
simple
one,
and
it
will
be
more
easy
to
just
show
a
simple,
a
simple
transaction
which
is
not
multisick
in
the
multisig,
and
we
can
compare.
What
we
need
to
do
will
be
okay,
like
this
yeah.
C
So
if
you
want
to
create
a
transaction,
you
need
to
specify
the
input
for
the
transaction,
the
input,
utxos
and
the
output.
So
we're
doing
this
with
this
transaction
builder.
C
C
You
will
need
like
sop
data
to
be
the
output
zero
and
you
need
to
send
some
like
dust,
just
a
small
amount,
and
if
you
do
this,
like
in
usual
stuff
here
for
the
output,
you
just
put
there
the
the
address
which
will
receive
this
one,
the
the
output.
C
C
Yeah
and
for
the
in
order
to
spend
the
funds
the
the
inputs,
you
need
to
sign
them
yeah
and.
F
C
This
case,
you
need
a
key
pair.
If
you
remember
our
previous
week
conversation
about
the
signing,
you
need
private
and
public
key,
and
so
this
is
like
usual
code.
You
just
sign
with
key
pair
and
for
redeem
script.
You
don't
need
anything.
C
And
same
for
the
so
yeah,
this
is
how
you
usually
use
the
non-multisig
transactions,
but
if
you
want
to
so
what
is
this
doing?
So
the
transactions
is
looking
something
like
this
one
like
you
can
see.
This
is
the
the
op
return,
the
sop
data,
and
here
you
have
just
the
the
simple
like
decryption
or
something,
but
when
it's
multi-sick
you
need
several
guys
signatures
right.
F
C
So,
instead
of
this
simple
way
is
my
code,
so
when
you
put
when
you
sign,
you
just
cannot
have
one
key
pair.
C
You
need
three
signatures
and
you
need
to
put
this
in
some
specific
format.
So
this
is.
This.
Is
the
one
signature
two
signature,
three
signatures,
not
just
one
public
private
key
and
also
you
need
to
tell
him
how
to
use
this
three
signatures
to
sign.
So
you
tell
him:
okay,.
C
C
This
will
be
concatenated
with
this
one,
so
this
is
the
one
two
three
and
up
three
and
one
two,
three
four
five
public
keys.
Okay
and
you
tell
them-
this-
will
be
check
multi
seek
operation,
so
it
will
use
all
of
this.
This
plus
this
to
to
sign
to
check
the
signature.
In
fact,
it
will
check
with
this
public
keys
and
this
signature.
Is
this
a
valid
transaction?
C
D
C
C
Yeah
yeah,
I
hope
it's
a
little
complicated
to
to
explain
it.
I'm
also
still
learning.
So
if
you
want
more
information,
this
bitcoin
book
is
a
good
start.
D
And
let
me
switch
back
over
for
us
here,
get
back
to
the
obs
window
or
yeah
there
we
go
and
for
those
who
do
want
more,
we
do
a
podcast
called
roots
up
crypto
and
code
where
stoian
was
on
last
week
and
we
were
going
over
smart
contracts
and
we
are
going
to
do
some
more
smart
contracts
tomorrow,
but
that
will
definitely
be
a
subject
that
we
cover
in
depth
and
going
into
m-death
how
bitcoin
transactions
work,
how
the
signatures
work.
I
think
that's
a
great
idea
for
an
episode.
D
You
can
check
that
out
on
shoemaker360
on
youtube
or
we
do
have
a
telegram
chat,
so
you
can
jump
into
that.
We
try
to
keep
some
of
that
stuff
separate
from
all
the
psf
stuff
that's
going
on,
but
with
that
we
go
and
we
get
our
hands
dirty
with
the
code.
A
lot
more
and
we're
gonna
get
you
on
there
pretty
soon
here
chris,
to
show
some
of
this
stuff.
B
Yeah
yeah
yeah
I've
been
watching
some
of
the
episodes.
It's
good
stuff
well
yesterday,
and
thank
you
so
much
for
walking
us
through
that.
I'm
I'm
I'm
because
the
the
op
return
for
the
slp
stuff
is
very
similar
where
you're
you're
taking
like
an
op
code
and
then
some
data
and
some
data
and
some
data
and
you're
pushing
it
onto
the
stack
like.
I
definitely
check
out
that
encode
two
function,
because
that
could
very
well
be
if
it's
like
it
might
not
be
the
issue,
but
it
yeah.
B
It's
definitely
smells
like
you
know
it
could
be
an
issue
to
me
to.
B
B
B
But
to
do
that,
I
really
want
us
to
have
multi-sig
so
that
there's
a
council,
a
minting
council,
that's
in
charge
of
that's
ultimately
responsible
for
the
number
of
tokens
in
circulation
and
that
shouldn't
be
that
shouldn't
be
under
the
control
of
some
one
person.
F
D
The
stairs
yeah
now
the
multi-sig
is
is
great
in
so
many
different
ways,
and
not
only
can
it
apply
to
business,
but
imagine
the
capability
for
like
gaming,
you
know
collective
gaming
type
stuff,
you
could
you
could
utilize
stuff
for
that.
C
Is
how
to
see
one
of
the
first
thing
if
you
want
to
have
a
dao
de
centralized
organization,
is
multisig
because
yeah
it's.
We
was
joking,
that
this
is
just
how
to
see
a
bunch
of
people
using
sharing
like
a
wallet
together.
B
C
C
D
D
No,
it
makes
sense
and
having
the
ability
to
do
that
on
bch
and
ecash
as
well
as
avalanche,
gives
dows
a
lot
of
versatility,
which
we
really
need
right
now,.
B
Yeah
yeah
yeah,
exactly
the
we
can't.
What
is
it
you
can't?
You
can't
eliminate
the
risk,
but
you
can
decentralize
it.
You
can
spread.
You
can
spread
it
out.
Among
many
people.
D
Yeah
dream
trove
says
would
be
nice
to
also
to
have
the
various
slp
tech.
That's
been
built
like
the
woocommerce
spice
button,
slp
dot
cocktail
cash
shuffle
for
slp
he's
been
very
active
in
the
chat.
Thank
you
for
being
active
and
I
put
the
link
to
the
the
mastering
bitcoin
cash
book
in
the
chat
and
then
the
telegram
so
yeah.
It
would
be
great
to
have
some
of
that
stuff
and
look
into
some
of
that
stuff.
D
It
says
nft
as
access
key
to
audience
for
encrypted
contact
is
definitely
the
future
versus
ownership
of
one-off
content.
You
should
definitely
check
out
stollen's
github
because
he
did
that
for
story,
and
you
just
did
that
for
a
what
do
they
call
it?
A
dev
challenge
with.
D
D
Yeah,
if
you
check
out,
I
saw
you
join
the
roots
up
telegram,
so
just
we
will
be
on
10
a.m,
central
time
and
story
and
we'll
talk
all
about
that
sort
of
stuff.
D
E
All
right,
well,
is
there
anything
else
you
guys
want
to
cover
today
before
we
call
it
a
wrap.
I
just
have
to
say
thank
you
again.
I
mean
without
the
smart
people
in
this
room.
I
would
I
wouldn't
be
able
to
do
anything.
E
E
D
Chris
yeah
we're
we're
working
hard
and
yeah
check
out
the
roots
up,
live
stream
tomorrow,
where
we're
gonna
get
deep
into
the
code,
and
hopefully
chris
will
get
you
on.
I
know
you're
really
busy
with
getting
this
slp
stuff
stood
up.
So
when
you
feel
like
you
have
some
you're
freed
up,
you
know,
let's
get
you
on
for
an
episode.
C
You
have
a
little
like
several
minutes.
I
I
wanted
just
to
show
one
link
about
our
previous
conversation.
Maybe
will
be
interesting,
yeah
for
sure,
and
maybe
for
you,
I'm
not
sure.
So
I
found
it
yesterday.
This
lead
protocol,
so
I'm
still
researching
it,
but
this
stuff
is
interesting.
C
It's
about
the
encrypting
content
like
nft
and
stuff
like
this.
Just
let
me
find
some
at
this,
maybe
elite
protocol.
C
Okay,
I
will,
I
will
share
the
github,
so
everybody
can
search
for
their
own
where
to
put
this
thing
in
the
chat.
C
Yeah,
I
am
on
another
computer.
C
B
Yeah
yeah
so
for
context
for
for
ceramic
is
very
very
similar
to
our
pay
to
write
database
that
the
text
very
very
similar,
except
ceramics,
free
and
the
pay
to
write
database.
You
paid
or
write
to
it
so
them
using
encryption.
So
we
could
do
the
same
thing.
We
could
very
easily
just
like
that
end-to-end
encrypted
messaging.
We
just
added
to
the
clie
wallet.
B
We
could
just
encrypt
a
message
and
put
it
on
ceramic
instead
of
putting
it
on
the
pay
to
write
database.
So
I
mean
really
the
difference
between
what
they're
doing
what
we're
doing.
Probably
just
comes
down
to
you
know
the
the
encryption
algorithm
and
and
what
what
sort
of
blockchain
they
prefer,
which
is
probably
ethereum.
C
C
D
It
is,
I
mean
it
is
really
close
and
I
I'll
jump
drop
the
couple
white
papers.
I
wrote
in
the
roots
up
telegram
chat
for
anybody
that
wants
to
see
that
in
the
psf
social
on
one
of
them
is
an
overview
and
one
of
them
gets
more
into
the
mathematics
on
how
it
can
happen,
and
you
know
love
to
I.
I
know
I
send
them
to
you
as
well
stoian,
and
I
mean
it
yeah
with
with
the
signature
message.
D
B
B
I
anticipate
a
lot
of
synergy
like
I'm
glad
you
guys
are
looking
ceramic,
I'm
definitely
keeping
a
very
close
ion
ceramic
because
you
know
I
keep
coming
back
to
orbis,
I'm
I'm
gonna
like
I've,
I'm
in
this
love-hate
relationship
with
orbis
right
now,
for
so
for
people
who
don't
know
what
I'm
talking
about
orbus
is
a
twitter
clone.
It
uses
the
ceramic
all.
The
data
goes
over.
The
ipfs
ceramic
network
that
would
normally
be
coming
from
the
twitter
servers
and
the
problem
with
orbis
is
that
it's
not
open
source.
B
B
B
Where,
where
ceramic
excels,
is
this
decentralized
mutable
data,
so
data
that
can
change
over
time,
which
is
perfect
for
like
this?
This
sort
of
social
media
application
like
the
twitter
clone
and
like
craigslist,
could
very
easily
like
that,
would
translate
to
the
craigslist
to
the
actual
ads.
That
way,
the
person
who
created
the
ad
is
the
only
person
who
can
edit
it
and
they
can
update
it,
and
it
can
all
be
done
in
real
time,
and
anybody
can
run
their
own
local
ceramic
node.
B
But
then
I
think
where
we
would
add
to
it
and
with
all
this
dex
technology
that
we're
building
is
that,
like
you,
could
you
could
tokenize
goods
on
this
craigslist
and
then
and
then
exchange
them,
and
that
use
case
is
a
little
bit
different
in
that?
That's
where
I
think
the
pay-to-write
database
excels,
because
we
need
that.
That's
sybil
resistance.
B
F
B
It's
not
an
either
or
it's
an
and
in
both
like
we're
going
to
be
able
to
leverage
the
ceramic
tech,
I'm
glad
that
they
have
all
this
money
and
all
these
engineers
and
they're
working
on
that
really
important
use
case,
and
I
think
that
our
more
limited,
restricted
use
case
is
going
to
complement
very
well
in
those
situations
where
you
need
that
extra
sybil
resistance,
where
just
attribution
is
not
enough
like
like
what
they
have
is
attribution
where
everything
uses
keys.
So,
like
you
can't
write
to
my
stream
only.
B
B
That
was
more
of
yeah,
that
was,
that
had
to
do
with
rate
limits
that.
B
B
As
a
bus,
and
so
people
can
just
find
one
of
several
back
ends
to.
F
D
B
Yeah
yeah,
because
what
we
need,
what
we
need
is
a
rendezvous
point.
That's
what
the
blockchain
fundamentally
provides
that
other
solutions
don't
provide
is
like.
I
don't
know
you
and
I
don't
trust
you,
but
I
can
drop
some
data
over
here
on
the
blockchain
and
you
can
access
that
data
and
we
can
use
that
blockchain
as
a
a
way
to
organize
a
trade
yeah.
D
I
see
farmers
markets
really
taking
on
this.
This
tech,
once
it
gets
to
a
stable
place
like
just
makes
a
lot
of
sense.
You
tokenize
your
goods,
you
know
you
can
pre-sell
those
goods
and
then
people
can
come
and
redeem
the
tokens
and
just
pick
up
their
goods.
That
day,
you
know.
B
Yeah,
so
it's
it's
really
that
rendezvous
point.
That's
the
value
that
I
think,
like
the
paid
right
database,
provides
that
the
ceramic
solution
does
not
provide
yeah,
but
but
where
the
ceramic
solution
excels
is
is,
is
more
data
like
large
quantities
of
changeable
data
that
are
secure
in
the
in
the
sense
that
they're
a
true
bit
attributable
so.
B
A
lot
of
room
for
synergy
in
the
future,
I'm
following
the
ceramic
tech
very
closely,
and
I'm
hoping
that
once
we
get
things
a
little
more
refined
like
yeah,
ultimately
blending
something
with
ceramic
like
orbis,
with
our
ability
to
do
money
and
tokens
and
token
exchanges,
you
know
very
efficiently
and
scalable
in
a
scalable
way.
We
can
meet
those
two
ideas
together.
D
C
C
D
I'm
excited
for
what's
happening
with
the
slp
indexer.
I
I
like
the
slp
protocol.
It
is
very
easy
to
use
and
I
think
that
it's
going
to
be
a
lower
barrier
of
the
entry
to
you
know
businesses
than
say
something
like
smart
contracts
on
ethereum,
you
know
and
being
able
to
help
and
develop
that
for
businesses
like
farmers,
markets
like
farmers
in
general.
B
Yeah
yeah
and
so
like
to
bring
this
back
around
to
those
videos.
You
know
in
that
that
400
desktop
I'm
really
looking
at
that
as
like
that's
the
appliance
and
and
I
that
that's
as
a
community
as
the
psf
community.
That's
what
I
want
us
to
come
together
to
refine
the
software
that
lives
on
that
appliance,
so
that,
like
you,
aaron
and
your
geographic
location,
can
set
one
up
to
support
your
local
farmers
market,
and
I
can
set
one
up
to
support
my
local.
B
You
know
island
community,
and
anybody
can
like
the
software
lives
on
that.
It
really
only
takes
one
person
to
understand
how
it
all
works.
In
order
to
support
you
know
tens
or
hundreds
of
other
people
who
can
then
use
that
infrastructure
to
set
up
a
community
currency
and
and
do
whatever
that
community
needs
to
do.
D
And
this
could
be
a
good,
a
good
business
opportunity
for
people
to
actually
make
rack
mountable
cases
with
this
stuff,
like
take
a
rack,
manageable
case
and
build
a
computer
that
that
runs
this,
because
if
I'm
gonna
sell
to
business
I'd
love
to
be
able
to
just
put
it
in
a
rack
in
their
back
room,
and
they
don't
touch
it,
you
know,
or
their
tech
touches
it.
You
know
anything
that
can
be
just
racked
up
like
that.
D
D
C
D
We
have
one
more
comment
down
here.
Of
course,
crazy
money
said
viva
psf.
Thank
you,
crazy
money.
Dreamtrove
says
definitely
any
marketplace
daps.
He
loves
that.
If
you
can
make
permissionless
paper,
you
can
even
bring
it
to
the
amish.