►
From YouTube: Transparent Forest and Nature Management in Flanders (Belgium) using Hyperledger Fabric
Description
Daan Poron, Kunstmaan | Accenture Interactive
Together with the Flemish government, Daan has been working on a proof of concept trying to give an active identity to pieces of land and let them interact with other stakeholders like the owners, maintainers, government employees, and contractors. In this presentation, Daan Poron will talk about their experience with Hyperledger Fabric for creating this proof of concept; the technical and UX design decisions they made, how they deployed this to multiple machines on Amazon AWS, the challenges they faced and the different open source tools they created for completing this proof of concept successfully.
----
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
So
yeah
I'm
going
to
talk
today
about
real
Kunzman,
Accenture,
interactive,
think
of
blockchain
and
our
distributed
Ledger's
as
a
an
ideal
experience
day.
But
in
this
presentation
it
will
be
primarily
about
how
we
use
the
technology
to
deliver
those
experiences
and
most
of
the
experiences
that
we
are
thinking
about
involves
improving
the
lives
of
people.
A
Things
and
since
2016
I've
been
working
in
the
blockchain
team,
where
we've
been
thinking
about
use
cases
and
also
been
experimenting
with
different
technologies
and
in
the
project
I'm
going
to
talk
to
you
today
we
use
hyper
ledger
fabric,
so
yeah
it's
a
project.
We
did
for
the
Flemish
government,
where
we
got
innovation
budgets
to
think
about
how
we
could
improve
the
lives
of
people
who
are
involved
with
managing
nature
like
an
owner
of
a
piece
of
land,
someone
who
needs
to
maintain
it
and
also
the
public
servants
themselves.
A
But
we
try
to
get
even
a
step
further
and
we
wanted
to
see
how
we
could
use
the
technology
to
improve
the
ecological,
social
and
economic
values
of
nature.
It's
already
project
within
a
year
ago,
and
I
will
go
into
the
technical
stuff
as
quickly
as
possible,
so
how
we
did
it,
but
first
I'm
going
to
tell
a
bit
about
the
business
case
itself.
A
All
the
code
is
open
source
by
the
Flemish
government,
so
you
can
find
it
on
github,
but
I
will
provide
a
link
later
on
so
about
the
business
case
in
Belgium,
people
get
subsidies
for
managing
nature
and
all
they
have
to
do,
for
that
is
create
a
nature
management
plan.
That's
this
I've
secured
and
state
of
a
piece
of
nature
and
the
future
states
aware
they
want
the
the
nature
to
be
in
twenty
years.
A
There
was
no
transparency
in
the
subsidy
flow,
even
if
they
would
buy
a
Tesla
with
it,
which
was
also
ecological.
They
yeah,
it
wasn't
meant
for
that,
so
that
was
really
sure
they
had
and
with
all
those
problems
in
mind.
We
try
to
reading
the
ecosystem
and
we
came
up
with
following
a
proof
of
concept,
going
to
show
a
small
video
describing
what
we
did
if
it
works.
B
The
environment,
therefore,
we
manage
nature
very
closely.
Woods
and
parks
are
monitored
by
governments
and
environmental
organizations,
governments
that
usually
means
a
lot
of
administration,
but
what
if
we
could
manage
it
without
hassle?
Wouldn't
it
be
fantastic
if
we
could
give
people
complete
and
crystal-clear
transparency?
B
We
built
a
prototype
application
where
owners,
nature
organisations
and
managers,
engineering
firms,
contractors
and
the
agency
for
nature
and
Forests
can
collaborate
and
easily
monitor
the
evolution
of
nature
and
the
subsidy
settlement.
Blockchain.
Yes,
blockchain.
It's
a
new
technology
that
will
dramatically
change
the
way
we
exchange
information,
more
specific,
it's
a
distributed
ledger
in
which
all
kinds
of
transactions
can
be
exchanged
and
verified
in
a
trusted
way
without
the
control
of
a
central
party.
It's
easy
to
use
and
highly
trustworthy
as
all
the
transactions
are
securely
stored
on
the
blockchain.
B
The
results
of
our
prototype
is
a
complete
new
ecosystem
that
maximizes
the
ecological,
social
and
economic
value
for
nature
and
forests
in
Flanders
subsidies
are
an
important
component
of
the
application
and
they're
paid
in
the
form
of
a
euro
backs
digital
token.
By
creating
this
token,
we
made
it
possible
to
issue
subsidies
to
pieces
of
land.
Each
piece
of
land
has
its
own
rules
programmed
on
how
subsidies
can
be
spent,
making
sure
subsidies
flow
to
the
rightful
beneficiary
owners,
nature,
managers
and
contractors.
B
In
other
words,
this
new
app
offers
absolute
convenience
and
efficiency,
resulting
in
the
correct
use
of
subsidies,
less
administration
and
more
resources
and
people
in
the
field,
and
that's
not
all
this
pioneering
proof-of-concept
show
how
we
can
reshape
the
complete
government
for
the
better.
In
the
coming
months,
we
will
rework
the
prototype
into
a
real-life
application
and
start
rolling
it
out.
Let's
use
technology
to
reach,
strengthen
our
fragile
relationship
with
nature
and
take
care
of
it
with
all
the
respect
it
deserves.
A
A
The
first
thing
was:
we
wanted
to
see
if
we
could
create
an
identity
for
a
piece
of
land
so
that
we
could
gather
all
the
attributes
of
a
piece
of
land
in
in
one
authentic
source
and
also
to
try
to
see
if
it
would
be
possible
for
a
piece
of
land
to
participate
in
transactions.
The
second
part
was
automation
by
continuous
registration
effects
instead
of
on
regular
checkpoints,
so
right
now,
every
five
years
they
will
see
what
the
evolution
of
nature
is
doing
and
then
they
will.
Then
they
can
take
actions
on
that.
A
So
there
are
few
actors
involved
owner
of
a
piece
of
land,
maintainer
contractor
and
then
the
public
servants
they
were
working
on
with
objects
like
a
piece
of
land
which
had
an
owner
in
nature
management
plan
than
nature,
dives
that
get
defined
and
a
few
contracts.
And
then
the
coins,
the
user
journey,
was
splitted
into
four
parts,
creating
a
nature
management
plan
where
the
owners
will
agree
on
a
piece
of
land
that
gets
assigned
to
a
maintainer.
The
Tcat
will
maintain
it
and
then
the
maintainer
can
start
making
observations.
A
We
have
the
maintenance
subsidies,
where
the
maintenance
maintenance
for
subsidies,
the
approver,
the
public
server
servant
will
need
to
approve
it
and
then,
if
it's
approved,
the
the
coins
will
flow
directly
to
the
piece
of
land
instead
of
to
the
maintainer.
And
then
we
have
the
work
contracts
where
the
maintainer
and
the
contractor
will
set
up
a
work
contract.
The
money
will
flow
into
the
contract
and
after
the
work
is
done,
the
money
will
flow
to
the
contractor.
A
There
was
also
an
extra
subsidy
part
there
that
we
integrated
and
on
the
last
process,
was
where
the
contractor
could
exchange
these
nature
points
for
euros,
but
we
didn't
do
that
in
the
proof-of-concept.
So
so
technically,
it
was
our
first
proof
of
concept
using
hybridized
fabric.
We
had
previous
experiences
with
other
technologies.
It
was
complex
data
because
geographical
information
is
it's
quite
complex.
A
You
have
yeah,
we
had
to
do
some
intersections
and
to
do
that
with
yeah
with
contours.
It
was
quite
difficult.
Also,
the
Flemish
government
was
saying
that
I
wanted
to
create
generic
building
blocks
so
that
they
could
use
those
blocks
in
in
other
projects
and
yeah
and
that's
what
we
wanted
to
keep
in
mind
while
creating
the
application
and
then
yeah,
we
use
hydrology
fabric.
It
was
a
year
ago,
so
1.0
was
just
released,
but
we
used
1.1
because
yeah
it
wasn't
better.
We
are
coming
from
a
web
background
as
well,
so
we
have.
A
We
had
a
lot
of
notes.
Developers
no
go,
we
didn't
know,
go
yet
and
Evernote
geo
libraries
for
go
at
the
time,
so
we
chose
to
use
no
chess.
There
are
a
lot
of
other
reasons
why
we
use
hyper
ledger
fabric,
also
one
because
we
want
to
experiment
with
that
and
see
what
the
technology
is
all
about,
see
how
the
components,
work
and
stuff
like
that.
We
chose
not
to
be
used
composer
because
they
wanted
to
create
generic
building
blocks
so
and
the
way
we
saw
composer
was
more
like
a
black
box.
A
That
was
doing
a
lot
of
things,
but
it
was
a
bit
magically.
So
we
use
hyper
ledger
fabric
to
really
understand
why
the
order,
the
beer,
how
do
they
work
to
go
together?
How
does
the
endorsements
work
and
so
on,
so
that
we
could
get
valuable
insights
that
we
could
give
to
our
client
I'm
going
to
talk
about
how
we
set
it
up?
It's
in
three
parts,
the
first
part
it's
about
how
we
set
up
the
network:
I'm,
not
really
a
DevOps
guy,
so
I
know
high
level
how
we
did
it.
A
But
if
you
have
questions
about
that,
I
can
get
you
into
context
with
who
did
that
so
yeah
it
was
put
on
in
high
pralaya
fabric
1.1
right
now
we
are
at
1.3
and
I.
Think
1.4
will
be
released,
so
there
are
a
few
things
that
might
be
outdated
or
can
be
done
differently
at
the
time.
So
but
I
think
the
message
will
be
same
so
setting
up
the
network,
we
had
three
organizations
that
needed
to
work
together
all
organizations
from
the
Flemish
government.
A
Yes,
a
and
B
we,
which
is
the
department
of
nature
and
Forests
itself,
and
with
the
Flemish
government,
it's
the
vo
one
and
then
GRB
they
had
data
about
the
pieces
of
land
and
who
is
the
owner
of
that
piece
of
land
we
created.
We
wanted
to
create
two
channels,
one
virtue
or
B,
because
they
have
private
data
about
the
owners
and
on
the
public
channel,
where
everybody
can
yeah
we're
all
public
data
or
all
the
data
that
the
Flemish
government
could
know
could
be
stored.
A
We
also
stored
everything
on
chain
because
we
wanted
to
see
how
far
we
could
go
if
he
had
all
the
data
at
hand.
The
citizens
have
no
nodes.
They
connect
through
a
note
from
the
Flemish
government
because
it
would
be
would
have
been
too
complex,
but
we
talked
with
nature
organisations
to
see
if
they
would
want
to
participate
in
it,
but
yeah
and
they
wanted
to.
But
in
the
end
we
didn't
add
a
note
for
them
in
this
proof
of
concept,
because
this
would
lead
us
to
far
so.
A
This
is
what
we
wanted
to
create,
but
it
was
a
bit
difficult
at
the
time,
because
we
also
wanted
to
do
this
on
multiple
physical
machines,
because
we
wanted
to
learn
from
it
and
to
give
good
information
to
the
client
to
see
how
they
could
take
this
to
a
production
system.
So
it
was
quite
complex
because
we
didn't
find
any
examples
a
year
ago
about
how
to
set
this
up
on
multiple
physical
machines
or
even
on
on
Amazon
PPC,
with
multiple
machines.
A
In
there
everything
was
running
on
one
node,
so
we
thought
it
would
take
a
week
and
in
the
end
it
was
like
three
or
four
weeks
that
it
took
so,
but
we
got
it
working
on
Amazon,
virtual
private
clouds.
Every
instance
was
docker
eyes,
so
we
also
devised
our
application,
and
then
we
use
the
dock
relay
overnight
overlay
networks
to
connect
the
containers
together
and
that
works
when
it's
running
on
one
machine,
but
because
it
was
on
multiple
machines.
A
They
couldn't
find
each
other
and
that's
why
we
used
console
at
a
time
to
share
the
settings
of
the
dock
relay
over
net
button
overlay
Network.
So
if
one
instance
spins
up
the
console
in
console
instance,
we'll
make
sure
that
the
settings
are
shared
within
the
cluster,
the
console
cluster
that
was
created.
A
A
A
But
we
wanted
to
keep
their
certificate
structure
because
it
it
was.
It
was
a
good
structure.
Yet
the
thing
with
the
citizen
certificates
who
only
has
user
certificates,
and
then
you
are
the
second
branch
where
you
have
all
the
service
certificates,
where
you
can
create
a
chain
of
trust
with
each
department
having
their
intermediate
certificate
that
could
create
certificates
for
all
their
services.
A
A
You
know
there
are
also
script
things
in
there
to
update
Django
to
generate
new
user
certificates,
so
it
really
is
a
replacement
of
the
fabric
CA
as
well,
then
developing
the
chain
codes
not
going
to
go
into
too
much
detail,
because
all
the
chain
code
is
also
available
online.
I'm
just
going
to
talk,
you
talk
about
a
few
concepts.
A
We
try
to
integrate,
we're
not
sure,
because
if
it's
yeah
the
right
thing
to
do
it
that
way,
because
we
were
learning
I-
are
set
by
ourselves
at
the
time,
but
we
find
it
quite
that
it
we
found
out
that
it
worked
good.
So
first
thing
was
separation
of
concerns,
so
we
created
19
codes
each
with
their
own
responsibility
Shango.
It's
also
good
to
talk
to
other
chain
codes.
A
This
way
there
are
more
maintainable
and
yeah
a
lot
smaller
and
a
lot
smaller
means
it's
more
islands
easier
to
maintain,
also
because
they
were
saying
that
they
wanted
to
create
generic
components.
So
in
here
there
are
a
lot
of
things
that
they
could
reuse
in
other
projects
as
well
like
access
management
and
identity
management.
I.
Think
almost
everything
is
quite
generic.
Only
the
nature
management
plan
contours
is
a
lot
of
business
logic
of
a
and
B
in
there
yeah.
A
A
Second
thing
we
implemented
was
privacy
through
channels,
so
at
the
moment
the
private
data
collections
weren't
available.
Yet
so
yeah
we
had
to
do
it
with
the
channels.
Grb
was
the
only
one
that
could
know
the
ownership
of
a
certain
piece
of
land
and
yeah.
So
we
wanted
to
keep
that
data
private
with
a
GRB,
so
we
created
two
channel
a
public
and
a
private
channel
and
a
GRB.
No,
it
was
used
as
a
bridge
between
the
private
channel
and
the
public
channel
cross
channel.
Writing
was
possible
at
at
the
moment.
No
cross
channel.
A
Writing
was
not
possible.
Cross
channel
reading
was
possible,
I'm,
not
sure
if
cross
channel
channel.
Writing
is
possible
at
right
now,
but
that's
had
a
few
wishes.
So
we
had
a
few
issues
with
that.
So
how
did
this
work?
So?
A
user
could
ask
on
the
public
channel
I
want
to
request
approval
of
the
owner
of
that
ground.
Contour.
Then,
when
an
owner
logs
into
the
system,
we
did
a
request
to
the
private
channel
to
see.
If
there
are
any
requests
open,
the
private
channel
could
communicate
with
the
public
channel
to
get
a
request.
A
They
get
back
to
the
owner
and
the
owner
approves
or
a
checks
on
the
private
channel
and
then
because
we
couldn't
do
cross
channel
writing.
Another
event
was
posted
and
a
GRB
note
was
used
as
a
bridge,
so
they
were
listening
to
the
events
and
then
they
just
updated
the
public
channel.
If
all
the
data
was
there
and
that
way
we
did
the
whole
privacy
of
data.
A
We
also
worked
with
child
tier
data,
which
also
involves
there
are
a
lot
of
complex
algorithms.
You
have
specific
databases
for
that
as
well,
and
those
weren't
supported
by
high
polish
fabric.
We
only
possibilities
that
we
had
was
level
DB
NKOTB,
also
because
we
wanted
to
do
as
much
as
possible
on
chain.
We
had
to
do
it
with
those
MongoDB
as
limited
support
of
geospatial
as
limited
geospatial
support,
but
that
wasn't
available
at
the
time
and
I
don't
think
it's.
A
There
was
a
ticket
open
to
him
doing
integrated,
but
I
don't
think
it's
integrated
yet
so
so
we
looked
at
other
possibilities
and
then
we
were
thinking
about
setting
up
an
Oracle
and
do
off
chain
process,
which
might
be
a
good
idea.
But
we
wanted
to
do
as
much
on
chain
as
possible
so
and
then
geospatial
blockchain
we
looked
at.
A
Can
we
can
we
switch
the
level
DB
or
the
couchdb
for
the
contours
chain
code
with
another
database
like
PostGIS,
with
with
solitaire
just
two
interfaces
that
you
needed
to
implement,
but
they
were
quite
complex,
so
it
was
just
a
proof-of-concept.
We
skipped
that
so
what
we
did
in
the
end
was
just
use
LGB
and
then
we
we
index
the
bounding
boxes
of
a
contour
so
that
we
could
do
intersection
with
the
bounding
boxes
and
then
in
the
inner
chain
code
itself.
A
We
use
their
chairs
to
remove
the
false
positives
that
works
for
a
proof
concept,
but
and
it
wouldn't
be
feasible
for
a
larger
data
set.
So
yeah.
That's
why
we
also
proposed
your
twist
to
solutions
to
the
client.
Then
we
also
have
the
data
with
the
geo
data
is
also
quite
complex.
There
are
large
data
sets
that
we
had
to
handle
with
a
lot
of
metadata.
We
use
geo
jason
because
we
could
just
store
it
in
CouchDB
and
we
could
query
on
it,
but
also
there.
A
A
Then
for
the
identity,
as
I
said
earlier,
we
did
into
a
connection
with
a
Belgian
a
ID,
but
we
used.
We,
we
want
to
integrate
with
the
systems
they
had.
They
had
an
identity
and
access
management
system,
so
we
used
those
systems
and
we
made
an
integration
with
those
systems,
because
then
they
could
have
used
those
chain
codes
that
we
Friedan.
For
that
also
in
other
projects
it
was,
we
looked
at
it
as
more
like
a
generic
building
block
that
they
could
reuse
inside
Identity
and
Access
Management
inside
our
system.
A
There
is
an
ID
for
a
user
which,
which
is
only
known
internally,
and
we
you
that
ID
on
the
blockchain
so
that
we
don't
and
we
don't
store
any
more
private
data.
So
we
hope
that
we
don't
have
too
much
problems
with
gdpr.
That
way,
we
also
looked
at
how
we
could
store
the
keys
at
the
beginning.
We
were
thinking
about.
We
want
a
user
to
store
their
own
keys,
but
yeah.
That
would
be
very
difficult,
not
from
a
user
experience
perspective.
So
we
also
looked
at
how
we
could
its
centralized
way
through
an
HSM.
A
So
we
looked
at
two
possibilities:
we
looked
at
how
they
could
work
and
we
made
our
chain
go
that
way
that
they
could
work
with
into
in
the
two
situations
so
that
they
could
take
it
further
if
they
wanted
to.
We
made
it
so
that
an
idea
that
the
user
in
the
in
blockchain
in
this
insider
chain
code
has
a
link
with
multiple
device
ID.
So
it
would
be
possible
that
he
has
multiple
devices
linked
to
his
account.
A
A
There
are
a
lot
of
things
you
need
to
do
there,
so
we
had
a
lot
of
code
application
because
we
also
had
a
19
code
so
by
combining
them
in
in
these
utility
tools,
we
could
reuse
them
easily,
also
based
contract
with
which
has
a
basic
implementation
of
invoke,
and
in
it,
so
that
your
chain
code
contract
only
has
to
implement
the
functions
itself.
I
think
this
moral
has
the
same
thing.
That's
one
point
for
we'll
go
to
so.
A
It
also
takes
a
lot
of
time,
so
we
also
created
tool
for
that
where
you
just
have
a
menu
below
that
you
can
choose
which
chain
go
to
update,
and
even
to
that
there
is
a
possibilities
to
say
just
watch
my
chain
code.
If
I
change,
something
it
will
update
my
chain,
go
it
immediately.
It's
better
the
development
process
a
lot,
so
this
is
here
just
spinning
up
the
network,
where
we
also
have
an
advanced
configuration
object
for
in
JavaScript,
because
the
simple
network
doesn't
have
the
two
channels
in
there.
A
The
only
thing
I'm
going
to
tell
here
is
that
yeah.
We
also
created
tools
for
that,
because
there
was
a
lot
of
boiler,
boilerplate
code
to
invoke
and
query
chain
codes.
So
we
try
to
wrap
the
fabric
client
inside
an
order
tool
with
an
higher
level
functions
for
querying
and
invoking
chain
code,
and
also
for
listening
to
events.
There's
also
base
herbs
in
there
where
you
can
easily
extend
and
just
implement
the
functions
that
are
provided
by
by
the
chain
code.
You
want
to
service
so.
A
In
conclusions
yeah
for
us,
it
was
new
at
the
time
there
weren't
a
lot
of
things
available.
So
we
try
to
look
to
different
things
and
try
to
combine
them,
and
we
think
it's
very.
If
everybody
should
collaborate
and
just
open-source
their
things,
it
could
only
make
make
the
blockchain
community
stronger
and
especially
hyper,
lighter
fabric.
So
we
also
like
it
that
the
Flemish
government
open
sourced
the
total
project.
So
we
really
appreciate
it.
A
We
create
because
we
another
issue
we
had
was
we
needed
to
do
something
with
the
oaken's
and
we
couldn't
find
a
good
example
of
the
ogin.
So
to
test
our
tools,
we
created
a
token
example
with
a
with
with
the
things
we
did
inside
the
project
and
we
also
open
source
that
as
well.
So
you
can
look,
take
a
look
at
our
tools.
A
We
created
with
that
projects,
and
other
thing
I
wanted
to
say
is
that
we
think
it's
not
good
to
just
push
blockchain
into
a
corner,
because
we
were
vertical
with
the
client
they
just
they
through
their
own
technical
architecture
and
put
a
blockchain
somewhere
below.
But
if
you
try
to
understand
the
technology,
look
at
all
the
components,
I
think
it
can
be
become
part
of
your
technical
architecture
instead
of
just
one
thing:
willow
like
a
regular
database.
A
Also,
it's
good
to
to
bring
all
to
think
with
all
the
components
and
like
hyper
logic,
fabric
has
a
more
modular
structure,
it's
good
to
think
with
them,
but
you
also
need
to
watch
out
to
not
bring
too
much
complexity
to
the
end-user,
because
but
enough
complexity,
so
that
they
trust
the
system
so,
and
that
was
it.
Thank
you.
A
It
was
actually
yeah.
We
had
one
chain
code
that
manages
the
token.
We
know
that
right
now,
hypoplasia
fabric
is
also
creating
a
fab
going
or
they're
busy
with
that,
but
we
didn't
use
that
at
a
time.
It's
just
chain
code,
where
you
have
different
wallets
linked
to
the
public
key
of
a
user.
It's
it's
just
in
one
chain
code
that
we
have
written
it
down.
So
it
was
just
a
number
that
we
stored
with
the
user.
We
also
had
an
possibilities
to
create
a
chain
code
wallet.
A
So
then
there
the
thing
is
that
and
that
wallet
can
only
be
changed
from
within
another
chain
code.
So
whenever
a
token
should
move
from
from
that
wallet,
we
would.
She
would
see
that
the
request
was
coming
from
another
chain
code,
and
that
way
we
created
the
wallets
for
the
ground
contours,
because
only
the
ground
contour
chain
code
could
manage
those
wallets.