►
From YouTube: CasperLabs Community Call
Description
Engineering update, Delgator UX, How Casper is different from Ethereum, why CasperLabs is launching a separate blockchain
A
Good
morning,
good
afternoon,
good
evening,
everyone
from
wherever
you're
joining
us,
my
name
is
metta
parlikar,
I'm
the
cto
of
casper
labs,
and
today
I
will
be
sharing
our
engineering
status
update
and
we're
going
to
talk
a
little
bit
about
what
I'm
most
excited
about.
The
next
big
milestone,
I'm
most
excited
about.
So
let's
get.
A
Started
see
my
screen
yeah,
it
looks
good
all
right,
so
the
team
has
entered
the
second
weekly
sprint
of
the
20.10
release
cycle.
This
is
sprint
6.2.
The
focus
of
this
cycle
is
to
launch
delta
test
net
with
a
minimum
of
50
validators.
A
Today
we
will
be
cutting
a
release,
one
of
our
first
debian
packages
from
the
rust
repository.
We
have
made
the
rust
repository
public,
so
those
of
you
that
are
interested
in
seeing
what
we've
been
working
on
for
quite
some
time.
You
can
check
it
out
at
casper
dash
node
on
casper
lab,
so
that
is
the
new
rust
node
that
we'll
be
going
to
delta
test
net.
A
With
this
release,
we're
going
to
basically
get
to
a
place
where
economics
complete
and
security
complete,
pretty
close
to
code
complete,
there's
a
few
additional
features
that
we
intend
on
implementing
to
make
the
blockchain
much
much
more
user-friendly
and
powerful,
but
those
that's
going
to
be
the
unification
of
accounts
and
contracts,
payments,
2.0
and
the
state
pruning
and
garbage
collection.
A
So
you
can
go
check
out
that
repo
here
casper
dash
node
for
those
of
you
that
are
curious
about
what
it
is
they've
been
working
on.
A
We've
got
our
documentation
up
there
and
the
process
of
running
a
node
is
different,
but
you
can
definitely
run
a
node
locally
on
your
machine.
We
don't
have
debian
packages
as
yet,
but
we
should
have
them
shortly.
A
Skipping
forward
test
net,
the
beta
test
net
is
stable.
We
have
40
validators
that
are
in
sync,
and
the
test
net
is
healthy
and
working
as
intended,
we'll
be
loading
launching
the
charlie
network,
the
charlie
russ
network.
This
is
the
thing
that
I'm
very
excited
about
I'll,
be
working
with
about
five
of
our
validators
that
were
participated
in
the
alpha
test
net
to
launch
this
network
I'll,
be
working
with
them
today
to
kick
that
off,
and
it's
going
to
be
a
little
bit
of
a
bumpy
road.
A
We
know
there's
a
lot
of
things
that
the
net
that
the
system
needs,
but
I'm
excited
to
have
them.
You
know,
put
the
code
in
their
hands
and
start
getting
feedback
on
current
focus
on
highways,
so
we
are
working
on
our
permissionless
features.
That
is
validator
set
rotation
slashing
right,
so
we're
going
to
slash
for
equivocation,
so
we
already
detect
equivocations,
but
we
don't
slash
for
them.
We
will
now
slash
for
them
we'll
be
implementing
the
highway
core
security
features,
so
these
are
defenses
against
the
equivocation-based
spam
attacks.
A
A
So
if
you
go
into
casper
labs
here
and
you
look
at
highway,
you'll
see
that
we
have
an
open
pull
request.
So
these
are
new.
This
is
the
section
about
spam.
So
if
you
want
to
understand
what
the
spam
attack
is,
you're
absolutely
welcome
to
review
this.
We
are
partnering
with
cardinal
cryptography,
they're
working
on
the
aleph
protocol.
A
They
understand
consensus
protocol,
so
they
are
collaborating
with
us
to
help
get
the
paper
updated
and
andreas
is
doing
the
review
for
all
of
that
work
on
the
rust
side
on
the
node
rust
side,
so
we're
doing
a
lot
of
design
work.
As
I
indicated
before,
we're
going
to
be
providing
merkle
proofs
for
the
global
state
because
we're
going
to
be
doing
state
passing
for
fast
synchronization,
this
is
going
to
be
available
at
the
main
net
launch.
This
is
something
that
is
new
and
important,
but
planned
for
the
rust
work.
A
For
quite
some
time,
we're
implementing
some
infrastructure
for
improved
testing
and
rust
node.
This
part
of
this
is
the
s-test
work.
Part
of
this
is
the
lrt
work,
terraform
and
ansible
we're
improving
the
node
api
to
support
client
interfaces
and
adding
more
features
to
rust
clients.
A
You
can
imagine
how
this
work
is
going
we're
you
know
getting
the
rust
client
to
feature
parity
with
the
python
client,
as
we
do
that
we
discover
there's
things
that
are
needed
in
the
rust
node
and
so
we're
implementing
those
kind
of
back
and
forth
back
and
forth.
Frazier
is
doing
this
work
test
and
sre
support
to
launch
the
network,
with
five
validators
supporting
beta
test
net.
A
Doing
some
updates
in
s
test
to
get
it
to
work
with
the
rust
node,
and
then
we
are
continuing
automation
that
is
really
work
around
lrt
and
adding
more
tests
to
lrt3,
where
we
test
a
geographically
distributed
network
with
20
to
50
validators
we're
also
partnering
with
sensei
group.
I'm
very
excited
about
this
sensei
group,
his
team
of
developers.
A
They
actually
implemented
the
original
boot
node
back
in
march
of
2019
way
back
when
they're
going
to
be
working
with
us
to
test
and
harden
the
rust
node,
they
will
be
kicking
off
this
week
with
the
new
debian
packages,
they're
really
going
to
put
a
lot
of
pressure
into
the
node
and
the
networking
protocol.
It's
going
to
help
us
with
hardening
ecosystem
design
of
payments.
2.0
we've
got
mate
on
the
line
matches
our
smart
contract
developer
and
our
voice
of
the
user
voice
of
the
customer
on
the
project.
A
He's
done
great
work
with
really
specifying
what
the
dapp
developer
experience
needs
to
be
at
a
very
low
level,
so
he
was
responsible
for
a
lot
of
the
work
on
smart
contracts
around
the
dsl
he's
the
guy
that
wrote
the
solidity
transpiler
the
big
chunk
of
the
lift
that
we've
done
for
the
casper
side
of
it
to
create
casper
contracts
and
he's
been
a
phenomenal
developer
advocate
internally
about
making
the
system
easier
to
use
for
adapt
developers
he's
also
the
guy
that
does
our
weekly
workshops.
A
We've
got
improvements
for
the
proof
of
concept
for
ipv
around
privacy.
Ipwe
had
a
requirement
to
be
able
to
support
private
two-party
transactions
on
the
chain,
and
so
we've
been
doing
some
work
with
seiler
from
the
ethereum
foundation.
Seiler
is
a
big
guy
around
cryptography,
so
he's
got
some
work,
he's
been
doing
for
the
proof
of
concept.
There
we're
doing
some
updates
to
the
user
experience
and
the
ux
for
clarity.
This
is
a
cleaner
skin
and
simpler
user
experience.
A
Mache
is
working
on
a
review
of
the
token
standards
and
the
wired
landscape
of
defining
a
casper
token
standard
we'd
also
like
to
have
the
casper
token
actually
implement
the
token
standard.
So
this
gets
a
very
clean
and
straightforward
way
of
dealing
with
tokens
on
the
casper
platform.
So
basically
the
casper
token
implements
the
casper
token
standard,
as
well
as
providing
a
token
standard
that
is
flexible
and
easy
to
use.
A
Self-Hosted
blog
we're
going
to
support
creating
blog
posts
by
github.
I
got
the
initial
uat.
We
did
a
uat
for
this
the
other
day
and
very
excited
marketing
team's
very
excited,
because
we
want
to
be
going
into
big
content
creation
mode
as
we
get
ready
for
our
our
main
net
launch.
We
want,
we
know
folks
want
to
hear
from
the
developers.
A
So,
for
example,
when
mache
talks
about
the
casper
token
standard,
he
can
write
a
blog
post
about
that.
He
can
do
that
using
github
we're
creating
a
generic
voting
app
we'll
be
updating
some
new
designs
for
that,
and,
hopefully
open
sourcing,
both
the
code,
the
web
code,
for
that,
as
well
as
the
smart
contract
code
on
economics,
we
continue
prototyping
the
chain
link,
casper
labs
adapter.
A
This
has
been
going
on
for
some
time,
but
it's
fairly
challenging
what
we're
looking
to
build
because
we'll
be
the
first
protocol
that
would
do
any
kind
of
chain
link
cl
integration
at
the
protocol
level
versus
at
the
contract
level.
So
it's
definitely
a
lower
level
integration
and
makes
it
very
challenging
we're
also
investigating
gas
futures
and
writing
preliminary
specs.
We
have
rejected
cep,
pull
7
as
it
doesn't
meet
the
requirements
for
price
stabilization
properly.
A
It's
very
interesting
research
work
and
we
submitted
this
work
to
the
ethereum
foundation
in
the
event.
Ethereum
wants
to
use
it
because
I
think
it
does
move
the
ball
up
field
for
what
the
problems
that
ethereum
is
having
right
now
in
terms
of
instability
of
prices,
but
it
doesn't
meet
the
requirements
for
what
we
want
to
do
so
we're
going
to
actually
look
at
implementing
gas
futures
as
a
way
for
customers
to
really
be
in
charge
of
stabilizing
their
prices,
and-
and
this
is
a
flexible
and
powerful
feature
as
we
envision
it.
A
So
owner
is
going
to
start
working
on
that
right
away
on
the
contract,
runtime
and
node
scala.
We
don't
have
much
work,
we're
doing
on
it
now,
they're,
more
or
less
feature
frozen,
because
we've
got
dap
developers
that
are
writing
code
against
it.
So
we
want
to
keep
that
as
stable
as
possible,
we'll
restart
work
on
it
once
we
have
designs
and
specs
for
accounts
and
contracts,
unification
and
payments
2.0,
which
majay's
working
on
on
the
team.
A
We've
resumed
some
hiring
very
excited
to
have
dan
werner
join
the
team
as
a
core
russ
developer
he's
going
to
be
working
with
fraser
on
the
rust
node
container,
and
we
also
have
next
week.
We
have
a
dev
trainer,
an
advocate
joining
the
team,
I'm
very
excited
about
this
new
hire.
He's
someone
that
I've
worked
with
before
he's
going
to
be
taking
over
the
weekly
workshops
for
mate
he's.
Also
excellent
at
writing.
Recipes
he's
written
recipes
for
other
protocols,
the
past.
A
I'm
excited
that
he's
going
to
be
joining
us,
we're
searching
for
talented
sres
to
join
our
team
and
we
have
a
very
exciting
rust
developer,
a
very
talented
mathematics,
researcher
and
cryptocurrency
developer.
Very
big
in
the
space
he'll
be
joining
us,
hopefully,
in
october,
we're
waiting
on
final
paperwork
before
we
make
any
announcements,
but
I'm
really
excited
about
this
guy
joining
the
team.
So
it's
very,
very
cool
we
still
hold
our
weekly
workshops,
bless
mate
and
pieter
piotr
and
mark
greenslade
for
providing
content
for
those
that
are
held
twice
a
week.
A
Thursday
7
am
pacific
time
and
friday
at
midnight,
pacific
for
our
folks
in
asia
and
the
zoom
meeting
id
can
be
found
here.
We've
adopted
the
casper
enhancement
process
feel
free
to
take
a
look
at
our
caps,
we're
doing
them
in
a
transparent,
open
manner,
open
for
feedback
from
our
validators
and
app
developers.
So,
if
you're
interested
in
learning
about
what
future
work
we're
doing,
you
can
check
out
that
repository
and
the
details.
A
The
process
can
be
found
at
ceps
that
repo
on
github-
and
we
have
these
meetings
every
morning,
every
tuesday
morning,
at
nine
o'clock
so
and
they're
available
on
youtube
for
live
streaming.
So
that's
my
update
talking
about
what
I'm
most
excited
about.
It's
our
charlie
test
net
that
is
coming
today.
The
goal
of
the
charlie
test
net
really
is
to
create
a
five
node
network
using
the
rust
code.
A
And
so
this
is
the
internal
documentation.
You
can
look
at
this.
This
is
a
public
release.
The
release
section
release
in
atlassian
is
public,
so
you
can
absolutely
anybody
can
go
and
take
a
look
at
our
release.
Plans,
if
you
so
wish
to
do
so
I'll
make
a
point
to
include
this
in
the
documentation
in
the
update,
but
this
isn't
going
to
involve
validators
launching
the
network.
It's
about
the
engagement
to
be
as
decentralized
as
possible.
The
chain
spec
process
will
remain
the
same.
A
So
we
just
pulled
the
requirements
for
the
chain
spec
process
from
forward
from
the
scala
network
into
the
rust
network,
and
that's
what
we're
going
to
be
using
so
it'll
be
very
simple:
they
will
provide
their
public
key
to
us
and
they'll
pull
and
they'll,
basically
we'll
pull
down
accounts.csv
and
the
manifest.tamil
and
basically
launch
the
network
with
a
future
date.
They'll
peer
up
the
nodes
will
peer
up
the
exchange
message.
A
With
the
workload
generators
it'll
be
a
little
scary
for
the
des,
but
we'll
flush
out
a
lot
of
the
issues
and
they'll
learn
a
lot
about
the
system.
A
So
the
subsequent
we'll
run
charlie
testing
it
for
about
three
to
five
weeks
before
we
launch
the
delta
test
net
and
over
time,
we'll
probably
we'll
have
more
validators
join
the
network
if
they
so
wish.
They're
gonna
have
to
roll
their
sleeves
up
because
there
will
not
be
clarity.
Block
explorer,
it'll,
be
mostly
just
it'll
just
be
logs
at
this
point,
so
it'll
it'll
require
a
fair
bit
of
validator
chops
in
order
to
work
with
this
network
in
the
early
days.
A
But
by
the
time
we
launched
delta
test
net
expect
the
same
user
experience
with
charlie
with
the
delta
test
net,
as
you
see
with
the
current
scala
node.
With
that,
I
can
open
up
to
any
questions.
If
there's
any
questions.
B
Yes,
hi,
can
you
just
say
a
few
words
about
the
charlie
ness
test
net
worth
versus
delta
test
net.
A
Sure
yeah
charlie
testnet
we're
not
code
complete
yet
in
charlie
testnet,
so
the
purposes
of
the
charlie
test
net
one
is
to
start
hardening
the
software
as
soon
as
possible.
It
also
helped
kind
of
force
the
engineering
team.
These
milestones,
force
the
engineering
team
to
kind
of
make
sure
that
the
software
is
coming
together
and
there's
a
few
basic
things
that
it
has
to
do,
and
you
know
really.
We
want
to
get
the
software
in
the
hands
of
a
few
validators,
so
they
can
bang
on
it.
A
And-
and
you
know,
once
you
get
the
software
out
in
the
wild,
you
always
get
a
lot
of
feedback
right.
I
mean
developers
like
it
or
not.
They
have
their
their.
You
know
fishbowl
that
they
from
within
which
they
operate
and
and
kind
of
putting
the
software
in
the
wild,
even
if
it's
only
with
a
handful
of
folks
is
going
to
teach
us
a
whole
lot
about
software.
So
this
is
why
getting
the
software
in
the
hands
of
people
early
on
is
so
so
important.
A
A
So
that's
kind
of
my
take
on
charlie
testnet
and
you
know
with
with
delta
test
net.
Of
course
it
will
be
permissionless,
so
we
will
launch
the
genesis
block
with
a
set
of
validators,
but
from
there
validators
will
be
able
to
bond
and
unbond.
A
Additionally
we're
going
to
work
with
eta
on
the
launch
of
the
delta
test
net.
I
would
like
the
eta,
which
is
the
devdow,
to
be
more
fully
engaged
in
the
launch
and
management
of
the
delta
test
net.
So
we
want
it
to
be
as
decentralized
as
possible
and
right
now
you
know
I
manage
most
of
the
launches
of
these
test
nets.
So
I'd
like
to
get
to
a
place
where
eta
takes
a
bigger
role
right.
The
dev
down
takes
a
bigger
role
in
launching
the
network.
B
We're
excited
to
do
that
meta,
and
so
whatever
information
comes
out
of
the
charlie
test
net,
I
think
our
devs
probably
want
to
see
what
what
you
guys
are
doing,
but
we
have
open
communication
channels
anyway,
so
I'm
assuming
you're
making
that
data
available
right.
A
Oh
absolutely,
yes,
the
data
is
completely
available.
Members
of
the
eta
are
already
validators
in
the
network,
so
they
are
already
of
the
existing
beta
network
and
they're
in
the
channels
where
we're
talking
about
charlie
testnet,
so
they're
going
to
be
deeply
involved.
A
Any
other
questions
amazing.
Well,
thanks
for
the
engagement
always
happy
to
see
other
faces
and
questions
come
on.
So
if
you
have
more
questions
do
participate.
There's
something
you
want
me
to
talk
about,
do
participate
in
our
telegram.
We
send
a
poll
out
every
week
around
what
topics
you'd
like
to
hear
me
talk
about
or
what
questions
you
have.
So
I'm
most
happy
to
answer
those
either
join
us
here
directly
or
drop
your
questions
and
comments
in
our
telegram
or
discord
channels
cheers
have
a
great
week.
Everyone
bye.