►
From YouTube: Status Townhall #28 - February 18, 2019
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
A
A
A
C
Yeah,
so
some
updates
on
the
cooler
stuff,
the
DAP
is
kind
of
more
or
less
complete
appreciative
contracts
are
more
or
less
complete,
there's
just
some
basic
stuff
with
like
learning
embark
and
and
dealing
with
that
out,
love
flex
and
support
with,
but
it's
more
or
less
functionally
ready
to
go.
It
just
needs
a
bit
of
styling
and
ends
a
bit
of
testing
worst
case.
C
You
could
always
just
deploy
the
contractor
ring
be
and
start
playing
around
with
it
and
I
could
give
you
some
command
line,
sort
of
things
to
copy
and
paste
in
there
to
get
used
to
it.
Well,
that's
it
roll
in
that
front
and
yeah
and
they
were
studying
a
new
swarm
as
part
of
our
sort
of
fundraising
efforts.
We
wanted
to
get
a
lot
more
formalized
in
modeling
our
token
economy,
so
Barry
has
been
doing
a
great
job.
Ready
checkout
is
in
the
swarm,
is
a
link
to
his
observable
user
account.
C
He
has
a
bunch
of
plate
models.
He
started
working
on
the
bill.
Kyle
and
I
have
been
collecting
some
empirical
growth
data
from
various
competitors
and
other
areas
of
interest.
So
if
you
plug
in
you
that
into
that,
so
hopefully
in
the
near
future,
we
can
have
essentially
a
model
of
what
we
expect
the
economy
to
look
like.
You
know,
one
to
three
years
down
the
line,
even
so
so
that'll
be
really
interesting
for
everybody
involved.
C
A
Thanks
Jerry
all
right,
jumping
in
engagement
surveys.
This
is
arm
from
people.
Ops,
people,
ops
after
the
Town
Hall
will
be
sending
out
a
questionnaire
survey.
It's
only
three
questions.
It
will
take
no
more
than
two
minutes.
It's
just
to
see
how
everyone
is
feeling
and
we
will
post
the
results
and
discuss
after
the
survey
is
complete.
So
please
keep
an
eye
out
for
that.
D
D
D
The
team
was
in
Denver
last
weekend
for
this
previous
weekend
at
F
Denver,
and
we
saw
some
really
really
cool
submissions
to
our
bounty
track.
Our
bounty
track
was
to
use
the
status
web
api
or
extensions,
and
it
was
Johan
and
the
leaped
out
team
who
built
the
red
envelope
extension,
which
is
really
really
cool.
D
The
winners,
I
believe
and
then
a
paper
extension
which
is
allowing
to
get
pay
for
your
photos.
That's
you
can
see
there
and
then
a
leaderboard
for
status
based
on
your
sign
pseudo,
random
name
and
once
again,
it's
just
really
exciting
to
see
people
brave
enough
to
hack
on
extensions
and
come
up
with
something
cool
and
help.
You
know
push
the
work
along
so
really
exciting
to
see
that.
B
A
A
E
B
E
Everyone
so
we're
doing
the
TTT
screens
and
integrating
contracts
screens
are
in
second
stage
of
bug.
Fixing
virtual
everything
is
completed,
parts
from
some
scrolling,
most
of
the
minor
things
have
been
nailed
out,
hopefully
I'm
virtually
finished,
with
the
status
with
the
chat,
integration
of
T,
DT
and
now
working
on
the
contract,
backend
integrating
contracts,
because
for
now
this
is
connected
to
stop.
It's
just
stores
the
T
DT
values
and
the
database.
E
B
Awesome
work,
cool
and
I'll
give
the
sticker
market
update
for
this
week.
So
great
progress
here
and
the
sticker
market.
Technical
implementation
of
the
designs
and
of
the
contract
work
has
actually
been
completed
by
Andre.
So
there's
a
PR
in
now,
which
is
currently
in
review
for
the
interface
between
the
sticker
market
MVP
and
the
contract,
which
is
deployed
two
ropes
ten.
B
So
next
up
there
and
we've
launched
this
community
contest
to
call
for
sticker
illustrations
from
the
community
and
we're
working
also
directly
with
one
illustrator,
whose
experience
with
creating
stickers
to
create
an
initial
status.
Themed
sticker
pop
and
Cory
is
continuing
to
manage
the
security.
I
thought
it
needs
for
this
one
before
we
launch,
hopefully
by
end
of
March,
and
that's
that
for
stickers.
F
So
the
total
network
we're
continuing
the
design
implementation,
it's
sort
of
a
state
of
flux.
Right
now
is
we
modifying
the
previous
work
to
the
to
the
one
that's
defined
in
the
designs,
but
it's
going
really
really
well.
There's
been
more
work
to
support
the
arbitration
protocol
in
in
the
browser
so
because
we
want
to
make
this
also
work
on
desktop
and
not
on
normal
browser,
not
just
on
mobile.
So
that
means
some
changes
in
murmurs
for
that,
and
we
also
been
deployed
to
test
nuts
and
interesting
if
everything
works
there.
As
expected.
A
G
Yeah
we
are
close
to
closing
our
research
phase,
so
there
is
a
post
from
Andrea
on
it
been
there
for
quite
a
while.
So
I
really
encourage
you,
if
you're
interested
to
read
it
and
have
some
feedback,
and
then
we
also
start
at
UX
exploration
and
hopefully
by
the
next
town
hall.
We'll
have
something
to
show
you
in
terms
of
designs
that
you
can
actually
so
you
can
look
at
and
yeah.
This
is
from
us.
So
far.
B
B
So
any
implementation
will
be
held
off
on
until
we've
completed,
that
sort
of
research,
investigation,
phase
and
I
believe
that
Ricardo
is
making
really
good
progress
on
the
contract,
which
is
meant
to
provide
and
functionality
laid
out
by
Andy
in
the
product
specs
for
using
bonded
curves
as
a
communication
mechanism
Ricardo.
Would
you
like
to
give
an
update
on
how
that's
going.
H
Okay,
so
I'm
working
in
this
is
my
contract.
That
is
a
very
for
now.
It's
very
simple,
with
smart
contract,
the
basic
functionality
is
it
to
make
a
ranking
of
the
apps.
So
when
you
we
want
to
load
from
this
might
contact,
it
will
always
give
you
the
top
and
from
the
top
you
can
get
the
next
like
a
linkedlist
and
I'm.
Also
studying
the
bank
are
bonding
curve,
so
I'm
working
to
implement
that
bonding
curve
that
they
are
using.
H
So
they
have
like
some
some
things
that
I
need
to
verify
like
how
they
made
their
explanation
with
some
Precision's,
but
everything
is
going
well,
it's
not
like
something
from
the
other
world
we
have.
We
have
some
example
implementations
from
other
people
that
we
can
look
so
that
that's
for
me
in
job
star,
perfect.
G
So
I
just
said
that
it's
one
point:
zero
in
there
with
the
implementation
we
are
like
quarter
ish
through
the
back
loop
and
recently
we
had
this
0
933
released
at
the
community
I've
seen
the
progress.
Essentially
it
was
this
faster
sign-in
and
other
fixes.
Yeah,
you
probably
see
from
the
screenshot
I,
still
struggling
with
reliable
messaging
there's
every
now
and
then
some
bugs
are
there.
We
also
working
on
the
reproducible,
builds
and
Pedro
does
a
great
job
of
doing
that
and
yeah.
So
pretty
much.
B
I
B
F
Hello,
so
the
first
thing
we're
we're
gonna
talk
about,
did
work
for,
and
it
was
well
the
new
website.
So
first
thing
we're.
We
are
working
on
the
new
website
that
better
communicates
what
the
former
framework
can
do
and
as
as
well
as
a
cleaner
documentation
and
and
learning
material.
This
is
the
latest
iteration
of
the
designs
and
we're
currently
in
the
implementation
phase
of
the
front-end
for
this,
and
we
should
release
the
new
website
soon
together.
The
goal
is
to
release
it
together
with
embark
for
so
next
slides.
F
F
So
it
includes
a
dashboard
UI,
which
you
have
log
supposed
to
have
eternal
terminal
with
also
suggest
quick
overview
of
the
contracts.
It
has
an
interactive
deployment
tool,
full
feature:
poachin
Explorer,
an
IDE
and
and
various
utilities
useful
for
for
developers
for
for
smart
contract
developers,
mainly
it
also
it
work
for,
will
include
and
revamp
our
clients,
and
we
completely
change
the
pipeline.
This
is
from
this
list.
This
is
not
only
thing
that
is
the
left
to
do
is
ongoing.
F
F
The
other
stuff
is
already
there,
so
we
have
transaction
logger
which
essentially
decode
the
transaction.
I.
Tell
you
exactly
what
contracts
being
called?
What
mattered
mattered?
What
arguments?
If
a
transaction
failed,
it
will
display
the
exact
line
of
code
that
it
failed.
It
has
a
built-in
debugger
and
it
even
has
also
a
code
code
generators.
So
a
developer
can
break
quickly,
prototype
attack
and
under
the
hood,
a
lot
a
lot
has
happened.
So
first,
we
support
now
pretty
much
any
Xmas
script,
no
specification
as
we
using
webpack
and
and
babel
in
the
code.
F
So
we
can
transpile
the
code
so
that
allows
us
to
make
use
of
much
more
modern
JavaScript,
even
if
not
yesterday
supported
yet
so
it's
making
the
code
way
nicer
and
cleaner.
We're
also
moving
to
two
typescript,
so
it's
it's
part
of
the
code
is
already
in
typescript
and
because
we
use
the
translation
and
we
post
in
the
pipeline-
and
we
can
use
both
at
the
same
time
and
the
idea
is
to
eventually
move
100%
to
to
typescript.
We
also
move
the
code
to
a
bona
repo.
F
This
means
some
repositories
like
in
part
gf
important,
yes,
I've
already
moved
and
it
will
be
in
an
archive.
This
also
will
allow
us
to
modularize
the
code
even
more,
and
the
idea
is
that
in
pro
you're
on
with
part
5,
we
everything
will
essentially
be
a
plug-in
and
part
will
be
much
much
lighter
and
people
just
install
the
modules
that
they
need
for
for
the
particular
tab
that
they're
trying
to
do.
F
Finally,
is
that
which
also
we
have
shaming
support
and
we're
sharing
support.
We
mean
that
it's
possible
to
do
project
specifics,
specific
versioning
of
embark.
This
is
something
actually
it's
quite
hard
to
do
it.
So
this
means
that
you
can
have
different
projects
and
have
different
versions
of
embark
for
each
projects.
F
It
looks
it
looks
easy,
but
it's
actually
not
quite
and
we're
not
yes,
and
it
took
us
a
lot
of
work
to
get
this
right
and
working
in
differing
all
this
different
platforms.
And
that's
it.
That's
like
a
quick
highlights
of
embark
for
we
hope
to
release
it
this
month
or
so,
and
it's
that's
wait.
It's
it's
very
exciting
what
it
brings
to
the
to
the
table.
Yeah.
B
A
All
right,
so
Q&A
will
be
a
little
different.
This
Town
Hall
we're
gonna,
kick
off
something
new.
We
launched
status
town
hall
questions
so
that
people
could
submit
questions
ahead
of
time,
and
so,
let's
kick
off
with
the
first
question,
somebody
submitted
this
question
and
said:
good
progress
seems
to
have
been
made
on
the
SMT
utility
swarms
with
an
ETA
on
most
what
that
being
said,
the
network
incentives,
firms
hosting
nodes
and
the
status
core
improvement
swarms
seem
to
be
further
behind
and
don't
have
an
ETA.
A
C
Dictator
I
sure
yeah
I
mean
I,
think
all
these
questions
were
from
wars
over
Joe,
so
shout
out
to
him
yeah,
basically,
I
mean
status,
isn't
really
a
straight
engineering
problem.
This
looks
absolutely
reason
why
there
isn't
many
decentralized
peer-to-peer
communication
tools
out
there.
A
lot
of
there's
like
a
lot
of
research
efforts
going
into
both
the
UI
and
like
how
we
actually
make
these
things
happen.
C
So
getting
networked.
Incentivization
right
depends
on
like
a
lot
of
these
technical
trade-offs.
It
also
starts
to
tie
into
like
our
new
protocol
research
that
we're
doing
which
is
going
to
be
a
very
long
process.
That's
going
to
take
a
while
and
basically
core
improvements
is
the
same
like
this.
It's
hard
to
estimate
and
solve
these
problems
in
linear
time,
however,
like
I
mean
with
the
backlog,
is
going
pretty
well
and
it
all
seems
pretty
on
on
track.
C
The
other
thing
is
I
wanted
to
mention
here
is
that
we
only
time
bugs
so
timebox
is
basically
just
sort
of
like
very
rough
sketches
of
where
we
would
like
to
be,
but
they're
not
gospel,
and
we
certainly
don't
set
any
sort
of
like
public
release
schedules,
because
basically
it
is
a
research
applied
research
process
that
we
go
through
so
I
mean,
and
of
course
you
know,
this
is
a
community
project.
If
you'd
like
it
to
see
a
public
release
faster,
come
chip
chip
in
and
help
us
out.
A
Cool
all
right,
the
next
question:
there
has
been
chatter
in
the
status
channels
that
suggests
using
the
existing
mobile
framework
and
incorporating
it
it
into
the
desktop,
rather
than
continuing
to
develop
desktop
as
a
standalone.
If
this
happens,
can
we
expect
to
see
a
desktop
wallet
and
dot
store?
If
so,
can
you
elaborate
on
the
approximate
time
scale?
A
C
This
is
like
it's
already
demoed
right,
sir
robot
UI
is
on
desktop
now
you
know
we'll
continue
to
evolve.
That
looks
looking
really
good,
so
we'll
probably
modify
that
to
be
like
two
panes
so
like
the
main
home
screen
will
be
on
the
left
and
then,
like
your
main
chat
context
or
whatever
daffy
or
wallet
will
be
on
the
right
hand.
C
Side
maybe
like
we
don't
know,
but
we
do
invest
a
lot
into
react
native
desktop,
so
we
could
have
a
consistent
codebase
across
all
the
platforms,
whether
it's
on
Android
iOS
or
any
of
your
desktop
flavors.
So
yeah
looks
like
it's
gonna
be
happening
and
scale.
You
know
like
lost
the
last
question.
I
answered
like
we
don't
do
that.
A
Okay,
the
next
question:
again,
there
is
no
current
date
when
key
key
card
will
be
made
publicly
available.
There
is,
however,
suggested
purchase
price
of
$29
when
it
is
made
available.
Can
you
elaborate
on
how
the
team
arrived
at
this
price
is?
Is
there
a
profit
margin,
and
if
so,
will
this
go
into
the
Dow
pot
yep.
C
So
there
is
definitely
a
margin
with
this
two
different
models
here
you
can
see
the
margin
going
to
the
Dow
is
definitely
a
great
idea,
but
we
don't
have
the
infrastructure
for
that
at
the
moment,
but
for
us
taking
a
margin,
it
allows
us
to
do
a
larger
production
run
the
second
time.
It
also
allows
us
to
handle
things
like
recalls
and
that
sort
of
thing
so
I
believe
don't
quote
me
on
this,
but
I
believe
that
the
initial
beta
stuff
will
start
shipping
mid-march.
A
J
J
If
people
do
leave,
then
we
may
like
to
replace
them
or
use
that
budget
in
a
different
way,
so
we're
not
actively
hiring,
but
you
may
see
some
small
pockets
of
hiring
I
guess
come
up
in
the
next
few
months
and
then,
if
we
do
hired
new
people
I'm
guessing
this
is
kind
of
references
and
the
compensation
changes
we
made
in
December.
If
we
do
Hanyu
people,
their
salaries
will
be
kind
of
benchmarks
against.