►
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
Now
those
are
the
things
that
will
be
in
following
releases,
which
will
actually
some
of
them
will
be
features,
but
we're
calling
our
release
that's
coming
up
shortly
over
the
next
in
about
two
weeks
time
around
the
8th
of
August,
that's
going
to
be
a
beta
release
which
will
contain
basically
all
the
functionality
that
we've
achieved
so
far.
So,
let's
find
out
about
the
discovery.
The
discovery
is
basically
sending
UDP
packets
around
the
around
the
network
to
try
and
discover
the
neighbors
of
peers
in
order
to
build
up
the
the
peer
list.
B
A
B
Quite
the
opposite:
it
turns
out
that
most
pierced
after
are
kind
of
in
the
greedy
mode,
so
they
do
not
accept
connections
from
others.
We
receive
a
lot
of
too
many
peers,
disconnected
message
so
yeah.
There
are
not
many
peers
that
accept
other
connections
or
maybe
they're
just
already
full
of
other
peers.
A
Yeah,
okay,
so
unfortunately
it
wasn't
the
bountiful
provider
of
blocks
and
things
that
we
hoped
for
so
we'll
look
at
our
options.
I
guess
in
in
the
next
iteration,
but
the
discovery
as
we
described
it
in
the
beginning
is:
is
there
and
we
are
able
to
to
get
a
a
a
fairly
well,
a
pretty
much
never-ending
list
of
peers
appears
of
peers
right.
A
Okay
cool,
so
that
was
discovery
and
the
other
I
guess
significant
bit
of
functionality
we
were
looking
at
was
the
pruning
which
is
trying
to
keep
the
size
of
our
database
down
by
removing
parts
of
the
state.
Try
that
are
hopefully
not
well
provably,
no
longer
needed
so
Alan.
Where
are
we
with
that?.
C
Well,
this
week
we
have
have
food
that
go
through
the
review
process
and
it's
close
to
be
merged.
Hopefully
today
and
we
have
a
two
instances
running
this
cold
on
Amazon
and
we
found
that
the
pruning,
at
least
as
for
the
blog,
the
blog
in
1
million
its.
We
have
4
gigabytes
database
with
pruney
against
12,
almost
20
gigabytes,
without
proving
so
it's
the
it's
a
good
disk
sale.
It's
like
a
quarter
of
the
size
so
looks
promising.
C
A
So
that's
good
and
then
we've
we
have
done
I
mean
that
the
the
everything
still
works,
obviously
because
all
the
transactions
are
being
processed,
but
over
the
next
two
weeks
we're
gonna
give
that
even
more
of
a
of
a
rigorous
test.
One
of
the
tests
that
we
were
that
we
did
complete
during
the
week
was
the
the
theorem
classic
test
net
Adam,
you
you
that
finished
up
for
you.
Yes,.
D
A
Okay,
cool,
so
that's
another
another,
a
good
test,
I
guess
to
have
under
our
belt.
We
know
that
we
can.
We
can
synchronize
that
and
in
the
area
of
testing
we've
started
looking
at
the
sweet
Radek
that
that
sweet,
I,
I,
thought
might
have
might
have
been
difficult
to
leverage
you've
been
looking
at
it
for
a
few
days.
What
what's
your
experience
been.
E
All
right,
so,
basically,
that's
the
suite
is
a
bunch
of
JSON
files
with
even
more
tests
within
each
so
well,
they're,
quite
consistent.
So
with
with
a
single
piece
of
small
framework,
we
can
leverage
a
really
big
amount
of
tests
to
be
executed
against
on
VM
and
yeah.
This,
basically
a
lot
to
be
gained
here
as
long
as
those
tests
of
good
quality,
but
so
far
we
have
no
reason
to
doubt
that.
A
Okay,
cool,
so
we'll
have
will
I'm
not
sure
exactly
we
don't
know
yet,
when
we'll
be
able
to
get
a
report
on
that,
but
the
goal
that
you
have
at
the
moment
is
to
try
and
get
those
executing
and
generate
the
generate
the
output.
So
we
see
see
where
we
are
with
respect
to
the
in
inverted
commas:
I
guess
standard
test,
suite
I
suppose
it
is
a
standard
test
week,
really
isn't
it
I.
A
E
That's
specified
the
environment
under
which
the
tests
are
on
I
haven't,
found
anything
but
would
specify
the
current
fork
that
is
being
around
like
even
the
current
EIP.
That's
that
to
change
the
rules
of
the
VM,
but
mainly
you
know,
I
just
haven't
dig
through
all
of
those,
because
that's
really
a
lot
a
lot
of
tests,
so
it
may
be
simply
that's
not
on
all
of
them
and
those
parameters
are
specified
and,
and
the
different
ones
are
the
difference
here.
For
the
you
know,
the
beginning
of
the
theorem
right.
A
Okay,
but
as
you
say
for
not
an
enormous
amount
of
effort
surprisingly-
and
you
know
happily
we'll
be
able
to
get
results
on
all
the
tests
that
are
there,
so
that's
that's
definitely
worth
doing
yeah,
okay,
cool
thanks,
rhotic,
okay,
so
that's
I,
guess
the
the
current
state.
We
have
we're
pretty
happy
that
we've
got
the
discovery
that
we
set
out
to
do
Don,
although
we
were
slightly
surprised
by
the
quality
of
the
peers
that
we
got
pruning,
is
looking
quite
good
and
should
go
in
today,
which
is
well
today
or
possibly
early
tomorrow.
A
There's
still
one
reviewer
standing
on
that,
which
is
pretty
good.
All
things
considered
because
excuse
me,
because
today
we
declared
as
the
day
that
we
freeze
the
code
so
no
more
functionality
that
goes
in
after
today.
Only
bug
fixes
that
that
are
going
to
affect
the
the
quality
of
the
beta,
and
so
what
we're
gonna
attempt
to
do
now
is
to
do
some
stress
testing
of
the
of
the
current
code
over
the
next
couple
of
weeks,
and
to
that
end
we
have
to
come
up
with.
We
have
come
up
with
a
plan.
A
Basically,
we
know
the
we
know
the
basic
functionality.
We
have
the
test
that
we
that
we
executed
along
the
along
the
way
for
each
milestone.
We
have
the
tests
from
the
test
suite,
which
we
also
want
to
to
do,
and-
and
we
have
a
bunch
of
ec2
instances
to
set
up
our
networks
and
and
and
do
stuff
for
so.
What
we
need
really
is
a
is
a
matrix
of
all
the
different
scenarios
that
we
want
to
test
and
to
work
our
way
through
them
and
then
I
guess.
A
Sync
I've
been
running
the
regular
sync
on
that
ec2
instance
now
for
probably
a
week,
and
it's
still
not
synchronized,
so
we'll
probably
have
to
provide
users
with
bootstrap
database
to
allow
them
to
skip
that
internal
wait
or
use
fasting.
So
all
that
sort
of
documentation
needs
to
be
sorted
out
and
put
on
the
wiki
and
then
of
course
this
is
a.
This
is
a
very
early
basic
release.
A
So
the
the
next
release,
or
the
next
page,
at
which,
as
I
say,
the
Nama
clutter,
is
gone
a
bit
wonky
at
this
stage,
because
there
actually
will
be
slightly.
There
will
be
some
new
features
in
it,
which
will
be
the
integration
with
it
with
the
Daedalus
wallet
and
that
will
be
a
more
significant
release.
So
that
suits
us,
because
this
is
a
good
opportunity
to
try
and
get
some
some
feedback
from
from
fairly
technical
people
through
either
the
slack
there's
them.
A
A
So
yeah,
that's
what
happened
last
week,
we've
got
the
this
stuff
in
so
we're
pretty
much
there.
There
abouts
facing
into
two
weeks
of
of
testing
and
gonna,
come
up
with
a
plan
a
matrix
for
the
snares
you
want
to
test
and
then
potentially
look
at
the
Daedalus
wallet
and
ETH
support,
depending
on
on
how
many
resources
need
for
a
test
plan.
A
No,
okay,
well
good
I,
guess
I
mean
in
some
ways.
This
is
this
is
we're
getting
a
close
to
the
exciting
part
where,
as
some
more
people
are,
hopefully
gonna
have
a
look
at
the
code
and
yeah
that
actually
reminds
me
that
one
of
the
things
we're
gonna
have
to
do
after
that
and
won't
happen
for
a
little
while
yet,
but
we
might
start
making
the
initial.
A
The
initial
inquiries
is
to
try
and
get
some
kind
of
audit
done,
and
when
we
go
to
do
that,
there
will
be
a
phase
of
us
looking
at
our
code
from
the
point
of
view
of
okay,
how
do
we?
How
do
we?
What
do
we
want
to
do
to
make
sure
that
the
that
it's
as
ordered
ready
as
possible?
So
that's
something
else:
that's
going
to
come
up,
so
there's
lots
and
lots
of
tasks
that
are
going
to
come
up
that
aren't
I,
guess
just
that
aren't
going
to
be
related
to
developing
entirely
new
features.