►
Description
Join the Regen Network Development team to better understand Regen Ledger, the new ecocredit module, how it's used, plus what's on the horizon for our team! This is a fantastic overview for all levels, from crypto newcomer to expert, to learn more about our blockchain's utility and the future of the tokenized carbon economy.
A
So
what
is
this?
Essentially,
we
have
these
deep
dive
presentations
that
we
do
at
r
d
internally,
it's
a
way
for
us
to
build
context
between
teams
between
our
engineering,
science,
product
teams,
and
we
went
through
one
of
these
deep
dives
last
week
and
we
decided
that
it'd
be
a
really
good
opportunity
to
do
some
more
context.
Building
with
our
community,
which
is
a
community
that
is
diverse
in
itself.
We
have
members
from
the
blockchain
community,
as
well
as
members
from
ecosystem
service,
community
or
climate
change,
communities
and
science
communities.
A
So
we
decided
that
we
would
go
ahead
and
give
this
presentation
again
to
our
community
as
a
larger
audience
to
do
some
context
building,
and
so
this
is
the
lineup
today
that
we're
gonna
go
through
four
parts
here
the
first
part
will
be
covered
by
corey,
we're
gonna
talk
about
regen,
ledger
and
understanding
blockchain.
What
is
blockchain
on
a
general
level?
Some
of
you
might
be
veterans
here,
but
we
are
doing
that
context
building
for
those
of
you
that
are
less
familiar.
A
A
Part
three
is
going
to
be
led
by
sam
and
we're
going
to
talk
a
little
bit
about
the
relationship
between
eco
credit
module,
how
it's
being
used
with
the
registry
and
how
it's
being
used
with
registry
and
kind
of
look
looking
ahead
in
part
four,
which
will
be
broken
up
between
all
all
of
us
to
give
a
little
outro
on.
What's
on
the
horizon.
So
without
further
ado,
I'm
gonna
hand
it
off
to
corey
to
get
started
off.
B
B
So
for
the
purposes
of
this,
let's,
let's
all
set
a
kind
of
common
understanding
and
framing
here
for
what
a
blockchain
actually
is
at
its
core.
A
blockchain
is
a
replicated
deterministic
state
machine.
So
what
that
means
is
that
there
is
a
progression
of
state
right.
Some
internal
state
application
logic
that
updates
over
time.
B
The
way
that
that
updates
is
through
state
transitions,
where
there
is
a
transaction
that
is
sent
to
the
network
and
that
triggers,
let's
say
the
application
state
to
go
from
you
know
previously.
It
said
that
the
account
balance
sheet
was
x
and
now
it
says
the
account
balance
sheet
is
y.
An
important
thing
about
blockchains
is
that
all
of
the
state
transitions
that
come
through
transactions
are
all
cryptographically
signed,
which
means
the
only
way
that
the
application
system
can
actually
like
update
its
state.
B
And
you
know,
progress
over
time
is
through
authenticated
messages
that
individual
end
users
are
signing
onto
the
network
and
all
of
these
messages.
In
terms
of
like
how
they're
structured
on
the
on
the
actual
computers
and
servers
is
that
they're
assembled
into
what
are
called
blocks
and
certain
people
who
are
running
the
software
will
when
they
assemble
a
bunch
of
transactions
into
a
group
and
call
it
a
block,
they
will
then
sort
of
solidify
it.
A
process
called
minting
and
then
send
that
block
around
to
all
the
other
peers
in
the
network.
B
A
B
B
That
means
that
all
of
the
data,
that's
being
that's,
being
landed
on
the
blockchain.
All
of
the
state
updates
that
we
were
just
talking
about
before
they
can't
get
reversed.
There's
no
way
to
go
back
in
history
and
there's
no
way
to
sort
of
change
the
the
state
to
sort
of
rewrite
history
or
remove
that
an
action
happened
in
the
past.
B
So
there
isn't
a
single
person
or
a
single
entity
or
server
infrastructure
runner
who
can
take
down
their
software
for
their
servers
and
shut
down
the
whole
network,
because
it's
a
peer
to
peer
network.
People
can
join
the
network
at
any
point
in
time
they
can
participate
in
validating
blocks
and
and
because
of
that,
it's
it's
quite
difficult
unless
all
of
the
people
validating
the
network
in
a
coordinated
way
choose
to
go
offline
so
that
censorship
resistance
is
also
something
that
is
valuable
for
us.
In
our
use
case,.
B
So
another
thing
that
you'll
probably
hear
commonly
in
the
blockchain
ecosystem
is
proof
of
stake.
I
think
it's
worth
to
just
give
a
little
bit
of
context
for
what
this
is
proof
of
stake
and
proof
of
work
are
two
different
consensus
mechanisms
for
a
blockchain,
so
they're
describing
actually,
how
does
the
the
different
nodes
in
the
network
come
to
alignment
on
what
the
next
block
in
the
chain
should
be
in
proof
of
work.
The
way
that
these
these
miners
are
actually
deciding.
B
We
have
it
proportional
to
staking
tokens.
So
in
our
case,
that's
the
native
regen
token
and
there's
a
few
concrete
benefits
of
proof-of-stake
blockchains.
The
ones
that
I
think
are
worth
calling
out
here
are
that
one
it's
drastically
more
environmentally
friendly,
so
there's
no
wasteful
compute
cycles,
where
they're
just
trying
to
spin
cpu
cycles
in
an
effort
to
solve
a
meaningless
hard
computational
puzzle
and
the
other
component.
That's
interesting
for
proven
stake
networks
is
that
it
gives
the
token
holders
governance
over
the
network.
B
So
now
talking
a
bit
about
regen,
ledger.
Regent
ledger
is
a
domain
specific
proof
of
state
blockchain
application,
that's
built
with
the
cosmos
sdk.
We
can
talk
a
little
bit
about
what
these
terms
mean.
So
I
think
this
diagram
is
useful
to
look
at
at
the
top.
You
see
regen
ledger
right.
We're
going
to
have
a
bunch
of
within
the
context
of
region.
Ledger
in
our
you
know,
quote.
Like
code
base,
the
repository
for
regen
ledger.
We
have
a
lot
of
domain
specific
modules
and
functionality.
B
And
what
he
describes
is
that
our
approach
is
a
hybrid
of
sort
of
two
potential
paths
for
proven:
stake:
networks
on
one
hand,
you've
got
community
specific
networks.
Where
really
you
know,
you're
just
distributing
a
bunch
of
tokens
and
you're,
saying,
let's
let
the
token
holders
decide
through
governance,
what
they
want
the
network
to
do
and
what
they
think
the
purpose
of
the
network
should
be.
B
On
the
other
hand,
you
could
have
an
application,
specific
network,
where
you're
being
really
concrete
about
what
the
software
features
are
going
to
be
for
this
network
and
you're,
wanting
that
to
kind
of
bring
users
together
and
you
know,
drive
adoption
and
for
us
we
see
regen
as
kind
of
a
hybrid
of
these
two
models.
You
know
we
as
r
d
inc,
you
know,
are
very
opinionated
about.
B
You
know
how
the
kinds
of
functionality
that
we
think
regen
network
should
have,
but
we
we
actively
want
to
invite
the
community
into
that
governance
process
and
to
really
have
it
be
a
conversation
and
eventually
to
have
it,
be
a
situation
where
it's
not
just
us
being
the
only
developers
of
the
network.
But
there
are
community
contributors
who
are
also
putting
in
their
own
governance
proposals
and
contributing
with
software
upgrades.
B
And
then
underneath
all
of
these
modules
are
wired
together
and
they're,
able
to
kind
of
communicate
with
each
other.
Maybe
send
data
back
and
forth
through
each
other.
But
you
should
think
of
each
of
these
modules
as
basically
their
own
little
state
machine.
Each
one
has
its
own
application.
State
has
its
own
set
of
messages
that
it
accepts
from
end
users
and
its
own
way
of
processing
and
managing
some
internal
state.
A
B
A
Great,
thank
you
corey.
So
in
this
part,
I'm
going
to
talk
about
the
eco
credit
module
in
more
detail,
as
corey
mentioned.
Just
as
a
little
introduction,
the
eco
credit
module
is
going
to
be
the
first
module
that
is
going
to
be
a
domain.
Specific
module
built
into
region
ledger
available
on
regen
mainnet.
The
the
other
modules
are
available
on
a
experimental
test
network,
but
this
will
be
the
first
module
that
will
be
on
mainnet,
so
it's
really
exciting
and
yeah.
A
In
this
part,
we're
going
to
go
a
little
more
detail
on
understanding
the
eco
credit
module.
So
what
is
the
eco
credit
module?
Well.
Corey
also
talked
about
modules
there,
their
ways
of
defining
state
and
internal,
how
internal
state
can
be
updated
and
the
eco
credit
module
is
focused
on
the
state.
Around
ecosystem
service
credits
and
ecosystem
service
credits
can
be
a
variety
of
types
of
ecosystem
service
credits.
So
there
is
no
focus
on
carbon
credits
alone.
A
The
primary
abstraction
of
ecosystem
service
credits,
and
this
is
essentially
used
to
manage
the
issuance
process
and
credit
classes
are
managed
by
admins
and
they
have
issuers
and
they
in
the
issuers
issue,
credits
in
the
form
of
credit
batches
and
we're
going
to
go
into
detail
on
how
all
that
works.
By
looking
at
some
of
the
data
structures
within
the
eagle
credit
module.
A
So,
first
off
credit
classes,
as
I
mentioned,
this
is
the
primary
abstraction
for
ecosystem
service
credits
and
credit
classes
are
used
to
manage
the
issuance
process
on
the
right.
Here
we
have
an
overview
of
what
the
properties
are
for
a
credit
class
as
represented
on
chain,
the
first
property
there
is
class
id,
and
this
is
an
auto-generated
unique
id
that
is
constructed
from
the
credit
type.
A
So
c01
in
the
example
on
the
right
is
just
a
representation
of
what
a
credit
class
id
might
look
like,
and
that
takes
the
abbreviation
from
the
credit
type,
the
c
abbreviation
and
zero.
One
is
the
sequence
number
within
that
credit
type.
So
this
is
the
first
credit
type
or
credit
class
creative,
using
the
carbon
credit
type.
A
If
you're
asking
what
a
credit
type
is
we're
going
to
go
into
that
on
the
next
slide,
but
yeah
next
up,
we
have
the
admin.
The
admin
is
responsible
for
managing
the
credit
class.
The
admin
has
the
capabilities
of
updating
the
issuers
list,
as
well
as
updating
the
metadata,
as
well
as
changing
the
admin
role
over
to
another
address
in
this.
In
this
example
on
the
right,
we
have
a
region
address
representing
the
admin,
there's
only
one
admin
for
each
credit
class.
A
A
So,
within
the
credit
class,
it's
going
to
track
the
number
of
batches
that
have
been
issued
from
this
credit
class
and
that's
a
general
overview
of
the
credit
class
next
slide
we're
going
to
look
at
the
credit
types.
So
what
is
a
credit
type?
Well,
credit
type
is
the
primary
indicator
used
by
methodology
to
measure
the
change
or
impact
resulting
from
an
ecosystem
service.
A
A
The
credit
type
in
terms
of
its
data
structure
and
properties.
It
includes
a
name,
an
abbreviation,
an
abbreviation,
can
be
one
to
three
characters:
long,
the
measurement
unit,
which
is
more
details
about
what
is
actually
being
measured
in
this
case
metric
tons,
co2
equivalent
and
a
decimal
precision.
So
how
precisely
it's
being
measured
and
yeah
the
credit
type
is
something
that
needs
to
be
included
within
the
credit
class.
When
the
credit
class
is
created
and
the
credit
class.
A
So
next
up
we're
going
to
look
at
credit
batches
and,
as
I
mentioned
in
the
first
slide,
so
credit
batches
are
essentially
how
credits
are
issued
and,
within
the
credit
credit
batches
are
issued
by
issuers
of
that
credit
class,
and
so
looking
at
some
of
the
properties
within
the
credit
batch,
we
are
starting
with
the
class
id.
This
is
the
same
representation
that
is
in
the
credit
class.
So
when
a
credit
batch
is
issued,
it
stores
information
about
the
class
that
it's
being
issued
from
the
denomination.
A
So
next
up
we're
going
to
look
at
issuer
that
just
records
the
issuer
that
was
responsible
for
issuing
this
credit
batch,
as
we
have
in
credit
class
there's
also
a
metadata
field.
This
can
include
information
about
the
monitoring
process
or
the
data
accumulated
from
the
process
and
once
again,
that's
a
256
byte
array
that
can
be
used
to
store
a
small
amount
of
information
or
point
to
a
content
hash.
A
The
credit
batch
also
keeps
track
of
the
number
of
active
credits,
credits
that
have
been
issued
from
this
credit
batch.
That
includes
tradable
credits
as
well
as
retired
credits,
and
then
it
also
tracks
the
number
of
cancelled
credits.
So
it
is
possible
to
cancel
credits
that
have
been
issued
and
then
it
also
includes
the
start
and
end
date,
which
is
included
in
the
denomination,
as
well
as
the
project,
location
and
the
project.
Location
is
constructed
from
the
country
code,
the
subnational
code
and
the
postal
code,
and
it's
following
the
iso
3166
to
standards.
A
But
all
that
information
is
included
in
each
credit,
patch
and
yeah.
I
think
that
covers
this
slide,
so
I'll
just
move
on
to
the
next
one
life
cycle
of
a
credit.
Okay.
So,
as
corey
mentioned
in
the
first
part,
there
are
these
transactions
that
perform
straight
state
transitions
within
these
transactions.
There
are
messages
and,
within
the
eco,
credit
module
the
defined
message,
messages
or
functionality
that
is
used
to
update
state
eco-credit
module
state,
the
ability
to
create
a
class.
So
there's
a
message
create
class
the
ability
to
update
the
credit
class.
A
These
are
the
functions
that
the
admin
is
responsible
for.
So
that's
updating
the
admin
role,
updating
the
metadata,
updating
the
issuers
list,
as
well
as
a
message
for
creating
a
credit
batch
and
that's
what
the
issuer
is
responsible
for
within
a
credit
class
and
then
there's
also
the
ability
to
send
retire
and
cancel
credits,
and
something
important
to
note
here
in
relation
to
creating
credit,
batches
and
sending
credit,
batches
and
retiring
credit
patches
is
that
credits
are
either
tradable
or
retired
and
they're
tracked
for
each
account
as
either
being
tradable
or
retired.
A
Once
credits
are
retired,
they
can
no
longer
be
unretired.
Essentially
when
credits
are
retired,
it's
it's
implies
that
the
holder
is
claiming
the
credit
as
an
offset
and
credits
can
be
retired
in
three
different
stages.
Essentially,
so,
when
you
create
a
credit
batch,
you
can
list
credits
that
are
going
to,
or
you
can
specify
a
number
of
credits
that
will
be
retired
upon
issuance.
A
A
You
have
the
option
to
specify
how
many
credits
will
be
either
tradable
or
retired,
and
this
is
also
possible
when
you're
sending
credits
to
another
address.
So
if
you're,
the
owner
of
credits-
and
you
have
say,
20
tradable
credits,
you
want
to
retire
10
of
those
credits
upon
transfer
to
another
account,
so
you
can
send
10
tradable
credits
and
10
credits
that
retire
upon
transfer
and
then
obviously
the
other
option
is
to
retire
the
credits.
A
When
you
are
the
holder
or
owner
of
a
certain
number
of
tradable
credits,
you
have
the
option
to
retire
credits,
so
this
is
the
functionality
and
an
overview
of
how
the
credit
life
cycle
works
and
the
functionality
is.
These
messages
here
listed
at
the
bottom
in
terms
of
this
is
how
state,
within
the
equal
credit
module,
is
updated.
A
As
I
mentioned,
when
I
was
talking
about
credit
types,
there
are
these
on-chain
parameters.
Each
module
has
specific
on-chain
parameters
that
can
only
be
updated
through
a
governance
process.
So
there's
a
parameter
change
proposal
that's
submitted
and
actually
on
regen
mainnet
we've
already
had
three
parameter
change.
Proposals
go
through,
one
was
the
enabling
ibc
transfers
enabling
token
transfers
and
another
one
was
the
increasing
the
max
validator
set.
So
we've
already
gone
through
three
governance
proposals
for
updating
parameters
and
these
parameters
within
the
eco
credit
module.
A
The
four
parameters
within
the
eco
credit
module
include
the
credit
class
fee.
This
is
the
fee,
that's
charged
when
a
credit
class
is
created,
the
allowed
class
creators.
So
we're
going
to
talk
about
this
on.
I
believe
the
next
slide
that
the
allowed
class
creators
is
a
list
of
addresses
that
are
able
to
create
credit
classes,
and
this
can
be
either
enabled
or
disabled
on
a
network.
A
So
that
brings
us
to
the
next
parameter,
which
is
allow
list
enabled
this
is
going
to
be
set
for
true,
initially
on
once
regen
ledger,
2.0
has
been
or
once
regen
mainnet
has
been
updated,
region,
ledger,
2.0
and
the
final
parameter.
There
is
credit
types
which
is
what
I
started
with
at
the
beginning.
There
is
a
list
of
credit
types
that
have
been
approved
in
this
default.
A
Credit
type
that's
going
to
be
starting
on.
That
list
is
going
to
be
the
carbon
credit
type
and
in
order
to
add
another
credit
type,
that
is
usable
when
you
want
to
create
a
credit
class
you're
going
to
have
to
go
through
this
parameter
chains,
proposal
process
and
submit
a
governance
proposal
to
add,
for
example,
a
biodiversity
credit
type.
A
Okay,
so
credit
class
creator
allow
list.
This
is
something
that
can
be
either
enabled
or
disabled,
as
mentioned
on
the
previous
slide,
and
this
is
intended
to
be
a
temporary
feature
essentially
on
regen
mainnet.
The
idea
here
is
that
we're
we're
aware
that
there
might
be
some
changes
to
the
eco
credit
module
in
terms
of
how
the
data
is
structured,
that
we
want
to
make
sure
that
anyone
who's
creating
credit
classes
and
issuing
credits
is
willing
to
work
with
the
regen
network
development
team
and
the
community
on
the
migration
process.
A
These
guidelines
are
included
in
our
governance,
repo,
that
we
created
to
draft
proposals,
governance
proposals-
and
this
is
a
document
called
process
for
becoming
a
credit
class
creator,
and
this
includes
information
such
that
if
you're
either
an
applicant
interested
in
becoming
a
credit
class
creator
or
if
you're,
a
community
member
wondering
how
you
should
properly
vote
upon
or
judge
people
that
are
applying,
then
this
document
provides
some
more
information.
The
main
key
points
here
are:
we
want
people
that
are
actively
engaged
in
the
design
and
development
of
ecosystem
service
credits.
A
We
want
people
that
are
going
to
demonstrate
their
desire
and
capacity
to
work
with
the
region.
Ledger
team,
the
maintainers
community.
When
and
if
the
credit
class
data
changes
and
we
need
to
do
some
migrations
and
then
also,
we
want
people
to
socialize
their
candidacy
in
the
forum
and
gather
initial
support
before
submitting
a
proposal
and
there's
more
details
about
that.
As
I
mentioned
in
the
governance
repo
in
this
document
called
process
for
becoming
a
credit
class
creator,.
A
A
I
guess
the
gen
batch
json
function
is
something
that
helps
you
create
a
credit
batch
because
there's
a
lot
of
information
that
goes
in
there
so
but
yeah.
There
are
command
line,
there's
the
command
line,
interface
available,
which
is
using
the
regen
binary
and
then
also
we
have
grpc
and
rest
api
endpoints
available
for
third-party
developers
wanting
to
build
guise
or
adapts
and
then
also
in
the
future,
we're
planning
on
building
out
our
own
web
app
or
our
registry
application
in
order
to
support
the
managing
of
issuance
and
custody
of
credits.
A
So
that
is
something
to
look
forward
to
for
people
that
are
not
as
comfortable
with
using
the
command
line
interface
or
that
are
not
necessarily
looking
to
build
an
application
themselves,
but
to
be
a
general
user
using
a
interface
built
by
the
region
network
development
team,
and
that
brings
us
to
the
end
of
part
two.
So
I'm
going
to
go
ahead
and
hand
it
off
to
sam
now.
C
Cool
thanks
ryan,
so
yeah.
Now
that
we've
talked
about
the
ledger
and
the
eco-credit
module,
I
mean
how
different
actors
can
engage
in
managing
on-chain
assets.
I'll
speak
a
bit
more
to
how
the
eco-credit
module
can
be
used
in
the
real
world.
So
how
registry
registries,
project
developers,
land
stewards
and
other
organizations
might
use
the
eco-credit
module
to
represent
credits
that
are
being
issued
to
conservation
or
restoration
projects.
C
Land
stewards
must
provide
evidence
to
prove
how
their
environmental
stewardship
helps
conserve,
restore
or
regenerate
landscapes,
and
traditionally
this
work
is
done
using
an
ecosystem
service
registry.
So
registries
are
organizations
who
work
with
land
stewards
to
measure
changes
in
ecological
state
to
provide
payments
for
ecosystem
service
for
services
such
as
carbon
credits.
So
examples
of
these
groups
include
vera
gold,
standard,
dory
or
our
own
regen
registry
and
at
a
high
level.
C
What
all
these
groups
are
doing
is
we're
working
with
land
stewards
to
help
bundle
their
work
into
a
report
which
can
provide
evidence
for
credit
issuance
walking
through
this
process
a
bit
more.
We
typically
start
with
registration
where
the
land
steward
or
the
project
developer,
will
select
a
methodology
which
provides
the
detail,
details
for
the
monitoring,
reporting
and
verification
process.
C
They'll
check
the
project
eligibility
requirements
outlined
by
the
registry
program
or
in
the
methodology
they'll
develop
a
project
plan
that
defines
what
they're
doing
their
practice,
how
they're
doing
it
and
the
different
actors
that
are
involved
and
then
they'll
establish
a
baseline,
which
essentially
says
at
the
beginning
of
this
project.
This
was
the
current
state
of
the
environment
so
that
in
the
future
we
can
reference
that
to
help
measure
ecological
change.
B
C
Which
they
then
provide
to
what's
called
a
verifier,
and
so
the
role
of
the
verifier
is
to
double
check
the
work
that
might
be
going
through
the
report
itself
in
a
desk
audit,
they
might
be
performing
an
in-field
visit
to
collect
their
own
measurements
in
cross-references.
To
see
if
what's
being
claimed,
is
actually
happening.
C
The
verifier
produces
their
own
report
and
then
they
submit
that
to
the
registry,
and
so
the
registry
is
checking
both
these
reports
to
see.
If
there
are
any
discrepancies
between
what
the
different
actors
are
finding
I
mean
if
everything
checks
out
they'll
go
ahead
and
issue
credits,
so
the
registry
will
issue
credit
to
the
project
proponent.
This
could
be
the
land
store.
This
could
be
a
project
developer.
C
Speaking
on
behalf
of
the
land
steward
or
another
trusted
third
party,
once
the
the
project
proponent
has
those
credits,
they
can
do
a
bunch
of
different
things.
They
could
retire
them.
They
could
list
them
on
the
registry
for
sale.
They
could
give
them
to
a
third
party
broker
to
sell
them
and
then
they'll
transfer
those-
and
maybe
they
transfer.
C
C
C
C
They
provide
the
infrastructure
to
share
in-field
measurements,
digital
management
records,
credit
and
methodology,
methodology,
information
and
reports
on
an
open
access.
Digital
ledger
with
the
launch
of
the
ecocredit
module,
we're
doing
two
big
things:
we're
decentralizing
the
management
of
on-chain
assets
and
ecological
assets
and
we're
starting
to
digitize
the
long
paper
trail
of
information
which
goes
into
a
claim
and
storing
it
on
an
immutable
ledger
such
that
a
wider
set
of
actors
can
help
evaluate
and
come
to
an
agreement
around
claims
next
slide.
Please.
C
What
we're
doing
is
a
little
bit
different
and
we're
introducing
a
new
set
of
actors.
So
this
is
the
same
slide
that
I
showed
a
few
same
same
flow.
I
showed
a
few
slides
ago,
but
a
little
bit
different.
So
on
the
left,
you
can
see
the
project
life
cycle
where
a
land
steward
or
project
developer
will
register
a
project,
submit
documents,
establish
baseline
and
monitor
changes
and,
at
the
end
of
that
they're
ready
to
get
issued
credits,
while
registry
typically
might
issue
them
to
them
directly.
C
C
The
credit
class
creator
will
set
an
administer
and
a
set
of
issuers
who
will
mint
new
batches
of
those
credits
on
behalf
of
the
land
steward.
When
they
issue
those
credits,
they
can
issue
them
to
a
variety
of
different
actors.
They
can
issue
them
to
the
landscapers
themselves.
They
can
issue
them
to
project
developers
or
another
third
party,
that's
speaking
on
behalf
of
the
land
steward,
they
can
issue
them
directly
to
the
buyer
and
they
can
also
issue
them
directly
into
a
retired
state
or
a
non-retired
state.
C
Similarly,
buyers
and
credit
holders
are
now
able
to
transfer
and
retire
credits
without
having
to
go
through
a
third
party,
so
they
have
more
autonomy
of
managing
on-chain
assets.
So
if
a
buyer
wanted
to
claim
those
offsets
or
transfer
them
or
retire
them,
they
could
do
that
directly
without
having
to
put
in
a
request
to
do
that.
C
So
in
terms
of
who
would
be
a
credit
class
administrator
or
creator
or
issuer.
This
could
be
a
variety
of
different
actors.
It
could
be
the
registry,
that's
creating
credits
on
the
lan
store's
behalf,
but
the
responsibility
could
also
be
delegated
to
a
trusted.
Third
party
or
an
interested
party,
so
a
methodology
developer
or
a
project
developer,
which
typically
works
with
a
single
type
of
project,
might
want
to
take
on
administ
admin,
administering
and
issuing
credits
and
managing
those
assets.
C
C
C
So
on
the
left,
you
can
see
that
the
credit
class
that
ryan
was
speaking
about
earlier
and
on
the
right.
You
can
see
a
mock-up
of
what
it
would
look
like
to
start
to
digitize
some
of
these
processes.
So
within
each
of
these
sections
there
might
be
a
set
of
information,
but
you
you
could
be
storing
information
about
the
credit
class
or
the
methodology
or
the
project
itself
and
events
related
to
that
project.
C
So
the
credit
class
metadata
can
list
information
about
the
credit
definition,
the
project,
eligibility
requirements,
the
ghg
accounting
procedures
and
verification
requirements.
So
whether
or
not
additionality
is
included
whether
or
not
that
type
of
credit
allows
for
things
like
aggregate
projects
and
maybe
information
about
what
methodologies
are
allowed
to
be
used
for
that
type
of
credit.
C
They
manage
those
assets
on
behalf
of
buyers
and
trusted
third
parties,
and
they
also
provide
a
platform
for
scientists
and
researchers
to
work
together
to
create
methodologies
which
can
actually
measure
changes
in
ecological
state.
But
the
region
ledger
is
designed
to
be
an
open
platform
for
the
creation
of
assets,
and
so,
rather
than
having
a
single
registry,
manage
everything
we're
trying
to
decentralize
or
create
a
decentralized
system
where
the
public
can
help
manage,
assess
and
create
claims.
C
C
So,
what's
on
the
horizon
next
slide,
so
with
the
launch
of
the
ecocredit
module,
we
hope
to
showcase
how
it
can
be
used
to
trade
ecosystem
service
credits.
The
region
registry
hopes
to
get
voted
in
as
one
of
the
first
credit
class
creators
and
in
doing
so
we're
going
to
be
issuing
credits
for
our
historical
vintages.
C
B
Cool
and
on
the
ledger,
functionality
side:
you
know
we
can
talk
about
what
are
the
future
features
planned
for
the
eco
credits.
Module
upcoming
first
is
going
to
be
the
ability
to
list,
buy
or
sell
eco
credits,
so
we
actually
have
plans
and
there's
specifications
for
this
already
in
progress
for
how
we
can
build
into
the
ego
credits,
module
itself.
B
A
A
Essentially,
a
duplicate
of
the
configuration
and
everything
that
regen
mainnet
is
running
on
with
a
lower
voting
period,
where
you
could
test
out
specifically
the
ego
credit
module
without
using
live
funds,
and
also
there's
a
lot
of
fruitful
discussions
that
have
grown
out
of
the
signaling
proposal
posted
in
the
forum
and
there's
been
a
lot
of
activity
and
a
lot
of
really
thoughtful
responses.
And
we
would
like
to
continue
to
encourage
people
to
use
the
forum
as
a
way
to
express
ideas
and
to
discuss
opportunities
for
interoperability
or
improvements
on
the
eco-credit
module.
A
Things
like
that.
The
signaling
proposal
is
getting
that
particular
post
or
thread
is
getting
quite
long,
so
feel
free
to
open
up
new
threads
and
different
areas
and
new
ideas.
But
yeah.
We
would
really
like
to
encourage
people
to
use
the
form
as
a
way
to
continue
discussing
ways
that
they're
planning
on
using
the
eco-credit
module
ways.
A
If
you're
interested
in
a
grant
working
on
something
related
to
the
eco
credit
module
so
yeah,
we
we
look
forward
to
building
the
eco
credit
module
and
improving
upon
it
with
the
community
and
yeah.
We
would
like
it
to
be
a
community
effort
as
much
as
possible.
So
that
brings
us
to
the
end.
We
have
about
10
minutes
left
for.