►
Description
Data is the new oil, and as with any valuable market, it is becoming very tightly regulated for all companies. Part of that regulation in Europe is GDPR which ensures the storage and retrieval of data is 100% irrefutable.
In this webinar Jani Partanen, CTO, of Hyperledger member Joisto will share first hand how they have implemented a production GDPR Compliant Storage offering with Hyperledger Fabric. Jani, with his team, will share their journey both business and technical and how document storage with blockchain-based integrity is set to increase data security and mitigate the pitfalls of privacy legislation. He will also explore how this will affect companies globally not just in Europe. Not to be missed.
Topics – with interactive sessions
What are GDPR requirements for document storage?
Scope of GDPR
Document disposal
Individual Rights
Proper security and practices
Why Blockchain for Document Storage integrity?
Blockchain as proof of integrity
Conflict between blockchain and GDPR
High volume vs high value
The Joist technical and business journey with lessons learnt
Business justification
Why Hyperledger Fabric
The Architecture and implementation
Lessons learnt
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
B
B
C
B
A
B
B
B
B
A
A
B
Okay,
I
think
I'm
going
to
kick
off.
Okay,
welcome
everybody
to
this
hyperledger
member
webinar.
We
have
a
great
webinar
today,
I'm
very
glad
that
we
have
our
our
hyperledger
member,
joist
or
joist.
I
think,
if
I
correct
it
might
pronounce
it
correctly
and
we
are
going
to
talk
about
gdpr
storage
with
hyperledger
fabric
compliant
gdpr
compliant
storage.
B
So
this
is
a
very
exciting
subject:
we're
going
to
be
looking
at
gdpr
itself,
how
it
that
relates
to
blockchain
and
then
about
the
story
that
joyce
had
gone
through
and
providing
this
a
great
production
system
that
they
have
today,
so
what
I'm
gonna
do
and
and
by
the
way
before
I
start,
please
go
to
raise
your
hand
or
press.
This
is
interactive
session.
So
please
do
raise
your
hand,
put
some
questions
in
the
q,
a
as
we
go
along
we'll,
try
and
answer
those.
B
A
Okay,
thank
you
julian.
So
my
name
is
yani
partanen,
I'm
the
cto
of
yoast
group
and
I
have
been
around
since
the
founding
of
the
company.
I
am
an
employee
number
one
in
the
company
and
kind
of
minor
shareholder
also
and
with
me
today:
tommy
henningen,
janie,
linton
and
jeffrey
williams.
Tommy.
If
you
want
to
introduce
yourself
a
little
bit.
C
B
C
Sure
yeah,
my
name
is
janie
linton
and
in
in
short,
I've
been
working
in
in
choice
since
2012,
so
nearing
10
years
in
this
company
and
yeah.
That's
that's
very
short
kind
of
introduction,
hi
jeffrey
williams.
Here
I
am
I'm
the
new
joiny
I've
been
there
for,
like
five
years
now
and
yeah,
I'm
a
senior
developer
and
work
on
the
technology
side
of
things.
A
A
Hopefully,
you're
able
to
see
kind
of
the
color
page
of
this,
so
the
subject
of
this
session
is
gdpr
compliance,
storage
with
hyperledger
fabric,
and
I
mean
part
of
the
cto.
As
I
mentioned,
a
couple
of
words
about
the
company
that
we
come
from.
Joystock
is
a
finnish
company.
We
have
offices
also
in
uk
and
poland
we
have
been
around
since
the
beginning
of
2000s.
A
Our
product
is
document,
storage
and
archival
system.
We
specialize
in
high
volume,
multi-tenant
document
storage
that
used
around
europe,
mainly
in
europe,
for
utilities,
finances
banking
and
such
basically.
We
have
a
platform
for
service
provider
to
provide
document,
storage
and
archiving
services
as
a
service,
so
compared
to
document
management
systems,
you
that
can
do
something
like
tens
of
thousands
or
hundreds
of
thousands
documents.
We
do
hundreds
of
millions
of
documents
or
billions
of
documents,
so
that
is
a
definite
difference
in
scale
there.
A
So
we
have
a
very
particular
niche
that
we
are
actually
looking
into
expanding
and
what
we
learned
here
is
part
of
that
expanding
project
going
on
okay.
Here
we
have
the
kind
of
session
outline
that
what
I'm
going
to
go
through.
We
have
first
I'm
going
to
kind
of
do
a
quick
recap
of
gdpr.
I
know
that
the
most
everybody
knows
something
about
gdpr,
I'm
probably
go.
A
A
How
does
gdpr
kind
of
what
you
gdpr
has
about
blockchain?
What
the
eu
has
about
blockchain
and
gdpr
compatibility
and
then
we're
going
to
have
an
technical
and
business
journey?
What
we
learned,
how
we
did
it?
Why
we
did
it
and
all
that
stuff,
then,
in
the
end,
we
have
questions
and
answers.
However,
if
you
have
any
questions
feel
free
to
ask
them
along
the
way.
I
believe
julian
is
going
to
kind
of
monitor
the
questions
and
and
manage
that
side
of
things.
A
A
A
Okay,
here
we
have
a
couple
of
basic
facts
about
gdpr.
First
of
all,
it
stands
for
general
data
protects
and
regulation,
it's
applicable
as
of
may
25th
2018..
So
it's
been
around
about
three
years
and
the
initial
panic
has
passed.
The
gdpr
generally
caused
a
lot
of
havoc
and
a
lot
of
well
panicked
around
the
it
industry
and
stuff
around
that,
it's
more
or
less
now
day-to-day
stuff
that
you
need
to
take
account
the
two
first
gdpr
fines
have
been
given
that's
around.
A
A
A
So
it's
more
about
general
concepts
and
principles
and
stuff
it's
enforced
by
each
member
state,
and
this
brings
a
little
bit
of
complexity
into
it,
because
it's
up
for
interpretation,
so
each
country
can
interpret
it
as
they
see
it.
So
something
that
is
acceptable
in
finland
might
not
be
acceptable
in
germany
and
that's
an
that's
a
little
bit
of
a
complication,
but
for
that
actually
eu
has
an
european
data
protection
board,
providing
guidelines
and
recommendations
for
that,
and
I
have
listed
a
couple
of
key
terms
on
the
bottom
of
that
slide,
which
are
data.
A
Subject:
data
processor
and
data
controller
I
go
quickly
to
root
these,
so
data
subject
is
subject
of
the
data
storage,
so
that's
the
person
that
you're,
whose
data
you
or
companies
are
storing
for
data
processor
is
something
that
is
handling
or
processing.
The
data
and
data
controller
is
the
one
that
kind
of
owns
the
data
and
is
responsible
for
that.
So
the
processor
controller
distinction
is
a
kind
of
important
one
in
gdpr
and
then,
if
we
discuss
a
little
bit
about
the
scope
at
heart,
it's
about
personal
data.
A
That's
that's
that's
what
it
is
all
about
and
on
the
right
hand,
side
there.
You
can
see
how
information
commissioner's
office
in
uk
defines
the
personal
data
and
it's
quite
wide
quite
wide
definition,
so
anything
like
ip
addresses
or
cookie
ids
or
all
all
that
kind
of
stuff
can
be
thought
as
some
personal
data.
A
So
it's
a
very
wide
area,
also
there's
a
facial
recognition
and
all
this
kind
of
stuff
is
considered
in
some
cases
to
be
personal
data.
If
you're,
not
storing
personal
data
at
all,
gdpr
does
not
apply.
So
that's
that's
simple.
Your
life
is
going
to
be
easy
and
and
so
on,
but
typically
businesses
do
store
at
least
some
level
of
personal
data
and
again
it's
technology
agnostic.
So
it
doesn't
matter.
What's
the
media
of
the
storage
that
you
are
using?
A
If
you
are
storing
papers,
they
also
are
applicable
for
jdpr,
so
so
it
just
makes
things
more
complicated
or
microfilm
for
or
or
anything
what
you're
storing
doesn't
matter.
You
still
need
to
comply
with
gdpr
and
the
territorial
scope
is
eu.
So
basically,
this
is
eu
legislation
and
set
up
by
eu
commission
and
so
on,
but
it
affects
the
rest
of
the
world
when
the
businesses
around
the
world
are
processing
or
handling
personal
data
of
your
eu
citizens.
So
it
has
this
kind
of
a
viral
nature
to
it
all
right.
A
Let's
have
a
quick
glance
at
the
main
areas
of
gdpr.
Of
course,
this
is
just
one
one
way
of
looking
stuff
and
and
gdpr
is
and
quite
complicated
legislation,
and
you
it's
up
for
your.
It
depends
on
your
point
of
view,
but
these
are
five
points
that
I
kind
of
like
to
point
out
that
there
is
one
aspect
of
gdpr
security
of
processing
businesses,
handling
personal
data
are
required
to
do
it
in
a
secret,
secure
manner
and
and
they
need
to
follow
best
practices
and
that
kind
of
stuff.
A
Then
businesses
need
to
act
lawfully
lawfully
and
have
a
consent.
Constant
means
that
they
need
to
have
permission
to
start
data
and
they
need
to
do
it
in
lawful
way,
accountability
and
compliance.
That's
a
that's
a
actually
quite
big
subject
that
this
session
is
not
going
to
going
to
touch
that
much,
but
accountability
needs
means
that
you,
you
need
to
comply,
and
you
need
to
prove
that
one.
You
need
to
prove
that
you
have
done
done
your
business
in
compliance
to
gdpr,
then
there's
data
protection.
A
A
A
A
A
That's
an
simple
one!
If
the
data
is
incorrect,
somebody
may
demand
that
you
correct
it
and
you
might
need
to
do
it
the
right
to
eraser.
This
is
also
called
the
right
to
be
forgotten
by
the
eu.
So
this
means
that
if
an
user
demands
that
the
data
needs
to
be
deleted,
you
may
be
required
to
do
so.
This
is
an
subjective
right
and
it
doesn't
apply
automatically,
so
they
need
to
be
need
to
be
certain
certain
situations
that
are
going
on.
Then
you
have
the
right
to
restrict
processing.
A
This
is
probably
the
most
complicated
one.
What
this
means,
and
but,
however,
it's
probably
one
of
the
least
used
ones,
so
the
right
to
restrict
processing
is
that
the
person
may
demand
that
you
can't
not
modify
or
lose.
The
data
that
you
are
holding
about
them
where
this
comes
up
is,
could
be
something
like
a
legal
dispute
that
you
are
required
that
you
do
not
lose
the
evidence
that
you
have
and
that's
one
of
the
basic
individual
rights
that
there
are.
This
is
very
subjective.
It
doesn't
apply
automatically.
A
Somebody
just
can't
just
go
on
and
go
on
and
fire
away
the
right
to
restrict
processing,
requests
around
the
world
and
expect
that
everything
is
then
restricted
that
doesn't
happen.
Then
you
have
the
right
to
data
portability.
This
means
that
when
you
provide
data,
you
need
to
provide
it
in
a
sensible
form,
that's
pretty
much
it!
A
Then
you
have
the
right
to
object.
This
means
that
you
can
deny
direct
marketing
and
such
communications
at
all
in
all
in
all,
then
there's
rights
related
to
automated
decision
making
and
profiling,
first
of
all,
beautiful
name
for
the
right,
but
that
kind
of
describes
this.
The
persons
may
demand
that
now
this
none
of
this
can
be
done
to
that
date.
A
I
pointed
out
data
retention
here
because,
from
our
point
of
view,
that's
an
hugely
important
subject
and
data
retention
means
that
you
should
not
store
any
data
unless
it's
necessary
and
whatever.
That
means.
That's
that's
up
for
up
for
court
cases,
then,
but
nevertheless,
that's
the
basic
principle
that
the
eu
is
taking
with
gdpr
legislation
and
when
we
say
data
here,
that's
of
course
personal
data.
A
If
you
have
some
statistics
about
wind,
that's,
that's
not
that
doesn't
apply
okay,
so
basically
all
data
containing
personally
identifiable
information
and
it's
no
longer
necessary-
needs
to
be
removed,
and
you
have
to
have
practices
to
do
this
and
if
you
have
done
your
kind
of
document
storage
on
paper,
this
is
going
to
be
a
pain.
This
is
really
going
to
be
a
pain,
of
course,
depending
on
the
archival
system.
If
you,
if
you
have
sorted
them
by
date,
then
just
throw
the
old
boxes
away,
then
the
other
last
laws
come
in
at
this
stage.
A
So
the
other
laws
typically
go
over
gdpr
in
this
area.
I
am
not
a
lawyer.
I
am
a
techie.
This
is
something
that
you.
If
you
really
have
a
problem,
you
need
to
talk
with
lawyers,
so
that's
and
then
later
and
then
in
data
retention.
You
need
to
be
prepared
for
right
to
eraser,
so
that
you,
if,
if
people,
has
a
valid
right
to
right
to
be
forgotten,
you
need
to
be
prepared
for
that.
A
B
B
A
An
easy
one
yeah:
no,
we
didn't
develop
it
for
the
blockchain
because
because
this
has
existed,
the
actual
product
has
a
lot
existed
since
the
90s
and
blockchain
wasn't
around
in
there.
So
so
blockchain
has
become
an
addition,
not
a
happy
happy
accident.
Actually
it
was
planned,
but
but
believe
it
or
not,
but
nevertheless
it
has
come
as
an
afterthought,
not
an
initial
creation
of
that
system.
A
A
I've
gone
to
that
rabbit,
hole
and
spent
quite
some
time
in
there
and
came
up
still
relatively
sane,
but
there
are
studies
about
blockchain
and
gdpr,
and
I'm
going
to
kind
of
highlight
what
what
the
first,
what
the
eu's
main
findings
were
and
what
are
the
kind
of
so.
First
of
all,
tdpr
assumes
that
the
personal
data
is
controlled
by
one
entity
to
that
data
controller.
If
you
remember
I,
I
referred
to
data
controller
in
the
beginning.
A
A
The
other
kind
of
conflict
is
that
gdpr
requires
all
personal
data
to
be
modifiable
and
erased,
and
we
all
know
blockchain-
hopefully
at
least
something
about
blockchain,
and
we
know
that
blockchain
tries
to
prevent
this
as
much
as
possible.
Blockchain
tries
to
create
do
the
data
immutable,
so
once
you
enter
the
data,
the
track
of
that
data
stays
there
forever.
That's
the
great
feature
about
great
feature
about
blockchain,
but
this
can
cause
server
limitation.
A
Unfortunately,
what
they
kind
of
came
up
with
with
is
that
in
general
cell
dynamization
is
forbidden,
so
they
take
this
at
the
infinitum
aspect,
with
data
that
given
infinite
time,
the
cell
dynamization
should
not
be
unsodomized
and
in
terms
of
computers,
infinite
time
is
a
very
long
time.
Basically,
you
can
crack
anything
if
you
have
infinite
time.
Of
course.
A
In
reality,
none
of
us
have
at
least
haven't
had
since,
but
that's
definitely
an
kind
of
an
limiting
factor
using
blockchains
and
gdpr,
and
that
needs
to
be
taken
into
account.
Anonymization
anonymization,
then,
however,
is
completely
okay.
If
you
do
proper
anonymization
and
then
there's
the
discussion,
what
is
anonymization
and
severe
dynamisation?
A
I'm
not
going
to
go
into
huge
details
about
that
one,
but
server
dynamicization
in
general
could
be,
for
example,
using
an
hash
to
calculate
if
you
use
a
social
security
number
and
has
that
one
that's
not
going
to
be
acceptable
because
that
can
be
kind
of
brute
forced
back
into
the
social
security
number.
Then
again,
if
you
have
a
book
containing
personal
information,
and
you
calculate
the
hash
of
that
book,
that's
most
probably
is
going
to
be
completely.
Okay,
so
there
is
granularity
in
it.
A
You
store
it
in
some
other
system
and
you
refer
it
in
the
blockchain,
so
you
store
hashes
and
fingerprints
and
all
that
kind
of
stuff
of
the
data
and
the
metadata
into
the
blockchain.
That's
that's.
The
officially
recommended
way
of
eu
well
eu
doesn't
make
a
kind
of
clear
recommendation,
but
that
comes
up
from
the
reports
quite
often,
then
the
other
option,
if
of
course
to
anonymize
your
data,
this
might
be
used
very
good
solution
for
some
use
cases.
A
A
Okay,
what
this
comes
up
and
what's
kind
of
our
approach
to
this-
is
kind
of
use,
blockchain
as
proof
of
integrity
instead
of
storing
the
swiss
store
documents
in
the
system
and
vista
document
pathway
needs
to
be
in
this
context
needs
to
be
taken.
Kind
of
widely
document
can
be
anything
it's
basically
anything
that
can
be
a
file,
for
example,
or
multiple
files,
or
something
like
that
can
be
considered
as
a
document.
A
A
This
actually
allows
allows
the
blockchain
to
track
the
contents
of
the
archive
and
the
whole
document
storage
system,
so
so
that
one
can
be
tracked
and
and
prove
the
integrity
of
the
system
and
and
that's
an
kind
of
excellent
excellent
feature
of
blockchain.
If
we
take
an
example
which
is
right
to
restrict
processing,
which
I
one
of
the
individual
rights
in
the
gdpr,
what
blockchain
can
do
for
you
in
this
rather
weird
requirement
that
you
are
not
not
allowed
to
do
anything
with
your
data?
A
What
blockchain
can
do
is
actually
it
can
prove
that
if
all
the
transactions
and
modifications
are
tracked
in
the
blockchain,
you
can
easily
show
what
transactions
have
been
applied
against
this
object
and-
and
what
has
happened
to
this
since
some
particular
point
in
time?
Actually
since
the
since
the
starting
of
the
object,
but
nevertheless
for
right
to
restrict
processing,
it's
the
one
particular
point
in
time
that
can
be
seen
there.
That's
a
perfectly
kind
of
perfect
example.
How
blockchain
can.
A
What
actually
this
approach?
The
approach
to
using
blockchain
does
is
that
as
eu
identified,
multiple
data
controllers
to
be
the
problem,
this
actually
doesn't
change
in
this
model.
The
data
controller
is
still
responsible
for
controlling
the
data,
and
the
data
processor
is
the
one
storing
the
proof
of
the
data.
So
this
really
simplifies
the
scenario.
What
kind
of
what
applies
to
gdpr
and
that's
an
excellent
result,
a
result,
because
simplification
in
in
gdpr
isn't
well,
it's
always
nice.
B
I
think
I
think
we
can
go
straight
ahead.
We've
got
a
lot
of.
I've
got
some
questions
coming
in
right.
One
thing
people
asked
and
we'll
send
you
the
link
everyone's
asking
what
this
eu
report
and
where
they
can
get
it
eu
report,
gdpr
and
and-
and
I
think
we
should
there's
a
couple
of
links
and
thank
you
for
everyone,
who's
sharing
that
I
think
I
think
we
can
continue.
Jeffrey
is
doing
a
great
job
of
answering
some
of
these
questions
as
we
go
along.
B
A
Yeah
exactly
so,
and
the
answer
that
we
have
come
up
with
is
definitely
the
offset
exchange
storage,
so
the
actual
data
is
not
stored
in
the
blockchain.
So
if,
if
we
do
not
store
anything
anything
containing
personally
identifiable
information
in
the
blockchain,
then
we
don't
basically
need
to
worry
about
the
contents
of
the
blockchain,
because
gdpr
doesn't
apply
in
there.
That's
the
kind
of
separation
of
concerns
that
we
are
creating
there
gdpr
doesn't
apply
at
all
in
the
blockchain,
because
we
are
not
storing
anything
that
is
personally
identifiable.
B
A
Completely
understand
that
one,
but
let's
say
I
have
what
I
can
say
about
this-
is
that
what
I've
understood
is
that,
for
example,
using
the
private
key,
this
private
key
to
encrypt
stuff
in
the
blockchain,
and
then
you
have
public
key
available
and
kind
of
trusting.
The
private
key
is
considered
from
eu's
point
of
view
considered
to
be
pseudonymization.
A
B
That's
not
eager,
if,
if
you
want
more
to
ask
again-
and
we
can
get
more
clarification
on
that,
but
I
think
that
that
was
good
and
then
the
second
one
is
from
a
new
pam
and
he
says
doing
anonymization
of
data
or
coordinating
offline
storage
still
makes
out
a
way
to
circumnavigate
the
gdpr
close
of
right
to
raise
your
because,
though
unlinked
it
is
still
stored,
hashes
and
check
sums
being
stored
on
blockchain
means
at
a
later
date.
Someone
would
need
to
validate
it
by
checking
the
original
data
or,
if
not,
how
yeah.
A
Yeah
yeah,
that's
the
case.
If
you
get
the
original
data,
then
you're
kind
of
that's
the
key
to
kind
of
everything
the
contents
of
the
blockchain
is
not
the
key
to
anything.
You
can
take
a
look
at
the
blockchain
and
you
can
never
build
back.
What's
the
actual
data
is
given
at
infinitum.
I
believe
that
is
the
case.
So.
B
A
Sure
all
right,
what
I'm
going
to
go
through
is
kind
of
the
architecture
and
implementation.
This
is
the
technological
side
of
things,
but
I'm
not
going
to
go
too
techy
in
there
unless
somebody
wants
to.
I
am
taking
back
so
I
can
go,
but
I
don't
think
that's
serves
a
purpose
here.
So
the
architectural
implementation,
as
I
said,
we
use
the
storage
integrity
by
the
blockchain
so
often
stay
change,
storage,
and
this
brings
in
the
benefits
that
I
was
talking
about
a
couple
of
slides
ago.
A
That
you
need
to
this
is
separates
the
controller
and
processor
and
we
don't
need
gdpr
doesn't
apply
into
the
blockchain
itself
as
it
doesn't
store
anything.
That's
the
main
approach
that
we
did
and
it's
a
conservative
choice.
It's
definitely
a
conservative
choice,
and-
and
here
we
are
not
challenging
au
or
gdpr,
and
but
we
are
taking
the
kind
of
the
most
compliant
approach,
the
the
gdpr
there,
then,
what
we
have
done
is
we
have
created
a
hybrid
blockchain.
A
Instead
of
I
don't
know.
Typically,
we
categorize
blockchains
in
two
main
categories,
which
one
is
private
and
permission,
and
one
is
public.
This
is,
of
course,
or
oversimplification
of
stuff,
but
for
the
sake
of
sake
of
argument,
that's
that's
one
way
of
separating
them.
What
we
have
actually
created
is
a
hybrid
blockchain
using
actually
hybrid
fabrics
features
there.
The
hybrid
blockchain,
in
from
our
point
of
view,
means
that
actual
data
processing,
transaction
transaction
handling
within
the
blockchains
are
happening
in
private
and
permissioned
environment.
A
A
A
A
How
trustworthy
you
consider
me
to
be
my
blockchain
on
my
laptop
is
is
as
equally
trustworthy,
trustworthy
and
then
there
is
the
issue
of
data
distribution.
If
I
run
it
only
on
my
laptop,
it's
it's
relatively
not
distributed
at
all.
So
what
we
came
up
is
what
we
call
institutional
members.
We
have
built
a
network.
A
A
Nearly
any
company
is
up
for
sale
if
the
price
is
right,
and
so
the
there's
always
the
possibility
that
the
data
ends
up
in
in
in
some
kind
of
a
malicious
hands
or
something
of
that
similar.
Then
universities,
then
do
not
have
seem
to
have
this
problem.
I
haven't
heard.
I
I
believe
that
it's
possible
that
the
university
might
be
both,
but
at
least
that's
going
to
cause
some
noise
and
somebody
is
going
to
notice
when
you're
near
university
has
been
sold
to
somebody
and
the
owners.
A
A
A
So,
from
my
point
of
view,
we
have
more
or
less
managed
to
kind
of
bring
additional
trust
in
the
private
blockchains
without
getting
the
problems
of
public
public
blockchains
and
what
we
have
then
have
suma
sumarum.
We
have
publicly
verifiable
in
the
critic
with
gdpr
compliance,
so
that's
the
method
of
hybrid
blockchain
or
that's
the
benefit
of
hybrid
blockchain
that
we
come
up
with.
There
are
a
lot
of
hyperledger
fabric,
specific
features
that
we
utilize
there
and
it.
A
It
has
kind
of
been
a
driver,
a
lot
of
lot
of
innovation
in
in
our
company,
and
it
has
brought
a
lot
of
smaller
features
in
there.
But
this
is
the
kind
of
high
level
view
what
we
actually
have
done
there
all
right.
That's
about
the
architecture
I,
as
I'm
a
techie
I
can.
I
can
go
as
deep
as
deep
as
we
want,
but
that
time
is
limited,
I'm
not
going
to
proudly
present
what
I
have
come
up
with
and
with
my
colleagues,
but
that's
the
kind
of
general
idea
of
that
one.
B
A
C
C
We
have
coming
to
conclusion
that
there
is
kind
of
new
things
happening
and
new
demands
coming
up
where
blockchain
enabled
archive
can
add
value,
especially
under
these
three
main
categories
here
and
and
and
that's
our
kind
of
of
viewpoints.
So
we
we
have
developed
a
solution
which
gives
and
adds
additional
value
for
many
of
these
service
providers.
C
We
serve,
who
use
our
system
then
to
storage,
business,
critical
data
from
from
companies
and
organizations
operating
in
many
industries.
Of
course
everything
shouldn't
go
to
blockchain
very
under
blockchain
verification,
but
there
are
most
of
businesses.
An
organization
has
some
extremely
critical
sensitive
data.
They
want
to
kind
of
off
yeah,
I'm
a
salesperson,
so
I
use
a
kind
of
additional
insurance
on
top
of
everything
to
get
this
irrefutable
integrity
for
the
data,
and
that's
that's
the
kind
of
use
case
and
viewpoint.
C
We
have,
of
course
this
is
a
new
new
area.
We
are
pioneers
here
in
in
a
way,
so
it's
also
learning
together
with
our
customers
and
their
end,
customers,
where
this
solution
can
really
add
most
value.
So
at
the
moment
it
looks
very
much,
for
example,
in
insurance
industry
is,
is,
and
seems
to
be
extremely
interesting
about
this
solution.
C
A
If
we
go
kind
of
to
the
high
volume,
slash
high
value
point
on
there,
what
we
from
what
tommy
there
kind
of
describe
is,
is
what
kind
of
the
our
customers
are
expecting
from
us.
That's
that's
what
they
are
expecting,
what
they
are
kind
of
habit
see
us
do,
and
the
high
volume
slash
high
value
is
kind
of
an
point.
From
our
point
of
view,
why
what's
good
in
this?
For
us
of
course,
happy
customers
are
always
good
for
us.
A
That's
definitely
the
case,
but
what
we
are
doing
here
by
bringing
new
this
irrefutable
integrity
in
the
archive.
What
we
are
kind
of
moving
is
that
we
typically
have
been
high
volume
business.
We
have
been
storing
up
as
well.
I've
said
hundreds
of
millions,
millions
of
documents
per
installation
and
stuff
like
that.
What
we
are
now
bringing
in
that
we
are
bringing
the
kind
of
moving
into
the
more
high
value
document
really
important
stuff.
That
needs
to
be
proven
to
be
there's.
No.
A
C
The
the
one
one
key
challenge
is
that
there
is
always
human
human
acting
as
an
administration,
a
person
and
that
that
opens
let's
say
some
most
of
time
very
small
challenges
or
or
problems.
But
with
this
this
methodology
we
are
bringing
to
the
market
you
can
kind
of,
if
I
say
kindly,
remove
human
factor
in
a
way
from
the
process
and
and
and
that's
opens
interesting
ideas
for
these
organizations.
C
Or
there
are
many,
these
kind
of
of
areas
which,
which
jani
pointed
out
as
high
value
documents
and,
and
now
what
we
are
working
with
our
customers
and
prospects
is,
is,
is
to
understand
the
balance
and
and
demands
from
from
these,
both
areas
that
which
should
go
to
blockchain
and
which
are
just
fine
to
be
kept.
As
as
of
today,
yeah.
A
Roles
of
controller
and
processor
in
this
model,
this
actually
brings
in
additional
trust
into
the
system
as
whole,
and,
what's,
of
course,
this
difficult
subject
for
service
providers
is
that
this
also
brings
the
aspect
of
that.
The
customer
doesn't
need
to
have
as
much
trust
of
the
service
provider.
They
don't
have
the
kind
of
trust
them
so
completely
and
blindly,
because
they
have
always
methodology
how
to
prove
stuff
independent
of
the
service
provider.
A
A
B
We
have
a
bunch
of
questions
coming
in.
Actually,
okay,
we've
got
about
five
ten
minutes
more,
so
please
do
ask
the
questions
so
who
owns
the
who
owns
and
finances
the
network,
who
picks
the
orderer,
is
user
authentication
done
with
certificates
or
by
next
rest
api?
How
does
the
architecture
scale
be
on
20
nodes?
In
fact,
that's
four
questions
in
one
yeah.
A
Owns
it
works
and
the
other
question
is
yep.
Go
ahead
again,
I
can
think
about
the
network
ownership.
That's
that's
actually
a
really
important
subject
in
in
this
kind
of
well
do
because
the
governance
model
and
the
ownership
of
the
network
actually
is
a
key
key
ingredient
in
the
trust
of
the
system
you
need
to
have
and
what
we
have
created.
We
have
created
an
open
governance
model,
meaning
that
we
have
governance
statement
that
states
and
we
have.
A
We
have
a
formal
procedures
in
that
government
statement
described
what
are
the
responsibilities
and
and
rights
of
each
of
the
members
within
the
network.
So
that's
a
kind
of
a
kind
of
a
it's,
a
really
big
question
who
wants
to
and
we
have
tried
to
make
it
as
open
as
possible.
For
example,
all
the
network
covenants
decisions
will
be
kind
of
public
and
all
that
stuff.
So
so
that's
a
great
question.
Yeah.
B
Yeah
thanks
ken
that's
ken,
I
know
in
hong
kong,
hi,
kent,
so
a
great
question
there
and
then
we've
got
one
in
our
chat
here.
A
question
to
understand:
hybrid
blockchain
we've
had
a
lot
of
questions
around
the
concept
and
what
you're
doing
hybrid
con
hybrid
blockchain?
What
is
meant
with
institutional
members?
Is
it
not
common
to
any
hyperledger?
Is
it
is
not
common
to
any
high
political
influence
to
have
multiple
nodes
spread
over
members
in
the
ecosystem?
A
Yeah
it
is,
it
could
be
governmental
members,
it's
it's
neutral
parties,
parties
that
don't
have
interest
in
the
data
as
such.
That's
kind
of
important
distinction
there,
because
the
data
processor
might
have
an
interest
in
the
actual
data
itself
and
might
be
doing
malicious
stuff
and
all
that
kind
of
stuff.
So
what
we
bring
in
is
that
this
could
be.
We
actually
have
a
one
governmental
party
joining
in
joining
in
as
an
institutional
member.
A
B
B
It's
it's.
It's
a
it's
a
it's
a
hyperledger,
a
fabric
thing,
but
we
could.
We
can
leave
that
let's
see
and
trying
to
find
a
specific
one
or
maybe
what
I
can
ask
you,
because
we're
coming
up
to
near
the
end.
What
what
has
been-
and
I
think
it's
been
a
great
talk
right-
we've
covered
gdpr,
gdpr,
blockchain,
how
you
know
what
the
troubles
were.
So
so,
what
would
you
say?
Maybe
tommy
annie
what
have
been
the
the
biggest
challenges
of
making
this
happen.
B
A
If
I,
if
I
start
fund
technology
of
course,
is
is,
is
blockchains
are
not
simple:
by
definition,
they
are
not
simple
systems
to
hand
and
handle,
and
so
so
so
this
there
is
a
definite
learning
curve
there.
However,
in
my
opinion
that
hasn't
been
that's
that's
what
techies
do
we
do
challenging
stuff
and
that's
what
we
live
for,
so
that
hasn't
been
as
much
as
a
problem
as
you
might
guess,
consortium
building
has
definitely
been
these
institutional
members
that
we
are
bringing
in
the
network.
They
have
been
slow.
C
To
this
kind
of
of
later
on
global
network
is,
is
a
quite
unique
opportunity
for
them
as
well
to
research
further
and
and
and
that's
why
it
seems
to
be
the
way
to
go
there,
because
we,
how
we
see
the
this
blockchain
network,
that
we
start
with
our
the
government,
storage
and
archival
system,
but
that's
how
we
have
designed
the
consort
and
governance
the
blockchain
network
this.
This
hybrid
solution
we
have
built,
can
grow
to
wherever
so
so
it
opens
very
interesting
opportunities.
C
So
so,
but
it's
always
when
you
we,
you
are
kind
of
front
runner
or
pioneer.
So
it
takes
time
and
and
like
yanny
said
it's
not
only
technology
which
is
challenging
enough
to
learn
and
kind
of
it's
it's
the
world
around
to
get
people
understand.
Also
in
now
most
of
you
are
techies,
but
but
the
most
of
world
doesn't
know
more
about
blockchain
than
bitcoin.
C
A
C
And,
and
maybe
adding
a
one
one
more
thing
generally
for
everyone
is
also
that
when
we
look
blockchain,
we
we
we
are
fairly
pragmatic
and
try
to
be
realistic.
We
tried
to
see
ways
how
business
world
could
get
great
benefit
out
of
it
and,
like
yani,
explained
that
public
blockchains
has
its
challenges
and
same
with
the
private
ones.
So
this
hybrid
model
we
have
created,
at
least
at
the
moment.
B
Excellent,
so
I
think
I'm
going
to
wrap
now
and
thank
you,
that's
a
I
think.
An
hour
is
probably
not
enough,
so
I
I
think
we've
got
a
lot
of
information
that
out
there
I
seeing
a
lot
of
interest
from
people
actually
just
one
quick
question:
if
people
want
to
get
involved,
can
they
just
contact
you
or
what's?
What's
the
actually?
Yes,
yes,
definitely
I'll
put
the
contacts
down
below,
but
yes,
yeah.
B
And
if
people
want
to
discuss,
I
know
I
see
lots
of
technology.
Of
course
some
people
say
ethereum.
How
do
the
logic
there's
all
kinds
of
other
kind
of
technology?
How
do
we
work
with
many
different
platforms?
Is
that
standard
interoperability
issues
right?
So
all
really
good,
so
I'm
going
to
say
thank
you
to
yanny.
Thank
you
to
tommy,
thank
you
to
other
yanni
and
for
jeffrey
he's,
been
answering
many
of
those
questions
as
we
go
along.