►
From YouTube: CasperLabs Community Call
Description
Rewards Distribution presentation & status update.
A
A
A
A
All
right,
let's
get
it
started.
Can
you
see
my
screen?
Okay,
yep
excellent,
so
good
morning,
good
afternoon,
good
evening,
wherever
you
may
be
listening
to
this
I
hope,
you're,
safe
and
secure
and
healthy
and
I
hope
you're
able
to
keep
yourself
occupied
and
not
feeling
too
lonely
during
this
quarantine
time,
I
myself,
I'm
coming
to
you
out
of
San
Diego
here,
San
Diego,
California
and
I'm
quarantine,
eing
with
quite
a
few
of
my
children,
both
biological
and
non-biological.
A
So
we've
got
a
house
full
of
ten
folks
here
and
we
are
keeping
ourselves
occupied
with
a
variety
of
yard,
games
and
the
like
and
with
our
pets.
We
have
lots
of
pets
here
too.
So
we've
been
weathering
this
quarantine
now
for
five
weeks
here,
where
we've
all
been
sheltered
in
place
in
Southern
California,
so
wherever
you
are
I
do
hope,
you're
well
and
thanks
for
joining
and
listening
I'm
going
to
provide
the
engineering
status
and
update
on
Casper
labs
today.
A
So
you
know
before
we
get
into
the
written
status
and
for
those
of
you
that
dialed
in
last
week
you
know
that
we
did
some
big
changes
in
the
engineering
team.
We
restructured
the
engineering
team
into
a
single
organization.
We
shortened
our
sprints
I'm
happy
to
report
that
we
exited
our
first
sprint
with
a
pretty
nice
burn
down.
Considering
it
was
the
first
sprint
the
planning
process
went
very
smoothly.
We
are
marching
towards
our
May
release
that
is
going
to
be
released,
hopefully
in
middle
of
May.
I.
A
Think
on
my
birthday,
actually
fun
fact
and
that's
my
birthday
present
is
the
is:
is
contract
headers?
That's
what
I
want
for
my
birthday,
we're
going
to
be
delivering
contract,
headers
and
very
nice
features
in
the
execution
engine
for
a
smart
contracting
development
and
in
collaboration
with
that
feature,
we'll
also
be
doing
a
good
amount
of
work
on
the
examples
right
to
port
port
those
examples
over
to
the
new
format.
All
the
examples
in
a
repository,
our
documentation
will
need
to
be
updated.
A
So
this
there's
a
an
amount
of
work
that
goes
along
with
the
smart
contract
headers
themselves.
So,
let's
kind
of
dive
in
to
our
our
update
so
enter
the
second
sprint
on
Monday.
We
have
now
moved
clarity
to
point
to
the
test
set,
so
those
of
you
that
go
to
clarity,
cazuelas
of
I/o,
you
are
now
interacting
with
our
test
net.
In
our
20,
wonderful
validators,
you
can
fund
accounts
there.
You
can
send
deployments
there.
The
deployed
Casa
absol
endpoint
has
is
pointing
now
to
test
net
it
points
to
our
validating
nodes.
A
There
are
additional
validator
nodes
that
you
can
also
choose
to
send
your
deployment
to
the
turnaround.
Time
on
transactions
is
still
pretty
slow
in
test
net
and
the
reason
for
this
is
there
is
no
deploy
gossipping.
So
only
after
we
release,
deploy,
gossiping
and
upgrade
the
test
net.
This
will
not
be
a
breaking
change.
As
far
as
I
know,
we
do
not
need
to
restart
state,
we
might
need
to
with
contract
headers
OFI
deployed
contract
headers.
We
might
need
to
restart
the
testament,
I
think
Ashok.
You
need
to
find
that
out.
A
If
it's
a
new
genesis,
we
need
to
go
through
that
we'll
probably
important
to
know
whether
the
contract
header
has
changed.
That
will
come
in
may
will
also
happen
with
deploy
gossipping.
So
we
have
to
figure
that
out
and
if
a
state
bounces
needed
so
we'll
have
those
features,
and
so
without
deploy
gossipping,
it
does
take
a
little
bit
longer.
You
have
to
wait
until
the
node
that
reseed
your
deploy
is
picked
us
leader,
and
so
there
can
be
a
slow
down,
but
the
transactions
are
finalizing.
A
All
right,
so,
let's
talk
about
performance
and
the
network
is
stable.
Nodes
are
in
perfect
sync,
we
have
one
that
is
rejoining
right.
One
that's
been
having
some
challenges.
I
think
he's
been
playing
around
with
his
note
a
bit,
but
we've
got
a
rank
of
twelve
thousand
six
hundred
eighty
eight
blocks
yesterday,
so
he
probably
would.
A
All
moved
clicking
down
will
be
gradually
getting
moved.
Okay
sounds
good.
It
would
be
good
for
us
to
track
how
long
it
takes
for
them
to
install
an
upgrade,
so
I
want
to
track
which
nodes
install
the
upgrade
first
and
fastest.
So
we
should
be
tracking
that
KPI.
How
long
does
it
take
for
them
to
all
upgrade
it's
important
for
us
to
know
that
a
definite
has
been
decommissioned,
so
the
dev
net
is
no
longer
functioning.
A
We
have
moved
fully
to
testament
current
focus.
So
as
part
of
the
big
changes
we
made
on
April
15th,
we
have
kicked
off
a
full
rust
implementation
and
we
have
started
working
on
the
initial
consensus
container
and
we've
started
implementing
the
protocols
state
data
type
and
we've
also
started
looking
at
the
storage
model.
It
is
our
intention
to
provide
state
pruning
and
checkpointing
as
part
of
our
main
net,
and
so
that
is
definitely
a
big
piece
of
the
storage
story
for
us.
A
In
the
contract
run
time,
we
are,
that
is
the
execution
engine
formerly
known
as
execution
engine
we're
implementing
contract
headers
and
then
we're
also
working
on
figuring
out
our
gas
basic
error
or
transaction
pricing
model.
How
we're
going
to
basically
account
for
computation,
storage
and
bandwidth
test
and
sree
sree
has
gone
through
a
small
reorg
tom
Vasile,
who
many
of
you
probably
know
is
now
leading
up.
The
sre
group
he's
done
tremendous
work,
helping
us
launch
the
test
net
working
with
me
on
all
of
the
weekly
workshops.
A
Getting
everybody
trained
and
now
he's
got
the
production
lead
infrastructure
set
up.
So
we've
got
monitoring
of
the
test
net
around
the
clock
and
24/7
support.
Sorry,
we'll
also
be
taking
a
bigger
role
in
ensuring
that
our
code
meets
their
guidelines
for
production
readiness.
We
are
going
to
consider.
We
consider
testing
it
as
our
production
system.
We
have
alerting
and
monitoring
in
place.
So
when
a
validator
node
experiences
problems,
the
SRE
team
is
alerted
of
that.
So
our
validators
can
option.
A
A
A
A
Although
Inc
presents
to
me
like
a
completely
separate
language,
but
it
really
is
a
rust
DSL,
so
we'll
be
doing
something
similar,
maybe
not
as
extensive
as
as
link,
but
definitely
something
that
will
make
it
easier
for
smart
contract
creation,
that's
something
that
we're
designing
and
then
we're
also
doing
a
prototype,
CLX
integration
with
exchanges,
so
we
have
found
some
open
source
exchange
software
remind
me
of
the
name
of
it,
I've
forgotten
again
our
shock.
Do
you
remember
what
the
name
is?
Can
you
look
at
the
name,
so
you
can
put
it
in
here.
A
And
on
the
ecosystem,
front-end
economics,
so
economics,
we
are
updating
the
tech
spec
for
the
reward
distribution
to
include
that
the
cartel
resistant
rewards
distribution
mechanism
that
we
have
we're
going
to
update
our
documentation
for
that
and
we're
also
doing
an
integration
with
chain
link.
So
we're
designing
that
integration.
We
want
to
represent
transaction
fees
in
Fiat.
It's.
A
Q,
that's
a
so
yeah.
Let's
update
this
to
include
Ruby
cubes
that
we're
prototyping
with
Ruby
cube,
Ruby
cube
is
an
open
source
exchange
platform.
Software
and
quite
a
few
exchanges,
use
this
open
source
software
to
bootstrap
their
exchanges,
and
so
we're
going
to
just
do
an
integration
with
the
open
source
software
to
see.
If
there's
any,
you
know
things,
we
need
to
be
concerned
about.
A
We're
also
announcing
an
integration
with
chain-linked.
Today,
it's
gonna
be
hitting
the
press
releases
like
I,
said
we're
using
the
chain
link
Oracle
system
to
help
grant
it
give
price
for
basically
Fiat
prices
for
our
customers.
This
will
help
them
budget
better
right,
the
cost
of
execution
going
from
tokens
back
and
forth
and
internalizing
all
that
the
exchanges
for
tokens
it
just
makes
it
harder
for
businesses
to
deal
with
so
we're
just
gonna.
A
Take
that
problem
away
from
them
and
let
them
get
consistency
in
pricing
in
fiat,
we're
doing
weekly
workshops
till
those
are
continuing
to
happen,
but
they,
our
timings,
are
a
little
bit
better
they're,
not
as
great
for
a
Pacific,
but
they
are
great
for
everybody
else
right.
So
if
we
want
to
do
something
in
Pacific
time,
you
can
always
ping
me
on
discord
or
telegram.
If
you
want
to
do
a
one-off,
Ashok
and
I
and
any
number
of
the
you
know,
us-based
developers
can
can
hold
a
workshop
for
you,
but
otherwise
there
is
7
a.m.
A
A
We've
heard
feedback
from
the
community
that
you
want
to
know
more
about
what
we
are
going
to
be
doing
for
community
building,
so
I'm
going
to
be
inviting
sanaya
here
and
she'll
present.
You
know
some
stats
around
what
our
engagement
looks
like
and
how
how
it's
improving
week
over
week,
we
have
some
KPIs
that
we've
been
tracking
and
I'm
going
to
be
working
with
the
team
to
try
to
operationalize
some
of
those
keep
you
guys
so
ash.
Oh
look
at
that
coming
your
way
there
definitely
some
kpi's.
We
want
to
start
operationalizing
and
tracking.
A
Those
carefully
sounds
good
who's
presenting.
Oh
no,
are
you
presenting
today.
B
So
well,
as
a
meta
mentioned,
we
are
doing
a
lot
of
work
around
the
integration
of
steam
link
and
you
know
so
previous
has
said
many
times.
This
is
a
critical
piece
of
our
infrastructure,
because
the
first
step
toward
sprite
stabilization,
we
intend
to
you,
know
fix
prices
in
yet,
and
you
know
this
entails
quite
a
bit
of
design.
So
you
know
what
I
want
to
describe.
Is
you
know
how
we
actually
plan
on
carrying
this
out
rather
than
the
you
know,
rather
than
rather
than
the
economics
to
it?
B
B
Nevertheless,
you
know
it
is
you
know,
for
historical
reasons.
You
know
sort
of
centered
around
here,
and
you
know
this
presents
naturally
some
challenges
for
us,
because
you
know
it
seems
it's
naturally
forward
is
going
to
be.
Essentially,
an
implementation
of
you
know,
chain
links
original
white
paper
in
a
you
know
on
our
platform,
right
I
mean
so
because,
once
we
broke
down,
you
know
all
the
moving
pieces
in
such
a
system,
it
you
know
it
more
or
less
matched
with
a
chain
link.
Originally
envisioned.
This
is
generalized.
B
You
know,
system
of
Oracle's,
and
you
know,
in
terms
of
the
process
this
week
is
going
to
be
dedicated.
I
suspect,
mostly
to
sort
of
knowledge
exchange
with
a
chain
links.
Engine
years
to
make
sure
is,
if
you
understand
the
you
know
where
the
gaps
in
their
capabilities
are
over.
The
gaps
in
our
capabilities
are
so
that
we
can
actually
no
plan
no
plan
to
fill
those
gaps
subsequently
were
the
course
of
the
next.
B
You
know
two
or
three
weeks
we
are
going
to
be
right
and
high-level
design
document
and
I
believe
old,
shared
something
like
that
for
the
system.
Previously,
these
community
calls,
but
this
thing
is
going
to
be
more
detailed
right.
It's
not
going
to
be
so
detailed
that
you
know
you're
going
to
be
able
to
go
into.
You
know
extreme
detail
on
every
single
contract
system,
but
will
be
able
to
describe
more
comprehensively.
You
know
what
the
pieces
are
supposed
to
do,
how
they
link
together.
You
know
how
you
know
the
platform
reaches
consensus
on.
B
You
know
the
work
of
the
system
you
know
and
how
the
interfaces
specifically
visit
FIRREA,
because,
obviously
you
know
work
chain
links,
oracle
nodes,
reliant
payments
in
link.
The
link
is
an
experience,
so
that
me
deserve
as
the
bridge
to
do
this
so
over
the
next
two
or
three
weeks.
We
hope
to
get
that.
You
know
completely
filled
in
at
this
high
level
to
the
point
where
we
can
take
it
to
engineering
and
confirms
as
the
overall
design
sound
you
know
compatible.
This
really
is
what
we
anticipate
may
net
to
be
subsequent
to
that
I.
B
You
know
I,
it's
all
harder
to
give
definitive
timelines
with
I'm
you
know
suspected
after
is
that
you
know
we
should
aim
to
implement
this
thing,
at
least
as
a
prototype
within
a
month
or
so,
and
so
well,
that
is
essentially
the
you
know.
The
present
situation,
I
will
be
happy
to
speak
about.
You
know
both
problems
as
a
breakthroughs
encounter.
Is
this
work?
A
A
I'm
very
excited
about
this,
because
I
believe
it's
going
to
open
up
a
lot
of
doors
for
us
as
a
project,
one
of
the
things
that
the
cash
for
loss
protocol
has
done
a
really
great
job
of
is
providing
the
features
for
users
to
administer
their
on
chain
contracts
centrally
right
and
I
think
that
this
is
an
extremely
important
feature.
Instead
of
features
that
we've
developed,
that
businesses
really
need
for
real
world
adoption
right,
you
can't
you
can't
expect
a
company
to
depend
on
a
piece
of
technology
that
they
cannot
administer
centrally.
A
It's
just
not
realistic.
Right
like
decentralization
is
fantastic
and
it's
a
wonderful
thing
and
there's
definitely
a
place
for
defy.
There's,
definitely
a
place
in
the
space
and
a
great
need
for
it.
But
I
think
that
if
we
want
to
see
the
benefits
of
the
trust
layer
of
blockchain
adopted
by
real
world
companies,
we
also
need
to
provide
them
the
ability
to
centrally
manage
their
on
chain
contracts
right.
You
always
have
immutable
transactions.
You
always
have
an
immutable
history
and
I
think
that's
important.
A
It's
really
important,
even
today,
because
you
know
if
you
look
at
applications
today,
that
that
write
data
to
some
canonical
log.
Even
if
it's
a
centralized
database,
you
know
you
see
them
doing
weird.
You
see
these
applications
doing
weird
things
by
indicating
whatever
the
version
number
is
or
if
they
don't
have
good
practices,
they
modify
their
schema
and
then
you've
got
like
holes
in
the
data
right.
A
That
wrote
that
record
at
that
point
in
time
right-
and
you
can
observe
this
when
you
do
a
state
synchronization
when
a
new
node
syncs
up
to
state
they
run
through
all
of
that
history
right,
they
have
to
go
through
all
that
versioning
as
they
as
they
wrap
up.
So
you
know,
the
community
asked
that
we
should
talk
a
little
bit
about
use
cases,
so
this
is
this
is
something
that
you
know
I've
been
thinking
about.
This
is
the
way
I
think
about
about
blockchain
technology
right
so,
and
the
benefits
that
I
can
bring.
A
Anyone
want
to
add
anything
else.
This
is
kind
of
a
short
call
today.
We're
only
we're
at
21
minutes
join
us
on
discord.
If
you
want
to
join
the
conversation,
we
have
some
great
technical
discussions
here.
You
can
also
interact
with
our
validators
and
learn
about
how
the
test
net
is
operating,
find
us
on
telegram
as
well.
You
can
definitely
engage
in
the
conversation
and
ask
me
any
questions.
I'm
I
pop
it
on
both
I
actively
watch,
discord
and
telegram,
and
I'm
always
up
for
it.
You
know
a
technical
conversation
if
you
ever
interested.