►
From YouTube: CasperLabs Community Call
Description
Rewards Distribution presentation & status update.
A
B
A
C
D
Yeah
I
mean
I've,
been
speaking
a
good
good
morning.
Everyone
we're
just
catching
up
here
on
the
call
on
coronavirus,
hope
everyone's
staying
safe
out
there
and
I've
been
thinking
you
several
friends
of
mine
and
true
Indian
form.
We
have
a
lot
of
friends
that
are
physicians
and
bless
them
they're
working
so
hard
on
the
front
lines
here.
There's
a
lot
of
fear
and
panic,
but
take
heart
in
that
you
know,
is
an
unpopular
opinion,
but
in
the
u.s.
D
D
That
goes
without
saying,
and
this
thing
is
obviously
very
contagious,
so
we
do
want
to
keep
you
know
the
line
as
flat
as
we
can
so
do.
Think
of
your
community
and
especially
particularly
elderly
folks,
and
be
cognizant
of
who
you're.
You
know
who
you're
staying
in
touch
with
so
but
do
take
heart
in
the
fact
that
this
virus
will
probably
dissipate
as
all
flu
and
cold
viruses
do
once
warmer
weather
hits.
So
stay
safe
out
there
and
don't
don't
not
get
knocked
over
by
any
old.
D
Ladies
in
the
grocery
store,
when
you
try
to
get
toilet
paper
on
that
note
engineering
status,
we
are
pushing
real
hard
towards
our
alpha
test
net
release.
The
engineering
team
has
started
doing
daily
stand-ups,
with
the
specific
focus
of
what
we're
testing
what
we've
learned.
What
needs
to
be
fixed,
so
we
can
stay
tightly
aligned
on
what
we're
pushing
towards.
At
the
end
of
the
month.
I
have
been
working
with
the
business
team
on
engaging
with
prospective
validators
and
staking
pools.
D
I
will
be
releasing
the
incentivized
test
net
program
on
or
you
and
I
have
been
working
on
this,
but
we're
going
to
step
up
the
game
a
little
bit,
because
I
got
to
get
a
PDF
out
to
Marin
all
today,
so
he
can
distribute
it
to
the
potential
shakers
staking
pools
so
I'm
working
on
a
Google
Doc.
It's
coming
off
of
the
template
that
we
started
with,
but
I'm
going
to
just
talk
in
a
very
high
level.
What
the
rounds
are.
D
They
know
the
three
different
cycles
for
testing
it:
the
entire
test
net
program
and
a
high
level
what
the
prizes
are,
but
I
think
we
have
a
lot
of
work
to
do
in
the
back
end
with
respects,
to
you
know,
transparently
keeping
track
of
metrics,
in
terms
of
which
validator
did
what
how
we're
going
to
harvest
those
from
the
network,
etc,
etc.
We
want
to
be
as
objective
as
we
possibly
can
with
respects
to
who
the
winners
are,
who
the
participants
are
etc,
etc.
D
So
that
is
due
to
get
kicked
off
in
the
next
couple
of
weeks
around
working
with
the
validators
closely
making
sure
they
have.
The
software
Ashok
is
doing
the
weekly
workshops
for
those
one
in
the
morning
on
Thursdays
one
in
the
afternoon
on
Thursday,
specifically
around
validators,
you
know
getting
to
Genesis
right.
You
know
two
or
three
nodes
getting
to
Genesis.
They
were
walking
them
through
how
to
bootstrap
the
network.
B
D
B
B
D
Are
entering
our
code
freeze
on
Thursday?
We
were
going
to
cut
our
release
on
Thursday,
but
we
decided
from
an
efficiency
perspective
because
we
are
pushing
so
hard
for
those
of
you
that
may
not
be
aware.
Highway
is
really
just
hot
off
the
presses
right.
So
the
code
still
needs
a
significant
amount
of
testing
and
bug
fixing.
D
We
believe
that,
even
though
it's
really
hot
off
the
presses,
we
want
to
take
off
which
to
take
advantage
of
the
code,
while
it's
in
this
format
form
to
work
with
our
validators
regardless.
So
we
are
doing
a
code
freeze
on
Thursday,
but
we
will
cut
the
release
once
we
think
we're
ready
what
you
know
highway
is
stable
enough
and
we've
we've
identified
all
the
the
child.
You
know
the
first
of
front-running
issues
and
we've
tuned.
The
we've
got
the
metrics.
D
We
need
in
place
to
go
into
alpha
test
that
we're
going
to
then
cut
the
release
so
probably
going
to
cut
the
release
sometime
next
week,
and
this
you
know
situation
is
developing
rapidly,
so
we're
just
trying
to
be
as
agile
as
we
can
in
this
case,
not
the
most
ideal
situation,
but
where
we're
gonna
be
transparent
about.
How
were
you
know,
failing
and
learning
here,
moving
along
current
focus,
so
testing
and
debugging
Kasper
labs,
honest
highway
will
continue
to
moving
standard
payment
to
hoe
side
and
making
sitting
there
turbo
mode
as
default.
D
What
this
means
is
that
in
Genesis
there
are
there's
no
contract
hashes,
you
need
for
Genesis
for
these
system
contracts,
and
so
that's
really
what
making
turbo
mode
as
default
means
is
that
there's
only
one
way,
one
basic
way
to
start
the
execution
engine
and
and
go
through
Genesis
and
it's
this
will
simplify
Genesis
quite
a
bit
because
you
don't
have
to
worry
about
compiling
the
system
contracts
yourself
and
including
them
to
get
the
Genesis
hash.
So
that
was
going
to
be
a
bit
of
a
challenge
with
the
generic
contracts.
D
We
are
s
tests
our
test
framework.
You
can
see
that
in
github,
that
is
also
hot
off
the
presses
right,
so
we've
been
building
a
test
framework
to
test
large.
You
know
perform
large-scale
production
engineering
testing
of
the
system,
that's
also
half
the
presses,
so
we
continue
to
iterate
on
s
test.
As
we
do
the
testing
itself,
we
are
formalizing
our
approach
to
spam
protection.
A
spam
protection
is
the
equivocation
bomb.
We
have
a
fix
that
is
in
in
research.
D
Andreas
is
integrating
his
fix
into
the
mathematical
proofs,
so
there
will
be
an
update
to
the
highway
specification
and
the
equivocation
bomb
we
elect
referred
as
equivocation
bomb
is
basically
a
vulnerability
that
exists.
An
all
dag
based
fork,
choice,
dag
protocols,
so
there's
two
rather
large
protocols
out
there
on
on
in
the
space
that
are
susceptible
to
this
attack.
D
I
believe
neither
of
those
protocols
are
decentralized.
They
probably
are
not
decentralized
because
of
this
problem.
If
I
was
in
charge
of
those
protocols,
I
would
not
decentralize
them.
I
would
have
like
you
know
either
I
would
be
checking
for
trusted,
validators
or
selecting
the
validator
set
to
ensure
or
reduce
the
likelihood
of
a
bad
validator,
throwing
an
equivocation
bomb.
This
is
one
of
the
things
that
we're
doing
that's
really
hard.
When
I
talk
about
you
know,
building
a
decentralized,
open,
permissionless
network,
it's
a
hard
thing
to
do.
D
This
is
why
it's
a
hard
thing
to
do.
You
find
these
attacks
so
we're
integrating
that
the
the
proofs
into
the
proofs
making
sure
the
proofs
still
hold
up,
and
then
we
will
go
into
implementation.
We're
going
to
go
into
that
implementation
as
part
of
alpha
tests
net,
so
we'll
probably
be
making
the
changes,
the
communication
protocols
what
will
be
updated
likely
as
a
result
of
this?
That's
our
that's
that
piece.
D
D
Lift
breed,
why
don't
you
ask
your
questions
after
my
update
sounds
good
and
then
on
the
node
side,
we
are
focused
a
lot
on
stability,
optimizations
and
performance
of
the
node
and
stress
testing
of
the
network,
we're
also
implementing
the
is
orphaned
flag.
So,
in
the
event
that
a
block
does
get
orphaned,
there
will
be
a
very
clear
flag
that
that
provides
that
this
is
the
ante
is
finalized
flag,
we're
actually
updating
and
adding
consensus
metrics
to
monitor
for
monitoring
the
protocol.
This
is
again
part
of
the
production
engineering
plan
and
we're
working
on
deploy.
D
D
We
are
removing
bonding
and
unbonded
for
alpha.
So
the
reason
we're
removing
the
calls
is
for
the
first
round
of
alpha
test
net.
We
want
to
work
with
a
closed
set
of
validators
when
we
go
into
the
second
round
likely
in
the
May
time
frame,
we
will
reintroduce
bonding
and
unbonded.
There
are
a
few
considerations
when
we
before
we
add
bonding
and
unbonded.
This
basically
enables
anybody
to
join
the
network.
At
any
time,
this
is
the
decentralized
nature
of
it.
One
is
we
knew
that
we
have
the
equivocation
bomb.
That
needs
a
fix.
D
The
second
thing
is,
we
would
need
to
figure
out
how
much
how
the
validator
games
will
work
in
terms
of
the
bond
amounts
and
what
the
implications
are
for
the
faucet.
So
we
wanted
to
make
sure
that
we
really
had
all
those
questions
answered
and
with
respect
to
the
validator
games
for
alpha
we're
doing
some
documentation
on
assembly
script.
D
We
do
support
assembly
script
contracts,
but
we
need
to
finish
up
the
documentation
on
how
to
use
assembly
script
and
this
smart
contract
library
for
assembly
script
and
then,
of
course,
tutorials
to
go
with
it
and
then
the
proof
of
State
contract
needs
some
modifications
to
support
the
highway
protocol
and
so
those
those
last-minute
changes
that
are
getting
pushing
the
execution
engine.
As
far
as
I
know,
these
are
on
track
for
Florida,
Thursday,
tessa,
sorry,
again,
estás
integrating
with
ansible
and
run
dec.
D
So
it's
really
easy
to
spin
up
whole
AWS
internet
works
and
put
them
under
load
and
testing,
and
then
we're
also
setting
up
the
infrastructure
for
alpha
test
net,
setting
up
all
the
ansible
roles
for
the
primary
nodes
that
we
will
be
supporting
and
hosting
or
test
net.
Of
course,
all
the
other
validators
will
have
their
own
infrastructure
to
set
up
and
and
join
the
network
spin
it
up
and
spin
down
and
install
updates
ecosystem.
D
It
is
our
intention
to
support,
deploy,
signing
within
clarity
and
deploy,
sending
within
clarity,
we're
also
gonna
get
Google
Analytics
working
on
clarity,
as
far
as
I
knew
I
thought
that
was
already
done,
but
it
might
be
a
little
delayed
and
then
we're
going
to
update
the
DAP
developer
guide
with
the
new
assembly
script.
Information.
D
Economics
research
Alexander's
going
to
be
presenting
today
and
then
we're
also
going
to
be
figuring
out
our
validator
community
engagement
and,
more
broadly,
the
community
engagement
strategy
and
then
they're
also
looking
at
how
the
l
RTS
are
consuming
resources.
So
we
understand
what
disk
memory
and
CPU
utilization
looks
like
in
a
fully
loaded
system
and,
of
course,
with
covet
19
we're
probably
gonna
have
our
off-site
online.
Unfortunately,
we
were
hoping
on
getting
together,
but
in
the
interests
of
everyone,
well
travel
bans
notwithstanding
we'll
probably
do
this
remotely.
D
We've
got
our
weekly
workshops.
Every
Thursday
morning
at
8
a.m.
Pacific
and
Thursday
evening
we
are
going
to
figure
out
exact
timings,
ma
che
and
Pio.
2D
are
also
going
to
be
working
on
smart
contracting
workshops
during
their
time.
They
are
based
in
Europe,
so
being
the
European
time
zone,
approximately
nine
hours
ahead
of
our
time
zone.
So
sometime
in
that
window,
they
will
be
setting
up
workshops
to
talk
about
how
to
write
contracts
and
how
to
work
in
and
with
the
system
and
build
smart
contracts.
So
they
will
be
setting
that
up
independently.
D
Look
for
those
updates,
discord
and
telegrams.
So
receipt
you
know
for
folks
over
in
India
and
Europe.
It
will
be
easier
for
them
to
engage,
be
a
little
hard
for
us,
but
we
always
have
our
8:00
a.m.
slots
that
we
can
always.
You
know,
drop
that
into
fantastic.
We
have
somebody
that
raised
their
hand,
but
unfortunately,
I
think
that
they
dropped
off
I,
don't
know
if
they
put
their
question
in
the
channel
at
all
between
now
and
then
I
didn't
see
it.
C
Before
I
explain
what
this
is
so
I
believe
it
was
previously
discussed
in
one
of
these
meetings
that
you
know
ER.
So
then,
if
you're
trying
to
solve
the
problem
of
gas
price
volatility
that
plagues
platforms
like
etherium-
and
you
know
this
is
a
very
complex
problem.
You
know
it's
very
difficult
to
come
up
with
a
comprehensive
solution.
C
So
initially
we
intended
to
do
sort
of
a
stopgap,
as
that
is
not
ideal,
effectively
amounts
to
price
fixing,
but
should
probably
do
the
job
for
a
few
months,
and
this
fix
is
basically
you
know
once
we
you
know
once
we
do
all
the
measurements
on
the
you
know,
time
use,
but
virtual
opcodes,
we
assign
you
know
to
one
unit
of
gas
v
aside
a
real
dollar
price.
Now,
of
course,
in
order
for
the
system
to
remain
convenient.
C
For
you
know,
validators
a
user
is
a
should
be
able
to
pay
transaction
fees
in
CLX,
whereas
thousand
dollar,
so
you
know.
So
how
do
we
actually
do
the
fixin?
Well,
we
do
the
fixed
and,
by
you
know,
link
in
our
transaction
process
into
external
deed,
from
exchanges
right
so
and
things
that
you
see
on
your
screen
is
a
document
that
they,
unfortunately
still
in
preparation
as
it
is
intended
for
our
leadership
team,
as
it
will
present
multiple
options
for
how
this
will
be
done.
C
So
our
default
option
was
considered
to
be
a
chain
link
and
I've.
Read:
there's
a
chain
link
white
paper
and
I'm
in
the
process
of
reviewing
their
node
operators
guide,
but
I
believe
that
there
may
be
some
issues
with
using
this
as
the
driver
here,
because,
while
chain
link
claims
that
you
know
their
infrastructure
can
be
set
up
on,
you
know
many
major
block
chain.
It's
not
currently
clear
to
me
exactly
what
sort
of
features
do
they
expect
and
you
know
whether
V,
actually
you
know,
support
all
the
features
that
they
need.
C
Alright,
so,
for
example,
in
etherium
they
require.
You
know,
there's
a
it's
assumed
that
you
know
participants.
It
was
actual
providers
of
data
rights
in
disease.
You
know
intermediate
oracle
nodes,
the
monitor.
You
know
the
events
tree,
but
you
know
it's
some
clear
how
this
would
work
on
our
system.
But
again
this
is,
you
know
the
suspended
me
door
finishing
even.
C
However,
one
thing
is
that
you
know
presents
itself
as
an
immediate
alternative.
If
you
know
chain-link,
I,
the
two
aetherium
or
two
other
platforms
to
be
easily
into
for
us.
So
another
alternative
is
that
we
could,
you
know
basically
just
implement
our
own
fairly
simple
oracle.
Right
I
mean
so
you
know
the
you
know
the
final
version
of
this
document.
Will
you
know
going
to
detail
the
pros
and
cons
of
this
but,
of
course,
I'm
a
jerk.
C
The
operation
of
this
Oracle
is
to
be
subject
to
you
know
our
Gordon's
processes,
which,
hopefully
you
know
hopefully
should
take
care
or
was
a
decentralization
concerns,
but
so
the
attractor
source
option
is
that
it
could
conceivably
be
much
simpler
and
you
know
avoid
making
payments
to
third
parties
right,
because
the
fact
you
know
we
would
operate.
You
know
all
the
you
know,
links
and
that
chain
right
the
right
up
until
the
point
where
it
causes
extreme
and
remember
that
we
don't
you
know
in
this
particular
instance.
C
We
only
need
the
data
from
handful
of
you
know.
Well
they
you
know
designated
sources
right,
I
mean
we
don't
need.
You
know
Oracle's
to
go
and
get
creative
about
how
they
procure
this
information.
You
literally
just
need
an
interface
to
you
know,
essentially
a
big
website
sitting
outside
the
blockchain.
C
The
final
fullback
that
I
will
eventually
discusses
documented
cones.
The
manual
mode,
which
is
essentially
you
know,
there's
a
team
at
Casper,
Labs
literally
in
devious,
you
know
set
in
is
the
price
for
the
cilix
use.
D
pair,
you
know
maybe
on
a
daily
basis
or
something
exactly
mean.
This
is,
of
course,
not
really
stuff.
You
would
plan
to
do,
but
this
be
you
know
something
you
could
consider
is
a
you
know,
an
emergency
fallback,
for
example.
C
You
know
if,
for
some
reason
you
know
the
api's
or
for
major
exchanges
fail
for
something
that
nature
you
know
if
we
implement
chain
like
for
some
reason.
No
something
goes
over.
It
is
you
know
so
so
this
is
the
status
of
you
knows.
You
know
work
on
this
component.
Those
the
gas
pricing
model
remember
is:
is
there
are
two
other
components
in
it?
One
of
them
is
one
of
them
is
actual.
C
You
know,
measurement
of
compute
time
used
by
you
know
individual
op
codes,
and
you
know
currently
our
EE
team
is
very
busy
of
course.
So
you
know
right
now.
That
component
is
temporarily
on
hold
and
the
third
component,
which
we
did
not
yet
start
on,
is
you
know
the
the
mechanism
for
adjust
and
this
in
a
real
goal
or
price
its
we're
gonna
be
set
in
Genesis
right.
C
D
Terrific
yeah,
the
fix
the
fixed
transaction
price
problem
is
a
hard
problem
to
solve
because
it's
always
possible
to
potentially,
you
know
to
dasa
a
node
out
by
its
just
sending
an
infinite
loop
right,
and
this
is
something
that
the
gas
pricing
model
does
solve
very
elegantly.
Ultimately,
in
the
final
analysis,
it's
all
about
scalability
is
why
gas
prices
tend
to
go
up
right.
So
the
long
term
solution
is
absolutely
implementing
a
scaling
solution.
D
Then
you
don't
necessarily
heat
a
peg
right,
but
irrespective
of
a
scaling
solution,
I
think
now,
businesses
and
users
tend
to
be
a
little
bit
gun
shy
with
you
know,
without
having
the
peg
I
think
it
makes
them
feel
a
lot
more
comfortable
for
lack
of
a
better
term.
So
we're
also
working
on
trying
to
get
together
with
the
chain
link
guys
we
had
a
meeting
set
up
with
them
and
I
think
the
travel
ban,
kind
of
got
in
the
way,
and
things
got
a
little
crazy,
so
I'll
be
reaching
out
to
them
again.
C
C
D
C
Yes,
sir,
my
microphone
screws
up,
sometimes
right
so
I
remember,
is
that
you
know
we
don't
have
to
just
hope.
Is
that
eventually
we'll
achieve
scalability,
you
know
there's
probably
going
to
be
a
solution
before
Xen.
Does
that
feel
a
dampen?
You
know
the
little
tap
and
price
volatility
right,
because
again
we
can
weaken
price.
We
can
find
a
way
to
price
future
gasp.
Basically,
we
just
don't
know
exactly
how
to
do
it
now,
but
there
is
a
way
yep.
D
D
A
C
A
D
D
Yeah
absolutely
I
mean
at
the
entire
idea
is
to
provide
stability
to
end
users
and
developers,
and
we
certainly
will
need
some
kind
of
a
fallback,
that's
clear
yeah.
So
it's
part
of
the
test
net
program,
one
of
the
things
you're
gonna,
be
focusing
a
lot
on
really
is
engagement
and
governance.
I
just
trial
by
fire,
we're
just
gonna
jump
right
into
the
fry
pan
and
see
what
the
natural
like
we're.
Gonna
try
to
get
organized
with
validators
right
and
casper
labs.
D
You
know
the
way
I
look
at
it
is
we're
a
steward
of
the
blockchain
we're
not
in
control
of
the
blockchain,
but
we
are
steward
of
the
blockchain,
and
so
we
help
assure
things
in
we
help
organize
things,
but
we
should
not
be
essential
right.
The
idea
is
that
we
kind
of
step
away
from
it
with
our
hands
up
in
the
air
and
let
ultimately
the
validators
and
the
community
over
time
take
ownership
of
the
blockchain.
That's
the
that's!
D
The
sincere
desire
from
this
group
so
we'll
be
looking
at
setting
up
these
governance
processes
and
them
as
decentralized
way
as
possible
right
and
have
to
see
if
the
validators
how
they
want
to
organize
and
how
they
want
us
to
be
delivering,
updates,
etc,
etc.
So
we're
gonna
try
to
do
this
and
as
to
centralized
ways
possible.
That's
the
spirit
of
the
alpha
test
that
time
frame
so
pushing
hard
towards
that
I.
Don't
think,
there's
any
more
update.
So
we
can
adjourn
a
little
early
today
and
talk
to
everybody
next
week.
Please
stay
safe
out.