►
From YouTube: Hive Blockchain Core Developer Meeting #3
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.
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
This meeting originally recorded:
May 2 - 2020
A
A
I
changed
the
way
we
allocate
slots
I'll
make
a
post
about
that
later
on,
but
basically
I
previously,
we
only
allowed
the
first
and
second
slots
to
be
changed
by
the
basic
with
eight
of
witness
or
the
recovery
account.
And
now
is
the
user
can
set
its
own
slots,
but
we
still
keep
that
all
capability
yeah.
It
basically
gives
more
control
to
the
user,
basically
so
yeah
for
the
next
two
weeks.
I
think
I'll
be
more
focused
on
hot524.
A
B
Sure
we've
done
the
first,
I
guess
our
first
we've
finished
the
continuous
integration
work
that
we
initially
wanted
to
get
done
and
that's
working
now.
We
do
want
to
make
one
further
step,
though,
to
get
the
python
api
level
regression
tests
integrated
as
well.
So
that's
kind
of
the
next
step
there,
but
I
don't
anticipate
that
I'll.
Take
too
long,
we'll
probably
create
a
separate
issue
for
that.
B
We've
got
a
docker
file
to
generate
witness
nodes,
fat,
node
and
test
nets
in
there
and
we're
sort
of
still
checking
over
that
we've
done
this,
the
steam
dial
rename
and
we're
we've
done
most
of
the
work
for
rebounding
rebranding
the
code
base.
This
is
basically
going
in
and
replacing
steam
with
hive
etc.
In
the
code,
we've
got
one
more
change.
We
want
to
make
associated
with
that,
but
we're
kind
of
holding
off
on
that
change
until
some
other
changes
get
done
because
it's
likely
to
cause
conflicts.
B
C
C
B
I
guess
one
more
thing
is
the
image
server.
The
image
server
stuff
is
mostly
done
at
the
infrastructure
level.
The
only
thing
left
that
we're
really
working
on
now
is
how
to
safely
mirror
the
the
final
data.
That's
in
the
file
storage,
the
file,
server
storage,
so
that
we
can
have
that
distributed
well
across
a
bunch
of
nodes,
and
I
guess
ultimately
our
idea
is
that
once
that's
set
up
properly,
someone
could
just
register
themselves
to
be
a
backup
data
source
and
they
would
basically
get
pushed
the
the
image
server
data.
A
Sadly,
this
was
recommended
by
sergio,
which
is
not
here
today,
but
I
guess
this
is
a
good
discussion
to
have.
How
much
should
we
want
to
to
offload
off
hivemind?
In
my
opinion,
I
think
it's
a
it's
a
great
way.
To
I
mean
there
is
no
harm
in
just
trying
to
get
as
much
out
of
simply
and
as
much
on
hivemind.
B
Yeah
for
sure
I
totally
agree,
so
I
guess
in
terms
of
organization
there's
probably
I
guess
at
least
two
sort
of
roles
I
would
see
in
that
for
an
api
working
group.
We
need
one
of
basically
people
who
are,
I
guess,
specifying
out
what
kind
of
apis
we
want
to
support
and
that's
going
to
come
primarily
from
the
apps
side
of
things,
obviously,
from
the
front
ends
for
the
for
the
posting
and
things
like
that,
but
from
I
suppose,
other
other
apps
as
well.
B
So
certainly
my
group
can
be
involved
in
that
and,
like
I
said,
there's
this
other
guy
who
seems
to
be
interested
in
doing
that
too.
So
he
should
probably
be
pulled
into
the
api
working
group
as
well.
That's
his
handle
is,
I
am
s-w-a-t-I,
but
I
haven't
talked
to
him
or
anything.
I
don't
know
if
anyone
else
has.
I.
B
A
A
For
instance,
we
at
steampress
use
a
ton
of
calls
to
hyphen
to
render
our
comments
section
and
out
of
hybrid.
We
don't
use
that
much
data,
but
it
would
be
really
nice
if
we
could
have
have
mine
kind
of
the
same
way
as
steam
node,
where
you
can
load
more
or
less
data
depending
on
your
use
because,
for
instance,
icon
history
would
be
really
useful
to
have
in
the
high-fined
layout,
okay,
sql
able,
but
not
even
but
it's
a
huge
amount
of
data.
A
A
A
B
Yeah
yeah.
No,
that's
that's
an
interesting
idea,
so
I
guess
what
we'd
want
to
do
to
do
something
like
that
would
start
off
by
categorizing
the
apis
in
terms
of
what
tables
they
needed
access
to,
what
data
needed
to
be
put
into
the
database
for
that
so
sort
of
an
organization
of
the
of
the
hive
mind
api.
I
suppose.
C
A
Storing
that
much
data,
it
may
be
more
worth
it
to
use
like
radius
or
something
else,
not
really.
Sorry,
it's
it's
the
one
in
ruby.
I
don't
remember
the
name
yeah.
Perhaps
we
should
also
explore
other
database
engines
to
see
if
some
are
more
fits
for
some
more
use
cases,
because
I
don't
know
how
metroidscape
really
thought
out
hyphmine
and
the
in
terms
of
optimizing,
the
calories
et
cetera
but
yeah.
So.
B
B
B
A
A
B
A
B
C
Yes,
this
is
huge
work,
but
it
allows
it
will
allow
us
to
make
to
clean
up
the
code
and
really
oh
yeah,
make
simpler
other
changes,
because
this
idea
is
very
easy
but
constructed,
and
sometimes
it's
redundant
to
other
apis
generally.
We
should
eliminate
it
and
definitely
avoid
using
in
third-party
libraries
and
front-end
applications.
So
I
I'd
like
see
this
change
as
the
first
one
in
redesigning
apis,
which
is
a
complex
process
and
other
changes.
Probably
we
need
much
much
further
and
much
more
analysis
and
design
also
together
with
front-end
guys
and
librarians
maintainers.
B
Is
we
look
over
what
what
the
apis
are
that
are
currently
being
used,
not
only
ones
we
want
to
add,
but
what
we've
currently
got
and
how
we
can
swap
over
those
that
are
using
portions
of
those
api
that
are
condenser
api
and
into
something
else
so
find
out.
If
we
need
to
add
a
new
api
to
support
that-
and
I
mean
we've
got
an
issue
for
that-
and
people
have
already
started
working
on
it.
But
it's
it's
probably
worth
a
group
discussion
as
well
in
text.
A
Yeah,
it
would
be
interesting
to
roll
out
sequencer
appear
in
over
several
folks,
so
that
we
can
like
deprecate
x,
like
one
set
of
calls
and
another
set
of
calls.
That
way.
There
isn't
like
a
huge
strain
on
the
apps
like
every
if
they
just
have
to
to
migrate,
only
a
part
of
their
app
and
then
that
should
be
shouldn't
put
asthma.
B
So
you're
suggesting
doing
I
mean
well,
I
guess
there's
I
I
guess
you're
talking
about
apis-
that
don't
have
an
immediate
replacement
right,
yeah
yeah,
so
I
mean
the
first
thing
to
do-
is
sort
of
identify
and
change
everything
that
has
an
immediate
replacement.
So
we
sort
of
need
somebody
to
just
go
through
and
say
this
api
should
be
complete.
This
condenser
api
should
be
completely
replaceable,
so
you
shouldn't
be
using
it.
So
you
should
have
a
list
of
all
the
apis
that
no
one
should
be
using
because
there's
a
easy
replacement
right
now.
B
B
A
A
But
perhaps
we
could
try
to
find
a
replacement
and
optimize
it.
I
mean
create
a
replacement,
but
that's
for
another
call,
so
the
chain
id
swap.
We
already
spoke
a
bit
about
it,
but
I
guess
we
should
just
like
enforce
testing
as
much
as
possible.
It
would
be
great
to
write
up
a
post
to
explain
to
all
the
the
up
owners
what
it's
and
what
it
entails
and
what
they
should
do,
although
it's
easy
like
just
test
against
it,
that's
not
bad,
but
I
assume
well,
we
really
as
a
core
team.
B
Yeah-
and
it's
I
mean
mostly
yeah-
it's
mostly
the
libraries
themselves
right,
that's
what
we
need
to
change.
Any
library
that
does
transactions
is
essentially
what
needs
to
change.
If
your
library
doesn't
actually
create
transactions,
it's
not
an
issue
but
but
for
like
hybjs
and
d
steam,
and
you
know
for
the
other
ones
as
well.
The
python
libraries
for
example,
so
we
just
kind
of
need
every
library
guy
to
if
he
has
a
you
know,
indicate
drop
his
his
note
on
the
drop
a
note
on
the
the
top
level
issue.
A
B
A
Okay,
great
and
now
the
weekly
discuss
ongoing
issues,
blah
blah
blah.
Let
me
go
over
okay,
so
first,
this
is
it's
good
that
I
have
you
breakfast,
because
I
noticed
that
the
hive
development
funds
payout
are
slightly
wrong.
There
is
like,
I
think,
it's
like
a
precision
issue,
if
you,
for
instance,
if
you
look
at
nature's
profile,
he's
earning
six
stops
240
hpd
per
hour,
even
though
his
proposal
is
at
150
hpd
and
basically
it's
like
off
by
a
very
tiny
amount
and
so
yeah.
B
A
B
B
A
A
One
issue
is
that
it
might
become
a
commodity
and
then
people
will
sell
stuff
and
it
kind
of
loses
its
original
purpose,
but
at
the
same
time,
it's
quite
useful
to
be
able
to
just
send
it
to
people
like,
for
instance,
I
have
quite
a
few
that
I
don't
use,
and
I
and
I'd
rather
just
give
them
to
pharisim
for
his
hive.
Invite
system
and.
B
B
A
B
A
Yeah
the
issue
that
right
now
pretty
much
everyone
is
just
claiming
them
because
they
can
and
yeah.
Perhaps
it's
just
a
social
issue.
I
mean
it's
yeah.
Perhaps
it
shouldn't
be
solved
with
the
code
and
also
if
we
make
them
transferable
and
then
they
get
as
they
become
they
get
a
value.
Basically,
because
I
I
guess.
A
B
A
Some
discussion
on
power
down
time
still
not.
I
guess
this
needs
its
color
in
itself,
basically
reduce
it
to
four
weeks
or
the
whole
proposal
by
steemit
did
back
in
the
days
to
have
a
thing
where
you
you
can
lock
for
as
long
as
you
want
and
the
longer
you
lock
the
more
return
you
get
stuff
like
this.
B
A
A
B
B
A
B
Active-
and
so
I
I
actually
threw
in
an
issue
for
that
already,
because
I
really
think
that's
useful
it'll
solve
some
problems
for
the
front
ends
just
kind
of
a
side
thing.
I've
I've
been
looking
at
the
the
implementation
of
how
proposal
are
displayed
in
hive.blog,
and
I
really
don't
like
it
at
all.
B
One
of
the
things
I
found
really
annoying
was
it
was
very
difficult
to
see
proposals
that
aren't
yet
active
because
they
basically
show
up
at
the
very
very
bottom
yeah
exactly
so
yeah,
I
think
there's
some
changes
that
need
to
be
made
there
both
the
front
end
and
the
back
end.
Another
thing:
that's
that's,
really
been.
B
The
one
that
really
occurs
to
me
is
when
you're.
When
you
look
at
a
proposal
there's
you
may
have
never
viewed
a
proposal
before
so.
A
negative
vote
has
some
more
meaning.
In
my,
in
my
opinion,
it
means
you've,
read
the
proposal
and
voted
against
it,
whereas
voting
for
everything
and
not
voting
for
that
proposal
is
not
the
same
thing
in
my
mind.
I
think
they're
very
different
things.
B
B
A
I
see
all
your
points
and
I'm
still
on
the
fence
with
it,
because
it
basically
increases
the
well
and
the
on
one
hand.
It
would
also
be
allowed
to
have
the
return
proposal
to
be
lower,
because
that
means
you
can
have
like
you
can
have
an
easier
access
and
proposals
that
are
considered
by
the
community
will
get
them
voted.
B
B
A
B
B
B
B
A
A
A
B
C
C
I
can
see
that
some
people
object
some
some
other
folks
amount
of
money
per
day
paid
out
or
requested
to
be
paid
out.
So
then
what
one
could
do
is
make
four
proposals
for
the
same
thing
right,
so
you
can
make
one
okay.
I
did
this
or
I'm
doing
this
and
I'm
asking
ten
dollar
per
day
and
then,
but
if
you
think
it's
worth
twenty
dollar,
I'm
asking
20,
so
you
make
five
proposals,
but
another
thing
could
maybe
be
that
the
community
could
vote
on.
C
A
Think
it's
a
good
idea,
just
to
say:
okay
I'll
spend
like
10
hours
a
week
on
this,
but
if
you
fund
me
to
this
amount,
I'll
spend
20
hours
et
cetera,
I
think
it's
an
interesting
idea,
but
then
how
you
you
would
have
like
several
like.
Let's
say
you
have
oh
yeah,
you
could
have
like
kind
of
like
a
a
patreon
thing
where
you,
if
you
pass
a
certain
threshold,
then
you
get
to
this
much
to
this
much
funding.
C
C
A
A
C
B
So-
and
I
mean
it
also
depends
a
little
bit
on
the
nature
of
the
the
proposal.
Is
you
know
you?
You
obviously
can't
just
cut
it
off
early
if
it's
continuing
work
and
they
can
just
stop
so
yeah
I
mean
it.
I
mean
I
don't
know
that
there's
not
possible
to
do
this
now
right
I
mean
somebody
can
make
a
proposal
and
it's
not
voted
in
and
then
they
can
make
another
proposal
to
lower
them
out
and
see
if
that
gets
voted
in
right
I
mean
I
I
mean
generally
in
a
negotiation.
A
B
A
B
A
B
A
What
else
I
think
a
great
thing
about
this
would
be
inertia
who
did
a
proposal
who
got
funded
a
free
time
for
his
documentation
proposals
and
did
one
at
500
and
people
did
not
agree.
Sent
did
one
at
200
and
people
still
did
not
agree,
but
I
think
people
still
agree
for
100
and
I
think
it
would
be
a
great
use
case.
B
A
A
Yeah,
you
know
you'd
know
me
yeah.
I
think
I
I
think
crimson
is
right
when
she
says
it's
like
a
cultural
issue
when
you
set
it
and
forget
that
not
that
many
people
are
reviewing
proposals,
I
think,
on
the
frontend
side,
we
should
try
to
have
perhaps
some
notifications
about
like,
oh
by
the
way
you
there
is
a
new
proposal
that
came
up.
Do
you
want
to
review
it
or
things
like
this?
B
Well,
I
mean
we
have.
I
think
the
notification
is
other
people.
If
somebody
thinks
that
someone's
not
doing
the
job,
then
I
think
it's
somebody's
responsibility
to
raise
the
issue
and
and
then
it
happens
right
I've
I've
seen
that
happen.
A
couple
times
someone's
said:
hey
this
guy's
not
really
doing
the
work.
Why
are
we
voting
for
him?
I
mean
yeah.
No,
no.
I
mean.
B
Arguing
there's
lots
of
there's
all
these
people
are
voting
for
small
proposals.
I
mean
voting
proposals,
never
paying
any
attention,
but
I
don't
know
that
a
lot
of
that's
going
on.
I
mean
I
think
the
most
interesting
case
is
the
case
where
the
the
front
end
app
actually
says.
Would
you
like
to
vote
for
my
proposal?
A
B
B
B
A
Yeah
cool
yeah,
because
then,
if
we
allow
a
month
that's
as
for
june
and
then
half
of
25
will
do
a
ton
of
changes,
so
I'm
mostly
thinking
that
way,
because
I
think
we'll
try
to
get
smt
for
household
26
or
27,
and
if
each
hard
fork
takes
like
several
months.
We
want
to
try
to
get
this
one
as
fast
as
possible
and
also
get
to
hard
fork
25,
which
should
allow
for
much
more
changes
like
rc
delegations.
B
A
B
A
A
A
Okay,
well
see
you
in
oh,
since
it's
perfect
because
next
time
it's
in
two
weeks,
that's
one
week
before
the
code
freeze
excellent
time
third
year.
It
is
one
of
soft
requirements.
Yes,
that's
interesting,
because
I've
been
hearing
the
30
days
after
freeze
a
lot
of
times,
and
do
we
really
need
do
they
really
need
30
days
just
to
update
the
node.
B
B
A
Yeah,
probably
hopefully
that
would
be
enough,
because
two
weeks
is
like
much
more
lean
in
terms
of
upgrades
so
that
we
don't.
We
are
not
like
oh
yeah,
so
if
we
got
freeze
now,
then
it
takes
like
a
month
and
then
we
can
like
start
to
think
about
the
next
one,
that's
kind
of
a
tough
requirement
but
yeah.