►
From YouTube: CasperLabs Community Call
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
B
A
B
B
B
So
we
do
this
meeting
every
tuesday
morning.
The
details
are
here
on
github
in
the
casper
labs
governance.
You
can
also
get
to
this
from
the
casper
dash
node
repository
or
the
casper
labs
repository
in
github.
If
you
want
to
join
the
zoom
call
directly
you're
most
welcome
to
join
the
zoom
call
directly
and
ask
us
questions.
B
The
team
has
entered
our
fourth
fourth
sprint
of
the
20.10
release
cycle.
At
the
end
of
this
cycle,
we
will
be
feature
complete
to
launch
the
delta
test
net
with
50
validators.
B
This
release
is
going
to
incorporate
block
rewards,
which
you
call
senior
edge
as
as
well
as
some
security
features,
and
that
is
slashing
and
we
are
going
to
have
a
full
featured
rust,
client
and
an
event
stream
that
will
send
events
to
all
subscribers.
B
This
basically
will
provide
a
stream
of
events
from
the
validating
node,
as
part
of
also
part
of
this
release
cycle,
we're
developing
the
token
standard
for
casper
tokens
and
we're
doing
some
design
work
around
payments
2.0,
which
will
bring
additional,
really
really
cool
functionality
to
the
platform
in
time
for
maintenance.
B
Our
release
candidate
will
be
cut
at
the
end
of
the
sprint
and
it's
going
to
go
into
lrt
testing
and
we
also
have
a
small
alpha,
pre-delta
test
net,
we're
calling
it
charlie
testnet
that
we
are
working
with.
You
know
a
handful
of
validators
on
so
they're
going
to
be
really,
you
know
banging
on
it
right
and
and
helping
us
harden
it.
We're
also
working
with
a
few
companies
to
help
us
harden
that
node.
So
it's
ready
to
go
for
prime
time
our
beta
test
net.
B
We
bounced
it
on
22nd
of
september,
with
52
validators.
We've
got
38
validators
in
sync,
and
the
network
is
healthy
in
finalizing
blocks.
We
will
be
you
know
tearing
this
down
in
favor
of
the
delta
test
net,
which
will
include
a
brand
new
block.
Explorer
it'll
still
have
the
look
and
feel
of
clarity,
but
it
will
be
pointing
to
the
rust
node.
B
B
B
We
had
similar
rates
in
the
charlie
network,
but
they
were
very
short,
bursts
right.
There's
still
a
lot
of
work
to
be
done
on
the
rust
node
in
terms
of
hardening
and
making
it
stable.
We
haven't
done
any
real
performance
work
on
this
node.
So
there's
still
some
work
to
be
done.
You
know,
as
we
run
up
to
mainnet,
our
focus
on
highway
is
on
validator
set
rotation,
completing
the
slashing
we're,
also
completing
bonding
and
unbonding.
B
Do
we
anticipate
this
is
going
to
be
ready
for
delta
testnet,
ashok,
yep,
yep,
okay,
great
so
you'll
be
able
to
participate
and
join
the
network
through
bonding
on
bonding.
It
will
all
happen
by
an
api.
There
won't
be
a
an
auction
interface
to
see
but
you'll
be
able
to
make
an
api
call
to
see
where
you
are
in
terms
of
your
likelihood
of
joining
the
network
and
for
the
delta
test
net
we'll
have
50
slots.
Is
that
correct,
available.
B
50
slots
for
validators
for
the
rust
node
we're
implementing
the
event
stream.
We
are
building
out
a
full-featured,
rust,
client,
we're
enhancing
s-tests
and
the
nctl
that
enable
us
to
spam
the
network
with
workload
generators
at
specific
intervals,
so
we
can
put
it
under
pressure.
B
B
You
know.
The
entire
deploy
prioritization
based
on
gas
prices
that
happens
in
ethereum
is
a
feature
in
the
deploy
buffer.
So
same
thing
here,
right
on
the
api
servers,
we're
doing
some
work
on
status
and
metrics,
and
even
the
deploy
endpoint
right
now
it
just
dumps
a
bunch
of
data
out.
We
need
to
throttle
that,
so
it
doesn't
adversely
affect
the
node
as
an
example
test
in
sre
we're
supporting
the
rust
network
with
the
existing
validators
supporting
beta
test
net
as
needed,
we're
doing
a
lot
of
work
at
automating
the
release
process.
B
I
don't
know
what
the
tl
said.
I
think
it's
network
control
functionality.
B
We're
doing
work
on
clarity,
we're
getting
ready
to
do
a
port
from
the
existing
clarity
over
to
the
rust
node.
There
are
some
different
pieces
that
will
be
available.
You
know
rust.
The
rust
node
is
different
from
the
scala
node
in
terms
of
how
it
works,
and
so
that
it's
going
to
be
pushed
out
into
clarity.
That's
going
to
be
visible
in
clarity
and
then
the
connection
between
signer
and
clarity.
Can
you
talk
a
little
bit
more
about
this
ashok.
A
Yeah,
so
we
have,
we
have
signer
as
a
chrome
extension
available,
and
we
would
you
you
can
actually
show
that
on
your
screen
there
meta
designer.
B
A
Okay,
I
don't
know
it's,
it
has
been
working
perfectly
for
for
me.
So
basically,
there
is
integration
required
between
signer
and
clarity.
It
was
working,
but
we
need.
We
need
some
additional
functionalities
there.
That's
that's
the
work
that
is
going
on,
basically
porting
porting
keys.
That's
clarity
creates
for
an
account.
B
I
would
hope
that
by
building
our
own,
we
can
do
some
really
cool
things
with
it
to
make
it
easy
for
people
to
use,
we
are
doing
a
prototype
for
the
chain
link,
casper
labs,
adapter
alex.
Maybe
in
some
future
meeting
you
can
review
some
of
the
changes
that
we
made
and
why
we
made
them.
C
So
essentially,
we
realized
a
few
weeks
back
that
the
way
that
the
chain
link
ecosystem
works
unfortunately
imposes
some
very
severe
risks
on
us,
and
the
nature
of
the
risk
is
that
the
tokens
handling
tokens
are
highly
volatile
and
it
is
rather
unclear
who,
actually,
you
know,
makes
a
payment
for
the
data
or
you
know
how
flexible
the
recipients
would
want
to
be
with
accepting
payments
for
us,
as
there
is
additional
technical
challenge
of
actually,
you
know
basically
cross
chain
integration,
because
you
would
have
to
make
payments
on
ethereum.
C
So
what
we
sort
of
decided
is
that
okay,
well,
we
are
going
to
you,
know
essentially
use
chain
link
nodes,
but
without
the
ethereum
integration
you
know.
Essentially
it
was
really
like
a
standalone
mode
right
without
any
integration
with
the
chain
ecosystem
and
having
thought
through
that
you
know,
I
realized
basically
that
actually
makes
no
sense
at
all,
because
it's
a
really
hard
problem.
If
you
are
not
constrained
by
you,
know
having
to
understand
or
adapt,
you
know
existing
infrastructure
and
things
like
that.
C
You
know
the
real
problem
is
like
it's
an
incentives
problem
about
getting
people
to
reveal
some
private
information
right,
so
you
he
wants
them
to
reveal
something
that
they
know
about
the
exchange
rates,
and
this
is
the
problems
that
chain
link
addresses
their
white
paper,
but
they
don't
think
really
addresses
in
practice,
except
for
kind
of
a
you
know,
sort
of
implicit
reputation
system
right
in
the
sense
that
you
know
the
nodes
are
long
standing
and
you
know
you
know,
there's
a
line
because
you
can
check.
C
But
you
know
that's
the
reputation
thing
is
a
little
hard
to
implement.
You
know
on
chain.
Basically,
so
it
doesn't
really
solve
the
problem.
So
basically
you
know
without
if
you,
if
you're,
not
solving
that
particular
problem,
we
refer
the
solution
to
the
future.
What
actually
makes
perfect
sense
is
that
okay?
Well,
you
know
you
designed
something
that
you
know
works
like
sheen
like,
but
it's
a
lot
simpler
right.
I
mean
it's
no
longer
some
kind
of
a
general
solution.
C
It's
basically
just
the
link
between
you
and
the
exchange
apis
right
and
initially.
What
that
would
mean
is
that
the
casper
labs
would
simply
operate.
You
know
a
bike
shoes.
You
know
this
is
just
operator
servers
that
you
know
acts
as
a
standard.
You
know
as
a
standard
between
those
exchange
apis
and
there's
a
casper
blockchain,
and
we
would
design
the
contract
system
around
it
on
the
chain
in
such
a
way.
C
Is
that
if
you
wanted
to
participate,
you
could,
and
if
you
don't
care
who
you
are
or
how
you
know
how
you
know
you
get
the
you
know,
exchange
api
information
or
you
run
in
some
kind
of
a
you
know.
Node,
like
you,
don't
care
about
that
right
and
you
could
literally,
ideally
submit
a
transaction
into
the
system,
and
that
would
be
considered
somehow
for
some
kind
of
a
reward
mechanism
right,
and
this
is
where
we
come
back
to
the
heart
problem,
which
is
okay.
C
Well,
how
do
we
get
people
to
reveal
the
truth?
So
essentially,
what
we're
going
to
do
is
that
we
will
design
this
simplified,
simplified
set
of
contracts
that
take
in
and
reward
this
information.
C
We
will
make
the
incentive
part
as
plugable
as
we
can
so
that
we
can
improve
it
later
and
for
opera
operationalizing
this
initially
casper
labs
is
just
going
to
run.
Essentially,
you
know
its
own.
C
You
know
it's
all
nodes
that
will
feed
this
information
into
the
system
and
since
the
upgrades
and
stuff
you
know,
other
people
will
be
able
to
submit
their
information
as
well
and
be
rewarded
rewarded
accordingly,
and
I'm
currently
in
the
process
of
doing
some
preliminary
research
on
the
exchange
apis
on
relevant
parts
of
economic
theory
and
additionally
right
in
the
plan.
That's
you
know,
ticket
by
ticket
going
from
now
to
actually
having
the
system
up
and
running.
B
Nice,
terrific
sounds
good,
so
the
other
things
that
we've
got
working
on
we're
looking
at
the
gas
futures
proposal,
the
cap
for
price
stabilization
didn't
clear
for
because
it
didn't
actually
meet
the
goals,
so
we
believe
gas
futures
will
work
to
solve
the
problem.
Are
you
can
more
convinced
with
this
alex
than
the
other
cep
that
we
had?
I
know
andreas
is
the
one
that
really
put
a
kibosh
on
that.
C
C
You
know
like
a
first
stab
at
the
you
know:
gas
features
thing:
they
think
that
we'll
be
able
to
actually
implement
it,
and
I
think
it
will
work
fine
right,
because
you
know
it
turns
out
that
the
solution
to
the
problem
of
how
do
you
actually
enforce
gas
allocation
may
be
actually
easier
than
we
originally
thought.
C
B
Sounds
good,
that's
good!
I'm
glad
to
hear
it.
What
are
the
specifications
for
the
event
capturing
service.
A
That's
basically
kind
of
creating
intermediate
event
store
so
that
users
can
consume
events.
B
Okay,
can
you
update
that
yeah
contract
runtime,
so
we
are
updating
proof
of
stake
to
get
the
with
the
auction
contract.
This
is
for
bonding
on
bonding.
This
again
is
for
bonding
and
bonding,
and
then
this
is
for
senior
edge.
B
B
Team
and
company
updates.
So
we're
very
happy
to
welcome
george
otterson
full-time
georgia's
working
as
a
part-time
intern.
He
will
be
a
full-time
intern
starting
the
1st
of
october.
We
also
have
a
new
sre
joining
mark.
Lemoyne
he's
going
to
be
working
on
the
s
test
platform
he's
going
to
be
really
focused
on
testing
the
system,
we're
very
excited
to
welcome
him
and
matthew
wampler.
I'm
really
excited
about
matt
wampler
joining
the
team.
For
those
of
you
that
don't
know
who
matt
wampler
is,
he
is
a
giant
in
crypto.
B
Matt
was
responsible
for
writing,
designing
and
writing
the
ethereum
mining
algorithm.
So
if
you
go
to
eth
hash
in
github,
you
will
find
that
mr
wampler
matt
is
the
guy
that
did
all
that
work.
It's
pretty
cool
that
he
has
decided
to
join
us.
He
is
a
friend
of
a
friend
of
someone
on
the
team
and
so
yep.
This
is
matt
right
here,
matthew,
doty,
so
matt
will
be
joining
us
on
monday.
We
are
so
excited.
You
can
hear
the
excitement
of
my
voice
at
having
matt
join
the
team.
B
B
We
are
looking
for
talented
sres
to
join
our
teams
and
we're
also
looking
for
developer,
training
and
advocate
to
join
the
team,
the
one
that
we
had
cut
an
offer
to
did
not
pan
out.
Unfortunately,
life
changes.
So
these
things
do
happen,
but
we're
looking
forward
if
you,
if
you
love
working
with
developers
and
you've,
got
the
technical
chops
to
write
smart
contracts
and
you
love
developing
training
materials
go
ahead
and
apply
at
casperlabs.io.
B
B
Reach
out
to
me
feel
free
to
reach
out
to
me
in
telegram
or
discord
or
on
linkedin
or
any
of
the
channels
where
you
can
find
me
at
mparlikar,
and
let
us
know
if
you're
interested
in
working
with
us,
so
I'm
going
to
do
my
presentation
for
wyoming
hackathon
and
then
I'm
going
to
talk
a
little
bit
about
decentralization.
B
B
It's
coming
through,
okay,
great
yeah,
so
I
presented
this
deck
at
the
wyoming
hackathon,
the
stampede.
It
was
a
devcon.
B
I
was
told
that
the
the
audience
was
fairly
technical,
so
I
kind
of
dove
in
I
think
the
audience
was
maybe
not
as
technical
as
I
had
predicted,
but
I
felt
like
this
is
a
great
topic
for
us
to
talk
about.
It's
really
a
game
changer
in
terms
of
when
you
talk
about
competitive
differentiation
and
the
user
experience
for
developing
smart
contracts.
B
What
we've
built
is
something
that
we
we
will
use.
We
use
internally
right,
so
I'm
just
gonna
give
the
pitch
right.
So
everybody
knows
who
I
am
we
we
are
actually
founded
in
wyoming,
we're
proud
to
be
founded
in
casper
wyoming
when
we
initially
set
up
the
company.
That's
where
casper
labs
llc
was
founded
was
in
casper
wyoming
and
we
founded
casper
labs
to
build
a
blockchain
that'll
scale
right,
and
so
I
for
those
of
you
that
know
about
me.
B
You
know
that
I
come
from
the
web
2
world,
sas
cloud,
there's
lots
of
names
and
I
manage
large
engineering
organizations
and
you
know
both
at
startups,
but
also
companies
like
adobe
and
avalera,
and
today
I
was
I'll,
be
talking
about
the
testing
of
smart
contracts
and
the
importance
of
testing
in
scaling
out
the
adoption
of
blockchain
right.
So
learning
about
a
new
technology
takes
time.
B
You
know
the
blockchain
space
is
really
confusing
right
now,
with
lots
of
different
projects
all
vying
for
developer
adoption,
ours
being
one
of
them
littered
with
new
consensus
protocols
and
languages
and
communities
with
tokens
going
to
the
moon
for
the
26
million
developers
that
are
not
working
with
blockchain.
Yet
the
space
is
pretty
intimidating.
B
There's
96
layer,
one
protocols
out
there
alone
and
we've
got
them
all
here
on
the
screen.
Imagine
putting
your
code
on
a
public
blockchain
that
can
never
change.
You
get
one
shot
to
write
a
perfect
smart
contract
in
a
brand
new
language
on
a
system
where
you
can't
debug
your
this
code
sound
like
a
recipe
for
success.
B
B
The
number
one
value
that
blockchain
is
supposed
to
bring
is
trust.
This
is
why
it's
so
terrific
for
multi-party
transactions
with
no
intermediaries,
but
how
does
one
know
that
on
a
given
chain
protocol
on
a
given
on-chain
protocol
is
defect-free?
I
mean
these
transactions
are
reversible
right.
We
know
that
software
is
prone
to
defects.
B
B
All
in
all,
getting
started
at
blockchain
today
is
no
trivial
matter,
and
the
important
thing
to
remember
in
terms
of
casper
labs
positioning
is
that
we
want
to
scale
blockchain
right
really
broadly,
like
we're
not
just
talking
about
scaling
token
transfers
per
second,
because
that's
a
very
naive
and
simple
way
of
looking
at
scale,
we
want
to
scale
the
adoption
of
blockchain.
We
want
to
scale
out
the
number
of
projects
that
can
use
blockchain.
We
want
to
scale
out
the
development
and
go
to
market
processes
for
blockchain.
B
B
B
You
can
kind
of
think
of
this
as
a
you
know,
you
think
of
a
manufacturing
pipeline.
What
do
they
call
it?
God.
Somebody
help
me
out
here
the
the
the
conveyor
belt.
What
is
that
called
the
big
conveyor
belt
that
you
put
assembly
line?
Thank
you.
It's
an
assembly
line
right,
so
you
have
an
assembly
line
to
build
cars.
You
have
an
assembly
line
to
build
software
right.
B
This
is
how
software
is
built
and
in
order
to
maintain
a
competitive
advantage,
devops
is
essential
to
any
technology
company's
success,
and
this
is
how
software
is
produced
at
scale
today.
So
you
ask:
how
do
you
know
this
meta?
You
know
my
background
is
a
technology
leader
in
a
medium
to
large
enterprise
software
development
organizations,
where
I
focused
on
delivering
high
quality
software
at
scale
fast.
B
B
In
fact,
these
pipelines
are
literally
best
set
up
at
the
beginning
of
a
project
and
evolve
over
time,
and
so,
when
you
see
problems
in
your
software
delivery
problems,
they
usually
happen
in
a
few
places.
One
you
don't
have
a
continuous
build
pipeline
or
you
don't
have
a
production-like
environment.
This
is
really
a
big
problem
here.
B
This
production-like
environment
is
really
where
a
lot
of
the
rubber
meets
the
road
right,
because
your
devops
services
teams
build
a
production
environment
where
they
drop
in
the
software
developed
by
engineering,
and
they
quote,
unquote,
put
it
in
wrappers
and
get
a
production
ready
and
this
production
environment
when
it
starts
diverging
from
your
development
environment.
That's
where
you
start
seeing
bugs
and
then
the
bugs
only
appear
in
production
and
they're
very
hard
to
reproduce
in
development
right.
B
So
the
bigger
your
divergence
between
your
production-like
environment
and
your
development
environment,
the
greater
the
probability
and
problems
with
bugs
right
so
being
able
to
rapidly
iterate
in
a
production-like
environment
is
how
you're
going
to
flush
out
bugs
and
within
your
production
environment.
You
want
to
be
able
to
do
your
performance,
testing
and
integration
testing
in
a
continuous
type
of
test
environment.
This
is
really
really
important
right.
B
This
typically,
this
uat
is
what
you
would
call
a
beta
environment
right
and
if
you
look
at
this
kind
of
carefully
and
I'm
going
into
a
little
bit
more
depth
than
I
did
in
the
hackathon
in
the
presentation,
but
this
interactive
testing
in
the
blockchain
environment.
This
is
your
test
net
right.
This
is
your
test
net
right
here
right.
This
all
here
is
going
to
be
your
internal
test
environment
right,
we're
doing
this
kind
of
continuous
testing
and
continuous,
build
in
in
github
right
now.
That's
what
we're
building
right!
B
B
So
it
seems
like
a
lot
to
set
up,
and
is
it
worth
it?
You
ask
the
efficiencies
that
come
with
devops
are
very
well
documented
or
almost
necessary,
regardless
of
whether
you're
using
the
agile
development
process
or
not.
In
fact,
if
you're
shipping
firmware
it's
even
more
critical,
because
pushing
updates
out
to
firmware
is
really
really
expensive
and
the
risk
with
bugs
is
very,
very
high.
B
Tighter
collaboration
between
your
engineering
teams
and
your
operations
teams
will
give
you
better
uptime.
This
is
really
critical
with
web
2
types
environment.
Automated
testing
is
much
much
more
efficient
and
economical,
all
in
all,
which
gives
you
better
code
faster,
which
in
turn
gives
you
a
competitive
advantage.
B
B
These
ides
are
great.
They
will
let
you
deploy
your
smart
contracts
and
test
them
out,
but
this
really
doesn't
work
when
your
contract
is
part
of
a
larger
architecture,
because
your
application,
if
your
application
is
a
website
or
mobile
interface,
you
will
be
sending
data
to
the
contract
and
you
won't
have
any
guarantees
that
bugs
won't
appear
there
and,
more
importantly,
there
isn't
any
way
to
integrate
this
online
ide
into
your
devops
pipeline,
along
with
the
rest
of
your
application.
B
Here
you
can
see
there
are
multiple
proprietary
tools
being
used
for
development,
blockchain
development,
workflow,
and
none
of
these
are
going
to
support
your
existing
application
pipeline,
and
so
you
can
see
here
this
adapt
continuous
delivery.
This
is
a
one-off
right.
It
only
allows
you
to
test
your
dab
in
a
petri
dish
separate
right,
so
you
can
develop
your
code
using
ganache
and
truffle
and
metamask,
and
these
will
work
with
this.
But
it's
not
going
to
work
with
your
entire
entire
delivery
pipeline.
B
B
Tools
so
before
you
can
get
to
that
point,
you
have
to
build
them
first,
and
the
space
is
riddled
with
a
lot
of
brand
new
programming
languages
and
developer
tools
that
will
help
make
smart
contract
authoring
easier.
But
with
these
tools
you
don't
get
the
freedom
to
select
your
ide
and
the
workflow
you
need.
So,
if
you're
building
your
existing
project
using
intellij
or
c-line,
you
can't
use
those
with
solidity
and
run
and
test
your
contracts.
B
You
might
get
code
formatting,
but
that's
it,
and
this
is
true
for
all
the
blockchain
projects
out
there,
the
newer
and
cooler,
the
language,
less
support
with
ides
and
runtimes
and
the
longer
and
harder
the
path
to
delivering
value.
We
chose
rust
and
wasm
because
we
wanted
our
platform
to
be
accessible
and
open
for
anyone
to
use.
B
We
adapted
our
product
to
integrate
fully
into
existing
development
processes,
and
because
we
went
this
route,
you
can
select
any
id.
You
want
to
use
to
develop
your
smart
contract
that
supports
the
tool
chain
for
the
language
you
want.
So
as
new
languages
get
compilation
targets
for
web
assembly,
we
can
build
libraries
into
our
platform
without
needing
a
cord
fork
or
anything.
B
B
You
can
see
that
I
have
some
assertions
here
on
whether
my
contract
was
set
up
correctly
and,
what's
really
cool
is
I
can
set
up
set
up
my
starting
state
for
the
con
that
the
contract
expects.
Before
I
call
it,
then
I
can
call
the
contract
then
assert
whether
my
contract
did
what
it
was
supposed
to
do.
I
can
also
dump
out
variables
and
return
values
to
validate
whether
the
variables
are
being
set
within
the
contract
correctly,
and
I
can
do
this
all
locally.
B
B
B
So,
let's
stop,
you
know,
take
a
step
back
from
that
and
say:
well,
I'm
okay
using
the
browser-based
ide,
that's
fine
with
me!
I
like
it
I'm
going
to
use
it.
You
still
have
to
integrate
your
smart
contract
into
your
application.
Let's
talk
about
how
this
would
work.
You
say
I
don't
want
to
go
this
other
route.
I
want
to
use
what's
out
there.
B
Well,
we've
talked
about
how
your
application
can
be
delivered
by
the
existing
devops
tools
with
the
protocols
that
are
out
there
today.
The
blockchain
tooling
doesn't
work
with
the
existing
devops
ecosystem.
So
it's
going
to
be
this
one-off,
snap-on
and
the
contracts
will
be
tested
in
this
petri
dish
like
we
talked
about
disconnected
from
the
rest
of
the
system.
So
here's
your
options.
You
can
choose
to
push
your
entire
devops
pipeline
into
a
cloud
system
that
provides
blockchain
devops.
B
You
can
choose
to
run
inside
this
full
production-like
environment.
You
can
run
a
full
blockchain
node.
This
is
this
local
network,
we're
talking
about
here
in
the
corner.
You
would
stick
that
in
here
and
then
you
can
choose
to
pay
gas
fees,
gas
fees
to
run
your
contracts
and
test
nets
at
some
interval.
B
And
then
your
pipeline
is
going
to
look
something
like
this
right,
you're
going
to
have
your
existing
devops
pipeline
that
can
run
really
fast
and
then
you're
going
to
have
this
test
net.
That's
going
to
be
this
hitch
and
it's
going
to
be
slow
and
you're
going
to
spend
cycles
managing
these
dependencies,
and
this
is
not
going
to
scale
and
it's
going
to
take
you
away
from
actually
maintaining
your
smart
contract
and
building
your
application
and
responding
to
your
customer
needs.
B
This
will
work
with
jenkins
drone
or
any
ci
instrumentation
that
you
currently
use
for
your
application
and
any
devops
professional
can
set
this
up
and
it
will
integrate
into
your
existing
pipeline
seamlessly
and,
as
you
can
see
here,
there's
a
large
existing
ecosystem
of
tools
that
facilitate
devops
in
use.
Today.
B
Yaml
calls
the
build
command
and
test
command,
and
this
can
also
work
with
make
or
any
build
tool
which
could
theoretically
call
a
crate
and
a
crate
could
run
all
the
tests.
So
you
can
structure
your
tests
and
your
build
system
exactly
as
you
want
it.
You
just
drop
it
into
yaml
and
you
drop
the
yaml
in
to
any
one
of
these
tools.
It'll
work
with
any
tool,
and
this
is
possible
because
we
provide
this
vm.
An
internal
blockchain
state
store
to
you
as
a
small
runnable
component
that
will
run
on
any
linux
box.
B
It's
not
realistic
to
expect
that
industries
are
going
to
throw
out
all
the
code.
That's
been
constructed
in
the
past
20
years
and
start
over
just
to
use
blockchain
it's
much
much
more
likely
that
they
will
select
specific
features
in
their
larger
product.
Offering
for
blockchain
blockchain
is
really
expensive
to
use.
Every
single
transaction
is
run
a
hundred
or
even
a
thousand
times
for
security,
so
only
key
portions
of
the
existing
code
will
be
candidates
for
blockchain.
This
small
tiny
portion
here
is
the
candidate
for
blockchain
right
and
all
of
this
code.
B
Blockchains
present
the
opportunity
to
streamline
operations
across
many
industries
by
adding
a
layer
of
trust
and
guarantees
in
multi-party
operations.
We
want
to
scale
opportunity
for
everyone,
including
the
many
millions
of
developers
that
have
yet
to
explore.
Blockchain
our
developer
workflows
will
be
familiar
and
support.
You
in
your
success
so
participate
in
the
revolution
with
us,
with
our
future
proof
foundation,
which
will
enable
your
great
idea
to
grow
and
involve.
B
So
we
built
this
tool
for
ourselves.
If
you
go
into
github
and
you
look
at
you
can
look
at
our
our
test
structure,
you
will
see
that
we
we
actually
test
our
smart
contracts.
We
test
our
smart
contracts
with
every
change,
both
in
the
execution
engine
and
changes
in
the
contracts,
and
we
did
this
so
we
always
know
that
the
proof
of
stake
contract
is
going
to
work,
and
so
we
know
this
stuff
works
and
every
time
the
execution
engine
changes,
we
automatically
you
build
a
new
version
of
casper
contract.
B
So
as
this
as
the
nodes
themselves
see
upgrades
to
the
smart
contract,
I'm
sorry
as
the
vm.
Those
are
actually
automatically
manifested
in
casper
labs
contracts.
So
there's
never
a
compatibility
problem
right
if
you're
using
the
latest
version
of
all
the
packages
because
they
are
built
seamlessly
with
every
change.
Programmatically
they're
always
going
to
be
in
sync,
so
you
never
have
the
configuration
management
problem
that
you
would
otherwise
see
you'll
be
able
to
test
your
dapps,
for
you
know
future
facing
protocol
compatibility
well
in
advance
through
this
process.
B
B
B
That's
going
to
have
more
validator
slots
than
we
have
demand
right,
so
we're
always
making
it
possible
for
new
validators
to
join
the
network
and
bond
in
right
through
an
open,
open
auction
process
and
bonding
and
bonding
mechanism,
but
then
also
by
providing
a
validator
date
delegation
right
staking
delegation,
and
we
want
to
empower
people
to
have
self-sovereign
wallets
right,
so
make
it
really
easy
for
you
to
control
your
own
keys
and
use
tools
like
social
recovery
on
chain.
Making.
B
Those
functionalities
really
easy
for
you
to
maintain
control
of
your
keys
and
not
store
them
on
an
exchange
right.
So
this
promotes
more
decentralization
and
open
access,
so
you
can
choose
which
validator
you
want
to
stake
your
tokens
with
right
and
also
making
it
possible
for
adapt
developers
to
choose
which
version
of
the
protocol
they're
going
to
go
with.
B
So
I
like
to
think
that
we've
actually
solved
the
collection
action,
collective
action
problem
with
our
protocol,
because
it's
not
going
to
be
just
up
to
validators
and
minors
to
decide
and
have
a
voice
at
the
table
on
a
given
protocol
version.
So
I
think
that
we
will
be
able
to
fight
whale
formation
on
our
network
through
these
mechanisms
and
we're
going
to
be
paying
close
attention
to
make
sure
that
you
know
we
don't
have
centralization
of
the
protocol
over
time.
B
So
I
think
that's
probably
the
biggest
thing
for
us
to
worry
about
right
now
is
honestly
is
exchanges
becoming
a
central
point
of
control,
and
I
think
the
easiest
thing
to
do
there
is
make
it
really
really
easy
for
people
to
have
self-sovereign
wallets
in
staking
delegation.
So
that's
that's
my
my
bit
about
decentralization.
B
If
you
have
more
questions,
feel
free
to
post
them
on
telegram
and
tell
us
what
you
want
me
to
talk
about.
I
know
a
lot
of
people
are
anxious
about
us
getting
to
mainnet.
I
believe
having
a
secure
and
decentralized
protocol
is
the
most
important
thing
and
and
giving
a
trusted
protocol
to
all
of
you
is
the
best
way
we
can
honor
the
trust
you've
put
in
us.
B
It
we're
not
here
to
do
a
pump
and
dump
we're
not
here
to
make
a
quick
buck,
we're
here
to
build
something
that's
going
to
last
and
persist
and
be
trustworthy,
and
we
take
our
job
very
seriously
and
we
take
the
trust
you
placed
in
this
very
seriously
with
great
humility
and
a
dedication
to
build
what's
right,
and
so
we're
not
going
to
rush
this
out,
no
matter
how
much
we
get
pressured
into
it.
We're
going
to
build
something,
that's
correct
by
construction!