►
From YouTube: June Mid Month Development Update
Description
It’s the middle of the month, so it’s time for our regular technical update on the latest in Cardano development. Today, Tim Harrison is joined by regulars Nigel Hemsley & Kevin Hammond.
It's a critical week as the core IOG team (working with a number of SPOs and Dapp projects from the ecosystem) is in the final mile of testing and integration, including Plutus v2 compatibility and performance. Nigel talks about the new Vasil developer testnet for the Dapp community, and discusses the careful evaluation process underway and decision points as we head towards locking down and deploying the Vasil upgrade. Kevin also offers an update on the very positive results we’re seeing when it comes to node performance and how Vasil will see Cardano become more decentralized than ever before.
Useful Links
Follow IOG on Twitter: https://twitter.com/InputOutputHK
Sign up for our new Essential Cardano newsletter here! https://mailchi.mp/iohk/creators
Check IOG blog page for all the latest blogs: https://iohk.io/en/blog/posts/page-1/
A
B
C
There's
lots
of
moving
parts
tim,
but
it's
going
extremely
well.
I
think
it's
worth
me
just
talking
to
you
now
about
what
happened
last
week
and
where
we
were
in
terms
of
our
evaluation
on
friday.
So
what
is
the
process
that
we're
trying
to
go
through?
Well
we're
pulling
together
over
20
different
components
to
make
sure
that
they
work
properly
for
the
vasel
hard
fork,
and
we
want
to
make
sure
that
all
our
community,
all
the
principal
actors,
sbos
exchanges
and
apps-
are
all
stepping
in
line
with
us
and
that
we're
working
together
successfully.
C
So
we
brought
all
that
together.
We
had
a
good
session
with
our
adapt
community
last
monday
they
gave
us
some
really
helpful
feedback
and
then,
on
friday
we
did
an
evaluation
about
whether
we
think
we're
in
a
position
to
hard-fought
the
test
now
and
we
step
through
every
single
different
component,
whether
it's
ready
or
not,
and
we
step
through
what
our
current
quality
status
was,
and
we
had
an
assessment
on
the
sentiment
of
what
we
needed
to
do
and
also
had
an
assessment
of
what
the
impact
might
be
on
exchanges,
spos
and
dapps.
A
C
The
way
to
really
understand
it
at
the
top
level
and
then
it
makes
it
easier
to
do
that,
and
then
you
drill
down.
So
really,
if
you
look
at
it
from
a
functional
and
non-functional
perspective,
functionally
number
one:
we've
got
to
do
our
regression
testing
against
pluto's
version,
one.
What
does
that
mean?
Well
we're
testing
against
backwards
compatibility.
C
We
have
to
be
cautious
and
careful
and
assess
what
our
performance
is,
because,
obviously
what
we've
done
is
we've
done
a
significant
amount
of
optimization
and
performance
improvements
with
pipelining
parameter,
updates
and
other
elements,
as
we
step
through.
All
of
that
on
friday,
there's
lots
of
really
good
news,
so
in
terms
of
pluto's
version,
one
functionality,
a
number
of
our
components
that
we've
tested
and
some
of
the
dapps
that
we've
working
with
have
given
us,
100
green
light
on
that
regression.
C
Testing
capability,
which
is
fantastic,
things
are
working
and
what's
even
better
than
that
is
we've
also
tested.
The
fact
that
it's
significantly
faster
and
it's
faster
from
our
own
performance
benchmarks,
which
is
based
on
our
network
parameters,
so
we're
also
seeing
it
from
the
front
end
as
a
dab
and
where
we've
got
some
of
our
adapt
partners
working
with
us
and
going
end
to
end
on
their
transactions
and
that
they've
got
another
layer
of
complexity
and
theirs
is
going
faster
as
well.
So
that's
terrific
news
now,
we've
seen
we
obviously
know
the
numbers.
C
We
can
see
the
factors
that
we're
working
with
in
terms
of
the
improvements
in
performance
and
optimization.
Yet
we
can't
publish
those
because
we
can't
be
exact
so
how
the
mainnet
interacts
to
how
the
different
test
nets
interact
are
very
different.
But
what
we
can
say
is
it's
heavily
indicative
as
we've
seen
in
the
past,
for
our
parameters
updates
in
the
past,
so
we're
feeling
very,
very
positive
about
the
results
that
we're
getting
on
version,
one
regression
and
also
in
terms
of
performance.
So
that's
terrific.
A
C
C
C
But
we
did
feel
on
friday
that,
as
a
team,
we
needed
to
see
more
end-to-end
testing
to
give
us
a
confidence
in
not
just
you
know
that
everything
was
working
correctly,
but
actually
to
make
us
really
see
how
dapps
might
use
this
behavior,
because,
even
though
we've
invented
it,
you
know
as
we're
seeing
in
the
main
network.
Today,
they
can
often
be
put
into
different
configurations
that
we
didn't
originally
expect.
A
C
So
the
process
we've
now
found
is
that
actually,
as
we
go
through
this,
we
line
up
all
the
components
and
the
major
axis
and
we
do
an
evaluation
every
week.
So
we
know
we're
close.
We've
got
a
very
small
amount
of
bugs
and
the
last
count
was
on
friday
was
at
20..
None
of
these
are
you
know,
severity,
one
or
twos,
which
is
terrific,
but
when
we
looked
at
it
we
said
well,
if
we're
that
high
quality,
why
don't
we
hard
for
the
kadano
test
net?
A
C
And,
as
you
might
imagine,
they've
all
got
quite
you
know
significant
architectures,
but
they
can
take
a
sub
amount
of
that
architecture
and
test
out
the
components
in
relative
version.
So
you
can
actually
do
a
smaller
transaction
and
use
all
three
and
then
you
layer
it
and
build
it,
and
you
can
actually
then
start
to
see
the
results
of
the
dap
as
a
whole.
C
A
B
Absolutely
tim,
so
things
are
progressing
very
well,
and
today
we
have
a
vasel
ready
version
of
the
node,
which
includes
reference
inputs,
reference
scripts
input,
datums
collateral
inputs,
all
the
things
we've
promised
in
previous
updates,
as
well
as
lots
of
other
improvements
to
the
networking
to
the
logging
and
to
the
other
components
systems.
This
is
all
looking
absolutely
great.
At
the
moment.
B
We've
got
lots
of
good
test
results,
including
from
our
own
qa
team,
as
well
as
stake,
pool
operators
and
app
developers,
who've
been
running
on
the
dev
test
net
and
we're
starting
to
get
some
really
promising
time
and
memory
benchmarking
results.
I
don't
want
to
spoil
the
surprise
too
much,
but
watch
this
space.
I
think
people
are
going
to
be
very,
very
pleasantly
surprised,
but
what
they
observe
from
the
time
performance,
particularly
of
the
new
node
and
finally,
we've
got
a
version
of
db,
sync
that
improves
the
sync
times
and
memory
usage.
A
B
Yeah,
so
the
g
parameter
tim.
This
is
all
about
decentralization.
So,
as
you
remember,
we
started
off
with
the
shelly
hard
fork,
with
the
d
parameter
set
to
one.
Iog
was
running
the
network
using
our
federated
notes
and
we
gradually,
over
a
period
of
time,
reduced
d
so
that
staple
operators
were
making
more
and
more
of
the
blocks
on
the
network,
and
about
a
year
ago
we
set
d
to
zero.
B
100
of
the
blocks
were
being
made
by
the
state
pool,
operates
on
the
cardano
network
and
that's
where
it
stayed
ever
since,
what's
happening
with
the
vassal
hard
fork,
is
we're
going
to
make
that
permanent
and
irreversible
we're
taking
the
d
parameter
away?
It
can
never
increase
again,
and
this
supports
karjana's
journey
to
becoming
more
decentralized
and
also,
very
importantly,
it
means
that
it's
a
very
important
step
to
the
community,
taking
on
a
more
prominent
role
in
operating,
running
and
controlling
the
cardano
network.
B
That's
where
we're
going
heading
forwards
tim
before
signing
off,
I
did
want
to
run
the
community
about
a
few
things
ahead
of
the
vasel
hard
fork.
First
of
all,
hard
forks
they're,
not
like.
Turning
on
a
switch
people
have
to
do
things.
Nothing
is
magical,
though
the
hard
fork
combinator
really
acts
like
a
bit
of
magic.
It
makes
things
very,
very
smooth
for
our
stake.
Pool
operators
makes
things
very,
very
smooth
for
arts
and,
after
we've
gone
through
the
hard
fork.
B
Obviously,
it's
not
going
to
be
complete
instant,
but,
as
more
developers
start
to
deploy
their
dapps
on
cardano
as
they
start
to
take
advantage
of
the
new
features
that
are
rolled
out
and
the
new
improvements
that
we're
making
to
the
throughput
of
cardano,
you
will
see
a
greater
degree
of
efficiency
and
reliability
in
the
apps
in
and
in
the
network.
So
things
looking
great
just
be
aware:
it's
not
going
to
be
completely
instantaneous.
A
C
Where
we
are
now
is
in
a
really
positive
place,
we've
done
a
lot
of
work.
We've
tested
a
significant
amount.
We've
got
a
very
high
quality
release
in
our
basel
dev
test
net,
but
we
are
going
to
be
doing
a
lot
more
work
in
terms
of
testing
pluto's
version,
2
scripts
and
having
our
adap
partners
start
testing
and
interacting
with
those
pluses
version.
Two.
What
we'll
do
towards
the
end
of
the
week
is
we'll
set
up.
Another
evaluation
point
where
the
whole
team
comes
together.