►
From YouTube: IOHK | PMO Project Shelley August 2018 Update
Description
In this update, IOHK project manager Liz Bancroft-Turner provides a Project Shelley update. She explains the Shelley Project and its overarching goal, how it's broken down into manageable workstreams and outlines the key deliverables.
https://iohk.io/team/liz-bancroft
--
Input Output
See more at: https://iohk.io
Get our latest news updates: https://iohk.io/blog/
Meet the team: https://iohk.io/team/
Learn about our projects: https://iohk.io/projects/cardano/
Read our papers: http://iohk.link/paper-ouroboros
Visit our library: https://iohk.io/research/library/
In the press: https://iohk.io/press/
Work with us: https://iohk.io/careers/
A
Hello,
everyone-
this
is
Liz
Bancroft
Turner
from
IOH,
came
here
today
to
give
you
August
update
for
project
Shelly.
So
in
today's
Jen
tell
give
you
a
recap
of
why
we're
doing
this
project
and
highlight
the
three
main
rocks
Ashima
start
with
deliver
decentralization
and
provides
an
update
of
the
work
we've
carried
out
for
the
month
of
August.
So
as
a
reminder
for
those
of
you
not
familiar
with
Shelly,
this
is
what
the
project
is
all
about,
so
the
goal
of
Shelly
is
to
come
fully
decentralized
and
autonomous.
A
There
are
three
main
work
streams
that
will
help
us
deliver
decentralization.
They
are
incentives,
delegations
and
networking.
So
if
the
incentives,
this
is
about
encouraging
stakeholders
to
follow
the
protocol
and
assure
that
the
system
runs
smoothly
for
delegation.
This
is
about
allowing
users
to
hand
over
their
right
to
sign
blocks
to
a
third
party
and
for
networking
this
is
about
enabling
the
infrastructure
to
support
decentralization.
A
So
against
our
plan,
we
have
split
out
the
deliverables
into
three
core
project
phases.
They
are
research,
design
and
implementation,
so,
starting
with
the
research
we've
successfully
completed
this
phase.
So
there
are
two
deliverables
here:
they
are:
the
incentives
and
the
delegation
research
papers,
so
the
center's
research
paper
was
submitted
to
whine
end
of
July,
and
the
delegation
paper
was
recently
submitted
to
n
DSS
there's
an
e
print
version
of
the
incentives
paper
on
archive,
and
the
paper
is
also
available
from
our
website.
We're
expecting
to
have
a
delegation
research
paper
ePrint.
A
So
please
watch
out
for
this.
So
moving
on
to
the
design
phase,
we're
still
in
progress
with
a
number
of
deliverables
here,
starting
with
the
delegation
design
spec.
So
here
we
merge
the
incentives,
design
document
into
the
delegation,
design
spec
we're
in
the
final
stages
of
completing
the
design.
Spec
we've
had
a
number
of
internal
reviews
and
updates.
Throughout
the
month
we
have
recently
decided
to
change
how
we
decentralize
in
there.
At
the
moment,
more
blocks
are
crated
by
one
of
eight
core
nodes.
A
Once
the
system
is
fully
decentralized,
they
have
to
be
created
by
independent
nodes
for
the
security
of
the
coordinate
protocol.
It's
important
that
not
too
many
people
miss
the
opportunity,
crater
block
when
it's
their
turn.
So
therefore,
when
going
from
centralized
to
footage
decentralized,
we
must
make
sure
that
the
blocks
are
still
reliably
produced.
A
So
we
therefore
plan
to
have
a
gradual
transition
phase
so
in
which
we
slowly
give
control
of
block
creation
to
the
world
so,
while
still
being
able
to
monitor
sufficiently
many
blocks
are
being
produced
and
while
still
being
able
to
guarantee
system
security.
So
moving
on
to
the
detailed
technical
implementation
plan,
we've
been
working
on
this
over
the
last
few
weeks
and
we
have
a
number
of
work
packages
being
written
across
core
wallet
front
and
back-end.
A
We
expect
this
to
be
great
in
the
next
week
or
so,
and
then
we'll
translate
these
into
tasks
for
the
developers
to
go
and
implement
with
the
delta-q
measurements
design
in
July,
we
validated
the
design
assumptions
with
a
set
of
real
world
experiments
between
AWS
data
centers
worldwide.
This
gives
us
a
greater
confidence
that
our
design
targets
should
support
high
performance
at
world
scale.
A
Communication
protocol
design
we've
been
working
on
expressing
a
protocol
for
blockchain
exchange
as
x-cubed
executable
Haskell,
so
that
the
same
program
can
run
in
production
and
in
simulation,
so
moving
then
on
to
test
nets.
So
we're
still
working
on
how
we
deliver
test
nets
so
we're
still
in
the
early
stages
of
defining
how
the
test
net
will
operate
for
Shelly
I'm,
currently
working
on
the
design
principle
mechanisms
of
how
we
go
about
the
exercise
of
transitioning
from
bioone
to
shelly
test
net.
A
So
we
are
currently
defining
and
creating
a
deployment
plan
that
addresses
the
operational
requirements
and
a
high-level
test
plan
and
as
well
as
known
unknowns
and
collaborating
with
the
various
teams
to
produce
those
answers
and
solutions.
So,
from
a
DevOps
point
of
view,
they
are
defining
what
those
supporting
scripts
look
like
to
deploy
the
different
parts
of
Shelly.
A
For
example,
the
state
pool
infrastructure
they'll
need
infrastructure,
so
they'll
need
instructions
from
the
working
guys
on
how
this
is
going
to
look
and
need
some
architecture
to
do
diagrams
before
they
can
see
what
that
looks
like
and
how
the
public
will
use
it.
So
we'll
get
a
better
sense
of
that
towards
the
end
of
this
month.