►
From YouTube: IOHK Team Grothendieck - Ethereum Classic Scala Client Meeting, June 27, 2017 (Take 2)
Description
Second attempt at weekly meeting, the first was ruined by an echo.
A
A
Last
week
we
were
trying
to
complete
the
milestone
involving
the
command
and
query
interface
or
the
JSON
or
PC
as
it's
commonly
known,
and
we
had
I
think
about
seven
or
eight
of
those
guys
left
to
complete,
and
one
of
them
was
in
a
fairly
large
peor,
as
they
were
all
related
filters.
So
quite
a
few
of
them
have
gone
through
so
I'm.
Just
gonna
share
the
screen.
A
So
we
can
see
the
burndown
basically
there's
a
big
there's,
a
big
drop-off
there
as
as
those
six
went
through.
So
the
good
news
is
we're
pretty
much
complete
with
this
Jason
or
PC
milestone
and
that
peor
has
gone
through
and
there
is
there's
been
quite
a
bit
of
testing
done
with
mist
and
we'll
get
the
results
of
that
together
and
we'll
put
a
link
up
for
it,
and,
apart
from
that,
I
think
there's
one.
A
I
was
just
saying
that
there
is
still
one
p
or
to
be
merged,
which
I
think
your
your
just
finishing
up.
It
was
a
something
that
you
found
with
regard
to
the
filter
and
the
pending.
Yes,
I
mean
implementing
the
pending
block,
filter
and
I
already
have
some
reviews
on
my
foot
requests,
so
I
think
it
will
be
done
in
between
tomorrow
and
today,
probably
okay,
okay!
So
that's
a
that's
a
pretty
good
improvement.
A
We're
not
gonna
say
that
the
milestones
complete
yet
because
it's
it's
not
complete
till
it's
fully
done,
but
we're
as
close
as
we
possibly
could
be.
To
the
extent
that
we
have.
We
have
restarted
some
of
the
other
business
that
we
were,
that
we
were
taking
care
of
some
of
the
other
functionality
that
we're
trying
to
take
care
of
so
Adam
you're
working
on
the
on
the
mining
right.
Yes,.
A
C
I
discovered
that
when
repeated
issuing
transaction
from
single
account
to
get
and
then
propagating
those
transaction
to
our
clients,
we
may
lose
one
transaction,
which
means
that
this
other
transaction
in
chain
are
all
invalid
and
we
are
unable
to
mind
them
because
of
knowns
difference.
But
this
is
I
believe
special
case
when
one
account
issue
like
two
transactions
per
second
and
two.
Two
clients
are
concurrently
mining
and
competing
with
block.
So
I
will
take
more
into
that.
A
Okay,
yeah
great
I,
mean
I,
know
where
I
suppose
there's
lots
of
views
you
can
take
on
this,
but
I
always
say
what
this
reminds
me
of
is
just
how
important
it
is
to
test,
because,
obviously
it's
great
to
find
this
before
we
try
to
try
to
go
to
beta
and
it
just.
It
always
reminds
me
how
important
it
is
to
try
and
you
know,
do
as
much
testing
as
humanly
possible,
so
I
know
you're
keeping
a
log
of
that,
and
we.
A
Cool
okay,
thanks
for
that
Adam
Radek
you've
been
looking
at
some
of
the
some
of
the
code.
You
did
a
little
bit
of
maintenance
on
the
code
base
in
the
area
of
the
tests.
I
know
just
to
frame
this
I
mean.
Last
week
we
were
looking
at
your
pee
or
for
for
the
for
the
Wallace
stuff
for
the
keystore
and
that's
all
sort
hadn't
gone
through
and
you've
moved
on
to
this.
Yes,
exactly.
D
D
D
D
A
A
Okay,
but
that's
that's
some
steps
in
the
right
direction,
thanks
rhotic
and
going
back
to
I
guess
our
JSON
or
PC
interface.
While
we're
not
finished
the
milestone,
we
pretty
much
have
the
well.
We
can't
say
that
we've
completely
finished
with
the
milestone,
because
there
is
we're
not
ready
to
merge
it.
Yet
we
still
have
one
p
or
hanging
out
but
Lukesh.
B
While
it
was
good
for
showing
the
functionality,
it
was
not
very
good
for
non-technical
people,
so
this
time
I've
prepared
a
demo
that
actually
shows
a
very
simple
doubt.
The
trans
insight
missed
and
it's
fully
integrated
with
him,
but
first
things.
First,
my
setup
for
today
is
quite
different
than
the
last
time.
I
am
not
using
gas
at
all,
and
this
time
is
just
our
node
connected
directly
to
mist
and
to
ETH
Milan
that
that
I
used
to
mind
blocks.
B
So
the
application
is
just
a
simple
messaging
application:
we've
got
a
bunch
of
maybe
I'll
show
you
the
contract
code
first.
So
this
is
just
one
method,
new
message
that
issues
one
even
new
message,
even
nothing
special,
but
the
application
is
quite
a
bit
more
complex
than
that.
So
we
are
able
to
to
show
all
the
messages
from
all
friends,
along
with
the
time
stamps
of
the
blocks.
B
B
B
At
the
magnet
running,
but
if
I
now
try
to
send
another
message
to
the
thread,
it
should
almost
immediately
show
on
the
list.
Let's
give
some
time
for
the
block
in
mind,
and
here
is
this
message
and
I:
remove
the
filter,
computing
and
once
again,
I've
got
the
list
of
all
the
messages
from
whatever
threat.
I
cannot
secure
the
messages
so
that
there
is
no
message
with
with
such
type,
ID
or
generally
I.
Think
input
has
slight
delay.
D
A
A
B
B
We
are
able
to
get
the
filters
we
are
able
to
now.
We
are
able
to
get
the
blocks
for
the
timestamp
and
get
the
transaction
object
to
get
its
sender
and
yeah.
That
would
be,
and,
as
I
said,
it's
fully
integrated
with
mist
and
it's
just
our
client
without
gas
or
any
other
intermediate
client
connected
to
me.
A
A
A
Yes.
So
far
we
haven't
found
any
issues
besides
broadly
and
maybe
a
nice
bag,
but
our
application
behaves
exactly
as
other
clients,
okay,
excellent
okay.
So
that's
our
status
for
the
last
week,
which
is
I,
think
pretty
good.
We're
definitely
going
to
be
I
mean
just
to
I
guess,
what's
the
word
I'm
looking
forward
just
to
officially
say
that
next
week,
we'll
the
milestone
will
be
will
have
been
achieved.
A
We
can't
quite
say
it
yet,
just
because
the
PR
is
merged,
but
we're
extremely
close
and
in
the
near
future,
I
think
we'll
also
have
the
our
mining
integration
milestone,
complete
big,
a
there's,
a
question
mark
over
that,
because
it's
not
complete,
but
also
because
just
some
of
the
stuff
that
were
that
we've
that
we
found
has
made
it
a
bit
more
of
an
interesting
milestone.
It
was
it
was,
it
was
starting
to
look
really
boring,
but
now
it
looks
a
little
bit
more
interesting.
A
We
found
one
or
two
potential
issues,
so
that
would
be
that
was
good
for
last
week
and
looking
good
for
this
week
as
well.
So
the
planning
I
guess
starts
this
week
for
our
beta,
who
I'm
making
the
assumption
that
we'll
have
those
two
milestones
sorted
out
very
soon.
So
the
planning
then
starts
with
regard
to
how
we're
going
to
do
our
beta
and
what's
what?
A
What
are
the
things
you're
going
to
be
in
so
one
of
I
think
the
things
that
will
definitely
be
in
that
we
have
to
work
on
is
discovery,
so
that's
gonna
crank
up
this
week
and
the
one
or
two
other
things
are
floating
around
there.
We've
discussed
the
possibility
of
ETH
support
and
we've
looked
at
an
estimate
for
that
and
we've
looked
at
the
possibility
of
integrating
well
we're
currently
looking
at
the
possibility
of
integrating
with
Daedalus.
So
those
are
a
couple
of
things
that
we
hadn't
really
hadn't,
really
timed
in
our
original
estimate.
A
So
if
we
do
a
couple
of
those
things
and
obviously
the
the
timeline
will
change
likely-
probably
not
buy
too
much,
but
that
as
I
say
all
remains
to
be
seen
so
next
week
we'll
we
will
hopefully
be
talking
about.
Definitely
one,
if
not
two
milestones
achieved
and
talking
about
our
approach
to
two
beta.
What
what
other
things
we're
gonna
prioritize
and
get
in
before
we
go
to
beta.