►
From YouTube: PSF TC Meeting 1/5/22
Description
Technical Steering Committee Meeting for Jan. 5, 2022
B
All
right
welcome
everybody.
It
is
january,
15th
2022
our
first
meeting
of
2022.
This
is
the
permissionless
software
foundation,
our
technical
steering
committee
meeting.
My
name
is
chris
troutner.
I
am
the
head
janitor
at
the
psf
and
I'm
joined
with
few
other
members
of
the
of
the
community.
Let's
go
around
and
do
a
quick
round
robin
introduction,
aaron.
Why
don't
you
start
us
off.
A
A
C
D
B
We've
got
quite
a
bit
to
get
through
today,
so
our
organization
is
definitely
growing.
So
historically,
these
meetings
have
been
the
only
meetings
that
we
have
because
our
community's
been
so
small
and
it's
been
an
opportunity
to
for
us
to
celebrate
our
technical
achievements
over
the
la
over
every
two
weeks.
We're
getting
to
the
point
now,
where
we're
covering
so
much
ground
over
a
two-week
period
that
it's
actually
getting
hard
to
keep
these
meetings
under
an
hour.
B
But
let
me
just
dive
in
here
to
the
agenda.
As
always.
Anybody
on
the
call
feel
free
to
interrupt
me
at
any
time.
I
prefer
this
to
be
a
conversation,
but
I
have
no
problem
getting
on
a
soapbox
and
droning
on
if
that's
what's
required.
Anybody
watching
this
like
the
live
stream
on
youtube
or
watching
this
later,
and
you
have
questions
the
best
way
to
reach
us-
is
the
permissionless
software
foundation,
telegram
channel.
B
B
All
right
so
in
terms
of
the
community,
one
of
the
big
updates
is
gary
and
daniel,
and
I
have
been
we've
had
our
own
private
telegram
room
where
we
do
stand-ups
stand-ups
are
an
artifact
from
the
scrum
management
process
for
for
building
software,
and
so
every
tuesday
and
thursday.
We
do
stand
up
where
we
quickly
state
what
we've
been
working
on.
B
If
we
have
any
blocks
and
what
we're
going
to
work
on,
we
are
going
to
now
start
doing
now
that
we've
we're
in
to
a
groove
we've
decided
to
move
those
standups
over
to
the
general
public,
psf
telegram
channel,
so
every
tuesday
and
thursday
gary
daniel,
and
I
will
be
giving
our
updates
as
to
like
what
what
we're
working
on
and
what
our
current
status
is
of
what
we're
working
on.
So
this
is
an
attempt
to
just
be
more
transparent
and
to
engage
the
community
a
little
more.
B
C
B
Right
yep,
just
the
general
psf
chat
room
thanks:
okay,
so
psf
core.
This
is
our
bch
api,
rest,
api,
bchjs,
javascript
library
and
our
gatsby
plugins
for
the
web
wallet.
That's
what
composes
the
psf
core
software
got
a
few
updates
on
that
slp
mutable
data
is
there's
a
link
here
in
the
agenda
to
the
mpm
library.
This
was
sponsored
by
a
launchpad
ip,
which
is
a
patent
agency.
B
So
if
anybody
needs
a
patent
agent
for
their
intellectual
property,
there's
a
link
in
the
npm
library
suggest
you
start
with
them,
but
they
sponsored
the
development
of
this
library
and
it
can
be
used
to
generate
mutable
or
changeable
data
attached
to
an
slp
token.
So,
among
other
things,
this
can
be
used
for
permissionless
token
icons,
but
it
can
be
used
for
a
whole
range
of
additional
use
cases
like
tracking
a
video
game
character
whose
stats
change
over
time
tracking
the
ownership
of
an
nft
that
changes
over
time.
B
You
know
virtually
any
piece
of
data
that
changes
over
time
can
now
be
tracked
by
a
token,
and
so
we've
got
some
links
to
some
examples
of
how
to
use
it.
To
create
a
token
with
mutable
data,
how
to
update
that
mutable
data
with
token
icon
information
and
then
how
a
wallet
or
some
other
app
would
would
then
retrieve
and
read
the
mutable
data
associated
with
the
token
and,
in
addition
to
this,
we've
updated
wallet.fullstack.cache
to
automatically
detect
this
the
the
token
icon
and
display
it
in
the
wallet.
B
So
this
has
been
a
big
feature
long
time
incoming.
This
is
a
hair
on
fire
problem
that
people
are
constantly
asking
about.
So
we
now
have
an
answer
to
the
question.
How
do
I
add
an
icon
to
my
token
and
there's
a
couple
caveats
here?
First,
this
is
not
retroactive.
You
can't
apply
this
to
tokens
that
already
exist.
You
have
to
it's
something
that
happens
when
the
token
is
initially
created
with
that.
First
genesis
transaction.
B
So
that's
a
little
unfortunate,
but
once
this
step
is
taken
during
the
initial
creation
of
the
token
that
mutable
data
and
its
icon,
it's
permissionless
the
only
person
who
can
update
it
is
the
person
who
has
the
private
key
that
controls
the
address,
that
controls
immutable
data
and
they
can
update
that
data
at
any
time.
They
want,
and
so
this
means
that
if
you
have
an
icon
on
your
token,
you
can-
and
you
want
to
rebrand
and
change
that
token
icon.
B
A
That's
awesome,
I'm
very
excited
about
this
and
I
will
be
making
a
video
on
this,
probably
with
my
buddy
out
in
denver.
You
know,
because
we're
going
to
be
trudging
through
different
nft
and
token
protocols
on
different
chains
and
I've
been
excited
about
this
for
a
while.
So
this
is
I
mean
for
the
3d
stuff.
It
means
that
I
can
put
up
a
3d
object
and
then
make
the
uv
file
mutable.
So
you
could
change
the
colors
of
3d
stuff
for
people
and
that'd,
be
that
could
be
cool.
B
C
B
A
D
B
Yeah,
that's
really
good.
It's
significant
yeah,
it's
a
good
question
and
it
right
now
at
this
moment
in
time,
it's
a
significant
amount,
because
we
haven't
done
taken
any
effort
to
try
and
like
optimize
it
in
any
way.
So
it's
pretty
dumb
and
pretty
brute
force
the
way
that
it
it
like.
If
the,
if
the,
if
the
token
doesn't
have
any
it's
just
like
a
normal
token,
it
doesn't
have
any
data.
B
This
is
a
really
good
time
for
me
to
reiterate
the
the
disclaimer
that
the
wallet
does
not
work
very
well
with
lots
of
different
types
of
tokens.
I
I
recommend
that
people
use
our
paper
wallet
to
store
tokens
on
paper
wallets
for
like
long-term
storage
and
only
keep
the
tokens
that
they
like
use
on
a
regular
basis
in
their
wallet,
because
that
will
slow
down
performance
with
the
number
of
wallet
or
number
of
tokens
in
your
wallet.
B
So
right
now
it
is
rough,
and
so
we
need
to
net
like
that.
For
next
steps
is
to
is
to
optimize
that
that
back
and
forth
exchange
to
make
that
a
little
more
efficient
and
then
second
of
all
the
I'll
get
to
this.
But
the
emphasis
is
really
moving,
moving
away
from
the
rest,
api
and
moving
towards
the
ipfs-based
infrastructure.
For
the
for,
like
the
free
and
hobbyist
type
stuff,
we'll
be
able
to
scale
much
better
with
that
technology.
B
But
if
you
have
money-
and
you
can
pay
like
because
rest
apis,
they
require
cloud
infrastructure
that
requires
money.
So
for
businesses
who
want
to
use
this
in
a
business
setting,
they,
you
know
they're
still
the
rest
api
and
that
can
be
optimized
and
it
can
be
done.
But
there's
definitely
we're
going
to
see
a
dichotomy
between
the
people
who
are
paying
for
use
and
people
who
are
not
paying
for
users
we're
going
to
have
very
different
infrastructures
for
those
two
types
of
use
cases.
A
B
Yes,
yes,
and
no
I
mean
it
still
exists,
still
works.
Some
of
the
tokens
give
it
trouble
like,
for
instance,
flex
usd
with
all
their
airdrop
utxos
that
really
electronic
cash
slp
has
a
hard
time
with
that
art.
The
web
wallet
has
a
heart.
Every
wallet
has
a
hard
time
with
that.
So
there's
some
tokens
out
there
that'll
pretty
much
screw
up
every
wallet,
the
flex
usd
being
the
the
biggest
culprit
there,
but
yeah
it
still
exists.
D
Some
clone
of
electron
cache
actual
something
which
they
have
to
see.
They
fix
a
little
they
fixed.
I
mean
the
electronic
cash
wallet
have
problems
with
validating
the
tokens.
It's
a
lot
of
requests
to
these
gs,
plus
servers
to
validate
the
tokens.
I
think
somebody
make
a
clone
which
is
not
doing
this,
so
it's
not
validating
them
on
the
server
side
or
I
don't
know
what,
but
it's
faster
and
it
can
work
with
this
problem.
Problematic
tokens.
D
B
Over
there,
they
forked
slpdb,
and
they
got
it
to
work
with
a
sequel
like.
If
I'm,
I
think,
I'm
right
about
that.
A
nosql
or
sql
a
sql
library
rather
than
mongodb,
and
then
they
forked
electron
cash
slp
and
it
uses
their
forked
version
of
slp
db.
So
it
is
faster,
there's
also
a
lot
more
dependence
on
actor.
Fourth,
so
if,
if
that
makes
your
life
better,
you
know
go
for
it,
it
hasn't
helped.
A
lot
of
people
has
helped
a
lot
of
people.
B
B
This
one's
been
around
for
a
while
yeah,
it's
like
a
preferred
chat
room.
They
have
a
really
tight
integration
with
github
and
anyways
actor.
Fourth
has
a
a
get
her
channel
there.
If
you
want
to
use
her
stuff
and
need
support
as
long
as
you
don't
use
a
token
like
flex
usd
that
has
or
that
has
these
just
ridiculous
dags,
the
original
version
of
electron
cash
slp
will
run
fine,
it'll
figure
it
out.
It's
just
it's.
It's
these
corner
cases.
A
Those
guys
geez,
we
got
some
some
activity
in
the
chat
about
this.
Let
me
go
ahead
and
pull
that
up.
We
got
aaron
sonmen,
says
very
excited
about
the
slp
mutable
data
bit
also
very
excited
about
the
bitcoin
payment
module
so
glad
you
guys
joined
this
group
aaron.
I
think
he's
talking
to
the
other
aaron
in
the
chat.
That's
there.
So
what's
up
aarons
a
lot
of
good
errands
in
the
chat
today.
B
B
You
can
give
it
a
token
id
and
it
will,
if
it
has
an
icon,
it'll
display
the
icon
and
then
it'll
have
two
text
boxes
where
it
will
display
the
immutable
data
if
it
exists,
which
you
can
attach
the
document
url
and
the
mutable
data,
if
it
exists,
which
is
attached
to
the
document
hash
field
of
the
token
and
so
it'll
be
kind
of
a
diagnostic
tool.
So
I'll
talk
about
that
more
once,
once
that's
available.
A
B
Okay,
moving
on
to
the
minimal
slp
wallet
this
this
is
this:
is
the
sort
of
wallet
engine
in
the
web
in
the
web
wallet.
It's
also
used
in
the
psf
bch
wallet
the
command
line
wallet.
So
this
is
essentially
like
our
our
wallet
engine.
It's
it
anytime.
You
create
a
wallet
or
send
money
or
send
a
token.
It's
going
to
invoke
this
this
library.
B
What
this
is
doing
is
it's
running
this
ipfs
bch
wallet
consumer
app,
which
is
then
over
ipfs,
finding
and
selecting
the
most
appropriate
backend
that
it
can
talk
to,
and
so,
and
so
this
is
going
to
allow
us
to
offer.
You
know
for
free
and
free
infrastructure
infrastructure
is
supported
by
the
community
as
a
whole.
So
on
the
one
hand
there
won't
be
some
one
person
to
blame
if
you're
having
bad.
B
You
know
connectivity
issues,
in
which
case
you
know
you
should
go
to
fullstack.cache
and
pay
for
something,
because
if
you're
not
the
product,
then
you
are
the
product
and
but
if
you
are
running
a
hobby
grade
type
system
or
just
building
a
prototype,
real
quick
and
you
don't
want
to
pay
for
professional
service.
This
is
a
great
way
to
get
free
access
to
the
backend
infrastructure.
B
Yeah,
it's
a
great
way
to
dip
your
toe
into
the
water
of
this
new
ipfs
ipfs-based
paradigm,
because
the
next
step
after
this,
if
someone
gets
comfortable
with
this,
the
next
step
is
to
actually
just
run
this
ipfs
bch
wallet
consumer
on
your
own
computer,
which
will
then
allow
you
to
have
full
control
instead
of
relying
on
free
bch.fullstack.cache
to
determine
which
backend
it
wants
you
to
talk
to.
You
have
full
control
over
which
backend
on
the
ipfs
network.
B
You
want
your
app
to
talk
to
and
so
there's
there
will
definitely
be
situations
in
the
future
where,
where
freebch.fullstack.cache
is
down,
but
if
you're
running
this
software
yourself
on
your
own
computer,
you
it'll
never
be
down,
because
you
can,
you
can
just
essentially
scan
the
ip
all
the
nodes
on
the
ipfs
network
and
find
one
that
is
working
and
then
and
then
use
that
one.
So
it
gives
it
gives
you
I'm
trying
to
like
give
stair
steps
for
developers
to
level
themselves
up
as
they
go
down
this
path.
A
B
B
D
B
Be
like
great,
I
think,
for
starting
yeah.
That's
what
I
wanted
to
achieve
is
to
be
able
to
build
single
page
apps,
that
you
can
upload
on
like
file
coin
or
or
the
see
a
home.
What's
that
home
screen,
skynet,
skynet
and
and
yeah,
and
have
these
apps
that
are
just
sort
of
anonymous
and
do
not
need
an
account
and
and
can
tap
into
our
ipfs
infrastructure
in
order
to
to
talk
to
the
backend
infrastructure
that
it
needs
to
do
whatever
it's
doing.
B
All
right
so
moving
on
to
the
jason
rpc
over
ipfs
and
pay
to
write
database
stuff
boy.
I
don't
even
know
where
to
start
with
this,
there's
been
essentially
massive
changes
this
last
week,
massive
basically
everything's
changed
so
sam
rock
who's,
like
the
one
guy
who's
actually
trying
to
use
this
code.
I
apologize
for
for
turning
your
life
upside
down,
but
things
are
running
much
better
after
a
lot
of
these
changes.
B
So,
basically
the
last
two
weeks,
I've
been
doing
a
deep
dive
onto
all
this
stuff
and
in
our
last
meeting
we
talked
about
ceramic
and
I've
been
really
excited
about
this
twitter
clone
called
orbis
that
runs
on
ceramic
and
what
they're
doing
is
very
very
similar
to
what
we're
doing.
But
it's
not
the
same.
B
It
really
we're
using
all
the
same
tech
they're
using
ipfs
we're
using
ipfs
they're
using
the
ethereum
blockchain
we're
using
the
bitcoin
cash
blockchain,
really
not
that
big
of
a
difference
from
a
technical
level,
and
so
it's
been
really.
It
was
really
informative
for
me
to
dive
in
where,
where
we
differ
is
on
the
emphasis
of
the
technology,
they
they're
focused
more
on
mutable
content
like
the
kind
of
content
you'd
use
in
social
media
like
twitter,
whereas
we're
more
focused
on
communication,
so
so
basically
building
a
replacement
for
a
rest
api.
B
That's
that
maybe
not
as
performant
but
is
more
censorship
resistant
and
can
go
over
the
ipfs
network
other
than
those
like
minor
emphases.
Our
tech
stacks
are
pretty
much
identical
and,
and
so
they've
been
struggling
with
all
the
same
issues
that
we've
been
struggling
with
when
it
comes
to
ipfs,
and
so
one
of
the
big
changes
that
they
just
recently
implemented.
I
just
watched
their
lap.
They
have.
B
They
have
community
meetings
just
like
this,
and
I
went
and
watched
their
last
one
and
they
are
switching
from
the
embedded
javascript
implementation
of
ipfs
over
to
the
go
ipfs
implementation,
and
the
reason
for
this
is
just
because
the
javascript
version
is
essentially
treated
like
a
red-headed
step
child.
It's
just
it
is
that's
like
the
official
stance
of
of
protocol
labs
is
that
they've
chosen
to
make
go
ipfs
the
the
primary
reference
implementation.
B
It
gets
all
the
new
updates,
it's
the
cutting
edge
and
then
they
update
the
javascript
stuff
like
when
they
have
time
as
it's
convenient
and
they
have
manpower.
So
there's
always
this
big
lag.
So
that's
one
good
reason
to
use.
Go
ipfs,
but
there's
also
like
a
bunch
of
bugs
in
js
ipfs
like
there's.
This
memory
leak
that
I'm
aware
of
they're,
aware
of
and
there's
ways
to
manage
that,
but
there's
also
just
these
other.
Like
random
issues
like
I
just
discovered
this
major
issue
with
pub
sub.
B
I
just
happened
to
discover
this
because
I
noticed
it
and
then
came
across
some
github
issues,
and
so
it
seems
like
there's
only
a
handful
of
people
that
are
even
aware
that
this
is
an
issue,
but
I
found
so
so
that
basically
right
there
limited
the
ability
of
all
of
our
nodes
to
talk
to
one
another,
and
so
that
was
a
big
problem.
That's
been
going
on
for
a
while
that
I
wasn't
even
aware
of
so.
That's
that's
fixed
now.
B
So
all
the
nodes
are
like
way
like
communicating
way
better
now
and
what
was
this
final
one?
Oh
yeah,
so
we
moved
to
a
private
network,
and
this
is
a
little
controversial.
I
didn't
want
to
move
to
a
private
network,
but
there
are
dragons
even
in
the
go
ipfs
implementation.
There
are
some
serious
bugs.
B
I
got
to
a
point
where
I
was
able
to
rule
out
that
the
source
of
these
bugs
is
our
code.
It's
definitely
something
deep
deep
into
the
ipfs
implementation,
where
the
node
will
like
try
to
connect
to
like
700
or
1000
nodes
at
one
time,
and
so
what
you'll
see
is
the
cpu
spikes
and
the
bandwidth.
Spikes
and,
like
your
computer,
will
freeze
and
I'd
notice
this
in
the
javascript
implementation.
But
it's
also
exist
in
the
go
implementation.
B
It
seems
to
happen
randomly.
Sometimes
it
fixes
itself,
and
sometimes
it
does
not
fix
itself
and
and
at
other
times
like
one
node
will
infect
another
node
I
this
this
is
what
caused
me
to
start
really
doing
all
this
refactoring
is
that
I
was
just
saying,
like
the
en.
Our
entire
network
was
just
going
down
for
no
apparent
reason,
and
it
was
this
and
and
so
whatever
I
still
don't
exact.
No
one.
B
No
one
knows
exactly
what
the
the
root
cause
of
this
is,
but
by
moving
ourselves
to
a
private
network,
we
get
to
sidestep
all
those
issues
we
don't
like
they
just
they
just
go
away
because
it
has
something
to
do
with
our
nodes,
trying
to
interact
with
the
wider
ipfs
network,
so
by
simply
isolating
our
network.
That
issue
goes
away,
and
so
it's
still
ipfs.
It
still
uses
all
the
same
tech.
It's
just
that
our
nodes
can't
talk
to
other
ipfs
nodes
and
we
can
still
get
content
through
gateways.
B
We
can
still
share
content
across
our
network
and
just
for
net,
like
we'll,
probably
eventually
move
away
from
this
private
network
model
as
we
can
and
as
it
does
not
cause
issues,
but
that'll
be
that'll,
be
down
the
road,
so
anyways
I've
got
instructions
here.
It's
just
like
a
little
key,
a
little
piece
of
code
that
you
drop
into
your
directory
and
then
your
nodes
on
our
private
network,
and
so
I've
got
instructions
there.
For
anybody
who
wants
to
spin
up
a
note
on
on
how
to
do
that.
D
B
Yeah
yeah,
so
I'm
glad
you
asked
us
doing
because
what
this
is
mostly
going
to
affect
if
this
thing
comes
up,
I'll
show
it.
But
in
that
that
blog
post
that
I
talked
about
last
week,
I
described
this
new
cache
deck,
where
there's
a
local
back
end
and
a
global
back-end.
So
this
mostly
affects
these
local
and
global
back-ends
on
the
front
end.
There's
this
gatsby
like
I
want.
B
B
Our
emphasis
is
on
these
back
end,
like
we've
got
to
get
these
back
ends
running
properly
before
we
can
even
worry
about
the
front
end
stuff,
and
so
I
think,
if
the
bulk,
especially
if
our
back
end
infrastructure,
if
it
if
it
doesn't,
have
these
problems
and
everything's
running
good,
that's
good
and
then
and
then
we
just
have
to
see
if
these
are
are
significant
enough
issues
for
the
front
end
apps
they
may
be.
I
just
I
don't
really
know
yet
and
then
we'll
have
to
figure
out
our
own
our
own
solutions
to
that.
B
Okay,
so
that's
that
so
I'll
just
leave
this
section
off
by
saying
that,
if
anybody
you
know
is,
is
really
interested
in
ipfs
and
wants
to
understand
this
stuff
at
a
deeper
level.
Please
ask
questions
on
the
psf
channel
or
the
bchjs
telegram
channel
for
our
technical
stuff
and
stuff
yeah
just
ask
questions.
I
I
really.
We
still
have
open
bounties
for
spinning
up
some
of
this
back
in
infrastructure.
B
So
what
I
need
to
do
from
here
is
create
more
videos
and
more
documentation
on
how
to
create
circuit
relays
and
how
to
create
a
bitcoin
cash
infrastructure.
Using
these
new
methods
and
using
this
new
code,
there
are
already
bounties
and
videos
and
for
the
most
part
they
still
apply.
But
basically,
if
anybody
has
questions,
please
reach
out
to
me.
A
B
B
It
uses
it
by
default.
So
if
anybody
wants
to
get
started,
that's
a
nice
thing
is
this
command
line
wallet
you
don't
have
to
pay
to
use
it
it's
using
the
free,
bch
infrastructure.
So
it's
also
a
great
way
to
get
example
code.
If
you
want
to
see
how
we
did
it
here
in
your
own
app,
so
I've
got
this
wallet.
B
It's
got
a
little
bit
of
bitcoin
cash.
It's
got
a
little
bit
less
than
one
psf
token,
and
so
anybody
who's
used
message.fullstack.cache.
This
is
the
same
thing.
The
difference
is
that,
whereas
that
app
used
a
custom,
ipfs
node,
this
is
now
using
the
pay
to
write
database
so
what's
happening
here
is
this
is
the
address
for
my
own
wallet
and
I'm
sending
a
message
with
the
with
the
subject
test
and
the
message.
This
is
a
test.
B
I
think
this
hash
in
it,
and
so,
if
I
pull
up
the
pay
to
write
database
explorer,
we
can
actually
see
that
right
here,
psf
bch
wallet.
This
is
the
latest
entry,
and
so
this
is
what
this
is:
the
data
that
was
actually
entered
into
the
paid
right
database.
Here's
our
encrypted
message
that
can
only
be
decrypted
by
the
person
who
has
the
private
key
for
that
address.
So
it's
end
to
end
encrypted.
So,
even
though
this
date
is
public,
it's
encrypted,
so
it's
okay
and
and
basically
this
is
how
it's
working.
B
You
know
between
one
person
sending
it
and
one
person
reading
it.
So
pretty
happy
with
that.
I
mean
I'm
just
like
we
having
end
to
end
encrypted
messaging
is
so
important
in
today
and
today's
day
and
age
like
I'm.
Trying
to
this
is
such
a
big
milestone,
because
what
I
want
us
is
to
be
able
to
securely
and
privately
transmit
money
securely
and
privately
communicate,
and
then
that
can
those
two
ingredients
can
lead
to
like
more
expressive
ways
of
trading,
whether
it's
icons
or
censorship,
resistant
craigslist
or
whatever
you
want.
A
Now
this
sort
of
thing
is
awesome,
this
just
to
be
able
to
do
this.
I
totally
agree
with
you.
This
is
how
you
move
into
the
future,
and
I
think
there
are
people
that
don't
understand.
It's
not
just
about
censorship
from
the
state
or
government,
but
like
competitors
is
another
form
of
where
you
can
experience
censorship.
People
can
reroute
your
messages
or
rewrite
your
payments
and
really
mess
with
you
and
there
this
happens
all
the
time
in
the
regular
business
world.
A
B
Yeah,
you
know
I
I
I
it's
what's
funny.
Is
I'm
hearing
the
story
over
and
over,
and
so
somebody
knows
somebody
who,
basically,
like
the
bank,
told
them?
No,
you
can't
use
your
money
and,
like
you
know,
you
roll
the
clock
back
five
years
and
that
wouldn't
have
even
been
something
that
was
worth
talking
about
like
that,
would
have
just
been
part
of
business,
but
it's
only
because
things
have
gotten
so
good
with
crypto
that
everybody
in
the
crypto
space
is
so
used
to
like
it
just
works,
and
why
would
why?
B
How
could
anybody
stop
me
from
using
my
own
money
like
that's,
absurd
and
yeah,
and
and
so
now
that
we
have
that
frame
this
new
frame
of
reference
now,
every
time
it
happens
to
somebody
it's
worth
mentioning,
and
it
happens
a
lot.
It
happened
a
lot
before,
but
now
it's
actually
worth
mentioning,
and
so
I
just
love
it.
A
B
D
B
D
B
B
Well,
I
mean
yeah
it
could
every
everything
could
be
done
directly
with
bchjs.
I
mean
it
is
under
the
hood
through
minimal
slp
wallet,
the
main
change
here.
The
only
the
only
thing
that's
like
new
that's
happening
here
is
the
use
of
the
pay
to
write
database,
which
is
using
that
p2wdb
npm
library,
which
is
actually
what
I
was
going
to
talk
about.
Next,
that's
really
the
only
like.
Fundamentally,
that's
the
only
thing.
That's
changed
from
message.fullstack.cache
or
the
functionality
that
exists
now.
D
My
point
was:
is
it
more,
is
it
better
to
be
this
code
to
be
included
like
separately
in
every
of
the
different
wallets
or
or
it
can
be?
Something
like
I
don't
know,
library,
some
common
component
that
can
be
used
in
any
of
this,
so
there
will
be
no
several
copies
of
the
code
or
stuff
like
this
one.
B
Yeah
yeah,
so
there's
there's
a
list
of
software
here,
there's
there's
minimal
slp
wallet,
which
is
our
wallet
engine,
there's
p2wdb,
which
allows
you
to
interact
with
the
pay
to
write
database.
Those
are
both
npm
libraries
there's
also
the
vch
message,
lib,
which
is
an
npm
library
which
does
the
actual
messaging
protocol
in
terms
of
like
signaling
to
someone.
B
They
have
a
message
and
writing
writing
those
transactions
and
those
follow
another
specification
and
then
there's
the
bch
encrypt
lib,
which
is
another
npm
library
that
does
the
ntn
encryption,
and
so
all
four
of
those
libraries
are
used
in
the
psf
bch
wallet
plywallet
in
and
in
the
web
wallet.
So
that's.
D
B
I
agree
I
don't
I
don't
want
to
duplicate
a
bunch
of
code.
I
want
to
make
it
as
abstract
and
easy
to
copy
and
paste.
You
know
like
three
or
four
lines
you
know
as
as
possible,
so
yeah
and
I
mean
it's
a
journey,
so
I'm
pretty
happy
with
where
we're
at
right
now
and
then
this
this
whole
trajectory
of
of
going
from
the
command
line
wallet
to
the
web
wallet
and
because
that's
that's
a
big
shift.
B
There's
a
lot
of
things
that
break
just
from
going
from
node.js
to
to
browser
javascript,
there's
a
lot
of
things
that
can
break
so
yeah
these
those
libraries
I
mentioned
the
encrypt
library
and
the
message,
library
and
minimal
slp
wallet.
These
are
all
compiled
with
browser
fi
to
make
sure
that
they
run
in
a
in
a
browser
environment.
And
so
that's
that's.
Essentially.
B
B
B
But
someone
makes
the
offer
someone
browses
those
and
they
take
one
of
the
offers
and
then
that
original
party
who
made
the
offer,
reviews
it
and
accepts
it,
and
then
that
completes
the
trade,
and
so
we
have
that
first
part
that
offer
making.
We
have
that
working
now
on
avalanche.
We
had
it
working
on
bitcoin
cash,
it's
now
working
on
avalanche,
so
that
whole
workflow
for
the
first
part
of
actually
creating
an
offer
and
getting
out
there
is
done.
So
that's
a
big
progress.
B
D
D
B
Yeah
so
vin
armani's
original
implementation
used
the
the
bitcoin
file
protocol
created
by
james
crane
or
bfb,
and
so
that
stores
this
data
on
the
blockchain
directly,
which
makes
sense
from
like
from
an
app
developer
standpoint.
That's
probably
the
easier
thing
to
do
because,
rather
than
trying
to
deal
with
two
networks,
you
only
have
to
deal
with
one
network
but
yeah.
The
pay
to
write
database
is
just
much
more
convenient
to
use.
B
So,
like
I
said
like
on
a
surface
that
makes
sense
on
a
surface
level,
but
but
this
whole
process
that
whole
bitcoin
files
protocol
that
was
never
fully
baked
james,
abandoned
it
early
on
and
it's
actually
much
more
complex
and
bug
prone
than
than
you'd.
Think
just
giving
a
cursory
look,
so
the
pay
to
write
database
we've
already
gotten
that
to
a
point
where
the
workflow's
much
smoother
and
and
it
can
hold
more
data.
B
B
Right
yeah,
that's
the
fundamental
like
problem
like
this.
This
whole
collaborative
transaction
thing
like
it's
been
around
for
a
long
time.
Vin
definitely
refined
it,
and
I
learned
about
it
from
him
and-
and
he
did
a
lot
of
the
initial
code
that
that
led
us
like
in
javascript
that
let
us
like
really
run
with
this
idea,
but
at
the
heart
of
it
we
need
a
censorship
resistant
database.
B
We
need
a
rendezvous
point
for
the
two
people
in
the
trade
to
to
meet
up,
and
so
that
could
be
the
blockchain
and
if
it's
not
the
previously
there
just
really
was
no
other
option
other
than
like,
like
like
there.
Just
aren't
very
many
censorship-resistant
databases
out
there
I
mean
there
are
today
now
there's
filecoin
and
and
essentially
that's
what
the
pay-to-write
database
is.
It's
a
censorship-resistant
database,
and
so
it's
a
it's
a
natural
fit
for
this.
B
Okay,
well,
I
will
move
on
to
the
okay
and
this
real
quick.
So
it's
it's
after
january,
so
we're
now
officially
starting
work
on
the
ecash
decks,
and
so
the
next
step
there
is
to
we're
going
to
be
able
to
leverage
all
this
work
that
we're
doing
in
the
avalanche
chain
and
for
to
really
kick
off
the
ecash
specific
stuff.
B
I'm
gonna
submit
some
pull
requests
to
bch
api
and
bchjs
to
just
improve
the
support
for
the
ecash
blockchain
in
there
and
make
it
make
it
more
dealing
with
addresses
and
denominations
a
little
better
and
then
we'll
be
able
to
port
all
this
code
that
we're
building
on
the
avalanche
chain
over
to
the
ecash
chain
and
because
we
already
have
it
working
in
bitcoin
cash.
We
know
that
it's
once
we
solve
the
denomination
and
address
issues
with
ecash
it'll,
just
work.
D
B
Yeah
we're
not
all
the
labs
is
already
doing
a
lot
of
that
work
like
like
they
already
have
their
avalanche
js
library,
and
they
already
have
like
examples
and
stuff
gabriel's
doing
a
great
job
with
that
over
there.
So
I
don't
want
to
recreate
their
work.
The
the
I
created
that
separate
directory
in
the
bchjs
examples,
repo
cause,
someone
had
submitted
some
ecash
specific
code
and
it
was
kind
of
stepping
on
the
bch
stuff
and
and
a
lot
of
people
use
those
examples
and
they
don't
care
about
ecash.
B
They
just
want
to
focus
on
pch.
So
that's
why
I
just
basically
moved
some
of
those
files
to
a
separate
directory.
I
do
plan
to
flesh
that
out
as
we
go
and
because
yeah
just
so
that
we
can
give
equal
support
to
both
bch
and
ecash
good
question
but
yeah
in
terms
of
avex.
We
we
have
our
psf
ovix
wallet,
which
is
a
command
line
wallet.
It's
essentially
a
copy
of
the
psf
bch
wallet
but
running
on
avik.
B
So
those
are
we're
using
that
same
that
same
model
where,
like
that
command
line,
wallet's
going
to
be
our
essentially
our
reference
implementation
and
then
from
there
we'll
take
those
features
and
we'll
move
them
up
out
to
the
web
wallet.
But
but
we
don't
we're
we're
essentially
stopping
there.
We're
not
worried
about
the
backend
infrastructure.
For
that
like
we
are
with
bch,
because
all
ava
labs
is
very
well
funded
and
they
have
public
avalanche
nodes
that
we
can
use,
and
so
it's
just
like
that's
just
stuff
that
we
don't
need
to
deal
with.
B
Okay,
so
the
indexer,
probably
actually
the
first
thing.
I
should
jump
down
to
to
frame
all
this
very
last
item.
On
january
1st,
there
was
a
per
I
actually
wow.
I
know
exactly
what
happened
is
someone
was
consolidating
all
their
flex
usd
coins,
and
so
there
were
these
transactions
that
had
like
hundreds
of
inputs
of
little
flex
usd
utxos
and
and
consolidating
them,
and
this
is
what
happens.
This
is
why
flex
usd
is
like
a
problematic
coin
and
it
basically
knocked
all
the
slpdbs
off
the
network.
B
So
I
increased
the
timeout
from
like
30
seconds
to
120
seconds
and
that
that
at
least
a
lot
is
now
allowing
slpdb
to
struggle
forward,
but
but
slp
db
is
like
very
clearly
in
its
death
throws
right
now.
If
I
had
a
system
with
64
gigabytes
of
ram,
it
might
be
a
little
better,
but
most
vpss
don't
offer
that
service.
It's
it's
really
hard
to
buy
a
desktop
with
that
much
ram.
32
is
kind
of
where
everything's
at
right
now.
B
So
if
you
set
that
as
your
reference
implementation
of
32
gigabytes
of
memory,
slpdb
is
like
clearly
in
its
death
throws,
and
it's
just
very
struggling
very
hard
to
maintain
a
sink
to
the
tip
of
the
blockchain,
which
we
knew
this
day.
I
knew
this
day
was
coming.
I've
been
waiting
for
it.
That's
why
we
created
we
started
work
on
the
on
the
this
new
slp
indexer,
so
timing
is,
is
actually
pretty
good.
B
The
I've
been
looking,
I've
been
running
at
the
indexer
and
then
comparing
the
results
against
slpdb
and
in
most
cases,
everything's
exactly
the
same.
There's
a
few
tokens
with
really
weird
dags
and
people
doing
really
weird
things
where
it's
a
little
different,
so
maybe
not
counting
all
the
burns,
definitely
all
corner
cases.
I
need
I'll
need
to
continue
to
look
into
that,
but
for
the
most
part,
the
accuracy
is
looking
pretty
good.
B
I've
built
a
rest
api
that
lets
you
look
up.
The
balance
of
an
address,
validate
that
a
transaction
is
a
is
a
valid
slp
transaction
and
and
get
sort
of
hydrated
transaction
information
like
how
many
tokens
were
in
the
input.
How
many
tokens
are
on
the
output
that
sort
of
thing
and
token
statistics
like
looking
up
the
total
burned
tokens
and
the
total
tokens
in
circulation
for
token,
so
those
apis
have
been
built.
B
The
latest
iteration
of
this
code
is
at
block
704,
000
and
the
tip
of
the
chain
right
now
is
like
722
000.
So
it's
like
I
got
like
20
000
blocks
to
go,
but
it's
only
doing
as
what
I've
noticed
is
these
indexers.
They
start
off
really
fast,
but
then,
as
the
database
gets
bigger,
it
gets
slower,
and
so
now
it's
only
indexing
like
a
thousand
to
two
thousand
blocks
a
day,
which
is
fine
because
there's
only
144
new
blocks
in
a
day.
B
So
I'm
I'm
basically
indexing
a
week
for
every
day
of
processing
time
as
it
gets
closer
to
the
tip
of
the
chain.
It's
pretty
slow
but
anyway,
so
we'll
get
there.
But
it's
it's!
This
last
20
000
blocks
is
probably
gonna
take
a
few
days
to
get
there.
So
I'm
trying
to
package
everything
up
in
a
docker
container
get
a
public
instance
out
there,
so
that
people
can
start
kicking
the
tires
and
interacting
with
the
rest
api.
B
And
then
you
know
at
some
point
in
the
next
10
to
20
days.
It'll
it'll,
it'll
it'll
sink
to
the
tip
of
the
chain,
and
we
can
actually
use
it
and
then
from
there.
I
can
actually
just
take
snapshots
of
the
database
and
distribute
it
over
the
cash
strap
same
way.
We
do
the
cash
draft
infrastructure,
so
people
don't
actually
need
to
index
from
genesis.
A
So
if
once
this
launches,
if
people
say
a
business,
wants
to
use
slp
for
rewards
points
or
something
like
that,
they
could
just
take
a
snapshot
from
a
certain
point
and
then
run.
Would
they
need
to
run
that
out
on
location
or
could
they
could
this
be
a
business
that
somebody
could
start
up
where
it
says,
hey
I'll
run
it
and
you
can
run
your
rewards
points
for
me.
Yeah.
B
All
of
the
above,
so
I'm
trying
to
get
this
to
a
point
where,
like
the
other
bitcoin
cash
infrastructure,
you
don't
have
to
rely
on
anybody
you,
if
you,
if
you
have
the
technical
prowess,
you
can
run
your
own
infrastructure
and
you
don't
have
to
be
dependent
on
anyone.
So
that's
that's
the
that's
the
thing
I'm
trying
to
get
to,
but
but
we
we
will
offer
this
as
a
service
through
full
stack.cash
for
businesses
that
just
want
to
pay
a
monthly
fee
and
get
access
to.
B
You
know
a
professional
version
of
this
and
not
have
to
run
all
that
stuff
in
in-house
and
then
also
we're
going
to
incorporate
this
into
the
cash
stack
and
our
ipfs
infrastructure.
So
people
will
be
able
to
access
it
through.
This
isn't
going
to
be
a
drop-in
replacement
for
slp
db,
but
from
an
api
standpoint
it
can
be.
B
It
will
be
like
my
goal,
is
to
get
this
set
up
and
then
add
endpoints
to
bch
api
that
are
identical
or
very,
very
similar
to
the
existing
endpoints
for
slp
db,
so
that
you
can
get
all
the
same
information
that
you're
used
to
getting
and
so
anyways.
That's
that's
the
plan
for
for
moving
forward
with
that,
so
so
offering
different
tiers
of
availability
based
on
money
and
technical
prowess
and
yeah
yeah,
but
but
ultimately
making
it
so
that
people
aren't
required
to
depend
on
anybody
else.
For
this
information.
A
Yeah,
that's
one
of
the
things
that
excites
me
about
the
slp
protocol.
Over
some
of
the
other
token
protocols
I
see
out,
there
is
just
the
cheapness
and
the
ease
of
use,
and
so
it
helps
like
right
now,
especially
I've
been
diving
into
the
ethereum
world,
because
everything
is
so
expensive.
You
have
this
incentive
to
make
these
big
tokens
or
big
nfts.
You
know
it's
got
to
be
this
big
campaign.
It's
got
to
be.
We
have
to
develop
a
community
which
isn't
bad.
Those
are
all
good
things,
but
it's
not
something.
A
Where
say
I
run
a
food
co-op.
There's
lots
of
those
and
people
usually
pay
a
membership
to
be
a
part
of
it,
and
maybe
they
pay
that
membership
and
I
use
an
slp
token
to
distribute
to
them
for
claims
on
the
food
and
now
maybe
I'm
also
running
a
farmer's
market,
and
you
can
also
come
and
use
that
slp
token
at
the
farmers
market.
A
B
A
Go
ahead,
I
had
a
question
I
just
kind
of
lost.
Maybe
it'll
come
back
to
me:
oh
yeah,
so
is
there
a
possibility
of
utilizing
cell
phones
for
the
database?
So
you
know
people
could
be
because
they're
talking
about
you,
know
bluetooth,
le
there's,
a
guy,
that's
big
into
security,
for
cell
phones
and-
and
you
know,
that's
internet
of
things,
tech.
I
forget-
I
think
it's
brax
or
whatever
on
on
youtube
and
odyssey
and
he's
talking
about
how
every
bluetooth
device
now
communicates.
A
That's
a
bluetooth
led
it
communicates
with
every
other
device
within
like
a
mile
radius,
and
my
thoughts
are.
Why
can't
we
utilize
this
in
a
way
to
say
essentially
have
a
second
internet
that
could
talks
to
the
internet
and
can
make
transactions
that
way.
So,
even
when
you're
not
connected
you're
connected
in
a
way.
B
So
really
it
all
comes
down
to
memory
and
and
so
a
full
node
uses
about
two
gigabytes
of
memory.
The
fulcrum
indexer
also
uses
about
two
gigabytes
of
memory.
They
both
use
like
two
to
four,
but
I
think
they
can
run
on
two.
If
that's
how
you
give
them
and
and
then
this
new
index
or
the
slp
indexer
it'll
consume.
B
D
B
B
D
D
This
part
of
the
code
was
not
very
clear,
but
I
found
some
unit
tests
here
and
reading
this
code.
It
seems
so
easy
to
create
like
this
one
will
create
the
this
code
will
just
encode
the
all
of
the
public
keys
in
the
redeem
script,
like
it's
multi-c,
output
in
code
and
pop
key
one,
two,
three,
four:
five
something
and
this
transaction
builder.
You
just
put
this
in
the
redeem
script
and
it's
this
some
interesting
like
flak
for
the
signatures.
D
Usually
you
put
here
like
sick
hash
all,
but
there's
something
like
this
one
and
looking
on
this
coat.
It
must
be
everything
needed
for
multi-seek
transaction.
So
I'm
now
in
the
middle
of
trying
this
code
to
see
if
it
will
be
hubsy
enough
to
have
a
multi-seek
transaction.
That's
awesome!
This
is
all
in
bchjs.
B
D
Yeah,
it's
the
unit
code
for
the
because
how
to
see
looking
on
this
code,
it's
very
different.
This,
for
example,
this
line
for
some
input
with
c
some
index,
the
in
the
output
for
this
input,
but
it's
not
existing
for
us,
so
it
was
very
difficult,
but
looking
on
this
stuff,
maybe
this
mechanism
is
already
how
to
see
existing
inside
the
bch
library
itself.
Yeah.
You
just
need
to
put
there
the
the
right
redeem
script
and
it
will
create
the
other
parts.
B
Man,
I'm
so
glad
you
found
yeah.
You
know
that
I'm
glad
you
dug
into
this
because
so
I
mean
this
gets
back
to
the
history
of
bchjs,
so
it
started
as
bitbox,
which
was
created
by
gabriel
and
he
gabriel
cardona,
and
he
just
grabbed
a
bunch
of
bitcoin
likes.
He
basically
just
went
out
and
found
like
a
bunch
of
different
bitcoin,
javascript
libraries,
adapted
them
for
bitcoin
cash
and
then
and
then
incorporated
them
into
bitbox.
B
They
were
all
mit
licensed
so
and
so
bitbox
really
just
started
out
as
a
as
a.
What
do
you
call
it
like
a
collection
of
other
projects
and
so
that,
in
that
transaction
builder,
is
one
of
those
such
projects
like
gabriel,
didn't
create
that
it's
its
own
separate
javascript
project
which
may
have
been
abandoned
or
may
still
be
maintained?
I
don't
know,
and
so
yeah
he
must
have.
D
B
Yeah
yeah,
you
might
just
have
to
dig
into
that
transaction
builder,
and
if
you,
if
you
go
through
the
package.json
you
can,
you
can
sort
of
figure
out
where
that
code
originally
came
from
yeah
and
all
those
all
those
different
sig
hash
types
and
yeah.
All
that
information
you
just
kind
of
have
to
dig
through,
I
mean
so
good
job,
stewie
good
job
on
on
on
digging
into
this
and
really
dogging
this
thing
yeah.
So.
D
Just
wait
a
little
I
will
have,
maybe
more
so
in
the
other
ones,
just
10
minutes.
Maybe
I
maybe
briefly
talk
about
this
site
build
space
dot.
So
maybe
I
mentioned
it
in
the
end
of
the
previous
meeting,
but
I
encourage
everybody
to
try
this
because
it's
awesome
it's
how
to
see
hands-on
tutorials
to
create
different
stuff,
but
first
the
the
topics
are
great
see
you
just
built
it
down.
D
So
in
the
end
of
this,
you
have
a
working
down
or
you
can
have
like
nft
collection
on
solana.
Stuff
like
this
one
and
the
whole
process
is
great.
It's
like
a
small
you.
You
start
with
some
starter
code,
so
it's
already
small
working
application,
but
very
generous
one
like
a
small
react
application,
and
you
have
some
copy
paste,
the
code
that
you
add
and,
in
the
end
of
every
lesson
you
take
usually
like
a
screenshot
of
your
current
work.
D
Like
governance
tokens,
you
distribute
this
with
some
like
airdrop.
Also,
you
remove
admin
powers
from
the
keys.
All
of
these
steps
are
like
exactly
what
you
need
to
do.
It's
like
a
great
like
a
manual,
even
if
you
do
this
in
some
other
language
or
framework
or
whatever
wow,
so
this
dao
stuff
is
so
good
and
the
best
part.
All
of
this
is
without
a
single
co,
how
to
see
code
of
solidity.
It's
everything
javascript,
pure.
B
D
Thirdweb.Com.
These
guys
are
also
like,
like
champions.
What
they
have
is.
I
I
don't
know
how
exactly
to
explain
it,
but
it's
like
factory
of
contracts,
so
you
can
create
some
contracts
from
here,
but
in
the
end,
you
own
the
contracts,
not
they
so
you're,
using
some
like
contracts,
factories
to
to
create
your
contracts,
okay
and
they
is
it,
make
sense
or.
B
D
Okay,
I
will
not
lose
time
with
this
one,
so
you
can
give
different
modules.
But,
as
I
mentioned,
you
just
have
to
see
four
core,
I
don't
know
create
the
your
contract
from
their
contract
and
they
have
also
a
javascript
library
which
is
named
like
third
web
dot
sdk,
and
it's
just
how
to
see
a
wrapper
on
top
of
the
eaters.
D
Oh
okay,
so
like
for
this
dao
project,
my
final
code
is
this
one,
so
this
is
bunch
of
javascript
scripts
like,
for
example,
see.
This
is
how
I'm
creating
the
governance.
Token.
It's
just
app
deploy
token
module
wow
and
you
just
gave
him
name
or
something
so
looking
on
this
one,
it
does
not
have
any
blockchain
dependencies
here,
so
you.
C
D
B
D
So
if
you
have
time
just
go
through
this
build
space
project,
it
will
introduce
you
all
of
this
ready
ready,
like
libraries,
this
third
web
or
something
it
was
also
for.
The
solana
was
great
and
your
final.
This
is
the
interesting
part
when
you
finish
the
product
you
you're
getting
nft
for
the
completing
some
jobs
and
they're
awesome,
also
they're
like
animated
nice,
so
very
cool
so
see.
This
is
for
my
doll
guy
some
cookies.
D
A
D
D
Educational
and-
and
I
I
can't
steal
this-
how
to
see
use
it
every
day.
I
just
look
on
this
like
journal
what
I've
done,
so
I
can
do
this
on
other
framework,
smart
bch
or
whatever-
or
I
can
do
this
without
the
third
web,
because
this
just
common,
like
sense
like
create
all
tokens,
do
this
this
this,
like
great.
B
Yeah,
if
I
iman,
if
I
can
find
the
time,
I
really
want
to
just
play
with
that,
just
to
assess
like
how
much
energy
would
it
take
to
build
a
dow
and
then
create
a
token
and
then
create
like
the
just.
You
know
like
okay:
let's
do
a
vote
and
release
some
funds
that
you
know
in
a
treasury
wallet
using
a
vote
using
the
nfts
and
just
like
yeah,
be
good
to
assess
just
that.
The
basic
that
basic
dow
governance,
workflow.
D
Like
it's
a
list
of
the
all
of
the
projects
that
we
talked
the
previous
year,
oh,
if
you're
sharing
your
screen,
we
can't
see
it.
Okay,
it's
just
a
list.
So
but
that's
fine
yeah!
It's
just
a
list
of
the
all
of
the
projects
that
we
told
the
previous
year.
This
unlocked
gnosis,
all
of
them
nice
and
I
just
tried
to
see
which
chef
blockchain
supporting
most
of
them,
so
the
golden
guy
was
polygon.
All
of
them
are
working
there
and
until
the
week
ago
it
was
my
first
choice.
D
I
was
like
okay
next
year,
I
will
develop
on
polygons,
but
before
a
week
something
happens
with
their
blockchain,
some
shitty
game
like
sunflowers
farmers
or
something
it's
broke.
The
whole
network,
like
their
fees,
increased
like
10
times
or
something
but
yeah.
So
I
I'm
now
searching
again
for
something,
but
polygon
was
great.
All
of
this.
They
have
like
gnosis
there
gelato
for
this
automation,
all
of
them
all
of
the
things
that
I
talk
about
and
maybe
next
one
I'm
not
sure
avalanche.
Also,
they
have
most
of
them.
B
Well,
that's
good
see,
that's
the
thing
is
like
there's
such
a
race
to
build
business
apps
on
some
of
these
networks
that
you
know
privacy
and
decentralization
and
like
these.
These
are
these
considerations
are,
are,
being
you
know,
just
they're
not
at
the
forefront,
and
so
you
get
things
like.
Oh,
let's
build
everything
on
polygon
and
then
it
crashes-
and
it's
like
why
I
don't
you
know
I
guess
I've
just
gotten
used
to
being
like
I'm
different
and
other
people
don't
think
about
it.
B
D
D
A
B
A
Because
I'm
running
obs
it
doesn't
work
for
that
and
then
another
thing
is
the
helium
ecosystem.
Crazy
money
was
saying
that
they
are
already
using
what
we
just
talked
about
bluetooth,
to
build
a
networking
and
looks
like
they're
mining
and
doing
crypto
using
bluetooth
and
iot
devices.
So
I
will
transition
back
over
here,
but
that
was
in
the
chat
there
and,
let's
see
who
else
and
then
yeah
crazy
money
was
talking
about
that
and
then
bitcoin
payment
module
says
meeting,
isn't
complete
without
gems.
So
and
I.
D
E
E
A
D
Creating
the
bch
manual,
I
think
they
will
be
interested
like
if
you
can
put
some
of
our
stuff
inside
their
build
space
framework,
so
people
can
try
building.
It
will
be
great
like
creating
sop
token,
on
bch
or
some
kind
of
yeah.
I
like
their
how
to
see
how
they
going
like
a
small
journal
of
what
you're
doing
you're
getting
in
the
end
nft
to
be
happy
with
the
how
to
see
something.