►
From YouTube: Community Development Call #13
Description
Join the Regen Network Development Team for weekly calls open to the public. Led by Chief Technology Officer Aaron Craelius, these calls are designed to update our development community on the latest product news (approximately 30 min), and engage our network in a Q&A (approximately 30 min). We look forward to seeing you there!
When: Biweekly
Where: https://zoom.us/j/9998884567
Duration: 1 hour
Connect with our community 👇
• Website: https://regen.network
• Twitter: https://wwwtwitter.com/regen_network
• Facebook: https://www.facebook.com/weareregennetwork
• Telegram: https://t.me/regennetwork_public
• Medium: https://medium.com/regen-network
• GitHub: https://github.com/regen-network/
• LinkedIn: https://www.linkedin.com/company/regen-network
• Reddit: https://www.reddit.com/r/regen_network/
A
And
their
upgrade,
that
is
going
to
be
happening
soon,
to
switch
the
binary
to
0.53
I
set
the
voting
window
to
six
hours,
which
will
allow
testing
emergency
upgrades.
There
is
proposal
number
five
that
is
now
in
progress,
and
so
please
vote
on
it.
If
you
haven't
done
so
already,
and
here's
some
important
links
on
the
the
binary
release
is
is
blanked
here.
A
Some
information
on
the
upgrade
and
instructions
with
upgrade
are
links
here
and
everybody
I
remember
that,
once
the
darién
gap
is
crossed
once
this
upgrade
happens,
there
will
be
an
emergency
on
de
subject.
So
yeah
everybody,
you
know,
stay
on
top
of
the
communications
and
let's
make
this
these
next
two
upgrades
really
quick
and
really
successful.
A
Updates
on
the
registry
later
we
have
made
the
magpie
release
where
buyers,
ecological
credits
can
understand
what
a
project
is
about
and
purchase
credits
offline
and
confirm
the
purchase
of
credits
online
and
basically
there's
the
detailed
page
version.
One
that's
complete
with
the
project
the
project
listing
page
is
designed
and
the
blockchain
integration
is
starting
soon,
and
here
you
see
a
screenshot
of
basically
the
project
listing
page,
that's
in
progress,
so
we're
excited
about
the
progress
on
that
and
we
don't
actually
have
any
science
updates.
A
This
week,
I've
heard
from
gizelle
a
few
updates
on
the
key
management
grant
that
we've
been
working
on
message.
Authorization
is
almost
ready,
there's
just
a
few
small
things
that
are
beans
about
before
we
mark
that
ready
for
review.
We
created
an
ORM
package
for
those
of
you
that
aren't
familiar
with
the
concept
of
ORM
s.
Orm
means
it's
object,
relational
mapping.
A
We
now
have
a
framework
for
doing
that.
Generally.
We
are
also
going
to
use
that
internally
for
issuing
the
fractional
and
of
T's
that
we
will
use
for
the
use
of
some
service
credits,
so
that
package
is
ready
to
be
used
and
work
on
the
actual
group.
Module
will
begin
soon.
There's
some
work
on
it,
that
is,
is
in
the
tests
for
the
ORM
module,
but
kind
of
the
work
in
earnest
on
that
modules
will
begin
soon.
I
apologize
for
the
delay
that
there's
been
on
this
I
know.
A
Many
people
have
been
waiting
on
this
for
a
while
and
yeah.
We
are,
you
know,
getting
getting
close
to
it,
being
it
being
ready,
so
we're
hoping
for
by
the
end
of
February
having
this
ready
for
review,
hopefully
sooner,
hopefully,
once
now
that
we've
got
things
kind
of
a
few
things
on
blocks
that
I
in
the
next
weeks,
or
so,
we
have
something
that's
ready
for
review
so
also,
there's
still
some
ongoing
work
on
the
upgrade
module.
These
are.
A
These
are
upgrades
to
that
to
the
basic
upgrade
functionality
to
handle
different
edge
cases
that
we
came
across.
So
this
one
that
I
has
just
recently
finished
allows
for
multi
store
upgrades,
which
are
basically
renaming
the
different
sub
stores
that
are
used
in
different
modules
within
the
cosmos
SDK
or
for
deleting
modules.
A
A
So
with
this,
with
this
multi-store
upgrade
feature
that
would
handle
that
sort
of
edge
case.
There's
still
a
couple
things
to
do
on
the
on
the
upgrade
module,
but
mostly
mostly
pretty
small,
it's
our
brushes
that
it's
pretty
much
there.
It
handles
all
the
basic
functionality
and
some
edge
cases.
The
one
big
thing
that
is
is
so
in
progress,
which
I
see
is
as
happy
be
related
to
upgrades,
is
the
perturb
of
migration
work,
which
is
happening
for
both
the
cosmos,
SDK
and
tender
mint,
and
we're
pretty
heavily
involved
in
that
and
supporting
that
work.
A
A
If
there's
certain
changes
to
the
tender
mint
block
structure
because
of
the
the
way
immuno
encodes
things
they're,
breaking
changes
in
the
transaction,
history
and
protobuf
makes
this
much
easier
to
track
and
to
basically
have
a
check
during
a
continuous
integration
testing
that
the
format
of
what's
in
on
this
in
state,
the
the
block
structure
isn't
breaking.
So
we're
really
excited
to
move
that
along
and
that
should
I
give
us
a
much
more.
Our
hope
is
that
that
gives
us
a
much
more
stable
ecosystem
going
forward.