►
From YouTube: Community Development Call 4/13/22
Description
Join Regen Network for the latest updates from our team, including blockchain development, science development, registry and go to market progress. After a 15 min update presentation we open the field for questions and engagement from our community of open source developers.
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
Okay,
well,
I
think
we
can
get
started
the
call's
recorded
and
it
will
be
available
on
youtube
sometime
later
this
week.
For
those
of
you
who
could
not
attend
and
yeah.
I
appreciate
you
guys,
showing
up
today
we
have
a
special
guest
intern
over
here
at
r
d
working
on
the
science
and
registry
team,
she's
gonna
present
here
on
a
new
project,
that's
underway
and
I'll
just
go
ahead
and
get
started
walking
through
some
of
the
regular
items
that
we
discuss
on
this
call.
A
This
call
happens
every
two
weeks:
community
dev
call
opportunity
for
community
members
to
participate,
usually
the
we
start
with
15
minutes
of
running
through
updates
and
then
15
minutes
of
discussion.
A
I'm
not
sure
if
we'll
use
the
full
time
today,
given
that
I'm
reading
it
and
we
yeah
we'll
we'll
see
how
it
goes
but
yeah
today's
agenda,
here's
a
quick
overview.
Let's
just
go
ahead
and
get
dive
dive
right
in
so
proposal
number
11
passed.
This
was
a
community-led
government's
proposal
to
help
out
some
participants
in
the
initial
token
sale
who
were
unable
to
access
their
tokens
since
genesis,
and
these
tokens
have
not
been
staked
or
transferred
or
touched
in
any
sort
of
way.
A
Thank
you,
daniel
and
josh
for
leading
the
proposal
and
getting
helping
out
this
community
member.
It
passed
with
67
turnout,
a
little
bit
lower
than
our
previous
turnouts
and
other
votes
proposals,
but
that's
most
likely
due
to
the
fact
that
we
shortened
the
voting
period
to
seven
days.
So
just
a
quick
reminder
that
proposal
10
was
decreasing
the
voting
period
to
seven
days.
So
all
governance
proposals
on
regen
network
are
currently
open
for
a
seven
day
voting
period
past
the
time
the
deposit
was
made.
A
So
our
current
plan
now
that
this
proposal
is
passed,
is
to
include
the
necessary
changes
manual
operations
during
the
upgrade
process
that
will
re-distribute
these
tokens
to
a
new
account
address
for
the
token
sale
participant
who's
unable
to
access
their
fund.
I
believe
there's
just
one
person
at
the
moment,
but
the
community
proposal
is
written
in
a
way
that
there
might
be
multiple
people,
and
this
would
be
a
one-time
change
if,
if
anything
were
to
happen
with
the
same
community
members.
A
This
is
not
something
that
we
would
do
in
a
follow-up
upgrade
as
well,
but
based
on
the
community
turnout
in
the
voting
pass.
So
we're
going
to
go
ahead
and
move
forward
with
this,
including
in
4.0,
upgrade
and
yeah
we're
going
to
be
working
with
regen
foundation
as
well
to
verify
the
person's
identity,
and
this
person
participated
in
our
token
sale,
so
they're
kyc,
so
all
making
sure
all
checks
are.
A
We
did
include
updated
guidelines
in
proposal
number
10
when
we
decreased
the
voting
period,
which
is
available
on
the
readme,
the
home
page
for
the
governance
repo,
but
this
would
potentially
create
a
more
formal
process
and
open
to
community
feedback.
A
Obviously,
and
would
love
to
have
people
participate
in
this
discussion
to
help
refine
our
guidelines
in
terms
of
how
governance
proposals
are
submitted
and
what
the
process
is
before
submitting
a
proposal
on
chain
also,
the
tokenomics
upgrade
lp
incentivization
discussion
led
by
will
zahl
from
reason
foundation
is
still
underway
and
would
love
people
to
participate
in
that
as
well
when
regen
ledger
4.0
so
about
four
weeks
ago,
I
think
I
said
maybe,
like
a
month
out,
we
would
be
finishing
up
with
some
of
the
development
work
and
we
are
currently
nearly
complete
with
implementing
all
the
features
that
we're
planning
to
include
in
4.0
and
most
of
the
refactoring
work
that
I
previously
mentioned
has
been
completed
as
well,
and
we've
kind
of
started
doing
some
auditing
and
testing,
while
other
people
are
still
finishing
up
a
few
other
items.
A
You
can
track
our
progress
with
the
issue
and
milestone
listed
here,
and
our
current
target
is
mid-may,
giving
us
time
to
really
do
a
full,
thorough
audit
and
making
sure
that
all
of
our
testing
is
complete
and
thorough.
So
currently,
targeting
mid-may
there's
one
update
into
the
region
ledger
4.0
upgrade,
which
is
that
we're
no
longer
going
to
include
cosmos,
sdk
version.
046.
A
046
is
also
targeting
an
official
release
in
mid-may
and
we
don't
want
to
delay
the
regen
ledger.
4.0
upgrade
based
on
cosmos,
sdk,
b046
and
then
also
following
the
4-6
upgrade
to
cosmos,
sdk
ibc
and
will
also
need
to
be
updated.
So
this
could
potentially
extend
our
timeline
further.
I
believe
ibc
is
working
and
making
sure
to
provide
support
as
soon
as
possible
with
the
46
release.
A
I'm
not
sure
where
the
cosmosome
team
is
at
at
the
moment,
but
cosmos
is
not
necessary
for
the
upgrade
on
mainnet,
but
we
have
included
it
as
an
experimental
module
which
will
be
available
on
hombok
following
an
official
release
for
v
4.0.
So,
ideally,
we
would
wait.
Till
qasim,
wasm
and
ibc
have
both
been
upgraded
to
force
to
support
4-6
before
we
move
forward
with
upgrading
to
4-6
on
regen
ledger.
A
A
A
We
have
further
plans
for
dex
functionality,
but
what
we're
calling
this
is
a
simple
storefront
model
and
then
also
we're
adding
project
support
to
core
functionality
of
eco
credit
modules.
A
So
we
previously
included
project
location
within
the
batch
info
and
we've
actually
pulled
that
out
and
created
a
new
entity
which
is
a
project
in
the
core
functionality
of
the
eco
credit
module,
which
will
allow
for
people
to
create
projects
that
have
their
own
defined
metadata,
as
well
as
including
the
project
location
and
any
other
information
such
as
baseline
measurements
can
be
included
in
the
metadata
and
then
the
batch
will
actually
just
reference
the
project
id
number
rather
than
including
the
project
information
directly
in
the
batch.
A
So
projects
will
be
able
to
be
created.
We've
also
made
the
ability
for
projects
metadata
and
admin
to
be
updated.
Basically,
when
a
project
is
created
it
can
it
will.
The
creator
will
be
assigned
as
the
admin
and
the
the
only
people
that
are
allowed
to
create
projects
initially
will
be
someone
who's.
A
A
designated
issuer
in
the
credit
class
to
avoid
people
creating
projects
that
yeah
aren't,
are
not
real
projects,
so
there's
some
sort
of
permission
any
set
in
place
with
project
creation
so
and
that
that
might
change
in
the
future.
But
that's
the
current
model
that
we're
working
with
now
also
we're
adding
the
data
module
to
the
stable,
app
configuration.
This
is
something
that
we've
been
developing
pre-launch
on
mainnet
and
a
couple
years
now,
and
we
finally
feel
that
we're
ready
to
include
it
in
an
upgrade.
A
This
is
gonna
allow
for
anchoring
data,
also
known
as
secure
time,
stamping
and
then
attesting
to
the
validity
of
that
data
and
also
the
ability
to
define
a
data
resolver
and
then
register
data
with
that
resolver,
so
very
excited
to
see
that
moving
along
and
included
in
regen
ledger.
Additionally,
we're
making
some
migrations
in
terms
of
how
we
store
data
for
each
module,
which
were
which
is
migrating
to
the
orm
storage
model.
A
So,
in
addition
to
that,
we're
adding
dynamic
minting
of
credits-
I
didn't
talk
about
this
four
weeks
ago,
but
this
was
under
development
and
in
design
phase
and
we've
actually
implemented.
This
feature
now,
basically
we're
allowing
for
dynamic
minting
of
credits
to
batches
that
are
unsealed,
and
the
idea
here
is
that
this
would
support
bridging
assets
over
from
the
polygon
chain.
A
We're
working
with
two
can
on
the
design
and
the
implementation
of
this
functionality,
so
that,
when
like
traditionally
a
credit
batch
is
immutable,
and
the
idea
here
is
that,
in
order
to
provide
fungibility
with
credits
that
are
coming
from
the
same
monitoring
period,
basically,
a
new
batch
will
be
created
for
a
bridged
ass
for
bridged
credits
and
then
any
credits
that
are
matching
the
same
monitoring
period
rather
than
creating
a
new
batch.
A
It
would
actually
allow
for
the
dynamic
minting
of
credits
into
the
the
the
batch
that
represents
the
monitoring
period
and
that
has
the
same
source.
The
idea
here
too,
is
that
we're
preserving
the
immutability
of
credit
batches
issued
natively
on
regen
ledger,
and
so
this
would
primarily
be
just
primarily
used
for
just
bridged
assets
over
from
polygon
and
from
other
source
chains
in
the
future.
A
B
Awesome,
thank
you
ryan,
so
for
anyone
I
haven't
interacted
with
yet
I'm
josie
I've
been
working
with
regen
since
the
beginning
of
march
part
time
with
the
registry
team.
It's
been
fun
to
tackle
this
built
on
region
network
project,
which
is
this
external
facing
public
notion.
B
B
However,
after
this
call
and
we're
planning
to
promote
it
publicly
next
week,
tentatively
across
our
channels,
so
there's
a
lot
of
different
components
on
this
page
right
now
we
have
seven
complete
project
cards
where
regen
affiliates
have
gone
in
multi-faceted
our
affiliates
have
offered
up
kind
of
a
basic
education.
B
What
is
the
ecological
story
if
they're
a
methodology
developer,
for
example?
What's
the
ecological
story?
You
know
here
on
this
slide,
we
have
yaokan
holly,
what
is
yalpan
holly
or
we
have
dao
ocean
they're
talking
about
the
seaweed
work
that
they're
doing
off
the
west
coast
of
france.
So
there's
this
education
component
there's
this
project
outline
component,
which
is
what
are
we
working
on
right
now?
What
is
our
relationship
to
regen
network
and
then
there's
also
this
needs
and
constraints
component
which
we've
designed
to
enable
collaboration
in
a
decentralized
way
across
projects.
B
So
maybe
we
have
a
project
who
is
in
need
of
a
monitoring
service
provider?
We
have
people
who
offer
monitoring
services
they
can
connect.
Alternatively,
maybe
you
have
dow
ocean,
for
example,
who's
looking
to
have
conversations
about
blue
carbon.
They
can
connect
with
lucas
winkleprince
who's,
also
kind
of
thinking
through
these
similar
challenges,
so
yeah
exciting
stuff.
B
Next
slide,
please
so
here
I
have
some
examples
that
I
pulled
from
the
cards,
so
you
can
get
a
feel
for
what's
going
on,
like
I
said
before,
the
our
affiliates
are
filling
out
these
cards
with
some
help
from
the
registry
team,
giving
some
basic
education
in
the
second
kind
of
skinnier
photo.
You
can
see
this
seeking
collaboration
section
through
notion.
B
We've
been
able
to
leverage
this
tagging
feature
which
will
make
it
easy
for
people
to
filter
out
projects,
whether
they're
looking
for
again
like
a
monitoring
service
provider,
they
can
see
who
offers
that
or
maybe
they're
working
in
agroforestry,
and
they
want
to
see
what
other
projects
are
being
developed
on
on
the
across
the
network.
In
that
realm,
there's
also
an
option
to
do
that
next
slide,
please
so
here's
an
example
of
that
in
a
little
bit
closer
way.
This
is
courageous
lands
who
have
been
like
a
treat
to
work
with.
B
You
can
see
all
of
the
the
tags
that
they've
selected
that
they
can.
Other
people
can
find
them
using
these
tags
or
they
can
use
some
of
these
tags
to
find
other
projects
and,
in
this
upper
right
hand
corner.
You
can
see
examples
of
the
different
actors
who
are
working
across
the
network
right
now.
B
So,
as
I
said
right
now,
we
have
about
seven
people
with
a
totally
completed
card
and
we
also
have
about
40
people
who
are
logged
on
this
page
that,
where
they're
still
working
on
their
card,
it's
in
progress,
there's
a
little
quip
about
this
is
who
we
are.
This
is
what
we're
doing
this
is
our
relationship
to
regen
project
outline
coming
soon,
so
these
this
is
a
living,
a
living
link
that
will
continue
to
develop
and
change
as
people
interact
with
it.
B
One
exciting
component
about
this,
a
big
question
that
the
registry
team
is
getting
right
now
is:
okay,
I'm
I'm
a
methodology
developer,
I'm
developing
this
methodology
that
demonstrates
improvement
in
water
quality.
What
is
what
is
the
market
for
this
thing,
and
this
is
a
place
for
an
investor
to
come
and
say:
oh
wow,
there's
50
projects,
there's
30
projects
whatever
that
are
developing
these
projects,
we're
building
a
market
by
putting
all
these
people
and
organizations
in
the
same
place.
B
This
is
a
way
to
decentralize
for
these
people
to
connect
amongst
themselves,
and
you
know
this
wave
of
regenerates
that
is
rising
up
in
in
response
to
the
climate
crisis.
This
is
a
way
for
innovation
to
to
happen
so
yeah.
This,
like
I
said,
I'm
happy
to
share
this
link
and
we'll
be
promoting
it
more
publicly.
Next
week.
A
Awesome,
thank
you
so
much
josie.
It
looks
like
someone's
requesting
a
link
in
the
chat
too.
If
you
could
share
that
there
cool
moving
ahead,
just
a
couple
more
items,
regenerating
newshour.
Just
as
a
quick
reminder.
We
have
this
twitter
space
every
thursday
at
1600
ugc.
Last
week
we
discussed
methodologies.
Biochar
grants
science.
A
I
didn't
listen
to
it
myself,
yet
it's
on
my
backlog
of
items
to
catch
up
on,
but
these
are
great
conversations
for
the
community
to
participate
in
and
to
discuss
all
things.
Regen,
regen,
ecosystem,
refi
ecosystem,
so
check
it
out.
If
you
haven't
already,
the
topics
are
kind
of
on
a
to
be
determined
basis,
sometimes
being
decided
on
the
fly.
I
don't
think
there's
one
to
be
determined
quite
yet
for
this
week,
but
tomorrow
thursday
at
1600
utc.
A
If
you
want
to
tune
in
to
the
next
generation
newshour
and
then
as
usual,
we
provide
updated
market
and
liquidity
report
on
these
calls.
So
here
are
the
stats.
Dan
went
ahead
and
updated
these
earlier
this
morning,
but,
as
mentioned
dan,
is
at
ecosystem
retreat
and
gregory
was
out
today.
So
I
appreciate
you
all
sticking
with
me
and
going
through
the
community
dev
update
this
week
and
yeah.
We
can
use
the
remaining
time
for
questions
if
anyone
has
any.
C
I'm
curious
about
the
dynamic
minting
within
the
batches
and
I
guess
I
took
a
quick
look
at
one
of
the
pr's,
but
I
guess
I
didn't
quite
see
what
I
was
hoping
to
find,
but
maybe
like
soon
there'll
be
documentation
on
that
or
something
yeah.
A
So
this
is
a
just
like
a
quick
overview.
This
is
something
that
we've
been
working
with
on
the
with
the
toucan
team.
A
Basically,
how
assets
are
handled
on
different
chains
differs
so
tco2
token,
being
bridged
over
to
regen
network,
doesn't
align
perfectly
with
our
credit
badge
module
our
credit
batch
data
model
so
essentially
we're
creating
this
ability
for
credits
to
be
dynamically
minted
into
an
existing
credit
batch.
A
If
that
credit
batch
is
unsealed
or
open
any
assets
that
are
created
on
regen
ledger,
the
default
is
to
have
credit
batches
sealed
so
that
credits
cannot
be
dynamically
minted
into
credit
batches,
but
in
order
to
support
assets
coming
over
from
other
chains
and
in
order
for
those
assets
to
be
fungible
within
the
same
credit
batch
and
to
represent
the
same
monitoring
period.
Basically,
we
need
to
add
the
support
for
dynamically
minting
batches
to
existing
credit
batches.
A
So,
for
example,
if
alice
sends
10
credits
over
from
polygon
to
regen
network,
and
then
she
sends
10
credits
over
the
next
day
in
the
current
model.
Basically,
we
would
have
to
create
two
separate
batches,
even
if
those
credits
were
from
the
same
monitoring
period,
but
to
prevent
that
we're
creating
this
dynamic
functionality
so
that
the
credits
can
actually
be
added
to
the
existing
batch.
A
If
it's
the
same
credit
batch
as
represented
like
on
the
vera
registry,
for
example,
so
yeah,
and
that
will
also
allow
us
to
track
and
make
sure
double
spending
is
not
not
being
occurred
because
we'll
include
the
origin
transaction
as
well
within
that
dynamically
minted
batch,
so
there
yeah
there
will
be
documentation.
A
A
My
current
focus
is
getting
documentation
up
for
the
data
module,
but
that
would
be
the
next
item
for
sure
to
include
documentation
around,
but
nothing
nothing
really
changes
for
those
interested
in
issuing
credits,
natively
on
regen,
ledger
and
there's
no
new
security
vulnerabilities
for
issues
for
credit,
batches
that
are
sealed,
and
so
there's
nothing
to
be
concerned
in
that
regard-
and
this
is
primarily
the
primary
use
case-
is
to
support
bridging
assets
over
from
polygon.
A
Might
be
a
question
yeah
and
we
we
discussed
this
too
in
some
of
our
product
calls
whether
there
would
be
potential
use
cases
and
yeah.
I
think
I
I
think
there
might
be
some
edge
cases
where
it
could
be
beneficial
to
have
an
unsealed
batch
for
a
batch
issue,
natively
on
regen
ledger,
but
I
think
we're
still
kind
of
exploring
that
in
the
idea
for
now
is
that
this
would
this
would
just
be
used
for
bridging
assets,
but
people
are
able
to
override
the
default
setting
when
issuing
a
batch.
A
So
if
they
do,
for
some
reason
want
to
create
this
dynamic
batch
model,
then
that
is
possible,
but
r
d
doesn't
have
any
plans
or
the
registry
doesn't
have
any
plans
to
use
it
in
that
way,
because
we
want
to
ensure
the
immutability
of
the
credit
bash
is
issued
natively
on
regen
ledger,
so
I
I
mean
yeah.
That
might
be
a
question
for
others
to
talk
on
a
little
bit
as
well
at
a
future
time
or
feel
free
to
ping
us
in
discord.
D
Not
directly
related
to
what
you've
presented,
but
one
of
the
questions
coming
up
for
me
around.
I,
I
guess
it
like
batching
triggers
it,
at
least
as
I'm
thinking
about
the
endowment
tokens
and
where
they
land
with
endowment
candidates,
because
I
believe
it
can
only
be
issued
once
and
it's
all
in
one
big
block
because
of
technical
reasons.
I'm
just
wondering
does
that
tie
into
any
of
the
functionality
you're
talking
about
here
in
being
able
to
drip
drab
endowment
offerings,
perhaps
through
the
batches
module.
A
I
I
think
that
that
would
be
separate
and
I
there's
there's
no
real
functionality
on
the
horizon
that
might
improve
that
other
than
the
group
module
being
included
in
sdk46,
which
is
being
pushed
back.
It
wouldn't
necessarily
allow
for
dripping
assets,
but
it
would
allow
for
the
better
governance
of
the
account
that's
receiving
those
assets,
but
the
the
batch
credit
batch
functionality
specific
to
ecosystem
service
credits
and
not
tokens,
so
it
wouldn't
necessarily
change
any
of
that.
A
But
yeah,
that's
a
great
question
and
I
think
a
technical
problem
that
we
would
love
to
resolve.
Essentially,
I'm
pretty
sure
that
the
technical
issue
there
is
that
we
need
to
create
a
vesting
account
and
each
time
you
create
each
time
you
want
to
issue
tokens
to
investing
account.
You
essentially
have
to
create
a
new
vesting
account
so
that
that's
like
an
issue
more
so
on
the
sdk
side
of
things
that
we're,
hopefully
gonna
figure
out
a
solution
for
in
the
near
future,
but
I
don't
think
it
will
be.
A
There
will
be
anything
in
the
near
term
that
will
help
resolve
that.
Unfortunately,.
D
Well,
thanks,
that's
good
to
know
if
it
could
land
on
a
board
somewhere
they'd
be
super
appreciated,
because
it
would
really
help
endowment
de-risk
their
allocations
and,
like,
I
think
doing,
that
would
provide
incredible
benefits
for
the
ecosystem
if
we
can
drip
drab
stuff
in
a
kind
of
safer
way,
rather
than
you
know,
here's.
A
Yeah
for
sure
I'll
make
sure
that
it's
it's
it's
being
tracked
somewhere
and
I'm.
I
know
it
is
already
being
tracked,
but
I'll
try
to
resurface
it
and
bring
it
to
priority.
A
Cool
well
we're
at
the
top
of
the
hour.
Thank
you
all
for
joining
and
bearing
with
me
on
leading
this
call,
and
thank
you
very
much
josie
for
joining
and
presenting
built
on
regen
very
excited
about
that
project.
So
have
a
good
day,
see
you
guys
all
in
two
weeks
and
for
those
of
you
watching
on
youtube.