►
From YouTube: Status Townhall #37 - Monday June 24, 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
B
B
That's
right
until
next
year,
many
of
you
to
pay
cuts
in
return
for
extra
SNT
to
help
you
ensure
the
continuance
of
status
and
we're
I'm
very
grateful
for
that.
As
we
mentioned,
when
it's
financially
viable
and
sensible,
we
do
aim
to
reverse
those
cuts.
Our
focus
remains
on
ensuring
the
long-term
success
of
the
projects
and,
despite
the
improved
situation,
the
markets.
B
We
are
wary
of
making
any
rash
decisions,
given
the
volatility,
but
we
are
closely
monitoring
its
over
the
next
few
weeks
to
months
and
we'll
update
when
we
can,
but
in
the
meantime,
as
a
gesture
of
gratitude
to
those
who
did
take
one
for
the
team,
we're
going
to
be
putting
an
extra
$500
to
your
June,
paycheck
I
just
want
to
say
thank
you
again,
everyone
for
supporting
project.
That's
it
thanks.
A
Cool
thanks,
Jared,
alright,
next
up
we
have
people,
ops,
update,
so
I
will
be
sending
out
more
information
on
the
off
side.
So
everybody
please
keep
an
eye
out
on
your
inboxes
and
the
discuss
post
and
Kari
is
out
today.
So
I
will
help
give
her
updates
on
the
engagement
survey.
We
will
share
the
results
out
with
the
team,
but,
as
you
can
see,
here
are
some
takeaways.
The
happiness
scores
were
up,
which
is
always
really
great
to
see.
D
C
Slide
you
will
get
a
different
overview,
which
is
basically
a
breakdown
of
all
the
tasks
remaining,
and
there
may
be
some
things
here,
especially
the
yellow
bit
of
the
pie
chart
that
may
be
removed
from
this
list.
You
can
see
we're
about
halfway
through
over
costs
getting
completed
on
the
right.
You
can
see
what
is
on
everyone's
plate,
and
you
know,
there's
some
things
that
are
more
ensembles
like
than
others.
A
month
ago,
it
looked
very
different
as
the
work
moved
from
design
to
engineering.
C
If
you
go
to
the
next
slide,
this
is
a
new
dashboard
that
we've
actually
been
worked
on,
which
gives
a
very
interesting
impression
and
I
think
everyone
who's
working
on
the
core
application
should
have
access
to
the
dashboard.
It's
under
the
dashboards
tab
at
the
top
of
the
screen,
and
basically
it
gives
you
an
interesting
oversight
into
three
main
areas.
C
One
is
you
click
Next
one
is
an
overview
of
where
each
sub
project
is
next
again,
you
can
see
all
the
tasks
that
are
currently
being
worked
on,
so
this
can
give
you
all
the
overdue
tasks-
everything
that's
due
today
or
this
week,
so
it's
kind
of
like
okay.
This
is
what's
in
being
in
play
right
now
and
what
is
being
worked
on,
as
you
can
see
here,
this
has
taken
about
four
hours
ago,
but
there's
already
a
bunch
of
tasks
that
are
overdue
from
Friday.
C
So
all
of
this
is
linked
to
github,
which
means
that
when
you
start
working
on
it
and
github
it,
when
you
accept
and
github
it
actually
comes
through
here
and
works,
that's
not
a
lot
of
manual
work,
that's
needed,
but
this
does
give
a
lot
of
interesting
insight
into
what
like
how
accurate
our
time
frames
will
be.
So
you
can
see
here
that
it's
probably
a
ton
of
stuff
that
needs
to
go
updated
in
terms
of
how
long
it'll
take.
C
C
One
of
the
pieces
of
feedback
from
the
survey
was
to
get
a
more
concise
overview
of
what
b1
looks
like
in
a
time
frame,
and
so
I
tried
to
do
that
in
this
plan
hole.
So
if
you
click
on
the
next
slide,
I
know
the
Gantt
chart
is
slightly
overwhelming,
so
I'm
just
summarizing.
Basically
everything.
That's
all
the
major
features
in
v1
and
that
the
largest
one
is
the
multi
account
support,
which
was
needed
to
get
keycard
integrated
and
as
long
as
well
as
multi
count
support.
C
Improving
our
mobile
application
performance,
as
well
as
creating
a
new
UI
and
ans
float.
So
these
are
the
major
features
that
are
or
improvements
that
are
going
into
v1
for
in
terms
of
go
to
the
next
slide,
we
can
see
I
guess
some
early
reflections
already
on
b1,
we've
been
at
it
for
around
five
months
now.
C
C
But
the
fact
that
we
aren't
completed
by
the
end
of
June
was
we
didn't
really
know
how
big
mother
multi-account
work
was
and
and
how
much
they
impacted
everything
else,
so
we're
on
we're
underway,
but
that's
something
that
we
probably
could
have
done
that
are
at
another
thing
to
attack
on,
for
the
inaccurate
estimates
is
that
when
you're
scoping
an
individual
toss,
you
think
yeah.
This
should
only
take
one
day
or
two
days,
but
you
don't
take
into
consideration
the
fact
that
the
same
person
could
be
work
like
is
attached
to
five
different
tasks.
C
Similarly,
you
know
June
July
August
is
holiday
season
and
we
didn't
really
consider
people.
You
know
taking
two
weeks
off,
which
you
know
is
definitely
encouraged,
but
that
impulse
impact
timeline,
so
something
we
should
be
doing
better
at
for
future
iterations
is
making
sure
that
we
are
under
estimating
I
think
the
overestimating
or
you
get
what
I
mean
the
amount
of
work
required
for
each
individual
task.
C
And
finally,
a
very
basic
timeline
is
that
a
assuming
that
we
are
code
complete
next
slide,
assuming
we're
code
complete
by
the
end
of
July,
we're
looking
at
a
security
order
in
August
and
then
an
app
launch
in
September,
depending
on
what
comes
out
of
the
security
of
it
once
again.
This
is
an
estimate,
but
this
should
give
you
know
everyone
visibility
into
the
work
that's
been
going
on,
and
obviously
every
two
weeks
will
give
updates
here
on
more
detailed
progress
towards
these
estimates,
and
that's
it
from
the
generous.
A
E
E
It's
mostly
about
implementing
the
new
bahding
screens
and
logging
screens
with
key
card
Dmitry's
working
on
that
and
pretty
much
on
track
to
have
this
delivered
second
week
of
July
some
update
about
the
work
we
are
doing
with
the
ledger
integration,
so
fresh
news
from
last
Friday
Mikki
Lee
has
successfully
managed
to
release
an
app
that
runs
on
the
Nano
X,
which
is
a
p-card
app.
So
it's
using
the
key
card
API
who
have
a
communication
between
the
nano,
X
and
and
a
client-side
application
using
the
keys
of
the
Nano
X.
So
that's
an
achievement.
E
That's
great!
It's
working
now
and
it's
working
over
Bluetooth
over
be
any
more
precisely
so
this
work
with
Android.
Today
we
have
client-side
SDK
that
already
that's
also
available.
It's
a
Java
one,
so
very
easy
to
use
with
any
Android
client
application,
and
this
app
can
also
be
used
with
a
knife
nyow
s
phone.
E
We
don't
have
a
swift
SDK
for
now,
but
so
this
is
great
progress
and
the
next
steps
on
this
ledger.
Integration
will
be
to
have
this
reviewed
by
ledger
and
the
status
side.
Part
of
the
integration
which
we've
not
prioritized
part
of
v1.
So
we'll
do
that,
once
the
v1
will
be
ready
on
the
outreach
side
which
we
are
Kentucky
contacting
more
and
more
projects.
E
Blockchain
projects
I
mean
just
wanted
to
note.
We
add
in
the
past
two
weeks
some
interesting
discussion
with
Opera
Mobile.
The
browser
is
a
web
free
browser.
They
are
interested
by
the
idea
of
integrating
with
a
smart
car,
the
fun
factor
so
interesting
discussion.
There,
Ignasi
safe
we've
mentioned
them
for
couple
of
month.
E
They
order
25
cards
to
speed
up
their
integration,
which
is
great
news
and
also
we
are
discussion
with
with
other
cards
and
the
your
father
10
cards
to
to
play
with
the
cards,
see
what
they
can
do
with
it
and
a
hack
with
them
so,
and
that
was
for
the
outreach
and
I
just
also
wanted
to
mention
that
to
progress
with
our
plans
to
set
up
some
payment
proof
of
concept.
At
first
we're
having
discussion
with
several
side-chain
project
to
set
up
some
I
mean
to
understand
the
technology,
see
how
we
could
do
proof-of-concept.
E
F
F
The
speed
of
syncing
for
group
shots
and
one-to-one
chat
should
should
improve
as
soon
as
again,
everyone
will
start
using
the
version.
So
it's
as
of
next
release,
I'm
still
working
on
a
huge
moving
protocol
to
status,
go
tasks
and
more
updates
about
it.
In
the
next
town
hall
for
the
performance
improvements,
more
models
were
created
for
Network
and
stanchions.
Actually,
you
can
see
from
the
slide
as
it
should
speed
up
a
bit
of
the
signing
like
they
start
up
of
the
application.
F
Also,
the
faster
rendering
of
heavily
formatted
text
was
again
tested
and
is
ready
to
be
merged
in
cases
when,
for
example,
we
have
very,
very
heavy
formatting
of
several
messages
that
is
shown
in
the
in
the
chart.
As
soon
as
you
open
it,
then,
on
even
like
mid
device
like,
for
example,
pixel
excels.
It
is
not
super
slow,
not
super
fast,
but
it's
good
enough.
It
could
take
about
seven
seconds
and
now
again
it's
in
special
cases
like
usually
you
don't
have
these
messages,
but
it's
possible
so
in
in
like
with
this
PR.
F
It
will
take
from
two
to
three
seconds
to
to
render
this
text.
So
it's
quite
an
improvement.
There
is
also
pyramids
that
our
icons
are
changed
to
PNG
icons,
so
it
should
improve
loading
of
this
each
screen
that
contain
icons-
and
there
are
other
PR
that
actually
are
not
listed
so
upgraded.
We
upgraded
react
navigation.
Also,
some
macro
says
updated.
That
again
should
adapt
actually
decrease
as
the
number
of
seconds
or
milliseconds
for
different
actions.
Ins
up
still
working
on
reproducible,
Android
builds,
and
you
can
see
what
was
done.
F
The
big
next
step
for
desktop
as
soon
as
two
pane,
UI
and
watch
screens
will
be
reviewed,
tested
and
merged.
It
will
allow
us
to
switch
to
mobile
UI
in
the
desktop.
So
it's
more
like
we
are
more
close
to
the
features
on
desktop
that
already
available
on
mobile.
So
it's
again
big
milestone.
It
is
almost
almost
done
and
again
what
epi
on
status
go
side
also
done
so
work
in
these
transactions.
I'm
getting
the
transactions
information
should
become
faster
and
easier
as
soon
as
it
will
be
used
in
the
status
up.
G
A
G
Cool
okay,
so
I'm
some
good
progress
over
the
last
two
weeks
on
our
big,
a
mix
and
so
andre
finish
and
merge
the
new
wallet
transaction
overview
screen.
He
also
laid
the
foundation
for
the
new
multi
count
UI
within
the
wallet
you
can
now
see
in
develop
that
there
are
multiple
wallets
hypothetically.
G
You
cannot
yet
at
wallet,
but
the
UI
is
there
and
there
are
a
few
little
items
remains
a
cleanup
there's
some
settings
missing
and
icon
or
two
missing,
but
we've
captured
issues
for
those
and
that
work
will
be
bored
with
eric
over
the
next
two
weeks,
while
andres
on
vacation
julian
merged
native
ANS
registration.
So
you
can
also
experience
that
and
develop
and
he
should
hopefully
have
SPR
for
ENS
resolution
in
chat
today.
G
Meanwhile,
literally
on
onboarding,
as
nearly
finished
with
his
work
on
the
first
few
screens,
where
new
onboarding,
where
you
can
select
your
new
P
and
is
currently
working
on
new
pin
code
encryption
for
the
six
digit
code
that
we
are
replacing
the
password
with
in
the
meantime,
I've
put
some
bounties
on
some
very
like
surface
level.
Ui
issues
for
other
components
of
onboarding,
like
account
recovery
and
new
sign-in
flow
and
I'm,
also
going
to
be
doing
the
same
as
some
of
the
cosmetic
changes
to
the
profile.
G
Just
in
the
interest
of
excavating
network
as
possible
and
having
more
team
members
available
for
supporting
multi
count
and
then
also
wrapping
up
S&T
utility
features,
as
we
do
have
a
few
outstanding
changes
to
make
for
tribute
to
talk
and
for
sticker
market.
And
on
that
note,
we're
thinking
that
once
Jillian's
work
on
DNS
resolution
is
finished
this
week,
he
will
shift
over
to
stickers
rather
than
profile
screens
and
attempt
to
rub
up
the
few
remaining
issues
for
the
client
there,
because
we
could
very
easily
isolate
out
the
sticker
market
feature
and
create
a
release.
G
H
Yeah,
the
main
change
would
be
that
we
erase
the
storage
contracts
that
are
the
NFC's
or
here
see
seven
to
one
super
separated
contract
for
a
better
architecture.
Thinking
about
the
migration
process
and
the
grade
of
the
sticker
market
logic.
So
we
can
safely
update
out
the
logic
in
the
lead
gear
of
ownership.
Of
of
who
is
the
outer
of
each
toe.
A
I
I
We
work
us
on
the
on
contract
ability,
so
we
can
upgrade
the
contracts
later
if
we
so
wish
an
able
to
use
better
mechanism
for
ESCOs
that
might
come
up
in
the
meanwhile.
We
also
working
were
working
currently
not
on
the
government's
mechanism
and
also
we
work
mechanism
for
the
salad
Network.
We
did
some
progress
on
the
side
chains
aspects
and
we
did
and
finally
did
the
miscellanea
UI
improvements
to
to
the
teller.
J
So
we've
pretty
much
started
wrapping
up
our
Minimum
Viable
Data
Sync
paper.
So
we
have
that
integrated
in
the
status
console
client
as
well,
where
we
can
now
send
around
messages
reliably
without,
depending
on
the
mail
servers
anymore.
The
next
step
is
to
add
the
remote
log
extension
to
minimum
viable
data,
sync,
which
allows
better
usability
for
offline
first
devices
by
storing
messages
in
the
storage
like
swarm,
so
that
we
don't
need
a
wait
for
message.
D
D
Yes,
so
the
Deaf
stole
there
hasn't
been
too
much
progress
over
the
last
two
weeks,
Lyme
Jane
delivered
the
work,
we're
in
the
process
of
testing
it's
and
still
waiting
for
a
sort
of
formal,
smart
contract
audits.
But,
as
it
says
on
the
slide,
you
can
test
that
the
test
site
at
dev
depths.
If
you
need
some
rust
and
test
it
and
see
them,
you
can
just
contact
me
or
Jakob
or
Corrie.
You
can
add
your
own
D
apps.
You
can
voice
on
them.
H
The
link
is
in
the
relevant
links
this
that
was
not
audited,
but
it
is
an
example
and
on
how
we
can
make
this
country
continuous
integration,
and
also
reproducible
builds
for
the
apps
and
this
multisig
that
by
I'm,
working
as
in
the
research
of
topic,
democracy
for
building
the
UI
components
and
when
one
improvement
was
in
the
East
is
at
address
that
display
the
address.
So
you
can
now
have
this
menu
that
it
can
be
reused
and
it
is
using
and
the
lists
so
that
there
is
improvements
in
the
usage
of
this
component.
H
K
All
right
I,
this
short
sweet,
but
basically
you
just
wanted
to
show
you
guys
a
quick
demo
of
the
embark
plasma
plugin
that
we've
been
working
on
just
quickly.
What
does
this
get
us?
This
gets
us
a
few
things
into
our
depth.
So
this,
basically
this
plugin,
let's
adapt
interact
with
the
plasma
chain
in
particular
lets
us
interact
with
the
me
say,
goes
sam
wrong
chain.
It
exposes
an
embarked
jeaious
that
plasma
api
so
that
the
dep
can
interact
with
the
plasma
chain
in
the
browser.
K
It
also
gets
us
some
embarked
console
command
so
that
we
can
interact
with
the
plasma
chain
inside
of
the
embark
console
or
inside
a
cup
fit
and
of
course,
the
first
one
goes
last,
so
we
can
do
things
like
deposit
from
the
main
chain
into
the
child
chain.
We
can
transfer
funds
around
and
the
child
chain
and
we
can
exit
our
funds
from
the
shallow
chain
into
the
main
chain.
So
those
are
some
of
the
examples
of
interaction
that
we
can
do
using
this
plugin.
We're
currently
limited
to
test
minutes.
K
So
the
main
plasma
core
contract
is
sitting
on
rinkeby
and
we're
using
a
Mesa
ago,
Sam
wrong
plasma
network
that
they've
set
up
but
yeah
we're
planning
to
support
local
dev
chains
and
future
versions,
and
a
current
limitation
is
that
the
DAP
must
use
meta
mass
to
sign
transactions.
But
again
this
will.
This
will
change
very
soon.
We're
supporting
signing
transactions
locally
using
accounts
configure
it
inside
of
embark
or
inside
the
DEP
yeah
embarks
config
in
the
DEP.
Okay,
quick
demo,
I'm
gonna
show
you
guys
when
I
pre-recorded.
K
All
right
so
can
I
make
this
bigger.
I
cannot
alright.
So
what
we're
looking
at
here
is
essentially,
this
is
a
me
say,
goes
Jay
s,
starter
kit
that
they
created
it's
just
a
DAP
that
they've
created
that
shows
off
some
of
the
functionality
that
I
talked
about
like
depositing,
transferring
and
editing
funds.
Now.
K
K
Look
that
better
yeah?
Okay,
oh
you
guys
missed
all
my
slides,
which
would've
been
really
interesting
staring
at
my
gate,
client,
okay
anyway.
So
this
is
basically
jeaious.
Starter
kit
that
me
se
quedó,
created
and
all
that
we've
done
is
convert
what
they
had
into
using
the
embark
jeaious
dot
plasma
api,
so
basically
we're
showing
that
we
can
use
using
the
embark
plasma
plugin.
We
can
support
all
the
functionality
that
they
wants
to
show
off
in
their
j/s
starter
kit.
So
just
quickly,
so
you
can
see
here,
we've
got
a
wallet
address.
K
This
is
the
wallet
that
meta
mask
exposes
I
swear.
This
is
meant
to
get
bigger
anyway,
and
then
we've
got
a
so
we've
got
a
root
chain
balance.
So
this
is
our
balance
on
rinkeby
and
child
chain
balance.
So
that's
our
balance
on
the
plasma
chain,
so
we
can
deposit
funds
from
rincon
P
into
the
chavo
chain.
It
does
support
a
OC
20s
if
you'd
like
to
try
that
as
well
that
actually
takes
so
yeah.
We
have
to
sign
a
transaction
to
tell
the
plasma
contract
any
one
deposit
funds.
K
K
So
for
those
of
you
that
don't
really
know
that
much
about
plasma
chains
or
at
least
the
more
vp1
there's
a
watcher
that
watches
transaction-
that's
happening
on
the
child
chain
and
eventually
it
will
include
it'll,
replicate
every
transaction
on
the
child
chain
onto
the
main
chain,
but
it
has
to
make
sure
that
block
is
finalized,
that
you
know
I
think
there's
probably
like
six
or
seven
confirmations
that
need
to
happen
before
that
actually
occurs.
So
that's
why
that
child
chain
balance
hasn't
refreshed
yet
then
we
can
go
on.
We
can
transfer
funds,
we
can.
K
You
can
send
funds
to
any
account.
You
want
so
example,
for
example,
will
send
five
by
five
way,
and
this
is
kind
of
cool,
because
this
is
this
is
a
ip7
one
to
support.
So
you
can
see
that
we
have
a
domain
with
a
verifying
contract
in
the
salt,
but
we
can
also
see
what
we're
signing
so,
for
example,
we
have
an
output
here
we
tried
to
send
555
way
to
this,
to
this
contract.
I'm.
Sorry
to
this
address
and
that's
good.
It's
not
just
a
bunch
of
random
data,
so
that's
actually
cool.
K
So
you
see
that
the
transaction
was
very
quick.
I
would
show
you
you
see
here,
there's
a
little
link
here
to
a
block
explore,
but
CloudFlare
killed
the
internet.
So
that's
not
working
and
again
refreshing.
It's
still.
You
still
would
see
an
update,
yet
you'll
see
it
at
the
end
of
the
demo.
Just
see
the
update
happen,
but
the
other
thing
you
can
do
you
can
exit
you
TXO.
So
again,
if
you
don't
know
how
clauser
chains
work
just
quickly,
they
work
so
similar
to
Bitcoin
so
they're
they
work
with
UT
exo's,
unspent
transaction
outputs.
K
It's
a
bit
funny
the
way
it
works
and
very
confusing.
But
if
you
want
to
send,
for
example,
555
way
to
sum
someone
you
send
that
amount
to
them
and
then
the
remainder
of
the
unspent
transaction
output
gets
sent
back
to
yourself,
so
there's
essentially
no
state
in
the
chain
and
that's
kinda
how
they
handle
it.
So,
moving
on
to
the
exit,
you
can
exit
individual
UT
exo's,
so
we
can
essentially
select
one
of
them:
click,
exit,
okay
and
sign
the
transaction
and.
K
We'll
kick
off
an
exit
process
that
takes
about
seven
days,
there's
like
three
and
a
half
days,
I
think
for
contesting
any
exits
like
any
malicious
exits
and
another
three
and
a
half
days
for
finalizing
or
resolving
those.
So
you
see
here,
the
child,
Jaden
balance
is
finally
updated
with
our
555
way
and
we
have
a
transaction
up
here.
So
that's
very
quickly.
The
demo
demo
just
want
to
show
you
that
you
can
do
the
same
thing
inside
of
a
bar
using
some
console
commands.
K
So
this
is
the
this
is
inbox
cockpit
and
on
the
dashboard
you
can
see
here.
We've
got
a
nice
ego,
plasmid
chain
running,
it's
just
talking
to
the
watcher
and
we
can
get
help.
We
can
see.
We've
got
some
plasma
commands,
so
the
first
one
we
can
do
is
plasma
deposit
and
we
can
say
just
exactly
what
we
did
for
this
deposit
ten
thousand
way.
K
It
will
eventually
show
us
that
we
have
a
transaction
in
rinkeby
which
it's
good.
Then
we
can
see
that
transaction
gets
in
a
block
at
some
point
and
that's
all
good.
Then
we
can
transfer
same
thing
pick
an
address.
We
want
to
transfer
to
picking
him
out
or
typing
in
the
mountain
and
transfer.
It
happens
very
quickly
and
again.
Well,
Castillo
wasn't
working
and
finally,
we
can
do
something
like
exit.
A
A
All
right
so
now
we're
gonna
jump
into
your
Q&A,
so
we
had
just
one
question
that
was
submitted
through
our
channel
today
and
I.
Believe
it's
about
the
top
store.
So
in
the
top
story
is
SNT
that
is
used
to
votes,
take
logs
away
in
the
contract
forever
and
therefore,
in
effect,
burned
and
taken
out
of
circulation
permanently.
A
H
I
can
answer
for
him
so
the
year
yes
is.
This
is
the
main
idea,
so
the
contract
is
designed
it
this
way
that
this
S&T
would
be
locket
I'm,
not
entirely
sure
if
there
is
a
escape
hatch,
but
we
can,
if
that,
if
that's
that's
the
case,
we
might
never
push
that
hatch,
but
I
don't
think
there
is
an
escape
hatch
there
from
what
I
remember
the
last
time,
I
see
the
contract
and
and
as
far
as
I
remember
seeing.
H
L
Top
of
that
anyone
company
decided
to
stake
your
given
DAP
on
to
the
dab
store.
They
still
have
the
ability
to
withdraw
a
portion
of
those
funds
depending
on
what
how
the
voting
goes
after
they've
staked
it.
So
anyone
can
stake
on
the
deaf
store,
but
also
remove
a
portion
of
those
funds.
It
can
never
be
the
total
amount,
but
it
will
be
there
will
be
a
percentage
and
then
they
get
removed
from
the
deaf
store
altogether.
So
things
aren't
necessarily
burned
immediately
or
all
the
way,
there's
a
little
more
subtlety
and
complexity
to
it.