►
From YouTube: March 30, 2020 Town Hall # 54
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
So
it's
to
new
core
contributors
joining
us
to
announce
so
Simon
started
last
week
on
the
marketing
team
he's
joining
us,
a
gross
marketing
manager
to
head
up
all
our
paid
and
performance
marketing
efforts,
he'll
be
like
part-time
until
first
May,
then
he'll
join
us
full-time
and
then
on
the
core
team.
We
have
some
real
hockey
Robinson
who's
joining
us
as
a
go
dev
welcome
to
them
both
so
quick,
hiring
update
for
you.
It's
no
surprise.
A
I
need
some
help
on
pops,
so
we've
just
hired
an
HR
and
Operations
Coordinator
who'll,
be
starting
in
mid-april
I'm,
pretty
excited
about
that
one.
We're
still
hiring
for
the
senior
product,
design,
architect,
role
on
design
and
also
protocol
engineer,
working
with
Dmitriy
on
engineering
and,
obviously,
we've
just
closed
the
NGO
developer
role
that
we
had
open
on
the
marketing
side.
We're
d
prioritizing
for
the
time
being,
a
technical
marketing
manager
and
a
technical
copywriter
and
those
are
less
of
a
priority.
A
But
what
is
is
a
growth
marketer
who
will
be
picking
up
where
all
of
the
leaves
off
when
he
ends
his
contract
with
us
in
mid-april,
so
yeah
I
think
really.
The
focus
will
be
getting
that
growth
mark
to
advert
out
this
week
and
promoting
it
and
see
what
comes
back
in
okay.
So
a
quick
recap
of
our
engagement
score
and
how
that
is
looking
right
now
and
I
pulled
this
from
the
system
today.
A
So
actually
we're
up
point
one
of
in
the
engagement
score,
since
our
last
survey
and
I
was
actually
kind
of
surprised
to
see
this
at
first
because
I
feel
like
in
general
and
when
you
see
turbulence
in
the
outside
world
that
simply
translates
to
a
dip
in
engagement
score,
but
I
chalk
it
up
to
as
being
like
pretty
resilient
overall
I
think
we've
we've
been
through
volatile
times.
You
know
working
in
crypto
anyway,
so
maybe
we're
just
gonna
battle
tested
and
ready
for
these
kind
of
things.
A
But
essentially,
although
the
outside
world
is
a
bit
more
insert-
and
you
know,
there's
certain
things
around
our
roles-
that
really
not
don't
change
like
the
environment-
that
we
work
in
the
flexibility
that
we
have
to
do
that
work
and
and
the
mission
and
how
we
connect
to
it.
So
that
was
really
cool
to
see
also
as
well.
A
The
fact
that
we
have
kind
of
high
engagement
in
terms
of
like
the
number
of
respondents
of
people
actually
answering
the
survey,
so
thank
you,
everyone
that
responded
and
then
I
just
wanted
to
have
a
deep
dive
into
one
area
that
I
thought
was
particularly
interesting,
and
that
was
around
strategy.
So
you
see
here
that
strategy
is
actually
made
up
of
two
different
parts.
One
is
the
communication
of
the
strategy
and
the
one
is
the
mission
itself
and
what
I
thought
was
interesting
about.
A
This
is
actually,
if
you
think,
of
the
mission,
as
kind
of
like
how
people
relate
to
the
overall
thing
that
we're
trying
to
do
and
are
they
able
to
connect
their
work
into
that
communication,
then,
is
really
the
bit
that
it's
like.
Are
we
then
communicating
that
strategy
back
out
in
a
coherent
way,
so
you'll
see
actually
there's
a
big
Delta
between
the
two
and,
if
I
had
to
choose
one
of
them
to
be
higher
than
the
other
I
would
say.
The
mission
is
the
most
important
thing.
A
I
think
that's
really
cool
to
see
that
we
have
such
strong
engagement
around
like
identifying
with
the
mission
itself
communication,
of
course,
being
like
a
hygiene
factor
of
how
we
make
that
real
and
how
we
communicate
that.
So
there's
a
bit
of
work
to
do
there
and
I
think
in
future
town
halls
or
try
and
bring
more
of
the
strategy
and
like
repeat
that
and
make
it
kind
of
more
visible.
So,
just
noting
that
this
work
to
do-
and
you
should
hear
more
from
us
on
that
soon-
all
right
on
to
core.
B
Okay,
cool,
so
I,
don't
want
to
jinx
us
we're
still
in
the
process
of
smoke
testing
the
latest
release
build,
but
we
should
tentatively
most
likely
be
submitting
version
1.2
to
the
App
Store's
today.
This
is
a
really
significant
release
for
us
because
it
includes
Waku
mail
servers
which
are
built
using
our
fork
of
the
whisper
protocol.
The
back
p2p
team
has
been
working
on
and
which
are
designed
to
prevent
the
app
from
using
really
ungodly
amounts
of
bandwidth
per
user.
B
We've
calculated
that
we
should
be
able
to
handle
roughly
10
times
as
many
users
and
currently
can
with
Waku
mail
servers
in
place
of
the
traditional
whisper
servers.
So
this
is
big
news
for
us.
We
want
to
make
this
release
relatively
focused,
so
we
could
chip
it
as
quickly
as
possible
and
get
to
making
sure
that
Waku
works
in
production.
B
Although
we
have
done
extensive
testing
on
our
end
and
the
new
mail
server
is
just
for
users
to
know
they
will
be
enabled
by
default,
but
you
can
still
like
to
use
the
whisper
servers
under
the
profiles.
Advanced
Settings,
for
the
time
being
so
we'll
be
in
a
transitionary
period
and
beyond
that,
once
we
get
this
release
at
the
door,
we've
already
got
a
good
selection
of
features
that
are
ready
to
go
for
version
1.3,
the
highlights
of
which
will
be
the
much
requested
dark
theme.
B
The
return
of
group
chat
also
popular
request
and
a
new
implementation
of
our
react.
Native
webview
beyond
that
Andre
and
I
are
discussing
using
a
few
days
this
week
and
next
for
cleaning
up
technical
tax
debt,
bug,
fixing
documentation
really
looking
at
maintenance
and
chores
and
something
that
was
suggested
by
by
one
of
our
QA
team
in
verse,
2
as
they
do
have
a
backlog
of
bugs
piling
up
and
we're
currently
blocked
on
the
highest
priority.
Growth
related
feature
that
we
have
in
the
pipeline,
which
is
the
status
starter
pack.
B
We've
pushed
that,
basically,
as
far
as
we
can
from
an
implementation
perspective
and
we're
now
waiting
for
approval
from
the
App
Store
on
something
to
do
with
our
registered
entity
and
we'll
also
be
working
on
key
card
integration.
Eme
has
a
nice
update
on
the
new
cards
that
they
ordered
successfully.
B
So
we'll
need
to
run
that
through
QA
again
before
we
can
include
that
in
a
future
release
and
beyond
that,
I
really
want
to
pick
back
up
on
where
we
left
off
with
the
roadmap
and
some
of
the
engagement
oriented
chat,
features
that
we
had
selected
months
ago
and
which
we
still
think
are
really
really
important
for
applications.
So
the
two
highlights
for
that
will
be
image
sending
and
chat
and
push
notifications
for
Android
devices.
So
that's
my
update.
C
C
You
can
check
them
out
now
at
spec
stuff
status.
That
I
am
to
figure
out
kind
of
how
stuff
works
at
the
very
basic
level
miscellaneous
stuff.
We
did
a
lot
of
diagramming
for
protocol
stacks
over
the
past
couple
weeks
and
that's
for
Nimbus
go
theorem
the
status
tab
itself,
future
NIMH
implementations
so
on
and
so
forth.
These
are
great
for
threat,
modeling
figuring
out
where
things
work,
how
information
flows,
how
they
fit
together,
where
problems
may
exists
and
just
understanding
how
the
app
and
its
components
all
fit
together
and
work.
C
Over
the
past
few
weeks,
there's
a
small
working
group,
that's
kind
of
getting
together
to
start
standardizing
the
threat
modeling
across
that
there's
a
myriad
of
ways
to
try
and
figure
out
where
threats
exists
in
any
any
given
application.
So
we're
trying
to
figure
out
a
more
standard
way
for
that.
We
can
do
this
for
all
of
the
projects
within
status
so
that
we
can
understand
where
risks
lie
and
how
to
mitigate
them.
C
D
So,
as
Corey
mentioned,
we
have
the
new
sights
that
I
am
there's,
also
work,
we're
going
to
get
a
starter
pack,
integration
for
universal
links
and
that's
been
already
deployed.
Although
properly
there's
been
some
improvements
for
the
Nimbus
fleet,
mostly
for
memory
limits,
because
there's
to
figure
out
exactly
where
the
no
more
leaks
are,
but
at
least
now
it
won't
be
crash.
The
whole
thing
we
have
improvements
in
the
build
process
first
is
react
to
lower
the
build
time,
especially
for
J's
bundle
and
also
some
promise
for
for
linting.
D
D
We've
also
the
Commission
did
the
swarm
fleet
because
pretty
much
nobody
was
using
it
and
also
got
some
additional
old
bus
or
some
cloud
there,
possibly
for
IPSS
or
for
any
personal
links
and
I'm
finishing
the
playing
at
3.
Db
I
was
a
bucket
for
Prometheus,
because
last
month
we
had
trouble
there.
They
just
work
for
emissions,
metrics
and
I
did
play
a
alternative
just
to
have
more
data
resilience
and
security.
D
E
You,
okay,
yeah
next
slide:
hey
I'm,
just
going
to
go
through
some,
some
metrics
really
quickly
on
social
or
content,
is
performing
really
well,
and
people
are
just
generally
chatting
about
status.
I
wanted
to
post
some
of
the
conversations
happening
once
that
is
in
here,
but
instead
I'll
just
show
the
impressions.
Sorry,
that's
impressions
and.
E
Sorry,
though,
impressions
and
and
mentions
once
again,
people
are
just
talking
about
status
generally
in
the
positive
light,
which
is
great
and
then
I
wanted
to
show
our
web
traffic
from
January
to
February
I,
sorry
from
January
February
to
March
you'll,
see.
Obviously,
February
I
had
a
much
significantly
higher
spike
because
of
the
launch,
but
our
numbers
are
up
from
one
month
before
from
January.
E
So
traffic
to
the
site
is
is
up
as
well
next
slide,
so
two
campaigns
which
are
closing
out
now:
the
sticker
market,
competition
we've
got
our
winner
here,
the
dog
sticker
pack
and
now
we're
just
working
with
all
the
artists
to
upload
all
of
their
packs
into
the
sticker
market
and
we're
gonna
be
running.
These
kind
of
small,
like
we're
gonna,
run
small
campaigns
like
this
throughout
the
year,
just
to
populate
the
sticker
market,
and
then
we're
also
getting
ready
to
launch
the
analytics
dashboard
for
the
sticker
market.
E
So
we
can
see
the
flow
of
SMT
through
the
from
the
feature
and
then
also
we've
got
like
an
ongoing
mobile,
defy
campaign,
ending
Revere
continuing
to
work
on
this,
and
it's
just
performing
really
well
both
on
social
and
driving
traffic
to
the
site.
So
we're
going
to
continue
to
do
that
and
think
about
how
we
can
expand
on
this
topic.
E
Just
because
it
is
such
a
hot
topic
within
the
industry,
and
then
we
are
doing
some
light
that
well
outreach
to
potential
partners
to
figure
out
what
a
potential
partnership
could
look
like
and
then
there's
a
lot
of
other
stuff
going
on
with
the
releases.
Unfortunately
well
well
we're
working
with
our
PR
team
a
lot
more
these
days
and
a
lot
of
like
you
know,
future
releases
or
big
campaigns
are
under
embargo.
Just
so,
we
can
maximize
our
reach
during
these
moments.
So
there's
not
much
to
report
on
there.
F
F
F
F
F
All
locking,
bugs
and
high-priority
bugs
have
been
fixed,
but
we
we
want
to
have
a
QA
effort.
As
Rachel
said,
when
the
testing
we
will
be
ready
to
work
on
this
before
we
actually
release
these
features
in
the
instead
of
V
1.3
seems
a
bit
probably
a
bit
talk,
so
the
most
realistic
target
is
V
1
point
4.
F
All
right,
can
you
jump
to
the
next
slide?
Please
yeah,
a
second
thing
so
well,
as
you
know,
the
primary
use
case
for
key
card
is
to
be
a
city
or
store
value
out
of
a
wallet
and
that's
what
we
are
reading
in
status,
as
discussed
in
the
previous
slide.
Now,
we've
identified
a
couple
of
months
ago.
A
second
interesting
use
case
is
to
use
key
card
as
a
mean
of
payment
in
real
life
in
the
physical
world,
and
there
are
two
core
ideas
about.
F
That's
one,
and
the
second
core
idea
is
that
status
should
be
able
to
be
turned
into
a
point
of
sale
by
simply
accessing
a
point
of
sale,
dab
within
status
to
be
completed
as
a
third
core
idea,
but
with
not
designed
and
implanting
implemented
it.
Yet.
The
third
idea
is
that
merchants
should
be
running
status.
We
know
that
because
they
that's
the
second
point.
They
are
accessing
the
point
of
sale
that
rooster
us,
but
they
should
be
actually
securing
the
network
by
staking
some
assets
there.
F
So
we
worked
on
this
in
the
past
month
and
we
are
now
really
single
framework.
It
consists
of
several
parts:
there's
a
keycard
applet,
there's
a
smart
contract
wallet,
there's
a
factory
to
generate
the
smart
contract
wallets.
There's
a
point-of-sale
DAP,
there's
non-web
free
website
application
to
check
the
user
wallet
that
is
carrying
with
this
key
card
and
a
couple
of
other
things
with
overall
focused
on
the
logic
needed
on
the
payment
network
using
key
card
more
than
on
the
scalability
aspects.
F
A
F
So
so,
here
we're
on
the
user
side,
the
users
got
a
key
card,
it
could
be
preloaded
with
some
assets
or
it
could
be
empty
and
to
check
and
top
this
up.
It's
simple:
it
just
taps
the
card
on
any
phone
and
is
the
standard
word
to
browser
that
shows
the
the
balance
here.
We
are
bit
ahead,
but
the
user
has
been
also
able
to
show
it
to
echoed
and
from
another
wallet
is
topping
up,
is
wallet,
so
that's
just
the
user
facing
experience.
F
The
and
the
merchant
is
confirming
the
transaction,
and
that's
it.
The
payment
went
through
directly
by
tapping
a
card
on
the
point
of
sale.
Now
something
the
user
can
tap.
This
card
on
any
phone
status
is
not
even
installed
here
and
it
opens
up
the
way
that
app
and
you
can
see
is
balanced.
Well,
it
was
a
bit
quick,
but
you
can
check
the
video
it's
on
the
the
disk
indistinct
I
talked
about
earlier
on.
F
F
F
F
It
can
you
can
print
a
QR
code
on
it
or
you
can
use
the
NFC
tap
feature
to
carry
this
deep
link
and
this
deep
link
can
download
status
can
open
a
tab
can
allow
some
referral
features.
Second,
key
card
can
be
prodded
with
assets,
and
I
wanted
to
know
that
this
is
now
possible
because
we
have
two
card
cash,
a
plate
and
the
request
crane.
Third,
it's
also
a
support
for
physical
marketing
can
be
printed,
it
can
be
distributed,
it
can
be
sold
and
the
fourth
thing,
obviously,
it's
a
sexual
store
value.
F
It's
a
hardware
while
it's
and
that's
a
true
added
value
for
most
crypto
users
so
from
there,
and
if
you
can
go
to
next
slide,
we
believe
they
are
partnerships.
We
can
build
with
some
relevant
deaths
because
of
all
these
characteristics
and
to
make
things
simple.
I
wanted
to
give
two
examples
with
two
different,
two
very
different
types
of
that.
These
are
just
examples,
because
we're
currently
brainstorming
all
on
who
are
the
most
relevant
that
first,
one
would
be
with
with
a
blockchain
game.
F
Just
imagine
a
nice
co
branded
card
printed
with
some
status
logo
and
with
the
the
game
logos,
cars
would
be
offered
or
sold
on
events
or
sold
in
shops
and
from
their
user
could
either
scan
a
QR
code
on
the
back
of
the
card
or
tab
the
card
they
would
get
status.
They
would
on
board
status,
I,
create
a
wallet
and
easily
redeem
some
n
FTS
from
the
game
and
could
get
could
redeem
some
if
gas,
if
needed.
F
If
there's
no
obstruction
of
gas
in
the
attraction
in
the
interaction
with
the
DAP
game
and
and
be
directed
directly
to
the
DAP,
the
ganged-up,
so
that's
one
example.
Another
example
would
be
with
decentralized
exchanges,
which
are
already
actually
quite
prone
to
distribute
hardware.
Well
it's
to
their
users
because
they
want
their
users
to
understand
that
the
assets
are
on
the
ownership
of
the
users
and
not
on
the
decks
itself.
So
they
could
offer
or
sell
cards
to
their
customers,
maybe
high-value
customers
and
just
an
example.
F
They
could
be
sent
by
mail
from
their
user
would
scan
the
QR
code
on
it
or
tap
the
card
or
just
simply
click.
Oh,
you
were
a
deep
link.
You
are
sent
by
email
to
them
and
same
experience.
They
would
get
status
on
board,
maybe
reading
some
free
token,
if
that's
relevant
with
this
exchange-
and
this
is
onboarding
the
user
into
an
experience
where
they
can
use
the
decks
with
status
on
their
mobile
phone
and
use
the
keycard
as
a
super
sexual
hardware
wallet.
So
we
believe
this
makes
a
lot
of
sense.
F
We
would
still
have
some
work
to
do
to
identify
the
most
relevant
app
to
explain
the
value
proposition
to
these
dabs,
we're
working
on
that
with
the
marketing
team
now
and
develop
first
partnerships.
So
if
you
have
some
ideas
about
this,
there's
a
discussed
post
from
last
week
and
your
feedback
will
be
super
appreciated
and
that's
it.
For
me,
amazing.
A
G
All
right
so
new
updates
for
subspace,
we
had
the
two
releases.
One
was
1.3
which
we
make
it
3
shakable
support.
That
was
something
was
missing
before
we
all
saw
the
new
matters
to
be
able
to
track
a
various
blocks.
Data
such
as
a
block
x,
or
particularly
data
in
the
block,
well
I'm
kind
of
missing
whoa.
What
is
that,
but
anyway
and
grass,
and
also
things
like
gas
prices-
and
there
was
various
bug
fixes
on
that
and
on
on
a
soft
space?
We
had
this
react
component
support,
so
it
provides.
G
It
provides
a
react
provider
which
automatically
can
connect
to
soft
space.
It
also
provides
a
bunch
of
utility
methods
for
react
which
makes
integration
much
much
easier
case.
For
this
release
goes
to
Richard
Ramos,
then,
on
to
the
website,
we
have
a
brand
new
website.
You
can
please
check
it
at
subspace
at
embark,
labs
at
I/o,
Christa
Graham
for
organizing
this
with
the
wood
front-end
developer.
G
G
For
it,
so
we
are
then
202
releases.
So
first
is
the
embark
525
point:
it's
a
it's
again
we're
making
him
work
lighter
and
faster
and
easier
to
use.
So
one
one
change
that
instead
of
gas
we're
using
a
simulator
as
the
default
blockchain,
which
makes
it
much
faster
to
start
and
interact
with
also
doesn't
require
really
I
get
anymore
as
a
requirement
to
use
embark.
We
improve
the
support
for
for
proxying
contracts.
We
improve
the
ENS
integration.
We
added
some
utility
matters
like
artefacts
required,
which
makes
it
easier
to
switch
projects
to
embark.
G
We
added
script
support
which
allows
the
developer
to
do
custom,
migration
and
custom
scripts,
and
we
had
a
lot
of
warning
deprecation
warnings
in
preparation
for
six
points,
so
things
that
the
developer
needs
to
change,
so
the
that
that
will
work
in
and
6.0
and
on
6.0,
which
is
will
it's
nearly
there
which
should
release
this
week?
Hopefully,
so
a
lot
of
plugins
no
longer
come
as
default.
That
includes
from
get
to
the
graph
functionality
ipfs
priority
whisper
swarm.
So
all
of
that
now
it's
plugins
that
you
can
pick
and
choose.
G
G
So
everything
is
a
plugin
with
what
6.0
we
also
for
compatibility
purposes
with
support
projects
without
needing
embark
at
Jason
file.
We
had
support
for
this.
Also
this
new
config
file
in
GS,
which
is
much
more
powerful
flexible.
What
we
can
do,
we
also
have
we
can
configure
contract
arguments
as
us
functions
again
is
very,
very
flexible.
We
have
this
kind
of
like
magical
super
template
functionality
being
done
by
by
Michael,
and
we
also
support
custom,
atrium
library
to
libraries
to
generate
artifacts
when
before
we
were
only
supporting
embark
at
GES.
A
That
said,
awesome
thanks,
Yuri
lots
of
cool,
shout
outs.
There
I,
like
the
sound
of
the
magic
super
template
as
well
all
right
cool.
So
that's
the
end
of
our
kind
of
like
scheduled
content,
let's
get
into
the
Q&A.
So
if
you're
ever
wanting
to
ask
us
a
question,
just
drop
by
that
channel
mentioned
there
and
we'll
get
them
answered
in
the
next
town
hall
all
right,
so
we
have
three
questions
today.
All
from
our
friend
Paul,
majestic
Iceland
goal.
Number
one
is
on
sticker
market.
A
B
Yeah,
can
you
answer
that
so
yeah,
so
not
from
then
we're
not
going
to
build
an
interface
for
this
any
time
soon.
It
hasn't
prioritized,
yet
simply
because
it
doesn't
really
factor
into
user
growth,
although
we
really
think
it's
an
exciting
feature
and
opportunity,
and
you
can
actually
still
get
to
the
end
result.
Here
we
have
a
very
ad
hoc
google
form
available
for
designers
who
would
like
to
submit
stickers.
So
if
you
go
through
the
Google
form,
I'll
find
a
way
to
distribute
it.
B
We
can
send
it
through
in
status
and
somewhere
in
a
town
hall
slide,
but
you
can
just
submit
your
images
and
the
metadata
for
your
packs
there,
as
well
as
your
aetherium
address,
where
you
would
like
to
receive
payment
for
stickers
and
in
a
forthcoming
release.
Well,
we'll
be
sure
to
pull
those
in.
You
know.
A
B
A
B
Unfortunately,
heartbreakingly
this
one
is
also
not
in
the
pipeline
in
time
soon,
just
a
massive
massive
project,
we've
got
so
much
else
on
our
on
plate
right
now
that
that
is
really
factoring
into
user
growth.
Again
we
love
extensions.
We
see
great
opportunity
there,
but
unfortunately
dude
the
level
of
effort
required
on
all
fronts
from
all
teams,
we're
going
to
have
to
delay
that
or
ice
box
it
for
now
so
I'm.
Sorry
about
that.
Well,.