►
From YouTube: Block to Basics – Hyperledger Key Management - Alex Rabke, Digital Asset Security, Unbound Tech
Description
Block to Basics – Hyperledger Key Management - Alex Rabke, Digital Asset Security, Unbound Tech
The foundation of any blockchain-based technology lies in the quality of the cryptography that underpins the ledger. More specifically, successful management of the blockchain private keys is critical to the success of any project using this technology. Typically, the private keys exist as a single point of failure for security and operational concerns. Join this session to learn the basics of traditional blockchain key management methods (including those implemented in Hyperledger-based architectures) and how they compare to more modern and sophisticated models such as those based on MPC (multi party computation). Session will include a live demo of key management interface for Hyperledger-based project workflow.
----
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 #HyperledgerGlobalForum2020 #Blockchain
A
Good
afternoon,
everyone
for
some
reason,
I
always
find
myself
giving
the
presentation
on
cryptography
after
lunch
lucky
me,
but
as
you're
probably
aware
that
since
you're
here,
key
management
and
cryptography
is
obviously
critical
to
the
cause
of
everyone
traveled
into
Phoenix
around
the
hyper
ledger
initiatives.
So
thanks
for
being
here,
especially
in
the
light
of
issues
with
with
coronavirus,
my
name
is
Alex
rabokki
I'm,
a
director
at
a
company
called
unbound
Tech.
We
are
cryptography
company
and
specifically,
a
type
of
cryptography
known
as
MPC
or
multi-party
computation,
I.
A
Titled,
the
the
topic
of
my
slide
has
blocked
two
basics
right
play
on
back
to
basics
and
I'll
just
take
a
quick
poll
of
everyone
in
the
room
on
a
scale
of
one
to
three
one
being
don't
really
know
much
about
key
management
came
here
to
get
the
101
to
is
you're
a
technology
or
security
practitioner
and
three
is
you're,
a
cryptographer,
so
ones
in
the
room.
People
just
learning
about
this
twos
and
threes.
A
A
What's
going
on,
I'll
share
some
of
the
things
that
that
we're
working
on,
but
the
point
being
is
that
fundamentally,
blockchain
is
a
technology
that
has
an
underlying
reliance
on
cryptography
and
there's
a
lot
of
potential
for
blockchain
based
technology
and
applications
of
it,
but
there's
also
inherent
challenges
and
the
technology.
So,
first
of
all,
it
bought
chain
isn't
a
panacea
to
our
technology
plates
that
exist,
there's
certainly
advantages
and
disadvantages,
and
one
of
those
and
those
disadvantages
and
advantages
need
to
be
considered
in
terms
of
the
use
cases.
We
target
that
being
said.
A
When
the
technology
is
a
fit,
it
tends
to
be
a
really
good
fit,
but
it
does
present
us
with
a
historical
trade-off
or
compromise
between
what's
referred
to
as
the
trilemma.
Anyone
in
the
room
familiar
with
this
notion
all
right.
It's
the
idea
of
having
having
your
cake
and
eating
it
too.
So
when
implementing
a
blockchain
technology
like
something
based
on
the
hyper
ledger
fabric,
how
how
can
we
implement
technology
in
a
way
that
delivers
security
scale
and
decentralization
to
capitalize
on
the
best
attributes
across
those
elements?
A
So
when
we
talk
about
the
domain
from
a
pill
from
a
pillar
based
standpoint,
around
security,
again
back
to
the
idea
of
key
management
and
cryptography
being
fundamental
to
the
success
of
this
technology,
we
have
to
understand,
and
the
market
needs
to
understand
and
I
do
believe.
There's
a
lot
of
growing
awareness
around
this
that
were
ultimately
protecting
and
storing
data
on
a
distributed,
ledger
or
database,
and
if
you
don't
control
the
keys,
the
private
keys
to
that
database
or
that
ledger.
It's
not
your
data.
A
This
applies
to
public
based
use
cases
like
crypto
currencies
and
private
use
cases
and
the
enterprise
around
initiatives.
We've
worked
on
on
supply
chain
and
and
other
various
types
of
implementations.
One
of
the
stories
I
like
to
tell
is
the
notion
of
digital
transaction
signing.
This
takes
place
in
the
enterprise
space,
with
instances
like
software
code
signing,
for
example,
in
the
context
of
this
situation,
it
relates
to
how
transactions
are
signed
and
hashed
to
the
blockchain.
A
So
when
you
go
to
a
store
and
you
swipe
your
credit
card
and
get
a
receipt
and
sign
it
with
a
smiley
face,
who's
checking
to
make
sure
that
you
actually
signed
the
receipt
accurately
who's,
verifying
that
the
signature
was
accurate
and
reliable
and
authentic.
This
ties
back
to
the
identity
of
the
participating
parties
and
it's
only
as
sound
as
verification
that
occurs,
and
this
verification
can
and
should
happen
at
the
cryptographic
layer.
So
the
security
element
is
critically
important
because
the
foundation
of
the
technology
relies
on
this
now.
A
This
back
to
technology
frameworks
that
are
well
known
and
understood
because
ultimately
we're
delivering
a
new
paradigm
to
the
market
with
technology.
That's
a
bleeding
edge,
not
bleeding
out
and
in
order
to
relate
that
back
to
key
stakeholders
who
we
need
to
gather
buy-in
from
and
resources
from,
whether
it
be
human
capital
or
or
financial
investment.
We
need
to
articulate
things
in
a
way
that
are
well
understood
and
accepted
and
have
a
legacy
of
successful
implementations.
A
So
for
this
often
reference
the
NIST
800
series,
which,
if
we
have
any
cybersecurity
practitioners
in
the
room,
might
be
familiar
with.
It's
actually
a
really
really
good
set
and
library
of
resources
for
implementing
information.
Security
controls
across
the
enterprise
and
many
of
them
tied
directly
back
to
encryption
and
cryptography,
which
of
course,
as
I
mentioned
and
will
continue
mentioned,
is
the
underpinning
of
everything
that
we're
doing
whether
some
people
realize
it
or
not
and
there's
a
footman
there's
a
framework.
A
I
got
this
thing
with
triangles,
obviously
right,
it's
the
trilemma
and
and
then
the
the
CIA
triumvirate
so
delivering
a
decentralized
model.
That's
aligned
with
a
well-understood
InfoSec
framework
that
encompasses
confidentiality,
integrity
and
availability
of
the
the
digital
services
being
provided
is
one
that
in
a
lot
of
times,
is
aspirational,
but
it
doesn't
have
to
be,
nor
should
it
be
so
ultimately
I'm
drawing
an
emphasis
on
why
key
management
is
critical
and
it's
again
because
the
technology
relies
on
an
underpinning
of
encryption
and
cryptography.
A
But
ultimately
it
comes
back
to
the
fact
that
clip
those
hard
right
there's
a
reason.
Only
two
or
three
of
us
in
the
room
consider
themselves
in
the
field
of
cryptography
and
it's
because
it's
it's
really.
It's
a
really
challenging
field
of
study
and
an
even
more
challenging
field
of
implementation.
A
The
most
accepted
paradigm
in
in
the
space
is
really
this
notion
of
protecting
keys,
and
typically
this
is
done
with
something
called
a
hardware:
security
module
or
HSM,
which
is
a
black
box.
Typically,
it's
a
piece
of
hardware
that
sits
in
a
data
center
either
or
someone
else's,
and
it
exists
with
the
sole
intention
of
protecting
cryptographic,
keys
and
certificates.
A
It's
the
only
reason
that
exists.
No
one
buys
an
HSM
bit
because
they
want
to
write
it's
supposed
to
be
an
enabler.
I
see
some
smiles
in
the
back
of
the
room.
It's
supposed
to
be
an
enable,
a
neighborhood
of
technical
service
delivery
and,
in
some
cases,
it's
quite
good
at
that
specifically
around
the
notion
of
key
protection,
but
what's
unique
about
the
blockchain
space.
Is
that
we're
not
just
concerned
with
key
protection,
but
we're
also
concerned
with
key
key
usage
and
specifically
the
notion
of
fraudulent
key
usage.
A
This
can
often
often
comes
come
from
in
not
just
external
but
also
internal,
bad
actors,
or
simply
the
mismanagement
of
keys,
where
they're
not
necessarily
stolen
but
they're,
simply
lost
or
mismanaged
or
made
unavailable
in
instances
or
use
cases
where
high
availability
is
a
requirement.
This
can
become
challenging
when
you
rely
on
a
hardware
based
model.
A
There's
digital
communications
that
generate
proposals
to
the
hyper
ledger
network
and
one
of
the
things
that's
interesting
to
me
and
I
think
the
advantage
to
the
network
is
this
notion
of
peer
based
endorsement
to
review
and
quote-unquote
endorse
transaction
proposal
so
that
they're
actually
posted
to
the
ledger
so
I
think
it's
one
of
the
elements
that
makes
the
blockchain
architecture
for
hyper
ledger,
somewhat
unique
and
potentially
powerful.
So
keys
are
involved
on
a
daily
and
even
in
certain
use
cases
a
per
hour
per
minute
or
per
second
based
workflow
requirement.
A
Essentially,
these
these
black
boxes
are
used
to
to
protect
keys
and
they're,
primarily
concerned
with
again
the
protection
of
the
keys,
but
not
so
much
the
usage
or
the
fraudulently
usage
of
them
again.
I've
emphasized
that
this
tends
to
be
in
many
instances
a
model-
that's
quote-unquote,
secure,
I,
never
say
coming
from
the
cyberspace
that
anything
is
100%
secure.
A
If
anyone
tries
to
sell
you
something,
that's
a
hundred
percent
of
anything
they're,
100
percent
full
of
it
I've
used
that
that
line
before
and
it
becomes
interesting
because
I'll
talk
a
little
bit
about
the
operational
model
around
traditional
key
store
and
key
management
based
architectures
and
implementations,
but
from
a
pure
security
standpoint
again,
I've
said
this
probably
three
or
four
times
the
sole
purpose.
A
reason
of
being
for
the
HSM
based
technology
is
to
protect
keys.
A
So
why
is
it
that
when
you
pay
attention
to
the
space
there's
many
many
instances,
not
just
in
research,
but
also
in
the
field
of
either
key
extract
ability
done
in
a
way
that
it's
not
supposed
to
be
done
or
fraudulent
key
usage?
This
is
the
fun
slide,
and
the
one
that's
worth
looking
into
in
your
in
your
free
time
is
some
research
done
by
the
ledger
team
that
was
posted
at
blackhat
this
summer.
A
Scary
thing
here
is
that
they
were
actually
able
to
demonstrate
remote
access
again
to
devices
that
are
supposed
to
be
physically
tamper
proof
they
were
able
to
demonstrate
remote
access
to
exfiltrate
the
key
material
and
then
apply
it
in
a
way
that
was
not
detected
by
the
device
that
is
intended
purely
to
protect
and
alert
if
there
was
some
type
of
tampering
done
to
the
device.
So
again,
it's
not
an
ideal
model.
In
many
cases,
this
being
a
demo
based
presentation,
I
won't
go
into
detail
on
the
numerous
alternative
models.
A
I
will
focus
on
what
our
companies
deliver
to
market
about
five
five
years
ago
with
organizations
that
truly
deliver
service
is
at
enterprise
scale
and
do
so
in
a
way
with
quite
rigorous
security
and
operational
requirements,
namely
some
of
the
large
financial
institutions
like
Citibank
and
Goldman
Sachs.
The
yellow,
the
yellow
circle
that's
represented
here
is,
quite
frankly,
a
poor
illustration
of
how
our
underlying
technology
is.
Taking.
Some
private
key
material
and
charting
it
or
distributing
it
during
the
entirety
of
it,
the
key
lifecycle.
A
So
this
is
a
little
bit
of
it's
not
a
little
bit.
It's
it's
a
it's
a
hard
concept
to
grasp.
If
this
is
the
first
time
hearing
about
it,
but
the
initial
intention
of
our
technology
NPC
was
used
for
use
cases
like
auctioneering,
where
multiple
parties
could
collaborate
around
data
specifically
compute
around
data,
so
that
they
could
provide
an
input
with
the
identity
of
the
input
being
private
and
the
input
itself
remaining
private
as
well,
but
the
output
becoming
publicly
verified.
A
A
Many
people,
including
myself,
are
learning
about
this
technology
in
just
the
recent
years
or
potentially
recent
months
or
potentially
today,
but
it's
actually
a
field
of
cryptography.
That's
been
in
study
since
about
the
days
of
disco,
so
the
early
80s
was
when
the
the
the
research
into
MPC
began.
It's
known
as
a
zero
knowledge
proof
and
it
really
was
not
brought
to
act.
It
brought
to
market
at
commercial
scale
for
a
number
of
reasons.
I
won't
go
into
detail,
but
it
relates
primarily
primarily
back
to
performance
challenges
and
the
dependency
of
the
protocols.
A
Well,
of
course,
is
different
about
about.
Unbound
is
that,
starting
five
years
ago,
we
developed
some
protocols
that
are
patented
and
deliver
reliable
enterprise
grade
scalable
key
security,
key
management
based
on
NPC
protocols,
so
we're
achieving
a
degree
of
security
that
some
of
our
clients
claim
is
even
more
bust
than
a
hardware
based
model,
because
the
key
material
never
exists
as
a
single
point
of
failure
but,
more
importantly,
we're
delivering
a
software-defined
value
proposition.
A
So
you
can
kind
of
think
of
this
as
a
software
to
find
cryptography
scheme
that
that
is,
delivering
security
guarantees
at
a
software-based
value
proposition
a
further
emphasis
again
because
I
get
the
question
of
people
who
kind
of
liken
our
technology
to
other
cryptographic,
schemes
for
the
twos
and
threes
in
the
room,
namely
multi
signature
or
triple
last
remarks.
Tomaters
keep
Shamir's
secret
sharing,
say
that
three
times
fast
based
schemes,
but
with
any
alternative
solution
in
the
market,
key
material
is
brought
together
at
some
point
during
its
lifecycle.
A
Perhaps
that
generation
store
use
on
the
wire
whatever
it
might
be,
so
that
the
private
keys
exist
as
a
single
point
of
failure.
There's
also
a
number
of
integration
and
operational
concerns
with
some
of
the
alternative
availabilities
and
in
the
market
and
I'm
emphasizing
once
again,
I'm
glad
to
see
some
people
taking
pictures
here,
but
the
key
material
never
exists,
incomplete
form.
A
Okay,
before
going
into
the
demo.
This
slide
is
intended
to
look
much
like
the
trilemma
talk
track.
I
spoke
to
prior,
but
I
want
to
emphasize
now
on
some
of
the
specifics
that
I've
covered
in
the
last
couple
minutes
going
from
a
never
heard
of
this
to
okay.
Now
we
have
some
familiarity,
I'm
real,
quick
before
jumping
in
any
any
comments
or
questions
that
could
take
one
or
two
before
going
on.
A
It
doesn't
have
to
be
combined
with
the
protocols
behind
secure
multi-party
computation,
and
this
is
a
foreign
concept
I
never
like
to
use
the
words
trust
me,
because
when
someone
tells
me
that
it
scares
me,
but
what
we've
done
and
do
on
a
frequent
basis
with
clients
is
run
them
through
the
protocols
and
the
mathematics
behind
this
there's
thousands
of
scholarly
papers
and
research,
citations
and
things
of
this
nature,
and
our
founder
professor,
you
Dylan
Dell,
is
he's
the
Big
Daddy
of
MPC.
He
literally
wrote
the
book
called
modern,
applied
cryptography.
A
I'll
show
you
that
also
yeah,
okay,
you
know
don't
get
if
you're,
not
too
technical,
don't
get
scared
by
the
architecture.
This
is
actually
based
on
an
anonymized
use
case
with
the
client
that
we're
delivering
a
hyper
ledger
based
ball
chain
use
case
with,
and
the
use
case
is
around
I
can't
say
the
company,
but
the
use
cases
around
essentially
tokenizing
assets
and
doing
partial
asset
ownership
for
high
value
physical
assets
and
tying
that
ownership
record
and
verification
back
to
the
hyper
ledger
fabric.
A
This
is
the
key
security
and
key
management
mechanism
for
based
on
NPC
for
the
blockchain
private
keys
and
encryption
decryption.
Signing
processes
occurs
within
that
software
perimeter
secured
again
by
that
npc
paradigm,
and
then
transactions
are
reported
via
the
application
service
provider
to
the
hyper
ledger.
Node.
The
data
is
hashed
to
the
node
that
way.
Okay,
so
I'm
going
to
show
you
what
it
looks
like.
A
All
right,
so
three
things
architecture:
this
is
our
unbound
key
control,
web
user
interface
there's
also
an
API
in
which
the
automation
elements
and
things
take
place
and
then
I'm
using
the
postman
application
as
a
sample
application.
This
would
be
much
prettier.
This
would
be
from
your
your
service
provider.
That's
offering
the
services
to
market,
so
in
the
unbound
user
face
we
have
a
number
of
features.
A
A
These
these
types
of
elements,
I've
added
a
hyper
ledger
client,
which
is
my
device,
is
validated
by
a
CA
delivery
of
a
certificate
and
I'm
provision
as
a
user
in
the
system,
security
officer
in
the
system
with
standard
authentication,
access
and
note
that,
with
our
with
our
system,
clients
and
users
are
actually
create,
cryptographically,
verified
and
segmented
to
to
the
system
and
can
be
and
can
have
rules
applied
to
their
usage
and
permissions.
So
this
is
where
policy
and
automation
takes
place
because
users
and
clients
can
be
permissioned
and
added
to
the
system.
A
I'll
just
mention
it
because
it
says
it
here
their
secrets,
this,
the
the
the
software,
can
also
be
used
to
protect
secrets
to
perform
secret
protection
and
management
as
well.
Well,
let's
get
to
the
fun
stuff
around
keys.
Remember
not
your
keys!
Not
your
data.
I've
created
three
key
R
three
keys
keys
here
that
a
representative
representative
of
various
cryptographic
keys
that
be
used
to
sign
certain
transactions.
A
Creat
keys
are
created
this
way
named
and
described
in
the
way
that
you
choose,
the
various
types
of
encryption
keys
can
be
chosen
and
for
the
number
three
is
in
the
room,
you
might
notice
pqc
based
schemes,
meaning
post
quantum
talked
a
little
bit
before
we
wrap
up
around
the
notion
of
something
called
crypto,
agility
and
privilege,
for
that
key
is
also
specified.
So
this
is
an
area
where
we
can
assign
assign
capabilities
or
restrict
them
for
incremental
layers
of
protection.
Again
keys
are
added
with
the
click
of
a
button.
A
A
Now,
let's
go
back
to
the
postman
application.
That's
used
to
sign
transactions
from
this
service
provider
for
an
asset
value
that'll,
be
posted
to
the
blockchain
I've,
inserted
the
user
ID
and
assigning
operation
into
the
into
the
service
provider
application.
This
would
be
blind
to
the
user,
but
for
the
purposes
of
the
demo
I'm
showing
what
it
looks
like.
Let's
pray
that
the
demo
gods
are
kind
and
the
Wi-Fi
is
still
connected.
A
This
is
communicating
real-time
with
my
demo
system
and,
as
you
can
see,
a
valid
key
signature
is
posted
to
the
application.
Now,
let's
jump
back
briefly
to
the
architecture,
so
what
we
just
walked
through
was
horizontally
from
user
blockchain
application
to
the
UKC
system.
What
would
happen
now
is
that.
A
A
I'm
sorry,
like
key
shares
in
this
instance
too,
as
you
saw
in
the
architecture,
slide,
there's
essentially
two
servers,
and
these
are
virtual
servers.
Again.
We
have
no
reliance
on
Hardware,
which
again
maps
to
the
ability
to
deliver
digital
digital
services
right,
okay,
very
similar
slide,
but
we
went
from
high
level
to
more
complicated
to
really
simple.
It's
critically
important
to
control
keys,
and
the
interesting
thing
about
the
software-defined
value
proposition
is
allowing
key
control
mechanisms
and
models
that
are
tuned
to
the
use
case.
A
So
you
can
enable
the
opportunity
for
your
users
to
control
the
keys
or
you
can
do
it
as
a
service
provider.
It's
flexible
from
that
standpoint,
when
we
talk
about
scaling
to
many
users,
many
keys,
etc.
I
was
just
talking
to
someone
today
upstairs
who
has
over
10,000
individual
wallets
with
a
private
key
associated
with
each
of
them.
A
Call
that
key
sprawl,
because
all
those
keys
are
stored
in
a
database
encrypted
by
a
single
encryption
key
for
that
database,
meaning
that,
if
someone
accesses
that
database,
whether
it
be
through
gaining
access
to
the
encryption
key
or
some
other
side
channel
based
mechanism,
they
expose
all
the
data
associated
with
that
customers,
business
and
the
customers
themselves.
This
becomes
really
really
scary.
How
do
we
take
care
of
key
management
at
scale?
It
needs
to
be
quote
unquote.
A
Enterprise-Grade
kernel
quote
unquote
institutional
grade,
as
we
think
about
use
cases
that
occur
across
broad
geographies,
broad
performance
requirements,
etc
and,
of
course,
in
line
with
the
nature
and
ethos
of
the
technology
itself
around
being
a
decentralized
lender,
but
doing
so
in
a
way,
that's
secure
and
compliant.
The
way
that
this
maps
back
to
what
other
technologies
doing
is
that
notion
of
cryptographic,
verification
so
we're
not
trusting
application
based
in
layer,
7
based
technology,
we're
actually
trusting
the
mathematical
proof
of
security
that
I
mentioned
earlier
on.
A
A
A
A
Yaki
wrapping
is
a
really
relevant
use
case
because
you
might
have
especially
an
I
mean
it
could
be
a
green
field
or
a
brown
field
deployment.
But
you,
if
you
already
have
a
workflow,
but
do
you
want
to
protect
that
single
point
of
failure,
the
foundation
of
the
security
model
and
you
can
wrap
a
key
exported
import
that
whatever
you
want,
but
have
it
be
charted
to
the
NPC
based
protocol
such
that?
That
single
point
of
compromise
is
a
limited
eliminated
and
happy
to
talk
to
about
that
use
case.
A
Yes,
so
historically,
there's
been
NPC
protocols
based
on,
what's
known
as
round
trips
and
somewhere
in
the
realm
of
six
to
twelve
or
sometimes
even
more
I
believe,
and
what
this
does
is
introduced
a
high
degree
of
latency
that
must
be
combatted
with
computational
overhead
right.
So
one
of
the
things
that's
unique
about
our
protocols
is
that
they're,
actually
two
round-trips
secure
MPC
based
protocols
and
therefore
the
requirements
for
implementing
this
technology
are
quite
low,
like
single
core
processor,
virtual
machines
and
two
gigs
of
ram
per.
So
that's
to
be.
A
You
know
it's
a
pair
right,
so
at
least
two
servers
that
can
ride
on
any
bare
metal
across
any
cloud
or
geography.
You
could
observe
east-west
AWS,
West,
Zuri
East,
however,
however,
it
makes
sense
to
architect
it
and,
however
many
layers
of
security
you'd
like
to
implement,
of
course,
with
the
reason
you're
looking
at
me.
That
way
is
performance
types
of
concerns
right
availability,
these
these
types
of
these
types
of
things.
So
the
answer
is
that
the
the
computational
overhead
is
quite
low
and,
more
specifically
for
use
cases
that
require
high
TPS
or
transaction
per.
A
B
A
Right
so
if,
if
I
understand
the
question
correctly,
one
mechanism
for
doing
that
is
method
that
we
have
that
logs
all
of
the
activity
that
for
communications
to
and
from
our
software
boundaries.
So
there's
a
logging
mechanism
through
the
command-line
interface
that
can
be
exported
to
some
type
of
automated
reporting,
like
a
sim
based
type
of
solution.
But
essentially
the
verification
would
be
evident
through
the
the
logging
mechanism.
A
I
see
yes,
there
would
be
a
different
mechanism
based
on
an
application
versus
a
cryptographic
versus
posting
to
the
node.
But
let
me
get
you
an
answer
on
that:
okay,
all
right!
So
just
two
am
I
getting
the
tap
okay,
so
just
to
wrap
things
up
again,
control
the
keys.
Do
this
at
scale
and
the
one
thing
I
forgot
to
mention.
You
know
how
silly
of
me,
because
who
cares
about
cost
right
is
providing
a
more
cost-effective
mechanism.
A
Someone
gave
me
a
statistic
earlier
today
and
stated
that
over
there,
enterprise
blockchain
deployments,
half
of
the
capital
cost
is
from
HSM
based
investments.
So
half
of
the
investment
from
the
market
participant
is
in
these
black
box
type
of
technology.
So
how
do
we
position
cryptography
as
enabler
of
next-gen
business
services
versus
an
inhibitor
and
an
obstacle
of
frankly,
a
technology
and
market
that's
maturing
and
needs
and
needs
as
much
help
as
we
can
give
it
so
there's
a
cost
benefit
as
well
that
that
helps
to
address
the
scale
issue.