►
From YouTube: Hyperledger Seattle Meetup - June 24, 2019
Description
Enterprise Blockchain: How to Protect Private Data on Chain
Join us as we meet a local startup addressing data privacy and confidentiality with production blockchain implementations.
Presenters & BlockNKey Team
Ali Agha, Co-Founder, Consulting Services and Product Development
Bruce Leader, CEO and Co-Founder
Patrick Townsend, Co-Founder, Security & Compliance
Yuri Vizitei, Co-Founder, Architecture & Strategy
More about this event is at: https://www.meetup.com/Hyperledger-Seattle-Chapter/events/261787428/
----
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 #HyperledgerMeetups #Blockchain
B
A
A
C
A
Am
going
to
so
a
couple
of
things
these
things
to
create
three
three
for
sponsoring
the
space
to
walk
me
he
for
sponsoring
the
event
or
water
and
snacks.
If
folks
are
getting
too
hot,
we
thinner
lower
the
lines
there
so
just
feel
free
to
go
in
and
do
that
and
I
think
that's
all
the
logistics
I'm
gonna
turn
it
over,
and
only
you
can
take
that
III
to
just
share
a
little
bit
about
the
space
and
then.
B
D
A
Hi,
thank
you
for
being
here.
My
name
is
Emily
Kenji
I'm,
the
new
director
of
vertical
development
for
create
33
we've
been
around
about
a
year
and
we
are
essentially
a
Resource
Center
for
technology.
No
flowers
here
at
Northwest
magic,
a
different
tax
than
you
would
normally
find
in
some
of
the
accelerators,
the
incubators,
because
we
don't
take
equity.
A
We
have
a
membership
based
organization
and
our
objective
is
to
create
hub
for
everybody:
that's
working
in
the
technology
space
as
an
entrepreneur,
I'm,
providing
you
with
the
resources
and
access
to
make
you
successful
as
quickly
as
possible.
So
that
includes
this
lovely
space,
which
is
about
22,000
feet
and
with
a
great
view,
and
as
well
as
access
to
capital
and
introductions
of
that
sort
of
access
to
customers
that
can
help.
You
get
your
climate,
your
about
the
ground
and
access
to
peers
who
are
going
through
the
same
slog.
A
You
are,
and
among
other
things
and
then
programming
like
this,
and
so
we
aim
to
continually
evolve
and
expand
that.
So
we
love
to
hear
your
feedback
after
today,
as
much
as
and
for
my
part,
I'm
building
out
our
FinTech
vertical,
which
is
our
first
path
on
the
vertical
development
front.
So
I
come
from
10
years
in
New,
York
and
a
number
of
different
financials
and
then
ultimately,
recently
I
just
hurt
my
own
FinTech,
not
in
the
blockchain
space
and
then
joined
up
with
this
team.
A
Who
is
an
amazing
group
of
former
founders
economic
development
officers
from
the
city?
Folks,
who've
worked
in
startups
themselves
kind
of
bring
all
the
different
perspectives
of
the
startup
experience
to
the
table
that
helped
hopefully
build
something
out.
That's
valuable
to
people,
so
I'm
very
excited
to
have
you
here.
A
If
you
have
any
interest,
we
do
have
two
types
of
memberships:
one
is
a
residential
membership
for
companies,
so
as
your
company
grows
and
evolves,
this
may
be
an
option
for
you
and
the
other
is
a
builder
membership
which
is
available
to
anybody
in
the
entrepreneurial
community
and
we're
always
happy
to
share
a
little
bit
more
about
that.
But
you
can
also
find
details
about
that
on
our
website
in
Crete,
3300.
A
Actually
co-presenting
with
Nerium,
so
we're
looking
a
little
application
in
the
barriers
to
and
a
bold
adoption,
so
it
will
be
and
then
space,
Philippe's,
autonomous,
right
and
I'll
get
that
posted
and
also
provokes
that
stay
to
the
end.
We
have
a
raffle
for
a
high-calorie
t-shirt,
so
please
don't
go
anywhere
and
then
to
turn
this
evenings
programming.
It's
been
really
exciting
to
watch
Bruce
and
the
botany
team.
Over
the
last
few
months,
I
think
person
I
met
at
my
hyper
later
style
meet
up
last
year.
So
it's
very
exciting
and
it's
my
pleasure.
C
My
name
is
Vicki
and
I.
Have
the
pleasure
of
introducing
to
you
the
cofounders
of
block
and
key
I
know
the
meet
some
of
these
folks
at
Microsoft
when
I
was
there
and-
and
they
kind
of
circled
me
in
early
on
so
first
I'd
like
to
introduce
Ali
and
Ali,
has
a
ten
years
of
experience
in
in
the
on
material
space
and
specifically
in
blocking
solutions.
So
he
founded
a
company
called
ellipsis
technologies
and
they
have
created
solutions
for
companies
like
IBM
and
Thomas
Reuters.
So
next
is
a
URI.
Uri
is
a.
E
C
C
Development
and
Yuri
is
a
is
a
blockchain
advocate
on
the
enterprise
in
the
enterprise
rule
and
has
been
working
in
that
for
quite
a
while
and
then
Bruce
is
whether
Bruce
is
the
CEO
of
a
block
and
key
and
Bruce
comes
with
a
lot
of
enterprise
background
from
IBM
user
terminal
manager,
IBM
at
Microsoft,
most
recently,
who
is
the
general
manager
and
senior
director
of
a
department
of
strategic
relations
at
Microsoft.
So
we
got
a
lot
of
different
pieces
to
the
puzzle.
C
One
of
our
local
president
was
able
to
be
here
today
in
his
Patrick's
council
and
maverick,
is
a
security
and
compliance
guru
and
has
written
articles
for
just
about
every
technology
magazine
that
is
around
IBM
systems
magazine
info
security.
He
works
with
MongoDB
and
IBM,
so
we
got
a
lot
of
death
in
all
of
the
different
areas.
F
So
Patrick,
who
was
speaking
at
the
MongoDB
conference
last
week
in
New,
York
and
claims
he
got
a
thought.
That's
why
it's
not
with
us.
So
thank
you
all
for
coming
wonderful
job,
and
it's
it's
just
great.
It's
been
great
for
me
personally
and
I
think
for
a
lot
of
people
in
this
room
to
get
together,
learn
about
what
each
other
is
doing
as
far
as
community
support.
F
F
So
we
already
went
through
the
co-founders
and
so
on
and
so
forth.
We
are
going
to
talk
about
data
privacy
and
we're
going
to
talk
about
data
privacy,
focusing
on
the
enterprise
and
there's
a
couple
reasons
for
that.
One
is
the
fact
that
they're
probably
most
concerned
about
it
and
two.
If
we're
really
going
to
crack
this
and
we
got
a
crack
there,
even
though.
F
F
F
F
So
enterprise
responsibility
can
enterprises
protect
the
sensitive
information
as
they
move
from
centralized
to
decentralized
systems
and
they're
on
their
way
to
do
it
along
the
way
they
have
to
deal
with
things
like
enterprise
confidentiality
supply
chain.
Consortiums
are
big
issues
and
concerns
about
protecting
their
trade
secrets,
as
well
as
their
own.
On.
F
The
other
hand,
many
of
the
industries
around
here,
especially
healthcare,
which
we've
had
a
lot
of
really
good
sessions
here-
are
under
a
lot
of
regulations
from
HIPAA,
but
even
those
organizations
in
hospital
you
know
PCI
is
a
big
deal
there,
financial
institutions,
you
know
big
deal
in
New
York
right
now
with
encryption,
some
mandate,
some
of
you
get
caught
and
you
weren't
encrypting,
it's
a
backdoor
mandate
or
in
trouble.
Okay,
so
you're
running
an
enterprise.
F
We
believe
that
you
shouldn't
be
restricted
by
the
shortfalls
in
the
network
as
to
where
you
put
your
data,
we
think
we
should
be
able
to
encrypt
it
and
protect
it
wherever
you
decide.
Okay,
that's
the
design
point
for
what
we're
doing.
If
you
encrypt
it
right
at
the
application
layer
which
we're
advocating
here
wherever
it
goes,
it's
stored
somewhere
it's
encrypted.
F
If
you
move
it
from
one
node
to
another,
one
participant
to
another,
it's
encrypted,
then
the
big
deal
becomes
how
you
decrypt
it
in
a
distributed
environment,
how
you
decrypt
it
in
a
decentralized
environment,
and
what
do
you
choose
to
put
on
the
chain
or
off
the
chain
and
again
a
lot
of
people
when
they
look
at
the
chain
they're
a
little
worried
about
what
they
put
on
the
chain?
Talk
about
that
one?
Second,
we
don't
think
they
should
be
restricted
by
that.
F
F
So
Gartner
published
this
I
think
last
year.
No
inherent
tools
from
meeting
various
compliance
or
privacy
needs.
Payloads
are
usually
in
plain
text
Accenture
in
2019
by
default,
there's
no
confidentiality
in
blockchain
design,
as
all
the
data
on
chain
is
visible
to
all
participants.
No
there's
good
in
that
right.
I
mean
you
want
to
have
access
to
that
data
for
the
right
person
at
the
right
time
and
participants
on
the
chain,
eliminating
all
the
data
silos
you
know
kind
of
knocking
down
like
inconsistencies,
great
payback.
F
We'll
use
the
food
safety
example
just
because
I
think
people
can
relate
to
that
and
it'll
be
more
on
the
confidentiality
side
that
we're
talking
about
so.
But
what
is?
Okay,
let's
skip
this
line.
Go
back
a
slide
for
a
second
yeah
I'm.
Sorry,
well,
I
missed
the
title
here
watch
as
a
blank
slate,
so
people
look
at
it.
They
try
to
figure
out
what
they
should
put
on
it.
F
So
what
does
that
mean?
Well,
let's
just
take
a
real
dummy
down
example
here:
let's
just
suppose
that
a
batch
identify
er
is
on
a
crate
of
lettuce.
You
know
the
hit
a
store,
let's
say:
Whole
Foods
and
equaling
right.
Well,
if
everybody
enters
where
all
the
principal
is
they
end
up
in
that
store,
and
they
have.
F
It
well
then,
traceability
times
shrink
and
you
know,
as
IBM
and
Walmart
improving
from
you
know,
weeks
to
seconds,
which
is
a
really
good
deal.
It's
a
good
deal
for
all
of
us.
You
can
pinpoint
and
maybe
notify
folks
reduce
the
illnesses
and
outbreaks
may
be
really
specific.
Direct.
You
recall,
concert
women,
you
know
if
you've
read
about
that
way,
I'm
sure
you
all
have
I
mean
you
know
when
there's
an
e
coli,
great
romaine
lettuce,
no
one
eats
romaine
lettuce,
all
the
stores
throughout
all
over
Maine.
Let's
I
mean
it's
huge.
F
This
is
a
great
example.
How
you
can
use
watching
problem
is
candy
valuable
information
required
on
the
chain.
In
order
to
make
this
work,
businesses
can
be
reluctant
to
run
a
plate.
Information
on
the
cheek
I
think
so
there
are
methods
to
deal
with
this.
There
are
there's
access
control.
There
are
things
that
are
being
built
or
be
built
in
lots
of
different
projects
to
do
it
doing
that.
F
F
So,
let's
get
to
the
next
slide.
So
could
we
imagine
in
that
same
scenario,
plaintext,
maybe
but
very
restricted?
What
if
it
went
onto
the
chain
and
you
encrypt
it
again,
a
column
level
or
on
a
record
level?
I,
don't
know
what
the
company
is.
I,
don't
know
the
location
of
the
company
today.
I
might
know
that
stuff
and
people
get
their
hands
on
it.
They
can
pretty
much
decide
or
figure
out.
F
You
know
what
your
distribution
strategy
is
a
trade
secret
and
that's
a
bad
thing
and
we
had
actually
early
on
which,
because
going
further,
had
a
company
approaches
on
that
and
talked
about
concern
about
security
and
the
fact
that
if
it
got
even
hands
moldable
data
on
a
supply
chain,
you
know
the
AI.
Scientists
could
really
site
that
decipher
exactly
what
your
distribution
strategy
was,
and
that
was
a
big
competitive
disadvantage.
Now
you
can
go
through
your
own
examples
in
your
own
industries,
the
only
thing
you're
doing
health
care.
You
know,
genome
pet.
F
F
So
essentially,
today
many
of
encryption
schemes
are
done
at
a
volume
or
database
level.
Great
schemes,
you
know
sequel,
has
break
the
security
capabilities,
but
it's
kind
of
a
brute
force
attack
one
you
could
continue
put
the
entire
database,
or
else
you
do
column,
which
is
rules
or
you
just
cook.
The
blonde
think
about
this
for
a
minute.
If
you
are
distributing
the
data
across
the
network
and
the
distributor
or
decentralized
application.
F
Well,
everybody
in
that
network,
who
has
a
piece
of
hardware,
has
better
administer
it
well
or
else
this
doesn't
work,
because
if
one
of
them
is
not
administered
little
I'm
not
encrypting.
My
database
of
my
volume
and
I
breached
that
I
attack
that
and
I
get
into
it,
I'm
going
to
be
able
to
open
up
and
I
understand
everything
on
the
chain.
F
So
that's
a
problem
doesn't
matter
well
again:
application
layer
does
work
well
in
a
distributed
environment,
centralized
key
management
services,
you're
dependent
on
a
network,
and
they
know
and
I
was
say
well
the
big
deals
about
this.
Why
doesn't
it
work
with
a
decentralized
world?
There's?
Actually
a
lot
of
network
latency
a
lot
of
the
functions?
Christian
don't
perform
well
getting
the
encryption
key
to
the
right
person
at
the
right
time
in
the
network
is
harder,
then
there's
distributed
data
itself,
so
doesn't
work
all
that
well,
but
then
someone
I,
think
main
consent.
F
F
B
Encryption
key
management
with
a
major
infrastructure,
pharmacologic
implementations
in
the
future
I
think
we
can
all
understand
that
it
doesn't
make
sense
to
use
a
centralized
key
management
solution
for
a
decentralized
base.
That's
an
obvious
blunt
attack
I
just
really
work.
It
has
been
this
compliant
and
meet
all
the
best
security
standards
and,
of
course,
we
want
to
give
an
image
of
the
best
part
of
the
blockchain,
which
is
a
trusted
environment.
It'll
be
doing
a
great
audit
trail.
B
You
get
from
that
and
having
all
of
the
commands
which
shirt
on
the
trains,
you
can
go
back
and
review,
and
it
needs
to
be
easy
for
developers
to
integrate,
with
typically
when
Enterprise,
especially
unfriended
blocking
applications,
they're
really
difficult
to
integrate
and
create
applications.
On
top
of
that's
a
big
disconnect
that
I'm
seeing
between
the
appearing
environment,
hyper,
lizard
environment,
you
can
get
anyone
and
drink
about
in
baking
start
praying
imperium
application.
B
E
Just
a
quick
question
chip
blink
every
because
I
was
I
was
noticing
not
too
many
enterprise.
Folks
here
just
want
to
make
sure.
Does
everybody
understand,
miss
them
fits
I.
Think
that's
a
sports
betting
just
30
seconds
on
that.
Okay,
these
are
formal
certification
levels
of
how
your
keys
are
generated,
stored
and
managed.
The
reason
this
is
important
is
because
most
of
the
confidentiality
and
financially
sensitive
applications
users-
companies
enterprises
banks.
So
if
you
don't
take
that
column,
if
you
just
say
your
application
is
not
missed,
your
keys
are
not
missed
and
FIPS
140-2
compliant.
E
It
will
say
it's
a
very
interesting
presentation,
real
cool
stuff,
come
back
when
you
do
it's
just
one
of
those
things
that,
if
you
don't
do
it,
you
can
really-
and
this
is
where
a
lot
of
proof
of
concepts
never
convert
to
real
applications.
You
can
do
a
group
of
concept
and
say:
oh
yeah,
we
just
grabbed
a
key
from
open
source,
key
generator
and
it's
all
good
and
which
is
going
to
store
it
somewhere
over.
Here
it
has
some
good
stuff
in
a
pass
muster
with
anyone
who
has
liability
for
data
or
financial.
E
F
A
F
Guys
were
awesome
and
they
were
talking
about
all
kinds
of
important
things
about
ability,
consortium
and
all
that
kind
of
stuff.
But
then
they
did
touch
on
data
and
they
talked
about
and
David
huling
who
is
on
the
panel
from
Microsoft,
is
pretty
articulate
very
articulate.
This
area
I
said
you
know:
I
talked
to
him
afterwards.
He
goes
yes,
people
move
into
production,
they
kind
of
think
about
how
they
manage
Kings.
F
F
B
So
Before
we
jump
in
the
demo.
Let's
just
quickly
go
over
a
little
bit
of
architecture.
You
can
talk
about
it.
So,
as
you
can
see
here
long,
he
takes
care
of
all
the
heavy
lifting.
It's
all
pretty
self-contained,
because
a
client
application
just
interact,
lock
and
key
and
stands
through
a
calls.
This
is
actually
here.
You
see
Ariel
watching
you
can
switch
out
a.
A
B
For
any
blockchain
that
you'd,
like
hyper
ledger
for
an
example,
this
system
are,
we
started
a
foundation.
We
started
with
a
km
which
is
a
product
of
patrick
townsend,
created
it's
a
great
key
name
that
software
Agenor
prize
grades
used
by
companies
like
MongoDB
the
fantastic
product.
So
this
is
a
good
Kendall
over
you.
Now
we're
gonna
jump
into
a
demo,
so
many
parts
demo
is
that
we're
just
demonstrating
the
steps
that
you
go
through.
If
you
wanted
to
use
different
calls,
how
that
would
look?
Of
course
we
actually
it
reaches
an
application
level.
B
It's
going
to
be
a
lot
more
exciting.
It's
going
to
or
dynamic
we're
just
showing
the
steps
here
and
I'd
like
to
also
say
this
is
probably
the
first
time
a
year,
you've
ever
seen
encryption
on
a
blockchain
that
was
running
about
public
test
net
and
there's
never
ever
been
in
question
on
blockchains.
This
will
be
one
of
the
first
times
in.
C
F
You
saw
there
in
the
architecture.
What
makes
this
work
fundamentally
is
all
that
functionality
is
in
every
application.
Every
nose
was
distributed
everywhere,
including
the
keyboard
okay,
so
this
is
fundamentally
the
secret
sauce
that
makes
this
work
all
that
capability
is
decentralized.
Now
the
challenge
becomes.
How
do
you
coordinate
right?
How
do
you
coordinate.
E
E
But
if
you
this
keep
this
resource
is
replicated
and
effectively.
The
blockchain
becomes
not
only
audit
record
of
all
that
transpired
between
them,
but
also
a
mechanism
of
sharing
key
components.
Data
in
this
case
for
the
purpose
of
enabling
certain
functions,
business
functions
in
different
members.
E
So
you're
running
a
No
I
mean
you
don't
prejudge.
You
could
have
a
permission
based
network
where
everybody
is
very
well
established,
what
they
do
and
what
you
know
how
they're
all
boarded.
You
can
also
have
an
ad
hoc
network
permissionless
network,
where
people
join
at
will,
but
fundamentally,
if
you're
going
to
manage
keys
with
blocking
key
you're
going
to
have
an
instance,
a
stack
of
capabilities
which
includes
the
key
manager
and
all
of
the
cryptographic
functions
that
go
along
with
it
in
every
instance
that
you
operate,
make
sense.
B
A
D
Great
individuals
and
organizations
can
use
block
and
key
to
protect
and
control
their
confidential
information.
When
developing
a
long-term
solution,
the
number
of
block
chain
nodes
can
range
from
the
view
up
to
hundreds
of
thousands
or
even
more
their
simplicity,
simplicity
sake.
We
will
demonstrate
the
interaction
between
just
to
imagine
that
node
1,
which
is
the
window
here,
represents
one
participant
on
the
block
chain
and
node
2,
which
is
the
window
to
the
right.
The
LARPers
have
a
different
spin.
D
Encryption
keys
will
be
created
and
used
them
to
your
data
owned
by
the
first
participant.
We
will
show
the
basic
building
blocks
without
information
is
encrypted
and
protected
from
others
on
the
chain.
We
will
illustrate
how
that
permission
can
be
granted
to
others
to
be
light
information.
We
will
then
show
how
permission
can
get
revoked.
Finally,
how
that
nina
can
be
deleted.
D
All
this
activity
is
recorded
on
the
blockchain,
moved
by
summary
of
activities
and
their
return.
In
this
step,
we
will
create
a
symmetric,
key
participating.
The
one
can
use
later
to
protect
his
information
through
encryption.
The
end
result
is
that
a
key
has
been
successfully
created,
recorded
font
electric
and
stored
in
the
key
ball
of
every
node
of
the
block
akita
network.
D
D
D
We
can
see
that
a
key
creation
event
has
been
detected
and
a
key
retrieval
request
has
been
made.
The
end
result
is
that
the
key
with
name
my
key
is
now
imported
in
Note,
2
Keeble.
However,
it
does
not
yet
have
the
authority
to
use
it
now,
let's
try
the
retrieving
the
symmetric
key.
We
just
created
using
the
node
that
we
use
to
create
key.
D
D
D
Now,
let's
demonstrate
what
it
looks
like
to
perform
the
same
operation
on
note.
That
does
not
have
the
authorization
for
that
key.
Let's
go
over
to
node
number
two.
You
will
try
to
get
the
same
key
with
named
my
key,
and
we
will
expect
that
it
will
fail
because
it
does
not
have
the
authorization
on
this
key.
You.
D
Can
see
that
the
error
has
been
returned
and
that
the
key
access
is
not
granted.
This
is
because
know,
number
one
has
not
given
Authority
or
the
key
created
to
any
other
node
with
block
and
key
participants
can
create
cryptic
keys
that
can
be
used
to
obscure
data.
We've
created
a
key
and
demonstrate
the
process
of
retrieving
that
key
from
nodes
that
are
authorized
and
nodes
that
are
not
authorized.
If
this
step,
we
will
demonstrate
encrypting
a
key
encrypting
data
with
the
key
we
just
created.
D
D
And
this
is
our
IV.
We
have
all
the
components
necessary
to
decrypt
this
file.
Take
note,
that's
a
key.
My
key
has
been
created
by
our
note.
This
means
that
we
should
expect
a
successful
decryption.
Let's
try,
it
looks
like
that
operation
is
successful
and
we
got
the
plaintext
in
return.
The
plaintext
is
medical
record.
D
Since
we
were
able
to
successfully
decrypt
this
file
on
the
note
which
created
the
key,
let's
demonstrate
the
cross
decrypting
this
file
on
another
note
that
does
not
have
access
to
that
key.
What
we
will
do
is
go
over
to
the
second
node
and
use
all
the
same
information
that
we
did
for
this.
The
previous
decryption
process.
D
So
we
will
attempt
to
decrypt
the
following
ciphertext
using
this
key,
and
this
IV
take
note
that
this
this
node
does
not
have
authorization
to
use
this
key.
So
we
should
expect
this
decryption
process
to
fail.
Let's
test
it
out
now
looks
like
we
need
NIC
fail
and
we
got
the
error.
Key
access
is
not
granted.
D
In
the
previous
step.
Note
number
two
was
unable
to
decrypt
this
file
because
it
had
no,
it
did
not
have
access
to
use
the
key
to
decrypt
that
file.
In
this
step,
we
will
authorize
nodes
to
to
use
the
key
that
we
created
its
go
to
authorize,
key
and
use
key
name.
My
key
here
I
have
the
theory
of
address
for
that
lock
and
key
node,
which
I'll
paste
here.
In
this
step,
we
will
authorize
that
node
to
use
the
key
name.
My
key.
D
D
Now
that
no
2
has
been
granted
access
to
the
key
with
named
Mikey
will
try
and
perform
the
same
decryption
operation
previously
decrypting
the
Sutton.
This
ciphertext
return
to
error.
Key
access
is
not
granted
now
that
the
key
access
has
been
granted,
I
was
trying
to
grip
with
the
actual
Sacre
text.
Imagine.
B
D
D
And
will
revoke
access
to
the
following
key,
my
key,
the
node
with
aetherium
address
listed
here.
When
we
submit
this
request,
we
will
expect
that
the
the
key
access
for
node
2
will
live
in
revoke
and
node.
2
will
no
longer
be
able
to
use
the
key.
My
key
to
decrypt
files,
let's
try
it,
it
looks
like
the
result
has
been.
The
authority
has
been
revoked
for
key
my
key
to
node.
With
this
address
now
the
key
access
has
been
revoked
for
node,
2
or
key.
My
key,
as
shown
here.
D
Let's
try
and
decrypt
the
same
file
on,
though,
to
show
that
the
node
is
no
longer
able
to
get
that
file
and
no
2.
We
have
the
same
key
name.
We
have
the
same
cipher
text.
We
have
the
same
ip.
The
only
difference
that
node
2
is
no
longer
authorized
to
use
this
key.
Now,
let's
try
it
and
decrypt
the
file.
D
D
D
We
can
drill
into.
We
can
view
all
the
transactions
taking
place
on
the
smart
contract.
We
can
also
drill
into
specific
transactions
to
see
the
details
of
how
they
took
place.
For
example,
the
latest
transaction
shown
here
shows
the
address
of
the
of
the
node,
which
we
revoke
access
to
just
moments
ago.
D
B
So
I
know
that
was
a
really
developer
kind
of
focused
demo
and
not
exactly
fireworks.
Let
me
give
you
just
contact,
so
what
you
just
saw
you
know
for
years
we
thought
blockchain
was
one
thing.
We
thought
that
blockchain
is
great.
It's
for
the
first
time
in
human
history.
We
now
have
a
trusted
space
that
doesn't
rely
on
other
human
beings
that
doesn't
rely
on
any
centralized
organizations,
but
that
came
in
caveat
my
caveat
was
the
important
blockchain
is
being
exposed
to
everyone.
B
E
E
It
makes
it
amazing
concept,
but
I
think
once
you
start
getting
comfortable
with
it
even
see
things
that
you
can
do
so.
The
next
couple
of
slides
deal
with
what
what
does
that
mean?
What
you
just
saw,
what
does
that
mean
in
real
life,
and
these
I
will
I
will
say
that
in
describing
this,
these
are
not
just
theoretical.
We
have
engaged
early
with
prospects
who
are
each
there's?
It's
not
accidental.
That's
not
that
we
have
prospects
in
each
one
of
those
spaces
that
we're
working
with
to
make
their
application
real.
E
So
we
speak
from
a
position
of
actually
having
elbow-deep
in
this
in
these
particular
solutions,
but
I
think
they're
instructive
in
what
it
means.
So,
let's
talk
about
that
the
first
and
really
this
will
be
in
the
order
of
closest
to
today's
reality
to
farthest
away
from
today's
reality.
Ok,
so
it's
it's!
A
bit
of
a
continuum
we
seem
to
have
the
blockchain
space
that's
divided
into
two
worlds.
There
are
people
who
want
to
make
it
work
just
in
a
today's
infrastructure
and
really
don't
care
about
all
of
the
philosophical
aspects
of
it.
A
E
And
but
the
reality
is
that
it's
going
to
be
a
process
and
it's
going
to
be
a
continuum
as
with
any
technology,
and
so
this
is
meant
to
kind
of
trying
to
close
a
little
bonus.
So
what
does
this
mean?
The
first
use
case
really
talks
about
the
fact
that
your
date
of
it
actually
can
be
centralized,
which
means
that
you
can
attach
this
mentality.
You
can
decentralize
your
control
of
the
data
while
still
working
with
centralized
data.
That
made
me
a
little
counterintuitive.
E
You
know,
but
when
you
think
about
it,
you're
not
going
to
change
the
world
overnight,
you're
going
to
have
centralized
databases.
The
difference
is,
is
that
today
the
people
who
run
the
central
databases
also
hold
the
keys,
and
typically
one
team
or
just
a
few
keys.
But
it's
they're,
you
know
saying
well,
I'm
encrypted
it
and
I
have
the
key,
so
you're
safe
and
what
the
world
is
pushing
to
and
what
the
regulations
are
pushing
to
it
and
what
people
are
pushing
to
is
to
say.
E
Well,
you
can
hold
the
data,
but
let
me
hold
the
keys
yeah,
it's
us
when
you
think
about
it.
So
it's
a
small
conceptually
technical
change,
but
it's
a
big
conceptual
change,
because
what
you're
doing
is
you're
moving
the
keys
outside
of
that
control
environment.
So
what
does
that
mean?
Well
in
our
vision,
it
means
that
you
have
nodes
that
operate
key
orchestration,
which
enable
different
parties
to
control
an
able
and
revoke
keys
for
the
data
that
is
actually
stored
in
the
centralized
database.
E
That
makes
sense
so
you
have
used
the
blockchain
as
the
mechanism
of
enforcing
rights
obligations,
financial
obligations
between
the
participants
who
are
managing
the
keys
and
passing
the
keys
to
each
other
and
revolting
keys
from
each
other,
but
the
data
remains
st.
Tripp
centralized.
Now
we're
not
saying
this
is
a
decentralized
solution,
we're
just
saying
that
this
is
the
decentralized
way
of
workers
trading
keys.
So
what
does
it
mean?
Let's,
let's
to
take
it,
you
really
use
real
use.
E
Okay,
we'll
circle
back
around
to
that
commit
the
next
use
case,
takes
it
up
a
notch
and
it
says
well
you're
going
to
have
use
cases
where
the
data
will
be
decentralized,
but
it's
not
going
to
be
on
the
chain.
Each
member
is
going
to
have
their
own
data
instances
and
sometimes
there's
going
to
be
data
objects
that
belong
to
a
different
number
than
a
stored
here
or
in
this.
But
fundamentally
the
data
is
decentralized.
It's
just
not
decentralized
on
the
chain
in
this
case.
E
Once
again,
the
chain
is
the
controlling
mechanism
for
writes
encryption
decryption,
but
the
data
is
now
not
centralized,
but
it
actually
follows,
along
with
each
node
different
use
case,
different
scenario,
different
implications
for
costs,
speed
of
operations,
all
of
those
things
come
into
play.
Let's,
let's
take
a
look
at
the
example
of
that.
E
So
in
this
case,
if
we're
talking
about,
for
example,
supply
chain
and
it's
the
real
example
where
different
members
of
the
supply
chain
have
their
own
data,
sets
that
they're,
maintaining
and
contributing
and
sharing
with
each
other,
but
really
what
they're
sharing
is?
Yes,
sometimes
specific
data,
but
they're
sharing
rights
to
getting
to
that
data
I'm
not
getting
to
that
data
as
appropriate
in
this
particular
use
case.
Yes,.
E
A
E
This
is
the
Nirvana
that
everybody
talks
about.
You
know
which
is
well
I
have
my
keys,
and
my
data
is
on
the
chain.
So
now
the
keys
are
being
distributed
and
the
data
is
actually
written
on
the
chain
as
well,
so
there
is
no
traditional
database
centralized
or
divided
or
decentralized
in
any
way.
The
data
is
now
writing
on
the
chain.
The
issue
with
is,
of
course,
to
get
a
use
case
America
if
you're
a
load
in
today's
technologies
of
distributed
letters,
your
payload
can
only
be
so
big.
E
E
E
How
to
treat
digital
assets
written
in
the
form
of
smart
contracts
on
the
chain,
so
what
they
accomplished
by
doing
that
is
that
the
policy
can
be
verified
and
enforced
by
another
member
and
verified
by
another
member
so
effectively
by
publishing
it.
They
prevent
any
internal
possibility
of
fraud
or
Mophie
'sons,
because
it's
now
they've
published
it,
but
somebody
else
enforces
it
effectively.
E
Why
am
I
showing
this
is
because
there
isn't
one
way.
What
we
find
is
that
the
reality
of
use
cases
in
the
reality
of
what
people
are
doing
with
this
technology?
There's
a
whole
vast
continuum
here
and
you
can't
just
say:
well
you
do
it
this
way,
you
have
to
take
into
consideration.
What's
the
other
result,
you're
looking
for
what
is
the
payload?
What
is
this?
The
transaction?
What
is
the
volume
of
transactions?
What
is
the
cost
you
willing
to
sustain
for
processing
these
transactions?
Is
this
going
to
be
permission,
change
public
chamber?
E
All
of
those
things
come
in
two
places,
but
we're
claiming
is
that,
regardless
of
how
you
do
this
you're
going
to
need
to
encrypt
that
data,
regardless
of
how
it
moves
about
and
you're
going
to
need
to
do
it
with
keys
that
are
properly
created,
managed
and
safe?
And
that's
what
button
key
provides
next
slide
it.
Actually,
there
is
a
use
case
that
we
have
that
actually
leverages
all
of
these.
E
E
F
A
E
I
mean
I,
don't
want
to
say
completely
no
in
the,
for
example,
policy
question
you,
you
do
deal
with
keys
and
policy,
but
that's
not
what
this
is
about.
What
this
is
about
is
we're
using
smart
contract
to
pass
the
key
between
one
key
manager
to
another
key
manager,
that's
in
the
network
and
then
enable
or
revoke
rights
from
this.
E
F
E
F
F
E
E
F
E
Let
me
answer
kind
of
a
two-step
two-step
home.
The
the
mechanism
is
not
open
for
general
examination.
Let's
put
it
this
way
now.
Is
it
it's?
It's
meant
to
help
somebody
comply
with.
What's
supposed
to
happen,
it
doesn't
mean
that
it
cannot
be
violate
the
intent
of
it
cannot
be
violated.
Doesn't
she
say
so?
B
We
thought
about
you
know
it's
what
we
buy
developers
when
they're
creating
applications.
How
do
they
get
around
this
right?
So
there's
two
different
ways
that
they
can
get
around
this
one
will
be
a
tiny
mechanism
that
requires
you
to
check
back
in
after
a
certain
amount
of
time
right,
so
you
can't
just
get
granted
permission
and
then
just
run
off
with
all
the
data
right.
Another
way
to
do
it
is
you
great
access,
the
data
ad
hoc
as
soon
as
it's
requested,
so
it
can
be
very
dynamic.
B
E
Let's
address
good
I
mean
it's
a
good
point
and
one
answer
you
will
find
unsatisfactory,
but
real
life
and
I
think
the
end
of
a
movie
more
satisfactory.
But
the
first
point
is
that
actually
one
of
the
reasons
we
use
this
heart
and
T
manager
is
because
it's
not
that
simple,
that
both
the
key
management
functions.
Generation
management,
the
use
and
encryption/decryption-
are
all
within
a
hardening
clave
of
that
on
that
part.
So
that's
a
significantly
harder
thing
to
deal
with
okay,
so
which
is
a
good
thing.
E
Having
said
that,
one
of
the
inherent
benefits
of
decentralized
meta
system
and
decentralized
data
is
it,
of
course,
significantly
lessens
the
price.
So
if
you
manage
to
hack
one
node
and
you
get
the
price
for
that,
one
node,
it's
not
the
same
as
getting
the
mother
lode
of
the
entire
database
axis
and
having
only
access
to
that.
This
is
not
some
kind
of
a
magic
silver
bullet
that
conquers
all
challenges,
but
it
is
significantly
more
robust
than
what's
happening
right
now.
In.
D
E
To
me
why
this
would
ensure
sure
a
couple
of
points.
One
is
so
you
run
into
all
sorts
of
current
and
to
all
sorts
of
shortcomings.
The
mountain
domain,
one
that
you
will
find
is
that
the
proposed
architecture
says
everything
is
nicely
decentralized,
but
not
the
key
manager.
Key
managers
still
centralized
so
you're,
relying
on
that
one
one
provider.
So
that's
that's.
That's
that's
one
case.
There
is
a
whole
host
of
others,
typical,
open
source
and
other
tools
that
you
can
work
and
weave
into
your
work.
E
If
you
know
how
to
do
it,
if
you
know
how
to
properly
implement
it,
if
you
have
a
write
scheme
that
you
have
thought
through
about
how
you're
going
to
pass
the
keys
and
under
what
conditions
or
what
roles
we're,
not
necessarily
saying
that
you
couldn't
achieve
this
through
careful
design,
architecture,
thinking,
pieces
and
doing
development
yourself,
that's
not
that's
not
what
we're
saying
we're
just
saying
that
you
can
do
it
a
lot
faster,
reliably,
compliantly,
very
importantly,
to
miss
the
fits
with
what
we're
providing
off-the-shelf.
So
it's
not
a
you
know
it's
not
like.
E
E
E
The
there's
some
interesting,
it's
been
interesting.
The
adoption
barriers
is
probably
as
much
what
we
found
with
the
developer
mentality
as
anything
else.
A
lot
of
the
developers
in
this
space
just
don't
care.
You
know,
I'm
gonna,
grab,
I'm
gonna
grab
me
some
ethereal
open
source
that
he
might
be
generating.
I'm
gonna,
stick
it
in
it's
good
enough
for
now
I'll
get
through
and
then
I'll
worry
about
it
afterwards
and
then,
of
course,
worrying
about
it
is
nothing
things
as
permanent
as
temporary
solutions
right.
So
it's
it's
solomon
is
is
just
the
mentality.
E
Oh,
this
is
a
not
important
piece.
What
I'm
doing
is
important.
This
is
something
I
can
take
care
of
later,
and
that's
of
course,
if
you
look
back
20
years,
this
was
the
problem
with
the
original
security
propositions
is
we'll
deal
with
it
later
and
then
you
have
Equifax.
So
it's
it's.
What
we're
you
know,
what
we're
trying
to
say.
Do
it
right
up
front?
Do
the
right,
Hutchins
press,
so
that's
that's
one!
Okay,
two
is
is
what
we
found.
E
This
is
for
the
that's
for
the
people
who
are
in
the
decentralized
space
and
are
all
sold
on
the
block
for
people
who
are
in
the
enterprise
space.
It's
a
really
difficult
mental
leap
from
centralized
you're
under
my
control
behind
my
firewall
that
had
totally
control
all
of
a
sudden
sharing
keys
with
external
parties.
That's
that's
it.
E
That's
a
paradigm
shift
that
for
enterprise
folks
is,
is
not
a
simple
one
which
I'm
sorry
just
which,
which
is
why
actually,
we
found
more
traction
with
people
who
already
have
a
pressing
need
to
move
legacy
data
into
the
cloud.
So
when
you
think
about
that,
it's
sitting
there
in
a
silo
and
it's
protected
by
all
tools
and
all
means,
but
they're
being
pressed
to
ETL
their
data
into
the
cloud
and
move
it
into
analytics
and
they
are
their
tools
that
they're
going.
These
are
my
crown
jewels.
Do
I
how
do
I
control
this?
F
F
F
E
To
be
fair,
there
is
a
and
you
triggered
that
point
about
adoption
issues.
There
is
a
issue
about
private
versus
public
blockchain
right
and
that
has
to
do
with
cost
and
speed,
because
if
your
application
requires
these
keys
to
be
lickety-split
in
a
thousand
different
nodes
right
now,
we
can
know
based
on
the
brand
on
the
public
change.
That's
a
significantly
more
difficult
proposition.
B
E
B
I
could
give
two
cents
on
some
berries
I
see
it's
almost
entirely
comes
down
to
education,
how
much
whatever
the
other
party?
How
much
the
other
party
knows
about
the
industry
of
the
space,
how
deep
they
are
a
theoretical
conversation
that
we've
been
having
it's
really
really
difficult
to
approach,
doesn't
know
that
much
about
blockchain
and
start
having
these
kind
of
sessions.
A
E
F
F
Think
that
was
our
last
question
really.
Thank
you
very
much.
The
you
know.
This
is
a
great
opportunity
for
all
of
us
to
be
here
and
have
these
kinds
of
meetings,
the
use
cases
that
you
put
forward.
I
love
it.
If
you
guys
would
contact
us,
have
challenges
on
your
use
cases,
we'd
love
to
work
with
you
and
understand
the
stage
where.