►
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
Last
week
we
were
speaking
about
trying
to
complete
a
couple
of
miles
milestones.
We
were
trying
to
get
our
mining
integration
going
on
and
also
we
were
looking
at,
missed
integration
and
Adam
you've
been
doing
some
testing
with
me,
see
two
instances
and
some
some
different
configurations
of
mining.
Yes,.
B
So
we
set
up
10,
ec2
nodes
and
configured
our
client
there
to
start
some
private
network
mining.
We
were
using
ETH
miner
for
Mac
for
mining
and
test
was
like
first
start
the
notes.
Let
them
operate
separately,
to
create
some
branches
and
then
connect
them
together
into
one
network
to
check
if
they
will
resolve
conflicts
correctly
and
continue
mining
and
after
some
time
we
then
connected
it
to
fresh,
go
et
Jim,
client
and
checked.
B
If
the
synchronization
between
fresh
note
joining
the
network
will
be
as
we
work
as
expected,
so
it
went
well,
but
we
have
some
issue
with
goiti
room
node,
which
means
that,
while
when
testing,
we
killed
it
for
a
second
to
test,
if
it
kept,
it
will
catch
up
F
and
it
didn't.
It
was
because
it
was
connected
only
to
one
node
and
it
turned
out
that
were
after
connecting
it
through
the
gate
console
to
other
nodes.
B
It
just
started
working
so
maybe
go
etherium
head
has
some
kind
of
protection
against
malicious
node
when
when
when
it
sees
that
train
on
a
given
node
is
too
far
ahead.
It
just
drops
the
blocks
received
from
that
node
and,
besides
that,
after
connecting
it
to
two
other
nodes
in
the
network,
it
just
a
continuously
continued
syncing
and
looks
like
we
are
good
to
go
to
with
mining.
We
also
tested
that
we
are
preparing
blocks
with
correct
OMERS
and
transactions.
A
Okay,
so
that
that
was
interesting
as
he
as
he
said
them
I
mean
we
don't
know
this
definitively
because
we
haven't,
we
haven't
done
that
level
of
checking,
but,
as
you
say
when
we,
when
we
added
more
nodes
into
it,
gets
just
took
off
again,
so
it
looks
like
it
was
sort
of
it
might
be
some
kind
of
security
feature
where
it
doesn't
want
to
synchronize
with
a
single
peer.
Yes,.
B
A
A
A
Cool
and
so
that
pretty
much
concludes
and
that
milestone,
which
is
excellent.
That's
that's
the
the
testing
done.
The
code
is
integrated,
so
we
have
that
sort
of
them.
So
that's
really
good
news
and
then
the
other
one
we
were
trying
to
close
thanks.
Adam
was
actually
just
before
we
leave
that
I'm
gonna
show
the
page.
A
A
So
we've
completed
that
as
well
I'm
delighted
to
say
that
miles.
Don't
behind
us.
We
have
a
little
bit
of
documentation
on
some
of
the
testing
that
was
done.
We
were
using
a
missed
integration
as
a
sort
of
a
as
a
way
of
checking
out
our
node
I
mean
obviously
we've
we've,
we've
done
all
our
unit
testing
and
we've
got
Waukesha's
app
to
exercise
the
API
as
well.
So
we've
got
quite
a
bit
of
coverage
there,
but
this
is
the
the
mist
integration
testing
report
that
I'm
currently
shown
now
and
Alan
ooh.
C
So,
just
to
add
some
more
info
and
what
what
do
you
have
just
said?
Besides
our
unit
tests
and
integration
tests,
I
mean
automatic,
admitted
ones
and
peer
review.
We
also
wanted
to
make
sure
that
our
PC
RPC
API
a
was
working
with
mist,
which
was
most
of
the
minds
own.
So
we
tested
exercised
our
API
against
using
list.
I
mean
mist
UI.
C
We
try
not
to
be
like
miss
testers,
but
just
wanted
to
make
sure
that
everything
worked
and
on
any
issue
we
found.
We
just
checked
that
with
other
trends
we
had
or
not
the
same
issue
and
most
of
the
you
I
mean
all
the
UI
works.
As
expected,
you
can
use
it
as
if
it
was
like
gas
or
parity
on
another
plane.
It
works
just
fine
and
we
found
if
you
scroll
down
and
on
please
or
maybe
I
can
share
my
screen.
If
you
want
to
yeah
it's
going
down,
okay,
we
found
it
there.
C
You
will
find
or
all
the
UI
tests
that
we
run.
There
are
not
automated
ones,
of
course,
and
we
haven't
changed
nice
source
code,
but
in
the
bottom
you
will
see
some
issues
that
were
here
then.
So
there
are
some
other
issues
that
we
found
that
we
are
also
present
equality
and
again
so
we
decided
not
to
continue
trying
to
chasing
them
and
they
are
probably
least
biased
or
something
like
that
so
and
we
were
quite
happy
because
we
were
able
to
use
the
wallet
us
any
other
know
so
I
think
that's
it.
A
A
That's
right!
It
has
been
implemented
without
any
major
problems.
There's
we
still
have
a
task
plans
to
test
it
with
integration
with
all
the
clients
get
parity.
However,
this
they
still
haven't
released
that
functionality
at
least
not
officially
yeah,
okay.
So
when,
when
that
comes
out,
then
we'll
do
our
integration
test
just
just
set
the
set
the
figures
so
that
we
don't
have
to
wait
till
the
actual
block
comes
around
and
make
sure
that
everything
just
rolls
over
as
we
expect.
A
Okay,
thanks
Eric,
and
so
that
is
I,
guess
the
two
milestones,
which
is
a
pretty
good
achievement.
We've
been
working
on,
we
put
that
monetary
policy
and
some
Guinea
IP
behind
us
as
well,
and
so
now
what
we're
doing
is.
We've
we've
looked
at
what's
going
to
be
in
for
our
our
first
early
release,
we're
looking
at
a
code
freeze
of
the
latest,
the
18th
of
this
month,
which
is
in
two
weeks
from
now,
and
to
get
into
that.
A
The
things
that
we're
looking
to
get
into
that
apart
from
the
1017
which
I
think
is
almost
merged,
we're
looking
at
two
big
ones
and
and
some
small
ones.
So
we'll
just
really
talk
about
the
tube
the
discovery
and
the
second
one
is
potentially
pruning.
So
we've
really
only
started
on
those,
but
basically
discovery
involves
them
broadcasting,
UDP,
packets
and,
and
that
are
fairly
well
specified
in
order
to
discover
a
bunch
of
other
peers
and
adding
them
to
the
list.
A
So
that's
underway
at
the
moment,
the
other
big
one
I
guess
is
pruning
because
our
database
is
currently
humongous
and
gets
bigger
every
time
with
every
block.
So
we
need
to
find
some
way
of
reducing
that
size.
So
that's
the
second
thing
that
we're
hoping
to
get
in
before
the
code
freeze
in
the
next
two
weeks
and
then
there's
a
couple
of
smaller
things
which
I
won't
even
mention.
A
So
that's
code,
freeze,
as
I
say,
are
only
eight
well
before
some
at
the
latest,
the
18th
of
July
and
then
we'll
have
two
weeks
of
soak
testing
and
stress
testing
for
some
of
the
for
some
of
the
team.
You
won't
need
all
the
team
for
that
looking
to
an
early
release
as
some
kind
of
early
release
beta
in
around
the
1st
of
August.