►
From YouTube: Status Townhall #32 - April 15, 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
Okay,
so
let's
get
started
hi
everyone
welcome
to
the
thirty-second
town
hall.
As
always,
I
am
your
host
roshani
still
flying
solo
Rachel
will
be
back
with
us
hosting
in
a
few
weeks.
Thank
you.
Everyone
for
the
feedback
with
the
last
Town
Hall
I
heard
you
guys
loud
and
clear.
Get
some
jokes
make
the
town
hall
more
engaging.
So
today's
Town
Hall
was
less
jokes,
but
the
guest
will
be
brought
to
you
by
dancing
Drake.
If
you
don't
know
who
Drake
is
you
will
by
the
end?
So
let's
get
started.
First,
we
have
Carl,
hey.
B
B
That
brings
us
through
to
January,
2020
and
I'm
cognizant
that
the
volatility
of
the
organization
script
OSS,
can
induce
uncertainty,
but
we
have,
in
my
opinion,
a
reasonable
balance
right
now
we
still
have
a
lotta
three
served
to
retain
outside
potential
and
we're
in
the
best
financial
position
we've
been
in
four
months.
So
we'll
continue
to
give
rolling
updates
on
this,
and
hopefully
we'll
have
only
more
good
news
to
come
anyway.
That's
it
for
me,
and
so
thank
you
very.
A
All
right
thanks
Carl
and
thanks
for
that
fantastic
update
all
right.
Next,
we
have
build
week,
okay,
metals
didn't
show,
but
thank
you.
Everyone
who
participated
and
helped
during
build
week.
It
was
a
really
successful
week.
We
had
13
amazing
amazing
projects,
and
here
are
the
winners.
First
place
went
to
embedded
chats
with
Gary
and
Richard,
so
congratulations
guys.
Second
place
went
to
continuous
subscriptions
with
Barry.
Congratulations,
Barry
and
third
place
went
to
key
card
Metatron's,
actually
with
Andrea
Demetri
Michele,
inky
Louie,
and
so
congratulations
all
for
everyone
who
participated
all
the
projects
were
amazing.
A
You
guys
all
killed
it.
Voting
was
decided
on
a
voting.
Deb
and
I
also
asked
some
of
the
community
members
to
weigh
on
their
favorites
the
voting
pretty
much
matched
up
with
the
voting
gap,
so
yeah
winners.
You
will
be
receiving
your
present
soon
and
later.
Today
a
recap
will
be
posted
and
everybody
can
check
the
links
that
are
shared
all
right
now.
Our
Hale
here
from
the
bill
with
a
write,
update,
hey.
C
C
We
all
know
so
we're
just
testing
on
different
tools
and
raqqa
is
a
pretty
good
balance
between
overly
powerful
Microsoft,
Project
style
software
and
something
that's
easy
to
use
and
hopefully
doesn't
take
up
too
much
time
with
the
goal
of
increasing
visibility
for
timelines
of
dependencies
and
also
making
sure
that
some
teams
own
overburden.
So
what
we
found
in
q1
was
that
there
was
a
lot
on
plate
for
certain
swarms
and
that
ended
up
setting
unrealistic
deadlines
on
winning
things
will
get
done.
So
the
goal
is
that
software
like
this
can
help.
C
C
So
we
want
to
make
sure
that
it's
going
to
be
useful
before
we
invest
the
money
into
signing
up
for
it,
because
it's
a
pretty
significant
cost
as
a
good
rule
of
thumb,
if
it
if
it
takes
over
10
hours
of
work
or
it's
a
significant
milestone,
it's
worth
it
to
be
tracked
inside
of
Reich,
and
you
can
see
an
example
on
the
next
slide
of
what
a
typical
project
would
look
like.
So
you
can
see
this
is
the
DAP
store
swarm.
C
You've
got
the
MVP
there.
You've
got
the
new
version
of
the
design
and
ma
che
has
gone
in
and
kind
of
put
in
a
bunch
of
work
that
he's
going
to
be
doing
each
one
of
these
being,
for
example,
over
ten
hours
of
work.
You've
got
that
you've
got
the
contract
section
as
well,
and
it's
if
you
play
around
with
it
it's
a
lot
simpler
than
look.
You've
got
tasks
and
subtasks,
and
things
like
that
so
anyway,
I
would
suggest
everyone
take
a
look
play
around
become
familiar
and
over
the
coming
week.
C
We'll
be
deciding
what
I
like
you
know,
it
doesn't
make
sense,
but
does
it
make
sense
for
some
business
and
if
so,
how
many
licenses
are
we
doing?
And
things
like
that?
So
hopefully
this
can
get
everyone,
especially
on
the
core
team.
Increased
visibility
on
you
know
what
what
everyone
else
is
working
on
and
just
help
us
overall,
as
an
organization.
A
D
That
is
more
future
proof
and
we
all
know
we've
decided
to
go
for
the
more
future
proof
one
and
make
things
right
the
first
time
and
be
able
to
do
updates
in
a
proper
way
without
disruption
to
the
feature
so
right
now,
the
current
situation
is.
We
are
exploring
the
use
of
swarm
for
storing
the
treetog
manifest,
which
will
make
setting
a
tribute
to
talk
actually
free
and
updating
it
as
well.
D
So
it
has
quite
some
advantage
or
so
there's
some
feedback
from
the
contract
auditing
and
the
firm
that
does
the
auditing
rightfully
exposed
the
concern
that
if
we
use
a
contract,
then
it
will
give
someone
the
possibility
to
spam
during
the
small
window
when
someone
is
setting
needs
to
be
to
talk
and
before
it's
actually
put
on
chain.
So
long
story
short
now
we
are
experimenting
with
form
and
it
should
make
the
feature
easier
and
more
popular
because
it
will
be
free
to
set.
So
that's
it
for
now.
E
So,
with
this
again,
first
of
things,
that's
right
now
in
the
test
mode
and
reg
develops
like
it
as
a
proof
of
concept,
a
new
fleet
that
has
mail
servers
from
a
smart
contract.
It's
should
be
merged,
all
ready
to
status
reacts
and
then
the
second
thing
that
we
were
actually
worked
on
the
build
week
is
their
admin
UI
for
notes
that
we'll
need
for
installation
anyway.
So
that's
also
work
in
progress,
I'm
planning
to
keep
working
on
it
little
by
little.
That's
all
for
us.
B
Right
so
we've
been
working
in
this
and
then
you
do
surprise.
Arbitration
I,
wrote,
work,
form
and
I'm
actually
my
protocol,
which
is
that
the
physical
second
phase
of
arbitration
protocol,
when
starting
to
do
some
pre
secret
testing
and
review.
That's
basically
what
was
essentially
the
extensive
reviews
of
the
of
the
contracts
and
the
workflow
that
finally
flows,
and
we
also
migrated
for
to
embark
for
and
encrypt
reactor,
which
makes
it's
much
much
nicer
to
people.
B
C
Hi,
so
in
the
last
week,
I
created
some
react
components
to
start
testing
the
contracts
in
a
more
user
way
and
I
basically
made
a
simple
UI
for
set
delegate
as
well.
I
participated
on
the
build
week,
building
a
muted,
multisig
so
topic
that
democracy
is
basically
it's
like
a
multi
seek,
but
instead
of
signatures,
you
have
this
token
holders
deciding
so
some
of
the
UI
I
don't
for
the
hackathon
would
be
useful
also
for
top
with
democracy,
and
that's
it.
A
E
We
show
this
and
you
have
actually
a
button
to
load
this
missing
messages
on
demand.
If
you
want
to-
and
it's
yeah,
we
don't
do
it
automatically,
because
we
try
to
avoid
too
much
traffic
consumption,
but
right
now
for
the
public
chat
rooms,
we
also
increase
in
our
increase
in
the
number
of
days
from
one
day
of
data
to
seven
days.
So
it's
also
helped
so
hopefully
you
won't
see
this
UI
that
much
but
yeah.
If
you
do
that's
it,
then
we
also
did
some
updates.
E
Like
react
native
realm',
we
help
help
a
little
bit
with
bounties
and
we
actually
get
a
good
result
from
bounties
that
were
bug
fixes
much
more
than
from
budget
set
more
features.
So
that's
a
good
learning
thing
more
thing.
That's
one
thing
that
was
discovered
today,
literally,
but
it's
before
the
it's
important.
So
it's
a
last
time,
payload
box
away
mitri
stumbled
upon
a
bot
that
could
cause
a
neverending,
like
literally
a
never-ending
singular
messages.
E
Think
so
I
hope
that
when
we
fix
this
I'm
not
saying
that
is
the
only
bug
that
can
cause
the
very
long
initial
scene,
but
it
might
be
one,
that's
yeah
influences
a
lot
and
yeah.
You
see,
there's
quite
a
lot
of
themes
there,
including
the
documented,
like
current
status
protocol
that
we
use
like
an
RFC
and
yep
anyone
who's
interested
can
take
a
look
at
the
repository,
but
yeah
I've
been
talking
for
yeah,
okay,.
A
F
Everyone
it's
been
a
while,
since
we
give
last
update
now
since
bean
of
April
Dinah's
joined
us.
It's
a
very
welcome
addition
and
Adam
as
well,
has
been
working
a
lot
of
on
documenting
the
current
protocol.
It's
really
shaping
up
and
soon
we'll
have
a
kind
of
at
least
solid,
solid
draft
of
what
that
current
protocol
looks
like
and
and
the
guarantees
it
provides,
and
so
on
and
sort
of
part
of
the
cultural
change
in
having
a
process
for
how
we
change
the
protocol
so
going
forward.
F
Whenever
you
want
to
make
larger
changes,
your
protocol
will
do
that
in
this
picture.
Posturing
as
part
of
that
also
Adam,
is
also
been
doing.
Some
good
work
on
on
implementing
is
a
reference
client
as
part
of
the
effort
in
core
to
move
the
protocol
from
closer
to
go
that
will
simplify
testing
and
so
on
the
inner
circle
atoms
of
this.
F
This
new
family
of
protocols,
which
you
called
the
Big
Brother
specs
and
is
essentially
our
current
understanding
of
what
the
next
version
of
status
protocols
would
look
like
and
as
part
of
that,
we've
also
been
working
on
the
peer
to
peer
data.
Synchronization
as
survey,
it
was
kind
of
turning
into
its
own
paper.
F
We
also
have
these
bi-weekly
calls
that
are
kind
of
similar
to
the
court
of
call
sort
of
him
to
Bhutto
implementation
calls
with
other
interested
teams
in
the
space
to
sort
of
provide
solid
foundations
for
for
messaging
web
free
and
then
recently.
We
also
had
this
or
basic
a
swarm
piece
as
proof
of
concept,
the
slightly
rated
it
to
PSS,
but
it's
more
kind
of
like
a
spike
to
see.
F
Sorry
today,
sync,
but
it's
it's
more
kind
of
a
spike
to
see
what
an
alternative
stack
would
look
like,
and
we
also
got
a
shout
that
in
this
weekend,
affair,
together
with
the
chaos
unicorn
and
the
winner,
URIs
Richards
embeddable
chat
in
terms
of
an
expertise.
It's
about
defining
a
minimally
viable
data,
synchronization
specification
and
proof
concept
as
well
as
sort
of
finalizing
at
this
is
a
first
draft
of
our
current
protocol
and
providing
a
more
clear
interface
to
other
products
in
space
like
valid
labs
and
them,
and
so
on.
F
A
G
Hi
everyone
can
you
go
through
the
next
slide,
please
yeah.
So,
with
regards
to
availability
of
the
cards,
the
factory
had
the
several
delays,
but
we're
now
ready
to
go
so
we
have
2000
cards
at
a
logistic
provider
which
is
in
France
they're,
ready
to
fulfill
orders
for
worldwide
shipping
and
from
today.
Actually
so
we
have
about
500
developers
we
signed
up
and
provided
provided
their
github
accounts
to
get
some
free
code
to
test.
They
will
shoot
tomorrow
and
about
you
guys.
I
mean
contributors.
I'll,
send
you
before
tomorrow
a
coupon
card
code.
G
Sorry,
you
can
use
on
a
our
website
to
receive
a
receive,
a
card
for
free,
of
course
and
yeah.
It
would
be
very
helpful
if
you
can
provide
that
to
me
any
feedback
about
the
experience
to
order
it
receive
it
and
the
look
and
feel
of
the
the
products
we
can.
So
we
can
make
it
even
better
in
the
future.
G
G
It
looks
pretty
simple,
as
you
see
in
as
you
will
experience
it
but
simple,
and
we
can
probably
make
it
better,
but
it
works
and
I'm
really
confident
it
will
be
quite
reliable
all
for
a
smooth
lounge.
If
you
can
go
to
next
slide,
please
some
characteristics
of
this
site
work
quite
quickly,
so
it
manages
all
v80
rules,
especially
the
European
one.
It's
legally
compliant
with
GDP
era,
European
warranty
rules,
so
thanks
Sonia,
for
all
your
help
on
that
payment
can
be
done
with
the
visa
off
crypto.
G
So
for
now
it's
if
a
bitcoin
and
litecoin,
it's
powered
by
your
conveys
the
Commerce
for
now
I
try
to
have
as
much
automation
as
possible
with
the
site.
So
returns
management
are
semi
automated
through
a
pothole
and
all
invoice
management
and
logistic
fatimids,
which
is
the
big
stuff.
Actually,
the
registering
fulfillment
is
fully
automated.
G
G
So
what
our
main
development
priorities
a
couple
of
things.
Of
course,
we
want
to
integrate
key
card
in
status,
Android
build
with
a
great
user
experience.
Of
course
we
want
to
integrate
key
card
with
the
ledger
and
I
know
X.
So
this
is
for
Android
and
iOS,
and
this
is
working
over
Bluetooth.
We
want
to
enabled
payment
with
key
karada.
So
that's
what
we
call
point-of-sales
use
cases.
G
There's
been
some
discussion
in
the
channels
and
instead
us
about
that-
and
we
say:
what's
our
the
tinted
for
the
pin
week,
and
we
want
to
enable
super
easy
onboarding
for
new
key
card
users
for
this
payment
scenarios.
I
had
explained
more
about
this
after
a
next
one,
please
so,
first,
as
per
the
integration
in
the
Android
app,
we
now
have
a
fully
featured
Android
build.
We've
got
that
for
about
two
weeks
now,
I
call
it
the
MVP
on
this
planning
we're
in
a
phase
where
it's
been
tested
bugs
enlisted.
G
Thanks
for
all
the
work
from
the
testing
team
about
that-
and
they
are
being
fixed-
and
here
also
really
kudos
to
Dimitri
for
all
the
hard
work
to
fix
all
the
issues,
we
can
use
that
for
real
now
we
can
also
have
more
uxf
feedbacks
and
we
will
be
going
from
tomorrow
through
a
new
round
of
user
experience,
discussion
and
improvements.
The
decision
to
make
the
experience
better,
because
here
I
mean
you
really
need
to
use
the
app
with
tucking
the
card
to
make
sure
about
the
user
account.
G
One
thing
to
note
quickly
is
that
key
card
does
I
mean
account.
The
key
card
base,
use
a
different
paths
for
wallet
and
chat
key,
so
this
creates
some
user
experience,
issues
that
we
will
fully
solve
only
when
we
would
have
a
multiple
account
where
it
experience,
and
these
issues
are
the
two
things
basically
I
mean
we
need
multiple
accompaniment
to
manage
fans
that
get
to
the
whisper
path.
G
That's
one
thing
and
the
other
one
is
for
now:
if
you
import
them
the
manic
two
key
card,
you
won't
find
the
same
identity
same
three
words
that
you
would
get
if
you
import
it
the
same
mnemonic
into
a
non
key
called
studies
account
and
next
one
please.
So,
as
per
ledger,
we
have
progressed
a
lot.
We
have
a
ledger
app
now
with
the
sexual
channel,
it
sounds
transaction.
You
can
export
a
whisper
keys.
G
Fana
we
are
blocked.
We
need
some
samples
from
ledger
to
finish
all
the
work,
especially
about
Bluetooth
Low
Energy
I
mean
the
the
Bluetooth
link
and
do
all
the
testing
and
average
durability
app
me
Kelly
has
made
some
t-carr
DPI
an
applet
evolution
to
support
the
legend,
use-case
main
thing
being
to
manager
hard
wallet
that
has
its
own
UI.
G
So
we
provided
some
details
there,
so
I'll
be
quick,
and
there
is
this
demo
that
Andrea
did
that
you
can
check
and
and
the
discussed
post
about
that
too.
Overall,
we
are
still
in
a
research
phase.
Here
we
want
to
enable
quick
and
easy
payments.
I
whiskey,
God,
just
like
a
delicate
the
issues
we
are
trying
to
solve
and
how
we
are
currently
thinking
about
solving
them.
First,
we
need
a
very
quick
tap
experience.
No
pairing
code,
no
pin
so
to
order
that
we
made
a
new
version
of
kicad
API,
an
applet.
G
The
point
of
sales
side
can't
be
fully
trusted
and
the
key
code
has
no
screen.
So
the
problem
here
is
that
it's
hard
to
know
for
sure
which
transaction
we
sign
when
tapping
what
we
investigating
is
to
use
meta
transaction,
that's
the
demo
that
was
done
last
week.
The
wallet
that's
actually
actually
used
for
phones
is
just
a
smart
contract
and
it
has
complete
control
about
the
transaction.
G
Typically,
maximum
amount
allowed
per
transaction
and
keycard
is
just
a
trigger
to
spend
the
funds
by
this
wallet,
and
another
issue
is
I
mean
what
we
are
trying
to
build
with
status.
Here
is
really
a
an
open
network
of
payment
terminals
and,
on
the
other
hand,
point-of-sales
are
custom
and
hardware
and
software.
G
G
G
Second,
one
is
that
we
want
to
allow
prepaid
prepaid
cards
so
either
in
shops
or
at
events,
and
the
third
thing
is
that
we
want
the
user
to
be
able
to
spend
this
crypto
easily
and
when
I
say
easily,
for
these
three
cases
means
before
sending
up
a
for
status.
Account
is
the
key
card,
because
setting
up
cause
status
account
completely.
It
takes
some
time,
I
mean
it's
a
process.
That
saying
is
difficult.
Obviously
we're
working
hard
to
make
it
smooth,
but
still
it's.
G
It
takes
some
time
and
some
effort,
and
we
want
a
very
good
in-store
experience
or
very
good
teller
experience.
So
we
want
the
user
to
be
able
to
do
these
three
things
in
a
snap
and
do
the
full
in
creation
of
the
status
account
on
the
card
only
after
when
it's
home,
for
instance,
so
we
need
to
make
a
key
car.
The
protocol
evolve
that
next
one
please.
G
So
this
is
a
last
word.
We
were
really
glad
to
have
some
PRS
coming
from
non
core
contributors.
This
is
starting.
We've
got,
for
instance,
key
cards
report
merged
in
gas
by
the
ground
teams,
every
one
team,
sorry
so
kudos
to
Andrew
for
the
support
that
he
provided
and
we've
got
two
fellow
projects
a
grid
plus
and
the
ID
pass
that
started
to
submit
cures
for
key
card.
It's
pretty
recent
actually
ends
coming
from
last
week.
A
Thanks
keely
super
excited
to
hear
all
about
key
cards,
and
can
we
choose
my
key
card
all
right,
jumping
into
Q&A,
so
we
had
some
questions
that
were
submitted
from
status,
chance,
Town
Hall
questions.
So
the
first
question
was:
what's
the
status
communication
performance,
if
there
is
hundreds
of
millions
of
users
online
at
the
same
time,
does
anybody
have
a
online
answer.
F
B
F
A
brief
one:
it's
it's
not
good
with
a
hundred
million
muses,
that's
that's
part
of
the
problem
with
whisper
as
well
as
the
way
we're
currently
using
it.
That's
largely
why
we
are
there's
wonderful
raises
way.
We're
looking
into
is
protocol
effort
to
be
able
to
sort
of
create
a
base
that
a
protocol
base
that
can
scale
to
launch
or
mass
of
users.
So
it's
definitely
a
limitation
right
now,
but
we're
working
on.
A
E
F
F
Can
just
briefly
on
there
because
it
was
the
second
question,
which
is
how
many
notes
in
Toronto
Star's
network
to
maintain
cell
yeah,
no
I
think
one
way
to
think
about
that
is
that
it's
more,
it's
not
an
absolute
number,
its
instead
a
kind
of
proportion
to
the
amount
of
total
users.
So
so,
given
that
you
have
hundred
users,
then
maybe
you
need
at
least
10
people
who
who
runs
or
while
or
whatever
you
need
some
amount
of
for
users
who
run
these
of
notes,
with
extra
capabilities
and
so
on
and
and
they're.