►
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
Hello,
everybody
and
welcome
to
the
team
growth
and
ich
weekly
status
meeting
today
is
Tuesday
September,
the
19th
okay.
So
this
week
we're
just
going
to
I
guess:
do
a
straightforward
status
update
so
I'll
go
around
and
just
we
will
talk
about
what
what's
been
achieved
over
the
last
week
so
and
Alan.
Can
you
can
you
give
us
an
update?
Please.
B
A
B
This
week,
I've
been
working
on
the
Dow
four
o'clock,
and
that
was
work
that
Adam,
left
and
I
finished
that
hey,
it's
all
ready
for
ready
for
review
and
and
I
Lucas
has
left
some
comments
there.
So
I
think
it's
in
good
shape,
so
I'm
hoping
to
get
that
merge
soon.
That
functionality
allows
us
to
process
that
our
four
o'clock
and
10:00
after
that
one
and
also
includes
the
mining
configuration
in
order
to
find
the
dogs
with
the
extra
header
and
stuff,
and
so
ok,
that's
it
for
me
all.
A
B
I've
run
three
kind
of
tests.
The
first
one
I
tried
to
connect
to
helium
network
and
a
target
in
the
fourth
block,
and
it
worked
also
I
created
unit
tests,
as
you
said,
and
last
I
run
the
test
that
a
rather
can
Conrad
have
been
working
on
the
ones
that
the
officiality
tests
they
ran.
Okay,
so
okay
related
to
transition
from
homestead
to
the
dog
park
and
they
were
okay.
I
was
a
little
bit
blocked
because
there
is
an
issue
on
the
description.
B
The
description
says
something,
but
it's
not
quite
accurate,
but
I
was
able
to
fix
it
locally.
It's
not
related
to
our
code
base,
but
to
the
tests
that
are
published
on
Athenian
repo,
maybe
I.
We
can
create
that
I
could
request
there
and
but
it's
just
a
description
issue
and
it
worked
just
fine.
Okay,.
A
All
right,
I
suppose
no
harm
in
mentioning
it
again.
So
because,
obviously,
that's
that's
very
good
news
that
that
particular
book
is
hopefully
sore
that
we
haven't
seen
it
since
all
right.
Thanks
on
Mukesh
welcome
back,
you
came
in
at
the
end
of
at
the
end
of
last
week.
So
what
if
he
would
up
to.
A
C
A
And
sometimes
I
think
lady
look
is
definitely
smiling
on
us
because
the
the
the
fix
was
literally
just
an
initialization
of
a
variable
right.
Yes,
exactly.
D
Don't
know
if
I
under
through
all
all
the
earth
yeah
there.
D
A
D
E
E
E
Yes,
I
mean
mostly
by
taking
it
and
checking
also
spotted
that
it
was
a
similar
rounding
error
with
between
the
competitor
that
made
our
client
is
incompatible.
Get
one
so
I
mean
also
looking
into
how
the
calculations
had
to
properly
so
as
to
be
compatible
with
with
the
gift
grant,
which
is
what
which
we
finally
mystical
to
pass.
Both
gate
and
party
are
incompatible
right.
A
Yeah
so
I
guess
just
as
an
overview.
They
I
mean
it's
interesting,
that
the
rounding
errors
and
stop
me
if
I'm
wrong
here
with
the
rounding
errors
are
absolutely
are
absolutely
tiny
and
probably
wouldn't
make
any
difference
in
in
an
accounting
package,
for
example,
but
of
course
the
the
values
that
they
produce
go
into
the
going
to
the
hash,
and
so
the
hashes
end
up
differently
end
up
being
different,
and
if
the
hashes
are
different,
then
we
have
a
chain
slit.
A
A
The
rounding
errors
are
caused.
I
know
we
had
a
little
discussion
about
this
earlier.
The
rounding
errors
are
caused,
basically
by
more
or
less
when
you
decide
to
do
your
your
division,
so
actually
that
thanks,
Nico
I'm
gonna
ask
her
I'll
pass
that
one
on
product,
because
he
actually
wrote
that
little
bit
of
code.
That
was
the
that
does
the
reward
calculation
and
Radek
p.m.
to
calculate
the
the
rounding
error
is
basically
introduced,
as
a
result
of
where
you
actually
do
trigger
the
division.
Yes,.
F
F
F
C
F
Of
division,
of
course
we
be
lost,
we
can
still
run
the
cameras
and
so
I'm
actually
going
to
make
an
issue
on
on
cap
repository
Steve,
whether
they're
interested
a
lot.
But
anyway,
we
will
have
to
achieve
compatibility
which
is
easy
to
do,
but
don't
try
to
convince
those
guys
to
follow
our
formulas.
Yeah.
A
Yeah
I
think,
as
we've
seen
earlier,
those
guys
they're
very
interested
in
that
in
that
in
that
level
of
detail,
so
might
be
something
that
really
appeals
them.
So
yeah,
let's
see,
let's
see
how
that
goes.
Okay,
so
that's
the
that
was
that
error
erratic
you
you've
also
been
you've
also
been
working
on
a
refactor.
Yes,.
F
So
it's
a
real
factor
of
how
we
do
regular
sync
and
actually
it's
moving
the
responsibility
of
including
blocks
into
option
away
from
the
network.
The
factors
it
into
the
ledger
and
the
part
of
executable
actions
and
blocks.
And
so
the
idea
here
is
that
we
should
be
able
to
just
throw
any
boost
Abbot's
and
see
to
resolve
any
Forks
and
branch
happens.
F
Primary
motivation
for
this
one's
to
be
able
to
run
and
approaching
texts
from
the
past
with
because
of
those
tests
have
parallel
chains.
We
didn't
move
in
the
box
that
they
that
they
require
we
executed.
So
we
have
to.
We
have
to
surpass
simple
entry
point
for
those
blocks,
which
would
be
practically
all
after
the
execution
stole.
F
So
we
had
that
that
work
is
going
already
shown
that,
with
the
changes
we
are
able
to
sync
at
least
some
initial
portion
of
the
blocks.
I
believe
it
was
one
of
three
thousand
blocks.
Those
able
to
sync
I
mean
I
just
thought
at
that
time,
and
also
many
of
the
of
that
in
test
I
mean
around
30
tests
that
we
previously
have
had
to
had
to
skip,
because
we
were
able
to
support
them.
I
know
as
a
kid
incorrectly.
F
F
And
also
I
think
I
may
not
who's.
Who
is
missing
today,
so
recognizing
those
boxing
as
this
was
this
past,
but
I
was
closely
supervising
that
work
and
I
think
it's
safe
to
say
that
the
very
close
match
that
thanks
and
then
I
can
continue
integrating
that
with
factoring
with
those
tests,
and
so
those
tests
are
animation
has
proven
to
be
useful
for
testing
the
drought.
A
A
Okay,
very
good
thanks,
tarick,
all
right,
so
just
I,
guess
in
more
general
terms,
the
the
that
work
that
we
have
there
is
is
is
the
existing
ETH
support
so
not
including
new
Forks
that
are
not
including
new
releases.
New
AI
peas
that
are
just
to
be
just
about
to
be
supported.
The
first
half
of
Metropolis
is
coming
out
soon.
That's
not
what
we're
talking
about.
A
We
have
done
some
support
for
the
existing
ETH
chain,
so
we're
trying
to
finish
that
up
and
we've
also
done
that
refactoring
to
better
support
the
tests,
and
also
we
fixed
a
few
things
that
we
basically
I
think
we
fixed
almost
everything
that
we
found
in
our
inner
beta
tests
and
we've
gone
through
our
backlog
and
cover
up
to
date,
so
we're
in
reasonably
good
shape
in
that
regard,
but
for
the
Daedalus
release.
Obviously,
we
need
integration
with
the
with
the
wallet
and
that
is
still
completely
outstanding,
so
yeah.
A
We
just
need
support
from
from
that
team
to
get
that
done,
and
then
we
have
the
other
major
part
of
that
is
installer,
which
is
also
really
out
of
our
hands.
So
we're
going
to
be
bringing
I
guess
we're
going
to
be
starting
to
test
cycle
reasonably
soon
and
hopefully
we'll
get
that
we'll
have
the
UI
business
wallet,
integration,
dy
integration,
Don
as
well,
so
yeah,
that's
a
little
bit
fuzzy
on
the
day
as
of
as
of
now.
Just
because
of
that,
okay,
I.