►
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
So
once
again
the
usual
proviso
that
quite
a
few
of
the
team
are
out
on
a
training
course,
so
we're
operating
with
a
very
much
reduced
team
at
the
moment,
but
we
still
managed
to
get
1.0
from
out
the
door
last
week.
So,
as
we
mentioned
last
week,
1.0
has
been
released
after
a
beta
period
of
about
I.
Guess
it's
6
months
and
release
candidate
1
was
out
in
December
and
last
week
was
1.0.
So
the
major
the
feedback
that
we've
had
so
far
is
some
people
are
having
difficulty
with
the
synchronization.
A
A
Originally
the
the
Daedalus
wallet
synchronized,
the
Daedalus
wallet
has
been,
has
been
altered,
basically
to
integrate,
with
etherium
classic
the
mantas
client
and
so
in
the
integration.
One
of
the
things
it
has
to
do
is
synchronize
the
chain
now,
with
etherium
classic
the
chain
takes
a
long
long
time
to
synchronize
and
to
avoid
the
entire
synchronization
process.
We
use
something
called
fast.
Sync
by
default
and
fast
sync
takes
all
of
the
state
nodes
from
a
recent
snapshot
of
the
state
and
downloads
them
before
it
begins
to
download
the
blockchain.
A
So
the
Daedalus
wallet
interprets
that
as
zero
percent
synchronized,
and
so
what
happens
is
the
the
Daedalus
wallet
will
will
stay
at
zero
until
the
entire
state
is
download,
which,
as
I
say,
can
take
some
time
then
to
unfortunately,
to
add
to
the
confusion
they
two
logs.
One
is
the
dateless
log,
which
is
the
front-end
long,
as
it
attaches
reads
from
the
backend,
and
the
second
is
the
Mantis
log,
which
is
the
actual
back-end
log.
A
So
the
front-end
log
will
will
produce
a
lot
of
debug
type
output
where
it
shows
that
it's
consistently
trying
to
attach
to
the
backend
and
then
the
backend
log
really
shows
how
the
backend
is
progressing
in
terms
of
the
download,
so
just
to
illustrate
that
we've
installed
it
on
a
Windows
10.
We've
installed
the
integration,
dateless
mantas
on
Windows
10,
hosted
box
and
we're
going
to
show
how
to
view
the
logs
to
make
sure
that
the
backend
is
in
fact
progressing.
So
Conrad
I
believe
you're
going
to
share
your
screen.
Oh.
B
B
B
A
B
B
Vm
and
my
resolution,
so
it's
clunky
okay,
so,
as
you
can
see,
the
directory
is
in
use
and
calm
that
Monty
slugs
and
our
bar
controls
are
monkeys
long
when,
after
the
after
cuz
I
have
to
install
like
there
are
zipped
files
from
the
old
logs,
but
when
after
15
days
only
a
month,
is
that
one
okay?
So
let's
run.
A
A
B
B
A
B
A
B
B
B
A
B
A
A
B
A
B
B
A
A
B
A
B
A
B
A
As
we've
said
that
this
log
is
really
shows
it,
doesn't,
it's
never
gonna
show
a
lot
about
the
progress
of
the
the
back
end,
really
the
one
that
that
people
want
to
look
at
if
they
want
to
make
sure
that
the
back
end
is
actually
synchronizing.
The
chain
is
the
Mantis
log
that
we
showed
a
little
earlier.
A
Okay,
alright,
so
that's
the
to
log
files.
Now,
as
we've
said
it
it's
it's,
it
is
a
little
misleading.
There's
no
question
about
that
because
it
does
set
at
0
percent
for
a
while.
But
the
reason
is,
as
we've
stated
is
because
it's
downloading
the
state
nodes
and
that's
just
not
registering
as
progress
once
those
state
nodes
are
downloaded
and
it
starts
to
download
the
rest
of
the
chain.
Then
it
should
increase.
However,
we
have
a
shortcut
for
that.
A
So
what
we
recommend
and
users
to
do
is
to
download
the
bootstrap
database
and
install
that
and
that
allows
them
to
circumcircle
vent
the
the
weight
which
can
potentially
be
several
days
depending
on
network
resources
and
the
state
of
the
internet
and
network
at
the
time.
So
Conrad
I
think
you
already
have
you
already
downloaded
that
or
do
you
have.
A
Those
steps
are
outlined
on
the
on
the
Montes
wiki,
along
with
the
checksum
that
you
use
to
check
your
bootstrap
download
against.
So,
in
other
words,
when
you
download
this
bootstrap
database,
you
want
to
make
sure
that
you're
not
suffering
a
man-in-the-middle
attack,
and
so
you
take
the
zip
file,
that's
been
downloaded
and
you
use
the
search
util,
the
name
of
the
file
and
Shah.
A
B
A
A
B
A
A
B
A
A
Okay,
so
I
don't
know
how
long
this
will
take,
but
probably
not
I
mean
not
more
than
this.
This
this
our
bootstrap,
was
created
last
week.
So
when
users
use
the
the
latest
bootstrap,
it
shouldn't
take
more
than
an
hour
I
guess
to
some.
Sometimes
it's
something
something
in
the
order
of
hours
to
get
to
get
up
to
speed
again,
depending
on
network
availability,
yeah.
A
B
B
A
Think
the
the
just
a
big
takeaway
for
for
anyone
watching
is
just
that
is
just
to
try
and
use
the
bootstrap
database
and
also
to
make
sure
you
do
your
checksum
of
the
database
when
you,
when
you
download
it
and
that
will
save
a
huge
amount
of
time
waiting
for
the
network
to
to
synchronize.
Having
said
that,
it
is
on
clear
it
is
misleading
when
you
start
the
wallet
that
it
stays
on.
0.0%
apologies
for
that.
That
is
something
that
we
will
have
to
look
at.
I'm,
not
sure
how
we
can
it's
something.
A
That's
gonna
have
to
go
into
the
into
the
pile
of
tasks
that
need
to
get
sorted
in
in
that
actually
using
the
fast,
the
the
state,
no
synchronization
as
part
of
the
chain.
Synchronization
progress
bar
is
not
something
that
has
been
added
to
the
list
as
of
yet
but
as
I
say
it.
The
whole
thing
is
fairly
easily
too
easy
to
walk
to
to
get
around
by
by
using
the
bootstrap
database.
A
A
A
A
We
know
that
there's
some
some
POS
that
are
sort
of
that
have
been
that
were
started
even
before
we
released
1.0
but
didn't
make
it
into
the
1.0,
so
they
will
definitely
be
in
1.1
and
then
there's
you
know,
there's
there's
some
audit
results,
I
guess
you'd
call
them
in
terms
of
there
was
one
or
two
functions
found
that
weren't
that
were
not
actually
being
used.
So
we
just
have
a
little
bit
of
cleanup
to
do
there
in
terms
of
the
what
what
new
features
will
be
in
there.