►
From YouTube: CasperLabs Community Call
Description
Mainnet launch status update & Engineering update
A
Good
morning,
good
afternoon,
good
evening,
everyone,
wherever
you're
joining
us
from
my
name,
is
metta
parlikar.
I
am
the
cto
of
casper
labs
and
this
is
the
weekly
community
call
and
development
status
update,
and
I
will
be
reviewing
where
we
are
in
engineering
and
the
community
has
asked
me
to
provide
a
status
update
on
mainnet
launch
so
I'll
be
doing
that
today.
Alex
do
you
have
anything
to
share
today
for
the
agenda.
B
A
Okay,
great,
so
I
will
go
ahead
and
kick
it
off.
So
we
started
our
third
weekly
sprint
of
the
20.11
release
cycle,
and
this
is
for
7.3.
We
did
release
the
october
release,
which
is
going
to
form
the
basis
of
the
delta
test
net
that
is
currently
in
test.
We
are
working
through
some
bugs
and
issues
with
specifically
node
joining
and
rejoining.
If
you
want
to
see
the
work
that's
happening,
you
can
hop
onto
discord
and
in
the
node
rust
channel
you'll,
see,
there's
a
good
amount
of
activity.
A
The
the
beta
test
net
is
stable
and
we
will
be
releasing
a
new
signup
sheet
for
the
delta
test
net
because
we
need
to
do
new
key
generation,
I'm
working
on
getting
the
rust
client
published
to
crates.
So
it's
a
lot
easier
for
folks
to
get
the
rust
client.
You
don't
need
to
build
it
any
of
that
nonsense
right.
So
that's
something
that
we
we've
got
to
work
on
getting
set
up,
so
I
believe
joe
and
the
sre
team
are
looking
into
into
how
to
do
that.
A
A
You
can
bond
into
charlie,
provided
you
can
get
your
node
to
synchronize
and
that's
like
I
said
what
we're
working
on
right
now
is
figuring
out
the
workflow
for
synchronization,
but
I
will
be
releasing
some
documentation
on
how
to
do
bonding
and
unbonding,
because
that
is
part
of
the
delta
test
that
is
permissionlessness.
A
Current
focus
is
we're
working
on
the
adaptive
round,
length
strategy
and
we're
working
on
enhancing
highway
security.
We
are
preparing
for
our
security
audit.
We
have
the
project
kickoff
in
mid-november,
we've
got
some
bugs
to
fix.
Consensus
doesn't
appear
to
recover
after
aliveness
failure.
We
have
economic
incentives
around
aliveness
failure,
but
still
in
the
event
of
a
network
partition,
we
would
expect
that
we
would
want
consensus
to
heal.
So
there's
definitely
some
work
that
we
need
to
do
there
we're
working
on
testing.
A
A
In
testing
sre,
we're
testing
the
delta
release
candidate
and,
like
I
said,
we
found
some
issues
with
joint
node
joining
and
rejoining.
So
if
you
have
a
small
liveness
fault,
are
you
able
to
resync
up
your
protocol
state
and
can
rejoin
consensus
fairly
seamlessly?
These
are
things
that
we're
working
in
the
scala
client,
the
scala
basically
node,
but
are
not
yet
working
in
the
rust
node.
This
is
stuff
we
have
to
work
on.
A
We
want
to
automate
the
release
process
because
we
suspect
that
we're
going
to
have
a
lot
of
rapid
iteration
once
we
get
into
delta
test
net,
so
we
want
to
be
able
to
release
patches
rapidly
and
then
we're
going
to
be
working
on
gathering
metrics.
We've
got
a
new
bunch
of
metrics
that
came
out
as
a
result
of
the
last
release,
and
so
we'll
want
to
start
looking
at
those
metrics
and
create
a
grafana
for
it.
A
On
the
ecosystem
front
in
preparation
for
delta,
we
want
to
have
clarity
set
up,
so
there
is
a
block
explorer
that
people
can
use
the
faucet
and
fund
accounts
and
create
create
accounts,
and
then,
of
course,
some
ux
ui
ux
enhancements
and
changes
as
a
result
of
the
rust
node.
It's
slightly
different,
so
we'll
have
to
do
things
differently.
A
Documentation
updates
I've
personally
been
working
on
the
dap
developer
guide,
to
use
the
rust
client
and
some
of
the
newer
way
to
do
things
right
with
rust,
vis-a-vis
with
scala
and
then
we're
building
an
event
store.
This
is
going
to
make
it
make
it
so
that
nodes
don't
have
to
fulfill
a
heavy
query.
Load
graphql
really
wasn't
stable
for
validator
nodes,
because
it
was
what
we
call
non-deterministic
load
on
a
validating
node.
So
we
are
going
to
offload
those
events
into
an
event
store
separate
from
that.
A
B
Yes,
well,
there's
actually
a
whole
bunch
of
things
like
this
that
we're
doing
right
now,
so
I
mean,
in
fact
the
future
is
probably
better
to
populate
this
field
here
in
these
release
notices
with
epics,
razors
and
particular
stories.
This
is
one
of
the
stories
in
a
large
collection
of
them
that
have
to
do
with
basically
improving
the
initial
implementation
of
options
right
so
well.
B
This
is
one
of
those
improvements
which
will
enable
validator
to
designate
somebody
else
to
actually
sign
basically
delegate
the
power
of
signing
the
consensus
messages
to
somebody
else.
As
operator
there
are
going
to
be
some
tightenings
around
a
slashing
of
delegators
a
couple
of
other
things,
but
you
know
basically
this
and
the
next
vehicle
that
should
be
completed
and
handed
over
to
devs
for
implementation,
and
at
that
point
we
are
more
or
less
feature
complete
for
economics
for
mainnet.
A
Nice
everything's,
coming
together
contract
runtime
updates
to
support
transa
transfer
transaction
proofs,
and
what
this
means
is,
if
I,
if
alice,
sends
bob
money
alice,
will
want
some
proof
of
how
much
she
spent
on
the
transaction
and
how
much
was
actually
sent
to
bob
and
be
able
to
get
that
along
with
a
merkle
proof.
One
of
the
things
that
we're
doing
that's
kind
of
cool
is
for
those
of
you
that
are
not
aware.
A
One
of
the
reasons
why
majority
of
the
networks
out
there
require
you
to
run
a
node
in
order
to
get
data
from
it
is
is
actually
twofold
one.
They
don't
actually
have
a
really
great
data
recovery
data
story.
You
know
like
we
have
the
event
store,
but
the
second
reason
is:
is
you
don't
know
if
you
can
trust
it?
You
don't
know
if
you
request
it
from
a
validator,
if
that's
actually
information
that
can
be
trusted,
and
so
what
we're
building
is.
A
This
transaction
proof
will
actually
provide
you
a
merkle
proof
from
the
global
state,
and
so
you
could
actually
request
this
of
a
couple
of
validators
of
the
network
and
just
get
the
answer
without
having
to
necessarily
just
go.
You
know
basically
run
your
own
node.
We
suspect
that
people
will
still
want
to
run
their
own
node
but
for
different
reasons
like
free
transactions
as
an
example,
and
so
yeah
admiral
proves
to
query
state
responses
right
and
then
we're
also
implementing
storage
costs.
A
So
when
you
send
very
large
wasm,
it's
going
to
cost
a
lot
more,
so
it'll
cost
more
to
install
a
contract
than
it
will
to
call
a
contract
right
simply
because
when
you
invoke
a
contract,
you're
not
storing
anything
in
the
global
state,
your
storage
costs
will
be
limited
to
whatever
the
bandwidth
is
of
that
wasm
right.
A
It
should
be
tiny
to
just
invoke
a
contract
versus
actually
having
to
deploy
and
store
a
contract
for
the
time
being,
storage
will
be
one
time,
but
we
will
be
implementing
garbage
collection
and
rent
either
prior
to
may
nate
main
net
or
very
shortly
after
mainnet.
A
Team
and
company
update,
we
are
searching
for
talented
sres
to
join
our
team
and
we
do
have
new
timings
for
weekly
workshops,
thursday
7
a.m,
pacific
and
friday,
midnight
pacific,
that's
4pm,
japan
time.
The
meeting
information
is
here
and
I
strongly
encourage
folks
to
join
these
calls
because
you
get
hands-on
help
with
learning
how
to
build
smart
contracts
on
casper
from
our
smart
contract
devs,
and
this
is
something
that
we
dedicate
time
and
they're
actually
under
subscribed
right
now.
A
So
it's
a
great
opportunity
to
get
one-on-one
tutorial
and
training
on
how
to
get
started
with
smart
contract
development
on
casper.
So
if
you
want
to
learn
how
to
build
smart
contracts
and
you're,
just
looking
for
some
help
to
dig
in
strongly
recommend
that
you
take
advantage
of
this,
there's
no
cost
to
you
and
we're
more
than
happy
to
be
here
to
help.
A
So
the
community
wanted
to
know
I'm
going
to
dive
in
directly
into
the
request
from
the
community,
which
is
you
know
what
is
the
mainnet
launch
time
frame
looking
like,
and
I'm
going
to
launch
my
telegram
right
now,
and
so
we've
been
talking
about
a
q4
launch
date.
A
We
are
planning
to
be
dev
ready,
we're
going
into
our
security
review
end
of
november,
so
we
plan
on
being
ready
by
december,
but
we
are
working
with
a
custody
provider,
so
there
will
be
some
exciting
announcements
coming
up
next
week
about
our
mainnet
public
sale,
our
recent
private
sale
and
what
the
implications
are
for
mainnet
launch.
So
if
we're
going
to
do
a
mainnet
public
sale,
we
need
to
work
with
a
custody
provider.
A
For
those
of
you
that
are
aware,
you
know
doing
a
private
token
sale
will
involve
a
custody
provider
and
we
have
some
very
exciting
news
that
we
hope
to
share
in
this
arena.
But
the
custody
provider
needs
time
to
be
ready,
and
so,
in
all
probability,
the
custody
provider
has
given
a
tentative
time
of
end
of
january
to
be
production
ready.
So
what
this
means
is,
they
will
start
implementation
very
soon
for
building
out
hardware,
wallets
software
wallets
and
the
entire
end-to-end
custody
solution
and
then
we'll
go
into
production.
A
Testing
in
january
and
main
net
launch
can
happen.
Some
point
after
that,
no
main
net
sale
provider
will
allow
for
a
main
net
sale.
Until
you
have
a
custody
solution
in
place,
that's
production
ready
and
tested.
So
then
chinese
new
year
happens
in
february.
A
So
it's
really
going
to
be
up
to
the
business
to
decide
what
this
all
looks
like
in
terms
of
timeline,
but
no
from
an
engineering
perspective.
We
intend
to
be
ready
by
q4.
That
is
the
goal.
We
expect
that
we'll
be
rapidly
iterating,
even
after
mainnet
launch.
There
will
be
a
lot
of
hard
forks
right,
there'll
be
a
lot
of
updates
because,
as
I've
already
indicated,
we
have
features.
We
know
we
want
to
put
forth
immediately
after
mainnet
launch.
So
we
expect
that
we'll
be
working
with
the
early
validator
set
pretty
closely.
A
It's
most
most
important
that
we
go
out
completely
ready
both
from
a
business
perspective,
as
well
as
a
security
and
protocol
readiness
perspective.
I'm
very
confident
that
we
will
be
well
on
track.
The
charlie
testnet
has
been
performing
extremely
well,
and
the
engineering
team
knows
what
needs
to
be
done
right
like
we
know
what
work
is
remaining
in
terms
of
you
know,
final
touches,
and
I
have
absolute
confidence
in
our
ability
to
get
it
done.
A
Excellent
ashok:
do
you
want
to
talk
a
little
bit
about
like
the
business
readiness
that
we're
doing?
We
have
to
keep
names
out
of
it,
so
we
can't
talk
about
who
we're
working
with
yet
until
it's
all
publicly
released,
but
on.
C
A
Our
perspective,
we
can
talk
a
little
bit
about
what
we're
doing
right.
Pyotr
d
is,
is
busy
at
a
meet
up
that
we're
holding
today
in
zug,
so
he
wasn't
able
to
join
the
call,
but
ashok
has
kind
of
spun
off
from
the
core
engineering
team
to
get
the
business
ready
for
launch
readiness
so
I'll.
Let
him
talk
a
little
bit
about
some
of
the
work
that
he's
engaged
in.
D
Yeah
happy
happy
to
talk
about
it,
so
there
are.
There
are
essentially
two
aspects
to
this:
one
is
working
with
enterprises
and
then
a
second
is
growing
our
developer
community
and
on
both
fronts.
You
know
there
are
really
some
exciting
things
which
are
happening.
We
are
getting
lots
of
interest
from
enterprises
to
come
and
build
on
us,
so
that
pipeline
is
is
really
really
strong.
D
The
idea
is
for
us
to
to
really
scale
this
up
in
a
way
that
we
can
support
the
big
enterprises
that
are
reaching
out
to
us
for
for
building
solutions
and
integrating
with
them.
So
that's
one
aspect
of
it,
and-
and
there
are
there-
are
enterprises
coming
from
all
different
technologies.
So
to
say
right,
there
is
defy
interest
on
casper
networks.
There
is,
there
is
storage
there
are
there?
Are
enterprises
reaching
out
to
us
who
are
from
a
security
and
identity
solutions
perspective
there
are?
D
There
are
other
tokens
who
want
to
integrate
and
have
bridge
develop
with
us,
so
this
is.
This
is
a
really
exciting
time.
Right
now,
on
the
enterprise
side,
on
the
dev
community
side,
we
are
working
with
a
lot
of
country.
Specific
initiatives
trying
to
really
generate
a
lot
of
excitement
and
giving
some
real
exposure
to
the
fantastic
features
that
we
have
on
our
network
to
the
developers.
We
are
planning
over
a
period
of
like
next
next
few
months
before
the
main
net
launch.
D
We
would
be
doing
meetups
we'll
be
doing
something
like
idea,
thoughts
or
hackathons
in
various
countries.
A
No,
I
think
that's
good
right
and
so
so
we're
getting
ready
from
a
perspective
of
building
the
developer
community
pilot
projects
working
to
grow
the
developer
community,
because
now
we
finally
feel,
like
you
know,
with
the
rust
client
and
the
contract
macros
the
contract,
headers
the
app
developer
guide.
These
things
were
working
on
the
developer
journey.
Just
you
know,
really
kind
of
buttoned
up
and
tighten
up
the
developer
journey,
so
developers
can
be
successful
very
quickly.
A
So
it's
really
about
kind
of
stitching
together
a
lot
of
the
building
blocks
into
a
clean
user
experience,
and
then
our
intention
is
to
go
big
with
developers
right
here
shortly
to
get
people
excited
about
building
on
casper.
That's
the
that's
the
first
piece.
The
second
piece
is
from
a
compliance
regulatory
perspective,
we're
also
getting
ready.
You
know
for
the
sec
right,
so
we
have
new
regulatory
requirements
for
those
of
you
that
have
been
involved
in
these
community
calls
in
the
beginning.
A
You
know
that
very
consistently
from
day
one
our
focus
has
been
on
the
regulatory
framework
for
the
project,
and
so
we
continue
to
invest
time,
energy
and
a
lot
of
money
with
lawyers
and
and
doing
research
regarding
what
the
regulatory
framework
looks
like
for
us
to
to
do
this
and
be
as
inclusive
as
possible
for
as
many
people
as
possible,
it
hasn't
been
easy
and
we've
even
taken
some
risk
on.
A
You
know
to
do
these
things
and
some
of
some
folks
get
very
frustrated,
because
we
can't
give
them
the
kinds
of
answers
that
they
want
in
our
public
channels,
but
there's
a
reason
for
that
is.
We
need
to
adhere
very
tightly
to
what
the
sec
lays
out
for
us
right,
and
so
we
consider
this
to
be
extremely
important
for
all
parties
concerned.
A
A
So
the
code
is,
we've
been
working
on
the
code
for
a
long
period
of
time
been
working
on
the
product
for
a
long
time,
and
now
we
need
to
get
basically
the
other
pieces,
the
other
two
parts
of
the
stool
that
the
two
legs
of
the
stool
ready
to
go.
So
we
can
have
a
solid
launch.
D
Also
also
cleaning
up
our
documentation
because
the
pace
of
development
has
been
frantic.
We
want
to
make
sure
that
the
documentation
kind
of
catches
up-
and
you
know
it's
ready
for
the
developer
community.
A
Yep,
that's
exactly
right!
So
there's
a
lot,
there's
a
lot
of
documentation
to
be
done
and
actually,
like,
I'm
doing
a
bunch
of
it.
So
I
I'm
doing
a
bunch
of
the
adapt
developer
guide
documentation
because
I'm
one
of
those
people
that
wants
to
know
one
of
those
product
owners
that
wants
to
know
hands
on
how
the
thing
works
and
see
if
it
meets
my
expectations.
A
So
I
do
a
lot
of
the
uat
myself
around
the
system
and
I've
been
spending
a
lot
of
time
working
on
bonding
and
unbonding
over
the
past
few
weeks.
I'm
not
past
few
past
few
days
so
late
last
week
and
earlier
this
week
we
received
the
capability
to
do
bonding
and
unbonding,
and
so
I've
been
writing
up
a
lot
of
documentation
how
that
works
and
now
we're
working
with
joint
syncing
and
non-syncing
so
syncing,
which
is
not
actually
working
the
way
we
want
right
now.
A
A
Our
goal
is
that
our
community
feels
has
confidence
and
feels
comfortable
with
our
progress
and
is
informed
very
transparently
on
where
we
stand
right
so
by
in
all
means,
if
you
have
questions,
don't
hesitate
to
reach
out
all
right
folks,
that's
all.
I
have
alex
anything
to
share
you're
going
to
talk
more
next
week
right.