►
From YouTube: Cosmos Community SDK Development Call 9/9
Description
Welcome to the monthly Cosmos SDK Community of users call. Lead by the Regen Network Engineering team, we meet each month to review the technical roadmap and get feedback from the community. This is a great place to connect if you are an engineer using the Cosmos SDK to build a blockchain, or are an engineer contributing to the Cosmos SDK itself. We welcome new users, veterans, and engineers just wanting to check things out and learn about the community.
Connect with our community 👇
• Website: https://cosmos.network/
• Twitter: https://twitter.com/cosmos
• Telegram: https://t.me/cosmosproject
• YouTube: https://www.youtube.com/c/CosmosProject
• Medium: https://blog.cosmos.network/
• GitHub: https://github.com/cosmos/cosmos-sdk
• Reddit: https://reddit.com/r/cosmosnetwork
A
Well,
I'm
thinking
it's
going
to
be
a
small
group
today,
which
is
sort
of
to
be
expected.
We've
been,
we
haven't,
been
publicizing
the
meeting
very
much,
but
I
wanted
to
use
you
all
as
guinea
pigs
for
a
new
way
of
conducting
this
meeting.
So
we've
created
a
a
shiny
new
road
map
system.
That's
going
to
be
public
facing
and
we're
just.
A
Moving
forward
on
sort
of
interactive
conversations
as
we
move
into
test
nets
as
we
move
into
people
building,
you
know
the
collaboration,
people,
building
applications
and
credits
and
all
of
the
rest
of
the
exciting
stuff
happening
with
with
regen
network.
So
without
further
ado,
and
with
your
permission,
I'll
I'll,
do
a
quick
screen
share
and
walk
you
through
the
road.
B
A
A
This
is
documented,
and
this
isn't
quite
public
yet,
but
we're
actually
going
to
embed
this
in
our
website,
so
everybody
will
be
able
to
see
it,
it'll
be
completely
public
and
then
we'll
use
it
as
the
basis
for
our
monthly
check-ins
moving
forward.
So
you
can
see
the
roadmap
is
broken
into
five
main
categories.
Region
ledger:
the
cosmos
sdk,
the
registry
for
credits
for
trading
and
retiring
credits
are
science
for
r
d,
which
is
mostly
grant
funded
to
do
verification
and
monitoring
stuff
and
then
open
team.
A
A
We
have
the
registry
and
we
have
science,
and
then
we
have
open
team.
So
each
one
of
these
is
a
simple
kanban
which
has
the
backlog
the
coming
soon.
What's
in
progress
and
what's
been
released,
so
you
can
see
with
region
ledger.
As
I
think
everybody
knows,
we
paused
work
on
regent
ledger
until
post
stargate,
so
our
engineering
team
is
strictly
working
on
stargate
right
now
and
then
we'll
start
moving
these
pieces
into
in
progress
as
we
have
more
bandwidth,
post,
stargate
release.
A
Moving
into
the
region.
Le
registry
there's
a
bunch
of
stuff
in
progress,
as
you
can
see,
and
we're
actually
in
the
process
of
populating
the
backlog
a
little
bit
as
a
team.
But
you
can
see
what
we're
working
on.
Is
this
sort
of
mvp
for
being
able
to
buy
and
retire
credits
and
a
credit
class?
That's
coming
any
moment
as
we
get
legal
sort
of
a
bunch
of
legal
work
done
for
for
all
of
that
on
the
sort
of
compliance
side
of
things,
which
is
very
exciting.
A
Science,
lots
of
stuff
moving
in
the
science
work
world,
so
we're
very
excited
to
be
automating.
The
monitoring
and
verification
process
for
our
first
go-to-market
credit,
which
means
that
we'll
have
this
open
source
pipeline
for
the
data
science
around
generating
these
credits.
That
will
then
live
on
region
ledger,
which
is
really
exciting.
A
So
that's
moving
and
actually
moving
very
fast
for
will
and
other
folks
in
the
open
team,
actually
we're
essentially
building
an
alternative
to
gibbs,
simply
because
gibbs
hasn't
really
been
available
and
there's
some
needs
that
we
have
in
terms
of
us
signatures
on
data
packages
and
other
things
which
aren't
really
reflected
in
that
architecture.
So
then,
we're
doing
sort
of
other
work,
mapping
out
future
methodologies
and
executing
some
work
on
grants.
A
Ecosystem
service
marketplace
consortium
report,
which
is
where
we're
sort
of
outlining
the
scientifically
robust
approach
to
soil
carbon
quantification
in
open
team,
we're
in
the
process
of
wrapping
up
all
three
of
these
work
packages.
Our
work,
paired
work
sessions
and
moving
them
into
work
packages
that
will
run
through
2021,
I'm
in
the
process
of
of
creating
a
a
draft
road
map
and
sort
of
billing
strategy
for
open
team,
in
collaboration
with
the
secretariat.
So
there'll
be
a
bunch.
A
This
will
sort
of
shift
and
evolve
and
we're
really
excited
about
what's
coming
next
in
open
team,
but
here
you
can
see
what's
currently
underway
so
yeah
that
was
just
a
quick
run
through
I'd.
Yeah
I'd
love
it.
If
you
know
just
people
have
reflections
or
comments
on
just
sort
of
presenting
our
work
in
this
way
and
having
a
living
road
map
where
you
can
sort
of
see
things
move
from
backlog
to
coming
soon
to
progress-
and
you
know-
and
hopefully
these
calls
will
start
to
be
dynamic.
A
Conversations,
for
instance,
about
region
ledger
mostly,
and
the
registry,
where
we
can
have
conversations
about
what
future
features
might
get
put
into
the
backlog
is
my
hope
of
how
these
calls
kind
of
evolve
over
the
coming
months.
So
yeah
I'll
take
a
pause
and
see
if,
if
folks
have
comments
or
questions
or
ideas.
B
Yeah,
I
can
comment
on
that.
So
personally,
I'm
a
person
who
loves
structure-
and
I
believe,
structure
is
important
for
everyone
to
better
understand
how
what's
happening
in
a
project
what's
happening
in
a
company
what's
happening
in
a
team
and
in
this
case
structuring
the
work.
That
region
does
so
clearly
on
like
different
projects,
that
a
team
is
working
on
and
making
sure
that
everyone
in
the
community
understands
exactly
what
the
focus
of
the
team
is
and
how
this
will
shift
in
terms
of
what
will
be
accomplished.
B
What
is
coming
soon,
what
is
finished
brings
a
lot
of
clarity
both
to
region
as
a
company
and
what
region
as
a
company,
does,
and
also
to
the
region,
as
as
a
team
and
understanding
more
on
what
the
team
is
currently
working
and
how
they
are
dividing
their
tasks
and
work.
So
we're
really
supportive
of
this
of
this
road
map
and
the
way
it
is
presented
like
this.
D
Yeah,
it
looks
good
to
me,
I'm
I'm
interested
to
poke
at
notion
a
little
bit
more
because
I
don't
know
I'm
always
looking
for
better
workflow
tools
and
it
looks
super
nice.
It
seems
like
it'll,
be
less
work
in
like
preparation
for
this
like
so
you
don't
have
to
be
generating
a
lot
of
like
boilerplate
or
like
generating
a
lot
of
different
presentations
that
are
kind
of
like
one-time
use
and
yeah.
It
seems
nice
people
can
track
things
on
their
own
kind
of
which
is
nice
too.
A
Actually,
so
you
can
just
pop
in
and
and
go
to
the
detailed
documentations,
all
the
ards.
All
the
poll
requests
are
right
there,
for
instance,
this
ecosystem
service
credit
module.
You
know,
okay,
you
can
just
pop
over
it's
because
I
have
most
people
wouldn't
have
edit
access.
That's
why
it
doesn't
just
link
but
okay,
you
pop
over
and
here's
this
rfc
for
the
ecosystem
service
credit
module,
which
is
what
we're
using
as
the
specification
for
that
work.
A
So
people
who'd
like
to
be
able
to
dig
into
the
documentation
it'll
just
be
right
there,
which
is,
which
is,
I
think,
very
as
adriana's
saying
it's
sort
of
the
foundation
for
generating
a
lot
of
clarity
and
specification
and
conversation
yeah.
So
my
hope
is
this
really
serves
to
just
clarify
and
get
in
a
rhythm
of
you
know,
just
just
a
lot
of
coherence.
B
So
this
is
more
of
over
organizing
tasks
rather
than
organizing
projects,
so
it
might
make
more
sense
to
find
a
way
to
identify
like
create
a
dashboard
for
each
project
and
then
link
a
general
dashboard
with
all
the
projects.
So,
for
example,
you
have
these
four
main
projects
and
when
you
press
on
one,
then
you
find
the
backlog
afferent
to
each
project.
So,
for
example,
I
don't
know
regional
ledger.
B
Region
ledger,
so
can
you
go
back?
So
if
you
go
back
here,
okay,
okay,
I
see
so.
Let's
say
you
have
like
the
credit
model
project.
Then
the
credit
model
has
a
dashboard
of
its
own
and
has
backlog
coming
soon
in
progress
and
release.
And
then
you
have
the
region
ledger
which
has
a
project
by
its
own.
And
then
you
have
the
open
team
which
it's
a
project
by
its
own
and
has
like
its
own
dashboard.
A
A
If
you
look,
for
instance,
you
know
so
this
is
the
cool
farm.
Perennials
module
within
open
team,
open
team
does
all
of
it
project
management
in
gitlab.
We
do
all
of
our
cosmos,
sdk
and
cause
and
region
ledger
and
github,
the
the
actual
backlogs
and
the
details
of
those
don't
live
in
notion.
They
live
in
gitlab
or
github.
So,
for
instance,
there's
this
board
that
you
can
see
in
terms
of
open
team.
A
You
know
these
are
all
the
things
that
are
going
on.
So,
if
you
switch
back
over
here,
what
we
tried
to
do
is
just
have
a
simple
overview
right,
because
this
is
quite
there's
quite
a
bit
going
on.
There's
multiple
teams,
there's
multiple
repositories
and
it's
sort
of
similar
to
the
cosmos
sdk,
where
there's
multiple
teams
working
and
it's
quite
complex.
A
So
what
we're
trying
to
do
is
create
a
simple
and
ack
visual
over
overlook,
but
we
can't
actually
the
amount
of
work
to
get
it
sort
of
like
fully
integrated
with
the
multiple
different
project
management
tools,
so
that
you
don't
have
to
basically
have
somebody
spending
their
full
time
sort
of
like
managing
the
information.
Just
the
information
flows
is,
is
a
little
bit
there's
a
little
bit
of
a
creative
tension
there
to
get
it
all
kind
of
like
working
together.
This
was
our
compromise.
A
Was
the
ability
to
have
like
these
large,
essentially
epics,
that
just
move
across
and
essentially
refer
back
to
wherever
they
are,
but
at
the
end
of
the
day
we
still
have
to
sort
of
you
know
on
a
monthly
cadence
go
in
and
make
sure
that
we
move
everything
across
and
have
the
appropriate
links
and
everything,
because
it's
not
possible
to
automate
it.
Quite
yet
I
mean,
maybe
in
a
few
years,
when
all
these
different
software's
mature,
it
will
happen
that
way,
but
it
doesn't
currently
exist.
B
A
Yeah,
so
each
one
of
these
has
its
own
dashboard
and
actually
oops
you
can.
There
is
a
view
of
this
that
has
all
of
them
together
into
a
single
roadmap
in
which
there's
just
different
tags
for
ledger:
sdk,
open
team
science
registry
and
there's
all
of
the
stuff
that
we're
doing
that's
just
tagged
appropriately,
but
we
we
thought
that
this
view
that
actually
discerns
the
different
you
know
flows.
A
So
at
any
point
and
we'll
we'll
work
on
making
this,
you
know
better
and
better,
but
at
any
point
you
know
the
community
can.
Actually
you
know,
okay
sdk
store
improvements.
I
want
to
learn
about
that.
Oh
okay,
here's
the
issue:
what
are
they
working
on?
Oh
cool,
there's,
the
summary
there's
the
details:
these
are
all
the
ards,
so
it
just
gives
you
a
just
a
very
simple
way
to
to
understand.
What's
happening
there.
A
Yes
yeah:
this
is
our
public.
This
will
all
be
complete
like
public
facing
on
and
it's
actually
going
to
get
embedded
in
region.network
website
and
and
then
you
know,
obviously
we
can
share
it
on
sort
of
a
monthly
cadence
out
as
a
link,
so
people
can
just
go
and
look
at
it
and
you
know,
ask
questions
and
whatnot.
C
A
That's
where
the
bulk
of
I
mean
that
and
oh
you
know
open
team
and
science
there's
a
lot
of
movement
going
and
then
we're
very
excited
to
you
know
start
to
swing
into
region,
ledger
work
which,
by
the
way,
just
to
pass
it
along
to
your
networks.
It
looks
as
though
we're
going
to
be
hiring
a
couple
more
engineers,
sort
of
full
stack,
blockchain
engineers.
B
A
Anytime
I
mean
that
we're
getting
a
little
bit
more
input
from
the
team
just
to
make
sure
that
everything's
represented
specifically
there's
a
little
bit
more
work
to
do
on
the
registry.
So
there's
a
a
little
bit
of
work
to
publish
to
that,
but
I
think
in
the
next
week
or
two
I
mean
we're
sort
of
sharing
it
now,
obviously,
and
we'll
embed
it
in
the
website
in
the
coming
version.
A
So
so
there's
as
it's
noted
here,
there's
actually
a
launch
of
a
we're
upgrading
the
website
and
that's
going
to
be
happening
very
soon,
and
so
with
the
upgraded
website.
This
will
be
included
and
there'll
be
a
fully
revamped
website,
which
includes
the
ability
for
people
to
purchase
credits
and
see
profile
pages
and
see
this
dynamic
roadmap
and
yeah
should
be
pretty
exciting.
A
Cool
all
right
well,
unless
anybody
has
any
questions
or
comments
or
discussion
points
that
you'd
like
to
have.
I
think
it's
probably
a
good
moment
to
to
conclude
and
see
everybody
in
a
month
and
we'll
I
I
wanted
to
keep
this
one
actually
kind
of
intimate
this.
This
dev
co
commit
we're.
Focusing
most
of
our
attention
on
stargate
right
region
is
there's
a
lot.
A
B
A
Sorry
well
we'll
just
be
using
this
format
moving
forward
and
we're
also
hoping
I
I
mean
it
looks
as
though
we're
wrapping
up
the
stargate
release
on
cosmos,
which
means
that
the
team
will
start
to
spend
more
time
on
region.
Ledger
and
there'll
be
much
more
conversation,
and
you
know
report
back
on.
What's
moving
on
the
sort
of
region,
ledger
blockchain
as
we
move
towards
the
end
of
the
year
and
future
test
net,
so.
A
More
juice
to
these
calls
starting
next
month,
gotcha
as
well
as
you
know.
Next
month
is
october
and
then
the
following
month
is
november
and
will,
as
you
know,
will
be
digging
into
the
collab-a-thon
with
open
climate.
So
there's
going
to
start
to
be
a
lot
of
activity,
it's
going
to
get
a
little
crazy,
actually
yeah.
Definitely.
D
A
Both
busy
right
now
we're
just
all
busy.
We
need
to
get
a
prompt,
we
need
to
solidify
a
prompt,
and
I
also
I'm
thinking
I
actually
think
there's
room
to
have
multiple
prompts
moving,
but
I
want
to
crystallize
the
prompt
that
we're
co-creating
with
martine
and
then
make
a
couple.
Invitations
for
other
community
members
to
participate
in
the
collab-a-thon
with
prompts
and
dorne
open
team
has
committed
a
match
of
25k
and
and
martine
got
another
25k
so
and
we're
actually
talking
to
google
and
microsoft
and
a
couple
of
other
folks.