►
From YouTube: CasperLabs Community Call
Description
Engineering update, Delgator UX, How Casper is different from Ethereum, why CasperLabs is launching a separate blockchain
B
A
A
So,
as
you
all
are,
may
or
may
not
be
aware,
the
team
executes
in
four
week
cycles
each
four
week
cycle
is
comprised
of
four
sprints
and
it
terminates
with
a
release
and
a
planning
virtual
planning
offsite
about
four
hours.
We
had
our
virtual
planning
outside
on
friday
and
we
completed
the
work
for
this
release
cycle,
which
is
the
august
release.
We
will
be
cutting
our
release
here
very
shortly
now.
A
This
release
is
primarily
focused
on
the
rust
client,
so
you
will
not
see
a
public
release
of
this
client
is
much
much
more,
an
internal
milestone
that
we
are
we
are
cutting
here.
However,
we
are
actually
physically
cutting
bits,
we're
cutting
bits
and
we're
deploying
those
bits
into
long-running
test
beds
that
we
that
we
run
in
aws
and
performing
a
series
of
tests
of
load
testing
which
is
sre
is
is
working
on.
It
is
our
intention
to
open
source
the
rust
this
this
repo,
it's
in
a
different
repo.
A
It's
closed
right
now
only
because
we
didn't
want
to
create
confusion
in
the
community
while
we
were
building
it
up,
but
now
that
the
scala
repo
is
is
more
or
less
under
maintenance
mode
and
all
the
work
is
happening.
The
rust
repo
we're
going
to
be
opening
that
up,
probably
this
week
in
alignment
with
the
august
release.
So
look
for
that,
I'm
going
to
be
doing
mad
amounts
of
documentation,
making
sure
that
the
repo
is
nice
and
clean
with
all
the
readmes
that
you
see
here
so
we'll
be
moving.
A
All
of
that
over
we're
going
to
figure
out
how
we're
going
to
move
everything
over.
So
that's
there's
a
little
bit
of
an
internal
discussion
around
that,
but
that
expect
that
to
happen
this
week,
so
what's
planned
for
the
september
release,
so
the
next
iteration.
A
So
during
the
august
release-
and
you
can
see
the
releases
within
our
confluence-
those
of
you
that
are
attending
weekly
workshops-
you'll
see
that
the
release
plans
are
there
I'll
drop
the
august
release
plan
here.
Yes,
we
do
use
atlassian
toolset,
so
the
august
release
here
talks
really
about
a
functional
rust
implementation
that
can
stand
up.
You
know
a
20
node
network
for
about
seven
days.
Nodes
can
join
the
network
in
sync
with
the
rest
of
the
state
transitions.
A
We
have
the
chain
specification
done,
and
then
we
include
some
validator
set
rotation
and
then
the
consensus,
implementation
and
an
evolving
rust
client.
We
also
have
to
update
our
testing
framework
to
work
with
the
new
rust
node,
and
here
you
can
see
some
of
the
work.
That's
you
know
implementing
it
in
review.
Most
of
this
is
done,
we're
just
in
the
final
stages
of
completing
it.
A
A
So
you
can
now
see
that,
as
a
separate
repository,
we
had
to
extricate
that
from
the
core
code
base
that
took
a
little
bit
of
work
and
then,
of
course,
we're
building
some
clarity
metrics
here,
so
we
can
get
some
insights
into
how
folks
are
using
it,
and
we've
got
git
pod
integration
done
and
that's
going
to
be
integrated
into
our
tutorial.
So
we've
got
a
lot
of
work,
a
lot
of
work
here,
you
can
see
being
done
on
the
ecosystem
front,
so
this
is
how
we
manage
our
our
releases.
A
A
A
Each
epic
contains
a
bunch
of
stories
within
them
which
we
we
still
have
to
cut
those
stories
and
put
them
into
their
release
plan,
but
you'll
see
them
popping
up
here
right.
There's
a
good
chunk
of
design
work
ashok
alludes
to
that
in
the
status
update.
There's
a
lot
of
design
work
that
we're
doing
social
consensus
is
what
happens
in
the
event
of
a
complete
catastrophe,
an
equivocation
catastrophe
or
what
you
see
in
proof
of
work.
A
What
we
call
a
deep
chain,
reorganization
right,
so
the
validators
all
get
together
and
figure
out
that
there's
an
attack
happening
on
the
network
and
they
kick
out
the
malicious
attacker
or
undo
what
that
attacker
attempts
to
do.
That's
what
social
consensus
is
referred
to
as
design
specification,
auto
price
adjustment.
This
is
the
work
that
owner
has
done.
He's
actually
proposed.
This
submitted
this
to
even
ethereum
research
and
they'll,
be
going
up
on
our
new
blog
that
we're
building
validator
onboarding
after
genesis.
A
I
talked
about
this
preparation,
the
rest
network
to
launch
with
20
validators,
and
then
this
is
off
chain
execution
use
cases.
This
is
event
streaming.
A
This
is
really
like
functions
that
don't
necessarily
mutate
the
global
state
but
provide
allow
you
to
do
certain
things
like
return
values,
and
then
we've
got
to
do
storage
and
bandwidth
pricing
and
then
benchmarking
out
again,
I
wanna
this
is
about
token
transfers
per
second
and
then
we're
also
gonna
look
at
design
of
checkpoints
and
we
can
talk
a
little
bit
about
what
checkpointing
is
later
on
in
in
the
call.
If
we
wanna
know
about
what
that
is.
A
So
that's
the
release
plan
for
20
20.09
september
and
we
launched
our
beta
test
net
on
the
3rd
of
august.
Testnet
is
stable.
We're
probably
going
to
do
another
bounce
here,
because
we
want
to
bring
in
some
more
validators
and
we
ran
into
a
problem
with
clarity
when
ashok
joins
I'll,
probably
put
them
on
a
spot
and
see
where
we
are
with
that
fix.
There
was
a
challenge
with
with
account
hashes
versus
pro
public
keys
right.
A
The
proof
of
stake
contract
only
understands
public
keys,
but
with
this
implementation
of
multi-key
support,
we
have
an
internal
representation
in
the
system,
which
is
an
account
hash
and
we
expose
that
in
a
manner
to
validators.
That
was
confusing.
So
we
got
a
lot
of
account
hashes
in
the
sign
up,
but
account
hashes
don't
work,
and
so
we
have
to
fix
the
onboarding
process
and
the
user
experience
so
that
validators
can
use
the
public
key
correctly,
so
they
can
bond
in.
So
that's
what
we're
going
to
fix.
A
20
can
be
indicated
here:
20
node,
rest,
20,
node,
rest
network
and
lrts
we're
also
building
a
complete
integration
test
framework
for
highway
core
that
enables
engineers
to
very
quickly
add
new
tests.
This
is
for
the
correctness
test
of
highway
to
make
sure
it's
implemented
as
specified
in
the
paper.
A
We're
doing
a
gap.
Analysis,
the
russ,
client
vis-a-vis,
the
python
client
make
sure
we
want
to
have.
We
want
to
offer
all
the
same
functions
and
recognizing
that
some
of
the
functions
are
still
not
implemented
in
the
rust
node.
So
some
of
the
things
may
not
work
or
they
may
not
work
exactly
the
same
we
want
to.
A
A
A
So
we
talked
a
little
bit
about
the
permissionless
validator
onboarding.
We
also
talked
about
extending
solidity
transpiler
to
support
bitwise
operators.
I
was
doing
an
update
here
and
we're
also
going
to
generize
the
voting
dap
that
we
created
to
support
hackathons,
that
we
want
to
do
on
our
own
network
and
enable
other
people
to
use
the
voting
dapp
as
an
open
source
piece
of
software.
Pardon
my
doggy
there
that
is
playing
with
his
toy
you'll,
probably
hear
him
squeaking.
In
the
background.
A
Contract
runtime
is
mostly
feature
complete.
We
are
doing
a
little
bit
of
analysis
on
returning
return.
Values
system
doesn't
return
values
right
now
and
we
we
recognize
that
this
is
a
miss
and
we
want
to
implement
that
and
that's
it.
That's
my
update
on
the
core
technical
front
team
is
really
working
hard
story
point
achievement
has
been
just
phenomenal
and
for
those
of
you
that
aren't
aware,
we
are
hiring
we're
hiring
a
full
stack
developer,
we're
hiring
core
rust
engineers
and
we're
hiring
sre
and
we're
also
hiring
a
tech
writer.
A
So
if
you
know
people,
if
you
know
a
tech
writer
that
has
some
blockchain
experience,
please
have
them
reach
out
to
us.
They
can
apply
via
workable
there's
a
link
I
shared,
we've
shared
it
in
our
telegram
channel.
We
shared
it
in
discord,
it's
also
on
our
website
at
casperlabs.io.
So
if
you're
interested
in
working
with
the
project
drop
your
resume
there
and
we'll
get
in
touch
with
you,
because
we
are
hiring
all
right,
so
a
question
from
the
community
was
around:
how
are
we
different
than
ethereum?
A
You
know?
What's
the
difference
between
what
casper
labs
is?
What
ethereum
is
right,
and
so
I'm
going
to
start
with
I'll
start
with
our
similarities,
so
how
about
we
start
with
that?
Let's,
let's
find,
let's
talk
about
how
we're
similar
to
ethereum
before
we
start
talking
about
how
we're
different
from
ethereum.
A
So
casper
labs
is
a
lot
like
ethereum
in
many
ways
right
one
we
are,
we
are
taking
the
lessons
learned
from
ethereum
and
we
are
you
know,
and
some
of
the
ethereum
research
and
we're
implementing
that
research
right.
So
that's
one
way
in
which
you're
similar
with
ethereum
we're
also
a
touring
complete
smart
contracting
platform.
A
We
also
are
striving
to
build
a
very
secure,
permissionless,
fault-tolerant
and
decentralized
consensus
protocol
and
that's
a
way
in
which
we're
similar
with
theorem
ethereum
uses
proof
of
work
we're
also
similar
in
ethereum.
In
that
you
know,
we
want
to
support
open
source
initiatives.
We
want
to
support,
you
know
decentralized
governance
models.
We
want
to
support.
A
You
know
web
3
development
application
to
centralize
application
development.
We
want
to
support
all
those
things.
So
in
those
ways
I
think
we're
very
similar
to
ethereum.
I'm
you
know
I'm
a
libertarian
at
heart.
You
know
we
kind
of
embody
the
decentralized
steampunk
movement
in
that
we
believe
that
the
security
of
blockchain
comes
through
individuals
participating
and
you
know
in
the
blockchain
should
be
owned
by
by
the
people.
Not
by
a
company
right
so
and
not
by
a
centralized
cabal,
so
we
we
align
our
ethos,
I
believe
pretty
similar
to
ethereum
in
that
regard.
A
I
think
that,
oh
you
know,
software
needs
certain
things
in
order
to
grow
and
evolve,
and
we've
built
those
tools
here
that
enable
you
know
an
enterprising
developer
to
hopefully
ultimately
someday
build
a
rich
and
flourishing
business
on
the
casper
blockchain,
and
in
order
to
do
that,
you
need
you
need
a
system
that
supports
open
source
principles.
It
supports
entrepreneurial
efforts,
but
it
also
supports
features
and
use
cases
that
at
some
point,
if
your
business
really
becomes
successful,
that
you'll
need
to
support
right,
sometimes
being
successful,
can
be
your
own
worst
enemy
right.
A
You
set
out
to
build
something:
that's
really
really
amazing
and
it
grows
wildly
and
suddenly
now
you
need
to
do
things
to
support
your
customers
or
to
monetize
your
business
that
you
didn't
think
you
needed
to
do
early
on.
This
is
very,
very
common.
You
know
business
models
evolve
and
grow
through
pivots
right
and
you
need
a
platform.
That's
going
to
support
that
and
that's
what
we've
built
right.
We've
built
a
platform
that
supports
the
kinds
of
pivots
that
we
think
are
essential
to
build
a
real
business
using
blockchain
technology.
A
We
also
believe
that
blockchain
technology's,
most
important
thing
is
its
security,
and
you
really
can't
have
a
super
secure
system
without
making
sure
that
it
checks
for
faults
that
all
the
stake,
that's
in
the
network,
is
applied
to
single
transaction.
So
that
means
it's
not
probabilistic
right.
It
doesn't
use
statistical
sample,
sampling
or
probabilistic
methods
to
secure
transactions,
but
really,
you
know
a
very
large
chunk
of
the
stake.
If
not
all
the
stake
votes
on
your
transaction
right,
it
it
uses
it
checks
for
faults.
It's
permissionless.
A
It
provides
open
access
for
as
many
validators
to
participate
as
possible.
It
provides
a
reliable
and
consistent
user
experience
for
its
end
users,
as
well
as
the
staff
developers
right,
and
it
gives
you
the
flexibility
to
evolve
your
application
over
time.
So
we
we
set
out
to
build
the
smart
contracting
runtime
purposefully
with
these
features
right.
I
think
that
the
evm
was
a
great
initial
proof
of
concept.
A
I
think
it
has
enabled
a
lot
of
amazing
things
to
happen
in
ethereum,
and
I
sincerely
hope
that
ethereum
is
able
to
eventually
upgrade
the
ethereum
protocol
to
use
ewasm.
I
also
think
that
you
know
casper
labs
will
enable
we
can
take
the
risk
to
do
experimentation
right.
Our
investors
are
taking
a
pretty
big
gamble
on
the
casper
protocol.
A
We
took
a
pretty
big
gamble
on
the
caster
protocol
because
when
we
set
out
to
build
casper
labs,
casper
protocol
was
not
complete,
it
was
not
provably
live
it's
one
of
the
reasons
why
you
don't
see
a
live
implementation
of
cb
cast
cbc
casper,
yet
you
see
snippets
of
the
fork
choice
rule
in
protocols.
There
are
protocols
out
there
that
have
implemented
four
choice
or
dag
based
fork,
choice
protocols,
but
you'll
notice
that
many
of
them
are
not
permissionless
and
the
permissionless
part
of
dag
based
fork
choice.
A
Protocols
is
really
really
non-trivial
and
it
it
is
actually
prudent
and
behooves
ethereum
vitalik
and
the
core
ethereum
devs
to
proceed
with
extreme
caution
because
of
the
amount
of
value
that's
locked
in
ethereum
right,
arguably,
casper
labs.
Current
market
cap
is
pretty
low
right,
and
so
it's
going
to
be
risky.
When
we
launch
this
protocol,
I'm
not
going
to
say
that
it's
not
a
bold
move
and
not
a
gamble
and
we
won't
be
attacked.
We've
done
our
very
best
to
try
to
have
the
protocol
be
provably,
live
and
safe.
A
We've
done
a
lot
of
work.
We
spend
a
lot
of
time
thinking
about
how
the
protocol
can
be
attacked,
we're
designing
social
consensus
to
give
the
validators
the
tool
to
recover
the
network.
If
it
ever,
god
forbid,
is
attacked.
A
Having
a
permissionless,
you
know
open
fork,
choice,
dag-based
protocol
is
not
is
not
a
small
matter,
and
so
how
are
we
different?
How
do
you
know
this
thing's?
A
You
know
it
would
be
a
very,
very
long
test
net,
a
multi-year
test
net,
but
even
with
a
multi-year
test
net,
you
don't
necessarily
have
the
incentive
for
attackers
to
attack
it
right,
so
people
that
have
invested
in
casper
labs
and
that's
includes
token
holders
people
myself,
you
know
I'm
staking
my
reputation
right,
my
career
on
the
cbc
casper
protocol
on
the
highway
protocol
and
we're
doing
it.
So
we
can
prove
out
whether
this
thing
is
actually
secure.
A
It's
it's
not
a
small
thing,
and
so
that's
why
it
has
to
be
a
separate
blockchain.
It's
not
a
money
grab,
it's
not
about
us
trying
to
make
a
quick
buck
because,
god,
you
know,
god
is
my
witness.
I've
been
working
on
the
cbc
castle
protocol
for
over
three
years,
and
this
would
mark
you
know
october
of
this
year-
would
mark
three
years
total
my
investment
in
cbc
casper,
and
so
it's
definitely
not
a
fast
money
grab.
A
It's
definitely
risky
and
it
certainly
has
been
a
hell
of
a
lot
of
work
trying
to
secure
this
thing,
and
you
know,
provide
the
economic
security
and
the
the
provable
security
for
the
cbc
casper
protocol.
A
So
I'm
going
to
pause
there
because
I've
been
doing
a
lot
of
talking
and
I
want
to
let
owner
talk
a
little
bit
about
delegation,
because
you
know
for
those
of
you
that
aren't
aware.
Cbc
casper
has
a
lot
of
game
theory
and
economic
security
as
a
means
to
unlock
some
of
the
performance
that
we
can
get
out
of
proof
of
stake
by
making
sure
that
the
incentives
and
disincentives
tightly
align
so
that
the
validators
are
highly
incentive
to
do
the
right
thing
right.
So
we
don't
have
to
slow
everything
down.
A
You
know
in
the
and
have
a
tight,
synchrony
constraint,
and
so,
if
there's
questions
about
this
bring
it,
you
know
about
what
I've
said
hit
me
up,
discord
telegram
even
twitter,
and
you
know
you
can
also
bring
the
questions
here
next
week
owner
over
to
you.
B
B
So
I
I
want
to
talk
about
this
week
to
delegate
delegated
user
experience
because
I've
been
implementing
it,
the
interface
and
the
yeah,
the
reward
distribution
to
delegators.
So
it's
a
good
time
for
me
to
talk
about
it.
B
Basically,
what
is
delegation
so
in
all
of
these
blockchains
you
have
issuance
right,
you
inflate
the
supply.
Basically
you
you
meant
new
tokens
in
order
to
incentivize
violators
to
you
know,
operate
their
machines,
that's
how
the
that's
that's
in
in!
In
the
majority
of
the
blockchains,
I
would
say
in
all
of
them
the
majority
of
the
minor
or
validator
revenue
comes
from
this
issuance
and
so
delegation
has
to
do
with
users.
B
So
what?
Let's?
Let's
say,
I'm
a
user.
I
just
obtained
like
new
casper
labs
tokens.
I
want
to
say
clx,
but
I
I
saw
mirnal
said
we
will
be
using
a
different
ticker
symbol
for
that,
so
I'll
just
refer
it
as
the
castle
labs
token.
B
The
first
thing
I
want
to
do
with
my
token
is
make
sure
its
value
doesn't
depreciate,
so
there
is
issuance
overall,
it
will
be.
We
are
expecting
it
to
be
around
two
three
percent
annual,
but
of
course
we
have
a
also
release
period
for
the
casper
labs
token
supply.
B
B
It
will
be
even
lower
than
provost
state
launches,
but
if
you're
yeah
you
you'll
want
to
want
it
to
be
high
when
you're
launching-
and
that
means
your
tokens
won
you
from
now,
if
you're
not
a
validator,
they
will
be,
they
will
well
their
your
market
share
will
decrease
because
validators
will
be
richer.
So
one
the
first
thing
that
comes
to
mind,
because
when
the
project
first
launches,
you
don't
have
a
lot
of
projects.
B
The
first
thing
you
can
do
is
to
delegate
your
tokens
to
a
validator,
and
that
means
a
validator
can
accept
tokens
from
users.
Stakes
take
them
on
their
behalf
and
then
then
do
some
internal
accounting
with
the
rewards
that
you
receive
so
for
evaluator.
My
rewards
are
directly
proportional
to
the
amount
I
stake.
That
means,
if
I
stay
hundred
tokens
I
get
x
rewards.
B
If,
with
delegations
I
have
200
tokens,
the
rewards
I'll
get
will
be
2x
right
and
this
extra
1x
comps
is
is
owing
to
the
delegators
that
have
like
trust,
trusted
me
with
their
tokens.
B
So
this
is
the
this
is
this
business
is
called
delegation
and
it's
not
it's
not
doesn't
directly
have
to
do
with
delegated
proof
of
stake.
So
we
had.
I
think
eos
was
depos,
so
we
don't
have
it's
like
token.
Holders
are
not
voting
with
their
tokens.
B
It's
the
word
delegation
stuck
in
in
the
industry
and
all
of
the
like,
except
polkadot,
which
uses
the
word
nominated
because
they
have
a
slightly
different
mechanism.
B
So
how
is
the
delegation
delegated
user
experience
going
to
be
in
casper
labs?
First
of
all,
we
don't
want
exchanges
delegating
on
behalf
of
users,
because
exchanges
have
a
tendency
to
you
know
they
are
for
profit
entities
and
you
you
can
never
trust
them
with
you
know
having
a
one-to-one,
you
know
collateral
or
stake
like
they.
They
are
you.
Can
you
can
trust
them
to
state
all
tokens
that
they
receive
from
the
users?
They
will
probably
do
some
other
businesses
with
with
the
value
they
get
run
a
fractional
reserve.
B
B
Have
this
feature
in
the
protocol
itself,
and
that's
that's
why
we
we
support
this
on
chain
delegation,
and
so
how
does
it
work?
I
have
I
I
go
to
like
an
exchange.
I
get
my
tokens
by
the
first.
Like
I
get
my
tokens
by
summiting
fiat
right.
I
got
my
casper
labs
tokens
and
I
go
through
probably
clarity.
Right
yeah,
we
haven't
prepared
the
delegator
interface
like
user
interface,
yet
you
go
to
clarity.
B
Casper
labs
is
blockchain
explorer,
which,
which
offers
a
lot
of
features
for
violators
and
delegators,
and
looking
up
data
and
so
on,
and
what
you
do.
Is
you
connect
with
your
wallet?
You
choose
you,
you
have
a
list
of
validators,
you
just
choose
an
amount
that
you
want
to
delegate
and
then
choose
which
validator
you
want
to
delegate
to.
B
One
factor
you
are
you
that
affects
your
choice.
Is
the
delegation
rate
of
the
validator
right?
Sorry,
not
delegation
rate
commission
rate,
so
there
was
a
confusion
in
our
respects
and
I
meant
to
say:
commission
rate
commission
rate
is
how
much
a
validator
is.
A
Yeah,
I
think
that's
key
right
so
like
I,
we
would
want
that
the
validators
I'm
not
sure
what
the
interface
would
look
like
for
validators,
and
I
certainly
wouldn't
want
to
be
the
one
building
this
right,
but
in
theory
validators,
would
actually
create
some
kind
of
a
site
or
a
page.
That
would
indicate
here's
where
you
can
delegate
your
tokens
right
and
it
would
be
a
business
for
them
and
it's
it
becomes
an
interesting.
B
A
While
while
token
holders
don't
necess
explicitly
vote
for
a
validator
because
we're
going
to
support
a
bonding
queue
where
the
top
n
get
in
right,
the
top
the
the
top
n
number
of
validators
with
the
greatest
stake
are
the
ones
that
will
get
in
into
the
next
round
up
for
validation.
It's
an
interesting
and
there's
actually
an
economic
incentive
right
for
for
token
holders
to
watch
which
validators
they
are
delegating
their
tokens
with
ice.
My
concern
is,
I
mean
one
of
the
things
I
I
always
I'm
concerned
about.
Is
centralization
right?
A
Like
will
people
just
say?
Well,
I
don't
want
to
go
with
a
smaller
validator
because
they
may
turn
out,
and
so
I'm
just
going
to
go
with
the
big
guy,
because
I
know
he's
always
going
to
be
in
right,
and
so
that's
that's
something.
That's
a
little
bit
concerning
to
me.
How
does
you
know?
I
want
to
make
sure
that,
and
I
suppose
it
would
come
down
to
the
fact
that
there
will
be
an
equilibrium
where
the
smaller
guys
could
offer
much
much
more
lucrative
returns
right.
C
Yeah,
basically,
you
know
the
risk
is
a
risky
investment
that
there
you
know
the
smaller
validators
they
offer
higher
returns.
B
This
is
a
this
is
a
such
a
market
and
well
regarding
centralization.
I
think
it's
a
spectrum,
so
the
spec
on
one
end
of
the
spectrum.
You
have
a
monopoly
right,
just
one
value
and
they
can
do
whatever
they
want.
As
you
go
to
the
other
side
of
the
spectrum,
you
have
a
cartel.
B
Now
you
have
like
maybe
three
two
three
validators
four
validators,
and
then
they
are
basically
trying
to
censor
each
other
completely
like
there
is
a
byzantine
behavior
going
on
and
as
you
go
to
the
other
end,
you
have
a
cartel,
but
they
are
just
deterred
from
attacking
each
other.
They
are
just
they,
they
reach
a
certain
size
and
they
are-
and
basically
you
know
it's
it's
like
the
it's
like
one
of
the
duopolies
or
like
oligopolies.
B
You
you
see
in
a
economic
theory
and
on
on
the
furthest
end
of
the
spectrum
you
have
like
10,
000
validators,
which
ethereum
2.0
I
mean
you
have
seen
we
have.
I
have
I
have
read
before
that
vitalik
was
would
expect,
like
thousands,
even
tens
of
thousands
of
validators,
which
I
think
is
very
unpractical,
and
you
have
a
this-
is
a
in
proof
of
stake.
You
have
this
message:
communication
complexity.
B
There
is
a
sweet
spot.
What
the
conclusion
I
coming
at
is:
there's
a
sweet
spot
on
the
spectrum,
which
is
makes
it
both
practical
for
this
blockchain
to
operate.
But
it's
it's.
You
know
just
decentralized
enough,
so
that
it's
it's
still.
You
know
you
can
take
it
down.
B
Just
like
proof
of
work.
No,
it
offers
the
same
security
guarantees
as
proof
of
work.
I
I
think
what
most
people
would
call
centralization
is
like
an
oligopoly
of
four
or
five
validators.
Is
the
steady
state
like
eventually
what
all
of
the
proof
of
stake
protocols
would?
B
You
know
converge
to
eventually
what
I'm
saying
is
these
these
protocols
would
see
as
a
coagulation
of
stake
and
decentralization
would
happen
through
the
delegation
delegations
that
users
are
delegating.
So
all
of
these,
like
the
ideal
status
majority
of
the
tokens,
come
from
users,
so
they
can
withdraw
it
at
from
from
validators
anytime
and
that
that's
that's
like
a
deterrence
for
from
for
the
validators,
from
acting
badly
showing
bad
behavior.
B
A
I
mean
a
hundred
percent
right,
like
I
think,
one
of
the
things
that
we've
I've
learned
in
working
with
this
protocol
for
as
long
as
I've
been
working
with
it
in
the
weeds
on
the
economics-
and
you
know
just
the
security
of
it-
is
that
it's
it's
a
there's
quite
a
bit
of
entanglement
and
game
theory
and
we're
just
really
not
going
to
know
we're
just
not
going
to
know
how
this
all
going
to
shake
out
until
we
actually
put
some
value
against
it
and
see
how
the
incentive
and
disincentive
mechanisms
work.
A
We
would
like
this
idea
of
a
progressive,
slash
right,
but
we're
starting
off
with
100
slash
right
now
in
test
net,
and
because
we
haven't
figured
out,
we
have
to
figure
out
like
how
many
equivocations
actually
can
cause
harm
to
the
network,
and
if
we,
if
we
reduce
the
percentage
of
the
slash,
we
effectively
reduce
the
security
for
each
block
to
whatever
that
percentage
is
right
and
so
yeah.
But
it
could
also
be
that
we
increase
the
slashing
rate,
as
the
network
gets
older
right.
A
So
the
higher
the
block
height,
the
higher
the
slash
amount
until
it
eventually
caps
out
at
100
or
something
like
that.
But
so
I'm
going
to
go,
get
a
question.
So
wolfe
had
a
great
question
here.
So
wolf
and
marco
are
on
the
line
they're
both
participating
in
the
devdao.
We
haven't
broadly
announced
the
dev
dab,
but
the
devdow
is
doing
a
lot
of
great
work
in
terms
of
its
own
formation,
and
so
I'm
gonna,
I'm
not
gonna
talk
too
much
about
the
devdow
itself.
A
I'll
leave
those
announcements
to
them
for
them
to
announce
their
hard
work,
but
the
devdao
briefly
is
a
separate
entity.
It's
a
separate,
not-for-profit
entity
that
really
is
an
organization
for
developers,
and
you
know
the
dev
dow
really
aligns
beautifully
with
the
casper
lab's
mission,
which
is
to
scale
opportunity
for
everyone.
A
Our
mission
is
to
use
distributed,
ledger
technology,
public
permissionless,
blockchain
technology
to
disintermediate
processes
and
to
provide
more
autonomy
and
opportunity
for
the
individual.
That's
that's
our
mission
statement.
A
That's
our
goal
and
the
dev
dao
aligns
beautifully
with
this,
because
it's
almost
like
a
developer's
quote-unquote
union
right
for
developers
by
developers
for
the
betterment
of
developers,
and
so,
if
you
think
of
a
lot
of
blockchain
projects-
and
this
is
something
that
eos
did-
this
is
something
that
a
lot
of
the
other
blockchain
protocols
out
there
have
done
is
they've
put
aside
a
bunch
of
token
for
developer
incentives
and
those
developer
incentives,
and
that
token
was
centrally
managed
by
the
company
building
the
blockchain.
But
we're
not
going
to
do
that.
A
We're
actually
going
to
put
our
money
where
our
mouth
is
and
we're
going
to
carve
off
a
massive
token
allocation
and
those
incentives
are
going
to
go
to
the
devdao.
And
we
will
have
no
say
in
how
those
tokens
are
allocated.
A
We
hope
and
believe
that
we've
built
the
best
product
and
the
devdao
will
will
be
able
to
make
a
lot
of
developers
successful
and
build
successful
businesses
using
the
casper
technology,
but
they
don't
have
to
they're,
not
bound
strictly
bound
to
do
that,
and
we
believe
that
this
dev
down
will
ultimately
be
the
incubator
for
the
ecosystem.
A
Yes,
marco,
this
is
this
is
live.
It's
live
it's
on
youtube.
I
hope
I
don't
get
in
trouble,
but
maybe
I
might
get
in
trouble,
so
we
it
is
our
intention
to
do
this,
and
and-
and
so
I've
said-
a
lot
of
things
that
maybe
get
me
trouble.
Hopefully
I
won't
get
in
trouble
for
this,
but
at
any
rate,
so
what
we
want.
A
We
want
the
dev
dao
to
actually
take
a
central
spot
in
a
central
spot
in
in
launching
the
test
net
and
and
what
we,
what
you
know,
the
delta
test
nate
right.
So
we
have
some
ideas
about
how
we
want
the
delta
test
net
to
evolve.
A
We
want
the
delta
test
net
to
be
as
decentralized
as
possible
to
enable
open,
bonding
and
unbonding,
and
we
would
like
very
much
for
the
dev
dow
to
take
a
much
bigger
role
in
helping
us
launch
the
delta
test
net.
Helping
us
launch
the
mainnet,
so
casper
labs
is
not
an
active
participant
in,
but
rather
a
single
participant
in
the
launching
of
the
network.
I
have
big
bold
ideas
about
the
network
being
permissionless
more
or
less
on
day,
one.
A
The
initial
founding
validators,
because
they
are
their
their
tokens,
will
have
to
be
locked
for
90
days,
will
likely
have
a
grandfathered
spot
in
into
the
bonding
auctions
for
a
minimum
of
90
days,
because
their
tokens
have
to
be
locked,
and
so
we'll
have
to
do
some
figuring
out
of
what
the
initial
slot
size
is
going
to
be
and
how
it's
going
to
decentralize
from
there.
A
Our
node
will
just
be
a
participant
right.
We
will
provide
a
bootstrap
node,
but
the
approval
of
the
genesis
block
the
validators.
Accepting
the
genesis
block
accepting
the
code
setting
up
the
manifest
tomml
in
terms
of
when
the
network
is
going
to
launch
is
going
to
be
collaborative,
but
it
will
not
be
defined
by
casper
labs.
A
That
is
the
spirit
and
idea
because
we
want
to.
We
really
want
to
build
a
decentralized
blockchain.
So
that's
my
answer.
Wolf,
that's!
My
idea
is
that
the
you
know
the
founding
validators,
which
will
be
some.
Obviously,
a
lot
of
them
will
be
the
delta
test
net
and
the
test
net
participants,
as
well
as
the
infrastructure
providers.
The
staking
pools
staking
service
and
exchanges
that
are
going
to
launch
with
us.
They
will
all
participate.
We
believe
in
launching
the
network
in
in
very
decentralized
decentralized
manner.
A
D
Yeah,
hey,
thank
you
mata.
This
is
excellent
news.
I
I'm
we're
all
super
excited
about
this.
Do
you,
and
obviously
we
we
have
to
internally
manage
manage
some
of
this
at
the
dev
down,
so
we're
trying
to
sort
of
grapple
with
the
amount
of
woman,
slash
man,
man
hours,
we
might
be
required
in
trying
to
successfully
help
launch
and
build
out
the
test
net.
Do
you
have
any
idea
what
what
it
could
take
to
give
us
sort
of
ballparks
for
our
internal
discussions.
A
So,
in
terms
of
the
coordination
I
my
intent
is
that
the
the
the
genesis
block
and
the
pre-mine
will
all
be
put
into
github
and
approved
by
github.
I
believe
what
we
would
want
to
do
is
we
want
to,
for
avoidance
of
doubt,
because
it
is
open
source
software.
We
wouldn't
want
somebody
to
launch
the
network
out
from
under
us
for
lack
of
a
better
term
so
likely
the
the
the
the
authoritative
genesis
block
should
probably
be
you
know,
announced
in
a
more
I
don't
know.
I
won't
use
a
word.
A
That's
not
that's
not
very
pretty
here,
but
a
more
private
manner
amongst
the
devdao,
and
that
coordination
should
probably
happen
a
little
bit
behind
closed
doors.
So
nobody
comes
in
under
us
and
launches
the
genesis
block
out
from
under
us.
If
that
makes
any
sense,
the
authoritative
network
would
have
the
authoritative
genesis
hash
right.
A
Yeah
absolutely
but
the
the
the
genesis
process
and
the
chain
specification
is
quite
decentralized
right.
Validators
get
the
genesis
block
specification
from
a
trusted
source,
something
that
they
trust
and
then
they
build
the
genesis
block
locally
on
their
system
and
if
their
hash
is
a
match,
the
nodes
peer
up.
That's
how
it
works.
Yeah.
A
Yes,
I
am,
I
also
am
very
excited
about
it.
I'm
looking
forward
to
just
being
a
participant
instead
of
an
active
participant,
so
we've
tried
very
hard
to
not
have
a
satoshi
here,
there's
no
satoshi,
no
fake
toshi,
no
craig
right,
no
satoshi!
None
of
that.
So
we
are
a
team
here,
we're
all
collaboratively
building
this
thing
and
launching
it
together
as
a
group.
A
Going
once
going
twice,
yeah
catch
me
on
discord.
Catch
me
on
telegram
and
yeah
I
mean
joe
will
huddleshark
will
ask
what
the
what
the
community
wants
to
learn
about
next
week
and
I'd
be
happy
to
talk
about
it.
So
cheers
everyone
have
a
great
day,
bye.