►
From YouTube: Hyperledger Seattle Meetup - October 17, 2019
Description
Hyperledger Seattle Meetup welcomes Clive Boulton of CertifiedTrue to present on the topic: Toward the Evaluation of Privacy and Confidentiality in Hyperledger Platforms
Clive Boulton has been an active community member in Hyperledger projects since Feb 2017, for the last year meeting bi-weekly with senior practitioners at the Architecture Working Group to develop a white paper on the Evaluation of Privacy and Confidentiality in Hyperledger Platforms.
In this talk we plan to summarize and present how the group went about developing the goals for the paper, the methods for analysis, the commonly used technologies and the ever evolving Evaluation of Privacy and Confidentiality in Hyperledger Platforms. This talk is aimed at a general CTO audience.
More about the event can be found at:
https://www.meetup.com/Hyperledger-Seattle-Chapter/events/264855643/
----
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
A
Thank
you
everybody
for
being
here
tonight.
This
afternoon,
I
said
couple
of
quick
announcements.
You
have
Kevin
from
Steve
Lee.
Today,
that's
doing
some
photography
for
us.
Some
stabling
is
a
local,
stable
point
organization
based
down
at
Pier
66.
So
if
you
aren't
familiar
with
them,
check
them
out
and
then
thanks
to
IBM
for
sponsorships
out
the
snaps
in
water,
which
we
all
always
greatly
appreciate,
I
think
you've
all
been
here.
So
you
know
the
lay
of
the
land
just
a
reminder:
doors
lock
at
6:00.
So
please
don't
leave
anything
here.
A
A
He
learned
my
building
the
micro
services
and
e-commerce
is
much
simpler,
underpinned
by
co-op
chain
consensus.
The
privacy
and
confidentiality
needs
to
be
evaluated
and
underlying
problems.
So
today
he
will
be
sharing
a
white
paper
that
he's
been
working
on
with
the
architecture
working
group
under
hyper
ledger
called
towards
the
evaluation
of
privacy
and
confidentiality
in
hyper
layer
platform.
So
thank
you
so
much
for
being
here
and
thank
you.
I.
B
At
least
18
months,
probably
a
little
bit
longer
than
that
now
his
entitlement
goes
on
and,
generally
speaking,
we
need.
You
know
a
bi-weekly
basis,
which
is
a
lot
of
the
high
polygamy
tips
along
those
lines
and
also
doing
some,
what
sort
of
a
quarterly
face-to-face
meeting
new
identity,
Cisco
or
Fujitsu
or
Intel.
Someone
like
just
Oracle
absolutely
and
just
you
can
sort
of
go
so
far
on
the
web
and
then
you
need
to
have
a
face-to-face.
B
So
this
is
kind
of
where
we
are
right
now,
but
the
paper
is
back
to
its
26
pages,
probably
25
of
that
table
of
contents,
so
I
kind
of
have
prepared
some
slides
where
I
can
just
cherry
picked
a
few
things
to
present
the
kind
of
oranges
I
have
prepared,
and
this
is
a
deck
online,
so
they
can
look
at
it
afterwards.
There's
also
a
copy
of
a
bitly
link.
B
B
Okay,
how
the
architecture
PNC
group
went
truck,
went
about
developing
calls
to
the
painted
methods
of
analysis
commonly
used
technologies
and
the
ever-evolving
the
ever-evolving
evaluation
of
privacy
and
confidentiality,
because
doesn't
stop
because
the
new
technologies
keep
coming
along,
such
as
ZK
proofs.
So
not
in
this
talk,
but
I
thought
it
would
make
me
worthwhile.
Just
looking
at
this
is
brian
behlendorf
broke
down
this
and
just
show
this
remote.
A
B
B
He's
also
saying
that
with
sawtooth
and
that's
the
next
product
that
came
along,
it
was
a
unique
about.
Assaultive
is
even
bring
different.
Small
contracting
systems
to
sort
and
press
fabrics
got
his
own
small
contracting
system,
but
what's
going
on
now
is
because
of
this
greenhouse
concept,
piece,
which
is
being
broken
at
a
soldier.
A
narrative
fabric
is
the
ability
to
bring
those
capability
word
with
different
small
contracting
systems
to
fabric.
A
A
B
B
So,
where
does
that
put
us
why
we
kind
of
they
also
weren't
wanting
to
really
free?
Why
we
here
why
this
is
really
relevance
and
to
kind
of
like
just
tune
us
in
a
little
bit,
so
this
is
from
the
this
is
from
the
IPS
meets
a
big
Toki
of
just
a
couple
of
days
ago.
This
slide
so
I
think
it's
kind
of
interesting,
the
most
the
time
when
we
think
about
business
systems
that
pretty
much
rules
they
will
be
centrally
based.
B
A
B
B
His
print
privacy
and
confidentiality
relevant
men
on
permission,
blockchain
persists
what
we're
talking
about
a
psychologic.
So
we've
got
a
simple
like
similar
tax
on
TLT,
because
identity
based
blockchain,
where
you
can
spin
up
multiple
identities
and
kind
of
like
see
if
even
cheaper
system
sort
of
thing
I'll
be
vulnerable.
We're
going
to
talk
about
some
of
these
things
and
we
can
make
we
can
handle
probe
things
such
as
making
spinning
up
identities
just
a
little
bit
difficult
into
trying
to
add
some
of
those
things
off
and
by
using
by
biometrics
and
so
forth.
A
B
But
what's
going
on
is
they've
got
really
like
two
very,
very
different
business
cultures
there
and
Panasonic
is
actually
embedded
inside
inside
the
mosques
battery
factory
in
the
body,
but
they
have
two
completely
different
business
cultures.
This
Wall
Street
Journal
article
over
here,
showed
that
you
know
you
know.
B
So
so,
what's
going
on
as
they
NAB
some
commonality,
though,
and
the
commonality
is
that
they
both
have
focused
on
the
production
data.
But
when
you
look
at
most
business
systems
you
can
buy,
they
don't
have
that
capability.
They're
designed
pretty
much
like
this.
You
know
central
systems
and
there's
there's
no
real
sharing
of
data,
whereas
I
think
in
Musk's
situation
and
actually
I
picked
up
on
something
and
a
long
time
to
go
out.
B
Expensing
the
question
time
years,
Intel
and
more
recently,
Intel
Cargill,
who
are
members
of
five
alleged
making
some
again
some
innovative
stuff
in
that
supply
chain.
I,
think
we're
seeing
businesses
move
more
towards
this.
Embedding
one
business
inside
another
business,
a
high
level
of
cooperation
and
to
get
that
cooperation
really
needs
a
different
type
of
ID
system,
the
block,
Inc
and
support.
B
And,
of
course,
you
know
in
the
evaluation
of
healthcare
as
well.
The
flow
of
information
is
probably
going
to
be
quite
different,
so
the
engine,
the
paper,
then
this
is
the
introduction
and
goals
the
target
audience
for
this
paper
is
the
general
technical
audience
it's
been
written
by
some
guys.
Most
of
the
guys
that
I'd
say
probably
everybody
is,
is
I'm
not
sure
how
I
got
into
this
group.
B
Yeah
on
that,
so
so
the
document
is
intended
to
educate
the
read
about
potential
channels
where
premising
confidentiality
may
be
breached
through
a
distributed
ledger.
So,
even
though
it's
permission
that
can
still
be
breached,
I'm
going
to
talk
about
that
describe
the
tools
and
constructs
that
may
be
used
to
evaluate
the
privacy
and
confidentiality
guarantees
claimed
by
a
particular
distributed
legend
and
three
to
analyze.
Current
hydrologic
technology,
rather
relative
to
those
objectives.
B
So
while
we
attempt
to
provide
several
examples,
our
intent
is
to
base
your
analysis
on
a
specific
uses,
a
specific
use
case,
and
in
this
case
it's
going
to
be
the
trading
of
liabilities
and
supply
chain.
They
could
actually
call
it
a
factoring
so
there's
a
little
bit
of
academic
that
gets
sprinkled
into
this
and
that's
why
I
needed
to
put
a
poppet
in
front
of
this
team
to
make
it
more
consumable,
Robbin
meeting
from
home
payment.
B
B
So
definitions
for
the
purpose
of
this
paper,
we
concern
about
the
protection
of
information
enforcement,
of
acceptable
policies
for
who
has
access
to
what
information
about
blocking
transactions
and
when
they
have
they
have
that
access
owners.
The
information
should
be
able
to
control
who
has
access
to
the
information
and
for
what
period
of
time.
So
if
you
actually
unwrap
that
it's
quite
a
lot
of
business
logic,
that's
going
on
they're
all
about
data.
B
So,
in
particular,
in
an
ideal
world
we'd
like
to
show
the
users
complete
information,
they're
not
supposed
to
know
this
should
be
doing
it.
You
know
provably,
secure
manner,
ie.
If
someone
knows
something
that
they
shouldn't,
then
they
can
break
either
some
fundamental
cryptographic
assumption
or
some
assumption
we
have
made
about
the
limitations
of
participants
in
adversary's.
So
in
visionaries,
that
sort
of
takes
us
to
a
Bitcoin
may
be
to
a
theorem.
In
the
section
method
for
analysis,
we
define
method
the
method
that
we
can
use
for,
evaluating
properties
of
blogging
platforms.
Okay,
so.
B
So
confidentiality
for
the
paranoid
so
side
channels,
these
represent
a
bounce
through
the
paper
a
little
bit,
so
they
wouldn't
manage
you
to
come
together.
Side
channels
represents
a
second
and
far
less
obvious
form
of
exposing
confidential
information,
for
example,
in
Bitcoin
links,
uses
addresses
for
transactions
which
in
theory,
provided
anonymity
for
transaction.
However,
correlation
between
the
transactions
on
the
address
and
activity
in
exchange
often
enabled
disclosure
of
the
actual
identity
of
the
address
of
the
omen.
B
So
one
things
we
use
in
signals
looking
through
all
these
signals
that
we,
if
you
look
at
enough
information
for
a
enough
period
of
time,
we
can
glean
we
clean
identities
and
all
sorts
of
things
from
that.
So
oftentimes.
We
kind
of
want
to
switch
the
radio
on
transmission
and
switch
it
off
as
quickly
as
possible
to
reduce
that.
B
A
B
Okay,
so
there's
a
section
simmering
here,
and
that
is,
it's
nearly
impossible
to
prevent
all
information
leakage
in
any
internet-based
computation
and
tend
to
miss
patrons
to
provide
the
readers
with
some
tools
for
evaluating
what
information
is
leaked
and
how
to
balance
the
cost
of
prevention
versus
the
cost
of
the
leakage
trade-offs.
So
the
CTO
stuff,
that's
really
what
a
CTA
I
was
up
to
usually
is
he's.
Trying
to
figure
out
is
to
do
the
trade-offs.
Attempting
here
the
smoke
coming,
which
is
you
probably
also
coding,
and
everything.
B
So
the
deep
use
case
that
the
paper
refers
to
is
supply
chain
by
trim.
You
can
kind
of
think
of
that
is
really
like
it
I
think.
Probably
it
would
cover
a
really
good
online
SABR
called
Amazon
type
ordering
system
dollar
system.
The
current
practice
places
old
control
data
under
a
single
organization.
But
to
that
the
ipfs
analogy
I
was
drawn
on
with
with
Elon
Musk
of
the
batteries,
but
with
blockchain
solutions
the
dangerous
potentially
shed
or
will
be
unless
it's
about
management.
B
B
However,
the
existence
of
the
contract
must
be
recording
for
use
to
the
interested
parties,
so
a
lot
of
that
is
going
on,
especially
especially
you
see
in
UK
banking
and
baby
hospitals,
where
you
need
to
share
records,
but
probably
it's
time
base
sharing
to
get
shared
and
after
everything's
kind
of
settled
down
at
some
point,
the
seller
may
choose
to
disclose
the
existence
of
the
contract
and
some
of
the
details
to
specific
the
specific
collection
of
factors.
Only
these
factors
chosen
by
the
seller
may
see
the
information
in
the
cell
exposes
just
about
the
contract.
B
Okay,
each
fact
may
create
big
for
the
for
the
contract.
Details
of
the
bit
may
be
only
known
to
the
batter
and
the
seller.
However,
the
fact
it
must
commit
to
the
mid.
So
perhaps
this
is
a
little
bit
more
like
Wall,
Street,
ish
sort
of
like
financially
the
Stella
may
chose
one
big
and
executed
transfer
of
ownership
generate
through
the
bid
was
selected
at
this
point.
Winning
the
fight
to
mix
the
only
information
about
the
contract
after
hand
off
the
original
selling.
Local,
no
longer
see
changes
in
the
contract
or
make
modifications
to
it.
B
B
Some
discussion
and
some-
but
this
is
what
the
paper
tries
to
get
for
participants-
have
the
ability
to
could
to
keep
danger
about
the
transactions
confidential
entitlement
to
danger
access
control
lights.
This
made
through
the
ability
to
hide
the
existence
of
objects
like
the
contract
participants,
have
the
ability
to
choose
when
and
with
whom
to
disclose
the
data
participants
have
the
ability
to
selectively
disclose
part
of
the
data
with
chosen
parties
and
the
right
to
disclose
information
is
transferred
with
with
ownership
transfer.
B
A
B
B
So
the
method
for
analysis,
the
fact
to
supply
usage
described
in
the
previous
section-
shows
the
potential
complexity
of
information
and
access
policies
for
even
relatively
simple
usages.
Adult
methods
reevaluating.
The
preservation
of
confidentiality
provided
by
specific
blockchain
platform,
can
lead
to
incomplete
and
affect
ineffective
analysis.
We
would
like
to
propose
a
more
full
method
for
evaluating
whether
a
blockchain
platform
meets
the
functional
requirements
for
usage.
B
Our
proposal,
which
is
the
pavement,
consists
of
a
formal
definition
of
material
models
and
a
method
for
explicitly
capturing
a
functional
requirement
using
a
cryptographic
gain
so
I
think
in
the
probably
all
read
the
big
corn
paper
or
aware
of
it.
So
what
we're
doing
here
is
we're
we're
not
going
down
that
path.
We're
going
down
a
path
which
is
specific
for
permission
blocking,
and
so
the
examples
in
the
paper.
B
We're
going
to
add
something
into
the
paper
I
mentioned
drive-in.
Tell
people
correctly
pick
what
is
their
adversary
along
inside
their?
You
know
problem
that
business
news
case,
so
the
we
do
have
the
Byzantine
anniversary
we've
got
selected,
Byzantine
anniversary,
we're
going
to
adopted,
crush,
won't
tolerance.
My
good
the
honest
book
here
is.
B
B
I'm
sure
did
a
great
job
there,
but
I'm
going
to
come
back
to
this
reference
system,
which
I
think
ties
it
together,
so
because
that's
okay,
so
here's
how
we
moved
from
like
the
academic
to
the
probe
to
the
product.
Okay,
we
use
something
called
the
reference
system
moment
can
be
very
difficult
to
properly
analyze
privacy,
confidentiality
in
a
rigorous
way
to
the
complexity
of
watching
systems,
improving
properties
of
blockchain
systems
in
settings
that
involve
real
rules
and
things
like
continuous
time
and
outside
influences
can
be
extremely
difficult
or
outright
impossible.
B
So
one
way
to
analyze
the
privacy
confidentiality
property
distributed
alleges
this
consider
a
reference
model.
In
this
context,
a
reference
model
is
a
construct
for
the
analysis.
It's
not
intended
to
be
a
practical
system,
so
we
actually
going
to
introduce
something
called
the
ideal
system.
So
we
kind
of
like
cheat
a
little
bit.
Surely
yeah
I
remember
taking
something
pretty
in
about
CS
classes
and
and
profess
a
cup
to
like
this
big
old
number
on
the
board
and
just
kind
of
pulled
it
one?
B
B
B
A
B
A
B
To
try
make
to
answer
your
question
aim
to
make
the
concept
more
concrete.
Okay,
we
use
the
bulletin
board
system.
Is
the
ideal
solution
for
supply
chain
flat
training
described
previously.
We
can
imagine
a
solution
that
works
at
faults
where
user
sends
the
encrypted
message
to
them
or
the
board
post.
It
makes
it
available
to
the
hospital
in
encrypted
form.
The
bulletin
board
is
also
responsible
for
ordering
messages
as
they
come
in,
which
is
kind
of
like
what
fabric
is
doing.
The
order
with
its
ordering
any
encryption.
B
B
B
B
B
Extend
to
viewing
so
the
technologies
we
just
mentioned,
so
what
happens
here
conceptually?
The
Enclave
is
setups
acuity,
which
is
kind
of
like
this
has
kind
of
been
pretty
important,
in
other
words,
the
act
when
he
says
the
only
actually
talking
about
the
CPU
inside
inside
inside
the
the
server.
So
that's
that's
secure.
B
B
We
know
that
the
Alice
have
Bob
sent
ten
thousand
transactions.
Special
addresses
can
be
used
to
can
also
change
the
addresses
to
intensity,
to
keep
things
more
secure.
We
could
watch
the
private
Enclave
everyone,
even
big
Percy
group,
has
access
to
the
to
it
to
the
information.
So
we
set
up
a
group
think
only
that
group
has
the
information
to
that.
B
B
B
B
Is
well
one
of
the
things
I'd
like
to
show
is
that
different
people,
who
are
experts
in
different
areas
of
the
technologies
that
we
contribute
and
they're
still
contributing
into
this
resemble
odds,
is
senior
researcher
at
Fujitsu
is
kind
of
more
an
expert
in
really
experiencing
the
security
has
been
focusing
on
the
zero
knowledge
proof.
That's
like
a
huge
bonus
area
and
so
anyways.
B
Well,
the
neat
things
about
some
of
these
TED
talk
talk
I'm
seeing
people
is,
they
can
boil
things
down
just
a
couple
of
sentences,
so
you
can
get
the
value
without
actually,
you
know
being
an
expert
in
cryptographic
proofs.
This
is
the
system.
Another
thing
we're
trying
to
elevate
with
the
papers
here
we're
trying
to
make
the
paper
that
is
consumable
by
sort
of
like
that,
a
general
audience.
You
know
who
was
thinking
about
CTO
issues,
but
not
necessarily
deep,
deep
experts
in
cryptography.
B
B
The
hide
alleged
blocking
projects
are
perhaps
different
than
some
other
projects
in
some
widgets.
By
doing
the
segmentation,
that's
how
we're
able
to
to
restrict
us
access
to
say
the
information
at
certain
times
and
and
then
there
are
cryptographic
protocols
that
are
applied
to
each
one
of
those
segments
such
as
you
know,
encrypting
the
danger
electric
in
the
day
using
ZK
personal
decency,
capers
and
the
same
happens
not
only
on
the
ledger,
but
also
of
the
contracts
themselves.
So
the
contracts
we
can,
you
see,
secured
the
contract.
B
B
To
do
Lucca
and
processing
and
what
they
found,
that
is,
that
they've
been
optimized
in
such
a
way
that
when
they're,
actually,
when
the
memory
is
doing
this
Luca,
add
it's
actually
in
an
unencrypted
state.
So
if
you've
got
to
piece
it
to
that,
while
the
data
is
an
unencrypted
state
that
it's
easy
to,
scrape
that
key
off
and
and
then
to
have
a
system.
So
this
is
where
the.
B
Especially
if
you
set
it
up
a
permission
network
on
a
cloud
provided
and
you're
gonna
have
different
business
participants
from
Federation
you'd
want
to
choose,
or
do
some
digging
around
to
make
sure
that
they've
got
these
SPX
processes.
So,
for
example,
when
you
use
I
believe
when
you
use
IBM's
service,
they
will
they
will,
but
these
SGI
processes.
B
B
B
B
Parts
of
its
blocking
platform
I
mean,
for
example,
one
of
the
things
that
became
apparent
was
they
have
this
sort
of
a
concept
that
like
three
columns,
they
have
the
small
contract
column,
where
the
business
logic
is
in
the
small
contract,
but
also
the
the
segmentation
logic
is
in
the
small
contract.
So
I
can
have
logic
from
my
business.
You
know
what
happens
in
this
student
conditions.
We
do.
B
Agree
to
agree
to
execute
on
the
constant
light
rain
contract,
but
then
another
one
is
what
else.
What
also
I
can
put
into
into
the
small
contract
is
I
can
also
put
into
the
small
contract
what
the
sharing
is
in
the
data
and
saving
the
timeliness,
whether
they
think
to
shed
or
not,
and
the
third
thing
I
can
actually
do
with
hyperlinks
in
I'm
glad
your
project
is
I
can
actually
propagate
all
of
those
and
upgrade
the
network
itself
through
the
small
contracts.
So
that's
the
first
column.
A
B
May
be
a
legacy
datastore,
but
then
they
notice
I
to
that
is
I've
got
a
blockchain
that
will
actually
share
business
between
my
business
parties
and
so
that
that
three
column
model
is
that
it
paid
to
me
to
be.
You
know
where
they
were
where
they
were,
where
they
have,
they
sort
of
rearrange
things
when
were
looking
at
things,
and
so
when
it
comes
to
choosing
an
alleged
project,
you
might
say:
okay
well,
fabric
is,
you
know,
has
a
lot
of
bells
and
whistles
that
fits
into
that
for
my
this
year
alone.
B
So
one
thing
we,
we
added
head
to
the
paper
to
train
this
produced
soon,
because
there's
a
lot
of
text
in
the
baby,
but
one
thing
we
want
to
do
is
to
try
tabulate
some
things
to
tabulate,
so
you
can
actually
look
at
it
and
see
what
the
difference
is
on.
So
where
can
we
have
got
that
underway
right
now?
So,
but
I
think
we
were
doing
that
with
respect
to
the
capabilities
you
know,
fabric
soldier
bra
borrow.
B
It
looks
like
we
have
a
table.
The
images
currently
underway,
they're
being
filled
in
so
one
of
the
things
that
came
up
here
is,
is
that
a
lot
of
the
engineers
and
the
focused
on
building
the
projects,
that's
kind
of
like
their
complete
focus?
They
have
no,
and
even
though
they're
under
the
green
house
and
everything
because
everything's
open
source
is
shared,
their
focus
is
on
the
products
and
it's
not
always
on
amplifying
what
the
differences
are
in
the
products
such
as
another
reason
we
wrote
the
paint
bag
and
another
reason.
B
For
example,
I
mean
somebody
may
have
added
zk
Troost
to
that
to
their
products
are
writing
to
be
the
addition
of
identity,
which
is,
and
that
could
be
like
community
next
released,
so
we're
going
to
make
that
sort
of
like
each
of
the
product
happens,
I'm
also
a
weekly
forum.
So
it's
a
living
document
rather
than
there
are
white
paper
which
will
go
out
to
day
today.
You
know
nearly
days.
B
It's
kind
of
interesting,
because
a
couple
of
these
projects
or
growers
based
in
Japan
and
I
got
me.
A
I
took
the
research
of
that
because,
in
order
to
1932
can
do
capabilities
what
the
pros
and
cons
of
the
product
were.
So
it
took
some
digging
around
in
order
to
get
this
ain't
elevating
this
information,
so
it
could
make
those
the
differences
see
what
the
differences
were
seen
between
D
and
with
borrow
with
so
most
of
the
folks
you'll
see
these
double
brackets.
Who
are
really
the
CTO?
It
will
be
original
engineers
for
those
products.
B
B
B
B
The
systems
are,
do
have
some
approaches
that
you
can
use
to
attack
them.
So
we
wanted
to
to
try
and
produce
an
educational
pavement.
It's
fairly
consumable
to
just
show
what
the
differences
are.
It
may
be,
and
also
the
approach
to
keeping
it
a
living
document
rather
having
in
a
sort
of
a
white
pavement.
So
you
like
a
Bitcoin
time
paper
that
you
never
just
set
it
in
stone
from
the
date.
A
A
At
the
recent
conference,
different
pillars
approach
they
use,
or
they
support
hyper
ledger
and
I.
Think
in
pricing,
theory
and
I
think
our
3/4
recent
announcement.
It
seems
to
me
that
that
has
some
real
value
expand
the
scope
to
include
those
within
I
know
the
scope
you're
doing
this,
but
as
any
thought
or
consideration
given
to
expanding
Nexus
I.
Think
people
really
appreciate
what
you've
done
here.
A
B
Definitely
is
that's
crossed
my
mind
a
couple
times,
but
the
other
thing
that's
also
come
up.
Is
that
some
of
these
folks
that
are
working
on
this
paper
now
the
lead
engineers
who
are
driving
some
pretty
significant
engineering
teams
or
research
behind
them,
and
they
just
want
to
finish
this
dog
paper.
B
A
B
Anyway,
you
can
see
there's
a
little
anything
here
like
publish
it,
and
that
was
the
reason
why
it
was
like
hey.
Let's
take
the
the
method
of
approach,
let's
make
that
kind
of
more
frozen
wiki
document,
but
then,
let's
make
a
page
reach
of
the
projects
so
that
they
can
be
updated,
but
I
think
it
would
be
really
useful,
especially
to
see
to
have
some
analysis.
You
know
for
the
approach
of
the
microseconds,
apparently
taking,
which
is
where
they
recognize
that
coexistence
is
really
important.
B
It's
really
hard
to
kind
of
just
somebody
to
just
pull
out
their
business
system
and
just
put
in
the
blockchain
based
system,
especially
when
it
doesn't
have
a
lot
of
the
capabilities
systemized.
We
think
you
could
make
it
coexist
and
that's
a
pretty
sweet
thing,
because
then
you
can
start
to
do
some
things
like
that
must
be
like
to
do,
which
is
like
share
production
data,
and
if
you
can
share
production,
they
can
get
rid
of
some
of
these
cultural
differences
between
the
management's
and
then,
if
you
can
do
that
in
the
batteries.
A
B
B
B
B
That's
an
explosive
overall
penis,
most
folks
want
to
buy
these
types
of
technologies
and
also
want
to
acquire
the
team's
expertise
as
well,
because
when
you
bounce
around
in
these
technologies,
peen
hands
over
them
for
a
while,
actually
produce
something
he
never
doesn't
mean
in
commercially
successful
kind
of
in
quiet,
useful
skills
and
that
it's
body
will
to
other
folks.
For
you
know,.
A
It
and
just
so
everybody
knows
our
next
meeting
will
be
back
here:
November
12th,
we
have
Zach
he's
from
Denver
and
Zula
sorry,
Denver
Colorado
with
the
company
called
zua
and
they'll,
be
looking
at
real
world
experiences
with
building
on
hyper
ledger,
so
it'll
be
another
more
technically
focused
conversation
and
we're
kind
of
rounding
the
year
with
a
little
bit
more
getting
a
little
bit
more
than
week.
So
thank
you
so
much
for
coming
really
appreciate
it.