►
From YouTube: CasperLabs Community Call
Description
Rewards Distribution presentation & status update.
A
Good
morning,
good
afternoon,
good
evening,
wherever
you
may
be,
thank
you
for
joining
us
this
morning,
I'm
here
with
Noren,
Alex
and
og,
our
community
manager
and
our
economist
and
we're
gonna
talk
about
Casper
labs,
I'm
sitting
here
enjoying
my
morning
cup
of
coffee
and
so
wherever
you
are
in
the
world.
Whatever
time
of
day
you're.
A
Listening
to
this
I
hope,
you
know,
pull
up
an
easy
chair
and
relax
and
enjoy
hearing
about
how
the
project
is
doing
so
very
happy
to
report
that
we
are
in
the
process
of
our
final
touches
for
the
node
12
release
that
we'll
be
announcing
later
this
week.
I'm
really
excited
about
this
release
because
we're
bringing
two
very
large
offerings
to
bear
for
adapt
developers.
The
first
one
is
a
runtime
test,
environment
and
and
infrastructure
to
support
contracts
developed
in
rust.
A
You
can
write
contracts
and
rust
and
test
them
on
a
machine
without
meeting
all
of
the
overhead
of
a
node,
and
this
is
super
important
that
you
can
run
and
test
contracts
directly
from
within
an
IDE
use.
Breakpoints
observe
how
inserts
and
ads
are
done
to
the
global
state
and
really
debug
your
contracts
right.
So
it
gives
you
a
true
like
a
development
kit
for
lack
of
a
better
term
and
we've
also
created
our
Minimum
Viable
for
assembly
script
support.
A
So
as
you're
well
aware,
the
Casper
labs
engine
supports
webassembly,
basically,
contracts
and
code
compiled
to
webassembly
can
run
if
they're
compiled
deterministically
can
run
without
issue
in
our
system,
and
so
this
enables
us
to
support
both
assembly
script
and
rust
and
any
other
future
languages
that
compile
down
to
blossom,
and
so
that
will
be
released
as
part
of
the
node
12
release.
We're
cutting
packages
today
and
we'll
be
updating
definite
before
the
end
of
the
week,
probably
on
Thursday.
A
If
you
have
accounts
in
clarity,
you'll
need
to
go
back
through
the
faucet
and
refund
them,
because
we
re
going
through
a
brand
new
Genesis
right.
So
we're
not
yet
at
the
point
in
the
product
where
we
can
do
rolling
up
what
we
call
rolling
up
grades
or
Forks
hard
or
soft
Forks.
We
still
go
through
a
brand
new
Genesis
process,
so
any
deployments
or
any
account
balances
that
you
have
those
will
be
wiped
out,
kneeling
to
start
over
and
so
moving
along.
A
Let's
talk
about
what
we're
currently
focused
on,
so
we're
focused
on
getting
a
production
version
of
honest
highway,
calling
this
honest
highway
and
what
that
means
is
this
network
doesn't
have
economic
security.
It
has
where
vacation
detection
its
pbft
compliant,
but
it
doesn't
have
all
the
struts
in
as
deterrents
for
attacks,
be
it
liveness
attacks
or
safety
attacks,
which
equivocations
will
detect
equivocations,
but
we
won't
slash
for
equivocations
right,
so
it
doesn't
have
the
economic
security
or
some
of
the
security
around
things
that
we're
calling
like
equivocation
bombs
and
social
consensus.
A
A
A
Then
we
will
go
into
developer,
engage
testing,
so
the
developers
will
be
doing
their
round
of
testing,
and
then
we
will
go
into
our
integration
and
testbed
testing
in
the
subsequent
weeks
running
up
to
the
March
release,
we're
implementing
the
fourth
choice,
rule
and
validation.
This
is
important.
You
know
when
you
validate
a
block,
you
get
a
validate,
that
the
validator
proposing
that
block
followed
an
appropriate
fourth
choice,
rule
and
we're
still
working
on
the
Sukhoi
simulator.
A
Execution
engine
we're
pulling
in
the
system,
contracts
and
making
them
native.
So
this
is
to
give
us
a
nice
performance
boost
and
we're
going
to
be
doing
some
benchmarking.
When
you
look
later
on,
you'll
see
that
SRA
is
doing
some
benchmarking
we're
creating
rust
stocks.
We
have
some
fabulous
rust
stocks
that
we
created
to
support
app
development
using
the
new
contracts
kit
and
so
within
the
rust
workflow.
You
will
have
rust
rust,
docks
to
guide
you
through
on
the
execution
engine
and
how
it
works,
logging
and
metrics
for
the
execution
engine.
A
A
We're
gonna
be
working
on
deploy
gossipping.
This
is
an
important
piece
of
the
protocol.
I
hope
that
this
will
be
done
by
March
should
be
fairly
straightforward.
We
basically
will
piggyback
the
existing
block
gossipping
infrastructure
we
had
and
include
deploys
that
are
in
the
deploy
buffer
as
an
initial
naive
implementation
of
what
goes
into
deploy
gossipping
our
CEO
type,
integration
with
node
and
clients
will
expose
all
of
the
CL
types
to
the
contracts,
interface,
all
the
way
out
to
the
client
and
this.
A
A
The
recommended
hardware
configuration
is
going
to
be
an
8
core
machine
that
is
generally
the
midpoint
I,
see
the
midpoint
in
terms
of
physical
resources
around
what
you
can
buy
a
server
that
you
can
buy
for
about
two
thousand
dollars
right
if
you're
dealing
with
infrastructure,
that's
racked,
that's
that
goes
to
about
2
km,
2,
K,
initial
investment
and
then
your
cost
for
bandwidth
and,
of
course,
monitoring
and
managing
that
instance.
A
And
then,
if
you're,
looking
at
AWS
and
be
about
five
hundred
bucks
a
month,
I
think
that's
a
Excel
instance,
the
eight
core
instance-
and
this
is
where
we
see
the
right
level
of
performance,
and
we
believe
this
will
be
the
right.
And
you
know
by
the
time
we
launch
the
network.
We
suspect
that
the
the
eight
cores
will
become
even
more
affordable,
right,
they'll,
be
even
more
affordable,
hey
shoke,
welcome.
B
A
A
A
A
It's
around
9
a.m.
it's
around
either
8
or
9
a.m.
and
Asia,
depending
where
you
are
in
Asia,
so
to
help
folks
come
in
Asia
to
get
some
deeper
engagement
out
of
Asia
we're
doing
the
afternoon
session
there
and
I'm
going
to
turn
this
over
now
to
you
own
or
all
right.
Let
me
stop
my
share
there.
You
go.
C
So,
to
show
to
this,
this
evolved
from
a
mock-up
I
want
to.
You
know,
act
as
a
reference
for
our
developers,
because
the
formulation
isn't
ready
to
translate
into
code,
so
I
want
to
bridge
bridge
formulation
and
code
and
then
I
like
I
thought,
while
I'm
at
it.
It
would
be
nice
to
be
able
to
simulate
validators
and
different
round
exponents
and
network
conditions,
so
I'm
envisioning
this
to
become
a
simulator
for
anything
with
the
economics,
transaction
fees,
maybe
cartel
formation,
and
so
on
and
I
try
to
compare
different
scenarios
in
the
future.
C
This
is
based
on
the
reward
distribution
document.
I
think
I'll.
Add
this
later
to
the
community
called
wiki
page,
but
it's
Ori.
You
can
get
the
link
from
the
video
if
you
want,
and
so
how
this
works
is
I
basically
created
a
module
called
source
I
create
a
module
called
highway
economic
simulator,
you
just
import
all
variables
or
not.
That's
not
really
good
code
practice,
but
I
just
for
these
example.
C
Example,
files
which
I
put
on
your
example
this
code
I'm
not
able
to
publish
it
yet
so
it's
a
private
repo,
but
it
will
be
your.
It
will
be
out
in
one
or
two
weeks
because
I'm
converting
into
it's
right
now,
a
fixed
increment,
simulator,
I'm,
converting
it
to
a
discrete
event
simulation
somewhere
to
run
faster
and
be
more
add,
more
details
related
to
messages.
The
highways
highways
you.
C
Structure
so
I
have
these
example
cases
what
well.
What
we
have
here
is
that
we
first
define
an
intial
supply
of
tokens,
just
values
that
I
assign
from
the
top
of
my
head,
that
this
is
not
representative
of
what
we're
gonna
launch.
So
this
is
just
basic
values.
If
I
thought
that
would
work
and
then
I
launch
the
I
created
three
validators
with
equal
stake,
so
they
in
total
they
make
up
30%
of
total
supply
and
then
I
set
a
constant
round
exponent
for
all
of
them.
C
What
this
means
is
these
the
v2
and
v3
will
be
participating
in
every
2
to
the
power.
7
ticks,
that's
like
128
milliseconds
wait.
Is
it
I
think
so,
and
then
this
will
be
participating
every
256
milliseconds,
so
I
changed
these
later
and
to
be
more
realistic.
So
these
we
should
be
like
more
like
8
seconds,
but
for
an
examples.
B
C
A
C
C
C
C
What
the
majority
receives
on
average,
so
we
just
yeah
and
I
have
another
example
here.
So
what?
If?
What?
If
this
guy?
So
here
these
two
times
slower?
What
if
we
had
the
majority
slow
but
another
another
validator,
which
is
four
times
faster,
so
the
difference
of
between
round
exponent
is
2,
so
2
to
power.
2
is
4
with
this
guy,
like
runs
four
four
times
faster.
So
this
means
that
three
out
of
every
four
rounds
that
this
guy
has
is
infeasible
by
infeasible
you
can.
C
B
C
So
it's
not,
it
doesn't
have
any
enough
validators
participating
on
it
and
we
want
to.
We
want
to,
in
our
formulation,
eliminate
this
behavior,
where
validators
underestimate
there
around
exponents
to
in
order
to
catch
catch
every
round
possible,
because
with
how
we
design
our
lower
distribution.
Even
though
you're
not
sending
a
message
in
in
your
round,
you
may
still
get
rewarded,
because
this
is
this
is
to
deal
with
censorship.
So
we
just
look
at
whether
a
block
was
finalized
on
time
and
and
then
we
increase
rewards
the
more
the
more
weight
votes
for
it.
C
The
more
values
wait
for
it,
so
this
dis
creates
this
situation
where
well,
DeeDee
can
just
set
round
exponent
0
and
then
he
would
literally
be
participating
participating
in
each
round
each
tick.
Sorry,
so
each
millisecond
he
would
be
starting
a
new
realm
and
we
don't
want
such
a
thing,
because
it's
not
feasible.
C
For
space
in
a
round
which
has
very
small
weight,
smaller
than
50%,
for
example,
which
is
required
to
finalize
a
block,
then
here
I
said
s3.
So
if
you
are
like
4
times
faster
than
3
out
of
your
each
block
will
be
infeasible,
it
won't
be
finalized
in
time
on
time
it
will
be
finalized
only
when
other
validators
build
on
it.
C
C
C
And
you
can
see
that
validators
hero,
which
is
the
first
valve
aider,
earned
much
less.
Actually,
the
valve
leader
was
rewarded
only
for
the
initial
round,
which
didn't
have
any
previous
previous
round.
So,
like
the
first
round,
you
don't
have
any
history,
but
in
like
four
rounds
later
you,
your
punishment,
takes
effect
and
then
he
doesn't
receive
any
any
rewards
from
the
subsequent
blocks.
The
blocks
get
finalized.
His
vote
counts,
but
he
doesn't
receive
any
rewards.
A
So
this
is
a
very
interesting
principle
right,
because
what
we
want
to
support
a
Casper
Labs
is,
you
know
more
decentralization
right,
so
it's
counterintuitive
that
the
fast
that
the
validator
setting
his
round
exponent
low
actually
doesn't
get
more
rewards
because
you
think
oh
I'm,
super
fast
I
can
propose
a
lot
of
blocks,
but
the
rewards
really
are
for
processing
transactions
and
finalizing
them.
So
if
you're
out
there
running
away
ahead
of
everybody
else,
you're
not
actually
participating
you're,
not
helping
to
that
goal
right
to
that
aim.
So
you
cannot.
C
C
With
this-
and
this
is
a
this-
is
a
current
view-
if
we
can
find
a
better
way
of
dealing
with
this
I
think
we
would
have
won,
but
this
is
the
best
we
thought
of
now
and
we
will
see
how
how
it
will
affect.
So
we
want.
Do
you
want
this
number
not
too
low,
because
there
might
still
value
will
be
no
reacting
to
metric
commissions,
and
you
don't
want
just
because
of
LDR
increases.
If
this
per
like
one,
then
the
validators
would
all
of
them
would
have
to
have
the
same
round
exponent.
C
C
This
is
like
a
herd
and
they're
moving
like
slowly
when
they
can
run
faster
one
by
one
they
will,
they
will
be,
you
know,
increasing
their
round
exponents
and
this
will
signal
and
then,
after
some
time,
all
of
them
will,
you
know,
tip
off
to
the
faster
side.
But
you
know
it
will
be
like
step
by
step.
You
won't
just
decrease
your
round
exponent
like
by
an
order
of
four
something.
I
mean.
A
C
C
B
C
A
C
A
Definitely
you
can
certainly
talk
about
it,
I'm
gonna!
Let
me
just
kind
of
thread
something
in
here:
we've
got
a
new
website,
so
go
check
it
out,
there's
a
lot
of
great
information
and
on
the
new
website
about
who
we
are,
what
we're
building.
Why
we're
here
our
ethos,
so
I'd
love
to
hear
feedback
from
the
community
and,
more
broadly,
beyond
and
yeah
moving
on
to
test
net.
A
I
also
there
is
also
a
release
plan
here
that
you
can
go
check
out
pertaining
to
tests
that
it's
our
alpha
tests,
net
release
plan
and
we
talked
a
little
bit
about
the
incentivize
test
net
that
we're
planning
here.
What
we
want
to
learn
the
contribution
of
the
validators
and
then
rewards
for
participation.
A
C
Me
stop
sharing
yeah.
For
me,
it's
fine
I
I,
don't
I
will
just
speak.
C
So
I
sanitize
test
myths
are
a
very
good
way
like,
as
demonstrated
by
cosmos
last
year,
with
game
of
stakes
which,
which
was
like
beautiful.
How
they
played
how
it
played
out
is
a
good
way
of
onboarding
valuators
to
the
ecosystem,
having
giving
them
something
to
you
know,
develop,
also
learn
about
the
protocol
like
it
has
so
many
facets
and
how
it
you
know,
aligns
people
in
the
same
direction.
C
A
C
Think
they're
all
running
everybody's,
you
know
so
the
potential
and
like
launching
launching
such
a
test
net
also
Cardinal,
and
there
are
many
aims
in
launching
such
a
testament.
1:1
I'll,
just
go
on
by
one
one
is
to
for
security
to
you,
know,
find
any
bugs
in
the
client
code
or
find
many
like
allow
other
people
to
also
have
look
at
the
code
and
like
have
more
eyes
looking
at
the
protocol.
So
the
formulation,
if
there
are
issues
with
it
and
then
point
out
to
potential
bugs
before
main.
C
C
A
single
entity
used
many
different
accounts
and
passports
and
so
on
to
you
know,
participate
in
the
game,
so
they
launched
when
they
launched
with
44%
stake
a
single
entity
and
after
some
time
they
as
as
other
validators,
were
being
jailed,
and
you
know,
dropping
out
of
the
game
because
of
you
know,
misconfigure
nodes
or
not
not
being
able
to
catch
up.
This
is
so
a
test
net.
Their
stake
grew
up
to
53%.
C
So
what
happened?
Was
the
community
coordinated
and
they
actually
forked
out
the
the
cartel
which
owned
thirty
to
fifty
three
percent?
It's
not
actually
a
cartel,
but
a
monopoly.
So
a
single
agent
they
discovered
through
like
bonding
requests
and
such
that,
oh
and
and
also
the
IPS
IPS,
from
which
the
messages
came
from
they
all
came
from
a
digital,
no
digitalocean
instances.
C
They
eventually
discovered
all
the
addresses
that
bird
that
belonged
to
this
cartel
and
they
eventually
forked
out
all
the
addresses
by
unbounding
delegated
tokens
and
moving
tokens
to
the
community
pool
and
eventually,
at
the
at
the
very
end,
it
was
discovered
that
it
was
bit
fish.
One
of
the
participants
in
the
game
who
attempted
this
without
letting
others
know
and
like
this
sort
of
thing,
is
of
course,
really
good
for.
C
Like
simulating
potential,
it's
like
a
drill
like
you.
What
would
happen
if
you
actually
needed
to
do
do
a
hard
fork
like
it's
the
last
thing
that
everybody
wants
to
do,
but
what,
if
you
really
need
to
do
it?
So
we
saw
that
cosmos
developers
and
also
like
valid
leaders,
were
already
like
ready
to
prepare
to
respond
to
such
a
situation.
So
they
reacted
quickly
after
it
is
discovered
they
had
the
preparation
in
advance
before
they
launched
game
of
stakes.
A
Just
depends
on
the
attack
right,
like
I,
mean
there's
some
attacks
that
are
tremendously
useful
and
I
sincerely
hope
that
lots
of
people
come
out
and
attack.
Our
network
is
an
invitation
to
attack
our
network,
not
our
alpha
test
net.
Please,
because
our
alpha
test
net
won't
have
economic
security,
but
our
beta
test
net.
Certainly
once
we
have,
you
know
the
slashing
and
liveness
detection
I
certainly
want
to
see
if
there's
validators
out
there
that
can
execute
an
attack
against
the
network,
how
much
that
attack
would
cost,
etc,
etc.
A
A
It
was
usually
people
to
the
team
more
broadly
to
see
how
the
protocol
worked
and
I
think
the
same
thing
goes
with
you
know:
if
their
alpha
test
met
a
lot
of
people
like
to
have
things
really
really
baked
before
they
put
them
out
there,
but
I
believe
it's
important
that
people
see
and
interact
with
our
process
in
in
the
public
eye
a
lot
more
right,
and
so
that's
why
our
test
myths
I
mean
we're
finishing
the
consensus
protocol.
Literally
two
weeks,
the
Alpha
put
consensus
protocol.
A
The
MVP
consensus
protocol
is
literally
going
to
be
finished
two
weeks
before
we
deploy
or
chestnut
so
we're
going
to
finish
it
we're
going
to
we're
going
to
stabilize
it
as
much
as
we
can
stabilize
it
and
we're
gonna
start
working
with
our
validators
immediately.
So
we
can,
you
know,
start
getting
feedback
from
them
on
what
it
means
to
run
and
support
this
protocol,
because
it
gives
us
the
most
time
to
build
whatever
kind
of
monitoring
tools.
If
there's
any
social
consensus
that
the
validators
need
to
formulate
tooling
around.
A
They
have
plenty
of
time
to
do
that.
So
we
just
believe
in
in
iteration
is
key
right
and
we
want
to
launch
the
Genesis
block
many
many
many
times
so
between
between
launching
the
alpha
test
net
and
launching
maintenance,
Genesis
process
at
least
two
dozen
times.
So
practice
makes
perfect
in
my
eye
right
in
my
mind,
and
so
we
will
learn
a
great
deal
about
what
it
means
to
go
through.
A
C
We
need
to
different
like
communication,
there
technical
aspects
of
it
and
there
are
also
none
technical
aspects
like
communication
with
validators,
actually
specifying
like
the
roles
we
think
for
them,
and
this
test
net.
So
it's
it's
it's
beneficial
when
everybody
knows
what
they
should
do
or
like
the
framework
in
which
they
should
try
out
scenarios
and
also
it's
important
to
draw
people
in
because
and
also
how
to
how
to
judge
them
because
they
are,
they
will
be
potentially
be
future
partners
of
the
protocols
and
they
will
develop
software.
C
A
Have
some
amazing
things?
We
have
some
amazing
things
that
we're
working
on
for
developer,
adopt
developer
engagement
and
developer
engagement
that
we
will
be
announcing
while
our
community,
our
fledgling
community,
will
be
announcing
here
in
the
next.
You
know,
two
to
four
months
that
we
are
working
on
I'm,
very,
very
excited
about
this
I
think
it's
we've
got.
We've
got
a
several
announcements
that
are
coming
in
the
next
two
to
four
months.
A
That
will
be
transformative,
I
think
both
for
this
project-
and
this
is
faced
more
broadly,
so
I'm
really
excited
about
the
things
that
we
have
in
the
hopper.
We're
not
talking
about
them
just
yet,
because
we
haven't
gone
through
all
the
you
know,
we're
still
working
through
details
and
it's
those
regulatory
constraints
around
it,
but
I'm
very
very
excited
around
what
we're
going
to
be
talking
about
here
in
the
next
several
months.
So
thank
you
own
or
so
much
for
those
of
you
that
have
joined
us
this
morning,
dialed
in
and
listened
in.
A
Thank
you
so
much
for
doing
so,
and
we
have
our
weekly
workshops:
Thursday
mornings,
9a
8:00
a.m.
Pacific
and
4:00
p.m.
Pacific,
which
is
9:00
a.m.
Japan
Asia
time
we're
going
to
be
talking
about
the
vesting
contract
and
the
user
interface
this
week
during
that
session.
So
please
join
us.
Cheers
have
a
great
day
bye.