►
From YouTube: Community Development Call #11
Description
Join the Regen Network for biweekly calls open to the public. Led by Chief Technology Officer Aaron Craelius, these calls are designed to update our community on the latest Regen Network news. We look forward to seeing you there!
A
Right,
that's
a
little
better,
yeah,
fantastic.
So
on
today's
call
we're
going
to
share
our
usual
update
updates
from
the
dev
team,
the
science
team
and
the
design
team
each
given
just
a
brief
little
update.
It's
been,
it's
been
the
holidays
and
even
though
things
have
been
slow,
lots
of
big
things
have
been
happening
and
yeah
looking
forward
to
sharing,
and
then
we
can
have
a
little
bit
of
question
answer
and
comment.
Go
free
folks
who
are
on
to
just
chime
in
if
you've
got
questions
or
comments.
A
A
Cool
so
first
things:
first
just
see
there
we
go.
We
had
a
fun
pick.
Your
favorite
salsa,
solstice
holiday
treasure
hunt
that
Joe
Brewer
led
and
he's
going
to
be
announcing
both
of
that
and
we'll
we'll
add
those
results.
They're
sort
of
the
official
incentivized
test
at
point
tally
that
R&D
incas
is
keeping
so
we'll
have
an
announcement
about
that
next
week
during
the
community
community
validator
call,
so
it
was
pretty
fun
to
watch
that
happen.
Some
encoded
I'm,
not
sure
anybody
got
Joe's
crazy,
encoded
message.
A
Cool,
so
on
the
science
side,
some
of
you
may
have
seen
me
tweeting
about
this,
but
one
of
the
exciting
things
to
chat
about
that.
You
know
I
kind
of
wanted
to
spend
a
moment
on
was
just
sharing
some
progress
and
participation
on
our
end
with
open
team
and
for
those
of
you
who
aren't
familiar
open
team
is
a
collaborative
open
source
group
that
is
doing
development
in
science
and
technology,
open
science
and
technology
and
is
funded
by
the
foundation
for
food
and
agriculture,
research,
which
is
fed
a
federally
funded
organization.
A
So
it's
really
cool
Gisele
and
I
got
to
sit
in
and
and
have
some
geeky
conversations
about
measurement
methodologies.
All
of
and
then
just
to
sort
of,
let
folks
know
I
mean
we're
both
participating
on
the
science
side
of
things
with
Gisele,
mostly
leading
that
and
me
sort
of
supporting
her
in
methodology
development.
A
But
our
main
role
in
open
team
is
actually
data,
structure
and
interoperability,
because
we
have
all
of
these
different
groups
who
are
looking
to
collect
data
and
then
use
it
for
a
variety
of
different
applications,
the
sort
of
highest
order
of
application
being
to
provide
proof
of
claims
for
ecosystem
service
markets.
But
there's
also
the
need
to
use
this
same
data
for
farmer
decision
making
to
improve
performance
and
yields
and
get
information
to
you
know
local
and
national
governments
etc.
A
So
this
data
is
going
to
be
used
and
reused
and
so
there's
a
whole
sort
of
structure
of
permissions
and
data
marketplaces,
etc.
That
we're
sort
of
digging
into
and
a
big
plain
playing
a
lead
role.
I
would
sort
of
note
that
I'm
very
excited
about
this
group,
because
I
think
it's
a
really
fantastic
opportunity
for
proof
of
stake
to
be
supplanting
the
old
sort
of
corporate
and
governmental
adversarial
that
an
MA
took
created
or
sort
of
data,
interoperability
claims
and
agreements.
So
it's
a
really
exciting
place
to
be
so
I'm,
not
sure.
B
A
Work
with
them
through
the
rest
of
the
year
and
we're
actually
we're
part
of
it.
The
the
grant
is
a
three
year
grant
process
so
we'll
be
working
with
these
folks
for
for
the
long
term
right
now,
I
wanted
to.
Hopefully
it
looks
like
Aaron's
on
I
wanted
to
give
a
quick
update
on
the
dev
side,
I'm,
not
equipped
to
give
this
update
really
in
any
sort
of
depth.
A
But
there's
been
a
bunch
of
movement
over
the
holidays
on
a
what
has
turned
out
to
be
a
perennial
long
term,
discussion
and
debate
in
there
in
the
cosmos,
SDK
community
about
amino
versus
proto,
death,
protobuf
and
there's
been
a
substantial
amount
of
movement
and
region.
That
network
is
sort
of
taking
leadership
in
that,
and
so
maybe
Aaron
and
I
could
pass
it
over
to
you
or
Ethan
I,
see
you've
just
hopped
on
if
either.
C
Aaron
details
but
I
can
say
briefly
the
motivation
I
mean
it's
been
an
issue
for
two
three
years
in
that
you
can
build,
go
see,
allies,
you're,
very
powerful,
very,
very
powerful
for
a
cosmos
decay,
but
their
solution
for
JavaScript
client
is
not
so
hot.
This
is
how
they
have
a
custom
encoding
scheme,
which
was
never
really
imprinted
in
JavaScript
and
actually
is
not
really
amenable.
It's
a
very,
very
go
specific
library,
so
it
works
right
answers.
C
Go
was
really
hard
to
port
to
foreign
clients
and
there's
been
you
know,
a
very
slow
development
of
any
sort
of
friend,
apps
bindings
for
JavaScript
or
Swift
or
Kotlin
or
Java,
or
anything
like
that.
So
one
of
the
things
we
had
one
of
works
years
were
one
and
basically
backwards.
Pat
ability
we
need
to
have
backs
private
building
and
he
wanted
nice
easy
to
use
ways
of
building
standard
web
apps.
They
talk
to
botching
like
by
3m,
which
does
have
libraries
for
its
I,
made
it
ugly
RLP
encoding
scheme
anyway.
C
D
Yes,
so
we've
been
working
on
creating
some
protobuf
encoding
files.
I've
been
working
together
with
some
developers
from
the
cosmos,
SDK
team
and
we've.
We
started
by
experimenting
with
different
approaches
and
just
kind
of
crystallizing
on
on
the
approach
that
we
are
going
to
take,
and
it's
it's
likely
that
the
first
prototypes
will
get
merged
into
the
cosmos
SDK
master
today
or
tomorrow,
and
we're
taking
an
incremental
approach
to
the
migration.
So
we're
gonna
go
module
by
module
first
working
on
migrating,
the
state,
encoding
and
then
second
we'll
add
clients
encoding.
D
So
just
just
the
sum
of
adding
state
encoding
will
make
backwards,
compatibility
of
the
state
store
and
thus
smooth
upgrades,
more
seamless
and
then
and
then
adding
the
clients.
Encoding
role
will
make
it
really
easy
for
your
having
mobile,
swift's
or
or
Kotlin
Android
clients
that
are
basically
just
natively
native
that
use
protobuf
and
we're
hoping
we
have
sort
of
an
ambitious
timeline.
But
we're
hoping
to
get
this
done
this
month
and
at
least
the
current
talk
is:
maybe
they
even
try
to
get
this
in
the
point
three
eight
cosmos
has
to
here
release.
A
Thanks
Aaron
things
Ethan
and
just
to
weave
this
back
in
with
our
roll
and
open
team
and
our
business
development
strategy.
This
was
a
blocker
for
us
to
be
able
to
provide
to
use
region
ledger
to
support.
You
know,
applications
you
know
in
that
are
written
in
JavaScript,
etc.
To
be,
you
know,
creating
interoperability
and
sort
of
building
out
our
ecosystem.
A
A
C
Yeah
I
really
should
last
I
think
you
last
time
that
there's
there's
public
post
about
it.
It's
out
there
0
5,
2,
's
out
there
and
it's
time
to
use,
got
some
feedback
on
it
to
people
interested
in
building
on
it
and
try
it
out
that
tutorial
to
use
it.
I
got
some
feedback.
One
developer
built
out
here.
C
She
20
token
contracts
using
it
and
give
me
a
lot
of
feedback
on
API
design,
which
it
took
in
to
build
a
0-6
release,
which
has
some
improvements
in
security,
I
verify
more
blocked
on
German
ISM,
like
any
it
filters
out
all
floating-point
operations,
upgraded
and
there's
new,
new
caching
and
stuff
anyway.
A
new
version
of
the
underlying
libraries,
so
I
got
some
proof
it's
in
there,
as
well
as
a
clean
API.
They
made
love
consistent
and
I'm
building
out.
There's
a
awesome,
awesome
page
cost
cause
I'm
awesome.
C
Awesome
wasn't
out
there
for
to
gather
all
the
contracts
and
trying
to
retouch
people
like
me,
starting
to
move
on
telegram,
so
I'll
be
putting
out
some
more
sample
contracts
and
helping
anyone
else
that
wants
to
put
them
out
and
some
more
tutorials.
How
to
use
it
to
show
how
to
use
more
use
cases,
people
excited
about
Yoshi,
2000,
Kenney
contracts
index
and
a
number
of
bigger
features
on
the
pipeline
for
Regions
use
cases.
C
But
yes,
right
now,
just
helping
fully
get
on
board
is
and
try
and
build
a
community
there
and
hope
to
launch
in
about
two
weeks
or
so
a
public
test
net
demo
net
with
no,
you
know
so
people
can
share
it.
One
public
IP
address
people
can
use
a
public
at
URL.
If
you
can
use
it
right,
contracts,
upload
them
and
share
them
with
their
friends.
So
if
you
want
to
are
contracts,
come
enjoying
there's
a
cosmos
and
tell'em
channel-
and
hopefully
we'll
have
my
stuff
too-
for
reach
and
test
at
lunch
main
at
lunch.
A
C
C
C
Document
and
we
took
a
design
document
and
built
it
in
our
system.
You
have
to
demo
it
the
reason
for
that,
not
because
the
best
thing
ever,
but
because
it's
very,
very
well-known
and
almost
every
project
wants
own
token,
and
this
is
one
the
highlight
requested
thing.
So
when
you
build
a
set,
people
extend
it
then
minting
abilities,
bonding
curves,
a
lot
of
things
build
off
it
so,
rather
than
trying
to
fit
in
the
wheel,
we
said:
let's
build
things.
People
like
so
I
think
porting.
A
Definitely-
and
it
does,
it
feel
like
there's
an
opportunity
to
sort
of
build
network
effect
and
community
around
woz,
and
you
know
you
and
I
were
chatting
the
other
day
about
how
cool,
like
common
stack,
is,
etc,
so
sort
of
bringing
some
of
those
developments
and
tools
into
the
into
the
Wazza
ecosystem.
B
A
C
C
I
mean
they're,
not
gonna,
learn
this
and
build
it,
there's
their
shorten
their
charm
people.
Why
I've
seen
there
is
sketching
slowly,
you
definitely
shorter,
but
there's
a
lot
of
hidden
stuff
there.
It's
really
card
and
loaded,
you
know,
is
magic.
Don't
you
magic
it
can
it's
not
clear.
So
I've
only
seen
these
things
and
actually
trying
to
test
things
and
make
it
you
know,
bulletproof
seems
much
easier.
Actually
with
awesome.
Awesome,
it's
hard
to
write
your
sample,
but
you
have
you
can
see
it.
You
can
test
it.
C
You
have
much
more
rather
than
feeling
aetherium
things
just
happen
somehow
and
it's
easy
to
write
it,
but
it's
hard
to
audit
it.
So
anyway,
I've
looked
at
some
etherium
contracts
from
centers
game
project
to
have
out
there
and
definitely
here
supporting
many
of
them
to
cause.
Also
important
is
the
community
building
that
to
and
help
people
build
that
stuff
out.
They're,
not
just
me,
so
we.
A
C
Reach,
and
hopefully
we
get
more
people
what
expires
macaws
maasdam
is
one
thing
about
cosmos.
Sdk
ecosystem
is
supposed
to
build
ecosystem
of
sharing
modules
and
the
truth
is
few
zones
of
shared
modules.
One
reason
is:
there's
no
real
incentive
to
their
source
code
open
source,
but
you
have
to
you
know
they
don't
actually
make
it
easy
to
take
the
module
out
in
this
copy
if
you
want
to.
C
But
the
other
point
is:
if
you
look
at
these
things,
there's
you
know
0:34
modules,
there's
six
modules,
there's
seven
modules
once
based
on
master,
which
is
38
pre
58
and
they
keep
changing
api's,
and
these
modules
need
many
hours
or
days
have
work
to
port
from
one
to
the
other.
So
it's
fragmented.
Already.
C
These
people,
you
know,
wrote
a
contract
three
months
ago,
doesn't
work
with
a
new
net
other
net
that
was
written
last
month,
so
having
a
stable,
API
I
hope
to
have
that
soon
and
that
will
allow
these
contracts
to
keep,
keep
growing
and
growing
and
then
easier
to
share
them
and
having
one
platform.
People
can
share
them
on
and
having
a
public
test
net
unless
people
to
share
their
contracts
in
one
place.
C
So
I've
been
also
building
out
tooling
for
uploading
modules,
two
crates
I/o
for
rust
and
doing
distributed
code,
abuse,
classic
code
abuse
and
putting
a
tooling
out
there
and
documenting
how
to
use
this
really,
which
is
reusing
other
tooling,
but
really
trying
to
build
a
system
that
encourages
sharing
Reata
ting
reuse
from
this
day
one.
So,
hopefully
we
can
get
more
people,
products,
building
code
and
sharing
each
other
I
I.
D
Also
want
to
chime
in
on
that
concept,
the
PR
that
was
open
today
to
start
the
initial
prototype
off
integration
into
cosmos.
Sdk
includes
a
backwards
compatibility,
checker
called
buff,
so
all
of
the,
although
the
part
about
files
in
cosmos,
SDK,
will
be
tested
for
backwards
compatibility
going
forward,
at
least
that's
the
current
plan
and
I
think
that
will
help
with
sharing
modules
that
are
in
and
go
or
that
could
possibly
have
API
compatible
implementations
that
are
in
rust,
but
have
the
same
proto
files,
so
I
think.
C
Definitely
ups
client
side
because
they
are
definitely
client
side,
clients
and
wallet
have
up
to
every
time
they
update
the
version
they
break
all
the
wallets.
That's
a
change,
but
internally
may
break
the
internal
fbi's,
so
my
module,
those
written
for
hackin
I'm
had
to
be
upgraded
again
and
again
and
again
and
where's.
My
master.
I've
definitely
found
like
every
three
weeks.
It
changed
something
an
internal
master.
D
A
A
C
A
E
E
So
I'll
give
a
little
bit
of
an
update
of
just
where
we've
been
at
from
our
you
know,
going
from
design
to
development
towards
main
net
launch.
You
know,
while
we
we
started
with
some,
you
know
low
fidelity,
mock-ups
and
kind
of
just
exploring
the
space
and
and
looking
at
you
know
what
you
know
well,
I
guess
let
me
take
a
step
back,
you
know
so
there's
there's
what
we
heard
from
Ethan
and
Aaron
is
more
on
the
you
know,
region
ledger
and
this
sort
of
infrastructure.
E
E
Protect
biodiversity
and
and
and
practicing
regenerative
agriculture,
you
know,
and
the
the
situation
in
Western,
Australia
or
in
Australia
in
general,
is
that
there's
many
different
states
in
Australia.
They
all
have
their
own
compliance
and
regulatory
markets
for
issuing
credits
and
and
and
they'd
like
to
find
I'd
like
to
work
with
us
to
kind
of
to
make
it
easier,
rather
than
having
to
comply
with
different
protocols
and
standards,
and
we
could
potentially
build
out
an
application
that
allows
them
to
issue
their
own
credits
and
in
their
own
way
and
work
with
their
own
buyers.
E
And
so
this
first
application
that
we'd
like
to
build
is
the
issuance
of
biodiversity
and
carbon
credits
and
and
where
the
the
deal
flow
happens
offline.
So
the
payments
for
those
credits
happens
somewhere
else,
not
on
the
platform
initially,
and
it
could
happen
on
the
platform
in
the
future,
but
that
you
can
confirm
ownership
so
Gregory.
E
If
I
was
to
sell
you
some
carbon
credits,
we
could
look
online
and
you'd
see
your
name
associated
with,
or
your
organization
associated
with,
those
credits
that
were
issued
and
and
what
we're
doing
now
is
we're
kind
of
moving
from.
We
are
moving
from.
You
know
the
design
side
and
moving
into
implementation,
and
it's
a
you
know,
working
with,
and
so
the
these
two
screenshots
here
one
is
in
thigma,
where
you
know:
we've
got
kind
of
getting
higher
fidelity,
mock-ups
and
then
we're
moving
towards
development.
E
This
is
a
screenshot
from
an
application
that
we
have
set
up
called
storybook
that
allows
us
to
build
out,
and
these
react
components
that
will
then
compose
into
the
application
itself.
So
I'll
stop
there
and
Ron
is
also
on
the
call
here:
who's
leading
up
the
product
and
yeah
Ron.
Do
you
have
any
extra
any
additional
words
you
want
to
add
or
did
I
cover,
most
of
it
I.
F
On
top
of
the
strengths
of
you
know,
the
whole
tech
stack
from
automating
contracts
in
the
future,
automating
verification,
issuance
and
selling
of
credits,
and
all
of
these
is
kind
of
fancy.
At
the
end
of
the
day,
technologies
will
would
translate
to
actual
funds
going
to
land
stewards
on
the
ground
in
this
project.
Here
you
have
indigenous
communities
in
Western
Australia
that
are
actually
various
practices
to
maintain
the
biodiversity,
the
bird
habits
at
the
fauna
and
that
will
send
to
a
lot
of
weather
regenerative
agriculture
work
really
important
work
for
for
our
planet.
E
This
and
this
connects
with
our
work
that
we
did
at
see
her
the
time
that
we
spent
at
TNC
and
towards
the
end
of
T
and
C.
We
put
up
a
page.
You
know
like
a
landing
page
that
garnered
interest
from
from
various
land
stewards
around
the
world
and
a
lot
of
a
lot
of
farms.
There's
just
been
a
lot
of
seller
interest
like
when
you
say
seller.
It's,
like
you,
know,
land
steward
interest
who
want
to
be.
A
A
A
little
bit
of
our
update
I'm,
just
looking
forward
we're
going
to
be
working
to
announce
the
January
incentivize
test
net
D,
ETA
Oh
David
tells
us
as
we
can.
It's
a
you
know
complex.
As
everybody
knows,
so
it
may
be
a
partial
announcement
or
it
may
be
the
full
full
package
next
week.
So
we're
gonna
be
talking
about
that
on
the
community
test,
net
call
with
Joe
and
Chris
and
our
great
validators
a
couple
of
appearances
coming
up.
A
I
didn't
put
the
dates
on
either
of
these,
but
natural
capital
project
has
an
event
in
palo
alto,
california,
that
daniel
and
maybe
others
are
going
to
be
attending,
and
then
christian
and
Sarah
are
gonna,
be
at
Hong
Kong
blockchain
week
coming
up,
I
think
that's
in
February,
early
February!
So
yeah,
that's
our
that's
our
show.
Does
anybody
have
any
questions
or
comments
before
we
to
wrap
up.
A
In
the
in
the
open
team-
yes
yeah,
so
so
our
role
is
we're
we're
sort
of
getting
paid
to
do
some
specific
work
on
data,
interoperability,
data
management
and
then
moving
and
ecosystem
service
markets.
So
building
the
tools
for
people
to
use
to
buy
and
sell
digital
representation
of
the
public
goods
or
positive
externalities
of
good
land
management.
And
so
that's
the
specific
role
which
is
you
know,
which
is
cool,
because
it's
right,
you
know
it's
it's
right.
What
we're
trying
to
do,
yeah
and
so
in
open
team.
A
We
have,
you,
know,
sort
of
like
an
all
community
meeting
twice
a
year.
The
next
one
is
going
to
be
coming
up
and
we
had
one
in
September.
The
next
one
is
coming
up
in
March,
we'll
see
if
it
falls
before
after
main
net
launch
yet
to
be
determined.
But
then
you
know
moving
forward
we're
essentially
we're
collaborating
with
people
who
are
building
sensors
people
who
are
building
scientific
methodologies,
people
who
are
researching
best
practices
and
agriculture
and
land
use.
In
order
to
sort
of
bring
that
data
into
structured
contract.