►
From YouTube: Peerplays Weekly Townhall Meeting February 04, 2022
Description
Peerplays Weekly Townhall Meeting February 04, 2022
Peerplays is the first-ever blockchain
Humanizing your experience of crypto.
Join the movement to bring you crypto ecosystems that
understand you, build relationships & maximize your freedom.
---------------------------------------------------------------------------------------
Join us now:
Rocket Chat: https://chat.peerplays.live/
Twitter: https://twitter.com/peerplays
Instagram: https://www.instagram.com/peerplays/
A
Good
morning,
everyone
so
today,
we'll
be
doing
the
weekly
town
hall
meeting
for
february
4th
the
agenda
for
today
is
project
and
development
updates,
marketing
updates
collaboration
updates
and
questions
and
answers.
So
we
start
with
the
project
and
development
updates.
Bob
and
son.
B
Hi,
thank
you,
so
I
don't
have
control
to
the
screen.
So
can
you
go
to
the
first
yeah?
So
one
of
the
major
items
we
wanted
to
do
this
week
was
about
the
demo
of
the
bitcoin
deposit
on
the
mainnet
but
looks
like
the
demo
is.
B
The
setup
was
not
yet
completed
and
we
would
try
to
do
this
hopefully
next
week,
so
one
of
the
qa
team
members
is
trying
to
set
this
up
and
hopefully
next
week,
we'll
have
this
stuff.
So
this
is
one
of
one
of
the
most
important
items.
So
that's
why
I
thought
of
putting
the
screen
here,
even
though
the
demo
is
not
exactly
ready.
B
Now
the
remaining
the
rest
of
the
update,
then
the
first
one
is
the
dex
ui
premier
release
where
our
major
focus
is
to
get
the
hive
and
hbd
withdrawals.
So
those
screens
are,
we
were
supposed
to
again.
These
screens
are
delayed.
We
were
supposed
to
get
this
completed
last
month.
Hopefully,
it
was
essentially
by
jan
15th
or
so,
but
this
is
also
kind
of
delayed.
B
So
this
is
also
blocking
our
new
release
to
the
dex
ui.
So
we
we
have
0.70
released.
But
after
that
we
have
a
lot
of
these
upgrades
to
the
js
and
quite
a
few
bug
fixes,
but
we're
waiting
on
this
high
event,
hvd
or
screens
to
be
completed
so
that
we
can
do
the
next
release.
But
it
looks
like
we'll
have
to
do
the
release
without
these
screens,
because
there
is
a
there's,
a
large
set
of
updates
being
pending
right
now.
B
B
So
these
are
oh
yeah
now
another.
Another
major
point
is
when
we
look
into
the
decks
ui's
tickets.
B
There
are
a
lot
of
items
missing,
so
this
is
again
one
item
we've
been
trying
to
fix
or
improve
for
a
very
long
time,
but
now
we
need
to
take
this
as
a
public
action
item
and
work
on
it.
So
the
details
have
been
listed
here
so
but.
B
What's
happening
is
we
have
issues
and
we
have
issues
or
ziklab
tickets,
where
we
mention,
let's
say,
features
we
have
bugs,
etc.
B
Now
the
and
these
bugs
the
developers
works
on
the
box
or
the
features
and
it
gets
released
now
the
what
is
missing
here
is
that
we
have
absolutely
no
traceability
into.
When
we
look
into
any
of
the
tickets.
There
is
no
traceability
into
which
release
the
fix
has
gone
into.
That
is
missing
now.
B
Secondly,
when
after
the
qa
is
done
at
least
the
qa
is
expected
to
provide
additional
information
like
which
was
the
build,
which
was
the
ui
build
or
which
is
the
blockchain
build
browser
versions
against
it.
It
was
tested,
or
maybe
resolutions
against
it
was
tested,
all
sort
of
minor
details
and
os
versions.
C
B
The
major
concern
is
that
we
have
absolutely
no
information
if
you're
looking
to
look
into
the
tickets,
so
this
has
been.
This
is
a
major
problem
because
in
the
future,
if
you
want
to
go
back
and
address
something,
let's
say:
if
you
want
to
look
into
the
logs,
there
is
no
way
to
look
into
the
logs.
So
we
need
to
take
this
as
a
major
action
item
and
get
this
fixed.
B
So
then
we
have
let's
go
back
to
the
previous
slide
once
again,
so
there
are
some
more
items
now
another
as
pictures.
Now
we
have
a
early
earlier
screens
were
not
done
by,
let's
say
a
dedicated
ux
engineer.
Now
we
have
a
dedicated
ux
engineer
and
any
new
screen
that
we're
doing
this
is
done
with
done
by
a
ux
engineer.
But
what?
But
we
are
again
something
that
we're
missing
is
the
ux.
B
From
the
ux
engineer,
we
get
one
set
of
designs
which
is
approved
and
that
cost
goes
for
development.
So
what
is
expected?
Is
we
get
exactly
the
same
screens
because
it
goes
through
through
lord
of
iterations
and
back
and
forth
to
get
each
and
every
screen
designed?
B
But,
but
something
that
we're
missing
right
now
is
right,
these
screens,
first
of
all
they
get
during
the
development.
Obviously
these
screens
get
changed
changed
a
little
bit.
It
could
be,
it
could
be
a
possible,
I
mean
it
could
be
because
of
improvements
that
we
figured
out
or
could
be
because
of
some
some
things
that
we
cannot
implement
during
the
implementation.
B
In
such
scenarios,
what
we
need
to
do
is
we
need
to
have
a
change
request
created
and
those
change
requests
should
be
acted
upon
first
and
then
we
need
to
deviate
from
the
ux
designs,
but
right
now
what
is
happening
is
we
are
not
tracking
these
differences
from
the
design
and
implementation,
and
we
need
to
work
on
this
and
the
reason
why
this
is
being
mentioned
in
the
dex
ui
is
because
we
we
are
starting
to
work
on
the
next
and
we're
working
on
the
nfd
store,
and
we
cannot
have
these
smaller
gaps
in
those
projects.
B
So
we
need
to
start
from
the
dex
ui.
So
any
deviation
from
the
or
from
the
ux
designs
it
has
to
undergo
a
change
request
process.
So
some
of
the
new
screens
that
we
have
done
for
the
text
ui
there,
the
labels
are
incorrect
and
things
are
very
confusing.
For
example,
there
is
a
screen
which
says:
bitcoin
address
generation
where
the
design
was
originally
saying
it
was
supposed
to
be
bitcoin
deposit
address
creation.
B
So
these
are
major
issues
because,
for
example,
if
you
look
at
the
take
the
example
of
bitcoin
or
address
bitcoin,
deposit
screens
or
withdrawal
screens,
it
has
10
to
12
steps,
and
these
10
to
12
steps
are
combined
into
a
small
screen
and
it's
it's
extremely
confusing.
So
we
tried
out
with
some
of
the
some
people
who
who
has
a
deep
experience
with
bitcoin
and
currencies,
even
they're,
not
able
to
figure
out
which
what
exactly
these
screens
are
doing.
B
So
we
have
to
work
on
these
ux
changes
and
make
sure
that
any
change
it
is
tracked
efficiently.
Now.
Another
point
is
we
have
we
have
elk
setup,
which
is
elasticsearch
log,
stash
and
kibana.
B
This
has
been
set
up
for
closely
one
and
a
half
years,
but
this
is
not
getting
used,
so
this
is
something
we
we
really
have
to
start
using
because,
apart
from
some
of
the
blockchain
tickets,
where
logs
are
manually
collected
and
posted,
we
don't
have
any
historical
information
regarding
what
what
happened
during
any
any
of
the
bug,
verifications
or
feature
verifications.
B
So
this
is
again
something
we
need
to
take
seriously
and
work
on.
The
last
point
is
the
the
environment
that
is
given
to
a
given
for
qa.
So
right
now,
one
of
our
challenges
is
that
we,
so
we
we
have
two
kind
of
official
testers.
One
is
iron
and
another
one.
So
in.
B
To
have
bitcoin
sons,
it
is
not
having
bitcoins
and
for
for
a
for
a
very
long
time
so
so
this
is
another
item
which
we
need
to
work
on
and
fix.
So
these
are.
This
is
quite
important
because
and
because
this
is
not
just
impacting
our
our
ability
to
address
issues
in
the
future,
and
we
are
also
losing
visibility
and
transparency.
B
So
we
have
to
we'll
keep
this
particular
action
item
open
and
in
the
next
few
weeks,
we'll
make
sure
that
this
is
addressed
now
rest
of
the
screens.
These
are
these
screens,
so
we're
talking
about
the
dexious
progress.
Let's
skip
the
next
two
slides.
C
I
have
a
comment
robinson:
can
we
show
this
progress
one
more
time
so
currently,
this
progress
reflects
the
tickets
that
are
complete,
but
we
currently
have
a
bunch
of
tickets
around
affording
tickets
in
the
testing
stage,
and
they
hopefully
will
be
complete
today,
so
today
they
will,
by
the
end
of
the
day,
we
should
have
way
more
completed
tasks
and
way
better
progress
than
right
now.
This
is
this
diagram
shows
the
state
on
like
on
thursday
evening.
Okay,.
B
Okay,
thank
you.
So
this
is
again
we'll
skip
this
slide,
because
this
gives
we
talked
about
it.
Okay
now,
so
this
particular
screen
now
this
is
this
is
our
tracking,
where
we
are
trying
to
track
the
exact
progress.
So
this
is
in
the
early
stages
and
some
of.
C
B
You
look
into
the
earlier
processes
like
lld
updates
and
all
those
are
kind
of
irrelevant
for
this
project,
but
generally
going
forward
in
all
the
projects
we'll
be
having
these
detailed
tracking.
Okay,
let's
go
to
the
next
slide,
so
in
the
next.
In
this
slide,
we
have
the
historical
tracking.
B
This
will
hopefully
get
combined
into
the
previous
screen,
the
gantt
charts
and
visualization
the
new
type
of
visualization
that
we're
using
so
again,
this
gives
our
historical
progress
from
when
we
started
using
this.
This
tablet
format
for
tracking
okay.
Let's
go
to
the
next
item:
okay,
the
next
ui,
which
is
our
newly
designed
index,
decks
interface.
B
So
this
is
coming
along
pretty
well,
even
though
the
progress
is
kind
of
the
charts
are
not
showing
much
so
we
have
been
working
on
the
setup
and
we've
been
identifying
the
identifying
various
libraries
like
the
bitcoin
library
and
for
the
hive
and
spd
deposit.
B
C
I
also
have
a
comment
right
now,
so
we
currently
need
more
developers
new
hands
and
for
the
next
project,
so
we
are
doing
very
extensive,
recruiting.
We
are
looking
for
new
react
developers
also.
I
hope
people
who
are
currently
doing
dex
ui
will
be
become
available
for
next
starting
from
next
week
and
we
will
have
more
developers
and
better
progress.
B
Okay,
thank
you.
So
this
is
again
our
charting
this.
This
this
particular
information.
I
believe
it's
it's
getting
much
better,
and
this
is
next
is
the
first
project
where
we
started
tracking
with
our
new
tracking
methodology
and
type.
It
looks
it's
looking
it's
much
better,
even
though
I
think
the
estimates
needs
to
go
in
and
because
some
of
the
items
like
earlier
the
initial
screens
it
looks
like
our
estimate
is
on
the
lower
side.
B
So
so
we
need
to
improvise
those
one
reason
why
we're
not
providing
this
excited
estimate
from
day.
One
is
because
we're
not.
Let's
say
this
is
we're
not
following
like
a
gate
or
waterfall
kind
kind
of
mechanism
where
everything
is
projected
first,
so
these
projections
are
kind
of
indicative.
B
Okay,
let's
go
to
the
next
slide,
okay,
dexbot!
So
for
this
project
we
have
finally
managed
to
connect
to
the
place
test
net
or
the
yaml
test
net,
and
we
are
able
to
place
orders
so
far.
It
is
just
orders
because
the
trades
are
not
happening
because
we
have
not
yet
created
additional
tokens
or
user
issued
assets.
B
So
once
we
have
that
we
will
start
seeing
the
trades
as
well
and
we
also
have
the
initial
release
ready,
which
essentially
changed
a
lot
of
api
endpoints
and
also
a
fixed
few
bucks,
and
some
changes
to
the
underlying
libraries
are
also
made
to
make
it
make
it
work.
B
So
the
alpha
release
is
available
and
in
the
upcoming
weeks
we
will
we'll
have
a
will
come
conclude,
some
more
testing
and
the
the
idea
is
to
come
up
with
some
strategies
or
some
trading
strategies
and
then
release
it
to
the
right.
So
it's
going
to
be
a
desktop
application.
I
think
a
lot
of
people
family
with
a
bit
shares
our
community
is
already
familiar
with
familiar
with
the
with
the
tool.
B
So
it's
got
to
be
desktop
app
and
anybody
who
wants
to
provide
liquidity
can
run
them
and
run
these
tools
and
provide
liquidity.
Okay,
let's
move
on
to
the
next
slide.
B
The
okay,
so
our
blockchain
upgrades
so
here
again
we're
kind
of
working
on
various
existing
outstanding
issues
and
trying
to
improve
our
stability.
B
There
are
various
tickets
which
is
improving
logs
and
in
some
tickets
we
are
trying
to
provide
with
better
debug
information,
etc,
and
some
some
of
the
items
that
we
need
to
start
working
on
immediately
is
so
we
have
challenges
with
respect
to
the
sender
queue
or
the
bitcoin
nodes
connectivity,
so
the
bitcoin
node,
so,
as
I
had
pointed
out
in
the
case
of
the
iron
or
testnet,
what's
happening,
is
in
many
many
times
the
cmq
interface
was
the
bitcoin.
B
Node
exposes
it's,
not
it's
not
functional
and
we
are
not
able
to
identify
that
from
the
from
the
peer
play
side,
not
just
from
the
paper
side.
Even
if
you
just
try
to
debug
it,
it's
extremely
complicated.
B
So
the
end
result
is
that
when,
when
somebody
tries
to
create
a
bitcoin
deposit
address,
it's
not
getting
created
and
also
there
are
problems
with
the
ui,
because
the
ui
is
not
able
to
figure
out
whether
the
zero
mq
communication
is
happening
or
not.
B
So
that
is
one
item
which
we
need
to
work
on
another
problem.
Another
challenge
we
have
is
unlike
the
bitcoin
deposit
and
withdrawal
process,
the
hive
and
the
spdd
withdrawal
process
is
slightly
different,
so
there
are
scenarios
where
the
deposit
and
withdrawal
can
fail.
B
B
So
those
are
some
of
the
major
items
being
worked
on
on
the
blockchain
side
and
we're
also
starting
to
work
on
the
eighth
suns,
like
the
initial
workers
started
on
both
heath
sons,
and
we
are
also
looking
into
create
a
universal
adapter
sort
of
mechanism
which
will
help
us
to
connect
with
the
various
chains
or
external
data
sources.
So
we
have
started,
look
exploring
these
ideas
as
well.
Okay,
in
addition
to
these
updates.
B
So
from
the
grand
proposal
we
have
a,
we
have
a
quote:
we
have
some
interesting
inputs
which
can,
let's
say
easily
write.
B
Like
minimal
plugins
or
contracts,
and
also
create
site
chains
to
peer
place,
so
those
are
some
of
the
items
which
is
which
we
are
evaluating
right
now.
So
at
this
point,
we're
not
sure
how
exactly
we
can
use
this
in
the
paper
place
a
maintenance,
but
it
looks
like
the
the
the
ball,
which
is
the
blockchain
abstraction
layer.
B
It's
essentially
adding
some
additional
data
structures
or
storage
locations
to
our
chain,
which
can
be
used
to
perform
minimal
contract
or
minimal
logical
operations
similar
to
something
that
we
see
in
a
relational
database.
So
we
are
exploring
these
interesting
ideas
as
well.
Okay,
let's
go
to
the
next
slide.
B
Okay.
This
is
an
interesting
slide.
This
shows
our
ongoing
progress,
monthly
progress
so
again
here
the
numbers
are
pretty
low
in
terms
of
the
progress,
but
we
are
actually
working
on
some
interesting
and
major
bug
fixes
like
the
corruption
of
the
blockchain
file
and
some
other
features
which
will
help
us,
I'm
not
yeah
the
sudden
queue
features,
etcetera,
the
same
key
feature
which
I
mentioned,
etc.
So
so
even
the
numbers
looks
pretty
small.
B
I
believe
this
will
have
a
huge
impact
on
our
stability.
That's
on
the
blockchain
updates.
Let's
move
on
to
the
next
slide:
okay,
js
library:
the
only
item
which
is
being
painting
right
now
is
the
hive
related
changes,
so
that's
being
worked
on.
D
Hello,
everybody
happy
friday.
Marketing
updates
for
this
week
are
we've
continued
the
rollout
of
the
new
pureplays.com
website
with
updates
ongoing.
We
should
start
to
see
more
of
that
coming
online
in
in
the
near
future,
with
respect
to
the
the
community
aspects
of
it
and
the
the
forums
and
chat
availability
with
respect
to
it
as
well.
D
D
I've
created
a
pure
plays
community
outreach
survey,
which
is
currently
an
internal
review.
The
purpose
of
this
is
to
a
get
a
sense
of
the
demographics
of
our
fireplace
community
who's
involved.
How
long
they've
been
involved?
Do
they
own
ppy
and
go
from
there,
and
then,
on
top
of
that,
we
also
want
to
get
a
sense
of
what
they
think
of
what
we're
doing.
D
What
they'd
like
to
see
us
doing
what
they
don't
want
to
see
us
doing,
and
if
there
are
any
other
tokens
that
we
could
potentially
align
ourselves
with
through
the
through
the
suns,
so
that's
gonna
probably
get
released
on
monday
or
tuesday
next
week,
using
a
lot
of
different
channels
in
order
to
get
a
wide
reach.
D
And
then
I
will
summarize
the
information
in
a
presentation
in
one
of
these
meetings
within
about
two
to
three
weeks,
probably
just
to
kind
of
give
an
update
as
to
what
was
happening
with
the
the
community
and
what
they
want.
We
have
the
ongoing
brand
images,
brand
voice
and
content
strategy
project.
That's
been
going
on.
There's
been
a
lot
of
work.
D
That's
been
done
this
week
we
spent
a
good
amount
of
time
on
setting
up
how
to
reach
the
goals
that
we've
determined
for
our
social
media
posts
and
how
we're
going
to
to
reach
those
and
in
what
way.
The
big
one
goal
that
we
have
is
to
increase
our
engagement
and
then
it
will
be
to
drive
our
traffic
to
the
website
as
well
as
the
next
one
going
forward,
so
that
we're
able
to
build
the
community.
D
So
the
strategy
is
all
being
built
around
how
to
do
that
and
to
be
an
educational
force
and
to
be
seen
as
a
a
thought
leader
in
the
blockchain
space.
So
those
are
our
major
content
strategies
and
everything
we'll
be
doing
will
be
aligned
with
those
strategies
going
forward,
so
we're
in
the
process
right
now
of
just
setting
up
how
to
reach
those
goals.
What
kind
of
content
we're
going
to
go?
D
As
a
result,
I've
been
investigating
some
new
tools
to
increase
the
productivity
of
the
marketing
department
and
facilitate
communication
around
content
creation.
So,
just
looking
at
different
tools
that
there
could
be
for
like
content,
calendars
or
discussions
of
ideas,
collaborations
on
ideas
and
that
sort
of
thing
going
forward,
that'll
be
an
ongoing
investigation
to
find
out
what
the
best
resources
that
we
can
have
in
place
to
use
so
that
we
can
put
out
the
best
content
and
and
be
as
successful
in
our
goals
as
we
can
be.
D
That's
the
marketing
update
from
my
side.
I
will
turn
it
back
to
salah
for
the
performance.
A
Thank
you,
michael,
so
from
my
side
from
the
side
of
the
performance.
This
is
a
snapshot
of
the
this
week's
this
week's
like
social
media
performance
where
we're
starting
getting
more
growth
in
some
social
media
channels,
some
others
still
have
like
decline
in
terms
of
followers
and
subscribers.
A
But
the
engagement
on
some
of
the
like
instagram
and
linkedin
is
going
up
and
then
with,
as
michael,
have
stated,
with
the
new
content,
ideas
and
new
brand
and
image
standard,
and
then
we
will
be
having
more
growth
and
once
the
new
ideas
will
be
implemented,
we
will
see
more
growth
and
for
the
next
weeks
we
will
be
adding
more
kpis
in
the
performance
weekly
report,
so
we
can
see
more
kpi's
growth
throughout
the
week.
A
E
So
this
is
a
collaboration
update
for
the
past
couple
of
weeks,
since
we
didn't
get
to
put
one
out
last
week,
starting
off
with
gaming,
we
had
parlays
nfts.
The
casino
3.0
had
two
calls
and
had
iterated
further
on
how
pure
plays
will
be
used
in
their
casino
3.0.
E
It
looks
like
there
will
be
a
closed-loop
token
involved,
which
is
like
a
casino
chip
which
they're
going
to
be
using
in
various
games
that
they
want
to
host
utilizing
bot
pier,
plays
blockchain
on
it.
This
will
be
in
addition
to
the
nfts
they
plan
to
use
on
pure
plays
so
there'll
be
more
details
on
that
in
the
future.
E
The
other
gaming,
the
other
gaming
element,
was
gaming
benefits
corp,
with
charitable
gaming,
had
communication
with
them
regarding
the
acquisition
of
apps,
which
they'll
be
using
on
peer,
plays
for
their
back
end
and
that's
all
for
the
regulated
charitable
gaming
suite
of
products
they
plan
to
use.
E
So
that's
progressing
well
and
as
bobson
mentioned
in
the
update
with
follow
my
vote,
we
had
an
update.
We
received
a
report
on
the
blockchain
abstraction
platform,
the
ball
for
short
ball's,
a
software
development
framework
for
developers
wishing
to
create
smart
contracts,
and
so
we
now
this
is
all
focused
on
smart
contracts,
which
is
part
of
the
blockchain
which
are
back-end
solutions.
E
There
aren't
any
apps
yet
associated
with
this
you'll
see
you'll
still
need
a
front-end
to
make
this
work,
so
it's
more
for
developers
not
so
much
for
users,
so
we're
still
in
review
of
the
code
implementation
and
how
it
could
integrate
into
the
mainnet
for
pureplace,
but
that
review
will
take
some
time
regardless.
The
ball
is
an
interesting
technology
and
of
course,
that
would
be
interesting
for
peer
plays.
So
those
were
the
three
collaborations
that
we
had
happen
over
the
last
couple
weeks.
That's
it.