►
Description
A recording of a webinar session led by Ethereum experts who work in the field everyday and build some of the leading Ethereum projects in Hyperledger. The Ethereum leaders will discuss:
Give a brief technical overview of Cactus and Besu
Demo of Cactus and Besu
Technical Overview of Ethereum
Answer your questions
Note: This is the second session of Hyperledger’s Introduction to Ethereum series. To view the prior session introducing how Ethereum fits into the Hyperledger community, visit our video library.
More about Besu is at: https://www.hyperledger.org/use/besu
More about Cactus is at: https://www.hyperledger.org/use/cactus
Our video library is at: https://www.hyperledger.org/learn/webinars
----
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 #HyperledgerMemberWebinars #Blockchain
A
B
Great,
let
me
go
ahead
and
share
my
screen
thanks
everyone
for
joining
very
excited
to
have
you
here.
Hopefully
you
guys
know
you're
in
the
right
place
and
we're
here
today
talking
about
ethereum
within
the
hyperledger
community.
This
is
part
two
of
a
series.
This
session
will
be
a
little
more
technical
than
the
last
session
we
had.
If
you
haven't
already
seen
our
first
session,
we
highly
recommend
you
check
it
out,
but
not
a
prerequisite.
You
know
this
will
just
be
covering
slightly
different
things.
B
B
C
D
B
D
B
Perfect,
so
moving
us
along
quickly
here
as
the
agenda,
so
we're
going
to
cover
a
few
things,
but
I
like
to
say
this
is
a
not
your
typical
webinar.
This
is
not
us
talking
at
you
for
45
minutes
or
an
hour.
He
wants
to
be
highly
collaborative.
We
want
you
to
ask
questions,
jump
in
that's
why
we
have
everyone
able
to
mute
and
unmute
themselves
use
the
chat,
ask
questions
all
that.
B
So
essentially,
we've
prepared
some
information
in
some
slides,
but
if
there
are
no
questions,
this
would
be
over
very
very
quickly.
So
don't
be
shy
is
the
point
this
is
you
know
for
your
learning,
your
education
and
we're
here
to
be
a
resource
to
you
so
anyway,
but
what
we
will
cover
kind
of
looking
at
the
bullets
we
have
on
the
side,
so
we
will
do
a
quick
recap
of
ethereum
and
and
how
it
fits
into
hyper
ledger.
B
B
B
A
A
B
14
now
pretty
good
okay,
so
it
looks
like
the
majority
are.
The
winner
is,
I
know
some
about
ethereum,
so
it's
good
to
know
and
then
just
getting
started
and
excited
to
learn
more
is
is
the
second
is
about
half
the
group
and
then
one
person
is
an
expert,
so
this
is
great.
This
is
why
you're
here
we're
here
to
help
you
become
experts,
maybe
slowly
and
yeah,
just
feel
free
to
jump.
In
with
any
questions
you
have.
B
So
maybe
just
taking
a
moment
what
is
ethereum
ethereum
is
the
open
source
blockchain
it
launched
in
2015..
It
has
one
of
the
largest
developer
communities
in
the
world
for
blockchains.
I
think
it's
at
over
250
000..
It's
often
considered
the
most
programmable
blockchain
for
creating
decentralized
applications
and
smart
contracts.
B
You
can
use
ethereum,
so
it's
a
public
public
blockchain,
but
then
there's
also
flavors
that
we'll
talk
about
with
baesu
and
others
where
it's
also
permission
blockchain.
So,
if
you're
familiar
with
permission,
blockchains
or
permission
dlts,
you
can
also
use
it
for
that
lucas,
peter
anything
else
to
add
to
kind
of
set
the
scene.
C
C
B
Sometimes
we
get
the
question
you
know:
what's
the
difference
between
hyperledger
and
ethereum
and
in
fact
there
are
ethereum
projects
in
hyperledger,
including
and
basu
and
cactus
also
interact
with
ethereum
baesu
is
the
enterprise
ethereum
client,
that's
written
in
java,
which
we'll
talk
about
a
lot
with
lucas
burrow?
Is
the
permissionable
smart
contract
machine
or
an
evm
ethereum
virtual
machine,
then
there's
avalon
and
then
there's
a
cactus
peter.
Do
you
want
to
give
a
quick
intro
to
cactus.
D
Yeah,
just
a
30
second
version
of
it,
because
we
really
want
to
look
fast
is
that
cactus
is
a
framework
for
integrating
or
interoperating
different
distributed
ledgers.
So
it's
not
its
own
ledger.
It's
there
to
help.
You
create
applications
that
have
to
deal
with
multiple
lectures.
At
the
same
time,
it's
sort
of
an
sdk
of
sdks.
B
Hello,
sdk
sdks,
I
think
so
when
you're
looking
at
kind
of
hyperledger
and
you're
thinking
about
all
of
you
know,
it
is
kind
of
a
greenhouse
for
enterprise,
blockchain
vlts
libraries
tools
labs,
as
you
can
see
in
kind
of
this
view,
and
it's
pretty
cool
that
you
know
it's
not
necessarily
hyperledger
versus
ethereum.
It's
actually
kind
of
it
all
fits
together
pretty
well
and
you
have
kind
of
different
options.
B
So
you
know
I
like
to
say
that
if
you're
thinking
about
getting
started
with
blockchain
or
distributed
ledgers,
go
to
hyperledger
and
you'll,
be
able
to
see
kind
of
there
are
a
bunch
of
different
flavors.
You
can
figure
out
what
works
for
you
and
and
and
get
a
good
sampling
of
what's
out
there
by
just
coming
to
this
group.
A
B
B
A
B
Currently,
the
consensus
team
builds
both
hyper
ledger,
baysu
and
gokura,
and
and
we're
team
that
work
on
both
of
them
but-
and
I
guess
to
be
clear:
there's
not
a
yeah
they're,
both
being
worked
on
by
the
consensus
team.
So
I
think
your
question
was,
you
know
the
gokurum
project.
Has
it
stopped
and
the
answer
is
actually
no.
Both
of
the
blitz
are
working
on
and
what's
kind
of
cool
is
when
you're
thinking
about
enterprise,
ethereum
and
ethereum
projects
generally
in
enterprise
dlt.
A
B
B
Great
okay,
so
we
have
another
poll
for
you
all
to
participate
in
so
we'd
love
to
hear
what
problems
are
you
trying
to
solve
with
using
a
dlt
data,
traceability,
security,
collaboration,
lower
cost?
Maybe
maybe
transaction
fees
or
do
you
want
to
have
productivity
increases
to
your
business
or
maybe
there's
something
else
if
so
drop
in
the
chat?
We'd
love
to
get
your
feedback.
C
But
I
think
one
concept
that
not
everyone
understands
is
that,
like
mainnet
is
only
called
main
app
because
it's
open
and
everyone
wants
to
join,
but
there's
nothing
preventing
people
from
studying
their
own
nodes
and
you
know
building
a
network
for
themselves.
It's
almost
like.
I
don't
know
if
you
think
about
a
you
know
one
of
those
wiki
internal
websites
that
only
the
company
has
access
to
or
something
you
can
view
those
kind
of
networks
to
fit
your
needs.
So
you
don't
have
to
use
open.
You
know
the
open
mainnet
network
for
that.
C
So
when
it
comes
to
collaboration,
you
know
a
group
of
entities
might
decide
to
have
a
shared
ledger
to
collaborate
and
share
data
in
a
specific
format.
Again
touching
on
traceability
and
security
and
everything,
so
you
have
this
trace
of
everything
that's
happening
and
not
a
single
entity
can
just
go
back
and
erase
everything.
So
I
think
those
things
kind
of
work
together
and
it's
cool,
because
one
of
the
things
I'm
going
to
show
in
the
demo
is
actually
how
you
can
build
a
permission
network
and
send
private
transactions
and
things
between
entities.
D
Yes,
yeah.
I
also-
I
also
like
this
very
much
that
this
is
the
result
that
we've
gotten,
because
on
top
of
cactus,
just
trying
to
help
abstract
away
the
mechanics
of
interacting
with
different
ledgers,
we
also
put
a
big
focus
on
creating
and
managing
consortiums
and
in
a
way
that
is
baked
into
the
plug-in
architecture
that
we
have
itself.
So
there's
a
lot
of
flexibility
in
there
on
how
you
can
or
will
be
able
to
create
and
manage
consortium
depending
on
what
is
the
actual
legal
or
trust
framework
that
you
want
to
apply
there.
B
Yeah-
and
I
will
say
you
know,
what's
really
cool
is
what
lucas
and
peter
are
going
to
show.
You
know
the
technology
works,
but
sometimes
to
create
a
consortium
but
actually
kind
of
sometimes
the
hardest
part.
Is
you
know
the
people
aspect
and
the
getting
all
these
competitors
to
work
together
and
and
it's
actually
not
the
technology,
that's
the
biggest
blocking
point
so
or
at
least
we're
gonna.
Try
to
show
you
how
it
can
be
easy
mark.
E
You
know
through
apis
and
get
data
from
the
various
different
enterprise
departments
and
stuff.
So
they
could,
you
know,
have
have
it
all
in
one
place,
and
that
was
really
difficult
to
do,
and
you
know
looking
at
blockchain,
I
saw
that
there
was
a
way
that
this
could
actually
be
a
unifying
solution
to
it.
So
that's
really
how
we
got
into
it,
and
you
have
a
lot
of
the
projects
that
I've
been
working
on
are
really
you
know
of
that
flavor.
E
B
Yeah,
no
that's
great
context
and
you're
right
yeah,
no,
all
the
legacy
systems
being
you
know,
weren't
built,
you
know,
thinking
of
how
they
all
work
together.
It
was,
you
know
they
were
built
for
one
specific
need,
and
now
how
are
they
all
going
to
talk
to
each
other
and
what
makes
sense,
and
how
are
we
cross-communicating
that
that
makes
a
lot
of
sense?
No,
that's
great!
You
should
put
that
one
on
the
pole.
E
And
another
headwind
that
I
think
all
of
us
fly
into
and
stuff
is,
you
know,
as
we
get
closer
to
an
actual
implementation,
you
start
to
contemplate.
How
does
the
blockchain
solution
fit
into
the
it
architecture,
because
I
think
by
now
those
of
us
that
have
done
some
laps
around
the
track,
trying
to
create
blockchain
solutions,
as
databases
on
steroids
you
know
is,
is
great
in
theory,
but
in
practice
it's
it's
a
completely
different
animal.
B
For
sure
yeah,
no
and
that's
something
like
the
I
mean
at
least
with
the
baysu
team,
like
we're
all
constantly
thinking
about
deployment.
How
are
we
making
it
easier
to
use?
What
is
you
know,
a
network
administration,
and
not
just
you
know,
you
know,
if
you
don't,
how
do
you
fit
it
with
the
other
enterprise
applications
and
all
that?
So
that's
definitely
constantly
a
discussion
so
that
that
resonates
at
least
with
me.
E
So
yeah
and
so
you're
going
to
have
a
lot
of
people,
a
lot
of
enterprises
that
have
made
significant
investments
in
their
erp
systems
and
they
are
not
going
to
just
rip
and
replace
with
a
blockchain
solution
onto
that.
So
you
know
we
start
looking
at
more
creativity
as
far
as
how
it
actually
you
know,
fits
when
whether
it's
going
to
be
an
event,
bus
or
you
know
a
proof
of
consistency
between
state
machines.
B
C
And
I
think
that's
an
interesting,
an
interesting
scenario
that
we
see
with
some
some.
You
know
some
companies
is
that
it's
almost
like
there's
a
journey
between
understanding.
You
know
what
you
could
use
blockchain
for
and
actually
you
know
when
you
start
using
it,
and
then
you
find
that
it
fit
for
specific
purposes
and
some
other
purposes
not
directly
one-to-one
mapping.
So
you
know
the
thing
that
mark
was
talking
about
where
oh
yeah,
they
have
like
a
regular
relational
database
or
something
and
suddenly
oh
yeah.
C
We
can
move
everything
to
smart
contracts
and
putting
and
put
all
this
data
in
the
on
the
chain
and
everything
without
realizing
that
that's
not
necessarily
the
best
use
of
the
two.
So
I
think
this
is
part
of
the
journey
and
part
of
the
learning
is
actually
also
understanding
where
the
blockchain
would
fit
and
solve
problems
and
not
just
create
more
problems
and
the
other
way
around
as
well.
So
I
think
that's
just
an
interesting
thing
to,
and
I
think
it
just
takes
like.
C
Maybe
time
or
just
you
know
more
research
for
whoever
wants
to
use
the
technology
understand
and
make
sure
that
it's
not
just
don't
look
at
it
just
as
a
another
database,
it's
more
than
a
database.
You
know
you
can
do
so
many
more
things
but
yeah
it's.
I
just
thought
it
was
something
interesting
to
highlight
that
this
journey
that
we
see
companies
going
through
not
just
I
mean
the
technology
is
new,
so
I
think
everyone's
evolving
and
learning
together,
but
yeah.
That's
interesting.
E
B
Oh
yeah,
for
sure
I
know
that's
interesting,
but
yeah.
It's
interesting,
though
in
the
poll
nobody
said
what
problems
are
you
trying
to
solve?
Lower
costs
and
particular
productivity
increase,
no
one's
kind
of
in
but
you're
right
or
it
kind
of
goes
hand
in
hand,
at
least
when
you're
building
the
business
case.
I
will
keep
going
so
I
think
we
kind
of
already
covered
at
least
the
intro
section
to
these,
so
I'm
actually
going
to
jump
ahead
to
our
next
poll.
If
that's
all
right.
B
D
B
I
know
so
the
good
news
is:
is
that
we're
showing
all
of
these
things
mark
we're,
probably
not
going
to
show
a
private
transaction
in
a
public
network?
But
lucas
can
probably
talk
about
how
basu
does
solve
for
that,
but
so
the
first
two
will
be
solved
and
demoed
by
lucas,
which
is
how
to
connect
maine
ethereum
and
how
to
send
private
transaction
in
a
permission.
B
Network
he'll
talk
to
the
private
transaction
public
network
and
then
peter
is
going
to
be
doing
happy,
create
a
web
application
to
interact
with
multiple
ledgers
with
with
cactus.
So,
yes,
we
did
kind
of
to
you
up
for
that.
I
apologize,
but
with
that
peter
I'll,
let
you
go
ahead
and
kick
off
the
demos
and
for
anyone
who
wants
to
follow
along.
We
have
the
links
here,
but
I'll
leave
before
you.
D
D
Here's
the
eternal
command
that
I
will
show,
and
this
runs
on
any
computer
with
docker.
That
does
not
have
an
arms
to
you
in
it,
which
now
nowadays
you
actually
have
to
say
that,
because
they
started
rolling
out
these
laptops
with
that
fruit
logo
that
have
arm
chips
in
them.
So
but
anyway,
I'll
run.
This
command
yep
face
anyway
living
on
the
edge.
D
A
A
D
D
Then
I
do
docker
ps,
then
there
there's
no
containers
running
inside
that
container,
so
this
is
truly
an
to
an
example
that
simulates
the
lectures
themselves
as
well,
and
I
think
by
now
it
probably
booted
up.
So
I
will
get
over
to
this,
which
is
the
local
host
that
you
can
also
use
if
you
are
trying
this
at
home,
but
you
should.
D
D
This
is
a
run-of-the-mill
web
application
that
manages
data,
so
it's
very
boring
and
that's
by
design,
and
you
can
book
bamboo
harvests
and
bookshelves
in
it.
Bookshelves
are
made
of
out
of
bamboo
in
this
case,
and
the
data
for
bambi
harvest
is
stored
on
the
quorum
ledger.
That's
running
inside
that
container
right
now
and
the
bookshelves
are
stored
on
a
basil
letter
and
the
bottom
line
is
oops.
Sorry,
not
this
one,
the
other
one.
So
first
you
have
to
create
a
bamboo
harvest
list
or
a
bamboo
harvest
record.
D
And
then,
if
you
hit
this,
then
it
gets
saved.
Then
you
have
this
record.
So
now
you
have
these
records
one
reference
in
the
other
and
they
are
in
different
ledgers.
But
the
point
here
is
that
the
map
application
does
not
really
make
a
big
deal
out
of
this,
and
all
you
have
to
do
apart
from
some
extra
boilerplate
code.
D
Well
I
could
do
this
in
10
lines
of
code
with
truffle
and
vap3
as
well,
but
into
that
I
will
say
that
in
the
coming
weeks
we
are
also
adding
into
this
example
fabric
and
quarter,
which
are
also
lectures
that
we
are
supporting
now
and
then
suddenly.
That
equation
looks
much
much
different,
because
you
can
really
start
to
see
there
the
value
of
having
a
framework
where
an
api
call
to
you
to
a
transaction
on.
D
Just
the
last
thing
I
wanted
to
show
is
the
insert
bamboo
harvest
endpoint.
So
if
you
compare
this
to
the
other
one,
they
are
pretty
much
the
same
thing,
just
calling
a
different
contract
with
a
different
abi
on
a
different
ledger,
but
this
is
about
as
different
as
it
gets,
and
it
will
look
almost
exactly
the
same
for
the
other
lectures
as
well.
So
the
idea
is
that
this
should
allow
people
to
be
more
productive
and
that's
all
I
have
it's
a
very
quick
demo.
B
B
B
C
C
I
also
wanna
show
everyone
how
you
can
start
your
own
private
network,
so
I'm
the
same
private
network,
but
you
can
think
about
it
as
a
consortium
network.
It's
up
to
you
who
you
want
to
connect
to
your
network.
It
only
depends
on
your
rules
for
the
network,
and
things
like
that,
and
the
other
thing
that
I
want
to
demonstrate
is
how
you
can
use
some
of
the
in
enterprise
features:
investor
like
permissioning
and
private
transactions,
so
we're
gonna
go
through
it
a
little
bit
as
well.
C
So
that's
a
really
interesting
question
because
we
do
have
so
the
way
that
the
the
privacy
model
that
we
implemented
in
basu
supports
a
public
network,
because
I
I'll
try
to
explain
it
without
getting
too
much
into
the
internals
of
how
private
transactions
work,
but
basically
every
time
that
two.
You
know
two
participants.
Let's
say
that
they're
sending
a
private
transaction
between
them
themselves
or
two
nodes
in
the
network.
C
We
have
a
secondary
network
layer
with
orion,
which
is
like
a
we
call,
the
private
transaction
manager,
which
is
going
to
be
responsible
for
transmitting
the
actual
transaction
payload
between
only
the
participants
and
on
the
public
side
of
the
network.
We
create
what
we
call
a
private
transaction
marker,
which
is
a
public
transaction
that
contains
a
hash
that
can
be
used
to
retrieve
the
private
payload
from
orion
so
and
for
every
node
when
you,
when
they
see
the
public
transaction,
and
then
they
see
that
hash.
C
That
hash
doesn't
really
mean
anything
so
all
nodes
that
are
not
participants
in
the
network.
They
will
just
skip
that
transaction.
It's
just
they're
going
to
treat
it
as
a
transaction
that
is
storing
some
data
in
the
chain
or
something
like
that,
but
for
all
no
better
nodes
that
are
a
participant
on
that
network.
They
will
understand
that
that
transaction
is
something
else
and
then
they're
going
to
use
that
key
to
retrieve
the
payload
from
orion
and
execute
that
private
transaction
on
their
private
state.
C
C
But
you
have
the
option
of
doing
your
private
transactions
affecting
your
private
state
on
the
side
kind
of
thing,
and
another
interesting
concept
is
that
we
allow
you
from
reading
public
data
from
private
transactions,
so
you
can
even
have
a
private
transaction
that
reads
some
data
from
the
public
tank
and
uses
that
for
some
calculation
or
something
of
course,
the
other
way
around
doesn't
work.
You
can't
have
like
a
public
transaction
that
reads
from
private,
because
otherwise
there's
no
point
in
calling
it
private
anymore.
C
So
I
hope
this
just
quickly
demonstrate
how
you
could
use
this
in
a
public
network
environment.
I
think
we
might
have
had
a
webinar
in
the
past
where
we
showed
the
public
transaction
I'll
see
if
I
can
dig
it
and
if
I
find
it
I'll,
send
it
the
link
but
yeah.
If
you
have
any
more
questions
about
this
specific
public
and
private
transactions,
you
can
find
us
on
rocket
chat,
and
then
we
can
talk
a
bit.
C
You
know
some
of
the
internal
details
about
it,
so
yeah
so
and
just
quickly
talking
about
this
topology
here
we
have
three
basta
notes
running,
so
you
can
see
one
two
and
three
here.
I
know
that
the
logs
are
a
bit
small,
but
probably
doesn't
matter
too
much
at
the
moment
and
on
the
side
here
I
have
three
orion
nodes
running
each
one
connected
to
my
best
to
know
so.
C
Basically,
three
best
nodes
and
three
orion
nodes,
and
I
also
have
one
web
application
running
here,
which
is
the
web
application
that
we
use
to
manage
permissioning
rules
in
basu.
So
that's
kind
of
a
cool
thing.
It
makes
it
really
flashy
for
a
demo,
because
our
permission
rules,
we
have
different
modes,
but
one
of
the
more
robust
modes
is
the
mode
where
all
the
rules
are
saved
in
smart
contracts.
C
And
the
cool
thing
is
that,
because
they
are
stored
in
as
much
contract,
the
management
of
those
rules
are
really
easy
because
everyone
that
joins
the
network
will
synchronize
with
the
chain
and
then
have
the
rules
up
to
date,
so
that
we
have
another
mode
where
you
can
use
like
a
configuration
file
to
specify
things,
but
it
only
works
for
it.
It
works
kind
of
like
a
firewall
or
something
because
the
rules
are
not
really
shared
between
all
the
nodes.
C
So,
of
course,
depending
on
the
use
case,
one
makes
more
sense
over
the
other,
but
for
like
a
social
network,
especially
if
you
have
entities
outside
your
own
organization,
the
on-chain
option
is
probably
a
good
fit
because
everything
is
synchronized
on
the
chain
and
again
I'm.
I
usually
talk
too
fast.
So
if
I'm
going
too
fast
or
if
anyone
has
any
questions,
yeah
just
jump
in
because
I
don't
want
to.
I
want
to
make
sure
that
everyone
understands
what
what's
happening
here.
C
So
three
notes
I'll
start
with
the
permissioning
demo,
so
I'll
bring
up
the
dab
here.
It
looks
kind
of
nice.
Hopefully,
this
one
is
big
enough
that
anyone
can
see.
So
this
is
a
dab
connected
to
my
node
and
then
it
is
displaying
the
rules
that
we
have,
in
the
permission,
smart
contract,
we're
gonna,
have
all
the
links
for
like
docs
and
how
to
set
up
this
yourself
later
on,
but
yeah.
C
C
It
doesn't
mean
that
the
others
account
won't
be
able
to
send
a
transaction.
They
can
try.
But
then
all
the
nodes
are
going
to
check
the
sender
of
the
transaction
against
the
rules
and
then
they're
going
to
reject
the
transaction,
because
it's
a
invalid
transaction
from
the
permissioning
point
of
view,
the
same
thing
for
the
nodes.
C
Unfortunately,
all
my
nodes
are
gonna
be
mean
to
her
and
say
no
you're
not
going
to
connect
and
they're
just
going
to
reject
her
incoming
requests
and
the
admins
is
a
concept
where
you
can
have
special
accounts
that
you
promote
to
admins
and
those
accounts
are
the
accounts
that
are
able
to
change
the
rules
pretty
much
so
I
can,
you
know,
delete
rules
and
create
rules
here
you
can
see
through
this
step
and
in
this
case
I
only
have
one
account.
That
is
the
one
that
I'm
connected
at
metamask
at
the
moment.
C
C
So
basically,
each
one
of
these
entries
corresponds
to
one
of
the
nodes
here.
So
what
I'm
gonna
do?
First,
I'm
gonna
delete
one
of
the
nodes
from
this
list,
basically
saying
that
this
node
is
not
allowed
to
transaction
the
network,
it's
unable
to
be
removed.
So
let
me
refresh
the
page
because
it's
been
running
for
a
while
here
and
let
me
make
sure
that
I
don't
have
anything
from
my
previous
run
to
make
sure
that
everything
was
working
before
and
I'll.
Try
again,
okay
cool!
C
It's
only
permissioning
in
a
public
networks.
It's
interesting
because
you
you,
you
can't
really
enforce
it.
Every
other
node
will
be
running
bazoo
with
permissioning
enabled.
So
it
is.
I
don't
want
to
use
the
word
complicated,
but
it's
an
interesting
use
case.
If
you're
trying
to
use
permission
in
a
public
network
in
a
private.
B
B
No,
and
just
so
one
thing,
I
think
that
you
said
was
really
intere
or
like
worth
saying
again.
Is
you
know
it's
pretty.
You
know
just
with
a
quick
button
you
can
remove.
You
know
a
node,
it's
that
simple
and
it's
and
there's
no
gas.
So
permission
networks
you
can
decide
if
you
want
to
have
gas
within
a
permission
network,
sometimes
consortiums
think
it's
valuable.
Sometimes
they
don't,
but
within
a
permission
network
you
can
choose
within
public
ethereum
you
you
don't
get
to
decide.
You
know,
that's
that
correct.
So.
C
Okay,
so
what
happened
here
is
that
I
removed
that
rule
and
then
using
metamask
I've
created
a
transaction
to
that
contract,
and
you
can
see
here
from
the
logs
that
the
third
node
here
was
the
one
that
ended
up
being
kicked
out
of
the
network.
So
you
can
see
that
it
is
giving
this
message
where
it's
saying
that
it's
waiting
for
peers
and
it
doesn't
have
a
connection
and
the
other
two
nodes
they
are
still
talking
to
each
other.
So
this
one
is
producing
blocks.
This
one
is
importing
blocks
and
we
we.
C
Basically
we
kicked
someone
off
the
network
using
the
rules
and
again
this
is
like
a
three
node
network,
so
it
wouldn't
be
that
hard
to
just
go.
You
know
into
two
configuration
files
and
updating
some
kind
of
rule,
or
maybe
going
you
know
into
two
firewalls
and
removing
those
rules
and
creating
those
rules,
but
imagine
that
you
had
like
200
500,
a
thousand
notes.
So
you
know
keeping
everything
in
sync
and
on
you
know
all
the
rules
the
same
without
a
ledger
taking
care
of
it.
It
can
be.
C
C
One
use
case
that
I've
seen
that
was
really
good
is
that
you
could
have
some
kind
of
oracle
application
querying
the
rules,
the
contract
rules
and
updating,
for
example,
your
aws
firewall
rules
based
on
the
state
of
this
contract.
So
I've
seen
this
kind
of
interesting
enterprise
application
where
you
have
the
contract,
but
you
also
want
to
have
some
kind
of
network
layer
security,
so
you
can
have
some
kind
of
you
know
application!
C
That's
going
to
be
querying
this
smart
contract
for
the
for
the
up-to-date
rules
and
make
sure
that
your
firewall
rules
are
going
to
reflect
the
contact
rule.
So
that's
kind
of
an
interesting
use
case
and
again
after
a
while,
the
all
the
nodes
picked
up
the
rules,
so
node
three
was
trying
to
talk
to
node
one
and
two,
but
they
were
just
rejecting
it
at
the
moment
that
we
updated
the
rules
node
one
and
two
pretty
much
opened
the
gate
and
said
yep.
C
C
Okay,
let
me
move
now
to
I
think
I'll
go
to
the
private
transaction
one
just
because
it's
where
is
it?
They
go.
I'm
sorry,
I'm
jumping
between
screens
yeah,
so
proper
transactions.
I
just
want
to
show
you
how
we
could
again
in
a
setup
with
three
nodes,
send
prior
transactions
between
them.
This
is
really
a
really
really
simple
example:
we
have
the
storage
contract
and
I
don't
know
if
everyone's
familiar
with
solidity,
but
this
is
a
smart
contract
in
which
we
can
store
a
number
and
then
we
have
a
function.
C
So
you
store
the
number
and
a
function
to
re.
You
know
retrieve
the
number
of
course:
that's
probably
not
a
super
enterprise
use
case,
but
it's
going
to
be
good
enough
to
show
us
what
we
will
be
doing
here
and
then
in
my
examples,
I'll
show
you
how
we
can
so
I'm
not
sure
again
if
this
is
too
deep
into
the
code,
but
hopefully
everyone
will
be
able
to
follow
up.
C
What
this
is
saying
is
that
I
want
to
send
this
transaction
from
from
participant
one
to
participant
one
and
two,
so
I'm
saying
that
this
transaction
should
be
visible
or
available
for
these
two
participants
right
so
node,
one
and
two
are
gonna:
be
able
to
see
that
transaction
and
down
down
the
track
here,
I'm
creating
another
transaction
where
node,
two
so
private
from
participant
two
is
gonna,
be
updating
the
contract
with
some
some
value.
I
think
it's
five.
C
I
think
it's
hardcoded
to
five
at
the
moment,
so
just
demonstrating
that
it's
like
it
goes
both
ways,
so
I
can
create
a
you
know,
deploy
a
contract
that
is
private
between
two
parties
or
even
more
parties,
and
only
the
members
of
that
party
will
be
able
to
not
only
see
the
contract
but
interact
with
the
contract.
That's
what
I'm
trying
to
demonstrate
here
and
hopefully,
if
the
code
wasn't
clear,
but
if
the,
if
the
code
wasn't
clear,
my
nice
logs
will
be
clear.
C
C
C
The
reason
is,
it
doesn't
know
about
that
transaction
right.
No
3
was
never
a
member
of
that
transaction,
so
it
doesn't
know
about
it.
So
you
know,
even
if
someone
sends
this
hash
to
note
3
or
something
you
know,
it
won't
have
access
to
it.
So
it
doesn't
know
that
there's
something
there
and
we
can
see
here
that
the
second
node
that's
the
receipt
for
the
transaction
that
updated
the
value-
and
this
is
the
address
of
the
private
contract
that
we've
deployed
again.
C
It
lives
on
the
private
state
I'll
copy
this
address,
because
what
I
want
to
show
you
now
is
that
we
can
read
that
value
and
hopefully
I've
typed
this
right.
So
I'm
calling
another
script
that
is
going
to
call
the
contract
on
that
address
and
see
what
value
is
safe
there,
okay,
cool
again
best
one,
that's
the
contract
address
and
the
value
that
it's
retrieving
from
the
address
and
the
form
is
a
bit
weird,
because
that's
like
the
the
way
that
we
are
decoding
things.
C
I
didn't
do
like
a
nice
string,
but
you
can
see
that
it's
seeing
the
value
5
here
and
hopefully
you
can
see
that
that's
a
2
is
also
getting
the
value
5.
and
note
3,
even
though,
even
though
note
3
knew
about
this
address
somehow
so
somehow
it
found
out
that
there
was
an
address
on
that
sorry,
there
was
a
contract
on
that
address.
It
doesn't
have
access
to
it
because
it
doesn't
exist
on
its
private
state.
So
it's
retrieving
an
empty
value
here.
That's
the
way
that
the
theorem
deals
with.
C
If
you
try
to
call
something
that
doesn't
exist.
Basically,
so
even
if
note
3
tries
to
go
through
every
possible,
you
know
contract
address
and
tries
to
find
data.
It's
never
going
to
find
it
because
the
data
doesn't
exist
on
the
node
3
node
on
the
node
3
database.
It
doesn't
exist
so,
and
I
could
I
could
try
going
through
the
logs
here
to
show
how
this
is
happening,
but
I
think
it's
going
to
be
probably
not
that
interesting,
but
you
can
see
on
the
orion
logs,
which
is
that
intermediate
that
that
auxiliary,
oh
gosh.
C
I
can
say
that
word
that
that
underlying
network
that
makes
sure
of
transmitting
the
encrypted
data,
you
can
see
that
we're
going
to
have
a
few
methods
like
push
where
it's
sending
the
data
to
the
participants
encrypted
and
you're
gonna
see
this
one
calling
a
receive.
So
that's
when
the
node
is
processing
private
transactions,
it's
trying
to
retrieve
that
private
transaction,
and
you
can
see
that
node
three.
Pretty
much
only
has
this
party
info,
which
is
almost
like
they
keep
alive
in
the
network.
C
They
keep
talking
to
each
other
to
make
sure
that
they're
all
online.
But
nothing
happened
on
the
orion
side
here
and
I
think,
that's
kind
of
what
they
have
for
a
demo
here,
I'll
stop
sharing.
But
if
anyone
wants
me
to
go
back
and
show
something,
I
can
probably
go
back
and
talk
a
bit
more.
Oh,
I
forgot
about
showing
sorry
public
ethereum.
B
C
Demos
and
I
keep
promising
that
I'm
gonna
try
to
implement
like
a
proper
depth
that
uses
privacy
for
something
interesting,
but
I
keep
postponing
it
so
hopefully
seeing
the
logs
and
the
requests
is
not
too
boring
for
everyone
else.
You
know
for
permission.
We
have
the
dab
and
it's
kind
of
cool,
so
I
I
think
I
need
ideas
for
building
like
a
proper
private
one
that
it
makes
it
more
interesting.
So
if
anyone
has
an
idea,
please
send
it
in
the
chat
and
maybe
next
time
I
can.
I
can
implement
it.
C
B
C
C
C
Main
or
maybe
just
best,
I
don't
know,
and
the
other
one
is
that
you
need
is
this
net
method
and
this
one
it's
only
needed
because
I'm
running
it
on
my
local
computer
inside
my
private
network
right,
I'm
I'm
I'm
on
my
wi-fi.
So
this
is
something
that
we
added
investor
recently
that
allows
you
to.
You
know
automatically
use
upnp
to
open
the
rules
and
the
ports
and
everything
that
you
need.
C
Of
course,
if
you're
running
this
on
aws
or
some
kind
of
like
you
know
server
that
is
exposed
to
the
world,
you
don't
need
to
use
your
pnp,
that's
just
because
I'm
running
on
my
local
network,
but
that
makes
it
really
easy
for
people
that
just
want
to
get
like
a
feeling
of
running
a
mainnet
node
locally.
You
know
you
can
use
this,
so
you
don't
have
to
worry
about
messing
with
your
router
and
you're,
creating
rules
or
you
know,
static,
ips
or
whatever
you
you
don't
have
to
worry
about
it.
C
C
It's
just
because
by
default,
basso
uses
ford
30303
for
all
the
p2p
connections
and
then
just
taking
a
while
to
shut
down
everything,
and
then
because
I
was
running
the
other
nodes,
I
was
running
one
on
the
on
port
30303,
the
other
one
port
404
another
one,
five
or
five
or
five.
So
it's
just
complaining
that
it
can't
use
the
same
port.
B
C
C
C
C
So
yeah,
so
you
you
totally,
can
so
you
can
use
so
one
of
the
things
that
you,
it's
probably
gonna,
make
your
life
easier.
It's
using
a
wallet
application
to
keep
track
of
your
account
and
your
keys,
and
things
like
that.
So
you
probably
saw
that
I
was
using
a
meta
mask
here
so
metamask
I
I'm
not
sharing
my
screen
anymore.
Am
I
sorry?
Let
me
share
the
whole
screen
again.
So,
for
example,
here
I'm
using
metamask
with
some
accounts
right
and
you
can
see
that
they've
got
like
some
fake
ether.
C
C
The
node
is
what
it's
almost
like
the
plugin,
so
you
can
connect
to
the
network
if
you
want
to
transfer,
if
you
want
to
transfer
ether
or
if
you
want
to
deploy
a
contract
or
anything
that's
going
to
create
a
transaction
to
interact
with
the
network,
you
probably
need
a
application,
that's
going
to
deploy
the
the
contract
or
some
kind
of
wallet
to
to
make
it
easier.
So,
for
example,
here,
if
I
connect
to
mainnet,
you
see
that
all
my
accounts
now
have
zero
ether.
Unfortunately,
but
you
could
you
can
use
it.
C
C
I
hope
that
answer
your
question
and
why
I'll
just
run
the
the
demo
here
about
the
feel
free
to
follow
up.
If
you
have
any
any
more
questions,
I'm
good!
Thank
you
cool,
so
we
can
see
here
again
setting
up
the
data
path,
just
because
I
want
a
specific
folder
to
save
this
data
and
the
upnp,
because
I'm
behind
my
router
but
instantly
a
lot
of
things
coming
up
on
screen.
But
we
are
already
trying
to
talk
to
four
ps
here,
so
they
are
all
peers
from
mainnet
we're
going
to
keep
talking
to
them.
C
But
that's
why
I
said
it
was
a
five
second
demo.
I
just
wanted
to
show
you
guys
that
by
default,
pesu
is
a
mainnet
client.
So
all
the
permissioning
and
privacy
options
that
I
was
showing
everyone
was,
they
are
all
optional.
You
don't
have
to
use
them.
You
can
just
join
mainnet
join.
You
know
some
of
the
public
test
networks
to
get
you
started
with
this
year
and
get
your
hands
get
your
hands
dirty.
B
Well,
that's
a
good,
I
think
way
to
wrap
up.
I
know
we
have
two
minutes
we'll
stay
on
an
extra
couple
minutes.
If
there
are
any
other
questions,
we
hope
you
really
enjoyed
this.
We
would
love
you
to
check
out
the
each
of
the
projects
that
we
shared
cactus
and
baysu
I'll
drop
a
couple
links
in
the
chat.
We
have
one
final
poll,
so
if
you
thought
this
was
interesting,
we
want
that
feedback.
We
want
to
know
what
your
interested
in
learning
about.
C
B
No,
it's
so
cool
and
I
think
yeah
we
want.
You
know
the
high
quality
community
to
be
more
familiar
with
ethereum
and
comfortable
with
it
and
understand
how
it
fits
into
the
hyperledger
and
enterprise
blockchain
ecosystem.
So
you
know
always
just
looking
for
you
know
any
feedback.
You'll
have
you
know
we're
all
on
rocket
chat,
so
so
feel
free
to
message
us
on
rocketchat
and
go
from
there
and
looking
at
this
last,
it
looks
like
use.
B
Yeah,
no,
no
worries
yeah,
no,
so
we'll,
probably
the
next
session
we'll
talk
about
baisu
and
cactus
use
cases
and
different
networks
that
are
running
both
of
them.
But
consensus
does
have.
We
have
our
own
kind
of
webinar
series
that
talks
about
all
of
our
different
products
and
offerings
and
all
that,
but
this
audience
will
definitely
be
hyperledger
focused
but
highly
encourage.
You
know:
there's
tons
of
great
resources
through
consensus
as
well
as
hyperledger.
So
if
you're
looking
to
learn
more,
you
know
you're,
definitely
in
the
right
place.