►
From YouTube: Cardano Monthly Update - March 2020
Description
Tim Harrison, Marketing & Communications Director, and Aparna Jue, Cardano Product Director, went live with other members of the IOHK Cardano team on Tuesday March 31 to share the latest on Cardano development.
Watch a recording of this live update to learn about what’s been going on, including the Byron reboot which is rolling out now. You'll also hear all about Adrestia – the new solution for exchanges and third-party wallets – Hydra and scaling, and an update on the Shelley Incentivized testnet.
Product managers who joined this live update:
Dynal Patel - IOHK Senior Product Manager (Incentivized Testnet)
Kevin Hammond - IOHK Product Manager & Formal Methods Engineer (Byron Reboot/Shelley Testnet)
Darko Mijić - IOHK Product Manager (Daedalus)
Nick Nayfack - IOHK Product Manager (Adrestia)
Rob Cohen - IOHK Product Manager (Hydra)
For more on the Byron reboot: https://iohk.io/en/blog/posts/2020/03/30/what-the-byron-reboot-means-for-cardano/
More on Daedalus Flight: https://iohk.io/en/blog/posts/2020/04/01/we-need-you-for-the-daedalus-flight-testing-program/
To learn more about IOHK and our work:
Company website: https://iohk.io
Get our latest news updates: https://iohk.io/blog/
Meet the team: https://iohk.io/team/
Work with us: https://iohk.io/careers/
A
Welcome
to
a
live
shows.
You
can
probably
tell
already
great
to
have
you
all
here
and
thanks
for
your
patience,
fantastic
to
see
so
many
people
here.
So
the
purpose
of
this
is
a
new
monthly
update
from
the
IO
HK
product
team,
primarily,
but
we'll
also
be
bringing
in
people
from
the
wider
family,
so
we'll
have
guests
from
imago
and
the
CF,
and
also
the
the
wider
community.
A
A
B
We
all
wish
you
safety
and
sanity
really
during
these
trying
times
so
pivoting
to
product.
So
our
current
focus
for
the
product
team
is
obviously
Cardno
delivering
the
solution
which
to
me
is
more
than
a
solution.
It's
really
a
Purpose
Driven
platform
and
it
has
real-world
applications
and
just
a
little
bit
about
me,
my
experience
and
my
passion
has
always
been
working
with
innovation
and
working
on
innovation,
the
based
solutions
that
and
here's
the
key.
B
We've
heard
this
and
that's
why
we're
all
here
and
then
the
use
of
formal
methodology
and
the
process
around
that
to
spec
out
the
designs,
and
that
is
truly
how
you
get
higher
surance
code,
so
why
product
management,
product
management
and
product
in
general,
because
it's
not
just
about
product
managers,
it
really
is
full
cast
of
characters
that
support
this.
Where
they
inject
themselves
is
really
about
about
asking
about
the
fundamentals:
it's
the
whys,
it's
the!
B
Why
are
we
putting
in
a
certain
feature
of
or
something
else
it
is
for
whom
are
we
designing
all
these
features?
It's?
What
are
we
actually
going
to
be
designing?
What
does
the
experience
look
like
and,
of
course,
the
how
so
our
purpose
is
not
to
design
it?
Our
purpose
is
really
to
make
the
best
help.
The
experts
make
the
best
decisions
on
how
to
design
something
and
really
putting
some
real
little
context
to
what
I
feel
is
beautiful,
research
that
we
have
here
and
if
you
talk
to
anybody
in
our
team,
they'll
tell
you.
B
B
Why
would
a
stakeholders
such
as
you
or
someone
in
the
community
care
and,
in
my
opinion,
it's
not
really
about
building
just
anything
right,
we're
building
a
technology
that
could
be
exponentially
innovative
to
so
many
real-world
use
cases
right
and
to
make
this
sticky
and
adopt
and
be
there
long
after
we're
we're
here,
it's
really
needs
to
have
a
level
of
high
assurance,
which
is
quality,
but
also
it
has
to
have
a
level
of
customer
and
user
based
input
into
it.
So
we're
prioritizing
and
building
the
right
things.
A
That's
right,
I
mean
I.
Think.
Obviously
the
focus
for
today
is
gonna
be
around
the
buyer
and
reboot,
which
is
kicking
off
this
weekend
is
obviously
a
porcupine
a
lot
of
our
time.
A
lot
of
the
dev
team
can't
actually
join
us
on
this
call
because
they're
still
in
the
final
stages
of
delivery,
but
I
think
really.
The
ITN
was
a
was
the
best
example.
A
Yet
we've
seen
of
that
collaboration
between
the
community
and
the
product
team
and
in
fact
the
whole
of
the
the
three
companies
involved
behind
Cardno
so
I
think
that's
probably
where
we'd
like
to
start
today
with
a
bit
of
an
up
to
date,
so
we've
asked
dinah'll
to
join
us
who
I'm
gonna
now
invite
to
give
us
a
little
bit
of
an
update
on
where
we
are
with
the
with
the
ITN.
Don't
know
hello.
A
Can
hear
you
fine,
hopefully
everybody
else
can
I
don't
know,
is
based
in
South,
Africa
and
I
understand
a
few
cables
got
cut
in
the
last
week,
so
we've
had
some
challenges,
but
hopefully
we
can
hear
you
loud
and
clear.
So
to
know
you
know
we
launched
the
test
net
back
in
December.
It
was
a
pretty
crazy
month.
I
know,
members
of
the
state
pool
operator
community
had
as
much
sleep
as
we
did
during
December.
C
Yeah
I
mean
what
I
will
say
is
the
ITN
has
really
exceeded
our
expectations.
If
I
was
honest
and
I
think
probably
the
whole
team
would
say
that
as
well
that
it
is
yeah
it's
basically,
the
level
of
participation
and
engagement
that
we've
had
has
been
way
beyond
what
we
expected
we've
had
over.
You
know.
1000
stake
goes
on
chain,
for
example,
800
of
those
active
we've
seen
you
know
over
17,000
people
delegate
to
six
take
polls.
You
know
we've
seen
in
30,
38
percent
of
the
total
ADA
supply
delegated
with
incentivize
test
net.
C
You
know,
and
also
the
country,
the
community
contributions
and
we've
seen
over
a
hundred
github
accounts
contribute
to
the
project.
You
know
250
unique
loans,
we've
seen
the
community
step
up
and
and
build.
You
know,
tools
that
were
missing.
So
no
really
a
big.
Thank
you
to
everyone.
That's
contributed
to
making
this
a
huge
success,
so.
A
I
think,
obviously,
the
the
feedbacks
been
continuous
throughout
the
whole
process,
but
is
upon
a
set
of
the
beginning.
We
actually
had
an
event
in
London,
which
we
got
in
just
before
the
the
coronavirus
really
closed.
Everything
down
I
mean
that
was
a
particularly
useful
session,
a
relatively
small
group
for
reason
to
geography.
But
what
was
some
of
the
key
things
that
we
heard
from
our
staple
community
from
that.
C
Yeah
we
had
a
lot
of
great
input
from
from
the
stigma.
Operators,
I
would
say
the
things
that
would
be
top
of
my
mind
would
be.
Firstly,
they
wanted
us
to
make
sure
that
we
consolidate
information
in
one
place.
Our
documentation
is
very
fragmented,
so
the
team's
gonna
work
on
that
they
were.
They
asked
us
to
sort
of
look
at
also
the
key
parameters
to
issue
the
economic
model
makes
sense
for
for
stable
operators,
especially
in
this
economic
climate.
C
They
also
asked
us
to
to
think
about.
You
know
how
we
could
enable
communication
between
you
know:
stake,
pool
operators
and
delegate
us
and
even
for
simple
things
like
alerts,
some
of
the
things
that
they
were
concerned
about
also
was
avoiding
a
race
to
the
bottom,
especially
as
example,
exchanges
come
online
and
and
also
initiatives
that
we
could
think
about
to
help.
Smallest
stake
pools
the
ones
that
are
struggling
to
create
great
blocks,
but
with
a
great
set
up-
and
you
know
beyond
that-
was
also
marketing
elements.
Now,
how
can
we
support
stake?
C
Pool
operators
to
build
a
brand?
You
know
how
can
we
help
them
to
migrate
that
onto
onto
main
net?
You
know
what
can
we
do
to
enhance
the
metadata
schema,
so
they
can
better
promote
themselves
and
and
also
give
the
community
choice
so
introducing
this
concept
of
aggregators
and
curators
on
a
protocol
level.
There's
a
lot
we
we
learnt
about.
C
You
know
improvements
that
need
to
be
made
to
the
incentive
scheme
to
discourage
bad
behavior,
for
example
the
cloning
and
in
general
as
well
those
a
request
for
for
help
of
example,
best
practice
from
DevOps
in
terms
of
how
to
run
a
stake
pool-
and
you
know
the
parameter
settings
around
that
also
commute
appreciate.
You
know
technical
training
sessions,
for
example,
having
a
training
week
or
or
providing
access
to
to
our
developers.
C
A
Yes
yeah
so
we've
had,
you
know,
support
from
all
over
the
world.
As
I
say
we
had
our
event
in
Europe,
with
a
few
of
the
guys
from
Europe
and
I've
noticed
a
few
names.
So
Rick
is
there,
for
example,
and
his
show
that
cut
uneffective
honestly
been
really
valuable,
contribute
to
the
computer
so
heads
up
to
you
Rick
and
Philip,
particularly,
but
also
everybody
over
there.
We
would
have
loved
to
have
got
far
more
people
from
far
wider
to
our
particular
event.
A
But
what
we
have
done
is
we've
captured
some
of
the
main
feedback
from
that
original
document
about
16
pages
of
notes,
I
think
which
poor
old
Mackay
had
to
write
up,
but
has
done
a
fantastic
job
as
ever.
So
we
shared
that
now
with
the
core
ambassador
community,
but
we
intend
to
share
that
more
widely
so
that
all
the
stake
pool
operator
community
can
have
access
to
some
of
the
the
things
we've
been
told
and
have
a
chance
to
offer
their
own
feedback.
A
You
know
that
the
I-10
has
been
this
Pathfinder
really
on
the
journey
to
shelly
on
main
there
and
the
learnings
from
both
a
technical
perspective,
a
game
theory
perspective.
A
marketing
perspective
have
been
massively
valuable
there.
Now.
Perhaps
you
just
share
a
little
bit
more
about
how
you
know
operationally
we're
trying
to
build
some
of
that
stuff
in
as
we
head
towards
Maine
that
Shelley.
C
Yes
sure,
so
what
we've
done
as
a
team
is
we've
basically
gone
to
to
each
of
the
function,
so
you
know
DevOps
the
product
team,
project,
management
teams
and
we've
done
an
internal
lessons
learned,
but
we've
also
gone
to
all
the
various
stakeholders,
so
our
partners
and
and
looked
at
you
know
how
they've
interacted
with
the
various
tools
that
we've
given
them.
We've
talked
to
you
know
all
the
delegates
have
sent
out
surveys
over
a
course
of
I
think
a
month
we've
held
these
workshops.
We've
consolidated
all
of
these
learnings
into
a
single
document.
C
I
think
we've
got
over
300
actions
from
across
all
these
different
work
streams.
So
we're
now
working
with
upon
and
team
to
prioritize
the
key
ones
and
see
which
of
those
we
can
actually
make
who
make
it
into
main
that.
But
the
idea
is
that
we'll
continuously
improve
the
product.
So
we'll
pick
those
up
over
the
course
of
the
year.
A
Here
we
go,
hopefully
that's
better
yeah,
just
looking
at
the
poll
here,
you
know:
we've
got
thirty
percent
of
the
votes.
People
running
a
stake
pool
here;
66
votes
delegating
ADA,
so
really
good
to
see
this
level
of
participation
in
the
test
and
obviously
we
hope
going
forwards
to
invite
everybody
else
to
be
staking
on
the
main
net.
A
Okay,
so
Appanna
ITN,
where
we
are
now
we're
heading
to
the
bar
and
reboot,
literally
as
we
speak,
all
right,
few
bits
and
pieces
have
been
deployed
already.
Some
of
the
relays
have
been
live
already
on
the
network
for
some
time,
but
perhaps
just
to
set
things
off
in
terms
of
setting
some
context.
Perhaps
you
just
want
to
tell
us
a
little
bit
about
why
Biron
reboot
matters
I
mean
we're
heading
to
Shelly.
Why
are
we?
Why
are
we
talking
about
Byron
again?
You.
B
Know
it's
a
great
question
so
for
me
you
know
it.
The
theme
is
foundation.
Byron's
theme
has
always
been
about
foundation,
so
bear
with
me
people
but
I'm,
more
of
a
visual
visual
learners.
If
you
think
about
concentric
circles:
circles
with
a
common
center,
we
start
at
the
core
and
the
core
is
really
about
fundamentals.
Is
the
innermost
circle,
its
foundational,
its
performance,
its
reliability,
its
sink
times?
Things
of
that
nature
around?
That
would
be
a
circling
layer
of
integrations
and
interactions
right.
C
B
A
blockchain
platform,
then
it
would
go
into
the
integrations,
and
why
would
this
be
the
easiest
way
for
you
to
interact
with
us
and
how
you
could
try
us
out,
and
then
you
finally
go
to
the
core,
so
the
performance
and
the
reliability
make
it
stick.
That's
what
makes
the
product
really
sticky,
because
it's
a
high
quality
product
at
this
point
right
so
with
Byron's
reboot,
it's
got
it.
The
design
and
the
core
has
been
improved,
so
it's
modular,
you've
separated-
and
this
is
kind
of
going
under
the
hood
a
little
bit.
B
But
it's
separating
the
ledger
and
the
consensus,
the
network
components
and
what
this
means
to
you
as
a
community
member.
It's
really
about
the
performance
and
the
reliability
of
the
code
and
whenever
we
do
make
updates
to
any
of
it
based
on
the
user
feedback
loops,
then
it
doesn't
really
take
us
that
long
to
be
able
to
deliver
it
to
you
and
also
it
has
less
chances
or
dependencies
or
breaking
the
other
piece,
an
other
portion
of
it.
B
The
reboot
also
allows
us
to
do
the
whole
evidence
based
methodology
or
the
engineering
approach
right
to
what
they're
doing
it's
a
key
position
for
us.
We
believe
it
where
we're
going
with
it
and
it's
multiple
teams
here,
so
we
have
four
for
Byron.
For
example,
you've
got
multiple
teams
you're
going
to
hear
from
our
product
people
on
this
call,
but
multiple
teams
coming
together
to
work
on
their
piece
of
the
pie
when
it
comes
to
or
component
really
and
then
putting
it
all
together
and
testing.
All
of
this.
B
All
of
this
before
they
hand
it
over
to
you
to
test
I,
do
want
to
take
a
minute
to
talk
about
the
testing
Tim,
because
there
are
different
levels
of
testing
that
make
formal
methodology
such
a
key
value
proposition
for
us.
So,
for
instance,
at
the
core
at
the
performance
level,
our
developers
use
something
called
quick
check,
which
is
really
a
software
library
right.
It's
it's.
It
supports
what
we
call
property
based
testing.
B
Some
of
you
may
already
be
familiar
with
it,
but
this
is
a
chance
for
them
to
specify
these
high
level
mathematical
properties
about
the
code,
and
then
they
run
them
through
these
randomized
test
cases
to
test
those
properties
out
and
what
this
really
does
is.
It
brings
out
bugs
and
issues
that
you
wouldn't
be
able
to
catch
in
regular
QA
and
what
we
call
a
you
know,
an
exotic
bug,
for
example,
or
something
that
we
would
have
never
found,
and
we
have
a
bunch
of
these
that
our
teams
have
have
found
through
this
process.
B
Getting
here
and
I
mean
there
was
actually
one
that
I
wrote
down,
because
I
thought
that
was
pretty
interesting.
It
was.
It
was
one
that
the
consensus
team
was
working
on
where
they
were
trying
to
improve
the
sync
performance
and
they
were
making
the
block
addition
portion
of
it
asynchronous,
rather
than
synchronous
to
be
able
to
increase
the
sync
Tyler
get
better
sync
times.
What
ended
up
happening
is
through
this
quick
check.
B
They
were
testing
it
out
and
they
found
that
the
block
fetch
code,
the
logic
to
it,
didn't
really
align
with
the
whole
asynchronous
nature
of
block
addition,
and
what
that
did
was
it
did
the
opposite
effect
it.
Actually,
it
was
detrimental
for
syncing
times
now,
something
like
that.
You
can't
really
catch
during
regular
QA
so
by
using
this
property
based
methodology
with
informal
methods
to
be
able
to
check
this
at
these
component
levels.
That
gives
us
a
level
of
testing.
B
E
Hi
hi
Bonner,
so
it's
great.
It's
only
exciting
questions
coming
up
on
the
on
the
list,
I'm
not
sure
we're
going
to
have
enough
time
to
answer
all
of
these,
but
first
thing
to
say:
is
it's
been
really
exciting?
A
few
months,
we've
all
been
working
really
really
hard
behind
the
scenes
and
it's
fantastic
to
get
to
the
stage
where
we're
releasing
by
reboot
and
where
Shelley
is
just
on
the
horizon
and
Gogan,
and
so
on.
Just
behind
that
I
thought
it's
been
amazing
to
interact
with
people
on
the
idea.
E
Incentivize
test
met
to
meet
with
the
state
pool
operators
and
see
people
actually
using
the
code.
I'm
particularly
excited
to
get
Daedalus
out.
You
think
the
node
and
having
ordinary
people
using
things
that
we've
built.
It's
an
amazing
experience.
So
thanks
guys
for
that
so
I
pop
upon
it
and
you
wanted
to
go
through
a
few
things.
If
you
look.
E
I
think
you've
come
up
quite
a
few
of
them
already.
You've
you've
done
such
a
good
job
aparna,
but
I'm
not
sure,
there's
a
huge
amount
for
me
to
add,
and
so,
of
course,
the
performance
and
reliability
improvements.
This
is
what
we've
been
aiming
at,
but
but
this
is
not
just
to
bring
benefits
Byron.
This
is
going
to
underpin
all
of
the
future
development
that
we're
doing
so,
we've
completely
rewritten
our
the
Byron
code-based.
This
is
literally
from
the
ground
up
rewrite
the
consensus
code.
Leger
owed
the
networking
code.
E
These
are
all
new,
the
byron
reboot
and
the
advantage
of
that
is
because
we're
following
a
mortal
approach.
We
can
easily
sort
in
the
future
developments.
We
need
to
save
delegation
for
Shelley
our
smart
contracts
for
Gogan
and
lots
and
lots
of
other
exciting
things
that
are
going
to
happen
coming
forward
in
the
very
near
future.
E
So
another
great
thing
that
we've
done,
of
course,
is
to
deploy
this
formal
but
agile
development
methodology,
and
this
is
great
because
we've
been
able
to
bring
things
very
quickly
to
go.
I
noticed.
Eight,
it
appears
to
take
in
18
months.
Well,
actually
seems
to
be
moving
very,
very
fast
behind
the
scenes,
so
we
have
a
new
software
development
methodology
where
we
have
proved
formally
key
aspects
of
the
ledger
rules.
For
example,
we
know
that
the
ADA
is
preserved
by
the
ledger.
Rules
nobody's
going
to
lose
any
ADA
seeing
our
process
are
correct.
E
We
have
been
able
to
translate
that
into
two
paths:
quickcheck
tests
and-
let's
say
we've
been
checked
code
and
verified
code-
does
exactly
what
we're
saying,
but
the
same
time
be
able
to
make
very
quick
and
rapid
adjustments
and
including
incorporating
some
feedback
from
state
pull
operators
workshop.
There
were
some
issues
that
people
raised,
but
very
important.
We've
been
listening
to
you,
we've
been
listening
to
what's
happening
on
the
ITN
and
we've
been
able
to
incorporate
those.
B
Absolutely
Kevin,
you
know:
we've
we've
learned
a
lot
going
through
this
process
and
in
such
a
short
amount
of
time
and
we're
putting
out
some
great
stuff.
But
really
a
lot
of
the
community
is
also
here
to
talk
about
Shelley
and
let's
just
kind
of
go
into
the
test
net
phase
of
Shelley
and
how
we're
going
to
be
applying
what
we've
learned
with
firing
and
bringing
into
the
community
into
Shelley's
test
net
yeah.
E
So
the
great
thing
about
the
Shelley
code
is
that
about
8%
of
it
is
the
same
as
Byron
code
component.
So
all
the
things
that
we've
been
working
on
recently,
all
all
the
improvements
will
be
carried
forward
to
Shelley
as
well.
So
the
way
we
will
be
rolling
this
out
first
thing
should,
of
course,
is
to
have
an
internal
test
net.
E
So
we're
going
to
be
testing
the
code
internally,
the
new
Shelley
node
code,
then
we're
going
to
open
up
our
to
a
few
pool
operators,
exchanges
and
other
key
partners
and
go
through
a
phased
process
of
testing.
So
we
really
want
to
test
this
out
to
systematically
test
all
of
the
features.
All
the
delegation
and
other
features
are
they're
going
to
be
important
and
make
sure
that
the
documentation
we
have
is
asking
first
rate.
E
We
know
that
a
lot
of
you
appreciated
the
help
and
documentation
that
you
heard
for
the
incentivize
test
net,
we're
hoping
to
provide
documentation
least
as
good
as
that,
and
hopefully
better
so
we're
working
really
hard
to
do
that,
having
gone
through
our
first
phase
of
opening
up
the
test
net.
What
we
then
do
is
to
open
it
up
to
the
world.
So
this
will
we,
when
we
open
the
gates-
and
we
say
please,
come
and
try
it
out.
E
We
expect
that
to
be
a
relatively
short
phase,
because
by
that
stage
everything
should
be
thoroughly
tested.
We've
proved
things:
we've
applied
our
formal
methodology,
we've
been
doing
lots
and
lots
of
testing.
We
all
have
tried
everything
out
on
a
large
number
of
nodes,
probably
about
ten
thousand
nodes
and
we'll
have
a
lot
of
confidence
that
things
will
work
and
really
what
we're
going
to
be
doing
in
the
second
test.
E
Net
phase
will
be
tuning
setting
parameters
and
onboarding
the
pool
operators,
because
that's
going
to
be
incredibly
important
to
each
with
everyone
and
I
noticed
that
somebody
said.
Are
we
going
to
make
it
easy
for
the
existing
ITN
pool
operators
to
establish
themselves
on
the
mick
on
the
Shelly
main
net?
And
the
answer
is
yes:
we've
been
thinking
about
how
we
do
that.
We've
been
investigating
various
ways
to,
for
example,
and
carry
over
tikkun
names
and
other
and
other
information.
B
Okay,
so
then
there
was
a
quite
a
few
things
we
learned
from
the
idea-
and
you
heard
you
guys
heard
of
what
dnal
had
talked
about
earlier
and
a
lot
of
it
had
to
do
with
communication
about
what
we're
coming
up
with
how
we're
rolling
this
out,
where
the
phases,
a
lot
of
you,
really
want
to
know
what
we're
working
on
and
when
is
it
going
to
come
out?
It's
as
simple
as
that,
and
we
would
love
to
give
you
straight
for
more
dancers.
B
B
This
product
management
update
we're
gonna,
do
this
once
a
month,
but
there's
also
going
to
be
other
areas
that
Tim
can
talk
about
of
what
we're
constantly
to
give
you
guys
in
terms
of
videos
and
updates
weekly
bi-weekly
fortnightly
just
to
keep
you
in
the
loop
of
what's
going
on,
because
at
this
point
we
really
do
need
this
feedback
with
a
lot
of
the
product
Tim.
Do
you
want
to
speak
a
little
bit
to
that
before
we
go
on
yeah.
A
I
mean
we've
had
a
couple
of
questions
come
through
the
community,
our
market
and
communications,
and
obviously
to
a
policy
a
point
really
the
focus
up
until
this
point
has
been
about
building
foundations,
about
building
a
core
platform
that
we
can
really
start
implementing
and
building
the
functionality.
That's
gonna
make
card
our
know
what
we've
always
promised
it's
going
to
be.
A
So
I'm,
obviously
working
very
closely
with
you
and
your
team
of
parler
on
defining
those
kind
of
core
product
benefits
based
on
the
implementation.
That's
happening
on
the
platform
and
the
and
the
software
side,
as
it
were.
So
it's
still
a
moving
feast,
there's
no
point
in
promoting
a
product
until
it's
ready,
but
equally
we
need
to
make
absolutely
sure
we
are
shaping
a
product.
A
There
is
a
clear
demand
for
we've
got
some
good
partnerships
already
you've
seen
a
few
of
the
that
the
things
we've
done
already
with
some
of
the
proof
of
concepts
and
some
of
the
memorandums
understanding,
the
commercial
team
is
continuing
to
those
relationships.
So
really
it's!
It's
it's
an
ongoing
process,
building
the
brand
building
understanding,
but,
first
and
foremost,
having
real,
clear
propositions
that
we
can
get
people
to
build
on
that
will
really
drive
aid
reduction
going
forwards.
A
So
we'll
we'll
have
a
little
slot
pretty
much
every
time
on
some
aspect
of
that
marketing
and
comms
story.
But
as
a
partner
says,
our
primary
intention
is
just
to
make
you
guys
it
keep
you
informed
of
what's
happening
with
a
more
regular
cadence
of
information
which
itself
mirrors
the
more
regular
cadence
of
releases,
sprints
and
so
forth.
A
F
A
I'm,
just
merely
to
close
this
conversation
off
I
suppose,
more
than
anything
else,
we
sort
of
talked
about
the
Haskell
test
net.
Obviously
again
the
learnings
from
the
IDE
going
to
be
a
significant
part
of
that
we
will
be
reaching
out
to
some
of
the
state
pool
operators
in
the
community
over
the
course
of
the
next
few
weeks
and
we'll
be
looking
for
some
early
people
to
help
us
with
our
documentation.
Is
that
correct?
That's.
E
Right
so
we're
reaching
out
to
people
we'll
be
publishing,
documentation
and
other
information
information,
you'll,
be
able
to
download
and
install
the
code,
and
the
plan
is
to
make
available
as
standard
AWS
instance.
So
you'll
be
able
to
pick
that
up
and
use
it
by
yourself.
So
we've
plenty
of
opportunity
plenty
of
scope
to
tune
things
and
I
can
see
people
saying
how
long
will
expect
the
test
net
to
last
realistically
through
the
top
question.
E
A
B
A
You,
okay,
so
we've
talked
about
community
we've
talked
about
users
and
we've
talked
about
the
buyer
and
reboot.
What
happens
when
you
put
them
all
together
and
what
are
people
going
to
experience?
What
are
people
actually
going
to
see
as
a
result
of
the
reboot
and
also
some
of
the
other
work?
That's
been
going
on
behind
the
scenes
so
I'm
now
inviting
Darko
doc,
oh
hi,
hi,
so
Darko
is
product
manager
for
Dallas.
A
We
have
some
news
about
dadless
we're
going
to
share
so
perhaps
Darko,
just
before
we
kind
of
start
that
just
be
good
for
anybody
who
hasn't
come
across
you
before
I'm
sure
before
watch
your
amazing
videos
that
you
make.
But
perhaps
you
just
want
to
tell
us
a
little
bit
about
yourself,
your
role
and
your
particular
area
of
interest
and
expertise.
Yeah.
F
Sure,
so
let
me
start
it
a
bit
of
background
when
I
dial
IH
k.
Almost
four
years
ago,
I
was
working
mostly
as
a
JavaScript
developer
and
I
actually
wrote
the
first
lines
of
code
for
Daedalus,
with
one
more
colleague,
who's
working
with
me
and
I
also
came
to
educated
technical
background
before
our
H
K
I
was,
and
architecting
bid
financial
systems
and
government
systems
with
Enterprise
Java,
so
currently
I'm,
mostly
a
technical
product
manager.
F
This
would
probably
change
as
the
dolls
continues
to
grow
and
I
will
probably
continue
in
the
direction
of
strategic
product
manager,
and
my
area
of
expertise
is
user
experience
and
user
interface,
design
and
software
architecture,
and
there
is
one
things
I'm
especially
excited
about,
and
that's
executable
specification
and
just
briefly,
it
serves
two
purposes
in
thatis.
It's
a
human,
readable
way
of
capturing
software
requirements,
so
we
use
it
to
specify
features,
and
secondly,
it
also
works
as
automated
tests.
A
F
So
I
always
start
with
working
on
software
requirements,
so
I
I
was
working
on
specification
for
our
software
requirements
for
Byron
and
then
I
I
work
with
the
our
UX
and
UI
teams
to
actually
build
designs
and
like
lay
the
foundation
for
development
and,
for
example,
in
this
finally
boot
released.
There
is
a
very
important
feature,
which
is
a
bullet
migration
and
I,
wanted
to
make
sure
that
this
feature
requires
zero
manual,
a
test
from
user
point
of
view.
F
So
it's
completely
automatic
no
manual
action
directions
are
I
needed
and
I'm,
also
working
on
our
roadmap
and
I
work
on
our
split
planning
and
sprint
execution
with
our
excellent
excellent
in
team
lead
nickel
elements
case
doing
amazing
work.
We
also
have
dedicated
no
experienced
multidisciplinary
team.
So
thanks
that
I
was
team.
You
you
are
amazing,
then
I
participate
in
the
release
process.
F
A
F
F
This
was
the
the
core
idea
behind
the
Daedalus
fight
program-
yeah.
We
are
doing
right
now,
so
this
is
a
pretty
loose
version
of
Daedalus.
This
user
users
can
use
with
real
a
down
the
main
it.
So
this
is
the
important
part.
People
can
join
the
program
by
downloading
the
flight
wallet
and
they
can
use
it
alongside
their
production
version
of
the
levels,
so
they
can
compare
them
and
the
idea
is
for
them
to
help
us
find
these
shoes.
F
So
we
can
fix
issues
and
we've
seen
that
people
want
to
help
and
and
these
people
will
also
gain
access
to
new
features
before
everyone
else.
So
it's
kind
of
similar
to
beta
testing
or
like
canary
Google
releases
for
its
Chrome
browser,
and
this
will
be
like
a
very
valuable
source
of
test
data-
will
be
able
to
improve
the
quality
of
our
new
software
and
move
to
to
production
more
quickly.
So
this
is.
A
F
So
when
you
download
and
install
that
little
slice,
it's
a
completely
separate
installation,
so
it's
completely
safe
saving
in
in
terms
that
it
doesn't
touch
your
production
version
of
Dale's.
You
just
copies
over
and
migrates
in
wallets
and
that's
it.
So
if
you
help
us
find
and
find
issues
and
fix
issues,
and
if
you
are
stuck
with
an
issue,
you
can
just
go
back
to
your
production
version
of
Daedalus
and
continue
using
it
yep.
F
So
here
on
the
left
side,
I
have
production
version
of
Daedalus
and
here
on
the
right
side
of
Daedalus
flight,
and
this
is
actually
blocking
my
screen.
Okay,
so
the
first
thing
you
will
see
when
you
install
Daedalus
flight
is
it
has
a
new
team.
So
this
this
team
is
the
only
team
available
in
this
version
of
Daedalus
in
that's,
because
we
wanted
to
differentiate
it
from
the
production
version
at
all,
and
it
also
has
this
icon
here,
which
opens
this.
F
The
screen,
which
explains
what
the
flight
product
is
and
how
it
should
be
used
and
who
should
be
using
it.
So
the
only
thing
I
did
so
far:
I
just
installed
the
flight
for
revision
of
dados
and
I.
Obviously
let
it
sink,
and
it
detected
all
of
my
notes
from
the
production
version
of
Daedalus
and
it
migrated
them
all
or
imported
them
here.
So
this
will
happen
for
all
users
who
are
actually
using
Daedalus
and
who
have
four
wallets
in
there
dead,
almost
production
version
of
Bale's,
okay.
F
So
next
bullet
import
is
created,
two
wallets
here
and
one
of
these
wallets.
This
one
doesn't
have
a
spending
password
spending
passwords
were
not
mandatory
in
the
previous
version
of
Daedalus,
but
that
now
they
are
mandatory.
So
the
first
time
I
click
on
this
wallet
I
will
actually
need
to
set
the
same
spending
password,
which
is
good
a
year
generally.
F
F
So
it's
a
neat
feature
which
lets
you
filter
transactions
by
incoming
and
outgoing
by
the
time
and
amount
of
Ada,
and
the
very
neat
feature
is
this
one:
all
transactions
which
actually
pre-populates
data
with
minimum
and
maximum
amounts
for
all
these
values,
so
by
minimum
transaction
in
this
wallet
is
zero.
Six
six
ada
and
my
maximum
transaction
is
one
ADA,
so
I
can
kind
of
know.
What
can
I
filter
from.
F
Then
we
could
completely
reside
or
design
board
restoration.
It
now
has
multiple
steps
and
it
also
supports
reporting
your
wallets.
So
you
can
restore
your
wallet
here
in
Delos
and
it
will
be
completely
functional
until
have
the
same
state
because
State
lives
on
the
blockchain,
and
you
can
continue
using
both
your
own
Intel's
and
compare
user
experiences.
So
this
restoration
razor
is
now
multi
step,
wizard,
I'm,
not
sure
if
we
have
time
to
for
me
to
enter.
F
Here
we
go,
I
mean
insect
nevermind
I.
Think
I
wanted
to
show
you
is
that
the
this
ball,
this
step
of
enteric
words,
recovery
phrases
is
a
discrete
step,
because
we
wanted
to
make
sure
that
user
understand
that
the
only
thing
that
you
need
to
restore
a
wallet
is
just
the
wallet
recovery
phrase.
So
in
the
next
step
you
are
setting
the
wallet
naming
spending
wise
password.
F
Then-
and
there
is
one
more
thing-
I'll
close
this
window-
there
is
one
more
important
thing
to
show
that
there
obviously
a
lot
of
small
improvements
which
we
were
developing
during
the
course
of
incentivize
testing.
But
the
one
more
important
feature
here
is
changes
to
the
send
form.
So
if
I
want
to
receive
a
dot
in
this
for
it
and
I
go
to
get
the
other
one
and
I
enter.
F
To
confirm
transaction
dialogue,
because
we
want
to
make
sure
that
anyone
who
is
using
Daedalus
light
is
using
main
it,
and
these
are
real
main
it
ADA
transactions
and
they
are
irreversible.
So
in
order
to
make
a
transaction
I
would
need
to
type.
My
spending
password
and
I
also
need
to
confirm
this
by
using
this
check
box.
F
But,
for
example,
I
have
seen
this
toilet
in
90
minutes
from
from
from
the
beginning,
and
with
the
minute
it
took
me
4
hours
and
then
the
wallet
restoration
here
took
15
minutes,
and
here
it's
still
running
it.
It
still
takes
about
2
and
a
half
to
3
hours,
so
great
improvements
in
performance
so
far.
A
F
A
A
Ok,
so
I
I
think
one
you
know
when
talking
about
well,
it's
one
important
point
to
note,
and
this
is
something
another
key
learning
from
the
itn
is
around
safety
and
security,
particularly
with
new
programs
like
flight.
We
know
the
scammers
out
there.
We
know,
there's
always
people
trying
to
exploit
opportunities
and
the
community
team
and
the
ambassadors
are
kind
of
it's
it's
fashion,
mole
to
a
certain
extent
at
certain
times.
A
A
D
So
as
it
stands
today,
they're
often
great
number
repos
in
github,
it's
not
always
straightforward
for
exchanges
or
third-party
wallets
or
other
developers
to
find
and
integrate
with
the
core
node.
We
often
have
amazing
protocols
that
sometimes
can
be
difficult
to
understand
for
people
that
are
new
to
them.
An
address
via
it
creates
a
nice
set
of
API
s
and
libraries
to
create
sign,
submit
transactions
and
also
have
things
like
card
on
a
wallet
at
your
disposal
to
manage
you
TX
O's,
and
do
things
on
your
behalf.
D
D
So
the
bottom
line
for
this
is
that
we
are
headed
towards
building
a
coherent
set
of
SDKs
that
remain
stable
across
a
regular
release.
Schedule
so
that
again,
exchanges
to
pretty
wallet,
state,
co-operators
and
other
developers
who
build
against
the
core
node
don't
have
to
keep
pace
with
a
lot
of
the
node
to
client
protocol
changes,
and
we
can
manage
that
essentially
on
their
behalf.
D
A
D
I
can't
really
mention
specific
exchanges
for
various
reasons,
but
we
are
working
with
all
the
top
exchanges
in
the
crypto
space
right
now
and
essentially
creating
a
more
reliable
and
high-performing
method
of
not
only
just
integrating,
but
also
maintaining,
that
code
base
for
the
exchanges,
because
it's
quite
a
challenge
for
them
on
their
side
as
well
to
keep
pace
with
a
lot
of
the
changes.
Now,
given
our
expanded
product
team
and
given
our
expanded
focus
to
release
more
frequently.
A
D
You'll
see
in
this
upcoming
release
and
also
card
honor
graph
QL
and
those
are
all
just
ways
to
do
very
similar
things
to
explore
the
blockchain
more
efficiently
and
quickly
and
to
have
more
flexible
queries
for
developers
and
beyond
that,
in
terms
of
our
library,
specifically
we're
going
to
be
supporting
bachelor
t2.
We
have
a
library
to
create
sign
up
several
libraries
to
create
signs,
submit
and
serialize
transactions
and
do
address
things
like
address
management.
D
A
Okay,
so
we've
been
focused
on
the
immediate,
so
the
byron
reboot
we've
been
looking
at
the
slightly
longer
term
address
here.
Let's
maybe
go
a
couple
of
steps.
Further
still,
one
of
the
other
pieces
of
news
from
the
I/o
HK
camp
in
the
last
couple
of
weeks
has
been
around
Hydra
the
publication
of
a
paper.
That's
obviously
been
quite
a
significant
source
of
interest
for
a
lot
of
the
community.
A
G
G
A
So
Hydra
the
paper
stage
now
it's
a
piece
of
academic
research
which
obviously
has
a
roadmap
of
its
own
ultimately
will
become
part
of
the
Ouroboros
protocol.
But
just
before
we
talk
a
little
bit
about
that.
Perhaps
you
just
want
to
give
a
little
bit
of
a
overview
of
Ouroboros
to
anybody
who
may
be
different.
A
G
Sure
so
it's
important
I
understand
that
Ouroboros
is
really
family
or
an
evolution
of
protocols.
The
or
burrows
paper
was
the
first
iteration
of
the
herbivores
family
I
was
published
in
2017,
that's
or
Boris
classic.
That's
how
I
refer
to
it.
Now
that
introduced
the
mathematical
framework
for
the
protocol
as
an
energy
efficient
alternative
to
proof-of-work.
G
It
also
introduced
the
ability
to
use
secure
at
PC
to
generate
unbiased
randomness
in
the
selection
of
slot
leaders.
That
was
the
initial
iteration
and
since
then,
there's
been
a
number
of
additional
protocols
that
we've
developed
that
iterate
and
improve
on
it.
There's
a
reverse
B
of
T,
which
is
the
bridge
between
Ouroboros
classic
and
reverse
press
there.
G
This
is
the
transition
from
the
old
cordon
OSL
code
based
the
new
Cardano
node,
which
is
going
to
occur
during
the
Pyron
reboot
this
or
burst
press
right,
which
is
that's
going
to
be
introduced
during
the
Shelly
era.
This
is
what
enables
the
decentralisation
it's
built
or
burrows
classic,
and
it
provides
stronger,
assertive
security
assumptions.
It
assumes
semi
synchronous
settings,
for
example,
there's
also
or
Boris
Genesis.
This
is
an
iteration
on
press
where
it
has
a
novel
chain
selection
rule
which
enables
bootstrapping
from
Genesis
providing
the
same
security
guarantees
as
Bitcoin.
G
You
no
longer
need
checkpoints
in
order
to
synchronize
there's
also
Genesis
proved
the
security
of
or
burrows
under
Universal
composability,
so
it's
gone
through,
there's
been
a
huge
amount
of
effort
and
work
to
prove
that
that
Ouroboros
is
highly
secure
so
moving
from
there,
you
know
now
we're
going
to
or
Boris
Hydra
the
paper
that
was
published
last
week.
Well,
that
was
about
the
Hydra
protocol,
but
Ouroboros
Hydra
is
the
second
layer
protocol,
which
enables
vastly
increased
scalability
with
cardano.
G
Hydra
is
an
off
chain
scalability
architecture
for
distributed
Ledger's,
so
you
can
actually
use
it
on
other
distributed,
ledger
technologies.
Now
it
enables
high
transaction
throughput,
low,
latency
and
minimal
storage
print
node.
So
again
it's
a
it's
important
understand
that
Boris
Hydra.
That
is
our
second
layer
solution
for
for
card.
Oh,
no,
the
the
scalability
architecture
can
be
divided
into
four
components,
really
there's
the
head
protocol,
and
this
is
the
paper
that
you
saw
that
was
published
just
a
few
weeks
ago.
G
This
is
what
enables
a
high
set
of,
or
a
set
of
high
performance
and
high
availability
participants
such
as
state
pools
to
very
quickly
process
large
numbers
of
transactions
with
minimal
storage
requirements
by
way
of
isomorphic,
isomorphic,
multi-party
state
channels.
That's
a
mouthful.
So
this
is
the
concept
that
generalizes
to
parties
payment
channels
as
implemented
in
the
context
of
the
Lightning
Network,
except
instead
of
with
two
participants
in
a
payment
channel,
you
could
have
multiple
participants.
G
So
after
this
head
protocol
there
we're
gonna,
be
working
on
the
tail
protocol
right
metal
that'll
be
available
in
a
research
paper.
That's
forthcoming.
This
is
what's
going
to
enable
high
performance
participants
to
provide
scalability
for
large
numbers
of
end-users,
who
might
use
the
system
from
low-power
devices
such
as
mobile
phones
and
who
might
be
offline
for
extended
periods
of
time,
and
then
we're
also
going
to
need
the
cross
head
and
tail
communication
protocol
right.
G
G
Yeah
sustainability
right,
you
know,
my
vision
on
scalability
is
that
this
is.
This
is
really
what
we're
waiting
for
to
explode
a
whole
set
of
killer
applications.
You
know,
obviously,
the
one
that
many
people
are
focused
on
is
micro
payments.
You
know,
I
foresee
a
future
where
or
worse,
Hydra
is
responsible
for
99
percent
of
all
the
transactions
that
would
occur
in
the
Cardano
ecosystem.
G
G
A
G
G
If
you
compare
you
want
to
compare
apples
to
apples
is
what
I'm
getting
at
right.
If
you
compare
the
Internet
to
snail
mail,
you
know
that's
a
difficult
comparison
to
make
realistically
because
they're
very
different
systems.
If
you
want
to
have
a
fair
comparison,
you
know
you
really
have
to
take
the
whole
system
into
consideration.
So
you
know
visa.
You
know,
there's
various
claims
on
how
many
transactions
they
can
do.
Twenty
four
thousand,
we're
in
that
general
ballpark,
but
that's
completely
different
architecture
for
Hydra.
G
You
know
we
saw
in
the
simulations
is
that
we
can
easily
accomplish
1,000
transactions
per
second
per
head
now.
This
is
a
very
paralyzed
able
protocol.
So
by
paralyzing
these
heads,
you
can
easily
scale
to
the
size
of
the
amount
of
bandwidth
that
you
actually
share
with
the
other
participants.
So
you
know
we
could
throw
out
crazy
claims
that
you
know
billions
or
very
high
claims
of
transactions
per.
G
Second,
but
it
really
comes
down
to
to
the
architecture
of
the
underlying
network
on
which
you're
doing
these
transactions,
so
you
know
when
I'm
happy
to
report
is
that
it's
very
parallelizable
and
it
comes
very
close
to
the
theoretical
maximum-
that's
feasible
the
communications.
So
you
know,
unless
the
laws
of
physics
are
broken,
I
find
it
unlikely
that
somebody
will
be
able
to
invent
something,
that's
a
much
more
capable
than
what
we
have.
G
A
G
A
Do
okay,
so
partner,
I'm,
very
aware,
I'm,
keeping
all
your
team
away
from
the
reboot
we've
got
a
lot
of
questions
here.
We've
got
51
questions,
I,
don't
think
we
can
really
hope
to
too
many
of
those
I
mean,
maybe
just
before
we
close,
it
would
be
worth
just
mentioning
a
couple
of
these
here.
I
think
there's
a
couple
of
here
we
might
want
to
talk
to
particularly
I
mean
ultimately
we're
here
today
and
the
reason
we're
all
doing
this
is
to
create
a
world-class
well
booting
product
and
there's.
C
B
We've
actually
answered
quite
a
few
of
those
and
the
questions
and
the
answers
panel.
So
if
we
go
down
to
that,
if
you
guys
go
down
to
that,
a
lot
of
them
we're
trying
to
answer
and
then
we'll
try
to
get
to
a
lot
of
these,
also
throughout
the
throughout
the
week
and
before
our
next
live,
show
as
well
and
put
it
out
there
for
the
community.
B
So
it
you
know,
in
my
opinion,
what
we're
doing
here
today,
apart
from
giving
you
guys
a
product
update
and
introducing
this
whole
foundational
reboot
with
byron
that
we're
kicking
off
as
well
as
the
concept
of
flight,
which
I
hope
you
guys
are
really
excited
about,
because
I
think
it's
a
beautiful
way
of
being
able
to
get
you
involved
into
our
products
before
we
actually
put
it
in
production,
ready
environments
right,
there's
a
couple
of
key
takeaways
one.
We
have
a
great
team.
We
truly
believe
in
this
mission
to
deliver
card.
B
I
know
and
you've
heard
from
quite
a
few
of
them
and
on
this
show
we'll
continue
to
to
bring
them
on
from
different
aspects
of
the
I/o
to
showcase
what
they're
working
on
what
they're
doing
in
support
of
this,
we
are
starting
a
quick,
agile
delivery
methodology
in
how
we're
going
to
be
releasing
these.
So,
yes,
formal
methodology
means
we
take
time,
but
that
doesn't
mean
we
don't
release
in
a
way
that
you
can
test
things
that
are
maybe
not
as
stable
as
it
would.
If
we
had
to
go
through
the
waterfall
methodology.
B
That
way,
we
invite
you
in
to
our
product
development
process
as
the
community
and
we're
asking
for
that
participation
and
we're
really
excited
to
be
doing
this
and
then
three
of
the
communication
with
our
community.
Where
do
we've
been
doing
a
pretty
good
job
of
that
we're
gonna?
Take
it
up
a
level
and
now
introducing
the
faces
of
Cardno
to
you,
with
the
product
teams
and
with
the
other
team.
Supporting
teams
as
well
and
doing
this
regularly
will
be
will
be,
will
be
great,
so
looking
forward
to
continuing
this
relationship
with
you
guys
there.