►
From YouTube: Cardano Monthly Update - April 2020
Description
Tune in for our new LIVE monthly show (recorded 30th April 2020), where we bring you all the latest Cardano development news. Join hosts Tim Harrison & Aparna Jue, and members of the IOHK Cardano team, to hear their updates from the project. Updates /guests include:
- IOHK CTO, Romain Pellerin introduces himself and talks about his first months on the job and how he’s been recalibrating the way we deliver our software
- There's an update from Darko on the first month of the Daedalus Flight program and the recent launch of Daedalus 1.0.0
- Charles Morgan, IOHK director of cybersecurity gives a rundown of the recent report from R9B and why independent audits are important to us, our future users and the wider blockchain industry
- Nick Nayfack has an Adrestia update and a quick demo, as well as giving us a quick tour of our GitHub repos
- Kevin Hammond shares the latest info on the rollout of the Shelley Haskell testnet, as we approach the early ‘Friends & Families’ phase in May
0:35 Aparna Jue, Product Director for Cardano
1:10 What has been happening?
4:07 (TIM HARRISON) Can you tell us more about the work that is being done with the brand refresh?
5:55 I want to share a quote from one of our users regarding Flight.
7:07 Setting up people to be successful is a part of our DNA at this point.
8:15 Romain Pellerin, CTO
8:40 Introduction of Romain Pellerin.
10:30 What are your first impressions of coming into the Cardano project?
11:20 What is the technical focus at the moment?
12:37 What are the processes that you are putting into place now to improve delivery?
14:34 Charles Morgan, Director of Cybersecurity.
14:52 Why do we need to bring outside security auditors on?
16:00 How do the external and internal security auditing teams work together?
18:27 What is the difference between static and dynamic testing?
19:52 What is happening with the next audit for Shelley?
20:29 Will we share the results of the next audit?
22:00 Darko Mijic Product Manager for Daedalus
22:24 Can you tell us about the new Daedalus release?
23:21 It was a successful release and the numbers confirm this.
24:48 How does Daedalus Flight play into the strategy of Daedalus as a product?
26:49 How do you plan on bringing the community into Daedalus long term?
27:55 Can you tease anything new from the Daedalus roadmap?
29:05 Kevin Hammond, Formal Methods\Haskell Engineer
29:40 Can you summarize the content of the Shelley Haskell Testnet blog you recently put out?
31:09 When will the first phase of the Haskell Shelley Testnet begin?
31:54 What is happening on May 11th?
33:01 We’ll be working with feedback from the initial launch which is similar to the Flight program and the ITN.
33:31 The Road to Shelley presentation.
36:29 Main Cardano Components.
36:56 Cardano testnets and mainnet.
38:25 Shelley Haskell testnet phases post pioneer.
39:40 What are some of the things that we’ve learned from the ITN that we’re bringing into the Haskell Shelley testnets and beyond?
40:55 After Shelley will stake pools continue to be registered by the Cardano Foundation?
42:30 Will stake pools that have built their identity on the ITN be able to maintain it going forward?
42:50 What can you tell us about the k-parameter and the pledge?
44:20 What is pledging?
46:05 Can you tell us what you are looking for in terms of stake pool operators to test out the initial phases of the Haskell Shelley testnet?
48:36 Nick Nayfack, Product Manager for Adrestia
48:40 Is Adrestia live now?
48:55 What is Adrestia?
49:40 Can you tell us more about how you plan on using these tools?
50:42 Presentation on Adrestia.
52:10 We have the Adrestia user guide.
54:16 Do you have any additional support channels?
55:40 What is the estimated delta between Shelley and Goguen?
57:30 Can you talk about the progress of education?
58:20 What will be happening with the IOHK Summit?
59:40 How do you plan to market Cardano to the masses once Shelley is deployed?
A
I
machine
well,
I
am
I'm,
surely
being
a
good
hello.
Everybody
I
welcome
to
the
monthly
updates
great
to
have
you
back
here,
lots
of
people
coming
again.
We've
got
462
people
in
the
line
there,
which
is
absolutely
fantastic.
We
hope
to
grow
this
from
strength
to
strength
over
the
months
ahead.
So
joining
me
is
a
partner
who
you
all
know
very
well.
By
now
it's
been
it's
been
a
busy
month.
It's
been
a
difficult
month
and,
as
usual,
all
our
thoughts
go
out
to
everybody
who's.
A
Having
a
tough
time
at
the
moment,
with
the
the
worldwide
Kovas
situation,
we've
been
keeping
business
as
usual
as
best
we
can,
but
we
recognize
that
people
are
touched
in
different
ways
by
this.
So
best
of
luck
to
you
if
you're
going
through
troubles
at
the
moment,
but
thank
you
for
your
continued
support
on
this.
So
upon
a
a
busy
week,
a
busy
month
in
the
world
of
card,
our
know
what's
been
happening
right.
B
It
does
feel
like
a
week
Tim.
So
no
blame
no
blame
on
that.
One
yeah!
You
know
what
actually,
let's
address
the
big
topic
here.
We
are
here
really
for
Shelley
right,
so
this
monthly
update
is
for
our
community
to
understand
where
we
are
in
Shelley
and
I'm
not
going
to
talk
about
it
right
now,
but
Kevin
during
Kevin
segment,
who
is
responsible
for
the
node.
We
will
definitely
touch
it
on
that,
so
just
that
you
know,
keep
tight
guys
we'll
be
getting
there.
B
So
what's
been
happening
this
past
month,
Wow,
so
there's
quite
a
bit.
Let
me
just
talk
about
four
of
the
major
areas
and
it's
going
to
be
pretty
exciting
for
a
lot
of
people
because
of
the
progress
we've
made
in
many
of
the
different
areas.
Since
the
last
time
we
were
here
March
31st,
so
there
is
obviously
overall
work.
B
That's
been
done
on
the
PWC
workshop,
so
the
overall
strategy
for
card
on
o,
which
not
only
includes
the
vision
but
setting
up
the
roadmaps,
setting
up
this
continuous
delivery
platform
for
features
that
are
allowing
for
more
parallel
work
streams
on
the
roadmap.
So,
instead
of
the
whole
era
based
roadmaps,
you
know
I
talked
about
how
we
would
become
more
agile
and
have
more
innovation
and
more
features
that
keep
coming
out
and
what's
been
happening.
B
Firing
was
obviously
one
of
the
areas
we
pretty
well
and
we
were
successful
with
the
whole
reboot
and
Daedalus
the
flight
concept,
getting
a
lot
of
the
community
feedback
in
there
and
doing
the
whole
flight
area.
Darker
is
going
to
be
touching
a
little
bit
about
that
and
we've
done
an
excellent
job
there
and
I'm
actually
going
to
talk
a
little
bit
about
the
tech
support
piece
of
that
as
well.
B
Now,
you're
gonna
see
that
this
highly
committed,
IO
HK
group
of
people
that
are
working
on
Cardno
will
be
touching
base
with
our
community
a
lot
more
especially
through
these
updates.
So
you
guys
will
be
dates.
What
we're
working
on
as
a
state
of
our
roadmaps,
but
also
Charles,
does
his
visionary
ama's,
and
he
does
provide
a
lot
of
information
there
and
from
Tim
and
the
marketing
and
communication
standpoint
to
be
doing
a
lot
of
blog
post
like
Timmy.
You
already
do
that.
The
next
piece
that
I
want
to
touch
on
is
the
tactical
work.
B
So
we
said
we
were
going
to
get
a
July.
How
are
we
doing
that
so
getting
all
that
research
and
making
it
into
a
delivery
mode
firing,
like
I
told
you
is
the
first
step
with
that?
Shelly
is
obviously
the
second
and
we
will
introduce
here
on
the
show,
our
CTO
Roman
and
we'll
be
talking
us
through
how
we're
doing
that
for
Shelly
as
well.
It
is
a
lot
of
works.
B
Not
only
is
it
Shelly,
but
we're
also
looking
at
Gogan
and
Nellie
get
Gogan
up
into
the
mainstream,
but
also
promotion
of
the
underlying
us
piece
of
card
on.
Oh
and
you
guys
are
all
fans
of
us.
You
know
what
we're
vision
is
you
know
why
we're
doing
this,
the
whole
scientific
methodology
and
evidence-based
engineering?
How
that
sets
us,
apart
from
everything
else,
so
how
many
message
that
and
how
do
we?
How
do
we
show
that
to
the
world
that
we
are?
B
A
Well,
I'm
a
child's
mission.
It's
a
few
times,
we've
been
collaborating
with
McCann
over
the
last
few
months
to
I,
guess
really
refresh
the
brand
refresh
the
Cardona
brand
on
the
one
hand,
but
also
and
I
think
equally
important
create
what
we're
calling
a
single
source
of
truth.
Because,
ultimately,
you
know
the
project
has
grown
organically
over
a
period
of
years.
And
yet
what
hasn't
happened
is
that
the
resources
available
to
the
community
and
the
resources
available
to
the
developer
community
as
well
having
this
kept
pace
with
that.
A
So
we've
ended
up
with
a
situation
where
really
we
have
a
web
presence
that
doesn't
represent
properly
where
we
are
now.
So
it's
been
a
massive
focus
for
me
and
my
team
over
the
last
two
or
three
months
really
working
with
McCann
very
collaboratively
around
refreshing,
the
Cardno
brand
updating
the
website
creating
new
copy,
creating
new
documentation,
whether
that's
technical
documentation
or
more
kind
of
informational
documentation
from
other
general
sort
of
ADA
holder.
A
That's
been
a
massive
focus
for
us
over
the
last
couple
of
months
and
will
continue
to
be
for
the
next
few
months
as
well
and
ongoing.
So
it's
an
entirely
new
process.
We've
been
in
place,
we've
got
a
great
relationship
going
with
McCann
and
working
with
a
card
on
our
foundation
very
closely
with
those
guys
as
well,
and
the
Mojo
as
well
I
mean
it's
been
very
much
a
collaborative
effort,
so
people
can
expect
to
see
the
fruits
of
that
work
in
due
course,
as
well
as
charles's
said.
Absolutely.
B
Tim
you,
you
guys,
have
been
doing
a
great
job,
so
I've
been
I've,
been
in
the
trenches
with
them
and
and
kind
of
reviewing
and
taking
a
look
at
some
of
the
work
and
I'm.
So
inspired
and
I
know
that
you
guys
will
be
as
well
once
we're
able
to
unveil
it
for
everybody.
So
the
speaking
of
the
community
engagement,
that's
another
big
piece
flight,
as
you
know,
was
a
pretty
much
a
success
and
how
that
how
that
whole
concept
took
us
to
production
version,
Daedalus
and
I.
B
Just
want
to
I
want
to
give
a
shout
out
to
our
tech
support
needs.
Victor
is
our
tech
support
lead
in
our
tech
support
group
is,
does
such
a
great
job,
and
it's
not
only
Tech's
worry
about
DevOps
and
QA
as
well,
that
are
that
are
holding
down
the
front
lines
when
we
launch
something
like
a
flight
program
and
I
want
to
just
share
a
quote
from
one
of
our
users
regarding
flight.
B
It's
he
said
been
running
flight
since
launch
new
version
downloaded
and
installed
main
screen
opened
up
immediately
and
synced
in
a
matter
of
minutes,
running
windows,
brilliant
job
team.
Let's,
though,
card
on
oh
and
I've
got
quite
a
few
of
those,
so
I
just
want
to
give
a
shout
out
to
the
team.
That's
really
done
a
great
job
here.
B
Windows
was
kind
of
a
problem
child
for
us
and
and
we
fix
it
in
a
matter
of
a
few
weeks
and
the
number
of
flight
candidates
we've
done,
Daedalus
100
that
we
have
about
263
tickets
that
have
come
in
already.
Ninety
four
have
been
solved
in
the
past
five
days.
There's
we
get
these
reports
every
day
and
it's
kind
of
a
closed
loop
feedback
with
with
the
tech
support
teams
with
our
groups
with
Darko's
group
in
order
to
be
able
to
get
you
guys,
a
better
product
bringing
in
the
community.
So
this
is.
B
This
has
been
wonderful
on
that
I
hope
you
guys
are
seeing
this
seeing
that
as
well
and
then
finally,
is
a
segue
kind
of
into
romance
piece
is
setting
up
the
organization
I
mean
as
as
leaders
of
Cardno
every
every
portion
and
every
portion
of
what
we're
doing
it's
successful
people
it's
at
the
end
of
the
day
in
order
to
get
a
successful
product.
It's
the
underlying
organization,
people
that
that
are
a
part
of
it
and
setting
that
up
setting
the
processes
for
them
to
be
successful.
B
That's
all
very
much
a
part
of
our
our
DNA
at
this
point
and,
for
example,
Tim
talked
about
Cardno
Docs
and
what
we're
doing
there
cleaner
documentation,
a
lot
of
you
guys
have
asked
about
it
and
rented
threads
and
some
of
the
others
or
what
are
you
guys
doing
about
documentation?
And
you
know:
where
can
we?
Where
can
we
see
it,
there's
a
lot
of
cleanup
that
needs
to
happen.
We.
B
We've
been
taking
stock
of
that
and
and
and
where
we're
putting
that
together
and
you'll
see
a
little
bit
of
that
at
the
end,
also
with
address
via
what
we're
doing
there
with
the
github
repositories
and
then
also
roadmap
communications.
So
you've
seen
our
roadmap
I
told
you
that
we
will
be
doing
some
changes.
We
had
a
user
suggested
progress
Mars
on
certain
things,
love
that
idea,
so
we're
definitely
planning
around
with
how
we
can
communicate
this
better.
B
But
our
focus
right
now
is
getting
Shelley
and
getting
you
guys,
Shelley
and
then
getting
rid
of
the
platform
up
and
running
that
way.
So
piece
of
that
is
in
the
delivery
stage
and
with
that
Tim
I'd
like
to
bring
on
the
show
our
CTO
our
new
CEO,
who
now
feels
like
he's
been
here
for
years,
just
like
myself,
Romano.
A
C
A
So
Ramon
we
partner
and
I
were
just
talking
about
in
the
within
IOH.
Kaiser
is
a
professionalizing.
It's
moving
from
a
project
to
a
product,
delivery
organization
and
I.
Think
there's
been
some
fairly
significant
moves
in
the
software
side
as
well
and
I
think
you're,
obviously
a
big
part
of
that,
both
now
and
going
forwards,
but
brick
before
we
get
onto
that.
Perhaps
you
can
just
maybe
introduce
yourself
a
little
bits
of
people.
You've
been
with
the
business
a
couple
of
months
now,
something
like
that
happens
a
little
bit
about
how
you
arrived.
C
A
C
Was
the
really
blown
away
again
by
completed
the
competency
and
dedication
of
the
object
team?
Everyone
is
a
very
focused,
open,
I,
think
I
I
think
it's
the
most
innovative
company
I've
been
involved
in
and
we
were
extremely
active.
I
mean
more
than
300
public
repositories
on
github
3,000
commits
this
week,
if
I
according
to
calendar,
dates
dot-com.
C
A
So
what
is
what
are
some
of
the
measures
we
spied
last
month
for
the
partner
about
the
kind
of
increased
cadence
and
the
idea
of
Sprint's
and
the
way
that
we're
kind
of
managing
the
software
development
and
delivery
process?
What
are
some
of
the
processes
that
you're
putting
into
place
now,
and
also
focusing
on
in
the
near
future,
to
continue
kind
of
improving
our
our
delivery?
So.
C
We
are
pushing
for
agile
development,
we've
bee
weekly
release,
cadence
for
most
of
our
components,
and
we
are
going
to
work
on
defining
and
specifying
early
milestones
every
quarter,
for
example,
but
way
ahead
of
time.
So
everyone
can
live
better,
that's
what
we
are
trying
to
put
in
place
right
now,
so
we'll
continue
to
bring
your
new
talents
to
the
company,
because
this
is
a
very
impressive
work
and
the
goals
are
very
high,
so
we
need
a
we
need.
C
A
A
Does
my
dirty
minds
but
I
just
like
putting
on
the
French
accent,
you
know
hey,
it's
just
me,
okay!
So
next
up
one
of
the
other
pieces
of
news
this
past
month,
which
a
lot
of
you
responded
to
was
around
our
code
audit,
the
security
code
audit
that
we
we
delivered,
and
we
shared
that
with
you.
As
you
know,
we
try
and
be
as
transparent
as
we
can
as
a
business
as
a
project,
and
so
that
was
something
that
we
shared
publicly
with
everybody.
A
But
a
few
questions
came
up
and
we
thought
let's
get
Charles
different
Charles
this
time
this
is
Charles
Morgan.
Who
is
our
director
of
cyber
security
and
we
thought
let's
get
Charles
on
directly
and
Anne,
asked
Charles
Charles.
We
will
do
formal
methods,
we
use
papers.
We
have
some
of
the
foremost
scientific
experts
in
the
world,
helping
us
build
card
honor.
Why
do
we
need
to
bring
somebody
else
in
for
for
an
external
code
audit?
What's
what's
it
all
about?
It's.
D
Actually,
a
really
good
question:
it's
pretty
much
analogous
to
writing
an
essay
when
you're
really
familiar
with
your
own
writing,
it's
very
easy
to
overlook
what
you
have
written.
It's
easy
to
miss
mistakes.
You
your
mind
knows
what
you
wanted
it
to
say
what
you
wanted
to
do,
and
this
really
kind
of
carries
over
to
what
we
see
in
the
coding
world
as
well,
and
it's
really
important
to
get
the
fresh
eyes
in
there
use
fresh
eyes.
D
Take
a
look
at
the
code
that
don't
have
a
vested
interest
in
that
particular
code
base,
but
have
the
expertise
you
couple
that
with
some
automated
tools
to
help
them
see
the
overall
big
picture
of
how
everything
fits
gather
and
you're
gonna
find
most
all
of
those
issues,
and
it's
really
the
smart
and
a
responsible
thing
to
do.
If
we're
putting
something
out
that
controls
people's
for
investments,
we
want
to
make
sure
that
their
money
is
as
safe
as
we
can
make.
Yeah.
A
D
D
He
leads
a
team
that
does
a
almost
continuous
routine
in-depth
audit
on
everything
that
comes
out
or
development
they're,
looking
for
the
way
that
we're
implementing
the
code
as
compared
to
the
formal
methods
and
proofs
that
we
have
written
and
it
just
basically
make
sure
that
everything
that
we're
doing
is
is
basically
mathematically
proven,
so
we're
going
from
the
formal
proof
to
the
code.
Yes,
it's
implemented
correctly
or
making
sure
the
cryptography
is
in
place.
Okay
after
it
comes
out
of
there.
D
Of
course,
we
have
our
QA
team
who's
going
to
do
functionality,
testing
on
every
little
incremental
release,
that's
coming
up
and
making
sure
that
our
end
users
are
going
to
have
a
good
experience
with
what
they're
running
as
far
as
not
having
an
issue
with
clicking
on
a
button
and
a
not
working
form
or
anything
like
that.
And
then,
of
course,
after
that
we
have
another
audit,
that's
led
by
my
team
and
what
we
do
there
is
we
actually
take
a
look
at
all
the
pull
requests
that
have
been
against
open
issues.
D
We
look
at
outstanding
issues
that
might
still
be
out
there
that
we
haven't
had
a
chance
to
address
yet
and
we
take
a
look
at
any
other
additional
functionality.
That's
been
added
since
the
last
real
exemple
since
the
last
major
erotic
that
we've
done,
and
so
we
can
get
a
good
feel
that
what
we're
going
to
push
out
on
an
incremental
release.
That's
good,
and
then
after
that,
that's
where
we
really
come
into
the
idea
of
having
the
external
third
party
audit.
D
A
I
guess
the
the
biron
reboot
was
a
very
significant
release
in
its
own
way,
and
Shelley
will
be
an
even
more
significant
release.
So
one
of
the
things
that
came
up
is
this
difference
between
the
static
and
dynamic
testing.
I
understand
that
was
static,
testing
with
the
buyer
and
reboot.
What
tell
us
a
little
bit
about
that
and
how
that's
shaping
up?
Okay,.
D
Static
and
dynamic
testing
is
basically
what
is
being
audited.
Okay,
it
all
pertains
to
the
same
codebase,
the
static
analysis.
You
have
experts
and
the
programming
languages,
taking
a
look
at
the
way
the
code
is
written
and
the
way
that
it
is
called
the
routines
that
are
used.
Everything
from
how
your
keys
are
managed
memory
space
is
managed
and
everything,
but
it's
really
looking
at
it
static,
so
think
of
it.
You
could
almost
look
at
it
print
it
on
a
piece
of
paper.
D
That's
what
you're
already
when
you
get
into
dynamic
audits,
that's
where
it
gets
to
be
a
little
bit
more
interesting
they're,
not
only
taking
a
look
at
the
static
portion
of
it.
They
do
that
initially
to
make
sure
they've
got
a
grasp
of
how
the
system
is
supposed
to
be
working,
and
then,
on
top
of
that
they
actually
start
up
live
notes.
They
start
up
their
own
network,
their
own,
basically
their
own
test
net,
so
they
they
can
attack
it
very
much
like
a
hacker.
Would
they
try
and
do
penetration
testing?
They
look
for
vulnerabilities.
D
A
D
We've
got
one
that
we're
actually
we've
got
requests
out
right
now
for
proposals
to
get
a
good
grip
on
and
we're
expecting
that
to
probably
be
coming
out
so
far.
We're
expecting
that
Auto
probably
takes
somewhere
between
two
to
three
months
and
we're
actually
waiting
for
a
particular
piece
of
the
codebase
to
get
done
right
now,
and
it
has
to
do
with
the
peering
selection
in
in
the
node.
So
once
we
have
that
in
place,
we'll
actually
start
that
next
audit
and.
D
The
idea
behind
doing
code
audits
is
really
it
really
helps
put
out
a
better
assurance
who
are
that
that
we're
putting
about
a
better
product
out
there?
It's
it's
having
an
order
to
come
in
and
take
a
look
at
what
we've
done,
they're,
putting
their
name
and
the
reputation
on
the
line
saying
that,
yes,
this
is
good
code,
so
putting
it
out
there
doing
the
audits,
it's
responsible.
We
don't
want
want
to
keep
that
transparency
going
so
that
they
can
see.
This
is
what
was
already.
This
is
what
was
found.
These
were
the
issues.
D
This
is
how
they
mitigated
them.
This
is
you
know
if
the
auditors
final
to
take
on
yes,
everything
we
found
has
been
mitigated.
What
that
does
that
transparency?
It
really
makes
it
possible
so
that
people
see
we're
not
trying
to
hide
anything
under
the
rug,
we're
fixing
every
issue
we
find
as
quick
as
we
can
do
it
and
we're
giving
them
the
best
product.
We
can
contest.
A
E
A
E
So
we
have
five
release:
candidates
of
five
candidates
for
Daedalus
1.0
release
and
then
the
final
release
all
in
25
days,
and
we
also
produced
a
lot
of
supporting
content.
So
every
release
had
release
notes
and
then
we
made
instructional
video
on
installation
and
what
migration
and
support
portal
articles
and
I
would
really
like
to
take.
Everyone
who
worked
on
Daedalus,
especially
Daedalus
team,
led
by
Nico
Nico,
did
an
amazing
job
and
special
thanks
to
Amy
in
unico
who
did
a
lot
of
last-minute
copy,
proofreading
and
translation,
and
they
were
amazing
yeah.
E
E
Yes,
we
were
waiting
for
this
for
many
many
years
and
the
the
rivet
was
done
we've
by
for
18
months.
It
was
a
very
successful
release,
so
the
numbers
confirm
this,
so
we
had
2500
unique
downloads
for
that
one
all
and
only
268
support
portal
tickets
as
a
comparison
like
with
major
releases
of
the
other
was
previously,
we
had
thousands
even
2000
tickets,
with
major
version
released
and
a
lot
of
these
tickets
were
actually
for
unsupported
versions
of
the
operating
systems.
Unfortunately,
Windows
7
and
8
zero
are
not
supported.
E
Users
need
to
have
Windows
8.1
or
newer
200
O's,
and
it's
not
very
good
idea
to
run
that
also
none
supported
version
Windows
is
just
not
secure.
So
basically,
we
only
have
a
handful
of
issues
and
issues
are:
some
users
cannot
complete
synchronization,
and
this
is
already
fixed
in
the
upcoming
one,
eleven
zero
version
of
the
Cardano
node
and
that
will
be
released
next
version
of
the
O's.
E
E
I
think
the
flight
was
the
key
to
success
of
the
I.
Was
we
had
two
thousand
unique
donald's
for
fraud
candidates
and
we
don't
least
100
support
tickets?
It
managed
to
basically
resolve
all
major
issues:
they're
connecting
issues,
network,
synchronization
issues,
crashes,
issues
we
solved
all
of
them
before
releasing
one
of
to
everyone
and
we'll
continue
to
have
a
little
fight
releases
like.
Let
me
just
cover
how
the
release
process
will
look
going
forward.
E
One
always
be
specific
because
we
wanted
to
have
Cardinal,
then
heard
an
award
as
in
completely
new
Maryam
written
dependencies
out
in
the
wild
in
testing
for
a
while.
So
I
took
us
25
days
to
reach
the
final
version
and
we
were
actually
adding
new
features,
which
will
not
be
the
case
going
forward.
So
in
that
we
have
two
week,
development
cycles
or
sprints
and
the
the
next.
The
current
sprint
is
ending
this
Sunday
and
we
will
be
creating
a
new
data
released
on
Monday
and
we
will
take
two
days
for
QA.
E
Even
though
development
process
is
embedded
in
our
QA
is
the
embedded
in
our
development
process
will
take
two
days
to
do
the
QA
and
we
will
release
the
dogfight
1
1
0
on
Wednesday
and
then
based
on
the
feedback.
As
soon
as
we
are
confident
we
are
releasing
on
Monday
with
exception
Fridays.
We
never
released
main
its
versions
and
Fridays
because
then
the
weekend
is
coming.
If
and
if
there
is
a
major
issue,
we
cannot
really.
A
I
mean
I,
guess
that
part
of
the
inspiration
we've
talked
about
this
before,
but
part
of
the
inspiration
for
the
Daedalus
flight
was
what
we
saw
with
the
ITN
and
how
incredibly
powerful
it
is
when
you
kind
of
bring
the
community
into
a
into
a
testing
program
to
really
put
stuff
through
its
paces.
What
kind
of
other
plans
do
you
have
to
extend
this
this?
You
know
bringing
the
community
into
the
development
of
Daedalus
longer-term
yeah.
E
This
is
a
very
good
question,
so
the
idea
is
to
really
become
an
open-source
project.
Daedalus
is
open
source
project
because
the
sources
are
out
there
and
it's
free
to
use,
but
the
flight
is
just
the
first
step
in
opening
our
development
roads
to
do
community
flight
open
the
QA
part
of
our
release
process.
E
So
people
are
helping
a
PEZ
disorder,
but
we
also
be
opening
development
and
code
contributions,
so
we'll
prepare
specifications
and
user
interface
designs
for
new
features
which
are
not
urgent
to
be
implemented,
and
then
we
will
ask
community
to
help
us
with
code
contributions.
We
already
had
code
contributions
on
our
react:
polymer
project,
which
is
our
UI
library.
We
are
using
four
levels
and
we
hired
a
developer
who
contributed
the
most
there.
So
I
cannot
promise
anything,
but
they
will
be
hiring
a
new
developer
in
giorgetto
still
very
very
soon.
So
maybe.
A
A
E
Yeah,
absolutely
so
we'll
be
having
a
lot
of
discussions
in
about
the
Romans
in
the
future.
But
the
next
major
feature
coming
to
Delos
is
definitely
hard
level
support
and
that's
both
ledger
and
tzur.
So
our
next
development
cyclists
beginning
on
Monday
and
we'll
build
a
prototype,
400
world
support,
and
if
we
find
that
we
have
all
required
pieces,
you
will
have
it
relatively
soon
and
we'll
be
able
to
announce
it
relatively
soon.
So
watch
out
for
news,
the
Daedalus
and
how
the
world
support
is
coming
real
soon,
fantastic.
A
Okay
Rana,
should
we
talk
about
business
as
we
do
it
yeah?
Let's
do
it.
Okay,
let's
see
if
we
can
get
Kevin
onto
onto
the
screen
now
he
should
be
should
arriving
here.
He
comes
Kevin
was
having
a
few
connection
problems
earlier,
I'm,
not
sure
whether
he
was
just
playing
with
us
to
keep
suspense
going
longer
and
longer,
but
hopefully
Kevin
will
be
able
to
join
us
soon.
Here
we
go.
A
So
welcome
welcome
so
Kevin.
A
few
of
you
may
have
a
comment
Kevin
before
Kevin
actually
pushed
out
a
blog
piece
today,
which
I
hope
some
have
a
chance
to
read
already
really
just
taking
us
through
the
steps
and
the
three
different
tests
met,
stages
that
will
be
sort
of
travelling
on
on
the
road
to
Shelly,
but
Kevin,
perhaps
just
for
the
sake
of
people
haven't
seen
that
blog
post.
A
F
F
Okay,
thanks
Dave
you've
stolen
my
thunder
because
the
key
messages
you're
going
to
be
three
phases.
The
first
phase
is
going
to
be
a
friends
we're
going
to
be
inviting
and
some
we
know,
and
some
stalwarts
of
the
ITM
community
chosen
who
carefully
so
criteria
to
join
us
to
get
things
up
and
running,
to
kick
the
tires
test
the
documentation
and
make
things
ready
for
the
world
and
then
what
we're
going
to
be
doing
is
to
open
up
to
a
public
test
net.
F
Anyone
will
be
able
to
joined
in
that
this
will
be
a
chance
for
pool
of
risk
example
to
test
out
their
parameters
and
be
chance
for
everyone
to
try
out
all
the
new
diglettz
Explorer
and
on
teachers
that
we'll
be
producing
at
that
point
in
time
and
the
third
phase,
it's
very
important
to
anyone,
who's
been
delegating
onto
the
ITN.
This
is
the
balance
check
phase
when
we
take
stock
of
all
the
rewards,
you've
earned
through
your
delegations
thinking
and
we
transfer
these
over
to
the
main
mantasy.
G
F
B
B
F
B
You're
testing
and
the
feedback
that
we
get
do
you
open
up
to
the
public?
We've
got
the
majority
of
the
feedback
on
rebuilt
in,
and
that
is
similar
to
the
flight
program.
It's
also
similar
to
what
we
heard
from
the
ITN
feedback
from
a
lot
of
our
stick
pool
operators
a
lot
of
feedback.
We
got
there
that
people
did
like
the
rollout
approach,
so
we're
doing
that
just
to
ensure
that
when
we
get
to
Shelly
main
net
that
we
have
pretty
much
every
single
sort
of
possible
feedback
loop
from
the
community
built
into
it.
B
F
Yeah,
so
about
a
month
ago,
where
we
were,
we
were
running
byron.
We
heard
the
baroness
elko
that
we've
been
running
for
quite
quite
a
while,
and
then
we
went
through
the
byron
reboot
just
about
a
month
ago.
What's
going
to
happen
going
ahead,
is
we're
going
to
take
the
byron
reboot
we're
going
to
go
through
a
hard
fork
on
the
Haskell
code
and
we're
going
to
end
up
in
the
celli
era
and
the
way
we're
going
to
do?
This
is
essentially
going
to
be
by
evolving
the
haskell
byron
reboot
code,
so
we're
not.
F
This
is
not
going
to
be
a
complete
rewrite.
The
way
that
byron
reboot
is
rather
what's
going
to
happen,
is
we're
going
to
add
in
some
features
and
capabilities.
So
the
moment
we're
at
stage
where
we
have
federated
block
production,
simple
transactions,
and
where
we're
going
to
we're
going
to
have
decentralized
block
production,
we
can
have
delegation
staking
and
rewards
we're
going
to
have
transactions
with
metadata,
multi
signature
transactions
and
the
treasury.
It's
going
to
open
up
all
kinds
of
exciting
possibilities.
The
way
we're
going
to
do
that
is
we've
now
in
the
byron.
F
Reboot
got
a
number
of
components,
so
we
have
a
networking
code.
We
have
a
consensus
layer,
running
PFT,
PFT
protocol.
We
have
electrical
component
running
our
Byron
ledger
rules,
command
line,
interface,
database,
client,
API
and
we're
about
to
put
in
something
called
the
hard
fork
Combinator
and
that's
a
piece
of
magic.
So
what
the
heart
felt
Combinator
is
going
to.
Let
us
do
is
essentially
the
kind
of
trick
we
pulled
with
Byron,
which
is
that
we
are
going
to
be
running
with
Byron
reboot
code
and
magically
in
real
time.
F
We
will
flip
a
switch
and
gradually
nodes
will
come
online
that
are
running
share
it
jelly
era,
block
production
so
within
a
very
short
space
of
time,
we'll
go
from
running
byron
era,
nodes
to
running
shelley,
erin,
no
nodes
live
on
the
main
net
and
you
won't
even
notice.
It
will
just
happen.
We
been
instantly
able
to
delegate
its
etc
and
obviously
there'll
be
a
few
things
that
we
have
need
to
do
to
do
that.
F
There's
a
lot
of
work
going
on
the
background
by
the
no
team,
particularly
implementing
new
Prius
protocol,
implementing
new
literals
for
Shelly,
extending
various
components
incorporating
transaction
metadata,
but
it's
not
just
about
the
node
team.
It's
also
about
all
the
other
teams.
Are
that
a
part
of
the
contour
no
community?
So
it's
about
Daedalus,
it's
about
the
Explorer.
It's
about
the
new
address,
dear
client,
API,
libraries
for
its
changes
and
it's
about
connecting
everything
up
with
the
world.
F
So
this
is
what
we're
going
to
be
doing.
In
brief,
we
will
have
two
phases
of
the
Haskell.
Show
you
test
net,
which
launched
with
a
boot
going
into
the
pioneer
phase,
our
relatively
small
number
of
pool
operators,
reboot
that
and
go
into
the
public
phase
in
public
phase.
What
we're
doing
is
we'll
be
testing
out
all
the
user
facing
components,
wallet,
etc
in
the
Pioneer
phase.
What
we're
doing
is
we'll
be
checking
that
everything
that's
important
to
state
pool
operators.
Is
that
ready
and
running
for
you
in
parallel
with
that?
F
We'll
continue
to
run
the
main
net.
The
bar
and
reboot
code
then
gradually
add
in
more
shellye
features
up
to
the
hard
fork
going
to
the
show
era
and
as
it
going
to
the
shellye
era,
there'll
be
gradual.
Decentralization
OB
ft
will
continue
on
some
notes
for
a
while,
it
will
be
gradually
phased
out
and
eventually
we
become
completely
decentralized
and
completely
shelling,
and
the
third
strand
is
the
ITN.
F
So,
to
give
you
a
bit
of
more
detail,
get
on
the
test
net
pioneer
phase,
what
we're
doing
gyrating,
Keys
starting
nodes,
registering
pools,
missing
state
keys,
staking
fake
ADA
and
testing
transactions
will
be
running,
Shelly
only
blocks
with
vrf
crypto
and
Forsyth
sharing
fake
ADA,
and
then
we
go
to
public
tests.
Net
will
be
looking
not
only
the
state
pool
side,
but
also
the
wallet.
F
Cli
are
the
Explorer
dateless
this
address
dear
client,
API
we'll
be
testing
out
the
hard
fork
Combinator
in
the
test
net
before
we
go,
live
on
the
main
net,
generating
Shelley
and
Byron
era
blocks
to
let
us
do
that
and
with
additional
crypto
security
built-in.
So
this
will
be
as
close
to
the
real
thing
as
we
can
get
I'll
just
stop
sharing
my
screen.
Ten.
B
So
thanks
Kevin:
let's,
let's
talk
a
little
bit
about
the
ITN,
because
there
is
a
portion
that
we
do
the
balance
check
and
bring
them
on
board
into
into
your
Shelley's
Haskell
version.
So
you
were
involved
with
the
ITN.
We've
done
a
lot
of
retrospective
on
feedback
from
the
ITN
that
we've
mitigated
and
we're
trying
to
build
into
this
form
into
this
into
the
Shelly.
So
can
you
give
us
some
of
the
top
areas?
Kevin
yeah.
F
A
Kevin
we've
we've
had
a
couple
of
couple
of
questions
here.
Maybe
we
can
just
take
a
couple
of
these
now,
if
that's,
if
that's
possible,
so
we've
got
a
question
here
from
oh:
do
Z
Aurora's,
not
quite
sure
which
one
so
after
Shelly
will
state
courts
continue
to
be
registered
by
the
condyle,
no
foundation.
I.
Think
a
few
people
in
the
past
have
been
slightly
concerned
that
this
is
a
potential
point
of
centralization,
but
I
understand
with
the
ITN.
It
was
really
just
a
sort
of
a
pragmatic
decision
to
have
them
manage
it.
How
well?
F
So
we
get
to
the
main
that
state
power
registration
will
be
entirely
on
chain
Tim,
though
the
Carmona
foundation
will
not
be
involved
in
registering
state
poles
at
all,
you'll
be
able
to
come
along
and
risk
your
self
and
fully
decentralized
way.
We
have
had
requests
for
maintaining
stewardship
of
pools,
pool
identities.
Tickers
object
have
been
a
particular
concern,
so
what
we're
looking
into
is
providing
groups
of
whitelist
servers
which
you
may
choose
to.
F
To
read
from,
and
one
of
these
working
on
by
the
cantare
foundation
Betsy
the
pools
are
on
this
list.
They
will
want
to
participate
in
the
ICN.
So
when
you
come
to
stake
your
ADA
on
the
main
net,
you
still
be
staking
it
with
the
people
who
ran
the
the
pools
on
the
test.
Next,
do
you
think
that's
a
fair
thing
to
do
so?
F
A
A
We've
also
had
a
couple
of
questions
here.
I
think
we've
seen
these
questions
a
lot,
I'm,
not
sure
how
much
you
can
answer
at
this
stage.
But
we've
had
a
question
here
about
the
values
of
the
K
parameters,
for
example,
and
also
the
amount
of
H.
Is
there
anything
you
can
answer
on
either
of
those
this
stage
so.
F
I
can't
tell
you
about
the
precise
value
of
the
K
parameter,
because
we've
got
a
meeting
on
Tuesday
when
we're
going
to
be
discussing
it,
we
have
had
a
lot
of
feedback
on
where
we
should
set
it
be
the
way
it
worked
on.
The
ITM
was
very
interesting.
We
were
expecting
that
the
number
of
poles
and
stabilized
around
the
K
parameter,
and
actually
what
we
noticed
was
that
it
stabilized
around
2k,
so
we
ended
up
with
more
poles
are
than
we
were
expecting
so
again
to
be
taking
that
into
account.
F
Choosing
that
priority
is
going
to
be
quite
important,
because
if
we
set
it
too
low,
then
we
don't
get
enough
decentralization,
but
we
set
it
too
high.
Then
it's
not
gain
it's
going
to
mean
that
you
can't
maintain
a
Bible
staking
business
again,
you're
looking
that
very
very
carefully,
so
that
we
get
that
exactly
right
as
we
go
forward-
and
this
is
something
that
we
can-
we
will
certainly
be
testing
in
the
test
nets.
F
One
of
the
great
things
for
the
chat
says
is
that
will
we
actually
be
able
to
dairy
that
so
with
the
ITN?
Aren't
we
started
off
with
one
setting
and
for
technical
reasons
we
couldn't
bury
it
very
easily
and
once
we
had
started
running,
we
felt
it
wasn't
a
good
move
to
bury
it
even
when
we
could,
but
we
will
be
able
to
test
that
much
more
thoroughly
in
the
two
tests.
Nest-Like
mentioned
him
great.
F
A
Question
around
pledging,
perhaps
you
just
want
to
explain
very
briefly:
people
may
hear
the
word
pledge
a
lot,
but
not
be
totally
familiar
with
what
it
is.
It's
really
a
core
part
of
the
the
way
the
system
will
work.
When
perhaps
you
can
explain
a
bit
more
about
pledging
and
where
our
thinking
is
at
the
moment.
On
that
sure.
F
So,
essentially,
what
what
pledging
is?
Is
it's
wave
for
pool
owners
to
show
their
backing
for
the
pools
that
they're
running,
though
pool
owners
and
operators
will
put
forward
a
certain
a
mistake
to
back
their
pool
when
it's
created,
that's
the
pledge
and
you
will
be
seen
the
then
pledged
to
each
of
the
poles.
Now
when
it
comes
to
rewards,
we
will
require
the
pool
owners
to
honor
the
potential
they've
made.
If
they
don't
all
the
pledge,
nobody
will
get
any
rewards
for
the
pool
in
that
epoch.
F
A
A
And
getting
our
first
pioneers
on
so
we'll
be
also
be
starting,
inviting
some
of
those
statehood
operators
who
we've
effectively
we've
been
used
to
better
set
of
criteria.
Somebody
haven't,
we
came
in
to
try
and
identify
a
bit
of
a
mix
of
technical
skills
and
a
few
other
things
maybe
just
touch
on
that.
Briefly
before
we
end.
Oh,
we.
F
Were
trying
we're
trying
to
get
a
broad
mix
of
operators,
so
we
obviously
need
people
who
have
to
be
actually
with
rowing
systems.
We
want
to
include
experienced
state
pool
operators,
but
we
also
want
to
select
operates
from
different
backgrounds.
We
need
to
select
them
from
different
geographical
areas.
That's
going
to
be
incredibly
important.
We've
got
a
whole
list
of
criteria,
including
what
we
want.
Some
we
want
have
some
people
who
are
professional
pool
operators.
F
F
A
A
A
Who
introduced
us
to
address
here
addressed
here
is
the
set
of
libraries
and
ap
is
that
will
allow
katana
to
be
more
an
exchange
and
third-party
wallet
set
of
api's
and
libraries
that
we
can
use
to
start
to
help
with
Karno
adoption
and
implementation?
So
I
hope
you
invite
Nick,
may
fatback
honor
the
court
who's
been
leading
for
this
this
project?
For
us,
it's,
let's
invite
Nick
Nick,
Nick,
nade
frick
in
here.
A
G
A
G
Yeah,
addressing
is
essentially
a
modular
SDK
which
allows
you
to
essentially
do
several
things,
but
primarily,
if
you
happen
to
be
a
wallet
developer
or
an
exchange
developer
or
any
other
developer
for
that
matter.
Think
of
it
like
a
toolkit
that
will
allow
you
to
create,
signed,
serialized
and
submit
transactions,
for
example,
in
addition
to
offering
access
to
their
libraries
to
use
things
like
batch
32
to
encode
things
more
efficiently.
G
G
Right
now,
we
are
focused
on
essentially
doing
a
few
things,
we're
trying
to
make
it
much
easier
for
the
developer
population
to
understand
how
to
install,
configure
and
run
essential
pieces
of
these
libraries
and
ap
is
and
improve
and
create
a
consistent
document,
documentation,
environment.
So,
for
example,
for
installation
we
are
offering
docker
compose
files
that
make
it
easy
to
download,
install
and
run
things
very
quickly
so
that
you
can
get
up
and
running
as
a
developer.
G
Okay,
is
everyone
able
to
see
my
command
line?
Looks
good,
okay
great.
So
this
is
a
great
example
where
I
downloaded
the
core.
Node
essentially
took
me
about
two
minutes,
and
it's
with
one
line,
I'm
able
to
run
that
node
locally
on
my
localhost,
and
you
can
see
it
starting
up
right
now.
This
is
great.
It
used
to
take
a
pretty
good
amount
of
time
to
build
and
install
and
create
all
the
dependencies.
G
G
But
here
you
see
that
with
one
single
docker
compose
line,
I
essentially
install
all
the
components
and
subcomponents
that
I
need
even
Postgres
and
then
I'm
able
to
really
just
have
that
on
my
localhost
and
you
know,
configure
it
and
get
it
running,
so
this
is
really
exciting
for
developers
to
have
an
easier
and
faster
way.
In
addition,
we
also
have
the
address
to
a
user
guide
which
is
now
in
the
repo
that
provides.
You
know
a
great
overview
of
what
address.
Tia
is
with
respect
to
the
roadmap.
G
It
covers
all
of
the
api's
and
corresponding
libraries
that
you
can
use
again.
If
you
want
to
create
your
own
wallet,
you
can
use
these
libraries
if
you
want
to
use
the
card
on
a
wallet
to
manage
utx
those
for
you,
you
can
do
that
as
well.
If
you
want
to
submit
a
transaction,
you
can
do
that.
If
you
want
to
assemble
a
transaction,
you
can
create
and
spine
that
transaction
as
well.
G
So
we
have
a
lot
of
nice
tools
for
people
to
use,
there's
also
a
good
contrast
between,
what's
end-of-life
in
for
SL
and
kind
of
some
corresponding
elements.
If
you're
in
exchange,
which
will
replace
that,
we
also
created
a
nice
kayson's
here
as
well,
that
you
would
like
to
create
a
wallet
with
a
nice
difficulty
level
to
make
it
simple
and
straightforward
to
simply
just
make
a
post
this
links
to
a
swagger,
which
is
quite
nice
as
well.
G
If
you
write
code
because
it
makes
it
pretty
straightforward
to
understand
what
the
requests
and
responses
look
like,
what
attributes
are
supported
and
the
different
forms
of
errors
that
you
might
have
to
handle
as
a
developer.
So
we're
constantly
improving
this
and
you
know
we're
adding
new
use
cases
all
the
time,
we'll
be
adding
a
use
case
for
exchanges
that
are
on
SL
and
we'll
also
be
adding
use
cases
for
creating
your
own
wallet
with
the
libraries
but
lots
of
great
stuff
here.
G
In
addition,
there's
some
there's
some
key
concepts
that
you
can
read
through
there's
a
great
summary
of
the
overall
architecture
which
for
the
core
node
and
address
yeah,
so
that
you
can
have
a
sense,
for
you
know
how
the
pieces
fit
together,
whether
you're
doing
some
blockchain
exploration
through
something
like
graph
QL
or
you
simply
just
want
a
wallet
to
use
so
that
you
don't
have
to
write
your
own.
You
TXS
and
just
post
to
it
through
her
on
a
wallet.
But
it's
all
here
and
we're
trying
to
make
it
easier
for
every
developer.
A
G
In
fact,
for
any
support
item,
while
you're
running
an
attempt
to
integrate,
you
can
simply
leave
an
issue
in
the
respective
github
repository.
Our
team
will
respond
to
you
right
away.
We
also
have
a
telegram
channel
that
you
know
we'll
be
including
in
our
FAQ,
so
that
people
can
you
know
it's
leave
feedback,
get
feedback
and
get
help
again.
A
Brilliant
mix,
thank
you
very
much
so
I
guess.
If
there's
any
exchanges
or
lot
of
developers
out
there,
Mackie's
put
the
link
at
the
bottom
there,
where
you
can
find
the
address
to
your
user
guide.
There's
also
get
sub
github
resources
that
people
can
access.
You
know
we'll
be
hearing
more
from
the
address.
That's
a
mangie,
of
course,
so
Nick.
Thank
you
very
much
for
joining
us.
Cheers.
A
Thanks,
Nick,
okay,
so
apana
we've
got
little
bits
on
left.
Wow.
Look
at
that
four
minutes.
We've
got
time
for
some
questions,
so
we
have
a
little
look
at
what
we've
got
here.
Yeah
is
a
good
one.
Here's
a
good
one,
so
look
I
mean
what's
the
estimated
delta
between
the
release
of
shelley
and
Gogan,
probably
the
most
common
type
of
question
we
get
is
obviously
around
the
cadence
and
releases
and
it's
always
the
old.
A
You
know
when
Shelley
joke
I
think
perhaps
you
just
want
to
reiterate
a
little
bit
about
what
our
methodology
and
what
our
approach
is
because,
as
we
said
at
the
beginning
of
the
call,
it's
it's
you've
matured
significantly
over
the
past
few
months
and
over
the
past
year,
iliyan,
the
byron
reboot,
is
really
marked
a
whole
new
way
of
doing
things.
Perhaps
just
rather
than
answer
that
question
specifically,
you
can
just
talk
a
little
bit
more
generally
about
how
we're
developing
and
how
we're
pushing
stuff
out
to
market
now,
absolutely.
B
You
guys
heard
from
Romana
in
terms
of
delivery
organization
and
how
we're
becoming
a
little
more
agile.
So
what
does
that
mean?
That
means,
as
you
can
see,
the
Shelley
getting
rolled
out
when
it
finally
does
do
a
feature
complete
portion
of
Shelley.
It's
not
like
Gogan
starts
it's
not
going
to
be
in
a
sequential
format,
we're
already
working
on
Gogan,
so
we're
not
you're
working
on
Shelley
we're
working
on
Gogan
we're
working
on
a
couple
of
other
projects.
B
That
Charles
has
mentioned
a
little
bit
about
in
his
AMAs
and,
as
you
just
come
to
these
updates
every
month
guys,
we
will
definitely
update
you
on
on
dates,
as
you
can
tell
like
today,
we
want
to
share
these
things
with
you.
It's
not
like
we
don't
want
to.
We
just
want
to
be
sure
of
what
we're
what's
coming
out
and
when
it's
coming
out
and
how
we're
going
to
message
it
to
the
community.
A
So
we've
got
a
couple
of
questions
here
also
around
education,
particularly
so
we've
had
a
couple
of
questions
on
the
progress
of
MOOCs
around
Plutus
we've
actually
got
a
new
Marlow
playground.
Now
that
you
can
have
a
try,
we
can
put
a
link
in
or
social
media
for
that
this
week,
so
you
can
get
access
to
that
and
have
a
go
with
that.
There's
also
quite
a
couple
good
couple
of
videos
that
Simon
has
a
shot
actually
for
the
University
of
Colorado.
A
So
we'll
share
those
videos
as
well,
which
give
you
a
little
bit
of
an
idea
about
the
progress
on
Marlowe
and
Plutus,
which
is
is,
as
I,
say,
it's
kind
of
come
out
of
the
limelight
a
little
bit
in
the
last
few
months.
Inevitably
because
we've
been
so
folks
and
other
things,
but
it
that
team
has
really
made
some
amazing
progress
while
we've
been
busy
on
our
thing
as
well.
So
we'll
share
more
about
that.
A
B
See
so
there
was
one
last
time
that
we
didn't
get
through
I,
don't
think
it
was
regarding
here's
one
about
a
big
summit,
so
this
is
probably
more
of
a
community
thing
where
we
had
a
big
summit
last
year.
You
are
organising
something
similar
for
2020,
but
Ken.
Do
you
want
to
talk
about
creation
and
where
we're
going
with
that
yeah.
A
So,
on
with
we're
hard
we're
now
planning
our
virtual
summit
charles's
mentioned
this
several
times.
We
will
continue
to
keep
you
updated,
but
again
it's
we've
really
got
a
sort
of
a
multi-function
multi-company
team
working
on
this,
so
we've
got
people
from
all
three
companies
kind
of
planning
that
you
know
that
the
situation
in
the
world
of
the
moment
is
such
that
the
virtual
summit
has
become
the
new
normal
in
many
ways,
but
that
doesn't
change
the
fact
that
we
really
want
to
do
a
good
job
of
this.
A
We
want
to
really
use
it
as
a
showcase
for
Shelley,
so
we'll
be
telling
you
the
date
of
that
virtual
summit.
Obviously
in
due
course,
I
think
the
word
is
soon
but
stay
tuned,
and
we
will
obviously
tell
you
more
about
that
as
it
happens,
but
we've
got
some
very
exciting
plans
for
that
not
only
talking
about
Cardno,
but
also,
maybe
talking
more
widely
about
some
of
the
other
words
going
on
within
the
ecosystem
and
also
within
the
community.
A
B
A
Well,
I'll
get
what
I've
got
one
minute.
Maybe
I
want
to
come
back
and
say
a
bit
more
about
that.
I'll
tell
you
what
we
can
do
next
month.
I
think
we
might
try,
give
you
a
little
bit
of
a
sneak
preview
of
some
of
the
work
been
doing
on
the
marketing
side
just
to
just
to
let
people
feel
and
see
what
we,
where
we
going
there,
because
there's
some
exciting
work
happening
behind
the
scenes.
A
It's
not
quite
ready
for
primetime
yet,
but
it
will
be
soon
so
yeah
we'll
share
a
bit
more
next
time
on
that.
Okay,
good!
Thank
you!
Everybody
for
joining
us
again,
a
few
technical
snafus,
but
I
think.
Hopefully
you
managed
to
catch
most
of
what
we
said.
I
believe
we've
been
streaming
live
to
YouTube
for
this
show,
which
is
the
first
time
so
hopefully
more
people
have
seen
it,
but
thank
you
all
for
joining.
A
Thank
you
for
your
questions
and
obviously,
if
you
want
to
go
back
and
watch
the
video,
it
should
either
be
able
to
matically
upload
it
to
youtube
or
will
be
on
there
very
soon
for
you
to
look
look
it
up.
So
yeah
may
the
11th
kick
off
friends
and
family
test
net,
inviting
our
staple
pioneers
in
there
they'll
get
everything
ready
and
then
we'll
start
inviting
everybody
else
on
board.
So
we'll
see
you
see
you
all
very
soon.
Thank
you
very
much
for
joining
thanks.