►
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
crossing
geek
weekly
status
meeting
today
is
Tuesday
the
11th
of
July.
Last
week
we
talked
about
our
status
with
regard
to
the
two
milestones
that
we
had
been
working
on.
One
was
our
Jason
or
PC
API,
the
other
one
was
our
mining
integration
and
we
had
completed
those
as
of
last
week.
So
then
we
were
looking
to
do
a
couple
of
different
things.
We
talked
about
getting
set
up
for
our
beta
tests.
Sorry,
our
beta
release.
A
A
We're
still
we're
not
there
yet
the
tasks
that
we
specifically
because
we've
been
working
on,
getting
ready
for
a
beta
release
and
that
basically
has
taken
up
all
our
bandwidth,
and
so
we
have
had
the
tasks
that
we
had
basically
have,
as
I
say,
taken
off
the
Pinewood,
so
no
movement
on
the
ETH
the
day.
The
Daedalus
integration,
as
I
said
last
week,
was,
is
still
in
the
planning
stage.
So
not
surprisingly,
there's
no
there's
no
movement
on
that
yet,
but
we
have
been
working
on
getting
ready
for
our
for
our
beta
release.
A
Now
we
have
two
larger,
rather
bigger
pieces
of
functionality
to
get
in
and
we'll
come
to
them
in
a
minute.
But
one
of
the
other
things
that
we
wanted
to
square
away
was
our
testing
with
test
naps.
So
we
didn't
need
to
go
back
and
check
that
our
client
does
synchronize
correctly
with
with
test
night
and
Adam.
You
you've
been
working
on
that.
Yes,.
B
A
B
It
was
on
more
than
because
this
is
I
if
I
may
say,
target
test
net
for
a
theory
on
classic,
since
this
test
net
does
not
implement
a
IP
158,
which
is
cleaning
out
cleaning
up.
The
accounts
that
were
created
in
spam
attack,
so
Rob
stem
requires
the
CIP
to
be
present,
which
is
more
for
helium,
not
classic
yeah.
A
Here,
iam
of
the
cold
aetherium
hard
fork,
if
you're
in
HF
I'm,
yours,
ok,
so
so
yes,
there's
a
point
there.
I
guess
about
the
RUP
stem
Network
that
when
we
do
get
round
to
supporting
aetherium
HF,
we
will
have
to
go
back
and
check
that
test
that
as
well,
because
we'll
have
that
support
built
in
but
for
the
moment
were
going
through
the
etherium
classic
test
net
and
it's
in
progress.
Basically,
there
was
I
guess
that
one
little
scare
and
then
there
was
one
or
two
configuration
issues,
but
it's
going
I
think
reasonably
well.
A
C
A
Okay,
cool
and
that's
I'm,
just
going
to
talk,
I
guess
in
terms
of
the
in
terms
of
our
release
or
our
beta
release,
we
will
be
able
to
integrate
that
in
I.
Imagine
will
be
will
be
called
complete
on
that
by
next
Tuesday.
Is
that
about
right?
But
that's
that's
how
it's
looking
at
the
moment.
It's
that's
about
right!
Okay,
all
right!
A
D
So
we
have
decided
to
go
for
for
a
basic
boolean
implementation.
On
the
first
iteration,
we
are
trying
to
improve
the
solution,
but
the
first
one
basically
tries
to
delete
all
MPD
gnomes
that
are
not
longer
needed
and
when
dealing
with
pruning,
you
have
two
main
problems.
The
first
one
is
that
when
you
are
creating
new
states,
there
are
notes
that
are
no
longer
needed
because
of
how
Michael
Patricia
tree
works,
and
the
other
issue
is
that
a
nodes
are
referenced
by
hash.
D
So
it
might
happen
that
you
might
be
using
the
same
known
in
different
parts
of
the
state.
Try,
and
so
you
cannot
just
let
it
delete
it
as
as
you
wish.
So
we
are
working
on
a
basic
pruning
solution
which
is
tracking
a
null
reference
count
based
on
block
numbers,
and
there
will
be
a
let's
say,
a
show
that
will
be
removing
all
no
longer
needed
node
and
it's
currently
working
progress
and
we
will
probably
start
we
will
probably
blow
it
up
version
on
our
integration
server
and
start
checking
how
that
works.
A
Okay,
so
just
when
we,
when
we
say
pruning
place,
a
reference
count
based
on
block
number
I
mean
it's
there's
sort
of
two
aspects
to
that
right.
There's
the
there's
the
reference
count
for
a
node
based
on
whether
the
node
is
being
used
in
multiple
places
in
the
Tri
and
then
there's
marking
nodes
that
might
be
deleted
with
the
block
number.
They
might
be
deleted
that
right,
yeah,
that's
correct,
okay,
just
to
sort
of
separate
those,
two
things
we
don't.
We
don't
sort
of
reference
count
with
the
block
with
the
block
number
as
such.
A
There's
like
he
it's
a
sort
of
a
there's.
Two
aspects
to
a
I
guess
is
what
I'm
just
trying
to
clarify.
Yes,.
D
A
Okay,
so
that's
the
the
pruning
effort,
and
just
while
we're
just
talking
about
stuff
that
we've
done
over
the
last
week,
Radek
you've
been
looking
well.
You've
been
looking
a
couple
of
things,
you're
looking
at
some
of
an
issue
or
two
that
came
up
but
you're.
Also
looking
at
user
friendly
flying
or
making
more
readable,
our
configuration.
A
Okay,
good
stuff,
okay,
so
I
guess
that's
the
summary
of
what
we've
been
up
to
and
so
last
week
I
was
talking
about
a
code
freeze
next
Tuesday,
which
is
the
18th
and
a
beta
on
the
1st
of
August.
So
given
where
we
are
over
the
last
week,
one
thing
I
think
that
we
wouldn't
be
too
I,
mean
I,
think
the
discovery
stuff
we're
going
to
we're
gonna,
get
that
in
it's
it's
reasonably
independent
of
pretty
much
all
of
the
other
codes.
A
What's
the
word
I'm
looking
for
thanks
to
give
it
a
given,
give
it
more
time
to
for
us
to
test
it,
so
it
would
be
a
bit
of
a
squeeze
to
try
and
get
that
in
so
I.
Don't
think
that
that's
going
to
go
into
the
release,
that's
gonna
be
released
on
the
1st
of
August,
so
technically,
because
we
won't
be
fully
feature
complete.
Who
did
probably
talk
talked
about
that
peanut,
a
very
advanced
alpha,
but
I'm
not
gonna,
get
too
hung
up
on
the
particular
nomenclature.
A
A
Sorry,
not
short,
but
yes,
short,
coming.
We
download
the
whole
blockchain
by
providing
some
kind
of
some
kind
of
file.
That's
been
pre-populated
with
with
them
with
a
lot
of
the
blockchain
in
it.
So
there's
a
few
tasks
there
that
need
to
be
sorted
out
before
we
talk
about
our
early
reefs
as
well.
Okay,.