►
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
welcome
to
the
team
growth.
Antique
weekly
status
meeting
today
is
Tuesday
the
18th
of
July,
so
it's
all
about
beta
again
this
week
and
trying
to
try
to
get
ourselves
ready
for
a
beta
release.
Last
week
we
spoke
about
the
two
things
that
were
outstanding
were
the
two
major
bits
of
functionality
that
were
outstanding
and
we
were
hoping
to
have
I
guess
code
freeze
by
this
week,
but
before
we
talk
about
that,
let's
just
go
through
and
talk
about
what
people
have
been
doing.
A
B
B
A
C
B
Yes,
this
one,
you
can
see
my
terminal,
we
are
currently
at
block
1
million,
seven
hundred
seventeen
thousand
and
as
I
checked
in
parity,
and
this
latest
block
is
101
million
nine
hundred
thousand.
So
we
are
not
far
away
from
the
latest
block
and
besides
each
I
mentioned
sync
is
going
well
and
says
that
I
was
also
working
on
adding
configuration
for
the
IP
155
and
for
optimization
of
transaction
execution.
When
preparing.
B
A
A
Cool,
so
that
will
be
one
more
tick
box
for
our
preparation
will
have
will
have
completely
synced.
The
will
have
completely
synced
the
test
net
with
our
client.
So
we'll
have
the
configuration
ready
to
go
and
we'll
know
what
works.
Are
you
having
issues
with
with
finding
peers
for
the
test
net
or
how
is
that
going?
Okay,
okay,
yeah.
B
A
A
Right,
okay,
great
speaking
of
peers
and
network
discovery,
is
our
attempt
to
try
and
ping
our
periods
and
find
their
neighbors
and
basically
create
a
list
of
peers
that
have
successfully
hand
shaped
now.
Last
week
we
were,
we
were
talking
about
getting
this
merged
really
soon.
So
it's
not
it's
not
actually
merged.
As
of
yet
Mukesh
kini.
What
can
you
tell
us
about
it?
How's
it
going.
D
A
Okay,
cool
yeah,
so
just
to
recap,
I
mean
that
was
a
little
bit
of
a
surprise
to
us.
We
thought
that
I
mean
I
was
certainly
under
the
impression
that
we'd
have
we'd
have
peers
all
around
us
and
we'd
feel
the
love
and
everything
we
thought
would
would
immediately
operate
more
smoothly.
But,
to
our
surprise,
we
found
there
are
lots
and
lots
of
lots
of
peers
who,
for
some
reason
or
other,
are
just
not
interested
in
our
connection,
so
mostly
mostly
sometimes
just
they
actually
disconnected
at
different
stages
in
the
process.
That's
right!
Yes!
A
D
A
D
A
D
A
Yeah,
which
that's
as
we
said,
that's
why
we
we
sort
of
stopped
and
started
to
investigate
that
a
bit
further
and-
and
but
you
know,
we've
got
a
solution
now
we're
able
to
get
a
list
of
peers
that
we
can
connect
it.
Okay,
so
we're
looking
at
integrating
that
and
sometime
this
week,
post
post
unit,
testing
integration,
testing,
okay,
thanks
because.
C
C
C
The
basic
stuff
is
just
adjusting
parameters
like
chain
and
in
the
bootstrap
nodes,
cycling
and
difficulty
bump,
delayed
policy.
So
simple
things
like
that
that
we
already
have
well
configurable
and
it's
just
a
matter
of
turning
the
switch
of
us
I,
still
have
to
have
to
confirm
that
it
works
by
at
least
starting
some
sync,
with
with
th
notes
and
I'm
still
working
with
that.
Okay.
A
A
So
that's
working
out
one
thing:
I
skipped
actually
was
going
back
to
the
current
ATC
effort,
is
the
pruning.
So
again,
pruning
is,
is
I,
suppose
a
delicate
operation
in
that
it
absolutely
has
to
be
done
right
or
nothing
will
work
so
Allen.
Can
you
give
us
an
update
on
where
we're
at
with
that?
Yes,.
E
Basically,
we
were
focused
on
MPT,
no
MPD
nodes
that
are
not
longer
than
needed.
So
this
week
we
have
deployed
operation,
actually
two
versions
to
the
to
our
staging
environments,
and
let
me
share
my
screen.
So
I
can
show
you
we
do
some
data.
So
can
you
see
my
screen
right?
Yep,
okay,
so
here
I
have
two
thumbs
in
the
first,
this
one,
the
first
one
is
the
pruning
known.
E
As
you
can
see,
we
are
a
little
bit
closer
about
a
hundred
thousand
block
and
let
me
share
with
you
the
size
of
the
database,
which
is
to
dig
up
almost
or
a
little
bit
more,
and
this
is
our
number
in
now
which
is
close
to
the
same
block
number
and
if
I
share
with
you,
the
size
is
11
years
and
the
nulls
are
still
in
sync.
So
let
me
try
well
now
we
have
a
check.
E
So
now
it's
trying
to
download,
for
example,
here
it's
executing
transaction
and
I-
have
a
graph
to
share
with
you.
Oh,
this
is
the
evolution
of
the
data
rate,
sighs
and
I'm
to
blog,
let's
say
300,000.
This
is
their
kite
mode,
and
this
is
the
premium
Wow.
So,
as
you
can
see,
for
example,
for
blog
300,000,
we
are
less
than,
and
we
are
really
really
far
from
the
values
that
we
are
here,
that
it's
almost
2.5
Jigga's.
E
So
it
seems
that
bringing
in
its
successful
at
least
this
basic
pruning,
we
were
only
focus
on
science
benchmarks.
We
weren't
targeting
speed,
for
example
at
this
time,
and
and
we
are
in
the
process
of
merging
all
the
branches
and
creating
tests,
and
the
pull
request
will
be
ready
for
our
review
process
very
soon.
I
guess.
A
A
I,
guess
is
because
we
have
the
two
instances
running
side
by
side
on
very
similar
hardware.
At
the
very
same
time
we'll
be
able
to
see
if
the
archived
one
you
know
pulls
ahead
of
the
pruning
one
by
any
significant
number
of
blocks.
So
that'll
give
us
a
rough
measurement
of
the
speed
comparison,
but
I,
don't
think
there's
any
cause
for
concern
as
of
yet
right
now
and.
E
A
E
A
Okay,
so,
given
all
of
that
and
the
week
that
we've
had
we're,
probably
I
mean,
maybe
it
was
a
tiny
bit
ambitious
to
expect
us
to
to
be
talking
about
code
freezing
and
bugs
only
as
of
today,
today
being
the
18th.
So
what
we're
gonna
have
to
do
is
push
that
back
by
one
week.
I
think
we're
we've
pretty
much
decided
that
we
can
get
those
POS
in
over
this
week,
including
review
and
then
we'll
be
talking
about
bug
fixing
only
for
the
following
two
weeks,
which
means
we'll
release
a
beta
I.
A
So
then
we
kind
of
expect
the
next
one,
as
this
has
not
been
fully
decided
yet
I
mean
only
the
only
the
first
release
has
has
been
decided,
but
we
can't
expect
the
next
release
then
to
probably
support
ETH,
but
that
remains
to
be
seen.
Maybe
we'll
find
a
lot
of
our
initial
estimates
suggest
that
that's
possible,
but
maybe
we'll
find
a
lot
of
issues
as
we
go
as
we
go
through
the
test
cycle.
A
Ok,
so
then,
just
to
recap-
and
this
week
we're
going
to
try
and
merge
both
of
those
those
features
post
pass
will
have
two
weeks
of
tests.
In
the
meantime,
the
team
will
be
moving
on
to
do
et
hard
for
Cory
ths,
recalling
it
and
the
other.
Only
other
thing
that's
going
to
happen
is
we
will
we
will
just
as
a
as
an
initial
smoke
test.