►
Description
Hyperledger Member company, Bosch, will be hosting a session about their journey as contributors to Hyperledger community. The core outcome is Perun project which is now part of Hyperledger Labs. Perun is a joint DLT Layer 2 scaling project between the Robert Bosch GmbH’s “Economy of Things” project and the Perun team of Technical University of Darmstadt. The protocol can be used on top of any blockchain system to accelerate decentralized applications and lower transaction fees. The payment and state-channel technology of Perun protocol is especially useful for high-frequency and small transactions. By providing a cheap, fast, and secure transaction system, the Perun protocol is a major step forward in the mass adoption of blockchain applications.
We will start off with a discussion of scalability challenges and would love to hear from the attendees on their experiences. Then, researchers from Darmstadt University will talk about State Channel Technology before diving into the Perun Framework. There will be time for a demo and an AMA. We will finish off with another discussion round about the challenges the Enterprises face when working with Open Source. We hope together we can come up with some tips!
In the “Hyperledger In-depth: An hour with… .” series, Hyperledger members share learnings from their projects and try to answer all the hard questions about the pains of working with DLTs. It is not yet another webinar: participants will be encouraged to take part, come with prepared questions and voice opinions. Expect live demos and tutorials, stories from the battle field and hopefully some heated discussions. Let's get out of the zoom fatigue and engage to share experiences and build a stronger community
----
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 #Blockchain
A
A
A
A
Now,
as
hyperledger
in-depth
is
not
a
typical
zoom
presentation,
it
is
really
about
being
interactive,
so
please
participate.
We
have
discussions
set
us
scheduled
throughout
the
talk,
so
there
will
be
time
to
participate
to
engage
if
you
feel,
like
you
know,
everybody's
speaking
and
you
want
to
just
jump
in,
you
can
raise
your
hand,
which
is
a
button
that
you
have
on
your
navigation
bar.
A
B
Okay,
I
will
arrange
it
a
little
bit.
Yep.
Okay,
so
looks
good
on
my
side
as
well,
so
yeah
welcome
everybody
again.
My
name
is
matthias.
I'm
working
for
previously
theo
darmstadt.
We
now
founded
a
company
called
polycrypt,
and
I
will
presenting
be
presenting
to
you
together
with
my
colleagues,
also
from
bosch.
B
B
It's
the
general
observation
that
popular
blockchains
that
we
use
widely
don't
scale
very
well.
So
when
we
look
at
the
two
most
popular
in
the
open
space,
bitcoin
and
ethereum,
then
we
have
a
transaction
throughput
limit
of
about
5
to
15
transactions
per.
Second,
we
have
transaction
confirmation
times
in
the
order
of
minutes
or
potentially
hours,
and
we
have
transactions
costs
that
vary
a
lot
depending
on
the
load
on
the
blockchain.
B
So,
on
the
right
hand,
side
you
can
see
the
graph
of
the
gas
price,
which
is
the
basis
for
the
ethereum
transaction
price,
and
even
if
we
don't
convert
it
to
us
dollars,
even
the
inherent
gas
price
varies
a
lot
over
time
depending
on
the
load
on
the
ethereum
network.
So
this
really
makes
these
these
blockchain
technologies
that
are
used
for
for
some
user
cases,
but
for
other
use
cases
they
this
makes
them
insufficient.
B
So,
for
example,
when
we
think
of
micropayments,
we
need
usually
high
throughput
low
transaction
cost
fast
confirmation
times
the
same
for
high
frequency
trading.
It
doesn't
work
if
we
have
to
wait
several
minutes
or
hours
for
our
confirmation
and
any
day-to-day
shopping
of
goods
that
are
not
off
of
high
value,
isn't
feasible
with
with
these
higher
transaction
costs.
B
C
C
C
Next,
please,
the
iot
space
consists
of
several
kinds
of
entities
from
cloud
native
instances
up
to
small
embedded
devices.
Looking
there
at
the
different
domains
and
constellations
like
manufacturing
or
sensors.
You
cannot
assume
that
every
entity
has
a
persistent
connection
to
the
internet.
This
is
on
one
hand
resulting
from
energy
optimizations
if
it
runs
by
battery.
For
example,
on
the
other
hand,
it
can
be
located
in
a
local
available
secured
network
with
no
direct
internet
connection.
C
D
D
So,
as
mentioned
already,
whether
you
experience
too
low
transaction
throughput
in
particular
for
microtransactions,
if
you
experienced,
of
course,
this
is
rather
relevant
for
public
blockchains.
But
if
you
experienced
a
problem
with
transaction
costs
and
also
which
is
sometimes
very
important
for
some
applications,
if
you
sometimes
experience
that
the
confirmation
took
too
long
so
that
the
finality
of
a
transaction,
even
if
it
is
just
seconds
that
can
still
be
a
big
problem
in
some
applications-
and
this
is
also
something
that
we
will
can
tackle
with
our
solutions.
D
A
D
A
D
D
A
E
Yeah
fine
yeah!
Well,
I
don't
have
my
my
my
camera
activated
yeah,
I'm
just
using
it
sometimes
for
token
swaps
and
with
metamask.
It
already
finds
the
cheapest
the
cheapest
platform
to
swept
the
tokens,
but
it's
still
way
too
expensive
yeah.
So
I
hope
there's
an
easier
solution
which
can
be
used
as
easily
with
with
meter
mask
as
a
uniswap,
for
example,.
D
F
D
A
D
So
probably
some
of
my
colleagues
can
answer
that
better,
because
iot
is,
of
course,
just
one
application
of
the
technology,
but
we
already
have
proof
of
concepts
running
on
iot
devices-
I
don't
know,
maybe
hendrick
or
daniel-
want
to
share
some
of
their
experience
in
doing
that,
because
we
also
have
in
in
at
theo
darmstadt.
We
also
have
projects
with
students
where
they
we're
exactly
using
the
pyruvate
framework
for
scaling
on
iot
devices.
A
Right
greg
mentioned
that,
while
ethereum
is
also
part
of
hyper
ledger
and
quotes
part
of
so
it
comes
at
the
price,
but
in
his
opinion,
bitcoin
is
beyond
reach
for
most
right
now,
which,
yes,
it's
a
good
point.
We
all
wish
that
we
were
early
in
early
adopters
right
well,
I'll.
Let
you
continue
sorry.
D
B
You
deposit
some
funds
on
the
smart
contract,
and
then
you
can
interact
without
any
of
the
on-chain
limitations.
So
once
you've
deposited
the
funds
on
the
contract
and
you
signal
with
whom
you
want
to
interact
offchain,
you
can
transact
with
basically
unlimited
throughput,
which
is
just
limited
by
the
number
of
signatures
that
your
computer
can
generate.
B
So
this
is
really
a
direct
communication,
and
this
is
also
why
it
achieves
instant
confirmation
times
and
our
protocols
that
we
developed
on
the
research
side
are
provably
secure,
and
this
also
has
another
interesting
property.
We
can
even
have
cross
chain
support,
so
we
can
open
channels
between
different
blockchains
and
have
clients
from
on
different
blockchains
exchange
funds
with
each
other,
even
though
they
are
not
connected
to
the
same
network.
B
B
Then
clients
can
either
directly
build
on
top
of
the
sdk
or
if
they
are
thin
clients,
they
can
use
the
the
peru
node,
which
is
in
some
sense
a
wrapper
around
the
sdk
which
enables
thin
clients
to
work,
and
this
is
built
by
bosch
and
then
in
a
separate
repository.
We
have
the
smart
contracts
which
realize
the
smart
contract
logic
that
I
just
talked
about
in
more
detail.
B
How
is
the
framework
built
and
what
component
does
the
framework
have
so
at
its
core?
As
I
said,
there's
the
stage
and
a
logic
and
an
important
property
is
that
we
build
it
with
modularity
in
mind,
so
we
initially
planned
to
have
a
framework
which
is
usable
with
many
types
of
blockchains,
not
just
with
ethereum,
but
you
can
build
your
own
blockchain
adapter
and
through
our
abstract
interface,
you
can
integrate
it
easily
without
changing
the
application
code.
B
That's
from
my
point
of
view
a
main
feature
of
our
framework
and
the
same
accounts
for
the
persistence,
so
you
can
plug
in
your
favorite
database
adapter.
You
can
plug
in
your
favorite
logging
engine
in
your
favorite
message
broker.
So
all
of
these
things
are
not
directly
integrated
into
the
framework.
H
G
So
paro
node
is
a
multi-user
node
that
we
are
building
using
the
parent
sdk,
which
provides
the
opportunity
for
devices
with
less
resources
to
use
the
parent
protocol
and
make
state
channel
at
the
core.
We
use
the
parent,
sdk
and
initialize
the
different
adapters
required
for
it,
so
we
use
ethereum
adapter
for
blockchain
and
level
db
for
persistence
and
so
on,
and
on
top
of
that
we
add
two
other
functionalities.
G
So
the
first
is
key
handling
and
the
first
thing
we
have
implemented
is
like
to
use
ethereum
key
stores
and
second
is
option:
identity
provider.
So
this
optional
provider
is
like,
if
you
have
an
option
network
and
many
participants
in
that,
you
need
two
things.
One
is
an
identity
of
the
provider
which
using
which
he
will
authenticate
his
ownership
of
that
identity.
G
Second,
is
the
communication
address
to
reach
him?
So
this
is
what
this
module
does,
and
this
complete
adapters
and
identity
providers
are
all
encapsulated
in
a
session
so
that
multiple
users
can
use
the
same
node
and
to
use
the
node.
We
have
a
user
api
and
this
api
is
define
an
abstract
way
that
you
can
either
use
it
as
direct
function
calls
or
as
a
remote
calls.
So
in
the
upcoming
demo.
I
will
show
you
the
using
this
api
via
remote
call
a
grpc
interface.
G
A
G
D
So
we
use
if
we
have
a
very
modular
approach
using
dependency
injection
by
which
you
could
use
any
database
back
end
and
in
particular,
if
you
want
to
use
couch
to
be
instead
of
level
db.
We
could
basically,
within
one
or
two
days,
just
provide
a
wrapper
for
this,
because
we
have
like
an
abstraction
using
a
key
value
store
and,
as
far
as
I
remember,
couchdb
is
also
a
key
value
store,
so
we
can
very
quickly
just
integrate
any
key
value
store
as
as
the
backend.
D
F
D
Yeah,
there's
a
there's,
a
nice
parallel
that
you
can
see
here.
So
basically,
when
you
have
a
contract
with
someone
like
a
real
life
contract
with
a
person,
let's
say
you
have
a
business
relationship
with
with
another
business.
You
have
a
contract
right,
it's
a
very
complex
contract,
but
of
course
you
do
the
business
with
the
other
business
person
peer-to-peer
right,
you
don't
go
to
a
judge
or
to
a
court.
Every
time
you
you
just
do
a
normal
business
transaction,
and
this
is
exactly
the
way
how
we
use
the
blockchain.
D
So
if
you
use
the
blockchain
for
every
single
transaction,
that
basically
means
you
go
to
the
court
to
do
every
single,
even
benign
business
transaction.
And
basically
that's
the
that's
the
metaphor
here
that
we
use
the
that
we
use
a
blockchain
only
as
a
dispute
handler
as
a
dispute
resolver.
So
it's
a
trust
anchor
but
normal
transactions.
If
all
involved
parties
behave
honestly,
can
then
be
done
off
chain.
That's
the
idea
and.
A
D
So
the
idea
is
in
any
in
any
kind
of
transaction
there's
at
least
one
party
who
would
have
like
a
negative
outcome.
If
so,
if
one
party
tries
to
cheat
another
party,
then
that
other
party
has
a
disadvantage
and
then
that
other
party
can
just
go
to
the
blockchain
and
dispute
the
state
of
the
system,
so
it
basically
works
like
this.
So
every
time
you
do
transactions,
you
exchange,
cryptographic
signatures
and
those
signatures
prove
that
all
parties
agreed
on
some
state
of
the
system
on
some
state
of
a
transaction.
D
So
the
thing
is
you:
you
only
can
affect
the
involved
parties.
So
if
three
pt-
let's
say
three
people
are
involved,
then-
and
all
three
people
agree
on
some
state,
then
it
doesn't
matter
because
they
cannot
hurt
anyone
else
outside
the
system,
because
you,
for
example,
using
channels
two
parties
deposit
into
a
channel
and
then
that
channel
only
affects
those
two
parties.
So
even
if
they
both
collude,
they
can
only
cheat
themselves
and
not,
and
it
doesn't
have
any
other,
like
effect
on
anything
outside
their
channel.
So
to
speak.
B
F
B
I
would
also
like
to
point
out
that
you
can
actually
program
this
resolution
mechanism
and
what's
a
weather
transaction
on
that
channel,
so
we
have
an
app
concept
on
the
channel
level
where
you
can
program,
what
is
a
valid
transition
for
that
channel
and
what
is
an
image
transition?
So
you
can
even
impose
rules
on
what
is
okay
or
not
not.
Okay,.
D
I
mean
it's
rather
general,
so,
for
example,
when
you
have
iot
devices,
you
probably
would
use
a
node
like
the
node
from
bosch,
because
you
would
then
have
like
one.
It's
like
an
intermediate
server
service
running
and
then
you
have
thousands
of
iot
devices
and
you
usually
have
so
what
you
usually
experience
in
those
systems
is
that
you
don't
have
so
much
malicious
acting.
But
if
that
happens
of
course,
then
the
node
would
jump
in
and
then
resolve
the
dispute.
D
So
that
means
the
node
would
send
a
transaction
to
the
blockchain
opening
a
dispute
and
then,
of
course,
the
parties,
the
particular
party
involved
in
the
dispute
so,
for
example,
the
one
party
that
was
behaving
dishonestly
of
course,
then
at
that
point
you
cannot
further
transact,
but
anyways
I
mean.
If
a
party
is
misbehaving,
then
then
you
want
to
stop
transacting
with
that
party
anyways.
D
B
G
Presenting
a
split
of
the
screen,
so
the
first
split
will
be
the
blockchain
node
running
I'll,
be
running
ganache
airline
node
and
in
the
second
split
I'll,
be
running
a
parent
node
and
in
the
bottom,
two
splits
I'll
be
running.
Two
client
applications
that
we
provide,
along
with
parent
node,
but
suggest
reference
implementations
to
interact
with
the
parent
node.
So
now
I'll
present
my
screen.
G
Hope
my
screen
is
visible,
so
in
this
split,
as
I
told
I
will
start
a
ganesha
line
node-
and
here
I
will
start
the
barrel
nodes
before
I
start
the
parent
node.
I
was
talking
about
the
id
provider
and
for
building
the
parent
node
and
generating
the
default
configuration
files.
You
can
have
it
look
at
the
readme
files,
but
I
can
point
you
to
one
of
the
configuration
files.
That's
here
just
a
second.
G
So
you
have
the
parent
node
binary
and
then
you
can
generate
the
configuration
files
here.
So
if
you
generate
the
alice,
if
you
look
at
alice
directly,
there
are
four
components:
one
is
the
database
directory
where
the
level
db
database
will
go
and
then
there
is
a
id
provider
file.
So
if
you
look
into
the
id
provider
file,
it
actually
tells
who
bob
is
like
what
is
his
option
address
and
what
is
his
communication
address
and
how
he
can
be
connected
like
we
are
tcp
connection
or
whatever?
G
G
So
now
we
have
started
the
paranoid
cli
and
for
the
first
time
we
need
to
use
the
contracts
we
needed.
The
context
we
deployed,
but
in
real
life
case
I
think,
there's
only
a
singleton
instance
of
the
contract
deployed,
and
hence
this
will
not
be
done
for
like
every
time.
You
want
to
open
a
contract.
G
G
Here
so
this
session
will
initialize
the
id
provider
and
key
store
and
everything
else.
So
now
we
have
that
we
can
check
if
you
are
able
to
get
bob's
id
from
this
terminals,
so
yeah
we're
able
to
get
so.
It
tells
the
address.
Now
we
can
send
a
channel
opening
request
to
bob
so
channel,
send
opening
request
to
bob,
and
we
can
say
the
initial
balance
should
be
10
for
myself
and
10
for
bob.
G
G
Ethers-
and
this
is
bob's
balance,
which
is
also
like
89.9,
something
ethers.
So
now
we
are
free
to
send
any
number
of
transactions
between
these
two
parties.
So
I
will
try
to
send
a
transaction
from
this
person
and
on
this
channel
and
I
will
say,
sent
to
ethers
so
he
gets
a
notification
which
he
can
accept.
G
So
that
can
also
be
accepted.
So
this
way
you
can,
you
can
either
accept
the
transactions,
also
reject
them.
If
you
check
them,
then
the
channel
states
are
not
updated.
So
if
you
look
at
the
states
after
the
channel
update,
you
can
see
the
update
balance
changes,
but
none
of
this
is
reflected
on
change,
so
the
balances
still
remain
the
same.
Now,
if
either
of
the
parties
feel
that
they're
not
want
to
transact
anymore
and
want
to
close
the
channels,
they
can
send
a
close
request.
G
So
if
it
is
a
collaborative
close,
what
happens
is
that
a
finalized
state
is
sent
to
other
party
which
he
signs
and
if
both
parties
sign
that
state,
then
the
finalized
state
is
submitted
to
blockchain.
Then
it's
very
fast
resolution,
because
both
the
parties
agree,
but
in
this
case
I
will
show
you
where
one
of
the
parties
is
rejecting
the
finance
update.
Still,
the
first
party
is
able
to
settle
the
channel
on
blockchain,
so
I
will
say,
channel
close
and
settle
on
chain
and
the
channel
name.
G
So
if
you
look
at
here,
he
is
getting
another
update
which
says:
should
I
accept
the
finalized
state?
I
will
detect
it
here
so
though
he
is
rejecting
it.
It
will
take
a
little
more
time
because
that
we
should
provide
some
time
out
for
the
parties
to
wait
and
provide
some
challenges,
but
after
the
timeout
the
channel
automatically
gets
settled
and
the
balances
are
withdrawn.
So
now
we
get
an
update
that
the
channel
is
settled,
so
we
can
check
the
on-chain.
G
G
B
C
C
The
goal
of
I
blockchain
is
to
build
an
open
and
decentralized
marketplace
for
the
industry
4.0
domain
as
a
demonstrator,
especially
for
the
so-called
order
controlled
production
use
case
scenario,
which
is
described
by
the
platform
industry
4.0
consortium
as
a
sample
for
a
better
understanding.
You
can
think
of
ordering
and
customizing
a
bicycle
which
needs
then
to
be
manufactured
and
assembled
by
different
suppliers
based
on
the
chosen
parameters
by
the
customer.
C
D
A
D
I'm
happy
to
repeat
that
yeah,
so
so
in
general,
the
sdk
it
doesn't
make
any
expectations
on
how
peer-to-peer
messages
are
transported
because
again
we
use
dependency
injections,
so
you
can
insert
any
communication
mechanism
that,
for
example,
already
is
in
place.
I
mean,
probably
if
you
want
to
insert
this
into
some
existing
application.
D
You
already
have
your
communication
infrastructure
right,
so
maybe
you
use
lib
p2p
or
maybe
you
have
encrypted
tcp
connections,
or
maybe
you
have
some
other
kind
of
message
broker
system
and
any
can
any
kind
of
system
can
be
used
to
then
just
transmit
our
system,
our
messages.
So
basically,
of
course
you
have
to
implement
some
interface,
so
you
basically
have
to
provide
a
kind
of
thin
wrapper
around
the
the
communication
system
that
you
have
and
then
we
can
reuse
your
existing
communication
system
to
transfer
the
peer-to-peer
messages
that
our
framework,
our
protocol
needs.
A
A
A
Oh
someone
added
high
relevance:
okay,
so
between
medium
and
high,
is
what
we're
seeing
right
now
so
yeah.
Well,
what
do
you
think
then?
Do
you
think
that
are
you
happy
with
this
result
or
would
you
well,
I
guess
you
are
you
you'd
rather
have
it
high
than
not
how
how
would
it
be
relevant
to
other
industries?
So
we
talked
about
iot.
But
how
do
you
imagine
using
parent-
and
I
know,
supply
chain
or
something
else.
D
So
so
in
general,
so
this
particular
technology
that
we
present
your
channels
are
most
relevant.
If
you
have
recurring
transactions
between
the
same
set
of
participants,
or
at
least
if
you
have-
or
you
can
also
have
a
like
hub
and
spoke
infrastructure,
so
basically
you
have.
You
can
have
like
one
hub
in
the
middle
and
then
you
have
thousands
of
other
devices
or
people
connected
to
that
hub.
D
So
this
is,
in
general,
the
the
kind
of
application
usage
scenario
where
this
makes
sense
so,
for
example,
in
supply
chain,
you
sometimes
have
the
situation
that,
of
course,
basically,
when
you
update
the
system
state,
for
example,
you
use
a
fabric
system,
hyperledger
fabric,
and
then
you
you
want
to
publish
some
system
update
state.
Then
of
course
it
should
be
visible
to
the
whole
world.
So
to
speak
right
because
you
use
the
ledger
as
a
means
of
single
source.
D
F
B
F
B
That
might
be
also
a
use
case
where
you
can
still
use
channels.
I
would
be
interested
from
those
people
who
rated
medium
or
low
what
yeah,
what
why?
Why
is
it
a
little
bit
relevant,
but
could
we
extend
the
framework
maybe
to
make
it
more
relevant
or
what
are
their
main
challenges
or
main
interests
in
that
area?
So,
if
somebody
would
like
to
comment,
I
would
be
curious
to
hear.
A
A
I
Hi
hi,
yes,
I
am
working
at
this
particular
use
cases
wherein
we
require
a
lot
of
transactions
amongst
two
devices,
basically
hardware
devices
and
because
those
are
the
micro
payments,
which
is
why
I
was
looking
at
peru
and
I
have
been
following
it
since
almost
six
to
eight
months.
But
I
really
wanted
to
know
the
dispute
logic
and
glad
that
I
could
get
it
from
you.
I
D
I
mean
just
to
reiterate
here,
so
it
really
depends
on
the
on
the
on
the
whole
system
setup
you
so
either
each
device
itself
can
run
the
dispute
in
case
of
of
a
dispute,
but
of
course
in
in
like
some
industrial
application,
or
it
sounds
like
in
your
application.
It
probably
makes
more
sense
that
you
have
like
a
node
a
server
running
for
you
that
is
handling
all
the
disputes
so
that
the
all
the
thousands
of
devices
don't
really
need
to
handle.
I
D
F
D
F
G
I
One
thing
which
we
can
also
focus
on
is
how
to
address
the
confidentiality
of
the
data
that,
because,
as
far
as
I
saw
in
the
demo,
when
two
nodes
were
interacting,
we
can
see
that
the
addresses
were
been
issued.
So
if
we
have
some
encoding
or
encryption
there
to
ensure
that
the
data
or
whatever
transactions
are
happening
remains
confidential
not
only
to
the
parties
but
also
when
they
are
stored,
finally
appended
to
the
ledger
as
well,
so
that
thing
can
also
be
taken
care.
F
D
D
So
say
you
open
a
channel
and
both
parties
put
in
100
and
then
I
don't
know
at
the
end,
you
have
a
channel
where
the
balance
is
50
and
150,
and
then
only
this
final
balance
would
be
visible
on
chain,
of
course,
because
people
withdraw
their
funds
back
on
chain.
But
how
you
came
to
that
final
balance
is
not
visible,
so
the
privacy
of
the
intermediate
steps
so
to
speak
is
preserved
here.
H
H
We
started
to
implement
a
first
version
of
this
state
channel
node
application,
and
this
was
always
meant
to
be
open
source,
and
I
think
it
may
be
interesting
to
quickly
recap
what
our.
Why
that?
Why
we
think
it
that
is
so
and
what
the
initial
open
source
strategy
was,
and
that
would
be
the
next
slide.
H
So
we
are
a
potential
user
of
the
technology
and
not
the
technology
provider
per
se.
Actually,
but
our
overall
goal
for
perron
is
that
we
want
to
have
enabled
scalability
of
blockchain
payments
and
smart
contracts
and
without
any
gatekeepers
or
it
shouldn't
be
monopolizable
infrastructure
in
the
end,
to
enable
a
high
volume
of
arbitrary
transactions,
including
scalable
micro
payments,
that
support
our
vision
of
an
economy
of
things.
H
And
if
you
go
to
the
next
thing,
perron
as
it
is
as
we've
learned
as
a
protocol
at
heart,
we
think
it
needs
widespread
adoption
to
function,
and
so
the
main
open
source
goal
is
to
lead
the
standardization
efforts
to
establish
it
as
a
major
part
in
the
payments
and
smart
contracts.
Ecosystem
and
a
second,
very
important
benefit
of
an
open
source
approach,
as
you'll
know,
is
that
open
source
provides
a
framework
for
partner
collaboration
and
we'll
see
that
in
a
minute.
H
H
I
just
wanted
to
point
you
to
an
interesting
article
by
karl
fogle
and
chainsaw
sealed
from
open
tech
strategists
which
they
published
against
mozilla,
which
helps
to
guide
strategic
thinking
about
the
question
how
to
set
up
such
projects
and
they
talk
about
open
source
archetypes,
which
are
just
open
source
project
patterns
until
the
most
fitting
archetype
for
perron
is,
I
think,
a
multi-vendor
infrastructure
archetype,
which
is
exactly
designed
for
non-monopolizable
infrastructure
projects.
And
you
know
many
of
the
well-known
projects
like
kubernetes,
openstack
or
hyperledger
itself
are
some
well-known
examples
now
to
the
next
slide.
H
We
continue
now
that
you
know
where
you
want
to
go.
We
continue
our
journey,
so
we
were
at
the
point
where
we
had
started
with
an
initial
in-house
implementation
and
the
major
obstacles
around
that
time
and
until
the
first
open
source
release,
which
you
already
saw
up
here,
or
a
lack
of
speed
and
ensuing
friction
and
collaboration.
H
So
we
have
different
internal
repos,
different
communication
channels
etc,
and
you
may
have
experienced
similar
things
and
ultimately,
this
led
to
two
independent
implementations
being
open
sourced
in
the
end
of
2019.
So
more
than
a
year
ago,
you
got
the
state
channel
nodes
and
the
first
version
of
the
proven
sdk.
H
So
it
started
to
evolve
into
this
modular
framework
we
presented
today,
and
I
think
the
next
important
step
was
to
move
to
a
neutral
home
to
further
evolve
this
project
and
we're
happy
to
have
founded
at
hyperledger
labs
and
I'd
like
to
use
the
opportunity
here
to
thank
orno,
who
was
our
sponsor
and
ryan
tracy,
who
has
lab
stewards,
helped
us
to
get
the
infrastructure
going
and
not
to
get
martha
who's
our
host.
Here
we
had
to
get
this
rolling
to
start
with
and
with
the
founding
of
polycrypts.
H
We
also
first
see
additional
blockchain
backends
and
I
mean
there's
many
dlts
in
the
hyperledger
space
and
maybe
there's
some
interesting
uses,
and
I
guess
which
ones
get
implemented
depends
on
user
needs
and
it
we
would
also
welcome
contributions.
Of
course,
if
you're
interested
to
get
involved
here,
we're
also
looking
forward
to
virtual
channels
to
support
just
some
of
the
the
the
features
we
haven't
spoken
into
detail
yet,
but
that
would
enable
this
hop
and
spoke
architecture.
I
think,
and
could
even
build
or
enable
cross-chain
transactions
matthias
mentioned
earlier.
H
A
B
You
don't
have
to
pre-determine,
who
can
talk
to
whom
you
can
go
off
chain,
interact
very
efficiently
and
go
on
chain
again
and
create
a
new
group,
or
you
can
even
transact
between
different
different
blockchains
using
that
state
that
the
channel
technology-
and
I
think
this
is
something
I'm
not
totally
familiar
with
all
the
existing
projects.
Honestly.
D
D
But
if
you
say,
okay,
I'm
setting
up
a
system,
but
it's
a
closed
system.
So
it's
like
a
private
blockchain,
and
I
really
know
that
this
is
exactly
the
kind
of
use
case.
And
then
I
don't
know
I.
If
ira
perfectly
covers
this
use
case,
then
I
would,
I
would
suggest
okay,
then
better
use
the
special
purpose
and
software,
because
it's
made
for
this
particular
use
case.
A
G
Explain
it
here,
so
what
the
current
node
that
we
have
per
say
the
parent
node
has
all
functionalities
like
can
set
up
blockchain.
It
can
help
you
to
do
off-intensive
change
transactions
and
it
can
settle.
But
if
you
look
at
iot
use
cases,
maybe
they
will
not
have
the
access
to
the
funds,
because
the
wallets
need
more
security
and
cannot
be
stored
on
embedded
devices.
G
So
they
can
request
for
the
owner
of
the
iot
device,
some
gateway
to
set
up
the
state
channel,
and
they
can
have
components
only
for
making
off-chain
transactions
and
the
setting
of
stitch
channel
and
closing
can
be
taken
care
of
by
the
gateway
and
for
like
off-chain
transactions.
They
can
completely
do
independent
of
the
gateway
itself.
So
that
is
one
of
the
directions
that
we
are
looking
for.
Light
nodes
where
we
have
a
minimal
possible
functionality
on
the
embedded
device
to
do
off-chain
transactions.