►
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
B
So
I've
been
testing
the
SB
API
I
found.
There
is
an
issue
with
more
than
discovery
that
I
just
looked
in,
and
there
is
also
when
the
miner
is
is
on.
The
blog
sinking,
has
issues
keeping
up
with
the
latest
blog
other
than
that
I
haven't
found
any
major
issue
yet,
and
the
testing
is,
we
are
still
missing
testing
regarding
sending
transactions.
B
B
A
Okay,
good,
so
that's
a
small
bit
of
a
surprising
results,
but
then
again
that's
why
we
do
the
the
regression
test.
So
those
two
I
guess
issues
that
you
found
on
the
board
and
we'll
be
investigating
them
and
trying
to
come
up
with
either
a
fixer,
an
explanation
for
what's
going
on
over
the
next
week
now,
I
know
that
East,
it's
just
over
so
there's
been
a
bit
of
there's
been
a
little
bit
of
disruption
and
I.
Think
this
week,
there's
a
few
there's,
a
scholar
conference
that
quite
a
few
people
are
going
to.
A
So
it's
probably
gonna
be
a
slow
week,
but
I'll
expect
it
by
this
time
next
week,
we'll
certainly
have
a
better
indication
of
what
we're
gonna,
what
we're
gonna
do,
but
those
they
don't
think
they're
gonna
be
I,
don't
think
they're
going
to
affect
our
release
date.
But
let's
see,
let's
see
how
what
happens
when
we,
when
we
get
into
them
a
bit
more
okay
and
then
Conrad
you've
been.
How
are
we
doing
with
P
or
is
what's
what's
left?
What's
what's
left
to
merge
or
are
we
fixed
yeah.
C
Last
week,
I
have
marked
improvements
to
the
discovery
and
there
were
some
problems
with
incoming
connections
and
it
was
fixed,
and
now
there
is
one
of
outstanding
PR
with
the
issue.
I
recently
found
that
after
first
sake,
we
are
saving
all
our
state
notes
under
one
key
for
pruning
and
after
the
fasting
end,
and
we
are
pruning
the
target,
look,
we
would
have
almost
22
millions
of
state
notes
some
shots
prune.
It
was
taking
a
lot
of
time,
so
there
is
one
we
are
to
fix.
That.
B
A
Of
April
is
what
we
were
saying
middle
of
April,
so
it
looks
like
it's
going
to
be.
I
mean
I'm,
going
to
say
that
we're
not
going
to
release
next
week
for
sure
so
it'll
be
in
the
last
two
weeks
of
April
when
we're
when
we
when
we
expect
to
release,
so
that
gives
us
an
opportunity
to
look
at
some
of
the
things
that
we
found
in
our
regression
test
and
just
and
just
when
we
get
the
fixes
in
give
give
a
chance
to
to
bed
those
down.
A
A
C
Yeah
there
is
this
client
but
Belfort
for
our
clients,
which
for
transaction
execution
and
it's
basically
locally
sinking
from
a
master
note
over
1
million
blocks,
and
we
have,
after
all
the
performance
improvements.
We
have
go
down
from
13
hours,
40
14
hours
to
6,
so
it's
really
good
improvement.
In
that
case,
you
know
this
quite
performances,
I
would
say
on
the
par
with
other
clients.
C
A
Ok,
so
that's
that's,
obviously,
something
that
that
we
can
look
forward
to
getting
that
out
there.
Alright.
So
the
only
other
I
guess
thing
to
to
make
people
aware
of
is
that
beyond
this
1.1
release,
which,
as
I
said,
is
probably
gonna,
be
the
last
two
weeks
in
April
we're
starting
to
look
at
the
following
release
and
and
ramp
up
our
requirements
gathering
and
a
level
of
planning
around
that
release.
A
So
that's
what's
ongoing
at
the
moment
and
I'm
guessing
that
that
release
will
be
well,
definitely
will
be
towards
the
in
the
in
the
last
quarter
of
the
year.
So
sometime
in
q4
and,
what's
what's
in
it,
I
will
be,
will
document
that
over
the
next
week
or
so,
okay,
so
short
and
sweet
again
today
we're
still
at
that
stage
of
trying
to
get
1.1
out.
Some
issues
were
found
in
regression.
A
That
may
be
a
small
surprise
there,
but
as
I
say,
that's
why
we
actually
do
the
regression
to
make
sure
that
there
is
the
level
of
quality
when
it
goes
at
the
door
and
and
that's
going
to
cause
a
pause
for
us
to
try
and
figure
out
what
to.
And
you
know
what
what's
the
fix
required
for
them,
but
still
aim
for
the
second
half
of
April.
Okay
and
any
questions
in
any
of
that.