►
From YouTube: Community Call With Special Guest BitGo
Description
In this week's community call the Casper association is joined by special guests BitGo
Read more about our partnership with BitGo for secure asset custody here
https://blog.casperlabs.io/bitgo-building-secure-custody-solution-for-casper/
Follow Casper on Twitter
https://twitter.com/home?lang=en-gb
Join our Telegram
https://t.me/casperblockchain
Check out BitGo here
https://www.bitgo.com/
A
Hi
everyone
and
welcome
to
the
community
call.
My
name
is
ashley
kariaga
and
I
help
with
the
operations
at
casper
labs
on
today's
call
we'll
be
talking
about
our
partnership
with
bill
with
bitgo
to
build
secure,
custody
solutions.
We
are
joined
in
today's
call
by
joe
from
bitgo
and
metta
ashok
and
ed
from
casper
labs.
A
B
Thanks
a
bunch
ashley,
so
yeah
we're
super
excited
to
have
the
folks
that
were
on
the
call.
Today
you
know
joe
from
bitco
and
hastings.
B
You
know
ed
is
the
engineering
manager
of
casper
labs,
so
he
is
the
force
behind
the
engineering
team
and
like
one
of
the
most
essential
people
to
me,
you
know,
along
with
ashoka
course,
director
of
professional
services.
These
guys
really
gosh
my
right
and
left
hand.
B
I
don't
know
what
else
to
say
and
then,
of
course,
joe
we've
been
have
such
a
wonderful
time,
working
with
bitco,
really
really
honored
that
you
selected,
you
know
bitco
gets
to
decide
who
they
integrate
with
so
we're
very
honored
and
grateful
to
have
been
selected
by
bitco.
B
You
know
for
custody
on
casper,
so
today
we're
gonna,
we're
gonna
talk
a
little
bit
about
our
integration
with
bitco
and
the
implications
for
enterprise,
and
then
I
will
provide
a
technical
update,
including
the
launch
of
mainnet,
so
without
further
ado,
let's
dive
in
ed.
You
want
to
give
a
little
update
about
yourself
just
a
little
bit
of
background,
because
I
think
it's
one
of
the
first
community
calls
you've
been
on.
So
just
introduce
yourself
to
the
community
and
then
we'll
have
joe
talk
about
himself
a
bit.
C
Sure
so
I'm
a
engineer.
I've
been
in
the
software
industry
for
a
little
bit
over
20
years,
working
on
various
you
know:
military
financial,
leisure,
etc,
medical.
So
I've
worked
on
a
lot
of
different
bases
and
a
lot
of
different
technologies,
and
this
has
been
coming
up
on
my
two
years
here
at
casper
and
building
this
blockchain.
It's
been
a
great
experience,
so
I
lead
the
team.
We've
got
several
groups
within
engineering
and
they
all
sort
of
funnel
up
and
hopefully
work
together
to
deliver
a
quality
product.
B
Thanks
a
bunch
yeah,
I
definitely.
I
definitely
agree
with
that
and
I
would
say
that
our
validators
also
agree.
I've
heard
great
great
feedback
about
the
product,
so
great
job
there
and
we're
in
the
final
push
to
mainnet.
So
six
days
it's
been.
You
know
two
years
in
the
making,
so
very
excited
about
that
joe.
You
want
to
tell
us
a
little
bit
about
yourself
and
bitco
and
what
you
do
there.
D
I've
been
in
the
crypto
space
specifically
at
bitco
for
three
years,
but
got
introduced
to
bitcoin
in
2014
and
haven't
looked
back
ever
since
one
of
my
favorite
parts
about
my
role
at
bitco
is
I
get
to
manage
all
of
our
relationships
with
different
networks
and
protocols,
and
it's
been
an
absolute
pleasure
working
with
casper
throughout
this
whole
process.
Super
excited
for
your
mainnet
launch.
B
Yeah,
likewise
and
community
folks,
I'm
sorry
we
don't
have
our
cameras
on
today,
because
you
know
all
of
us
have
been
pulling
some
pretty
late
nights
and
I
just
don't
want
to
accost
you
with
the
way
I
look
today.
So
please
forgive
me.
I
will
have
my
cameras
on
next
week,
but
we're
giving
ourselves
a
little
bit
of
a
breather
from
cameras
on
screen.
B
So
so,
let's,
let's
kind
of
dive
into
you,
know
the
bitgo
integration
so
joe
and
ed,
do
you
want
to
talk
a
little
bit
about
how
the
integration
works
right
and
and
namely,
like
I
would
like
to
know,
because
I
completely
understand
the
integration
from
the
perspective
of
you
know:
custody
right,
so
custody
is
a
custody
solution.
Is
one
where
you
don't.
You
know
it
supports
you
in
taking
care
of
your
of
your
keys
right
of
your
crypto.
B
I
that
that
how
much
I
know,
but
I
also
understand
that
there's
a
huge
vertical
that
bitco
provides
for
enterprise,
so
talk
a
little
bit
about
your
custody
solution.
What
makes
you
guys
a
leader
in
the
space
and
what
that,
what
the
implications
are
for
enterprise,
if
you
could
joe.
D
You
know
a
bitco
client
can
come
in
and
define
exactly
how
transactions
should
be
conducted,
who
should
be
involved?
Who
needs
to
approve
things
and
so
on
and
so
forth,
and
so
we
make
it
very
easy
for
enterprises
not
only
to
use
multiple
blockchains
from
a
single
platform
and
api,
but
also
to
enforce
whatever
sorts
of
controls
that
they
might
need
to
run
their
business
in
the
most
secure
manner.
B
That's
that's
amazing,
and
if
you
know
we
completely
align
on
this
right,
like
ed,
is
actually
the
gentleman
that
designed
the
weighted
accounts
and
threshold
feature
in
casper
for
the
exact
same
reason
like
we
recognize
that,
having
that
flexibility
and
control
is
absolutely
essential
for
people
when
they
are,
you
know
dealing
with
their
accounts.
Writing
security
is
massively
important,
but
flexibility
and
control
is
also
important,
so
yeah,
I
completely
completely
get
it.
That's.
That's
amazing.
Let's
dig
in
a
little
bit
into
the
integration.
B
If
we
could
so
can
we
talk
a
little
bit
about
a
little
bit
just
dive
in
a
little
bit
more
deeply
into
the
integration
and
what
users
can
expect
from
the
partnership.
D
Sure
so
I
think
there's
there's
two
things
happening
in
parallel,
so
first
I'll
start
off
with
the
custody
side
of
things
which
it
looks
like
we're
addressing
in
this
slide
here
so
bitco's
custody
offering
allows
people
to
create
wallets.
In
this
case
for
casper
and
the
way
that
bitco
operates
its
custody
business
is
we
do
deep,
cold
storage,
so
this
means
that
we
operate
super
secure
facilities
where
private
keys
are
generated
and
stored
offline.
D
So
we
have
a
very
secure
environment
where
you
know
when
a
client
transacts,
we
have
multiple
key
signing
which
are
thousands
of
miles
apart,
and
I
think
one
of
the
the
best
features
of
this
bitco
and
casper
integration
is
that
not
only
do
we
have
the
ability
to
store
these
assets,
we
also
have
the
ability
to
interact
with
the
blockchain
in
bigger
ways,
and
so,
for
example,
a
client
can
have
their
private
keys
held
in
cold
storage
at
bitco,
which
is
regulated
and
insured,
but
they
can
also,
for
example,
delegate
to
validators
of
their
choice,
claim
their
staking
rewards
and
take
other
actions
that
you
know
are
unique
to
casper,
so
we're
providing
this
deep
level
of
security
and
also
having
the
utility
right
from
that
environment.
B
Yeah,
that's
that's
really
amazing.
I
mean
providing
that
flexibility,
and
you
know
enabling
bitcoin
customers
to
be
to
participate
in
staking
is
huge.
You
know
we
don't
have
a
slide
about
the
hot
wallet
offering,
but
do
you
want
to
talk
a
little
bit
about
that?
You
guys
will
be
powering
everything
that's
happening
on
coin
list.
Is
that
correct?
So
when
people
participate
in
coinless,
are
they
using
they're
using
bitco
hot
wallets?
Is
that
correct.
D
That's
correct
and
I
think
it's
actually
a
really
important
point
for
the
community.
So,
as
I
was
saying
earlier,
bitco
is
actually
among
the
largest
providers
of
all
technology
in
the
world
somewhere
around
20
of
all
unchained
bitcoin
transactions
come
through
our
wallets
and
the
reason
for
that
is.
We
have
over
200
exchanges
in
50
countries
which
use
bitco's
wallets
to
power
their
platforms,
and
so
you
know
as
part
of
this
broader
rollout.
You
know
over
time.
D
I
do
think
there's
going
to
be
tons
of
exchanges
that
will
want
casper
to
be
a
part
of
it,
and
you
know
if
I
look
at
something
like
coin
list.
For
example,
you
know
they'll
be
using
a
combination
of
bitco's
custody
and
hot
wallets
to
make
sure
that
they
can
offer
the
highest
levels
of
service
to
their
users
and
facilitate
you
know,
large
volumes
of
deposits
and
withdrawals
in
a
very
secure
fashion,.
B
Yeah,
that's
that's
super
important
right,
like
you
hear
about
the
horror
stories
with
exchanges
where
they
don't
actually
custody
the
keys
very
securely.
So
for
me
personally,
that
gives
me
a
massive
peace
of
mind
when
working
with
coinless
that,
knowing
that
you
know
the
back
end
is
powered
by
bitco
when
you're
buying
casper
that's
hugely
hugely
important
right,
you
know
you
can
have
you
know
kind
of
rest
assured
that
the
crypto
is
going
to
be
stored,
securely
right
and
safely
with
bitco
solutions.
So
that's
that's
amazing!
Ed!
B
Do
you
want
to
talk
a
little
bit
about
like
the
integration,
because
we've
been
working
with
bitco
for
four
months
right?
I
think
we
started
working
with
you
guys
in
october
and
we
learned
a
lot
in
the
product
as
we
you
know
embarked
upon
this.
It
was
one
of
our
first,
if
not
the
first
deep
integration
we
did
with
the
blockchain.
Do
you
want
to
talk
a
little
bit
about
the
things
that
that
you
learned
about
about
our
product
when
you
worked
with
him.
C
C
Our
general
internal
model
is
a
deploy
model,
so
all
transactions
that
affect
any
sort
of
a
change
to
global
state
do
so
through
a
variety
of
kinds
of
deploys,
and
so
basically
the
main
interaction
points
for
third-party
integration,
like
bitgo,
is,
is
determining
which
smart
contracts
or
session
logic
they
need
to
execute
via
put
deploys
and
then
what
information
they
want
to
query
for
afterwards
to
verify
that
the
intended
action
occurred
which
block
it
is
in
and
to
be
able
to
then
have
some
programmatic
responses
on
their
side
to
take
further
action
that
they
need
to
keep
their
data
correct
and
then
also
later,
actions
that
they
might
drive.
C
Based
on
that.
So
the
most
sort
of
complicated
new
thing
that
we
had
to
contend
with
for
bitgo
is
their
account
initialization,
where
they
want
to
initialize
it
and
then
essentially
configure
it
and
so
working
out.
The
details
of
that
took
a
little
bit
of
back
and
forth
communication,
but
we
got
there
and
then
we
also
provide
them
with
a
javascript
sdk
so
that
some
of
their
in-client
or
in-browser
experience
apps
can
also
interact
with
that
json
rpc
in
an
easily
and
convenient
way
for
them.
That
was
pretty
much
it.
B
C
Yeah
correct,
so
all
all
staking
or
proof
of
stake,
related
behaviors
go
through
what
we
call
our
auction
contracts
and
those
are
all
just
straight
up.
Normal
deploys
nothing
special
about
them.
You
effectively
have
through
our
contract
api.
C
Your
your
session
logic
or
contract
logic
can
essentially
talk
directly
to
the
auction
contract
to
increase
your
bid
or
decrease
your
bid
or
delegate
on
delegates
so
forth.
So
all
of
that
is
fundamentally
baked
in
foundational
behavior,
that's
accessible
to
any
party,
and
then
the
bitco
integration
just
uses
that-
and
you
know
their
own
internal
logic
on
their
side
of
it
to
affect
the
changes
that
they
need
to
to
the
stake
amounts.
B
Amazing
excellent,
this
yeah,
it's
it
for
me,
it
was
a
big
why
you
know
big
eye
opener
when
we
started
working
with
bitco
and
really
understood
the
internals
of
their
system,
and
you
know
what
they
needed
from
us,
because
their
before
intensive
purpose
is
very
much
like
an
exchange
right.
So
we
learned
a
lot
about
what
exchanges
need
from
the
for
the
protocol
as
we
integrated
with
them
and
we're
super
excited.
B
It's
been
really
a
pleasure
working
with
the
team
everybody's
been
super,
responsive
and
yeah
looking
forward
to
a
long-
and
you
know
fruitful
partnership
with
bitco
over
the
coming
years.
So
thank
you
very
much
joe
for
hopping
on
I'm
going
to
do
the
engineering
update
now,
if
that's
okay
with
everyone,
I'm
going
to
talk
a
little
bit
about
where
we're
at
and
our
engineering
status,
so
execution
we're
in
our
third
weekly
sprint
of
the
21.04
release
cycle,
and
this
is
going
to
be
the
first
production
upgrade
of
the
casper
protocol.
B
So
the
top
priority
right
now
obviously
is
to
launch
mainnet,
and
you
know
this
release
is
going
to
focus
on
performance
and
stability.
I
have
you
know,
told
ed
that
I
would
like
very
much
to
increase
the
validator
set
size
to
200
nodes
by
the
end
of
this
release,
and
we
have
you
know-
reducing
protocol
state
memory,
consumption
and
networking
robustness
to
help
support
that,
so
the
team
is
actively
working
on
you
know
getting
to
that
place.
Tag
0.0.94
with
rust
is
our
release
candidate.
B
We
believe
this
is
going
to
be
our
main
net
release
candidate
and
I'll
talk
a
little
bit
about
our
plans
towards
launch
and
what
we're
doing
between
now
and
next
monday
is
when
we're
planning
on
launching
mainnet.
B
So
let's
talk
a
little
bit
about
current
focus
right
so
again,
performance
hardening
and
production
engineering
work,
so
highway
is
digging
in
a
little
bit
deeper,
around
specific
equivocation
type
attacks
and
then
prioritize
synchronization
of
vertices
lower
sequence
number.
This
again.
These
are
efficiency
and
security
type
of
features.
On
the
node
rust
side,
we
are
testing
the
social
consensus
emergency
restart.
B
So
we
actually
did
this
in
delta
last
week.
It
wasn't
the
really
efficient.
I
mean
the
really
elegant
version.
It
was
a
much
more
rough
version,
and
do
you
want
to
talk
a
little?
I
put
you
on
the
spot
to
talk
a
little
bit
about
social
consensus
and
what
that
looks
like.
C
Yeah,
okay,
so
basically
we
have,
you
know
just
step
back
from
that.
Briefly,
we
have
a
unified
upgrade
mechanism
where
we
use
essentially
a
launcher
process
to
spin
up
binaries
through
upgrade
points,
and
our
upgrade
model
is
built
around
what
we
call
protocol
versions.
We
have
a
single
simver
based
version
for
all
of
our
protocol
definitions.
The
protocol
definition
is
effectively
consensus
and
external
apis
node
to
node
and
client
to
node.
C
So
as
we
make
changes
to
the
software
over
time,
and
we
need
to
get
it
out
to
the
network,
our
goal
is
to,
whenever
possible,
have
a
in-place
upgrade,
so
people
don't
have
to
bring
their
machines
down.
Essentially,
they
opt
in
to
the
new
protocol
version
by
pulling
down
the
binary
and
artifacts
such
as
the
chain
spec
to
their
operating
machines.
C
They
don't
stop
the
running
node
process,
the
launcher
itself
and
the
node
process
itself
will
detect
that
an
upgrade
is
available
and
the
block
the
era
id
that
it
is
supposed
to
happen
at
right.
So
it
all
works
mechanically
and
hands-free.
C
Well,
then,
we
leveraged
that
same
mechanic
to
do
that.
We
have
two
different
styles,
one
of
which
is
what
we
call
a
hard
reset,
where
we
basically
can
just
roll
the
chain
back
to
a
specific
era,
very
similar
to
doing
a
hard
reset
and
get
that
would
be.
You
know,
essentially
the
the
brute
force
approach
that
I
just
mentioned
that
we
tested
in
delta
11
last
week.
C
That
has
certain
advantages.
It's
very
easy!
You
just
basically
pop
some
blocks
off
the
chain
and
go
back
to
the
previous
era.
Typically,
however,
we
also
have
a
much
more
sophisticated
upgrade
version
or
sorry
hard
reset
version
where
we
can
essentially
retain
those
blocks
and
just
modify
global
state
into
the
next
block.
C
So
if
you,
for
instance,
there
was
a
rogue
validator,
we
could
potentially
remove
them
if
the
community
decided
that
that's
what
they
wanted
to
do
and
we
would
essentially
just
without
losing
state
the
next
block
forward
would
lack
that
validator
things
like
that,
where
you
can
very
surgically
make
changes,
that's
obviously
a
much
more
of
a
sandbox,
it's
open,
it's
open-ended.
It
would
be
a
one-off
each
time
and
so
we're
setting
up
a
test
for
that.
C
For
you
know
a
very
particular
scenario
of
that
that
we're
going
to
actuate
here,
probably
later
this
week
and
the
plan
there
is
it's
an
option
it's
available
if
necessary,
but
it's
a
sort
of
break
class.
If
needed,
we
don't
intend
for
that
to
be
the
common
or
or
normal
mechanism
of
affecting
correction
to
the
next
network.
That
would
be,
if
you
had
to
if
the
community
really
desired,
that.
B
Yeah
I
mean
we're
all
about
providing
tools
and
and
core
capabilities
in
the
platform.
I
talk
about
this
a
lot,
and
this
is
an
example
too,
that
the
community
can
administer
the
blockchain
as
they
deem
fit,
and
they
would
need
two-thirds
of
the
stake
to
agree
that
they
wanted
to
perform.
You
know
execute
on
social
consensus
right.
It
isn't
like
any
single
validator
could
could
do
this.
The
community
would
need
to
agree-
and
I
believe
that
you
know
we
we
actually
hold
on
to
some
protocol
state
right.
B
So
this
is
where,
like
the
unbonding
wait
period
and
the
amount
of
protocol
state
that
we
store
in
memory
becomes
important
right,
so
giving
the
the
validator
set
or
the
community
enough
time
to
make
these
kinds
of
decisions
right.
I
think
we're
looking
at
about
14
hours.
Is
that
correct?
It's
like
about
14
hours,
we're
giving
them
to
kind
of
rally
around
any
kind
of
social
consensus
decision
right
before.
B
Yep
yep
got
it
yeah
very
cool.
I
mean
I,
I
really
do
love
our
upgrade
model.
I
think
it's
really
really
excellent,
because
it
provides
us
a
very
clean
cut
from
one
version
to
the
other,
and
it
also
provides
enough
flexibility
that
we
can
continue
to
upgrade
and
maintain
the
chain
which
is
massively
important
right
being
able
to
drop
new
releases.
I
mean,
theoretically,
we
could
even
do
a
radically
different
consensus
protocol
as
long
as
it's
you
know,
dag
based
right
era
based
consensus
protocol.
B
C
That
is
correct
yeah,
so
we
designed
it
to
essentially
be
pluggable
consensus
as
long
as
it's
dag-based
and
era
based
as
you
said
so
in
the
future.
If,
for
some
reason
we
did
need
to
transition
the
rest
of
the
operating
software
global
state
execution
engine,
all
of
that
stuff
is
completely
agnostic
to
the
consensus
algorithm.
The
communication
back
and
forth
is
very
arm's
length,
so
we
could
swap
out
some
other
equivalent
consensus
algorithm
without
disrupting
either
the
past
state
or
the
other
parts
of
the
of
the
software.
B
Yeah,
it's
pretty,
it's
really
really
cool.
It's
a
it's
a
fantastic
design,
and
you
know
with
the
mainnet
launch
of
mainnet
and
the
public
sale,
we
will
be
transitioning
all
of
the
intellectual
property
to
the
association
and
it
is
the
association's
intention
to
open
source
it
under
apache
2.0.
B
So
when
that
happens,
I
would
not
be
at
all
surprised
to
see
lots
of
forks
of
the
casper
software
to
experiment
with
exactly
these
kinds
of
things.
Right.
You'll
see
folks
experimenting
with
different
consensus
program
protocols
within
the
plugable
consensus.
I
think
it's
only
a
matter
of
time,
so
very
interesting
stuff.
So
we
are
doing
the
prototype.
Joiner
is
for
fast
synchronization,
so
we
are
planning
on.
B
We
have
a
pull
request
open
from
henry
that
does
do
state
try
pruning,
and
this
is
basically
pruning
away
global
state
so
that
old
versions
of
the
blockchain
you
know,
after
a
certain
point
can
be-
can
be
pruned
away
to
make
it
more
efficient
for
validators
to
operate
nodes.
We
will
have
large
archival
nodes.
That
is
the
intention
that
the
association
will
run
the
archival
node,
but
that
basically
majority
of
the
validators,
if
they
so
wish,
can
run
lighter
clients.
B
This
is
to
make
the
protocol
really
really
efficient
right
in
terms
of
for
operating
expenses.
We
tend
to
be
a
bit
of
a
disc
hog
right
now,
let's
see
what
else
you
want
to
talk
about.
We
are
supporting
at
test
testing
sre
preparing
for
maine
net
provisioning
hardware
and
setting
up
infrastructure.
So
let's
talk
a
little
bit
about
the
plan
to
maintain
it,
I'm
going
to
share
something
here:
it's
pretty
raw,
but
this
is
my
mainnet
launch
workback.
B
I
call
it
a
work
back
schedule
and
the
big
piece
that
we're
working
on
right
now
you
can
see
a
lot
of
work
in
progress.
Joe
has
been
working
tirelessly
to
onboard
our
vfta
holders
onto
bitco.
B
We
want
to
provide
them
an
opportunity
to
use
bitco,
custody
and
delegate
those
keys
to
validators
in
the
casper
network,
and
so
he's
working
really
hard
to
get
them
onboarded
and
we're
going
to
generate
their
wallets
and
then
roll
those
wallets
into
the
genesis
block
right
and
so
that
the
date
for
that
is
the
25th
so
by
the
25th,
we'll
have
all
of
our
bitco
wallets
and
their
staking
options
decided
along
with
their
token
balances,
and
at
that
point
around
the
25th
26th.
B
The
validators
will
be
launching
the
genesis
block,
so
this
is
not
going
to
be
up
to
us
right,
casper
labs.
The
company
itself
will
not
be
running
a
known
and
main
node
in
mainnet.
We
will
not
have
an
ip
in
the
trusted
ip
addresses
and
the
config.tomml
for
those
of
you
familiar
with
it.
It's
going
to
be
the
validators
themselves,
so
I
will.
I
am
preparing
my
go:
no
go
documentation
and
working
with
them
to
gauge
their
readiness
for
launch
and
assuming
that
they
give
us
a
green
light
on
the
26th.
B
We
will
then
stage
the
final
files,
the
1.0
version
of
the
software
and
the
and
and
be
ready
to
go.
You
know
so
we'll
stage
everything
on
the
27th
with
a
predicted.
You
know
ensure
that
everybody's
ready
by
the
20
29
with
gen
the
genesis
block
launching
on
the
30th.
So
that's
the
plan
gosh
two
years
in
the
making,
so
we've
been
working
on
this
for
a
really
long
time.
It's
very
very
exciting,
and
I
am
super
stoked
to
be
working
with
all
of
our
wonderful
genesis.
Validators.
B
You
know
our
founding
founding
set
for
the
genesis
block.
So
that's
a
little
bit
about
that
about
mainnet,
launch
and
moving
forward
we're
going
to
continue
working
really
hard
with
the
ecosystem
right.
So
if
we
talk
about
a
little
bit
about
the
customers,
there's
three
big
personas
that
are
involved
in
blockchain.
It's
going
to
be
the
people
that
join
your
community
via
public
sales.
It's
going
to
be
validators
that
run
the
network
and
and
stake
tokens,
and
then
the
third
one
is
going
to
be
smart
contract
developers
and
truthfully
we,
we
haven't.
B
You
know,
engaged
with
smart
contract
developers
that
much-
and
we
are
starting
now
to
see
some
of
that
engagement.
So
we're
going
to
be
really
focusing
hard
on
the
ecosystem
right,
implementing
the
contract,
dsl
casper
course
slides
and
recordings,
and-
and
you
know
the
javascript
sdk
and
even
you
know,
working
a
lot
more
with
the
typescript
contract
library,
where
we
have
a
developer.
That's
really
focused
on
that.
So
there's
going
to
be
a
lot
of
work
on
the
ecosystem
and
the
smart
contract.
B
Runtime
right
features
that
we
expect
to
come
in
on
the
economics
research.
We
did
engage
with
tim
roughgarden.
We're
very
excited
that
he's
going
to
be
doing
a
formal
analysis
of
the
economics
of
highway
super
excited
to
see
what
he
comes
up
with
he's,
also
going
to
be
weighing
in
on
our
slashing
decision.
We
have
furloughed
slashing
for
a
period
of
time,
simply
because
we
we
believe
that
it's
more
likely
that
it
will
be
operator,
error
right
or
the
untoward
bug
that
could
potentially
cause
an
equivocation.
B
So
right
now,
validators
just
go
into
a
penalty
box
for
both
liveness
failures
and
equivocation
disasters
or
like
equivocations
by
themselves,
and
we
did
this
to
really
protect
that
investment,
and
you
know
their
investment
and
tim
will
be
providing
a
deep
analysis
on
the
merits
of
slashing
or
not
slashing
and
alternative
slashing
strategies.
C
Yeah,
okay,
so
we're
basically
working
on
essentially
the
gas
price
market,
to
enable
individuals
to
compete
for
prioritized
slots
and
block
right
now,
it's
egalitarian
and
it's
essentially
first
in
first
out
so
as
we
get
more
information
around
usage
patterns
and
sizing
of
deploys
and
blocks,
we're
going
to
be
essentially
introducing
alternatives,
sort
of
pivoting
around
the
idea
of
well.
I
really
want
my
thing
to
go
first,
so.
B
C
Yeah,
so
right
now
we're
collecting
data.
We
don't
want
to
do
something
just
sort
of
arbitrarily.
So
as
we
you
know,
try
different
strategies
and
analyze
the
information
we're
gaining
from
usage
of
the
system.
We
can
roll
out
an
alternative
strategy
once
we've
settled
on
on.
You
know
what
works
best
right.
B
Yeah,
absolutely
and
one
of
the
things
we
did
promise
our
customers
is,
you
know,
is
stabilized
gas
fees
right.
So
definitely
the
gas
futures
market's
going
to
play
a
role,
but
so
is
scalability
right.
So
we
get
a
lot
of
questions
around
the
scale
of
the
casper
network
and
you
know
from
my
perspective,
I
believe
we
have
a
fair
bit
of
headroom
and
engineering
work
that
we
can
do
to
increase
the
performance
of
the
base
protocol
right.
B
So
this
is
just
our
first
release
candidate,
but
there's
there's
a
lot
of
work
and,
if
I
can
just
say
so,
and
has
a
long
and
illustrious
career
of
doing
of
building
high
performance,
you
know
architectures
at
scale.
So
I
have
absolutely
no
doubt
that
we
know
where,
where
we
need
to
make
you
know
performance
enhancements
and
we're
going
to
be
going
after
that
hard.
C
Yeah,
so
the
the
main
goal
is
to
balance
you
know
the
economics
and
also
with
the
the
throughput
of
the
system
right,
so
we
want
to
find
that
optimal
equilibrium
where
we're
able
to
guarantee
a
certain
amount
of
throughput
across
the
board
for
certain
fundamental
transactions
or
fundamental
behaviors,
while
also
allowing
for
some
competition,
for
you
know,
user,
to
find
work
and
so
forth.
So
you
know
that's.
C
B
Yeah,
that's
exactly
right,
it
is
you
know
we
there
we've
done
a
great
job
in
moving
the
needle
forward
with
respect
to
the
trade-offs,
but
there
are
still
some
trade-offs
that
we
have
to
address
right.
I
have
to
have
to
work
within
so
first
question
is
coming
from
the
community.
This
is
for
you,
joe
is.
Is
there
a
special
wallet
app
that
we
can
use
on
bitco?
So
I
think
maybe
what
we
can
do
is
just
talk
about.
D
Hey
man
sure
so
I'd
say
you
know
very
generally,
bitco
is
typically
institutional.
Only
so
our
typical
client
base
includes
exchanges,
trading
firms,
institutional
investors,
brokers,
lending
and
borrowing
platforms,
so
on
and
so
forth.
So
it
is
a
standardized
application
for
all
those
parties,
and
you
know,
we'd,
be
happy
to
do
a
demo
of
the
bitco
system
for
the
broader
community
in
the
future.
To
kind
of
give
a
behind-the-scenes
view
of
you
know
what
an
institutional
casper
wallet
looks
like.
B
Yeah,
that
sounds
great
from
what
I
understand:
it's
completely
transparent
to
the
user
right,
so
the
exchanges
basically
have
an
agreement
to
use.
Bitco
wallets
the
end
user
doesn't
actually
know
that
they're
using
bitcoin
wallets
right,
but
when
they
create
accounts
on
the
exchange.
That
token
is
actually
custodies
with
custody
with
bitco.
So
you
don't
have
the
mount
gox
kind
of
thing
happening
right,
that's
really
what
it's
about
and
you
can.
B
Yep,
so
I
mean
those
of
you
that
have
you
know
will
be
purchasing
and
holding
casper
tokens
on
coin
list.
You
have,
you
know
assurances
that
your
tokens
are
being
custodied
and
bitco
on
the
back
end,
you
don't
have
to
do
anything
special
for
that
right,
bitco
is,
is
really
kind
of
you
know
the
foundation
upon
which
the
casper
wallets
are
built
when
you're
working
with
coinlist
and
from
what
I
understand,
many
other
exchanges
as
well.
So
that's
fantastic.
B
The
first
question:
will
you
be
introducing
a
gas
token?
So
you
know
the
idea
is
that
we
plan
to
tokenize
block
space
right
so
that
that
would
be
in
essence,
this
idea
of
not
necessarily
a
gas
token,
but
in
a
manner
where
we
can,
you
know,
create
a
way
to
purchase
future
block
space.
So
maybe
alex
can
talk
about
this,
he's
one
of
our
economists
and
put
him
on
the
hot
spot.
E
Yes,
certainly
so,
yes,
when
we
designed
the
initial
gas
futures
system,
we
did
have
this
possibility
in
mind.
Actually,
as
we
move
into
mainnet,
and
we
start
flushing
out
the
design
and
confirming
that
everything
about
the
design
is
feasible.
I
suspect
that
there
will
be
a
way
to
re-trade
space
after
this
purchase.
So
essentially
yes,
it
will
be
sort
of
like
a
gas
token.
E
I
mean
it's
a
little.
You
know
it's
a
to
be
clear.
It's
not
really
like
you
know
it's
not
like
a
fungible
token.
Really,
it's
more
like
an
nft
right,
you're,
basically
you're
trading
contracts.
You
know
either
for
other
contracts
or,
for
you
know
actual
you
know
malts
but
yeah.
So
you
you
have
a
particular.
What
you
will
be
trading
right
is
as
a
right
to
include
some
deploys.
You
know,
after
a
certain
amount
of
gas,
at
a
particular
block
height
or
in
some
range
of
block
heights,
or
something
like
that.
B
Sounds
good
yep
and
so
likely
that
we
will
see
some
secondary
markets
emerge.
Let's
see
here,
I
did
answer
this
question
last
week,
in
my
opinion,
is
casper
a
rival
to
ethereum.
So
I
get
this
question
a
lot
right.
So
casper
is
a
smart
contracting
block
platform.
B
I
don't
consider
ourselves
a
direct
rival
for
ethereum
because
number
one
we're
not
actively
targeting
ethereum
developers
right.
Our
smart
contracts
are
written
in
rust.
We
do
have
a
transpilation
path
for
solidity
contracts
to
casper,
but
we're
not
running
an
evm
within
our
blockchain
right.
So
if
you
want
to
work
with
casper,
there's
going
to
be
a
little
bit
of
a
lift
right,
even
if
you
transpile
your
contract,
the
execution
model
is
slightly
different
than
ethereum
right.
It's
not
like
very
straightforward
or
just
like
yeah.
B
You
know
just
transpile
your
contracts
and
drop
them
on
casper.
There
are
differences
right
and
we
believe
that
those
differences
are
important
enough
to
differentiate
us
from
other.
You
know
blockchain
protocols
in
the
space,
so
we
don't
see
ourselves
as
actually
being
a
direct
competitor
to
ethereum
at
all.
B
Another
question
is:
is
this
true
that
proof
of
stake
chains
have
have
a
weakness
about
duplicate
contracts?
How
about
casper?
I
don't
really
understand
this
question
ashley.
Can
you
get
some
more
information
from
the
person
asking
that
what
they
mean
by
duplicate
contracts?
Are
they
talking
about
duplicate
contracts
in
the
event
of
a
hard
fork
that
you
have
two
contracts
in
the
global
state
for
two
different
forks
or
something
else?
Okay,.
B
F
Directly,
I
had
a
couple
questions.
I
got
a
couple
questions.
First
off
the
the
idea
of
the
block
space
tokenization
being
nfts,
will
you
be
able
to
or
do
you
theorize
you'll
be
able
to
buy
specific
block
nfts
like
block
height
anniversary
nfts
and
and
to
me
it
kind
of
sounds
like
there'd,
be
a
collector's
market
for
that
did
you
think
that
that
might
happen.
F
C
Currently,
no,
it's
it's
all
era
based,
so
our
expectation
is,
is
you
know
normally
it
would
be
to
the
so,
let's
say
you're
in
era,
50
right
and
halfway
through
era,
50
something
happens
and
the
community
says
we
don't
want
that
to
have
happened.
We
want
to
fix
this.
So
in
that
scenario
you
would
roll
back
to
the
very
end
of
era.
49
and
all
of
the
blocks
that
had
been
produced
in
era.
C
50
would
essentially
just
be
orphaned
right,
but,
technologically
speaking
mechanically,
you
could
go
all
the
way
back
in
time
right,
there's
no
like
hard
limit
on
it.
It's
essentially
what
the
community
decides.
C
Yeah,
that's
entirely.
All
of
these
quote.
Unquote,
you
know,
consensus
driven
changes
are
based
on
the
community,
deciding
something
we
would
never
just
assert
that
this
must
occur
right.
F
Yeah,
of
course,
the
other
one,
a
couple
of
questions
for
you
metta,
the
archival
nodes,
are
they're
gonna,
get
incentives
right
now
that
you
guys
have
planned
for
running
archival
nodes
aside
from
the
association
running
them.
B
It's
a
great
question
right
because
running
the
archival
nodes
are
going
to
be
pretty
expensive.
It's
going
to
be
pretty
beefy
in
terms
of
disk
casper
can
get
it's
a
bit
of
a
disc
pac-man.
It
likes
it
likes
to
make
deep
copies
of
the
state.
Try
right,
so
some
contracts
can
be
worse
than
others.
So
you
know
when
you're
creating
your
contracts.
B
Like
you
know
token
contracts
and
such
you
have
to
be
real
cognizant
that
you're
not
doing
deep
copies,
because
you
can
your
your
storage
costs
could
escalate
rapidly
with
that
kind
of
a
contract,
so
yeah
I
mean,
I
think,
having
incentives
in
place.
Of
course,
that
would
be
the
dev
dow.
That
would
really
be
empowered
to
have
those
incentives,
or
we
could
talk
about
the
association
having
some
incentives
in
place
for
for
folks
to
run
archival
nodes.
B
As
I
said,
the
the
association
will
absolutely
be
running
a
large
archival
node
for
sure
and
an
event
store.
That's
the
intention.
F
All
right,
one
last
question:
real
quick
on
the
bitco
side.
Do
you
have
a
a
list
of
exchanges
that
you
might
be
working
with?
Is
that
something
that
you
publish
any
links
that
you
might
be
able
to
provide
for
the
for
the
community.
F
D
I
have
two
answers
to
that.
One
is,
if
you
go
to
our
website,
we
do
have
a
streaming
banner
of
some
of
our
sample
clients.
We
also
have
some
really
cool
case
studies
on
there
of
some
larger
exchanges
that
have
integrated
with
bitco
and
I
think
we're
gonna
be
making
plenty
of
intros
for
the
casper
team,
and
I
I'd
posit
to
say
that
you
know
a
lot
of
big
announcements
that
will
be
coming
out
of
casper
will
be
done
in
conjunction
with
bitco.
B
Okay,
terrific!
Well!
Thank
you,
everyone
for
joining
joe!
Thank
you
for
taking
time
out
of
your
very
busy
schedule
to
you
know,
join
us
today,
ed
same
thing,
I'm
looking
forward
to
the
launch
of
mainnet.
So
this
time
next
week,
hopefully
the
genesis
block
will
have
launched.
So
I'm
very
very
excited
for
this.
So
looking
forward
to
seeing
everybody
on
the
call
next
week,
cheers
have
a
great
day,
bye,
bye,.