►
Description
Al Brandt & Eric Vaughn, BlocLedger
BlocLedger integrates with market leading document centric solutions to track, authenticate, manage and securitize e-signed documents. BlocLedger’s API enables an easy on ramp for digital transaction management companies to secure and manage high-value and high-risk asset documents in a compliant and secure fully digital environment with blockchain.
BlocLedger will demonstrate the execution of an auto lease agreement that is electronically signed, stored and transferred as a securitized asset between parties using blockchain. Leveraging Hyperledger Fabric's privacy and confidentiality features delivered in v1.2, documents are tracked, stored and managed using the Private Data and state-based endorsement features. We'll show the overall demo architecture, step through how transactions are processed, and follow the flow of a document through the architecture. Specific attention will be paid to how the document asset is stored, managed and transferred within the Fabric blockchain. Lastly, we'll discuss the trade-offs one can make while deciding what information gets stored on-chain versus off-chain (Private Data).
----
Hyperledger – Open Source Blockchain Technologies
Hyperledger is an open source community focused on developing a suite of stable frameworks, tools and libraries for enterprise-grade blockchain deployments.
It serves as a neutral home for various distributed ledger frameworks including Hyperledger Besu, Fabric, Sawtooth, Indy, as well as tools like Hyperledger Avalon, Cactus and libraries like Hyperledger Aries, Ursa. Learn more about Hyperledger projects: https://www.hyperledger.org/use
Case Studies: https://www.hyperledger.org/learn/case-studies
Training & Certification: https://www.hyperledger.org/learn/training
Tutorials: https://www.hyperledger.org/use/tutorials
Webinars: https://www.hyperledger.org/learn/webinars
Events: https://www.hyperledger.org/events
Vendor Directory: https://www.hyperledger.org/use/vendor-directory
Subscribe to the Hyperledger Newsletter: https://www.hyperledger.org/newsletter
Follow-us on Twitter @Hyperledger
Learn about Hyperledger Membership: https://www.hyperledger.org/about/join
#Hyperledger #HyperledgerGlobalForum2018 #Blockchain
A
Good
afternoon
everyone
we're
gonna
go
ahead
and
get
started.
It's
I
think
it's
4:40
and
I.
Think
Eric
and
I
sit
between
you
and
cocktails.
So
we
want
to
to
stay
on
schedule
here.
My
name
is
al
Brandt.
This
is
Eric
Vaughn,
we're
both
from
black
ledger.
We
are
community
contributors
to
hyper
ledger
fabric
have
been
around
the
space
since
version
0.6,
so
we
have
quite
a
bit
of
experience
with
fabric
and
we
have
focused
our
company
on
document-centric
processes
and
using
blockchain
to
leverage
the
digitization
of
those
document.
A
Centric
processes,
we're
gonna
focus
on
a
very
specific
use
case
today
called
securing
high
value
asset
documents,
and
with
that
example,
we
will
show
how
our
underlying
API
technology
is
used
in
what
is
happening
underneath
with
fabric
from
both
a
transaction
processing
perspective
and
privacy
and
confidentiality
features
around
private
data
and
Eric
will
go
into
details
associated
with
that.
So
we'll
start
off
with
just
explaining
the
use
case.
A
So
with
that
let's
go
ahead
and
get
started.
So
when
we
talk
about
high
value
asset
documents,
these
are
the
documents
that
are
actually
securing
the
financial
interest
of
the
institution
that
is
loaning
and
finance
in
providing
the
financing
around
the
purchasing
of
some
physical
asset.
And
so,
if
you
look
at
the
three
largest
vertical
is
associated
with
that
that's
the
home
mortgage
industry,
autos
and
then
equipment
finance.
A
So
it's
very
important
that
the
financial
institution
has
the
ability
to
get
their
hands
on
these
documents,
otherwise
they
lose
their
right
to
protect
the
collateral
collateral
behind
that
document.
So
if
we
take
a
step
back
a
little
bit
further
and
we
look
at
the
electronic
document
process,
we
really
have
three
major
components.
One
is:
everyone
starts
off
with
an
origination
that
origination
is
customized
to
the
specific
terms
and
conditions
of
the
transaction
that
will
be
taking
place
in
this
transaction
can
be
business
to
business
business
to
consumer,
but
from
the
unique
terms
and
conditions.
A
The
agreement,
then,
is
electronically
signed
and
finalized.
As
an
agreement
from
that
package
of
documents
or
the
clothes,
you
then
need
to
manage
how
those
documents
are
treated
post
clothes
from
a
life
cycle
perspective
and
with
these
financial
instruments
you
have
the
ability
to
securitize
them.
A
So
what
will
be
used
is
the
API
software
that
we've
developed
as
a
company.
It's
all
around
the
treatment
of
documents,
and
so
you
know
we
won't
get
into
the
specifics
of
this.
If
people
have
an
interest
in
the
leveraging
of
the
API
and
the
use
of
an
API
and
a
future
proof
of
concept,
you
know
please
come
see
us.
Our
focus
here
is
to
help
with
the
education
around
fabric
and
the
intricacies
associated
with
that.
One
of
the
things
we
will
be
demonstrating,
though,
is
we've
done.
A
A
custom
integration
with
an
e
sign
piece
of
software,
and-
and
so
you
know
all
of
this
will
be
integrating
with
existing
software
Suites.
None
of
this
will
really
come.
Natively
out
to
the
industry
will
all
be
integrated
within
a
CRM
or
within
some
type
of
enterprise
content
management
platform,
things
of
that
nature,
and
so
we'll
show
that
integration
and
how
its,
how
it's
used
and
leveraged.
A
So
we
sit
as
an
infrastructure
technology
play.
We
sit
on
top
of
fabric
everything
we
do
relates
and
leverages
fabric
as
the
underlying
blockchain,
and
then
you
have
applications
that
sit
on
top
of
us,
which
would
be
a
lending
platform.
Things
of
that
nature
and
that
market
is
called
digital
transaction
management,
which
is
really
just
the
digitisation
of
document-centric
processes.
A
A
So
with
that
I've
got
to
go
to
glasses
now
and
let's
see
what
we
got
here
so,
first
of
all,
what
will?
What
will
we'll
start
with
is
this?
Is
the
the
e-signature
app
that
we're
integrated
with?
Is
a
company
called
one
span?
Think
of
this
as
DocuSign
or
Adobe
psy
and
things
of
that
nature,
and
simply
what
you're
doing
is
you're
going
to
be
loading
templates
into
the
software
I?
Have
a
template
already
loaded?
That's
a
draft
and
it's
to
do
an
auto
lease
of
a
BMW,
and
we
will
go
ahead
and.
A
Start
insted
already
instrumented
for
signature,
and
so
here's
myself
and
Eric-
and
these
are
all
instrumented
for
signature
and
signing
okay
back
here.
What
we
have
is
a
browser
interface
to
our
server
software,
and-
and
this
is
the
actual
blockchain
itself
running
on
fabric.
We
have
the
the
full
transaction
list
recorded
with
the
various
with
various
blocks
of
791
blocks.
So
this
is
utilizing
our
document
management
software,
which
is
built
around
packages
and
packages
being
an
aggregation
of
multiple
documents.
A
So
here
is
the
auto
lease
BMW
we
are
like
I,
said
integrated
in
with
the
signature
app
and
with
it
you
know
we're
capturing
event
logs
and
in
Auto
trails
we
have
a
package
create,
which
is
what
exists
over
here
in
this
in
this
application.
So
if
we
now
send
this
to
sign,
both
Eric
and
I
will
get
email
notifications
associated
with
having
a
document
ready
for
signature.
A
So
so
here
we
have
the
auto
lease
it
is
going
to
Eric
Eric
has
a
personalized
license:
plate
called
fabric
he's
such
a
fan
of
fabric
and
the
various
terms
and
conditions
associated
with
the
laces,
so
I
will
sign
it.
It
will
automatically
date
it
for
me,
and
now
it's
applying
the
digital
signature
associated
with
my
signing.
A
A
And
I
don't
know
if
that,
if
we
look
at
the
audit
trail
that'll
give
us
the
details.
Each
of
these
are
written
as
a
blockchain
transaction.
You
know
what
you
see
here
is
we've
done
this
from
demonstration
perspective.
You
have
to
make
decisions
on
what
you
want
to
record
as
a
transaction,
what
you
want
to
pool
as
a
set
of
transactions-
and
it's
all
about
you-
know
your
use
of
the
blockchain
and
where
you
think
various
value
will
will
be
added,
and
so
these
are
the
audit
trails
associated
with
digital
signing.
A
You
know
you
have
to
here
with
the
red
Xs
because
it
had
not
been
the
event
which
we
grabbed
from
the
signature
application
and
not
been
validated
to
the
blockchain
if
we
refresh
that
should
clean
up
to
all
good
okay.
So
now,
if
we
go
back
to
our
list
packages
here
we
have
the
auto
lease
BMW.
We
have
the
two
documents
which
were
the
electronic
disclosures
and
the
auto
lease.
A
If
we
go
look
at
the
actual
document
that
was
signed
itself,
we
can
now
grab
that
from
the
private
data
repository
associated
with
the
various
peer
nodes
within
fabric
and
pull
up
the
document
and
takes
a
little
bit
of
time.
And
so
it's
going
to
now
open
the
PDF
and
it
is
going
to
show
the
actual
document
with
the
digital
signatures
applied
by
both
Eric
and
I
time
stamped
through
the
electronic
software
and
in
recorded
all
as
transactions
on
the
blockchain.
Okay.
A
With
that,
though,
we
keep
a
full
history
associated
with
the
package
and
the
signing,
and
this
is
important
because
you
have
to
prove
in
a
court
of
law
that
this
actually
took
place
and
in
so
here's
the
various
events,
the
timestamps,
the
transactions
that
existed,
and
it
should
conclude
with
a
download
that
took
place.
Okay.
So
now
we
have
this
document
and
should
Eric
default
on
his
lease
payments,
to
provide
proof
of
this
document
that
it
secured
by
my
institution
in
order
to
have
legal
right
to
repossess
that
car
from
Eric.
A
Otherwise
he
has
a
case
that
it
was
never.
You
know
that
I
fully
handled
the
terms
of
my
agreement
and-
and
you
do
not
have
a
right
to
it
so,
but
now
I-
want
to
free
up
additional
capital
such
that
I
can
further
lend
to
additional
users.
So
I'm
going
to
go
ahead
and
transfer
this
asset
to
a
pool
of
investors.
They
happen
to
reside
over
on
org
three.
A
And
so
before,
I
go
there.
My
investors
are
over
here
in
this
browser
window.
Here's
my
investors.
They
have
already
auto
lease,
Toyota
and
and
Oddie
will
just
refresh
and
make
sure
there's
nothing
else
out
there,
and
we
will
go
ahead
then
and
transfer
that
that
auto
lease
to
the
investors.
All
of
this
is
handled
by
the
chain
code
residing
on
the
pier.
So
you
know
this
is
very
tightly
managed
from
security
and
in
transparency
perspective.
Part
of
the
the
regulation
requires
a
two
step
approach
to
transferring
an
asset.
A
You
not
only
transfer
out,
but
you
have
to
select
and
and
selectively
approve
the
transfer
in
to
what's
called
your
electronic
vault.
So
the
investor
pool
has
a
transfer
in
request.
We
could
actually
reject
this
transfer,
and
so
then
we're
just
saying
we
just
don't
want
it.
So
the
the
package
has
been
rejected.
If
we
go
back
here
and
refresh
it's,
the
transfer
was
rejected.
Okay,.
B
A
So
we
will
then
physically
then
we
will
selectively
cancel
that
transfer,
so
all
of
this
once
again
being
recorded
as
historical
events
providing
the
full
transparency
of
the
to
tea
on
the
blockchain,
so
transfer
reject
by
investors,
and
then
the
cancel
all
right.
So
this
time,
though,
we're
going
to
transfer
and
we're
going
to
force
the
investors
to
accept
this
thing.
A
And
the
asset
now
is
owned
and
recorded
through
the
investors.
Once
again,
if
we
look
at
the
event
history,
you
know
we
keep
the
full
historical
capability
between,
with,
with
the
final
accept
from
the
investors
from
from
myself.
So
we
can
also
control
access
and
usage
from
other
members.
We
could
add
a
in
an
auditor
function
that
could
look
that
could
provide,
read
access
to
the
to
the
documents
itself
and
and
so
on.
A
And
now
our
package
has
been
augmented
with
not
only
the
signed
lease
and
the
disclosure,
but
the
insurance
policy
associated
with
the
auto
lease.
Okay,
and
so
this.
These
are
the
capabilities
that
we've
built
based
upon
our
API,
but
what's
really
making
a
lot
of
this
happen
and
what's
simplifying
this
whole
process
are
the
capabilities
of
fabric
in
how
it
is
processing
transactions
and
how
the
private
data
capability
is
being
leveraged
to
provide
full
privacy
and
confidentiality
without
adding
additional
overhead
to
the
blockchain
itself.
A
B
Okay
I
said
I'm
gonna
go
through
and
describe
some
of
the
details
that
goes
on
a
hyper
laser
fabric
as
we
as
we
do
these
transactions
first
we'll
go
through
a
transaction.
You
know
the
basic
transaction
flow
and
then
we'll
take
a
another
pass
through
it
talking
about
private
data
and
how
a
document
is
handled
in
in
the
private
data
case.
B
So
for
the
discussion
we'll
use
this
basic
picture,
it
shows
a
high
per
litter,
brick
with
two
organizations,
and
it's
made
up
of
a
bunch
of
nodes
which
are
the
boxes
there
and
the
blue
ones,
the
p1,
p2
or
two
peers.
So
each
of
the
organizations
have
two
peers
in
them.
The
peers
have
a
chain
code
attached,
that's
kind
of
the
yellow
box
over
the
CC
and
a
ledger:
the
red
box
and
hyper
ledger
fabric.
B
B
B
And
then
each
organisation
could
have
their
own
application
and
then
I've
got
a
UI
shown
there.
So
as
we're
going
through
the
demonstration,
I'll
clicked
on
different
things
and
then
and
those
were
requesting,
the
transaction
of
some
sort
from
the
UI
that
went
to
the
application
and
the
application
will
take
that
that
request
from
from
the
UI
newsy
sdk
and
build
a
proper
transaction
proposal
for
it
and
I'll
use
the
credentials
based
on
the
user
that
that
that
did
the
request
and
actually
sign
that
transaction
proposal
with
that
users
ID
and
then
it'll.
B
Take
that
that
proposal
and
we'll
send
it
to
each
of
the
peers
in
the
network
and
the
peer
will
validate
that
as
a
proper
proposal
and
forward
that
on
to
the
chain
code
and
the
chain
code.
At
that
point,
we'll
do
a
simulation
of
the
transaction
and
the
transaction
is
really
going
to
be
a
function,
call
to
the
chain
code
and
some
information
in
terms
of
arguments
to
go
along
with
that.
That
transaction
the
chain
code
will
go
through
and
it
will.
B
It
will
simulate
that
transaction
wait
and
what
that
means
that
I'll
go
and
read
the
values
out
of
the
world
state
that
it
needs
to
perform.
The
transaction
and
I'll
come
up
with
new
results
that
should
be
written
into
the
world
State
when
it's
all
said
and
done.
But
at
that
point
it
just
simulates
it.
B
So
then
the
the
application
will
take
each
of
those
endorsements.
You
know
create
a
real
transaction
that
will
have
their
transaction
proposal,
the
results
from
the
chain
code,
and
then
this
the
digital
signatures
from
each
of
the
each
of
the
peers
and
I'll
send
that
transaction
to
the
order
in
the
order.
At
this
point,
we'll
put
it
into
a
block
and
it
that
the
order
doesn't
do
any
validation,
it
doesn't
run
the
you
know,
it
doesn't
have
chain
code,
it
doesn't
run
any
of
this.
It
doesn't
have
the
world
state
all
it
does.
B
B
At
that
point,
and
for
our
demonstration,
we
use
the
default
values
of
ten
transactions
per
block
or
two
seconds,
and
then
the
order
will
distribute
that
blackout
to
each
of
the
peers
and
the,
and
then
the
peers
will
go
through
a
validation
phase
and
in
this
validation
phase
the
peers
will
check
to
see
if
there's
enough
endorsements
on
the
transaction
to
meet
the
endorsement
policy,
and
if
the
the
world
state
has
changed.
The
simulation
was
done
now.
B
The
endorsement
policy
that
gets
set
on
a
Tran
chain
code
by
chain
code
basis
in
it
and
you
know
for
and
you
the
writer,
the
chain
code
or
the
whoever
deploys
a
chanko
can
decide
what
they
want.
This
endorsement
policy
to
be
in
the
case
of
this
small
network,
you'd
probably
want
both
both
organizations
to
endorse
it
with
at
least
one
peer
and
then
also
they
also
check
that
the
world
state
hasn't
changed.
B
So
if,
if
a
transaction
comes
in,
you
know,
two
translation
could
be
in
place
in
the
same
block
that
happen
to
change
the
same
information
in
the
world
state
and
what
will
happen
is
only
the
first
transaction
that
the
peer
goes
through
will
get
get
approved,
that
pier
will
update
the
world
state
and
then
on
this.
The
next
transaction
that
that
tries
to
make
the
same
change
to
the
world
state
or
change
the
same
same
information.
B
World
state
will
get
get
reject
it
rejected
it'll,
be
marked
as
invalid,
and
so
the
peers
will
go
through
each
of
these
transactions
one
by
one
and
if
they're
valid
will
update
the
world
stay.
Fourth
and
market
is
valid.
If
it's
not
valid
or
there's
some
conflict
there,
it
will
mark,
the
transaction
is
invalid
and
whether
the
transaction
is
valid
or
not,
it
stays
in
the
block
and
then,
once
all
that's
been
checked,
the
block
will
be
appended
to
the
blockchain.
B
B
So
now
we'll
go
into
the
the
document
flow.
Everything
that
we
just
covered
will
be
done
as
well,
and
then,
with
this
we're
going
to
add
some
new
elements
to
it
and,
as
you
can
see,
we've
got
private
data
collections
in
use
and
we've
got
a
org
one
special
specific
to
order.
Guan
the
org
one
collection
and
we've
got.
B
But
this
at
this
point
can't
put
it
into
the
real
private
data
collection,
so
that
data
goes
into
you.
What's
called
the
transient
data
store
and
I'll
sit
there
during
the
endorsement
and
validation
phase
and
then
get
used
later
in
the
validation
phase.
If
the
transaction
goes
through,
the
transaction
does
not
go
through
then
it'll
get
cleaned
up
out
of
here
after
some
number
of
blocks,
which,
which
is
a
configurable
parameter.
B
But
at
this
point
the
chain
code
will
will
respond
back
to
the
pier
and
we'll
go
through
the
whole
process.
We
talked
about
before
our
pier
we'll
send
it
back
to
the
application
application,
we'll
kit
up
a
transaction
that
will
go
to
the
order
and
then
the
order
we'll
distribute
it
back
to
the
peers,
and
we
come
back
here
to
the
validation
phase
and
in
the
validation
phase.
If
everything
is
okay
with
the
transaction,
the
the
pier
will
update
the
world
state
and
also
move
the
transient
data
store
into
the
the
private
data
collection.
B
And
then
coming
back
out
to
the
larger
picture,
so
at
this
point
we've
got
the
we've
got
the
document,
it's
in
the
org
one
collection,
and
at
this
point
only
only
or
Guan
has
access
to
us.
So
a
transaction
that
goes
to
pure
or
one
of
the
peers
in
or
guan.
That
will
be
able
to
read
that
data.
But
if,
if
a
transaction
goes
to
that
one
of
the
piers
in
org
two,
it
will
not
be
able
to
read
the
data
and
then
our
access
control
piece
will
control.
B
B
C
B
B
It's
it's
in
a
separate
database,
and
so
here
what
you
can
actually
do
is
you
could
run
another
transaction
to
delete
this
data
but
delete
it
out
of
the
private
data
collection
and
there'll
be
no
record
of
it
at
that
point,
and
the
the
main
chain
just
has
information
about
the
transactions
and
a
hash
of
the
data.
Okay
and
then
just
to
follow
up
question
what
what
is
it
is.
C
B
C
A
C
And
I
understood
that
the
order
here
is
acting
like
a
centralized
entity
right,
so
the
order
of
the
green
box
there
yeah
okay,
we're
trying
to
avoid
this
like,
but
wouldn't
this
cause
an
issue
like
if
you,
if
you
just
make
this
as
a
centralized
where
it
will
distribute
the
document
to
all
beers,
I
mean
the
idea
of
blockchain,
is
just
to
have
like
a
DC
DC,
a
decentralized.
You
know
concept
and
now
here
the
order
will
be
sitting
in
the
middle
yeah.
B
Male
role:
oh,
the
main
role
of
the
order,
is
simply
to
keep
the
transit,
be
the
authority
on
the
the
blocks
and
what
goes
into
the
blocks
and
the
order,
the
transactions
in
the
block
and
then
the
order,
the
blocks.
So
every
every
pier
out
in
the
system
has
to
have
the
same.
Understanding
of
you
know
what
which
block
comes
first
and
which
transactions
come
first
in
those
blocks.
Okay,.
C
One
more
question
about
the
code
chain:
you
stated
that
each
pier
has
like
its
own
coach,
an
aunt
will
check
and
twelve
validate,
and
if
it's,
okay
now
the
document
will
be
added
right.
What,
if
like
one
of
the
beers
like
core
chain,
has
an
issue
with
it?
Wouldn't
that
be
like,
for
example,
you
know
so.
B
B
Could
you
know,
that's
decay
in
the
application
could
figure
that
out
and
throw
that
that
endorsement
away
or
if
it
included
that
endorsement
it
would
not.
It
would
not
be
correct,
and
so,
during
the
validation
phase,
when
the
peers
look
at
a
it
would
have
a
bad
endorsement,
and
then
you
know
that
which
could
be
okay.
If
your
endorsement
policy
didn't
require
all
four
peers
to
be
part
of
it,
if
it
was,
if
you
only
require
two
valid
endorsements
one
from
each
organization,
then
you
would
you
could
stand
a
bad
peer
in
that
case.
Thank.
C
C
I,
thank
you
for
the
demonstration
I'm
just
curious.
How
are
you
retrieving
the
historical
data
on
on
an
asset?
Typically
I
would
think
it's
more
of
using
like
composite
key
functions
within
the
chain
code,
but
you
showed
how
there
was
a
very
brief
history
on
an
asset
and
where
it
went
and
what
its
latest
date
is
because
I
think
the
you
can
easily
query
the
world
state
but
retrieving
the
historical
data.
It's
in
my
personal
experience
has
been
a
challenge.
Yes,.
B
So
so
we've
got
a
couple
things
there.
We
actually
for
a
package.
You
know,
we've
got
a
more
complicated
data
structure
and
we're
storing
the
event
history
and
the
audit
audit
trail
in
that
package
data
structure.
So
that
might
be
the
one
that
you
were
you
were
talking
about
and
then
the
history
we're
getting
that
from
the
history
of
the
fabric
provides,
and
so
since
we've
got
a
package,
it's
got
a
key
associated
with
that
package
and
we're
getting
the
transaction
history
for
for
the
package
itself
and
and
we're
retrieving
at
that.
That
way.
C
First,
thanks
for
the
very
clean
explanation:
I
got
one
question
about:
let's
say
cleanup
job
when
the
document
is
stored
in
the
transient
data
store
uh-huh
and
you
have
failover
from
the
application
or
something
which
part
of
the
system
will
keep
or
will
execute
this
cleanup
job.
You
mentioned
that
it's
configurable.
So
if
there's.
B
A
yeah,
the
pier
itself,
will
we'll
clean
that
up
and
delete
that
transient
data
and
it
it's
going
to
use
a
kind
of
a
block
count
to
figure
out
when
to
do
that
and
so
like.
If
it
runs
fine,
if
it
moves
it
to
the
the
private
data,
then
I'll
get
delete
at
that
point.
But
if,
if
that
never
happens,
then
you
know
when
a
certain
number
of
blocks
goes
by
it'll
get
deleted
out
at
the
transient
data
at
that
point,
so
the
pure
itself
will
handle
them.
C
B
So
as
part
of
fabric
is,
as
you
scale
this
out,
you
know
you
can
send
an
endorsement
policy
where
you
can.
You
know
if
you've
got
a
hundred
peers
all
doing
this,
and
you
may
not
want
all
of
those
peers
to
endorse
and
run
run
all
of
this,
so
you
could
set.
You
know
just
20
out
of
the
hundred
or
something
to
do
that.
Do
the
endorsement,
and
then
you
know
with
part
of
what
the
on
the
private
data
is.
B
A
C
A
So,
in
other
words,
you
know
we
don't
have
we've
chosen
to
stay
away
from
multiple
channels
with
work.
We've
done
some
of
the
direction
that
we've
heard
from
IBM
is
that,
as
you
get
into
zero
knowledge,
proofs,
the
need
for
channels
becomes
less
and
less
and
and
they
tend
to
keep
you
away
from
a
large-scale
channel
deployment
and
to
focus
more
on
the
minimization
of
channels
within
your
environment.
So.
A
A
So,
although
they're
not
the
ending
using
client,
their
software
simply
enabled
they
tend
to
want
to
see
that
outsourced
and
managed
and
controlled
by
someone
like
ourselves
or
some
other
cloud
provider
or
blocked
universes
service
provider.
So
but
you
know,
you're
you're
dealing
with
existing
software
solutions
that
are
looking
to
helps,
sell
on
the
excitement
and
future
value
of
blockchain,
and
so
they
want
to.
Basically,
you
know,
walk
slowly
so.
C
Of
ownership,
okay,
the
document
the
attachment
is
moved
from
organization,
one
collection,
private
collection
to
organization
whose
private
collection-
that's
true.
Does
that
happen
as
an
atomic
operation
when
the
blocks
are
committed
to
individual
peer
nodes,
or
is
it
asynchronous
because
you
showed
that
attachment
almost
to
the
the
common
collection
and
then
it
moves
to
the
organization
to
collection.
So,
yes,.
B
So
the
move,
the
move
from
org
one
to
the
common
collections
atomic,
but
it
doesn't
doesn't
move.
You
know
you
have
to
run
a
whole
nother
transaction
to
move
it
down
to
or
two
and
then
that
would
be
an
atomic
that'd,
be
one
transaction
to
move
it
down
to
or
two
and
then,
but
once
once
it's
been
initiated
the
documents
no
longer
an
org
one's
collection.
So
that's
why
you
have
to
do
the
the
cancel
if
it
gets
rejected
by
the
new
owner
and
that
cancel
actually
moves
that
document
back
into
the
Oregon
collection.