►
From YouTube: Hyperledger Besu Asia Pacific Meetup - April 21, 2020
Description
A virtual Hyperledger meetup led by Hyperledger Besu experts and maintainers:
-Rob Dawson, Product Lead, PegaSys (the protocol -engineering group at ConsenSys)
-Joshua Fernandes, Protocol Engineer, PegaSys
- Edmund To, Solutions Architect, ConsenSys
Slides from the event are at:
https://mredmundto-others.s3-ap-southeast-1.amazonaws.com/Hyperledger+Besu+APAC+Meetup+-+Meet+the+maintainers.pdf
For more details about the event, see:
https://zoom.us/webinar/register/WN_0CUyhyBFT2yoqKDJ_QbfYQ
----
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
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 #HyperledgerMeetups #Blockchain
A
Hi
everyone
welcome
for
joining
today's
hi
pleasure,
a
peck
of
virtual
meet
up
on
on
Hyperallergic
basu
so
and
thanks
again
to
hi
pleasure
for
for
hosting
us.
So
my
name
is
when
I'm
a
solution
architect
here
at
consensus,
so
next
I'm
going
to
share
my
screen
to
to
quickly
share
with
you
some
of
the
rundown
on
today's
event.
A
A
So
I
hope
you're
all
seeing
my
screen.
So
next
I
want
to
talk
a
little
bit
about
the
background
of
consensus
and
the
the
background
of
myself
so
so.
Consensus
joint
hi
pleasure
as
a
Premium
Member
last
September
and
and
along
with
that,
we
actually
donated
our
theorem
kyon
written
in
Java.
So
devious.
This
project
was
known
as
a
PV
on
Canfield,
and
now
it
becomes
a
project
called
hyper
ledger
Basu,
which
is
the
topic
of
today's
Meetup.
A
A
So
my
role
as
a
solution,
architect
and
I,
am
under
the
solutions,
department
and
so
I
may
need
help
in
building
production,
ready
function,
solutions
for
all
kinds
of
all
sizes,
whether
it's
enterprises
or
startup,
particularly
leveraging
a
free
unboxing
technologies
such
as
I'm
hyper
education,
and
so
we
have
done
like
work
on
the
department
work
chain,
as
well
as
perfect
proctoring
consortium
network,
as
well
as
smart
contract
later,
such
as
development
as
well
as
auditing.
So
so,
if
your
interest
in
this
base,
I
would
love
to
speak
with
you
after
this
presentation.
A
So
this
is
a
quick
summary
of
some
of
the
work
which
we
have
done
here
consensus.
So
in
the
financial
surface
phase
we
have
worked
with
a
number
of
banks
such
as
sent
and
BNP
paribas
Union
Bank,
as
well
as
exchanges
such
as
SGX
and
and
liquor
share,
which
is
a
project
backed
by
a
UNIX
and
a
number
of
central
banks
such
as
mes
and
self
ethical
reserve
bank
other
than
financial
surface
supply
chain
is
an
area
which
we
have
done
quite
not
projects
in
and
work
with.
A
A
A
You
talk
we
first
on
hyper-aggressive
and
for
everyone
who
has
questions
when
they
are
presenting,
please
feel
free
to
use
the
Q&A
function
in
soon.
So
what
we
are
going
to
do
is
I
will
each
of
the
slide
I
would
try
to
get
at
a
question,
and
we
try
to
hear
your
question
as
we
go
along
in
the
presentation
and
towards
the
end.
We
also
have
a
Q&A
sections
opening
up
before
so
for
for
any
outstanding
question
left
behind,
so
so
with
that
I
think
that's
it
on
me.
B
Thank
you
so
much
Edmund
I'm
going
to
start
sharing
my
screen
and
it
will
look
with
fly
to
look
very
familiar
to
the
one
that
you
just
saw
before.
John
sharing
now,
okay,
so
I'm
going
to
be
talking
to
you
about
Michael
and
Jabez
sue,
Hollinger,
fescue
and
agathis
plus
products
that
we
in
the
Pegasus
group,
the
protocol
engineering
part
of
consensus,
had
produced
how
College
Ebisu
you'll
know
as
a
part
of
the
hyper
ledger
project
you'll,
know,
beginning
to
know
it.
B
Hopefully
more
and
more
it'll
be
a
name
that
you
will
hear
more
and
more.
The
Pegasus
group
consensus
we
made
it
available
and-
and
it
became
first
became
a
part
of
the
hydrologic
group
last
last
year
and
very
recently
had
moved
across
to
being
an
active
status.
The
the
actual
code
base
says
Edmund
was
saying,
comes
from
work
that
we've
been
doing.
B
So
the
pegasus
group
we
are
focused
on
on
enterprise,
which
is
an
important
part
of
our
sort
of
mix
of
aetherium
for
for
enterprise
and
how
we,
we
think
about
ourselves
as
an
organization
and
that
maps
to
two
ways
so
a
match
to
enterprise,
using
cases
of
the
maintenance
of
the
public
network,
that's
available
for
etherium
and
also
are
very
much
enterprise
for
private
and
consortium
chain.
So
those
are
two
areas
we
think
are
very
important
for
enterprise.
B
In
the
white
words,
but
more
revolutionary
I
guess
startup
companies
that
are
that
are
using
etherium
as
well,
and
so
both
of
those
we
see
as
the
groups
that
we
want
to
support
and
make
sure
that
we
are
producing
enterprise
grade
software
with
and
with
enterprise
grade
vendor
support.
That
is,
is
very
much
a
part
of
the
of
the
hydrologic
community.
B
Ecology,
Barry
is
aetherium
and
so
just
sort
of
ground
us
on
some
of
the
foundational
ideas
here
and
so
aetherium
being
a
blockchain
technology.
The
distinctive
flavor
of
aetherium
is
that
it
was
the
the
first
smart
contract
based
technology
that
was
there.
There's
the
the
turing-complete
aetherium
virtual
machine,
which
has
quiet
code,
which
gets
deployed
and
and
runs
on
on
chain
Basu
is
the
node
client
software.
So
it
is
the
software
that
runs
your
transactions
that
it's
responsible
for
taking
the
transactions
that
come
in
put
some
into
Bloxx.
B
B
Where
it's
a
organizational
group
of
organizations
that
are
working
together,
they
will
have
missions
that
control
who
can
get
access
to
the
to
the
chain
and
to
the
information
public
being
very
much
that
distinctive
with
the
etherium
in
this
space
that
it's
it's
available
for
anyone
to
be
able
to
connect
into,
and
so
it's
that
distributed
peer-to-peer
type
type
system.
That's
sitting
there,
that
is,
that
is
the
introduction,
the
the
bird's
eye
view
of
etherium
and
invested
so.
A
B
A
B
B
So
basically,
some
of
those
are
really
high
levels
for
the
features
and
and
what
it
looks
like
as
in
aetherium
point.
The
first
is
at
the
underlying
technology
that
it
was
developed
in
is
Java
to
users
of
the
software.
This,
hopefully,
is
not
something
that
you
are
exposed
to
too
strongly.
Apart
from
the
fact
that
you
need
to
have
a
JVM
on
your
real
machine,
we've
chosen
Java
as
an
implementation
technology
to
make
it
enterprise
friendly.
We
know
that
enterprises
have
Java
running
on
on
hardware
that
is
familiar
and
on
their
virtual
machine.
B
That
is,
there's
a
well-known
tuning
and
performance
monitoring
of
Java
Java
systems,
and
so
we're
able
to
work
in
with
that
and
ensure
that
it's
a
familiar
technology
for
people
to
be
working
with
it's
open
source,
and
it's
got
an
Operations
Apache
2
license,
which
is
actually
an
important
part
before
becoming
a
part
of
the
the
hydrologic
community
and
as
I
was
mentioning
before
it
works
on
both
public
and
permissions
chains,
and
so
we'll
touch
more
on
what
this
sort
of
means.
The
public
chain
for
aetherium.
B
So
the
the
architecture
of
better
and
the
architecture
of
a
software
that
uses
an
interactive
session,
and
so,
as
a
developer
that
wants
to
use
this
technology,
you
will
be
building
your
client
software
as
it's
got
here,
some
sort
of
data,
the
people
call
a
distributed
application
or
you
know
just
think
about
it.
As
like
a
application
software,
that's
interacting
with
the
the
etherium
network
in
your
software,
then
you'll
you'll
have
some
sort
of
client
libraries,
so
there's
actually
well
supported.
B
Client,
libraries
in
many
popular
languages
or
already
so
ago,
Java
JavaScript,
Ruby
all
has
a
theory
of
client
libraries
for
interacting
with
the
etherium
server
software
or
the
etherium
network.
Those
your
client
software
that
you're
writing
will
then
send
HTTP
requests
over
over
the
either
your
private
network
or
over
the
Internet
to
your
underlying
client
software.
Those
requests
will
then
be
processed
at
the
the
JSON
RPC
layer
that
was
got
sitting
here
from
that
the
the
Pegasus
and
the
etherium
client
will
take
that
request.
That
transaction,
maybe
that's
coming
into
the
system.
B
It
will,
if
it's
a
transaction,
that's
coming
in
it'll,
put
it
into
the
etherion
core
transaction
pool.
The
etherium
software
will
then
take
responsibility
for
taking
that
transaction
synchronizing
that,
with
the
rest
of
the
network,
using
our
networking
stack
to
send
it
out
to
the
other
aetherium
blockchain
clients
that
are
a
part
of
your
network
and
and
adding
this
to
their
transaction
pools
within
a
aetherium
network.
You'll
be
running
either
using
a
proof
of
authority
type
system.
B
So
you'll
have
some
sort
of
consensus
mechanism,
I
guess
blocks
in
the
the
block,
tang
and
and
so
the
way
that
those
blocks
will
be
produced
into
either
our
there's
having
some
sort
of
consensus
mechanism
around
the
production
of
those
blocks.
So
there's
either
a
proof-of-work
type
system
similar
to
the
original
bitcoin
consensus
sort
of
mechanism
that
is
there
and
then
there's
within
within
hydrology
bessie.
There's
two
different
proofs
of
authority,
type
approaches
that
can
be
used.
B
So
one
is
the
klique
consensus
mechanism
and
the
second,
which
is
the
one
that
we
recommend
using,
is
if
you're
using
a
group
of
authority
systems
or
I'll
spend
time
talking
about
this
later
on
is
IVF
t2.
So
the
IVF
t2
is
a
Byzantine
fault,
tolerant
consensus
mechanism,
which
means
that
if
you
there
will
be
a
pool
of
validators
that
you'll
have
that
will
be
sort
of
around
there
producing
those
locks.
That
pool
of
ala
daters
will
need
to
have
a
two-thirds
plus
one
majority
of
those
validators
agree
to
produce
a
block.
B
So
that's
kind
of
our
how
things
sort
of
happen
at
this
really
high
high
kind
of
level
within
aetherium
Betsy.
Oh,
when
you
have
a
block
that
gets
produced
as
a
part
of
that
block
being
processed
there'll,
be
a
transaction
processor
which
will
take
every
transaction,
but
in
the
block,
as
we
were
saying
before,
these
transactions
might
be,
are
able
to
be
more
than
just
single
value
transfer,
as
originally
in
in
Bitcoin.
They
can
actually
include
executable
code
as
a
part
of
that
within
the
theorem.
B
Within
these
blocks
that
get
created
and
and
executed,
they
will
update
a
world
state,
and
so
this
is
the
the
shared
kind
of
state
that
you
see
across
across
the
chain
and
where,
where
you
start
to
see
what
would
actually
the
this
current
state
of
affairs
e
and
so,
though,
the
world
state
can
always
be
reached
and
regenerated
by
replaying
all
the
transactions
in
the
chain.
But
it's
actually
your
point
that
clients
will
all
store
the
world
state
to
make
it
efficient
to
access
the
information
about
the
current
state.
A
B
B
That's
right
and
I
think
the
the
other
aspect
of
this
that
that
maybe
was
a
part
of
this
is
hottelet
a
fabric
and
so
there's
currently
some
layer.
So
if
we
think
about
the
underlying
block
protocol
as
a
layer,
1
and
then
things
that
you
build
on
top
of
it
as
a
layer,
2
there's
currently
a
number
of
different
layer,
2
type
projects
which
are
looking
to
provide
ways
of
having
these
two
different
blockchain
solutions
or
pathology
fabric
and
and
aetherium
interacting
together.
Well,.
A
B
So
it
is
not
currently
support
Rask
as
a
pla
consensus
mechanism.
We
we've
looked
at
it,
the
Byzantine
fault,
tolerant,
sort
of
properties.
We
thought
were
were
very
important
when
implementing
our
consensus
mechanism,
and
so
IVF
t2
is
the
one
that
we
have
as
a
initial
sort
of
POA
type
mechanism,
and
we
are
very
open
to
contribution
to
the
project
to
help
it
support
other
contenders
mechanism,
and
so
there
was
someone
that
was
able
to
either
contribute
or
sponsor
the
development
of
a
raft
based
approach.
A
B
B
I'll
touch
on
some
of
these
as
we
go
forward,
I
think,
there's
so
I
guess
the
the
key
things
that
are
there
so
a
channel,
and
when
you
hear
me
people
say
privacy
group
that
starts
to
be
very
similar
to
the
hydrology
fabric
channel
the
idea
of
an
order
within
hi
Felicia
fabric.
The
closest
sort
of
alignment
is
around
the
idea
of
a
validator
inside
of
inside
of
Pathology
best
suit.
B
From
from
the
conversations
that
I've
had
with
some
former
hyper
legit
fabric
developers,
those
are
kind
of
the
the
alignment
points
that
I've
had
very
closely
with
that
I
will
we'll
get
back
to
you
around
around
the
idea
of
peers
and
how
they
fit
into
the
architecture
and
get
a
get
a
better
answer
to
that
than
that
I
can
give
sort
of
on
the
spot
right
here.
Thank.
A
B
I
think
that
the
the
public
aetherium
and
the
etherium
main
that
shows
just
the
the
volumes
of
transactions
that
that
basically
sort
of
runs
well
with,
and
so
some
of
the
the
key
sort
of
things
around
that
underlying
etherion
protocol,
which
are
touched
on
from
the
architecture
slide.
There's
the
etherion
virtual
machine,
which
is
the
execution
environment
for
for
transactions,
there's
the
storage
for
how
the
data
gets
persisted
so
that
world
states
that
are
touched
on
there's
the
dev
P
here
gave
p2p
protocol.
B
B
We
talked
about
the
public
chain,
then
there's
also
the
enterprise
aetherium,
which
is
hiriam
for
private
chains
and
so
there's
a
group,
the
enterprise
aetherium
Alliance,
which
is
specifying
a
a
layering
on
top
of
the
public
main
material
to
work
well
for
consortiums
and
private
Commission
chains
within
that
they
talked
about
the
idea
of
3p,
and
so
they
use
it.
The
three
pieces,
a
nice
way
of
alliteration
and
helping
us
to
think
about
and
remembering
what
makes
Enterprise
etherium
enterprises
area.
B
The
ideas
that
stood
in
with
that
privacy
so
being
able
to
have
private
private
transactions
I'll
definitely
be
diving
into
the
details
of
what
that
means
for
hydrology,
basically
permissioning,
so
being
able
to
control
which
nodes
and
emitting
into
that
peer-to-peer
network
and
which
accounts
can
submit
transactions
into
the
network.
And
the
third
P
is
performance
where
performance
actually
often
sort
of
translates
to
custom
consensus
mechanism.
B
So
I'm
going
to
touch
on
each
of
these
three
P's
now
and
then
that
will
probably
be
a
good
spot
for
us
to
support
your
questions
after
I
get
through
the
next
couple
of
slides
so
without
privacy,
so
that
within
haploid
your
basis
is
I
think
there's
two
sort
of
ideas
that
we
have
around
privacy.
That
I
want
to
highlight.
B
So
the
first
is:
we
think
that
there's
no
one-size-fits-all
our
privacy
solution
and
so
there's
a
number
of
different
privacy
approaches
which
get
talked
about
unused
on
ethereum
and
so
those
things
like
a
zero
knowledge
type
technologies,
advanced
cryptography
libraries
for
using
things
on
on
chain
and
then
there's
an
idea
around,
not
keeping
your
encrypted
data
on
the
public
facing
sort
of
chain
public
being
either
the
public
wide,
aetherium
maintenance
or
public
being
within
your
consortium.
The
the
states
that
every
the
list
of
transactions
that
everyone
can
see
and
so
within
within
their
suit.
B
We
have
an
extension.
A
Ryan
Orion
is
a
tool
for
having
the
private
transaction
that
limits
the
actual
transaction.
The
information
you've
never
sent
is
only
ever
sent
to
the
participants
in
the
private
transaction.
So
this
starts
to
be
very
similar
to
hi
villager
channels
within
within,
with
cut
alleged
fabric
fabric
channels,
start
to
map
into
these
sort
of
private
transactions
they
get
sent
and
they
get
sent
to
this
idea
of
a
privacy
group,
and
so
the
first
thing
that
you'll
do
is
you'll,
create
a
privacy
group.
B
Creating
a
privacy
group
is
a
very
cheap
operation
and
just
as
straight
sort
of
JSON
RPC
request
that
is,
is
not
an
expensive
overhead
operation
to
perform.
Creating
privacy
groups
is
something
that
we
expect
people
there
easily
and
regularly
be
doing
in
a
consortium.
I
then
will,
when
you
submit
a
transaction,
it
will
be
given
off
to
the
Orion
node
to
be
able
to
distribute
around
to
the
participants
in
that.
For
the
members
of
that
privacy
group,
they
will
then
keep
their
own
to
the
private
state
which
they'll
keep
in
sync
between
the
members.
B
What
will
be
written
to
the
public
state
is
a
hash
of
the
transaction,
and
so
you'll
have
this
non-repudiation
record
of
of
the
of
the
transactions
written
to
the
public
sort
of
spaced
purity
LTC.
As
that
information,
then
is
is
available
on
the
on
the
public
for
the
shared
ledger
for
people
to
see
that
there
have
been
transactions.
There
are
techniques
made
available
officer
Kate
the
original
original
of
that,
let
transaction
so
that
you're
not
able
to
track
that
dead
information.
B
And
so
this
gives
a
very
strong
repudiation
and
also
means
that
the
public
chain
starts
to
act
like
an
ordering
service
in
in,
like
an
alleged
favorite
kind
of
sense,
and
so
it'll
be
the
responsibility
of
the
validators
to
be
ordering
the
transactions.
They
will
order.
The
hash
of
that
transaction,
which
will
act
as
the
way
for
them
to
get
that
transaction
ordering
happening.
A
B
B
There's
there's
a
room
for
it
coming
across
to
you
too,
hyper
ledger.
We
expect
that,
as
especially
matures
the
private
transaction
manager
that
it
uses,
we
would
expect
it
to
move
across
to
the
hyper
ledger.
There's
potential,
some
some
transition
that
might
happen
around
that,
and
so
we
want
to
make
sure
that
there's
a
clear
strategy
with
that
technology.
Moving
forward.
B
You
know
you
know
whitelist,
then
there's
also
the
ability
to
control
the
accounts
that
are
able
to
submit
transactions
in,
and
apologies
I,
just
moved
to
black
screen
there
for
a
second,
the
the
other
area
that
we
want
to
highlight
with
our
permissioning
I
mentioned
they
have
whitelist.
So
we
have
a
a
extensive
sort
of
models
around
that
and
governance
models
and
the
ability
to
support
things
like
a
role
based
access
control
during
governance
around
it.
B
A
lot
of
these
things
are
very
strongly
in
our
our
roadmap
for
the
future,
and
we
would
love
to
talk
to
people
about
how
they
would
like
to
see
commissioning
are
working
when
we
talk
about
the
account
commissioning,
so
it's
very
much
around
so
the
the
two
aspects.
Just
touch
on
them
briefly
again,
so
the
note
reasoning
is
to
name
controlling
which
nodes
can
connect
into
the
network.
The
account
commissioning
is
controlling
the
transactions
that
get
submitted
into
that.
B
Next
area,
then,
is
consensus
protocols,
and
so,
as
I
touched
on
before,
there's
three
sort
of
main
consensus
protocols
that
we
have
implementations
of
so
the
eff
hash
creep
of
work
contentious
mechanism.
So
this
is
the
consensus
protocol
of
the
main
main
aetherium
network.
It's
also
implemented
on
the
public
test
nets
are
robson
and
it's
a
proof-of-work
based
system
which
talks,
which
means
that
it
has
the
same
sort
of
properties
that
that
medium
to
that,
then
there's
the
two
sort
of
proof
of
authority
system
city
listed
here.
B
So
we
have
a
queen,
which
is
a
fast
sort
of
protocol
that
has
high
fault
tolerance,
but
does
not
quite
offer
immediate
finality,
and
then
it's
the
idft
to
which
is
actually
coming
from
that
same
tweet
kind
of
family
and
heritage,
but
has
been
updated
to
be
suitable
for
enterprise
use
cases.
You
know
in
our
private
network,
so
one
of
the
sort
of
flagship
properties
of
IBF
t2
is
that
it
offers
immediate
transaction
finality.
B
So
with
this,
and
with
everything
that
we're
talking
about
here,
I'm
sort
of
doing
a
brush
over
of
a
lot
of
very
quickly
over
a
lot
of
big
features,
we
will
share
later
on.
There's
been
a
large
number
of
webinars
and
videos
made
and
presentations
made
about
all
of
these
different
features.
And
so
we
would
encourage
you
to
dive
in
or
to
reach
out
to
us
to
either
edmund
joshua
myself
around
around
this
information
to
help
process
as
well.
Cool.
A
B
Yep
so
I
think
we've
touched
on
some
of
these
already,
but
I
haven't
sort
of
put
up
a
matrix
which
shows
the
differences,
so
I
think
the
some
of
the
keys
that
are
there.
So
the
idft
to
consensus
protocol
is
a
is
based
on
the
IBF
tea
protocol
in
Coram.
There
are
some
additional
enhancements
that
we
made
to
the
safety
and
liveness
of
the
the
protocol
to
make
sure
that
it
works,
has
better
properties
and
fixes
some
edge
cases
are
there
with
the
protocol,
and
so
that's
our
first
to
the
starting
point.
B
The
privacy
group
and
the
privacy
functionality
that
we
have
in
investing
so
is
again
learning
from
the
way
that
quorum
has
done
it.
But
the
idea
of
these
privacy
groups,
where
you
can
also
then
add
and
remove
members
from
a
policy
group
and
they
will
they
will
be
able
to
get
the
historical
state
information,
is
another
sort
of
key
difference.
That
says.
Another
area
that
that's
different
is
is
the
license,
and
so
quorum
is
an
LGPL
sort
of
based
software.
B
B
A
Thinking
so
next
set
of
questions
is
actually
around
it
kind
of
questions
around
commissioning.
So
what
I'm
gonna
do
is
I'm
going
to
like
just
we
kept
all
the
questions
here
and
then
you
can
add
sort
of
address
in
one
go.
So
there's
one
question
about
how
is
on
check
off
chain
commissioning
being
intended?
Second
question
is:
how
can
grow
pace?
Permissioning
can
be
done
using
a
platform
with
regards
to
permission,
to
execute
a
method
on
smart
contract
and
and
the
last
one
is.
A
B
B
The
off
chain
commissioning
is
done
on
a
a
a
else,
a
server
or
node
by
both
by
node
basis,
each
node
will
maintain
its
own,
its
own
whitelist
and
sort
of
commissioning
file
for
the
different
nodes
that
it
can
connect
to
it
and
the
different
accounts
that
will
connect
to
it.
And
so
what
you
would
see
in
this
sort
of
space
is
perhaps
you
might
be
running
a
consortium
across
a
different
group
of
different
organizations,
and
maybe
we
say
for
different
banks.
B
One
of
those
banks
might
want
to
have
within
its
nodes,
have
a
smaller
white
list
of
within
the
four
organizations.
You
might
have
a
white
list
of
all
the
different
accounts
that
are
able
to
submit
transaction,
and
that
would
be
shared.
You
probably
saw
that
on
chain
because
it
would
be
shared
across
everyone
and
then
within
the
individual
organizations.
B
The
individual
banks,
they
might
have
their
own
a
smaller
white
list,
which
limits
the
number
of
the
people
within
there
that
they
would
actually
take
transactions
from
and
when
I
say
people,
it
would
be
the
accounts
which
might
actually
be
more
sort
of
application
level
accounts.
But
that's
that
sort
of
is
where
the
the
sort
of
use
cases
and
things
around
those
on
chain
and
off
chain
types
commissioning
video.
B
When
we
look
at
the
looking
through
the
other
areas
of
those
to
suspend
an
account,
you
would
the
way
we
would
think
about.
It
is
removing
an
account
from
a
whitelist
would
be
the
the
sort
of
leading
way
to
do
that
and
and
being
able
to
have
that
available
there
and
similarly
sort
of
that
black
listing
of
broken
contracts,
so
that
similar
sort
of
approach
as
the
permission
to
execute
a
method.
B
B
That
said,
if
you,
if
you
had
a
system
where
you
wanted
it
to
be
enforced
at
a
protocol
layer,
the
the
smart
contracts
based
commissioning
approach,
so
the
on
chain
commissioning
that
we've
got
is,
is
a
flexible
model.
We've
got
it
well
specified
as
a
set
of
enforcement
interfaces
which
are
used,
and
so
you
could
provide
a
different
implementation
of
that
security
approach
and
use
that
to
to
do
permissions
around
executing
those
specific
methods.
If
that's
the
sort
of
level
of
system
that
you
would
want.
Thank.
A
You
rob
so
we
confront
questions
on
around
privacy
and
now
permissions
may
be
less
answer.
One
question
on
performance
and
then
we
move
on
to
the
further
path.
So
is
there
any
pain
to
support
benchmarking
benchmarking
test
platform
like
hyper
at
your
caliber
in
Basu?
Maybe
you
can
quickly
also
comment
on
the
performance
in
regard
to
some
of
the
consciousness.
Now,
where
from
you,
you
touch
one.
B
Yes,
so
I'll
give
a
good
answer
to
the
first
part,
probably
not
as
good
to
the
in
the
second
part.
So
what
and
I
I'm
really
looking
over
in
my
overview
slide,
I
was
I,
I
know
in
the
agenda.
We
talked
about
having
a
discussion
of
our
telephone,
so
it's
good
to
this
question
has
come
in
because
I
neglected
to
put
a
slide
in
talking
about
holistic
caliber.
B
We
are
definitely
working
with
with
the
telephoto
jet,
so
we
we
use
caliper
for
our
benchmarking
and
it's
used
extensively
by
us
to
reproduce
some
initially,
some
simple
second
numbers
and
we're
doing
some
more
sophisticated
benchmarking
as
well
and
I'll
touch
upon
the
actual
use
case
in
project
where
we're
we're
doing
a
lot
of
benchmarking
work
as
well.
So
we
treat
that
caliper
as
a
first
class
citizen.
We
are
working
closely
and
contributing
pull
requests
against
the
caliper
project
to
ensure
that
it
supports
virtually
well
and
I
expect.
B
This
is
is
something
that
we're
actively
working
on
to
improve
both
the
performance
benchmarks
and
the
underlying
software
at
the
moment.
So
we
have
active
work
from
the
hydrology
community
and
the
bet
who
sort
of
developer
community-
and
the
Pegasus
group
in
particular,
are
working
very
hard
on
on
making
sure
that
we
have
good
performance
there.
Thank.
B
Okay,
I'm
one
of
the
other
areas
that
that
we
want
to
sort
of
highlight
around
it.
So
I
talked
a
lot
about
the
json-rpc
API.
So
these
are
the
traditional
sort
of
well
standardized
ways
are
being
able
to
interact
with
aetherium
I
mean
it
works.
As
for
the
HTTP
host
host
requests
to
to
an
endpoint-
and
the
other
thing
that
you
like
to
highlight
with
the
investor
is
the
support
for
graph,
QL
and
so
graph.
B
We
within
high
village
of
su
support
a
graph
QL
as
a
first-class
citizen
and
way
of
interacting
with
the
client
and
have
an
implementation
of
there's
a
e.
So
E
is
the
etherium
improvement
project
proposal.
Sorry
improvement
proposal,
so
each
has
a
way
that
the
core
sort
of
protocol
is
improved
and
enhanced.
So
there's
a
well
specified
way
of
using
graph
QL
with
superior,
which
is
done
in
the
EIP
1767
within
hydrology.
Basically,
we
implement
and
conform
to
that
that
interface.
B
So,
starting
to
look
a
little
bit
at
about
moving
towards
production,
one
of
the
key
things
that
we
think
is
very
important
with
an
enterprise
software
is,
is
monitoring
and
being
able
to
look
at
your
your
node
and
the
network,
health
and
performance,
and
so
the
other.
The
other
part
of
this
is
being
enterprise,
so
the
software
you
don't
want
to
reinvent
the
wheel
and
adding
another
tool
to
your
monitoring,
stack
and
your
health,
so
we
have
done
this
initially
with
Prometheus
and
katana.
B
We
also
I
think
Josh
will
talk
about
this
touch
on
this
briefly,
that
has
support,
for
the
the
elk
kind
of
stack
is
something
that
josh
is
really
been
driving
and
making
sure
that
we
get
integrated
in
well,
and
so
this
this
got
a
snapshot
here,
showing
you
kind
of
how
it
might
look.
I,
wouldn't
Joshua
does
the
the
demo
he
will
run
through
this.
You
know
in
a
live
system.
B
I've
got
a
couple
more
quick,
slides
to
go
through
one
of
the
other
areas
that
we
think
is
then
so
around
this
is
monitoring
I
think
definitely
after
Josh.
Does
a
demo
is
the
right
time
to
look
into
the
details
there
I
will
quickly
brush
through
some
slides
now
and
and
it
and
give
us
an
opportunity
for
more
questions,
so
our
plug-in
framework
and
is
an
important
part
of
our
software.
B
So,
first,
who
is
it's
designed
to
be
modular
and
extendable
software
to
support
that
we
built
out
a
plug-in
API
but
I
think
there's
too
much
magic
here.
It
sort
of
makes
sense,
there's
an
API.
It
has
a
life
cycle
and
exposes
some
of
the
underlying
services
gives
you
the
ability
to
add
in
your
own
hooks
to
do
things
in
in
different
ways,
so
we
actually
within
our
plug-in
framework,
it's
something
that
Pegasus
uses
to
produce.
It's
it's
Enterprise
version
of
effective
or
the
the
commercial
sort
of
offering
and
supported
version.
B
So
the
the
idea
of
these
plugins
is
something
that
the
hi
villager
Bess.
You
sort
of
development
community
takes
very
seriously
the
the
Pegasus
team,
which
is
one
of
those
sort
of
leading
contributors
very,
very
much
takes
seriously
and
wants
to
make
sure
that
it
works
well
because
it's
how
our
commercial
product
is
built.
On
top
of
that,
we
think
that
that,
and
also
we've
seen
a
number
of
other
use
cases
where
people
are
looking
at
building
their
own
plugins
more
and
more
to
be
able
to
do
custom
things
with
the
underlying
client.
B
These
plugins
currently
are
all
very
much
Java
based
there's
some
some
talk
about
having
a
more
a
and
we'll
run
in
process
with
the
main
sort
of
pursue
client
software.
There's
some
some
thinking
around
how
to
to
do
this
as
a
separate
service
and
hooking
apps
to
to
micro
services.
To
do
that.
That's
potential
for
the
future.
For
today,
the
the
plug-in
framework
is
very
much
around
the
sort
of
thing
sitting
here.
So
the
key
implementations
that
we've
seen
in
in.
A
B
Plus
encrypted
storage
so
encrypting
that
that
well
stage
database
at
when
it's
when
it's
stored
on
disk,
we
use
event
streaming
so
making
the
the
underlying
events
that
are
inside
the
system,
pushing
them
out
to
Katherine
or
sort
of
those
for
a
message
broker
systems
so
that
you
can,
rather
than
holding
the
clients
for
changes
over
the
JSON
RPC
or
subscribing
enviro.
A
WebSocket
they're
able
to
subscribe
to
a
queue
over
Casca
and
be
able
to
add
more
reliably,
see
those
those
information.
And
then
we
have
some
advanced
monitoring
that
we
make
available
as
well.
B
A
B
Yeah
and
so
I
think,
there's
there's
two
different
directions
so
getting
started.
So
if
you're,
a
developer
and
you're
you're
sort
of
wanting
to
get
started
with
actually
contributing
to
the
project,
we
we're
on
github,
there's
a
good
first
issue
and
help
wanted
tags.
So
I
will
share
these
slides
later
on.
B
So
the
links
take
you
to
those
queries
and
we
have
some
excellent
documentation
around
the
software
to
help
you
get
started
within
we're
on
we're
on
the
like
hydrology
R
stands
for
the
hug
logic,
we're
on
rocket
chat,
and
so
there's
a
best
to
and
basically
contributors
channel.
There's,
there's
lots
of
people
that
are
the
maintainer
and
developers
are
available
on
those
channel.
I
mean
for
you
to
interact
with
cool.
A
B
So
there's
there's
not
yet
an
integration
or
exploring
devices.
We
I
think
the
the
the
best
research
community
would
love
to
see
that
that
happen
and
we'd
love
to
collaborate
would
be
exhorting
to
help
make
that
that
work,
but
that's
not
find
that
that's
been
done
today,
there's
yep
so
and
I
guess
in
terms
of
contributing
just
let
me
do
one
more
and
then
and
then
can
move
on.
So
the
the
other
thing
that
that's
really
valuable
is
the
contributor
calls
that
that
list
is
there.
B
So
we
have
I
guess
within
the
the
maintenance,
especially
there's
a
large
numbers
that
are
actually
based
out
of
Australia
and
so
that
forces
the
a
lot
of
the
work
being
done
to
be
done
in
a
pet-friendly
time,
and
so
you'll
see
that
there's
every
there's
calls
to
run
every
two
weeks
on
an
alternating
schedule
between
a
tax
friendly
times
and
then
there's
sort
of
a
European
and
United
States
that
are
friendly
at
time.
And
so
you
can
see
those
those
time
for
good.
A
Thank
you
so
so
I,
just
just
maybe
I'm
going
to
ask
a
set
of
questions
which
is
summarized
on
some
of
this
question
and
then
we
move
on
to
the
next
stage
you
push.
This
set
of
question
is
around.
How
does
hyper
ledger
base
you
compare
integrate
with
other
hype,
energy
project,
so
a
big
area
is
how
how
would
it
compare
high
pressure
best
you
with
hyper
at
your
fabric
like
so
that
is
people
ask
you?
Why
would
you
some
use
some
for
a
go?
A
B
Yes,
sir,
so
at
the
moment
we're
we're
not
using
areas
as
a
library,
the
sort
of
execution
and
the
environment
sort
of
I
guess
a
lot
of
it
predates
its
inclusion
into
the
hyper
ledger,
sort
of
foundation
and
the
hardware
organization,
and
so
I
think
there's
room
for
sort
of
changing
different
implementations
of
things
as
we
move
forward
in
terms
of
interrupts
and
working
with
with
fabric.
So
I
think
that
we
very
much
see
that
as
a
layer
to
sort
of
peace.
B
At
the
moment,
the
direct
different
client-to-client
integration
is
done
at
that
higher
layer
in
the
stack
rather
than
at
the
actual
low
level
protocol
in
terms
of
their
services
fabric.
I
think
that
the
the
etherium
sort
of
story-
and
the
thing
that
you
get
from
bases
is,
is
that
public
sort
of
main
net
support
the
Interop
with
other
networks
and
other
ethereal
networks.
A
lot
of
this
at
the
moment
is
it's
still
a
little
bit
aspirational
and
and
it's
kind
of
building
software.
B
Now
that
is
going
to
work
in
the
future
for
the
world
that
we're
going
to
see
and
I
think
that's
the
key
sort
of
thing
around
that
that
base
to
sort
of
spot
is
particularly
on
somewhere,
maybe
as
a
when
you
think
about
a
private
mission
chain.
Maybe
maybe
there's
elements
where,
where
fabric
is
still
our
head
in
some
of
those
specific
use,
cases
I
think
best
suit
and
Enterprise.
B
Etherium
are
very
strong,
compelling
options
to
consider
for
any
as
their
enterprise
network,
but
I
think,
particularly
if
you're
thinking
about
how
you
might
want
to
interact
with
the
public
sort
of
chain.
If
you're
thinking
about
the
the
scalability,
the
future
proofing
of
your
will
work.
I
think
that
aetherium
provides
a
great
platform
to
do
that
on
enterprise.
B
Aetherium
is
a
way
of
getting
the
the
consortium
and
of
privacy
and
missioning
sort
of
properties
that
you
need
for
now
and
best
use
sort
of
offers,
both
of
those
so
I'm
a
I'm,
an
aetherium
etherion
fan,
as
they
probably
not
getting
the
most
unbiased
answer
to
that
question.
But
that's
that's
the
answer
that
I
have
cool.
A
B
C
B
We
offer
a
large
number
of
scripts
to
help
enable
getting
your
Jeannette
works,
going
in
a
production-ready
way,
so
ansible
docker,
kubernetes
terraform
or
on
AWS,
as
you
are
in
the
z-row
marketplace.
There's
these
number
of
examples
that
are
available
for
it.
We
so
we
provide
the
the
automation
and
tools
to
help.
Make
that
easy
easy
to
do.
C
Thank
you
room
good
evening.
Everyone
all
right
so
before
I
jump
into
the
sample
networks,
I'll
quickly
touch
on
the
dashboard
itself
and
why
we
recommend
using
this.
So
this
is
one
of
the
key
things
that
we
recommend
people
start
deploying
right
from
when
they
deploying
the
network
itself.
Reason
being
it
gives
you
a
lot
of
insights
into
how
your
network
is
performing
as
a
whole,
but
also
how
each
individual
node
is
performing.
C
So
you
get
early
warning
signs
of
maybe
nodes
going
down
or
you're
running
out
of
disk
space,
or
you
know
some
great
error,
and
you
know
maybe
some
other
process
is
going
wrong
and
CPU
has
spiked
soft-touch
on
this
first,
so
row
right
up
top.
This
is
something
very
near
and
dear
to
my
heart,
I
like
to
have
clean
overview
of
all
the
nodes
that
we
have
so
I've
spun
up
a
few
in
last
week.
C
All
these
are
public
notes
on
public
network
sorry.
So
there
is
a
few
main
net
drops
to
in
rinkeby
and
a
couple
in
goalie
and
what
you
can
see
straight
off.
The
bat
is
the
chain
height
of
each
node,
as
well
as
the
target
chain
height
and
as
it
gets
to
the
target
chain
height.
This
should
be
zero.
Eventually,
things
like
block
number
you'll,
eventually
see
like
for
the
golian
ring.
It
could
be
ones
when
they
eventually
come
back
to
normal.
C
We
generally
don't
like
seeing
these
about
15
seconds
give
or
take,
and
you
can
alert
on
every
single
thing
over
here.
So
when
you
have
a
new
node
come
up
on
a
public
network
by
default,
they
generally
use
fast,
sync.
So
on
this
for
any
nodes
that
come
up
automatically,
you
get
a
view
of
what's
going
on
in
the
fast
sync,
so
you
can
see
these
two
main
net
notes
I'm
far
from
reaching
their
heads,
but
there's
one
in
here
that's
quite
broken,
and
it
works
very
well
for
this
demo.
C
C
So
this
gives
you
an
overview
of
all
the
CPU,
so
you
can
again
put
an
alert
across
the
entire
lot
and
if
anything
goes
over
a
certain
threshold.
You've
got
an
alert
that
comes
to
you
and
you
can
set
up
early
warning
systems.
You
don't
have
to
wait
little
things
go
really
bad
garbage
collection
is
another
key
thing,
so
if
we
generally
like
to
see
all
nodes
hovering
around
about
0
to
maybe
5%
in
this
case,
this
is
a
very
good
example
of
something
gone
really
really
wrong
here.
C
So
if
I
see
a
garbage
collection
where
the
drafts
going
like
this,
it's
very
bad
and
straight
away,
I
know
I
can
jump
into
the
box,
and
I
can
have
a
look
and
see
what's
going
on
similar
process
for
memory
now,
I
just
to
get
going
quick
start.
The
main
thing
that
we'll
touch
on
today
here
is
the
QuickStart
or
the
sample
in
books
repo.
C
So
this
is
a
very
quick
way
of
getting
you
up
and
running
on
your
platform
of
choice
so
that
we
do
Linux
Mac
as
well
as
Windows
and
you've
got
its
it's
sort
of
a
pick,
a
user
scenario
that
matches
your
needs.
So,
for
example,
if
you're
a
dev
developer,
you
only
may
need
just
the
blockchain
bare
minimums
of
monitoring
if
you're
a
sysadmin
you
may
care
about
logs
and
so
on
and
so
forth.
C
C
You
can
start
things
up
and
say,
for
example,
if
you
were
a
deaf
developer,
you
can
spin
everything
else
up
here,
and
you
only
know
that
your
DEP
just
replaces
this
orange
box
and
you're
good
to
go,
and
the
last
thing
that
we've
done
to
make
things
really
easy
for
people
to
adopt
and
get
used
to
things
is:
we've
got
video
tutorials
scattered
in
between,
so
you
can
see
a
lot
of
examples
of
how
things
work
and
there
you
click
on
them.
They
clink
back
here.
C
So
to
answer
some
of
the
questions
we
had
on
commissioning
for
you
can
allow
or
disallow
nodes
there's
a
good
example
in
here.
We've
got
a
deaf
that
comes
up
and
you
can
on-the-fly
disallow
nodes
the
same
for
privacy
as
well
as
for
taps
as
well.
So
in
the
demo
today
at
least
the
first
one
will
be
covering
this
use
case
over
here.
C
So
we've
got
four
nodes
on
the
network:
one
idft
to
network
an
explorer
over
there
monitoring
setup
that
I've
just
covered
over
there
and
we've
got
logs
recent
addition
that
we've
had
to
this
is
that
we've
got
support
for
elk
natively.
Now
so
any
logs
that
you
have
as
well
as
this
dashboard,
if
you
don't
want
to
run
from
you
dissing
Ravana
separately,
in
your
interest,
you
can
just
run
native
elk
and
you
have
the
same
dashboard
replicated
over
here.
So
you
get
exactly
the
same
things.
C
C
So
for
all
the
base,
your
nodes,
so
I
can
go
if
I'm
only
interested
in
just
the
messages.
For
example,
we're
not
really
interested
in
everything
else.
I
can
see
everything
over
there
and
because
I'm
running
a
local
set
up
over
here,
you
can
see.
I've
got
containers
over
here
and
I
can
drill
down
on
one
specific
container,
and
so
we
use
this
to
quickly
see
water
logs
coming
out
of
a
single
machine
and
same
if,
if
there's
something
going
wrong,
you
can
see
this
very
quickly
over
here.
C
C
But
basically
you
see
the
four
validators
over
there.
There's
one
RPC
know
that
comes
in
excess,
so
you
make
any
RPC
calls
to
it
all
the
code
for
this
lives
in
here
and
we've
got
documentation
for
it,
and
the
second
example
that
I
will
quickly
touch
on
and
then
I'll
move
on
to
some
of
our
other
deployment
mechanisms
and
tools
that
we
offer
is
the
kubernetes
repo
that
we
offer.
C
So
we've
got
setups
from
just
basic
IB
ft2
we've
got
setups
with
privacy
with
attach,
as
well
as
a
full-blown
consortium.
So
if
you
want,
you
can
go
down
to
the
level
of
having
a
consulting,
which
just
has
your
validators
in
there
a
another
name
space
for
just
members
and
another
namespace
for
monitoring.
One
thing
I'll
add
is
that
with
all
the
setups
you
get
a
clean
separation
of
a
namespace
just
for
all
the
Basu
nodes
and
things
that
you
have
and
there's
another
name.
Special
monitoring,
so
I'll
quickly
jump
into
that.
C
So
I've
got
a
local
mini
cube
set
up
running
over
here.
I've
got
four
nodes
in
here,
and
I
can
quickly
jump
in
checking
logs
and
everything's
humming
away
quite
nicely.
The
same
dashboard
is
available
whoops.
Well
this
one
over
here,
so
I
got
five
nodes
over
there.
The
same
block
time
blocks
behind
everything
runs
up
nice
and
clean
and.
C
C
When
you
get
the
whole
overview
of
how
everything
works
at
that
particular
one
was
this
the
hill,
my
bf
t2
variant
for
those
of
you
that
are
deploying
this
in
cloud
platforms
in
AWS,
GCP
or
Anzio?
We've
also
got
Congress
rules,
so
you
can
have
an
ingress
controller
that
routes
to
the
co-founder
dashboards,
as
well
as
to
the
RPC
node.
So
instructions
are
all
over
here.
I
haven't
got
this
in
this
demo,
because
I
don't
have
enough
time
to
cover
that
so
quickly.
I
want
to
touch
on
a
couple
of
other
things
in
this.
C
Is
that
you'll
see
that
absolutely
nothing
is
deployed
in
default?
What
you
instead
have
is
everything
is
put
in
a
BC
namespace
and
we've
got
everything
down
to
our
backs
further
down
here.
So
each
validator
has
its
own
policy
that
you
can
that
it
gets
the
keys
in
secrets
in
and
for
those
of
you
all
that
have
ad
and
things
like
that,
a
new
one
restrict
users
to
only
using
a
certain
node
or
have
access
to
certain
validators.
You
can
easily
tap
onto
these
are
back
policies
and
force
your
own
atom,
and
we
welcome.
C
Okay,
so
all
of
these
have
automatic
monitoring,
as
I've
mentioned
earlier.
So
to
maintain
our
fleet
of
nodes,
we
heavily
use
a
ansible
role,
which
provides
you
things
like
a
systemd
service
that
you
can
go
start/stop
so
on.
There's
support
for
logging,
this
work
for
environment
variables
and
so
on
and
so
forth.
So
this
is
used
by
us
pretty
much
in
most
places.
We
also
support
tarah
forms
if
you
have
ews
or
as
your
setups
we've
got
them
here.
C
B
A
Thank
you
rob,
so
maybe
you
can
take
one
question
here
which
is
jerry
around
this
topic.
So
there's
a
question
around
it's
a
kid
which
I
think
there's
the
one
we
show
is
that
it's
an
open
source
or
is
a
pipe
into
the
tools
may
be.
I
think
it's
good
for
you
to
touch
on.
Ok,
so
for
all
the
stuff
that
you
show.
Ok,
what
what
I
would
our
open
source,
what
are
some
of
the
commercial
offering
particular
I
guess
audience
today.
A
lot
of
them
are
the
Pampas.
B
Yes,
so
the
vast
majority
of
everything
we've
got
is
open
sourced,
and
so
the
samples
and
everything
that
we
are
looking
at
today
were
all
open
source
everything
that
open
source
that
we
we've
got.
We
we
very
strongly
default
to
an
Apache
Apache
based
license
to
make
it
our
missile
and
easy
to
work,
with
the
only
exceptions
that
you're
ever
see
on
a
Pegasus
repo
will
be
if
it's
a
a
for
given
as
a
library,
and
so
we
call
it
carry
on
with
the
license.
B
That
was
there
just
because
that's
what
you
have
to
do,
and
so
the
the
sample
networks
that
we're
looking
at
there,
the
kubernetes
and
other
areas
as
they
are
all
available
under
an
Apache
License,
the
the
more
commercial
things
were
some
of
the
features
that
I
touched
on
earlier,
so
which
are
which
are
done
by
a
plugins
Bessie.
So
that's
the
the
advanced
validator
monitoring,
so
the
function
is
I
touched
on
very
briefly,
the
event
streaming,
so
the
task
curse
or
the
integration
and
database
encryption
at
rest.
B
So
those
three
things
are
hard
requires
that
sort
of
commercial
license,
but
the
rest
of
our
software
is
open
source
and
we
take
our
open
source
for
the
community-
very,
very
importantly,
within
in
Pegasus
and
very
much
this.
This
conversation
that
we're
having
today
is
very
much
around
the
the
open
source,
hi
Balaji
Basu,
sort
of
project
where
we
will
I'm,
Josh
and
I,
avoid
you
know:
full
disclosure,
a
part
of
consensus
and
Pegasus,
and
so
we
come
with
that
sort
of
direction.
B
A
B
You
so
so
so
really
quickly,
I
guess,
with
with
the
the
things
that
we're
talking
about
I,
think
having
vendor
support
is
a
useful
thing.
So
this
is
my
put
on
my
Pegasus
show
strongly
and
say
to
think
about
having
the
vendor
support.
We
would
love
to
do
that,
but
I
don't
want
to
spend
much
time
on
that.
I
want
to
actually
focus
on
some
of
the
key
use
cases,
and
so
it's
industry,
agnostic
software,
there's
use
cases
and
people
working
on
a
banking
financial
services
supply
chain
in
healthcare.
I.
B
Guess
a
lot
of
the
different
use
cases
that
the
admin
is
putting
up
early
on,
either
on
on
and
using
Bessie
currently
or
on
the
path
to
using
better
and
we've,
had
I
think
since
becoming
a
active
part
of
high
college
and
active
project
in
in
hyper
ledger,
which
is
something
that
happened
recently.
It's
been
another
sort
of
moment
for
us
where
we're
seeing
greater
and
greater
uptake
with
it
bursaries
being
active,
is
a
strong
indicator
that
is
not
tied.
Just
to
to
Pegasus
is
a.
B
It
is
a
true,
a
true
first-class
part
of
hyper
ledger.
So
there's
two
use
cases
in
particular
that
I
want
to
touch
on
just
now.
The
first
is
lack,
Jenk
and
so
like
chain
is
the
say,
a
consortium
that
can
set
it
up
in
the
license:
Latin,
America
and
Caribbean,
so
la
si,
and
then
it's
a
chain
so
block
chain
like
chain.
B
If
the
the
purpose
of
life
chain
is
producing
shared
blockchain
infrastructure
for
the
region
and
so
they're
running
that
and
so
there's
a
consortium,
that's
available
for
the
Latin
American
Caribbean
sort
of
region
which
is
running
on
on
pursue
using
using
all
of
the
features.
So
it's
using
the
IVF
t2
it's
using
permissioning
to
control
connecting
to
the
network
and
using
the
privacy
features
as
well.
B
B
Josh
is
sort
of
been
working
with
them
as
well
to
make
sure
that
the
performance
through
porch
and
understanding
their
the
characteristics
of
what
happens
with
the
smart
contracts
that
they've
got
there.
It's
a
project
and
finished
early
early
days,
but
is
looking
to
be
a
very
useful
tool
for
for
their
that
consortium
in
I,
guess
helping
to
attract
and
prevent
the
the
spreaders
coronavirus
in
the
in
Latin
America.
B
Another
another
use
case
to
highlight
is
head
Hara,
so
I'd
Hara
is
a
Bay's
a
partner
with
with
Pegasus.
They
have
developed
a
number
of
solutions
on
top
of
a
spear.
Remember
sue,
so
the
one
to
highlight
is
that
they've
brought
to
a
token
floss
products
that
they
deployed
to
the
South
African
Stock
Exchange
Zarek's,
to
do
like
it.
B
Talks
about
here
distributed
settlement
system,
four-year
trusts,
and
so
this
is
is
built
on
top
of
built
on
top
of,
has
alleged
best
food
and
is
running
successfully
in
that
world
at
are
using
Betsy
as
their
kind
of
choice
for
a
number
of
other
projects
and
partnerships
which
we'll
be
able
to
talk
about
more
and
more
in
in
the
future.
It's
still
sort
of
early
days
as
some
of
those
other
other
projects
and
things
that
they're
they're
working
on.
B
Those
are
a
couple
of
the
use
cases
and
things
to
touch
on
there.
We've
got
a
bunch
of
sort
of
links
to
help
you
kind
of
get
started
and
think
about
using
using
Betsy.
So
our
documentation,
which
is
I,
think
you
know
maybe
I'm
a
little
bit
biased
but
is
is
excellent.
It's
definitely
above
and
beyond
any
of
the
other
etherion
based
elements
of
documentation.
It's
I
think
one
of
the
the
actual,
distinct
Goo's
for
us
as
a
product,
and
so
that's
available
on
the
Hippolyta
for
the
site.
You
can
see
basically
Judith
org.
B
We
had
the
the
sample
networks
and
kubernetes
github
repos,
which
Joshua
shared
again,
as
I
mentioned
before.
These
are
open
source
repositories
that
that
Pegasus
hosts
there's
the
the
main
github
repo,
which
is
hydrology
under
the
hi
villager
github
organization,
and
it's
the
best
suit
repo
there
and
we've
got
a
link
to
the
wiki
again.
These
slides
are
ones
that
I'll
share
later
so
that
you'll
be
able
to
have
access
to
them.
B
A
Thank
you
all
and
thank
you
Joshua,
so
so
what
I
do
now
is
I
know
some
questions
we
didn't
quite
address,
but
we
would
sort
of
go
for
the
remaining
questions
feel
free
to
drop
in
the
board.
So
that's
one
question
being
asked
pretty
early
on
in
the
conversation
and
that's
the
special
support.
If
okay,
it's
talking
about
what
is,
if
we
run
and
what
it
does
or
not
or
yeah
or
what
is
what
is,
what
is
Pegasus
pant
is
a
pony
for
him.
Yep.
B
B
B
The
the
beacon
chain
itself
is
initially
being
implemented
as
a
thing
that's
separate
to
Tibet,
so
we
are
not
including
a
beacon
change
support
inside
of
the
zoo
in
the
initial
sort
of
view
of
the
world
as
the
technology
and
what
it
does
is
is
quite
different
to
have,
as
you
kind
of
works,
currently
the
beacon
chain
of
work.
The
initial
sort
of
public
test
network
schedules
will
be
happening
any
day
now
and
then
from
that,
we
there's
an
expectation
of
after
about
three
months.
So
far
we
around
July,
maybe
August.
B
That'll
then
follow
with
sort
of
test
nets
around
the
real
sort
of
charges
for
the
environments,
the
architecture
and
exactly
how
the
sharding
and
cross
shard
communications
and
everything
happened,
is
still
being
fleshed
out
and
and
researched.
What
there's
a
thing
talking
a
lot
about
what
the
execution
environments
for
each
different
shard
will
be,
and
so
those
different
execution
environments
or
what
that
is
going
to
look
like
sort
of
changes
and
moves
a
little
bit.
B
It's
expected
that
one
of
the
leading
initial
execution
environments
will
be
the
EVM
and
so
will
look
very
much
like
what
the
current
enterprise,
deuterium
and
etherium
looks
like
and
so
I
think.
There's
a
lot
of
a
lot
of
work
and
research,
that's
being
done
still
on
a
theory
into
it's
still,
I
think
for
thinking
about
it
in
terms
of
enterprise
use
cases
right
now.
This
barium
two
is
the
future,
but
we're
still
a
little
ways
away
from
it.
B
The
expectation
is
that
there
will
be
a
clear,
very
clear
transition
from
best
soo,
&,
etherium
and
Enterprise
aetherium
to
aetherium,
and
how
that
how
that
works?
I
think
we
it's
too
early
to
say
exactly
what
they're
going
to
look
like,
but
I
think
there's
strong
commitments
from
the
the
best
few
maintenance
community
to
make
sure
that
that
transition
is
as
seamless
as
possible
and
I
think
it
will
be
quite
seamless
for
the
enterprises
that
start
using
BES
you
now
to
make
sure
that
they
are
able
to
work
well
into
an
aetherium
to
future.
A
Questions
and
then
you
can
share
a
little
bit.
Okay,
if,
if
there
are
further
questions,
I
hope
today's
event
is
just
just
definite
the
beginning.
So
if
for
all
the
attendance
here,
if
you
have
further
questions,
feel
free
to
join
a
rocket
chair
for
myself,
you
can
reach
me
on
the
gain.
If
you
have
any
further
question
in
regard
to
pursue
Pegasus
consensus.
So
the
last
question
we
take
here
so
any
idea
when
the
that,
if
we
library
Nephilim,
who
have
extension
to
support
privacy
transaction
ambassador,
as
he
already
support,
form.
A
A
So
maybe
we
I
take
one
more
question,
so
it
is,
there
is
there's
a
question
around,
and
can
you
share
a
little
bit
of
the
work
that
we
have
done
with
LVMH?
So
maybe
I
take
this
one,
so
particular
France
team
is
working
with
LVMH.
So
every
actress
is
a
consumer
goods
manufacturer
and
they
have
a
lot
of
products,
in
particular
in
the
area
of
luxury
product
like
handbags
and
all
this
and
the
work
that
we
are
doing
is.
A
We
are
using
approaching
in
the
likes
of
punching
area,
to
check
in
the
individual
goods
that
are
making,
let's
say
a
handbag
and
we
are
leveraging.
Some
of
the
tokens
specification
in
particular
around
are
what
we
call
non-functional
token
so
ERC
seven
to
one,
which
is
certain
representations
on
on
approaching
which
you
can
represent
as
a
single
unique
asset
on
a
project
which
is
similar
to
you.
Let's
say
if
you
have
a
luxury
goods,
so
that
is
yeah.
So
there
is
a
quick
answer
on
the
work
that
we
are
doing
in
France.