►
From YouTube: Status Dev Call #33
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).
B
A
C
Am
seeing
what
goofy
to
feedback
were
probably
best
async
and
discuss
threat,
but
looking
for
here,
commitment
from
the
core
desta
and
stimulus
team
participation,
so
walk
with
me
to
is
the
topic.
Second,
is
Simba's
here
cloth
for
death
to
write
new
code
in
nib
and
the
third
is
clarity
on
the
metrics.
C
A
A
A
D
Yes,
it's
in
say
scene,
one
wasn't
discussed,
read
that
I
think
people
have
read
what
we
need
is
assembly
team,
so
we
can
stop
working
it
now
which
of
the
timelines.
Perhaps
so.
The
main
thing
that's
missing
now
is
just
people,
someone
from
core
desktop
and
symbols,
and
then
we
can
start
having
kickoff
call,
ideally
tomorrow
or
sometime
this
week.
A
In
regards
to
data
as
a
batter,
we
actually
started
the
steam
bus
stop
first
and
and
from
there.
Actually
you
know
go
to
the
to
the
wacky
stuff,
because
because
just
now
like
we
integrating
desktop
and
mobile
into
the
the
name,
work
and
steam
bus
is
supposed
to
be
the
first
step
toward
that.
So
it's
more.
D
D
The
same
thing
goes
for
core,
and
it
was
something
that
Andrea
brought
up,
that
there
should
be
someone
who
speaks
on
behalf
of
core
when
it
comes
to
integration,
to
make
sure
we
capture
these
issues
orally
and
so
on,
because
otherwise
we
could
be
off
in
our
own
corner
and
just
do
whatever,
but
that's
probably
some
optimal,
because
the
ultimate
use
would
be
core.
That's
talking,
snippers
right,
it
doesn't
have
to
be
a
big
commitment.
D
D
Yeah
I
like
this
is
a
predictor
from
from
Simba's
I'm,
not
sure
about
person.
Beyond
this,
it
was
called
I'm
looking
to
organize
a
kick
up
called
for
for
this
knit
back
with
you,
but
in
order
to
do
that
with
with
the
main
team
and
so
on.
In
order
to
do
that,
it
has
to
be
clear
who
the
participants
are
so
that
that's
it,
but
it's
a
separate
from
this
team
Pacific.
It
wouldn't
be
the
same
thing,
because
a
lot
of
the
work
would
happen
in
in
back,
go
and
overly
p2p,
and
so
on.
F
A
D
F
A
A
D
I
just
mean
that
it
just
something
that
Andrea
brought
up
that
in
order
for
us
to
do
not
do
double
work
and
you
start
in
cells
go.
It
has
to
be
the
case
that
we
saw
to
write
yourself
in
in,
but
it
seems
like
given
course
timeline
constraint
that
that's
not
yet
possible,
and
maybe
that
will
be
possible
once
the
chin
is
out.
So
if
just
clarity
on
that
and
and
future
self,
like
p.m.
server
you
know-
and
so
on,
could
be
written
in
in
once
this
gymnast
it's
done,
then
everything
is
good.
D
G
G
Gonna
have
to
invite
a
quite
a
bit,
and
so
what
I
gave
me
like
Nimbus
provides
the
way
for
me
not
to
have
to
drive,
see
this
girl
code
and
see
me
into
the
bright
new
hood
and
somehow
in
today,
and,
for
example,
like
to
make
a
simple
example.
The
client
is
very
difficult
to
write
in
name
that
will
be
technically
very
challenging.
It's
very
much
involved
in
your
keys,
your
contacts
as
well.
The
server
is,
it's
tiny,
easy,
but
you
know
simplest
anywhere.
You
know
we
do
use.
G
How
do
I
do
that
essentially
like
if
I
Drive
mean
code,
then
I
would
need
you
know
either
I've
got
and
leave
library
to
implement
PFS,
which
others
is
not
physically
reasonable
timeline,
but
they
appear
to
push
the
server
or
you
know,
like
I,
have
another
way
essentially
like.
If
it's
this
quiet,
even
please,
then
I
can
start
doing.
A
Okay,
so
I
mean,
for
example,
for
the
stuff,
for
the
keys
would
be
acceptable
that
we
we
could,
for
example,
sign
sign
in
status,
go
and
and
make
you
know,
we
build
the
messages
protocol
and
all
that
and
in
them,
and
then
sign
it
and
installers
go,
and
then,
when
that
is
ready,
we
can
actually
move
on
to
account
what
that
kind
of
like
approach,
half
half
would
be
not
half
half
of
a
day
lucky
and
steadily,
and
we
move
things
over
be
like
acceptable.
It.
G
Depends
have
been
union
issue
want
to
surface
everything
like
anybody
want
to
get
I
mean.
You
know
it's
difficult
to
figure
it
out
how
it
would
work
the
distraction
speaking.
You
know
that
would
be
making
a
fairly
big
changes
to
say.
There's
no
code
base,
something
that
you
know
doesn't
seem
like.
We
might
want
to
do
it
like
that's
just
it's
more
about
you
know
they
have
got
this
library.
Ii
need
my
surface
decryption
message,
but
then
I
have
to
send
it
through
to
pass
it
back
and
go
because
we're
using
whisper
white
boy.
G
A
Yeah
yeah
I
mean
probably
a
bit
hard
to
talk
about
that
because
I
just
don't
know
what
are
the
the
challenges
with
that
and
I
think
we're
gonna
find
out
with
the
shame
exactly.
Oh,
oh
he's
are
hard.
It
is
in
the
first
place
to
communicate
between
the
to
the
end.
For
me,
like
that's
the
first
step
before
you've
been
thinking
about
that
both
those
things
so
I
know
so
I
suggest
we
go
ahead
with
the
chambers,
shame
and
then
based
on
that
and
what
we
learn.
We
can
think
more
about
above
that
stuff.
G
B
A
H
D
Mean
so
what
we
need
is
basically,
we
need
some
something
that
we
use
this
source
of
truth
ordained
active
your
system
for
attention,
there's
topic
on,
discuss
the
process.
What
else
our
building
or
Jacob,
birth
and
others
have
been
working
on?
I,
don't
think
we're
gonna
in
terms
of
messaging
we're
not
gonna
get
much
better
than
you
need
whisper
peers.
The
main
thing
is
ensuring
that
they
are
unique,
which
it
should
be
and
then
getting
rid
of
the
test
traffic
and
so
on,
to
accept
it's
possible
one
specific
detail,
data.
D
We
have
to
figure
out
this
when
it
comes
to
end-to-end
testing,
because
it's
not
clear
what
the
impact
of
them
are
and
if
we
remove
them,
for
example,
by
changing
statuses
fleet
that
might
have
an
impact
on
Q
way
in
the
core
apps,
so
that
something
that
would
be
good
to
have
a
decision
on
if
we
are
fine
moving
at
the
static
plate
or
if
there's
some
other
way,
we
can
solve
that.
Yes,.
D
H
Some
feedback
on
changing
the
fleet
that
we
use
for
end-to-end
tests
because
a
testimony
said
we
want
to
use
exactly
what
isn't
probably.
But
the
thing
is
that's
the
point
of
the
staging,
for
occasionally
it
is
what
prod
will
use
before
it
uses
it
right.
So,
unless
you
consciously
agus
change
it
to
something
newer
and
yeah,
it's
digitally
pretty
much
always
the
same
thing
as
as
product,
but
they
understand
the
reservation,
because
it
is
more
practical
to
just
test
on
the
production
fleet
which
is
used
by
everyone
else.
A
E
H
You
have
to
have
essentially
a
set
of
data
for
every
day
or
every
time,
so
it's
really
that
you're
calculating
it's
not
always
day.
Sometimes
you
do
two
months
right,
so
you
have
to
have
several
indices.
That
would
hold
the
data
about
the
peers
used
by
end-to-end
tests
and
what
every
query
peers
from
the
logs
of
prod
fleet,
but
also
have
to
subtract
the
peers
for
every
single
time,
slice
or
they've.
Given
query
from
the
list
of
peers
use,
purity
is
used
by
the
end-to-end
tests.
That's
definitely
doable.
Keep
an
Asda
is
right.
H
D
F
G
Need
to
do
be
a
bit
more
careful
with
the
processor,
so
thank
you.
Another
good
process
is,
like
you
know,
like
I,
have
a
trade
staging
and
until
this
out
staging
will
stay
the
same,
so
you
don't
want
to
run
the
arse
of
an
unrelated
code
against
aging
at
that
point
right
because
they
might
not
have
necessarily
upgraded
version
of
stasis
could
be
placed
lazy.
F
H
The
alternative
is
to
essentially
modify
status,
go
logs
to
also
include
the
names
of
peers
and
filter
that
in
Gnostic
search
and
then
use
that
in
the
queries
to
limit
which
ones.
But
then
you
have
to
indicate
which
ones
are
end
to
end
bells
for
for
the,
and
that
is
not
indicated
by
the
name
of
the
node,
because
that's
always
sad
as
I
am
for
all
mobile
nodes,
so
that
essentially
build
the
Castros
capable
version
with
a
different
name
or
the
modified
version
to
detect
and
twinned
nodes.
H
H
H
D
D
Is
that
right
now
we're
looking
at
a
THAAD
and
then
it's
checking
what
is
it
among
processing
requests,
so
any
initial
notice
processing
request
and
then
it's
doing
a
unique
on
the
PID
and
that's
what's
showing
up
as
day-day
you
and
right
now,
that's
around
at
around
4,000,
which
seems
to
be
high,
but
maybe
that's
all
accounted
for
when
it
comes
to
end-to-end
tests
and
so
on.
But
do
people
have
any
other
reasons
to
doubt
the
accuracy
of
that
data.
D
What
we
knew
we
do
know
is
that
there's
fifty
concurrent
connections,
ish
so
I,
don't
know
people
have
any
thoughts
on
if
that
seems
reasonable,
to
have
four
thousand
active
users
a
day
with
50
concurrent
connections
or
give
them
that
the
traffic
they
see
or
downloads
or
anything
else
right.
It
seems
high
to
me,
but
maybe
that's.
C
H
Right
now,
it's
more
like
eighty,
and
a
hundred
did
you
like
connected
peers,
are
add
the
thirty
second
slice
at
the
specific
second
that
the
metric
is
pulled.
Does
the
connect,
like
the
kind
of
peers
and
mobile
nodes,
go
up
and
down
all
the
time
right,
so
that
count
itself
is
not
useful
in
terms
of
knowing
how
many
people
actually
have
been
using
the
app
within,
for
example,
an
hour
slice
just
know
that
at
the
moment
these
many
devices
are
connected
to
the
human
mail
server.
H
D
B
H
D
H
Yeah
well,
we
definitely
want
to
exclude
end-to-end
test,
because
this,
the
impact
of
those
might
be
actually
quite
big,
because
I
assume
every
end-to-end
test
is
a
separate
installation
of
the
separate.
It's
such
an
idea,
which
gives
you
a
new
in
note,
so
that
probably
would
be
no
object,
but
I
thought,
maybe
maybe
because
we.
H
Oh,
you
mean
two
devices
that
connect
talk
to
another
okay
yeah.
Then.
Yes,
there
they
will
have
different
attorneys
and
they
would
be
counted
as
separate
so
yeah.
Each
each
test
would
be
two
notes
actually
potentially
yeah,
okay
yeah.
So
so
those
numbers
could
be
equal,
quite
skewed
tied
by
the
end
to
end
test
for
sure.
D
Cool
then
the
outer
metric,
so
at
the
end,
other
metric
is
sort
of
retention
or
or
stickiness
I
suggest
that
we
start
very
basic
with
Cygnus
mathematic,
which
is
just
de
da
you,
but
is
provided
by
Mau
before
going
into
returns.
You
cut
this
one
I
think
to
make
that
nice.
They
have
added
some
some
some
graphics
for
that
in
metrics,
on
the
material.
H
D
D
Well,
it
it's
it's
right
now,
it's
it's
not
so,
for
example,
there's
a
line
and
then
it
that
ends
like
three
weeks
ago
and
then
that
line
is
looking
back
a
month
ago.
So
it's
not
very,
it's
lagging
it's
not
very
actionable
and
it's
not
really
same
thing
for
da
you
it's
changing
per
month
and
it's
not
up
to
date
with
the
latest
date.
So
it's
just
not
as
actionable
oh,
not
as
nice
as
it
could
be.
It
does
have
to
be
pretty,
but
just
it
should
be
accurate.
D
C
Just
because
it
bugs
me
I
do
want
to
be
accurate
about
the
fact
that
we're
going
after
a
proxy
of
retention,
and
you
not
retention,
because
we're
not
comparing
individual
users
over
time
and
that
could
be
miss
misconstrued.
If
we
use
try
bit
as
retention,
and
it
also
think
that
the
data
actually
is
I.
D
Agree
in
a
point
that
to
our
efforts
that
we
have
to
do
so,
this
is
measuring
like
stickiness,
and
it's
not
the
proper
cohort
analysis.
Something
is
that
something
I
think
we
should
do,
but
first
we
need
to
get
the
base.
Exam
I
agree
with
that.
The
other
point
with
that
is
that
we
need
to
have
clear
documentation,
though,
for
ourselves,
but
also
for
marketing
and
fundraising
and
performance
marketing
and
so
on.
D
H
I,
don't
think
this
is
doable
elasticsearch
by
itself
or
not
in
the
format
that
it
has
right
now.
So
we
have
to
think
of
a
different
way
of
storing
the
data
about
peers
that
connect
to
us
to
query
it
properly
or
even
use
a
different
database
core
for
a
metrics
like
in
index
DB
or
whatever
else
is
there.
Are
that
because
the
way
it
is
stored
right
now
is
just
not
easily
cuerpo,
so
the
problem
is
it
isn't
just?
We
need
a
nice
way
to
query
it.
H
D
D
F
A
C
H
C
Yeah,
it
would
be
so
what
one
thing
this
is
probably
like.
A
critical
flaw
for
me
to
understand
is
peer
connectivity
say
if
someone
install
status
on
boards,
but
never
sends
a
message
or
joins
a
public
chat,
would
they
not
be
counted
at
all
or
are
they
still
a
note
in,
let's
say
the
peer
IDs
that
we
are
keeping
those.
H
C
H
Don't
we
get
a
question
too
car?
If,
if
this
the
UPS
is
started
and
no
chat
is
open,
no
public,
no
one-to-one
chat.
No,
nothing
and
no
options
in
the
chat
are
done,
those
the
notes
start
and
if
it
does
doesn't
do
any
like
generic
startup
requests
or
those
no
because
if
it
doesn't
make
no,
it
makes
no
requests
but
just
connects.
Then
it
probably
wouldn't
show
up
in
the
statistics,
because
we
look
at
specifically
a
a
local
message
that
says
something
like
process
processing
requests.
H
B
D
This
is
all
black
box
yeah,
it's
all
black
box,
any
anyone
running
a
node
could
in
theory,
do
this.
The
main
difference
is
that
we're
running
cluster,
so
you
we
are
more
likely
to
get
the
better
view.
But
in
theory,
if
someone
is
connected
to
node
not
connected
your
cluster,
then
they
would
be
able
to
get
the
same
kind
of
metrics.
So.
H
D
H
A
A
F
A
F
E
E
A
A
E
There
was
also
zip
your
lips
and
such
and
payment
channels,
with
payment
channel
have
too
much
of
I'm
boring
cost
and
it
mobilizes
capital.
So
it
wasn't
that
good
yeah
and
it's
it's
going
in
the
direction
of
optimistic
products,
because
there
is
more
chances
that
it's
ready
to
use
in
the
shorter
term.
F
D
E
It
depends
if
you,
if
you
consider
that
what
will
bring
user
retention
first
is
chat
or
the
side
features
ready
to
the
wallet.
So
if
you,
if
the
wallet,
has
nothing
to
do
with
user
retention
and
it
it
won't
help,
but,
on
the
other
hand,
for
faces
I'd
own
personal
experience,
I've
stopped
using
the
kudos
that
that,
for
instance,
because
I'm
too
lazy
to
refill
my
my
gas
on
my
account.
E
E
It
would
be
super
easy
to
do
in
in
the
very
short
term,
and-
and
there
is
no
uncertainty
about
whether
it
would
succeed
on
it,
and
then
there
is
what
was
the
the
other
one
sn2
reaction.
Well,
the
first
step
would
be
to
have
emoji
reactions
before
before.
It's
answer,
reactions
and
both
are
like
much
shorter
term
than
all
the
whatever
in
certainties.
We
have
with
using
a
side
chain,
a
layer,
2
solution
to
make
transactions
cheaper
and
faster.
C
Yeah
I
mean
I,
think
that
makes
sense.
It's
not
funny.
We
already
consider
like
a
layer,
2
solution,
virgins
for
efficiency
sake.
If
the
key
car
team
is
working
on
it,
it
helps
to
keep
track
of
the
solution,
they're
choosing
to
understand
if
it
can
be
used
for
set
as
mobile
and
yeah.
There
might
be
other
solutions
to
kind
of
to
having
to
pay
for
a
user
name
which
could
definitely
be
a
blocker,
because
it's
such
a
j19
feature,
I
yeah
I,
think
you
would
make
a
good
point.
C
That
is
the
trade
off
between
SNT
utility
and
retention.
I,
don't
want
to
I,
don't
think
we
want
to
reduce
SNT
utility
any
more
than
we
have
by
yeah
kind
of
nullifying
to
work.
That
was
done
on
tribute
to
talk
so
I
I.
Don't
really
see
it
as
an
option
to
remove
SNT
utility
from
from
to
username,
also
because
of
the
uniqueness
study.
What.
E
H
E
Yeah
yeah
yeah.
That
would
be
a
potential,
so
so
it
wouldn't
replace
the
three
names
that
could
be
a
solution
like
if
the
user
doesn't
have
any
NS
name.
You
still
see
the
three
random
name
plus
the
name
they
want
to
be
called
with
or
whatever,
but
just
to
go
back
to
like
more
features
for
for
user
retention.
E
So
you
mentioned
the
essential
action
and
and
should
be
to
took
and
for
those
I
think
that
they
won't
bring
any
user
retention
if
they
are
done
with
the
main
net,
high
cost
and
and
and
transactions,
because,
like
we
had
tribute
to
talk
until
we
switch
to
multi
account,
and
it
was
quite
annoying
that
the
way
the
feature
works
you
you
cannot
talk
until
your
transaction
is
done.
So
first,
you
have
to
open
a
chat
to
the
transaction,
and
now
you
add
to
that
the
fact
that
you
need
to
ask
what
address
first.
E
Well,
not
if
it's
any
honest
name
but
anyway,
there
is
that
and
for
a
century
action,
it's
it's
for
something
as
simple
as
making
a
reaction,
you
would
hope
for
ease
of
use
not
having
to
do
a
transaction
and
then
make
sure
it
works
and
so
on,
and
also
if
it
about
sending
one
incentive
as
a
reaction,
can
you
imagine
sending
one
SNT
and
being
the
equivalent
of
20
SMT
just
for
the
gastrin
transaction?
So
it's.
D
So
in
terms
of
the
written
top,
it
would
lay
it
to
and
in
core
and
so
on,
there's
three
things:
I
would
probably
do
before
going
further
with
that.
One
is
in
terms
of
making
doing
due
diligence
and
it
seems,
like
that's,
been
done
the
artisan
thoroughly,
but
also
making
sure
that
there's
like
secured
audits
and
all
these
kinds
of
things
which
has
soomi
something
at
the
key
Conti.
We
would
look
into
the
second
thing.
D
I
would
look
at
it
in
terms
of
understanding
how
big
of
a
bottleneck
like
gas
prices
are,
if
it's
temperature
ramen
or
if
it's
something
that
will
keep
going,
we
have
reasonably
will
keep
them
for
longer
period
of
time
and
the
farthest
I
would
look
at
the
specific
use.
Demographics
we're
talking
about,
because
I
wouldn't
for
me
the
difference
between
having
no
crypto
and
having
some
creep.
So
it's
the
big
one.
D
I'm,
not
sure
if
we're
talking
about
Latin
America
you'll
be
useful
to
have
some
backup
theory
for
why
this
would
matter
in
terms
of
maybe
our
users,
the
demographic
we're
targeting
with
our
campaigns
and
so
on
or
users
where
are
more
price
sensitive,
or
this
will
make
a
big
difference.
If
that's
the
case,
then
that
would
make
a
stronger
argument
for
reducing
gas
costs.
What
do
they
do?
E
Mean
no
I
think
the
the
status
pay
team
anyway
is
going
on
their
own
direction.
They
they
have
a
partnership
with
leapt
out
and
the
decision
to
go
with
optimistic
herbs
was
made
this
morning
in
Nepal
and
they
will
and
I
think
most
of
the
work
will
be
done
by
lip
tau,
which
will
provide,
which
it
will
end
out
prototype,
environment
or
or
the
keycard
seem
to
to
play
with
and
see
if
they
can
make
everything
work.
E
So
from
the
core
perspective,
it
was
more
of
an
interesting
what
solution
they
are
going
to
use
to
see
if
we
can
reuse
for
for
features
that
could
improve.
User
retention
such
like
Esther,
mentioned
the
sn2
reactions
and
an
tribute
to
topic
in
particular,
because
instance
of
that
transactions
I
think,
like
Oscar
said
it
would
be
need
to
be
very
fine.
I
think
are
important.
A
F
A
E
I
think
that's
that's
why
they
chose
opportunistic
growth
because,
like
the
key
roll-ups,
if
you
listen
to
Alex
the
developer
for
the
casing,
it
was,
it
would
seem
super
nice.
Everything
was
possible
and
all
but
I
guess
fear
is
that
it's
not
as
shiny
as
it
sounds,
and
two
mystic
roll-ups
are
simple:
simpler
mathematically,
yeah.
I
I
think
it's
yes
worth
to,
especially
if
we
don't
have
really
feel
pressure
on
implementing
a
payment
solution.
I
think
it's
worth
to
kind
of
wait
and
see
a
little
bit,
especially
in
optimistic
roll
ups.
If
you
want
to
use
it
reasoning
is
I've.
I've
read
some
posts
that
are
still
kind
of
questioned
in
the
security
model
and
I
would
rather
not
bet
on
something
which
ends
up
being
a
second
plasma.
A
A
E
I
Also
get
to
get
the
part
about
like
not
having
to
far-fetched
like
models
in
mind
here,
but
the
the
thing
is
like
if
I
look
at
what
happened
in
plasma.
If
someone
invested
some
level
of
resources
into
this,
they
would
be
wasted
like
looking
at
it
from
from
today
and
I.
Think
it's
especially
given
that
we
want
to
work
on
increasingly
user
numbers.
I
would
just
go
for
okay.
We
have
something
better
to
do
and
cannot
selects
it
sit
back
a
little
and
wait
to
see
if
the
project
actually
much
worse
or
if
they
yep.
E
A
A
A
D
A
Right
so
some
part
of
it
I,
guess,
okay,
so
it
says
specs
reviews,
two
specs
and
and
then
there's
the
expand
exchange.
The
proposals
which
includes
team
bus,
Waku
version
to
your
feedback
on
that
and
then
latest
solutions
week.
We
kind
of
discussed
that
already-
and
there
was
something
else
on
about
the
notifications,
so
I
mean
the
specs.
First
of
all,
there
was
this
Audi
one
and
I.
D
H
C
G
A
E
G
Love
myself,
but
I
made
a
change.
Sir
there's
always
the
issue.
You
know
the
main
issue
with
this
fix
is
pub,
but
you
know
spam
is
not
undressed
by
the
main
app
and
it
won't
be
addressed
by
by
the
push
notification
service.
So
you
know
essentially
like
any
spam
prevention
magnet
would
be
very
bland.
Let's
go.
A
A
A
All
right
cool,
then,
then:
okay,
the
other
one,
is
package
changing
proposals.
So
symbols
there's
that
issue,
which
is
the
ashamed,
so
we
partially
already
discussed
this
early
in
the
call.
A
lot
for
everyone
has
a
chance
to
look
at
the
at
the
issue
that
proposes
how
to
go
about
this,
which
is
essentially
to
implement
to
the
the
shame-
and
it
has
some
details
of
all
this
could
be
accomplished.
Are
there
like
any
comments
on
this
or
I?
Don't
know
like
objections,
suggestions,
I.
G
Mean
you
know
really
said
that
I
think
it's
worth
taking
into
position,
because
we
are
using
the
exactly
the
opposite
method
that
pandro
used
so
regime
in
stuff
be
nothing,
and
so
at
least
you
know,
I
think
it's
worth
taking
into
position.
What
page
was
done
and
explain
why
we're
not
following
that
path
for
support.
G
A
A
Bottom
right,
I
think
I
think,
like
the
would
I
think
that's
like
a
potential
valid
approach.
I
think
I
think
was
discussing
the
call
hour
or
at
least
I,
remember,
Jessica,
saying
something
about
that:
it's
not
a
sensor.
We
don't
necessarily
need
to
go
like
we
don't
necessarily
to
exclude
that
although
it'd
be
a
bit
weird
I
guess,
but
we
can
know
it's
it's
possible
still
to
go
with
that
approach.
Even
with
the
shim.
G
A
A
Mean
that's
would
be
the
Waku
that
this
this
just
impose
just
to
clarify
like
so.
Everyone
is
in
the
same
page,
so
there's
the
same
bus
channel
that
you
can
follow
the
updates
on
on
sting
bus,
there's
a
call
tomorrow
at
8
a.m.
Eastern
Time,
and
this
call
is
it's
an
iteration
meaning,
so
people
are
kind
of
going
to
be
developing,
are
gonna,
be
induct
and
that
call
and
any
like
relevant
stakeholders.
A
A
D
A
F
D
So
I
mean
the
devaki
one
is
very
well
defined.
Obviously,
if
there
are
specific
things
that
we
want
to
change,
you
can
create
issues
and
so
on,
and
we
can
iterate
on
that.
That
way,
in
terms
of
that
could
be
I.
Think
initially
they
did.
The
target
is
to
port
it.
You
need
to
sort
of
Liberty
B,
and
that
will
look.
D
It's
simply
the
same
initially
with
some
changes,
because
it's
running
on
the
PTP
and
the
pub/sub
interface
is
different,
but
yeah
I
mean
that
will
be
an
issue
and
other
people
can
comment
on
that
design
and
so
on.
You
can
also
do
that
in
discussed,
ready,
but
a
specific
drops,
PR
prospects
will
probably
not
come
until
until
next
week.
D
A
Right
sounds
good,
then,
all
right
next
topic,
where
they
discussed
I,
believe
with
the
latest
solutions
that
will
rob
gas
gas
cost
barrier,
for
instance
esnt
transactions.
That
was
already
discussed.
Am
I
right
or
or
is
this
something
else,
all
right,
okay,
cool
and
then
finally,
notifications
on
iOS
progress
decisions
and
decisions
that
have
been
made
so
who
adopt
it
on
this?
Is
it
Andrea
I.
G
C
Yeah
for
context
reason,
I
put
it
on
the
agenda
was
and
up
to
you
to
what
extent
you
and
I
discuss
it.
I
really
don't
know,
but
I
know
there
was
a
long
discussed
threat
with
different
options
upon
which
there
was
a
conclusion
and
spec
and
implementation
was
based
on
that.
So
my
thinking
was
yes,
it's
helpful
for
everyone
who
did
not
follow
closely
to
understand
what
the
current
status
is
and
if
any
decisions,
one
name.
G
G
G
A
F
Hey
yeah
I
have
one
thing:
it's
actually
quick
enough
like
criterium
to
there
was
a
shared
tested
launched
right
now
with
four
other
client
and
Nimbus
participated
successfully
were
part
of
the
sort
of
Altona
Genesis
launch
and
we
have
a
whole
bunch
of
valadares
running
up
on
the
network.
So
big,
congratulations
to
the
entire
Nimbus
team.
They've
been
a
great
work.
They
were
making
all
weekend
to
get
this
thing
up
and
running,
and
it
worked
very
nice.