►
From YouTube: Core dev meeting #51
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
Awesome
a
new
month,
a
new
recorded
meeting.
So
in
my
end
thank
you
for
the
review
biotech,
so
the
one
of
my
old
Hive
Minds,
merge
request
has
been
merged,
so
an
old
bug
is
about
to
be
fixed.
Whenever
we
release
it
I'm
not
quite
sure
what
the
release
schedule
is
for
hive
mind,
but
it's
like
low
priority.
A
So
whenever
you
guys
are
ready
on
top
of
that,
I
started
looking
at
documentation
a
bit,
because
Crimson
has
been
telling
me
that
it's
been
communicated
for
her
to
onboard
new
devs,
because
new
devs
are
confused
by
our
the
state
of
our
documentation
because
it's
been
done
by
inertia
a
while
ago
now,
selecting
to
it
and
I
wanted
to
touch
base
on
that
with
your
Gandalf
because
from
where
in
the
studio
are
also
looking
into
it
yeah.
So
that's
kind
of
my
points
for
other
thing.
A
I'm
going
to
submit
my
funnel
I
have
a
bunch
of
code.
You
know
locally
that
I
haven't
pushed
but
I'm
going
to
submit
the
the
communities
type
student
3,
probably
this
week
for
review
about
like
it's
mostly
test
and
test
at
this
point.
B
Okay
sounds
good,
so
you
mentioned
release
schedule,
so
it's
very
appropriate
since
I
think
we're
going
to
have
a
release.
We're
gonna
do
a
release
candidate,
probably
this
week,
for
just
about
everything:
I
guess
so
that
means
hobd
half
and
pretty
much
all
the
half
apps
and
some
of
the
other
new
apps
as
well.
Hopefully
so
the
release
candidate
will
come
out
like
I
said
this
week
sometime
and
then
we're
aiming
to
actually
do
an
official
release
around
the
end
of
the
month.
B
So
in
the
meantime
you
know
we'll
basically
solicit
people
to
start
trying
to
try
it
out
and
we'll
run,
run
it
on
production
tests
and
we'll
also
be
doing
performance
benchmarking
and
things
like
that
during
the
coming
during
this
month.
B
So
as
far
as
well,
I
guess
I
put
out
a
post,
that's
in
previous
posts
that
have
really
documented
I.
Guess
everything
that's
going
into
the
new
release,
but
we'll
also
create
a
you
know,
an
issue.
A
list
of
release,
features
too
along
with
that,
when
we
do
the
release
candidate,
so
I
guess
in
terms
of
things,
I
could
think
of
that
are
probably
the
biggest
changes.
B
One
would
be
in
in
half
that
we've
got
the
we're,
storing
the
operations
in
boundary
format,
so
I've
been
encouraging
anybody
who's
doing
half
development
for
a
while
to
use
the
development
version.
So
finally,
we'll
be
to
the
point
where
they
can
use
the
master
version.
I
think
without
you
know
having
to
necessarily
use
the
developed
version
for
everything
beyond
that
we've
also.
B
Another
thing:
that's
kind
of
important
is
that
we've
created
new
record
types
for
all
the
blockchain
operations
in
half
and
there's
the
idea
behind
this
is
first
of
all,
it
makes
it
more
performant.
So
it's
sort
of
like
a
best
practices
way
to
create
your
half
app.
You
wouldn't
necessarily
have
to
use
them,
but
it's
extremely
well
extremely
highly
recommended
that
you
do.
B
It'll
also
make
your
app
easier
to
combine
with
other
half
apps,
so
I
guess
it's
probably
been
a
while
since
I
talked
about
this
idea,
so
maybe
just
to
mention
again
the
whole
one
of
the
driving
forces
between
behind
half
really
was
the
was
that
we
were
looking
at
the
beginning
at
how
to
improve
the
API
of
Hive.
So
this
is
also
I.
Guess
significant
in
terms
of
talking
about
documentation,
and
so
the
idea
I
kind
of
settled
on
was
that
we'd
move
most
of
the
API
development
outside
of
Hive.
B
It's
a
hive
D
itself
and
into
this
into
basically
half
apps.
So
the
idea
is
Hive
pushes
all
the
data
into
into
a
half
database
and
then
we
can
create
whatever
kind
of
apis.
We
need
with
that
data,
and
it
gives
us
a
lot
of
flexibility.
So,
on
the
one
hand
it
means
you
can
create
your
own
custom
API,
but
on
the
other
hand,
it
also
means
that
we've
got
a
way
that
somebody
can
basically
create
an
API
and
then
provide
it
to
other
people.
B
So
as
an
example
that
we
created
this
balance,
Tracker
app,
which
you've
been
improving
recently-
and
it
gives
basically
an
entire
new
API
for
doing
things
like
graphing
a
balances
of
an
account
over
time,
for
instance,
something
that
before
was
you
basically
had
to
do
all
the
work
yourself.
No
decent
amount
of
work
to
do
we're
also
creating
a
similar
API
for
the
block
explorer
that
we're
creating.
B
So
the
block
explorer
that
we're
developing
is
can
be
divided
into
two
parts:
there's
the
API,
which
is
a
half-based
app
and
then
there's
just
a
UI
that
runs
on
top
of
it
that
actually
uses
that
API,
but
that
API
can
be
used
by
anybody
who's,
developing
a
block
Explorer
or
just
anybody
who
wants
to
make
some
of
the
calls.
The
API
calls
that
are
available
in
that
block,
Explorer,
API,
app,
so
I
hope,
that's
clear
as
to
why
why
half
I
think
is
really
important.
It's
really
our
next
Generation
API.
B
In
many
ways
it's
just
a
and
it
basically
redefines
the
flow
of
how
we
create
our
API.
In
the
past,
the
API
was
kind
of
a
very
centralized
process
to
change
it,
because
all
the
changes
had
to
be
made
at
The
Hive
D
level,
which
is
sort
of
the
most
security
sensitive
area.
Whereas
now,
basically,
anybody
can
create
a
new
API
that
tap
that
they
plug
in.
On
top
of
a
half
I
mean
on
top
of
Hive,
just
using
half
app
to
do
it
and
we've
seen
a
couple.
B
People
do
that
just
recently,
matayari
in
fact,
basically
created
a
sort
of
a
a
similar
tool
to
The
Hive,
SQL
app,
which
basically
gives
us.
You
know
a
new
API
as
well
and
also
in
lotsy
created
one
for
notifications,
so
I
hope
that's
clear
as
to
why
I
think
this
is
really
important
for
us.
B
This
idea
that
anybody
can
now
add
and
modify
the
API
itself
if
they
want
to,
and
they
can
change
its
characteristics
for
performance
or
for
ease
of
use,
whatever
they
need
so
anyways
I,
guess
that's
the
gist
of
what
we're
doing
I
guess
in
terms
of
half
the
other
things
that
have
been
done
recently,
we
made
some
more
bug
fixes
and
improvements
aimed
at
easing
the
life
of
the
node
operators,
so
we've
been
making
changes,
the
block,
block
log
tools,
improvements
to
the
replay
and
sync
process,
and
we
also
got
a
couple
new
apps
that
will
also
be
released
as
part
of
this,
this
upcoming
release
we
have
The
Beekeeper,
which
is
essentially
a
new
way
to
manage
keys
and
also
to
create
transactions,
and
we're
hoping
this
will
be
like
a
a
library
that,
basically,
everyone
can
use
going
forward.
B
So
we'll
have
a
a
very
small
footprint
very
well
audited
way
of
people
can
use
to
anybody's
building
app,
can
generate
transactions
and
sign
them.
So
it
was
really
two
versions
of
beekeeper
one's,
a
C
plus
plus
based
app,
and
that's
really
for
essentially
just
desktop
applications,
and
then
we've
also
got
a
new
tool,
we're
creating
now
beekeeper
wasm,
which
is
basically
a
version,
a
web
assembly
version
of
beekeeper.
B
So
you
can
run
it
inside
a
inside
a
browser
and
I
think
that'll
be
really
interesting
for
anyone
who's,
creating
Java
based
apps
with
hive
beyond
that,
we
also
got
two
other
apps
that
we're
creating
right
now,
Clive,
which
is
a
replacement
for
the
CLI
wallet.
That's
been
around
for
ages
and
really
hasn't
been
done
much
to
in
a
while.
So
we've
been
just
basically,
it's
been
on
maintenance,
and
so
Clive
is
basically
a
much
easier
to
use
version
of
that.
B
B
This
is
essentially
a
totally
new
app
that
just
models
the
look
and
feel
of
condenser,
but
is
using
more
new
technologies
and
we're
trying
to
develop
something.
That's
much
easier
to
maintain
and
both
of
those
are
proceeding
pretty
well.
I.
Think
we're
going
to
include
some
version
of
Clive
in
the
new
release.
Denser
is
really
a
little
more
separate,
so
I
don't
know
if
we'll
see
a
release
for
that,
probably
not
so
that's
kind
of
what
we've
been
working
on,
oh
and
since
how
I
mentioned
his
improvements
to
the
community
roles
feature
yeah.
B
B
C
I
had
a
question
about
the
apis
or
basically
like,
following
on
from
what
you
said:
I
got
wants
to
see
feedback
about
potential
new,
like
an
additional
layer
to
everything
you
just
said
about
the
apis
and
the
flexibility
of
sort
of
empowering
the
devs
to
to
create
their
own
API,
how
how
they
want
it,
and
this
is
the
sort
of
basic
I
guess
principle
of
it
would
be
more
robust
if,
if
there
was
like
many
small
apis,
like
even
yeah.
B
That's
that's
exactly
the
intent
of
half.
In
fact,
I
used
to
call
half
of
the
original
origin
I
used
to
call
it
modular
High,
mind
which
was
the
ad
and
I
think
I
might
have
stole
the
name
from
Ohio,
but
the
idea
behind
it
was
Hive
man
had
this
really
large
API
of
all
these
different
various
somewhat
unrelated
API
calls,
and
so
we
wanted
to
have
a
way
that
you
could
basically
create
apps.
We
would
have
smaller
sets
of
apis
that
you
could
decide.
B
I
want
to
support
these
apis
on
my
half
server
and
now
then
I'll
run
this
app.
So
basically,
by
choosing
what
apps
you
run
on
your
half
server,
you
essentially
decide
what
what
apis
you
want
to
support
on
you
on
your
server
and
then
you
know
you
can
either
make
that
a
Publix
half
server,
that
other
people
can
use
the
apis
on
or
you
know,
if
you're
doing
your
own
private
server
for
your
application,
you
could
just
pick
and
choose
which
ones
which
apis
you
need
to
support.
C
Yeah
yeah,
absolutely
yeah
yeah.
That's
that's
really
great
and
I
guess
where
I'm
going
with
this
is
potentially
in
order
to
reduce
the
the
server
itself
like
the
in
terms
of
Hardware
needs,
because
right
now
you
have
to
have
in
order
to
have
half.
You
have
to
also
run
type
D,
which
creates
its
own
server
requirements.
C
So
if
there
was
a
way
to
sort
of
have
very
tiny
for
Hardware
requirements
and
provides
an
API,
and
so
you
could
stop,
you
know
a
large
number
of
apis
in
addition
to
it's
like
just
an
additional
layer
and
child
that
could
be
done,
potentially
as
if
there's
like
a
standalone
database
posner's
database
that,
like
queries,
full
half
note
and
just
gets
in
real
time
only
the
blockchain
data
that
it's
interested
in.
Let's
say
only
this
type
of
custom
Json
or
something
like
that.
C
C
Yeah
yeah
right
so
I
guess
I
wanted
to
see
if
like
if
this
makes
sense
and
if
this
would
fit
well
with
what's
planned,
forecast
because
I
know,
there's
yeah.
B
I
mean
essentially
like
I,
said
what
you're
talking
about
really
is
is
even
possible
now,
because,
when
somebody's
running,
an
API
node
operator
is
running
a
server,
if
he's
running
I
mean
there's
still
some
Legacy
stuff.
But
if
he's
running
the
latest
stuff,
then
he's
already
running
a
half
database.
That's
you
know
already
got
a
huge
amount
of
data
and
he's
probably
he's
running
a
you
know.
It's
got
all
the
data
for
half
for
basically
all
the
account
history
API,
for
instance,
so
you
could
then
create
another.
B
B
It
was
I
guess
the
issues
I
would
see
right
now
with
doing
that
is
if
it
wasn't,
if
you
did
it
without
half
technology
back
in
your
own
local
database,
and
maybe
this
is
something
I
want
to
think
about,
because
the
thing
about
having
it
backed
by
using
half
as
the
database
rather
than
just
using
a
generic
database,
is
that
in
the
case
of
forking,
if
you're
running
a
half-based
database,
it'll
automatically
Fork
back
to
you
know,
everything
will
revert
to
the
the
right
version.
B
You
won't
run
into
a
consistency
problem,
whereas
if
you,
if
you're
just
querying
a
half
server
to
get
the
data
from
it
than
when
a
fork
happens,
the
data
changes
on
a
half
server,
but
you,
your
database,
wouldn't
necessarily
know
that
that
data,
the
past
data
you'd
fetched,
had
changed
due
to
the
fork.
So
that
could
be
one
one
particular
issue
with
the
implementation
you're
describing
versus
just
running
a
full
half
app
yeah.
D
B
I'll
have
to
think
about
that
see
if
there's
something
we
could
do
to
mitigate
that,
that,
of
course,
and
if
you're,
working
and
you're,
if
you're
working
in
irreversible
mode,
that's
not
an
issue.
So
if
your
app
is
only
getting
data
after
it's
irreversible,
then
that's
not
a
problem
at
all,
and
that's
frequently,
that's
probably
just
fine
I
think
now
you
know
when
we
developed
half
originally
handling
reversible
data
was
much
more
important
because
it
took
a
while
for
data
to
become
irreversible,
but
once
we
introduced
the
one
block
your
reversibility
feature.
B
D
C
Yeah,
that's
what
I
was
thinking
because
of
the
other
one
blocking
irreversibility.
It's
basically,
the
API
can
provide
the
blockchain
data
in
real
time,
even
though
it's
just
it,
it
queries
just
the
irreversible
yeah.
B
Yeah,
it
still
look,
I,
don't
think
anybody.
You
know
in
general
usage
they
wouldn't
even
notice
the
difference.
The
only
time
that
might
come
up
is
would
be
in
case
of
a
large
fork,
for
you
know
a
number
of
blocks,
but
that's
that's
extremely
rare
nowadays,
generally,
you
must
see
one
block.
You
know
that
gets
gets
reverted.
C
B
I
think
that
would
be
best,
I
mean
it
it
to
me.
It
makes
sense
if
we
use
the
same
tools,
it
makes
it
easier
for
the
devs
to
move
back
and
forth
between
projects.
D
B
And
that's
one
of
the
things
that's
one
of
the
thrusts
we've
actually
had
with
half
is
we're
moving
more
and
more
towards
trying
to
make
sure
that
if
you
develop
your
half
app,
you've
got
like
a
best
practices
way
to
do
it.
That
makes
it
easier.
If
you
go,
look
at
somebody
else's
half
app
and
understand
it,
and
also
to
that
you're
doing
it
the
best
way.
Essentially,
you
know
doing
a
way.
That's
most
performant.
C
Well,
ideally,
it
would
be,
you
could
even
take
the
code
and
directly
make
it
into
a
half
app
yeah.
B
Absolutely
yeah,
yeah
yeah,
and
so
one
of
one
of
the
things
I
think
the
most
important
things
we
did
recently
in
terms
of
half
other
than
the
binary
was
this
idea
of
creating
these
record
types
that
basically
they're
just
SQL
record
types
that
Define
the
blockchain
operations
in
a
standardized
way?
So
if
you
do
that,
if
you
use
those
for
for
your
database,
then
it'll
be
easier
to
you
know
to
make
it
into
a
half
app
and
to
exchange
data
with
another
with
a
half
app
too
another
half
app
foreign.
B
B
Okay,
so
yeah
I
guess
that's
any
other
questions
about
any
of
this
stuff.
Any
I
mean
I.
Had
some
people
privately
ask
me
about
denser
and
things
like
that.
But
I
don't
know
if
anybody
has
any
questions
about
it
or
if
it's
a
clear,
why
we're
doing
it.
A
D
D
From
my
side
either,
but
we're
excited
to
see
the
release
candidate
and
then
hopefully
the
release
by
end
of
month,
so
keep
up
the
great
work
guys
thanks
appreciate
it.