►
From YouTube: Hive core dev meeting #32
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
Yeah
yeah
cool,
okay,
devsync,
so
obviously
irrigation
is
now.
I
have
updated
everything
it's
it's
released
to
the
latest
develop.
I
saw
there
was
a
bunch
of
new
comics
to
that
branch.
So
that's
done
so
that's
that's
done.
I
updated
this
to
add
the
latest
test
requirements
from
abw.
So
that's
done.
I
there
was
a
few
requests
by
the
community
to
add
new
two
new
useful
operations.
A
I
want
to
record
the
miss
blocks,
which
makes
it
easier
to
track
whenever
one
misses
a
block
or
not
and
another
to
log
the
let's
say
the
hive
in
and
hbd
out
whenever
you
do
a
hype
transfer
to
the
transitory
accounts,
because
right
now
that
information
is
not
logged
which
is
annoying
for
people
who
try
to
build
trackers.
A
So
that's
also
done
pushed
replayed
tested.
So
that's
cool
and
wait.
A
The
well
technically
all
of
my
developments,
let's
say
but
the
I
added
two
new
vias
in
another
merge
request
and
so
yeah
that's
tested
replayed,
and
so
it
should
be
ready.
I
mean
stuff
here,
so
it's
not
too
complicated
what
else
yeah,
I
think
that's
about
it.
I
have
a
bunch
of
topics
regarding
hive
mind
which
will
be
my
next
focus
unless
more
stuff
comes
in
with
segregations
but
yeah.
We
can
talk
about
that
later.
That's
it
for
me,.
B
B
Yeah
I
understand
now
I
think
I
dismissed
exactly
what
was
going
on
with
the
producer
missed
part.
I
think
I
got
confused
because
I
saw
the
additional
mops
that
you
were
talking
about
and
that
you
have
listed
for
the
get
vests
to
hide
block,
and
I
thought
it
was
somehow
related
to
that.
Okay,
yeah
now
I
get
it
now.
B
As
far
as
we've
been
working
on
a
lot
of
work
on
half,
primarily
we
just
we
did
like
what
we,
I
guess
you
could
call
a
pre-release
of
half
to
ma
to
a
master
branch.
Finally,
so
we
did
that
so
that
we
could
make
changes
quickly,
develop
without
interfering
with
anybody
who
wants
to
start
experimenting
with
half
now,
so
that
the
version
that's
now
in
master
can
be
checked
out.
B
It'll
we've
synced
it
up
to
the
head
block
and
it's
takes
about
10
hours
on
a
fairly
fast
machine
to
do
so
figure
longer
if
your
machine
is
not
extremely
fast,
but
pretty
pretty
good
speed
and
we've
got
a
bunch
of
half
apps
that
you
can
try
out
too.
B
As
far
as
examples
go,
the
big
thing,
it's
still
missing,
which
is
probably
reason
for
most
people
to
hold
off
on
trying
it
yet
is
we're
still
working
on
some
scripts
to
simplify
the
installation,
which
basically
does
things
like
install
the
dependencies
and
may
even
set
up
a
half
database
itself.
B
Basically,
it's
set
it
up
so
that
when
you
can
do
a
replay
from
hive
d,
so
I
I'd
say
if
you
haven't
already
experiment
with
half,
probably
just
wait,
because
that'll
save
you
a
lot
of
pain,
figuring
out
the
installation,
steps
and
being
sure
you
get
it
all
right
across
whatever
version
you're
using
anyways,
the
other
things
we've
been
working
on
hive
d,
we've
been
working
on
as
well
we're
doing
some
work
there
to
try
to
speed
up
the
get
block,
call
and
we've
had
some
success.
B
Finally,
I
don't
know
I
think
the
last
time
I
saw
it
looks
like
it's
about
overall
twice
as
fast
now
and
the
serialization,
which
was
the
part
that
was
just
what
we're
speeding
up
is
about
three
times
as
fast.
If
I
remember
correctly,
I
don't
know
if
you
remember
bartek,
does
that
sound
about
right.
C
B
Yeah,
so
just
to
clarify,
so
what
we're
talking
about
is
speeding
up
the
the
code
that
serializes
the
output
of
api
call,
so
this
will
have
the
most
impact
any
api
call
that
returns
a
lot
of
data,
so
get
block,
obviously
returns
a
lot
of
data,
so
it
has
a
fair
amount
of
impact
there,
but
any
other
api
too.
That
happens
to
return
a
lot
of
information.
The
faster
serialization
will
obviously
speed
things
up
a
lot.
B
Okay,
let's
see
what
else
anything
there's
been
a
bunch
of
other
stuff,
but
I
think
I've
covered
it
in
my
post
in
past
and
plus
I
don't
have
all
the
details,
I
haven't
even
put
it
all
together.
Yet
so,
let's
just
move
on,
I
think
to
to
the
new
stuff.
A
New
stuff,
so
yeah
speaking
of
instant
withdrawals,
I
don't
think
we'll
ship
that
into
a
hot
floor
26,
but
I
just
wanted
to
get
your
input
on
who,
when
and
kind
of
your
overall
stance
in
terms
of
complexities.
A
I
feel
like
it's
doable,
but
it's
mostly
about
how
we
would
do
it
in
regards
to
yeah.
B
So
I
mean
I,
I
think
it's
definitely
doable.
I
think
we
should
do
it.
I
don't
think
we
should
do
it
in
this
hard
fork,
mainly
because
I
think
we
we
want
to
be
sure
we
have
broad
agreement
on
it
before
anything
else.
You
know
it's
in
community.
My
thoughts
on
it
are
a
couple.
B
B
You
know
basically
the
power
down
normal
power
down
period
and
then,
after
that,
your
account
would
then
have
the
instant
power
down
ability,
but
you
basically
had
to
say
I
know
what
I'm
doing
and
I'm
taking
off
the
training
wheels
and
safety
margins,
because
it's
not
just
training
wheels.
It's
like
disabling
your
sensors
on
your
car,
but-
and
the
other
thing,
I
guess,
is
the
discussion
of
potential
costs
for
it
and
there's
been
a
couple
different
proposals
along
those
lines.
So
I
think
that's
something
that
would
be
up
for
discussion.
B
I
think
that
I've
seen
you
know
the
idea
of
maybe
a
couple
percent
cost
to
get
spurned
when
you,
when
you
do
it
and
to
me
that
seems
reasonable,
but
anyways.
I
guess
it'll
really
be
up
to.
You
know
stakeholders
in
general
to
see
what
they
want
in
that
part,
and
I
think
that's
the
part-
that's
probably
most
contentious,
potentially.
A
Yeah,
most
likely,
oh
sorry,
go
ahead.
I
can't.
D
Yeah,
what
would
be
your
opinion
to
to
use
the
best
way
to
to
discuss
about
it,
either
in
the
most
or
create
an
issue
and
discuss
it
on
on
the
issue
of.
B
So
I
was
thinking
somebody
could,
you
know,
make
a
proposal
for
it
as
far
as
what
they
think
it
should
do,
and
I
mean
maybe
we
can
just
dig
up
some
proposals
and
that
have
been
done
in
the
past
and
just
reference
them
in
a
new
post
and
discuss
it.
But
I
I
don't
really
want
to
get
into
it
right
now,
because
I'm
distracted
with
other
stuff
frankly-
and
I
don't
see
us
doing
it
in
this
hard
fork
anyways.
So
I
think
we
should
just
re-bring
this
up
after
the
after.
A
Yeah
sounds
good.
The
only
thing
I
sorry
against
it.
Apart
from
the
whole
training
world
side
as
the
with
the
the
fact
that
then
it
could
incentivize
exchanges
from
pouring
and
powering
up,
which
could
be
yeah.
A
B
A
That's
a
good
point
but
yeah
I
kind
of
wanted
to
get
some
early
discussions,
so
we
can
then
make
a
post
and
everything.
Okay.
Then
there
was
a
question
by.
I
think
it's
mint
thrower.
He
wanted
to
add
a
v
up
to
be
published
to
basically
every
x
blocks,
for
instance
every
1
million.
A
We
log
the
vest
to
high
value,
because
I
don't
that
could
also
be
done
on
like
a
layer,
2
situation
like
yeah
like
hyperdb,
for
instance,
but
at
the
same
time
that
via
would
virtually
cost
nothing
and
allow
us
to
to
do
it
directly
and
also.
A
Yeah
but
the
issue
that
now
that
information
is
kind
of
lost
already,
I
mean
it's
not
lost,
but
my
point
is:
if
someone
wants
to
start
logging
it
now,
he
will
never
have
the
historical
values
unless
you
make
like
a
custom,
5d
and
polish
it
to
yourself
to
to
backfill
the
tv.
I
guess
you
could
do
that.
B
B
Yeah,
oh
I'll
talk
to
the
guy.
Who
did
it
here?
He's
he's
on
vacation
right
now,
but
he
should
be
back
probably
tomorrow.
I
think
and
see
what
we
did.
As
far
as
I
know,
it's
just
a
modified
hive
deed
I
mean.
Maybe
we
could
just
even
commit
those
changes
if
we
haven't
already-
which
I
suppose
would
probably
have
it.
Yeah.
A
But
then
that
did
weren't
you
working
on
a
like
accounting,
half-based
app
or
something.
B
There's
a
there
are
some
half
apps
that
we've
got
there's
there's
a
balance,
tracker
app,
that
bartek
wrote
that
basically
and
then
some
other
guys
are
working
on
now,
but
it
it'll
allow
you
to
track
your
balance
of
over
time.
So
it's
it's
not
really
the
same
thing
at
all,
but
I
mean
oh.
A
B
B
Certainly,
certainly
a
half
app,
I
think,
could
be
created
for
this
for
sure.
How
would
it
what
it
would
look
like?
I
think
we
need
to
look
at
and
talk
about
a
little
bit,
but
yeah.
A
A
Yeah
finally,
we
we
spoke
about
this
like
10
meetings
ago.
It
was
about
like
basically
adding
recurrent
transfers
on
hivemind
back
then
or
like
it
would
make
more
sense
to
have
it
as
a
half
app.
They
show
that
if
it's
as
a
half
app
as
I
was
like
digging
through
things,
I
realized
that
then
we
cannot
really
benefit
from
it.
In
a
hive,
mind
application
to
like
enable
paid
communities
and
stuff
like
this
so
well,
because
it
adds
a
new
dependency
on
everything.
B
A
B
A
A
Them
together,
oh
yeah,
which
would
be
a
startup
like
mozilla
of
mine.
We've
been
talking
they're
talking
about
foreign
yeah.
Do
you
have
a
I
mean?
I
know
we
never
ask
about
timelines,
but
do
you
know
when
more
or
less
you
guys
will
start
working
on
that.
B
Well,
we
kind
of
already
started.
I
I
don't
know
if
bartek
can
probably
comment
on
where
we
were
at,
but
I
think
primarily
we
just
wanted
to
make
some
architectural
improvements
to
it.
A
It's
being
half
hi
man.
C
We
need
to
redesign
a
few
parts
of
data
interface
providing
operations
to
the
hive
mind
and
because
we
were
focused
most
of
the
time
on
the
half
implementation
itself,
optimizations
and
others.
Actually,
that
part
related
to
improving
a
high
mind
to
to
support
direct
hub
synchronization
was
a
little
delayed,
but
I
hope
once
most
of
the
team
will
return
back
from
vacations
because
because
the
period
now
is
mostly
used
by
employees
for
vacations,
we
can
get
back
to
that.
A
Okay
cool.
Would
you
reckon
that
then
would
delay
any
community's
improvement
or
not.
B
You
can
make
communities
improvement
in
the
meantime.
It
doesn't.
I
don't
think,
it'll
really
impact
anything,
because
assuming
all
your
changes
are
on
the
query
side,
but
you
know
it
depends
on
what
exactly
what
you're
doing,
if
there's
something
you'd
benefit
from
using
half.
If
so
I
mean
the
way
half
works,
is
you
get
these
basic
tables
and
then
your
application
builds
these
auxiliary
tables
right.
So
if
all
you're
going
to
do
with
your
new
queries
is
work
with
those
those
auxiliary
tables,
then
you
could
just
go
ahead.
E
A
Yeah,
okay,
I
see
yeah.
I
was
just
wondering
because,
like
bartok
mentioned,
root
turns
away
hive
mind
ingests
data.
So
it's
curious
about
that.
B
Yeah,
so
part
of
that
is
just
that
some
of
hivemind
makes
a
epi
hivemind
makes
various
api
calls
to
hive
d
right
now,
and
so
some
of
it's
been
changed
to
pull
the
data
directly
from
the
tables,
but
I
think
not
all
of
it
has
yet
been
so
some
of
it's
some
of
the
he's
just
we're
just
in
the
process.
We
didn't
get
to
the
point
where
every
api
call
got
replaced
by
using
data
from
the
from
the
database
from
the
database
tables
instead
of
from
hd.
C
Okay,
yes
exactly,
we
have
made
some
architectural
changes
in
hivemind
a
few
months
ago,
which
quite
hard
separate
data.
The
supply
part
which
right
now
is
based
on
api,
calls
providing
operations
from
processing
them
by
height
mind.
So,
hopefully,
the
implementation
is
needed
only
in
part
or
actually
in
some
complexion
of
implementation.
C
Isn't
that
in
part
providing
the
data
and
we
don't
need
to
touch
any
other
part
of
hivemind,
especially
parts
specific
to
storing
high
mind
specific
data
on
or
serving
their
api
calls.
So
definitely
other
parts
will
be
not
touched,
but
but
this
implementation-
but,
as
I
said
previously
doing,
such
things
in
halfway
will
simplify
implementation
and
provide
better
performance
in
synchronization
and,
as
I
remember
in
the
past,
some
initial
measures
gave
us
probably
few
hours
less
time
than
original
one.
It
was
maybe
10
or
15
percent
of
our
all,
so
quite
effective
change.
A
Okay,
cool,
okay
sounds
good
anything
else
from
you
guys.
B
Good
question:
I
don't,
I
think
the
earliest
would
be
the
end
of
january,
and
that
may
be
optimistic.
It
really
there's
still
got
some
stuff
that
we
need
to
do
on
hive
d
that
I
haven't
even
started
on.
Yet
I'm
going
to
start
with
another
guy
here
once
he
gets
back
from
vacation,
and
so
that's
kind
of
the
sticking
point
and
we
could
do
a
test.
We
could
do
a
hard.
B
A
I
think
this
that
test
net
would
which
should
probably
meet
january
or
something
I'm
just
waiting
for.
Maybe
another
review
to
see
if,
like
they
have
more
feedback
on
the
inputs.
But
I
don't
if.
B
You
do
that
you
could.
You
could
also
experiment
if
you
want
it
with
some
of
the
stuff.
That's
been
done
by
bartek's
team
on
the
basically
filling
filling
the
test
net,
with
the
blockchain
too,
like
it's
like
from
the
real
net
you
might
want
to
play
with
that.
I
don't
know
oh
yeah,
I.
B
C
Actually,
there
is
no
need
to
have
a
much
documentation
for
it,
because
all
what
we
did
is
spawn
a
tool
which
converts
original
blockchain
into
a
test
emblem,
mirror
one
test
net
one
and
the
next
step
is
just
to
replay
id
using
this
blockchain.
Of
course,
both
needs
to
have
the
same
train
id
assignment
anyway.
C
C
A
Yeah,
I
see
yeah,
that's
been
nice,
okay,
so.
B
A
Yeah
I'll
try
to
I'll
play
with
that
next
week,
then
I'll
try
to
follow
around
the
this
list.
What's
the
the
name
of
the
merger
quest,
I
guess
I
can
figure
that
out.
Don't
need
to
waste
your
time.
Okay,.
B
E
E
A
E
A
E
Okay,
yeah,
I
was
wondering:
where
do
you
have
a
timeline
for
a
test
net
with
ajf
support.
B
That
is
actually
feasible
time.
We
can.
We
can
I
basically
you
that
is
pretty
straightforward
to
do
anytime.
We
have
it's
available
now,
so
I
mean,
I
think
if
he
builds
it,
it's
already
in
develop.
So
if
you
use
the
only
question,
yeah
yeah
bartek,
let
me
just
be
sure
so,
the
I
know
we've
got
it.
We've
got
the
hive
d
that
has
half
support
merged
into
half,
and
that's
is
that
from
the
developer.
That's
the
develop
branch
of
hive
d
right.
B
C
B
So
when
yeah,
so
the
answer
is
that
any
test
net
that's
built
from
develop
now
will
have
half
support
in
it.
E
Okay
sounds
good,
then
maybe
you
could
have
a
public
test
net
that
we
can
use
to
develop.
C
E
B
A
E
Yeah,
I
don't
know
just
two
gigabytes
of
ram
or
something
we
can
talk
later
on
and
figure
out.
Our
semi-public
yeah.