►
From YouTube: CasperLabs Community Call
Description
Rewards Distribution presentation & status update.
A
All
right,
good
morning,
everyone
good
day,
thank
you
for
joining
us
today
present
our
update
I
met
a
Polock,
our
CTO
Kasper
labs,
I'm
joined
on
the
call
by
Ashoka
run
today
our
program
manager,
own
or
Solmaz,
one
of
our
economists,
Alexander
Limonov,
another
economist
and
OG,
are
one
of
our
leading
community
managers.
So
thank
you.
Everyone
for
dialing
in
listening
in
or
following
along
later
on,
let's
see
happy
to
report
that
I'll
be
going
through
test
net.
This
morning
we
cut
node
18
on
April
8.
A
This
is
with
additional
optimizations
to
the
finalizar
and
fixing
a
bug
that
caused
multiple
dead
arrows
to
show
up
as
active.
So
for
those
of
you
not
familiar,
we
launched
test
net
on
March
31st.
We
went
through
Genesis
a
few
times
with
the
validators,
because
we
discovered
problems.
You
know
we
rapidly
iterated
right.
We
we
discovered
that
we
were
putting
the
code
in
a
much
more
wild
environment
as
what
happens
with
decentralized
networks,
and
we
learned
something
about
the
software
in
the
system.
A
As
a
result
of
that,
so
we
had
to
iterate
rapidly
and
make
some
patches.
You
know.
Mateos
and
a
coach
were
like
really
like
studs
on
how
they
got
this
done.
You
know
we
only
had
to
patch
the
network,
but
four
or
five
times
bounced
it
four
or
five
times,
but
now
I'm
happy
to
report
that
the
network
has
been
stable,
rock-solid
stable
since
that
time.
Here
you
can
see.
This
is
basically
the
this
testament
status.
Little
shell
script
shows
each
new,
it's
less
finalized
block
and
we're
querying
the
status
support.
A
We
have
one
node
that's
behind,
but
of
the
twenty
three
nodes
in
the
network.
All
of
them
are
absolutely
rock
locks
Inc.
So
the
network
is
reaching
consensus
in
the
last
finalized
block,
which
is
terrific.
It's
been,
you
know
like
watching
paint
dry,
which
is
great.
That's
what
you
want
when
you're
dealing
with
the
production
system
should
be
very
boring
and
we
have
some
issues
we're
still
working
through.
A
You
know
we
notice
that
there's
a
stack
overflow
error
and
out
of
memory
area
error,
because
we
are
aggressively
doing
a
state
synchronization
when
a
node
goes
offline
or
updates
installs.
An
update,
synchronous
synchronizing
that
node
backup
to
the
network
is
something
that
was
way
too
slow
and
way
too
conservative
before
and
we've
made
that
a
lot
more
aggressive,
but
now
we're
seeing
some
issues
in
the
JVM
or
out
of
memory.
A
You
know
out
of
memory
errors
on
the
system
during
synchronization,
so
there
there
is
an
issue
we
are
still
working
through
and
we
suspect
there'll
be
more,
but
on
balance,
we're
very
pleased
with
the
way
the
network
has
been
performing
as
of
late.
This
test
net
supports
highway
right.
It
implements
the
highway
protocol,
it
assumes
honest
validators
right,
so
we'd
haven't
yet
built
in
the
equivocation,
fault,
detection
or
support
to
deal
with
equivocations
nor
economic
security
right.
So
this
is
more
or
less
aid
to
call
it
be
honest
and
transparent
with
what
it
is.
A
This
is
a
permissioned
network
that
implements
the
highway
protocol.
We
have
selected
a
validator
set
that
we
are
working
with
the
validator
set.
We
didn't
select
the
validator
set,
but
they
signed
up
right.
They
signed
up
by
a
deadline.
They
are
in
the
account
CSV
file,
which
then
creates
the
genesis
block
with
them
bonded
into
the
network
with
their
stakes
and
for
this
time.
So
it's
more
like
a
permission
network
right
now.
A
We
recognize
that
you
know
we
have
a
lot
of
work
ahead
of
us
right
to
open
up
bonding
a
ton,
bonding,
slashing
and
rewards
right.
This
is
part
of
becoming
a
permission
list
decentralized
network
and
we
have
some
work
ahead
of
us
to
do
that.
Also
to
support
you
know,
equivocation,
detection
and
handling.
So
what
it
does
support
is
we
have
our
Genesis
process.
We
have
all
of
our
smart
contracting
features
and,
of
course,
I've
included
a
link
here
to
the
Explorer
right
now
it
is
a
separate
URL.
A
We
will
eventually
be
moving
the
production
instance
of
clarity
that
everybody
gets
to
buy
the
website
to
the
test
net.
Here
shortly.
We
haven't
done
that
yet
simply
because
we
wanted
to
make
sure
everything
was
stable,
we're
gonna
be
decommissioning,
definite,
and
you
know,
the
decommissioning
of
dev
net
basically
means
that
clarity
would
be
pointed
to
testing
it
and
that's
how
you'll
interact
with
the
network.
We'll
also
be
providing
a
list
of
deploy
endpoints
as
well,
so
current
focus
keeping
test
net
stable.
A
We
consider
this
our
production
production
system
and
it
has
the
same
SLA
as
of
any
other
production
system.
We
are
working
on,
deploy,
gossipping
deploy.
Gossipping
will
enable
us
to
expose
a
few
endpoints
to
the
network
and
then
those
nodes
will
then
gossip
all
those
deploys
throughout
the
network,
making
it
not
as
critical
for
you
for
all
the
validators
to
expose
an
endpoint,
but
rather
there
could
be
a
couple
of
endpoints.
We
want
more
endpoints.
A
Obviously
that
makes
it
more
decentralized
and
more
robust,
but
the
deploy
gossiping
enables
a
few
leader
quote-unquote
nodes
if
they
want
to
expose
their
endpoint
can
do
so
to
accept
transactions
and
then
gossip
those
transactions,
we're
augmenting
the
estás
environment
and
running
our
long
rolling
tests.
Our
long
running
tests
are
basically
our
network
test
beds.
A
The
LR
T's
were
originally
called
LR
T's,
because
we
wanted
to
make
sure
the
network
was
up
and
stable
for
a
minimum
of
seven
days,
just
because
we
wanted
to
know
that
we
could
support
a
production
system
for
an
extended
duration.
So
we
call
them
LR
T's,
we
are
doing
we're
starting
to
prototype
highway,
plus,
plus
now
highway
plus
plus,
is
of
a
an
improvement
on
the
existing
highway
protocol.
It
is
a
different
enough
consensus
protocol
that
we
put
the
plus
plus
behind
it.
It
has
the
hardening
needed
for
equivocation,
detection
and
equivocation
handling.
A
So
this
is
a
different
protocol.
We
will
be
upgrading
the
highway
paper
to
include
the
information
for
a
highway
plus
plus
and
we
are
working
through.
We
have
worked
through
all
the
mathematical
proofs
to
make
sure
that
the
protocol
holds
up
we're
going
to
update
our
technical
specification.
I
made
some
updates
that
are
not
loaded
here
more
than
design
of
more
than
a
price
link,
it's
actually
what
we're
calling
the
cross
peg.
A
And
we're
starting
to
prototype
highway
plus
plus,
so
that
work
is
underway.
We
are,
let's
see
what
else
we'll
be
working
on
here
execution
engine
we
got
to
get
contract
headers
done
in
a
balance.
Endpoint
we've
had
fair
number
of
requests
to
be
able
to
interrogate
the
balance
of
tokens
stored
at
an
address,
and
that
needs
to
happen
with
with
him
contracts
as
well,
and
this
is
where
you
want
to.
You
know,
for
example
like
what
maker
Dow
does
the
contract
can
hold
token.
You
need
a
balanced
endpoint
to
support.
A
A
We're
working
with
our
with
our
wonderful
validators
in
discord.
If
you
want
to
see
it,
the
conversations
have
been
like
that's
all
happening
openly
and
transparently
in
discord
with
the
validators,
so
you
can
definitely
go
check
it
out.
We
have
I'm
happy
to
report
that
we've
got
validators
that
are
helping
other
Valladares,
which
is
amazing.
That's
what
we
want
to
see.
We
want
the
validators
to
run
and
own
this
network
and
make
it
their
own,
and
some
of
them
are
coming
up
with
new
tools
to
help
them
monitor
the
network.
Much
like
what
I've
shut.
A
What
I'm
sharing
here
on
my
screen,
but
other
new
and
unique
tools
to
help
them
better,
manage
their
notes
right
using
system
D
versus
no
hub
and
there's
a
whole
bunch
of
administrative
type
functions
that
they
are
working
through
right
and
learning
how
to
learning
how
to
manage
that
and
we're
scaling
s
tests
with
new
features
for
monitoring
and
new
scenarios.
So
what
we
want
to
do
is
we're
going
to
continue
investing
in
s
test
because
it
enables
us
to
ultimately
at
some
point.
A
We
want
to
turn
s
test
over
to
validators
and
let
the
validators
just
you
know,
performance
test
the
test
net
right.
So
ideally,
the
S
test
framework
is
one
that
the
validators
can
ultimately
deploy
against
the
network,
and
then
they
can
report
can
report
to
the
the
trends
you
know,
report
the
transaction
speed
or
the
transaction
processing
the
network
and
fine-tune
the
network
ultimately
themselves.
A
On
the
ecosystem
front,
we
are
enhancing
clarity,
we're
gonna
give
them
a
folks.
A
browser,
plugin
assign
deploys
being
able
to
filter
ballots,
do
more
analytics,
do
more
interesting
things
within
the
block
Explorer,
and
you
know
from
my
perspective,
the
clarity
block
is
for
really
is
a
learning
tool
as
well
to
help
people
understand
how
the
network
works
and
what
are
they
looking
at
right
and
so
I
also
want
to
put
some
context.
A
Sensitive
help
within
the
clarity
block
is,
for
we
recently
supported
assembly
script,
and
we
need
to
put
some
smart
contract
examples
and
tutorials
and
documentation,
so
we're
gonna
update
that
def,
developer
or
guide
for
that
and
then
Ashok.
We
also
need
to
add
some
work
around
documenting
the
DAP
developer
guide
on
how
to
use
our
CL
types
at
the
clients,
yeah.
C
A
To
do
the
querying
and
stuff
yeah,
yes,
I
think
that'll
be
important,
so
we
should
probably
take
an
action
item
for
that
too.
Cuz
that's
been
out
there
for
quite
some
time
and
then
tutorial
for
how
to
do
tutorials
on
the
multi-sig
and
weighted
keys,
payment
and
payment
code
contract
support
and
how
to
use
payment
code,
because
we
have
touring
payment
shrink,
complete
payment
code,
economics,
research
again
we're
talking
with
thinking
a
lot
about
transaction
fees,
a
whole
bunch
and
RFC
is
what
request
for
what
is
RFC
for.
A
A
So
we
understand
it
better.
So
that's
the
update
real
quickly,
I'm
going
to
walk
through
the
Explorer
here
for
folks.
So
you
guys
can
see.
This
is
the
test
net
Explorer
and
let's
try
to
see
if
we
can
reload
it
it'd
be
nice
if
it
reloads
with
the
settings
that
I
currently
have
right
now
a
show.
Maybe
you
can
take
an
action
item
to
let
ecosystem
know
about
that,
because
what
it's
gonna
do
it's
gonna
default
back
to
10
yeah.
B
A
A
C
B
I
can
show
my
screen
in
the
mean
time,
so
this
is
this.
Is
the
current
state
of
our
Explorer?
You
can
see
that
blocks
are
getting
finalized
and
all
the
nodes
are
in
sync.
I
also
have
the
dashboard
that
tom
has
created
running
here.
You
can
see
that
all
the
nodes,
except
this
one
93
130
57,
are
are
synchronized
at
the
same
last
finalized
block
and
it
is
fifty-seven
thousand
six
hundred
and
thirty-four.
B
B
D
Yeah
so
yeah,
so
that
node
in
particular,
is
one
that
you
can
see
he's
still
sinking.
So,
if
you
look
in
the
initial
sink
column,
it
says
running
right,
so
he's
catching
up
State
at
the
moment
he
started
at
zero
State
and
he's
caught
up
44,000
so
far,
so
he's
on
his
way.
Yeah.
B
A
C
C
And
you
know
in
order
to
make
a
business
model
blockchain,
you
know
what
has
to
determine
first,
you
know
what
it
is
that
a
blockchain
is
good
for
if
you're
a
business-
and
you
know
if
anyone
is
actually
reading
our
blog
on
medium
I,
published
a
post
a
few
days
ago
that
addresses
that,
to
a
certain
degree,
the
main
takeaway
beans
that
you
know
the
utility
of
the
blockchain
has
very
little
to
do.
Viz.
C
You
know
it's
Lucy,
macro
financial
implications.
Right
I
mean
people
worry
a
lot
about.
You
know
whether
cryptocurrencies
equate
to
displace
Fiat.
You
know
what
the
few
interaction
between
Fiat
coupe
de
crazy
he's
going
to
be.
You
know,
is
you
know,
central
bank
cryptocurrency,
a
threat
to
the
centralized,
cryptocurrencies
and
frankly,
I
mean
my
hitter
looks
position
on
this
is
a
none
of
that
stuff?
C
Actually
matters
right,
so
my
position,
the
ref
lease
weakens
that
well,
the
blockchain
is
good
for
if
your
business,
it's
two
things
right,
the
first
of
them
is
that
it
provides
you
with
an
ability
to
securely.
No
publicly
verify
you
know,
counterparty
characteristics
and
behaviors,
because
you
know
for
such
counterparty
wants
to
establish
a
certain
reputation.
You
know
they
can
put
public
data
I.
You
know
public
data
on
the
block
chains
at
as
they
cannot
later
tamper
this
right-
and
this
is
this
secure
basic
consensus
and
it's
you
know
completely
static
going
forward.
C
You
can
always
review
it
right.
So
the
second
you
know
the
second
thing
that
it's
good
for
is
automation
of
contract
execution.
So
what
that
means
is
the
basic
boxing
is
good,
for
you
know
minimizing
certain
transaction
risks
right
without
relying
on
third
parties,
because
you
know
the
cortex
executes
themselves.
C
You
know
you
can
go
and
you
know
verify
yourself.
You
know
any
date
is
that
is
sitting
on
the
blockchain,
so
you
know
certain
transaction
risks
can
be
minimized
by
using
this
technology.
Unfortunately,
this
technology
causeways,
you
know
certain
other
risks
as
it
need
to
be
mitigated-
and
here
you
know
like
I,
for
a
business
practices
at
the
you
know,
I'm
kind
of
assuming
here
a
stable.
You
know
ecosystem
something.
Like
a
theory
of
worry,
though
you
don't
expect
it.
C
You
know
the
more
you
wake
up
and
that
the
network
has
experienced
a
hostile
takeover
or
something
right.
So
what
are
the
day-to-day
risks?
Is
that
the
machine
has
to
deal
with
that
really
related
to
consensus.
Wills
are
essentially
free
right.
The
first
time
is
a
volatility
of
the
fees.
It's
you
know
fewer.
You
know
you
were
to
use
the
blockchain
as
a
critical
piece
of
your
infrastructures,
and
you
know
you
will
be
introduced
in
this
giant
Rosetta.
You
have
no
idea,
you
know
what
you're
you
know.
C
Critical
messages
are
going
to
cost
to
send
tomorrow
right,
very
least
Ito.
It's
a
conventional.
You
know
the
conventional
model
that
is
exemplified
by
a
theory.
Problem
number
two
is
extreme.
Ui
complexity,
I
mean
it
is
not
the
you
know
interactive
is
the
blockchain,
in
my
view,
is
not
generally
a
particularly
pleasant
experience.
C
The
third
problem
is,
you
know,
well-baked
old-school
finalization,
which
is
generally
slow,
perform
its
rating
in
Windows
a
day
like
all
block
chains,
are
such
a
bottleneck
by
individual
machines
and
the
fortunately
makes
it
currently
rather
slower
ISM.
Something,
like
you
know,
dedicated
proprietary
payment
process
networks
like
Visa
or
something
alright.
So
you
know
you,
you
know
you
minimize
some
risks,
but
you
introduce
certain
other
risk.
So,
in
order
to
make
you
know
business
friendly
blockchain,
you
must
tamp
down
Ziza,
you
know
risks
after
being
introduced.
So
the
question
is
okay.
C
So
what
are
we
trying
to
do
about
these?
The
first
thing
we're
trying
to
do
is
you
know
we're
dedicating
considerable
efforts
to
stabilize
in
our
fees
intro.
You
know
in
fiat
terms
alright.
So
this
is
a
cross
specs
that
might
have
talked
about
and
the
way
we're
going
to
be
going
about.
It
is
well
first
we're
going
to
implement
a
very
crude
approach,
which
is
that
we're
going
to
fix
the
price
in
dollars.
C
You
know
true,
you
know
utilize
this
cross
peg,
but
of
course
later
we
will
try
to
design
a
system
that
is
a
demand
responsive
that
still
minimize.
This
is
a
volatility,
and
this
is
a
complex
topic,
but
they
do
things
that
it
is
feasible
in
the
long
term
and
essential
to
transition
to
a
system
here.
That
is,
in
fact,
demand
response
so
that
you
know
you
know
best
users
over
the
blockchain.
There
can,
you
know,
receive
priority
essentially.
C
C
You
know
we
have
introduced
business
friendly,
a
user
experience
features
such
as
you
know
our
out-of-the-box
support
for
custom
payment
code
right.
So
you
know
which
is
a
turing-complete.
In
our
case
we
don't
work.
However,
you
want
to
pay
for
something
that
is
entirely
your
choice.
Of
course,
you
know
should
point
out
the
special
degree
in
away
increases
complexity,
so
you
know,
hopefully
we
will.
You
know
continue
through
in
our
documentation
about
that.
C
And
finally,
you
know
we
are
constantly
evaluating
the
performance,
but
for
the
life
system,
rights
from
the
current
test
net
in
simulation,
so
various
kinds
and
in
theoretical
voltage
for
is
it
there?
You
know
this
is
the
most
performant
proof
of
stake,
a
block
Sheen's.
There
is
right
so
to
reiterate
what
we're
trying
to
do
is.
You
know,
provide
businesses,
a
hassle-free,
you
know
it's
actually
pluggable
pieces,
their
infrastructures,
as
they
can
rely
right.
So
they
know
what
they're
paying
for
is
they
know
exactly
what
they're
getting
out
with
you
know.
C
C
So,
and
you
know
the
reason
why
we
are
oriented
in
this
direction
right,
this
can
be
the
way
you
know
various
review
to
latarian
approach
to
you
know.
Well
what
can
we
offer
you
right
instead
of
trying
to
revolutionize
the
world
financial
system
or
if
there
were,
you
know,
nonsense.
Other
people
in
this,
you
know
in
the
sphere
into
well.
You
know
you
can
read
the
you
know
the
blog
post
is
that
I
mentioned
previously,
and
you
know
it
could
dresses
this.
C
You
know
this
question
is
some
detail
or
item,
and
so
how
feasible
is
it
to
build
this?
You
know
smart
contract
economy
and
how
you
know
put
it
cater
to
business.
Why
would
business
want
to
use
it?
So
you
know
as
extent
that
the
explanation
is
basically
in
this
blog
post,
but
this
is
pretty
much
it.
You
know
today
from
me.
A
B
Thanks
Alex,
thank
you
so
much
yeah.
So
as
a
zero
elevator,
you
know,
Kasparov
is
focused
on
business
cases
and
enterprise
class
customers
via
calling
us
as
blockchain
for
builders.
So
that
remains
as
our
primary
use
case.
Thanks
Alex
anything
else
here
to
talk
about
I,
don't
know
me,
the
joint
back
I,
don't
think
she's
going
back.