►
From YouTube: From an Ethereum 1 Client to an Execution Engine - Matt Nelson & Francesco Andreoli, Consensys
Description
From an Ethereum 1 Client to an Execution Engine - Matt Nelson & Francesco Andreoli, Consensys
From an Ethereum 1 client to an Execution engine Monolithic client infrastructure will make less and less sense as new roles appear. The Merge is pushing us to think of modularizing Besu. Maintaining a monolith that caters to both enterprises and mainnet users is not sustainable Gap between enterprise ethereum and mainnet ethereum is growing (EIP 1559, gas fee optimization… the Merge itself). Modular architecture: Is more aligned with Open Source Software. Enables more contributors from the ecosystem Enables configurations for different use-cases without extraneous components or complexity Unlock opportunities (ex: MEV support by extracting TX pool)
Sessions Details & Slides (if available): https://sched.co/14H6w
Access All Sessions: https://events.linuxfoundation.org/hyperledger-global-forum/program/schedule/
----
Hyperledger – Open Source Blockchain Technologies
Hyperledger is an open source community focused on developing a suite of stable frameworks, tools and libraries for enterprise-grade blockchain deployments.
It serves as a neutral home for various distributed ledger frameworks including Hyperledger Besu, Fabric, Sawtooth, Indy, as well as tools like Hyperledger Avalon, Cactus and libraries like Hyperledger Aries, Ursa. Learn more about Hyperledger projects: https://www.hyperledger.org/use
Discord: https://discord.gg/rVCn4j7UFd
Case Studies: https://www.hyperledger.org/learn/case-studies
Training & Certification: https://www.hyperledger.org/learn/training
Tutorials: https://www.hyperledger.org/use/tutorials
Webinars: https://www.hyperledger.org/learn/webinars
Events: https://www.hyperledger.org/events
Vendor Directory: https://www.hyperledger.org/use/vendor-directory
Subscribe to the Hyperledger Newsletter: https://www.hyperledger.org/newsletter
Follow-us on Twitter @Hyperledger
Learn about Hyperledger Membership: https://www.hyperledger.org/about/join
#Hyperledger #Blockchain
License
Creative Commons Attribution license (reuse allowed)
A
Cool
I
think
we
are
we're
live
awesome,
yeah
I
know
I'm,
very
grateful
for
for
the
talk
here.
I
think
this
time,
as
this
hyperledger
conference
is
starting,
we
want
to
change
a
little
bit
like
the
dynamic.
We
will
not
do
like
40
minutes
talk
only,
and
we
just
literally
do
some
some
discussion
with
Matt.
Let's
introduce
ourselves
briefly,
yeah.
B
For
sure
so,
I'm
Matt
Nelson
I'm
a
product
manager
that
helps
manage
Basu
at
consensus,
so
I've
been
working
with
a
bunch
of
the
hyperledger
community.
Now
for
about
six
months
and
working
on
the
merge,
you
know
for
even
longer
than
that
so
very
excited
to
talk
about
kind
of
what
we
view
as
the
next
steps
post
merge
how
we
want
basically
to
be
able
to
serve
a
bunch
of
different
use
cases.
A
Cool
I'm,
Francesco
I'm
a
part
also
from
consensus,
I'm
working
mostly
on
on
devrel,
for
for
a
protocol,
metamask
and
infuria
and
I'm
grateful
that
we
are
today
explaining
the
merged
next
steps
and
anything
that
to
do
with
with
Apple
education,
cool
I
guess
we
can
start,
it
will
be
very
interactive,
so
feel
free.
Also
to
ask
questions.
A
We
look
like,
let's
just
start
and
feel
free,
also
to
jump
in
these
are
literally
like
we
said,
okay,
how
we
feel
in
40
minutes.
So
we
literally
I
put
a
lot
of
like
interesting,
slides
just
to
give
an
overview,
but
we
need
to
yeah.
We
can
just
quickly
quickly
show
like
how
a
web
3
and
digital
assets
in
terms
of
like
reaching
out
audience.
We
put
some
numbers
here.
A
I,
don't
know
like
Matt
feel
free
also
to
add
things,
but
those
are
quickly
quick,
slides
before
we
get
into
the
the
the
important
parts.
I
think
the
the
next
slide.
It's
it's
quite
interesting.
So
how
is
the
theorem
ecosystem
look
like
how
big
in
terms
of
like
user
addresses
and
and
the
transaction
per
days?
A
So
this
is
something
that
is
growing
a
day
today
and
and
yeah
and
I,
don't
know,
I
think
the
latest
number
around
the
400
400
000
active
devs
and
we're
also
seeing-
and
you
know
the
builders
Market
is-
is
remaining
intact
and
it's
still
growing
compared
compared
to
the
the
the
the
the
the
the
token
markers
that
we
see
today.
Yeah
but
yeah
cool
I,
don't
know
any
questions
until
so
far
or
anything
to
add.
A
B
B
The
you
know,
kind
of
less
sustainable
points
under
that
are
that
we
think
more
Enterprises
will
be
interested
in
cryptocurrency
and
blockchain
Technology.
When
the
you
know,
nightmare
of
of
sustainability
is,
is
resolved
within
the
network,
so
we're
really
eager
to
get
rid
of
that,
so
that
more
and
more
folks
can
come
online
without
having
the
you
know,
the
frankly
embarrassing
carbon
footprint
that
ethereum
has
today
there's
also
a
desire
to
democratize.
Access
to
the
network.
B
Proof
of
stake
in
this
case
will
allow
more
and
more
nodes
to
come
online
that
are
not
basically
concentrated
in
the
hands
of
mining
pools
and,
of
course,
there's
Optics
around
the
the
usage
of
these
things,
as
I
mentioned,
and
there's
going
to
be
changes
to
the
economics
of
The
Ether
token
that
we
are
really
excited
about
and
those
around
the
issuance
rate
specifically.
But
there
are
some
other
tweaks
that
I
encourage
you
to
read
about
online
to
how
the
economics
there
work.
B
B
It
will
increase
scale
and
speed
on
the
network,
but
that
is
actually
not
the
case,
but
it
does
set
the
stage
for
some
upgrades
that
will
allow
those
Technologies
like
Roll-Ups
to
become
first-class
citizens
on
the
network,
which
we'll
hopefully
see
a
lot
of
these
improvements
come
down
the
line,
much
much
faster.
Now
that
we're
also
removing
the
biggest
obstacle
to
upgrading
the
ethereum
roadmap.
B
The
Energy
Efficiency
is,
although
listed
at
number,
two
is
personally
my
number
one,
the
you
know:
diversity
and
openness
of
the
network,
as
I
mentioned
as
we
remove
the
need
for
Hardware
intensive
mining
operations
to
participate
more
and
more
validators
and
clients
can
come
online
and
participate
in
the
network
and
we're
going
to
see
I
hope
a
lot
more
Enterprises
join.
Yes,
you
still
need
a
capital
investment
in
order
to
participate
in
proof
of
stake,
although
for
a
lot
of
the
Enterprises
that
I
think
are
are
ready
to
join
the
public
network.
B
B
That
is
really
based
around
the
economic
changes
that
I
mentioned
changes
to
the
issuance
of
ether,
changes
to
the
way
that
if
ether
is,
you
know
burned.
So
essentially
you
know
with
in
combination
with
some
previous
things
mentioned
or
I,
encourage
you
to
look
up
EIP
1559,
then
you
know
we're
going
to
see
a
lot
different
economics
around
the
way
that
ethers
is
operating
on.
A
B
Yeah
yeah
we're
seeing
you
know
basically,
who
has
grown
tremendously
in
the
past
few
months.
We're
really
excited
about
that,
but
it's
frankly
due
to
a
lot
of
the
work
that
people
in
the
community
have
done
to
help
develop
a
client
for
ethereum
mainnet
and
making
sure
that
we
are
doing
press
around
what
that
looks
like
for
diversity,
participation
and
for
getting
Enterprises
involved
into
the
next
slide
key
takeaways.
We
can
I
think
skip
this
I'd,
rather
go
straight
to
questions
exactly.
A
That's
that's
that's
a
longer
I
mean
that's
not
long,
but
it
is
quite
interesting
exactly
what
we're
talking
right
now
around
around
key
takeaways
cool
yeah,
merge,
timeline,
I
think
we're
already
kind
of
like
pasta,
pasties
I,
but
but
it's
quite
interesting
to
have
an
overview.
I
think
bellantrix
was
successful
with
some
bugs
yep.
B
B
B
That
split
is
that
the
consensus
layer
has
been
intentionally
removed
from
the
kind
of
execution,
because
it
one
allows
us
to
run
consensus
in
a
way
that
is
based
off
of
proof
of
stake,
but
two
it.
It
splits
out
kind
of
the
complexity
of
of
executing
and
operating
on
those
smart
contract
layer
from
the
consensus
mechanisms.
B
So
this
doesn't
immediately
provide
the
speed
and
scale
that
we
might
think
with
the
merge,
but
it
will
set
the
stage
like
I
mentioned,
for
a
lot
of
changes
to
the
way
that
those
two
layers
work
separately
to
allow
us
to
make
some
very
interesting
protocol
upgrades
you
might
have
heard
of
of
sharding.
That's
one
of
them
I
encourage
you
to
look
up
eip4844
if
you're
interested
to
learn
more,
but
basically,
as
you
can
see,
still
well
my
head's
kind
of
blocking
it.
But
it's
on
this
bottom
layer.
B
So
the
the
data
availability
that
charting
is
going
to
provide
will
be
on
the
consensus
layer.
So
splitting
these
out
into
two
pieces
has
provided
us
the
ability
to
really
innovate
and
it
allows
Basu
which
sits
in
this
blue
box,
the
execution
layer
to
become
a
lot
more
lean
and
a
lot
more
focused
on
serving
different
types
of
use
cases
and,
at
the
end
of
the
day,
we
get
a
scalable
sustainable
ethereum.
But
we
also
get
a
lot
of
other
kind
of
benefits.
B
Of
this
as
Basu
is
not
just
compatible
with
ethereum
mainnet,
because
it's
an
execution
client
that
we're
interested
in
right.
Here,
it's
executing
evm
based
smart
contracts.
It's
executing
you
know
in
Theory
transactions
that
don't
really
require
kind
of
all
the
baggage
of
the
evm,
and
it's
we'll
get
more
to
this
in
in
the
future,
slides
as
we
go
along.
But
it's
again
splitting
this
out
has
allowed
kind
of
Basu
to
reevaluate
what
we're
looking
at
as
a
client,
and
we
really
want
the
community
to
help
us
kind
of
shape.
B
What
that
looks
like
going
forward,
and
how
can
we
add,
you
know
more
consensus
mechanisms?
How
can
we,
you
know
plug
this
layer
out
and
put
something
else
in
on
the
bottom?
You
know
so
that
means
support
for
different
kinds
of
networks.
Daniel
just
gave
a
talk
on
how
they
use
the
basic
evm
and
hedera.
You
know
in
theory,
you
could
use
the
hedera
consensus
service
to
run
a
network
where
Basu
just
does
the
execution
and
that
doesn't
even
require
using
all
the
overhead
of
the
other
hedera
pieces.
B
A
A
B
For
proof
of
stake
versus
proof
of
work,
so
that's
a
great
question
and
the
you
know
there's
a
bunch
of
different
answers
and
they
all
kind
of
approach
this
from
multiple
angles,
with
the
beacon
chain
itself.
The
the
reason
that
proof
of
stake
is
effective
is
because
there
are
monetary
requirements
to
attack
the
network
so
that
you
know
you
might
have
heard
of
a
51
attack.
B
That's
the
same,
improve
of
work
as
it
is
in
proof
of
stake.
If
you
control
51
of
the
consensus
power,
let's
call
it
of
the
network,
you
can
make
changes
to
the
way
that
The
Ledger
operates,
and
then
you
can
validate
those
changes
with
your
percentage
of
the
network
to
make
sure
that
it
appears
valid
so
in
proof
of
work
that
was
prohibitively
expensive
for
a
number
of
reasons
to
to
to
mining
power,
essentially
requiring
hardware
and
proof
of
stake.
B
There
are
a
lot
of
other
kind
of
nuances
to
how
that
specifically
Works
and
a
lot
of
it
comes
down
to
there's
also
kind
of
self-policing
within
the
network.
After
the
move
to
proof
of
stake,
so
validators
can
slash
or
nominate
to
slash
other
validators
when
they
misbehave
so
say,
I,
try
to
fake
that
I
have
51
of
stake.
B
I
use
my
keys
in
my
validators
to
pretend,
like
I,
have
two
stakes
when
I
only
have
one,
if
somebody
notices
that
fact
they
can
effectively
reduce
my
stake
to
zero
and
are
rewarded
for
that
fact.
So,
I
think
that
we're
going
to
see
you
know
kind
of
these
Watchdogs
come
within
the
network
we've
already.
We
had
our
a
couple
of
slashing
events.
Recently.
B
People
are
I,
hope
incorrectly
putting
their
validator
keys
in
multiple
locations,
but
but
we're
we're
starting
to
see
kind
of
an
uptick
of
people
who
are
penalizing
others
in
the
network,
one
to
reward
themselves,
but
two
to
really
keep
the
network
secure
as
a
whole
to
take
this
into
a
convert
conversing.
But
so
so
your
assumption
is.
Most
of
people
are
going
to
continue
to
keep
the
staking
right
because,
for
whatever
reason.
B
Goes
down
the
network?
Yes,
that
is
true.
We
would
hope
that
everyone
would
not
so
the
question
to
reiterate
for
the
stream
and
for
everyone
that
wants
to
hear
is
that
the
you
know
as
folks
exit
the
network,
the
number
of
validators
would
go
down
and
therefore
the
amount
of
value
needed
to
attack
the
network
will
decrease
yes
there.
B
So
so
there
is
an
example
for
where
you
could
say:
oh
I
would
exit
a
ton
of
validators
over
here
and
then
start
like
a
bunch
really
quick,
so
that
I
have
quickly
have
a
percentage
of
the
stake
and
I
can
take
it
over.
However,
there's
cues
to
both
enter
and
exit
the
network,
so
in
theory
that
a
attack
wouldn't
be
impossible
kind
of
like
as
like
a
flash
loan-esque
exploit
and
two.
The
hope
is
that,
as
we
add,
withdrawals
and
exits
from
the
network,
the
demand
for
staking
will
not
go
down.
B
It
will
go
up
because
the
more
liquid
stake
becomes
the
hopefully
the
more
validators
will
come
online.
There's
also
the
notion
of
liquid
staking
in
general,
where
I
don't
necessarily
need
32e
to
run
these
validators
so
you're,
using
a
technological
approach
to
add
more
validators
to
the
network.
So
there's
things
like
rocket
pool
like
Lido,
where
they
match
up
basically
smaller
Stakes
with
larger
Stakes,
to
create
one
unique
validator.
B
Yes,
you
have
to
presume
that
those
organizations
won't
collude
against
the
network
as
a
whole.
I
think
that
we
are
going
to
see
kind
of
centralization
around
certain
entities
that
control
portion,
large
portions
of
network
stake,
like
big
exchanges,
or
these
groups
like,
like
Lido
Etc,
that
control
a
lot
of
these
Stakes.
But
it
is
hard
to
say
how
this
will
play
out
in
reality.
I'd
encourage
you
to
read
up.
B
Fair
to
say,
maybe
my
understanding
of
how
the
secure
the
network
would
be
is
an
open
question,
but
the
the
again
the
costs
have
moved
from.
Basically,
the
the
hardware
perspective
to
an
actual
stake
in
the
hundreds
of
billions
of
dollars
and
if
you
look
at
the
breakdown
of
the
top
sets
of
validators,
so
you
know
these
accounts,
since
the
validator
keys
are
basically
there's
public
keys
for
all
these
things,
you
can,
in
theory,
look
and
see
who
controls
what
portion
of
stake.
B
B
As
far
as
the
merge
transition
is
concerned,
a
lot
of
the
kind
of
mitigations
come
down
to
like
the
technological
components
as
opposed
to
the
economic
components,
so
we're
feeling
very
confident
in
the
way
that
the
merge
is
going
to
progress
because
of
the
kind
of
one
the
robustness
of
the
actual
consensus
algorithms.
So
the
proof
of
stake
is
based
on
something
called
lmd
ghost,
which
is
just
a
fork,
Choice
algorithm.
B
So
there's
a
lot
of
like
Nuance.
In
that
there's
kind
of
nuanced
mitigations
to
certain
edge
cases,
researchers
have
been
spending
years,
trying
to
figure
out
what
they
could
be
for
this
exact
scenario
once
the
things
level
off
after
the
merge,
I
think,
like
you
said,
we'll,
be
able
to
really
evaluate
what
the
validators
I
think
my
computer.
B
Yes,
but
so
think
about
it,
this
way
as
more
Mission
critical
act,
applications
and
things
migrate
to
the
network.
More
and
more
folks
will
be
participating
directly
or
indirectly
and
you'd
hope
that
more
value
comes
onto
the
network,
distributed
via
decentralization,
whether
geographically,
whether
you
know
politically
to
the
point
where
the
cost
to
intact
the
network
increases
as
there's
more
participation
by
users,
but.
B
B
Potentially
so
it's
a
little
bit
of
a
you
know,
I
guess
the
security
is
the
thing
that
concerned
me
the
most
about
kind
of
moving
to
delivery
system,
s
yeah
yeah.
It's
definitely
a
concern,
but
again
there's
a
lot
of.
None
of
these
things
happen
instantaneously.
There
are
a
lot
of
signals
to
this
kind
of
thing.
B
It
is
a
public
distributed
ledger,
so
you
would
presume
that
nation
states
would
be
watching
what
each
other
are
doing
if
they're
accumulating
hundreds
of
billions
of
dollars
worth
of
eth
in
specific,
you
know,
locales
I,
think
that
would
be
something
that
people
would
want
to
look
at
for
sure.
I
think
we
should,
in
the
interest
of
time,
continue
forward,
but
yeah
I
love.
These
questions.
B
It's
I
don't
know
more
and
more
coming
online
frankly
by
the
second,
as
people
get
ready
for
the
merge,
so
the
the
activation
queue
is
getting
quite
long,
which
is
good
and,
like
I
said,
these
queues
are
designed
in
such
a
way
where
it's
impossible.
You
can't
just
jump
on
the
network
all
at
once
and
can
start
immediately
controlling
a
portion
of
the
stake
and
there
are
also
exit
cues
to
prevent
kind
of
the
opposite,
where
you
can't
just
withdraw
all
of
your
Stakes,
so
that
maybe
somebody
else
has
a
51
stake.
B
Yeah
I
think
we
should
get
straight
to
the
book
about
Basu,
as
mentioned
before,
Basu
is
a
monolithic,
ethereum
client.
What
that
means
is
that
it
essentially
tries
to
do
everything
as
Dana
was
mentioning.
It
serves
a
variety
of
different
use
cases,
not
just
within
proof
of
work
or
proof
of
stake,
but
it
also
serves
bft-based
consensus
algorithms,
and
to
this
point
it's
been
quite
you
know
great.
Actually,
this
is
a
pretty
good
view
of
the
architecture
right
here.
B
B
A
lot
of
the
other
talks
and
a
lot
of
the
other
hyper
Ledger
based
projects.
Their
goal
is
to
bring
evm
compatibility
to
other
things
or
to
create
interoperability
directly
with
the
evm,
and
you
know
again,
I'm
not
here
to
comment
on
whether
that's
a
good
thing
or
not,
but
it
is
what
it
is
and
within
Basu
it
is
a
first-class
Citizen,
and
what
we're
trying
to
do
is
make
a
lot
of
these
other
boxes.
B
Dark,
green
as
well,
where
the
components
are
not
necessarily
stuck
in
this
layout,
and
you
don't
necessarily
need
all
of
these
components.
So
the
reason
that
these
kind
of
things
are
dotted
lines
is
because
they
are
optional.
Those
are
privacy,
related
features.
You
don't
necessarily
need
to
use
them.
You
don't
necessarily
need
to.
You
know,
not
use
them
and
they
kind
of
touch
a
lot
of
different
areas,
which
is
why
things
can
get
kind
of
messy.
B
We
like
this
picture
for
what
it
is,
but
we're
really
trying
to
move
kind
of
towards
a
new
paradigm
and
I
think
that
that's
being
driven
in
part
by
the
fact
that
we
support
a
lot
of
different
network
types
and
that
we
want
to
continue
to
support
different
network
types
and
we
want
to
support
more
Network
types
and
they
might
not
use
pow.
They
might
not
use
proof
of
stake,
they
might
not
use
bft
consensus.
You
know
we
we
want
to
to
kind
of
lean
into
the
plugable
consensus.
B
We
want
to
lean
into
the
fact
that
the
evm
can
go
away
and
you
know,
or
certain
not
go
away
rather
but
exist
in
other
components:
Exist
Elsewhere,
because
our
users
want
different
things.
So
if
we
go
to
the
next
slide
here,
Francesco
like
what
does
this
kind
of
boil
down
to?
What
are
the
users
and
developers
want?
They
want
an
execution
client
for
ethereum
proof
of
stake.
Sure
they
want
to
be
able
to
run
on
mainnet.
They
want
a
client
to
connect
to
a
Consortium
Network.
Maybe
they
want
to
join.
B
B
They
don't
necessarily
know
what
that
means,
and
they
don't
necessarily
know
what
all
of
their
requirements
are
right
now,
because,
frankly,
the
requirements
reveal
themselves
much
further
into
the
line
of
developing
blockchain-based
applications
than
you
would
think
up
front,
and
they
might
want
a
diverse
software
to
connect
to
many
different
kinds
of
networks.
This
could
be
like
you
know,
gnosis
chain,
for
example,
some
other
l1s.
They
we
can
provide
Basu
as
a
piece
of
software
that
connects
to
those
different
things.
It
could
be
a
chain
link
node,
it
could
be.
B
You
know,
a
bunch
of
different
applications
run
semi-adjacent
platforms
to
a
mainnet
ethereum,
or
they
run
entirely
different
chains
with
different
chain
IDs,
and
we
want
to
be
able
to
serve
kind
of
all
these
different
things
or
they
may
just
want
evm
execution.
So
the
users
really
don't
necessarily
know
what
they
want
up
front,
which
is
why
a
monolith
appears
enticing,
because
you
get
everything
in
one
box.
B
However,
we
only
serve
kind
of
the
one
basic
thing
and
if
they
just
want
one
of
these
boxes,
they
have
to
get
the
rest
of
the
crops
kind
of
with
it.
So
what
needs
to
change
right
kind
of
two
things
that
I
view
and
again
these
are.
This
is
a
proposal
for
what
we
want
to
do
with
bases.
So
this
is
an
active
discussion.
We
want
to
actively
bring
people
in.
You
know
we
have
a
binary
distribution,
but
we
want
to
go
to
Binary
distributions
multiple.
We
want
to
move
to
a
proof
of
stake.
Distro.
B
B
Yet
it's
a
new
blockchain
technology
that
hasn't
been
built
yet
I
just
want
an
evm
or
I
just
want
to
run
a
chain
link
node
like
I,
said
and
I.
Don't
need
all
of
the
stuff
to
do
with
proof
of
State
consensus.
I
just
need.
Rpc
I
need
RPC
from
Basu
to
be
able
to
run
queries.
I
just
want
to
get
data
from
the
network.
I
don't
want
to
participate
at
all.
Then
you
can
have
state
storage
within
Basu
and
you
just
pull
the
stuff
out
via
the
RPC.
B
B
This
one
sorry,
this
is
perfect.
Plugable
execution
plug
will
consensus,
possibly
plugable
storage.
We
have
to
figure
that
one
out,
but
it's
something
that
we're
looking
at
very
closely
because
there's
a
lot
of
nice
use
cases
that
are
enabled
by
pluggable
storage
and
then
networking
plugable
networking.
You
know
what
like
that,
that
one
is
unique,
I
haven't.
We
haven't
thought
too
much
through
that
yet,
but
you
know
there.
As
Dano
mentioned,
we
have
different
kinds
of
networking
and
we
have
different
kinds
of
interfaces
that
are
not
just
Json
RPC.
B
How
do
we
create
a
modular
code
base
where
I'm
a
new
developer?
I?
Have
this
basic
client
in
front
of
me,
but
I
know
that
I
have
a
hard
requirement
for
grpc
I
slot.
This
thing
out,
because
you
know
I,
have
a
very
clean
interface
between
Json
RPC
and
my
execution
and
then
I'm
able
to
replace
that
right.
I
have
a
very
clean.
B
You
know
not
necessarily
with
networking,
but
basically
it's
a
it's
a
big
line
in
how
do
we
turn
this
into
a
much
bigger
notion
right,
so
I
think
that
the
client
that
we're
looking
to
build
serves
all
these
use
cases,
because
it's
designed
to
have
exposure
to
what
you
need
and
then
you
can
drop
in
the
rest
and
it's
an
open
source
product
right.
If
I
want
to
tweak
Basu
to
serve
my
certain
needs
or
if
I
want
to
build
a
plug-in
that
extends
the
engine
API
or
extends
the
Json
RPC
I.
B
Not
because
it's
you
know
one,
because
we
want
to
move
to
a
more
sustainable
code
base,
but
two
because
I
frankly
think
that
we're
moving
towards
a
multi-chain
world
that
will
require
you
know
some
or
all
of
these
components,
and
we
want
to
be
able
to
serve
that
because
it's
the
best
way
to
bring
in
more
developers
to
Basu
it's
the
best
way
to
bring
more
developers
into
the
ethereum
and
ethereum
adjacent
ecosystem.
And
you
know
it's
the
best
way
to
build
the
best
execution
client.
We
can.
B
Yeah,
it's
you
know
it's
like
that,
like
the
cactus
team
is
now
becoming
the
cacti
team
and
they're
building
all
these
interoperability
components.
But
imagine
if
you
got
a
lot
of
that
for
free
by
just
exposing
the
low-level
apis
that
you
needed
to
interact
with
the
blockchain
state
and
the
blockchain
virtual
machine,
not
that
I,
don't
like
those
projects.
B
I
just
think
that
we
can
go
bare
metal
on
this
one
and
avoid
a
lot
of
that
stuff
by
opening
up
these
kind
of
four
layers,
consensus,
interface,
execution
and
then
you
know,
the
rest
is
already
essentially
build
your
own
Choose
Your,
Own
Adventure,
because
Basu
has
plugable
storage
to
a
degree.
We
have
several
options
and
you
can
write
your
own
plugins
to
do
whatever
storage
you
want.
B
Anyway,
we
have
relatively
modular
networking
and
we
have
a
kind
of
plug-in
interface
which
I
haven't
discussed
much
because
I
frankly
think
it
needs
kind
of
a
revamp
or
it
needs
to
be
opened
up
a
little
bit
more
or
even
created
into
the
thing
that
I'm
trying
to
describe
here.
But
you
can
already
extend
Basu
to
do
most
of
what
you
want
to
do
through
this
plugin
interface
but
yeah,
it's
you
know,
Legos
Dano
kept
saying
talking
about
Legos
and
it's.
B
B
B
You
go
one
more.
It's
like
a
animation
slide.
I
need
to
get
rid
of
this
crap.
So
why
again,
why?
Why
am
I
doing
all
the
stuff
that
I
just
or
why
is
the
like
the?
Why
do
we
want
to
move
Basu
towards
this
kind
of
new
mission
statement?
And
it's
right
here
right?
We
want
to
enable
Network
participation,
I,
don't
know
what
that
looks
like
in
two
years
and
I.
Don't
really
want
to
know.
B
It's
space
to
enables
Network
participation
for
institutions.
It
supports
ethereum,
post,
merge,
private
networks,
mining
networks
and
we
aim
to
evolve
for
a
multi-chain
evm
compatible
worlds
around.
You
know:
evm
compatible
virtual
machines,
Roll-Ups
hybrid
networks,
side
chains,
more
all
that
good
stuff
with
a
familiar
license,
a
familiar
programming,
language,
institutional
grade
features
and,
hopefully,
keeping
our
nodes
very
low
overhead.
C
B
Pitch
this
is
kind
of
a
boilerplate.
Why
do
you
want
to
do
or
why
do
you
want
to
run
on
public
networks?
So
I
mean
another
of
the
big
reasons
that
you
know
Francesco
and
I
are
here
today
is
not
to
espouse
Basu.
It's
mostly
to
talk
about.
Why
do
you
want
to
participate
as
an
Enterprise
in
public
networks?
This
doesn't
just
mean
ethereum
I'm
talking
everything
like
we
want
to
see
Enterprise,
we
think
Enterprise
will
Converge
on
kind
of
a
main
net
Focus
within
the
future
anyway.
B
So
getting
your
toes
wet
now
is
definitely
valuable
and
we
think
that
Basu
is
a
great
means
to
do
that,
and
it's
rewarding
you
can
get
literally
paid
to
do
this.
You
know,
as
I
mentioned,
there's
a
capital
investment
in
actually
staking,
but
the
staking
rewards
will
likely
be
around
12
post
merge,
which
is
pretty
great.
That
number
will
Go
Down
Over
time.
B
With
your
organization's,
infosec
teams
learning
how
to
set
up
the
infrastructure
in
a
way
that
is
highly
available
and
fault,
tolerant
and
all
that
other
good
stuff
and
making
sure
that
you
have
like
everything
kind
of
squared
away,
so
that
when
again,
when
these
things
come
to
disrupt
what
your
business
does,
you
don't
have
to
be
reactive.
You
can
be
a
little
bit
proactive
because
I
believe
that
a
lot
of
the
public
network
infrastructure
will
disrupt
many
Enterprises.
B
Of
course,
not
all,
but
I
also
believe
that
it
that
enterprises
can
feel
safe
and
secure
in
participating
in
public
networks.
For
a
number
of
reasons,
however,
I'm
working
with
hyperledger
to
provide
a
bunch
of
different
workshops
on
what
that
actually
means
so
I
know.
Antoine.
One
of
the
basic
contributors
has
run
a
great
recently,
a
great
workshop
on
how
to
operate
and
extend
hyperledger
Basu
extend
as
I
mentioned.
There's
that
plug-in
interface,
where
you
can
change
the
way
that
the
client
operates
and
operate
is
self-explanatory.
B
You
have
to
actually
know
how
to
run
it,
but
there
are
more
details.
I
think
the
next
Workshop
is
October
5th,
so
check
out
on
hyperledger,
and
they
will.
The
wiki
has
the
dates
and
I
will
be
hosting
a
workshop
on
Enterprises
running
public
network
infrastructure
and
we
may
even
stake
some
fake
eth,
so
that'll
be
fine.
It'll,
be
cool
yeah.
A
Oh,
no,
no,
that's
the
boring
stuff,
but
I
mean
I.
Don't
know
how
boring
is
that,
but
basically,
like
super
long
story,
short
is
I
mean
I,
don't
know
everybody
saw
the
vitalik
paper
on
on
the
verge.
You
know
merge,
Verge
surge,
all
those
great
namings,
but
literally
it's
what
what
Matt
is
mentioning
post
merge.
Nothing
is
is
finished.
B
B
We
have
left
to
explain,
volitions,
but
I
think
that
the
key
the
key
pieces
as
franchise
mentioned,
is
that,
like
we
are
going
to
continue
to
see
side
chains
and
l1s
we're
going
to
continue
to
see
ethereum
execution,
layer,
consensus,
layer
and
shards
and
then
focus
on
Roll-Ups
here
and-
and
you
know,
what
does
this
all
look
like
is?
Basically
how
do
we
provide
data
to
users
cheaply?
How
do
we
continue
to
scale?
How
do
we
serve
a
multi-chain
world?