►
From YouTube: Hive Blockchain Core Developer Meeting #21
Description
The Hive blockchain is open source and community built. Core developer meeting livestreams are open for anyone to watch and provide feedback on, and are held bi-weekly to allow the devs around the world who are working on the Hive blockchain to coordinate and discuss. Check this channel's upcoming events for the next scheduled meeting, or follow @hiveio on 3speak or VIMM.TV for Hive powered live streams.
Hive is fast, feeless, and powers an incredible array of dapps in a social ecosystem where your wallet address unlocks access to blogging platforms, games, video sites, marketplaces, and beyond.
This meeting originally recorded:
April 12 - 2021
The follow up notes from this meeting:
https://hive.blog/meeting/@howo/hive-core-developer-meeting-21
The GitLab issue for this meeting:
https://gitlab.syncad.com/hive/tasks_without_projects_yet/-/issues/35
Want to learn more about Hive as a decentralized blockchain solution for web 3.0?
Website: https://hive.io/
Hive Codebase: https://github.com/openhive-network/hive
Hive development community: https://peakd.com/c/hive-102930/created
A
Okay,
so
we
are
live,
I
think,
hopefully,
okay,
so
developer,
meeting
21
time
flies
so
on
the
devsync
I
spent
the
better
of
the
last
two
weeks
making
sure
my
code
was
ready,
mostly
associations.
I
pushed
a
lot
of
tests
regarding
that
also
made
sure
that
the
recurrent
transfers
were
mergeable
again
because
there
were
some
changes
regarding.
I
think
the
latest
boost
changes
or
making
it
compatible
with
ubuntu
220,
but
that
made
it
made
it
required
a
rebase.
B
Okay,
as
far
as
what
we're
doing
we've
we're
still
doing
a
little
bit,
we're
still
writing
doing
some
testing
of
the
curation
reward
changes
and
then
we'll
make
the
change
for
the
linear,
convergent
post
rewards
to
go
to
linear.
For
that,
I
think
that's
probably
done
in
the
next
day
or
two
we're
also
working
on
the
hdb
conver
hpd
conversion
code.
B
B
B
As
you
noted,
ubuntu
20
support
is
now,
is
now
been
merged
and
developed,
so
you
can
basically
build
on
18
or
20.
mira.
Configuration
has
been
removed
from
the
build,
so
it's
no
longer
possible
to
build
mira,
and
we
did
some
other
cleanup
in
the
cmake
settings
to
make
it
easier
for
build
the
different
configurations
for
id.
B
B
We
saw
that
when
it
hit
about
the
time
it
hit,
50
million
blocks
is
using
about
15
gigs
of
memory
and
we
did
a
measurement
and
it
seems
like
it's
down
to
10
gigabytes
now,
but
we
think
there's
still
more
that
we
can
cut
out.
So
we
are
still
analyzing
that
issue
to
see
if
we
can
further
reduce
the
amount
of
memory
consumed
by
the
python
process.
B
We
have
a
fixed
implemented
for
the
api
highmind
api
pagination
issue
that
was
filed,
but
we're
still
still
reviewing
that
for
smerged
in
and
we
also
going
to
make
some
improvements.
The
opening
api
documentation
for
hivemind
we're
also
doing
a
test
to
check
how
high
mount
works
on
low
end
machine
that
doesn't
have
an
ssd.
B
It's
only
got
eight
gigabytes
of
memory
and
it's
an
intel
i3.
So
it
did
manage
to
reach
sync
state,
but
we
still
want
to
examine
a
little
more.
It
hits
it
had
some
problems
when
it
passed
out
of
massive
sink
into
regular
live
sync,
so
we're
gonna
investigate
that
a
little
bit
just
to
figure
out
what
happened
there.
B
It's
really
the
first
time
we've
tested,
I
guess
anyone's
tested,
highmind
syncing
on
a
truly
low-end
machine.
So
what
else?
We
fixed
a
hive
d,
replay
problem
associated
with
some
of
the
code,
cleanup
changes,
and
so
we're
replaying,
develop
branches
replaying
again
without
any
problems,
and
I
think
that's
about
it.
That
comes
to
mind
right
off
hand.
B
C
B
C
A
I
heard
the
six
six
start.
We
interviewed
okay,
so
that's
good
moving
on
to
today's
subject.
After
deviations
do
we
include
it
or
not
in
the
end,
because
I
feel
like
it's
pretty
much
widely
tested
and
we'll
have
another
month
to
figure
out
if
it's
truly
truly
stable
enough,
but
at
this
point
pretty
much
everything
is
tested.
B
B
I
go
maybe,
if
he's
not,
he
might
not
be
able
to
unmute.
So
I
can
relay
what
I
know
one.
One
of
the
concerns
he
had
was
that
the
there's
some
operations
there's
some
transaction
operations
associated
with
the
the
rc
plug-in.
I
mean
with
the
rc
delegations
feature
and
they're
in
the
rc
plug-in,
apparently,
which
is
normally
where
non-consensus
only
non-consensus
code
is
included.
But
in
this
case
these
are
you
know.
The
operations
themselves
are
consensus.
B
B
D
So
maybe
it
is
better
to
implement
the
storage
to
regular
sql
database
and
next
store
it's
there
without
any
limits,
actually,
instead
of
holding
them
in
memory
and
but
maybe
let's
create.
First
such
benchmark
example,
which
will
show
us
how
it
is
it
can
behave
and
how
much
operation
and
data
we
can
store
in
hyped
without
some
potential
problems.
D
So
I
think
we
can
say
that
this
implementation
is
quite
safe,
but
otherwise
I
think
it
can
make
some
problems,
especially
that
if
I
could
understand
this
feature
there,
it
can
be
easily
made
association
between
polls,
users
and
delegations
of
resource
credits
between
them.
So
maybe
it
will
be
even
very
easy
to
generate
a
lot
of
data
in
the
5g
node.
A
A
A
A
A
B
Time
I
just
assumed
that
they
were,
they
were
afraid
they
could
be
abused
in
various
ways.
One
thing
I
think
they
could
be
quite
fairly
large
transactions
and
somebody
might
just
be
able
to
eat
up
most
of
the
eat
up
most
of
the
block
size,
because
the
block
isn't
that
big
itself,
if
somebody
could
generate
a
bunch
of
these
things,
basically
fill
up
the
fill
up.
The
block.
A
Yeah,
my
well
my
so
my
consideration
is
that
we
as
we
move
into
let's
say
the
next
six
months.
So
let's
say
we
we
have
one
month
and
then
six
months
on
the
line
we
have
half
of
26..
I'm
afraid
that
in
that
timeline,
we'll
have
an
increased
need
for
a
custom
piece
of
version
from
your
team.
When
you
do
the
so
like
your
two
stuff
and
from
all
of
the
the
guys
who
are
building
like
layer
two.
So.
C
A
B
Yeah
I
mean
they
could
have
done
it
per,
but
you're
right.
They
could
have
done
it
per
block
because
they're
afraid
of
somebody
with
a
bunch
of
accounts
doing
something
to
yeah.
I
I
do
not
know
the
answer
I
mean.
If
it
I
mean
it
seems
like
if,
if
it's
per
block
it
shouldn't
be
based
on
the
number
of
operations,
it
should
be
the
size
of
the
operations
of
anything,
in
other
words,
they're,
like
a
cumulative
total
that
you
could
use
up
over
in
a
given
block.
B
A
B
A
A
A
A
B
I
just
figured
the
witnesses
so
if
you
want
to
be
involved
in
that
as
a
witness,
that's
fine,
if
you
want
to
be
the
organizator,
I
don't
care
any
witness.
I
think,
can
should
be
able
to
stand
up
and
do
this
because
we're
not
there's
no
coding
involved
in
this
right.
That's
a
strictly
a
process
of
check
it's
what
every
witness
can
do.
They
can
check
out
code
and
build
it
so.
A
C
A
So
last
time
we
I
mean
last
time
I
mean
for
hot
fox
24.
We
mentioned
a
back
bounty,
but
we
never
really
got
that
rolling
and
that
wasn't
really
necessary
and
I'm
bringing
it
I'm
bringing
it
to
the
table
again
this
time,
but
I'm
but
with
hpd.
I
have
two
dollars:
it's
hard
to
really
justify
the
making
a
proposal,
etc.
B
B
Mean
I
think
if
anybody
is
I
just
can't
imagine
a
lot
of
people
are
going
to
be
spending
a
lot
of
time
just
to
find
a
bug
to
make
a
bounty
that
wouldn't
just
look
for
the
bug
anyways,
but
I
could
be
wrong.
Maybe
somebody
will
tell
me
I'll
be
much
more
incentivized
to
do
work
if
there's
a
book
bounding
and
we
can
talk
about
it,
but
it's
it's
not
going
to
change
the
way.
We
do
anything
here.
A
Yeah,
true
so
yeah,
then
we
were
into
the
less
important
stuff
really
good.
There
is
a
hive
stem
hackathon
happening
soon.
I
don't
really
know
how
when
it's
happening,
but
there
was
some
discussion
on
matter
most
about
how
we
we
could
make
them
work
on
a
new
algorithm
to
solve
stuff
in
enhancement
like
the
communities
et
cetera.
A
How
do
you
think
that's
like
feasible
because
then
well,
we
would
have
to
build
a
a
guide
to
it
then
more
easily,
because,
as
we've
seen
seen
with
the
myc,
I
think
I
can
get.
The
learning
curve
for
heartbreak
can
be
quite
hard
and
also
I'm
not
sure,
code
done
in
a
hackathon,
even
though
it's
two
months
long
would
be
suitable
to
be
merged
quite
right
away.
So
I
just
wanted
to
get
your
take
on
this.
A
B
A
B
A
B
B
A
A
Yeah
yeah,
so
then
sorry
so
right
now
we're
using
zoom
which
works
fine,
but
it's
also
a
paying
platform.
I
mean
it's
a
platform
we
pay
thanks
to
roland
and
so
yeah.
We
never
really
tried
any
other
platform
which
are
free
like
jitsi
or
ferrari,
no,
which
obviously
there
is,
and
at
the
same
time
we
could
also
move
the
meeting
ahead
for
by
a
few
hours
to
accommodate
all
the
people,
namely
asgard.
Do
you
guys
have
any
thoughts
on
that,
especially
because.
B
I
don't
really
care
on
the
the
applications
that
are
used
for
the
meetings
I
mean
whatever
is
easiest
for
who's
ever
dealing
with.
That
is,
is
fine
by
me,
so
I
guess
I'll.
I
guess
right
now.
It's
crimson
cloud
right,
so
I
guess
it
feels
like
whoever's
doing.
The
work
should
get
the
decision
on
that
one
and
as
far
as
the
meeting
times
personally,
it's
not
a
big
deal.
B
B
A
A
That's
also
to
see
in
there
okay,
I
guess
I
just
need
to
figure
out
all
of
the
tools
and
see
how
how
easy
it
is
to
use
them
and
the
and
because,
like
I,
don't
know
how
often
roland
pays
for
it.
As
far
as
I
know,
I
think
he
pays
by
year,
and
so,
if
he
pays
by
year,
we
may
have
like
another
year
or
two
to
consume.
So.
A
A
B
B
B
B
A
A
C
B
A
B
C
A
B
Yeah,
I
guess
anyone
who's.
Anyone
can
who's
involved
in
issue.
Can
do
that
kind
of
thing.
So
certainly
anybody
who
creates
an
issue
should
occasionally
probably
check
the
issues
they
created
and
see
if
they've
either
been
done
or
no
one's
paid
any
attention
to
them
or
if
it
looks
like
they,
don't
really
want
them
anymore
and
close
them
out.
B
So
that's
that's.
Probably
the
biggest
missing
link,
I
would
guess,
is
people
filing
them
as
far
as
people
who
are
you
know,
I
think
normally
developers
will
usually
try
to
close
it
out
if
they,
if
they
can,
if
they're
comfortable
to
do
so,
but
sometimes
they
may
not
be
comfortable
to
do
so
without
the
input
from
the
initial
filer
of
the
issue.
B
B
Well,
I
mean
the
thing
is
that
we
may
know
there's
going
to
be
ones
that
are
persistently
around
for
a
long
time
and
we're
just
tracking
that
at
some
point
it
needs
to
be
done,
so
it
wouldn't
make
sense
to
just
keep
bringing
it
something
like
that
forward,
but
I
think
I
mean
just
as
I
think.
Maybe
it's
maybe
what
we're
really
saying
this
year
is.
B
We
should
be
reviewing
as
individuals.
We
should
occasionally
be
reviewing
the
issues
and
then,
if,
if
we
think
there's
some,
if
something
maybe
needs
to
be
done
or
if
it
should
be
removed
just
proposing
in
the
meeting,
I
think
that
should
be
sufficient.
I
mean
I
look
at
issues
occasionally
just
see
if
there's
ones
that
can
close
out
every
once
in
a
while
and
but
then
a
lot
of
them.
I
don't
really
know
so.
B
I
guess
the
question
is:
if
you
think,
there's
something
that
you
don't
know
personally,
what
should
be
done,
but
you
feel
like
either.
It
should
be
gotten
rid
of
to
clear
up
the
clear
up
the
the
issues
table
or,
on
the
other
hand,
you
think
it
should
be
looked
at
again,
yeah
just
bringing
forward
the
meeting.
B
C
B
C
C
A
A
A
B
I
mean
I
don't
think
it
was
necessarily
wrong.
I
just
just
didn't
think
it
was
worth
doing.
I
I
didn't
see
a
lot
of
benefit
to
it.
I
didn't
see
a
benefit
to
it.
Ultimately,
that
was
why
I
just
didn't
feel
it's
worth
the
work,
so
I'm
foreclosing
it,
but
somebody
wants
to
advance
some
arguments
to
keep
it
open.
You
know,
go
for
it.
B
You
know
the
issues
of
yeah,
it's
not
like,
we
can
just
randomly
assign
it
to
some
trusted
person
and
that
works
they.
Those
people
can't
recover
either,
because
how
are
they
going
to
know
who's?
The
original
person
is,
I
mean,
there's
there's
real
problems
there
with
that
idea,
and
maybe
the
person
who
created
just
wasn't
didn't
understand
that
yeah.
B
B
I
100
agree
with
that.
That's
what
that's
the
first
thing
I
was
saying
earlier.
In
fact,
I
was
saying
that
if
you
create
an
issue,
you
kind
of
you
should
you
know
it's
a
good
policy
to
try
to
track
it
and
see
what's
happening
with
it
over
time
I
mean
that
doesn't
mean
bug
the
devs.
You
know
every
day,
but
if
you
think
it's
an
important
issue
and
it's
not
you
see,
no,
you
get
no
response
on.
D
D
B
Yeah,
I
think
both
are
good.
I
think
it's
generally.
You
know
if,
if,
if
we're
not
clear
on
the
issue,
it's
better,
if
the
post,
if
the
author
closes
it
because
then
we
know
that
we
correctly
understood
what
they
were
talking
about
and
that
they've
either
you
know
changed
their
mind
or
whatever,
but
on
the
other
hand,
if
we're
quite
sure
we
understand
what
they're
saying
and
it's
just
wrong.
I
think
it's
fine
to
close
the
issue
too.