►
From YouTube: Community Call | 10/15
Description
See slides here: https://www.slideshare.net/AaronCraelius/2019-1016-regen-network-community-dev-update-182848309
A
So
I
just
an
update
on
our
test
net,
the
regen
test,
1001
test
that
has
halted.
We
did
a
little
bonus
rounds
to
see
if
the
community
could
organize
a
parameter
change
for
to
make
jailing
list.
We
need
like
more
lenient
people
were
getting
jailed
very
quickly
and
it
just
didn't
make
sense
to
have
it
be
that
stringent
in
a
test
net
set
up.
A
But
it
was
a
good
test
of
that
functionality
to
see
you
know
how
it
worked.
Ethan,
maybe
you
can
say
a
little
more
specifically
what
happened
as
a
follow-up
for
the
test
net?
We're
working
on
telling
up
all
the
points
for
people
that
participated
in
preparation
for
the
next
test
net?
Is
there
anything
else?
You
wanted
to
say
on
that.
What
happened?
Yes,.
B
I,
don't
really
know
what
it
was
as
far
as
I
could
tell
having
done
a
thorough
analysis,
but
the
past
puzzle
basically
had
recorded
50%
of
the
last
hundred
blocks
to
be
signed,
and
then
that
means,
if
you
missed
50
blocks
in
a
row,
you'd
be
off,
which
I
think
was
pretty
harsh,
because
it
was
something
like
you
know.
Five
minutes,
you'd
have
a
restart,
could
knock
you
off
and
jail
you,
so
they
want
to
extend
it.
B
So
the
extending
power
was
like
I
think
in
the
last
thousand
blocks,
which
would
give
you,
like
you
know,
half
an
hour
or
an
hour
to
go
down.
We
got
jails.
The
problem
was
once
that
passed.
Suddenly
everyone
had
the
sliding
window
that
kept
track
of
the
sliding
they
had.
You
know
a
hundred
of
100
we're
there
now
so
there's
a
hundred
out
of
a
thousand
and
that's
below
fifty
percent,
so
every
single
validators
jailed
in
the
same
block
and
there's
no
validator
assassinate
so
helps
so.
B
B
A
A
So
we
were
intending
to
end
this
text
test
it
anyway,
and
now
we
have
a
new
schedule
for
our
community
death
calls.
So
now
we're
going
to
do
alternating
Wednesday's
we're
on
Wednesday
we'll
do
community
death
calls,
which
is
what
we're
doing
today
and
then
the
following
Wednesday
we'll
do
validator
planning,
which
will
be
led
by
our
lead
validators
course,
when
a
jane
who
will
be
helping
us
coordinate
the
test
net.
A
Yeah,
we'll
have
you
know,
join
us
next
week,
if
you're
interested
in
in
validating
on
the
next
test,
that
an
update
on
our
work
on
the
key
management
and
upgrade
community
groups
for
those
of
you
that
that
arms
you
haven't
been
following
our
updates.
We
have
to
grant
what's
yet
to
grants
basically
from
the
interchain
foundation
to
work
on
improve
key
management
functionality
and
upgrade
functionalities
to
get
merged
into
the
cosmos.
A
Sdk
we've
been
having
just
a
bit
of
trouble
scheduling
a
sync
up
with
the
cosmos,
SDK
team,
just
scheduling
issues
on
both
of
our
sides,
but
we
found
a
time
next
week,
next
Wednesday
at
10:00
a.m.
so
a
little
before
this
call,
where
we're
discussing
the
progress
on
both
key
management
and
upgrade
work
being
merged
into
the
cosmos.
Sdk
Ethan
has
recently
restarted
work
on
the
the
fee
delegation,
pull
request
for
key
management,
and
you
can
follow
the
latest
work
on
the
key
management
group
at
this
link.
A
B
Thought
you
sorry
mute.
I
did
a
web
assembly
integration
with
the
hold
on
some
stands
in
the
June
hackathon
in
Berlin,
and
this
is
a
follow
up
grant
to
work
on
that
working.
A
few
things
needed
were
like
small
Rossum,
builds
a
stable
library
to
build
them
with,
and
deterministic
Watson
bills
to
actually
have
a
product
build
environment.
We
also
want
to
enable
a
gas
metering
on
the
VM,
because
you
need
to
enforce
that
to
ask
me
doing
very
well
bench
market
and
integrated
with
the
cosmos
decay
in
a
clean
way.
B
So
the
current
path
I
started
researching
is
for
a
while
and
we're
using
Waze,
merwin,
rust
and
I
user
code
got
into
it
and
realized
that
most
of
their
functionality
is
not
exposed
and
go,
have
a
PR
actually
to
expose
update
their
capi,
but
that
was
not
merging,
so
I'm
actually
doing
the
whole
building
whole
thing
now.
So
my
pills
so
far
is
basically
built.
A
new
library
called
cause.
I'm
awesome,
which
is
basically
building
blocks,
to
build
it
and
then
also
have
a
virtual
and
simple
abstraction
using
their
VM
to
make
their
calls.
B
Not
generic
wasum
calls,
but
calling
are
two
functions
in
it
and
handle
those
are
the
two
functions
we
have.
So
it's
a
nice
high
level
abstraction
around
using
a
virtual
to
execute
contracts
and
then
work
on
go
bindings
right
now.
It
was
a
nice
fun
paying
work
at
the
C
code
C
to
to
rust,
especially
trying
to
pass
kV
store
structures
and
callbacks
and
state
cuz
islands.
We
actually
methods
with
some
state
to
ago
structure
all
the
way
through
these
piles
of
findings,
but
yeah.
B
It's
mostly
working
out-
and
that's
gonna
finish-
that
up
this
week,
hopefully
early
next
week
and
the
next
week
really
start
working
on
that
across
mr.
K
integration.
Much
more,
they
go
side
of
things.
I
can
show
you
what's
done
in
rush.
The
rest
up
is
mostly
finishing.
It's
just
being
polished
now
so
I'll.
Do
you
have
a
quick
screen
share
right
now?
A
boy
have.
A
I'll,
stop
my
share
and
and
just
kind
of
see
for
those
of
you
who
haven't
been
kind
of
following
our
work
on
this
high
level.
You
know
kind
of
overview
at
this
point
is:
is
that
we're
adding
webassembly
smart
contracts
and
into
the
cosmos
SDK?
So
that
would
let
us
write
smart
contracts
in
languages
such
as
rust,
so
really
exciting
work
there.
So
you.
B
So
yeah
see
this.
This
is
Qasim
awesome,
just
to
show
you
it
is
come
there
and
your
hub.
So
basically,
the
whole
point
is
to
end
up
lease
your
allocate
deallocate
from
every
management,
the
awesome
contract
we
work,
assembly
contract
hasn't
unit
in
a
handle.
You
can
upload
code
one
time
this
whole
hack,
MD
documentation,
honest,
which
we're
still
open.
B
We
were
working
group
on,
but
you
initialize
at
one
time
and
then
you
call
handle
on
it
multiple
times,
prams
being
a
bunch
of
passage
from
the
environment
like
its
own
addresses,
balance,
their
trusted
and
message
and
I'll
return
message,
returns
messages,
and
basically,
this
is
were
left
with.
Yes,
I've
been
put
these
two
functions
in
rust
to
them
and
you
have
access
to
a
KB
store.
B
You
could
also
input
in
a
different
language.
You'll
have
to
rest,
but
long
dissolve
in
Flint,
it's
a
very
simple
API
between
the
web
assembly
and
the
calling
function.
We
try
to
make
it
very
simple
for
the
purpose
it's
very
portable
and
if
you
want
implement
in
hospital,
you
could
input
as
Haskell
I'm
sure,
so
we
basically
built
this
out
and
then
to
get
started
on
this.
B
If
you
want
to
get
started
and
try
this
out
at
all,
like
I
said
the
the
underlying
part
works,
you
can
build
a
contract
right
now,
they're
starting
to
get
this
decay
yet
so
I've
asked
awesome,
awesome
template.
So
if
you've
got
stuff,
you
can.
You
know,
look
at
this
if
you're
using
a
recent
version
of
rusty
and.
B
B
B
Yeah,
so
we
can
look
inside
here
and
you
have
basically
have
this
library,
which
is
a
few
bindings
just
see
stuff,
and
the
contract
is
just
this
and
you
see
the
whole
contract
is
we
have
a
message
in
it
message?
State
variable
can
store
and
strengthen.
This
is
all
it
is
the
initialization
get
the
message
from
the
user
and
store
under
the
conflict
and
the
funder
set
to
this
parameter.
B
Signer
who
set
the
parameters
on
handle
escrow
see
if
the
signer
is
equal
to
verify,
restored
reefs
loaded
from
the
state
and
then,
if
it
is
then
returned,
I
send
a
message
same
transaction
so
as
an
escrow,
so
Glasgow-
and
this
is
like
40
lines
of
code.
Third,
twenty
lines
of
code
right-
and
this
is
a
fully
functional
module.
You're
loaded
contract
input
many
times
and
of
course
it's
testable,
so
you
can
write
unit
tests
set
of
stuff,
so
I
can
build.
Kaga
Watson
will
compile
this
thing.
B
Cargo
tests
will
build
it
and
you
have
a
full
thing.
You
can
just
create
basic
messages
here
and
make
mock
parameters.
Call
it
one
time
and
verified.
It
responds
sets
property
in
the
store,
that's
just
everything.
So,
basically,
if
you
want
to
run
tests,
you're
running
in
rust,
not
and
wash
them
just
in
rust,
you
run
the
test
natively.
It
doesn't
quite
a
huge
harnesses,
I
think
much
easier
solidity
to
this,
and
you
can
basically
get
full
coverage.
Just
as
if
you're
writing
a
go
SDK,
it
should
be
easy
to
write
and
test.
B
A
Let's
say:
let's
jump
back
a
couple:
slides,
okay,
yeah,
so
just
an
update
on
their
roadmap
to
main
net.
We
are
now
currently
planning
maenette
launch
in
quarter
one
of
2020.
Instead
of
quarter
four
of
2019,
we
it
doesn't
make
sense
to
do
a
maenad
launch
over
the
holidays
on
the
on
the
deb
side
of
the
progress
towards
main
net
remaining
blockers
towards
smooth
chain
upgrades
are
tracked
in
the
issue
that
I've
linked
there.
A
If
anybody
wants
to
check
that
out,
basically
one
of
the
key
things
we
want
to
make
sure
we
have
ready
before
we
launch
main
net,
is
the
ability
to
have
smooth
upgrades
of
our
blockchain
without
needing
to
dump
the
state
and
then
restart
a
new
chain.
The
reason
being
is
that
we
want
to
have
a
persistent
ledger
of
ecological
claims
so
that
people
can
see
you
know.
Basically,
the
history
of
one
claims
have
been
made
or
credits
have
been
issued.
A
A
C
C
C
Can
we
go
to
next
I
know
the
previous
one
that
one
okay,
so
there
you
can
see
some
relationships
and-
and
we
are
really
happy
because
it's
just
raw
data
and
we
are
getting
really
accurate
regressions,
and
so
this
means
that
we
can
monitor
certain
areas
which
is
I,
guess
great
part
of
Australia,
and
we
are
now
working
on
different
partnerships
also
to
do
the
same
in
Patagonia
Argentina
in
other
areas
of
Australia
and
with
many
like
millions
of
actors,
so
really
happy
to
to
do
this.
They
are
doing
holistic
management.
C
What
we
can
build
now,
instead
of
having
just
some
points
of
the
area
where
you
know
how
much
organic
carbon
you
have.
You
can
now
see
the
whole
variation
in
the
area
for
each
year
next,
and
then
we
can.
We
can
also
compare
between
years
and
see,
which
are
the
areas
of
the
landscape
that
are
sequestering
carbon
and
which
areas
are
losing
their.
You
have
like
from
red
to
yellow
the
losses
and
between
two
years
from
yellow
to
green
the
games
in
southern
and
carbon.
C
This
is
in
tones
per
pixel,
okay
and
next
there's
another
pilot,
we're
working
in
it's
for
very
fine
raising
from
ships
in
Northern
California.
They
are
like
two
organizations.
One
has
farms
with
vineyards
and
they
are
doing
organic
vineyards
and
they
want
to
show
to
the
world
that
they
are
increasing
for
organic
carbon
and
they're.
Also
there's
another
organization
that
has
chips
and
they
they
they
take
the
shape
to
different
fields
from
other
owners
like
vineyards
or
for
fuel
reduction
also,
and
they
there's
a
study
from
the
University
of
Davis.
C
So
we
had
really
good
results
and
just
from
NDVI
with
drops,
and
we
were
able
to
verify
that
their
ships
were
grazing
in
a
farm
and
so
for
next
winter
they
are
going
to
expand
the
sampling
and
we
are
going
to
correlate
over
more
fields
in
order
to
build
a
model
over
the
area.
So
next
I
think
yeah,
there's
just
a
demo
how
we
see
from
one
week
to
the
next
one
in
the
parcels
where
ships
were
grazing,
you
can
see
NDVI
drops,
and
so
it's
it's
really
quite
a
file.
A
The
basically
have
a
specification
in
progress
they're.
Our
product
team
is
working
and
collecting
more
user
requirements
from
our
pilot
partners.
To
improve
this
specification,
we
want
to
build
basically
the
most
best
most
flexible
ecosystem
service
credit
registry
that
exists,
and
we
hope
it
will
be
used
for
many
different
types
of
credits,
including
carbon
credits,
but
not
limited
to
carbon
credits.
A
We're
looking
at
biodiversity
credits,
potentially
water
credits,
there's
you
know
many
different
possibilities
for
outcome
system
services
can
be
quantified
and
incentivized,
and
our
design
scheme
was
working
on
mock-ups
for
the
first
version
of
the
credit
registry.
So,
hopefully
we'll
have
more
updates
on
that
in
the
coming
weeks.