►
From YouTube: CasperLabs Community Call
Description
Why Casper is the future proof blockchain built for Enterprise & Business & Development Update. Medha presents 'Blockchain as part of Application Architeture'
A
Good
morning,
good
afternoon,
good
evening,
wherever
you're
coming
to
us
from
this,
is
metta
parlikara
cto
of
casper
labs,
one
of
the
co-founders
I'm
here
to
present
our
weekly
development
update
and
project
update,
I'm
joined
by
alex
leminov
and
piotr
d.
We
just
go
by
d
because
I
can't
say
his
name
very
well
sure
it's
on
me,
I'm
not
here
all
alone
talking
to
you
guys,
let's
get
started
here,
I'm
going
to
pull
up
the
agenda
real
quickly
here
and
I
want
to
make
sure
I
talk
about
what
the
community
is
asking
about.
A
A
A
All
right,
so
we
are
in
the
fourth
sprint
of
our
seven
7.4,
I
believe,
is
a
sprint
that
we're
in
right
now
so
the
fourth
sprint
in
our
release
cycle
for
the
november
release
and
we're
focusing
on
transaction
fees,
adapt
round,
lathe
proof
of
transfer
and
bonding
and
unbonding.
A
A
We
I'm
going
to
skip
past
beta
test
net
because
it's
been
up
and
stable.
Thank
goodness,
I'm
going
to
talk
a
lot
about
charlie
charlie,
with
15
validators.
I
don't
know
if
we
got
15
people
in
there,
but
we're
pretty
close,
then
we
got
like
12
or
10
validators
in
there
there's
15
slots
available
in
the
network,
so
there's
15
slots
in
the
auction
and
if
you're
a
really
sharp
validator,
you
could
find
a
way
to
bond
and
unbond
onto
the
network.
A
I
will
be
putting
out
a
node
operator
guide
that
will
include
instructions
on
how
to
bond
into
the
network.
We
did
bond
someone
in.
We
helped
we
helped
them
out
and
got
them
bonded
in.
So
we
know
that
you
can
synchronize
your
node
and
bond
to
the
network.
It
took
us
a
little
time
to
figure
out
the
exact
sequence
of
events
with
this
version
of
the
code,
but
it's
possible
current
focus.
We've
got
our
adaptive
round
length
strategy
for
those
of
you
not
familiar
highway.
Protocol
is
partially
synchronous.
A
That
means
validators
can
choose
what
they're
around.
Basically,
when
they're
going
to
propose
blocks,
so
it
actually
makes
the
protocol
more
robust.
A
Recently
we
discovered
we
discovered
that
there's
an
attack
against
the
ethereum
3.0
protocol
called
gasper
that
actually
goes
after
the
full
synchrony
right,
so
highway
being
partially
synchronous
is
actually
important
for
security,
so
we
want
validators
to
be.
You
know
less
than
completely
synchronous
in
terms
of
when
they
propose
votes.
You
know
when
they
put
votes
out
there
and
when
they
propose
leader
slots.
This
enables
the
network
to
take
as
much
network
bandwidth
as
available
right.
So
as
the
network
is
faster
and
faster
blocks
should
be
proposed
more
frequently.
A
We're
enhancing
highway
security,
endorsements
and
fork
bomb
protection.
This
is
a
big
story.
Imitation
been
working
on
this
for
a
couple
weeks,
I'm
hoping
that
this
comes
in
next
week,
so
this
will
be
available
when
we
cut
the
dot
11
release
in
the
first
week
in
november.
So
what
we're
cutting
right
now
is
an
interim
interim
package,
because
we
have
enough
that
we
feel
we
should
put
it
in
with
charlie
and
that
the
validators
bang
on
it.
A
Adaptive
air
initialization
with
the
median
of
round
exponents
from
the
previous
era,
so
within
an
era
validators
can
slow
down
or
speed
up.
But
then,
when
we
initialize
the
era,
we
use
the
median
of
the
round
exponents
in
the
previous
area.
So
that's
a
nice
little
optimization
there
on
the
node
side,
focusing
a
lot
on
joining
rejoining
supporting
restarts
in
the
deploy
buffer.
A
So
when
you
bounce
your
node,
the
the
deploys
will
stay
in
there.
You
know
a
hard,
restart
and,
of
course,
we're
forcing
block
proposers
to
slash
faulty
validators
when
they
propose
a
block.
The
validators
will
be
slashed
in
that
block
and
then
a
proof
of
transfer.
So
basically
what
this
means
is
when
you
transfer
token
to
per
from
person
a
to
person
b,
you
see
what
the
transaction
fees
are.
For
that
token
transfer.
A
You
can
see
how
much
was
netted
out.
Basically,
some
of
this
ledger
type
functionality
that
you
would
fully
expect
from
a
financial
application.
That
is
what
we
built
tests
and
sre
we're
cutting
the
release.
So
that's
the
work
that
joe
is
doing
we're
testing
the
delta
release
candidate,
the
website
ci
cd.
For
blog.
This
is
pretty
much
done
and
we're
working
to
automate
our
release
process.
A
We
believe
we're
going
to
get
to
a
place
where
we
will
be
having
to
cut
rapid
releases
right
for
bug,
fix
and
whatnot,
so
we
want
to
automate
our
releases
completely
and
then
s
test
is
our
testing
tool.
So
we
are
basically
updating
that
to
one
to
work
with
the
rust
node,
but
then
to
add
new
features,
really
heavy
lift
on
ecosystem.
So
we've
got
clarity
that
we're
basically
porting
from
the
scala
node
to
the
rust
node.
A
We
are
doing
some
work
on
the
website.
We
updated
our
branded
messaging.
You
might
have
noticed
that
I
just
merged
a
pull
request
into
the
developer
guide
for
the
rust
node,
so
the
new
rust
client
and
how
that
works.
That's
been
merged
in
and
I'll,
be
adding
more
information
around
how
to
upgrade
contracts,
because
I
actually
figured
out
how
to
do
that
and
how
to
call
contracts.
A
So
we
now
have
both
the
updated
querying
capability,
as
well
as
calling
contracts
using
contract,
headers
and
entry
points
that
has
all
been
documented
and
available
in
the
developer
guide
and
we're
implementing
the
api
api
endpoints
for
the
event
store.
So
now
we're
going
to
do
is
we're
going
to
be
offloading.
These
query
functions
to
an
event
store
so
that
nodes
are
not
overloaded
with
query
events
right,
so
we're
trying
to
eliminate
non-deterministic
load
on
the
nodes
themselves
through
this
process.
A
Economics,
what
are
node-splitting
incentives.
B
I
mean
so
it's
essentially
an
analysis
of
how
you
can
possibly
game
the
auction
system
by
splitting
yourself
into
multiple
validators.
A
A
So
we
believe
that
this
is
a
very
nice
features
for
adapt
developers
that
they're
not
required
to
you
know,
stake
the
network
or
run
a
read-only
node
in
order
to
get
a
trusted
response
back
and
we're
implementing
storage
costs.
So
when
you
store
something
in
the
global
state,
you'll
have
to
pay
for
that
and
it
should
be
pretty
expensive
because
we
don't
want
people
putting
pictures
up
on
the
web
right
on
the
blockchain
on
the
scala
side.
We're
not
doing
any
fixes
right.
So
it's
definitely
in
maintenance
mode.
A
Only
we
haven't
done
fixes
in
a
long
time
and
we
will
be
end
of
lifeing,
the
scala
node
with
the
launch
of
delta
testness.
So
nobody
will
run
the
scala
node.
It
will
not
be
supported
if
the
community
wishes
to
take
up
the
scala
node.
They
are
certainly
welcome
to
do
that
and
make
it
compatible.
But
I
got
to
tell
you
it's
going
to
be
a
pretty
heavy,
lift,
there's
a
lot
there's
a
lot
to
do
there.
A
We're
looking
for
talented
sres
to
join
our
teams
and
we
continue
to
hold
our
weekly
work
workshops.
So
if
you
do
want
to
learn
about
how
to
write
smart
contracts
and
if
you're,
diving
in
and
you
need
some
help,
our
team
is
available
for
a
live
screen
share
session.
Where
we
will
answer
your
questions
during
these
time.
Slots
so
feel
free
to
join
us,
and
you
can
find
this
information
on
our
governance
wiki
with
current
status.
So
you
can
always
find
the
zoom
information.
A
The
the
community
has
requested
that
I
walk
through.
Why
casper
is
the
best
option
for
big
enterprises,
so
I'm
going
to
go
ahead
and
talk
about
that
real
quickly.
A
A
We
are
getting
ready
to
put
our
rewards
forth,
I'm
in
the
getting
and
final
stages
of
getting
those
approved
from
renault
renault,
and
I
have
a
meeting
scheduled
and
we're
also
going
to
figure
out
the
prize
amounts
for
the
two
prizes,
which
is
the
first
five
to
sign
a
genesis
block
as
well
as
the
most
prominent
validator
or
the
most
helpful
validator
for
the
alpha
phase,
we'll
be
closing
the
beta
phase
with
the
launch
of
the
delta
test
net.
We
pushed
that
launch
back
by
about
a
week.
A
The
marketing
team
requested
that
we
needed
a
little
extra
time
to
be
ready
to
talk
about
the
launch
comprehensively
we're
also
working
on
the
sign
up
sheet
and
getting
the
rust
client
ready
for
prime
time
so
we'll
have
the
rust
client
ready
for
key
generation.
We
will
need
all
validators
to
basically
regen
their
keys
right
as
part
of
this
process
right.
So
I'm
gonna
go
into
presentation
mode
here.
A
A
So
those
of
you
who
don't
know
me
you
know
before
I
got
involved
in
blockchain,
I
spent
two
decades
working
at
really
big
marquee
software
companies,
and
I
was
a
technical
leader
right.
I
was
responsible
for
quality
and
core
product
delivery,
and
so
the
business
you
know,
depended
on
me
to
deliver
robust,
reliable.
A
You
know
software
that
was
really
centrally
run
right,
so
we
had
servers
in
our
data
centers
for
those
of
you
that
aren't
aware
some
of
these
data
centers,
like
you
know,
back
in
the
day,
this
is
of
course,
a
long
time
ago.
Omniture
had
over
16
000
servers
in
their
data
centers
and
we're
talking
about
over
a
decade
ago.
A
So
just
imagine
how
much
how
much
more,
how
many
more
servers
they
have
running
in
their
data
centers
now
right
at
that
time
they
had
16
000.,
imagine
shipping
code
to
16,
000,
servers
right
and
imagine
a
bug
getting
into
any
one
of
those
16
000
servers.
A
So
it
was
a
massive
responsibility
that
I
held
on
my
shoulders
and
I
was
entrusted
to
make
these
kinds
of
technical
product
decisions
around
code
quality
or
whether
we
were
ready
to
go
or
no
go
for
the
company,
and
I
did
this
on
a
daily
basis
and
what
I
learned
you
know,
as
I
delved
into
the
blockchain
space,
that
a
lot
of
blockchains
really
didn't.
Take
this
kind
of
point
of
view.
A
I
learned
that
the
the
market
just
simply
did
not
meet
these
requirements,
and
so
we
set
out
to
build
a
protocol
that
did-
and
we
didn't
actually
do
this
intentionally.
I
was
like
well,
of
course
you
need
to
do
that.
Well,
of
course,
you
need
to
do
that.
Like
what
do
you
mean?
You
can't
do
these
things,
it's
absolutely
required.
A
I
would
never
use
a
protocol
that
didn't
do
this
and
we
kind
of
fell
into
this
right,
and
so
today
you
know
we'll
kind
of
walk
through
four
key
business
problems
in
software
architecture
and
how
we
solve
for
that
at
casper
right,
and
so
you
know
just
so.
You
know
our
team
really
is
steeped
in
building
enterprise
grade
software
right.
This
is
just
a
few
of
the
companies
that
folks
on
the
core.
A
This
is
the
core
development
team
have
worked
at
right,
we're
not
even
talking
about
the
business
side,
the
business
side,
there's
even
more
expertise
with
large
large
financial
companies
in
fintech
right,
but
this
is
on
the
core
side.
These
are
the
big
some
of
the
big
companies
where
we've
built
backbone
infrastructure
for
them,
and
so
we
know
what
it
takes
and
so
blockchain's
got
a
huge
potential
to
give
us
an
edge
in
the
marketplace
for
companies
that
adopt
it
right.
A
But
in
order
to
adopt
it,
you
need
to
know
that
you
can
build
a
business
on
it
and
a
business.
That's
going
to
stand
the
test
of
time
right.
It's
not
good
enough!
For
today,
it's
gotta
work
for
tomorrow.
A
So
from
my
perspective,
you
don't
want
to
implement
blockchain
for
its
own
sake.
You
got
to
think
about.
It
is
there's
a
business
benefit
to
adding
a
layer
of
trust
right.
So
really
you
know
provenance
who
owns
this
asset,
what
happened
and
what
order
did
it
happen
in
traceability
and
then
really
that
has
to
be
grounded
in
a
trust
layer
and
there's
lots
of
existing
applications.
A
That
answer
the
top
two
questions,
but
they
use
agencies
to
achieve
this
trust,
layer
and
they're,
also
error
prone
and
very
expensive,
and
so
the
question
to
ask
is:
does
the
product
or
service
benefit
from
a
trust
layer
or
are
operations
more
efficient
as
a
result
of
a
trust
layer?
And
if
the
answer
is
yes,
then
blockchain
can
make
sense
for
your
product
or
service
or
offering
right,
and
some
of
the
examples
we've
got
is
like
you
know,
we're
doing
a
patent
project
here
right
and
five
to
ten
percent
of
all.
A
Patents
are
sold
by
someone
that
doesn't
actually
have
the
right
to
sell
them.
Pharmaceutical
companies
spend
almost
twice
the
amount
of
time
validating
their
clinical
trial
data
compared
to
collecting
the
data
set
itself,
and
just
imagine
if
you
can
bring
drugs
to
market
almost
fifty
percent
faster
with
the
same
layer
of
efficacy
and
trust
in
the
data.
What
are
the
implications
right,
if
not
more
trust
in
the
data?
A
So,
let's
start
talking
about
the
essential
pieces
of
an
application
right,
there's
a
few
core
user
stories
that
you
need
a
compelling
answer
for
if
you're
going
to
go
ahead
and
build
a
product
or
service
that
uses
technology
or
maybe
not
even
use
technology
right,
these
are
basically
things.
You
need
in
any
kind
of
business
and
if
you're,
not
leveraging
technology
for
them,
you're
going
to
get
left
behind
very
quickly
you're
going
to
be
out
competing
in
the
market
right,
so
you
got
to
acquire
users,
and
you
have
to
support
these
users.
A
You
got
to
accept
payments
and
apply
them
towards
the
use
of
the
core
service
that
you're
offering
or
else
you're
not
going
to
make
any
money.
You
have
your
core
logic.
This
is
your
unique
value
proposition.
You
have
to
store
your
data
somehow
either
on
chain
or
off
chain
and
you're
going
to
need
some
kind
of
reporting.
A
You'll
either
need
kpis
to
improve
your
business
or
your
users
are
going
to
need
reports
and
you'll
need
to
administer
all
of
these
pieces
in
some
fashion
and
you'll
need
to
upgrade
your
entire
system,
including
your
smart
contracts
right
and
because
you're
talking
about
blockchain
we're
talking
about
smart
contracts
here.
So
let's
dig
into
each
functional
area.
So,
let's
start
with
user
accounts
right.
You
can't
have
a
business
without
users
and
depending
on
what
your
application
does,
you
may
need
a
basic
notion
of
accounts
or
something
more
complex.
A
Like
identity
and
since
we're
talking
at
blockchain,
this
means
keys
and
the
management
of
keys
and
the
administration
of
keys,
and
so
we
also
know
that
we
want
users
to
retain
control
of
keys,
because
this
is
very
important
in
order
to
main
decentralization
and
the
self-sovereignty
of
keys
right
and
as
a
layer
one.
If
you
think
about
it,
all
these
layer
ones
have
different
stories
for
user
accounts
right.
A
Taking
responsibility
for
keys
and
accounts
are
hugely
important
right,
both
for
your
internal
administration
of
contracts
and
accounts,
but
for
your
users
as
well-
and
you
don't
want
to
be
outdone
by
competitors
that
offer
a
better
customer
service
or
a
better
user
experience,
and
so
it
would
never
be
reasonable
for
me
to
inform
my
stakeholders
that
we
simply
cannot
recover
user
accounts
or
passwords,
and
so,
if
you
think
about
account
management,
it's
really
essential.
For
business,
so
we
built
this
directly
to
the
protocol
right.
A
We
built
support
for
multiple
key
types,
and
this
reduces
cross-chain
user
account
friction.
We
created
account
delegation
and
a
powerful
permissioning
structure,
and
so,
if
you
think
about
a
platform,
you
really
wanted
to
provide
core
capabilities
that
enable
developers
to
create
features,
and
even
if
you
don't
need
all
these
core
capabilities
today,
you
don't
want
to
get
stuck
with
a
protocol
and
build
against
it
and
invest
in
it.
That
doesn't
going
to
give
you
what
you
need
in
the
future.
If,
at
some
point
in
the
future,
you
need
more
powerful
account
capability.
A
A
And
then
you
have
to
maintain
all
that
code,
because
the
protocol
doesn't
give
you
any
apis
to
do
it
on
chain
and
securely,
and
so
just
because
you
don't
need
it
today
doesn't
mean
you're
not
going
to
need
it
tomorrow
and
it's
a
massive
risk
you
take
on
when
you
build
with
a
protocol
that
doesn't
give
you
these
kinds
of
core
capabilities
right
account.
Delegation
enables
you
and
permissioning
schemes
enable
you
to
create
any
kind
of
permissioning
scheme.
You
want
at
the
protocol
level,
and
this
can
be
features
for
your
users.
A
It'll
enable
you
to
govern
your
your
smart
contracts
and
it'll
enable
you
to
even
grant
support
support,
temporary
access
to
you
to
accounts
if
you
need
to
and
recover
accounts.
A
So
I
certainly
wouldn't
bank
on
a
protocol
that
didn't
give
me
these
things,
and
neither
should
you
so
if
you
think
about
payments,
you
think
about
the
blockchain
being
payments
all
about
payments
and
tokens
and
they
got
to
be
all
buttoned
up
right.
Just
remember
again:
we
want
users
to
sign
transactions.
We
want
this
self-sovereignty
of
keys
right
and
if
you
got
to
pay
for
use
of
the
blockchain,
that
means
your
users
need
to
pay
for
the
blockchain.
So
let's
take
a
look
and
see
how
it
works
on
ethereum.
A
This
is
the
actual
ethereum
workflow
before
you
do
anything
with
with
your
data
before
you
do
anything
with
your
dap.
This
is
what
your
users
have
to
do
so
once
again
right,
if
you
think
about
it,
the
platform
interface
is
bleeding
into
your
application.
You
don't
actually
have
control
over
the
end
user
experience,
because
this
is
what
ethereum
forces
your
users
to
do,
and
there
really
isn't
any
way
for
you
to
work
around
it.
Except
adopting
meta
mask
right,
metamask
helps
with
it,
but
it
still
doesn't
eliminate
it
right.
A
So
you
have
to
integrate
it
into
your
application
ux.
So
imagine.
If
you
have
an
existing
application
that
isn't
browser-based,
you
still
have
to
use
metamask.
You
still
have
to
build
this
entire
user
experience
into
a
mobile
platform
or
any
kind
of
platform.
You
don't
really
have
any
control,
and
so
again
we
have
the
sad
panda
user
story
right.
A
So
you're
telling
your
users
to
go,
find
an
exchange,
buy
some
token
and
make
sure
that's
in
the
right
account
before
you
even
get
started
right
and
if
you
think
about
conversion
funnels,
which
is
what
a
lot
of
businesses
use.
This
is
going
to
sit
right
in
front
of
your
cost
to
acquire
a
customer.
It's
going
to
be
brutal
right,
it's
just
it's
absolutely
a
show
stopper.
A
So
what
we
built
is
we
built
the
ability
for
people
to
design
whatever
kind
of
payment
code
they
want,
and
this
makes
it
possible
for
contracts
to
pay
for
themselves
right.
So,
basically,
your
user
can
sign
up
hold
on
to
their
keys.
They
pay
a
subscription
amount.
You
know
for
a
monthly
subscription
and
you
use
that
for
them
to
fund
their
own
account
their
own
accounts
transactions,
and
you
can
do
this
while
they
still
sign
with
their
own
keys.
A
This
is
massively
important
right
having
flexible
payment
code
and
allowing
contracts
to
pay
for
themselves
makes
the
user
experience
really
really
simple
and
really
really
straightforward.
A
So,
let's
talk
about
building
core
application,
logics
right,
so
we're
talking
about
blockchain
here,
so
we're
going
to
focus
on
smart
contracts,
but
I'll
try
to
educate
you
a
little
bit
on
how
traditional
software
is
built
for
those
of
you
that
don't
know
so.
You
know,
there's
a
lot
of
brand
new
cool
programming
languages
and
developer
tools
in
the
space
to
make
smart
contracting
easier.
But
none
of
these
give
you
any
freedom
to
select
the
tooling
and
workflow.
A
But
casper
is
the
only
one
that
gives
you
a
contract,
runtime
and
a
blockchain
store
that
runs
locally
on
any
machine,
and
so
this
is
hugely
important,
because
if
you
have
a
large
application
architecture,
it's
sending
data
to
this
blockchain
and
this
application
is
created
with
all
of
these
different
tools
like
visual
studio
or
c-line,
as
I'm
showing
here
or
intellij
right.
That
blockchain
platform
needs
to
work
within
that
product,
not
the
other
way
around,
and
so
here
you
can
see.
A
These
are
a
bunch
of
assertions
which
are
local
tests
on
whether
the
contract
was
set
up
correctly,
and
so
I
can
initialize
the
blockchain
locally
on
my
computer,
with
whatever
I
need
for
a
starting
state.
So
if
I
have
an
application
logic,
an
application
infrastructure
that
requires
a
starting
state,
I
can
set
that
up
here
locally.
A
I
don't
need
to
use
truffle
or
anything
else
like
that
and
somebody's
node
someplace
and
try
to
create
a
starting
state
there.
It's
not
what
I'm
going
to
do,
I'm
going
to
build
it
locally,
because
that's
the
way
I
build
my
application
in
my
organizations.
If
anybody
committed
buggy
code
to
the
repository
heard
about
it,
the
entire
that
bug
would
halt
the
entire
pipeline
and
stop
builds,
and
it's
the
same
as
halting
a
big
assembly
line
and
as
the
product
owner
you
want
to
give
customers
guarantees
that
you've
tested
your
code.
A
So
building
an
application
that
fuels
business
requires
that
the
entire
application
be
maintained
and
upgraded.
So
let's
talk
about
how
this
happens
on
ethereum
today
in
ethereum,
you
have
the
proxy
contract
right
blockchains
today,
don't
let
you
upgrade
contracts,
so
what
authors
do
instead?
Is
they
create
a
pointer
to
the
version
of
the
contracts?
A
And
so
this
is
a
hack
right.
That's
a
workaround
of
a
basing
missing
platform
capability
and
that's
to
maintain
software,
so
your
data
and
logic
becomes
separated
instead
of
being
stored
together,
because
you've
got
the
logic,
layer
and
the
proxy
contract,
which
has
the
storage
layer,
because
the
contract
has
to
execute
in
the
context
of
the
proxy
contract.
This
is
the
way
blockchains
work.
A
Just
because
you
update
your
proxy
contract
doesn't
mean
that
the
old
version,
the
logic
is
gone,
it's
still
there
and
someone
who's
savvy
can
still
call
it
and
in
the
event
of
a
protocol
fork,
both
versions
of
your
on-chain
code
exist
on
both
forks,
and
this
is
a
big
deal
for
for
enterprise.
They
don't
want
multiple
versions
of
their
platform
out
there
other
you
know
core
contracts
out
there,
and
this
is
one
of
the
reasons
why
they're
choosing
private
blockchains
is
because
they
need
control.
A
A
You
can
specify
the
protocol
version
of
for
each
contract
when
you
deploy
a
new
version
of
the
contract,
the
system
versions
it
you
can
manage
versions
of
your
contract
and
even
create
access
control,
lists
authorizing
who
can
perform
upgrades
of
your
contract
and,
most
importantly,
you
can
kill
all
versions
of
your
contract.
So
this
makes
sure
that
you
don't
have
multiple
versions
in
the
event
of
protocol
forks.
It
makes
sure
that
you
don't
have
old
versions
of
your
contract.
A
Of
course,
if
you
want
to
have
multiple
versions
of
your
contract,
you
can
certainly
do
that
and
enable
your
customers
to
manually
choose
to
upgrade
themselves
from
version
one
to
version
two
and
at
which
time
your
customers
are
completely
migrated.
You
can
kill
version
two
or
you
can
choose
to
migrate,
your
customers
for
your
customers.
A
Do
you
know
right
now
that
d5
protocols
spend
about
nine
billion
dollars
to
upgrade
or
nine
million
dollars,
sorry
to
upgrade
their
protocols,
because
each
customer
has
to
migrate
themselves
instead
of
just
handling
it
for
them,
it's
a
horrendous
expense
right
and
it's
a
waste
of
money
that
doesn't
need
to
be
wasted.
So
we
believe
that
control
over
the
code
is
absolutely
essential
and
the
best
part
is
you
can
do
this
on
a
public
permissionless
blockchain,
so
you
don't
have
to
forgo
the
trust
that
blockchain
brings.
A
So
let's
talk
a
little
bit
about
how
software's
really
developed
right.
So
software
today
is
really
developed
by
something
called
a
development
operations
pipeline
or
a
software
delivery
pipeline.
So
you
develop
your
software
locally
and
this
is
how
we
develop
the
software
right
now
on
casper
labs
right.
So
if
you
look
here
and
you
hop
over
to
our
casper
labs,
casper
node
and
you
look
at
any
of
our
pull
requests
here,
you
see
these
little
yellow
circles.
These
yellow
circles
mean
that
the
build
is
currently
running.
Zero
of
one
checks
are
okay.
A
This
means
the
check
failed
right.
I
can't
see
a
green
one
yet
because
all
the
green
ones
are
emerged.
But
if
you
look
at
some
of
the
closed
prs
here,
you'll
see
this
green
check.
That
means
two
of
two
checks
are
okay.
So
if
we
dig
in
here-
and
this
is
the
way
code
is
delivered-
you
have
a
pull
request.
You
have
a
review
process,
but
when
you
go
down
in
here
way
down
here,
you
can
look
at
the
checks
here.
A
You'll
see
here
that
we
have
a
bunch
of
workflows.
I
can't
show
you
the
bores
here
right
now,
but
you'll
see
that
there
are
actual
workflows
that
are
running
here.
I
can
show
you
in
an
in
progress,
pull
request
here,
continuous
integration
drone-
and
this
is
required
and
you'll
see
here.
A
A
So
this
is
basically
this
builds
the
software
with
every
time
you
have
code
committed
to
your
repository,
continuous
test
means
right
now
we
have
unit
tests
and
we
have
some
function
tests,
but
we're
also
building
system
tests,
and
you
actually
want
to
have
all
three
tiers
of
testing
happening
in
every
single
commit
right.
Typically,
your
your
integration
test
and
your
performance
test
happen.
What
we
call
nightly
builds
the
unit
tests
will
happen
with
every
commit.
A
Your
system
level
test
could
happen
with
every
merge
and
you
can
have
code
promotion
throughout
this
entire
process
to
say
well,
unit
tests
happen
at
one
level
of
code,
quality
function
tests
happened,
which
is
modular
integration
test.
It
happened
a
second
level
and
system
tests.
There's
complete
integration
tests
happen
at
the
highest
level
and
only
after
you
go
through
your
performance
test.
Do
you
promote
your
code
to
what
you
call
your
interactive
beta
test,
which,
in
our
case
is
test
nets?
A
Where
you
go
through
user
acceptance,
testing
and
then
at
which
point
you
actually
go
into
production,
where
you
do
a
final
level
of
testing,
with
your
development
operations
team
on
a
single
server
that
they
pull
out
of
their
production
ip
pools,
and
then
it
goes
into
production,
and
this
is
the
entire
release
management
process.
This
is
the
way
code
is
shipped
today
you
go
to
salesforce.
This
is
what
they
do.
You
go
to
amazon.
This
is
what
they
do.
You
go
to
facebook.
This
is
what
they
do.
A
Any
of
them
right
call
code
promotion,
and
this
is
what
it
looks
like
in
blockchain
right
and
what
you
actually
want.
Is
you
actually
want
to
put
your
you
want
to
drop
your
blockchain
ledger
into
this
process
and
there's
a
massive
fail
right,
because
blockchain
companies
don't
understand
this
process,
they
really
don't
get
it
right,
and
so,
if
you
attempt
to
snap
this
on
to
this
process,
it's
going
to
look
like
this.
This
is
what
it's
going
to
look
like
right.
A
This
is
the
current
devops,
and
this
is
your
blockchain
devops
here
it
just
it
just
really
doesn't
work,
and
this
is
exactly
how
your
developers
will
feel,
because
what's
going
to
happen,
is
that
those
bugs
are
going
to
leak
in,
because
you're
only
very
intermittently
testing
your
smart
contracts.
You
can't
test
them
alongside
of
your
application
right
and
what
you
actually
want.
A
Is
you
actually
want
to
plug
into
this
continuous
integration
process
and
the
way
you
do
it
is
you
want
your
casper
contracts
to
build
with
the
casper
vm
directly
inside
all
of
us,
and
this
is
what
the
cash
for
contract
build
process
looks
like.
It
runs
in
a
yaml
file
and
yaml
files
run
directly
inside
this
devops
pipeline,
and
if
you
look
at
casper
labs,
you
will
see
our
yaml.
A
Actually,
you
can
take
a
look
at
it
right
here,
it's
directly
in
casper
node.
We
have
a
yaml
file
right
here,
the
drone.yaml,
and
if
you
look
at
it
in
there,
you
will
see
that
we
have
a
building
of
the
contracts
which
we
build
all
of
our
regular
contracts,
just
like
any
other
application
would
build.
A
We
build
our
contracts
right
in
here
cargo
format
and
at
the
cargo
clippy,
and
if
we
find
look
for
a
command
f
here
and
we
say
contracts,
we
will
find
the
cargo
build
for
the
contracts
in
here
as
well.
A
A
A
And
so,
when
you
pour
put
all
these
together
right
with
the
with
the
value
proposition
of
building
on
a
decentralized
public,
permissionless
blockchain,
you
can
actually
unlock
the
real
value
right.
So
this
is
why
we
are
really
the
right
option
for
enterprise
and
we
believe
that
enterprise,
primarily
their
development
operations
team,
is
going
to
build
on
casper
and
they're,
going
to
they're
going
to
want
to
use
casper,
because
it
makes
sure
that
nothing's
going
to
go
down
in
production
right.
A
A
So
next,
let's
talk
about
a
real
world
use
case,
so
for
those
of
you
that
are
familiar,
we're
building
with
ipv
and
we
are
going
to
be
pushing
all
of
the
public
patent
data
onto
the
casper
blockchain,
and
this
is
something
that
is
in
development
right
now.
We've
actually
done
an
initial
prototype
and
ipwe
selected
us,
because
we
offer
real
decentralized
consensus
and
security
to
prove
patent
ownership,
and
we
have
smart
contract
capability
to
manage
contract
compliance,
and
we
have
powerful
account
features
which
simplify
their
blockchain
interoperability.
A
You'll
see
here,
they
still
have
hyperledger
hyperledger
uses,
ethereum
ethereum
type
addresses
and
which
we
can
support.
So
we
can
support
a
single
user
account
and
they
can
basically
create
using
their
existing
accounts.
You
know
accounts
on
the
casper
blockchain.
They
didn't
have
to
create
a
separate
set
of
casper
accounts
for
their
use
case,
and
so
we,
this
is
one
of
the
reasons
why
we
supported
multiple
keys
is
because
we
believe
that
there's
a
lot
of
existing
keys
out
there,
and
why
can't
you
just
use
those
keys
on
casper?
A
Why
create
new
ones
and
make
them
force
them
to
manage
that
complexity?
At
the
application
level
right
there's
no
need.
We
can
support
multiple,
multiple
key
types,
and
we
can
do
it
as
a
soft
fork
right.
It
doesn't
need
to
be
a
hard
fork
to
support
new
encryption,
a
new
key
types,
it's
just
another
account
type.
A
So
we
want
to
empower
software
developers
to
go
and
build
solutions
that
don't
require
anything
new,
because
the
protocol
snaps
right
into
their
architecture
and
they
don't
need
to
wait
until
their
product
or
you
know,
application
is
millions
of
users
to
select
the
right
layer
one.
You
should
build
a
layer,
one
assuming
you're
gonna
have
millions
of
users
right
set
yourself
up
for
success
in
the
beginning,
and
they
can
make
the
right
choice.
You
can
make
that
right,
choice
today
and
capture
a
competitive
advantage
that
blockchain
can
bring
right
by
selecting
the
right
layer.
A
One
that
allows
you
to
develop.
Iteratively
using
agile
principles
is
the
way
to
go
right
and
so
there's
a
significant
risk
of
falling
behind.
If
you
aren't
thinking
way
ahead
right
and
the
decisions
that
you
make
today
are
going
to
decide
who's
going
to
make
the
winners
and
losers
of
tomorrow.
So
for
those
of
you
that
are
interested
in
learning
how
you
can
benefit
from
blockchain
in
your
application
and
architecture
reach
out
to
us,
and
we
can
help
you
build
the
decentralized
future
together.
A
So
that's
the
priso.
That's
really
the
value
proposition
of
why
casper
is
better
for
enterprise,
so
I
hope
you
guys
enjoyed
that.
If
you
have
any
questions
about
it,
I'm
open
to
hearing
questions.
B
C
Yeah
I
made
a
cop,
I
made
a
comment
in
there
as
well
that
all
the
all
the
memes
and
all
the
storytelling
today
to
tie
it
together
with
enterprise
you
know,
are
great.
I
think
this
is.
I
think
the
community
needs
more
of
this
to
to
really
pull
it
all
together,
and
I
think
today
was
great,
so
thank
you
appreciate
it.
A
A
You
know
companies
becoming
successful
using
using
our
technology.
For
me,
the
greatest
indicator
is
how
many
real
businesses
can
leverage
the
value
of
blockchain
using
our
protocol
right
and
how
many
of
those
can
turn
into
multi-billion
dollar
enterprises
right,
and
it
doesn't
need
to
be
a
really
big
application
right.
It
doesn't
need
to
have
billions.
You
know
millions
and
millions
of
transactions
right.
It
needs
to
be
able
to
plug
into
comprehensively
into
the
software.
That's
already
been
constructed.
A
We've
been
building
software
in
the
sas
space
for
over
20
years.
It's
crazy
to
think
that
we're
going
to
toss
it
all
out
and
start
over
with
blockchain
we're
just
not
going
to
do
that
right.
We're
going
to
incrementally
add
value
by
by
dipping
our
toe
in
the
water
and
seeing
those
pieces
where
you
know
blockchain
can
add
a
truss
layer
right.
So
that's
that's
really
really
what
we're
focusing
on
and
that's
the
niche
we're
going
after
awesome
guys,
so
you
know
bring
on
the
memes.
I
love
memes.
A
So
you
know
sad
panda
was
a
great
one
for
my
for
blockchain.
We
definitely
need
to
mimify
more
so
have
a
great
day
and
hit
me
up
with
more
questions
and
keep
the
requests
for
topics
coming
cheers.
Folks.