►
Description
Because it is All About Collaboration, Security and Removing Friction - Jonathan Levi, HACERA
----
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 #HyperledgerGlobalForum2018 #Blockchain
A
Okay,
so
head
over
everybody,
my
name
is
jonathan
levine.
Some
of
you
know
me
from
probably
hyper
lady
fabric.
We
do
a
lot
of
Sabathia
theorem
and
we
play
with
a
lot
of
chains.
I
was
on
at
ESC
for
a
year
last
year
and
were
very
active
as
a
company
in
open
source
rocks
and
technology
security,
digital
identity
and
a
focus
this
year,
and
probably
next
is
gonna,
be
even
more
so
is
interoperability
and
collaboration.
So
I'm
gonna
talk
about
the
unbounded
network,
which
is
a
network
that
we
created.
A
Brian
introduces
comes
for
the
beginning
as
one
of
the
examples
of
a
coin
market
cap
for
the
enterprise
block
chains.
We
wanted
to
find
a
way
to
bridge
between
permission
chains
and
public
chains,
all
right
so
when
I
started
working
on
blockchain
I
actually
started
on
Bitcoin
lighting
network
and
then
moved
on
to
etherium
in
when
it
was
out.
Frontier
like
that
was
2015,
and
the
main
problem
that
we
had
back
then
was
regulation
right,
I
came
in
as
a
banker.
A
My
background
I've
been
through
a
lot
fortunately,
and
unfortunately
so
spend
a
lot
of
time
in
banking.
I
spend
a
lot
of
time
in
kind
of
highly
regulated
environments
where
you
really
care
about.
Who
is
your
customer
where
the
money
is
coming
from
reporting
auditing,
and
my
mindset
didn't
change
right
when
I
moved
to
blockchain
is
and
I
was
looking
at
a
global
payment
system
where
you
have
relatively
quick
finality,
it's
very
difficult
to
move
stuff
in
regulated
environments,
especially
when
you
do
any
cross-border
payments
or
asset
transfer.
A
So
I
came
to
the
blockchain
with
that
mindset
on,
and
the
first
thing
I
wanted
is
to
meet
kyc
requirements
and
AML
and
how
to
kind
of
allow
participants
to
join
a
network
but
in
an
open
way,
while
still
meeting
the
regulations,
all
right
so
hyper
ledger
just
started
and
I
jumped
on
that
when
I
first
saw
it,
because
it
was
my
hope
to
get
more
enterprises
and
bankers
kind
of
into
that
space
like
financial
institutions
that
need
kyc
so
took
more,
they
started
in
banking.
I
did
all
stuffy
networking.
A
No,
it
was
kind
of
I'm
a
mathematician
and
a
cryptographer
by
training,
but
over
the
years
I
started
doing
more
and
more
systems
and
working
with
more
kind
of
critical
systems.
Where
things
cannot
fail,
you
have
to
be
able
to
work
with
those
numbers
and
build
stuff
in
a
much
more
kind
of
auditable
way
which
tied
in
very
well
into
the
blocks
in
space.
So
let's
look
at
the
background.
A
If
I
take
a
step
back,
like
people
have
different
opinions
about
what's
blockchain
the
philosophy
of
etc,
but
my
kind
of
the
way
I
look
at
permission
chains
is
a
permission
chain
is
it
is
a
blockchain
where
or
even
a
DLT,
where
you
actually
know
the
validators,
so
I
don't
know.
A
year
ago,
people
looked
at
permission,
changes
like
private
chains
protected
chains.
A
A
If
you
look
at
what
you
can
do
with
the
ID
and
in
D,
you
can
always
take
an
identity
or
an
identifier
and
allow
somebody
grant
them
the
access
to
a
network
I'm
just
under
conditions
right,
you
want
to
have
I,
don't
know
you
want
to
do
a
token.
I,
don't
know
a
token
race
where
you
want
to
allow
only
accredited
investors
in
right,
otherwise,
security
tokens.
You
want
to
allow
a
collaboration
between
financial
institutions
that
have
to
meet
a
certain
criteria.
A
So
that's
where
you
really
need
in
Chains
that
kind
of
happy
legends
kind
of
mostly
around
and
I
still
argue
that
you
see
need
to
connect
to
a
pocket
chain.
So
it's
very
difficult
to
work
with
kind
of
only
permission,
gesture
that
is
connected
and
in
a
way
at
the
beginning,
we
and
I
was
kind
of
guilty
as
well.
When
we
started
doing
a
lot
of
PLC's,
we
created
a
few
silos
because
we
had
like
a
few
people,
organizations
that
were
happy
with
a
small
set
of
a
chain
that
actually
had
high
value
in.
A
It
was
very
critical,
but
we
still
couldn't
connect
them
all
right.
So
back
in
the
day,
we
kind
of
started
looking
at
it
and
I
always
believe
that
there
will
be
more
than
one
chain,
and
now
we
see
it
yeah.
Two
years
later,
we
were
right,
but
the
problem
that
we
saw
is
that
many
people
kind
of
getting
into
the
space
and
by
the
way,
please
ignore
token
prices,
because
that's
like
yeah
I
know
it's
in
a
bit
of
a
volatile
market
yeah,
but
we
started
looking
at.
This
is
just
an
example.
A
There
are
many
more
players,
as
you
know
how
many
members
you
have
in
a
villager
is
their
own
inter
personalized,
and
there
are
other
people
that
are
just
trying
to
look
into
blockchain,
but
the
beacon
of
players
started
talking
about.
Okay,
let's
have
a
deal
T
or
a
blockchain
or
a
framework
that
everybody
can
use.
Yes,
stuff
was
open-source,
but
making
the
day
I'm
sorry
to
say
that
they
didn't
talk
to
each
other.
That
well
right.
Ibm
was
running
into
kind
of
you
know,
fabric
and
the
ferry
system
actually
grew
from
equals.
A
Zero
we
had
27
or
28
organizations
into
was
pushing
sawtooth
because
they
were
trying
to
do
a
lot
of
stuff
with
SG.
Xr3
was
kind
of
basically
built
and
kind
of
got
all
the
banks
around
a
consortium.
So
we
saw
like
different
consortiums
adhesive
frameworks
and
my
concern
was
okay.
We
need
to
collaborate
right.
How
are
we
going
to
do
it
right
so
and
we
participated
right?
We
welcome.
A
It
was
a
big
conquer
guys
I
contribute
to
if
you
spend
a
lot
of
time
with
IBM
fabric
and
not
just
an
idea
in
for
me,
but
anyone
in
the
fabric
ecosystem
that
you
can
mean
I
was
a
maintainer
right.
There
was
an
element:
Ernie
was
a
release.
Manager
f10
still
active
on
1.3
1.4,
helping
with
that
energy
mixer
kind
of
component,
so
we're
still
involved
with
all
of
them,
but
we
felt
that
there
was
kind
of
you
know
what
do
together
right.
A
Another
step
back
a
syrup
basically
created
kind
of
a
way
to
look
at
permissioning
in
a
much
more
granular
way,
and
it
was
our
vision-
was
to
be
a
little
bit
blocked
and
agnostic.
It's
difficult,
because
these
frameworks
were
moving
a
lot,
but
you
are
trying
to
think
about.
Okay.
If
I
want
to
do
more
than
just
kyc,
we
were
looking
at
permissioning
in
who
can
see
what
who
can
do
what
who
can
write,
how
I
can
access
the
network
and
I
wanted
to
also
revoke
rights
of
participants
that
don't
misbehave
right.
A
So
why
did
he
want
to
do
visioning?
And
you
know
all
the
guys
here
that
are
in
franchise
editions
or
are
sitting
in
any
kind
of
healthcare,
highly
regulated
space,
for
whatever
reason
you
have
so
many
kind
of
restrictions
and
risk
in
having
a
super
open
chain,
but
you
also
have
other
issues
when
it's
too
closed
right,
like
if
you,
you
can't
run
a
POC
with
only
four
people
in
somebody's
lab
right.
So
this
is
why
we
were
thinking.
A
Let's
have
this
permission
in
in
a
much
more
kind
of
flexible
way
that
is
kind
of
if
I
look
at
the
spectrum
of
okay,
everything
is
public,
like
a
Twitter
kind
of
you
know,
because
everything
is
like
shared
with
everybody
or
the
other
ways
like.
We
are
really
closely
guarding
everything
to
a
point
where
my
blockchain
technology
or
my
whole
kind
of
POC
is
running
in
somebody's
lab.
A
We
need
to
find
somewhere
kind
of
some
middle
ground
right,
so
our
approaches
you
realize
we
are
not
as
big
as
the
big
players
that
are
coming
into
the
space
right
so
very
early
on.
We
decided
not
to
have
our
own
blockchain
and
not
to
come
to
any
of
the
partners,
customers
and
friends.
Organizations
that
we
work
with
our
attitude
was,
we
are
not
here
to
displace
your
protein,
like
we
didn't
want
to
come
in.
A
Fabric
is
better
than
this
code
is
that
we
were
saying
okay,
you
probably
did
you
do
diligence
and
you
tried
enough,
and
you
know
what
you're
doing.
Let
me
see
how
I
can
help
you
meet
regulations
and
actually
connect
different
block
chains
or
just
have
different
set
that
interact.
Okay.
This
is
how
we
started
kind
of,
and
this
is
why
we
walked
along
with
fabric.
We
played
a
lot
with
sawdust
and
we're
trying
to
sit
on
top
actually,
while
still
contributing
back
to
the
framework.
A
A
We
have
some
other
values,
but
I'm
not
gonna.
Talk
too
much
water,
Sarah
I
want
over
unbounded
right.
So
this
is
us
back
in
the
day
we
had
a
lot
of
partnerships
and
then
we
kind
of
started
to
kind
of
think
about
how
we
can
have
like
the
public
main
net
of
hybrids
of
fabric,
so
tools
and
all
these
permission
chains
right.
This
is
that
that
was
kind
of
the
division
back
in
the
day,
and
we
already
had
a
lot
of
partnerships
in
place.
We
already
work
with
a
few
cloud
providers.
A
We
just
wanted
to
be
able
to
allow
somebody
to
run
fabric
on
different
clouds
to
run
anything
that
he
wants
to
look
up
with
Stella,
but
not
to
really
work
all
the
way
to
create
your
own
folk
of
something
when
things
are
available
online.
Okay,
so
I
wanted
to
talk
a
little
bit
about
some,
so
that
many
use
cases
that
many
sectors
right,
but
in
the
end,
but
I
can
talk
about
it.
But
I
don't
talk
about
too
much.
A
We
look
at
the
different
cryptocurrencies
and
all
these
tables
and
what
people
need
to
do
and,
like
all
these
tokens-
and
we
still
sorted
these-
are
very
similar
problems
right
some
of
them.
You
really
need
the
permission
chains,
but
all
the
times
you
want
to
share
data.
Okay,
that's
an
example
that
is
not
really
relevant,
but
here's
an
interesting
kind
of
concept
that
we've
all
talked
about
for
a
long
time
like
many
financial
institutions,
we're
talking
about.
A
When
you
have
a
sector
based
solution,
your
participants
are
actually
competitors
right,
so
it
doesn't
matter
if
you
have
hospitals
trying
to
share
trial
data
or
if
you
have
banks
trying
to
save
the
KYC.
That
is
pretty
expensive
and
time-consuming,
and
actually
it's
not
a
nice
accessibility
right
for
me
to
move
from
one
bank
to
another,
but
the
problem
was
that,
even
if
you
have
this
kyc
and
a
portal,
I
still
have
a
lot
of
issues
right
with
privacy.
A
What
I
can
share,
with
whom,
let
alone
the
fact
that
not
everybody
still
built
into
this
kind
of
notion
of
changing
the
business
model
to
work
with
rocky
right.
So
these
are
all
very
good
ideas
that
we
saw
in
practice.
We
needed
to
have
this
kind
of
permissions
to
public
kind
of
connectivity,
let
alone
that
just
permission
did
enough
just
to
be
able
to
list
stuff
and
to
find
and
discover
what's
outer,
but
not
was
not
an
existence
right.
So
we
started
working
with.
A
A
So
we
connected
kind
of
the
etherium
blockchain
go
through
the
Indian
sovereign
kind
of
network
to
get
an
identifier,
then
you
go
and
play
chess
actually
on
sawtooth
and
once
you
get
the
result,
you
go
and
you
get
your
reward
in
Heath
and
it
was
kind
of
a
nice
kind
of
composition.
We
it's
the
first
time,
I,
think
I,
think
which
you
dislike
the
concept
of
multi
chain
atomic
swap
that
is
more
between
more
than
two
parties.
A
We
didn't
patent,
anything
that
copy
didn't
result
of
money
and
now
that
they'll
pay
lawyers
a
lot
of
money
for
it.
But
the
idea
was
okay,
I
can't
walk
always
in
silos,
but
I
still
need
to
be
able
to
have
a
token.
Even
though
in
fabric,
for
example,
we
didn't
want
to
have
a
talking
backed
into
the
system
at
at
a
time
we
didn't
want
to
have
like
a
currency,
but
still
if
you
have
a
way
to
all
the
transactions
and
to
look
at
everything,
it's
a
waste.
A
It's
a
waste
not
to
use
the
connectivity
to
the
maintenance.
Okay,
so
we've
done
a
lot
of
debt
later
on
and
then
we
actually
made
a
product
and
a
platform
out
of
it.
But
the
idea
is
to
be
able
to
tell,
for
example,
stella
payment,
ethion
payment
have
a
sovereign
identity
with
a
sovereign
identifier
and
then
connect
to
different
hyper
ledger
technologies.
If
you
want
to
work
with
permission
chains,
so
kind
of
division,
I,
don't
know,
I,
think
2019,
you'll
see
more
of
that.
A
This
is
a
site
that
actually
was
created
by
to
be
honest,
IBM
and
the
idea
was
to
have
the
unbothered
connecting
these
different
chains
and
we
wanted
to
be
able
to
move
data
around
and
currency
route.
But
I'll
be
honest
with
you.
We
wanted
to
run
a
platform.
We
didn't
want
to
become
an
exchange.
We
didn't
want
to
pump
token.
A
We
didn't
want
to
do
care
I
see,
so
we
wanted
to
provide
the
framework
for
all
this
to
integrate
the
chains,
so
I'll
show
in
a
second
like
how
it
looks
like,
but
actually
that's
a
bit
technical.
So
if
you
guys
wanna
talk
about
that,
we
can
so
let's
talk
about
that
bounded
right
by
the
way.
Any
questions
stop
me
at
any
time.
Yes,
please.
B
B
B
A
B
B
B
A
I
didn't
prepare
this
question
yesterday.
Thank
you
so
much
for
asking
right.
So
yeah,
that's
a
very
good
question
right.
So
first
question
is
like
this:
is
the
network
of
networks
right
so
I
using
a
blockchain
to
connect
different
blockchain?
So
actually
another
question
that
people
usually
ask
is:
why
did
they
need
another
blockchain
I'll
talk
about
in
a
second.
But
the
second
question
is
yeah.
It's
true.
We
don't
have
a
naming
system
today
right
if
I
want
to
move
data
around
from
chain
one
to
chain
B.
A
We
know
that
there
is
a
big
problem.
I
can't
use
IP
addresses
of
a
node
because
it
changes
right.
Oh
it's
behind
some
firewall
and
there
are
some
naming
mechanisms
right.
So
the
there
is
a
project
that
does
naming
on
Bitcoin
E&S
the
theorem
naming
services.
They
have
an
auction
where
you
can
try
to
claim
a
name,
so
all
the
ICS
right
they
have
a
token
and
they
want
it
to
be
unique.
So
you
basically
beat,
and
then
you
wait,
I
don't
know
48
hours
or
72
hours
depends
of
the
protocol.
A
If
there's
no
kind
of
friction
or
any
dispute,
you
will
get
the
name
and
as
long
as
your
money
is
there,
you
keep
it,
but
the
ENS
was
working
only
for
a
theorem
so
that
you're
naming
services
right
and
even
to
go
to
a
theorem
now
and
to
just
to
look
up
names.
You
have
to
run
so.
The
two
options
right,
like
the
correct
way,
is
to
download
all
the
past
transactions.
So
you
have
to
keep
an
idiom
synchronize
nodes.
That's
like
a
Tara
class
of
data.
It
takes
two
weeks
on
an
IBM
mainframe
right.
A
B
B
A
So
the
question
is:
how
do
we
have
a
DNS
for
blockchain
and,
to
be
honest,
I,
don't
know
if
we're
gonna
have
only
one
we
created
one,
because
we
needed
one
right
and
we
wanted
to
create
one.
That
is
not
if
that
blockchain
specific
right,
so
we
wanted
it
to
work
with
sato's
and
with
fabric
and
with
etherium,
etc,
etc,
and
we
didn't
want
to
charge
for
it.
Like
our
big
thing,
we
didn't
want
to
make
money
from
the
names,
so
we
do
a
completely
crazy
approach.
A
We
just
went
to
the
vendors
and
we
asked
them
to
help
us
build
this,
so
they
sponsor
the
development
and
we
didn't
want
them
to
own
it.
It's
kind
of
a
sure
thing
and
if
you
look
here
to
the
left,
menu
Oh
where's,
my
slice
and
you
can
extend
what
everybody's
looking
to
me.
Finally,
I
just
near
this
place,
so
that
I
don't
know.
A
A
A
Collaborating
now
with
Cola
were
creating
like
a
big
partnership
on
getting
some
of
the
certified
applications
listed
on
to
the
unbounded,
but
they
will
be
the
ones
that
are
certifying
kind
of
the
dead
abs,
but
we
will
still
be
able
to
kind
of
list
them
out,
but
the
idea
was
to
be
able
to
move
data
in
a
way
that
its
auditable
and
reproducible
right.
So
the
main
problem
that
you
have
in
proteins
in
general:
yes,
it's
not
the
fastest.
A
And
yes,
we
are
wasting
a
lot
of
storage
because
everybody
keeps
a
copy
of
everything,
but
there
is
a
huge
value
and
being
able
to
reproduce
numbers
right.
So
we
wanted
to
have
a
system
where,
when
I'm
doing
when
I'm
making
a
DNS
resolution
request
so
I'm
saying
what
is
the
IP
of
google.com
I
would
like
to
be
able
to
verify
that
I
got
the
right
data
and
I
used
it
and
I
can
even
use
it
in
a
smart
contract.
So
that
was
like
the
it's
actually
modern.
A
A
directory
right
like
the
idea,
is,
if
I
want
to
resolve
a
name
and
go
to
a
chain
and
request
some
data.
Even
the
name
resolution
is
part
of
the
result,
and
I
can
always
replay
this
and
then
make
sure
that
my
response
and
my
contract
is
actually
deterministic.
So
I
didn't
want
to
make
two
different
calls
and
get
different
numbers,
or
somebody
would
change
the
DNS
and
then
I'll
never
be
able
to
go
to
the
same
request
right.
So
that's
why
we
created
it
with
a
blockchain.
We
used
hydrologic
fabric.
A
There
was
no,
we
could
have
done
it
with
different
chains.
Like
honestly,
we
work
with,
like
I,
don't
know
five
chains
every
day.
So
that's
that
was
not
the
issue.
The
issue
was
to
actually
making
like
very
in
terrible
and
to
make
it
clear
and
how
to
use
stuff
in
a
very
enough
seamless
way
right
so
I'm
sure.
A
I
want
to
show
you
how
it
looks,
and
now
you
see
that
we
created
a
very
consistent
way
of
looking
at
different
block
chains
and
and
they
all
look
the
same
kind
of
if
I
look
at
the
blockchain
Explorer
on
fabric
or
blocks
and
a
story
on
sawtooth,
we
made
it
look
like
you
have
blocks
and
transactions,
and
you
can
fetch
the
data.
You
can
request
for
a
block
number
and
you
know
even
in
public
chain
world.
A
If
this
process
is
not
unified,
like
you
want
to
go
to
Bitcoin,
you
go
I,
don't
know
block
info.
Alright.
If
you
want
to
go
to
Cu,
you
go
to
eat
the
skin.
If
you
go
to
fabric
look,
you
have
to
understand.
We
are
using
a
lot
of
hyper
laser
technologies
right.
We
are
using
the
hyper
ledger.
Explorer.
The
problem
was
not
how
to
run
it
because
all
the
cloud
providers.
You
know
that
provide
you
an
explorer
so
we're
using
that.
But
how
do
you
connect
it
to
the
chain
right?
A
How
do
you
get
access
to
the
data
that
you
can
share
in
the
permission
chain?
Right?
That's!
The
difficulty.
Difficulty
is
actually
to
make
this
to
make
this
permission.
Chains
choose
what
they
share
and
what
they
don't
share,
because
in
fabric
you
have
channels,
it's
obvious.
You
have
like
transaction
families.
You
know,
instead,
that
different
technologies
are
doing
something
very
similar
in
terms
of
kind
of
conditional
sharing,
actually
I,
don't
even
if
you
guys
go
to
a
lot
unbounded
notice.
A
Ericom,
you
just
be
able
to
see
I,
don't
know
why
we
can
say
this
doesn't
doesn't
help.
I
can
try
to
restart
everything,
but
I'll
try
to
start
everything
you
just
died,
but
the
idea
is
that
I'll
be
able
to
go
so,
let's,
let's
sorry,
question
five
minutes,
so
that's
about
what
we
can
do
with
unbounded
right.
The
easiest
thing,
first
of
all,
the
whole
system
is
free,
so
you
can
just
go
in
creative
if
you
have
a
network,
whether
it's
fabric,
if
you
call
like
whatever
it
is,
you
can
get
your
name.
A
This
name
is
unique.
At
least
in
this
system.
We
have
a
dispute
resolution
mechanism
where
which,
for
example,
doesn't
have
so
you
cannot
reserve
a
name
to
this
trademark.
That
is
not
yours.
So
we
have
a
procedure
where,
when
you
make
a
request,
we
look
at
it
and
actually
there
is
a
consensus
mechanism
at
the
moment.
Just
the
partners,
it's
sponsored,
but
we
would
like
to
expand
it.
No
problem.
Oh
it
did.
I
good
is
back
okay
and
the.
B
A
A
I
can
just
share
my
slides
and
I've
summarized
anyway,
but
yeah.
So
if
you,
if
you
guys,
go
to
like
an
abundance
of
that
work,
you're
able
to
see
like
three
things
you
can
sign
up
and
create
the
user
for
free.
You
can
register
and
network
if
the
name
is
not
taken,
so
you
can
reserve
your
fabric
network,
your
sort
of
network,
etc,
etc,
and
the
highlight
of
the
thing,
if
you
go
to
any
network
you'll
be
able
to
look
at
whatever
is
public.
A
So
if
I
look
at
the
fab
car
example,
we
have
our
Duchess
example
on
Soto's.
If
you
look
at
any
kind
of
public
or
Commission
chain,
you'll
be
able
to
look
at
all
the
previous
blocks
and
transactions
search,
fine
stuff,
and
actually
we
have
a
REST
API
that
allows
you
to
integrate.
So
I
can
fetch
data
from
even
a
permission
chain
if
I'm
allowed
to
get.
If
I
have
the
permission
to
access
this
data.
So
three
things
that
you
can
easily
do
right.
You
can
look
up
networks,
so
it's
this
kind
of
the
discoverability.
A
B
A
I
can
I
would
not
have.
Basically
we
can
classify
so
you
can
list
out
the
project.
You
can
reserve
a
name
now,
even
if
it's
like
a
proof
of
concept,
if
you
are
just
trying
to
do
something
as
a
university
thing,
if
you
try
to
do
something
in
your
innovation
lab
it
doesn't
matter,
you
can
still
list
it
out.
We
have
ranks
so
you
can
say
this
is
an
alpha.
This
is
a
bitter
and
you
can
also
have
the
terms
of
conditions
of
what
you
expect.
A
No,
no
thank
you
so
the
problem
that
we
had
at
the
beginning.
We
were
worried
because
we
didn't
charge
because
we
don't
charge
for
listing
that
everybody's
gonna
list
out
stuff
and
we're
not
gonna
know
if
it's
a
real
network
or
not
right.
So
the
question
was:
do
we
put
like
a
barrier
of
like
I
know
$10
a
year,
something
like
that
or
we
just
make
it
easy
and
just
ping
the
network
and
see
if
it
responds.
A
A
B
A
So
actually
we
have
some
nice
technologies
there
right.
So
the
one
thing
that
people
wanted,
so
we
work
with
highly
regulated
environments
right
so
I'll
give
like
very
nice
use
cases
that
are
very
specific,
but
there
is
a
less
important
and
topic.
This
is
like
the
enterprise
stuff
so
easily
with
heavy,
but
some
networks
want
to
have
a
prove
of
existence.
A
Meaning
I
would
like
to
show
that
something
occurred
for
real
and
I
want
to
be
able
to
see
that
somebody
signed
it
and
it
was
really
there
and
nobody
is
proofing
it
right,
but
the
problem
is
that
information
space
I
can't
share
with
you
all
my
customer
information
as
a
bank,
but
I
do
want
to
tolerate
Jonathan
bitpay.
So
there's
a
lot
of
stuff
that
you
can
do
with
the
validators,
and
you
can
so
one
big
feature
that
we
are
adding
now
you
can
query
a
network
for
its
validators.
A
You
want
to
know
who
is
running
the
show.
Ok
so
especially
in
permission
chains
like,
let's
say
financial
sector,
you
wanna
know
who
are
the
banks
that
actually
validating
stuff,
and
you
need
to
choose
whether
you
trust
the
signature
or
not.
So
you
can
get
the
public
key
and
when
I
give
you
a
transaction,
you
can
verify
a
signed
transaction
with
their
private
key.
Then
it's
up
to
you.
If
you
want
to
trust
it
or
not,
but
at
least
you
get
a
signature
without
looking
at
everything.
A
This
is
part
of
the
staff
of
not
being
binary
right
like
all
or
nothing
is
it's
that
next
feature.
If
you
are
interested,
like
you
know,
MSP
the
membership
service
provider,
so
on
all
fabric
networks
in
the
world,
we
are
gonna,
allow
people
to
register
the
MSP.
So
when
you
want
to
join
a
network,
you
can
see
the
MSP.
You
say:
I
do
I,
trust
these
guys
or
not,
and
then
you
choose
whether
you
want
to
share
because
there's
a
lot
of
stuff
like
that,
I
think.
A
A
So
you
wanna
know
right
like
in
public
ones.
We
have
a
note
on
each
of
them,
so
even
in
theorem
note
synchronize
never
broken
a
bit
come
on
so
imperiling.
We
just
joined
the
consortium
in
permission,
but
that's
easy
right
public,
where
the
finishing
anyone
can
join
like
there's
no
kind
of
yeah
the
mission.
There
are
two
options:
we
either
run
our
own
node.
A
If
you
trust
us
and
you
can
limit
what
this
node
can
see
like
in
fabric
channel,
so
in
so
that
you
can
have
traduction
families,
if
the
information
is
even
more,
this
permission.
Stuff
is
easy
to
permission
right
because
the
definition
they
making
the
permissioning,
but
we
don't
have
to
be
intrusive.
We
can
also
give
you
an
IP.
I,
where
you
can
answer
our
queries.
We
have
a
standard
that
we
share
with.
All
these
guys
is
what
we
do
with
the
cloud
providers
and
if
you
had
hit
this
like
api,
we
can
query
your
network.
A
So
you
can
choose
what
you
share.
The
only
thing
that
we
do
is
cash
so
that
we
don't
like
if
I
get
like
cuz.
You
know
this
or
you
had
firewalls
and
stuff
that
we
get
in
our
service
attacks,
but
we
don't
want
to
bombard
your
network
right.
So
if
I
see
that
you
will
make
too
many
queries,
we
just
catch
it
and
reply
it
on
your
behalf.