►
From YouTube: CasperLabs Community Call
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Good
morning,
good
afternoon,
good
evening,
wherever
you're
coming
to
us
from
my
name,
is
metta
parlikar,
I'm
the
cto
and
one
of
the
co-founders
of
casper
labs,
and
today,
I'm
going
to
provide
an
engineering
status
and
project
update
for
the
launch
of
the
casper
blockchain
scheduled
for
q1.
We
are
targeting
end
of
february
early
march
for
the
launch
of
the
public
blockchain.
A
I'm
joined
here
by
piotr
our
program
manager
alex
liminov
one
of
our
economists,
because
we
often
have
questions
around
economics
of
the
blockchain
as
well
as
folks
from
our
community.
So
without
further
ado
I'll
get
started,
we
just
entered
our
10.1
sprint.
A
A
Most
recent
cut
is
tag
0.51
that
was
cut
on
january,
7th
and
deployed
to
the
delta
test
net
that
was
delta,
8.
delta
8
did
get
quite
a
bit
of
great
traction.
I
think
we
had
106
validators
on
the
network
before
we
started
seeing
gossiping
problems,
networking
and
connectivity
problems.
Ironically,
our
nodes
are
the
ones
that
went
offline,
so
we're
also
looking
to
replace
the
small
network
components
so
we're
seeing
that
the
small
network
component
wasn't
production
grade
and
we're
definitely
seeing.
A
You
know
the
effects
of
that
in
the
network
right
now,
because
the
system
is
falling
over
when
we
start
getting
to
all-time
highs
in
terms
of
the
number
of
validators
joining
all
right.
So,
let's
push
down
a
little
further,
so
we're
implementing
evicting
validators
that
are
having
liveness
failures
and
that
is
designing.
You
know
we're
designing
how
to
disable
bids
in
the
auction
contract
for
aliveness
favor
failure
and
then,
of
course,
we're
designing
crash
recovery.
A
So
this
is
really
about
how
we
pick
up
in
the
event
of
a
critical
failure
in
the
network.
As
indicated
on
the
rust
side,
we're
replacing
gossiper
component
with
lib
p2p,
and
then
we
are.
This
is
again
more
hardening
right,
so
the
rpc
endpoint
will
return
an
error.
If
the
deploy
is
invalid
and
then
we
want
to
switch
to
stable
rust.
I
think
we're
on
nightly
before
we
cut
our
production
release,
you
want
to
go
to
stable
and
then
we're
implementing
tracking
the
validator
set
when
synchronizing.
A
So
if
you
have
a
long
synchronization
time
frame,
then
the
validator
set
changes.
You
want
to
make
sure
that
you're
only
getting
blockchain
information
from
a
trusted
validator
or
somebody.
That's
part
of
the
active
validator
set
on
the
test
and
sre.
A
We
are
working
really
around
orchestration
of
testing
infrastructure,
and
you
know
this
is
something
we've
been
investing
in
from
the
very
beginning
to
enable
us
to
whoops.
I
have
to
update
my
gpg
update
to
basically
test
large-scale
networks
right
both
for
from
from
a
hardness
perspective
and
a
scaling
perspective.
So
this
is
something
we
continue
to
invest
in.
B
Yeah,
so
philip
in
fact,
is
working
on
the
contract,
upgrading
examples
and
julia
who
is
who
joined
us
recently.
She's
on
on
the
first
point
here
and
since
she's
still
struggling
with
the
move
to
switzerland
and
she's
part-time,
then
we
split
this
into
it
spans
over
two
sprints,
so
yeah.
A
Got
it
excellent,
great,
very
exciting
news
that
we
are
handing
the
clear
handing
clarity
over
to
community
members,
so
it's
going
to
folks
that
are
not
part
of
the
core
development
team
and
so
we're
starting
that
process
of
handing
it
over
today.
This
week,
I
believe
the
team
had
their
first
meeting.
Is
that
correct
people?
I
guess.
B
A
B
First
of
all,
we
split
the
contents
of
the
reaper.
We
want
to
extract
the
javascript
sdk
we
want
to,
as
we
want
to
make
sure
that
we'll
separate
the
clarity
from
any
other
elements,
and
then
we
are
discussing
today
there
will
be
a
follow-up
meeting
where
to
host
it.
In
fact,.
A
Okay
yeah,
so
we
should
look
at.
You
know
how
we
want
to
separate
the
code
base
as
well
for
clarity,
if,
if
we
want
it
outside
of
the
casper
labs
repo,
if
we
want
to
keep
it,
we
should
figure
out
how
that's
going
to
work.
Okay
and
yeah
an
example
for
upgrading
a
contract.
So
this
is
going
to
be
beneficial
for
developers,
so
they
know
how
contract
upgrades
work
in
casper
consensus
paper
econ
paper,
harmonization
alex
I'm
really
excited
to
see
the
econ
paper.
I
know
that
there
is
a
a
draft.
C
Well,
yes,
you
said:
there's
sort
of
a
draft,
it
doesn't
really
have
any.
You
know
anything
interesting
in
it.
Yet
right,
I'm
still
reading
the
consensus
paper
again,
and
so
once
that
should
be
done,
you
know
I'll
be
adding.
You
know
pieces
to
it
that
in
some
cases
all
exist
elsewhere,
but
you
know
so,
for
example,
there's
going
to
be
a
new
section
on
you
know
a
slashing.
C
You
know:
rework
probably
of
the
reward
scheme,
description,
description
of
the
options
I
mean
once
those
are
added
they
get.
You
know
that
be
actually
useful
for
people
to
read,
but
that's
still
not
the
complete
paper,
because
we
have
so
many
features
that
you
know
it's
gonna
be
a
while
before
it's
complete,
complete.
A
Yeah,
I
really
need
you
to
bear
down
on
it
like,
for
example,
there
is
a
post
I
was
looking
at
on
for
cosmos
network.
It
states
very
clearly
here's
what
you
need
in
order
to
become
a
validator
right.
A
So
I
understand
completely
understand
that
the
auction
contract
is
wide
open
right,
like
we
don't
know
how
much
right,
how
much
stake
is
ultimately
going
to
be
required
in
order
to
become
a
validator
in
the
network,
because
the
way
the
auction
contract
works
for
folks,
that
don't
understand
is
that
it's
always
the
rotating
top
set
right
so
based
on
stake.
The
top
x
number
of
validators,
with
the
most
stake,
are
the
ones
that
join
the
validator
set
and
delegators
right.
A
Only
the
validators
receive
block,
rewards
right
or
seniorage,
so
people
that
are
delegating
to
a
validator
will
basically
be
able
to
drive,
who
becomes
a
validator
set
right
through
state
delegation,
so
I
may
you
know
only.
I
may
have
like
a
million
tokens
in
stake,
but
only
30
percent
of
those
tokens
would
be
mine.
A
For
example,
70
could
just
be
all
from
delegators,
and
you
know
I
would
receive
some
percentage
of
of
a
commission
for
providing
the
service
of
running
the
node
as
a
result,
and
so
it's
kind
of
hard
for
us
to
say
like
what
is
the
minimum
amount
of
stake
that
you're
going
to
need
in
order
to
make
it
into
the
validator
set
depending
on
you
know
what
the
distribution
of
stakes
are,
it
could
be
reasonably
high
or
it
could,
it
could
even
become
like
you
know,
we
have
a
few
very
large
validators
initially
and
then
we
can
have
other
people
get
in
and
as
folks
delegate
their
stake,
they
can
work
their
way
up
into
becoming
one
of
the
larger
validators
so
but
having
some
kind
of
economic
analysis
around.
C
Yes,
so
yeah
I
mean
there's
a
last
figures.
Actually
you
know
so
something
that
they
didn't
occur
to
me
initially,
but
yeah
you're
completely
right.
It
will
be
in
the
options
section.
C
There
is
going
to
be
a
bump
there,
because
you
know
I
mean
the
reward
section
is
pretty
complicated
and
you
know
it
needs
to
be
to
conform
to
what
we
actually
implemented.
C
So
you
know
it's
it's
going
to
be
quite
tricky
but
I'll.
Consider,
basically,
you
know
I'll
add
these
sections
before
we
like
tightly
reward
one.
You
know
so
that
people
can
read
about
it.
A
Yep
sounds
good,
sounds
good
on
the
contract
runtime.
This
is
the
execution
engine.
The
you
know
the
the
vm
we're
going
to
be
applying
host
cost
to
all
the
host
side
system
contracts.
So
there
will
be
right
now.
If
you
do
wasmless
transfer
that's
host
side,
it
doesn't
cost
anything
right.
So
we're
gonna
and
much
like
ethereum
right,
there's
a
fixed
cost
to
transfer
ether.
We're
gonna
do
the
same
thing
here
on
casper
we're
also
going
to
get
rid
of
some
of
the
system
contracts.
A
So
for
those
of
you
that
have
ever
tried
to
compile
from
source,
you
know
that
you
need
pre-compiled
webassembly
in
order
to
run
a
node
compiled
from
source,
and
that
is
a
vestigial
thing
like
that.
You
know.
Originally,
our
design
was
that
the
implementation
of
the
blockchain
would
be
so
generic
that
even
the
system
contracts
would
be
deployed
like
contracts
like
any
other,
but
we
since
have
stepped
away
from
that
for
performance
optimizations.
A
We
have
stepped
away
from
that,
and
also
in
a
wasm
compilation
is
non-deterministic,
so
it
would
actually
be
harder
to
decentralize
without
having
the
system
contracts
be
host
side.
So
we
have
pushed
away
from
that
and
so
we're
removing
them.
There's
a
third
piece
to
piotr
we're
actually
removing
the
account
hash
implementation
and
going.
C
A
Public
key
plus
encryption
curve
right
so
that's
also
happening
the
contract
runtime.
If
I
understand
correctly,
yes,
yeah,
there's
all
that's
also
some
node
rs
work,
because
that
cuts
all
the
way
through
the
system.
It's
really
unfortunate,
but
we
discovered
we
received
feedback
from
our
custody
provider
and
we
discovered
that
account
hash
is
going
to
be.
A
This
creates
a
disconnect
right
that
will
make
users
uncomfortable
right
because
now
suddenly.
Well,
I
set
my
token
to
this
public
key
and
I'm
looking
at
this
thing
and
there
isn't
really
any
way
for
me
to
reconcile
what
the
account
hash
is
and
how
does
it
correspond
to
the
public
key
there's,
no
way
to
backward
engine
backwards,
engineer
a
hash
right,
so
that
provides
a
lot
of
security.
So
that's
why
we're
doing
what
we're
doing
there
on
team
and
company
update?
So
you
can
always
join
the
zoom
here
next
week.
A
I
believe
starting
the
19th,
which
I
think
is
next
week
we
are
going
to
be
changing
the
format
of
these
calls.
I
will
continue
to
provide
the
engineering
update,
but
we're
also
going
to
have
our
partners
some
of
our
strategic
partners
and
our
advisors
and
other
folks
joined
the
call
to
talk
about
how
they're
participating
in
the
project
why
they're
participating
with
casper
lab
so
we're
going
to
be
opening
it
up
to
some
of
our
community
members
to
join
the
call.
So
look
look
forward
to
that.
I'm
very
excited
about
this
new
format.
A
It'll
provide
a
lot
more
meat
and
you
know
information
for
those
of
you
that
are
dialing
in
so
any
questions
for
folks
on
the
call,
I
believe
we're
also
planning
to
do
an
ama
on
these
calls
moving
forward.
So
there's
going
to
be
much
more
of
an
ama
format.
Every.
A
A
Who
is
our
custody
provider?
So
this
is
super
exciting.
I
believe
marketing
wants
me
to
wait
till
they
do
a
proper
announcement,
but
I'll
give
you
guys
a
small
sneak,
peek,
it's
bitco,
so
we're
very
excited
about
that
they
don't
take
on.
A
They
have
been
turning
down
protocols
more
often
than
not,
but
they
were
so
impressed
with
the
work
that
we
have
done
both
on
the
protocol,
and
you
know
our
responsiveness
and
our
professionalism
that
they
agreed
to
integrate
with
us.
So
we
expect
the
integration
to
be
done
by
february.